Bug#860727: Please update to latest version
Package: python-networkmanager Version: 0.9.10-1 Severity: normal The current python-networkmanager package dates from 2013. There's been plenty of releases after that. Please update it to the latest version, thank you. -- Cheers, Marga
Bug#851774: Stop using apt-key add to add keys in generators/60local
Package: apt-setup Version: 1:0.123 Severity: serious For a long time it's been possible to preseed a local repository that has it's own keyring. However, with the latest changes related to gpg dependencies getting dropped in apt, this is no longer possible. I'm setting severity as serious as adviced by Julien Cristau on IRC. With the current state of things, in order to install a local repository with a keyring the user needs to somehow create a script that will put the keyring in place before 60local runs, and not preseed the keyring at all. If the keyring is preseeded, *the whole installation will fail* because apt-key add fails which causes 60local to fail, which causes the install base system step to fail. This is the offending code: https://sources.debian.net/src/apt-setup/1:0.123/generators/60local/#L33 This is using the deprecated apt-key add functionality. From the apt-key manpage: COMMANDS add filename (...) Note: Instead of using this command a keyring should be placed directly in the /etc/apt/trusted.gpg.d/ directory with a descriptive name and either "gpg" or "asc" as file extension. So, the right thing to do is to copy the file to the right path instead of calling apt-key add with it. This was fixed in pbuilder back in September: pbuilder (0.226.1) unstable; urgency=medium [ James Clarke ] * modules: add_additional_aptkeyrings: Copy keyrings to /etc/apt/trusted.gpg.d instead of using apt-key. We can no longer rely on being able to use apt-key in a minimal chroot, because gnupg has been demoted to a Recommends in apt. Instead, the keyrings can be copied directly into /etc/apt/trusted.gpg.d. Moreover, `apt-key` usage has been discuraged over the past years. This means that using the APTKEYRINGS option of pbuilder won't actually work with chroots older than squeeze (APT version 0.7.25.1) -- Regards, Marga -- Cheers, Marga
Bug#810158: This needs to be fixed
Control: tags -1 -wontfix With the change in debootstrap, this bug is now preventing ksh from getting installed in a fresh installation. In my case, this is even causing my automated install to fail because there's a package that tries to pull in ksh and so everything fails. The patch is pretty straightforward and it's basically the same that has already been applied in mksh: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807185 Please fix this. Thanks. -- Cheers, Marga
Bug#796583: How are people supposed to deal with the missing setterm calls?
The NEWS.Debian file says that users should move to console-setup instead of kbd, which would be fine if console-setup provided the same functionality. For certain things, it doesn't. Look at this snippet from the old init script: # screensaver stuff setterm_args="" if [ "$BLANK_TIME" ]; then setterm_args="$setterm_args -blank $BLANK_TIME" fi if [ "$BLANK_DPMS" ]; then setterm_args="$setterm_args -powersave $BLANK_DPMS" fi if [ "$POWERDOWN_TIME" ]; then setterm_args="$setterm_args -powerdown $POWERDOWN_TIME" fi if [ "$setterm_args" ]; then setterm $setterm_args fi As far as I can see, there's nothing in console-setup that provides this functionality. At all. Is each and every user of kbd expected to now write their own init script that calls setterm with the right arguments? Why was this dropped without providing an alternative? -- Cheers, Marga
Bug#820310: dh_lintian doesn't copy overrides for automatic -dbgsym packages
On Thu, Apr 7, 2016, 19:18 Niels Thykierwrote: > What tags are you observing with your dbgsym packages? Ideally the > debhelper generated packages should be fully policy compliant with no > lintian warnings (provided you use an up to date lintian). > It was an internal package that shipped binaries that had been pre-compiled, thus missing debugging symbols (the .debug files did have the strings though, as the original binaries were unstripped). -- Cheers, Marga
Bug#747851: Very simple fix for an annoying bug
Hi, I'm encountering this issue with an internal package that ships an upstart script and a systemd script but no sysv script. It's actually a very simple fix: --- debian/src/sysv-rc/sbin/invoke-rc.d 2015-05-20 07:54:32.0 +0200 +++ /usr/sbin/invoke-rc.d 2015-11-26 13:24:21.772967974 +0100 @@ -464,7 +464,7 @@ ## note that $ACTION is a space-separated list of actions ## to be attempted in order until one suceeds. if test x${FORCE} != x || test ${RC} -eq 104 ; then -if [ -n "$is_upstart" ] || testexec "${INITDPREFIX}${INITSCRIPTID}" ; then +if [ -n "$is_upstart" ] || [ -n "$is_systemd" ] || testexec "${INITDPREFIX}${INITSCRIPTID}" ; then RC=102 setechoactions ${ACTION} while test ! -z "${ACTION}" ; do Any chance that we can get this applied? I know that the expectation for packages in the distribution is to ship the old sysv script (and I agree that this is what should happen), but for internal packages not distributed broadly, used in a restricted environment, it makes little sense to create a script that will never get used. Thanks! -- Cheers, Marga
Bug#804693: Broken symlink: engine_pkcs11.so -> ../ssl/engines/engine_pkcs11.so
Package: libengine-pkcs11-openssl Version: 0.2.0-1 Severity: serious The package has a links file that says: usr/lib/ssl/engines/engine_pkcs11.so usr/lib/engines/engine_pkcs11.so However, with the latest version, the original file has been renamed to: usr/lib/ssl/engines/pkcs11.so >From https://packages.debian.org/sid/amd64/libengine-pkcs11-openssl/filelist : /usr/lib/engines/engine_pkcs11.so /usr/lib/ssl/engines/libpkcs11.la /usr/lib/ssl/engines/libpkcs11.so /usr/share/doc/libengine-pkcs11-openssl/changelog.Debian.alpha.gz /usr/share/doc/libengine-pkcs11-openssl/changelog.Debian.gz /usr/share/doc/libengine-pkcs11-openssl/copyright This should be a simple fix to the links file, but in the meantime it leads to brokenness for packages trying to use /usr/lib/engines/engine_pkcs11.so, so please fix it. Thanks! Marga -- Cheers, Marga
Bug#802591: Please provide libssl udeb as well as the libcrypto udeb
Control: tags -1 +patch As promised, here's the patch, applied to the version in unstable. Let me know if you want it applied to the version in experimental instead. -- Cheers, Marga -- Cheers, Marga openssl-libssl-udeb-unstable.debdiff Description: Binary data