Your message dated Fri, 25 Oct 2019 17:24:34 +0200 with message-id <349f9826-e0a1-caee-ac60-92311e4c6980@debian.org> and subject line Re: Bug#943490: unblock: rust-proc-macro2/1.0.5-1 has caused the Debian Bug report #943490, regarding unblock: rust-proc-macro2/1.0.5-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 943490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943490 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: rust-proc-macro2/1.0.5-1
- From: Nicolas Braud-Santoni <nicoo@debian.org>
- Date: Fri, 25 Oct 2019 14:43:30 +0200
- Message-id: <[🔎] 157200741097.6639.15423463261763098604.reportbug@neon.citronna.de>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear release team, Please unblock the package rust-proc-macro2. Its transition to bullseye is blocked because - - rust-quote/1.0.2-1 depends on rust-proc-macro2/1.0.5-1 ; - - rust-proc-macro2/1.0.5-1 introduces a regression in the autopkgtest for rust-quote/0.6.13-1 (which is currently in bullseye). unblock rust-proc-macro2/1.0.5-1 Best, nicoo - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAl2y7e8RHG5pY29vQGRl Ymlhbi5vcmcACgkQ5vmO4pLV7Mt35g/6Aib24TPJ2jAoufLizqCiHZsqaFCKAor+ URU8pcprrg4HVk5L8K3QWOhlqMVLByQJj+XAbEWA69rDTDOl1BKTD+a2hdoSk9Pw mYxa24O5kqSI1kiegvj0yoa4cVd1ODZFw8Ts4FlyxJRcWMugiEhoXfOqGuQsvaDB FepBe8dcLwRgbxqK3WMS+RPBUzM6wBhjy5PFHWEBiLTmB6scsp77ruQ+Wif0l//M KianYWIaRLQUtjMLj+5Q/EwuVCpXX3ufw9BaHi+HvEYcs95IlApuT+twhC9GHVHJ rafVqsMLDc6AHqU/yRG4WtG2ZxXO0f33gm+PyrAuRSUjesDhaoS0nB7nNwhz7M/K pSw1U4zKSkcGhDm97u60I4hm0qRrS+iLniRjps2RNjVu6LM+m8rtMfivYzYubssT 8c7cn1TDFXqT/E7GoRuQBTqpQRPcpSsO0zhIvUQPbsHnAaMOEC8vNOIQLwC6Ee53 a1LYcW4Cd3Aje9dmRTKHZQ/zWnc2taLjB/KmqxqF8q1+mw6hUdfd0LebivVmRHI6 iv89d1Rxyd5AgoqEWd/WzZfO46pdypOPLo+8jtDUWBpF5Qjf7JULRqhAe1VNfhJb d63tYkfA7vIMb4dafJVWOqljqx836LfiaTngucxmdOyQBah828DZkCI/iV5ZdPxS sAnrd61FBis= =pVpl -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
- To: Nicolas Braud-Santoni <nicoo@debian.org>, 943490-done@bugs.debian.org
- Subject: Re: Bug#943490: unblock: rust-proc-macro2/1.0.5-1
- From: Paul Gevers <elbrus@debian.org>
- Date: Fri, 25 Oct 2019 17:24:34 +0200
- Message-id: <349f9826-e0a1-caee-ac60-92311e4c6980@debian.org>
- In-reply-to: <[🔎] 157200741097.6639.15423463261763098604.reportbug@neon.citronna.de>
- References: <[🔎] 157200741097.6639.15423463261763098604.reportbug@neon.citronna.de>
Dear Nicolas, > Please unblock the package rust-proc-macro2. > > Its transition to bullseye is blocked because > - rust-quote/1.0.2-1 depends on rust-proc-macro2/1.0.5-1 ; > - rust-proc-macro2/1.0.5-1 introduces a regression in the autopkgtest for > rust-quote/0.6.13-1 (which is currently in bullseye). > > unblock rust-proc-macro2/1.0.5-1 The missing information here is that you "fixed" the autopkgtest of rust-quote already in unstable. So what's missing is the versioned Breaks in rust-proc-macro2 on rust-quote (although you might argue that that's not technically correct). If the package would have that, britney would automatically use the package from unstable and everything would, I heavily suspect, be OK. I have triggered the test with rust-quote from unstable, so you don't need to do that now; but for next time. PaulAttachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---