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

[Michael Stapelberg]

On Thu, Feb 7, 2019 at 8:46 AM Scott Kitterman  wrote:

> No.  It's an actual policy violation, so the bug is correct.  I'd leave it
> as is and ask the release team to mark it buster-ignore.
>

Could you kindly point me to where the process is described for this? I’m
not sure what I’d need to do to get it marked buster-ignore. Thanks.


>
> Scott K
>
> On February 7, 2019 7:29:01 AM UTC, Michael Stapelberg <
> stapelb...@debian.org> wrote:
> >On Wed, Feb 6, 2019 at 11:01 PM Scott Kitterman 
> >wrote:
> >
> >> It's not the FTP Team's job to fix policy compliance issues in
> >packages.
> >> If you have a problem with that being a policy must, then you should
> >take
> >> it up with the policy team.
> >>
> >
> >Yeah, I’ll post to #911165
> >
> >
> >>
> >> I completely understand the frustration, but in my own packages I
> >take the
> >> time to do it because Debian policy says it's required, not because I
> >> particularly care about sysvinit.
> >>
> >
> >I don’t think fulfilling the policy for fulfilling the policy’s sake is
> >a
> >good use of anyone’s time.
> >
> >Can we close this bug until someone comes along who actually cares? :)
> >
> >
> >>
> >> Scott K
> >>
> >> On February 6, 2019 9:23:46 PM UTC, Michael Stapelberg <
> >> stapelb...@debian.org> wrote:
> >> >Can you provide a patch if you care about sysvinit please? The Go
> >> >packaging
> >> >team is pretty manpower-constrained and non-systemd is a niche case,
> >so
> >> >any
> >> >help is appreciated. Thanks!
> >> >
> >> >On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman
> >
> >> >wrote:
> >> >
> >> >> Package: prometheus-postfix-exporter
> >> >> Version: 0.1.2-1
> >> >> Severity: serious
> >> >> Justification: Policy 9.11
> >> >>
> >> >> Excerpt from policy 9.11:
> >> >>
> >> >> However, any package integrating with other init systems
> >> >> must also be backwards-compatible with sysvinit by providing a
> >SysV-
> >> >> style init script with the same name as and equivalent
> >functionality
> >> >> to any init-specific job, as this is the only start-up
> >configuration
> >> >> method guaranteed to be supported by all init implementations.
> >> >>
> >> >> The package violates a policy must by not providing s sysvint init
> >> >script.
> >> >>
> >> >> Scott K
> >> >>
> >> >> ___
> >> >> Pkg-go-maintainers mailing list
> >> >> pkg-go-maintain...@alioth-lists.debian.net
> >> >>
> >> >
> >>
> >
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
> >>
>


-- 
Best regards,
Michael

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

[Scott Kitterman]

No.  It's an actual policy violation, so the bug is correct.  I'd leave it as 
is and ask the release team to mark it buster-ignore.

Scott K

On February 7, 2019 7:29:01 AM UTC, Michael Stapelberg  
wrote:
>On Wed, Feb 6, 2019 at 11:01 PM Scott Kitterman 
>wrote:
>
>> It's not the FTP Team's job to fix policy compliance issues in
>packages.
>> If you have a problem with that being a policy must, then you should
>take
>> it up with the policy team.
>>
>
>Yeah, I’ll post to #911165
>
>
>>
>> I completely understand the frustration, but in my own packages I
>take the
>> time to do it because Debian policy says it's required, not because I
>> particularly care about sysvinit.
>>
>
>I don’t think fulfilling the policy for fulfilling the policy’s sake is
>a
>good use of anyone’s time.
>
>Can we close this bug until someone comes along who actually cares? :)
>
>
>>
>> Scott K
>>
>> On February 6, 2019 9:23:46 PM UTC, Michael Stapelberg <
>> stapelb...@debian.org> wrote:
>> >Can you provide a patch if you care about sysvinit please? The Go
>> >packaging
>> >team is pretty manpower-constrained and non-systemd is a niche case,
>so
>> >any
>> >help is appreciated. Thanks!
>> >
>> >On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman
>
>> >wrote:
>> >
>> >> Package: prometheus-postfix-exporter
>> >> Version: 0.1.2-1
>> >> Severity: serious
>> >> Justification: Policy 9.11
>> >>
>> >> Excerpt from policy 9.11:
>> >>
>> >> However, any package integrating with other init systems
>> >> must also be backwards-compatible with sysvinit by providing a
>SysV-
>> >> style init script with the same name as and equivalent
>functionality
>> >> to any init-specific job, as this is the only start-up
>configuration
>> >> method guaranteed to be supported by all init implementations.
>> >>
>> >> The package violates a policy must by not providing s sysvint init
>> >script.
>> >>
>> >> Scott K
>> >>
>> >> ___
>> >> Pkg-go-maintainers mailing list
>> >> pkg-go-maintain...@alioth-lists.debian.net
>> >>
>> >
>>
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
>>

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

[Debian Bug Tracking System]

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

This means that you claim that 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.)


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

Source: qutemol
Version: 0.4.1~cvs2008-10
Tags: help

Qutemol terminates at startup with a segmentation fault when compiled 
with GCC 8.
--- End Message ---
--- Begin Message ---
Source: qutemol
Source-Version: 0.4.1~cvs2008-12

