Bug#607365: live-build: unknown location irror-binary/dists/squeeze/Release : --mirror-binary error
Package: live-build
Version: 2.0.9-1
Severity: normal
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages live-build depends on:
ii debootstrap 1.0.26 Bootstrap a basic Debian system
Versions of packages live-build recommends:
ii cpio 2.11-4 GNU cpio -- a program to
manage ar
ii gettext-base 0.18.1.1-3 GNU Internationalization
utilities
ii gnu-fdisk 1.2.4-3+b1 Linux fdisk replacement
based on l
Versions of packages live-build suggests:
ii dosfstools 3.0.9-1 utilities for making and
checking
Hi there! I think there's a bug in the way live-build manages the
--mirror-binary setting.
Here's the messages I get:
marcus89@mattpc:~$ mkdir live
marcus89@mattpc:~$ cd live
marcus89@mattpc:~/live$ lb config --architecture i386 --distribution
squeeze --archive-areas "main contrib non-free" --binary-images usb-hdd
--debian-installer false --language it --bootappend-live "locale=it_IT
keyb=it" --packages "kde-standard icedove gparted kde-l10n-it iceweasel
chromium-browser vlc mplayer knemo openoffice.org-writer
openoffice.org-calc wicd xserver-xorg-video-all alsa-utils
flashplugin-nonfree firmware-ralink nvidia-glx" --mirror-bootstrap
http://ftp.it.debian.org/debian/ --mirror-chroot-security
http://security.debian.org/ -mirror-binary http://ftp.it.debian.org/debian/
P: Considering defaults defined in /etc/live/build.conf
P: Creating config tree
marcus89@mattpc:~/live$ su
Password:
root@mattpc:/home/marcus89/live# lb build
P: Setting up cleanup function
P: Begin caching bootstrap stage...
P: Begin bootstrapping system...
P: If the following stage fails, the most likely cause of the problem is
with your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)...
I: Retrieving Release
E: unknown location irror-binary/dists/squeeze/Release
P: Begin unmounting filesystems...
root@mattpc:/home/marcus89/live# exit
Here's the config/bootstrap configuration file:
# config/bootstrap - options for live-build(7), bootstrap stage
# $LB_ARCHITECTURE: select chroot architecture
# (Default: autodetected)
LB_ARCHITECTURE="i386"
# $LB_BOOTSTRAP_CONFIG: set distribution config directory
# (Default: empty)
LB_BOOTSTRAP_CONFIG=""
# $LB_BOOTSTRAP_INCLUDE: include packages on base
# (Default: empty)
LB_BOOTSTRAP_INCLUDE=""
# $LB_BOOTSTRAP_EXCLUDE: exclude packages on base
# (Default: empty)
LB_BOOTSTRAP_EXCLUDE=""
# $LB_BOOTSTRAP_FLAVOUR: select flavour to use
# (Default: empty)
LB_BOOTSTRAP_FLAVOUR=""
# $LB_BOOTSTRAP_KEYRING: set distribution keyring
# (Default: empty)
LB_BOOTSTRAP_KEYRING=""
# $LB_DISTRIBUTION: select distribution to use
# (Default: squeeze)
LB_DISTRIBUTION="squeeze"
# $LB_MIRROR_BOOTSTRAP: set mirror to bootstrap from
# (Default: irror-binary)
LB_MIRROR_BOOTSTRAP="irror-binary"
# $LB_MIRROR_CHROOT: set mirror to fetch packages from
# (Default: irror-binary)
LB_MIRROR_CHROOT="irror-binary"
# $LB_MIRROR_CHROOT_SECURITY: set security mirror to fetch packages from
# (Default: http://security.debian.org/)
LB_MIRROR_CHROOT_SECURITY="http://security.debian.org/";
# $LB_MIRROR_CHROOT_VOLATILE: set volatile mirror to fetch packages from
# (Default: irror-binary)
LB_MIRROR_CHROOT_VOLATILE="irror-binary"
# $LB_MIRROR_CHROOT_BACKPORTS: set backports mirror to fetch packages from
# (Default: http://backports.debian.org/debian-backports/)
LB_MIRROR_CHROOT_BACKPORTS="http://backports.debian.org/debian-backports/";
# $LB_MIRROR_BINARY: set mirror which ends up in the image
# (Default: http://cdn.debian.net/debian/)
LB_MIRROR_BINARY="http://cdn.debian.net/debian/";
# $LB_MIRROR_BINARY_SECURITY: set security mirror which ends up in the image
# (Default: http://security.debian.org/)
LB_MIRROR_BINARY_SECURITY="http://security.debian.org/";
# $LB_MIRROR_BINARY_VOLATILE: set volatile mirror which ends up in the image
# (Default: http://cdn.debian.net/debian/)
LB_MIRROR_BINARY_VOLATILE="http://cdn.debian.net/debian/";
# $LB_MIRROR_BINARY_BACKPORTS: set backports mirror which ends up in the
image
# (Default: http://backports.debian.org/debian-backports/)
LB_MIRROR_BINARY_BACKPORTS="http://backports.debian.org/debian-backports/";
# $LB_MIRROR_DEBIAN_INSTALLER: set debian-installer mirror
# (Default: irror-binary)
LB_MIRROR_DEBIAN_INSTALLER="irror-binary"
# $LB_ARCHIVE_AREAS: select archive areas to use
# (Default: main contrib non-free)
LB_ARCHIVE_AREAS="main contrib non-free"
On the other hand, when the --mirror-binary setting isn't specified, the
live system builds succesfully:
marcus89@mattpc:~$ mkdir live
marcus89@mattpc:~$ cd live
marcus89@mattpc:~/live$ lb config --architecture i386 --distribution
squeeze --archive-areas "main contrib non-free" --binary-images usb-hdd
--debian-installer false --language it --bootappend-live "locale=it_IT
keyb=it" --packages "kde-standard icedove gparted kde-l10n-it iceweasel
chromium-browser vlc mplayer knemo openoffice.org-writer
openoffice.org-calc wicd xserver-xorg-video-all alsa-utils
flashplugin-nonfree firmware-ralink nvidia-glx" --mirror-bootstrap
http://ftp.it.debian.org/debian/ --mirror-chroot-security
http://security.debian.org/
P: Considering defaults defined in /etc/live/build.conf
P: Creating config tree
marcus89@mattpc:~/live$ su
Password:
root@mattpc:/home/marcus89/live# lb build
P: Setting up cleanup function
P: Begin caching bootstrap stage...
P: Begin bootstrapping system...
P: If the following stage fails, the most likely cause of the problem is
with your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)...
I: Retrieving Release
I: Retrieving Packages
I: Validating Packages
I: Retrieving Packages
I: Validating Packages
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
And so on...
So, according to me, live-build is just deleting the "m" in
"mirror-binary" when it writes it to the configuration files.
Sorry if I'm wasting your time because of this being not a bug, but an
error of mine.
Best regards
Marco Mattiolo
Reply to: