TW builds are not triggered with the latest snapshots
Currently TW builds are not triggered with the latest snapshots. I noticed this in my home repo, as well as on Packman and locally with "osc build". Examples: The latest build for vmware-host-modules is for kernel 6.1.7, although the latest snapshot brings kernel 6.1.8. Also the local build is done with kernel 6.1.7 and not 6.1.8 (packages come from openSUSE:Tumbleweed:OldKey). Packman's vlc is still linked against libBasicUsageEnvironment1, although libBasicUsageEnvironment2 is already available. Again, tested locally with "osc build": A "BuildRequires: libBasicUsageEnvironment2" is aborted with the message "unresolvable: nothing provides libBasicUsageEnvironment2". A "BuildRequires: libBasicUsageEnvironment1" on the other hand works without problems. Regards
On 1/27/23 00:53, munix9 wrote:
Currently TW builds are not triggered with the latest snapshots. I noticed this in my home repo, as well as on Packman and locally with "osc build".
Examples: The latest build for vmware-host-modules is for kernel 6.1.7, although the latest snapshot brings kernel 6.1.8. Also the local build is done with kernel 6.1.7 and not 6.1.8 (packages come from openSUSE:Tumbleweed:OldKey).
Packman's vlc is still linked against libBasicUsageEnvironment1, although libBasicUsageEnvironment2 is already available. Again, tested locally with "osc build": A "BuildRequires: libBasicUsageEnvironment2" is aborted with the message "unresolvable: nothing provides libBasicUsageEnvironment2". A "BuildRequires: libBasicUsageEnvironment1" on the other hand works without problems.
Strange. The builds of the kernel modules for VirtualBox have been matching the kernel. Does "BuildRequires: libBasicUsageEnvironment" work in both cases for Packman? Larry
Am 27.01.23 um 17:35 schrieb Larry Finger:
On 1/27/23 00:53, munix9 wrote:
Currently TW builds are not triggered with the latest snapshots. I noticed this in my home repo, as well as on Packman and locally with "osc build".
Examples: The latest build for vmware-host-modules is for kernel 6.1.7, although the latest snapshot brings kernel 6.1.8. Also the local build is done with kernel 6.1.7 and not 6.1.8 (packages come from openSUSE:Tumbleweed:OldKey).
Packman's vlc is still linked against libBasicUsageEnvironment1, although libBasicUsageEnvironment2 is already available. Again, tested locally with "osc build": A "BuildRequires: libBasicUsageEnvironment2" is aborted with the message "unresolvable: nothing provides libBasicUsageEnvironment2". A "BuildRequires: libBasicUsageEnvironment1" on the other hand works without problems.
Strange. The builds of the kernel modules for VirtualBox have been matching the kernel.
Yes, this may be true for packages on the main repo, but on (my) home repo (and Packman) something is not working as usual right now. Also one kernel module on Packman is compiled with the old kernel version, namely the 6.1.7 - the 6.1.8 is missing here too: https://pmbs.links2linux.de/package/live_build_log/Essentials/r8168/openSUSE... So somehow updated packages don't seem to have arrived everywhere - maybe it's related to the key change; can only guess.
Does "BuildRequires: libBasicUsageEnvironment" work in both cases for Packman?
The "libBasicUsageEnvironment" is just a basic example that something is currently wrong. libBasicUsageEnvironment1 has been officially replaced by libBasicUsageEnvironment2, but in local builds and on Packman you still get libBasicUsageEnvironment1. see https://pmbs.links2linux.de/public/build/Essentials/openSUSE_Tumbleweed/x86_... (search for libBasicUsageEnvironment)
Larry
On 27/01/2023 17:58, munix9 wrote:
Am 27.01.23 um 17:35 schrieb Larry Finger:
On 1/27/23 00:53, munix9 wrote:
Currently TW builds are not triggered with the latest snapshots. I noticed this in my home repo, as well as on Packman and locally with "osc build".
Examples: The latest build for vmware-host-modules is for kernel 6.1.7, although the latest snapshot brings kernel 6.1.8. Also the local build is done with kernel 6.1.7 and not 6.1.8 (packages come from openSUSE:Tumbleweed:OldKey).
Packman's vlc is still linked against libBasicUsageEnvironment1, although libBasicUsageEnvironment2 is already available. Again, tested locally with "osc build": A "BuildRequires: libBasicUsageEnvironment2" is aborted with the message "unresolvable: nothing provides libBasicUsageEnvironment2". A "BuildRequires: libBasicUsageEnvironment1" on the other hand works without problems.
Strange. The builds of the kernel modules for VirtualBox have been matching the kernel.
Yes, this may be true for packages on the main repo, but on (my) home repo (and Packman) something is not working as usual right now. Also one kernel module on Packman is compiled with the old kernel version, namely the 6.1.7 - the 6.1.8 is missing here too: https://pmbs.links2linux.de/package/live_build_log/Essentials/r8168/openSUSE...
So somehow updated packages don't seem to have arrived everywhere - maybe it's related to the key change; can only guess.
Does "BuildRequires: libBasicUsageEnvironment" work in both cases for Packman?
The "libBasicUsageEnvironment" is just a basic example that something is currently wrong.
libBasicUsageEnvironment1 has been officially replaced by libBasicUsageEnvironment2, but in local builds and on Packman you still get libBasicUsageEnvironment1. see https://pmbs.links2linux.de/public/build/Essentials/openSUSE_Tumbleweed/x86_... (search for libBasicUsageEnvironment)
I have the same problem with a project in my home. A kernel module does not get built with kernel 6.1.8 but only with 6.1.7. When I try to build it locally it says "The build root needs packages from project 'openSUSE:Tumbleweed:OldKey'." so the new key might indeed be the problem. -- On a long enough timeline the survival rate for everyone drops to zero...
On 28.01.2023 08:17, Andreas Prittwitz wrote:
I have the same problem with a project in my home. A kernel module does not get built with kernel 6.1.8 but only with 6.1.7. When I try to build it locally it says
"The build root needs packages from project 'openSUSE:Tumbleweed:OldKey'."
I cannot access it in OBS web, I get There has been an internal error. Please try again.
so the new key might indeed be the problem.
-- On a long enough timeline the survival rate for everyone drops to zero...
Further examples that probably since the change of the signing key for Tumbleweed problems exist with the package build on obs. Besides local builds, home repos and packman, dev repos are also affected, e.g. vhba-kmp is available in Factory for kernel 6.1.8 https://build.opensuse.org/package/live_build_log/openSUSE:Factory/vhba-kmp/... in the Devel repo but still only for kernel 6.1.7 https://build.opensuse.org/package/live_build_log/filesystems/vhba-kmp/openS... The same is true for VirtualBox: 6.1.8 in factory https://build.opensuse.org/package/live_build_log/openSUSE:Factory/virtualbo... 6.1.7 in devel repo https://build.opensuse.org/package/live_build_log/Virtualization/virtualbox:... But as already explained, not only kernel modules are affected, but every software package that has probably been released as a new snapshot since the key change. I have created a simple test package which simply requests updated packages from the last snapshot as buildrequires: https://build.opensuse.org/package/show/home:munix9:test/cannoli see also https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/F... BuildRequires: bind BuildRequires: logrotate BuildRequires: lsof Result: [ 47s] + echo 'bind (9.18.10 -> 9.18.11)' [ 47s] bind (9.18.10 -> 9.18.11) [ 47s] + rpm -q bind [ 48s] bind-9.18.10-2.1.x86_64 [ 48s] + echo 'logrotate (3.20.1 -> 3.21.0)' [ 48s] logrotate (3.20.1 -> 3.21.0) [ 48s] + rpm -q logrotate [ 48s] logrotate-3.20.1-3.1.x86_64 [ 48s] + echo 'lsof (4.96.5 -> 4.97.0)' [ 48s] lsof (4.96.5 -> 4.97.0) [ 48s] + rpm -q lsof [ 48s] lsof-4.96.5-1.1.x86_64 The outdated packages are still used for the build.
participants (4)
-
Andreas Prittwitz
-
Andrei Borzenkov
-
Larry Finger
-
munix9