Bug#951302: timeshift: /mnt is used programmatically

2020-02-13 Thread Nicholas Guriev
Package: timeshift Version: 19.01+ds-2 Severity: serious Dear maintainer, Please modify the timeshift program so that it does not use /mnt/timeshift or any sub-directories under /mnt. FHS 3.0 says no package allowed to access this directory directly. It is intended to use as a temporally mount

Bug#922582: marked as done (FTBFS against opencv 4.0.1 (exp))

2020-02-13 Thread Debian Bug Tracking System
Your message dated Fri, 14 Feb 2020 05:19:08 + with message-id and subject line Bug#922582: fixed in gmic 2.4.5-1.1 has caused the Debian Bug report #922582, regarding FTBFS against opencv 4.0.1 (exp) to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#951108: marked as done (node-opencv fails autopkg tests)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Fri, 14 Feb 2020 02:36:46 + with message-id and subject line Bug#951108: fixed in node-opencv 6.0.0+git20190322.db093cb2-7 has caused the Debian Bug report #951108, regarding node-opencv fails autopkg tests to be marked as done. This means that you claim that the problem

Bug#936806: koji: Python2 removal in sid/bullseye

2020-02-13 Thread Marek Marczykowski-Górecki
On Fri, Feb 14, 2020 at 01:30:29AM +, Holger Levsen wrote: > On Thu, Feb 13, 2020 at 08:14:11PM -0500, Sandro Tosi wrote: > > thanks! I'm gonna go ahead and file an RM bug for the following pkgs > > too: yum createrepo python-lzma yum-metadata-parser mock yum-utils > > dtc-xen deltarpm > > >

Bug#951108: marked as pending in node-opencv

2020-02-13 Thread Ying-Chun Liu
Control: tag -1 pending Hello, Bug #951108 in node-opencv reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#951108 marked as pending in node-opencv

2020-02-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #951108 [src:node-opencv] node-opencv fails autopkg tests Added tag(s) pending. -- 951108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#936806: koji: Python2 removal in sid/bullseye

2020-02-13 Thread Holger Levsen
On Thu, Feb 13, 2020 at 08:14:11PM -0500, Sandro Tosi wrote: > thanks! I'm gonna go ahead and file an RM bug for the following pkgs > too: yum createrepo python-lzma yum-metadata-parser mock yum-utils > dtc-xen deltarpm > > they are a closed set thank you for cleaning up after all of us, now

Bug#936806: koji: Python2 removal in sid/bullseye

2020-02-13 Thread Sandro Tosi
On Sat, Feb 8, 2020 at 1:51 PM Moritz Mühlenhoff wrote: > > On Thu, Jan 30, 2020 at 01:36:33AM -0500, Sandro Tosi wrote: > > > > koji is keeping createrepo in the archive, which keeps python-lzma in > > > > the archive. > > > > > > there's also mock, yum, rpm, deltarpm and yum-metadata-parser

Bug#938737: u1db: Python2 removal in sid/bullseye

2020-02-13 Thread micah anderson
Moritz Mühlenhoff writes: > On Fri, Aug 30, 2019 at 07:57:06AM +, Matthias Klose wrote: >> Package: src:u1db >> Version: 13.10-6.4 >> Severity: normal >> Tags: sid bullseye >> User: debian-pyt...@lists.debian.org >> Usertags: py2removal >> >> Python2 becomes end-of-live upstream, and Debian

Bug#951225: marked as done (schleuder: autopkgtest regression: Could not find 'sqlite3' (~> 1.4) - did find: [sqlite3-1.3.13])

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 23:21:05 + with message-id and subject line Bug#951225: fixed in schleuder 3.4.1-4 has caused the Debian Bug report #951225, regarding schleuder: autopkgtest regression: Could not find 'sqlite3' (~> 1.4) - did find: [sqlite3-1.3.13] to be marked as done.

Bug#951294: parsec47: exits with an error immediately after starting

2020-02-13 Thread Brian Vaughan
Package: parsec47 Version: 0.2.dfsg1-9 Severity: grave Justification: renders package unusable The window opens and immediately closes. From the command line: $ parsec47 parsec47: symbol lookup error: parsec47: undefined symbol:

Bug#951225: marked as pending in schleuder

2020-02-13 Thread Georg Faerber
Control: tag -1 pending Hello, Bug #951225 in schleuder reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#951225 marked as pending in schleuder

