Comment 5 for bug 910691

Hello Fidel,

On Sat, 07 Jan 2012, Fidel Nadera wrote:
> Excuse me, you have the respect to be clarified before the status change
> continuously?

First I did change it only once, and only to "incomplete" not to
"invalid". Precisely because there's nothing to be done about this
bug report if you don't tell what's broken according to you.

> Paul, Marc has a lot more to your karma, you will not have
> come to suspect that he is right?

Please don't judge on the karma level. I'm one of the upstream maintainers
of dpkg in Debian and I'm perfectly qualified to triage bug reports,
thank you.

> Could not you first ask for clarification?

That's what I did with my message... but instead of providing any
supplementary information, you just got upset and sort of insulted
me (by doubting of my qualifications).

> To me a package that you get by default as "dpkg" should
> not give all those "warnings". Clearly something is wrong there.

Can you start to explain what you were doing that lead to those
warnings?

Some warnings are legitimate in some corner-cases. In particular when you
are setting up a new debian/ubuntu installation with debootstrap or
similar (which I suspect is your case here).

There's just no way to satisfy the pre-dependencies during an initial
installation that doesn't have all the essential packages already
unpacked...

If that's effectively your case, I'm afraid that the only proper answer
is to tag it wontfix.

Cheers,
--
Raphaël Hertzog ◈ Debian Developer

Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/liberation/