Control: found -1 1.0.44
Control: severity serious
I hit this bug yesterday ... and think that this should be RC if
debootstrap/wheezy cannot produce a working chroot environment.
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Hi,
to be more precise abouti my previous message (#44), here is a log of
what happened while running
lb config --architectures i386 ; sudo lb build
http://paste.debian.net/243117/
Interesting lines are 791, 845, 863, 911, 915.
By the way, may this bug be related to #614029 ?
Hi,
i fall on a similar problem while running the following command on
wheezy (you should have live-config live-boot live-build packages
installed):
lb config --architectures i386 ; sudo lb build
I got the same warning (which eventually lead to an error saying that
some packages cannot be
I suggest to add a command rm -f $reldest before the gpg command, as
attached.
Otherwise although it works for debootstrap, however, when using with
Debian live-build, it will enter interactive mode:
=
P: If the following stage fails, the most likely
Hi Michael,
I confirmed that your patch does fix this issue.
Thanks.
Hope this patch will be applied in the next version of debootstrap...
Steven.
--
Steven Shiau steven _at_ nchc org tw steven _at_ stevenshiau org
National Center for High-performance Computing, Taiwan.
http://www.nchc.org.tw
On Sat, Mar 16, 2013 at 11:24:38AM +0100, David Kalnischkies wrote:
Hi Steven,
Hi David and Steven,
could you please try again?
This is very likely a temporary mirror hiccup while it is syncing.
With disabling InRelease we get all the Release vs. Release.gpg mismatches
back, which
On Sun, Mar 17, 2013 at 10:48:14AM +0100, Michael Vogt wrote:
On Sat, Mar 16, 2013 at 11:24:38AM +0100, David Kalnischkies wrote:
[..]
It looks like debootstrap is putting it here, I just re-ran
debootstrap and indeed, the file put there in the chroot is called
_Release but its actually the
Package: apt
Version: 0.9.7.8
Severity: important
Dear Maintainer,
I got an error:
W: GPG error: http://ftp.us.debian.org sid Release: The following signatures
were invalid: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key
(6.0/squeeze) ftpmas...@debian.org
when run apt-get update
Hi Steven,
could you please try again?
This is very likely a temporary mirror hiccup while it is syncing.
With disabling InRelease we get all the Release vs. Release.gpg mismatches
back, which look/are more critical than the (In)Release vs. Packages Co.
mismatches. There are various ideas to
Hi David,
I did a test 10 minutes ago, but still got the same error.
Anything more I can test here?
Thanks.
Steven.
On 03/16/2013 06:24 PM, David Kalnischkies wrote:
Hi Steven,
could you please try again?
This is very likely a temporary mirror hiccup while it is syncing.
With disabling
10 matches
Mail list logo