Re: Where to file a package-dependency bug?
(...rassum, frassum...)
On 01/02/2006 04:00 PM, Kevin B. McCarty wrote:
The Wanderer wrote:
(In the process, I've discovered that reportbug does not permit a
bug to be reported on a dependency package, but only on the
packages it depends on. This is probably another bug...)
I didn't believe this at first but it's true! I think it's planned
behavior, though. Looking into the reportbug code, you can force
reportbug to submit a bug against the dependency package when the
mode is set to advanced or expert. (This can be changed in
~/.reportbugrc) There are other sneakier ways, too, although the fact
that they work is probably unintentional.
Okay, that does sound intentional enough. (I'm currently wondering how
to get reportbug to re-present its initial "first-run setup" sequence,
since I cancelled out of that because I'd given the wrong command line
and as a result now have no ~/.reportbugrc. Reinstalling doesn't seem to
have done the trick, and neither has removing and installing afresh...)
By the way, while checking into this, I found that the reportbug in
sid actually crashes when one runs "reportbug x-window-system-core".
Just filed as #345699.
It doesn't for me - reportbug version 3.18, the one available in both
etch and sid. This may or may not have something to do with the fact
that I don't have a ~/.reportbugrc and that reportbug therefore defaults
to novice mode.
(As long as I'm here anyway, a minor question on completely another
topic: since I'm told that apt-get and apt-cache are deprecated, what is
the intended successor - in aptitude or similar - to 'apt-cache policy'?
The aptitude man page tells me nothing useful. I find 'apt-cache policy'
more routinely useful than just about any other apt command, and would
be very disturbed to lose its functionality.)
--
The Wanderer
Warning: Simply because I argue an issue does not mean I agree with any
side of it.
Secrecy is the beginning of tyranny.
Reply to: