2012/4/18 Joey Hess
> This bug report remains open only as a request for debootstrap to
> somehow extract and print the actual error message from debootstrap.log
> when the installation of a package fails. Ideally that would be done
> in a form that prevents users from filing bug reports on deboo
Package: debootstrap
Version: 1.0.39
Severity: important
libept upgraded recently its package and it creates an issue with
debootstrap (it fails).
debootstrap loads important priority packages but libept1 and libept1.4.12 both
have
"priority: important" set.
However libept1 is not compatible wit
After analysis, it appears that libept does not generate anymore binary
libept1 but libept1.4.12
However I didn't find where comes from the libept1 dependency with
debootstrap.
libept1 cannot be used anymore as it does not match the libapt-pkg version.
Olivier
--
gpg key id: 4096R/326D8438 (k
Le 4/17/12 3:56 PM, Olivier Sallou a écrit :
> Hi,
> I suddenly face the same error with debootstrap: (sid).
> I made today a complete apt-get upgrade, so I am up-to-date in packages.
>
> debootstrap --arch amd64 --keyring /etc/apt/trusted.gpg sid
> /mnt/deb
I am adding debootstrap.log extract for the issue.
In unpack step I see:
(Reading database ... 6280 files and directories currently installed.)
Unpacking adduser (from .../adduser_3.113+nmu1_all.deb) ...
Unpacking apt (from .../archives/apt_0.9.0_amd64.deb) ...
Unpacking apt-utils (from .../apt-ut
Hi,
I suddenly face the same error with debootstrap: (sid).
I made today a complete apt-get upgrade, so I am up-to-date in packages.
debootstrap --arch amd64 --keyring /etc/apt/trusted.gpg sid
/mnt/debootstrap.21191 ftp://ftp.fr.debian.org/debian
...
I: Configuring aptitude...
I: Configuring libs
6 matches
Mail list logo
