Bug 2606

Summary: Update losetup to add -j option required by schroot
Product: Mageia Reporter: claire robinson <eeeemail>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Normal CC: marja11, stormi-mageia
Version: 1   
Target Milestone: ---   
Hardware: All   
OS: Linux   
See Also: https://bugs.mageia.org/show_bug.cgi?id=2370
Whiteboard:
Source RPM: util-linux-ng-2.18-4.mga1.src.rpm CVE:
Status comment:
Bug Depends on:    
Bug Blocks: 2370    

Description claire robinson 2011-09-03 14:21:41 CEST
The missing option is currently preventing schroot from using loop mounted chroots. An update candidate for schroot is unable to be properly validated, see bug 2370.

-j, --associated file
              show status of all loop devices associated with given file


Source RPM: util-linux-ng-2.18-4.mga1.src.rpm
claire robinson 2011-09-03 14:24:46 CEST

Blocks: (none) => 2370

Manuel Hiebel 2011-09-03 14:33:32 CEST

Assignee: bugsquad => makowski.mageia

Comment 1 Philippe Makowski 2011-09-13 19:03:57 CEST
this is solved in Cauldron
may be this can be close as "fix in next release" ?
Comment 2 Samuel Verschelde 2011-09-14 13:03:39 CEST
(In reply to comment #1)
> this is solved in Cauldron
> may be this can be close as "fix in next release" ?

No, that's not possible. Mageia 1 packages are supported, so we can't dismiss bugs because they are fixed in cauldron.

Assigning back to triage team as you said in bug 2370 that you have no idea how to fix this bug.

CC: (none) => stormi
Assignee: makowski.mageia => bugsquad

Comment 3 Manuel Hiebel 2011-10-30 14:30:51 CET
Thomas, what do you think ?

URL: https://bugs.mageia.org/show_bug.cgi?id=2370 => (none)
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=2370
Assignee: bugsquad => tmb

Comment 4 Marja Van Waes 2012-01-17 14:41:52 CET
(In reply to comment #3)
> Thomas, what do you think ?

@ Thomas

This bug is blocking bug 2370, can you please tell whether there is a chance you'll fix it.

CC: (none) => marja11

Comment 5 Marja Van Waes 2012-04-23 16:54:28 CEST
3-monthly ping
Comment 6 Marja Van Waes 2012-07-06 15:05:23 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 7 claire robinson 2012-07-06 17:04:15 CEST
Seems mga2 has the -j option but I don't think there was any update for mga1.
Comment 8 Manuel Hiebel 2012-11-05 16:53:22 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 9 Manuel Hiebel 2012-12-02 14:32:39 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

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