Slowroll kernel signing key changed to openSUSE:ALP?
warning: kernel-default-6.4.12-1.13.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 1cbb508c: NOKEY /etc/uefi /etc/uefi/certs /etc/uefi/certs/FFF96EF6.crt bor@bor-Latitude-E5450:~/tmp$ rpm -qlp kernel-default-6.4.11-1.1.x86_64.rpm | grep /etc/ warning: kernel-default-6.4.11-1.1.x86_64.rpm: Header V3 RSA/SHA512 Signature, key ID 29b700a4: NOKEY /etc/uefi /etc/uefi/certs /etc/uefi/certs/1F673297.crt bor@bor-Latitude-E5450:~/tmp$ It is expected for the future? I tried to understand how packages actually get into slowroll, but failed. If someone could provide an overview how it works I would certainly appreciate it.
On 01/10/2023 09.02, Andrei Borzenkov wrote:
warning: kernel-default-6.4.12-1.13.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 1cbb508c: NOKEY /etc/uefi /etc/uefi/certs /etc/uefi/certs/FFF96EF6.crt bor@bor-Latitude-E5450:~/tmp$ rpm -qlp kernel-default-6.4.11-1.1.x86_64.rpm | grep /etc/ warning: kernel-default-6.4.11-1.1.x86_64.rpm: Header V3 RSA/SHA512 Signature, key ID 29b700a4: NOKEY /etc/uefi /etc/uefi/certs /etc/uefi/certs/1F673297.crt bor@bor-Latitude-E5450:~/tmp$
It is expected for the future?
No, it will change once we move out of the openSUSE:ALP namespace.
I tried to understand how packages actually get into slowroll, but failed. If someone could provide an overview how it works I would certainly appreciate it.
So far, I use https://github.com/bmwiedemann/slowroll-tools and run DRYRUN=0 make daily and later make release The first checks for what updates were released in Tumbleweed and submits a selection into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:S... After everything was built and published there, openQA testing is still missing, because the product-builder does not work with OBS' download-on-demand method we use for the TW-snaphot base repo. So we don't have an install-DVD or working Net-install there. Then `make release` uses `osc release` to publish updates into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll If Factory binaries are deemed equivalent by build-compare, those are published instead. I might drop this part later and not re-use any TW/Factory binaries. We also need something like the install-check to ensure we include required updates of dependencies. Ciao Bernhard M.
On 01.10.2023 11:34, Bernhard M. Wiedemann wrote:
On 01/10/2023 09.02, Andrei Borzenkov wrote:
warning: kernel-default-6.4.12-1.13.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 1cbb508c: NOKEY /etc/uefi /etc/uefi/certs /etc/uefi/certs/FFF96EF6.crt bor@bor-Latitude-E5450:~/tmp$ rpm -qlp kernel-default-6.4.11-1.1.x86_64.rpm | grep /etc/ warning: kernel-default-6.4.11-1.1.x86_64.rpm: Header V3 RSA/SHA512 Signature, key ID 29b700a4: NOKEY /etc/uefi /etc/uefi/certs /etc/uefi/certs/1F673297.crt bor@bor-Latitude-E5450:~/tmp$
It is expected for the future?
No, it will change once we move out of the openSUSE:ALP namespace.
I guess the actual question was - why RPMs are rebuilt at all? Was not the idea to use Tumbleweed binaries? At least, that is how I understood it so far.
I tried to understand how packages actually get into slowroll, but failed. If someone could provide an overview how it works I would certainly appreciate it.
So far, I use https://github.com/bmwiedemann/slowroll-tools and run DRYRUN=0 make daily and later make release
There is no "release" target in Makefile.
The first checks for what updates were released in Tumbleweed and submits a selection into https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll:S...
Nor is there any reference to Staging in sources.
After everything was built and published there, openQA testing is still missing, because the product-builder does not work with OBS' download-on-demand method we use for the TW-snaphot base repo. So we don't have an install-DVD or working Net-install there.
Then `make release` uses `osc release` to publish updates into
The only osc invocation I can find is "osc copypac". I was not aware of "osc release", but that explains why build log is completely missing. Same situation as with Leap - binaries just pop up in repository without any way to see how they were built. My feeling is that it does not help to attract contributors. It is already the problem with Leap where you have to be SUSE employee to actually see what's going on. But here everything is on OBS ... or so I naively expected. Is it possible to see build logs for packages moved from Staging to the main (or, better, update) repository?
https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Slowroll
If Factory binaries are deemed equivalent by build-compare, those are published instead. I might drop this part later and not re-use any TW/Factory binaries. We also need something like the install-check to ensure we include required updates of dependencies.
Ciao Bernhard M.
On 01/10/2023 15.16, Andrei Borzenkov wrote:
I guess the actual question was - why RPMs are rebuilt at all? Was not the idea to use Tumbleweed binaries? At least, that is how I understood it so far.
Yes, except sometimes Factory moved on to use new libraries (e.g. glibc) that we don't all want to take along at the same time. In the case of kernel, there are some non-determinisms in the build that caused the scripts to take the Staging version. Plus packages get re-signed with the ALP key on `osc release`
https://github.com/bmwiedemann/slowroll-tools There is no "release" target in Makefile.
my bad. I forgot to push the master branch.
But here everything is on OBS ... or so I naively expected.
It is. Except for the scripts in the git repo.
Is it possible to see build logs for packages moved from Staging to the main
In principle, yes when you know where to look, and no rebuild happened since then e.g. https://build.opensuse.org/package/show/openSUSE:Factory/bzip2 or https://build.opensuse.org/package/show/openSUSE:ALP:Experimental:Slowroll:S... Ciao Bernhard M.
On 01.10.2023 21:28, Bernhard M. Wiedemann wrote:
Is it possible to see build logs for packages moved from Staging to the main
In principle, yes when you know where to look, and no rebuild happened since then e.g. https://build.opensuse.org/package/show/openSUSE:Factory/bzip2
or https://build.opensuse.org/package/show/openSUSE:ALP:Experimental:Slowroll:S...
This only works as long as packages are still in staging. E.g. kernel-default 6.4.12 is not.
participants (2)
-
Andrei Borzenkov -
Bernhard M. Wiedemann