Bug#922497: BUG: unable to handle kernel paging request at ffff9b30a7cb488

[Allan Wind]

Package: nvidia-driver
Version: 390.87-8~deb9u1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

The stable release 9.8 contained an upgrade of nvidia-drivers from 
384.130-1 to 390.87-8~deb9u1 which caused my system hang during
subsequent boots.  The release also contains a linux-image 
update, and I installed a known working kernel (4.9.0-5) and it 
too failed to boot with 390.87-8~deb9u1. Then I upgraded 
nividia-driver to the version in unstable, and I was able to boot 
my system.  Unfortunately, this is the version information being 
picked up in this bug report.


Here are an overview of the relevant traces from the crash with 
linux-image-4.9.0-8-amd64:amd64 4.9.144-3

and nvidia-driver 390.87-8~deb9u1:

2019-02-17T04:46:15.746+00:00 vent kernel: BUG: unable to handle kernel paging 
request at 9b30a7cb4880
2019-02-17T04:47:10.146+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 23s! [ps:1177]
2019-02-17T04:48:04.181+00:00 vent kernel: BUG: unable to handle kernel paging 
request at 9dab95bae880
2019-02-17T04:48:54.181+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 23s! [ps:1164]
2019-02-17T04:49:22.181+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 23s! [ps:1164]
2019-02-17T04:49:58.181+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 22s! [ps:1164]
2019-02-17T04:50:26.181+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 22s! [ps:1164]
2019-02-17T04:51:02.181+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 22s! [ps:1164]
2019-02-17T04:51:30.181+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 22s! [ps:1164]
2019-02-17T04:52:06.181+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 22s! [ps:1164]
2019-02-17T04:52:34.181+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 23s! [ps:1164]
2019-02-17T04:53:06.181+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 22s! [ps:1164]
2019-02-17T04:58:46.294+00:00 vent kernel: BUG: unable to handle kernel paging 
request at 975a15bcc880
2019-02-17T04:59:37.347+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#5 stuck for 23s! [ps:1141]
2019-02-17T05:06:03.643+00:00 vent kernel: BUG: unable to handle kernel paging 
request at 9f8e15cdf880
2019-02-17T05:06:55.244+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#7 stuck for 23s! [ps:1137]
2019-02-17T05:07:23.244+00:00 vent kernel: NMI watchdog: BUG: soft lockup - 
CPU#7 stuck for 22s! [ps:1137]

and some selected traces:

2019-02-17T04:46:15.746+00:00 vent kernel: BUG: unable to handle kernel paging 
request at 9b30a7cb4880
2019-02-17T04:46:15.746+00:00 vent kernel: IP: [] 
_nv015088rm+0x614/0x780 [nvidia]
2019-02-17T04:46:15.746+00:00 vent kernel: PGD f5df34067 
2019-02-17T04:46:15.746+00:00 vent kernel: PUD 0 
2019-02-17T04:46:15.746+00:00 vent kernel: 
2019-02-17T04:46:15.746+00:00 vent kernel: Oops:  [#1] SMP

2019-02-17T04:46:15.746+00:00 vent kernel: Modules linked in: snd_seq_midi 
snd_seq_midi_event uvcvideo snd_usb_audio videobuf2_vmalloc hid_generic 
videobuf2_memops videobuf2_v4l2 videobuf2_core snd_usbmidi_lib snd_rawmidi 
videodev btusb btrtl media btbcm btintel bluetooth usbhid snd_hrtimer snd_seq 
snd_seq_device binfmt_misc nls_ascii nls_cp437 vfat fat arc4 thinkpad_acpi 
nvram intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_codec_realtek snd_hda_codec_generic kvm_intel iwlmvm 
i2c_designware_platform kvm i2c_designware_core irqbypass crct10dif_pclmul 
crc32_pclmul mac80211 snd_hda_intel efi_pstore joydev ghash_clmulni_intel 
pcspkr snd_hda_codec serio_raw efivars iwlwifi snd_hda_core snd_hwdep snd_pcm 
rtsx_pci_ms iTCO_wdt snd_timer iTCO_vendor_support snd soundcore idma64 
cfg80211 memstick mei_me rfkill mei intel_lpss_pci
2019-02-17T04:46:15.746+00:00 vent kernel:  intel_lpss shpchp battery ac evdev 
acpi_pad nvidia_drm(PO) drm_kms_helper drm nvidia_modeset(PO) nvidia(PO) 
ipmi_msghandler parport_pc ppdev lp parport efivarfs ip_tables x_tables autofs4 
ext4 crc16 jbd2 crc32c_generic fscrypto ecb mbcache rtsx_pci_sdmmc mmc_core 
crc32c_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd 
psmouse e1000e ptp i2c_i801 xhci_pci pps_core i2c_smbus rtsx_pci xhci_hcd nvme 
mfd_core nvme_core usbcore usb_common thermal wmi video i2c_hid hid button
2019-02-17T04:46:15.750+00:00 vent kernel: CPU: 5 PID: 704 Comm: irq/327-nvidia 
Tainted: P   O4.9.0-8-amd64 #1 Debian 4.9.144-3
2019-02-17T04:46:15.750+00:00 vent kernel: Hardware name: LENOVO 
20HHCTO1WW/20HHCTO1WW, BIOS N1UET37W (1.11 ) 07/24/2017
2019-02-17T04:46:15.750+00:00 vent kernel: task: 9b1ca9d9f080 task.stack: 
c1a8d0a1c000
2019-02-17T04:46:15.750+00:00 vent kernel: RIP: 0010:[]  
[] _nv015088rm+0x614/0x780 [nvidia]
2019-02-17T04:46:15.750+00:00 vent kernel: RSP: 0018:c1a8d0a1fcc8  EFLAGS: 
00010246

Bug#919058: itstool bug bisection

[Lars Skovlund]

Redhat now have this bug in their bug tracker. Given that the itstool author 
seems to
either be or have been a Redhat employee at some point, I guess this is good.

https://bugzilla.redhat.com/show_bug.cgi?id=1677838

Bug#921637: [pkg-go] Bug#921637: FTBFS: /usr/lib/ruby/vendor_ruby/ronn/roff.rb:165:in `block_filter': undefined method

[Andrew Janke]

I've confirmed this is the https://github.com/apjanke/ronn-ng/issues/24 
bug in ronn-ng.


It looks liike an easy fix and I have pushed a ronn-ng 0.8.1.beta.1 
gem/release with the fix. Are you able to test against a prerelease gem?


I've tested locally and it fixed the problem for git-lfs man generation. 
I've also added an ordered-list example to Ronn-NG's internal test suite.


Cheers,
Andrew

Bug#922420: got an unexpected keyword argument 'bg'

[Ben Finney]

On 15-Feb-2019, Enrico Zini wrote:
> It looks like --background has been added to the command line
> parser, but not to the function arguments to which the command line
> parser result is sent.

The code changes from version “1.2” → “1.4” includes a bunch of
changes related to the ‘--background’ option. The change log
unfortunately does not describe what behaviour change this is meant to
have.

So maybe, though upstream has not described any change to this effect,
the bug has been fixed? Can you try again with version “1.4-1”, now in
Debian?

-- 
 \  “People demand freedom of speech to make up for the freedom of |
  `\   thought which they avoid.” —Soren Aabye Kierkegaard (1813–1855) |
_o__)  |
Ben Finney 

signature.asc
Description: PGP signature

Bug#921637: [pkg-go] Bug#921637: FTBFS: /usr/lib/ruby/vendor_ruby/ronn/roff.rb:165:in `block_filter': undefined method

[Andrew Janke]

Hi folks. ronn-ng maintainer here. I've prioritized this bug since it's 
causing problems for Debian package builds.


Cheers,
Andrew Janke

Bug#922489: qtkeychain: relies on existence of libsecret-1.so -dev symlink

[Simon McVittie]

Control: reassign -1 qtkeychain 0.9.1-1
Control: retitle -1 qtkeychain: relies on existence of libsecret-1.so -dev 
symlink

On Sun, 17 Feb 2019 at 00:21:55 +0100, Sandro Knauß wrote:
> qtkeychain is using libsecret as a backend to request passwords. ldd is
> showing me that it is linked against libsecret-1.so.0 (fine). But strace
> shows one sucessfull read of libsecret-1.so.0 (fine) but afterwards, it
> tries to load libsecret-1.so without success (as libsecret-1-dev is not
> installed). If I create this symlink from libsecret-1.so ->
> libsecret-1.so, qtkeychain can load/store successfully passwords.

Sorry, this is not how shared libraries are packaged in
Debian. libsecret-1-0 must not contain the libsecret-1.so symlink. If it
did, it would not be co-installable with a future libsecret-1-1, defeating
a large part of the purpose of having an ABI version in the name.
(See Debian Policy §8.)

> For me this looks like an error in libsecret, as qtkeychain only imports
> libsecret/secret.h in libsecret.cpp [0]. Or maybe the usage in that file
> is wrong or cmake screws things up...

I think this is a qtkeychain bug. This code that appears to be responsible
for dlopen()ing libsecret:

LibSecretKeyring::LibSecretKeyring()
: QLibrary("secret-1")

doesn't mention the ABI version, so it could equally easily end up loading
an incompatible future library libsecret-1.so.1 or libsecret-1.so.27,
and then crashing when it calls a function by assuming that it has the
same ABI as the corresponding function in libsecret-1.so.0.

I haven't programmed against Qt for years, but the documentation
suggest that it should probably inherit from QLibrary("secret-1", 0)
as described at ,
so that Qt will specifically load libsecret-1.so.0 on Unix platforms.

smcv

Processed: Re: Bug#922489: qtkeychain: relies on existence of libsecret-1.so -dev symlink

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 qtkeychain 0.9.1-1
Bug #922489 [libsecret-1-0] libsecret-1-0: needs symlink to libsecret-1.so
Bug reassigned from package 'libsecret-1-0' to 'qtkeychain'.
No longer marked as found in versions libsecret/0.18.7-1.
Ignoring request to alter fixed versions of bug #922489 to the same values 
previously set
Bug #922489 [qtkeychain] libsecret-1-0: needs symlink to libsecret-1.so
There is no source info for the package 'qtkeychain' at version '0.9.1-1' with 
architecture ''
Unable to make a source version for version '0.9.1-1'
Marked as found in versions 0.9.1-1.
> retitle -1 qtkeychain: relies on existence of libsecret-1.so -dev symlink
Bug #922489 [qtkeychain] libsecret-1-0: needs symlink to libsecret-1.so
Changed Bug title to 'qtkeychain: relies on existence of libsecret-1.so -dev 
symlink' from 'libsecret-1-0: needs symlink to libsecret-1.so'.

-- 
922489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#922489: libsecret-1-0: needs symlink to libsecret-1.so

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #922489 [libsecret-1-0] libsecret-1-0: needs symlink to libsecret-1.so
Severity set to 'serious' from 'normal'
> affects -1 libqt5keychain
Bug #922489 [libsecret-1-0] libsecret-1-0: needs symlink to libsecret-1.so
Added indication that 922489 affects libqt5keychain

-- 
922489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#922488: linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation

[Ralf Jung]

Oh, I should probably also mention that these machines all run an extra kernel
module compiled via dkms: batman-adv 2019.0 from .
The same kernel module also runs on a fourth machine with the same setup, but
which hasn't gotten the kernel update yet, and that machine runs stable.

; Ralf

Bug#922488: linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation

[Ralf Jung]

Package: linux-image-4.9.0-8-amd64
Version: 4.9.144-3
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

after installing the kernel updates that got released to Debian stable earlier
today or yesterday, we saw all the three updated systems fail in the same way:
after 3-5h, they stop responding. We managed to grab a picture of the kernel
console on one of them, which showed a kernel panic in the IPv6 stack:

  https://imgur.com/7Teb8BV

The topmost stack items are (hoping I got no typos)

  __pskb_pull_tail
  ip6_dst_lookup_tail
  _decode_session6
  __xfrm_decode_session
  icmpv6_route_lookup
  icmp6_send

That system was using the kernel this bug is reported against 
(linux-image-4.9.0-8-amd64 4.9.144-3).
The other two affected systems used a backports kernel instead 
(linux-image-4.19.0-0.bpo.2-amd65 4.19.16-1~bpo9+1).
Unfortunately we have no console access there, all we can do there is a hard 
reboot from the web interface.

These servers are all operating as gateway servers for our Freifunk network, 
meaning they mostly forward traffic and their network setup is very 
non-standard.
Please let me know if there is any configuration details that would be helpful 
to track this down.

Kind regards,
Ralf

Bug#908427: marked as done (nzbget depends on libjs-twitter-bootstrap that will not be in buster)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 22:07:48 +
with message-id 
and subject line Bug#908427: fixed in nzbget 21.0~r2296+dfsg-1
has caused the Debian Bug report #908427,
regarding nzbget depends on libjs-twitter-bootstrap that will not be in buster
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
908427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nzbget
Version: libjs-twitter-bootstrap
Severity: serious
Control: block 907724 by -1

See #907724 for background.
--- End Message ---
--- Begin Message ---
Source: nzbget
Source-Version: 21.0~r2296+dfsg-1

We believe that the bug you reported is fixed in the latest version of
nzbget, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Moog  (supplier of updated nzbget package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 21:44:55 +0100
Source: nzbget
Architecture: source
Version: 21.0~r2296+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Andreas Moog 
Changed-By: Andreas Moog 
Closes: 908427
Changes:
 nzbget (21.0~r2296+dfsg-1) experimental; urgency=medium
 .
   * New upstream development version
   * Use bundled bootstrap 2.0.3 for Web UI (Closes: #908427)
 Will use Debian's bootstrap 3 when nzbget supports it
Checksums-Sha1:
 1ad5a36a552e0f9de8f9a3b4e958af4fc52763c9 2010 nzbget_21.0~r2296+dfsg-1.dsc
 a7f53161d3c3d6696e2362af68109c7e9fb270df 1099572 
nzbget_21.0~r2296+dfsg.orig.tar.xz
 eafde2db8446467e566101187969c090bece4855 27476 
nzbget_21.0~r2296+dfsg-1.debian.tar.xz
 21b0147c012fc1aec553822cc2ba52a446fdb0d4 6717 
nzbget_21.0~r2296+dfsg-1_source.buildinfo
Checksums-Sha256:
 c3c91f9b7ba11ac2076904b577cb492e8b61e073458fde57ea80c164ef14bf3a 2010 
nzbget_21.0~r2296+dfsg-1.dsc
 2dda5f3350882af71300a955db4f931e4f5f9e2c5a376adf11e8a399a8f585e9 1099572 
nzbget_21.0~r2296+dfsg.orig.tar.xz
 7f980743eee6535ef24cab8f397b0564523023f4807e0429fb259465ca0a 27476 
nzbget_21.0~r2296+dfsg-1.debian.tar.xz
 d4c2f35c8e59b47a02afdaa81213ee9353543d532934bc7f7c401b49967bd75a 6717 
nzbget_21.0~r2296+dfsg-1_source.buildinfo
Files:
 30e44429d4a74964982ab708a5db9244 2010 net optional nzbget_21.0~r2296+dfsg-1.dsc
 d5881f250bb688f5502bee4cb2d7f1b8 1099572 net optional 
nzbget_21.0~r2296+dfsg.orig.tar.xz
 faee8319ee3e88674886e79d8f7405cb 27476 net optional 
nzbget_21.0~r2296+dfsg-1.debian.tar.xz
 a14a2e6ec3e18bb4fe107afe02be3475 6717 net optional 
nzbget_21.0~r2296+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJOBAEBCgA4FiEEdM3Z/lvL/g0T7o7qYfNEJnTeZiQFAlxohdEaHGFuZHJlYXMu
bW9vZ0B3YXJwZXJiYnMuZGUACgkQYfNEJnTeZiTscBAAoLF/fAO8At6LSK6RjM//
7jVogVvGQwaZJuwSgSdXjXtHDwwEhWH8Yb9GYaK9M/to9XSPf4CxMbcWSyKjIX31
JDWl/Dz2T88ctpR7mavv0u/Ht/4mj9KttxKn3N+XYLlAVKiGS+drKlmMzACcVdaX
1V0V7H7h+i1erJY+iNBe+ype/dYUQ6oo80PMMqbr6x5KkFLJUsCWxuiwBkfZovQs
io51Cwd2SttwCvlb0/GXKkUed47ILgyj/nB4p+/+rDXz3cN6n3e8N2rowoUeF9b8
5VnRyzywKKzQLNTRpc+9Hp2zqlFJqBO3vB/UHzhChf+hN8irXtxWMF65q8wd/Iwi
UIPkZuc2cs+tO3bredOc2gLKKL2gu/1sWCTLzu080RkgkVDT2XxQBRQ7RKl9qA2l
RDUKw/eKn/2YKkRvUUP5KnoeT5ksh+0S9W5oEjmyrEF5rvwiVz/OqhwSgXj0soZ4
Dw5rXG9lrxYm2XiOPK6dOd76WwCUtPyQi1peJxc2uH1cD51N+ZM6p/JDUGoZR4UF
zJ1twvDSyy4dzRRngQPXH1ncQku/qykUr3KMOYwbG3kQ1CK2AuU0Y2b4FFyPqEup
oxpaMlq99FtQOaoCJXfK6/hxNfQykFQ3jp5q0R0DvZjJKGLLaKZDXhSdi8R9whEe
XzIvlml9FeSQ4x/wH+Usw6I=
=B/kE
-END PGP SIGNATURE End Message ---

Bug#919461: marked as done (ssreflect FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 21:36:29 +
with message-id 
and subject line Bug#919461: fixed in ssreflect 1.7.0+dfsg-1
has caused the Debian Bug report #919461,
regarding ssreflect FTBFS in unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
919461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ssreflect
Version: 1.6.1-3
Severity: serious
Tags: sid buster

[...]
   debian/rules override_dh_auto_install
make[1]: Entering directory '/home/packages/tmp/ssreflect-1.6.1'
/usr/bin/make -C mathcomp
make[2]: Entering directory '/home/packages/tmp/ssreflect-1.6.1/mathcomp'
Generating Makefile.coq for Coq v8.8 with COQBIN=/usr/bin/
# Override COQDEP to find only the "right" copy .ml files
COQDEP VFILES
*** Warning: in file ssreflect/ssreflect.v, library ssrmatching is required and
has not been found in the loadpath!
*** Warning: in file ssreflect/ssreflect.v, declared ML module ssreflect_plugin
has not been found!
*** Warning: in file ssreflect/ssreflect.v, library ssrmatching is required and
has not been found in the loadpath!
*** Warning: in file ssreflect/ssreflect.v, declared ML module ssreflect_plugin
has not been found!
COQC ssreflect/ssreflect.v
File "./ssreflect/ssreflect.v", line 4, characters 15-26:
Error: Unable to locate library ssrmatching.

make[4]: *** [Makefile.coq:657: ssreflect/ssreflect.vo] Error 1
make[3]: *** [Makefile.coq:318: all] Error 2
make[2]: *** [Makefile:26: all] Error 2
make[2]: Leaving directory '/home/packages/tmp/ssreflect-1.6.1/mathcomp'
make[1]: *** [debian/rules:41: override_dh_auto_install] Error 2
make[1]: Leaving directory '/home/packages/tmp/ssreflect-1.6.1'
make: *** [debian/rules:22: binary] Error 2
--- End Message ---
--- Begin Message ---
Source: ssreflect
Source-Version: 1.7.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
ssreflect, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated ssreflect package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 16 Feb 2019 20:06:49 +0100
Source: ssreflect
Architecture: source
Version: 1.7.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Closes: 919461
Changes:
 ssreflect (1.7.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version. This fixes a FTBFS with coq 8.9.0 (closes: #919461)
 Repack upstream (remove docs/htmldoc/js/)
   * Update debian/watch to github
   * Update Vcs-* to salsa
   * Standards-Version 4.3.0
 - https in format string of debian/copyright
   * d/rules: fix installation of htmldocs
   * Drop packages libssreflect-ocaml[-dev] as the plugin is now included in
 the coq package.
   * d/libssreflect-coq.docs: adjust pathnames of files
   * d/copyright: drop short paragraph at first occurrence of CeCILL-B
   * Build-depend on debhelper-compat (=12)
 - use dh_missing (instead of dh_install) with --fail-missing
   * No more compilation with ocaml:
 - dropped build-dependencies on ocaml stuff
 - dropped --with-ocaml flag to dh and usage of ocamlvars.mk
   * Updated short and long description. Thanks to Enrico Tassi.
   * Added an as-installed test, thanks again to Enrico Tassi.
   * Added myself as Uploader.
Checksums-Sha1:
 8e27be1770334396e3cf8662f7665d76d53ca61b 2114 ssreflect_1.7.0+dfsg-1.dsc
 85cc33d95fe976dd29c308491d3a68c7bb8197b3 4039037 
ssreflect_1.7.0+dfsg.orig.tar.gz
 8a8a311eb049d1e0fbdd6f247b692082a57318d5 12252 
ssreflect_1.7.0+dfsg-1.debian.tar.xz
 3bb1a170b982101f19e0940298803fbbec74f471 6090 
ssreflect_1.7.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 9c93e1d8af1b64d97091548237527e791c148799ac1e1f9a0bde8cf8c01045b2 2114 
ssreflect_1.7.0+dfsg-1.dsc
 2ed4db186ae03f7a2f48c72a30efbe31643a83937b58865db0ea2f03547aaf50 4039037 
ssreflect_1.7.0+dfsg.orig.tar.gz
 2755526e153910a793a99cd07f477680af65a125b201ce87fa2715cc70ddc7af 12252 
ssreflect_1.7.0+dfsg-1.debian.tar.xz
 

Bug#922455: marked as done (pinfo: malloc(): invalid size (unsorted))

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 21:09:29 +
with message-id 
and subject line Bug#922455: fixed in pinfo 0.6.13-1
has caused the Debian Bug report #922455,
regarding pinfo: malloc(): invalid size (unsorted)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
922455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: pinfo
Version: 0.6.12-2
Severity: grave

pinfo doesn't start:

  $ pinfo
  Przemek's Info Viewer v0.6.12
  malloc(): invalid size (unsorted)
  Aborted

Valgrind suggests some memory corruption happened:

  Syscall param stat64(file_name) points to unaddressable byte(s)
 at 0x49FE605: __xstat64@@GLIBC_2.2 (xstat64.c:35)
 by 0x10DCD3: stat (stat.h:455)
 by 0x10DCD3: initpaths (filehandling_functions.c:1042)
 by 0x10AAE8: main (pinfo.c:248)
   Address 0x0 is not stack'd, malloc'd or (recently) free'd

  Invalid write of size 4
 at 0x10DE6A: initpaths (filehandling_functions.c:1051)
 by 0x10AAE8: main (pinfo.c:248)
   Address 0x4b008a8 is 0 bytes after a block of size 96 alloc'd
 at 0x4836A16: calloc (in 
/usr/lib/i386-linux-gnu/valgrind/vgpreload_memcheck-x86-linux.so)
 by 0x118C69: xmalloc (utils.c:110)
 by 0x10DC7F: initpaths (filehandling_functions.c:1036)
 by 0x10AAE8: main (pinfo.c:248)

  Invalid write of size 4
 at 0x10DE70: initpaths (filehandling_functions.c:1051)
 by 0x10AAE8: main (pinfo.c:248)
   Address 0x4b008ac is 4 bytes after a block of size 96 alloc'd
 at 0x4836A16: calloc (in 
/usr/lib/i386-linux-gnu/valgrind/vgpreload_memcheck-x86-linux.so)
 by 0x118C69: xmalloc (utils.c:110)
 by 0x10DC7F: initpaths (filehandling_functions.c:1036)
 by 0x10AAE8: main (pinfo.c:248)

  ...


-- System Information:
Architecture: i386

Versions of packages pinfo depends on:
ii  libc6 2.28-7
ii  libncursesw6  6.1+20181013-2
ii  libreadline7  7.0-5
ii  libtinfo6 6.1+20181013-2
ii  install-info  6.5.0.dfsg.1-4+b1

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: pinfo
Source-Version: 0.6.13-1

We believe that the bug you reported is fixed in the latest version of
pinfo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 922...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Zoetekouw  (supplier of updated pinfo package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 21:28:19 +0100
Source: pinfo
Architecture: source
Version: 0.6.13-1
Distribution: sid
Urgency: medium
Maintainer: Bas Zoetekouw 
Changed-By: Bas Zoetekouw 
Closes: 922455
Changes:
 pinfo (0.6.13-1) sid; urgency=medium
 .
   * New upstream release
 - Fix crash on some architectures (Closes: #922455)
   * Remove patch 
0001-Fix-signed-unsigned-comparisons-causing-Wsign-compar.patch
 (included in upstream)
Checksums-Sha1:
 f43997bb0b32a06cb12b210eefa07a575990f95c 1774 pinfo_0.6.13-1.dsc
 3dbb3b756f3ae88b748b07fe76e1616b0510a9fd 157103 pinfo_0.6.13.orig.tar.gz
 800e13bbcfc0ab71d08ae0801971ca0dd77b4633 7416 pinfo_0.6.13-1.debian.tar.xz
 d9d9385fe0a9e013be12b1e49a8e692b5e5fd474 6436 pinfo_0.6.13-1_amd64.buildinfo
Checksums-Sha256:
 f0e6e024bdfe23a64dd170f236eb100f62aa16c2b4e25430b5759cdbdabea867 1774 
pinfo_0.6.13-1.dsc
 9dc5e848a7a86cb665a885bc5f0fdf6d09ad60e814d75e78019ae3accb42c217 157103 
pinfo_0.6.13.orig.tar.gz
 28d6fab51f29a7cac0159a90867591a6c77a1444770b7626240915eb230a8015 7416 
pinfo_0.6.13-1.debian.tar.xz
 f1affac1c4cf0980905f77d2393910c2d4585a847e08f92c0ecb2b0ac3d80198 6436 
pinfo_0.6.13-1_amd64.buildinfo
Files:
 ee7d9da1a375ecca2695e0dc79d77877 1774 doc optional pinfo_0.6.13-1.dsc
 b2671c8f6ef0aa5d7c6460c3111e2f50 157103 doc optional pinfo_0.6.13.orig.tar.gz
 485af81908790cc399f431000cf4af2c 7416 doc optional pinfo_0.6.13-1.debian.tar.xz
 2a763c90bb72c77a2bb914c1ee0f51c5 6436 doc optional 
pinfo_0.6.13-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEghC4pFfxxgR8lpr/0YOlF7+pjeYFAlxodSUPHGJhc0BkZWJp
YW4ub3JnAAoJENGDpRe/qY3myTkP/3aneN8pTpTILiQiZ8iQ9vdYCBOTmUVQOLNL
r9Z8v+EGXkP4JHQW50j2/EQ4og9iDdU6QF+GswLLOUxA4ApHFsXxJFWyHtt2URHy

Bug#921900: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:27:41 +
with message-id 
and subject line Bug#921899: fixed in rt-extension-calendar 1.01-1.1
has caused the Debian Bug report #921899,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-smsnotify
Version: 1.04-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
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc . /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" 
returned exit code 2
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-smsnotify.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: rt-extension-calendar
Source-Version: 1.01-1.1

We believe that the bug you reported is fixed in the latest version of
rt-extension-calendar, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated rt-extension-calendar 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:14:45 CET
Source: rt-extension-calendar
Binary: rt4-extension-calendar
Architecture: source
Version: 1.01-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: gregor herrmann 
Description: 
 rt4-extension-calendar - Calendar view for Request Tracker 4
Closes: 921899
Changes:
 rt-extension-calendar (1.01-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dominic Hargreaves ]
   * Update Vcs-* fields to point to Salsa
 .
   [ gregor herrmann ]
   * Add libcapture-tiny-perl to Build-Depends-Indep. (Closes: #921899)
Checksums-Sha256: 
 dc6be3a6ffb541e127e31ca1c488edbd64d909b14083e8a4aef845e6a2583157 2392 
rt-extension-calendar_1.01-1.1.dsc
 32b6756518303fed701303dd5dddcd487e8d2de7ea7da47bd626cc863b476717 2164 
rt-extension-calendar_1.01-1.1.debian.tar.xz
 

Bug#921804: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:27:41 +
with message-id 
and subject line Bug#921899: fixed in rt-extension-calendar 1.01-1.1
has caused the Debian Bug report #921899,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-jsgantt
Version: 1.03-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
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
rm -rf inc/Module
for ver in 4; do \
 perl Makefile.PL INSTALLDIRS=vendor; \
 mv Makefile Makefile$ver; \
done
Cannot determine perl version info from lib/RT/Extension/JSGantt.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
mv: cannot stat 'Makefile': No such file or directory
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-jsgantt.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: rt-extension-calendar
Source-Version: 1.01-1.1

We believe that the bug you reported is fixed in the latest version of
rt-extension-calendar, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated rt-extension-calendar 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:14:45 CET
Source: rt-extension-calendar
Binary: rt4-extension-calendar
Architecture: source
Version: 1.01-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: gregor herrmann 
Description: 
 rt4-extension-calendar - Calendar view for Request Tracker 4
Closes: 921899
Changes:
 rt-extension-calendar (1.01-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dominic Hargreaves ]
   * Update Vcs-* fields to point to Salsa
 .
   [ gregor herrmann ]
   * Add libcapture-tiny-perl to Build-Depends-Indep. (Closes: #921899)
Checksums-Sha256: 
 dc6be3a6ffb541e127e31ca1c488edbd64d909b14083e8a4aef845e6a2583157 2392 
rt-extension-calendar_1.01-1.1.dsc
 32b6756518303fed701303dd5dddcd487e8d2de7ea7da47bd626cc863b476717 2164 
rt-extension-calendar_1.01-1.1.debian.tar.xz
 7dbcfa1960ee85bc28a26a963b98e951006de2a4a2507e64fbbf4aeacb823344 16470 
rt-extension-calendar_1.01-1.1_sourceonly.buildinfo
Checksums-Sha1: 
 bf7241279a94ca58e21b6dced9e249ca098730c3 2392 
rt-extension-calendar_1.01-1.1.dsc
 

Bug#922391: marked as done (isso: (ERROR: module path does not exist: /usr/lib/nodejs/node-almond/almond.min.js))

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:26:15 +
with message-id 
and subject line Bug#922391: fixed in isso 0.12.2-2
has caused the Debian Bug report #922391,
regarding isso: (ERROR: module path does not exist: 
/usr/lib/nodejs/node-almond/almond.min.js)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
922391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:isso
Version: 0.12.2-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 python3,sphinxdoc --buildsystem=pybuild --test-nose
   dh_update_autotools_config -i -O--buildsystem=pybuild -O--test-nose
   dh_autoreconf -i -O--buildsystem=pybuild -O--test-nose
   dh_auto_configure -i -O--buildsystem=pybuild -O--test-nose
pybuild --configure --test-nose -i python{version} -p 3.7
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
nodejs /usr/lib/nodejs/requirejs/r.js -convert /usr/lib/nodejs/jade/lib/ 
isso/js/components/jade/
/usr/bin/make RJS="nodejs /usr/lib/nodejs/requirejs/r.js" LC_ALL=C.UTF-8 
SASS="sass --sourcemap=none"
make[2]: Entering directory '/<>'
/bin/sh: 1: git: not found
sphinx-build -b man docs/ -d debian/doctrees man/
Running Sphinx v1.8.3
making output directory...
building [mo]: targets for 0 po files that are out of date
building [man]: all manpages
updating environment: 17 added, 0 changed, 0 removed
reading sources... [  5%] contribute
reading sources... [ 11%] docs/configuration/client
reading sources... [ 17%] docs/configuration/server
reading sources... [ 23%] docs/extras/advanced-integration
reading sources... [ 29%] docs/extras/advanced-migration
reading sources... [ 35%] docs/extras/api
reading sources... [ 41%] docs/extras/deployment
reading sources... [ 47%] docs/index
reading sources... [ 52%] docs/install
reading sources... [ 58%] docs/man/index
reading sources... [ 64%] docs/quickstart
reading sources... [ 70%] docs/setup/multiple-sites
reading sources... [ 76%] docs/setup/sub-uri
reading sources... [ 82%] docs/troubleshooting
reading sources... [ 88%] faq
reading sources... [ 94%] news
reading sources... [100%] releasing

/<>/docs/docs/extras/advanced-migration.rst:12: WARNING: Error in 
"code-block" directive:
1 argument(s) required, 0 supplied.

.. code-block::

A list of threads, each item being a dict with the following data:

- id: a text representing the unique thread id (note: by default isso
  associates this ID to the article URL, but it can be changed on
  client side with "data-isso-id" - see :doc:`client configuration 
<../configuration/client>` )
- title: the title of the thread
- comments: the list of comments

Each item in that list of comments is a dict with the following data:

- id: an integer with the unique id of the comment inside the thread
  (it can be repeated among different threads); this will be used to
  order the comment inside the thread
- author: the author's name
- email: the author's email
- website: the author's website
- remote_addr: the author's IP
- created: a timestamp, in the format "%Y-%m-%d %H:%M:%S"
/<>/docs/docs/extras/advanced-migration.rst:35: WARNING: Error in 
"code-block" directive:
maximum 1 argument(s) allowed, 50 supplied.

.. code-block:: json
[
{
"id": "/blog/article1",
"title": "First article!"
comments": [
{
"author": "James",
"created": "2018-11-28 17:24:23",
"email": "em...@mail.com",
"id": "1",
"remote_addr": "127.0.0.1",
"text": "Great article!",
"website": "http://fefzfzef.frzr;
},
{
"author": "Harold",
"created": "2018-11-28 17:58:03",
"email": "ema...@mail.com",
"id": "2",
"remote_addr": "",
"text": "I hated it...",
"website": ""
}
]
}
]
looking for now-outdated files... none found
pickling environment... done
checking consistency... /<>/docs/contribute.rst: WARNING: document 
isn't 

Bug#921899: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:26:31 +
with message-id 
and subject line Bug#921804: fixed in libmodule-install-readmefrompod-perl 
0.30-3
has caused the Debian Bug report #921804,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-calendar
Version: 1.01-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
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
rm -rf inc/Module
for ver in 4; do \
 perl Makefile.PL RTHOME=/usr/share/request-tracker$ver INSTALLDIRS=vendor; \
 mv Makefile Makefile$ver; \
done
Cannot determine perl version info from lib/RTx/Calendar.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
mv: cannot stat 'Makefile': No such file or directory
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-calendar.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: libmodule-install-readmefrompod-perl
Source-Version: 0.30-3

We believe that the bug you reported is fixed in the latest version of
libmodule-install-readmefrompod-perl, which is due to be installed in the 
Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libmodule-install-readmefrompod-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:52:47 CET
Source: libmodule-install-readmefrompod-perl
Binary: libmodule-install-readmefrompod-perl
Architecture: source
Version: 0.30-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Description: 
 libmodule-install-readmefrompod-perl - automatically convert POD to a README
Closes: 921804
Changes:
 libmodule-install-readmefrompod-perl (0.30-3) unstable; urgency=medium
 .
   * Team upload.
   * Add libcapture-tiny-perlto Depends. (Closes: #921804)
Checksums-Sha256: 
 61f152072c72c366e901a2d6789465d84f4452ea9a22264fe09e0bde9e87dee2 2650 
libmodule-install-readmefrompod-perl_0.30-3.dsc
 574117e254bb3b9bbd81175a046ae46300e60a9d8308ab6a2d51788344819d99 4808 
libmodule-install-readmefrompod-perl_0.30-3.debian.tar.xz
 aca7507b902036cab509f330f3295322ecfb14633ed89a0b69d902618900704a 6248 
libmodule-install-readmefrompod-perl_0.30-3_sourceonly.buildinfo
Checksums-Sha1: 
 d3964436ca42e2096c879982fb1edf083161b9f6 2650 
libmodule-install-readmefrompod-perl_0.30-3.dsc
 

Bug#921899: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:27:41 +
with message-id 
and subject line Bug#921899: fixed in rt-extension-calendar 1.01-1.1
has caused the Debian Bug report #921899,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-calendar
Version: 1.01-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
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
rm -rf inc/Module
for ver in 4; do \
 perl Makefile.PL RTHOME=/usr/share/request-tracker$ver INSTALLDIRS=vendor; \
 mv Makefile Makefile$ver; \
done
Cannot determine perl version info from lib/RTx/Calendar.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
mv: cannot stat 'Makefile': No such file or directory
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-calendar.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: rt-extension-calendar
Source-Version: 1.01-1.1

We believe that the bug you reported is fixed in the latest version of
rt-extension-calendar, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated rt-extension-calendar 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:14:45 CET
Source: rt-extension-calendar
Binary: rt4-extension-calendar
Architecture: source
Version: 1.01-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: gregor herrmann 
Description: 
 rt4-extension-calendar - Calendar view for Request Tracker 4
Closes: 921899
Changes:
 rt-extension-calendar (1.01-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dominic Hargreaves ]
   * Update Vcs-* fields to point to Salsa
 .
   [ gregor herrmann ]
   * Add libcapture-tiny-perl to Build-Depends-Indep. (Closes: #921899)
Checksums-Sha256: 
 dc6be3a6ffb541e127e31ca1c488edbd64d909b14083e8a4aef845e6a2583157 2392 
rt-extension-calendar_1.01-1.1.dsc
 32b6756518303fed701303dd5dddcd487e8d2de7ea7da47bd626cc863b476717 2164 
rt-extension-calendar_1.01-1.1.debian.tar.xz
 7dbcfa1960ee85bc28a26a963b98e951006de2a4a2507e64fbbf4aeacb823344 16470 
rt-extension-calendar_1.01-1.1_sourceonly.buildinfo
Checksums-Sha1: 
 bf7241279a94ca58e21b6dced9e249ca098730c3 2392 
rt-extension-calendar_1.01-1.1.dsc
 cfdebb8d9c426050e4f15cd894fdd4ebb1400fdd 2164 

Bug#921805: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:27:47 +
with message-id 
and subject line Bug#921804: fixed in rt-extension-jsgantt 1.03-1.1
has caused the Debian Bug report #921804,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-nagios
Version: 1.01-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
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Cannot determine perl version info from lib/RT/Extension/Nagios.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc . /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" 
returned exit code 2
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-nagios.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: rt-extension-jsgantt
Source-Version: 1.03-1.1

We believe that the bug you reported is fixed in the latest version of
rt-extension-jsgantt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated rt-extension-jsgantt 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:23:21 CET
Source: rt-extension-jsgantt
Binary: rt4-extension-jsgantt
Architecture: source
Version: 1.03-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: gregor herrmann 
Description: 
 rt4-extension-jsgantt - Gantt charts for your tickets (for RT4)
Closes: 921804
Changes:
 rt-extension-jsgantt (1.03-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dominic Hargreaves ]
   * Update Vcs-* fields to point to Salsa
 .
   [ gregor herrmann ]
   * Add libcapture-tiny-perl to Build-Depends-Indep. (Closes: #921804)
Checksums-Sha256: 
 2e810c5b8e497ccbd2b79ed33807e310d70259a0ba4b6d3251c7f25d393d94a9 2380 
rt-extension-jsgantt_1.03-1.1.dsc
 7f0b5a4218f1c0e8a713e49a1e19b09be7e5df6682c6670eefa2008fd50cc3ec 2792 

Bug#921899: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:27:47 +
with message-id 
and subject line Bug#921804: fixed in rt-extension-jsgantt 1.03-1.1
has caused the Debian Bug report #921804,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-calendar
Version: 1.01-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
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
rm -rf inc/Module
for ver in 4; do \
 perl Makefile.PL RTHOME=/usr/share/request-tracker$ver INSTALLDIRS=vendor; \
 mv Makefile Makefile$ver; \
done
Cannot determine perl version info from lib/RTx/Calendar.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
mv: cannot stat 'Makefile': No such file or directory
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-calendar.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: rt-extension-jsgantt
Source-Version: 1.03-1.1

We believe that the bug you reported is fixed in the latest version of
rt-extension-jsgantt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated rt-extension-jsgantt 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:23:21 CET
Source: rt-extension-jsgantt
Binary: rt4-extension-jsgantt
Architecture: source
Version: 1.03-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: gregor herrmann 
Description: 
 rt4-extension-jsgantt - Gantt charts for your tickets (for RT4)
Closes: 921804
Changes:
 rt-extension-jsgantt (1.03-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dominic Hargreaves ]
   * Update Vcs-* fields to point to Salsa
 .
   [ gregor herrmann ]
   * Add libcapture-tiny-perl to Build-Depends-Indep. (Closes: #921804)
Checksums-Sha256: 
 2e810c5b8e497ccbd2b79ed33807e310d70259a0ba4b6d3251c7f25d393d94a9 2380 
rt-extension-jsgantt_1.03-1.1.dsc
 7f0b5a4218f1c0e8a713e49a1e19b09be7e5df6682c6670eefa2008fd50cc3ec 2792 
rt-extension-jsgantt_1.03-1.1.debian.tar.xz
 30ea56ccc4efecf9c3496653fe4b45432a0ef5644dbc4bc5d08059c112ad53be 16391 
rt-extension-jsgantt_1.03-1.1_sourceonly.buildinfo
Checksums-Sha1: 
 6695e1281ad56d516f2a8b22d480e652bb7df576 2380 rt-extension-jsgantt_1.03-1.1.dsc
 836bef9de2c4e82193c407b24a273188a9c7bf94 2792 

Bug#921805: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:27:41 +
with message-id 
and subject line Bug#921899: fixed in rt-extension-calendar 1.01-1.1
has caused the Debian Bug report #921899,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-nagios
Version: 1.01-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
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Cannot determine perl version info from lib/RT/Extension/Nagios.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc . /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" 
returned exit code 2
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-nagios.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: rt-extension-calendar
Source-Version: 1.01-1.1

We believe that the bug you reported is fixed in the latest version of
rt-extension-calendar, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated rt-extension-calendar 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:14:45 CET
Source: rt-extension-calendar
Binary: rt4-extension-calendar
Architecture: source
Version: 1.01-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: gregor herrmann 
Description: 
 rt4-extension-calendar - Calendar view for Request Tracker 4
Closes: 921899
Changes:
 rt-extension-calendar (1.01-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dominic Hargreaves ]
   * Update Vcs-* fields to point to Salsa
 .
   [ gregor herrmann ]
   * Add libcapture-tiny-perl to Build-Depends-Indep. (Closes: #921899)
Checksums-Sha256: 
 dc6be3a6ffb541e127e31ca1c488edbd64d909b14083e8a4aef845e6a2583157 2392 
rt-extension-calendar_1.01-1.1.dsc
 32b6756518303fed701303dd5dddcd487e8d2de7ea7da47bd626cc863b476717 2164 

Bug#921900: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:27:47 +
with message-id 
and subject line Bug#921804: fixed in rt-extension-jsgantt 1.03-1.1
has caused the Debian Bug report #921804,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-smsnotify
Version: 1.04-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
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc . /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" 
returned exit code 2
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-smsnotify.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: rt-extension-jsgantt
Source-Version: 1.03-1.1

We believe that the bug you reported is fixed in the latest version of
rt-extension-jsgantt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated rt-extension-jsgantt 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:23:21 CET
Source: rt-extension-jsgantt
Binary: rt4-extension-jsgantt
Architecture: source
Version: 1.03-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: gregor herrmann 
Description: 
 rt4-extension-jsgantt - Gantt charts for your tickets (for RT4)
Closes: 921804
Changes:
 rt-extension-jsgantt (1.03-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dominic Hargreaves ]
   * Update Vcs-* fields to point to Salsa
 .
   [ gregor herrmann ]
   * Add libcapture-tiny-perl to Build-Depends-Indep. (Closes: #921804)
Checksums-Sha256: 
 2e810c5b8e497ccbd2b79ed33807e310d70259a0ba4b6d3251c7f25d393d94a9 2380 
rt-extension-jsgantt_1.03-1.1.dsc
 7f0b5a4218f1c0e8a713e49a1e19b09be7e5df6682c6670eefa2008fd50cc3ec 2792 
rt-extension-jsgantt_1.03-1.1.debian.tar.xz
 

Bug#921804: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:26:31 +
with message-id 
and subject line Bug#921804: fixed in libmodule-install-readmefrompod-perl 
0.30-3
has caused the Debian Bug report #921804,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-jsgantt
Version: 1.03-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
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
rm -rf inc/Module
for ver in 4; do \
 perl Makefile.PL INSTALLDIRS=vendor; \
 mv Makefile Makefile$ver; \
done
Cannot determine perl version info from lib/RT/Extension/JSGantt.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
mv: cannot stat 'Makefile': No such file or directory
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-jsgantt.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: libmodule-install-readmefrompod-perl
Source-Version: 0.30-3

We believe that the bug you reported is fixed in the latest version of
libmodule-install-readmefrompod-perl, which is due to be installed in the 
Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libmodule-install-readmefrompod-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:52:47 CET
Source: libmodule-install-readmefrompod-perl
Binary: libmodule-install-readmefrompod-perl
Architecture: source
Version: 0.30-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Description: 
 libmodule-install-readmefrompod-perl - automatically convert POD to a README
Closes: 921804
Changes:
 libmodule-install-readmefrompod-perl (0.30-3) unstable; urgency=medium
 .
   * Team upload.
   * Add libcapture-tiny-perlto Depends. (Closes: #921804)
Checksums-Sha256: 
 61f152072c72c366e901a2d6789465d84f4452ea9a22264fe09e0bde9e87dee2 2650 
libmodule-install-readmefrompod-perl_0.30-3.dsc
 574117e254bb3b9bbd81175a046ae46300e60a9d8308ab6a2d51788344819d99 4808 
libmodule-install-readmefrompod-perl_0.30-3.debian.tar.xz
 aca7507b902036cab509f330f3295322ecfb14633ed89a0b69d902618900704a 6248 
libmodule-install-readmefrompod-perl_0.30-3_sourceonly.buildinfo
Checksums-Sha1: 
 d3964436ca42e2096c879982fb1edf083161b9f6 2650 

Bug#921804: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:27:47 +
with message-id 
and subject line Bug#921804: fixed in rt-extension-jsgantt 1.03-1.1
has caused the Debian Bug report #921804,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-jsgantt
Version: 1.03-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
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
rm -rf inc/Module
for ver in 4; do \
 perl Makefile.PL INSTALLDIRS=vendor; \
 mv Makefile Makefile$ver; \
done
Cannot determine perl version info from lib/RT/Extension/JSGantt.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
mv: cannot stat 'Makefile': No such file or directory
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-jsgantt.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: rt-extension-jsgantt
Source-Version: 1.03-1.1

We believe that the bug you reported is fixed in the latest version of
rt-extension-jsgantt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated rt-extension-jsgantt 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:23:21 CET
Source: rt-extension-jsgantt
Binary: rt4-extension-jsgantt
Architecture: source
Version: 1.03-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: gregor herrmann 
Description: 
 rt4-extension-jsgantt - Gantt charts for your tickets (for RT4)
Closes: 921804
Changes:
 rt-extension-jsgantt (1.03-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dominic Hargreaves ]
   * Update Vcs-* fields to point to Salsa
 .
   [ gregor herrmann ]
   * Add libcapture-tiny-perl to Build-Depends-Indep. (Closes: #921804)
Checksums-Sha256: 
 2e810c5b8e497ccbd2b79ed33807e310d70259a0ba4b6d3251c7f25d393d94a9 2380 
rt-extension-jsgantt_1.03-1.1.dsc
 7f0b5a4218f1c0e8a713e49a1e19b09be7e5df6682c6670eefa2008fd50cc3ec 2792 
rt-extension-jsgantt_1.03-1.1.debian.tar.xz
 30ea56ccc4efecf9c3496653fe4b45432a0ef5644dbc4bc5d08059c112ad53be 16391 
rt-extension-jsgantt_1.03-1.1_sourceonly.buildinfo
Checksums-Sha1: 
 6695e1281ad56d516f2a8b22d480e652bb7df576 2380 rt-extension-jsgantt_1.03-1.1.dsc
 

Bug#921805: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:26:31 +
with message-id 
and subject line Bug#921804: fixed in libmodule-install-readmefrompod-perl 
0.30-3
has caused the Debian Bug report #921804,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-nagios
Version: 1.01-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
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Cannot determine perl version info from lib/RT/Extension/Nagios.pm
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc . /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" 
returned exit code 2
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-nagios.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: libmodule-install-readmefrompod-perl
Source-Version: 0.30-3

We believe that the bug you reported is fixed in the latest version of
libmodule-install-readmefrompod-perl, which is due to be installed in the 
Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libmodule-install-readmefrompod-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:52:47 CET
Source: libmodule-install-readmefrompod-perl
Binary: libmodule-install-readmefrompod-perl
Architecture: source
Version: 0.30-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Description: 
 libmodule-install-readmefrompod-perl - automatically convert POD to a README
Closes: 921804
Changes:
 libmodule-install-readmefrompod-perl (0.30-3) unstable; urgency=medium
 .
   * Team upload.
   * Add libcapture-tiny-perlto Depends. (Closes: #921804)
Checksums-Sha256: 
 61f152072c72c366e901a2d6789465d84f4452ea9a22264fe09e0bde9e87dee2 2650 
libmodule-install-readmefrompod-perl_0.30-3.dsc
 574117e254bb3b9bbd81175a046ae46300e60a9d8308ab6a2d51788344819d99 4808 

Bug#921900: marked as done (libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 19:26:31 +
with message-id 
and subject line Bug#921804: fixed in libmodule-install-readmefrompod-perl 
0.30-3
has caused the Debian Bug report #921804,
regarding libmodule-install-readmefrompod-perl: missing dependency on 
Capture::Tiny
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rt-extension-smsnotify
Version: 1.04-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
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny 
module) (@INC contains: inc . /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40.
include /<>/inc/Module/Install.pm
include inc/Module/Install/RTx.pm
include inc/Module/Install/Base.pm
include inc/Module/Install/Metadata.pm
include inc/Module/Install/Makefile.pm
include inc/Module/Install/ReadmeFromPod.pm
dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" 
returned exit code 2
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-smsnotify.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: libmodule-install-readmefrompod-perl
Source-Version: 0.30-3

We believe that the bug you reported is fixed in the latest version of
libmodule-install-readmefrompod-perl, which is due to be installed in the 
Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libmodule-install-readmefrompod-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 19:52:47 CET
Source: libmodule-install-readmefrompod-perl
Binary: libmodule-install-readmefrompod-perl
Architecture: source
Version: 0.30-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Description: 
 libmodule-install-readmefrompod-perl - automatically convert POD to a README
Closes: 921804
Changes:
 libmodule-install-readmefrompod-perl (0.30-3) unstable; urgency=medium
 .
   * Team upload.
   * Add libcapture-tiny-perlto Depends. (Closes: #921804)
Checksums-Sha256: 
 61f152072c72c366e901a2d6789465d84f4452ea9a22264fe09e0bde9e87dee2 2650 
libmodule-install-readmefrompod-perl_0.30-3.dsc
 574117e254bb3b9bbd81175a046ae46300e60a9d8308ab6a2d51788344819d99 4808 
libmodule-install-readmefrompod-perl_0.30-3.debian.tar.xz
 

Bug#921804: Bug #921804 in libmodule-install-readmefrompod-perl marked as pending

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #921804 in libmodule-install-readmefrompod-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:

https://salsa.debian.org/perl-team/modules/packages/libmodule-install-readmefrompod-perl/commit/4fbb728c5e2e273a6b5e62894987ddc307be10bf


Add libcapture-tiny-perlto Depends.

Closes: #921804


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/921804

Processed: Bug #921804 in libmodule-install-readmefrompod-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #921804 [libmodule-install-readmefrompod-perl] 
libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny
Bug #921805 [libmodule-install-readmefrompod-perl] 
libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny
Bug #921899 [libmodule-install-readmefrompod-perl] 
libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny
Bug #921900 [libmodule-install-readmefrompod-perl] 
libmodule-install-readmefrompod-perl: missing dependency on Capture::Tiny
Ignoring request to alter tags of bug #921804 to the same tags previously set
Ignoring request to alter tags of bug #921805 to the same tags previously set
Ignoring request to alter tags of bug #921899 to the same tags previously set
Ignoring request to alter tags of bug #921900 to the same tags previously set

-- 
921804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921804
921805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921805
921899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921899
921900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#879007: cyrus-imapd does not accept new connections

[Simon Josefsson]

Hi.  Just another person to confirm this bug, it took me some time to
track down and then notice it was already reported.  I upgraded my mail
server to debian 9 and cyrus imapd always stop working after a couple
of days due to this.  Fortunately my mail server is pretty low traffic,
so I'm hoping a /etc/cron.daily/ job to '/etc/init.d/cyrus-imapd
restart' will work around it.

/Simon


signature.asc
Description: This is a digitally signed message part

Processed: reassign 921900 to libmodule-install-readmefrompod-perl ..., merging 921900 921899 921805 921804 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 921900 libmodule-install-readmefrompod-perl 0.30-1
Bug #921900 [src:rt-extension-smsnotify] rt-extension-smsnotify: FTBFS 
(dh_auto_configure fails)
Bug reassigned from package 'src:rt-extension-smsnotify' to 
'libmodule-install-readmefrompod-perl'.
No longer marked as found in versions rt-extension-smsnotify/1.04-1.
Ignoring request to alter fixed versions of bug #921900 to the same values 
previously set
Bug #921900 [libmodule-install-readmefrompod-perl] rt-extension-smsnotify: 
FTBFS (dh_auto_configure fails)
There is no source info for the package 'libmodule-install-readmefrompod-perl' 
at version '0.30-1' with architecture ''
Unable to make a source version for version '0.30-1'
Marked as found in versions 0.30-1.
> reassign 921899 libmodule-install-readmefrompod-perl 0.30-1
Bug #921899 [src:rt-extension-calendar] rt-extension-calendar: FTBFS (mv: 
cannot stat 'Makefile': No such file or directory)
Bug reassigned from package 'src:rt-extension-calendar' to 
'libmodule-install-readmefrompod-perl'.
No longer marked as found in versions rt-extension-calendar/1.01-1.
Ignoring request to alter fixed versions of bug #921899 to the same values 
previously set
Bug #921899 [libmodule-install-readmefrompod-perl] rt-extension-calendar: FTBFS 
(mv: cannot stat 'Makefile': No such file or directory)
There is no source info for the package 'libmodule-install-readmefrompod-perl' 
at version '0.30-1' with architecture ''
Unable to make a source version for version '0.30-1'
Marked as found in versions 0.30-1.
> reassign 921805 libmodule-install-readmefrompod-perl 0.30-1
Bug #921805 [src:rt-extension-nagios] rt-extension-nagios: FTBFS (you may need 
to install the Capture::Tiny module)
Bug reassigned from package 'src:rt-extension-nagios' to 
'libmodule-install-readmefrompod-perl'.
No longer marked as found in versions rt-extension-nagios/1.01-1.
Ignoring request to alter fixed versions of bug #921805 to the same values 
previously set
Bug #921805 [libmodule-install-readmefrompod-perl] rt-extension-nagios: FTBFS 
(you may need to install the Capture::Tiny module)
There is no source info for the package 'libmodule-install-readmefrompod-perl' 
at version '0.30-1' with architecture ''
Unable to make a source version for version '0.30-1'
Marked as found in versions 0.30-1.
> reassign 921804 libmodule-install-readmefrompod-perl 0.30-1
Bug #921804 [src:rt-extension-jsgantt] rt-extension-jsgantt: FTBFS (mv: cannot 
stat 'Makefile': No such file or directory)
Bug reassigned from package 'src:rt-extension-jsgantt' to 
'libmodule-install-readmefrompod-perl'.
No longer marked as found in versions rt-extension-jsgantt/1.03-1.
Ignoring request to alter fixed versions of bug #921804 to the same values 
previously set
Bug #921804 [libmodule-install-readmefrompod-perl] rt-extension-jsgantt: FTBFS 
(mv: cannot stat 'Makefile': No such file or directory)
There is no source info for the package 'libmodule-install-readmefrompod-perl' 
at version '0.30-1' with architecture ''
Unable to make a source version for version '0.30-1'
Marked as found in versions 0.30-1.
> merge 921900 921899 921805 921804
Bug #921900 [libmodule-install-readmefrompod-perl] rt-extension-smsnotify: 
FTBFS (dh_auto_configure fails)
Bug #921805 [libmodule-install-readmefrompod-perl] rt-extension-nagios: FTBFS 
(you may need to install the Capture::Tiny module)
Added tag(s) patch and pending.
Bug #921900 [libmodule-install-readmefrompod-perl] rt-extension-smsnotify: 
FTBFS (dh_auto_configure fails)
Added tag(s) patch and pending.
Bug #921804 [libmodule-install-readmefrompod-perl] rt-extension-jsgantt: FTBFS 
(mv: cannot stat 'Makefile': No such file or directory)
Bug #921899 [libmodule-install-readmefrompod-perl] rt-extension-calendar: FTBFS 
(mv: cannot stat 'Makefile': No such file or directory)
Merged 921804 921805 921899 921900
> retitle 921804 libmodule-install-readmefrompod-perl: missing dependency on 
> Capture::Tiny
Bug #921804 [libmodule-install-readmefrompod-perl] rt-extension-jsgantt: FTBFS 
(mv: cannot stat 'Makefile': No such file or directory)
Bug #921805 [libmodule-install-readmefrompod-perl] rt-extension-nagios: FTBFS 
(you may need to install the Capture::Tiny module)
Bug #921899 [libmodule-install-readmefrompod-perl] rt-extension-calendar: FTBFS 
(mv: cannot stat 'Makefile': No such file or directory)
Bug #921900 [libmodule-install-readmefrompod-perl] rt-extension-smsnotify: 
FTBFS (dh_auto_configure fails)
Changed Bug title to 'libmodule-install-readmefrompod-perl: missing dependency 
on Capture::Tiny' from 'rt-extension-jsgantt: FTBFS (mv: cannot stat 
'Makefile': No such file or directory)'.
Changed Bug title to 'libmodule-install-readmefrompod-perl: missing dependency 
on Capture::Tiny' from 'rt-extension-nagios: FTBFS (you may need to install the 
Capture::Tiny module)'.
Changed Bug title to 'libmodule-install-readmefrompod-perl: missing dependency 
on Capture::Tiny' from 

Bug#921754: gfsview: undefined reference to symbol 'glEndList'

[Andreas Tille]

Hi,

I tried to build gfsview whether I could do something to fix #921754.
I can confirm that the build leads to

...
/usr/bin/ld: 
/build/gfsview-20121130+dfsg/batch/.libs/librender2D.a(librender2D_la-render.o):
 undefined reference to symbol 'glEndList'
/usr/bin/ld: //usr/lib/x86_64-linux-gnu/libGL.so.1: error adding symbols: DSO 
missing from command line
/usr/bin/ld: 
/build/gfsview-20121130+dfsg/batch/.libs/librender3D.a(librender3D_la-render.o):
 undefined reference to symbol 'glEndList'
/usr/bin/ld: //usr/lib/x86_64-linux-gnu/libGL.so.1: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status
...

I guess this is just a missing OpenGL library - but which one.  I have
no idea about OpenGL but may be someone here on the list could help?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: rt-extension-jsgantt: diff for NMU version 1.03-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 921804 + patch pending
Bug #921804 [src:rt-extension-jsgantt] rt-extension-jsgantt: FTBFS (mv: cannot 
stat 'Makefile': No such file or directory)
Added tag(s) patch and pending.

-- 
921804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921804: rt-extension-jsgantt: diff for NMU version 1.03-1.1

[gregor herrmann]

Control: tags 921804 + patch pending


Dear maintainer,

I've uploaded an NMU for rt-extension-jsgantt (versioned as 1.03-1.1). The diff
is attached to this message.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jerry Lee Lewis: High School Confidencial
diff -Nru rt-extension-jsgantt-1.03/debian/changelog rt-extension-jsgantt-1.03/debian/changelog
--- rt-extension-jsgantt-1.03/debian/changelog	2015-06-03 20:21:53.0 +0200
+++ rt-extension-jsgantt-1.03/debian/changelog	2019-02-16 19:21:10.0 +0100
@@ -1,3 +1,15 @@
+rt-extension-jsgantt (1.03-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Dominic Hargreaves ]
+  * Update Vcs-* fields to point to Salsa
+
+  [ gregor herrmann ]
+  * Add libcapture-tiny-perl to Build-Depends-Indep. (Closes: #921804)
+
+ -- gregor herrmann   Sat, 16 Feb 2019 19:21:10 +0100
+
 rt-extension-jsgantt (1.03-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru rt-extension-jsgantt-1.03/debian/control rt-extension-jsgantt-1.03/debian/control
--- rt-extension-jsgantt-1.03/debian/control	2015-06-03 20:21:53.0 +0200
+++ rt-extension-jsgantt-1.03/debian/control	2019-02-16 19:21:10.0 +0100
@@ -2,16 +2,18 @@
 Section: perl
 Priority: optional
 Maintainer: Debian Request Tracker Group 
-Uploaders: KURASHIKI Satoru 
+Uploaders: KURASHIKI Satoru ,
+Dominic Hargreaves 
 Build-Depends: debhelper (>= 8)
 Build-Depends-Indep: request-tracker4,
+ libcapture-tiny-perl,
  libjson-perl,
  liblist-moreutils-perl,
  libmodule-install-rtx-perl
 Standards-Version: 3.9.6
 Homepage: http://search.cpan.org/dist/RT-Extension-JSGantt/
-Vcs-Git: git://anonscm.debian.org/pkg-request-tracker/rt-extension-jsgantt.git
-Vcs-Browser: http://anonscm.debian.org/?p=pkg-request-tracker/rt-extension-jsgantt.git
+Vcs-Browser: https://salsa.debian.org/request-tracker-team/rt-extension-jsgantt
+Vcs-Git: https://salsa.debian.org/request-tracker-team/rt-extension-jsgantt.git
 
 Package: rt4-extension-jsgantt
 Architecture: all


signature.asc
Description: Digital Signature

Bug#921899: rt-extension-calendar: diff for NMU version 1.01-1.1

[gregor herrmann]

Control: tags 921899 + patch
Control: tags 921899 + pending

Dear maintainer,

I've prepared an NMU for rt-extension-calendar (versioned as 1.01-1.1) and
uploaded it to DELAYED/0.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jerry Lee Lewis: High School Confidencial
diff -Nru rt-extension-calendar-1.01/debian/changelog rt-extension-calendar-1.01/debian/changelog
--- rt-extension-calendar-1.01/debian/changelog	2017-01-20 15:16:42.0 +0100
+++ rt-extension-calendar-1.01/debian/changelog	2019-02-16 19:05:12.0 +0100
@@ -1,3 +1,15 @@
+rt-extension-calendar (1.01-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Dominic Hargreaves ]
+  * Update Vcs-* fields to point to Salsa
+
+  [ gregor herrmann ]
+  * Add libcapture-tiny-perl to Build-Depends-Indep. (Closes: #921899)
+
+ -- gregor herrmann   Sat, 16 Feb 2019 19:05:12 +0100
+
 rt-extension-calendar (1.01-1) unstable; urgency=medium
 
   * Drop incorrect Build-Depends on perl-modules and unnecessary
diff -Nru rt-extension-calendar-1.01/debian/control rt-extension-calendar-1.01/debian/control
--- rt-extension-calendar-1.01/debian/control	2017-01-20 15:11:53.0 +0100
+++ rt-extension-calendar-1.01/debian/control	2019-02-16 19:05:12.0 +0100
@@ -6,14 +6,15 @@
 Dominic Hargreaves ,
 Build-Depends: debhelper (>= 9)
 Build-Depends-Indep: request-tracker4,
+ libcapture-tiny-perl,
  libmodule-install-rtx-perl,
  libdatetime-perl,
  libdatetime-set-perl,
  perl,
 Standards-Version: 3.9.8
 Homepage: http://search.cpan.org/dist/RTx-Calendar/
-Vcs-Git: git://anonscm.debian.org/pkg-request-tracker/rt-extension-calendar.git
-Vcs-Browser: http://anonscm.debian.org/?p=pkg-request-tracker/rt-extension-calendar.git
+Vcs-Browser: https://salsa.debian.org/request-tracker-team/rt-extension-calendar
+Vcs-Git: https://salsa.debian.org/request-tracker-team/rt-extension-calendar.git
 
 Package: rt4-extension-calendar
 Architecture: all


signature.asc
Description: Digital Signature

Processed: rt-extension-calendar: diff for NMU version 1.01-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 921899 + patch
Bug #921899 [src:rt-extension-calendar] rt-extension-calendar: FTBFS (mv: 
cannot stat 'Makefile': No such file or directory)
Added tag(s) patch.
> tags 921899 + pending
Bug #921899 [src:rt-extension-calendar] rt-extension-calendar: FTBFS (mv: 
cannot stat 'Makefile': No such file or directory)
Added tag(s) pending.

-- 
921899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#776246: Processed: severity of 776246 is grave

[Andrey Rahmatullin]

On Sat, Feb 16, 2019 at 12:33:08PM +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
> > severity 776246 grave
> Bug #776246 [librsync1] MD4 collision/preimage attacks (CVE-2014-8242)
> Severity set to 'grave' from 'important'
> > thanks
> Stopping processing here.
> 
> Please contact me if you need assistance.
Fixing this requires a transition and removing or patching rdiff-backup so 

Checking reverse dependencies...
# Broken Depends:
burp: burp [amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips 
mips64el mipsel ppc64el s390x]
csync2: csync2
duplicity: duplicity
rdiff-backup: rdiff-backup

# Broken Build-Depends:
burp: librsync-dev
csync2: librsync-dev
duplicity: librsync-dev (>= 0.9.6)
   rdiff
rdiff-backup: librsync-dev


Unfortunately I was too demotivated by the initial state of new librsync
(1.0+) and the API breakage affecting rdiff-backup to proceed with this
during the release cycle.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Processed: bug 922455 is forwarded to https://github.com/baszoetekouw/pinfo/pull/9

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 922455 https://github.com/baszoetekouw/pinfo/pull/9
Bug #922455 [pinfo] pinfo: malloc(): invalid size (unsorted)
Set Bug forwarded-to-address to 'https://github.com/baszoetekouw/pinfo/pull/9'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
922455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921775: marked as done (avr-libc: FTBFS (LaTeX error))

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 16:19:26 +
with message-id 
and subject line Bug#921775: fixed in avr-libc 1:2.0.0+Atmel3.6.1-2
has caused the Debian Bug report #921775,
regarding avr-libc: FTBFS (LaTeX error)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:avr-libc
Version: 1:2.0.0+Atmel3.6.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
test -f debian/rules
cd libc/avr-libc && ./bootstrap
+ rm -rf avr/lib
+ ./devtools/gen-avr-lib-tree.sh
Generating source directories:
  avr/lib/avr2/
  avr/lib/avr2/at90s1200
  avr/lib/avr2/attiny11
  avr/lib/avr2/attiny12
  avr/lib/avr2/attiny15
  avr/lib/avr2/attiny28
  avr/lib/avr2/at90s4414
  avr/lib/avr2/at90s4434

[... snipped ...]

pnmtopng: 12 colors found
Fixing transparency for open.png
pnmtopng: 2 colors found
Fixing transparency for releases.png
pnmtopng: 2 colors found
Fixing transparency for splitbar.png
pnmtopng: 7 colors found
Fixing transparency for sync_off.png
pnmtopng: 54 colors found
Fixing transparency for sync_on.png
pnmtopng: 57 colors found
Fixing transparency for tab_a.png
pnmtopng: 27 colors found
Fixing transparency for tab_b.png
pnmtopng: 30 colors found
Fixing transparency for tab_h.png
pnmtopng: 32 colors found
Fixing transparency for tab_s.png
pnmtopng: 35 colors found
echo timestamp > fix_png
cd latex_src && make refman.pdf
make[5]: Entering directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc/api/latex_src'
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl 
refman.pdf
pdflatex refman
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./refman.tex
LaTeX2e <2018-12-01>

make[5]: *** [Makefile:6: refman.pdf] Error 1
make[5]: Leaving directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc/api/latex_src'
make[4]: [Makefile:653: avr-libc-user-manual.pdf] Error 2 (ignored)
cp latex_src/refman.pdf avr-libc-user-manual.pdf
cp: cannot stat 'latex_src/refman.pdf': No such file or directory
make[4]: *** [Makefile:654: avr-libc-user-manual.pdf] Error 1
make[4]: Leaving directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc/api'
make[3]: *** [Makefile:380: all-recursive] Error 1
make[3]: Leaving directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc/doc'
make[2]: *** [Makefile:435: all-recursive] Error 1
make[2]: Leaving directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc'
make[1]: *** [Makefile:374: all] Error 2
make[1]: Leaving directory 
'/<>/avr-libc-2.0.0+Atmel3.6.1/libc/avr-libc'
make: *** [debian/rules:14: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/avr-libc.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: avr-libc
Source-Version: 1:2.0.0+Atmel3.6.1-2

We believe that the bug you reported is fixed in the latest version of
avr-libc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hakan Ardo  (supplier of updated avr-libc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 16:54:38 +0100
Source: avr-libc
Binary: avr-libc
Architecture: source all
Version: 1:2.0.0+Atmel3.6.1-2
Distribution: unstable
Urgency: medium

Bug#922457: [Pkg-fonts-devel] Bug#922457: fonts-roboto-hinted: update broke reverse-dependencies without notice

[Norbert Preining]

On Sat, 16 Feb 2019, Markus Koschany wrote:
> the recent upload of fonts-roboto broke reverse-dependencies like
> renpy because you removed or renamed previously installed files in
> fonts-roboto-hinted. I find that less than optimal given that we have
> entered the soft freeze for Debian 10. Please revert this change or
> provide the missing files again.

+1, same problem here with TeX Live packages suddently having dead
links.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#918823: Update on your bug report

[Aurelien Jarno]

Hi Richard,

On 2019-02-15 17:03, Richard Hartmann wrote:
> Hi Leopold,
> 
> did you have a chance to run the commands requested by Aurelien? This
> bug is marked critical, but has been stale for more than a month, now.

Leopold answered me privately, I am sorry to not have provided a summary
to the bug log earlier. There was an issue on the system with a
/usr/local/lib/libvirt-lxc.so.0 symlink but it turned out to not be the
issue.

I am personally out of ideas, if someone is able to reproduce the issue
or have ideas about what causes the issue, please don't hesitate to tell
it here.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: closing 921976

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 921976 1.5.6-1
Bug #921976 [src:mosquitto] mosquitto: CVE-2018-12546 CVE-2018-12550 
CVE-2018-12551
Marked as fixed in versions mosquitto/1.5.6-1.
Bug #921976 [src:mosquitto] mosquitto: CVE-2018-12546 CVE-2018-12550 
CVE-2018-12551
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
921976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921976: closing 921976

[Salvatore Bonaccorso]

close 921976 1.5.6-1
thanks

Processed: severity of 922461 is minor

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 922461 minor
Bug #922461 [src:qemu] CVE-2018-20124
Severity set to 'minor' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
922461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#922449: marked as done (autopkgtest with tox fails (and is ineffective))

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 13:52:05 +
with message-id 
and subject line Bug#922449: fixed in python-static3 0.7.0-6
has caused the Debian Bug report #922449,
regarding autopkgtest with tox fails (and is ineffective)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
922449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-static3
Version: 0.7.0-5
Severity: serious

Hi there,

tox's (new) maintainer here. python-static3 uses "tox" as an
autopkgtest, which is currently broken and that holds a newer version of
tox from migrating to testing. (Hence setting the severity to serious)

The use of tox here as an autopkgtest doesn't make a lot of sense to me
for the following reasons:
* This currently relies on the network to work, as it fetches
  dependencies over from pypi. That could be addressed with
  --sitepackages, however.

* This also means that the tests are against dependencies from pypi, not
  the versions in Debian. That's not really a Debian package test then,
  just an upstream test, and I'm not sure what the point of that is --
  presumably upstream is already doing that given they ship a tox.ini?

* In turn, this also means that those tests may fail at any point in
  time, because of changes outside of Debian. I think this is the case
  right now while I was trying to reproduce the debci failure (I get an
  unrelated backtrace from the pypi package "kid").

* Even more to it, this tests against Python versions set by upstream,
  which are currently set to:
envlist = py26, py27, py33, py34, pypy
  The package doesn't build Python 2 binaries, so these are out; it does
  not Build-Depend on pypy so that's out too; and the Python 3 versions
  are not versions that exist in sid/testing. So these tests are really
  not for any of the Python versions shipped in Debian...

* At the end of the day, the upstream tox just has a
commands=python setup.py test []
  ...which could be the command that autopkgtest runs. However, it may
  make more sense to just run that as part of the dh_auto_test step, as
  it runs the upstream tests and not any kind of Debian integration
  tests.

TL;DR: I'd remove the autopkgtest altogether, and make sure that
"python3 setup.py" when the package builds e.g. as part of dh_auto_test.
YMMV :)

Regards,
Faidon
--- End Message ---
--- Begin Message ---
Source: python-static3
Source-Version: 0.7.0-6

We believe that the bug you reported is fixed in the latest version of
python-static3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 922...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Herbert Parentes Fortes Neto  (supplier of updated 
python-static3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 16 Feb 2019 11:29:04 -0200
Source: python-static3
Binary: python3-static3
Architecture: source all
Version: 0.7.0-6
Distribution: unstable
Urgency: medium
Maintainer: Herbert Parentes Fortes Neto 
Changed-By: Herbert Parentes Fortes Neto 
Description:
 python3-static3 - Really simple WSGI way to serve static content (Python 3)
Closes: 922449
Changes:
 python-static3 (0.7.0-6) unstable; urgency=medium
 .
   * debian/control:
   - Buil-Depends rm tox and python-kid
   - Bump Standards-Version from 4.2.1 to .4.3.0
   * debian/rules:
   - dh_clean:
   - Remove .tox
   - Add .pytest_cache
   * debian/tests/control:
   - run pytest-3 (Closes: #922449)
 Thanks Faidon Liambotis
Checksums-Sha1:
 92be1bc1851b67a44e2cbc7669fee27842d4e164 2086 python-static3_0.7.0-6.dsc
 19d0e4a5e7d7299a7cdc0c91bd64ae188cf50adc 2912 
python-static3_0.7.0-6.debian.tar.xz
 814bd57eac3f79b94ec89ec639cea9875a3a2842 6811 
python-static3_0.7.0-6_amd64.buildinfo
 66860ed90718291567e3e739119465e7b8024e92 12756 python3-static3_0.7.0-6_all.deb
Checksums-Sha256:
 27bebce33ddaabef2011909c14e72c07e0589a25e7493fb3c83f718d343b82c1 2086 
python-static3_0.7.0-6.dsc
 0e638c7d3839c01f293f93359f406b86d10213393d9fe54c502557d7ea205b3e 2912 
python-static3_0.7.0-6.debian.tar.xz
 

Bug#909933: marked as done (jekyll: CVE-2018-17567: bypass of symlink checking)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 13:34:48 +
with message-id 
and subject line Bug#909933: fixed in jekyll 3.8.3+dfsg-3.1
has caused the Debian Bug report #909933,
regarding jekyll: CVE-2018-17567: bypass of symlink checking
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
909933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jekyll
Version: 3.8.3+dfsg-3
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/jekyll/jekyll/pull/7224
Control: found -1 3.1.6+dfsg-3

Hi,

The following vulnerability was published for jekyll.

CVE-2018-17567[0]:
| Jekyll through 3.6.2, 3.7.x through 3.7.3, and 3.8.x through 3.8.3
| allows attackers to access arbitrary files by specifying a symlink in
| the "include" key in the "_config.yml" file.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-17567
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17567
[1] https://github.com/jekyll/jekyll/pull/7224
[2] https://jekyllrb.com/news/2018/09/19/security-fixes-for-3-6-3-7-3-8/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: jekyll
Source-Version: 3.8.3+dfsg-3.1

We believe that the bug you reported is fixed in the latest version of
jekyll, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated jekyll package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 16 Feb 2019 13:46:27 +0100
Source: jekyll
Architecture: source
Version: 3.8.3+dfsg-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Dr. Tobias Quathamer 
Closes: 909933
Changes:
 jekyll (3.8.3+dfsg-3.1) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Non-maintainer upload.
   * Use secure URI in Homepage field.
 .
   [ Dr. Tobias Quathamer ]
   * Fix CVE-2018-17567, patch by Youhei SASAKI 
 (Closes: #909933)
Checksums-Sha1:
 d2f264b74f6013766d5a049f2ec188bb67cc3efa 2690 jekyll_3.8.3+dfsg-3.1.dsc
 28dc4004219998f643b5e083b0bcd04b77785e58 30452 
jekyll_3.8.3+dfsg-3.1.debian.tar.xz
 cb26414bb1db55baafcab4e1ed3e92fd14f27f45 20615 
jekyll_3.8.3+dfsg-3.1_amd64.buildinfo
Checksums-Sha256:
 74b27a9e51dbccb3c46f8ae436889cecc692d87b7f13f88b9d002a1198e4c43b 2690 
jekyll_3.8.3+dfsg-3.1.dsc
 c28b7929424e0fead30bf4685a0caa67af431891d6b543ad2a3d77bf8a3dc6a8 30452 
jekyll_3.8.3+dfsg-3.1.debian.tar.xz
 cfcf0398589fcd8bf19f79cf5d044cd63a3365ab7555710e2e5a2bceea18c973 20615 
jekyll_3.8.3+dfsg-3.1_amd64.buildinfo
Files:
 7b3b40508f5ebf860dbb8445a061716a 2690 web optional jekyll_3.8.3+dfsg-3.1.dsc
 3898f898d804331ec4bf0f00a170f84c 30452 web optional 
jekyll_3.8.3+dfsg-3.1.debian.tar.xz
 10b399b528babc9a9023c28521064065 20615 web optional 
jekyll_3.8.3+dfsg-3.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlxoCKYACgkQEwLx8Dbr
6xlsww/9F1XHJdK3dLukIUlkkWpwLyNFGkiAHgXrCW5uosFrbqOFPrbo7wjC1TFg
hsUJLlD2NbqpCteluRuz3QEeC9NgKNCj3Qep794Wzl/Xf2rC6YWMpy+7WgMGiKJX
qqdKmo/weFRWSTIIgGfGJbpxP/GIbMbDeRDgSIJC2ktw2QppDlk2wr/mZKDYzNBT
elukI9DArIP0VNy0VyKDKivBnC+F/NOHPkl9nVcCsF8Sm3WOzVM5NXVbd9FIZfQI
SAWkW4Qx3lYmR8/0qdpdUULhbjpbJ1LTue4zKgRpCWyZ5gFg8dlpXtYtnnb347Ef
wveA11ZNbGl2sj+h1TLgfFFw/aR7RlK0VNlx1wGCOjDsddIx5S7We6leNez7j4mu
jG/i3TqHhc4q7cloSZLpNGnvKBrK5riPS9kj/mHkKXVad42tNHsdfopRyqtFcKCY
Z1KPlfHJd7URhvOQ/i2RBb9IGtZYOmSdeQzfpxY02e4yRABU7tNv3B4ZolxP853w
f5vZmy1TnHaekI30xAFc4IZPapV6eD8FhNvRYn143TfdHw6LMOckmSGIw0e9B7yz
JHgqRh2o1v1QaWfO5szw5E56R8qJac7YgVqmLIpHsqkctx9t09mHyluCiZWhLKB2
x2doYI+WIAkq8pdYvMQm2HPa8aHtID6B36kesuNe57lqJAO/7/I=
=EVhy
-END PGP SIGNATURE End Message ---

Bug#921039: closed by Matthias Klose (Bug#921039: fixed in python2.7 2.7.15-6)

[Salvatore Bonaccorso]

Control: notfound -1 2.7.15-6
Control: notfound -1 2.7.15-5
Control: fixed -1 2.7.15-5

Hi,

On Fri, Feb 01, 2019 at 10:40:26AM +0100, Salvatore Bonaccorso wrote:
> Control: reopen -1
> Control: found -1 2.7.15-6
> Hi
> 
> On Fri, Feb 01, 2019 at 08:51:07AM +, Debian Bug Tracking System wrote:
> >  - CVE-2018-14647: _elementtree.c doesn't call XML_SetHashSalt().
> >Closes: #921039.
> 
> The change
> https://github.com/python/cpython/commit/18b20bad75b4ff0486940fba4ec680e96e70f3a2
> though does not seem to be applied looking at the debdiff from
> 2.7.15-5 to  2.7.15-6.
> 
> Can you please recheck, and if I'm wrong please hilight me what am I
> missing?

To answer my question: the fix is actually already included in the
git-updates.diff patch as uploaded in the -5 revision. Thus the diff
was not spotted in the debdiff between -5 and -6 causing the
confusion.

Regards,
Salvatore

Processed: Re: Bug#921039: closed by Matthias Klose (Bug#921039: fixed in python2.7 2.7.15-6)

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 2.7.15-6
Bug #921039 {Done: Matthias Klose } [python2.7] CVE-2018-14647
No longer marked as found in versions 2.7.15-6.
> notfound -1 2.7.15-5
Bug #921039 {Done: Matthias Klose } [python2.7] CVE-2018-14647
No longer marked as found in versions python2.7/2.7.15-5.
> fixed -1 2.7.15-5
Bug #921039 {Done: Matthias Klose } [python2.7] CVE-2018-14647
Marked as fixed in versions python2.7/2.7.15-5.

-- 
921039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#922453: marked as done (cernlib: fortran modules must be compiled with no stronger optimization than -O1 (aka -O))

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 13:04:08 +
with message-id 
and subject line Bug#922453: fixed in cernlib 20061220+dfsg3-4.4
has caused the Debian Bug report #922453,
regarding cernlib: fortran modules must be compiled with no stronger 
optimization than -O1 (aka -O)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
922453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cernlib
Version: 20061220+dfsg3-4.3
Severity: grave
Justification: renders package unusable
Tags: patch


 Message transféré 
Sujet : cernlib (20061220+dfsg3-4.3build1) misbehaves on x86_64
Date : Mon, 4 Feb 2019 00:52:08 +0100
De : Jacek M. Holeczek 
Pour : Matthias Klose , Gilles Filippini 

Hi,
I tried to use the cernlib related executables on an Ubuntu 18.04 /
x86_64 / gcc 7.3.0.
I have found that the "pawX11" misbehaves.
The problem is related to the used fortran optimization flag.
By default it is now "-O3" but this is producing misbehaving libraries.
I tried to rebuild everything using "-O2" but they still misbehaved.
Finally, after I switched to "-O" (i.e. "-O1"), they started to behave
properly.
Please find attached a small patch file which tries to ensure that the
fortran source code will be compiled with "-O" (and not "-O3" nor "-O2").
Hope it helps,
Best regards,
Jacek.

diff -Naur 
cernlib-20061220+dfsg3.original/debian/patches/102-dont-optimize-some-code.dpatch
 cernlib-20061220+dfsg3/debian/patches/102-dont-optimize-some-code.dpatch
--- 
cernlib-20061220+dfsg3.original/debian/patches/102-dont-optimize-some-code.dpatch
   2017-08-06 19:23:39.0 +
+++ cernlib-20061220+dfsg3/debian/patches/102-dont-optimize-some-code.dpatch
2019-02-03 21:49:52.638404057 +
@@ -20,7 +20,7 @@
 +#endif
 +
 +/* GCC 7 on 64bit targets, see https://gcc.gnu.org/PR81723 */
-+SpecialFortranLibObjectRule(cwerf64,cwerf64,-O2,NullParameter)
++SpecialFortranLibObjectRule(cwerf64,cwerf64,-O,NullParameter)
 diff -urNad cernlib-2006.dfsg.2~/src/mathlib/gen/d/Imakefile 
cernlib-2006.dfsg.2/src/mathlib/gen/d/Imakefile
 --- cernlib-2006.dfsg.2~/src/mathlib/gen/d/Imakefile   1996-06-12 
08:25:38.0 -0700
 +++ cernlib-2006.dfsg.2/src/mathlib/gen/d/Imakefile2008-02-22 
12:06:26.0 -0800
diff -Naur 
cernlib-20061220+dfsg3.original/debian/patches/126-fix-patchy-compile-flags.dpatch
 cernlib-20061220+dfsg3/debian/patches/126-fix-patchy-compile-flags.dpatch
--- 
cernlib-20061220+dfsg3.original/debian/patches/126-fix-patchy-compile-flags.dpatch
  2013-08-24 09:16:07.0 +
+++ cernlib-20061220+dfsg3/debian/patches/126-fix-patchy-compile-flags.dpatch   
2019-02-03 21:48:36.151806615 +
@@ -76,7 +76,7 @@
  
 -  PARAMETER   (CHPOF = '-c -O -fno-automatic')
 -  PARAMETER   (CHPOC = '-c -O2 -m486')
-+  PARAMETER   (CHPOF = '-c -g -O2 -fno-automatic')
++  PARAMETER   (CHPOF = '-c -g -O -fno-automatic')
 +  PARAMETER   (CHPOC = '-c -g -O2')
PARAMETER   (CHPOA = ' ')
  
diff -Naur 
cernlib-20061220+dfsg3.original/debian/patches/304-update-Imake-config-files.dpatch
 cernlib-20061220+dfsg3/debian/patches/304-update-Imake-config-files.dpatch
--- 
cernlib-20061220+dfsg3.original/debian/patches/304-update-Imake-config-files.dpatch
 2015-09-09 01:24:30.0 +
+++ cernlib-20061220+dfsg3/debian/patches/304-update-Imake-config-files.dpatch  
2019-02-03 21:47:38.208869466 +
@@ -1794,7 +1794,7 @@
 +
 +#ifdef AMD64Architecture
 +# ifndef OptimizationLevel
-+#  define OptimizationLevel   -O3
++#  define OptimizationLevel   -O
 +# endif
 +# ifndef OptimizedCDebugFlags
 +#  define OptimizedCDebugFlags  OptimizationLevel


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cernlib
Source-Version: 20061220+dfsg3-4.4

We believe that the bug you reported is fixed in the latest version of
cernlib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 922...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated cernlib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED 

Processed: Re: Bug#922461: CVE-2018-20124

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 1:3.1+dfsg-4
Bug #922461 [src:qemu] CVE-2018-20124
No longer marked as found in versions qemu/1:3.1+dfsg-4.

-- 
922461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921075: marked as done (postfix: Email Address Internationalization (EAI) is missing, breaking UTF8 support (smtputf8_enable))

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 13:07:06 +
with message-id 
and subject line Bug#921075: fixed in postfix 3.3.2-3
has caused the Debian Bug report #921075,
regarding postfix: Email Address Internationalization (EAI) is missing, 
breaking UTF8 support (smtputf8_enable)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 3.3.2-1+b1
Severity: important
Tags: l10n

Dear Maintainer,

Please reinstate EAI support, this is a vital component for modern mailservers.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postfix depends on:
ii  adduser3.118
ii  cpio   2.12+dfsg-6
ii  debconf [debconf-2.0]  1.5.70
ii  dpkg   1.19.2
ii  e2fsprogs  1.44.5-1
ii  libc6  2.28-5
ii  libdb5.3   5.3.28+dfsg1-0.2
ii  libsasl2-2 2.1.27+dfsg-1
ii  libssl1.1  1.1.1a-1
ii  lsb-base   10.2018112800
ii  netbase5.5
ii  ssl-cert   1.0.39

Versions of packages postfix recommends:
ii  python3  3.7.2-1

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]8.1.2-0.20180807cvs-1
ii  dovecot-core [dovecot-common]  2:2.3.4-2~stretch
ii  libsasl2-modules   2.1.27+dfsg-1
pn  postfix-cdb
pn  postfix-doc
pn  postfix-ldap   
pn  postfix-lmdb   
ii  postfix-mysql  3.3.2-1+b1
ii  postfix-pcre   3.3.2-1+b1
pn  postfix-pgsql  
ii  postfix-sqlite 3.3.2-1+b1
ii  procmail   3.22-26
ii  resolvconf 1.79
ii  s-nail [mail-reader]   14.9.11-2
pn  sasl2-bin  
pn  ufw

-- Configuration Files:
/etc/postfix/postfix-files changed [not included]
/etc/ppp/ip-down.d/postfix [Errno 2] No such file or directory: 
'/etc/ppp/ip-down.d/postfix'
/etc/ppp/ip-up.d/postfix [Errno 2] No such file or directory: 
'/etc/ppp/ip-up.d/postfix'

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.3.2-3

We believe that the bug you reported is fixed in the latest version of
postfix, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated postfix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 16 Feb 2019 06:24:34 -0500
Source: postfix
Binary: postfix postfix-cdb postfix-cdb-dbgsym postfix-dbgsym postfix-doc 
postfix-ldap postfix-ldap-dbgsym postfix-lmdb postfix-lmdb-dbgsym postfix-mysql 
postfix-mysql-dbgsym postfix-pcre postfix-pcre-dbgsym postfix-pgsql 
postfix-pgsql-dbgsym postfix-sqlite postfix-sqlite-dbgsym
Architecture: source amd64 all
Version: 3.3.2-3
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Scott Kitterman 
Description:
 postfix- High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-doc - Documentation for Postfix
 postfix-ldap - LDAP map support for Postfix
 postfix-lmdb - LMDB map support for Postfix
 postfix-mysql - MySQL map support for Postfix
 postfix-pcre - PCRE map support for Postfix
 postfix-pgsql - PostgreSQL map support for Postfix
 postfix-sqlite - SQLite map support for Postfix
Closes: 921075
Changes:
 postfix (3.3.2-3) unstable; urgency=medium
 .
   * Add debian/patches/use-pkg-config-for-icu.diff and add pkg-config to
 build-depends so libicu is detected and postfix is built with smtputf8
 support.  Closes: #921075
Checksums-Sha1:
 

Bug#922461: CVE-2018-20124

[Michael Tokarev]

Control: notfound -1 1:3.1+dfsg-4

16.02.2019 15:41, Moritz Muehlenhoff wrote:

Source: qemu
Severity: grave
Tags: security

When rdma was enabled in -3, this also made a fix for CVE-2018-20124 necessary:


Yes indeed.

But since this code has a ton of bugs (not only security) and is generally
quite a bit too "fluxy", I disabled it entirely in -4.


https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg02822.html
https://git.qemu.org/?p=qemu.git;a=commit;h=0e68373cc2b3a063ce067bc0cc3edaf370752890


Note this is pvrdma, an optimized vmware-like device.
RDMA is in migration, not guest visible.

So I think this can be closed, or at least be made unimportant,
b/c is is only applies to the source code, not to the binary
(code is not compiled into binary).

$ cat hw/rdma/Makefile.objs
ifeq ($(CONFIG_PVRDMA),y)
obj-$(CONFIG_PCI) += rdma_utils.o rdma_backend.o rdma_rm.o
obj-$(CONFIG_PCI) += vmw/pvrdma_dev_ring.o vmw/pvrdma_cmd.o \
 vmw/pvrdma_qp_ops.o vmw/pvrdma_main.o
endif


Thanks,

/mjt

Processed: found 922461 in 1:3.1+dfsg-3, found 922461 in 1:3.1+dfsg-4, tagging 922461 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 922461 1:3.1+dfsg-3
Bug #922461 [src:qemu] CVE-2018-20124
Marked as found in versions qemu/1:3.1+dfsg-3.
> found 922461 1:3.1+dfsg-4
Bug #922461 [src:qemu] CVE-2018-20124
Marked as found in versions qemu/1:3.1+dfsg-4.
> tags 922461 + upstream
Bug #922461 [src:qemu] CVE-2018-20124
Added tag(s) upstream.
> forwarded 922461 
> https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg02822.html
Bug #922461 [src:qemu] CVE-2018-20124
Set Bug forwarded-to-address to 
'https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg02822.html'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
922461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fixed 921039 in 2.7.13-2+deb9u3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 921039 2.7.13-2+deb9u3
Bug #921039 {Done: Matthias Klose } [python2.7] CVE-2018-14647
Ignoring request to alter fixed versions of bug #921039 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
921039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921039: marked as done (CVE-2018-14647)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 13:52:04 +0100
with message-id <4e626e28-25df-e844-68f2-63c75c420...@debian.org>
and subject line Re: Bug#921039: CVE-2018-14647
has caused the Debian Bug report #921039,
regarding CVE-2018-14647
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python2.7
Version: 2.7.15-5
Severity: grave
Tags: security

CVE-2018-14647 as fixed in DSA-4306-1 needs to be fixed in testing as well:

https://bugs.python.org/issue34623
https://github.com/python/cpython/commit/18b20bad75b4ff0486940fba4ec680e96e70f3a2

Cheers,
Moritz
 
 
--- End Message ---
--- Begin Message ---
Version: 2.7.15-9

closing again. afaics, this was already applied in -6.--- End Message ---

Bug#920467: marked as done (ngraph-gtk: fails at runtime on 32-bit archs)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 12:50:56 +
with message-id 
and subject line Bug#920467: fixed in ngraph-gtk 6.08.00-1.1
has caused the Debian Bug report #920467,
regarding ngraph-gtk: fails at runtime on 32-bit archs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ngraph-gtk
Version: 6.08.00-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco

Dear maintainers,

Since the upgrade to 6.08.00, ngraph-gtk has been failing its autopkgtests
in Ubuntu on 32-bit architectures (i386 and armhf):

[...]

autopkgtest [00:39:34]: test run-test: [---

(ngraph:2067): dbind-WARNING **: 00:39:37.513: Error retrieving accessibility 
bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus 
was not provided by any .service files
*** stack smashing detected ***:  terminated
Aborted (core dumped)
autopkgtest [00:39:40]: test run-test: ---]
autopkgtest [00:39:43]: test run-test:  - - - - - - - - - - results - - - - - - 
- - - -
run-test FAIL non-zero exit status 134

[...]

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/armhf/n/ngraph-gtk/20181211_004020_9e1b2@/log.gz

This hasn't been reported on the Debian infrastructure because Debian only
regularly runs autopkgtests for the amd64 architecture; however, I can
confirm that the autopkgtests fail the same way if run against the Debian
binaries.  It appears to me that this means the ngraph-gtk package is broken
at runtime on these architectures, so I'm filing this bug at severity
serious.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ngraph-gtk
Source-Version: 6.08.00-1.1

We believe that the bug you reported is fixed in the latest version of
ngraph-gtk, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated ngraph-gtk package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 16 Feb 2019 13:22:16 +0100
Source: ngraph-gtk
Architecture: source
Version: 6.08.00-1.1
Distribution: unstable
Urgency: medium
Maintainer: Koichi Akabe 
Changed-By: Dr. Tobias Quathamer 
Closes: 920467
Changes:
 ngraph-gtk (6.08.00-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix fails at runtime on 32-bit archs. Thanks to
 Bernhard Übelacker . Closes: #920467
Checksums-Sha1:
 c2d95b9640f2986fc735ac2c5131d646e441e1db 3074 ngraph-gtk_6.08.00-1.1.dsc
 8cf0e43c7a9bb91ffa33978b739b45b39be51c9b 12660 
ngraph-gtk_6.08.00-1.1.debian.tar.xz
 20ba565f5bc8290bb01701944b532c912c749b6b 18908 
ngraph-gtk_6.08.00-1.1_amd64.buildinfo
Checksums-Sha256:
 9cf9f3cfd9c288db8939d0e9684288a6f2e607e3f1e800d8de700bd74df50874 3074 
ngraph-gtk_6.08.00-1.1.dsc
 87597e83950a3acc90c43206a19e8a635788285ed8d780e25f72bc6abf50adf3 12660 
ngraph-gtk_6.08.00-1.1.debian.tar.xz
 983aa2ace32cd3fbcbf7439330013c808d6cfc9d7af20887f161bfebb1e2d0bb 18908 
ngraph-gtk_6.08.00-1.1_amd64.buildinfo
Files:
 7cdec0fd053e88b6f0d1f14ee345c043 3074 graphics optional 
ngraph-gtk_6.08.00-1.1.dsc
 4c7fbd2417eb0af48e9381024c6b8f27 12660 graphics optional 
ngraph-gtk_6.08.00-1.1.debian.tar.xz
 a0daf5bcb21d954b66f5fc0ce5388e1a 18908 graphics optional 
ngraph-gtk_6.08.00-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlxoAj4ACgkQEwLx8Dbr
6xnVMA//bFGo6s8KmiSSajJJwIyGT3bt2IF7szwxmW7I121PFxXAmpR5xZKOfTCf
4mNbwkEc/7ZNhCVIp+xppoJm2PQu//khQneTQgtrRoqlrrkzMl5Txqny2d3QVjfZ
CsZP0heDitdmp0ykJtGSN/c7nsT4+r5uypLJIWEyD5nwmn/OMpJWsoM/MOaZH1D+

Bug#921039: CVE-2018-14647

[Matthias Klose]

Version: 2.7.15-9

closing again. afaics, this was already applied in -6.

Bug#922461: CVE-2018-20124

[Moritz Muehlenhoff]

Source: qemu
Severity: grave
Tags: security

When rdma was enabled in -3, this also made a fix for CVE-2018-20124 necessary:

https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg02822.html
https://git.qemu.org/?p=qemu.git;a=commit;h=0e68373cc2b3a063ce067bc0cc3edaf370752890

Cheers,
Moritz

Processed: severity of 874109 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 874109 grave
Bug #874109 [src:pngcrush] pngcrush: CVE-2015-7700
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
874109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 776246 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 776246 grave
Bug #776246 [librsync1] MD4 collision/preimage attacks (CVE-2014-8242)
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
776246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#922451: Bug#921075: Bug#922451: icu-devtools: Removal of icu-config breaks postfix SMTPUTF8 support

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +moreinfo
Bug #921075 [postfix] postfix: Email Address Internationalization (EAI) is 
missing, breaking UTF8 support (smtputf8_enable)
Added tag(s) moreinfo.

-- 
921075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921075: Bug#922451: Bug#921075: Bug#922451: icu-devtools: Removal of icu-config breaks postfix SMTPUTF8 support

[GCS]

Control: tags -1 +moreinfo

On Sat, Feb 16, 2019 at 12:48 PM Scott Kitterman  wrote:
> On Saturday, February 16, 2019 12:00:51 PM László Böszörményi wrote:
> > Postfix is build tested very closely. Now it builds _without_ the
> > NO_EAI flag and links to ICU correctly. Still can't run it (I don't
> > have a server nor VM), but if you may give me a test case showing it
> > might still not work then I will do everything to fix it.
>
> It doesn't work.
 Just for the record, deleted everything and fetched plus patched
postfix from the beginning.

> The easiest way to tell is if you build postfix and it detected libicu
> correctly, the binary will depend on libicu.  From stable:
>
> Depends: libc6 (>= 2.14), libdb5.3, libicu57 (>= 57.1-1~), ...
 Then one of us doing something wrong. For the package in the archives:
Package: postfix
Source: postfix (3.3.2-1)
Version: 3.3.2-1+b1
[...]
Depends: libc6 (>= 2.14), libdb5.3, libsasl2-2 (>= 2.1.27+dfsg),
libssl1.1 (>= 1.1.1), debconf (>= 0.5) | debconf-2.0, netbase, adduser
(>= 3.48), dpkg (>= 1.8.3), lsb-base (>= 3.0-6), ssl-cert, cpio,
e2fsprogs

Indeed, no ICU dependency. But the local NMU of postfix with the patch:
Package: postfix
Status: install ok installed
[...]
Version: 3.3.2-1.1
[...]
Depends: libc6 (>= 2.14), libdb5.3, libicu63 (>= 63.1-1~), libsasl2-2
(>= 2.1.27+dfsg), libssl1.1 (>= 1.1.1), debconf (>= 0.5) |
debconf-2.0, netbase, adduser (>= 3.48), dpkg (>= 1.8.3), lsb-base (>=
3.0-6), ssl-cert, cpio, e2fsprogs

It contains the right ICU dependency.

> This can be verified by installing the package (even in a chroot where it
> won't run) and checking the defaults:
>
> # postconf | grep utf
> smtputf8_autodetect_classes = sendmail, verify
> smtputf8_enable = ${{$compatibility_level} < {1} ? {no} : {yes}}
> strict_smtputf8 = no
 I get the same output with my local NMU in a chroot. If I understand
you correctly, then this is the correct behavior showing SMTPUTF8 is
in place.

Regards,
Laszlo/GCS

Bug#922457: fonts-roboto-hinted: update broke reverse-dependencies without notice

[Markus Koschany]

Package: fonts-roboto-hinted
Version: 2:0~20170802-1
Severity: serious


Dear maintainer,

the recent upload of fonts-roboto broke reverse-dependencies like
renpy because you removed or renamed previously installed files in
fonts-roboto-hinted. I find that less than optimal given that we have
entered the soft freeze for Debian 10. Please revert this change or
provide the missing files again.

Regards,

Markus

Bug#921075: Bug#922451: icu-devtools: Removal of icu-config breaks postfix SMTPUTF8 support

[Scott Kitterman]

On Saturday, February 16, 2019 12:00:51 PM László Böszörményi wrote:
> Control: tags -1 +patch
> 
> On Sat, Feb 16, 2019 at 10:21 AM Scott Kitterman  
wrote:
> > It would have been nice if you had investigated the impact of dropping
> > icu-
> > config.  The postfix build system uses the presence of icu-config to
> > determine if libicu is present (and thus SMTPUTF8 support should be built
> > in).  See #921075.
> 
>  I did build testing and postfix compiled successfully without any
> warning that an important library for its working might be missing.
> I don't have the expertise to fire up test mail servers to investigate
> its functionality in every aspect.
> 
> > In my opinion, postfix is not releasable in its current state.  Please put
> > icu-config back or provide a tested alternative to enable postfix to build
> > correctly.
> 
>  No offense at all, just a note that the fix might take shorter time
> than writing your email. It is attached and you need to add pkg-config
> to your build dependencies.
> Postfix is build tested very closely. Now it builds _without_ the
> NO_EAI flag and links to ICU correctly. Still can't run it (I don't
> have a server nor VM), but if you may give me a test case showing it
> might still not work then I will do everything to fix it.

It doesn't work.

The easiest way to tell is if you build postfix and it detected libicu 
correctly, the binary will depend on libicu.  From stable:

Depends: libc6 (>= 2.14), libdb5.3, libicu57 (>= 57.1-1~), ...

This can be verified by installing the package (even in a chroot where it 
won't run) and checking the defaults:

# postconf | grep utf
smtputf8_autodetect_classes = sendmail, verify
smtputf8_enable = ${{$compatibility_level} < {1} ? {no} : {yes}}
strict_smtputf8 = no

If smtputf8 support is not compiled in, it will be:

# postconf | grep utf
smtputf8_autodetect_classes = sendmail, verify
smtputf8_enable = no
strict_smtputf8 = no

When I built with your patch, I got both indications of no smtputf8 support.

Scott K

Processed: tagging 921075

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 921075 - patch
Bug #921075 [postfix] postfix: Email Address Internationalization (EAI) is 
missing, breaking UTF8 support (smtputf8_enable)
Removed tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
921075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921370: marked as done (Not suitable for buster, package probably unmaintained)

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 11:40:57 +
with message-id 
and subject line Bug#921370: fixed in yamm3 1.1.0+dfsg1-2
has caused the Debian Bug report #921370,
regarding Not suitable for buster, package probably unmaintained
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yamm3
Version: 1.1.0+dfsg1-1
Severity: serious

Dear all,

In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.

Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked by someone with more involvement in
Javascript packaging than me. Thanks!

light+love,
Mike


-- System Information:
Debian Release: 9.7
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: yamm3
Source-Version: 1.1.0+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
yamm3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated yamm3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Feb 2019 08:36:00 +0530
Source: yamm3
Binary: libjs-yamm3
Architecture: source
Version: 1.1.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Utkarsh Gupta 
Closes: 921370
Description: 
 libjs-yamm3 - Yet another megamenu for Bootstrap 3 from Twitter
Changes:
 yamm3 (1.1.0+dfsg1-2) unstable; urgency=medium
 .
   [ Xavier Guimard ]
   * Bump debhelper compatibility level to 11
   * Declare compliance with policy 4.3.0
   * Change section to javascript
   * Change priority to optional
   * Update VCS fields to salsa
 .
   [ Utkarsh Gupta ]
   * Add myself as an uploader (Closes: #921370)
   * Add d/upstream/metadata
   * Re-write d/rules
   * Update d/copyright
 .
   [ Xavier Guimard ]
   * Add javascript-common in recommended dependencies
Checksums-Sha1: 
 28e2ce1f658f6a6eaebb65d87a74245a3fa29e1c 1939 yamm3_1.1.0+dfsg1-2.dsc
 57d67eadf0df70ffad3a2121ea77e29f78252778 2280 yamm3_1.1.0+dfsg1-2.debian.tar.xz
Checksums-Sha256: 
 222e235467c55f3f25a217dc4ae35910e196e5d52c3099bd3c8f5a74811c09c3 1939 
yamm3_1.1.0+dfsg1-2.dsc
 3a97b5af1add63a66394a2a2c45d5369d083961e6a6fe25d716c0d90321d0b4d 2280 
yamm3_1.1.0+dfsg1-2.debian.tar.xz
Files: 
 d7d21d2e311a8bc1eea08c2ff96764f6 1939 javascript optional 
yamm3_1.1.0+dfsg1-2.dsc
 0448b02d00978bdff863770f6d8c8d0a 2280 javascript optional 
yamm3_1.1.0+dfsg1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxn3m4ACgkQ9tdMp8mZ
7ukENBAAjTNV7dFqDBoM99JUeGAhc+gTGz6RQNzcIFwwdS96TTZ8ZlXYbtJzmt9Y
PkXusJX3944VR970KH0UYL4eU4HNSqWqhSWcLL7KgwJ/CoaO5IQ92uVynVYjvKx8
ycZX8O2mzWro1dGczBHJO6GTqAZ7W7QNIH1KmBirH4QyarhFcmXDES0sSxrB6g3H
e2s/Z5stljiDgH9H1de6lVKYkQMR1dV2QuoaNCDIyHXVouo85k9IrKCSKB4KZptR
mqorS6Jwg54+XFKwFZBR31fJ0DCR0nEeq1El1Ow0nVTMS4xyy46n8QwLVJEvHt0s
6qY4n/rThfsYkr+qfjg6fkBNuTdMWJCicMznmZfa7IapJ7CmmH06QUClwJl98PdH
aFL8ypU+y0xmC2U5USHjqx4mKiAwRGpZkcQj28gqUEpXnhcviqDUotD26MM3nqrq
NdhjgOk9VyApPsBEQBWJk3Cr1L3YMDG8TyTmBjm6c5vEtpeg2NfJe7AYkNUzqIO5
/YskL4aydUNUHCaQNGzF2sm1lDSjcd+L4PDesAWdhI2wohqbT1gElOGz9DvMrS0j
sIyAo2YIyln9+20kHajjo3ztzfjIsGOJbnE+8u1AEdITGkqq7YrPYrEwIxrIk5L/
6ip7kdshA8shft81GKxzRdkiFUmGeg8at3zTb1FWQyi6zQB0fmk=
=Upib
-END PGP SIGNATURE End Message ---

Bug#922453: cernlib: fortran modules must be compiled with no stronger optimization than -O1 (aka -O)

[Gilles Filippini]

Hi,

On Sat, 16 Feb 2019 10:27:43 +0100 Gilles Filippini  wrote:
> Source: cernlib
> Version: 20061220+dfsg3-4.3
> Severity: grave
> Justification: renders package unusable
> Tags: patch
> 
> 
>  Message transféré 
> Sujet : cernlib (20061220+dfsg3-4.3build1) misbehaves on x86_64
> Date : Mon, 4 Feb 2019 00:52:08 +0100
> De : Jacek M. Holeczek 
> Pour : Matthias Klose , Gilles Filippini 
> 
> Hi,
> I tried to use the cernlib related executables on an Ubuntu 18.04 /
> x86_64 / gcc 7.3.0.
> I have found that the "pawX11" misbehaves.
> The problem is related to the used fortran optimization flag.
> By default it is now "-O3" but this is producing misbehaving libraries.
> I tried to rebuild everything using "-O2" but they still misbehaved.
> Finally, after I switched to "-O" (i.e. "-O1"), they started to behave
> properly.
> Please find attached a small patch file which tries to ensure that the
> fortran source code will be compiled with "-O" (and not "-O3" nor "-O2").

The first hunk of the provided patch should be dropped. It addresses a
temporary Ubuntu fix for #853345 now closed.

Attaching the updated patch.

Thanks,

_g.

diff -Naur 
cernlib-20061220+dfsg3.original/debian/patches/126-fix-patchy-compile-flags.dpatch
 cernlib-20061220+dfsg3/debian/patches/126-fix-patchy-compile-flags.dpatch
--- 
cernlib-20061220+dfsg3.original/debian/patches/126-fix-patchy-compile-flags.dpatch
  2013-08-24 09:16:07.0 +
+++ cernlib-20061220+dfsg3/debian/patches/126-fix-patchy-compile-flags.dpatch   
2019-02-03 21:48:36.151806615 +
@@ -76,7 +76,7 @@
  
 -  PARAMETER   (CHPOF = '-c -O -fno-automatic')
 -  PARAMETER   (CHPOC = '-c -O2 -m486')
-+  PARAMETER   (CHPOF = '-c -g -O2 -fno-automatic')
++  PARAMETER   (CHPOF = '-c -g -O -fno-automatic')
 +  PARAMETER   (CHPOC = '-c -g -O2')
PARAMETER   (CHPOA = ' ')
  
diff -Naur 
cernlib-20061220+dfsg3.original/debian/patches/304-update-Imake-config-files.dpatch
 cernlib-20061220+dfsg3/debian/patches/304-update-Imake-config-files.dpatch
--- 
cernlib-20061220+dfsg3.original/debian/patches/304-update-Imake-config-files.dpatch
 2015-09-09 01:24:30.0 +
+++ cernlib-20061220+dfsg3/debian/patches/304-update-Imake-config-files.dpatch  
2019-02-03 21:47:38.208869466 +
@@ -1794,7 +1794,7 @@
 +
 +#ifdef AMD64Architecture
 +# ifndef OptimizationLevel
-+#  define OptimizationLevel   -O3
++#  define OptimizationLevel   -O
 +# endif
 +# ifndef OptimizedCDebugFlags
 +#  define OptimizedCDebugFlags  OptimizationLevel


signature.asc
Description: OpenPGP digital signature

Bug#921075: Bug#922451: icu-devtools: Removal of icu-config breaks postfix SMTPUTF8 support

[GCS]

Control: tags -1 +patch

On Sat, Feb 16, 2019 at 10:21 AM Scott Kitterman  wrote:
> It would have been nice if you had investigated the impact of dropping icu-
> config.  The postfix build system uses the presence of icu-config to determine
> if libicu is present (and thus SMTPUTF8 support should be built in).  See
> #921075.
 I did build testing and postfix compiled successfully without any
warning that an important library for its working might be missing.
I don't have the expertise to fire up test mail servers to investigate
its functionality in every aspect.

> In my opinion, postfix is not releasable in its current state.  Please put
> icu-config back or provide a tested alternative to enable postfix to build
> correctly.
 No offense at all, just a note that the fix might take shorter time
than writing your email. It is attached and you need to add pkg-config
to your build dependencies.
Postfix is build tested very closely. Now it builds _without_ the
NO_EAI flag and links to ICU correctly. Still can't run it (I don't
have a server nor VM), but if you may give me a test case showing it
might still not work then I will do everything to fix it.

Regards,
Laszlo/GCS
--- postfix-3.3.2.orig/makedefs
+++ postfix-3.3.2/makedefs
@@ -802,8 +802,8 @@ esac
 #
 case "$CCARGS" in
 *-DNO_EAI*) CCARGS="$CCARGS "'-DDEF_SMTPUTF8_ENABLE=\"no\"';;
-	 *) icu_cppflags=`(icu-config --cppflags) 2>/dev/null` && {
-		icu_ldflags=`(icu-config --ldflags) 2>/dev/null` && {
+	 *) icu_cppflags=`(pkg-config --cflags icu-i18n) 2>/dev/null` && {
+		icu_ldflags=`(pkg-config --libs icu-i18n) 2>/dev/null` && {
 		trap 'rm -f makedefs.test makedefs.test.[co]' 1 2 3 15
 		cat >makedefs.test.c <<'EOF'
 #include 

Processed: Re: Bug#922451: icu-devtools: Removal of icu-config breaks postfix SMTPUTF8 support

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #921075 [postfix] postfix: Email Address Internationalization (EAI) is 
missing, breaking UTF8 support (smtputf8_enable)
Added tag(s) patch.

-- 
921075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fixed 913159 in 3.50

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 913159 3.50
Bug #913159 [task-kannada-desktop] task-kannada-desktop: uninstallable on mips 
and mipsel
Marked as fixed in versions tasksel/3.50.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
913159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#922453: Fwd: cernlib (20061220+dfsg3-4.3build1) misbehaves on x86_64

[Gilles Filippini]

 Message transféré 
Sujet : Re: cernlib (20061220+dfsg3-4.3build1) misbehaves on x86_64
Date : Wed, 13 Feb 2019 09:58:12 +0100
De : Jacek M. Holeczek 
Pour : Matthias Klose , Gilles Filippini 

Dear Sirs,
these are very old problems which nobody cares about.
There is a bug report from 2014:

https://bugs.launchpad.net/ubuntu/+source/paw/+bug/1354692

I myself was notified about these problems (by my colleague) in 2017.
In that time, I found that your cernlib was broken on "Ubuntu 16.04 /
x86_64 " and "Ubuntu 16.10 / x86_64". However, the forthcoming (in that
time) "Ubuntu 17.10 / x86_64" seemed to be free from these problems. So
I started to advice people to move to this newer distribution (in "beta"
in that time), even though, I myself use the "monolithic" CERNLIB 2005
distribution.
It turns out, however, that I was wrong and these problems are still
there in "Ubuntu 18.04 / x86_64".

In general, the current status (for your cernlib compiled with "-O3" or
"-O2") is that there are severe problems with "ntuples". One cannot
properly create "ntuples", neither "memory resident" nor "disk
resident", in paw. In both cases, only the first variable has proper
values, the remaining variables are always set to 0 (well, usually,
sometimes another value appears).
Old "disk resident ntuples" (created with another properly working
cernlib versions) are sometimes retrieved properly, but sometimes also
this fails (that's what the old bug report from 2014 is talking about).

So, I tried to leave your "cernlib-20061220" libraries compiled with the
default "-O3" and rebuild your "paw-2.14.04" with "-O0" but it did not
help (i.e. the problems really originate in the "cernlib-20061220"
package, not in "paw-2.14.04").

Note that the original cernlib was always built with "-O". More
aggressive compiler optimizations were known to break it.

You can find my instructions here:

https://www-zeuthen.desy.de/linear_collider/cernlib/new/cernlib_2005.html

Last, but not least. It seems I cannot file a bug report "anonymously".
Your bug reporting system tries to force me to create and register a new
account in order to file a bug report. I'm sick of such behavior. I
already have tens of account somewhere there. I won't create another one
just for a simple bug report (when nobody cares about 5 years old bugs
anyhow).

Best regards,
Jacek.




signature.asc
Description: OpenPGP digital signature

Bug#922455: pinfo: malloc(): invalid size (unsorted)

[Jakub Wilk]

Package: pinfo
Version: 0.6.12-2
Severity: grave

pinfo doesn't start:

  $ pinfo
  Przemek's Info Viewer v0.6.12
  malloc(): invalid size (unsorted)
  Aborted

Valgrind suggests some memory corruption happened:

  Syscall param stat64(file_name) points to unaddressable byte(s)
 at 0x49FE605: __xstat64@@GLIBC_2.2 (xstat64.c:35)
 by 0x10DCD3: stat (stat.h:455)
 by 0x10DCD3: initpaths (filehandling_functions.c:1042)
 by 0x10AAE8: main (pinfo.c:248)
   Address 0x0 is not stack'd, malloc'd or (recently) free'd

  Invalid write of size 4
 at 0x10DE6A: initpaths (filehandling_functions.c:1051)
 by 0x10AAE8: main (pinfo.c:248)
   Address 0x4b008a8 is 0 bytes after a block of size 96 alloc'd
 at 0x4836A16: calloc (in 
/usr/lib/i386-linux-gnu/valgrind/vgpreload_memcheck-x86-linux.so)
 by 0x118C69: xmalloc (utils.c:110)
 by 0x10DC7F: initpaths (filehandling_functions.c:1036)
 by 0x10AAE8: main (pinfo.c:248)

  Invalid write of size 4
 at 0x10DE70: initpaths (filehandling_functions.c:1051)
 by 0x10AAE8: main (pinfo.c:248)
   Address 0x4b008ac is 4 bytes after a block of size 96 alloc'd
 at 0x4836A16: calloc (in 
/usr/lib/i386-linux-gnu/valgrind/vgpreload_memcheck-x86-linux.so)
 by 0x118C69: xmalloc (utils.c:110)
 by 0x10DC7F: initpaths (filehandling_functions.c:1036)
 by 0x10AAE8: main (pinfo.c:248)

  ...


-- System Information:
Architecture: i386

Versions of packages pinfo depends on:
ii  libc6 2.28-7
ii  libncursesw6  6.1+20181013-2
ii  libreadline7  7.0-5
ii  libtinfo6 6.1+20181013-2
ii  install-info  6.5.0.dfsg.1-4+b1

--
Jakub Wilk

Bug#870406: Removal from testing

[Joachim Reichel]

Due to bugs 870406 and 887057 the following packages are scheduled for removal
from testing on 2019-03-11:

gjay, mp3cd, mp3roaster, mpg321, normalize-audio, ripit, terminatorx

Is anyone working on these bugs?

  Joachim

Processed: Source packages paw, mclibs, geant321 have to be rebuilt as well

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 922453 src:paw src:mclibs src:geant321
Bug #922453 [src:cernlib] cernlib: fortran modules must be compiled with no 
stronger optimization than -O1 (aka -O)
Added indication that 922453 affects src:paw, src:mclibs, and src:geant321
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
922453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#922453: cernlib: fortran modules must be compiled with no stronger optimization than -O1 (aka -O)

[Gilles Filippini]

Source: cernlib
Version: 20061220+dfsg3-4.3
Severity: grave
Justification: renders package unusable
Tags: patch


 Message transféré 
Sujet : cernlib (20061220+dfsg3-4.3build1) misbehaves on x86_64
Date : Mon, 4 Feb 2019 00:52:08 +0100
De : Jacek M. Holeczek 
Pour : Matthias Klose , Gilles Filippini 

Hi,
I tried to use the cernlib related executables on an Ubuntu 18.04 /
x86_64 / gcc 7.3.0.
I have found that the "pawX11" misbehaves.
The problem is related to the used fortran optimization flag.
By default it is now "-O3" but this is producing misbehaving libraries.
I tried to rebuild everything using "-O2" but they still misbehaved.
Finally, after I switched to "-O" (i.e. "-O1"), they started to behave
properly.
Please find attached a small patch file which tries to ensure that the
fortran source code will be compiled with "-O" (and not "-O3" nor "-O2").
Hope it helps,
Best regards,
Jacek.

diff -Naur 
cernlib-20061220+dfsg3.original/debian/patches/102-dont-optimize-some-code.dpatch
 cernlib-20061220+dfsg3/debian/patches/102-dont-optimize-some-code.dpatch
--- 
cernlib-20061220+dfsg3.original/debian/patches/102-dont-optimize-some-code.dpatch
   2017-08-06 19:23:39.0 +
+++ cernlib-20061220+dfsg3/debian/patches/102-dont-optimize-some-code.dpatch
2019-02-03 21:49:52.638404057 +
@@ -20,7 +20,7 @@
 +#endif
 +
 +/* GCC 7 on 64bit targets, see https://gcc.gnu.org/PR81723 */
-+SpecialFortranLibObjectRule(cwerf64,cwerf64,-O2,NullParameter)
++SpecialFortranLibObjectRule(cwerf64,cwerf64,-O,NullParameter)
 diff -urNad cernlib-2006.dfsg.2~/src/mathlib/gen/d/Imakefile 
cernlib-2006.dfsg.2/src/mathlib/gen/d/Imakefile
 --- cernlib-2006.dfsg.2~/src/mathlib/gen/d/Imakefile   1996-06-12 
08:25:38.0 -0700
 +++ cernlib-2006.dfsg.2/src/mathlib/gen/d/Imakefile2008-02-22 
12:06:26.0 -0800
diff -Naur 
cernlib-20061220+dfsg3.original/debian/patches/126-fix-patchy-compile-flags.dpatch
 cernlib-20061220+dfsg3/debian/patches/126-fix-patchy-compile-flags.dpatch
--- 
cernlib-20061220+dfsg3.original/debian/patches/126-fix-patchy-compile-flags.dpatch
  2013-08-24 09:16:07.0 +
+++ cernlib-20061220+dfsg3/debian/patches/126-fix-patchy-compile-flags.dpatch   
2019-02-03 21:48:36.151806615 +
@@ -76,7 +76,7 @@
  
 -  PARAMETER   (CHPOF = '-c -O -fno-automatic')
 -  PARAMETER   (CHPOC = '-c -O2 -m486')
-+  PARAMETER   (CHPOF = '-c -g -O2 -fno-automatic')
++  PARAMETER   (CHPOF = '-c -g -O -fno-automatic')
 +  PARAMETER   (CHPOC = '-c -g -O2')
PARAMETER   (CHPOA = ' ')
  
diff -Naur 
cernlib-20061220+dfsg3.original/debian/patches/304-update-Imake-config-files.dpatch
 cernlib-20061220+dfsg3/debian/patches/304-update-Imake-config-files.dpatch
--- 
cernlib-20061220+dfsg3.original/debian/patches/304-update-Imake-config-files.dpatch
 2015-09-09 01:24:30.0 +
+++ cernlib-20061220+dfsg3/debian/patches/304-update-Imake-config-files.dpatch  
2019-02-03 21:47:38.208869466 +
@@ -1794,7 +1794,7 @@
 +
 +#ifdef AMD64Architecture
 +# ifndef OptimizationLevel
-+#  define OptimizationLevel   -O3
++#  define OptimizationLevel   -O
 +# endif
 +# ifndef OptimizedCDebugFlags
 +#  define OptimizedCDebugFlags  OptimizationLevel


signature.asc
Description: OpenPGP digital signature

Bug#921075: postfix: Email Address Internationalization (EAI) is missing, breaking UTF8 support (smtputf8_enable)

[Scott Kitterman]

On Fri, 01 Feb 2019 11:40:48 +0100 Michiel Hazelhof  
wrote:
> Package: postfix
> Version: 3.3.2-1+b1
> Severity: important
> Tags: l10n
> 
> Dear Maintainer,
> 
> Please reinstate EAI support, this is a vital component for modern 
mailservers.

Thank you for reporting this bug.  It's caused by changes in the icu package 
which causes postfix to not realize libicu is available.  See 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922451 for details.

As one of the maintainers I agree that postfix should not be released this way 
and have raised the severity accordingly.

Scott K

Processed: severity of 921075 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 921075 serious
Bug #921075 [postfix] postfix: Email Address Internationalization (EAI) is 
missing, breaking UTF8 support (smtputf8_enable)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
921075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#922449: autopkgtest with tox fails (and is ineffective)

[Faidon Liambotis]

Package: src:python-static3
Version: 0.7.0-5
Severity: serious

Hi there,

tox's (new) maintainer here. python-static3 uses "tox" as an
autopkgtest, which is currently broken and that holds a newer version of
tox from migrating to testing. (Hence setting the severity to serious)

The use of tox here as an autopkgtest doesn't make a lot of sense to me
for the following reasons:
* This currently relies on the network to work, as it fetches
  dependencies over from pypi. That could be addressed with
  --sitepackages, however.

* This also means that the tests are against dependencies from pypi, not
  the versions in Debian. That's not really a Debian package test then,
  just an upstream test, and I'm not sure what the point of that is --
  presumably upstream is already doing that given they ship a tox.ini?

* In turn, this also means that those tests may fail at any point in
  time, because of changes outside of Debian. I think this is the case
  right now while I was trying to reproduce the debci failure (I get an
  unrelated backtrace from the pypi package "kid").

* Even more to it, this tests against Python versions set by upstream,
  which are currently set to:
envlist = py26, py27, py33, py34, pypy
  The package doesn't build Python 2 binaries, so these are out; it does
  not Build-Depend on pypy so that's out too; and the Python 3 versions
  are not versions that exist in sid/testing. So these tests are really
  not for any of the Python versions shipped in Debian...

* At the end of the day, the upstream tox just has a
commands=python setup.py test []
  ...which could be the command that autopkgtest runs. However, it may
  make more sense to just run that as part of the dh_auto_test step, as
  it runs the upstream tests and not any kind of Debian integration
  tests.

TL;DR: I'd remove the autopkgtest altogether, and make sure that
"python3 setup.py" when the package builds e.g. as part of dh_auto_test.
YMMV :)

Regards,
Faidon

Bug#921823: marked as done (chromium: FTBFS of vaapi_wrapper.cc in i386/armhf (pointer casting))

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 08:39:12 +
with message-id 
and subject line Bug#921823: fixed in chromium 72.0.3626.109-1
has caused the Debian Bug report #921823,
regarding chromium: FTBFS of vaapi_wrapper.cc in i386/armhf (pointer casting)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chromium
Version: 72.0.3626.81-1
Severity: grave
X-Debbugs-CC: 856...@bugs.debian.org

FAILED: obj/media/gpu/vaapi/vaapi/vaapi_wrapper.o
g++ -MMD -MF obj/media/gpu/vaapi/vaapi/vaapi_wrapper.o.d
-DMEDIA_GPU_IMPLEMENTATION -DV8_DEPRECATION_WARNINGS -DUSE_UDEV
-DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
-DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
-D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -DVK_NO_PROTOTYPES
-DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DSK_HAS_PNG_LIBRARY
-DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY
-DSK_VULKAN_HEADER=\"../../skia/config/SkVulkanConfig.h\"
-DSK_VULKAN=1 -DSK_SUPPORT_GPU=1
-DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\"
-DVK_NO_PROTOTYPES -DUSING_SYSTEM_ICU=1
-DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC -DUCHAR_TYPE=uint16_t
-DU_IMPORT=U_EXPORT -DGOOGLE_PROTOBUF_NO_RTTI
-DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD
-DLEVELDB_PLATFORM_CHROMIUM=1 -DLEVELDB_PLATFORM_CHROMIUM=1 -I../..
-Igen -I../../third_party/libyuv/include
-Igen/shim_headers/libevent_shim -Igen/shim_headers/libpng_shim
-Igen/shim_headers/libwebp_shim -Igen/shim_headers/icuuc_shim
-Igen/shim_headers/zlib_shim -I../../third_party/khronos -I../../gpu
-Igen/shim_headers/libdrm_shim -I../../third_party/vulkan/include
-Igen/shim_headers/icui18n_shim -Igen/shim_headers/re2_shim
-Igen/shim_headers/ffmpeg_shim -Igen/shim_headers/libvpx_shim
-Igen/shim_headers/snappy_shim -Igen/shim_headers/opus_shim
-I../../skia/config -I../../skia/ext
-I../../third_party/skia/include/c
-I../../third_party/skia/include/config
-I../../third_party/skia/include/core
-I../../third_party/skia/include/docs
-I../../third_party/skia/include/effects
-I../../third_party/skia/include/encode
-I../../third_party/skia/include/gpu
-I../../third_party/skia/include/pathops
-I../../third_party/skia/include/ports
-I../../third_party/skia/include/utils
-I../../third_party/vulkan/include
-I../../third_party/skia/third_party/vulkanmemoryallocator
-I../../third_party/skia/include/codec
-I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl
-I../../third_party/skia/modules/skottie/include
-I../../third_party/vulkan/include -I../../third_party/ced/src
-I../../third_party/protobuf/src -I../../third_party/mesa_headers
-I../../third_party/libwebm/source -I../../third_party/protobuf/src
-Igen/protoc_out -I../../third_party/leveldatabase
-I../../third_party/leveldatabase/src
-I../../third_party/leveldatabase/src/include -fno-strict-aliasing
--param=ssp-buffer-size=4 -fstack-protector
-Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__=
-funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
-mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -Wall -Wno-psabi
-Wno-unused-local-typedefs -Wno-maybe-uninitialized
-Wno-deprecated-declarations -Wno-comments
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0
-fvisibility=hidden -I/usr/include/glib-2.0
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -std=gnu++14
-Wno-narrowing -fno-exceptions -fno-rtti -fvisibility-inlines-hidden
-Wdate-time -D_FORTIFY_SOURCE=2 -Wno-pedantic -Wno-unused-function
-Wno-unused-variable -Wno-unused-but-set-variable
-Wno-deprecated-declarations  -Wno-return-type
-Wno-misleading-indentation  -Wno-attributes -Wno-subobject-linkage
-Wno-ignored-attributes -Wno-address -Wno-dangling-else
-Wno-class-memaccess -Wno-invalid-offsetof -Wno-packed-not-aligned
-Wno-pedantic -Wno-unused-function -Wno-unused-variable
-Wno-unused-but-set-variable -Wno-deprecated-declarations
-Wno-return-type -Wno-misleading-indentation  -Wno-attributes
-Wno-subobject-linkage  -Wno-ignored-attributes -Wno-address
-Wno-dangling-else -Wno-class-memaccess -Wno-invalid-offsetof
-Wno-packed-not-aligned  -c ../../media/gpu/vaapi/vaapi_wrapper.cc -o