Bug#837534: apt-listchanges: postinst runs a Python script out of /tmp/

Package: apt-listchanges Version: 3.3 Severity: critical Tags: security The postinst script runs a Python script that it creates in /tmp/. Unfortunately python will add the directory where the script resides to sys.path and all the imports will be thus resolved in that directory. A simple user

Bug#836076: O: splint

Package: wnpp Severity: normal User: de...@kali.org Usertags: origin-kali The splint package has not seen a maintainer upload since 2009 and its maintainer Y Giridhar Appaji Nag is missing in action). I'm therefore orphaning the package. At the same time I made a QA upload switching package

Bug#835983: python-pypdf2: Incorrect Breaks/Replaces which forbids co-installation with python-pypdf

Package: python-pypdf2 Version: 1.26.0-1 Severity: serious Justification: co-installation User: de...@kali.org Usertags: origin-kali python-pypdf and python-pypdf2 use a differente module name and can thus be co-installed... except that this is no longer possible because you added unversioned

Bug#834708: apache2: server locks up with "AH00288: scoreboard is full, not at MaxRequestWorkers"

Source: apache2 Version: 2.4.10-10+deb8u5 Severity: normal Tags: upstream Control: forwarded -1 https://bz.apache.org/bugzilla/show_bug.cgi?id=53555 We got hit by this bug on Debian Jessie running on tracker.debian.org. The server would not accept new connections until we force a restart. A

Bug#834515: sbuild-createchroot support of SUITE-VARIANT breaks when suite names contain dashes

Package: sbuild Version: 0.70.0-1 Severity: important User: de...@kali.org Usertags: origin-kali Hello, in Kali our main suite is named "kali-rolling" and our development release is called "kali-dev". When we try to use sbuild-createchroot, it will incorrectly assume that "kali-rolling" is a

Bug#832503: apt: foo:any dependency is not handled correctly when foo is not Multi-Arch: allowed

Package: apt Version: 1.3~pre2 Severity: normal User: de...@kali.org Usertags: origin-kali Hello dear APT maintainers, I have a package dependency "firefox-esr:any | firefox:any | www-browser" in a metapackage. Unfortunately firefox-esr is neither "Multi-Arch: foreign" nor "Multi-Arch: allowed"

Bug#832501: firefox-esr: Please mark as "Multi-Arch: foreign" (or allowed)

Package: firefox-esr Version: 45.2.0esr-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali In a Kali metapackage, we have a dependency on firefox-esr. But on arm64, we would like to be able to install "firefox-esr:armhf" (which actually works better right now). Unfortunately,

Bug#832102: transition: ftplib

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hello, I have small transition in the ftplib package, the SONAME got bumped but the API is fully backwards-compatible. The package is ready in experimental and I tested that the build

Bug#832053: devscripts: deblog command to display current and former build logs

Package: devscripts Version: 2.16.6 Severity: wishlist I find myself often typing: $ less ../build-area/ftplib_4.0-1-1_amd64.build or $ less ../build-area/ftplib_4.0-1-1_amd64-20160721-1340.build (usually playing with tab completion to find an older build log) I would like to have a "deblog"

Bug#832050: sbuild: Allow to run commands as root before/after installing the build dependencies

Package: sbuild Version: 0.69.0-2 Severity: wishlist I have updated a library and in the process I renamed ftplib-dev into libftp-dev (which provides "ftplib-dev") and I want to ensure that reverse dependencies build correctly with the new package. I used --extra-package to inject my package but

Bug#831737: pbnj: missing dependency on libshell-perl

Package: pbnj Version: 2.04-4.1 Severity: serious User: de...@kali.org Usertags: origin-kali Forwarding a bug from Kali: https://bugs.kali.org/view.php?id=3420 root@kali # apt-get install pbnj ( accept dependencies and install ) root@kali # scanpbnj Can't locate Shell.pm in @INC blah, blah,

Bug#831730: desktop-base: Integration with KDE's plasma-desktop seems to no longer work with current version

Package: desktop-base Version: 8.0.2 Severity: important User: de...@kali.org Usertags: origin-kali When you install KDE on a fresh system, the default wallpaper that you get is not the one provided by desktop-base. So it looks like that the integration provided by

Bug#830795: nautilus: Trying to change a folder's icon in the properties dialog freezes nautilus

Package: nautilus Version: 3.20.1-3 Severity: important Tags: upstream patch User: de...@kali.org Usertags: origin-kali Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=767229 If you right click on a folder, then select "Properties" and then click on the icon to try to change it,

Bug#830288: wireless-regdb: New upstream release available, current version is out of date

Package: wireless-regdb Version: 2015.07.20-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali Hello Ben, there's a new upstream release available: https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2016.06.10.tar.xz It would be nice to update the Debian

Bug#828037: fontconfig: font-config should not register .dpkg-tmp files in its cache, users ends up seeing squares instead of expected characters

Package: fontconfig Version: 2.11.0-6.4 Severity: serious User: de...@kali.org Usertags: origin-kali For many months now, I have experienced myself and I have received dozens of reports (on the Kali side) of users having squares instead of the expected characters in their GNOME setup. The

Bug#827749: reprepro: Please add _removereference command to remove a reference to a given filekey

Package: reprepro Version: 4.17.1-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali I followed your advice to use temporary snapshots to keep some files around for a few days... and now I always have like 16 snapshots for the last 4 days. But from time to time, Debian uploads a

Bug#827741: libatk-wrapper-java: File selection dialog not refreshed when changing directory

Package: libatk-wrapper-java Version: 0.33.3-7 Severity: important User: de...@kali.org Usertags: origin-kali Hello Samuel, I got a new report of a problem related to libatk-wrapper-java: https://bugs.kali.org/view.php?id=3367 You can reproduce it with the zaproxy package:

Bug#827478: hydra: New upstream version available

Source: hydra Version: 8.1-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali Hello, it would be nice if you could update the package with version 8.2 that got recently released: http://www.thc.org/releases/hydra-8.2.tar.gz Also I would like to suggest you to join the new

Bug#825923: python-nltk: nltk/tokenize/api.py imports ntlk.six which has been dropped

Package: python-nltk Version: 3.2.1-1 Severity: grave Justification: renders package unusable User: de...@kali.org Usertags: origin-kali I just got a report on Kali that w3af no longer works: https://bugs.kali.org/view.php?id=3323 The stacktrace ends with this: File

Bug#824168: apt-listchanges: Should not display news for libraries and other packages that the user does not care about

Package: apt-listchanges Version: 2.89 Severity: wishlist It happened multiple times that I have been annoyed by a NEWS.Debian saying that some perl library installed on my system got some backwards incompatible change. I have that perl library as a dependency of something else and I don't care

Bug#824165: $apt_allow_unauthenticated = 1 in .sbuildrc breaks the chroot

Package: sbuild Version: 0.69.0-2 Severity: important $ sbuild-update --update source:jessie-amd64-sbuild source:jessie-amd64-sbuild: Performing update. E: Syntax error /var/lib/sbuild/apt.conf:3: Malformed tag Exiting from update with status 100. And the broken /var/lib/sbuild/apt.conf looks

Bug#822682: libharfbuzz0b: breaks display of ê/ô/û with fonts-cantarell

Package: libharfbuzz0b Version: 1.2.6-2 Severity: serious With this version of harfbuzz and fonts-cantarell 0.0.21-1 I get incorrectly formatted accents in labels in GTK-3 apps at least. A word like "Fenêtres" is badly displayed with the "t" being displayed on top of the "ê". The "^" accent is a

Bug#822670: dh-systemd should be merged into debhelper

Package: dh-systemd,debhelper Severity: wishlist Hello dh-systemd maintainers and debhelper maintainers, with the adoption of systemd as default init system for quite a while now, it does not make sense that we have to Build-Depend on dh-systemd and use dh --with systemd to be able to properly

Bug#822669: debhelper: dh_installinit add autoscript for non-existent init script when service file exists

Package: debhelper Version: 9.20160403 Severity: normal User: de...@kali.org Usertags: origin-kali If a package contains a debian/foo.service file that gets installed by dh_installinit (but no debian/foo.init) then the generated maintainer scripts will still contain the update-rc.d invocations

Bug#822157: python-future hides and breaks python-configparser

Source: python-future Version: 0.15.2-1 Severity: serious Tags: upstream User: de...@kali.org Usertags: origin-kali Control: forwarded -1 https://github.com/PythonCharmers/python-future/issues/118 Control: affects -1 python-configparser python-future provides the "configparser" module and so does

Bug#821070: samba-vfs-modules: File overwrite error on libnon-posix-acls.so.0 when upgrading from 4.2.10 in jessie to 4.3.6 in stretch

Package: samba-vfs-modules Version: 2:4.3.7+dfsg-1 Severity: serious User: de...@kali.org Usertags: origin-kali In a (Kali) Jenkins job that test upgrades from one release to the next I got this error: Preparing to unpack .../samba-vfs-modules_2%3a4.3.6+dfsg-1_i386.deb ... Unpacking

Bug#820867: reprepro: Please allow to apply overrides on already installed packages

Package: reprepro Version: 4.17.0-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali For some reasons it seems that "update" + "pull" rules do not properly transfer the priority... for instance I have the emdebian-archive-keyring which is priority extra in Debian's Packages files but

Bug#820660: reprepro: Generate by-hash indices and add Acquire-By-Hash: yes to InRelease

Package: reprepro Version: 4.17.0-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali See http://www.chiark.greenend.org.uk/~cjwatson/blog/no-more-hash-sum-mismatch-errors.html It looks like that APT supports now clean atomic updates of all the indices by retrieving index files

Bug#820288: wordpress: Keep alternate *-php5 and php5-* dependencies for installability in old releases

Source: wordpress Version: 4.4.2+dfsg-1 Severity: wishlist Hello, I'm running the wordpress package from unstable on wheezy/jessie and up to now it was working just fine (upgrading only some js packages from time to time). But now the package is uninstallable due to the switch to php-* and

Bug#819473: dh-golang: dh_golang generates invalid Built-Using field when Build-Depends is a virtual package

Package: dh-golang Version: 1.12 Severity: important User: de...@kali.org Usertags: origin-kali dh-make-golang had a Build-Depends with this: Build-Depends: debhelper (>= 9), [...] golang-blackfriday-dev | golang-github-russross-blackfriday-dev, [...] While golang-blackfriday-dev

Bug#819472: dh-make-golang builds not accepted due to invalid Built-Using

Package: dh-make-golang Version: 0.0~git20150913.0.1221041-1 Severity: serious User: de...@kali.org Usertags: origin-kali Recent builds of dh-make-golang (such as on arm64 or ppc64el) have been rejected by DAK because the package generated an invalid Built-Using field: Built-Using: golang (=

Bug#819059: firefox-esr: firefox should be compiled without MALLOC_STATIC_SIZES on arm64 too

Source: firefox-esr Version: 45.0.1esr-1 Severity: important Tags: patch User: de...@kali.org Usertags: origin-kali The Kali Linux arm64 porter (Steev Klimaszewski in copy) reported to me that firefox needs to be compiled without MALLOC_STATIC_SIZES for it to work on all ARM64

Bug#818907: live-build: Fails to integrate a binary package whose name contains an uppercase character

Package: live-build Version: 1:20151215 Severity: normal User: de...@kali.org Usertags: origin-kali If you download a Nessus deb from here: https://www.tenable.com/products/nessus/select-your-operating-system You get a Nessus-6.5.6-debian6_amd64.deb file for a "Nessus" package. Note the

Bug#818175: dh-python: "dh --with python3" should lead to dh_python3 failure if nothing is done

Package: dh-python Version: 2.20151103 Severity: wishlist User: de...@kali.org Usertags: origin-kali When I call "dh --with python3" it's because I know that the package is built with Python3 and I know that dh_python3 should do some work... So I would like

Bug#816714: wkhtmltopdf: Please package new upstream version 0.12.3

Source: wkhtmltopdf Version: 0.12.2.4-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali Upstream has published 0.12.3 in January. Also it would be nice to have a version of wkhtmltopdf that works headless. I don't know if this new version add this but the feature is advertised

Bug#816644: masscan: Package new upstream snapshot and pick a version number higher than in Kali

Package: masscan Version: 1.0.3-95-gb395f18~ds0-2 Severity: wishlist User: de...@kali.org Usertags: origin-kali Hello, Kali had a masscan package before Debian and much like Debian we packaged an upstream git snapshot: http://pkg.kali.org/pkg/masscan But for historical reason, we have an epoch

Bug#816554: cdebootstrap: Please add Kali as a know Origin

Package: cdebootstrap Version: 0.7.1 Severity: wishlist User: de...@kali.org Usertags: origin-kali Please add this to /usr/share/cdebootstrap/suites: Match-Origin: Kali Mirror: http://http.kali.org Keyring: kali-archive-keyring.gpg Thank you! -- System Information: Debian Release: stretch/sid

Bug#816553: cdebootstrap: --suite-config=sid makes cdebootstrap segfault

Package: cdebootstrap Version: 0.7.1 Severity: important User: de...@kali.org Usertags: origin-kali In Kali we use cdebootstrap and since our release were not known to cdebootstrap, we always used "--suite-config=sid" to ensure it used the same logic as the one of Debian. Nowadays with 0.7.1 if

Bug#814805: pyscard: Dropped python-pyscard without explanation

Source: pyscard Version: 1.9.2-1 Severity: serious User: de...@kali.org Usertags: origin-kali This version of pyscard dropped the Python 2 version without any explanation on why this was needed. In the process, you made yubioath-desktop uninstallable (as well as another package which is only

Bug#813786: apt: Warning "Can't drop privileges" when running "apt-get source" as root

Package: apt Version: 1.2.1 Severity: normal Simple to reproduce: $ LANG=C sudo apt-get source debian-installer [sudo] password for rhertzog: Reading package lists... Done Building dependency tree Reading state information... Done NOTICE: 'debian-installer' packaging is maintained in

Bug#813801: kismet: New upstream release 2016-01-R1 available

Source: kismet Severity: wishlist User: de...@kali.org Usertags: origin-kali Please package the new uptsream release 2016-01-R1. http://www.kismetwireless.net/code/kismet-2016-01-R1.tar.xz We updated the kismet package in Kali already and you might find some useful changes there (updated

Bug#811064: dh-exec: Specify optional files that should be installed when available

Package: dh-exec Version: 0.23 Severity: wishlist Sometimes I would like to install files when they are available, and not have to hardcode the precise list of conditions under which they are available or not. For example, I hade to make the pandoc build-dependency conditional so that it does

Bug#810785: ifupdown breaks debootstrap of Debian

Package: ifupdown Version: 0.8.5 Severity: critical Justification: breaks the whole system User: de...@kali.org debootstrap of stretch currently fails due to ifupdown: $ sudo debootstrap --components=main,contrib,non-free stretch stretch http://ftp.debian.org/debian [...] I: Unpacking

Bug#809440: lintian: runtime-test-file-is-not-a-regular-file complains about a symlink to a regular test file

Package: lintian Version: 2.5.39.1 Severity: normal With python-django 1.9-2 I get those tags: I: python-django source: runtime-test-file-is-not-a-regular-file debian/tests/django-admin-py3 I: python-django source: runtime-test-file-is-not-a-regular-file debian/tests/test-suite-py3 Both files

Bug#809442: autopkgtest: Add a way to run the same test script in multiple environments

Package: autopkgtest Version: 3.19 Severity: wishlist I just added some DEP-8 tests to python-django and it would have been nice if I could have reused the same script in multiple environments (python2 only, python3 only). Right now I created symlinks to the same script and the sole purpose of

Bug#809443: autopkgtest: support systemd-nspawn as an isolation-container level virtualization tool

Package: autopkgtest Version: 3.19 Severity: wishlist systemd-nspawn supports --template and/or --ephemeral (provided that you use btrfs) so that you can have throw-away chroots. It also supports various networking related options (--private-network notably) so that you can get proper network

Bug#808863: uhd-host: postinst fails when installed with a read-only /proc

Package: uhd-host Version: 3.9.1-5 Severity: normal User: de...@kali.org Usertags: origin-kali I'm running tests of upgrades in chroots managed by systemd-nspawn. By default /proc is read-only in such chroots and this lead to this failure: Setting up uhd-host (3.9.1-5) ... sysctl: setting key

Bug#808583: sbuild: Builds but does not put files into place, and outputs "Could not move to ."

Package: sbuild Version: 0.66.0-5 Severity: important This morning I wanted to build pysvn_1.8.0-1.dsc out of its git repository with "gbp buildpackage --git-builder=sbuild" (just like I usually do) but the I got warnings and errors at the end (the start was entirely normal, more comments after

Bug#808256: libnsgif: Should libnsgif be removed from Debian?

Source: libnsgif Severity: serious Hello, libnsgif has not seen a maintainer upload ever since its addition to Debian in 2009. Recently two CVE [1] have been reported against this package and I wonder why we have this package in Debian at all. [1]

Bug#808257: libnsbmp: Should libnsbmp be removed from Debian?

Source: libnsbmp Severity: serious Hello, libnsbmp has not seen a maintainer upload ever since its addition to Debian in 2009. Recently two CVE [1] have been reported against this package and I wonder why we have this package in Debian at all. [1]

Bug#807515: jessie-pu: package debian-handbook/8.20151209~deb8u1

Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hello, I would like to update the Debian Administrator's Handbook in jessie so that it documents jessie instead of wheezy. We finished the update about a month ago and basicly I'd

Bug#806781: tryton-modules-party: Need to specify the correct minimal version of python-stdnum

Package: tryton-modules-party Version: 3.8.0-1 Severity: normal Hello, I installed the backport of tryton on wheezy but I got a failure during database upgrade: 18474 140635880355584 [2015-12-01 08:46:27,838] INFO trytond.modules party:registering classes Traceback (most recent call last):

Bug#806237: lintian: false positive for obsolete-url-in-packaging in debian/watch

Package: lintian Version: 2.5.38.1 Severity: normal User: de...@kali.org Usertags: origin-kali I just got this warning: W: bully source: obsolete-url-in-packaging debian/watch http://code.google.com/p/wps-bully/ But my watch file is like this: $ cat debian/watch version=3 # The original

Bug#805291: preseed: Offer a way to override initrd-level preseeding with kernel command line preseeding

Source: preseed Version: 1.68 Severity: wishlist User: de...@kali.org Usertags: origin-kali In Kali, we rely on initrd preseeding to set a bunch of Debconf entries because it's the only sane way to ensure that we have those during netboot too. Unfortunately, it makes it very hard for end-users

Bug#804240: libsane: scanning does not work with HPLIP backend

Package: libsane Version: 1.0.25-1 Severity: serious Control: fixed -1 1.0.25+git20150927-1 With libsane 1.0.25-1 available in sid, I can't scan with my HP printer. I use this to start the scanning process: simple-scan hpaio:/net/HP_Color_LaserJet_2840?ip=192.168.1.10 With libsane 1.0.24-14 in

Bug#803066: tryton-server: problem with init scripts and "$DAEMON_OPTS" as set in /etc/default/tryton-server

Source: tryton-server Version: 3.6.3-2 Severity: important I'm not quite sure how this happened but I just upgraded from 3.4 to 3.6 on a wheezy server and /etc/default/tryton-server contained this: DAEMON_OPTS=" --config ${CONFIGFILE} --logconf ${LOGCONF} --cron" Note the initial space. With the

Bug#802671: bouncycastle: ECC private keys can be recovered via invalid curve attack

Source: bouncycastle Version: 1.44+dfsg-2 Severity: serious Tags: security Control: fixed -1 1.51-1 Hello, bouncycastle 1.49 in stable/testing/unstable (and 1.44 in wheezy/squeeze) is vulnerable to an invalid curve attack as described here:

Bug#802480: gnome-keyring: iceweasel gets stuck when login into a password-protected website

Package: gnome-keyring Version: 3.18.1-1 Severity: grave Justification: renders package unusable Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=756865 This is the continuation of #800660 (that I failed to re-open). There's still something fishy in gnome-keyring and I have filed

Bug#801926: mass-bug: option to include an external file

Package: devscripts Version: 2.15.9 Severity: wishlist Hello, When I use mass-bug, it's because I have rebuilt many packages and some of them failed to build. I need to provide the details to the packager... for now I host the build los on people.debian.org and provide a link but that's not

Bug#801666: git-dpm: Need a way to set the upstream branch names from within the repository

Package: git-dpm Version: 0.9.1-1 Severity: important Hello, Since the Python team now mandates git-dpm usage, I have to look into how to use it for my own packages and I immediately came across this limitation. The only way to configure the name of the various branches is through "git config".

Bug#801667: git-dpm offers no way to merge between different packaging branches

Package: git-dpm Version: 0.9.1-1 Severity: normal Still discovering git-dpm, I tried to do something basic: - make a packaging change in debian/sid (adding debian/README.source) - switch to debian/experimental - merge debian/sid into it to get the latest packaging changes But this doesn't work

Bug#801668: git-dpm: Should create the upstream tag when importing the upstream tarball

Package: git-dpm Version: 0.9.1-1 Severity: wishlist It looks git-dpm will only create the upstream tag with "git-dpm tag" and this operation can only be called when you want to tag a released package. However when I work on a new upstream release, it might take some time until the new release

Bug#800660: gnome-keyring: crashes iceweasel when logging into a password-protected website

Package: gnome-keyring Version: 3.18.0-1 Severity: grave Justification: renders package unusable Since I upgraded to gnome-keyring 3.18, I'm no longer able to login into password-protected website with iceweasel. It just gets stuck and I have to kill it. In the logs I see this: oct. 02 10:04:42

Bug#800013: valgrind: New upstream release available (3.11.0)

Package: valgrind Version: 1:3.10.1-4 Severity: wishlist User: de...@kali.org Usertags: origin-kali Hello, I just noticed[1] that there's a new upstream version of valgrind: http://valgrind.org/downloads/valgrind-3.11.0.tar.bz2 It would be nice to update the package in sid/stretch. Thank you!

Bug#799550: libuhd003v5 lost its v5 suffix...

Package: libuhd003 Version: 3.9.0-1 Severity: serious User: de...@kali.org Usertags: origin-kali I just noticed that with uhd 3.9.0 libuhd003 lost the v5 suffix that had been introduced with 3.8.5-2.1. And the changelog has no explanation for this. So to avoid problems when upgrading from jessie

Bug#798636: puppet: Plans to switch to puppet 4 (new upstream release)

Source: puppet Severity: wishlist Hello, what are your plans to switch to puppet 4? I see that the watch file currently tracks version 3 but upstream makes regular releases of version 4. Should version 4 be packaged separately or do you intend to switch to it? I do not know anything about the

Bug#798564: debootstrap: Add scripts for kali releases

Package: debootstrap Version: 1.0.72 Severity: wishlist User: de...@kali.org Usertags: origin-kali Control: block -1 by 798562 Hello, I'd like debootstrap to have native support of the various kali releases. We don't need any special script compared to Debian except that we use a different

Bug#798560: debootstrap: Add a --suite-config option replacing the need for the script parameter

Package: debootstrap Version: 1.0.72 Severity: wishlist User: de...@kali.org Usertags: origin-kali Most debootstrap wrappers allow you to inject arbitrary options and let you customize the target suite and the mirror. But very few let you specify the "script" parameter (the specific wrapper that

Bug#798562: debootstrap: Support "scripts" sharing code with Debian but with different default_mirror and keyring

Package: debootstrap Version: 1.0.72 Severity: wishlist User: de...@kali.org Usertags: origin-kali I would like to add a /u/s/debootstrap/scripts/kali file that behaves exactly like Debian's one except that it would have different meta-information at the top... in particular default_mirror and

Bug#798181: gnuradio: Some files take way too long to compile

Source: gnuradio Version: 3.7.8-2.2 Severity: important The package failed to build on mips recently because some files take way too long to compile and the build got killed due to inactivity: [ 65%] Building CXX object gr-blocks/swig/CMakeFiles/_blocks_swig5.dir/blocks_swig5PYTHON_wrap.cxx.o

Bug#798011: bugs.debian.org: Please add severity in a new X-Debian-PR-Severity mail header field

e severity in the same way... Example: X-Debian-PR-Message: closed 784766 X-Debian-PR-Package: libadios-dev X-Debian-PR-Keywords: sid stretch X-Debian-PR-Source: adios X-Debian-PR-Severity: serious Thank you in advance for your help! Raphaël Hertzog, tracker.debian.org maintainer.

Bug#797899: gpsd: New upstream release available: 3.15

Source: gpsd Severity: wishlist User: de...@kali.org Usertags: origin-kali Hello, There's a new upstream release available (3.15). Can you package it and coordinate its upload to unstable? (I saw that the experimental version already has a SONAME change so a library transition is required) FTR,

Bug#797783: sbuild fails without any error message when /var/lib/sbuild is not writable in the chroot

Package: sbuild Version: 0.65.2-1 Severity: normal User: de...@kali.org Usertags: origin-kali I had to reinstall a machine, but I had the possibility to keep around all the build chroots since they were stored in a separate filesystem. So I did that but the resulting system failed miserably.

Bug#797223: tracker.debian.org: Replace LDAP access to get DD names with nm.debian.org REST API

Package: tracker.debian.org Severity: wishlist Tags: newcomer distro_tracker/vendor/debian/sso_auth.py uses the ldap Python module in DebianSsoUserBackend.get_user_details() to retrieve the first name and last name of Debian developers. I would like to stop relying on LDAP (as the ldap module

Bug#796892: ftp.debian.org: Broken Sources.bz2 file for at least 3 repositories

Package: ftp.debian.org Severity: grave tracker.debian.org has been failing to import new source packages for 4 days. I have such failures during apt-get update: [...] FetchFailedException: W:Failed to fetch file:/srv/mirrors/debian/dists/jessie-backports/main/source/Sources Hash Sum mismatch

Bug#795480: impacket: New upstream release available (and watch file is broken)

Source: impacket Severity: wishlist User: de...@kali.org Usertags: origin-kali Please fix the watch file to have this: version=3 opts=uversionmangle=s/(rc|a|b|c)/~$1/ \ http://pypi.debian.net/impacket/impacket-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) You will notice that there's a

Bug#795027: jarwrapper: Does not work when installed in chroot while already active outside the chroot

Package: jarwrapper Version: 0.52 Severity: important User: de...@kali.org Usertags: origin-kali In Kali, we have a package depending on jarwrapper and which provides /usr/bin/burpsuite as an executable jar. However when it gets installed in the build chroot of our live ISO image, the postinst of

Bug#794238: how-can-i-help: provide a machine parsable output

Package: how-can-i-help Version: 11 Severity: wishlist User: de...@kali.org Usertags: origin-kali In Kali we would like to detect when Debian package that we are using are at risk (mainly for testing autoremoval for now). Thus we want to run how-can-i-help -s testing-autorm as part of a jenkins

Bug#793609: dh-python: pybuild incorrectly parses Build-Depends

Package: dh-python Version: 1.20150705-1 Severity: important I would have never expected this patch to break my package, yet it did: --- a/debian/control +++ b/debian/control @@ -8,6 +8,8 @@ Build-Depends: debhelper (= 9), dh-python, pylint (= 1.0.0), +# Enable once pylint3 is in unstable

Bug#793360: apt: APT::Never-MarkAuto-Sections not working as advertised

Package: apt Version: 1.0.9.6 Severity: normal User: de...@kali.org Usertags: origin-kali There are probably multiple problems but just to prove my case: $ apt-config dump|grep metapackages APT::Never-MarkAuto-Sections:: metapackages; APT::Never-MarkAuto-Sections:: restricted/metapackages;

Bug#793079: nvidia-graphics-drivers: New upstream release available (352.21)

Source: nvidia-graphics-drivers Severity: wishlist User: de...@kali.org Usertags: origin-kali A new upstream (long-lived) release is available since June 15: http://www.nvidia.com/object/unix.html It would be nice if it could be packaged for unstable, or at least experimental. -- System

Bug#793081: schroot: tmpfs mounted in a chroot's /dev/shm is not properly unmounted

Package: schroot Version: 1.6.10-1.1 Severity: normal User: de...@kali.org Usertags: origin-kali Consider the log below and you'll see that /dev/shm is mounted in the chroot setup but it's never umounted when the chroot is ended. That's because schroot-listmounts is not listing it. The chroot is

Bug#792695: wine: Please provide /usr/bin/wineconsole

Source: wine Severity: wishlist User: de...@kali.org Usertags: origin-kali Wine provides a wineconsole command ready to use to execute text-mode programs. It would be nice if the Debian package shipped that executable too. It's possible to use this feature already but it requires some hackery

Bug#792246: nmu: jemalloc_3.6.0-3

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu jemalloc_3.6.0-3 . powerpc . -m Rebuild to fix crash reported in #788591. gb hiredis_0.13.1-2 . powerpc dw hiredis_0.13.1-2 . powerpc . -m 'libjemalloc1 (= 3.6.0-3+b1) In #788591, Tom

Bug#791874: python-guess-language: Please add a python 2 library package

Source: python3-guess-language Version: 0.5.2-2 Severity: normal User: de...@kali.org Usertags: origin-kali Hello, New upstream version of w3af that we have in Kali (the package in Debian is currently outdated) depend on this Python module but the package uses Python 2. Can you thus provide the

Bug#791647: debtags no longer supports debtags update --local

Package: debtags Version: 2.0 Severity: important User: de...@kali.org Usertags: origin-kali In Kali, we have a kali-debtags package to provide custom tags at the appropriate place and the postinst runs debtags update --local to update the tag database. This broke recently with the arrival of

Bug#791588: texinfo: package installation fails with update-fmtutil: cannot read /etc/texmf/fmt.d/00tex.cnf

Package: texinfo Version: 6.0.0.dfsg.1-2 Severity: serious User: de...@kali.org Usertags: origin-kali The problem is that texinfo's postinst can fail this way: Setting up texinfo (6.0.0.dfsg.1-2) ... update-fmtutil: cannot read /etc/texmf/fmt.d/00tex.cnf update-fmtutil: if it was removed by

Bug#791591: pinba-engine-mysql-5.5: package is uninstallable, unsatisfiable dep on mysql-server-core-5.5 ( 5.5.43)

Package: pinba-engine-mysql-5.5 Version: 1.0.0-4 Severity: grave Justification: renders package unusable User: de...@kali.org Usertags: origin-kali The package is not installable in stretch or sid: (stretch-amd64-sbuild)root@x230-buxy:/root# apt-get install pinba-engine-mysql-5.5 Reading

Bug#789800: live-build: Extract versions from Release files

Package: live-build Version: 4.0.4-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali When live-build is used to build a distribution not listed in /usr/share/live/build/functions/releases.sh then it will fail with a cryptic error message like this one: E: Invalid operation

Bug#788843: reprepro: Cloning/duplicating/forking a distribution

Package: reprepro Version: 4.16.0-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali It would be nice if reprepro had the possibility to clone a distribution under a new codename/suite. Since this requires editing conf/distributions I would understand if you opted to only document a

Bug#788846: reprepro: Support renaming a distribution

Package: reprepro Version: 4.16.0-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali It would be nice if reprepro had a feature to rename a distribution. For example I have a kali distribution and would like to rename it to moto and use kali as suite name. I don't know of a simple

Bug#788351: reprepro: Support private/internal distributions that are never exported

Package: reprepro Version: 4.16.0-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali In Kali, we build our distribution on top of the Debian distribution. As such we have some debian-* distributions defined in conf/distributions with update rules pointing to an official Debian

Bug#788105: reprepro: Keep unreferenced files for a configurable duration (3 days per default)

Package: reprepro Version: 4.16.0-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali reprepro should make it possible to not immediatly delete files which are no longer referenced. Instead it should be able to drop them a few days after. This avoids breaking users's apt-get

Bug#784959: blhc: possible false positive about missing CPPFLAGS in a linker call

Package: blhc Version: 0.04+20140813+gitac2b8ce-1 Severity: normal For cpputest I get two reports (out of 80 calls scanned) of CPPFLAGS missing: $ blhc deb/pkg/build-area/cpputest_3.7.2-1_amd64.build CPPFLAGS missing (-D_FORTIFY_SOURCE=2): libtool: link: g++ -include

Bug#783800: security-tracker: squeeze-lts/non-free not handled correctly

Package: security-tracker Severity: important It looks like that squeeze-lts/non-free is not handled correctly. Have a look at jruby: $ rmadison jruby jruby | 1.5.1-1| oldoldstable/non-free | source, all jruby | 1.5.1-1+deb6u1 | buildd-squeeze-lts/non-free | source, all

Bug#783005: suricata: ships embedded libhtp and can conflict with a future libhtp update

Package: suricata Version: 2.0.7-2 Severity: important Looking at https://packages.debian.org/sid/amd64/suricata/filelist you will see this: /usr/lib/x86_64-linux-gnu/libhtp-0.5.17.so.1 /usr/lib/x86_64-linux-gnu/libhtp-0.5.17.so.1.0.0 But libhtp is already packaged separately. Embedded copy are

Bug#782747: gnome-shell-extensions: alternative-status-menu no longer shipped should be dropped from the default list of enabled extensions

Package: gnome-shell-extensions Version: 3.14.2-1 Severity: normal $ cat /usr/share/glib-2.0/schemas/10_gnome-shell-extensions.gschema.override [org.gnome.shell] enabled-extensions=['alternative-status-m...@gnome-shell-extensions.gcampax.github.com'] $ dpkg -L gnome-shell-extensions|grep

Bug#782493: u-a: allow to override the priorities of alternatives at a system-wide level

Package: dpkg Version: 1.17.24 Severity: wishlist User: de...@kali.org Usertags: origin-kali In the context a Debian derivative, you might want to tweak the priorities of alternatives because you make different choices about what should be the default implementation of something (my immediate

Bug#782499: RM: multiple packages in squeeze-security

Package: ftp.debian.org Severity: normal Hello, squeeze-security (on security.debian.org) contains packages which were dropped from squeeze (on main archive) because they are no longer supported. They should thus be also dropped from squeeze-security. I noticed at least: - bugzilla 3.6.2.0-4.4

Bug#781155: openbsd-inetd: openbsd-inetd.service should be the main service file

Package: openbsd-inetd Version: 0.20140418-2 Severity: serious User: de...@kali.org Usertags: origin-kali systemd doesn't seem to handle having two service files for the same service very well. For example, systemctl disable openbsd-inetd does not work since inetd.service is the unit enabled by

<    1   2   3   4   5   6   >