netinst image on USB stick asks for cdrom
Hi, I took todays (2015-04-16 18:20) daily Jessie netinstaller build[1], copied the image to an USB stick[2] and started the installation. At the "Partition disks" step the installer asked me: "/media/cdrom/:Please insert the disc labeled: 'Debian GNU/Linux Jessie-DI-rc1 _Jessie_ - Official RC amd64 NETINST Binary-1 2015-01-09-01:04' in the drive '/media/cdrom/' and press enter. Media change " Neither "Go Back" nor "Continue" got me away from this screen. I checked the installation manual. It says in 4.3.1 paragraph one[3] that the netinst image could also be used for USB installation. The problem seems to be present for a longer time[4] and not related to this particular daily build? I have never had this problem with a CD or DVD image on an USB stick. An easy workaround might be to put a warning about netinst images in the installation manual? Regards, Thomas Koch [1] http://cdimage.debian.org/cdimage/daily-builds/daily/arch- latest/amd64/iso-cd/debian-testing-amd64-netinst.iso [2] sudo cp *.iso /dev/sdb [3] http://d-i.debian.org/manual/en.amd64/ch04s03.html [4] https://debianforum.de/forum/viewtopic.php?f=12&t=150536 -- 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/201504170941.13614.tho...@koch.ro
Bug#782743: unblock: brltty/5.2~20141018-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello,
We have just received a report from a blind user saying that braille
auto-detection in the debian-installer does not work any more for his
device. This is reported as bug report #782732. I could reproduce the
issue, and fix it. This is pretty bad because it matters for 4 brands
(Albatross, Cebra, HumanWare and HandyTech) of braille devices of the
30 supported brands, among which HumanWare and HandyTech are AIUI very
commonly found. The price of such device makes it unaffordable for their
user to use a replacement device, so they really have no way install
debian 8.0 by themselves.
What happens is that these braille devices use the same USB ID,
0403:6001, because their manufacturers were too lazy to change the
USB-to-serial chip ID. So when one of these is connected, brltty has
to try the 4 different drivers for these various devices, which happens
to work fine because the protocols are different enough for this to be
safe.
However, the probing function of one of those drivers, Albatross,
actually uses an infinite loop, keeping trying between 19200 bauds and
9600 bauds. As a result, when brltty tries it, it gets stuck inside
that probing loop. It happens that in the past the driver would get
an open error at some point, thus breaking its loop and letting other
drivers try their protocol. This open error has apparently been fixed
in the latest version of brltty, and thus the probing gets stuck inside
the Albatross driver. In the attached change which I have uploaded to
unstable, I change this infinite loop into a simple loop over the two
19200 and 9600 bauds values, i.e. the driver will just try them both,
and if they both fail, notice the end of available baud possibilities,
thus abort, and thus let the brltty core give other drivers a chance to
do their probing, before the brltty core tries Albatross again. This
infinite loop inside the Albatross driver was indeed spurious since the
brltty core already performs it.
I'm Cc-ing debian-boot for udeb confirmation.
Thanks,
Samuel
unblock brltty/5.2~20141018-5
-- System Information:
Debian Release: 8.0
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (500, 'oldstable'), (1, 'buildd-experimental'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.0.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--
Samuel
*** s has joined channel #ens-mim
re
pfff
mare de la pfp.
pas commencer et j'en ai deja marre.
bon ct juste un cou de gueule ++
*** s has left channel #ens-mim (s)
-+- #ens-mim et la peufeupeu -+-
--
Samuel
The problem with America is stupidity. I'm not saying there should be a
capital punishment for stupidity, but why don't we just take the safety labels
off of everything and let the problem solve itself?
--
Samuel
"I once witnessed a long-winded, month-long flamewar over the use of
mice vs. trackballs...It was very silly."
(By Matt Welsh)
diff -Nru brltty-5.2~20141018/debian/changelog
brltty-5.2~20141018/debian/changelog
--- brltty-5.2~20141018/debian/changelog2015-02-15 02:25:15.0
+0100
+++ brltty-5.2~20141018/debian/changelog2015-04-16 23:20:11.0
+0200
@@ -1,3 +1,10 @@
+brltty (5.2~20141018-5) unstable; urgency=high
+
+ * patches/60-albatross.patch: Fix probing loop stuck inside the albatross
+driver (Closes: #782732).
+
+ -- Samuel Thibault Thu, 16 Apr 2015 23:19:16 +0200
+
brltty (5.2~20141018-4) unstable; urgency=medium
* patches/git-9337089: Fix xbrlapi into really not writing anything when
diff -Nru brltty-5.2~20141018/debian/patches/60-albatross.patch
brltty-5.2~20141018/debian/patches/60-albatross.patch
--- brltty-5.2~20141018/debian/patches/60-albatross.patch 1970-01-01
01:00:00.0 +0100
+++ brltty-5.2~20141018/debian/patches/60-albatross.patch 2015-04-16
22:40:26.0 +0200
@@ -0,0 +1,13 @@
+diff --git a/Drivers/Braille/Albatross/braille.c
b/Drivers/Braille/Albatross/braille.c
+index e15d32b..27c504c 100644
+--- a/Drivers/Braille/Albatross/braille.c
b/Drivers/Braille/Albatross/braille.c
+@@ -478,7 +478,7 @@ brl_construct (BrailleDisplay *brl, char **parameters,
const char *device) {
+ if (afterTimePeriod(&period, NULL)) break;
+ }
+
+- if (!*++baud) baud = baudTable;
++ if (!*++baud) break;
+ }
+
+ io->closePort();
diff -Nru brltty-5.2~20141018/debian/patches/series
brltty-5.2~20141018/debian/patches/series
--- brltty-5.2~20141018/debian/patches/series 2015-02-11 19:59:38.0
+0100
+++ brltty-5.2~20141018/debian/patches/series 2015-04-16 22:41:19.0
+0200
@@ -6,3 +6,4 @@
git-a7123d7
git-2421eda
git-9337089
+60-albatross.patch
Re: Please avoid trivial changes in the manual
Hello, Dixit Samuel Thibault, le 17/04/2015 : >Some changes such as command lines, device names etc. can actually be >easily applied in all languages, so it is fine to do it *provided that >you do the propagation of the change in all languages yourself*. If >you don't propagate the changes to all languages, there is a quite >strong chance that the translators will not have the time to do the >propagation before the release. Thanks for saying it : it is a very hard and boring work for translators to check that "there is no change but 1 letter". I saw the timeline proposed by Kibi but not sure about the manual : When do you plan to do the last upload ? >If somebody could take the time to unfuzzy the u-boot -> U-Boot change, >that'd be very helpful for languages which already have a translation. I will try to help on this. Thanks. Baptiste signature.asc Description: PGP signature
Re: Please avoid trivial changes in the manual
Baptiste Jammet, le Fri 17 Apr 2015 11:41:29 +0200, a écrit : > Thanks for saying it : it is a very hard and boring work for > translators to check that "there is no change but 1 letter". BTW, aren't there some editor plugin which would highlight the difference between the #| quote and the current msgid? > I saw the timeline proposed by Kibi but not sure about the > manual : > When do you plan to do the last upload ? I'll probably do it on Thursday evening. > >If somebody could take the time to unfuzzy the u-boot -> U-Boot change, > >that'd be very helpful for languages which already have a translation. > > I will try to help on this. Steve is already having a look, please coordinate with him on #debian-boot. Samuel -- 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/20150417095746.gd3...@type.bordeaux.inria.fr
Re: Please avoid trivial changes in the manual
Samuel Thibault, le Fri 17 Apr 2015 11:57:46 +0200, a écrit : > Baptiste Jammet, le Fri 17 Apr 2015 11:41:29 +0200, a écrit : > > Thanks for saying it : it is a very hard and boring work for > > translators to check that "there is no change but 1 letter". > > BTW, aren't there some editor plugin which would highlight the > difference between the #| quote and the current msgid? (I mean character-difference, of course). Samuel -- 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/20150417100051.ge3...@type.bordeaux.inria.fr
Bug#782753: console-setup.postinst hangs forever during upgrades to jessie
Package: console-setup Version: 1.121 Severity: grave Justification: breaks upgrades to jessie Dear Maintainer, I tried upgrading a computer via ssh from debian 7 to 8. It hang forever in console-setup.postinst, with a zombie process. This are the last lines printed: update-initramfs: deferring update (trigger activated) update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Setting up libklibc (2.0.4-2) ... Setting up klibc-utils (2.0.4-2) ... Setting up cpio (2.11+dfsg-4.1) ... Setting up kmod (18-3) ... Setting up busybox (1:1.22.0-9+deb8u1) ... Setting up initramfs-tools (0.120) ... update-initramfs: deferring update (trigger activated) Setting up xkb-data (2.12-1) ... Setting up console-setup (1.121) ... A ps shows: root 2694 0.0 0.0 6468 1024 ?Ss Mar03 0:08 /usr/sbin/sshd root 29796 0.0 0.1 9268 3008 ?Ss 08:16 0:00 \_ sshd: admin [priv] admin29798 0.0 0.0 9400 1468 ?S08:16 0:00 | \_ sshd: admin@pts/0 admin29799 0.0 0.1 6308 3484 pts/0Ss 08:16 0:00 | \_ -bash root 29900 0.0 0.0 4208 1240 pts/0S08:16 0:00 | \_ su - root 29902 0.0 0.1 5672 2956 pts/0S08:16 0:00 | \_ -su root 30202 1.0 2.7 110400 57288 pts/0Sl+ 08:20 0:22 | \_ aptitude root 19447 0.1 0.1 7284 3664 pts/1Ss+ 08:46 0:00 | \_ /usr/bin/dpkg --status-fd 37 --configure locales:all libc6-i686:i386 libgomp1:i386 libquadmath0:i386 libgfortran3:i386 bzip2:i386 libkeyutils1:i386 libkrb5support0:i386 libk5crypto3:i386 [truncated] root 4876 0.0 0.5 16732 12244 pts/1S+ 08:49 0:00 | \_ /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/console-setup.postinst configure 1.88 root 4935 0.0 0.0 0 0 pts/1Z+ 08:49 0:00 | \_ [console-setup.p] Opening a shell and kill -9 4876 was the trick to complete the upgrade. console-setup is then in state: "partially configured" I could reproduce the problem after that with a "apt-get -f install": I always have to kill the postinst. I modified /var/lib/dpkg/info/console-setup.postinst: -> set -x -> Change "setupcon --save-only" into "setupcon -v --save-only" -> Change "setupcon" into "setupcon -v" The output is in the attached file "console-setup.bug.txt". The process hangs. I also tried adding a "set -x" in "/bin/setupcon" and it did fixed the issue, which is really weird. oO Now I can only reproduce it with "dpkg-reconfigure console-setup": If I use the original files it hangs, always. If I add "set -x" on line 2 of "/bin/setupcon", it works, always. Last thing printed before hanging is: Loading /etc/console-setup/cached_UTF-8_del.kmap.gz I'm attaching /etc/defaut/console-setup and /etc/console-setup/cached_UTF-8_del.kmap.gz files. I did not reboot after the upgrade, yet. My /tmp is not a special mount point, permissions are standard (drwxrwxrwt root:root), disk is not full. Sorry to fill a RC bug so close to the release, fell free to downgrade it if you believe it's not a common problem. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages console-setup depends on: ii console-setup-linux 1.121 ii debconf 1.5.56 ii keyboard-configuration 1.121 ii xkb-data2.12-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.19-17 ii lsb-base 4.1+Debian13+nmu1 Versions of packages keyboard-configuration depends on: ii debconf 1.5.56 ii initscripts 2.88dsf-59 ii liblocale-gettext-perl 1.05-8+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-2 ii keyboard-configuration 1.121 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-2 -- debconf information: keyboard-configuration/unsupported_layout: true console-setup/framebuffer_only: keyboard-configuration/other: keyboard-configuration/unsupported_config_options: true keyboard-configuration/layoutcode: fr console-setup/guess_font: keyboard-configuration/store_defaults_in_debconf_db: true keyboard-configuration/model: Generic 105-key (Intl) PC console-setup/store_defaults_in_debconf_db: false debian-installer/console-setup-udeb/title: console-setup/fontsize: 8x16 keyboard-configuration/toggle: No toggling keyboard-configuration/variantcode: conso
Re: Please avoid trivial changes in the manual
Samuel Thibault, le Fri 17 Apr 2015 12:00:51 +0200, a écrit :
> Samuel Thibault, le Fri 17 Apr 2015 11:57:46 +0200, a écrit :
> > Baptiste Jammet, le Fri 17 Apr 2015 11:41:29 +0200, a écrit :
> > > Thanks for saying it : it is a very hard and boring work for
> > > translators to check that "there is no change but 1 letter".
> >
> > BTW, aren't there some editor plugin which would highlight the
> > difference between the #| quote and the current msgid?
>
> (I mean character-difference, of course).
Yes, there is:
$ cd ~/src ; svn co svn://anonsvn.kde.org/home/kde/trunk/l10n-support/pology
$ cd .../po/fr/
$ ~/src/bin/posieve diff-previous
That'll mark additions/removals with {+...+} and {-...-} in the #|
quote.
Samuel
--
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/20150417110843.gg3...@type.bordeaux.inria.fr
Re: Bug#782712: pre-upload unblock request: systemd/215-17 for RC bug #751707
Martin Pitt [2015-04-16 14:53 -0500]: > Hello Cyril, > > Cyril Brulebois [2015-04-16 19:40 +0200]: > > Anyway, asking for home encryption indeed leads to swap encryption, > > through a ecryptfs-setup-swap call, which in turn triggers: I just tried the current rc2 installer (netinst image/graphical) and it does not actually ask me whether I want to encrypt my home direction. It seems you got this option? If the installer calls ecryptfs-setup-swap, then IMHO we should also fix ecryptfs-utils by the release. If the installer doesn't offer this, but people run ecryptfs-setup-swap manually after installation, then a post-release fix is fine of course. But either way I'd rather like to see the systemd fix in the release proper, as it breaks existing installations with that config. BTW, 215-16 still didn't hit testing, so I didn't upload -17 yet. I'll do as soon as it migrates. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#782757: installation-report: Jessie-RC-AMD64 on my build-PC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.58 Severity: wishlist Dear Maintainer, This is wishlist only, just some info. - -- Package-specific info: Boot method: USB Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso, 2015-04-13 Date: 2015-04-16, about 9.00 h to 10.00 h Machine: GA-MA78GM-S2H with Phenom II 710 Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on /dev/sdb1 btrfs 14336000 3492036 8835228 29% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 3592325172354060 2% /run tmpfs tmpfs 898076 0898076 0% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 898076 0898076 0% /sys/fs/cgroup /dev/sdb3 btrfs 12735488 5420224 5427104 50% /home /dev/sda6 ext4999320 32544897964 4% /boot 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: I wanted to celebrate the CPU-upgrade of my secondary build-PC by submitting this report. It is Phenom II x3 710 now, but it cost me a half day to upgrade the BIOS. It is running well now, with just below 80W of power-consumption, when idle, like before and it draws about 130W when fully loaded. I installed on a USB-Flashdrive with a separate /boot/-partition on the harddisk, in order to be able to put the USB-key into a USB3-port upon installation. But unfortunately my USB3-controller card broke, it was very low-cost and turned out o have dummy-fuses only, so I will have to get a new card now, before actually trying out USB3-speed. There is only the base-system so far and everything required to build a kernel-package. I am also going to try it out as a remote-desktop server. I tried to use cpufreqd and cpufrequtils in order to limit the maximum CPU-frequency to 80%, but I don't quite remember, how to do this, I will have to read the documentation first, or maybe it didn't work out because of hardware-incompatibility. In case of problems, I'll file a separate report about this. - -- 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="8 (jessie) - installer build 20150413-00:04" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux build 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-1 (2015-04-08) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge [1022:9600] lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge [1022:9600] lspci -knn: 00:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (int gfx) [1022:9602] lspci -knn: 00:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5) [1022:9609] lspci -knn:Kernel driver in use: pcieport lspci - -knn: 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:b002] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] lspci -knn: Kernel driver in use: ohci-pci lspci -knn: 00:12.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller [1002:4398] lspci -knn:Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] lspci -knn: Kernel driver in use: ohci-pci lspci -knn: 00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0
Re: Bug#782712: pre-upload unblock request: systemd/215-17 for RC bug #751707
Martin Pitt (2015-04-17): > I just tried the current rc2 installer (netinst image/graphical) and > it does not actually ask me whether I want to encrypt my home > direction. It seems you got this option? I tried to follow the code path in Ubuntu, which offers this option, to track down where the offset can come from; and see whether Debian was affected. I didn't mean to imply that Debian proposes the same option, as it does not. > BTW, 215-16 still didn't hit testing, so I didn't upload -17 yet. I'll > do as soon as it migrates. systemd| 215-16 | testing systemd| 215-16 | unstable Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#782712: pre-upload unblock request: systemd/215-17 for RC bug #751707
On 17/04/15 13:51, Martin Pitt wrote: > BTW, 215-16 still didn't hit testing, so I didn't upload -17 yet. I'll > do as soon as it migrates. systemd| 215-16 | testing | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x systemd| 215-16 | unstable | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x, sparc Emilio -- 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/5530fa98.3060...@debian.org
Bug#782753: console-setup.postinst hangs forever during upgrades to jessie
The problem is gone after a reboot into jessie. This is good, but that doesn't really solve the upgrade issue. signature.asc Description: OpenPGP digital signature
Re: netinst image on USB stick asks for cdrom
On Fri, 2015-04-17 at 09:41 +0200, Thomas Koch wrote: > Hi, > > I took todays (2015-04-16 18:20) daily Jessie netinstaller build[1], copied > the image to an USB stick[2] and started the installation. > > At the "Partition disks" step the installer asked me: > > "/media/cdrom/:Please insert the disc labeled: 'Debian GNU/Linux > Jessie-DI-rc1 > _Jessie_ - Official RC amd64 NETINST Binary-1 2015-01-09-01:04' in the drive > '/media/cdrom/' and press enter. You have an April 16th image but it is asking for rc1? Isn't that a bit strange? > Media change > " > > Neither "Go Back" nor "Continue" got me away from this screen. > > I checked the installation manual. It says in 4.3.1 paragraph one[3] that the > netinst image could also be used for USB installation. > > The problem seems to be present for a longer time[4] and not related to this > particular daily build? That forum post has someone using 'Universal-USB-Installer' to mangle the ISO image. Not the right way to put it on a USB stick. > I have never had this problem with a CD or DVD image on an USB stick. An > easy workaround might be to put a warning about netinst images in the > installation manual? No because netinst images generally work on USB sticks. [...] > [2] sudo cp *.iso /dev/sdb [...] Why *.iso? Are you sure this matched only one file? Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Re: netinst image on USB stick asks for cdrom
> No because netinst images generally work on USB sticks. > [...] > > [2] sudo cp *.iso /dev/sdb > [...] > Why *.iso? Are you sure this matched only one file? Of course *iso, what else? *img? But i'd be surprised if cp ever can manage that copying Because there should the 512 bit at the very beginning! For the information where the *iso-bootloader is expected - by BIOS. Or does one start with a bootloader from anywhere else being able to start the image on the stick? And also keep in mind, dd only will manage sdb, never sdb1. -- 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/20150417134022.ga17...@9398.at
Re: Bug#782712: pre-upload unblock request: systemd/215-17 for RC bug #751707
Hello all, Cyril Brulebois [2015-04-17 14:15 +0200]: > I tried to follow the code path in Ubuntu, which offers this option, to > track down where the offset can come from; and see whether Debian was > affected. I didn't mean to imply that Debian proposes the same option, > as it does not. Ah ok, that explains the confusion. So let's fix ecryptfs in a post-release update, I'll file a bug with the references and explanations. > systemd| 215-16 | testing > systemd| 215-16 | unstable -17 uploaded with the originally attached patch. The only difference is the s/UNRELEASED/unstable/ and the timestamp in the changelog. Thanks, and sorry for the late timing again! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Re: netinst image on USB stick asks for cdrom
On Friday, April 17, 2015 03:02:28 PM Ben Hutchings wrote: > > [2] sudo cp *.iso /dev/sdb > > Why *.iso? Are you sure this matched only one file? Sorry. I wanted to keep the mail short. Of course I specified the correct file. Meanwhile I repeated the process with the RC2 netinst and even with the RC2 CD1 with exactly the same result. I've not tried anymore because I just wanted to get a shell on a laptop to decide whether I buy it and used Knoppix instead. It might rather be that the USB stick has a defect? Regards, Thomas Koch -- 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/201504171620.43142.tho...@koch.ro
Bug#782765: d-i.debian.org: copying images fails on dillon (manual build)
Package: d-i.debian.org Severity: normal I suppose this happens after some files were added under images/ due to the recent CSS (re)work, it's possibly the following bit in the manual's build/buildone.sh: | # Copy the custom css stylesheet to the destination directory | cp $stylesheet_css $destdir/html/ | cp -r $stylesheet_images_dir $destdir/html/images Not sure whether we should adjust how the building works on dillon or whether we should change something on the manual side. Keeping this in a bug report for now since it's not critical for RC3. Mraw, KiBi. Messages from the crontab run follow: mv: cannot move `./build.out.en.i386/html/images' to `/srv/d-i.debian.org/www/manual/en.i386/images': File exists mv: cannot move `./build.out.en.amd64/html/images' to `/srv/d-i.debian.org/www/manual/en.amd64/images': File exists mv: cannot move `./build.out.en.arm64/html/images' to `/srv/d-i.debian.org/www/manual/en.arm64/images': File exists mv: cannot move `./build.out.en.armel/html/images' to `/srv/d-i.debian.org/www/manual/en.armel/images': File exists mv: cannot move `./build.out.en.armhf/html/images' to `/srv/d-i.debian.org/www/manual/en.armhf/images': File exists mv: cannot move `./build.out.en.mips/html/images' to `/srv/d-i.debian.org/www/manual/en.mips/images': File exists mv: cannot move `./build.out.en.mipsel/html/images' to `/srv/d-i.debian.org/www/manual/en.mipsel/images': File exists mv: cannot move `./build.out.en.powerpc/html/images' to `/srv/d-i.debian.org/www/manual/en.powerpc/images': File exists mv: cannot move `./build.out.en.ppc64el/html/images' to `/srv/d-i.debian.org/www/manual/en.ppc64el/images': File exists mv: cannot move `./build.out.en.s390x/html/images' to `/srv/d-i.debian.org/www/manual/en.s390x/images': File exists mv: cannot move `./build.out.en.kfreebsd-i386/html/images' to `/srv/d-i.debian.org/www/manual/en.kfreebsd-i386/images': File exists mv: cannot move `./build.out.en.kfreebsd-amd64/html/images' to `/srv/d-i.debian.org/www/manual/en.kfreebsd-amd64/images': File exists mv: cannot move `./build.out.cs.i386/html/images' to `/srv/d-i.debian.org/www/manual/cs.i386/images': File exists mv: cannot move `./build.out.cs.amd64/html/images' to `/srv/d-i.debian.org/www/manual/cs.amd64/images': File exists mv: cannot move `./build.out.cs.arm64/html/images' to `/srv/d-i.debian.org/www/manual/cs.arm64/images': File exists mv: cannot move `./build.out.cs.armel/html/images' to `/srv/d-i.debian.org/www/manual/cs.armel/images': File exists mv: cannot move `./build.out.cs.armhf/html/images' to `/srv/d-i.debian.org/www/manual/cs.armhf/images': File exists mv: cannot move `./build.out.cs.mips/html/images' to `/srv/d-i.debian.org/www/manual/cs.mips/images': File exists mv: cannot move `./build.out.cs.mipsel/html/images' to `/srv/d-i.debian.org/www/manual/cs.mipsel/images': File exists mv: cannot move `./build.out.cs.powerpc/html/images' to `/srv/d-i.debian.org/www/manual/cs.powerpc/images': File exists mv: cannot move `./build.out.cs.ppc64el/html/images' to `/srv/d-i.debian.org/www/manual/cs.ppc64el/images': File exists mv: cannot move `./build.out.cs.s390x/html/images' to `/srv/d-i.debian.org/www/manual/cs.s390x/images': File exists mv: cannot move `./build.out.cs.kfreebsd-i386/html/images' to `/srv/d-i.debian.org/www/manual/cs.kfreebsd-i386/images': File exists mv: cannot move `./build.out.cs.kfreebsd-amd64/html/images' to `/srv/d-i.debian.org/www/manual/cs.kfreebsd-amd64/images': File exists mv: cannot move `./build.out.da.i386/html/images' to `/srv/d-i.debian.org/www/manual/da.i386/images': File exists mv: cannot move `./build.out.da.amd64/html/images' to `/srv/d-i.debian.org/www/manual/da.amd64/images': File exists mv: cannot move `./build.out.da.arm64/html/images' to `/srv/d-i.debian.org/www/manual/da.arm64/images': File exists mv: cannot move `./build.out.da.armel/html/images' to `/srv/d-i.debian.org/www/manual/da.armel/images': File exists mv: cannot move `./build.out.da.armhf/html/images' to `/srv/d-i.debian.org/www/manual/da.armhf/images': File exists mv: cannot move `./build.out.da.mips/html/images' to `/srv/d-i.debian.org/www/manual/da.mips/images': File exists mv: cannot move `./build.out.da.mipsel/html/images' to `/srv/d-i.debian.org/www/manual/da.mipsel/images': File exists mv: cannot move `./build.out.da.powerpc/html/images' to `/srv/d-i.debian.org/www/manual/da.powerpc/images': File exists mv: cannot move `./build.out.da.ppc64el/html/images' to `/srv/d-i.debian.org/www/manual/da.ppc64el/images': File exists mv: cannot move `./build.out.da.s390x/html/images' to `/srv/d-i.debian.org/www/manual/da.s390x/images': File exists mv: cannot move `./build.out.da.kfreebsd-i386/html/images' to `/srv/d-i.debian.org/www/manual/da.kfreebsd-i386/images': File exists mv: cannot move `./build.out.da.kfreebsd-amd64/html/images' to `/srv/d-i.debian.org/www/manual/da.kfreebsd-amd64/images': File exists mv: cannot move `./build.out.de.i386/html/imag
Re: Bug#761815: installation adds entries for USB media to /etc/fstab which confuse udisks
Cyril Brulebois (2015-04-01): > Steve McIntyre (2015-04-01): > > As it stands, this is only for removable media which people have not > > already set up as part of their systems. The whole issue here is that > > this is not useful any more. If anybody is relying on being able to > > use such media without any of the existing auto-mounting stuff > > (desktop or whatever), adding it to /etc/fstab manually later isn't > > hard. I don't really see likely breakage here. > > OK. Color me convinced for the time being, feel free to push and upload; > I'll get that unblocked in a week(ish) if no objections have been raised > by then. Looks good to me, got the expected changes between d-i built against testing and one against sid: -/dev/sda1 /media/usb0 autorw,user,noauto 0 0 -/dev/sda2 /media/usb1 autorw,user,noauto 0 0 Will u/u-u accordingly, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#782712: pre-upload unblock request: systemd/215-17 for RC bug #751707
On 2015-04-17 15:44, Martin Pitt wrote: > Hello all, > > Cyril Brulebois [2015-04-17 14:15 +0200]: >> I tried to follow the code path in Ubuntu, which offers this option, to >> track down where the offset can come from; and see whether Debian was >> affected. I didn't mean to imply that Debian proposes the same option, >> as it does not. > > Ah ok, that explains the confusion. So let's fix ecryptfs in a > post-release update, I'll file a bug with the references and > explanations. > >> systemd| 215-16 | testing >> systemd| 215-16 | unstable > > -17 uploaded with the originally attached patch. The only difference > is the s/UNRELEASED/unstable/ and the timestamp in the changelog. > > Thanks, and sorry for the late timing again! > > Martin > Hi, Just to clarify, are we still intending to do a systemd update prior to Jessie with -17 and then now also a p-u (i.e. for 8.1) for ecryptfs? If we are /not/ pulling systemd for Jessie release next release, we can document the issue for the release notes (possibly as a "non-standard" setup given d-i in Debian does not create this kind of disks, if I understand the discussion correctly). Thanks, ~Niels -- 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/55312cee.5000...@thykier.net
Processing of installation-guide_20150417_amd64.changes
installation-guide_20150417_amd64.changes uploaded successfully to localhost along with the files: installation-guide_20150417.dsc installation-guide_20150417.tar.gz installation-guide-amd64_20150417_all.deb installation-guide-arm64_20150417_all.deb installation-guide-armel_20150417_all.deb installation-guide-armhf_20150417_all.deb installation-guide-i386_20150417_all.deb installation-guide-kfreebsd-amd64_20150417_all.deb installation-guide-kfreebsd-i386_20150417_all.deb installation-guide-mips_20150417_all.deb installation-guide-mipsel_20150417_all.deb installation-guide-powerpc_20150417_all.deb installation-guide-ppc64el_20150417_all.deb installation-guide-s390x_20150417_all.deb 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/e1yj8hs-00064s...@franck.debian.org
Bug#782673: marked as done (installation-guide: doesn't notice errors within the for loop)
Your message dated Fri, 17 Apr 2015 16:21:25 + with message-id and subject line Bug#782673: fixed in installation-guide 20150417 has caused the Debian Bug report #782673, regarding installation-guide: doesn't notice errors within the for loop 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.) -- 782673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: installation-guide Version: 20150323 Severity: important Hi, as noted while discussing with Mattia Rizzolo: an individual failure (e.g. ppc64el / cs / pdf as of r69765) doesn't trigger an FTBFS, so a “debuild -b” on a multicore machine might lead to believe everything is OK while some files (e.g. ./debian/manual/ppc64el/cs/install.cs.pdf) are missing. Samuel mentioned errors aren't recorded in the for loop, and have that bug report on his todolist. Mraw, KiBi. --- End Message --- --- Begin Message --- Source: installation-guide Source-Version: 20150417 We believe that the bug you reported is fixed in the latest version of installation-guide, 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 782...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated installation-guide 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: SHA512 Format: 1.8 Date: Sat, 28 Mar 2015 10:10:34 +0100 Source: installation-guide Binary: installation-guide-amd64 installation-guide-arm64 installation-guide-armel installation-guide-armhf installation-guide-i386 installation-guide-kfreebsd-amd64 installation-guide-kfreebsd-i386 installation-guide-mips installation-guide-mipsel installation-guide-powerpc installation-guide-ppc64el installation-guide-s390x Architecture: source all Version: 20150417 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Samuel Thibault Description: installation-guide-amd64 - Debian installation guide for amd64 installation-guide-arm64 - Debian installation guide for arm64 installation-guide-armel - Debian installation guide for armel installation-guide-armhf - Debian installation guide for armhf installation-guide-i386 - Debian installation guide for i386 installation-guide-kfreebsd-amd64 - Debian installation guide for kFreeBSD amd64 installation-guide-kfreebsd-i386 - Debian installation guide for kFreeBSD i386 installation-guide-mips - Debian installation guide for mips installation-guide-mipsel - Debian installation guide for mipsel installation-guide-powerpc - Debian installation guide for powerpc installation-guide-ppc64el - Debian installation guide for powerpc installation-guide-s390x - Debian installation guide for s390x Closes: 782673 782765 Changes: installation-guide (20150417) unstable; urgency=medium . [ Stéphane Blondon ] * Improve html table aspect. * Add missing "warning" icon. . [ Karsten Merker ] * Add a "Debian-provided U-Boot (system firmware) images" subsection in the "Pre-Installation Hardware and Operating System Setup" section and add a link to the U-Boot images in the "Downloading Files from Debian Mirrors" section. * Add a "Using pre-built SD-card images with the installer" subsection in the "Booting the Installer on ARM" section. * Correct the number of supported architectures (arm64 and ppc64el are release architectures now). * Add a "Pre-built netboot tarball" subsection for armhf in the "Booting by TFTP" section. * Add a "Console configuration" subsection in the "Booting the Installer on ARM" section. * Add information that the IXP4xx platform support in Jessie is limited to dist-upgrades from Wheezy, that new installations are not supported for the IXP4xx platform and that kernel support for it will definitely be dropped in Stretch. * Add LinkSprite pcDuino3 to the list of supported armhf systems. * Change http.debian.net references to httpredir.debian.org. . [ Holger Wansing ]
Bug#782765: marked as done (d-i.debian.org: copying images fails on dillon (manual build))
Your message dated Fri, 17 Apr 2015 16:21:25 + with message-id and subject line Bug#782765: fixed in installation-guide 20150417 has caused the Debian Bug report #782765, regarding d-i.debian.org: copying images fails on dillon (manual build) 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.) -- 782765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: d-i.debian.org Severity: normal I suppose this happens after some files were added under images/ due to the recent CSS (re)work, it's possibly the following bit in the manual's build/buildone.sh: | # Copy the custom css stylesheet to the destination directory | cp $stylesheet_css $destdir/html/ | cp -r $stylesheet_images_dir $destdir/html/images Not sure whether we should adjust how the building works on dillon or whether we should change something on the manual side. Keeping this in a bug report for now since it's not critical for RC3. Mraw, KiBi. Messages from the crontab run follow: mv: cannot move `./build.out.en.i386/html/images' to `/srv/d-i.debian.org/www/manual/en.i386/images': File exists mv: cannot move `./build.out.en.amd64/html/images' to `/srv/d-i.debian.org/www/manual/en.amd64/images': File exists mv: cannot move `./build.out.en.arm64/html/images' to `/srv/d-i.debian.org/www/manual/en.arm64/images': File exists mv: cannot move `./build.out.en.armel/html/images' to `/srv/d-i.debian.org/www/manual/en.armel/images': File exists mv: cannot move `./build.out.en.armhf/html/images' to `/srv/d-i.debian.org/www/manual/en.armhf/images': File exists mv: cannot move `./build.out.en.mips/html/images' to `/srv/d-i.debian.org/www/manual/en.mips/images': File exists mv: cannot move `./build.out.en.mipsel/html/images' to `/srv/d-i.debian.org/www/manual/en.mipsel/images': File exists mv: cannot move `./build.out.en.powerpc/html/images' to `/srv/d-i.debian.org/www/manual/en.powerpc/images': File exists mv: cannot move `./build.out.en.ppc64el/html/images' to `/srv/d-i.debian.org/www/manual/en.ppc64el/images': File exists mv: cannot move `./build.out.en.s390x/html/images' to `/srv/d-i.debian.org/www/manual/en.s390x/images': File exists mv: cannot move `./build.out.en.kfreebsd-i386/html/images' to `/srv/d-i.debian.org/www/manual/en.kfreebsd-i386/images': File exists mv: cannot move `./build.out.en.kfreebsd-amd64/html/images' to `/srv/d-i.debian.org/www/manual/en.kfreebsd-amd64/images': File exists mv: cannot move `./build.out.cs.i386/html/images' to `/srv/d-i.debian.org/www/manual/cs.i386/images': File exists mv: cannot move `./build.out.cs.amd64/html/images' to `/srv/d-i.debian.org/www/manual/cs.amd64/images': File exists mv: cannot move `./build.out.cs.arm64/html/images' to `/srv/d-i.debian.org/www/manual/cs.arm64/images': File exists mv: cannot move `./build.out.cs.armel/html/images' to `/srv/d-i.debian.org/www/manual/cs.armel/images': File exists mv: cannot move `./build.out.cs.armhf/html/images' to `/srv/d-i.debian.org/www/manual/cs.armhf/images': File exists mv: cannot move `./build.out.cs.mips/html/images' to `/srv/d-i.debian.org/www/manual/cs.mips/images': File exists mv: cannot move `./build.out.cs.mipsel/html/images' to `/srv/d-i.debian.org/www/manual/cs.mipsel/images': File exists mv: cannot move `./build.out.cs.powerpc/html/images' to `/srv/d-i.debian.org/www/manual/cs.powerpc/images': File exists mv: cannot move `./build.out.cs.ppc64el/html/images' to `/srv/d-i.debian.org/www/manual/cs.ppc64el/images': File exists mv: cannot move `./build.out.cs.s390x/html/images' to `/srv/d-i.debian.org/www/manual/cs.s390x/images': File exists mv: cannot move `./build.out.cs.kfreebsd-i386/html/images' to `/srv/d-i.debian.org/www/manual/cs.kfreebsd-i386/images': File exists mv: cannot move `./build.out.cs.kfreebsd-amd64/html/images' to `/srv/d-i.debian.org/www/manual/cs.kfreebsd-amd64/images': File exists mv: cannot move `./build.out.da.i386/html/images' to `/srv/d-i.debian.org/www/manual/da.i386/images': File exists mv: cannot move `./build.out.da.amd64/html/images' to `/srv/d-i.debian.org/www/manual/da.amd64/images': File exists mv: cannot move `./build.out.da.arm64/html/images' to `/srv/d-i.debian.org/www/manual/da.arm64/images': File exists mv: cannot
installation-guide_20150417_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 28 Mar 2015 10:10:34 +0100 Source: installation-guide Binary: installation-guide-amd64 installation-guide-arm64 installation-guide-armel installation-guide-armhf installation-guide-i386 installation-guide-kfreebsd-amd64 installation-guide-kfreebsd-i386 installation-guide-mips installation-guide-mipsel installation-guide-powerpc installation-guide-ppc64el installation-guide-s390x Architecture: source all Version: 20150417 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Samuel Thibault Description: installation-guide-amd64 - Debian installation guide for amd64 installation-guide-arm64 - Debian installation guide for arm64 installation-guide-armel - Debian installation guide for armel installation-guide-armhf - Debian installation guide for armhf installation-guide-i386 - Debian installation guide for i386 installation-guide-kfreebsd-amd64 - Debian installation guide for kFreeBSD amd64 installation-guide-kfreebsd-i386 - Debian installation guide for kFreeBSD i386 installation-guide-mips - Debian installation guide for mips installation-guide-mipsel - Debian installation guide for mipsel installation-guide-powerpc - Debian installation guide for powerpc installation-guide-ppc64el - Debian installation guide for powerpc installation-guide-s390x - Debian installation guide for s390x Closes: 782673 782765 Changes: installation-guide (20150417) unstable; urgency=medium . [ Stéphane Blondon ] * Improve html table aspect. * Add missing "warning" icon. . [ Karsten Merker ] * Add a "Debian-provided U-Boot (system firmware) images" subsection in the "Pre-Installation Hardware and Operating System Setup" section and add a link to the U-Boot images in the "Downloading Files from Debian Mirrors" section. * Add a "Using pre-built SD-card images with the installer" subsection in the "Booting the Installer on ARM" section. * Correct the number of supported architectures (arm64 and ppc64el are release architectures now). * Add a "Pre-built netboot tarball" subsection for armhf in the "Booting by TFTP" section. * Add a "Console configuration" subsection in the "Booting the Installer on ARM" section. * Add information that the IXP4xx platform support in Jessie is limited to dist-upgrades from Wheezy, that new installations are not supported for the IXP4xx platform and that kernel support for it will definitely be dropped in Stretch. * Add LinkSprite pcDuino3 to the list of supported armhf systems. * Change http.debian.net references to httpredir.debian.org. . [ Holger Wansing ] * Add ppc64el bits. . [ Wookey ] * Update the "Supported Hardware" section for arm64. . [ Steve McIntyre ] * Update stats for number of packages per arch, number of DDs and number of mailing lists * Add mention of BD-ROM like CD/DVD * Lots of updates to documentation about EFI * Make USB boot a more prominent option for booting the installer on x86 * Remove the old hdX device names, switch to sdX for disks * Various fixes for arm* support * Loads of trivial translations. . [ Samuel Thibault ] * Add missing "set -e" in build/Makefile to trap build failures. Closes: #782673. * Loads of trivial translations. * Fix moving the html images when destination already contains a built manual. Closes: #782765. Checksums-Sha1: 12d09b7525062de909a56e36ce63eecff547ab56 2848 installation-guide_20150417.dsc 5b51829bd9451a91b7552041bcddae77f585fb3e 9116471 installation-guide_20150417.tar.gz 07900f38bb15d299de52a459d7223e7cc82daaff 15227330 installation-guide-amd64_20150417_all.deb 87707884f6ed1cbd15cf1d064145f689988429b8 13585748 installation-guide-arm64_20150417_all.deb afba8bd9a0f492875c25540e3fafc51f6bf407cf 13629688 installation-guide-armel_20150417_all.deb 4fd1c6920abb70ba143b6979a13f79e610a65a14 13805674 installation-guide-armhf_20150417_all.deb f3bb99c56cf91ba9ea027b4131892cd19c1559c6 15291790 installation-guide-i386_20150417_all.deb 2863c9d7f80615137f1cea680201d4515a21225f 13492742 installation-guide-kfreebsd-amd64_20150417_all.deb 4b755425d1f7b2247068b26e8f3cb7c3a1705e0c 13460856 installation-guide-kfreebsd-i386_20150417_all.deb 8e85be3c734d3c9b0fc5d0842a0ba2764b217999 13034580 installation-guide-mips_20150417_all.deb bd2dddc157cf234047fca4c074bedbb141c460e8 12933128 installation-guide-mipsel_20150417_all.deb fcf393631e7fbc6eae975f4eb06d1cf8f9ed407c 14662538 installation-guide-powerpc_20150417_all.deb 08a9621419f60b0d8606f1c3bd7940f278b374da 13165510 installation-guide-ppc64el_20150417_all.deb 701af8b9054e1144e639f42310515783a2ba03d0 11889674 installation-guide-s390x_20150417_all.deb Ch
Bug#779546: Further information
Cyril Brulebois (2015-03-04): > Ben Hutchings (2015-03-03): > > Yes, that's right. The problem is that we now detect missing firmware > > by scraping the kernel log, and we still pick up old ones after > > installing firmware and poking the driver. > > > > I think we could solve this by noting the timestamp at the bottom of the > > kernel log every time we scan it, then only checking lines after that on > > the next scan. > > I think that's an idea I mentioned in a previous bug report, yes. I'll > try and see if I can implement & verify this before RC2. I've now implemented that in the following commit: http://anonscm.debian.org/cgit/d-i/hw-detect.git/commit/?id=1fda53e722375a3ea580f465f7e716d9a3b5da36 Pasting the commit message here for reference: | Make sure not to look at past lines in dmesg (Closes: #779546). | | If user supplies firmware on a USB stick, missing firmware detection | happens again, and if dmesg hasn't received enough lines to get rid of | old “firmware: failed to load” entries, the situation looks like it | hasn't improved. | | To avoid such a loop, note the timestamp of the last dmesg line after | having scanned for such lines, and in case missing firmware detection | runs again, use this timestamp to filter out previous lines in case it's | still present in the new dmesg output; or use the whole dmesg output if | that timestamp has vanished. | | Tested successfully on bare metal with iwlwifi, in 3 cases: | - USB stick with firmware in place before boot: seamless. | - USB stick with firmware plugged after the “search on removable media” |prompt: OK. | - USB stick with firmware not plugged after the first “search on |removable media” prompt, but on the second try (so that there's a |search that doesn't find anything): OK. | | Tested-by: Cyril Brulebois | Signed-off-by: Cyril Brulebois And as mentioned on IRC… certainly not the prettiest code ever, but one of the criterion was “must work and be built before 19:52”. Let's see how that works or breaks for others through D-I Jessie RC3… Mraw, KiBi. signature.asc Description: Digital signature
Bug#779546: marked as done (debian-installer: Debian-installer does not load iwlwifi firmware correctly)
Your message dated Fri, 17 Apr 2015 17:33:55 + with message-id and subject line Bug#779546: fixed in hw-detect 1.108 has caused the Debian Bug report #779546, regarding debian-installer: Debian-installer does not load iwlwifi firmware correctly 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.) -- 779546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Version: Debian Installer Jessie RC 1 release Severity: important When loading non-free firmware for installation of iwlwifi the debian-installer looks for the wrong .ucode file. I have the following card: 09:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak] Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi And during install it gets correctly identified as a module that needs additional firmware. After spending some time getting the partition table on the usb key correct(Another bug I didn't know about), I finally was able to make a usb key with the nonfree firmware. It seems like the installer doesn't know it's supposed to look for iwlwifi-1000-5.ucode. In the installer log I get things like these: check-missing-firmware: looking for firmware file iwlwifi-1000-5.ucode requested by iwlwifi However, on the curses display it never says anything about the 1000.5 file. Instead, it looks like this: check-missing-firmware: missing firmware files (iwlwifi-1000-4.ucode iwlwifi-1000-3.ucode iwlwifi-1000-2.ucode iwlwifi-1000-1.ucode iwlwifi-1000-4.ucode iwlwifi-1000-3.ucode iwlwifi-1000-2.ucode iwlwifi-1000-1.ucode iwlwifi-1000-4.ucode iwlwifi-1000-3.ucode iwlwifi-1000-2.ucode iwlwifi-1000-1.ucode) Which led me to guess that it doesn't actually look for the 1000.5 file. I downloaded the firmware-iwlwifi package and manally copied the iwlwifi-1000-5.ucode file and gave it names iwlwifi-1000-4.ucode and downward until I had all of the ones included in the list shown above.(Maybe I just needed 1000.4 but I wasn't quite sure) After rebuilding the deb with these files in it, installation went along as normal. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: hw-detect Source-Version: 1.108 We believe that the bug you reported is fixed in the latest version of hw-detect, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois (supplier of updated hw-detect 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: SHA1 Format: 1.8 Date: Fri, 17 Apr 2015 19:24:22 +0200 Source: hw-detect Binary: hw-detect ethdetect disk-detect driver-injection-disk-detect archdetect Architecture: source amd64 all Version: 1.108 Distribution: unstable Urgency: high Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Description: archdetect - Hardware architecture detector (udeb) disk-detect - Detect disk drives (udeb) driver-injection-disk-detect - Detect OEM driver injection disks (udeb) ethdetect - Detect network hardware and load kernel drivers for it (udeb) hw-detect - Detect hardware and load kernel drivers for it (udeb) Closes: 779546 Changes: hw-detect (1.108) unstable; urgency=high . * Make sure not to look at past lines in dmesg (Closes: #779546): - If user supplies firmware on a USB stick, missing firmware detection happens again, and if dmesg hasn't received enough lines to get rid of old “firmware: failed to load” entries, the situation looks like it hasn't improved. - To avoid such
Re: Bug#782712: pre-upload unblock request: systemd/215-17 for RC bug #751707
Hello Niels, Niels Thykier [2015-04-17 17:55 +0200]: > Just to clarify, are we still intending to do a systemd update prior to > Jessie with -17 and then now also a p-u (i.e. for 8.1) for ecryptfs? That's still my intent, yes, primarily to avoid people who have this set up in wheezy already (#751707 has at least two reporters) upgrade and find their swap partition gone and boot stuck. > If we are /not/ pulling systemd for Jessie release next release, we can > document the issue for the release notes (possibly as a "non-standard" > setup given d-i in Debian does not create this kind of disks, if I > understand the discussion correctly). That's possible as well, of course. In this case you should revert to sysvinit (or upstart) straight after upgrading, *before* you reboot (after it's too late). I documented the manual upgrade fix on the LP bug a while ago: https://launchpad.net/bugs/953875 (in the description). Maybe some bits could also be stolen from there. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.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/20150417172230.gq3...@piware.de
Processing of hw-detect_1.108_amd64.changes
hw-detect_1.108_amd64.changes uploaded successfully to localhost along with the files: hw-detect_1.108.dsc hw-detect_1.108.tar.xz hw-detect_1.108_amd64.udeb ethdetect_1.108_all.udeb disk-detect_1.108_all.udeb driver-injection-disk-detect_1.108_all.udeb archdetect_1.108_amd64.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/e1yja2e-f3...@franck.debian.org
hw-detect_1.108_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 17 Apr 2015 19:24:22 +0200 Source: hw-detect Binary: hw-detect ethdetect disk-detect driver-injection-disk-detect archdetect Architecture: source amd64 all Version: 1.108 Distribution: unstable Urgency: high Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Description: archdetect - Hardware architecture detector (udeb) disk-detect - Detect disk drives (udeb) driver-injection-disk-detect - Detect OEM driver injection disks (udeb) ethdetect - Detect network hardware and load kernel drivers for it (udeb) hw-detect - Detect hardware and load kernel drivers for it (udeb) Closes: 779546 Changes: hw-detect (1.108) unstable; urgency=high . * Make sure not to look at past lines in dmesg (Closes: #779546): - If user supplies firmware on a USB stick, missing firmware detection happens again, and if dmesg hasn't received enough lines to get rid of old “firmware: failed to load” entries, the situation looks like it hasn't improved. - To avoid such a loop, note the timestamp of the last dmesg line after having scanned for such lines, and in case missing firmware detection runs again, use this timestamp to filter out previous lines in case it's still present in the new dmesg output; or use the whole dmesg output if that timestamp has vanished. - Tested successfully on bare metal with iwlwifi. Checksums-Sha1: 7d31647e7ec89c0aefcdbe44fa24657e6af8f49c 2017 hw-detect_1.108.dsc dca72ea9d88b2252a1e6cbcb613f6b088c5b5d32 180476 hw-detect_1.108.tar.xz 6f1b041c114cb575824162eb6f879714f8fb0014 128988 hw-detect_1.108_amd64.udeb bdec4f0dfaf63edafb449f55ff9e00a95d1ca652 36084 ethdetect_1.108_all.udeb 6b69f341e0ccd8219fb1d647b1526f8e22edbdb9 27648 disk-detect_1.108_all.udeb 283e90713c66723c7946fa5d255f219f18039297 15148 driver-injection-disk-detect_1.108_all.udeb 23114ee2495540e3e6e7287a67e95ae6c0d4ac64 2526 archdetect_1.108_amd64.udeb Checksums-Sha256: 6159e7debbd325c903c488d64668bff601053ce0eac9968ec65f6edc3aa768c2 2017 hw-detect_1.108.dsc c7943b4e9fb9592fffa0e826d9a36c88fb33540b3886b04396d01113ecc47fb8 180476 hw-detect_1.108.tar.xz 4cdf37c790df89dece99ee83fe6b8629a2a2908cc8502f41df4ca32c78a557dc 128988 hw-detect_1.108_amd64.udeb 5b64cbc76ed889905ee82936b4a81bb37e228575b26f971d274ffcf25891c526 36084 ethdetect_1.108_all.udeb a9fe613d3694610c913d99c5efc5e70e5404aa9b1e43356231cc94c3a206e797 27648 disk-detect_1.108_all.udeb b953a161566d75f722853f77debb87a795ba9c83f84439b8db859762467b0738 15148 driver-injection-disk-detect_1.108_all.udeb 447ec8edf754a6e13eb829b19196de9ccaafb17b74ae7561e91fb1d27e196a3c 2526 archdetect_1.108_amd64.udeb Files: 1ebd472a15e6546b175b46bb791e9660 2017 debian-installer standard hw-detect_1.108.dsc ac5df7611ce969ec1eb07f2591a6c943 180476 debian-installer standard hw-detect_1.108.tar.xz c16430515568041632f2622298980002 128988 debian-installer standard hw-detect_1.108_amd64.udeb 4fd3df9f2b84494aa2c2801a2fd835dc 36084 debian-installer optional ethdetect_1.108_all.udeb 8d343a8eadeede0068c75be0b2750f68 27648 debian-installer optional disk-detect_1.108_all.udeb 25433c8a6515f1adb572ec97cad8ce12 15148 debian-installer optional driver-injection-disk-detect_1.108_all.udeb f8bd66fce71bedb53c5c14e4274f3910 2526 debian-installer standard archdetect_1.108_amd64.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVMUIzAAoJEP+RSvDCs1UgyU0P/0ofZ9f6Tu4nrd009Bqbh1FE WxCu9ACI5gwft9+99pwT44m9nAGo9+QkrVC+CsZ9IYWjaSodprm9PhHZxSVnSamX ICyhA5Oex1UF1B8mO594b2nTMxAn8AYJB93qjM+bVy2UI3olVH866Qe8kQfwsoob Hssf7PcHxqQZgAXNdG1p6G8nXoIw6BnGg7A5Mx0AbtLH9OmQsn62WZMHNkB9nnGk zinDuLRRea2PTm7B1gXG03VFM1DC5RsZRp4gSbo+YVBsJDidRwcaA8Bu/3/cX0gS CS5iggEFdYOs3IlSuyGLe7WV0kF7mrKXWMpwt9ZehxYwtR2AB5IHRI7W3zT1DvUr nbjPA8s0dx4QX+ts6UDgTn0DYfQlDhK4cxioU/KNHvG6Y34UF6b2jYwa1whoi8ig DwK02DASTc3tbzsJqqwYjXa4JiS6o/F2vHJIwRsF+4WRqoeDnVyV9jiBiJaul/Vo sS9Ev8pNSEq2f8hZo9bsAWw7pbUDwTCSA50uELSISfKOq1xqCZOxXeLmQICejvGn vyZZQVYetE5K6hfjOOiVZkNx4BnybBiNRz4N2RffTBu/Vzo/Z1Bkz8uYtrnmSl8l E8zOe7V4EzLaQhYlwODRUAKGxJLjmu8KMVDVeIfgbJs1SCYKa095xGLIuoeTVccD i7up/+WRkrW0zdrMfy2x =+GOV -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/e1yja9l-00015d...@franck.debian.org
Hints for d-i jessie RC3, part 5
Hi people, here's a fifth (and hopefully last) round of unblock/unblock-udeb hints for the upcoming d-i jessie RC3. Don't hesitate to ask questions if anything looks fishy. I've added urgents this time, to meet the timeline I've proposed (https://lists.debian.org/debian-boot/2015/04/msg00264.html). There's also the brltty unblock request dealt with in #782743. From a few follow-ups on debian-accessibility@, it looks like the situation isn't ideal yet, but I suppose not hanging is better than hanging, so keeping the hints Ivo has in place is probably OK; Cc-ing Samuel and his unblock bug report to make sure. I'm quite unhappy with my only having looked at the firmware thing today but live tests seem quite encouraging and I feel that giving this more user exposure before 8.0 is the right thing to do at this point. (I've uploaded most of these packages, you may want to make sure I didn't screw up my self-review.) # improve firmware support, avoiding loops (#779546); just uploaded, # hopefully builds will be there on time: unblock hw-detect/1.108 unblock-udeb hw-detect/1.108 urgent hw-detect/1.108 # stop polluting /etc/fstab with USB things: unblock partman-target/96 unblock-udeb partman-target/96 urgent partman-target/96 # l10n-only: unblock console-setup/1.122 unblock-udeb console-setup/1.122 urgent console-setup/1.122 # l10n-only: unblock partman-crypto/81 unblock-udeb partman-crypto/81 urgent partman-crypto/81 # l10n-only unblock tasksel/3.31 urgent tasksel/3.31 Thanks for your time. Mraw, KiBi. signature.asc Description: Digital signature
Re: Hints for d-i jessie RC3, part 5
Cyril Brulebois (2015-04-17): > # improve firmware support, avoiding loops (#779546); just uploaded, > # hopefully builds will be there on time: > unblock hw-detect/1.108 > unblock-udeb hw-detect/1.108 > urgent hw-detect/1.108 > > # stop polluting /etc/fstab with USB things: > unblock partman-target/96 > unblock-udeb partman-target/96 > urgent partman-target/96 > > # l10n-only: > unblock console-setup/1.122 > unblock-udeb console-setup/1.122 > urgent console-setup/1.122 > > # l10n-only: > unblock partman-crypto/81 > unblock-udeb partman-crypto/81 > urgent partman-crypto/81 > > # l10n-only > unblock tasksel/3.31 > urgent tasksel/3.31 And since there were people caring about it (thanks!), it wasn't on my todo-list and I forgot to mention it: # doc doc doc! unblock installation-guide/20150417 urgent installation-guide/20150417 Mraw, KiBi. signature.asc Description: Digital signature
Re: netinst image on USB stick asks for cdrom
On Fri, 2015-04-17 at 15:40 +0200, w...@vienna.at wrote: > > No because netinst images generally work on USB sticks. > > [...] > > > [2] sudo cp *.iso /dev/sdb > > [...] > > Why *.iso? Are you sure this matched only one file? > > Of course *iso, what else? *img? > But i'd be surprised if cp ever can manage that copying > Because there should the 512 bit at the very beginning! > For the information where the *iso-bootloader is expected - > by BIOS. Or does one start with a bootloader from anywhere > else being able to start the image on the stick? The #1 ISO images for x86 include an MBR containing the first stage of syslinux, an Apple partition map and for amd64 a GPT with an EFI boot partition containing GRUB. So, yes, copying to the whole-disk device is right, though it is unusual to use cp for this. > And also keep in mind, dd only will manage sdb, never sdb1. sdb1 is part of sdb. Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Re: netinst image on USB stick asks for cdrom
On Fri, 2015-04-17 at 16:20 +0200, Thomas Koch wrote: > On Friday, April 17, 2015 03:02:28 PM Ben Hutchings wrote: > > > [2] sudo cp *.iso /dev/sdb > > > > Why *.iso? Are you sure this matched only one file? > > Sorry. I wanted to keep the mail short. Of course I specified the correct > file. > > Meanwhile I repeated the process with the RC2 netinst and even with the RC2 > CD1 with exactly the same result. > > I've not tried anymore because I just wanted to get a shell on a laptop to > decide whether I buy it and used Knoppix instead. > > It might rather be that the USB stick has a defect? Can you try filling the USB stick with zeroes before writing the image? Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Re: Hints for d-i jessie RC3, part 5
Ivo De Decker (2015-04-17): > As noted on irc: when there are no new lines in dmesg, the timestamp is empty, > and on the next run, the entire dmesg is used. This is probably still better > than what was done before, so added the hints anyway. Good catch, thanks. Documented in a bug report before I got your reply. :) > All added. Thanks! Mraw, KiBi. signature.asc Description: Digital signature
Re: Hints for d-i jessie RC3, part 5
Cyril Brulebois, le Fri 17 Apr 2015 19:52:07 +0200, a écrit : > here's a fifth (and hopefully last) round of unblock/unblock-udeb hints > for the upcoming d-i jessie RC3. Don't hesitate to ask questions if > anything looks fishy. I've added urgents this time, to meet the > timeline I've proposed > (https://lists.debian.org/debian-boot/2015/04/msg00264.html). Doesn't installation-guide need a hint too? Samuel -- 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/20150417183316.ga7...@type.youpi.perso.aquilenet.fr
Bug#782780: hw-detect: edge case in checking-missing-firmware: timestamp handling
Package: hw-detect Version: 1.108 Severity: important Spotted by Ivo while reviewing the rushed code addition: “ - if get_fresh_dmesg doens't find any new lines in dmesg, the timestamp is empty - next time it runs, it outputs the entire dmesg again ” It seems it would make sense to check whether $dmesg_file is empty, so that we don't forget about the previously-saved timestamp. It seems to me a fix could go through unstable→testing (as stretch), and be backported for 8.1 (as opposed to re-uploading after RC3, before 8.0). Mraw, KiBi. -- 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/20150417182838.6192.85177.report...@arya.home.mraw.org
Re: Hints for d-i jessie RC3, part 5
Hi, On Fri, Apr 17, 2015 at 07:55:35PM +0200, Cyril Brulebois wrote: > Cyril Brulebois (2015-04-17): > > # improve firmware support, avoiding loops (#779546); just uploaded, > > # hopefully builds will be there on time: > > unblock hw-detect/1.108 > > unblock-udeb hw-detect/1.108 > > urgent hw-detect/1.108 As noted on irc: when there are no new lines in dmesg, the timestamp is empty, and on the next run, the entire dmesg is used. This is probably still better than what was done before, so added the hints anyway. > > # stop polluting /etc/fstab with USB things: > > unblock partman-target/96 > > unblock-udeb partman-target/96 > > urgent partman-target/96 > > > > # l10n-only: > > unblock console-setup/1.122 > > unblock-udeb console-setup/1.122 > > urgent console-setup/1.122 > > > > # l10n-only: > > unblock partman-crypto/81 > > unblock-udeb partman-crypto/81 > > urgent partman-crypto/81 > > > > # l10n-only > > unblock tasksel/3.31 > > urgent tasksel/3.31 > > And since there were people caring about it (thanks!), it wasn't on my > todo-list and I forgot to mention it: > > # doc doc doc! > unblock installation-guide/20150417 > urgent installation-guide/20150417 All added. Cheers, Ivo -- 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/20150417182714.ga29...@ugent.be
Bug#779546: Further information
On Fri, 2015-04-17 at 19:29 +0200, Cyril Brulebois wrote: > Cyril Brulebois (2015-03-04): > > Ben Hutchings (2015-03-03): > > > Yes, that's right. The problem is that we now detect missing firmware > > > by scraping the kernel log, and we still pick up old ones after > > > installing firmware and poking the driver. > > > > > > I think we could solve this by noting the timestamp at the bottom of the > > > kernel log every time we scan it, then only checking lines after that on > > > the next scan. > > > > I think that's an idea I mentioned in a previous bug report, yes. I'll > > try and see if I can implement & verify this before RC2. > > I've now implemented that in the following commit: > > http://anonscm.debian.org/cgit/d-i/hw-detect.git/commit/?id=1fda53e722375a3ea580f465f7e716d9a3b5da36 [...] For what it's worth, I've read this and it looks functional. Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Re: netinst image on USB stick asks for cdrom
On Fri, 2015-04-17 at 09:41 +0200, Thomas Koch wrote: > Hi, > > I took todays (2015-04-16 18:20) daily Jessie netinstaller build[1], copied > the image to an USB stick[2] and started the installation. > > At the "Partition disks" step the installer asked me: > > "/media/cdrom/:Please insert the disc labeled: 'Debian GNU/Linux > Jessie-DI-rc1 > _Jessie_ - Official RC amd64 NETINST Binary-1 2015-01-09-01:04' in the drive > '/media/cdrom/' and press enter. > See Bug#764587 Phil. -- Philip Charles; 39a Paterson Street, Abbotsford, Dunedin, New Zealand +64 3 488 2818Fax +64 3 488 2875Mobile 027 663 4453 phil...@copyleft.co.nz - personal.i...@copyleft.co.nz - business -- 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/1429309892.12032.28.ca...@copyleft.co.nz
Processed: reassign 782451 to src:zabbix, reassign 782699 to installation-reports ...
Processing commands for cont...@bugs.debian.org: > reassign 782451 src:zabbix Bug #782451 [zabbix-proxy] zabbix-proxy: [wishlist] remove conflict with zabbix-server Warning: Unknown package 'zabbix-proxy' Bug reassigned from package 'zabbix-proxy' to 'src:zabbix'. Ignoring request to alter found versions of bug #782451 to the same values previously set Ignoring request to alter fixed versions of bug #782451 to the same values previously set > reassign 782699 installation-reports Bug #782699 [debian-boot] debian-boot: IPv6 prefix notation in the installer Warning: Unknown package 'debian-boot' Bug reassigned from package 'debian-boot' to 'installation-reports'. Ignoring request to alter found versions of bug #782699 to the same values previously set Ignoring request to alter fixed versions of bug #782699 to the same values previously set > reassign 782701 installation-reports Bug #782701 [debian-boot] debian-boot: Dublicate address detection needed Warning: Unknown package 'debian-boot' Bug reassigned from package 'debian-boot' to 'installation-reports'. No longer marked as found in versions jessie. Ignoring request to alter fixed versions of bug #782701 to the same values previously set > reassign 628571 src:ace 6.0.1-2 Bug #628571 [libtao-2.0.1] Public method TAO::ORB::default_svc_conf_entries() is not exported Warning: Unknown package 'libtao-2.0.1' Bug reassigned from package 'libtao-2.0.1' to 'src:ace'. No longer marked as found in versions ace/6.0.1-2. Ignoring request to alter fixed versions of bug #628571 to the same values previously set Bug #628571 [src:ace] Public method TAO::ORB::default_svc_conf_entries() is not exported Marked as found in versions ace/6.0.1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 628571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628571 782451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782451 782699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782699 782701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782701 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.14293167375.transcr...@bugs.debian.org
Re: Hints for d-i jessie RC3, part 5
Cyril Brulebois (2015-04-17): > Hi people, > > here's a fifth (and hopefully last) round of unblock/unblock-udeb hints > for the upcoming d-i jessie RC3. Don't hesitate to ask questions if > anything looks fishy. I've added urgents this time, to meet the > timeline I've proposed > (https://lists.debian.org/debian-boot/2015/04/msg00264.html). > > There's also the brltty unblock request dealt with in #782743. From a > few follow-ups on debian-accessibility@, it looks like the situation > isn't ideal yet, but I suppose not hanging is better than hanging, so > keeping the hints Ivo has in place is probably OK; Cc-ing Samuel and his > unblock bug report to make sure. > > > I'm quite unhappy with my only having looked at the firmware thing today > but live tests seem quite encouraging and I feel that giving this more > user exposure before 8.0 is the right thing to do at this point. > > > (I've uploaded most of these packages, you may want to make sure I > didn't screw up my self-review.) > > > # improve firmware support, avoiding loops (#779546); just uploaded, > # hopefully builds will be there on time: > unblock hw-detect/1.108 > unblock-udeb hw-detect/1.108 > urgent hw-detect/1.108 > > # stop polluting /etc/fstab with USB things: > unblock partman-target/96 > unblock-udeb partman-target/96 > urgent partman-target/96 > > # l10n-only: > unblock console-setup/1.122 > unblock-udeb console-setup/1.122 > urgent console-setup/1.122 > > # l10n-only: > unblock partman-crypto/81 > unblock-udeb partman-crypto/81 > urgent partman-crypto/81 > > # l10n-only > unblock tasksel/3.31 > urgent tasksel/3.31 All are in, including installation-guide; thanks everyone! Mraw, KiBi. signature.asc Description: Digital signature
Bug#782798: installation-reports: jessie doesnt use a repo by default with BDROM ISO dated 2015 04 13-06:57
Package: installation-reports Severity: important Dear Maintainer, The debian install BDROM ISO of Jigdo testing labeled: 2015 04 13-06:57 from http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-bd/ selects no repository by default, leaving a misconfigured /etc/apt/sources.list file. ALSO: Installing from said BDROM image, I cannot install i386 libs by default without commenting out the (amd64) BDROM in /etc/apt/sources.list and re-adding the following repo information(I dont know if this is by default or a BUG): (this is after adding the i386 archetecture) deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free # jessie-updates, previously known as 'volatile' deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free deb-src http://ftp.debian.org/debian/ jessie-updates contrib main non-free # jessie-backports, previously on backports.debian.org deb http://http.us.debian.org/debian/ jessie main non-free contrib -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-bd/debian-testing-amd64-BD-1.jigdo Date: Machine: custom PC Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: -- 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="8 (jessie) - installer build 20150413-00:02" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux livingroom 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-1 (2015-04-08) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) [1002:5a14] (rev 02) lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) [1002:5a14] lspci -knn: 00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) [1002:5a16] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D) [1002:5a18] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port E) [1002:5a19] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port F) [1002:5a1a] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port G) [1002:5a1b] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port H) [1002:5a1c] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port A) [1002:5a1d] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:0b.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (NB-SB link) [1002:5a1f] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:0d.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port B) [1002:5a1e] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] (rev 40) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:84dd] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] lspci -knn: Kernel driver in use: ohci-pci
