Bug#681227: some analysis
On Sat, Dec 15, 2012 at 06:24:46PM +0100, Wouter Verhelst wrote: At this point, I'm tempted to add a check to the for loop that starts on line 650 in the current HEAD (commit 062ddbcb66150) for something along the lines of: if [ ! -b $bootdev ]; then # jump to the next loop iteration here fi I've done that, but also added a check so that if this means we don't actually install grub to any boot device, grub-installer will fail. It's not a proper fix, so I didn't mark the change as closing this bug; but I do plan to downgrade the severity (since it now no longer causes the installation to fail) once it's been built everywhere. -- Copyshops should do vouchers. So that next time some bureaucracy requires you to mail a form in triplicate, you can mail it just once, add a voucher, and save on postage. -- 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/20121216163433.ga21...@grep.be
Processing of grub-installer_1.84_amd64.changes
grub-installer_1.84_amd64.changes uploaded successfully to localhost along with the files: grub-installer_1.84.dsc grub-installer_1.84.tar.gz grub-installer_1.84_amd64.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tkha0-0006xa...@franck.debian.org
Bug#651720: marked as done (new ZFS installs completely broken in Wheezy/Sid)
Your message dated Sun, 16 Dec 2012 16:47:29 + with message-id e1tkhnb-0001sa...@franck.debian.org and subject line Bug#651720: fixed in grub-installer 1.84 has caused the Debian Bug report #651720, regarding new ZFS installs completely broken in Wheezy/Sid 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.) -- 651720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: partman-zfs Severity: grave 2011/12/11 Robert Millan r...@debian.org: 2.3- /boot/zfs/zpool.cache is NOT present!! No idea why this happens, but potentially it could also break installed systems (since they attempt to boot using outdated /boot/zfs/zpool.cache that was generated with older ZFS version). Could this be related to #651624 ? Some ZFS on root documentation suggests that after creating a pool you should export it and import it to flush zpool.cache. This needs to be verified. I put it in partman-zfs so it's not forgotten. -- Robert Millan ---End Message--- ---BeginMessage--- Source: grub-installer Source-Version: 1.84 We believe that the bug you reported is fixed in the latest version of grub-installer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 651...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wouter Verhelst wou...@debian.org (supplier of updated grub-installer 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, 16 Dec 2012 17:28:47 +0100 Source: grub-installer Binary: grub-installer Architecture: source amd64 Version: 1.84 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Wouter Verhelst wou...@debian.org Description: grub-installer - Install GRUB on a hard disk (udeb) Closes: 651720 Changes: grub-installer (1.84) unstable; urgency=low . * Add workaround for #681227. Won't mark it as closed, since I didn't find the root cause, but with this at least we can downgrade the severity. * Apply patch from Arno Töll to fix / on ZFS where /boot isn't. Closes: #651720. * Add $SELF to uploaders Checksums-Sha1: f9895d6ef61627d3121e39588d1e9d2e2d30367a 1897 grub-installer_1.84.dsc 938d8f332b7b2ccb849902c088e1f23d1c638ac0 221007 grub-installer_1.84.tar.gz dc831784646f53a1d20b002b0fc83c391822b027 206300 grub-installer_1.84_amd64.udeb Checksums-Sha256: a3339314283f5daf20bd42ad29f9923d3eb54542125b277d0e816c4bac3b50ec 1897 grub-installer_1.84.dsc b344a42065436f2db2b8194cd694db9f0c1221a7cea415a1b800761541941863 221007 grub-installer_1.84.tar.gz fc047c026ce5a79b723dc9378fd6563b5be92dc8c6385c37688712618a4712ca 206300 grub-installer_1.84_amd64.udeb Files: d4cd78bc984214719a92f62ca938e0a0 1897 debian-installer standard grub-installer_1.84.dsc fcbe2e5ad942dca50e3f8b63f328fcdf 221007 debian-installer standard grub-installer_1.84.tar.gz acfd40440263685305710a944b37cd3a 206300 debian-installer standard grub-installer_1.84_amd64.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJQzfbUAAoJEMKUD5Ub3wqdkG0P/3RqhM4MMNcm++zaGTsELfpm jCaoGPXUw0P0Z22hEtkSGlZqGMYO3l/DuILg3EjQ3LhdCydooNnxzS8cJaaP+Pqh A/z8/ZEuNJt0zDykO4vgKyfeEdCbZw+Y9ujS1YXw+mDDVh9K7l/l4K8qsFvTKE6x 0yPj+fMuWfoqyDViKKV/LfNs3pUVGQUvqxeg4kmoo1xjq3xTau18t8XfVpanuWsj PqCS60tP1qsqWGdMZRXJM1SNeKpRUBEvroXDcMdmsKJGb1PFaZ4hVmbWAmbYOmB8 904d8ut6d/g6FT5SHHYuRibjOKuwHSjhedGfbKFdzYUc4kz3uAUcrZJ2PEJlIb4F 0qwOAJjycR6nsOwWnf9VYwPVDiN6yff3eVKt0nR3v1z1evjZJZ3WfluIB4pULGWY 26CqLzFTsnlV72gLq/LS6oQ7k6b+fnZSwlrknN4eVaBF+0glU9VaD1hR9lSjZZuX /1IkiP3HFJXyB9nnv5f4pS/7tZhZSYi3d7ocCZ057nz9bfTPnrXsJ14JZnuJRBUY 14v0U3ww18DY+VSKnTeVCrwGWYLDoFZXSVon0XFTjYphsO7zwl1n12UCxJ84v56I jjo0tycKiKeTaYPJ9XafamyYBMBQYTcnGz7Kz71Nb/wo2+hWJV/91GobXCUXODJg w+jDoUQ9KJid09hkScDE =lHb0 -END PGP SIGNATUREEnd Message---
grub-installer_1.84_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 16 Dec 2012 17:28:47 +0100 Source: grub-installer Binary: grub-installer Architecture: source amd64 Version: 1.84 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Wouter Verhelst wou...@debian.org Description: grub-installer - Install GRUB on a hard disk (udeb) Closes: 651720 Changes: grub-installer (1.84) unstable; urgency=low . * Add workaround for #681227. Won't mark it as closed, since I didn't find the root cause, but with this at least we can downgrade the severity. * Apply patch from Arno Töll to fix / on ZFS where /boot isn't. Closes: #651720. * Add $SELF to uploaders Checksums-Sha1: f9895d6ef61627d3121e39588d1e9d2e2d30367a 1897 grub-installer_1.84.dsc 938d8f332b7b2ccb849902c088e1f23d1c638ac0 221007 grub-installer_1.84.tar.gz dc831784646f53a1d20b002b0fc83c391822b027 206300 grub-installer_1.84_amd64.udeb Checksums-Sha256: a3339314283f5daf20bd42ad29f9923d3eb54542125b277d0e816c4bac3b50ec 1897 grub-installer_1.84.dsc b344a42065436f2db2b8194cd694db9f0c1221a7cea415a1b800761541941863 221007 grub-installer_1.84.tar.gz fc047c026ce5a79b723dc9378fd6563b5be92dc8c6385c37688712618a4712ca 206300 grub-installer_1.84_amd64.udeb Files: d4cd78bc984214719a92f62ca938e0a0 1897 debian-installer standard grub-installer_1.84.dsc fcbe2e5ad942dca50e3f8b63f328fcdf 221007 debian-installer standard grub-installer_1.84.tar.gz acfd40440263685305710a944b37cd3a 206300 debian-installer standard grub-installer_1.84_amd64.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJQzfbUAAoJEMKUD5Ub3wqdkG0P/3RqhM4MMNcm++zaGTsELfpm jCaoGPXUw0P0Z22hEtkSGlZqGMYO3l/DuILg3EjQ3LhdCydooNnxzS8cJaaP+Pqh A/z8/ZEuNJt0zDykO4vgKyfeEdCbZw+Y9ujS1YXw+mDDVh9K7l/l4K8qsFvTKE6x 0yPj+fMuWfoqyDViKKV/LfNs3pUVGQUvqxeg4kmoo1xjq3xTau18t8XfVpanuWsj PqCS60tP1qsqWGdMZRXJM1SNeKpRUBEvroXDcMdmsKJGb1PFaZ4hVmbWAmbYOmB8 904d8ut6d/g6FT5SHHYuRibjOKuwHSjhedGfbKFdzYUc4kz3uAUcrZJ2PEJlIb4F 0qwOAJjycR6nsOwWnf9VYwPVDiN6yff3eVKt0nR3v1z1evjZJZ3WfluIB4pULGWY 26CqLzFTsnlV72gLq/LS6oQ7k6b+fnZSwlrknN4eVaBF+0glU9VaD1hR9lSjZZuX /1IkiP3HFJXyB9nnv5f4pS/7tZhZSYi3d7ocCZ057nz9bfTPnrXsJ14JZnuJRBUY 14v0U3ww18DY+VSKnTeVCrwGWYLDoFZXSVon0XFTjYphsO7zwl1n12UCxJ84v56I jjo0tycKiKeTaYPJ9XafamyYBMBQYTcnGz7Kz71Nb/wo2+hWJV/91GobXCUXODJg w+jDoUQ9KJid09hkScDE =lHb0 -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tkhnb-0001su...@franck.debian.org
Bug#694344: installation-report: Wheezy beta set up on FSC Futro S400
Forwarded Message From: Andreas Glaeser bugs.andreas.glae...@freenet.de To: Ben Hutchings b...@decadent.org.uk Subject: Re: Bug#694344: installation-report: Wheezy beta set up on FSC Futro S400 Date: Sun, 16 Dec 2012 14:53:40 +0100 On Mon, 26 Nov 2012 01:33:23 +0100 Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2012-11-25 at 18:48 +0100, Andreas Glaeser wrote: [...] Finally CPU-frequency-scaling was enabled, but I did not manage to make this persistent through reboots at first try. I am going to file this separately against the package 'cpufreqd'. The kernel is supposed to trigger loading of the CPU frequency scaling driver that is appropriate for your CPU. It should no longer rely on cpufreqd or cpufrequtils. Did this not happen? Which driver did you need to load? Ben. As my device does not boot anymore, I can not look up any current information, but what I saw upon first installation can be seen here: http://kmuto.jp/debian/hcl/Fujitsu+Siemens/Futro+S400 thr 'powernow_k7'-module was used. Bootproblems were intermittent at first, now the system will not start anymore at all. I guess it is an IRQ- or ACPI-related problem, because when I try to boot in 'recovery-mode', the output I see there points into this direction. Enabling frequency-scaling in userspace was no problem: 694...@bugs.debian.org Now I do not know, where to report the problem against, to be honest I also doubt, that anyone is going to fix it for me. -- 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/1355680911.18807.140.ca...@deadeye.wl.decadent.org.uk
Bug#694344: Device does not work with 'linux-image-686-pae', but it is the default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First there were intermittent bootproblems, then more often and finally the box would not boot anymore at all. I tried all kinds of BIOS-settings changes, but could not resolve the situation, began to feel desperate already. Then I installed the XFCE-version of Linux-Mint-Debian-Edition and found, that this works and that the default there is actually 'linux-image-486', which works. linux-image-686-pae is not bootable, but hangs upon showing the grub-menu. So the default for this machine has to be changed in Debian, too. Until this happens, the only workaround I can think of right now is to install in expert mode and choose the - -486-kernel during the process. Having a -686-kernel without PAE again would be nicer here, too, else users have to build their own custom kernels especially for AMD-Geode to get the full performance potential out of their boxes. Thus changing the severity of this report to 'important'. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlDOERoACgkQ5+rBHyUt5wtoiQCfTcetIKklKUly86jPxhjLvFsA pMEAn3EgFffRQiUMDsLPWm+6VtvU1PJ5 =f0bP -END PGP SIGNATURE-
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 694344 important Bug #694344 [installation-reports] installation-report: Wheezy beta set up on FSC Futro S400 Severity set to 'important' from 'wishlist' End of message, stopping processing here. Please contact me if you need assistance. -- 694344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.135568228022041.transcr...@bugs.debian.org
Bug#694344: Device does not work with 'linux-image-686-pae', but it is the default
On Sun, 2012-12-16 at 19:21 +0100, Andreas Glaeser wrote: First there were intermittent bootproblems, then more often and finally the box would not boot anymore at all. I tried all kinds of BIOS-settings changes, but could not resolve the situation, began to feel desperate already. Then I installed the XFCE-version of Linux-Mint-Debian-Edition and found, that this works and that the default there is actually 'linux-image-486', which works. linux-image-686-pae is not bootable, but hangs upon showing the grub-menu. And yet previously you said it was bootable. So it would seem that the hardware is progressively failing. So the default for this machine has to be changed in Debian, too. Until this happens, the only workaround I can think of right now is to install in expert mode and choose the -486-kernel during the process. We don't have a big map of processor models to kernel flavours, we just look at what the actual processor features are. This computer has a Geode NX processor that supports PAE (since it is based on the K7 core, like the Athlon processors). It is a completely different design from the older Geode processors based on the MediaGX core, for which we would install the 486 flavour. Having a -686-kernel without PAE again would be nicer here, too, else users have to build their own custom kernels especially for AMD-Geode to get the full performance potential out of their boxes. There don't seem to be any Geode models that can run a 686 flavour but not a 686-pae flavour. Also, the 486 flavour is optimised for uniprocessor systems. Ben. Thus changing the severity of this report to 'important'. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way. signature.asc Description: This is a digitally signed message part
Processed (with 1 errors): merging 606268 682608
Processing commands for cont...@bugs.debian.org:
# duplicate behavior
merge 606268 682608
Bug #606268 [network-manager] Network interface used for installation is
configured as unmanaged by NM
Bug #609072 [network-manager] Network interface used for installation is
configured as unmanaged by NM
Bug #611281 [network-manager] Network interface used for installation is
configured as unmanaged by NM
Bug #617906 [network-manager] Network interface used for installation is
configured as unmanaged by NM
Unable to merge bugs because:
blockedby of #682608 is '' not '614884'
affects of #682608 is 'network-manager' not ''
package of #682608 is 'netcfg' not 'network-manager'
Failed to merge 606268: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2742ce8)',
'requester', 'Kees Cook k...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'1355689334-2613-bts-k...@debian.org', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', undef, 'clonebugs',
'HASH(0x26bc160)', 'limit', 'HASH(0x26bbb48)', 'common_control_options',
'ARRAY(0x26bbb90)', 'errors', ...) called at /usr/lib/debbugs/service line 474
thanks
Stopping processing here.
Please contact me if you need assistance.
--
606268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606268
609072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609072
611281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611281
617906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617906
682608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.13556893374970.transcr...@bugs.debian.org
Bug#696123: partman-base: need progress wrapper for non-libparted-based filesystem operations
Package: partman-base Version: 162 Severity: wishlist parted 3.x removes most of the ped_file_system_* entry points that required extensive copies of file system code in libparted, with the exception of some limited support for HFS+ and FAT resizing (see its NEWS file for more details; facilities such as file system probing are still available). d-i still uses these for important functions. In most cases we fall back to external utilities, but if there are any remaining places where we don't then we'll need to fix those. However, simply falling back to external utilities is not a functionally-equivalent option right now, because in general we have no support for handling progress information from those utilities. Most of them have some kind of progress interface, usually requiring some special option and designed for human consumption rather than machine parsing. Rather than the Sisyphean task of giving all the appropriate utilities machine-parseable progress interface, I instead suggest that we study the current progress interfaces and try to identify some common factors that can be parsed heuristically (e.g. solid bar of characters; \-/|-style spinner; percentage output), and write a wrapper utility that can translate some of the common ones into debconf progress output. I think this ought to be a single program in partman-base, since there are only so many ways people have invented for console progress interfaces and we don't want to keep reinventing the wheel. We can then use that to wrap various mkfs, resize, etc. utilities, and in the process fix some ancient bugs about lack of progress feedback in various operations since some cases haven't actually used libparted's file system support for a while. The relevant parted_server commands to grep for in various partman-* modules for ideas on the kinds of utilities that need to be wrapped are: CREATE_FILE_SYSTEM CHECK_FILE_SYSTEM RESIZE_PARTITION (Theoretically also COPY_PARTITION but we have no fallback for that; we may have to either desupport this or reimplement it by hand somehow.) I looked at doing this once but unfortunately I seem to have lost the source code for my attempt; I'd only really made a start at it anyway. I'm filing this bug as a memory aid, and because people keep asking me what's happening with packaging of parted 3.x and I want to have something reasonably coherent to point them to. -- Colin Watson [cjwat...@debian.org] -- 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/20121217001112.gu21...@riva.dynamic.greenend.org.uk
Bug#696124: (no subject)
Subject: installation-reports: The installer, when finished, ejects the optical disk. This is unhelpful and annoying, especially if you are installing from an .iso image into a virtual machine, and wish to install packages from the disk after the install (and APT sources.list defaults to an install from a local disk vs. network servers). Ejecting the optical disk is a bad solution to the problem of inexperienced users inadvertantly re-entering the installer after the install is complete; a more helpful solution wuld be something similiar to Microsoft Windows, which, if it detects a hard disk is bootable, prompts the user to strike a key if they wish to boot from the CD-ROM (and if no key is pressed within 5 seconds, automatically defaults to booting the hard disk). Package: installation-reports Severity: wishlist -- Package-specific info: Boot method: CD Image version: debian-6.0.6-i386-DVD-1.iso Date: Date and time of the install Machine: VMware VM Partitions: df -Tl will do; the raw partition table is preferred 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: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- 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=6.0 (squeeze) - installer build 20110106+squeeze4+b2 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux dsql1 2.6.32-5-486 #1 Sun Sep 23 09:17:35 UTC 2012 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 01) lspci -knn: Subsystem: VMware Device [15ad:1976] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge [8086:7191] (rev 01) lspci -knn: 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 08) lspci -knn: Subsystem: VMware Device [15ad:1976] lspci -knn: 00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) lspci -knn: Subsystem: VMware Device [15ad:1976] lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08) lspci -knn: Subsystem: VMware Device [15ad:1976] lspci -knn: 00:07.7 System peripheral [0880]: VMware Virtual Machine Communication Interface [15ad:0740] (rev 10) lspci -knn: Subsystem: VMware Virtual Machine Communication Interface [15ad:0740] lspci -knn: 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] lspci -knn: Subsystem: VMware SVGA II Adapter [15ad:0405] lspci -knn: 00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01) lspci -knn: Subsystem: VMware Device [15ad:1976] lspci -knn: Kernel driver in use: mptspi lspci -knn: 00:11.0 PCI bridge [0604]: VMware PCI bridge [15ad:0790] (rev 02) lspci -knn: 00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:15.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:15.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:15.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:15.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:15.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:15.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:15.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) lspci -knn:
Processed: block 646130 with 696123
Processing commands for cont...@bugs.debian.org: block 646130 with 696123 Bug #646130 [parted] parted versions lags behind Bug #665465 [parted] Please upgrade parted to new upstream release 646130 was not blocked by any bugs. 646130 was not blocking any bugs. Added blocking bug(s) of 646130: 696123 665465 was not blocked by any bugs. 665465 was not blocking any bugs. Added blocking bug(s) of 665465: 696123 thanks Stopping processing here. Please contact me if you need assistance. -- 646130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646130 665465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13557033594471.transcr...@bugs.debian.org
Bug#696123: (no subject)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm confused. My understanding is that partman was already using external utilities for everything besides fat, hfs, and ext2 resize, and that there were already bug reports covering the lack of progress indication with those. Parted3 appears to have moved the resize functions for fat and hfs to a separate library, so partman should be able to just link to the new library and be no worse off than before, with the exception of ext2, and well, who really cares about that? What you describe here seems to be targeted at fixing the lack of progress indication already covered by other bugs. While providing progress indication is nice, I'm not sure why it is still blocking the migration to parted3. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQzoRfAAoJEJrBOlT6nu75mVgH/A6LQ34N3rAl2nCy1TH9dvB4 FWZiIhNcDriBkN2AFjfbTMs37P59N5Pf4xm+r3O9X4uwV7dr5nF7oyDx1DYIgOWB i08jyfm6HIsBnoOxCvDr/zVumFN3AEfJ3Od0AyDzufZJ+WIEsrFUOKHv1iUHgXem co1cGKfGgJiRd0ObbgSsm91VzXK3cimR7yL4AeXzqls7TwLJEx0YVpUw1bGv8Aaz iA0Az5xce+v0IjWBP60WNUSkL2F4GQXJCZvHeCVI7T/G+gtUk9OlXxyzFtQAVl8Q EpM2/JTXJZ/SzF7eMWVe0khVJURgDtn9p2sICzwSIXFMXgu45k/DUiudpkv5CHg= =yS46 -END PGP SIGNATURE- -- 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/50ce845f.7090...@ubuntu.com
Bug#696123: partman-base: need progress wrapper for non-libparted-based filesystem operations
On Mon, 2012-12-17 at 00:11 +, Colin Watson wrote: [...] Rather than the Sisyphean task of giving all the appropriate utilities machine-parseable progress interface, I instead suggest that we study the current progress interfaces and try to identify some common factors that can be parsed heuristically (e.g. solid bar of characters; \-/|-style spinner; percentage output), and write a wrapper utility that can translate some of the common ones into debconf progress output. [...] I have trouble believing that this is going to be easier than patching the most common utilities to add an option for a machine-readable progress indicator. Ben. -- Ben Hutchings Life is like a sewer: what you get out of it depends on what you put into it. signature.asc Description: This is a digitally signed message part
Bug#696123: partman-base: need progress wrapper for non-libparted-based filesystem operations
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have trouble believing that this is going to be easier than patching the most common utilities to add an option for a machine-readable progress indicator. Not too long ago I was looking at patching gparted to support this and while it did not seem difficult to process the output of the e2fsprogs utilities for the progress information, I was wondering why the various fs utilities don't already have a flag to generate machine readable output... and I think some of the utilities supported this, and some did not, even within e2fsprogs. IIRC, I found that at least some of them already have a flag to write output to a specified auxiliary fd to indicate progress, it just seemed that a standard needed decided on and implemented in all of them. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQzpAJAAoJEJrBOlT6nu75XrkH/RdWFitPR0tsOXWDv5rFtYuu mWSLXzcVT/meq8o/pfr0QthOjggeFNG5Bl1cKSQYEVs6kwLd37HP1CW93jSLqjHp 9t99OgIaE1xH320yp2fpX4/ScMl8eEcV8tOUzPlyth+RDMU0tI11lMOIKZb/eeha I74zQ3CkBY6tT026ZSodsaq1bua6dmY6lzgYvxIImXTYDY58OvjL5LbmM/l4urJS ZlVMTIxfE7FYX+YPKwYcqn1j5MirQlbniaFgY1Pi6eVv26KqghKuuZ5RH16Fuxdi qcMA52Xq5J3fZl5O0kMsZLBBvM3B3g1ORDypHc+gEwrrGPVPWjfOHj7BCSsnx/E= =VINZ -END PGP SIGNATURE- -- 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/50ce9009.4030...@ubuntu.com
Bug#696135: CD not detected on Dell Optiplex 755
Package: installation-reports Attempting to install wheezy i386 XFCE weekly build on Dell Optiplex 755 fails at Detect and mount CD-ROM with No common CD-ROM drive was detected. Most recent weekly build tried is 2012/11/12 (XFCE). The installer can successfully check the CD-ROM's integrity. System BIOS has been updated to latest (A19). A test install of squeeze (6.0.1a) is OK. Ubuntu 12.04 i386 installed OK too. Another Optiplex 755 is OK. Differences identified between these two machines include: FailOK BIOS VersionA19 A09 CDROM Model DS-8W1P TS-L633A Will test with a new Weekly image when it appears (right now, latest on cdimage.d.o is from 3 Dec). Thanks, Neale. -- 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/pine.lnx.4.05.11212171452070.3358-100...@marina.lowendale.com.au
