Bug#890689: ruby-rgen FTBFS with ruby 2.5

Hi, These errors happen in ruby >= 2.4 since Fixnum and Bignum were merged into Integer. The following upstream commit fixes the issue: https://github.com/mthiede/rgen/commit/1124f4303db52973967e78d93512a1c1b64f23cf Attached is a patch to the debian source from https://salsa.debian.org/ruby-t

Processed: Re: [Pkg-fonts-devel] Bug#919721: fonts-firacode: looks broken on at least kitty and hexchat

Processing control commands: > severity -1 normal Bug #919721 [fonts-firacode] fonts-firacode: looks broken on at least kitty and hexchat Severity set to 'normal' from 'grave' -- 919721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919721 Debian Bug Tracking System Contact ow...@bugs.debia

Bug#919721: [Pkg-fonts-devel] Bug#919721: fonts-firacode: looks broken on at least kitty and hexchat

Control: severity -1 normal Hi Antonio, thanks for the report, but I fail to see how a change in vertical spacing could justify grave severity for a font package. - Fabian signature.asc Description: This is a digitally signed message part

Bug#919773: libdbd-sqlite3-perl FTBFS on mips: test failure

On Sat, 19 Jan 2019 20:25:44 +0100, Xavier wrote: > There is a difference earlier between mips and amd64: the first writes: > > # current DEFENSIVE value: 0 > > while the second has "1" Hm, I don't see "1" in any logs on the buildds and also not in my local amd64 build log. > So it seems th

Processed: user debian-rele...@lists.debian.org, usertagging 887750, tagging 887750

Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was anar...@debian.org). > usertags 887750 + bsp-2019-01-ca-montreal There were no usertags set. Usertags are now: bsp-2019-01-ca-montreal. > tags 887750 + pendi

Processed: user debian-rele...@lists.debian.org, usertagging 887750, tagging 887750

Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was anar...@debian.org). > usertags 887750 + bsp-2019-01-ca-montreal Usertags were: bsp-2019-01-ca-montreal. Usertags are now: bsp-2019-01-ca-montreal. > tags 88

Processed: not important

Processing commands for cont...@bugs.debian.org: > owner 910627 po...@debian.org Bug #910627 [xul-ext-nostalgy] xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+ Owner recorded as po...@debian.org. > End of message, stopping processing here. Please contact me if you

Bug#919289: [Pkg-kde-extras] Bug#919289: kile: After upgrade, kile will not open until okular installed

I have checked the code and Kile is trying to open the plugin and not the library: From src/kileviewmanager.cpp::1088 void Manager::createViewerPart(KActionCollection *actionCollection) { m_viewerPart = Q_NULLPTR; KPluginLoader pluginLoader(OKULAR_LIBRARY_NAME); KPluginFactory *fact

Processed: set patch tag

Processing commands for cont...@bugs.debian.org: > tags 890689 + patch Bug #890689 [src:ruby-rgen] ruby-rgen FTBFS with ruby 2.5 Added tag(s) patch. > thank you Stopping processing here. Please contact me if you need assistance. -- 890689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890689

Processed: Pending

Processing commands for cont...@bugs.debian.org: > tag 919289 pending Bug #919289 [kile] kile: After upgrade, kile will not open until okular installed Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 919289: https://bugs.debian.org/cgi-bin/b

Bug#855958: marked as done (xserver-xorg-video-nv: FTBFS with current Xorg: nv_driver.c:1181:6: error: too many arguments to function 'pScreen->BlockHandler')

Your message dated Sat, 19 Jan 2019 20:46:55 + with message-id and subject line Bug#855958: fixed in xserver-xorg-video-nv 1:2.1.21-1 has caused the Debian Bug report #855958, regarding xserver-xorg-video-nv: FTBFS with current Xorg: nv_driver.c:1181:6: error: too many arguments to function '

Processed: update

Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was kie...@koumbit.org). > usertags 904657 + bsp-2019-01-ca-montreal There were no usertags set. Usertags are now: bsp-2019-01-ca-montreal. > tags 904657 + patch

Bug#904657: update

user debian-rele...@lists.debian.org usertags 904657 + bsp-2019-01-ca-montreal tags 904657 + patch thank you Hi, I tested a proposed patch from the upstream github repository which allows the package to build and run : https://github.com/snare/voltron/pull/243 I'm not sure if there are other si

Bug#919817: mysql-5.7: Security fixes from the January 2019 CPU

Source: mysql-5.7 Version: 5.7.24-3 Severity: grave Tags: security upstream Justification: user security hole Hi Details at https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html#AppendixMSQL Regards, Salvatore

Bug#910627: xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+

Hello from the Montreal BSP! I tested the latest release of the upstream version (0.2.36) and it worked fine for me on the latest Thunderbird in testing. I migrated the nostalgy VCS from the Alioth archive to Salsa and updated it to the latest release: https://salsa.debian.org/webext-team/nostalg

Bug#887750: pam-python: diff for NMU version 1.0.6-1.1

Dear maintainer, I've prepared an NMU for pam-python (versioned as 1.0.6-1.1) and uploaded it to DELAYED/0. Please feel free to tell me if I should delay it longer. Regards. -- diff -Nru pam-python-1.0.6/debian/changelog pam-python-1.0.6/debian/changelog --- pam-python-1.0.6/debian/changelog 20

Processed: tagging 919529, bug 919529 is forwarded to https://github.com/rgaufman/live555/issues/19

Processing commands for cont...@bugs.debian.org: > tags 919529 + upstream Bug #919529 {Done: Sebastian Ramacher } [src:liblivemedia] CVE-2019-6256 Added tag(s) upstream. > forwarded 919529 https://github.com/rgaufman/live555/issues/19 Bug #919529 {Done: Sebastian Ramacher } [src:liblivemedia] CV

Bug#887750: marked as done (pam-python FTBFS with glibc 2.26)

Your message dated Sat, 19 Jan 2019 21:35:22 + with message-id and subject line Bug#887750: fixed in pam-python 1.0.6-1.1 has caused the Debian Bug report #887750, regarding pam-python FTBFS with glibc 2.26 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#919529: CVE-2019-6256

Hey! On Thu, Jan 17, 2019 at 12:00:13AM +0100, Sebastian Ramacher wrote: > Control: found -1 2016.11.28-1 > > On 2019-01-16 23:19:45, Moritz Muehlenhoff wrote: > > Source: liblivemedia > > Severity: grave > > Tags: security > > > > Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-201

Bug#919820: mysql-connector-python: CVE-2019-2435

Source: mysql-connector-python Version: 8.0.11-1 Severity: grave Tags: security upstream Control: found -1 2.1.6-1 Hi, The following vulnerability was published for mysql-connector-python. CVE-2019-2435[0]: | Vulnerability in the MySQL Connectors component of Oracle MySQL | (subcomponent: Connec

Processed: mysql-connector-python: CVE-2019-2435

Processing control commands: > found -1 2.1.6-1 Bug #919820 [src:mysql-connector-python] mysql-connector-python: CVE-2019-2435 Marked as found in versions mysql-connector-python/2.1.6-1. -- 919820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919820 Debian Bug Tracking System Contact ow...@

Bug#917482: jhove: FTBFS in buster at least since 2018-12-07

Hi, I've attached a patch and made an upstream pull request. On Thu, 27 Dec 2018 22:52:58 + Santiago Vila wrote: > Package: src:jhove > Version: 1.20.1-4 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > > -

Bug#917482: jhove: FTBFS in buster at least since 2018-12-07

Control: tags -1 +patch On Sat, 19 Jan 2019 16:51:02 -0500 Abdelhakim Qbaich wrote: > Hi, > > I've attached a patch and made an upstream pull request. > > On Thu, 27 Dec 2018 22:52:58 + Santiago Vila > wrote: > > Package: src:jhove > > Version: 1.20.1-4 > > Severity: serious > > Tags: ftb

Processed: Re: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was kie...@koumbit.org). > usertag 919737 + bsp-2019-01-ca-montreal There were no usertags set. Usertags are now: bsp-2019-01-ca-montreal. > tags 919737 + unrepr

Bug#919822: gitlab: CVE-2019-6240: Arbitrary repo read in Gitlab project import

Source: gitlab Version: 11.5.6+dfsg-1 Severity: grave Tags: security upstream fixed-upstream Justification: user security hole Hi, The following vulnerability was published for gitlab, and fixed in 11.6.4, 11.5.7, and 11.4.14. CVE-2019-6240[0]: RESERVED If you fix the vulnerability please also

Processed: Re: jhove: FTBFS in buster at least since 2018-12-07

Processing control commands: > tags -1 +patch Bug #917482 [src:jhove] jhove: FTBFS in buster at least since 2018-12-07 Added tag(s) patch. -- 917482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tagging 919006

Processing commands for cont...@bugs.debian.org: > # does not affect buster yet as libdbd-sqlite3-perl 1.62-1 is blocked from > migrating by #919773 > tags 919006 - buster Bug #919006 [src:libclass-dbi-plugin-type-perl] FTBFS: test failure with new DBD::SQLite Removed tag(s) buster. > thanks Sto

Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

user debian-rele...@lists.debian.org usertag 919737 + bsp-2019-01-ca-montreal tags 919737 + unreproducible moreinfo thank you Hi, I tried building this package (underscore-1.8.3~dfsg) in a clean buster chroot (with sbuild) and a clean unstable chroot (also with sbuild), and it worked in both ca

Bug#910627: marked as done (xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+)

Your message dated Sat, 19 Jan 2019 22:04:26 + with message-id and subject line Bug#910627: fixed in nostalgy 0.2.36-1.1 has caused the Debian Bug report #910627, regarding xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+ to be marked as done. This means that y

Bug#919737: marked as done (underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option))

Your message dated Sat, 19 Jan 2019 23:14:24 +0100 with message-id <154793606424.5603.7578120566150068...@auryn.jones.dk> and subject line Re: [Pkg-javascript-devel] Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option) has caused the Debian Bug report #919737, rega

Bug#919289: marked as done (kile: After upgrade, kile will not open until okular installed)

Your message dated Sat, 19 Jan 2019 22:20:19 + with message-id and subject line Bug#919289: fixed in kile 4:2.9.92-2 has caused the Debian Bug report #919289, regarding kile: After upgrade, kile will not open until okular installed to be marked as done. This means that you claim that the prob

Bug#919823: harp: FTBFS in sid (ERROR: CODA library and/or header file not found)

Package: src:harp Version: 1.5+data-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-arch dh build-arch --with python3 dh_update_auto

Processed: Re: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

Processing commands for cont...@bugs.debian.org: > tags 919737 - unreproducible moreinfo Bug #919737 {Done: Jonas Smedegaard } [src:underscore] underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option) Removed tag(s) unreproducible and moreinfo. > thanks Stopping processing here.

Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

tags 919737 - unreproducible moreinfo thanks Based on the last message by Jonas, I'm removing those tags which do not apply here. Thanks.

Bug#919806: sbcl: FTBFS randomly (failing tests)

retitle 919806 sbcl: FTBFS randomly (failing tests) severity 919806 important thanks The build does not always fail. Thanks.

Processed: Re: Bug#919806: sbcl: FTBFS randomly (failing tests)

Processing commands for cont...@bugs.debian.org: > retitle 919806 sbcl: FTBFS randomly (failing tests) Bug #919806 [src:sbcl] sbcl: FTBFS (failing tests) Changed Bug title to 'sbcl: FTBFS randomly (failing tests)' from 'sbcl: FTBFS (failing tests)'. > severity 919806 important Bug #919806 [src:sb

Bug#916977: snoopy w/ ld preload enabled breaks "apt upgrade" jessie-to-buster

Hello, I use testing and updated hundreds of package without any trouble. Please, could you give an example of a package that fails to upgrade? Greetings, Marcos. On 11/1/19 18:52, Adrian Bunk wrote: > On Thu, Dec 20, 2018 at 05:26:25PM -0500, deb...@mailinator.com wrote: >> Package: snoopy >>

Bug#865955: marked as done (odin: FTBFS with dcmtk 3.6.1~20170228-2)

Your message dated Sat, 19 Jan 2019 22:49:46 + with message-id and subject line Bug#865955: fixed in odin 2.0.3-1 has caused the Debian Bug report #865955, regarding odin: FTBFS with dcmtk 3.6.1~20170228-2 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#904657: voltron: fails to install with Python 3.7 (was: Re: update)

On 2019-01-19 21:55, Kienan Stewart wrote: > I tested a proposed patch from the upstream github repository which allows > the package to build and run : https://github.com/snare/voltron/pull/243 > > I'm not sure if there are other side-effects to the patch, since the async > (now asynchronous) v

Processed: Bug #825501 in tika marked as pending

Processing control commands: > tag -1 pending Bug #825501 [src:tika] CVE-2016-4434 Added tag(s) pending. -- 825501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#825501: Bug #825501 in tika marked as pending

Control: tag -1 pending Hello, Bug #825501 in tika 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: https://salsa.debian.org/java-team/tika/commit/da8f564f02250bc904da8c03c45d2fa4c8f9c14

Bug#825501: marked as done (CVE-2016-4434)

Your message dated Sat, 19 Jan 2019 23:35:47 + with message-id and subject line Bug#825501: fixed in tika 1.18-1 has caused the Debian Bug report #825501, regarding CVE-2016-4434 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#910627: closed by Louis-Philippe Véronneau (Bug#910627: fixed in nostalgy 0.2.36-1.1)

On 19.01.19 22:06, Debian Bug Tracking System wrote: > It has been closed by Louis-Philippe Véronneau . Thanks, Louis-Philippe, one less package I have to take care about in a private repository. Great work. Thanks so much!!! Best, Daniel signature.asc Description: OpenPGP digital signature

Bug#919826: linux-image-4.19.0-1-arm64: Loading Linux 4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic

Package: linux-image-4.19.0-1-arm64 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upgrading kernel in Buster from 4.18.0-3-arm64 via apt-get dist-upgrade

Bug#917482: jhove: FTBFS in buster at least since 2018-12-07

On Sat, Jan 19, 2019 at 04:51:02PM -0500, Abdelhakim Qbaich wrote: > Hi, > > I've attached a patch and made an upstream pull request. Hello Abdelhakim Qbaich, Thank you for the patch. I have applied it and a few other misc packaging changes and uploaded to the archive. Cheers, tony signature

Bug#919828: asterisk-opus: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM)

Package: src:asterisk-opus Version: 13.7+20171009-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules binary-arch test -x debian/rules dh_testr

Bug#919827: asterisk-espeak: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM)

Package: src:asterisk-espeak Version: 5.0~1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules binary-arch test -x debian/rules dh_testroot dh

Bug#919829: libatteanx-store-sparql-perl: FTBFS (failing tests)

Package: src:libatteanx-store-sparql-perl Version: 0.010-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch test -x debian/rules mk

Processed: tagging 919829

Processing commands for cont...@bugs.debian.org: > tags 919829 + buster sid Bug #919829 [src:libatteanx-store-sparql-perl] libatteanx-store-sparql-perl: FTBFS (failing tests) Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 919829: htt

Processed: reassign 919826 to src:linux, severity of 919826 is important

Processing commands for cont...@bugs.debian.org: > reassign 919826 src:linux 4.19.12-1 Bug #919826 [linux-image-4.19.0-1-arm64] linux-image-4.19.0-1-arm64: Loading Linux 4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic Bug reassigned from package 'linux-image-4.19.0-1-arm6

Bug#917482: marked as done (jhove: FTBFS in buster at least since 2018-12-07)

Your message dated Sun, 20 Jan 2019 00:35:01 + with message-id and subject line Bug#917482: fixed in jhove 1.20.1-5 has caused the Debian Bug report #917482, regarding jhove: FTBFS in buster at least since 2018-12-07 to be marked as done. This means that you claim that the problem has been de

Bug#919831: libcds-moc-java: FTBFS (The code being documented uses packages in the unnamed module)

Package: src:libcds-moc-java Version: 5.0-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with javahelper d

Bug#905415: libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}

Followup-For: Bug #905415 Control: reopen -1 Control: reassign -1 libnode-dev 10.15.0~dfsg-8 Control: retitle -1 libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h} Hi, the package reorganisation changed th eissue but did not completely resolve it

Processed: Re: libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}

Processing control commands: > reopen -1 Bug #905415 {Done: Jérémy Lal } [libnode64-dev] libnode64-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/uv*.h -> ../../../../uv*.h Warning: Unknown package 'libnode64-dev' 'reopen' may be inappropriate when a bug has been closed with a version

Processed: user debian...@lists.debian.org, usertagging 876231 ..., affects 903762

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 876231 piuparts There were no usertags set. Usertags are now: piuparts. > found 905282 python-lldb-8/1:8~svn350193-1~exp1 Bug #905282 [pyt

Processed: reassign 919422 to firebird3.0-server, fixed 919422 in 3.0.5.33086.ds4-2 ...

Processing commands for cont...@bugs.debian.org: > reassign 919422 firebird3.0-server 3.0.1.32609.ds4-14 Bug #919422 {Done: Damyan Ivanov } [firebird3.0-server_3.0.1.32609.ds4-14_amd64.deb] firebird3.0-server_3.0.1.32609.ds4-14_amd64.deb: When installing I get an error Warning: Unknown package '

Bug#905415: Bug #905415 in nodejs marked as pending

Control: tag -1 pending Hello, Bug #905415 in nodejs 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: https://salsa.debian.org/js-team/nodejs/commit/c57aaadcde0715b0b383c037382b310c8f2d2

Processed: Bug #905415 in nodejs marked as pending

Processing control commands: > tag -1 pending Bug #905415 [libnode-dev] libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h} Added tag(s) pending. -- 905415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905415 Debian Bug Tracking System Conta

Processed: limit source to nodejs, tagging 905415

Processing commands for cont...@bugs.debian.org: > limit source nodejs Limiting to bugs with field 'source' containing at least one of 'nodejs' Limit currently set to 'source':'nodejs' > tags 905415 + pending Bug #905415 [libnode-dev] libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/inc

Bug#905415: libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}

Le dim. 20 janv. 2019 à 02:12, Andreas Beckmann a écrit : > Followup-For: Bug #905415 > Control: reopen -1 > Control: reassign -1 libnode-dev 10.15.0~dfsg-8 > Control: retitle -1 libnode-dev: broken symlinks: > /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h} > > Hi, > > the

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

Thanks but one still must forbid # aptitude search ~U iFA libilmbase23 iFA libopenexr23 if gimp is to start on experimental.

Bug#919836: jupyter-sphinx-theme-common: broken symlinks: /usr/share/jupyter_sphinx_theme/jupyter/static/boots{trap,watch}-2

Package: jupyter-sphinx-theme-common Version: 0.0.6+ds1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m30.4s ERROR: FAIL: Brok

Bug#919840: sqwebmail: leaves broken symlink after purge: /etc/apache2/conf-available/sqwebmail.conf -> ../../sqwebmail/apache24.conf

Package: sqwebmail Version: 6.0.0+1.0.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m54.4s ERROR: FAIL: Broken symlinks: /

Bug#919841: node-istanbul: broken symlinks: /usr/lib/nodejs/istanbul/lib/assets/vendor/prettify.{css,js} -> ../../../../../../share/javascript/prettify.{css,js}

Package: node-istanbul Version: 0.4.5+ds-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m33.0s ERROR: FAIL: Broken symlinks:

Bug#919843: lirc-doc: broken symlinks: /usr/share/doc/lirc/lirc.org/* -> /build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/*

Package: lirc-doc Version: 0.10.1-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m24.4s ERROR: FAIL: Broken symlinks: /usr/sh

Bug#919846: ruby-rails-assets-highlightjs: missing Depends: libjs-highlight.js

Package: ruby-rails-assets-highlightjs Version: 9.12.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m30.0s ERROR: FAIL: Broke

Bug#919847: ruby-rails-assets-markdown-it: missing Depends: libjs-markdown-it

Package: ruby-rails-assets-markdown-it Version: 8.4.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m28.5s ERROR: FAIL: Broken

Bug#919848: tclxml-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libtclxmlstub.a -> libtclxmlstub3.2.a

Package: tclxml-dev Version: 1:3.2.7-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m28.5s ERROR: FAIL: Broken symlinks: /usr

Bug#919850: python3-link-grammar: broken symlink: /usr/lib/python3.7/site-packages/linkgrammar/_clinkgrammar.so -> _clinkgrammar.so.5.5.1

Package: python3-link-grammar Version: 5.5.1-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m41.0s ERROR: FAIL: Broken symlinks

Bug#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

Santiago Vila 於 2019/1/20 上午1:35 寫道: > Package: src:libjstun-java > Version: 0.7.3+dfsg-1 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > > > [...]

Bug#919855: s390x executables crash

Source: klibc Version: 2.0.5-1 Severity: serious While investigating some test failures on klibc upstream, I found that the new Debian version crashes on s390x. It looks like this is due to an address collision between the build ID in the shared library and the code in the executables. The addit

Bug#919064: scala FTBFS: java.lang.NoClassDefFoundError: com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute

Hi Java team, I realised that there is no comment on this bug yet. Since several of my packages got a "removal from testing warning": Can I help somehow? Not that I had the slightest idea what to do about this bug but may be you have some idea I could test? I've seen that there is a new upstream

Processed: Re: [Pkg-rust-maintainers] Bug#918854: segfault updating crates.io index

Processing control commands: > severity -1 important Bug #918854 [cargo] segfault updating crates.io index Severity set to 'important' from 'grave' > tag -1 + moreinfo unreproducible Bug #918854 [cargo] segfault updating crates.io index Added tag(s) unreproducible and moreinfo. -- 918854: https:

Bug#918854: [Pkg-rust-maintainers] Bug#918854: segfault updating crates.io index

Control: severity -1 important Control: tag -1 + moreinfo unreproducible I can't reproduce this, can you install cargo-dbgsym rustc-dbgsym rust-gdb libstd-rust-1.31-dbgsym libllvm7-dbgsym libc6-dbg and provide a backtrace? X Josh Triplett: > Package: cargo > Version: 0.31.1-1 > Severity: grave

Bug#919002: Really bad regression

https://github.com/systemd/systemd/issues/11502

Bug#918841: Really bad regression

https://github.com/systemd/systemd/issues/11502

Bug#918848: Really bad regression

https://github.com/systemd/systemd/issues/11502

<    1   2