Bug#939960: libprelude: fails to build with gtk-doc 1.32

Source: libprelude Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated when there's no

Bug#939770: wireshark: Wrong path in pre-install notification

Control: tags -1 pending Hi Justin, On Mon, Sep 9, 2019 at 8:49 PM Justin B Rye wrote: > > Balint Reczey wrote: > > Justin B Rye wrote: > >> So instead of saying "after the package installation is finished" you > >> might change it to something like: > >> > >> For more detailed information

Bug#939959: libtasn1-6: fails to build with gtk-doc 1.32

Package: libtasn1-6 Version: 4.13-3 Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated

Bug#939898: glibc: new getegid, geteuid and getppid syscalls used unconditionally on alpha

control: retitle -1 glibc: new getegid, geteuid and getppid syscalls used unconditionally on alpha On 2019-09-10 09:27, Adhemerval Zanella wrote: > > > On 10/09/2019 07:28, John Paul Adrian Glaubitz wrote: > > On 9/10/19 11:05 AM, John Paul Adrian Glaubitz wrote: > >> Yes, we have already

Bug#939588: uim package lacks 2 files

In Message , Takatsugu Nokubi writes: > What Japanese engines do you use? I had uim-anthy and uim-mozc, and it works. I use uim-anthy. If /var/lib/uim/{installed-modules,loader}.scm are disappeared, uim-toolbar does not work properly, and I cannot switch input system to anthy. > I tried

Bug#939957: libpreludedb: fails to build with gtk-doc 1.32

Source: libpreludedb Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated when there's no

Bug#939958: librsvg: fails to build with gtk-doc 1.32

Source: librsvg Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated when there's no content

Bug#939956: liblangtag: fails to build with gtk-doc 1.32

Source: liblangtag Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated when there's no

Bug#939955: libdbusmenu: fails to build with gtk-doc 1.32

Source: libdbusmenu Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated when there's no

Bug#939954: libccss: fails to build with gtk-doc 1.32

Source: libccss Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated when there's no content

Bug#939951: keybinder-3.0: fails to build with gtk-doc 1.32

Source: keybinder-3.0 Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated when there's no

Bug#939953: kylin-burner: fails to build with gtk-doc 1.32

Source: kylin-burner Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated when there's no

Bug#939949: sleepyhead: B-D on cruft package

Source: sleepyhead Version: 1.0.0-beta-2+dfsg-6 Severity: serious Currently sleepyhead build-depends on libquazip5-headers, which is no longer built from source as its contents have been merged into libquazip5-dev, thus making sleepyhead unbuildable since these two packages are not coinstallable.

Bug#939950: hkl: fails to build with gtk-doc 1.32

Source: hkl Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated when there's no content to

Bug#939952: keybinder: fails to build with gtk-doc 1.32

Source: keybinder Severity: important Control: block 939500 by -1 Hello, Your package seems to fail to build from source with the new gtk-doc-tools 1.32 (currently in experimental). The issue seems to be that your sgml files include a file that's no longer being generated when there's no

Bug#932169: dante-server: systemd fails to start danted service

Hi, I can confirm this behavior on armhf. Removing "lib64" from the danted.service file fixes it. Lukas

Bug#939898: glibc: setuid/getuid broken on alpha with 2.29-1

On 10/09/2019 07:28, John Paul Adrian Glaubitz wrote: > On 9/10/19 11:05 AM, John Paul Adrian Glaubitz wrote: >> Yes, we have already figured out that this happens when the kernel is >> too old. According to Aurelien, the problem is that the glibc package >> has been built against the kernel

Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed

[2019-09-08 17:53] Jean-Marc LACROIX > > Please: > > > > * Try installing something else, like `tor'. I expect you will get > > similar error (`tor' depends on libsystemd0, sigh) > > ansible@pinebook:~$ sudo apt install tor > [...] Okay, tor installs fine with your apt-pinning. My

