Description of problem: Tracker for the upgrade bugs.
Keywords: (none) => TRACKERPriority: Normal => release_blockerDepends on: (none) => 3324
CC: sysadmin-bugs => (none)
Severity: critical => normal
Depends on: (none) => 3409
Depends on: (none) => 3780
General ping for Alpha 3
Whiteboard: (none) => QA
Depends on: (none) => 4136
Depends on: (none) => 4150
Depends on: (none) => 4165
Depends on: (none) => 3550
Depends on: (none) => 4569
Depends on: (none) => 4919
Depends on: 3780 => (none)
I haven't opened a separate bug for this because I don't really have a reproducible case, but a testing concern for a 1->2 migration is to check that services previously enabled under sysvinit stay enabled under systemd. It's been my experience with cauldron that as systemd was integrated, enabled services would mysteriously not start at boot time. IIRC cups was once such, and more recently, sshd. Historically, I believe it was left to the individual RPMs to auto-enable their services at statrup, so the probable cause is RPMs not properly updated for systemd. This is fine for cauldron day-to-day, but should be checked for the 1 -> 2 upgrade.
CC: (none) => ftg
Depends on: (none) => 5066
CC: (none) => davidwhodginsDepends on: (none) => 5100
Depends on: (none) => 5101
Depends on: (none) => 5103
Depends on: (none) => 4541
CC: (none) => luigiwalserDepends on: (none) => 5147
Depends on: (none) => 5219
Depends on: (none) => 5357, 5358
Depends on: (none) => 5528
Depends on: (none) => 5535
Depends on: (none) => 5556
Depends on: (none) => 5645
Depends on: (none) => 5646
Depends on: (none) => 5677
Depends on: (none) => 5687
Depends on: (none) => 5686
Depends on: (none) => 5721
Depends on: (none) => 5763
Depends on: (none) => 5746
Depends on: (none) => 5792
Depends on: (none) => 5767
Depends on: (none) => 5796
Depends on: (none) => 5775
Depends on: (none) => 5774
Depends on: (none) => 5791
Depends on: 4136 => (none)
Depends on: (none) => 5307
Depends on: (none) => 4777
Depends on: 5307 => (none)
Depends on: 5687 => (none)
Depends on: (none) => 5942
Depends on: (none) => 5969
Depends on: (none) => 6061
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Depends on: (none) => 6114
Keywords: NEEDINFO => (none)CC: (none) => marja11Depends on: (none) => 6309, 6180
Priority: release_blocker => HighBlocks: (none) => 8016Severity: normal => major
Version: Cauldron => 2
Blocks: (none) => 5140
Blocks: 5140 => (none)
Depends on: 6061 => (none)
CC: (none) => ennael1Blocks: 8016 => (none)
Closing as OLD Mageia 1 isn't supported anymore and upgrading from Mageia 2 to 3 is center of attention, now
Status: NEW => RESOLVEDResolution: (none) => OLD
(In reply to Marja van Waes from comment #4) > Closing as OLD > > Mageia 1 isn't supported anymore and upgrading from Mageia 2 to 3 is center > of attention, now Upgrading from Mageia 1 to Mageia 2 is still supported, and if there are packaging issues in Mageia 2 packages that cause problems, we can still fix those.
(In reply to David Walser from comment #5) > Upgrading from Mageia 1 to Mageia 2 is still supported, and if there are > packaging issues in Mageia 2 packages that cause problems, we can still fix > those. reopening
Status: RESOLVED => REOPENEDResolution: OLD => (none)
Sorry it's not. Mageia 1 is not supported anymore for some time now. If some packages need to be fixed they should be reattributed to Mageia 2. Not for upgrade
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
(In reply to Anne Nicolas from comment #7) > Sorry it's not. Mageia 1 is not supported anymore for some time now. If some > packages need to be fixed they should be reattributed to Mageia 2. Not for > upgrade Um, we know Mageia 1 isn't supported, but if anyone is still running it, they should upgrade. If the upgrade doesn't work because of issues in Mageia 2 packages, they should still be fixed if possible.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Depends on: 5746 => (none)
closing, mga2 will be eol soon
Status: REOPENED => RESOLVEDResolution: (none) => OLD