Bug#913144: marked as done (android-platform-system-core: FTBFS when built with dpkg-buildpackage -A)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Thu, 15 Nov 2018 07:33:58 + with message-id and subject line Bug#913144: fixed in android-platform-system-core 1:8.1.0+r23-3 has caused the Debian Bug report #913144, regarding android-platform-system-core: FTBFS when built with dpkg-buildpackage -A to be marked as done.

Processed: The upload of scilab 6.0.1-6 has fixed the problem

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # This problem is also fixed in the last upload. > fixed #913630 6.0.1-6 Bug #913630 [scilab] scilab: Raise java.lang.module.FindException on start Marked as fixed in versions scilab/6.0.1-6. > thanks Stopping processing here. Please contact me

Bug#913552: marked as done (firehol: wrong mktemp path if built on a merged-/usr system and used on an unmerged-/usr system)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Thu, 15 Nov 2018 06:49:01 + with message-id and subject line Bug#913552: fixed in firehol 3.1.6+ds-6 has caused the Debian Bug report #913552, regarding firehol: wrong mktemp path if built on a merged-/usr system and used on an unmerged-/usr system to be marked as done.

Bug#913408: marked as done (librust-crossbeam-epoch-0.5-dev: missing Breaks+Replaces: librust-crossbeam-epoch-dev (<< 0.6))

2018-11-14 Thread Debian Bug Tracking System
Your message dated Thu, 15 Nov 2018 05:49:14 + with message-id and subject line Bug#913408: fixed in rust-crossbeam-epoch-0.5 0.5.2-2 has caused the Debian Bug report #913408, regarding librust-crossbeam-epoch-0.5-dev: missing Breaks+Replaces: librust-crossbeam-epoch-dev (<< 0.6) to be

Bug#899690: marked as done (scim-pinyin: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Thu, 15 Nov 2018 04:49:38 + with message-id and subject line Bug#899690: fixed in scim-pinyin 0.5.92-4 has caused the Debian Bug report #899690, regarding scim-pinyin: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org to be marked as done. This means that

Processed: Re: Processed: Re: Bug#913753: FTBFS: test-suite fails with ERROR: Rust compiler rustc can not compile programs.

2018-11-14 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 llvm-7 Bug #913753 [rustc] FTBFS: test-suite fails with ERROR: Rust compiler rustc can not compile programs. Bug reassigned from package 'rustc' to 'llvm-7'. Ignoring request to alter found versions of bug #913753 to the same values previously set

Bug#913753: Processed: Re: Bug#913753: FTBFS: test-suite fails with ERROR: Rust compiler rustc can not compile programs.

2018-11-14 Thread Ximin Luo
Control: reassign -1 llvm-7 Control: forcemerge 913271 -1 Control: affects 913271 + src:meson src:rustc Debian Bug Tracking System: > Processing commands for cont...@bugs.debian.org: > >> reassign 913753 rustc > Bug #913753 [src:meson] FTBFS: test-suite fails with ERROR: Rust compiler > rustc

Bug#913771: marked as done (syncthing-gtk: unsatisfiable dependency on non-existent gir-1.2-glib-2.0)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Thu, 15 Nov 2018 02:40:25 + with message-id and subject line Bug#913771: fixed in syncthing-gtk 0.9.4.2-2 has caused the Debian Bug report #913771, regarding syncthing-gtk: unsatisfiable dependency on non-existent gir-1.2-glib-2.0 to be marked as done. This means that you

Bug#913776: mozjs60: FTBFS with icu63; upstream cherry-pick attached

2018-11-14 Thread Adam Conrad
Package: mozjs60 Version: 60.2.3-1 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch In Ubuntu, the attached patch was applied to achieve the following: *

Bug#913036: marked as done (dulwich fails to build everywhere)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Thu, 15 Nov 2018 02:16:17 + with message-id <20181115021617.GA23136@blodeuwedd> and subject line Fixed in 0.19.8-1 has caused the Debian Bug report #913036, regarding dulwich fails to build everywhere to be marked as done. This means that you claim that the problem has been

Processed: fixed 913036 in 0.19.8-1

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 913036 0.19.8-1 Bug #913036 [src:dulwich] dulwich fails to build everywhere Marked as fixed in versions dulwich/0.19.8-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 913036:

Bug#913775: php-imap: imap_open() function command injection

2018-11-14 Thread rhns
Package: php-imap Version: 1:7.0+49 Severity: grave Tags: security Justification: user security hole Dear Maintainer, A command injection vulnerability has been identified in the imap extension of php. It is located in the imap_open() function which does not validate correctly the server URI.

Bug#913771: syncthing-gtk: unsatisfiable dependency on non-existent gir-1.2-glib-2.0

2018-11-14 Thread Jelmer Vernooij
Hi Steve, On Wed, Nov 14, 2018 at 03:16:32PM -0800, Steve Langasek wrote: > The syncthing-gtk package is uninstallable, because it depends on > gir-1.2-glib-2.0, which does not exist. The correct spelling of this > package name is gir1.2-glib-2.0. Please find a patch attached. Argh, that was

Bug#874727: OSG changing VRML renderer away from coin3

2018-11-14 Thread Manuel A. Fernandez Montecelo
Em seg, 5 de nov de 2018 às 07:10, Sebastiaan Couwenberg escreveu: > On 11/5/18 12:45 AM, Manuel A. Fernandez Montecelo wrote: > > 2018-11-04 18:28 Christoph Berg: > >> > >> | Patches for both OSG packages have been submitted to use SGI Inventor > >> | instead of COIN: > >> | > >> |

Bug#913771: syncthing-gtk: unsatisfiable dependency on non-existent gir-1.2-glib-2.0

2018-11-14 Thread Steve Langasek
Package: syncthing-gtk Version: 0.9.4.2-1 Severity: grave Tags: patch Justification: uninstallable User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch Hi Jelmer, The syncthing-gtk package is uninstallable, because it depends on gir-1.2-glib-2.0, which does not exist.

Bug#901516: marked as done (sbt-serialization: FTBFS with openjdk-10: NumberFormatException: For input string: "0x100")

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 22:49:52 + with message-id and subject line Bug#901516: fixed in sbt-serialization 0.1.2+repack-1 has caused the Debian Bug report #901516, regarding sbt-serialization: FTBFS with openjdk-10: NumberFormatException: For input string: "0x100" to be marked as

Processed: Bug #901516 in sbt-serialization marked as pending

2018-11-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #901516 [sbt-serialization] sbt-serialization: FTBFS with openjdk-10: NumberFormatException: For input string: "0x100" Added tag(s) pending. -- 901516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901516 Debian Bug Tracking System Contact

Bug#901516: Bug #901516 in sbt-serialization marked as pending

2018-11-14 Thread Emmanuel Bourg
Control: tag -1 pending Hello, Bug #901516 in sbt-serialization 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#898520: marked as done (u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 21:51:33 + with message-id and subject line Bug#898520: fixed in u-boot 2018.11+dfsg-1 has caused the Debian Bug report #898520, regarding u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC to be marked as done. This means that you

Bug#913764: mozilla-noscript: FTBFS because of dh_webext UnicodeDecodeError

2018-11-14 Thread Markus Koschany
Source: mozilla-noscript Version: 10.1.9.6-2 Severity: serious Hi, mozilla-noscript currently FTBFS because of https://buildd.debian.org/status/fetch.php?pkg=mozilla-noscript=all=10.1.9.6-2=1537976571=0 dh_webext: Ignored some command-line arguments: ['-i'] Traceback (most recent call last):

Bug#913720: eccodes: follow up patch for hard coded python3

2018-11-14 Thread Jeremy Bicha
Since you're currently only building for the default python3, I am attaching a minor patch to update your Build-Depends. It might be useful later to build for all supported python3 versions but that would take more work. Thanks, Jeremy Bicha From 3909dfbdfec7df36bdba03d2f3e114488833149c Mon Sep

Bug#913720: marked as done (eccodes: hard-codes python3.6 but doesn't depend on python3.6)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 15:48:27 -0500 with message-id and subject line Bug#913720: fixed in eccodes 2.9.2-2 has caused the Debian Bug report #913720, regarding eccodes: hard-codes python3.6 but doesn't depend on python3.6 to be marked as done. This means that you claim that the

Bug#908678: Testing the filter-branch scripts

2018-11-14 Thread Salvatore Bonaccorso
Hi, On Wed, Nov 14, 2018 at 07:45:59PM +0100, Moritz Muehlenhoff wrote: > On Wed, Nov 14, 2018 at 07:34:03AM +0100, Daniel Lange wrote: > > Am 13.11.18 um 23:09 schrieb Moritz Muehlenhoff: > > > The current data structure works very well for us and splitting the files > > > has many downsides. >

Processed: Re: Bug#913753: FTBFS: test-suite fails with ERROR: Rust compiler rustc can not compile programs.

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 913753 rustc Bug #913753 [src:meson] FTBFS: test-suite fails with ERROR: Rust compiler rustc can not compile programs. Bug reassigned from package 'src:meson' to 'rustc'. No longer marked as found in versions meson/0.48.1-1. Ignoring

Bug#908678: Testing the filter-branch scripts

2018-11-14 Thread Holger Levsen
On Wed, Nov 14, 2018 at 07:45:59PM +0100, Moritz Muehlenhoff wrote: > Nearly all the tasks of actually editing the data require a look at the > complete > data, e.g. to check whether something was tracked before, whether there's an > ITP > for something, whether something was tracked as NFU in

Processed: r-cran-stringi: FTBFS on big-endian against new ICU

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 913626 r-cran-stringi: FTBFS on big-endian against new ICU Bug #913626 [src:r-cran-stringi] r-cran-stringi ftbfs with the new icu Changed Bug title to 'r-cran-stringi: FTBFS on big-endian against new ICU' from 'r-cran-stringi ftbfs with

Bug#913752: Why is an "all" package compiling things?

2018-11-14 Thread Steve McIntyre
Package: autobahn-cpp Version: 17.5.1+git7cc5d37-2 Severity: serious Justification: fails to build from source Hi, Running an rebuild of armhf and armel running on top of arm64 machines, I'm seeing build failures for autobahn-cpp. Investigating further, I can see that it's not actually trying to

Bug#908678: Testing the filter-branch scripts

2018-11-14 Thread Moritz Muehlenhoff
On Wed, Nov 14, 2018 at 07:34:03AM +0100, Daniel Lange wrote: > Am 13.11.18 um 23:09 schrieb Moritz Muehlenhoff: > > The current data structure works very well for us and splitting the files > > has many downsides. > > Could you detail what those many downsides are besides the scripts that > need

Bug#913623: marked as done (ocrmypdf: FTBFS when built twice in a row)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 18:35:02 + with message-id and subject line Bug#913623: fixed in ocrmypdf 6.2.5-2 has caused the Debian Bug report #913623, regarding ocrmypdf: FTBFS when built twice in a row to be marked as done. This means that you claim that the problem has been dealt

Bug#913270: marked as done (systemc FTBFS: symbol differences)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 18:20:54 + with message-id and subject line Bug#913270: fixed in systemc 2.3.2-3 has caused the Debian Bug report #913270, regarding systemc FTBFS: symbol differences to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#913709: boost1.67: intermitent FTBFS on mips64el: build hangs

2018-11-14 Thread Giovanni Mascellani
Hi, Il 14/11/18 18:16, Emilio Pozuelo Monfort ha scritto: > Some questions which may help solve this: > > - What is happening when the build hangs? Is xsltproc still running, just > being > too slow / taking way too long? I believe so, since apparently, even on the slow builders, given enough

Bug#913709: boost1.67: intermitent FTBFS on mips64el: build hangs

2018-11-14 Thread Emilio Pozuelo Monfort
Hi Giovanni, On 14/11/2018 10:29, Giovanni Mascellani wrote: > Hi, > > Il 14/11/18 09:56, Emilio Pozuelo Monfort ha scritto: >> Your package fails to build quite often on mips64el, where the build gets >> killed due to inactivity: >> >> Cannot find class named 'action' >> Cannot find class named

Bug#913641: libreoffice-report-builder: report builder reports fail to run

2018-11-14 Thread Rene Engelhard
On Tue, Nov 13, 2018 at 06:40:06PM -0800, Anton Cohen wrote: >On Tue, 13 Nov 2018 13:13:09 +0100 Lionel Elie Mamane ><[1]lio...@mamane.lu> wrote: >> Downgrading to 8u171-b11-2 makes this problem disappear. >Except 8u171-b11-2 (and all 8u171 builds) was removed from the pool for >

Bug#913556: marked as done (apt-show-versions: Max. recursion depth with nested structures exceeded)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 16:49:15 + with message-id and subject line Bug#913556: fixed in apt-show-versions 0.22.10 has caused the Debian Bug report #913556, regarding apt-show-versions: Max. recursion depth with nested structures exceeded to be marked as done. This means that

Bug#912916: mysql-connector-java: CVE-2018-3258: allows low privileged attacker to compromise it

2018-11-14 Thread Rene Engelhard
Hi, On Mon, Nov 05, 2018 at 04:54:55PM +0100, Markus Koschany wrote: > libreoffice-base-drivers https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/3c5f364b4a31f29cf1e3ad44bcd2d3c7ef37206e Regards, Rene

Bug#913744: onedrive: Fails to sync after curl upgrade

2018-11-14 Thread Herbert Snorrason
Package: onedrive Version: 1.1.20180922~really1.1.3-1+b1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, onedrive makes three attempts to synchronise a file, reporting a 302 Found as an error, before throwing an exception and barfing a stack trace. This is

Bug#913729: marked as done (wrong modinfo path if compiled on merged-usr system and executed on unmerged system)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 16:19:30 + with message-id and subject line Bug#913729: fixed in firewalld 0.6.3-3 has caused the Debian Bug report #913729, regarding wrong modinfo path if compiled on merged-usr system and executed on unmerged system to be marked as done. This means

Bug#911626: marked as done (elpa-vimish-fold: fails to upgrade from 'stretch': vimish-fold.el:59:1:Error: Cannot open load file: No such file or directory, s)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 16:20:08 + with message-id and subject line Bug#911626: fixed in vimish-fold 0.2.3-3 has caused the Debian Bug report #911626, regarding elpa-vimish-fold: fails to upgrade from 'stretch': vimish-fold.el:59:1:Error: Cannot open load file: No such file or

Bug#913116: chromium

2018-11-14 Thread Josh Triplett
On Wed, Nov 14, 2018 at 03:35:24PM +0100, Salvo Tomaselli wrote: > If it can't start without it, it really should depend on it I get the impression that chromium is *supposed* to work without the setuid sandbox, if it has the necessary support from the underlying system to do unprivileged

Bug#913742: ip6tables-save produces broken syntax, unable to load them

2018-11-14 Thread Stefan Bühler
Package: iptables Version: 1.8.1-2 Severity: grave Tags: security Reproduce with: # ip6tables -A INPUT ! -s ::1 # ip6tables-save | ip6tables-restore Bad argument `!-s' Error occurred at line: 6 Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information. # ip6tables-save #

Bug#913620: marked as done (phpize7.3 hardcodes incorrect absolute path to sed if built on /usr-merged system)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 15:35:07 + with message-id and subject line Bug#913620: fixed in php7.3 7.3.0~rc5-2 has caused the Debian Bug report #913620, regarding phpize7.3 hardcodes incorrect absolute path to sed if built on /usr-merged system to be marked as done. This means that

Bug#913609: bpfcc FTBFS on amd64: No such file or directory: 'bcc-0.7.0'

2018-11-14 Thread Ritesh Raj Sarraf
Control: tag -1 +help I am very occupied right now with limited time on weekends. If anyone else, who cares for bpfcc in Debian, wants to take this up, that will help a lot (given that the bug has severity 'serious'). Ritesh On Tue, 2018-11-13 at 00:05 +0200, Adrian Bunk wrote: > Source: bpfcc

Processed: Re: Bug#913609: bpfcc FTBFS on amd64: No such file or directory: 'bcc-0.7.0'

2018-11-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 +help Bug #913609 [src:bpfcc] bpfcc FTBFS on amd64: No such file or directory: 'bcc-0.7.0' Added tag(s) help. -- 913609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#913730: marked as done (connman: unable to upgrade 1.33-1 -> 1.36-1)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 16:14:44 +0100 with message-id and subject line Re: connman: unable to upgrade 1.33-1 -> 1.36-1 has caused the Debian Bug report #913730, regarding connman: unable to upgrade 1.33-1 -> 1.36-1 to be marked as done. This means that you claim that the problem has

Bug#913620: Happened before in #905187

2018-11-14 Thread Ondřej Surý
Oh, so thought I already uploaded it, but I hadn’t. So, I did it just now. Thanks! -- Ondřej Surý > On 14 Nov 2018, at 15:47, Felipe Sateler wrote: > > Hi Ondrej, > > On Wed, Nov 14, 2018 at 11:42 AM OndÅ™ej Surý wrote: >>> The previous fix was not a real fix, it only rebuilt the package

Bug#913270: marked as done (systemc FTBFS: symbol differences)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 14:53:41 + with message-id and subject line Bug#913270: fixed in eccodes 2.9.2-2 has caused the Debian Bug report #913270, regarding systemc FTBFS: symbol differences to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#913620: Happened before in #905187

2018-11-14 Thread Felipe Sateler
Hi Ondrej, On Wed, Nov 14, 2018 at 11:42 AM Ondřej Surý wrote: > The previous fix was not a real fix, it only rebuilt the package in a > non-merged environment. > > > Umm, what? > > >

Bug#913125: marked as done (missing requested rename of libsane)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 15:46:42 +0100 with message-id and subject line Re: Bug#913125: missing requested rename of libsane has caused the Debian Bug report #913125, regarding missing requested rename of libsane to be marked as done. This means that you claim that the problem has

Bug#913729: [Pkg-utopia-maintainers] Bug#913729: wrong modinfo path if compiled on merged-usr system and executed on unmerged system

2018-11-14 Thread Simon McVittie
On Wed, 14 Nov 2018 at 13:45:59 +0100, Michael Biebl wrote: > Am 14.11.18 um 13:18 schrieb Michael Biebl: > > I.e. AC_PATH_PROG return the wrong path when built in a merged-usr > > system. > > I suspect that this particular problem is very widespread, so i was > > wondering if we couldn't just

Bug#913620: Happened before in #905187

2018-11-14 Thread Michael Biebl
Thanks for the updated patch. Am 14.11.18 um 15:12 schrieb Felipe Sateler: > Thanks. Please find an attached patch. However, I don't think this makes > a practical difference for debian packages, since they run configure > only once per builddir. True. That said, I wanted to post it here since I

Bug#913620: Happened before in #905187

2018-11-14 Thread Ondřej Surý
> The previous fix was not a real fix, it only rebuilt the package in a > non-merged environment. Umm, what? https://salsa.debian.org/php-team/php/blob/master-7.3/debian/patches/0048-Don-t-use-sed-found-by-configure-use-the-sed-command.patch -- Ondřej Surý > On 14 Nov 2018, at 14:42,

Bug#913116: chromium

2018-11-14 Thread Salvo Tomaselli
If it can't start without it, it really should depend on it -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno." -- Galileo Galilei http://ltworf.github.io/ltworf/

Bug#913620: Happened before in #905187

2018-11-14 Thread Felipe Sateler
On Wed, Nov 14, 2018 at 11:01 AM Michael Biebl wrote: > Hi Felipe > > On Wed, 14 Nov 2018 10:42:55 -0300 Felipe Sateler > wrote: > > + SED=/bin/sed dh_auto_configure --builddirectory $${target}-build > $(PARALLEL) -- $$(eval echo \$${$${target}_config}); \ > > Reading > >

Bug#913620: Happened before in #905187

2018-11-14 Thread Michael Biebl
On Tue, 13 Nov 2018 01:27:41 -0800 Kunal Mehta wrote: > This is the same regression as #905187 - is there a good way we can > prevent this from happening again? Fwiw, reprroducible-builds.org now also contains a merged-usr variation, which also found this particular problem:

Bug#913620: Happened before in #905187

2018-11-14 Thread Michael Biebl
Hi Felipe On Wed, 14 Nov 2018 10:42:55 -0300 Felipe Sateler wrote: > + SED=/bin/sed dh_auto_configure --builddirectory $${target}-build > $(PARALLEL) -- $$(eval echo \$${$${target}_config}); \ Reading

Bug#911405: marked as done (gnocchi FTBFS: error in setup.cfg: command 'build_py' has no such option 'pre_hook.build_config')

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 13:49:22 + with message-id and subject line Bug#911405: fixed in gnocchi 4.3.1-2 has caused the Debian Bug report #911405, regarding gnocchi FTBFS: error in setup.cfg: command 'build_py' has no such option 'pre_hook.build_config' to be marked as done.

Bug#888383: kodi: FTBFS with FFmpeg 3.5

2018-11-14 Thread Bálint Réczey
Rémi DUCCESCHI ezt írta (időpont: 2018. nov. 14., Sze, 11:30): > > Hello, > > I recently did the following bug report on kodi-bin because of broken > dependencies: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912994 > > I just saw that in Ubuntu, they are depending on libavcodec58 for their

Bug#913620: Happened before in #905187

2018-11-14 Thread Felipe Sateler
Control: tags -1 patch Control: user m...@linux.it Control: usertags -1 usrmerge On Tue, 13 Nov 2018 01:27:41 -0800 Kunal Mehta wrote: > This is the same regression as #905187 - is there a good way we can > prevent this from happening again? The previous fix was not a real fix, it only rebuilt

Processed (with 2 errors): Re: Happened before in #905187

2018-11-14 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #913620 [php7.3-dev] phpize7.3 hardcodes incorrect absolute path to sed if built on /usr-merged system Added tag(s) patch. > user m...@linux.it Unknown command or malformed arguments to command. > usertags -1 usrmerge Unknown command or malformed

Bug#913271: marked as done (segfault - broken rust compiling)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 13:35:53 + with message-id and subject line Bug#913271: fixed in llvm-toolchain-7 1:7.0.1~+rc2-3 has caused the Debian Bug report #913271, regarding segfault - broken rust compiling to be marked as done. This means that you claim that the problem has been

Bug#913500: marked as done (cargo FTBFS: rustc segfaults)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 13:35:53 + with message-id and subject line Bug#913271: fixed in llvm-toolchain-7 1:7.0.1~+rc2-3 has caused the Debian Bug report #913271, regarding cargo FTBFS: rustc segfaults to be marked as done. This means that you claim that the problem has been

Bug#901523: marked as done (sbt-template-resolver: FTBFS with openjdk-10)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 13:36:52 + with message-id and subject line Bug#901523: fixed in sbt-template-resolver 0.1+repack-1 has caused the Debian Bug report #901523, regarding sbt-template-resolver: FTBFS with openjdk-10 to be marked as done. This means that you claim that the

Bug#893345: marked as done (javafxsvg FTBFS with openjdk-9)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 13:34:28 + with message-id and subject line Bug#893345: fixed in javafxsvg 1.2.1-2 has caused the Debian Bug report #893345, regarding javafxsvg FTBFS with openjdk-9 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug #893345 in javafxsvg marked as pending

2018-11-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #893345 [src:javafxsvg] javafxsvg FTBFS with openjdk-9 Added tag(s) pending. -- 893345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#893345: Bug #893345 in javafxsvg marked as pending

2018-11-14 Thread Markus Koschany
Control: tag -1 pending Hello, Bug #893345 in javafxsvg 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: sbt-serialization: FTBFS with openjdk-10: NumberFormatException: For input string: "0x100"

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian-j...@lists.debian.org Setting user to debian-j...@lists.debian.org (was ebo...@apache.org). > usertag 901516 + default-java10 There were no usertags set. Usertags are now: default-java10. > tags 901516 + sid buster Bug #901516

Bug#913088: Bug fixed in upstream version 1.8.2

2018-11-14 Thread Holger Hahn
Hi, FYI, the new upstream release 1.8.2 for iptables already contains the fix. According to i00kv6d (https://github.com/arno-iptables-firewall/aif/issues/53), the fix is working as expected. Holger

Bug#901523: Bug #901523 in sbt-template-resolver marked as pending

2018-11-14 Thread Emmanuel Bourg
Control: tag -1 pending Hello, Bug #901523 in sbt-template-resolver 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 #901523 in sbt-template-resolver marked as pending

2018-11-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #901523 [src:sbt-template-resolver] sbt-template-resolver: FTBFS with openjdk-10 Added tag(s) pending. -- 901523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: sbt-template-resolver: FTBFS with openjdk-10

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian-j...@lists.debian.org Setting user to debian-j...@lists.debian.org (was ebo...@apache.org). > usertag 901523 + default-java10 There were no usertags set. Usertags are now: default-java10. > tags 901523 + sid buster Bug #901523

Bug#913729: [Pkg-utopia-maintainers] Bug#913729: wrong modinfo path if compiled on merged-usr system and executed on unmerged system

2018-11-14 Thread Michael Biebl
Am 14.11.18 um 13:18 schrieb Michael Biebl: > I.e. AC_PATH_PROG return the wrong path when built in a merged-usr > system. > I suspect that this particular problem is very widespread, so i was > wondering if we couldn't just address this once in the AC_PATH_PROG [1] > macro, by preferring /bin/

Bug#913730: connman: unable to upgrade 1.33-1 -> 1.36-1

2018-11-14 Thread Per Andersson
Package: connman Version: 1.36-1 Severity: grave Justification: causes non-serious data loss Hi! Upgrade of connman from 1.33-1 to 1.36-1 fails. Unable to upgrade normally, used full-resolver to remedy. This upgraded the package but removed /etc/resolv.conf and deconfigured the wireless network

Bug#911527: [Pkg-emacsen-addons] Bug#911527: please remove Pre-Depends on common-lisp-controller

2018-11-14 Thread David Bremner
Sébastien Villemot writes: > Source: ilisp > Version: 5.12.0+cvs.2004.12.26-27 > Severity: important > Tags: patch > > Dear Maintainer, > > Please drop the Pre-Depends on common-lisp-controller. This package is > obsolete, and ideally it will not ship with Buster. It has been superseded by >

Bug#913729: wrong modinfo path if compiled on merged-usr system and executed on unmerged system

2018-11-14 Thread Michael Biebl
Package: firewalld Version: 0.6.3-2 Severity: serious Trying to start firewalld, I get: Nov 14 13:05:04 pluto firewalld[1126]: WARNING: modinfo command is missing, not able to detect conntrack helpers. Nov 14 13:05:04 pluto firewalld[1126]: ERROR: Failed to load nf_conntrack module: Nov 14

Bug#901522: marked as done (scala-pickling: FTBFS with openjdk-10)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 12:08:20 + with message-id and subject line Bug#901522: fixed in scala-pickling 0.10.1+repack-1 has caused the Debian Bug report #901522, regarding scala-pickling: FTBFS with openjdk-10 to be marked as done. This means that you claim that the problem has

Processed: tagging 896006

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 896006 + wontfix Bug #896006 [src:eclipse] eclipse: FTBFS on buster, unmappable character encoding errors Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 896006:

Bug#901522: Bug #901522 in scala-pickling marked as pending

2018-11-14 Thread Emmanuel Bourg
Control: tag -1 pending Hello, Bug #901522 in scala-pickling 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 #901522 in scala-pickling marked as pending

2018-11-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #901522 [src:scala-pickling] scala-pickling: FTBFS with openjdk-10 Added tag(s) pending. -- 901522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#913614: [pkg-gnupg-maint] Bug#913614: Bug#913614: gnupg2 fails with "cannot open '/dev/tty': No such device or address"

2018-11-14 Thread Werner Koch
On Tue, 13 Nov 2018 16:19, tia...@debian.org said: > Even for something that shouldn't have a reason to prompt, like > "--recv-keys" with a full fingerprint? You are right, this should not be needed. I recall that we recently fixed a similar case where we accidentally printed to the tty. In

Processed: severity of 913509 is serious

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # icu63 transition obviously has started > severity 913509 serious Bug #913509 [src:openttd] openttd FTBFS with ICU 63.1 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#880393: libsasl2-modules-gssapi-heimdal seems built against MIT - Buster?

2018-11-14 Thread Johan Wassberg
Hi again! Will the patch from Helmut be included in Buster and make this library useful again? -- jocar

Bug#901520: marked as done (scopt: FTBFS with openjdk-10)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 10:35:03 + with message-id and subject line Bug#901520: fixed in scopt 3.5.0+repack-1 has caused the Debian Bug report #901520, regarding scopt: FTBFS with openjdk-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#888383: kodi: FTBFS with FFmpeg 3.5

2018-11-14 Thread Rémi DUCCESCHI
Hello, I recently did the following bug report on kodi-bin because of broken dependencies: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912994 I just saw that in Ubuntu, they are depending on libavcodec58 for their last version of kodi-bin (see

Bug#913699: marked as done (keymapper depends on nonexistent package python-yapps2)

2018-11-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Nov 2018 10:27:07 + with message-id and subject line Bug#913699: fixed in keymapper 0.5.3-12 has caused the Debian Bug report #913699, regarding keymapper depends on nonexistent package python-yapps2 to be marked as done. This means that you claim that the problem

Processed: Re: scala-pickling: FTBFS with openjdk-10

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian-j...@lists.debian.org Setting user to debian-j...@lists.debian.org (was ebo...@apache.org). > usertag 901522 + default-java10 There were no usertags set. Usertags are now: default-java10. > tags 901522 + sid buster Bug #901522

Bug#911711: svgwrite FTBFS: tests fail

2018-11-14 Thread Herbert Fortes
On Mon, 12 Nov 2018 23:06:30 + "foss.freedom" wrote: > I can confirm that v1.2.0 that has been released a few weeks ago > compiles just fine. > > If it helps I've created a debdiff for the changes between 1.1.8-2 and > 1.2.0 - a few tweaks to the debian package is additionally required >

Bug#913719: Don't include metche in Buster

2018-11-14 Thread intrigeri
I should add that I'm not running away because maintaining metche is particularly troublesome: it is pretty stable software, does its intended job pretty well, hasn't bitrotted, and does not require much maintenance work (maybe 4-12 hours a year). I'm simply cleaning up my plate of things I don't

Processed: tagging 913614

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 913614 + stretch Bug #913614 [gnupg] gnupg2 fails with "cannot open '/dev/tty': No such device or address" Added tag(s) stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 913614:

Processed: notfound 913614 in 2.2.1-5

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 913614 2.2.1-5 Bug #913614 [gnupg] gnupg2 fails with "cannot open '/dev/tty': No such device or address" Ignoring request to alter found versions of bug #913614 to the same values previously set > thanks Stopping processing here.

Bug#913720: eccodes: hard-codes python3.6 but doesn't depend on python3.6

2018-11-14 Thread Jeremy Bicha
Source: eccodes Version: 2.9.0-1 Severity: serious eccodes requires python3.6 in its debian/rules but doesn't Build-Depend on python3.6. It Build-Depends on python3-all-dev. In Ubuntu 19.04 Alpha, python3-all-dev depends on python3.7-dev but not python3.6-dev. I'm filing this bug as Serious since

Bug#913719: Don't include metche in Buster

2018-11-14 Thread intrigeri
Package: metche Severity: serious Version: 1:1.2.4-1 X-Debbugs-Cc: met...@lists.riseup.net Hi! I've de facto been the only upstream maintainer for 10+ years and Debian package maintainer for ~7 years. I'm not using metche anymore and have lost interest so I don't feel comfortable taking care of

Processed: fixed 913614 in 2.2.2-1

2018-11-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 913614 2.2.2-1 Bug #913614 [gnupg] gnupg2 fails with "cannot open '/dev/tty': No such device or address" Marked as fixed in versions gnupg2/2.2.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 913614:

Processed: Bug #901520 in scopt marked as pending

2018-11-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #901520 [src:scopt] scopt: FTBFS with openjdk-10 Added tag(s) pending. -- 901520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#901520: Bug #901520 in scopt marked as pending

2018-11-14 Thread Emmanuel Bourg
Control: tag -1 pending Hello, Bug #901520 in scopt 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#913713: ndctl: Incomplete debian/copyright?

2018-11-14 Thread Chris Lamb
Source: ndctl Version: 63-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Breno Leitao , ftpmas...@debian.org Hi, I just ACCEPTed ndctl from NEW but noticed it was missing attribution in debian/copyright for at least Junio Hamano, Fujitsu, etc. This is in no way exhaustive so please

Bug#913699: keymapper depends on nonexistent package python-yapps2

2018-11-14 Thread Colin Watson
On Wed, Nov 14, 2018 at 05:02:08AM +, peter green wrote: > keymapper depends on python-yapps2 which does not appear to exist, did > you mean to depend on python-yapps? Urgh, yes, silly mistake, sorry! Upload on its way. -- Colin Watson

Bug#913709: boost1.67: intermitent FTBFS on mips64el: build hangs

2018-11-14 Thread Giovanni Mascellani
Hi, Il 14/11/18 09:56, Emilio Pozuelo Monfort ha scritto: > Your package fails to build quite often on mips64el, where the build gets > killed due to inactivity: > > Cannot find class named 'action' > Cannot find class named 'action' > Cannot find class named 'file-target' > Cannot find class

Processed: Re: [pkg-gnupg-maint] Bug#913614: gnupg2 fails with "cannot open '/dev/tty': No such device or address"

2018-11-14 Thread Debian Bug Tracking System
Processing control commands: > tags 913614 + confirmed Bug #913614 [gnupg] gnupg2 fails with "cannot open '/dev/tty': No such device or address" Added tag(s) confirmed. > fixed 913614 2.2.2 Bug #913614 [gnupg] gnupg2 fails with "cannot open '/dev/tty': No such device or address" There is no

Bug#913709: boost1.67: intermitent FTBFS on mips64el: build hangs

2018-11-14 Thread Emilio Pozuelo Monfort
Source: boost1.67 Version: 1.67.0-9 Severity: serious Hi, Your package fails to build quite often on mips64el, where the build gets killed due to inactivity: Cannot find class named 'action' Cannot find class named 'action' Cannot find class named 'file-target' Cannot find class named

Bug#908678: Testing the filter-branch scripts

2018-11-14 Thread Guido Günther
Hi, On Tue, Nov 13, 2018 at 11:09:41PM +0100, Moritz Muehlenhoff wrote: > On Tue, Nov 13, 2018 at 12:22:54PM -0500, Antoine Beaupré wrote: > > But before going through that trouble, I think we'd need to get approval > > from the security team first, as that's quite a lot of work. I figured > > we

  1   2   >