Your message dated Tue, 17 Apr 2018 02:53:57 +
with message-id
and subject line Bug#872577: fixed in debootstrap 1.0.97
has caused the Debian Bug report #872577,
regarding debootstrap: Handle existing /dev
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Tue, 17 Apr 2018 02:53:57 +
with message-id
and subject line Bug#890419: fixed in debootstrap 1.0.97
has caused the Debian Bug report #890419,
regarding [PATCH] Fix boostrapping libvirt LXC containers
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 17 Apr 2018 02:53:57 +
with message-id
and subject line Bug#895466: fixed in debootstrap 1.0.97
has caused the Debian Bug report #895466,
regarding debootstrap 1.0.96 fails due to missing apt-config
to be marked as done.
This means that you claim that the problem has b
Your message dated Tue, 17 Apr 2018 02:53:57 +
with message-id
and subject line Bug#893954: fixed in debootstrap 1.0.97
has caused the Debian Bug report #893954,
regarding debootstrap ignores https mirror setting, just use default http
mirror (i.e. http://deb.debian.org)
to be marked as done.
Your message dated Tue, 17 Apr 2018 02:53:57 +
with message-id
and subject line Bug#872948: fixed in debootstrap 1.0.97
has caused the Debian Bug report #872948,
regarding debootstrap: Debootstrap does not explain what is calls a Debian base
system
to be marked as done.
This means that you c
Your message dated Tue, 17 Apr 2018 02:53:57 +
with message-id
and subject line Bug#872059: fixed in debootstrap 1.0.97
has caused the Debian Bug report #872059,
regarding No longer creates /dev/console.
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 17 Apr 2018 02:53:57 +
with message-id
and subject line Bug#866401: fixed in debootstrap 1.0.97
has caused the Debian Bug report #866401,
regarding Please print proper error message when download fails
to be marked as done.
This means that you claim that the problem ha
Your message dated Tue, 17 Apr 2018 02:53:57 +
with message-id
and subject line Bug#844118: fixed in debootstrap 1.0.97
has caused the Debian Bug report #844118,
regarding debootstrap: APTCACHE for debootstrap
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Tue, 17 Apr 2018 02:53:56 +
with message-id
and subject line Bug#826709: fixed in debootstrap 1.0.97
has caused the Debian Bug report #826709,
regarding debootstrap: fail early when debootstrapping foreign arches whose
binaries cannot be run
to be marked as done.
This mean
Your message dated Tue, 17 Apr 2018 02:53:56 +
with message-id
and subject line Bug#698677: fixed in debootstrap 1.0.97
has caused the Debian Bug report #698677,
regarding debootstrap: 'Release signed by unknown key' should report keyring
used
to be marked as done.
This means that you claim
Hi,
On Wed, 11 Apr 2018 13:06:22 +0200
Clément Hermann wrote:
> I had a look today. It looks good to me, at first glance I had concerns
> (like using hash keys in boolean context without the exists function),
> but everytime I checked further, it looked fine in context. That for the
> perl part.
On Thu, 12 Apr 2018 10:41:57 +0200
Raphael Hertzog wrote:
> 1/ You will put files there but what happens if "apt-get clean" is run in
> a cron job while you are running debootstrap ?
>
> 2/ APT stores files there with a naming policy of its own (for instance
> it adds the epoch to the version) an
12 matches
Mail list logo
