Dear Tumbleweed users, more specifically users of the 32bit intel architecture (i586),
Throughout the last few weeks, I have prepared the entire setup, and it is now time to let 'i586' live its own life.
## What does this mean for users ## =================================== The repositories need to be adjusted. The main repositories are no longer http://download.opensuse.org/tumbleweed/repo/oss and http://download.opensuse.org/tumbleweed/repo/non-oss, but those two are now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss
You should update your repository list accordingly when running an i586 setup (the command 'arch' would tell you)
## i586 will be removed from the main tree ## =============================================
You have until the end of March) to migrate to the new repositories. After April 1st (no joke), i586 packages will no longer be shipped as part of the main repositories (we will keep shipping the -32bit.x86_64 packages for things like steam, wine, …)
## What does this mean for contributors / package maintainers ## ================================================================ Just like for all the other ports, we as a community strive to support the architecture as well as we can. If somebody submits fixes for those architectures, we accept them, assuming they are not causing problems to the main architecture (x86_64). The Staging process will not monitor all i586 builds anymore. If something is not supported on i586 and should not be shipped (or build-attempted), we keep on using the ExcludeArch tags, as we did in the past.
## Is the i586 port tested / usable? ## ======================================== Just like all the other ports, i586 inherits the same sources, so is built from the same tarballs and spec files as the main x86_64 tree. After the build is complete, the port is handed over to openQA in the same way too and tested there. The i586 test progress can be monitored at https://openqa.opensuse.org/group_overview/75
Compared to when i586 was part of the main group I have even extended the test coverage a bit and the GNOME, KDE, and XFCE desktops are now tested on this architecture.
In case there are issues only on i586, not seen on x86_64, this now even allows us to release x86_64 without having to risk i586 (or explicitly having to ignore it), which is a win.
## Call for help - somebody to look after the port ## ===================================================== The port still requires somebody to take responsibility for it. As is visible on openQA, since December 11 this port has been silently rolling along the main port. Most snapshots have been published without much interaction at all. Yet, when something goes wrong, somebody needs to look after it and 'chase the relevant fixes'. Some people have expressed their interest to take on this task, but nobody has fully committed to it (of course there was also the holiday when people shifted their priorities to families, which is perfectly fine)
Please help spread the word so that all i586 users are aware of this change.
Cheers, Dominique
Hi Dominique,
On 03.01.23 10:52, Dominique Leuenberger / DimStar wrote:
Dear Tumbleweed users, more specifically users of the 32bit intel architecture (i586),
Throughout the last few weeks, I have prepared the entire setup, and it is now time to let 'i586' live its own life.
Thanks, I appreciate that (even if I only have one useful machine still 32bit-only).
[...]
## Call for help - somebody to look after the port ##
The port still requires somebody to take responsibility for it. As is visible on openQA, since December 11 this port has been silently rolling along the main port. Most snapshots have been published without much interaction at all. Yet, when something goes wrong, somebody needs to look after it and 'chase the relevant fixes'. Some people have expressed their interest to take on this task, but nobody has fully committed to it (of course there was also the holiday when people shifted their priorities to families, which is perfectly fine)
Would it be possible to send out "build fail notifications" for this port? I'll probably not have time to actively look at the build status and openQA results, but I'm certainly interested in trying to fix problems that arise. So these notifications would be a good way to get people to notice that there is something to do ;-)
Thanks for your efforts,
seife
Hi,
On 03. 01. 23, 10:52, Dominique Leuenberger / DimStar wrote:
## What does this mean for users ##
The repositories need to be adjusted. The main repositories are no longer http://download.opensuse.org/tumbleweed/repo/oss and http://download.opensuse.org/tumbleweed/repo/non-oss, but those two are now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss
Apparently, the non-oss is empty. Perhaps, it's a transient/mirror problem?
thanks,
On Wed, 2023-01-04 at 11:14 +0100, Jiri Slaby wrote:
now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss
Apparently, the non-oss is empty. Perhaps, it's a transient/mirror problem?
Thanks for chhecking and noticing! This was a publisher issue which has just been corrected.
Cheers, Dominique
Hi Dominique,
Am Di., 3. Jan. 2023 um 10:52 Uhr schrieb Dominique Leuenberger / DimStar dimstar@opensuse.org:
Throughout the last few weeks, I have prepared the entire setup, and it is now time to let 'i586' live its own life.
Given that we can test for this case trivially with [ $(arch) = "i586" ] || [ $(arch) = "i686" ] - can we automatically migrate those users to the new locations? IIRC the plan was to add a post install snipped to some package that is always installed, like the product package. This would avoid a 2nd flow of news stories that start with "Tumbleweed is breaking for (some of its) users".
Also a good reminder to put https://en.opensuse.org/openSUSE:OpenSUSE_Distribution_Architectures_Policy into effect for Tumbleweed :)
Thanks, Dirk
On Wed, 2023-01-04 at 15:41 +0100, Dirk Müller wrote:
Hi Dominique,
Am Di., 3. Jan. 2023 um 10:52 Uhr schrieb Dominique Leuenberger / DimStar dimstar@opensuse.org:
Throughout the last few weeks, I have prepared the entire setup, and it is now time to let 'i586' live its own life.
Given that we can test for this case trivially with [ $(arch) = "i586" ] || [ $(arch) = "i686" ] - can we automatically migrate those users to the new locations? IIRC the plan was to add a post install snipped to some package that is always installed, like the product package. This would avoid a 2nd flow of news stories that start with "Tumbleweed is breaking for (some of its) users".
Yes, I have the script ready to be added to the release package - but before mass-moving it'd be nice to have a few regulars move manually and see if there is anything missing (just like the reported, empty non-oss repo)
Cheers, Dominique
Dirk Müller wrote:
Am Di., 3. Jan. 2023 um 10:52 Uhr schrieb Dominique Leuenberger / DimStar dimstar@opensuse.org:
Throughout the last few weeks, I have prepared the entire setup, and it is now time to let 'i586' live its own life.
Given that we can test for this case trivially with [ $(arch) = "i586" ] || [ $(arch) = "i686" ] - can we automatically migrate those users to the new locations? IIRC the plan was to add a post install snipped to some package that is always installed, like the product package. This would avoid a 2nd flow of news stories that start with "Tumbleweed is breaking for (some of its) users".
Weren't there some efforts to make zypp read default repos from files in /usr? Having a package that just ships changed repo files in /usr would be cleaner than than doing it the dirty old way with scriptlets messing around in /etc. As there's some time left until the switch this might be a good opportunity.
cu Ludwig
Hi Ludwig,
Weren't there some efforts to make zypp read default repos from files in /usr?
You'd still have to do some script to delete the corresponding files from /etc/zypp/repos.d that are now in /usr/etc/zypp/repos.d (assuming that exists, which doesn't seem to be the case right now).
Hi Dominique,
Am Dienstag, 3. Januar 2023, 10:52:05 CET schrieb Dominique Leuenberger / DimStar:
## What does this mean for users ##
The repositories need to be adjusted. The main repositories are no longer http://download.opensuse.org/tumbleweed/repo/oss and http://download.opensuse.org/tumbleweed/repo/non-oss, but those two are now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss
You should update your repository list accordingly when running an i586 setup (the command 'arch' would tell you)
Will there be an update channel as well? ...and for the repos like 'geo' it is up to the maintainers if there will be a i586 port I guess?
Thanks Axel
On Wed, 2023-01-04 at 16:19 +0100, Axel Braun wrote:
Hi Dominique,
Am Dienstag, 3. Januar 2023, 10:52:05 CET schrieb Dominique Leuenberger / DimStar:
## What does this mean for users ##
The repositories need to be adjusted. The main repositories are no longer http://download.opensuse.org/tumbleweed/repo/oss and http://download.opensuse.org/tumbleweed/repo/non-oss, but those two are now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss
You should update your repository list accordingly when running an i586 setup (the command 'arch' would tell you)
Will there be an update channel as well?
https://download.opensuse.org/ports/i586/update/tumbleweed/
As usual, it's mostly supposed to be empty - but the setup is ready.
...and for the repos like 'geo' it is up to the maintainers if there will be a i586 port I guess?
Correct; like the other ports, some devel projects add it, others did not (mostly based on user demand and help)
Cheers, Dominique
Dominique Leuenberger / DimStar composed on 2023-01-03 10:52 (UTC+0100):
The repositories need to be adjusted. The main repositories are no longer http://download.opensuse.org/tumbleweed/repo/oss and http://download.opensuse.org/tumbleweed/repo/non-oss, but those two are now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss
I just started my first dup using this reconfiguration on a P4, last upgraded 20220929, using the -d switch. It's downloading 1215 packages, which seems as though it's replacing the entire (KDE3/IceWM-only) distro, with over 500 packages listed as "vendor-change", and less than 400 as upgrades. Is this to-be-expected behavior?
Hi Felix,
Am Mi., 4. Jan. 2023 um 17:52 Uhr schrieb Felix Miata mrmazda@earthlink.net:
I just started my first dup using this reconfiguration on a P4, last upgraded 20220929, using the -d switch. It's downloading 1215 packages, which seems as though it's replacing the entire (KDE3/IceWM-only) distro, with over 500 packages listed as "vendor-change", and less than 400 as upgrades. Is this to-be-expected behavior?
What vendor change? The vendor of the packages is "openSUSE" (and signed by the openSUSE key) in both cases.
I did notice that it isn't using the right %distribution though: Distribution: openSUSE:Factory:LegacyX86
it should be something like "openSUSE Tumbleweed for X86"
Greetings, Dirk
On Wed, 2023-01-04 at 11:52 -0500, Felix Miata wrote:
Dominique Leuenberger / DimStar composed on 2023-01-03 10:52 (UTC+0100):
The repositories need to be adjusted. The main repositories are no longer http://download.opensuse.org/tumbleweed/repo/oss and http://download.opensuse.org/tumbleweed/repo/non-oss, but those two are now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss
I just started my first dup using this reconfiguration on a P4, last upgraded 20220929, using the -d switch. It's downloading 1215 packages, which seems as though it's replacing the entire (KDE3/IceWM-only) distro, with over 500 packages listed as "vendor-change", and less than 400 as upgrades. Is this to-be-expected behavior?
Thanks Felix,
it being a 'large update' sounds about normal, as all packages are rebuilt in a different project in OBS.
Them being considered a changed vendor though is definitively not correct and will need some investigation (and possibly a full rebuild of the pkg tree).
Cheers, Dominique
Dominique Leuenberger / DimStar composed on 2023-01-04 18:08 (UTC+0100):
On Wed, 2023-01-04 at 11:52 -0500, Felix Miata wrote:
I just started my first dup using this reconfiguration on a P4, last upgraded 20220929, using the -d switch. It's downloading 1215 packages, which seems as though it's replacing the entire (KDE3/IceWM-only) distro, with over 500 packages listed as "vendor-change", and less than 400 as upgrades. Is this to-be-expected behavior?
it being a 'large update' sounds about normal, as all packages are rebuilt in a different project in OBS.
Them being considered a changed vendor though is definitively not correct and will need some investigation (and possibly a full rebuild of the pkg tree).
Still seems weird. I ran zypper up to cause the above. Now with zypper dup, there are:
202 to upgrade 343 to downgrade 199 new 62 to reinstall 9 to remove 568 to change vendor 2 to change arch
# zypper lr ... # | Enabled | GPG Check | URI --+---------+-----------+----------------------------------------------------------------------------- 1 | Yes | (r ) Yes | http://ftp5.gwdg.de/pub/opensuse/repositories/KDE:/KDE3/openSUSE_Tumbleweed/ 2 | Yes | (r ) Yes | http://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss 3 | Yes | (r ) Yes | http://download.opensuse.org/ports/i586/tumbleweed/repo/oss 4 | Yes | (r ) Yes | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Tumbleweed/Essentials 5 | Yes | (r ) Yes | http://download.opensuse.org/ports/i586/update/tumbleweed/
Felix Miata composed on 2023-01-04 12:50 (UTC-0500):
Dominique Leuenberger / DimStar composed on 2023-01-04 18:08 (UTC+0100):
On Wed, 2023-01-04 at 11:52 -0500, Felix Miata wrote:
I just started my first dup using this reconfiguration on a P4, last upgraded 20220929, using the -d switch. It's downloading 1215 packages, which seems as though it's replacing the entire (KDE3/IceWM-only) distro, with over 500 packages listed as "vendor-change", and less than 400 as upgrades. Is this to-be-expected behavior?
it being a 'large update' sounds about normal, as all packages are rebuilt in a different project in OBS.
Them being considered a changed vendor though is definitively not correct and will need some investigation (and possibly a full rebuild of the pkg tree).
Still seems weird. I ran zypper up to cause the above. Now with zypper dup, there are:
202 to upgrade 343 to downgrade 199 new 62 to reinstall 9 to remove 568 to change vendor 2 to change arch
# zypper lr ... # | Enabled | GPG Check | URI
--+---------+-----------+-----------------------------------------------------------------------------
1 | Yes | (r ) Yes | http://ftp5.gwdg.de/pub/opensuse/repositories/KDE:/KDE3/openSUSE_Tumbleweed/ 2 | Yes | (r ) Yes | http://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss 3 | Yes | (r ) Yes | http://download.opensuse.org/ports/i586/tumbleweed/repo/oss 4 | Yes | (r ) Yes | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Tumbleweed/Essentials 5 | Yes | (r ) Yes | http://download.opensuse.org/ports/i586/update/tumbleweed/
On another P4-32, last upgraded to 20221222, using above 5 repo URIs only:
# zypper -v dup -d --allow-vendor-change ... The following 6 patterns are going to change vendor: base 20200505-38.1 openSUSE -> obs://build.opensuse.org/openSUSE:Factory enhanced_base 20200505-38.1 openSUSE -> obs://build.opensuse.org/openSUSE:Factory fonts 20170319-8.2 -> 20170319-8.1 openSUSE -> obs://build.opensuse.org/openSUSE:Factory minimal_base 20200505-38.1 openSUSE -> obs://build.opensuse.org/openSUSE:Factory sw_management 20200505-38.1 openSUSE -> obs://build.opensuse.org/openSUSE:Factory x11 20200505-38.1 openSUSE -> obs://build.opensuse.org/openSUSE:Factory
The following NEW package is going to be installed: yast2-control-center-qt3 2.17.3-16.40
The following 3 packages are going to be REMOVED: pam_unix 1.5.2-10.1 xf86-input-keyboard 1.9.0-2.9 yast2-control-center-qt 4.5.0-1.4
123 packages to upgrade, 448 to downgrade, 1 new, 515 to reinstall, 3 to remove, 748 to change vendor, 1 to change arch. Overall download size: 169.7 MiB. Already cached: 372.9 MiB. Download only. Continue? [y/n/v/...? shows all options] (y):
Dominique Leuenberger / DimStar composed on 2023-01-04 18:08 (UTC+0100):
On Wed, 2023-01-04 at 11:52 -0500, Felix Miata wrote:
I just started my first dup using this reconfiguration on a P4, last upgraded 20220929, using the -d switch. It's downloading 1215 packages, which seems as though it's replacing the entire (KDE3/IceWM-only) distro, with over 500 packages listed as "vendor-change", and less than 400 as upgrades. Is this to-be-expected behavior?
it being a 'large update' sounds about normal, as all packages are rebuilt in a different project in OBS.
Them being considered a changed vendor though is definitively not correct and will need some investigation (and possibly a full rebuild of the pkg tree).
https://susepaste.org/55790989 has a 1294 line selective directory list of my i586 oss LAN cache containing only packages present in more than one version. I see in many cases a newer version is attached to an older date, so it's presented here in case it might help in investigating.
Most recent (4th 32bit) host (gx260): # zypper -v dup -d --allow-vendor-change ... The following 5 NEW packages are going to be installed: libSPIRV-Tools-2022_4_sdk236 2022.4+sdk236-1.1 libde265-0 1.0.8-1.45 libopencv407 4.7.0-1.1 librtmp1 2.4.20151223.fa8646d-1.96 yast2-control-center-qt3 2.17.3-16.40
The following 5 packages are going to be REMOVED: libSPIRV-Tools-2022_4 2022.4-1.1 libopencv406 4.6.0-2.3 pam_unix 1.5.2-10.1 xf86-input-keyboard 1.9.0-2.9 yast2-control-center-qt 4.5.0-1.4
204 packages to upgrade, 609 to downgrade, 5 new, 564 to reinstall, 5 to remove, 975 to change vendor, 1 to change arch. Overall download size: 51.2 MiB. Already cached: 585.9 MiB. Download only. Continue? [y/n/v/...? shows all options] (y): n
Am Dienstag, 3. Januar 2023, 10:52:05 CET schrieb Dominique Leuenberger / DimStar:
## Call for help - somebody to look after the port ##
The port still requires somebody to take responsibility for it. As is visible on openQA, since December 11 this port has been silently rolling along the main port. Most snapshots have been published without much interaction at all. Yet, when something goes wrong, somebody needs to look after it and 'chase the relevant fixes'. Some people have expressed their interest to take on this task, but nobody has fully committed to it (of course there was also the holiday when people shifted their priorities to families, which is perfectly fine)
I had a look at openQA for i586 the last days - always the same 4 failed tests, which relate to three bugs: https://bugzilla.opensuse.org/show_bug.cgi?id=1205363 https://bugzilla.opensuse.org/show_bug.cgi?id=1206322 And a bit older: https://bugzilla.opensuse.org/show_bug.cgi?id=1183454 - maybe we smoke the test for Pentium III?
Cheers Axel
Am 03.01.23 um 10:52 schrieb Dominique Leuenberger / DimStar:
## What does this mean for users ##
The repositories need to be adjusted. The main repositories are no longer http://download.opensuse.org/tumbleweed/repo/oss and http://download.opensuse.org/tumbleweed/repo/non-oss, but those two are now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss
You should update your repository list accordingly when running an i586 setup (the command 'arch' would tell you)
There seems to be a problem with the update of the new repo:
bda24bb85b12:/ #zypper lr newi586 Alias : newi586 Name : newi586 URI : https://download.opensuse.org/ports/i586/tumbleweed/repo/oss Enabled : Yes GPG Check : (r ) Yes Priority : 99 (default priority) Autorefresh : Off Keep Packages : Off Type : rpm-md GPG Key URI : Path Prefix : Parent Service : Keywords : [5] gpg-pubkey-29b700a4-62b07e22.asc?fpr=AD485664E901B867051AB15F35A2F86E29B700A4 gpg-pubkey-39db7c82-5f68629b.asc?fpr=FEAB502539D846DB2C0961CA70AF9E8139DB7C82 gpg-pubkey-3dbdc284-49144c3f.asc?fpr=22C07BA534178CD02EFE22AAB88B2FD43DBDC284 gpg-pubkey-3dbdc284-53674dd4.asc?fpr=22C07BA534178CD02EFE22AAB88B2FD43DBDC284 pool Repo Info Path : /etc/zypp/repos.d/newi586.repo MD Cache Path : /var/cache/zypp/raw/newi586 bda24bb85b12:/ #zypper info --requires libQt6Sensors6 Loading repository data... Reading installed packages...
Information for package libQt6Sensors6: --------------------------------------- Repository : newi586 Name : libQt6Sensors6 Version : 6.4.1-1.2 Arch : i586 Vendor : openSUSE Installed Size : 349.2 KiB Installed : No Status : not installed Source package : qt6-sensors-6.4.1-1.2.src Upstream URL : https://www.qt.io Summary : Qt 6 Sensors library Description : The Qt 6 Sensors library. Requires : [10] libstdc++.so.6 libstdc++.so.6(GLIBCXX_3.4) libstdc++.so.6(CXXABI_1.3) libc.so.6(GLIBC_2.4) libstdc++.so.6(CXXABI_1.3.9) libQt6Core.so.6 libQt6Core.so.6(Qt_6) libQt6Core.so.6(Qt_6.4) libQt6Core.so.6(Qt_6.4.1_PRIVATE_API) /sbin/ldconfig
Whereas the old repo has the update:
603d9ff1b579:/ #zypper lr openSUSE-Tumbleweed-Oss Alias : repo-oss Name : openSUSE-Tumbleweed-Oss URI : http://download.opensuse.org/tumbleweed/repo/oss/ Enabled : Yes GPG Check : (r ) Yes Priority : 99 (default priority) Autorefresh : On Keep Packages : Off Type : rpm-md GPG Key URI : Path Prefix : Parent Service : Keywords : [4] gpg-pubkey-29b700a4-62b07e22.asc?fpr=AD485664E901B867051AB15F35A2F86E29B700A4 gpg-pubkey-39db7c82-5f68629b.asc?fpr=FEAB502539D846DB2C0961CA70AF9E8139DB7C82 gpg-pubkey-3dbdc284-53674dd4.asc?fpr=22C07BA534178CD02EFE22AAB88B2FD43DBDC284 pool Repo Info Path : /etc/zypp/repos.d/repo-oss.repo MD Cache Path : /var/cache/zypp/raw/repo-oss 603d9ff1b579:/ #zypper info --requires libQt6Sensors6 Loading repository data... Reading installed packages...
Information for package libQt6Sensors6: --------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : libQt6Sensors6 Version : 6.4.2-1.1 Arch : i586 Vendor : openSUSE Installed Size : 349.2 KiB Installed : No Status : not installed Source package : qt6-sensors-6.4.2-1.1.src Upstream URL : https://www.qt.io Summary : Qt 6 Sensors library Description : The Qt 6 Sensors library. Requires : [10] libstdc++.so.6 libstdc++.so.6(GLIBCXX_3.4) libstdc++.so.6(CXXABI_1.3) libc.so.6(GLIBC_2.4) libstdc++.so.6(CXXABI_1.3.9) libQt6Core.so.6 libQt6Core.so.6(Qt_6) libQt6Core.so.6(Qt_6.4) libQt6Core.so.6(Qt_6.4.2_PRIVATE_API) /sbin/ldconfig
OBS projects having the snapshots in their path instead of openSUSE:Factory/standard seem to suffer from it too:
https://build.opensuse.org/package/show/KDE:Qt:PyQt/python-PyQt6 i586 -- unresolvable: nothing provides libQt6Core.so.6(Qt_6.4.1_PRIVATE_API) needed by libQt6Sensors6, nothing provides libQt6Core.so.6(Qt_6.4.1_PRIVATE_API) needed by libQt6TextToSpeech6
- Ben
On Mon, 2023-01-30 at 20:09 +0100, Ben Greiner wrote:
There seems to be a problem with the update of the new repo: bda24bb85b12:/ # zypper lr newi586 Alias : newi586 Name : newi586 URI : https://download.opensuse.org/ports/i586/tumbleweed/repo/oss%C2%A0 Enabled : Yes GPG Check : (r ) Yes Priority : 99 (default priority) Autorefresh : Off Keep Packages : Off Type : rpm-md GPG Key URI : Path Prefix : Parent Service : Keywords : [5] gpg-pubkey-29b700a4- 62b07e22.asc?fpr=AD485664E901B867051AB15F35A2F86E29B700A4 gpg-pubkey-39db7c82- 5f68629b.asc?fpr=FEAB502539D846DB2C0961CA70AF9E8139DB7C82 gpg-pubkey-3dbdc284- 49144c3f.asc?fpr=22C07BA534178CD02EFE22AAB88B2FD43DBDC284 gpg-pubkey-3dbdc284- 53674dd4.asc?fpr=22C07BA534178CD02EFE22AAB88B2FD43DBDC284 pool Repo Info Path : /etc/zypp/repos.d/newi586.repo MD Cache Path : /var/cache/zypp/raw/newi586 bda24bb85b12:/ # zypper info --requires libQt6Sensors6 Loading repository data... Reading installed packages... Information for package libQt6Sensors6: --------------------------------------- Repository : newi586 Name : libQt6Sensors6 Version : 6.4.1-1.2
Should be ok now with snapshot 0130. The issue is quite simple: qt6-sensors (and some others) failed to build and needed a kick. As nobody looks at the port, nobody requested that kick to happen.
I took your mail as 'that kick' :)
Cheers, Dominique
Dominique Leuenberger / DimStar composed on 2023-01-03 10:52 (UTC+0100):
The repositories need to be adjusted. The main repositories are no longer http://download.opensuse.org/tumbleweed/repo/oss and http://download.opensuse.org/tumbleweed/repo/non-oss, but those two are now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss
You should update your repository list accordingly when running an i586 setup (the command 'arch' would tell you)
## i586 will be removed from the main tree ##
You have until the end of March) to migrate to the new repositories.
It appears any who have made the change already did it prematurely. e.g.: http://download.opensuse.org/ports/i586/tumbleweed/repo/oss/i586/openSUSE-re... 2023-02-08 http://download.opensuse.org/ports/i586/tumbleweed/repo/oss/i586/zypper-1.14... 2023-01-07 http://download.opensuse.org/ports/i586/tumbleweed/repo/oss/i586/util-linux-... 2023-01-27
http://download.opensuse.org/tumbleweed/repo/oss/i586/openSUSE-release-20230... 2023-02-26 http://download.opensuse.org/tumbleweed/repo/oss/i586/util-linux-2.38.1-7.1.... 2023-02-16 http://download.opensuse.org/tumbleweed/repo/oss/i586/zypper-1.14.59-1.3.i58... 2023-02-18
Is there any testing I could do to help get building in the new repos unstuck from 20230208?
Felix Miata composed on 2023-02-27 01:34 (UTC-0500):
Dominique Leuenberger / DimStar composed on 2023-01-03 10:52 (UTC+0100):
The repositories need to be adjusted. The main repositories are no longer http://download.opensuse.org/tumbleweed/repo/oss and http://download.opensuse.org/tumbleweed/repo/non-oss, but those two are now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss
You should update your repository list accordingly when running an i586 setup (the command 'arch' would tell you)
## i586 will be removed from the main tree ##
You have until the end of March) to migrate to the new repositories.
It appears any who have made the change already did it prematurely. e.g.: http://download.opensuse.org/ports/i586/tumbleweed/repo/oss/i586/openSUSE-re... 2023-02-08 http://download.opensuse.org/ports/i586/tumbleweed/repo/oss/i586/zypper-1.14... 2023-01-07 http://download.opensuse.org/ports/i586/tumbleweed/repo/oss/i586/util-linux-... 2023-01-27
http://download.opensuse.org/tumbleweed/repo/oss/i586/openSUSE-release-20230... 2023-02-26 http://download.opensuse.org/tumbleweed/repo/oss/i586/util-linux-2.38.1-7.1.... 2023-02-16 http://download.opensuse.org/tumbleweed/repo/oss/i586/zypper-1.14.59-1.3.i58... 2023-02-18
Is there any testing I could do to help get building in the new repos unstuck from 20230208?
By changing 20230208 back from ports: # zypper dup -d Loading repository data... Reading installed packages... ... The following package is going to be REMOVED: libSPIRV-Tools-2022_4_sdk236
499 packages to upgrade, 247 to downgrade, 16 new, 274 to reinstall, 1 to remove. Overall download size: 414.8 MiB. Already cached: 0 B. Download only. Continue? [y/n/v/...? shows all options] (y):
On Mon, 2023-02-27 at 02:12 -0500, Felix Miata wrote:
It appears any who have made the change already did it prematurely. e.g.: http://download.opensuse.org/ports/i586/tumbleweed/repo/oss/i586/openSUSE-re... 2023-02-08 http://download.opensuse.org/ports/i586/tumbleweed/repo/oss/i586/zypper-1.14... 2023-01-07 http://download.opensuse.org/ports/i586/tumbleweed/repo/oss/i586/util-linux-... 2023-01-27
No, users that did do the change are actually protected from openQA failures happening on i586 - users that did not change are no longer protected on i586
http://download.opensuse.org/tumbleweed/repo/oss/i586/openSUSE-release-20230... 2023-02-26 http://download.opensuse.org/tumbleweed/repo/oss/i586/util-linux-2.38.1-7.1.... 2023-02-16 http://download.opensuse.org/tumbleweed/repo/oss/i586/zypper-1.14.59-1.3.i58... 2023-02-18
Is there any testing I could do to help get building in the new repos unstuck from 20230208?
https://openqa.opensuse.org/group_overview/75
which brings you to https://bugzilla.opensuse.org/show_bug.cgi?id=1208188 as the reason for the snapshots not being published (the crash will happen on the non- port repo too - but there we don't test i586 anymore already, which is why it keeps on being published)
By changing 20230208 back from ports: # zypper dup -d Loading repository data... Reading installed packages... ... The following package is going to be REMOVED: libSPIRV-Tools-2022_4_sdk236
499 packages to upgrade, 247 to downgrade, 16 new, 274 to reinstall, 1 to remove. Overall download size: 414.8 MiB. Already cached: 0 B. Download only. Continue? [y/n/v/...? shows all options] (y):
Hope you don't run plasma - or you'll regret it.
-
Axel Braun -
Ben Greiner -
Dirk Müller -
Dominique Leuenberger -
Dominique Leuenberger / DimStar
-
Felix Miata -
Jiri Slaby -
Ludwig Nussel -
Stefan Seyfried