Processed: tagging 763695, reassign 763695 to keyboard-configuration, affects 763695 ..., usertagging 763695
Processing commands for cont...@bugs.debian.org: tags 763695 + help Bug #763695 [console-setup] console-setup is slowest part of boot, not fast as setupcon manpage tells us Added tag(s) help. reassign 763695 keyboard-configuration console-setup/1.113 Bug #763695 [console-setup] console-setup is slowest part of boot, not fast as setupcon manpage tells us Bug reassigned from package 'console-setup' to 'keyboard-configuration'. No longer marked as found in versions console-setup/1.113. Ignoring request to alter fixed versions of bug #763695 to the same values previously set Bug #763695 [keyboard-configuration] console-setup is slowest part of boot, not fast as setupcon manpage tells us Marked as found in versions console-setup/1.113. affects 763695 + console-setup systemd Bug #763695 [keyboard-configuration] console-setup is slowest part of boot, not fast as setupcon manpage tells us Added indication that 763695 affects console-setup and systemd user pkg-systemd-maintain...@lists.alioth.debian.org Setting user to pkg-systemd-maintain...@lists.alioth.debian.org (was naes...@gmail.com). usertags 763695 + systemd-units There were no usertags set. Usertags are now: systemd-units. thanks Stopping processing here. Please contact me if you need assistance. -- 763695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.142956301614593.transcr...@bugs.debian.org
Bug#764982: Backports when the danger is contrib and non-free
Op 20-04-15 om 22:19 schreef Geert Stappers: Op 20-04-15 om 09:39 schreef Turbo Fredriksson: Besides, we had this exact argument for weeks (months) about contrib and non-free 'in the day'. Eventually, _that_ (amongst others) won the argument - it's not an official part of Debian GNU/Linux! I had a closer look at /etc/apt/sources.list of a recent installed machine. And sadly discovered that 'contrib' and 'non-free' were enabled ... I have installed with RC1 and with RC2, but I cannot remember that I have seen that! Maybe you have used a nightly build? I am interested who did this when you are correct. Enabling non-free and contrib in sources.list is a very stupid idea because Debian is about DFSG software and non-free is not DFSG, and contrib needs non-DFSG software. I don't think this was a diskussion, this was maybe somebody who don't know Debian. Or somebody who does not care about free software, and wants to provocate a bit. But backports main is DFSG software and an official part of Debian. Or an official Debian service, like Turbo prefers. With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- 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/553568d9.5080...@vandervlis.nl
Processing of oldsys-preseed_3.16_i386.changes
oldsys-preseed_3.16_i386.changes uploaded successfully to ftp-master.debian.org along with the files: oldsys-preseed_3.16.dsc oldsys-preseed_3.16.tar.xz oldsys-preseed_3.16_i386.udeb Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- 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/e1ykqtu-0003vy...@coccia.debian.org
Processing of oldsys-preseed_3.16_i386.changes
oldsys-preseed_3.16_i386.changes uploaded successfully to localhost along with the files: oldsys-preseed_3.16.dsc oldsys-preseed_3.16.tar.xz oldsys-preseed_3.16_i386.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1ykqvt-0005sy...@franck.debian.org
oldsys-preseed_3.16_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Apr 2015 07:07:22 +0200 Source: oldsys-preseed Binary: oldsys-preseed Architecture: source i386 Version: 3.16 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: oldsys-preseed - Preseed debian-installer from an existing device (udeb) Closes: 783019 Changes: oldsys-preseed (3.16) unstable; urgency=medium . [ Ian Campbell ] * Avoid exiting prematurely on arm*/orion5x or arm*/kirkwood platforms when they do not use device tree. (Closes: #783019) Checksums-Sha1: c05e44ac69e17160bd20e1fac3eee757a51a7926 1663 oldsys-preseed_3.16.dsc 4bc41c1ca24e97bfe724d057cfbfec44a78d97fd 289364 oldsys-preseed_3.16.tar.xz 0595b04d68a95a05bebaf2f06658b481b7cebd62 6572 oldsys-preseed_3.16_i386.udeb Checksums-Sha256: 740a809cb9dc491967e0fa721ce386942c98198cfbbc55ff88d83be58345ad8f 1663 oldsys-preseed_3.16.dsc ffc98aa0fd48edda90a25f14613b39572ac97378417e58ba7f5c091ce458cba3 289364 oldsys-preseed_3.16.tar.xz 106c0cef11204eb3e3abe9904fd08b4f7e2c5f47ee23b83ea81eeabe91436d93 6572 oldsys-preseed_3.16_i386.udeb Files: c441eb325f2117714a95c1886cb483ce 1663 debian-installer optional oldsys-preseed_3.16.dsc b483c29ecf677f8119878d52ff0a800a 289364 debian-installer optional oldsys-preseed_3.16.tar.xz 2ca360237c06d918f7ed4b7340ac9ec3 6572 debian-installer optional oldsys-preseed_3.16_i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJVNdtsAAoJEIcvcCxNbiWoSy0P/jhgmGx/Vw4b/9ldji0iUN1+ ly4aNB3ML8vQMWMSAEyO4BDuP0m2LxD5NeIPIsqQcCC8iV8uFTM8WWtzCySg5AQh cDIv069hZZhjawnmTFx5qSWZhyBJTrvIRlIO/xsvj6IPC26vga6S6VM66NprgaZE Nydi9c2xokgQa5yFw0MTEJUArHDfCyw7Edv3WM/fs1Njbz1e8lbdQv/U40pmXubG UtB6ZNoZ/Ndwv7uRU/9ZivM+qVH9lax7rxe5h967byoBW4N1BsfLimkdOL4Wo+Gl JU2HdaRDUfd5oltzjTUiVvxSnB2MAWycLljMjiLtLrlGunPRc3hyx3Gtye/dK8Wn tXUnqysIqoyagbhkXOLXtBt+guTWnI+K+FUxbA0QZ30TLg+4v+hoc5CFBm42EC3c I/WolFAIDlsL9bH3dmIFzDni58o/dtHeGalRJLv/L5JM3d3HwmpwRc+MpuM3Ddmm fPemvUBwGEprffX5wis10B+kxdNpdhkj0HaVMoNXy0DmFOodbyYEFCVJafMeoTGy CF9hJng+bdzSkxXubEGgIH4NQE8gc6M+xVRwjPthj8tYci6WHb7FjH07Q7Fuvamd pNR0S2ukW/2o5QM2CDste5JBkf2C1lg18fjDdQDyT/p4EjoCGuoVOG1pfGs7sxHz JNSCZDwbqghhAw3tB2tF =g2jB -END PGP SIGNATURE- Thank you for your contribution to Debian. -- 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/e1ykqzs-0005ys...@franck.debian.org
Bug#783041: Advanced Options in Debian 8 Jessie DI-rc3 installer (Debian 8 Jessie DI-rc3 installer AMD64 DVD ( Re-submited)
Package:installation-reports (Debian 8 Jessie DI-rc3 installer AMD64 DVD) Boot method: How did you boot the installer? CD? floppy? network? DVD Image version: http://cdimage.debian.org/cdimage/jessie_di_rc3/amd64/iso-dvd/debian-jessie-DI-rc3-amd64-DVD-1.iso Date: Monday April 20, 2015 at 12:30 PM Machine: Description of machine (Acer Aspire 5336-2460 Laptop) Processor:Intel Celeron 925 Memory:3 GB DDR3 Partitions: df -Tl will do; the raw partition table is preferred Don't Know. PS Have Kubuntu on my laptop right now using its partition. The /dev/sda. Output of lspci -knn (or lspci -nn):Don't Know. Base System Installation Checklist: [O]= OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems:I didn't go any farther then installer boot because after I booted up the “Debian 8 Jessie DI-rc3 installer http://forums.debian.net/viewtopic.php?f=17t=121528”, I clicked on “Advanced Options” in the installation menu and the “Alternative Desktop Environment” option wasn't in there. Did they move it or just forgot to put it back in? PS. Was trying to install Debian-7.8.0 AMD64 DVD (Wheezy) using the KDE Alternative Desktop Environment at http://cdimage.debian.org/debian-cd/7.8.0/amd64/bt-dvd/debian-7.8.0-amd64-DVD-1.iso.torrent, and it had a problem with the video card or monitor. When booting up, it did fine up to the point of the login screen and then it was just black. Worked fine on the desktop I have, just not on the Acer laptop. I heard that you upgraded the firmware and drivers in Debian Jessie including non-free firmware so I wanted to give it a shot. Booted up just fine. But when I went to the Advanced Options to change the Alternative Desktop Environment to KDE, that option wasn't there.
Bug#783041: Advanced Options in Debian 8 Jessie DI-rc3 installer (Debian 8 Jessie DI-rc3 installer AMD64 DVD ( Re-submited)
On Mon, Apr 20, 2015 at 06:47:40PM -0700, Ricky Ritchey wrote: snip Comments/Problems:I didn't go any farther then installer boot because after I booted up the “Debian 8 Jessie DI-rc3 installer http://forums.debian.net/viewtopic.php?f=17t=121528”, I clicked on “Advanced Options” in the installation menu and the “Alternative Desktop Environment” option wasn't in there. Did they move it or just forgot to put it back in? For the Jessie builds, it's been moved into the installer itself. You boot as normal from the boot menu and you have the choice of desktops later via tasksel. -- Steve McIntyre, Cambridge, UK.st...@einval.com Since phone messaging became popular, the young generation has lost the ability to read or write anything that is longer than one hundred and sixty characters. -- Ignatios Souvatzis -- 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/20150421020828.gc16...@einval.com
Bug#783042: Package: installation-reports
Package: installation-reports Boot method: sdcard (microSDHC) Image version: Jessie RC 3 from http://ftp.nl.debian.org/debian/dists/testing/main/installer-armhf/current/images/netboot/SD-card-images/ Date: Tue Apr 21 01:27:41 UTC 2015 Machine: cubieboard a10 (revision 2) Processor: armhf Memory: 1GB Partitions: sdcard image standard Output of lspci -knn (or lspci -nn): N/A Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: The above O items I completed using the 2015-04-18 images a few days ago; they are likely still working, HOWEVER I had to deviate from the installation instructions slightly to obtain a usable system (the E components that I re-tested with the RC 3 image to see if they had been resolved). Testing Jessie RC 3 netinstall (from SSD) for CubieBoard A10 Loosely following: https://wiki.debian.org/InstallingDebianOn/Allwinner#Installing_from_an_SD_card_image (location: http://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/ ) Except using: https://www.debian.org/devel/debian-installer/ (location: http://ftp.nl.debian.org/debian/dists/testing/main/installer-armhf/current/images/netboot/SD-card-images/ ) ls -l *.gz ; md5sum -b *.gz ; sha1sum -b *.gz ; sha512sum -b *.gz ; zcat firmware.Cubieboard.img.gz partition.img.gz /dev/sdd ; sync -rw-r--r-- 1 user user 157271 Apr 18 04:17 firmware.Cubieboard.img.gz -rw-r--r-- 1 user user 16332765 Apr 18 04:17 partition.img.gz 948a8e4e3c7d69c6ce616c1216ba310f *firmware.Cubieboard.img.gz 013e43ccca9e0d49d4a28bbc6f8ee01a *partition.img.gz 5e963bc536de7a17dbeff469b487edce9b4543ca *firmware.Cubieboard.img.gz 0d5f1d75d4c40f6b4448a20db753c651ab69d8bf *partition.img.gz 2fe6e467cbe024cd232bfc265ca6cee1de57931f8f4c88c859d10da3afd2c9ac5857ca256a834d2479d69e9f021a44919df3b1fe2a76cbe5db0150a47e8badf9 *firmware.Cubieboard.img.gz 3a77f517c4dc9892748731759632f6947ab7af87910a1078d485240ba4b19d0de471507c010b76013f6001ff2c5bceeb8edd44defdc3b8e1501f91915e40 *partition.img.gz Attempt 1: zcat firmware.Cubieboard.img.gz partition.img.gz /dev/sdd ; sync Attempt 1+mod: dd if=u-boot-sunxi-with-spl-v2015.04.bin of=/dev/sdd bs=1k seek=8 Attempt 1: * Serial console works * HDMI display does not work Attempt 1+mod (updated Mainline U-Boot: git tag v2015.04): * Serial console works * HDMI display DOES WORK * As noted in community, a USB 2.0 hub may be necessary for USB 1.0 / 1.1 devices to work. Retrying with a different SD card, my main remaining complaint is lack of HDMI support, both initially, and after the kernel boots. I understand a more recent kernel (4.1?) has updated framebuffer support for these devices; however the existing debian kernel + an updated U-Boot is sufficient to get basic Xorg support working (if you finish installing via the serial console). dterm /dev/ttyUSB0 115200 8 n 1 Attempt 1: === U-Boot SPL 2014.10+dfsg1-5 (Apr 07 2015 - 22:05:03) DRAM: 1024 MiB CPU: 100800Hz, AXI/AHB/APB: 3/2/2 U-Boot 2014.10+dfsg1-5 (Apr 07 2015 - 22:05:03) Allwinner Technology CPU: Allwinner A10 (SUN4I) I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial SCSI: SUNXI SCSI INIT SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: emac Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0... Found U-Boot script /boot.scr reading /boot.scr 1451 bytes read in 28 ms (49.8 KiB/s) ## Executing script at 4310 Mainline u-boot / new-style environment detected. reading vmlinuz 3183080 bytes read in 1829 ms (1.7 MiB/s) reading dtbs/sun4i-a10-cubieboard.dtb 18505 bytes read in 192 ms (93.8 KiB/s) reading initrd.gz Error reading cluster ** Unable to read file initrd.gz ** ^ My old microSD card went bad. SCRIPT FAILED: continuing... ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** scanning bus for devices... Found 0 device(s). SCSI device 0: Device 0: not available (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found USB1: USB EHCI 1.00 scanning bus 1 for devices... cannot reset port 1!? 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found USB device 0: unknown device ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 1 Attempt
Bug#764982: Backports when the danger is contrib and non-free
On Mon, Apr 20, 2015 at 11:00:09PM +0200, Paul van der Vlis wrote: Op 20-04-15 om 22:19 schreef Geert Stappers: Op 20-04-15 om 09:39 schreef Turbo Fredriksson: Besides, we had this exact argument for weeks (months) about contrib and non-free 'in the day'. Eventually, _that_ (amongst others) won the argument - it's not an official part of Debian GNU/Linux! I had a closer look at /etc/apt/sources.list of a recent installed machine. And sadly discovered that 'contrib' and 'non-free' were enabled ... I have installed with RC1 and with RC2, but I cannot remember that I have seen that! Maybe you have used a nightly build? I am interested who did this when you are correct. I don't know how it happened. Facts: * /var/log/installer/lsb-release says 'build 20150324' * the is from 2015-03-30 Enabling non-free and contrib in sources.list is a very stupid idea because Debian is about DFSG software and non-free is not DFSG, and contrib needs non-DFSG software. Groeten Geert Stappers -- Leven en laten leven -- 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/20150421040630.gt23...@gpm.stappers.nl
Bug#783019: marked as done (kirkwood network console images ask to choose ethernet device)
Your message dated Tue, 21 Apr 2015 05:18:32 + with message-id e1ykqzs-0005z3...@franck.debian.org and subject line Bug#783019: fixed in oldsys-preseed 3.16 has caused the Debian Bug report #783019, regarding kirkwood network console images ask to choose ethernet device to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 783019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: oldsys-preseed Version: 3.15 Severity: grave Tags: patch Doing a test install of jessie on my TS-419 I get asked (via the serial) for a serial port and a ssh password. I happen to have a serial port but these devices mostly do not and are supposed to be headless. I'm using the images from http://ftp.uk.debian.org/debian/dists/jessie/main/installer-armel/20150418/images/kirkwood/network-console/qnap/ts-41x/ From the logs there is no sign of oldsys-preseed running. Poking around in the shell I see: ~ # sh -x /usr/bin/oldsys-preseed + set -e + . /usr/lib/oldsys-preseed/functions + NONINTERACTIVE=yes + FILE=/preseed.cfg + archdetect + + sed s/Hardware\s*:\s*// grep ^Hardware /proc/cpuinfo + machine=QNAP TS-41x + cat /proc/device-tree/model + dt_model= ~ # IOW due to set -e it exits early on systems where /proc/device-tree/model does not exist, since the cat fails. By commenting out that one line things seem to progress in a way which looks promising (i.e. much more spew than above). I think the most plausible solution would be: diff --git a/oldsys-preseed b/oldsys-preseed index f60196f..4cd7138 100755 --- a/oldsys-preseed +++ b/oldsys-preseed @@ -115,7 +115,11 @@ case `archdetect` in arm*/orion5x | arm*/kirkwood) machine=$(grep ^Hardware /proc/cpuinfo | sed 's/Hardware\s*:\s*//') # /proc/device-tree may not exist on all architectures - dt_model=$(cat /proc/device-tree/model 2/dev/null) + if [ -e /proc/device-tree/model ] ; then + dt_model=$(cat /proc/device-tree/model 2/dev/null) + else + dt_model=UNKNOWN + fi if echo $machine | grep -q ^Buffalo/Revogear Kurobox Pro; then check_file /proc/mtd rootfs=$(get_mtdblock rootfs) I'll build an image and test that shortly. Severity grave because d-i is mostly useless on qnap hardware (and headless orion or kirkwood generally) with this issue, at least for non-DT systems, which I think is still most of them in Jessie. Ian. ---End Message--- ---BeginMessage--- Source: oldsys-preseed Source-Version: 3.16 We believe that the bug you reported is fixed in the latest version of oldsys-preseed, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 783...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Perrier bubu...@debian.org (supplier of updated oldsys-preseed package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Apr 2015 07:07:22 +0200 Source: oldsys-preseed Binary: oldsys-preseed Architecture: source i386 Version: 3.16 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: oldsys-preseed - Preseed debian-installer from an existing device (udeb) Closes: 783019 Changes: oldsys-preseed (3.16) unstable; urgency=medium . [ Ian Campbell ] * Avoid exiting prematurely on arm*/orion5x or arm*/kirkwood platforms when they do not use device tree. (Closes: #783019) Checksums-Sha1: c05e44ac69e17160bd20e1fac3eee757a51a7926 1663 oldsys-preseed_3.16.dsc 4bc41c1ca24e97bfe724d057cfbfec44a78d97fd 289364 oldsys-preseed_3.16.tar.xz 0595b04d68a95a05bebaf2f06658b481b7cebd62 6572 oldsys-preseed_3.16_i386.udeb Checksums-Sha256: 740a809cb9dc491967e0fa721ce386942c98198cfbbc55ff88d83be58345ad8f 1663 oldsys-preseed_3.16.dsc ffc98aa0fd48edda90a25f14613b39572ac97378417e58ba7f5c091ce458cba3 289364
Bug#764982: Backports when the danger is contrib and non-free
On Mon, Apr 20, 2015 at 09:39:41AM +0200, Turbo Fredriksson wrote: On Apr 20, 2015, at 7:01 AM, Christian PERRIER wrote: I really don't think this is a good idea and I'm this close to re-close the bug report. Well, I asked a fair question I think. I knew the answer (but I could be wrong - I haven't been paying attention to Debian GNU/Linux matters in years): Is anything but main part of the official Debian GNU/Linux distribution? If not, it should not be enabled _by default_. Right? So I still think it can, and should, be closed. Done. If not for all the other reasons, then that? There have, in any case, been numerous cases against enabling it, but NONE for enabling it. And no, I want it and I use it is NOT an opinion FOR it! :) Besides, we had this exact argument for weeks (months) about contrib and non-free 'in the day'. Eventually, _that_ (amongst others) won the argument - it's not an official part of Debian GNU/Linux! I had a closer look at /etc/apt/sources.list of a recent installed machine. And sadly discovered that 'contrib' and 'non-free' were enabled ... Groeten Geert Stappers -- Leven en laten leven -- 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/20150420201915.gp23...@gpm.stappers.nl
Bug#769778: marked as done (installation-report: Testing set up by upgrading Stable)
Your message dated Mon, 20 Apr 2015 13:27:03 +0200 with message-id 20150420132703.4775986b@s5.lokal and subject line done has caused the Debian Bug report #769778, regarding installation-report: Testing set up by upgrading Stable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.49 Severity: normal Dear Maintainer, Debian-Testing is still not installable for me only expert-installation is possible (because of IPv6?) and then it failed at the step of installing tasks, so I set it up by upgrading Stable, but several problems showed. For example Grub was not installable on a BTRFS-root-filesystem and XFS is not upgradeable from Kernel 3.2 to 3.16 . But inspite of that it worked out in the end with ext4 and even firmware-linux-nonfree did not break the radeon-graphics as reported there: 769...@bugs.debian.org - -- Package-specific info: Boot method: USB Image version: http://cdimage.debian.org/debian-cd/7.7.0/amd64/iso-cd/debian-7.7.0-amd64-netinst.iso 2014-10-18 Date: 2014-11-16 Machine: HP t5735 thin-client Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on /dev/sdb1 ext4 13981548 3295252 9953016 25% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 1983085028193280 3% /run tmpfs tmpfs 495760 0495760 0% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 495760 0495760 0% /sys/fs/cgroup tmpfs tmpfs99156 0 99156 0% /run/user/107 tmpfs tmpfs99156 4 99152 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [o] Load installer modules: [o] Clock/timezone setup: [o] User/password setup:[o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Install tasks: [o] Install boot loader:[o] Overall install:[o] Comments/Problems: t would be much nicer to set up Jessie/beta directly, but well, as long as UEFI-boot-problems persist, everyone has to be patient, I guess. Upon upgrading to Testing, there was one broken or half-installed package and kernel 3.16 had to be set up manually. - -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7 (wheezy) - installer build 20130613+deb7u2+b3 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge [1002:7910] lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge [1002:7910] lspci -knn: 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (Internal gfx) [1002:7912] lspci -knn: 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI Device [1002:7914] lspci - -knn: Kernel driver in use: pcieport lspci -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI0) [1002:4387] lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI0) [1002:4387] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI1) [1002:4388] lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI1) [1002:4388] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI2) [1002:4389] lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI SB600 USB (OHCI2) [1002:4389] lspci -knn: Kernel driver in use: ohci_hcd
Bug#764982: Backports, where is the danger (why the FUD)
Turbo Fredriksson tu...@bayour.com writes: On Apr 19, 2015, at 9:48 PM, Paul van der Vlis wrote: Did you check if it really was back ports? Yes. I've been using Debian GNU/Linux since.. 'bo' or something and a DD since '97 or so. I know what I'm doing (98% of the time :). I use backports on all machines I care about, and I never had dependency problems from backports (so far I remember). Good for you. Maybe it's better now, but my opinion still stands. Well, that's a jolly constructive attitude, well done. ... Why!? Why should _I_ adapt to YOUR opinion? What makes you think that YOUR opinion is the only, correct one?? If everyone adopted such a position, we'd never get anything done now, would we? Personally, I very regularly enable backports, and I have no problems whatsoever with that, but perhaps the fact that I have come to that point by a conscious choice means that I'm only installing packages from backports with definite intent, and so happen to select packages that are not problematic. It had not occur ed to me that I would receive backports versions of packages missing from main, without any real warning unless I was paying close attention to the download phase. I'd suggest that using the configuration or not of backports quite a blunt tool here. It would be much better to somehow ensure that the only time that packages would be automatically installed from backports would be when upgrading packages that already came from backports, and that otherwise one would need to explicitly specify the target-release. Sadly, I don't think that we have the technology at present to make this the case, and there's no chance to add it for this release, so that seems like justification enough to back this out. I don't like that much, since that means that I continue to need to add it back in, but that's clearly better than someone being bitten by the down-side of this. An alternative that occurs to me is that we could split backports main into main and novel, say, where main is reserved for packages that do already exist in stable, and novel for packages that are being added by backports. If we did that (which could be done after the release by the backports team, so there is much less time pressure) then we could safely re-enable backports. On the other hand, that idea would need to be informed by the numbers. What proportion of backports are upgrades, rather than new packages? My subjective impression is that most of what I use backports for would fall into the 'novel' category anyway, so I'd not be saved any effort by such a change, and it would require people to understand an extra layer of complexity in order to get what they want, so really wouldn't make anyone happy. While we're at it, it would be nice to have the same Only if I explicitly ask for it feature for non-free (and probably contrib). I may be willing to compromise my freedom in order to get my laptop wifi working, on the basis that I could always buy a better wifi card, but that does not mean I want anything else out of non-free. This also seems to suggest that this is a more generic bug in apt. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Re: Debian Installer Jessie RC 3 release
Hello Installer experts, Am Sonntag, den 19.04.2015, 16:25 +0200 schrieb Cyril Brulebois: Feedback for this release = We need your help to find bugs and further improve the installer, so please try it. Installer CDs, other media and everything else you will need are available at our web site[3]. Maybe you can look on #740330 which was raised on debian-boot in October: https://lists.debian.org/debian-boot/2014/10/msg00115.html IMHO it is an important problem with a patch. Thanks for your work. -- Noël Köthe noel debian.org Debian GNU/Linux, www.debian.org signature.asc Description: This is a digitally signed message part
Bug#764982: Backports, where is the danger (why the FUD)
On Apr 19, 2015, at 10:48 PM, Paul van der Vlis wrote: Backports main is official Debian. [1] You misunderstand the announcement. … official Debian service … Notice the last word here! It say service. Not 'official _PART_ of Debian'! -- Life sucks and then you die -- 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/31113396-6033-4fc2-a294-43e5eabb9...@bayour.com
Bug#764982: Backports, 2B || !2B
On Apr 20, 2015, at 7:01 AM, Christian PERRIER wrote: I really don't think this is a good idea and I'm this close to re-close the bug report. Well, I asked a fair question I think. I knew the answer (but I could be wrong - I haven't been paying attention to Debian GNU/Linux matters in years): Is anything but main part of the official Debian GNU/Linux distribution? If not, it should not be enabled _by default_. Right? So I still think it can, and should, be closed. If not for all the other reasons, then that? There have, in any case, been numerous cases against enabling it, but NONE for enabling it. And no, I want it and I use it is NOT an opinion FOR it! :) Besides, we had this exact argument for weeks (months) about contrib and non-free 'in the day'. Eventually, _that_ (amongst others) won the argument - it's not an official part of Debian GNU/Linux! -- System administrators motto: You're either invisible or in trouble. - Unknown -- 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/d1fed47c-47dd-4032-8cdf-b16dfea4e...@bayour.com
Bug#764982: Backports, where is the danger (why the FUD)
On Apr 20, 2015, at 9:26 AM, Philip Hands wrote: Turbo Fredriksson tu...@bayour.com writes: Good for you. Maybe it's better now, but my opinion still stands. Well, that's a jolly constructive attitude, well done. Not how I meant it, but thanx for misunderstanding. I meant that my opinion about back ports still stand. For that reason and all the others that's been mentioned. If everyone adopted such a position, we'd never get anything done now, would we? Of course we would. And so would the user(s). User opt-out is always better than forced opt-in. Right? This is the same thing. Users should know what they're in for and have to choose to enable this themselves. It should not be 'forced' upon them... -- 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/8b3d4c22-cd53-45a7-8287-9d1ea3819...@bayour.com
Re: Bug#764982: Backports, where is the danger (why the FUD)
On Mon, Apr 20, 2015 at 08:26:10AM +0100, Philip Hands wrote: While we're at it, it would be nice to have the same Only if I explicitly ask for it feature for non-free (and probably contrib). I may be willing to compromise my freedom in order to get my laptop wifi working, on the basis that I could always buy a better wifi card, but that does not mean I want anything else out of non-free. There is a case to me made that the documentation in non-free, especially that released uneder the GNU Free Documentation Licence with invariant parts, might be a special case here. -- hendrik -- 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/20150420153741.ga3...@topoi.pooq.com
Bug#783019: kirkwood network console images ask to choose ethernet device
Package: oldsys-preseed Version: 3.15 Severity: grave Tags: patch Doing a test install of jessie on my TS-419 I get asked (via the serial) for a serial port and a ssh password. I happen to have a serial port but these devices mostly do not and are supposed to be headless. I'm using the images from http://ftp.uk.debian.org/debian/dists/jessie/main/installer-armel/20150418/images/kirkwood/network-console/qnap/ts-41x/ From the logs there is no sign of oldsys-preseed running. Poking around in the shell I see: ~ # sh -x /usr/bin/oldsys-preseed + set -e + . /usr/lib/oldsys-preseed/functions + NONINTERACTIVE=yes + FILE=/preseed.cfg + archdetect + + sed s/Hardware\s*:\s*// grep ^Hardware /proc/cpuinfo + machine=QNAP TS-41x + cat /proc/device-tree/model + dt_model= ~ # IOW due to set -e it exits early on systems where /proc/device-tree/model does not exist, since the cat fails. By commenting out that one line things seem to progress in a way which looks promising (i.e. much more spew than above). I think the most plausible solution would be: diff --git a/oldsys-preseed b/oldsys-preseed index f60196f..4cd7138 100755 --- a/oldsys-preseed +++ b/oldsys-preseed @@ -115,7 +115,11 @@ case `archdetect` in arm*/orion5x | arm*/kirkwood) machine=$(grep ^Hardware /proc/cpuinfo | sed 's/Hardware\s*:\s*//') # /proc/device-tree may not exist on all architectures - dt_model=$(cat /proc/device-tree/model 2/dev/null) + if [ -e /proc/device-tree/model ] ; then + dt_model=$(cat /proc/device-tree/model 2/dev/null) + else + dt_model=UNKNOWN + fi if echo $machine | grep -q ^Buffalo/Revogear Kurobox Pro; then check_file /proc/mtd rootfs=$(get_mtdblock rootfs) I'll build an image and test that shortly. Severity grave because d-i is mostly useless on qnap hardware (and headless orion or kirkwood generally) with this issue, at least for non-DT systems, which I think is still most of them in Jessie. Ian. -- 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/1429553469.6174.12.ca...@debian.org
Bug#783019: kirkwood network console images ask to choose ethernet device
On Mon, 2015-04-20 at 19:11 +0100, Ian Campbell wrote: By commenting out that one line things seem to progress in a way which looks promising (i.e. much more spew than above). I think the most plausible solution would be: diff --git a/oldsys-preseed b/oldsys-preseed index f60196f..4cd7138 100755 --- a/oldsys-preseed +++ b/oldsys-preseed @@ -115,7 +115,11 @@ case `archdetect` in arm*/orion5x | arm*/kirkwood) machine=$(grep ^Hardware /proc/cpuinfo | sed 's/Hardware\s*:\s*//') # /proc/device-tree may not exist on all architectures - dt_model=$(cat /proc/device-tree/model 2/dev/null) + if [ -e /proc/device-tree/model ] ; then + dt_model=$(cat /proc/device-tree/model 2/dev/null) + else + dt_model=UNKNOWN + fi if echo $machine | grep -q ^Buffalo/Revogear Kurobox Pro; then check_file /proc/mtd rootfs=$(get_mtdblock rootfs) I'll build an image and test that shortly. Test was successful, proper patch is below. Ian. diff --git a/debian/changelog b/debian/changelog index 422a43d..ad9a6ba 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +oldsys-preseed (3.16) UNRELEASED; urgency=medium + + * Avoid exiting prematurely on arm*/orion5x or arm*/kirkwood which do not use +device tree. (Closes: #783019) + + -- Ian Campbell i...@debian.org Mon, 20 Apr 2015 19:06:00 +0100 + oldsys-preseed (3.15) unstable; urgency=medium [ Michael Walle ] diff --git a/oldsys-preseed b/oldsys-preseed index f60196f..4cd7138 100755 --- a/oldsys-preseed +++ b/oldsys-preseed @@ -115,7 +115,11 @@ case `archdetect` in arm*/orion5x | arm*/kirkwood) machine=$(grep ^Hardware /proc/cpuinfo | sed 's/Hardware\s*:\s*//') # /proc/device-tree may not exist on all architectures - dt_model=$(cat /proc/device-tree/model 2/dev/null) + if [ -e /proc/device-tree/model ] ; then + dt_model=$(cat /proc/device-tree/model 2/dev/null) + else + dt_model=UNKNOWN + fi if echo $machine | grep -q ^Buffalo/Revogear Kurobox Pro; then check_file /proc/mtd rootfs=$(get_mtdblock rootfs) signature.asc Description: This is a digitally signed message part
Bug#758410: marked as done (d-i manual: update for bootmenu entries of graphical installer)
Your message dated Mon, 20 Apr 2015 20:18:01 +0200 with message-id 20150420201801.17eea1c9afae1a55a703e...@wansing-online.de and subject line Re: Bug#758410: d-i manual: update for bootmenu entries of graphical installer has caused the Debian Bug report #758410, regarding d-i manual: update for bootmenu entries of graphical installer to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 758410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-guide Tags: patch Hi, some parts in the d-i manual for the graphical installer were written in times, were we had only *one* entry Graphical install in the initial boot menu, but we had no submenu Alternative desktop environments existing. Now we have *several* Graphical install entries all over the bootmenu, not only one (under Alternative desktop environments submenu). This should probably result in some small changes for the manual. Patch attached. Holger -- Holger Wansing hwans...@mailbox.org Index: en/appendix/graphical.xml === --- en/appendix/graphical.xml (Revision 69238) +++ en/appendix/graphical.xml (Arbeitskopie) @@ -24,7 +24,11 @@ The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select -the relevant option from the boot menu. Expert and rescue mode for the +one of the relevant options (quoteGraphical install/quote) from the boot +menu. There are also such entries for different desktop environments in the +quoteAlternative desktop environments/quote submenu under +quoteAdvanced options/quote. +Expert and rescue mode for the graphical installer can be selected from the quoteAdvanced options/quote menu. The previously used boot methods userinputinstallgui/userinput, userinputexpertgui/userinput and userinputrescuegui/userinput can Index: en/using-d-i/using-d-i.xml === --- en/using-d-i/using-d-i.xml (Revision 69238) +++ en/using-d-i/using-d-i.xml (Arbeitskopie) @@ -61,8 +61,8 @@ For this architecture the d-i; supports two different user interfaces: a character-based one and a graphical one. The character-based interface is -used by default unless you selected the quoteGraphical install/quote -option in the initial boot menu. For more information about the +used by default unless you selected an quoteGraphical install/quote +option in the boot menu. For more information about the graphical installer, please refer to xref linkend=graphical/. /parapara condition=not-gtk ---End Message--- ---BeginMessage--- Hi, Holger Wansing hwans...@mailbox.org wrote: Package: installation-guide Tags: patch Hi, some parts in the d-i manual for the graphical installer were written in times, were we had only *one* entry Graphical install in the initial boot menu, but we had no submenu Alternative desktop environments existing. Now we have *several* Graphical install entries all over the bootmenu, not only one (under Alternative desktop environments submenu). This should probably result in some small changes for the manual. This bug can be closed. The Alternative desktop environments submenu does not exist anymore in Jessie installer, since the desktop selection is now done in tasksel. Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ ---End Message---
Re: Bug#781882: frequent flash-kernel triggers on Wheezy-Jessie upgrade
Control: reasssign -1 flash-kernel flash-kernel/3.34 On Sat, 04 Apr 2015 10:49:14 +0100 Ian Campbell i...@debian.org wrote: Control: clone -1 -2 Control: retitle -2 frequent flash-kernel triggers on Wheezy-Jessie upgrade Control: severity -2 normal Control: found -2 3.34 On Thu, 2015-04-02 at 13:04 +0200, reportbug wrote: Thanks for the report. I'm cloning out the flash-kernel trigger issue to track against that package. You seem to have missed a step; I have attempted to correct this above, and Bcc'd flash-ker...@packages.debian.org so they get some notice of the reassignment. ** frequent flash-kernel triggers As mentioned about, on all the machines the flash-kernel trigger ran frequently during the upgrade and dist-upgrade operations. Since this takes several minutes, it would be ideal if this only happened once during an upgrade or dist-upgrade run. I can reproduce this on a fresh Wheezy install upgraded to Jessie on a TS-419something. I've attached the script logs from that update. From them: [See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781882#10 for the attachments.] $ grep -E apt-get\|flash-kernel: tmp/upgrade-jessie.script root@qnap:/home/ijc# apt-get update root@qnap:/home/ijc# apt-get upgrade flash-kernel: installing version 3.2.0-4-kirkwood flash-kernel: root@qnap:/home/ijc# apt-get linux-image-^C root@qnap:/home/ijc# apt-get dist-upgrade flash-kernel: installing version 3.2.0-4-kirkwood flash-kernel: installing version 3.2.0-4-kirkwood flash-kernel: deferring update (trigger activated) /etc/kernel/postinst.d/zz-flash-kernel: flash-kernel: deferring update (trigger activated) flash-kernel: installing version 3.16.0-4-kirkwood flash-kernel: installing version 3.16.0-4-kirkwood root@qnap:/home/ijc# apt-get dist-upgrade Use 'apt-get autoremove' to remove them. So it seems it ran once on apt-get upgrade and 4 times on apt-get dist-upgrade, with two deferrals as well. At first glance it seems like invocations via the initramfs-tools hooks are not being deferred. Ian. -- 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/CAJYzjmfsamrwtzERRJaFbXc5Ts2T1OHpUVKwnVW5mEYz=4_...@mail.gmail.com
Bug#764982: marked as done (apt-setup-udeb: Backports via d-i, but not by default)
Your message dated Mon, 20 Apr 2015 22:01:45 +0200
with message-id 20150420200145.go23...@gpm.stappers.nl
and subject line Re: Bug#764982: Backports, 2B || !2B
has caused the Debian Bug report #764982,
regarding apt-setup-udeb: Backports via d-i, but not by default
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
764982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: apt-setup-udeb
Version: 1:0.82
Severity: normal
Hello,
Current apt-setup enable backports by default (since #691651),
contrary to Mike's report:
Commenting them out by default would probably be a safe default.
See proposed patch, attached.
Regards
Mathieu Parent
From 84467e85f52c7ec85cbde29f7177ed16cb24088c Mon Sep 17 00:00:00 2001
From: Mathieu Parent math.par...@gmail.com
Date: Sun, 12 Oct 2014 20:57:53 +0200
Subject: [PATCH] Don't enable backport by default
---
debian/apt-setup-udeb.templates | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/debian/apt-setup-udeb.templates b/debian/apt-setup-udeb.templates
index 3f54087..1843e65 100644
--- a/debian/apt-setup-udeb.templates
+++ b/debian/apt-setup-udeb.templates
@@ -75,7 +75,6 @@ _Description: Cannot access repository
Commented out entries for ${HOST} have been added to the
/etc/apt/sources.list file.
-# All services are enabled by default to allow preseeding
Template: apt-setup/services-select
Type: multiselect
Choices-C: security, updates, backports
@@ -84,7 +83,7 @@ Choices-C: security, updates, backports
# including host name. In short, KEEP THIS SHORT and, yes, that's tricky
# :sl1:
__Choices: security updates (from ${SEC_HOST}), release updates, backported software
-Default: security, updates, backports
+Default: security, updates
# :sl1:
_Description: Services to use:
Debian has two services that provide updates to releases: security and
--
2.1.1
---End Message---
---BeginMessage---
On Mon, Apr 20, 2015 at 07:01:02AM +0200, Christian PERRIER wrote:
Quoting Geert Stappers (stapp...@stappers.nl):
reopen 764982
stop
I really don't think this is a good idea and I'm this close to
re-close the bug report.
If anyone feels that something should be done for backports,
please open a new bug report,
That is better then keeping this BR open.
Groeten
Geert Stappers
--
Leven en laten leven
signature.asc
Description: Digital signature
---End Message---
