Bug#921351: [pkg-go] Bug#921351: prometheus-postfix-exporter: Init script missing

On Thu, Feb 7, 2019 at 8:46 AM Scott Kitterman wrote: > No. It's an actual policy violation, so the bug is correct. I'd leave it > as is and ask the release team to mark it buster-ignore. > Could you kindly point me to where the process is described for this? I’m not sure what I’d need to do

Bug#921351: [pkg-go] Bug#921351: prometheus-postfix-exporter: Init script missing

No. It's an actual policy violation, so the bug is correct. I'd leave it as is and ask the release team to mark it buster-ignore. Scott K On February 7, 2019 7:29:01 AM UTC, Michael Stapelberg wrote: >On Wed, Feb 6, 2019 at 11:01 PM Scott Kitterman >wrote: > >> It's not the FTP Team's job

Bug#921510: marked as done (qutemol: segfaults at startup when compiled with GCC 8)

Your message dated Thu, 07 Feb 2019 07:37:10 + with message-id and subject line Bug#921510: fixed in qutemol 0.4.1~cvs2008-12 has caused the Debian Bug report #921510, regarding qutemol: segfaults at startup when compiled with GCC 8 to be marked as done. This means that you claim that

Bug#921351: [pkg-go] Bug#921351: prometheus-postfix-exporter: Init script missing

On Wed, Feb 6, 2019 at 11:01 PM Scott Kitterman wrote: > It's not the FTP Team's job to fix policy compliance issues in packages. > If you have a problem with that being a policy must, then you should take > it up with the policy team. > Yeah, I’ll post to #911165 > > I completely understand

Bug#918566: Lost of code copies of MurmurHash3 (Was: Bug#918566: mash FTBFS on big endian: test failures)

Hi, On Wed, Feb 06, 2019 at 01:20:48PM +0100, Andreas Tille wrote: > On Mon, Feb 04, 2019 at 05:26:08PM +0100, Fabian Klötzl wrote: > > So I improved the upstream libmurmurhash, adapted the package and filed an > > ITP (#921353). I even managed to locally build mash against the new package. > >

Bug#919256: marked as done (dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1)

Your message dated Thu, 07 Feb 2019 06:49:47 + with message-id and subject line Bug#919256: fixed in dnssec-trigger 0.17+repack-3 has caused the Debian Bug report #919256, regarding dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess

Bug#921227: marked as done (dnssec-trigger: crashes (SIGSEGV))

Your message dated Thu, 07 Feb 2019 06:49:47 + with message-id and subject line Bug#921227: fixed in dnssec-trigger 0.17+repack-3 has caused the Debian Bug report #921227, regarding dnssec-trigger: crashes (SIGSEGV) to be marked as done. This means that you claim that the problem has been

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

version: 0.17+repack-3 tag: pending I have a new version (hopefully uploaded successfully) where I fixed dnssec-trigger-control-setup to not generate new keys or certificates if called repeatedly. So now the code to delete small keys should get called. I also included upstream's fix for the

Bug#921538: Fails to start since upgrade to 1.9.0-1

> > It seems like chroot'ing to /etc/unbound is attempted. To workaround you > can try this: > > cat << EOF > /etc/unbound/unbound.conf.d/chroot.conf > server: > chroot: "" > EOF > service unbound restart This fix worked for me.

Bug#918289: marked as done (node-autoprefixer build depends on node-js-beautify that is currently not in buster)

Your message dated Thu, 7 Feb 2019 06:52:24 +0100 with message-id <4f31120f-b978-6cf2-5508-ace266943...@debian.org> and subject line Fwd: node-js-beautify 1.7.5+dfsg-2 MIGRATED to testing has caused the Debian Bug report #918289, regarding node-autoprefixer build depends on node-js-beautify that

Bug#918290: marked as done (node-postcss build depends on node-js-beautify that is currently not in buster)

Your message dated Thu, 7 Feb 2019 06:52:24 +0100 with message-id <4f31120f-b978-6cf2-5508-ace266943...@debian.org> and subject line Fwd: node-js-beautify 1.7.5+dfsg-2 MIGRATED to testing has caused the Debian Bug report #918290, regarding node-postcss build depends on node-js-beautify that is

Processed: affects 915584

Processing commands for cont...@bugs.debian.org: > affects 915584 dicoweb Bug #915584 [python3.7] dicoweb: fails to install with python 3.7 Added indication that 915584 affects dicoweb > thanks Stopping processing here. Please contact me if you need assistance. -- 915584:

Processed: affects 921195

Processing commands for cont...@bugs.debian.org: > affects 921195 mcabber Bug #921195 [libloudmouth1-0] libloudmouth1-0: does not support IPv6 (fails Squeeze release goal) Added indication that 921195 affects mcabber > thanks Stopping processing here. Please contact me if you need assistance.

Processed: Re: Bug#915584: dicoweb: fails to install with python 3.7

Processing commands for cont...@bugs.debian.org: > affects 916584 -dico Bug #916584 [src:libpodofo] libpodofo: CVE-2018-11255 Removed indication that 916584 affects dico > affects 915584 +dico Bug #915584 [python3.7] dicoweb: fails to install with python 3.7 Added indication that 915584 affects

Processed: Re: Bug#915584: dicoweb: fails to install with python 3.7

Processing commands for cont...@bugs.debian.org: > reassign 915584 python3.7 Bug #915584 [dicoweb] dicoweb: fails to install with python 3.7 Bug reassigned from package 'dicoweb' to 'python3.7'. No longer marked as found in versions dico/2.7-1. Ignoring request to alter fixed versions of bug

Bug#914153: Update to version 2.3.0-3 breaks Megaglest

> > My suggestion of 2018-11-25 still stands. But if you want me to do > > my part of it, please do your review quickly and tell me soon > > (or, if it's indeed necessary for the soft freeze, immediately) to > > avoid running out of time. > > Your plan sounds OK. Changing packages after the

Bug#899567: marked as done (libapache2-mod-nss: Invalid maintainer address pkg-fedora-ds-maintain...@lists.alioth.debian.org)

Your message dated Thu, 07 Feb 2019 03:20:54 + with message-id and subject line Bug#915512: Removed package(s) from unstable has caused the Debian Bug report #899567, regarding libapache2-mod-nss: Invalid maintainer address pkg-fedora-ds-maintain...@lists.alioth.debian.org to be marked as

Bug#918284: marked as done (librdf-trine-serializer-rdfa-perl build depends on librdf-rdfa-parser-perl that is currently not in buster)

Your message dated Thu, 07 Feb 2019 03:20:40 + with message-id and subject line Bug#918284: fixed in librdf-trine-serializer-rdfa-perl 0.100-2 has caused the Debian Bug report #918284, regarding librdf-trine-serializer-rdfa-perl build depends on librdf-rdfa-parser-perl that is currently not

Bug#860072: marked as done (botan1.10: CVE-2017-2801: Incorrect comparison in X.509 DN strings)

Your message dated Thu, 07 Feb 2019 03:17:43 + with message-id and subject line Bug#889675: Removed package(s) from unstable has caused the Debian Bug report #860072, regarding botan1.10: CVE-2017-2801: Incorrect comparison in X.509 DN strings to be marked as done. This means that you claim

Bug#888089: marked as done (botan1.10 EOL)

Your message dated Thu, 07 Feb 2019 03:17:43 + with message-id and subject line Bug#889675: Removed package(s) from unstable has caused the Debian Bug report #888089, regarding botan1.10 EOL to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#917582: Please prevent autoremoval of freedombox

Hello, The two bugs #917582 and #917584 are threatening removal of freedombox from testing. As soft freeze is fast approaching, and once removed, we won't be able to add freedombox back into buster. Please consider uploading soon the newer upstream 0.9.0 which will hopefully eliminate the two

Processed: Bug #918284 in librdf-trine-serializer-rdfa-perl marked as pending

Processing control commands: > tag -1 pending Bug #918284 [src:librdf-trine-serializer-rdfa-perl] librdf-trine-serializer-rdfa-perl build depends on librdf-rdfa-parser-perl that is currently not in buster Added tag(s) pending. -- 918284:

Bug#918284: Bug #918284 in librdf-trine-serializer-rdfa-perl marked as pending

Control: tag -1 pending Hello, Bug #918284 in librdf-trine-serializer-rdfa-perl 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#916921: marked as done (radicale: upgrade to 2.x breaks compatibility with 1.x without any prior warning)

Your message dated Thu, 07 Feb 2019 02:46:57 + with message-id and subject line Bug#916921: fixed in radicale 2.1.11-4 has caused the Debian Bug report #916921, regarding radicale: upgrade to 2.x breaks compatibility with 1.x without any prior warning to be marked as done. This means that

Bug#918283: marked as done (librdf-query-client-perl build depends on libhttp-lrdd-perl that is currently not in buster)

Your message dated Thu, 07 Feb 2019 02:45:30 + with message-id and subject line Bug#918283: fixed in librdf-query-client-perl 0.114-2 has caused the Debian Bug report #918283, regarding librdf-query-client-perl build depends on libhttp-lrdd-perl that is currently not in buster to be marked

Bug#918283: Bug #918283 in librdf-query-client-perl marked as pending

Control: tag -1 pending Hello, Bug #918283 in librdf-query-client-perl 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 #918283 in librdf-query-client-perl marked as pending

Processing control commands: > tag -1 pending Bug #918283 [src:librdf-query-client-perl] librdf-query-client-perl build depends on libhttp-lrdd-perl that is currently not in buster Added tag(s) pending. -- 918283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918283 Debian Bug Tracking

Bug#921580: marked as done (golang-google-cloud must version the golang-google-genproto-dev build dependency on a post-buster version)

Your message dated Thu, 07 Feb 2019 01:34:40 + with message-id and subject line Bug#921580: fixed in golang-google-cloud 0.9.0-9 has caused the Debian Bug report #921580, regarding golang-google-cloud must version the golang-google-genproto-dev build dependency on a post-buster version to be

Bug#819705: marked as done (firmware-b43-installer: Brittle handling of /lib/firmware/b43, can readily conflict with other packages, improper removal during *postrm*)

Your message dated Thu, 07 Feb 2019 01:34:10 + with message-id and subject line Bug#819705: fixed in b43-fwcutter 1:019-4 has caused the Debian Bug report #819705, regarding firmware-b43-installer: Brittle handling of /lib/firmware/b43, can readily conflict with other packages, improper

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

Your message dated Thu, 07 Feb 2019 01:35:14 + with message-id and subject line Bug#919829: fixed in libatteanx-store-sparql-perl 0.012-1 has caused the Debian Bug report #919829, regarding libatteanx-store-sparql-perl: FTBFS (failing tests) to be marked as done. This means that you claim

Bug#921590: xen-utils-4.11: pygrub bails out with "ImportError: No module named fsimage"

Package: xen-utils-4.11,xen-utils-common Version: 4.11.1-1 Severity: serious Control: affects -1 xen-tools Hi, both, /usr/lib/xen-4.11/bin/pygrub as well as /usr/bin/pygrub bail out for me as follows on Buster: # /usr/bin/pygrub Traceback (most recent call last): File "/usr/bin/pygrub", line

Processed: xen-utils-4.11: pygrub bails out with "ImportError: No module named fsimage"

Processing control commands: > affects -1 xen-tools Bug #921590 [xen-utils-4.11,xen-utils-common] xen-utils-4.11: pygrub bails out with "ImportError: No module named fsimage" Added indication that 921590 affects xen-tools -- 921590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921590

Bug#914153: Update to version 2.3.0-3 breaks Megaglest

Em qua, 6 de fev de 2019 às 04:15, Frank Heckenbach escreveu: > > > Em qui, 3 de jan de 2019 às 22:56, Frank Heckenbach > > escreveu: > > > > > > According to https://release.debian.org/buster/freeze_policy.html: > > > > > > 2019-01-12 - Transition freeze > > > > > > Is there still time yet to

Bug#903056: marked as done (foremancli FTBFS: update Build-Depends: ruby-ronn -> ronn)

Your message dated Thu, 07 Feb 2019 00:19:47 + with message-id and subject line Bug#903056: fixed in foremancli 1.0-3 has caused the Debian Bug report #903056, regarding foremancli FTBFS: update Build-Depends: ruby-ronn -> ronn to be marked as done. This means that you claim that the problem

Bug#903056: Bug #903056 in foremancli marked as pending

Control: tag -1 pending Hello, Bug #903056 in foremancli 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#921284: build-using should only include copylefted files

On Thu, 7 Feb 2019 at 04:09, Antoine Beaupré wrote: > On 2019-02-03 17:21:35, Antoine Beaupre wrote: > > My first submissions for the dmarc-cat package (#920385) were refused > > by the FTP masters because the built-using field did not respect §7.8 > > of the Debian policy. > > That's actually

Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)

Control: reassign -1 libloudmouth1-0 Control: retitle -1 libloudmouth1-0: does not support IPv6 (fails Squeeze release goal) Control: tag -1 + patch On 2019-02-03 09:32, W. Martin Borgert wrote: > I'm in the same network, and mcabber works for me. After testing again, I believe, that my

Processed: Re: Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)

Processing control commands: > reassign -1 libloudmouth1-0 Bug #921195 [mcabber] mcabber: does not connect to Jabber via IPv6 (fails Etch release goal) Bug reassigned from package 'mcabber' to 'libloudmouth1-0'. No longer marked as found in versions mcabber/1.1.0-1.1. Ignoring request to alter

Bug#921580: golang-google-cloud must version the golang-google-genproto-dev build dependency on a post-buster version

Source: golang-google-cloud Version: 0.9.0-8 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-google-cloud/1861825/log.gz ... # cloud.google.com/go/profiler/mocks src/cloud.google.com/go/profiler/mocks/mock_profiler_client.go:49:86: undefined:

Bug#920536: marked as done (lintian: fails to build because of test failure)

Your message dated Wed, 06 Feb 2019 22:52:48 + with message-id and subject line Bug#920536: fixed in lintian 2.6.0 has caused the Debian Bug report #920536, regarding lintian: fails to build because of test failure to be marked as done. This means that you claim that the problem has been

Bug#921172: marked as done (qmath3d: Please stop build-depending on gcc-6)

Your message dated Wed, 06 Feb 2019 22:22:55 + with message-id and subject line Bug#921172: fixed in qmath3d 0~1.0-2 has caused the Debian Bug report #921172, regarding qmath3d: Please stop build-depending on gcc-6 to be marked as done. This means that you claim that the problem has been

Bug#919555: marked as done (libemf FTBFS on arm64: #error Unknown CPU architecture!)

Your message dated Wed, 06 Feb 2019 22:05:09 + with message-id and subject line Bug#919555: fixed in libemf 1.0.11-2 has caused the Debian Bug report #919555, regarding libemf FTBFS on arm64: #error Unknown CPU architecture! to be marked as done. This means that you claim that the problem

Bug#919766: marked as done (libemf FTBFS on big endian: FAIL: docheck2)

Your message dated Wed, 06 Feb 2019 22:05:09 + with message-id and subject line Bug#919766: fixed in libemf 1.0.11-2 has caused the Debian Bug report #919766, regarding libemf FTBFS on big endian: FAIL: docheck2 to be marked as done. This means that you claim that the problem has been dealt

Bug#921351: [pkg-go] Bug#921351: prometheus-postfix-exporter: Init script missing

It's not the FTP Team's job to fix policy compliance issues in packages. If you have a problem with that being a policy must, then you should take it up with the policy team. I completely understand the frustration, but in my own packages I take the time to do it because Debian policy says

Bug#921473: [deb...@kitterman.com: Bug#921473: calibre: Invalid maintainer address]

Hi all On Tue, 05 Feb 2019, Nicholas D Steeves wrote: > Shall I update d/control to use "Norbert Preining > "? If not, I'll need to move the salsa project > to a new namespace--either collab-maint or my own. Please see https://github.com/norbusan/calibre-debian which has all these changes,

Processed: Re: Bug#921510: [Debichem-devel] Bug#921510: qutemol: segfaults at startup when compiled with GCC 8

Processing control commands: > tags -1 patch Bug #921510 [src:qutemol] qutemol: segfaults at startup when compiled with GCC 8 Added tag(s) patch. -- 921510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#921510: [Debichem-devel] Bug#921510: qutemol: segfaults at startup when compiled with GCC 8

Control: tags -1 patch On Wed, Feb 06, 2019 at 08:50:21PM +0200, Graham Inggs wrote: > Commenting out AOgpu2::init() avoids the problem with GCC 8 and so far > I haven't noticed any side-effects. > > --- a/src/Common.cpp > +++ b/src/Common.cpp > @@ -1054,7 +1054,7 @@ >if (!shadowmap.init())

Bug#921553: marked as done (python{,3}-xopen: missing dependencies)

Your message dated Wed, 06 Feb 2019 21:52:33 + with message-id and subject line Bug#921553: fixed in python-xopen 0.5.0-2 has caused the Debian Bug report #921553, regarding python{,3}-xopen: missing dependencies to be marked as done. This means that you claim that the problem has been dealt

Bug#921274: teeworlds: baseline violation on i386

On Sun, 03 Feb 2019 22:35:22 +0200 Adrian Bunk wrote: > Source: teeworlds > Version: 0.7.2-2 > Severity: serious > Tags: patch > > SSE is not part of the i386 baseline, fix attached. Could you go into more detail why this is release-critical and what issue we are trying to solve? Markus

Bug#920711: marked as done (r-cran-repr: autopkgtest regression)

Your message dated Wed, 06 Feb 2019 21:34:27 + with message-id and subject line Bug#920711: fixed in r-cran-repr 0.19.2-1 has caused the Debian Bug report #920711, regarding r-cran-repr: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt

Bug#920712: marked as done (r-cran-repr: autopkgtest regression)

Your message dated Wed, 06 Feb 2019 21:34:27 + with message-id and subject line Bug#920711: fixed in r-cran-repr 0.19.2-1 has caused the Debian Bug report #920711, regarding r-cran-repr: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt

Processed: affects 919231

Processing commands for cont...@bugs.debian.org: > affects 919231 salt-master Bug #919231 [systemd] CacheDirectory/StateDirectory does not change owner/group Added indication that 919231 affects salt-master > thanks Stopping processing here. Please contact me if you need assistance. -- 919231:

Bug#921351: [pkg-go] Bug#921351: prometheus-postfix-exporter: Init script missing

Can you provide a patch if you care about sysvinit please? The Go packaging team is pretty manpower-constrained and non-systemd is a niche case, so any help is appreciated. Thanks! On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman wrote: > Package: prometheus-postfix-exporter > Version: 0.1.2-1 >

Bug#920645: marked as done (libgd2: CVE-2019-6977)

Your message dated Wed, 06 Feb 2019 20:49:57 + with message-id and subject line Bug#920645: fixed in libgd2 2.2.5-5.1 has caused the Debian Bug report #920645, regarding libgd2: CVE-2019-6977 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#920728: marked as done (libgd2: CVE-2019-6978)

Your message dated Wed, 06 Feb 2019 20:49:57 + with message-id and subject line Bug#920728: fixed in libgd2 2.2.5-5.1 has caused the Debian Bug report #920728, regarding libgd2: CVE-2019-6978 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#921571: afnix FTBFS on armhf when built on arm64 hardware

Source: afnix Version: 2.9.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=afnix=armhf=2.9.2-1=1548047247=0 ... running: SEC0003.als exception : assert-error in file : SEC0003.als at or around line 113 afnix-aexec: failure SEC0003.als make[6]: ***

Bug#892288: arrayfire test crash

On i386 with the above patches (plus the gcc8 build fix from the other bug), all tests pass in the build but Test_gfor_cpu fails in the autopkgtest; I don't yet know why.

Processed: reassign 921527 to cuneiform

Processing commands for cont...@bugs.debian.org: > reassign 921527 cuneiform 1.1.0+dfsg-7 Bug #921527 [1.1.0+dfsg-7] cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el Warning: Unknown package '1.1.0+dfsg-7' Bug reassigned from package '1.1.0+dfsg-7' to 'cuneiform'. Ignoring request to alter found

Processed: severity of 921533 is serious

Processing commands for cont...@bugs.debian.org: > severity 921533 serious Bug #921533 [nvidia-cuda-dev] nvidia-cuda-dev: cannot install with uuid-dev Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 921533:

Processed: Re: Bug#921527: cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el

Processing commands for cont...@bugs.debian.org: > reassign 921527 1.1.0+dfsg-7 Bug #921527 [*cuneiform*] cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el Warning: Unknown package '*cuneiform*' Bug reassigned from package '*cuneiform*' to '1.1.0+dfsg-7'. Warning: Unknown package '1.1.0+dfsg-7' Warning:

Processed: severity of 921510 is serious

Processing commands for cont...@bugs.debian.org: > severity 921510 serious Bug #921510 [src:qutemol] qutemol: segfaults at startup when compiled with GCC 8 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 921510:

Processed: limit source to why3, tagging 921465

Processing commands for cont...@bugs.debian.org: > limit source why3 Limiting to bugs with field 'source' containing at least one of 'why3' Limit currently set to 'source':'why3' > tags 921465 + pending Bug #921465 [src:why3] why3 FTBFS: dh_install: Cannot find (any matches for)

Processed: Move to the package where it was fixed

Processing commands for cont...@bugs.debian.org: > reassign 915023 openstack-dashboard 3:14.0.0-7 Bug #915023 {Done: Michal Arbet } [python3-senlin-dashboard] openstack-dashboard: fails to install in buster along python3-senlin-dashboard Bug reassigned from package 'python3-senlin-dashboard' to

Processed: affects 921488

Processing commands for cont...@bugs.debian.org: > affects 921488 w1retap Bug #921488 [libmariadb3] libmariadb3: OpenSSL license contamination of GPL reverse-dependencies Added indication that 921488 affects w1retap > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#921558: lsb-base: killproc does not pass name parameter to start-stop-daemon

Package: lsb-base Version: 10.2018112800 Severity: serious Hello, there is a logic error in /lib/lsb/init-functions's killproc: base=${1##*/} if [ ! $pidfile ]; then name_param="--name $base --pidfile /var/run/$base.pid" else name_param="--pidfile $pidfile" fi The

Bug#918736: marked as done (libthrift-java: CVE-2018-1320)

Your message dated Wed, 06 Feb 2019 19:19:49 + with message-id and subject line Bug#918736: fixed in libthrift-java 0.9.1-2.1 has caused the Debian Bug report #918736, regarding libthrift-java: CVE-2018-1320 to be marked as done. This means that you claim that the problem has been dealt

Bug#919219: marked as done (abcm2ps: fails to build from scratch because debhelper detects the ninja build system)

Your message dated Wed, 06 Feb 2019 19:04:05 + with message-id and subject line Bug#919219: fixed in abcm2ps 8.14.2-0.2 has caused the Debian Bug report #919219, regarding abcm2ps: fails to build from scratch because debhelper detects the ninja build system to be marked as done. This means

Bug#919462: marked as done (coq FTBFS on architectures without native OCaml backends)

Your message dated Wed, 06 Feb 2019 19:05:32 + with message-id and subject line Bug#919462: fixed in coq 8.9.0-1 has caused the Debian Bug report #919462, regarding coq FTBFS on architectures without native OCaml backends to be marked as done. This means that you claim that the problem has

Bug#919235: marked as done (abcm2ps: FTBFS because debhelper uses ninja build system instead of autoconf)

Your message dated Wed, 06 Feb 2019 19:04:05 + with message-id and subject line Bug#919219: fixed in abcm2ps 8.14.2-0.2 has caused the Debian Bug report #919219, regarding abcm2ps: FTBFS because debhelper uses ninja build system instead of autoconf to be marked as done. This means that you

Processed: found 918973 in 2.1.0-2

Processing commands for cont...@bugs.debian.org: > found 918973 2.1.0-2 Bug #918973 [libtss2-udev] udev rules and created user conflict with the one shipped in trousers package Marked as found in versions tpm2-tss/2.1.0-2. > thanks Stopping processing here. Please contact me if you need

Bug#824229: Good News

You are lucky,Two Million has just been donated to you, contact: lerynnewest...@outlook.com for more details. University of Northampton: Transforming Lives and Inspiring Change www.northampton.ac.uk This e-mail is private and may be confidential and is for the

Bug#921555: ciftilib FTBFS on big endian: test failures

Source: ciftilib Version: 1.5.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=ciftilib ... 7/35 Test #7: datatype-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.dscalar.nii ..***Failed0.01 sec CMake Error at /<>/cmake/scripts/testmd5.cmake:4

Bug#918736: libthrift-java: CVE-2018-1320

Dear maintainer, I've uploaded a new version of libthrift-java, versioned as 0.9.1-2.1 to fix CVE-2018-1320. Please find attached the debdiff. Regards, Markus diff -Nru libthrift-java-0.9.1/debian/changelog libthrift-java-0.9.1/debian/changelog --- libthrift-java-0.9.1/debian/changelog

Bug#921554: sparse FTBFS on mips/mipsel: error: test 'preprocessor/predef-lp64.c' failed

Source: sparse Version: 0.6.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=sparse ... TESTpredefined macros for LP64 (preprocessor/predef-lp64.c) Using command : test-linearize -Wno-decl -m64 $file Expecting exit value: 0 error: test

Processed: python{,3}-xopen: missing dependencies

Processing control commands: > affects -1 python3-xopen Bug #921553 [python-xopen] python{,3}-xopen: missing dependencies Added indication that 921553 affects python3-xopen -- 921553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921553 Debian Bug Tracking System Contact

Bug#921553: python{,3}-xopen: missing dependencies

Package: python-xopen Version: 0.5.0-1 Severity: serious Control: affects -1 python3-xopen The following dependencies are missing for loading the module (import xopen): python-xopen: - python-pkg-resources - python-bz2file python3-xopen: - python3-pkg-resources

Processed: Re: Bug#919231: Salt-master unable to access directories

Processing commands for cont...@bugs.debian.org: > reassign 919231 systemd 240-5 Bug #919231 [salt-master] salt-master: Upgrade Stretch -> Buster: permission denied on certain files/directories Bug reassigned from package 'salt-master' to 'systemd'. No longer marked as found in versions

Bug#919231: Salt-master unable to access directories

reassign 919231 systemd 240-5 retitle 919231 CacheDirectory/StateDirectory does not change owner/group thanks Hi Stijn, your bug description was enough for me to reproduce this misbehavior and tracked it down to systemd not behaving like the documentation describes: StateDirectory=,

Bug#921549: golang-1.8: Security update of golang-1.8 breaks pieces of cgo pkg-config support

Source: golang-1.8 Version: 1.8.1-1+deb9u1 Severity: grave Dear Maintainer, with libyara-dev, libyara3, golang-github-hillu-go-yara-dev from stretch-backports, the attached trivial tool used to build fine, both with and without build tag "yara_static" which causes pkg-config to be called using

Bug#921538: Fails to start since upgrade to 1.9.0-1

Here is a merge request [*] to disable chroot'ing again like it has been since version 1.0.0-3 Regards, Simon *: https://salsa.debian.org/dns-team/unbound/merge_requests/3 signature.asc Description: OpenPGP digital signature

Bug#921450: marked as done (fetchmail: Fetchmail segfaults upon execution)

Your message dated Wed, 06 Feb 2019 17:05:03 + with message-id and subject line Bug#921450: fixed in fetchmail 6.4.0~beta4-3 has caused the Debian Bug report #921450, regarding fetchmail: Fetchmail segfaults upon execution to be marked as done. This means that you claim that the problem has

Bug#921542: tc qdisc kernel crash

Package: src:linux Version: 4.19.16-1 Severity: critical When I'm trying to use this script: #!/bin/bash ifaces[0]="tun0" ifaces[1]="ens192" ifaceIn="ifb0" ifaceOut="ifb1" #echo ${#iface[@]} #exit tc qdisc del dev $ifaceIn root for iface in ${ifaces[@]}; do echo "Delete qdisc ingress on

Bug#913843: marked as done (ruby-mail-gpg FTBFS with gpgme 1.12.0)

Your message dated Wed, 06 Feb 2019 16:51:13 + with message-id and subject line Bug#913843: fixed in ruby-mail-gpg 0.4.0-2 has caused the Debian Bug report #913843, regarding ruby-mail-gpg FTBFS with gpgme 1.12.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#920629: marked as done (volumecontrol.app: Cannot quit, blocks under some circumstances)

Your message dated Wed, 06 Feb 2019 16:41:22 + with message-id and subject line Bug#920629: fixed in volumecontrol.app 0.8-1 has caused the Debian Bug report #920629, regarding volumecontrol.app: Cannot quit, blocks under some circumstances to be marked as done. This means that you claim

Bug#921538: Fails to start since upgrade to 1.9.0-1

Hi Ryan, On 2019-02-06 11:12 a.m., Ryan Kavanagh wrote: > Since the upgrade to 1.9.0-1, unbound fails to start. Purging the > package and reinstalling does not fix the issue. The errors seem to be > due to being unable to read various configuration files. > > Feb 06 11:01:12 zeta unbound[28647]:

Processed: forcibly merging 921538 921539

Processing commands for cont...@bugs.debian.org: > forcemerge 921538 921539 Bug #921538 [unbound] Fails to start since upgrade to 1.9.0-1 Bug #921539 [unbound] unbound fails to start after upgrade Merged 921538 921539 > thanks Stopping processing here. Please contact me if you need assistance.

Bug#921539: unbound fails to start after upgrade

Package: unbound Version: 1.9.0-1 Severity: grave Justification: renders package unusable Immediately after installing 1.9.0-1, unbound refused to run after restart. System logs contained: Feb 6 11:00:24 annuminas package-helper[6142]: /var/lib/unbound/root.key has content Feb 6 11:00:24

Bug#921538: Fails to start since upgrade to 1.9.0-1

Package: unbound Version: 1.9.0-1 Severity: grave Since the upgrade to 1.9.0-1, unbound fails to start. Purging the package and reinstalling does not fix the issue. The errors seem to be due to being unable to read various configuration files. Feb 06 11:01:12 zeta unbound[28647]: [28647:0]

Bug#911515: dvtm in backports

On 2019-01-17 21:28 +, Dmitry Bogatov wrote: > Hello? Hello. Apologies for not replying sooner. Your mail from October[1] never reached me, and during the past three weeks I have been rather ill. > Dear maintainer of ncurses, could you please upload a backport of > ncurses-term? I am

Bug#907718: marked as done (python-dateutil: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware)

Your message dated Wed, 06 Feb 2019 15:06:30 + with message-id and subject line Bug#907718: fixed in python-dateutil 2.7.3-3 has caused the Debian Bug report #907718, regarding python-dateutil: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware to be marked as done.

Bug#918378: marked as done (Wrong path to binary in systemd unit)

Your message dated Wed, 06 Feb 2019 15:06:59 + with message-id and subject line Bug#918378: fixed in qemu 1:3.1+dfsg-3 has caused the Debian Bug report #918378, regarding Wrong path to binary in systemd unit to be marked as done. This means that you claim that the problem has been dealt

Bug#921284: build-using should only include copylefted files

On 2019-02-03 17:21:35, Antoine Beaupre wrote: > My first submissions for the dmarc-cat package (#920385) were refused > by the FTP masters because the built-using field did not respect §7.8 > of the Debian policy. That's actually inaccurate: the package was refused because the dependencies

Processed: Re: Bug#921495: libbio-perl-perl: Package not upgradable, file conflicts.

Processing control commands: > severity -1 serious Bug #921495 [libbio-perl-perl] libbio-perl-perl: Package not upgradable, file conflicts. Severity set to 'serious' from 'normal' -- 921495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921495 Debian Bug Tracking System Contact

Processed: severity of 899304 is important

Processing commands for cont...@bugs.debian.org: > severity 899304 important Bug #899304 [bareos-storage] bareos-storage will not start after upgrade to 16.2.6-4 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 899304:

Bug#921450: Info received (Bug#921450: (no subject))

Control: tags -1 confirmed upstream fixed-upstream -moreinfo -unreproducible This got fixed in upstream Git as of commit 8c57ec38ae327fcd648569acc915f47f0eb2547d - please cherry-pick this. https://gitlab.com/fetchmail/fetchmail/commit/8c57ec38ae327fcd648569acc915f47f0eb2547d

Processed: Re: Bug#921450: Info received (Bug#921450: (no subject))

Processing control commands: > tags -1 confirmed upstream fixed-upstream -moreinfo -unreproducible Bug #921450 [fetchmail] fetchmail: Fetchmail segfaults upon execution Added tag(s) fixed-upstream, confirmed, and upstream. Bug #921450 [fetchmail] fetchmail: Fetchmail segfaults upon execution

Bug#914537: openmw: segfault at start

Hi Bret, Am 06.02.19 um 11:43 schrieb psi...@gmail.com: > Hello! > > Hot off the presses, OpenMW 0.45.0 > https://salsa.debian.org/games-team/openmw > > I built it against buster and sid, tested both and ran without segfaults. > This should wrap up this bug (closes in changelog entry). > >

Bug#914537: marked as done (openmw: segfault at start)

Your message dated Wed, 06 Feb 2019 13:08:31 + with message-id and subject line Bug#914537: fixed in openmw 0.45.0-1 has caused the Debian Bug report #914537, regarding openmw: segfault at start to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#921521: chromium-browser: CVE/Security fixes missing in stable-sec

Package: chromium Version: 71.0.3578.80-1~deb9u1 Severity: serious The stable-sec package is stuck with version 71.0.3578.80 and is missing security updates for several CVEs. Take for example the list from 72.0.3626.81 - Stack buffer overflow in Skia. Reported by Ivan Fratric - Use after free

Bug#915657: marked as done (google-android-installers NMU binaries cannot be installed due to unchanged version of the binary packages)

Your message dated Wed, 06 Feb 2019 12:50:09 + with message-id and subject line Bug#915657: fixed in google-android-installers 1472023576+nmu3 has caused the Debian Bug report #915657, regarding google-android-installers NMU binaries cannot be installed due to unchanged version of the binary

  1   2   >