Hi Release Team,

I'm trying to understand why this package (haskell-copilot-theorem[1])
isn't migrating to testing. It looks like it is saying that it is being blocked by haskell-what4, but haskell-what4 has already migrated to
testing on October 17. Also, if I look at excuses for haskell-what4,
there aren't any.

The only thing I can possibly think is that it is referring to migration
of binNMU's, but I can't see any way to see the status of those. Is it possible?

Thanks,
Scott

[1] https://qa.debian.org/excuses.php?package=haskell-copilot-theorem

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

To: debian-release@lists.debian.org

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

SGkgU2NvdHQsDQoNCk9uIDIzLTExLTIwMjIgMTU6MjYsIFNjb3R0IFRhbGJlcnQgd3JvdGU6 DQo+IEhpIFJlbGVhc2UgVGVhbSwNCj4gDQo+IEknbSB0cnlpbmcgdG8gdW5kZXJzdGFuZCB3 aHkgdGhpcyBwYWNrYWdlIChoYXNrZWxsLWNvcGlsb3QtdGhlb3JlbVsxXSkgDQo+IGlzbid0 IG1pZ3JhdGluZyB0byB0ZXN0aW5nLsKgIEl0IGxvb2tzIGxpa2UgaXQgaXMgc2F5aW5nIHRo YXQgaXQgaXMgYmVpbmcgDQo+IGJsb2NrZWQgYnkgaGFza2VsbC13aGF0NCwgYnV0IGhhc2tl bGwtd2hhdDQgaGFzIGFscmVhZHkgbWlncmF0ZWQgdG8gDQo+IHRlc3Rpbmcgb24gT2N0b2Jl ciAxNy7CoCBBbHNvLCBpZiBJIGxvb2sgYXQgZXhjdXNlcyBmb3IgaGFza2VsbC13aGF0NCwg DQo+IHRoZXJlIGFyZW4ndCBhbnkuDQo+IA0KPiBUaGUgb25seSB0aGluZyBJIGNhbiBwb3Nz aWJseSB0aGluayBpcyB0aGF0IGl0IGlzIHJlZmVycmluZyB0byBtaWdyYXRpb24gDQo+IG9m IGJpbk5NVSdzLCBidXQgSSBjYW4ndCBzZWUgYW55IHdheSB0byBzZWUgdGhlIHN0YXR1cyBv ZiB0aG9zZS7CoCBJcyBpdCANCj4gcG9zc2libGU/DQo+IA0KPiBUaGFua3MsDQo+IFNjb3R0 DQo+IA0KPiBbMV0gaHR0cHM6Ly9xYS5kZWJpYW4ub3JnL2V4Y3VzZXMucGhwP3BhY2thZ2U9 aGFza2VsbC1jb3BpbG90LXRoZW9yZW0NCj4gDQoNCkl0IHNheXM6DQpoYXNrZWxsLWNvcGls b3QtdGhlb3JlbSBoYXNrZWxsLXBhcmFtZXRlcml6ZWQtdXRpbHMvcHBjNjRlbCAobm90IGNv bnNpZGVyZWQpDQoNCldoaWNoIG1lYW5zIHRoYXQgaGFza2VsbC1jb3BpbG90LXRoZW9yZW0g b24gcHBjNjRlbCBkZXBlbmRzIG9uIA0Kc3JjOmhhc2tlbGwtcGFyYW1ldGVyaXplZC11dGls cy4NCg0KUGlja2luZyBvbmUgb2YgdGhlIGJpbmFyaWVzIGZyb20gdGhhdCBzb3VyY2UgYW5k IGFza2luZyBybWFkaXNvbiBzYXlzOg0KcGF1bEBtdWxjaWJlciB+ICQgcm1hZGlzb24gbGli Z2hjLXBhcmFtZXRlcml6ZWQtdXRpbHMtZGV2DQpsaWJnaGMtcGFyYW1ldGVyaXplZC11dGls cy1kZXYgfCAyLjEuNS4wLTIrYjEgIHwgdGVzdGluZyAgICB8IGFtZDY0LCANCmFybTY0LCBh cm1lbCwgYXJtaGYsIGkzODYsIG1pcHM2NGVsLCBtaXBzZWwsIHBwYzY0ZWwsIHMzOTB4DQps aWJnaGMtcGFyYW1ldGVyaXplZC11dGlscy1kZXYgfCAyLjEuNS4wLTIrYjIgIHwgdW5zdGFi bGUgICB8IG1pcHM2NGVsLCANCm1pcHNlbCwgcHBjNjRlbA0KbGliZ2hjLXBhcmFtZXRlcml6 ZWQtdXRpbHMtZGV2IHwgMi4xLjUuMC0yK2IzICB8IHVuc3RhYmxlICAgfCBhcm1oZiwgDQpp Mzg2LCBzMzkweA0KbGliZ2hjLXBhcmFtZXRlcml6ZWQtdXRpbHMtZGV2IHwgMi4xLjUuMC0y K2I0ICB8IHVuc3RhYmxlICAgfCBhbWQ2NCwgDQphcm02NCwgYXJtZWwNCg0KU28gaW5kZWVk LCB0aGUgYmluTk1VJ3Mgb2YgdGhhdCBzb3VyY2UgYXJlIG91dC1vZi1zeW5jIGJldHdlZW4g dGVzdGluZyANCmFuZCB1bnN0YWJsZS4NCg0KU2VhcmNoaW5nIGluIHRoZSBleGN1c2VzIFsy XSBJIHNlZSB0aGlzOg0KRGVwZW5kczogaGFza2VsbC1wYXJhbWV0ZXJpemVkLXV0aWxzL2Ft ZDY0IDxhIA0KaHJlZj0iI2hhc2tlbGwtdGgtYWJzdHJhY3Rpb24iPmhhc2tlbGwtdGgtYWJz dHJhY3Rpb248L2E+DQoNClNvIHRoYXQgcG9pbnRzIGF0IGhhc2tlbGwtdGgtYWJzdHJhY3Rp b24uLi4uICh3aGljaCBzZWVtcyBpbiBhIHNpbWlsYXIgDQpzaXR1YXRpb24gYnV0IHRoZW4g d2l0aCBoYXNrZWxsLWNsYXNoLXByZWx1ZGUpDQoNClBhdWwNCg0KWzJdICJzb3VyY2U6IGhh c2tlbGwtcGFyYW1ldGVyaXplZC11dGlscyIgaW4gDQpodHRwczovL3JlbGVhc2UuZGViaWFu Lm9yZy9icml0bmV5L2V4Y3VzZXMueWFtbA0K

