Bug#921450: (no subject)

[GCS]

Hi Lev and Matthias,

On Wed, Feb 6, 2019 at 8:00 AM Lev Lamberov  wrote:
> I have the same problem, I run testing + some bits from unstable on this 
> machine.
> $ env LC_ALL=C fetchmail -v -v -v  --nodetach --nosyslog -b 2
[...]
> fetchmail: POP3> DELE 1
> fetchmail: POP3< +OK Marked to be deleted.
> Segmentation fault
 It seems the POP3 deletion is the problem or related to it somehow.
Others also experienced that the mail is fetched and delivered locally
but not deleted from the POP3 server (on the next fetchmail run the
same mail fetched again) despite the 'DELE' command is received but
was not acted upon.

> I've tried to downgrade to fetchmail 6.4.0~beta4-1 (from
> snapshot.debian.org), tried to upgrade to glibc 2.28-6, tried to reboot
> with another version of Linux kernel, and the problem is still there.
 Do you mean 6.4.0~beta4-1 worked right previously?

Thanks,
Laszlo/GCS

Bug#921430: closed by Andreas Beckmann (Re: libssl1.0.2-dbgsym: Cannot install libssl1.0.2-dbgsym since packet is outdated)

[Alexander Lochmann]

Thank you for the advice!
That works.

- Alex

On 05.02.19 23:45, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libssl1.0.2-dbgsym package:
> 
> #921430: libssl1.0.2-dbgsym: Cannot install libssl1.0.2-dbgsym since packet 
> is outdated
> 
> It has been closed by Andreas Beckmann .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Andreas Beckmann 
>  by
> replying to this email.
> 
> 

-- 
Technische Universität Dortmund
Alexander LochmannPGP key: 0xBC3EF6FD
Otto-Hahn-Str. 16 phone:  +49.231.7556141
D-44227 Dortmund  fax:+49.231.7556116
http://ess.cs.tu-dortmund.de/Staff/al



signature.asc
Description: OpenPGP digital signature

Bug#921432: closed by Andreas Beckmann (Re: libssl1.0.2-dbgsym: Cannot install libssl1.0.2-dbgsym since packet is outdated)

[Alexander Lochmann]

Thank you for the advice!
That works.

- Alex

On 05.02.19 23:45, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libssl1.1-dbgsym package:
> 
> #921432: libssl1.1-dbgsym: Cannot install libssl1.1-dbgsym since packet is 
> outdated
> 
> It has been closed by Andreas Beckmann .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Andreas Beckmann 
>  by
> replying to this email.
> 
> 

-- 
Technische Universität Dortmund
Alexander LochmannPGP key: 0xBC3EF6FD
Otto-Hahn-Str. 16 phone:  +49.231.7556141
D-44227 Dortmund  fax:+49.231.7556116
http://ess.cs.tu-dortmund.de/Staff/al



signature.asc
Description: OpenPGP digital signature

Bug#921450: (no subject)

[Lev Lamberov]

Hi,

I have the same problem, I run testing + some bits from unstable on this 
machine.

$ env LC_ALL=C fetchmail -v -v -v  --nodetach --nosyslog -b 2
Old UID list from mail.riseup.net:
 

Scratch list of UIDs:
 

fetchmail: removing stale lockfile
fetchmail: 6.4.0.beta4 querying mail.riseup.net (protocol POP3) at Wed Feb  6 
11:42:01 2019: poll started
Trying to connect to 198.252.153.22/110...connected.
fetchmail: POP3< +OK howdy, ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< AUTH-RESP-CODE
fetchmail: POP3< STLS
fetchmail: POP3< SASL
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< +OK Begin TLS negotiation now.
fetchmail: Certificate chain, from root to peer, starting at depth 2:
fetchmail: Issuer Organization: COMODO CA Limited
fetchmail: Issuer CommonName: COMODO RSA Certification Authority
fetchmail: Subject CommonName: COMODO RSA Certification Authority
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: COMODO CA Limited
fetchmail: Issuer CommonName: COMODO RSA Certification Authority
fetchmail: Subject CommonName: COMODO RSA Domain Validation Secure Server CA
fetchmail: Server certificate:
fetchmail: Issuer Organization: COMODO CA Limited
fetchmail: Issuer CommonName: COMODO RSA Domain Validation Secure Server CA
fetchmail: Subject CommonName: *.riseup.net
fetchmail: Subject Alternative Name: *.riseup.net
fetchmail: Subject Alternative Name: riseup.net
fetchmail: mail.riseup.net key fingerprint: 
A6:13:14:09:4D:61:97:D9:D0:A1:E1:C7:2D:F4:4E:6E
fetchmail: SSL/TLS: using protocol TLSv1.2, cipher ECDHE-RSA-AES128-GCM-SHA256, 
128/128 secret/processed bits
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< AUTH-RESP-CODE
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN LOGIN
fetchmail: POP3< .
fetchmail: mail.riseup.net: upgrade to TLS succeeded.
fetchmail: POP3> USER dogsleg
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 29 272396
29 messages for dogsleg at mail.riseup.net (272396 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 6319
fetchmail: POP3> RETR 1
fetchmail: POP3< +OK 6319 octets
reading message dogs...@mail.riseup.net:1 of 29 (6319 octets) About to rewrite 
Return-Path: ...
...rewritten version is Return-Path: 
.
About to rewrite From: Paul Wise ...
...rewritten version is From: Paul Wise .
About to rewrite To: debian-de...@lists.debian.org...
...rewritten version is To: debian-de...@lists.debian.org.
About to rewrite Resent-From: debian-de...@lists.debian.org...
...rewritten version is Resent-From: debian-de...@lists.debian.org.
About to rewrite Resent-Sender: debian-devel-requ...@lists.debian.org...
...rewritten version is Resent-Sender: debian-devel-requ...@lists.debian.org.

Trying to connect to ::1/25...connection failed.
fetchmail: connection to localhost:smtp [::1/25] failed: Connection refused.
Trying to connect to 127.0.0.1/25...connected.
fetchmail: SMTP< 220 urfu-thinkpad ESMTP Exim 4.92-RC5 Wed, 06 Feb 2019 
11:42:05 +0500
fetchmail: SMTP> EHLO mail.riseup.net
fetchmail: SMTP< 250-urfu-thinkpad Hello mail.riseup.net [127.0.0.1]
fetchmail: SMTP< 250-SIZE 52428800
fetchmail: SMTP< 250-8BITMIME
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250-CHUNKING
fetchmail: SMTP< 250-PRDR
fetchmail: SMTP< 250 HELP
fetchmail: forwarding to localhost
fetchmail: SMTP> MAIL 
FROM: BODY=8BITMIME 
SIZE=6319
fetchmail: SMTP< 250 OK
fetchmail: SMTP> RCPT TO:
fetchmail: SMTP< 250 Accepted
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself
#**
fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 OK id=1grGuL-0002s8-Oa
 flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< +OK Marked to be deleted.
Segmentation fault

I've tried to downgrade to fetchmail 6.4.0~beta4-1 (from
snapshot.debian.org), tried to upgrade to glibc 2.28-6, tried to reboot
with another version of Linux kernel, and the problem is still there.

Since the problem is a recent one, I've tried to investigate, which
packages were upgraded on my machine recently:

$ which-pkg-broke fetchmail
perl-base  Tue Feb  5 11:20:26 2019
libdb5.3:amd64 Wed Feb  6 11:02:03 2019
libc6:amd64Wed Feb  6 11:20:43 2019
fetchmail  Wed Feb  6 11:41:49 2019

Changes in libc6 reflect my attempts to upgrade to glibc 2.28-6 and
changes in fetchmail reflect my attempts to downgrade (which I mentioned
before).

With regards,
Lev Lamberov

Bug#921488: [debian-mysql] Bug#921488: libmariadb3: OpenSSL license contamination of GPL reverse-dependencies

[Steve Langasek]

On Wed, Feb 06, 2019 at 07:21:46AM +0200, Otto Kekäläinen wrote:
> The OpenSSL licence will change from 3.0.0 onwards
> (https://www.openssl.org/source/license.html) but you are right that
> for version 1.1.1 the SSLeay clause applies. MySQL and MariaDB has the
> OpenSSL exception, and YaSSL has been used due to earlier
> interpretation by non-maintainers that it might be needed, but
> currently I think using OpenSSL is the right thing to use, just like
> upstream MariaDB uses as well.

How does your statement that you think it is "the right thing to use" help
the maintainers of the various packages in the archive that are not
violating the GPL?  What action do you expect them to take for the buster
release?

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


signature.asc
Description: PGP signature

Processed: fixed 887733 in 1.6.0-3+deb9u2

[Debian Bug Tracking System]

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

> fixed 887733 1.6.0-3+deb9u2
Bug #887733 [src:unbound] unbound: CVE-2017-15105: vulnerability in the 
processing of wildcard synthesized NSEC records
Marked as fixed in versions unbound/1.6.0-3+deb9u2.
> thanks
Stopping processing here.

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

Bug#921488: [debian-mysql] Bug#921488: libmariadb3: OpenSSL license contamination of GPL reverse-dependencies

[Otto Kekäläinen]

Hello!

The OpenSSL licence will change from 3.0.0 onwards
(https://www.openssl.org/source/license.html) but you are right that
for version 1.1.1 the SSLeay clause applies. MySQL and MariaDB has the
OpenSSL exception, and YaSSL has been used due to earlier
interpretation by non-maintainers that it might be needed, but
currently I think using OpenSSL is the right thing to use, just like
upstream MariaDB uses as well.

Bug#919555: Bug#919766: FTBFS-es

[Balint Reczey]

Hi Barak,

On Thu, Jan 31, 2019 at 2:54 AM Barak A. Pearlmutter
 wrote:
>
> Thanks, that was very kind of you. Much appreciated. I'm in the
> process of preparing to upload.
> But next time feel free to just NMU, 0 day, tell me after, I totally don't 
> mind!
> (This goes for any of my packages.)

Thanks!

I see you have already closed the changelog in git just did not
upload. If you hold back the upload because of the current doxygen
breakage [1], then please just do a source-only upload and let it be
built when the broken build-dependencies are fixed.

[1] https://lists.debian.org/debian-science/2019/02/msg6.html

Cheers,
Balint

>
> Cheers,
>
> --Barak.



-- 
Balint Reczey
Ubuntu & Debian Developer

Bug#921423: /var/log/letsencrypt gets wiped on transitional package purge

[Harlan Lieberman-Berg]

On Tue, Feb 5, 2019 at 10:57 PM Mattia Rizzolo  wrote:
> Sure, of course that's the cause, but your suggested fix would instead
> introduce the other bug that "purge does not delete related logs", which
> is what everybody is expecting "purge" to do.

Hi Mattia,

The bug here is that the transitional dummy package purges the
directory that the main package which provides it uses.  Both certbot
and letsencrypt use `/var/log/letsencrypt` for their log storage, but
the letsencrypt package has been hollowed out and made into a dummy.
The directory will still be deleted if you purge certbot, which is the
new and correct owner of that path.

Sincerely,

-- 
Harlan Lieberman-Berg
~hlieberman

Bug#921488: libmariadb3: OpenSSL license contamination of GPL reverse-dependencies

[Steve Langasek]

Package: libmariadb3
Version: 1:10.3.12-2
Severity: serious
Affects: w1retap
Justification: renders many Debian packages undistributable

Hello,

It's come to my attention that in buster and unstable, packages which
build-depend on default-libmysqlclient-dev wind up linked against
libmariadb3, which in turn links against OpenSSL (libssl1.1).

This includes software which is licensed under the GPL and uses the MySQL
APIs.  (Example: w1retap)

It is well understood that the OpenSSL license is not "compatible" with the
GPL (either version 2 or 3); and furthermore, Debian has long taken the
position that, unless a license exception is granted by the copyright
holders, a package which is distributed under the GPL must only link to
libraries whose licenses are also GPL-compatible in order for it to be
included in Debian.

There is bug #787118 requesting that mariadb-server use OpenSSL instead of
YaSSL; this bug is still open in the BTS despite the fact that mariadb does
now link against OpenSSL.  This bug also acknowledges the need for a license
exception for MariaDB itself to ship linked against OpenSSL, but the license
compatibility problem for reverse-dependencies of the client library seems
to have been overlooked.

I cannot find any discussion of the switch from yassl to openssl in the
mariadb-10.3 changelog, so as near as I can see, there has been no explicit
consideration of the licensing implications.

I am opening this as a serious bug, since I believe this makes a large and
indeterminate number of packages non-distributable in buster.

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


signature.asc
Description: PGP signature

Bug#919477: marked as done (acl2 ftbfs on armel, armhf, arm64 and ppc64el)

[Debian Bug Tracking System]

Your message dated Wed, 06 Feb 2019 04:07:56 +
with message-id 
and subject line Bug#919477: fixed in gcl 2.6.12-83
has caused the Debian Bug report #919477,
regarding acl2 ftbfs on armel, armhf, arm64 and ppc64el
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.)


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

acl2 ftbfs on armel, armhf, arm64 and ppc64el.

https://buildd.debian.org/status/fetch.php?pkg=acl2=armel=8.0dfsg-1=1515868416=0

and checked that it ftbfs on plummer (ppc64el).
--- End Message ---
--- Begin Message ---
Source: gcl
Source-Version: 2.6.12-83

We believe that the bug you reported is fixed in the latest version of
gcl, 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.
Camm Maguire  (supplier of updated gcl 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 21:54:42 +
Source: gcl
Binary: gcl gcl-dbgsym gcl-doc
Architecture: source amd64 all
Version: 2.6.12-83
Distribution: unstable
Urgency: high
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Description:
 gcl- GNU Common Lisp compiler
 gcl-doc- Documentation for GNU Common Lisp
Closes: 919477
Changes:
 gcl (2.6.12-83) unstable; urgency=high
 .
   * Version_2_6_13pre79
   * Fix acl2 arm builds (Closes: #919477).
Checksums-Sha1:
 dbdacd75798bcc0369c3138133df1487e510ead0 1832 gcl_2.6.12-83.dsc
 eb2fa6557822e35c888c921022b6a8dcfb76a9a5 416484 gcl_2.6.12-83.debian.tar.xz
 d5a3e52dbc5aee228bf04556f5c3cce572867f60 18096464 
gcl-dbgsym_2.6.12-83_amd64.deb
 a531bc917d22827af7c1753f61964cc8c44a0dfa 1129712 gcl-doc_2.6.12-83_all.deb
 efe2a3ab2cff554fe38d45e6218f50cf6794369a 7580 gcl_2.6.12-83_amd64.buildinfo
 ce89faa26411ccb669c46edf4c1e4eae272f3642 30384172 gcl_2.6.12-83_amd64.deb
Checksums-Sha256:
 deb04f925297de0ee81d3281a779eb66077ab95a6e951eb10c214ad31531396f 1832 
gcl_2.6.12-83.dsc
 6474ff06cb7e467afbd36ea243f74b75ac7fe0b68fe167ab5fd5f62a4e8667a3 416484 
gcl_2.6.12-83.debian.tar.xz
 c0bcb790b0c2dcf2a8973199eeea305f4d9b02e01f762837702e20b16f1ba9ad 18096464 
gcl-dbgsym_2.6.12-83_amd64.deb
 63df6b4cf8e1242d5d2152209a58487e85fd1b1568f147591f395357215d03d8 1129712 
gcl-doc_2.6.12-83_all.deb
 d2d3d5246e1212219259d71d0eaea83cddeeef0160d5b46d88c066fe3762622b 7580 
gcl_2.6.12-83_amd64.buildinfo
 914e5d9698a9c7a4ce21c1604116a2e4e6c338b59d5f32a6a0fc430184d8155a 30384172 
gcl_2.6.12-83_amd64.deb
Files:
 4a235a1c141c3c2dcf6a3ff3bb12ea9e 1832 lisp optional gcl_2.6.12-83.dsc
 a55bb38b9c7a6b8b428f8324d0c850b3 416484 lisp optional 
gcl_2.6.12-83.debian.tar.xz
 53ccb7c97bd7126b499314ea476225b6 18096464 debug optional 
gcl-dbgsym_2.6.12-83_amd64.deb
 60090d1065f5fe490e98e5ae22696e25 1129712 doc optional gcl-doc_2.6.12-83_all.deb
 4db462d80561d669103da5197fc4712a 7580 lisp optional 
gcl_2.6.12-83_amd64.buildinfo
 46721f69c2c3278ca1d6e410afa69569 30384172 lisp optional gcl_2.6.12-83_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/iFPNjaXdzJC6BbsuEXOUQ+bcU0FAlxaSZoACgkQuEXOUQ+b
cU3hpA/+JwR2rnUn6PvaDp/xvSsBnMw7f/XyA+PuSYTAvzg44jgzke48AYUzO/YM
M0FngvljF0Iy1WepjJXQ2rbvhRoNBDacuYxFCHUsIznZgec5uwtn640Ij8Owhm7k
ASLCRz7+8Ty+rXQfCCEE67Q1Jh8CSP17EgD7IRhMAiTvBvCI4ttRdZP1RH1wjHaK
IRBaRsnUSMyf8G2kjqkNdvwf1XVk/kOfv5BgyK6jj3JdaiFUwGi5U8r0jTMvSdEU
SnlCLz0h9Rr2otbiwrD4tuJZ2WEG88YeP+vufQT1bt8k/XUp2ok4rlOxbRGQPXr4
qyi2q8H4hoscuD6lbap6m6s05JmNfj3vcO+InDANQw7HcsWv5vdHUmQM7YsGLiXv
oEDnRHOADd1GjM6PDorKzGCEr0TFp8asS6OWRQzSvcKzBhTgMPNWZr5tGsGR6ls0
uqyHG8Z8Xyaq3c3Xqn+bPH9d7tfqlYRC3IU/QgJEeqUpKo3rd3VDnnqyahU0Spbs
FOKh+uRWLR5d556uyZTup6jaDaBxaOgHXqHkNLtZd1wb41WImTKoPa/bxhyVAy2t
GtFScjRQO+2s2VuudxVw4H9zbhTPrE+jrHuhWzjq41ZQc3oFFifEEULBQ8nsqHHo
igB1JBSJOsf1SE1XVFkXjl9S1FjQ+Ehoq3UrBDSxXSaa34+fIfo=
=XYub
-END PGP SIGNATURE End Message ---

Bug#921423: /var/log/letsencrypt gets wiped on transitional package purge

[Mattia Rizzolo]

On Tue, Feb 05, 2019 at 10:42:25AM +, Robie Basak wrote:
> Expected: logs still exist back to the beginning, or at least since step
> 4.
> 
> Actual: logs are gone.
> 
> Real use case: users upgrading through the regular upgrade path will,
> upon purging old transitional packages, lose their logs.

Well, purging by definition would go about deleting such things.
At most, you'd be expecting to see the stuff coming from after step 4,
but everything before should be deleted by the definition of "purge".

> Suspected cause: letsencrypt.postrm removes /var/log/letsencrypt.
> 
> Suggested fix: drop the "rm -rf /var/log/letsencrypt" from
> letsencrypt.postrm (which makes the postrm redundant so the entire file
> can be removed).

Sure, of course that's the cause, but your suggested fix would instead
introduce the other bug that "purge does not delete related logs", which
is what everybody is expecting "purge" to do.

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

Bug#921423: marked as done (/var/log/letsencrypt gets wiped on transitional package purge)

[Debian Bug Tracking System]

Your message dated Wed, 06 Feb 2019 03:54:12 +
with message-id 
and subject line Bug#921423: fixed in python-certbot 0.28.0-2
has caused the Debian Bug report #921423,
regarding /var/log/letsencrypt gets wiped on transitional package purge
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.)


-- 
921423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: letsencrypt
Version: 0.28.0-1
Severity: grave
Justification: causes data loss
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco

Steps to reproduce:

1. Start on sid
2. apt install letsencrypt  # using transitional package
3. Use letsencrypt or certbot
4. Later, note the project rename and start using the certbot name
5. Note the package description says that the letsencrypt binary package
can be removed, and purge it.
6. Look for previous logs

Expected: logs still exist back to the beginning, or at least since step
4.

Actual: logs are gone.

Real use case: users upgrading through the regular upgrade path will,
upon purging old transitional packages, lose their logs.

Suspected cause: letsencrypt.postrm removes /var/log/letsencrypt.

Suggested fix: drop the "rm -rf /var/log/letsencrypt" from
letsencrypt.postrm (which makes the postrm redundant so the entire file
can be removed).


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-certbot
Source-Version: 0.28.0-2

We believe that the bug you reported is fixed in the latest version of
python-certbot, 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.
Harlan Lieberman-Berg  (supplier of updated 
python-certbot 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: Tue, 05 Feb 2019 22:15:02 -0500
Source: python-certbot
Architecture: source
Version: 0.28.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Let's Encrypt 
Changed-By: Harlan Lieberman-Berg 
Closes: 921423
Changes:
 python-certbot (0.28.0-2) unstable; urgency=medium
 .
   * Remove unnecessary letsencrypt.postrm (Closes: #921423)
Checksums-Sha1:
 a0a9a8e1cbf0cfe61ab312b64d9d0458a0c4c770 3116 python-certbot_0.28.0-2.dsc
 38956e7e002338ac8786dfc86ec5f3e1a1cd5230 9836 
python-certbot_0.28.0-2.debian.tar.xz
 23a02956240586ac7a8ec5f9015c29c98c6302b7 8778 
python-certbot_0.28.0-2_amd64.buildinfo
Checksums-Sha256:
 fca9ff3735f47742d10f774e9b3c9bacc46f49fdd22ded0bcd081d46484f729f 3116 
python-certbot_0.28.0-2.dsc
 94afbc51400177707086863f43a87ea5073490c3be8a49c5c8e3f3af9b36a1b8 9836 
python-certbot_0.28.0-2.debian.tar.xz
 53b71ab6bcaf3f1625a921caba621909eb41968b398a02622209bb35d186eeb5 8778 
python-certbot_0.28.0-2_amd64.buildinfo
Files:
 54ce54ed5b6ca4eb806335b03afaf2a4 3116 python optional 
python-certbot_0.28.0-2.dsc
 d85ce3dee065f420e1db7d6c48fc60d2 9836 python optional 
python-certbot_0.28.0-2.debian.tar.xz
 2ceeeaa517cb70d6c5bdfe901d6957ad 8778 python optional 
python-certbot_0.28.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKqBAEBCgCUFiEEAUCsXNRiG9DwejN3fudPmcDF31sFAlxaUhxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDAx
NDBBQzVDRDQ2MjFCRDBGMDdBMzM3NzdFRTc0Rjk5QzBDNURGNUIWHGhsaWViZXJt
YW5AZGViaWFuLm9yZwAKCRB+50+ZwMXfW2ZhD/4gQQaQzjIrHmRGPka4hQUbXMla
b/9WtxVcTBlUnwLz+imTKAkHPUjY4RYM2v8aRiFJPNSYCa5aDkgobnuaatZ97pLI
OHLq/eCdH9Jf7dvMCG0I8HAi5LOiQWOKIiXqttXGlfwvIaE+IQ7hWBjkeqNjkx57
6IrUgtpLAI+xg8impmLXvoaKEQnY/g9rRHW7+E4NFAaGJhCbSJyeKxvrwrBPAZie
D0EyPezBN+NvxNdqY8ZgwFuIA++hYvOMl1iDhbVrwSR/dWvzpsyx6Xta3gmTE4Jq
4ktuULYJ8I3ESarcyRyX5XkEKY5jsxXbLUKCGvYk5a5hp+1FZE9+4Tz7lOrg3+ir
giCKR4eLcf33j4dlp5jjao/xAc+jbEiMvz2vGEHaRw/AkAGvRbaVSZcdQMMBOro2
DOBGRiBhpU5SGKnCvNm7Acf/kahTEjTVaQL3OAdmXzUu8mmjiFLmcd2wnI5AuPbj
lAi+DpTWuDDOGkUI5ZE3XqXOM3PK9mSolAukmsU7NePDVE4t+9nw+8XNkYQW13sg
DSnQIGltskb+phH1Qi9BXY9DgZvvp49DppHYrl35tuHbpx6Fm+1GkIuJiz68CtE9
RuP7I+1r5Lb6KOeh2keWf6/UqU9ZuSeRyyHrAaCWvsHIinudaEud8Q2EAcpgOMdD
+6fkH6jOHpPcIdZCww==
=SFG9
-END PGP SIGNATURE End Message ---

Bug#921484: Origin of background.js and manifest.json not documented?

[Vincent Bernat]

Package: webext-browserpass
Version: 2.0.22-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

I am curious to know why there is a debian/background.js as well as a
debian/manifest.json? They are not documented in debian/copyright. The
manifest seems to have a bogus version numbre (2.1.19 instead of
2.0.22) and is different from the manifest shipped in
{firefox/chrome}/manifest.json. The background.js is also different
(fillLoginForm doesn't have the right signature for example).

Thanks.

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages webext-browserpass depends on:
ii  libc6  2.28-5

Versions of packages webext-browserpass recommends:
ii  chromium  72.0.3626.81-1
ii  firefox   65.0-1

webext-browserpass suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAlxaN5kSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5hMsP/0Z/JrWfOJLZzSy5/0QIzJYlzkhtcpsI
iehpCZuAoMn5vkmthZT7drdUUclHGKk6QHhnpWRi0nk2d5CF7wFhKdn7VUx32oKD
h0rIxDA+8O17SqZxNNBcykiKbODVpRqIu3L04BqrlVnNMIJotyQmf+ddAq41Bast
IXL0tENdNNOXtuUXAaU6//wBvKChe0Mnq4L5m084Jj8do+enDELiMO9Eu3/fs/EL
nOdOrltMS+6UAik4K3cA/8l/ZX5wsYJbQTmrFizkyNNqWRnx83imbPHmPsMhPsAA
M4LL5XMsMNEeY0VYyQHgtONkb0J8XMGO2hOODvx5xhoEx71PA+/NgP/IN2XDbUaz
8SXc5UIoR/ATHreN05DyG55eiQGMJo8AdQmAsyJdULn7vMLU00HawutMW62M324+
gyJY00h+9ZB6lP8crNtR2a4rR/tHxQef4zhNC0zuJqMEV0LDltefqOas9PAVPBzB
T0k2jPlbmGqX60aqCQYKL+LYEZd2ZZnAdEDIeqXiQ2kpEabLYaQDoUpepDiVXYpj
Sr3xXYFYDvUVylbEdqAqR5nQ6t8xHVwcriq9JkaXFqJfUj1W80dMLd/bhrd/E5dP
xgx8j0jJuLf2jX/KT5VNUymWyCLPpEvZHm/0NDiJmnQ9TigtIJrZx8tt5e7HvzxU
Wb2keYQ6r02I
=8GJn
-END PGP SIGNATURE-

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

[Frank Heckenbach]

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

> Assuming that the changes in a new release do not change
> other behaviour, or that I can cherry pick a targeted fix for this
> problem, we're still good to go.

Not much to cherry pick AFAICS. This issue is the only discrepancy
between our versions and if we find a (transitory) solution, we'll
be in sync.

Cheers,
Frank

Bug#921126: marked as done (wine-development: checks for /run/user instead of /run/user/$uid)

[Debian Bug Tracking System]

Your message dated Wed, 06 Feb 2019 01:24:18 +
with message-id 
and subject line Bug#921126: fixed in wine-development 4.1-1
has caused the Debian Bug report #921126,
regarding wine-development: checks for /run/user instead of /run/user/$uid
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.)


-- 
921126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:wine-development
severity: serious
version: 3.12-2

This has been fixed in wine [0].  It also needs to be fixed in wine-development.

Best wishes,
Mike

[0] http://bugs.debian.org/918666
--- End Message ---
--- Begin Message ---
Source: wine-development
Source-Version: 4.1-1

We believe that the bug you reported is fixed in the latest version of
wine-development, 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.
Michael Gilbert  (supplier of updated wine-development 
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 00:19:39 +
Source: wine-development
Architecture: source
Version: 4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Closes: 921126
Changes:
 wine-development (4.1-1) unstable; urgency=medium
 .
   * New upstream release 4.1, released Feb 4, 2019.
 - Support for NT kernel spinlocks.
 - Better glyph positioning in DirectWrite.
 - More accurate reporting of CPU information.
 - Context handle fixes in the IDL compiler.
 - Various bug fixes.
   * Switch to the development branch.
 - Checks that /run/user/$uid exists (closes: #921126).
Checksums-Sha1:
 476398b5871706a08facadf9459080a1dd97be2b 4743 wine-development_4.1-1.dsc
 0b291845abc58c1e788a19a43f8ea05b8b9fb5a9 19928840 
wine-development_4.1.orig.tar.xz
 1b2d8dbb032d37249540c9f948781b3d91a661f2 192688 
wine-development_4.1-1.debian.tar.xz
 ab790d2b9451f02d537a35e1499ad77533701cf6 19249 
wine-development_4.1-1_source.buildinfo
Checksums-Sha256:
 ebe77f2cc53c99a894c7764064d85fa990e0e763e13573edea7b74e8f641e316 4743 
wine-development_4.1-1.dsc
 ab2801e99596ca297c8a9e9e54216bff3fb1d6d6ccebf493f0c37a85ff59f466 19928840 
wine-development_4.1.orig.tar.xz
 079ac2412cc36057c641dd322fbb1c8f86ae19efd9c1ec9f0d462f5b5a5c6c88 192688 
wine-development_4.1-1.debian.tar.xz
 c066a2caad56cffc1f80190e5996b00884f6de3bb4847e5daf9ddf41f284000a 19249 
wine-development_4.1-1_source.buildinfo
Files:
 6f383349338d0412323f62c773db1fd5 4743 otherosfs optional 
wine-development_4.1-1.dsc
 e701e1764130a9808a3cd5b44f07e205 19928840 otherosfs optional 
wine-development_4.1.orig.tar.xz
 4b4c4983a6b6b010128b380d191c1092 192688 otherosfs optional 
wine-development_4.1-1.debian.tar.xz
 902f2ff3272fe56bbd00c94736acb28a 19249 otherosfs optional 
wine-development_4.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEluhy7ASCBulP9FUWuNayzQLW9HMFAlxaMEYACgkQuNayzQLW
9HMq8B//QaUG7MnJGLhZ1BIRuQI85wPWS0u26xNbhXO+b8GHnBKpdsSKv6+Z8bnO
z2itpAIrpH/yaTsi6tigECX6w7ifHMsDTlQ3mmnX/KHmBU/6wsDvdiD56PjS3bCq
6NvNe5Hwhok+m2wlHCVhZKCFG8bR5qjpyC86Wr4RYPhExXkTlR7Tw0PlglG8EBpP
ZHkTq9TjPcOEi0U6C0iPjrLxIid7WqRSBXB+cmifvi3ym+bhkj4LQ4YhTVDanMAi
Xd/S8glyMPDD4cGltjBD2qhMxf+w26949N0DoZpQuyoYFCS95UBm4eaT5SOL+CHD
u96CbmHm0XqDqcTvvyS43uyyVtcW4pAannah4zyFfiIT3OFLKYVf5bz5s7LFjfp6
XnZ7MEVrzdf25QNLHAzdu5G8kXmZnytJs4wv8zSCPbvK9MP/bSs7WlfdZwo9iURx
nDbahAJ/Chqo/TNR61MSpXavKhc25fWOAtoUOMT7xJrBYa3qo2VAXMTruru25+KH
BfUSyzDgZW4Vo8fgCj8EBf3gosEVLiNfAT9gbDoAFYbKUT2Oe2d6TtnaNf3V8wv8
szL73DiIcPDAMEvf2D/5eVJnlXtee8ydVNqUdwbsNFjlRgktfY8wlq4FgxIsgJ1F
dQcCAOrMn5N4JeeY5jM3SdErH15GiFH2k7l5wICyPz6BKF0P9inLGsEsCYIF+De1
/LQA+f61oZUDZR9mZTUKA5Vjrc5IvVGCGhci96MlHSMkE5sR1mDZ7zYEJh5b6vTY
5ypJjt9/elkuKcDYWrOtYTk38J8Bb32drgWaSpPSLGUksJKAhVORBUUQ+kCpHBG3
O7acNE7w6iti68Ok1q+1u1AvN8nJ9a0sjaCqiQoZoKsVGWu7YXWZv7Ql9IWkG0Oo
5E8mQrUPOdnYG+ckTFBQ2RhuZ/D4TrnqemHjxrqp4A27foXJuJDb0BCfKXA/kz1b
h1yceBEiUAbG++MzUlqB7QjcayoHD0P0ZmxTRC3vX+obBvObEppUxqn1flCUguoi
DxO32xEfV+7rqTw7IGmILd+eD8oA/DUnzunuW6upl+iEGxtc48BXMkGZ0Op1+zx3

Bug#921479: marked as done (lxqt-branding-debian: fails to upgrade from 'stable' to 'sid' - trying to overwrite /etc/xdg/lxqt/panel.conf)

[Debian Bug Tracking System]

Your message dated Wed, 06 Feb 2019 01:22:34 +
with message-id 
and subject line Bug#921479: fixed in lxqt-branding-debian 0.14.0.1
has caused the Debian Bug report #921479,
regarding lxqt-branding-debian: fails to upgrade from 'stable' to 'sid' - 
trying to overwrite /etc/xdg/lxqt/panel.conf
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.)


-- 
921479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lxqt-branding-debian
Version: 0.14.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

From the attached log (scroll to the bottom...):

  Preparing to unpack .../lxqt-branding-debian_0.14.0_all.deb ...   

   Unpacking 
lxqt-branding-debian (0.14.0) ...   

   dpkg: error processing archive 
/var/cache/apt/archives/lxqt-branding-debian_0.14.0_all.deb (--unpack): 

   trying to overwrite '/etc/xdg/lxqt/panel.conf', which is 
also in package lxqt-panel 0.11.1-1 
   
Errors were encountered while processing:   

  
/var/cache/apt/archives/lxqt-branding-debian_0.14.0_all.deb 

  


cheers,

Andreas


lxqt-panel=0.11.1-1_lxqt-branding-debian=0.14.0.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lxqt-branding-debian
Source-Version: 0.14.0.1

We believe that the bug you reported is fixed in the latest version of
lxqt-branding-debian, 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.
Alf Gaida  (supplier of updated lxqt-branding-debian 
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 01:42:13 +0100
Source: lxqt-branding-debian
Binary: lxqt-branding-debian lxqt-theme-debian
Architecture: source
Version: 0.14.0.1
Distribution: unstable
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Alf Gaida 
Description:
 lxqt-branding-debian - Debian branding for LXQt
 lxqt-theme-debian - Debian theme for LXQt
Closes: 921479
Changes:
 lxqt-branding-debian (0.14.0.1) unstable; urgency=medium
 .
   * Added needed Breaks and Replaces for lxqt-panel. (Closes: #921479)
 Thanks Andreas Beckmann (a...@debian.org) for the finding.
Checksums-Sha1:
 d77b15862447f7d626219cac591ffc60caf46127 1512 lxqt-branding-debian_0.14.0.1.dsc
 cb6247011c99c623f4bd939e95c88d7b06786be0 27452 
lxqt-branding-debian_0.14.0.1.tar.xz
 070f5c07911fc5bc299401192cef5c3e3883f01b 12374 
lxqt-branding-debian_0.14.0.1_source.buildinfo
Checksums-Sha256:
 141306a36c1049cc96ab2138d9d4484a47f1dc1f7ae3cdd1b8f382de0d171ff0 1512 
lxqt-branding-debian_0.14.0.1.dsc
 fb15c4121be66e510167a60191f2c26911fb3f6efe5ee8b4f8aeb8ba1e779394 27452 
lxqt-branding-debian_0.14.0.1.tar.xz
 

Bug#921476: marked as done (python3-spf-engine: missing Breaks+Replaces: postfix-policyd-spf-python (<< 2.9))

[Debian Bug Tracking System]

Your message dated Wed, 06 Feb 2019 01:23:14 +
with message-id 
and subject line Bug#921476: fixed in spf-engine 2.9.0-2
has caused the Debian Bug report #921476,
regarding python3-spf-engine: missing Breaks+Replaces: 
postfix-policyd-spf-python (<< 2.9)
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.)


-- 
921476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-spf-engine
Version: 2.9.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

From the attached log (scroll to the bottom...):

  Preparing to unpack .../python3-spf-engine_2.9.0-1_all.deb ...

   Unpacking 
python3-spf-engine (2.9.0-1) ...

   dpkg: error processing archive 
/var/cache/apt/archives/python3-spf-engine_2.9.0-1_all.deb (--unpack):  

   trying to overwrite 
'/usr/lib/python3/dist-packages/spf_engine/__init__.py', which is also in 
package postfix-policyd-spf-python 2.1.0-1  
  Errors were encountered while processing: 


/var/cache/apt/archives/python3-spf-engine_2.9.0-1_all.deb  

  

cheers,

Andreas


postfix-policyd-spf-python=2.1.0-1_python3-spf-engine=2.9.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: spf-engine
Source-Version: 2.9.0-2

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated spf-engine 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:04:23 -0500
Source: spf-engine
Binary: postfix-policyd-spf-python pyspf-milter python3-spf-engine
Architecture: source all
Version: 2.9.0-2
Distribution: unstable
Urgency: high
Maintainer: Scott Kitterman 
Changed-By: Scott Kitterman 
Description:
 postfix-policyd-spf-python - Postfix policy server for SPF checking
 pyspf-milter - Modern milter for SPF checking
 python3-spf-engine - Sender Policy Framework (SPF) processing module
Closes: 921476
Changes:
 spf-engine (2.9.0-2) unstable; urgency=high
 .
   * Add Breaks/Replaces for python3-spf-engine to fix upgrade issues (Closes:
 #921476)
Checksums-Sha1:
 5c3ef93254a9b17117f0bee22c58bfc7cdad8ea1 2152 spf-engine_2.9.0-2.dsc
 9a96a7cfa484c2247992b1467a14216c06de2b62 9028 spf-engine_2.9.0-2.debian.tar.xz
 ff82554edc391df3c3567c0d6c4989c05992d490 36032 
postfix-policyd-spf-python_2.9.0-2_all.deb
 fc12a122244278765adba3c2f13696ab7a1df063 21356 pyspf-milter_2.9.0-2_all.deb
 77025205e8050cb227bae395001b973ecb4b2ae3 26588 
python3-spf-engine_2.9.0-2_all.deb
 db7d7ff63a43bb4cef05b70495a99db7566d0513 5634 
spf-engine_2.9.0-2_amd64.buildinfo
Checksums-Sha256:
 7f87e1d53a59fe64170e455be12c4e865fe858fa81804178524fdd62411051b4 2152 
spf-engine_2.9.0-2.dsc
 a7f12d513e112abf1e7aa01b4889ed22905ed43bbcbe19c05572fab9484b70e4 9028 

Bug#921473: calibre: Invalid maintainer address

[Scott Kitterman]

On February 5, 2019 11:50:47 PM UTC, Nicholas D Steeves  
wrote:
>Hi Scott,
>
>Reply follows inline.
>
>On Tue, Feb 05, 2019 at 05:31:23PM -0500, Scott Kitterman wrote:
>> Package: calibre
>> Version: 3.39.1+dfsg-1
>> Severity: serious
>> Justification: Policy 3.3
>> 
>> Debian policy requires a valid maintainer address:
>> 
>> A message that you sent could not be delivered to one or more of its
>> recipients. This is a permanent error. The following address(es)
>failed:
>> 
>>   prein...@debian.org
>> Unrouteable address
>> 
>> From: Debian FTP Masters 
>> Subject: Processing of calibre_3.39.1+dfsg-1_source.changes
>> Date: Tue, 05 Feb 2019 22:27:18 +
>> X-Debian: DAK
>> X-DAK: DAK
>> Precedence: bulk
>> Auto-Submitted: auto-generated
>> X-Debian-Package: calibre
>> Message-Id: 
>> 
>> calibre_3.39.1+dfsg-1_source.changes uploaded successfully to
>localhost
>> along with the files:
>>   calibre_3.39.1+dfsg-1.dsc
>>   calibre_3.39.1+dfsg.orig.tar.xz
>>   calibre_3.39.1+dfsg-1.debian.tar.xz
>>   calibre_3.39.1+dfsg-1_amd64.buildinfo
>> 
>> Greetings,
>> 
>>  Your Debian queue daemon (running on host usper.debian.org)
>> 
>> --1549405639-eximdsn-1087713461--
>> 
>> Scott K
>
>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.
>
>Worst case scenario, what is the deadline to adopt Calibre?  I believe
>Norbert is still the maintainer, but am willing to adopt the package
>if I do not receive consent to publish a package using his private
>address before $deadline.

For deadlines for Buster, you should consult the release team's emails on the 
freeze schedule.

Scott K

Bug#899558: marked as done (iw: Invalid maintainer address pkg-wpa-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Wed, 6 Feb 2019 01:20:57 +0100
with message-id 
and subject line Re: iw: Invalid maintainer address 
pkg-wpa-de...@lists.alioth.debian.org
has caused the Debian Bug report #899558,
regarding iw: Invalid maintainer address pkg-wpa-de...@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.)


-- 
899558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:iw
Version: 4.14-0.1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of iw,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package iw since the list address
pkg-wpa-de...@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-wpa-de...@lists.alioth.debian.org is 1.

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: 4.14-1

I adopted the package and set myself as maintainer.--- End Message ---

Bug#921479: lxqt-branding-debian: fails to upgrade from 'stable' to 'sid' - trying to overwrite /etc/xdg/lxqt/panel.conf

[Alf Gaida]

Thank you very much, nice finding. No discussions, my fault.

Processed: tagging 921476

[Debian Bug Tracking System]

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

> tags 921476 + pending
Bug #921476 [python3-spf-engine] python3-spf-engine: missing Breaks+Replaces: 
postfix-policyd-spf-python (<< 2.9)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: packages affected by mpi4py

[Debian Bug Tracking System]

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

> affects 921437 python3-mpi4py src:dolfin
Bug #921437 [release.debian.org] nmu: mpi4py_2.0.0-3+b2
Added indication that 921437 affects python3-mpi4py and src:dolfin
> thanks
Stopping processing here.

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

Bug#921479: lxqt-branding-debian: fails to upgrade from 'stable' to 'sid' - trying to overwrite /etc/xdg/lxqt/panel.conf

[Andreas Beckmann]

Package: lxqt-branding-debian
Version: 0.14.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

From the attached log (scroll to the bottom...):

  Preparing to unpack .../lxqt-branding-debian_0.14.0_all.deb ...   

   Unpacking 
lxqt-branding-debian (0.14.0) ...   

   dpkg: error processing archive 
/var/cache/apt/archives/lxqt-branding-debian_0.14.0_all.deb (--unpack): 

   trying to overwrite '/etc/xdg/lxqt/panel.conf', which is 
also in package lxqt-panel 0.11.1-1 
   
Errors were encountered while processing:   

  
/var/cache/apt/archives/lxqt-branding-debian_0.14.0_all.deb 

  


cheers,

Andreas


lxqt-panel=0.11.1-1_lxqt-branding-debian=0.14.0.log.gz
Description: application/gzip

Bug#909071: pbbam: FTBFS on every release architecture where it previously built (fwd)

[Steve Langasek]

On Tue, Feb 05, 2019 at 11:10:15PM +0200, Adrian Bunk wrote:
> On Tue, Feb 05, 2019 at 12:06:22PM -0800, Steve Langasek wrote:
> > On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> > > And then there is the unrelated #908269 that currently prevents testing 
> > > migration of pbbam.

> > > Steve seems to be addressing this with
> > > http://launchpadlibrarian.net/409374477/pbbam_0.19.0+dfsg-1ubuntu3_0.19.0+dfsg-1ubuntu4.diff.gz

> > Yes, but the net result of this change is that now the autopkgtest fails by
> > running out of memory during the package build at test time, which is why I
> > haven't submitted a better patch to the BTS.

> > I think the ideal here would be to either have a way to generate just the
> > single data file we need for the tests, or to capture that file from the
> > package build and ship it in a binary package, so that we don't have to do a
> > full rebuild during the autopkgtests.

> The file is generated during configure, not build.

> As proof of concept, it works to do

> override_dh_auto_test: $(subst .t.in,.deb.t,$(wildcard 
> tests/src/cram/pb*.t.in))
> ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
>   dh_auto_configure -O--buildsystem=meson
> ...

Indeed, with this pbbam now passes its autopkgtests on all three
architectures in Ubuntu.  Attached is a complete patch against pbbam
0.19.0+dfsg-3 for this.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru pbbam-0.19.0+dfsg/debian/rules pbbam-0.19.0+dfsg/debian/rules
--- pbbam-0.19.0+dfsg/debian/rules  2019-02-04 02:47:51.0 -0800
+++ pbbam-0.19.0+dfsg/debian/rules  2019-02-05 13:58:07.0 -0800
@@ -26,6 +26,7 @@
 
 override_dh_auto_test: $(subst .t.in,.deb.t,$(wildcard 
tests/src/cram/pb*.t.in))
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
+   dh_auto_configure -O--buildsystem=meson
mkdir -p $(generated_data_dir)
python tests/scripts/generate_data.py $(CURDIR)/tests/data 
$(generated_data_dir)
# Fix broken PATH
diff -Nru pbbam-0.19.0+dfsg/debian/tests/control 
pbbam-0.19.0+dfsg/debian/tests/control
--- pbbam-0.19.0+dfsg/debian/tests/control  2019-02-02 22:57:09.0 
-0800
+++ pbbam-0.19.0+dfsg/debian/tests/control  2019-02-05 13:58:07.0 
-0800
@@ -1,11 +1,5 @@
 Test-Command: debian/rules override_dh_auto_test
 Depends:
-   make,
-   python,
+   @builddeps@,
pbbamtools,
-   python-cram,
-   samtools
-Restrictions:
-   rw-build-tree,
-   allow-stderr,
-   build-needed
+Restrictions: rw-build-tree, allow-stderr


signature.asc
Description: PGP signature

Bug#920037: dont include in buster - scala and sbt

[Thomas Finneid]

Hi

I am arriving a little late to this disucussion, so please forgive me if 
this is old news or I have misunderstood.


First, a small comment. Even though there might be only a few debian 
packages that requires java 8, there are still a lot of projects, both 
amateur and professional that still use java 8 and will use it for many 
years to come. So it would probably be missed if removed too early.


To the main point:

Long story short: the current scala package in debian depends on the 
wrong version of java so it does not allways work correctly.


The current scala package contains scala 2.11, which is compatible with 
java 6, but it depends on the java 8 package, so its not really well 
supported.

That is, the scala project built and tested scala 2.11 using java 6.
The current Scala release, 2.12, requires java 8 to work correctly.

I have suggested this, in an email to the pkg-java list and have offered 
to help resolve these issues, as I want to help provide a painless and 
fuller scala development environment for both debian and ubuntu.


But that means jdk 8 must be available in some form in the release.

NB: its not just the java language version, but also the jdk classes 
that are important for correct working of scala. So that means it must 
actually be the jdk-v8 that has to be available, not just jdk11 with 
java8 interpretation.


Regards

Thomas

Bug#921473: calibre: Invalid maintainer address

[Nicholas D Steeves]

Hi Scott,

Reply follows inline.

On Tue, Feb 05, 2019 at 05:31:23PM -0500, Scott Kitterman wrote:
> Package: calibre
> Version: 3.39.1+dfsg-1
> Severity: serious
> Justification: Policy 3.3
> 
> Debian policy requires a valid maintainer address:
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
> 
>   prein...@debian.org
> Unrouteable address
> 
> From: Debian FTP Masters 
> Subject: Processing of calibre_3.39.1+dfsg-1_source.changes
> Date: Tue, 05 Feb 2019 22:27:18 +
> X-Debian: DAK
> X-DAK: DAK
> Precedence: bulk
> Auto-Submitted: auto-generated
> X-Debian-Package: calibre
> Message-Id: 
> 
> calibre_3.39.1+dfsg-1_source.changes uploaded successfully to localhost
> along with the files:
>   calibre_3.39.1+dfsg-1.dsc
>   calibre_3.39.1+dfsg.orig.tar.xz
>   calibre_3.39.1+dfsg-1.debian.tar.xz
>   calibre_3.39.1+dfsg-1_amd64.buildinfo
> 
> Greetings,
> 
>   Your Debian queue daemon (running on host usper.debian.org)
> 
> --1549405639-eximdsn-1087713461--
> 
> Scott K

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.

Worst case scenario, what is the deadline to adopt Calibre?  I believe
Norbert is still the maintainer, but am willing to adopt the package
if I do not receive consent to publish a package using his private
address before $deadline.


Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#886836: closed by Simon McVittie (Bug#886836: fixed in gtkmm2.4 1:2.24.5-3)

[Andreas Beckmann]

Control: found -1 1:2.24.5-3

On 2019-02-05 01:24, Debian Bug Tracking System wrote:
>* Fix "both ship usr/share/doc/libgtkmm-2.4-dev/examples/*":
>  Install all demos into the -dev package, and only there;
>  and also install Makefile*.

libgtkmm-2.4-dev now needs Breaks+Replaces: libgtkmm-2.4-doc (<< 1:2.24.5-3)


Andreas

Processed: Re: Bug#886836 closed by Simon McVittie (Bug#886836: fixed in gtkmm2.4 1:2.24.5-3)

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:2.24.5-3
Bug #886836 {Done: Simon McVittie } 
[libgtkmm-2.4-dev,libgtkmm-2.4-doc] libgtkmm-2.4-dev,libgtkmm-2.4-doc: both 
ship usr/share/doc/libgtkmm-2.4-dev/examples/*
Marked as found in versions gtkmm2.4/1:2.24.5-3; no longer marked as fixed in 
versions gtkmm2.4/1:2.24.5-3 and reopened.

-- 
886836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886836
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 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

Sorry, I've been very busy since end of November, with unexpected work
and family loads.

I have to review the situation again, I completely swapped it out of
my memory.  Assuming that the changes in a new release do not change
other behaviour, or that I can cherry pick a targeted fix for this
problem, we're still good to go.

Cheers,
-- 
Manuel A. Fernandez Montecelo 

Bug#921476: python3-spf-engine: missing Breaks+Replaces: postfix-policyd-spf-python (<< 2.9)

[Andreas Beckmann]

Package: python3-spf-engine
Version: 2.9.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

From the attached log (scroll to the bottom...):

  Preparing to unpack .../python3-spf-engine_2.9.0-1_all.deb ...

   Unpacking 
python3-spf-engine (2.9.0-1) ...

   dpkg: error processing archive 
/var/cache/apt/archives/python3-spf-engine_2.9.0-1_all.deb (--unpack):  

   trying to overwrite 
'/usr/lib/python3/dist-packages/spf_engine/__init__.py', which is also in 
package postfix-policyd-spf-python 2.1.0-1  
  Errors were encountered while processing: 


/var/cache/apt/archives/python3-spf-engine_2.9.0-1_all.deb  

  

cheers,

Andreas


postfix-policyd-spf-python=2.1.0-1_python3-spf-engine=2.9.0-1.log.gz
Description: application/gzip

Bug#921466: rust-rusty-tags: Section: FIXME-(source.section)

[Robin Krahl]

Thanks for the report!  I prepared a new version to fix this issue [0]
and will double-check the section field in the future (though I am
surprised that lintian did not catch that).

[0] 
https://salsa.debian.org/rust-team/debcargo-conf/commit/bcda3d8c5b6efbd1b5b3f6ea0ffa3afea45dbc66


signature.asc
Description: PGP signature

Processed: Re: Bug#921183 closed by Andreas Tille (Bug#921183: fixed in pysurfer 0.9.0-2)

[Debian Bug Tracking System]

Processing control commands:

> found -1  0.9.0-2
Bug #921183 {Done: Andreas Tille } [python3-surfer] 
python3-surfer: missing Breaks+Replaces: python-surfer (<< 0.9.0)
Marked as found in versions pysurfer/0.9.0-2; no longer marked as fixed in 
versions pysurfer/0.9.0-2 and reopened.

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

Bug#921183: closed by Andreas Tille (Bug#921183: fixed in pysurfer 0.9.0-2)

[Andreas Beckmann]

Control: found -1  0.9.0-2

On 2019-02-04 14:54, Debian Bug Tracking System wrote:
>* Breaks / Replaces: python-surfer (<= 0.7-1)

buster has 0.7-2.1 with the file in the old location.


Andreas

Processed: tagging 921473, found 921471 in 0.14.6+ds-4

[Debian Bug Tracking System]

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

> tags 921473 + sid buster
Bug #921473 [calibre] calibre: Invalid maintainer address
Added tag(s) buster and sid.
> found 921471 0.14.6+ds-4
Bug #921471 [pdf2htmlex] Should pdf2htmlex be removed?
There is no source info for the package 'pdf2htmlex' at version '0.14.6+ds-4' 
with architecture ''
Unable to make a source version for version '0.14.6+ds-4'
Marked as found in versions 0.14.6+ds-4.
> thanks
Stopping processing here.

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

Bug#921474: mtail: /usr/bin/mgen is already provided by the mgen package

[Andreas Beckmann]

Package: mtail
Version: 3.0.0~rc19-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

From the attached log (scroll to the bottom...):

  Selecting previously unselected package mtail.

   Preparing to unpack 
.../mtail_3.0.0~rc19-1_amd64.deb ...

 Unpacking mtail (3.0.0~rc19-1) ... 


  dpkg: error processing archive 
/var/cache/apt/archives/mtail_3.0.0~rc19-1_amd64.deb (--unpack):

   trying to overwrite '/usr/bin/mgen', which is also in 
package mgen 5.02.b+dfsg1-2.2   
  
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

 Errors were encountered 
while processing:   

  
/var/cache/apt/archives/mtail_3.0.0~rc19-1_amd64.deb

  

cheers,

Andreas


mgen=5.02.b+dfsg1-2.2_mtail=3.0.0~rc19-1.log.gz
Description: application/gzip

Processed: notfound 920031 in 2.7.1+dfsg1-1

[Debian Bug Tracking System]

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

> notfound 920031 2.7.1+dfsg1-1
Bug #920031 {Done: Georg Faerber } [schleuder] schleuder: 
DEP8 failures with ruby-mail 2.7.1
There is no source info for the package 'schleuder' at version '2.7.1+dfsg1-1' 
with architecture ''
Unable to make a source version for version '2.7.1+dfsg1-1'
No longer marked as found in versions 2.7.1+dfsg1-1.
> thanks
Stopping processing here.

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

Processed: found 920031 in 3.3.0-6

[Debian Bug Tracking System]

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

> found 920031 3.3.0-6
Bug #920031 {Done: Georg Faerber } [schleuder] schleuder: 
DEP8 failures with ruby-mail 2.7.1
Marked as found in versions schleuder/3.3.0-6.
> thanks
Stopping processing here.

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

Bug#920031: marked as done (schleuder: DEP8 failures with ruby-mail 2.7.1)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 22:49:55 +
with message-id 
and subject line Bug#920031: fixed in schleuder 3.3.0-8
has caused the Debian Bug report #920031,
regarding schleuder: DEP8 failures with ruby-mail 2.7.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.)


-- 
920031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: schleuder
Version: 2.7.1+dfsg1-1
Severity: normal

Dear Maintainer,

The DEP8 tests from schleuder are currently failing on all arches
because it can't find ruby-mail 2.6.0:

https://ci.debian.net/packages/s/schleuder/

The test output doesn't show it, but here is a manual run in an Ubuntu
Disco LXD container:

https://pastebin.ubuntu.com/p/Tp3g2PFPp7/
...
/usr/lib/ruby/2.5.0/rubygems/dependency.rb:312:in `to_specs': Could
not find 'mail' (~> 2.6.0) - did find: [mail-2.7.1]
(Gem::MissingSpecVersionError)

I found these upstream:
- https://0xacab.org/schleuder/schleuder/merge_requests/128/diffs:
commit that pinned ruby-mail to 2.6.0
- https://0xacab.org/schleuder/schleuder/issues/277: "ruby-mail 2.7.0
breaks unicode and various other formats
"

I hacked the gem spec to allow ruby-mail 2.7.1, which is what we have
in Ubuntu Disco and Debian Testing, and the test run had two failures:

https://pastebin.ubuntu.com/p/WZhZf42gJg/
...

Failures:

  1) user sends keyword x-resend with utf-8 body and umlauts
 Failure/Error:
expect(message.parts[1].body.to_s.force_encoding(message.parts[1].charset)).to
eql(content_body.encode(message.parts[1].charset))

   expected: "This is a test\nAnd here are some umlauts:ÄäÖöÜüß"
got: "This is a test\r\nAnd here are some umlauts:ÄäÖöÜüß"

   (compared using eql?)

   Diff:

 # ./spec/schleuder/integration/keywords_spec.rb:1923:in `block (2
levels) in '
 # ./spec/spec_helper.rb:47:in `block (3 levels) in '
 # ./spec/spec_helper.rb:46:in `block (2 levels) in '

  2) user sends keyword x-resend with iso-8859-1 body
 Failure/Error:
expect(message.parts[1].body.to_s.force_encoding(message.parts[1].charset)).to
eql(content_body.encode(message.parts[1].charset))

   expected: "Hello again! \xA1Hola!\n"
got: "Hello again! \xA1Hola!\r\n"

   (compared using eql?)

   Diff:

 # ./spec/schleuder/integration/keywords_spec.rb:1881:in `block (2
levels) in '
 # ./spec/spec_helper.rb:47:in `block (3 levels) in '
 # ./spec/spec_helper.rb:46:in `block (2 levels) in '
--- End Message ---
--- Begin Message ---
Source: schleuder
Source-Version: 3.3.0-8

We believe that the bug you reported is fixed in the latest version of
schleuder, 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.
Georg Faerber  (supplier of updated schleuder 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: Tue, 05 Feb 2019 22:32:16 +
Source: schleuder
Architecture: source
Version: 3.3.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Georg Faerber 
Closes: 919072 920031
Changes:
 schleuder (3.3.0-8) unstable; urgency=medium
 .
   * debian/control:
 - Bump required versions of ruby-sinatra and ruby-sinatra-contrib to
   >= 2~.
 - Add missing dependencies on ruby-mail >= 2.7.1~.
   * debian/patches:
 - Pull in upstream patch to strip HTML-part of
   multipart/alternative-messages if it contains keywords. The keywords
   aren't parsed, because Schleuder doesn't touch any HTML. In order to
   prevent the keywords from being disclosed to third parties, for example
   via resent messages, the HTML-part is completely dropped. This issue
   should be considered privacy-sensitive.
 - Add patch to disable a flaky spec, which tests signed-inline cleartext
   messages. Since some time, this formerly pretty stable spec became
   flaky. It it still unclear what causes this, ruby-mail 2.7.1 might be
   somehow related. (Closes: #919072)
 - Add patch which fixes the expected output of one spec. This spec 

Bug#919072: marked as done (schleuder: FTBFS in both buster and sid)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 22:49:55 +
with message-id 
and subject line Bug#919072: fixed in schleuder 3.3.0-8
has caused the Debian Bug report #919072,
regarding schleuder: FTBFS in both buster and sid
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.)


-- 
919072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:schleuder
Version: 3.3.0-6
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

Failures:

  1) user sends a plain text message from thunderbird being signed-inline
 Failure/Error: expect(error).to be_empty
   expected `"Error: A serious, unhandleable error happened. Please contact 
the administrators of this system or service and provide them with the 
following information:\n\ninvalid byte sequence in US-ASCII\n".empty?` to 
return true, got false
 # ./spec/schleuder/integration/send_plain_spec.rb:18:in `block (3 levels) 
in '
 # ./spec/spec_helper.rb:47:in `block (3 levels) in '
 # ./spec/spec_helper.rb:46:in `block (2 levels) in '

  2) user sends keyword x-resend with utf-8 body and umlauts
 Failure/Error: 
expect(message.parts[1].body.to_s.force_encoding(message.parts[1].charset)).to 
eql(content_body.encode(message.parts[1].charset))

   expected: "This is a test\nAnd here are some 
umlauts:\u00C4\u00E4\u00D6\u00F6\u00DC\u00FC\u00DF"
got: "This is a test\r\nAnd here are some 
umlauts:\u00C4\u00E4\u00D6\u00F6\u00DC\u00FC\u00DF"

   (compared using eql?)
 # ./spec/schleuder/integration/keywords_spec.rb:1923:in `block (2 levels) 
in '
 # ./spec/spec_helper.rb:47:in `block (3 levels) in '
 # ./spec/spec_helper.rb:46:in `block (2 levels) in '

  3) user sends keyword x-resend with iso-8859-1 body
 Failure/Error: 
expect(message.parts[1].body.to_s.force_encoding(message.parts[1].charset)).to 
eql(content_body.encode(message.parts[1].charset))

   expected: "Hello again! \xA1Hola!\n"
got: "Hello again! \xA1Hola!\r\n"

   (compared using eql?)
 # ./spec/schleuder/integration/keywords_spec.rb:1881:in `block (2 levels) 
in '
 # ./spec/spec_helper.rb:47:in `block (3 levels) in '
 # ./spec/spec_helper.rb:46:in `block (2 levels) in '

Finished in 4 minutes 38.7 seconds (files took 2.25 seconds to load)
375 examples, 3 failures

Failed examples:

rspec './spec/schleuder/integration/send_plain_spec.rb[1:2]' # user sends a 
plain text message from thunderbird being signed-inline
rspec ./spec/schleuder/integration/keywords_spec.rb:1890 # user sends keyword 
x-resend with utf-8 body and umlauts
rspec ./spec/schleuder/integration/keywords_spec.rb:1848 # user sends keyword 
x-resend with iso-8859-1 body

Randomized with seed 23471

/usr/bin/ruby2.5 /usr/bin/rspec --format documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/schleuder returned 
exit code 1
make: *** [debian/rules:7: binary-indep] Error 1
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but this kind of failure (extra \r in the expected output) also happens here

https://tests.reproducible-builds.org/debian/rbuild/buster/amd64/schleuder_3.3.0-6.rbuild.log.gz

If this is the result of some ongoing transition, please consider fixing the 
FTBFS problem
in sid at least (which is different).

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: schleuder
Source-Version: 3.3.0-8

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

A 

Bug#921432: marked as done (libssl1.1-dbgsym: Cannot install libssl1.1-dbgsym since packet is outdated)

[Debian Bug Tracking System]

Your message dated Tue, 5 Feb 2019 23:44:18 +0100
with message-id <09283296-c75d-5d69-fa1e-8fd5dd084...@debian.org>
and subject line Re: libssl1.0.2-dbgsym: Cannot install libssl1.0.2-dbgsym 
since packet is outdated
has caused the Debian Bug report #921432,
regarding libssl1.1-dbgsym: Cannot install libssl1.1-dbgsym since packet is 
outdated
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.)


-- 
921432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libssl1.1-dbgsym
Severity: serious
Tags: upstream
Justification: Policy 7.2

Dear Maintainer,

I tried to install libssl1.1-dbgsym on my machine.
However, apt refuses to install it:
he following packages have unmet dependencies:
libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.0f-3+deb9u2) but
1.1.0j-1~deb9u1 is to be installed

I already tried to clean the apt cache ("apt-get clean") and fetch it
again ("apt update") without any effect.
I used the following repo to retrieve the package:
deb http://deb.debian.org/debian-debug/ stable-debug main

For me, it seems that the package is out-dated.

Regards,
Alex


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

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

Versions of packages libssl1.1-dbgsym depends on:
ii  libssl1.1  1.1.0j-1~deb9u1

libssl1.1-dbgsym recommends no packages.

libssl1.1-dbgsym suggests no packages.
--- End Message ---
--- Begin Message ---
On Tue, 05 Feb 2019 14:15:27 +0100 Alexander Lochmann
 wrote:
> Package: libssl1.0.2-dbgsym

> I tried to install libssl1.0.2-dbgsym on my machine.
> However, apt refuses to install it:
> he following packages have unmet dependencies:
>  libssl1.0.2-dbgsym : Depends: libssl1.0.2 (= 1.0.2l-2+deb9u3) but
>  1.0.2q-1~deb9u1 is to be installed

> deb http://deb.debian.org/debian-debug/ stable-debug main
> 
> For me, it seems that the package is out-dated.

The libssl1.0.2 1.0.2q-1~deb9u1 package comes from the security updates
archive. AFAIK the security updates don't provide a separate debug
archive itself, but you can get the desired package from the debug
section of stretch-proposed-updates, e.g. with an sources.list entry like

deb http://deb.debian.org/debian-debug stretch-proposed-updates-debug main

$ rmadison -a amd64 libssl1.0.2-dbgsym
libssl1.0.2-dbgsym | 1.0.2l-2+deb9u3 | stable-debug   | amd64
libssl1.0.2-dbgsym | 1.0.2q-1~deb9u1 | proposed-updates-debug | amd64
libssl1.0.2-dbgsym | 1.0.2q-2| unstable-debug | amd64

$ apt-cache policy libssl1.0.2-dbgsym
libssl1.0.2-dbgsym:
  Installed: (none)
  Candidate: 1.0.2q-1~deb9u1
  Version table:
 1.0.2q-1~deb9u1 500
500 http://ftp.de.debian.org/debian-debug
stretch-proposed-updates-debug/main amd64 Packages
 1.0.2l-2+deb9u3 500
500 http://ftp.de.debian.org/debian-debug stretch-debug/main
amd64 Packages

Andreas--- End Message ---

Bug#921450: fetchmail: Fetchmail segfaults upon execution

[Sébastien Dinot]

- Mail original -
>  Thanks! Do you get the message via procmail and / or does it get
> deleted from your server?

Each time I launch fetchmail, I retrieve a copy of the same first message in my 
local mailbox, but this message is not deleted from my server.

I don't know if this other piece of information can help, but this issue is not 
the only issue I encounters since the last update of fetchmail. Actually, I 
also use fetchmail to retrieve messages from another mail server (my ISP's). 
Since the last update of fetchmail, recovery on this server fails (without 
segmentation fault) for another reason:


$ env LC_ALL=C fetchmail -v -v -v  --nodetach --nosyslog -b 2
Old UID list from pop.free.fr:
 

Scratch list of UIDs:
 

fetchmail: removing stale lockfile
fetchmail: 6.4.0.beta4 querying pop.free.fr (protocol POP3) at Tue Feb  5 
23:33:22 2019: poll started
Trying to connect to 212.27.48.3/110...connected.
fetchmail: POP3< +OK POP3 ready <1391411951.1549406002@popn1>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< UIDL
fetchmail: POP3< SASL LOGIN PLAIN
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< -ERR invalid command
fetchmail: invalid command
fetchmail: pop.free.fr: upgrade to TLS failed.
fetchmail: Unknown login or authentication error on sebastien.di...@pop.free.fr
fetchmail: socket error while fetching from sebastien.di...@pop.free.fr
fetchmail: 6.4.0.beta4 querying pop.free.fr (protocol POP3) at Tue Feb  5 
23:33:22 2019: poll completed
Merged UID list from pop.free.fr:
 
fetchmail: Query status=2 (SOCKET)
fetchmail: normal termination, status 2


Sébastien

Bug#921430: marked as done (libssl1.0.2-dbgsym: Cannot install libssl1.0.2-dbgsym since packet is outdated)

[Debian Bug Tracking System]

Your message dated Tue, 5 Feb 2019 23:44:18 +0100
with message-id <09283296-c75d-5d69-fa1e-8fd5dd084...@debian.org>
and subject line Re: libssl1.0.2-dbgsym: Cannot install libssl1.0.2-dbgsym 
since packet is outdated
has caused the Debian Bug report #921430,
regarding libssl1.0.2-dbgsym: Cannot install libssl1.0.2-dbgsym since packet is 
outdated
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.)


-- 
921430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libssl1.0.2-dbgsym
Severity: serious
Justification: Policy 7.2

Dear Maintainer,


I tried to install libssl1.0.2-dbgsym on my machine.
However, apt refuses to install it:
he following packages have unmet dependencies:
 libssl1.0.2-dbgsym : Depends: libssl1.0.2 (= 1.0.2l-2+deb9u3) but
 1.0.2q-1~deb9u1 is to be installed

I already tried to clean the apt cache ("apt-get clean") and fetch it
again ("apt update") without any effect.
I used the following repo to retrieve the package:
deb http://deb.debian.org/debian-debug/ stable-debug main

For me, it seems that the package is out-dated.

Regards,
Alex

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

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

Versions of packages libssl1.0.2-dbgsym depends on:
ii  libssl1.0.2  1.0.2q-1~deb9u1

libssl1.0.2-dbgsym recommends no packages.

libssl1.0.2-dbgsym suggests no packages.
--- End Message ---
--- Begin Message ---
On Tue, 05 Feb 2019 14:15:27 +0100 Alexander Lochmann
 wrote:
> Package: libssl1.0.2-dbgsym

> I tried to install libssl1.0.2-dbgsym on my machine.
> However, apt refuses to install it:
> he following packages have unmet dependencies:
>  libssl1.0.2-dbgsym : Depends: libssl1.0.2 (= 1.0.2l-2+deb9u3) but
>  1.0.2q-1~deb9u1 is to be installed

> deb http://deb.debian.org/debian-debug/ stable-debug main
> 
> For me, it seems that the package is out-dated.

The libssl1.0.2 1.0.2q-1~deb9u1 package comes from the security updates
archive. AFAIK the security updates don't provide a separate debug
archive itself, but you can get the desired package from the debug
section of stretch-proposed-updates, e.g. with an sources.list entry like

deb http://deb.debian.org/debian-debug stretch-proposed-updates-debug main

$ rmadison -a amd64 libssl1.0.2-dbgsym
libssl1.0.2-dbgsym | 1.0.2l-2+deb9u3 | stable-debug   | amd64
libssl1.0.2-dbgsym | 1.0.2q-1~deb9u1 | proposed-updates-debug | amd64
libssl1.0.2-dbgsym | 1.0.2q-2| unstable-debug | amd64

$ apt-cache policy libssl1.0.2-dbgsym
libssl1.0.2-dbgsym:
  Installed: (none)
  Candidate: 1.0.2q-1~deb9u1
  Version table:
 1.0.2q-1~deb9u1 500
500 http://ftp.de.debian.org/debian-debug
stretch-proposed-updates-debug/main amd64 Packages
 1.0.2l-2+deb9u3 500
500 http://ftp.de.debian.org/debian-debug stretch-debug/main
amd64 Packages

Andreas--- End Message ---

Bug#892288: arrayfire test crash

[Rebecca N. Palmer]

Control: tags -1 fixed-upstream patch

These look like the upstream fixes, though I haven't actually tried them 
yet.


for index:

https://github.com/arrayfire/arrayfire/commit/58ac59497b50257631713e689a6b0ddffb73361a

for assign:

https://github.com/arrayfire/arrayfire/commit/1b18226dfec811e4b7b7254f5cfc85a3116a3dc2

Processed: Re: arrayfire test crash

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream patch
Bug #892288 [src:arrayfire] arrayfire FTBFS on i386: test segfaults
Added tag(s) patch and fixed-upstream.

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

Bug#921473: calibre: Invalid maintainer address

[Scott Kitterman]

Package: calibre
Version: 3.39.1+dfsg-1
Severity: serious
Justification: Policy 3.3

Debian policy requires a valid maintainer address:

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  prein...@debian.org
Unrouteable address

From: Debian FTP Masters 
Subject: Processing of calibre_3.39.1+dfsg-1_source.changes
Date: Tue, 05 Feb 2019 22:27:18 +
X-Debian: DAK
X-DAK: DAK
Precedence: bulk
Auto-Submitted: auto-generated
X-Debian-Package: calibre
Message-Id: 

calibre_3.39.1+dfsg-1_source.changes uploaded successfully to localhost
along with the files:
  calibre_3.39.1+dfsg-1.dsc
  calibre_3.39.1+dfsg.orig.tar.xz
  calibre_3.39.1+dfsg-1.debian.tar.xz
  calibre_3.39.1+dfsg-1_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

--1549405639-eximdsn-1087713461--

Scott K

Bug#921471: Should pdf2htmlex be removed?

[Johannes Schauer]

On Tue, 05 Feb 2019 23:12:03 +0100 Moritz Muehlenhoff  wrote:
> Should pdf2htmlex be removed? It's RC-buggy for over a year and upstream
> development seems to have stopped:
> http://pdf2htmlex.blogspot.de/2016/12/looking-for-new-maintainer.html

Yes, possibly.

Funny, that you are reporting this today because just a few hours ago, I
reached out to a fork that claims to continue development. Unfortunately,
things don't look rosy over there either:

https://github.com/pdf2htmlEX/pdf2htmlEX/issues/20


signature.asc
Description: signature

Bug#921471: Should pdf2htmlex be removed?

[Moritz Muehlenhoff]

Package: pdf2htmlex
Severity: serious

Should pdf2htmlex be removed? It's RC-buggy for over a year and upstream
development seems to have stopped:
http://pdf2htmlex.blogspot.de/2016/12/looking-for-new-maintainer.html

Cheers,
Moritz

Bug#921450: fetchmail: Fetchmail segfaults upon execution

[GCS]

On Tue, Feb 5, 2019 at 10:36 PM Sébastien Dinot  wrote:
> I didn't find the fetchmail-dbgsym package, but here is what the
> suggested command displays:
[...]
> fetchmail: POP3> LIST 1
> fetchmail: POP3< +OK 1 474
> fetchmail: POP3> RETR 1
> fetchmail: POP3< +OK 474 octets
> reading message m...@mail.example.com:1 of 22 (474 octets) About to rewrite 
> Return-Path: ...
> ...rewritten version is Return-Path: .
> About to rewrite From: Fail2Ban ...
> ...rewritten version is From: Fail2Ban .
> About to rewrite To: r...@example.com...
> ...rewritten version is To: r...@example.com.
> fetchmail: about to deliver with: /usr/bin/procmail -Y -d 'me'
> #*** flushed
> fetchmail: POP3> DELE 1
> fetchmail: POP3< +OK Marked to be deleted.
> Segmentation fault
 Thanks! Do you get the message via procmail and / or does it get
deleted from your server?

Cheers,
Laszlo/GCS

Bug#921450: fetchmail: Fetchmail segfaults upon execution

[Eduard Bloch]

On Tue, 5 Feb 2019 19:22:21 +0100 
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?=  wrote:
> Control: tags -1 +unreproducible moreinfo
> 
> Hi James,
> 
> On Tue, Feb 5, 2019 at 6:09 PM James Henried  wrote:
> > fetchmail has stopped working in version 6.4.0~beta4-2.
>  Which previous version did you use?
> 
> > Running the daemon gets the first mail in the queue delivered, but then it 
> > segfaults.
>  Please install fetchmail-dbgsym if it may give more information.
> 
> What happens if you stop the daemon and run it from the command line?
> What's the output if it still fails?
> Are you open to provide detailed log like the following produces?
> $ env LC_ALL=C fetchmail -v -v -v  --nodetach --nosyslog -b 2

I can reproduce it well if it's the same problem.
Here is your stack information, with minimal anonymization.

For me it's not crashing ASAP, it skips two messages with "bad header"
status and crashes upon encountering the first good message.

(gdb) bt
#0  pop3_delete (sock=, ctl=0x555b4db0, number=3) at 
pop3.c:1362
#1  0x555669b0 in fetch_messages (msgsizes=0x5559f480 , 
transient_errors=, 
deletions=, dispatches=, 
fetches=, maxfetch=1000, 
count=, ctl=0x555b4db0, mailserver_socket=3) at 
driver.c:812
#2  do_session (ctl=ctl@entry=0x555b4db0, proto=proto@entry=0x5559a200 
, maxfetch=maxfetch@entry=1000)
at driver.c:1435
#3  0x55567df9 in do_protocol (ctl=0x555b4db0, proto=0x5559a200 
) at driver.c:1677
#4  0xfb48 in query_host (ctl=0x555b4db0) at fetchmail.c:1546
#5  0xa37b in main (argc=, argv=0x7fffe5d8) at 
fetchmail.c:793
(gdb) display ctl
1: ctl = (struct query *) 0x555b4db0
(gdb) display *ctl
2: *ctl = {server = {pollname = 0x555b4cf0 "MYSERVER", via = 0x0, akalist = 
0x0, localdomains = 0x0, protocol = 3, 
service = 0x0, interval = 0, authenticate = 1, timeout = 300, envelope = 
0x0, envskip = 0, qvirtual = 0x0, 
skip = 0 '\000', dns = 1 '\001', uidl = 0 '\000', sdps = 0 '\000', 
checkalias = 0 '\000', tracepolls = 0 '\000', 
principal = 0x0, esmtp_name = 0x0, esmtp_password = 0x0, badheader = 
BHREJECT, interface = 0x0, monitor = 0x0, 
monitor_io = 0, interface_pair = 0x0, plugin = 0x0, plugout = 0x0, 
base_protocol = 0x5559a200 , poll_count = 0, 
queryname = 0x555b3f90 "MYSERVER", truename = 0x555b4020 
"MYSERVER", trueaddr = 0x555fcf50, 
trueaddr_len = 16, lead_server = 0x0, esmtp_options = 3, workarounds = 0}, 
localnames = 0x555b4d50, wildcard = 0, 
  remotename = 0x555b4cd0 "ANON", password = 0x555b4d10 "ANON", 
mailboxes = 0x555b4080, 
  smtphunt = 0x555b4060, domainlist = 0x0, smtpaddress = 0x0, smtpname = 
0x0, antispam = 0x555b4d90, mda = 0x0, 
  bsmtp = 0x0, listener = 83 'S', preconnect = 0x0, postconnect = 0x0, keep = 0 
'\000', fetchall = 1 '\001', flush = 0 '\000', 
  limitflush = 0 '\000', rewrite = 1 '\001', stripcr = 0 '\000', forcecr = 0 
'\000', pass8bits = 0 '\000', 
  dropstatus = 0 '\000', dropdelivered = 0 '\000', mimedecode = 0 '\000', idle 
= 0 '\000', limit = 0, warnings = 3600, 
  fetchlimit = 0, fetchsizelimit = 100, fastuidl = 4, fastuidlcount = 0, 
batchlimit = 70, expunge = 1000, use_ssl = 1 '\001', 
  sslkey = 0x0, sslcert = 0x0, sslproto = 0x0, sslcertfile = 0x0, sslcertpath = 
0x0, sslcertck = 1 '\001', 
  sslcommonname = 0x0, sslfingerprint = 0x0, properties = 0x0, active = 1 
'\001', destaddr = 0x5564c7e0 "localhost", 
  errcount = 0, authfailcount = 0, wehaveauthed = 1, wehavesentauthnote = 0, 
wedged = 0, 
  smtphost = 0x555b4040 "localhost", smtphostmode = 83 'S', smtp_socket = 
4, uid = 103, skipped = 0x0, oldsaved = {
pat_root = 0x555b41c0, records = 0x555dbd00, records_max = 2048, 
records_next = 1888, num_ndx = {records = 0x0, 
  pos_0_value = 4294967295, end_value = 4294967295}}, newsaved = {pat_root 
= 0x0, records = 0x555b4130, 
records_max = 16, records_next = 0, num_ndx = {records = 0x0, pos_0_value = 
4294967295, end_value = 4294967295}}, 
  lastdigest = '\000' , folder = 0x0, mimemsg = 1, digest = 
'\000' , next = 0x0}

Valgrind confirms:

==4368== Invalid write of size 4
==4368==at 0x10DDDA: pop3_delete (pop3.c:1374)
==4368==by 0x10DDDA: pop3_delete.cold.13 (pop3.c:1362)
==4368==by 0x11A9AF: fetch_messages (driver.c:812)
==4368==by 0x11A9AF: do_session (driver.c:1435)
==4368==by 0x11BDF8: do_protocol (driver.c:1677)
==4368==by 0x113B47: query_host (fetchmail.c:1546)
==4368==by 0x10E37A: main (fetchmail.c:793)
==4368==  Address 0x14 is not stack'd, malloc'd or (recently) free'd
==4368== 
==4368== 
==4368== Process terminating with default action of signal 11 (SIGSEGV)
==4368==  Access not within mapped region at address 0x14
==4368==at 0x10DDDA: pop3_delete (pop3.c:1374)
==4368==by 0x10DDDA: pop3_delete.cold.13 (pop3.c:1362)
==4368==by 0x11A9AF: fetch_messages (driver.c:812)
==4368==by 0x11A9AF: 

Bug#910442: marked as done (genshi FTBFS: tests fail: RuntimeError: generator raised StopIteration)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 21:49:46 +
with message-id 
and subject line Bug#910442: fixed in genshi 0.7.1-1
has caused the Debian Bug report #910442,
regarding genshi FTBFS: tests fail: RuntimeError: generator raised StopIteration
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.)


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

genshi fails to build from source in sbuild on unstable/amd64. A build
log ends with:

| ==
| FAIL: replace (genshi.filters.transform.Transformer)
| Doctest: genshi.filters.transform.Transformer.replace
| --
| Traceback (most recent call last):
|   File "/usr/lib/python3.7/doctest.py", line 2198, in runTest
| raise self.failureException(self.format_failure(new.getvalue()))
| AssertionError: Failed doctest test for 
genshi.filters.transform.Transformer.replace
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/filters/transform.py",
 line 368, in replace
| 
| --
| File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/filters/transform.py",
 line 374, in genshi.filters.transform.Transformer.replace
| Failed example:
| print((html | Transformer('.//title/text()').replace('New Title')))
| Exception raised:
| Traceback (most recent call last):
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/filters/transform.py",
 line 118, in __iter__
| event = next(self.stream)
| StopIteration
| 
| The above exception was the direct cause of the following exception:
| 
| Traceback (most recent call last):
|   File "/usr/lib/python3.7/doctest.py", line 1329, in __run
| compileflags, 1), test.globs)
|   File "", line 
1, in 
| print((html | Transformer('.//title/text()').replace('New Title')))
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/core.py", line 248, 
in __str__
| return self.render()
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/core.py", line 184, 
in render
| return encode(generator, method=method, encoding=encoding, out=out)
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/output.py", line 
57, in encode
| return _encode(''.join(list(iterator)))
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/output.py", line 
241, in __call__
| for kind, data, pos in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/output.py", line 
669, in __call__
| for kind, data, pos in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/output.py", line 
774, in __call__
| for kind, data, pos in chain(stream, [(None, None, None)]):
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/output.py", line 
594, in __call__
| for ev in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/core.py", line 289, 
in _ensure
| for event in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/core.py", line 289, 
in _ensure
| for event in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/filters/transform.py",
 line 706, in _unmark
| for mark, event in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/filters/transform.py",
 line 1076, in __call__
| for mark, event in stream:
| RuntimeError: generator raised StopIteration
| 
| 
| --
| Ran 861 tests in 0.443s
| 
| FAILED (failures=8, errors=56, skipped=1)
| Test failed: 
| error: Test failed: 
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python3.7 setup.py test 
| dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit 
code 13
| make: *** [debian/rules:8: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Could it be that this is due to Python 3.7 having become a supported
Python version?

Helmut
--- End Message ---
--- Begin Message ---
Source: genshi
Source-Version: 0.7.1-1

We believe that the bug you reported is fixed in the latest version of
genshi, 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 

Bug#787603: marked as done ([src:genshi] Some sources are not included in your package)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 21:49:46 +
with message-id 
and subject line Bug#787603: fixed in genshi 0.7.1-1
has caused the Debian Bug report #787603,
regarding [src:genshi] Some sources are not included in your package
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.)


-- 
787603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:genshi
version; 0.7-3
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package seems to include some files that lack sources
in prefered forms of modification:
examples/tutorial/geddit/static/jquery.js
  
According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution 
  in source code as well as compiled form.".

This could also constitute a license violation for some copyleft licenses such 
as the GNU GPL.

In order to solve this problem, you could:
1. repack the origin tarball adding the missing source to it.
2  add the source files to "debian/missing-sources" directory

Both way satisfies the requirement that we ship the source. Second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them, thus full 
filling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: genshi
Source-Version: 0.7.1-1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Feb 2019 11:42:17 -0200
Source: genshi
Binary: python-genshi python-genshi-dbgsym python-genshi-doc python3-genshi
Architecture: source amd64 all
Version: 0.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Herbert Parentes Fortes Neto 
Description:
 python-genshi - Python XML-based template engine - Python 2.x
 python-genshi-doc - Python XML-based template engine (documentation and 
examples)
 python3-genshi - Python XML-based template engine - Python 3.x
Closes: 787603 910442
Changes:
 genshi (0.7.1-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release (Closes: #910442)
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove Testsuite field, not needed anymore
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
 .
   [ Herbert Fortes ]
   * debian/control:
   - Bump Standards-Version from 3.9.6 to 4.3.0
   * debian/copyright:
   - Add myself to debian/
   - Files field for upstream first
   * debian/missing-sources:
   - examples/tutorial/geddit/static/jquery.js file
 already is a symlink to libjs-jquery. Add the
 sources (Closes: #787603)
   * debian/patches:
   - Remove issue566.patch. Fixed upstream.
   - Remove issue566.patch. Fixed upstream.
   - Remove issue602.patch. Fixed upstream.
   - Remove fix_tests_failure_with_python27.patch.
   * debian/python-genshi-doc.examples:
   - Remove 

Processed: severity of 920031 is serious

[Debian Bug Tracking System]

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

> severity 920031 serious
Bug #920031 [schleuder] schleuder: DEP8 failures with ruby-mail 2.7.1
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#915738: fixed in GCC

[Matthias Klose]

gcc-8 8.2.0-18 will have the upstream fix for that issue.

Bug#918858: marked as done (python-meep-*: fails to install: Exception: cannot get content of python-meep)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 21:35:26 +
with message-id 
and subject line Bug#918858: fixed in meep-openmpi 1.7.0-3
has caused the Debian Bug report #918858,
regarding python-meep-*: fails to install: Exception: cannot get content of 
python-meep
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.)


-- 
918858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 
python-meep-openmpi,python-meep-mpich2,python-meep-mpi-default,python-meep-lam4
Version: 1.7.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up python-meep-openmpi (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-openmpi (--configure):
   installed python-meep-openmpi package post-installation script subprocess 
returned error exit status 1

  Setting up python-meep-mpich2 (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-mpich2 (--configure):
   installed python-meep-mpich2 package post-installation script subprocess 
returned error exit status 1

  Setting up python-meep-mpi-default (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-mpi-default (--configure):
   installed python-meep-mpi-default package post-installation script 
subprocess 

Bug#921450: fetchmail: Fetchmail segfaults upon execution

[Sébastien Dinot]

Hi,

I have the same problem with the same version of fetchmail package.

I didn't find the fetchmail-dbgsym package, but here is what the
suggested command displays:


$ env LC_ALL=C fetchmail -v -v -v  --nodetach --nosyslog -b 2
Old UID list from mail.example.com:
 

Scratch list of UIDs:
 

fetchmail: removing stale lockfile
fetchmail: 6.4.0.beta4 querying mail.example.com (protocol POP3) at Tue Feb  5 
22:22:59 2019: poll started
Trying to connect to 12.34.56.78/110...connected.
fetchmail: POP3< +OK Dovecot (Debian) ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< AUTH-RESP-CODE
fetchmail: POP3< STLS
fetchmail: POP3< SASL
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< +OK Begin TLS negotiation now.
fetchmail: Certificate chain, from root to peer, starting at depth 2:
fetchmail: Issuer Organization: Digital Signature Trust Co.
fetchmail: Issuer CommonName: DST Root CA X3
fetchmail: Subject CommonName: DST Root CA X3
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: Digital Signature Trust Co.
fetchmail: Issuer CommonName: DST Root CA X3
fetchmail: Subject CommonName: Let's Encrypt Authority X3
fetchmail: Server certificate:
fetchmail: Issuer Organization: Let's Encrypt
fetchmail: Issuer CommonName: Let's Encrypt Authority X3
fetchmail: Subject CommonName: mail.example.com
fetchmail: Subject Alternative Name: mail.example.com
fetchmail: Subject Alternative Name: smtp.example.com
fetchmail: mail.example.com key fingerprint: 
A8:63:B2:92:47:25:A2:89:E5:00:09:F6:80:B2:47:D5
fetchmail: SSL/TLS: using protocol TLSv1.3, cipher TLS_AES_256_GCM_SHA384, 
256/256 secret/processed bits
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< AUTH-RESP-CODE
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: mail.example.com: upgrade to TLS succeeded.
fetchmail: POP3> USER me
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 22 262046
22 messages for me at mail.example.com (262046 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 474
fetchmail: POP3> RETR 1
fetchmail: POP3< +OK 474 octets
reading message m...@mail.example.com:1 of 22 (474 octets) About to rewrite 
Return-Path: ...
...rewritten version is Return-Path: .
About to rewrite From: Fail2Ban ...
...rewritten version is From: Fail2Ban .
About to rewrite To: r...@example.com...
...rewritten version is To: r...@example.com.
fetchmail: about to deliver with: /usr/bin/procmail -Y -d 'me'
#*** flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< +OK Marked to be deleted.
Segmentation fault

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

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 21:23:03 +
with message-id 
and subject line Bug#921364: fixed in node-active-x-obfuscator 0.0.2-2
has caused the Debian Bug report #921364,
regarding Not suitable for buster, package unmaintained
to be marked as done.

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

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


-- 
921364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-active-x-obfuscator
Version: 0.0.2-1
Severity: serious

Dear all,

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

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

light+love,
Mike


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

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

Versions of packages node-active-x-obfuscator depends on:
pn  node-zeparser  
ii  nodejs 4.8.2~dfsg-1

node-active-x-obfuscator recommends no packages.

node-active-x-obfuscator suggests no packages.
--- End Message ---
--- Begin Message ---
Source: node-active-x-obfuscator
Source-Version: 0.0.2-2

We believe that the bug you reported is fixed in the latest version of
node-active-x-obfuscator, 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.
Xavier Guimard  (supplier of updated node-active-x-obfuscator 
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: Tue, 05 Feb 2019 21:42:51 +0100
Source: node-active-x-obfuscator
Binary: node-active-x-obfuscator
Architecture: source
Version: 0.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 921364
Description: 
 node-active-x-obfuscator - Safely obfuscate the string 'ActiveX' inside of 
JavaScript code
Changes:
 node-active-x-obfuscator (0.0.2-2) unstable; urgency=medium
 .
   [ Mike Gabriel ]
   * debian/control: Drop myself from Uploaders: field.
 .
   [ Xavier Guimard ]
   * Bump debhelper compatibility level to 11
   * Declare compliance with policy 4.3.0
   * Change section to javascript
   * Change priority to optional
   * Update VCS fields to salsa
   * Update debian/copyright
   * Add upstream/metadata
   * Enable tests
   * Add myself to uploaders (Closes: #921364)
   * Fix install
Checksums-Sha1: 
 4f34d3698092e5ab2740c7f794043c5a2f5c09ff 2175 
node-active-x-obfuscator_0.0.2-2.dsc
 911d5c7bfebba124e9b73b629f4fb1ba73671577 2568 
node-active-x-obfuscator_0.0.2-2.debian.tar.xz
Checksums-Sha256: 
 fa1b07ddf30e9a65d5c89a292e12735bf6c48ad0650f4610b34898a06ad957fd 2175 
node-active-x-obfuscator_0.0.2-2.dsc
 d995d61315a318b60ad1de5ade63626ef5227f9900b7c45d1a65859da2484a8d 2568 
node-active-x-obfuscator_0.0.2-2.debian.tar.xz
Files: 
 ea05e6d1df5c2b572002bf833d2d3fa9 2175 javascript optional 
node-active-x-obfuscator_0.0.2-2.dsc
 db9329de4e81a3830f134a6584394175 2568 javascript optional 
node-active-x-obfuscator_0.0.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxZ9qgACgkQ9tdMp8mZ
7uktWg//S8Ghmfk8RWet5sYqhm125nWzeQFBun6NaS2T0Kfcm+0ASdN/sk+RnQBu
drsqmJJjA+pAeSzNkrlmUJPesF1VX0TlHfxenYbXqj3V5sZgCrpnaOrHsdUxNyiH
Iw7/QLcEutNtXiABtmnI0k5xU+z9Igl06xNbmV2OJoabJIR/axL5TM4jlPNxQWGf
GR741HCbp+4gRr/cJmVZMMtsG2TiTvHcY4geCpPGJ+JRg3yAtzi1lzFZ3S5w/oP7
O8liXBhi16Dvf04U8EkG/SZlAlr6Im5S4yGGO8L14CzwjMrla3lsZfZsdZV8X7dI
D3lbt7I74s3KwbMHa/VkufBAEPdkABL/+Q0/w5eMoDE8+z5EFJmOIdo/2s+F773c
T2dZqQbleTNvSUgw9r62VkQVGMfD+I44T4L/y1kt6vlkXlYBkv/43XvoN1D7BCzh
HI94iCwBbDoCxz/dd2jZ9FGbBtT/M0RzcpYMyNXLKBpbEVQAfb6QHCTWR5VpEYtG
Trxa8RP7TD9bwnitoa40QEiGyID3nphs7YvgfuVdgCNZckGUx1zfG6s7n6ALwXXV

Bug#909071: pbbam: FTBFS on every release architecture where it previously built (fwd)

[Adrian Bunk]

On Tue, Feb 05, 2019 at 12:06:22PM -0800, Steve Langasek wrote:
> On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> > And then there is the unrelated #908269 that currently prevents testing 
> > migration of pbbam.
> 
> > Steve seems to be addressing this with
> > http://launchpadlibrarian.net/409374477/pbbam_0.19.0+dfsg-1ubuntu3_0.19.0+dfsg-1ubuntu4.diff.gz
> 
> Yes, but the net result of this change is that now the autopkgtest fails by
> running out of memory during the package build at test time, which is why I
> haven't submitted a better patch to the BTS.
> 
> I think the ideal here would be to either have a way to generate just the
> single data file we need for the tests, or to capture that file from the
> package build and ship it in a binary package, so that we don't have to do a
> full rebuild during the autopkgtests.

The file is generated during configure, not build.

As proof of concept, it works to do

override_dh_auto_test: $(subst .t.in,.deb.t,$(wildcard tests/src/cram/pb*.t.in))
ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
dh_auto_configure -O--buildsystem=meson
...


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

Bug#909071: pbbam: FTBFS on every release architecture where it previously built (fwd)

[Andreas Tille]

On Tue, Feb 05, 2019 at 12:56:53PM -0800, Steve Langasek wrote:
> 
> Regardless, the autopkgtest problem is not amd64-specific, because at least
> for Ubuntu, we do not size our autopkgtest runners any differently on amd64
> than on other architectures.  Fixing the autopkgtest to not require a full
> source build for one data file would allow the autopkgtest to run (and
> likely succeed) on all available archs.

OK, I'll check tomorrow (by all means feel free to NMU since we are
quite close before freeze and if you find a solution that works on
Ubuntu for these packages I'm pretty sure it will work for Debian).
I'm too tired now and I'm not sure when I will manage tomorrow.

Thanks a lot for your patience

   Andreas.

-- 
http://fam-tille.de

Bug#920711: Test suite seems to uncover conflict between new version of tibble and repr (Was: Bug#920711: r-cran-repr: autopkgtest regression)

[Graham Inggs]

Hi!

On Tue, 5 Feb 2019 at 22:34, Andreas Tille  wrote:
> I can also add r-cran-tibble via
>
> apt-get install --no-install-recommends r-cran-tibble
>
> and the test suite keeps on succeeding!  However, after intalling
> r-cran-dplyr the described error occures while after deinstalling
> r-cran-dplyr the test suite passes again.  So the incompatibility
> seems to be rather between r-cran-repr and r-cran-dplyr.

The reason the two tests only fail when r-cran-dplyr is installed is because of:
if (has_dplyr) { }
in both cases [1][2].

Regards
Graham


[1] 
https://salsa.debian.org/r-pkg-team/r-cran-repr/blob/master/tests/testthat/test_array_manipulation.r#L226
[2] 
https://salsa.debian.org/r-pkg-team/r-cran-repr/blob/master/tests/testthat/test_array_manipulation.r#L249

Bug#909071: pbbam: FTBFS on every release architecture where it previously built (fwd)

[Steve Langasek]

On Tue, Feb 05, 2019 at 09:45:33PM +0100, Andreas Tille wrote:
> Hi Steve,

> On Tue, Feb 05, 2019 at 12:06:22PM -0800, Steve Langasek wrote:
> > On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> > > And then there is the unrelated #908269 that currently prevents testing 
> > > migration of pbbam.

> > > Steve seems to be addressing this with
> > > http://launchpadlibrarian.net/409374477/pbbam_0.19.0+dfsg-1ubuntu3_0.19.0+dfsg-1ubuntu4.diff.gz

> > Yes, but the net result of this change is that now the autopkgtest fails by
> > running out of memory during the package build at test time, which is why I
> > haven't submitted a better patch to the BTS.

> > I think the ideal here would be to either have a way to generate just the
> > single data file we need for the tests, or to capture that file from the
> > package build and ship it in a binary package, so that we don't have to do a
> > full rebuild during the autopkgtests.

> Thanks a lot for the time you have spent into this leaf package.  I
> think it is absolutely realistic that this package these days and also
> for the next couple of years will be practically used only on amd64
> architecture.  It might be sensible to draw a line here and simply
> declare this package and its rdepends "Architecture: amd64" and move on
> with problems that might affect more users and realistic applications
> for other architectures.

> What do you think?

I have no opinion.  I recognize that pretty much everyone working in this
domain is using x86, but I also know that Debian and Ubuntu run quite well
on both arm64 and ppc64el servers (the other two architectures pbbam
supports); and Amazon has recently announced ARM64 cloud instances which are
a fraction of the price of x86; so if I were the maintainer I would probably
leave these enabled.

Regardless, the autopkgtest problem is not amd64-specific, because at least
for Ubuntu, we do not size our autopkgtest runners any differently on amd64
than on other architectures.  Fixing the autopkgtest to not require a full
source build for one data file would allow the autopkgtest to run (and
likely succeed) on all available archs.

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


signature.asc
Description: PGP signature

Bug#909071: pbbam: FTBFS on every release architecture where it previously built (fwd)

[Adrian Bunk]

On Tue, Feb 05, 2019 at 09:45:33PM +0100, Andreas Tille wrote:
> Hi Steve,
> 
> On Tue, Feb 05, 2019 at 12:06:22PM -0800, Steve Langasek wrote:
> > On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> > > And then there is the unrelated #908269 that currently prevents testing 
> > > migration of pbbam.
> > 
> > > Steve seems to be addressing this with
> > > http://launchpadlibrarian.net/409374477/pbbam_0.19.0+dfsg-1ubuntu3_0.19.0+dfsg-1ubuntu4.diff.gz
> > 
> > Yes, but the net result of this change is that now the autopkgtest fails by
> > running out of memory during the package build at test time, which is why I
> > haven't submitted a better patch to the BTS.
> > 
> > I think the ideal here would be to either have a way to generate just the
> > single data file we need for the tests, or to capture that file from the
> > package build and ship it in a binary package, so that we don't have to do a
> > full rebuild during the autopkgtests.
> 
> Thanks a lot for the time you have spent into this leaf package.  I
> think it is absolutely realistic that this package these days and also
> for the next couple of years will be practically used only on amd64
> architecture.  It might be sensible to draw a line here and simply
> declare this package and its rdepends "Architecture: amd64" and move on
> with problems that might affect more users and realistic applications
> for other architectures.
> 
> What do you think?

All problems discussed are on amd64.

> Kind regards
> 
>   Andreas.

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

Bug#921364: Bug #921364 in node-active-x-obfuscator marked as pending

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #921364 in node-active-x-obfuscator reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-active-x-obfuscator/commit/f25e2379a25ac4ca39ad3ed50a677ee60d5bb04c


Add myself to uploaders

Closes: #921364


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/921364

Bug#909071: pbbam: FTBFS on every release architecture where it previously built (fwd)

[Andreas Tille]

Hi Steve,

On Tue, Feb 05, 2019 at 12:06:22PM -0800, Steve Langasek wrote:
> On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> > And then there is the unrelated #908269 that currently prevents testing 
> > migration of pbbam.
> 
> > Steve seems to be addressing this with
> > http://launchpadlibrarian.net/409374477/pbbam_0.19.0+dfsg-1ubuntu3_0.19.0+dfsg-1ubuntu4.diff.gz
> 
> Yes, but the net result of this change is that now the autopkgtest fails by
> running out of memory during the package build at test time, which is why I
> haven't submitted a better patch to the BTS.
> 
> I think the ideal here would be to either have a way to generate just the
> single data file we need for the tests, or to capture that file from the
> package build and ship it in a binary package, so that we don't have to do a
> full rebuild during the autopkgtests.

Thanks a lot for the time you have spent into this leaf package.  I
think it is absolutely realistic that this package these days and also
for the next couple of years will be practically used only on amd64
architecture.  It might be sensible to draw a line here and simply
declare this package and its rdepends "Architecture: amd64" and move on
with problems that might affect more users and realistic applications
for other architectures.

What do you think?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#920711: Test suite seems to uncover conflict between new version of tibble and repr (Was: Bug#920711: r-cran-repr: autopkgtest regression)

[Andreas Tille]

Hi Philipp,

On Tue, Feb 05, 2019 at 07:01:42PM +0100, Philipp Angerer wrote:
> Hi! Umm, why me? I’m neither the tibble author nor a Debian package
> maintainer :D

Sure you are not the Debian maintainer but the test case of repr
failes if latest r-cran-tibble Debian package is installed.  Thus
I was contacting you as the maintainer of the repr CRAN package.

However, the whole bug was misleading and I'm sorry about this.  Feel
free to ignore the following text in case you are swamped.  Anyway it
would be nice to know what happens on your side if you co-install
repr and dplyr on your side and run the repr test suite.

I tried to reproduce the issue and it seems the guess that the
r-cran-tibble upload happened before the regression of the test suite is
a bit vague.   I've created a clean chroot environment and installed
r-cran-repr into it.  Since r-cran-tibble is only in the dependency
graph of Recommended packages I tried without this package and the test
suite succeeds.  I can also add r-cran-tibble via

apt-get install --no-install-recommends r-cran-tibble

and the test suite keeps on succeeding!  However, after intalling
r-cran-dplyr the described error occures while after deinstalling
r-cran-dplyr the test suite passes again.  So the incompatibility
seems to be rather between r-cran-repr and r-cran-dplyr.

The only reason why r-cran-plyr is installed together with r-cran-tibble
is since it is in its Test-Depends (and thus also mentioned in
Recommends).  So the issue seems to boil down to some strange
incompatibility between r-cran-repr and r-cran-dplyr which occured right
after the upload of r-cran-tibble but not before.

Any help to sort this out is more than welcome.

Kind regards

Andreas.

> Andreas Tille  schrieb am Di., 5. Feb. 2019 um 10:36 Uhr:
> 
> > Hi Philipp,
> >
> > the continuous integration test in Debian has uncovered an issue after
> > tibble 2.0.0 was uploaded.  Please have a look below.  The full build
> > log can be found here:
> >
> >
> > https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-repr/1847462/log.gz
> >
> > (Please scroll down to the very bottom of that page!)
> >
> > Any hint how this can be solved?
> >
> > Kind regards
> >
> >Andreas.
> >
> > On Mon, Jan 28, 2019 at 04:24:10PM +0200, Graham Inggs wrote:
> > > 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/
> > >
> > > ___
> > > R-pkg-team mailing list
> > > r-pkg-t...@alioth-lists.debian.net
> > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team
> >
> > --
> > http://fam-tille.de
> >

-- 
http://fam-tille.de

Bug#921466: rust-rusty-tags: Section: FIXME-(source.section)

[Adrian Bunk]

Source: rust-rusty-tags
Version: 3.3.0-1
Severity: serious

https://tracker.debian.org/media/packages/r/rust-rusty-tags/control-3.3.0-1

Source: rust-rusty-tags
Section: FIXME-(source.section)
...


This is likely the reason why the buildds don't upload the built
packages and similar weirdnesses.

Processed: why3 FTBFS: dh_install: Cannot find (any matches for) "debian/tmp/usr/local/lib/ocaml/*/why3"

[Debian Bug Tracking System]

Processing control commands:

> block 918633 by -1
Bug #918633 {Done: Ralf Treinen } [why3-coq] why3-coq: 
package should Depend on a specific Coq version
918633 was not blocked by any bugs.
918633 was not blocking any bugs.
Added blocking bug(s) of 918633: 921465

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

Bug#921465: why3 FTBFS: dh_install: Cannot find (any matches for) "debian/tmp/usr/local/lib/ocaml/*/why3"

[Adrian Bunk]

Source: why3
Version: 1.1.1-3
Severity: serious
Tags: ftbfs
Control: block 918633 by -1

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

...
dh_install -a -XLICENSE
dh_install: Cannot find (any matches for) 
"debian/tmp/usr/local/lib/ocaml/*/why3" (tried in ., debian/tmp)

dh_install: libwhy3-ocaml-dev missing files: 
debian/tmp/usr/local/lib/ocaml/*/why3
dh_install: missing files, aborting
make[1]: *** [debian/rules:31: override_dh_install-arch] Error 25

Bug#909071: pbbam: FTBFS on every release architecture where it previously built (fwd)

[Steve Langasek]

On Tue, Feb 05, 2019 at 09:35:23AM +0200, Adrian Bunk wrote:
> And then there is the unrelated #908269 that currently prevents testing 
> migration of pbbam.

> Steve seems to be addressing this with
> http://launchpadlibrarian.net/409374477/pbbam_0.19.0+dfsg-1ubuntu3_0.19.0+dfsg-1ubuntu4.diff.gz

Yes, but the net result of this change is that now the autopkgtest fails by
running out of memory during the package build at test time, which is why I
haven't submitted a better patch to the BTS.

I think the ideal here would be to either have a way to generate just the
single data file we need for the tests, or to capture that file from the
package build and ship it in a binary package, so that we don't have to do a
full rebuild during the autopkgtests.

> On Tue, Feb 05, 2019 at 12:04:16AM +0200, Adrian Bunk wrote:
> > On Mon, Feb 04, 2019 at 04:36:22PM +0100, Andreas Tille wrote:
> > > Hi Adrian,
> > > 
> > > On Mon, Feb 04, 2019 at 01:06:35PM +0200, Adrian Bunk wrote:
> > > > >Bug#916576: pbdagcon: FTBFS pbdata/Types.h: No such file or 
> > > > > directory
> > > > > 
> > > > > I need to make some noise in the team since I'm definitely overworked
> > > > > with these pb* packages.  It might be that we will loose these for
> > > > > Buster. :-(
> > > > 
> > > > the patches for pbbam and pbdagcon should sort out most of the issues.
> > > 
> > > I've now uploaded the old upstream version of pbdagcon.  Unfortunately
> > > I can not see that pbbam has fixed the build issues[1] - thus I think
> > > #909071 needs to be re-opened.
> > >...
> > 
> > pbbam does now build on arm64/mips64el/ppc64el,
> > this is what #909071 fixed.
> > 
> > pbbam fails its tests on 32bit (#829741) and big endian,
> > these are expected failures that won't block migration.
> > 
> > But the pbdagcon build failure points at a bug in pbbam:
> > libpbbam0.19.0 is not ABI compatible with the stretch libpbbam,
> > so mustn't provide it.
> > 
> > The following changes should fix the latter problem:
> > - remove the Provides: libpbbam from libpbbam0.19.0
> > - remove manual dependencies on libpbbam from the following
> >   source packages (correct dependencies on libpbbam0.19.0
> >   are now generated):
> >   - blasr
> >   - pbdagcon
> >   - pbseqlib
> >   - unanimity
> > 
> > > Kind regards
> > > 
> > >   Andreas.
> > > 
> > > 
> > > [1] https://buildd.debian.org/status/package.php?p=pbbam 

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


signature.asc
Description: PGP signature

Processed: block 916369 with 919462

[Debian Bug Tracking System]

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

> block 916369 with 919462
Bug #916369 {Done: Benjamin Barenblat } [libcoq-ocaml] 
libcoq-ocaml depends and build-depends on cruft packages.
916369 was not blocked by any bugs.
916369 was not blocking any bugs.
Added blocking bug(s) of 916369: 919462
> thanks
Stopping processing here.

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

Processed: tagging 921459

[Debian Bug Tracking System]

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

> tags 921459 + buster sid
Bug #921459 [freefem3d] dead upstream - keep out of testing
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 921460

[Debian Bug Tracking System]

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

> tags 921460 + buster sid
Bug #921460 [clsparse] dead upstream - keep out of testing
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#918858: marked as done (python-meep-*: fails to install: Exception: cannot get content of python-meep)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 19:39:08 +
with message-id 
and subject line Bug#918858: fixed in meep-mpich2 1.7.0-3
has caused the Debian Bug report #918858,
regarding python-meep-*: fails to install: Exception: cannot get content of 
python-meep
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.)


-- 
918858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 
python-meep-openmpi,python-meep-mpich2,python-meep-mpi-default,python-meep-lam4
Version: 1.7.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up python-meep-openmpi (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-openmpi (--configure):
   installed python-meep-openmpi package post-installation script subprocess 
returned error exit status 1

  Setting up python-meep-mpich2 (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-mpich2 (--configure):
   installed python-meep-mpich2 package post-installation script subprocess 
returned error exit status 1

  Setting up python-meep-mpi-default (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-mpi-default (--configure):
   installed python-meep-mpi-default package post-installation script 
subprocess 

Bug#918074: marked as done (python-meep-mpich2 fails to install, postinst script looks for wrong package name.)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 19:39:08 +
with message-id 
and subject line Bug#918074: fixed in meep-mpich2 1.7.0-3
has caused the Debian Bug report #918074,
regarding python-meep-mpich2 fails to install, postinst script looks for wrong 
package name.
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.)


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

Package: python-meep-mpich2
Version: 1.7.0-2
Severity: serious

https://piuparts.debian.org/sid/fail/python-meep-mpich2_1.7.0-2.log


Setting up python-meep-mpich2 (1.7.0-2) ...
   dpkg-query: package 'python-meep' is not installed
   Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
   Traceback (most recent call last):
 File "/usr/bin/pycompile", line 289, in 
   main()
 File "/usr/bin/pycompile", line 262, in main
   options.force, options.optimize, e_patterns)
 File "/usr/bin/pycompile", line 154, in compile
   for fn, versions_to_compile in filter_files(files, e_patterns, versions):
 File "/usr/bin/pycompile", line 109, in filter_files
   for fn in files:
 File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
   for fn in files:
 File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
   for fn in files:
 File "/usr/share/python/debpython/files.py", line 69, in filter_public
   for fn in files:
 File "/usr/share/python/debpython/files.py", line 53, in from_package
   raise Exception("cannot get content of %s" % package_name)
   Exception: cannot get content of python-meep
   dpkg: error processing package python-meep-mpich2 (--configure):
installed python-meep-mpich2 package post-installation script subprocess 
returned error exit status 1
   Processing triggers for libc-bin (2.28-4) ...
   Errors were encountered while processing:
python-meep-mpich2
   E: Sub-process /usr/bin/dpkg returned an error code (1)

After some investigating it looks like this was caused by failing to update the 
package name in the postinst script when copying the python changes from the 
plain meep source package to the meep-mpich2 source package. The prerm script 
also seems to suffer from a similar issue.

While working on the above issues I also discovered that the clean target did 
not clean up properly, so I fixed that too.

A debdiff fixing that is attatched, no intent to NMU.


diff -Nru meep-mpich2-1.7.0/debian/changelog meep-mpich2-1.7.0/debian/changelog
--- meep-mpich2-1.7.0/debian/changelog  2018-12-25 15:29:02.0 +
+++ meep-mpich2-1.7.0/debian/changelog  2019-01-03 01:21:28.0 +
@@ -1,3 +1,9 @@
+meep-mpich2 (1.7.0-2+rpi1) buster-staging; urgency=medium
+
+  * Fix postinst script for python-meep-mpich2 to use correct package name.
+
+ -- Peter Michael Green   Thu, 03 Jan 2019 01:21:28 
+
+
 meep-mpich2 (1.7.0-2) unstable; urgency=medium
 
   * upload to unstable
diff -Nru meep-mpich2-1.7.0/debian/python-meep-mpich2.postinst 
meep-mpich2-1.7.0/debian/python-meep-mpich2.postinst
--- meep-mpich2-1.7.0/debian/python-meep-mpich2.postinst2018-12-23 
11:41:15.0 +
+++ meep-mpich2-1.7.0/debian/python-meep-mpich2.postinst2019-01-03 
01:19:17.0 +
@@ -2,7 +2,7 @@
 set -e
 
 if which pycompile >/dev/null 2>&1; then
-  pycompile -p python-meep
+  pycompile -p python-meep-mpich2
 fi
 
 #DEBHELPER#
diff -Nru meep-mpich2-1.7.0/debian/python-meep-mpich2.prerm 
meep-mpich2-1.7.0/debian/python-meep-mpich2.prerm
--- meep-mpich2-1.7.0/debian/python-meep-mpich2.prerm   2018-12-23 
11:41:15.0 +
+++ meep-mpich2-1.7.0/debian/python-meep-mpich2.prerm   2019-01-03 
01:21:28.0 +
@@ -2,7 +2,7 @@
 set -e
 
 if which pyclean >/dev/null 2>&1; then
-  pyclean -p python-meep 
+  pyclean -p python-meep-mpich2
 else
   dpkg -L python-meep | grep \.py$ | while read file
   do  
diff -Nru meep-mpich2-1.7.0/debian/rules meep-mpich2-1.7.0/debian/rules
--- meep-mpich2-1.7.0/debian/rules  2018-12-23 15:24:08.0 +
+++ meep-mpich2-1.7.0/debian/rules  2019-01-03 01:21:28.0 +
@@ -50,6 +50,7 @@
rm -f meep_mpi.pc
rm -f src/libmeep_mpi.la
dh_clean
+   rm -f scheme/meep_enum_renames.i scheme/meep_renames.i 
scheme/meep_swig_bug_workaround.i scheme/meep_wrap.cxx src/sphere-quad.h 
src/step_generic_stride1.cpp
 
 override_dh_auto_test:
echo ${arch}
--- End Message ---
--- Begin Message ---
Source: meep-mpich2
Source-Version: 1.7.0-3

Bug#918858: marked as done (python-meep-*: fails to install: Exception: cannot get content of python-meep)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 19:38:54 +
with message-id 
and subject line Bug#918858: fixed in meep-mpi-default 1.7.0-3
has caused the Debian Bug report #918858,
regarding python-meep-*: fails to install: Exception: cannot get content of 
python-meep
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.)


-- 
918858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 
python-meep-openmpi,python-meep-mpich2,python-meep-mpi-default,python-meep-lam4
Version: 1.7.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up python-meep-openmpi (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-openmpi (--configure):
   installed python-meep-openmpi package post-installation script subprocess 
returned error exit status 1

  Setting up python-meep-mpich2 (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-mpich2 (--configure):
   installed python-meep-mpich2 package post-installation script subprocess 
returned error exit status 1

  Setting up python-meep-mpi-default (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-mpi-default (--configure):
   installed python-meep-mpi-default package post-installation script 

Bug#921460: dead upstream - keep out of testing

[Ghislain Vaillant]

Le mar. 5 févr. 2019 à 20:21, Rebecca N. Palmer  a
écrit :

> Package: clsparse
> Severity: serious
> X-Debbugs-Cc: debian-scie...@lists.debian.org, ghisv...@gmail.com
> (plus an identical one for freefem3d)
>
> This package is dead upstream, and it has been suggested [0] that
> because of this, it should not be fixed for buster.
>
> I don't know enough about it to have an opinion on this: I am opening
> this bug as a "don't waste your time fixing it" notice.
>
> If this remains the consensus, please consider removing it from unstable
> as well.
>
> [0] https://lists.debian.org/debian-science/2019/02/msg00015.html


Agreed. It should be removed.

Ghislain

>
>

Bug#921459: dead upstream - keep out of testing

[Rebecca N. Palmer]

Package: freefem3d
Severity: serious

This package is dead upstream, and it has been suggested [0] that 
because of this, it should not be fixed for buster.


I don't know enough about it to have an opinion on this: I am opening 
this bug as a "don't waste your time fixing it" notice.


If this remains the consensus, please consider removing it from unstable 
as well.


[0] https://lists.debian.org/debian-science/2019/02/msg00015.html

Bug#659321: Fix for Gnome 3

[David D Lowe]

Hello folks,

Thank you for your efforts, bug reporting and triaging. I am the author of
ooo-thumbnailer and the Debian maintainer for this package. There have been
several barriers to continuing my work on it, and for this reason I will be
orphaning this package so that another maintainer can step in. I apologise
for the long delay.

On Tue, 5 Feb 2019 at 18:21, Adrian Bunk  wrote:

> On Fri, Feb 01, 2019 at 07:37:38PM +0100, Bruno Kleinert wrote:
> > Am Samstag, den 26.01.2019, 15:23 +0100 schrieb Bruno Kleinert:
> > > Hi David,
> > >
> > > please consider addressing this RC bug.
> > >
> > > Just to raise awareness: I plan to NMU with my previously attached
> > > patch around week 7.
> > >
> > > Cheers - Bruno
> >
> > Hi,
> >
> > I uploaded to the DELAYED=10 queue.
>
> I've rescheduled this for immediate upload.
>
> No special authority from my side, but if it isn't in testing on
> February 12th it won't be in buster.
>
> > Cheers - Bruno
>
> 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
>
>

Bug#921460: dead upstream - keep out of testing

[Rebecca N. Palmer]

Package: clsparse
Severity: serious
X-Debbugs-Cc: debian-scie...@lists.debian.org, ghisv...@gmail.com
(plus an identical one for freefem3d)

This package is dead upstream, and it has been suggested [0] that 
because of this, it should not be fixed for buster.


I don't know enough about it to have an opinion on this: I am opening 
this bug as a "don't waste your time fixing it" notice.


If this remains the consensus, please consider removing it from unstable 
as well.


[0] https://lists.debian.org/debian-science/2019/02/msg00015.html

Bug#918077: marked as done (python-meep-mpich2 fails to install, postinst script looks for wrong package name.)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 19:07:33 +
with message-id 
and subject line Bug#918077: fixed in meep-lam4 1.7.0-3
has caused the Debian Bug report #918077,
regarding python-meep-mpich2 fails to install, postinst script looks for wrong 
package name.
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.)


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

Package: python-meep-lam4
Version: 1.7.0-2
Severity: serious

https://piuparts.debian.org/sid/fail/python-meep-lam4_1.7.0-2.log

  Setting up python-meep-lam4 (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-lam4 (--configure):
   installed python-meep-lam4 package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.28-4) ...
  Errors were encountered while processing:
   python-meep-lam4
  E: Sub-process /usr/bin/dpkg returned an error code (1)



After some investigating it looks like this was caused by failing to update the 
package name in the postinst script
when copying the python changes from the plain meep source package to the 
meep-lam4 source package. The prerm
script also seems to suffer from a similar issue.

A debdiff fixing that is attatched, no intent to NMU.



diff -Nru meep-lam4-1.7.0/debian/changelog meep-lam4-1.7.0/debian/changelog
--- meep-lam4-1.7.0/debian/changelog2018-12-25 15:30:09.0 +
+++ meep-lam4-1.7.0/debian/changelog2019-01-03 02:10:44.0 +
@@ -1,3 +1,9 @@
+meep-lam4 (1.7.0-2+rpi1) buster-staging; urgency=medium
+
+  * Fix postinst and prerm scripts for python-meep-mpich2 to use correct 
package name.
+
+ -- Peter Michael Green   Thu, 03 Jan 2019 02:10:44 
+
+
 meep-lam4 (1.7.0-2) unstable; urgency=medium
 
   * upload to unstable
diff -Nru meep-lam4-1.7.0/debian/python-meep-lam4.postinst 
meep-lam4-1.7.0/debian/python-meep-lam4.postinst
--- meep-lam4-1.7.0/debian/python-meep-lam4.postinst2018-12-23 
11:39:19.0 +
+++ meep-lam4-1.7.0/debian/python-meep-lam4.postinst2019-01-03 
02:10:44.0 +
@@ -2,7 +2,7 @@
 set -e
 
 if which pycompile >/dev/null 2>&1; then
-  pycompile -p python-meep
+  pycompile -p python-meep-lam4
 fi
 
 #DEBHELPER#
diff -Nru meep-lam4-1.7.0/debian/python-meep-lam4.prerm 
meep-lam4-1.7.0/debian/python-meep-lam4.prerm
--- meep-lam4-1.7.0/debian/python-meep-lam4.prerm   2018-12-23 
11:39:19.0 +
+++ meep-lam4-1.7.0/debian/python-meep-lam4.prerm   2019-01-03 
02:10:44.0 +
@@ -2,7 +2,7 @@
 set -e
 
 if which pyclean >/dev/null 2>&1; then
-  pyclean -p python-meep 
+  pyclean -p python-meep-lam4
 else
   dpkg -L python-meep | grep \.py$ | while read file
   do  
--- End Message ---
--- Begin Message ---
Source: meep-lam4
Source-Version: 1.7.0-3

We believe that the bug you reported is fixed in the latest version of
meep-lam4, 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.
Thorsten Alteholz  (supplier of updated meep-lam4 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 

Bug#918858: marked as done (python-meep-*: fails to install: Exception: cannot get content of python-meep)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 19:07:33 +
with message-id 
and subject line Bug#918858: fixed in meep-lam4 1.7.0-3
has caused the Debian Bug report #918858,
regarding python-meep-*: fails to install: Exception: cannot get content of 
python-meep
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.)


-- 
918858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 
python-meep-openmpi,python-meep-mpich2,python-meep-mpi-default,python-meep-lam4
Version: 1.7.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up python-meep-openmpi (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-openmpi (--configure):
   installed python-meep-openmpi package post-installation script subprocess 
returned error exit status 1

  Setting up python-meep-mpich2 (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-mpich2 (--configure):
   installed python-meep-mpich2 package post-installation script subprocess 
returned error exit status 1

  Setting up python-meep-mpi-default (1.7.0-2) ...
  dpkg-query: package 'python-meep' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 289, in 
  main()
File "/usr/bin/pycompile", line 262, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/pycompile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/pycompile", line 109, in filter_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
  for fn in files:
File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
  for fn in files:
File "/usr/share/python/debpython/files.py", line 69, in filter_public
  for fn in files:
File "/usr/share/python/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-meep
  dpkg: error processing package python-meep-mpi-default (--configure):
   installed python-meep-mpi-default package post-installation script 
subprocess 

Bug#915311: dumb-init FTBFS on mips*: test failures

[Adrian Bunk]

On Sun, Dec 02, 2018 at 04:18:30PM -0800, Chris Kuehl wrote:
> Hi Adrian,
> 
> Thanks for filing this. I can't be certain, but I have a strong
> suspicion that this is caused by a bug that we fixed upstream with
> dumb-init 1.2.2 which was causing flakiness in the test suite on
> certain environments and architectures.
> 
> The bug was: https://github.com/Yelp/dumb-init/issues/136
> The patch was: https://github.com/Yelp/dumb-init/pull/174
> 
> If possible, I would suggest packaging the latest version of dumb-init
> (currently 1.2.2) as the easiest way to fix this.
> 
> Please let me know if there's any way we can help from the upstream side.

1.2.2 still fails:
https://buildd.debian.org/status/package.php?p=dumb-init
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dumb-init.html

Based on the (non)pattern of the failures I would suspect some kind of 
race condition (or timeout) that is more likely to hit on slow hardware.

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

Bug#921301: marked as done (starpu: FTBFS while building documentation)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 18:37:23 +
with message-id 
and subject line Bug#921301: fixed in starpu 1.2.6+dfsg-6
has caused the Debian Bug report #921301,
regarding starpu: FTBFS while building documentation
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.)


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

Dear Maintainer,

I tested your package against a draft package for doxygen 1.8.15:
https://bugs.debian.org/919413

and it FTBFS with this error:
mv: cannot stat 'latex/refman.pdf': No such file or directory

Paolo

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (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_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: starpu
Source-Version: 1.2.6+dfsg-6

We believe that the bug you reported is fixed in the latest version of
starpu, 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.
Samuel Thibault  (supplier of updated starpu 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: Tue, 05 Feb 2019 19:57:23 +0200
Source: starpu
Binary: libsocl-1.2-0 libsocl-1.2-0-dbgsym libstarpu-1.2-5 
libstarpu-1.2-5-dbgsym libstarpu-dev libstarpufft-1.2-0 
libstarpufft-1.2-0-dbgsym libstarpumpi-1.2-3 libstarpumpi-1.2-3-dbgsym 
starpu-examples starpu-examples-dbgsym starpu-tools starpu-tools-dbgsym 
starpu-top
Architecture: source
Version: 1.2.6+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 libsocl-1.2-0 - Task scheduler for heterogeneous multicore machines
 libstarpu-1.2-5 - Task scheduler for heterogeneous multicore machines
 libstarpu-dev - Task scheduler for heterogeneous multicore machines - dev
 libstarpufft-1.2-0 - Task scheduler for heterogeneous multicore machines
 libstarpumpi-1.2-3 - Task scheduler for heterogeneous multicore machines
 starpu-examples - Task scheduler for heterogeneous multicore machines - exs
 starpu-tools - Task scheduler for heterogeneous multicore machines - tools
 starpu-top - Task scheduler for heterogeneous multicore machines - top
Closes: 921301
Changes:
 starpu (1.2.6+dfsg-6) unstable; urgency=medium
 .
   * patches/doc-nopdf: Disable building pdf version of doxygen documentation
 (Closes: Bug#921301).
   * rules: Fix docdir.
Checksums-Sha1:
 4e089a1839683759141ceed71c8bead5b132f323 2941 starpu_1.2.6+dfsg-6.dsc
 835427f49b58487d9b2bd9b6505436c998648803 13652 
starpu_1.2.6+dfsg-6.debian.tar.xz
Checksums-Sha256:
 47e868af49b7a658d2a127231fd30bc805de1d0b901848b7836744f28fd6d142 2941 
starpu_1.2.6+dfsg-6.dsc
 049fe83a82354303599859e063742560c5f58ed090caf2879c61a0cd6af65821 13652 
starpu_1.2.6+dfsg-6.debian.tar.xz
Files:
 43730cbd53fddc17b7d77663218442d1 2941 libs optional starpu_1.2.6+dfsg-6.dsc
 c6a6f024471d9523570f40ef14c67bd0 13652 libs optional 
starpu_1.2.6+dfsg-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEM/p7ZGGVAfjOnI+X4/ZanpVg20wFAlxZ0+kACgkQ4/ZanpVg
20zYlw/9EvEhMKG6krbKnFegntYC4rkha+VZEfqX5KzdepEWnFmRcX7TFO82k2r8
uPfesiNGq/pxu7h/1N/p16kLiam0tMyzPzzCtMMr5wV10pj6gOOJMgjdWnx6G+yJ
gePe7aq40Lbd2LkNo5o7ySYNBHw2VS0PZDCmcHV3P1czF842jE+FBDZA/aBk+cdb
DsPnu7hRq37i2SD1iafAXxwj3LPdX/+vlYPvWwSBhlOSgAzgKMpKeka4phi/IegZ
WERDc4/tYXOWnw2KeIoY26pipTzBaJU/QCagFPSymJkiuCSXRNhbnJLaVMsGSk+o
IiMQ7aUkI+vxrKdMVpWzzJSB0yQpChl+NhWEmFrooO/qcnkcd6bdtvsCRTuWdRjc
c4/Vm0miVsJh+dCtbbb1g3PIf0NUepuHbW9t//aXLXIM3/Hqj8pQWNb5vDQXsfMo
Tyq7/4qp6oKPyne5kMVxi902Touj93LWkRV1PjIuzQlb/Er62kTEsIjIzUiQUd5d
tB8xx2rPNVu8WrDykgi7Xm0Z22El1btXqK7pz7A+Xr2bfDTndNT6jE6OHTWQpIei

Bug#921450: fetchmail: Fetchmail segfaults upon execution

[GCS]

Control: tags -1 +unreproducible moreinfo

Hi James,

On Tue, Feb 5, 2019 at 6:09 PM James Henried  wrote:
> fetchmail has stopped working in version 6.4.0~beta4-2.
 Which previous version did you use?

> Running the daemon gets the first mail in the queue delivered, but then it 
> segfaults.
 Please install fetchmail-dbgsym if it may give more information.

What happens if you stop the daemon and run it from the command line?
What's the output if it still fails?
Are you open to provide detailed log like the following produces?
$ env LC_ALL=C fetchmail -v -v -v  --nodetach --nosyslog -b 2

Thanks in advance,
Laszlo/GCS

Processed: Re: Bug#921450: fetchmail: Fetchmail segfaults upon execution

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: Re: Bug#921301: starpu: FTBFS with upcoming doxygen 1.8.15

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #921301 [src:starpu] starpu: FTBFS while building documentation
Added tag(s) pending.

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

Bug#921301: starpu: FTBFS with upcoming doxygen 1.8.15

[Samuel Thibault]

Control: tags -1 + pending

Hello,

Andreas Beckmann, le mar. 05 févr. 2019 10:54:49 +0100, a ecrit:
> Control: retitle -1 starpu: FTBFS while building documentation

Ok, I give up with building the pdf version, doxygen+latex is too much
of a hassle.

(FTR, Nathalie told me that the issue encountered by Andreas is
typically because the pdf generation does not manage to create
hyperlinks that are broken by a page break, which happens often with a
documentation with long function names).

Samuel

Bug#919583: marked as done (ebtables: broken symlinks: /sbin/ebtables{,-restore,-save} -> /usr/sbin/ebtables{,-restore,-save})

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 18:05:02 +
with message-id 
and subject line Bug#919583: fixed in ebtables 2.0.10.4+snapshot20181205-2
has caused the Debian Bug report #919583,
regarding ebtables: broken symlinks: /sbin/ebtables{,-restore,-save} -> 
/usr/sbin/ebtables{,-restore,-save}
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.)


-- 
919583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ebtables
Version: 2.0.10.4+snapshot20181205-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m33.7s ERROR: FAIL: Broken symlinks:
  /sbin/ebtables-restore -> /usr/sbin/ebtables-restore
  /sbin/ebtables-save -> /usr/sbin/ebtables-save
  /sbin/ebtables -> /usr/sbin/ebtables


cheers,

Andreas


ebtables_2.0.10.4+snapshot20181205-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ebtables
Source-Version: 2.0.10.4+snapshot20181205-2

We believe that the bug you reported is fixed in the latest version of
ebtables, 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.
Alberto Molina Coballes  (supplier of updated ebtables 
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 19:31:28 +
Source: ebtables
Architecture: source
Version: 2.0.10.4+snapshot20181205-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Alberto Molina Coballes 
Closes: 848948 918678 918787 919583
Changes:
 ebtables (2.0.10.4+snapshot20181205-2) unstable; urgency=medium
 .
   [ Alberto Molina Coballes ]
   * [d0a79d0] d/rules: include build architecture compiler (Closes: #848948)
   * [322fbda] Revert "d/rules: include build architecture compiler"
   * [25138b7] d/ebtables.prerm: iptables verification deleted (Closes: #919583)
   * [22208c6] d/control: Mark ebtables as 'Multi-Arch: foreign'
 (Closes: #918787)
   * [b739b36] d/ebtables-{save,restore}.8 renamed
 .
   [ Arturo Borrero Gonzalez ]
   * [a9cfc27] d/rules: make build verbose
   * [5e3d23f] d/stamp-autotools-files: delete file
 .
   [ Alberto Molina Coballes ]
   * [7a58bd0] ebtables: System V init script removed (Closes: #918678)
   * [9d015e9] ebtables: remove, disable and purge systemvinit script and
 systemd service
   * [1292475] d/README.Debian: add explanation about nftables migration
   * [de05c5e] d/patches: minor update
   * [b4d4f1e] d/control: bump std-version to 4.3.0
Checksums-Sha1:
 0d5abd56d63f74c156a2dd2a075c306fc6e003ef 2091 
ebtables_2.0.10.4+snapshot20181205-2.dsc
 ee19d5a562e9ed5c4c30e2df7c2d57bdb450e785 9536 
ebtables_2.0.10.4+snapshot20181205-2.debian.tar.xz
 94e521a93cb0379ca3273b2c5cf266821031a7ba 5433 
ebtables_2.0.10.4+snapshot20181205-2_amd64.buildinfo
Checksums-Sha256:
 31db68b27f1a84dfd4a45232833701e0f2b66007ef88c84294042fa79d970155 2091 
ebtables_2.0.10.4+snapshot20181205-2.dsc
 818dc3f77203596609233b6a6caa9cd4dfed234c53f5ab5162da6059dd137551 9536 
ebtables_2.0.10.4+snapshot20181205-2.debian.tar.xz
 3b50b8e6010e0678c0231840665e8eacdd6cec95575887e09ef17ff3b056d9a4 5433 
ebtables_2.0.10.4+snapshot20181205-2_amd64.buildinfo
Files:
 a6b9446214b6882b6d6fd15ba1b48382 2091 net optional 
ebtables_2.0.10.4+snapshot20181205-2.dsc
 537c93f05ebcb82a9f3b8beff033cee4 9536 net optional 
ebtables_2.0.10.4+snapshot20181205-2.debian.tar.xz
 332ef1f6029eda3d1734bcb98899a1d9 5433 net optional 
ebtables_2.0.10.4+snapshot20181205-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE3ZhhqyPcMzOJLgepaOcTmB0VFfgFAlxZzbwACgkQaOcTmB0V
Ffgznw/+IK7EZZXaL74W+OhHsFCGE5QHXWoIj1v9lJLye8vDf8ocbKn6tL6xQMRg
ZNBjFB7w7ig+mcwo8NN5qK2Hy4jt3x7LpFUJZU5dK2CgRkN+LV/AkI78Lno4A3eF
asJe8NMW0nwTZTGdyKg6hQF0lZc4xuK6B2qskRfuNhcJN0vrOF1OKihuGamVExtq
3oSsZqnQZavZweSUoWDN2ONqmLYsEHeMksUbUzat6vyrOiUNudeuRvqMvxv5JyCn
Bny55/rGg847U2rXqb2XR7JrNCdVOcfrdKpc/dfzaxkPu6QVgC1w+YzDm0Fq1nx3

Bug#914410: marked as done (ruby-validate-url FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 18:08:22 +
with message-id 
and subject line Bug#914410: fixed in ruby-validate-url 1.0.2+git-2
has caused the Debian Bug report #914410,
regarding ruby-validate-url FTBFS: 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.)


-- 
914410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-validate-url
Version: 1.0.2+git-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ruby-validate-url=all=1.0.2%2Bgit-1=1542891743=0

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=. 
GEM_PATH=debian/ruby-validate-url/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation

An error occurred while loading 
/<>/ruby-validate-url-1.0.2+git/spec/validate_url_spec.rb.
Failure/Error: require 'active_record'

LoadError:
  cannot load such file -- active_record
# /<>/ruby-validate-url-1.0.2+git/spec/spec_helper.rb:7:in `'
# /<>/ruby-validate-url-1.0.2+git/spec/validate_url_spec.rb:2:in 
`'
No examples found.

Finished in 0.00031 seconds (files took 0.18346 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/<>/ruby-validate-url-1.0.2\+git/debian/ruby-validate-url returned 
exit code 1
make: *** [debian/rules:7: binary-indep] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-validate-url
Source-Version: 1.0.2+git-2

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-validate-url 
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: Tue, 05 Feb 2019 17:44:00 +0100
Source: ruby-validate-url
Architecture: source
Version: 1.0.2+git-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Closes: 914410
Changes:
 ruby-validate-url (1.0.2+git-2) unstable; urgency=medium
 .
   * Team upload
   * Bump debhelper compatibility level to 11
   * Bump Standards-Version to 4.3.0 (no changes needed)
   * Build-depend on ruby-activerecord (Closes: #914410). Thanks Logan Rosen
 for the patch.
Checksums-Sha1:
 9435ec299ebfa0b1e05856ccaf46ef21a7e9fe29 1876 ruby-validate-url_1.0.2+git-2.dsc
 f4c340facbbf95d62946c8965ba1b1e8631ae946 2416 
ruby-validate-url_1.0.2+git-2.debian.tar.xz
 3003b3e3031aeff67e169be8067cfbced6075f3c 13886 
ruby-validate-url_1.0.2+git-2_source.buildinfo
Checksums-Sha256:
 21e5d41b7bd8a217b23e6a44430bedc392e5dbff3ead43e1370999f5e5506a35 1876 
ruby-validate-url_1.0.2+git-2.dsc
 4a97fcf4258cc7a576f439ce8ca5c2c1087311819456542eedd39181d11029c9 2416 
ruby-validate-url_1.0.2+git-2.debian.tar.xz
 0ddbcb237db9131c37424ef99af7d91893d5cc08e66c357c82be520734b1cbad 13886 
ruby-validate-url_1.0.2+git-2_source.buildinfo
Files:
 4c506ca6ef788825a74072131d0c8d98 1876 ruby optional 
ruby-validate-url_1.0.2+git-2.dsc
 46c64cca8f5318f653d97f6181aca18b 2416 ruby optional 
ruby-validate-url_1.0.2+git-2.debian.tar.xz
 b042f6464b0546b0d17c856bb6fb4b5c 13886 ruby optional 
ruby-validate-url_1.0.2+git-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlxZyU8ACgkQia+CtznN
IXrjjQf/dCcNz+Ia9l10b8X6sWRulbHWCoG3I8OP4SCagfO+Auf9ktGD3juHw9gM
ZIcUEBpwmj0VY1u4W9ZM7NBE8yB6Jv+TcTYecslTx5zy7+rLhZGQGCgvba6X10ml

Bug#920711: Test suite seems to uncover conflict between new version of tibble and repr (Was: Bug#920711: r-cran-repr: autopkgtest regression)

[Philipp Angerer]

Hi! Umm, why me? I’m neither the tibble author nor a Debian package
maintainer :D

Andreas Tille  schrieb am Di., 5. Feb. 2019 um 10:36 Uhr:

> Hi Philipp,
>
> the continuous integration test in Debian has uncovered an issue after
> tibble 2.0.0 was uploaded.  Please have a look below.  The full build
> log can be found here:
>
>
> https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-repr/1847462/log.gz
>
> (Please scroll down to the very bottom of that page!)
>
> Any hint how this can be solved?
>
> Kind regards
>
>Andreas.
>
> On Mon, Jan 28, 2019 at 04:24:10PM +0200, Graham Inggs wrote:
> > 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/
> >
> > ___
> > R-pkg-team mailing list
> > r-pkg-t...@alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team
>
> --
> http://fam-tille.de
>

Bug#921176: redis-server service is failing to start in buster lxc container

[Chris Lamb]

severity 921176 serious
thanks

Hi Pirate,

[Dropping severity as it only affects LXC right now]

> It is working on the same host machine with stretch(-backports)
> container (5:5.0.3-3~bpo9+2). So host machine seems fine.

Thanks for looking into this and providing some LXC basics.
(However, I am not sure why I do not have working networking inside
my container so I cannot debug it better on my end.)

On the other hand, the first thing I would do if this was working
would be to try removing more hardening features as previously
discussed on this bug number until it (likely) worked. Could you
try this please?

Also, perhaps enable some deeper logging? Or check the actual
redis-server.log file too?


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Processed: Re: redis-server service is failing to start in buster lxc container

[Debian Bug Tracking System]

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

> severity 921176 serious
Bug #921176 [redis-server] redis-server service is failing to start in buster 
lxc container
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Bug#914410: Bug #914410 in ruby-validate-url marked as pending

[Cédric Boutillier]

Control: tag -1 pending

Hello,

Bug #914410 in ruby-validate-url 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/ruby-validate-url/commit/d363a5532add438c926963131c99811a5d755c53


Build-depend on ruby-activerecord (Closes: #914410)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/914410

Bug#659321: Fix for Gnome 3

[Adrian Bunk]

On Fri, Feb 01, 2019 at 07:37:38PM +0100, Bruno Kleinert wrote:
> Am Samstag, den 26.01.2019, 15:23 +0100 schrieb Bruno Kleinert:
> > Hi David,
> > 
> > please consider addressing this RC bug.
> > 
> > Just to raise awareness: I plan to NMU with my previously attached
> > patch around week 7.
> > 
> > Cheers - Bruno
> 
> Hi,
> 
> I uploaded to the DELAYED=10 queue.

I've rescheduled this for immediate upload.

No special authority from my side, but if it isn't in testing on 
February 12th it won't be in buster.

> Cheers - Bruno

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

Bug#659321: marked as done (ooo-thumbnailer: No thumbnail generated in Gnome 3 Nautilus)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 17:19:29 +
with message-id 
and subject line Bug#659321: fixed in ooo-thumbnailer 0.2-5.1
has caused the Debian Bug report #659321,
regarding ooo-thumbnailer: No thumbnail generated in Gnome 3 Nautilus
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.)


-- 
659321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ooo-thumbnailer
Version: 0.5-1
Severity: important

Dear Maintainer,

In latest version of testing (0.2), no thumbnail is generated for any 
LibreOffice/OpenOffice documents.

I’ve updated with latest file from launchpad, and after compilation of the deb 
package and installation, it works fine.

I believe the /usr/share/thumbnailer/ooo-thumbnailer.thumbnailer is missing in 
previous version which explains why it doesn’t work with Gnome 3 Nautilus.

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

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ooo-thumbnailer depends on:
ii  file 5.09-2
ii  gconf2   2.32.4-1
ii  imagemagick  8:6.6.9.7-5+b2
ii  libgsf-bin   1.14.21-2
ii  unzip6.0-5

ooo-thumbnailer recommends no packages.

Versions of packages ooo-thumbnailer suggests:
ii  libreoffice-calc 1:3.4.5-2
ii  libreoffice-draw 1:3.4.5-2
ii  libreoffice-impress  1:3.4.5-2
ii  libreoffice-writer   1:3.4.5-2

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: ooo-thumbnailer
Source-Version: 0.2-5.1

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

Debian distribution maintenance software
pp.
Bruno Kleinert  (supplier of updated ooo-thumbnailer 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: Fri, 01 Feb 2019 19:14:09 +0100
Source: ooo-thumbnailer
Binary: ooo-thumbnailer
Architecture: source all
Version: 0.2-5.1
Distribution: unstable
Urgency: medium
Maintainer: David D Lowe 
Changed-By: Bruno Kleinert 
Description:
 ooo-thumbnailer - thumbnailer for OpenOffice.org documents
Closes: 659321
Changes:
 ooo-thumbnailer (0.2-5.1) unstable; urgency=medium
 .
   [ Bruno Kleinert ]
   * Non-maintainer upload.
   * Fix no thumbnail generated in Gnome 3 Nautilus (Closes: #659321)
 - Don't install gconf2 scheme and remove call to dh_gconf in debian/rules.
   This also removes the dependency on gconf2.
 - Install /usr/share/thumbnailers/ooo.thumbnailer which replaces the
   gconf2 scheme.
Checksums-Sha1:
 981f8599718ca98b89b13a10db569de06661373a 1715 ooo-thumbnailer_0.2-5.1.dsc
 5187720ff8d9e8843cb29b83f812e82b749da909 2442 ooo-thumbnailer_0.2-5.1.diff.gz
 84919611c80d5ec4748672fa036c915e46519d90 4932 ooo-thumbnailer_0.2-5.1_all.deb
 4bbf9bc6f7c68f830fff8571e52563c8f78f57c5 5373 
ooo-thumbnailer_0.2-5.1_amd64.buildinfo
Checksums-Sha256:
 21f56d6478ccbace9c2742348266466d032f42f8b62cf947e1bddbea94981a8e 1715 
ooo-thumbnailer_0.2-5.1.dsc
 b39e9f9929924f0553b887f4f20cf73d5878ead87910991e80bb77fa10838a59 2442 
ooo-thumbnailer_0.2-5.1.diff.gz
 15a63ad0876b548d2bd53f0ef6f46f02d6c4e180f89aafadb36da3c157a8cc0f 4932 
ooo-thumbnailer_0.2-5.1_all.deb
 f045ea3b5977ca5700eab77b75c9c1133a9afbd855643ee325306fc1e787c6de 5373 
ooo-thumbnailer_0.2-5.1_amd64.buildinfo
Files:
 5a9d381160ddfcfcd6eebdc55c18a39a 1715 gnome optional 
ooo-thumbnailer_0.2-5.1.dsc
 490f370ac753d4fd58d322a38c6f549e 2442 gnome optional 
ooo-thumbnailer_0.2-5.1.diff.gz
 df1c6ec336b62768d631f2887a9725a2 4932 gnome optional 
ooo-thumbnailer_0.2-5.1_all.deb
 591417c8b0e2b97351d2fa99e30aa0ed 5373 gnome optional 
ooo-thumbnailer_0.2-5.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbNBoYg3hPRuThXIzSwBpzPZSeEcFAlxUjwEACgkQSwBpzPZS
eEexag//XBSY7YY04Or/3Xkg4fNElvBS18I6cUd9rsk7F00ENtBd0pOE59zFjEts
g0GNEjLUizjuG/Kt0/9qPfCVU4AkEcq46iVvwcAXGbvcoPZDl59dG4w6ISUVPRhT

Bug#921450: fetchmail: Fetchmail segfaults upon execution

[James Henried]

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

Bug#918858: python-meep-*: fails to install: Exception: cannot get content of python-meep

[Thorsten Alteholz]

Thanks a lot for the reference to $DPKG_MAINTSCRIPT_PACKAGE, an updated 
package is on its way ...


 Thorsten

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

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 15:49:33 +
with message-id 
and subject line Bug#921371: fixed in node-log4js 4.0.2-1
has caused the Debian Bug report #921371,
regarding Not suitable for buster, package probably unmaintained
to be marked as done.

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

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


-- 
921371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-log4js
Version: 0.6.18-1
Severity: serious

Dear all,

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

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

light+love,
Mike


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

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

Versions of packages node-log4js depends on:
ii  node-async  0.8.0-1
ii  nodejs  4.8.2~dfsg-1

node-log4js recommends no packages.

node-log4js suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: node-log4js
Source-Version: 4.0.2-1

We believe that the bug you reported is fixed in the latest version of
node-log4js, 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.
Xavier Guimard  (supplier of updated node-log4js 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: Tue, 05 Feb 2019 16:34:44 +0100
Source: node-log4js
Binary: node-log4js
Architecture: source
Version: 4.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard 
Changed-By: Xavier Guimard 
Closes: 921371
Description: 
 node-log4js - Conversion of the log4js framework to work with Node.js
Changes:
 node-log4js (4.0.2-1) unstable; urgency=medium
 .
   [ Mike Gabriel ]
   * debian/control: Drop myself from Uploaders: field.
 .
   [ Xavier Guimard ]
   * Bump debhelper compatibility level to 11
   * Declare compliance with policy 4.3.0
   * Change section to javascript
   * Change priority to optional
   * Add myself to uploaders (Closes: #921371)
   * Update VCS fields to salsa
   * Update debian/copyright
   * New upstream version 4.0.2
   * Install components: rfdc, flatted, streamroller and date-format
   * Add upstream/metadata
   * Drop patches
   * Add node-debug, node-fs-extra and node-lodash in dependencies
   * Update debian/install
   * Enable upstream tests
   * Remove test from docs
   * Update debian/copyright
   * Hide min.js lintian errors: file is not installed
Checksums-Sha1: 
 09e5fc1cfca030c461333cf64a7d3404c3f287cb 3176 node-log4js_4.0.2-1.dsc
 7cf7b172f1ec564f0003b39ea302c5498fb98c8f 4935 
node-log4js_4.0.2.orig-date-format.tar.gz
 55122b6536ea496b4b44893ee2608141d10d9916 3936 
node-log4js_4.0.2.orig-flatted.tar.gz
 e6e72d74f5dc39de8f538f65e00c36c18018e349 3174 
node-log4js_4.0.2.orig-rfdc.tar.gz
 6771c9c750638e3ad9de93781d431a05514eeb2f 13231 
node-log4js_4.0.2.orig-streamroller.tar.gz
 e61cf245c28e13db2c0774adf1a07f13667d7c30 122935 node-log4js_4.0.2.orig.tar.gz
 11e5069136d09ca008ca4e79f003519f43880984 4320 node-log4js_4.0.2-1.debian.tar.xz
Checksums-Sha256: 
 69564f701742aad90eeef892a122f11a4bf2ee028df62337bf6b837a8cfb271a 3176 
node-log4js_4.0.2-1.dsc
 33487ba316c29c53639fd8ae3083f55dece23de69c2d360b26a1ad1e67ea55bd 4935 
node-log4js_4.0.2.orig-date-format.tar.gz
 f23e225b94d518a5ac9c3f81f38e7d8b03dac05f9c1669624563fc186e778ecf 3936 
node-log4js_4.0.2.orig-flatted.tar.gz
 60852b89f86df8ae51fccfaef22aa92942a88bb9fc80da34735641886d6a190d 3174 
node-log4js_4.0.2.orig-rfdc.tar.gz
 ea7df68d7b7d34b003921271f2af55a00a5aa287d88d7654d339ec2ac22f108b 13231 
node-log4js_4.0.2.orig-streamroller.tar.gz
 

Bug#921443: ddnet FTBFS on architectures where char is unsigned

[Adrian Bunk]

Source: ddnet
Version: 11.7.2-1
Severity: serious
Tags: ftbfs

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

...
/usr/bin/c++  -DCONF_AUTOUPDATE -DCONF_OPENSSL -DCONF_SQL -DCONF_WEBSOCKETS 
-DGLEW_STATIC -D_FORTIFY_SOURCE=2 -I/<>/obj-aarch64-linux-gnu/src 
-I/<>/src -I/usr/include/mariadb  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -O3 -Wdate-time -D_FORTIFY_SOURCE=2   
-fstack-protector-all -Wall -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers -Wformat=2 -std=gnu++11 -o 
CMakeFiles/testrunner.dir/src/test/str.cpp.o -c 
/<>/src/test/str.cpp
/<>/src/test/str.cpp: In member function 'virtual void 
Str_Utf8ToLower_Test::TestBody()':
/<>/src/test/str.cpp:70:28: error: narrowing conversion of '-128' 
from 'int' to 'char' inside { } [-Wnarrowing]
  const char a[2] = {-128, 0};
^
make[5]: *** [CMakeFiles/testrunner.dir/build.make:183: 
CMakeFiles/testrunner.dir/src/test/str.cpp.o] Error 1

Bug#920524: marked as done (valabind: valabind does not start, libvalaccodegen.so not found.)

[Debian Bug Tracking System]

Your message dated Tue, 05 Feb 2019 15:34:57 +
with message-id 
and subject line Bug#920524: fixed in valabind 1.7.0-1
has caused the Debian Bug report #920524,
regarding valabind: valabind does not start, libvalaccodegen.so not found.
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.)


-- 
920524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: valabind
Version: 1.5.0-3
Severity: serious

Dear Maintainer,

when trying to run valabind, I get:

,
| $ valabind
| valabind: error while loading shared libraries: libvalaccodegen.so:
| cannot open shared object file: No such file or directory
`

valac/0.42.5-1 ships the shared library but it is not installed into a
standard directory:

,
| valac: /usr/lib/x86_64-linux-gnu/vala-0.42/libvalaccodegen.so
`

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Source: valabind
Source-Version: 1.7.0-1

We believe that the bug you reported is fixed in the latest version of
valabind, 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.
Sebastian Reichel  (supplier of updated valabind 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 15:44:42 +0100
Source: valabind
Binary: valabind valabind-dbgsym
Architecture: source amd64
Version: 1.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Reichel 
Changed-By: Sebastian Reichel 
Description:
 valabind   - converts vapi files to SWIG, C++, GIR or GEAR files
Closes: 920524
Changes:
 valabind (1.7.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
 .
   [ Sebastian Reichel ]
   * New upstream release
   * Switch to meson build system
   * Add patches to fix meson build system
   * Add tight dependency for valac, which contains a private library
 used by valabind. Upstream vala and valabind people should find
 a better solution for this, but for now this hack gets things
 running (Closes: #920524)
   * Bump Standards-Version to 4.3.0
   * Fix Upstream URL in copyright file
   * Bump compat level to 12
   * Add manpage
Checksums-Sha1:
 14ea95f2770031e153d910234d15675b6114f867 1878 valabind_1.7.0-1.dsc
 35c8efea5d207fc881d4e214224082f50029fa2c 58143 valabind_1.7.0.orig.tar.gz
 a4be5780de93c50a63b73e226119bcf89df0d6b2 5996 valabind_1.7.0-1.debian.tar.xz
 51c3474647ba3fc82b3b9312a7f84d92979f21df 409068 
valabind-dbgsym_1.7.0-1_amd64.deb
 8edf2d1dcbdefdddac8b71e87e7dd21524f5f5b4 6987 valabind_1.7.0-1_amd64.buildinfo
 2bb9d8750358f7595a50e26a381250d4f6a47592 71828 valabind_1.7.0-1_amd64.deb
Checksums-Sha256:
 1b900b9da792d1d4c78679a49f50b667bb84636407badc303d2a73da470b55c7 1878 
valabind_1.7.0-1.dsc
 8a8db4ddd664f3f1ec65ca5d32784e3912e75df791c0a400d557a617da1a2fa7 58143 
valabind_1.7.0.orig.tar.gz
 72d2245e0ce7408bde0d62990e58ee1aacab9acb5b4f68dc5e94a14a49168fae 5996 
valabind_1.7.0-1.debian.tar.xz
 22c1d3bcf3b14b39d4c6a3e0cc68ab08b90f9806bd8538b8ac917639ad51c248 409068 
valabind-dbgsym_1.7.0-1_amd64.deb
 c30b8f50f34ef45d8be54190f1e74e474d7737e9c059856a917ad2128d8e7167 6987 
valabind_1.7.0-1_amd64.buildinfo
 8dd8ef7756724cf45d3c5cf549db4649372b275bb92183fa8f886731b42e1db8 71828 
valabind_1.7.0-1_amd64.deb
Files:
 af0d349aa7760c3f05062994423737a0 1878 devel optional valabind_1.7.0-1.dsc
 0745bfc6a936a0aba0bd41ba13afed44 58143 devel optional 
valabind_1.7.0.orig.tar.gz
 0af282405278f5db910f5dbbcd19bced 5996 devel optional 
valabind_1.7.0-1.debian.tar.xz
 8d4a41888f5f0c9cb19335cd567b3b4d 409068 debug optional 
valabind-dbgsym_1.7.0-1_amd64.deb
 042be2da3114ae0fa3562427c1a64ca3 6987 devel optional 
valabind_1.7.0-1_amd64.buildinfo
 59b1ff1e1a3f56499bb4666957bf7f87 71828 devel optional 
valabind_1.7.0-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAlxZpzgPHHNyZUBkZWJp
YW4ub3JnAAoJENju1/PIO/qaixwQAJBoEVTCPYA3IBn+acMF1fvg53p32fJDDloy
QiedyfUvpx+tncpOFiGQb6x4hD1lah0HkeVNLa5iUv+pJsPVZDvdy2/R/0bitpvF
F0YvbsEyiLYmXEqn8qPGwfcSp+y9qOmwqfyD4QgJ1FgF8ep0WMvIMhiyQ0m+CaIJ