tickets #136373
closedObsolete Tumbleweed i586 iso images
0%
Description
We have these laying around https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-NET-i586-Snapshot20230326-Media.iso while the current i586 images are here https://download.opensuse.org/ports/i586/tumbleweed/iso/openSUSE-Tumbleweed-LegacyX86-NET-i586-Snapshot20230922-Media.iso
Updated by luc14n0 over 1 year ago
- Status changed from New to Workable
- Private changed from Yes to No
Indeed, it seems no one realized that and deleted those "leftovers".
Updated by luc14n0 over 1 year ago
Although I don't have privileges on pontifex2, I'd expect there's some way to mark those images and links as deprecated in order to delete them, and so that the deletion propagates to mirrors.
Let's see what others have to say.
Updated by pjessen over 1 year ago
luc14n0 wrote in #note-3:
Although I don't have privileges on pontifex2, I'd expect there's some way to mark those images and links as deprecated in order to delete them, and so that the deletion propagates to mirrors.
Let's see what others have to say.
pontifex is really only doing what it is told, i.e. publishing whatever is being pushed from build service.
Updated by cboltz over 1 year ago
- Assignee set to dimstar
Dominique, can you clean this up on the OBS side?
Updated by luc14n0 over 1 year ago
pjessen wrote in #note-4:
luc14n0 wrote in #note-3:
Although I don't have privileges on pontifex2, I'd expect there's some way to mark those images and links as deprecated in order to delete them, and so that the deletion propagates to mirrors.
Let's see what others have to say.
pontifex is really only doing what it is told, i.e. publishing whatever is being pushed from build service.
That's good to know. A concern I have had in the past, but haven't looked at it closer, is when we disable the build flag of a package (and even perhaps of a project). Without manually wiping the built binaries, they will hang in the repositories who knows for how long. But I don't think this has much to do with the issue at hand here, so I'm diverging.
Updated by luc14n0 over 1 year ago
I also like to point out that something is still recreating those links:
luc14n0@provo-mirror:~> ls -l /srv/ftp/pub/opensuse/tumbleweed/iso/openSUSE-Tumbleweed-NET-i586-*
lrwxrwxrwx 1 mirror mirror 55 Sep 27 14:42 /srv/ftp/pub/opensuse/tumbleweed/iso/openSUSE-Tumbleweed-NET-i586-Current.iso -> openSUSE-Tumbleweed-NET-i586-Snapshot20230326-Media.iso
lrwxrwxrwx 1 mirror mirror 62 Sep 27 14:42 /srv/ftp/pub/opensuse/tumbleweed/iso/openSUSE-Tumbleweed-NET-i586-Current.iso.sha256 -> openSUSE-Tumbleweed-NET-i586-Snapshot20230326-Media.iso.sha256
lrwxrwxrwx 1 mirror mirror 66 Sep 27 14:42 /srv/ftp/pub/opensuse/tumbleweed/iso/openSUSE-Tumbleweed-NET-i586-Current.iso.sha256.asc -> openSUSE-Tumbleweed-NET-i586-Snapshot20230326-Media.iso.sha256.asc
-rw-r--r-- 1 mirror mirror 191889408 Mar 27 2023 /srv/ftp/pub/opensuse/tumbleweed/iso/openSUSE-Tumbleweed-NET-i586-Snapshot20230326-Media.iso
-rw-r--r-- 1 mirror mirror 122 Mar 27 2023 /srv/ftp/pub/opensuse/tumbleweed/iso/openSUSE-Tumbleweed-NET-i586-Snapshot20230326-Media.iso.sha256
-rw-r--r-- 1 mirror mirror 827 Mar 27 2023 /srv/ftp/pub/opensuse/tumbleweed/iso/openSUSE-Tumbleweed-NET-i586-Snapshot20230326-Media.iso.sha256.asc
Updated by michals over 1 year ago
luc14n0 wrote in #note-6:
That's good to know. A concern I have had in the past, but haven't looked at it closer, is when we disable the build flag of a package (and even perhaps of a project). Without manually wiping the built binaries, they will hang in the repositories who knows for how long. But I don't think this has much to do with the issue at hand here, so I'm diverging.
It sounds like it is very much what is happening here. Binaries come out of OBS only when they are built in a project, and when very old ones come out this is quite plausible explanation.
Updated by luc14n0 over 1 year ago
michals wrote in #note-8:
luc14n0 wrote in #note-6:
That's good to know. A concern I have had in the past, but haven't looked at it closer, is when we disable the build flag of a package (and even perhaps of a project). Without manually wiping the built binaries, they will hang in the repositories who knows for how long. But I don't think this has much to do with the issue at hand here, so I'm diverging.
It sounds like it is very much what is happening here. Binaries come out of OBS only when they are built in a project, and when very old ones come out this is quite plausible explanation.
I'm not sure about that, actually. I'm confident of what I said, about packages in projects other than openSUSE:Factory -- or openSUSE:Leap*, or SUSE:SLE*, etc -- where they have the release flag activated in OBS, so they are taken care of by the publisher. Tumbleweed snapshots and ISO images are different because they are tested first, before something else publish them. I hope someone correct me if I'm mistaken.
Updated by luc14n0 over 1 year ago
Correcting myself. openSUSE:Factory/standard gets published normally.
Updated by dimstar over 1 year ago
- Assignee changed from dimstar to adrianSuSE
hi Adrian,
from what I can see, openSUSE:Factory:ToTest does not contain those i586/i686 images anymore, yet OBS is rsyncing them over to pontifex on each publish.
Can you help with that cleanup please?
Updated by adrianSuSE over 1 year ago
- Status changed from Workable to Closed
I hope this is cleaned up now.
(sorry, never saw a mail)