Processed: Re: dealing with old debian-installer bugs
Processing commands for cont...@bugs.debian.org: > reassign 655579 debian-installer Bug #655579 [rootskel-gtk] debian-installer: Unable to perform an installation : USB-input devices unusable Bug reassigned from package 'rootskel-gtk' to 'debian-installer'. Ignoring request to alter found versions of bug #655579 to the same values previously set Ignoring request to alter fixed versions of bug #655579 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 655579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.139358836211232.transcr...@bugs.debian.org
Bug#552700: marked as done (Add dfbinfo into libdirectfb-udeb)
Your message dated Fri, 28 Feb 2014 12:53:59 +0100 with message-id <20140228115359.ga6...@mraw.org> and subject line Re: Bug#552700: installation-report: dfbinfo has changed location & no longer available has caused the Debian Bug report #552700, regarding Add dfbinfo into libdirectfb-udeb 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.) -- 552700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-report Version: 2.38 The utility dfbinfo used to be included in the libdirectfb udeb in /usr/lib/libdirectfb-*/bin/. In Lenny the utility has been split out into a separate package libdirectfb-bin and moved to /usr/bin, and as a result of that is no longer included in the udeb. Possibly we should request dfbinfo to be included in the libdirectfb udeb again. In that case its path needs to be updated in report-hw. If we don't, it should probably just be removed from report-hw. --- End Message --- --- Begin Message --- Frans Pop (2009-10-28): > Package: installation-report > Version: 2.38 > > The utility dfbinfo used to be included in the libdirectfb udeb in > /usr/lib/libdirectfb-*/bin/. > In Lenny the utility has been split out into a separate package > libdirectfb-bin and moved to /usr/bin, and as a result of that is no > longer included in the udeb. > > Possibly we should request dfbinfo to be included in the libdirectfb udeb > again. In that case its path needs to be updated in report-hw. > If we don't, it should probably just be removed from report-hw. DirectFB is gone, so dfbinfo is no longer needed, closing. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Processed: Re: Bug#395040: Check that ywrap,mtrr options for the vesafb device on i386 are harmless
Processing control commands: > tag -1 pending Bug #395040 [rootskel-gtk] Check that ywrap,mtrr options for the vesafb device on i386 are harmless Added tag(s) pending. -- 395040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=395040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b395040.139359121229358.transcr...@bugs.debian.org
Bug#433073: marked as done (Please disable DirectFB's window backend buffer)
Your message dated Fri, 28 Feb 2014 13:45:56 +0100 with message-id <20140228124556.ga12...@mraw.org> and subject line Re: Bug#433073: Please disable DirectFB's window backend buffer has caused the Debian Bug report #433073, regarding Please disable DirectFB's window backend buffer 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.) -- 433073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: rootskel-gtk severity: wishlist tags: patch DirectFB allows to set [1] the way the desktop window buffering mechanism works by disabling the backend buffer. The result, in my experiments, was saving some some hundreds KB of memory with no noticeable drawbacks. I propose to apply the attached one-line patch and look for possible artifact which may appear on the display, and in the case reverse the patch. regards Attilio [1] http://www.directfb.org/docs/directfbrc.5.html Index: src/etc/directfbrc === --- src/etc/directfbrc (revisione 48095) +++ src/etc/directfbrc (copia locale) @@ -4,3 +4,4 @@ disable-module=keyboard disable-module=ps2mouse #disable-module=linux_input +desktop-buffer-mode=frontonly --- End Message --- --- Begin Message --- Attilio Fiandrotti (2007-07-14): > package: rootskel-gtk > severity: wishlist > tags: patch > > DirectFB allows to set [1] the way the desktop window buffering > mechanism works by disabling the backend buffer. > The result, in my experiments, was saving some some hundreds KB of > memory with no noticeable drawbacks. > I propose to apply the attached one-line patch and look for possible > artifact which may appear on the display, and in the case reverse > the patch. DirectFB is gone, so closing this bug report. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#395040: Check that ywrap,mtrr options for the vesafb device on i386 are harmless
Control: tag -1 pending Frans Pop (2006-11-23): > I have tested during one install that g-i works without these parameters. > However, the directfb README still says that they are needed: > http://www.directfb.org/index.php?path=Documentation%2FUser+Manuals%2FREADME > > Could you please check with upstream whether or not the parameters are > still needed or if the documentation is outdated? So we switched away from DirectFB a while ago; I've just removed that (that lives in src:debian-installer): http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=commitdiff;h=0917b2d There's plenty of time before jessie, and it can be reverted if people complain and we find out that's actually still needed. Mraw, KiBi. signature.asc Description: Digital signature
Bug#395257: marked as done ([g-i] keymap change works only once)
Your message dated Fri, 28 Feb 2014 13:54:41 +0100 with message-id <20140228125441.ga13...@mraw.org> and subject line Re: Bug#395257: Bug still here: cannot change keymap back in g-i has caused the Debian Bug report #395257, regarding [g-i] keymap change works only once 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.) -- 395257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=395257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cdebconf-gtk-udeb Severity: normal Keymap selection under g-i works once and if you try to change it it will not work; switching to text consle all changes have effect. I tried to select Italian keymap and everything looks ok; if I change the keymap to "American English" nothing changes; I switch to VT2 and it works as expected. regards, Davide signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Christian Perrier (2008-11-15): > Quoting Frans Pop (elen...@planet.nl): > > On Saturday 15 November 2008, Christian Perrier wrote: > > > This bug is still present in Lenny RC1 images > > > > I don't believe that is correct. Please provide details of how you tested > > and exactly what you observed. > > > - Boot g-i > - localechooser: Select French, France > - kbd-chooser: Select fr-latin9 keymap (Français) > - netcfg: type "azerty" (qwerty for users of non fr keyboards) > in the hostname field-->gives "azerty" > - Hit "Go back" > - kbd-chooser: change keymap to (États-Unis) > - netcfg: type qwerty: -->gives "azerty" I can't reproduce this. Also, at least since wheezy, the console keymap is sync'd with the one in X thanks to the setupcon call in /etc/profile so I think we're good now. Closing accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#695270: add support for disabling DPMS via preseeding
Cyril Brulebois (2014-02-14): > I've implemented support for dpms=false/dpms=true in rootskel-gtk: > > http://anonscm.debian.org/gitweb/?p=d-i/rootskel-gtk.git;a=commitdiff;h=ac4176a5a857b8f1ac7de82a479c7723908bea14 […] > It would probably be nice to check that this name doesn't conflict with > any kernel-side parameters, and whether that's an appropriate name at > all. No clash according to “git grep dpms -- Documentation” as of linux v3.14-rc4. Luca, Holger, Per, any comments on the naming of the option? Mraw, KiBi. signature.asc Description: Digital signature
Processing of grub-installer_1.93_multi.changes
grub-installer_1.93_multi.changes uploaded successfully to localhost along with the files: grub-installer_1.93.dsc grub-installer_1.93.tar.gz grub-installer_1.93_amd64.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjnor-0004wi...@franck.debian.org
Captive laptop
Hello, I have a persistent problem and I was hoping that the Debian install discs would solve it. I have a new laptop with Windows 8 on it (was purchased for the hardware) and Windows is holding it prisoner. I am unable to install any other Operating system on it whatsoever including Debian 7.4 that I downloaded from this site. It will not allow the 'test' with no files installed or the full installation. I am not exactly a computer newbie but have only 'new' level of linux background. I have tried six different OS packages from two or three different devices for installs and all have failed. Windows 8 will not let any install. Any chance you have an ISO that will produce a dvd disc that can be bootable from a bare harddrive. The 7.4 version I downloaded gets an 'invalid media' message and I have tried more than one copy/download/version with the same results. In the attempt to run from dvd without installing files, get a 'try compatibility settings' message that always fails. I am apparently not the only one with this problem. Please help. I NEED my computer without the Windows garbage taking control of it. I am even willing to pay for a 'guaranteed' installation disc but I try it before I pay as I feel Windows will defeat all comers at this point. Looking forward to being proved wrong! When I bought the laptop, I never dreamed that it would take months to attempt to get Windows off of it and still be failing. I feel like billing Microsoft for taking my laptop prisoner but that would get me as far as this installation is gettingnowhere. R. Edwards Desperate -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/592820025.971060.1393598499933.JavaMail.root@cds045
Bug#666974: marked as done (installs to /dev/sda when grub-installer/bootdev = /dev/sdb)
Your message dated Fri, 28 Feb 2014 15:19:53 + with message-id and subject line Bug#666974: fixed in grub-installer 1.93 has caused the Debian Bug report #666974, regarding installs to /dev/sda when grub-installer/bootdev = /dev/sdb 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.) -- 666974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: grub-installer Version: 1.60+squeeze3 Severity: important *** Please type your report below this line *** When I specify in my preseeding file: d-i partman-auto/disk string /dev/sdb d-i grub-installer/bootdev string /dev/sdb grub-installer ignores me and installs to /dev/sda. partman-auto does the right thing. In some cases this can result in an unbootable system. Attached is a syslog excerpt for the execution of grub-installer, with DEBCONF_DEBUG=5 set in the boot line. You can see that it reads in the right disk name from the preseeding file, but somewhere in the step_os_probe .. step_bootdev .. step_install_loader sequence it changes $bootdev to /dev/sda. I have also observed (on other installations, using software RAID-1) that d-i grub-installer/bootdev string /dev/sda /dev/sdb is read in but also ultimately ignored and grub-installer only installs to /dev/sda. This installation was on a machine with two hard disks of identical size, but only one was intended to be used in the installation. The partioning was one ext3 partition for /, and one LVM for everything else. No separate /boot partition. No software raid is specified. I was able to stop the installer at the end and ran grub-installer again on one of the installer consoles: sh -vx /usr/bin/grub-installer /target 1>/target/var/log/gi 2>&1 This shows the problem comes when parsing the grub-mkdevicemap output. + os-prober + db_settitle debian-installer/grub-installer/title + _db_cmd SETTITLE debian-installer/grub-installer/title + IFS= printf %s\n SETTITLE debian-installer/grub-installer/title + IFS= read -r _db_internal_line + RET=OK + return 0 + tmpfile=/tmp/menu.lst.extras + [ -s /tmp/os-probed ] + q=grub-installer/only_debian + state=1 + [ ] + chroot /target grub-mkdevicemap --no-floppy -m+ -head -n1 + cut -f2 + default_bootdev_os=/dev/disk/by-id/scsi-35000c50017a6040b + [ /dev/disk/by-id/scsi-35000c50017a6040b ] + chroot /target readlink -f /dev/disk/by-id/scsi-35000c50017a6040b + default_bootdev=/dev/sda when I run that grub-mkdevicemap on the host after installation, I get: # grub-mkdevicemap --no-floppy -m - (hd0) /dev/disk/by-id/scsi-35000c50017a6040b (hd1) /dev/disk/by-id/scsi-35000c50017a7843b so it seems that there is a disconnect here from the specification of $bootdev and the attempt to guess $default_bootdev_os. The consequences are as follows. A little further down the script there is this, er, dense if statement: case $ARCH:$grub_package in *:grub|*:grub-pc|sparc:grub-ieee1275) if [ "$(device_to_disk "$cdsrc")" = "$default_bootdev" ] || \ ([ -n "$hdsrc" ] && [ "$(device_to_disk "$hdsrc")" = "$default_bootdev" ]) || \ ([ "$default_bootdev" = '(hd0)' ] && \ (([ -n "$cdfs" ] && [ "$cdfs" != "iso9660" ]) || \ [ "$hybrid" = true ])) || \ ([ "$default_bootdev" != '(hd0)' ] && \ ! partmap "$default_bootdev" >/dev/null && \ ! grub_probe -t fs -d "$default_bootdev" >/dev/null); then db_fget grub-installer/bootdev seen if [ "$RET" != true ]; then bootfs=$(findfs /boot) [ "$bootfs" ] || bootfs="$(findfs /)" disk=$(device_to_disk "$bootfs") db_set grub-installer/bootdev "$disk" state=2 fi fi ;; ... This fails out at the "$default_bootdev" = '(hd0)' comparison. + device_to_disk + echo + sed s:\(/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|da\)[0-9]\+\|/dev/[a-z]\+\).*:\1: + [ = /dev/sda ] + [ -n ] + [ /dev/sda = (hd0) ] Then we come to step_bootdev, a loop that continues until we have a suitable value of $state. There $default_bootdev supercedes what I set $bootdev to. $state is already set to 1 and $q to grub-installer/only_debian (see above). db_progress STEP 1 db_progress INFO grub-installer/progress/step_bootdev while : ; do if [ "$state" = 1 ]; then db_input high $q || true if ! db_go; then
grub-installer_1.93_multi.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 28 Feb 2014 13:41:56 + Source: grub-installer Binary: grub-installer Architecture: amd64 source Version: 1.93 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Dimitri John Ledkov Closes: 666974 Launchpad-Bugs-Fixed: 1012629 Description: grub-installer - Install GRUB on a hard disk (udeb) Changes: grub-installer (1.93) unstable; urgency=medium . * Revert 1.92 changes, as unattended installations which do not preseed grub-installer/bootdev now fail to install unattended. This thus reopens #666974, LP#1012629. * Instead check if grub-installer/bootdev was seen, and only then query for it's value. Also do so, ahead of the loop that processes only_debian and with_other_os, such that grub-installer/bootdev takes precedence. Closes: #666974. LP: #1012629. * Jenkins which regressed with previous upload, are now back to normal. Checksums-Sha1: 77b77abdc2f23442ea248ac4c1adc4456b043d62 1838 grub-installer_1.93.dsc 28fdfa3043d7513315a801f2469874792a411f7c 227810 grub-installer_1.93.tar.gz 52bce3c6e9dcaffb7a7b4c3b31e58e85ac6d1cf2 260798 grub-installer_1.93_amd64.udeb Checksums-Sha256: 5a3253adea15ccc9f226ebaf035971c71abd7501c43ef7049dca9ae76fdd5481 1838 grub-installer_1.93.dsc 62956e4a1b4fcf2d0d86bd6b585355cacca7fd5b3146c4fb597294e0acf9e7df 227810 grub-installer_1.93.tar.gz 75ee19b3502ce969c7dc5acc696462e2759350e01ace0a1aac803c7ed065c497 260798 grub-installer_1.93_amd64.udeb Files: d778b77c3180f6adbd37e3f04c03b33c 1838 debian-installer standard grub-installer_1.93.dsc 0b4996e9ab85b0388407fafde63b6353 227810 debian-installer standard grub-installer_1.93.tar.gz 482c7f38d0e20cf37218a900028d0a0b 260798 debian-installer standard grub-installer_1.93_amd64.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJTEJKmAAoJEIh7YGGLPBauj8cP/j2JA2ux+21PYdQP2+uFPnah jB84Z/Cs5L+UbubobMBA8ycSuhFoSvnME2TC8Jm8cP0jEkhi9y4s1lJJAwyoy/X7 BIUqoAqUVjUnlEwDJKrLzc5eSXhmA+nhI1MB+GBnNyx8xx3s4GDcaG5rxCbwEXOh AE1BIHx1U9jlRGDZHdq/PXZrS33facma6b9hQNqjkiD6gl8RpyONLjD2mdENFdc1 ea8uUlV1M6uMQml7xw8wfaim053e890kEHY2IHOnWtihv6cRA/RCa5+sUdwJ9sBU aX9RSvRgkGz0BFi4w7UDTtdxyBP+nLBLUBEKOvqhOODxK/qyZmTgjxDvuxXHPU0a V9Yf61QZWTDkRCjqj4TgksB/zaNa87ynJx2bVpmgquSfjq1VW04mAU3cX9bCm0aX WvRjUlpHjA1Hm1ylRe/nP1Lcvjvo5GGxPoloOOCLdnPw2QQxJfxbh/LmDzZfEC+x pgsmuBHUlE13k7UgwzBeIabEb2e1krmftbXur8lmNAOMF4BNnznmTJ/loZM7w0/9 dZKv+yrAZsNBCbyubKrOwDxHcFuktE728KjY5qjoF/9KtvH4Fpd4rAwc7nKcIxvm aiSIp5vQaAlZjdm++OdWDOM+VC8dbrcURZkqRXYFq6awwh+4sGeOSVjiMW19kR4p uZ2wMRPyjOlvZAYTZHBo =c/3g -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjpe9-0006ep...@franck.debian.org
Re: Captive laptop
On Fri, Feb 28, 2014 at 07:41:39AM -0700, R Edwards wrote: > Hello, > I have a persistent problem and I was hoping that the Debian install discs > would solve it. I have a new laptop with Windows 8 on it (was purchased for > the hardware) and Windows is holding it prisoner. I am unable to install any > other Operating system on it whatsoever including Debian 7.4 that I > downloaded from this site. It will not allow the 'test' with no files > installed or the full installation. I am not exactly a computer newbie but > have only 'new' level of linux background. I have tried six different OS > packages from two or three different devices for installs and all have > failed. Windows 8 will not let any install. Any chance you have an ISO that > will produce a dvd disc that can be bootable from a bare harddrive. The 7.4 > version I downloaded gets an 'invalid media' message and I have tried more > than one copy/download/version with the same results. In the attempt to run > from dvd without installing files, get a 'try compatibility settings' message > that always fails. I am apparently not the only one with this problem. > Please help. I NEED my computer without the Windows garbage taking control > of it. I am even willing to pay for a 'guaranteed' installation disc but I > try it before I pay as I feel Windows will defeat all comers at this point. > Looking forward to being proved wrong! When I bought the laptop, I never > dreamed that it would take months to attempt to get Windows off of it and > still be failing. I feel like billing Microsoft for taking my laptop > prisoner but that would get me as far as this installation is > gettingnowhere. If you download the installer (say DVD-1 iso or netinstall iso) and then burn it as an image to the DVD: http://windows.microsoft.com/en-ca/windows7/burn-a-cd-or-dvd-from-an-iso-file So windows can do that apparently. It should then be bootable, but of course you have to tell the BIOS/EFI/whatever you have, to boot from the DVD drive. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140228155022.gq17...@csclub.uwaterloo.ca
Re: Captive laptop
On Feb 28, 2014 7:59 AM, "Lennart Sorensen" wrote: > > On Fri, Feb 28, 2014 at 07:41:39AM -0700, R Edwards wrote: > > Hello, > > I have a persistent problem and I was hoping that the Debian install discs would solve it. I have a new laptop with Windows 8 on it (was purchased for the hardware) and Windows is holding it prisoner. I am unable to install any other Operating system on it whatsoever including Debian 7.4 that I downloaded from this site. It will not allow the 'test' with no files installed or the full installation. I am not exactly a computer newbie but have only 'new' level of linux background. I have tried six different OS packages from two or three different devices for installs and all have failed. Windows 8 will not let any install. Any chance you have an ISO that will produce a dvd disc that can be bootable from a bare harddrive. The 7.4 version I downloaded gets an 'invalid media' message and I have tried more than one copy/download/version with the same results. In the attempt to run from dvd without installing files, get a 'try compatibility settings' message that always fails. I am apparently not the only one with this problem. Please help. I NEED my computer without the Windows garbage taking control of it. I am even willing to pay for a 'guaranteed' installation disc but I try it before I pay as I feel Windows will defeat all comers at this point. Looking forward to being proved wrong! When I bought the laptop, I never dreamed that it would take months to attempt to get Windows off of it and still be failing. I feel like billing Microsoft for taking my laptop prisoner but that would get me as far as this installation is gettingnowhere. > > If you download the installer (say DVD-1 iso or netinstall iso) and then > burn it as an image to the DVD: > > http://windows.microsoft.com/en-ca/windows7/burn-a-cd-or-dvd-from-an-iso-file > > So windows can do that apparently. > > It should then be bootable, but of course you have to tell the > BIOS/EFI/whatever you have, to boot from the DVD drive. You may also have to disable secure boot. > > -- > Len Sorensen > > > -- > To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: https://lists.debian.org/20140228155022.gq17...@csclub.uwaterloo.ca >
Bug#696969: rootskel-gtk: Improve theme=dark, especially the banner
Control: severity -1 important Control: clone -1 -2 Control: reassign -2 cdebconf-gtk 0.182 Control: retitle -2 cdebconf-gtk: Support loading an alternative banner for theme=dark Cyril Brulebois (2013-01-28): > Thanks! Looks good, will try and see how to integrate that post-rc1, > will keep you posted about the progress once it's committed. So, it took a year, but here it comes. I've merged your banner locally and I've modified rootskel-gtk to ship it. I also have a patch for cdebconf so that it detects the dark theme and loads this alternate banner, falling back to the regular one in case it is not found (which could happen with the new cdebconf-gtk and the old rootskel-gtk). Needs a bit of clean-up, but that works. The commands above should do the cloning job. I might try and get that pushed into stable, since shipping an extra image should be pretty much harmless, and since code changes are more or less minimal. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#696969: rootskel-gtk: Improve theme=dark, especially the banner
Processing control commands: > severity -1 important Bug #696969 [rootskel-gtk] rootskel-gtk: Improve theme=dark, especially the banner Severity set to 'important' from 'normal' > clone -1 -2 Bug #696969 [rootskel-gtk] rootskel-gtk: Improve theme=dark, especially the banner Bug 696969 cloned as bug 740358 > reassign -2 cdebconf-gtk 0.182 Bug #740358 [rootskel-gtk] rootskel-gtk: Improve theme=dark, especially the banner Bug reassigned from package 'rootskel-gtk' to 'cdebconf-gtk'. No longer marked as found in versions rootskel-gtk/1.26. Ignoring request to alter fixed versions of bug #740358 to the same values previously set Bug #740358 [cdebconf-gtk] rootskel-gtk: Improve theme=dark, especially the banner Marked as found in versions cdebconf/0.182. > retitle -2 cdebconf-gtk: Support loading an alternative banner for theme=dark Bug #740358 [cdebconf-gtk] rootskel-gtk: Improve theme=dark, especially the banner Changed Bug title to 'cdebconf-gtk: Support loading an alternative banner for theme=dark' from 'rootskel-gtk: Improve theme=dark, especially the banner' -- 696969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696969 740358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b696969.139360443319586.transcr...@bugs.debian.org
Processed: tagging 696969
Processing commands for cont...@bugs.debian.org: > tags 696969 + patch pending Bug #696969 [rootskel-gtk] rootskel-gtk: Improve theme=dark, especially the banner Added tag(s) pending and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 696969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.139360487622610.transcr...@bugs.debian.org
Bug#740358: cdebconf-gtk: Support loading an alternative banner for theme=dark
Control: tag -1 patch pending Cyril Brulebois (2014-02-28): > I also have a patch for cdebconf so that it detects the dark theme and > loads this alternate banner, falling back to the regular one in case it > is not found (which could happen with the new cdebconf-gtk and the old > rootskel-gtk). Needs a bit of clean-up, but that works. Here it is: http://anonscm.debian.org/gitweb/?p=d-i/cdebconf.git;a=commitdiff;h=a209703 I don't talk gtk fluently, so there might be a better way to implement it, but that seems to work just fine (with an old rootskel-gtk or with a patched one, with or without theme=dark). (I'm not sure why the debug message is emitted twice on vt1, but not scary enough for me to lose sleep over it.) Mraw, KiBi. signature.asc Description: Digital signature
Processed: Bug#740358: cdebconf-gtk: Support loading an alternative banner for theme=dark
Processing control commands: > tag -1 patch pending Bug #740358 [cdebconf-gtk] cdebconf-gtk: Support loading an alternative banner for theme=dark Added tag(s) pending and patch. -- 740358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b740358.139360966423077.transcr...@bugs.debian.org
Processing of cdebconf_0.188_amd64.changes
cdebconf_0.188_amd64.changes uploaded successfully to localhost along with the files: cdebconf_0.188.dsc cdebconf_0.188.tar.xz cdebconf-priority_0.188_all.udeb cdebconf_0.188_amd64.deb cdebconf-gtk_0.188_amd64.deb libdebconfclient0_0.188_amd64.deb libdebconfclient0-dev_0.188_amd64.deb cdebconf-udeb_0.188_amd64.udeb libdebconfclient0-udeb_0.188_amd64.udeb cdebconf-text-udeb_0.188_amd64.udeb cdebconf-newt-udeb_0.188_amd64.udeb cdebconf-gtk-udeb_0.188_amd64.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjskl-0008bk...@franck.debian.org
cdebconf_0.188_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 28 Feb 2014 21:49:31 +0300 Source: cdebconf Binary: cdebconf cdebconf-gtk libdebconfclient0 libdebconfclient0-dev cdebconf-udeb cdebconf-priority libdebconfclient0-udeb cdebconf-text-udeb cdebconf-slang-udeb cdebconf-newt-udeb cdebconf-gtk-udeb Architecture: source all amd64 Version: 0.188 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Description: cdebconf - Debian Configuration Management System (C-implementation) cdebconf-gtk - Gtk+ frontend for Debian Configuration Management System cdebconf-gtk-udeb - Gtk+ frontend for Debian Configuration Management System (udeb) cdebconf-newt-udeb - Newt frontend for Debian Configuration Management System (udeb) cdebconf-priority - Change debconf priority (udeb) cdebconf-slang-udeb - S-Lang frontend for Debian Configuration Management System (udeb) cdebconf-text-udeb - Plain text frontend for Debian Configuration Management System (udeb) cdebconf-udeb - Debian Configuration Management System (C-implementation) (udeb) libdebconfclient0 - Debian Configuration Management System (C-implementation library) libdebconfclient0-dev - Development files for cdebconf libdebconfclient0-udeb - Debian Configuration Management System (C-implementation) (udeb) Closes: 740358 Changes: cdebconf (0.188) unstable; urgency=medium . [ Samuel Thibault ] * Re-introduce -lpthread for being able to load gtk dynamically on hurd-any. . [ Cyril Brulebois ] * Add support for loading an alternate banner when the GTK theme name is "dark" (Closes: #740358). Fall back to the regular one if it's not available (See: #696969). * Adjust clean to remove all Makefile files generated from Makefile.in (3 out of 7 weren't cleaned yet). Checksums-Sha1: 5f9a19c316e132e83b02682c11b79558514aa4de 2569 cdebconf_0.188.dsc b574aa1e76bf0ce86f2ac37f92a3edfe09b57e72 265360 cdebconf_0.188.tar.xz 9c6115ad2c8e57e36e3eadafc53083ff4dd24c78 3344 cdebconf-priority_0.188_all.udeb 6c89c13df4279ae59a54fb524a9b284bdaf41412 173448 cdebconf_0.188_amd64.deb b1bfdc633be9cf6e187b916b7f340067dcc3f52a 70624 cdebconf-gtk_0.188_amd64.deb 4e7449722f3e5a1f63fb476ca5e4d21fb99fa4ae 46076 libdebconfclient0_0.188_amd64.deb ca64ca983aadcfb49b3873f356c3e41dfde3d5dc 50606 libdebconfclient0-dev_0.188_amd64.deb b26974045247365c2aa1d23fad6bc56d6ae862b9 82008 cdebconf-udeb_0.188_amd64.udeb 2780a0fd0ac869447d226a4c2c224b1d6e067c9e 3158 libdebconfclient0-udeb_0.188_amd64.udeb 4388303a1c5c283028c89e56fd4a7e88c0c1fa08 24542 cdebconf-text-udeb_0.188_amd64.udeb b9a3fdec2d26337ae140d48cb24f55b9db9974b9 20444 cdebconf-newt-udeb_0.188_amd64.udeb d9a9c1d4cc5f9c5d50cb75e2ba3f5afd92a7947f 28602 cdebconf-gtk-udeb_0.188_amd64.udeb Checksums-Sha256: af6fe2528b749e63a0ce4b0e5acb326eed371b03087a3a61d6525d7ee9a572da 2569 cdebconf_0.188.dsc 95d7d65b26febbe1e1bd302facc489b9d9243ddcde84e78ce24bfb6e4341f25d 265360 cdebconf_0.188.tar.xz 14f1e011f425cf93dea5cf91b4ede5de2a1b51f336304dbef3cbb01fd98c8e55 3344 cdebconf-priority_0.188_all.udeb fb9b9687fca5d44f65346dffc1c102cb2d61810765f1ee2b8d81b4688349aad2 173448 cdebconf_0.188_amd64.deb b9e17e0e8143a80575ee1218588e3d33accc960ce8a420e120886eb4573f2cc9 70624 cdebconf-gtk_0.188_amd64.deb 18748e0c39b93c94bcd2bd7cac836c35d0fc1eb3641e5c6b3f4149e980fb6718 46076 libdebconfclient0_0.188_amd64.deb ba7780f001211f4847a7667769e47b2774cdd1c91d4d76f5010f43863a61509e 50606 libdebconfclient0-dev_0.188_amd64.deb 0644e674070399b68c31e39388cab9387aa08f910847f108605f9e49d34c729d 82008 cdebconf-udeb_0.188_amd64.udeb 6d545248518a59646d419122194388c1ac2949360f61c2b2ea43d0b0b6cb0214 3158 libdebconfclient0-udeb_0.188_amd64.udeb 2bdaed4f7008497a5742bf5fa918538d0f7ac6ea8fec3a8d825f60d6152c0333 24542 cdebconf-text-udeb_0.188_amd64.udeb 304111cf2fcc6d812b49938d116ad3f430a2894e47b634e57eaf12e44eb1196b 20444 cdebconf-newt-udeb_0.188_amd64.udeb 214145e1e25ae1c7516b7d415be2fd494b0885f249c44937ae58f7460a292d57 28602 cdebconf-gtk-udeb_0.188_amd64.udeb Files: 1a75e3df64718d52906953e554db1db3 2569 utils optional cdebconf_0.188.dsc d182ed904c5436f8654eb5dcdd9fa567 265360 utils optional cdebconf_0.188.tar.xz f3e5f8f085e5ee03541e0ad5f6e8b36b 3344 debian-installer standard cdebconf-priority_0.188_all.udeb 6d30cb3ed39fd97a4ee722a3f691fa20 173448 utils extra cdebconf_0.188_amd64.deb 13913e8e23483e1c6aaf0367ba2ee659 70624 admin extra cdebconf-gtk_0.188_amd64.deb 597fd5945919f08e3952b0336d3085f0 46076 libs optional libdebconfclient0_0.188_amd64.deb acbaca00a348dc49fa280dfa5c0d5389 50606 libdevel optional libdebconfclient0-dev_0.188_amd64.deb cc344da9aa8cd0511a69ff2973e8ad3e 82008 debian-installer standard cdebconf-udeb_0.188_amd64.udeb fbc1293eff0155b382968fe70307bb5e 3158 debian-installer optional libdebconfclient0-udeb_0.188_amd64.udeb 57ed65e84686629dc63a818576e0517f 24542 debian-installer optional cdebconf-text-u
Bug#401681: marked as done (DirectFB should always use the vesa fb device on i386)
Your message dated Fri, 28 Feb 2014 20:47:10 +0100 with message-id <20140228194710.ga28...@mraw.org> and subject line Re: Bug#400898: More informations needed to fix this bug has caused the Debian Bug report #400898, regarding DirectFB should always use the vesa fb device on i386 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.) -- 400898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: rotskel-gtk severity: normal tags: patch At boot time, on i386, "video=vesa" is passed to the kernel to start the framebuffer device /dev/fb0 via vesafb driver (built into the kernel). Later in the boot process, the vga16fb module is loaded, and a second framebuffer device, /dev/fb1 is created, but sometimes, why i don't know, the fb devices minor numbers end up swapped. By default DirectFB accesses the first available fb device (/dev/fb0) and as 4 bit modes provided by vga16 are not supported, it fails initializing. The attached patch takes care of adding to DirectFB configuration file (/etc/directfbrc) a line indicating what fb device has to be used (the one provided by vesafb). A miniiso [1] including this patch is available for testing. Attilio Fiandrotti [1] https://debian.polito.it/downloads/mini_vesafbonly.iso Index: src/lib/debian-installer.d/S61choose-fb-device-x86 === --- src/lib/debian-installer.d/S61choose-fb-device-x86 (revisione 0) +++ src/lib/debian-installer.d/S61choose-fb-device-x86 (revisione 0) @@ -0,0 +1,7 @@ +#This script takes care of making DirectFB use the vesa fb device, as other +#fb devices may exist + +if [ "$DEBIAN_FRONTEND" = gtk ] ; then + FB_INDEX=$(grep -i vesa /proc/fb | cut -d " " -f 1 ) + echo "fbdev=/dev/fb"$FB_INDEX >> /etc/directfbrc +fi Index: src/lib/debian-installer.d/Makefile === --- src/lib/debian-installer.d/Makefile (revisione 43160) +++ src/lib/debian-installer.d/Makefile (copia locale) @@ -20,7 +20,8 @@ ifneq (,$(filter i386 amd64,$(DEB_HOST_ARCH_CPU))) files += \ - S61mouse-support-x86 + S61mouse-support-x86\ + S61choose-fb-device-x86 endif ifneq (,$(filter powerpc,$(DEB_HOST_ARCH_CPU))) files += \ --- End Message --- --- Begin Message --- Attilio Fiandrotti (2006-12-10): > It looks like vesafb was unable to start on your Geforce, hence no > /dev/fb0 was provided: we aready experience that for Inlel 82810 and > S3ViRGE DX. > Another user reported fb0 (vesa) and fb1 (vga 16 colours) being > swapped on a grforce go 6200, but he was later unable to reroduce > the swap. > I prepared a patch that disables the graphical frontend in the case > vesafb cannot be started at boot time and this iso [1] includes the > patch. > The patch should detect lack of vesafb fb device and falback to the > classical textual installer, could you please test and report > whether it works or not? We haven't heard back from the submitter in a very long while, the kernel development pace is very high, so I'm going to assume this bug hasn't bitten anyone in a while. Closing accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#400898: marked as done (Pixelformat rgba 6/0, 6/0, 6/0, 0/0 not supported by DirectFB)
Your message dated Fri, 28 Feb 2014 20:47:10 +0100 with message-id <20140228194710.ga28...@mraw.org> and subject line Re: Bug#400898: More informations needed to fix this bug has caused the Debian Bug report #400898, regarding Pixelformat rgba 6/0, 6/0, 6/0, 0/0 not supported by DirectFB 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.) -- 400898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: hd_image with kernel-options installgui root=/dev/ram0 ramdisk_size=12000 Image version: http://cdimage.debian.org/cdimage/etch_di_rc1/i386/iso-cd/debian-testing-i386-netinst.iso http://http.at.debian.org/debian/dists/etch/main/installer-i386/current//images/hd-media/gtk/vmlinuz Date: 29. nov 2006 / 12:46 Machine: aopen barebook 1559as Processor: centrino Intel(R) Pentium(R) M processor 1.73GHz Memory: 1G Partitions: /dev/sda1 ext3 6728280 5288844 1097656 83% / tmpfstmpfs 517808 0517808 0% /lib/init/rw udev tmpfs 1024052 10188 1% /dev tmpfstmpfs 540672 0540672 0% /dev/shm /dev/sda6 ext367519860 48521404 15568584 76% /home none tmpfs 540672 0540672 0% /dev/shm Output of lspci -nn (lspci -vnn atteched): 00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03) 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port [8086:2591] (rev 03) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 04) 00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 04) 00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 04) 00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 04) 00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 04) 00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 04) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d4) 00:1e.2 Multimedia audio controller [0401]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller [8086:266e] (rev 04) 00:1e.3 Modem [0703]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller [8086:266d] (rev 04) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge [8086:2641] (rev 04) 00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA Controller [8086:2653] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller [8086:266a] (rev 04) 01:00.0 VGA compatible controller [0300]: nVidia Corporation NV43 [GeForce Go 6600] [10de:0148] (rev a2) 03:05.0 Ethernet controller [0200]: Atheros Communications, Inc. AR5212 802.11abg NIC [168c:0013] (rev 01) 03:07.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] (rev 10) 03:09.0 CardBus bridge [0607]: Texas Instruments PCIxx21/x515 Cardbus Controller [104c:8031] 03:09.2 FireWire (IEEE 1394) [0c00]: Texas Instruments OHCI Compliant IEEE 1394 Host Controller [104c:8032] 03:09.3 Mass storage controller [0180]: Texas Instruments PCIxx21 Integrated FlashMedia Controller [104c:8033] 03:09.4 Generic system peripheral [0805]: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller [104c:8034] Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] 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: i tried the graphical installer after the console started fine, and there seems to be a problem with my graphic card, as the DirectFB couldn't start. i have a internal display with 1400x1050 and the nvidia geforce go 6600 (nv43), with the current k
Bug#369312: marked as done (miBoot enable floppies don't eject; must use a paperclip)
Your message dated Fri, 28 Feb 2014 20:54:23 +0100 with message-id <20140228195423.ga29...@mraw.org> and subject line Re: Bug#369312: miBoot enable floppies don't eject; must use a paperclip has caused the Debian Bug report #369312, regarding miBoot enable floppies don't eject; must use a paperclip 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.) -- 369312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: normal On Macs floppy drives don't come with a manual eject button; you are expected to eject floppies through software. This is a problem for floppy installs of debian because the boot floppy is not ejected to permit the insertion of the root floppy, nor is the root floppy ejected to allow insertion of a driver floppy. Floppies can be ejected manually but it takes a straightened paperclip inserted into a pinhole on the front of the floppy, which is less than ideal. I plan to work on this soon. -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore --- End Message --- --- Begin Message --- Daniel Dickinson (2006-05-28): > Package: debian-installer > Severity: normal > > On Macs floppy drives don't come with a manual eject button; you are > expected to eject floppies through software. This is a problem for > floppy installs of debian because the boot floppy is not ejected to > permit the insertion of the root floppy, nor is the root floppy ejected > to allow insertion of a driver floppy. Floppies can be ejected > manually but it takes a straightened paperclip inserted into a pinhole > on the front of the floppy, which is less than ideal. Boot floppies are gone, so closing. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#290366: marked as done (bootloader doesn't set VESA mode on x86, so vesafb is never loaded)
Your message dated Fri, 28 Feb 2014 20:52:45 +0100 with message-id <20140228195245.ga29...@mraw.org> and subject line Re: Bug#290366: Should this bug be closed ?? has caused the Debian Bug report #290366, regarding bootloader doesn't set VESA mode on x86, so vesafb is never loaded 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.) -- 290366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=290366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: normal For vesafb to work, the kernel bootloader needs to set up a VESA mode. This is typically done by passing something like vga=0x301 (which will set a 256 colour 640x480 display). If this succeeds, vesafb should load and work correctly. Otherwise, the system will fall back to vga16fb when the vesafb modprobe fails. Currently, vga16fb is loaded unconditionally. I have a machine here that works correctly with vesafb but fails with vga16fb. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (600, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) --- End Message --- --- Begin Message --- Frans Pop (2006-11-14): > On Monday 13 November 2006 16:09, Attilio Fiandrotti wrote: > > I accidentally ran into this bug. > > We currently set the vesafb fbdev in 800x600@75 in images containing > > the GTK frontend at least: should this bug be closed? > > IMO not as the BR is not about the graphical installer, but about display > problems using the newt frontend. src:debian-installer has: | commit 63d9d35e4d0306ca3c1ae2b4848140782342a2d1 | Author: Frans Pop | Date: Sat Oct 10 12:01:55 2009 + | | Change default video mode for i386/amd64 to vga=788 for the "newt" frontend so closing this bug report. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#408588: marked as done (Debian on SGI Altix IA-64 (follow-up))
Your message dated Fri, 28 Feb 2014 21:02:01 +0100
with message-id <20140228200201.ga29...@mraw.org>
and subject line Re: Bug#408588: Debian on SGI Altix IA-64 (follow-up)
has caused the Debian Bug report #408588,
regarding Debian on SGI Altix IA-64 (follow-up)
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.)
--
408588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rootskel
Reply below..
Stéphane Larose wrote:
> Hi,
>
> At the end of December, I posted on this list about booting and running
> Debian
> etch on SGI Altix 350. There was basically 3 things to modify on the netinst
> cd to make it boot and install:
> - putting 'relocatable' in elilo.conf (done - thanks to Dann Frazier)
> - adding some modules to the d-i kernel (done - thanks to Dann Frazier)
> - modifying something with the console device since we lose the console
> output
> when booting the cd (just when init - or busybox init starts)
>
> The trick I found to get the console output after init starts was to comment
> out this line:
> makedev 600 /dev/tts/"$i" c 4 "$(($i + 64))"
> in /lib/debian-installer/init-udev-devices. I've done some research to know
> exactly why this make the console output work.
>
> In kernel > 2.6.7, there is a new serial console driver for the Altix L1
> (CONFIG_SERIAL_SGI_L1_CONSOLE=y) and the device is /dev/ttySG0. I think this
> device gets associated with /dev/console in the d-i because, if I
> create it (just before busybox init starts):
> mknod ttySG0 c 204 40
> and
> echo "something" > /dev/ttySG0 or
> echo "something" > /dev/console
> both will echo.
>
> Then I looked at how busybox init was choosing the console and found out that
> this part of code is being executed:
> ... (from busybox init.c source)
> if (ioctl(0, TIOCGSERIAL, &sr) == 0) {
> /* this is a serial console */
> snprintf(console, sizeof(console) - 1, SC_FORMAT, sr.line);
> ...
> while ((fd = open(console, O_RDONLY | O_NONBLOCK)) < 0 && tried < 2) {
>/* Can't open selected console -- try
> logical system console and VT_MASTER */
> safe_strncpy(console, (tried == 0 ? _PATH_CONSOLE : CURRENT_VC),
> sizeof(console));
> ...
>
> So sr.line is set to 0 which seems correct but the SC_FORMAT variable
> is '/dev/tts/' (hard-coded) resulting in console=/dev/tts/0 instead
> of /dev/ttySG0.
>
> On the d-i CD, /dev/tts/0 is created by
> the /lib/debian-installer/init-udev-devices script, so busybox will try to
> open it and will succeed but this device is not the correct one on the Altix
> so no more console output after busybox init.
>
> If I delete /dev/tts/0 (or comment out the line to create this device in the
> init-udev-devices script), the 'open' call of busybox will fail so busybox
> will retry with console=_PATH_CONSOLE (which is defined as /dev/console) and
> this will work since we effectively are on /dev/console (/dev/ttySG0) during
> the Debian installation on Altix.
>
> That is what I think creates the problem with console output when installing
> on Altix. I don't know what is the best solution to correct this but maybe:
> 1- patching busybox so that SC_FORMAT would be /dev/ttySG on Altix (if kernel
> > 2.6.7)
> 2- creating the /dev/ttySG0 device in the init-udev-devices script
I don't know how doable #1 is (would need some way for busybox to detect
this machine), so I'm focusing on #2.
However, I'm not sure why creating the /dev/ttySG0 device would work.
From your description it sounds like busybox init would still try to use
the hardcoded /dev/tts/0 device instead.
Seems like we could fix it by making init-udev-devices skip creation of
/dev/tts/0, if running on the altix. What would be a good way to detect
that machine?
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Joey Hess (2007-01-26):
> I don't know how doable #1 is (would need some way for busybox to detect
> this machine), so I'm focusing on #2.
>
> However, I'm not sure why creating the /dev/ttySG0 device would work.
> From your description it sounds like busybox init would still try to use
> the hardcoded /dev/tts/0 device instead.
>
> Seems like we could fix it by making init-udev-devices skip creation of
> /dev/tts/0, if running on the altix. What would be a good way to detect
> that machine?
So, ia64 is no longer supported[1]; the kernel, udev, and busybox had a lot
of changes, which might have fixed this issue, so I'm not sure there's
anything I can do about this parti
Bug#492077: marked as done ([optimization] d-i: avoid searching for libgcc_s.so)
Your message dated Fri, 28 Feb 2014 21:06:11 +0100
with message-id <20140228200611.ga30...@mraw.org>
and subject line Re: Bug#492077: debian-installer: avoid searching for
libgcc_s.so
has caused the Debian Bug report #492077,
regarding [optimization] d-i: avoid searching for libgcc_s.so
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.)
--
492077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: debian-installer: avoid searching for libgcc_s.so
Package: debian-installer
Version:
Severity: wishlist
*** Please type your report below this line ***
Many executables used by the installer depend on libgcc_s.so. Searching for
this library (by ld-linux.so just after execve) takes more than 1% of install
time. The search tries:
2375 open("/lib/tls/libgcc_s.so.1", O_RDONLY) = -1 ENOENT
2373 open("/lib/fast-mult/libgcc_s.so.1", O_RDONLY) = -1 ENOENT
2372 open("/lib/v5l/libgcc_s.so.1", O_RDONLY) = -1 ENOENT
2372 open("/lib/v5l/fast-mult/libgcc_s.so.1", O_RDONLY) = -1 ENOENT
2356 open("/lib/tls/v5l/fast-mult/libgcc_s.so.1", O_RDONLY) = -1 ENOENT
2355 open("/lib/tls/fast-mult/libgcc_s.so.1", O_RDONLY) = -1 ENOENT
2351 open("/lib/tls/v5l/libgcc_s.so.1", O_RDONLY) = -1 ENOENT
before finding it in /lib. [Those counts in the first column are for less than
1/3 of base install on a NSLU2 armel-eabi in low-memory mode.]
The search can be avoided, by forcing it to succeed on the first try:
export LD_LIBRARY_PATH=/lib
Please apply.
The users of libgcc_s.so include:
ash busybox cat chmod chown cp cttyhack dd df dmesg echo egrep false grep
gunzip gzip ip kill ln ls mkdir mknod more mount mv parted_server pidof ps pwd
rm rmdir sed sh sleep sync tar touch true umount uname zcat libblkid.so.1.0
libext2fs.so.2 libext2fs.so.2.4 libnewt.so.0.52
libparted-1.7.so.1 libparted-1.7.so.1.0.0 libslang.so.2 libuuid.so.1
libuuid.so.1.2
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: armel (armv5tel)
Kernel: Linux 2.6.25-2-ixp4xx
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
--
--- End Message ---
--- Begin Message ---
Control: tag -1 wontfix
Joey Hess (2008-07-24):
> So for a typical install on modern hardware, these 16 thousand extra
> syscalls use less than 0.1 second.
>
> I don't have my slug handy to try, but 1% of install time sounds very
> excessive even there.
>
> Also, when trying to optimise something, it's generally a good idea to
> find an optimiation target that yields significantly better than 1%
> improvement..
[…]
> IIRC the linker/glibc already has a bug open about its innefficient
> attempts to open libraries that arn't there. I don't think we should
> try to work around such a bug in the installer.
Agreed, so tagging accordingly and closing.
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
Bug#267227: marked as done (Minor efficiency improvement for scsi device search)
Your message dated Fri, 28 Feb 2014 21:11:48 +0100 with message-id <20140228201148.ga31...@mraw.org> and subject line Re: Bug#267227: Minor efficiency improvement for scsi device search has caused the Debian Bug report #267227, regarding Minor efficiency improvement for scsi device search 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.) -- 267227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=267227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rootskel Version: 0.79 Severity: wishlist Tags: patch Hi, When playing with bugreporter-udeb, I had a good look at init code in this package's src-bootfloppy directory. find /dev/scsi This list many useless entries. Assuming no one wish to use partition after part9, changing above with find /dev/scsi -name 'part?'||true may improve code. (Or I should say, I did so in bugreporter-udeb.) Does this make sense or it is bad idea. If bad tell me so. Then I will fix bugreporter-udeb patch too. Osamu --- init.org2004-08-21 11:08:22.0 +0200 +++ init2004-08-21 11:09:51.0 +0200 @@ -96,7 +96,7 @@ DEVS=/dev/floppy/? fi if [ -d /dev/scsi ]; then - DEVS="$DEVS `find /dev/scsi`" + DEVS="$DEVS `find /dev/scsi -name 'part?' || true`" fi else DEVS="`find $INSTALL_MEDIA_DEV`" --- End Message --- --- Begin Message --- Version: 1.40 Osamu Aoki (2004-08-21): > Package: rootskel > Version: 0.79 > Severity: wishlist > Tags: patch > > Hi, > > When playing with bugreporter-udeb, I had a good look at init code > in this package's src-bootfloppy directory. > > find /dev/scsi The relevant code was rewritten in the above-mentioned version, so closing this bug report accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#287412: Bug#287344: rc2 netinst install on hp pavilion ze4900 laptop
Control: tag -1 patch
Joey Hess (2004-12-27):
> I was suprised to see that the acpi fan and thermal modules were not
> loaded on the installed system. This seems to be an oversight in
> rootskel, it loads the modules in the installer, but neglects to
> register-module them.
>
> If acpid had been installed, I think it would have taken care of
> loading all those modules. And it's needed for the gnome battery
> monitor anyway. We need a laptop task! However, I think that even with
> that, unconditionally register-moduleing fan and thermal is good from
> a belt and suspenders POV.
I know close to nothing about module (auto)loading and the like, but if
the attached patch can do no harm and can actually help, I'm happy to
push it. What do you think?
Mraw,
KiBi.
From 45fb2aaa5d4e449c89fd3fe61a2c568628c0ec57 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois
Date: Fri, 28 Feb 2014 23:26:24 +0300
Subject: [PATCH] register-module {acpi,thermal} in addition to modprobe
(Closes: #287412).
---
debian/changelog | 8
src/lib/debian-installer-startup.d/S05acpi-linux-x86 | 2 ++
2 files changed, 10 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index b067778..a336a06 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+rootskel (1.108) UNRELEASED; urgency=medium
+
+ * debian-installer-startup.d/S05acpi-linux-x86: In addition to calling
+modprobe {acpi,thermal}, register-module them so that the installed
+system is configured accordingly (Closes: #287412).
+
+ -- Cyril Brulebois Fri, 28 Feb 2014 23:23:53 +0300
+
rootskel (1.107) unstable; urgency=low
[ Martin Michlmayr ]
diff --git a/src/lib/debian-installer-startup.d/S05acpi-linux-x86 b/src/lib/debian-installer-startup.d/S05acpi-linux-x86
index 3300192..49392be 100644
--- a/src/lib/debian-installer-startup.d/S05acpi-linux-x86
+++ b/src/lib/debian-installer-startup.d/S05acpi-linux-x86
@@ -2,3 +2,5 @@
# overheating.
modprobe fan >/dev/null 2>&1 || true
modprobe thermal >/dev/null 2>&1 || true
+register-module fan
+register-module thermal
--
1.9.0
signature.asc
Description: Digital signature
Processed: Re: Bug#287344: rc2 netinst install on hp pavilion ze4900 laptop
Processing control commands: > tag -1 patch Bug #287412 [rootskel] should register-module the fan and thermal modules Added tag(s) patch. -- 287412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b287412.139361956930517.transcr...@bugs.debian.org
Re: [Pkg-zfsonlinux-devel] any news/reply regarding ZFS in NEW?
On 28/02/14 15:13, Turbo Fredriksson wrote: > It's very flattering that people thought my stuff was good enough to accept > without further review, > but it's also a bit frightening - I'm good, but not THAT good (as we could > see :). ISTR it was committed to master by mistake? Then reverted, but when Christian Perrier originally did this he rewrote git history; Joey Hess corrected that in the VCS, but Christian's next upload reintroduced it all from his working copy. Or something like that. The actually useful bits for Linux were later reverted by KiBi due to d-i build issues, but the other changes (including some that are problematic for kFreeBSD) are still there. Perhaps I could undo Turbo's changes in master, and we can later carefully review, clean up and reintroduce changes ZoL really needs? Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5310f6e7.4000...@pyro.eu.org
Bug#612281: marked as done (installation-reports: volatile reference instead of squeeze/updates in, installer)
Your message dated Fri, 28 Feb 2014 21:51:04 +0100 with message-id <20140228205104.ga3...@mraw.org> and subject line Re: Bug#492937: apt-setup: inconsistent path handling for 'security' and 'volatile' services has caused the Debian Bug report #492937, regarding installation-reports: volatile reference instead of squeeze/updates in, installer 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.) -- 492937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: minor -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/debian-cd/6.0.0/multi-arch/iso-cd/debian-6.0.0-amd64-i386-netinst.iso Date: 7th February 2011 Machine: HP DL380 G4 Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] -- with non-free firmware added to iso Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Simple base minimalistic installation with ssh server and standard only, as server, no desktop GUI installed. -- 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+b1" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux hp-dl380g4-a 2.6.32-5-amd64 #1 SMP Fri Dec 10 15:35:08 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation E7520 Memory Controller Hub [8086:3590] (rev 0c) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3200] lspci -knn: 00:02.0 PCI bridge [0604]: Intel Corporation E7525/E7520/E7320 PCI Express Port A [8086:3595] (rev 0c) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:06.0 PCI bridge [0604]: Intel Corporation E7520 PCI Express Port C [8086:3599] (rev 0c) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 [8086:24d2] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 [8086:24d4] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 [8086:24d7] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.3 USB Controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 [8086:24de] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller [8086:24dd] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev c2) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge [8086:24d0] (rev 02) lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller [8086:24db] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: ata_piix lspci -knn: 01:03.0 VGA compatible controller [0300]: ATI Technologies Inc Rage XL [1002:4752] (rev 27) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:00
Bug#492937: marked as done (apt-setup: inconsistent path handling for 'security' and 'volatile' services)
Your message dated Fri, 28 Feb 2014 21:51:04 +0100 with message-id <20140228205104.ga3...@mraw.org> and subject line Re: Bug#492937: apt-setup: inconsistent path handling for 'security' and 'volatile' services has caused the Debian Bug report #492937, regarding apt-setup: inconsistent path handling for 'security' and 'volatile' services 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.) -- 492937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: debian-installer severity: wishlist Hi, I was looking at packages/apt-setup/generators/and noticed a difference between the way that 91security and 92volatile add lines to the new sources.list file (subversion, r54582): 91security does this - echo "deb http://$host/ $codename/updates $dists" >> $file 92volatile does this - echo "deb http://$host/debian-volatile $codename/volatile $dists" >> $file I noticed this when I was trying to preseed these settings, but using a local apt-proxy machine instead of security.d.o and volatile.d.o. At present I can preseed the security source like this d-i apt-setup/security_host string aptproxy:/security and the "right thing" happens. But to get volatile right I would have to preseed differently d-i apt-setup/volatile_host string aptproxy: and use the path /debian-volatile on the apt-proxy. This would look a bit odd to an unitiated reader of the preseeding file. To me, the answer appears to allow additional variables apt-proxy/security_path apt-proxy/volatile_path and default these to '' and '/debian-volatile', respectively, so you can do e.g. echo "deb http://$host/$path $codename/volatile $dists" >> $file Then I could preseed the settings for my apt-proxy as well, in a nicer way. Does this seem sensible? This might also help #364650. Cheers Vince --- End Message --- --- Begin Message --- Vincent McIntyre (2008-07-30): > I was looking at packages/apt-setup/generators/and noticed a > difference between the way that 91security and 92volatile add > lines to the new sources.list file (subversion, r54582): > […] volatile.d.o is now gone and updates are available in the main archive (see generators/92updates). Closing this bug report accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#614862: marked as done (debian-installer: Still asks whether to enable volatile updates)
Your message dated Fri, 28 Feb 2014 21:51:04 +0100 with message-id <20140228205104.ga3...@mraw.org> and subject line Re: Bug#492937: apt-setup: inconsistent path handling for 'security' and 'volatile' services has caused the Debian Bug report #492937, regarding debian-installer: Still asks whether to enable volatile updates 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.) -- 492937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Version: 20110106 Severity: normal The volatile archive is discontinued in squeeze and replaced by the squeeze-updates suite[0] but debian-installer still asks whether you want to use it. [0] http://www.debian.org/News/2011/20110215 --- End Message --- --- Begin Message --- Vincent McIntyre (2008-07-30): > I was looking at packages/apt-setup/generators/and noticed a > difference between the way that 91security and 92volatile add > lines to the new sources.list file (subversion, r54582): > […] volatile.d.o is now gone and updates are available in the main archive (see generators/92updates). Closing this bug report accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#596716: marked as done (debian-installer: please add easy path to bpo and volatile sources)
Your message dated Fri, 28 Feb 2014 21:51:04 +0100 with message-id <20140228205104.ga3...@mraw.org> and subject line Re: Bug#492937: apt-setup: inconsistent path handling for 'security' and 'volatile' services has caused the Debian Bug report #492937, regarding debian-installer: please add easy path to bpo and volatile sources 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.) -- 492937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: wishlist Hello, Today I wanted to install Debian "lenny" on a recent new machine with is not supported by debian-installer kernel in "lenny". I also tried kmuto's d-i backport, but it is bit out of date. I believe it would not be hard to ask a new debconf question on whether you want to add bpo and/or volatile sources list for the installer to pick up new kernel and packages. Best regards, -- Hector Oron -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (700, 'unstable'), (600, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Vincent McIntyre (2008-07-30): > I was looking at packages/apt-setup/generators/and noticed a > difference between the way that 91security and 92volatile add > lines to the new sources.list file (subversion, r54582): > […] volatile.d.o is now gone and updates are available in the main archive (see generators/92updates). Closing this bug report accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Re: [Pkg-zfsonlinux-devel] any news/reply regarding ZFS in NEW?
Steven Chamberlain (2014-02-28): > The actually useful bits for Linux were later reverted by KiBi due to > d-i build issues, but the other changes (including some that are > problematic for kFreeBSD) are still there. > > Perhaps I could undo Turbo's changes in master, and we can later > carefully review, clean up and reintroduce changes ZoL really needs? That's what I suggested in the last paragraph of <20140203224646.gb5...@mraw.org>: https://lists.debian.org/debian-bsd/2014/02/msg00043.html Mraw, KiBi. signature.asc Description: Digital signature
Bug#364650: marked as done (Option to enter URL for security / optional apt-src lines)
Your message dated Fri, 28 Feb 2014 21:59:07 +0100 with message-id <20140228205907.ga4...@mraw.org> and subject line Bug#364650: Option to enter URL for security / optional apt-src lines has caused the Debian Bug report #364650, regarding Option to enter URL for security / optional apt-src lines 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.) -- 364650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: Daily netinst CD Image version: April 22 Date: April 24 Machine: Advantech PCA-6187 (i865G) Processor: P4 3.0GHz Memory: 512MB Partitions: 509M swap (pri), 8GB root (pri), 11GB data (log) Output of lspci and lspci -n: I can get this if anyone is interested. There were no problems with hardware detection. Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[E] Install boot loader:[O] Reboot: [O] Comments/Problems: I got the same error message reported here: http://lists.debian.org/debian-boot/2006/02/msg00693.html I was able to work around it in the same manner -- editing the base-installer.postinst file. I'll attach the gzipped syslog; grep for "no_codename". I have a few suggestions concerning the apt configuration: 1. If I choose to manually enter a Debian mirror URL, then please also prompt me to provide a URL for the security mirror. I'm firewalled and the only accessible mirror is my local apt-proxy server. Currently apt freezes for a long time trying to access security.debian.org directly, and I have to switch to console 2 and kill the http retrieval process. Then I have to edit sources.list later to correct the security entry. 2. The default sources.list doesn't include "contrib" or "non-free". In many cases I need these (mainly for nvidia drivers). It would be nice if the installer could write these into the sources.list file by default, or at least allow me to choose to do so. 3. Most end-user systems do not need "deb-src" lines in the sources.list -- maybe these could be commented out by default? Let me know what you think. -- graham syslog.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- [ Replying on the current bug title: “Option to enter URL for security / optional apt-src lines” ] Graham (2006-04-24): > 1. If I choose to manually enter a Debian mirror URL, then please also > prompt me to provide a URL for the security mirror. I'm firewalled and > the only accessible mirror is my local apt-proxy server. Currently apt > freezes for a long time trying to access security.debian.org directly, > and I have to switch to console 2 and kill the http retrieval process. > Then I have to edit sources.list later to correct the security entry. This is a marginal case and you can preseed that. > 3. Most end-user systems do not need "deb-src" lines in the > sources.list -- maybe these could be commented out by default? I agree with Joey's analysis, there's not much to be gained here. Closing this bug report accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#368243: packagessplit, new package apt-security-setup
Control: tag -1 moreinfo Hi, Steffen Joeris (2006-05-20): > <--snip--> > > I wondered if it would be possible to outsource the security mirror > stuff (90 security) into an own package, maybe apt-mirror-setup*udeb ? > I guess this is also done with the apt-mirror-setup and apt-cdrom-setup > packages or? > > <--snip--> > > This would allow others to decide if they want to include this udeb into > the installation or not. > > Short report why I would like to have it: > When the security mirror question is inputed the network is not yet > setup and therefore no mirror can be called. Anyway we are including the > security mirror later, so it would be nice to have the opportunity to > skip this part during the installation :) I'm not sure what the "security mirror question" means. apt-setup/security_host maybe? AFAICT the network is set up long before we hit apt-setup so I'm not sure I understand what you're requesting. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#368243: packagessplit, new package apt-security-setup
Processing control commands: > tag -1 moreinfo Bug #368243 [apt-setup] packagessplit, new package apt-security-setup Added tag(s) moreinfo. -- 368243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b368243.139362150910755.transcr...@bugs.debian.org
Bug#465817: marked as done (debian-installer: Should not enable source package lines by default)
Your message dated Fri, 28 Feb 2014 22:09:06 +0100 with message-id <20140228210906.ga5...@mraw.org> and subject line Re: Bug#465817: sources enabled in sources.list has caused the Debian Bug report #465817, regarding debian-installer: Should not enable source package lines by default 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.) -- 465817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: wishlist *** Please type your report below this line *** The etch DI release (at least) adds source package lines to apt, which on a slow link (eg, 128k ISDN) can add several minutes to the install time. As a vast majority of *users* never need them please consider disabling them by default. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Miguel Figueiredo (2010-09-12): > Not sure this is a good idea as this will prevent having an installed > system to be ready to get package sources. > > Having sources commented will also go against previous added feature of > adding deb-src to all package sources (#269154). > > Also with current apt feature to download only the changes in archive > the time used to update sources is minimized. > > I propose closing this bug. Agreed, and doing so. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#483957: marked as done (apt-setup: Display a link to the authoritive list of mirrors in sources.list)
Your message dated Fri, 28 Feb 2014 22:13:51 +0100 with message-id <20140228211351.ga6...@mraw.org> and subject line Re: Bug#483957: apt-setup: Display a link to the authoritive list of mirrors in sources.list has caused the Debian Bug report #483957, regarding apt-setup: Display a link to the authoritive list of mirrors in sources.list 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.) -- 483957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt-setup Severity: wishlist In the case the mirror choosen by the user stops working, the user doesn't have any information about how to change it. A first answer to this problem should be adding such a line in the sources.list file generated by apt-setup during installation : # Reference list of Debian mirrors: http://www.debian.org/mirror/list Best regards, -- Simon Paillard mirr...@debian.org --- End Message --- --- Begin Message --- Frans Pop (2008-06-01): > On Sunday 01 June 2008, Simon Paillard wrote: > > In the case the mirror choosen by the user stops working, the user > > doesn't have any information about how to change it. > > > > A first answer to this problem should be adding such a line in the > > sources.list file generated by apt-setup during installation : > > > > # Reference list of Debian mirrors: http://www.debian.org/mirror/list > > IMO that info belongs in the SOURCES.LIST(5) man page, not in the file > itself. > > One reason is that including it the sources.list file would mean that > derived distributions would be stuck with documentation pointing to > Debian mirrors while they might have their own. Of course, they could > patch that, but avoiding distribution-specific information when possible > is generally considered desirable. > As the sources.list man page is rather Debian-specific already this is > less of an issue there. Therefore cloning to apt. ACK; Simon, you may want to propose a patch there since it's still not implemented. > The most we could do in apt-setup is to include a reference to that > manual page in the generated sources.list file, but consulting > manpages should be the first step for finding info anyway, so that > could be considered redundant. How do others feel about this? ACK as well, so closing the apt-setup bug report accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Remaster amd64 iso to include some i386 packages?
Hey guys, I've created remastered lenny and squeeze install isos for our org in the past, but we've since moved to amd64 as our main platform, and I have some questions about trying to manually create a multiarch iso. Previously, I would do a vanilla install, clean up apt, then do any system updates, as well as our own packages. Then pull everything out of /var/cache/apt/archives and create a mini repo using dpkg-scanpackages. Then define that repo in the preseed file. This all worked well enough with a single i386 arch, but I'm wondering if apt/dpkg is smart enough for me to do the same with a base amd64 install, then enable i386 support? I'd turn on i386 support and install any additional files via preseed/late_command. But do I need some kind of separate setup/pool for the i386 packages? Thanks. -- Ryan Braun Defence Weather Services Chief Information Officer Branch, Environment Canada CIV: 204-833-2500x2625 CSN: 257-2625 FAX: 204-833-2558 E-Mail: ryan.br...@ec.gc.ca -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140228211136.gq11...@infinity.isb.ec.gc.ca
Bug#594461: marked as done (apt-setup: Should propose using t-p-u when testing is installed)
Your message dated Fri, 28 Feb 2014 22:26:04 +0100 with message-id <20140228212604.ga7...@mraw.org> and subject line Re: Bug#594461: apt-setup: Should propose using t-p-u when testing is installed has caused the Debian Bug report #594461, regarding apt-setup: Should propose using t-p-u when testing is installed 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.) -- 594461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt-setup Severity: wishlist After a (short) discussion in -devel, I came up with the proposal of activating "testing-proposed-updates" when users install testing, in a similar way that we currently propose activating volatile when they install stable. So, sending this as a bug report against apt-setup. I suggest this is done post-squeeze. Quoting Paul Wise (p...@debian.org): > On Wed, Aug 25, 2010 at 6:38 PM, Christian PERRIER wrote: > > Quoting Russ Allbery (r...@debian.org): > > > >> > Hmhm, out of curiosity, why is t-p-u “way riskier”. > >> > >> Mostly because there isn't any large pool of systems using t-p-u the way > >> there is for unstable, so the aging process where we get testing in > >> unstable before migrating the package never happens. This means uploads > > > > I wonder whether we (in D-I) could add t-p-u to the list of proposed > > repositories when users install testing. We already propose security > > and volatile (defaulting to both added): the same mechanism could be > > made for t-p-u when users install testing. > > Sounds like a good idea to me. When they reject t-p-u you could either > add it commented out or with pinning such that it is not selected by > default but when packages from it are selected then they are kept > upgraded within it until the packages migrate to testing itself. AFAIK > to achieve that you need pinning priorities > 500 and < 1000. > > -- > bye, > pabs > > http://wiki.debian.org/PaulWise > > > -- > 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/aanlktinbf2ktsg7ppwmv4cnz74wvhdj2vkfq3n9wf...@mail.gmail.com > > > > ** CRM114 Whitelisted by: WHITELIST ** > -- signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Joey Hess (2010-08-26): > Does it really make sense for users to use t-p-u? Anything can be > uploaded there, rejected by the release team, and no upgrade path is > necessarily provided for a system that installed a package from there > and ends up tracking stable. Since t-p-u → testing is an approve hint away (on the release team side), and since virtually anything can be uploaded there as Joey mentioned, I don't think it should be enabled by default. Good packages will probably flow to testing quickly, while bad packages will get filtered out. (Another way of saying this is that t-p-u is an implementation detail for packages to reach testing without having to migrate from unstable. We generally try very hard to avoid going that route anyway.) Closing this bug report accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#410571: marked as done (debian-installer: configure package mgr takes long time without UI feedback.)
Your message dated Fri, 28 Feb 2014 22:28:58 +0100
with message-id <20140228212858.ga8...@mraw.org>
and subject line Re: Bug#410571: debian-installer: configure package mgr takes
long time without UI feedback.
has caused the Debian Bug report #410571,
regarding debian-installer: configure package mgr takes long time without UI
feedback.
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.)
--
410571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Severity: wishlist
The configure package mgr screen takes a long while (presumably to init
the package manager, it takes +10 seconds) but there is no feedback
that something is taking place. Maybe a progress bar (or even a string
stating that this action could take longer).
Regards, Geert-Jan.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
Joey Hess (2007-02-11):
> I don't understand what step in the installation process you're
> referring to. What is the text that appears on the screen? ("Configure
> package mgr" is not it.)
No reply in 7 years, so closing.
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
Bug#368243: marked as done (packagessplit, new package apt-security-setup)
Your message dated Fri, 28 Feb 2014 22:31:53 +0100 with message-id <20140228213153.gf3...@mraw.org> and subject line Re: Bug#368243: packagessplit, new package apt-security-setup has caused the Debian Bug report #368243, regarding packagessplit, new package apt-security-setup 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.) -- 368243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt-setup Severity: wishlist Hi Here a short report from my mail to debian-boot, I am posting it as a wishlist bug :) <--snip--> I wondered if it would be possible to outsource the security mirror stuff (90 security) into an own package, maybe apt-mirror-setup*udeb ? I guess this is also done with the apt-mirror-setup and apt-cdrom-setup packages or? <--snip--> This would allow others to decide if they want to include this udeb into the installation or not. Short report why I would like to have it: When the security mirror question is inputed the network is not yet setup and therefore no mirror can be called. Anyway we are including the security mirror later, so it would be nice to have the opportunity to skip this part during the installation :) Greetings Steffen -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) --- End Message --- --- Begin Message --- Cyril Brulebois (2014-02-28): > I'm not sure what the "security mirror question" means. > apt-setup/security_host maybe? AFAICT the network is set up long before > we hit apt-setup so I'm not sure I understand what you're requesting. : Command died with status 127: "exec /usr/bin/procmail". Command output: sh: 1: exec: /usr/bin/procmail: not found → closing. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Re: Remaster amd64 iso to include some i386 packages?
ryan (2014-02-28): > Hey guys, I've created remastered lenny and squeeze install isos for our > org in the past, but we've since moved to amd64 as our main platform, and > I have some questions about trying to manually create a multiarch iso. > > Previously, I would do a vanilla install, clean up apt, then do any > system updates, as well as our own packages. Then pull everything out of > /var/cache/apt/archives and create a mini repo using dpkg-scanpackages. > Then define that repo in the preseed file. > > This all worked well enough with a single i386 arch, but I'm wondering if > apt/dpkg is smart enough for me to do the same with a base amd64 install, > then enable i386 support? > > I'd turn on i386 support and install any additional files via > preseed/late_command. But do I need some kind of separate setup/pool for > the i386 packages? You probably want to look at reprepro, which lets you handle several architectures in a single repository: http://mirrorer.alioth.debian.org/ It works a bit differently from dpkg-scanpackages, but it's worth the efforts on the middle/long run. Mraw, KiBi. signature.asc Description: Digital signature
Bug#201252: anna: "No installer modules found" the second time you load modules
Control: tag -1 moreinfo root (2003-07-14): > Package: anna > Version: 0.031 (not installed) > Severity: normal > > Use the floppy retriever. Load all available modules. > Repeat. The second time round, anna reports "no modules available", > which is confusing. Hi, boot floppies are gone now, but maybe the bug you experienced can still be reproduced. I haven't been able to do so by downloading installer components, and trying to re-enter that step. Can you please tell us whether you can replicate this issue on recent installation images? (Wheezy images would be seen as “recent”. ;)) Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#201252: anna: "No installer modules found" the second time you load modules
Processing control commands: > tag -1 moreinfo Bug #201252 [anna] anna: "No installer modules found" the second time you load modules Added tag(s) moreinfo. -- 201252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=201252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b201252.139362429732213.transcr...@bugs.debian.org
Bug#213834: marked as done (depends on libc-udeb)
Your message dated Fri, 28 Feb 2014 22:58:03 +0100
with message-id <20140228215803.gh3...@mraw.org>
and subject line Re: Bug#213834: anna 0.060
has caused the Debian Bug report #213834,
regarding depends on libc-udeb
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.)
--
213834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=213834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: anna
Severity: normal
Tags: d-i
anna depends on libc-udeb. I don't understand why. If anna is on the
initrd, then it gets all necessary symbols thanks to library reduction.
If it is not on the initrd, then it's going to be hard to load libc-udeb
at all anyway, and the creator of the images hopefully knows what he was
doing to set up such a weird circumstance.
In the meantime, just building d-i downloads all of libc-udeb, only to
throw it away, which makes it very painful on dialup.
Petter added the dependency to debian/control in cvs rev 1.25, with the
comment, "Replace ${shlibs:Depends} in depends to explicit list;
libc-udeb, cdebconf-udeb.".
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Miguel Figueiredo (2010-09-20):
> Hi all,
>
> i found this entry in anna's changelog (version 0.060), which may be
> relevant to this bug:
>
> - Stop hardcoding dependency on no longer existant libc-udeb, just use
> the libc6 dependency from substvars, and let libc6-udebs provide, plus
> libd-i's lack of version checking, do their thing.
I might be missing something but the current state of affairs (Depends on
libc$foo-udeb, with $foo varying across architectures) looks OK to me, so
closing this bug report.
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
Processed: Re: cdrom-retriever is a shell script; it'll be the caller that's segfaulting
Processing control commands: > tag -1 moreinfo Bug #391733 [anna] Segfault after unable to find Release file Added tag(s) moreinfo. -- 391733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b391733.13936252074995.transcr...@bugs.debian.org
Bug#391733: cdrom-retriever is a shell script; it'll be the caller that's segfaulting
Control: tag -1 moreinfo
Colin Watson (2010-03-11):
> reassign 391733 anna
> thanks
If nobody can come up with a simple way to reproduce the anna segfault,
I think I'll just close this bug report. Given the issue was triggered
{on,due to} broken installation media, I suspect this might be difficult.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Processed: severity of 367515 is important
Processing commands for cont...@bugs.debian.org: > severity 367515 important Bug #367515 [anna] kernel ABI mismatch message should tell user to look for an updated CD Severity set to 'important' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 367515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.13936254886525.transcr...@bugs.debian.org
Bug#334994: marked as done (debian-installer/function=rescue)
Your message dated Fri, 28 Feb 2014 23:34:49 +0100 with message-id <20140228223449.ga16...@mraw.org> and subject line Re: Bug#334994: debian-installer/function=rescue has caused the Debian Bug report #334994, regarding debian-installer/function=rescue 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.) -- 334994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Version: subversion Severity: wishlist Hello, Currently is the rescue mode activated by rescue/enable=true I wish to have that changed into more generic like debian-installer/function=rescue That "hook" will allow activation of other functions of debian-installer like network-console, sshclient, cloning or whatever ... GSt signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Frans Pop (2007-12-12): > tags 334994 wontfix > thanks > > From reading the BR again, especially Colin's comments, and knowing that we > already have the shortcut 'rescue=true', I doubt this will ever get > implemented. > > Tagging wontfix to allow further discussion. Agreed, and I don't think we're going to deviate from the current status, so closing accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#434930: Should "Continue" automatically when no key has been typed
Control: tag -1 moreinfo Jérémy Bobbio (2007-07-27): > Package: cdebconf-newt-entropy > Version: 0.4 > Severity: wishlist > > If enough entropy was already gathered before cdebconf-newt-entropy is > called, the user only sees a message saying "Key has been created" > without ever seeing the previous message. > > It would be better if the plugin would notice that no random key has > been pressed and continue automatically instead of waiting for the user > to select "Continue". > input. It would be nice to mention how to reproduce this issue. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#434930: Should "Continue" automatically when no key has been typed
Processing control commands: > tag -1 moreinfo Bug #434930 [cdebconf-newt-entropy] Should "Continue" automatically when no key has been typed Added tag(s) moreinfo. -- 434930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b434930.139362717616362.transcr...@bugs.debian.org
Bug#369256: installation-reports: modprobe does not find kernel modules
Joey Hess (2006-05-28): > Eddy Petrisor wrote: > > The modprobe command bundled in d-i environment does not work out of the > > box. If one starts the installer in expert mode and skips directly to > > the "Load installer components from CD" menu item, chooses a kernel > > module (let's say crypto modules) after the package's installation > > attempting to run "modprobe aes" on vt2 will result in an error message > > that the module is not found. > > > > It seems that after running netcfg the modprobe command behaves > > corectly. > > You have to run depmod. Before that, obviously modprobe has no way to > know that your module is available. depmod is run by hw-detect. > > I'm not sure that I'd characterise this as a bug at all. I'm not sure whether the following idea would make sense: when an udeb is installed, shipping something below /lib/modules, we could queue a depmod run (more or less mimicking a dpkg trigger). (I haven't done any cost analysis, but we probably don't want do that after every udeb when installing a bunch of them at once.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#379057: Please allow to deselect the modules that get loaded by default
Frans Pop (2007-12-12): > > While these all add functionality that allows one to do interesting > > things with debian-installer, it is also true that they all require > > memory to be used for functionality of which at least some is not > > going to be used during any random install session. > > Just wanted to note that with very recent changes at least partman-lvm > and partman-crypto, both of which have a relatively large number of > templates and dependencies, are now loaded dynamically and will only > be loaded if sufficient memory to run them is available. This goes > for their partman-auto-* variants as well of course. Wouter, have you been hitting this issue recently? Mraw, KiBi. signature.asc Description: Digital signature
Processed: Bug#261415: network installation always asks for proxy
Processing control commands: > tag -1 wontfix Bug #261415 [choose-mirror] network installation always asks for proxy Added tag(s) wontfix. -- 261415: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=261415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b261415.139362780120096.transcr...@bugs.debian.org
Bug#261415: network installation always asks for proxy
Control: tag -1 wontfix [ Edited Subject to match the cloned-to bug's status. ] Martin Pitt (2004-03-24): > - network installation always asks for proxy; I know what a proxy is, > but not all potential users may; would it be possible to try without > proxy first and ask for proxy settings only if direct connection > does not work? Never mind if that is not possible, just asking :-) Some translations have a less-techy way of explaining what a proxy is, and a default empty value should just be OK (people are expected to install Debian by pressing Enter most of the time, right? :)). I'm not sure we want to play with trial-and-error in d-i too much… Tagging wontfix for now to allow for somebody to step up and say otherwise. Mraw, KiBi. signature.asc Description: Digital signature
Bug#647405: please allow pre-seeding for deb-src line
Control: reassign -1 src:apt-setup Christian PERRIER (2011-11-02): > reassign 647405 choose-mirror > thanks > > Quoting Marc Haber (mh+debian-packa...@zugschlus.de): > > Package: debian-installer > > Severity: wishlist > > > > Hi, > > > > it is obviously not possible to de-select the generation of deb-src > > lines for the mirror selected during the installation process. > > > > Please consider allowing this, for example by a pre-seeding option > > d-i mirror/http/source boolean > > > Reassigning to what this report belongs to. I think that's rather about apt-setup's generators, so reassigning there. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#647405: please allow pre-seeding for deb-src line
Processing control commands: > reassign -1 src:apt-setup Bug #647405 [choose-mirror] please allow pre-seeding for deb-src line Bug reassigned from package 'choose-mirror' to 'src:apt-setup'. Ignoring request to alter found versions of bug #647405 to the same values previously set Ignoring request to alter fixed versions of bug #647405 to the same values previously set -- 647405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b647405.139362831923270.transcr...@bugs.debian.org
Bug#702093: debian-installer: please allow the user to set the system time manually
Riku Saikkonen (2013-03-02): > I have two suggestions for fixing this bug: > > - Please include the "date" command in busybox in the initrd to allow >setting the system time from the command line. I suspect this should be rather straightforward and harmless (a few extra bytes in busybox-udeb). > - If the user answers "No" to the NTP question in the installer menus, >please consider adding a dialog that shows the current time and asks >the user for a new time if it is wrong. (Possibly also ask about >writing the new time to the RTC using hwclock.) I don't think I'm going to implement that part though. Mraw, KiBi. signature.asc Description: Digital signature
Bug#645740: ntp suggestions for installation
Marc Haber (2011-10-18): > while playing around with d-i, I had the following ideas about ntp > handling: > > - d-i should show which ntp server it is trying to talk to while it >is trying to talk to them. I guess these are some pool.ntp.org >servers. Default clock-setup/ntp-server is 0.debian.pool.ntp.org indeed. > - If d-i cannot successfully talk to any pool.ntp.org servers, it >could try ntp'ing from the default gateway, and, if a proxy is >configured, from the proxy. Well, clock-setup checks netcfg/dhcp_ntp_servers, which contains NTP servers mentioned in DHCP replies, so I'd expect such gateways to announced the NTP servers properly. > - The installed system should have its ntp server configured to the >servers that the installer was able to correctly talk to. I don't think we necessarily install an ntp client; and since ntp configuration is client-dependent, this part looks hard to achieve. Mraw, KiBi. signature.asc Description: Digital signature
Bug#519079: installation-report: please provide an option to skip the attempt to set the system clock via NTP
Fabian Greffrath (2009-03-10): > However, there was one thing during installation that I found > annoying: My computer is behind a firewall that even blocks NTP > requests, so there is no chance to set the clock over the network. I > know this, so I wasn't too excited when d-i's first attempt to set the > clock apparently failed. It also did not upset me, when it failed a > second and a third time, but I really became impatient when it tried a > forth time and I really hesitated to click on the "Cancel" button for > a second. Fortunately it gave up after the fifth try. > > Now my request is, please add a "Skip" button for people who know that > setting the clock over the net won't work and who deliberately want to > skip this step. It isn't a crucial step for installation anyway. > > At least, if you don't find another button an appropriate solution, > please report to the user how many attempts you are still going to try > before d-i skips this step itself. Something like "Attempt number 3 of > 5." below the progress bar would have actually appeased me. The way it > is now, some users might get the impression that the installation > actually hangs and feel tempted to abort it after the second or third > try failed without a feedback. clock-setup/ntp=false should be your friend. Mraw, KiBi. signature.asc Description: Digital signature
Bug#519079: marked as done (installation-report: please provide an option to skip the attempt to set the system clock via NTP)
Your message dated Sat, 1 Mar 2014 00:40:51 +0100 with message-id <20140228234051.gb18...@mraw.org> and subject line Re: Bug#519079: installation-report: please provide an option to skip the attempt to set the system clock via NTP has caused the Debian Bug report #519079, regarding installation-report: please provide an option to skip the attempt to set the system clock via NTP 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.) -- 519079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Version: 2.38 Severity: minor *** Please type your report below this line *** Dear d-i team, last weekend I installed Debian Lenny and it worked like a charm (yay!). Please note that I decided to use the d-i images provided by Kenshi Muto in order to get my network card to work during installation (see #512546). Afaict only the kernel package has been replaced on his installation media. However, there was one thing during installation that I found annoying: My computer is behind a firewall that even blocks NTP requests, so there is no chance to set the clock over the network. I know this, so I wasn't too excited when d-i's first attempt to set the clock apparently failed. It also did not upset me, when it failed a second and a third time, but I really became impatient when it tried a forth time and I really hesitated to click on the "Cancel" button for a second. Fortunately it gave up after the fifth try. Now my request is, please add a "Skip" button for people who know that setting the clock over the net won't work and who deliberately want to skip this step. It isn't a crucial step for installation anyway. At least, if you don't find another button an appropriate solution, please report to the user how many attempts you are still going to try before d-i skips this step itself. Something like "Attempt number 3 of 5." below the progress bar would have actually appeased me. The way it is now, some users might get the impression that the installation actually hangs and feel tempted to abort it after the second or third try failed without a feedback. Thank you very much! Cheers, Fabian -- Package-specific info: Boot method: CD Image version: http://mirror.home-dn.net/d-i/2.6.28/lenny-custom-0302.iso Date: Machine: DELL Optiplex 760 Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [E] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: I gave "Detect network card" an "E" because I had to use unofficial installation media in order to install the system because of the usage of an outdated Linux kernel. I gave "Clock/timezone setup" an "E" because of the minor issue I described above. Everything else worked just perfectly. Great job! -- 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 20090302-13:09" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux frodo 2.6.28-1-486 #1 Mon Feb 23 02:22:20 UTC 2009 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e10] (rev 03) lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI Express Root Port [8086:2e11] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation 4 Series Chipset HECI Controller [8086:2e14] (rev 03) lspci -knn: 00:03.2 IDE interface [0101]: Intel Corporation 4 Series Chipset PT IDER Controller [8086:2e16] (rev 03) lspci -knn: 00:03.3 Serial controller [0700]: Intel Corporation 4 Series Chipset Serial KT Controller [8086:2e17] (rev 03) lspci -knn: Kernel d
Bug#287412: Bug#287344: rc2 netinst install on hp pavilion ze4900 laptop
On Fri, 2014-02-28 at 21:32 +0100, Cyril Brulebois wrote: > Control: tag -1 patch > > Joey Hess (2004-12-27): > > I was suprised to see that the acpi fan and thermal modules were not > > loaded on the installed system. This seems to be an oversight in > > rootskel, it loads the modules in the installer, but neglects to > > register-module them. > > > > If acpid had been installed, I think it would have taken care of > > loading all those modules. And it's needed for the gnome battery > > monitor anyway. We need a laptop task! However, I think that even with > > that, unconditionally register-moduleing fan and thermal is good from > > a belt and suspenders POV. > > I know close to nothing about module (auto)loading and the like, but if > the attached patch can do no harm and can actually help, I'm happy to > push it. What do you think? [...] udev loads these modules. Please remove S05acpi-linux-x86 instead. Ben. -- Ben Hutchings Gates has joked that everything goes on and off unexepectedly in the house, which is run by a high-end PC network built on Windows NT. - Seattle Times signature.asc Description: This is a digitally signed message part
Bug#369256: installation-reports: modprobe does not find kernel modules
On Fri, 2014-02-28 at 23:23 +0100, Cyril Brulebois wrote: > Joey Hess (2006-05-28): > > Eddy Petrisor wrote: > > > The modprobe command bundled in d-i environment does not work out of the > > > box. If one starts the installer in expert mode and skips directly to > > > the "Load installer components from CD" menu item, chooses a kernel > > > module (let's say crypto modules) after the package's installation > > > attempting to run "modprobe aes" on vt2 will result in an error message > > > that the module is not found. > > > > > > It seems that after running netcfg the modprobe command behaves > > > corectly. > > > > You have to run depmod. Before that, obviously modprobe has no way to > > know that your module is available. depmod is run by hw-detect. > > > > I'm not sure that I'd characterise this as a bug at all. > > I'm not sure whether the following idea would make sense: when an udeb > is installed, shipping something below /lib/modules, we could queue a > depmod run (more or less mimicking a dpkg trigger). > > (I haven't done any cost analysis, but we probably don't want do that > after every udeb when installing a bunch of them at once.) Or we could ship the module indices in kernel-image-* (I thought we did because kernel-wedge does run depmod, but that's just so it can use modules.dep at build time). This won't work if there are OOT module udebs, though. (There aren't any in Debian any more, but there might be in derivatives.) Ben. -- Ben Hutchings If at first you don't succeed, you're doing about average. signature.asc Description: This is a digitally signed message part
Bug#369256: installation-reports: modprobe does not find kernel modules
Control: reassign -1 src:linux Control: retitle -1 please ship module indices in udebs Ben Hutchings (2014-03-01): > Or we could ship the module indices in kernel-image-* (I thought we did > because kernel-wedge does run depmod, but that's just so it can use > modules.dep at build time). That looks very fine to me, please go ahead. :) > This won't work if there are OOT module udebs, though. (There aren't > any in Debian any more, but there might be in derivatives.) Those few packages can ship a postinst script to update indices through depmod I suspect. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#369256: installation-reports: modprobe does not find kernel modules
Processing control commands: > reassign -1 src:linux Bug #369256 [anna] anna: should call depmod after a set of installed modules Bug reassigned from package 'anna' to 'src:linux'. Ignoring request to alter found versions of bug #369256 to the same values previously set Ignoring request to alter fixed versions of bug #369256 to the same values previously set > retitle -1 please ship module indices in udebs Bug #369256 [src:linux] anna: should call depmod after a set of installed modules Changed Bug title to 'please ship module indices in udebs' from 'anna: should call depmod after a set of installed modules' -- 369256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b369256.139363922415482.transcr...@bugs.debian.org
Bug#734769: Same business for dockstar
On Sun, 2014-02-09 at 09:02 +0100, army.of.root wrote: > so that the Entry for the Dockstar looks like this (last 3 lines > added): Thanks. I pushed the following to flash-kernel.git: commit 9526f1d5d4b2261ea9edc763d912aa4acac70abe Author: Ian Campbell Date: Sat Mar 1 01:57:39 2014 + Append DTB on "Seagate FreeAgent DockStar" from v3.12 onwards Based on info from army.of.root in https://lists.debian.org/debian-boot/2014/02/msg00067.html diff --git a/db/all.db b/db/all.db index fab3407..67efaaf 100644 --- a/db/all.db +++ b/db/all.db @@ -377,10 +377,13 @@ Bootloader-Sets-Incorrect-Root: yes Machine: Seagate FreeAgent DockStar Kernel-Flavors: kirkwood +DTB-Id: kirkwood-dockstar.dtb +DTB-Append: yes U-Boot-Kernel-Address: 0x8000 U-Boot-Initrd-Address: 0x0 Boot-Kernel-Path: /boot/uImage Boot-Initrd-Path: /boot/uInitrd +Boot-DTB-Path: /boot/dtb Required-Packages: u-boot-tools Bootloader-Sets-Incorrect-Root: no diff --git a/debian/changelog b/debian/changelog index 73e95ff..516fd89 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +flash-kernel (3.14) UNRELEASED; urgency=low + + * Append DTB on "Seagate FreeAgent DockStar" from v3.12 onwards. + + -- Ian Campbell Sat, 01 Mar 2014 01:56:36 + + flash-kernel (3.13) unstable; urgency=low [ Ian Campbell ] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1393639330.19684.3.ca...@hastur.hellion.org.uk
Re: Bug#702093: debian-installer: please allow the user to set the system time manually
Control: reassign -1 busybox-udeb Control: retitle -1 busybox-udeb: please enable the 'date' applet Control: tag -1 patch Cyril Brulebois (2014-03-01): > Riku Saikkonen (2013-03-02): > > I have two suggestions for fixing this bug: > > > > - Please include the "date" command in busybox in the initrd to allow > >setting the system time from the command line. > > I suspect this should be rather straightforward and harmless (a few > extra bytes in busybox-udeb). > > > - If the user answers "No" to the NTP question in the installer menus, > >please consider adding a dialog that shows the current time and asks > >the user for a new time if it is wrong. (Possibly also ask about > >writing the new time to the RTC using hwclock.) > > I don't think I'm going to implement that part though. Reassigning this bug report to busybox-udeb accordingly. I've successfully tested the attached patch in a d-i environment. Mraw, KiBi. From ffb340341d0915e6af2043f4d5f5b310ccc155c8 Mon Sep 17 00:00:00 2001 From: Cyril Brulebois Date: Sat, 1 Mar 2014 03:06:15 +0100 Subject: [PATCH] Enable the date applet in the udeb (Closes: #702093) --- debian/changelog | 6 ++ debian/config/pkg/udeb | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 9bbeea5..21b48ab 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +busybox (1:1.22.0-5) UNRELEASED; urgency=medium + + * Enable the date applet in the udeb (Closes: #702093) + + -- Cyril Brulebois Sat, 01 Mar 2014 03:05:45 +0100 + busybox (1:1.22.0-4) unstable; urgency=low * new: do-not-fail-on-missing-SIGPWR.patch: fix FTBFS on !linux, diff --git a/debian/config/pkg/udeb b/debian/config/pkg/udeb index a5f174d..668c366 100644 --- a/debian/config/pkg/udeb +++ b/debian/config/pkg/udeb @@ -176,7 +176,7 @@ CONFIG_FEATURE_TAR_NOPRESERVE_TIME=y # CONFIG_BASENAME=y CONFIG_CAT=y -# CONFIG_DATE is not set +CONFIG_DATE=y # CONFIG_FEATURE_DATE_ISOFMT is not set # CONFIG_FEATURE_DATE_NANO is not set # CONFIG_FEATURE_DATE_COMPAT is not set -- 1.9.0 signature.asc Description: Digital signature
Processed: Re: Bug#702093: debian-installer: please allow the user to set the system time manually
Processing control commands: > reassign -1 busybox-udeb Bug #702093 [clock-setup] debian-installer: please allow the user to set the system time manually Bug reassigned from package 'clock-setup' to 'busybox-udeb'. Ignoring request to alter found versions of bug #702093 to the same values previously set Ignoring request to alter fixed versions of bug #702093 to the same values previously set > retitle -1 busybox-udeb: please enable the 'date' applet Bug #702093 [busybox-udeb] debian-installer: please allow the user to set the system time manually Changed Bug title to 'busybox-udeb: please enable the 'date' applet' from 'debian-installer: please allow the user to set the system time manually' > tag -1 patch Bug #702093 [busybox-udeb] busybox-udeb: please enable the 'date' applet Added tag(s) patch. -- 702093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b702093.139363965717671.transcr...@bugs.debian.org
Bug#740397: busybox: please add support for parallel building
Package: busybox
Version: 1:1.20.0-7
Severity: normal
Tags: patch
Hi,
the title and the attached patch say it all.
(On a slightly, but not totally unrelated note: supporting nocheck as
well would be nice.)
Reference:
https://www.debian.org/doc/debian-policy/ch-source.html
Mraw,
KiBi.
>From 6c22faa974e2a20a65f725ae408c9418ec61697d Mon Sep 17 00:00:00 2001
From: Cyril Brulebois
Date: Sat, 1 Mar 2014 03:12:56 +0100
Subject: [PATCH] Implement support for parallel=n in DEB_BUILD_OPTIONS.
---
debian/changelog | 6 ++
debian/rules | 7 ++-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index 9bbeea5..19c5c30 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+busybox (1:1.22.0-5) UNRELEASED; urgency=medium
+
+ * Implement support for parallel=n in DEB_BUILD_OPTIONS.
+
+ -- Cyril Brulebois Sat, 01 Mar 2014 03:12:30 +0100
+
busybox (1:1.22.0-4) unstable; urgency=low
* new: do-not-fail-on-missing-SIGPWR.patch: fix FTBFS on !linux,
diff --git a/debian/rules b/debian/rules
index 0afe7a6..7fd 100755
--- a/debian/rules
+++ b/debian/rules
@@ -22,6 +22,11 @@ ifneq (${DEB_HOST_GNU_TYPE},${DEB_BUILD_GNU_TYPE})
export CROSS_COMPILE = ${DEB_HOST_GNU_TYPE}-
endif
+# support for parallel building
+ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
+NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
+endif
+
# we filter out -Werror=format-security from CFLAGS, because
# bb uses constructs like
# bb_error_msg_and_die(bb_msg_memory_exhausted);
@@ -88,7 +93,7 @@ ${b}/stamp-build: $(patsubst %,${b}/%/.stamp-build, ${flavours}) ${test-dep}
${b}/%/.stamp-build: DIR = ${b}/$*
${b}/%/.stamp-build: ${b}/%/.stamp-setup
dh_testdir
- $(MAKE) -C ${DIR} install docs/busybox.1 \
+ $(MAKE) -j$(NUMJOBS) -C ${DIR} install docs/busybox.1 \
SKIP_STRIP=y \
BB_EXTRA_VERSION="${VENDOR} ${PKGVERSION}" \
CONFIG_EXTRA_CFLAGS='${EXTRA_CFLAGS} ${EXTRA_CPPFLAGS}' \
--
1.9.0
Re: busybox failing to build on raspbian due to text formatting differences, any thoughts on what the cause could be?
peter green (2014-02-25): > Busybox has been failing to build in raspbian with what appear to be text > formatting differences. > > http://buildd.raspbian.org/status/fetch.php?pkg=busybox&arch=armhf&ver=1%3A1.22.0-4&stamp=1393285422 > > FAIL: expand with unicode characher 0x394 > --- expected > +++ actual > @@ -1 +1 @@ > -Δ 12345ΔΔΔ12345678 > +Δ 12345ΔΔΔ 12345678 > > FAIL: fold -sw66 with unicode input > --- expected > +++ actual > @@ -4,8 +4,13 @@ > 2,500,000 light-years (1.58×10^11 AU) away in the constellation > Andromeda. It is the nearest spiral galaxy to our own, the Milky > Way. > -Галактика або Туманність Андромеди (також відома як M31 за > -каталогом Мессьє та NGC224 за Новим загальним каталогом) — > -спіральна галактика, що знаходиться на відстані приблизно у 2,5 > -мільйони світлових років від нашої планети у сузір'ї Андромеди. -На > початку ХХІ ст. в центрі галактики виявлено чорну дірку. > \ No newline at end of file > +Галактика або Туманність Андромеди +(також відома як M31 за > каталогом +Мессьє та NGC224 за Новим загальним +каталогом) — > спіральна галактика, +що знаходиться на відстані +приблизно у 2,5 > мільйони світлових +років від нашої планети у сузір'ї +Андромеди. На > початку ХХІ ст. в +центрі галактики виявлено чорну +дірку. > \ No newline at end of file > > And so on > > Does anyone have any idea what might be causing this? maybe some kind > of locale issue that is causing different measurements of string > length? (our buildds seem to be setup with LC_ALL=posix) I'm getting this as well in a sid development chroot, be it with LANG=en_GB.UTF-8, or with LC_ALL=C. All failures: FAIL: expand with unicode characher 0x394 FAIL: fold -sw66 with unicode input FAIL: ls unicode test with codepoints limited to 767 FAIL: taskset (set_aff, needs CAP_SYS_NICE) FAIL: unexpand with unicode characher 0x394 I could open up a placeholder bug report, but digging a bit more would be nice. Mraw, KiBi. signature.asc Description: Digital signature
Bug#739976: add device support: mirabox
On Mon, 2014-02-24 at 14:41 +0100, Jasmin Schnatterbeck wrote: > Package: flash-kernel > Version: 3.13 > Severity: important > > The device DB is missing support for the Mirabox. > > Proposal: Thanks for this. Perhaps you could also add some information to http://wiki.debian.org/DebianOn ? > Machine: Globalscale Mirabox > Kernel-Flavors: armmp > DTB-Id: armada-370-mirabox.dtb > DTB-Append: yes Is this really required on new platform like this? I would expect that a newish system would have a u-boot which supports FDT natively rather that via appending. Does loading the dtb at some address and adding that address as a third argument to the "bootz" or "bootm" command work? On the other hand you say the u-boot is quite old so maybe this is correct, I just wanted to check that you didn't just copy this bit from an older platform. > U-Boot-Kernel-Address: 0x8000 > U-Boot-Initrd-Address: 0x0 > Boot-Device: /dev/sdb1 > Boot-Kernel-Path: uImage > Boot-Initrd-Path: uInitrd > Boot-DTB-Path: dtb > Required-Packages: u-boot-tools > Bootloader-Sets-Root: no This is now called Bootloader-Sets-Incorrect-Root. > Even kernel 3.13. does not support the device's internal > NAND chip - /dev/sdb is the microsd-slot of the device which can be used > as rootfs. > Bootloader is u-boot (heavily modified by the manufacturer and fairly > old) with unusable ext2load (at least for ext4), so separate boot > partition /dev/sdb1 for fatload makes sense. OOI do you know if mainline u-boot getting any support for this device (whether based on the vendor's version or not)? Ian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1393641774.19684.10.ca...@hastur.hellion.org.uk
Bug#740397: busybox: please add support for parallel building
On Sat, 2014-03-01 at 03:17 +0100, Cyril Brulebois wrote:
> - $(MAKE) -C ${DIR} install docs/busybox.1 \
> + $(MAKE) -j$(NUMJOBS) -C ${DIR} install docs/busybox.1 \
If parallel build is not set then won't this end up passing a bare "-j"
which will run an unlimited number of jobs...
https://www.debian.org/doc/debian-policy/ch-source.html suggests:
ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
NUMJOBS = $(patsubst parallel=%,%,$(filter
parallel=%,$(DEB_BUILD_OPTIONS)))
MAKEFLAGS += -j$(NUMJOBS)
endif
to avoid this.
Ian.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/1393641942.19684.12.ca...@hastur.hellion.org.uk
Bug#740397: busybox: please add support for parallel building
Ian Campbell (2014-03-01):
> On Sat, 2014-03-01 at 03:17 +0100, Cyril Brulebois wrote:
> > - $(MAKE) -C ${DIR} install docs/busybox.1 \
> > + $(MAKE) -j$(NUMJOBS) -C ${DIR} install docs/busybox.1 \
>
> If parallel build is not set then won't this end up passing a bare "-j"
> which will run an unlimited number of jobs...
>
> https://www.debian.org/doc/debian-policy/ch-source.html suggests:
>
> ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
> NUMJOBS = $(patsubst parallel=%,%,$(filter
> parallel=%,$(DEB_BUILD_OPTIONS)))
> MAKEFLAGS += -j$(NUMJOBS)
> endif
>
> to avoid this.
Well I didn't want to set MAKEFLAGS unconditionally (not sure how other
$(MAKE) calls deal with parallelism), so I've written crap instead; oops
thanks for catching. If following policy's suggestion isn't possible, we
could add "else\nNUMJOBS = 1" to avoid what you spotted.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Bug#740397: busybox: please add support for parallel building
On Sat, 2014-03-01 at 04:01 +0100, Cyril Brulebois wrote:
> Ian Campbell (2014-03-01):
> > On Sat, 2014-03-01 at 03:17 +0100, Cyril Brulebois wrote:
> > > - $(MAKE) -C ${DIR} install docs/busybox.1 \
> > > + $(MAKE) -j$(NUMJOBS) -C ${DIR} install docs/busybox.1 \
> >
> > If parallel build is not set then won't this end up passing a bare "-j"
> > which will run an unlimited number of jobs...
> >
> > https://www.debian.org/doc/debian-policy/ch-source.html suggests:
> >
> > ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
> > NUMJOBS = $(patsubst parallel=%,%,$(filter
> > parallel=%,$(DEB_BUILD_OPTIONS)))
> > MAKEFLAGS += -j$(NUMJOBS)
> > endif
> >
> > to avoid this.
>
> Well I didn't want to set MAKEFLAGS unconditionally (not sure how other
> $(MAKE) calls deal with parallelism), so I've written crap instead; oops
> thanks for catching. If following policy's suggestion isn't possible, we
> could add "else\nNUMJOBS = 1" to avoid what you spotted.
If you are worried about changing MAKEFLAGS then I would suggest setting
you own var including the -j too, e.g. J_FLAG=-j$(NUMOBJS), and using it
where it is needed.
Ian.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/1393643951.19684.14.ca...@hastur.hellion.org.uk
