ops
turns out that in both cases they where using a pre-release, namely,
.disk/info contains
Debian GNU/Linux testing Sarge - Official Snapshot i386 Binary-1
(20041121)
:-
turn off red alarm
a.
On Fri, Dec 02, 2005 at 04:09:49PM +0100, debdev wrote:
hi everybody
two friends of mine tried
On 12/4/05, A Mennucc [EMAIL PROTECTED] wrote:
ops
turns out that in both cases they where using a pre-release, namely,
.disk/info contains
Debian GNU/Linux testing Sarge - Official Snapshot i386 Binary-1
(20041121)
Apparently that wasn't obvious.
Shouldn't it be made more clear what
On Sun, Dec 04, 2005 at 12:11:13PM +0100, Olaf van der Spek wrote:
On 12/4/05, A Mennucc [EMAIL PROTECTED] wrote:
Apparently that wasn't obvious.
Shouldn't it be made more clear what version is being used?
yes, I was thinking the same... maybe it would be useful
if the installer snapshots
hi everybody
two friends of mine tried (separately) to install sarge using the
netinst cdrom, and failed
in both cases, the first part of the install was OK, but, after
reboot, when APT was called to upgrade the system, it stopped
claiming:
E: This installation run will require temporarily
* A. Mennucc:
in both cases, the first part of the install was OK, but, after
reboot, when APT was called to upgrade the system, it stopped
claiming:
E: This installation run will require temporarily removing the essential
package e2fsprogs due to a Conflicts/Pre-Depends loop. This is
That day, Florian Weimer wrote
I've seen this as well, but attributed it to an old sarge installer
which used testing instead of sarge (or stable) in the installed
sources.list file. In this case, an update from a pre-sarge testing
snapshot (is installed by the base system) to a current etch
On Fri, Dec 02, 2005 at 06:35:19PM +0100, A Mennucc wrote:
That day, Florian Weimer wrote
By the way, your Mail-Followup-To: header is broken.
thanks;some time ago I decided to abide by
http://larve.net/people/hugo/2000/07/ml-mutt
but I forgot to fix this account
So, shouldn't your
7 matches
Mail list logo
