Bug#1074711: rootskel: FTBFS: ln: failed to create symbolic link '/<>/debian/rootskel//etc/mtab': No such file or directory
Source: rootskel Version: 1.136 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240702 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/src/etc' > install -d /<>/debian/rootskel//etc > install -d -m755 /<>/debian/rootskel///run > ln -fs /proc/mounts /<>/debian/rootskel//etc/mtab > install -d -m755 /<>/debian/rootskel///sys > install -d -m755 /<>/debian/rootskel//etc/rcS.d > ln: failed to create symbolic link > '/<>/debian/rootskel//etc/mtab': No such file or directory > make[3]: *** [Makefile:18: install-local] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/07/02/rootskel_1.136_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240702=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1031431: debian-installer-netboot-images: FTBFS: Building 20220917, but bookworm has 20230207, failing the build
Hi, On 17/02/23 at 13:07 +0100, Cyril Brulebois wrote: > Version: 20230217 > > Hi Lucas, > > Lucas Nussbaum (2023-02-17): > > Source: debian-installer-netboot-images > > Version: 20220917+rebuild1 > > Severity: serious > > Justification: FTBFS > > Tags: bookworm sid ftbfs > > User: lu...@debian.org > > Usertags: ftbfs-20230216 ftbfs-bookworm > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > It'd be great to skip debian-installer and debian-installer-netboot-images > for those automated bug reports. The former depends on the contents of the > archive, and we need it to release; it can't be missed. The latter also > depends on the contents of the archive, and goes with the former on each > d-i release. > > Having those bugs filed means having to remember to copy-paste bug numbers, > possibly miss a dinstall or britney run when we're in the thick of it. > > That's not really helping, quite the opposite… OK, I remembered about skipping debian-installer, but wasn't sure about debian-installer-netboot-images Lucas
Bug#1031431: debian-installer-netboot-images: FTBFS: Building 20220917, but bookworm has 20230207, failing the build
Source: debian-installer-netboot-images Version: 20220917+rebuild1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230216 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > if ! ./get-images.sh amd64; then \ > if [ -n "" ]; then \ > echo; echo; echo; \ > echo "Version not found in bookworm, falling back to "; \ > echo; echo; echo; \ > sleep 5; \ > DISTRIBUTION= ./get-images.sh amd64; \ > else \ > echo "Version not found in bookworm, no fallback defined"; \ > exit 1; \ > fi \ > fi > --2023-02-17 01:24:15-- > http://127.0.0.1:12990/debian/dists/bookworm/Release.gpg > Connecting to 127.0.0.1:12990... connected. > HTTP request sent, awaiting response... 200 OK > Length: 1601 (1.6K) [text/plain] > Saving to: ‘/<>/Release.gpg’ > > 0K . 100% 177M=0s > > 2023-02-17 01:24:15 (177 MB/s) - ‘/<>/Release.gpg’ saved > [1601/1601] > > --2023-02-17 01:24:15-- http://127.0.0.1:12990/debian/dists/bookworm/Release > Connecting to 127.0.0.1:12990... connected. > HTTP request sent, awaiting response... 200 OK > Length: 171552 (168K) [text/plain] > Saving to: ‘/<>/Release’ > > 0K .. .. .. .. .. 29% 329M 0s > 50K .. .. .. .. .. 59% 276M 0s >100K .. .. .. .. .. 89% 60.2M 0s >150K .. ...100% > 13.9M=0.002s > > 2023-02-17 01:24:15 (69.1 MB/s) - ‘/<>/Release’ saved > [171552/171552] > > gpgv: Signature made Thu Feb 16 20:13:29 2023 UTC > gpgv:using RSA key 0146DC6D4A0B2914BDED34DB648ACFD622F3D138 > gpgv: Good signature from "Debian Archive Automatic Signing Key (10/buster) > " > gpgv: Signature made Thu Feb 16 20:14:07 2023 UTC > gpgv:using RSA key A7236886F3CCCAAD148A27F80E98404D386FA1D9 > gpgv: Good signature from "Debian Archive Automatic Signing Key (11/bullseye) > " > --2023-02-17 01:24:15-- > http://127.0.0.1:12990/debian/dists/bookworm/main/binary-amd64/Packages.xz > Connecting to 127.0.0.1:12990... connected. > HTTP request sent, awaiting response... 200 OK > Length: 9040064 (8.6M) [text/plain] > Saving to: ‘amd64.Packages.xz’ > > 0K .. .. .. .. .. 0% 191M 0s > 50K .. .. .. .. .. 1% 83.8M 0s >100K .. .. .. .. .. 1% 109M 0s >150K .. .. .. .. .. 2% 21.6M 0s >200K .. .. .. .. .. 2% 51.3M 0s >250K .. .. .. .. .. 3% 110M 0s >300K .. .. .. .. .. 3% 113M 0s >350K .. .. .. .. .. 4% 114M 0s >400K .. .. .. .. .. 5% 100M 0s >450K .. .. .. .. .. 5% 89.4M 0s >500K .. .. .. .. .. 6% 99.9M 0s >550K .. .. .. .. .. 6% 73.4M 0s >600K .. .. .. .. .. 7% 174M 0s >650K .. .. .. .. .. 7% 120M 0s >700K .. .. .. .. .. 8% 133M 0s >750K .. .. .. .. .. 9% 13.4M 0s >800K .. .. .. .. .. 9% 102M 0s >850K .. .. .. .. .. 10% 141M 0s >900K .. .. .. .. .. 10% 106M 0s >950K .. .. .. .. .. 11% 161M 0s > 1000K .. .. .. .. .. 11% 47.5M 0s > 1050K .. .. .. .. .. 12% 132M 0s > 1100K .. .. .. .. .. 13% 23.4M 0s > 1150K .. .. .. .. .. 13% 118M 0s > 1200K .. .. .. .. .. 14% 124M 0s > 1250K .. .. .. .. .. 14% 36.5M 0s > 1300K .. .. .. .. .. 15% 29.8M 0s > 1350K .. .. .. .. .. 15% 110M 0s > 1400K .. .. .. .. .. 16% 101M 0s > 1450K .. .. .. .. .. 16% 92.6M 0s > 1500K .. .. .. .. .. 17% 112M 0s > 1550K .. .. ..
Bug#1026485: debian-installer: FTBFS: Failed to stat - stat (2: No such file or directory)
Source: debian-installer Version: 20220917 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build' > Using generated sources.list.udeb: >deb [trusted=yes] copy:/<>/build/ localudebs/ >deb http://127.0.0.1:12990/debian bookworm main/debian-installer > make[9]: 'sources.list.udeb' is up to date. > Ign:1 copy:/<>/build localudebs/ InRelease > Ign:2 copy:/<>/build localudebs/ Release > Err:3 copy:/<>/build localudebs/ Packages > Failed to stat - stat (2: No such file or directory) > Err:3 copy:/<>/build localudebs/ Packages > Failed to stat - stat (2: No such file or directory) > Err:3 copy:/<>/build localudebs/ Packages > Failed to stat - stat (2: No such file or directory) > Get:3 copy:/<>/build localudebs/ Packages [20 B] > Get:4 http://127.0.0.1:12990/debian bookworm InRelease [164 kB] > Get:5 http://127.0.0.1:12990/debian bookworm/main/debian-installer amd64 > Packages [51.8 kB] > Fetched 216 kB in 0s (637 kB/s) > Reading package lists... > W: http://127.0.0.1:12990/debian/dists/bookworm/InRelease: Key is stored in > legacy trusted.gpg keyring (/usr/share/keyrings/debian-archive-keyring.gpg), > see the DEPRECATION section in apt-key(8) for details. > Reading package lists... > Building dependency tree... > dh_testroot > dh_testroot: warning: dh_testroot must be called from the source root > get-packages udeb acpi-modules-5.19.0-1-amd64-di alsa-utils-udeb anna > archdetect bogl-bterm-udeb brltty-udeb busybox-udeb ca-certificates-udeb > cdebconf-gtk-terminal cdebconf-gtk-udeb cdebconf-newt-terminal > cdebconf-newt-udeb cdebconf-priority cdebconf-text-udeb cdebconf-udeb > cdrom-checker cdrom-core-modules-5.19.0-1-amd64-di cdrom-detect > cdrom-retriever console-setup-linux-fonts-udeb console-setup-pc-ekmap > console-setup-udeb di-utils di-utils-reboot di-utils-shell di-utils-terminfo > env-preseed espeak-ng-data-udeb espeakup-udeb fat-modules-5.19.0-1-amd64-di > fb-modules-5.19.0-1-amd64-di file-preseed > firewire-core-modules-5.19.0-1-amd64-di fontconfig-udeb fonts-android-udeb > fonts-dejavu-mono-udeb fonts-dejavu-udeb fonts-farsiweb-udeb > fonts-freefont-udeb fonts-khmeros-udeb fonts-knda-udeb fonts-lao-udeb > fonts-lohit-guru-udeb fonts-mlym-udeb fonts-noto-hinted-udeb > fonts-sil-abyssinica-udeb fonts-sil-padauk-udeb fonts-taml-udeb > fonts-telu-udeb fonts-thai-tlwg-udeb fonts-tibetan-machine-udeb > fonts-ukij-uyghur-udeb gtk2-engines-udeb haveged-udeb hw-detect > initrd-preseed input-modules-5.19.0-1-amd64-di installation-locale > isofs-modules-5.19.0-1-amd64-di kbd-udeb kernel-image-5.19.0-1-amd64-di > kmod-udeb libacl1-udeb libasound2-udeb libatk-adaptor-udeb > libatk-bridge-2.0-0-udeb libatk1.0-udeb libatspi0-udeb libblkid1-udeb > libbsd0-udeb libc6-udeb libcairo2-udeb libcap2-udeb libcrypt1-udeb > libcrypto3-udeb libdatrie1-udeb libdbus-1-3-udeb libdebconfclient0-udeb > libdebian-installer4-udeb libdrm2-udeb libevdev2-udeb libexpat1-udeb > libffi8-udeb libfontenc1-udeb libfreetype6-udeb libfribidi0-udeb > libgail18-udeb libgdk-pixbuf-2.0-0-udeb libglib2.0-udeb libgtk2.0-0-udeb > libharfbuzz0-udeb libinput10-udeb libkmod2-udeb libmd0-udeb libmtdev1-udeb > libncursesw6-udeb libnewt0.52-udeb libpango1.0-udeb libpci3-udeb > libpciaccess0-udeb libpcre2-8-0-udeb libpixman-1-0-udeb libpng16-16-udeb > libreadline8-udeb libselinux1-udeb libslang2-udeb libssl3-udeb > libtextwrap1-udeb libthai-data-udeb libthai0-udeb libtinfo6-udeb > libudev1-udeb libuuid1-udeb libvte9-udeb libx11-6-udeb libxau6-udeb > libxcb1-udeb libxcursor1-udeb libxcvt0-udeb libxdmcp6-udeb libxext6-udeb > libxfixes3-udeb libxfont2-udeb libxft2-udeb libxi6-udeb libxinerama1-udeb > libxkbfile1-udeb libxrandr2-udeb libxrender1-udeb libxshmfence1-udeb > load-cdrom localechooser lowmemcheck main-menu media-retriever mountmedia > mouse-modules-5.19.0-1-amd64-di nano-udeb pata-modules-5.19.0-1-amd64-di > pciutils-udeb pcmcia-modules-5.19.0-1-amd64-di > pcmcia-storage-modules-5.19.0-1-amd64-di pcmciautils-udeb preseed-common > readline-common-udeb rescue-check rootskel rootskel-gtk > sata-modules-5.19.0-1-amd64-di save-logs scsi-core-modules-5.19.0-1-amd64-di > scsi-modules-5.19.0-1-amd64-di serial-modules-5.19.0-1-amd64-di > sound-modules-5.19.0-1-amd64-di speakup-modules-5.19.0-1-amd64-di udev-udeb > udpkg usb-modules-5.19.0-1-amd64-di usb-storage-modules-5.19.0-1-amd64-di > util-linux-udeb wget-udeb wireless-regdb-udeb x11-xkb-utils-udeb > xkb-data-udeb xserver-xorg-core-udeb xserver-xorg-input-libinput-udeb > xserver-xorg-video-fbdev-udeb zlib1g-udeb > make[10]: 'sources.list.udeb' is up to date. > Ign:1 copy:/<>/build localudebs/ InRelease > Ign:2 copy:/<>/build localudebs/ Release > Err:3 copy:/<>/build localudebs/ Packages > Failed to stat - stat (2:
Bug#1007037: debian-installer: please consider upgrading to 3.0 source format
Source: debian-installer Version: 20210731+deb11u2 Severity: wishlist Tags: bookworm sid Usertags: format1.0 format1.0-kp-nv Dear maintainer, This package is among the few (1.9%) that still use source format 1.0 in bookworm. Please upgrade it to source format 3.0, as (1) this format has many advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2) this contributes to standardization of packaging practices. Please note that this is also a sign that the packaging of this software could maybe benefit from a refresh. It might be a good opportunity to look at other aspects as well. This mass bug filing was discussed on debian-devel@: https://lists.debian.org/debian-devel/2022/03/msg00074.html Thanks Lucas
Bug#999249: discover: missing required debian/rules targets build-arch and/or build-indep
Source: discover Version: 2.1.2-9 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas
Bug#997541: oldsys-preseed: FTBFS: Running test misc/hostname... ./do-test: line 17: tempfile: command not found
Source: oldsys-preseed Version: 3.22 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd tests && ./runtests > Running test arm/dns323-dhcp... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/dns323-dhcp.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/dns323-static... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/dns323-static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/kuroboxpro_dhcp... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/kuroboxpro_dhcp.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/kuroboxpro_static... ./do-test: line 17: tempfile: command > not found > diff: missing operand after 'arm/kuroboxpro_static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/lspro_dhcp... ./do-test: line 17: tempfile: command not found > diff: missing operand after 'arm/lspro_dhcp.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/lspro_static... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/lspro_static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/mv2120_dhcp... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/mv2120_dhcp.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/mv2120_static... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/mv2120_static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2... ./do-test: line 17: tempfile: command not found > diff: missing operand after 'arm/nslu2.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_invalid_hostname... ./do-test: line 17: tempfile: > command not found > diff: missing operand after 'arm/nslu2_invalid_hostname.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_static... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/nslu2_static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_static_no_dns... ./do-test: line 17: tempfile: command > not found > diff: missing operand after 'arm/nslu2_static_no_dns.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_static_no_gw... ./do-test: line 17: tempfile: command > not found > diff: missing operand after 'arm/nslu2_static_no_gw.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_static_no_ip... ./do-test: line 17: tempfile: command > not found > diff: missing operand after 'arm/nslu2_static_no_ip.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/nslu2_uninitialized... ./do-test: line 17: tempfile: command > not found > diff: missing operand after 'arm/nslu2_uninitialized.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/qnap_dhcp... ./do-test: line 17: tempfile: command not found > diff: missing operand after 'arm/qnap_dhcp.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/qnap_static... ./do-test: line 17: tempfile: command not > found > diff: missing operand after 'arm/qnap_static.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/qnap_static_unreachable_gateway... ./do-test: line 17: > tempfile: command not found > diff: missing operand after 'arm/qnap_static_unreachable_gateway.preseed' > diff: Try 'diff --help' for more information. > ./runtests: line 10: d-i: command not found > not ok > Running test arm/thecus_dhcp... ./do-test: line 17: tempfile: command not > found > diff: missing operand after
Bug#997110: console-setup: FTBFS: ./kbdcompiler: ckbcomp failed
Source: console-setup Version: 1.205 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Compiling compact keymaps for amiga... > Compiling compact keymaps for ataritt... > Compiling compact keymaps for pc105... > Compiling compact keymaps for sun4... > ./kbdcompiler: ckbcomp failed > make: *** [debian/rules:68: /<>/sun4.ekmap] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/console-setup_1.205_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Re: Tentative summary of the AMD/ATI/NVidia issue (was: Finding a tentative bullseye release date)
On 25/04/21 at 11:04 +0200, Cyril Brulebois wrote: > > B) In the installer, detect that firmware-amd-graphics or > > firmware-misc-nonfree should be installed, and either install it (?), > > or redirect the user to the unofficial installer that includes them. > > That could be achieved for an installer that has non-free enabled, > provided the proposal by Ben gets implemented, then consumed on the d-i > side. For reference, I think Ben's proposal is: https://lists.debian.org/debian-boot/2021/03/msg00088.html Lucas
Re: [AMD/ATI graphics] Missing firmware not declared / kernel modules not included in initrd
On 25/04/21 at 10:26 +0200, Holger Wansing wrote: > Hi, > > Holger Wansing wrote (Sun, 25 Apr 2021 10:08:32 +0200): > > >I don't understand: > > >does this mean that the issue that you reported in > > >https://lists.debian.org/debian-boot/2020/12/msg00026.html can be > > >considered fixed? And that the situation improved between buster and > > >bullseye? > > > > For this (old) hardware: yes, seems so. > > > > However, we have several user reports, that not installed firmware leads to > > problems > > like black or garbled screen. > > To be more clear: > > The main point of my report at > https://lists.debian.org/debian-boot/2020/12/msg00026.html ist: > the installer is - per design - unable to detect, that the hardware needs > firmware to be installed. > > And this situation did not change! > > The bullseye installation yesterday did not install the firmware package. > > What seems to have changed is: > GNOME seems to work (at least on this hardware !!!), even without the > firmware > installed. > > (Also: Look at the other reports I quoted in my mail above for more user > cases.) But aren't all those other reports from either the buster installer, or from installers for releases before buster? Lucas
Re: [AMD/ATI graphics] Missing firmware not declared / kernel modules not included in initrd
On 24/04/21 at 23:27 +0200, Holger Wansing wrote: > Results: > > Installing Buster (with GNOME DE) lead to a system failing to start X, > system hangs on the console, latest entry is "Starting GNOME Display Manager". > The needed firmware package (firmware-amd-graphics) was NOT installed. > Installing it makes GNOME UI start fine. > > Installation of Bullseye was basically the same (installation completed > successfully, amd firmware package was NOT installed). > The difference: there was a small delay while starting up (~ 10 sec.), but > after that X and GNOME were starting fine. > > So, on this hardware and with 'radeon' kernel module, everything would be > fine for Bullseye. No need for further action. > (I can deliver installation logs or whatever information, if needed, feel > free to ask.) > However, it's somewhat older hardware with 'radeon' module. > Thus it does not stand for the "amdgpu firmware problem", I fear. I don't understand: does this mean that the issue that you reported in https://lists.debian.org/debian-boot/2020/12/msg00026.html can be considered fixed? And that the situation improved between buster and bullseye? Lucas
Re: [AMD/ATI graphics] Missing firmware not declared / kernel modules not included in initrd
Hi Holger, On 04/12/20 at 22:08 +0100, Holger Wansing wrote: > Hi all, > > after a test installation on an IBM thinkpad with radeon RV515/M52 graphics, > I ended up with a "broken" system (Gnome login screen was not shown, instead > there was the "boot-up screen" showing the starting services like > > [ OK ] Started User Login Management. > [ OK ] Started Bluetooth service. > ... > [ OK ] Started Network Manager. > ... > [ OK ] Started Accounts Service. > ... > [ OK ] Reached target sound card. >Starting GNOME Display Manager ... > > and somewhere at that point it hangs. > No login possible from there! > > > Problem was the missing firmware for the Radeon graphics card (package > "firmware-amd-graphics"), similar to several other bugreports we had here in > the > past: Would you be in a position to check a debian 10 install on the same hardware, and fetch the dmesg output and /var/log/Xorg.0.log after installation, as well as the list of installed packages (to understand if firmware packages were installed somehow)? And then maybe do the same with the bullseye RC1 image? Also can you confirm that just switching to another console and installing the firmware package there was enough to fix the issue? I don't understand whether this is a regression from Debian 10 or not. For example, > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931436 was about the RC2 for the buster installer. Thanks Lucas
Tentative summary of the AMD/ATI/NVidia issue (was: Finding a tentative bullseye release date)
On 24/04/21 at 09:25 +0200, Holger Wansing wrote: > Hi, > > Cyril Brulebois wrote (Fri, 23 Apr 2021 15:13:15 +0200): > > D-I Bullseye RC 1 was published a few hours ago. And at the risk of > > sounding like a broken record: I have *absolutely no guarantee* to > > have a fix or workaround for the amdgpu issue in less than a month, > > that would be tested somewhat. > > > > Can we please *not* release with black screens for AMD users? > > Moreover, it's not just an AMD issue. > We got a confirmation just now on debian-boot, that also NVIDIA users can > get affected by this: > https://lists.debian.org/debian-boot/2021/04/msg00225.html > Some months ago, I have confirmed with that user, that missing firmware > is indeed the issue there! Hi, Disclaimer: I read the "[AMD/ATI graphics] Missing firmware not declared / kernel modules not included in initrd" thread. While my understanding of the issue is not complete, I'm trying to summarize what I undertood so far in the hope that others can jump in and fill in the blanks or correct me. There are graphic cards whose in-kernel drivers require non-free firmwares. Typically AMD/ATI cards that require firmware-amd-graphics[1] to work with the radeon, amdgpu and r128 drivers; or NVIDIA cards that require firmware-misc-nonfree to work with the nouveau driver. [1] https://packages.debian.org/unstable/firmware-amd-graphics With Debian 10, the behaviour was that the installation succeeded without installing firmware-* packages, and then, and the first boot, X would start in a "degraded" mode (using, for example, the vesa driver). The user would generally then install the firmware package (or, in the case of NVidia, switch to the proprietary drivers). With Debian 11, the installation also succeeds, but then at first boot, X fails to work correctly. What happens here is unclear: reports vary between "black screen" (but does the system works if the user switches to console mode?), "garbled screen", "system crash" (but maybe the user did not notice that the system works in console mode). It looks like the three open paths for resolution are: A) understand and restore the behaviour from Debian 10, that is, get X to work in a degraded mode after installation. How it worked with Debian 10 (and why it doesn't with Debian 11) is unknown. B) In the installer, detect that firmware-amd-graphics or firmware-misc-nonfree should be installed, and either install it (?), or redirect the user to the unofficial installer that includes them. C) Do nothing and document this in the release notes The main blocking factor for progress seems to be that not enough people have both hardware that is not supported (laptops/desktops with AMD or NVidia graphic cards), and the knowledge and time to investigate this. Lucas
Bug#980607: netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args]
Source: netcfg Version: 1.169 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -c -W -Wall -Werror -DNDEBUG -DNETCFG_VERSION="\"1.169\"" -I. -DWIRELESS > -DNM -Os -fomit-frame-pointer -o test/test_inet_mton.o test/test_inet_mton.c > In file included from test/srunner.h:1, > from test/test_inet_mton.c:1: > test/test_inet_mton.c: In function ‘test_inet_mton_v4_24_fn’: > test/test_inet_mton.c:12:15: error: too many arguments for format > [-Werror=format-extra-args] >12 | "Mask address wasn't 24 bits"); > | ^ > test/test_inet_mton.c: In function ‘test_inet_mton_v4_22_fn’: > test/test_inet_mton.c:24:15: error: too many arguments for format > [-Werror=format-extra-args] >24 | "Mask address wasn't 22 bits"); > | ^ > test/test_inet_mton.c: In function ‘test_inet_mton_v6_64_fn’: > test/test_inet_mton.c:38:15: error: too many arguments for format > [-Werror=format-extra-args] >38 | "Mask address wasn't 64 bits"); > | ^ > test/test_inet_mton.c: In function ‘test_inet_mton_v6_60_fn’: > test/test_inet_mton.c:52:15: error: too many arguments for format > [-Werror=format-extra-args] >52 | "Mask address wasn't 60 bits"); > | ^ > cc1: all warnings being treated as errors > make[1]: *** [Makefile:60: test/test_inet_mton.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/netcfg_1.169_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not found
Source: console-setup Version: 1.195 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf > >/<>/Fonts/bdf/legacy16a-double.bdf > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx > >/<>/man/bdf2psf.1.txt > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf > >/<>/Fonts/bdf/legacy16b-double.bdf > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx > >/<>/man/console-setup.5.txt > /bin/sh: 1: col: not found > /bin/sh: 1: col: not found > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf > >/<>/Fonts/bdf/legacy16c-double.bdf > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf > >/<>/Fonts/bdf/legacy16d-double.bdf > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf > >/<>/Fonts/bdf/legacy16e-double.bdf > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf > >/<>/Fonts/bdf/legacy16f-double.bdf > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error > 127 The full build log is available from: http://qa-logs.debian.net/2020/06/20/console-setup_1.195_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#923483: flash-kernel: db entry for Banana Pi M2 Berry
Package: flash-kernel Version: 3.97 Severity: wishlist Hi, I'm trying to run Debian on a Banana Pi M2 Berry. Here is a DB entry, confirmed to work: Machine: Banana Pi M2 Berry Kernel-Flavors: armmp armmp-lpae Boot-Script-Path: /boot/boot.scr DTB-Id: sun8i-v40-bananapi-m2-berry.dtb U-Boot-Script-Name: bootscr.sunxi Required-Packages: u-boot-tools Thanks Lucas -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.61 pn devio ii initramfs-tools0.130 ii linux-base 4.5 pn mtd-utils ii ucf3.0036 Versions of packages flash-kernel recommends: ii u-boot-tools 2016.11+dfsg1-4 flash-kernel suggests no packages.
Bug#919982: apt-setup: preseeded installation hangs at "Use a network mirror?"
On 21/01/19 at 10:55 +0100, Lucas Nussbaum wrote: > Package: apt-setup > Severity: normal > > Hi, > > We use d-i weekly images[1] to create Debian testing system images. Our > installation process is fully automated with preseeding. > > The installation process hangs on the apt-setup/use_mirror question (see > screenshot). It did not with d-i alpha 4. > > See attached log and preseeding file. > > - Lucas Hi, After further investigations, it seems that the bug is related to: > Jan 21 08:02:09 kernel: [0.00] Command line: > BOOT_IMAGE=/install.amd/vmlinuz vga=788 initrd=/install.amd/initrd.gz --- > quiet preseed/url=http://10.0.2.2:8000/preseed.cfg auto locale=en_US > kbd-chooser/method=us netcfg/get_hostname=localhost > netcfg/get_domain=localdomain fb=false debconf/frontend=noninteractive > console-setup/ask_detect=false console-keymaps-at/keymap=us > keyboard-configuration/xkb-keymap=us Which is a bit stupid: instead of passing many parameters on the cmdline, we could just use 'auto url=' Still, there's a regression in d-i, when installing with install preseed/url=https://blop.info/pub/preseed.cfg With debian-buster-DI-alpha4-amd64-netinst.iso, the installer asks questions about language, location, keyboard, hostname, and domainname, but then proceeds until the end of the installation (which is expected). With the current debian-testing-amd64-netinst.iso, the installer asks the same questions, proceeds with the installation, but then, near the end, asks the 'Use a network mirror?' question as described in this bug. Lucas
Bug#860695: win32-loader: FTBFS on i386: segmentation fault
Source: win32-loader Version: 0.8.2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): > make[3]: Entering directory '/<>/l10n' > gcc -DTEXTDOMAINDIR=\"/<>/l10n/locale\" win32-loader.c -o > win32-loader > xgettext --msgid-bugs-address=win32-loa...@packages.debian.org > --from-code=utf-8 -ctranslate --keyword=_ win32-loader.sh win32-loader.c -o > po/messages.pot > mkdir -p templates locale/ar/LC_MESSAGES > msgmerge -U po/ar.po po/messages.pot > done. > msgfmt -c --statistics -o locale/ar/LC_MESSAGES/win32-loader.mo po/ar.po > 66 translated messages. > LANGUAGE=ar ./win32-loader.sh > templates/ar.nsh > mkdir -p templates locale/be/LC_MESSAGES > msgmerge -U po/be.po po/messages.pot > done. > msgfmt -c --statistics -o locale/be/LC_MESSAGES/win32-loader.mo po/be.po > po/be.po:9: warning: header field 'Language' still has the initial default > value > 66 translated messages. > LANGUAGE=be ./win32-loader.sh > templates/be.nsh > mkdir -p templates locale/bg/LC_MESSAGES > msgmerge -U po/bg.po po/messages.pot > ... done. > msgfmt -c --statistics -o locale/bg/LC_MESSAGES/win32-loader.mo po/bg.po > 66 translated messages. > LANGUAGE=bg ./win32-loader.sh > templates/bg.nsh > mkdir -p templates locale/bs/LC_MESSAGES > msgmerge -U po/bs.po po/messages.pot > done. > msgfmt -c --statistics -o locale/bs/LC_MESSAGES/win32-loader.mo po/bs.po > 66 translated messages. > LANGUAGE=bs ./win32-loader.sh > templates/bs.nsh > mkdir -p templates locale/ca/LC_MESSAGES > msgmerge -U po/ca.po po/messages.pot > done. > msgfmt -c --statistics -o locale/ca/LC_MESSAGES/win32-loader.mo po/ca.po > 66 translated messages. > LANGUAGE=ca ./win32-loader.sh > templates/ca.nsh > mkdir -p templates locale/cs/LC_MESSAGES > msgmerge -U po/cs.po po/messages.pot > done. > msgfmt -c --statistics -o locale/cs/LC_MESSAGES/win32-loader.mo po/cs.po > 66 translated messages. > LANGUAGE=cs ./win32-loader.sh > templates/cs.nsh > mkdir -p templates locale/da/LC_MESSAGES > msgmerge -U po/da.po po/messages.pot > done. > msgfmt -c --statistics -o locale/da/LC_MESSAGES/win32-loader.mo po/da.po > 66 translated messages. > LANGUAGE=da ./win32-loader.sh > templates/da.nsh > mkdir -p templates locale/de/LC_MESSAGES > msgmerge -U po/de.po po/messages.pot > ... done. > msgfmt -c --statistics -o locale/de/LC_MESSAGES/win32-loader.mo po/de.po > po/de.po:8: warning: header field 'Language' still has the initial default > value > 66 translated messages. > LANGUAGE=de ./win32-loader.sh > templates/de.nsh > mkdir -p templates locale/el/LC_MESSAGES > msgmerge -U po/el.po po/messages.pot > done. > msgfmt -c --statistics -o locale/el/LC_MESSAGES/win32-loader.mo po/el.po > 66 translated messages. > LANGUAGE=el ./win32-loader.sh > templates/el.nsh > mkdir -p templates > LANGUAGE=C ./win32-loader.sh > templates/en.nsh > mkdir -p templates locale/eo/LC_MESSAGES > msgmerge -U po/eo.po po/messages.pot > done. > msgfmt -c --statistics -o locale/eo/LC_MESSAGES/win32-loader.mo po/eo.po > 66 translated messages. > LANGUAGE=eo ./win32-loader.sh > templates/eo.nsh > mkdir -p templates locale/es/LC_MESSAGES > msgmerge -U po/es.po po/messages.pot > done. > msgfmt -c --statistics -o locale/es/LC_MESSAGES/win32-loader.mo po/es.po > po/es.po:36: warning: header field 'Language' still has the initial default > value > 66 translated messages. > LANGUAGE=es ./win32-loader.sh > templates/es.nsh > mkdir -p templates locale/eu/LC_MESSAGES > msgmerge -U po/eu.po po/messages.pot > done. > msgfmt -c --statistics -o locale/eu/LC_MESSAGES/win32-loader.mo po/eu.po > 43 translated messages, 13 fuzzy translations, 10 untranslated messages. > LANGUAGE=eu ./win32-loader.sh > templates/eu.nsh > mkdir -p templates locale/fa/LC_MESSAGES > msgmerge -U po/fa.po po/messages.pot > done. > msgfmt -c --statistics -o locale/fa/LC_MESSAGES/win32-loader.mo po/fa.po > 66 translated messages. > LANGUAGE=fa ./win32-loader.sh > templates/fa.nsh >
Bug#837004: installation-locale: FTBFS: no output file produced because warnings were issued
Source: installation-locale Version: 1.6 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160906 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > localedef -i C.UTF-8.in -f "UTF-8" ./C.UTF-8 > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_CTYPE' > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_NUMERIC' > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_TIME' > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_COLLATE' > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_MONETARY' > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_MESSAGES' > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_PAPER' > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_NAME' > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_ADDRESS' > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_TELEPHONE' > LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category > `LC_IDENTIFICATION' > no output file produced because warnings were issued > Makefile:4: recipe for target 'C.UTF-8' failed > make[1]: *** [C.UTF-8] Error 4 The full build log is available from: http://people.debian.org/~lucas/logs/2016/09/06/installation-locale_1.6_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#700292: netcfg/choose_interface=auto fails to select eth1 when eth0 has no link
On 31/08/16 at 13:15 +0800, Paul Wise wrote: > On Wed, 2016-08-31 at 07:10 +0200, Lucas Nussbaum wrote: > > > Well, FTR it's exactly the kind of hardware I was using yesterday > > (with the current jessie installer) > > Did you try with the cable plugged into only eth1? Yes. > If so, I guess this is fixed. signature.asc Description: PGP signature
Bug#700292: netcfg/choose_interface=auto fails to select eth1 when eth0 has no link
On 31/08/16 at 11:26 +0800, Paul Wise wrote: > On Tue, 2016-08-30 at 17:48 +0200, Lucas Nussbaum wrote: > > > What you put in the preseeding file has no effect for network > > detection (at least in the case where this file is fetched over the > > network). > > The preseeding I was talking about was added to the ISO IIRC. > > > So it's possible that this bug could be closed, but I wasn't the > > original submitter. Paul, do you have a way to check again? > > The libvirt infra I used to test this has gone away so I don't have an > easy way to check that right now. Any hardware with 2 NICs and the > cable plugged into only one of them would work for testing too but I > don't have any local access to such hardware for testing right now. Well, FTR it's exactly the kind of hardware I was using yesterday (with the current jessie installer) Lucas
Bug#700292: netcfg/choose_interface=auto fails to select eth1 when eth0 has no link
On 24/04/15 at 09:38 +0200, Lucas Nussbaum wrote:
> On 18/02/13 at 07:28 +0800, Paul Wise wrote:
> > On Sun, 2013-02-17 at 23:24 +0100, Philipp Kern wrote:
> >
> > > Now I'm not sure why we're checking for a link in netcfg_autoconfig
> > > again without error handling, but why does it try the wrong ifname in
> > > the first place? In the auto selection process we should've picked
> > > one earlier that had a link already in GET_INTERFACE.
> >
> > If you or anyone else needs a way to test this, you can use a libvirt
> > based virtual machine and run this command after setting up the VM:
> >
> > virsh domif-setlink down --persistent
>
> Hi,
>
> I'm hit by this bug. My case is simple: two interfaces, only one with link
> (and
> netcfg correctly detects the link only on one interface, so the expected
> behaviour of "just pick up the interface with the link" would work).
>
> So the known workaround for this bug is:
> Still set:
> d-i netcfg/choose_interface select auto
> add "IPAPPEND 2" in debian-installer/amd64/boot-screens/adtxt.cfg, so
> that it looks like:
>
> label auto
> menu label ^Automated install
> kernel debian-installer/amd64/linux
> append auto=true priority=critical vga=788
> initrd=debian-installer/amd64/initrd.gz --- quiet
> IPAPPEND 2
>
> However, even with that, it doesn't select automatically the bootif interface:
> - I get BOOTIF= in /proc/cmdline
> - the installer detects it (I get the "Found interface eth2 with link-layer
> address )
> - but I still get prompted for the interface
>
> After booting with DEBCONF_DEBUG=developer DEBCONF_DEVELOPER=debug (Cyril
> wasn't sure which one was working), I see that:
> - netcfg/choose_interface gets SET to eth2: Intel Corporation [ rest of
> desc]
> - I see the SUBST netcfg/choose_interface ifchoices eth2: [desc], eth3: [desc]
> - I see the INPUT critical netcfg/choose_interface
>
> So I think that the bottom line is: why did I get prompted by this INPUT since
> netcfg/choose_interface was already SET before? Shouldn't the priority be
> lower
> than critical?
>
> For reference, the code is in netcfg-common.c, in netcfg_get_interface.
> The corresponding code for the input is:
>
> else if (num_interfaces > 1) {
> *numif = num_interfaces;
> /* remove the trailing ", ", which confuses cdebconf */
> ptr[strlen(ptr) - 2] = '\0';
>
> debconf_subst(client, "netcfg/choose_interface", "ifchoices", ptr);
> free(ptr);
>
> asked = (debconf_input(client, "critical", "netcfg/choose_interface")
> == CMD_SUCCESS);
> ret = debconf_go(client);
>
> /* If the question is not asked, honor preseeded interface name.
> * However, if it was preseeded to "auto", or there was no old value,
> * leave it set to defif. */
> if (!asked && strlen(old_selection) && strcmp(old_selection, "auto")
> != 0) {
> debconf_set(client, "netcfg/choose_interface", old_selection);
> }
>
> free(old_selection);
>
> if (ret)
> return ret;
>
> debconf_get(client, "netcfg/choose_interface");
> inter = client->value;
>
> if (!inter)
> netcfg_die(client);
> }
>
>
> I also tried with "d-i netcfg/choose_interface select eth2" and BOOTIF in
> /proc/cmdline, and I still get prompted.
>
> With "d-i netcfg/choose_interface select eth2" and no BOOTIF in /proc/cmdline,
> I also get prompted! So this is more severely broken than I thought.
After encountering this problem again, I understood something that
wasn't clear to me before (but is quite obvious when you think about
it).
What you put in the preseeding file has no effect for network detection
(at least in the case where this file is fetched over the network).
For me, setting netcfg/choose_interface=auto on the kernel command-line
(in amd64/boot-screens/adtxt.cfg, in my case) did the trick.
So it's possible that this bug could be closed, but I wasn't the
original submitter. Paul, do you have a way to check again?
Lucas
Bug#700292: netcfg/choose_interface=auto fails to select eth1 when eth0 has no link
On 18/02/13 at 07:28 +0800, Paul Wise wrote:
On Sun, 2013-02-17 at 23:24 +0100, Philipp Kern wrote:
Now I'm not sure why we're checking for a link in netcfg_autoconfig
again without error handling, but why does it try the wrong ifname in
the first place? In the auto selection process we should've picked
one earlier that had a link already in GET_INTERFACE.
If you or anyone else needs a way to test this, you can use a libvirt
based virtual machine and run this command after setting up the VM:
virsh domif-setlink machine mac down --persistent
Hi,
I'm hit by this bug. My case is simple: two interfaces, only one with link (and
netcfg correctly detects the link only on one interface, so the expected
behaviour of just pick up the interface with the link would work).
So the known workaround for this bug is:
Still set:
d-i netcfg/choose_interface select auto
add IPAPPEND 2 in debian-installer/amd64/boot-screens/adtxt.cfg, so
that it looks like:
label auto
menu label ^Automated install
kernel debian-installer/amd64/linux
append auto=true priority=critical vga=788
initrd=debian-installer/amd64/initrd.gz --- quiet
IPAPPEND 2
However, even with that, it doesn't select automatically the bootif interface:
- I get BOOTIF=mac in /proc/cmdline
- the installer detects it (I get the Found interface eth2 with link-layer
address mac)
- but I still get prompted for the interface
After booting with DEBCONF_DEBUG=developer DEBCONF_DEVELOPER=debug (Cyril
wasn't sure which one was working), I see that:
- netcfg/choose_interface gets SET to eth2: Intel Corporation [ rest of
desc]
- I see the SUBST netcfg/choose_interface ifchoices eth2: [desc], eth3: [desc]
- I see the INPUT critical netcfg/choose_interface
So I think that the bottom line is: why did I get prompted by this INPUT since
netcfg/choose_interface was already SET before? Shouldn't the priority be lower
than critical?
For reference, the code is in netcfg-common.c, in netcfg_get_interface.
The corresponding code for the input is:
else if (num_interfaces 1) {
*numif = num_interfaces;
/* remove the trailing , , which confuses cdebconf */
ptr[strlen(ptr) - 2] = '\0';
debconf_subst(client, netcfg/choose_interface, ifchoices, ptr);
free(ptr);
asked = (debconf_input(client, critical, netcfg/choose_interface)
== CMD_SUCCESS);
ret = debconf_go(client);
/* If the question is not asked, honor preseeded interface name.
* However, if it was preseeded to auto, or there was no old value,
* leave it set to defif. */
if (!asked strlen(old_selection) strcmp(old_selection, auto) !=
0) {
debconf_set(client, netcfg/choose_interface, old_selection);
}
free(old_selection);
if (ret)
return ret;
debconf_get(client, netcfg/choose_interface);
inter = client-value;
if (!inter)
netcfg_die(client);
}
I also tried with d-i netcfg/choose_interface select eth2 and BOOTIF in
/proc/cmdline, and I still get prompted.
With d-i netcfg/choose_interface select eth2 and no BOOTIF in /proc/cmdline,
I also get prompted! So this is more severely broken than I thought.
Lucas
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150424073828.ga11...@xanadu.blop.info
Re: Unable to preseed keyboard layout
(Replying to a super-old email) On 03/12/12 at 12:57 +0100, Samuel Thibault wrote: Antoine Pitrou, le Mon 03 Dec 2012 11:55:49 +0100, a écrit : d-i keyboard-configuration/xkb-keymap select fr(oss) fr(oss) is not a selectable option. Only fr(latin9) is. Also, simply use d-i keymap select fr(latin9) as documented in the installation manual. Where is that documented, actually? https://www.debian.org/releases/jessie/amd64/apbs04.html.en#preseed-l10n says: # Keyboard selection. d-i keyboard-configuration/xkb-keymap select us # d-i keyboard-configuration/toggle select No toggling Same for http://www.debian.org/releases/jessie/example-preseed.txt Also, is there a way to find the list of valid values? d-i keyboard-configuration/xkb-keymap select fr did not work for me. I haven't tried fr(latin9). I guess it would have worked... Thanks, Lucas -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150423164333.ga21...@xanadu.blop.info
status of d-i development -- call for help?
Hi, It has been suggested to me that the work on d-i could use more manpower. AFAIK, the current active maintainer is Cyril Brulebois, but I've been told that he could use some help for the jessie cycle. :) Cyril, am I correct? I think that something that is worth trying is to write a call for help with a job description, outlining what are the required skills to contribute to d-i. What usually works great is to provide a micro-task that allows prospective contributors to check that they have the basic skills required (that also has the advantage to detect people that don't have the required skills, and avoid losing time mentoring them). For example, adding one's name in an 'About' box. We could then ensure that that job description gets wide coverage (dpn, dda bits). Could someone write such a job description, or help me write it? I'm totally clueless about d-i development, so I would need some help, unfortunately. Lucas -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130815220035.ga17...@xanadu.blop.info
Bug#713129: ttf-cjk-compact: FTBFS: build-dependency not installable: libgettext-ruby1.8
Source: ttf-cjk-compact Version: 1.20 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install ttf-cjk-compact build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-ttf-cjk-compact-dummy : Depends: libgettext-ruby1.8 but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/ttf-cjk-compact_1.20_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130622114222.ga23...@xanadu.blop.info
Bug#684834: installation-guide: FTBFS: Error: unknown language 'el'
Source: installation-guide Version: 20110122 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120814 qa-ftbfs Justification: FTBFS in wheezy on amd64 Hi, During a rebuild of all packages in *wheezy*, your package failed to build on amd64. Relevant part: debian/rules build rm -f build-stamp rm -rf /«PKGBUILDDIR»/debian/manual set -e cd build \ for arch in i386 amd64 armel hppa ia64 mips mipsel powerpc s390 sparc kfreebsd-i386 kfreebsd-amd64 ; do \ official_build=1 manual_release=lenny \ architectures=$arch languages=en ca cs de el es fi fr it ja pt ru sv vi zh_CN \ destination=/«PKGBUILDDIR»/debian/manual/$arch noarchdir=1 \ ./build.sh ; \ done Generating integrated XML files and POT files Building list of entities... Converting XML files to UTF-8... Merging XML files per 'chapter'... Language: en Architecture: i386 Info: creating temporary profiled .xml file... Info: creating .html files... Writing build.out/html/pr01.html for preface Writing build.out/html/ch01s01.html for sect1(what-is-debian) Writing build.out/html/ch01s02.html for sect1(what-is-linux) Writing build.out/html/ch01s03.html for sect1(what-is-debian-linux) Writing build.out/html/ch01s04.html for sect1(what-is-debian-kfreebsd) Writing build.out/html/ch01s05.html for sect1(getting-newest-inst) Writing build.out/html/ch01s06.html for sect1(getting-newest-doc) Writing build.out/html/ch01s07.html for sect1(doc-organization) Writing build.out/html/ch01s08.html for sect1 Writing build.out/html/ch01.html for chapter(welcome) Writing build.out/html/ch02s01.html for sect1(hardware-supported) Writing build.out/html/ch02s02.html for sect1(hardware-firmware) Writing build.out/html/ch02s03.html for sect1 Writing build.out/html/ch02s04.html for sect1(installation-media) Writing build.out/html/ch02s05.html for sect1(memory-disk-requirements) Writing build.out/html/ch02.html for chapter(hardware-req) Writing build.out/html/ch03s01.html for sect1(install-overview) Writing build.out/html/ch03s02.html for sect1(backup) Writing build.out/html/ch03s03.html for sect1(needed-info) Writing build.out/html/ch03s04.html for sect1(minimum-hardware-reqts) Writing build.out/html/ch03s05.html for sect1(non-debian-partitioning) Writing build.out/html/ch03s06.html for sect1(pre-install-bios-setup) Writing build.out/html/ch03.html for chapter(preparing) Writing build.out/html/ch04s01.html for sect1(official-cdrom) Writing build.out/html/ch04s02.html for sect1(downloading-files) Writing build.out/html/ch04s03.html for sect1(boot-usb-files) Writing build.out/html/ch04s04.html for sect1(boot-drive-files) Writing build.out/html/ch04s05.html for sect1(install-tftp) Writing build.out/html/ch04s06.html for sect1(automatic-install) Writing build.out/html/ch04.html for chapter(install-methods) Writing build.out/html/ch05s01.html for sect1 Writing build.out/html/ch05s02.html for sect1(boot-installer-accessibility) Writing build.out/html/ch05s03.html for sect1(boot-parms) Writing build.out/html/ch05s04.html for sect1(boot-troubleshooting) Writing build.out/html/ch05.html for chapter(boot-installer) Writing build.out/html/ch06s01.html for sect1 Writing build.out/html/ch06s02.html for sect1(modules-list) Writing build.out/html/ch06s03.html for sect1(module-details) Writing build.out/html/ch06s04.html for sect1(loading-firmware) Writing build.out/html/ch06.html for chapter(d-i-intro) Writing build.out/html/ch07s01.html for sect1(base-boot) Writing build.out/html/ch07s02.html for sect1(mount-encrypted-volumes) Writing build.out/html/ch07s03.html for sect1(login) Writing build.out/html/ch07.html for chapter(boot-new) Writing build.out/html/ch08s01.html for sect1(shutdown) Writing build.out/html/ch08s02.html for sect1(unix-intro) Writing build.out/html/ch08s03.html for sect1(debian-orientation) Writing build.out/html/ch08s04.html for sect1(further-reading) Writing build.out/html/ch08s05.html for sect1(mail-setup) Writing build.out/html/ch08s06.html for sect1(kernel-baking) Writing build.out/html/ch08s07.html for sect1(rescue) Writing build.out/html/ch08.html for chapter(post-install) Writing build.out/html/apas01.html for sect1(howto-preliminaries) Writing build.out/html/apas02.html for sect1(howto-getting-images) Writing build.out/html/apas03.html for sect1(howto-installation) Writing build.out/html/apas04.html for sect1(howto-installation-report) Writing build.out/html/apas05.html for sect1(howto-installation-finally) Writing build.out/html/apa.html for appendix(installation-howto) Writing build.out/html/apbs01.html for sect1(preseed-intro) Writing build.out/html/apbs02.html for sect1(preseed-using) Writing build.out/html/apbs03.html for sect1(preseed-creating) Writing build.out/html/apbs04.html for sect1(preseed-contents) Writing build.out/html/apbs05.html for sect1(preseed-advanced)
Bug#666616: installation-guide: FTBFS: build-dependency not installable: ko.tex-base
Source: installation-guide Version: 20110122 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120331 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install installation-guide build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-installation-guide-dummy : Depends: ko.tex-base but it is not going to be installed E: Broken packages The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/31/installation-guide_20110122_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120331193533.ga7...@xanadu.blop.info
Bug#639057: rootskel: FTBFS: /usr/lib/klibc/include/linux/posix_types.h:47:29: fatal error: asm/posix_types.h: No such file or directory
Source: rootskel Version: 1.97 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110822 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[2]: Entering directory `/build/rootskel-soNXDW/rootskel-1.97/src-bootfloppy' klcc -Os -Wall -shared init.c -o init In file included from /usr/lib/klibc/include/sys/types.h:15:0, from /usr/lib/klibc/include/unistd.h:11, from /usr/lib/klibc/include/stdio.h:11, from init.c:14: /usr/lib/klibc/include/linux/posix_types.h:47:29: fatal error: asm/posix_types.h: No such file or directory compilation terminated. make[2]: *** [init] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/08/22/rootskel_1.97_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110823210105.ga31...@xanadu.blop.info
Re: Bug#385919: bogl: requesting removal
tags 385919 - moreinfo reassign 385919 wnpp retitle 385919 O: bogl -- Ben's Own Graphics Library - graphical terminal thanks On 20/02/11 at 14:18 +0100, Alexander Reichle-Schmehl wrote: tags 385919 + moreinfo thanks Hi! * Lucas Nussbaum lu...@debian.org [110220 08:41]: The bogl package has been orphaned for a long time, and nobody has been willing to take it over. I am therefore requesting its removal from Debian. There are some packages, which would need to be fixed, first: Checking reverse dependencies... # Broken Depends: bterm-unifont: bterm-unifont [alpha amd64 armel hppa i386 ia64 mips mipsel powerpc s390 sparc] # Broken Build-Depends: bterm-unifont: libbogl-dev debian-edu-artwork: libbogl-dev debian-installer: libbogl-dev I'm especially hesistate to break debian-installer ;) OK, I'm turning back the bug to wnpp in the meantime. It would be great to find a solution where d-i doesn't depend on a package orphaned since 2006... Thanks, - Lucas -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110220135650.gb18...@xanadu.blop.info
Bug#587133: usb-discover: FTBFS: Nonexistent build-dependency: discover1-data
Source: usb-discover Version: 1.08 Severity: serious Tags: squeeze sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20100624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ** Using build dependencies supplied by package: Build-Depends: debhelper (= 7.0.0) Build-Depends-Indep: discover1-data ┌──┐ │ Install build dependencies (internal resolver) │ └──┘ Checking for already installed source dependencies... W: Unable to locate package discover1-data debhelper: missing Using default version 7.9.1 discover1-data: missing Checking for source dependency conflicts... E: Couldn't find package discover1-data The full build log is available from: http://people.debian.org/~lucas/logs/2010/06/24/usb-discover_1.08_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100625101541.ga2...@xanadu.blop.info
Bug#584371: win32-loader: FTBFS: Target not specified
Source: win32-loader Version: 0.6.16 Severity: serious Tags: squeeze sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20100602 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[2]: Entering directory `/build/user-win32-loader_0.6.16-amd64-hreEE5/win32-loader-0.6.16' i586-mingw32msvc-gcc -Os plugins/cpuid/cpuid.c plugins/cpuid/plugin.c -Wl,--file-alignment,512 -Werror -D_WIN32_WINNT=0x0500 -L/usr/i586-mingw32msvc/lib/nsis -lpluginapi -shared -o plugins/cpuid/test64.dll i586-mingw32msvc-strip plugins/cpuid/test64.dll i586-mingw32msvc-gcc -Os plugins/systeminfo/systeminfo.c -Wl,--file-alignment,512 -Werror -D_WIN32_WINNT=0x0500 -L/usr/i586-mingw32msvc/lib/nsis -lpluginapi -shared -o plugins/systeminfo/systeminfo.dll i586-mingw32msvc-strip plugins/systeminfo/systeminfo.dll i586-mingw32msvc-gcc -Os plugins/string.c -Wl,--file-alignment,512 -Werror -D_WIN32_WINNT=0x0500 -L/usr/i586-mingw32msvc/lib/nsis -lpluginapi -shared -o plugins/string.dll i586-mingw32msvc-strip plugins/string.dll sed -e s/@VERSION@/0.6.16/g license.in license bash genpif loadlin.pif gunzip -c /usr/lib/loadlin/loadlin.exe.gz loadlin.exe grub-mkimage -o core.img --prefix /win32-loader biosdisk part_msdos part_gpt fat ntfs ntfscomp search linux bsd vbe boot minicmd cat cpuid chain halt help ls reboot Try `grub-mkimage --help' for more information. Target not specified. make[2]: *** [core.img] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2010/06/02/win32-loader_0.6.16_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100603101450.ga19...@xanadu.blop.info
Bug#569389: win32-loader: FTBFS: plugins/cpuid/plugin.c:18:21: error: windows.h: No such file or directory
Source: win32-loader Version: 0.6.13 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20100211 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/build/user-win32-loader_0.6.13-amd64-wy87Ht/win32-loader-0.6.13' i586-mingw32msvc-gcc -Os plugins/cpuid/cpuid.c plugins/cpuid/plugin.c -Wl,--file-alignment,512 -Werror -D_WIN32_WINNT=0x0500 -L/usr/i586-mingw32msvc/lib/nsis -lpluginapi -shared -o plugins/cpuid/test64.dll plugins/cpuid/plugin.c:18:21: error: windows.h: No such file or directory In file included from /usr/lib/gcc/i586-mingw32msvc/4.4.2/../../../../i586-mingw32msvc/include/nsis/pluginapi.h:8, from plugins/cpuid/plugin.c:22: /usr/lib/gcc/i586-mingw32msvc/4.4.2/../../../../i586-mingw32msvc/include/nsis/api.h:37: error: expected declaration specifiers or '...' before '*' token /usr/lib/gcc/i586-mingw32msvc/4.4.2/../../../../i586-mingw32msvc/include/nsis/api.h:37: error: 'UINT_PTR' declared as function returning a function /usr/lib/gcc/i586-mingw32msvc/4.4.2/../../../../i586-mingw32msvc/include/nsis/api.h:66: error: expected declaration specifiers or '...' before 'HWND' plugins/cpuid/plugin.c:25: error: expected ')' before 'hwndParent' plugins/cpuid/plugin.c:31: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'WINAPI' make[1]: *** [plugins/cpuid/test64.dll] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2010/02/11/win32-loader_0.6.13_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562294: cdebconf-entropy: FTBFS: strutl.h:13:37: error: debian-installer/macros.h: No such file or directory
Source: cdebconf-entropy Version: 0.12 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091213 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -Wall -g -O2 -I. -fPIC -o text-plugin-entropy.opic -c text-plugin-entropy.c In file included from text-plugin-entropy.c:25: /usr/include/cdebconf/strutl.h:13:37: error: debian-installer/macros.h: No such file or directory /usr/include/cdebconf/strutl.h:16:19: error: missing binary operator before token ( make[1]: *** [text-plugin-entropy.opic] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/13/cdebconf-entropy_0.12_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560570: console-setup: FTBFS: Couldn't open ckb/rules/xorg.xml
On 12/12/09 at 14:58 +0200, Anton Zinoviev wrote: tags 560570 unreproducible thank you On Fri, Dec 11, 2009 at 09:54:15AM +0100, Lucas Nussbaum wrote: Source: console-setup Version: 1.50 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Can you test this again? Maybe there was something wrong with your build environment? ./xmlreader KeyboardNames.pl Couldn't open ckb/rules/xorg.xml: No such file or directory at ./xmlreader line 67 The file ckb/rules/xorg.xml exists in the source package and it is a static file - nothing removes or changes it. Please post your build log (including dependencies installation) so we can diff it with mine. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560570: console-setup: FTBFS: Couldn't open ckb/rules/xorg.xml
Source: console-setup Version: 1.50 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[2]: Entering directory `/build/user-console-setup_1.50-amd64-s4we6W/console-setup-1.50/Keyboard' rm -f *~ rm -f acm/*.acm.gz rm -rf compose compose.ARMSCII-8.inc compose.CP1251.inc compose.CP1255.inc compose.CP1256.inc compose.GEORGIAN-ACADEMY.inc compose.GEORGIAN-PS.inc compose.IBM1133.inc compose.ISIRI-3342.inc compose.ISO-8859-1.inc compose.ISO-8859-10.inc compose.ISO-8859-11.inc compose.ISO-8859-13.inc compose.ISO-8859-14.inc compose.ISO-8859-15.inc compose.ISO-8859-16.inc compose.ISO-8859-2.inc compose.ISO-8859-3.inc compose.ISO-8859-4.inc compose.ISO-8859-5.inc compose.ISO-8859-6.inc compose.ISO-8859-7.inc compose.ISO-8859-8.inc compose.ISO-8859-9.inc compose.KOI8-R.inc compose.KOI8-U.inc compose.TIS-620.inc compose.VISCII.inc rm -rf keymaps rm -f keymaps.dir names.list rm -f amiga.ekmap.gz ataritt.ekmap.gz macintosh_old.ekmap.gz pc105.ekmap.gz sun4.ekmap.gz sun5.ekmap.gz rm -f MyKeyboardNames.pl ./xmlreader KeyboardNames.pl Couldn't open ckb/rules/xorg.xml: No such file or directory at ./xmlreader line 67 make[2]: *** [maintainer-clean] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/console-setup_1.50_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545648: win32-loader: FTBFS: grub-mkimage: error: cannot stat /usr/lib/grub/i386-pc/pc.mod
ca cs de el en es eu fi fr gl he hr hu it ja ko lt nb nl pl pt
pt_BR ro ru sk sq sv th tr zh_CN zh_TW ; do \
echo Push \${`LANGUAGE=$i ./win32-loader.sh LANG_ENGLISH`} ; \
echo Push \`LANGUAGE=$i ./win32-loader.sh English`\ ; \
done templates/dialog.nsh
make[2]: Leaving directory
`/build/user-win32-loader_0.6.12-amd64-b5oYR9/win32-loader-0.6.12/l10n'
makensis -O/dev/null main.nsi
du -h win32-loader.exe
300K win32-loader.exe
grub-mkimage -o core.img --prefix / biosdisk pc gpt fat ntfs ntfscomp search
linux boot minicmd cat cpuid chain halt help ls reboot
grub-mkimage: error: cannot stat /usr/lib/grub/i386-pc/pc.mod
make[1]: *** [core.img] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2009/09/07/win32-loader_0.6.12_lsid64.buildlog
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536961: win32-loader: FTBFS: grub-mkimage: error: cannot stat /usr/lib/grub/i386-pc/_linux.mod
/ru.nsh templates/sk.nsh templates/sq.nsh
templates/sv.nsh templates/th.nsh templates/tr.nsh templates/zh_CN.nsh
templates/zh_TW.nsh ; do echo ; BEGIN $i ; cat $i ; echo ; END $i ; done
templates/all.nsh
for i in be bg ca cs de el en es eu fi fr gl he hr hu it ja ko lt nb nl pl pt
pt_BR ro ru sk sq sv th tr zh_CN zh_TW ; do \
echo Push \${`LANGUAGE=$i ./win32-loader.sh LANG_ENGLISH`} ; \
echo Push \`LANGUAGE=$i ./win32-loader.sh English`\ ; \
done templates/dialog.nsh
make[2]: Leaving directory
`/build/user-win32-loader_0.6.11-amd64-53XWst/win32-loader-0.6.11/l10n'
makensis -O/dev/null main.nsi
du -h win32-loader.exe
292K win32-loader.exe
grub-mkimage -o core.img --prefix / biosdisk pc gpt fat ntfs ntfscomp search
linux _linux boot cat cpuid _chain chain halt help ls reboot
grub-mkimage: error: cannot stat /usr/lib/grub/i386-pc/_linux.mod
make[1]: *** [core.img] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2009/07/13/win32-loader_0.6.11_lsid64.buildlog
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#501409: tzsetup: FTBFS in lenny: /usr/share/iso-codes/iso_3166.tab: No such file or directory at ./gen-templates
Package: tzsetup Version: 1:0.21 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20081006 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: make[1]: Entering directory `/build/user-tzsetup_0.21-amd64-eOIR8m/tzsetup-0.21' rm -f tzmap make[1]: Leaving directory `/build/user-tzsetup_0.21-amd64-eOIR8m/tzsetup-0.21' dh_clean dpkg-source -b tzsetup-0.21 dpkg-source: info: using source format `1.0' dpkg-source: info: building tzsetup in tzsetup_0.21.tar.gz dpkg-source: warning: missing information for output field Standards-Version dpkg-source: info: building tzsetup in tzsetup_0.21.dsc debian/rules build /usr/bin/make make[1]: Entering directory `/build/user-tzsetup_0.21-amd64-eOIR8m/tzsetup-0.21' ./gen-templates debian/common.templates.in debian/common.templates /usr/share/iso-codes/iso_3166.tab: No such file or directory at ./gen-templates line 13. make[1]: *** [tzmap] Error 2 The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/10/06 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497676: win32-loader: FTBFS in lenny: Nonexistent build-dependency: loadlin
Package: win32-loader Version: 0.6.7 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080903 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: ** Using build dependencies supplied by package: Build-Depends: cdbs, debhelper (= 5), nsis (= 2.25), mingw32, gettext, grub-pc (= 1.95+20080101), grubutil-win32, grub-pc ( 1.96+20080203) | grubutil-win32 (= 1.1-18-2~), loadlin, locales-all, cpio-win32 (= 2.9-11), gzip-win32 Checking for already installed source dependencies... cdbs: missing debhelper: missing Using default version 7.0.15 nsis: missing Using default version 2.37-2 mingw32: missing gettext: missing grub-pc: missing Using default version 1.96+20080724-9 grubutil-win32: missing grub-pc: missing Default version of grub-pc not sufficient, no suitable version found. Skipping for now, maybe there are alternatives. grubutil-win32: missing Using default version 1.1-18-2 loadlin: missing locales-all: missing cpio-win32: missing Using default version 2.9-13 gzip-win32: missing Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... Package loadlin is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package loadlin has no installation candidate The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/09/03 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497675: partconf: FTBFS in lenny: Nonexistent build-dependency: libparted1.7-dev
Package: partconf Version: 1.26 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080903 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: ** Using build dependencies supplied by package: Build-Depends: debhelper ( 5.0.22), libdebconfclient0-dev (= 0.47), libparted1.7-dev (= 1.7.1-1), po-debconf (= 0.5.3), libdebian-installer4-dev (= 0.41) Checking for already installed source dependencies... W: Unable to locate package libparted1.7-dev debhelper: missing Using default version 7.0.15 libdebconfclient0-dev: missing Using default version 0.131 libparted1.7-dev: missing Default version of libparted1.7-dev not sufficient, no suitable version found. Skipping for now, maybe there are alternatives. po-debconf: missing Using default version 1.0.15 libdebian-installer4-dev: missing Using default version 0.58 Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... E: Couldn't find package libparted1.7-dev The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/09/03 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497682: partman-base: FTBFS in lenny: Nonexistent build-dependency: libparted1.7-dev
Package: partman-base Version: 120 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080903 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386. Relevant part: ** Using build dependencies supplied by package: Build-Depends: debhelper (= 4.2.0), po-debconf (= 0.5.0), libparted1.7-dev (= 1.7.1-1) Checking for already installed source dependencies... W: Unable to locate package libparted1.7-dev debhelper: missing Using default version 7.0.15 po-debconf: missing Using default version 1.0.15 libparted1.7-dev: missing Default version of libparted1.7-dev not sufficient, no suitable version found. Skipping for now, maybe there are alternatives. Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... E: Couldn't find package libparted1.7-dev The full build log is available from: http://newpeople.debian.org/~lucas/logs/2008/09/03 It is possible that your package builds fine in sid, but you should make sure that your package also builds fine in lenny before the release. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497675: partconf: FTBFS in lenny: Nonexistent build-dependency: libparted1.7-dev
On 03/09/08 at 18:15 +0300, Martin Michlmayr wrote: * Lucas Nussbaum [EMAIL PROTECTED] [2008-09-03 16:34]: Package: partconf Is there some way you can ignore packages that only build udebs? Those packages will be synced when rc1 is out and then they'll all build again in lenny. it's not really easy to do, but it would be possible if absolutely necessary. I've added this to my TODO list, but probably won't do that for a while, so this might happen again in the future. Will try to be careful when the package name rings a bell, though. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489103: rootskel: FTBFS: open3: exec of /usr/bin/gcc-4.1 [..] failed at /usr/bin/klcc line 138
Package: rootskel Version: 1.62 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080702 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: make[4]: Entering directory `/build/user-rootskel_1.62-amd64-mFBW87/rootskel-1.62/src/var/log' make[4]: Leaving directory `/build/user-rootskel_1.62-amd64-mFBW87/rootskel-1.62/src/var/log' make[3]: Leaving directory `/build/user-rootskel_1.62-amd64-mFBW87/rootskel-1.62/src/var' make[2]: Leaving directory `/build/user-rootskel_1.62-amd64-mFBW87/rootskel-1.62/src' make[2]: Entering directory `/build/user-rootskel_1.62-amd64-mFBW87/rootskel-1.62/src-bootfloppy' klcc -Os -Wall -shared init.c -o init open3: exec of /usr/bin/gcc-4.1 -D__KLIBC__=1 -D__KLIBC_MINOR__=5 -D_BITSIZE=32 -fno-stack-protector -mregparm=3 -D_REGPARM=3 -m32 -nostdinc -iwithprefix include -D__KLIBC__=1 -D__KLIBC_MINOR__=5 -D_BITSIZE=32 -I/usr/lib/klibc/include/arch/i386 -I/usr/lib/klibc/include/bits32 -I/usr/lib/klibc/include -march=i386 -Os -g -fomit-frame-pointer -falign-functions=0 -falign-jumps=0 -falign-loops=0 -Os -Wall -c -o init.o -x c init.c failed at /usr/bin/klcc line 138 make[2]: *** [init] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2008/07/02 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482255: ttf-cjk-compact: FTBFS: Open: Failed to open: /usr/share/fonts/truetype/arphic/uming.ttf
Package: ttf-cjk-compact Version: 1.12 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080520 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now the default on most architectures (even if it's not the case on i386 yet). Consequently, many failures are caused by the switch to gcc 4.3. If you determine that this failure is caused by gcc 4.3, feel free to downgrade this bug to 'important' if your package is only built on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with gcc 4.2). Relevant part: /usr/bin/fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp configure-stamp # Add here commands to clean up after the build process. rm -f tmp/* fonts/* dh_clean dpkg-source -b ttf-cjk-compact-1.12 dpkg-source: info: using source format `1.0' dpkg-source: info: building ttf-cjk-compact in ttf-cjk-compact_1.12.tar.gz dpkg-source: info: building ttf-cjk-compact in ttf-cjk-compact_1.12.dsc debian/rules build dh_testdir # Add here commands to configure the package. touch configure-stamp dh_testdir # Make fonts ./makettf zh /usr/share/fonts/truetype/arphic/uming.ttf embedded bitmap: disable Copyright (c) 2000-2008 by George Williams. Executable based on sources from 16:34 GMT 30-Mar-2008. Library based on sources from 15:57 GMT 30-Mar-2008. The requested file, uming.ttf, does not exist Open: Failed to open: /usr/share/fonts/truetype/arphic/uming.ttf Called from... ./stripttf.ff: line 13 make: *** [build-stamp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2008/05/20 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479913: linux-kernel-di-i386-2.6: FTBFS: Nonexistent build-dependency: linux-image-2.6.24-1-486
Package: linux-kernel-di-i386-2.6 Version: 1.60 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080506 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now the default on most architectures (even if it's not the case on i386 yet). Consequently, many failures are caused by the switch to gcc 4.3. If you determine that this failure is caused by gcc 4.3, feel free to downgrade this bug to 'important' if your package is only built on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with gcc 4.2). Relevant part: ** Using build dependencies supplied by package: Build-Depends: kernel-wedge (= 2.44), linux-image-2.6.24-1-486 [i386] Checking for already installed source dependencies... kernel-wedge: missing Using default version 2.44 linux-image-2.6.24-1-486: missing Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... Package linux-image-2.6.24-1-486 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package linux-image-2.6.24-1-486 has no installation candidate The full build log is available from: http://people.debian.org/~lucas/logs/2008/05/06 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479913: linux-kernel-di-i386-2.6: FTBFS: Nonexistent build-dependency: linux-image-2.6.24-1-486
On 07/05/08 at 12:02 +0200, Frans Pop wrote: Hi Lucas, On Wednesday 07 May 2008, Lucas Nussbaum wrote: During a rebuild of all packages in sid, your package failed to build on i386. I thought we'd agreed that trying to rebuild the linux-kernel-di-*-2.6 and linux-modules-di-*-2.6 packages was rather pointless and that you would exclude them, or at least not report bugs against them? Closing as the cause of this failure is known and not something that needs to be kept track of. Sorry, forgot about that. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | signature.asc Description: Digital signature
Bug#475975: cdebconf-entropy: FTBFS: frontend.h:11:20: error: strutl.h: No such file or directory
Package: cdebconf-entropy Version: 0.6 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080413 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now the default on most architectures (even if it's not the case on i386 yet). Feel free to downgrade this bug to 'important' if your package is only built on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with gcc 4.2). Relevant part: gcc -Wall -g -O2 -I. -fPIC -o newt-plugin-entropy-text.opic -c newt-plugin-entropy-text.c In file included from newt-plugin-entropy-text.c:25: /usr/include/cdebconf/frontend.h:11:20: error: strutl.h: No such file or directory newt-plugin-entropy-text.c: In function 'prepare_window': newt-plugin-entropy-text.c:231: warning: passing argument 1 of 'question_get_field' from incompatible pointer type newt-plugin-entropy-text.c:231: warning: passing argument 2 of 'question_get_field' from incompatible pointer type newt-plugin-entropy-text.c:231: error: too few arguments to function 'question_get_field' newt-plugin-entropy-text.c:232: warning: passing argument 1 of 'question_get_field' from incompatible pointer type newt-plugin-entropy-text.c:232: warning: passing argument 2 of 'question_get_field' from incompatible pointer type newt-plugin-entropy-text.c:232: error: too few arguments to function 'question_get_field' make[1]: *** [newt-plugin-entropy-text.opic] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2008/04/13 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476064: linux-kernel-di-i386-2.6: FTBFS: some modules are in more than one package
Package: linux-kernel-di-i386-2.6 Version: 1.59 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080413 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now the default on most architectures (even if it's not the case on i386 yet). Feel free to downgrade this bug to 'important' if your package is only built on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with gcc 4.2). Relevant part: /usr/bin/fakeroot debian/rules binary kernel-wedge gen-control debian/control dh_testdir dh_testdir dh_clean -k kernel-wedge install-files install -D -m 644 /boot/vmlinuz-2.6.24-1-486 debian/kernel-image-2.6.24-1-486-di/boot/vmlinuz install -D -m 644 /boot/System.map-2.6.24-1-486 debian/kernel-image-2.6.24-1-486-di/boot/System.map kernel-wedge copy-modules 2.6.24-1 486 2.6.24-1-486 kernel-wedge find-dups 2.6.24-1-486 some modules are in more than one package debian/nic-wireless-modules-2.6.24-1-486-di lib/modules/2.6.24-1-486/kernel/lib/crc-itu-t.ko debian/firewire-core-modules-2.6.24-1-486-di lib/modules/2.6.24-1-486/kernel/lib/crc-itu-t.ko command exited with status 1 make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2008/04/13 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#461191: console-setup: FTBFS: ./ckbcomp: instead of } in pt expected };.
Package: console-setup version: 1.20 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080116 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: WARNING: Unknown X keysym 0x010002E1D WARNING: Unknown X keysym 0x010002E1D WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul WARNING: Unknown X keysym Hangul ./ckbcomp: instead of } in pt expected };. ./kbdcompiler: ckbcomp failed make[1]: *** [amiga.ekmap] Error 2 rm amiga.ekmap make[1]: Leaving directory `/build/user/console-setup-1.20/Keyboard' make: *** [main_build] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 The full build log is available from: http://people.debian.org/~lucas/logs/2008/01/16 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460353: linux-kernel-di-i386-2.6: FTBFS: unmet b-dep linux-image-2.6.22-3-486
Package: linux-kernel-di-i386-2.6 version: 1.57 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080111 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Btw, should I report build failures of linux-kernel-di-i386-2.6 and linux-modules-di-i386-2.6, or you don't care about them? I don't mind reporting them when they occur, but if that's just useless for you... Relevant part: ** Using build dependencies supplied by package: Build-Depends: kernel-wedge (= 2.39), linux-image-2.6.22-3-486 [i386] Checking for already installed source dependencies... kernel-wedge: missing Using default version 2.41 linux-image-2.6.22-3-486: missing Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... Package linux-image-2.6.22-3-486 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package linux-image-2.6.22-3-486 has no installation candidate apt-get failed. Package installation failed Trying to reinstall removed packages: Trying to uninstall newly installed packages: Source-dependencies not satisfied; skipping linux-kernel-di-i386-2.6 The full build log is available from: http://people.debian.org/~lucas/logs/2008/01/11 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460382: linux-modules-di-i386-2.6: FTBFS: unmet b-dep loop-aes-modules-2.6.22-3-486
Package: linux-modules-di-i386-2.6 version: 1.08 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080111 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: ** Using build dependencies supplied by package: Build-Depends: kernel-wedge (= 2.38), loop-aes-modules-2.6.22-3-486 [i386], squashfs-modules-2.6.22-3-486 [i386] Checking for already installed source dependencies... W: Unable to locate package loop-aes-modules-2.6.22-3-486 kernel-wedge: missing Using default version 2.41 loop-aes-modules-2.6.22-3-486: missing squashfs-modules-2.6.22-3-486: missing Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... E: Couldn't find package loop-aes-modules-2.6.22-3-486 apt-get failed. Package installation failed Trying to reinstall removed packages: Trying to uninstall newly installed packages: Source-dependencies not satisfied; skipping linux-modules-di-i386-2.6 The full build log is available from: http://people.debian.org/~lucas/logs/2008/01/11 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460389: choose-mirror: FTBFS: 14:52:33 ERROR 404: Not Found.
Package: choose-mirror version: 2.20 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080111 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Seems like your online detection is failing? Relevant part: make[1]: Entering directory `/build/user/choose-mirror-2.20' rm -f choose-mirror choose-mirror.o *~ mirrors_*.h rm -f debian/templates-countries debian/httplist-countries debian/ftplist-countries rm -f demo demo.templates rm -rf debian/iso-codes debian/pobuild if [ $ONLINE != n ]; then \ if wget -nv 'http://cvs.debian.org/*checkout*/webwml/english/mirror/Mirrors.masterlist?rev=HEADcvsroot=webwmlcontent-type=text/plain' -O - Mirrors.masterlist.new \ test -s Mirrors.masterlist.new; then \ mv Mirrors.masterlist.new Mirrors.masterlist; \ else \ rm -f Mirrors.masterlist.new; \ fi; \ fi http://cvs.debian.org/*checkout*/webwml/english/mirror/Mirrors.masterlist?rev=HEADcvsroot=webwmlcontent-type=text/plain: 14:52:33 ERROR 404: Not Found. ./mirrorlist http Mirrors.masterlist Mirrors.masterlist: No such file or directory at ./mirrorlist line 37. make[1]: *** [mirrors_http.h] Error 2 make[1]: Leaving directory `/build/user/choose-mirror-2.20' make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 The full build log is available from: http://people.debian.org/~lucas/logs/2008/01/11 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460389: choose-mirror: FTBFS: 14:52:33 ERROR 404: Not Found.
On 12/01/08 at 20:36 +0100, Frans Pop wrote: On Saturday 12 January 2008, Lucas Nussbaum wrote: Package: choose-mirror Seems like your online detection is failing? It's not set anywhere, so I expect the intention is that the person who does the mass build does an 'export ONLINE=n' if he knows that a network connection is not available and still wants to test building choose-mirror. It worked fine for a long time, and started failing recently... -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453204: installation-guide: FTBFS: Error: build of pdf failed with error code 1
Package: installation-guide version: 20070319 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20071126 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: Writing build.out/html/apds02.html for sect1(tasksel-size-list) Writing build.out/html/apds03.html for sect1(linux-upgrade) Writing build.out/html/apds04.html for sect1(plip) Writing build.out/html/apds05.html for sect1(pppoe) Writing build.out/html/apds06.html for sect1(graphical) Writing build.out/html/apd.html for appendix(random-bits) Writing build.out/html/apes01.html for sect1(about) Writing build.out/html/apes02.html for sect1(contributing) Writing build.out/html/apes03.html for sect1(contributors) Writing build.out/html/apes04.html for sect1(trademarks) Writing build.out/html/ape.html for appendix(administrivia) Writing build.out/html/apf.html for appendix(appendix-gpl) Writing build.out/html/index.html for book Info: creating temporary .tex file... Info: creating temporary .dvi file... Error: build of pdf failed with error code 1 Info: creating temporary .html file... Info: creating .txt file... Warning: The following formats failed to build: pdf make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 The full build log is available from: http://people.debian.org/~lucas/logs/2007/11/26 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443043: ttf-cjk-compact: FTBFS: SyntaxError: invalid syntax
Package: ttf-cjk-compact version: 1.10 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20070917 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: dpkg-source: building ttf-cjk-compact in ttf-cjk-compact_1.10.dsc debian/rules build dh_testdir # Add here commands to configure the package. touch configure-stamp dh_testdir # Make fonts ./makettf zh /usr/share/fonts/truetype/arphic/uming.ttf embedded bitmap: disable Copyright (c) 2000-2007 by George Williams. Executable based on sources from 15:43 31-Aug-2007. File ./stripttf, line 8 if ($argc 4) ^ SyntaxError: invalid syntax make: *** [build-stamp] Error 1 The full build log is available from http://people.debian.org/~lucas/logs/2007/09/17 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408228: cdebconf: uninstallable under some conditions because of dependancy cycle
Package: cdebconf Version: 0.108 Severity: important Usertags: grid5000 piuparts Hi, During a piuparts run over all the packages in etch, I ran into a problem with your package: Reading package lists... Building dependency tree... The following extra packages will be installed: defoma file fontconfig fontconfig-config libatk1.0-0 libcairo-directfb2 libcairo2 libdb4.4 libdebian-installer4 libdirectfb-0.9-25 libexpat1 libfontconfig1 libfreetype6 libgdbm3 libglib2.0-0 libgtk-directfb-2.0-0 libgtk2.0-0 libgtk2.0-common libjpeg62 libmagic1 libnewt0.52 libpango1.0-0 libpango1.0-common libpng12-0 libpopt0 libsysfs2 libtextwrap1 libtiff4 libx11-6 libx11-data libxau6 libxcursor1 libxdmcp6 libxext6 libxfixes3 libxft2 libxi6 libxinerama1 libxrandr2 libxrender1 perl perl-modules ttf-dejavu ucf whiptail x11-common Suggested packages: defoma-doc psfontmgr x-ttcidfont-conf dfontmgr libfreetype6-dev ttf-kochi-gothic ttf-kochi-mincho ttf-thryomanes ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp ttf-arphic-gkai00mp ttf-arphic-bkai00mp libterm-readline-gnu-perl libterm-readline-perl-perl Recommended packages: libft-perl libatk1.0-data libglib2.0-data hicolor-icon-theme libgtk2.0-bin libfribidi0 perl-doc debconf-utils The following NEW packages will be installed: cdebconf defoma file fontconfig fontconfig-config libatk1.0-0 libcairo-directfb2 libcairo2 libdb4.4 libdebian-installer4 libdirectfb-0.9-25 libexpat1 libfontconfig1 libfreetype6 libgdbm3 libglib2.0-0 libgtk-directfb-2.0-0 libgtk2.0-0 libgtk2.0-common libjpeg62 libmagic1 libnewt0.52 libpango1.0-0 libpango1.0-common libpng12-0 libpopt0 libsysfs2 libtextwrap1 libtiff4 libx11-6 libx11-data libxau6 libxcursor1 libxdmcp6 libxext6 libxfixes3 libxft2 libxi6 libxinerama1 libxrandr2 libxrender1 perl perl-modules ttf-dejavu ucf whiptail x11-common 0 upgraded, 47 newly installed, 0 to remove and 0 not upgraded. Need to get 22.6MB of archives. [...] E: Couldn't configure pre-depend x11-common for libxft2, probably a dependency cycle. I could reproduce it outside piuparts. If debconf is not installed, and you try to install cdebconf, you run into a problem: cdebconf depends on libxft2 libxft2 pre-depends on x11-common x11-common pre-depends on debconf | debconf-2.0 For some reason, apt doesn't understand that it can solve this by installing first debconf, then x11-common, then cdebconf... -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395262: Arch: all package FTBFS due to test needing network access - RC?
(Cced the relevant bug report) On 31/10/06 at 23:50 -0500, Anthony DeRobertis wrote: Lucas Nussbaum wrote: Some packages (e.g choose-mirror) fetch a newer version of a file during build if it's possible to fetch that file. I don't think this is RC, since the file is not missing from the package if the network is not available. In general, I strongly suspect that fetching updated source during build is RC due to a violation of the Social Contract: the source we are shipping intentionally does not correspond to the binary package. I'm not sure if the above applies to choose-mirror. In particular, if the file shipped in the binary is its own source, then it doesn't. However, I'd still say it's bad idea, and a bug (maybe even RC). Some more general reasons (not all necessarily apply to choose-mirror) * changes to the package are not reflected in the changelog * random network or remote server issues can cause a broken (or worse) build. What happens if the file on the server is corrupted? * builds are no longer repeatable. Different source may even wind up built on different architectures. * the package is much harder to NMU. What should be a spelling fix suddenly becomes a large change (due to the automated source pull), unbeknown to the NMU-er. Same problem for the security team. * the supposedly-signed source package isn't really; it's pulling unsigned source for the build Also, depending on what is being downloaded from the network, there could be security issues. What happens if the server is compromised? While I fully agree with you on all points, I think that this should be discussed post-etch with the general question of in which environment are packages supposed to build ?. There are other similar issue, like: - should packages allow to build as root ? (aegis, bazaar, subversion don't) - should packages build the same if they are built in a minimal debian environment only satisfying their b-dep, and in a system with lots of useless packages installed ? There are RC bugs to fix now ;) -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395262: choose-mirror: requires internet access to build
Package: choose-mirror Version: 2.08 Severity: serious Justification: Requiring network access during build causes lots of problems Hi, Building choose-mirror seems to require network access, since it retrieves a file found on cvs.d.o: if [ $ONLINE != n ]; then \ if wget -nv 'http://cvs.debian.org/*checkout*/webwml/english/mirror/Mirrors.masterlist?rev=HEADcvsroot=webwmlcontent-type=text/plain' -O - Mirrors.masterlist.new \ test -s Mirrors.masterlist.new; then \ mv Mirrors.masterlist.new Mirrors.masterlist; \ else \ rm -f Mirrors.masterlist.new; \ fi; \ fi Quoting from #393900 (against libwww-myspace-perl): Accessing the network during build is bad for these reasons: - It's a privacy concern: without being asked, some information about the system is being sent to a remote host; - It should be possible to autobuild the package on a buildd with no network access. - The test has a high probability to fail lateron because of the referenced host (temporarily) disappearing. Making ONLINE default to n would probably solve the problem. Thank you, -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395262: choose-mirror: requires internet access to build
severity 395262 important tags 395262 + patch thanks (setting severity to important since that's probably what you wanted to do :-) On 25/10/06 at 15:15 -0700, Steve Langasek wrote: tags 395262 important thanks On Wed, Oct 25, 2006 at 11:28:45PM +0200, Lucas Nussbaum wrote: Building choose-mirror seems to require network access, since it retrieves a file found on cvs.d.o: if [ $ONLINE != n ]; then \ if wget -nv 'http://cvs.debian.org/*checkout*/webwml/english/mirror/Mirrors.masterlist?rev=HEADcvsroot=webwmlcontent-type=text/plain' -O - Mirrors.masterlist.new \ test -s Mirrors.masterlist.new; then \ mv Mirrors.masterlist.new Mirrors.masterlist; \ else \ rm -f Mirrors.masterlist.new; \ fi; \ fi This doesn't cause a build failure, because all errors are checked and a failure in wget is ignored. Downgrading accordingly. Agreed, but one problem with wget is that it tries extremly hard to download files (retries 20 times by default, with a 900 seconds timeout each time !). I would recommend changing the wget call so that it runs wget --timeout=60 --tries=2, which would be much more tolerable than waiting for 20*900=18000 seconds. Tagging +patch, even if this is just a workaround to make the situation slightly better. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395262: choose-mirror: requires internet access to build
On 26/10/06 at 01:27 +0200, Frans Pop wrote: On Thursday 26 October 2006 00:27, Lucas Nussbaum wrote: I would recommend changing the wget call so that it runs wget --timeout=60 --tries=2, which would be much more tolerable than waiting for 20*900=18000 seconds. Please explain in which specific case this is needed. AFAICT wget fails immediately if it cannot resolve the host name it is looking for, so AFAICT you are talking about a setup here where an address does resolve, but cannot be accessed. I don't know if we want to make any changes to defaults to allow for that sort of (broken) setup. I run archive-wide tests on a HPC cluster where DNS resolution works, but it's not possible to reach the outside world to protect it from possible DDOS attacks. Building choose-mirror just takes hours on this cluster because of this. I agree that this setup is probably not perfect, but I'm not in a position to change it currently. If you don't want to add a workaround for this now, please at least reopen the bug and set severity to wishlist. I will try to work on it post-etch. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Building debian-installer
Hi, I am working on a custom Ubuntu distribution, making changes both in the installer (I'd like to backport debian's partman) and in the packages list. I've downloaded Ubuntu's branch of debian-cd, but can't understand how to build debian-installer so that debian-cd scripts can use it. The only info I've found is on http://wiki.debian.net/index.cgi?DebianInstallerBuild, which doesn't seem to be up to date. Could somebody point me to relevant documentations, or describe the process of building debian-installer, then building a CD with it ? (Do I need to actually build debian-installer if I'm only backporting debian's partman to ubuntu ?) Thank you, -- Lucas Nussbaum -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
