Your message dated Mon, 22 Feb 2010 19:35:15 +0100
with message-id <[email protected]>
and subject line Package removed from Debian unstable
has caused the Debian Bug report #465944,
regarding dfsbuild fails with message (appended)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
465944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465944
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dfsbuild
Version: etch
Severity: important
dfsbuild 0.99.3 failed to run
installed dfsbuild afresh, tried running it, got this:
================
r...@blather:~# dfsbuild -c /etc/dfsbuild/dfs.cfg -w /files/dfsbuild
[dfs/INFO] Welcome to dfsbuild. Image architecture: "i386"
[dfs/INFO] Using working directory /files/dfsbuild
[dfs/INFO] Using library directory /usr/lib/dfsbuild
[dfs/INFO] Running.
[dfs/INFO] Mirroring process starting.
[dfs/INFO] Running cdebootstrap for amd64
E: Couldn't download Release.gpg!
[MissingH.Cmd.safeSystem/WARNING] Command cdebootstrap
["-a","amd64","-q","-d","stable","/files/dfsbuild/target","http://amd64.debian.net/debian";]
failed; exit
code 1
[dfs/CRITICAL] Exception: user error (Command cdebootstrap
["-a","amd64","-q","-d","stable","/files/dfsbuild/target","http://amd64.debian.net/debian";]
failed; exit code 1)
dfsbuild: user error (Command cdebootstrap
["-a","amd64","-q","-d","stable","/files/dfsbuild/target","http://amd64.debian.net/debian";]
failed; exit code 1)
========================
In addition, note that:
1) I do not have an AMD64 processor, yet that seems to be assumed in the
configfile.
Running it with the "-a i386" option did not help; same message
2) the kernel version info in the configfile is hardcoded, and does not
match mine - though this didn't come up yet for me
W.r.t #2, shouldn't it be possible to look at, oh, /boot and pick a vmlinuz
that actually exists, during installation or runtime?
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-486
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
--- End Message ---
--- Begin Message ---
Version: 1.0.2.0+rm
Package removed from Debian unstable: http://bugs.debian.org/570272
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
