[opensuse-factory] Tumbleweed - Review of the Week 2015/33
Dear Tumbleweed users and hackers, Despite the summer holidays and the perfect weather seen in Europe, there have been 4 snapshots released in the last week. The most important changes were: * GParted 0.23 update (mainly interesting for GPT) * Libreoffice was pushed to 5.0.0.5, getting you some fixes * Mesa 10.6.3 (fixes crashes when playing videos in VLC with vdpau) * Firefox 39.0.3 (security fixes over 39.0) * BIND 9.10.2P3 (Security fixes) * CMAKE was bumped to 3.3; for once, it was painless * Linux kernel 4.1.4 To our knowledge, is is now finally again possible to put the Tumbleweed ISOs on a USB Stick and boot from it in UEFI environments. Some users seem still to have issues, but those have a different cause; those users also experience issues after updating an existing TW installation; the cause is not yet known What is happening in the future * We are still waiting / working on systemd 222. Staging:A grew to a small monster that does not want to be tamed... but I'm sure the monster is getting tired soon. * Of course the latest kernel will hit you again * KDE Application 15.07.90 are being prepared Have a great weekend! Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dear Dominique, Em sex 14 ago 2015, às 16:20:10, Dominique Leuenberger / DimStar escreveu:
The most important changes were: * GParted 0.23 update (mainly interesting for GPT) * Libreoffice was pushed to 5.0.0.5, getting you some fixes * Mesa 10.6.3 (fixes crashes when playing videos in VLC with vdpau) * Firefox 39.0.3 (security fixes over 39.0) * BIND 9.10.2P3 (Security fixes) * CMAKE was bumped to 3.3; for once, it was painless * Linux kernel 4.1.4
To our knowledge, is is now finally again possible to put the Tumbleweed ISOs on a USB Stick and boot from it in UEFI environments. Some users seem still to have issues, but those have a different cause; those users also experience issues after updating an existing TW installation; the cause is not yet known
I tried to install Tumbleweed in UEFI system from the ISO on a USB stick. Now, it seems that I can boot into the installation. However, when the partitions are read, then YaST crash. I managed to install Tumbleweed by upgrading from openSUSE 13.2. But it turns out that if I open disk module of YaST, it also crashes with the same error, which is: Run command: /sbin/yast2 disk & terminate called after throwing an instance of 'storage::SystemCmdException' what(): parted complains: Warning: failed to translate partition name: "/usr/sbin/parted -s '/dev/sda' unit cyl print unit s print" YaST got signal 6 at file /usr/share/YaST2/modules/ProductFeatures.rb:170 /sbin/yast2: line 434: 18463 Abortado $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS The output of parted command in my system is: http://paste.opensuse.org/3908373 Is it a known bug or should I report? P.S.: By the way, the upgrade from 13.2 to Tumbleweed initially gave me a kernel panic :D The problem occurred when apparmor-abstraction was updated. I fixed by disabling apparmor before `zypper dup` by `systemctl stop apparmor`. Another guy in this spanish forum: http://www.forosuse.org/forosuse/showthread.php?t=32755 also had the same problem. Again, is it a known bug or should I report it? Regards, Ronan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dear Dominique, Em sex 14 ago 2015, às 16:20:10, Dominique Leuenberger / DimStar escreveu:
The most important changes were: * GParted 0.23 update (mainly interesting for GPT) * Libreoffice was pushed to 5.0.0.5, getting you some fixes * Mesa 10.6.3 (fixes crashes when playing videos in VLC with vdpau) * Firefox 39.0.3 (security fixes over 39.0) * BIND 9.10.2P3 (Security fixes) * CMAKE was bumped to 3.3; for once, it was painless * Linux kernel 4.1.4
To our knowledge, is is now finally again possible to put the Tumbleweed ISOs on a USB Stick and boot from it in UEFI environments. Some users seem still to have issues, but those have a different cause; those users also experience issues after updating an existing TW installation; the cause is not yet known
I tried to install Tumbleweed in UEFI system from the ISO on a USB stick. Now, it seems that I can boot into the installation. However, when the partitions are read, then YaST crash. I managed to install Tumbleweed by upgrading from openSUSE 13.2. But it turns out that if I open disk module of YaST, it also crashes with the same error, which is: Run command: /sbin/yast2 disk & terminate called after throwing an instance of 'storage::SystemCmdException' what(): parted complains: Warning: failed to translate partition name: "/usr/sbin/parted -s '/dev/sda' unit cyl print unit s print" YaST got signal 6 at file /usr/share/YaST2/modules/ProductFeatures.rb:170 /sbin/yast2: line 434: 18463 Abortado $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS The output of parted command in my system is: http://paste.opensuse.org/3908373 Is it a known bug or should I report? P.S.: By the way, the upgrade from 13.2 to Tumbleweed initially gave me a kernel panic The problem occurred when apparmor-abstraction was updated. I fixed by disabling apparmor before `zypper dup` by `systemctl stop apparmor`. Another guy in this spanish forum: http://www.forosuse.org/forosuse/showthread.php?t=32755 also had the same problem. Again, is it a known bug or should I report it? Regards, Ronan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2015-08-14 at 20:33 -0300, Ronan Arraes Jardim Chagas wrote:
Dear Dominique,
Em sex 14 ago 2015, às 16:20:10, Dominique Leuenberger / DimStar escreveu:
The most important changes were: * GParted 0.23 update (mainly interesting for GPT) * Libreoffice was pushed to 5.0.0.5, getting you some fixes * Mesa 10.6.3 (fixes crashes when playing videos in VLC with vdpau) * Firefox 39.0.3 (security fixes over 39.0) * BIND 9.10.2P3 (Security fixes) * CMAKE was bumped to 3.3; for once, it was painless * Linux kernel 4.1.4
To our knowledge, is is now finally again possible to put the Tumbleweed ISOs on a USB Stick and boot from it in UEFI environments. Some users seem still to have issues, but those have a different cause; those users also experience issues after updating an existing TW installation; the cause is not yet known
I tried to install Tumbleweed in UEFI system from the ISO on a USB stick. Now, it seems that I can boot into the installation. However, when the partitions are read, then YaST crash. I managed to install Tumbleweed by upgrading from openSUSE 13.2. But it turns out that if I open disk module of YaST, it also crashes with the same error, which is:
Run command: /sbin/yast2 disk & terminate called after throwing an instance of 'storage::SystemCmdException' what(): parted complains: Warning: failed to translate partition name: "/usr/sbin/parted -s '/dev/sda' unit cyl print unit s print" YaST got signal 6 at file /usr/share/YaST2/modules/ProductFeatures.rb:170 /sbin/yast2: line 434: 18463 Abortado $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
That's an entirely different bug - please report it, if you can't find anything in bugzilla (I'm not aware of any such bug so far)
P.S.: By the way, the upgrade from 13.2 to Tumbleweed initially gave me a kernel panic The problem occurred when apparmor-abstraction was updated. I fixed by disabling apparmor before `zypper dup` by `systemctl stop apparmor`. Another guy in this spanish forum: http://www.forosuse.org/forosuse/showthread.php?t=32755 also had the same problem. Again, is it a known bug or should I report it?
Search in bugzilla for apparmor an if you can't find anything looking
to be the same, report it...
--
Dimstar / Dominique Leuenberger
Op zaterdag 15 augustus 2015 11:25:54 schreef Dimstar / Dominique Leuenberger:
"/usr/sbin/parted -s '/dev/sda' unit cyl print unit s print" YaST got signal 6 at file /usr/share/YaST2/modules/ProductFeatures.rb:170 /sbin/yast2: line 434: 18463 Abortado $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
The same error message, except for a different location, is in bug report https://bugzilla.opensuse.org/show_bug.cgi?id=936788 Maybe the cause is a wrong version of binutils used to build libyui-ncurses- pkg6. I am exploring that route on an armv6l system. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Em sáb 15 ago 2015, às 11:25:54, Dimstar / Dominique Leuenberger escreveu:
Run command: /sbin/yast2 disk & terminate called after throwing an instance of 'storage::SystemCmdException'
what(): parted complains: Warning: failed to translate partition
name: "/usr/sbin/parted -s '/dev/sda' unit cyl print unit s print" YaST got signal 6 at file /usr/share/YaST2/modules/ProductFeatures.rb:170 /sbin/yast2: line 434: 18463 Abortado $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
That's an entirely different bug - please report it, if you can't find anything in bugzilla (I'm not aware of any such bug so far)
<snip>
Search in bugzilla for apparmor an if you can't find anything looking to be the same, report it...
Thanks for the answer Dominique. Both bugs was reported: _ https://bugzilla.opensuse.org/show_bug.cgi?id=941866 _ https://bugzilla.opensuse.org/show_bug.cgi?id=941867 Em sáb 15 ago 2015, às 18:41:32, Freek de Kruijf escreveu:
Op zaterdag 15 augustus 2015 11:25:54 schreef Dimstar / Dominique Leuenberger:
"/usr/sbin/parted -s '/dev/sda' unit cyl print unit s print" YaST got signal 6 at file /usr/share/YaST2/modules/ProductFeatures.rb:170 /sbin/yast2: line 434: 18463 Abortado $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
The same error message, except for a different location, is in bug report https://bugzilla.opensuse.org/show_bug.cgi?id=936788
Maybe the cause is a wrong version of binutils used to build libyui-ncurses- pkg6. I am exploring that route on an armv6l system.
The error message is the same, but I think the cause is completely different. It seems that the bug I reported is being caused by something related to parted due to this warning message: parted complains: Warning: failed to translate partition name I guess it should be something related to GPT. On the other hand, the bug you showed is being caused in sw_single module and it is not related to parted. But I am confused because the error message from YaST is the same :) Regards, Ronan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op zaterdag 15 augustus 2015 14:59:42 schreef Ronan Arraes Jardim Chagas:
I guess it should be something related to GPT. On the other hand, the bug you showed is being caused in sw_single module and it is not related to parted. But I am confused because the error message from YaST is the same :)
More details about the cause can be found at the end of /var/log/YaST2/y2log -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 08/14/2015 04:20 PM, Dominique Leuenberger / DimStar wrote:
Staging:A grew to a small monster that does not want to be tamed... but I'm sure the monster is getting tired soon.
I've incidentally followed that growth ... and I'm wondering if "adding packages until no errors" is the fastest strategy? Staging:A started with ~5-8 packages 25 days ago. As there were some errors, other packages with fixes got added - now we're at 47 packages. Wouldn't it have been easier at some point to move some packages out for a while, thus splitting the problem? Thanks & have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bernahrd, On Sat, 2015-08-15 at 16:59 +0200, Bernhard Voelker wrote:
On 08/14/2015 04:20 PM, Dominique Leuenberger / DimStar wrote:
Staging:A grew to a small monster that does not want to be tamed... but I'm sure the monster is getting tired soon.
I've incidentally followed that growth ... and I'm wondering if "adding packages until no errors" is the fastest strategy?
It is to a certain point - then we generally start splitting stuff up again.
Staging:A started with ~5-8 packages 25 days ago. As there were some errors, other packages with fixes got added - now we're at 47 packages. Wouldn't it have been easier at some point to move some packages out for a while, thus splitting the problem?
If we'd not add the fixes to the same staging directly, the fix would
first have to go through any other staing, be accepted into factory and
the the first staging be completely rebased (stagings are not building
against 'openSUSE:Factory', but contain frozen links to a 'snapshot in
openSUSE:Factory'; so fixes do not auto-propagate).
In some cases it's over-eager devs causing some more delays (like,
superseding a request when a staging is almost ready.. meaning we have
to redo the integration test with the new submission).
:A grew indeed in a strange way, two stagings were merged because one
package contained fixes for both cases.. (A which had glibc and a
couple others and E at the time, which was systemd). Now, systemd has
no longer build fails, but it fails to pass openQA (enrypted disks /
password dialogs with plymouth seem to be a big issue).
Cheers,
--
Dimstar / Dominique Leuenberger
Hi, On Mon, Aug 17, 2015 at 04:06:25PM +0200, Dimstar / Dominique Leuenberger wrote: [ 8< ]
In some cases it's over-eager devs causing some more delays (like, superseding a request when a staging is almost ready.. meaning we have to redo the integration test with the new submission).
Not alone. Coolos automatism for example also pushes sometimes package sources when the maintainers are by intention keep them back. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Mon, 2015-08-17 at 16:39 +0200, Lars Müller wrote:
Hi,
On Mon, Aug 17, 2015 at 04:06:25PM +0200, Dimstar / Dominique Leuenberger wrote: [ 8< ]
In some cases it's over-eager devs causing some more delays (like, superseding a request when a staging is almost ready.. meaning we have to redo the integration test with the new submission).
Not alone. Coolos automatism for example also pushes sometimes package sources when the maintainers are by intention keep them back.
factory-auto CAN be overruled by project/package maintainers by setting
appropriate attributes.
There are way too many devel projects that simply never did and never
do forward submissions... opt-in obviously would not work for those
projects anyway... on the other hand, opt-out for the active projects
works just fine.
you can check GNOME:Factory for an example on how to opt-out (check the
attributes).
Cheers,
--
Dimstar / Dominique Leuenberger
On 08/17/2015 04:06 PM, Dimstar / Dominique Leuenberger wrote:
On Sat, 2015-08-15 at 16:59 +0200, Bernhard Voelker wrote:
On 08/14/2015 04:20 PM, Dominique Leuenberger / DimStar wrote: I've incidentally followed that growth ... and I'm wondering if "adding packages until no errors" is the fastest strategy?
It is to a certain point - then we generally start splitting stuff up again.
Staging:A started with ~5-8 packages 25 days ago. As there were some errors, other packages with fixes got added - now we're at 47 packages. Wouldn't it have been easier at some point to move some packages out for a while, thus splitting the problem?
If we'd not add the fixes to the same staging directly, the fix would first have to go through any other staing, be accepted into factory and the the first staging be completely rebased (stagings are not building against 'openSUSE:Factory', but contain frozen links to a 'snapshot in openSUSE:Factory'; so fixes do not auto-propagate).
I see, thanks. I just thought that it might be easier to move packages out into other staging projects which are "supposedly highly unlikely to be related to current problems", thus keeping the problematic staging project small and concentrated to the origin of the problem and its (and only its) fixes. Maybe the world is not ideal. ;-)
In some cases it's over-eager devs causing some more delays (like, superseding a request when a staging is almost ready.. meaning we have to redo the integration test with the new submission).
BTW: why is it that some of the original requests are regularly superseeded by a new request with the same content by factory-maintainer, e.g. 318007 superseeding 317472? Does this require such double work? Thanks & have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2015-08-17 at 17:11 +0200, Bernhard Voelker wrote:
In some cases it's over-eager devs causing some more delays (like, superseding a request when a staging is almost ready.. meaning we have to redo the integration test with the new submission).
BTW: why is it that some of the original requests are regularly superseeded by a new request with the same content by factory-maintainer, e.g. 318007 superseeding 317472? Does this require such double work?
shortcomin in factory-auto script: it checks if the existing submission
is the same rev as currently available in the repo, if not, it submits.
in your example, the old submission was from rev
c7eaf920ad344e750c6d2ce951a53dde and the new one from rev 263
They don't exactly look the same.. but the issue here is that OBS has
actually two methods to refer to one exact commit... and not every tool
does the same it seems.
Fixes for obs-autosubmit are welcome :) (
https://github.com/openSUSE/obs-autosubmit)
--
Dimstar / Dominique Leuenberger
participants (6)
-
Bernhard Voelker -
Dimstar / Dominique Leuenberger -
Dominique Leuenberger / DimStar
-
Freek de Kruijf -
Lars Müller -
Ronan Arraes Jardim Chagas