Re: Bug#737580: marked as done (ufsutils-udeb: mkfs.ufs: DIOCGMEDIASIZE: Inappropriate ioctl for device)
On 08/03/2014 13:21, Debian Bug Tracking System wrote: > ufsutils (9.2-3.1) unstable; urgency=high > . >* Non-maintainer upload. >* Steal the following patch from the 10 branch, fixing failures to run > mkfs.ufs, notably from d-i (Closes: #737580): > 05_wipe_otherfs.patch: Handle DIOCGMEDIASIZE failure gracefully. >* Fix FTBFS due to missing by adding a libutil-freebsd-dev > build-dep (Closes: #741088). Thank you. I assume your plan is to include ufsutils 9.2 in jessie alpha 1? In that case I would postpone upload of 10.0, which I planned to do tomorrow. -- Robert Millan -- 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/531b3625.5060...@debian.org
Re: Bug#737580: marked as done (ufsutils-udeb: mkfs.ufs: DIOCGMEDIASIZE: Inappropriate ioctl for device)
Robert Millan (2014-03-08): > On 08/03/2014 13:21, Debian Bug Tracking System wrote: > > ufsutils (9.2-3.1) unstable; urgency=high > > . > >* Non-maintainer upload. > >* Steal the following patch from the 10 branch, fixing failures to run > > mkfs.ufs, notably from d-i (Closes: #737580): > > 05_wipe_otherfs.patch: Handle DIOCGMEDIASIZE failure gracefully. > >* Fix FTBFS due to missing by adding a libutil-freebsd-dev > > build-dep (Closes: #741088). > > Thank you. I assume your plan is to include ufsutils 9.2 in jessie > alpha 1? In that case I would postpone upload of 10.0, which I planned > to do tomorrow. Yep, that's the plan. Need to figure out what to do with the apt-cdrom bug (maybe just propose a revert for now); linux is now building fine so should be a candidate for migration to testing. All in all, it shouldn't take too long to get debian-installer uploaded; thanks for your patience. Mraw, KiBi. signature.asc Description: Digital signature
Bug#724931: Please include the patch in git
Hi,
On 08.03.2014 02:13, Cyril Brulebois wrote:
Given the apt-cdrom regression we're hitting (#740673), I don't feel
like shipping this amount of additional modifications in jessie alpha 1
images; on the other hand, not uploading what's in apt-setup's master
currently would mean not using updated l10n material, which isn't too
nice. I'm tempted to branch "iso-loopback" from current master, so that
it's easily found afterwards, and to revert the ISO loopback bits for
now.
I generally agree that it would be good to have an alpha 1 installer to
use for testing regressions of this patch, but on the other hand using
loopmount to install Debian *works*.
So you might want to reconsider applying this patch now, as it seems to
be currently the only way to install Debian jessie directly. ;)
Yesterday I made a new installation using the patched:
Debian GNU/Linux testing "Jessie" - Official Snapshot amd64 CD Binary-1
20140203-06:21
I'm only half-joking, it really works, otherwise I would have reported a
bug.
I fixed a few things in my previous patch (see attachments):
* Fix typo in finish-install.d/10apt-cdrom-setup: cdrom/$j -> cdrom$j
* Always test for other CDs, except if it is a netinst CD.
Otherwise one can't use CD-2 together with
debian-testing-amd64-kde-CD-1.iso of type full_cd/single. (Maybe I
didn't get how this is supposed to work?)
* Mount further ISOs if at least four parts (seperated by -) of the
name are the same. Example:
a) debian-testing-amd64-CD-1.iso
b) debian-testing-amd64-kde-CD-1.iso
c) debian-testing-amd64-CD-2.iso
d) debian-testing-amd64-CD-2-local-changes.iso
e) debian-testing-i386-CD-2.iso
a) and b) would load c) or d), but not e).
* Fix crash, if the filesystem is not know (e.g. unpartitioned).
Pease add the attached patches on top of current git, even if you don't
want to apply the patch now and instead move it to another branch.
Best regards,
Andreas
diff -ruN apt-setup.orig/finish-install.d/10apt-cdrom-setup apt-setup/finish-install.d/10apt-cdrom-setup
--- apt-setup.orig/finish-install.d/10apt-cdrom-setup 2014-02-13 12:42:00.738178000 +0100
+++ apt-setup/finish-install.d/10apt-cdrom-setup 2014-02-13 15:49:18.868155368 +0100
@@ -10,10 +10,10 @@
if [ "$loopdev" ]; then
# Remove additional CD-Set mount points
j=1
- while [ -d /target/media/cdrom/$j ]; do
- logger -t finish-install "unmount /target/media/cdrom/$j"
- umount /target/media/cdrom/$j 2>/dev/null || true
- rmdir /target/media/cdrom/$j
+ while [ -d /target/media/cdrom$j ]; do
+ logger -t finish-install "unmount /target/media/cdrom$j"
+ umount /target/media/cdrom$j 2>/dev/null || true
+ rmdir /target/media/cdrom$j
j=$(($j + 1))
done
diff -ruN apt-setup.orig/generators/41cdset apt-setup/generators/41cdset
--- apt-setup.orig/generators/41cdset 2014-02-13 12:42:00.738178000 +0100
+++ apt-setup/generators/41cdset 2014-02-13 15:28:30.555167746 +0100
@@ -8,6 +8,20 @@
logger -t apt-setup "$@"
}
+split_string() {
+ # Save the old internal field separator.
+ OIFS=$IFS
+ # Change the internal field separator.
+ IFS=$2
+ arr=$1
+ # Convert the separator to newline.
+ for x in $arr; do
+ echo "$x"
+ done
+ # Restore the old internal field separator.
+ IFS=$OIFS
+}
+
# This code is copied from chroot-setup.sh, and is needed until after a d-i
# release whose initrds contain a sufficiently new version of di-utils.
if ! type chroot_cleanup_localmounts >/dev/null 2>&1; then
@@ -46,7 +60,7 @@
# bluray CDs have cd_type 'bluray'
cd_type=$(cat /cdrom/.disk/cd_type)
log "The disk type is: $cd_type"
-if [ "$cd_type" != full_cd ] && [ "$cd_type" != dvd ]; then
+if [ "$cd_type" == "not_complete" ]; then
exit 0
fi
@@ -123,23 +137,32 @@
if [ $run_count -eq 0 ]; then
log "Trying to find usable ISOs in the folder, where the boot ISO is..."
loopdir=$(db_getval cdrom-detect/cdrom_device)
- ISOname=$(basename $loopdir)
- loopdir=$(dirname $loopdir)
- if [ "$cd_type" = "dvd" ]; then
-# DVD
-ISOstart=${ISOname%DVD-*}
-ISOs=$(ls ${loopdir}/ | grep ${ISOstart}DVD-[^1].*[.]iso$)
- elif [ "$cd_type" = "blueray" ]; then
-# BD
-ISOstart=${ISOname%BD-*}
-ISOs=$(ls ${loopdir}/ | grep ${ISOstart}BD-[^1].*[.]iso$)
- else
-# probably CD
-ISOstart=${ISOname%CD-*}
-ISOs=$(ls ${loopdir}/ | grep ${ISOstart}CD-[^1].*[.]iso$)
- fi
- for iso in $ISOs; do
-max_run=$(($max_run + 1))
+ ISOname=${loopdir##*/}
+ loopdir=${loopdir%/*}
+
+ ISOarray=$(split_string "$ISOname" "-")
+ allISOs=$(ls ${loopdir}/ | grep .iso)
+ ISO=""
+ for iso in $allISOs; do
+arr=$(split_string "$iso" "-")
+count=0
+# Count common specifiers.
+for elem in $arr; do
+ if [ "$elem" == "1.iso" ]; then
+ # Only look for supplementary ISOs, not ISOs like '*-CD-1.iso'.
+ count=-1
+ break
+ fi
+ for orig_elem in $ISOarray; do
+ if [ "$elem" == "$orig_elem" ]; then
+ count=$(($count + 1))
+ fi
+ don
Bug#724931: Please include the patch in git
Andreas Cadhalpun (2014-03-08): > I generally agree that it would be good to have an alpha 1 installer > to use for testing regressions of this patch, but on the other hand > using loopmount to install Debian *works*. Sorry, but until it's been pushed to the masses, I can't blindly trust that. Many moving parts already, not going to add a critical one when we already have a (known) regression in apt-setup/apt-cdrom. Especially not a few days before a release. Mraw, KiBi. signature.asc Description: Digital signature
Bug#724931: Please include the patch in git
Hi, On 08.03.2014 19:04, Cyril Brulebois wrote: Andreas Cadhalpun (2014-03-08): I generally agree that it would be good to have an alpha 1 installer to use for testing regressions of this patch, but on the other hand using loopmount to install Debian *works*. Sorry, but until it's been pushed to the masses, I can't blindly trust that. Many moving parts already, not going to add a critical one when we already have a (known) regression in apt-setup/apt-cdrom. Especially not a few days before a release. I didn't really suggest applying the patch without further testing from someone other than me. I just wanted to express my amazement that loopmount works, while the usual way doesn't. I looked more closely and found that commenting out the following in 40cdrom fixes the problem: # Allow apt-cdrom to manage mounting/unmounting CDs in /target if [ "$cd_mountable" ]; then rm -f $ROOT/etc/apt/apt.conf.d/00NoMountCDROM $logoutput umount /target/media/cdrom* || true $logoutput umount /cdrom || true fi At least I managed to install Debian jessie in a Virtual Machine. So if there are no compelling reasons to have this (Note: I don't know, what this is supposed to do.), I would suggest removing this as a fix for Bug #740673. Best regards, Andreas -- 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/531b721e.3080...@googlemail.com
Bug#724931: Please include the patch in git
Andreas Cadhalpun (2014-03-08): > I looked more closely and found that commenting out the following in > 40cdrom fixes the problem: > # Allow apt-cdrom to manage mounting/unmounting CDs in /target > if [ "$cd_mountable" ]; then > rm -f $ROOT/etc/apt/apt.conf.d/00NoMountCDROM > > $logoutput umount /target/media/cdrom* || true > $logoutput umount /cdrom || true > fi > > At least I managed to install Debian jessie in a Virtual Machine. > So if there are no compelling reasons to have this (Note: I don't > know, what this is supposed to do.), I would suggest removing this > as a fix for Bug #740673. Err, no. We had something that worked well enough for a while, it broke due to a change in apt-cdrom, which was confirmed to be unintentional. So let's fix that for now, and *maybe* rethink stuff after that. I'm not goint to drop random lines, especially not based on “I don't know what this is supposed to do”… Mraw, KiBi. signature.asc Description: Digital signature
Bug#740410: installation-reports: Hang at "CD check" stage
Hi, in the meantime, I've used the Crunchbang CD install, based on Wheezy, and then I have updated to testing. My Debian testing runs smoothly again . 2014-03-08 1:51 GMT+01:00 Cyril Brulebois : > Control: block -1 by 740673 > > Cyril Brulebois (2014-03-04): > > I think you're hitting a known bug, I'd suggest using a wheezy > > installer for the time being, until an alpha image is released > > for jessie. > > So that's another bug, but it's confirmed as a known one; and > my suggestion (wait for alpha) stands for the time being. ;-) > > Mraw, > KiBi. >
Bug#741137: installation-reports
Package: installation-reports Boot method: Image version: http://cdimage.debian.org/debian-cd/7.4.0/amd64/iso-cd/debian-7.4.0-amd64-netinst.iso Date: 20140308 Machine: <6 year old workstation> Processor: amd64 - 4 processors Memory: 8GB Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/md0 ext4 33478296 5437524 26317080 18% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs826228 896825332 1% /run tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 2046460 148 2046312 1% /run/shm /dev/md2 ext4 1153351556 448741152 646016868 41% /home /dev/md3 ext4 288534864 8207136 265664304 3% /var none tmpfs 4 0 4 0% /sys/fs/cgroup Output of lspci -knn : 00:00.0 RAM memory [0500]: NVIDIA Corporation MCP55 Memory Controller [10de:0369] (rev a2) Subsystem: NVIDIA Corporation Device [10de:cb84] 00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP55 LPC Bridge [10de:0364] (rev a3) Subsystem: NVIDIA Corporation Device [10de:cb84] 00:01.1 SMBus [0c05]: NVIDIA Corporation MCP55 SMBus [10de:0368] (rev a3) Subsystem: NVIDIA Corporation Device [10de:cb84] Kernel driver in use: nForce2_smbus 00:02.0 USB controller [0c03]: NVIDIA Corporation MCP55 USB Controller [10de:036c] (rev a1) Subsystem: NVIDIA Corporation Device [10de:cb84] Kernel driver in use: ohci-pci 00:02.1 USB controller [0c03]: NVIDIA Corporation MCP55 USB Controller [10de:036d] (rev a2) Subsystem: NVIDIA Corporation Device [10de:cb84] Kernel driver in use: ehci-pci 00:04.0 IDE interface [0101]: NVIDIA Corporation MCP55 IDE [10de:036e] (rev a1) Subsystem: NVIDIA Corporation Device [10de:cb84] Kernel driver in use: pata_amd 00:05.0 IDE interface [0101]: NVIDIA Corporation MCP55 SATA Controller [10de:037f] (rev a3) Subsystem: NVIDIA Corporation Device [10de:cb84] Kernel driver in use: sata_nv 00:05.1 IDE interface [0101]: NVIDIA Corporation MCP55 SATA Controller [10de:037f] (rev a3) Subsystem: NVIDIA Corporation Device [10de:cb84] Kernel driver in use: sata_nv 00:05.2 IDE interface [0101]: NVIDIA Corporation MCP55 SATA Controller [10de:037f] (rev a3) Subsystem: NVIDIA Corporation Device [10de:cb84] Kernel driver in use: sata_nv 00:06.0 PCI bridge [0604]: NVIDIA Corporation MCP55 PCI bridge [10de:0370] (rev a2) 00:06.1 Audio device [0403]: NVIDIA Corporation MCP55 High Definition Audio [10de:0371] (rev a2) Subsystem: Tyan Computer Device [10f1:2925] Kernel driver in use: snd_hda_intel 00:08.0 Bridge [0680]: NVIDIA Corporation MCP55 Ethernet [10de:0373] (rev a3) Subsystem: NVIDIA Corporation Device [10de:cb84] Kernel driver in use: forcedeth 00:09.0 Bridge [0680]: NVIDIA Corporation MCP55 Ethernet [10de:0373] (rev a3) Subsystem: NVIDIA Corporation Device [10de:cb84] Kernel driver in use: forcedeth 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP55 PCI Express bridge [10de:0376] (rev a3) Kernel driver in use: pcieport 00:0b.0 PCI bridge [0604]: NVIDIA Corporation MCP55 PCI Express bridge [10de:0374] (rev a3) Kernel driver in use: pcieport 00:0c.0 PCI bridge [0604]: NVIDIA Corporation MCP55 PCI Express bridge [10de:0374] (rev a3) Kernel driver in use: pcieport 00:0d.0 PCI bridge [0604]: NVIDIA Corporation MCP55 PCI Express bridge [10de:0378] (rev a3) Kernel driver in use: pcieport 00:0e.0 PCI bridge [0604]: NVIDIA Corporation MCP55 PCI Express bridge [10de:0375] (rev a3) Kernel driver in use: pcieport 00:0f.0 PCI bridge [0604]: NVIDIA Corporation MCP55 PCI Express bridge [10de:0377] (rev a3) Kernel driver in use: pcieport 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] Kernel driver in use: amd64_edac 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] Kernel driver in use: k8temp 00:19.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:19.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:19.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] Kernel driver in use: amd64_edac 00:19.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] Kernel
Bug#730414: installation-reports: no network after installation
Package: installation-reports Followup-For: Bug #730414 -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash I think I had the same problem. It was a reserved IP address at the router. I have a LAN and use my computer for all apt-cache and other things, so I had reserved an IP address in my router. Did a fresh install of 7.4.0 and upon reboot I had no network except IPV6. After turning off reserved IP and reinstalling, everything worked fine. -- 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/20140309002358.16261.89952.reportbug@MIKES.MIKEAIR
Bug#740073: You can continue OR install it the other way.
Here's a workaround that works: The installation process can be continued just by killing the apt-cdrom process (Alt-F2, Enter, ps, find out the PID, kill the process). And for those crying that 'YOU CAN'T INSTALL JESSIE! THERE IS NO WAY..!' No matter how loud you are, you just are not right. For your urgent needs (all needs before jessie releases) just install wheezy and update it afterwards. -- 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/531bef4c.7080...@unboiled.info
