Re: wait for the boot device
also sprach Marco d'Itri [2009.07.19.2309 +0200]: > > Really? So is /usr/share/initramfs-tools/scripts/local-top/mdadm > > (from the mdadm package) wrong, or something else buggy or broken by > > design? I also experienced the need for udevsettle when booting from > > LVM over partitioned multipath devices. I thought it was the kpartx > > invocation which I had to wait for before the lvm2 script. I'd be > > grateful for some advice on how to handle such cases properly. > > In an event driven model everything should happen as a reaction to a > kevent, introducing a serialization point is just a workaround for a > broken design. > Other distributions (SuSE at least) mount file systems with udev RUN > rules as a side effect of the relevant device appearing. Yeah, that sounds great, and mdadm has recently grown the bits to support that (incremental assembly). However, that does not mean that it's ready for production use or that anyone has had the time to really make it happen in Debian. The Ubuntu patch is mostly useless for Debian as it's one big lump that touches other things and introduces dependencies, and Suse did some weird udev stuff the last time I checked. Then there is udev, which is so contrary to my understanding of how Unix works that it always takes me ages to get anything done with it. Plus, udev's deprecation period wasn't very clearly communicated either, and there are no usable docs that would make a migration easier. It would be good if you could help and provide something to work of. Basically it's just calling `mdadm --incremental` for all component devices. But then there are things to work out: 1. use --run to start arrays as soon as possible, or only start an array when it's completely assembled? 2. when can we assume that the arrays are ready to be started? 3. how does the rest of the operating system find out when /dev/md0 is ready to be used? 4. How do we properly deal with the device node change? What previously was /dev/md2 with normal assembly is now /dev/md_d2? It's not quite as easy as just deprecating udevsettle on a distro scale. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "the truth is rarely pure and never simple. modern life would be very tedious if it were either, and modern literature a complete impossibility!" -- oscar wilde digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: please let dhcp3 into testing
Quoting Luk Claes (l...@debian.org): > >That seems feasible and sustainable, isn't it? > > There is a webpage [1] tracking it, maybe it should just be used more? That's pulled information (one has to think about visiting the page, etc.). I happen to think that pushed information could be more efficient. Maybe someone could hack the script that generates this page to optionnally mail its content...or changes, condensed, to a configurable mail address? signature.asc Description: Digital signature
Re: kFreeBSD progress report week 8
Hello Luca, On Sun, Jul 19, 2009 at 9:03 PM, Luca Favatella wrote: > In the past two weeks I focused on getting network configuration > working in debian-installer (d-i), without success. > I skipped the keyboard layout selection, because not a top priority, > and I didn't reach udeb download (and installation). First I'd like to thank you for all your work and offer help to merge ready things in trunk during those days. I'm at Debcamp and have time to work on that with you on that. Another thing I'd like to inform you is that netcfg has now support for udhcpc. You need to use the script I've commited in Bastian's branch of busybox and remove few files to udhcpc to be choosen (look at mailing list how to test it) but it ought to make your testing easier. Cheers, -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#536820: please add scratchbox2 variant
Hello Riku, On Sun, Jul 19, 2009 at 5:00 PM, Riku Voipio wrote: > Manpage updated. I didn't touch the whitespace issues because I already > try match what is in the files it patch - tabs for debootstrap and functions, > mixed for scripts/sid. [...] Is, it doesn't mean we ought to not avoid addming more mess on that ;-) > Also, I think for low-volume projects such as debootstrap, it is faster to > just fix up the whitespaces while commiting and tell the contributor > to take a close look at whitespace issues before sending the next patch. Well I somewhat agree with that. I've reported it to you so you could look at it and fix it but in case you did not found the time for that I'd do that. BTW the thing I had noticed you got fixed. @@ -52,6 +52,8 @@ if doing_variant fakechroot; then setup_devices_fakechroot +elif doing_variant schratchbox; then +true Typo? :-) I'll wait few days for comments from others before commit it. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
kFreeBSD progress report week 8
In the past two weeks I focused on getting network configuration working in debian-installer (d-i), without success. I skipped the keyboard layout selection, because not a top priority, and I didn't reach udeb download (and installation). I focused on network configuration in d-i, mostly done by netcfg [din0]. I disabled unuseful udebs, to semplify debugging; in particular, I disabled the ethdetect one [din1], concentrating on those cards whose driver is automatically detected and loaded by the kernel (e.g. NE2000, as QEMU's one). I made a little portability fix in netcfg [din2] about a Linux specific PCMCIA file. While debugging netcfg, I discovered that "/var/log/syslog" is not created, even manually executing syslogd. Currently, in d-i, BusyBox syslogd is used. Even without syslogd working, I managed to go forward in netcfg debug manually running "dhclient ed0" [din3] (thanks to Julián Moreno Patiño): the "ip" command is not found, because the dhclient-script used in the dhcp3-client udeb is Linux specific; on the deb package, there is a different script for GNU/kFreeBSD and GNU/Linux, but the GNU/kFreeBSD version needs "ifconfig" and "route". I considered porting and switching to BusyBox udhcpc. I also worked on * BusyBox + realizing there is a FreeBSD port [bb0] + asking upstream [bb1] for partially reverting a commit, proposing a patch rejected [bb2] because - breaking GNU/Linux build - against BusyBox policy about "#define"s, as I discovered later [bb3] + moving to [bb4] some patches: - those from the previous efforts on version 1.01 [bb6], merging them in [bb5] - those from FreeBSD [bb0], against version 1.13, almost useless; in particular @ init is disabled @ syslogd is enabled but not patched (so not working, I think) - those I wrote in previous weeks [bb7] (against version 1.13), reviewing and cleaning most of them; these [bb5] are the recommended patches to use + looking for Linux-specific code in syslogd (and logger), without success * enabling auxiliary consoles (alt-fX) in d-i [dic0] (read the commit log) * merging some patches to d-i trunk + committing already proposed patches - add cons25 terminfo file [dip0] - more fine-grained wireless building and linking in netcfg [dip1] + proposing and committing new patches - substitute Linux-specific code in get_all_ifs() using getifaddrs() [dip2] - poll() portability issue [dip3] - add ufs2 initrd support [dip4]; mkfs.ufs2 needs root rights, perhaps NetBSD makefs (or its FreeBSD [dip4_0] or MirBSD version) could be useful to run it as a normal user - fix in the kfreebsd-i386 kernel udeb ABI and a dependency version [dip5] - add kfreebsd-i386 monolithic config files [dip6] + proposing new patches (without committing them yet) - generalize rootskel splitting Linux specific stuff [dip7] (unblocked by [dip7_0]) To quickly test all this * download the mini.iso cd at [test0], built from current d-i kfreebsd branch [test1] * boot it in your favourite virtual machine + if it is qemu, "qemu -boot d -cdrom mini.iso" will suffice In the next two weeks I should (still) * get network configuration working * get udeb download and installation working For that I should work on * BusyBox + udhcpc + syslogd + understanding if [todo0] fixes some known problems or is unuseful * netcfg + network interface detected twice + filtering lo0 * rootskel + clean [dic0] for merging to d-i trunk Luca Favatella [din0] http://packages.debian.org/sid/netcfg [din1] http://packages.debian.org/sid/ethdetect [din2] http://svn.debian.org/viewsvn/d-i?view=rev&revision=59287 [din3] http://svn.debian.org/viewsvn/d-i/trunk/packages/netcfg/dhcp.c?revision=58009&view=markup [bb0] http://www.freebsd.org/cgi/ports.cgi?query=busybox&stype=all [bb1] http://lists.busybox.net/pipermail/busybox/2009-July/069902.html [bb2] http://lists.busybox.net/pipermail/busybox/2009-July/069914.html [bb3] http://lists.busybox.net/pipermail/busybox/2009-July/069938.html [bb4] http://svn.debian.org/viewsvn/d-i/people/slackydeb/kfreebsd/busybox/ [bb5] http://svn.debian.org/viewsvn/d-i/people/slackydeb/kfreebsd/busybox/1.13/debian/ [bb6] http://glibc-bsd.alioth.debian.org/patches/ [bb7] http://slackydeb.blogspot.com/2009/05/busybox-status-on-gnukfreebsd.html [dic0] http://svn.debian.org/viewsvn/d-i/branches/d-i/kfreebsd/packages/rootskel/src/etc/inittab?revision=59364&view=markup [dip0] http://lists.debian.org/debian-boot/2009/07/msg00051.html [dip1] http://lists.debian.org/debian-boot/2009/07/msg00052.html [dip2] http://lists.debian.org/debian-boot/2009/07/msg00142.html [dip3] http://lists.debian.org/debian-boot/2009/07/msg00149.html [dip4] http://lists.debian.org/debian-boot/2009/07/msg00150.html [dip4_0] http://svn.freebsd.org/viewvc/base/head/usr.sbin/makefs/ [dip5] http://lists.debian.org/debian-boot/2009/07/msg00365.html [dip6] http://lists.debian.org/debian-boot/2009/07/msg00345.html [dip7] http://lists.debian.org/debian-boot/2009/07/msg003
Bug#387696: marked as done (mdcfg: MD stands for "multiple device", not "multidisk")
Your message dated Sun, 19 Jul 2009 21:34:40 + with message-id and subject line Bug#387696: fixed in partman-md 46 has caused the Debian Bug report #387696, regarding mdcfg: MD stands for "multiple device", not "multidisk" 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.) -- 387696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mdcfg Severity: minor In the templates file for mdcfg, the acronym MD has been consistently translated with "multidisk". However, it really is short for "multiple devices". As a rough synonym "software RAID" is often used. "Multiple device" is also prefered by the Debian maintainer of mdadm. In the mdadm documentation and messages the term "MD array" is now used frequently. In Google "md multiple device" gives twice as many hits as "md multiple disk". See for example: - http://www.die.net/doc/linux/man/man4/md.4.html Although wikipedia also seems to have it wrong: - http://en.wikipedia.org/wiki/Redundant_array_of_independent_disks There are also a two strings in partman that contain multidisk: ./partman/partman-auto-raid/debian/partman-auto-raid.templates:39:_Description: Multidisk (MD) not available ./partman/partman-auto-raid/debian/partman-auto-raid.templates:40: The current kernel doesn't seem to support multidisk devices. This should be pgpbeYTDeQbr5.pgp Description: PGP signature --- End Message --- --- Begin Message --- Source: partman-md Source-Version: 46 We believe that the bug you reported is fixed in the latest version of partman-md, which is due to be installed in the Debian FTP archive: partman-md_46.dsc to pool/main/p/partman-md/partman-md_46.dsc partman-md_46.tar.gz to pool/main/p/partman-md/partman-md_46.tar.gz partman-md_46_all.udeb to pool/main/p/partman-md/partman-md_46_all.udeb 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 387...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated partman-md 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 19 Jul 2009 20:59:36 +0100 Source: partman-md Binary: partman-md Architecture: source all Version: 46 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Colin Watson Description: partman-md - Add to partman support for MD (udeb) Closes: 387696 499285 Changes: partman-md (46) unstable; urgency=low . * Merge mdcfg, making partman-md stand-alone. (This work sponsored by Canonical Ltd.) * Bugs fixed along the way: - Talks about "software RAID" or "multiple device" rather than "multidisk" (closes: #387696). - Uses partman locking mechanism (closes: #499285). . [ Updated translations ] * Asturian (ast.po) by Marcos Alvarez Costales * Belarusian (be.po) by Pavel Piatruk * German (de.po) by Holger Wansing * Esperanto (eo.po) by Felipe Castro * Basque (eu.po) by Piarres Beobide * French (fr.po) by Christian Perrier * Hindi (hi.po) * Italian (it.po) by Milo Casagrande * Marathi (mr.po) by Sampada * Portuguese (pt.po) by Miguel Figueiredo * Russian (ru.po) by Yuri Kozlov * Slovak (sk.po) by Ivan Masár * Turkish (tr.po) by Mert Dirik * Wolof (wo.po) by Mouhamadou Mamoune Mbacke * Simplified Chinese (zh_CN.po) by Deng Xiyue Checksums-Sha1: 0f7ebf86f2f34af4c542b10d5ac2cff4a990536e 886 partman-md_46.dsc 090e130486cea02ed07782a53826489a46bf1a22 170329 partman-md_46.tar.gz dc9cc9967bc161a296b00d997b999629093795ca 59004 partman-md_46_all.udeb Checksums-Sha256: 50b45761def3a35b42a4b228b24fafa0bb0e6fe3d20eeed3495a75343ccc56a8 886 partman-md_46.dsc b817e59173d2fee9a1469804708df007690ec4d77811f274ccb2a8ab23041d4f 170329 partman-md_46.tar.gz 1eb23cbe96dd2be2926e1258b856b657617840c33ae0567658389b9f83f65392 59004 partman-md_46_all.udeb Files: 94538cb21244e1a772036ac1764594e6 886 debian-installer standard partman-md_46.dsc 292aa02085a4e1b2f008a0c058576f08 170329 debian-installer standard partman-md_46.tar.gz 80452f79f05028867c7ea3c447778ced 59004 debian-installer standard partman-md_46_all.udeb Package-Type: udeb -BEGIN PGP SIGNATURE-
Bug#499285: marked as done (partman-md: should use partman locking mechanism)
Your message dated Sun, 19 Jul 2009 21:34:40 + with message-id and subject line Bug#499285: fixed in partman-md 46 has caused the Debian Bug report #499285, regarding partman-md: should use partman locking mechanism 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.) -- 499285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Version: daily build 16th Sep Severity: normal I have a machine that had been used in a Linux Software RAID-1 configuration with LVM running on top of the RAID. The Debian Installer recognised the LVM devices which in most cases is a good thing. But having LVM enabled it was unable to cease all kernel access to the partitions for the purpose of getting the kernel to recognise the new partitions I created (I decided I wanted a slightly different RAID installation for the rebuild). So when it gave errors about being unable to get the kernel to recognise the devices I rebooted and then it recognised the devices and allowed me to create a new software RAID installation. --- End Message --- --- Begin Message --- Source: partman-md Source-Version: 46 We believe that the bug you reported is fixed in the latest version of partman-md, which is due to be installed in the Debian FTP archive: partman-md_46.dsc to pool/main/p/partman-md/partman-md_46.dsc partman-md_46.tar.gz to pool/main/p/partman-md/partman-md_46.tar.gz partman-md_46_all.udeb to pool/main/p/partman-md/partman-md_46_all.udeb 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 499...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated partman-md 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 19 Jul 2009 20:59:36 +0100 Source: partman-md Binary: partman-md Architecture: source all Version: 46 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Colin Watson Description: partman-md - Add to partman support for MD (udeb) Closes: 387696 499285 Changes: partman-md (46) unstable; urgency=low . * Merge mdcfg, making partman-md stand-alone. (This work sponsored by Canonical Ltd.) * Bugs fixed along the way: - Talks about "software RAID" or "multiple device" rather than "multidisk" (closes: #387696). - Uses partman locking mechanism (closes: #499285). . [ Updated translations ] * Asturian (ast.po) by Marcos Alvarez Costales * Belarusian (be.po) by Pavel Piatruk * German (de.po) by Holger Wansing * Esperanto (eo.po) by Felipe Castro * Basque (eu.po) by Piarres Beobide * French (fr.po) by Christian Perrier * Hindi (hi.po) * Italian (it.po) by Milo Casagrande * Marathi (mr.po) by Sampada * Portuguese (pt.po) by Miguel Figueiredo * Russian (ru.po) by Yuri Kozlov * Slovak (sk.po) by Ivan Masár * Turkish (tr.po) by Mert Dirik * Wolof (wo.po) by Mouhamadou Mamoune Mbacke * Simplified Chinese (zh_CN.po) by Deng Xiyue Checksums-Sha1: 0f7ebf86f2f34af4c542b10d5ac2cff4a990536e 886 partman-md_46.dsc 090e130486cea02ed07782a53826489a46bf1a22 170329 partman-md_46.tar.gz dc9cc9967bc161a296b00d997b999629093795ca 59004 partman-md_46_all.udeb Checksums-Sha256: 50b45761def3a35b42a4b228b24fafa0bb0e6fe3d20eeed3495a75343ccc56a8 886 partman-md_46.dsc b817e59173d2fee9a1469804708df007690ec4d77811f274ccb2a8ab23041d4f 170329 partman-md_46.tar.gz 1eb23cbe96dd2be2926e1258b856b657617840c33ae0567658389b9f83f65392 59004 partman-md_46_all.udeb Files: 94538cb21244e1a772036ac1764594e6 886 debian-installer standard partman-md_46.dsc 292aa02085a4e1b2f008a0c058576f08 170329 debian-installer standard partman-md_46.tar.gz 80452f79f05028867c7ea3c447778ced 59004 debian-installer standard partman-md_46_all.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Colin Watson -- Debian developer iD8DBQFKY3wL9t0zAhD6TNERAhFnAJ4s85NNY6FX7FBnlzNP5Cgf+IQ3mwCfQDag BQp/F/gQLhhl0lde/Saqhgk= =e5Se -END PGP SIGNATURE- --- End Message ---
partman-md_46_i386.changes ACCEPTED
Accepted: partman-md_46.dsc to pool/main/p/partman-md/partman-md_46.dsc partman-md_46.tar.gz to pool/main/p/partman-md/partman-md_46.tar.gz partman-md_46_all.udeb to pool/main/p/partman-md/partman-md_46_all.udeb Override entries for your package: partman-md_46.dsc - source debian-installer partman-md_46_all.udeb - standard debian-installer Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 387696 499285 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
Re: wait for the boot device
On Jul 19, Ferenc Wagner wrote: > > If you need udevsettle anywhere else than after running udevtrigger then > > something is either buggy or broken by design. > Really? So is /usr/share/initramfs-tools/scripts/local-top/mdadm > (from the mdadm package) wrong, or something else buggy or broken by > design? I also experienced the need for udevsettle when booting from > LVM over partitioned multipath devices. I thought it was the kpartx > invocation which I had to wait for before the lvm2 script. I'd be > grateful for some advice on how to handle such cases properly. In an event driven model everything should happen as a reaction to a kevent, introducing a serialization point is just a workaround for a broken design. Other distributions (SuSE at least) mount file systems with udev RUN rules as a side effect of the relevant device appearing. -- ciao, Marco signature.asc Description: Digital signature
Re: wait for the boot device
m...@linux.it (Marco d'Itri) writes: > On Jul 19, Ferenc Wagner wrote: > >> Now that a kernel (and initramfs-tools) maintainer gave the >> explanation you requested, how do you think we could proceed with >> this? > > As I explained, I will consider this after I will have finished the next > upload. Sorry, I must have missed that. Thanks! >> I'd like to add that udevsettle calls are also needed in other package >> scripts (LVM, multipath, etc.) and there's even a wait_for_udev >> canned > > If you need udevsettle anywhere else than after running udevtrigger then > something is either buggy or broken by design. Really? So is /usr/share/initramfs-tools/scripts/local-top/mdadm (from the mdadm package) wrong, or something else buggy or broken by design? I also experienced the need for udevsettle when booting from LVM over partitioned multipath devices. I thought it was the kpartx invocation which I had to wait for before the lvm2 script. I'd be grateful for some advice on how to handle such cases properly. -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#536820: please add scratchbox2 variant
On Sat, Jul 18, 2009 at 06:32:54PM -0300, Otavio Salvador wrote: > On Wed, Jul 15, 2009 at 5:54 PM, Riku Voipio wrote: > > Argh, please forget the previous patch. That one was certainly not the > > one I wanted to send. The patch attached to this mail has the advantage > > of actually working. > Previous comments still fits. It has coding style issues and miss the > manpage updating. Manpage updated. I didn't touch the whitespace issues because I already try match what is in the files it patch - tabs for debootstrap and functions, mixed for scripts/sid. There is no apparent whitespace codingstyle in debootstrap. Tabs and spaces are used in different styles in different files and even different parts of the same file. If you want me to use a specific coding style, despite of the irregularities of existing code, you will need to specify exactly what codingstyle I should follow. Also, I think for low-volume projects such as debootstrap, it is faster to just fix up the whitespaces while commiting and tell the contributor to take a close look at whitespace issues before sending the next patch. > Take also a look at || since you have one missing spaces before and after it. Fixed too. I have this vague memory that || doesn't allways work properly when there is spaces around. But I just tested and the modified version still works. diff -urN debootstrap-1.0.13.old/debian/changelog debootstrap-1.0.13/debian/changelog --- debootstrap-1.0.13.old/debian/changelog 2009-04-24 22:08:27.0 +0300 +++ debootstrap-1.0.13/debian/changelog 2009-07-19 22:50:16.0 +0300 @@ -1,3 +1,9 @@ +debootstrap (1.0.14~0.1) unstable; urgency=low + + * scratchbox support + + -- Riku Voipio Mon, 13 Jul 2009 15:43:54 +0300 + debootstrap (1.0.13) unstable; urgency=low [ Otavio Salvador ] diff -urN debootstrap-1.0.13.old/debootstrap debootstrap-1.0.13/debootstrap --- debootstrap-1.0.13.old/debootstrap 2009-03-24 16:08:43.0 +0200 +++ debootstrap-1.0.13/debootstrap 2009-07-19 22:20:28.0 +0300 @@ -79,7 +79,8 @@ --components=A,B,C use packages from the listed components of the archive --variant=Xuse variant X of the bootstrap scripts - (currently supported variants: buildd, fakechroot) + (currently supported variants: buildd, fakechroot, + scratchbox) --keyring=Kcheck Release files against keyring K --no-resolve-deps don't try to resolve dependencies automatically @@ -346,7 +347,23 @@ error 1 WHATARCH "Couldn't work out current architecture" fi -export ARCH SUITE TARGET +if [ "$TARGET" = "/" ]; then + CHROOT_CMD="" +elif doing_variant scratchbox; then + for config in ~/.scratchbox2/*/sb2.config; + do + export `grep ^SBOX_TARGET_ROOT= $config` + if [ "x$SBOX_TARGET_ROOT" = "x$TARGET" ]; then + SB2_TARGET=$(basename $(dirname $config)) + fi + done + [ "x$SB2_TARGET" != "x" ] || error 1 SBOXTARGETREQ "No scratchbox target configured for $TARGET" + CHROOT_CMD="sb2 -eR -t $SB2_TARGET" +else + CHROOT_CMD="chroot $TARGET" +fi + +export ARCH SUITE TARGET CHROOT_CMD if am_doing_phase first_stage second_stage; then if [ -x /usr/bin/id ] && [ `id -u` -ne 0 ]; then diff -urN debootstrap-1.0.13.old/debootstrap.8 debootstrap-1.0.13/debootstrap.8 --- debootstrap-1.0.13.old/debootstrap.8 2009-01-13 23:46:30.0 +0200 +++ debootstrap-1.0.13/debootstrap.8 2009-07-19 22:28:17.0 +0300 @@ -70,13 +70,15 @@ rely on this option. With this option set, this behaviour is disabled. .IP -.IP "\fB\-\-variant=minbase|buildd|fakechroot\fP" +.IP "\fB\-\-variant=minbase|buildd|fakechroot|scratchbox\fP" Name of the bootstrap script variant to use. Currently, the variants supported are minbase, which only includes essential packages and apt; buildd, which installs the build-essential packages into .IR TARGET ; and fakechroot, which installs the packages without root privileges. +Finally there is variant scratchbox, which is for creating targets +for scratchbox usage. The default, with no \fB\-\-variant=X\fP argument, is to create a base Debian installation in .IR TARGET . diff -urN debootstrap-1.0.13.old/functions debootstrap-1.0.13/functions --- debootstrap-1.0.13.old/functions 2009-03-24 16:08:43.0 +0200 +++ debootstrap-1.0.13/functions 2009-07-19 22:20:28.0 +0300 @@ -730,7 +730,7 @@ ); } in_target_nofail () { - if ! chroot "$TARGET" "$@" 2>/dev/null; then + if ! $CHROOT_CMD "$@" 2>/dev/null; then true fi return 0 @@ -741,7 +741,7 @@ local msg="$2" local arg="$3" shift; shift; shift - if ! chroot "$TARGET" "$@"; then + if ! $CHROOT_CMD "$@"; then warning "$code" "$msg" "$arg" return 1 fi @@ -749,7 +749,7 @@ } in_target () { - in_target_failmsg IN_TARGET_FAIL "Failure trying to run: %s" "chroot $TARGET $*" "$@" + in_target_failmsg IN_TARGET_FAIL "Failure trying to run: %s" "$CHRO
Processing of partman-md_46_i386.changes
partman-md_46_i386.changes uploaded successfully to localhost along with the files: partman-md_46.dsc partman-md_46.tar.gz partman-md_46_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: wait for the boot device
On Jul 19, Ferenc Wagner wrote: > Now that a kernel (and initramfs-tools) maintainer gave the > explanation you requested, how do you think we could proceed with > this? As I explained, I will consider this after I will have finished the next upload. > I'd like to add that udevsettle calls are also needed in other package > scripts (LVM, multipath, etc.) and there's even a wait_for_udev canned If you need udevsettle anywhere else than after running udevtrigger then something is either buggy or broken by design. -- ciao, Marco signature.asc Description: Digital signature
Bug#533384: marked as done (do not add ff02::3 to /etc/hosts)
Your message dated Sun, 19 Jul 2009 18:17:20 + with message-id and subject line Bug#533384: fixed in netcfg 1.50 has caused the Debian Bug report #533384, regarding do not add ff02::3 to /etc/hosts 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.) -- 533384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netcfg Version: 0.66 Severity: normal Please remove the ff02::3 address from netcfg.h, it is not actually assigned and the same change has already been done in netbase. Reference: http://www.iana.org/assignments/ipv6-multicast-addresses/ -- ciao, Marco signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: netcfg Source-Version: 1.50 We believe that the bug you reported is fixed in the latest version of netcfg, which is due to be installed in the Debian FTP archive: netcfg-static_1.50_amd64.udeb to pool/main/n/netcfg/netcfg-static_1.50_amd64.udeb netcfg_1.50.dsc to pool/main/n/netcfg/netcfg_1.50.dsc netcfg_1.50.tar.gz to pool/main/n/netcfg/netcfg_1.50.tar.gz netcfg_1.50_amd64.udeb to pool/main/n/netcfg/netcfg_1.50_amd64.udeb 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 533...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Otavio Salvador (supplier of updated netcfg 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 19 Jul 2009 15:02:44 -0300 Source: netcfg Binary: netcfg netcfg-static Architecture: source amd64 Version: 1.50 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Otavio Salvador Description: netcfg - Configure the network (udeb) netcfg-static - Configure a static network (udeb) Closes: 533384 Changes: netcfg (1.50) unstable; urgency=low . [ Christian Perrier ] * No longer add ff02::3 to /etc/hosts Thanks to Marco d'Itri for the proposed change Closes: #533384 . [ Luca Favatella ] * If wireless is disabled, don't build and link wireless related stuff. * Disable by default wireless on non-linux architectures. * Inverse the logic about building without wireless support (WIRELESS=0). * Substitute Linux-specific code in get_all_ifs() using getifaddrs(). . [ Colin Watson ] * check_kill_switch is Linux-specific; provide a stub implementation for non-Linux systems. . [ Otavio Salvador ] * Refactor dhcp.c code to use an argument list instead of an string. * Add support for udhcpc. This was based on Luk Claes but changed to avoid dropping support for dhclient, dhclient3 and pump for now. . [ Updated translations ] * Hindi (hi.po) * Italian (it.po) by Milo Casagrande Checksums-Sha1: 8870040a688d86a9b56468edac0c173ced11479f 1015 netcfg_1.50.dsc 33af3797736b55c5f02f86c21b506d72628b71b8 34 netcfg_1.50.tar.gz c0275957fbaf3114db98428a3bc51034e7f69649 303972 netcfg_1.50_amd64.udeb dc84c1211ff73e6bdb489b7e6c9c144ab1f76a22 234832 netcfg-static_1.50_amd64.udeb Checksums-Sha256: 83c3891305c2040eac9acef0dd66e7161f26ee23b490388a80f4e187b91686a1 1015 netcfg_1.50.dsc 4d73b840d170c1ce3c8e22539aee2aa01746c79eca808c189d977e5cc57c191b 34 netcfg_1.50.tar.gz 2f8c2de3561dbd89ad195939702fda3465c95bbcbbba29594f17418ed2a6b551 303972 netcfg_1.50_amd64.udeb ad7124a77cf79f4f285e439c28b1fa8d198a35a00fca6a64e85f851b95900332 234832 netcfg-static_1.50_amd64.udeb Files: c8bd45d00ec8b1be4b63659adb6da440 1015 debian-installer optional netcfg_1.50.dsc 9a68305040ae96894fc84f338573ca1a 34 debian-installer optional netcfg_1.50.tar.gz a3000ed55ff0b6b66817f1ccd2cb54ac 303972 debian-installer optional netcfg_1.50_amd64.udeb a3e1a6931bf613b0e18b9a7db160cd0b 234832 debian-installer optional netcfg-static_1.50_amd64.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkpjYJwACgkQLqiZQEml+FW9KACgu0LiTaQDp+PnXVpE1m9xtjsJ EbkAn2vrkySgTvNcmWRNtvzvhOqRVkXZ =daDP -END PGP SIGNATURE- --- End Message ---
Re: Switch to udhcpc in netcfg
Hello all, On Sat, Jul 18, 2009 at 6:00 PM, Otavio Salvador wrote: > To test the udhcpc usage you can build an installer image with the > modified udebs and do, at console: > > #: rm -rf /var/lib/dhcp3 /sbin/dhclient* To make it easier to test I've pushed the netcfg changes and also uploaded netcfg. Now the only thing you need to do, besides the removal of the above files, is to copy the udhcpc script from SVN repository[1]. 1. http://svn.debian.org/wsvn/d-i/people/waldi/packages/busybox/debian/bin/default.script This script ought to be installed at /usr/share/udhcpc/ Besides it ought to change nothing for regular users for now, specially for kFreeBSD porting efforts it is quite important. Cheers, -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
netcfg_1.50_amd64.changes ACCEPTED
Accepted: netcfg-static_1.50_amd64.udeb to pool/main/n/netcfg/netcfg-static_1.50_amd64.udeb netcfg_1.50.dsc to pool/main/n/netcfg/netcfg_1.50.dsc netcfg_1.50.tar.gz to pool/main/n/netcfg/netcfg_1.50.tar.gz netcfg_1.50_amd64.udeb to pool/main/n/netcfg/netcfg_1.50_amd64.udeb Override entries for your package: netcfg-static_1.50_amd64.udeb - optional debian-installer netcfg_1.50.dsc - source debian-installer netcfg_1.50_amd64.udeb - optional debian-installer Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 533384 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
Processing of netcfg_1.50_amd64.changes
netcfg_1.50_amd64.changes uploaded successfully to localhost along with the files: netcfg_1.50.dsc netcfg_1.50.tar.gz netcfg_1.50_amd64.udeb netcfg-static_1.50_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of netcfg_1.50_amd64.changes
netcfg_1.50_amd64.changes uploaded successfully to ftp.upload.debian.org along with the files: netcfg_1.50.dsc netcfg_1.50.tar.gz netcfg_1.50_amd64.udeb netcfg-static_1.50_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf)
Processing commands for cont...@bugs.debian.org: > reassign 515249 installation-guide-powerpc Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf) Bug reassigned from package `installation-reports' to `installation-guide-powerpc'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf)
Processing commands for cont...@bugs.debian.org: > severity 515249 normal Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf) Severity set to `normal' from `grave' > clone 515249 -1 Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf) Bug 515249 cloned as bug 537590. > retitle -1 manual: Mention console=hvc0 for ppc? Bug#537590: installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf) Changed Bug title to `manual: Mention console=hvc0 for ppc?' from `installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf)'. > reassign -1 installation-guide Bug#537590: manual: Mention console=hvc0 for ppc? Bug reassigned from package `installation-reports' to `installation-guide'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf)
severity 515249 normal clone 515249 -1 retitle -1 manual: Mention console=hvc0 for ppc? reassign -1 installation-guide thanks On Sun, Feb 15, 2009 at 10:49:36AM +, Paul McEnery wrote: > Comments/Problems: > > Initial boot: Maybe not soe much an error, I had to specify the > console at the boot prompt "console=hvc0,38400" There is no mention of hvc0 in the powerpc installation guide, so it might be useful to add a mention there. Is it common to have hvc0 on ppc? I know it only wrt. XEN. Max -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#520697: marked as done (installation-reports: xterm not work without I command metacity gnome-panel and nautilus)
Your message dated Sun, 19 Jul 2009 17:59:04 +0200 with message-id <20090719155903.ga30...@dp.lan> and subject line Re: Bug#520697: installation-reports: xterm not work without I command metacity gnome-panel and nautilus has caused the Debian Bug report #520697, regarding installation-reports: xterm not work without I command metacity gnome-panel and nautilus 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.) -- 520697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: grave Justification: renders package unusable -- Package-specific info: Boot method: CD Image version: "CD-Debian GNU/linux 5.0.0 "Lenny" - Oficial amd64 NETINST Binary-1 20090214 15:57" Date: Machine: Intel Intel Core 2 Quad Q8200 2.33GHz with 4 processor and 4 GB of ram 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: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] 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="5.0 (lenny) - installer build 20090123" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux jandira 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82X38/X48 Express DRAM Controller [8086:29e0] (rev 01) lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 82X38/X48 Express Host-Primary PCI Express Bridge [8086:29e1] (rev 01) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 02) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 [8086:294a] (rev 02) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.7 USB C
Bug#536439: marked as done (installation-reports: Postgresql package problem after clean install of Lenny-Netinst.)
Your message dated Sun, 19 Jul 2009 17:20:56 +0200 with message-id <20090719152055.ga29...@dp.lan> and subject line Re: Bug#536439: installation-reports: Postgresql package problem after clean install of Lenny-Netinst. has caused the Debian Bug report #536439, regarding installation-reports: Postgresql package problem after clean install of Lenny-Netinst. 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.) -- 536439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: grave Justification: renders package unusable I had PostgreSQL 8.3 from Lenny running after I "aptitude install postgresql" in a former isntalation, this time I wanted to start it right away, so I clicked the "Database server" field in the "graphical expert instalation" for the XCFE4 desltop. When the mahine rebooted the /etc/postgresql/ folder was created, but it was empty and there were no clusters running. I did a "aptitude purge postgresql?" and a "aptitude install postgresql" and now everything works fine. I use PostgreSQL for the gnumed-client/testing program, by the way ;-) cheers. Rogerio (Brasil) -- Package-specific info: Boot method: CD Image version: Lenny 5.0 Netinst - Stable CD made with first stable image in 2008 Date: Machine: Toshiba Satellite M35X-S114 (old :) 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: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] 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="5.0 (lenny) - installer build 20090123" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux acupuntura 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3580] (rev 02) lspci -knn: 00:00.1 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3584] (rev 02) lspci -knn: 00:00.3 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3585] (rev 02) lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 03) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 83) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge [8086:24cc] (rev 03) lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE Controller [8086:24ca] (rev 03) lspci -knn: Kernel drive
Re: please let dhcp3 into testing
Christian Perrier wrote: Quoting Luk Claes (l...@debian.org): Cyril Brulebois wrote: Andrew Pollock (18/07/2009): I didn't realise that udeb-generating packages were still frozen. Is that necessary? Could you please let 3.1.2p1-1 into testing. It has a security fix for CVE-2009-0692 You're supposed to mail -boot as well… (Doing so, adjusting subject.) And yes, udeb-generating are always frozen. For the moment, it's supposed to change in the future though. Andrew's suggestion in his blog is interesting, though: "I think if debian-boot is going to mandate this freeze for udeb-generating packages, then someone on debian-boot should be getting a report every day of udeb-generating packages that are due to enter testing in the next 24-48 hours, so they can be proactively vetted and their entry into testing not delayed unnecessarily. It shouldn't have to fall on me as the package maintainer to have to notice." That seems feasible and sustainable, isn't it? There is a webpage [1] tracking it, maybe it should just be used more? Cheers Luk [1] http://people.debian.org/~joeyh/d-i/testing-summary.html -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#534248: debian-installer: File system creation failed
Processing commands for cont...@bugs.debian.org: > reassign 534248 parted Bug#534248: debian-installer: File system creation failed Bug reassigned from package `debian-installer' to `parted'. > found 534248 1.8.8.git.2009.06.03-1 Bug#534248: debian-installer: File system creation failed Bug marked as found in version 1.8.8.git.2009.06.03-1. > tags 534248 + pending Bug#534248: debian-installer: File system creation failed There were no tags set. Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: wait for the boot device
maximilian attems writes: > On Thu, Jun 25, 2009 at 01:55:40PM +0200, Marco d'Itri wrote: > >> On Jun 25, Ferenc Wagner wrote: >> >>> Any word on this? >> >> I'd like to get an explanation from the kernel maintainers about why >> this would be needed (and it would be needed in my package). > > your package ships the udev initramfs hook with the udevsettle call. > > i could easily put it somewhere else, but it is the logical place > to put this modprobe in. Hi Marco, Now that a kernel (and initramfs-tools) maintainer gave the explanation you requested, how do you think we could proceed with this? I'd like to add that udevsettle calls are also needed in other package scripts (LVM, multipath, etc.) and there's even a wait_for_udev canned function for this purpose, but these are more optional than yours. -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: please let dhcp3 into testing
Quoting Luk Claes (l...@debian.org): > Cyril Brulebois wrote: > >Andrew Pollock (18/07/2009): > >>I didn't realise that udeb-generating packages were still frozen. Is that > >>necessary? Could you please let 3.1.2p1-1 into testing. It has a security > >>fix for CVE-2009-0692 > > > >You're supposed to mail -boot as well… (Doing so, adjusting subject.) > > > >And yes, udeb-generating are always frozen. > > For the moment, it's supposed to change in the future though. Andrew's suggestion in his blog is interesting, though: "I think if debian-boot is going to mandate this freeze for udeb-generating packages, then someone on debian-boot should be getting a report every day of udeb-generating packages that are due to enter testing in the next 24-48 hours, so they can be proactively vetted and their entry into testing not delayed unnecessarily. It shouldn't have to fall on me as the package maintainer to have to notice." That seems feasible and sustainable, isn't it? signature.asc Description: Digital signature
Processed: block 328498 with 537535, block 328498 with 537536
Processing commands for cont...@bugs.debian.org: > block 328498 with 537535 Bug#537535: other missing utilities for debconf replacement Bug#328498: switch to cdebconf as default Was blocked by: 212881 247744 321038 327730 331730 331731 331732 331733 331734 331735 331736 331737 331738 331739 331740 331741 331742 331743 331744 331745 331746 331747 331748 331749 331750 331751 331752 331753 331754 331756 331763 331764 331765 331766 331767 331768 331769 331770 331771 331772 331773 331774 331775 331776 331777 331778 331779 331780 331781 331782 331783 331784 331785 331786 331787 331788 331789 331790 331791 331792 331793 331794 331795 331796 331797 331798 331799 331800 331801 331802 331803 331804 331805 331806 331807 331808 331809 331810 331811 331812 331813 331814 331815 331816 331817 331818 331819 331820 331821 331822 331823 331824 331825 331826 331827 331828 331829 331830 331831 331832 331833 331834 331835 331836 331837 331838 331839 331840 331841 331842 331843 331844 331845 331846 331847 331848 331849 331850 331851 331852 331853 331854 331855 331856 331857 331858 331859 331860 331861 331862 331863 331864 331865 331866 331867 331868 331869 331870 331871 3 31872 331873 331874 331875 331876 331877 331878 331879 331880 331881 331882 331883 331884 331885 331886 331887 331888 331889 331890 331891 331892 331893 331894 331895 331896 331897 331898 331899 331900 331901 331902 331903 331904 331905 331906 331907 331908 331909 331910 331911 331912 331913 331914 331915 331916 331917 331918 331919 331920 331921 331922 331923 331924 331925 331926 331927 331928 331929 331930 331931 331932 331933 331934 331935 331936 331937 331938 331939 331940 331941 331942 331943 331944 331945 331946 331947 331948 331949 331950 331951 331952 331953 331954 331955 331956 331957 331958 331959 331960 331961 331962 331963 331964 331965 331966 331967 331968 331969 331970 331971 331972 331973 331974 331975 331976 331977 331978 331979 331980 331981 331982 331983 331984 331985 331986 331987 331988 331989 331990 331991 331992 331993 331994 331995 331996 331997 331998 331999 332000 332001 332002 332003 332004 332005 332006 332007 332008 332009 332010 332011 332012 332 013 332014 332015 332016 332017 332018 332019 332020 332021 332022 332023 332024 332025 332026 332027 332028 332029 332030 332031 332032 332033 332034 332035 332036 332037 332038 332039 332040 332041 332042 332043 332044 332045 332046 332047 332048 332049 332050 332051 332052 332053 332054 332055 332056 332057 332058 332059 332060 332061 332062 332063 332064 332065 332066 332067 332068 332069 332070 332071 332072 332073 332074 332075 332076 332077 332078 332079 332080 332081 332082 332083 332084 332085 332086 332087 332088 332089 332090 332091 332092 332093 332094 332095 332096 332097 332098 332099 332100 332101 332102 332103 332104 332105 332106 332107 332108 332109 332110 332111 332112 332113 332114 332115 332116 332117 332118 332119 332120 332121 332122 332123 332124 332125 332126 332127 332128 332129 332130 332131 332132 332133 332134 332135 332136 332137 332138 332139 332140 332141 332142 332143 332144 332145 332146 332147 332148 332149 332150 332151 332152 332153 33215 4 332155 332156 332157 332158 332159 332160 332161 332162 332163 332164 332165 332166 332167 332168 332169 332170 332171 332172 332173 332174 332175 332176 332177 332178 393455 397890 397891 402570 415684 415685 415688 415689 415691 442288 442290 442291 442293 443760 448476 448477 449540 451130 469363 480899 Blocking bugs of 328498 added: 537535 > block 328498 with 537536 Bug#537536: missing hacks to run config script, do template autoload, etc Bug#328498: switch to cdebconf as default Was blocked by: 212881 247744 321038 327730 331730 331731 331732 331733 331734 331735 331736 331737 331738 331739 331740 331741 331742 331743 331744 331745 331746 331747 331748 331749 331750 331751 331752 331753 331754 331756 331763 331764 331765 331766 331767 331768 331769 331770 331771 331772 331773 331774 331775 331776 331777 331778 331779 331780 331781 331782 331783 331784 331785 331786 331787 331788 331789 331790 331791 331792 331793 331794 331795 331796 331797 331798 331799 331800 331801 331802 331803 331804 331805 331806 331807 331808 331809 331810 331811 331812 331813 331814 331815 331816 331817 331818 331819 331820 331821 331822 331823 331824 331825 331826 331827 331828 331829 331830 331831 331832 331833 331834 331835 331836 331837 331838 331839 331840 331841 331842 331843 331844 331845 331846 331847 331848 331849 331850 331851 331852 331853 331854 331855 331856 331857 331858 331859 331860 331861 331862 331863 331864 331865 331866 331867 331868 331869 331870 331871 3 31872 331873 331874 331875 331876 331877 331878 331879 331880 331881 331882 331883 331884 331885 331886 331887 331888 331889 331890 331891 331892 331893 331894 331895 331896 331897 331898 331899 331900 331901 331902 331903 331904 331905 331906 331907 331908 331909 331910 331911 331912 331913 331914 331915
Processed: forcibly merging 469363 537522
Processing commands for cont...@bugs.debian.org: > forcemerge 469363 537522 Bug#469363: dpkg-reconfigure should run prerm upgrade Bug#537522: dpkg-reconfigure does not run prerm, postinst Forcibly Merged 469363 537522. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#537536: missing hacks to run config script, do template autoload, etc
Package: cdebconf Version: 0.146 Severity: normal perl debconf, in the "frontend" program, has complicated probing that figures out the package whose postinst script is being run, and loads the corresponding templates file and runs the corresponding config script first. (Etc.) cdebconf is missing all that ugliness. It is not needed in d-i, because udpkg kindly loads the templates, and udebs don't have config scripts. But, to replace perl debconf, all that nastiness needs to be replicated in cdebconf. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (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/bash Versions of packages cdebconf depends on: ii debconf 1.5.27 Debian configuration management sy ii libc6 2.9-19 GNU C Library: Shared libraries ii libdebian-installer4 0.63 Library of common debian-installer ii libnewt0.52 0.52.10-4 Not Erik's Windowing Toolkit - tex ii libslang2 2.1.4-3The S-Lang programming library - r ii libtextwrap1 0.1-8 text-wrapping library with i18n - cdebconf recommends no packages. Versions of packages cdebconf suggests: pn cdebconf-gtk (no description available) -- no debconf information -- see shy jo signature.asc Description: Digital signature
Bug#537535: other missing utilities for debconf replacement
Package: cdebconf Version: 0.146 Severity: normal In order to replace perl debconf, the following utilities are also probably needed in cdebconf: * debconf-set-selections (preseed has a shell version of this, just needs some minor breaking out and the ability to read stdin if no file is specified) * debconf-get-selections * debconf-show * debconf-escape (the perl script could be copied into cdebconf and would work ok, but cdebconf is also missing the escape CAPB) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (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/bash Versions of packages cdebconf depends on: ii debconf 1.5.27 Debian configuration management sy ii libc6 2.9-19 GNU C Library: Shared libraries ii libdebian-installer4 0.63 Library of common debian-installer ii libnewt0.52 0.52.10-4 Not Erik's Windowing Toolkit - tex ii libslang2 2.1.4-3The S-Lang programming library - r ii libtextwrap1 0.1-8 text-wrapping library with i18n - cdebconf recommends no packages. Versions of packages cdebconf suggests: pn cdebconf-gtk (no description available) -- no debconf information -- see shy jo signature.asc Description: Digital signature
flash-kernel_2.20_armel.changes ACCEPTED
Accepted: flash-kernel-installer_2.20_armel.udeb to pool/main/f/flash-kernel/flash-kernel-installer_2.20_armel.udeb flash-kernel_2.20.dsc to pool/main/f/flash-kernel/flash-kernel_2.20.dsc flash-kernel_2.20.tar.gz to pool/main/f/flash-kernel/flash-kernel_2.20.tar.gz flash-kernel_2.20_armel.deb to pool/main/f/flash-kernel/flash-kernel_2.20_armel.deb Override entries for your package: flash-kernel-installer_2.20_armel.udeb - standard debian-installer flash-kernel_2.20.dsc - source utils flash-kernel_2.20_armel.deb - optional utils Announcing to debian-devel-chan...@lists.debian.org 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
Processed: setting package to cdebconf-gtk-udeb cdebconf-slang-udeb cdebconf-text-udeb cdebconf cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb libdebconfclient0-dev cdebconf-priority libdebconfclient0
Processing commands for cont...@bugs.debian.org: > #cdebconf (0.146) UNRELEASED; urgency=low > # > # * dpkg-reconfigure: Don't treat config script exit 1 as success. > #Closes: #443760 > # * dpkg-reconfigure: Run prerm script to simulate package reinstallation. > #Closes: #469363 > # > package cdebconf-gtk-udeb cdebconf-slang-udeb cdebconf-text-udeb cdebconf > cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb libdebconfclient0-dev > cdebconf-priority libdebconfclient0 libdebconfclient0-udeb Ignoring bugs not assigned to: cdebconf-slang-udeb cdebconf-gtk-udeb cdebconf cdebconf-text-udeb cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb cdebconf-priority libdebconfclient0-dev libdebconfclient0-udeb libdebconfclient0 > tags 443760 + pending Bug#443760: dpkg-reconfigure does not detect config script exiting nonzero There were no tags set. Tags added: pending > tags 469363 + pending Bug#469363: dpkg-reconfigure should run prerm upgrade There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of flash-kernel_2.20_armel.changes
flash-kernel_2.20_armel.changes uploaded successfully to localhost along with the files: flash-kernel_2.20.dsc flash-kernel_2.20.tar.gz flash-kernel_2.20_armel.deb flash-kernel-installer_2.20_armel.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: partman-md/mdcfg merge
On Sat, Jul 18, 2009 at 06:52:51AM +0200, martin f krafft wrote: > also sprach Colin Watson [2009.07.17.2209 +0200]: > > It looks as if this is too difficult for people to test without it > > being in the archive, so in the absence of objections I've gone > > ahead and committed this. Let's see how it goes. > > I am sorry, I just couldn't. Fundamentally, there shouldn't be > anything in the way of running debconf outside of d-i to test this > on a running system, right? partman does rather assume that it's on its own on the system; for example, it has no compunctions about disabling swap, and it can get a bit upset about there being mounted partitions. At the moment, I think there would be a lot of gotchas involved in running it on a normal system. -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: setting package to cdebconf-gtk-udeb cdebconf-slang-udeb cdebconf-text-udeb cdebconf cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb libdebconfclient0-dev cdebconf-priority libdebconfclient0
Processing commands for cont...@bugs.debian.org: > #cdebconf (0.146) UNRELEASED; urgency=low > # > # * Remove newt screen clearing code. Closes: #442291 > # * dpkg-reconfigure: Fix -p to set priority. Closes: #442288 > # * dpkg-reconfigure: Fix skipping of seen questions. Closes: #442290 > # > package cdebconf-gtk-udeb cdebconf-slang-udeb cdebconf-text-udeb cdebconf > cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb libdebconfclient0-dev > cdebconf-priority libdebconfclient0 libdebconfclient0-udeb Ignoring bugs not assigned to: cdebconf-slang-udeb cdebconf-gtk-udeb cdebconf cdebconf-text-udeb cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb cdebconf-priority libdebconfclient0-dev libdebconfclient0-udeb libdebconfclient0 > tags 442291 + pending Bug#442291: debconf-communicate clears screen when used with newt frontend There were no tags set. Tags added: pending > tags 442288 + pending Bug#442288: dpkg-reconfigure -p doesn't change priority There were no tags set. Tags added: pending > tags 442290 + pending Bug#442290: dpkg-reconfigure skips seen questions There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: setting package to cdebconf-gtk-udeb cdebconf-slang-udeb cdebconf-text-udeb cdebconf cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb libdebconfclient0-dev cdebconf-priority libdebconfclient0
Processing commands for cont...@bugs.debian.org: > #cdebconf (0.146) UNRELEASED; urgency=low > # > # * Remove newt screen clearing code. Closes: #442291 > # > package cdebconf-gtk-udeb cdebconf-slang-udeb cdebconf-text-udeb cdebconf > cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb libdebconfclient0-dev > cdebconf-priority libdebconfclient0 libdebconfclient0-udeb Ignoring bugs not assigned to: cdebconf-slang-udeb cdebconf-gtk-udeb cdebconf cdebconf-text-udeb cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb cdebconf-priority libdebconfclient0-dev libdebconfclient0-udeb libdebconfclient0 > tags 442291 + pending Bug#442291: debconf-communicate clears screen when used with newt frontend Tags were: pending Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: setting package to cdebconf-gtk-udeb cdebconf-slang-udeb cdebconf-text-udeb cdebconf cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb libdebconfclient0-dev cdebconf-priority libdebconfclient0
Processing commands for cont...@bugs.debian.org: > #cdebconf (0.146) UNRELEASED; urgency=low > # > # * Remove newt screen clearing code. Closes: #442291 > # * dpkg-reconfigure: Fix -p to set priority. Closes: #442288 > # > package cdebconf-gtk-udeb cdebconf-slang-udeb cdebconf-text-udeb cdebconf > cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb libdebconfclient0-dev > cdebconf-priority libdebconfclient0 libdebconfclient0-udeb Ignoring bugs not assigned to: cdebconf-slang-udeb cdebconf-gtk-udeb cdebconf cdebconf-text-udeb cdebconf-udeb cdebconf-gtk cdebconf-newt-udeb cdebconf-priority libdebconfclient0-dev libdebconfclient0-udeb libdebconfclient0 > tags 442291 + pending Bug#442291: debconf-communicate clears screen when used with newt frontend Tags were: pending Tags added: pending > tags 442288 + pending Bug#442288: dpkg-reconfigure -p doesn't change priority Tags were: pending Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: block 328498 with 443760, block 328498 with 469363
Processing commands for cont...@bugs.debian.org: > block 328498 with 443760 Bug#443760: dpkg-reconfigure does not detect config script exiting nonzero Bug#328498: switch to cdebconf as default Was blocked by: 212881 247744 321038 327730 331730 331731 331732 331733 331734 331735 331736 331737 331738 331739 331740 331741 331742 331743 331744 331745 331746 331747 331748 331749 331750 331751 331752 331753 331754 331756 331763 331764 331765 331766 331767 331768 331769 331770 331771 331772 331773 331774 331775 331776 331777 331778 331779 331780 331781 331782 331783 331784 331785 331786 331787 331788 331789 331790 331791 331792 331793 331794 331795 331796 331797 331798 331799 331800 331801 331802 331803 331804 331805 331806 331807 331808 331809 331810 331811 331812 331813 331814 331815 331816 331817 331818 331819 331820 331821 331822 331823 331824 331825 331826 331827 331828 331829 331830 331831 331832 331833 331834 331835 331836 331837 331838 331839 331840 331841 331842 331843 331844 331845 331846 331847 331848 331849 331850 331851 331852 331853 331854 331855 331856 331857 331858 331859 331860 331861 331862 331863 331864 331865 331866 331867 331868 331869 331870 331871 3 31872 331873 331874 331875 331876 331877 331878 331879 331880 331881 331882 331883 331884 331885 331886 331887 331888 331889 331890 331891 331892 331893 331894 331895 331896 331897 331898 331899 331900 331901 331902 331903 331904 331905 331906 331907 331908 331909 331910 331911 331912 331913 331914 331915 331916 331917 331918 331919 331920 331921 331922 331923 331924 331925 331926 331927 331928 331929 331930 331931 331932 331933 331934 331935 331936 331937 331938 331939 331940 331941 331942 331943 331944 331945 331946 331947 331948 331949 331950 331951 331952 331953 331954 331955 331956 331957 331958 331959 331960 331961 331962 331963 331964 331965 331966 331967 331968 331969 331970 331971 331972 331973 331974 331975 331976 331977 331978 331979 331980 331981 331982 331983 331984 331985 331986 331987 331988 331989 331990 331991 331992 331993 331994 331995 331996 331997 331998 331999 332000 332001 332002 332003 332004 332005 332006 332007 332008 332009 332010 332011 332012 332 013 332014 332015 332016 332017 332018 332019 332020 332021 332022 332023 332024 332025 332026 332027 332028 332029 332030 332031 332032 332033 332034 332035 332036 332037 332038 332039 332040 332041 332042 332043 332044 332045 332046 332047 332048 332049 332050 332051 332052 332053 332054 332055 332056 332057 332058 332059 332060 332061 332062 332063 332064 332065 332066 332067 332068 332069 332070 332071 332072 332073 332074 332075 332076 332077 332078 332079 332080 332081 332082 332083 332084 332085 332086 332087 332088 332089 332090 332091 332092 332093 332094 332095 332096 332097 332098 332099 332100 332101 332102 332103 332104 332105 332106 332107 332108 332109 332110 332111 332112 332113 332114 332115 332116 332117 332118 332119 332120 332121 332122 332123 332124 332125 332126 332127 332128 332129 332130 332131 332132 332133 332134 332135 332136 332137 332138 332139 332140 332141 332142 332143 332144 332145 332146 332147 332148 332149 332150 332151 332152 332153 33215 4 332155 332156 332157 332158 332159 332160 332161 332162 332163 332164 332165 332166 332167 332168 332169 332170 332171 332172 332173 332174 332175 332176 332177 332178 393455 397890 397891 402570 415684 415685 415688 415689 415691 442288 442290 442291 442293 448476 448477 449540 451130 480899 Blocking bugs of 328498 added: 443760 > block 328498 with 469363 Bug#469363: dpkg-reconfigure should run prerm upgrade Bug#328498: switch to cdebconf as default Was blocked by: 212881 247744 321038 327730 331730 331731 331732 331733 331734 331735 331736 331737 331738 331739 331740 331741 331742 331743 331744 331745 331746 331747 331748 331749 331750 331751 331752 331753 331754 331756 331763 331764 331765 331766 331767 331768 331769 331770 331771 331772 331773 331774 331775 331776 331777 331778 331779 331780 331781 331782 331783 331784 331785 331786 331787 331788 331789 331790 331791 331792 331793 331794 331795 331796 331797 331798 331799 331800 331801 331802 331803 331804 331805 331806 331807 331808 331809 331810 331811 331812 331813 331814 331815 331816 331817 331818 331819 331820 331821 331822 331823 331824 331825 331826 331827 331828 331829 331830 331831 331832 331833 331834 331835 331836 331837 331838 331839 331840 331841 331842 331843 331844 331845 331846 331847 331848 331849 331850 331851 331852 331853 331854 331855 331856 331857 331858 331859 331860 331861 331862 331863 331864 331865 331866 331867 331868 331869 331870 331871 3 31872 331873 331874 331875 331876 331877 331878 331879 331880 331881 331882 331883 331884 331885 331886 331887 331888 331889 331890 331891 331892 331893 331894 331895 331896 331897 331898 331899 331900 331901 331902 331903 331904 331905 331906 331907 331908 331909 331910 331911 331912 331913 331914 331915 331916 331917 33191
Bug#537523: passthrough frontend and debconf-apt-progress needed to replace perl debconf
Package: cdebconf Version: 0.146 Severity: normal In order to fully replace perl debconf, cdebconf needs to have an implementation of debconf-apt-progress and the passthrough frontend. This doesn't really block the perl debconf replacement bug, because it would be possible to use cdebconf as a debconf replacement without this. But for d-i to install it to /target by default, this will need to be dealt with. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (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/bash Versions of packages cdebconf depends on: ii debconf 1.5.27 Debian configuration management sy ii libc6 2.9-19 GNU C Library: Shared libraries ii libdebian-installer4 0.63 Library of common debian-installer ii libnewt0.52 0.52.10-4 Not Erik's Windowing Toolkit - tex ii libslang2 2.1.4-3The S-Lang programming library - r ii libtextwrap1 0.1-8 text-wrapping library with i18n - cdebconf recommends no packages. Versions of packages cdebconf suggests: pn cdebconf-gtk (no description available) -- no debconf information -- see shy jo signature.asc Description: Digital signature
Bug#212881: not a blocker
unblock 328498 with 212881 retitle 212881 alternative noninteractive (but visible) frontend tag 212881 patch thanks cdebconf already treats "noninteractive" the same as "none" when selecting a frontend, which is I think close enough to perl debconf's behavior that this bug is not a blocker for cdebconf as the default. -- see shy jo signature.asc Description: Digital signature
Bug#537522: dpkg-reconfigure does not run prerm, postinst
Package: cdebconf Version: 0.146 Severity: normal Perl dpkg-reconfigure runs the prerm upgrade and the postinst configure, so as to simulate a page upgrade and cause the reconfiguration to take effect. cdebconf is missing this. Also, perl dpkg-reconfigure has a nasty hack to detect prerm/postinst scripts using debconf, so as to avoid them starting another copy of debconf (which would contend with it writing to the DB). This might need to be brought over as well. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (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/bash Versions of packages cdebconf depends on: ii debconf 1.5.27 Debian configuration management sy ii libc6 2.9-19 GNU C Library: Shared libraries ii libdebian-installer4 0.63 Library of common debian-installer ii libnewt0.52 0.52.10-4 Not Erik's Windowing Toolkit - tex ii libslang2 2.1.4-3The S-Lang programming library - r ii libtextwrap1 0.1-8 text-wrapping library with i18n - cdebconf recommends no packages. Versions of packages cdebconf suggests: pn cdebconf-gtk (no description available) -- no debconf information -- see shy jo signature.asc Description: Digital signature