Matthias Klose wrote:
> thanks, and please could you make checking the source package for
> bug reports a part of your daily practice?
If it's a bug in the source package like e.g. a FTBFS, of course I do.
But not if the bug is clearly in binary package.
Regards, Axel
--
,''`.
On 12.12.2015 23:19, Axel Beckert wrote:
Control: affects -1 + python-pkg-resources
Matthias Klose wrote:
I always appreciate your sensibility for checking the BTS before
filing bug reports.
I _did_. There was none. And actually, there is now none again:
https://bugs.debian.org/cgi-bin/pkgrep
Control: affects -1 + python-pkg-resources
Matthias Klose wrote:
> I always appreciate your sensibility for checking the BTS before
> filing bug reports.
I _did_. There was none. And actually, there is now none again:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=python-pkg-resources;dist=uns
Control: severity -1 important
Control: forcemerge 807681 -1
I always appreciate your sensibility for checking the BTS before filing bug
reports.
Package: python-pkg-resources
Version: 18.7.1-1
Severity: grave
Control: affects -1 git-buildpackage whatmaps
Justification: renders package unusable
Since the recent upgrade of packages built from the python2.7 source
package, multiple unrelated programs bail out with the following
backtraces, at
5 matches
Mail list logo