--------------VZVHDkhiEyX6EY1BIr07Wrm9--

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

wsB5BAABCAAjFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmN+aKIFAwAAAAAACgkQnFyZ6wW9dQpa mAf7BjwrxxpjRtXHC6DzJOP04RsAq2jYIehC0C1YkHT7lUipbN3InLLNiTnR2DguvhCodUgcoNhY J4u4u8sjbcF+GWo5gtKoiDgWrS7c8R3+uULsg41mkHf9lg0KQLR9hLRGN5keIJQ1WWK6tqZBBBjk l3wFBhk//FEDs1Kgjnf32Zxb4kx+AYnI2jj2nn+1PAw8KZY0Kb/WdttxjTXYV2FkUDrAfdpT7Hpv Ip3BGkMcjb2zkLcOg84wNb/kkwgpkjK7V5GPOXiH3m0/RgTw43b5kH2rGYjIaqrQmtn1B5Vi4aBX TLpu1HTDhvdo+LDxdsPOEv8qhoAn65OWBKAXRKmDKA==
=ZeZ0
-----END PGP SIGNATURE-----

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

Hi Scott

On 2022-11-23 19:38:26 +0100, Paul Gevers wrote:

Hi Scott,

On 23-11-2022 15:26, Scott Talbert wrote:

Hi Release Team,

I'm trying to understand why this package (haskell-copilot-theorem[1]) isn't migrating to testing.  It looks like it is saying that it is being blocked by haskell-what4, but haskell-what4 has already migrated to
testing on October 17.  Also, if I look at excuses for haskell-what4, there aren't any.

The only thing I can possibly think is that it is referring to migration
of binNMU's, but I can't see any way to see the status of those.  Is it possible?

Thanks,
Scott

[1] https://qa.debian.org/excuses.php?package=haskell-copilot-theorem

It says:
haskell-copilot-theorem haskell-parameterized-utils/ppc64el (not considered)

Which means that haskell-copilot-theorem on ppc64el depends on src:haskell-parameterized-utils.

Picking one of the binaries from that source and asking rmadison says: paul@mulciber ~ $ rmadison libghc-parameterized-utils-dev libghc-parameterized-utils-dev | 2.1.5.0-2+b1 | testing | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libghc-parameterized-utils-dev | 2.1.5.0-2+b2 | unstable | mips64el, mipsel, ppc64el
libghc-parameterized-utils-dev | 2.1.5.0-2+b3 | unstable | armhf, i386, s390x
libghc-parameterized-utils-dev | 2.1.5.0-2+b4 | unstable | amd64, arm64, armel

So indeed, the binNMU's of that source are out-of-sync between testing and unstable.

Searching in the excuses [2] I see this:
Depends: haskell-parameterized-utils/amd64 <a href="#haskell-th-abstraction">haskell-th-abstraction</a>

So that points at haskell-th-abstraction.... (which seems in a similar situation but then with haskell-clash-prelude)

And if you go down the rabbit hole far enough, you'll eventually reach
#1023149 which needs to be taken care of.

Cheers
--
Sebastian Ramacher

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

This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.

On Thu, 24 Nov 2022, Sebastian Ramacher wrote:

Hi Scott

On 2022-11-23 19:38:26 +0100, Paul Gevers wrote:

Hi Scott,

On 23-11-2022 15:26, Scott Talbert wrote:

Hi Release Team,

I'm trying to understand why this package (haskell-copilot-theorem[1])
isn't migrating to testing.  It looks like it is saying that it is being >>> blocked by haskell-what4, but haskell-what4 has already migrated to
testing on October 17.  Also, if I look at excuses for haskell-what4,
there aren't any.

The only thing I can possibly think is that it is referring to migration >>> of binNMU's, but I can't see any way to see the status of those.  Is it >>> possible?

Thanks,
Scott

[1] https://qa.debian.org/excuses.php?package=haskell-copilot-theorem

It says:
haskell-copilot-theorem haskell-parameterized-utils/ppc64el (not considered) >>
Which means that haskell-copilot-theorem on ppc64el depends on
src:haskell-parameterized-utils.

Picking one of the binaries from that source and asking rmadison says:
paul@mulciber ~ $ rmadison libghc-parameterized-utils-dev
libghc-parameterized-utils-dev | 2.1.5.0-2+b1 | testing | amd64, arm64, >> armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libghc-parameterized-utils-dev | 2.1.5.0-2+b2 | unstable | mips64el,
mipsel, ppc64el
libghc-parameterized-utils-dev | 2.1.5.0-2+b3 | unstable | armhf, i386, >> s390x
libghc-parameterized-utils-dev | 2.1.5.0-2+b4 | unstable | amd64, arm64, >> armel

So indeed, the binNMU's of that source are out-of-sync between testing and >> unstable.

Searching in the excuses [2] I see this:
Depends: haskell-parameterized-utils/amd64 <a
href="#haskell-th-abstraction">haskell-th-abstraction</a>

So that points at haskell-th-abstraction.... (which seems in a similar
situation but then with haskell-clash-prelude)

And if you go down the rabbit hole far enough, you'll eventually reach #1023149 which needs to be taken care of.

Yes, that's the same conclusion I came to. Thanks!

Scott

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

On 2022-11-24 09:47:51 -0500, Scott Talbert wrote:

On Thu, 24 Nov 2022, Sebastian Ramacher wrote:

Hi Scott

On 2022-11-23 19:38:26 +0100, Paul Gevers wrote:

Hi Scott,

On 23-11-2022 15:26, Scott Talbert wrote:

Hi Release Team,

I'm trying to understand why this package (haskell-copilot-theorem[1]) isn't migrating to testing.  It looks like it is saying that it is being
blocked by haskell-what4, but haskell-what4 has already migrated to testing on October 17.  Also, if I look at excuses for haskell-what4, there aren't any.

The only thing I can possibly think is that it is referring to migration
of binNMU's, but I can't see any way to see the status of those.  Is it
possible?

Thanks,
Scott

[1] https://qa.debian.org/excuses.php?package=haskell-copilot-theorem

It says:
haskell-copilot-theorem haskell-parameterized-utils/ppc64el (not considered)

Which means that haskell-copilot-theorem on ppc64el depends on src:haskell-parameterized-utils.

Picking one of the binaries from that source and asking rmadison says: paul@mulciber ~ $ rmadison libghc-parameterized-utils-dev libghc-parameterized-utils-dev | 2.1.5.0-2+b1 | testing | amd64, arm64,
armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libghc-parameterized-utils-dev | 2.1.5.0-2+b2 | unstable | mips64el, mipsel, ppc64el
libghc-parameterized-utils-dev | 2.1.5.0-2+b3 | unstable | armhf, i386,
s390x
libghc-parameterized-utils-dev | 2.1.5.0-2+b4 | unstable | amd64, arm64,
armel

So indeed, the binNMU's of that source are out-of-sync between testing and
unstable.

Searching in the excuses [2] I see this:
Depends: haskell-parameterized-utils/amd64 <a href="#haskell-th-abstraction">haskell-th-abstraction</a>

So that points at haskell-th-abstraction.... (which seems in a similar situation but then with haskell-clash-prelude)

And if you go down the rabbit hole far enough, you'll eventually reach #1023149 which needs to be taken care of.

Yes, that's the same conclusion I came to. Thanks!

The next blocker is #1023020.

Cheers
--
Sebastian Ramacher

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

This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.

On Sun, 27 Nov 2022, Sebastian Ramacher wrote:

On 2022-11-24 09:47:51 -0500, Scott Talbert wrote:

On Thu, 24 Nov 2022, Sebastian Ramacher wrote:

Hi Scott

On 2022-11-23 19:38:26 +0100, Paul Gevers wrote:

Hi Scott,

On 23-11-2022 15:26, Scott Talbert wrote:

Hi Release Team,

I'm trying to understand why this package (haskell-copilot-theorem[1]) >>>>> isn't migrating to testing.  It looks like it is saying that it is being >>>>> blocked by haskell-what4, but haskell-what4 has already migrated to
testing on October 17.  Also, if I look at excuses for haskell-what4, >>>>> there aren't any.

The only thing I can possibly think is that it is referring to migration >>>>> of binNMU's, but I can't see any way to see the status of those.  Is it >>>>> possible?

Thanks,
Scott

[1] https://qa.debian.org/excuses.php?package=haskell-copilot-theorem >>>>>

It says:
haskell-copilot-theorem haskell-parameterized-utils/ppc64el (not considered)

Which means that haskell-copilot-theorem on ppc64el depends on
src:haskell-parameterized-utils.

Picking one of the binaries from that source and asking rmadison says: >>>> paul@mulciber ~ $ rmadison libghc-parameterized-utils-dev
libghc-parameterized-utils-dev | 2.1.5.0-2+b1 | testing | amd64, arm64,
armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libghc-parameterized-utils-dev | 2.1.5.0-2+b2 | unstable | mips64el, >>>> mipsel, ppc64el
libghc-parameterized-utils-dev | 2.1.5.0-2+b3 | unstable | armhf, i386, >>>> s390x
libghc-parameterized-utils-dev | 2.1.5.0-2+b4 | unstable | amd64, arm64,
armel

So indeed, the binNMU's of that source are out-of-sync between testing and >>>> unstable.

Searching in the excuses [2] I see this:
Depends: haskell-parameterized-utils/amd64 <a
href="#haskell-th-abstraction">haskell-th-abstraction</a>

So that points at haskell-th-abstraction.... (which seems in a similar >>>> situation but then with haskell-clash-prelude)

And if you go down the rabbit hole far enough, you'll eventually reach
#1023149 which needs to be taken care of.

Yes, that's the same conclusion I came to. Thanks!

The next blocker is #1023020.

Is there a next blocker that you're aware of?

Thanks,
Scott

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