[opensuse-factory] Tumbleweed - Review of the week (2015/22)
Dear Tumbleweed users and hackers, The last week has been an interesting one: we can produly talk of Tumbleweed to be rolling smooth this week: there has been one release published per day (since 0521 so far up to 0528). This is the longest streak we had, as far as I remember. Yet, I have some trouble to find 'exciting' changes in those snapshots. They are all minor version updates, which on their own are certainly important for some users. But 'buzzing' about them is difficult. Nevertheless, let me try to give it a try, and see what we got: * Linux kernel 4.0.4: bugfix release * Timezone 2015d (mostly interesting for Egypt) * On new installs, the firewall service will be auto-enabled * Apache2: access_compat now built as shared and disabled by default. Outlook for the coming days: * hplip: Disabled build for parallel port because parallel port support was disabled by default by upstream HPLIP at least since 2011 and is deprecated by upstream HPLIP since 2013. This will be part of 0529+ * The KDE Team submitted Plasma 5.3.1 bugfixes, which will be part of 0529+ snapshots (checked in this morning). * GCC 5 is making progress: For packages up to ring2 (full DVD), we are down to 10 build failures. (gsl, java (x2) kbuild, ksh, libkolabxml, llvm, powerdevil5, python-cffi & qemu) * We have kde3 packages failing to build for 3 weeks without any reaction. If nobody steps up to maintain this, I will file delete requests (notice mails went to the maintainers already). Special things to note: * Lately we see an increased number of build jobs failing with kernel crashes on the XEN hosts. The reason for this is not yet known. -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org>
* Dimstar / Dominique Leuenberger <dimstar@opensuse.org> [05-29-15 08:59]:
Dear Tumbleweed users and hackers,
The last week has been an interesting one: we can produly talk of Tumbleweed to be rolling smooth this week: there has been one release published per day (since 0521 so far up to 0528). This is the longest streak we had, as far as I remember.
Worthy of mention, good job. [...]
Special things to note: * Lately we see an increased number of build jobs failing with kernel crashes on the XEN hosts. The reason for this is not yet known.
These posts are interesting and informative. Thanks much for providing them. Looking forward .... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op vrijdag 29 mei 2015 14:53:44 schreef Dimstar / Dominique Leuenberger:
Dear Tumbleweed users and hackers,
The last week has been an interesting one: we can produly talk of Tumbleweed to be rolling smooth this week: there has been one release published per day (since 0521 so far up to 0528). This is the longest streak we had, as far as I remember.
Yet, I have some trouble to find 'exciting' changes in those snapshots. They are all minor version updates, which on their own are certainly important for some users. But 'buzzing' about them is difficult.
Nevertheless, let me try to give it a try, and see what we got: * Linux kernel 4.0.4: bugfix release * Timezone 2015d (mostly interesting for Egypt) * On new installs, the firewall service will be auto-enabled * Apache2: access_compat now built as shared and disabled by default.
Outlook for the coming days: * hplip: Disabled build for parallel port because parallel port support was disabled by default by upstream HPLIP at least since 2011 and is deprecated by upstream HPLIP since 2013. This will be part of 0529+ * The KDE Team submitted Plasma 5.3.1 bugfixes, which will be part of 0529+ snapshots (checked in this morning). * GCC 5 is making progress: For packages up to ring2 (full DVD), we are down to 10 build failures. (gsl, java (x2) kbuild, ksh, libkolabxml, llvm, powerdevil5, python-cffi & qemu) * We have kde3 packages failing to build for 3 weeks without any reaction. If nobody steps up to maintain this, I will file delete requests (notice mails went to the maintainers already).
Special things to note: * Lately we see an increased number of build jobs failing with kernel crashes on the XEN hosts. The reason for this is not yet known.
Thanks for posting these updates. -- Gertjan Lettink, a.k.a. Knurpht Official openSUSE Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 29 May 2015 14:53:44 +0200 Dimstar / Dominique Leuenberger wrote:
* We have kde3 packages failing to build for 3 weeks without any reaction. If nobody steps up to maintain this, I will file delete requests (notice mails went to the maintainers already).
We have two packages failing to build: "kde3-amarok" and "kdebindings3" from KDE:KDE3. I will try to fix the "kde3-amarok" package. -- WBR Kyrill
Dimstar / Dominique Leuenberger composed on 2015-05-29 14:53 (UTC+0200):
* We have kde3 packages failing to build for 3 weeks without any reaction. If nobody steps up to maintain this, I will file delete requests (notice mails went to the maintainers already).
Though I have KDE3 as only DE on several TW systems, they are used mostly only for testing, and infrequently for fresh installations. Thus, non-building, non-essential packages wouldn't get noticed here, leaving already installed packages untouched at zypper dup times, or would it? Do non-building packages result in zypper wanting to remove the installed older packages? A lot of zypper -v dup messaging asking confirmation scrolls beyond the start of the vtty screen buffer. Typically what's accessible stops among the lib* items to be upgraded. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2015-05-29 at 18:38 -0400, Felix Miata wrote:
Dimstar / Dominique Leuenberger composed on 2015-05-29 14:53 (UTC+0200):
* We have kde3 packages failing to build for 3 weeks without any
reaction. If nobody steps up to maintain this, I will file delete requests (notice mails went to the maintainers already).
Though I have KDE3 as only DE on several TW systems, they are used mostly only for testing, and infrequently for fresh installations. Thus, non-building, non-essential packages wouldn't get noticed here, leaving already installed packages untouched at zypper dup times, or would it? Do non-building packages result in zypper wanting to remove the installed older packages? A lot of zypper -v dup messaging asking confirmation scrolls beyond the start of the vtty screen buffer. Typically what's accessible stops among the lib* items to be upgraded.
As long as the deps of the package are in place (mainly lib) it will remain installed, probably without issues. This can change any day. Also, if deps are missing, a user performing updates likely sees less issue than a user trying to newly install the package: the updater has the deps already installed - the new user simply can't find them. A package that does not build in the distribution is per definition to be considered unmaintained, if nobody steps up and attempts to fix it in a reasonable time - or at least can give reason why this is breaking at the moment, with an outlook to get a fix. Hence, the statement stays: if nobody steps up to maintain those KDE3 packages, they are being kicked out of the repositories (and anything depending on them) Cheers, Dominique -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org>
29/05/2015 Dimstar / Dominique Leuenberger :
* GCC 5 is making progress: For packages up to ring2 (full DVD), we are down to 10 build failures. (gsl, java (x2) kbuild, ksh, libkolabxml, llvm, powerdevil5, python-cffi & qemu)
About python-cffi, I have updated it and added a patch for gcc5 (SR 309237). -- Benoît
On Fri, May 29, 2015 at 02:53:44PM +0200, Dimstar / Dominique Leuenberger wrote:
* We have kde3 packages failing to build for 3 weeks without any reaction. If nobody steps up to maintain this, I will file delete requests (notice mails went to the maintainers already).
Please keep KDE3 as an option. I'll help to fix the build failures, there are only a handful of them and mostly trivial. It would be sad to drop a whole DE just because of that. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2015-06-02 at 14:08 +0200, David Sterba wrote:
On Fri, May 29, 2015 at 02:53:44PM +0200, Dimstar / Dominique Leuenberger wrote:
* We have kde3 packages failing to build for 3 weeks without any
reaction. If nobody steps up to maintain this, I will file delete requests (notice mails went to the maintainers already).
Please keep KDE3 as an option. I'll help to fix the build failures, there are only a handful of them and mostly trivial. It would be sad to drop a whole DE just because of that.
David, As long as people take care of the failures in a reasonable time, I'm fine with keeping it around... if stuff is not maintained, it's thrown out.. if it fails for several weeks, when not even mails to the maintainers help, I dare to consider it unmaintained. Hence: if somebody submits fixes to keep it, fine - then we see some need to keep it - any other case means 'bye bye'. What timeframe do you consider realistic to submit fixes for those packages? -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org>
On Tue, Jun 02, 2015 at 02:11:22PM +0200, Dimstar / Dominique Leuenberger wrote:
Please keep KDE3 as an option. I'll help to fix the build failures, there are only a handful of them and mostly trivial. It would be sad to drop a whole DE just because of that.
As long as people take care of the failures in a reasonable time, I'm fine with keeping it around... if stuff is not maintained, it's thrown out.. if it fails for several weeks, when not even mails to the maintainers help, I dare to consider it unmaintained.
I understand that. The KDE3 codebase is frozen so I did not see the need to be formally involved in maintaining it for openSUSE. The 13.2 build status is all-green, I've seen failures due to changes in non-kde3 tools. My request for maintainer rights has been just approved.
Hence: if somebody submits fixes to keep it, fine - then we see some need to keep it - any other case means 'bye bye'.
What timeframe do you consider realistic to submit fixes for those packages?
A week should be enough. Thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Benoît Monin -
David Sterba -
Dimstar / Dominique Leuenberger -
Felix Miata -
Knurpht - Gertjan Lettink -
Kyrill Detinov -
Patrick Shanahan