Bug#690210: debootstrap: please add support for debian-ports
Package: debootstrap
Version: 1.0.42
Severity: wishlist
Tags: patch
Dear Maintainer,
I wonder if we could have debootstrap support the repository
ftp.debian-ports.org.
Please find the script attached as an illustration of the requested
features, in the form of a script
/usr/share/debootstrap/scripts/debian-ports.
(A diff against the stock script for unstable is attached as
from_unstable_to_debian-ports.diff.gz)
ftp.debian-ports.org hosts unofficial architectures until they are
integrated in the main Debian archive (currently alpha, hppa, m68k,
powerpcspe, ppc64, sh4 and sparc64, and GNU/Hurd).
It requires specific workarounds in debootstrap since the needed
packages are sometimes not in the "unstable" suite of the repository.
Thanks in advance !
J-H Chatenet
-- System Information:
Debian Release: wheezy/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: alpha
Kernel: Linux 3.2.0-4-alpha-generic
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages debootstrap depends on:
ii wget 1.14-1
Versions of packages debootstrap recommends:
ii debian-archive-keyring 2012.4
ii gnupg 1.4.12-4
debootstrap suggests no packages.
-- debconf-show failed
# /usr/share/debootstrap/scripts/debian-ports
SUITE="unstable"
DEF_MIRROR="http://ftp.debian-ports.org/debian";
mirror_style release
download_style apt
finddebs_style from-indices
variants - buildd fakechroot minbase scratchbox
# use the debian-ports keyring if debian-ports-archive-keyring is installed
#keyring /usr/share/keyrings/debian-archive-keyring.gpg
keyring /usr/share/keyrings/debian-ports-archive-keyring.gpg
# or the one installed
keyring /etc/apt/trusted.gpg
# Install debian-ports-archive-keyring (priority: extra) along with the
important packages on the target
if [ -z "$ADDITIONAL" ]; then
ADDITIONAL="debian-ports-archive-keyring"
elif $(echo "$ADDITIONAL" | fgrep -qv 'debian-ports-archive-keyring'); then
ADDITIONAL="${ADDITIONAL} debian-ports-archive-keyring"
fi
if doing_variant fakechroot; then
test "$FAKECHROOT" = "true" || error 1 FAKECHROOTREQ "This variant
requires fakechroot environment to be started"
fi
case $ARCH in
alpha|ia64) LIBC="libc6.1" ;;
kfreebsd-*) LIBC="libc0.1" ;;
hurd-*) LIBC="libc0.3" ;;
*) LIBC="libc6" ;;
esac
# overload download_indices from /usr/share/debootstrap/functions
download_indices () {
local mem_suite
mk_download_dirs
"$DOWNLOAD_INDICES" $(echo "$@" | tr ' ' '\n' | sort)
mem_suite=$SUITE
SUITE="unreleased" "$DOWNLOAD_INDICES" $(echo "$@" | tr ' ' '\n' | sort)
SUITE=$mem_suite
}
# add unreleased
add_fake_component () {
local TEMP_COMPONENTS
local m2 c c1 path1 pkgdest1 path2 pkgdest2
components_wo_unreleased=$(echo $COMPONENTS|tr ' ' '\n'|\
sort|uniq|tr '\n' ' ')
TEMP_COMPONENTS="$components_wo_unreleased"
for m2 in $MIRRORS; do
for c in $components_wo_unreleased; do
path1="dists/unreleased/$c/binary-$ARCH/Packages"
pkgdest1="$TARGET/$($DLDEST pkg "unreleased" "$c"
"$ARCH" "$m2" "$path1")"
# Fake component unreleased
c1="${c}unreleased"
path2="dists/$SUITE/$c1/binary-$ARCH/Packages"
pkgdest2="$TARGET/$($DLDEST pkg "$SUITE" "$c1" "$ARCH"
"$m2" "$path2")"
ln -sf $(basename $pkgdest1) $pkgdest2
TEMP_COMPONENTS="${TEMP_COMPONENTS} ${c1}"
done
done
TEMP_COMPONENTS="$(echo $TEMP_COMPONENTS|tr ' ' '\n'|sort|uniq|tr '\n'
' ')"
if [ "$TEMP_COMPONENTS" != "$components_wo_unreleased" ] ; then
COMPONENTS="$TEMP_COMPONENTS"
fi
}
work_out_debs () {
# add a symlink for unreleased
add_fake_component
required="$(get_debs Priority: required)"
if doing_variant - || doing_variant fakechroot; then
#required="$required $(get_debs Priority: important)"
# ^^ should be getting debconf here somehow maybe
base="$(get_debs Priority: important)"
elif doing_variant buildd || doing_variant scratchbox; then
base="apt build-essential"
elif doing_variant minbase; then
base="apt"
fi
if doing_variant fakechroot; then
# ldd.fake needs binutils
required="$required binutils"
fi
}
# from /usr/share/debootstrap/scripts/sid unmodified
first_stage_install () {
extract $required
mkdir -p "$TARGET/var/lib/dpkg"
: >"$TARGET/var/lib/dpkg/status"
: >"$TARGET/var/lib/dpkg/available"
setup_etc
if [ ! -e "$TARGET/etc/fstab" ]; then
echo '# UNCONFIGURED FS
Bug#690238: Installing DI beta2 on DELL PowerEdge T620 with RAID controller H710 and an LTO3 connected to a SAS controller
Package: installation-reports Boot method: USB memory stick with ISO image embedded Image version: http://hammurabi.acc.umu.se/cdimage/wheezy_di_beta2/amd64/iso-cd/debian-wheezy-DI-b2-amd64-netinst.iso Date: 2012-10-11 Machine: DELL PowerEdge T620 Processor: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz Memory: 32GB Partitions: Disk /dev/sda: 599.6 GB, 599550590976 bytes 255 heads, 63 sectors/track, 72891 cylinders, total 1170997248 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000177d3 Device Boot Start End Blocks Id System /dev/sda1 *2048 487423 242688 83 Linux /dev/sda2 487424 1170995199 585253888 8e Linux LVM File systemTipo 1K-blocchi Usati Disponib. Uso% Montato su rootfs rootfs 4866816 698424 3924272 16% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 3297080288 3296792 1% /run /dev/mapper/agenzia--f27-root ext44866816 698424 3924272 16% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 6594140 0 6594140 0% /run/shm /dev/sda1 ext2 227431 17606197691 9% /boot /dev/mapper/agenzia--f27-home ext4 27266916 532036 25367840 3% /home /dev/mapper/agenzia--f27-samba ext4 44826400 791072 41789288 2% /srv/samba /dev/mapper/agenzia--f27-tmp ext32882592 69900 2666260 3% /tmp /dev/mapper/agenzia--f27-var ext4 38971192 929624 36088596 3% /var Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation Sandy Bridge DMI2 [8086:3c00] (rev 07) Subsystem: Dell Device [1028:04cf] 00:01.0 PCI bridge [0604]: Intel Corporation Sandy Bridge IIO PCI Express Root Port 1a [8086:3c02] (rev 07) Kernel driver in use: pcieport 00:02.0 PCI bridge [0604]: Intel Corporation Sandy Bridge IIO PCI Express Root Port 2a [8086:3c04] (rev 07) Kernel driver in use: pcieport 00:03.0 PCI bridge [0604]: Intel Corporation Sandy Bridge IIO PCI Express Root Port 3a in PCI Express Mode [8086:3c08] (rev 07) Kernel driver in use: pcieport 00:05.0 System peripheral [0880]: Intel Corporation Sandy Bridge Address Map, VTd_Misc, System Management [8086:3c28] (rev 07) Subsystem: Dell Device [1028:04cf] 00:05.2 System peripheral [0880]: Intel Corporation Sandy Bridge Control Status and Global Errors [8086:3c2a] (rev 07) Subsystem: Dell Device [1028:04cf] 00:11.0 PCI bridge [0604]: Intel Corporation Patsburg PCI Express Virtual Root Port [8086:1d3e] (rev 05) Kernel driver in use: pcieport 00:16.0 Communication controller [0780]: Intel Corporation Patsburg HECI Controller #1 [8086:1d3a] (rev 05) Subsystem: Dell Device [1028:04cf] 00:16.1 Communication controller [0780]: Intel Corporation Patsburg HECI Controller #2 [8086:1d3b] (rev 05) Subsystem: Dell Device [1028:04cf] 00:1a.0 USB Controller [0c03]: Intel Corporation Patsburg USB2 Enhanced Host Controller #2 [8086:1d2d] (rev 05) Subsystem: Dell Device [1028:04cf] Kernel driver in use: ehci_hcd 00:1c.0 PCI bridge [0604]: Intel Corporation Patsburg PCI Express Root Port 1 [8086:1d10] (rev b5) Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation Patsburg PCI Express Root Port 5 [8086:1d18] (rev b5) Kernel driver in use: pcieport 00:1c.7 PCI bridge [0604]: Intel Corporation Patsburg PCI Express Root Port 8 [8086:1d1e] (rev b5) Kernel driver in use: pcieport 00:1d.0 USB Controller [0c03]: Intel Corporation Patsburg USB2 Enhanced Host Controller #1 [8086:1d26] (rev 05) Subsystem: Dell Device [1028:04cf] Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5) 00:1f.0 ISA bridge [0601]: Intel Corporation Patsburg LPC Controller [8086:1d41] (rev 05) Subsystem: Dell Device [1028:04cf] 00:1f.2 SATA controller [0106]: Intel Corporation Patsburg 6-Port SATA AHCI Controller [8086:1d02] (rev 05) Subsystem: Dell Device [1028:04cf] Kernel driver in use: ahci 01:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) Subsystem: Dell Device [1028:1f1c] Kernel driver in use: mpt2sas 02:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS TB [1000:005b] (rev 01) Subsystem: Dell Device [1028:1f35] 06:00.0 Ethernet controller [0200]: Intel Corporation Device [8086:1521] (rev 01) Subsystem: Dell Device [1028:04cf] Kernel driver in use: igb 06:00.1 Ethernet controller [0200]: Intel Corporation Device [8086:1521] (rev
Bug#690246: debian-installer: initial install reboot failure to find lvm devices when hostname has a - in it
Package: debian-installer Version: 6.0.1a Severity: important Tags: d-i Standard debian 6 install, hostname has a dash in it, ie this-name. The lvm volume group then uses this-name for the volume group name. Install goes fine, but on reboot it dumps into initram shell saying it can't find root /dev/mapper/this-name-root. Not sure where the 2nd dash came from. lvm lvscan shows the volumes as inactive. lvchange -a y this-name/root activates the volume and creates /dev/mapper/this--name-root. System still won't boot 'cause it's confused about the mapper device name. -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (800, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain GeneDx proprietary information, which is privileged, confidential, or subject to copyright belonging to GeneDx. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121011143940.4751.49325.report...@gdx-commvault.bioreference-laboratories.com
Bug#690246: debian-installer: initial install reboot failure to find lvm devices when hostname has a - in it
On Thu, Oct 11, 2012 at 10:39:40AM -0400, Eli wrote: > Package: debian-installer > Version: 6.0.1a > Severity: important > Tags: d-i > > Standard debian 6 install, hostname has a dash in it, ie this-name. The lvm > volume group then uses this-name > for the volume group name. Install goes fine, but on reboot it dumps into > initram shell saying it can't > find root /dev/mapper/this-name-root. Not sure where the 2nd dash came from. > lvm lvscan shows the volumes > as inactive. lvchange -a y this-name/root activates the volume and creates > /dev/mapper/this--name-root. > System still won't boot 'cause it's confused about the mapper device name. > > -- System Information: > Debian Release: 6.0.6 > APT prefers stable > APT policy: (800, 'stable'), (500, 'stable-updates') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/16 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > The information transmitted in this email and any of its attachments is > intended only for the person or entity to which it is addressed and may > contain GeneDx proprietary information, which is privileged, confidential, or > subject to copyright belonging to GeneDx. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, this > information by persons or entities other than the intended recipient is > prohibited and may be unlawful. If you received this in error, please contact > the sender immediately and delete and destroy the communication and all of > the attachments you have received and all copies thereof. The method lvm uses for naming is: Use volumegroupname-volumename if the names have dashes in them, double up the dashes so that the only place with a single dash is the one seperating the volumegroupname from the volumename. I think they do this to make sure hey stay unique. After all if you had a volume group named 'a-b' with a volume named 'c' and a nother volume group named 'a' with a volume named 'b-c' you would end up with: a-b-c for both of them if you didn't do the doubling thing. Instead you get get: a--b-c (VG a-b with LV c) a-b--c (VG A with LV b-c) So the installer must double the dash in any volumegroup name or volumename when generating the name in /dev/mapper to expect. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121011152905.gb18...@csclub.uwaterloo.ca
Bug#396023: Allow encrypted partitions to be removed
The issues about re-installing with partman-auto-lvm on top of stale lvm metadata on disk is solved with a patch in [1] My take on solving "Should allow de-allocation of encrypted volumes" bug 381892 is actually resolving the TODO item in partman-crypto: "Understand and add undo.d scripts if required" My understanding is that all cryptsetup dm-devices should be closed. That implies deactivating any dm volumes that sit on top of cryptsetup device (e.g. lvm) as well as unlocking the underlying physical volume(s). I am not sure if this should be done before or after 30partman - i.e. parted UNDO command. Naturally this will also imply that patch from bug 451535 [2] should be applied, which allows activating existing cryptsetup volumes. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687160#28 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451535#42 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANBHLUjCpt+7o23Pi=v7mopdgn6czysnm-pv-tj_mpcdfhg...@mail.gmail.com