Bug#939768: gimp: Downgrading gimp to 2.10.8-2 to ensure GEGL compatibility doesn't fix bug

Package: gimp Version: 2.10.8-2 Followup-For: Bug #939768 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the

Bug#914336: netperfmeter: bogus debian/tests/control file

Hi, the problem is solved in the latest upstream version 1.8.5. I created an updated package on the mentors server: https://mentors.debian.net/package/netperfmeter . It requires a Debian sponsor to upload it. Den 22.11.2018 13:15, skrev Paul Gevers: > Source: netperfmeter > Version: 1.8.0-1 >

Bug#939947: RFS: netperfmeter/1.8.5-1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "netperfmeter": Package name: netperfmeter Version: 1.8.5-1 Upstream Author: Thomas Dreibholz URL: https://www.uni-due.de/~be0001/netperfmeter/ License: GPL-3+

Bug#939941: The solution

I found the issue: yesterday I had been trying to see if another monitor was working on this particular machine, and shut it down. The thing is: this particular monitor had precedence over all others and so, gdm was displaying the "primary" screen to this monitor. Since it was shut down, I was

Bug#939946: telepathy-logger: missing python build-dependency causes FTBFS with gtk-doc-tools 1.32

Source: telepathy-logger Severity: important Control: block 939500 by -1 Dear Maintainer, The telepathy-logger package seems to require python(2) during build, but relies on gtk-doc-tools to actually pull in python. This causes a failure to build from source when building with the new

Bug#939926: This is only on Wayland

The bug should probably be tagged for Wayland; since I switched back to Gnome on X11 the problem is gone. (As well as some other problems. This Wayland thing is not ready for prime time.)

Bug#830726: Regrabbing(was: Re: Bug#830726: xtrlock: CVE-2016-10894: xtrlock does not block multitouch events)

[adding x...@lists.x.org to CC, dropping t...@security.debian.org; please retain all CCs] Dear Xorg developers, > […] I recently became a co-maintainer for the xtrlock screen locking utility. As part of this, I noticed a bug report filed by Antoine Amarilli which points out that so-called

Bug#939945: frei0r-plugins-dev: frei0r.pc is not located correctly

Package: frei0r-plugins-dev Severity: major Dear Maintainers, frei0r-plugins-dev contains a file named frei0r.pc used by pkg-config. However the location for this file has changed since testing. In stable it was in /usr/lib/pkgconfig which seems correct but it doesn't seem to be where most .pc

Bug#939944: dput: make chown 0644 optional

Package: dput Version: 1.0.3 Severity: wishlist Dear Maintainer, Today I spent some time debugging why upload to my private server get 0644 permissions, no matter how I change permissions of built packages and no matter how I tweak umask on both sending and receiving hosts. Problem is

Bug#939939: libterm-choose-perl: testsuite failures

On Tue, 10 Sep 2019 13:08:48 +0200, Gianfranco Costamagna wrote: > Hello, since your last upload the testsuite is now failing. > https://ci.debian.net/packages/libt/libterm-choose-perl/testing/amd64 Hm, how I love failures somewhere else when it worked for me locally … >

Bug#939943: draft7 support missed, needed version 3

Package: python-jsonschema Version: 2.6.0-4 Severity: wishlist Hi, some python3 softwares uses draft7 but in actual packages version is missed, version 3.0 (latest is 3.0.2) is needed. Can you package the new version please? Thanks for any reply and sorry for my bad english.

Bug#939942: php-pecl-http; undefined symbol: uidna_IDNToASCII

Package: php-pecl-http Version: Version: 3.2.1+2.6.0-1+ubuntu16.04.1+deb.sury.org+1 After upgrading from pecl_http-3.2.0+2.6.0-1+ubuntu16.04.1+deb.sury.org+10 - > pecl_http-3.2.1+2.6.0-1+ubuntu16.04.1+deb.sury.org+1 I get an error message: php7.1: symbol lookup error:

Bug#939941: Adding details to bug #939941

Out of desperation, I went and purged everything labelled as nvidia on my system. After rebooting, and nouveau being not blacklisted anymore, I was surprised to see that I had the same issue. Indeed, nouveau was back: $ sudo lsmod | grep video video 45056 1 nouveau I guess I

Bug#852733: Cannot reproduce with 2.2.10

I can't reproduce this with the latest version, can you please test with Bluefish 2.2.10 and confirm whether this still affects you? Thanks.

Bug#939941: Adding details to bug #939941

Here is an excerpt of dmesg after a reboot ; as you can see, it does not "flood" anymore the ttys with the "NVRM: Xid ... " error but still, I got several of them when booting up. sudo dmesg | grep NVRM [3.050208] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 418.74 Wed May 1 11:49:41

Bug#700472: Upgrade of the foreign arch libc6 causes service restart

On 2019-09-09 22:18, Sven Joachim wrote: > Control: tags -1 + patch > > On 2013-02-13 06:20 +0600, Andrey Rahmatullin wrote: > > > Package: libc6 > > Version: 2.17-0experimental2 > > Severity: wishlist > > > > Filing as wishlist, maybe it's minor or even worse for some people. > > > > The

Bug#844449: Cannot reproduce

Can you please check whether this still happens for you? I have tried with version 2.2.10 and this doesn't seem to happen anymore. Thanks.

Bug#939940: libvirt-sandbox: missing python build-dependency causes FTBFS with gtk-doc-tools 1.32

Source: libvirt-sandbox Severity: important Control: block 939500 by -1 Dear Maintainer, The libvirt-sandbox package seems to require python(2) during build, but relies on gtk-doc-tools to pull in python. The new gtk-doc-tools (currently in experimental) has been ported to python3 and no

Bug#935250: , #935252: buster-pu: mutter, gnome-shell

On Wed, 21 Aug 2019 at 08:41:31 +0100, Simon McVittie wrote: > I uploaded some mutter fixes to unstable after the buster release which > I think would be worth considering for a buster update - perhaps for > 10.2 rather than 10.1 at this point. On Wed, 21 Aug 2019 at 08:44:47 +0100, Simon

Bug#939941: nvidia-driver: "display engine hung" error at boot with gdm background frozen

Package: nvidia-driver Version: 418.74-1 Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? I tried to boot up my machine and ended up having the X server frozen on the background of gdm. * What exactly did you do (or not do) that was

Bug#939939: libterm-choose-perl: testsuite failures

Source: libterm-choose-perl Version: 1.700-1 Severity: serious Hello, since your last upload the testsuite is now failing. https://ci.debian.net/packages/libt/libterm-choose-perl/testing/amd64 https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libterm-choose-perl/2922560/log.gz thanks

Bug#939938: harfbuzz: missing python build-dependency causes FTBFS with gtk-doc 1.32

Source: harfbuzz Severity: important Control: block 939500 by -1 Dear Maintainer, The harfbuzz package fails to build from source when built using gtk-doc-tools 1.32 (currently available in experimental). The problem seems to be that harfbuzz uses python(2) during build, but relies on

Bug#939898: glibc: setuid/getuid broken on alpha with 2.29-1

On 9/10/19 11:05 AM, John Paul Adrian Glaubitz wrote: Yes, we have already figured out that this happens when the kernel is too old. According to Aurelien, the problem is that the glibc package has been built against the kernel 5.3 headers which is why users need to upgrade their kernel first

Bug#939937: Remotely exploitable null pointer dereference bug

Package: libapreq2-3 Version: 2.13-5+b3 Severity: grave libapreq's multipart parser can be made dereference the null pointer by issuing a simple CURL command: curl http://a/b -F 'foo=bar;type=multipart/dummy' This POSTs a "multipart/form-data" body where one part has the Content-Type

Bug#939733: lsb-release: lsb_release does not show point release on Debian 10.1

reassign 939733 lsb-release thanks On Tue, 10 Sep 2019, Jonathan Wiltshire wrote: > This stems from lsb_release switching to reading the cross-distro > standard file, /usr/lib/os-release: Therefore it was lsb_release who changed behaviour, not base-files. > So arguably base-files should be

Bug#939935: stopped responding to play/next/previous keys; evtest and Keyboard Settings see them

Package: rhythmbox Version: 3.4.3-2 Severity: normal Dear Maintainer, I have a Debian/buster install that was a fresh install when buster was in release freeze. It is a regular GNOME install with minimal customization. The media keys all worked out-of-box. Recently, previous/play/next

Bug#939936: ITP: xtl -- basic tools (containers, algorithms) used for xtensor and xeus

Package: wnpp Severity: wishlist Owner: Vincent Bernat -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: xtl Version : 0.6.5 Upstream Author : QuantStack * URL : https://github.com/QuantStack/xtl * License : BSD Programming Lang: C++

Bug#779686: (no subject)

Hi Masayuki, Is there any news on the Namecoin Core package you submitted at https://ftp-master.debian.org/new/namecoin_0.17.0~dfsg-1.html ? I'm not familiar enough with Debian procedures to have any idea whether the lack of news since February 2019 is an indication of a problem, or if this is

Bug#939934: xserver-xorg-video-nouveau: Nouveau fails to work correctly for GeForce GT610 card with kernel 5.2.9

Package: xserver-xorg-video-nouveau Version: 1:1.0.16-1 Severity: important Dear Maintainer, Nouveau seemed to work fine with kernel 5.2.7 on GeForce GT 610 card. With the upgrade to kernel 5.2.9 I get no graphics. It seems that the GNOME session tries to start but fails. Below is all the

Bug#939933: ITP: megadock -- ultra-high-performance protein-protein docking for heterogeneous supercomputers

Package: wnpp Severity: wishlist Subject: ITP: megadock -- ultra-high-performance protein-protein docking for heterogeneous supercomputers Package: wnpp Owner: Michael R. Crusoe Severity: wishlist * Package name: megadock Version : 4.1.1 Upstream Author : Copyright: © 2014-2018

Bug#939932: varnish-modules: FTBFS after new varnish update

Source: varnish-modules Version: 0.15.0-1 Severity: serious Hello, can you please update the package to cope with new varnish APIs? the current package FTBFS in sid. Upstream PR 142 might help in the porting work https://github.com/varnish/varnish-modules/pull/142/files G.

Bug#935304: #935304: Set severity to important

reopen 935304 found 935304 243-1 severity 935304 important thanks On Tue, 2019-09-10 at 11:10 +0200, Michael Biebl wrote: > Am 10.09.19 um 11:03 schrieb Svante Signell: > > severity 935304 important > > thanks > > > > Michael: Next time you lower the importance of this bug, please give a > >

Bug#885156: ITA: daemonize -- tool to run a command as a daemon

Control: retitle -1 ITA: daemonize -- tool to run a command as a daemon Control: owner -1 Sonoma

Bug#903762: BOINC server experimental package python 2-3 transition error: Upstream is aware of it

Hi Andreas, thank you for the report. A "once worked" patch is part of https://github.com/BOINC/boinc/pull/3259. No exact idea what this is waiting for but I remain confident that it will eventually be accepted. Cheers, Steffen

Bug#939931: Upgrading mstflint package to 4.12.0-1

Package: mstflint Version: 4.11.0+1-1 Priority: wishlist >From Sept/2019 we are moving to a firmware image that is larger than 4M. This requires newer tools to be able to upgrade the firmware. Older tools will not support migration. There where bugs fixed to support this in the version

Bug#939733: lsb-release: lsb_release does not show point release on Debian 10.1

Control: reassign -1 base-files Control: severity -1 serious Control: found -1 10.3+deb10u1 Hi, On 09/09/2019 13:54, Andy Smith wrote: > Hello, > > On Sun, Sep 08, 2019 at 05:08:12PM +0200, Thorsten Glaser wrote: >> On Sun, 8 Sep 2019, Markku Leiniö wrote: >>> On Buster, "lsb_release -d" does

Bug#936045: Can not reproduce anymore ...

Am Dienstag, 10. September 2019, 01:06:16 CEST schrieben Sie: > On Sun, Sep 8, 2019 at 6:36 PM Dietz Proepper wrote: > > As in the subject - my bt headset now works with 12.99.2-1. > > Thanks for coming back to report this. You're welcome. And now for the real source of the problem. Since I

Bug#939930: -doc package should recommend the python3 package

Package: src:python-lockfile Version: 1:0.12.2-2 Tags: patch The -doc package should recommend the python3 package. patch at http://launchpadlibrarian.net/441479258/python-lockfile_1%3A0.12.2-2_1%3A0.12.2-2ubuntu1.diff.gz

Bug#936856: libfiu: Python2 removal in sid/bullseye

tags 936856 + pending thanks Hi Alberto, > Sorry for the delay, I was away traveling. No problem at all. Just uploading 1.00 now that drops Python 2.x support; thanks. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org  chris-lamb.co.uk `-

Bug#939910: arch-test.1: binfmt no longer requires an interpreter to live inside the chroot

Control: tags -1 +pending On Tue, Sep 10, 2019 at 11:05:18AM +0800, Paul Wise wrote: > Package: arch-test > Since Debian buster, qemu-user-static enabled the "fix binary" mode, > which means that interpreters no longer need to be copied or bind > mounted into chroots, which means that this

Bug#939929: terminator: crash when trying to start

Package: terminator Version: 1.91-4 Severity: important I am not able to start terminator v1.91, it crashes immediately. Downgrading to 1.90 works. Error report below, please let me know if you need any more information. Traceback (most recent call last): File "/usr/bin/terminator", line 117,

Bug#936613: ginac: Python2 removal in sid/bullseye

On 10.09.19 10:51, Richard B. Kreckel wrote: I am very sure that ginac 1.7.6 does neither build-depend, depend on Python2, or use Python2 in the autopkg tests. How was this determined? Was it found by grepping for "python2" in the extracted package? If so, grep will have found strings like

Bug#939877: closed by Josue Ortega (Bug#939877: fixed in rpcbind 1.2.5-7)

I missed the actual receive line in the 1.2.5-7 apologies. It alone DOES Not fix it though. There is breakage in libwrap to accompany it. Once the fix in 1.2.5-7 is in, rpcbind starts receiving (according to strace) messages which is followed by interrogating addresses and interfaces by

Bug#939927: mariadb-server-10.1 Cannot complete the upgrade package

Linux dev 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64 GNU/Linux 9.11

Bug#939898: glibc: setuid/getuid broken on alpha with 2.29-1

On 2019-09-09 23:16, Aurelien Jarno wrote: > On 2019-09-09 22:49, John Paul Adrian Glaubitz wrote: > > Source: glibc > > Version: 2.29-1 > > Severity: important > > User: debian-al...@lists.debian.org > > Usertags: alpha > > > > Hello! > > > > Both on my Alpha XP-1000 as well as inside a

Bug#885156: ITA: daemonize -- tool to run a command as a daemonproperties

Control: retitle -1 ITA: daemonize -- tool to run a command as a daemon Control: owner -1 Sonoma onoma...@gmail.com>

Bug#935304: #935304: Set severity to important

Am 10.09.19 um 11:03 schrieb Svante Signell: > severity 935304 important > thanks > > Michael: Next time you lower the importance of this bug, please give a > motivation. It is not especially instructive doing such a thing without > explaining why. Svante, next you respect the decision of the

Bug#939898: glibc: setuid/getuid broken on alpha with 2.29-1

Hi! On 9/10/19 10:52 AM, Michael Cree wrote: I assume this would also work on qemu-system-alpha although I haven't tried yet. But it should work the same way but without the "--foreign" argument. What kernel are you running? Be aware that recent kernels on alpha (since ecf7e0a4ad15287) now

Bug#935304: #935304: Set severity to important

severity 935304 important thanks Michael: Next time you lower the importance of this bug, please give a motivation. It is not especially instructive doing such a thing without explaining why.

Bug#939898: glibc: setuid/getuid broken on alpha with 2.29-1

On Mon, Sep 09, 2019 at 10:49:48PM +0200, John Paul Adrian Glaubitz wrote: > Shortly after typing "root" and pressing enter, the following message is > printed to the > console which seems to be an alpha-specific syscall: > > [ 195.414939] do_entUnaUser: 7 callbacks suppressed No, that is not

Bug#939898: glibc: setuid/getuid broken on alpha with 2.29-1

On Mon, Sep 09, 2019 at 11:14:50PM +0200, John Paul Adrian Glaubitz wrote: > On 9/9/19 10:49 PM, John Paul Adrian Glaubitz wrote: > > Both on my Alpha XP-1000 as well as inside a qemu-user chroot, upgrading > > glibc > > to version 2.29-1 resulted in setuid/getuid breaking in a weird way: > > To

Bug#939928: ovmf 0~20190606.20d2e5a1-4: VM does not start with UEFI BIOS

Package: ovmf Version: 0~20190606.20d2e5a1-4 Severity: grave It is not possible to start a virtual machine with UEFI BIOS. qemu-system-x86_64 -bios /usr/share/qemu/OVMF.fd The QEMU window shows: "Guest has not initialized the display (yet)." Downgrading ovmf to 0~20181115.85588389-3 solves

Bug#920263: custom AMD-server kernel-package

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am no longer trying to configure backported kernel-sources now, but in fact my build-pc has the stable (buster) distribution software-set now, there seems to be some problem about SSL, and I cannot see which option to disable in the crypto-section

Bug#939927: mariadb-server-10.1 Cannot complete the upgrade package

Package: mariadb-server-10.1 Version: 10.1.41-0+deb9u1 When I ran the command "apt-get update && apt-get upgrade" the process ended with a message: ru Настраивается пакет mariadb-server-10.1 (10.1.41-0+deb9u1) … /var/lib/dpkg/info/mariadb-server-10.1.postinst: строка 18: 25729 Завершён

Bug#939926: gnome-shell: Window screen and workspace locations forgotten when working with an external monitor

Package: gnome-shell Version: 3.30.2-9 Severity: normal Dear Maintainer, the window placement on my external screen is not remembered when I unplug and suspend my laptop. I upgraded from Debian stretch to buster. I'm using a laptop with a plain Gnome desktop. At home, I use just the laptop,

Bug#939877: closed by Josue Ortega (Bug#939877: fixed in rpcbind 1.2.5-7)

That's not it. Same story with 1.2.5-7 from unstable. This is after NIS restart on the client on the NIS server: root@jain:# tcpdump -nvvv -i enp7s0f1.502 udp and port 111 tcpdump: listening on enp7s0f1.502, link-type EN10MB (Ethernet), capture size 262144 bytes     192.168.20.41.36268 >

Bug#939925: gmime: Add a superficial test for the -dev package

Source: gmime Version: 3.2.1-1 Severity: wishlist Tags: patch I've recently been adding superficial autopkgtests for -dev packages in GNOME and GNOME-adjacent libraries. These tests check that the -dev package is usable, and in particular often detect missing -dev dependencies like #939222 in

Bug#939924: iptables-nft 1.8.2-4 check reports bad rule on "-m mark --mark 0x8000"

Package: iptables Version: 1.8.2-4 Hi, there is a bug in iptables-nft 1.8.2-4 in Debian buster: |# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster # dpkg -s iptables | grep ^Version Version: 1.8.2-4

Bug#919567: New version 3.2.3 available

Version: 3.2.3-1 On Thu, 17 Jan 2019 at 10:27:39 +0100, Sebastien Bacher wrote: > There is a new version available including some fixes, it would be nice > to get it into Debian This version is available in experimental, although not unstable yet. smcv

Bug#939834: claws-mail: Does not respond to `can_change_accels`

control: tags -1 moreinfo Hi Paul, On Mon, Sep 09, 2019 at 12:32:31PM +0100, Paul "LeoNerd" Evans wrote: > Package: claws-mail > Version: 3.17.4-1 > Severity: normal > > GTK applications ought to allow users to customise the keyboard > shortcuts ("accelerators") if enabled globally, by users

Bug#939787: RFS: assaultcube/1.2.0.2.1-3 [ITA] -- realistic first-person-shooter

Control: tags -1 moreinfo On Sun, Sep 08, 2019 at 03:50:55PM -0300, Carlos Donizete Froes wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > (...) > Changes since the last upload: > >* debian/control: (Closes: #728193) > + Added Breaks+Replaces This

Bug#939923: mono ftbfs in unstable (still calling python)

Package: src:mono Version: 5.18.0.240+dfsg-4 Severity: serious Tags: sid bullseye https://buildd.debian.org/status/package.php?p=mono Making all in mini make[2]: Entering directory '/<>/mono/mini' echo "#define FULL_VERSION \"Debian $(dpkg-parsechangelog -l../../debian/changelog | grep ^Vers |

Bug#938823: wicd and Python 3 (was: "wicd" utf8 and too many APs nightmare/bug)

Hi Alex, > I tried this one already, but bailed out, too. The other one > lookedmore promising IMHO. What worked in the end was this, though: > https://stackoverflow.com/questions/47838405/porting-a-sub-class-of-python2-file-class-to-python3 >

Bug#934099: Pending bugs

Hi, this error is locally fixed. However, since the last binNMU, the Python package does not work anymore, and this still needs to be analyzed and fixed (see Ci tests, ). Stay tuned! Cheers Ole

Bug#939845: modprobe: ERROR: could not insert 'wireguard': Exec format error

Thanks for looking into this, Daniel. On 10/09/2019 02:24, Daniel Kahn Gillmor wrote: > I note here that you're not running the latest kernel -- 4.19.0-5-amd64 > is not 4.19.0-6-amd64. is it possible that you don't have > linux-image-4.19.0-5-amd64 or its headers installed any more, despite >

Bug#939922: greenbone-security-assistant: init script inconsistency wrt DAEMON_ARGS

Package: greenbone-security-assistant Version: 7.0.3+dfsg.1-1 Severity: normal Dear Maintainer, although probably nobody is still using the init scripts ... The gsa daemon gets a few parameters via the DAEMONOPTS shell variable which is built after sourcing the default file

Bug#939921: greenbone-security-assistant: Please suggest "systemctl edit ..." instead of manually creating systemd service overrides

Package: greenbone-security-assistant Version: 7.0.3+dfsg.1-1 Severity: whishlist Dear Maintainer, For systems running systemd, the default file at /etc/default/greenbone-security-assistant contains a note about overriding the hardcoded daemon defaults, by manually creating a file at a certain

Bug#939920: openvas: Missing dependency on psmisc

Package: openvas Version: 9.0.3 Severity: normal Dear Maintainer, The openvas package ships a script /usr/bin/openvas-setup which in about line 30 calls the killall program - which isn't necessarily installed. Please consider adding an according install dependency. Regards, Christoph

Bug#939918: openvas: Please consider making rsync a dependency

Package: openvas Version: 9.0.3 Severity: normal Dear Maintainer, The openvas package ships a script /usr/bin/openvas-feed-update which uses rsync to update the local database. Currently, openvas only recommends rsync - while in my opinion there isn't much use of the package without updating

Bug#939919: openvas: Misleading package description "dummy"

Package: openvas Version: 9.0.3 Severity: minor Dear Maintainer, The short description of the openvas package | remote network security auditor - dummy package suggests it does basically nothing, besides possibly depending on other packages. Your package however does ship a few files as seen

Bug#936030: ***UNCHECKED*** Bug#936030: /usr/bin/cloud-init: cloud-init 18.3 failed to detect network link type: cascading (datasource: OpenStack)

Hello Thomas, cascading is a network type only available in OpenTelekomCloud based on Huawei Fusion. We found this problem solved in https://github.com/number5/cloud-init/commit/5352dd99eb2937b4eaaaf596b40ad7ca69d87f64 This still is not aware of network type: cascading but has a fallback.

Bug#930735: WireGuard: Add resolvconf as optional dependency

Hi dkg, > It sounds to me like there is still no great suggestion on how to make > this work smoothly, or a clear consensus on what we should do to ensure > that the DNS = directive works for wg-quick :( Correct. > > On Sat 2019-09-07 08:55:17 +0200, Willem van den Akker wrote: > > If

Bug#939904: Processed (with 1 error): Re: Bug#930735: WireGuard: Add resolvconf as optional dependency

Am 10.09.19 um 08:54 schrieb Michael Biebl: > You're right about the resolvconf.1 man page. We should not ship that in > the systemd man page since we don't ship the resolvconf symlink either systemd package... -- Why is it that all of the instruments seeking intelligent life in the universe

Bug#939917: at-spi2-core: obsolete conffiles left behind

Package: at-spi2-core Version: 2.34.0-1 Severity: normal In recent versions, two conffiles have been dropped from at-spi2-core, but they remain on the system: , | $ adequate at-spi2-core | at-spi2-core: obsolete-conffile /etc/environment.d/90qt-a11y.conf | at-spi2-core: obsolete-conffile

Bug#939904: Processed (with 1 error): Re: Bug#930735: WireGuard: Add resolvconf as optional dependency

wouldn't it be better if wireguard calls resolvctl directly? Then it knows exactly what kind of behaviour it'll get. You're right about the resolvconf.1 man page. We should not ship that in the systemd man page since we don't ship the resolvconf symlink either (for obvious reasons). Regards,

Bug#936281: Patch for Python3 [Was: Bug#936281: centrifuge: Python2 removal in sid/bullseye]

Hi, as you can read below Debian will remove Python2 support in the next release. I noticed that the issue tracker of centrifuge is switched off on github so I hope you can be reached via this e-Mail. I've crafted a patch using 2to3 to port centrifuge to Python3. You can find it in the Debian

Bug#939916: clfow: CVE-2019-16166

Source: cflow Version: 1:1.6-4 Severity: important Tags: security upstream Forwarded: https://lists.gnu.org/archive/html/bug-cflow/2019-04/msg0.html Control: found -1 1:1.6-1 Hi, The following vulnerability was published for cflow. CVE-2019-16166[0]: | GNU cflow through 1.6 has a heap-based

Bug#931950: transition: libgeotiff

libgeotiff (1.5.1-2) is in testing, but libgeotiff-dfsg (1.4.3-1) cannot be removed from testing due to gnudatalanguage, which I don't understand. But this should be resolved when the package get autoremoved on the 14th. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint:

Bug#939915: clfow: CVE-2019-16165

Source: cflow Version: 1:1.6-4 Severity: important Tags: security upstream Forwarded: https://lists.gnu.org/archive/html/bug-cflow/2019-04/msg1.html Control: found -1 1:1.6-1 Hi, The following vulnerability was published for cflow. CVE-2019-16165[0]: | GNU cflow through 1.6 has a

Bug#842292: libnss3: re-enable SSLKEYLOGFILE support

On Thu, 27 Oct 2016 21:56:32 +0300 Evgeny Kapun wrote: > Package: libnss3 > Version: 2:3.26-2 > Severity: wishlist > > In previous versions of libnss, it was possible to use SSLKEYLOGFILE environment variable to save session keys to a file. Since version 3.24, this is disabled by default at

<    1   2