cdebconf_0.235_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 27 Nov 2017 08:02:28 +0100 Source: cdebconf Binary: cdebconf cdebconf-gtk libdebconfclient0 libdebconfclient0-dev cdebconf-udeb cdebconf-priority libdebconfclient0-udeb cdebconf-text-udeb cdebconf-newt-udeb cdebconf-gtk-udeb Architecture: source Version: 0.235 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Christian Perrier Description: cdebconf - Debian Configuration Management System (C-implementation) cdebconf-gtk - Gtk+ frontend for Debian Configuration Management System cdebconf-gtk-udeb - Gtk+ frontend for Debian Configuration Management System (udeb) cdebconf-newt-udeb - Newt frontend for Debian Configuration Management System (udeb) cdebconf-priority - Change debconf priority (udeb) cdebconf-text-udeb - Plain text frontend for Debian Configuration Management System (udeb) cdebconf-udeb - Debian Configuration Management System (C-implementation) (udeb) libdebconfclient0 - Debian Configuration Management System (C-implementation library) libdebconfclient0-dev - Development files for cdebconf libdebconfclient0-udeb - Debian Configuration Management System (C-implementation) (udeb) Changes: cdebconf (0.235) unstable; urgency=medium . [ Updated translations ] * Lithuanian (lt.po) by Rimas Kudelis * Norwegian Nynorsk (nn.po) by Allan Nordhøy Checksums-Sha1: 6f1acd37931af7db6a9c268832412a3e3f4206b7 2676 cdebconf_0.235.dsc 40ba83cb91c0b13ee68010846915e23859c7f15c 273760 cdebconf_0.235.tar.xz Checksums-Sha256: 292992257cad3ad79a9487cf5915de431b4ebdf6cc1c0a6bcb944b3bee00fe41 2676 cdebconf_0.235.dsc 684a0bdb4bd579ef5296522d47abbf24401dc3ee3dc96097bc6f06dbf6f6c496 273760 cdebconf_0.235.tar.xz Files: c86388c6066cc1a0d06ed378bdbac0e3 2676 utils optional cdebconf_0.235.dsc 80c1cc2730c8aadc4b82056d30f7e029 273760 utils optional cdebconf_0.235.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE1cL5v8oSi7oip3IYhy9wLE1uJagFAlobvFkACgkQhy9wLE1u JajurA//bNspzJ5SUx52Sgto/7XJjT/kG3k2nvlWhk8PRbMgrA3GACRTzrr+LF+3 YprMx36nebMk3g8p8OxYvZ+z0zdo6l4J5pXLyC85UFpqra2cI+VO49Atj2c2uYsb DhzYX0Znq4wlchwfK0HhntLj09LSm1Z9E8PrT6KJdVLS09KovvpNiymJfkpsXxg/ 1gmadeWBNytGjwnt7uHhkme0moET9Ci/mzv9hPRgQP2cLxdaNuxvvXLG/BkMdDcZ 3rv0CjepjIBMGpidNbC3G5yDX96acy7GJ6BLBO5zqQqYMifN5PaHRYOMlossUT0C LXlsgXhisXSR1+xnmcStN2YCLtsP0rt7Nt3OZyiLmnIczcM0Sdm7Fm91AvKn/el9 gEoP/N9r4o4sczXF2l/uPPBaEeszHzUVSmWVbwre4w6kHmO2KNMwlP21R4bfMxhQ 2VT0dUae7u9lnL3X2OswhuEDxI3jmziBbDS8Ie+KrfzxUS5r0Be7rIuvcBeSrDbY aPrU3g2JhIpAAnnrxoAFn2rAXUppZDczt1Yxt327xcw7eVf4f6U8lgFP26iHBar9 +gX1btHfmFfypcva6SHWERgUt8QHbE1YA2EjOiHlLfoOTOEplvHyqvKu7tLnm+wC bpWBefZ7DOIiLknTQW2RB1JopMA5w7Uq5yVY/KO+vp1RpJg4Iis= =+yON -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processed: affects 882804
Processing commands for cont...@bugs.debian.org: > affects 882804 rescue-mode Bug #882804 [cdebconf-gtk-udeb] cdebconf-gtk-udeb: Missing rescue mode label at start-up Added indication that 882804 affects rescue-mode > thanks Stopping processing here. Please contact me if you need assistance. -- 882804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#838503: debian-installer: mdadm should not start syncing RAID1 arrays at full speed during installation
Hi Cyril! Could You provide preseed variable for "dev.raid.speed_limit_max" sysctl setting? I want to adjust it to near acceptable value around 50Mbytes per second, because RAID 1 installation is really slow now regards Mikhail Zakharenko
Bug#882766: Proposal: reinstate automated device selection, blacklisting d-i?
> On Mon, 27 Nov 2017 00:15:23 +0100, Thomas Lange > said: > ls -l /dev/disk/by-label gives > Debian\x209.2.1\x20amd64\x20n -> ../../sr0 > This is a kvm virtual machine booting from CD. Booting real hardware from USB stick with an buster netinst shows Debian\x20buster-DO-a1\x20amd64\x20n -> ../../sdb1 After loading the additional components in the installer the USB stick is mounted from /dev/sdb1 to /cdrom. -- regards Thomas
Bug#838503: debian-installer: mdadm should not start syncing RAID1 arrays at full speed during installation
On Mon, 27 Nov 2017, Mikhail Zakharenko wrote: > Hi Cyril! > > Could You provide preseed variable for "dev.raid.speed_limit_max" sysctl > setting? > I want to adjust it to near acceptable value around 50Mbytes per second, > because RAID 1 installation is really slow now This seems like a bit of a kludge to me. Do dpkg pre and post hooks work in the context of d-i? If so, could we not just have a hook for dpkg install that tunes the max setting down low to avoid the conflict, and turn it back up again afterwards? I suspect that that would not result in a significant slow-down of the sync, while getting rid of the performance issue. To address the concern about leaving people with still-sync-ing systems post-reboot (which is not actually prevented by the status quo, I note) we could add an extra progress screen near the end of the install. It could track the progress of any remaining md sync (if any), while pointing out that cancelling out of the screen will do no harm, and will only mean that the sync that one is waiting for is going to be completed post reboot. A preseed variable to allow always skipping past that progress screen would seem like a reasonable thing to have, if we did all the above. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Re: Busybox 1.27 breaks kernel cmdline preseeding
On Fri, 24 Nov 2017, Raphael Hertzog wrote: > Apparently, kfreebsd has a working /proc/cmdline (thanks to linprocfs mounted > by default) so we might want to switch to that. I pushed a pu/kernel-cmdline-preseed branch implementing the preseeding out of /proc/cmdline. It's more elaborate than Mathieu's patch (https://paste.ubuntu.com/26034695/) in that it is able to handle multi-word values. I tested it locally and it fixes the rescue mode for me. For consistency, I renamed the command and the udeb, but the only place where it matters is in "debian-installer" itself where we have to update the package name. https://anonscm.debian.org/cgit/d-i/preseed.git/log/?h=pu/kernel-cmdline-preseed Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Re: Busybox 1.27 breaks kernel cmdline preseeding
On Mon, Nov 27, 2017 at 3:08 PM, Raphael Hertzog wrote: [...] > I pushed a pu/kernel-cmdline-preseed branch implementing the preseeding > out of /proc/cmdline. It's more elaborate than Mathieu's patch > (https://paste.ubuntu.com/26034695/) in that it is able to handle > multi-word values. > > I tested it locally and it fixes the rescue mode for me. For > consistency, I renamed the command and the udeb, but the only place > where it matters is in "debian-installer" itself where we have to update > the package name. > That will work on most arches, but not on kfreebsd/*. That said, the easy fix would be to look at both environment and /proc/cmdline. I *think* you only really need -e 's/\([^ =]*=[^ "]\)/\n\1/g' -e "s/\([^ =]*=[^ ']\)/\n\1/g" to multiline the entries and appropriately handle any multiword. With my limited testing it seemed to work well, and would be less complex than your solution ;) Did I miss some important corner-case? -- Mathieu Trudel-Lapierre Freenode: cyphermox, Jabber: mathieu...@gmail.com 4096R/65B58DA1 818A D123 0992 275B 23C2 CF89 C67B B4D6 65B5 8DA1
Bug#868848: debian-installer-utils: "list-devices partition" should report LVM logical volumes too
Control: tag -1 + pending Hi, On Sun, 29 Oct 2017, Colin Watson wrote: > I think this is basically a reasonable thing to do, but it seems to me > that it's going to cause rescue-mode to list LVs twice (see the > choose_root function). Could you fix that? A sensible approach would > probably be to exclude entries from LVMPARTS that are already in > PARTITIONS, and we can simplify that later once the new list-devices is > in place. I fixed that by simply deduplicating the entries (with sort -u) after having collated all entries to display. See https://anonscm.debian.org/cgit/d-i/rescue.git/commit/?id=cfcb7296b519f462395bcf7a63c1ed7da897b5d7 > > and I'm not convinced that it's really required either (it's not a > > requirement for iso-scan at least). I'm ccing Colin, he might have > > some insight to share on this. > > I could go either way on this, but I think it would probably make most > sense to exclude partitions already in use by VGs. "list-devices > partition" is generally used to offer menus of partitions to find > various files on, for which in-use PVs aren't going to be eligible; and > the LVM assembly code uses its own code to find partitions. Done. I pushed my changes. https://anonscm.debian.org/cgit/d-i/debian-installer-utils.git/commit/?id=7e7e7905fb9805244274b93ae5280354d642125b https://anonscm.debian.org/cgit/d-i/debian-installer-utils.git/commit/?id=3b2e9de85580f384e234aa787ae8a9e0b677f62e Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Processed: Re: Bug#868848: debian-installer-utils: "list-devices partition" should report LVM logical volumes too
Processing control commands: > tag -1 + pending Bug #868848 [src:debian-installer-utils] debian-installer-utils: "list-devices partition" should report LVM logical volumes too Added tag(s) pending. -- 868848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 868852
Processing commands for cont...@bugs.debian.org: > tags 868852 + pending Bug #868852 [src:debian-installer] debian-installer: hd-media images should have LVM support to find ISO in logical volumes Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 868852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Busybox 1.27 breaks kernel cmdline preseeding
Hi, On Mon, 27 Nov 2017, Mathieu Trudel-Lapierre wrote: > On Mon, Nov 27, 2017 at 3:08 PM, Raphael Hertzog wrote: > [...] > > I pushed a pu/kernel-cmdline-preseed branch implementing the preseeding > > out of /proc/cmdline. It's more elaborate than Mathieu's patch > > (https://paste.ubuntu.com/26034695/) in that it is able to handle > > multi-word values. > > > > I tested it locally and it fixes the rescue mode for me. For > > consistency, I renamed the command and the udeb, but the only place > > where it matters is in "debian-installer" itself where we have to update > > the package name. > > That will work on most arches, but not on kfreebsd/*. That said, the > easy fix would be to look at both environment and /proc/cmdline. We wants to stop using the environment because busybox hides it from us... I don't see the point of continuing to use it. Can you elaborate on what's wrong with /proc/cmdline on kfreebsd? We know that it exists. Are you saying that it doesn't contain the actual parameters passed on the kernel command line at boot time? I put debian-...@lists.debian.org in copy to have their feedback/advice. Is there any other way to get the parameters passed on the kernel command line? > I *think* you only really need -e 's/\([^ =]*=[^ "]\)/\n\1/g' -e > "s/\([^ =]*=[^ ']\)/\n\1/g" to multiline the entries and appropriately > handle any multiword. With my limited testing it seemed to work well, > and would be less complex than your solution ;) > > Did I miss some important corner-case? At least it does not cope well with parameters without any "=". Try adding words like "quiet" in the middle of your parameter list. They do not end up on a line of their own. I freely admit that my solution is complex but I was not able to find a simpler one that works well enough with my test case: language=fr_FR long?='1 2 3' rescue/enable="true" my/description="un message" --- quiet Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Re: Busybox 1.27 breaks kernel cmdline preseeding
On Mon, Nov 27, 2017 at 4:22 PM, Raphael Hertzog wrote: [...] > We wants to stop using the environment because busybox hides it from us... > I don't see the point of continuing to use it. I understand that; I tend to agree, modulo things not being listed in /proc/cmdline as below... > > Can you elaborate on what's wrong with /proc/cmdline on kfreebsd? We know > that it exists. Are you saying that it doesn't contain the actual > parameters passed on the kernel command line at boot time? > Correct; /proc/cmdline exists, but anything set up using: set kFreebsd.priority=high set kFreebsd.auto=true Which appears to me to be the current method for preseeding on the command-line (ie. at boot time; from grub); these options do not show up in /proc/cmdline in my testing. I tried to pass things after boot_one; but did not dig in any farther than that. There probably is another way to get this to work. [...] > At least it does not cope well with parameters without any "=". Try adding > words like "quiet" in the middle of your parameter list. They do not end > up on a line of their own. > > I freely admit that my solution is complex but I was not able to find a > simpler one that works well enough with my test case: > language=fr_FR long?='1 2 3' rescue/enable="true" my/description="un message" > --- quiet Yeah, I didn't have one of those in my test case. Oops. -- Mathieu Trudel-Lapierre Freenode: cyphermox, Jabber: mathieu...@gmail.com 4096R/65B58DA1 818A D123 0992 275B 23C2 CF89 C67B B4D6 65B5 8DA1
Re: Busybox 1.27 breaks kernel cmdline preseeding
On Mon, 27 Nov 2017, Mathieu Trudel-Lapierre
wrote:
> On Mon, Nov 27, 2017 at 3:08 PM, Raphael Hertzog wrote:
> [...]
>> I pushed a pu/kernel-cmdline-preseed branch implementing the preseeding
>> out of /proc/cmdline. It's more elaborate than Mathieu's patch
>> (https://paste.ubuntu.com/26034695/) in that it is able to handle
>> multi-word values.
>>
>> I tested it locally and it fixes the rescue mode for me. For
>> consistency, I renamed the command and the udeb, but the only place
>> where it matters is in "debian-installer" itself where we have to update
>> the package name.
>>
>
> That will work on most arches, but not on kfreebsd/*. That said, the
> easy fix would be to look at both environment and /proc/cmdline.
>
> I *think* you only really need -e 's/\([^ =]*=[^ "]\)/\n\1/g' -e
> "s/\([^ =]*=[^ ']\)/\n\1/g" to multiline the entries and appropriately
> handle any multiword. With my limited testing it seemed to work well,
> and would be less complex than your solution ;)
>
> Did I miss some important corner-case?
I'm not sure its important, but when testing a similar script I came up
with something that seems to give better results on the (perhaps
demented) test case I was playing with. Here's mine:
's/\([^= ]\+\|\([^= ]*=\("[^"]*"\|'"'[^']*'"'\|[^"'"'"' ][^ ]*\)\)\)\(
\|$\)/\1\n/g'
The sed is not as nice to look at though. I attach my test script.
BTW Should we actually be outputting the bits that contain no '=' for this?
If not, we could just pipe into:
grep =
Cheers, Phil.
signature.asc
Description: PGP signature
#!/bin/busybox sh
TEST='wibble x=y a/b="c '"'d'"' e" f=g h/j='"'k \"l\" m' foo bar aaa=bbb"
split_cmdline() {
# for testing, add this echo -- instead it should just have /proc/cmdline as sed's parameter
echo $TEST | busybox sed -e 's/\([^= ]\+\|\([^= ]*=\("[^"]*"\|'"'[^']*'"'\|[^"'"'"' ][^ ]*\)\)\)\( \|$\)/\1\n/g'
}
echo "=-=-=-=- Splitting: $TEST"
split_cmdline
echo "=-=-=-=-"
# to use merge this into the env, this should do the trick
# { split_cmdline ; set ; } | sort -u
--
|)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd.
|-| http://www.hands.com/http://ftp.uk.debian.org/
|(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY
Bug#875989: console-setup: generated cached_setup_keyboard.sh references /tmp/ file
Hi, I got same issue with this bug, and checked the details of bug. # stat /etc/console-setup/cached_ISO-8859-1_del.kmap.gz File: /etc/console-setup/cached_ISO-8859-1_del.kmap.gz Size: 4793 Blocks: 16 IO Block: 4096 regular file Device: 801h/2049dInode: 18350479Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) Access: 2017-01-29 19:32:33.001665826 +0900 Modify: 2017-11-28 14:10:18.621974890 +0900 Change: 2017-11-28 14:10:18.621974890 +0900 Birth: - # stat /etc/default/console-setup File: /etc/default/console-setup Size: 281 Blocks: 8 IO Block: 4096 regular file Device: 801h/2049dInode: 18350186Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) Access: 2017-11-28 14:10:18.009968364 +0900 Modify: 2017-11-28 14:10:18.005968321 +0900 Change: 2017-11-28 14:10:18.005968321 +0900 Birth: - Here is timestamps of some of affected files. Like above, FS is using nanoseconds timestamp, and cached is newer than config file (/etc/default/console-setup) as expected. But the issue in bash, # if [ /etc/default/console-setup -ot /etc/console-setup/cached_ISO-8859-1_del.kmap.gz ]; then echo yes; else echo no; fi no On debian, bash is not compiled with nanoseconds support (this seems be the bug of bash). So, if same timestamp in seconds resolution, setupcon confuses like the following log. + '[' -z '' -a -f /etc/console-setup/cached_ISO-8859-1_del.kmap.gz ']' + '[' /etc/default/keyboard -ot /etc/console-setup/cached_ISO-8859-1_del.kmap.gz -a /etc/default/console-setup -ot /etc/console-setup/cached_ISO-8859-1_del.kmap .gz ']' + '[' '' ']' + tempfile ++ mktemp /tmp/tmpkbd.XX + TMPFILE=/tmp/tmpkbd.kmP7z9 + tempfiles=' /tmp/tmpkbd.kmP7z9' So, my suggestion to fix this bug, choose the cached file if same timestamp, not only older. With this patch, seems to be working as expected in my case (if console-setup and cached_* was updated within same second). Thanks. --- setupcon~ 2017-11-28 14:33:16.030927321 +0900 +++ setupcon2017-11-28 15:05:46.735112236 +0900 @@ -1121,9 +1121,12 @@ if [ "$do_kbd" = linux ]; then fi fi +# If timestamp is same, use cached if \ -[ -z "$KMAP" -a -f "$cached" ] \ -&& [ "$CONFIG" -ot "$cached" -a "$CONFIG2" -ot "$cached" ] +[ -z "$KMAP" ] \ + && [ -f "$cached" ] \ + && [ ! "$cached" -ot "$CONFIG" ] \ + && [ ! "$cached" -ot "$CONFIG2" ] then KMAP="$cached" fi -- OGAWA Hirofumi