We believe that the bug you reported is fixed in the latest version of
qutemol, 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.
Graham Inggs  (supplier of updated qutemol 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: Thu, 07 Feb 2019 06:30:38 +
Source: qutemol
Binary: qutemol
Architecture: source
Version: 0.4.1~cvs2008-12
Distribution: unstable
Urgency: high
Maintainer: Debichem Team 
Changed-By: Graham Inggs 
Description:
 qutemol- interactive visualization of macromolecules
Closes: 921510
Changes:
 qutemol (0.4.1~cvs2008-12) unstable; urgency=high
 .
   [ Adrian Bunk ]
   * Build with default g++ again, enable all warnings
   * Fix segfault due to not returning true in AOgpu2::init()
 (Closes: #921510)
Checksums-Sha1:
 7233fd8ff179ab0a55e3cf7a669a65be764685a4 2108 qutemol_0.4.1~cvs2008-12.dsc
 0b61e1d348e7bf6ee6652361f2606694b96f3965 25808 
qutemol_0.4.1~cvs2008-12.debian.tar.xz
Checksums-Sha256:
 a4c426bf9621d932f23f0e43d087d06b74de1677f64248de8fa28a40d4d3d081 2108 
qutemol_0.4.1~cvs2008-12.dsc
 1c4733aaab569e0ac9b9b2eb696626808c1f03ad336cc91f6c19e0c7db52b4bc 25808 
qutemol_0.4.1~cvs2008-12.debian.tar.xz
Files:
 09557b8e555e057d1f9ccc4c8e743d0a 2108 science optional 
qutemol_0.4.1~cvs2008-12.dsc
 b3f80a4b1eba44817bfa1f14fa59873b 25808 science optional 
qutemol_0.4.1~cvs2008-12.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAlxb094ACgkQr8/sjmac
4cIO4RAAr6XJHGhaM0ASFQPbALXRBmBr6R4y71E02+xucTKv+5blNhUMAz+V5cJj
fIOrCWto828bfMKlYJAirGSjvXtPBWPwQLLuT+7Ym19WzT+tjubu+SQu0A4uXiMT
Cx1Ov7LfsiOWilQaXbqGjWVwNzSzAXNyO7raiKUps0+iCwZSpcuyHXo8LZIq2YJd
bFhUS+9kjMQZHZRHZzzsnu085LnRkfZ6BtaflS+JchlyxrYZGuV9GHUuZ1rTLAjn
feSIbWxoq1MN+FGUdNS1jez6+dZ+05cLEsvHn1xCEWRdS7p1Ka909enfLwkry8eO
7qaZ8pBveXlu+7p37cok8UCvFofMMoOaLfb78Emz2qdBIpPEHU8m6hA1Yr5up+mO
A9Qokal+ZIAMEygyW234ZplZZ6P+eTFsCmCcdcW3/7ABscJMO8UeMftA7P+otadl
lNp0FpbWZGAZ2kwXCNu5N2pHt1wN0G3iwBIlQRnZbv91RR0f32zz4CT1d4qmQtIb
pfvmOLBhs7PY/fZ4atAH0VXGZkulo4al0HnzgopxDN+lfgqznzsIHzknbXlholuz
Jss49vmqWRbbNYyMjG9Aoa5OjYi11etxMOieSOZXvCeyr86T+TzIBYLY4RDvyJmV
qH7wwvgSSTmFNJv0O57+dzvoSwj1vYjS8BOwJtSk4hKFLzjh81Y=
=ukMC
-END PGP SIGNATURE End Message ---

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

[Michael Stapelberg]

On Wed, Feb 6, 2019 at 11:01 PM Scott Kitterman 
wrote:

> It's not the FTP Team's job to fix policy compliance issues in packages.
> If you have a problem with that being a policy must, then you should take
> it up with the policy team.
>

Yeah, I’ll post to #911165


>
> I completely understand the frustration, but in my own packages I take the
> time to do it because Debian policy says it's required, not because I
> particularly care about sysvinit.
>

I don’t think fulfilling the policy for fulfilling the policy’s sake is a
good use of anyone’s time.

Can we close this bug until someone comes along who actually cares? :)


>
> Scott K
>
> On February 6, 2019 9:23:46 PM UTC, Michael Stapelberg <
> stapelb...@debian.org> wrote:
> >Can you provide a patch if you care about sysvinit please? The Go
> >packaging
> >team is pretty manpower-constrained and non-systemd is a niche case, so
> >any
> >help is appreciated. Thanks!
> >
> >On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman 
> >wrote:
> >
> >> Package: prometheus-postfix-exporter
> >> Version: 0.1.2-1
> >> Severity: serious
> >> Justification: Policy 9.11
> >>
> >> Excerpt from policy 9.11:
> >>
> >> However, any package integrating with other init systems
> >> must also be backwards-compatible with sysvinit by providing a SysV-
> >> style init script with the same name as and equivalent functionality
> >> to any init-specific job, as this is the only start-up configuration
> >> method guaranteed to be supported by all init implementations.
> >>
> >> The package violates a policy must by not providing s sysvint init
> >script.
> >>
> >> Scott K
> >>
> >> ___
> >> Pkg-go-maintainers mailing list
> >> pkg-go-maintain...@alioth-lists.debian.net
> >>
> >
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
>


-- 
Best regards,
Michael

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

[Andreas Tille]

Hi,

On Wed, Feb 06, 2019 at 01:20:48PM +0100, Andreas Tille wrote:
> On Mon, Feb 04, 2019 at 05:26:08PM +0100, Fabian Klötzl wrote:
> > So I improved the upstream libmurmurhash, adapted the package and filed an
> > ITP (#921353). I even managed to locally build mash against the new package.
> > So hereby I kindly ask you to fix the last lintian issue about NMU which I
> > don't fully understand and then maybe sponsor an upload.
> 
> I uploaded to new with my Automake patches and pinged ftpmaster via IRC.

I confirm I've tested mash with the now accepted libmurmurhash.
Unfortunately it does not pass its build time tests any more now that I
rebuild it for uploading.  I get lots of diffs in the expected and
calculated results.  It starts like this:

   dh_auto_test
make -j4 test VERBOSE=1
make[1]: Entering directory '/build/mash-2.1+dfsg'
cd test ; ../mash sketch -o genomes.msh genome1.fna genome2.fna genome3.fna
cd test ; ../mash sketch -r -I reads reads1.fastq reads2.fastq -o reads.msh
Sketching genome1.fna...
Sketching genome2.fna...
Sketching genome3.fna...
Estimated genome size: 127897
Estimated coverage:1.113
Writing to reads.msh...
Writing to genomes.msh...
./mash info -d test/genomes.msh > test/genomes.json
./mash dist test/genomes.msh test/reads.msh > test/genomes.dist
cd test ; ../mash screen genomes.msh reads1.fastq reads2.fastq > screen
Loading genomes.msh...
   1412 distinct hashes.
Streaming from 2 inputs...
./mash info -d test/reads.msh > test/reads.json
diff test/genomes.dist test/ref/genomes.dist
1,3c1,3
< genome1.fna   reads   0.1244911.3814e-218 38/1000
< genome2.fna   reads   0.1402581.1397e-151 27/1000
< genome3.fna   reads   0.1244911.37891e-21838/1000
---
> genome1.fna   reads   0.12101 4.48626e-21441/1000
> genome2.fna   reads   0.12827 2.61074e-18035/1000
> genome3.fna   reads   0.12101 4.45454e-21441/1000
make[1]: *** [Makefile:97: testDist] Error 1
make[1]: *** Waiting for unfinished jobs
diff test/genomes.json test/ref/genomes.json
7c7
<   "hashType" : "MurmurHash3_x86_32",
---
>   "hashType" : "MurmurHash3_x64_128",
18,1017c18,1017
...


I'm stoping here since this this is a suspicious one that might
(or might not) explain all the following diffs.  Any clue how to
solve this?

Kind regards

   Andreas.

-- 
http://fam-tille.de

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

[Debian Bug Tracking System]

Your message dated Thu, 07 Feb 2019 06:49:47 +
with message-id 
and subject line Bug#919256: fixed in dnssec-trigger 0.17+repack-3
has caused the Debian Bug report #919256,
regarding dnssec-trigger: Failed to upgrade: installed dnssec-trigger package 
post-installation script subprocess returned error exit status 1
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.)


-- 
919256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnssec-trigger
Version: 0.17+repack-1
Severity: serious

Setting up dnssec-trigger (0.17+repack-1) ...
Job for dnssec-triggerd.service failed because the control process exited with 
error code.
See "systemctl status dnssec-triggerd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript dnssec-triggerd, action "restart" failed.
# dnssec-triggerd.service - Reconfigure local DNSSEC resolver on connectivity 
changes
   Loaded: loaded (/lib/systemd/system/dnssec-triggerd.service; enabled; vendor 
preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2019-01-14 
07:20:18 CET; 16ms ago
  Process: 29431 ExecStartPre=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--prepare (code=exited, status=0/SUCCESS)
  Process: 29438 ExecStart=/usr/sbin/dnssec-triggerd -d (code=exited, 
status=1/FAILURE)
  Process: 29439 ExecStartPost=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--update_all (code=exited, status=0/SUCCESS)
  Process: 29443 ExecStopPost=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--cleanup (code=exited, status=1/FAILURE)
 Main PID: 29438 (code=exited, status=1/FAILURE)
dpkg: error processing package dnssec-trigger (--configure):
 installed dnssec-trigger package post-installation script subprocess returned 
error exit status 1
Processing triggers for libc-bin (2.28-5) ...
Errors were encountered while processing:
 dnssec-trigger

I said "no" to the new dnssec-trigger.conf, but except comments the only
difference is the search domain setting:

$ diff /etc/dnssec-trigger/dnssec-trigger.conf 
/etc/dnssec-trigger/dnssec-trigger.conf.dpkg-dist 
28c28
< search: "deuxchevaux.org noone.org ethz.ch debian.org"
---
> # search: ""
51c51
< # check-updates: 
---
> # check-updates: no
65a66
> # These relay incoming DNS traffic on the other port numbers to the usual DNS
76a78,86
> 
> # Use VPN servers for all traffic
> # use-vpn-forwarders: no
> 
> # Forward RFC 1918 private addresses to global forwarders
> # use-private-addresses: yes
> 
> # Add domains provided by VPN connections into Unbound forward zones
> # add-wifi-provided-zones: no

The syslog shows again this:

Jan 14 07:18:59 c-cactus2 dnssec-triggerd[22039]: Jan 14 07:18:59 
dnssec-triggerd[22039] error: Error in SSL_CTX use_certificate_file crypto 
error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small

So maybe https://bugs.debian.org/898969 is not fully fixed yet?

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dnssec-trigger depends on:
ii  gir1.2-nm-1.0   1.14.4-4
ii  libc6   2.28-5
ii  libgdk-pixbuf2.0-0  2.38.0+dfsg-7
ii  libglib2.0-02.58.2-3
ii  libgtk2.0-0 2.24.32-3
ii  libldns21.7.0-3.1+b1
ii  libssl1.1   1.1.1a-1
ii  python3 3.7.1-3
ii  python3-gi  3.30.4-1
ii  python3-lockfile1:0.12.2-2
ii  sensible-utils  0.0.12
ii  unbound 1.8.1-1+b1

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- Configuration Files:
/etc/dnssec-trigger/dnssec-trigger.conf changed:
search: "deuxchevaux.org noone.org ethz.ch debian.org"
url: "http://ster.nlnetlabs.nl/hotspot.txt OK"
url: "http://fedoraproject.org/static/hotspot.txt OK"
tcp80: 185.49.140.67
tcp80: 2a04:b900::10:0:0:67
ssl443: 185.49.140.67 
7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF
ssl443: 2a04:b900::10:0:0:67 
7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: 

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has been 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.)


-- 
921227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnssec-trigger
Version: 0.17+repack-2
Severity: grave
Justification: renders package unusable

dnssec-trigger has been crashing for me the last few weeks.  I'm not
sure what triggers it.

Just got around to getting a core file:

Core was generated by `dnssec-triggerd -d'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  string_list_contains (list=, 
value=value@entry=0x55d49c44d0b0 "d.f.ip6.arpa", 
buffer_size=buffer_size@entry=12) at riggerd/string_list.c:90
90  riggerd/string_list.c: No such file or directory.
(gdb) bt full
#0  string_list_contains (list=, 
value=value@entry=0x55d49c44d0b0 "d.f.ip6.arpa", 
buffer_size=buffer_size@entry=12) at riggerd/string_list.c:90
len = 12
iter = 0x707060703050701
#1  0x55d49c441e4a in string_list_contains (list=, 
value=value@entry=0x55d49c44d0b0 "d.f.ip6.arpa", 
buffer_size=buffer_size@entry=12) at riggerd/string_list.c:76
len = 
iter = 
#2  0x55d49c434b23 in nm_connection_list_contains_zone 
(list=list@entry=0x7ffd55ff4400, zone=zone@entry=0x55d49c44d0b0 "d.f.ip6.arpa", 
len=len@entry=12) at riggerd/connection_list.c:99
iter = 0x55d49e0cd3c0
#3  0x55d49c4445f9 in update_connection_zones (connections=0x7ffd55ff43f0) 
at riggerd/svr.c:1002
zone = 
i = 
global_forwarders = {first = 0x0, ownership = LIST_NON_OWNING}
gf_string = 
static_label = 
stored_zones = {dir = 0x55d49c44cf31 "/var/run/dnssec-trigger", path = 
0x55d49c44cf13 "/var/run/dnssec-trigger/zones", path_tmp = 0x55d49c44d518 
"/var/run/dnssec-trigger/zones.tmp", cache = {
first = 0x55d49e0a5bb0}}
forward_zones = {first = 0x55d49e0ce4a0, ownership = LIST_OWNING}
iter = 
static_label = 
stored_zones = 
forward_zones = 
iter = 
zone = 
iter = 
c = 
string_iter = 
zone = 
in_store = 
in_fwd_zones = 
new_fwd_zone = 
global_forwarders = 
gf_string = 
i = 
zone = 
new_zone = 
#4  handle_update_all (json=) at riggerd/svr.c:817
original = {first = 0x0, ownership = LIST_OWNING}
original = 
#5  sslconn_command (sc=) at riggerd/svr.c:1303
header = "DNSTRIG1 "
str = 
header = 
str = 
#6  control_callback (c=, arg=, 
reply_info=, err=0) at riggerd/svr.c:480
s = 
r = 
#7  0x55d49c444a4d in control_callback (c=, arg=, err=, reply_info=) at riggerd/svr.c:380
s = 
r = 
r2 = 
errbuf = 
x = 
#8  0x55d49c438a76 in handle_select (base=base@entry=0x55d49e04d950, 
wait=, wait@entry=0x7ffd55ff4690) at riggerd/mini_event.c:221
bits = 2
r = {fds_bits = {128, 0 }}
w = {fds_bits = {0 }}
ret = 0
i = 7
__func__ = "handle_select"
#9  0x55d49c438cd3 in event_base_dispatch (base=0x55d49e04d950) at 
riggerd/mini_event.c:243
wait = {tv_sec = 8, tv_usec = 977143}
#10 0x55d49c43ae3c in comm_base_dispatch (b=) at 
riggerd/netevent.c:252
retval = 
#11 0x55d49c432cf1 in do_main_work (verb=, nodaemonize=1, 
cfgfile=0x55d49c44c788 "/etc/dnssec-trigger/dnssec-trigger.conf") at 
riggerd/riggerd.c:286
cfg = 0x55d49e04d7c0
svr = 0x55d49e04dc00
cfg = 
svr = 
c2 = 
#12 main (argc=, argv=) at riggerd/riggerd.c:395
c = 
cfgfile = 0x55d49c44c788 "/etc/dnssec-trigger/dnssec-trigger.conf"
nodaemonize = 1
verb = 
uninit_it = 0
winopt = 0x0
(gdb) info registers
rax0xc 12
rbx0x707060703050701   506380110287668993
rcx0x1016
rdx0x55d49c44d0b0  94371643183280
rsi0xc 12
rdi0x55d49c44d0a0  94371643183264
rbp0xc 0xc
rsp0x7ffd55ff4380  0x7ffd55ff4380
r8 0xc 12
r9 0x55d49e0cd360  94371673068384
r100x6 6
r110x246   582
r120x55d49c44d0b0  

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

[Diane Trout]

version: 0.17+repack-3
tag: pending

I have a new version (hopefully uploaded successfully) where I fixed
dnssec-trigger-control-setup to not generate new keys or certificates
if called repeatedly. So now the code to delete small keys should get
called.

I also included upstream's fix for the segfault we were having.
(Also reported as #921227)

Unfortunately a bug #921538 showed up in unbound that is causing my CItests to 
fail 

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

[Trout, Diane E.]

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

This fix worked for me.

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

[Debian Bug Tracking System]

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


-- 
918289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-autoprefixer
Version: 7.2.5-1
Severity: serious
Tags: ftbfs
Control: block -1 by 60 888903

node-autoprefixer build depends on node-js-beautify
that is currently not in buster due to #60 and #888903.
--- End Message ---
--- Begin Message ---
 Forwarded Message 
Subject : [Pkg-javascript-devel] node-js-beautify 1.7.5+dfsg-2 MIGRATED
to testing
Date : Thu, 07 Feb 2019 04:39:24 +
>From : Debian testing watch 
To : node-js-beaut...@packages.debian.org

FYI: The status of the node-js-beautify source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  1.7.5+dfsg-2

-- 
This email is automatically generated once a day.  As the installation
of new packages into testing happens multiple times a day you will
receive later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.--- End Message ---

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

[Debian Bug Tracking System]

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


-- 
918290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-postcss
Version: 6.0.23-1
Severity: serious
Tags: ftbfs
Control: block -1 by 60 888903

node-postcss build depends on node-js-beautify
that is currently not in buster due to #60 and #888903.
--- End Message ---
--- Begin Message ---
 Forwarded Message 
Subject : [Pkg-javascript-devel] node-js-beautify 1.7.5+dfsg-2 MIGRATED
to testing
Date : Thu, 07 Feb 2019 04:39:24 +
>From : Debian testing watch 
To : node-js-beaut...@packages.debian.org

FYI: The status of the node-js-beautify source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  1.7.5+dfsg-2

-- 
This email is automatically generated once a day.  As the installation
of new packages into testing happens multiple times a day you will
receive later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.--- End Message ---

Processed: affects 915584

[Debian Bug Tracking System]

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

> affects 915584 dicoweb
Bug #915584 [python3.7] dicoweb: fails to install with python 3.7
Added indication that 915584 affects dicoweb
> thanks
Stopping processing here.

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

Processed: affects 921195

[Debian Bug Tracking System]

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

> affects 921195 mcabber
Bug #921195 [libloudmouth1-0] libloudmouth1-0: does not support IPv6 (fails 
Squeeze release goal)
Added indication that 921195 affects mcabber
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> affects 916584 -dico
Bug #916584 [src:libpodofo] libpodofo: CVE-2018-11255
Removed indication that 916584 affects dico
> affects 915584 +dico
Bug #915584 [python3.7] dicoweb: fails to install with python 3.7
Added indication that 915584 affects dico
> quit
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> reassign 915584 python3.7
Bug #915584 [dicoweb] dicoweb: fails to install with python 3.7
Bug reassigned from package 'dicoweb' to 'python3.7'.
No longer marked as found in versions dico/2.7-1.
Ignoring request to alter fixed versions of bug #915584 to the same values 
previously set
> affects 916584 +dico
Bug #916584 [src:libpodofo] libpodofo: CVE-2018-11255
Added indication that 916584 affects dico
> quit
Stopping processing here.

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

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

[Frank Heckenbach]

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

OK.

> Maybe it would even be possible to have the applications set a global
> variable, e.g.:
> 
>   enum class Render { Default = 1, Basic };
>   FTGL->setRender(Render  renderType);
> 
> and then the Render() function(s) would dispatch to either
> RenderDefault() or RenderBasic() versions as appropriate?

I generally don't much like global flags, but in this particular
case, it might be the least painful approach.

It wouldn't be foolproof. If two pieces of code, e.g. libraries,
that are used in the same program, use Render() with different
settings of this flag, one of them would do the wrong thing. (And
manually changing this flag every time code from the other library
may be used would be a maintenance nightmare.)

So maybe the following is even easier to implement, while also not
foolproof:

- No RenderDefault() and RenderBasic(), just Render() as is.

- A flag similar to your proposal (though I wouldn't actually call
  it "Render..."; if we aren't renaming the Render functions, we can
  use a more specific name), such as LegacyOpenGLState, and it can
  be a bool actually.

- However, ftgl will only allow setting this flag to one value ever
  (but any number of times, so libraries that expect the same
  setting can work together). I.e., if it's set to false, further
  calls setting it to false will succeed, but a call setting it to
  true will abort, indicating a mix of incompatible code pieces; and
  vice versa.

  If it's never set, if will default to true (legacy behaviour);
  I'll have to accept that.

- In my code I'll set it to false; likewise for others relying on
  this behaviour. (My code actually contains libraries using ftgl,
  so I'll make sure to set it from within the libraries, rather than
  the programs using them.)

- Programs relying on the "old" behaviour need no change
  immediately, but should soon (so for Debian, after the release of
  Buster), add a "true" call. This would be a single line change
  near the start, so easy to do even if it affects a number of
  packages.

- Both kinds of program will need to require ftgl>=2.4.0 because of
  the new call.

- Sometime in the future, I hope I can require setting this flag,
  first with a warning, later with an error if it's not set before
  the first rendering. Provided you've added the call to all
  packages by then, nothing will break.

Cheers,
Frank

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

[Debian Bug Tracking System]

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


-- 
899567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libapache2-mod-nss
Version: 1.0.14-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of libapache2-mod-nss,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package libapache2-mod-nss since the list address
pkg-fedora-ds-maintain...@lists.alioth.debian.org used in the
Maintainer: field was not transferred to the alioth-lists service that
provides a continuation for the lists in the @lists.alioth.debian.org
domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-fedora-ds-maintain...@lists.alioth.debian.org is 10.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.0.14-1+rm

Dear submitter,

as the package libapache2-mod-nss has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/915512

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

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


-- 
918284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librdf-trine-serializer-rdfa-perl
Version: 0.100-1
Severity: serious
Tags: ftbfs
Control: block -1 by 750946

librdf-trine-serializer-rdfa-perl build depends on librdf-rdfa-parser-perl
that is currently not in buster due to #750946.
--- End Message ---
--- Begin Message ---
Source: librdf-trine-serializer-rdfa-perl
Source-Version: 0.100-2

We believe that the bug you reported is fixed in the latest version of
librdf-trine-serializer-rdfa-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 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated 
librdf-trine-serializer-rdfa-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: Thu, 07 Feb 2019 03:52:42 +0100
Source: librdf-trine-serializer-rdfa-perl
Architecture: source
Version: 0.100-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Jonas Smedegaard 
Closes: 918284
Changes:
 librdf-trine-serializer-rdfa-perl (0.100-2) unstable; urgency=medium
 .
   * Add patch 2001 to avoid RDF::RDFa::Parser
 which is unfit for stable release.
 Stop build-depend on librdf-rdfa-parser-perl.
 Closes: Bug#918284. Thanks to Adrian Bunk.
Checksums-Sha1:
 f817ed881b641518baa0352948053bb58326d08e 2440 
librdf-trine-serializer-rdfa-perl_0.100-2.dsc
 62a9f509f61a094ec990f3a1d4179a19ade7b52d 3548 
librdf-trine-serializer-rdfa-perl_0.100-2.debian.tar.xz
 d17a1ed20e2da5f5c3362a0206a1d9ce962776ae 9376 
librdf-trine-serializer-rdfa-perl_0.100-2_amd64.buildinfo
Checksums-Sha256:
 ab1be6e68c49a973f52bf7a967b8f9c006debdb1c94a36909fdc352127ffd9d5 2440 
librdf-trine-serializer-rdfa-perl_0.100-2.dsc
 fc846759cd63946e3563c9534f72d4ffcfbd6bd7522100ecf2a900e187beeb5d 3548 
librdf-trine-serializer-rdfa-perl_0.100-2.debian.tar.xz
 6d60270a201ceb80cb67733709f8e8af7605ac97e4e71fde50ed3a4e26d46ccd 9376 
librdf-trine-serializer-rdfa-perl_0.100-2_amd64.buildinfo
Files:
 f990bf8f92a2f6731a8304e03721fef4 2440 perl optional 
librdf-trine-serializer-rdfa-perl_0.100-2.dsc
 9f8e84a02c52ebcffb9035bd611541dd 3548 perl optional 
librdf-trine-serializer-rdfa-perl_0.100-2.debian.tar.xz
 7fef2b5845273ca9ea840e49ebc066ff 9376 perl optional 
librdf-trine-serializer-rdfa-perl_0.100-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxbngoACgkQLHwxRsGg
ASEZLw//VZYt9fAUAw+kKGNnH8XPSJwD9WuiECCKHQvVAhmjSP2MocAlied/d6OO
fCvBLgop91VmM6+0+X9sgz/PcFiInPFDngM2aG4K7i+Je9J68hlNAOqOJRKsV303
BISHM4ATWfSQfWPeXlGLj9iXi5OV0117UnYA+zsgtsh8ZbknPXeOjGlfcdH0bV+6
cCizJSyuqQ1i1408bDnipxNsFEKyj4Y79r/Uc+zWYuk/XDQj7BP9yEEYtXZWZruF
jWRnqOuvek3CxDs9G/8e9WfOx2UYb1Lryg24EeUyDeEa9i+f/PUq/uesb+VNYT0v
iCgRck2Qi8WMM4EQBy1UUcOUx5mz30SGIUbCEd3N1vunYvvLC4ulRzncL21NZGKR
MBHBUQm/TTI+EifNtq8w00hcp508enh/sPYg3j1Mw4hV0km3XuOwc4DL7QQuqa41
ZBW4Bz7RXNrhx/UFAc+C13YNNwPC5GGFAKY84TAqIS9e6l3lipchYGu4iEBWcswJ
JZMNuC7cAUDTV4a9gNUykHIyvIyHMCy1tg5dD+6za+vsK90kOTvoDtUHKNZlsTom
cKGaScZOIgTiK+pzmX2//ZNfZ9u2kzwvelYBLlf/v/auoLVRZ6d7ySDNRqVH5XoB
+vEBcYU/7BO+OCDoDXdMYSGQYxGvf/l9jj50UpSv+XizHrvVbqE=
=h5qi
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

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

This means that you claim 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.)


-- 
860072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: botan1.10
Version: 1.10.8-2
Severity: important
Tags: patch security upstream

Hi,

the following vulnerability was published for botan1.10.

CVE-2017-2801[0]:
Incorrect comparison in X.509 DN strings

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-2017-2801
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2801
[1] 
https://github.com/randombit/botan/commit/c927101675e5f63fc0bdd93c5a4825adc54323b4

Regards,
Salvatore


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Version: 1.10.17-0.1+rm

Dear submitter,

as the package botan1.10 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/889675

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Thu, 07 Feb 2019 03:17:43 +
with message-id 
and subject line Bug#889675: Removed package(s) from unstable
has caused the Debian Bug report #888089,
regarding botan1.10 EOL
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not 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.)


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

Upstream has announced that security support for botan1.10 will end
latest December 2018. Given the small number of rdepends it might be
wise to get botan1.10 out of testing.

rdepends:

monotone: monotone [amd64 arm64 armel armhf i386 mips mips64el mipsel powerpc 
ppc64el s390x]
ovito: ovito [amd64 arm64 i386 mips mips64el mipsel ppc64el s390x]
qtcreator: qtcreator [amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 
mips mips64el mipsel powerpc ppc64el s390x]

Ondřej, thoughts on this?

Chris



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.10.17-0.1+rm

Dear submitter,

as the package botan1.10 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/889675

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#917582: Please prevent autoremoval of freedombox

[Sunil Mohan Adapa]

Hello,

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

Thank you,

-- 
Sunil



signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Processing control commands:

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

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

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

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #918284 in librdf-trine-serializer-rdfa-perl reported by you has been fixed 
in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/librdf-trine-serializer-rdfa-perl/commit/44ba0b752e41beb44efe3bdd3b1f9af3ee00d9de


Add patch 2001 to avoid RDF::RDFa::Parser unfit for stable release. Stop 
build-depend on librdf-rdfa-parser-perl. Closes: Bug#918284. Thanks to Adrian 
Bunk.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918284

Bug#916921: marked as done (radicale: upgrade to 2.x breaks compatibility with 1.x without any prior warning)

[Debian Bug Tracking System]

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

This means that 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.)


-- 
916921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: radicale
Version: 2.1.11-2
Severity: important

On Debian unstable, Radicale was just upgraded from 1.x to 2.x. Only after
upgrading did I realize that my calendars were not available any more.

As stated on https://radicale.org/1to2/, upgrade to 2.x forces you to use
Python 3, and thus to upgrade mod_wsgi as well. I was using Python 2 version of
mod_wsgi only because it was the default version and it wasn't causing any
problem (Radicale was my only WSGI application).
Moreover, Radicale 2.x can't even use 1.x data files. You must export your
files *before* upgrading.

The Debian package silently ignores all these issues. I think there should be
warning messages and a ad hoc prerm kind of script.

By the way, installing Radicale 1.x and using --export-storage didn't even work
for me. It probably had something to do with my using single iCalendar file
calendars and my /etc/radicale/config was not configured to support this
anymore.

Just in case someone with the same problem as me read this message, here is how
I fixed all this mess.
For each calendar, I unsubscribed in Lightning, created a new calendar through
the web interface, renamed the created directory in
/var/lib/radicale/collections/collection-root// (for some reason,
Radicale uses random hexadecimal strings instead of calendar title, whereas it
is the actual string you have to type in your CalDAV client), subscribed
the newly created calendar in Lightning, and imported the old iCalendar file
from /var/lib/radicale/collections// using the "Events and
Tasks->Import" Lightning menu.
It actually was more straightforward than using the whole export storage thing.
After doing that my other CalDAV clients worked without needing to be
reconfigured.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armel

Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to fr_FR.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages radicale depends on:
ii  adduser  3.118
ii  init-system-helpers  1.56+nmu1
ii  lsb-base 10.2018112800
ii  python3  3.7.1-3
ii  python3-radicale 2.1.11-2

Versions of packages radicale recommends:
ii  ssl-cert  1.0.39

Versions of packages radicale suggests:
ii  apache2 2.4.37-1
ii  apache2-utils   2.4.37-1
pn  libapache2-mod-proxy-uwsgi  
pn  python3-bcrypt  
pn  python3-passlib 
pn  uwsgi   

-- Configuration Files:
/etc/radicale/config changed [not included]

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: radicale
Source-Version: 2.1.11-4

We believe that the bug you reported is fixed in the latest version of
radicale, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated radicale 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: Thu, 07 Feb 2019 02:28:00 +0100
Source: radicale
Architecture: source
Version: 2.1.11-4
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 916921
Changes:
 radicale (2.1.11-4) unstable; urgency=medium
 .
   * Add NEWS entry about incompatible changes to storage format.
 Closes: Bug#916921. Thanks to Bernard Massot.

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

[Debian Bug Tracking System]

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


-- 
918283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librdf-query-client-perl
Version: 0.114-1
Severity: serious
Tags: ftbfs buster sid
Control: block -1 by 750946

librdf-query-client-perl build depends on libhttp-lrdd-perl
that is currently not in buster due to #750946.
--- End Message ---
--- Begin Message ---
Source: librdf-query-client-perl
Source-Version: 0.114-2

We believe that the bug you reported is fixed in the latest version of
librdf-query-client-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 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated librdf-query-client-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: Thu, 07 Feb 2019 03:16:58 +0100
Source: librdf-query-client-perl
Architecture: source
Version: 0.114-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Jonas Smedegaard 
Closes: 918283
Changes:
 librdf-query-client-perl (0.114-2) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * Update URLs from {search,www}.cpan.org to MetaCPAN.
   * Update GitHub URLs to use HTTPS.
 .
   [ Jonas Smedegaard ]
   * Simplify rules
 Stop build-depend on devscripts.
   * Use short-form dh sequencer (not cdbs).
 Stop build-depend on cdbs dh-buildinfo.
   * Stop build-depend on, and suggest (not recommend) libhttp-lrdd-perl.
 Closes: Bug#918283. Thanks to Adrian Bunk.
   * Relax to (build-)depend unversioned on libnamespace-clean-perl:
 Needed version satisfied even in oldstable.
   * Set Rules-Requires-Root: no.
   * Enable autopkgtest.
   * Declare compliance with Debian Policy 4.3.0.
   * Update copyright info:
 + Use License-Grant and License-Reference fields.
   Thanks to Ben Finney.
 + Use https protocol in file format URL.
 + Extend coverage of packaging.
   * Update watch file:
 + Bump to file format 4.
 + Track only metacpan.
 + Rewrite usage comment.
 + Use substitution strings.
   * Update git-buildpackage config: Ignore any .git* files.
   * Bump debhelper compatibility level to 9.
   * Add lintian overrides regarding License-Reference.
Checksums-Sha1:
 d5d681a88230168601577e24daf35304cf1f7d24 2305 
librdf-query-client-perl_0.114-2.dsc
 28390ffbe75b0e2b2bbae8424e62ffb0f08f6582 4988 
librdf-query-client-perl_0.114-2.debian.tar.xz
 2c6fe6a62842f5e2d260e28fe05182766a7d5bc2 8666 
librdf-query-client-perl_0.114-2_amd64.buildinfo
Checksums-Sha256:
 7e289c393ecd4270351bdde0a2b684334a7b5ac6fb3b467d47b8de0757e52e5f 2305 
librdf-query-client-perl_0.114-2.dsc
 a9d37ca046e27b4137965557edd6cf69a735122f12b6a03d278b09facaa3d08a 4988 
librdf-query-client-perl_0.114-2.debian.tar.xz
 83dd648a89691b1bbecd9f6159382ab598f1a6d5804638e7b6aff552a90e1079 8666 
librdf-query-client-perl_0.114-2_amd64.buildinfo
Files:
 f38605bf80ddae6cbacabc8a296c7ea9 2305 perl optional 
librdf-query-client-perl_0.114-2.dsc
 f45ab92c6cf4ed55d3e17f1d1d3a8ec4 4988 perl optional 
librdf-query-client-perl_0.114-2.debian.tar.xz
 1de1901a692e6e5f041966d0f34c620a 8666 perl optional 
librdf-query-client-perl_0.114-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxblg0ACgkQLHwxRsGg
ASHciRAAqClCLnDRhvrIcEeozfcfdYB4vlXAxTCs7mb35Wp0GfUNnxacySaqkn5P
LJks8uFCsxWRAUQzo0AZL3gIalIjK41ovF0tUhIr4s/AKGeYSFqMFHZUraDZ8m0z
TDXeGq8UmYZkuz96Q4puLBnTPnFd3F9GfvWZ0dYcxfCEHCSFma9W26t5mXZiNCUI
UZFAp99k2QwD/BuJdqJ6/CD3SGR3SBdJ3KLs6qbcdHFCQq/8Rl6RqlkvMKZekE8B
9h/yRanYMn1xiT49s9eRD5L2XEOCYoMW6PfPrbweZNZl56rkrynR9Bb7s1E2Dil/
62rnQ33Y5V1iGbSM4ec7YUETdSnyKjOcDZaoHrEBDpl83ue4d0io7mivQ4jgr6zV

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

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #918283 in librdf-query-client-perl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/librdf-query-client-perl/commit/431ef56b42bbedbc373b9e915d1396ba633258dc


Stop build-depend on, and suggest (not recommend) libhttp-lrdd-perl. Closes: 
Bug#918283. Thanks to Adrian Bunk.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918283

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918283 [src:librdf-query-client-perl] librdf-query-client-perl build 
depends on libhttp-lrdd-perl that is currently not in buster
Added tag(s) pending.

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

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

[Debian Bug Tracking System]

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


-- 
921580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-google-cloud
Version: 0.9.0-8
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-google-cloud/1861825/log.gz

...
# cloud.google.com/go/profiler/mocks
src/cloud.google.com/go/profiler/mocks/mock_profiler_client.go:49:86: 
undefined: cloudprofiler.CreateOfflineProfileRequest
...
--- End Message ---
--- Begin Message ---
Source: golang-google-cloud
Source-Version: 0.9.0-9

We believe that the bug you reported is fixed in the latest version of
golang-google-cloud, 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.
Stephen Gelman  (supplier of updated golang-google-cloud 
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: Wed, 06 Feb 2019 19:02:17 -0600
Source: golang-google-cloud
Architecture: source
Version: 0.9.0-9
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 
Changed-By: Stephen Gelman 
Closes: 921580
Changes:
 golang-google-cloud (0.9.0-9) unstable; urgency=high
 .
   * Team upload.
   * Update golang-google-genproto-dev dependency to 0.0~git20190111.db91494
 (Closes: #921580)
Checksums-Sha1:
 6ac2ad87418b850170516bd38f1dda46e19792b2 2774 golang-google-cloud_0.9.0-9.dsc
 6f8d4916958676f24c52785d9d71f73881200fb2 15136 
golang-google-cloud_0.9.0-9.debian.tar.xz
 64b6cfe4e1dd468786227fbaea557e36d3e763c9 7017 
golang-google-cloud_0.9.0-9_amd64.buildinfo
Checksums-Sha256:
 29084cda31852b0b645e6712e28edcaac610ba91202993387159fad2dfaddb30 2774 
golang-google-cloud_0.9.0-9.dsc
 2a5673ecda8d3fe1b5c4e03018899571ca3e6a188b9f14748c05cf9e225dc464 15136 
golang-google-cloud_0.9.0-9.debian.tar.xz
 9aa83f253621bc6e2fa3f8aa74dc7d7d8691a2256426464c2447a9cf0007f5f5 7017 
golang-google-cloud_0.9.0-9_amd64.buildinfo
Files:
 1e4075e540acebf098f5c321d887d8b2 2774 devel optional 
golang-google-cloud_0.9.0-9.dsc
 f1bf991b0c2934ab39efaca17b28c26d 15136 devel optional 
golang-google-cloud_0.9.0-9.debian.tar.xz
 152c7e461a386d596bd7234d41d1334c 7017 devel optional 
golang-google-cloud_0.9.0-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPwDop1BN06KlsbfijqM4hED8f1wFAlxbhUMSHHNzZ2VsbUBk
ZWJpYW4ub3JnAAoJEI6jOIRA/H9cnngP/A7T0jeblEj4ed06Hvh4JFn2+umvQX+S
Pf8hzEy88ShcJRjkelqvlJkec4F/DQGJOSkp1j7207Pf5r04ImWDh3Z+pv1AbwYs
m56uQ7deaZF+W1MqgUxjYhnxUdN0KFcSfgXzbxkZ3I7PxZo9ub2nhQ/6H8HelpJW
fR4LOUB43HHkgUGU7b6Q+HzclRYdJMxkv+PW7HEzexrDCHYlg/VIHlS9xDL9p3Ik
umII5UwL+9p1CCaoV4tDY+3HL+yfTcLRqB//oTO/O9YmGgYt6CQYLKcvop8fGSBU
eSszIPUpKVxsIGYSzwZRLzbT7TNdY8A47gGnoFD1H80ClD1+CgvCQooQUitjEATX
H4MhSQ2yLgV5FyKYAwzbbfe8SNwUo3EyfxGT0AvjcXTk1P1EBmcXOPej2pY83Oi1
fGGJwRtaN98u/fDkoeJwoVhbSRotaa+PpRsNlhfeQXadGOosczB34PfR/0yIC+r3
bcp/+NHp2xuGxk0PXDOyVPF8gx9O2nuVevMAfJsrqALbFLkjcR7VYQrTCFTLe8X6
HCo0kut207siwMYkMF+0VDPo6r7IlAEvveT5nDSxeTkwU+L2Opt7FQW+985lpzMD
IkRmXHWicP7CJSYw+0tT1O7kMJz011aHUTmKWRejQrqTmYGS9XuPdrXEpe6UlSzH
nSRW94WASwrF
=u5cD
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Thu, 07 Feb 2019 01:34:10 +
with message-id 
and subject line Bug#819705: fixed in b43-fwcutter 1:019-4
has caused the Debian Bug report #819705,
regarding firmware-b43-installer: Brittle handling of /lib/firmware/b43, can 
readily conflict with other packages, improper removal during *postrm*
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.)


-- 
819705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-b43-installer
Version: 1:019-2
Severity: important
Tags: patch

I'm fearful this should be marked "serious", rather than "important".

firmware-b43-installer's handling of /lib/firmware/b43 is very brittle.
Notably it doesn't register the contents of the directory with `dpkg`.
Worse, during *postrm* it does an `rm -rf /lib/firmware/b43`.  As a
result, even a package that merely conflicts with firmware-b43-installer
will be broken since the rm will be done *after* that package is
installed.

The attached patch attempts to remedy this in two ways.  First, it
creates a file in /lib/firmware/b43 cataloging the firmware files that
have been installed.  Second, during removal the list of files is run
past `dpkg-query -S` to ensure nothing taken over by other packages is
removed.

A better solution is bug #819136.  Making the firmware into a package
which can then be installed using `dpkg` and thus removal is safely
handled.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445


>From 12387d36ac959d6355af15103c13681afda56298 Mon Sep 17 00:00:00 2001
From: Elliott Mitchell 
Date: Thu, 31 Mar 2016 17:33:23 -0700
Subject: [PATCH 01/10] Implement catalog of firmware files installed

This allows for targeted removal of downloaded firmware files, instead of
needing to remove the whole directory.  Also pass paths to be removed
through `dpkg-query -S`, increasing safety of removals.  This is much
safer and allows for other features.
---
 debian/firmware-b43-installer.postinst |   33 +---
 debian/firmware-b43-installer.postrm   |   15 ---
 debian/firmware-b43-installer.prerm|   28 +++
 3 files changed, 54 insertions(+), 22 deletions(-)
 delete mode 100644 debian/firmware-b43-installer.postrm
 create mode 100644 debian/firmware-b43-installer.prerm

diff --git a/debian/firmware-b43-installer.postinst b/debian/firmware-b43-installer.postinst
index 0d9c0e1..d8794c2 100644
--- a/debian/firmware-b43-installer.postinst
+++ b/debian/firmware-b43-installer.postinst
@@ -25,16 +25,35 @@ fi
 if ! wget --timeout=60 http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2 ; then
 	echo "Some problem occurred during the firmware download. Please check your internet connection." 
 	exit 0
-else
-	if [ -d /lib/firmware/b43 ]; then
-	   echo "Deleting old extracted firmware..."
-	   rm -rf /lib/firmware/b43
-	fi
 fi
 tar xvjf broadcom-wl-5.100.138.tar.bz2
 cd broadcom-wl-5.100.138/linux
-b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta.o
+if [ -d "${FIRMWARE_INSTALL_DIR}/b43" ]; then
+	echo "Deleting old extracted firmware..."
+	xargs -r -0 -a "${FIRMWARE_INSTALL_DIR}/b43/firmware-b43-installer.catalog" dpkg-query -S 2>&1 1>/dev/null | cut -d/ -f4- | xargs rm --
+	rm "${FIRMWARE_INSTALL_DIR}/b43/firmware-b43-installer.catalog"
+fi
+mkdir "${FIRMWARE_INSTALL_DIR}/b43" || true
+catalog="${FIRMWARE_INSTALL_DIR}/b43/firmware-b43-installer.catalog"
+retcode=0
+b43-fwcutter -w "${FIRMWARE_INSTALL_DIR}" wl_apsta.o | while read line
+do	echo "${line}"
+	file="${line#Extracting }"
+	if [ "${file}" != "${line}" ]
+	then	if [ "${retcode}" -ne 0 ]
+		then	rm "${FIRMWARE_INSTALL_DIR}/${file}"
+
+		elif [ -z "${FIRMWARE_INSTALL_DIR}/${file}" ] || \
+		! printf %s/%s\\x00 "${FIRMWARE_INSTALL_DIR}" "${file}" >> "${catalog}"
+		then	echo "$0: Failed during extraction of ${file} from ${WL_APSTA}" 1>&2
+			echo "$0: Warning, manual removal/cleaning of ${FIRMWARE_INSTALL_DIR}/b43 may be needed!" 1>&2
+			rm "${FIRMWARE_INSTALL_DIR}/${file}"
+			retcode=1
+		fi
+	fi
+done
 rm -rf $tmp
+[ ${retcode} -eq 0 ] || exit ${retcode}
 }
 
 # check environment
@@ -48,7 +67,7 @@ if [ "$(stat -c %d/%i /)" != "$(stat -Lc %d/%i /proc/1/root 2>/dev/null)" ];
 echo "No chroot environment found. Starting normal installation"
 fi
  
- 
+
 
 
 # check 

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

[Debian Bug Tracking System]

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

This means that you claim 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.)


-- 
919829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libatteanx-store-sparql-perl
Version: 0.010-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
test -x debian/rules
mkdir -p "."

Scanning upstream source for new/changed copyright notices...

set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
8 combinations of copyright and licensing found.
WARNING:New or changed notices discovered:

Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
License: Artistic-1.0 and/or GPL-1

To fix the situation please do the following:

[... snipped ...]

t/triplestore.t .. 
# Subtest: testing with main
# Subtest: get_triples
ok 1
ok 2
1..2
ok 1 - get_triples
# Subtest: count_triples
ok 1 - unexpected IRI
ok 2 - expected subject
ok 3 - expected predicate
ok 4 - expected object
ok 5 - expected object (2)
ok 6 - expected subject/object
ok 7 - expected predicate with variable
ok 8 - expected object with variable
ok 9 - expected object (2) with variable
ok 10 - expected subject/object with variable
ok 11 - count_triples_estimate
1..11
ok 2 - count_triples
# Subtest: size
ok 1
ok 2
ok 3
ok 4
1..4
ok 3 - size
1..3
ok 1 - testing with main
1..1
ok

Test Summary Report
---
t/plan.t   (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
Files=2, Tests=1,  7 wallclock secs ( 0.05 usr  0.01 sys +  5.78 cusr  0.51 
csys =  6.35 CPU)
Result: FAIL
Failed 1/2 test programs. 0/1 subtests failed.
make[1]: *** [Makefile:871: test_dynamic] Error 255
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:113: 
debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build-arch 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 -B"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libatteanx-store-sparql-perl.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: libatteanx-store-sparql-perl
Source-Version: 0.012-1

We believe that the bug you reported is fixed in the latest version of
libatteanx-store-sparql-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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated 
libatteanx-store-sparql-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: Thu, 07 Feb 2019 02:14:39 +0100
Source: libatteanx-store-sparql-perl
Architecture: source
Version: 0.012-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Jonas Smedegaard 
Closes: 919829
Changes:
 libatteanx-store-sparql-perl (0.012-1) unstable; urgency=medium
 .
   [ upstream ]
   * New release.
 + Allow the Store to handle count_quads_estimate
   

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

[Axel Beckert]

Package: xen-utils-4.11,xen-utils-common
Version: 4.11.1-1
Severity: serious
Control: affects -1 xen-tools

Hi,

both, /usr/lib/xen-4.11/bin/pygrub as well as /usr/bin/pygrub bail out
for me as follows on Buster:

# /usr/bin/pygrub
Traceback (most recent call last):
  File "/usr/bin/pygrub", line 23, in 
import fsimage
ImportError: No module named fsimage

This is a regression from Stretch and breaks many DomUs after upgrade as
well as most DomUs generated with xen-tools' defaults (which uses
pygrub). It especially severly harms the release testing for the
xen-tools pending 4.8 release. :-(

This seems related (and partially mentioned), but not identical to
#912441 as pygrub is present for me, just not working at all. Which
means: This bug report is about pygrub being present, but completely
broken.

There aren't many differences between pygrub in Stretch and Buster:

1c1
< #! /usr/bin/python2.7
---
> #! /usr/bin/python
22,23d21
< 
< sys.path.insert(1, sys.path[0] + '/../lib/python')

That's all differences.

The latter removal of a search path is very likely the reason for this
issue. (Already hinted towards that in #912441, too.)

As a (very ugly) workaround I tried to copy over pygrub from a Stretch
Dom0, i.e. from xen-utils-4.8, but this helped only partially:

# pygrub
Traceback (most recent call last):
  File "/usr/bin/pygrub", line 25, in 
import fsimage
ImportError: libfsimage.so: cannot open shared object file: No such file or 
directory

Note the different error message on the last line. Now it doesn't find
libfsimage.so.

"strace /usr/lib/xen-4.11/bin/pygrub" reveals that pygrub from
xen-utils-4.8, when copied onto a Buster system, indeed tries to access
that /usr/lib/xen-4.11/lib/python/fsimage.so, just doesn't use it:

# strace /usr/lib/xen-4.11/bin/pygrub |& fgrep -A20 lib/python/fsimage.so 
--color
openat(AT_FDCWD, "/usr/lib/xen-4.11/bin/../lib/python/fsimage.so", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=16128, ...}) = 0
openat(AT_FDCWD, "/usr/lib/xen-4.11/bin/../lib/python/fsimage.so", 
O_RDONLY|O_CLOEXEC) = 4
read(4, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0p\21\0\0\0\0\0\0"..., 
832) = 832
fstat(4, {st_mode=S_IFREG|0644, st_size=16128, ...}) = 0
mmap(NULL, 18352, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = 0x7f1af1082000
mmap(0x7f1af1083000, 4096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x1000) = 0x7f1af1083000
mmap(0x7f1af1084000, 4096, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 
0x2000) = 0x7f1af1084000
mmap(0x7f1af1085000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x2000) = 0x7f1af1085000
close(4)= 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=49493, ...}) = 0
mmap(NULL, 49493, PROT_READ, MAP_PRIVATE, 4, 0) = 0x7f1af0f92000
close(4)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/x86_64/x86_64/libfsimage.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls/x86_64/x86_64", 0x7fff92e70430) = -1 ENOENT (No 
such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/x86_64/libfsimage.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls/x86_64", 0x7fff92e70430) = -1 ENOENT (No such 
file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/x86_64/libfsimage.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls/x86_64", 0x7fff92e70430) = -1 ENOENT (No such 
file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/libfsimage.so", O_RDONLY|O_CLOEXEC) 
= -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls", 0x7fff92e70430) = -1 ENOENT (No such file or 
directory)

Reason for this seems to be that the linker doesn't find libfsimage.so:

# ldd /usr/lib/xen-4.11/lib/python/fsimage.so
linux-vdso.so.1 (0x7fff1bbb5000)
libfsimage.so => not found
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f657bd3a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f657bb72000)
/lib64/ld-linux-x86-64.so.2 (0x7f657bd7a000)

What finally works is using pygrub from Stretch _and_ setting
LD_LIBRARY_PATH=/usr/lib/xen-4.11/lib/x86_64-linux-gnu:

# env LD_LIBRARY_PATH=/usr/lib/xen-4.11/lib/x86_64-linux-gnu pygrub
Usage: /usr/bin/pygrub [-q|--quiet] [-i|--interactive] [-l|--list-entries] 
[-n|--not-really] [--output=] [--kernel=] [--ramdisk=] [--args=] [--entry=] 
[--output-directory=] [--output-format=sxp|simple|simple0] [--offset=] 

So using that LD_LIBRARY_PATH when calling xl and the pygrub from
stretch, I can boot pygrub/grub-legacy based DomUs again.

Even if this doesn't affect the general usage of Xen, this is a severe
regression from Stretch and needs to be fixed for Buster. Hence the RC

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

[Debian Bug Tracking System]

Processing control commands:

> affects -1 xen-tools
Bug #921590 [xen-utils-4.11,xen-utils-common] xen-utils-4.11: pygrub bails out 
with "ImportError: No module named fsimage"
Added indication that 921590 affects xen-tools

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

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

[Manuel A. Fernandez Montecelo]

Em qua, 6 de fev de 2019 às 04:15, Frank Heckenbach
 escreveu:
>
> > Em qui, 3 de jan de 2019 às 22:56, Frank Heckenbach
> >  escreveu:
> > >
> > > According to https://release.debian.org/buster/freeze_policy.html:
> > >
> > > 2019-01-12 - Transition freeze
> > >
> > > Is there still time yet to get a fix in, or is it FUBAR already?
> >
> > Transition freeze means ABI changes in libraries are forbidden.  We're
> > almost in soft-freeze now, more info at:
> > https://lists.debian.org/debian-devel-announce/2019/01/msg8.html
>
> So do we have time until the soft freeze on 2019-02-12 (I hope not)
> or the full freeze (2019-03-12) to get a 2.4.0 uploaded?

I believe so, yes, maybe even for the soft freeze (I am not sure how
much the time shortens for migrating packages fixing important bugs,
it varies).


> > I have to review the situation again, I completely swapped it out of
> > my memory.
>
> My suggestion of 2018-11-25 still stands. But if you want me to do
> my part of it, please do your review quickly and tell me soon
> (or, if it's indeed necessary for the soft freeze, immediately) to
> avoid running out of time.

Your plan sounds OK.  Changing packages after the release, with time,
should be OK.  I can submit automatic bug reports for the affected
packages.

Maybe it would even be possible to have the applications set a global
variable, e.g.:

  enum class Render { Default = 1, Basic };
  FTGL->setRender(Render  renderType);

and then the Render() function(s) would dispatch to either
RenderDefault() or RenderBasic() versions as appropriate?


Cheers.
-- 
Manuel A. Fernandez Montecelo 

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

[Debian Bug Tracking System]

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

This means that you claim that the problem 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.)


-- 
903056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: foremancli
Version: 1.0-2
Severity: serious

Since ronn got split out of ruby-ronn, foremancli fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with ronn as foremancli uses the
command line tool.

Helmut
--- End Message ---
--- Begin Message ---
Source: foremancli
Source-Version: 1.0-3

We believe that the bug you reported is fixed in the latest version of
foremancli, 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 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated foremancli 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: Thu, 07 Feb 2019 00:46:49 +0100
Source: foremancli
Architecture: source
Version: 1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Closes: 903056
Changes:
 foremancli (1.0-3) unstable; urgency=medium
 .
   * Team upload
   * debian/control: remove obsolete DM-Upload-Allowed flag
   * Bump debhelper compatibility level to 9
   * Remove version in the gem2deb build-dependency
   * Run wrap-and-sort on packaging files
   * Build-depend on ronn instead of ruby-ronn (Closes: #903056)
   * Use --roff long option in rule to build manpage
   * Move debian/watch to gemwatch.debian.net
   * Bump debhelper compatibility level to 11
   * Use salsa.debian.org in Vcs-* fields
   * Bump Standards-Version to 4.3.0 (no changes needed)
   * Use https in copyright formal URL
Checksums-Sha1:
 43fd2bf46fdc843ffd20b9299f0dd6e0cd81df54 1642 foremancli_1.0-3.dsc
 c1254d184c256b0e872ea684ac99986a592d90ca 3408 foremancli_1.0-3.debian.tar.xz
 a7d950eee2ef096ddcccbeb60a0839dde12e5373 13452 
foremancli_1.0-3_source.buildinfo
Checksums-Sha256:
 24c1ac545242eb81d7fae399c12c04dc987479ceb3173bddff922750ba26a156 1642 
foremancli_1.0-3.dsc
 d1471e6d0ff83a3b646e26539092e871092e6dbc0d233979fbbf1ef0cd825dc7 3408 
foremancli_1.0-3.debian.tar.xz
 4cce67d7c4f03dfd0eb6214d969c4abbd6d11c65179d7553837f5251b23b 13452 
foremancli_1.0-3_source.buildinfo
Files:
 887e452e32b41841ff567b499aa3c45f 1642 admin optional foremancli_1.0-3.dsc
 298a1eb87ee960932b70f0a4b84245cb 3408 admin optional 
foremancli_1.0-3.debian.tar.xz
 41fee85830fa8b6f95f1145c2590cec4 13452 admin optional 
foremancli_1.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlxbdWYACgkQia+CtznN
IXpz1Qf/WLJphZ54k599Z+nlZvLJKw4xQKFyrjT6Jqi3YzwG/MImgfKURlHbp2Sa
kO5lmQrXcKu4vBd7xJBXGPTuFu5nLlHXJ1CMvKY3h4D0Q5Q5CTnd9Iu+QIGzOXPJ
fEFyowh6i3i5KNXNZYqm9lR47J4m001HH1wIXoRDr7ouwm2La/lttyVBO73WQq3u
F+z4o2tuhLo3YuzPX2tz3U73MN/GI8jH80Om8WwaVAcG1FVMk7GgZLBGNu3gtlFX
1GJWGMLNaAhL5M6HXWvnJbIgGqf2aQa6He7DYtQAbZitc1covT257YuxS/NjESww
3rQJor/tLkkd3wFwT0bXxnBVnBcpLQ==
=sV8L
-END PGP SIGNATURE End Message ---

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

[Cédric Boutillier]

Control: tag -1 pending

Hello,

Bug #903056 in foremancli reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ruby-team/foremancli/commit/6f23f059a4276a4d1d5ac3ccd45b89f1f598939c


Build-depend on ronn instead of ruby-ronn (Closes: #903056)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/903056

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

[Michael Hudson-Doyle]

On Thu, 7 Feb 2019 at 04:09, Antoine Beaupré  wrote:

> On 2019-02-03 17:21:35, Antoine Beaupre wrote:
> > My first submissions for the dmarc-cat package (#920385) were refused
> > by the FTP masters because the built-using field did not respect §7.8
> > of the Debian policy.
>
> That's actually inaccurate: the package was refused because the
> dependencies specified in `built-using` were missing and indeed, one of
> the dependencies hadn't passed NEW when dmarc-cat was uploaded. For
> example, here's the last REJECTION I had:
>
> An exception was raised while processing the package:
> Traceback (most recent call last):
>   File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 109,
> in wrapper
> function(upload, srcqueue, comments, transaction)
>   File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 222,
> in comment_accept
> extra_archives=[upload.target_suite.archive],
>   File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 451,
> in copy_binary
> self._ensure_extra_source_exists(filename, db_source, archive,
> extra_archives=extra_archives)
>   File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 245,
> in _ensure_extra_source_exists
> raise ArchiveException('{0}: Built-Using refers to package {1} (= {2})
> not in target archive {3}.'.format(filename, source.source, source.version,
> archive.archive_name))
> ArchiveException: d/dmarc-cat/dmarc-cat_0.9.1-1_amd64.deb: Built-Using
> refers to package golang-github-ivpusic-grpool (= 1.0.0-1) not in target
> archive ftp-master.
>
> When grpool was ACCEPTED, dmarc-cat also was ACCEPTED by the
> FTP-masters. So this is not a blocker for the FTP masters.
>
> > Extract from #debian-ftp:
> >
> > 16:55:59  Built-Using is only meant to be used when the result
> is GPL/MPL/similar and you've statically linked (/bundled) another source
> package
> > 16:56:33  okay, so to comply with licensing issues?
> > 16:56:47  it also seems useful to track rdeps for golang as
> well, no?
> > 16:57:03  no, built-using is _not_ for tracking dependencies
> > 16:57:10  it is for license compliance
> > 16:57:26  and bsd licensed software does not require that
> >
> > So in the case of dmarc-cat, dependencides like
> > golang-github-stretchr-testify-dev should actually not be listed in
> > the Built-Using field.
>
> It's true, however, that the Debian policy specifies built-using is for
> copyright reasons.
>
>
> https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using
>
> Specifically, the last pargraph reads:
>
> > This field should not be added solely for purposes other than
> > satisfying license or DFSG requirements to provide full source
> > code. In particular, it should not be added solely to enable finding
> > packages that should be rebuilt against newer versions of their build
> > dependencies.
>
> Yet, from what I understand, that is *exactly* how that field is used in
> the golang team. Is that correct?
>
> It should be noted this is a SHOULD NOT and not a MUST NOT, so it's a
> little more relaxed - may we are allowed to abuse it like this.
>
> I do wonder if it's deliberate, however. It seems to me this should be
> clarified, both in dh-golang and in policy, either way.
>

It's a pretty recent change in policy to clarify that how go packages use
it is not the intended use. When go packages started using Built-Using,
they were 100% compliant with the wording (if not the intent) of policy :)

Cheers,
mwh

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

[W. Martin Borgert]

Control: reassign -1 libloudmouth1-0
Control: retitle -1 libloudmouth1-0: does not support IPv6 (fails Squeeze 
release goal)
Control: tag -1 + patch

On 2019-02-03 09:32, W. Martin Borgert wrote:
> I'm in the same network, and mcabber works for me.

After testing again, I believe, that my computer just
re-connected to the other (IPv4-capable) network.

With this commit (patch applies), IPv6 seems to work:

https://github.com/mcabber/loudmouth/commit/95078ef12ab30735b4280675837c64686cf9faaa

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

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libloudmouth1-0
Bug #921195 [mcabber] mcabber: does not connect to Jabber via IPv6 (fails Etch 
release goal)
Bug reassigned from package 'mcabber' to 'libloudmouth1-0'.
No longer marked as found in versions mcabber/1.1.0-1.1.
Ignoring request to alter fixed versions of bug #921195 to the same values 
previously set
> retitle -1 libloudmouth1-0: does not support IPv6 (fails Squeeze release goal)
Bug #921195 [libloudmouth1-0] mcabber: does not connect to Jabber via IPv6 
(fails Etch release goal)
Changed Bug title to 'libloudmouth1-0: does not support IPv6 (fails Squeeze 
release goal)' from 'mcabber: does not connect to Jabber via IPv6 (fails Etch 
release goal)'.
> tag -1 + patch
Bug #921195 [libloudmouth1-0] libloudmouth1-0: does not support IPv6 (fails 
Squeeze release goal)
Added tag(s) patch.

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

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

[Adrian Bunk]

Source: golang-google-cloud
Version: 0.9.0-8
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-google-cloud/1861825/log.gz

...
# cloud.google.com/go/profiler/mocks
src/cloud.google.com/go/profiler/mocks/mock_profiler_client.go:49:86: 
undefined: cloudprofiler.CreateOfflineProfileRequest
...

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has been 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.)


-- 
920536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lintian
Version: 2.5.124
Severity: serious
Tags: ftbfs

lintian fails to build as seen in Ubuntu and with Reproducible Builds.
The latest upload was not a source-only upload so there isn't a
failure on the buildds.

https://tests.reproducible-builds.org/debian/rb-pkg/lintian.html
https://launchpad.net/ubuntu/+source/lintian/2.5.124/+build/16320548

Build log excerpt


 Tags do not match
# --- t/tags/tests/legacy-libbaz/tags 2019-01-24 22:47:53.0 +
# +++ 
/build/1st/lintian-2.5.124/debian/test-out/tags/tests/legacy-libbaz/tags.actual.parsed.sorted
2020-02-28 21:47:32.0 +
# @@ -33,8 +33,12 @@
#  I: libbaz1-dev: package-contains-empty-directory usr/include/
#  I: libbaz1-dev: wrong-section-according-to-package-name libbaz1-dev
=> libdevel
#  I: libbaz1: binary-has-unneeded-section
usr/lib/ma-dir/perl/version/auto/Foo/Foo.so .comment
# +I: libbaz1: file-references-package-build-path usr/lib/libbaz1.so.1.0.3b
# +I: libbaz1: file-references-package-build-path usr/lib/libbaz3.so.1.0.3b
# +I: libbaz1: file-references-package-build-path usr/lib/libfoo2.so.1.0.3b
#  I: libbaz1: no-md5sums-control-file
#  I: libbaz1: symbols-file-missing-build-depends-package-field
# +I: libbaz2-dbg: file-references-package-build-path
usr/lib/debug/usr/lib/libbaz2.so.1.0.3b
#  I: libbaz2-dbg: no-md5sums-control-file
#  I: libbaz2-dbg: wrong-section-according-to-package-name libbaz2-dbg => debug
#  I: libbaz2-dev: no-md5sums-control-file
#   Failed test 'Lintian tags match for legacy-libbaz'
#   at /build/1st/lintian-2.5.124/lib/Test/Lintian/Run.pm line 334.
# Looks like you failed 1 test of 1.


Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.6.0

We believe that the bug you reported is fixed in the latest version of
lintian, 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.
Chris Lamb  (supplier of updated lintian 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: Wed, 06 Feb 2019 22:51:14 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.6.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 911449 920299 920469 920536 920568 920593 920638 920647 920691 920699 
921084
Changes:
 lintian (2.6.0) unstable; urgency=medium
 .
   * Summary of tag changes:
 + Added:
   - package-contains-sass-cache-directory
   - package-uses-dh-runit-but-lacks-breaks-substvar
   - pkg-config-references-unknown-shared-library
 .
   [ Chris Lamb ]
 .
   * Enhancements:
 - Check for pkg-config(1) files that reference unknown shared objects
   via (for example) "Libs: -lfoo". (Closes: #920699)
 - Check for packages that use dh_runit without specifying a Breaks on
   the "${runit:Breaks}" substvar. (Closes: #920299)
 - Require that build paths aren't "/" when checking for
   file-references-package-build-path.
 - Check for packages that ship with .sass-cache directories.
   (Closes: #920593)
 - Detect accidental ".git.git" (etc.) in Vcs-Git headers.
   (Closes: #921084)
 .
   * Bug fixes:
 - Fix FTBFS by avoiding "self" false-positives when checking for
   file-references-package-build-path in the Lintian test suite.
   (Closes: #920536)
 - Ignore duplicate .buildinfo files which can be supplied by using
   mergechanges(1) from devscripts. (Closes: #920469)
 - Rewrite "old" version calculation to prevent false-positives in the
   maintainer-script-supports-ancient-package-version tag.
   (Closes: #920638)
 - 

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has been 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.)


-- 
921172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qmath3d
Version: 0~1.0-1
Severity: serious
Control: block 920171 by -1
X-Debbugs-Cc: Wookey 

Dear maintainer,

your new package qmath3d has

Build-Depends: debhelper (>= 10), qbs, qtbase5-dev, dh-exec, libstdc++-6-dev

We are going to remove gcc-6 soon, so please stop build-depending on
libstdc++-6-dev.

I would also be curious to know such an odd dependency is needed,
libstdc++-7-dev (which is pulled in by build-essential) is no good?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: qmath3d
Source-Version: 0~1.0-2

We believe that the bug you reported is fixed in the latest version of
qmath3d, 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.
Wookey  (supplier of updated qmath3d 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: Wed, 06 Feb 2019 18:00:56 +
Source: qmath3d
Binary: libqmath3d-dev libqmath3d1 libqmath3d1-dbgsym
Architecture: source amd64
Version: 0~1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Wookey 
Changed-By: Wookey 
Description:
 libqmath3d-dev - Useful 3dmaths functions from Qt3d v1.0
 libqmath3d1 - Useful 3dmaths functions from Qt3d v1.0
Closes: 921172
Changes:
 qmath3d (0~1.0-2) unstable; urgency=medium
 .
   * Remove spurious libstdc++-6-dev build-dep (CLoses: #921172)
Checksums-Sha1:
 1db7ddbc735e761252e3ced556ff6e7663f87b20 1769 qmath3d_0~1.0-2.dsc
 421e2b8215f816a24864312e1e12a98e0c558da8 3660 qmath3d_0~1.0-2.debian.tar.xz
 d634e2669c820898925c1e51a4ed41f01306679a 5984 libqmath3d-dev_0~1.0-2_amd64.deb
 6ae82593f315d47a423ab9ebc04e24eb2ad1fb37 587352 
libqmath3d1-dbgsym_0~1.0-2_amd64.deb
 d349fcec41871b8d8b2504d6e57f9ce322ad5527 14388 libqmath3d1_0~1.0-2_amd64.deb
 e9bb7f2aff6cd31989a3c8da24a87078214c0280 9515 qmath3d_0~1.0-2_amd64.buildinfo
Checksums-Sha256:
 f56fe6d9d9d54b98a1c543851ac68b939f8d304136abd43d5f7cd237f1d46eb6 1769 
qmath3d_0~1.0-2.dsc
 3bc9b33a607f504883864c7be2a054bc64c2454179c8dfda0b93e83a3bc82cbc 3660 
qmath3d_0~1.0-2.debian.tar.xz
 10014bf4ecf8ed44a8ecedb3ab8cae8e03c9b5134a3c5c9ef2c69ea9b35fa6c0 5984 
libqmath3d-dev_0~1.0-2_amd64.deb
 61ae93f20aab76660e59900e3c42741c3dbd43fe87fd503fee2dfa9e1f5676ce 587352 
libqmath3d1-dbgsym_0~1.0-2_amd64.deb
 4294d4ab08c6aa90e5db407aee57be059e2e9b0ec3fd230bf8241af7ed7d4b5f 14388 
libqmath3d1_0~1.0-2_amd64.deb
 255a461c400d819835fa690380f4e346268941fd595cadcd3cca7f2d75e72568 9515 
qmath3d_0~1.0-2_amd64.buildinfo
Files:
 070717ac97fcaf9c6442747fee230535 1769 libs optional qmath3d_0~1.0-2.dsc
 faa53fbbdb6f8cd3c1722b1c630a7e93 3660 libs optional 
qmath3d_0~1.0-2.debian.tar.xz
 e02b3ddc584e8a9a752ffc854ae7ff65 5984 libs optional 
libqmath3d-dev_0~1.0-2_amd64.deb
 e6b17680193b34da1d9213bf7ca21cac 587352 debug optional 
libqmath3d1-dbgsym_0~1.0-2_amd64.deb
 84e9e997759a9b8758dfc8ae456ec347 14388 libs optional 
libqmath3d1_0~1.0-2_amd64.deb
 4894a68612ac93ed5139f1686f0cb3c6 9515 libs optional 
qmath3d_0~1.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJcW1xSAAoJEPuGMlGob55HOuYP/1uxNPFbv4G4O7juLnbALES2
FZHXQVMd7WQN7dqYatSi1XXjX/SzxwCex23pWFJHTPyET5uhp/gES2YLlPkVORS5
8/EEy7u9/i/EDgVsUjQKIrCudPKEJmKwBXHNjhdoMg7HEQIIx22lMEFKQ+EcSbuT
g/0VeaIHNMvS7v5erJwgUdDJQCk2MfUQJ8REWsMb3M7yZ8v6dcfwz3WcyXotrAj3
X1rTwkxUx2aC4Jn08o0Hbu+Xf+OezXUK+Ipnxb0l67vBxDmq6qy6TeuWfEPzKsVr

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

[Debian Bug Tracking System]

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

This means that you claim that the problem 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.)


-- 
919555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libemf
Version:  1.0.11-1
Severity: important
Tags: upstream
Justification: fails to build from source

Hi,

Builds of libemf have been failing on arm64 and s390x and the
non-release architectures ppc64 and sparc64:

See https://buildd.debian.org/status/package.php?p=libemf

Tail of log for libemf on arm64:

^~~
../include/libEMF/wine/winbase.h:1377:50: error: 'CONTEXT' does not
name a type; did you mean 'CONTEXT86'?
 BOOLWINAPI SetThreadContext(HANDLE,const CONTEXT *);
  ^~~
  CONTEXT86
make[3]: *** [Makefile:480: libemf.lo] Error 1
make[3]: Leaving directory '/<>/libemf'
make[2]: *** [Makefile:429: all-recursive] Error 1
make[2]: *** Waiting for unfinished jobs
echo Timestamp >doxygen-doc/libemf.tag
make[2]: Leaving directory '/<>'
dh_auto_build: make -j8 all doxygen-doc doxygen-pdf returned exit code 2
make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-arch] Error 2

Tail of log for libemf on s390x:

See tests/test-suite.log
Please report to dallenbarn...@users.sourceforge.net

make[5]: *** [Makefile:733: test-suite.log] Error 1
make[5]: Leaving directory '/<>/tests'
make[4]: *** [Makefile:841: check-TESTS] Error 2
make[4]: Leaving directory '/<>/tests'
make[3]: *** [Makefile:908: check-am] Error 2
make[3]: Leaving directory '/<>/tests'
make[2]: *** [Makefile:429: check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j2 check VERBOSE=1 -j1 returned exit code 2
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-arch] Error 2

Cheers,
Balint

-- 
Balint Reczey
Ubuntu & Debian Developer
--- End Message ---
--- Begin Message ---
Source: libemf
Source-Version: 1.0.11-2

We believe that the bug you reported is fixed in the latest version of
libemf, 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.
Barak A. Pearlmutter  (supplier of updated libemf 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: Wed, 06 Feb 2019 14:15:12 +
Source: libemf
Binary: libemf-dev libemf1 libemf-doc printemf
Architecture: source
Version: 1.0.11-2
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Description:
 libemf-dev - Enhanced Metafile library (development)
 libemf-doc - Enhanced Metafile library (documentation)
 libemf1- Enhanced Metafile library (run-time)
 printemf   - Enhanced Metafile library (executable)
Closes: 919555 919766
Changes:
 libemf (1.0.11-2) unstable; urgency=medium
 .
   [ Balint Reczey ]
   * Pick patch from Fedora to fix build on arm64 (Closes: #919555)
   * Handle EOF and other errors in an endianness-aware way (Closes: #919766)
 .
   [ Barak A. Pearlmutter ]
   * Accept Balint Reczey patches, with thanks.
   * Add build dependency for /usr/bin/dot used by doxygen
Checksums-Sha1:
 21cd6d73533c6756d51b60d2315d184447dc3f82 2469 libemf_1.0.11-2.dsc
 7257a358a3de5036532c9c4ee107fe8c9868bf20 31264 libemf_1.0.11-2.debian.tar.xz
 c8da0d35de1b3c9125fceb2b9b3032dd9b134416 9445 libemf_1.0.11-2_source.buildinfo
Checksums-Sha256:
 c6a9388282ca2d1806a1f69ff7d5420fbd7f71fe18a1c3111b23c7b1fe05ef60 2469 
libemf_1.0.11-2.dsc
 8d31b092cc0094d9fa832339680c93aec066bc23e2cd4f735bc074654e8c87bf 31264 
libemf_1.0.11-2.debian.tar.xz
 4a83f746c4755289fbd270cc94e8a232043ceaf8c5ac36b4d32b31490a317c36 9445 

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has been dealt 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.)


-- 
919766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libemf
Version:  1.0.11-1
Severity: important
Tags: upstream
Justification: fails to build from source

Hi,

Builds of libemf have been failing on arm64 and s390x and the
non-release architectures ppc64 and sparc64:

See https://buildd.debian.org/status/package.php?p=libemf

Tail of log for libemf on arm64:

^~~
../include/libEMF/wine/winbase.h:1377:50: error: 'CONTEXT' does not
name a type; did you mean 'CONTEXT86'?
 BOOLWINAPI SetThreadContext(HANDLE,const CONTEXT *);
  ^~~
  CONTEXT86
make[3]: *** [Makefile:480: libemf.lo] Error 1
make[3]: Leaving directory '/<>/libemf'
make[2]: *** [Makefile:429: all-recursive] Error 1
make[2]: *** Waiting for unfinished jobs
echo Timestamp >doxygen-doc/libemf.tag
make[2]: Leaving directory '/<>'
dh_auto_build: make -j8 all doxygen-doc doxygen-pdf returned exit code 2
make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-arch] Error 2

Tail of log for libemf on s390x:

See tests/test-suite.log
Please report to dallenbarn...@users.sourceforge.net

make[5]: *** [Makefile:733: test-suite.log] Error 1
make[5]: Leaving directory '/<>/tests'
make[4]: *** [Makefile:841: check-TESTS] Error 2
make[4]: Leaving directory '/<>/tests'
make[3]: *** [Makefile:908: check-am] Error 2
make[3]: Leaving directory '/<>/tests'
make[2]: *** [Makefile:429: check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j2 check VERBOSE=1 -j1 returned exit code 2
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-arch] Error 2

Cheers,
Balint

-- 
Balint Reczey
Ubuntu & Debian Developer
--- End Message ---
--- Begin Message ---
Source: libemf
Source-Version: 1.0.11-2

We believe that the bug you reported is fixed in the latest version of
libemf, 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.
Barak A. Pearlmutter  (supplier of updated libemf 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: Wed, 06 Feb 2019 14:15:12 +
Source: libemf
Binary: libemf-dev libemf1 libemf-doc printemf
Architecture: source
Version: 1.0.11-2
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Description:
 libemf-dev - Enhanced Metafile library (development)
 libemf-doc - Enhanced Metafile library (documentation)
 libemf1- Enhanced Metafile library (run-time)
 printemf   - Enhanced Metafile library (executable)
Closes: 919555 919766
Changes:
 libemf (1.0.11-2) unstable; urgency=medium
 .
   [ Balint Reczey ]
   * Pick patch from Fedora to fix build on arm64 (Closes: #919555)
   * Handle EOF and other errors in an endianness-aware way (Closes: #919766)
 .
   [ Barak A. Pearlmutter ]
   * Accept Balint Reczey patches, with thanks.
   * Add build dependency for /usr/bin/dot used by doxygen
Checksums-Sha1:
 21cd6d73533c6756d51b60d2315d184447dc3f82 2469 libemf_1.0.11-2.dsc
 7257a358a3de5036532c9c4ee107fe8c9868bf20 31264 libemf_1.0.11-2.debian.tar.xz
 c8da0d35de1b3c9125fceb2b9b3032dd9b134416 9445 libemf_1.0.11-2_source.buildinfo
Checksums-Sha256:
 c6a9388282ca2d1806a1f69ff7d5420fbd7f71fe18a1c3111b23c7b1fe05ef60 2469 
libemf_1.0.11-2.dsc
 8d31b092cc0094d9fa832339680c93aec066bc23e2cd4f735bc074654e8c87bf 31264 
libemf_1.0.11-2.debian.tar.xz
 4a83f746c4755289fbd270cc94e8a232043ceaf8c5ac36b4d32b31490a317c36 9445 

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

[Scott Kitterman]

It's not the FTP Team's job to fix policy compliance issues in packages.  If 
you have a problem with that being a policy must, then you should take it up 
with the policy team.

I completely understand the frustration, but in my own packages I take the time 
to do it because Debian policy says it's required, not because I particularly 
care about sysvinit.

Scott K

On February 6, 2019 9:23:46 PM UTC, Michael Stapelberg  
wrote:
>Can you provide a patch if you care about sysvinit please? The Go
>packaging
>team is pretty manpower-constrained and non-systemd is a niche case, so
>any
>help is appreciated. Thanks!
>
>On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman 
>wrote:
>
>> Package: prometheus-postfix-exporter
>> Version: 0.1.2-1
>> Severity: serious
>> Justification: Policy 9.11
>>
>> Excerpt from policy 9.11:
>>
>> However, any package integrating with other init systems
>> must also be backwards-compatible with sysvinit by providing a SysV-
>> style init script with the same name as and equivalent functionality
>> to any init-specific job, as this is the only start-up configuration
>> method guaranteed to be supported by all init implementations.
>>
>> The package violates a policy must by not providing s sysvint init
>script.
>>
>> Scott K
>>
>> ___
>> Pkg-go-maintainers mailing list
>> pkg-go-maintain...@alioth-lists.debian.net
>>
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Norbert Preining]

Hi all

On Tue, 05 Feb 2019, Nicholas D Steeves wrote:
> Shall I update d/control to use "Norbert Preining
> "?  If not, I'll need to move the salsa project
> to a new namespace--either collab-maint or my own.

Please see https://github.com/norbusan/calibre-debian which has all
these changes, including the VCS updates as well as the email adr
change.

And yes, please complain to DAM about this mess.

> Thank you for bringing this to my attention, as far as I know, Norbert
> I've contacted him using his other email address, to ask to use that
> address as maintainer.

It is already used in the packages I published on my website, as well 
as in the github repository which is the current correct and only 
repository for packaging calibre.

> Worst case scenario, what is the deadline to adopt Calibre?  I believe
> Norbert is still the maintainer, but am willing to adopt the package

Wait, first of all, what is the 3.39.1 that was uploaded to unstable?
Please use the github repository for packaging,

SALSA IS DEPRECATED WITH RESPECT TO MY PACKAGES

And it would be nice to inform me about uploads before doing them,
thanks.

And no, the package is not orphaned, so don't adopt it.

Best

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

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #921510 [src:qutemol] qutemol: segfaults at startup when compiled with GCC 8
Added tag(s) patch.

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

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

[Adrian Bunk]

Control: tags -1 patch

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

With -Wall gcc even tells what the actual bug is:
  src/ShadowMap.cpp: In static member function 'static bool AOgpu2::init()':
  src/ShadowMap.cpp:250:25: warning: control reaches end of non-void function 
[-Wreturn-type]

Proper fix attached.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -Nru qutemol-0.4.1~cvs2008/debian/control 
qutemol-0.4.1~cvs2008/debian/control
--- qutemol-0.4.1~cvs2008/debian/control2019-02-06 13:20:00.0 
+0200
+++ qutemol-0.4.1~cvs2008/debian/control2019-02-06 23:42:28.0 
+0200
@@ -6,7 +6,6 @@
 Section: science
 Priority: optional
 Build-Depends: debhelper (>= 12~),
-   g++-7,
libgif-dev (>= 5),
libglew-dev,
libpng-dev,
diff -Nru qutemol-0.4.1~cvs2008/debian/patches/41_aogpu2_init_return.patch 
qutemol-0.4.1~cvs2008/debian/patches/41_aogpu2_init_return.patch
--- qutemol-0.4.1~cvs2008/debian/patches/41_aogpu2_init_return.patch
1970-01-01 02:00:00.0 +0200
+++ qutemol-0.4.1~cvs2008/debian/patches/41_aogpu2_init_return.patch
2019-02-06 23:47:20.0 +0200
@@ -0,0 +1,14 @@
+Description: Fix segfault due to not returning true in AOgpu2::init()
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/921510
+
+--- qutemol-0.4.1~cvs2008.orig/src/ShadowMap.cpp
 qutemol-0.4.1~cvs2008/src/ShadowMap.cpp
+@@ -248,6 +248,7 @@ bool ShadowMap::initHalo(){
+ bool AOgpu2::init(){
+   if (!moltextureCanvas.Test()) return false;
+   mainCanvas.SetAsOutput();
++  return true;
+ }
+ 
+ float myrand();
diff -Nru qutemol-0.4.1~cvs2008/debian/patches/series 
qutemol-0.4.1~cvs2008/debian/patches/series
--- qutemol-0.4.1~cvs2008/debian/patches/series 2019-02-04 
13:28:00.0 +0200
+++ qutemol-0.4.1~cvs2008/debian/patches/series 2019-02-06 
23:47:20.0 +0200
@@ -36,3 +36,4 @@
 38_libpng15.patch
 39_reproducible_build.patch
 40_c++11_compatibility.patch
+41_aogpu2_init_return.patch
Binary files /tmp/mefexQx1b2/qutemol-0.4.1~cvs2008/debian/qutemol.png and 
/tmp/eIepoe2zGj/qutemol-0.4.1~cvs2008/debian/qutemol.png differ
diff -Nru qutemol-0.4.1~cvs2008/debian/rules 
qutemol-0.4.1~cvs2008/debian/rules
--- qutemol-0.4.1~cvs2008/debian/rules  2019-02-06 13:20:00.0 
+0200
+++ qutemol-0.4.1~cvs2008/debian/rules  2019-02-06 23:47:20.0 
+0200
@@ -2,7 +2,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
-export CXX = g++-7
+export DEB_CXXFLAGS_MAINT_APPEND = -Wall
 
 %:
dh $@

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has been dealt 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.)


-- 
921553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-xopen
Version: 0.5.0-1
Severity: serious
Control: affects -1 python3-xopen

The following dependencies are missing for loading the module
(import xopen):

python-xopen:
- python-pkg-resources
- python-bz2file

python3-xopen:
- python3-pkg-resources
--- End Message ---
--- Begin Message ---
Source: python-xopen
Source-Version: 0.5.0-2

We believe that the bug you reported is fixed in the latest version of
python-xopen, 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.
Andreas Tille  (supplier of updated python-xopen 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: Wed, 06 Feb 2019 22:26:09 +0100
Source: python-xopen
Architecture: source
Version: 0.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 921553
Changes:
 python-xopen (0.5.0-2) unstable; urgency=medium
 .
   * Add missing Depends
 Closes: #921553
Checksums-Sha1:
 1c317d68bac830a1221b91ecf9ec2f98d80a3c56 2264 python-xopen_0.5.0-2.dsc
 59f8257185692dc648d7cc15a4d597d9f37e6bc7 2468 
python-xopen_0.5.0-2.debian.tar.xz
 31f320b84ad4b7b6d1c0380ae6f8ba0eb7efe038 7302 
python-xopen_0.5.0-2_amd64.buildinfo
Checksums-Sha256:
 78ea85d0bd806702faa9536fe9d160e2fb3a1194890a1e102a0afe42f490ada6 2264 
python-xopen_0.5.0-2.dsc
 a4e75444fc1f0205e5f9c56a4bf0755a1fc986accf92e2fcee4df1526ccee5c3 2468 
python-xopen_0.5.0-2.debian.tar.xz
 a3c563bb482afec8b9f660d3fafe7d1208a422f22f374c48cce6b8012f8bfe33 7302 
python-xopen_0.5.0-2_amd64.buildinfo
Files:
 7318aee5d0757958c29a14a71e5fc6d0 2264 python optional python-xopen_0.5.0-2.dsc
 ce555cbd2d54da33452acaf1e16406e4 2468 python optional 
python-xopen_0.5.0-2.debian.tar.xz
 6b224d9b9d206e61a8cb7f4097cfb95d 7302 python optional 
python-xopen_0.5.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxbUWwRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEFZQ/9HiM0vSfohkMqi0yFleHuma0GAXHOotkg
WqGgBeNHj2CJZc6Me1GBqbqulB2Zk8GOvXdIpRYj+Bc1jLSc9wZdeuh3M8NqQFsK
wQVNGQpEWDXj1F9oH9YDVQ+JMQchuLbqCcfH4ki61UAzpybceqgbQjeU1s6lKglF
gzHJ3QIqvM2JGq/5Y+xkejlLyOxKTCx0iyKjBNHbW0NP9CGUfImJAZEei3C9fiS+
MyM/JFiJKA4IKJrdHyCzqJGhUDcp2b9pRfIA28E4DvsIr2CRzXxWU7+UwEhmxZBi
6/526szUxJtgbS5U6Q2QAzERH/Yg9v2LV8Twvdt6bIgEvGcayhx/S2/zO7LwKR9u
y31Ymy5D/kYQe67ZBBgdPj0othHDnGwJhCicivY/O5UvfHKtjz913Z5dGPInVFzL
8uYuPbmtHstcJiQFo439UldySrDmWdi6cWZTyGRV3ys7iXFwwI++Y6d7J700j9zZ
G4zjx/p8hWTTPLHjfvfXWxqZqhzBRjrNLAVSIPRB4Ku8SB5LvSL0LnD3n57OWp5x
sUqx8/0FTt98SUIPJWdYKBM2UbBFsK/bu+efX0atZnKZO1ZIj9XdLJpdFQGSGvHw
OWzEWetyUm9ptxkN67swBbXs8FjACWDjtplJ75nfLdKDM0ZnxSHAh2GKxKaj9/rz
N7nYUUAHWHk=
=VTAI
-END PGP SIGNATURE End Message ---

Bug#921274: teeworlds: baseline violation on i386

[Markus Koschany]

On Sun, 03 Feb 2019 22:35:22 +0200 Adrian Bunk  wrote:
> Source: teeworlds
> Version: 0.7.2-2
> Severity: serious
> Tags: patch
> 
> SSE is not part of the i386 baseline, fix attached.

Could you go into more detail why this is release-critical and what
issue we are trying to solve?

Markus



signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has been dealt 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.)


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

Source: r-cran-repr
Version: 0.19.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of r-cran-tibble 2.0.0-1 to unstable, r-cran-repr has 
been failing its autopkgtests [1] with the following error:


> test_check('repr')
-- 1. Failure: ellip_limit_arr preserves rownames when limiting rows 
(@test_arra

`limited_tbl` not identical to `expected_df_mat`.
Attributes: < Component "dimnames": Component 1: 4 string mismatches >

-- 2. Failure: ellip_limit_arr preserves rownames when limiting rows 
(@test_arra

`limited_tbl` not identical to `expected_df_mat`.
Attributes: < Component "dimnames": Component 1: 5 string mismatches >

== testthat results 
===

OK: 128 SKIPPED: 5 FAILED: 2
1. Failure: ellip_limit_arr preserves rownames when limiting rows 
(@test_array_manipulation.r#229)
2. Failure: ellip_limit_arr preserves rownames when limiting rows 
(@test_array_manipulation.r#251)


Error: testthat unit tests failed

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-repr/unstable/amd64/
--- End Message ---
--- Begin Message ---
Source: r-cran-repr
Source-Version: 0.19.2-1

We believe that the bug you reported is fixed in the latest version of
r-cran-repr, 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.
Andreas Tille  (supplier of updated r-cran-repr 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: Wed, 06 Feb 2019 22:05:03 +0100
Source: r-cran-repr
Architecture: source
Version: 0.19.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 920711
Changes:
 r-cran-repr (0.19.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #920711
   * Add Upstream-Contact
   * debhelper 12
Checksums-Sha1:
 3c04f4b91f9a03042ad5db21293e630307a174a5 2134 r-cran-repr_0.19.2-1.dsc
 4c0b5d82af238c83d7270a409c73717a691b83d2 28452 r-cran-repr_0.19.2.orig.tar.gz
 26cf9bd346fb7a0bc0cb8f0436ec2b664ef4aba7 2584 
r-cran-repr_0.19.2-1.debian.tar.xz
 eac9a90a4c6f36b47422125f9ee0e4af0dbce808 8552 
r-cran-repr_0.19.2-1_amd64.buildinfo
Checksums-Sha256:
 71c5407a0bd7c82906a0b065d02543869634b44ded9c389a3002701acf71763c 2134 
r-cran-repr_0.19.2-1.dsc
 dd4d766d95e8e75f90c05e50e44e759139a47b1477748f4cf9683d35a7fa10d6 28452 
r-cran-repr_0.19.2.orig.tar.gz
 dc876f0fb3c6e4ade663705a66a3aa2fdf023a079f8e0f4232b97a21f38b56d3 2584 
r-cran-repr_0.19.2-1.debian.tar.xz
 4d8765fedb177e16d47791906b804bddd4413a23206fcb5dc4ebaab622dcbd49 8552 
r-cran-repr_0.19.2-1_amd64.buildinfo
Files:
 245e96cca8497af1d0ddee07436f8e7f 2134 gnu-r optional r-cran-repr_0.19.2-1.dsc
 7adb2232478382bff3d37eb984949b2e 28452 gnu-r optional 
r-cran-repr_0.19.2.orig.tar.gz
 1d5d29280d51b173c64b69e92f855cd7 2584 gnu-r optional 
r-cran-repr_0.19.2-1.debian.tar.xz
 44dee5bb4d42db7e6c752e34894dd401 8552 gnu-r optional 
r-cran-repr_0.19.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxbUCwRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGZTg//fmlSn1dZoy1URMTA6m6MvFMlUqPNtFw1
4fTRajwrSWeaCRvCu0SJLmu8sW6UeVaiDKZ/nczo+cgkFJoOlq3ZMMJrDqEvMARJ
jjS0ooqg4JN+ULdT0x0DRFUGYYQQ6G+GOzbnXtufKn6QLCbkfm9vM9LF4ZKhzEwn
65Iwt6k7H68nIimZADSamQUAZWaOy4zGjhk9SglhYSYGUx/LlLDqpUfWwC+j+g1y
aA7ECfNN5n5TNYoosMhImNJd4tLnGvoCZ8ZrMdvGUkhSYOp/vzz0W8CD9CYBlbeS
FGDVIIfHix+rmUYb0fDjm6HQ9tFj+zUwTDjEcV2iyxhbgaHaJuZao65eJ7hvGCZi
67cSQ1IAbV98WVGaTxiFDBQwBT4x1n/TTBjSZZj2zB/yCBe+SmWFDe2XQI1W8v9d
JhmHjkFtn6h698xjZtW4VMfFYMwUXG2iR3rotZDVKdCgpyTeiUKv/365P1zCGdd5

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has been dealt 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.)


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

Source: r-cran-repr
Version: 0.19.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of r-cran-tibble 2.0.0-1 to unstable, r-cran-repr has 
been failing its autopkgtests [1] with the following error:


> test_check('repr')
-- 1. Failure: ellip_limit_arr preserves rownames when limiting rows 
(@test_arra

`limited_tbl` not identical to `expected_df_mat`.
Attributes: < Component "dimnames": Component 1: 4 string mismatches >

-- 2. Failure: ellip_limit_arr preserves rownames when limiting rows 
(@test_arra

`limited_tbl` not identical to `expected_df_mat`.
Attributes: < Component "dimnames": Component 1: 5 string mismatches >

== testthat results 
===

OK: 128 SKIPPED: 5 FAILED: 2
1. Failure: ellip_limit_arr preserves rownames when limiting rows 
(@test_array_manipulation.r#229)
2. Failure: ellip_limit_arr preserves rownames when limiting rows 
(@test_array_manipulation.r#251)


Error: testthat unit tests failed

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-repr/unstable/amd64/
--- End Message ---
--- Begin Message ---
Source: r-cran-repr
Source-Version: 0.19.2-1

We believe that the bug you reported is fixed in the latest version of
r-cran-repr, 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.
Andreas Tille  (supplier of updated r-cran-repr 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: Wed, 06 Feb 2019 22:05:03 +0100
Source: r-cran-repr
Architecture: source
Version: 0.19.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 920711
Changes:
 r-cran-repr (0.19.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #920711
   * Add Upstream-Contact
   * debhelper 12
Checksums-Sha1:
 3c04f4b91f9a03042ad5db21293e630307a174a5 2134 r-cran-repr_0.19.2-1.dsc
 4c0b5d82af238c83d7270a409c73717a691b83d2 28452 r-cran-repr_0.19.2.orig.tar.gz
 26cf9bd346fb7a0bc0cb8f0436ec2b664ef4aba7 2584 
r-cran-repr_0.19.2-1.debian.tar.xz
 eac9a90a4c6f36b47422125f9ee0e4af0dbce808 8552 
r-cran-repr_0.19.2-1_amd64.buildinfo
Checksums-Sha256:
 71c5407a0bd7c82906a0b065d02543869634b44ded9c389a3002701acf71763c 2134 
r-cran-repr_0.19.2-1.dsc
 dd4d766d95e8e75f90c05e50e44e759139a47b1477748f4cf9683d35a7fa10d6 28452 
r-cran-repr_0.19.2.orig.tar.gz
 dc876f0fb3c6e4ade663705a66a3aa2fdf023a079f8e0f4232b97a21f38b56d3 2584 
r-cran-repr_0.19.2-1.debian.tar.xz
 4d8765fedb177e16d47791906b804bddd4413a23206fcb5dc4ebaab622dcbd49 8552 
r-cran-repr_0.19.2-1_amd64.buildinfo
Files:
 245e96cca8497af1d0ddee07436f8e7f 2134 gnu-r optional r-cran-repr_0.19.2-1.dsc
 7adb2232478382bff3d37eb984949b2e 28452 gnu-r optional 
r-cran-repr_0.19.2.orig.tar.gz
 1d5d29280d51b173c64b69e92f855cd7 2584 gnu-r optional 
r-cran-repr_0.19.2-1.debian.tar.xz
 44dee5bb4d42db7e6c752e34894dd401 8552 gnu-r optional 
r-cran-repr_0.19.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxbUCwRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGZTg//fmlSn1dZoy1URMTA6m6MvFMlUqPNtFw1
4fTRajwrSWeaCRvCu0SJLmu8sW6UeVaiDKZ/nczo+cgkFJoOlq3ZMMJrDqEvMARJ
jjS0ooqg4JN+ULdT0x0DRFUGYYQQ6G+GOzbnXtufKn6QLCbkfm9vM9LF4ZKhzEwn
65Iwt6k7H68nIimZADSamQUAZWaOy4zGjhk9SglhYSYGUx/LlLDqpUfWwC+j+g1y
aA7ECfNN5n5TNYoosMhImNJd4tLnGvoCZ8ZrMdvGUkhSYOp/vzz0W8CD9CYBlbeS
FGDVIIfHix+rmUYb0fDjm6HQ9tFj+zUwTDjEcV2iyxhbgaHaJuZao65eJ7hvGCZi
67cSQ1IAbV98WVGaTxiFDBQwBT4x1n/TTBjSZZj2zB/yCBe+SmWFDe2XQI1W8v9d
JhmHjkFtn6h698xjZtW4VMfFYMwUXG2iR3rotZDVKdCgpyTeiUKv/365P1zCGdd5

Processed: affects 919231

[Debian Bug Tracking System]

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

> affects 919231 salt-master
Bug #919231 [systemd] CacheDirectory/StateDirectory does not change owner/group
Added indication that 919231 affects salt-master
> thanks
Stopping processing here.

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

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

[Michael Stapelberg]

Can you provide a patch if you care about sysvinit please? The Go packaging
team is pretty manpower-constrained and non-systemd is a niche case, so any
help is appreciated. Thanks!

On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman  wrote:

> Package: prometheus-postfix-exporter
> Version: 0.1.2-1
> Severity: serious
> Justification: Policy 9.11
>
> Excerpt from policy 9.11:
>
> However, any package integrating with other init systems
> must also be backwards-compatible with sysvinit by providing a SysV-
> style init script with the same name as and equivalent functionality
> to any init-specific job, as this is the only start-up configuration
> method guaranteed to be supported by all init implementations.
>
> The package violates a policy must by not providing s sysvint init script.
>
> Scott K
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers



-- 
Best regards,
Michael

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

[Debian Bug Tracking System]

Your message dated Wed, 06 Feb 2019 20:49:57 +
with message-id 
and subject line Bug#920645: fixed in libgd2 2.2.5-5.1
has caused the Debian Bug report #920645,
regarding libgd2: CVE-2019-6977
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not 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.)


-- 
920645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgd2
Version: 2.2.5-5
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 2.2.4-2+deb9u3
Control: found -1 2.2.4-2

Hi,

The following vulnerability was published for libgd2.

CVE-2019-6977[0]:
| gdImageColorMatch in gd_color_match.c in the GD Graphics Library (aka
| LibGD) 2.2.5, as used in the imagecolormatch function in PHP before
| 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1,
| has a heap-based buffer overflow. This can be exploited by an attacker
| who is able to trigger imagecolormatch calls with crafted image data.

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-2019-6977
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6977
[1] https://bugs.php.net/bug.php?id=77270
[2] https://gist.github.com/cmb69/1f36d285eb297ed326f5c821d7aafced

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libgd2
Source-Version: 2.2.5-5.1

We believe that the bug you reported is fixed in the latest version of
libgd2, 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.
Salvatore Bonaccorso  (supplier of updated libgd2 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, 02 Feb 2019 10:55:00 +0100
Source: libgd2
Binary: libgd-dev libgd-tools libgd-tools-dbgsym libgd3 libgd3-dbgsym
Architecture: source
Version: 2.2.5-5.1
Distribution: unstable
Urgency: medium
Maintainer: GD Team 
Changed-By: Salvatore Bonaccorso 
Closes: 920645 920728
Description: 
 libgd-dev  - GD Graphics Library (development version)
 libgd-tools - GD command line tools and example code
 libgd3 - GD Graphics Library
Changes:
 libgd2 (2.2.5-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Heap-based buffer overflow in gdImageColorMatch (CVE-2019-6977)
 (Closes: #920645)
   * Potential double-free in gdImage*Ptr() (CVE-2019-6978) (Closes: #920728)
Checksums-Sha1: 
 42b163af78a87397b20a7990ea69d4d3dbe75c49 2364 libgd2_2.2.5-5.1.dsc
 ccaeb4361a9906f09d357522b3544f5ebf60c36c 35292 libgd2_2.2.5-5.1.debian.tar.xz
Checksums-Sha256: 
 7315bbba389570a702db92aa2283b614efc95d81fe131074e5a8897d07953b98 2364 
libgd2_2.2.5-5.1.dsc
 69a9110470eefdc6874fcaab7d02b67db43974c3d5e431b8d2f16712ab69af22 35292 
libgd2_2.2.5-5.1.debian.tar.xz
Files: 
 1f8ed6ec471e26a93e806611e2ea47cf 2364 graphics optional libgd2_2.2.5-5.1.dsc
 a0cf086212a2573ac07454e950241b43 35292 graphics optional 
libgd2_2.2.5-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlxYmj9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EwJsQAIlDZiW+r/e2TJ7SwocSj5Rk9f2lJiuL
G1NSOByoPefEdLUCeZ6o5Gfy4gTEBYEht1YYkbgwj5AhGUyo8Ia5Jego9560tHw+
XG/jLDKFHZp/OeZM9yOA0YYG+MHoowQwgDvyPj3a0t+1hdJrrY6D9nY23hTOAIvZ
qWVBh7kfsvIYXcx+9BT2PVDo2rOnOYSKvqaPDgvOERSPjGy/nCBoRXG5VQPsUbEV
Yfku6ziiwJM/o1OJM7o/VWG4VlSqsvBZNxgG825Lk/Owc25S6IMipCSVDf+LGUMK
PCmPES0hq7cLDkinAjd2AgyluWkkWLEow/DZz0GXwiksBXhlH9WwSm63cNYK/Fnb
ksFb3JdGao8z9SrGsByCNiRnt0lTruGtXL2Vci6doUR5raDNZ8Lw1wH67ecGZx4y
M1VYQjYEgx02VKXQtNIQHRNE7fhnIql8QOSjAphF0A7wjSZ48fIDnLMYKPqt6L+o
u/YnfbUY7/IsKHIJfkYzwpBT2nuBRTqzhQqPjualz91ZNTLRumZ9TuDezbM6XfPz
kInTq7oPlioszAxH9sG+6fFQwHDAwxqSxZmbzLSxrb652Gr/SzUDOBEul/GCsKW0
aVfs0rlAxtYvDV3yeaDkyJbxjLRgbYBwsokd7er6Srm4CvZEC6tZYZ/a43B2l09J
8pPMjNwiLPKP
=9jqn
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 06 Feb 2019 20:49:57 +
with message-id 
and subject line Bug#920728: fixed in libgd2 2.2.5-5.1
has caused the Debian Bug report #920728,
regarding libgd2: CVE-2019-6978
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not 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.)


-- 
920728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgd2
Version: 2.2.5-5
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/libgd/libgd/issues/492

Hi,

The following vulnerability was published for libgd2.

CVE-2019-6978[0]:
| The GD Graphics Library (aka LibGD) 2.2.5 has a double free in the
| gdImage*Ptr() functions in gd_gif_out.c, gd_jpeg.c, and gd_wbmp.c.
| NOTE: PHP is unaffected.

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-2019-6978
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6978
[1] https://github.com/libgd/libgd/issues/492

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libgd2
Source-Version: 2.2.5-5.1

We believe that the bug you reported is fixed in the latest version of
libgd2, 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.
Salvatore Bonaccorso  (supplier of updated libgd2 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, 02 Feb 2019 10:55:00 +0100
Source: libgd2
Binary: libgd-dev libgd-tools libgd-tools-dbgsym libgd3 libgd3-dbgsym
Architecture: source
Version: 2.2.5-5.1
Distribution: unstable
Urgency: medium
Maintainer: GD Team 
Changed-By: Salvatore Bonaccorso 
Closes: 920645 920728
Description: 
 libgd-dev  - GD Graphics Library (development version)
 libgd-tools - GD command line tools and example code
 libgd3 - GD Graphics Library
Changes:
 libgd2 (2.2.5-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Heap-based buffer overflow in gdImageColorMatch (CVE-2019-6977)
 (Closes: #920645)
   * Potential double-free in gdImage*Ptr() (CVE-2019-6978) (Closes: #920728)
Checksums-Sha1: 
 42b163af78a87397b20a7990ea69d4d3dbe75c49 2364 libgd2_2.2.5-5.1.dsc
 ccaeb4361a9906f09d357522b3544f5ebf60c36c 35292 libgd2_2.2.5-5.1.debian.tar.xz
Checksums-Sha256: 
 7315bbba389570a702db92aa2283b614efc95d81fe131074e5a8897d07953b98 2364 
libgd2_2.2.5-5.1.dsc
 69a9110470eefdc6874fcaab7d02b67db43974c3d5e431b8d2f16712ab69af22 35292 
libgd2_2.2.5-5.1.debian.tar.xz
Files: 
 1f8ed6ec471e26a93e806611e2ea47cf 2364 graphics optional libgd2_2.2.5-5.1.dsc
 a0cf086212a2573ac07454e950241b43 35292 graphics optional 
libgd2_2.2.5-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlxYmj9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EwJsQAIlDZiW+r/e2TJ7SwocSj5Rk9f2lJiuL
G1NSOByoPefEdLUCeZ6o5Gfy4gTEBYEht1YYkbgwj5AhGUyo8Ia5Jego9560tHw+
XG/jLDKFHZp/OeZM9yOA0YYG+MHoowQwgDvyPj3a0t+1hdJrrY6D9nY23hTOAIvZ
qWVBh7kfsvIYXcx+9BT2PVDo2rOnOYSKvqaPDgvOERSPjGy/nCBoRXG5VQPsUbEV
Yfku6ziiwJM/o1OJM7o/VWG4VlSqsvBZNxgG825Lk/Owc25S6IMipCSVDf+LGUMK
PCmPES0hq7cLDkinAjd2AgyluWkkWLEow/DZz0GXwiksBXhlH9WwSm63cNYK/Fnb
ksFb3JdGao8z9SrGsByCNiRnt0lTruGtXL2Vci6doUR5raDNZ8Lw1wH67ecGZx4y
M1VYQjYEgx02VKXQtNIQHRNE7fhnIql8QOSjAphF0A7wjSZ48fIDnLMYKPqt6L+o
u/YnfbUY7/IsKHIJfkYzwpBT2nuBRTqzhQqPjualz91ZNTLRumZ9TuDezbM6XfPz
kInTq7oPlioszAxH9sG+6fFQwHDAwxqSxZmbzLSxrb652Gr/SzUDOBEul/GCsKW0
aVfs0rlAxtYvDV3yeaDkyJbxjLRgbYBwsokd7er6Srm4CvZEC6tZYZ/a43B2l09J
8pPMjNwiLPKP
=9jqn
-END PGP SIGNATURE End Message ---

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

[Adrian Bunk]

Source: afnix
Version: 2.9.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=afnix=armhf=2.9.2-1=1548047247=0

...
running: SEC0003.als
exception : assert-error
in file   : SEC0003.als at or around line 113
afnix-aexec: failure SEC0003.als
make[6]: *** [../../../../cnf/mak/afnix-rule.mak:270: SEC0003.als] Error 1


This is likely an unaligned access problem.

Bug#892288: arrayfire test crash

[Rebecca N. Palmer]

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

Processed: reassign 921527 to cuneiform

[Debian Bug Tracking System]

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

> reassign 921527 cuneiform 1.1.0+dfsg-7
Bug #921527 [1.1.0+dfsg-7] cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el
Warning: Unknown package '1.1.0+dfsg-7'
Bug reassigned from package '1.1.0+dfsg-7' to 'cuneiform'.
Ignoring request to alter found versions of bug #921527 to the same values 
previously set
Ignoring request to alter fixed versions of bug #921527 to the same values 
previously set
Bug #921527 [cuneiform] cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el
Marked as found in versions cuneiform/1.1.0+dfsg-7.
> thanks
Stopping processing here.

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

Processed: severity of 921533 is serious

[Debian Bug Tracking System]

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

> severity 921533 serious
Bug #921533 [nvidia-cuda-dev] nvidia-cuda-dev: cannot install with uuid-dev
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> reassign 921527 1.1.0+dfsg-7
Bug #921527 [*cuneiform*] cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el
Warning: Unknown package '*cuneiform*'
Bug reassigned from package '*cuneiform*' to '1.1.0+dfsg-7'.
Warning: Unknown package '1.1.0+dfsg-7'
Warning: Unknown package '1.1.0+dfsg-7'
Ignoring request to alter found versions of bug #921527 to the same values 
previously set
Warning: Unknown package '1.1.0+dfsg-7'
Warning: Unknown package '1.1.0+dfsg-7'
Ignoring request to alter fixed versions of bug #921527 to the same values 
previously set
Warning: Unknown package '1.1.0+dfsg-7'
> severity 921527 serious
Bug #921527 [1.1.0+dfsg-7] cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el
Warning: Unknown package '1.1.0+dfsg-7'
Severity set to 'serious' from 'important'
Warning: Unknown package '1.1.0+dfsg-7'
> thanks
Stopping processing here.

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

Processed: severity of 921510 is serious

[Debian Bug Tracking System]

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

> severity 921510 serious
Bug #921510 [src:qutemol] qutemol: segfaults at startup when compiled with GCC 8
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: limit source to why3, tagging 921465

[Debian Bug Tracking System]

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

> limit source why3
Limiting to bugs with field 'source' containing at least one of 'why3'
Limit currently set to 'source':'why3'

> tags 921465 + pending
Bug #921465 [src:why3] why3 FTBFS: dh_install: Cannot find (any matches for) 
"debian/tmp/usr/local/lib/ocaml/*/why3"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Move to the package where it was fixed

[Debian Bug Tracking System]

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

> reassign 915023 openstack-dashboard 3:14.0.0-7
Bug #915023 {Done: Michal Arbet } 
[python3-senlin-dashboard] openstack-dashboard: fails to install in buster 
along python3-senlin-dashboard
Bug reassigned from package 'python3-senlin-dashboard' to 'openstack-dashboard'.
No longer marked as found in versions senlin-dashboard/0.9.0-2.
No longer marked as fixed in versions horizon/3:14.0.2-1.
Bug #915023 {Done: Michal Arbet } 
[openstack-dashboard] openstack-dashboard: fails to install in buster along 
python3-senlin-dashboard
Marked as found in versions horizon/3:14.0.0-7.
> fixed 915023 3:14.0.2-1
Bug #915023 {Done: Michal Arbet } 
[openstack-dashboard] openstack-dashboard: fails to install in buster along 
python3-senlin-dashboard
Marked as fixed in versions horizon/3:14.0.2-1.
> affects 915023 python3-senlin-dashboard
Bug #915023 {Done: Michal Arbet } 
[openstack-dashboard] openstack-dashboard: fails to install in buster along 
python3-senlin-dashboard
Ignoring request to set affects of bug 915023 to the same value previously set
> thanks
Stopping processing here.

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

Processed: affects 921488

[Debian Bug Tracking System]

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

> affects 921488 w1retap
Bug #921488 [libmariadb3] libmariadb3: OpenSSL license contamination of GPL 
reverse-dependencies
Added indication that 921488 affects w1retap
> thanks
Stopping processing here.

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

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

[Andreas Metzler]

Package: lsb-base
Version: 10.2018112800
Severity: serious

Hello,

there is a logic error in /lib/lsb/init-functions's killproc:

base=${1##*/}
if [ ! $pidfile ]; then
name_param="--name $base --pidfile /var/run/$base.pid"
else
name_param="--pidfile $pidfile"
fi

The if clause checks for nonempty $pidfile instead of nonempty $base to
decide whether --name is used.

Also --pidfile $pidfile is always used, even when $pidfile is empty.

I am reportig this as serious since sid's start-stop-daemon requires a
name parameter in addition to --pidfile when the pidfile is not owned by
root, therefore this bug causes init script failures. (#921205)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has been dealt 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.)


-- 
918736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libthrift-java
Version: 0.9.1-2
Severity: important
Tags: patch security upstream
Forwarded: https://issues.apache.org/jira/browse/THRIFT-4506

Hi,

The following vulnerability was published for libthrift-java.

CVE-2018-1320[0]:
| Apache Thrift Java client library versions 0.5.0 through 0.11.0 can
| bypass SASL negotiation isComplete validation in the
| org.apache.thrift.transport.TSaslTransport class. An assert used to
| determine if the SASL handshake had successfully completed could be
| disabled in production settings making the validation incomplete.

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-1320
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1320
[1] https://issues.apache.org/jira/browse/THRIFT-4506
[2] 
https://github.com/apache/thrift/commit/d973409661f820d80d72c0034d06a12348c8705e

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libthrift-java
Source-Version: 0.9.1-2.1

We believe that the bug you reported is fixed in the latest version of
libthrift-java, 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 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated libthrift-java 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: Wed, 06 Feb 2019 19:04:12 +0100
Source: libthrift-java
Architecture: source
Version: 0.9.1-2.1
Distribution: unstable
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Markus Koschany 
Closes: 918736
Changes:
 libthrift-java (0.9.1-2.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Fix CVE-2018-1320:
 It was discovered that it was possible to bypass SASL negotiation
 isComplete validation in the org.apache.thrift.transport.TSaslTransport
 class. An assert used to determine if the SASL handshake had successfully
 completed could be disabled in production settings making the validation
 incomplete. (Closes: #918736)
Checksums-Sha1:
 d1b8333774342a9b9dafa6661bb6264d9557d3eb 2301 libthrift-java_0.9.1-2.1.dsc
 126eab3f003eae06e620e7964eb9b227926c2e11 3224 
libthrift-java_0.9.1-2.1.debian.tar.xz
 22a30bbc5be1f9e0a3145eba3a16edcd854bae2a 16747 
libthrift-java_0.9.1-2.1_amd64.buildinfo
Checksums-Sha256:
 2dc5b734bbbeb6ef40a65f0c722f6e259201d9b9fa2de3476d5cc30e5a8b3778 2301 
libthrift-java_0.9.1-2.1.dsc
 ec2bce943cde5acf766ca853ec9b5afc2b00ee73973aa2e047477b87e9f877b5 3224 
libthrift-java_0.9.1-2.1.debian.tar.xz
 fbc6e0046c49f613200c918ab90fbbed944168d906a9f120d584594a8d0b7618 16747 
libthrift-java_0.9.1-2.1_amd64.buildinfo
Files:
 f2a6d2269e9e46f8baa1e272ea67bb59 2301 java extra libthrift-java_0.9.1-2.1.dsc
 9cb7931277a664e2e7f045b552d949be 3224 java extra 
libthrift-java_0.9.1-2.1.debian.tar.xz
 4bc2728fb4eacc7713e7991ae5173801 16747 java extra 
libthrift-java_0.9.1-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlxbLNtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkicIP+gOOyd9rUsSEHZawREnX5wpMV2gIBtkYxilL
kyXgPx7CDCJQpdx62qR2YlGKhQx55OlXu5vg2SQQGMoGACaWnO1z5OvW2yTnoA+c
Xh5/uSRE5eFqTJAh+WTU0HZ+6WMYh6kLfcuzkwiLclrAFV6mYkwqYxXTUZ6R/224
t16M+WzvuS2PK7VCuWL5bxxthsKugVkzMDMuPck16l53t1+HjoSK4kRPNv7YqBdc
c66HB/B/n1N6/Cf6TPWnZx/Ku2Bm07PcrTJHI975oGbL3JeLndAekjOUODR65arO
j5fLX9n7WbiiWIVYR+HMMeK5DzOlFcs+EmN91OjGTI4oY8mpx1TSyd91gHRCidII
bFOF1Jj9XnUNHAA31zYGMYNn8S7ZXekOLliko+p20+QdffqAbUiU6Gmp2aUDBtOj

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

[Debian Bug Tracking System]

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

This means 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.)


-- 
919219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: abcm2ps
Version: 8.14.2-0.1
Severity: important
Tags: patch

My NMU fails to build because debhelper uses ./build.ninja instead of
./configure and ./Makefile.in.  This is quite surprising, and I cannot
reproduce the issue in my chroot.

However, the attached patch selects an explicit build system and most
probably fixes the issue.

It upgrades to debhelper 12 as well.

Do you want to upload the fix?
May I prepare another NMU?
Shall I set a shorter delay?
>From 277477041beeecea5174ad858aef2bf2c9f1aa4b Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sun, 13 Jan 2019 18:29:28 +0100
Subject: Fix for the FTBFS. Please add the bug number in the changelog entry.


diff --git a/debian/changelog b/debian/changelog
index e58aa37..d26f0e4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+abcm2ps (8.14.2-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Debhelper 12.
+  * Fix the build with an explicit debhelper build system.
+
+ -- Nicolas Boulenguez   Sun, 13 Jan 2019 18:10:08 +0100
+
 abcm2ps (8.14.2-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --git a/debian/compat b/debian/compat
deleted file mode 100644
index b4de394..000
--- a/debian/compat
+++ /dev/null
@@ -1 +0,0 @@
-11
diff --git a/debian/control b/debian/control
index ed43b92..d016670 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: text
 Priority: optional
 Maintainer: Anselm Lingnau 
 Build-Depends:
- debhelper (>= 11),
+ debhelper-compat (= 12),
  libfreetype6-dev,
  libpango1.0-dev,
  pkg-config,
diff --git a/debian/rules b/debian/rules
index e864f68..e2bff7f 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,4 +4,4 @@ export DEB_BUILD_MAINT_OPTIONS := hardening=+all
 export DEB_LDFLAGS_MAINT_APPEND := -Wl,--as-needed
 
 %:
-   dh $@
+   dh $@ --buildsystem=autoconf
--- End Message ---
--- Begin Message ---
Source: abcm2ps
Source-Version: 8.14.2-0.2

We believe that the bug you reported is fixed in the latest version of
abcm2ps, 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.
Nicolas Boulenguez  (supplier of updated abcm2ps 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: Sun, 27 Jan 2019 18:50:50 +0100
Source: abcm2ps
Binary: abcm2ps
Architecture: source
Version: 8.14.2-0.2
Distribution: unstable
Urgency: medium
Maintainer: Anselm Lingnau 
Changed-By: Nicolas Boulenguez 
Description:
 abcm2ps- Translates ABC music description files to PostScript
Closes: 919219 919514
Changes:
 abcm2ps (8.14.2-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop obsolete README.Debian. Closes: #919514.
   * Debhelper 12.
   * Cherry-pick bad-ps-when-centered-or-right-aligned.diff from upstream CVS.
   * Fix the build with an explicit debhelper build system. Closes: #919219.
Checksums-Sha1:
 d965b94c8f6381c700b1b077eacf011d2bf61eed 1827 abcm2ps_8.14.2-0.2.dsc
 f28e69b73309d8d03eefaadace43d43c680f3402 4460 abcm2ps_8.14.2-0.2.debian.tar.xz
Checksums-Sha256:
 52ca87d6ee1863424fb3873db16ad1600328aa5bb0306032a130e18a514f3f9b 1827 
abcm2ps_8.14.2-0.2.dsc
 06eda0ad1166eb8ef1318ec55c53e26286298ea972449217a9b149140bd70695 4460 
abcm2ps_8.14.2-0.2.debian.tar.xz
Files:
 03a279f9d6d4cedf472ae5a24990d58e 1827 text optional abcm2ps_8.14.2-0.2.dsc
 2849ac3a8629b6c70b858b486d5d28ac 4460 text optional 
abcm2ps_8.14.2-0.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAlxN9ZsTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jWqjD/967RqTxesejUEqNkuHOKXCB3tZtaE6
heelT5oYNcB5EM76gak+qBmhSz+O0lknBV9XnFIDAkeVj2Zq/M/ljGxPmVB7oLDo

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has 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.)


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

according to https://buildd.debian.org/status/package.php?p=coq
the package fails to build at least on armel and the mips* architectures.
--- End Message ---
--- Begin Message ---
Source: coq
Source-Version: 8.9.0-1

We believe that the bug you reported is fixed in the latest version of
coq, 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.
Benjamin Barenblat  (supplier of updated coq 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: Wed, 06 Feb 2019 12:41:09 -0500
Source: coq
Binary: coq coq-dbgsym coq-theories coq-theories-dbgsym libcoq-ocaml 
libcoq-ocaml-dbgsym libcoq-ocaml-dev
Architecture: source amd64
Version: 8.9.0-1
Distribution: unstable
Urgency: high
Maintainer: Debian OCaml Maintainers 
Changed-By: Benjamin Barenblat 
Description:
 coq- proof assistant for higher-order logic (toplevel and compiler)
 coq-theories - proof assistant for higher-order logic (theories)
 libcoq-ocaml - runtime libraries for Coq
 libcoq-ocaml-dev - development libraries and tools for Coq
Closes: 736761 854147 877938 919462
Changes:
 coq (8.9.0-1) unstable; urgency=high
 .
   * New upstream release
   * Set CAML_LD_LIBRARY_PATH and COQLIB correctly during building
 (Closes: #919462)
   * Coq no longer ships an Emacs mode; users should migrate to Proof
 General (Closes: #736761, #854147, #877938)
Checksums-Sha1:
 9bbd3854ecbfb64f66724d1f84ffbf94da076416 2417 coq_8.9.0-1.dsc
 3c87729e8528f060bf77994386faafb30180ec76 5395769 coq_8.9.0.orig.tar.gz
 14194604881ad111d1cb61d48d6bfb0a8dfa3f6a 27816 coq_8.9.0-1.debian.tar.xz
 6d94e4a8b95d18300479e85a88aba3ddf8b8c990 3736676 coq-dbgsym_8.9.0-1_amd64.deb
 e89f1bc50b17201c8b433ea73a258c11dce56cf7 773124 
coq-theories-dbgsym_8.9.0-1_amd64.deb
 6ccb1474dfa447143d8d639e722b9a0e3121a23d 29737672 
coq-theories_8.9.0-1_amd64.deb
 987692ef011f0d65c694bde4bbe66b710feeffc1 14840 coq_8.9.0-1_amd64.buildinfo
 7cec356e8f21970af83002cd224e90fe7cea66b7 58990560 coq_8.9.0-1_amd64.deb
 ac7f216c33ff1cf53ff0239da632274774a7522d 534608 
libcoq-ocaml-dbgsym_8.9.0-1_amd64.deb
 4e5ad529c09eb21295ce0a479b6d1c4ee71c56c0 13703936 
libcoq-ocaml-dev_8.9.0-1_amd64.deb
 946676d495835202c8096f47a11333fa78c07248 5463112 libcoq-ocaml_8.9.0-1_amd64.deb
Checksums-Sha256:
 a58269491c02821e38e3bcdf27a706679313b566443118320e3e352019f35a0e 2417 
coq_8.9.0-1.dsc
 6468ba1b0e5f0168dcd03b29de573be2198e1a2e0311a99f8d418f4d08458908 5395769 
coq_8.9.0.orig.tar.gz
 a8f122b61740f994bcdb3cc5e96cd82e31ec9e8f3d163b7afe546a590230acbd 27816 
coq_8.9.0-1.debian.tar.xz
 078f00688810975ad8cc3f6fc21524470873396df08fab0d0df0443b9de4d6ee 3736676 
coq-dbgsym_8.9.0-1_amd64.deb
 d1e8749133414ca9e8f94c773d6c1915c30d93a74633635377605f549c79b143 773124 
coq-theories-dbgsym_8.9.0-1_amd64.deb
 b08ab391ee8385f82d4f25c0edcd2e974ddc4385497afb39c027202be4fefcad 29737672 
coq-theories_8.9.0-1_amd64.deb
 16f3bad4dc04e2740e937dadc20d351130c6fd17ad101194abf9b859986c0da7 14840 
coq_8.9.0-1_amd64.buildinfo
 cfa6621744062e4c39a9da4d4beaa15e7af8bcb571f75da71c67040f51ce02c8 58990560 
coq_8.9.0-1_amd64.deb
 1ec5e056d451f08b6e77b3fea84f66bc7b4647ffe339907ccd7613ceab3b68f2 534608 
libcoq-ocaml-dbgsym_8.9.0-1_amd64.deb
 380b71f424d119587d5387055ae272fe33cf187f4c84fc5131af659fb659e474 13703936 
libcoq-ocaml-dev_8.9.0-1_amd64.deb
 589531afe8e00fd3f711d2c4d5eed9003f9c4f5db197132f0160e8f24ff43d59 5463112 
libcoq-ocaml_8.9.0-1_amd64.deb
Files:
 77c6f5e9b407b3e50e0d82c9138225c4 2417 math optional coq_8.9.0-1.dsc
 63e06c572a4503e22c651ce8b0237efa 5395769 math optional coq_8.9.0.orig.tar.gz
 d5d3dccd2c2f9cbe26c960d237c7c86f 27816 math 

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

[Debian Bug Tracking System]

Your message dated Wed, 06 Feb 2019 19:04:05 +
with message-id 
and subject line Bug#919219: fixed in abcm2ps 8.14.2-0.2
has caused the Debian Bug report #919219,
regarding abcm2ps: FTBFS because debhelper uses ninja build system instead of 
autoconf
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.)


-- 
919219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: abcm2ps
Version: 8.14.2-0.1
Severity: serious
Tags: patch
Justification: failure to build from scratch

Hello.

My NMU fails to build because debhelper uses ./build.ninja instead of
./configure and ./Makefile.in.  This is quite surprising, and I cannot
reproduce the issue in my chroot.

However, the attached patch selects an explicit build system and most
probably fixes the issue. It upgrades to debhelper 12 as well.

Do you want to upload the fix?
May I prepare another NMU?
Shall I set a shorter delay?
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+abcm2ps (8.14.2-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Debhelper 12.
+  * Fix the build with an explicit debhelper build system.
+
+ -- Nicolas Boulenguez   Sun, 13 Jan 2019 18:10:08 +0100
+
 abcm2ps (8.14.2-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
--- a/debian/compat
+++ /dev/null
@@ -1,1 +0,0 @@
-11
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: text
 Priority: optional
 Maintainer: Anselm Lingnau 
 Build-Depends:
- debhelper (>= 11),
+ debhelper-compat (= 12),
  libfreetype6-dev,
  libpango1.0-dev,
  pkg-config,
--- a/debian/rules
+++ b/debian/rules
@@ -4,4 +4,4 @@ export DEB_BUILD_MAINT_OPTIONS := hardening=+all
 export DEB_LDFLAGS_MAINT_APPEND := -Wl,--as-needed
 
 %:
-	dh $@
+	dh $@ --buildsystem=autoconf
--- End Message ---
--- Begin Message ---
Source: abcm2ps
Source-Version: 8.14.2-0.2

We believe that the bug you reported is fixed in the latest version of
abcm2ps, 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.
Nicolas Boulenguez  (supplier of updated abcm2ps 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: Sun, 27 Jan 2019 18:50:50 +0100
Source: abcm2ps
Binary: abcm2ps
Architecture: source
Version: 8.14.2-0.2
Distribution: unstable
Urgency: medium
Maintainer: Anselm Lingnau 
Changed-By: Nicolas Boulenguez 
Description:
 abcm2ps- Translates ABC music description files to PostScript
Closes: 919219 919514
Changes:
 abcm2ps (8.14.2-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop obsolete README.Debian. Closes: #919514.
   * Debhelper 12.
   * Cherry-pick bad-ps-when-centered-or-right-aligned.diff from upstream CVS.
   * Fix the build with an explicit debhelper build system. Closes: #919219.
Checksums-Sha1:
 d965b94c8f6381c700b1b077eacf011d2bf61eed 1827 abcm2ps_8.14.2-0.2.dsc
 f28e69b73309d8d03eefaadace43d43c680f3402 4460 abcm2ps_8.14.2-0.2.debian.tar.xz
Checksums-Sha256:
 52ca87d6ee1863424fb3873db16ad1600328aa5bb0306032a130e18a514f3f9b 1827 
abcm2ps_8.14.2-0.2.dsc
 06eda0ad1166eb8ef1318ec55c53e26286298ea972449217a9b149140bd70695 4460 
abcm2ps_8.14.2-0.2.debian.tar.xz
Files:
 03a279f9d6d4cedf472ae5a24990d58e 1827 text optional abcm2ps_8.14.2-0.2.dsc
 2849ac3a8629b6c70b858b486d5d28ac 4460 text optional 
abcm2ps_8.14.2-0.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAlxN9ZsTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jWqjD/967RqTxesejUEqNkuHOKXCB3tZtaE6
heelT5oYNcB5EM76gak+qBmhSz+O0lknBV9XnFIDAkeVj2Zq/M/ljGxPmVB7oLDo
b4BiEFFpuruu4Xslo/YLU69dGG45Kul7WdcLW95gk5G4zRwgtJbEtQyLh4k6wRlZ
PG29KlePupkPRXJVSVsOkT+C9moB6mkNDbd4jBp1EMwbEbgPzbwAIyAkmiQEJCYM
pv5z4bivUzf09iiGZjH/8BpRLLkF1aFLqjm4XtBrNZ14d1zichfrruaLknAw/sEs
hTYbagWT9vBwvpbxuW9YW2QgbIsTIu1AIGvT0J2sJ60TU7WNSE4++L8sfNh74JBl
vmvabPFf3M8yvddbQL35H2jp6YmUC+5KLELFklA5rUINHeP6GtKi3/+z0c33kEwp
WBbm2mMggqdbpzkj87VAwPAudyQqbzuCeORjMwO8Ke/66vAXHW5DXsdfYU2tbee2
czeCYfgdpxLHou/HKcMShLKyp6DW3Uc1+d+awrDk/rqhtWSKS4QIMoy1fkkA+JfJ

Processed: found 918973 in 2.1.0-2

[Debian Bug Tracking System]

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

> found 918973 2.1.0-2
Bug #918973 [libtss2-udev] udev rules and created user conflict with the one 
shipped in trousers package
Marked as found in versions tpm2-tss/2.1.0-2.
> thanks
Stopping processing here.

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

Bug#824229: Good News

[Chris Withers Green]

You are lucky,Two Million has just been donated to you, contact: 
lerynnewest...@outlook.com for more details.
University of Northampton: Transforming Lives and Inspiring Change 
www.northampton.ac.uk This e-mail is private and may be confidential and is for 
the intended recipient only. If you are not the intended recipient you are 
strictly prohibited from using, printing, copying, distributing or 
disseminating this e-mail or any information contained in it. We virus scan all 
E-mails leaving The University of Northampton but no warranty is given that 
this E-mail and any attachments are virus free. You should undertake your own 
virus checking. The right to monitor E-mail communications through our networks 
is reserved by us.

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

[Adrian Bunk]

Source: ciftilib
Version: 1.5.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=ciftilib

...
 7/35 Test  #7: 
datatype-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.dscalar.nii 
..***Failed0.01 sec
CMake Error at /<>/cmake/scripts/testmd5.cmake:4 (MESSAGE):
  expected 6db4a73e4e11a1ac0a5e7cbfb56eff40, got
  2f556798b4f8d4219bf22c4dcab20c79
...
14/35 Test #14: 
datatype-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.dtseries.nii 
.***Failed0.01 sec
CMake Error at /<>/cmake/scripts/testmd5.cmake:4 (MESSAGE):
  expected f321156573ed8f165b208d84769bfd9a, got
  92b1c53de71ef4c4d669a32e45c718ae
...
21/35 Test #21: 
datatype-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.ptseries.nii 
.***Failed0.01 sec
CMake Error at /<>/cmake/scripts/testmd5.cmake:4 (MESSAGE):
  expected 794d60d9d397fe341e18313efeeac5ea, got
  524bc9b45a4c606c012e879d58535467
...
28/35 Test #28: datatype-md5-Conte69.parcellations_VGD11b.32k_fs_LR.dlabel.nii 
.***Failed0.01 sec
CMake Error at /<>/cmake/scripts/testmd5.cmake:4 (MESSAGE):
  expected ea43725139bd3e152197fdf22c5e72e7, got
  5a31d95f9f22c4955e739249a0df9a79
...
35/35 Test #35: datatype-md5-ones.dscalar.nii 
..***Failed0.01 sec
CMake Error at /<>/cmake/scripts/testmd5.cmake:4 (MESSAGE):
  expected 4dbb23ab2564ba8c9f242a3cb6036600, got
  a9663c8d2d7561b6580dd3734530




86% tests passed, 5 tests failed out of 35

Total Test time (real) =   3.99 sec

The following tests FAILED:
  7 - datatype-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.dscalar.nii 
(Failed)
 14 - 
datatype-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.dtseries.nii (Failed)
 21 - 
datatype-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.ptseries.nii (Failed)
 28 - datatype-md5-Conte69.parcellations_VGD11b.32k_fs_LR.dlabel.nii 
(Failed)
 35 - datatype-md5-ones.dscalar.nii (Failed)
Errors while running CTest
make[2]: *** [Makefile:77: test] Error 8

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

[Markus Koschany]

Dear maintainer,

I've uploaded a new version of libthrift-java, versioned as 0.9.1-2.1 to
fix CVE-2018-1320. Please find attached the debdiff.


Regards,

Markus
diff -Nru libthrift-java-0.9.1/debian/changelog 
libthrift-java-0.9.1/debian/changelog
--- libthrift-java-0.9.1/debian/changelog   2014-10-17 00:28:43.0 
+0200
+++ libthrift-java-0.9.1/debian/changelog   2019-02-06 19:04:12.0 
+0100
@@ -1,3 +1,15 @@
+libthrift-java (0.9.1-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix CVE-2018-1320:
+It was discovered that it was possible to bypass SASL negotiation
+isComplete validation in the org.apache.thrift.transport.TSaslTransport
+class. An assert used to determine if the SASL handshake had successfully
+completed could be disabled in production settings making the validation
+incomplete. (Closes: #918736)
+
+ -- Markus Koschany   Wed, 06 Feb 2019 19:04:12 +0100
+
 libthrift-java (0.9.1-2) unstable; urgency=low
 
   * Use 3.0 (quilt) source format.
diff -Nru libthrift-java-0.9.1/debian/patches/CVE-2018-1320.patch 
libthrift-java-0.9.1/debian/patches/CVE-2018-1320.patch
--- libthrift-java-0.9.1/debian/patches/CVE-2018-1320.patch 1970-01-01 
01:00:00.0 +0100
+++ libthrift-java-0.9.1/debian/patches/CVE-2018-1320.patch 2019-02-06 
19:04:12.0 +0100
@@ -0,0 +1,32 @@
+From: Markus Koschany 
+Date: Wed, 6 Feb 2019 18:59:31 +0100
+Subject: CVE-2018-1320
+
+Bug-Debian: https://bugs.debian.org/918736
+Origin: 
https://github.com/apache/thrift/commit/d973409661f820d80d72c0034d06a12348c8705e
+---
+ src/org/apache/thrift/transport/TSaslTransport.java | 4 +---
+ 1 file changed, 1 insertion(+), 3 deletions(-)
+
+diff --git a/src/org/apache/thrift/transport/TSaslTransport.java 
b/src/org/apache/thrift/transport/TSaslTransport.java
+index b54746c..2f62016 100644
+--- a/src/org/apache/thrift/transport/TSaslTransport.java
 b/src/org/apache/thrift/transport/TSaslTransport.java
+@@ -268,7 +268,7 @@ abstract class TSaslTransport extends TTransport {
+ if (message.status == NegotiationStatus.COMPLETE &&
+ getRole() == SaslRole.CLIENT) {
+   LOGGER.debug("{}: All done!", getRole());
+-  break;
++  continue;
+ }
+ 
+ sendSaslMessage(sasl.isComplete() ? NegotiationStatus.COMPLETE : 
NegotiationStatus.OK,
+@@ -276,8 +276,6 @@ abstract class TSaslTransport extends TTransport {
+   }
+   LOGGER.debug("{}: Main negotiation loop complete", getRole());
+ 
+-  assert sasl.isComplete();
+-
+   // If we're the client, and we're complete, but the server isn't
+   // complete yet, we need to wait for its response. This will occur
+   // with ANONYMOUS auth, for example, where we send an initial response
diff -Nru libthrift-java-0.9.1/debian/patches/series 
libthrift-java-0.9.1/debian/patches/series
--- libthrift-java-0.9.1/debian/patches/series  1970-01-01 01:00:00.0 
+0100
+++ libthrift-java-0.9.1/debian/patches/series  2019-02-06 19:04:12.0 
+0100
@@ -0,0 +1 @@
+CVE-2018-1320.patch


signature.asc
Description: OpenPGP digital signature

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

[Adrian Bunk]

Source: sparse
Version: 0.6.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=sparse

...
  TESTpredefined macros for LP64 (preprocessor/predef-lp64.c)
Using command   : test-linearize -Wno-decl -m64 $file
Expecting exit value: 0
error: test 'preprocessor/predef-lp64.c' failed
error:  Pattern 'ret\..*\$0' unexpectedly absent
...
KO: out of 584 tests, 527 passed, 57 failed
56 of them are known to fail
43 tests were disabled
make[2]: *** [Makefile:230: check] Error 1

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

[Debian Bug Tracking System]

Processing control commands:

> affects -1 python3-xopen
Bug #921553 [python-xopen] python{,3}-xopen: missing dependencies
Added indication that 921553 affects python3-xopen

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

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

[Adrian Bunk]

Package: python-xopen
Version: 0.5.0-1
Severity: serious
Control: affects -1 python3-xopen

The following dependencies are missing for loading the module
(import xopen):

python-xopen:
- python-pkg-resources
- python-bz2file

python3-xopen:
- python3-pkg-resources

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

[Debian Bug Tracking System]

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

> reassign 919231 systemd 240-5
Bug #919231 [salt-master] salt-master: Upgrade Stretch -> Buster: permission 
denied on certain files/directories
Bug reassigned from package 'salt-master' to 'systemd'.
No longer marked as found in versions salt/2018.3.3+dfsg1-2.
Ignoring request to alter fixed versions of bug #919231 to the same values 
previously set
Bug #919231 [systemd] salt-master: Upgrade Stretch -> Buster: permission denied 
on certain files/directories
Marked as found in versions systemd/240-5.
> retitle 919231 CacheDirectory/StateDirectory does not change owner/group
Bug #919231 [systemd] salt-master: Upgrade Stretch -> Buster: permission denied 
on certain files/directories
Changed Bug title to 'CacheDirectory/StateDirectory does not change 
owner/group' from 'salt-master: Upgrade Stretch -> Buster: permission denied on 
certain files/directories'.
> thanks
Stopping processing here.

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

Bug#919231: Salt-master unable to access directories

[Benjamin Drung]

reassign 919231 systemd 240-5
retitle 919231 CacheDirectory/StateDirectory does not change owner/group
thanks

Hi Stijn,

your bug description was enough for me to reproduce this misbehavior
and tracked it down to systemd not behaving like the documentation
describes:

  StateDirectory=, CacheDirectory=
Except in case of ConfigurationDirectory=, the innermost specified
directories will be owned by the user and group specified in User=
and Group=. If the specified directories already exist and their
owning user or group do not match the configured ones, all files
and directories below the specified directories as well as the
directories themselves will have their file ownership recursively
changed to match what is configured. As an optimization, if the
specified directories are already owned by the right user and
group, files and directories below of them are left as-is, even
if they do not match what is requested.

The salt-master systemd service is configured to use
/var/lib/salt/pki/master and /var/cache/salt/master as state and cache
directory. salt should change the ownership, but it does not. Steps to
reproduce:

Take a minimal Debian 9 installation and:

```
root@debian:~# apt install salt-master
root@debian:~# sed -i 's/stretch/buster/g' /etc/apt/sources.list
root@debian:~# apt upgrade
[...]
Setting up salt-master (2018.3.3+dfsg1-2) ...
Installing new version of config file /etc/salt/master ...
Job for salt-master.service failed because the control process exited
with error code.
See "systemctl status salt-master.service" and "journalctl -xe" for
details.
invoke-rc.d: initscript salt-master, action "restart" failed.
● salt-master.service - The Salt Master Server
   Loaded: loaded (/lib/systemd/system/salt-master.service; enabled;
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-02-06 16:16:37
UTC; 8ms ago
 Docs: man:salt-master(1)
   file:///usr/share/doc/salt/html/contents.html
   https://docs.saltstack.com/en/latest/contents.html
  Process: 31417 ExecStart=/usr/bin/salt-master (code=exited,
status=13)
 Main PID: 31417 (code=exited, status=13)

Feb 06 16:16:37 debian systemd[1]: Starting The Salt Master Server...
Feb 06 16:16:37 debian salt-master[31417]: Failed to create directory
path "/var/lib/salt/pki/master/minions" - [Errno 13] Permission denied:
'/var/lib/salt/pki/master/minions'
Feb 06 16:16:37 debian systemd[1]: salt-master.service: Main process
exited, code=exited, status=13/n/a
Feb 06 16:16:37 debian systemd[1]: salt-master.service: Failed with
result 'exit-code'.
Feb 06 16:16:37 debian systemd[1]: Failed to start The Salt Master
Server.
dpkg: error processing package salt-master (--configure):
 installed salt-master package post-installation script subprocess
returned error exit status 1
[...]
```

Instead of doing an upgrade test, you can just do the test on testing
by stopping salt-master, changing the permission to root and starting
salt-master.

```
root@debian:~# systemctl cat salt-master.service 
# /lib/systemd/system/salt-master.service
[Unit]
Description=The Salt Master Server
Documentation=man:salt-master(1)
file:///usr/share/doc/salt/html/contents.html 
https://docs.saltstack.com/en/latest/contents.html
After=network.target

[Service]
LimitNOFILE=10
Type=notify
NotifyAccess=all
ExecStart=/usr/bin/salt-master
User=salt
Group=salt
CacheDirectory=salt/master
RuntimeDirectory=salt
StateDirectory=salt/pki/master

[Install]
WantedBy=multi-user.target
root@debian:~# ls -ld /var/lib/salt /var/lib/salt/pki
/var/lib/salt/pki/master
drwxr-xr-x 3 salt salt 4096 Feb  6 16:16 /var/lib/salt
drwxr-xr-x 3 root root 4096 Feb  6 16:16 /var/lib/salt/pki
drwx-- 7 root root 4096 Feb  6 16:10 /var/lib/salt/pki/master
root@debian:~# ls -ld /var/cache/salt /var/cache/salt/master
drwxr-xr-x 3 root root 4096 Feb  6 16:10 /var/cache/salt
drwxr-xr-x 8 root root 4096 Feb  6 16:11 /var/cache/salt/master
rroot@debian:~# dpkg -l | grep systemd | sed 's/ \+amd64 .*$//'
ii  libnss-systemd:amd64  240-5
ii  libpam-systemd:amd64  240-5
ii  libsystemd0:amd64 240-5
ii  python-systemd234-2+b1
ii  python3-systemd   234-2+b1
ii  systemd   240-5
ii  systemd-sysv  240-5
```

The workaround is to manually change the owner/group to salt:

root@debian:~# chown -R salt:salt /var/lib/salt/pki/master 
/var/cache/salt/master
root@debian:~# systemctl start salt-master

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de

Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim
Weiss

Member of United Internet

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

[Hilko Bengen]

Source: golang-1.8
Version: 1.8.1-1+deb9u1
Severity: grave

Dear Maintainer,

with libyara-dev, libyara3, golang-github-hillu-go-yara-dev from
stretch-backports, the attached trivial tool used to build fine, both
with and without build tag "yara_static" which causes pkg-config to be
called using the "--static" parameter.

,
| $ export GOPATH=/usr/share/gocode
| $ /usr/lib/go-1.8/bin/go build -x -tags yara_static t.go
| WORK=/tmp/go-build964606946
| mkdir -p $WORK/github.com/hillu/go-yara/_obj/
| mkdir -p $WORK/github.com/hillu/
| pkg-config --cflags --static yara
| pkg-config --libs --static yara
| [...]
`

(We can't really build a real statically-linked executable using glibc,
but never mind, this is just intended as a a demo / reproducer.)

After upgrading golang-1.8 to version 1.8.1-1+deb9u1, this breaks
because cgo no longer likes the pkg-config parameters:

,
| $ /usr/lib/go-1.8/bin/go build -x -tags yara_static t.go
| WORK=/tmp/go-build227067233
| mkdir -p $WORK/github.com/hillu/go-yara/_obj/
| mkdir -p $WORK/github.com/hillu/
| go build github.com/hillu/go-yara: invalid pkg-config package name: --static
`

I am pretty sure that this was introduced with the fix for
CVE-2018-6574 which introduced the following check:

,
| for _, pkg := range pkgs {
| if !SafeArg(pkg) {
| return nil, nil, fmt.Errorf("invalid pkg-config package name: 
%s", pkg)
| }
| }
`

Cheers,
-Hilko
package main

import "github.com/hillu/go-yara"

func main() {
yara.NewCompiler()
}

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

[Simon Deziel]

Here is a merge request [*] to disable chroot'ing again like it has been
since version 1.0.0-3

Regards,
Simon

*: https://salsa.debian.org/dns-team/unbound/merge_requests/3



signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has 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.)


-- 
921450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fetchmail
Version: 6.4.0~beta4-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

fetchmail has stopped working in version 6.4.0~beta4-2.

Running the daemon gets the first mail in the queue delivered, but then it 
segfaults.

>From /var/log/syslog:

Feb  5 10:58:01 mycomputer fetchmail[3690]: starting fetchmail 6.4.0.beta4 
daemon
Feb  5 10:58:01 mycomputer fetchmail[3690]: 21 messages for user at 
mail.isp.com (1413520 octets).
Feb  5 10:58:01 mycomputer fetchmail[3690]: reading message u...@isp.com:1 of 
21 (22515 octets) flushed
Feb  5 10:58:01 mycomputer kernel: [  296.487041] fetchmail[3690]: segfault at 
14 ip 55f377747dda sp 7ffdd477ae80 error 6 in 
fetchmail[55f377747000+2b000]
Feb  5 10:58:01 mycomputer kernel: [  296.487050] Code: ff 25 1a 12 04 00 68 d8 
00 00 00 e9 60 f2 ff ff ff 25 12 12 04 00 66 90 00 00 00 00 00 00 00 00 48 8b 
04 25 00 00 00 00 0f 0b  04 25 14 00 00 00 00 00 00 00 0f 0b 66 0f 1f 84 00 
00 00 00 00 

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/12 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)
LSM: AppArmor: enabled

