[opensuse-factory] Status: RC2
Hi, Over the long weekend both factory and 12.1 bootstrapped and I fixed some oversized ISOs. Unfortunately the DVDs did not boot as linuxrc only supports SHA1 and we switched (unknowingly) to to the more secure SHA256 for repository signatures. The tests I ran looked ok, but we have nothing but "SHA256 not supported" from openqa. So we need to rebuild DVDs one more time, but hopefully we have something to publish tomorrow. We still have 2 issues with mysql (#727706 and #712749) and two with systemd (#726823 and #724912). Additionally to that we have this hanging udev in installations that are reported by some - but we had that with 11.4 too, so I'm easy with releasing with the problem. Hardware specific problems come and go and very seldomly it makes sense to wait for updates as they just break other hardware ;( What we need now is testing installation and update stack, everything beside that do not matter at this point but get in the queue for maintenance. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mercredi 02 novembre 2011 à 14:36 +0100, Stephan Kulow a écrit :
Hi,
Over the long weekend both factory and 12.1 bootstrapped and I fixed some oversized ISOs. Unfortunately the DVDs did not boot as linuxrc only supports SHA1 and we switched (unknowingly) to to the more secure SHA256 for repository signatures.
The tests I ran looked ok, but we have nothing but "SHA256 not supported" from openqa. So we need to rebuild DVDs one more time, but hopefully we have something to publish tomorrow.
We still have 2 issues with mysql (#727706 and #712749) and two with systemd (#726823 and #724912). Additionally to that we have this hanging udev in installations that are reported by some - but we had that with 11.4 too, so I'm easy with releasing with the problem. Hardware specific problems come and go and very seldomly it makes sense to wait for updates as they just break other hardware ;(
Right now, #724912 is caused by getting notification from kernel before the raid is active. And unfortunately, I don't see a "smart" way for systemd to detect a mount point is a "md" one and add on the fly a dependency on md.service (ie boot.md) for fsck for this partition. Help is welcome.. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Mittwoch, 2. November 2011 schrieb Frederic Crozat:
Le mercredi 02 novembre 2011 à 14:36 +0100, Stephan Kulow a écrit :
We still have 2 issues with mysql (#727706 and #712749) and two with systemd (#726823 and #724912). Additionally to that we have
Wow, one of my bugreports is famous ;-)
Right now, #724912 is caused by getting notification from kernel before the raid is active. And unfortunately, I don't see a "smart" way for systemd to detect a mount point is a "md" one and add on the fly a dependency on md.service (ie boot.md) for fsck for this partition.
A not-so-smart and quite obvious idea: check if the device name matches /dev/md* ;-) BTW: Would it hurt to always have "After: md.service" in fsck@.service and cryptsetup@*.service? That would be the easiest solution. Regards, Christian Boltz -- Such mal im Archiv dieser Liste nach 'reiserfs', oder genauer, nach 'rasierfs' und 'reisswolffs'. Reiserfs reagiert auf Fehler (diverser Art) wie ne Diva... [David Haller in suse-linux] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le jeudi 03 novembre 2011 à 01:02 +0100, Christian Boltz a écrit :
Hello,
Am Mittwoch, 2. November 2011 schrieb Frederic Crozat:
Le mercredi 02 novembre 2011 à 14:36 +0100, Stephan Kulow a écrit :
We still have 2 issues with mysql (#727706 and #712749) and two with systemd (#726823 and #724912). Additionally to that we have
Wow, one of my bugreports is famous ;-)
Right now, #724912 is caused by getting notification from kernel before the raid is active. And unfortunately, I don't see a "smart" way for systemd to detect a mount point is a "md" one and add on the fly a dependency on md.service (ie boot.md) for fsck for this partition.
A not-so-smart and quite obvious idea: check if the device name matches /dev/md* ;-)
Except we don't have a garantee /dev/md* will be the name used in /etc/fstab or /etc/crypttab (it could be /dev/disk/by-...). It would be better to rely on sysfs (/sys/block/virtual/md ) but the change is non trivial and I don't want to break systemd so close to the release.
BTW: Would it hurt to always have "After: md.service" in fsck@.service and cryptsetup@*.service? That would be the easiest solution.
Yes, that is one possibility, but against, I'm a bit afraid of doing such changes so close to the release. We should probably also add After: dmraid.service too, I guess. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Nov 2, 2011 at 9:36 AM, Stephan Kulow <coolo@suse.de> wrote:
What we need now is testing installation and update stack, everything beside that do not matter at this point but get in the queue for maintenance.
I did a 11.4 Tumbleweed to RC1 update via zypper dup a week ago and found only known bugs as relates to the update. Someone should update http://en.opensuse.org/SDB:System_upgrade to use 12.1 examples. I assume updates via Yast2 Wagon are not supported since the above page has dropped any info about it? Here's the old page: http://old-en.opensuse.org/Wagon If it is meant to be supported, someone should try it and re-integrate the support page into the System_upgrade page. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Christian Boltz -
Frederic Crozat -
Greg Freemyer -
Stephan Kulow