On 5/24/22 21:34, Paul Gevers wrote:
https://bugs.debian.org/1011268 (but apparently my first assumption
was wrong and it's another bug, most likely Simon was right.
Thanks for the link. I was quite puzzled this morning when I saw
several removals messages.
https://bugs.debian.org/1011268 (but apparently my first assumption
was wrong and it's another bug, most likely Simon was right.
Issues preventing migration:
Not built on buildd: arch all binaries uploaded by venthur, a new source-only upload is needed to allow migration
I wonder why an irrelevant package suddenly triggered autoremoval
of a very large portion of packages from testing.
https://udd.debian.org/cgi-bin/autoremovals.cgi
Searched for keyword nvidia-graphics-drivers-tesla-470, and I got
68866 entries. There must be something wrong.
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=nvidia-graphics-drivers-tesla-470
Looking at the bug report of the package itself, and it does not
look like glibc package is made broken by it.
Any idea?
Hi,
sorry I didn't follow the conversation but it seems that all my
Python
packages are still not migrating to testing and I don't really
understand how to fix it. The error I see consistently in my Python
packages is:
Issues preventing migration:
Not built on buildd: arch all binaries uploaded by venthur, a new source-only upload is needed to allow migration
I've re-uploaded all packages a few days ago, but the error is still
the same.
On Tue, 28 Jun 2022, [email protected] wrote:
Wild guess: were your new uploads _*source-only*_ ?
I looked at a couple of them and they were (source all) so that does
appear to be the problem. All uploads need to be source-only (since bullseye?).
Hi,
sorry I didn't follow the conversation but it seems that all my
Python
packages are still not migrating to testing and I don't really
understand how to fix it. The error I see consistently in my Python
packages is:
Issues preventing migration:
Not built on buildd: arch all binaries uploaded by venthur, a new
source-only upload is needed to allow migration
I've re-uploaded all packages a few days ago, but the error is still
the same.
Wild guess: were your new uploads _*source-only*_ ?
There are patches to support throw away binaries, but as far as I'm
aware they haven't been merged and I don't know the status of the
patches. That won't remove the need for binary uploads, but it would
remove the need for a re-upload.
Le mardi 28 juin 2022 à 22:08 +0200, Bastian Venthur a écrit :
Wild guess: were your new uploads _*source-only*_ ?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 159:56:14 |
| Calls: | 12,094 |
| Calls today: | 2 |
| Files: | 15,000 |
| Messages: | 6,517,761 |