Bug#1031924: reportbug: reporting release.debian.org bullseye-pu bug for gtk+3.0 fills in details of wxpython3.0
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: Bug#1031924: reportbug: reporting release.debian.org bullseye-pu bug for gtk+3.0 fills in details of wxpython3.0
- From: Simon McVittie <smcv@debian.org>
- Date: Sat, 25 Feb 2023 11:48:08 +0000
- Message-id: <Y/n1eNrfoJ2rE0FP@momentum.pseudorandom.co.uk>
- Reply-to: Simon McVittie <smcv@debian.org>, 1031924@bugs.debian.org
Package: reportbug
Version: 11.6.0
Severity: normal
Steps to reproduce: I tried to report a bullseye-pu bug for a gtk+3.0
update:
> What sort of request is this?
...
> 3 bullseye-pu bullseye proposed updates requests
> Choose the request type: 3
> Please enter the name of the package: gtk+3.0
> Checking package information...
> Your report will be carbon-copied to the package maintainer.
> Please enter the version of the package: 3.24.24-4+deb11u3
Expected result: a bug report against release.debian.org, cc'd to
gtk+3.0 at packages.debian.org, affecting src:gtk+3.0
Actual result: the template email that opened in mutt had:
> Subject: bullseye-pu: package wxpython3.0/3.24.24-4+deb11u3
...
> X-Debbugs-Cc: wxpython3.0 at packages.debian.org
> Control: affects -1 + src:wxpython3.0
(but with an @ sign in the obvious place)
I tried starting the process of opening a bullseye-pu bug for gtk+3.0
again, and it seems to be consistently misdirected to wxpython3.0.
I also tried going through the motions of opening a bullseye-pu bug
for some arbitrary other source package names, and it looks like this
package name confusion might only be happening for packages with a "+"
in their names, and maybe not always:
dbus-c++ -> dbus-cpp
freefem++ -> (correct)
gtk+2.0 -> librcc
gtk+3.0 -> wxpython3.0
gtk4 -> (correct)
hello -> (correct)
lucene++ -> lucene-solr
smcv
-- Package-specific info:
** Environment settings:
EDITOR="vim"
VISUAL="vim"
DEBEMAIL="smcv@debian.org"
DEBFULLNAME="Simon McVittie"
** /home/smcv/.reportbugrc:
email smcv@debian.org
header "X-Mutt-Fcc: =.lists.debian/"
header "X-Debbugs-Cc: "
mutt
editor vim
mode advanced
no-cc
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 'oldstable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages reportbug depends on:
ii apt 2.5.6
ii python3 3.11.2-1
ii python3-reportbug 11.6.0
ii sensible-utils 0.0.17+nmu1
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail <none>
ii debconf 1.5.82
ii debsums 3.0.2
pn dlocate <none>
ii emacs-bin-common 1:28.2+1-11
ii file 1:5.44-3
ii gnupg 2.2.40-1
ii postfix [mail-transport-agent] 3.7.4-2
pn python3-urwid <none>
pn reportbug-gtk <none>
ii xdg-utils 1.1.3-4.1
Versions of packages python3-reportbug depends on:
ii apt 2.5.6
ii file 1:5.44-3
ii python3 3.11.2-1
ii python3-apt 2.5.3
ii python3-debian 0.1.49
ii python3-debianbts 4.0.1
ii python3-requests 2.28.1+dfsg-1
ii sensible-utils 0.0.17+nmu1
python3-reportbug suggests no packages.
-- no debconf information
Reply to: