[opensuse-factory] Tumbleweed - Review of the Week 2015/38
Dear Tumbleweed users and hackers, This week we were not able to deliver a single snapshot (yet). Sorry for this. The reason is actually rather simple: as RPM was switched to link against lua 5.3 instead of lua 5.1, the 'build' script needed to be updated to know of this difference. For this, the internally used version needed to be different from 132x (as only the first three digits are used). So, Tumbleweed has been 'bumped' to be suse_version 1330 and the build script was happy about this. Sadly, we missed kiwi in the game (and those version bumps can barely go through stagings). Anyway, kiwi has been fixed, it passed staging and has been checked in to openSUSE:Factory - that happened yesterday and we are now awaiting a full build that should hopefully soon go to openQA. If all goes well, you might get a release tomorrow. So, anyway, things that happened and are going to happen soon (based on the future outlook of last week): * Staging A with ncurses 6 is currently green! So you can expect NCurses 6.0 to land shortly (but not before the current snapshot starts to be tested) * Systemd 224: I debugged the issues currently seen in Staging:F. The KDE-related issues are tracked down to systemd currently not providing the pam libraries in a -32bit variant, thus failing to enable systemd integration. As a result, the session is not registering its seat. For GNOME, the same issue happens, PLUS wayland seems not to like to run in the new session. Additionally, plymouth seems to have trouble firing up in GUI mode, but stays in text mode. The last two items need more debugging... the first one 'only' needs somebody doing the fix. * libQt 5.5 got a step closer... still some yast modules missing to make this acceptable. * KDE Application 15.08.0: with the delays caused by the snapshots, we should be able to provide this next week too. * GNOME 3.18.0: RC2 (3.17.92) is submitted to staging and still looks like we're on track. You see, even without having produced snapshots this week, there is progress and you can expect a bunch of changes coming your way in the next few days (fingers crossed). I wish you a great weekend, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks for the update! Any idea about Mesa 11, llvm 3.7? Would like to test openGL 4.1 on radeonSI :D Is there a search engine or a cli command which would enable me to search for those packages and their versions in those "stagings"? I found this, http://download.opensuse.org/repositories/openSUSE:/Factory:/Staging:/ with A to G, but the packages in there make no sense... Mesa 10 in A? Then I found this: https://build.opensuse.org/project/subprojects/openSUSE:Factory:Staging I could find mesa and llvm, but have to click 2 times more for every package to get its version. So is there a faster way? And are A, B ... published in this order, or what is their meaning? This is not explained in https://en.opensuse.org/openSUSE:Factory_development_model I also learned that some packages go to staging and others live in devel projects. I would like to search through those as well - sorry if I am too curious :D cheers, tom Am 18.09.2015 um 15:44 schrieb Dominique Leuenberger / DimStar:
Dear Tumbleweed users and hackers,
This week we were not able to deliver a single snapshot (yet). Sorry for this.
The reason is actually rather simple: as RPM was switched to link against lua 5.3 instead of lua 5.1, the 'build' script needed to be updated to know of this difference. For this, the internally used version needed to be different from 132x (as only the first three digits are used). So, Tumbleweed has been 'bumped' to be suse_version 1330 and the build script was happy about this.
Sadly, we missed kiwi in the game (and those version bumps can barely go through stagings). Anyway, kiwi has been fixed, it passed staging and has been checked in to openSUSE:Factory - that happened yesterday and we are now awaiting a full build that should hopefully soon go to openQA. If all goes well, you might get a release tomorrow.
So, anyway, things that happened and are going to happen soon (based on the future outlook of last week): * Staging A with ncurses 6 is currently green! So you can expect NCurses 6.0 to land shortly (but not before the current snapshot starts to be tested) * Systemd 224: I debugged the issues currently seen in Staging:F. The KDE-related issues are tracked down to systemd currently not providing the pam libraries in a -32bit variant, thus failing to enable systemd integration. As a result, the session is not registering its seat. For GNOME, the same issue happens, PLUS wayland seems not to like to run in the new session. Additionally, plymouth seems to have trouble firing up in GUI mode, but stays in text mode. The last two items need more debugging... the first one 'only' needs somebody doing the fix. * libQt 5.5 got a step closer... still some yast modules missing to make this acceptable. * KDE Application 15.08.0: with the delays caused by the snapshots, we should be able to provide this next week too. * GNOME 3.18.0: RC2 (3.17.92) is submitted to staging and still looks like we're on track.
You see, even without having produced snapshots this week, there is progress and you can expect a bunch of changes coming your way in the next few days (fingers crossed).
I wish you a great weekend, Dominique
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2015-09-18 at 16:31 +0200, Thomas Langkamp wrote:
Thanks for the update!
Any idea about Mesa 11, llvm 3.7? Would like to test openGL 4.1 on radeonSI :D
llvm 3.7 is checked in and if we manage to get a snapshot out, it should be part of the next release Mesa 11 is currently part of Staging:E - keep your fingers crossed and you might get it soon.
Is there a search engine or a cli command which would enable me to search for those packages and their versions in those "stagings"?
osc search Mesa it shows currently one hit in a staging (openSUSE:Factory:Staging:E); but generally it's best to first check if it's in the devel project and generally, if there is a pending submission (osc rq list X11:XOrg Mesa)
I found this, http://download.opensuse.org/repositories/openSUSE:/Factory:/Staging: /
with A to G, but the packages in there make no sense... Mesa 10 in A?
Mesa is 'inherited' from the base project, not really added to the Staging. This is needed as anything going through staging must not break Mesa... so it needs to be rebuilt.
I could find mesa and llvm, but have to click 2 times more for every package to get its version. So is there a faster way?
I usually do "osc ls openSUSE:Factory Mesa" - then I just identify the tarball.. or osc ls -b and check the binaries.
And are A, B ... published in this order, or what is their meaning? This is not explained in https://en.opensuse.org/openSUSE:Factory_development_model
All stagings are independent to each other. They are just there to move forward in parallel... otherwise we might end up being stuck in a FIFO.
I also learned that some packages go to staging and others live in devel projects. I would like to search through those as well - sorry if I am too curious :D
Everything lives in a devel project and should be well tested there. Once it is submitted to openSUSE:Factory, it goes either into a 'full staging' (incl. openQA run) or to an 'ad-interim staging' (just checking it actually builds without modifications / tweaks from the devel prj)... anything that is part of the DVD goes through the full staging process (also ensuring it does not build-break other stuff on the DVD). Hope that clarifies things a bit. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I found this, http://download.opensuse.org/repositories/openSUSE:/Factory:/Staging: /
with A to G, but the packages in there make no sense... Mesa 10 in A?
Mesa is 'inherited' from the base project, not really added to the Staging. This is needed as anything going through staging must not break Mesa... so it needs to be rebuilt.
interesting. but the link above shows Mesa 10.0, this version is ancient... current TW has 10.6.5
I could find mesa and llvm, but have to click 2 times more for every package to get its version. So is there a faster way?
I usually do "osc ls openSUSE:Factory Mesa" - then I just identify the tarball.. or osc ls -b and check the binaries.
there we go :) sadly it shows mesa version 10.6.6 ... but wait, on the website staging E showed 11.0 and you confirmed that... so 10.6.6 is actually in factory but not published? And staging E shows what will come next?
And are A, B ... published in this order, or what is their meaning? This is not explained in https://en.opensuse.org/openSUSE:Factory_development_model
All stagings are independent to each other. They are just there to move forward in parallel... otherwise we might end up being stuck in a FIFO.
so I guess next snapshot is just who finishes openQA first, right?
I also learned that some packages go to staging and others live in devel projects. I would like to search through those as well - sorry if I am too curious :D
Everything lives in a devel project and should be well tested there. Once it is submitted to openSUSE:Factory, it goes either into a 'full staging' (incl. openQA run) or to an 'ad-interim staging' (just checking it actually builds without modifications / tweaks from the devel prj)... anything that is part of the DVD goes through the full staging process (also ensuring it does not build-break other stuff on the DVD).
this https://en.opensuse.org/openSUSE:Factory_development_model#Staging_Projects says that only the "inner ring" goes through staging, so core stuff like X mesa kernel, but as I understand KDE not neccesarily, right?
Hope that clarifies things a bit. Dominique
almost :p XD thx a lot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2015-09-18 at 21:20 +0200, Thomas Langkamp wrote:
Mesa is 'inherited' from the base project, not really added to the Staging. This is needed as anything going through staging must not break Mesa... so it needs to be rebuilt.
interesting. but the link above shows Mesa 10.0, this version is ancient... current TW has 10.6.5
Yeah... well, Stagings are a nasty beast: they are 'rebased' frequently, then 'frozen' to the versions at that very moment. This is needed, as otherwise any change to TW (think: any other staging being accepted) would completely retrigger a rebuild of other stagings, prolonging how long it takes until one is ready. Of course to one end this is a risk that something is being tested against a no longer valid TW setup, but this risk is understood and accepted (and yes, we did have issues coming from such cases, but that's also why TW is being openQA'ed before it's released... we don't just blindly trust that Staging checkins could not break anything new). Additionally, the Staging repositories are not really meant to be used by users: they are very volatile and most of the time in unknown shape :)
there we go :) sadly it shows mesa version 10.6.6 ... but wait, on the website staging E showed 11.0 and you confirmed that... so 10.6.6 is actually in factory but not published? And staging E shows what will come next?
The webui is known to be lying :) especially when it comes to inherited packages and frozen links. In this case: webui just has no clue what it's talking about.
And are A, B ... published in this order, or what is their meaning? This is not explained in https://en.opensuse.org/openSUSE:Factory_development_model
All stagings are independent to each other. They are just there to move forward in parallel... otherwise we might end up being stuck in a FIFO.
so I guess next snapshot is just who finishes openQA first, right?
Generally, yes... any staging that passes all openQA tests and reviews (manual as well as automatic) (and thus turns green) is considered for a checkin.
I also learned that some packages go to staging and others live in devel projects. I would like to search through those as well - sorry if I am too curious :D
Everything lives in a devel project and should be well tested there. Once it is submitted to openSUSE:Factory, it goes either into a 'full staging' (incl. openQA run) or to an 'ad-interim staging' (just checking it actually builds without modifications / tweaks from the devel prj)... anything that is part of the DVD goes through the full staging process (also ensuring it does not build-break other stuff on the DVD).
this https://en.opensuse.org/openSUSE:Factory_development_model#Staging_Pr ojects says that only the "inner ring" goes through staging, so core stuff like X mesa kernel, but as I understand KDE not neccesarily, right?
Anything up to ring2 goes into Stagings. That included everything shipped on the DVD, also KDE and GNOME. GNOME 3.17.92 for example is currently in Staging:G (preparing for a quick release of GNOME 3.18.0 to the TW users) Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 19/09/2015 07:34, Dominique Leuenberger / DimStar ha scritto:
On Fri, 2015-09-18 at 21:20 +0200, Thomas Langkamp wrote:
Mesa is 'inherited' from the base project, not really added to the Staging. This is needed as anything going through staging must not break Mesa... so it needs to be rebuilt.
interesting. but the link above shows Mesa 10.0, this version is ancient... current TW has 10.6.5
Yeah... well, Stagings are a nasty beast: they are 'rebased' frequently, then 'frozen' to the versions at that very moment. This is needed, as otherwise any change to TW (think: any other staging being accepted) would completely retrigger a rebuild of other stagings, prolonging how long it takes until one is ready.
Of course to one end this is a risk that something is being tested against a no longer valid TW setup, but this risk is understood and accepted (and yes, we did have issues coming from such cases, but that's also why TW is being openQA'ed before it's released... we don't just blindly trust that Staging checkins could not break anything new).
Additionally, the Staging repositories are not really meant to be used by users: they are very volatile and most of the time in unknown shape :)
there we go :) sadly it shows mesa version 10.6.6 ... but wait, on the website staging E showed 11.0 and you confirmed that... so 10.6.6 is actually in factory but not published? And staging E shows what will come next?
The webui is known to be lying :) especially when it comes to inherited packages and frozen links. In this case: webui just has no clue what it's talking about.
And are A, B ... published in this order, or what is their meaning? This is not explained in https://en.opensuse.org/openSUSE:Factory_development_model
All stagings are independent to each other. They are just there to move forward in parallel... otherwise we might end up being stuck in a FIFO.
so I guess next snapshot is just who finishes openQA first, right?
Generally, yes... any staging that passes all openQA tests and reviews (manual as well as automatic) (and thus turns green) is considered for a checkin.
I also learned that some packages go to staging and others live in devel projects. I would like to search through those as well - sorry if I am too curious :D
Everything lives in a devel project and should be well tested there. Once it is submitted to openSUSE:Factory, it goes either into a 'full staging' (incl. openQA run) or to an 'ad-interim staging' (just checking it actually builds without modifications / tweaks from the devel prj)... anything that is part of the DVD goes through the full staging process (also ensuring it does not build-break other stuff on the DVD).
this https://en.opensuse.org/openSUSE:Factory_development_model#Staging_Pr ojects says that only the "inner ring" goes through staging, so core stuff like X mesa kernel, but as I understand KDE not neccesarily, right?
Anything up to ring2 goes into Stagings. That included everything shipped on the DVD, also KDE and GNOME. GNOME 3.17.92 for example is currently in Staging:G (preparing for a quick release of GNOME 3.18.0 to the TW users)
Cheers, Dominique
Sorry for the following off-thread and dumb question: I'm using Tumbleweed and I wonder if I need to run 'zypper dup' to update for a next major version or is it enough to just run 'zypper up' to be updated: Many thanks. Regards, -- Marco Calistri opensuse Tumbleweed 64 bit - Kernel 4.1.6-3-desktop Gnome 3.16.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Dominique Leuenberger / DimStar -
Marco Calistri -
Thomas Langkamp