Bug#1051345: ca-certificates: update-ca-certificates does not recreate ca-certificates.crt if all certificates are deselected
Package: ca-certificates Version: 20230311ubuntu0.22.04.1 Severity: normal Dear Maintainer, I wanted to disable all the certificates provided by the ca-certificates package, and only include my own. Upon doing so, and running update-ca-certificates, I found that /etc/ssl/certs/ca-certificates.crt contained all the old certificates. To reproduce: 1. install package 2. deselect all listed entries in ca-certificates.conf sed -i '/^[^#!]/s/^/!/' /etc/ca-certificates.conf 3. run update-ca-certificates, see that /etc/ssl/certs/ca-certificates.crt is unmodified. The bug in update-ca-certificates is that the TEMPBUNDLE file is never created if the 'add' function is never called. If the TEMPBUNDLE file does not exist, then it will not be moved into place at the end. -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy') Architecture: amd64 (x86_64) Kernel: Linux 6.2.0-32-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ca-certificates depends on: ii debconf [debconf-2.0] 1.5.79ubuntu1 ii openssl3.0.2-0ubuntu1.10 ca-certificates recommends no packages. ca-certificates suggests no packages. -- debconf information excluded
Bug#1025706: example patch
Attached is a debdiff against 1.0.3-3 that is "working for me" so far. diff --git a/debian/changelog b/debian/changelog index b641b61..33801af 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +squashfuse (0.1.105-1) unstable; urgency=medium + + * New upstream release. + * Link against libfuse3 rather than libfuse2 (Closes: #1025706). + * debian/patches/* - drop patches. + + -- Scott Moser Wed, 07 Dec 2022 16:33:06 -0500 + squashfuse (0.1.103-3) unstable; urgency=medium * Fix "Switch from deprecated to " diff --git a/debian/control b/debian/control index 1b0f6f7..ea84c4f 100644 --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Section: utils Priority: optional Maintainer: Scarlett Moore Build-Depends: debhelper-compat (= 13), - libfuse-dev, + libfuse3-dev, liblz4-dev, liblzma-dev, liblzo2-dev, diff --git a/debian/libfuseprivate0.install b/debian/libfuseprivate0.install deleted file mode 100644 index d6268cc..000 --- a/debian/libfuseprivate0.install +++ /dev/null @@ -1 +0,0 @@ -usr/lib/*/libfuseprivate.so.* diff --git a/debian/libsquashfuse-dev.install b/debian/libsquashfuse-dev.install index b2eb5cd..f21b6a1 100644 --- a/debian/libsquashfuse-dev.install +++ b/debian/libsquashfuse-dev.install @@ -2,3 +2,4 @@ usr/include/ usr/lib/*/*.a usr/lib/*/*.so usr/lib/*/pkgconfig/squashfuse.pc +usr/lib/*/pkgconfig/squashfuse_ll.pc diff --git a/debian/libsquashfuse0.install b/debian/libsquashfuse0.install index 3ef587c..7f296f1 100644 --- a/debian/libsquashfuse0.install +++ b/debian/libsquashfuse0.install @@ -1,3 +1,2 @@ -usr/lib/*/libfuseprivate.so.* usr/lib/*/libsquashfuse.so.* usr/lib/*/libsquashfuse_ll.so.* diff --git a/debian/libsquashfuse0.symbols b/debian/libsquashfuse0.symbols index c755067..b3b0383 100644 --- a/debian/libsquashfuse0.symbols +++ b/debian/libsquashfuse0.symbols @@ -1,11 +1,3 @@ -libfuseprivate.so.0 libsquashfuse0 #MINVER# -* Build-Depends-Package: libsquashfuse-dev - sqfs_enoattr@Base 0.0.0 - sqfs_listxattr@Base 0.0.0 - sqfs_makedev@Base 0.0.0 - sqfs_opt_proc@Base 0.0.0 - sqfs_stat@Base 0.0.0 - sqfs_usage@Base 0.0.0 libsquashfuse.so.0 libsquashfuse0 #MINVER# * Build-Depends-Package: libsquashfuse-dev sqfs_block_cache_init@Base 0.0.0 @@ -79,12 +71,6 @@ libsquashfuse.so.0 libsquashfuse0 #MINVER# sqfs_stack_size@Base 0.0.0 sqfs_stack_top@Base 0.0.0 sqfs_swap16@Base 0.0.0 - sqfs_swapin16@Base 0.0.0 - sqfs_swapin16_internal@Base 0.0.0 - sqfs_swapin32@Base 0.0.0 - sqfs_swapin32_internal@Base 0.0.0 - sqfs_swapin64@Base 0.0.0 - sqfs_swapin64_internal@Base 0.0.0 sqfs_swapin_base_inode@Base 0.0.0 sqfs_swapin_dev_inode@Base 0.0.0 sqfs_swapin_dir_entry@Base 0.0.0 @@ -127,10 +113,148 @@ libsquashfuse.so.0 libsquashfuse0 #MINVER# sqfs_xattr_value_size@Base 0.0.0 libsquashfuse_ll.so.0 libsquashfuse0 #MINVER# * Build-Depends-Package: libsquashfuse-dev - fusefs_main@Base 0.1.103 + alarm_tick@Base 0.0.0 + setup_idle_timeout@Base 0.0.0 + sqfs_block_cache_init@Base 0.0.0 + sqfs_block_dispose@Base 0.0.0 + sqfs_block_read@Base 0.0.0 + sqfs_blockidx_add@Base 0.0.0 + sqfs_blockidx_blocklist@Base 0.0.0 + sqfs_blockidx_init@Base 0.0.0 + sqfs_blocklist_count@Base 0.0.0 + sqfs_blocklist_init@Base 0.0.0 + sqfs_blocklist_next@Base 0.0.0 + sqfs_cache_add@Base 0.0.0 + sqfs_cache_destroy@Base 0.0.0 + sqfs_cache_get@Base 0.0.0 + sqfs_cache_init@Base 0.0.0 + sqfs_cache_invalidate@Base 0.0.0 + sqfs_compression@Base 0.0.0 + sqfs_compression_name@Base 0.0.0 + sqfs_compression_supported@Base 0.0.0 + sqfs_data_block_read@Base 0.0.0 + sqfs_data_cache@Base 0.0.0 + sqfs_data_header@Base 0.0.0 + sqfs_decompressor_get@Base 0.0.0 + sqfs_dentry_init@Base 0.0.0 + sqfs_dentry_inode@Base 0.0.0 + sqfs_dentry_inode_num@Base 0.0.0 + sqfs_dentry_is_dir@Base 0.0.0 + sqfs_dentry_mode@Base 0.0.0 + sqfs_dentry_name@Base 0.0.0 + sqfs_dentry_name_size@Base 0.0.0 + sqfs_dentry_next_offset@Base 0.0.0 + sqfs_dentry_offset@Base 0.0.0 + sqfs_dentry_type@Base 0.0.0 + sqfs_destroy@Base 0.0.0 + sqfs_dir_lookup@Base 0.0.0 + sqfs_dir_next@Base 0.0.0 + sqfs_dir_open@Base 0.0.0 + sqfs_divceil@Base 0.0.0 + sqfs_enoattr@Base 0.0.0 + sqfs_export_inode@Base 0.0.0 + sqfs_export_ok@Base 0.0.0 + sqfs_fd_close@Base 0.0.0 + sqfs_fd_open@Base 0.0.0 + sqfs_frag_block@Base 0.0.0 + sqfs_frag_entry@Base 0.0.0 + sqfs_hash_add@Base 0.0.0 + sqfs_hash_destroy@Base 0.0.0 + sqfs_hash_get@Base 0.0.0 + sqfs_hash_init@Base 0.0.0 + sqfs_hash_remove@Base 0.0.0 + sqfs_id_get@Base 0.0.0 + sqfs_init@Base 0.0.0 + sqfs_inode_get@Base 0.0.0 + sqfs_inode_root@Base 0.0.0 + sqfs_listxattr@Base 0.0.0 + sqfs_ll_add_direntry@Base 0.0.0 sqfs_ll_daemonize@Base 0.1.103 sqfs_ll_destroy@Base 0.1.103 sqfs_ll_iget@Base 0.1.103 sqfs_ll_init@Base 0.1.103 sqfs_ll_inode@Base 0.1.103 + sqfs_ll_mount@Base 0.0.0 + sqfs_ll_op_create@Base 0.0.0 + sqfs_ll_op_forget@Base 0.0.0 + sqfs_ll_op_getattr@Base 0.0.0 + sqfs_ll_op_getxattr@Base 0.0.0 +
Bug#1025706: squashfuse: link against fuse3
Package: squashfuse Version: 0.1.103-3 Severity: normal Dear Maintainer, squashfuse should be built against libfuse3 rather than libfuse2. The current/supported version of libfuse is 3 and squashfuse supports linking and running with libfuse3. There are some existing issues that are fixed by using libfuse3 [1] and it is surely a better upstream support path. [1] https://github.com/vasi/squashfuse/issues/80 -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-53-generic (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages squashfuse depends on: ii libc6 2.35-0ubuntu3.1 ii libfuse22.9.9-5ubuntu3.1 ii libsquashfuse0 0.1.103-3 squashfuse recommends no packages. squashfuse suggests no packages. -- no debconf information
Bug#987320: dracut: Version is not included in --version, --help or initramfs runtime
I'm not sure if its 100% OK to do it, but what we do in cloud-init similarly is is just write the file in debian/rules, and reference DEB_VERSION. That way you even get the packaging number which could be helpful. https://github.com/canonical/cloud-init/blob/ubuntu/devel/debian/rules On Tue, Apr 27, 2021 at 5:39 AM Thomas Lange wrote: > > I can confirm this bug. > > I guess the dracut version is created during the build of the package > extracted from some git tags if avalable. Since I have to do source > only upload to Debian, the git information is missing and so > the version information is empty > > # cat /usr/lib/dracut/dracut-version.sh > DRACUT_VERSION= > > I'll try to work around this in the next version. > > -- > viele Grüße Thomas
Bug#987320: dracut: Version is not included in --version, --help or initramfs runtime
Package: dracut Version: 051-1 Severity: normal Dear Maintainer, The dracut package does not seem to 'know' its own version. Example: $ cat /lib/dracut/dracut-version.sh DRACUT_VERSION= $ dracut --version dracut $ dpkg-query --show dracut-core dracut-core 051-1 $ dracut --help | head -n 5 Usage: /usr/bin/dracut [OPTION]... [ []] Version: Creates initial ramdisk images for preloading modules This is admittedly a minor issue, but also manifests itself in the initramfs that is created by 'dracut'. It means an initramfs module cannot make decisions based on the dracut version. The fix seems simple enough: % echo DRACUT_VERSION=051-1 > /lib/dracut/dracut-version.sh % dracut --version dracut 051-1 So you just need to manage to write the version to that file during package build. -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-45-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dracut depends on: pn dracut-core dracut recommends no packages. Versions of packages dracut suggests: pn dracut-network
Bug#960941: ofono-phonesim: Re-add ofono-phonesim as it is updated to use qt5
Package: ofono-phonesim Version: 1.21-16-gadf231a8-0smoser0 Severity: important Dear Maintainer, Ofono-phonesim got dropped under bug #940141. The justification was "It depends on Qt4 and is dead upstream". Soon after the release of 1.21 upstream was ported to QT5. To my knowledge, this package is still required to make some bluetooth headsets work in HSP/HFP mode with pulseaudio [1]. At least for my headset, I have not found another way. A future solution my include hsphfpd, but that is not currently a work in progress upstream. I have an updated source package with version 1.21-16-gadf231a8-0 at [2]. The only change required was the Build-Depends and a new upstream snapshot. Thanks. [1] https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Bluetooth/#usinghfpwithofono [2] https://launchpad.net/~smoser/+archive/ubuntu/bluetooth . [3] https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/94 -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-29-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ofono-phonesim depends on: ii libc6 2.31-0ubuntu9 ii libgcc-s1 10-20200411-0ubuntu1 ii libqt5core5a5.12.8+dfsg-0ubuntu1 ii libqt5dbus5 5.12.8+dfsg-0ubuntu1 ii libqt5gui5 5.12.8+dfsg-0ubuntu1 ii libqt5network5 5.12.8+dfsg-0ubuntu1 ii libqt5qml5 5.12.8-0ubuntu1 ii libqt5widgets5 5.12.8+dfsg-0ubuntu1 ii libstdc++6 10-20200411-0ubuntu1 ofono-phonesim recommends no packages. ofono-phonesim suggests no packages. -- no debconf information diff --git a/debian/changelog b/debian/changelog index 57ba1d1..ee52714 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +ofono-phonesim (1.21-16-gadf231a8-0) unstable; urgency=medium + + * New upstream snapshot. Upstream ported to QT5. + * debian/control: replace qt4 deps with qt5. + + -- Scott Moser Fri, 17 Apr 2020 16:48:09 -0400 + ofono-phonesim (1.21-1) unstable; urgency=medium [ Jonny Lamb ] diff --git a/debian/control b/debian/control index a14b6e6..9797e90 100644 --- a/debian/control +++ b/debian/control @@ -5,7 +5,8 @@ Maintainer: Debian Telepathy maintainers Build-Depends: debhelper (>= 11), pkg-config, - libqt4-dev + qtbase5-dev, + qtdeclarative5-dev Standards-Version: 4.3.0 Rules-Requires-Root: no Homepage: http://www.ofono.org/
Bug#812574: ubuntu bug 564853
This is also reported in ubuntu bug 564853 (https://bugs.launchpad.net/bugs/564853). There is a recreate script attached to the bug there. As diagnosed there, the prompt will occur if the user has made *both*: a. changes to grub-pc.postinst fields: GRUB_CMDLINE_LINUX, GRUB_CMDLINE_LINUX_DEFAULT, GRUB_TIMEOUT, GRUB_HIDDEN_TIMEOUT b. any other changes
Bug#908160: FTBFS: build from source fails with undefined reference to `minor'
Package: open-iscsi Version: 2.0.874-5ubuntu7 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) Current build of open-iscsi (2.0.874-5ubuntu7) will fail to build from source. Build fails with: ./iscsiuio/src/unix/libs/bnx2x.c:754: undefined reference to `minor' collect2: error: ld returned 1 exit status This is reported to Ubuntu in bug 1791154 https://bugs.launchpad.net/bugs/1791154 Attached is the fix I am uploading to Ubuntu. -- System Information: Debian Release: buster/sid APT prefers cosmic APT policy: (500, 'cosmic') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-9-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages open-iscsi depends on: ii debconf [debconf-2.0] 1.5.69 ii libc6 2.28-0ubuntu1 ii libisns0 0.97-2build1 ii libmount1 2.32-0.1ubuntu1 ii lsb-base 9.20170808ubuntu1 ii udev 239-7ubuntu7 Versions of packages open-iscsi recommends: ii busybox-initramfs 1:1.27.2-2ubuntu4 ii finalrd3 open-iscsi suggests no packages. -- debconf information excluded commit e8ddf2765525522924a03f668220ba8f256a58d8 Author: Scott Moser Date: Thu Sep 6 15:38:20 2018 -0400 Include to properly define minor() LP: #1791154 diff --git a/debian/patches/bugfixes/include-sys-sysmacros.h-to-properly-define-minor.patch b/debian/patches/bugfixes/include-sys-sysmacros.h-to-properly-define-minor.patch new file mode 100644 index ..ba92af5f --- /dev/null +++ b/debian/patches/bugfixes/include-sys-sysmacros.h-to-properly-define-minor.patch @@ -0,0 +1,28 @@ +Description: Include to properly define minor() +Author: Scott Moser +Bug-Debian: https://bugs.launchpad.net/bugs/1791154 +Last-Update: 2018-09-06 +Origin: upstream, https://github.com/open-iscsi/open-iscsi/commit/6d68ef5871c94c6ebbbe6e6b1fe0bc2dce711052 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ + +--- a/iscsiuio/src/unix/libs/bnx2x.c b/iscsiuio/src/unix/libs/bnx2x.c +@@ -50,6 +50,7 @@ + #include + #include + #include ++#include + + #include "config.h" + +--- a/iscsiuio/src/unix/libs/bnx2.c b/iscsiuio/src/unix/libs/bnx2.c +@@ -46,6 +46,7 @@ + #include + #include + #include ++#include + + #include "config.h" + diff --git a/debian/patches/series b/debian/patches/series index 34608a68..d98a5c63 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -13,3 +13,4 @@ security/Ensure-strings-from-peer-are-copied-correctly.patch security/Skip-useless-strcopy-and-validate-CIDR-length.patch security/Check-iscsiuio-ping-data-length-for-validity.patch iscid-conf-use-systemd.socket-patch +bugfixes/include-sys-sysmacros.h-to-properly-define-minor.patch
Bug#907235: python3-scapy: Please provide package without large 'Recommends'
Package: python3-scapy Version: 2.4.0-2 Severity: normal Dear Maintainer, The current version (2.4.0-2) of python3-scapy has Recommends Recommends: tcpdump, ipython3, python3-matplotlib, python3-pyx, graphviz Version 2.3.3-3 had those as 'Suggests'. The change on "Recommends by default" systems such as Ubuntu means that any package that wants to Depend on scapy gets a huge stack of additional packages installed. A fresh ubuntu server install means currently adding python3-scapy will bring in 202 newly installed packages taking 583MB. Could the Recommends be moved back to Suggests? Alternatively, a package could be added 'scapy' that included the dependencies while the python3-scapy would only provide the python library itself. Thanks, Scott -- System Information: Debian Release: buster/sid APT prefers cosmic APT policy: (500, 'cosmic') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-6-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-scapy depends on: ii python3 3.6.6-1 Versions of packages python3-scapy recommends: ii graphviz2.40.1-3 ii ipython35.5.0-1 pn python3-matplotlib pn python3-pyx ii tcpdump 4.9.2-3 Versions of packages python3-scapy suggests: ii ebtables 2.0.10.4-3.5ubuntu5 pn gv pn hexer ii imagemagick 8:6.9.10.2+dfsg-3ubuntu2 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.2+dfsg-3ubuntu2 pn librsvg2-bin ii python3-crypto 2.6.1-9build1 pn python3-geoip ii sox 14.4.2-3 pn tcpreplay pn wireshark -- no debconf information
Bug#895377: /usr/bin/pristine-tar: add support for specifing branch name to pristine-tar cli
Package: pristine-tar
Version: 1.42
Severity: normal
File: /usr/bin/pristine-tar
Tags: patch
Dear Maintainer,
git-ubuntu is using pristine-tar. git-ubuntu tracks archive versions
of both ubuntu and debian packages (and orig tarballs). Because of the
fact that sometimes orig tarballs have differed within the same version
of a package, the pristine-tar branches are namespaced:
importer/ubuntu/pristine-tar
importer/debian/pristine-tar
In order for git-ubuntu to use the 'pristine-tar' cli, then to extract
original source tarballs we need to be able to specify the branch name.
So this is a request (and attached patch) for adding a '--branch' flag
to pristine-tar.
-- System Information:
Debian Release: buster/sid
APT prefers bionic
APT policy: (500, 'bionic')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-13-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pristine-tar depends on:
ii libbz2-1.0 1.0.6-8.1
ii libc6 2.27-0ubuntu3
ii perl5.26.1-5
ii tar 1.29b-2
ii xdelta 1.1.3-9.2
ii xdelta3 3.0.11-dfsg-1ubuntu1
ii zlib1g 1:1.2.11.dfsg-0ubuntu2
Versions of packages pristine-tar recommends:
ii bzip2 1.0.6-8.1
ii pbzip21.1.9-1build1
ii xz-utils 5.2.2-1.3
pristine-tar suggests no packages.
-- no debconf information
>From d9fdae97e557b4e7de28ad3bce1d662fe14885c5 Mon Sep 17 00:00:00 2001
From: Scott Moser <smo...@brickies.net>
Date: Tue, 10 Apr 2018 15:00:39 -0400
Subject: [PATCH] pristine-tar: add -b/--branch flag for specifying the branch.
Some repositories may not have the same naming convention for the
pristine-tar branch. One such example is the 'git ubuntu' work
that is being done.
This change allows tools using pristine-tar to provide the branch via
--branch=.
---
pristine-tar | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/pristine-tar b/pristine-tar
index 065582f..fb59bf6 100755
--- a/pristine-tar
+++ b/pristine-tar
@@ -118,6 +118,12 @@ Use this option to specify a custom commit message to
pristine-tar commit.
Applies to the B command.
+=item -b branch
+
+=item --branch=branch
+
+Use branch named B rather than the default 'pristine-tar'.
+
=item -s signaturefile
=item --signature-file=signaturefile
@@ -294,6 +300,7 @@ use constant {
my $recompress = 0;
my $recompress_theshold_bytes = 524288000;
my $recompress_theshold_percent = 30;
+my $branch = 'pristine-tar';
my ($message, $signature_file);
my $genversion =
version_from_env(XDELTA3, "xdelta" => XDELTA, "xdelta3" => XDELTA3);
@@ -314,6 +321,7 @@ dispatch(
},
options => {
"m|message=s"=> \$message,
+"b|branch=s"=> \$branch,
"s|signature-file=s" => \$signature_file,
"r|recompress!" => \$recompress,
"B|recompress-threshold-bytes=i" => \$recompress_theshold_bytes,
@@ -333,6 +341,8 @@ Options:
-v, --verbose Turn on verbose output
-k, --keepDon't delete temporary files
-h, --helpDisplay usage information
+ -b BRANCH, --branch=BRANCH
+ Use branch named B. default=pristine-tar
-m MSG, --message=MSG Set commit message
-s SIG, --signature-file Set signature file to be stored
together with the tarball
@@ -932,7 +942,6 @@ sub git_findbranch {
sub checkoutdelta {
my $tarball = shift;
- my $branch= "pristine-tar";
my $deltafile = basename($tarball) . ".delta";
my $idfile= basename($tarball) . ".id";
my $sigfile = basename($tarball) . ".asc";
@@ -986,7 +995,6 @@ sub commitdelta {
my $id = shift;
my $tarball = shift;
- my $branch= "pristine-tar";
my $deltafile = basename($tarball) . ".delta";
my $idfile= basename($tarball) . ".id";
my $sigfile = basename($tarball) . ".asc";
@@ -1137,7 +1145,6 @@ sub checkout {
}
sub list {
- my $branch = "pristine-tar";
my $vcs= vcstype();
if ($vcs eq "git") {
my $b = git_findbranch($branch, 1);
--
2.15.1
Bug#880186: Acknowledgement (gimp: screenshot does not work with wayland)
The gimp upstream bug is 757687. It has more information on the fix. https://bugzilla.gnome.org/show_bug.cgi?id=757687
Bug#880186: gimp: screenshot does not work with wayland
Package: gimp Version: 2.8.20-1 Severity: important Dear Maintainer, If you are running gimp under wayland, and you select Create -> Screenshot It is not able to select X windows, and a screenshot of the whole screen will be completely black. There is a fedora bug covering this at https://bugzilla.redhat.com/show_bug.cgi?id=1398556 This is reported to be fixed in the latest upstream release (2.9.4). Fedora seems to have the patch to add support against their 2.8.22 version at http://pkgs.fedoraproject.org/cgit/rpms/gimp.git/tree/gimp-2.8.22-fix-screenshot-in-wayland.patch -- System Information: Debian Release: buster/sid APT prefers bionic APT policy: (500, 'bionic') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-16-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gimp depends on: ii gimp-data2.8.20-1 ii libaa1 1.4p5-44build1 ii libbabl-0.1-00.1.30-1 ii libbz2-1.0 1.0.6-8.1 ii libc62.26-0ubuntu2 ii libcairo21.15.8-2 ii libdbus-1-3 1.10.22-1ubuntu1 ii libdbus-glib-1-2 0.108-2 ii libexif120.6.21-2.1 ii libfontconfig1 2.12.6-0ubuntu1 ii libfreetype6 2.8-0.2ubuntu2 ii libgdk-pixbuf2.0-0 2.36.11-1 ii libgegl-0.3-00.3.20-1 ii libgimp2.0 2.8.20-1 ii libglib2.0-0 2.54.1-1ubuntu1 ii libgs9 9.21~dfsg+1-0ubuntu3 ii libgtk2.0-0 2.24.31-2ubuntu1 ii libgudev-1.0-0 1:232-1 ii libjpeg8 8c-2ubuntu8 ii liblcms2-2 2.7-1ubuntu1 ii libmng2 2.0.2-0ubuntu3 ii libpango-1.0-0 1.40.12-1 ii libpangocairo-1.0-0 1.40.12-1 ii libpangoft2-1.0-01.40.12-1 ii libpng16-16 1.6.34-1 ii libpoppler-glib8 0.57.0-2ubuntu4 ii librsvg2-2 2.40.18-1 ii libtiff5 4.0.8-6 ii libwmf0.2-7 0.2.8.4-10.6ubuntu2 ii libx11-6 2:1.6.4-3 ii libxcursor1 1:1.1.14-3 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2 ii libxpm4 1:3.5.12-1 ii python 2.7.14-2ubuntu1 ii python-gtk2 2.24.0-5.1ubuntu1 ii python2.72.7.14-2ubuntu2 ii zlib1g 1:1.2.11.dfsg-0ubuntu2 Versions of packages gimp recommends: ii ghostscript 9.21~dfsg+1-0ubuntu3 Versions of packages gimp suggests: pn gimp-data-extras pn gimp-help-en | gimp-help ii gvfs-backends 1.34.1-1ubuntu1 ii libasound21.1.3-5 -- no debconf information
Bug#597580: [PATCH] copy_exec: use 'which' to find full path to executable.
Suggested patch is attached.
This would help to fix other bugs such as 852569.
From c16eddf70f92d1de9f77b4d39c00db329036ea1e Mon Sep 17 00:00:00 2001
From: Scott Moser <smo...@ubuntu.com>
Date: Tue, 26 Sep 2017 16:55:20 -0400
Subject: [PATCH] copy_exec: use 'which' to find full path to executable.
Add support in 'copy_exec' to not require a full path to the executable
that will be copied. This is related to #852569.
Debian: #597580
---
hook-functions | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/hook-functions b/hook-functions
index 5da0cde..02a4477 100644
--- a/hook-functions
+++ b/hook-functions
@@ -159,10 +159,15 @@ copy_file() {
# Location of the image dir is assumed to be $DESTDIR
# We never overwrite the target if it exists.
copy_exec() {
- local src target x nonoptlib ret
+ local osrc src target x nonoptlib ret
- src="${1}"
- target="${2:-$1}"
+ osrc="${1}"
+ if ! src=$(which "$osrc"); then
+ echo "Error: could not find path to '$osrc'"
+ return 2
+ fi
+
+ target="${2:-$src}"
copy_file binary "${src}" "${target}" || return $(($? - 1))
--
2.7.4
Bug#852569: related bug 597580
I'll fix cloud-initramfs-tools to find udevadm in PATH, but it seems like the right thing to do is to fix: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597580 And then to make cloud-initramfs-tools just use: copy_exec udevadm
Bug#852569: how to use initramfs-tools hook-function's copy-exec
Hi,
In cloud-initramfs-tools, udevadm is referred to by /sbin/udevadm only in
growroot/hooks/growroot with 'copy_exec /sbin/udevadm /sbin'.
It appears that even in most recent version of initramfs-tools only
supports full paths to as copy_exec's first argument.
What is the recommended way to use 'copy_exec' without a full path?
I can make cloud-initramfs-tools do something to the extent of:
udevadm=$(which udevadm) &&
copy_exec $udevadm /sbin ||
{ echo "failed copy_exec udevadm"; exit 1 }
But this seems like a generic issue with 'copy_exec' that it requires
full paths to files.
What is the advised solution here?
Thanks,
Scott
Bug#852564: fix for this issue is now upstream.
Hi,
This issue is fixed upstream now. See attached.
The fix can be seen in upstream git commit ad099a53d120 [1]
As suggested in the Debian bug, the change was just to drop the hard
coded path.
Thanks
--
[1]
https://git.launchpad.net/cloud-init/commit/?id=ad099a53d120e88719a5ad50f29d22e9f7a52bc7
From ad099a53d120e88719a5ad50f29d22e9f7a52bc7 Mon Sep 17 00:00:00 2001
From: Scott Moser <smo...@ubuntu.com>
Date: Mon, 25 Sep 2017 14:29:13 -0400
Subject: [PATCH] AltCloud: Trust PATH for udevadm and modprobe.
Previously we had hard coded paths in /sbin for the udevadm and modprobe
programs invoked by AltCloud. Its more flexible to expect the PATH to
be set correctly.
Debian: #852564
---
cloudinit/sources/DataSourceAltCloud.py | 4 ++--
tests/unittests/test_datasource/test_altcloud.py | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/cloudinit/sources/DataSourceAltCloud.py b/cloudinit/sources/DataSourceAltCloud.py
index ed1d691a..c78ad9eb 100644
--- a/cloudinit/sources/DataSourceAltCloud.py
+++ b/cloudinit/sources/DataSourceAltCloud.py
@@ -28,8 +28,8 @@ LOG = logging.getLogger(__name__)
CLOUD_INFO_FILE = '/etc/sysconfig/cloud-info'
# Shell command lists
-CMD_PROBE_FLOPPY = ['/sbin/modprobe', 'floppy']
-CMD_UDEVADM_SETTLE = ['/sbin/udevadm', 'settle', '--timeout=5']
+CMD_PROBE_FLOPPY = ['modprobe', 'floppy']
+CMD_UDEVADM_SETTLE = ['udevadm', 'settle', '--timeout=5']
META_DATA_NOT_SUPPORTED = {
'block-device-mapping': {},
diff --git a/tests/unittests/test_datasource/test_altcloud.py b/tests/unittests/test_datasource/test_altcloud.py
index 3b274d90..a4dfb540 100644
--- a/tests/unittests/test_datasource/test_altcloud.py
+++ b/tests/unittests/test_datasource/test_altcloud.py
@@ -280,8 +280,8 @@ class TestUserDataRhevm(TestCase):
pass
dsac.CLOUD_INFO_FILE = '/etc/sysconfig/cloud-info'
-dsac.CMD_PROBE_FLOPPY = ['/sbin/modprobe', 'floppy']
-dsac.CMD_UDEVADM_SETTLE = ['/sbin/udevadm', 'settle',
+dsac.CMD_PROBE_FLOPPY = ['modprobe', 'floppy']
+dsac.CMD_UDEVADM_SETTLE = ['udevadm', 'settle',
'--quiet', '--timeout=5']
def test_mount_cb_fails(self):
--
2.14.1
Bug#874502: plymouth hooks add duplicate copies of nss files to initramfs
Package: plymouth
Version: 0.9.2-3
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch
Dear Maintainer,
As originally reported in Ubuntu bug 1714319
(https://bugs.launchpad.net/bugs/1714319), plymouth's initramfs hook
script results in 2 copies of nss files (libnss_files-* ) getting
copied to the initramfs.
You can recreate this with:
$ initramfs=/boot/initrd.img-4.12.0-11-generic
$ rm -Rf x && mkdir x
$ /usr/lib/dracut/skipcpio $initrd | zcat | ( cd x && cpio -uid )
$ ( cd x && ls -l lib/libnss* lib/x86_64-linux-gnu/libnss* )
$ ( cd x && md5sum lib/libnss* lib/x86_64-linux-gnu/libnss* )
81c4fbcd350e004f1f59bfa50f9d3769 lib/libnss_files-2.24.so
81c4fbcd350e004f1f59bfa50f9d3769 lib/libnss_files.so.2
81c4fbcd350e004f1f59bfa50f9d3769 lib/x86_64-linux-gnu/libnss_files-2.24.so
81c4fbcd350e004f1f59bfa50f9d3769 lib/x86_64-linux-gnu/libnss_files.so.2
Note, 'skipcpio' is in the dracut-core package and is required to
extract a initramfs that has an 'early archive' in it. Such
a thing would happen if you have installed intel-microcode.
In Ubuntu, the attached patch was applied to achieve the following:
* debian/local/plymouth.hook: add only a single copy of nss libs in
initramfs.
Two copies of libnss_* were getting into the initramfs. One in /lib
and one in /lib/. The fix is to not provide a target
directory when copying those files, but rather copy to the
directory that they came from.
LP: #1714319
Thanks for considering the patch.
-- System Information:
Debian Release: stretch/sid
APT prefers artful
APT policy: (500, 'artful')
Architecture: amd64 (x86_64)
Kernel: Linux 4.12.0-11-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru plymouth-0.9.2/debian/local/plymouth.hook
plymouth-0.9.2/debian/local/plymouth.hook
--- plymouth-0.9.2/debian/local/plymouth.hook 2016-05-04 22:55:22.0
-0400
+++ plymouth-0.9.2/debian/local/plymouth.hook 2017-09-06 09:14:51.0
-0400
@@ -186,6 +186,6 @@
do
if [ -e "${_LIBRARY}" ]
then
- copy_exec ${_LIBRARY} /lib
+ copy_exec "${_LIBRARY}"
fi
done
Bug#783596: /sbin/resolvconf: Re: /e/n/i dns-* option only works in last of homonymous iface def'ns
Package: resolvconf
Version: 1.79ubuntu4
Followup-For: Bug #783596
Hi,
We've hit this bug in Ubuntu and it was filed under bug 1675571 [1].
The solution that I've come up with is to allow the author of /e/n/i to
provide a name for each interface definition stanza in the setting
dns-iface-name. If that is set, it will be used instead of 'inet' or
'inet6' as the 'PROG' portion of 'resolvconf -a IFACE.PROG' when
invoking resolvconf.
The patch is attached, and I have a Ubuntu review up at [2]. I'm
interested in upstream/debian feedback.
Thanks.
--
[1] https://bugs.launchpad.net/debian/+source/resolvconf/+bug/1675571
[2]
https://code.launchpad.net/~smoser/ubuntu/+source/resolvconf/+git/resolvconf/+merge/321203
-- System Information:
Debian Release: stretch/sid
APT prefers zesty-updates
APT policy: (500, 'zesty-updates'), (500, 'zesty-security'), (500, 'zesty')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-15-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages resolvconf depends on:
ii debconf [debconf-2.0] 1.5.59ubuntu1
ii ifupdown 0.8.16ubuntu1
ii init-system-helpers1.47
ii lsb-base 9.20160110ubuntu5
resolvconf recommends no packages.
resolvconf suggests no packages.
-- debconf information:
resolvconf/linkify-resolvconf: true
resolvconf/link-tail-to-original: false
resolvconf/downup-interfaces:
resolvconf/reboot-recommended-after-removal:
commit 4c6b3e659ee1148bdcb36a29414487a11253ee04 (HEAD -> lpusip/debian/sid)
Author: Scott Moser <smo...@brickies.net>
Date: Tue Mar 28 12:41:27 2017 -0400
allow setting of program name via dns-iface-name option in interfaces(5).
When ifupdown has multiple addresses for a given interface, integration
with resolvconf is broken. This is because resolvconf is called for each
stanza, but the scripts in /etc/network/if-*.d/ invoke
resolvconf -a IFACE.PROG
or
resolvconf -d IFACE.PROG
with IFACE being the interface name, and PROG set to ADDRFAM, where
ADDRFAM is only 'inet' or 'inet6'.
The solution here is to allow the author of interfaces(5) to provide
the program name via option 'dns-iface-name'.
As an example:
auto eth0
iface eth0 inet static
address 138.197.98.102/20
gateway 138.197.96.1
dns-nameservers 8.8.8.8
dns-iface-name public0
iface eth0 inet static
address 10.17.0.11/16
dns-iface-name local
LP: #1675571
diff --git a/debian/resolvconf.000resolvconf.if-up
b/debian/resolvconf.000resolvconf.if-up
index f799371..498c97e 100755
--- a/debian/resolvconf.000resolvconf.if-up
+++ b/debian/resolvconf.000resolvconf.if-up
@@ -7,10 +7,15 @@
[ -x /sbin/resolvconf ] || exit 0
-case "$ADDRFAM" in
- inet|inet6) : ;;
- *) exit 0 ;;
-esac
+if [ -n "${IF_DNS_IFACE_NAME}" ]; then
+ IFACE_NAME="${IF_DNS_IFACE_NAME}"
+else
+ case "$ADDRFAM" in
+inet|inet6) : ;;
+*) exit 0 ;;
+ esac
+ IFACE_NAME="${IFACE}.${ADDRFAM}"
+fi
R=""
if [ "$IF_DNS_DOMAIN" ] ; then
@@ -43,5 +48,5 @@ for OPT in $IF_DNS_NAMESERVER ; do
done
IFS="$STANDARD_IFS"
-echo -n "$R" | /sbin/resolvconf -a "${IFACE}.${ADDRFAM}" || :
+echo -n "$R" | /sbin/resolvconf -a "${IFACE_NAME}" || :
diff --git a/debian/resolvconf.000resolvconf.ppp.ip-down
b/debian/resolvconf.000resolvconf.ppp.ip-down
index 561ef41..a0458fd 100755
--- a/debian/resolvconf.000resolvconf.ppp.ip-down
+++ b/debian/resolvconf.000resolvconf.ppp.ip-down
@@ -17,5 +17,5 @@ case "$6" in
;;
esac
-/sbin/resolvconf -d "${PPP_IFACE}.pppd"
+/sbin/resolvconf -d "${IF_DNS_IFACE_NAME:-${PPP_IFACE}.pppd}"
diff --git a/debian/resolvconf.000resolvconf.ppp.ip-up
b/debian/resolvconf.000resolvconf.ppp.ip-up
index c83ea18..5090123 100755
--- a/debian/resolvconf.000resolvconf.ppp.ip-up
+++ b/debian/resolvconf.000resolvconf.ppp.ip-up
@@ -29,5 +29,5 @@ if [ "$DNS2" ] ; then
"
fi
-echo -n "$R" | /sbin/resolvconf -a "${PPP_IFACE}.pppd"
+echo -n "$R" | /sbin/resolvconf -a "${IF_DNS_IFACE_NAME:-${PPP_IFACE}.pppd}"
diff --git a/debian/resolvconf.resolvconf.if-down
b/debian/resolvconf.resolvconf.if-down
index 66e3a9f..1883261 100755
--- a/debian/resolvconf.resolvconf.if-down
+++ b/debian/resolvconf.resolvconf.if-down
@@ -7,10 +7,15 @@
[ -x /sbin/resolvconf ] || exit 0
-case "$ADDRFAM" in
- inet|inet6) : ;;
- *) exit 0 ;;
-esac
+if [ -n "${IF_DNS_IFACE_NAME}" ]; then
+ IFACE_NAME="${IF_DNS_IFACE_NAME}"
+else
+ case "$ADDRFAM" in
+inet|inet6) : ;;
+*) exit 0 ;;
+ esac
+ IFACE_NAME="${IFACE}.${ADDRFAM}&
Bug#841480: [pkg-eucalyptus-maintainers] Bug#841480: euca2ools: please release 3.3.1
On Fri, 21 Oct 2016, Charles Plessy wrote: > Le Thu, Oct 20, 2016 at 09:10:21PM -0400, Scott Moser a écrit : > > > > So, I'm requesting a release of 3.3.1 to Debian that we would then sync > > to Ubuntu. > > > > I've quickly done a build of euca2ools from git and trivially verified > > that euca-describe-images is functional and euca-bundle-image shows > > the 'ppc64el' arch in its help output. > > Thanks Scott for the ping. > > On my side, I do not manage to use the EC2 with euca2ools 3.3.1. I just > opened an issue upstream. > > https://eucalyptus.atlassian.net/browse/TOOLS-657 > > If you have an idea of what I am doing wrong, please let me know ! > > Have a nice week-end, The ~/.euca that I have is basically created from : https://gist.github.com/smoser/8286580 One thing to note, I do not have the certificate and private-key files, i think they might only be used for bundle. certificate = ~/creds/aws-smoser/cert.pem private-key = ~/creds/aws-smoser/pk.pem euca-describe-volumes does work for me. Also verified: $ euca-create-volume -z us-east-1c -s 1 VOLUME vol-bed76e18 1 us-east-1c creating 2016-10-21T13:24:27.272Z $ euca-describe-volumes VOLUME vol-bed76e18 1 us-east-1c available 2016-10-21T13:24:27.272Z standard $ euca-delete-volume vol-bed76e18 VOLUME vol-bed76e18 $ which euca-describe-volumes /usr/bin/euca-describe-volumes $ dpkg -S /usr/bin/euca-describe-volumes euca2ools: /usr/bin/euca-describe-volumes $ dpkg-query --show euca2ools euca2ools 3.3.1-1 I've pinged an upstream maintainer too, so maybe we'll get some help. Scott
Bug#841480: euca2ools: please release 3.3.1
Package: euca2ools Version: 3.1.0-1 Severity: normal Dear Maintainer, Hi, Bug 1527341 in ubuntu (http://bugs.launchpad.net/bugs/1527341) was filed, requesting a fix for the lack of 'ppc64el' as an arch. That bug fix is trivially pulled. However, Ubuntu does not currently have a delta on this package. And so we'd like to not pick one up. Additionally, it seems like the maintainer has already done the work of merging the debian branch at [1] with the upstream tag 3.3.1. [1] https://anonscm.debian.org/gitweb/?p=pkg-eucalyptus/euca2ools.git So, I'm requesting a release of 3.3.1 to Debian that we would then sync to Ubuntu. I've quickly done a build of euca2ools from git and trivially verified that euca-describe-images is functional and euca-bundle-image shows the 'ppc64el' arch in its help output. -- System Information: Debian Release: stretch/sid APT prefers yakkety-updates APT policy: (500, 'yakkety-updates'), (500, 'yakkety-security'), (500, 'yakkety') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-22-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#841107: Acknowledgement (ifupdown: stop networking.service takes 'lo' interface link down)
merge 841107 841106
Bug#841107: ifupdown: stop networking.service takes 'lo' interface link down
Package: ifupdown Version: 0.8.13ubuntu2 Severity: important Tags: patch ipv6 Dear Maintainer, Originally reported in Ubuntu bug 1629972 (http://pad.lv/1629972). stop of networking.service will bring down the link of the 'lo' interface. This causes problems. it does this whether or not there is a 'lo' entry in /etc/network/interfaces. For example: $ cat go.sh #!/bin/sh # clean out any state rm /run/network/ifstate* ip link set down dev lo ip link set down dev eth0 echo == all down ==; ip link show up echo == coming up ==; ifup -a echo == after up ==; ip link show up echo == going down ==; ifdown -a echo == after down ==; ip link show up That will show: == all down == == coming up == == after up == 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 == going down == == after down == The 'lo' link is taken down. As demonstrated https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1629972/comments/6 that actually breaks ipv6 networking. See attached suggested fix. -- System Information: Debian Release: stretch/sid APT prefers yakkety-updates APT policy: (500, 'yakkety-updates'), (500, 'yakkety-security'), (500, 'yakkety') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-22-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown depends on: ii adduser 3.113+nmu3ubuntu4 ii init-system-helpers 1.45 ii iproute2 4.3.0-1ubuntu3 ii libc62.24-3ubuntu1 ii lsb-base 9.20160110ubuntu5 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.3-5ubuntu15 Versions of packages ifupdown suggests: ii ppp 2.4.7-1+2ubuntu1 pn rdnssd -- no debconf information commit c25d5c6b832ffa9e93433862479ad7b7f632a674 Author: Scott Moser <smo...@brickies.net> Date: Thu Oct 13 16:21:10 2016 -0400 networking.service: exclude loopback device lo in ExecStop. Taking down the loopback device causes havoc on the system, such as issues with dbus or general ipv6 networking. The issue seen here was that ipv6 networking would stop functioning and the iscsi mount of root over that ipv6 would become unavailable. diff --git a/debian/networking.service b/debian/networking.service index 065c816..7d7af55 100644 --- a/debian/networking.service +++ b/debian/networking.service @@ -16,6 +16,6 @@ Type=oneshot EnvironmentFile=-/etc/default/networking ExecStartPre=-/bin/sh -c '[ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle' ExecStart=/sbin/ifup -a --read-environment -ExecStop=/sbin/ifdown -a --read-environment +ExecStop=/sbin/ifdown -a --read-environment --exclude=lo RemainAfterExit=true TimeoutStartSec=5min
Bug#841106: ifupdown: ExecStop in networking.service brings down loopback device
Package: ifupdown Version: 0.8.13ubuntu2 Severity: normal Tags: ipv6 Dear Maintainer, This was originally reported under Ubuntu bug 1629972 (https://bugs.launchpad.net/bugs/1629972). The systemd networking.service provided by ifupdown does ExecStop=/sbin/ifdown -a --read-environment That will take down the loopback (lo) device. Bringing down the lo device can completely break ipv6 networking. The result is shutdown of a system with an ipv6 network mounted root device will hang as it loses connection to the root. The fix is for networking.service to instead exclude lo device: ifdown -a --read-environment --exclude=lo As is seen in the equivalent upstart job (networking.conf). -- System Information: Debian Release: stretch/sid APT prefers yakkety-updates APT policy: (500, 'yakkety-updates'), (500, 'yakkety-security'), (500, 'yakkety') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-22-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown depends on: ii adduser 3.113+nmu3ubuntu4 ii init-system-helpers 1.45 ii iproute2 4.3.0-1ubuntu3 ii libc62.24-3ubuntu1 ii lsb-base 9.20160110ubuntu5 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.3-5ubuntu15 Versions of packages ifupdown suggests: ii ppp 2.4.7-1+2ubuntu1 pn rdnssd -- no debconf information diff --git a/debian/networking.service b/debian/networking.service index 065c816..7d7af55 100644 --- a/debian/networking.service +++ b/debian/networking.service @@ -16,6 +16,6 @@ Type=oneshot EnvironmentFile=-/etc/default/networking ExecStartPre=-/bin/sh -c '[ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle' ExecStart=/sbin/ifup -a --read-environment -ExecStop=/sbin/ifdown -a --read-environment +ExecStop=/sbin/ifdown -a --read-environment --exclude=lo RemainAfterExit=true TimeoutStartSec=5min
Bug#839779: python3-jsonpatch: version is incorrectly set as 1.19
Package: python3-jsonpatch Version: 1.19-3 Severity: normal The version in debian is incorrectly identified as 1.19. Upstream version is currently at 1.14 per https://github.com/stefankoegl/python-json-patch and https://pypi.python.org/pypi/jsonpatch $ tar xvf python-json-patch_1.19.orig.tar.xz python-json-patch-1.19/ ... python-json-patch-1.19/jsonpatch.py .. $ python3 -c 'import jsonpatch; print(jsonpatch.__version__)' 1.10 -- System Information: Debian Release: stretch/sid APT prefers yakkety APT policy: (500, 'yakkety') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-9136-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-jsonpatch depends on: ii python3-json-pointer 1.10-1 pn python3:any python3-jsonpatch recommends no packages. python3-jsonpatch suggests no packages. -- no debconf information
Bug#756321: python-boto: run 'test.py unit' with proper 'python'
On Sun, 22 May 2016, Eric Evans wrote: > [ Scott Moser ] > > When merging Ubuntu's python-boto delta from Debian, we have 2 changes > > that we're carrying, both represented in the attached diff. > > > > a.) run tests/test.py with each python in 'pyversions -i' > >This seemed simply typo/oversite. debian/tests/unit was doing: > > for python in $(pyversions -i) > >tests/test.py unit > /dev/null; done > >It didn't seem like there was any way that the expected python > >would be used there. Instead, I changed it to run: > >$python tests/test.py unit > > Definitely an oversight, thanks for bringing to my attention! Thanks. Looks like we can drop our delta if you get these two changes in, which is great. > > b.) Corey Bryant made a change to debian/tests/test.py described as > > "d/tests/unit: Fix autopkgtest error in test_timeout." . > > Unfortunately I don't have more information on this. I forwarded this upstream to boto at https://github.com/boto/boto/issues/3545 If you try running: nosetests -v tests/unit/manage/test_ssh.py And you have python-paramiko installed (so it doesn't skip it). Then its easily enough reproducible. Basically the test (via paramiko) requires a ~/.ssh/known_hosts. You can rm -Rf ~/.ssh/ to test, or if you're adverse to that (which makes sense) then something like below will still show it. Let me know if you need anything else. $ HOME=$(mktemp -d) nosetests -v tests/unit/manage/test_ssh.py test_timeout (tests.unit.manage.test_ssh.TestSSHTimeout) ... ERROR == ERROR: test_timeout (tests.unit.manage.test_ssh.TestSSHTimeout) -- Traceback (most recent call last): File "/home/ubuntu/python-boto-2.38.0/tests/unit/manage/test_ssh.py", line 48, in test_timeout test = SSHClient(server) File "/home/ubuntu/python-boto-2.38.0/boto/manage/cmdshell.py", line 62, in __init__ self._ssh_client.load_host_keys(os.path.expanduser(host_key_file)) File "/usr/lib/python2.7/dist-packages/paramiko/client.py", line 124, in load_host_keys self._host_keys.load(filename) File "/usr/lib/python2.7/dist-packages/paramiko/hostkeys.py", line 95, in load with open(filename, 'r') as f: IOError: [Errno 2] No such file or directory: '/tmp/tmp.HXnpo7af51/.ssh/known_hosts' -- Ran 1 test in 0.001s
Bug#823860: bcache-tools: bcache does not work with suspend
Package: bcache-tools Version: 1.0.8-2 Severity: normal Dear Maintainer, As first reported in Ubuntu under bug 1515780 (https://launchpad.net/bugs/1515780) suspend and resume is broken with bcache. This is described at https://bcache.evilpiepirate.org/FAQ/ in entry "Can I use bcache with suspend/resume?". There is an initial /lib/systemd/system-sleep/bcache.sh in the Ubuntu bug. The script there intends to use /lib/systemd/system-sleep/ . However, systemd-suspend.service(8) has the following to say: | Note that scripts or binaries dropped in /lib/systemd/system-sleep/ are | intended for local use only and should be considered hacks. If | applications want to be notified of system suspend/hibernation and | resume, there are much nicer interfaces available. -- System Information: Debian Release: stretch/sid APT prefers yakkety APT policy: (500, 'yakkety') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-21-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bcache-tools depends on: ii libblkid1 2.27.1-6ubuntu3 ii libc6 2.23-0ubuntu3 ii libuuid1 2.27.1-6ubuntu3 Versions of packages bcache-tools recommends: ii initramfs-tools [linux-initramfs-tool] 0.122ubuntu8 bcache-tools suggests no packages. -- no debconf information
Bug#812099: python-apt-common: unnecessary dependency on python | python3
Package: python-apt-common Version: 1.1.0~beta1build1 Severity: minor Dear Maintainer, I was just looking at reverse depends on python on a ubuntu system and saw python-apt-common listed. A quick look showed no obvious reason for apt-common's 'Depends' on 'python | python3'. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-5-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-apt-common depends on: ii python 2.7.11-1 ii python3 3.5.1-1ubuntu2 python-apt-common recommends no packages. python-apt-common suggests no packages. -- no debconf information
Bug#804591: [Pkg-iscsi-maintainers] Bug#804591: open-iscsi: iscsi_auto flag should use iscsistart --fwparam_network in addition to -b
On Mon, 9 Nov 2015, Christian Seiler wrote: > Hi, > > On 11/09/2015 10:40 PM, Scott Moser wrote: > >>> If we were to invoke 'iscsistart --fwparam_network' after having done > >>> configure_networking, then the iscsi parameters would be in affect. > >>> Its may be arguable that this is simply misconfiguration of the ip= > >>> parameter. > >> > >> On the other hand, one could argue that one might want to overwrite > >> the parameters set in the firmware with an explicit kernel commmand > >> line. > > > > Agreed. > > > >> I think the case is definitely clear if iscsi_auto is specified > >> without an ip= parameter, then iscsistart should take care of it. > > > > Definitely. Unfortunately, the case that I'm working on is with MAAS > > which specifies a ip= command line to its provided iscsi server. The > > install environment is then provided over read-only iscsi. > > Does the ip= match here or is there some problem with it? If > there's no problem and you are just mentioning it to be > cautious: I think it's fair to ask our users to not > misconfigure their network in initramfs. I mean, without > iscsi_auto and manual iSCSI config a wrong ip= will also lead > to an unbootable system. in the specific case, the ip= was for eth0 and 2 other nics would be configured per the iBFT. I was just listing it as an example of where you would possibly have ip= *and* want iscsistart --fwparam_network. > > It seems reasonable that you might have 'ip=' on the kernel command line > > for reasons unrelated to iscsi entirely, and possibly referencing > > different network devices. > > Then maybe we should do the following: if iscsi_auto is specified, > call iscsistart -N first, then configure the network regularly. > Then ip= will always override iBFT, but other devices will also > be activated. > > >> Btw. is there any way to test this in a VM? I don't have access to > >> the corresponding hardware that sets these values, so I can't > >> really test this myself. > > > > Luckily, you *can* do it entirely within qemu and ipxe with a few minor > > limitations. Figuring out how to do that is non-trivial, but I've managed > > my way through it. > > Oh great, I don't have time today anymore (I'm in time zone UTC+01, > so it's quite late here ;-)), but I'll take a look at it during > the next few days. > > > Right, that was my thought too. I might suggest not reading iscsistart > > -f, but rather the files from /sys/firmware/ibft. > > The problem there is matching against the right network interface > name - it's certainly possible, but parsing the output of > iscsistart is probably a lot simpler. > > > Here is some output > > from each, for those not adventuresome enough to try on their own. Note, i > > added a carriage return to subnet mask that did not have one. > > Where exactly did it not have a carriage return? According to > the open-iscsi source, all values printed have \n there > (at least Debian's git snapshot, maybe that was a bug in the > version that was fixed between the version you use and the > version I have). the /sys interface did not have a subnet mask. ie, /sys/firmware/ibft/ethernet0/subnet-mask had no trailing carriage return. > > I've created a VERY simple parser in POSIX shell that reads > the input of iscsistart -f and pseudo-creates the /run/net- > file and attached it to this email. If you don't have any > objections to it, I'll integrate that into the initramfs hook. it seems to look fine. reading from /sys isnt terribly hard, though. the mapping of nic name from ibft to current linux nic name is easily enough made through: /sys/class/net//address == /sys/firmware/ibft/ethernet0/mac your parser seems fine, and only incurs one subshell, so that is nice. > > Regards, > Christian >
Bug#804591: [Pkg-iscsi-maintainers] Bug#804591: open-iscsi: iscsi_auto flag should use iscsistart --fwparam_network in addition to -b
On Mon, 9 Nov 2015, Christian Seiler wrote: > >> Btw. is there any way to test this in a VM? I don't have access to > >> the corresponding hardware that sets these values, so I can't > >> really test this myself. > > > > Luckily, you *can* do it entirely within qemu and ipxe with a few minor > > limitations. Figuring out how to do that is non-trivial, but I've managed > > my way through it. > > Oh great, I don't have time today anymore (I'm in time zone UTC+01, > so it's quite late here ;-)), but I'll take a look at it during > the next few days. https://gist.github.com/smoser/810d59f0dd580b1c1256 That docs a lot of it.
Bug#804591: [Pkg-iscsi-maintainers] Bug#804591: open-iscsi: iscsi_auto flag should use iscsistart --fwparam_network in addition to -b
> > If we were to invoke 'iscsistart --fwparam_network' after having done
> > configure_networking, then the iscsi parameters would be in affect.
> > Its may be arguable that this is simply misconfiguration of the ip=
> > parameter.
>
> On the other hand, one could argue that one might want to overwrite
> the parameters set in the firmware with an explicit kernel commmand
> line.
Agreed.
> I think the case is definitely clear if iscsi_auto is specified
> without an ip= parameter, then iscsistart should take care of it.
Definitely. Unfortunately, the case that I'm working on is with MAAS
which specifies a ip= command line to its provided iscsi server. The
install environment is then provided over read-only iscsi.
It seems reasonable that you might have 'ip=' on the kernel command line
for reasons unrelated to iscsi entirely, and possibly referencing
different network devices.
> Btw. is there any way to test this in a VM? I don't have access to
> the corresponding hardware that sets these values, so I can't
> really test this myself.
Luckily, you *can* do it entirely within qemu and ipxe with a few minor
limitations. Figuring out how to do that is non-trivial, but I've managed
my way through it.
I'll try to collect my notes and post back here.
>
> > Also of note, /run/net-.conf will not be written if iscsistart
> > configures the networking as opposed to 'ipconfig' doing it.
>
> Could you give me the output of
>
> iscsistart -f
>
> on a system with iBFT? I think I could write a trivial POSIX
> shell parser for that that creates the corresponding
> /run/net-*.conf files. From the open-iscsi source I'm pretty
> confident I know what the output looks like, but I'd rather
> have real data to test that with.
Right, that was my thought too. I might suggest not reading iscsistart
-f, but rather the files from /sys/firmware/ibft. Here is some output
from each, for those not adventuresome enough to try on their own. Note, i
added a carriage return to subnet mask that did not have one.
This system was booted with an pxe config that looked like this and
'break=top' on the kernel command line. The values jsut then collected
from the initramfs:
#!ipxe
dhcp
set iscsi-host 192.168.1.131
set base-url http://192.168.1.131:/
sanhook --drive 0x80 iscsi:${iscsi-host}::3260:1:inst-000-1
sanhook --drive 0x81 iscsi:${iscsi-host}::3260:1:inst-000-2
kernel ${base-url}/boot-kernel break=top
initrd ${base-url}/boot-initrd
boot
(initramfs) iscsistart --fwparam_print
# BEGIN RECORD 2.0-873
iface.initiatorname =
iqn.2010-04.org.ipxe:----
iface.transport_name = tcp
iface.hwaddress = 52:54:00:12:34:56
iface.bootproto = STATIC
iface.ipaddress = 10.0.2.16
iface.subnet_mask = 255.255.255.0
iface.gateway = 10.0.2.2
iface.primary_dns = 10.0.2.3
iface.vlan_id = 0
iface.net_ifacename = eth0
node.name = inst-000-2
node.conn[0].address = 192.168.1.131
node.conn[0].port = 3260
node.boot_lun = 0100
# END RECORDk
(initramfs) ipconfig eth0
IP-Config: eth0 hardware address 52:54:00:12:34:56 mtu 1500 DHCP RARP
IP-Config: eth0 guessed broadcast address 10.0.2.255
IP-Config: eth0 complete (dhcp from 10.0.2.2):
address: 10.0.2.15broadcast: 10.0.2.255 netmask:
255.255.255.0
gateway: 10.0.2.2 dns0 : 10.0.2.3 dns1 : 0.0.0.0
rootserver: 10.0.2.2 rootpath:
filename :
(initramfs) for f in $(find /sys/firmware/ibft/ -type f); do echo == $f ==; cat
$f; done
== /sys/firmware/ibft/target0/lun ==
0100
== /sys/firmware/ibft/target0/port ==
3260
== /sys/firmware/ibft/target0/target-name ==
inst-000-2
== /sys/firmware/ibft/target0/flags ==
3
== /sys/firmware/ibft/target0/index ==
0
== /sys/firmware/ibft/target0/chap-type ==
0
== /sys/firmware/ibft/target0/nic-assoc ==
0
== /sys/firmware/ibft/target0/ip-addr ==
192.168.1.131
== /sys/firmware/ibft/initiator/flags ==
3
== /sys/firmware/ibft/initiator/index ==
0
== /sys/firmware/ibft/initiator/initiator-name ==
iqn.2010-04.org.ipxe:----
== /sys/firmware/ibft/ethernet0/mac ==
52:54:00:12:34:56
== /sys/firmware/ibft/ethernet0/vlan ==
0
== /sys/firmware/ibft/ethernet0/flags ==
3
== /sys/firmware/ibft/ethernet0/index ==
0
== /sys/firmware/ibft/ethernet0/primary-dns ==
10.0.2.3
== /sys/firmware/ibft/ethernet0/subnet-mask ==
255.255.255.0
== /sys/firmware/ibft/ethernet0/gateway ==
10.0.2.2
== /sys/firmware/ibft/ethernet0/origin ==
1
== /sys/firmware/ibft/ethernet0/ip-addr ==
10.0.2.16
Bug#804591: open-iscsi: iscsi_auto flag should use iscsistart --fwparam_network in addition to -b
Package: open-iscsi Version: 2.0.873-3ubuntu13 Severity: normal Dear Maintainer, It seems that 'iscsi_auto' should invoke 'iscsistart --fwparam_network' in addition to -b. The --fwparam_network will set up networking that was declared in iBFT. There is some overlap here with the 'ip=' kernel command line parameter, and it is possible that the two could conflict. For example, if the kernel command line had ip=192.168.1.2::192.168.1.1:255.255.255.0:myhostname:eth0 And iBFT was configured such that $ cat /sys/firmware/ibft/ethernet0/ip-addr 192.168.1.3 $ cat /sys/firmware/ibft/ethernet0/gateway 192.168.1.1 $ cat /sys/firmware/ibft/ethernet0/subnet-mask 255.255.255.0 If we were to invoke 'iscsistart --fwparam_network' after having done configure_networking, then the iscsi parameters would be in affect. Its may be arguable that this is simply misconfiguration of the ip= parameter. Also of note, /run/net-.conf will not be written if iscsistart configures the networking as opposed to 'ipconfig' doing it. -- System Information: Debian Release: jessie/sid APT prefers wily-updates APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-16-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages open-iscsi depends on: ii libc6 2.21-0ubuntu4 ii udev 225-1ubuntu9 open-iscsi recommends no packages. open-iscsi suggests no packages. -- no debconf information
Bug#804162: open-iscsi: support iscsi root by format in RFC 4173 (root=iscsi:server:prot:...)
On Thu, 5 Nov 2015, Christian Seiler wrote: > Yes, this seems like a good idea for something to support. I see a > minor implementation detail that might need some thinking to fix: > currently, open-iscsi only adds itself to the initramfs if > /etc/iscsi/initramfs.iscsi exists - and the information in there > would be replaced by the root= parameter. On the other hand, > unconditionally adding the iSCSI binaries to the initramfs might > also not be wanted behavior, because it makes the initramfs larger. > (iSCSI can also be used for non-root filesystems.) Other than size, iscsi is to my memory almost perfectly inert in the initramfs if it doesnt find any cmdline that says for it to do something. (iscsi_target_name= or iscsi_auto) So my feeling is if the user installs open-iscsi, then they want it in the initramfs. Do that unless they turn it off.
Bug#804162: open-iscsi: support iscsi root by format in RFC 4173 (root=iscsi:server:prot:...)
Package: open-iscsi Version: 2.0.873-3ubuntu13 Severity: normal Hi, RFC 4173 (http://tools.ietf.org/html/rfc4173) documents a fairly compact mechanism for an iscsi target definition. Copied from http://ipxe.org/sanuri: | fmt of an iSCSI SAN URI is defined by RFC 4173. The general syntax is: |iscsi: Examples: iscsi:10.0.4.1:::1:iqn.2010-04.org.ipxe.dolphin:storage iscsi:boot.ipxe.orgiqn.2010-04.org.ipxe.boot:public iscsi:192.168.0.1iqn.1991-05.com.microsoft:msdos622-target iscsi:opensolaris.homeiqn.1986-03.com.sun:02:e9abf4cd-714b-c6ec-d017-eea5a56252ed For the first example there, the way that would be done in current parameters would be: iscsi_target_name=iqn.2010-04.org.ipxe.dolphin:storage iscsi_target_ip=10.0.4.1 iscsi_target_group=1 It'd be nice if we could just: root=iscsi:10.0.4.1:::1:iqn.2010-04.org.ipxe.dolphin:storage Note that RFC does not cover username and password, so that would have to be done outside the spec if needed. -- System Information: Debian Release: jessie/sid APT prefers wily-updates APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-16-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages open-iscsi depends on: ii libc6 2.21-0ubuntu4 ii udev 225-1ubuntu9 open-iscsi recommends no packages. open-iscsi suggests no packages. -- no debconf information
Bug#785287: systemd unit solves install issue
Hi, I've found that installing a systemd service file fixes the problem, and have uploaded a fix to Ubuntu 15.10. For easy inclusion, the following is debian/openhpid.service: [Unit] Description=Daemon providing access to the SAF Hardware Platform Interface [Service] Type=simple ExecStart=/usr/sbin/openhpid -n -c /etc/openhpi/openhpi.conf [Install] WantedBy=multi-user.target
Bug#789067: initramfs-tools: if ip is specified on cmdline, networking should be brought up in initramfs
Package: initramfs-tools Version: 0.103ubuntu15 Severity: normal Dear Maintainer, Originally filed in Ubuntu at http://launchpad.net/bugs/1463846 If the kernel command line has 'ip=' in it, it is arguable that configure_networking should be run. Currently, initramfs only does this if something thinks it should. Ie, open-iscsi might do it, or some other things might call 'configure_networking'. But it seems reasonable that if the user put 'ip=' on the cmdline then they wanted that to happen in initramfs. One possible fallout is that currently calling configure_networking multiple times will try multiple times if unsuccessful, which could lead to longer timeouts if we added this behavior and it was called multiple times. Additionally, one feature i'd like to have (admittedly for debug purposes) is the ability to write the /run/initramfs/open-iscsi.interface file that is used at least by open-iscsi to say do not bring this interface down. generically, it seems like it'd be nice to have a way to have the same functionality that open-iscsi.interface accomplishes but not tied to open-iscsi. Ie, the user may for any reason want to keep a network from getting re-configured by normal OS bringup. -- Package-specific info: -- initramfs sizes -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=715c6da7-c111-4842-868b-7778623ead7c ro quiet splash vt.handoff=7 -- /proc/filesystems ext3 ext2 ext4 vfat fuseblk -- lsmod Module Size Used by overlay45056 0 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 1 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_conntrack_ipv4 16384 1 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 nf_nat_ipv416384 1 iptable_nat nf_nat 28672 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack 106496 4 nf_nat,nf_nat_ipv4,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 xt_tcpudp 16384 5 bridge110592 0 stp16384 1 bridge llc16384 2 stp,bridge iptable_filter 16384 1 ip_tables 28672 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 6 xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,iptable_filter,iptable_mangle rfcomm 69632 8 bnep 20480 2 dm_crypt 24576 1 dm_multipath 24576 0 scsi_dh16384 1 dm_multipath snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi coretemp 16384 0 snd_hda_codec_conexant24576 1 snd_hda_codec_generic69632 1 snd_hda_codec_conexant snd_rawmidi32768 1 snd_seq_midi pcmcia 65536 0 arc4 16384 2 snd_seq69632 2 snd_seq_midi_event,snd_seq_midi joydev 20480 0 serio_raw 16384 0 iwldvm237568 0 r852 20480 0 sm_common 20480 1 r852 snd_hda_intel 32768 3 nand 69632 2 r852,sm_common snd_hda_controller 32768 1 snd_hda_intel mac80211 724992 1 iwldvm thinkpad_acpi 86016 0 nand_ecc 16384 1 nand nvram 16384 1 thinkpad_acpi snd_hda_codec 143360 4 snd_hda_codec_conexant,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller snd_hwdep 20480 1 snd_hda_codec nand_bch 16384 1 nand bch20480 1 nand_bch uvcvideo 90112 0 nand_ids 16384 1 nand videobuf2_vmalloc 16384 1 uvcvideo mtd61440 2 nand,sm_common lpc_ich24576 0 yenta_socket 49152 0 videobuf2_memops 16384 1 videobuf2_vmalloc r592 20480 0 snd_pcm 106496 3 snd_hda_codec,snd_hda_intel,snd_hda_controller iwlwifi 196608 1 iwldvm memstick 20480 1 r592 videobuf2_core 49152 1 uvcvideo pcmcia_rsrc20480 1 yenta_socket v4l2_common16384 1 videobuf2_core pcmcia_core24576 3 pcmcia,pcmcia_rsrc,yenta_socket snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi videodev 159744 3 uvcvideo,v4l2_common,videobuf2_core cfg80211 540672 3 iwlwifi,mac80211,iwldvm btusb 32768 0 media 24576 2 uvcvideo,videodev bluetooth 491520 22 bnep,btusb,rfcomm snd_timer 32768 2 snd_pcm,snd_seq shpchp 40960 0 snd90112 17 snd_hwdep,snd_timer,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device mei_me 20480 0 mei90112 1 mei_me soundcore 16384 2
Bug#788841: multipath-tools-boot: inclusion of /etc/multipath/bindings in initramfs on install contains race condition
Package: multipath-tools-boot Version: 0.5.0-6+deb8u1 Severity: normal Dear Maintainer, Hi, in debugging an issue on Ubuntu under ubuntu bug 1462530 (http://pad.lv/1462530), we found that /etc/multipath/bindings needs to be included in the initramfs. The code in /usr/share/initramfs-tools/hooks/multipath will do that, but only if the file exists. The file is created in normal operation by the multipath-tools service (/etc/init.d/multipath-tools). However a normall install path of: apt-get install multipath-tools-boot will cause multipath-tools service to be started in the background and will not guarantee that the file exists before update-initramfs runs the hooks file to collect it. One possible way of addressing this would be to run 'multipath -r' to force its creation. That does possibly have side affects. Generally speaking this is an unlikely race condition to hit, but I don't see anything that guarantees it wont happen. -- Package-specific info: /etc/multipath.conf does not exist. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages multipath-tools-boot depends on: ii debconf [debconf-2.0] 1.5.56 ii initramfs-tools0.120 ii multipath-tools0.5.0-6+deb8u1 multipath-tools-boot recommends no packages. multipath-tools-boot suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783826: cloud-utils growroot doesn't work with newer sfdisk = 2.26 : fixed patch solution for newer and older sfdisk
On Mon, 4 May 2015, Thomas Goirand wrote: Hi Scott and Juerg, Someone has filed this bug in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783826 Unfortunately, the patch here: http://pkgs.fedoraproject.org/cgit/cloud-utils.git/plain/0002-Support-new-sfdisk-version-2.26.patch doesn't work with the older sfdisk, currently in Sid, but works with version 2.26 only. To make a smooth transition, best would be to make a conditional test, and check if we're running with util-linux 2.25, or = 2.26. This would also allow newer cloud-utils to be backported to Jessie. Juerg's 'Support-new-sfdisk-version-2.26.patch' seems to do 4 things: a.) drop use of MBR_CHS, which I think is probably no longer necessary. this was originally added when dealing with loop devices, but might not be necessary with --unit=S. b.) obtain 'tot' (the total size in sectors) of the disk differently sfdisk --list rather than tot=$$((cyl*$heads*$sectors) c.) use dd to restore the original in case of failure. I suspect that you're working around upstream sfdisk bug 1211405 here. https://bugzilla.redhat.com/show_bug.cgi?id=1211405 I'd rather not make assumptions on the output format of '-O'. Using '-I' and expecting sfdisk to do the right thing seems safer. d.) removal of use of --unit=S util-linux 2.26 seems to support this, so I'd just as soon leave it for now. This is what I've done on the attached patch. Scott, could you please use that upstream from now on? Also, what about the do-not-use-EXIT-when-trapping.patch patch which I had to add in Debian? Could you please apply them both? EXIT is posix compatible. you really should change the shell to be posix compatible rather than changing all programs to expect a subset of poxix shell. http://pubs.opengroup.org/onlinepubs/95399/utilities/trap.html I'll work something up upstream probably based on checking the sfdisk version. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783826: cloud-utils growroot doesn't work with newer sfdisk = 2.26 : fixed patch solution for newer and older sfdisk
On Mon, 4 May 2015, Antonio Terceiro wrote: On Mon, May 04, 2015 at 12:48:37PM -0400, Scott Moser wrote: Also, what about the do-not-use-EXIT-when-trapping.patch patch which I had to add in Debian? Could you please apply them both? EXIT is posix compatible. you really should change the shell to be posix compatible rather than changing all programs to expect a subset of poxix shell. http://pubs.opengroup.org/onlinepubs/95399/utilities/trap.html EXIT is supported by dash ... I have just tested the script below and it works as expected on all Debian release since at least wheezy. I think its not supported in the static busybox that is in debian initramfs. Not sure, but I think that was the problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783826: cloud-utils growroot doesn't work with newer sfdisk = 2.26 : fixed patch solution for newer and older sfdisk
On Mon, 4 May 2015, Juerg Haefliger wrote: This is what I've done on the attached patch. Scott, could you please use that upstream from now on? Also, what about the do-not-use-EXIT-when-trapping.patch patch which I had to add in Debian? Could you please apply them both? EXIT is posix compatible. you really should change the shell to be posix compatible rather than changing all programs to expect a subset of poxix shell. http://pubs.opengroup.org/onlinepubs/95399/utilities/trap.html I'll work something up upstream probably based on checking the sfdisk version. initial start at lp:~smoser/cloud-utils/growpart-sfdisk-2.26 I'm open to using sfdisk for gpt also if that actually works (instead of using sgdisk). Scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758910: euca2ools: please update to euca2ools 3.1
Package: euca2ools Version: 3.0.2-1ubuntu1 Severity: normal Dear Maintainer, Newest available version of euca2ools is 3.1.0. -- System Information: Debian Release: jessie/sid APT prefers utopic-updates APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500, 'utopic'), (100, 'utopic-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-6-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages euca2ools depends on: ii python 2.7.8-1 ii python-lxml3.3.5-1 ii python-requestbuilder 0.1.0-1 ii python-requests2.3.0-1 ii python-setuptools 5.5.1-1 ii python-six 1.7.3-1 pn python:any none Versions of packages euca2ools recommends: ii openssl 1.0.1f-1ubuntu7 euca2ools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756321: python-boto: run 'test.py unit' with proper 'python'
Package: python-boto Version: 2.29.1-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu utopic ubuntu-patch Dear Maintainer, When merging Ubuntu's python-boto delta from Debian, we have 2 changes that we're carrying, both represented in the attached diff. a.) run tests/test.py with each python in 'pyversions -i' This seemed simply typo/oversite. debian/tests/unit was doing: for python in $(pyversions -i) tests/test.py unit /dev/null; done It didn't seem like there was any way that the expected python would be used there. Instead, I changed it to run: $python tests/test.py unit b.) Corey Bryant made a change to debian/tests/test.py described as d/tests/unit: Fix autopkgtest error in test_timeout. . Unfortunately I don't have more information on this. Scott In Ubuntu, the attached patch was applied to achieve the following: * Merge with debian. Remaining Ubuntu changes: * d/tests/unit: Fix autopkgtest error in test_timeout. * d/tests/unit: run tests/test.py with each python in 'pyversions -i' Thanks for considering the patch. -- System Information: Debian Release: jessie/sid APT prefers utopic-updates APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500, 'utopic'), (100, 'utopic-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-5-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash === modified file 'debian/tests/unit' --- debian/tests/unit 2014-03-30 12:36:49 + +++ debian/tests/unit 2014-07-28 19:20:40 + @@ -1,9 +1,23 @@ #/bin/sh +set -ex + +#Create temporary home directory with .ssh/known_hosts file +#so that test_timeout will be able to work. +home_orig=$HOME +home_temp=$(mktemp -d) +mkdir -p $home_temp/.ssh +touch $home_temp/.ssh/known_hosts +export HOME=$home_temp + set -eu cp -r tests $ADTTMP/ cd $ADTTMP for python in $(pyversions -i); do -tests/test.py unit /dev/null +$python tests/test.py unit /dev/null done + +#Restore original home directory and remove temp home dir +export HOME=$home_orig +rm -rf $home_temp
Bug#734616: euca2ools: euca-get-console-output fails if output not to a console
Package: euca2ools Version: 3.0.2-1 Severity: normal Dear Maintainer, This bug is filed upstream at https://eucalyptus.atlassian.net/browse/TOOLS-407 , and in Ubuntu at http://pad.lv/1266898 . I'm uploading an ubuntu patch for the time being. euca-get-console-output fails if output is not to a console with: euca-get-console-output: error: decode() argument 1 must be string, not None $ dpkg-query --show euca2ools euca2ools 3.0.2-1 $ IID=i-36874418 $ euca-get-console-output --region=us-east-1 $IID /tmp/out euca-get-console-output: error: decode() argument 1 must be string, not None $ echo $? 1 $ euca-get-console-output --region=us-east-1 $IID output here ... $ echo $? 0 -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.12.0-2-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages euca2ools depends on: ii python 2.7.5-5ubuntu3 ii python-lxml3.3.0~beta2-1 ii python-requestbuilder 0.1.0~beta2-1 ii python-requests2.0.0-1 ii python-setuptools 2.0.1-2ubuntu1 ii python-six 1.4.1-1 pn python:any none Versions of packages euca2ools recommends: ii openssl 1.0.1e-4ubuntu4 euca2ools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731951: python-requestbuilder: new upstream version 0.1.0
Package: python-requestbuilder Version: 0.1.0~beta2-1 Severity: normal Dear Maintainer, A new version of 'requestbuilder' is available, version 0.1.0. The commit log between beta2 that is packaged is not big, and really only contains a few minor improvements and a few bug fixes. version 0.1.0 is available at https://pypi.python.org/pypi/requestbuilder -- System Information: Debian Release: wheezy/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.12.0-5-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-requestbuilder depends on: ii dpkg 1.17.1ubuntu1 ii python 2.7.5-5ubuntu1 ii python-requests 2.0.0-1 ii python-six 1.4.1-1 pn python:any none python-requestbuilder recommends no packages. python-requestbuilder suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720281: supervisor: 'service status supervisor' shows only ' is running' (LABEL undefined)
Package: supervisor Version: 3.0b2-1 Severity: normal Dear Maintainer, $ sudo service supervisor status is running The expected output would probably be 'supervisord is running' The issue I think is just that 'LABEL' variable in /etc/init.d/supervisor is used when possibly 'NAME' was intended. -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy'), (100, 'saucy-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.11.0-2-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717916: python-json-patch: package name does not conform to python policy
Package: python-json-patch Version: 1.0-1ubuntu2 Severity: normal Dear Maintainer, I believe that python-json-patch should be named python-jsonpatch according to section 2.2 of the python-policy [1]. This naming difference means that dh_python2 does not correctly determine the dependencies. -- [1] http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy'), (100, 'saucy-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.10.0-5-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-json-patch depends on: ii dpkg 1.16.10ubuntu3 ii python 2.7.5-1ubuntu1 ii python-json-pointer 1.0-1ubuntu2 python-json-patch recommends no packages. python-json-patch suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712915: python-requests: adapters.py uses undefined name ProxyManager
Package: python-requests
Version: 1.2.0-2
Severity: important
Dear Maintainer,
As first reported in Ubuntu bug 1187429 [1], requests is simply broken if
the user's environment contains 'http_proxy'. This fails recreates in both
python and python3.
[1] https://bugs.launchpad.net/ubuntu/+source/requests/+bug/1187429
$ echo import sys, requests recreate.py
$ echo print(requests.get(sys.argv[1]).status_code) recreate.py
$ python recreate.py http://debian.org
$ env -u http_proxy python recreate.py
200
$ env http_proxy=http://example.com/ python recreate.py http://debian.org
Traceback (most recent call last):
File recreate.py, line 2, in module
print(requests.get(sys.argv[1]).status_code)
File /usr/lib/python2.7/dist-packages/requests/api.py, line 55, in get
return request('get', url, **kwargs)
File /usr/lib/python2.7/dist-packages/requests/api.py, line 44, in request
return session.request(method=method, url=url, **kwargs)
File /usr/lib/python2.7/dist-packages/requests/sessions.py, line 354, in
request
resp = self.send(prep, **send_kwargs)
File /usr/lib/python2.7/dist-packages/requests/sessions.py, line 460, in
send
r = adapter.send(request, **kwargs)
File /usr/lib/python2.7/dist-packages/requests/adapters.py, line 191, in
send
conn = self.get_connection(request.url, proxies)
File /usr/lib/python2.7/dist-packages/requests/adapters.py, line 140, in
get_connection
conn = ProxyManager(self.poolmanager.connection_from_url(proxy))
NameError: global name 'ProxyManager' is not defined
This was upstream fixed at
https://github.com/kennethreitz/requests/commit/5152c98223d46c76cb7e88cb833b0087daf83d54
reported at https://github.com/kennethreitz/requests/issues/1017 .
It seems as simple as adding ProxyManager to the imports in adapters.py
-- System Information:
Debian Release: wheezy/sid
APT prefers saucy-updates
APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy'),
(100, 'saucy-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 3.8.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-requests depends on:
ii ca-certificates 20130610
ii python 2.7.5-1ubuntu1
ii python-chardet 2.0.1-2build1
ii python-urllib3 1.6-2
python-requests recommends no packages.
python-requests suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710511: alpine: passfile support (-passfile) seems completely broken
Package: alpine Version: 2.10+dfsg-1+maildir~ppa0 Severity: normal Dear Maintainer, The version reported above is a private build of alpine patched with maildir, but this bug is reproducible on 2.10+dfsg-1. It seems that '-passfile' support is completely broken in 2.10. If you pass argument '-passfile' and a path to any file that exists, alpine will core dump after the first time it attempts to read a password. This reproduces: touch passfile alpine -passfile $PWD/passfile This does not segfault, but does not store anything in passfile. rm -f passfile alpine -passfile $PWD/passfile -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy'), (100, 'saucy-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.8.0-21-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages alpine depends on: ii libc6 2.17-0ubuntu5 ii libgssapi-krb5-2 1.10.1+dfsg-6 ii libkrb5-3 1.10.1+dfsg-6 ii libldap-2.4-2 2.4.31-1ubuntu2 ii libpam0g 1.1.3-8ubuntu3 ii libssl1.0.0 1.0.1e-2ubuntu1 ii libtinfo5 5.9-10ubuntu4 ii mlock 8:2007e~dfsg-3.2ubuntu2 Versions of packages alpine recommends: ii alpine-doc 2.10+dfsg-1+maildir~ppa0 Versions of packages alpine suggests: ii aspell 0.60.7~20110707-1build1 ii postfix [mail-transport-agent] 2.10.0-3ubuntu2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709475: euca2ools: euca-bundle-vol and euca-bundle-image to EC2 require ec2 certificate
Package: euca2ools Version: 2.1.3-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu saucy ubuntu-patch Dear Maintainer, In order to upload an image to EC2 (either with euca-bundle-vol or euca-bundle-image), a X509 public key certificate is required. In order to upload or bundle to Amazon, Amazon's certificate is required. As AWS is the most popular target for usage of the euca2ools, Ubuntu has included the ec2 certificate in /usr/share/euca2ools/cert-ec2.pem and create a symlink to it from /etc/ssl/certs/cert-ec2.pem. This allows the user to be able to do: euca-bundle-vol --ec2cert /usr/share/euca2ools/cert-ec2.pem without having to externally find Amazon's certificate. This issue was originally raised in Ubuntu under bug 479836. Thanks for considering the patch. -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy'), (100, 'saucy-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.8.0-21-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash === added file 'debian/cert-ec2.pem' --- debian/cert-ec2.pem 1970-01-01 00:00:00 + +++ debian/cert-ec2.pem 2013-05-23 12:57:03 + @@ -0,0 +1,23 @@ +-BEGIN CERTIFICATE- +MIIDzjCCAzegAwIBAgIJALDnZV+lpZdSMA0GCSqGSIb3DQEBBQUAMIGhMQswCQYD +VQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRv +d24xJzAlBgNVBAoTHkFtYXpvbiBEZXZlbG9wbWVudCBDZW50cmUgKFNBKTEMMAoG +A1UECxMDQUVTMREwDwYDVQQDEwhBRVMgVGVzdDEdMBsGCSqGSIb3DQEJARYOYWVz +QGFtYXpvbi5jb20wHhcNMDUwODA5MTYwMTA5WhcNMDYwODA5MTYwMTA5WjCBoTEL +MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2Fw +ZSBUb3duMScwJQYDVQQKEx5BbWF6b24gRGV2ZWxvcG1lbnQgQ2VudHJlIChTQSkx +DDAKBgNVBAsTA0FFUzERMA8GA1UEAxMIQUVTIFRlc3QxHTAbBgkqhkiG9w0BCQEW +DmFlc0BhbWF6b24uY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC8v/X5 +zZv8CAVfNmvBM0br/RUcf1wU8xC5d2otFQQsQKB3qiWoj3oHeOWskOlTPFVZ8N+/ +hEaMjyOUkg2+g6XEagCQtFCEBzUVoMjiQIBPiWj5CWkFtlav2zt33LZ0ErTND4xl +j7FQFqbaytHU9xuQcFO2p12bdITiBs5Kwoi9bQIDAQABo4IBCjCCAQYwHQYDVR0O +BBYEFPQnsX1kDVzPtX+38ACV8RhoYcw8MIHWBgNVHSMEgc4wgcuAFPQnsX1kDVzP +tX+38ACV8RhoYcw8oYGnpIGkMIGhMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2Vz +dGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xJzAlBgNVBAoTHkFtYXpvbiBE +ZXZlbG9wbWVudCBDZW50cmUgKFNBKTEMMAoGA1UECxMDQUVTMREwDwYDVQQDEwhB +RVMgVGVzdDEdMBsGCSqGSIb3DQEJARYOYWVzQGFtYXpvbi5jb22CCQCw52VfpaWX +UjAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBBQUAA4GBAJJlWll4uGlrqBzeIw7u +M3RvomlxMESwGKb9gI+ZeORlnHAyZxvd9XngIcjPuU+8uc3wc10LRQUCn45a5hFs +zaCp9BSewLCCirn6awZn2tP8JlagSbjrN9YShStt8S3S/Jj+eBoRvc7jJnmEeMkx +O0wHOzp5ZHRDK7tGULD6jCfU +-END CERTIFICATE- === modified file 'debian/copyright' --- debian/copyright 2013-05-05 19:43:21 + +++ debian/copyright 2013-05-23 13:09:19 + @@ -29,3 +29,10 @@ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +Files: debian/cert-ec2.pem +Copyright: Copyright Amazon.com, Inc or its affiliates. +License: Amazon Software License +Comment: Amazon's EC2 public certificate + Amazon's EC2 public certificate is copied from + http://s3.amazonaws.com/ec2-downloads/ec2-ami-tools.zip + is required to sign an image to upload and use in EC2. === added file 'debian/dirs' --- debian/dirs 1970-01-01 00:00:00 + +++ debian/dirs 2013-05-23 12:57:03 + @@ -0,0 +1 @@ +etc/ssl/certs/ === modified file 'debian/install' --- debian/install 2010-01-17 21:36:04 + +++ debian/install 2013-05-23 13:23:55 + @@ -1 +1,2 @@ bin/* /usr/bin/ +debian/cert-ec2.pem /usr/share/euca2ools/ === added file 'debian/links' --- debian/links 1970-01-01 00:00:00 + +++ debian/links 2013-05-23 12:57:03 + @@ -0,0 +1 @@ +usr/share/euca2ools/cert-ec2.pem etc/ssl/certs/cert-ec2.pem
Bug#650480: updated debian/watch in ubuntu
Boto is now moving away from google code and over to github. I've updated the debian/watch to point to github now: version=3 opts=uversionmangle=s/(([ab]|rc)[0-9])$/~\1/ \ https://github.com/boto/boto/downloads \ /downloads/boto/boto/boto-(.*).tar.gz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650480: python-boto: debian/watch needs updating
Package: python-boto Version: 2.0-0ubuntu1 Severity: normal Dear Maintainer, $ uscan --verbose -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: http://code.google.com/p/boto/ http://boto.googlecode.com/files/boto-(.+).tar.gz uscan warning: In debian/watch, no matching hrefs for watch line http://code.google.com/p/boto/ http://boto.googlecode.com/files/boto-(.+).tar.gz -- Scan finished In the Ubuntu package I've fixed uscan with the following debian/watch file, which uses googlecode.debian.net reformatter and also accounts for the non-standard naming convention that boto they've used: version=3 opts=uversionmangle=s/(([ab]|rc)[0-9])$/~\1/ \ http://googlecode.debian.net/p/boto/boto-(.*)\.tar\.gz -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise'), (100, 'precise-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-boto depends on: ii python 2.7.2-9ubuntu1 ii python2.7 2.7.2-5ubuntu1 python-boto recommends no packages. python-boto suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646597: rabbitmq-server starts 3 processes that do nothing bug wait
Package: rabbitmq-server
Version: 2.6.1-1
Severity: minor
After installing and starting rabbitmq-server, a 'ps' will show something
like:
$ ps axw | grep [r]abbit
2688 ? Ss 0:00 sh -c RABBITMQ_PID_FILE=/var/run/rabbitmq/pid /usr/sb ...
2691 ? S 0:00 /bin/sh /usr/sbin/rabbitmq-server
2697 ? S 0:00 su rabbitmq -s /bin/sh -c /usr/lib/rabb ...
2699 ? S 0:00 sh -c /usr/lib/rabbitmq/bin/rabbitmq-server
2700 ? Sl 0:00 /usr/lib/erlang/erts-5.8.4/bin/beam ...
Above, pids 2688, 2697, 2699 are doing nothing but waiting for other
processes to exit. They're simply a waste.
In bug #646473, I submitted a fix to get rid of the 'sh -c
RABBITMQ_PID_FILE' process. The patch below will remove the other 2.
The patch does a couple things:
* replace the built-in re-quoting with use of 'getopt'. getopt is
util-linux, which is 'essential' so this shouldnt be a big deal.
The previous quoting would have had issues with some arguments.
getopt understands shell quoting, it makes sense to use it.
* if perl is installed (the extremely likely case), then 'runas' will
utilize it to change permissions and then execute the rabbitmq
server process as the un-priviledged user.
If perl is not installed, it will take the old 'su' path.
* use 'exec' if we're already running as the rabbitmq user.
=== modified file 'debian/rabbitmq-script-wrapper'
--- debian/rabbitmq-script-wrapper 2011-02-05 10:21:16 +
+++ debian/rabbitmq-script-wrapper 2011-10-24 14:53:46 +
@@ -15,24 +15,30 @@
## Copyright (c) 2007-2011 VMware, Inc. All rights reserved.
##
-# Escape spaces and quotes, because shell is revolting.
-for arg in $@ ; do
- # Escape quotes in parameters, so that they're passed through cleanly.
- arg=$(sed -e 's//\\/g' -END
- $arg
- END
- )
- CMDLINE=${CMDLINE} \${arg}\
-done
+runas() {
+local user=$1 cmd=
+shift;
+if command -v perl /dev/null; then
+# using perl rather than su stops a 'su' process from hanging around
+PATH=/usr/local/bin:/usr/bin:/bin; USER=$user; LOGNAME=$user
+exec perl -e '@pwd = getpwnam('$user');
+$( = $) = $pwd[3]; $ = $ = $pwd[2];
+$ENV{'HOME'} = $pwd[7]; exec @ARGV' -- $@
+else
+# use getopt to handle escaping shell variables, and su to change user
+cmd=$(getopt --shell sh --options -- -- $@) cmd=${cmd# --}
+exec su $user -s /bin/sh -c exec $cmd
+fi
+}
cd /var/lib/rabbitmq
SCRIPT=`basename $0`
if [ `id -u` = 0 ] ; then
-su rabbitmq -s /bin/sh -c /usr/lib/rabbitmq/bin/${SCRIPT} ${CMDLINE}
+runas rabbitmq /usr/lib/rabbitmq/bin/${SCRIPT} $@
elif [ `id -u` = `id -u rabbitmq` ] ; then
-/usr/lib/rabbitmq/bin/${SCRIPT} $@
+exec /usr/lib/rabbitmq/bin/${SCRIPT} $@
else
/usr/lib/rabbitmq/bin/${SCRIPT}
echo
-- System Information:
Debian Release: 6.0.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-xen-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rabbitmq-server depends on:
ii adduser 3.112+nmu2
ii erlang-nox 1:14.b.3-dfsg-2
ii logrotate 3.7.8-6
rabbitmq-server recommends no packages.
rabbitmq-server suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646175: pkill beam
On 24/10/11 14:43:37, Simon MacMullen wrote: On 21/10/11 22:24, Scott Moser wrote: I think that the issues is that the 'beam' program is not stopping soon enough or at all. Thanks for the bug report. I'm not sure whether just killing beam is the right thing to do but we'll look into it. Why would it be any different than killing epmd, which is already being done? On purge, the user is clearly asking for this thing to go away, they do not care about any data loss that might be incurred by killing the processes. I'm just curious what you're thinking. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646473: rabbitmq-server.init does not clouse filedescriptors for rabbitmq-server
Package: rabbitmq-server
Version: 2.6.1-1
Severity: normal
Currently, the rabbitmq init script does this to invoke
/usr/sbin/rabbitmq-server ($DAEMON):
setsid sh -c $DAEMON ${INIT_LOG_DIR}/startup_log \
2 ${INIT_LOG_DIR}/startup_err
$CONTROL wait /dev/null 21
That leaves stdin and stdout and stderr open for that daemon process.
The issue with this is if the user does something like:
apt-get install rabbitmq-server | tee
The stdin from 'sh -c' to 'tee' will never get closed, and it will hang
around even after apt is well done. This sometimes shows itself on the
command line directly but is always reproducible with:
ssh root@hostname 'apt-get install -y rabbitmq-server | tee my.log'
This is Ubuntu bug 878600.
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/878600
The fix is simply to do:
RABBITMQ_PID_FILE=$PID_FILE setsid $DAEMON \
${INIT_LOG_DIR}/startup_log 2 ${INIT_LOG_DIR}/startup_err 0-
$CONTROL wait $PID_FILE /dev/null 21
Which then closes stdin, stdout, stderr explicitly for that subproces.
-- System Information:
Debian Release: wheezy/sid
APT prefers oneiric-updates
APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500,
'oneiric'), (100, 'oneiric-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-12-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646175: rabbitmq-server: fails to purge: `userdel rabbitmq' returned error code 8
Package: rabbitmq-server Version: 2.6.1-1 Severity: important # apt-get --purge remove rabbitmq-server Reading package lists... Done Building dependency tree ... Stopping rabbitmq-server: rabbitmq-server. Purging configuration files for rabbitmq-server ... Removing user `rabbitmq' ... Warning: group `rabbitmq' has no more members. userdel: user rabbitmq is currently logged in /usr/sbin/deluser: `/usr/sbin/userdel rabbitmq' returned error code 8. Exiting. dpkg: error processing rabbitmq-server (--purge): subprocess installed post-removal script returned error exit status 1 Processing triggers for man-db ... configured to not write apport reports Errors were encountered while processing: rabbitmq-server E: Sub-process /usr/bin/dpkg returned an error code (1) I think that the issues is that the 'beam' program is not stopping soon enough or at all. I'm able to avoid the failure with this: # diff -u info/rabbitmq-server.postrm.dist info/rabbitmq-server.postrm --- info/rabbitmq-server.postrm.dist2011-09-27 16:35:50.0 + +++ info/rabbitmq-server.postrm 2011-10-21 21:22:22.0 + @@ -39,6 +39,7 @@ if getent passwd rabbitmq /dev/null; then # Stop epmd if run by the rabbitmq user pkill -u rabbitmq epmd || : +pkill -u rabbitmq beam || : deluser rabbitmq fi This is ubuntu bug 878597. -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric'), (100, 'oneiric-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-12-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645354: [Pkg-fonts-devel] Bug#645354: ttf-nanum: contained fontconfig setting files force to make it default font
On Sat, 15 Oct 2011, Changwoo Ryu wrote: 2011-10-14 (금), 15:19 -0400, Scott Moser: That fix will break default Debian desktop in Korean language. Obviously, that setting was intentional to make Nanum fonts as defaults. This is an ugly way. But this is an easy way to make Nanum fonts as defaults, until the modification of fontconfig default setting. AFAIK Ubuntu has massively customized fontconfig default setting, including Nanum font default settings. But I strongly disagree with such a way; I want to modify the upstream fontconfig settings. Thank you for your response, your input is greatly appreciated. I admit to not knowing much about the way font defaults are handled, and especially in non-English paths. I just saw that ttf-nanum was unmodified in ubuntu at this point, and that this might also affect the package on debian. Thanks for your input. Scott
Bug#645354: ttf-nanum: contained fontconfig setting files force to make it default font
Package: ttf-nanum Version: 3.010-1 Severity: normal Tags: patch This issue was originally reported in Ubuntu bug 835304 (http://pad.lv/835304). It seems that it would also affect the debian package of the same version, and an Ubuntu user has submitted a fix. Jinkyu Yi submitted the following fix to Ubuntu. diff -Nru ttf-nanum-3.010/debian/90-ttf-nanum.conf ttf-nanum-3.010/debian/90-ttf-nanum.conf --- ttf-nanum-3.010/debian/90-ttf-nanum.conf2011-02-02 06:12:33.0 +0900 +++ ttf-nanum-3.010/debian/90-ttf-nanum.conf2011-08-27 17:22:23.0 +0900 @@ -14,16 +14,6 @@ constbold/const /edit /match - !-- fallback of the MS fonts -- - alias -familyGulim/familyfamily굴림/family -familyDotum/familyfamily돋움/family -preferfamilyNanumGothic/family/prefer - /alias - alias -familyBatang/familyfamily바탕/family -preferfamilyNanumMyeongjo/family/prefer - /alias !-- specify fallbacks for the missing glyphs. -- match target=pattern test name=family compare=eq @@ -43,28 +33,4 @@ stringDejaVu Serif/string /edit /match - !-- default sans and serif - TODO: it will be moved to fontconfig default configs -- - match target=pattern -test qual=any name=lang compare=contains - stringko/string -/test -test qual=any name=family compare=eq - stringsans-serif/string -/test -edit name=family mode=prepend_first binding=same - stringNanumGothic/string -/edit - /match - match target=pattern -test qual=any name=lang compare=contains - stringko/string -/test -test qual=any name=family compare=eq - stringserif/string -/test -edit name=family mode=prepend_first binding=same - stringNanumMyeongjo/string -/edit - /match /fontconfig diff -Nru ttf-nanum-3.010/debian/changelog ttf-nanum-3.010/debian/changelog --- ttf-nanum-3.010/debian/changelog2011-02-02 06:38:52.0 +0900 +++ ttf-nanum-3.010/debian/changelog2011-08-27 17:47:15.0 +0900 @@ -1,3 +1,12 @@ +ttf-nanum (3.010-2) unstable; urgency=low + + * LP: #835304 + * debian/90-ttf-nanum.conf: +- Remove MS Korean font aliases +- Remove sans-serif and serif settings for language-selector + + -- Jinkyu Yi jincrea...@jincreator.net Sat, 27 Aug 2011 17:38:45 +0900 + ttf-nanum (3.010-1) unstable; urgency=low * New upstream release -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-12-generic (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642544: isc-dhcp-client: dhclient-script is broken for read-only root
Package: isc-dhcp-client Version: 4.1.1-P1-17ubuntu9 Severity: normal This is ubuntu bug 857524 [http://pad.lv/857524]. debian/dhclient-script.linux will not work with read-only root. For a read-only root to work, and support dhclient-script writing to /etc/resolv.conf, then /etc/resolv.conf would have to be a symlink to a writeable location (ie, /run or /var/run). Currently, that will not work as dhclient-script will write to /etc/resolv.conf.dhclient-script.new which will fail. It should, instead write directly to /etc/resolv.conf, following the symlink if it is. This bug has been raised against Ubuntu, and a patch is attached there for Ubuntu. I would be willing to write a patch to fix this in debian, but there are many changes in ubuntu's debian/dhclient-script.linux that may also be desirable, so I'm opting to not do that, but suggest reviewing the full diff against Ubuntu's script. -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-11-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages isc-dhcp-client depends on: ii debianutils 4.0.2 Miscellaneous utilities specific t ii iproute 20110315-1build1 networking and traffic control too ii isc-dhcp-common 4.1.1-P1-17ubuntu9 common files used by all the isc-d ii libc6 2.13-20ubuntu2 Embedded GNU C Library: Shared lib isc-dhcp-client recommends no packages. Versions of packages isc-dhcp-client suggests: ii apparmor2.7.0~beta1+bzr1774-1ubuntu1 User-space parser utility for AppA ii avahi-autoi 0.6.30-4ubuntu1 Avahi IPv4LL network address confi ii resolvconf 1.48ubuntu1 name server information handler -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633802: dkms leaves empty temp file in /tmp
Package: dkms Version: 2.1.1.2-5ubuntu1 Severity: normal Tags: patch dkms leaves a tmp file in /tmp each time it is run. $ ls -l /tmp/dkms* ls: cannot access /tmp/dkms*: No such file or directory $ /usr/sbin/dkms $ echo $? 0 $ ls -l /tmp/dkms* -rw--- 1 smoser smoser 0 2011-07-13 16:32 /tmp/dkms.gooAoqPK $ dpkg-query --show dkms dkms 2.1.1.2-5ubuntu1 This was introduced in the debian patch use-system-tmpdir.patch The following patch will fix the issue: --- debian/patches/use-system-tmpdir.patch 2010-06-04 13:53:23 + +++ debian/patches/use-system-tmpdir.patch 2011-07-13 20:40:21 + @@ -1,14 +1,16 @@ Description: Use system setting for tmpdir Author: Michael Gilbert michael.s.gilb...@gmail.com +Last-update: 2011-07-13 --- dkms-2.1.1.2.orig/dkms +++ dkms-2.1.1.2/dkms -@@ -3592,7 +3592,8 @@ current_kernel=`uname -r` +@@ -3592,7 +3592,9 @@ current_kernel=`uname -r` dkms_tree=/var/lib/dkms source_tree=/usr/src install_tree=/lib/modules -tmp_location=/tmp +tmp_file=`mktemp --tmpdir dkms.` +tmp_location=`dirname $tmp_file` ++rm -f $tmp_file verbose= dkms_frameworkconf=/etc/dkms/framework.conf -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric') Architecture: amd64 (x86_64) Kernel: Linux 3.0-2-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dkms depends on: ii build-essential 11.5ubuntu1 Informational list of build-essent ii coreutils 8.5-1ubuntu6 GNU core utilities ii dpkg-dev1.16.0.3ubuntu3 Debian package development tools ii gcc 4:4.6.0-5ubuntu1 The GNU C compiler ii make3.81-8.1ubuntu1 An utility for Directing compilati ii module-init-tools 3.16-1ubuntu1tools for managing Linux kernel mo ii patch 2.6.1-2 Apply a diff file to an original Versions of packages dkms recommends: ii fakeroot1.16-1 tool for simulating superuser priv ii linux-headers-2.6.39-3 2.6.39-3.10 Header files related to Linux kern ii linux-headers-2.6.39-3- 2.6.39-3.10 Linux kernel headers for version 2 ii linux-headers-3.0.0-5 [ 3.0.0-5.6Header files related to Linux kern ii linux-headers-3.0.0-5-g 3.0.0-5.6Linux kernel headers for version 3 ii linux-headers-generic 3.0.0.5.6Generic Linux kernel headers ii linux-image-3.0.0-5-gen 3.0.0-5.6Linux kernel image for version 3.0 ii menu2.1.45ubuntu1generates programs menu for all me ii sudo1.7.4p6-1ubuntu1 Provide limited super user privile dkms suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633802: patch
I included the patch to debian/patches/use-system-tmpdir.patch above, but to be more obvious, heres the change to 'dkms' directly. --- dkms 2011-03-12 11:07:47 + +++ dkms 2011-07-13 20:38:55 + @@ -3601,6 +3601,7 @@ install_tree=/lib/modules tmp_file=`mktemp --tmpdir dkms.` tmp_location=`dirname $tmp_file` +rm -f $tmp_file verbose= dkms_frameworkconf=/etc/dkms/framework.conf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630756: [uscan] support parsing S3 bucket listings
Package: devscripts Version: 2.10.69ubuntu2 Severity: wishlist File: /usr/bin/uscan Tags: patch A few (admittedly very few) upstreams host their files on S3. By default, S3 does not do apache like file listings, but instead gives file listing in XML format. uscan can be modified to allow watch files that reference these listings. Attached is a suggested patch. See also ubuntu bug 798293 (http://bugs.launchpad.net/bugs/798293). There is very little chance for false positives, and the content that is found in s3 bucket listings is well defined so it is not likely to stop working. Before considering the content to be an S3 bucket listing, it checks: a.) that the file begins with ?xml b.) that it contains the string 'xmlns=http://s3.amazonaws.com/doc/2006-03-01/' -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- DEBSIGN_KEYID=024BC6F0 DEBUILD_DPKG_BUILDPACKAGE_OPTS=--source-option=--abort-on-upstream-changes -- System Information: Debian Release: squeeze/sid APT prefers natty-updates APT policy: (500, 'natty-updates'), (500, 'natty-security'), (500, 'natty') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-8-server (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages devscripts depends on: ii dpkg-dev 1.16.0~ubuntu7 Debian package development tools ii libc6 2.13-0ubuntu13 Embedded GNU C Library: Shared lib ii perl 5.10.1-17ubuntu4.1 Larry Wall's Practical Extraction Versions of packages devscripts recommends: ii 3.1.12-1ubuntu2 Delayed job execution and batch pr ii 8.1.2-0.20100314cvs-1 simple mail user agent ii 2.3.1-1ubuntu1 easy to use distributed version co ii 7.21.3-1ubuntu1 Get a file from an HTTP, HTTPS or ii 2.14.5 Command-line tools to process Debi ii 0.9.6.1ubuntu1 Debian package upload tool ii 1.14.4-1ubuntu1 Gives a fake root environment ii 4.0.1+build1+nobinonly-0ubuntu0.11.04.3 Safe and easy web browser from Moz ii 1:1.7.4.1-3 fast, scalable, distributed revisi ii 1.4.11-3ubuntu1 GNU privacy guard - a free PGP rep ii 2.1500-1Authen::SASL - SASL Authentication ii 2.27-1 Perl module to parse and convert t ii 2.005-2 Easy OO parsing of Debian control- ii 0.2-4build3 Perl extension for retrieving term ii 1.2000-1collection of modules to manipulat ii 1.56-1 module to manipulate and access UR ii 5.837-1 simple and consistent interface to ii 2.5.0~rc2ubuntu3Debian package checker ii 4.0-0ubuntu11 Linux Standard Base version report ii 4.43-14ubuntu2 Compression method of 7z format in ii 2.5.9-4 on-line manual pager ii 1:5.8p1-1ubuntu3secure shell (SSH) client, for sec ii 2.6-3 Apply a diff file to an original ii 0.3.1-2build1 Utilities to work with patches ii 0.0.6ubuntu2Utilities for sensible alternative ii 4.5.20-2ubuntu2 A system call tracer ii 1.6.12dfsg-4ubuntu2.1 Advanced version control system ii 6.0-4ubuntu1De-archiver for .zip files ii 0.5.3-1 WWW browsable pager with excellent ii 0.6.3-1 Compares two files word by word ii 1.12-2.1ubuntu2 retrieves files from the web ii 5.0.0-2 XZ-format compression utilities Versions of packages devscripts suggests: ii build-essential 11.5ubuntu1 Informational list of build-essent pn cvs-buildpackage none (no description available) ii debian-keyring [debian-maint 2010.12.29 GnuPG keys of Debian Developers pn devscripts-elnone (no description available) pn equivs none (no description available) pn gnuplot none (no description available) pn libcrypt-ssleay-perl none (no description available) ii libfile-desktopentry-perl0.04-2 Perl module to handle freedesktop pn libnet-smtp-ssl-perl none (no description available) pn libsoap-lite-perlnone (no description available) pn libyaml-syck-perlnone (no description available) pn mutt none (no description
Bug#629457: postinst configure uses dpkg --compare-versions badly
Package: amavisd-new Version: 1:2.6.4-3 File: /var/lib/dpkg/info/amavisd-new.postinst Severity: normal /var/lib/dpkg/info/amavisd-new.postinst does the following: | # Work around dpkg not deleting removed conffiles | | # (template directories (with files) removed in 1:2.3.3-2) | if dpkg --compare-versions 1:2.3.3-2 gt-nl $1 ; then When invoked for configure or upgradae, the postinst script runs the above. In that context, $1 is the original input to the 'configure'. Thus, dpkg --compare-versions 1:2.3.3-2 gt-nl configure which is obviously not intended. Instead that line should say: | if dpkg --compare-versions 1:2.3.3-2 gt-nl $2 ; then -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages amavisd-new depends on: ii adduser 3.112+nmu2 add and remove users and groups ii debconf [debconf-2.0]1.5.36.1Debian configuration management sy ii file 5.04-5 Determines file type using magic ii libarchive-zip-perl 1.30-3 Perl module for manipulation of ZI ii libberkeleydb-perl 0.42-1~squeeze1 use Berkeley DB 4 databases from P ii libcompress-raw-zlib-per 2.026-1 low-level interface to zlib compre ii libconvert-tnef-perl 0.17-9 Perl module to read TNEF files ii libconvert-uulib-perl1.12-1 Perl interface to the uulib librar pn libdigest-md5-perl none (no description available) ii libio-stringy-perl 2.110-4 Perl modules for IO from scalars a ii libmail-dkim-perl0.38-1 cryptographically identify the sen ii libmailtools-perl2.06-1 Manipulate email in perl programs pn libmime-base64-perl none (no description available) ii libmime-tools-perl 5.428-1 Perl5 modules for MIME-compliant m ii libnet-server-perl 0.97-1 An extensible, general perl server ii libunix-syslog-perl 1.1-2 Perl interface to the UNIX syslog( ii pax 1:20090728-1Portable Archive Interchange ii perl [libtime-hires-perl 5.10.1-17 Larry Wall's Practical Extraction ii perl-modules [libarchive 5.10.1-17 Core Perl modules amavisd-new recommends no packages. Versions of packages amavisd-new suggests: pn apt-listchanges none (no description available) pn arj none (no description available) pn cabextractnone (no description available) pn clamavnone (no description available) pn clamav-daemon none (no description available) ii cpio 2.11-4 GNU cpio -- a program to manage ar pn dspam none (no description available) pn lha none (no description available) pn libauthen-sasl-perl none (no description available) pn libdbi-perl none (no description available) ii libmail-dkim-perl 0.38-1 cryptographically identify the sen pn libnet-ldap-perl none (no description available) pn libsnmp-perl none (no description available) pn lzop none (no description available) pn nomarch none (no description available) pn p7zip none (no description available) pn rpm none (no description available) pn spamassassin none (no description available) pn unrar none (no description available) pn unrar-freenone (no description available) pn zoo none (no description available) -- debconf information: amavisd-new/outdated_config_style_warning: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607129: vsftpd should not use grep in checking for group and user
Package: vsftpd
Version: 2.3.2-6
Severity: wishlist
vsftpd.postinst does
if ! getent passwd | grep -q ^${_USERNAME}:
and
elif ! getent group | grep -q ^${_USERNAME}:
the grep could potentiall hit a false positive due to its interpretation
of ${_USERNAME} as a regular expression. For example, _USERNAME could
be ftp.user which would then match ftp_user also.
This is mostly an edge case, but a '.' is allowable in unix user names.
The other small benefit of not using grep is avoiding a fork for some
minuscule performance benefit.
Instead of the grep, let 'getent' do the match for you:
- if ! getent passwd | grep -q ^${_USERNAME}:
+ if ! getent passwd ${_USERNAME}
and
- elif ! getent group | grep -q ^${_USERNAME}:
+ elif ! getent group ${USERNAME}
This was brought up under ubuntu bug 629234
(https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/629234)
-- System Information:
Debian Release: squeeze/sid
APT prefers natty-updates
APT policy: (500, 'natty-updates'), (500, 'natty-security'), (500, 'natty')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.37-8-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607129: suggested debdiff
diff -Nru vsftpd-2.3.2/debian/changelog vsftpd-2.3.2/debian/changelog
--- vsftpd-2.3.2/debian/changelog 2010-12-06 07:10:53.0 -0500
+++ vsftpd-2.3.2/debian/changelog 2010-12-14 16:16:22.0 -0500
@@ -1,3 +1,9 @@
+vsftpd (2.3.2-7) experimental; urgency=low
+
+ * fix small potential issue with adding new user (Closes #607129)
+
+ -- Scott Moser smo...@ubuntu.com Tue, 14 Dec 2010 16:15:38 -0500
+
vsftpd (2.3.2-6) experimental; urgency=low
* Adding Danish debconf translations from Joe Dalton
diff -Nru vsftpd-2.3.2/debian/vsftpd.postinst
vsftpd-2.3.2/debian/vsftpd.postinst
--- vsftpd-2.3.2/debian/vsftpd.postinst 2010-11-26 11:20:26.0 -0500
+++ vsftpd-2.3.2/debian/vsftpd.postinst 2010-12-14 16:17:08.0 -0500
@@ -16,10 +16,10 @@
db_stop
- if ! getent passwd | grep -q ^${_USERNAME}:
+ if ! getent passwd ${_USERNAME}
then
adduser --system --home ${_DIRECTORY} --no-create-home
--quiet --gecos 'ftp daemon' --group ${_USERNAME}
- elif ! getent group | grep -q ^${_USERNAME}:
+ elif ! getent group ${_USERNAME}
then
addgroup --system --quiet ${_USERNAME}
gpasswd -a ${_USERNAME} ${_USERNAME}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
