Bug#798347: fdisk-udeb: not installable, depends on libtinfo5
Package: fdisk-udeb Version: 2.27-1 Severity: grave Justification: renders package unusable Hi, Your package gained a dependency on libtinfo5, which makes it no longer installable, along with lilo-installer and rescue-mode, which both depend on it. Example on mips: Depends: libblkid1-udeb (>= 2.25), libc6-udeb (>= 2.19), libfdisk1-udeb (>= 2.26), libsmartcols1-udeb (>= 2.25), libtinfo5 (>= 6), libuuid1-udeb (>= 2.20.1) Mraw, KiBi.
Bug#798373: netcfg: Change default wireless networking type from WEP to WPA
Package: netcfg
Version: 1.133
Severity: wishlist
Tags: patch
Hi,
I recently installed Debian over wireless and was a little surprised to
see WEP as default wireless networking type.
Even the cheapest & lamest consumer routers now use WPA so d-i should
probably reflect that, especially if a user is unsure they will
generally try the first option, assuming it to be the most likely. (In
other words, this is a UI wart, rather than a security one.)
(Patch attached merely for illustration; not sure if it's complete re.
translations.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/debian/netcfg-common.templates b/debian/netcfg-common.templates
index 4525305..508e02c 100644
--- a/debian/netcfg-common.templates
+++ b/debian/netcfg-common.templates
@@ -65,13 +65,13 @@ _Description: Wireless ESSID for ${iface}:
Template: netcfg/wireless_security_type
Type: select
-Choices-C: wep/open, wpa
-__Choices: WEP/Open Network, WPA/WPA2 PSK
+Choices-C: wpa, wep/open
+__Choices: WPA/WPA2 PSD, WEP/Open Network
# :sl2:
_Description: Wireless network type for ${iface}:
- Choose WEP/Open if the network is open or secured with WEP.
Choose WPA/WPA2 if the network is protected with WPA/WPA2 PSK
(Pre-Shared Key).
+ Choose WEP/Open if the network is open or secured with WEP.
Template: netcfg/wireless_wep
Type: string
mips CDs (was Re: Dropping CDs entirely?! (was: Stretch Alpha 3 images))
On Sun, Sep 06, 2015 at 03:35:48PM +0200, Aurelien Jarno wrote: >On 2015-09-06 14:25, Thomas Schmitt wrote: >> Hi, >> >> Aurelien Jarno wrote: >> > I have no idea if they support booting over a >> > CD-ROM or USB image. Does someone known if we can do so on a Loongson 3 >> > or Octeon machine? >> >> Maybe one should ask grub-de...@gnu.org mailing list or >> Vladimir Serbinenko directly. > >GRUB only works on the Loongson 2 machines, not the Loongson 3 ones. >Given we are going to drop the Loongson 2 support soon, there is no >point trying to get it working for CD-ROM booting. ACK. We're similar on armel and armhf too. What *would* be useful on the CD/DVD for people wanting to start the installer by hand, though? I'm thinking for people ready to copy bits onto an SD card or similar... -- Steve McIntyre, Cambridge, UK.st...@einval.com "I suspect most samba developers are already technically insane... Of course, since many of them are Australians, you can't tell." -- Linus Torvalds
Bug#798376: debian-installer: configuring the network device fails on s390x if network devive is virtio_net and not qeth
Package: debian-installer
Severity: important
Dear Maintainer,
I would like to bring the following problem with the debian-installer to your
attention:
I tried to install Debian 8.0/8.1i/8.2 in a virtual machine on "KVM on IBM
System z". The installation can not completed, because the network device can
not be configured and the following message is displayed:
[!!] Configure a network using static addressing
Installation step failed
An installation step failed. You can try to run the failing item
again from the menu, or skip it and choose something else. The
failing step is: Configure a network using static addressing
Further analysis shows that the installer insists on having a qeth network
device, which is obivously not there because the VM has a virtio_net device.
Sep 4 13:24:37 netcfg-static[183]: INFO: Found link on eth0
Sep 4 13:24:37 netcfg-static[183]: ERROR **: no qeth found: virtio_net
Sep 4 13:24:37 main-menu[159]: WARNING **: Configuring 'netcfg-static' failed
with error code 1
Sep 4 13:24:37 main-menu[159]: WARNING **: Menu item 'netcfg-static' failed.
Sep 4 13:24:39 main-menu[159]: INFO: Modifying debconf priority limit from
'high' to 'medium'
Sep 4 13:24:39 debconf: Setting debconf/priority to medium
Looking at the source code of the installer it seems in case of a s390x it is
assumed that the network driver should be "qeth".
"./packages/netcfg/netcfg-common.c" 1736L, 49379C
#if defined(__s390__)
// Layer 3 qeth on s390(x) cannot do arping to test gateway reachability.
int is_layer3_qeth(const char *iface)
{
.
if (strcmp(driver, "qeth") != 0) {
di_error("no qeth found: %s", driver);
goto out;
}
This assumption is no longer true with a VM for "KVM on IBM System z" and
prevents installing a Debian VM from ISO. There are workarounds to get a Debian
VM up and running, but the simple way to install from ISO is not working.
Please let me know if I can be of further help,
Regards, Gerhard Stenzel
Bug#798373: netcfg: Change default wireless networking type from WEP to WPA
Hi,
Chris Lamb (2015-09-08):
> Package: netcfg
> Version: 1.133
> Severity: wishlist
> Tags: patch
>
> Hi,
>
> I recently installed Debian over wireless and was a little surprised to
> see WEP as default wireless networking type.
>
> Even the cheapest & lamest consumer routers now use WPA so d-i should
> probably reflect that, especially if a user is unsure they will
> generally try the first option, assuming it to be the most likely. (In
> other words, this is a UI wart, rather than a security one.)
>
> (Patch attached merely for illustration; not sure if it's complete re.
> translations.)
I'm surprised as well.
> diff --git a/debian/netcfg-common.templates b/debian/netcfg-common.templates
> index 4525305..508e02c 100644
> --- a/debian/netcfg-common.templates
> +++ b/debian/netcfg-common.templates
> @@ -65,13 +65,13 @@ _Description: Wireless ESSID for ${iface}:
>
> Template: netcfg/wireless_security_type
> Type: select
> -Choices-C: wep/open, wpa
> -__Choices: WEP/Open Network, WPA/WPA2 PSK
> +Choices-C: wpa, wep/open
> +__Choices: WPA/WPA2 PSD, WEP/Open Network
> # :sl2:
> _Description: Wireless network type for ${iface}:
> - Choose WEP/Open if the network is open or secured with WEP.
> Choose WPA/WPA2 if the network is protected with WPA/WPA2 PSK
> (Pre-Shared Key).
> + Choose WEP/Open if the network is open or secured with WEP.
>
> Template: netcfg/wireless_wep
> Type: string
I suppose adding a “Default” field would render the translation topic
moot and would be more explicit than depending on the order of the
values in the Choices-C field?
Mraw,
KiBi.
signature.asc
Description: Digital signature
Re: Bug#798347: fdisk-udeb: not installable, depends on libtinfo5
(Adding -boot@ for further discussion.) Hi, Andreas Henriksson (2015-09-08): > Hello Cyril Brulebois. > > Thanks for your bug report. > > On Tue, Sep 08, 2015 at 01:13:58PM +0200, Cyril Brulebois wrote: > > Package: fdisk-udeb > > Version: 2.27-1 > > Severity: grave > > Justification: renders package unusable > > > > Hi, > > > > Your package gained a dependency on libtinfo5, which makes it no longer > > installable, along with lilo-installer and rescue-mode, which both > > depend on it. > [...] > > Sorry for screwing up the udebs (again!). Would be nice to have lintian > catch this... > > I'm pondering just building static versions of fdisk,sfdisk,blkid > to put in the udebs instead to avoid current and future dependency > issues. Would that be acceptable? > > (That would also mean I can remove lib*-udeb.) Assuming nothing else using the lib*-udeb (I didn't check), I don't think there are compelling reasons for keeping those around. Having everything shipped into a single udeb doesn't seem crazy (if nothing else from other sources is expected toever depend on those features) and if that makes things easier for you, great! Historically, we've had a bunch of udebs built with specific options, be it to reduce size, dependencies/features, and I suppose (again, not going to check) static bits. I'm currently (this week, probably next) to give your updated package a look/try, I'm sorry. > The result would look like this: > > root@mbpah:~/util-linux-2.27# dpkg -c ../fdisk-udeb_2.27-2_amd64.udeb > drwxr-xr-x root/root 0 2015-09-08 15:17 ./ > drwxr-xr-x root/root 0 2015-09-08 15:17 ./usr/ > drwxr-xr-x root/root 0 2015-09-08 15:17 ./usr/sbin/ > -rwxr-xr-x root/root 1385224 2015-09-08 15:17 ./usr/sbin/fdisk > -rwxr-xr-x root/root 1378376 2015-09-08 15:17 ./usr/sbin/sfdisk > root@mbpah:~/util-linux-2.27# dpkg -I ../fdisk-udeb_2.27-2_amd64.udeb > new debian package, version 2.0. > size 972626 bytes: control archive=329 bytes. > 287 bytes,10 lines control > Package: fdisk-udeb > Source: util-linux > Version: 2.27-2 > Architecture: amd64 > Installer-Menu-Item: 9 > Maintainer: Debian util-linux Maintainers > Installed-Size: 2704 > Section: debian-installer > Priority: extra > Description: Manually partition a hard drive (fdisk) > > root@mbpah:~/util-linux-2.27# dpkg -c ../util-linux-udeb_2.27-2_amd64.udeb > drwxr-xr-x root/root 0 2015-09-08 15:17 ./ > drwxr-xr-x root/root 0 2015-09-08 15:17 ./sbin/ > -rwxr-xr-x root/root993064 2015-09-08 15:17 ./sbin/blkid > root@mbpah:~/util-linux-2.27# dpkg -I ../util-linux-udeb_2.27-2_amd64.udeb > new debian package, version 2.0. > size 347790 bytes: control archive=378 bytes. > 407 bytes,11 lines control > Package: util-linux-udeb > Source: util-linux > Version: 2.27-2 > Architecture: amd64 > Maintainer: Debian util-linux Maintainers > Installed-Size: 973 > Section: debian-installer > Priority: optional > Description: stripped down miscellaneous system utilities, for > debian-installer > This is a minimal version of util-linux for debian-installer. It only > contains the blkid binary at the moment. > > > Patch attached to accomplish this (which should be extended with > lib*-udeb removal). > > Regards, > Andreas Henriksson > diff --git a/debian/changelog b/debian/changelog > index f1af685..6b915af 100644 > --- a/debian/changelog > +++ b/debian/changelog > @@ -1,3 +1,10 @@ > +util-linux (2.27-2) UNRELEASED; urgency=medium > + > + * Build static binaries for fdisk-udeb and util-linux-udeb (Closes: > #798347) > +- this avoids udeb collecting invalid dependencies on non-udebs > + > + -- Andreas Henriksson Tue, 08 Sep 2015 17:00:05 +0200 > + > util-linux (2.27-1) unstable; urgency=medium > >[ Andreas Henriksson ] > diff --git a/debian/fdisk-udeb.install b/debian/fdisk-udeb.install > index 9cbe2fb..3aaf029 100755 > --- a/debian/fdisk-udeb.install > +++ b/debian/fdisk-udeb.install > @@ -1,3 +1,3 @@ > #!/usr/bin/dh-exec > -sbin/fdisk usr/sbin > -sbin/sfdisk usr/sbin > +./fdisk.static => /usr/sbin/fdisk > +./sfdisk.static => /usr/sbin/sfdisk > diff --git a/debian/rules b/debian/rules > index 660d55f..4f36861 100755 > --- a/debian/rules > +++ b/debian/rules > @@ -19,6 +19,9 @@ endif > CONFOPTS += --enable-tunelp > endif > > +# build static versions of programs used in fdisk-udeb and util-linux-udeb > +CONFOPTS += --enable-static-programs=fdisk,sfdisk,blkid > + > CONFOPTS += --localstatedir=/run > CONFOPTS += --disable-silent-rules > CONFOPTS += --without-python > diff --git a/debian/util-linux-udeb.install b/debian/util-linux-udeb.install > old mode 100644 > new mode 100755 > index 022f38d..9a089cf > --- a/debian/util-linux-udeb.install > +++ b/debian/util-linux-udeb.install > @@ -1 +1,2 @@ > -sbin/blkid > +#!/usr/bin/dh-exec > +./blkid.static => /sbin/blkid Mraw, KiBi. signature.asc Description: Digital signat
Re: Bug#798347: fdisk-udeb: not installable, depends on libtinfo5
Cyril Brulebois, le Tue 08 Sep 2015 17:39:24 +0200, a écrit : > (Adding -boot@ for further discussion.) > > I'm pondering just building static versions of fdisk,sfdisk,blkid > > to put in the udebs instead to avoid current and future dependency > > issues. Would that be acceptable? > > > > (That would also mean I can remove lib*-udeb.) You could link just libtinfo.a statically. Samuel
Re: Bug#798347: fdisk-udeb: not installable, depends on libtinfo5
Hello. On Tue, Sep 08, 2015 at 05:47:13PM +0200, Samuel Thibault wrote: > Cyril Brulebois, le Tue 08 Sep 2015 17:39:24 +0200, a écrit : > > (Adding -boot@ for further discussion.) > > > I'm pondering just building static versions of fdisk,sfdisk,blkid > > > to put in the udebs instead to avoid current and future dependency > > > issues. Would that be acceptable? > > > > > > (That would also mean I can remove lib*-udeb.) > > You could link just libtinfo.a statically. Another option would probably also be to work out how to get rid of the dependency on libtinfo (for udebs atleast). (There's a configure switch to disable tinfo already, but I guess we want it enabled for regular builds and would like to avoid double builds.) This would probably mean I walk into the same trap again in the future with some other library. Building it completely static is really simple for me and makes sure no (non-udeb or other) dependencies gets picked up in the future and avoids me reintroducing grave bugs. Any issues would be noticed at build-time (eg. if something does not provide a static lib). I'd feel best if I can just forget about udeb existance and building static version of fdisk,sfdisk,blkid seems like it could take away the most common pitfall for me. Are there any issues I should be aware of that would outweigh the benefits mentioned above? (I'm aware it's not perfectly optimal to build staticly, but can anyone forsee any actual practical or policy issue with doing so?) Regards, Andreas Henriksson
Re: Bug#798347: fdisk-udeb: not installable, depends on libtinfo5
Andreas Henriksson, le Tue 08 Sep 2015 18:01:08 +0200, a écrit : > Are there any issues I should be aware of that would outweigh the > benefits mentioned above? (I'm aware it's not perfectly optimal > to build staticly, but can anyone forsee any actual practical or > policy issue with doing so?) The static binary will carry possibly outdated copies of the library (potentially with bugs etc.). The size may also matter for embedded archs. Samuel
Bug#798373: netcfg: Change default wireless networking type from WEP to WPA
Quoting Cyril Brulebois (k...@debian.org):
> > Template: netcfg/wireless_security_type
> > Type: select
> > -Choices-C: wep/open, wpa
> > -__Choices: WEP/Open Network, WPA/WPA2 PSK
> > +Choices-C: wpa, wep/open
> > +__Choices: WPA/WPA2 PSD, WEP/Open Network
> > # :sl2:
> > _Description: Wireless network type for ${iface}:
> > - Choose WEP/Open if the network is open or secured with WEP.
> > Choose WPA/WPA2 if the network is protected with WPA/WPA2 PSK
> > (Pre-Shared Key).
> > + Choose WEP/Open if the network is open or secured with WEP.
> >
> > Template: netcfg/wireless_wep
> > Type: string
>
> I suppose adding a “Default” field would render the translation topic
> moot and would be more explicit than depending on the order of the
> values in the Choices-C field?
Yes, we definitely want a Default: field to not depend on the options'
order. I see nothing related to translations. Chris' patch was already
OK wrt i18n.
signature.asc
Description: Digital signature
Bug#798373: netcfg: Change default wireless networking type from WEP to WPA
Kibi wrote:
> I suppose adding a “Default” field would render the translation topic
> moot and would be more explicit than depending on the order of the
> values in the Choices-C field?
Ah, of course! Updated patch attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/debian/netcfg-common.templates b/debian/netcfg-common.templates
index 4525305..d1de469 100644
--- a/debian/netcfg-common.templates
+++ b/debian/netcfg-common.templates
@@ -65,6 +65,7 @@ _Description: Wireless ESSID for ${iface}:
Template: netcfg/wireless_security_type
Type: select
+Default: WPA/WPA2 PSK
Choices-C: wep/open, wpa
__Choices: WEP/Open Network, WPA/WPA2 PSK
# :sl2:
Bug#798373: netcfg: Change default wireless networking type from WEP to WPA
Quoting Chris Lamb (la...@debian.org): > Kibi wrote: > > > I suppose adding a “Default” field would render the translation topic > > moot and would be more explicit than depending on the order of the > > values in the Choices-C field? > > Ah, of course! Updated patch attached. > Template: netcfg/wireless_security_type > Type: select > +Default: WPA/WPA2 PSK > Choices-C: wep/open, wpa > __Choices: WEP/Open Network, WPA/WPA2 PSK > # :sl2: Thanks, Chris, However, Default: should match the choice you want, but in Choices-C, therefore it should be "wpa" alone. -- signature.asc Description: Digital signature
