Hi,
On 04-05-2024 11:39 a.m., Jerome BENOIT wrote:
What would be the best way to unblock the migration of gap and gap-io ?
If gap isn't going to change (which might be the easiest solution), then
file bugs and fix those reverse dependencies. Those bugs are RC and in due time will cause autoremoval.
Hi Bill
On Wed, 8 May 2024 at 13:58, Bill Allombert <ballombe@debian.org> wrote:
The problem is that all the debs in testing and sid are correct, it is the autopkgtest in
testing which are wrong (they are relying on undocumented behaviour).
They are fixed in sid.
I think an upload of gap, with Breaks on the versions of the gap-*
packages that are wrong, should allow migration.
The problem is that all the debs in testing and sid are correct, it is the autopkgtest in
testing which are wrong (they are relying on undocumented behaviour).
They are fixed in sid.
Hi,
On 08-05-2024 6:06 p.m., Bill Allombert wrote:
Agreed, but gap does not actually breaks anything, it is just the tests
in testing that are broken. So I can do that but that seems a bit artificial.
Aha, that wasn't at all clear to me. If you don't want to do the artificial thing (which is fine, except now you depend on members of the release team), I'll manually schedule the tests. Maybe tomorrow.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 147:29:00 |
Calls: | 10,383 |
Calls today: | 8 |
Files: | 14,054 |
D/L today: |
2 files (1,861K bytes) |
Messages: | 6,417,731 |