[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1007882: marked as done (RM: rust-weedle/0.12.0-2 rust-wasm-bindgen-webidl/0.2.75-1)

Your message dated Sat, 19 Mar 2022 21:55:04 +0100
with message-id <ac03cd3e-925c-c333-6f09-a1ac74bef879@debian.org>
and subject line Re: Bug#1007882: RM: rust-weedle/0.12.0-2 rust-wasm-bindgen-webidl/0.2.75-1
has caused the Debian Bug report #1007882,
regarding RM: rust-weedle/0.12.0-2 rust-wasm-bindgen-webidl/0.2.75-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.)


-- 
1007882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007882
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: rm

James McCoy and I have been working on updating the rust-nom package from
version 5 to version 7, this is needed to enable ICMP support in sniffglue and
I belive it is also needed to facilitate packaging of alacritty.

In addition to the rust-nom package (which is currently version 5.x in testing
and version 7.x in unstable) there is a rust-nom-4 package providing version
4.x and a rust-nom-3 package providing version 3.x. It would be possible to
introduce a rust-nom-5 package as well but I don't think it's justifiable to
introduce yet another version at this time.

All but one of the reverse (build-)dependencies of nom 5.x have been ported to
nom 7.x, either by new upstream versions or by patching. That leaves
rust-weedle. rust-weedle has a single reverse (build-)dependency
rust-wasm-bindgen-webidl, neither of them are currently used by any applications
in Debian.

The version of rust-weedle currently in testing is the latest upstream version
and depends on nom 5.x. I tried patching it to use nom 7.x but failed to do
so, I also filed a bug report upstream but got no response. 

I then decided to try patching rust-weedle to use nom 4.x since that would at
least avoid introducing yet another version of nom to the archive. I did so
by reverting the upstream commit porting it from 4.x to 5.x. The tests passed
and I uploaded it as rust-weedle 0.12.0-2.

Unfortunately after uploading it I discovered that the autopkgtest for
rust-wasm-bindgen-webidl failed and it became clear that my upload of
rust-weedle had caused an API break. I attempted to try and adjust the
patch to avoid the API break but was not successful, I don't think the version
with the API break can be considered fit for release.

At that point I filed bug 1007026 to give the rest of the rust team a chance
to comment on the issue and said that if noone objected I planned to file
a removal request with the release team.

I now request that rust-weedle and rust-wasm-bindgen-webidl are removed from
testing so that rust-nom and it's reverse dependencies can migrate.

-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi Peter,

On 18-03-2022 00:27, plugwash wrote:

I now request that rust-weedle and rust-wasm-bindgen-webidl are removed from
testing so that rust-nom and it's reverse dependencies can migrate.


Hint added.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: