• Re: new upstream version fails older tests of rdepends packages

    From Paul Gevers@21:1/5 to All on Sat May 4 14:40:01 2024
    To: debian-devel@lists.debian.org

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------RIwo5Ri2pTj9k99Hzz65B6uK
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    SGksDQoNCk9uIDA0LTA1LTIwMjQgMTE6MzkgYS5tLiwgSmVyb21lIEJFTk9JVCB3cm90ZToN Cj4gV2hhdCB3b3VsZCBiZSB0aGUgYmVzdCB3YXkgdG8gdW5ibG9jayB0aGUgbWlncmF0aW9u IG9mIGdhcCBhbmQgZ2FwLWlvID8NCg0KSWYgZ2FwIGlzbid0IGdvaW5nIHRvIGNoYW5nZSAo d2hpY2ggbWlnaHQgYmUgdGhlIGVhc2llc3Qgc29sdXRpb24pLCB0aGVuIA0KZmlsZSBidWdz IGFuZCBmaXggdGhvc2UgcmV2ZXJzZSBkZXBlbmRlbmNpZXMuIFRob3NlIGJ1Z3MgYXJlIFJD IGFuZCBpbiANCmR1ZSB0aW1lIHdpbGwgY2F1c2UgYXV0b3JlbW92YWwuDQoNClBhdWwNCg==


    --------------RIwo5Ri2pTj9k99Hzz65B6uK--

    -----BEGIN PGP SIGNATURE-----

    wsB5BAABCAAjFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmY2KtcFAwAAAAAACgkQnFyZ6wW9dQpV YwgAmSIUvEX23tyDEcWKYCYgf81MhXF+62K7xDhl32YlUGvj4TtcpV+aNrTYDKNwrQvNT/gzrdtE 2vFukyRF0hP78MBw0AJllUVibuzYOwRXeDQKhk93NniahzcA+o3426Q+DOf0uUfXmJVtlfDx3zBi 0mP45foT380fR9XIKmF+kdS4jKSNkiWN+83SEw+w1LvZlzFrrPTUUC+yKcI4THyN+qUDqcu6/9cr AMZFDabtVl256jUFHns80Y5FdJZrIjXUFETh7NxhpFPvzGVUlf9yGKM8fBAD6QHvW4ygx8OiX94c PGpDw45iwke0UeAhtW7IxNRbCZRJefc/KtGbO/9RdA==
    =LLDv
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bill Allombert@21:1/5 to All on Wed May 8 16:00:01 2024
    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. <ballombe@debian.org>

    Imagine a large red swirl here.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bill Allombert@21:1/5 to Graham Inggs on Wed May 8 18:10:01 2024
    On Wed, May 08, 2024 at 03:21:12PM +0000, Graham Inggs wrote:
    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.

    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. <ballombe@debian.org>

    Imagine a large red swirl here.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Graham Inggs@21:1/5 to Bill Allombert on Wed May 8 17:30:01 2024
    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.

    Regards
    Graham

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Gevers@21:1/5 to Bill Allombert on Wed May 8 20:50:01 2024
    To: debian-devel@lists.debian.org

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------d47O4WzS1EqaxSuSdTiooTcl
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    SGksDQoNCk9uIDA4LTA1LTIwMjQgNjowNiBwLm0uLCBCaWxsIEFsbG9tYmVydCB3cm90ZToN Cj4gQWdyZWVkLCBidXQgZ2FwIGRvZXMgbm90IGFjdHVhbGx5IGJyZWFrcyBhbnl0aGluZywg aXQgaXMganVzdCB0aGUgdGVzdHMNCj4gaW4gdGVzdGluZyB0aGF0IGFyZSBicm9rZW4uIFNv IEkgY2FuIGRvIHRoYXQgYnV0IHRoYXQgc2VlbXMgYSBiaXQgYXJ0aWZpY2lhbC4NCg0KQWhh LCB0aGF0IHdhc24ndCBhdCBhbGwgY2xlYXIgdG8gbWUuIElmIHlvdSBkb24ndCB3YW50IHRv IGRvIHRoZSANCmFydGlmaWNpYWwgdGhpbmcgKHdoaWNoIGlzIGZpbmUsIGV4Y2VwdCBub3cg eW91IGRlcGVuZCBvbiBtZW1iZXJzIG9mIHRoZSANCnJlbGVhc2UgdGVhbSksIEknbGwgbWFu dWFsbHkgc2NoZWR1bGUgdGhlIHRlc3RzLiBNYXliZSB0b21vcnJvdy4NCg0KUGF1bA0K

    --------------d47O4WzS1EqaxSuSdTiooTcl--

    -----BEGIN PGP SIGNATURE-----

    wsB5BAABCAAjFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmY7x2sFAwAAAAAACgkQnFyZ6wW9dQrN 3ggAuPh8GElKhm5sKM10E5KhF0hZUe3IruMN0VKxdXZtupINFerPdDrpnUgsIsORl4DSDftRfyjH 2tBJ6WPV+qwPaTGKXSPgQmfgD5pbAfV+j4MdH6Kh8ysKdELOmkShGzWJjdyokY1CehNTyCpHWNpA lu7UZfVhug5dunaHGWZrw1fOL6u7pNmcV+ajfnpuK9RAR30Qi97p+aQj+LfRZ3OE2xHEp8ZLFFnG eTQp0oiEeNnnnSLIk2JAHmLtgVzakUFz0AcwIWQk31k9eqkk5lrcqsF3LszcBsRqoRBvUulrCCBI e8I4+DIRyo4OZOx8kA4EOjWz7sukpTeGqHuK0migCg==
    =LyAr
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bill Allombert@21:1/5 to All on Fri May 10 15:00:02 2024
    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. <ballombe@debian.org>

    Imagine a large red swirl here.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)