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

Bug#911059: marked as done (reportbug: Behaviour on lowercase and UPPERCASE package names is inconsistent)

Your message dated Sat, 24 Nov 2018 13:04:57 -0500
with message-id <CAB4XWXz4CBRrQkjPks_hpU8==Te+tsBR6cCPiqjZV+uHJFMRQw@mail.gmail.com>
and subject line Re: Bug#911059: reportbug: Behaviour on lowercase and UPPERCASE package names is inconsistent
has caused the Debian Bug report #911059,
regarding reportbug: Behaviour on lowercase and UPPERCASE package names is inconsistent
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.)


-- 
911059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911059
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: reportbug
Version: 7.1.7+deb9u2
Severity: normal
Control: found -1 reportbug/7.5.0

reportbug does rather not work consistently when using UPPERCASE package names, e.g.:

# reportbug -p WNPP
Warning: no reportbug configuration found.  Proceeding in novice mode.
Detected character set: us-ascii
Please change your locale if this is incorrect.

Using 'Daniel Lange <DLange@debian.org>' as your from address.
Getting status for WNPP...
W: Unable to locate package WNPP
No matching source or binary packages.
A package named "WNPP" does not appear to be installed; do you want to search for a similar-looking filename in an installed
package [Y|n|q|?]? 
[..]

vs. the intended behaviour on lowercase "wnpp".

# reportbug -p wnpp

Warning: no reportbug configuration found.  Proceeding in novice mode.
Detected character set: us-ascii
Please change your locale if this is incorrect.

Using 'Daniel Lange <DLange@debian.org>' as your from address.
Will send report to Debian (per lsb_release).
What sort of request is this? (If none of these things mean anything to you, or you are trying to report a bug in an existing
package, please press Enter to exit reportbug.)

1 ITP  This is an `Intent To Package'. Please submit a package description along with copyright and URL in such a report.
2 O    The package has been `Orphaned'. It needs a new maintainer as soon as possible.
3 RFA  This is a `Request for Adoption'. Due to lack of time, resources, interest or something similar, the current maintainer is
       asking for someone else to maintain this package. They will maintain it in the meantime, but perhaps not in the best
       possible way. In short: the package needs a new maintainer.
4 RFH  This is a `Request For Help'. The current maintainer wants to continue to maintain this package, but they need some help
       to do this because their time is limited or the package is quite big and needs several maintainers.
5 RFP  This is a `Request For Package'. You have found an interesting piece of software and would like someone else to maintain
       it for Debian. Please submit a package description along with copyright and URL in such a report.

Choose the request type: 
[..]

Now the Pseudo-package name is WNPP, not wnpp.

Similar problem:

# reportbug -p Reportbug # notice the uppercase R
Warning: no reportbug configuration found.  Proceeding in novice mode.
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Daniel Lange <DLange@debian.org>' as your from address.
Getting status for Reportbug...
Checking for newer versions at madison...
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on Reportbug (source)...
216 bug reports found:

Bugs with severity important
    1) #709862  reportbug: GTK interface crashes on continue from package selection
    2) #711404  reportbug's GTK interface crashes if spelling dictionaries for the current locale are missing
    3) #717563  reportbug: web access thru proxy not available
    4) #848208  GUI segfaults when trying to collect system information  [RESOLVED]
    5) #849124  Reportbug 7.1.1 doesnt start (ValueError: Namespace Vte not available + another error)  [RESOLVED]
    6) #850733  Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"  [RESOLVED]
[..]

vs.

# reportbug -p reportbug # notice the lowercase r
Warning: no reportbug configuration found.  Proceeding in novice mode.
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Daniel Lange <DLange@debian.org>' as your from address.
Getting status for reportbug...
Checking for newer versions at madison...

Your version (7.1.7+deb9u2) of reportbug appears to be out of date.
The following newer release(s) are available in the Debian archive:
  testing: 7.5.0
  unstable: 7.5.0
Do you still want to file a report [y|N|q|?]? 
[..]

Reportbug should do the right thing, regardless of case.
So probably lowercasing package names given before processing.

--- End Message ---
--- Begin Message --- 
On Mon, Oct 15, 2018 at 4:21 AM Daniel Lange <DLange@debian.org> wrote:
> Now the Pseudo-package name is WNPP, not wnpp.

nope: the official list of pseudo-packages is at
https://www.debian.org/Bugs/pseudo-packages and lists `wnpp`,
lowercase.

> # reportbug -p Reportbug # notice the uppercase R
...
> # reportbug -p reportbug # notice the lowercase r

> Reportbug should do the right thing, regardless of case.
> So probably lowercasing package names given before processing.

i dont think that's always correct. we sometimes convert to lowercase
for easier handling, but debian policy mandates lowecase package
names. reportbug is used by other entities too and changing the
behaviour could affect them, so i'd prefer not to mangle with this.

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

--- End Message ---
Reply to: