Even more messages, mentioning purged packages too:
A == Anacron r...@jidanni.org writes:
A /etc/cron.daily/dpkg:
A cp: cannot stat '/var/lib/dpkg/arch': No such file or directory
A tar: alternatives/php: Warning: Cannot stat: No such file or directory
A tar: alternatives/php-cgi-bin: Warning:
Package: dpkg
Version: 1.17.9
Severity: wishlist
Even though they are indeed different, the admin needs to notice the same
message twice
# aptitude safe-update
Preparing to unpack .../alsa-base_1.0.27+1_all.deb ...
Moving obsolete conffile /etc/modprobe.d/alsa-base.conf out of the way...
Moving
Yes. Sorry. Thanks.
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: dpkg
Version: 1.17.10
Severity: wishlist
Idea:
Plain
$ dpkg --verify #with no arguments
is great to find all the problems on the system.
However then one needs dlocate etc. to find out the package
which the problem files belong to.
So there should be a way to get it to tell us at the
Package: dpkg
Version: 1.17.13
How did /var/lib/dpkg/status get corrupted?
$ dpkg -l
dpkg-query: error: parsing file '/var/lib/dpkg/status' near line 26673 package
'libmailutils4':
'(installed' is not allowed for third (status) word in 'Status' field
$ tail /var/log/dpkg.log
2014-09-22
Package: dpkg
Version: 1.17.13
Severity: wishlist
Whenever I encounter e.g.,
Unpacking libgtk-3-common (3.14.0-1) over (3.13.9-2) ...
dpkg-deb (subprocess): decompressing archive member: lzma error: compressed
data is corrupt
dpkg-deb: error: subprocess decompress returned error exit status 2
Package: dpkg
Version: 1.17.13
Severity: wishlist
$ man dpkg|grep -- -C
-C, --audit [package-name...]
$ dpkg --help|grep -- -C
-C|--audit Check for broken package(s).
that should be
-C|--audit [package-name...]Check for broken package(s).
P.S.,
$ dpkg -C
One might argue that it is the user's fault for mistyping file names.
But let's think in term of checksums. Do we proceed further with a .deb
if there is some problem with its checksum? No. Even though the checksum
might refer to 1000 files, only one of which has a problem.
So checking that all
Package: dpkg
Version: 1.18.4
Severity: wishlist
Wouldn't it be best that
# dpkg -i a.deb b.deb c.deb
first be sure that we even have each deb specified on the command line
before proceeding?
OK, and I suppose also check that their checksums are OK.
I mean doing that would never do any harm.
It
I note a full purge and then fresh install of all these programs avoids
the errors.
reopen 825918
thanks
There is actually 1954 error groups on my machine.
A normal user would and should kill the seemingly runaway situation
before hit computer locks up or disks get filled.
# sort /tmp/apt_term_log.txt |uniq -c|sort -nr|head
1954 dpkg-query: package 'imagemagick' is not
> "GJ" == Guillem Jover writes:
GJ> I guess you have tried to install this package many many times? Also
GJ> you are having this problem when installing a package not even from
GJ> unstable but from experimental! This needs fixing in the affected
GJ> package.
Maybe on a
MH> This is the third time you reported this issue.
Sorry. OK I will purge it from all my machines.
I'm turning APT::Get::Fix-Missing back on. One little missing package ruins my
"sneakernet"
offline safe-upgrades, plus I get this message anyway: E: Unable to
fetch some packages; try '-o APT::Get::Fix-Missing=true' to continue
with missing packages.
Package: dpkg
Version: 1.18.7
Severity: grave
Please try installing this version of imagemagick.
Dpkg will enter an infinite loop.
# dpkg -i imagemagick_8%3a6.9.2.10+dfsg-2_all.deb
Selecting previously unselected package imagemagick.
(Reading database ... 148492 files and directories currently
forcemege 825918 825897
thanks
> "DK" == David Kalnischkies writes:
DK> I would strongly advice against setting --fix-missing by default
DK> through. The intend of this mode is really not to be set permanently.
OK I'll turn it off.
DK> Well, that looks like a
>> BTW, you show a very long list of warning messages, did they stop by
>> themselves ? If yes, I'm very curious why.
Oops I'm sorry I neglected to truncate them for my bug post.
No I had to use ^C to stop them.
Dear ow...@bugs.debian.org, can you please truncate some of the repeated
messages I accidentally forgot to truncate.
>> BTW, you show a very long list of warning messages, did they stop by
>> themselves ? If yes, I'm very curious why.
Package: dpkg
Version: 1.18.4
Severity: minor
We read
--forget-old-unavail
Now obsolete and a no-op as dpkg will automatically forget unin-
stalled unavailable packages (since dpkg 1.15.4).
Well my /var/lib/dpkg/status has an odd six line entry
Package:
> "GJ" == Guillem Jover writes:
GJ> Sure, I can agree with the principle above, but currently it might not
GJ> be possible to perform all checks that would be ideal. Those will be
GJ> coming in the future piece by piece.
OK.
Package: dpkg
Version: 1.18.10
Severity: wishlist
dpkg: warning: package not in database at line 5: sphinx-common:all
dpkg: warning: found unknown packages; this might mean the available
database
is outdated, and needs to be updated through a frontend method
This should say which
Package: dpkg
Version: 1.19.2
Severity: minor
File: /usr/share/man/man1/dpkg.1.gz
After:
-r, --remove package...|-a|--pending
Remove an installed package. This removes everything
except conffiles, which may avoid having to
reconfigure the package if
Package: dpkg
Version: 1.19.4
man dpkg says:
--forget-old-unavail
Now obsolete and a no-op as dpkg will automatically forget
uninstalled unavailable packages (since dpkg 1.15.4), but
only those that do not contain user information such as
Package: dpkg
Version: 1.19.4
Severity: minor
How about removing
/var/lib/dpkg/available
/var/lib/dpkg/available-old
or at least zapping them to zero bytes.
They haven't been updated in five years,
and you could save the user four megabytes.
OK maybe they still update on some people's systems,
Package: dpkg
Version: 1.19.4
Severity: minor
File: /usr/share/man/man1/dpkg.1.gz
(In fact the unknown state is the majority state of dpkg -l \*
Anyway, there it is:
$ dpkg -l|sed q
Desired=Unknown/Install/Remove/Purge/Hold
^^^
)
--- dpkg.1 2019-01-23 20:06:39.0 +0800
Package: dpkg
Version: 1.19.6
Severity: wishlist
File: /usr/share/man/man1/dpkg.1.gz
Man page says
--clear-selections
Set the requested state of every non-essential package to
deinstall
(since dpkg 1.13.18). This is intended to be used
immediately
Package: dpkg
Version: 1.20.9
Severity: wishlist
Add a way to run /var/lib/dpkg/info/* scripts with sh -x instead of sh,
without needing to repackage a package just to put an set -x at the top
of a file.
Package: dpkg
Version: 1.20.9
Severity: minor
File: /usr/share/man/man1/dpkg.1.gz
Man page says
--unpack package-file...
Unpack the package, but don't configure it. If --recursive or -R
option is specified, package-file must refer to a directory
instead.
28 matches
Mail list logo