Bug#740397: busybox: please add support for parallel building
01.03.2014 06:17, Cyril Brulebois wrote: > Package: busybox > Version: 1:1.20.0-7 > Severity: normal > Tags: patch > > Hi, > > the title and the attached patch say it all. Oh well. This come several times in the past for various packages, and it always ends up in some strange place. I always build my packages in parallel mode locally and ofcourse ensure they build fine that way. Because, well, I dislike waiting for too long when my machine have many cores doing nothing. The way I alway do this is by passing -jX flag to dpkg-buildpackage, sbuild, or just ./d/rules -jX, and so on. This ends up being a flag for the top-level make (which calls d/rules) so the job server becomes global. It is the easiest and most strightforward way. Now, when adding support for DEB_BUILD_OPTIONS's parallel=X suboption, I always end up in either my packages building in just one thread (because I still haven't figured how to pass environment variables to sbuild for example), or I have to use a non-easy, much more verbose way to run dpkg-buildpackage (setting DEB_BUILD_OPTIONS= instead of just passing -j). Because DEB_BUILD_OPTIONS handling, at the end, overrides -j somehow. The way how you proposed to fix your initial proposal -- add "else\nNUMJOBS = 1" -- makes this obvious, -- no matter what -jX is passed to the top-level, the build will be done according to DEB_BUILD_OPTS (whenever it is set or unset). I asked about this several times on #irc but got no good answer. And after some tries I ended up in what we have now, -- I just ignore DEB_BUILD_OPTIONS, because I try to build the package much more often than it is built on buildds, and I want the process to be easiest for me not for machines, and I value my own time much more than CPU time of debian buildd network (even of the slowest machines in there). When you look at debhelper in this context, things becomes even more interesting. I wasn't able to make it work with -j _and_ with its --parallel flag. Also, when you set -j just for submakes, quite often make complains about various issues with the job server. When -j is set for the top-level d/rules, this doesn't happen (unless there's a bug in the submake invocation or in upstream build system). > (On a slightly, but not totally unrelated note: supporting nocheck as > well would be nice.) Yeah, nocheck is something I wanted to implement but forgot. Will do. > Reference: > https://www.debian.org/doc/debian-policy/ch-source.html Yes, I know parallel= in there. And I tried numerous times to obey the rules and to make it work. Every time had issues and finally gave up. Thanks, /mjt -- 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/531193c8.1000...@msgid.tls.msk.ru
Processed: Re: Bug#740397: busybox: please add support for parallel building
Processing control commands: > tag -1 + pending Bug #740397 [busybox] busybox: please add support for parallel building Added tag(s) pending. -- 740397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740397 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.b740397.1393662011730.transcr...@bugs.debian.org
Bug#740397: busybox: please add support for parallel building
Control: tag -1 + pending 01.03.2014 12:01, Michael Tokarev wrote: > 01.03.2014 06:17, Cyril Brulebois wrote: >> Package: busybox >> Version: 1:1.20.0-7 >> Severity: normal >> Tags: patch >> >> Hi, >> >> the title and the attached patch say it all. > > Oh well. > > This come several times in the past for various packages, and it always > ends up in some strange place. > > I always build my packages in parallel mode locally and ofcourse > ensure they build fine that way. Because, well, I dislike waiting > for too long when my machine have many cores doing nothing. > > The way I alway do this is by passing -jX flag to dpkg-buildpackage, > sbuild, or just ./d/rules -jX, and so on. This ends up being a flag > for the top-level make (which calls d/rules) so the job server becomes > global. It is the easiest and most strightforward way. > > Now, when adding support for DEB_BUILD_OPTIONS's parallel=X suboption, > I always end up in either my packages building in just one thread > (because I still haven't figured how to pass environment variables to > sbuild for example), or I have to use a non-easy, much more verbose > way to run dpkg-buildpackage (setting DEB_BUILD_OPTIONS= instead of > just passing -j). Because DEB_BUILD_OPTIONS handling, at the end, > overrides -j somehow. > > The way how you proposed to fix your initial proposal -- add > "else\nNUMJOBS = 1" -- makes this obvious, -- no matter what -jX > is passed to the top-level, the build will be done according to > DEB_BUILD_OPTS (whenever it is set or unset). > > I asked about this several times on #irc but got no good answer. > And after some tries I ended up in what we have now, -- I just ignore > DEB_BUILD_OPTIONS, because I try to build the package much more > often than it is built on buildds, and I want the process to be > easiest for me not for machines, and I value my own time much more > than CPU time of debian buildd network (even of the slowest machines > in there). Ok. After looking around I found a recipe which I used in other packages to satisfy both those requiriments: # support parallel build using DEB_BUILD_OPTIONS=parallel=N ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) MAKEFLAGS += \ -j$(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) endif (which is quite similar to what the debian policy says), and it appears to work. So I've added the same to busybox d/rules and it at least continues to work with -jN, so I know that my way of doing things hasn't broke, which is good. Other related topics (how to pass DEB_BUILD_OPTIONS or anything else to sbuild, or how to make simple -j work together with this DEB_BUILD_OPTIONS in dh-style d/rules etc), while related, are not holding this bug in any way. Thanks, /mjt -- 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/53119839.1060...@msgid.tls.msk.ru
Bug#740410: installation-reports
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso Date: Feb. 23th Machine: laptop Dell latitude D430 Processor:intel Memory: Partitions: Résultat de lspci -knn (ou lspci -nn) : Installation du système de base : [O] = OK, Always the same problem after the installation of the basic system: exactly at the stage "verification CD" the installation does not go on , it is blocked on " 11% " and it is useless to wait. I have changed the CD many times, and I have also tried another dayli built image iso , but it was always the same error. Too bad. I hope that this report will be useful. Long life to Debian ! Best wishes, Jo.
Re: Bug#740073: netinst hangs on scanning CD-ROM
> From: Atanas Kumbarov > Date: Thu, 27 Feb 2014 20:23:50 +0100 > Hi, > I've been having the same problem for several days. I am trying to install Debian 8 amd64 from the netinst image on an ASUS UL30A with both VMware Player and VirtualBox atop Debian 7 > and the installer stalls when scanning the CD-ROM. > > Regards, > AK Process stops at 11%? If so it's because the apt-cdrom part of the debian installer is borked and it's sitting there waiting for you to add another CD-ROM, but there's no way you can send Enter to it. A work-around is to:- ;Open a terminal ;ps | grep apt-cdrom ;note the PID of "apt-cdrom ident" ;kill -KILL $PID ;return to the installation screen and hit "Continue". Thanks to Slavko for pointing to the solution Now all I have to do is find a way to workaround the borked choose-mirror section, which fails regardless of which mirror is selected with "mirror does not support the specified release (jessie)" (though the mirror does support it). Then maybe I can fix the next bork "unable to locate package (popularity-contest, grub-common, etc, etc)" - which stops the installer from being able to install GRUB, or lilo. 'Debian GNU/Linux testing "Jessie" - Official Snapshot i386 NETINST Binary-1 20140224-04:27' Kind regards -- 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/5311ae9b.5030...@gmail.com
Bug#740397: busybox: please add support for parallel building
Michael Tokarev (2014-03-01): > Now, when adding support for DEB_BUILD_OPTIONS's parallel=X suboption, > I always end up in either my packages building in just one thread > (because I still haven't figured how to pass environment variables to > sbuild for example) You just have to set it in your environment, that ends up into sbuild sessions: | User Environment | | | DEB_BUILD_OPTIONS=parallel=8 | […] Mraw, KiBi. signature.asc Description: Digital signature
Bug#740397: busybox: please add support for parallel building
On Sat, 2014-03-01 at 12:01 +0400, Michael Tokarev wrote: > 01.03.2014 06:17, Cyril Brulebois wrote: > > Package: busybox > > Version: 1:1.20.0-7 > > Severity: normal > > Tags: patch > > > > Hi, > > > > the title and the attached patch say it all. > > Oh well. > > This come several times in the past for various packages, and it always > ends up in some strange place. > > I always build my packages in parallel mode locally and ofcourse > ensure they build fine that way. Because, well, I dislike waiting > for too long when my machine have many cores doing nothing. > > The way I alway do this is by passing -jX flag to dpkg-buildpackage, > sbuild, or just ./d/rules -jX, and so on. This ends up being a flag > for the top-level make (which calls d/rules) so the job server becomes > global. It is the easiest and most strightforward way. [...] dpkg-buildpackage -j does *not* put -j on the debian/rules command line. It sets DEB_BUILD_OPTIONS. This is done precisely so that build daemons can use dpkg-buildpackage -j for everything but it will only result in a parallel make where the maintainer has checked that this works. 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#740397: busybox: please add support for parallel building
On 1 March 2014 03:01, 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.
>
I typically choose:
dh_auto_build --parallel -B${DIR} -- install docs/busybox.1
That does DEB_BUILD_OPTIONS processing, et.al. One does not need to
the rest of dh, to use parallel dh_auto_build invocations.
--
Regards,
Dimitri.
--
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/CANBHLUh2=axmd2b_-xf6zpjz4_ygovkjkqsqeve18pjmge3...@mail.gmail.com
Bug#740397: busybox: please add support for parallel building
Ben Hutchings (2014-03-01):
> dpkg-buildpackage -j does *not* put -j on the debian/rules command line.
> It sets DEB_BUILD_OPTIONS. This is done precisely so that build daemons
> can use dpkg-buildpackage -j for everything but it will only result in a
> parallel make where the maintainer has checked that this works.
FWIW it does exactly that:
| if (defined $parallel) {
| $parallel = $build_opts->get("parallel") if $build_opts->has("parallel");
| $ENV{MAKEFLAGS} ||= '';
| $ENV{MAKEFLAGS} .= " -j$parallel";
| $build_opts->set("parallel", $parallel);
| $build_opts->export();
| }
Mraw,
KiBi.
signature.asc
Description: Digital signature
Re: Bug#735476: dns323-firmware-tools: Please migrate to Ruby 1.9/2.0
Christian Hofstaedtler (2014-01-15): > Package: dns323-firmware-tools > Version: 0.3-2 > Severity: important > > Dear Maintainer, > > your package "dns323-firmware-tools" depends on an obsolete version of > the ruby interpreter: ruby1.8. > > The Debian Ruby team will remove ruby1.8 from Debian soon. Please migrate > your package to a newer version of the Ruby interpreter, so it won't be > broken when the removal happens. So, d-i build-dep on this package on armel; could any arm* guy please look into porting it to ruby1.9/2.0 (see #1), or at least volunteer to test an updated package if somebody comes up with a patch against dns323-firmware-tools? 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735476#10 Thanks for your time. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#369256: installation-reports: modprobe does not find kernel modules
Processing control commands: > reassign -1 kernel-wedge Bug #369256 [src:linux] please ship module indices in udebs Bug reassigned from package 'src:linux' to 'kernel-wedge'. 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 -- 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.139367701418501.transcr...@bugs.debian.org
Bug#740397: busybox: please add support for parallel building
On Sat, 2014-03-01 at 12:51 +0100, Cyril Brulebois wrote:
> Ben Hutchings (2014-03-01):
> > dpkg-buildpackage -j does *not* put -j on the debian/rules command line.
> > It sets DEB_BUILD_OPTIONS. This is done precisely so that build daemons
> > can use dpkg-buildpackage -j for everything but it will only result in a
> > parallel make where the maintainer has checked that this works.
>
> FWIW it does exactly that:
> | if (defined $parallel) {
> | $parallel = $build_opts->get("parallel") if
> $build_opts->has("parallel");
> | $ENV{MAKEFLAGS} ||= '';
> | $ENV{MAKEFLAGS} .= " -j$parallel";
> | $build_opts->set("parallel", $parallel);
> | $build_opts->export();
> | }
Not exactly the same thing, but I agree that it's effectively passing -j
to make. Thanks for correcting my memory on this.
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#740426: Jessie-install problem
Package: installation-reports Boot method: Image version: Date: <02/27/14; 02/30/14; 03/01/14> Machine: Processor: Intel Duo E6850 @ 3.00ghz Memory: 4 Gg Partitions: Output of 00:00.0 Host bridge [0600]: Intel Corporation 82X38/X48 Express DRAM Controller [8086:29e0] (rev 01) 00:06.0 PCI bridge [0604]: Intel Corporation 82X38/X48 Express Host-Secondary PCI Express Bridge [8086:29e9] (rev 01) 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02) 00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 02) 00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 [8086:294a] (rev 02) 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) 00:1d.3 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02) 00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02) 00:1f.6 Signal processing controller [1180]: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem [8086:2932] (rev 02) 03:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84GL [Quadro FX 1700] [10de:040f] (rev a1) 0d:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5755 Gigabit Ethernet PCI Express [14e4:167b] (rev 02) 0f:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5754 Gigabit Ethernet PCI Express [14e4:167a] (rev 02) 11:0d.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] [104c:8023] Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0 ] Detect network card:[0 ] Configure network: [0 ] Detect CD: [ 0] Load installer modules: [0 ] Detect hard drives: [0 ] Partition hard drives: [E ] Install base system:[ 0] Clock/timezone setup: [0 ] User/password setup:[0 ] Install tasks: [ 0] Install boot loader:[E ] Overall install:[E ] Comments/Problems: I am install debian Jessie (testing) from burned iso (KDE) desktop, although it does not matter which DE is chosen. Install recognizes hardware correctly. When partition the HD, chose EXT4 on one partition. The installer does format and partition the HD. After partition is complete, and error reporting linux kernel is unavailable or busy does not know about changes. The installer offers you to ignore or cancel this error. In any event it will just keep providing those options. If you reboot, and attempt installation again, partitioning takes place, and the error does not happen again. At the end of the installation process, it does not offer you to install grub, and installer fails out, nothing happens. In short, the installer does not install or correctly install grub, and system is unbootable upon restart. -- 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/5437350.mctCqftNu9@fedora
Bug#740410: installation-reports
On Sat 01 Mar, Joseph Vidal-Rosset wrote: > Package: installation-reports > > Boot method: CD > Image version: > http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/i > so-cd/debian-testing-i386-netinst.iso > Date: Feb. 23th > > Machine: laptop Dell latitude D430 > Processor:intel > Memory: > Partitions: > > Résultat de lspci -knn (ou lspci -nn) : > > Installation du système de base : > [O] = OK, > > Always the same problem after the installation of the basic system: > exactly at the stage "verification CD" the installation does not go on > , it is blocked on " 11% " and it is useless to wait. I have changed > the CD many times, and I have also tried another dayli built image iso > , but it was always the same error. Too bad. > > > > > I hope that this report will be useful. > > > Long life to Debian ! > > > Best wishes, > > > Jo. > There used to be a frequent problem with hardware that could not use DMA. -- Chris Bell www.chrisbell.org.uk -- 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/marcel-1.53-0301135117-bc8h...@riscpc.main
Processed: tagging 702093
Processing commands for cont...@bugs.debian.org: > tags 702093 + pending Bug #702093 [busybox-udeb] busybox-udeb: please enable the 'date' applet Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 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.c.139369481032503.transcr...@bugs.debian.org
Processing of mklibs_0.1.39_amd64.changes
mklibs_0.1.39_amd64.changes uploaded successfully to localhost along with the files: mklibs_0.1.39.dsc mklibs_0.1.39.tar.xz mklibs_0.1.39_all.deb mklibs-copy_0.1.39_amd64.deb 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/e1wjope-00014c...@franck.debian.org
Bug#329733: marked as done (mlibs truncates newt symbols on mipsel)
Your message dated Sat, 1 Mar 2014 19:59:50 +0100 with message-id <20140301185950.ga22...@mraw.org> and subject line Re: Bug#329733: mlibs truncates newt symbols on mipsel has caused the Debian Bug report #329733, regarding mlibs truncates newt symbols on mipsel 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.) -- 329733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mklibs Version: 0.1.16.1 Severity: normal Tags: d-i This could easily be a binutils bug or something and not a mklibs issue. I'm seeing it on mipsel, during the d-i build or by hand, and it seems to be truncating some symbols. For example: joeyh@enyo:~/installer/build/tmp$ mkdir foo joeyh@enyo:~/installer/build/tmp$ cd foo joeyh@enyo:~/installer/build/tmp/foo$ cp /usr/bin/whiptail . joeyh@enyo:~/installer/build/tmp/foo$ mklibs -d . whiptail I: Using ld.so.1 as dynamic linker. I: library reduction pass 1 83 symbols, 83 unresolved I: library reduction pass 2 207 symbols, 57 unresolved Traceback (most recent call last): File "/usr/bin/mklibs", line 473, in ? raise "No library provides non-weak " + symbol No library provides non-weak NAMIC joeyh@enyo:~/installer/build/tmp/foo$ objdump -T libnewt.so.0.51-so-stripped |grep NAMIC DYNAMIC SYMBOL TABLE: 00ec gDO *ABS* Base_DYNAMIC DO *UND* 0826 NAMIC Now, I'm sure that "NAMIC" was not a symbol in libnewt before mklibs reduced it. During the d-i daily builds it fails similarly but with a symbol "ng", which is probably the end of one of the _string symbols. Workaround is to remove libnewt-pic. None of the other libraries used by d-i seem to trigger the problem. (I tried it with versions 0.51.6-31 and 0.51.6-30 of the newt libraries, same problem with either. Also reproduced it on two different raq2's.) -- see shy jo signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Joey Hess (2005-09-23): > Package: mklibs > Version: 0.1.16.1 > Severity: normal > Tags: d-i > > This could easily be a binutils bug or something and not a mklibs issue. > I'm seeing it on mipsel, during the d-i build or by hand, and it seems > to be truncating some symbols. I don't think it's been an issue in recent years, so closing this bug report for now. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
mklibs_0.1.39_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 01 Mar 2014 19:25:40 +0100 Source: mklibs Binary: mklibs mklibs-copy Architecture: source all amd64 Version: 0.1.39 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Description: mklibs - Shared library reduction script mklibs-copy - Shared library reduction script Changes: mklibs (0.1.39) unstable; urgency=medium . * Sort objects and libraries to reduce entropy in the output, which should make d-i build logs more easily post-processable. Checksums-Sha1: d8f3362290f20057615cf7a9fbcd3f2bec41e284 1726 mklibs_0.1.39.dsc 708caadf50a28a33912535da603182abd32ccc7f 22040 mklibs_0.1.39.tar.xz 93fc88ca10fe50c6faa7415007bb078bc8bbaaf3 14058 mklibs_0.1.39_all.deb a63eaac5ca83ee81ce778507728f34f24be1861c 36920 mklibs-copy_0.1.39_amd64.deb Checksums-Sha256: 3e400377c096ef5b053469ee27a271e97cd98a99f0d19495334947271cdeec2c 1726 mklibs_0.1.39.dsc fa2881ab4fe72b0504878357f1fc6b17920459b56e8a60dfb083ca28fb64e733 22040 mklibs_0.1.39.tar.xz be1be19ead3f4c7c460255b2b16c2154ece3a6224df60d034dee18397634a76c 14058 mklibs_0.1.39_all.deb 71acba22fdc263f44487531c3a5adf56f037e421773e7954ed09ba8e3a728607 36920 mklibs-copy_0.1.39_amd64.deb Files: 4a2cdfb925ded8710aae7a89bb4f4455 1726 devel optional mklibs_0.1.39.dsc 38a579a531401eb76f4bab4ccfb774a2 22040 devel optional mklibs_0.1.39.tar.xz 5383def865a7edbe42c3321f47a40985 14058 devel optional mklibs_0.1.39_all.deb bc03686e286a61c93f556730bf62117c 36920 devel optional mklibs-copy_0.1.39_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJTEihoAAoJEP+RSvDCs1Ug2qkQAKQpKMKBTnyOe/6on73Xf9Xs dC51wv0G0Mq5e31EXYLlqdf57a686MSjiftdPuXSWKcSnoO3lORvrPz1Yv1NSjAc +ONdlzzarwNa+dOmYxDQ4+4SmCzqkGCW3wNCOX95CE310o04NLbbJ3WLPMiLFlM4 uCBiKIRCKboNB6pjEakCvRE8p1VoJ6lhrRO4nS53DryqUkIut/emHzV2PyJNSrk8 DS5RgtxKVJdtIrp4xn7mLaEt3tBRRNS9fjzYVy22TBUuPneh3TPnWR57xHlh/ZIG xBXYLKiZdE26lv0iS1sFkkoWu22SdQvoflBpj1zQL9gmWh/BfxGerXNaI3y77wf4 iqQYxo1TehSnpXLiapxB8TCLIMa9Bnijr6YXCml1Z3RNt/Hc48z2oViezLlYiw2/ nDyOLndmxjUb0zYJtSt2vpPPp23hB29kJEAO0I6GnclYwaUZi30lmnFIUNrfFT2O 0D/QDDOFWbGvIaCHTZAVEdwZGmO7udVr6xWh+3GEwlXR30kJdWpABw2STBZP60CZ cfAzLd6n8NVB/7fL5KWZ3pfJhc5wXo7lgPM95CIhYmYW+gNBwvikAw+BagxVE5fr AqxNYZ8qQtoDaVe1bCbfuCg4/mvOg5y5Q8dNv/atzfTY1LCHPVvi5VFKjnqnZpQr 1CCi4xym6u26+O+tfqPh =2a66 -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/e1wjoyk-0002cg...@franck.debian.org
Bug#296629: mklibs: automatically include /etc/ld.so.conf paths
Hi dann, dann frazier (2005-02-23): > Package: mklibs > Version: 0.1.15 > Severity: normal > > If a required library is in a path referenced in /etc/ld.so.conf, but its > a non-typical path such as /usr/kerberos/lib, mklibs will fail to find it. > > I'd like to see mklibs parse ld.so.conf do you (still) think time should be spent in that area? Mraw, KiBi. signature.asc Description: Digital signature
Bug#562906: mklibs: fails on libc on hurd-i386
Samuel Thibault (2014-02-22): > You missed this part of what I wrote: > > “the simple solution would be to have libc*-pic provide > /usr/lib/libc-pic/shlib.lds” > > libc*-pic don't provide that shlib.lds script yet. Are you going to patch eglibc for that? IOW: is there anything actionable on the mklibs side? Mraw, KiBi. signature.asc Description: Digital signature
Bug#562906: mklibs: fails on libc on hurd-i386
Cyril Brulebois, le Sat 01 Mar 2014 20:05:09 +0100, a écrit : > Samuel Thibault (2014-02-22): > > You missed this part of what I wrote: > > > > “the simple solution would be to have libc*-pic provide > > /usr/lib/libc-pic/shlib.lds” > > > > libc*-pic don't provide that shlib.lds script yet. > > Are you going to patch eglibc for that? When I get time to work on it, yes. > IOW: is there anything actionable on the mklibs side? Not yet, unless it is decided to use another simple solution. The interim was to just use mklibs-copy in d-i for now. Samuel -- 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/20140301190815.GU5727@type
Bug#224073: marked as done (mklibs: reports broken libraries very ugly)
Your message dated Sat, 1 Mar 2014 20:12:36 +0100 with message-id <20140301191236.ga23...@mraw.org> and subject line Re: Bug#224073: mklibs: reports broken libraries very ugly has caused the Debian Bug report #224073, regarding mklibs: reports broken libraries very ugly 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.) -- 224073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=224073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mklibs Tags: patch On Mon, Dec 15, 2003 at 06:02:35PM +0100, Bill Allombert wrote: in a posting on debian-boot > > md@wonderland:/USR3/src/P/ppp/ppp-2.4.2+20031127$head -3 > > debian/ppp-udeb.postinst > > #!/bin/sh -e > > echo " $0 DISABLED "; exit 0 > > Oh, I well-know that. I use a modified version. My problem is I cannot > manage to properly load the udeb in d-i. > > After udpkg -i ppp-udeb.deb, I cannot find the postinst anywhere > and it is not run. > > I tried to rebuild d-i with ppp-udeb.deb in the local-udeb but it > do not build anymore: > > 461 symbols, 375 unresolved > Traceback (most recent call last): > File "/usr/bin/mklibs", line 469, in ? > raise "No library provides non-weak " + symbol > No library provides non-weak devnam > We, debian installer system team, have seen this before. At http://lists.debian.org/debian-boot/2003/debian-boot-200311/msg00925.html is a patch submitted. Cheers, Geert Stappers --- End Message --- --- Begin Message --- Geert Stappers (2003-12-15): > We, debian installer system team, have seen this before. > > At http://lists.debian.org/debian-boot/2003/debian-boot-200311/msg00925.html > is a patch submitted. I'm not sure what's wrong with raising an exception, so I'll just close this bug report for the time being. [ It needed a fix for a new python version back in the days: commit b28ced04c6c571ddc9ad0e80b004b37b196d6972 Author: Bastian Blank Date: Wed Nov 24 12:07:46 2010 + * debian/changelog: Update. * src/mklibs: Use explicit exceptions. r65770 but nothing dramatic. ] Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#698007: mklibs: Fix undefined reference to __dso_handle problem encountered with librt.so
Christian PERRIER (2013-01-12): > - Forwarded message from Joe Seymour - > > Date: Sat, 12 Jan 2013 13:13:56 + > From: Joe Seymour > To: debian-boot@lists.debian.org > Subject: [PATCH] Fix undefined reference to __dso_handle problem encountered > with librt.so > X-Mailing-List: archive/latest/170862 > X-CRM114-Status: Good ( pR: 18.8078 ) > > [Please CC me on any responses] > > When using mklibs on a simple test application I encountered the following > error > when mklibs attempts to build a reduced librt.so: > > /usr/lib64/libpthread_nonshared.a(pthread_atfork.oS): relocation R_X86_64_PC32 > against undefined hidden symbol `__dso_handle' can not be used when making a > shared object > ld: final link failed: Bad value > > Examining the link map for librt.so, when built by EGLIBC, I see the > __dso_handle definition used by it comes from crtbeginS.o, which isn't > included > in the link because mklibs passes -nostartfiles. > > In order to create a reduced librt.so that as closely as possible resembles > the > original, it makes sense to include crtbeginS.o when dealing with librt.so.1. > This patch does that. crtendS.o is included as a requisite of crtbeginS.o. In a sid chroot I'm getting this, which looks to me like there's no big issue with librt.so.1? (sid-amd64-devel)kibi@wodi:~/debian-installer/installer/build$ for i in $(find tmp/netboot-gtk/tree/ -type f); do if objdump -x $i 2>/dev/null|grep NEEDED|grep -qs librt.so.1; then echo $i; fi; done tmp/netboot-gtk/tree/sbin/rdnssd tmp/netboot-gtk/tree/lib/x86_64-linux-gnu/libudev.so.1.3.5 tmp/netboot-gtk/tree/lib/systemd/systemd-udevd tmp/netboot-gtk/tree/lib/libudev.so.1 tmp/netboot-gtk/tree/lib/udev/ata_id tmp/netboot-gtk/tree/lib/udev/scsi_id tmp/netboot-gtk/tree/lib/udev/cdrom_id tmp/netboot-gtk/tree/usr/lib/libcairo.so.2.11200.16 tmp/netboot-gtk/tree/usr/lib/libasound.so.2.0.0 tmp/netboot-gtk/tree/usr/bin/espeakup tmp/netboot-gtk/tree/bin/udevadm tmp/netboot-gtk/tree/bin/rdisc6 If you're still having any issues with it, it would be nice to describe a complete test case. Mraw, KiBi. signature.asc Description: Digital signature
Bug#698007: marked as done (mklibs: Fix undefined reference to __dso_handle problem encountered with librt.so)
Your message dated Sat, 1 Mar 2014 20:23:40 +0100
with message-id <20140301192340.gg28...@mraw.org>
and subject line Re: Bug#698007: mklibs: Fix undefined reference to
__dso_handle problem encountered with librt.so
has caused the Debian Bug report #698007,
regarding mklibs: Fix undefined reference to __dso_handle problem encountered
with librt.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.)
--
698007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mklibs
Tags: patch
- Forwarded message from Joe Seymour -
Date: Sat, 12 Jan 2013 13:13:56 +
From: Joe Seymour
To: debian-boot@lists.debian.org
Subject: [PATCH] Fix undefined reference to __dso_handle problem encountered
with librt.so
X-Mailing-List: archive/latest/170862
X-CRM114-Status: Good ( pR: 18.8078 )
[Please CC me on any responses]
When using mklibs on a simple test application I encountered the following error
when mklibs attempts to build a reduced librt.so:
/usr/lib64/libpthread_nonshared.a(pthread_atfork.oS): relocation R_X86_64_PC32
against undefined hidden symbol `__dso_handle' can not be used when making a
shared object
ld: final link failed: Bad value
Examining the link map for librt.so, when built by EGLIBC, I see the
__dso_handle definition used by it comes from crtbeginS.o, which isn't included
in the link because mklibs passes -nostartfiles.
In order to create a reduced librt.so that as closely as possible resembles the
original, it makes sense to include crtbeginS.o when dealing with librt.so.1.
This patch does that. crtendS.o is included as a requisite of crtbeginS.o.
Joe
diff --git a/src/mklibs b/src/mklibs
index 14ca02a..0b62136 100755
--- a/src/mklibs
+++ b/src/mklibs
@@ -617,6 +617,17 @@ while 1:
extra_post_obj.append(sysroot + libc_extras_dir + "/sofini.o")
symbols.add(ProvidedSymbol('__dso_handle', None, None, True))
+if soname in ("librt.so.1"):
+crtbegin = command(target + "gcc",
+ " ".join(gcc_options),
+ "-print-file-name=crtbeginS.o");
+crtend = command(target + "gcc",
+ " ".join(gcc_options),
+ "-print-file-name=crtendS.o");
+extra_pre_obj.append(" ".join(crtbegin))
+extra_post_obj.append(" ".join(crtend))
+symbols.add(ProvidedSymbol('__dso_handle', None, None, True))
+
map_file = find_pic_map(library)
if map_file:
extra_flags.append("-Wl,--version-script=" + map_file)
--
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/50f16194.2090...@codesourcery.com
- End forwarded message -
--
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Cyril Brulebois (2014-03-01):
> If you're still having any issues with it, it would be nice to describe
> a complete test case.
jseym...@codesourcery.com
SMTP error from remote mail server after pipelined DATA:
host mx0a-0013c101.pphosted.com [208.84.65.186]:
550 5.1.1 User Unknown
So closing…
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
Re: Bug#740330: dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13-1-amd64_3.13.4-1_amd64.deb (--unpack): (no space left) ошибка создания каталога
control: reassign -1 partman-auto control: retitle -1 root-fs should be larger Hi, summary: On Freitag, 28. Februar 2014, Andrey E. Polevoy wrote: > First instal wheezy (root FS is 315M), upgrade to jessie and later to sid > (root FS is still 315M): (no space left on root filesystem) > > dpkg: error processing archive > /var/cache/apt/archives/linux-image-3.13-1-amd64_3.13.4-1_amd64.deb > (--unpack): (no space left) > /dev/sda1 315M 221M 74M 75% / > /dev/sda9 276G 64M 262G1% /home so the disk is clerly large enough, so IMO the root fs should be 8,2G like /usr or as well. Or at least 2,7G: > /dev/sda5 8,2G 692M 7,1G9% /usr > /dev/sda6 2,7G 1,3G 1,3G 51% /var > > Partition the disks were produced in automatic mode (wheezy installer with > separate partitions for / /home /var /usr /tmp filesystems) cheers, Holger signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#673644: Message at end of successful install talks about floppies (should be updated)
Processing control commands: > tag -1 patch Bug #673644 [finish-install] Message at end of successful install talks about floppies (should be updated) Added tag(s) patch. -- 673644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673644 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.b673644.139370796412763.transcr...@bugs.debian.org
Bug#673644: Message at end of successful install talks about floppies (should be updated)
Control: tag -1 patch Wookey (2012-05-20): > Package: debian-installer > Version: wheezy alpha > Severity: minor > Tags: d-i > > At the end of a successful install you get the 'installation complete' > message: "installation is complete, so it is time to boot into your > new system. Make sure to remove the installatio media (CD-ROM, > floppies), ..." > > I suggest that be updated to (DVD, USB drive, CD) or something. Thanks for the report; I guess the attached patch should do the job? Christian, if this doc is still current, templates.pot && *.po are getting updated through the l10n bot and I don't need to do more than patch the templates file? http://d-i.alioth.debian.org/doc/i18n/ch02s04.html I suspect translators are automatically mailed as well, so I don't need to worry about either debconf-updatepo or podebconf-report-po? Sorry for all the questions, I think that's my first templates update… An ACK on the patch itself would be appreciated as well. Mraw, KiBi. From c21fb08c2a1cc3378524ecab50a94997764fee5f Mon Sep 17 00:00:00 2001 From: Cyril Brulebois Date: Sat, 1 Mar 2014 21:26:54 +0100 Subject: [PATCH] Update templates to list CD-ROM, DVD-ROM, USB flash disk instead of CD-ROM and floppies (Closes: #673644). --- debian/changelog| 7 +++ debian/finish-install.templates | 5 +++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index 204d771..baa2bdd 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +finish-install (2.47) UNRELEASED; urgency=low + + * Update templates to list CD-ROM, DVD-ROM, USB flash disk instead of +CD-ROM and floppies (Closes: #673644). + + -- Cyril Brulebois Sat, 01 Mar 2014 21:25:33 +0100 + finish-install (2.46) unstable; urgency=low [ Updated translations ] diff --git a/debian/finish-install.templates b/debian/finish-install.templates index e60ddb2..0371b42 100644 --- a/debian/finish-install.templates +++ b/debian/finish-install.templates @@ -39,8 +39,9 @@ Type: note # :sl1: _Description: Installation complete Installation is complete, so it is time to boot into your new system. - Make sure to remove the installation media (CD-ROM, floppies), so that - you boot into the new system rather than restarting the installation. + Make sure to remove the installation media (CD-ROM, DVD-ROM, USB flash + disk), so that you boot into the new system rather than restarting the + installation. Template: finish-install/keep-consoles Type: boolean -- 1.9.0 signature.asc Description: Digital signature
Processed: Re: Bug#740330: dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13-1-amd64_3.13.4-1_amd64.deb (--unpack): (no space left) ошибка создания каталога
Processing control commands: > reassign -1 partman-auto Bug #740330 [base] dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13-1-amd64_3.13.4-1_amd64.deb (--unpack): (no space left) ошибка создания каталога Bug reassigned from package 'base' to 'partman-auto'. Ignoring request to alter found versions of bug #740330 to the same values previously set Ignoring request to alter fixed versions of bug #740330 to the same values previously set > retitle -1 root-fs should be larger Bug #740330 [partman-auto] dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13-1-amd64_3.13.4-1_amd64.deb (--unpack): (no space left) ошибка создания каталога Changed Bug title to 'root-fs should be larger' from 'dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13-1-amd64_3.13.4-1_amd64.deb (--unpack): (no space left) ошибка создания каталога' -- 740330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740330 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.b740330.139370798113031.transcr...@bugs.debian.org
Bug#541831: marked as done (installation-reports: Sunfire T2000 success (one minor issue))
Your message dated Sat, 1 Mar 2014 22:58:36 +0100 with message-id <20140301215836.ga10...@mraw.org> and subject line Re: Bug#541831: installation-reports: Sunfire T2000 success (one minor issue) has caused the Debian Bug report #541831, regarding installation-reports: Sunfire T2000 success (one minor issue) 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.) -- 541831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal -- Package-specific info: Boot method: network Image version: http://ftp.nl.debian.org/debian/dists/lenny/main/installer-sparc/current/images/netboot/boot.img Date: 2009-08-15 Machine: Sun Sunfire T2000 Partitions: sgran@zee:~$ df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/zeevg-root ext3 7688360 1008076 6289732 14% / tmpfstmpfs16563896 0 16563896 0% /lib/init/rw udev tmpfs 10240 152 10088 2% /dev tmpfstmpfs16563896 0 16563896 0% /dev/shm /dev/sda1 ext3 186667 16120160909 10% /boot /dev/mapper/zeevg-home ext3 9611492152704 8970548 2% /home /dev/mapper/zeevg-srv ext328834812176196 28658616 1% /srv sgran@zee:~$ sudo fdisk -l Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sda (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sda1 0241927801 Boot /dev/sda224 8924 71489250 fd Linux raid autodetect /dev/sda3 0 8924 716820305 Whole disk Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sda1 (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sda1p1 0241927801 Boot /dev/sda1p224 8924 71489250 fd Linux raid autodetect /dev/sda1p3 0 8924 716820305 Whole disk Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sda3 (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sda3p1 0241927801 Boot /dev/sda3p224 8924 71489250 fd Linux raid autodetect /dev/sda3p3 0 8924 716820305 Whole disk Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sdb (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sdb1 024192780 83 Linux native /dev/sdb224 8924 71489250 fd Linux raid autodetect /dev/sdb3 0 8924 716820305 Whole disk Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sdb1 (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sdb1p1 024192780 83 Linux native /dev/sdb1p224 8924 71489250 fd Linux raid autodetect /dev/sdb1p3 0 8924 716820305 Whole disk Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need
Processed: found 673644 in 2.41wheezy1
Processing commands for cont...@bugs.debian.org: > # not sure we will want to try and get stable fixed once translations are > updated… > found 673644 2.41wheezy1 Bug #673644 [finish-install] Message at end of successful install talks about floppies (should be updated) Marked as found in versions finish-install/2.41wheezy1. > thanks Stopping processing here. Please contact me if you need assistance. -- 673644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673644 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.13937114224430.transcr...@bugs.debian.org
Bug#691366: marked as done (wheezy 2012-10-24 daily built netinst)
Your message dated Sat, 1 Mar 2014 23:16:47 +0100 with message-id <20140301221647.ga12...@mraw.org> and subject line Re: Bug#691366: wheezy 2012-10-24 daily built netinst has caused the Debian Bug report #691366, regarding wheezy 2012-10-24 daily built netinst to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 691366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-report Severity: important Hi, prelude: this is an installation report about things that were odd or did not work. Please keep in mind that Debian is (used to be?) a great distribution and the Debian developers do a lot of great work! I downloaded a "testing" daily built netinst from Oct 24 for amd64 (CPU is a 64-bit i7). Yet I have always used daily or weekly testing builds to install Debian GNU/Linux on my machines without major problems. However, it has been a long time ...and times seem to have changed. Let's start chronologically. I describe some oddities in different stages. The worst stuff comes in the end. IMHO the current wheezy beta distribution turns out to be unusable for the broad audience of GNOME or KDE desktop users. Oddities in debian-installer: (I decided to choose the graphical installer but I think there is no real difference to the text-mode installer.) 1. Internationalization debian-installer asked me for my location. A list with seemingly randomly chosen countries was offered. Although Germany is a big country and many Debian users are from Germany, Germany was not on the list. No problem: other -> Europe -> Germany. Everything's fine. The following question for the keyboard layout and locales was fine to me: *I* want English/US locales and the standard US keyboard layout, but I nevertheless was confused why I was asked for my location before. debian-installer did not get the idea that a preselection for German locales and keyboard layout could make sense. (I remember that this has been different in previous versions.) 2. Partitioning Later it was time to partition. Well, I could have reused the partition table from the user that installed Ubuntu before. However, I wanted to use LVM, so I thought it is nice that there are predefined partition schemes, like LVM with a root, /home and swap partition (and a /boot partition outside LVM). I used this and it offered me something like: - 300 MB /boot - LVM: - home 472.5 GB - root 10.0 GB - swap 17.2 GB Nice try. But I do not need 17.2 GB swap and I could indeed need more than 10.0 GB for the root partition. Sure, but how can I change this? I was unable to change anything. I remember that it has been possible before by clicking on a partition but when I did this I could only - change the file system, formatting options and mount point - copy data on the partition - erase data from the partition and NOT remove the partition or change size of the partition (removal would have sufficed). Damn! However, I thought, not that bad - it's LVM! - I can fix the settings afterwards... so I continued... Later I reinstalled the whole thing in expert mode where I added "cfdisk" and "parted" modules to the debian-installer. I still was not able to change the partition table according to my needs; there was no cfdisk or parted partitioning tool in the debian-installer menu, only the broken partman thingie... (Of course I would have been able by activating a console and starting cfdisk or parted, but it should be easily possible using the debian-installer. I hope everyone agrees.) 3. Selection of packages After installing the base system, the netinst debian-installer offered me an interesting bunch of "categories" to install like: "[X] Debian Desktop environment" -- wait, I thought I could choose between KDE, LXDE, Xfce and GNOME?! The Debian website told me so! Mh, perhaps I can choose afterwards... "[ ] Web server" "[ ] Mail server" "[X] Print server" -- wait! Why is this preselected? Does the typical Debian user really set up print servers? ... "[X] SSH server" -- wait?! Why is this a category? Of course, I want openssh-server to be installed, who doesn't? I mean: _who_ doesn't? and so on. I deselected the Print server and continued. And, damn, no question about the Desktop environment. It just installed Gnome. Disappointing. On the other side ...I was a little happy about this because I did not have to decide if I want to use a broken GNOME 3 or a broken KDE 4. And, hey, I could easily switch in Debian if it turns out that GNOME
Bug#606110: installation-report: gtk installer fail to start with PXE boot of Dell Latitude D505
Control: tag -1 moreinfo Petter Reinholdtsen (2010-12-06): > Package: installation-report > > I just tested a PXE installation on a Dell Latitude D505 of the > squeeze based d-i downloaded from > http://ftp.no.debian.org/debian/dists/squeeze/main/installer-i386/current/images/netboot/gtk/debian-installer/i386/. > The installer failed to start and the screen went black when X was > supposed to start. > > This was the pxelinux configuration used: > > LABEL edu-squeeze-i386-kde > MENU LABEL Debian Edu/Squeeze (KDE) > kernel neteduboot/squeeze/linux > append initrd=neteduboot/squeeze/initrd.gz > "url=http://ftp.skolelinux.org/installer-squeeze.dat"; desktop=kde > hostname=pxelinux domain=intern debug video=vesa:ywrap,mtrr > > The machine in question had a problem earlier with the kernel and X > because of a bug related to the X.org intel driver. See bug #599927 > for the details about that issue. Details about the hardware is > available in this bug. > > I lack the hardware to get a serial console on the machine, and the > skills and knowledge to get a network console, and thus am a but > unsure how to debug this. The installer crashes very early, before I > have any chance to get in and try to figure out what is going on. > > The text installer work just fine, and the machine is installing now > using the latest text installer. If you still have access to this machine, does the wheezy gtk installer start fine? Otherwise, lacking access to such a machine, I'm tempted to close this bug report. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#606110: installation-report: gtk installer fail to start with PXE boot of Dell Latitude D505
Processing control commands: > tag -1 moreinfo Bug #606110 [installation-report] installation-report: gtk installer fail to start with PXE boot of Dell Latitude D505 Added tag(s) moreinfo. -- 606110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606110 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.b606110.139371242210050.transcr...@bugs.debian.org
Bug#734756: Install failed
Control: reassign -1 installation-reports Control: tag -1 moreinfo John S. Hart (2014-01-09): > Package: installation-reports Boot method: CD > Image version: debian-3.1.0-1-486 Can you please tell us which URL you use to download your installation image? The above version looks rather strange to me. Mraw, KiBi. (Andrei, Holger: that's installation-report*s*; see the list of pseudo packages on the BTS: https://www.debian.org/Bugs/pseudo-packages) signature.asc Description: Digital signature
Processed: Re: Bug#734756: Install failed
Processing control commands: > reassign -1 installation-reports Bug #734756 [installation-report] Install failed Bug reassigned from package 'installation-report' to 'installation-reports'. Ignoring request to alter found versions of bug #734756 to the same values previously set Ignoring request to alter fixed versions of bug #734756 to the same values previously set > tag -1 moreinfo Bug #734756 [installation-reports] Install failed Added tag(s) moreinfo. -- 734756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734756 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.b734756.139371277012795.transcr...@bugs.debian.org
Bug#393987: save-logs: Add acpidump to report-hw?
Kurt Roeckx (2006-10-18): > We now have an acpidump in Debian. It might be useful if report-hw > could also dump that information, in case of problems with acpi. > > The package is rather small. On amd64 we have: > > Package: acpidump > Installed-Size: 72 > Size: 11322 > > -rwxr-xr-x 1 root root 11184 Aug 22 19:38 /usr/bin/acpidump > > It's available on i386 ia64 and amd64. It's apparently an arch:all package now, pulling acpica-tools from src:acpica-unix, which apparently built everywhere. I haven't played with it, so can't tell whether we want to include that into installation-report. Mraw, KiBi. signature.asc Description: Digital signature
Bug#740465: installation-report: consider including Xorg.0.log
Source: installation-report Version: 2.54 Severity: normal I've just gotten rid of some last DirectFB bits: http://anonscm.debian.org/gitweb/?p=d-i/installation-report.git;a=commitdiff;h=00ef09f I'm not sure we want to include Xorg.0.log instead. If X doesn't work, users are likely not going to be able to reach the end of the installation process; if it does, we don't need the log. I'm happy to take any comments on this topic. Mraw, KiBi. -- 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/20140301224315.16974.91292.reportbug@arya
Processed: Re: Bug#684777: installation-report: Install of kfreebsd-i386 failed in VirtualBox
Processing control commands: > reassign -1 installation-reports Bug #684777 [installation-report] installation-report: Install of kfreebsd-i386 failed in VirtualBox Bug reassigned from package 'installation-report' to 'installation-reports'. Ignoring request to alter found versions of bug #684777 to the same values previously set Ignoring request to alter fixed versions of bug #684777 to the same values previously set > tag -1 moreinfo Bug #684777 [installation-reports] installation-report: Install of kfreebsd-i386 failed in VirtualBox Added tag(s) moreinfo. -- 684777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684777 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.b684777.139371505725536.transcr...@bugs.debian.org
Bug#684777: installation-report: Install of kfreebsd-i386 failed in VirtualBox
Control: reassign -1 installation-reports Control: tag -1 moreinfo Valentin Lorentz (2012-08-13): > Boot method: netinstall > Image version: debian-wheezy-DI-b1-kfreebsd-i386-netinst.iso > Date: 2012-08-13 19:31 +0002 > > Machine: VirtualBox (on Debian GNU/Linux Sid amd64) > Processor: > Memory: > Partitions: automated install: /, /home, /var, ... separated > > Output of lspci -knn (or lspci -nn): > > Base System Installation Checklist: > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it > > Initial boot: [O] > Detect network card:[O] > Configure network: [E] > Detect CD: [O] > Load installer modules: [O] > Detect hard drives: [E] > Partition hard drives: [O] > Install base system:[O] > Clock/timezone setup: [ ] > User/password setup:[O] > Install tasks: [O] > Install boot loader:[E] > Overall install:[E] > > Comments/Problems: > > Cannot connect to my network, either automatically (does not connect to > DHCP server) or manually (no connection, cannot ping it from another > machine). I tried both "bridge" and "NAT" modes. > Running ifconfig is the installer shell prints (after I select > VirtualBox's bridge networking and manual configuration of the network): > pcn0: flags=8843 metric 0 mtu > 1500 > option=8 > ether 8:0:27:65:4d > inet6 [my IP here] prefixlen 64 scopeid 0x1 > inet 192.168.1.159 netmask 0xff00 broadcast 192.168.1.255 > media: Ethernet none > status: active > nd6 options=23 > > When detecting hard drives, I got this message: > Could not get identity of device /dev/ada0 - Inapropriate ioctl for > device > I selected "ignore", and it passed. > > GRUB installed failed: "package grub-pc could not be installed > in /target/". > /var/log/syslog contains errors of dpkg and/or aptitude, telling no > version of package grub-common is available, even if it has been found > in the database. Hi, and thanks for your report. Did you have better luck with the released wheezy installation images? Mraw, KiBi. signature.asc Description: Digital signature
Bug#384067: marked as done (the average user can't tell the difference between "English" and "C")
Your message dated Sun, 2 Mar 2014 00:11:21 +0100 with message-id <20140301231121.ga20...@mraw.org> and subject line Re: Bug#384067: the average user can't tell the difference between "English" and "C" has caused the Debian Bug report #384067, regarding the average user can't tell the difference between "English" and "C" 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.) -- 384067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: localechooser Severity: normal AFAIK, the "C" option is only useful for debugging. The average English user can't tell the difference between selecting "English" and selecting "C". I think it can be confusing. Could you make "C" disappear for a priority < high ? (perhaps the easiest way to do this is add a previous question asking wether user wants any localization at all). This wasn't much of a problem with console installs, because "C" doesn't appear in the default screen (you have to scroll up), but in GUI installs, "C" is one of the most prominent options. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) --- End Message --- --- Begin Message --- Christian Perrier (2006-08-21): > Quoting Robert Millan (r...@aybabtu.com): > > Package: localechooser > > Severity: normal > > > > AFAIK, the "C" option is only useful for debugging. The average English > > user > > Nope. Some users do *not* want the packages pulled in by "English" > (mostly locales and some -en packages when using the desktop task).) > > > can't tell the difference between selecting "English" and selecting "C". I > > "C - No localization" > > I really fail to see why users would be confused by this. The "C" > option is very clearly meant for users that do not want localization > at all. I don't know how to say this more clearly. > > The average user will jump on the language (s)he uses and I really > doubt (s)he would be confused. Especially since the default entry is… “English”. No need to keep that bug report open forever, closing. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#384510: marked as done (localechooser: Please use official country names)
Your message dated Sun, 2 Mar 2014 00:16:39 +0100 with message-id <20140301231639.ga21...@mraw.org> and subject line Re: Bug#384510: localechooser: Please use official country names has caused the Debian Bug report #384510, regarding localechooser: Please use official country names 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.) -- 384510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: localechooser Severity: minor (This refers to the version of localechooser from d-i beta 3) Hi, I wonder why you do not use the official country names. So I found for example "Macedonia, Republic of" whereas the offical name (according to comments in the PO file) is "The Former Yugoslav Republic of Macedonia". I noticed this because nearly all country names are of the form "Republic of XYZ", but "Moldova, Republic of" and "Macedonia, Republic of" do not match this pattern. Jens --- End Message --- --- Begin Message --- Christian Perrier (2006-08-25): > tags 384510 wontfix > thanks Let's close this old bug report; no need to keep it around. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#610943: marked as done (Add en_DK locale)
Your message dated Sun, 2 Mar 2014 00:19:07 +0100 with message-id <20140301231907.ga14...@mraw.org> and subject line Closing en_DK bug reports has caused the Debian Bug report #610943, regarding Add en_DK locale 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.) -- 610943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Boot method: CD - netinstaller Image version: Squeeze RC2, build date 22 Jan, 2011 - http://cdimage.debian.org/cdimage/squeeze_di_rc2/i386/iso-cd/debian-squeeze-di-rc2-i386-netinst.iso Date: 23 / 01 - 2011. 7 PM, danish time. Machine: HP Elitebook 6930P Processor: Memory: Partitions: sda1 = NTFS (win7), sda2 = /, sda3 = swap, sda4 = /home Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ O] Detect network card:[O ] 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:[ E] Comments/Problems: After the installation is done, and the first reboot, the following message shows, before it evens load grub. Grub is installed to the MBR and detects Win7 fine (as a Vista boot loader though). "non-system disk or disk error replace and strike any key when ready" It does not matter if I set the / with a boot flag or not. Same error. Only problem during the installation, was I could not select the Danish keyboard layout. Only when I selected United States / America, it showed. So there is still a bug here. --- End Message --- --- Begin Message --- They've been tagged wontfix for a long while, no need to keep them around. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#595783: marked as done (debian-installer: en_DK locale missing)
Your message dated Sun, 2 Mar 2014 00:19:07 +0100 with message-id <20140301231907.ga14...@mraw.org> and subject line Closing en_DK bug reports has caused the Debian Bug report #595783, regarding debian-installer: en_DK locale missing 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.) -- 595783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: normal I have customarily been using en_DK as my default locale because I want my system to speak English to me but units, dates etc to be sane for mainland Europe. Now when I tried to install Debian Testing, I noticed that en_DK is not available as an option during installation. While I fully agree that en_DK is technically whimsical, it has been a good locale to have; none of the en_XX options available in the installer seem to offer the same features (A4 paper size, year-month-date date format, metric units, etc) which are useful for a large part of Europe in multinational organizations which use English as their main language. I installed using the netinst squeeze image from http://www.debian.org/devel/debian-installer/ -rw-r--r-- 1 era era 168742912 2010-02-18 00:19 debian-testing-i386-netinst.iso Once the system was properly installed, the locales package (2.11.2-2) did include en_DK, but it was not available during installation. /* era */ -- If this were a real .signature, it would suck less. Well, maybe not. --- End Message --- --- Begin Message --- They've been tagged wontfix for a long while, no need to keep them around. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#740073: Info received (Bug#740073: netinst hangs on scanning CD-ROM [was: Message with no Package: tag cannot be processed! (Installation report)])
Hello, Do you know that testing network installation image still doesn't work? It's NOT POSSIBLE to install 'jessie' anyhow. I don't believe that there is no man working on this problem... It's just not possible. Not in our universe. Thank you. P.S. We, users, believe in you, Developers. And we believe in Debian. Thank you once again.
Bug#469670: marked as done (not run early enough when in expert mode)
Your message dated Sun, 2 Mar 2014 00:21:12 +0100 with message-id <20140301232112.ga21...@mraw.org> and subject line Re: Bug#469670: not run early enough when in expert mode has caused the Debian Bug report #469670, regarding not run early enough when in expert mode 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.) -- 469670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: localechooser Version: 1.46 Severity: normal When in expert mode, localechooser is not run early enough, causing the first menu option to be displayed (global menu) not to be localised, even if locale was being preseeded. The typical situation in which this happens is when using win32-loader: - User selects a language other than English (win32-loader needs to ask this as its first question, and afterwards preseeds the reply). - User selects expert mode. - win32-loader boots D-I with priority=low and locale=something. -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) --- End Message --- --- Begin Message --- Frans Pop (2008-03-06): > tags 469670 wontfix > thanks > > Therefore tagging wontfix. Unless others disagree with this, this report can > closed at some point in the future. The future is now. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#714350: marked as done (FTBFS when locales-all is installed)
Your message dated Sun, 2 Mar 2014 00:25:53 +0100 with message-id <20140301232553.gb14...@mraw.org> and subject line Re: Bug#714350: FTBFS when locales-all is installed has caused the Debian Bug report #714350, regarding FTBFS when locales-all 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.) -- 714350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: localechooser Severity: 2.54 localechooser FTBFS if locales-all (which provides locales) is installed. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ --- End Message --- --- Begin Message --- Daniel Baumann (2013-06-28): > Package: localechooser > Severity: 2.54 > > localechooser FTBFS if locales-all (which provides locales) is installed. No, it does not; closing accordingly. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Processed: Re: Bug#630623: With PXE boot localechooser/langlist = C or English
Processing control commands: > tag -1 moreinfo Bug #630623 [localechooser] With PXE boot localechooser/langlist = C or English Added tag(s) moreinfo. -- 630623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630623 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.b630623.13937166002847.transcr...@bugs.debian.org
Bug#630623: With PXE boot localechooser/langlist = C or English
Control: tag -1 moreinfo Hi, pierre-gilles (2011-06-15): > Package: localechooser > Version: 2.34 > Severity: normal > Tags: d-i > > PXE boot failed on Dell R610 with language=fr locale=fr_FR.UTF8 > console-keymaps-at/keymap=fr-latin9 debian-installer/country=FR > the same options work fine with kvm-qemu virtual servers. > > localechooser/languagelist is only C or English so the prompt ask for > a valid locale. are you still experiencing issues with wheezy or above? If that works fine in kvm, you may want to check (e.g. in /proc/cmdline) that the command line isn't getting truncated or otherwise altered? Mraw, KiBi. signature.asc Description: Digital signature
Bug#426829: marked as done (localechooser: doesn't display AX (Åland Islands) nor CI (Côte d'Ivoire))
Your message dated Sun, 2 Mar 2014 00:36:53 +0100 with message-id <20140301233653.ga23...@mraw.org> and subject line Re: Bug#426829: localechooser: doesn't display AX (Åland Islands) nor CI (Côte d'Ivoire) has caused the Debian Bug report #426829, regarding localechooser: doesn't display AX (Åland Islands) nor CI (Côte d'Ivoire) 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.) -- 426829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: localechooser Version: 1.37 Severity: normal Localechooser doesn't display AX (Åland Islands) nor CI (Côte d'Ivoire) entries, presumably because their names contain non-US-ASCII characters. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 2.6.21 Locale: LANG=C, LC_CTYPE=pl_PL.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Version: 2.46 Piotr Engelking (2007-05-31): > Package: localechooser > Version: 1.37 > Severity: normal > > Localechooser doesn't display AX (Åland Islands) nor CI (Côte d'Ivoire) > entries, presumably because their names contain non-US-ASCII characters. Thanks for your report. It took some years, but that got fixed: | commit f25e64edc1b426b4feb837bce01f775238da1b0c | Author: Samuel Thibault | Date: Mon Sep 17 00:46:55 2012 +0200 | | Do not skip non-ASCII country names by telling gettext they are encoded in UTF-8 Commit: http://anonscm.debian.org/gitweb/?p=d-i/localechooser.git;a=commitdiff;h=f25e64edc1b426b4feb837bce01f775238da1b0c I've verified both AX (Europe zone) and CI (Africa zone) are present and displayed properly, both in text and graphical modes. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Re: Bug#740330: dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13-1-amd64_3.13.4-1_amd64.deb (--unpack): (no space left) ошибка создания каталога
On Sat, 2014-03-01 at 15:06 -0600, Holger Levsen wrote: > control: reassign -1 partman-auto > control: retitle -1 root-fs should be larger > > Hi, > > summary: > > On Freitag, 28. Februar 2014, Andrey E. Polevoy wrote: > > First instal wheezy (root FS is 315M), upgrade to jessie and later to sid > > (root FS is still 315M): (no space left on root filesystem) > > > > dpkg: error processing archive > > /var/cache/apt/archives/linux-image-3.13-1-amd64_3.13.4-1_amd64.deb > > (--unpack): (no space left) > > > /dev/sda1 315M 221M 74M 75% / > > /dev/sda9 276G 64M 262G1% /home > > so the disk is clerly large enough, so IMO the root fs should be 8,2G like > /usr or as well. Or at least 2,7G: The separate /usr is an historical accident, and we keep having to move files out of /usr because they might be needed before mounting it; that plus the inability to autoremove kernels probably explains why this upgrade filled up the partition. Rather than wasting lots of space on / we should stop creating separate / and /usr in any of the standard recipes. (We are supposed to start mounting /usr from the initramfs some time soon, but that's because we need to support upgrades. I don't think it's an argument in favour of creating a separate /usr now.) Ben. > > /dev/sda5 8,2G 692M 7,1G9% /usr > > /dev/sda6 2,7G 1,3G 1,3G 51% /var > > > > Partition the disks were produced in automatic mode (wheezy installer with > > separate partitions for / /home /var /usr /tmp filesystems) -- 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#247582: marked as done (main-menu must escape commas when collecting package titles)
Your message dated Sun, 2 Mar 2014 01:43:27 +0100 with message-id <20140302004303.ga30...@mraw.org> and subject line Re: Bug#247582: main-menu must escape commas when collecting package titles has caused the Debian Bug report #247582, regarding main-menu must escape commas when collecting package titles 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.) -- 247582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=247582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: main-menu Severity: normal If a package has a title Choose your foo, bar or baz main-menu does not escape its comma and thus this title is broken into 2 select items. Denis --- End Message --- --- Begin Message --- Denis Barbier (2004-05-05): > Package: main-menu > Severity: normal > > If a package has a title > Choose your foo, bar or baz > main-menu does not escape its comma and thus this title is broken > into 2 select items. I've patched localechooser to have this: | Template: localechooser/title/language | Type: title | Description: Select a, possibly fun, language and that's working fine, both with text and graphical modes. If you have a way to reproduce this nowadays, please reopen. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#462617: marked as done (debian-installer: need RAID bitmap support (mdadm -b internal))
Your message dated Sun, 2 Mar 2014 01:54:46 +0100 with message-id <20140302005446.ga32...@mraw.org> and subject line Re: Bug#462617: debian-installer: need RAID bitmap support (mdadm -b internal) has caused the Debian Bug report #462617, regarding debian-installer: need RAID bitmap support (mdadm -b internal) 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.) -- 462617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: normal A recent (some time in the last 5 years) feature of Linux software RAID is a "write intent bitmap". The purpose of this is that before writing to a section of disk the bitmap is altered to mark it as dirty. Then if the machine experiences a power failure or other catastrophic event then when rebooted it will know that the section referenced by that bit is dirty. Thus on reboot after a serious failure small amounts of data will be synchronised instead of large amounts. This feature is not currently used by the Debian installer. So if you install to a system with multiple disks in a RAID-1 array (and probably RAID-5 and RAID-6) then every time there is a power failure the disks in the RAID will have to be completely read to ensure that they match. If the mdadm command that was used for the Debian installer had "-b internal" appended then the bitmap feature would be used and recovery from some failure conditions would be much faster. There does not seem to be any down-side to using this. I have not tested this with RAID-5 and RAID-6, but have tested the benefits of this option for RAID-1 and found it to be very useful. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) --- End Message --- --- Begin Message --- Russell Coker (2008-01-26): > A recent (some time in the last 5 years) feature of Linux software > RAID is a "write intent bitmap". The purpose of this is that before > writing to a section of disk the bitmap is altered to mark it as > dirty. Then if the machine experiences a power failure or other > catastrophic event then when rebooted it will know that the section > referenced by that bit is dirty. > > Thus on reboot after a serious failure small amounts of data will be > synchronised instead of large amounts. > > This feature is not currently used by the Debian installer. So if you > install to a system with multiple disks in a RAID-1 array (and > probably RAID-5 and RAID-6) then every time there is a power failure > the disks in the RAID will have to be completely read to ensure that > they match. > > If the mdadm command that was used for the Debian installer had "-b > internal" appended then the bitmap feature would be used and recovery > from some failure conditions would be much faster. There does not > seem to be any down-side to using this. > > I have not tested this with RAID-5 and RAID-6, but have tested the > benefits of this option for RAID-1 and found it to be very useful. The subject reminded me of some digging I've done lately to answer someone on #debian-boot. Pasting the IRC log, anonymizing the user nickname just in case: 2014-02-14 22:11:41[ ] do the d-i daily's automatically add write intent bitmaps to raid arrays created in the installer? 2014-02-14 22:12:11[ KiBi] I don't know what those are. 2014-02-14 22:12:18[ ] I think they must, a system I just installed has them. if anyone knows more details I would love to discuss 2014-02-14 22:12:55[ ] hmm, damn my notes on them aren't public 2014-02-14 22:13:17[ ] they are a small bitmap file that corresponds to chunks of the raid array 2014-02-14 22:13:33[ ] before the kernel goes to write to a chunk it sets the bit 2014-02-14 22:13:54[ KiBi] so maybe partman-auto-raid is the package you want to look at? 2014-02-14 22:14:12[ ] so if a system loses power, when it comes back up it only needs to resync the chunks that were actively being written to 2014-02-14 22:14:15[ ] really nice 2014-02-14 22:14:36[ KiBi] unless the code for it is elsewhere, maybe on the kernel side? 2014-02-14 22:14:59[ ] you can store them on other disks too in order to prevent the heads of a HDD needing to seek a lot 2014-02-14 22:15:07[ KiBi] ah, mdadm apparently: https://raid.wiki.kernel.org/index.php/Write-intent_bitmap 2014-02-14 22:15:15[ ]
Bug#616723: marked as done (Add support for bitmap option of md device)
Your message dated Sun, 2 Mar 2014 01:54:46 +0100 with message-id <20140302005446.ga32...@mraw.org> and subject line Re: Bug#462617: debian-installer: need RAID bitmap support (mdadm -b internal) has caused the Debian Bug report #462617, regarding Add support for bitmap option of md device 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.) -- 462617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: whishlist Tags: d-i Latest debian installer on Squeeze Iso disk debian-6.0.0-amd64-BD-1.iso used to install new computer. At the level of creating md devices it is not possible to add an bitmap as I can do with --bitmap=internal. Please add (for me internal is good enough ;-). -- System Information: Debian Release: 6.0 Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Russell Coker (2008-01-26): > A recent (some time in the last 5 years) feature of Linux software > RAID is a "write intent bitmap". The purpose of this is that before > writing to a section of disk the bitmap is altered to mark it as > dirty. Then if the machine experiences a power failure or other > catastrophic event then when rebooted it will know that the section > referenced by that bit is dirty. > > Thus on reboot after a serious failure small amounts of data will be > synchronised instead of large amounts. > > This feature is not currently used by the Debian installer. So if you > install to a system with multiple disks in a RAID-1 array (and > probably RAID-5 and RAID-6) then every time there is a power failure > the disks in the RAID will have to be completely read to ensure that > they match. > > If the mdadm command that was used for the Debian installer had "-b > internal" appended then the bitmap feature would be used and recovery > from some failure conditions would be much faster. There does not > seem to be any down-side to using this. > > I have not tested this with RAID-5 and RAID-6, but have tested the > benefits of this option for RAID-1 and found it to be very useful. The subject reminded me of some digging I've done lately to answer someone on #debian-boot. Pasting the IRC log, anonymizing the user nickname just in case: 2014-02-14 22:11:41[ ] do the d-i daily's automatically add write intent bitmaps to raid arrays created in the installer? 2014-02-14 22:12:11[ KiBi] I don't know what those are. 2014-02-14 22:12:18[ ] I think they must, a system I just installed has them. if anyone knows more details I would love to discuss 2014-02-14 22:12:55[ ] hmm, damn my notes on them aren't public 2014-02-14 22:13:17[ ] they are a small bitmap file that corresponds to chunks of the raid array 2014-02-14 22:13:33[ ] before the kernel goes to write to a chunk it sets the bit 2014-02-14 22:13:54[ KiBi] so maybe partman-auto-raid is the package you want to look at? 2014-02-14 22:14:12[ ] so if a system loses power, when it comes back up it only needs to resync the chunks that were actively being written to 2014-02-14 22:14:15[ ] really nice 2014-02-14 22:14:36[ KiBi] unless the code for it is elsewhere, maybe on the kernel side? 2014-02-14 22:14:59[ ] you can store them on other disks too in order to prevent the heads of a HDD needing to seek a lot 2014-02-14 22:15:07[ KiBi] ah, mdadm apparently: https://raid.wiki.kernel.org/index.php/Write-intent_bitmap 2014-02-14 22:15:15[ ] anyway it's super cool that d-i is doing it now 2014-02-14 22:15:44[ ] it only did some of them, the larger ones, which is also exactly what you probably want 2014-02-14 22:16:29[ ] when you set them up you get to pick the chunk size, it's a trade off of recovery time vs how often it needs to update the bitmap 2014-02-14 22:16:50[ ] so I am curious as to the decisions made by whoever added it 2014-02-14 22:16:53[ KiBi] autoraid-cfg does that: 2014-02-14 22:16:54[ KiBi] mdadm --create /dev/md$MD_NUM --auto=yes --force -R -l raid$RAID_TYPE \ 2014-02-14 22:16:54[ KiBi] -n $DEV_COUNT $MDADM_PARAMS 2014-02-14 22:17:07[ KiBi] (in the partman-auto-raid package) 2014-02-14 22:17:20[ KiBi] might just be some changed default on the mdadm side? 2014-02-14 22:17:28[ ] hmm, could be 2014-02-14 22:17:29[ KiBi] mjt would probably know 2014-02-14 22:17:43[ ] since that command line doesn't list it 2014-02-14 22:17:54[ ] well unl
Bug#280295: marked as done (nobootloader: [i386] kernel name not displayed correctly)
Your message dated Sun, 2 Mar 2014 02:10:28 +0100 with message-id <20140302011028.ga2...@mraw.org> and subject line Re: Bug#280295: nobootloader: [i386] kernel name not displayed correctly has caused the Debian Bug report #280295, regarding nobootloader: [i386] kernel name not displayed correctly 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.) -- 280295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nobootloader Version: 1.02 Severity: minor For i386, the dialog that displays the instructions for setting up the bootloader, shows "the /vmliuz kernel" instead of "the vmlinuz-2.4.27-1-386 kernel". So, please remove the leading slash and add the full version info. Cheers, FJP --- End Message --- --- Begin Message --- Frans Pop (2004-11-08): > On Monday 08 November 2004 18:42, Martin Michlmayr wrote: > > Why? Using the generic symlink is much better than hardcoding a > > specific version. > > Hmmm. Yes, forgot about the symlink. > > I have two objections to using the symlink though. > - If we install GRUB automatically we also refer to the real name. > - If I build my own kernel with 'make-kpkg' and install the resulting deb, > the symlink will be completely broken (deleted even), which would make > a boot into the old kernel difficult. > On the other hand, if you manually configured your bootloader, you will > have to set things up manually for the new kernel anyway. > > Let's think this over again after RC2; no hurry. This was never picked up again, so I'm just closing this bug report. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#279911: marked as done (Should mention the initrd parameter to be passed to kernel command line)
Your message dated Sun, 2 Mar 2014 02:16:12 +0100 with message-id <20140302011612.ga2...@mraw.org> and subject line Re: Bug#279911: debian-installer: initrd not mentioned when no bootloader is chosen has caused the Debian Bug report #279911, regarding Should mention the initrd parameter to be passed to kernel command line 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.) -- 279911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=279911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: important Justification: System would not boot if initrd is not passed to the kernel. The debian-installer provides the option to ``continue without a bootloader''. It might be an option for experts only but still it displays a note which should help configuring the bootloader. However this note is incomplete and thus the system won't boot because the kernel doesn't find its root filesystem. It mentions the kernel to boot (/vmlinuz) and the root (root=/dev/hdXX) boot option, but not the one required to load the initrd (initrd=/initrd.img) which is required by the shipped kernel to find the root partition. Keep up the good work -- the installations I did with the new debian-installer went mostly very well. Cheers, Philpp Kern --- End Message --- --- Begin Message --- Frans Pop (2004-11-07): > On Saturday 06 November 2004 11:49, Frans Pop wrote: > > In the meantime I'll add a comment in the manual about this. > > Done. > > --- nobootloader.xml(revision 23648) > +++ nobootloader.xml(working copy) > @@ -13,5 +13,16 @@ > Macintosh, Atari, and Amiga systems, where the original operating system > must be maintained on the box and used to boot GNU/Linux. > > + > + > +If you plan to manually configure your bootloader, you should check the > +name of the installed kernel in /target/boot. > +You should also check that directory for the presence of an > +initrd; if one is present, you will probably have > +to instruct your bootloader to use it. Other information you will need > +are the disk and partition you selected for your / > +filesystem and, if you chose to install /boot on a > +separate partition, also your /boot filesystem. > + > > So that's still around, namely “6.3.6.4. Continue Without Boot Loader”. Given Sven's comments[1], I'm tempted not to touch nobootloader at all; closing accordingly. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=279911#19 Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#395983: marked as done (nobootloader: [powerpc/pegasos] bump chrp-compliant partition numbering to 1.3.99+.)
Your message dated Sun, 2 Mar 2014 02:18:42 +0100
with message-id <20140302011842.ga3...@mraw.org>
and subject line Re: Bug#395983: nobootloader: [powerpc/pegasos] bump
chrp-compliant partition numbering to 1.3.99+.
has caused the Debian Bug report #395983,
regarding nobootloader: [powerpc/pegasos] bump chrp-compliant partition
numbering to 1.3.99+.
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.)
--
395983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=395983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nobootloader
Version: 1.13
Severity: normal
Please commit the attached patch to svn.
Notice that i already uploaded the package with the fix, so only a commit is
necessary.
Friendly,
Sven Luther
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-powerpc
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
diff -Nur nobootloader-1.13/debian/changelog nobootloader-1.14/debian/changelog
--- nobootloader-1.13/debian/changelog 2006-10-26 03:47:14.0 +0200
+++ nobootloader-1.14/debian/changelog 2006-10-29 09:37:40.0 +0100
@@ -1,3 +1,11 @@
+nobootloader (1.14) unstable; urgency=low
+
+ [ Sven Luther ]
+ * Genesi firmware 1.3 will be released without the chrp compliant partition
+numbering finally, so bumped the check to 1.3.99 and up.
+
+ -- Sven Luther Sun, 29 Oct 2006 09:36:13 +0100
+
nobootloader (1.13) unstable; urgency=low
[ Sven Luther ]
diff -Nur nobootloader-1.13/debian/postinst nobootloader-1.14/debian/postinst
--- nobootloader-1.13/debian/postinst 2006-10-26 03:18:33.0 +0200
+++ nobootloader-1.14/debian/postinst 2006-10-29 09:36:08.0 +0100
@@ -39,9 +39,9 @@
rest="${rest#*.}"
fv3="${rest%%.*}"
if [ "$fv1" -eq 1 ]; then
- if [ "$fv2" -eq 2 ] && [ "$fv3" -ge 99 ]; then
+ if [ "$fv2" -eq 3 ] && [ "$fv3" -ge 99 ]; then
partition_offset=0
- elif [ "$fv2" -ge 3 ]; then
+ elif [ "$fv2" -ge 4 ]; then
partition_offset=0
fi
elif [ "$fv1" -ge 2 ]; then
--- End Message ---
--- Begin Message ---
Sven Luther (2006-10-29):
> Package: nobootloader
> Version: 1.13
> Severity: normal
>
>
> Please commit the attached patch to svn.
>
> Notice that i already uploaded the package with the fix, so only a commit is
> necessary.
This was done long ago. Quoting git:
| $ git show 1.14
| tag 1.14
| Tagger: Frans Pop
| Date: Sun Oct 29 15:40:48 2006 +
|
| tagging version 1.14
|
| r42321
|
| commit 8762730767451740770e0f09845115d128253a4f
| Author: Frans Pop
| Date: Sun Oct 29 15:38:06 2006 +
|
| Genesi firmware 1.3 will be released without the chrp compliant partition
| numbering finally, so bumped the check to 1.3.99 and up
|
| r42320
Closing accordingly.
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
Processed: forcibly merging 693107 740330
Processing commands for cont...@bugs.debian.org: > forcemerge 693107 740330 Bug #693107 [partman-auto] Root partition quite small Bug #740330 [partman-auto] root-fs should be larger Severity set to 'important' from 'minor' Added tag(s) d-i. Merged 693107 740330 > thanks Stopping processing here. Please contact me if you need assistance. -- 693107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693107 740330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740330 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.13937234217591.transcr...@bugs.debian.org
Processed: Re: Bug#539512: prevent running kernel warning during d-i
Processing control commands: > tag -1 moreinfo Bug #539512 [pkgsel] prevent running kernel warning during d-i Added tag(s) moreinfo. -- 539512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539512 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.b539512.13937236588817.transcr...@bugs.debian.org
Bug#539512: prevent running kernel warning during d-i
Control: tag -1 moreinfo martin f krafft (2009-08-01): > After d-i installs the kernel, it connects to security.d.o and > possibly upgrades the kernel. This elicits a warning that the > currently running kernel is the same as the new one. I don't think I ever saw this in a d-i environment over the past few years I've been vaguely toying with it. Is that still seen with wheezy or above installation images? (I don't think so.) > Maybe this warning could/should be prevented, either by preseeding it > (if possible), or by adding security.d.o early enough so that the > non-security kernel is not even considered? Frans' comments are still valid; see pick_kernel in base-installer's library.sh file. Mraw, KiBi. signature.asc Description: Digital signature
Bug#740330: [PATCH] Combine / and /usr partitions in 'multi' recipes
Remove /usr partitions from all 'multi' recipes.
Increment the minimum size of the / partition by the minimum size
previously used for the /usr partition, and set the priority and
maximum size to be that previously used for the /usr partition.
Update debconf template to reflect that a /usr partition will not
be created.
---
This is entirely untested. Can't remember how to rebuild the installer.
Ben.
debian/changelog| 7 +++
debian/partman-auto.templates | 2 +-
recipes-amd64-efi/multi | 10 +-
recipes-armel-iop32x/multi | 10 +-
recipes-armel-ixp4xx/multi | 9 +
recipes-armel-kirkwood/multi| 10 +-
recipes-armel-orion5x/multi | 10 +-
recipes-armhf-efikasb/multi | 10 +-
recipes-armhf/multi | 10 +-
recipes-hppa/multi | 10 +-
recipes-ia64/multi | 9 +
recipes-mips-sb1-bcm91250a/multi| 9 +
recipes-mips-sb1a-bcm91480b/multi | 9 +
recipes-mipsel-loongson-2f/multi| 10 +-
recipes-mipsel-sb1-bcm91250a/multi | 9 +
recipes-mipsel-sb1a-bcm91480b/multi | 9 +
recipes-powerpc-apus/multi | 10 +-
recipes-powerpc-chrp_ibm/multi | 10 +-
recipes-powerpc-chrp_pegasos/multi | 10 +-
recipes-powerpc-powermac_newworld/multi | 10 +-
recipes-powerpc-powermac_oldworld/multi | 10 +-
recipes-powerpc-prep/multi | 10 +-
recipes-sparc/multi | 10 +-
recipes/multi | 10 +-
24 files changed, 30 insertions(+), 193 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 3d120ee..a37d076 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+partman-auto (119) UNRELEASED; urgency=medium
+
+ [ Ben Hutchings ]
+ * Combine / and /usr partitions in 'multi' recipes
+
+ -- Ben Hutchings Sat, 01 Mar 2014 23:32:28 +
+
partman-auto (118) unstable; urgency=low
* Add arm64 recipe
diff --git a/debian/partman-auto.templates b/debian/partman-auto.templates
index 5b81260..a164010 100644
--- a/debian/partman-auto.templates
+++ b/debian/partman-auto.templates
@@ -151,7 +151,7 @@ Template: partman-auto/text/multi_scheme
Type: text
# :sl1:
# TRANSLATORS: This is a menu entry. Keep in under 55 columns/characters
-_Description: Separate /home, /usr, /var, and /tmp partitions
+_Description: Separate /home, /var, and /tmp partitions
Template: partman-auto/text/small_disk
Type: text
diff --git a/recipes-amd64-efi/multi b/recipes-amd64-efi/multi
index 25e8ac6..37322bc 100644
--- a/recipes-amd64-efi/multi
+++ b/recipes-amd64-efi/multi
@@ -14,7 +14,7 @@ partman-auto/text/multi_scheme ::
filesystem{ ext2 }
mountpoint{ /boot } .
-100 800 500 $default_filesystem
+800 7000 7000 $default_filesystem
$lvmok{ }
method{ format }
format{ }
@@ -22,14 +22,6 @@ partman-auto/text/multi_scheme ::
$default_filesystem{ }
mountpoint{ / } .
-700 7000 7000 $default_filesystem
- $lvmok{ }
- method{ format }
- format{ }
- use_filesystem{ }
- $default_filesystem{ }
- mountpoint{ /usr } .
-
60 1500 3000 $default_filesystem
$lvmok{ }
method{ format }
diff --git a/recipes-armel-iop32x/multi b/recipes-armel-iop32x/multi
index fb70b76..49edd84 100644
--- a/recipes-armel-iop32x/multi
+++ b/recipes-armel-iop32x/multi
@@ -9,7 +9,7 @@ partman-auto/text/multi_scheme ::
filesystem{ ext2 }
mountpoint{ /boot } .
-70 800 280 $default_filesystem
+570 3000 5000 $default_filesystem
$lvmok{ }
$primary{ }
method{ format }
@@ -18,14 +18,6 @@ partman-auto/text/multi_scheme ::
$default_filesystem{ }
mountpoint{ / } .
-500 3000 5000 $default_filesystem
- $lvmok{ }
- method{ format }
- format{ }
- use_filesystem{ }
- $default_filesystem{ }
- mountpoint{ /usr } .
-
70 1500 3000 $default_filesystem
$lvmok{ }
method{ format }
diff --git a/recipes-armel-ixp4xx/multi b/recipes-armel-ixp4xx/multi
index 1c20cd6..4747caf 100644
--- a/recipes-armel-ixp4xx/multi
+++ b/recipes-armel-ixp4xx/multi
@@ -9,7 +9,7 @@ partman-auto/text/multi_scheme ::
filesystem{ ext2 }
mountpoint{ /boot } .
-70 800 280 $default_filesystem
+570 3000 5000 $default_filesystem
$primary{ }
method{ format }
format{ }
@@ -17,13 +17,6 @@ partman-auto/text/multi_scheme ::
$default_filesystem{ }
mountpoint{ / } .
-500 3000 5000 $default_filesystem
- method{ format }
- format{ }
- use_filesystem{ }
- $default_filesystem{ }
- mountpoint{ /usr } .
-
70 1500 3000 $default_filesystem
method{ format }
Bug#514647: marked as done (laptop-detect check for mipsel)
Your message dated Sun, 2 Mar 2014 02:31:04 +0100 with message-id <20140302013104.ga4...@mraw.org> and subject line Re: Bug#514647: laptop-detect check for mipsel has caused the Debian Bug report #514647, regarding laptop-detect check for mipsel 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.) -- 514647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pkgsel Severity: normal Tags: patch A mipsel laptop exists now, the Lemote Yeeloong. -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.18-6-amd64 (SMP w/2 CPU cores) Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Index: pre-pkgsel.d/10laptop-detect === --- pre-pkgsel.d/10laptop-detect (revision 56524) +++ pre-pkgsel.d/10laptop-detect (working copy) @@ -4,7 +4,7 @@ # Install laptop-detect on architectures known to have laptops case "$(archdetect)" in -i386/*|amd64/*|powerpc/*) +i386/*|amd64/*|powerpc/*|mipsel/*) apt-install laptop-detect || true ;; esac --- End Message --- --- Begin Message --- Frans Pop (2009-02-10): > tags 514647 - pending > severity 514647 wishlist > thanks […] > On that basis I've reverted the change in pkgsel. The patch can be > re-applied when the two conditions above have been met. This doesn't seem to have changed over a tiny 5-year time span, so closing. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Processed: tagging 740330
Processing commands for cont...@bugs.debian.org: > tags 740330 + patch Bug #740330 [partman-auto] root-fs should be larger Bug #693107 [partman-auto] Root partition quite small Added tag(s) patch. Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 693107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693107 740330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740330 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.139372433812311.transcr...@bugs.debian.org
Bug#652275: Bug#740330: [PATCH] Combine / and /usr partitions in 'multi' recipes
Ben Hutchings (2014-03-02): > Remove /usr partitions from all 'multi' recipes. > > Increment the minimum size of the / partition by the minimum size > previously used for the /usr partition, and set the priority and > maximum size to be that previously used for the /usr partition. > > Update debconf template to reflect that a /usr partition will not > be created. > --- > This is entirely untested. Can't remember how to rebuild the installer. Usually, debcheckout debian-installer, cd under build, and: make rebuild_netboot-gtk USE_UDEBS_FROM=unstable Hacked udebs can be put under build/localudebs. Since partman-auto isn't included in that image (and would then be fetched from the network), you can give it a shot replacing netboot-gtk with monolithic: make rebuild_monolithic USE_UDEBS_FROM=unstable You should see apt fetch the patched udeb from the localudebs directory. (For some reasons, while testing this, I see partman-auto stuff under /var/lib/dpkg/info in mini.iso's initrd.gz, but not in the running system; but then it's late and I might be missing something obvious.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#574336: marked as done (pkgsel: Only run update-initramfs once during installation?)
Your message dated Sun, 2 Mar 2014 03:00:15 +0100
with message-id <20140302020014.ga8...@mraw.org>
and subject line Re: Bug#574336: pkgsel: Only run update-initramfs once during
installation?
has caused the Debian Bug report #574336,
regarding pkgsel: Only run update-initramfs once during installation?
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.)
--
574336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pkgsel
Version: 0.25
Tags:patch
When checking the Ubuntu changes to pkgsel, I noticed this change:
- Divert update-initramfs and call it just once at the end (with
bind-mounted /dev, /proc, and /sys, and a preceding update-dev).
This seem like a good optimization for the installation time to bring
over to Debian, making sure update-initramfs is only executed twice
during the installation instead of several times more (once when the
kernel is installed by base-insatller, and once after pkgsel is done).
Is there any reason not to include it?
This patch relative to the current svn version would implement it. It
is ripped directly from the Ubuntu patch.
Index: debian/postinst
===
--- debian/postinst (revision 62670)
+++ debian/postinst (working copy)
@@ -6,7 +6,7 @@
export LANG=C
REMOUNT_CD=""
-DIVERTS='/usr/bin/scrollkeeper-update /usr/bin/scrollkeeper-rebuilddb
/usr/bin/fc-cache'
+DIVERTS='/usr/bin/scrollkeeper-update /usr/bin/scrollkeeper-rebuilddb
/usr/bin/fc-cache /usr/sbin/update-initramfs'
log() {
logger -t pkgsel "$@"
@@ -163,7 +163,22 @@
chroot /target fc-cache -f -v >/target/var/log/fontconfig.log 2>&1 \
|| true
fi
+if [ -x /target/usr/sbin/update-initramfs ]; then
+ # get UUIDs for any devices formatted after partitioning
+ update-dev
+ # make UUIDs etc. available in the target system
+ mount -o bind /dev /target/dev
+ mount -o bind /sys /target/sys
+ mount -o bind /proc /target/proc
+
+ chroot /target /usr/sbin/update-initramfs -u || true
+
+ umount /target/proc
+ umount /target/sys
+ umount /target/dev
+fi
+
db_progress STEP 30
db_progress STOP
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Petter Reinholdtsen (2010-03-17):
> Package: pkgsel
> Version: 0.25
> Tags:patch
>
> When checking the Ubuntu changes to pkgsel, I noticed this change:
>
> - Divert update-initramfs and call it just once at the end (with
>bind-mounted /dev, /proc, and /sys, and a preceding update-dev).
>
> This seem like a good optimization for the installation time to bring
> over to Debian, making sure update-initramfs is only executed twice
> during the installation instead of several times more (once when the
> kernel is installed by base-insatller, and once after pkgsel is done).
> Is there any reason not to include it?
>
> This patch relative to the current svn version would implement it. It
> is ripped directly from the Ubuntu patch.
With dpkg triggers, this shouldn't be needed any more, so closing.
See my comments in another bug report about a possible extra, explicit
call which we might want to get rid of:
https://lists.debian.org/debian-boot/2014/02/msg00296.html
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
Bug#282155: distinguish out-of-space from other installation failures
Joey Hess (2004-11-20): > Matt Kraai wrote: > > Package: base-config > > Version: 2.53.4 > > Severity: wishlist > > > > If tasksel fails, base-config displays a generic error message that > > does not distinguish whether the disk is full from whether a package > > is broken. It would be helpful if it provided more information. > > Do dpkg and aptitude use a special error code for out of space? From a quick git grep ENOSPC in both dpkg.git and apt.git, no match except a single unrelated one for apport on the apt side. Pinging the relevant maintainers to make sure might be an idea, asking them how much would be needed to implement it if needed would be another one. Mraw, KiBi. signature.asc Description: Digital signature
Bug#348963: marked as done (pkgsel: perl warning can be disabled by using PERL_BADLANG)
Your message dated Sun, 2 Mar 2014 03:08:09 +0100 with message-id <20140302020809.ga9...@mraw.org> and subject line Re: Bug#348963: pkgsel: perl warning can be disabled by using PERL_BADLANG has caused the Debian Bug report #348963, regarding pkgsel: perl warning can be disabled by using PERL_BADLANG 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.) -- 348963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pkgsel Severity: normal Version: 0.04 Hi, pkgsel is running with LANG=C because of: * Set LANG to C in postinst so that the bare chroot calls don't trigger perl warning messages for C.UTF-8 locale. (See #344159) But I think we can disable a perl warning by just setting PERL_BADLANG=0 instead of doing LANG=C. LANG=C makes all of messages derived from pkgsel to English. It's not so good for non English people. Thanks, -- Kenshi Muto km...@debian.org --- End Message --- --- Begin Message --- Kenshi Muto (2006-01-22): > But strangely, first tasksel screen still won't show translation; "At > the moment, only the core of Debian is..." and "Choose software to > install:". > All of processes derived from tasksel use a translation. > > I tried: > - Run tasksel on target chroot. It works correctly. > - Uncomment LANG=C of pkgsel. No effect. > - Change it to LANG=ja_JP.UTF-8. No effect. Either that was a transient issue (maybe due to a partial translation in a given language), or a real bug got fixed. Either way, I haven't seen anything like this during the wheezy release cycle, so I'm closing this bug report for now. Feel free to open a fresh one if you're able to reproduce it in wheezy (or newer) installation images. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#498003: marked as done (installation-reports: An a-g clean is missing before finishing the install process)
Your message dated Sun, 2 Mar 2014 03:13:05 +0100 with message-id <20140302021305.ga9...@mraw.org> and subject line Re: Bug#498003: installation-reports: An a-g clean is missing before finishing the install process has caused the Debian Bug report #498003, regarding installation-reports: An a-g clean is missing before finishing the install process 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.) -- 498003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Hi, I've just installed Lenny on a qemu, and noticed just after the install that the system wasn't cleaned. From the task chooser, i have chosen desktop+base. Here are the facts, first boot after install : francois@debian:~$ df -h FilesystemSize Used Avail Use% Mounted on /dev/hda1 4.7G 3.1G 1.4G 71% / tmpfs 253M 0 253M 0% /lib/init/rw udev 10M 80K 10M 1% /dev tmpfs 253M 0 253M 0% /dev/shm /dev/hdc 46M 46M 0 100% /media/cdrom0 francois@debian:~$ su -c "apt-get clean" Password: francois@debian:~$ df -h FilesystemSize Used Avail Use% Mounted on /dev/hda1 4.7G 2.4G 2.1G 53% / tmpfs 253M 0 253M 0% /lib/init/rw udev 10M 80K 10M 1% /dev tmpfs 253M 0 253M 0% /dev/shm /dev/hdc 46M 46M 0 100% /media/cdrom0 Regards, François. -- Package-specific info: Boot method: CD Image version: debian-testing-i386-businesscard.iso Date: 09/07/2008 - 4am GMT+2 Machine: qemu (but doesn't matter here) Partitions: FilesystemSize Used Avail Use% Mounted on /dev/hda1 4.7G 3.1G 1.4G 71% / tmpfs 253M 0 253M 0% /lib/init/rw udev 10M 80K 10M 1% /dev tmpfs 253M 0 253M 0% /dev/shm /dev/hdc 46M 46M 0 100% /media/cdrom0 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] 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: [E] Install boot loader:[O] Overall install:[O] -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="5.0 (lenny) - installer build 20080905-19:04" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux debian 2.6.26-1-486 #1 Thu Aug 28 11:14:57 UTC 2008 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] lspci -knn: Kernel driver in use: PIIX_IDE lspci -knn: Kernel modules: piix lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] lspci -knn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] lspci -knn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8029(AS) [10ec:8029] lspci -knn: Kernel driver in use: ne2k-pci lspci -knn: Kernel modules: ne2k-pci lsmod: Module Size Used by lsmod: ufs63620 0 lsmod: qnx47684 0 lsmod: ntfs 180416 0 lsmod: dm_mod 45384 0 lsmod: md_mod 65940 0 lsmod: xfs 446836 0 lsmod: reiserfs 187008 0 lsmod: jfs 148060 0 lsmod: ext3 103432 1 lsmod: jbd35092 1 ext3 lsmod: vfat8832 0 lsmod: fat39964 1 vfat lsmod: ext2 52616 0 lsmod: mbcache 6656 2 ext3,ext2 lsmod: ne2k_pci7904 0 lsmod: 83908064 1 ne2k_pci lsmod: nls_utf81664 2 lsmod: isofs 27684 0 lsmod: nls
Processed: Re: Bug#539512: prevent running kernel warning during d-i
Processing control commands: > reassign -1 src:linux-2.6 Bug #539512 [pkgsel] prevent running kernel warning during d-i Bug reassigned from package 'pkgsel' to 'src:linux-2.6'. Warning: Unknown package 'src:linux-2.6' Warning: Unknown package 'src:linux-2.6' Ignoring request to alter found versions of bug #539512 to the same values previously set Warning: Unknown package 'src:linux-2.6' Warning: Unknown package 'src:linux-2.6' Ignoring request to alter fixed versions of bug #539512 to the same values previously set Warning: Unknown package 'src:linux-2.6' > close -1 2.6.24-1 Bug #539512 [src:linux-2.6] prevent running kernel warning during d-i Warning: Unknown package 'src:linux-2.6' Marked as fixed in versions linux-2.6/2.6.24-1. Warning: Unknown package 'src:linux-2.6' Bug #539512 [src:linux-2.6] prevent running kernel warning during d-i Warning: Unknown package 'src:linux-2.6' Marked Bug as done Warning: Unknown package 'src:linux-2.6' -- 539512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539512 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.b539512.139372728926342.transcr...@bugs.debian.org
Bug#418590: main-menu: Segfault during automatic install on AMD64
Control: tag -1 moreinfo Olaf van der Spek (2007-05-22): > When I do that I get tons of questions and it seems the issue doesn't > occur anymore. Is there no other way to get that set -x in there? > > BTW, I'm using VMware Workstation on a Core 2 Duo processor. It's > weird that no one can reproduce this. Is that still reproducible with current wheezy installation images? If that's the case, we'll see how to help you debug that further. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#418590: main-menu: Segfault during automatic install on AMD64
Processing control commands: > tag -1 moreinfo Bug #418590 [preseed] main-menu: Segfault during automatic install on AMD64 Added tag(s) moreinfo. -- 418590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418590 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.b418590.139372738926456.transcr...@bugs.debian.org
Bug#539512: prevent running kernel warning during d-i
Control: reassign -1 src:linux-2.6 Control: close -1 2.6.24-1 On Sun, 2014-03-02 at 02:27 +0100, Cyril Brulebois wrote: > Control: tag -1 moreinfo > > martin f krafft (2009-08-01): > > After d-i installs the kernel, it connects to security.d.o and > > possibly upgrades the kernel. This elicits a warning that the > > currently running kernel is the same as the new one. > > I don't think I ever saw this in a d-i environment over the past few > years I've been vaguely toying with it. Is that still seen with wheezy > or above installation images? (I don't think so.) [...] The warning was completely removed long ago. Ben. -- Ben Hutchings Time is nature's way of making sure that everything doesn't happen at once. signature.asc Description: This is a digitally signed message part
Bug#696857: preseed: Does not re-enable locale and keymap selection
Control: tag -1 - pending Samuel Thibault (2012-12-29): > Control: tags -1 + pending > > Hello, > > Brian Potkin, le Fri 28 Dec 2012 11:25:08 +, a écrit : > > No such lines appear in the postinst for file-preseed, which means > > that with > > > >auto=true file=/mnt/preseed.cfg priority=low > > Agreed, tested, and commited. Hmm, sorry if I'm overlooking anything but I don't see any mention of #696857 under packages/, and the only commit I see from you in preseed.git is: | commit 8c26635f0a2b2e2b730ac63082f954ca4f9024a8 | Author: Samuel Thibault | Date: Mon Feb 27 00:09:58 2012 +0100 | | Point the keymap alias to console-setup-udeb var | | instead of the now-gone console-data. Untagging this bug report for now. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#696857: preseed: Does not re-enable locale and keymap selection
Processing control commands: > tag -1 - pending Bug #696857 [preseed] preseed: Does not re-enable locale and keymap selection Removed tag(s) pending. -- 696857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696857 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.b696857.139372784528688.transcr...@bugs.debian.org
Bug#610525: marked as done (Preseed: Debian Installer hangs during late_command)
Your message dated Sun, 2 Mar 2014 04:09:17 +0100 with message-id <20140302030917.ga16...@mraw.org> and subject line Re: Bug#610525: lvremove hangs late_command has caused the Debian Bug report #610525, regarding Preseed: Debian Installer hangs during late_command 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.) -- 610525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Version: 20110106+b1 Severity: serious Hello, i have added the following lines to my preseed config, because partman should use a static size for my partitions. d-i preseed/late_command string \ in-target lvremove -f /dev/vg0/dummy; After the installation the dummy partition should be removed, but the Debian Installer stops working. The following content is from the "syslog" and "ps". Jan 19 09:20:31 in-target: File descriptor 3 (pipe:[2171]) leaked on lvremove invocation. Jan 19 09:20:31 in-target: Parent PID 15538: log-output Jan 19 09:20:31 in-target: File descriptor 4 (/dev/pts/0) leaked on lvremove invocation. Parent PID 15538: log-output Jan 19 09:20:31 in-target: File descriptor 5 (/dev/pts/0) leaked on lvremove invocation. Parent PID 15538: log-output Jan 19 09:20:31 in-target: File descriptor 6 (/dev/pts/0) leaked on lvremove invocation. Parent PID 15538: log-output Jan 19 09:23:32 init: starting pid 249, tty '/dev/tty2': '-/bin/sh' Jan 19 09:28:10 init: starting pid 250, tty '/dev/tty3': '-/bin/sh' root 15335 0.0 0.2 1844 652 pts/0S+ 10:20 0:00 udpkg --configure --force-configure finish-install root 15336 0.0 0.2 1872 608 pts/0S+ 10:20 0:00 /bin/sh /var/lib/dpkg/info/finish-install.postinst configure root 15488 0.0 0.1 1708 420 pts/0S+ 10:20 0:00 log-output -t finish-install /usr/lib/finish-install.d/07preseed root 15489 0.0 0.1 1868 464 pts/0S+ 10:20 0:00 /bin/sh -e /usr/lib/finish-install.d/07preseed root 15490 0.0 0.2 1872 588 pts/0S+ 10:20 0:00 /bin/sh -e /bin/preseed_command preseed/late_command root 15492 0.0 0.1 1708 412 pts/0S+ 10:20 0:00 log-output sh -c in-target lvremove -f /dev/vg0/dummy; root 15493 0.0 0.1 1868 448 pts/0S+ 10:20 0:00 sh -c in-target lvremove -f /dev/vg0/dummy; root 15494 0.0 0.2 1868 540 pts/0S+ 10:20 0:00 /bin/sh /bin/in-target lvremove -f /dev/vg0/dummy root 15538 0.0 0.2 1708 532 pts/0S+ 10:20 0:00 log-output -t in-target chroot /target lvremove -f /dev/vg0/dummy root 15539 0.0 5.3 15300 13544 pts/0S signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- [ Adding the submitter back into the Cc loop. ] Andreas Unterkircher (2011-10-06): > Just for the records - this problem appears when you call lvremove > within the /target chroot environment by in-target. > > If you remove in-target from your late_command and by this invoke > lvremove within d-i's rootfs, it works. Looks like a reasonable fix for the issue Dennis described, so I'm closing this bug report since I don't think there's anything to fix in d-i. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#612727: env-preseed: mirror/http/proxy= in kernel parameters via PXE doesn't work
Samuel Thibault (2011-02-10): > Package: env-preseed > Version: 1.48 > Severity: normal > > Hello, > > Giving mirror/http/proxy= on the PXE kernel command line (i.e. giving an > empty value) doesn't seem to be feeding debconf: the question is still > getting asked. We also tried mirror/http/proxy="" with the same result. > > More precisely, the pxe configuration is > > APPEND ramdisk_size=14984 locale=fr_FR.UTF-8 > console-keymaps-at/keymap=fr-latin9 console-setup/layoutcode=fr > netcfg/get_hostname=inrescuemode netcfg/get_domain=ens-lyon.fr > mirror/country=fr mirror/http/hostname=ftp.fr.debian.org > mirror/http/directory=debian vga=normal > initrd=debian/squeeze/i386/debian-installer/i386/initrd.gz rescue/enable=true > -- I don't have any PXE test setup currently, but a few tests using wheezy or current images seem to show the behaviour is correct when adding this to the syslinux prompt. Is the issue you mentioned PXE-specific? Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#508157: debian-installer: Rescue mode: cryptsetup doesn't accept password (verified correct, muliple x)
Processing control commands: > tag -1 moreinfo Bug #508157 [rescue] debian-installer: Rescue mode: cryptsetup doesn't accept password (verified correct, muliple x) Added tag(s) moreinfo. -- 508157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508157 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.b508157.139373169116062.transcr...@bugs.debian.org
Bug#508157: debian-installer: Rescue mode: cryptsetup doesn't accept password (verified correct, muliple x)
Control: tag -1 moreinfo Daniel Dickinson (2008-12-08): > Package: debian-installer > Severity: normal > > Using the lenny-rc1 xfce-cd1 image I attempted to use rescue mode to > operate on an encrypted lvm which is detected and mounts fine with the > regular boot system. It was created using a previous version of > lenny's installer (but I don't remember which one). > > I suspect the problem may be related to the fact that when I initially > created the filesystem there was a usb key drive in the system. OTOH > I have tried rescue mode both with and without the key to no avail. > > It may matter that I have modified crypttab to use > /dev/disk/by-uuid/the-uuid-of-the-luks-partition and that the name of > the crypt volume has been changed from the default. > > I have tried with luksOpen /dev/disk/by-uuid/uuid-of-luks crypt_name > and get a message which states that cryptsetup failed because there > was no key with the entered password, however I have entered the > password multiple times. > > Could it matter that it is a logitech internet keyboard and not a > plain vanilla keyboard? > > Please let me know what other information I can send that would help. I've used rescue mode with encrypted lvm on various occasions with squeeze and wheezy, and I haven't had any issues. Are you still able to reproduce this kind of issues? Mraw, KiBi. signature.asc Description: Digital signature
Bug#589923: marked as done (debian-installer: Rescue mode fails to determine codename for the release)
Your message dated Sun, 2 Mar 2014 04:46:37 +0100 with message-id <20140302034637.ga20...@mraw.org> and subject line Re: Bug#589923: #589923 debian-installer: Rescue mode fails to determine codename for the release has caused the Debian Bug report #589923, regarding debian-installer: Rescue mode fails to determine codename for the release 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.) -- 589923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Version: Lenny 5.0.5 Severity: normal I am going booting into rescue mode from the Lenny minimal install business cd (point release 5.0.5). After selecting to install grub from the menu the rescue mode takes me to the partitioner (this is normal). In the partitioner I choose for automatic partitioning, use whole disk and seperate partitions for /home, /var etc. The program continues normally until I get a red screen saying: "[!!] Install the base system Debootstrap Error Failed to determine codename for the release. " In tty4 I see: cat: can't open '/dev/md0/device': Not a directory base-installer: error: exiting on error base-installer/no_codename Full syslog is included with this bug report. I think this happens because the kernel still thinks somehow it has to do something with the sw raid device that was there in the partition table before I started partitioning in rescue mode. I have seen with other installations sometimes that the installer gets confused when there are raid devices from a previous installation attempt. I have included fdisk -l with this bug report (generated after I got the error). Before partitioning both sda en sdb had the same partition table and there was a software raid md0 using sda2 and sdb2. I filed this to debian-installer because I expect this to be not specific to rescue mode. --- End Message --- --- Begin Message --- Miguel Figueiredo (2011-01-23): > as lenny's installer is not supported anymore can you try latest debian > installer release (squeeze rc2) rescue mode and report if you still > experience the issue you reported? > > http://cdimage.debian.org/cdimage/squeeze_di_rc2/ The submitter was pinged 3+ years ago, and we haven't heard back, so closing this bug report. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#508157: marked as done (debian-installer: Rescue mode: cryptsetup doesn't accept password (verified correct, muliple x))
Your message dated Sun, 2 Mar 2014 04:57:37 +0100 with message-id <20140302035737.gd22...@mraw.org> and subject line Re: Bug#508157: debian-installer: Rescue mode: cryptsetup doesn't accept password (verified correct, muliple x) has caused the Debian Bug report #508157, regarding debian-installer: Rescue mode: cryptsetup doesn't accept password (verified correct, muliple x) 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.) -- 508157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: normal Using the lenny-rc1 xfce-cd1 image I attempted to use rescue mode to operate on an encrypted lvm which is detected and mounts fine with the regular boot system. It was created using a previous version of lenny's installer (but I don't remember which one). I suspect the problem may be related to the fact that when I initially created the filesystem there was a usb key drive in the system. OTOH I have tried rescue mode both with and without the key to no avail. It may matter that I have modified crypttab to use /dev/disk/by-uuid/the-uuid-of-the-luks-partition and that the name of the crypt volume has been changed from the default. I have tried with luksOpen /dev/disk/by-uuid/uuid-of-luks crypt_name and get a message which states that cryptsetup failed because there was no key with the entered password, however I have entered the password multiple times. Could it matter that it is a logitech internet keyboard and not a plain vanilla keyboard? Please let me know what other information I can send that would help. Regards, Daniel -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Cyril Brulebois (2014-03-02): > Control: tag -1 moreinfo […] > I've used rescue mode with encrypted lvm on various occasions with > squeeze and wheezy, and I haven't had any issues. Are you still able to > reproduce this kind of issues? csh...@brucetelecom.com SMTP error from remote mail server after RCPT TO:: host prefix2.bmts.com [216.183.128.134]: 550 5.1.1 : Recipient address rejected: undeliverable address: host mailx.localnet[10.5.5.135] said: 550 5.1.1 : Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command) so: closing. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#511153: tzsetup-udeb: time zone list in tzsetup out of date wrt glibc/tzdata time
Hi Christian, Christian Perrier (2009-01-08): > Quoting Frans Pop (elen...@planet.nl): > > On Wednesday 07 January 2009, Jude Nagurney wrote: > > > Please update tzsetup-udeb so it's aligned with the latest pkg-glibc > > > time zone data. > > > > Thanks for the heads-up. > > > > As this also requires translation updates for the added time zones this is > > not something that can quickly be done in time for Lenny. > > I check current translations, just in case, but several of them use > transliterated text, for instance: > > ru.po:msgid "East Indiana" > ru.po-msgstr "Восточная Индиана" > > So these translators also might want to transliterate the city names > in the new "time zones"and we just can't put msgid's in msgstr's > > At the minimum, if we add new timezones, we could grab translations > back from tzdata (there are quite a lot of translations in that package). > > Definitely something for post-lenny, indeed...sorry for the few > counties in USA that decide to live differently from the rest of the > country. > > Actually, there might me other cases like this one as I haven't seen > anyone actively trying to cope with changes in tzdata to align tzsetup > with them (such as the recent nightmare in Argentinian timezones). what should we do about this bug report? Mraw, KiBi. signature.asc Description: Digital signature
Bug#675937: marked as done (installation-reports: Captital city: Melbourne, State: Victoria, Country: Australia missing from Configure Clock)
Your message dated Sun, 2 Mar 2014 04:59:10 +0100 with message-id <20140302035910.ga21...@mraw.org> and subject line Re: Bug#675937: installation-reports: Captital city: Melbourne, State: Victoria, Country: Australia missing from Configure Clock has caused the Debian Bug report #675937, regarding installation-reports: Captital city: Melbourne, State: Victoria, Country: Australia missing from Configure Clock 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.) -- 675937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Tags: d-i l10n Dear Maintainer, -- Package-specific info: Boot method: Booted USB built using unetbootin Image version: Testing_NetInstall. It affects x64 and 386. Date: 2 June 2012 Machine: Hand built Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[O] Configure network: [O] Detect CD: [ ] 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: On the installer's Configure Clock screen, following selecting Country: Australia, my state: Victoria was missing from the list of State or Province. So I selected an incorrect state. Later, after the installation was completed, I used sudo dpkg-reconfigure tzdata to correct it. 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="7.0 (wheezy) - installer build 20120508" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux mythtv-1 3.2.0-2-amd64 #1 SMP Sun Apr 15 16:47:38 UTC 2012 x86_64 GNU/Linux lspci -knn: 00:00.0 RAM memory [0500]: NVIDIA Corporation MCP78S [GeForce 8200] Memory Controller [10de:0754] (rev a2) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: 00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP78S [GeForce 8200] LPC Bridge [10de:075c] (rev a2) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: 00:01.1 SMBus [0c05]: NVIDIA Corporation MCP78S [GeForce 8200] SMBus [10de:0752] (rev a1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: 00:01.2 RAM memory [0500]: NVIDIA Corporation MCP78S [GeForce 8200] Memory Controller [10de:0751] (rev a1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: 00:01.3 Co-processor [0b40]: NVIDIA Corporation MCP78S [GeForce 8200] Co-Processor [10de:0753] (rev a2) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: 00:01.4 RAM memory [0500]: NVIDIA Corporation MCP78S [GeForce 8200] Memory Controller [10de:0568] (rev a1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: 00:02.0 USB controller [0c03]: NVIDIA Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller [10de:077b] (rev a1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:02.1 USB controller [0c03]: NVIDIA Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller [10de:077c] (rev a1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:04.0 USB controller [0c03]: NVIDIA Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller [10de:077d] (rev a1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:04.1 USB controller [0c03]: NVIDIA Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller [10de:077e] (rev a1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:06.0 IDE interface [0101]: NVIDIA Corporation MCP78S [GeForce 8200] IDE [10de:0759] (rev a1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82f2] lspci -knn: Kernel driver in use: pata_amd lspci -knn: 00:07.0 Audio device [0403]: NVIDIA Corporation MCP72XE/MCP72P/MCP78U/MCP78
Bug#364638: marked as done (Invalid characters in short user name need reboot)
Your message dated Sun, 2 Mar 2014 05:16:42 +0100 with message-id <20140302041642.ga24...@mraw.org> and subject line Re: Bug#364638: Invalid characters in short user name need reboot has caused the Debian Bug report #364638, regarding Invalid characters in short user name need reboot 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.) -- 364638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Severity: important Package: installation-reports Boot method: CD-image in VMware Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso 'built on 20060409' Download date: 20060420 Date: 20060424 Machine: VMware Workstation 5.5.1 under Debian/unstable Test sequence: - boot without parameters (=default) - language: German - keymap: German - etc. - at the prompt for the user account name type in a non-ASCII character like 'ä' LATIN SMALL LETTER A WITH DIARESIS into the edit field Expected behaviour: --- 1) it is not possible to enter invalid characters OR 2) let the user correct the string after an error message Actual behaviour: - - The edit field displays the string '' instead of 'ä', - the yellow background signalling the cursor position hangs on the '<' of '', - or is not working, - after an error message and managing going back to the question, the field again is initialized with the defect string -> no chance for correction, reboot needed Characters not working are: ß°§üÜöäÖĵ All other invalid characters (outside [a-z][a-z0-9]+) of the German keyboard do not damage the field editor. In case of other strings, e.g. hostname, it is possible to go to the main installer menu, retry, and a nice and sane edit field is displayed. BTW: g-i has better handling in the same situation. PS: maybe you want raise the severity higher. Helmut Wollmersdorfer --- End Message --- --- Begin Message --- Helmut Wollmersdorfer (2006-04-24): > Expected behaviour: > --- > > 1) it is not possible to enter invalid characters > > OR > > 2) let the user correct the string after an error message The latter is implemented, and working fine in both text and graphical modes. > Actual behaviour: > - > > - The edit field displays the string '' instead of 'ä', > - the yellow background signalling the cursor position hangs on the '<' > of '', > - or is not working, > - after an error message and managing going back to the question, > the field again is initialized with the defect string > -> no chance for correction, reboot needed > Characters not working are: ß°§üÜöäÖĵ > All other invalid characters (outside [a-z][a-z0-9]+) of the German > keyboard do not damage the field editor. > > In case of other strings, e.g. hostname, it is possible to go to the > main installer menu, retry, and a nice and sane edit field is > displayed. > > BTW: g-i has better handling in the same situation. > > PS: maybe you want raise the severity higher. > > Helmut Wollmersdorfer Closing this bug report as the current situation looks good to me. Feel free to reopen with more info if you're still having any issues. Mraw, KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#538086: marked as done (user-setup: Lenny version is incompatible with Squeeze/Sid)
Your message dated Sun, 2 Mar 2014 05:24:17 +0100 with message-id <20140302042417.ga25...@mraw.org> and subject line Re: Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set has caused the Debian Bug report #538086, regarding user-setup: Lenny version is incompatible with Squeeze/Sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 538086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: grave Justification: renders package unusable -- Package-specific info: Boot method: USB stick with netboot Image version: ftp://ftp.debian.org/debian/dists/stable/main/installer-i386/current/images/netboot/ Date: Machine: Lenovo Thinkpad x200s Partitions: dinyar-notebook:/home/dinyar# df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/dinyar--notebook-root ext3 295996296 5050720 275909776 2% / tmpfstmpfs 1979968 0 1979968 0% /lib/init/rw udev tmpfs 10240 148 10092 2% /dev tmpfstmpfs 1979968 0 1979968 0% /dev/shm /dev/sda1 ext2 25 44713176174 21% /boot Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[E] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: The first problem I encountered while trying to install a system with an encrypted LVM was that the USB stick was taken to be /dev/sda while the harddisk was /dev/sdb. This changed at first boot when the usb stick was unplugged. This first problem could be fixed either by booting into a rescue system and first changing grub's menu.lst to point to (hd0,0) instead of (hd1,0) and then unpack the initrd.img file and change /conf/conf.d/cryptroot to point to /dev/sda instead of /dev/sdb, or alternatively I pulled the USB stick out right before detecting the harddisk. (priority=medium is helpfull for timing here.) This seemed to have no negativ effects on the installation. The second problem I encountered was that neither my user account was created during installation nor was the root password set. This left the system fairly unusable until I used a rescue system to mount my encrypted disk, added a user to /etc/passwd and /etc/shadow (without a password) and subsequently added this user to the sudoers group. In this way I could aquire root on my new system. -- 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 20090123lenny3" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == umame -a: Linux dinyar-notebook 2.6.26-2-amd64 #1 SMP Sun Jun 21 04:47:08 UTC 2009 x86_64 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller [8086:2a44] (rev 07) lspci -knn: 00:03.2 IDE interface [0101]: Intel Corporation Mobile 4 Series Chipset PT IDER Controller [8086:2a46] (rev 07) lspci -knn: 00:03.3 Serial controller [0700]: Intel Corporation Mobile 4 Series Chipset AMT SOL Redirection [8086:2a47] (rev 07) lspci -knn: Kernel driver in use: serial lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) lspci -knn: K
Processed: Re: FTBFS when locales-all is installed
Processing commands for cont...@bugs.debian.org:
> reopen 714350
Bug #714350 {Done: Cyril Brulebois } [localechooser] FTBFS
when locales-all is installed
Bug reopened
Ignoring request to alter fixed versions of bug #714350 to the same values
previously set
> found 714350 2.60
Bug #714350 [localechooser] FTBFS when locales-all is installed
Marked as found in versions localechooser/2.60.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
714350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714350
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.13937366176635.transcr...@bugs.debian.org
Bug#714350: FTBFS when locales-all is installed
reopen 714350 found 714350 2.60 thanks no, it does; reopening accordingly. Checking syntax of localechooser LC_COLLATE=C ./mklanguagelist.data languagelist debian/languagelist.data ./get-SUPPORTED make[1]: *** [debian/SUPPORTED-short] Error 1 make[1]: Leaving directory `/home/user/localechooser-2.60' dh_auto_build: make -j1 returned exit code 2 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/5312bba4.6000...@progress-technologies.net
Bug#606110: installation-report: gtk installer fail to start with PXE boot of Dell Latitude D505
[Cyril Brulebois] > If you still have access to this machine, does the wheezy gtk > installer start fine? Otherwise, lacking access to such a machine, > I'm tempted to close this bug report. I still have access to the machine at work (it is one of my collection of test laptops). I'll retry the wheezy installer, but vaguely remeber the problem exist there too. Anything in particular I should test? -- Happy hacking Petter Reinholdtsen -- 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/20140302065529.gg7...@ulrik.uio.no
Processed: Re: Bug#696857: preseed: Does not re-enable locale and keymap selection
Processing control commands: > tags -1 + pending Bug #696857 [preseed] preseed: Does not re-enable locale and keymap selection Added tag(s) pending. -- 696857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696857 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.b696857.139374642129217.transcr...@bugs.debian.org
Bug#696857: preseed: Does not re-enable locale and keymap selection
Control: tags -1 + pending Hello, Cyril Brulebois, le Sun 02 Mar 2014 03:37:22 +0100, a écrit : > > >auto=true file=/mnt/preseed.cfg priority=low > > > > Agreed, tested, and commited. > > Hmm, sorry if I'm overlooking anything but I don't see any mention > of #696857 under packages/, and the only commit I see from you in > preseed.git is: > | commit 8c26635f0a2b2e2b730ac63082f954ca4f9024a8 > | Author: Samuel Thibault > | Date: Mon Feb 27 00:09:58 2012 +0100 > | > | Point the keymap alias to console-setup-udeb var > | > | instead of the now-gone console-data. > > Untagging this bug report for now. D'oh. It seems that I had forgotten to push that too... Sorry about that. Samuel -- 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/20140302074643.GD6572@type.hotspots
