Bug#916324: marked as done (i3pystatus: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 06:49:49 +
with message-id 
and subject line Bug#916324: fixed in i3pystatus 3.35~git20180925.a586a50-2
has caused the Debian Bug report #916324,
regarding i3pystatus: Incomplete debian/copyright?
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.)


-- 
916324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: i3pystatus
Version: 3.35~git20180925.a586a50-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Esteban Bosse , 
ftpmas...@debian.org

Hi,

I just ACCEPTed i3pystatus from NEW but noticed it was missing 
attribution in debian/copyright for at least the BSD licnese
in i3pystatus/scratchpad.py.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: i3pystatus
Source-Version: 3.35~git20180925.a586a50-2

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

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

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

Debian distribution maintenance software
pp.
Esteban Bosse  (supplier of updated i3pystatus 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: Sun, 16 Dec 2018 13:56:23 -0300
Source: i3pystatus
Binary: i3pystatus
Architecture: source all
Version: 3.35~git20180925.a586a50-2
Distribution: unstable
Urgency: medium
Maintainer: Esteban Bosse 
Changed-By: Esteban Bosse 
Description:
 i3pystatus - Large collection of status modules compatible with i3bar
Closes: 916324 916339
Changes:
 i3pystatus (3.35~git20180925.a586a50-2) unstable; urgency=medium
 .
   [ Estebanb ]
   * Fix section in debian control. (Closes: #916339)
   * Update missing copyright. (Closes: #916324)
Checksums-Sha1:
 5bdc7e930e3207ba9099b0ff16f7de3ca47d25d7 2092 
i3pystatus_3.35~git20180925.a586a50-2.dsc
 c402f0c0d233390779c8fca847567ba65a48fce9 3588 
i3pystatus_3.35~git20180925.a586a50-2.debian.tar.xz
 ed5a94c12c9dc60106f7d9ef9066b4fa4c9b8f86 124556 
i3pystatus_3.35~git20180925.a586a50-2_all.deb
 1bdd0fa441cfd4691f42de312b555204c67a2b96 6106 
i3pystatus_3.35~git20180925.a586a50-2_amd64.buildinfo
Checksums-Sha256:
 022f001c2f1fa2cd7d0ffbadd99158f64cd680769f2fdc6471bc5d9daf10 2092 
i3pystatus_3.35~git20180925.a586a50-2.dsc
 b0dca9362b58f4336e95575a8bd00b5efe5c8c35d84aef845f48d1deb25e1956 3588 
i3pystatus_3.35~git20180925.a586a50-2.debian.tar.xz
 54b4e8c135c6853c35b47ae0ae8433824702c5d67674753f9f75f4eb8c4f0eaa 124556 
i3pystatus_3.35~git20180925.a586a50-2_all.deb
 bd02890cdfeedde26f8f907b9c58369c3521a41d86dd0f36320176c7f2527711 6106 
i3pystatus_3.35~git20180925.a586a50-2_amd64.buildinfo
Files:
 5687d49014e0512fd182a1ad7a246c9c 2092 x11 optional 
i3pystatus_3.35~git20180925.a586a50-2.dsc
 5d623ac4ce6d669743fc2e8453ba51ad 3588 x11 optional 
i3pystatus_3.35~git20180925.a586a50-2.debian.tar.xz
 da3a894c2f758b002039180d62a10131 124556 x11 optional 
i3pystatus_3.35~git20180925.a586a50-2_all.deb
 f14c15bf04c90ec2d312c77146df94eb 6106 x11 optional 
i3pystatus_3.35~git20180925.a586a50-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEd4G8WDJexuSWyvTtAihSEHiQOPIFAlwYkyMACgkQAihSEHiQ
OPKHXg//eYAVlUTLcRKZtUsMxAenKoaZBdTxXlvrRVHXF8kvZ/eq8uZF2dsjD8uU
6lrxFwx5aNfawg4Y/NXFW/pMoiuadtNSOaBijWQFnq12698XeQcnJgJESSX7Or0u
cbiNRtnEQ74so6qB1pmKpgOwktKqWUqNvkOC1jY8WlK3uQHCcC2KNYWDXkCoh761
cfPlnjJK2vIJZhS2x4n7p+ho+whC+p+TENPaL2EnkkFOud5sPUt8vPM10TNoxwne
/lvwJoy2fHQ+J70Mvu9/HolegsGduZoJv3gGrp0ZJRnoxbu/9a7kjOAYjEWo5f0d
ioeMJ1iQli7oGgN/8RD9iUjcljDFGEOkyw5AsNMPgrd4LuRQKB1BC0tMYZIqTNk8
u++IGnwRA3PqE6TKC4Uc7q/IwzAqcgBHXPhnYl9qH43ScwTaxeZZCI5o4PTA9P6O
Ta7ghgLmxHeyidM8gBX9QF1sBJxSWPJBg1PmL+EJ4KPn9kIQ5tkrgeugc7jOIjEX
U9lKqfBkJ7npLTXwXXZT16cUXE4vaAT5GsipQLcBcRvmde5Pq5jqFhiljN0/309X
xOYq9Vb43/whqz8/SRhF9utz8Cv7r3CbRO5S5ZK/4rFix8u2avok8aSFHn9z+N/c
+b13qLLdPDClxdNUnVE0koh3vKGQTW/JLacc7mkbrqyiXc6Dcvw=
=B+EQ
-END PGP SIGNATURE End Message ---

Bug#789008: At least on Debian testing it upgraded without an issue.

[shirish शिरीष]

Dear all,

At least here it updated without any issues -

$ sudo aptitude install insserv -y
The following packages will be upgraded:
  insserv
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/64.7 kB of archives. After unpacking 8,192 B will be used.
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of insserv (1.14.0-5.4+b1 → 1.18.0-1) 
 b1 - #738775 - insserv: Insserv 1.16 tries to connect to systemd even
though system is running on sysv-init
   Merged with: 740459 741705
 b2 - #746170 - insserv: Still fails due to rpcbind/nfs
   Merged with: 789008
Summary:
 insserv(2 bugs)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] y
apt-listchanges: Mailing root: apt-listchanges: changelogs for debian
(Reading database ... 513126 files and directories currently installed.)
Preparing to unpack .../insserv_1.18.0-1_amd64.deb ...
Unpacking insserv (1.18.0-1) over (1.14.0-5.4+b1) ...
Processing triggers for man-db (2.8.4-3) ...
Setting up insserv (1.18.0-1) ...
==  How can you help?  (doc: https://wiki.debian.org/how-can-i-help ) ==

-  Show old opportunities as well as new ones: how-can-i-help --old  -
Scanning processes...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

Package: insserv
Version: 1.18.0-1
Severity: normal

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

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

Versions of packages insserv depends on:
ii  libc6  2.28-2

insserv recommends no packages.

Versions of packages insserv suggests:
ii  bootchart2  0.14.4-3+b1

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#916345: libmodbus: FTBFS on mips, s390x: test failure

[林上智]

Hi,

Ivo De Decker  於 2018年12月13日 週四 下午8:03寫道：
>
> package: src:libmodbus
> version: 3.1.4-1
> severity: serious
> tags: ftbfs
>
> Hi,
>
> The latest version of libmodbus in unstable fails on mips, s390x:
>
> https://buildd.debian.org/status/package.php?p=libmodbus
>
> The failure happens in the testsuite.
>
> Based on the failing architectures, it might be an endianess issue.

I've reproduced this issue with MIPS architecture.

===
TEST FLOATS
1/4 Set/get float ABCD:
Line 289: assertion error for 'equal_dword(tab_rp_registers,
UT_IREAL_ABCD)': FAILED Set float ABCD
**
===

According to above information, it might be a float endianess issue
and there is a potential fix for it [1].

I will continually squeeze my time to track this issue.

Any feedback is welcome.

[1] https://github.com/stephane/libmodbus/issues/358

SZ
>
>
> Also, please note this error:
>
> ./unit-tests.sh: 17: ./unit-tests.sh: killall: not found
>
> This doesn't happen for the builds that succeed. I guess the killall is done
> when the tests fail. This means a dependency on psmisc is missing.

Now fixed, thanks,

SZ
>
> Thanks,
>
> Ivo

Bug#899888: marked as done (xfce4-wmdock-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 05:59:59 +
with message-id 
and subject line Bug#916727: Removed package(s) from unstable
has caused the Debian Bug report #899888,
regarding xfce4-wmdock-plugin: Invalid maintainer address 
pkg-xfce-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.)


-- 
899888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-wmdock-plugin
Version: 0.6.0-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-wmdock-plugin,

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

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: 0.6.0-1+rm

Dear submitter,

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

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

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

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

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

Bug#899899: marked as done (xfce4-hdaps: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 05:57:04 +
with message-id 
and subject line Bug#916726: Removed package(s) from unstable
has caused the Debian Bug report #899899,
regarding xfce4-hdaps: Invalid maintainer address 
pkg-xfce-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.)


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

Dear uploader of xfce4-hdaps,

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

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: 0.0.9-2+rm

Dear submitter,

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

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

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

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

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

Bug#899434: marked as done (389-console: Invalid maintainer address pkg-fedora-ds-maintain...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 05:56:39 +
with message-id 
and subject line Bug#915513: Removed package(s) from unstable
has caused the Debian Bug report #899434,
regarding 389-console: Invalid maintainer address 
pkg-fedora-ds-maintain...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of 389-console,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.1.18-2+rm

Dear submitter,

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

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

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

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

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

Bug#916701: marked as done (dfwinreg FTBFS with Python 3.7)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 05:49:23 +
with message-id 
and subject line Bug#916701: fixed in dfwinreg 20181214-1
has caused the Debian Bug report #916701,
regarding dfwinreg FTBFS with Python 3.7
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.)


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

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

...
==
FAIL: testGlob2Regex (glob2regex.Glob2RegexTest)
Tests the Glob2Regex function.
--
Traceback (most recent call last):
  File "/build/1st/dfwinreg-20180712/tests/glob2regex.py", line 59, in 
testGlob2Regex
self.assertEqual(regex, expected_regex)
AssertionError: '[.^$*+?{}|()]' != '[.^$*+?{}\\|()]'
- [.^$*+?{}\\|()]
+ [.^$*+?{}\\\|()]
?+


--
Ran 76 tests in 0.840s

FAILED (failures=1, skipped=1)
Using Python version 3.7.2rc1 (default, Dec 12 2018, 06:25:49) 
[GCC 8.2.0]
Checking availability and versions of dependencies.
[OK]dfdatetime version: 20180704
[OK]dtfabric version: 20180808
[OK]pyregf version: 20170130
[OK]yaml version: 3.13

Checking availability and versions of test dependencies.
[OK]mock version: 2.0.0

make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: dfwinreg
Source-Version: 20181214-1

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

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

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

Debian distribution maintenance software
pp.
SZ Lin (林上智)  (supplier of updated dfwinreg 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, 18 Dec 2018 13:25:48 +0800
Source: dfwinreg
Binary: python3-dfwinreg
Architecture: source all
Version: 20181214-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: SZ Lin (林上智) 
Description:
 python3-dfwinreg - Digital Forensics Windows Registry library for Python 3
Closes: 916701
Changes:
 dfwinreg (20181214-1) unstable; urgency=medium
 .
   * Team upload.
   * Import new upstream release (Closes: #916701)
Checksums-Sha1:
 71631440f2271d5e88d076478ebd99469e59ccc0 2123 dfwinreg_20181214-1.dsc
 c1720be3b8e3ed503a589a5af11b8626b5dd06ec 1256528 dfwinreg_20181214.orig.tar.gz
 8d9306de510031d14037e1bfcd0677b851816420 2680 dfwinreg_20181214-1.debian.tar.xz
 1376091e0e3469980e31885d85eba51f3b023765 6302 
dfwinreg_20181214-1_amd64.buildinfo
 183b970822543a1fc1215ddc94b252a6ff84953d 15724 
python3-dfwinreg_20181214-1_all.deb
Checksums-Sha256:
 afa0e62f72ab6aea69be7b9bb3bf543ebe47262d928057bf30c79c5fc4551b0b 2123 
dfwinreg_20181214-1.dsc
 12500ec5545cfeb84d77473059997798064b220c8c86e6de707ab83b49622183 1256528 
dfwinreg_20181214.orig.tar.gz
 347120e6e3622356c3315cb921d1128c839111672a889e7d2a53b24777ee0416 2680 
dfwinreg_20181214-1.debian.tar.xz
 20f78bdd706b9cfcda419607621c58de57057e2be37d75192bd9d05c953e4824 6302 
dfwinreg_20181214-1_amd64.buildinfo
 ea251eadb2b6efcbc7eb716d81bc48b43a9780f1271a3f2191fcd74a3eb9d2a1 15724 
python3-dfwinreg_20181214-1_all.deb
Files:
 65b03dcffa1676658de7a2fdcaf9c846 2123 python optional dfwinreg_20181214-1.dsc
 779b3499fa0d56aae5c08c17d73bfff5 1256528 python optional 
dfwinreg_20181214.orig.tar.gz
 e5581435b76556c068e9f202c345d6f4 2680 python optional 
dfwinreg_20181214-1.debian.tar.xz
 12e0f88e2e023dd570236d947843c597 6302 python optional 
dfwinreg_20181214-1_amd64.buildinfo
 93e5d74d30b5ae37efd37879345f1c48 15724 python optional 
python3-dfwinreg_20181214-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF4+DOLMUAeME/ES6qVmzipVh8/kFAlwYhtgACgkQqVmzipVh
8/lsnQ/8Cnqgv7nQo9H/uCgEapPiZ2tHQEkiJoz2dGu9PMa4TrY13CoBjg2P5y1Z
6E79TFKCw26yniG1YjpnPB1DEBory8VSaWkAIVUu84pV1zpjjTUMS7we8rVzN4fl

Bug#916738: nvidia-alternative: Depends on a non-existent version of glx-alternative which breaks upgrade path.

[ewe2]

Package: nvidia-alternative
Version: 410.78-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Attempted to upgrade from buster/sid nvidia driver 390.87 to
experimental version 410.78-2

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Attempted to upgrade via version number and aptitude dependency management.

   * What was the outcome of this action?

All attempts failed due to circular dependencies which centred around a non-
existent version required for glx-alternative.

   * What outcome did you expect instead?

Normal upgrade.




-- Package-specific info:
uname -a:
Linux marvin 4.18.0-3-amd64 #1 SMP Debian 4.18.20-2 (2018-11-23)
x86_64 GNU/Linux

/proc/version:
Linux version 4.18.0-3-amd64 (debian-ker...@lists.debian.org) (gcc
version 7.3.0 (Debian 7.3.0-30)) #1 SMP Debian 4.18.20-2 (2018-11-23)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21
12:33:05 PDT 2018
GCC version:  gcc version 7.4.0 (Debian 7.4.0-1)

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107
[GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA
controller])
Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:11bf]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Dec 18 09:09 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Dec 18 09:09 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Dec 18 09:10 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Dec 18 09:10 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Dec 18 09:10 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Dec 18 09:09 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Dec 18 09:09 pci-:01:00.0-render -> ../renderD128
video:x:44:ewe2

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Dec 18 08:30 /etc/alternatives/glx ->
/usr/lib/nvidia
lrwxrwxrwx 1 root root   49 Dec 18 08:21
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   42 Dec 18 08:30
/etc/alternatives/glx--libEGL.so.1-i386-linux-gnu ->
/usr/lib/i386-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   44 Dec 18 08:30
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   48 Dec 18 08:21
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Dec 18 08:21
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   41 Dec 18 08:30
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu ->
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   41 Dec 18 08:30
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu ->
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Dec 18 08:30
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Dec 18 08:30
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   55 Dec 18 08:21
/etc/alternatives/glx--libGLESv1_CM.so-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so
lrwxrwxrwx 1 root root   55 Dec 18 08:21
/etc/alternatives/glx--libGLESv1_CM.so-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so
lrwxrwxrwx 1 root root   55 Dec 18 08:30
/etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu ->
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   55 Dec 18 08:30
/etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu ->
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   57 Dec 18 08:30
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   57 Dec 18 08:30
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   52 Dec 18 08:21
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root   52 Dec 18 08:21
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu ->
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root   52 Dec 18 08:30
/etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu ->
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   52 Dec 18 08:30

Bug#916716: live-wrapper: Replace vmdebootstrap usage with alternative

[Richard Lell]

These are the two choices. Which is better suited and has the dependencies
least conflicting? Is it possible to rewrite the packages spoken of above
in Python3?
Package: debootstrap (1.0.111)

debootstrap is used to create a Debian base system from scratch, without
requiring the availability of dpkg or apt. It does this by downloading .deb
files from a mirror site, and carefully unpacking them into a directory
which can eventually be chrooted into.
Package: cdebootstrap (0.7.7 and others)

cdebootstrap generates systems from scratch for Debian and derivates.

This is implementation is different from debootstrap. It features a
different package selection. The package selection is done according to the
flavour.

-- Rick
rainbowsolutions.tech

Bug#916737: bcron: fails to install: installed bcron package post-installation script subprocess returned error exit status 1

[Andreas Beckmann]

Package: bcron
Version: 0.11-3
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...):

  Selecting previously unselected package bcron.
  (Reading database ... 
(Reading database ... 4540 files and directories currently installed.)
  Preparing to unpack .../bcron_0.11-3_amd64.deb ...
  Unpacking bcron (0.11-3) ...
  Setting up bcron (0.11-3) ...
  dpkg: error processing package bcron (--configure):
   installed bcron package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   bcron


cheers,

Andreas


bcron_0.11-3.log.gz
Description: application/gzip

Bug#914954: marked as done (Fails to upgrade from 3.4.0 to 3.4.1: ERROR:root:After system restart, the values must be saved into db. Please, execute tuptime with a privileged user.)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 00:50:04 +
with message-id 
and subject line Bug#914954: fixed in tuptime 3.4.2
has caused the Debian Bug report #914954,
regarding Fails to upgrade from 3.4.0 to 3.4.1: ERROR:root:After system 
restart, the values must be saved into db. Please, execute tuptime with a 
privileged user.
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.)


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

Hi,

tuptime failed to upgrade from 3.4.0 to 3.4.1 for me as follows:

Setting up tuptime (3.4.1) ...
Installing new version of config file /etc/init.d/tuptime ...
ERROR:root:After system restart, the values must be saved into db. Please, 
execute tuptime with a privileged user.
dpkg: error processing package tuptime (--configure):
 installed tuptime package post-installation script subprocess returned error 
exit status 255

As I'm reading the error message, it seems to think for some reason
that root is not a privileged user… O.o

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

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

Versions of packages tuptime depends on:
ii  adduser  3.118
ii  init-system-helpers  1.56
ii  lsb-base 10.2018112800
ii  python3  3.7.1-2

tuptime recommends no packages.

tuptime suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tuptime
Source-Version: 3.4.2

We believe that the bug you reported is fixed in the latest version of
tuptime, 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.
Ricardo Fraile  (supplier of updated tuptime 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: Fri, 07 Dec 2018 15:48:00 +0100
Source: tuptime
Binary: tuptime
Architecture: source
Version: 3.4.2
Distribution: unstable
Urgency: low
Maintainer: Ricardo Fraile 
Changed-By: Ricardo Fraile 
Description:
 tuptime- report historical system real time
Closes: 914954
Changes:
 tuptime (3.4.2) unstable; urgency=low
 .
   * Fix Debian Bug Fails to upgrade (Closes: #914954)
   * Change deb architecture from any to all
Checksums-Sha1:
 9d2a0fa48f7c56dd8d6e0ef5e40cf293a40e0245 1091 tuptime_3.4.2.dsc
 9ff36537ea7dd64f6c43fff8c18e5d8d658e862b 37400 tuptime_3.4.2.tar.xz
 f033b17affb29f81d26ded188ac7cb1a03b7ef0c 5029 tuptime_3.4.2_amd64.buildinfo
Checksums-Sha256:
 117260d662c0add8dd649539f78c708f29b1e6d99e5f1926e9f60060bfebc1e6 1091 
tuptime_3.4.2.dsc
 7b942ee7c5e0d439c89f4edf8ab7cd6f7760b4afb5d60e87fab8195dd3b95e42 37400 
tuptime_3.4.2.tar.xz
 9d9e8f9357c22944052fc8f8984934239cde44e19e88a849cd027a68030b0497 5029 
tuptime_3.4.2_amd64.buildinfo
Files:
 e2839a9f1ab3b20c22af2e53fc2bd0fc 1091 utils optional tuptime_3.4.2.dsc
 f92c138d4008e22249da3d6d7c242c81 37400 utils optional tuptime_3.4.2.tar.xz
 40c82f872d1235ce3679f8d0fc0dc9be 5029 utils optional 
tuptime_3.4.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAlwXAlAACgkQPqHd3bJh
2XvATggAlKiNqwPEN9+Ctx5o47doVRkPKxIa6Q8I2WKfE7PIoSnkAHwrLA68QWF5
1XAuVnAIiL8L18RLKjYMHXUv8kso55i96qgHP+SvvB8ResNwQr2IDcsnc2qV1cg9
U4vEir/hEmzUMhekdMCMh1pawgrNcaf69IfQPvklF/UUcuHbhNg2mNHGEWSEKOVw
6+e7AFifoYfcqILYSlW3gTtOAHaMy4zESIXePpdXZBnoRLztYzHbwvNUXgwBGZGt
E6Wr4eCjuwjE5BN0f9vzoR4fFI4XkOsF0W4qTx8zHgmAKDdhh++7Zdzke+zwNRzE
6sHWSzsuVBt0V35IvT9LxJXobRxqQQ==
=leFQ
-END PGP SIGNATURE End Message ---

Bug#916052: marked as done (alsa-oss FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 23:49:19 +
with message-id 
and subject line Bug#916052: fixed in alsa-oss 1.1.6-2
has caused the Debian Bug report #916052,
regarding alsa-oss FTBFS with glibc 2.28
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.)


-- 
916052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alsa-oss
Version: 1.1.6-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alsa-oss.html

...
In file included from alsa-oss.c:736:
stdioemu.c:40:10: fatal error: libio.h: No such file or directory
 #include 
  ^
compilation terminated.
make[2]: *** [Makefile:517: alsa-oss.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: alsa-oss
Source-Version: 1.1.6-2

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

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

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

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated alsa-oss 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, 18 Dec 2018 00:27:03 +0100
Source: alsa-oss
Binary: alsa-oss
Architecture: source
Version: 1.1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ALSA Maintainers 
Changed-By: Jordi Mallach 
Description:
 alsa-oss   - ALSA wrapper for OSS applications
Closes: 916052
Changes:
 alsa-oss (1.1.6-2) unstable; urgency=medium
 .
   * Cherry-pick upstream patch to fix build with glibc 2.28
 (closes: #916052).
Checksums-Sha1:
 80a8c5373660f5fb52cc14e8e59d0ad2cc517e5d 2001 alsa-oss_1.1.6-2.dsc
 b3041878fa0059730a89a5d6dbd5dbf599f18f7b 7300 alsa-oss_1.1.6-2.debian.tar.xz
 c1f705894c60dd6927b613bc415263baa302e42f 6753 alsa-oss_1.1.6-2_source.buildinfo
Checksums-Sha256:
 feaceadf43824cefc3d3d0f3b31783df33101c813f38a3746761ec70bd2edc3b 2001 
alsa-oss_1.1.6-2.dsc
 cfb317725bdfa8ed0a3a8c97d7672301eadf4146e27480adc41f0b8aae321411 7300 
alsa-oss_1.1.6-2.debian.tar.xz
 4f6f6360867baaa8695862e2aeb249c8be023f092b92cf24ad3094f7ebe92f5a 6753 
alsa-oss_1.1.6-2_source.buildinfo
Files:
 5607d81fb795af259a9dd1303a820ff6 2001 sound optional alsa-oss_1.1.6-2.dsc
 318a624655f22347c94ff4dd8546f265 7300 sound optional 
alsa-oss_1.1.6-2.debian.tar.xz
 94ad6242241233ca6b184421d2e12a75 6753 sound optional 
alsa-oss_1.1.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAlwYMNsRHGpvcmRpQGRl
Ymlhbi5vcmcACgkQJVAvb8vjywSRJhAAnvRokz/3MYIOERXl79DVF75t5Di0d9B3
fBxTMUGd2xuHUmBarAHLsintP/mKPrHD8arcgnbt8zsvFZPB5hhvVCdkGn6Aewz/
UAlQtjT+NaftwO0m2i83nRWhmz6xMHDjDM/MovrPRUYAayTLwQPyqCxRz83OXxYJ
qjBw0zBpWM/F0MCA7rhbolSrSpkCqtN0kjrUvD56PYwQPbcJbs1bFzss3ms1k0Kn
hzGhiClBygGfvpkO+vR+PXmtanCYpZiMCQlNgc5Nsr3TT0oE+LOGy8NUvcWVUEoE
eaLc6V/LIZu0GFM9puenY8I/E1dPkraaE9QQqXaMVddxe+SCHI4/CQF1mCcBMftf
wm4PZMDFb3WVlaFAVzbrol88vUtV57Km3axyh6V2U6TcWmtK5PlGTOonoe23B9xD
pcbT7bjc/7JXe2n0J9fKVzUVN3zW3zwIpNyf/1cQW90t7enaN24myepwfUCmu2qy
JmCh1RyQol6IJ+7pvSG2/8SifW0AHxNzZNQSNP+aisiUvfuB0CdLUZtBBBRJdq8F
jbAkqx3sTksGrikAPNVC9hz4lPgYdnYa/kkcMvAoqR3rv7BhN4pBGXzvm2iYU+ti
M7pzleT/ON8J51GKL/l1clltqEZgfP3F2DKdaFeYAxWxwzV56gYxJX623quWO6+w
qvpRZ0N2ntU=
=2O3d
-END PGP SIGNATURE End Message ---

Processed: found 916302 in 12~24-2

[Debian Bug Tracking System]

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

> found 916302 12~24-2
Bug #916302 [openjdk-12-jre-headless] openjdk-12-jre-headless: modifies shipped 
file: /usr/lib/jvm/java-12-openjdk-amd64/lib/server/classes.jsa
Marked as found in versions openjdk-12/12~24-2.
> thanks
Stopping processing here.

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

Bug#911610: eldav: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el

[Andreas Beckmann]

Followup-For: Bug #911610
Control: found -1 10.8+0.20120427-16

I've also observed this behavior (i.e. lost files in some package, e.g.
eldav) in stretch, so it's probably apel there, too.
Could you backport the fix to stretch and open a stretch-pu request? If
you send a patch, I can test the fixed packages in my piuparts instance
in stretch.

Thanks.

Andreas

Processed: Re: eldav: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el

[Debian Bug Tracking System]

Processing control commands:

> found -1 10.8+0.20120427-16
Bug #911610 {Done: Tatsuya Kinoshita } [apel] eldav: files 
missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el
Bug #911612 {Done: Tatsuya Kinoshita } [apel] tdiary-mode: 
files missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el
Marked as found in versions apel/10.8+0.20120427-16.
Marked as found in versions apel/10.8+0.20120427-16.

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

Bug#904404: liece-dcc: fails to install with emacs25

[Andreas Beckmann]

On 2018-12-17 22:41, Tatsuya Kinoshita wrote:
> On December 17, 2018 at 9:38PM +0100, anbe (at debian.org) wrote:
>> 1m16.4s ERROR: FAIL: debsums reports modifications inside the chroot:
>>   debsums: missing file /usr/share/emacs/site-lisp/liece/bitmap-stipple.el 
>> (from liece package)
>>   debsums: missing file /usr/share/emacs/site-lisp/liece/delegate.el (from 
>> liece package)
> 
> This issue is fixed in apel 10.8+0.20120427-19.

Thanks for the info, rescheduling piuparts tests with smilar failures
(in my local piuparts instance).


Andreas

Bug#904404: liece-dcc: fails to install with emacs25

[Tatsuya Kinoshita]

Control: tags -1 + patch

On December 17, 2018 at 9:38PM +0100, anbe (at debian.org) wrote:
> 1m16.4s ERROR: FAIL: debsums reports modifications inside the chroot:
>   debsums: missing file /usr/share/emacs/site-lisp/liece/bitmap-stipple.el 
> (from liece package)
>   debsums: missing file /usr/share/emacs/site-lisp/liece/delegate.el (from 
> liece package)

This issue is fixed in apel 10.8+0.20120427-19.

On July 24, 2018 at 5:18AM +0200, anbe (at debian.org) wrote:
> Loading /usr/share/emacs25/site-lisp/liece/liece-config.el (source)...
> Cannot open load file: No such file or directory, install

It seems apel's install.el* is not found when byte-compiling.

The following patch fixes this bug.  Although liece seems to fail
with Emacs 26 (not yet packaged in Debian)...

```
--- a/debian/emacsen-install
+++ b/debian/emacsen-install
@@ -41,6 +41,7 @@
 done | sort -u)
 
 if [ ${FLAVOR} = emacs ]; then exit 0; fi
+if [ ! -f "/usr/share/$FLAVOR/site-lisp/apel/install.elc" ]; then exit 0; fi
 
 # Install-info-altdir does not actually exist. 
 # Maybe somebody will write it.
@@ -104,6 +105,7 @@
 done
 
 cat << EOF > path.el
+(setq load-path (cons "/usr/share/$FLAVOR/site-lisp/apel" load-path))
 (setq load-path (cons "." load-path) byte-compile-warnings nil)
 EOF
 if test "${APPEND_LOAD_PATH}" != ""
```

Thanks,
-- 
Tatsuya Kinoshita


pgpXQ5RH2anMW.pgp
Description: PGP signature

Processed: Re: Bug#904404: liece-dcc: fails to install with emacs25

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #904404 [liece-dcc] liece-dcc: fails to install with emacs25
Added tag(s) patch.

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

Bug#899742: marked as done (xfce4-notes-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 21:36:52 +
with message-id 
and subject line Bug#899742: fixed in xfce4-notes-plugin 1.8.1-2
has caused the Debian Bug report #899742,
regarding xfce4-notes-plugin: Invalid maintainer address 
pkg-xfce-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.)


-- 
899742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-notes-plugin
Version: 1.8.1-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-notes-plugin,

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

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 ---
Source: xfce4-notes-plugin
Source-Version: 1.8.1-2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-notes-plugin 
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: Mon, 17 Dec 2018 22:05:07 +0100
Source: xfce4-notes-plugin
Binary: xfce4-notes xfce4-notes-plugin
Architecture: source
Version: 1.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-notes - Notes application for the Xfce4 desktop
 xfce4-notes-plugin - Notes plugin for the Xfce4 desktop
Closes: 899742
Changes:
 xfce4-notes-plugin (1.8.1-2) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899742
   * d/gbp.conf added, following DEP-14
   * run wrap-and-sort
   * d/watch: use HTTPS protocol
   * New upstream version 1.8.1
   * d/control: drop Lionel from uploaders, thanks!
   * d/control: update standards version to 4.2.1
   * d/control: use HTTPS protocol for Homepage field
   * d/control: drop breaks/replaces for old versions
   * update debhelper compat to 10
   * d/patches imported in gbp pq
   * d/copyright updated
Checksums-Sha1:
 3d92f62376eb051b3a1abfcabaf1f21c7294d331 1945 xfce4-notes-plugin_1.8.1-2.dsc
 

Bug#907945: marked as done (libfm FTBFS with glib 2.58)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 21:35:06 +
with message-id 
and subject line Bug#907945: fixed in libfm 1.3.1-1
has caused the Debian Bug report #907945,
regarding libfm FTBFS with glib 2.58
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.)


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

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

...
cd tests && make  test
make[3]: Entering directory '/build/1st/libfm-1.3.0.2/src/tests'
TEST: fm-path... (pid=50413)

** (process:50413): WARNING **: 16:52:53.943: The directory '~/Templates' 
doesn't exist, ignoring it
Tests were compiled with G_DISABLE_ASSERT and are likely no-ops. Aborting.
FAIL: fm-path
make[3]: *** [Makefile:722: test-nonrecursive] Terminated
--- End Message ---
--- Begin Message ---
Source: libfm
Source-Version: 1.3.1-1

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

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

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

Debian distribution maintenance software
pp.
Andriy Grytsenko  (supplier of updated libfm 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: Mon, 17 Dec 2018 23:00:25 +0200
Source: libfm
Binary: libfm4 libfm-extra4 libfm-dev libfm-extra-dev libfm-gtk-dev libfm-doc 
libfm-dbg libfm-gtk-dbg libfm-modules-dbg libfm-data libfm-gtk-data libfm-gtk4 
libfm-tools libfm-modules
Architecture: source all amd64
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LXDE Maintainers 

Changed-By: Andriy Grytsenko 
Description:
 libfm-data - file management support (common data)
 libfm-dbg  - file management support (libfm debug)
 libfm-dev  - file management support (core development files)
 libfm-doc  - file management support (development documentation)
 libfm-extra-dev - file management support (libfm-extra development files)
 libfm-extra4 - file management support (extra library)
 libfm-gtk-data - file management support (GTK+ library common data)
 libfm-gtk-dbg - file management support (libfm-gtk debug)
 libfm-gtk-dev - file management support (GTK+ GUI development files)
 libfm-gtk4 - file management support (GTK+ 2.0 GUI library)
 libfm-modules - file management support (loadable modules for library)
 libfm-modules-dbg - file management support (libfm-modules debug)
 libfm-tools - file management support (utilities)
 libfm4 - file management support (core library)
Closes: 907945 914150
Changes:
 libfm (1.3.1-1) unstable; urgency=medium
 .
   * Removing debian/source/options file, let lintian get easy.
   * Merging upstream version 1.3.1 (Closes: #907945, #914150).
   * Bump Standards-Version to 4.2.1.
   * Bump debhelper compat to 11.
   * Updating override soname 4.1.1 -> 4.1.2.
Checksums-Sha1:
 3e5d76d13e7b99ce815033ac46d7b6bc25bc94be 3172 libfm_1.3.1-1.dsc
 29539f50acd5c00a00362adffd532053b0688e66 940632 libfm_1.3.1.orig.tar.xz
 5ecadbc7d36f280cb589b697fed50c512af873a5 15460 libfm_1.3.1-1.debian.tar.xz
 05d9ebfeed1e04bdc762ba8e11067d83be38a946 243812 libfm-data_1.3.1-1_all.deb
 7bbfb22b7a4c969a095a06531cf4a4640fd194cc 550500 libfm-dbg_1.3.1-1_amd64.deb
 96b7c11fa6957d596ddcf63c18be1535213a7df7 58252 libfm-dev_1.3.1-1_amd64.deb
 9b15a94896c2aef2f69eb04a6a20d9cd7ed33223 158692 libfm-doc_1.3.1-1_all.deb
 c01ec590b2da7f84757742d54fd1d8c255f65ef9 24336 
libfm-extra-dev_1.3.1-1_amd64.deb
 d49de2d552d7cd94006e60c96b7baac4e9c64a6f 32136 libfm-extra4_1.3.1-1_amd64.deb
 fec22a7ad3cb75395ba7c5b03140f37c64325cf5 35144 libfm-gtk-data_1.3.1-1_all.deb
 f7f3f7d155c094320f469c12ae5fead496f240f4 770064 libfm-gtk-dbg_1.3.1-1_amd64.deb
 50b5b57c3aa25372fde296ee600acac276cac436 22624 libfm-gtk-dev_1.3.1-1_amd64.deb
 02156a0dc77f1b24b930b4db8fbf62872dfc16fe 165076 libfm-gtk4_1.3.1-1_amd64.deb
 d2f1b5ba6f8dfc02497a9aa59c2d8a3f8893afc6 175884 
libfm-modules-dbg_1.3.1-1_amd64.deb
 77c7c8db0f00106c42c4c93f6c40713ddf5e6e50 52276 libfm-modules_1.3.1-1_amd64.deb
 711788c583535ed2cdf441607632792dcce88b18 34636 

Bug#915174: marked as done (recutils FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 21:14:19 +
with message-id 
and subject line Bug#915174: fixed in recutils 1.7-3
has caused the Debian Bug report #915174,
regarding recutils FTBFS with glibc 2.28
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.)


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

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

...
fseterr.c: In function 'fseterr':
fseterr.c:77:3: error: #error "Please port gnulib fseterr.c to your platform! 
Look at the definitions of ferror and clearerr on your system, then report this 
to bug-gnulib."
  #error "Please port gnulib fseterr.c to your platform! Look at the 
definitions of ferror and clearerr on your system, then report this to 
bug-gnulib."
   ^
make[4]: *** [Makefile:2057: fseterr.lo] Error 1


See #915151 for background.
--- End Message ---
--- Begin Message ---
Source: recutils
Source-Version: 1.7-3

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

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

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

Debian distribution maintenance software
pp.
Sven Wick  (supplier of updated recutils 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: Sun, 09 Dec 2018 17:14:53 +0100
Source: recutils
Binary: recutils librec-dev librec1
Architecture: source
Version: 1.7-3
Distribution: unstable
Urgency: medium
Maintainer: Sven Wick 
Changed-By: Sven Wick 
Description:
 librec-dev - recutils development files
 librec1- library for accessing recfiles programmatically
 recutils   - text-based databases called recfiles
Closes: 684394 849241 915174
Changes:
 recutils (1.7-3) unstable; urgency=medium
 .
   * debian/copyright
 - changed Homepage URL to HTTPS
 - bumped copyright years
   * debian/control
 - changed Homepage URL to HTTPS
 - providing a packaging VCS repo (Closes: #684394)
 - Bumped Standards-Version to 4.2.1
   * debian/patches
 - renamed following 2 patches for consistency ( .patch as file extension )
  - fix-includes.diff
  - spelling-error-in-binary-csv2rec
 - added gnulibrary-glibc-detection.patch (Closes: #915174)
 - added spelling-error-in-csv2rec-manpage.patch
  - fixes lintian warning spelling-error-in-manpage
 - added rec-mode.patch (Closes: #849241)
Checksums-Sha1:
 0c6096685f8f23227980797539dbd6927ffb0121 2273 recutils_1.7-3.dsc
 3cdd1d043c1b256e120196e7d9ff2c9a167f895d 52096 recutils_1.7-3.debian.tar.xz
 fecb230fe5761b7908bba558df37e0541811d321 8155 recutils_1.7-3_amd64.buildinfo
Checksums-Sha256:
 0d561c43bb04e19cb41186c9c93921c75fce9edbf2ebc39756e16fa1de2d29fd 2273 
recutils_1.7-3.dsc
 b4bbbf2c7c75c1549f922cfe498f8e4afbe14b9801bbca047c207155a141e141 52096 
recutils_1.7-3.debian.tar.xz
 78faa4310548d6f5a5e553c79b8826446bbffeb3a9c4bda71a9489392d721aaa 8155 
recutils_1.7-3_amd64.buildinfo
Files:
 9ecc356a7093f6c49619a634a0d49730 2273 database optional recutils_1.7-3.dsc
 b3e43ed00c68f9b70609eca3d01621c8 52096 database optional 
recutils_1.7-3.debian.tar.xz
 0b1954964d2a3bc41476faf01b4ee8b1 8155 database optional 
recutils_1.7-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlwYCPwACgkQCBa54Yx2
K631lg/+MSQs4wgzIWFiYZi+iRk05A9/bTBl80lBhyaPVdBYogjxt71hiKVGmmk+
UXUW4Rff8zOuSl/rfq96eULjaOGolbdvKqqs2BtLZsR6sN/xGqB+NX5WTiXAzj7g
cooyLnxQ2DI5ysk6pnTeOj6QnmwCE2foLcA9qn8lrgyA3cm5HuLabucM62xMP5tx
CzhMprxxIQwmx9sp9Un0SDdq2cgftW1K2oS3sa3luRLA0aix0IAS5Fo2C94+7nnA
fpkqpYeasN12pt4wEVBUUxM9C90iF0q4TGG1JTScWymXVGlBBnpQkhkP25xoHoVw
klX4Vho2nxJIZ6GSlRShgJ2guA1bAiPUldCMZn0Vf81sMxJdsm8rUsYJko95CexX
9+pOwrmfC6QYouUrNGnVYvJiHDey8RoC+Oj3cLZbxEneJ/xNyZx0gFxGyu0CUOiZ
aEuEBk+tdrYZ8iXRjkkyB0HDOmjxK7HiQGI8rB5Oq0Uiy3bwWCz8m/R8ZmV0QyHm
KtPj63ZK+eIhyXHrZMtjQswTWOShhS0e/5jp6MeGxodFlYE1BC3impCyU+kB38fO
dvZmGymp7K1weSLusYdlopAz/IryPUikhAf2DB1BbVLKuQSW6Ai52n89F+obNpTE
sRn5xeBLtF8P44NEAqTuDJPhXPZxpBlMSm5HmKKKpbRwI5BW3Xs=
=OYH4
-END PGP SIGNATURE End 

Processed: severity of 916716 is serious

[Debian Bug Tracking System]

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

> severity 916716 serious
Bug #916716 [live-wrapper] live-wrapper: Replace vmdebootstrap usage with 
alternative
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#904404: liece-dcc: fails to install with emacs25

[Andreas Beckmann]

Followup-For: Bug #904404

Another recent piupart test run revealed another, probably
related problem: after the installation several shipped files
are missing:

1m16.4s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/share/emacs/site-lisp/liece/bitmap-stipple.el 
(from liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/delegate.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/gettext.el (from liece 
package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-000.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-200.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-300.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-400.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-500.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-channel.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-clfns.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-coding.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-commands.el 
(from liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-compat.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-config.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-ctcp.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-dcc.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-emacs.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-filter.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-globals.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-handle.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-handler.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-hilit.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-inlines.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-intl.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-mail.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-make.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-menu.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-message.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-minibuf.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-misc.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-modules.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-nick.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-q-ccl.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-q-el.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-tcp.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-url.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-vars.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-version.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-window.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-x-face.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece-xemacs.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece.el (from liece 
package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece.xbm (from liece 
package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/liece.xpm (from liece 
package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/plum-support.el (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/queue-m.el (from liece 
package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/styles/bottom (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/styles/middle (from 
liece package)
  debsums: missing file /usr/share/emacs/site-lisp/liece/styles/top (from liece 
package)


Andreas


liece_2.0+0.20030527cvs-11.2.log.gz
Description: application/gzip

Bug#916683: libgnutls30: breaks msmtp 1.6.7-1

[Jonas Smedegaard]

Quoting Andreas Metzler (2018-12-17 19:37:05)
> On 2018-12-17 Jonas Smedegaard  wrote:
> > I use msmtp, and it worked fine until few days ago,
> > with msmtp 1.6.7-1 and libgnutls30 3.5.19-1+b1.
> 
> > Upgrading to libgnutls30 3.6.5-2 breaks msmtp:
> > Any attempt at connecting to a TLS-secured site gets disconnected.
> 
> FWIW I have had successful connections against exim4 (gnutls 3.5 and 
> 3.6). Which host are you trying to connect to?

Sorry for exaggerating!

The hosts I experienced problems with are mail.jones.dk and 
mail.homebase.dk - both running Postfix on Debian stable (which made me 
rule out them as cause for blame, but...) both of them managed by myself 
with various attempts at tightening security, so I realize now that I 
may possibly have exposed bugs in unusual setups rather than common 
ones.

Both systems are running in production so I am not happy doing drastic 
experiments on them - but on the other hand they are public accessible 
so available for testing this bug if needed.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#916683: libgnutls30: breaks msmtp 1.6.7-1

[Jonas Smedegaard]

Quoting Andreas Metzler (2018-12-17 19:37:05)
> On 2018-12-17 Jonas Smedegaard  wrote:
> > I use msmtp, and it worked fine until few days ago,
> > with msmtp 1.6.7-1 and libgnutls30 3.5.19-1+b1.
> 
> > Upgrading to libgnutls30 3.6.5-2 breaks msmtp:
> > Any attempt at connecting to a TLS-secured site gets disconnected.
> 
> FWIW I have had successful connections against exim4 (gnutls 3.5 and
> 3.6). Which host are you trying to connect to?
> 
> > Seems liek backwards-incompatible ABI change to me, which I believe 
> > should be handled in coordination with its reverse dependencies.  
> > Hence the severity.
> 
> It is not an API change but a side effect of different handshake with
> TLS1.3, now GNUTLS_E_AGAIN can be returned for blocking sockets.
> 
> See 
> https://github.com/marlam/msmtp-mirror/commit/ec043e5375d0ecd5ab987e53d0ebfecfc1de0858

Ahh, thanks a lot for digging deeper.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#916715: toulbar2: missing build dependency on zlib1g-dev

[Adrian Bunk]

Source: toulbar2
Version: 1.0.0+dfsg3-1
Severity: serious
Tags: ftbfs

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

...
CMake Error: The following variables are used in this project, but they are set 
to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake 
files:
ZLIB_LIBRARY
linked by target "toulbar2" in directory /build/1st/toulbar2-1.0.0+dfsg3

Bug#914060: marked as done (freeture FTBFS with boost 1.67)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 19:19:51 +
with message-id 
and subject line Bug#914060: fixed in freeture 1.3.0-1
has caused the Debian Bug report #914060,
regarding freeture FTBFS with boost 1.67
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.)


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

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

...
SMTPClient.cpp: In static member function 'static void 
SMTPClient::sendMail(std::__cxx11::string, std::__cxx11::string, 
std::__cxx11::string, std::__cxx11::string, 
std::vector >, std::__cxx11::string, 
std::__cxx11::string, std::vector >, 
SmtpSecurity)':
SMTPClient.cpp:347:57: error: 'boost::asio::ip::tcp::socket' {aka 'class 
boost::asio::basic_stream_socket'} has no member named 
'native'
 OpenSSL openSSL(socket.GetSocket()->native());
 ^~


This Ubuntu diff seems to contain a fix.
--- End Message ---
--- Begin Message ---
Source: freeture
Source-Version: 1.3.0-1

We believe that the bug you reported is fixed in the latest version of
freeture, 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.
Chiara Marmo  (supplier of updated freeture 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: Mon, 17 Dec 2018 17:30:27 +0100
Source: freeture
Binary: freeture
Architecture: source
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Chiara Marmo 
Description:
 freeture   - Free software to capTure meteors
Closes: 914060
Changes:
 freeture (1.3.0-1) unstable; urgency=medium
 .
   * Fix freeture FTBFS with boost 1.67. (Closes: #914060)
Checksums-Sha1:
 5ce961a36e3f873779b1d80eefee7a7cde004d23 2119 freeture_1.3.0-1.dsc
 c4219273cafb37c484b56e4d0f9a45524bac4daf 1973680 freeture_1.3.0.orig.tar.gz
 df5d7cf1e4f128363885b595a34eec591000f3c4 3676 freeture_1.3.0-1.debian.tar.xz
Checksums-Sha256:
 3b3ea2c0f898b9fd551027112fe3dd3fc9b278f00695969ba327c292eddf7666 2119 
freeture_1.3.0-1.dsc
 3e2d12d52d780587ebfbd948f80fe76c2e6e74f412e0cb78191e8a04719e3e79 1973680 
freeture_1.3.0.orig.tar.gz
 78e32d94fe2b5dd8a5413840c28e31d8757a71bee5f588bec3eabc780c0d0eb8 3676 
freeture_1.3.0-1.debian.tar.xz
Files:
 0133f496ba4c61a192d126c03789aaf4 2119 video optional freeture_1.3.0-1.dsc
 d3eb75ac2982cf063f2c0f65910412b7 1973680 video optional 
freeture_1.3.0.orig.tar.gz
 aaf0ca614298047622bf95381630ebe7 3676 video optional 
freeture_1.3.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAlwX85IACgkQcRWv0HcQ
3Pd8QhAAtq8lxKritlFYD2JmKZ9JwoBPhZnmjrNTDic+v+yBBsAfcdEqz3so9NhE
P3wYnbbLaK+fanH1d3I1vPXGfRGm8Q6UVjSuz9agyvHEEtY+w2IomFbmutG6VDVh
19kgBHz46WDtewIKZ3h1Wrye9uEJ6+VwXntsT7MOKS62zpO5WRxOK4Cpw5anxpvE
aaRpazobjG2lWdvddxImne6k4b39JqYxIkRbEPH3fil1A7KeKRTKqAnUUCfRkWkC
rChpFrMXhtbSvhYOwA0Xc+a7GPu6DU8wQL37GjJZd7PuqiM8DiL0rD/rQKVmz09Y
c+BS7HsUhblrvRv1ngdgqzk5/AV9bVizeYY0mw1lhg8DH0GiIw/TB6a2oZjj4VlC
3asqB4ipFkrBVx4u7aFEQ8MAniCGFK44PaM6GpgFhwKydJzG/VW6N4eqMFPLohaI
5pKtBFG4ZgKtkRt+w48tL3D1BwCxllqW8p39lSWf5pnXzgfLlbMCgUhs1WLrOTSH
Y4YZtk1j5DAOEIyf0d6EKw3h3sukMTZTFz1y6XF9BWK+AjbHOuYmSwDgozONkJmD
2OoFxveZhkd4lNweBf9dYFh3eZVGI2JtbBMJe+6jPKBnVa9J+8OwNBvJF04AXeoh
xu72KUkFQLaNNXVbEmFotIGrlF8umu/UtNYMLZh18CGyWmC/dwU=
=LC9l
-END PGP SIGNATURE End Message ---

Bug#916714: plplot FTBFS: Cannot find "usr/lib/*/plplot*/drivers/cairo.*"

[Adrian Bunk]

Source: plplot
Version: 5.13.0+dfsg-9
Severity: serious
Tags: ftbfs

Some recent change in unstable makes plplot FTBFS:

https://tests.reproducible-builds.org/debian/history/plplot.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/plplot.html

...
-- WARNING: pango and/or cairo not found with pkg-config.
   Disabling cairo drivers.  To enable these drivers you must install
   development versions of pango and cairo and/or set
   the environment variable PKG_CONFIG_PATH appropriately.
...
   dh_install -O-Scmake
dh_install: Cannot find (any matches for) "usr/lib/*/plplot*/drivers/cairo.*" 
(tried in ., debian/tmp)

dh_install: plplot-driver-cairo missing files: usr/lib/*/plplot*/drivers/cairo.*
dh_install: missing files, aborting
make: *** [debian/rules:35: binary] Error 25

Bug#916712: libgnutls30: Dummy bug - prevent too fast migration to testing

[Andreas Metzler]

Package: libgnutls30
Version: 3.6.5-2
Severity: serious
Justification: maintainer's opinion

gnutls 3.6.5-2 would be a candidate for testing migration tomorrow ("Too
young, only 1 of 2 days old"). This is too quick, the changes require
more testing in sid.

cu Andreas

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


signature.asc
Description: PGP signature

Bug#916711: only GPL-3

[Thorsten Alteholz]

Package: smbmap
Version: 1.0.5+git20180508-1
Severity: serious
thanks

Dear Maintainer,

according to smbmap-master/LICENSE, the license of this software is only 
GPL-3. Please adapt your debian/copyright accordingly.


Thanks!
  Thorsten

Bug#912129: marked as done (netkit-rwall misses the generator for configure)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 18:36:01 +
with message-id 
and subject line Bug#912129: fixed in netkit-rwall 0.17-8
has caused the Debian Bug report #912129,
regarding netkit-rwall misses the generator for configure
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.)


-- 
912129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netkit-ntalk
Version: 0.17-15
Severity: serious
Justification: DFSG #2
User: helm...@debian.org
Usertags: rebootstrap

The configure file in the netkit-ntalk is generated using confgen from
MCONFIG.in. However, the generator is missing. No package in unstable
contains said confgen tool. Thus configure cannot be regenerated after
fixing a bug. That's a violation of DFSG #2.

Helmut
--- End Message ---
--- Begin Message ---
Source: netkit-rwall
Source-Version: 0.17-8

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

Debian distribution maintenance software
pp.
Alberto Gonzalez Iniesta  (supplier of updated netkit-rwall 
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: Mon, 17 Dec 2018 18:52:30 +0100
Source: netkit-rwall
Binary: rwalld rwall
Architecture: source amd64
Version: 0.17-8
Distribution: unstable
Urgency: medium
Maintainer: Alberto Gonzalez Iniesta 
Changed-By: Alberto Gonzalez Iniesta 
Description:
 rwall  - Send a message to users logged on a host
 rwalld - Write messages to users currently logged in server
Closes: 912129
Changes:
 netkit-rwall (0.17-8) unstable; urgency=medium
 .
   [ Christoph Biedl ]
   * Move build system to cmake. (Closes: #912129)
   * Mayor cleanup in debian/
 .
   [ Alberto Gonzalez Iniesta ]
   * Rewrite debian/copyright
   * Bumped Standards-Version to 4.2.1. No changes.
Checksums-Sha1:
 97075660efd09ff202cd0e27e2907344741035d2 1757 netkit-rwall_0.17-8.dsc
 e1b91b8f82449df329274935746077c0d25ddd46 4332 netkit-rwall_0.17-8.debian.tar.xz
 185cbe550a66853407603a99eaeba933c8fd1cf1 7274 
netkit-rwall_0.17-8_amd64.buildinfo
 ea1e53f538872148e803b9ccc237ac59b6b129c2 10316 rwall-dbgsym_0.17-8_amd64.deb
 a1065902f4220fc42c4ab4cbe8ba7c910bc8a74e 10692 rwall_0.17-8_amd64.deb
 fbf12fe23c6232113baa7d6c5c9614407d25fec3 12928 rwalld-dbgsym_0.17-8_amd64.deb
 0e10f25dcb9d535f63d94aa62c16fd224e8f1ca2 9820 rwalld_0.17-8_amd64.deb
Checksums-Sha256:
 4a86a6d400e6b063f70c6d8078ce7b0451d2de93a512f2d5f3b287a0a3f000b7 1757 
netkit-rwall_0.17-8.dsc
 c734c1b11fdd63239d33e4df5c3b66808188d9b502ce203e14a7fa3301b4fd27 4332 
netkit-rwall_0.17-8.debian.tar.xz
 7f1850c6e25a06f686005c7a6c5090e4abd03b9ff10ece584a6c4768b48f0896 7274 
netkit-rwall_0.17-8_amd64.buildinfo
 9954cfa109f92bc4c2134c673e59bffc469eee3809e1e6c53ef1f067d2024f58 10316 
rwall-dbgsym_0.17-8_amd64.deb
 a6f52a1147c3da5706124581aeb8eec5b3664e9c58b29201bfa555a6d2bbe00b 10692 
rwall_0.17-8_amd64.deb
 b983d3ab0278d1494143e301785ae28717d3639ed199d59cfbb1dce91f80de1f 12928 
rwalld-dbgsym_0.17-8_amd64.deb
 8c15458dacadc391616fa96b34425ef6a1642aa75cdab042b3174d8f0e79c960 9820 
rwalld_0.17-8_amd64.deb
Files:
 a2bd93b28f4063c8da79f0d3addeb99a 1757 net optional netkit-rwall_0.17-8.dsc
 fab46dc2c05bab2cca0a19a1850aecab 4332 net optional 
netkit-rwall_0.17-8.debian.tar.xz
 e97f95539d30929d8f8281f1e6ed98c9 7274 net optional 
netkit-rwall_0.17-8_amd64.buildinfo
 96edd9bb6eaa6bb15b288e603e59921e 10316 debug optional 
rwall-dbgsym_0.17-8_amd64.deb
 58dd588619f858217bfd4a1b52295362 10692 net optional rwall_0.17-8_amd64.deb
 1007b2d5484782b8b6d66b2b049cf964 12928 debug optional 
rwalld-dbgsym_0.17-8_amd64.deb
 dce6b712359fdf423ff5a50bcf13ed11 9820 net optional rwalld_0.17-8_amd64.deb

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEEU0fL2D4wqetNfUvyAJszdWuaqlUFAlwX5gIQHGFnaUBpbml0
dGFiLm9yZwAKCRAAmzN1a5qqVSBgD/4gnAY5+thrq1mQ+0z8NGS6vtuvZxeAfzao
OTew3N72RmK+oWFeleXLTuIVABBp3mzCwjSOFNHE/0cnRgv/7Pcx1tiwbab7duot
8fDhWOdgNwYwHh8Jo0iX5idy+DA2a15pJvW2Xsxev89wb/0+k2y71f0zCegrytat
N9Eu3NiTzZjQXlGf1uVAb0yq148nfegoSIpBo1KwTgkqdt6KK5n7GH4YipltVzpr

Processed: Re: Bug#916683: libgnutls30: breaks msmtp 1.6.7-1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 msmtp 1.6.7-1
Bug #916683 [libgnutls30] libgnutls30: breaks msmtp 1.6.7-1
Bug reassigned from package 'libgnutls30' to 'msmtp'.
No longer marked as found in versions gnutls28/3.6.5-2.
Ignoring request to alter fixed versions of bug #916683 to the same values 
previously set
Bug #916683 [msmtp] libgnutls30: breaks msmtp 1.6.7-1
Marked as found in versions msmtp/1.6.7-1.
> tags -1 fixed-upstream
Bug #916683 [msmtp] libgnutls30: breaks msmtp 1.6.7-1
Added tag(s) fixed-upstream.

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

Bug#916630: marked as done (terminology: CVE-2018-20167: Remote execution via special escape codes that handle unknown media types)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 18:36:22 +
with message-id 
and subject line Bug#916630: fixed in terminology 1.3.1-1
has caused the Debian Bug report #916630,
regarding terminology: CVE-2018-20167: Remote execution via special escape 
codes that handle unknown media types
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.)


-- 
916630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: terminology
Version: 1.3.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Owner: r...@kallisti.us
Forwarded: https://phab.enlightenment.org/T7504

Terminology 1.3.1 has been released to fix a remote code execution
vulnerability in special escape handling.  This can be mitigated by unchecking
Settings -> Enable special Terminology escape codes.  I'm preparing a release.


Details from upstream bug report:
The \e}pn sequence allows a user to display media like an image or open a
web page. However, all unknown media types are handled with the
media_unknown_handle function which executes xdg-open against the file type.
This creates a large attack surface that allows a remotely introduced
executable file to be executed when that file's MIME type is registered for
xdg-open.

See the linked bug for full info.

Ross
--- End Message ---
--- Begin Message ---
Source: terminology
Source-Version: 1.3.1-1

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

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

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

Debian distribution maintenance software
pp.
Ross Vandegrift  (supplier of updated terminology 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: Sun, 16 Dec 2018 10:28:36 -0800
Source: terminology
Binary: terminology terminology-data
Architecture: source
Version: 1.3.1-1
Distribution: unstable
Urgency: high
Maintainer: Debian Pkg-e Team 
Changed-By: Ross Vandegrift 
Closes: 916630
Description: 
 terminology-data - Enlightenment efl based terminal emulator data
 terminology - Enlightenment efl based terminal emulator
Changes:
 terminology (1.3.1-1) unstable; urgency=high
 .
   * New upstream release.
 + Fix for CVE-2018-20167: Disable special escape handling for unknown media
   types (Closes: #916630).
   * d/p/0002-Minor-manpage-improvements.patch: drop, applied upstream
Checksums-Sha1: 
 faecbdaea8c66c45e04b5732d3cf225c79c532bc 2099 terminology_1.3.1-1.dsc
 b36a315edc317dbbf3062841dafac8a5b2df8590 4851556 terminology_1.3.1.orig.tar.xz
 681599bc89f8c2f0f531741ceb2ee68b470e7af7 9416 terminology_1.3.1-1.debian.tar.xz
Checksums-Sha256: 
 925fdde970656774a401b6f342b8866941724d3899dd28a415684a5ad6be078f 2099 
terminology_1.3.1-1.dsc
 5f8abe4a2a2dd0270c32f2c4f93078a7f759e067b6e8cf998994a06342948981 4851556 
terminology_1.3.1.orig.tar.xz
 90d3b141209d86955dd8c94269a3adc59a655084b033be592c93c12cdbbc9f58 9416 
terminology_1.3.1-1.debian.tar.xz
Files: 
 a3f14e8a2e87a7477b19a2e96b4cfdb4 2099 x11 optional terminology_1.3.1-1.dsc
 f8da11f61edf1d049bafac6c6d7a16f5 4851556 x11 optional 
terminology_1.3.1.orig.tar.xz
 1887d4a9e1f3ca79c9022c9f2c9b3d4f 9416 x11 optional 
terminology_1.3.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAlwX6UUACgkQpU8BhUOC
FIQ83g//W9ckTy+zd/KZjLiQYrPAyoCuJeo/JLBmPlQEQYa3awDusDcEuVmvAAuU
i0GBM7oz3P68qu174XR4eehNvSmlWtON81qJpsZl9dwy1155wTT+FEoiu6FvJx3l
PDmwaTSZiQTPlth1UEstCmFzJ2YPSZBTvaCeTjqNE1V2MoJOfGezHrKq9RrvUVSM
VuBeT3aVaL1EGIoDDHDm/gdNoSO+NQe1sIjr+gKuLyKhdznoX1HHcSlKCUdZzNgN
uQ0VFfAJZ056psqCSXs+WP2mIS7Bc7KgsCC6s5klIb0K2nkX7XyPzLhyzLbxUc4f
W6ueWsgAnSAINnhQuj7mrQnNZb1e+v8aj8c+m2ZoR9izapo/yC2Q+bfKcdxrS3O8
RLmUAN0pbo6ojtHKFtlbBHPyj1FMfLcTMmjInnderKTlZZ76LqHGDbGsuHvz+r+3
9vj1759LjnSuwJPP4z2wFy7B1gkQCFE1JohoxZ52q8lMIng66Cz/Prc8cPhvihRJ
wUeZzZpAGrJ1PVYeB293LiDwIgKJVpd/0WB9dNRyCt/XJETdSXycIpywRZ/r7TuW
0Oe+Ez6/L8T4EO2Wqpoyv82leMcYvaRwPy5sNyaEyhDAjaOhgd/+W1WaADzYHZv0
THrMkum+Ttmz0GxLSFBrUK+c/VEt1chqZVOF8ErOq2FiF++Xyy8=
=Zsry
-END PGP SIGNATURE End Message ---

Bug#916683: libgnutls30: breaks msmtp 1.6.7-1

[Andreas Metzler]

Control: reassign -1 msmtp 1.6.7-1
Control: tags -1 fixed-upstream

On 2018-12-17 Jonas Smedegaard  wrote:
> Package: libgnutls30
> Version: 3.6.5-2
> Severity: serious
> Justification: Policy 3.5

> I use msmtp, and it worked fine until few days ago,
> with msmtp 1.6.7-1 and libgnutls30 3.5.19-1+b1.

> Upgrading to libgnutls30 3.6.5-2 breaks msmtp:
> Any attempt at connecting to a TLS-secured site gets disconnected.

FWIW I have had successful connections against exim4 (gnutls 3.5 and
3.6). Which host are you trying to connect to?

> Seems liek backwards-incompatible ABI change to me,
> which I believe should be handled in coordination with its
> reverse dependencies.  Hence the severity.

It is not an API change but a side effect of different handshake with
TLS1.3, now GNUTLS_E_AGAIN can be returned for blocking sockets.

See 
https://github.com/marlam/msmtp-mirror/commit/ec043e5375d0ecd5ab987e53d0ebfecfc1de0858

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


signature.asc
Description: PGP signature

Bug#916710: info-beamer FTBFS with glew 2.1.0

[Adrian Bunk]

Source: info-beamer
Version: 1.0~pre3+dfsg-0.1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/info-beamer.html

...
In file included from main.c:25:
/usr/include/GL/glext.h:12066:25: error: conflicting types for 
'PFNGLFRAGMENTLIGHTFVSGIXPROC'
 typedef void (APIENTRYP PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum 
pname, const GLfloat *params);
 ^~~~
In file included from main.c:23:
/usr/include/GL/glew.h:18734:28: note: previous declaration of 
'PFNGLFRAGMENTLIGHTFVSGIXPROC' was here
 typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum 
pname, GLfloat* params);
^~~~
In file included from main.c:25:
/usr/include/GL/glext.h:12068:25: error: conflicting types for 
'PFNGLFRAGMENTLIGHTIVSGIXPROC'
 typedef void (APIENTRYP PFNGLFRAGMENTLIGHTIVSGIXPROC) (GLenum light, GLenum 
pname, const GLint *params);
 ^~~~
In file included from main.c:23:
/usr/include/GL/glew.h:18736:28: note: previous declaration of 
'PFNGLFRAGMENTLIGHTIVSGIXPROC' was here
 typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTIVSGIXPROC) (GLenum light, GLenum 
pname, GLint* params);
^~~~
In file included from main.c:25:
/usr/include/GL/glext.h:12070:25: error: conflicting types for 
'PFNGLFRAGMENTLIGHTMODELFVSGIXPROC'
 typedef void (APIENTRYP PFNGLFRAGMENTLIGHTMODELFVSGIXPROC) (GLenum pname, 
const GLfloat *params);
 ^
In file included from main.c:23:
/usr/include/GL/glew.h:18730:28: note: previous declaration of 
'PFNGLFRAGMENTLIGHTMODELFVSGIXPROC' was here
 typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTMODELFVSGIXPROC) (GLenum pname, 
GLfloat* params);
^
...

Bug#916709: fritzing: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Package: src:fritzing
Version: 0.9.3b+dfsg-7
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with dpkg-buildpackage -A but it failed:


[...]

make[2]: Entering directory '/<>/fritzing-0.9.3b+dfsg'
make[2]: Nothing to be done for 'first'.
make[2]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
make[1]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   dh_auto_install -i
make V=1 -j1 install 
DESTDIR=/<>/fritzing-0.9.3b\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no 
INSTALL_ROOT=/<>/fritzing-0.9.3b\+dfsg/debian/tmp
make[1]: Entering directory '/<>/fritzing-0.9.3b+dfsg'
make -f Makefile.Release install
make[2]: Entering directory '/<>/fritzing-0.9.3b+dfsg'
/usr/lib/qt5/bin/qmake -install qinstall -exe Fritzing 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/bin/Fritzing
: /<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/bin/Fritzing
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/fritzing.desktop 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/applications/fritzing.desktop
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/Fritzing.1 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/man/man1/Fritzing.1
install -D -m 0644 
/<>/fritzing-0.9.3b+dfsg/resources/images/fritzing_icon.png 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/icons/fritzing.png
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/sketches 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/sketches
find /<>/fritzing-0.9.3b+dfsg/translations -name *.qm -size +128c 
-exec cp -pr {} 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/translations \;
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/translations/syntax/arduino.xml 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/translations/syntax/arduino.xml
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/translations/syntax/picaxe.xml 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/translations/syntax/picaxe.xml
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/translations/syntax/styles.xml 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/translations/syntax/styles.xml
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/help 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/help
make[2]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
make[1]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
   debian/rules override_dh_install
make[1]: Entering directory '/<>/fritzing-0.9.3b+dfsg'
dh_install
convert 
/<>/fritzing-0.9.3b+dfsg/debian/fritzing/usr/share/pixmaps/fritzing_icon.png
 -resize 32x32 \

/<>/fritzing-0.9.3b+dfsg/debian/fritzing/usr/share/pixmaps/fritzing_icon.xpm
convert-im6.q16: unable to open image 
`/<>/fritzing-0.9.3b+dfsg/debian/fritzing/usr/share/pixmaps/fritzing_icon.png':
 No such file or directory @ error/blob.c/OpenBlob/2874.
convert-im6.q16: no images defined 
`/<>/fritzing-0.9.3b+dfsg/debian/fritzing/usr/share/pixmaps/fritzing_icon.xpm'
 @ error/convert.c/ConvertImageCommand/3258.
make[1]: *** [debian/rules:23: override_dh_install] Error 1
make[1]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
make: *** [debian/rules:12: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_install into override_dh_install-arch and
override_dh_install-indep.

While we are at it, please consider uploading in source-only form
(dpkg-buildpackage -S) so that this kind of bugs never propagate to
testing.

Thanks.

Bug#916706: python-cobra FTBFS with python-pip 18.1

[Adrian Bunk]

Source: python-cobra
Version: 0.13.4-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-cobra.html

...
= test session starts ==
platform linux -- Python 3.6.8rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
benchmark: 3.1.1 (defaults: timer=time.perf_counter disable_gc=False 
min_rounds=5 min_time=0.05 max_time=1.0 calibration_precision=10 
warmup=False warmup_iterations=10)
rootdir: /build/1st/python-cobra-0.13.4, inifile: setup.cfg
plugins: benchmark-3.1.1
collected 0 items / 1 errors

 ERRORS 
__ ERROR collecting  ___
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:430: in 
_importconftest
return self._conftestpath2mod[conftestpath]
E   KeyError: 
local('/build/1st/python-cobra-0.13.4/.pybuild/cpython3_3.6_cobra/build/cobra/test/conftest.py')

During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/pipdeptree.py:17: in 
from pip._internal import get_installed_distributions
E   ImportError: cannot import name 'get_installed_distributions'

During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:436: in 
_importconftest
mod = conftestpath.pyimport()
/usr/lib/python3/dist-packages/py/_path/local.py:668: in pyimport
__import__(modname)
cobra/__init__.py:11: in 
from cobra import flux_analysis, io
cobra/flux_analysis/__init__.py:3: in 
from cobra.flux_analysis.gapfilling import gapfill
cobra/flux_analysis/gapfilling.py:8: in 
from cobra.core import Model
cobra/core/__init__.py:6: in 
from cobra.core.gene import Gene
cobra/core/gene.py:13: in 
from cobra.util import resettable
cobra/util/__init__.py:7: in 
from cobra.util.util import *
cobra/util/util.py:5: in 
from depinfo import print_dependencies
/usr/lib/python3/dist-packages/depinfo/__init__.py:27: in 
from depinfo.info import *
/usr/lib/python3/dist-packages/depinfo/info.py:24: in 
from pipdeptree import build_dist_index, construct_tree
/usr/lib/python3/dist-packages/pipdeptree.py:20: in 
from pip import get_installed_distributions, FrozenRequirement
E   ImportError: cannot import name 'get_installed_distributions'

During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/py/_path/common.py:377: in visit
for x in Visitor(fil, rec, ignore, bf, sort).gen(self):
/usr/lib/python3/dist-packages/py/_path/common.py:429: in gen
for p in self.gen(subdir):
/usr/lib/python3/dist-packages/py/_path/common.py:418: in gen
dirs = self.optsort([p for p in entries
/usr/lib/python3/dist-packages/py/_path/common.py:419: in 
if p.check(dir=1) and (rec is None or rec(p))])
/usr/lib/python3/dist-packages/_pytest/main.py:601: in _recurse
ihook = self.gethookproxy(dirpath)
/usr/lib/python3/dist-packages/_pytest/main.py:418: in gethookproxy
my_conftestmodules = pm._getconftestmodules(fspath)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:414: in 
_getconftestmodules
mod = self._importconftest(conftestpath)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:453: in 
_importconftest
raise ConftestImportFailure(conftestpath, sys.exc_info())
E   _pytest.config.ConftestImportFailure: 
(local('/build/1st/python-cobra-0.13.4/.pybuild/cpython3_3.6_cobra/build/cobra/test/conftest.py'),
 (, ImportError("cannot import name 
'get_installed_distributions'",), ))
=== warnings summary ===
cobra/flux_analysis/gapfilling.py:83
  
/build/1st/python-cobra-0.13.4/.pybuild/cpython3_3.6_cobra/build/cobra/flux_analysis/gapfilling.py:83:
 DeprecationWarning: invalid escape sequence \s
"""

cobra/core/gene.py:248
  
/build/1st/python-cobra-0.13.4/.pybuild/cpython3_3.6_cobra/build/cobra/core/gene.py:248:
 DeprecationWarning: invalid escape sequence \(
the_gene_re = re.compile('(^|(?<=( |\()))%s(?=( |\)|$))' %

cobra/core/gene.py:262
  
/build/1st/python-cobra-0.13.4/.pybuild/cpython3_3.6_cobra/build/cobra/core/gene.py:262:
 DeprecationWarning: invalid escape sequence \(
other_gene_re = re.compile('(^|(?<=( |\()))%s(?=( |\)|$))' %

/usr/share/python-wheels/colorama-0.3.7-py2.py3-none-any.whl/colorama/ansitowin32.py:49
  
/usr/share/python-wheels/colorama-0.3.7-py2.py3-none-any.whl/colorama/ansitowin32.py:49:
 DeprecationWarning: invalid escape sequence \[

/usr/share/python-wheels/colorama-0.3.7-py2.py3-none-any.whl/colorama/ansitowin32.py:50
  
/usr/share/python-wheels/colorama-0.3.7-py2.py3-none-any.whl/colorama/ansitowin32.py:50:
 DeprecationWarning: invalid escape sequence \]

/usr/share/python-wheels/colorama-0.3.7-py2.py3-none-any.whl/colorama/ansitowin32.py:49
  

Processed: [bts-link] source package akregator

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package akregator
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #910852 (http://bugs.debian.org/910852)
> # Bug title: Akregator crashes very often, WebEngine thread safety issue
> #  * http://bugs.kde.org/show_bug.cgi?id=371511
> #  * remote status changed: REOPENED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 910852 + fixed-upstream
Bug #910852 [akregator] Akregator crashes very often, WebEngine thread safety 
issue
Added tag(s) fixed-upstream.
> usertags 910852 - status-REOPENED
Usertags were: status-REOPENED.
Usertags are now: .
> usertags 910852 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

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

Bug#907396: marked as done (kopano-server: Tools all fail with: MAPI error 80040111 (MAPI_E_LOGON_FAILED))

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 18:31:59 +0100
with message-id 
and subject line Re: Bug#907396: kopano-server: Tools all fail with: MAPI error 
80040111 (MAPI_E_LOGON_FAILED)
has caused the Debian Bug report #907396,
regarding kopano-server: Tools all fail with: MAPI error 80040111 
(MAPI_E_LOGON_FAILED)
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.)


-- 
907396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kopano-server
Version: 8.6.5-1
Severity: important

Dear Maintainer,

Trying to get Kopano to run, but all tools fail with:
root$ kopano-cli --create-store
[error  ] virtual HRESULT M4LMAPISession::OpenMsgStore(ULONG_PTR, ULONG, const 
ENTRYID*, LPCIID, ULONG, IMsgStore**): msp>Logon failed: logon failed 
(80040111)MAPI error 80040111 (MAPI_E_LOGON_FAILED)

On the forum they state that: [SOLVED] in kopanocore-8.6.80.1420-1.x86_64 built 
from sources
https://forum.kopano.io/topic/1522/solved-db-backend-kopano-cli-mapi-error-80040111-mapi_e_logon_failed/9

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

Kernel: Linux 4.17.0-3-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kopano-server depends on:
ii  dbconfig-common 2.0.9
ii  debconf [debconf-2.0]   1.5.69
ii  kopano-common   8.6.5-1
ii  kopano-libs 8.6.5-1
ii  libc6   2.27-5
ii  libcom-err2 1.44.3-1
ii  libgcc1 1:8.2.0-4
ii  libgsoap-2.8.60 2.8.60-2
ii  libgssapi-krb5-21.16-2
ii  libicu6060.2-6
ii  libk5crypto31.16-2
ii  libkrb5-3   1.16-2
ii  libldap-2.4-2   2.4.46+dfsg-5
ii  libmariadbclient18  1:10.1.35-1
ii  libpam0g1.1.8-3.8
ii  libssl1.1   1.1.0h-4
ii  libstdc++6  8.2.0-4
ii  libuuid12.32.1-0.1
ii  lsb-base9.20170808
ii  mariadb-client  1:10.1.35-1
ii  mariadb-client-10.1 [virtual-mysql-client]  1:10.1.35-1
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages kopano-server recommends:
ii  mariadb-server  1:10.1.35-1

kopano-server suggests no packages.

-- debconf information:
  kopano-server/mysql/admin-pass: (password omitted)
  kopano-server/password-confirm: (password omitted)
  kopano-server/mysql/app-pass: (password omitted)
  kopano-server/app-password-confirm: (password omitted)
  kopano-server/remote/host: localhost
* kopano-server/mysql/admin-user: root
* kopano-server/dbconfig-install: true
* kopano-server/install-error: ignore
* kopano-server/db/dbname: kopanoserver
  kopano-server/internal/skip-preseed: false
  kopano-server/database-type: mysql
  kopano-server/remote/port:
  kopano-server/internal/reconfiguring: false
* kopano-server/passwords-do-not-match:
  kopano-server/remote/newhost:
  kopano-server/dbconfig-upgrade: true
  kopano-server/upgrade-backup: true
  kopano-server/purge: false
* kopano-server/dbconfig-reinstall: true
* kopano-server/mysql/method: Unix socket
* kopano-server/db/app-user: kopano-server@localhost
  kopano-server/missing-db-package-error: abort
  kopano-server/dbconfig-remove: true
  kopano-server/upgrade-error: abort
  kopano-server/remove-error: abort
--- End Message ---
--- Begin Message ---
Version: 8.6.90-1

Hello Teun,

Am 27.08.18 um 16:42 schrieb Teun Kloosterman:
> Trying to get Kopano to run, but all tools fail with:
> root$ kopano-cli --create-store
> [error  ] virtual HRESULT M4LMAPISession::OpenMsgStore(ULONG_PTR, ULONG, 
> const ENTRYID*, LPCIID, ULONG, IMsgStore**): msp>Logon failed: logon failed 
> (80040111)MAPI error 80040111 (MAPI_E_LOGON_FAILED)
> 
> On the forum they state that: [SOLVED] in kopanocore-8.6.80.1420-1.x86_64 
> built from sources
> https://forum.kopano.io/topic/1522/solved-db-backend-kopano-cli-mapi-error-80040111-mapi_e_logon_failed/9

some hours ago we uploaded the recent beta 

Bug#916019: marked as done (zfs-fuse FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 17:22:33 +
with message-id 
and subject line Bug#916019: fixed in zfs-fuse 0.7.0-19
has caused the Debian Bug report #916019,
regarding zfs-fuse FTBFS with glibc 2.28
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.)


-- 
916019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zfs-fuse
Version: 0.7.0-18
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zfs-fuse.html

...
lib/libsolcompat/getmntany.c: In function 'getextmntent':
lib/libsolcompat/getmntany.c:89:19: warning: implicit declaration of function 
'major' [-Wimplicit-function-declaration]
   mp->mnt_major = major(st.st_dev);
   ^
lib/libsolcompat/getmntany.c:90:19: warning: implicit declaration of function 
'minor'; did you mean 'mknod'? [-Wimplicit-function-declaration]
   mp->mnt_minor = minor(st.st_dev);
   ^
...
gcc -o cmd/zdb/zdb -pipe -Wall -ggdb cmd/zdb/zdb.o cmd/zdb/zdb_il.o 
cmd/zdb/ptrace.o lib/libavl/libavl.a lib/libnvpair/libnvpair-user.a 
lib/libumem/libumem.a lib/libzfs/libzfs.a lib/libzpool/libzpool-user.a 
lib/libzfscommon/libzfscommon-user.a lib/libuutil/libuutil.a 
lib/libsolcompat/libsolcompat.a -lrt -lpthread -ldl -lz -lm -laio -lcrypto
/usr/bin/ld: lib/libsolcompat/libsolcompat.a(getmntany.o): in function 
`getextmntent':
/build/1st/zfs-fuse-0.7.0/src/lib/libsolcompat/getmntany.c:89: undefined 
reference to `major'
/usr/bin/ld: /build/1st/zfs-fuse-0.7.0/src/lib/libsolcompat/getmntany.c:90: 
undefined reference to `minor'
collect2: error: ld returned 1 exit status
scons: *** [cmd/zdb/zdb] Error 1
--- End Message ---
--- Begin Message ---
Source: zfs-fuse
Source-Version: 0.7.0-19

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

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

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated zfs-fuse 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: Mon, 17 Dec 2018 17:48:52 +0100
Source: zfs-fuse
Binary: zfs-fuse
Architecture: source
Version: 0.7.0-19
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Hilko Bengen 
Description:
 zfs-fuse   - ZFS on FUSE
Closes: 916019
Changes:
 zfs-fuse (0.7.0-19) unstable; urgency=medium
 .
   * QA upload.
   * Migrate Git repository to Salsa, fix VCS headers
   * Add several missing #include statements that lead to build failures
 with glibc 2.28 (Closes: #916019)
Checksums-Sha1:
 d13aab04be6ff7b7daca5736bca3cefcaf1efa3a 2073 zfs-fuse_0.7.0-19.dsc
 b28dda87780be8d6d2ee2803ac57b10fc6d6d8a1 26432 zfs-fuse_0.7.0-19.debian.tar.xz
 7a8fbd5a0f383e18f45dcf58218285ef4e276873 6280 
zfs-fuse_0.7.0-19_source.buildinfo
Checksums-Sha256:
 c9c65fc8a76bd0555784f3ef93567c864443ad98560b92f0327d35075df838b9 2073 
zfs-fuse_0.7.0-19.dsc
 2eeaaa36835a0f4f0ec20df212a261ab892a0d3640defd49fd2648ba1bf9a3aa 26432 
zfs-fuse_0.7.0-19.debian.tar.xz
 9b2561b595445d518b32bb4e1fd63b1cf8e568b9d7a3daee1486315ef0eda6a0 6280 
zfs-fuse_0.7.0-19_source.buildinfo
Files:
 389e8ddd03cca61c5c9f37492a380b3c 2073 otherosfs optional zfs-fuse_0.7.0-19.dsc
 202181806acbe2440dc59e4269256d2a 26432 otherosfs optional 
zfs-fuse_0.7.0-19.debian.tar.xz
 bfa2231ad5048312057a54dafa1d4652 6280 otherosfs optional 
zfs-fuse_0.7.0-19_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlwX0/wSHGJlbmdlbkBk
ZWJpYW4ub3JnAAoJEHW3EGNcITp+0VAQAIsSVhzYdaK0U2wa1XHQNuuLDuJaiy4+
PSPLcRQJztWdacJfV+6FwkSCGJ642mwn18lB3cQsE0bEqfI9OVijKiQIycbbjAEE
2g0n/mxsaRp5t0zaPwC77PO4/oq2KSyo+1mia10FAN7JEgj2Ff37N/15Dmgg97Sc
dp9EIuapUi9oVxx424V7VNEC48yHsk/pJ7g4dUIA/gZhmIHkwDcxb1Lt2SmO/J2d
SItUdRXVwWLsLu/dHHM/FVkN3YEqp51XoPwkNBsmcDtNtoq6dEH36zXGJnwA8MBP
r52lyoka1FKko4uhb4cLJ1NQqjSCxhiB7PpdTG8ZJinkOmUOaRlyZyLQnKa++miO
+21djOtK1WrAIvehCjuBSqlEIctGLz8RoHcwIxQbPseFzh9R+GpUpImHQBCB9U3K
wyT2KOpujSU2mxe2qL6BU/naRbGv1eOh2wDl9FzIhrG9lqGVdGngTnfIieguvi93
eb2ZlAkcfjlaltHRi7j/wm6fJBVq8c2oQ9zvQjmqzabDcr/qje1ucik2m+nhQuJ9

Bug#916703: mando FTBFS with Python 3.7

[Adrian Bunk]

Source: mando
Version: 0.6.4-3
Severity: serious
Tags: ftbfs

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd 
/build/1st/mando-0.6.4/.pybuild/cpython3_3.7_mando/build; python3.7 -m pytest 
= test session starts ==
platform linux -- Python 3.7.2rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
rootdir: /build/1st/mando-0.6.4, inifile:
collected 0 items

= no tests ran in 0.00 seconds =
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=5: cd 
/build/1st/mando-0.6.4/.pybuild/cpython3_3.7_mando/build; python3.7 -m pytest 
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned 
exit code 13
make: *** [debian/rules:18: build] Error 25

Bug#916702: freezegun FTBFS: test failures

[Adrian Bunk]

Source: freezegun
Version: 0.3.10-2
Severity: serious
Tags: ftbfs

Some recent change in unstable makes freezegun FTBFS:

https://tests.reproducible-builds.org/debian/history/freezegun.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/freezegun.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/freezegun-0.3.10'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
for python in python2.7; do \
$python /usr/bin/nosetests tests; \
done
SS..S
NameStmts   Miss  Cover   Missing
-
freezegun/__init__.py   8  0   100%
freezegun/api.py  422 2893%   30-31, 35-36, 40-41, 45, 50, 
72-73, 89, 158, 406, 443, 554, 556, 563-565, 581, 587, 604-605, 633-635, 654-657
-
TOTAL 430 2893%
--
Ran 93 tests in 2.412s

OK (SKIP=3)
for python in python3.6 python3.7; do \
$python /usr/bin/nosetests tests; \
done
...S.
NameStmts   Miss  Cover   Missing
-
freezegun/__init__.py   8  0   100%
freezegun/_async.py11  191%   12
freezegun/api.py  422 2195%   30-31, 35-36, 50, 72-73, 89, 158, 
443, 554, 556, 563-565, 587, 633-635, 654-657
-
TOTAL 441 2295%
--
Ran 93 tests in 1.868s

OK (SKIP=1)
...S.FF..
==
FAIL: Test that we can go back in time after setting a future date.
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/build/1st/freezegun-0.3.10/tests/test_uuid.py", line 28, in 
test_uuid1_future
assert_equal(time_from_uuid(uuid.uuid1()), future_target)
AssertionError: FakeDatetime(2020, 1, 19, 23, 8, 44, 720600) != 
datetime.datetime(2056, 2, 6, 14, 3, 21)
'FakeDatetime(2020, 1, 19, 23, 8, 44, 720600) != datetime.datetime(2056, 2, 
6, 14, 3, 21)' = '%s != %s' % _common_shorten_repr(FakeDatetime(2020, 1, 19, 
23, 8, 44, 720600), datetime.datetime(2056, 2, 6, 14, 3, 21))
'FakeDatetime(2020, 1, 19, 23, 8, 44, 720600) != datetime.datetime(2056, 2, 
6, 14, 3, 21)' = self._formatMessage('FakeDatetime(2020, 1, 19, 23, 8, 44, 
720600) != datetime.datetime(2056, 2, 6, 14, 3, 21)', 'FakeDatetime(2020, 1, 
19, 23, 8, 44, 720600) != datetime.datetime(2056, 2, 6, 14, 3, 21)')
>>  raise self.failureException('FakeDatetime(2020, 1, 19, 23, 8, 44, 720600) 
>> != datetime.datetime(2056, 2, 6, 14, 3, 21)')


==
FAIL: Test that we can go forward in time after setting some time in the past.
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/build/1st/freezegun-0.3.10/tests/test_uuid.py", line 42, in 
test_uuid1_past
assert_equal(time_from_uuid(uuid.uuid1()), past_target)
AssertionError: FakeDatetime(2020, 1, 19, 23, 8, 44, 748940) != 
datetime.datetime(1978, 7, 6, 23, 6, 31)
'FakeDatetime(2020, 1, 19, 23, 8, 44, 748940) != datetime.datetime(1978, 7, 
6, 23, 6, 31)' = '%s != %s' % _common_shorten_repr(FakeDatetime(2020, 1, 19, 
23, 8, 44, 748940), datetime.datetime(1978, 7, 6, 23, 6, 31))
'FakeDatetime(2020, 1, 19, 23, 8, 44, 748940) != datetime.datetime(1978, 7, 
6, 23, 6, 31)' = self._formatMessage('FakeDatetime(2020, 1, 19, 23, 8, 44, 
748940) != datetime.datetime(1978, 7, 6, 23, 6, 31)', 'FakeDatetime(2020, 1, 
19, 23, 8, 44, 748940) != datetime.datetime(1978, 7, 6, 23, 6, 31)')
>>  raise self.failureException('FakeDatetime(2020, 1, 19, 23, 8, 44, 748940) 
>> != datetime.datetime(1978, 7, 6, 23, 6, 31)')


NameStmts   Miss  Cover   Missing
-
freezegun/__init__.py   8  0   100%
freezegun/_async.py11  191%   12
freezegun/api.py  422 1995%   35-36, 50, 72-73, 89, 158, 443, 
554, 556, 563-565, 587, 633-635, 654-657

Bug#916701: dfwinreg FTBFS with Python 3.7

[Adrian Bunk]

Source: dfwinreg
Version: 20180712-1
Severity: serious
Tags: ftbfs

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

...
==
FAIL: testGlob2Regex (glob2regex.Glob2RegexTest)
Tests the Glob2Regex function.
--
Traceback (most recent call last):
  File "/build/1st/dfwinreg-20180712/tests/glob2regex.py", line 59, in 
testGlob2Regex
self.assertEqual(regex, expected_regex)
AssertionError: '[.^$*+?{}|()]' != '[.^$*+?{}\\|()]'
- [.^$*+?{}\\|()]
+ [.^$*+?{}\\\|()]
?+


--
Ran 76 tests in 0.840s

FAILED (failures=1, skipped=1)
Using Python version 3.7.2rc1 (default, Dec 12 2018, 06:25:49) 
[GCC 8.2.0]
Checking availability and versions of dependencies.
[OK]dfdatetime version: 20180704
[OK]dtfabric version: 20180808
[OK]pyregf version: 20170130
[OK]yaml version: 3.13

Checking availability and versions of test dependencies.
[OK]mock version: 2.0.0

make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1

Bug#915481: marked as done (sludge FTBFS with glew 2.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 16:35:57 +
with message-id 
and subject line Bug#915481: fixed in sludge 2.2.2-2
has caused the Debian Bug report #915481,
regarding sludge FTBFS with glew 2.1.0
to be marked as done.

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

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


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

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

...
mv -f $depbase.Tpo $depbase.Po
In file included from SpriteBankEditorMain.cpp:32:
/usr/include/GL/glext.h:12066:105: error: conflicting declaration 'typedef void 
(* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, const GLfloat*)'
 typedef void (APIENTRYP PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum 
pname, const GLfloat *params);

 ^
In file included from SpriteBankEditorMain.cpp:28:
/usr/include/GL/glew.h:18734:28: note: previous declaration as 'typedef void (* 
PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, GLfloat*)'
 typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum 
pname, GLfloat* params);
^~~~
--- End Message ---
--- Begin Message ---
Source: sludge
Source-Version: 2.2.2-2

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

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

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sludge 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: Mon, 17 Dec 2018 17:05:57 +0100
Source: sludge
Binary: sludge-engine sludge-devkit sludge-compiler sludge-doc
Architecture: source
Version: 2.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Tobias Hansen 
Description:
 sludge-compiler - Compiler for SLUDGE adventure games
 sludge-devkit - Development tools for creating SLUDGE adventure games
 sludge-doc - Documentation for SLUDGE
 sludge-engine - Runtime engine for playing SLUDGE adventure games
Closes: 910321 915481
Changes:
 sludge (2.2.2-2) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure.
 (Closes: #910321)
 .
   [ Tobias Hansen ]
   * Add patch dont-include-glext.h.patch. (Closes: #915481)
Checksums-Sha1:
 bdd61ec157a26c83387a3b214dae75f5142d2f0d 2306 sludge_2.2.2-2.dsc
 0406f159f2bfdfdaba293a41c1b746eee4d39d68 75516 sludge_2.2.2-2.debian.tar.xz
 b3a3c0481fac8a2901a4c04c376900b2b85afc8a 13288 sludge_2.2.2-2_source.buildinfo
Checksums-Sha256:
 28d6665eb4c9e06344183a4e2d64b5769a7756e490d6ae564908c1596453be23 2306 
sludge_2.2.2-2.dsc
 63d96427325089e1ac141cadf6e4d8cf2ef9dce992ca65c5c901195e4efb1a9e 75516 
sludge_2.2.2-2.debian.tar.xz
 4af1ad59af6cb3d35454e5de18bdf6324a68f09f9978b35c034cc63cd1db8597 13288 
sludge_2.2.2-2_source.buildinfo
Files:
 7745f55249e0cf5dd6994fa3a9f91229 2306 games optional sludge_2.2.2-2.dsc
 1cc3d6c8f92ca13ded46cd7222b212d7 75516 games optional 
sludge_2.2.2-2.debian.tar.xz
 c9dc2b8e25fbc00fb5f7a64f9ba76083 13288 games optional 
sludge_2.2.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoH46ol3M2u2mYo0kjIIWnY7OzSoFAlwXyu0ACgkQjIIWnY7O
zSoXqhAAlSjoUsW3q4ljnx0eAh3perFeZgNRLEM5cMWXVHchUmxk11LQdMvliTKl
SibgnSjXrL6ApIipuVb0qSStYbxKfnq8ejGTOJfeIuRihb2fgR7kG+iFSwCK2nlR
H2LQXDE63AQ2OY4tG9ZHBhCZZMg3HUSuM7kplhLjnYzojFZtW0Uk6TyLsGcZkz6E
M712pJtoUIfpk8L4paRCEbKYYqnIK3i8uBpuD+y3V7eAbZa3zxxmi+YgadSlr/fq
NFl5NxTUOHbhuo+62X/vQ2FpB1QSRSvDSPgqRmsCifl5ytytev2mu8XbXS48e+vt
f1hgQaGieWCNUzbGYRiL+sFxI8csYLvPZWEnbFAHyxfs05A1REGkOCnQkk5zNDan
fO+YfKJ9rnop/Zom0ugy+SiKKzxfxQArfAA7lQgTV2Ycrby/6C5QT3nhoLLnPJQk
SvVULAoPNTasbS+aa0+KRIgJfdja/qrEkON0FJ1ZIxKVbE0MlLnHbRMVQYrvg71e
HQGtIIlRzJ6KYEUsAJeR4AxuDX8oOAv3rRVHEZiZmYSL+/aXqrcFKNlRTs/8lbm7
BFxEehj71VWUZS35NAhXA0BItjZYjOhprWUT+ZjZ1rAL2fzMOy2vGhrLRt3iocH9
luRae/9a+3e36D69QZbAjkjUZDNcWT6BSUDILucbPdk4KxfKVxg=
=7dTS
-END PGP 

Bug#916140: python3-matplotlib-dbg: missing Breaks+Replaces: python-matplotlib-dbg (<< 3)

[Andreas Beckmann]

Hi Sandro,

On 2018-12-16 20:30, Sandro Tosi wrote:
> On Mon, Dec 10, 2018 at 12:57 PM Andreas Beckmann  wrote:
>>
>> Control: retitle -1 python3-matplotlib-dbg: missing Breaks+Replaces: 
>> python-matplotlib-dbg (<< 2.2.3-3)
>>
>> On 2018-12-10 17:47, Sandro Tosi wrote:
>>> On Mon, Dec 10, 2018 at 11:06 AM Andreas Beckmann  wrote:
>>>  is this right approach? there is a new src:matplotlib2 in experimetal
>>> NEW to drop py3k packages (so src:matplotlib2 will only ship python2
>>> and src:matplotlib will only ship py3k package), so that should remove
>>> the incompatibility?
>>
>> This will probably not change anything, but lets see what happens once
>> they clear new.
> 
> src:matplotlib2 (producing python-matplotlib*) has been accepted into
> experimental - mind giving this another try? thanks!

that doesn't change anything for the case of installing
python3-matplotlib-dbg (>= 3.0.2-1) on a system with
python-matplotlib-dbg (<< 2.2.3-3), which can easily happen (depending
on the unpack order chosen by apt/dpkg) while upgrading from testing or
(yesterdays) sid to (todays) sid (once you uploaded the two packages
from experimental to sid). So adding
  Breaks+Replaces: python-matplotlib-dbg (<< 2.2.3-3)
to python3-matplotlib-dbg seems to be the best solution to have clean
upgrade paths within testing/sid.


Andreas

Processed: forcemerge 914495 916656

[Debian Bug Tracking System]

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

> forcemerge 914495 916656
Bug #914495 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #914980 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #915178 {Done: Salvatore Bonaccorso } [src:linux] i915: 
unable to handle kernel NULL pointer dereference at 0008
Bug #915641 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: driver i915 crashed on GM45 chipset.
Bug #915645 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: Kernel 4.18-0-3 boots to a blank screen
Bug #915674 {Done: Salvatore Bonaccorso } [src:linux] i915 
driver crash on kernel 4.18.0-3 (buster/testing)
Bug #915954 {Done: Salvatore Bonaccorso } [src:linux] 
inteldrmfb: screen black in 4.18.0-3 (works in 4.18.0-2)
Bug #916090 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: Kernel update makes system unbootable: kernel-oops 
when loading "i915" module
Bug #916656 [src:linux] linux-image-4.18.0-3-amd64: (i915?) BUG: unable to 
handle kernel NULL pointer dereference at 0008
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=108850'.
Severity set to 'important' from 'serious'
Marked Bug as done
Marked as fixed in versions linux/4.19~rc2-1~exp1.
Marked as found in versions linux/4.18.20-1.
Added tag(s) fixed-upstream.
Bug #914980 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #915178 {Done: Salvatore Bonaccorso } [src:linux] i915: 
unable to handle kernel NULL pointer dereference at 0008
Bug #915641 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: driver i915 crashed on GM45 chipset.
Bug #915645 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: Kernel 4.18-0-3 boots to a blank screen
Bug #915674 {Done: Salvatore Bonaccorso } [src:linux] i915 
driver crash on kernel 4.18.0-3 (buster/testing)
Bug #915954 {Done: Salvatore Bonaccorso } [src:linux] 
inteldrmfb: screen black in 4.18.0-3 (works in 4.18.0-2)
Bug #916090 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: Kernel update makes system unbootable: kernel-oops 
when loading "i915" module
Merged 914495 914980 915178 915641 915645 915674 915954 916090 916656
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
914495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914495
914980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914980
915178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915178
915641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915641
915645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915645
915674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915674
915954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915954
916090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916090
916656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 916691

[Debian Bug Tracking System]

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

> tags 916691 + buster sid
Bug #916691 [src:cuyo] cuyo -- Not fit for next release
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#911693: librabbitmq: NMU ongoing

[Michael Fladischer]

Hi Gianfranco,

Am 17.12.2018 um 15:22 schrieb Gianfranco Costamagna:

I've prepared an NMU for librabbitmq (versioned as 0.9.0-0.2) and
uploaded it to unstable. Please feel free to tell me if I
should delay it longer.


thanks for the upload. Feel free to go ahead.

I was actually thinking of orphaning this package as I'm no longer using 
it in any project. Are you interested in taking over?


Regards,
Michael

Bug#913854: siril: diff for NMU version 0.9.9-1.1

[Adrian Bunk]

Control: tags 913854 + pending

Dear maintainer,

I've prepared an NMU for siril (versioned as 0.9.9-1.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru siril-0.9.9/debian/changelog siril-0.9.9/debian/changelog
--- siril-0.9.9/debian/changelog	2018-06-07 10:38:17.0 +0300
+++ siril-0.9.9/debian/changelog	2018-12-17 16:58:46.0 +0200
@@ -1,3 +1,10 @@
+siril (0.9.9-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with glibc 2.28. (Closes: #913854)
+
+ -- Adrian Bunk   Mon, 17 Dec 2018 16:58:46 +0200
+
 siril (0.9.9-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru siril-0.9.9/debian/patches/0001-Fixes-bug-with-next-release-of-glibc.patch siril-0.9.9/debian/patches/0001-Fixes-bug-with-next-release-of-glibc.patch
--- siril-0.9.9/debian/patches/0001-Fixes-bug-with-next-release-of-glibc.patch	1970-01-01 02:00:00.0 +0200
+++ siril-0.9.9/debian/patches/0001-Fixes-bug-with-next-release-of-glibc.patch	2018-12-17 16:58:24.0 +0200
@@ -0,0 +1,99 @@
+From 140d7356b390ff7ba52a93e8ae324596ed029df8 Mon Sep 17 00:00:00 2001
+From: lock042 
+Date: Wed, 4 Jul 2018 11:56:17 +
+Subject: [PATCH] Fixes bug with next release of glibc
+
+---
+ src/core/command.c  |  2 +-
+ src/core/proto.h|  5 ++---
+ src/core/siril.c| 10 +-
+ src/gui/callbacks.c |  2 +-
+ 4 files changed, 9 insertions(+), 10 deletions(-)
+
+diff --git a/src/core/command.c b/src/core/command.c
+index 7d44325..6a83759 100644
+--- a/src/core/command.c
 b/src/core/command.c
+@@ -358,7 +358,7 @@ int process_fdiv(int nb){
+ 	norm = atof(word[2]);
+ 	if (readfits(word[1], , NULL))
+ 		return -1;
+-	fdiv(, , norm);
++	siril_fdiv(, , norm);
+ 	adjust_cutoff_from_updated_gfit();
+ 	redraw(com.cvport, REMAP_ALL);
+ 	redraw_previews();
+diff --git a/src/core/proto.h b/src/core/proto.h
+index cc51643..cbae177 100644
+--- a/src/core/proto.h
 b/src/core/proto.h
+@@ -181,9 +181,8 @@ int	soper(fits *a, double scalar, char oper);
+ int	imoper(fits *a, fits *b, char oper);
+ int sub_background(fits* image, fits* background, int layer);
+ int 	addmax(fits *a, fits *b);
+-int	fdiv(fits *a, fits *b, float scalar);
+-int ndiv(fits *a, fits *b);
+-int fmul(fits *a, float coeff);
++int	siril_fdiv(fits *a, fits *b, float scalar);
++int siril_ndiv(fits *a, fits *b);
+ double 	gaussienne(double sigma, int size, double *gauss);
+ int 	unsharp(fits *,double sigma, double mult, gboolean verbose);
+ int	crop(fits *fit, rectangle *bounds);
+diff --git a/src/core/siril.c b/src/core/siril.c
+index 8e934a2..40cb298 100644
+--- a/src/core/siril.c
 b/src/core/siril.c
+@@ -260,8 +260,8 @@ int addmax(fits *a, fits *b) {
+ 	return 0;
+ }
+ 
+-/* If fdiv is ok, function returns 0. If overflow, fdiv returns 1*/
+-int fdiv(fits *a, fits *b, float coef) {
++/* If siril_fdiv is ok, function returns 0. If overflow, siril_fdiv returns 1*/
++int siril_fdiv(fits *a, fits *b, float coef) {
+ 	int i, layer;
+ 	int retvalue = 0;
+ 	double temp;
+@@ -289,7 +289,7 @@ int fdiv(fits *a, fits *b, float coef) {
+ 
+ /* normalized division a/b, stored in a, with max value equal to the original
+  * max value of a, for each layer. */
+-int ndiv(fits *a, fits *b) {
++int siril_ndiv(fits *a, fits *b) {
+ 	double *div;
+ 	int layer, i, nb_pixels;
+ 	if (a->rx != b->rx || a->ry != b->ry || a->naxes[2] != b->naxes[2]) {
+@@ -489,7 +489,7 @@ int ddp(fits *a, int level, float coeff, float sigma) {
+ 	unsharp(, sigma, 0, FALSE);
+ 	soper(, (double) level, OPER_ADD);
+ 	nozero(, 1);
+-	fdiv(a, , level);
++	siril_fdiv(a, , level);
+ 	soper(a, (double) coeff, OPER_MUL);
+ 	clearfits();
+ 	invalidate_stats_from_fit(a);
+@@ -824,7 +824,7 @@ static int preprocess(fits *brut, fits *offset, fits *dark, fits *flat, float le
+ 	}
+ 
+ 	if (com.preprostatus & USE_FLAT) {
+-		fdiv(brut, flat, level);
++		siril_fdiv(brut, flat, level);
+ 	}
+ 
+ 	return 0;
+diff --git a/src/gui/callbacks.c b/src/gui/callbacks.c
+index 3c9571e..0e35c5c 100644
+--- a/src/gui/callbacks.c
 b/src/gui/callbacks.c
+@@ -4775,7 +4775,7 @@ void on_button_bkg_correct_clicked(GtkButton *button, gpointer user_data) {
+ 		siril_log_message(_("Subtraction done ...\n"));
+ 		break;
+ 	case 1:
+-		if (ndiv(, _fit)) {
++		if (siril_ndiv(, _fit)) {
+ 			set_cursor_waiting(FALSE);
+ 			return;
+ 		}
+-- 
+2.11.0
+
diff -Nru siril-0.9.9/debian/patches/series siril-0.9.9/debian/patches/series
--- siril-0.9.9/debian/patches/series	2017-06-24 15:06:21.0 +0300
+++ siril-0.9.9/debian/patches/series	2018-12-17 16:58:46.0 +0200
@@ -1 +1,2 @@
 LICENSE_remover
+0001-Fixes-bug-with-next-release-of-glibc.patch

Processed: siril: diff for NMU version 0.9.9-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 913854 + pending
Bug #913854 [src:siril] siril ftbfs with glibc-2.28
Added tag(s) pending.

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

Bug#915371: marked as done (pivy: Coin3 cmake transition)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 15:00:26 +
with message-id 
and subject line Bug#915371: fixed in pivy 0.6.4-1~exp1
has caused the Debian Bug report #915371,
regarding pivy: Coin3 cmake transition
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.)


-- 
915371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pivy
Severity: grave
Justification: renders package unusable

Dear Maintainer,

coin3 is doing a transition to 4.0.0 using CMake as build system.

During the test the package FTBFS using the version that is in experimental. 
Please, check this version.



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

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/8 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pivy
Source-Version: 0.6.4-1~exp1

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

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

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

Debian distribution maintenance software
pp.
Kurt Kremitzki  (supplier of updated pivy 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, 15 Dec 2018 13:51:48 -0600
Source: pivy
Binary: python-pivy python3-pivy
Architecture: source amd64
Version: 0.6.4-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Kurt Kremitzki 
Description:
 python-pivy - Coin binding for Python
 python3-pivy - Coin binding for Python 3
Closes: 875099 915371
Changes:
 pivy (0.6.4-1~exp1) experimental; urgency=medium
 .
   [ Kurt Kremitzki ]
   * [fd3e9ff] Update d/watch to Bitbucket upstream
   * [1240704] New upstream version 0.6.4
   * [e146f09] Update packaging for 0.6.4 & Python 3 build
   * [32f691c] Update coin/soqt deps  (Closes: #915371)
   * [928033b] Update python3 build version
   * [1e62848] Use new setup.py
   * [bb4d9b1] Use multiarch cmake prefix path
   * [3ee4cb2] Add fakeheaders
   * [8af0d83] Add py37 patch
 .
   [ Leopold Palomo-Avellaneda ]
   * [082b614] Added patch to fix CMake Vars
   * [6444c2c][a3f8ccd] Added patch to make a workaround for Includes in swig
   * [b1cb822] Activating the patches
   * [e408ffc][52eb28e][3796801]
 Added cmake and qt5 correct build dependencies.
  Added QT_SELECT=qt5 to built against Qt5 (Closes: #875099)
   * [fb3f5a9] Bump Standards to 4.2.1. No changes
   * [3a0b6ea] Added description to a patch
 .
   [ Anton Gladky ]
   * [0496ce5] Fix typo in d/changelog
   * [2d065b0] Drop debian/source/options
Checksums-Sha1:
 cac23cb2082d4027addb869935c7a702541f4c7d 2433 pivy_0.6.4-1~exp1.dsc
 94d0aceaa4849eebf1b972b0011ceef3945df864 6556292 pivy_0.6.4.orig.tar.bz2
 69cb90a8e2c296883f90d519a23e4c75f7308140 5644 pivy_0.6.4-1~exp1.debian.tar.xz
 839053e9800f1886af4611309c49fcc881d73e4e 15746 
pivy_0.6.4-1~exp1_amd64.buildinfo
 273119bdd996e2cb2b69ba93f404b17c1013a65f 7332760 
python-pivy-dbgsym_0.6.4-1~exp1_amd64.deb
 d5dfe6742dadacde7b913e5944f87e551a7af967 2516712 
python-pivy_0.6.4-1~exp1_amd64.deb
 55e7ad829f7a52acfa4e6805f2f084c498125ff9 7380644 
python3-pivy-dbgsym_0.6.4-1~exp1_amd64.deb
 f0925723eb6171f763d0bd5c52a25b141ab48562 1608048 
python3-pivy_0.6.4-1~exp1_amd64.deb
Checksums-Sha256:
 91ff83be1f36fd5edd6c2dea45bf850a743e070f9076ff04908bfe3b2c8cf53f 2433 
pivy_0.6.4-1~exp1.dsc
 bd5cf50d167e64a397bed393f819b3df12e3c77d942df057e5c9bbc2b0ccffac 6556292 
pivy_0.6.4.orig.tar.bz2
 cf7b7c8cd87bcd0e8e671ab1c9c91f8bdc18d3d00f937095286639e370fd2206 5644 
pivy_0.6.4-1~exp1.debian.tar.xz
 29e0661ffa570e193213c666bddd1c8cc3d407a4bcd57a2362286703fc868b90 15746 
pivy_0.6.4-1~exp1_amd64.buildinfo
 d6f0fee4022ff9a94038171b7537ab01341252f64e406fd8bb48fd3fddff080b 7332760 
python-pivy-dbgsym_0.6.4-1~exp1_amd64.deb
 

Bug#915666: marked as done (linux: data corruption with blk-mq)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 15:00:24 +
with message-id 
and subject line Bug#915666: fixed in linux 4.19.9-1
has caused the Debian Bug report #915666,
regarding linux: data corruption with blk-mq
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.)


-- 
915666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.18.20-2
Severity: critical
Tags: upstream patch
Justification: causes serious data loss


Hi.

There's a bug in the blk-mq schedulers which may cause serious data
curruption...
See https://bugzilla.kernel.org/show_bug.cgi?id=201685

Seems like a patch was made recently,... maybe it would make sense
to cherry pick that one before it makes its way via the stable kernels.

AFAIU the discussions, at least 4.18 may be affected as well.


Cheers,
Chris.


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

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.19.9-1

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

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

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

Debian distribution maintenance software
pp.
Bastian Blank  (supplier of updated linux 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: Sun, 16 Dec 2018 19:45:54 +0100
Source: linux
Binary: linux-source-4.19 linux-support-4.19.0-1 linux-doc-4.19 linux-cpupower 
libcpupower1 libcpupower-dev usbip hyperv-daemons lockdep liblockdep4.19 
liblockdep-dev libbpf4.19 libbpf-dev linux-kbuild-4.19 linux-perf-4.19 
linux-bootwrapper-4.19.0-1 linux-headers-4.19.0-1-common 
linux-headers-4.19.0-1-common-rt linux-libc-dev linux-headers-4.19.0-1-all 
linux-headers-4.19.0-1-all-alpha linux-config-4.19 
kernel-image-4.19.0-1-alpha-generic-di nic-modules-4.19.0-1-alpha-generic-di 
nic-wireless-modules-4.19.0-1-alpha-generic-di 
nic-shared-modules-4.19.0-1-alpha-generic-di 
serial-modules-4.19.0-1-alpha-generic-di 
usb-serial-modules-4.19.0-1-alpha-generic-di 
ppp-modules-4.19.0-1-alpha-generic-di pata-modules-4.19.0-1-alpha-generic-di 
cdrom-core-modules-4.19.0-1-alpha-generic-di 
scsi-core-modules-4.19.0-1-alpha-generic-di 
scsi-modules-4.19.0-1-alpha-generic-di loop-modules-4.19.0-1-alpha-generic-di 
btrfs-modules-4.19.0-1-alpha-generic-di ext4-modules-4.19.0-1-alpha-generic-di
 isofs-modules-4.19.0-1-alpha-generic-di jfs-modules-4.19.0-1-alpha-generic-di 
xfs-modules-4.19.0-1-alpha-generic-di fat-modules-4.19.0-1-alpha-generic-di 
md-modules-4.19.0-1-alpha-generic-di 
multipath-modules-4.19.0-1-alpha-generic-di 
usb-modules-4.19.0-1-alpha-generic-di 
usb-storage-modules-4.19.0-1-alpha-generic-di 
input-modules-4.19.0-1-alpha-generic-di event-modules-4.19.0-1-alpha-generic-di 
mouse-modules-4.19.0-1-alpha-generic-di 
nic-pcmcia-modules-4.19.0-1-alpha-generic-di 
pcmcia-modules-4.19.0-1-alpha-generic-di 
nic-usb-modules-4.19.0-1-alpha-generic-di 
sata-modules-4.19.0-1-alpha-generic-di i2c-modules-4.19.0-1-alpha-generic-di 
crc-modules-4.19.0-1-alpha-generic-di crypto-modules-4.19.0-1-alpha-generic-di 
crypto-dm-modules-4.19.0-1-alpha-generic-di 
ata-modules-4.19.0-1-alpha-generic-di nbd-modules-4.19.0-1-alpha-generic-di 
squashfs-modules-4.19.0-1-alpha-generic-di 
virtio-modules-4.19.0-1-alpha-generic-di zlib-modules-4.19.0-1-alpha-generic-di
 compress-modules-4.19.0-1-alpha-generic-di 
fuse-modules-4.19.0-1-alpha-generic-di srm-modules-4.19.0-1-alpha-generic-di 
linux-image-4.19.0-1-alpha-generic linux-headers-4.19.0-1-alpha-generic 
linux-image-4.19.0-1-alpha-generic-dbg linux-image-4.19.0-1-alpha-smp 
linux-headers-4.19.0-1-alpha-smp linux-image-4.19.0-1-alpha-smp-dbg 
linux-headers-4.19.0-1-all-amd64 kernel-image-4.19.0-1-amd64-di 
nic-modules-4.19.0-1-amd64-di 

Bug#911360: marked as done (FTBFS every time default PHP version is changed)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 15:00:19 +
with message-id 
and subject line Bug#911360: fixed in kopanocore 8.6.90-1
has caused the Debian Bug report #911360,
regarding FTBFS every time default PHP version is changed
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.)


-- 
911360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kopanocore
Version: 8.6.5-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

your package contains code that requires specifying PHP version
in debian/rules.  This is not necessary and in fact it's harmful
because kopanocore FTBFS every time default PHP version is changed.

This prevents binNMUs on your package and currently kopanocore
cannot be built without changing the source.  The patch is very
simple and attached.

I would also suggest to use dh-exec instead of hand crafted d/rules
macro to replace DEB_HOST_MULTIARCH, but that's of course ultimately
your decision.

Cheers,
Ondrej

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8), LANGUAGE=en_DK.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAlvJcn1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcIRMw/9HiSQOmd/ey0ALmXdTr5nqw2Gzw7s5P/m5ECiN9gixw6snICTupf/d7K8
upe155sLk8iAoZxZ1y9uNDAbae0xH4lT9a85wyspwsOQTm0siDG7VLBqLWCZ3ZCy
0Cp9AGwlHYyi4+GVca/vDypegy9A2mIOwC762u66Lcwdz12WHNahxSo/RnO/1h0J
3Wr9oXmJ2iI5ZDQeJAX7tm/Z+iVKcvcInF+46C3zjlg3Y800Re8LkRaXzBJo7ip0
4wnLOlQQqAxnQvwz+89IrflpdMmvGLesvGPFkL9qjK5IqoSs9fdqkOS+lxNnfZgH
mlN0NRIF+B6kzBQe8alovDD7ZHcFkj7hC7GzYuAzeV5y/nKoBIpJecwrHxCFNJK2
9HPO7ITI0vdkxQKiu+UiSaPCNdDZ2mzd0iqnUyZKX5oTv1AqEi6Mu/BGdyUonu4u
qdXse2aZ2yHYlODwK4q+o5zpPXl/iqXzdcnpNKD09pDIUQkT8cf9FD9JIOndOkqL
WlS0X6LYubvEkHy0RBHlXaBtWD3SQ79/AbpYHAs6UtMeYuUFqHusoEaWtbqiUPk1
jQeeKoMfseEsJEnBJXKV9v+7DRsLFOXwfT8d8B7RSjY5pSmZKGk/xFj5AFBpATSS
HvvSGbyMwuKJmYPipvm8n0PMxee+1jMdEXjy4fLsTaJGlvQhICw=
=wwqz
-END PGP SIGNATURE-
>From c959c5017d7751471d88d9217cac641c4fd8c447 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ond=C5=99ej=20Sur=C3=BD?= 
Date: Fri, 19 Oct 2018 05:39:21 +
Subject: [PATCH 1/2] Use default Debian PHP version instead of manually
 specifying a version

---
 debian/rules | 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/debian/rules b/debian/rules
index f88a846..7899b90 100755
--- a/debian/rules
+++ b/debian/rules
@@ -15,8 +15,7 @@ include /usr/share/dpkg/pkg-info.mk
 DEB_BUILD_DIR=debian/build
 
 INSTDIR=$(CURDIR)/debian/tmp
-PHP_VERSION=7.2
-PHP_API_DATE=$(shell php-config$(PHPVERSION) --phpapi)
+PHP_API_DATE=$(shell php-config --phpapi)
 PREPROCESS_FILES := $(wildcard debian/*.in)
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
@@ -33,7 +32,7 @@ DEB_CONFIGURE_EXTRA_ARGS :=  \
 --sysconfdir=/etc \
 --mandir=\$${prefix}/share/man \
 --infodir=\$${prefix}/share/info \
---with-php-config=/usr/bin/php-config$(PHPVERSION) \
+--with-php-config=/usr/bin/php-config \
 --with-quotatemplate-prefix=/etc/kopano/quotamail \
 --with-userscript-prefix=/etc/kopano/userscripts \
 --disable-static \
@@ -46,7 +45,6 @@ DEB_CONFIGURE_EXTRA_ARGS :=  \
 
 $(PREPROCESS_FILES:.in=): %: %.in
sed -e 's,/@DEB_HOST_MULTIARCH@,$(DEB_HOST_MULTIARCH:%=/%),g' \
-   -e 's,/@PHP_VERSION@,$(PHP_VERSION:%=/%),g' \
-e 's,/@PHP_API_DATE@,$(PHP_API_DATE:%=/%),g' $< > $@
 
 %:
-- 
2.19.1

>From 6f6401bf8a25123a2808a81ca36c21eba4bb4742 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ond=C5=99ej=20Sur=C3=BD?= 
Date: Fri, 19 Oct 2018 05:52:10 +
Subject: [PATCH 2/2] Just use wildcard to remove the need to modify
 php-mapi.php

---
 debian/php-mapi.php| 3 +++
 debian/php-mapi.php.in | 3 ---
 debian/rules   | 3 +--
 3 files changed, 4 insertions(+), 5 deletions(-)
 create mode 100644 debian/php-mapi.php
 delete mode 100644 debian/php-mapi.php.in

diff --git a/debian/php-mapi.php b/debian/php-mapi.php
new file mode 100644
index 000..4f441d6
--- /dev/null
+++ b/debian/php-mapi.php
@@ -0,0 

Bug#913512: marked as done (ucto FTBFS with ICU 63.1)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 15:00:30 +
with message-id 
and subject line Bug#913512: fixed in ucto 0.14-1
has caused the Debian Bug report #913512,
regarding ucto FTBFS with ICU 63.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.)


-- 
913512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ucto
Source-Version: 0.9.6-1
Severity: important
Tags: patch
Usertags: icu63

Dear Maintainer,

ICU 63.1 recently released, packaged and uploaded to experimental.
Its transition is going to start soon. However your package fails to
build with this version. I attach a patch which fixes the problem.
Please check if it works with the version in Sid and upload the
package when it's feasible for you.

Thanks,
Laszlo/GCS
Description: fix FTBFS with ICU 63.1
 Add icu namespace.
Author: Laszlo Boszormenyi (GCS) 
Last-Update: 2018-11-09

---

--- ucto-0.9.6.orig/include/ucto/setting.h
+++ ucto-0.9.6/include/ucto/setting.h
@@ -38,15 +38,15 @@ namespace Tokenizer {
   public:
   Rule(): regexp(0){
 };
-Rule( const UnicodeString& id, const UnicodeString& pattern);
+Rule( const icu::UnicodeString& id, const icu::UnicodeString& pattern);
 ~Rule();
-UnicodeString id;
-UnicodeString pattern;
+icu::UnicodeString id;
+icu::UnicodeString pattern;
 UnicodeRegexMatcher *regexp;
-bool matchAll( const UnicodeString&,
-		   UnicodeString&,
-		   UnicodeString&,
-		   std::vector& );
+bool matchAll( const icu::UnicodeString&,
+		   icu::UnicodeString&,
+		   icu::UnicodeString&,
+		   std::vector& );
   private:
 Rule( const Rule& ); // inhibit copies
 Rule& operator=( const Rule& ); // inhibit copies
@@ -56,17 +56,17 @@ namespace Tokenizer {
   class Quoting {
 friend std::ostream& operator<<( std::ostream&, const Quoting& );
 struct QuotePair {
-  UnicodeString openQuote;
-  UnicodeString closeQuote;
+  icu::UnicodeString openQuote;
+  icu::UnicodeString closeQuote;
 };
   public:
-void add( const UnicodeString&, const UnicodeString& );
-UnicodeString lookupOpen( const UnicodeString &) const;
-UnicodeString lookupClose( const UnicodeString & ) const;
+void add( const icu::UnicodeString&, const icu::UnicodeString& );
+icu::UnicodeString lookupOpen( const icu::UnicodeString &) const;
+icu::UnicodeString lookupClose( const icu::UnicodeString & ) const;
 bool empty() const { return _quotes.empty(); };
 bool emptyStack() const { return quotestack.empty(); };
 void clearStack() { quoteindexstack.clear(); quotestack.clear(); };
-int lookup( const UnicodeString&, int& );
+int lookup( const icu::UnicodeString&, int& );
 void eraseAtPos( int pos ) {
   quotestack.erase( quotestack.begin()+pos );
   quoteindexstack.erase( quoteindexstack.begin()+pos );
@@ -90,14 +90,14 @@ namespace Tokenizer {
 bool readfilters( const std::string& );
 bool readquotes( const std::string& );
 bool readeosmarkers( const std::string& );
-bool readabbreviations( const std::string&,  UnicodeString& );
-void add_rule( const UnicodeString&, const std::vector& );
-void sortRules( std::map&,
-		const std::vector& );
-UnicodeString eosmarkers;
+bool readabbreviations( const std::string&,  icu::UnicodeString& );
+void add_rule( const icu::UnicodeString&, const std::vector& );
+void sortRules( std::map&,
+		const std::vector& );
+icu::UnicodeString eosmarkers;
 std::vector rules;
-std::map rulesmap;
-std::map rules_index;
+std::map rulesmap;
+std::map rules_index;
 Quoting quotes;
 UnicodeFilter filter;
 std::string set_file; // the name of the settingsfile
--- ucto-0.9.6.orig/include/ucto/tokenize.h
+++ ucto-0.9.6/include/ucto/tokenize.h
@@ -78,11 +78,11 @@ namespace Tokenizer {
   class Token {
 friend std::ostream& operator<< (std::ostream&, const Token& );
   public:
-UnicodeString type;
-UnicodeString us;
+icu::UnicodeString type;
+icu::UnicodeString us;
 TokenRole role;
-Token( const UnicodeString&,
-	   const UnicodeString&,
+Token( const icu::UnicodeString&,
+	   const icu::UnicodeString&,
 	   TokenRole role = NOROLE,
 	   const std::string& = "" );
 std::string lc;// ISO 639-3 language code
@@ -130,12 +130,12 @@ namespace Tokenizer {
 
 // Tokenize a line (a line is NOT a sentence, but an arbitrary string
 //  of characters, inclusive EOS markers, Newlines etc.)
-int tokenizeLine( const 

Bug#913514: marked as done (libfolia FTBFS with ICU 63.1)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 15:00:21 +
with message-id 
and subject line Bug#913514: fixed in libfolia 1.15-1
has caused the Debian Bug report #913514,
regarding libfolia FTBFS with ICU 63.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.)


-- 
913514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfolia
Source-Version: 1.6-2
Severity: important
Tags: patch
Usertags: icu63

Dear Maintainer,

ICU 63.1 recently released, packaged and uploaded to experimental.
Its transition is going to start soon. However your package fails to
build with this version. I attach a patch which fixes the problem.
Please check if it works with the version in Sid and upload the
package when it's feasible for you.

Thanks,
Laszlo/GCS
Description: fix FTBFS with ICU 63.1
 Add icu namespace.
Author: Laszlo Boszormenyi (GCS) 
Last-Update: 2018-11-07

---

--- libfolia-1.6.orig/include/libfolia/folia_document.h
+++ libfolia-1.6/include/libfolia/folia_document.h
@@ -56,7 +56,7 @@ namespace folia {
 Pattern( const std::vector&,  const std::string& );
 
 ~Pattern();
-bool match( const UnicodeString& , size_t&, int&, bool&, bool& ) const;
+bool match( const icu::UnicodeString& , size_t&, int&, bool&, bool& ) const;
 size_t size() const { return sequence.size(); };
 void unsetwild();
 bool variablesize() const;
@@ -66,8 +66,8 @@ namespace folia {
   private:
 bool case_sensitive;
 int maxgapsize;
-std::vector sequence;
-std::vector matchers;
+std::vector sequence;
+std::vector matchers;
 std::string matchannotationset;
   };
 
@@ -105,7 +105,7 @@ namespace folia {
 void set_foreign_metadata( xmlNode * );
 void addStyle( const std::string&, const std::string& );
 void replaceStyle( const std::string&, const std::string& );
-UnicodeString text( const std::string& = "current",
+icu::UnicodeString text( const std::string& = "current",
 			bool = false,
 			bool = false ) const;
 std::vector paragraphs() const;
--- libfolia-1.6.orig/include/libfolia/folia_impl.h
+++ libfolia-1.6/include/libfolia/folia_impl.h
@@ -272,12 +272,12 @@ namespace folia {
 bool hastext( const std::string& = "current" ) const;
 
 virtual const std::string str( const std::string& = "current" ) const = 0;
-const UnicodeString unicode( const std::string& cls = "current" ) const { return text( cls ); };
-virtual const UnicodeString text( const std::string& = "current",
+const icu::UnicodeString unicode( const std::string& cls = "current" ) const { return text( cls ); };
+virtual const icu::UnicodeString text( const std::string& = "current",
 bool = false, bool = false ) const = 0;
-const UnicodeString stricttext( const std::string& = "current" ) const;
-const UnicodeString toktext( const std::string& = "current" ) const;
-virtual const UnicodeString phon( const std::string& = "current",
+const icu::UnicodeString stricttext( const std::string& = "current" ) const;
+const icu::UnicodeString toktext( const std::string& = "current" ) const;
+virtual const icu::UnicodeString phon( const std::string& = "current",
 bool = false ) const = 0;
 virtual bool printable() const = 0;
 virtual bool speakable() const = 0;
@@ -337,8 +337,8 @@ namespace folia {
 virtual TextContent *textcontent( const std::string& = "current" ) const = 0;
 TextContent *settext( const std::string&, const std::string& = "current" );
 TextContent *settext( const std::string&, int , const std::string& = "current" );
-TextContent *setutext( const UnicodeString&, const std::string& = "current" );
-TextContent *setutext( const UnicodeString&, int , const std::string& = "current" );
+TextContent *setutext( const icu::UnicodeString&, const std::string& = "current" );
+TextContent *setutext( const icu::UnicodeString&, int , const std::string& = "current" );
 virtual int offset() const NOT_IMPLEMENTED;
 
 // PhonContent
@@ -410,7 +410,7 @@ namespace folia {
 
 virtual const std::string content() const NOT_IMPLEMENTED;
 virtual const std::string src() const NOT_IMPLEMENTED;
-virtual const UnicodeString caption() const NOT_IMPLEMENTED;
+virtual const icu::UnicodeString caption() const NOT_IMPLEMENTED;
 virtual std::vector resolve() const NOT_IMPLEMENTED;
 virtual const FoliaElement* resolveid() const NOT_IMPLEMENTED;
 virtual bool checkAtts() = 0;
@@ -563,14 +563,14 @@ namespace folia {
 // text/string content
 
 

Bug#911361: marked as done (FTBFS in Debian unstable)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 15:00:19 +
with message-id 
and subject line Bug#911360: fixed in kopanocore 8.6.90-1
has caused the Debian Bug report #911360,
regarding FTBFS in Debian unstable
to be marked as done.

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

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


-- 
911360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kopanocore
Version: 8.6.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

the gcc transition made the package FTBFS again due changed symbols:

dpkg-gensymbols: warning: the generated symbols file is empty
- --- debian/kopano-libs.symbols (kopano-libs_8.6.5-1_amd64)
+++ dpkg-gensymbols1FluVO2018-10-19 07:57:28.597928430 +0200
@@ -1,139 +0,0 @@
- -libkcarchiver.so.0 kopano-libs #MINVER#
- -#MISSING: 8.6.5-1# (symver|optional)EC_8.1.0 8.0.1
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.3 8.3.2
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.4.90 8.5.0~8.4.99
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.5 8.5.0
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.6 8.6.0
- - (symver|optional)KC_8.6.1 8.6.1
- -libkcarchivercore.so.0 kopano-libs #MINVER#
- -#MISSING: 8.6.5-1# (symver|optional)EC_8.1.0 8.0.1
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.3 8.3.2
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.4.90 8.5.0~8.4.99
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.5 8.5.0
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.6 8.6.0
- - (symver|optional)KC_8.6.1 8.6.1
- -libkcfreebusy.so.0 kopano-libs #MINVER#
- -#MISSING: 8.6.5-1# (symver|optional)EC_8.1.0 8.0.1
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.3 8.3.2
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.4.90 8.5.0~8.4.99
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.5 8.5.0
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.6 8.6.0
- - (symver|optional)KC_8.6.1 8.6.1
- -libkcicalmapi.so.0 kopano-libs #MINVER#
- -#MISSING: 8.6.5-1# (symver|optional)EC_8.1.0 8.0.1
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.3 8.3.2
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.4.90 8.5.0~8.4.99
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.5 8.5.0
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.6 8.6.0
- - (symver|optional)KC_8.6.1 8.6.1
- -libkcinetmapi.so.0 kopano-libs #MINVER#
- -#MISSING: 8.6.5-1# (symver|optional)EC_8.1.0 8.0.1
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.3 8.3.2
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.4.90 8.5.0~8.4.99
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.5 8.5.0
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.6 8.6.0
- - (symver|optional)KC_8.6.1 8.6.1
- -libkcmapi.so.0 kopano-libs #MINVER#
- -#MISSING: 8.6.5-1# (symver|optional)EC_8.1.0 8.0.1
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.3 8.3.2
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.4.90 8.5.0~8.4.99
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.5 8.5.0
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.6 8.6.0
- - (symver|optional)KC_8.6.1 8.6.1
- -libkcpyconv-2.7.so kopano-libs #MINVER#
- -#MISSING: 8.6.5-1# (symver|optional)EC_8.1.0 8.0.1
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.5 8.5.0
- -#MISSING: 8.6.5-1# (symver|optional)KC_8.6 8.6.0
- - (symver|optional)KC_8.6.1 8.6.1
- - _Z11DoExceptioni@Base 8.5.0~8.4.99
- - _Z13CopyPyUnicodePPwP7_objectPv@Base 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC6ECUSERENS0_13objectclass_tEXadL_ZNS1_10ulObjClassvPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC6ECUSERENS0_9ECENTRYIDEXadL_ZNS1_7sUserIdvPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC6ECUSEREPwXadL_ZNS1_12lpszFullNamevPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC6ECUSEREPwXadL_ZNS1_12lpszPasswordvPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC6ECUSEREPwXadL_ZNS1_12lpszUsernamevPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC6ECUSEREPwXadL_ZNS1_14lpszServernamevPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC6ECUSEREPwXadL_ZNS1_15lpszMailAddressvPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC6ECUSEREjXadL_ZNS1_10ulCapacityvPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC6ECUSEREjXadL_ZNS1_12ulIsABHiddenvPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC6ECUSEREjXadL_ZNS1_9ulIsAdminvPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC7ECGROUPENS0_9ECENTRYIDEXadL_ZNS1_8sGroupIdvPT_P7_objectPKcPvj@Base
 8.5.0~8.4.99
- - 
_Z16conv_out_defaultIN2KC7ECGROUPEPwXadL_ZNS1_12lpszFullnamevPT_P7_objectPKcPvj@Base
 

Bug#906371: [Debian-med-packaging] Bug#906371: Changes in alter-sequence-alignment break build of jmodeltest (Was: Bug#906371: jmodeltest: FTBFS in buster/sid)

[Olivier Sallou]

On 12/17/18 11:07 AM, Andreas Tille wrote:
> Hi,
>
> after I tried to follow the initial hint of Emmanuel I admit I was not
> successful to finally build the package:
>
> On Wed, Oct 17, 2018 at 10:32:58AM +0200, Andreas Tille wrote:
>>> Good catch.  The latest upstream version of alter-sequence-alignment has
>>> split these to an additional alter-lib.jar and the time of the build
>>> failure of jmodeltest correlates with the upload of
>>> alter-sequence-alignment 1.3.4-1.  But now the question is:  How to
>>> teach the jmodeltest build system to use alter-lib.jar.  I think adding
>>> it to debian/manifest[1] is needed to *run* jmodeltest but it surely
>>> does not help at build time.  I have not found any place where the
>>> build system specifies the needed jars. :-(
>> I tried to add alter-lib.jar to build.xml[1].  Unfortunately this does
>> not help to fix the issue
>>
>> [javac] 
>> /build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:28:
>>  error: package parser does not exist
>> [javac] import parser.ParseException;
>> [javac]  ^
>> [javac] 
>> /build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:29:
>>  error: package converter does not exist
>> [javac] import converter.Converter;
>> [javac] ^
>> [javac] 
>> /build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:30:
>>  error: package converter does not exist
>> [javac] import converter.DefaultFactory;
>> [javac] ^
>> [javac] 
>> /build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:31:
>>  error: package converter does not exist
>> [javac] import converter.Factory;
>>
>> Any hint how to get the classes in alter-lib.jar found?

I fixed the issue and pushed to git my patch d/patches/fix_alter-lib.patch

The lib was used but the package name in alter-lib.jar is different.
ModelTestService is patched to use correct package name

>> Moreover I get lots of
>>
>> [javac] 
>> /build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/exe/Distributor.java:23:
>>  warning: [deprecation] Observable in java.util has been deprecated
>> [javac] import java.util.Observable;
>> [javac] ^
> Any more hints?
>
> Kind regards
>
>Andreas. 
>
-- 
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#911953: marked as done (librabbitmq-dev missing Depends: libssl-dev)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 14:43:48 +
with message-id 
and subject line Bug#911953: fixed in librabbitmq 0.9.0-0.2
has caused the Debian Bug report #911953,
regarding librabbitmq-dev missing Depends: libssl-dev
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.)


-- 
911953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librabbitmq-dev
Version: 0.9.0-0.1
Severity: serious
Tags: ftbfs
Control: affects -1 + src:pmacct

pmacct fails to build from source. This is caused by a bug in
librabbitmq-dev. After installing librabbitmq-dev, the .pc file is
dysfunctional:

$ pkg-config librabbitmq --cflags
Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
Package 'openssl', required by 'librabbitmq', not found
$

The .pc file has

| Requires.private: openssl

but the package misses a dependency on libssl-dev. Either remove openssl
from requires or add libssl-dev to Depends.

Helmut
--- End Message ---
--- Begin Message ---
Source: librabbitmq
Source-Version: 0.9.0-0.2

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
librabbitmq 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: Mon, 17 Dec 2018 14:59:40 +0100
Source: librabbitmq
Binary: librabbitmq-dev librabbitmq4 amqp-tools
Architecture: source
Version: 0.9.0-0.2
Distribution: unstable
Urgency: medium
Maintainer: Michael Fladischer 
Changed-By: Gianfranco Costamagna 
Description:
 amqp-tools - Command-line utilities for interacting with AMQP servers
 librabbitmq-dev - AMQP client library written in C - Dev Files
 librabbitmq4 - AMQP client library written in C
Closes: 911693 911953
Changes:
 librabbitmq (0.9.0-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Runtime-depend on libssl-dev (Closes: #911953)
   * Disable new test_basic file, requires an active AMQP instance during
 build. (Closes: #911693)
Checksums-Sha1:
 a93094c2938504eff2636ce36286b3ff9be12a9e 2073 librabbitmq_0.9.0-0.2.dsc
 6d3f93c70a4952bd7e3c876b9f8e9187e1cbaa26 9412 
librabbitmq_0.9.0-0.2.debian.tar.xz
 837eaa3c5a1f442aea08de9e3743b0fe51722e00 8407 
librabbitmq_0.9.0-0.2_source.buildinfo
Checksums-Sha256:
 cfe40963712c02e918eb7b028ca78e3ca38e6c612018d6fa1ac48ad5c67e1857 2073 
librabbitmq_0.9.0-0.2.dsc
 1bec8804fbdf30d21a8605a07da8e4db89fbf4afd16dc2cc7a7e4d4a5dfc6c15 9412 
librabbitmq_0.9.0-0.2.debian.tar.xz
 11841d121ad92715327ecb3e0750c913f9a32fc432f288b20d071b91c13df367 8407 
librabbitmq_0.9.0-0.2_source.buildinfo
Files:
 91dfd67b08124ecc8e51d7625d563dae 2073 libs optional librabbitmq_0.9.0-0.2.dsc
 94ba6106292ed1597f5c193b8eb3bb4f 9412 libs optional 
librabbitmq_0.9.0-0.2.debian.tar.xz
 3b1e75e4d85338e7ebf171fa7fb28e4f 8407 libs optional 
librabbitmq_0.9.0-0.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAlwXrKMACgkQ808JdE6f
Xdndsw//WSEqsIq7AXeAm4UnsWTQKPk4/5IA+qBikmkFmDx+mZ+5YCo4HBNJDQFQ
QeFojXJ/kJHU0y1PJI8c9l9Rr1eFOYsRtHMH+sEjkDeoexJCBmBepO54GWvKwvqB
Ys329IXIHl54SWYR7WdRyXbIMmtolifHdh5xuzqlnztNQ/0fm9zeNyCpQn3i5SW+
4p9vz7at4FA5IB7OMRUnBbWdKyGBm4Fleep9pT0Tj6i4K6gYZAtBBxmnjUqpQlbA
jwnF68POWCxUkmdHEcNUVBeG74BsLSVU9BOXJHZCW7Sw8dRFd+UImFyjLrAGZ61K
nACan7GQ5FyYz2NwyN4h61WpffjiJVusEAd6jUs5rsDl0WflWHJ+DIAb2cUGsrA4
OPBNW4UIMJ7W6/XbK1ArVu8+KewhOLG5JfTffUwd4TdWpZYOXbg+rrrhcTeYkMaa
o/3R39gdYtXOwDXgcHHERzYwjoyDlqr2sBezPo1Hnm3TMcUB6MhGOxLKNubFk18n
k+ck8nTrHTUrDlRORQrBn7dfOiKxeq0eklt4APD73GRxkOyZ7tM3R6xV6FXnq7JV
17Gro0CfxKqPCEupHUOyEecPD6DPADbfhb61gIglY5czZO5FMpIm5hTNMkPDz7lF
rmE/mNK3M7HeMV3Sj3R0xspmUyOM/doQ/xSsJAyDl1bNWMLhFeA=
=/xGn
-END PGP SIGNATURE End Message ---

Bug#911693: marked as done (librabbitmq FTBFS: setup_connection_and_channel: Assertion `rc == AMQP_STATUS_OK' failed.)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 14:43:48 +
with message-id 
and subject line Bug#911693: fixed in librabbitmq 0.9.0-0.2
has caused the Debian Bug report #911693,
regarding librabbitmq FTBFS: setup_connection_and_channel: Assertion `rc == 
AMQP_STATUS_OK' failed.
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.)


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

librabbitmq fails to build from source in unstable on the official
buildds:

https://buildd.debian.org/status/fetch.php?pkg=librabbitmq=arm64=0.9.0-0.1=1538400732=0

| Running tests...
| /usr/bin/ctest --force-new-ctest-process -j1
| Test project /<>/obj-aarch64-linux-gnu
| Start 1: parse_url
| 1/7 Test #1: parse_url    Passed0.00 sec
| Start 2: tables
| 2/7 Test #2: tables ...   Passed0.00 sec
| Start 3: hostcheck
| 3/7 Test #3: hostcheck    Passed0.00 sec
| Start 4: status_enum
| 4/7 Test #4: status_enum ..   Passed0.00 sec
| Start 5: basic
| 5/7 Test #5: basic ***Exception: Child aborted  
0.01 sec
| test_basic: /<>/tests/test_basic.c:54: 
setup_connection_and_channel: Assertion `rc == AMQP_STATUS_OK' failed.
| 
| Start 6: sasl_mechanism
| 6/7 Test #6: sasl_mechanism ...   Passed0.00 sec
| Start 7: merge_capabilities
| 7/7 Test #7: merge_capabilities ...   Passed0.00 sec
| 
| 86% tests passed, 1 tests failed out of 7
| 
| Total Test time (real) =   0.03 sec
| 
| The following tests FAILED:
|5 - basic (Child aborted)
| Errors while running CTest
| make[1]: *** [Makefile:98: test] Error 8
| make[1]: Leaving directory '/<>/obj-aarch64-linux-gnu'
| dh_auto_test: cd obj-aarch64-linux-gnu && make -j1 test ARGS\+=-j1 returned 
exit code 2
| make: *** [debian/rules:4: build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: librabbitmq
Source-Version: 0.9.0-0.2

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
librabbitmq 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: Mon, 17 Dec 2018 14:59:40 +0100
Source: librabbitmq
Binary: librabbitmq-dev librabbitmq4 amqp-tools
Architecture: source
Version: 0.9.0-0.2
Distribution: unstable
Urgency: medium
Maintainer: Michael Fladischer 
Changed-By: Gianfranco Costamagna 
Description:
 amqp-tools - Command-line utilities for interacting with AMQP servers
 librabbitmq-dev - AMQP client library written in C - Dev Files
 librabbitmq4 - AMQP client library written in C
Closes: 911693 911953
Changes:
 librabbitmq (0.9.0-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Runtime-depend on libssl-dev (Closes: #911953)
   * Disable new test_basic file, requires an active AMQP instance during
 build. (Closes: #911693)
Checksums-Sha1:
 a93094c2938504eff2636ce36286b3ff9be12a9e 2073 librabbitmq_0.9.0-0.2.dsc
 6d3f93c70a4952bd7e3c876b9f8e9187e1cbaa26 9412 
librabbitmq_0.9.0-0.2.debian.tar.xz
 837eaa3c5a1f442aea08de9e3743b0fe51722e00 8407 
librabbitmq_0.9.0-0.2_source.buildinfo
Checksums-Sha256:
 cfe40963712c02e918eb7b028ca78e3ca38e6c612018d6fa1ac48ad5c67e1857 2073 
librabbitmq_0.9.0-0.2.dsc
 1bec8804fbdf30d21a8605a07da8e4db89fbf4afd16dc2cc7a7e4d4a5dfc6c15 9412 
librabbitmq_0.9.0-0.2.debian.tar.xz
 11841d121ad92715327ecb3e0750c913f9a32fc432f288b20d071b91c13df367 8407 
librabbitmq_0.9.0-0.2_source.buildinfo
Files:
 91dfd67b08124ecc8e51d7625d563dae 2073 libs optional librabbitmq_0.9.0-0.2.dsc
 94ba6106292ed1597f5c193b8eb3bb4f 9412 libs optional 
librabbitmq_0.9.0-0.2.debian.tar.xz
 3b1e75e4d85338e7ebf171fa7fb28e4f 8407 libs optional 
librabbitmq_0.9.0-0.2_source.buildinfo

Processed:

[Debian Bug Tracking System]

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

> Severity 852199 serious
Bug #852199 [snapd] /snap is a FHS violation
Severity set to 'serious' from 'normal'
> Severity 862199 normal
Bug #862199 [thunderbird] thunderbird: Thunderbird crashes when removing 
massively mails
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Processed: librabbitmq: NMU ongoing

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #911953 [librabbitmq-dev] librabbitmq-dev missing Depends: libssl-dev
Added tag(s) pending and patch.

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

Bug#911693: librabbitmq: NMU ongoing

[Gianfranco Costamagna]

control: tags -1 patch pending

Dear maintainer,

I've prepared an NMU for librabbitmq (versioned as 0.9.0-0.2) and
uploaded it to unstable. Please feel free to tell me if I
should delay it longer.

Regards.

G.
diff -Nru librabbitmq-0.9.0/debian/changelog librabbitmq-0.9.0/debian/changelog
--- librabbitmq-0.9.0/debian/changelog  2018-10-01 14:54:12.0 +0200
+++ librabbitmq-0.9.0/debian/changelog  2018-12-17 14:59:40.0 +0100
@@ -1,3 +1,12 @@
+librabbitmq (0.9.0-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Runtime-depend on libssl-dev (Closes: #911953)
+  * Disable new test_basic file, requires an active AMQP instance during
+build. (Closes: #911693)
+
+ -- Gianfranco Costamagna   Mon, 17 Dec 2018 
14:59:40 +0100
+
 librabbitmq (0.9.0-0.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru librabbitmq-0.9.0/debian/control librabbitmq-0.9.0/debian/control
--- librabbitmq-0.9.0/debian/control2018-10-01 14:54:12.0 +0200
+++ librabbitmq-0.9.0/debian/control2018-12-17 14:56:04.0 +0100
@@ -19,6 +19,7 @@
 Architecture: any
 Multi-Arch: same
 Depends: librabbitmq4 (= ${binary:Version}),
+ libssl-dev,
  ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
 Description: AMQP client library written in C - Dev Files
diff -Nru librabbitmq-0.9.0/debian/patches/disable-test-basic.patch 
librabbitmq-0.9.0/debian/patches/disable-test-basic.patch
--- librabbitmq-0.9.0/debian/patches/disable-test-basic.patch   1970-01-01 
01:00:00.0 +0100
+++ librabbitmq-0.9.0/debian/patches/disable-test-basic.patch   2018-12-17 
14:59:40.0 +0100
@@ -0,0 +1,17 @@
+Description: This test seems to require an active AMQP instance,
+ something not possible during build process. Disable it for now.
+Author: Gianfranco Costamagna 
+Bug-Debian: https://bugs.debian.org/911693
+Last-Update: 2018-12-17
+
+--- librabbitmq-0.9.0.orig/tests/CMakeLists.txt
 librabbitmq-0.9.0/tests/CMakeLists.txt
+@@ -34,7 +34,7 @@ add_executable(test_basic
+ target_link_libraries(test_basic rabbitmq-static)
+ 
+ if (NOT APPLE)
+-  add_test(basic test_basic)
++  #add_test(basic test_basic)
+ endif()
+ 
+ add_executable(test_sasl_mechanism test_sasl_mechanism.c)
diff -Nru librabbitmq-0.9.0/debian/patches/series 
librabbitmq-0.9.0/debian/patches/series
--- librabbitmq-0.9.0/debian/patches/series 2018-10-01 14:54:12.0 
+0200
+++ librabbitmq-0.9.0/debian/patches/series 2018-12-17 14:59:40.0 
+0100
@@ -1,2 +1,3 @@
 cmake_with_ssl.patch
 use_cmake_package.patch
+disable-test-basic.patch

Processed: librabbitmq: NMU ongoing

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #911693 [src:librabbitmq] librabbitmq FTBFS: setup_connection_and_channel: 
Assertion `rc == AMQP_STATUS_OK' failed.
Added tag(s) pending and patch.

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

Bug#862199: changed severity to serious, why?

[Carsten Schoenert]

Hello Stew,

Am 17.12.18 um 15:00 schrieb Debian Bug Tracking System:
> Processing commands for cont...@bugs.debian.org:
> 
>> severity 862199 serious
> Bug #862199 [thunderbird] thunderbird: Thunderbird crashes when removing 
> massively mails
> Severity set to 'serious' from 'normal'

could you please elaborate why you think this issue needs to have a
severity of serious? Also it would be better get in contact with the
package maintainer before doing such things.

The meanings of the severity are explained here:

  https://www.debian.org/Bugs/Developer#severities

I see absolutely no need to adjust the severity as no data loss is
given, no Debian policy is violated nor the is thunderbird doing any
damage on the installed system.

Yes, a crash isn't nice at all, but here on this bug report this isn't
not enough to increase the severity to anything RC.

-- 
Regards
Carsten Schoenert

Processed:

[Debian Bug Tracking System]

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

> severity 862199 serious
Bug #862199 [thunderbird] thunderbird: Thunderbird crashes when removing 
massively mails
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#916236: marked as done (golang-golang-x-net-dev: FTBFS on s390x - rawconn.go undefined: getsockopt)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 13:49:17 +
with message-id 
and subject line Bug#916236: fixed in golang-golang-x-net-dev 
1:0.0+git20181201.351d144+dfsg-2
has caused the Debian Bug report #916236,
regarding golang-golang-x-net-dev: FTBFS on s390x - rawconn.go undefined: 
getsockopt
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.)


-- 
916236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-golang-x-net-dev
Version: 1:0.0+git20181201.351d144+dfsg-1

It looks like the golang-golang-x-net-dev build is broken on s390x.

Syncthing gets the following error during build:

```
src/golang.org/x/net/internal/socket/rawconn.go:49:14: undefined: getsockopt
src/golang.org/x/net/internal/socket/rawconn.go:60:11: undefined: setsockopt
src/golang.org/x/net/internal/socket/rawconn_msg.go:26:14: undefined:
recvmsg
src/golang.org/x/net/internal/socket/rawconn_msg.go:62:14: undefined:
sendmsg
```

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-golang-x-net-dev
Source-Version: 1:0.0+git20181201.351d144+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated golang-golang-x-net-dev 
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: Fri, 14 Dec 2018 13:56:28 +
Source: golang-golang-x-net-dev
Binary: golang-golang-x-net-dev golang-go.net-dev
Architecture: source
Version: 1:0.0+git20181201.351d144+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Martín Ferrari 
Description:
 golang-go.net-dev - Transitional package for golang-golang-x-net-dev
 golang-golang-x-net-dev - Supplementary Go networking libraries
Closes: 916236
Changes:
 golang-golang-x-net-dev (1:0.0+git20181201.351d144+dfsg-2) unstable; 
urgency=medium
 .
   * Remove obsolete patch for s390. Closes: #916236.
Checksums-Sha1:
 c3a4fabaf3dd47c0a795eead44afc4585e9a4252 2505 
golang-golang-x-net-dev_0.0+git20181201.351d144+dfsg-2.dsc
 a8ab880d14789d57c596fbf1b2f1424bc8805b71 12868 
golang-golang-x-net-dev_0.0+git20181201.351d144+dfsg-2.debian.tar.xz
 0991fc7803c1218469397d3fb0c48f81ebd99704 6203 
golang-golang-x-net-dev_0.0+git20181201.351d144+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 e3d53b8e23669d4522e5ff72a4caf72044e6c5117fbe6f32dd2502426951bc37 2505 
golang-golang-x-net-dev_0.0+git20181201.351d144+dfsg-2.dsc
 f98b34506c24e6b684a302f5415fd2b93c1e291dbf3fb2c3932f6f11cd04587a 12868 
golang-golang-x-net-dev_0.0+git20181201.351d144+dfsg-2.debian.tar.xz
 f8a4409ec86241d9f3ddd222a88e8a53d53e7c82bfe72b3ffd3841be7f89dbed 6203 
golang-golang-x-net-dev_0.0+git20181201.351d144+dfsg-2_amd64.buildinfo
Files:
 61a7fd29197e6459f728f5ec7a902c5f 2505 devel optional 
golang-golang-x-net-dev_0.0+git20181201.351d144+dfsg-2.dsc
 a153db2068d4bac3d6b6f35e8a9683a4 12868 devel optional 
golang-golang-x-net-dev_0.0+git20181201.351d144+dfsg-2.debian.tar.xz
 e015ad3df303e154a91c4544587a0ed3 6203 devel optional 
golang-golang-x-net-dev_0.0+git20181201.351d144+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlwXo9oACgkQXdjgv5Gj
09oCSg//XaMJ6Q0C5f+ANThW+dMKJCmQ0RPa/CJojBM/ZOF8Pk8wpcEAW1WRFcwI
DLpF2+646YvNN09CdsmxDvRQzIvLPfYxxRcrkxVw4FegikIE02fhjtq+d4j9rGiO
Eop0MIElfSuBpWP8vOylNizjdtXGJEU76zs7ErOrm6BmU7wAH1YMqHewHOOttB65
KhugjIwt+b4jqx4UOC3VWNW2N1mckKfTSetU3KlcUtlGiWh3s00XQD2/4YVCRmR5
2ZV98D5vwVeLLH5oOLR1JGTRUgB778sW63XhphodTZmr52B5APwMRRJZsAVybhI4
lGnUGr8VlRhcFGBRwNA8z1gxVAw/vI2IDWzgmL2VpVcGkjDHK/UyHHxz86M3EHl5
DNaBmSII1Rs57dPkmnsI8MsBAXHNvVy/RGzaJvN5PjDLRcPsu+C7AiLkgzdAaYk5
41utDbhmZAy0dkLcW5gR9kYbHSrsXWJZyFKA6i16OKVFlXlcgyR6Au41G+jmmloh
FQcQ4BRTp0M8xQlneZJetBw3zBCYfo1cDnY4kfchfwa6k62AUjN2Hgmktj95RowM
SrjkuCMGqQEal0xIMZpa+Tg31Yvl4OI//RqVJeGWtT7ZAPEaBihzoyiKytcNHFnE
HbYdmdWvAS2rdhBcHe0/aRLO8JLCOzMNSO5gb47tlFdRd7CMDTs=

Bug#916691: cuyo -- Not fit for next release

[Bernhard R. Link]

Source: cuyo
Severity: critical

Pseudo-Bug to keep cuyo out fo testing so it does not end up in the next 
release.

Bernhard R. Link
-- 
F8AC 04D5 0B9B 064B 3383  C3DA AFFC 96D1 151D FFDC

Bug#909523: Intent to NMU (Re: Bug#909523: Default configuration is incompatible with a non-SELinux active LSM)

[intrigeri]

Hi,

Dmitry Smirnov:
> IMHO something that is so easy to fix hardly qualifies for severity 
> "serious"...

To fix this a user needs to first guess that the problem is related to
AppArmor and then find a workaround (either a way to fully disable
AppArmor, which causes unfortunate regressions elsewhere; or the
better fix I've proposed here, which I found only by reading the
kernel source code). This process does not look easy to me but YMMV
and I won't argue about it endlessly: I can very well live with this
bug severity being downgraded if you prefer :)

>> If one of you feels responsible for maintaining this package but
>> temporarily lacks time, I (or one of the attendees to one of the many
>> upcoming BSPs) will gladly fix this with a NMU.

> Please, please. That would be really nice if you could. Thanks.

OK, will do next time I go through the AppArmor-related bugs, probably
in a few weeks or so.

Cheers,
-- 
intrigeri

Bug#906156: marked as done (python-skbio ftbfs in unstable, and autopkg tests fail (Python 3.7 tests))

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 12:19:55 +
with message-id 
and subject line Bug#906156: fixed in python-skbio 0.5.5-1
has caused the Debian Bug report #906156,
regarding python-skbio ftbfs in unstable, and autopkg tests fail (Python 3.7 
tests)
to be marked as done.

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

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


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

python-skbio ftbfs in unstable (Python 3.7 tests)

https://ci.debian.net/data/packages/unstable/amd64/p/python-skbio/latest-autopkgtest/log.gz


==
ERROR: test_bool_index_both_axes 
(skbio.alignment.tests.test_tabular_msa.TestLoc)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/tests/test_tabular_msa.py",
line 1091, in test_bool_index_both_axes
new = self.get(msa, ([False, True, True], [True, True, False]))
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/tests/test_tabular_msa.py",
line 1271, in get
return obj.loc[indexable]
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 38, in __getitem__
return self._handle_both_axes(*indexable)
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 52, in _handle_both_axes
r = self._slice_on_first_axis(self._obj, seq_index)
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 71, in _slice_on_first_axis
if self.is_scalar(indexable, axis=0):
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 171, in is_scalar
duplicated_key = indexable in index.get_duplicates()
  File "/usr/lib/python3/dist-packages/pandas/core/indexes/base.py", line 2035,
in __contains__
hash(key)
TypeError: unhashable type: 'list'

==
ERROR: test_bool_index_first_axis 
(skbio.alignment.tests.test_tabular_msa.TestLoc)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/tests/test_tabular_msa.py",
line 1062, in test_bool_index_first_axis
new = self.get(msa, [True, True, False])
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/tests/test_tabular_msa.py",
line 1271, in get
return obj.loc[indexable]
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 42, in __getitem__
return self._slice_on_first_axis(self._obj, indexable)
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 71, in _slice_on_first_axis
if self.is_scalar(indexable, axis=0):
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 171, in is_scalar
duplicated_key = indexable in index.get_duplicates()
  File "/usr/lib/python3/dist-packages/pandas/core/indexes/base.py", line 2035,
in __contains__
hash(key)
TypeError: unhashable type: 'list'

==
ERROR: test_bool_index_second_axis 
(skbio.alignment.tests.test_tabular_msa.TestLoc)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/tests/test_tabular_msa.py",
line 1076, in test_bool_index_second_axis
new = self.get(msa, (Ellipsis, [True, True, False]))
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/tests/test_tabular_msa.py",
line 1271, in get
return obj.loc[indexable]
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 38, in __getitem__
return self._handle_both_axes(*indexable)
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 50, in _handle_both_axes
return self._slice_on_second_axis(self._obj, pos_index)
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 62, in _slice_on_second_axis
if self.is_scalar(indexable, axis=1):
  File
"/<>/.pybuild/cpython3_3.7_skbio/build/skbio/alignment/_indexing.py",
line 171, in is_scalar
duplicated_key = indexable in index.get_duplicates()
  File "/usr/lib/python3/dist-packages/pandas/core/indexes/base.py", line 2035,
in __contains__
hash(key)
TypeError: unhashable type: 'list'

Bug#911610: marked as done (eldav: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 11:49:14 +
with message-id 
and subject line Bug#911612: fixed in apel 10.8+0.20120427-19
has caused the Debian Bug report #911612,
regarding eldav: files missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el
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.)


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

Hi,

during a test with piuparts I noticed your package removes files that
were installed by this package.

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

1m7.9s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/share/emacs/site-lisp/eldav/eldav.el (from eldav 
package)
  debsums: missing file /usr/share/emacs/site-lisp/eldav/vc-eldav.el (from 
eldav package)


cheers,

Andreas


eldav_0.8.1-10.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: apel
Source-Version: 10.8+0.20120427-19

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

Debian distribution maintenance software
pp.
Tatsuya Kinoshita  (supplier of updated apel 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: Mon, 17 Dec 2018 20:22:47 +0900
Source: apel
Binary: apel
Architecture: source all
Version: 10.8+0.20120427-19
Distribution: unstable
Urgency: medium
Maintainer: Tatsuya Kinoshita 
Changed-By: Tatsuya Kinoshita 
Description:
 apel   - portable library for emacsen
Closes: 911612
Changes:
 apel (10.8+0.20120427-19) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
 .
   [ Tatsuya Kinoshita ]
   * Don't remove *.el files when handling reverse dependency (closes: #911612)
   * Use debhelper-compat 11
   * Update Standards-Version to 4.2.1
Checksums-Sha1:
 d09aeba7ed9422b615da57445f241d1e1045963d 1854 apel_10.8+0.20120427-19.dsc
 8376c94ca9b16dddb4bb4aa9c9e72da999c75a95 23244 
apel_10.8+0.20120427-19.debian.tar.xz
 350c38c695f433a0bb4d630a8e5519e38d00ae86 118240 apel_10.8+0.20120427-19_all.deb
 168dd82d63987c1c4b4820e7874177973c8ecd9b 5756 
apel_10.8+0.20120427-19_amd64.buildinfo
Checksums-Sha256:
 af28a301d41a78f16d57c1f94c8bffb39ba05b7f85251884c19e19cb247cf421 1854 
apel_10.8+0.20120427-19.dsc
 bbbe7e0401eedf071d2cf2a9dc28cad8121c3bfa1c708cee7441632bbc668822 23244 
apel_10.8+0.20120427-19.debian.tar.xz
 7e6f930826e36e368728a52d8f13a1c0b1c356f0e00ee618c8597222c6a41828 118240 
apel_10.8+0.20120427-19_all.deb
 f4e094ea3e029962dc1681603ac7c66eeb43828fd99dfe535a30478525f504d3 5756 
apel_10.8+0.20120427-19_amd64.buildinfo
Files:
 db272a70c1855283a63f6250834b4bb8 1854 lisp optional apel_10.8+0.20120427-19.dsc
 40de76e48b52e717c52f96ca365f9693 23244 lisp optional 
apel_10.8+0.20120427-19.debian.tar.xz
 582c5285bcd6fd25022085ed27b27896 118240 lisp optional 
apel_10.8+0.20120427-19_all.deb
 3f43bf80b15188de2f8a42761e37e9e2 5756 lisp optional 
apel_10.8+0.20120427-19_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAxxiPZTvHz7xexyE5e+rkAgOpjwFAlwXiS4ACgkQ5e+rkAgO
pjwBFQ//Xm9EFIC4H9vy1IWfzxBmqVNBogSt370qVe4m6YR/wETGFxXranOufpLH
yPg+FmVVgjMCIulumGPZQl2XFvEN7q+wYKO05DCu5ZX+iQv7r2hQM70rQOfZELN4
VTNf6YCF9aeIOBR3y3YUfnPux7mwtDyx0ztXUYhHFFfJbHpRwU4xrVkHVvhc6JQl
necq3zyz0KXvMhzvPunPca94I+hSQ4b5Bp5NZZA6ftPMhsLDVHJLh4IK3nykhoql
KC3OKuvVULS9hqMPEG1w8xMwqB8Eoqt1oLDylgx4fKZMim6sx2qJhIZGkQZcK433
tlKfaC+ave5mbpvpxMrt70/wjsejvh7jKUg/XA27EtOU77wJpc5VfcjS5+0uzDKC
gw1foch1aeFQ5+yyeo8zsHwuGrZtUXPEbaHEj0WEOP+1iZfWFIJrJsb5a175JPeg
WJM9Z8rVYNHzZXyICY1y5tbi9FmByhUNg7Wk8Gq1iqk7UWTua4VzvlaL3kA3JDmU
vvSxEy9DRVfCi2P1gu+KfOtJg2ryqw4JP3Dwzu69S1kRHxdsTB6inwxo3i3+5MtE
ESq+ssOJ6Ws/R3XPOtek1RQWmWtF9dSGbcHnBob/RQSANuZoo6hKyP4dxF2hPQ3E
5TCN93tf+NV+OCdGH1FVolBXYU6BNaE9Gqd4CnNDrPtjHefuvQE=
=/rhl
-END PGP SIGNATURE End Message ---

Bug#909523: Default configuration is incompatible with a non-SELinux active LSM

[Dmitry Smirnov]

On Monday, 17 December 2018 1:24:05 AM AEDT intrigeri wrote:
> I'm bumping severity to RC as the daemon won't start on current
> testing/sid with its default configuration. Anthony confirmed that my
> proposed fix works: a one-line change to disable the problematic line
> in the default configuration file.

IMHO something that is so easy to fix hardly qualifies for severity 
"serious"...


> I notice that Dmitry did all the cachefilesd uploads in the last 5+
> years, including packaging two new upstream releases; thanks!

:)


> Maybe Dmitry would be interested in co-maintaining or salvaging
> this package?

He is busy and currently not using this package... He tries to reduce number 
of packages he is involved with so he would be reluctant to assume full 
responsibility for this package as a maintainer. :)


> If one of you feels responsible for maintaining this package but
> temporarily lacks time, I (or one of the attendees to one of the many
> upcoming BSPs) will gladly fix this with a NMU.

Please, please. That would be really nice if you could. Thanks.

-- 
Cheers,
 Dmitry Smirnov.

---

The more false we destroy the more room there will be for the true.
 -- Robert G. Ingersoll, 1902


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

Bug#911612: marked as done (tdiary-mode: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 11:49:14 +
with message-id 
and subject line Bug#911612: fixed in apel 10.8+0.20120427-19
has caused the Debian Bug report #911612,
regarding tdiary-mode: files missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el
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.)


-- 
911612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tdiary-mode
Version: 5.0.10-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
were installed by this package.

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

0m59.2s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/share/emacs/site-lisp/tdiary-mode/http.el (from 
tdiary-mode package)
  debsums: missing file /usr/share/emacs/site-lisp/tdiary-mode/tdiary-mode.el 
(from tdiary-mode package)


cheers,

Andreas


tdiary-mode_5.0.10-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: apel
Source-Version: 10.8+0.20120427-19

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

Debian distribution maintenance software
pp.
Tatsuya Kinoshita  (supplier of updated apel 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: Mon, 17 Dec 2018 20:22:47 +0900
Source: apel
Binary: apel
Architecture: source all
Version: 10.8+0.20120427-19
Distribution: unstable
Urgency: medium
Maintainer: Tatsuya Kinoshita 
Changed-By: Tatsuya Kinoshita 
Description:
 apel   - portable library for emacsen
Closes: 911612
Changes:
 apel (10.8+0.20120427-19) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
 .
   [ Tatsuya Kinoshita ]
   * Don't remove *.el files when handling reverse dependency (closes: #911612)
   * Use debhelper-compat 11
   * Update Standards-Version to 4.2.1
Checksums-Sha1:
 d09aeba7ed9422b615da57445f241d1e1045963d 1854 apel_10.8+0.20120427-19.dsc
 8376c94ca9b16dddb4bb4aa9c9e72da999c75a95 23244 
apel_10.8+0.20120427-19.debian.tar.xz
 350c38c695f433a0bb4d630a8e5519e38d00ae86 118240 apel_10.8+0.20120427-19_all.deb
 168dd82d63987c1c4b4820e7874177973c8ecd9b 5756 
apel_10.8+0.20120427-19_amd64.buildinfo
Checksums-Sha256:
 af28a301d41a78f16d57c1f94c8bffb39ba05b7f85251884c19e19cb247cf421 1854 
apel_10.8+0.20120427-19.dsc
 bbbe7e0401eedf071d2cf2a9dc28cad8121c3bfa1c708cee7441632bbc668822 23244 
apel_10.8+0.20120427-19.debian.tar.xz
 7e6f930826e36e368728a52d8f13a1c0b1c356f0e00ee618c8597222c6a41828 118240 
apel_10.8+0.20120427-19_all.deb
 f4e094ea3e029962dc1681603ac7c66eeb43828fd99dfe535a30478525f504d3 5756 
apel_10.8+0.20120427-19_amd64.buildinfo
Files:
 db272a70c1855283a63f6250834b4bb8 1854 lisp optional apel_10.8+0.20120427-19.dsc
 40de76e48b52e717c52f96ca365f9693 23244 lisp optional 
apel_10.8+0.20120427-19.debian.tar.xz
 582c5285bcd6fd25022085ed27b27896 118240 lisp optional 
apel_10.8+0.20120427-19_all.deb
 3f43bf80b15188de2f8a42761e37e9e2 5756 lisp optional 
apel_10.8+0.20120427-19_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAxxiPZTvHz7xexyE5e+rkAgOpjwFAlwXiS4ACgkQ5e+rkAgO
pjwBFQ//Xm9EFIC4H9vy1IWfzxBmqVNBogSt370qVe4m6YR/wETGFxXranOufpLH
yPg+FmVVgjMCIulumGPZQl2XFvEN7q+wYKO05DCu5ZX+iQv7r2hQM70rQOfZELN4
VTNf6YCF9aeIOBR3y3YUfnPux7mwtDyx0ztXUYhHFFfJbHpRwU4xrVkHVvhc6JQl
necq3zyz0KXvMhzvPunPca94I+hSQ4b5Bp5NZZA6ftPMhsLDVHJLh4IK3nykhoql
KC3OKuvVULS9hqMPEG1w8xMwqB8Eoqt1oLDylgx4fKZMim6sx2qJhIZGkQZcK433
tlKfaC+ave5mbpvpxMrt70/wjsejvh7jKUg/XA27EtOU77wJpc5VfcjS5+0uzDKC
gw1foch1aeFQ5+yyeo8zsHwuGrZtUXPEbaHEj0WEOP+1iZfWFIJrJsb5a175JPeg
WJM9Z8rVYNHzZXyICY1y5tbi9FmByhUNg7Wk8Gq1iqk7UWTua4VzvlaL3kA3JDmU
vvSxEy9DRVfCi2P1gu+KfOtJg2ryqw4JP3Dwzu69S1kRHxdsTB6inwxo3i3+5MtE
ESq+ssOJ6Ws/R3XPOtek1RQWmWtF9dSGbcHnBob/RQSANuZoo6hKyP4dxF2hPQ3E
5TCN93tf+NV+OCdGH1FVolBXYU6BNaE9Gqd4CnNDrPtjHefuvQE=
=/rhl
-END PGP SIGNATURE End Message ---

Processed: affects 916683

[Debian Bug Tracking System]

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

> affects 916683 msmtp
Bug #916683 [libgnutls30] libgnutls30: breaks msmtp 1.6.7-1
Added indication that 916683 affects msmtp
> thanks
Stopping processing here.

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

Bug#914297: apache2: getrandom call blocks on first startup, systemd kills with timeout

[Michael Biebl]

Control: severity -1 wishlist
Control: retitle -1 allow crediting the seed file for some entropy
Control: forwarded -1  https://github.com/systemd/systemd/pull/10621

On Sat, 15 Dec 2018 09:17:46 +0100 Stefan Fritsch  wrote:
> reassign 914297 systemd
> affects 914297 apache2
> thanks
> 
> On Saturday, 15 December 2018 02:24:54 CET Alexander E. Patrakov wrote:
> > Stefan Fritsch :
> > > The rng should be initialized after the seed is loaded from disk.
> > 
> > This is false according to systemd developers. Its state is changed,
> > but it is still not initialized, because they think that the seed
> > might come from a gold master image.
> 
> That's broken, then.

I don't agree with this assessment. systemd-random-seed works the way it
is supposed to work.

> It turns out there was a similar bug against openssh which was closed as 
> wontfix [1]. I don't see how apache can do anything about this, either.

There is. Don't request high-quality randomness during boot unless you
explicitly need it.

You best talk to the openssl maintainers and upstream about this.
It is my understanding that it's a behavioural change in openssl which
is causing all this by using getrandom() which in turn requires high
quality randomness on newer kernels.

> But I disagree with the systemd maintainers that there is nothing that 
> systemd 
> can do about this. They should credit the entropy loaded from the seed but 
> save a new seed immediately after reading it during startup, to avoid that 
> the 
> same seed is used more than once.

Even if systemd-random-seed get's an option to credit the entropy, this
will be opt in. So if you have to explicitly configure it, you have
better options like using virtio-rng. It's not even clear if the PR I
mentioned above is merged anytime soon and will make it into buster.

Second, it won't have any effect if no seed file exists. This can happen
on a first boot, so affects especially containers and VMs which
typically get rebuilt instead of rebooted after upgrades. And
incidentally those type of systems are affected the most.

Third, there are other init systems besides systemd, which behave the
same as systemd in that regard and are affected as well. So a -c switch
for systemd-random-seed, as proposed in the upstream PR, won't help
those systems either.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#914297: apache2: getrandom call blocks on first startup, systemd kills with timeout

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #914297 [systemd] apache2: getrandom call blocks on first startup, systemd 
kills with timeout
Severity set to 'wishlist' from 'serious'
> retitle -1 allow crediting the seed file for some entropy
Bug #914297 [systemd] apache2: getrandom call blocks on first startup, systemd 
kills with timeout
Changed Bug title to 'allow crediting the seed file for some entropy' from 
'apache2: getrandom call blocks on first startup, systemd kills with timeout'.
> forwarded -1  https://github.com/systemd/systemd/pull/10621
Bug #914297 [systemd] allow crediting the seed file for some entropy
Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/10621'.

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

Processed: Re: Bug#916678: systemd: Caught , dumped core as pid 2097

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #916678 [systemd] systemd: Caught , dumped core as pid 2097
Severity set to 'important' from 'critical'
> tags -1 moreinfo
Bug #916678 [systemd] systemd: Caught , dumped core as pid 2097
Added tag(s) moreinfo.

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

Bug#916678: systemd: Caught , dumped core as pid 2097

[Michael Biebl]

Control: severity -1 important
Control: tags -1 moreinfo

Am 17.12.18 um 11:25 schrieb Cristian Ionescu-Idbohrn:

> | systemd[1]: Caught , dumped core as pid 2097.

Please try to get a backtrace following
https://wiki.debian.org/HowToGetABacktrace

Thanks,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#916683: libgnutls30: breaks msmtp 1.6.7-1

[Jonas Smedegaard]

Package: libgnutls30
Version: 3.6.5-2
Severity: serious
Justification: Policy 3.5

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I use msmtp, and it worked fine until few days ago,
with msmtp 1.6.7-1 and libgnutls30 3.5.19-1+b1.

Upgrading to libgnutls30 3.6.5-2 breaks msmtp:
Any attempt at connecting to a TLS-secured site gets disconnected.

Seems liek backwards-incompatible ABI change to me,
which I believe should be handled in coordination with its
reverse dependencies.  Hence the severity.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlwXhkIACgkQLHwxRsGg
ASE9yxAAhKWYFkAKdHem+DVzuK5vcym4ZgiGoK12JIkRpTkX7g/CdgoA4lXyszNJ
sdV87pI6ViiE6Y4ZTl+/81vhiJ52TnDq6XJnwGlHp8+BeXHc87ERMHkC4wbdoqxa
vZgpBkQ8Nb7gsZ6JA5ZEgVBbJ826zcdTvaCQseVsFghfE6RGUfOMba2U4k0D9YHZ
DPWDVHyJhIDgRmM9wm27xBFTPmHQ8llJbnkgoP+DcnTC9HC49vq50el5HtS1tkq8
tUsR3imRQc9AFqSv8d5Q5HOr9aE0UoDt43fPsa/3SNhAos7CYhYiCkELdj1fwmo9
Mea7rk4Huxn6BgXJPY/F4UADs3+rueMSi/Te6PEHERM1Zb0HFOoGQNI4E+F/y6bF
l3ArA8ZncmOmKe29ES3CIQ4T329O68RlEcL/UEJp76l1wsV9kXTZ0234gzCkrsUr
7OkqYtHGetSikBlknN2v5qBWPUJ9QiueTfVwNqg8vlfxBL3NhC0KmMpcEhbgRgqH
50Il1fKutIqO2n7U+DKpvzJ/WiKB1W9bTKqM4KLdEixYF1ie1HTMgxMvN+pCrMRD
IIAUOg23hMmHfoxoUCqNYlZBGogqYsThvziAQOBbLugWlKroAO3t/X5dQWS0igBr
qcCr19oAvsio4BUWBpKlgi+3YUY9o9g9Y/tp4mRtV+iAdWaUKi4=
=fl8q
-END PGP SIGNATURE-

Processed: Re: Bug#911610: eldav: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el

[Debian Bug Tracking System]

Processing control commands:

> reassign 911610 apel 10.8+0.20120427-18
Bug #911610 [eldav] eldav: files missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el
Bug reassigned from package 'eldav' to 'apel'.
No longer marked as found in versions eldav/0.8.1-7 and eldav/0.8.1-10.
Ignoring request to alter fixed versions of bug #911610 to the same values 
previously set
Bug #911610 [apel] eldav: files missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el
Marked as found in versions apel/10.8+0.20120427-18.
> forcemerge 911612 911610
Bug #911612 [apel] tdiary-mode: files missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el
Bug #911610 [apel] eldav: files missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el
Merged 911610 911612

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

Bug#911610: eldav: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el

[Tatsuya Kinoshita]

Control: reassign 911610 apel 10.8+0.20120427-18
Control: forcemerge 911612 911610

This problem is caused by apel when handling reverse dependency.

Thanks,
--
Tatsuya Kinoshita


pgpYni0ZT6_wD.pgp
Description: PGP signature

Bug#915507: marked as done (please remove Depends on common-lisp-controller)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 11:04:11 +
with message-id 
and subject line Bug#915507: fixed in cl-regex 1-4.1
has caused the Debian Bug report #915507,
regarding please remove Depends on common-lisp-controller
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.)


-- 
915507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cl-regex
Version: 1-4
Severity: serious
Tags: patch sid buster
Control: block 913649 by -1

Dear Maintainer,

Please drop the Depends on common-lisp-controller. This package is obsolete,
and will not ship with Buster. It has been superseded by ASDF, which is shipped
by all Common Lisp implementations in Debian.

Dropping the dependency and the postinst and prerm scripts should be enough.
ASDF is able to locate the files where they are installed (i.e. under
/usr/share/common-lisp/).

Best,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org
--- End Message ---
--- Begin Message ---
Source: cl-regex
Source-Version: 1-4.1

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

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

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated cl-regex 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: Mon, 17 Dec 2018 11:38:28 +0100
Source: cl-regex
Binary: cl-regex
Architecture: source
Version: 1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Matthew Danish 
Changed-By: Sébastien Villemot 
Description:
 cl-regex   - Common Lisp regular expression compiler/matcher
Closes: 915507
Changes:
 cl-regex (1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Drop Depends on common-lisp-controller, and postinst and prerm scripts
 (Closes: #915507)
Checksums-Sha1:
 21f254a4d38be8537ed7c17c95af586bc3a5bd89 1615 cl-regex_1-4.1.dsc
 70c618c0cefb9b0e39320a3bb6944f2889c14dc0 5200 cl-regex_1-4.1.diff.gz
 0edd92035274400300259b299ed8ea599ab414c7 5230 cl-regex_1-4.1_amd64.buildinfo
Checksums-Sha256:
 b3779f586d2948aa13b20653cf71ea6924c77c9e2b8e251f928459182f4aaa15 1615 
cl-regex_1-4.1.dsc
 6df1e81a07ea455c445dccaddc65660ac1b9bd7d84279500b4cd62b04261d52e 5200 
cl-regex_1-4.1.diff.gz
 0d343dc9e300137bb5ff34e8cdcaf105d801073e0c81e2c83c868aba497e3467 5230 
cl-regex_1-4.1_amd64.buildinfo
Files:
 393195c28301dfb7422fb571502a84c6 1615 devel optional cl-regex_1-4.1.dsc
 a8df6c10628c40b0f021d30d971abad3 5200 devel optional cl-regex_1-4.1.diff.gz
 01adb2a592c02e6f1a16892381fa0082 5230 devel optional 
cl-regex_1-4.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlwXfk0ACgkQLOzpNQ7O
vkoyfRAAgze3dvK4LGvlaYgaQrSO1evs0ggR0+Z0lFmz5YhH6tZI1Zqi4wYY55HH
965SL1q562iw7654tM+AWLuSpx+GxE3qbKBXsz/GLg1Ih9z/IYg+dH8PUH5d3G5y
baog8n6qt9AQg2beTOvHSm92hGPY/9N0RyWk1kO7cgS78A15a8Hs9FYXS2mWRQD/
kWuKDeNKlyWGtwxE665g5i/JkgS1g940X4hmG3SSvic+UBH8KEuQiLCYAbyE7px5
XuBHz8uJ7HdBl1er5tWurLOtG7Mt95K9hAmcDvnobBb6Kjoet/xX51saUgz4fDam
0VD/ulG5NgCr3YYslkjITIren7xzr6fEjS3eLReT+y+byWEPPboF7a5CsZ9wsqIZ
/214e92tx1dVDzLkET7OIILU2usGP+Au6mAD9L/r24HPboG5Ict7ffnzzZ+nExgt
LHkb7FgfvYtqrPVpUfMY8vu39BCZR79MFw7By8UhMeQH5WXPbQvJ2EzkTHoItiWY
RVu9Sk75H3jI/Ky41Hgi2LmCTQYhXwxKx124aD4dFZU0QNofodgrSUT9wI3UL8df
qprTLjIyge9WI7h6gY4zoDtUXgd1xifY8pTn6b6l3Zm5EvJs1EdPTorPvvyIQZKZ
IiveNjgTsdsC9Wlb0JbYtSyrZSViMDwIOzobPGOUft+uHFGFAs8=
=ztcz
-END PGP SIGNATURE End Message ---

Processed: reassign 916666 to src:python-pip

[Debian Bug Tracking System]

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

> reassign 91 src:python-pip 18.1-2
Bug #91 [src:pythonn-pip] python-pip's autopkg tests are failing (blocking 
python3.7)
Warning: Unknown package 'src:pythonn-pip'
Bug reassigned from package 'src:pythonn-pip' to 'src:python-pip'.
No longer marked as found in versions pythonn-pip/18.1-2.
Ignoring request to alter fixed versions of bug #91 to the same values 
previously set
Bug #91 [src:python-pip] python-pip's autopkg tests are failing (blocking 
python3.7)
Marked as found in versions python-pip/18.1-2.
> thanks
Stopping processing here.

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

Bug#915507: please remove Depends on common-lisp-controller

[Matthew Danish]

Thanks, I am attempting to track down an alternative upstream maintainer
since the original has long since vanished.

On Mon, 17 Dec 2018 at 10:57, Sébastien Villemot 
wrote:

> On Tue, 04 Dec 2018 10:21:43 +0100 =?utf-8?q?S=C3=A9bastien_Villemot?= <
> sebast...@debian.org> wrote:
> > Package: cl-regex
> > Version: 1-4
> > Severity: serious
> > Tags: patch sid buster
> > Control: block 913649 by -1
>
> > Please drop the Depends on common-lisp-controller. This package is
> obsolete,
> > and will not ship with Buster. It has been superseded by ASDF, which is
> shipped
> > by all Common Lisp implementations in Debian.
> >
> > Dropping the dependency and the postinst and prerm scripts should be
> enough.
> > ASDF is able to locate the files where they are installed (i.e. under
> > /usr/share/common-lisp/).
>
> I am about to NMU. The debdiff is attached.
>
> Best,
>
> --
> ⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
> ⣾⠁⢠⠒⠀⣿⡁  Debian Developer
> ⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
> ⠈⠳⣄  http://www.debian.org
>

Bug#915507: please remove Depends on common-lisp-controller

[Sébastien Villemot]

On Tue, 04 Dec 2018 10:21:43 +0100 =?utf-8?q?S=C3=A9bastien_Villemot?= 
 wrote:
> Package: cl-regex
> Version: 1-4
> Severity: serious
> Tags: patch sid buster
> Control: block 913649 by -1

> Please drop the Depends on common-lisp-controller. This package is obsolete,
> and will not ship with Buster. It has been superseded by ASDF, which is 
> shipped
> by all Common Lisp implementations in Debian.
> 
> Dropping the dependency and the postinst and prerm scripts should be enough.
> ASDF is able to locate the files where they are installed (i.e. under
> /usr/share/common-lisp/).

I am about to NMU. The debdiff is attached.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org
diff -u cl-regex-1/debian/changelog cl-regex-1/debian/changelog
--- cl-regex-1/debian/changelog
+++ cl-regex-1/debian/changelog
@@ -1,3 +1,11 @@
+cl-regex (1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Drop Depends on common-lisp-controller, and postinst and prerm scripts
+(Closes: #915507)
+
+ -- Sébastien Villemot   Mon, 17 Dec 2018 11:38:28 +0100
+
 cl-regex (1-4) unstable; urgency=low
 
   * Updating debhelper level (Closes: #817398) 
diff -u cl-regex-1/debian/control cl-regex-1/debian/control
--- cl-regex-1/debian/control
+++ cl-regex-1/debian/control
@@ -7,7 +7,7 @@
 
 Package: cl-regex
 Architecture: all
-Depends: common-lisp-controller (>= 3.37), ${misc:Depends}
+Depends: ${misc:Depends}
 Description: Common Lisp regular expression compiler/matcher
  A fully-featured regular expression compiler and matching engine for
  Common Lisp that claims to be roughly 5x-20x times faster than the GNU 
reverted:
--- cl-regex-1/debian/postinst
+++ cl-regex-1.orig/debian/postinst
@@ -1,52 +0,0 @@
-#! /bin/sh
-# postinst script for lml
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# package name according to lisp
-LISP_PKG=regex
-
-# summary of how this script can be called:
-#*  `configure' 
-#*  `abort-upgrade' 
-#*  `abort-remove' `in-favour' 
-#  
-#*  `abort-deconfigure' `in-favour'
-#`removing'
-#   
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-#
-# quoting from the policy:
-# Any necessary prompting should almost always be confined to the
-# post-installation script, and should be protected with a conditional
-# so that unnecessary prompting doesn't happen if a package's
-# installation fails and the `postinst' is called with `abort-upgrade',
-# `abort-remove' or `abort-deconfigure'.
-
-case "$1" in
-configure)
-	register-common-lisp-source ${LISP_PKG}
-
-;;
-
-abort-upgrade|abort-remove|abort-deconfigure)
-
-;;
-
-*)
-echo "postinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
-
-
reverted:
--- cl-regex-1/debian/prerm
+++ cl-regex-1.orig/debian/prerm
@@ -1,42 +0,0 @@
-#! /bin/sh
-# prerm script for lml
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# package name according to lisp
-LISP_PKG=regex
-
-# summary of how this script can be called:
-#*  `remove'
-#*  `upgrade' 
-#*  `failed-upgrade' 
-#*  `remove' `in-favour'  
-#*  `deconfigure' `in-favour'
-#`removing'
-#   
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-remove|upgrade|deconfigure)
-	unregister-common-lisp-source ${LISP_PKG}
-;;
-failed-upgrade)
-;;
-*)
-echo "prerm called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
-
-


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

Bug#911612: tdiary-mode: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el

[Tatsuya Kinoshita]

Control: reassign -1 apel 10.8+0.20120427-18

This problem is caused by apel when handling reverse dependency.

On October 22, 2018 at 4:55PM +0200, anbe (at debian.org) wrote:
>   debsums: missing file /usr/share/emacs/site-lisp/tdiary-mode/http.el (from 
> tdiary-mode package)
>   debsums: missing file /usr/share/emacs/site-lisp/tdiary-mode/tdiary-mode.el 
> (from tdiary-mode package)

However, the *.el files should be installed into another place such
as `/usr/share/tdiary-mode`, and accept the `emacs` flavor in
emacsen-install/remove scripts.

Because the directory `/usr/share/emacs/site-lisp/tdiary-mode` is
for the unversioned emacs flavor.  See also emacsen-common 3.x.

Thanks,
--
Tatsuya Kinoshita


pgpW89iNGmY4D.pgp
Description: PGP signature

Processed: Re: tdiary-mode: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 apel 10.8+0.20120427-18
Bug #911612 [tdiary-mode] tdiary-mode: files missing after upgrade from 
stretch: /usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el
Bug reassigned from package 'tdiary-mode' to 'apel'.
No longer marked as found in versions tdiary-contrib/5.0.10-2, 
tdiary-contrib/5.0.2-2, and tdiary-contrib/5.0.10-1.
Ignoring request to alter fixed versions of bug #911612 to the same values 
previously set
Bug #911612 [apel] tdiary-mode: files missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el
Marked as found in versions apel/10.8+0.20120427-18.

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

Bug#916678: systemd: Caught , dumped core as pid 2097

[Cristian Ionescu-Idbohrn]

Package: systemd
Version: 239-13
Severity: critical
Justification: breaks the whole system

While trying to upgrade postfix* packages I ended up in this mess :(
Every attempt (I know off) to get out of it failed :(

I also lost the ability to ssh login.

,
| systemd[1]: Caught , dumped core as pid 2097.
|
| Broadcast message from systemd-journald@host (Sun 2018-12-16 17:16:09 CET):
|
| systemd[1]: Freezing execution.
|
| Failed to reload daemon: Connection reset by peer
| Failed to retrieve unit state: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
| Failed to stop postfix.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
| See system logs and 'systemctl status postfix.service' for details.
| Failed to get load state of postfix.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
| invoke-rc.d: initscript postfix, action "stop" failed.
| dpkg: warning: old postfix package pre-removal script subprocess returned 
error exit status 1
| dpkg: trying script from the new package instead ...
| Failed to reload daemon: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
| Failed to retrieve unit state: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
| Failed to stop postfix.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
| See system logs and 'systemctl status postfix.service' for details.
| Failed to get load state of postfix.service: Connection timed out
| invoke-rc.d: initscript postfix, action "stop" failed.
| dpkg: error processing archive 
/tmp/user/0/apt-dpkg-install-FfjLf1/12-postfix_3.3.2-1_amd64.deb (--unpack):
|  new postfix package pre-removal script subprocess returned error exit status 
1
| Failed to reload daemon: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
| Failed to reload daemon: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
| Failed to retrieve unit state: Connection timed out
| Failed to start postfix.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
| See system logs and 'systemctl status postfix.service' for details.
| invoke-rc.d: initscript postfix, action "start" failed.
| Failed to get properties: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
| dpkg: error while cleaning up:
|  installed postfix package post-installation script subprocess returned error 
exit status 1
| Errors were encountered while processing:
|  /tmp/user/0/apt-dpkg-install-FfjLf1/12-postfix_3.3.2-1_amd64.deb
| [master 985cc4a] committing changes in /etc after apt run
|  1 file changed, 2 deletions(-)
| Error: Timeout was reached
| needrestart is being skipped since dpkg has failed
| E: Sub-process /usr/bin/dpkg returned an error code (1)
|
| root@host:~# systemctl status postfix.service
| Failed to get properties: Connection timed out
`

I don't really think the segfault had anything to do with the upgrade
of the postfix* packages, but with what happened prior to that.  libc*
packages were upgraded (caused by a dependency from gcc* package
upgrades, I guess).  I happen to have that documented:

,
| commit d31bcecaf0c85e3ced155a5b2ad813b65181c365
| Author: root 
| Date:   Sun Dec 16 17:02:44 2018 +0100
|
| committing changes in /etc after apt run
|
| Package changes:
| -cpp-7 7.3.0-30 amd64
| -cpp-8 8.2.0-9 amd64
| +cpp-7 7.4.0-1 amd64
| +cpp-8 8.2.0-12 amd64
| -g++-8 8.2.0-9 amd64
| -g++-8-multilib 8.2.0-9 amd64
| +g++-8 8.2.0-12 amd64
| +g++-8-multilib 8.2.0-12 amd64
| -gcc-7 7.3.0-30 amd64
| -gcc-7-base 7.3.0-30 amd64
| -gcc-7-multilib 7.3.0-30 amd64
| -gcc-8 8.2.0-9 amd64
| -gcc-8-base 8.2.0-9 amd64
| -gcc-8-multilib 8.2.0-9 amd64
| +gcc-7 7.4.0-1 amd64
| +gcc-7-base 7.4.0-1 amd64
| +gcc-7-multilib 7.4.0-1 amd64
| +gcc-8 8.2.0-12 amd64
| +gcc-8-base 8.2.0-12 amd64
| +gcc-8-multilib 8.2.0-12 amd64
| -lib32asan4 7.3.0-30 amd64
| -lib32asan5 8.2.0-9 amd64
| -lib32atomic1 8.2.0-9 amd64
| -lib32cilkrts5 7.3.0-30 amd64
| +lib32asan4 7.4.0-1 amd64
| +lib32asan5 8.2.0-12 amd64
| +lib32atomic1 8.2.0-12 amd64
| +lib32cilkrts5 7.4.0-1 amd64
| -lib32gcc-7-dev 7.3.0-30 amd64
| -lib32gcc-8-dev 8.2.0-9 amd64
| -lib32gcc1 1:8.2.0-9 amd64
| -lib32gomp1 8.2.0-9 amd64
| -lib32itm1 8.2.0-9 amd64
| -lib32mpx2 8.2.0-9 amd64
| -lib32quadmath0 8.2.0-9 amd64
| -lib32stdc++-7-dev 7.3.0-30 amd64
| -lib32stdc++-8-dev 8.2.0-9 amd64
| -lib32stdc++6 8.2.0-9 amd64
| -lib32ubsan0 7.3.0-30 amd64
| -lib32ubsan1 8.2.0-9 amd64
| +lib32gcc-7-dev 

Bug#906371: Changes in alter-sequence-alignment break build of jmodeltest (Was: Bug#906371: jmodeltest: FTBFS in buster/sid)

[Andreas Tille]

Hi,

after I tried to follow the initial hint of Emmanuel I admit I was not
successful to finally build the package:

On Wed, Oct 17, 2018 at 10:32:58AM +0200, Andreas Tille wrote:
> > Good catch.  The latest upstream version of alter-sequence-alignment has
> > split these to an additional alter-lib.jar and the time of the build
> > failure of jmodeltest correlates with the upload of
> > alter-sequence-alignment 1.3.4-1.  But now the question is:  How to
> > teach the jmodeltest build system to use alter-lib.jar.  I think adding
> > it to debian/manifest[1] is needed to *run* jmodeltest but it surely
> > does not help at build time.  I have not found any place where the
> > build system specifies the needed jars. :-(
> 
> I tried to add alter-lib.jar to build.xml[1].  Unfortunately this does
> not help to fix the issue
> 
> [javac] 
> /build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:28:
>  error: package parser does not exist
> [javac] import parser.ParseException;
> [javac]  ^
> [javac] 
> /build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:29:
>  error: package converter does not exist
> [javac] import converter.Converter;
> [javac] ^
> [javac] 
> /build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:30:
>  error: package converter does not exist
> [javac] import converter.DefaultFactory;
> [javac] ^
> [javac] 
> /build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:31:
>  error: package converter does not exist
> [javac] import converter.Factory;
> 
> Any hint how to get the classes in alter-lib.jar found?
> 
> Moreover I get lots of
> 
> [javac] 
> /build/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/exe/Distributor.java:23:
>  warning: [deprecation] Observable in java.util has been deprecated
> [javac] import java.util.Observable;
> [javac] ^

Any more hints?

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Bug#913116: Needs to depend on chromium-sandbox

[Bastian Blank]

On Mon, Dec 17, 2018 at 04:32:50AM -0500, Michael Gilbert wrote:
> On Fri, Nov 16, 2018 at 4:30 AM Bastian Blank wrote:
> > Debian does not support unprivileged user namespaces, so chromium needs
> > to depend on -sandbox to get a working package.
> The debian version of the kernel package provides
> kernel.unprivileged_userns_clone as a runtime selectable option for a
> while now.

Which is disabled by default and a package must not mangle it.

> Since this can be used in place of chromium's setuid binary, my
> opinion is that the Depends relationship on chromium-sandbox is no
> longer required.

Nope, at least if the package is supposed to work without admin
intervention.

Regards,
Bastian

-- 
Virtue is a relative term.
-- Spock, "Friday's Child", stardate 3499.1

Bug#850915: marked as done (ghc: Please switch to llvm 6.0)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 10:42:07 +0100
with message-id <9d6575b5-dc46-76c4-60ed-a2baaff20...@debian.org>
and subject line ghc uses llvm-6
has caused the Debian Bug report #850915,
regarding ghc: Please switch to llvm 6.0
to be marked as done.

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

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


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

Hello,

The armel build issue on 3.8 and 3.9 has been fixed thanks to a fix in 
libstdc++.
ghc can now change llvm version.

This is the last package using llvm 3.7, blocking its removal.
(note that I stopped caring about 3.7 more than a year ago, it is far behing 
3.8 or 3.9
in term of maintenance/support).

Sylvestre
--- End Message ---
--- Begin Message ---
Closing this one

G.--- End Message ---

Bug#913116: Needs to depend on chromium-sandbox

[Michael Gilbert]

On Fri, Nov 16, 2018 at 4:30 AM Bastian Blank wrote:
> Debian does not support unprivileged user namespaces, so chromium needs
> to depend on -sandbox to get a working package.

The debian version of the kernel package provides
kernel.unprivileged_userns_clone as a runtime selectable option for a
while now.

Since this can be used in place of chromium's setuid binary, my
opinion is that the Depends relationship on chromium-sandbox is no
longer required.

Best wishes,
Mike

Bug#915779: marked as done (vtk7: unsatisfable dependencies on armhf/armel)

[Debian Bug Tracking System]

Your message dated Mon, 17 Dec 2018 09:19:49 +
with message-id 
and subject line Bug#915779: fixed in vtk7 7.1.1+dfsg1-12
has caused the Debian Bug report #915779,
regarding vtk7: unsatisfable dependencies on armhf/armel
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.)


-- 
915779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvtk7-qt-dev
Version: 7.1.1+dfsg1-11
Severity: serious

From britney:
libvtk7-qt-dev/armel unsatisfiable Depends: libqt5opengl5-desktop-dev
libvtk7-qt-dev/armhf unsatisfiable Depends: libqt5opengl5-desktop-dev


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: vtk7
Source-Version: 7.1.1+dfsg1-12

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

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

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated vtk7 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: Mon, 17 Dec 2018 10:03:58 +0100
Source: vtk7
Binary: libvtk7-dev libvtk7-qt-dev libvtk7.1 libvtk7.1-qt libvtk7-jni 
libvtk7-java python3-vtk7 tcl-vtk7 vtk7 vtk7-doc vtk7-examples
Architecture: source
Version: 7.1.1+dfsg1-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Gert Wollny 
Description:
 libvtk7-dev - VTK header files
 libvtk7-java - Visualization Toolkit - A high level 3D visualization library - 
j
 libvtk7-jni - Visualization Toolkit - A high level 3D visualization library - j
 libvtk7-qt-dev - VTK header files, containing Qt files
 libvtk7.1  - VTK libraries
 libvtk7.1-qt - VTK libraries, Qt files
 python3-vtk7 - Python bindings for VTK
 tcl-vtk7   - Tcl bindings for VTK
 vtk7   - Binaries for VTK7
 vtk7-doc   - VTK class reference documentation
 vtk7-examples - VTK examples
Closes: 915779
Changes:
 vtk7 (7.1.1+dfsg1-12) unstable; urgency=medium
 .
   [ Emilio Pozuelo Monfort ]
   * Let libvtk7-qt-dev depend on libqt5opengl5-dev rather than on
 libqt5opengl5-desktop-dev, as it was done for the build-dep.
 This fixes the dependency on arm{el,hf} which have OpenGL ES.
 Closes: #915779.
Checksums-Sha1:
 7c76f3ea46f800051e80ad9208014c6ade406328 3661 vtk7_7.1.1+dfsg1-12.dsc
 691a3116cc5066e3d694df49563fcad28a7a05b2 26256 
vtk7_7.1.1+dfsg1-12.debian.tar.xz
 4bd0e8df36bae95530b814c1f6f4b9bf068624f5 31894 
vtk7_7.1.1+dfsg1-12_source.buildinfo
Checksums-Sha256:
 7e4052bf97f888c059feecebfd4292b3b26b96bc81d76951c8adfb7a17340e74 3661 
vtk7_7.1.1+dfsg1-12.dsc
 a61d2802643c4a13684279bf1e80a9042ccb3c36f1059e1633270eeec881bfbe 26256 
vtk7_7.1.1+dfsg1-12.debian.tar.xz
 a38714743abb0a96c9ef2f74e2c9961c92a18432ef805ba03577d0cec8f94534 31894 
vtk7_7.1.1+dfsg1-12_source.buildinfo
Files:
 6d938e2be5f72fb1c34489a43f68a1db 3661 graphics optional vtk7_7.1.1+dfsg1-12.dsc
 d2cf759e50321eeb6511202a4e7b1027 26256 graphics optional 
vtk7_7.1.1+dfsg1-12.debian.tar.xz
 5732153e8615cc0b607b55be52eb7a3b 31894 graphics optional 
vtk7_7.1.1+dfsg1-12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEELtRZww6NuKjZPKd6l/LU/KCfME4FAlwXZsUACgkQl/LU/KCf
ME4psg//bIiPxxEzHjsvvBEtnDCZat1sEQlhFEgTY1T1tsZfQMHc+RMJywTN3CvP
g24h+5tLLnPp2UinI8xNGbUlysHUqqw1EM183uJuYHXNrRBk6UYi4DcqJsiUlaTM
fk8HYP3pZmoiEWJCtrlFKdjqmYTK3C2Wwkb6u7QnRAWK0DaamVLCSbLAoT39ggMW
ogcMX/zg9d28ZdMKndmLNbruj6Wkkeppq5XyWBL6qQDnMhncm/G9Sjv3JhLSSMT2
BR4QZolA8Jbd19ys+MrGVeV/7YoLz+Zb0R0vdd6afCj3SxkwJrWzpP3q/oAGqLTa
HMw9fCSGCVWuB5NsEoghzhm0r+480mYvNdoIWEDUVPhCMhGFHnIz8I0iYZZTGqIH
a3rErnfyI2oJPT72IJkBQQ1mCzIn2OOc7nLBg9FnJ3bGk2DnQoaOMxTNgAQKzDom
KuVQb7sqdKnFGcOVfX46UjKpijKgFaLIzMszXqDUgA55E7XNhe0xdhuqADxnAndv
HOW9jOjxG+PWDYHsbAz4tPjFJlBvM16WVMibEjQlC+A96uDHyVMzKfQLo7+/dcyC

Bug#916674: qemu-guest-agent not started on boot with systemd

[Laurent Bigonville]

Package: qemu-guest-agent
Version: 1:3.1+dfsg-1
Severity: serious

Hello,

qemu-guest-agent now ships a systemd .service which is good, but it's
not being started on boot.

In Fedora/RHEL they are shipping the following file:
https://src.fedoraproject.org/cgit/rpms/qemu.git/tree/99-qemu-guest-agent.rules

That allows the daemon to be started if the device is present (or
appears when the machine has already booted).

Note that their .service file is a bit different:
https://src.fedoraproject.org/cgit/rpms/qemu.git/tree/qemu-guest-agent.service

I think that the udev rule should be enough though.

Also note that the path in the ExecStart is not correct either as the
qemu-ga daemon is installed in /usr/sbin/ and not /usr/bin

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages qemu-guest-agent depends on:
ii  libc6 2.28-3
ii  libgcc1   1:8.2.0-12
ii  libglib2.0-0  2.58.1-2
ii  libudev1  239-15
ii  lsb-base  10.2018112800

qemu-guest-agent recommends no packages.

qemu-guest-agent suggests no packages.

Bug#916673: mandos : Depends: libgnutls30 (< 3.6.0) but 3.6.5-2 is to be installed

[Adrian Bunk]

Package: mandos
Version: 1.7.20-1
Severity: serious

The following packages have unmet dependencies:
 mandos : Depends: libgnutls28-dev (< 3.6.0) but 3.6.5-2 is to be installed or
   libgnutls30 (< 3.6.0) but 3.6.5-2 is to be installed


Additionally, the libgnutls28-dev alternative of the dependencies
looks wrong - this should likely just be libgnutls30.

Processed: Re: vtk7: unsatisfable dependencies on armhf/armel

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #915779 [libvtk7-qt-dev] vtk7: unsatisfable dependencies on armhf/armel
Added tag(s) patch.

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

Bug#915779: vtk7: unsatisfable dependencies on armhf/armel

[Emilio Pozuelo Monfort]

Control: tags -1 patch

Hi Gert!

On Thu, 6 Dec 2018 19:16:28 +0100 Mattia Rizzolo  wrote:
> Package: libvtk7-qt-dev
> Version: 7.1.1+dfsg1-11
> Severity: serious
> 
> From britney:
> libvtk7-qt-dev/armel unsatisfiable Depends: libqt5opengl5-desktop-dev
> libvtk7-qt-dev/armhf unsatisfiable Depends: libqt5opengl5-desktop-dev

I have proposed a fix for this in a MR:

https://salsa.debian.org/science-team/vtk7/merge_requests/1

Can you merge it if it looks good to you, and upload it? This bug is blocking
the ongoing hdf5 and python3 transitions. If you're too busy I can upload it as
an NMU.

Thanks,
Emilio

Bug#916630: terminology: Remote execution via special escape codes that handle unknown media types

[Salvatore Bonaccorso]

Control: retitle -1 terminology: CVE-2018-20167: Remote execution via special 
escape codes that handle unknown media types

Hi

This issue has been assigned CVE-2018-20167.

Regards,
Salvatore

Processed: Re: Bug#916630: terminology: Remote execution via special escape codes that handle unknown media types

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 terminology: CVE-2018-20167: Remote execution via special escape 
> codes that handle unknown media types
Bug #916630 [terminology] terminology: Remote execution via special escape 
codes that handle unknown media types
Changed Bug title to 'terminology: CVE-2018-20167: Remote execution via special 
escape codes that handle unknown media types' from 'terminology: Remote 
execution via special escape codes that handle unknown media types'.

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