lb build stop after setting up the dctrl-tools package
Hi there! I try to build a wheezy live system from within my wheezy distro and when I run the "lb build" command the build process is stopped after it sets up the dctrl-tools. it doesn't emit any error message. I've attached here ( http://pastebin.com/WunNPBtH) the auto/config and the build.log files and will be happy if someone here can help me figure out what's the problem. Rregards, atar.
lb build error: No space left on device?
[2014-12-04 20:26:23] lb build --version 4.0.3-1 Hmmm. Strange error when I (again) tried to build image. When lb build enters the lb chroot_install-packages install stage at some point of unpacking packages I got no space left on device error. This is strange because I have 483,3 Gb free space lest so should be enough. And yes I am sure its this partition. User permissions are also fine (anyway I build as root). Important part of log in attachment. Any advices? I already tried with --hdd-size "3" and --hdd-size "auto" Same effect. [2014-12-04 19:57:10] lb chroot_install-packages install --verbose P: Begin installing packages (install pass)... Reading package lists... Building dependency tree... Reading state information... apt-utils is already the newest version. mawk is already the newest version. The following extra packages will be installed: aspell (0.60.7~20110707-1) aspell-en (7.1-0-1) [...] xserver-xorg-video-voodoo (1.2.4-2+b3) xterm (278-4) Suggested packages: openssh-client (6.0p1-4+deb7u1) app-install-data (2012.06.16.1) [...] touchfreeze () xfonts-cyrillic (1.0.3) Recommended packages: libpam-ck-connector (0.4.6-4~bpo70+1) fakeroot (1.18.4-2) linux-headers-686-pae (3.16+62~bpo70+1) linux-headers-amd64 (3.16+62~bpo70+1) linux-headers-generic () linux-headers () linux-image () gnupg-agent (2.0.19-2+deb7u2) libc6-dev (2.13-38+deb7u4) libc-dev () [...] xserver-xorg-input-wacom (0.15.0+20120515-2) xserver-xorg-video-geode (2.11.13-3) x11-utils (7.7~1) The following NEW packages will be installed: amd64-microcode (2.20120910-1~bpo70+1) apt-file (2.5.1) [...] xul-ext-wot (20110704-2) zd1211-firmware (2.21.0.0-1) Extracting templates from packages: 4% Extracting templates from packages: 9% Extracting templates from packages: 14% Extracting templates from packages: 19% Extracting templates from packages: 24% Extracting templates from packages: 29% Extracting templates from packages: 34% Extracting templates from packages: 39% Extracting templates from packages: 44% Extracting templates from packages: 49% Extracting templates from packages: 54% Extracting templates from packages: 59% Extracting templates from packages: 64% Extracting templates from packages: 69% Extracting templates from packages: 74% Extracting templates from packages: 79% Extracting templates from packages: 84% Extracting templates from packages: 89% Extracting templates from packages: 94% Extracting templates from packages: 99% Extracting templates from packages: 100% Preconfiguring packages ... [...] Need to get 0 B/450 MB of archives. After this operation, 1209 MB of additional disk space will be used. Selecting previously unselected package bash-completion. (Reading database ... (Reading database ... 5% (Reading database ... 10% [...] (Reading database ... 95% (Reading database ... 100% (Reading database ... 9371 files and directories currently installed.) Unpacking bash-completion (from .../bash-completion_1%3a2.0-1_all.deb) ... Selecting previously unselected package libcap2:i386. [...] Selecting previously unselected package libperl5.14. Unpacking libperl5.14 (from .../libperl5.14_5.14.2-21+deb7u2_i386.deb) ... Selecting previously unselected package pidgin-data. Unpacking pidgin-data (from .../pidgin-data_2.10.10-1~deb7u1_all.deb) ... dpkg: error processing /var/cache/apt/archives/pidgin-data_2.10.10-1~deb7u1_all.deb (--unpack): unable to create `/usr/share/locale/en_AU/LC_MESSAGES/pidgin.mo.dpkg-new' (while processing `./usr/share/locale/en_AU/LC_MESSAGES/pidgin.mo'): No space left on device dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Selecting previously unselected package libzephyr4. Unpacking libzephyr4 (from .../libzephyr4_3.0.2-2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libzephyr4_3.0.2-2_i386.deb (--unpack): unable to create `/usr/share/doc/libzephyr4/copyright.dpkg-new' (while processing `./usr/share/doc/libzephyr4/copyright'): No space left on device Selecting previously unselected package libsasl2-modules:i386. Unpacking libsasl2-modules:i386 (from .../libsasl2-modules_2.1.25.dfsg1-6+deb7u1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libsasl2-modules_2.1.25.dfsg1-6+deb7u1_i386.deb (--unpack): unable to create `/usr/lib/i386-linux-gnu/sasl2/libplain.so.2.0.25.dpkg-new' (while processing `./usr/lib/i386-linux-gnu/sasl2/libplain.so.2.0.25'): No space left on device tar: ./shlibs: Cannot open: No space left on device tar: Exiting with failure status due to previous errors dpkg-deb: error: subprocess tar returned error exit status 2 dpkg: error processing /var/cache/apt/archives/libpurple0_2.10.10-1~deb7u1_i386.deb (--unpack): subprocess dpkg-deb --control returned error exit status 2 Selecting previously unselected package libreoffice-l10n-pl. Unpacking libreoffice-l10n-pl (from .../libreoffice-l10n-pl_1%3a4.3.3~rc2-1~bpo70+1_all.deb) ... dpkg: error proces
Re: lb build stop after setting up the dctrl-tools package
On Thu, Dec 4, 2014 at 9:25 AM, Atar wrote: > Hi there! > > I try to build a wheezy live system from within my wheezy distro and when I > run the "lb build" command the build process is stopped after it sets up the > dctrl-tools. it doesn't emit any error message. I've attached here > (http://pastebin.com/WunNPBtH) the auto/config and the build.log files and > will be happy if someone here can help me figure out what's the problem. > Hi, Sometimes it is really hard to tell why a build process fails. However, I found too many "inconsistencies" in your configuration which could be the reason for your problem. This is usually caused by an unclean build environment. So the logical step would be to run a # lb clean and then try to build again # lb build Or you could also start your build system in a brand new directory (up to you to decide). The inconsistencies I'm talking about are, for example: In your auto/config you have (I copy and paste just part of it): --cache-indices true \ --debug \ BUT your config/common says: config/common: # $LB_CACHE_INDICES: control if downloaded package indices should be cached config/common: # (Default: false) config/common: LB_CACHE_INDICES="false" OR config/common: # $_DEBUG: enable debug config/common: # (Default: false) config/common: #_DEBUG="false" Hence I supposed you were "re-using" your build system after changing some variables. Not a good idea :) Apart from that, in your auto/config, most of your options are already defaults, so you do not need to set them, since live-build already does it for you. These are all defaults: --binary-images iso-hybrid \ --chroot-filesystem squashfs \ --apt-recommends true \ --bootloader syslinux \ [...] --firmware-chroot true \ --updates true \ --backports true \ --system live \ Cleaning your auto scripts is a good idea because it helps you identify your failing cases faster and more easily for you and for everybody else. Also, I noticed you are using live-build 4.0.3-1. I haven't tried to build wheezy with this version, but I guess there should be no problem with that. But again, I haven't tried it. So please, revise your config and start again from a clean state and see if you succeed. Good luck. -- chals www.chalsattack.com ch...@chalsattack.com -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cajrhvaknbbesse3yxh_ikqglwary1vxndmjrykcdodaaxud...@mail.gmail.com
Re: lb build error: No space left on device?
[SOLVED] The problem was not related to live-build. Only because live-build is creating a lot of new files at some point I was just out of free inodes on partition I had 99% used. And then every other program started to act weird. So anyway I cleaned a bit my disk and I am back on level 69% full. Still a bit high but at least I know what is the problem. signature.asc Description: OpenPGP digital signature
Re: lb build error: No space left on device?
[SOLVED] The problem was not related to live-build. Only because live-build is creating a lot of new files at some point I was just out of free inodes on partition I had 99% used. And then every other program started to act weird. So anyway I cleaned a bit my disk and I am back on level 69% full. Still a bit high but at least I know what is the problem. signature.asc Description: OpenPGP digital signature