Versions of packages fetchmail depends on:
ii  adduser   3.118
ii  debianutils   4.8.6.1
ii  libc6 2.28-5
ii  libcom-err2   1.44.5-1
ii  libgssapi-krb5-2  1.17-1
ii  libk5crypto3  1.17-1
ii  libkrb5-3 1.17-1
ii  libssl1.1 1.1.1a-1
ii  lsb-base  10.2018112800

Versions of packages fetchmail recommends:
ii  ca-certificates  20190110

Versions of packages fetchmail suggests:
ii  exim4-daemon-light [mail-transport-agent]  4.92~RC5-1
ii  fetchmailconf  6.4.0~beta4-2
pn  resolvconf 

-- Configuration Files:
/etc/default/fetchmail changed:

# This file will be used to declare some vars for fetchmail
#
# Uncomment the following if you don't want localized log messages
# export LC_ALL=C

# If you want to specify any additional OPTION to the start
# scripts specify them here
# OPTIONS=...

# Declare here if we want to start fetchmail. 'yes' or 'no'
START_DAEMON=yes

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fetchmail
Source-Version: 6.4.0~beta4-3

We believe that the bug you reported is fixed in the latest version of
fetchmail, 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.
Laszlo Boszormenyi (GCS)  (supplier of updated fetchmail 
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: Wed, 06 Feb 2019 16:33:00 +
Source: fetchmail
Architecture: source
Version: 6.4.0~beta4-3
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 921450
Changes:
 fetchmail (6.4.0~beta4-3) unstable; urgency=medium
 .
   * Backport fix potential SIGSEGV in pop3_delete (closes: #921450).
   * Backport native name verification for OpenSSL.
Checksums-Sha1:
 5fd7cab6c5aeefda64605bf441ce9e879769aa8d 1911 fetchmail_6.4.0~beta4-3.dsc
 ea029cdbdade40a682310c523408a7547ea3c44a 48568 
fetchmail_6.4.0~beta4-3.debian.tar.xz
 f55a3bfca4308ad043cd5464b7ed73c5c85c3b4a 8299 
fetchmail_6.4.0~beta4-3_amd64.buildinfo
Checksums-Sha256:
 a71bd2b38d7057e77ee3a9cc3c4f6f4195ec857e6cffa07d4a40ded19b28646c 1911 
fetchmail_6.4.0~beta4-3.dsc
 a2216a6c4c01bf0b5510d7e045bef94c8e02caf38fa1b0641e1db9e41dd57e39 48568 
fetchmail_6.4.0~beta4-3.debian.tar.xz
 

Bug#921542: tc qdisc kernel crash

[Adrian]

Package: src:linux
Version: 4.19.16-1
Severity: critical

When I'm trying to use this script:

#!/bin/bash

ifaces[0]="tun0"
ifaces[1]="ens192"

ifaceIn="ifb0"
ifaceOut="ifb1"

#echo ${#iface[@]}
#exit

tc qdisc del dev $ifaceIn root

for iface in ${ifaces[@]}; do
echo "Delete qdisc ingress on ${iface}"
tc qdisc del dev ${iface} handle : ingress
echo "Add qdisc ingress on ${iface}"
tc qdisc add dev ${iface} handle : ingress
#tc filter add dev ${iface} parent : protocol ip u32 match u32 0 0
action mirred egress redirect dev ${ifaceIn}
done

#tc qdisc add dev $ifaceIn root handle 1: prio bands 5
#tc qdisc add dev $ifaceIn parent 1:1 handle 10: sfq
#tc qdisc add dev $ifaceIn parent 1:2 handle 20: sfq
#tc qdisc add dev $ifaceIn parent 1:3 handle 30: sfq
#tc qdisc add dev $ifaceIn parent 1:4 handle 40: sfq
#tc qdisc add dev $ifaceIn parent 1:5 handle 50: sfq


### Create a root qdisc type DSmark
echo "Add qdisc root on ${ifaceIn} type DSmark"
tc qdisc add dev $ifaceIn handle 1:0 root dsmark indices 64 set_tc_index
### filter to copy the correct DS filed from the IP packet to skb->tc_index
echo "Add filter on parent 1:0  ${ifaceIn} for set the tcindex"
tc filter add dev $ifaceIn parent 1:0 protocol ip prio 1 tcindex mask 0xfc
shift 2

### Add a PRIO class with 5 bands on 1:0
echo "Add qdisc on parent 1:0 ${ifaceIn} as PRIO with 5 bands"
tc qdisc add dev $ifaceIn parent 1:0 handle 2:0 prio bands 5

### Add a qdisc on the leaf PRIO 2:1
#tc qdisc add dev $ifaceIn parent 2:1 tbf rate 1.5Mbit burst 1.5kB limit 1.6kB
echo "Add qdisc on leaf parent 2:1 ${ifaceIn} as SFQ"
tc qdisc add dev $ifaceIn parent 2:1 sfq
### Match the traffic with DSCP EF (ToS 0xb8 / DSCP 0x2e) mark
echo "Add filter on parent 2:0 ${ifaceIn} to match DSCP EF (ToS 0xb8 / DSCP
0x2e) mark and send the traffic to class 2:1"
tc filter add dev $ifaceIn parent 2:0 protocol ip prio 1 handle 0x2e tcindex
classid 2:1 pass_on

### Add a qdisck on leaf PRIO 2:2 - IPTV services
echo "Add qdisc on leaf parent 2:1 ${ifaceIn} as SFQ"
tc qdisc add dev $ifaceIn parent 2:2 sfq
### Match the traffic with DSCP AF41 (ToS 0x88 / DSCP 0x22) mark
echo "Add filter on parent 2:0 ${ifaceIn} to match DSCP AF41 (ToS 0x88 / DSCP
0x22 mark) and send the traffic to class 2:2"
tc filter add dev $ifaceIn parent 2:0 protocol ip prio 2 handle 0x22 tcindex
classid 2:2 pass_on

