Debian:Testing couldn't get packages signed for download
Hi Everyone, I found that my https://build.opensuse.org/project/show/home:alvistack couldn't get Debian:Testing signing package for download: * https://build.opensuse.org/project/repository_state/home:alvistack/Debian_Te... * https://build.opensuse.org/projects/home:alvistack/rebuild_time?arch=x86_64&repository=Debian_Testing BTW, following repo for latest rolling release could get signed package correctly, e.g. * https://build.opensuse.org/project/repository_state/home:alvistack/Fedora_Ra... * https://build.opensuse.org/project/repository_state/home:alvistack/openSUSE_... * https://build.opensuse.org/project/repository_state/home:alvistack/xUbuntu_2... (especially for this, because it is most likely with latest packages as similar as Debian:Testing) From Web UI I couldn't find any hints why all package for Debian:Testing build successfully completed, but didn't get signed for download. May someone give me a hints for debugging this issue? Regards, Edison Wong
On Freitag, 21. Oktober 2022, 04:27:30 CEST Wong Hoi Sing Edison wrote:
Hi Everyone,
I found that my https://build.opensuse.org/project/show/home:alvistack couldn't get Debian:Testing signing package for download:
* https://build.opensuse.org/project/repository_state/home:alvistack/Debian_Te... * https://build.opensuse.org/projects/home:alvistack/rebuild_time?arch=x86_64&repository=Debian_Testing
I can not see such an error on these pages, the cycles not a problem per se.
BTW, following repo for latest rolling release could get signed package correctly, e.g.
* https://build.opensuse.org/project/repository_state/home:alvistack/Fedora_Ra... * https://build.opensuse.org/project/repository_state/home:alvistack/openSUSE_... * https://build.opensuse.org/project/repository_state/home:alvistack/xUbuntu_2... (especially for this, because it is most likely with latest packages as similar as Debian:Testing)
From Web UI I couldn't find any hints why all package for Debian:Testing build successfully completed, but didn't get signed for download.
Your published repository has a signature in Release.gpg for the Release file.
What else do you expect to get signed?
--
Adrian Schroeter
Dear Adrian, Take this package as example (build completed 1 day ago): * https://build.opensuse.org/package/show/home:alvistack/containers-podman-4.3... For Debian:Testing it could show the result package get done correctly: * https://build.opensuse.org/package/binaries/home:alvistack/containers-podman... podman-docker_4.3.0-1_amd64.deb (2.52 KB) podman_4.3.0-1.debian.tar.xz (2.32 KB) podman_4.3.0-1.dsc (1.12 KB) podman_4.3.0-1_amd64.buildinfo (7.08 KB) podman_4.3.0-1_amd64.changes (2.1 KB) podman_4.3.0-1_amd64.deb (17.4 MB) podman_4.3.0.orig.tar.gz (12.6 MB) But it couldn't found from https://download.opensuse.org/repositories/home:/alvistack/Debian_Testing/, only https://download.opensuse.org/repositories/home:/alvistack/Debian_Testing/am... is now exists. Moreover, with Web UI shown by https://build.opensuse.org/project/show/home:alvistack, Debian:Testing just coming with a grey "tick" icon, but not the normal green "truck" icon. Accordingly to my daily experience with OBS, it means complete build package is now pending to be copy to https://download.opensuse.org/, so it is not ready to be use by APT. Regards, Edison Wong
Oh it suddenly get moving and showing the green "truck" icon for Debian:Testing again ;-) Anyway Adrian thank you very much for your prompt reply ;-)
participants (2)
-
Adrian Schröter -
Wong Hoi Sing Edison