Hi Bastian,
Il 05/01/25 22:03, Bastian Germann ha scritto:
Am 05.01.25 um 21:57 schrieb Antonio Valentino:
Removing c-blosc2 from mips64el without modifying "arch" would be ok
for me, but I would like to be sure that the migration of c-blosc2 is
not blocked after each upload.
Moreover, according to the discussion in [1], apparently the change in
arch is needed, and it is also required to change "arch" for packages
depending on c-blosc2 in order to remove it from mops64el unstable.
This looks strange to me but, apparently, this is the reason why the
migration of c-blosc2 is still blocked.
No, you can see this in the s390x state. This was removed (or never
built?) and is not considered for migration.
The migration check is a regression check. So as soon as the mips64el
bin pkg is removed you will not have to deal with it on subsequent uploads.
understood, thanks
--
Antonio Valentino
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
