Re: 2 questions on dpkg and 1 for m68k, thanks
On Thu, Dec 14, 2000 at 05:53:24PM +0800, Zhao Wei <zw@debian.org> spake forth:
> Sometime a ``dpkg -S /usr/bin/fffff'' fails to print out the package
> which owns it. Could you please tell me why this may happen? i.e. what
> is the possible reason(s) for it? Thanks!
Most likely /usr/bin/fffff is an alternative or some other type of symlink
that's not included in the package itself, but rather in its maintainer
scripts and whatnot.
> Another question is, ``dpkg -S /usr/bin/fffff'' is notably slower than
> ``grep /usr/bin/fffff /var/lib/dpkg/info/*.list'', could you tell me the
> possible reason(s) for it, or are they really the same? Thanks again!
AFAIK dpkg first parses /var/lib/dpkg/status and possibly other files before
getting on to the task of checking /var/lib/dpkg/info/*.list...
> Third, (hehe), a little OT here, how could I verify a port specific bug
> is fixed? (I have a m68k bug against older upstream version. I have no
> access/experience/books on m68k. I hope to avoid work through Internet.
> That is slow, and expensive to me. ;-)
I see that you have an @debian.org address; that suggests to me that you've
been accepted as a developer. There are developer machines on various arches
available; see http://db.debian.org/machines.cgi for more info. Another
alternative is to see if anyone on -devel or one of the arch-specific lists
is interested in testing it for you. If someone wants it working on their
favorite arch very much, they'll probably be willing to lend a hand.
--
Mike Markley <mike@markley.org>
PGP: 0xA9592D4D 62 A7 11 E2 23 AD 4F 57 27 05 1A 76 56 92 D5 F6
GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084
"I'm a doctor, not a mechanic."
- Dr. Mccoy, "The Doomsday Machine", when asked if he had heard of the idea
of a doomsday machine.
Reply to: