[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#157888: marked as done ((c)debconf-copydb: do not handle --config=Foo:bar)



Your message dated Mon, 26 Jun 2017 07:43:51 +0200
with message-id <2flzicvl2w8.fsf@diskless.uio.no>
and subject line Re: Bug#157888: (c)debconf-copydb: do not handle --config=Foo:bar
has caused the Debian Bug report #157888,
regarding (c)debconf-copydb: do not handle --config=Foo:bar
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 owner@bugs.debian.org
immediately.)


-- 
157888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=157888
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cdebconf
Version: 0.22
Severity: important

The cdebconf version of debconf-copydb do not handle the following
example from the manualpage for debconf-copydb in debconf-utils:

  debconf-copydb config_db pipe \
    -c Name:pipe -c Driver:Pipe -c InFd:none

It fails with a message saying -c is an unknown option.

I would like to use this functionality to copy the debconf database
from the debian-installer environment into the target file system
during installation.  I plan to call it like this after making sure
debconf-utils is installed in /target/:

  debconf-copydb config_db pipe \
    -c Name:pipe -c Driver:Pipe -c InFd:none | 
  chroot /target /usr/bin/debconf-copydb pipe configdb \
    -c Name:pipe -c Driver:Pipe


--- End Message ---
--- Begin Message ---
[Cyril Brulebois]
> Wow, the blast from the past. :)

Yeah.  Had a look at the still open bugs I've reported.

> A global grep on debconf-copydb in d-i packages returned two results:

Thank you.  Originially this request was for debconf-copydb in cdebconf
to behave the same way as the one from debconf, and according to the
manual page of debconf-copydb in debconf, but as this was expressed to
not be a goal of cdebconf, I guess that part is not relevant any more.

So I close this bug.  No idea which version to attribute to its
resolution. :)

-- 
Happy hacking
Petter Reinholdtsen

--- End Message ---

Reply to: