Re: new upstream version fails older tests of rdepends packages

2024-05-10 Thread Bill Allombert
Le Wed, May 08, 2024 at 08:41:47PM +0200, Paul Gevers a écrit :
> 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.

Thanks a lot, this fixed the issue, all packages have migrated to testing now. 
I still think this is a much better outcome than a new upload with
spurious Breaks:.

Cheers,
-- 
Bill. 

Imagine a large red swirl here.



Re: new upstream version fails older tests of rdepends packages

2024-05-08 Thread Paul Gevers

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.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature


Re: new upstream version fails older tests of rdepends packages

2024-05-08 Thread Bill Allombert
On Wed, May 08, 2024 at 03:21:12PM +, Graham Inggs wrote:
> Hi Bill
> 
> On Wed, 8 May 2024 at 13:58, Bill Allombert  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.

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.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



Re: new upstream version fails older tests of rdepends packages

2024-05-08 Thread Graham Inggs
Hi Bill

On Wed, 8 May 2024 at 13:58, Bill Allombert  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.

Regards
Graham



Re: new upstream version fails older tests of rdepends packages

2024-05-08 Thread Bill Allombert
Le Sat, May 04, 2024 at 02:32:22PM +0200, Paul Gevers a écrit :
> 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.

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.

Cheers,
-- 
Bill. 

Imagine a large red swirl here.



Re: new upstream version fails older tests of rdepends packages

2024-05-04 Thread Paul Gevers

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.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature


new upstream version fails older tests of rdepends packages

2024-05-04 Thread Jerome BENOIT

Hi,

it appears that the packages  gap [0] and gap-io [1] are blocked because
some of their r-dependent packages (e.g., gap-factint) actually in testing
fail one a their tests. The tests in question are similar and fail
because the last version of gap adds now a trailing slash to path directories 
[2].
This common issue has been effectively fixed for the involved packages (e.g., 
gap-factint).
What would be the best way to unblock the migration of gap and gap-io ?
Thanks in advance, cheers, Jerome


[0] https://tracker.debian.org/pkg/gap
[1] https://tracker.debian.org/pkg/gap-io
[2] https://lists.debian.org/debian-math/2024/03/msg0.html

--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B