Your message dated Thu, 22 Oct 2015 23:17:24 +0200
with message-id <[email protected]>
and subject line Re: [buildd-tools-devel] Bug#802679: please consider adding
--pre-chroot-setup-command
has caused the Debian Bug report #802679,
regarding please consider adding --pre-chroot-setup-command
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.)
--
802679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802679
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: sbuild
Version: 0.66.0-5
Severity: wishlist
Please consider adding an option --pre-chroot-setup-command which can
be used to prepare the chroot after the session was created (the
chroot directory existing) but unchrooted. That way such an option
could be use to copy data from the host file system into the chroot.
This is unfortunately harder than thought, since one would need to
know about the base path of the readied chroot in the host file system
for this to be useful.
Greetings
Marc
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.3-zgws1 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Thu, Oct 22, 2015 at 10:50:55PM +0200, Johannes Schauer wrote:
> Quoting Marc Haber (2015-10-22 16:34:52)
> > Please consider adding an option --pre-chroot-setup-command which can
> > be used to prepare the chroot after the session was created (the
> > chroot directory existing) but unchrooted. That way such an option
> > could be use to copy data from the host file system into the chroot.
> >
> > This is unfortunately harder than thought, since one would need to
> > know about the base path of the readied chroot in the host file system
> > for this to be useful.
>
> is --pre-build-commands not working for your use case for some reason?
It is. It's just confusingly named. Closing.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
--- End Message ---