2020-02-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #951225 [src:schleuder] schleuder: autopkgtest regression: Could not find 'sqlite3' (~> 1.4) - did find: [sqlite3-1.3.13] Added tag(s) pending. -- 951225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951225 Debian Bug Tracking System

Bug#948224: pillow: CVE-2020-5310 CVE-2020-5311 CVE-2020-5312 CVE-2020-5313

2020-02-13 Thread Robert Scott
FWIW I'm fairly convinced that the first vulnerable version for CVE-2020-5310 is 6.0.0, which is the first release that included https://github.com/python-pillow/Pillow/commit/e91b851fdc1c914419543f485bdbaa010790719f which introduced the overflow when switching away from the safer TIFFTileSize

Bug#951016: marked as done (strongswan FTBFS: missing build-depends libiptc-dev)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 22:21:17 + with message-id and subject line Bug#951016: fixed in strongswan 5.8.2-2 has caused the Debian Bug report #951016, regarding strongswan FTBFS: missing build-depends libiptc-dev to be marked as done. This means that you claim that the problem has

Processed: New version uploaded

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 951115 normal Bug #951115 [src:ns3] ns3: FTBFS on mipsel (OOM of the linker) Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 951115:

Bug#951115: New version uploaded

2020-02-13 Thread Martin Quinson
severity 951115 normal thanks Hello, so I uploaded a version of this package without mipsel, and it built nicely on all architectures where its dependencies are to be found (all official architectures plus some others). Thus downgrading this bug. Thanks, Mt. signature.asc Description: PGP

Bug#938737: u1db: Python2 removal in sid/bullseye

2020-02-13 Thread Moritz Mühlenhoff
On Fri, Aug 30, 2019 at 07:57:06AM +, Matthias Klose wrote: > Package: src:u1db > Version: 13.10-6.4 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the

Bug#936521: flashproxy: Python2 removal in sid/bullseye

2020-02-13 Thread Moritz Mühlenhoff
On Fri, Aug 30, 2019 at 07:17:13AM +, Matthias Klose wrote: > Package: src:flashproxy > Version: 1.7-4 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the

Bug#950817: marked as done (archmage: FTBFS: tests fail: ModuleNotFoundError: No module named 'bs4')

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 21:34:25 + with message-id and subject line Bug#950817: fixed in archmage 1:0.4.2.1-1 has caused the Debian Bug report #950817, regarding archmage: FTBFS: tests fail: ModuleNotFoundError: No module named 'bs4' to be marked as done. This means that you

Bug#949758: marked as done (archmage: Missing build dependencies on python3-sgmllib3k and python3-chm)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 21:34:25 + with message-id and subject line Bug#949758: fixed in archmage 1:0.4.2.1-1 has caused the Debian Bug report #949758, regarding archmage: Missing build dependencies on python3-sgmllib3k and python3-chm to be marked as done. This means that you

Bug#948930: closed ... (Bug#948930: fixed in python-socksipychain 2.1.0-2)

2020-02-13 Thread Paul Gevers
Dear maintainers, On 31-01-2020 11:54, Debian Bug Tracking System wrote: > python-socksipychain (2.1.0-2) unstable; urgency=medium [...] >* Migrate an autopkgtest to Python 3 from Python 2 (Closes: #948930) > (Closes: #938184). Unfortunately the test now fails in a different way:

Processed: tagging 943077

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 943077 + pending Bug #943077 [src:fonts-lohit-deva] fonts-lohit-deva: Python2 removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 943077:

Bug#942622: Would the Games Team adopt Lightyears (pygame based, Python 3 port available)?

2020-02-13 Thread Steve Cotton
Hi all in the Games Team, One of the Debian games affected by the python3 transition is 2 Lightyears Into Space, source package name "lightyears". I've ported it to python3-pygame, and opened an upstream issue for merging it (sadly this doesn't have an upstream response yet). The Debian

Bug#949083: marked as done (krfb FTBFS: error: field 'm_clientActions' has incomplete type 'QHash')

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 19:20:43 + with message-id and subject line Bug#949083: fixed in krfb 4:19.12.2-1 has caused the Debian Bug report #949083, regarding krfb FTBFS: error: field 'm_clientActions' has incomplete type 'QHash' to be marked as done. This means that you claim

Bug#950485: marked as done (evolution-dev still depends on libenchant-dev instead of libenchant-2-dev)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 18:49:18 + with message-id and subject line Bug#950485: fixed in evolution 3.34.1-4 has caused the Debian Bug report #950485, regarding evolution-dev still depends on libenchant-dev instead of libenchant-2-dev to be marked as done. This means that you

Processed: severity of 951237 is important

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 951237 important Bug #951237 [src:glibc] glibc/mips: bpo patch: mips: Fix argument passing for inlined syscalls on Linux [BZ #25523] Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you

Processed: Bug#950485 marked as pending in evolution

2020-02-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #950485 [evolution-dev] evolution-dev still depends on libenchant-dev instead of libenchant-2-dev Added tag(s) pending. -- 950485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950485 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#950485: marked as pending in evolution

2020-02-13 Thread Laurent Bigonville
Control: tag -1 pending Hello, Bug #950485 in evolution reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#951281: FTBFS: /usr/bin/ld: cannot find -lpthreads

2020-02-13 Thread Hans Joachim Desserud
Source: widelands Version: 1:20-1 Severity: serious Justification: ftbfs Tags: ftbfs Dear Maintainer, Widelands currently fails to build in Sid with the following error message: ... /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_893c8.dir/link.txt --verbose=1 /usr/bin/cc -g -O2

Processed: [bts-link] source package gplaycli

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package gplaycli > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:shim

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:shim > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:netty

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:netty > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:buzztrax

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:buzztrax > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#950435: marked as done (haproxy build-depends on package that has been dropped.)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 16:52:47 + with message-id and subject line Bug#950435: fixed in haproxy 2.1.3-1 has caused the Debian Bug report #950435, regarding haproxy build-depends on package that has been dropped. to be marked as done. This means that you claim that the problem

Processed: RMs

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 939181 ftp.debian.org Bug #939181 [src:cycle] cycle: Python2 removal in sid/bullseye Bug reassigned from package 'src:cycle' to 'ftp.debian.org'. No longer marked as found in versions cycle/0.3.1-14 and cycle/0.3.1-15. Ignoring request

Bug#951151: polymake: test failure on mips64el

2020-02-13 Thread Benjamin Lorenz
On 13/02/2020 13.18, David Bremner wrote: > Benjamin Lorenz writes: > >> >>> It looks like it's flint related? >> >> Yes, I think this is a bug in flint and for now I suggest disabling the >> flint-interface of polymake with the configure option --without-flint on >> mips64el. This has basically

Bug#951139: Can someone please have a look (Was: Bug#951139: toil fails it's autopkg tests)

2020-02-13 Thread Andreas Tille
Hi, in case you might have missed this. Seems to be serious to me. Kind regards Andreas. On Tue, Feb 11, 2020 at 05:10:10PM +0100, Matthias Klose wrote: > Package: src:toil > Version: 3.23.1-1 > Severity: serious > Tags: sid bullseye > > seen in https://ci.debian.net/packages/t/toil >

Bug#948734: marked as done (The package should be in contrib section)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 15:00:15 + with message-id and subject line Bug#948734: fixed in cyphesis-cpp 0.7.0~snap2~exp1 has caused the Debian Bug report #948734, regarding The package should be in contrib section to be marked as done. This means that you claim that the problem has

Bug#937750: python-feedvalidator: Python2 removal in sid/bullseye

2020-02-13 Thread Boyuan Yang
X-Debbugs-CC: nsla...@tumbolia.org python-modules-t...@lists.alioth.debian.org On Fri, 30 Aug 2019 07:39:15 + Matthias Klose wrote: > Package: src:python-feedvalidator > Version: 0~svn1022-3 > > Your package either build-depends, depends on Python2, or uses Python2 > in the autopkg tests.

Bug#938608: RM svn-workbench

2020-02-13 Thread Scott Talbert
reassign -1 ftp.debian.org retitle -1 RM: svn-workbench -- RoQA; dead upstream; low popcon; blocking py2 removal

Bug#951265: ruby-vips: autopkgtest fails on arm64: expected Vips::Error but nothing was raised

2020-02-13 Thread Paul Gevers
Source: ruby-vips Version: 2.0.13-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainers, Your new package ruby-vips has an autopkgtest, great. However, it fails on arm64. I copied some of the output at the bottom of

Bug#939181: RM cycle

2020-02-13 Thread Scott Talbert
reassign -1 ftp.debian.org retitle -1 RM: cycle -- RoQA; dead upstream; unmaintained; low popcon; blocking py2 removal

Bug#906026: Switch to Ayatana Indicators

