Re: dpkg was interrupted, you must MANUALLY *what*...????
On Tue, 2 Oct 2001, Wichert Akkerman wrote:
> Which is why there is a command-pipe feature as well.
Oh? Last I was told that was too difficult for you guys to do or something
like that.
vore{jgg}~#zgrep -i command-pipe /usr/doc/dpkg/changelog.Debian.gz
vore{jgg}~#zcat /usr/doc/dpkg/changelog.Debian.gz | head
dpkg (1.9.17) unstable; urgency=low
* updated-rc.d moved to the sysvinit package. Closes: Bug#108887,#109282
-- Wichert Akkerman <wakkerma@debian.org> Wed, 22 Aug 2001 01:24:52 +0200
dpkg (1.9.16) unstable; urgency=low
* Revert architecture-change to dpkg-source from 1.9.11, see ChangeLog
for details.
vore{jgg}~#dpkg --command-pipe
dpkg: unknown option --command-pipe
--status-pipe is in the change log but, it's actually called --status-fd,
and it doesn't really seem to work:
vore{root}~#dpkg --status-fd 1 --configure apt
dpkg: error processing apt (--configure):
package apt is already installed and configured
Errors were encountered while processing:
apt
No mention of the failure to configure on the pipe at all.
Oh well.
Jason
Reply to: