Your message dated Tue, 28 Mar 2017 07:28:44 +0200
with message-id <[email protected]>
and subject line Re: Bug#775065: dpkg --configure -a results in "Hangup" after
first package
has caused the Debian Bug report #775065,
regarding dpkg --configure -a results in "Hangup" after first package
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
775065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775065
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.17.23
Hi,
I have been away from Debian development for over a year due to some RL
issues. I booted my Sid box and did apt-get update and then upgrade, and
everything went wrong. Full story (badly told) is at
http://forums.debian.net/viewtopic.php?f=5&t=119834
The issue I have now is that whenever I try to use apt-get I am told
"dpkg was interrupted, you must manually run 'dpkg --configure -a' to
correct the problem". Running this as root results in
Setting up cups-daemon (1.7.5-10) ...
Hangup
... without that package being configured, nor any others.
If this is not a bug in dpkg, please could someone tell me how to go
about diagnosing and correcting it? I need to be able to finish
installing and configuring the ~55 half-done packages so that I can get
my system working again. At the moment it doesn't boot properly and
drops me into emergency mode. I cannot run openssh-server or reportbug.
Thanks in advance for any help, and apologies for (mis)using the BTS in
desperation. Google tells me that nobody else has reported this set of
issues anywhere.
CC
--- End Message ---
--- Begin Message ---
Am 12.01.2015 um 21:49 schrieb Chris Carr:
> On Sun, 2015-01-11 at 21:02 +0100, Michael Biebl wrote:
>> Ok, so this sounds like this is specific to systemd emergency mode.
>> Assuming systemd boots properly for you now, it would be interesting to
>> know, if dpkg now works properly as well when booted into a regular mode.
>
> I'm not sure exactly what you mean by "a regular mode", but at the
> moment I can only boot fully using sysvinit, and dpkg works then. With
> systemd I can boot only into an emergency shell, and I don't know
> whether dpkg is still broken because there is no further configuration
> for it to do! apt-get update and apt-get upgrade worked just now under
> systemd in emergency mode, upgrading the splendidly-named libhogweed2
> and libnettle4.
Looking at this old bug report, I tried to reproduce the issue by
installing packages in emergency mode. This worked just fine (for both
v215 and v232). I'm closing this bug report.
Chris, if you still run this problem, that dpkg receives SIGHUP in
emergency mode, please file a new bug report or let us know which
version you tried it with, so we can reopen this one.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