2020-02-13 Thread Mike Gabriel
Hi Andreas, thanks for following up on this. On Do 13 Feb 2020 13:11:50 CET, Andreas Henriksson wrote: Control: severity -1 serious Hello XFCE Maintainers, I'm bumping the severity of this bug report because the libindicators package in RC buggy and likely not going to make it for

Processed: block 941264 by 951258

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 941264 by 951258 Bug #941264 [php-cache-lite] phpunit breaks php-cache-lite autopkgtest: tries to write to /usr/bin/.phpunit.result.cache 941264 was not blocked by any bugs. 941264 was not blocking any bugs. Added blocking bug(s) of

Bug#951247: [Pkg-javascript-devel] Bug#951247: html2canvas: build-depends on removed package libjs-mocha

2020-02-13 Thread Ralf Treinen
On Thu, Feb 13, 2020 at 11:07:01AM +0100, Xavier wrote: > Le 13/02/2020 à 09:11, Ralf Treinen a écrit : > > Source: html2canvas > > Version: 0.5.0~beta4+ds1-2 > > Severity: serious > > User: trei...@debian.org > > Usertags: edos-uninstallable > > > > Hi, > > > > html2canvas build-depends on

Bug#951230: marked as done (linux-image-4.19.0-8-amd64: Boot Fails with LVM /usr)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 12:51:03 + with message-id and subject line Re: Bug#951230: linux-image-4.19.0-8-amd64: Boot Fails with LVM /usr has caused the Debian Bug report #951230, regarding linux-image-4.19.0-8-amd64: Boot Fails with LVM /usr to be marked as done. This means that

Bug#951151: polymake: test failure on mips64el

2020-02-13 Thread David Bremner
Benjamin Lorenz writes: > >> It looks like it's flint related? > > Yes, I think this is a bug in flint and for now I suggest disabling the > flint-interface of polymake with the configure option --without-flint on > mips64el. This has basically no functionality loss as polymake will use > its

Processed: Re: Switch to Ayatana Indicators

2020-02-13 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #906026 [lightdm-gtk-greeter] Switch to Ayatana Indicators Severity set to 'serious' from 'wishlist' -- 906026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#949303 marked as pending in vinagre

2020-02-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #949303 {Done: Debian FTP Masters } [src:vinagre] vinagre: FTBFS: appstream validation fails Added tag(s) pending. -- 949303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949303 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#951102: marked as done (iptables-restore empty line not accepted any more (regression))

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 11:49:08 + with message-id and subject line Bug#951102: fixed in iptables 1.8.4-3 has caused the Debian Bug report #951102, regarding iptables-restore empty line not accepted any more (regression) to be marked as done. This means that you claim that the

Bug#949518: marked as done (ufw: does not work with iptables-restore 1.8.4-2 (blank line in file))

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 11:49:08 + with message-id and subject line Bug#949518: fixed in iptables 1.8.4-3 has caused the Debian Bug report #949518, regarding ufw: does not work with iptables-restore 1.8.4-2 (blank line in file) to be marked as done. This means that you claim that

Bug#949303: marked as pending in vinagre

2020-02-13 Thread Andreas Henriksson
Control: tag -1 pending Hello, Bug #949303 in vinagre reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#933054: marked as done (gnome-disks: segfault error 4 in libgobject-2.0.so.0.5800.3)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 12:41:27 +0100 with message-id <20200213114127.v43wrdysa6466...@fatal.se> and subject line no feedback -> closing has caused the Debian Bug report #933054, regarding gnome-disks: segfault error 4 in libgobject-2.0.so.0.5800.3 to be marked as done. This means

Bug#826560: node-carto: Current version is old and incompatible with recent versions of mapnik

2020-02-13 Thread Manfred Stock
Package: node-carto Followup-For: Bug #826560 Hi, since I needed this at $WORK and am also personally interested in this as an OSM contributor and Debian user, I took a closer look at the current state. It basically seems to require work on three packages: * node-chroma-js [1,2]: The WIP

Bug#950062: marked as done (python-babel FTBFS: fixture 'locale' not found)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 10:39:16 + with message-id and subject line Bug#950062: fixed in python-babel 2.8.0+dfsg.1-1 has caused the Debian Bug report #950062, regarding python-babel FTBFS: fixture 'locale' not found to be marked as done. This means that you claim that the problem

Bug#951247: [Pkg-javascript-devel] Bug#951247: html2canvas: build-depends on removed package libjs-mocha

2020-02-13 Thread Xavier
Le 13/02/2020 à 09:11, Ralf Treinen a écrit : > Source: html2canvas > Version: 0.5.0~beta4+ds1-2 > Severity: serious > User: trei...@debian.org > Usertags: edos-uninstallable > > Hi, > > html2canvas build-depends on libjs-mocha which only exists in > old{old}stable. > > -Ralf. Hi,

Bug#949083: krfb FTBFS fixed upstream?

2020-02-13 Thread Aurélien COUDERC
Le 13 février 2020 03:57:06 GMT+01:00, Debian Bug Tracking System a écrit : >Processing commands for cont...@bugs.debian.org: > >> forwarded 949083 https://phabricator.kde.org/D23059 >Bug #949083 [src:krfb] krfb FTBFS: error: field 'm_clientActions' has >incomplete type 'QHash' >Set Bug

Bug#950535: [pkg-netfilter-team] Bug#950535: iptables-restore segfaults on nat table

2020-02-13 Thread Alberto Molina Coballes
On Thu, Feb 13, 2020 at 11:05:13AM +0100, Christoph Martin wrote: > > I choose the grave severity because the bug makes a reload of ufw fail > and then the firewall is off ! > Yes, I agree with you that it's a serious situation, but we have to determine if it's a general case of iptables (which

Bug#951249: marked as done (panicparse: FTBFS on arch:all)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 10:15:42 + with message-id and subject line Bug#951249: fixed in panicparse 1.3.0-3 has caused the Debian Bug report #951249, regarding panicparse: FTBFS on arch:all to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#950535: [pkg-netfilter-team] Bug#950535: iptables-restore segfaults on nat table

2020-02-13 Thread Christoph Martin
Hi Alberto, Am 13.02.20 um 10:11 schrieb Alberto Molina Coballes: > I don't understand the rule "-F PREROUTING" after a "-A ..." one. It > seems that the segfault happens in this specific case (it's a bug of > course, but not a bug with grave severity). I choose the grave severity because the

Bug#950535: [pkg-netfilter-team] Bug#950535: iptables-restore segfaults on nat table

2020-02-13 Thread Christoph Martin
Hil Alberto, Am 13.02.20 um 10:11 schrieb Alberto Molina Coballes: > > Is this ruleset a real one obtained from ufw? I ask because the next one > doesn't result in segfault: > > *nat > -F PREROUTING > -F POSTROUTING > -A PREROUTING -i eth0 -p tcp --dport 22 -j REDIRECT --to-ports 1194 > COMMIT

Processed: moreinfo

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 933054 + moreinfo Bug #933054 [gnome-disk-utility] gnome-disks: segfault error 4 in libgobject-2.0.so.0.5800.3 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 933054:

Bug#948780: yelp: FTBFS: Validation of files failed

2020-02-13 Thread Andreas Henriksson
Hi, A possible workaround for yelp FTBFS could be to add the --disable-appstream-util configure flag. This disables the validation and hopefully the parser is more relaxed during runtime and properly handles the missing field (as they where not required in the past). (Ofcourse a proper fix of

Bug#951249: marked as pending in panicparse

2020-02-13 Thread Shengjing Zhu
Control: tag -1 pending Hello, Bug #951249 in panicparse reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#951249 marked as pending in panicparse

2020-02-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #951249 [src:panicparse] panicparse: FTBFS on arch:all Added tag(s) pending. -- 951249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#951249: panicparse: FTBFS on arch:all

2020-02-13 Thread Paul Gevers
Hi Shengjing, On 13-02-2020 10:34, Shengjing Zhu wrote: > I probably don't understand what happens. I may not have been the best in describing the situation. > The package to be tested is src:panicparse, and it builds > bin:golang-github-maruel-panicparse-dev and bin:panicparse. The latest

Bug#951249: panicparse: FTBFS on arch:all

2020-02-13 Thread Shengjing Zhu
On Thu, Feb 13, 2020 at 4:33 PM Paul Gevers wrote: > > Source: panicparse > Version: 1.3.0-2 > X-Debbugs-CC: debian...@lists.debian.org > Severity: serious > Tags: ftbfs > User: debian...@lists.debian.org > Usertags: always-fails > > Dear maintainers, > > Your new package panicparse has an

Processed: notfixed 950535 in 1.8.3-2

2020-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 950535 1.8.3-2 Bug #950535 [iptables] iptables-restore segfaults on nat table No longer marked as fixed in versions iptables/1.8.3-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 950535:

Bug#951222: scikit-learn breaks python-skbio autopkgtest: skbio.stats.distance._permdisp.permdisp

2020-02-13 Thread Paul Gevers
Hi Andreas, On 13-02-2020 09:31, Andreas Tille wrote: > My observation is that responses to bug reports of scikit-bio github are > not to be expected in a short time frame. Please be aware that if the issue is really with python-skbio, than the way autoremovals work with these kind of bugs

Processed: Re: [pkg-netfilter-team] Bug#950535: iptables-restore segfaults on nat table

2020-02-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #950535 [iptables] iptables-restore segfaults on nat table Added tag(s) moreinfo. -- 950535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#950535: [pkg-netfilter-team] Bug#950535: iptables-restore segfaults on nat table

2020-02-13 Thread Alberto Molina Coballes
Control: tag -1 moreinfo Hi Christoph, Is this ruleset a real one obtained from ufw? I ask because the next one doesn't result in segfault: *nat -F PREROUTING -F POSTROUTING -A PREROUTING -i eth0 -p tcp --dport 22 -j REDIRECT --to-ports 1194 COMMIT I don't understand the rule "-F PREROUTING"

Bug#882919: marked as done (php-text-password FTBFS with phpunit 6.4.4-2)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 09:04:32 + with message-id and subject line Bug#882919: fixed in php-text-password 1.2.1-3 has caused the Debian Bug report #882919, regarding php-text-password FTBFS with phpunit 6.4.4-2 to be marked as done. This means that you claim that the problem has

Bug#950715: marked as done (libgcc1: upgrade from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc with gold linker)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 08:52:00 + with message-id <20200213085200.ga401...@espresso.pseudorandom.co.uk> and subject line Re: Bug#950715: libgcc1: upgrade from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc with gold linker has caused the Debian Bug report #950715, regarding

Bug#950545: marked as done (FTBFS against opencv 4.2.0)

2020-02-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Feb 2020 08:42:21 + with message-id and subject line Bug#950545: fixed in eviacam 2.1.4-2 has caused the Debian Bug report #950545, regarding FTBFS against opencv 4.2.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#951249: panicparse: FTBFS on arch:all

2020-02-13 Thread Paul Gevers
Source: panicparse Version: 1.3.0-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious Tags: ftbfs User: debian...@lists.debian.org Usertags: always-fails Dear maintainers, Your new package panicparse has an autopkgtest, great. However, it fails because your package fails to build from

Processed: Re: Bug#951222: scikit-learn breaks python-skbio autopkgtest: skbio.stats.distance._permdisp.permdisp

2020-02-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #951222 [src:scikit-learn, src:python-skbio] scikit-learn breaks python-skbio autopkgtest: skbio.stats.distance._permdisp.permdisp Added tag(s) upstream. > forwarded -1 https://github.com/biocore/scikit-bio/issues/1693 Bug #951222

Bug#951222: scikit-learn breaks python-skbio autopkgtest: skbio.stats.distance._permdisp.permdisp

2020-02-13 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 https://github.com/biocore/scikit-bio/issues/1693 > Due to the nature of this issue, I filed this bug report > against both packages. Can you please investigate the situation and > reassign the bug to the right package? I admit I'm not sure what

Bug#951248: origami-pdf: autopkgtest failure: output to stderr: warning: constant ::Bignum is deprecated

2020-02-13 Thread Paul Gevers
Source: origami-pdf Version: 2.0.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: always-fails Dear maintainers, Your package was removed some time ago due to bug 914333, which by now is fixed by src:netperfmeter. However, you package

Bug#951247: html2canvas: build-depends on removed package libjs-mocha

2020-02-13 Thread Ralf Treinen
Source: html2canvas Version: 0.5.0~beta4+ds1-2 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, html2canvas build-depends on libjs-mocha which only exists in old{old}stable. -Ralf.

Bug#951246: genetic: build-depends on non-existing package

2020-02-13 Thread Ralf Treinen
Source: genetic Version: 0.1.1b+git20170527.98255cb-1 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, genetic build-depends on python3-multiprocess, which does not exist in the archive. -Ralf.

Processed: kazoo: autopkgtest regression

2020-02-13 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #933631 [src:kazoo] kazoo: autopkgtest regression Severity set to 'serious' from 'important' -- 933631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems