Processed: statsmodels FTBFS: array |= frame now returns frame

2019-03-03 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:statsmodels Bug #923707 [src:pandas] statsmodels FTBFS: array |= frame now returns frame Added indication that 923707 affects src:statsmodels > tags -1 patch Bug #923707 [src:pandas] statsmodels FTBFS: array |= frame now returns frame Added tag(s)

Bug#923707: statsmodels FTBFS: array |= frame now returns frame

2019-03-03 Thread Rebecca N. Palmer
Source: pandas Version: 0.23+dfsg-2 Severity: serious Control: affects -1 src:statsmodels Control: tags -1 patch The fix for #918206 (setting __array_priority__ to make np.array @ DataFrame work) is technically API breaking: in-place operators arr = np.array(...) df = pd.DataFrame(...) arr +=

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

2019-03-03 Thread Pirate Praveen
On 2019, മാർച്ച് 3 10:45:19 PM IST, Justin Hallett wrote: >Well I hope it comes to that personally, cause I think you have been >doing a great job, it’s a TON of work to maintain all the depends you >do for gitlab and honestly there are rarely issues and when they are >you fix them very

Bug#914794: libmspack fails tests on big endian architectures (s390x, mips)

2019-03-03 Thread duck
Quack, On 2019-03-04 10:40, Stuart Caie wrote: I've released libmspack 0.10 and cabextract 1.9.1. They contain only fixes. Thanks a lot for being so fast. Unfortunately there is a build problem: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./mspack -I./test -Wdate-time -D_FORTIFY_SOURCE=2

Bug#914794: libmspack fails tests on big endian architectures (s390x, mips)

2019-03-03 Thread Stuart Caie
On 03/03/2019 04:47, Marc Dequènes (duck) wrote: Quack, On 2018-12-04 19:02, Stuart Caie wrote: This is fixed in the repository, it just hasn't been released. I'll release it in the near future. I was myself busy and we missed the Debian freeze deadline. Maybe there is still some hope

Processed: tagging 877122

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 877122 + stretch Bug #877122 [libengine-pkcs11-openssl1.1] libengine-pkcs11-openssl1.1: Engine is installed into wrong directory on i386 Added tag(s) stretch. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: fixed 877122 in 0.4.9-4

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 877122 0.4.9-4 Bug #877122 [libengine-pkcs11-openssl1.1] libengine-pkcs11-openssl1.1: Engine is installed into wrong directory on i386 Marked as fixed in versions libp11/0.4.9-4. > thanks Stopping processing here. Please contact me if you

Bug#923695: marked as done (libczmq-dev: pkg-config --cflags libczmq.pc fails without uuid-dev and libsystemd-dev installed)

2019-03-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Mar 2019 22:52:02 + with message-id and subject line Bug#923695: fixed in czmq 4.2.0-2 has caused the Debian Bug report #923695, regarding libczmq-dev: pkg-config --cflags libczmq.pc fails without uuid-dev and libsystemd-dev installed to be marked as done. This

Processed: severity of 923606 is important

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 923606 important Bug #923606 [src:beancount] beancount: FTBFS randomly (gpg-related race condition) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 923606:

Bug#923606: beancount: FTBFS randomly (gpg-related race condition)

2019-03-03 Thread Stefano Zacchiroli
severity -1 important thanks Hi Santiago, On Sat, Mar 02, 2019 at 06:03:10PM +, Santiago Vila wrote: > I tried to build this package in buster but it failed: > [...] > try: > > os.unlink(entry.name, dir_fd=topfd) > E FileNotFoundError:

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

2019-03-03 Thread Philip Hands
Didier 'OdyX' Raboud writes: > Dear Technical Committee members, > > I call for vote immediately on the following resolution. > > === Resolution === > > The Technical Committee resolves to decline to override the debootstrap > maintainers. > > Furthermore, using its §6.1.5 "Offering advice"

Bug#923695: libczmq-dev: pkg-config --cflags libczmq.pc fails without uuid-dev and libsystemd-dev installed

2019-03-03 Thread Luca Boccassi
Package: libczmq-dev Version: 4.2.0-1 Severity: grave Justification: rdeps FTBFS due to missing dependencies and pkg-config libczmq.pc lists the dependencies for static linking in Requires.private, which means pkg-config --cflags libczmq will fail if these dependencies (uuid-dev and

Processed: fix versions for 893244

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # BTS thinks this bug is found and fixed in 9.1.17.0-1, which confuses version > # tracking. Adjusting versions... > notfixed 893244 9.1.17.0-1 Bug #893244 {Done: Markus Koschany } [src:jruby] jruby FTBFS with openjdk-9 No longer marked as fixed

Bug#923686: kubernetes: CVE-2019-1002100: kube-apiserver: DoS with crafted patch of type json-patch

2019-03-03 Thread Salvatore Bonaccorso
Source: kubernetes Version: 1.7.16+dfsg-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/kubernetes/kubernetes/issues/74534 Hi, The following vulnerability was published for kubernetes. CVE-2019-1002100[0]: kube-apiserver: DoS with

Bug#921266: Same crash with linphone 4.1.1 (flatpak)

2019-03-03 Thread Alf
I just tried to setup linphone in Buster by installing flatpak and the latest version of linphone 4.1.1. Installation went smooth and it starts without any configuration (alltogether roughly ½ GB of disk space). However trying to configure my SIP-account results in the same (or very similar)

Bug#920042: lua-nvim: autopkgtest times out since 2019-01-10

2019-03-03 Thread Paul Gevers
Hi James, On 03-03-2019 18:41, James McCoy wrote: > It actually was caused by a test dependency (via @builddeps@) -- neovim. > I don't see a migration check that ran lua-nvim's tests as part of > neovim's migration. The migration software doesn't process @builddeps@ yet as that is a recent

Bug#920042: lua-nvim: autopkgtest times out since 2019-01-10

2019-03-03 Thread James McCoy
On Mon, Jan 21, 2019 at 09:17:00PM +0100, Paul Gevers wrote: > Since 2019-01-10 the autopkgtest of your package times out (after 2:47h) > on ci.debian.net. Unfortunately, this most likely isn't caused by any of > your direct (test) dependencies, otherwise the integration with our > migration

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

2019-03-03 Thread Justin Hallett
Well I hope it comes to that personally, cause I think you have been doing a great job, it’s a TON of work to maintain all the depends you do for gitlab and honestly there are rarely issues and when they are you fix them very quickly after a report. It’s very upsetting that I now have 10

Bug#923674: systemd: FTBFS (failing tests)

2019-03-03 Thread Santiago Vila
Package: src:systemd Version: 240-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules binary-arch dh binary-arch --without autoreconf,systemd

Bug#900299: marked as done (leiningen-clojure: depends on openjdk-8)

2019-03-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Mar 2019 15:34:41 + with message-id and subject line Bug#900299: fixed in leiningen-clojure 2.9.0-1 has caused the Debian Bug report #900299, regarding leiningen-clojure: depends on openjdk-8 to be marked as done. This means that you claim that the problem has been

Bug#923164: marked as done (leiningen-clojure: FTBFS (Could not resolve dependencies for project leiningen-core:leiningen-core:jar:2.8.1))

2019-03-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Mar 2019 15:34:41 + with message-id and subject line Bug#923164: fixed in leiningen-clojure 2.9.0-1 has caused the Debian Bug report #923164, regarding leiningen-clojure: FTBFS (Could not resolve dependencies for project leiningen-core:leiningen-core:jar:2.8.1) to

Bug#919638: marked as done (solr-tomcat: Permission problems after update to tomcat9)

2019-03-03 Thread Debian Bug Tracking System
Your message dated Sun, 03 Mar 2019 16:05:04 + with message-id and subject line Bug#919638: fixed in lucene-solr 3.6.2+dfsg-18 has caused the Debian Bug report #919638, regarding solr-tomcat: Permission problems after update to tomcat9 to be marked as done. This means that you claim that the

Processed: Bug #919638 in lucene-solr marked as pending

2019-03-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #919638 [solr-tomcat] solr-tomcat: Permission problems after update to tomcat9 Ignoring request to alter tags of bug #919638 to the same tags previously set -- 919638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919638 Debian Bug Tracking

Bug#919638: Bug #919638 in lucene-solr marked as pending

2019-03-03 Thread Markus Koschany
Control: tag -1 pending Hello, Bug #919638 in lucene-solr 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: Re: solr-tomcat: Permission problems after update to tomcat9

2019-03-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #919638 [src:tomcat9] solr-tomcat: Permission problems after update to tomcat9 Severity set to 'serious' from 'important' > reassign -1 solr-tomcat Bug #919638 [src:tomcat9] solr-tomcat: Permission problems after update to tomcat9 Bug

Bug#853016: No such release notes

2019-03-03 Thread 積丹尼 Dan Jacobson
Well, a fix would be to take the cautions route of: If pidof nodm is found, that means they currently running it, so abandon all attempts to restart it. If the user is so smart that they want to restart it, they can do it themselves. (Equivalent of them rebooting the system themselves.)

Bug#853016: No such release notes

2019-03-03 Thread Mike Gabriel
Hi Dan, On Sunday, 3 March 2019, 積丹尼 Dan Jacobson wrote: > P.S., there are no such "release notes", > $ dlocate --filename-only -L nodm|xargs grep -ic 'not upgrade' 2>&- > and even if there were... > don't you think it is silly if one cannot upgrade a package when using > the package lest

Processed: mariadb breaks libdbd-mysql-perl

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # oops > affects 923541 - mariadb-10.3 Bug #923541 [src:libdbd-mysql-perl] libdbd-mysql-perl: FTBFS against mariadb-10.3 1:10.3.13-1 Removed indication that 923541 affects mariadb-10.3 > affects 923541 src:mariadb-10.3 Bug #923541

Processed: mariadb breaks libdbd-mysql-perl

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 923541 mariadb-10.3 Bug #923541 [src:libdbd-mysql-perl] libdbd-mysql-perl: FTBFS against mariadb-10.3 1:10.3.13-1 Added indication that 923541 affects mariadb-10.3 > thanks Stopping processing here. Please contact me if you need

Bug#913165: CVE-2018-7727 CVE-2018-7726 CVE-2018-7725

2019-03-03 Thread Salvatore Bonaccorso
Control: retitle -1 zziplib: CVE-2018-7726 CVE-2018-7725 Hi, On Wed, Nov 07, 2018 at 07:51:10PM +0100, Moritz Muehlenhoff wrote: > Source: zziplib > Severity: important > Tags: security > > Please see > https://security-tracker.debian.org/tracker/CVE-2018-7727 >

Processed: Re: Bug#913165: CVE-2018-7727 CVE-2018-7726 CVE-2018-7725

2019-03-03 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 zziplib: CVE-2018-7726 CVE-2018-7725 Bug #913165 [src:zziplib] CVE-2018-7727 CVE-2018-7726 CVE-2018-7725 Changed Bug title to 'zziplib: CVE-2018-7726 CVE-2018-7725' from 'CVE-2018-7727 CVE-2018-7726 CVE-2018-7725'. -- 913165:

Processed: severity of 909309 is important

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 909309 important Bug #909309 [clipit] clipit: Unable to access history using hotkeys and crash Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 909309:

Processed: Re: Bug#903149: ClipIt crashes with segmentation fault on start

2019-03-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #903149 [clipit] ClipIt crashes with segmentation fault on start Severity set to 'important' from 'serious' -- 903149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903149 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#903149: ClipIt crashes with segmentation fault on start

2019-03-03 Thread Andrej Shadura
Control: severity -1 important On Sun, 8 Jul 2018 00:10:38 +0200 (CEST) Calle Kabo wrote: > Alright, I installed 1.4.4-2 from unstable, and it still crashes. > Here's the gdb output > > (gdb) bt > #0  0x76514339 in XGetModifierMapping () at > /usr/lib/x86_64-linux-gnu/libX11.so.6 > #1 

Bug#853016: No such release notes

2019-03-03 Thread 積丹尼 Dan Jacobson
P.S., there are no such "release notes", $ dlocate --filename-only -L nodm|xargs grep -ic 'not upgrade' 2>&- and even if there were... don't you think it is silly if one cannot upgrade a package when using the package lest disaster. Does upgrading the kernel trigger reboot?

Bug#923654: libowasp-java-html-sanitizer-java-doc: Depends on libjsr305-java-doc which is no longer built in sid/buster

2019-03-03 Thread Niels Thykier
Package: libowasp-java-html-sanitizer-java-doc Version: 0.1+r88-1 Severity: serious Hi, The libowasp-java-html-sanitizer-java-doc package is depending on libjsr305-java-doc in sid + buster, however libjsr305-java-doc is no longer buit. Please remove the dependency for buster. Thanks, ~Niels

Processed: retitle 853016 to restarting upon upgrade even kills APT, throws away all users' work

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 853016 restarting upon upgrade even kills APT, throws away all users' > work Bug #853016 [nodm] warn user all his work will be lost Bug #919980 [nodm] Ask before upgrading so user doesn't lose data Changed Bug title to 'restarting upon

Processed: Even ruins apt upgrade for all packages

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 853016 critical Bug #853016 [nodm] warn user all his work will be lost Bug #919980 [nodm] Ask before upgrading so user doesn't lose data Severity set to 'critical' from 'important' Severity set to 'critical' from 'important' > thanks

Processed: Re: python-hbmqtt FTBFS with Python 3.7

2019-03-03 Thread Debian Bug Tracking System
Processing control commands: > tags 911861 + fixed-upstream Bug #911861 [src:python-hbmqtt] python-hbmqtt FTBFS with Python 3.7 Added tag(s) fixed-upstream. -- 911861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#911861: python-hbmqtt FTBFS with Python 3.7

2019-03-03 Thread Stein Magnus Jodal
Control: tags 911861 + fixed-upstream The FTBFS on Python 3.7 has been fixed upstream since 0.9.3, ref. https://github.com/beerfactory/hbmqtt/commit/31888f8e691b0c51d61fc1a201ff99daa7a0eb8e Before packaging the latest release, I'd like upstream to fix

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

2019-03-03 Thread Pirate Praveen
On Mon, 25 Feb 2019 07:45:36 -0700 Justin Hallett wrote: > This ticket is bogus and should be closed and removed so that gitlab can be > fixed in testing and restore the faith of its users. I think we have not received the same level of respect from the rest of the project. Since everyone is

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

2019-03-03 Thread Margarita Manterola
> === Resolution === > > The Technical Committee resolves to decline to override the debootstrap > maintainers. > > Furthermore, using its §6.1.5 "Offering advice" power, the Technical > Committee considers that the desirable solution at the time of `bullseye` is: > > * W: `weak`: both

Bug#887880: boinc-app-eah-brp: non-standard gcc/g++ used for build (gcc-5)

2019-03-03 Thread Ralf Treinen
The build-dependency g++-5|g++ (<< 6) is not satisfiable in sid now. -Ralf

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

2019-03-03 Thread Pirate Praveen
On Mon, 25 Feb 2019 07:45:36 -0700 Justin Hallett wrote: > By keeping this out of testing you are really leaving those of us running it > and depending on it in a real mess. To get rails 2.5 support I had to do > some serious Debian badness, this really sucks, couldn’t it just be kept out >

Processed: Re: lua-nvim: autopkgtest times out since 2019-01-10

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 920042 ftbfs Bug #920042 [src:lua-nvim] lua-nvim: autopkgtest times out since 2019-01-10 Added tag(s) ftbfs. > tags 923448 ftbfs Bug #923448 {Done: Peter Pentchev } [src:stunnel4] stunnel4: autopkgtest fails with new version of openssl:

Processed: fix ftbfs bug metadata

2019-03-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # affects both binary and source > reassign 876608 src:ruby-compass 1.0.3~dfsg-5 Bug #876608 [ruby-compass] ruby-compass (build) depends on ruby-sass (< 3.5), but 3.5.1-2 is in unstable Bug reassigned from package 'ruby-compass' to