Bug 2335 - schroot is in updates_testing but there is no update candidate bug report assigned to qa-bugs@ml.mageia.org
Summary: schroot is in updates_testing but there is no update candidate bug report ass...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Philippe Makowski
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-29 23:53 CEST by Samuel Verschelde
Modified: 2011-08-04 11:12 CEST (History)
0 users

See Also:
Source RPM: schroot
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Samuel Verschelde 2011-07-29 23:53:04 CEST 

    


    


      



        
          Comment 1
        

        
          Philippe Makowski

        

        
        

        
          2011-08-01 21:14:04 CEST
        

      






hum
yes, no initial bug report, so no bug report to reassign to qa-bugs 
If I look at Debian, in fact it should go into backport
and if we put it in testing (as Fedora did), it have to be rebuild to take care of the updates policy about release and subrel 
but now there is even a version 1.4.23

so, what to do ?

    


    


      



        
          Comment 2
        

        
          Samuel Verschelde

        

        
        

        
          2011-08-01 21:38:48 CEST
        

      






I depends :
- if 1.4.22 (or 1.4.23) is a bugfix only release then providing an update could be a good idea
- otherwise it's a backport and we should remove it from updates_testing and wait for the backports media to open

    


    


      



        
          Comment 3
        

        
          Philippe Makowski

        

        
        

        
          2011-08-04 11:12:13 CEST
        

      






update build and bug report done #2370


  
Status:
      NEW =>
      RESOLVED
Resolution:
      (none) =>
      FIXED

  

    



  






  


    

      

        

          
            

              Note
              You need to
              log in
              before you can comment on or make changes to this bug.