I finaly have a working system, but I had to switch mirrors twice during
installation.
After the reboot, I still could not use my system. I had to remove
"debian-archive-keyring" (witch is not allowed unless you force it to)
and replace it with the proper one, reinstall apt, etc.
--
To UNSUBS
I did not have this busybox problem (actualy an authentication problem)
a few days ago, using pxe boot, maybe you installed your host like last
week?
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
A
"> Justification: breaks the whole system
No, it doesn't. :-). Hence lowering the severity."
Yeah, you're probably right. Even uni-erlangen will update their repo
one of these days.
And as a result, I would not have a system at all...
It would be a miracle when I was able to break a non-exis
Tried your workaround, no success during the installation proces.
I think just because I was redirected to the base install again. So the
same error occurs again.
After completing the installation, using uni-erlangen.de as a interim
mirror, and rebooting into my now working system, your directiv
debootstrap version 1.0.47 has been in sid for a while now. When can we
expect it in wheezy?
If that is going to take long, I suggest reverting apt (in wheezy) to
the version that masks the problems with debootstrap.
@Pierre Blondeau
Nice, what parameters did you use to get from a simple pxe bo
I have tried the expert mode (google got me there in about 10 secs) but
no luck whatsoever. First of all: Pierre Blondeau says:
>During the system base installation, the installer ask you to choice
your kernel version.
That implies that you get that far. When I submitted this bug, I did
inde
6 matches
Mail list logo