### Best Effort traffic move to 2:5
#BE class(2:2)
#tc qdisc add dev $ifaceIn parent 2:5 red limit 60KB min 15KB max 45KB burst 20
avpkt 1000 bandwidth 10Mbit probability 0.4
echo "Add qdisc on leaf parent 2:5 ${ifaceIn} as SFQ"
tc qdisc add dev $ifaceIn parent 2:5 sfq
echo "Add filter on parent 2:0 ${ifaceIn} to match DSCP BE (ToS 0x0 / DSCP 0x0
mark) and send the traffic to class 2:5"
tc filter add dev $ifaceIn parent 2:0 protocol ip prio 5 handle 0 tcindex mask
0 classid 2:5 pass_on

exit


And run it 2-3 times I'm getting a severe kernel crash:

Feb  6 17:15:34 Telenet-PC kernel: [  511.608275] general protection fault:
 [#1] SMP PTI
Feb  6 17:15:34 Telenet-PC kernel: [  511.608279] CPU: 2 PID: 3889 Comm: tc Not
tainted 4.19.0-2-amd64 #1 Debian 4.19.16-1
Feb  6 17:15:34 Telenet-PC kernel: [  511.608281] Hardware name: VMware, Inc.
VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 05/19/2017
Feb  6 17:15:34 Telenet-PC kernel: [  511.608285] RIP:
0010:__kmalloc_node+0x195/0x2b0
Feb  6 17:15:34 Telenet-PC kernel: [  511.608288] Code: fa 48 8b 74 24 08 e8 7a
54 7d 00 4c 8b 13 58 4d 85 d2 75 d7 e9 75 ff ff ff 41 8b 5a 20 49 8b 3a 48 8d
4a 01 4c 89 f8 4c 01 fb <48> 33 1b 49 33 9a 38 01 00 00 65 48 0f c7 0f 0f 94 c0
84 c0 0f 84
Feb  6 17:15:34 Telenet-PC kernel: [  511.608289] RSP: 0018:b4ad4322b978
EFLAGS: 00010286
Feb  6 17:15:34 Telenet-PC kernel: [  511.608291] RAX: d36cc438 RBX:
d36cc438 RCX: 0181
Feb  6 17:15:34 Telenet-PC kernel: [  511.608292] RDX: 0180 RSI:
006012c0 RDI: 00025120
Feb  6 17:15:34 Telenet-PC kernel: [  511.608294] RBP: 006012c0 R08:
984037ca5120 R09: 984037807900
Feb  6 17:15:34 Telenet-PC kernel: [  511.608295] R10: 984037806a00 R11:
 R12: 1c00
Feb  6 17:15:34 Telenet-PC kernel: [  511.608296] R13:  R14:
984037806a00 R15: d36cc438
Feb  6 17:15:34 Telenet-PC kernel: [  511.608298] FS:  7fc881130800()
GS:984037c8() knlGS:
Feb  6 17:15:34 Telenet-PC kernel: [  511.608299] CS:  0010 DS:  ES: 
CR0: 80050033
Feb  6 17:15:34 Telenet-PC kernel: [  511.608300] CR2: 7fc88153fee0 CR3:
000141b9e006 CR4: 003606e0
Feb  6 17:15:34 Telenet-PC kernel: [  511.608336] DR0:  DR1:
 DR2: 
Feb  6 17:15:34 Telenet-PC kernel: [  511.608337] DR3:  DR6:
fffe0ff0 DR7: 0400
Feb  6 17:15:34 Telenet-PC kernel: [  511.608338] Call Trace:
Feb  6 17:15:34 Telenet-PC kernel: [  

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has been dealt 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.)


-- 
913843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-mail-gpg
Version: 0.4.0-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-mail-gpg.html

...
===
Failure: test: Mail::Message with gpg turned on should raise bad passphrase on 
decrypt. (MessageTest)
/build/1st/ruby-mail-gpg-0.4.0/test/message_test.rb:222:in `block (4 levels) in 
'

 expected but was
)>

diff:
? GPGME::Error::Dec ryptFailed
?  OF ()
===

Finished in 48.989274563 seconds.
---
118 tests, 546 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
99.1525% passed
---
2.41 tests/s, 11.15 assertions/s
rake aborted!
Command failed with status (1): [ruby -w -I"lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/action_mailer_test.rb" "test/decrypted_part_test.rb" 
"test/encrypted_part_test.rb" "test/gpg_test.rb" "test/gpgme_helper_test.rb" 
"test/hkp_test.rb" "test/inline_decrypted_message_test.rb" 
"test/inline_signed_message_test.rb" "test/message_test.rb" 
"test/sign_part_test.rb" "test/version_part_test.rb" ]

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-mail-gpg-0.4.0/debian/ruby-mail-gpg returned exit code 1
make: *** [debian/rules:6: binary] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-mail-gpg
Source-Version: 0.4.0-2

We believe that the bug you reported is fixed in the latest version of
ruby-mail-gpg, 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 913...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Georg Faerber  (supplier of updated ruby-mail-gpg 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: Wed, 06 Feb 2019 16:34:11 +
Source: ruby-mail-gpg
Architecture: source
Version: 0.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Georg Faerber 
Closes: 913843
Changes:
 ruby-mail-gpg (0.4.0-2) unstable; urgency=medium
 .
   * debian/compat:
 - Drop obsolete compat file, now handled via build dependency.
   * debian/control:
 - Build depend on debhelper-compat, instead of debhelper.
 - Declare that the build doesn't need root privileges.
 - Bump Standards-Version to 4.3.0.
   * debian/copyright:
 - Bump years to include 2019.
   * debian/patches:
 - Add patch to drop failing spec due to gpgme 1.12.0. (Closes: #913843)
   * debian/rules:
 - Make the build verbose.
   * debian/upstream/signing-key.asc:
 - Remove unneeded signatures.
   * debian/.gitlab-ci.yml:
 - Add CI config.
Checksums-Sha1:
 1452bf9dc45da394741065ac165bb1ef3d928784 2166 ruby-mail-gpg_0.4.0-2.dsc
 82cb37e4ee08b36c5ea368f2f0963b41a125026c 11872 
ruby-mail-gpg_0.4.0-2.debian.tar.xz
 b817a05cee04feaa48d582b3631f36e59dbbb1e5 9829 
ruby-mail-gpg_0.4.0-2_amd64.buildinfo
Checksums-Sha256:
 fb78c5bfda3bcd674431a9d33eccad3dacd7c23860bd58582ed79f2ac0296e0a 2166 
ruby-mail-gpg_0.4.0-2.dsc
 fb9f81dafd4450f31f386fab000e1d5e3535722b3a543e3adfeecb25b921c08f 11872 
ruby-mail-gpg_0.4.0-2.debian.tar.xz
 b2eea3afdf925ff046e86315d0695fdaa161dda4e6216e7a5624bce674957ce9 9829 
ruby-mail-gpg_0.4.0-2_amd64.buildinfo
Files:
 8c496ae6df07fde4e4801ed8dec22b20 2166 ruby optional ruby-mail-gpg_0.4.0-2.dsc
 cfe611f2793e04ca6b8356e00b0589d1 11872 ruby optional 
ruby-mail-gpg_0.4.0-2.debian.tar.xz
 

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

[Debian Bug Tracking System]

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

This means that you claim 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.)


-- 
920629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: volumecontrol.app
Version: 0.7-1+b1
Severity: grave

The Quit menu item is greyed out and does not work.  Selecting missing
controls (Bass/Treble for my card) makes the "Control missing" dialog
appear but you can't get rid of it.  The app then becomes completely
unusable.

There are multiple identical entries in the log:

2019-01-27 18:57:31.160 VolumeControl[17687:17687] Target NSMenu: VolumeControl 
(Normal) does not respont to action terminate:

Apart from the spelling error this message is correct.  Note that as of
GUI 0.27.0 NSApplication -targetForAction:to:from: returns nil if the
target is not nil but it doesn't respond to the selector.

I opened Volumecontrol.gorm and noticed that the connection is
terminate: (NSMenu) while it should be NSFirst.  Changing the connection
makes the app behave as expected.  I guess it would be easier to make a
new upstream release than to deal with binary patches...

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

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

Versions of packages volumecontrol.app depends on:
ii  gnustep-back0.27   0.27.0-2
ii  gnustep-base-runtime   1.26.0-3
ii  gnustep-common [gnustep-fslayout-fhs]  2.7.0-4
ii  gnustep-gui-runtime0.27.0-3
ii  libasound2 1.1.7-2
ii  libc6  2.28-5
ii  libgnustep-base1.261.26.0-3
ii  libgnustep-gui0.27 0.27.0-3
ii  libobjc4   8.2.0-15

volumecontrol.app recommends no packages.

volumecontrol.app suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: volumecontrol.app
Source-Version: 0.8-1

We believe that the bug you reported is fixed in the latest version of
volumecontrol.app, 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.
Gürkan Myczko  (supplier of updated volumecontrol.app 
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: Wed, 06 Feb 2019 10:51:09 +0100
Source: volumecontrol.app
Architecture: source
Version: 0.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Gürkan Myczko 
Closes: 920629
Changes:
 volumecontrol.app (0.8-1) unstable; urgency=medium
 .
   * New upstream version. (Closes: #920629)
Checksums-Sha1:
 80a702267ef9a7d97a43f2b931a8e4f24a3d5355 2139 volumecontrol.app_0.8-1.dsc
 241000e9286e5d3125292f6f96a5ec7a51592da4 23586 
volumecontrol.app_0.8.orig.tar.gz
 733428f69df71c3c2293d4f5025f072ee7757aac 3764 
volumecontrol.app_0.8-1.debian.tar.xz
 f5d94b84b88a857b5e3ac94d70ab3859a90dce2f 6478 
volumecontrol.app_0.8-1_source.buildinfo
Checksums-Sha256:
 54813e38da84e63c95d8a417daa37e0c6e04c2d031642b815b7bd37de048e331 2139 
volumecontrol.app_0.8-1.dsc
 1f3f130628fe2489e3e2643d18156e500dfec6964d3405274429b695f5312b16 23586 
volumecontrol.app_0.8.orig.tar.gz
 3e3cbc60fde0823edbd67af37d81139b4cfb36a15300fcd52286cc6167ac6182 3764 
volumecontrol.app_0.8-1.debian.tar.xz
 5ece70925488f9e8b15ceac49965805297829ac0e28168b88042127e15e34fd5 6478 
volumecontrol.app_0.8-1_source.buildinfo
Files:
 4c12b068be90e05b105ab551496f55a9 2139 gnustep optional 
volumecontrol.app_0.8-1.dsc
 

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

[Simon Deziel]

Hi Ryan,

On 2019-02-06 11:12 a.m., Ryan Kavanagh wrote:
> Since the upgrade to 1.9.0-1, unbound fails to start. Purging the
> package and reinstalling does not fix the issue. The errors seem to be
> due to being unable to read various configuration files.
> 
> Feb 06 11:01:12 zeta unbound[28647]: [28647:0] error: unable to open 
> /var/lib/unbound/root.key for reading: No such file or directory
> Feb 06 11:01:12 zeta package-helper[28648]: [1549468872] 
> unbound-checkconf[28651:0] error: Could not open 
> /etc/unbound//etc/unbound/unbound.conf: No such file or director

It seems like chroot'ing to /etc/unbound is attempted. To workaround you
can try this:

cat << EOF > /etc/unbound/unbound.conf.d/chroot.conf
server:
  chroot: ""
EOF
service unbound restart

Regards,
Simon




signature.asc
Description: OpenPGP digital signature

Processed: forcibly merging 921538 921539

[Debian Bug Tracking System]

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

> forcemerge 921538 921539
Bug #921538 [unbound] Fails to start since upgrade to 1.9.0-1
Bug #921539 [unbound] unbound fails to start after upgrade
Merged 921538 921539
> thanks
Stopping processing here.

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

Bug#921539: unbound fails to start after upgrade

[Michael Stone]

Package: unbound
Version: 1.9.0-1
Severity: grave
Justification: renders package unusable

Immediately after installing 1.9.0-1, unbound refused to run after restart. 
System logs contained:

Feb  6 11:00:24 annuminas package-helper[6142]: /var/lib/unbound/root.key has 
content
Feb  6 11:00:24 annuminas unbound: [6146:0] notice: init module 0: subnet
Feb  6 11:00:24 annuminas unbound: [6146:0] notice: init module 1: validator
Feb  6 11:00:24 annuminas unbound: [6146:0] error: unable to open 
/var/lib/unbound/root.key for reading: No such file or directory
Feb  6 11:00:24 annuminas systemd[1]: unbound.service: Main process exited, 
code=exited, status=1/FAILURE
Feb  6 11:00:24 annuminas unbound: [6146:0] error: error reading 
auto-trust-anchor-file: /var/lib/unbound/root.key
Feb  6 11:00:24 annuminas systemd[1]: unbound.service: Failed with result 
'exit-code'.
Feb  6 11:00:24 annuminas unbound: [6146:0] error: validator: error in 
trustanchors config
Feb  6 11:00:24 annuminas unbound: [6146:0] error: validator: could not apply 
configuration settings.
Feb  6 11:00:24 annuminas unbound: [6146:0] error: module init for module 
validator failed
Feb  6 11:00:24 annuminas unbound: [6146:0] fatal error: failed to setup modules
Feb  6 11:00:24 annuminas kernel: [1792989.896766] audit: type=1400 
audit(1549468824.750:4639): apparmor="STATUS" operation="profile_replace" 
info="same as cur
rent profile, skipping" profile="unconfined" name="/usr/sbin/unbound" pid=6149 
comm="apparmor_parser"
Feb  6 11:00:24 annuminas systemd[1]: unbound.service: Service RestartSec=100ms 
expired, scheduling restart.
Feb  6 11:00:24 annuminas systemd[1]: unbound.service: Scheduled restart job, 
restart counter is at 1.
Feb  6 11:00:25 annuminas systemd[1]: unbound.service: Control process exited, 
code=killed, status=15/TERM
Feb  6 11:00:25 annuminas systemd[1]: unbound.service: Succeeded.

Commenting out the contents of 
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf allowed the 
process to start, presumably no longer validating DNSSEC. The 
/var/lib/unbound/root.key file is present and readable, as it was prior to the 
upgrade. 

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages unbound depends on:
ii  adduser 3.118
ii  dns-root-data   2018091102
ii  libc6   2.28-6
ii  libevent-2.1-6  2.1.8-stable-4
ii  libfstrm0   0.4.0-1
ii  libprotobuf-c1  1.3.1-1+b1
ii  libpython3.73.7.2-2
ii  libssl1.1   1.1.1a-1
ii  libsystemd0 240-5
ii  lsb-base10.2018112800
ii  openssl 1.1.1a-1
ii  unbound-anchor  1.9.0-1

unbound recommends no packages.

Versions of packages unbound suggests:
ii  apparmor  2.13.2-7

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

[Ryan Kavanagh]

Package: unbound
Version: 1.9.0-1
Severity: grave

Since the upgrade to 1.9.0-1, unbound fails to start. Purging the
package and reinstalling does not fix the issue. The errors seem to be
due to being unable to read various configuration files.

Feb 06 11:01:12 zeta unbound[28647]: [28647:0] error: unable to open 
/var/lib/unbound/root.key for reading: No such file or directory
Feb 06 11:01:12 zeta package-helper[28648]: [1549468872] 
unbound-checkconf[28651:0] error: Could not open 
/etc/unbound//etc/unbound/unbound.conf: No such file or director

--
rak@zeta:~$ sudo apt purge unbound && sudo apt install unbound
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  apg bmon byobu ccze cmatrix ipsec-tools jp2a libconfuse-common libconfuse2 
libipe7.2.7 moreutils pastebinit python-newt screen speedometer tree 
unbound-anchor
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  unbound*
0 upgraded, 0 newly installed, 1 to remove and 111 not upgraded.
After this operation, 4,286 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 450489 files and directories currently installed.)
Removing unbound (1.9.0-1) ...
Processing triggers for man-db (2.8.5-1) ...
(Reading database ... 450457 files and directories currently installed.)
Purging configuration files for unbound (1.9.0-1) ...
insserv: There is a loop between service sendsigs and racoon if stopped
insserv:  loop involving service racoon at depth 3
insserv:  loop involving service sendsigs at depth 2
insserv:  loop involving service bluetooth at depth 1
insserv:  loop involving service rsyslog at depth 4
insserv:  loop involving service avahi at depth 2
Processing triggers for systemd (240-5) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  apg bmon byobu ccze cmatrix ipsec-tools jp2a libconfuse-common libconfuse2 
libipe7.2.7 moreutils pastebinit python-newt screen speedometer tree
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  unbound
0 upgraded, 1 newly installed, 0 to remove and 111 not upgraded.
Need to get 0 B/795 kB of archives.
After this operation, 4,286 kB of additional disk space will be used.
Selecting previously unselected package unbound.
(Reading database ... 450450 files and directories currently installed.)
Preparing to unpack .../unbound_1.9.0-1_amd64.deb ...
Unpacking unbound (1.9.0-1) ...
Setting up unbound (1.9.0-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/unbound.service → 
/lib/systemd/system/unbound.service.
Created symlink 
/etc/systemd/system/unbound.service.wants/unbound-resolvconf.service → 
/lib/systemd/system/unbound-resolvconf.service.
Job for unbound.service failed because the control process exited with error 
code.
See "systemctl status unbound.service" and "journalctl -xe" for details.
insserv: There is a loop between service sendsigs and racoon if stopped
insserv:  loop involving service racoon at depth 3
insserv:  loop involving service sendsigs at depth 2
insserv:  loop involving service bluetooth at depth 1
insserv:  loop involving service rsyslog at depth 4
insserv:  loop involving service avahi at depth 2
Job for unbound.service failed because the control process exited with error 
code.
See "systemctl status unbound.service" and "journalctl -xe" for details.
invoke-rc.d: initscript unbound, action "start" failed.
● unbound.service - Unbound DNS server
   Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: 
enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 2019-02-06 
11:01:07 EST; 7ms ago
 Docs: man:unbound(8)
  Process: 28299 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup 
(code=exited, status=0/SUCCESS)
  Process: 28333 ExecStartPre=/usr/lib/unbound/package-helper 
root_trust_anchor_update (code=exited, status=0/SUCCESS)
  Process: 28374 ExecStart=/usr/sbin/unbound -d $DAEMON_OPTS (code=exited, 
status=1/FAILURE)
 Main PID: 28374 (code=exited, status=1/FAILURE)

Feb 06 11:01:07 zeta systemd[1]: Failed to start Unbound DNS server.
Feb 06 11:01:07 zeta unbound[28374]: [28374:0] fatal error: failed to setup 
modules
Processing triggers for systemd (240-5) ...
Processing triggers for man-db (2.8.5-1) ...
--


--
rak@zeta:~$ systemctl status unbound.service
● unbound.service - Unbound DNS server
   Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Wed 2019-02-06 11:01:12 EST; 3min 
43s ago
 Docs: 

Bug#911515: dvtm in backports

[Sven Joachim]

On 2019-01-17 21:28 +, Dmitry Bogatov wrote:

> Hello?

Hello.

Apologies for not replying sooner.  Your mail from October[1] never
reached me, and during the past three weeks I have been rather ill.

> Dear maintainer of ncurses, could you please upload a backport of
> ncurses-term?

I am afraid this will be difficult.  For starters, ncurses 6.1 has
introduced a new terminfo format, and several important libraries in
stretch such as libslang2 are not compatible with it.  So it is not
advisable to just rebuild the buster ncurses package on stretch.

It would be possible to build the terminfo database in the old format,
but that requires a few non-trivial packaging changes, and I would not
be comfortable to upload such a package to backports when these changes
had never been tested in unstable.

Maybe you could re-add the missing terminfo files in the dvtm backport?
In that case, they should be installed under /lib/terminfo rather than
under /usr/share/terminfo to avoid clashes with the files in
ncurses-term.

Cheers,
   Sven


1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911515#10

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

[Debian Bug Tracking System]

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

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.)


-- 
907718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dateutil, python-vobject
Control: found -1 python-dateutil/2.7.3-1
Control: found -1 python-vobject/0.9.5-2
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of python-dateutil the autopkgtest of
python-vobject started to fail in testing. I copied some of the output
below.

Currently this regression is contributing to the delay of the migration
of python-dateutil to testing [1]. Due to the nature of this issue, I
filed it against both packages. Could you please investigate the
situation and reassign the bug to the right package? If needed, please
change the bug's severity as appropriate.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=python-dateutil

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-vobject/911079/log.gz


autopkgtest [04:58:43]: test command2: cd debian/tests && ./test.sh 3
autopkgtest [04:58:43]: test command2: [---
.{name} {levelname} {message}
sE
==
ERROR: test_recurrence (__main__.TestIcalendar)
--
Traceback (most recent call last):
  File "./tests.py", line 754, in test_recurrence
dates = list(cal.vevent.getrruleset())
  File "/usr/lib/python3/dist-packages/vobject/icalendar.py", line 453,
in getrruleset
ignoretz=isinstance(dtstart, datetime.date))
  File "/usr/lib/python3/dist-packages/dateutil/rrule.py", line 1667, in
__call__
return self._parse_rfc(s, **kwargs)
  File "/usr/lib/python3/dist-packages/dateutil/rrule.py", line 1550, in
_parse_rfc
tzinfos=tzinfos)
  File "/usr/lib/python3/dist-packages/dateutil/rrule.py", line 1509, in
_parse_rfc_rrule
return rrule(dtstart=dtstart, cache=cache, **rrkwargs)
  File "/usr/lib/python3/dist-packages/dateutil/rrule.py", line 464, in
__init__
'RRULE UNTIL values must be specified in UTC when DTSTART '
ValueError: RRULE UNTIL values must be specified in UTC when DTSTART is
timezone-aware

--
Ran 39 tests in 0.229s

FAILED (errors=1, skipped=1)
autopkgtest [04:58:44]: test command2: ---]




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-dateutil
Source-Version: 2.7.3-3

We believe that the bug you reported is fixed in the latest version of
python-dateutil, 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 907...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated python-dateutil 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: Wed, 06 Feb 2019 14:35:10 +0100
Source: python-dateutil
Binary: python-dateutil python3-dateutil
Architecture: source
Version: 2.7.3-3
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Description:
 python-dateutil - powerful extensions to the standard Python datetime module
 python3-dateutil - powerful extensions to the standard Python 3 datetime module
Closes: 907718
Changes:
 python-dateutil (2.7.3-3) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * Add necessary breaks.
 Add breaks against reverse-dependencies that can't cope with the new
 upstream version. (Closes: #907718)
Checksums-Sha1:
 62fbc85a37e3fa501d4e13daf8f3e539f4306c6c 2485 

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has been dealt 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.)


-- 
918378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-guest-agent
Version: 1:3.1+dfsg-2
Severity: important

The systemd unit uses the wrong path to the binary (bin instead of sbin)
and fails to start.

Jan  4 18:29:33 opsvm systemd[607]: qemu-guest-agent.service: Executable 
/usr/bin/qemu-ga missing, skipping: No such file or directory

# dpkg -L qemu-guest-agent | grep qemu-ga
/usr/sbin/qemu-ga
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:3.1+dfsg-3

We believe that the bug you reported is fixed in the latest version of
qemu, 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 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated qemu 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: Wed, 06 Feb 2019 12:23:01 +0300
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-data qemu-system-common 
qemu-system-gui qemu-system-misc qemu-system-arm qemu-system-mips 
qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static 
qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm
Architecture: source
Version: 1:3.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Description:
 qemu   - fast processor emulator, dummy package
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-data - QEMU full system emulation (data files)
 qemu-system-gui - QEMU full system emulation binaries (user interface and 
audio sup
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscellaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 881527 889885 892945 901407 913103 916279 916442 918378 919668 920032 
920222 921525
Changes:
 qemu (1:3.1+dfsg-3) unstable; urgency=medium
 .
   [ Michael Tokarev ]
   * mention #696289 closed by 2.10
   * move ovmf to recommends on debian and update aarch ovmf refs
 (Closes: #889885)
   * remove /dev/kvm permission handling (moved to systemd 239-6)
 (Closes: #892945)
   * build qemu-palcode using alpha cross-compiler
 (Closes: #913103)
   * fix path in qemu-guest-agent.service (#918378), fixs Bind[s]To
 (Closes: #918378
   * use int for sparc64 timeval.tv_usec
 (Closes: #920032)
   * build-depend on libglusterfs-dev not glusterfs-common
 (Closes: #919668, #881527)
   * add breaks: qemu-system-data to qemu-system-common,
 to close #916279 completely (all this can be removed after buster)
 (Closes: #916279)
   * scsi-generic-avoid-possible-oob-access-to-r-buf-CVE-2019-6501.patch
 (Closes: #920222, CVE-2019-6501)
   * slirp-check-data-length-while-emulating-ident-function-CVE-2019-6778.patch
 (Closes: #921525)
   * pvrdma-release-device-resources-on-error-CVE-2018-20123.patch
 (Closes: #916442, CVE-2018-20123)
   * enable rdma and pvrdma, build-depend on
 librdmacm-dev, libibverbs-dev, libibumad-dev
   * sync debian/qemu-user-static.1 and debian/qemu-user.1 generate the latter
 from the former (finally Closes: 

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

[Antoine Beaupré]

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

That's actually inaccurate: the package was refused because the
dependencies specified in `built-using` were missing and indeed, one of
the dependencies hadn't passed NEW when dmarc-cat was uploaded. For
example, here's the last REJECTION I had:

An exception was raised while processing the package:
Traceback (most recent call last):
  File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 109, in 
wrapper
function(upload, srcqueue, comments, transaction)
  File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 222, in 
comment_accept
extra_archives=[upload.target_suite.archive],
  File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 451, in 
copy_binary
self._ensure_extra_source_exists(filename, db_source, archive, 
extra_archives=extra_archives)
  File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 245, in 
_ensure_extra_source_exists
raise ArchiveException('{0}: Built-Using refers to package {1} (= {2}) not 
in target archive {3}.'.format(filename, source.source, source.version, 
archive.archive_name))
ArchiveException: d/dmarc-cat/dmarc-cat_0.9.1-1_amd64.deb: Built-Using refers 
to package golang-github-ivpusic-grpool (= 1.0.0-1) not in target archive 
ftp-master.

When grpool was ACCEPTED, dmarc-cat also was ACCEPTED by the
FTP-masters. So this is not a blocker for the FTP masters.

> Extract from #debian-ftp:
>
> 16:55:59  Built-Using is only meant to be used when the result is 
> GPL/MPL/similar and you've statically linked (/bundled) another source package
> 16:56:33  okay, so to comply with licensing issues?
> 16:56:47  it also seems useful to track rdeps for golang as well, no?
> 16:57:03  no, built-using is _not_ for tracking dependencies
> 16:57:10  it is for license compliance
> 16:57:26  and bsd licensed software does not require that
>
> So in the case of dmarc-cat, dependencides like
> golang-github-stretchr-testify-dev should actually not be listed in
> the Built-Using field.

It's true, however, that the Debian policy specifies built-using is for
copyright reasons.

https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using

Specifically, the last pargraph reads:

> This field should not be added solely for purposes other than
> satisfying license or DFSG requirements to provide full source
> code. In particular, it should not be added solely to enable finding
> packages that should be rebuilt against newer versions of their build
> dependencies.

Yet, from what I understand, that is *exactly* how that field is used in
the golang team. Is that correct?

It should be noted this is a SHOULD NOT and not a MUST NOT, so it's a
little more relaxed - may we are allowed to abuse it like this.

I do wonder if it's deliberate, however. It seems to me this should be
clarified, both in dh-golang and in policy, either way.

A.

-- 
Perl is "some assembly required". Python is "batteries included". PHP
is "kitchen sink, but it’s from Canada and both faucets are labeled C".
 - Alex Munroe, PHP: a fractal of bad design

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

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #921495 [libbio-perl-perl] libbio-perl-perl: Package not upgradable, file 
conflicts.
Severity set to 'serious' from 'normal'

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

Processed: severity of 899304 is important

[Debian Bug Tracking System]

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

> severity 899304 important
Bug #899304 [bareos-storage] bareos-storage will not start after upgrade to 
16.2.6-4
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

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

[Matthias Andree]

Control: tags -1 confirmed upstream fixed-upstream -moreinfo -unreproducible


This got fixed in upstream Git as of commit
8c57ec38ae327fcd648569acc915f47f0eb2547d - please cherry-pick this.

https://gitlab.com/fetchmail/fetchmail/commit/8c57ec38ae327fcd648569acc915f47f0eb2547d

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

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#914537: openmw: segfault at start

[Markus Koschany]

Hi Bret,

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

Thanks for the update.


> Might I ask you for a small favour, WIldMIDI is ready to be
> reviewed/uploaded as well. The latest release contains several CVE fixes.
> https://salsa.debian.org/psi29a-guest/WildMIDI
> 
> It sits in my private repo at the moment, could someone move this to
> somewhere more appropriate? games-team maybe? It was originally in
> collab-main on Alioth.

I moved wildmidi to the games-team. Both packages looked good to me. You
didn't push the pristine-tar commit for openmw, so the resulting
.orig-tarball may be out-of-sync.

Cheers,

Markus



signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Your message dated Wed, 06 Feb 2019 13:08:31 +
with message-id 
and subject line Bug#914537: fixed in openmw 0.45.0-1
has caused the Debian Bug report #914537,
regarding openmw: segfault at start
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is 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.)


-- 
914537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openmw
Version: 0.44.0-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The latest build of this package (0.44.0-1+b1) makes the game crash at start on
my system (please see provided crash.log)




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

Kernel: Linux 4.18.0-2-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)
LSM: AppArmor: enabled

Versions of packages openmw depends on:
ii  libavcodec587:4.0.3-1
ii  libavformat58   7:4.0.3-1
ii  libavutil56 7:4.0.3-1
ii  libboost-filesystem1.67.0   1.67.0-10
ii  libboost-program-options1.67.0  1.67.0-10
ii  libboost-system1.67.0   1.67.0-10
ii  libbullet2.87   2.87+dfsg-3
ii  libc6   2.27-8
ii  libgcc1 1:8.2.0-9
ii  libgl1  1.1.0-1
ii  libmyguiengine3debian1v53.2.2+dfsg-2+b1
ii  libopenal1  1:1.19.1-1
ii  libopenscenegraph-3.4-131   3.4.1+dfsg1-4
ii  libopenthreads203.2.3+dfsg1-2+b9
ii  libqt5core5a5.11.2+dfsg-4
ii  libqt5gui5  5.11.2+dfsg-4
ii  libqt5widgets5  5.11.2+dfsg-4
ii  libsdl2-2.0-0   2.0.8+dfsg1-6
ii  libstdc++6  8.2.0-9
ii  libswresample3  7:4.0.3-1
ii  libswscale5 7:4.0.3-1
ii  libtinyxml2.6.2v5   2.6.2-4
ii  openmw-data 0.44.0-1

Versions of packages openmw recommends:
ii  openmw-launcher  0.44.0-1+b1

openmw suggests no packages.

-- no debconf information
*** Fatal Error ***
Segmentation fault (signal 11)
Address: (nil)

System: Linux debiananas 4.18.0-2-amd64 #1 SMP Debian 4.18.10-2 (2018-11-02) 
x86_64

Executing: gdb --quiet --batch --command=/tmp/gdb-respfile-i5hVPW
[New LWP 2002]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f31a65e424a in __waitpid (pid=2004, stat_loc=0x560a480fc78c, options=0) 
at ../sysdeps/unix/sysv/linux/waitpid.c:30

* Loaded Libraries
>FromTo  Syms Read   Shared Object Library
0x7f31a8bad3b0  0x7f31a8d2cfac  Yes (*) 
/usr/lib/x86_64-linux-gnu/libosg.so.131
0x7f31a8ac6460  0x7f31a8ac77f8  Yes (*) 
/usr/lib/x86_64-linux-gnu/libOpenThreads.so.20
0x7f31a8a850f0  0x7f31a8ab148f  Yes (*) 
/usr/lib/x86_64-linux-gnu/libosgParticle.so.131
0x7f31a890ae70  0x7f31a8a0d468  Yes (*) 
/usr/lib/x86_64-linux-gnu/libosgUtil.so.131
0x7f31a878bb60  0x7f31a882768b  Yes (*) 
/usr/lib/x86_64-linux-gnu/libosgDB.so.131
0x7f31a8673cd0  0x7f31a86e9f22  Yes (*) 
/usr/lib/x86_64-linux-gnu/libosgViewer.so.131
0x7f31a85b81b0  0x7f31a85eb6d2  Yes (*) 
/usr/lib/x86_64-linux-gnu/libosgGA.so.131
0x7f31a8562130  0x7f31a8563259  Yes (*) 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.67.0
0x7f31a854a8f0  0x7f31a855860b  Yes (*) 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.67.0
0x7f31a84e5360  0x7f31a852b045  Yes (*) 
/usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.67.0
0x7f31a83de870  0x7f31a842b161  Yes (*) 
/usr/lib/x86_64-linux-gnu/libopenal.so.1
0x7f31a6f486b0  0x7f31a788e2d2  Yes (*) 
/usr/lib/x86_64-linux-gnu/libavcodec.so.58
0x7f31a6cbb220  0x7f31a6e3d9ee  Yes (*) 
/usr/lib/x86_64-linux-gnu/libavformat.so.58
0x7f31a6c126e0  0x7f31a6c514e0  Yes (*) 
/usr/lib/x86_64-linux-gnu/libavutil.so.56
0x7f31a6b73220  0x7f31a6be8ddc  Yes (*) 
/usr/lib/x86_64-linux-gnu/libswscale.so.5
0x7f31a6b532b0  0x7f31a6b679cc  Yes (*) 
/usr/lib/x86_64-linux-gnu/libswresample.so.3
0x7f31a69ac2c0  0x7f31a6af1e41  Yes (*) 
/usr/lib/libMyGUIEngine.so.3debian1
0x7f31a6829ae0  0x7f31a68ecf3d  Yes (*) 

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

[Charlemagne Lasse]

Package: chromium
Version: 71.0.3578.80-1~deb9u1
Severity: serious

The stable-sec package is stuck with version 71.0.3578.80 and is
missing security updates for several CVEs.  Take for example the list
from 72.0.3626.81

- Stack buffer overflow in Skia. Reported by Ivan Fratric
- Use after free in Mojo, FileAPI, and Payments. Reported by Mark Brand
- CVE-2018-17481: Use after free in PDFium. Reported by Anonymous
- CVE-2019-5754: Inappropriate implementation in QUIC Networking. Reported
  by Klzgrad
- CVE-2019-5755: Inappropriate implementation in V8. Reported by Jay
  Bosamiya
- CVE-2019-5756: Use after free in PDFium. Reported by Anonymous
- CVE-2019-5757: Type Confusion in SVG. Reported by Alexandru Pitis
- CVE-2019-5758: Use after free in Blink. Reported by Zhe Jin
- CVE-2019-5759: Use after free in HTML select elements. Reported by Almog
  Benin
- CVE-2019-5760: Use after free in WebRTC. Reported by Zhe Jin
- CVE-2019-5762: Use after free in PDFium. Reported by Anonymous
- CVE-2019-5763: Insufficient validation of untrusted input in V8.
  Reported by Guang Gong
- CVE-2019-5764: Use after free in WebRTC. Reported by Eyal Itkin
- CVE-2019-5765: Insufficient policy enforcement in the browser. Reported
  by Sergey Toshin
- CVE-2019-5766: Insufficient policy enforcement in Canvas. Reported by
  David Erceg
- CVE-2019-5767: Incorrect security UI in WebAPKs. Reported by Haoran Lu,
  Yifan Zhang, Luyi Xing, and Xiaojing Liao
- CVE-2019-5768: Insufficient policy enforcement in DevTools. Reported by
  Rob Wu
- CVE-2019-5769: Insufficient validation of untrusted input in Blink.
  Reported by Guy Eshel
- CVE-2019-5770: Heap buffer overflow in WebGL. Reported by hemidallt
- CVE-2019-5772: Use after free in PDFium. Reported by Zhen Zhou
- CVE-2019-5773: Insufficient data validation in IndexedDB. Reported by
  Yongke Wang
- CVE-2019-5774: Insufficient validation of untrusted input in
  SafeBrowsing. Reported by Junghwan Kang and Juno Im
- CVE-2019-5775: Insufficient policy enforcement in Omnibox. Reported by
  evi1m0
- CVE-2019-5776: Insufficient policy enforcement in Omnibox. Reported by
  Lnyas Zhang
- CVE-2019-5777: Insufficient policy enforcement in Omnibox. Reported by
  Khalil Zhani
- CVE-2019-5778: Insufficient policy enforcement in Extensions. Reported
  by David Erceg
- CVE-2019-5779: Insufficient policy enforcement in ServiceWorker.
  Reported by David Erceg
- CVE-2019-5780: Insufficient policy enforcement. Reported by Andreas
  Hegenberg
- CVE-2019-5781: Insufficient policy enforcement in Omnibox. Reported by
  evi1m0
- CVE-2019-5782: Inappropriate implementation in V8 reported by Qixun Zhao
- CVE-2019-5783: Insufficient validation of untrusted input in DevTools.
  Reported by Shintaro Kobori

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

[Debian Bug Tracking System]

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


-- 
915657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: google-android-installers
Version: 1472023576+nmu1
Severity: serious

Your upload included the binary package google-android-platform-21-installer,
version 21+r02, for all, however stable already has version 21+r02.
--- End Message ---
--- Begin Message ---
Source: google-android-installers
Source-Version: 1472023576+nmu3

We believe that the bug you reported is fixed in the latest version of
google-android-installers, 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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Helge Kreutzmann  (supplier of updated 
google-android-installers 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: Tue, 05 Feb 2019 19:02:29 +0100
Source: google-android-installers
Architecture: source
Version: 1472023576+nmu3
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Helge Kreutzmann 
Closes: 915657
Changes:
 google-android-installers (1472023576+nmu3) unstable; urgency=medium
 .
   * Really increment *all* version numbers. Closes: #915657.
Checksums-Sha1:
 d9f449b3fff9cc66f7bceb2bd347a66d5d3deff6 5165 
google-android-installers_1472023576+nmu3.dsc
 7c15fa9d5454a3632e525f3fec66cda709fc38ff 17012 
google-android-installers_1472023576+nmu3.tar.xz
 bdf4dcef55e1db5959c48654b18b53dea413d416 16680 
google-android-installers_1472023576+nmu3_amd64.buildinfo
Checksums-Sha256:
 719cc2768d2b96d3203dba0f23d8d9bddee90c8ba6f57c2facafacd96a7c5285 5165 
google-android-installers_1472023576+nmu3.dsc
 71bf3ab5fc8575f769d2c9e5e25075ef510dd966e4ff10b764a9ad69cb3677f7 17012 
google-android-installers_1472023576+nmu3.tar.xz
 16cc3825a69424d975bfaa23d3a3ac2402f1478c33e7b3b76e37b9ac77dc89ff 16680 
google-android-installers_1472023576+nmu3_amd64.buildinfo
Files:
 804f6becc933950a63aeb7fc05d23529 5165 contrib/devel optional 
google-android-installers_1472023576+nmu3.dsc
 3b07078314292078abc65aaaf79335a9 17012 contrib/devel optional 
google-android-installers_1472023576+nmu3.tar.xz
 052fdc0788c8ce8c851c4958a6529bf3 16680 contrib/devel optional 
google-android-installers_1472023576+nmu3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlxa1GsACgkQEwLx8Dbr
6xkGLA/9FwyY8ogcbZUQlNkBba5L4vM+8Jg81SLJULuimF5z+N1vCo1sN8FDqIyd
spQCfL2TKQmCvzlTewLSS+x+xEIMk4FVJwG8BgNWvRZin2N9dQbJNtC9wUIubIK7
8ZAeTaxRK0Yu6/y2E60/UMZVAKhAZfDhkfOk3EJjrx8QFwaUH9BHPNx+HXX/3DsN
Rl4EuAnG0jbOBOWsBx7vWXBAeINLvYI+Y3xDYZHieJ5IRfHv3vzvelbmPUwaIsnp
zPoDj/h0NmvbU5755RqXqg/7IwtctxDxoLquy8JqetL7EyD5GjRJDdjIOOyV9bfe
8z2iozjCrv3z5ucbBiGQnD82dl7FPQstOaSy+l+/wgNv65u3VkxLOqpXz7NCY2Wi
5zvf8MOm5/SH2vBuwZZNsCew2/uIda7J5NRHQY2AgtjWYObYPalxaP84F0+0MfBt
BWQx9M75aDbLIgxf6YSpBy6g8ViQqhcMKVjViVm8YVnNOn3JOBHz90efd9hSPClB
JAKvbiIjC4TBp9B9+I5nwtFOuWox0lsqj870fp/cWLujmVQ0gp8M4jiXvzgzPcuF
Txni8r9kz1AmrGQGkca/DUv2rtnMS1ZV9my3n98Y9CiHCkTM/arPJWfqXL/Kstfw
7zjV4YtcCdkHXa4hOPz6hS2up6HGlp+lPrlFYWYObKBt11lD07A=
=7u5r
-END PGP SIGNATURE End Message ---