Bug#899811: marked as done (litecoin: Invalid maintainer address pkg-bitcoin-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 06:49:34 +
with message-id 
and subject line Bug#899811: fixed in litecoin 0.16.0-2
has caused the Debian Bug report #899811,
regarding litecoin: Invalid maintainer address 
pkg-bitcoin-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.)


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

Dear uploader of litecoin,

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

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: litecoin
Source-Version: 0.16.0-2

We believe that the bug you reported is fixed in the latest version of
litecoin, 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.
Dmitry Smirnov  (supplier of updated litecoin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Jun 2018 16:03:05 +1000
Source: litecoin
Binary: litecoind litecoin-qt
Architecture: source amd64
Version: 0.16.0-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 litecoin-qt - peer-to-peer network based digital currency - Qt GUI
 litecoind  - peer-to-peer network based digital currency - daemon
Closes: 899811
Changes:
 litecoin (0.16.0-2) unstable; urgency=medium
 .
   * set myself as Maintrainer (Closes: #899811).
Checksums-Sha1:
 3ec65792cc2d4ea30098954c6a1b2c6f5e1d2be8 2102 litecoin_0.16.0-2.dsc
 504defd12b156d13fc068b56ab08054c92ac1ca4 14204 litecoin_0.16.0-2.debian.tar.xz
 9a325adb704b2229c6a3d61191e32ff7f144fe40 44748648 
litecoin-qt-dbgsym_0.16.0-2_amd64.deb
 b775db839d3c188b4c24b9c2b46d74d03b400fc4 3952404 litecoin-qt_0.16.0-2_amd64.deb
 d354c06d1a68734f2ec10ebfb5b455809c222c98 18951 
litecoin_0.16.0-2_amd64.buildinfo
 497f54e0515d1218db5038b3d10b3193a8e3534f 31534008 
litecoind-dbgsym_0.16.0-2_amd64.deb
 6d1b96ee6bf8fceda4073a313b070ec7556b0717 1825204 litecoind_0.16.0-2_amd64.deb
Checksums-Sha256:
 7df2c8ba9ad8758857ff4473aea9c993deb0fb653e6ea5020b89bab58de786e8 2102 
litecoin_0.16.0-2.dsc
 d7e772998e0cfe9f424241443c2fd90e62eba0d061aab5ebf6170c7201bb8c13 14204 

Bug#900750: thunderbird: Launching Thunderbird completely locks my Xwindow session

[Jan Hovancik]

I'm having the same issue here.

Disabling apparmor profile (permanently) as described here 
(http://ask.xmodulo.com/disable-particular-apparmor-profile-ubuntu.html) 
helped.


On Tue, 5 Jun 2018 20:25:21 +0200 Carsten Schoenert 
 wrote:

> Hi,
>
> On Mon, Jun 04, 2018 at 10:41:04AM +0200, g.gragnani wrote:
> > f I launch thunderbird the whole xsession (XFCE) locks.
> > I'm only able to move the mouse arrow (without any effect)
> > and switching to a character console by using Cttrl-Alt-F1 etc.
> > Killing thhunderbird does not solve the problem.
> >
> > The same happens in an other machine, with a different set of installed
> > packages, different hardware and running LXDE.
>
> you have apparmor installed and it's likely it may causing issues.
> Can you check the behaviour with a deactivated AppArmor profile and also
> a removed AppAprmor package?
>
> > Versions of packages thunderbird suggests:
> > ii apparmor 2.12-4
>
> Other possible candidates are sometime the kernel. But without a small
> set of logs it's quite impossible to track down the root of the issue.
>
> Regards
> Carsten
>
>

Bug#900868: node-growl: CVE-2017-16042: Does not properly sanitize input before passing it to exec

[Salvatore Bonaccorso]

Source: node-growl
Version: 1.7.0-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/tj/node-growl/issues/60

Hi,

The following vulnerability was published for node-growl.

CVE-2017-16042[0]:
| Growl adds growl notification support to nodejs. Growl before 1.10.2
| does not properly sanitize input before passing it to exec, allowing
| for arbitrary command execution.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-16042
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16042
[1] https://github.com/tj/node-growl/issues/60

Regards,
Salvatore

Processed: Bug #899811 in litecoin marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #899811 [src:litecoin] litecoin: Invalid maintainer address 
pkg-bitcoin-de...@lists.alioth.debian.org
Added tag(s) pending.

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

Bug#899811: Bug #899811 in litecoin marked as pending

[onlyjob]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/litecoin/commit/69db224a383a9006b3b07348e8e8dde574274c9c


set myself as Maintrainer (Closes: #899811).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/899811

Bug#733180: marked as done (litecoin: not suitable for stable)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 16:07:16 +1000
with message-id <2218659.ZjixV9BoM4@deblab>
and subject line Done: litecoin: not suitable for stable
has caused the Debian Bug report #733180,
regarding litecoin: not suitable for stable
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.)


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

Similar to bitcoin bug #718272 this is to prevent "litecoin" migration
to "testing" as long as "litecoin" is considered unsuitable for "stable".
--- End Message ---
--- Begin Message ---
Source: litecoin

I consider Litecoin to be mature and stable enough for "stable".

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


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

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

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 05:35:34 +
with message-id 
and subject line Bug#899775: fixed in mc 3:4.8.21-1
has caused the Debian Bug report #899775,
regarding mc: Invalid maintainer address pkg-mc-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.)


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

Dear uploader of mc,

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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mc
Source-Version: 3:4.8.21-1

We believe that the bug you reported is fixed in the latest version of
mc, 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.
Dmitry Smirnov  (supplier of updated mc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Jun 2018 14:34:10 +1000
Source: mc
Binary: mc mc-data
Architecture: source all amd64
Version: 3:4.8.21-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 mc - Midnight Commander - a powerful file manager
 mc-data- Midnight Commander - a powerful file manager -- data files
Closes: 893389 899775
Changes:
 mc (3:4.8.21-1) unstable; urgency=medium
 .
   * New upstream release [June 2018].
 + added .tar.zst / .tzst support (Closes: #893389).
   * Set myself as Maintainer (Closes: #899775).
   * Updated Vcs URLs to Salsa.
   * Removed needless dependency versioning.
   * Standards-Version: 4.1.4.
   * rules: removed "--parallel" which is implied on DH/compat v11.
Checksums-Sha1:
 82733f730fdd8607fa93b87d2bf561b428b8002e 2098 mc_4.8.21-1.dsc
 f66fec68e6e3e284b6e8f26d96001aa47c23b2d9 2528292 mc_4.8.21.orig.tar.xz
 01f112d4ff95d7182d872d6f4fd572b9fd767dbc 47972 mc_4.8.21-1.debian.tar.xz
 5671f4b0b1858e17a7fe3e78ca5c66d0838298b9 1285592 mc-data_4.8.21-1_all.deb
 4743e3ae2eb5b792493cdd6b2de77dc557dfbdeb 1896492 mc-dbgsym_4.8.21-1_amd64.deb
 6aaae7c1b38572f602f19319f5e84812d158f9e7 8526 mc_4.8.21-1_amd64.buildinfo
 1cdef5ebd9bc2c77bd73873bcf3888af039e59cc 513488 mc_4.8.21-1_amd64.deb
Checksums-Sha256:
 dc8c130ecd2449614b9f350b97

Processed: Re: [Pkg-nagios-devel] Bug#900852: [icingaweb2] FTBFS: font fontello-ifont

[Debian Bug Tracking System]

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

> severity 900852 wishlist
Bug #900852 [icingaweb2] [icingaweb2] FTBFS: font fontello-ifont
Severity set to 'wishlist' from 'serious'
> tags 900852 wontfix
Bug #900852 [icingaweb2] [icingaweb2] FTBFS: font fontello-ifont
Added tag(s) wontfix.
> thanks
Stopping processing here.

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

Processed: Remove found versions

[Debian Bug Tracking System]

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

> notfound 891515 node-colormin/1.1.2-1
Bug #891515 {Done: Pirate Praveen } [node-colormin] 
node-colormin : Depends: node-has (>= 1.0.1) but it is not installable
No longer marked as found in versions node-colormin/1.1.2-1.
> --
Stopping processing here.

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

Processed: gh

[Debian Bug Tracking System]

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

> forwarded 900762 https://github.com/haskell/cabal/issues/5363
Bug #900762 [src:haskell-cabal-install] haskell-cabal-install: causes network 
access during build
Set Bug forwarded-to-address to 'https://github.com/haskell/cabal/issues/5363'.
> quit
Stopping processing here.

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

Bug#900435: marked as done (cryfs: Please rebuild against libcurl4; cryfs removed with the upgrade of libcurl3->libcurl4)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 01:19:28 +
with message-id 
and subject line Bug#900435: fixed in cryfs 0.9.9-2
has caused the Debian Bug report #900435,
regarding cryfs: Please rebuild against libcurl4; cryfs removed with the 
upgrade of libcurl3->libcurl4
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.)


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

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages cryfs depends on:
ii  fuse  2.9.7-1
ii  libc6 2.27-3
ii  libcrypto++6  5.6.4-8
pn  libcurl3  
ii  libcurl4  7.60.0-2
ii  libfuse2  2.9.7-1
ii  libgcc1   1:8.1.0-4
ii  libstdc++68.1.0-4

cryfs recommends no packages.

cryfs suggests no packages.
--- End Message ---
--- Begin Message ---
Source: cryfs
Source-Version: 0.9.9-2

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

Debian distribution maintenance software
pp.
David Steele  (supplier of updated cryfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Jun 2018 19:47:03 -0400
Source: cryfs
Binary: cryfs
Architecture: source amd64
Version: 0.9.9-2
Distribution: unstable
Urgency: high
Maintainer: David Steele 
Changed-By: David Steele 
Description:
 cryfs  - encrypt your files and store them in the cloud
Closes: 900357 900435
Changes:
 cryfs (0.9.9-2) unstable; urgency=high
 .
   * Remove hard-coded shared library dependencies (Closes: #900357, #900435).
Checksums-Sha1:
 29c162f60dc4abe89309ebf1c7a017ea0b5d964a 2277 cryfs_0.9.9-2.dsc
 c72fd331e6ee9e214261b96af9402212f2f5a3da 7888 cryfs_0.9.9-2.debian.tar.xz
 63891941c99014d4327486ee575d2959833ec9cd 29687988 
cryfs-dbgsym_0.9.9-2_amd64.deb
 f9deba5e7ad80ba5ec068301efff185fbcafdbf8 8292 cryfs_0.9.9-2_amd64.buildinfo
 9eb536924b8c13b4b4b12448c7039ee4fdc40bf3 616036 cryfs_0.9.9-2_amd64.deb
Checksums-Sha256:
 b6927461b22a2dcdd7732df6d55bda521c5174d81b814ae8d55361c7bc78d766 2277 
cryfs_0.9.9-2.dsc
 0668b64a742dac98e9b0bc7882bd6ef3d56fb92f52ad4e80ff1126464d704be6 7888 
cryfs_0.9.9-2.debian.tar.xz
 ab8fe8e75d65508fbcad7c9cd43f430e6c60ba02533ee0e2bb0ff4a88a958ceb 29687988 
cryfs-dbgsym_0.9.9-2_amd64.deb
 faab89737859919c8bd2ea082e77b587fb6816cb7c0b342e6c06e055581f57c3 8292 
cryfs_0.9.9-2_amd64.buildinfo
 987b9de04ce280b7ccf9f0ea515c44b5dcc3198c88ad5ee5aed54029b3d3fe24 616036 
cryfs_0.9.9-2_amd64.deb
Files:
 a9e88adadd2ad2ba5cb823c500a2586f 2277 utils optional cryfs_0.9.9-2.dsc
 1c691c2f78be3d002406274b1c52adff 7888 utils optional 
cryfs_0.9.9-2.debian.tar.xz
 c58545417d291f63ca4ac4df3ca0c95c 29687988 debug optional 
cryfs-dbgsym_0.9.9-2_amd64.deb
 da3896481b6e3e6a66f38da23c161c1a 8292 utils optional 
cryfs_0.9.9-2_amd64.buildinfo
 980bc3454d5d592711d21106d04a26c0 616036 utils optional cryfs_0.9.9-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE1wfmOgeeFqqbnJ0CYn67KQqBeoIFAlsXMOQSHGRzdGVlbGVA
Z21haWwuY29tAAoJEGJ+uykKgXqCaVoP/1Ts7YBayDLtg+M5r4/kWXNgJInLTF5S
rgw05nJPvKXIcnNhlngej8lCoZ0xelWROuKjM2fJRyRZiJKr6w5HaoiOis2eAwAD
OZEkOvAwEjaTmWdhk1IDdC/Ny+i5dDBVKlgCzJZjfZOxdGPBTZM61AYuUF1H1Av3
TsrrEXzDFBQzDWSVGjhU+1EytFzZa+4GsXpcxInkaylh5GCaY0b64NoEIgO3YKVS
vqqqt

Bug#900357: marked as done (cryfs: hardcodes shared library dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 01:19:28 +
with message-id 
and subject line Bug#900357: fixed in cryfs 0.9.9-2
has caused the Debian Bug report #900357,
regarding cryfs: hardcodes shared library dependencies
to be marked as done.

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

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


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

Your package hardcodes shared library dependencies rather than letting
shlibs:Depends pick them up as appropriate:

Package: cryfs
Architecture: any
Depends: fuse,
 libcrypto++6,
 libcurl3,
 libfuse2,
 libgcc1,
 libstdc++6 (>= 6),
 ${misc:Depends},
 ${shlibs:Depends}

You should just remove the hardcoded library dependencies.

Emilio
--- End Message ---
--- Begin Message ---
Source: cryfs
Source-Version: 0.9.9-2

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

Debian distribution maintenance software
pp.
David Steele  (supplier of updated cryfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Jun 2018 19:47:03 -0400
Source: cryfs
Binary: cryfs
Architecture: source amd64
Version: 0.9.9-2
Distribution: unstable
Urgency: high
Maintainer: David Steele 
Changed-By: David Steele 
Description:
 cryfs  - encrypt your files and store them in the cloud
Closes: 900357 900435
Changes:
 cryfs (0.9.9-2) unstable; urgency=high
 .
   * Remove hard-coded shared library dependencies (Closes: #900357, #900435).
Checksums-Sha1:
 29c162f60dc4abe89309ebf1c7a017ea0b5d964a 2277 cryfs_0.9.9-2.dsc
 c72fd331e6ee9e214261b96af9402212f2f5a3da 7888 cryfs_0.9.9-2.debian.tar.xz
 63891941c99014d4327486ee575d2959833ec9cd 29687988 
cryfs-dbgsym_0.9.9-2_amd64.deb
 f9deba5e7ad80ba5ec068301efff185fbcafdbf8 8292 cryfs_0.9.9-2_amd64.buildinfo
 9eb536924b8c13b4b4b12448c7039ee4fdc40bf3 616036 cryfs_0.9.9-2_amd64.deb
Checksums-Sha256:
 b6927461b22a2dcdd7732df6d55bda521c5174d81b814ae8d55361c7bc78d766 2277 
cryfs_0.9.9-2.dsc
 0668b64a742dac98e9b0bc7882bd6ef3d56fb92f52ad4e80ff1126464d704be6 7888 
cryfs_0.9.9-2.debian.tar.xz
 ab8fe8e75d65508fbcad7c9cd43f430e6c60ba02533ee0e2bb0ff4a88a958ceb 29687988 
cryfs-dbgsym_0.9.9-2_amd64.deb
 faab89737859919c8bd2ea082e77b587fb6816cb7c0b342e6c06e055581f57c3 8292 
cryfs_0.9.9-2_amd64.buildinfo
 987b9de04ce280b7ccf9f0ea515c44b5dcc3198c88ad5ee5aed54029b3d3fe24 616036 
cryfs_0.9.9-2_amd64.deb
Files:
 a9e88adadd2ad2ba5cb823c500a2586f 2277 utils optional cryfs_0.9.9-2.dsc
 1c691c2f78be3d002406274b1c52adff 7888 utils optional 
cryfs_0.9.9-2.debian.tar.xz
 c58545417d291f63ca4ac4df3ca0c95c 29687988 debug optional 
cryfs-dbgsym_0.9.9-2_amd64.deb
 da3896481b6e3e6a66f38da23c161c1a 8292 utils optional 
cryfs_0.9.9-2_amd64.buildinfo
 980bc3454d5d592711d21106d04a26c0 616036 utils optional cryfs_0.9.9-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE1wfmOgeeFqqbnJ0CYn67KQqBeoIFAlsXMOQSHGRzdGVlbGVA
Z21haWwuY29tAAoJEGJ+uykKgXqCaVoP/1Ts7YBayDLtg+M5r4/kWXNgJInLTF5S
rgw05nJPvKXIcnNhlngej8lCoZ0xelWROuKjM2fJRyRZiJKr6w5HaoiOis2eAwAD
OZEkOvAwEjaTmWdhk1IDdC/Ny+i5dDBVKlgCzJZjfZOxdGPBTZM61AYuUF1H1Av3
TsrrEXzDFBQzDWSVGjhU+1EytFzZa+4GsXpcxInkaylh5GCaY0b64NoEIgO3YKVS
vqqqtg356kPKlYqkjv9rYTuN88jxo9DW+NYxzdm0TNXCjfT1+Uggxltawh9y/3Jc
ewAqJXXDSdjgpg1DVpjTN0bNIqTQ+GqRodasIi3bEwbc2OBoZTEjCQT9gJuCcICI
XomCUmcXo6i3WXntaOJKCU1P93fRdYh9KEUtAmc2CzA9rthU1z+gXk22m6yMHnsI
NMLK6e4amwzrT7tBlN+RZ0tdhPNyUNPj0jWE7gXzGJpCV0i/gGKwe+aU7Lqws5DY
MlUe0/Nc+KgUi/DIAU1mq/HzkinT8cc6Wlkoy6P7bvq7lYQvyLf8P+fs8p+91/DY
IPJG0q2OPpjIT1Xy3PKPs+5hiiSdCPEeWcRFdSfJM7UOn4KpaShdjR8QfY0WwPZs
yRGfXlTlIcBt/k3kd0aerAmcQfdyj+NUWlwUyVCKUBN6y08GVu16hWC2XODyBHfF
7f+MxnVENCPG
=TXa7
-END PGP SIGNATURE End Message ---

Bug#896422: marked as done (python3-pymediainfo: pymediainfo fails to import)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 01:04:43 +
with message-id 
and subject line Bug#896422: fixed in pymediainfo 2.3.0-1
has caused the Debian Bug report #896422,
regarding python3-pymediainfo: pymediainfo fails to import
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.)


-- 
896422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pymediainfo
Version: 2.2.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-pymediainfo importing the module pymediainfo
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pymediainfo/__init__.py", line 6, in 

from pkg_resources import get_distribution
ModuleNotFoundError: No module named 'pkg_resources'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: pymediainfo
Source-Version: 2.3.0-1

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated pymediainfo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 05 Jun 2018 20:33:39 -0400
Source: pymediainfo
Binary: python-pymediainfo python3-pymediainfo pypy-pymediainfo 
python-pymediainfo-doc
Architecture: source
Version: 2.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Antoine Beaupré 
Description:
 pypy-pymediainfo - Library to fetch multimedia metadata information - PyPy 
version
 python-pymediainfo - Library to fetch multimedia metadata information - Python 
2.x
 python-pymediainfo-doc - documentation for the pymediainfo Python library
 python3-pymediainfo - Library to fetch multimedia metadata information - 
Python 3.x
Closes: 896313 896422 896831
Changes:
 pymediainfo (2.3.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Deprecating priority extra as per policy 4.0.1
 .
   [ Antoine Beaupré ]
   * fix copyright file to add original author
   * fix watch file
   * add missing libmediainfo depends (Closes: #896831)
   * new upstream release (Closes: #896422, #896313)
Checksums-Sha1:
 d5ff897b741105f945be3a3e0ff5103d7bd39b02 2028 pymediainfo_2.3.0-1.dsc
 3c8767cd4512984fc63862b7d8e4f9a69ebbb31b 424063 pymediainfo_2.3.0.orig.tar.gz
 75fea83fcf97dfd8fa2fa50e3e2a14c769617c5f 2452 pymediainfo_2.3.0-1.debian.tar.xz
 d4e7f5d5e1efd0974140f7ea5652ff5af11d507b 8103 
pymediainfo_2.3.0-1_amd64.buildinfo
Checksums-Sha256:
 debd622a823fa0ba1d95f3672171805bd73d081c02860b4efa661bdb6cce8fe9 2028 
pymediainfo_2.3.0-1.dsc
 bea5b9d09e1ba088493bb1ecff978abfcd7b669bbbe8ac78367e535835cb4d19 424063 
pymediainfo_2.3.0.orig.tar.gz
 7a8866600f64b86b53e4e18f46749c45d3fcdd092ceecb510d7ddb7a35d19f96 2452 
pymediainfo_2.3.0-1.debian.tar.xz
 4280187da1aa9809f3116ee1492f01654d0706f32abefe5e6e763484de65a583 8103 
pymediainfo_2.3.0-1_amd64.buildinfo
Files:
 b2d7135184a4952fcf64adc1fa35f24d 2028 python optional pymediainfo_2.3.0-1.dsc
 41bf711323b0a61b30b2ce5866ac6888 424063 python optional 
pymediainfo_2.3.0.orig.tar.gz
 48e99ce1fbca7373137159869dec34db 2452 python optional 
pymediainfo_2.3.0-1.debian.tar.xz
 0185425a614781006866ee3bf3fcdfd0 8103 python optional 
pymediainfo_2.3.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAlsXL6AACgkQPqHd3bJh
2XsaSQf/RqOTFLJyRPDlxGidd/ket2fA8Xbe5A53nTzMwM9OzeeUAEORvWrTYH/3

Bug#896313: marked as done (python-pymediainfo: pymediainfo fails to import)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 01:04:43 +
with message-id 
and subject line Bug#896313: fixed in pymediainfo 2.3.0-1
has caused the Debian Bug report #896313,
regarding python-pymediainfo: pymediainfo fails to import
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.)


-- 
896313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pymediainfo
Version: 2.2.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-pymediainfo importing the module pymediainfo
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/pymediainfo/__init__.py", line 6, in 

from pkg_resources import get_distribution
ImportError: No module named pkg_resources

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: pymediainfo
Source-Version: 2.3.0-1

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated pymediainfo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 05 Jun 2018 20:33:39 -0400
Source: pymediainfo
Binary: python-pymediainfo python3-pymediainfo pypy-pymediainfo 
python-pymediainfo-doc
Architecture: source
Version: 2.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Antoine Beaupré 
Description:
 pypy-pymediainfo - Library to fetch multimedia metadata information - PyPy 
version
 python-pymediainfo - Library to fetch multimedia metadata information - Python 
2.x
 python-pymediainfo-doc - documentation for the pymediainfo Python library
 python3-pymediainfo - Library to fetch multimedia metadata information - 
Python 3.x
Closes: 896313 896422 896831
Changes:
 pymediainfo (2.3.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Deprecating priority extra as per policy 4.0.1
 .
   [ Antoine Beaupré ]
   * fix copyright file to add original author
   * fix watch file
   * add missing libmediainfo depends (Closes: #896831)
   * new upstream release (Closes: #896422, #896313)
Checksums-Sha1:
 d5ff897b741105f945be3a3e0ff5103d7bd39b02 2028 pymediainfo_2.3.0-1.dsc
 3c8767cd4512984fc63862b7d8e4f9a69ebbb31b 424063 pymediainfo_2.3.0.orig.tar.gz
 75fea83fcf97dfd8fa2fa50e3e2a14c769617c5f 2452 pymediainfo_2.3.0-1.debian.tar.xz
 d4e7f5d5e1efd0974140f7ea5652ff5af11d507b 8103 
pymediainfo_2.3.0-1_amd64.buildinfo
Checksums-Sha256:
 debd622a823fa0ba1d95f3672171805bd73d081c02860b4efa661bdb6cce8fe9 2028 
pymediainfo_2.3.0-1.dsc
 bea5b9d09e1ba088493bb1ecff978abfcd7b669bbbe8ac78367e535835cb4d19 424063 
pymediainfo_2.3.0.orig.tar.gz
 7a8866600f64b86b53e4e18f46749c45d3fcdd092ceecb510d7ddb7a35d19f96 2452 
pymediainfo_2.3.0-1.debian.tar.xz
 4280187da1aa9809f3116ee1492f01654d0706f32abefe5e6e763484de65a583 8103 
pymediainfo_2.3.0-1_amd64.buildinfo
Files:
 b2d7135184a4952fcf64adc1fa35f24d 2028 python optional pymediainfo_2.3.0-1.dsc
 41bf711323b0a61b30b2ce5866ac6888 424063 python optional 
pymediainfo_2.3.0.orig.tar.gz
 48e99ce1fbca7373137159869dec34db 2452 python optional 
pymediainfo_2.3.0-1.debian.tar.xz
 0185425a614781006866ee3bf3fcdfd0 8103 python optional 
pymediainfo_2.3.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAlsXL6AACgkQPqHd3bJh
2XsaSQf/RqOTFLJyRPDlxGidd/ket2fA8Xbe5A53nTzMwM9OzeeUAEORvWrTYH/3
cIUAbHM7Ue

Bug#900629: debian-edu-install: breaks installation of samba

[Mike Gabriel]

Hi,

On  Di 05 Jun 2018 19:03:59 CEST, Holger Levsen wrote:


On Tue, Jun 05, 2018 at 01:06:52PM +0200, Wolfgang Schweer wrote:

> netbios name PROFITBRICKS-BUILD10-AMD64 is not a valid netbios name
> ERROR: Invalid smb.conf
> dpkg: error processing package samba-common-bin (--configure):
>  installed samba-common-bin package post-installation script subprocess
>  returned error exit status 255
IMO this bug should/could be fixed in jenkins.d.n by setting a valid
netbios name via $(hostname).


no.

installation must not fail just because the hostname is
profitbricks-build-amd64 or whatever.


IMHO, this is a samba bug...


For Debian Edu the netbios name is set to TJENER, but at the moment
samba-common-bin gets installed, the vanilla smb.conf is tested (plus
preseeded values w/ netbios name not preseedable), replaced with the
Debian Edu one later (via Cfengine). So there's nothing Debian Edu can
do to fix this bug (afaict).


we can shorten the netbios name if using the hostname for the netbios
name is problematic because its too long.


Please check the attached patch.


NACK, see above :)


I agree, but the fix needs to be in Samba.

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpDGmljt60Tt.pgp
Description: Digitale PGP-Signatur

Bug#900855: [qtquickcontrols2-opensource-src] FTBFS font fontenello

[Bastien ROUCARIÈS]

Package: qtquickcontrols2-opensource-src
Severity: serious

Hi,
examples/quickcontrols2/swipetoremove/fonts/fontello.ttf

fail to build from source

In your case I suppose they are no need to wait that I upload the package.

A repack will be quicker

Bastien





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

Bug#900853: [request-tracker4] FTBFS: missing fonts in ckeditor

[Bastien ROUCARIÈS]

Package: request-tracker4
Severity: serious

Hi,

third-party-source/devel/third-party/ckeditor-4.5.3/samples/toolbarconfigurator/font/fontello*

Does not build from source

Time to use ckeditor package ?

Will upload this font ASAP

Thanks

Bastien





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

Bug#900854: [bulk-media-downloader] FTBFS: missing source

[Bastien ROUCARIÈS]

Package: bulk-media-downloader
Severity: serious

Hi,

The file data/window/fontello.woff from fontello upstream does not build from 
source.

I plan to upload this fonts ASAP

Bastien

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

Bug#860650: marked as done (zookeeper: FTBFS on i386: java.io.FileNotFoundException: /home/user42/.ant/cache/resolved-org.apache.zookeeper-zookeeper-3.4.9-2.xml (No such file or directory))

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 22:04:56 +
with message-id 
and subject line Bug#860650: fixed in zookeeper 3.4.12-1
has caused the Debian Bug report #860650,
regarding zookeeper: FTBFS on i386: java.io.FileNotFoundException: 
/home/user42/.ant/cache/resolved-org.apache.zookeeper-zookeeper-3.4.9-2.xml (No 
such file or directory)
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.)


-- 
860650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zookeeper
Version: 3.4.9-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Run core Java test suite against zookeeper
> ant -Dversion=3.4.9-2 -DlastRevision=-1 test-core-java
> Buildfile: /<>/build.xml
> 
> init:
> 
> ivy-download:
>   [get] Getting: 
> http://repo2.maven.org/maven2/org/apache/ivy/ivy/2.4.0/ivy-2.4.0.jar
>   [get] To: /<>/src/java/lib/ivy-2.4.0.jar
> 
> ivy-taskdef:
> 
> ivy-init:
> 
> ivy-retrieve:
> [ivy:retrieve] :: Apache Ivy 2.4.0 - 20141213170938 :: 
> http://ant.apache.org/ivy/ ::
> [ivy:retrieve] :: loading settings :: file = /<>/ivysettings.xml
> [ivy:retrieve] :: resolving dependencies :: 
> org.apache.zookeeper#zookeeper;3.4.9-2
> [ivy:retrieve]confs: [default]
> 
> BUILD FAILED
> /<>/build.xml:364: impossible to resolve dependencies:
>   java.io.FileNotFoundException: 
> /home/user42/.ant/cache/resolved-org.apache.zookeeper-zookeeper-3.4.9-2.xml 
> (No such file or directory)
>   at java.io.FileOutputStream.open0(Native Method)
>   at java.io.FileOutputStream.open(FileOutputStream.java:270)
>   at java.io.FileOutputStream.(FileOutputStream.java:213)
>   at java.io.FileOutputStream.(FileOutputStream.java:162)
>   at 
> org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorUpdater.update(XmlModuleDescriptorUpdater.java:135)
>   at 
> org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorParser.toIvyFile(XmlModuleDescriptorParser.java:160)
>   at 
> org.apache.ivy.core.module.descriptor.DefaultModuleDescriptor.toIvyFile(DefaultModuleDescriptor.java:561)
>   at 
> org.apache.ivy.core.cache.DefaultResolutionCacheManager.saveResolvedModuleDescriptor(DefaultResolutionCacheManager.java:176)
>   at 
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:245)
>   at 
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:197)
>   at org.apache.ivy.Ivy.resolve(Ivy.java:508)
>   at org.apache.ivy.ant.IvyResolve.doExecute(IvyResolve.java:330)
>   at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:271)
>   at 
> org.apache.ivy.ant.IvyPostResolveTask.ensureResolved(IvyPostResolveTask.java:228)
>   at 
> org.apache.ivy.ant.IvyPostResolveTask.prepareAndCheck(IvyPostResolveTask.java:179)
>   at org.apache.ivy.ant.IvyRetrieve.doExecute(IvyRetrieve.java:88)
>   at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:271)
>   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
>   at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>   at org.apache.tools.ant.Task.perform(Task.java:348)
>   at org.apache.tools.ant.Target.execute(Target.java:435)
>   at org.apache.tools.ant.Target.performTasks(Target.java:456)
>   at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
>   at org.apache.tools.ant.Project.executeTarget(Project.java:1376)
>   at 
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>   at org.apache.tools.ant.Project.executeTargets(Project.java:1260)
>   at org.apache.tools.ant.Main.runBuild(Main.java:857)
>   at org.apache.tools.ant.Main.startAnt(Main.java:236)
>   at org.apache.tools.ant.launch.Launcher.run(Launcher.java:287)
>   at org.apache.tools.ant.launch.Launcher.main(Launcher.java:113)
> 
> Total time: 7 seconds
> debian/rules:90: recipe for target 'override_dh_auto_test-indep' failed
> make[1]: *** [override_dh_auto_test-indep] Error 1

The full build log is available fro

Bug#900852: [icingaweb2] FTBFS: font fontello-ifont

[Bastien ROUCARIÈS]

Package: icingaweb2
Severity: serious

I could not found the source for 
public/font/*

I plan to upload this fonts soon, but you must repack 

Bastien

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

Processed: Bug #860650 in zookeeper marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #860650 [src:zookeeper] zookeeper: FTBFS on i386:   
java.io.FileNotFoundException: 
/home/user42/.ant/cache/resolved-org.apache.zookeeper-zookeeper-3.4.9-2.xml (No 
such file or directory)
Added tag(s) pending.

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

Bug#860650: Bug #860650 in zookeeper marked as pending

[ebourg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/zookeeper/commit/7e06a3a108280a463ce77324de80868ca1b1b500


Ensure the unit tests are run in offline mode (Closes: #860650)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/860650

Bug#898943: Multiple vulnerabiliities in Mongoose

[Moritz Mühlenhoff]

On Mon, Jun 04, 2018 at 12:47:48PM -0400, Reinhard Tartler wrote:
> Ok, thanks. That sounds like a good plan!

BTW, I'm not sure if Talos security actually reported these to the
censenta/mongoose upstream project or whether they're doing it
for the security buzz/advertising factor...

I saw that upstream seem to be fairly active, so maybe it's just
a matter of properly reporting these vulnerabilities on their
Github page, letting them fix them and then rebasing the mongoose
copy to the fixed version?

Cheers,
Moritz

Bug#900848: Should this package be removed?

[Moritz Muehlenhoff]

Package: skipfish
Severity: serious

Should this package be removed?
- Dead upstream (last upstream commits from 2012)
- Unmaintained (last maintainer upload in 2012)
- RC-buggy (broken with OpenSSL 1.1)
- Marginal popcon numbers

If there's no objections, I'll reassign this bug to ftp.debian.org
for removal in a few weeks.

Cheers,
Moritz

Bug#851085: conserver: FTBFS with openssl 1.1.0

[Moritz Muehlenhoff]

On Sun, Jun 26, 2016 at 12:21:20PM +0200, Kurt Roeckx wrote:
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build. 

This has now been fixed in version 8.2.2:
https://github.com/conserver/conserver/commit/258c2e124135257dcc6128b629b4ad157841c81c

Cheers,
Moritz

Bug#859548: pam-ssh-agent-auth: Please migrate to openssl1.1 in buster

[Moritz Muehlenhoff]

On Thu, Oct 12, 2017 at 11:44:35PM +0200, Sebastian Andrzej Siewior wrote:
> Hi,
> 
> this is a remainder about the openssl transition [0]. We really want to
> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> of this bug to serious in a month. Please react before that happens.

Christian/Balint,
pam_ssh_agent_auth seems dead upstream, the last commits are from March
2014, is anyone of you working on a patch for this or should we rather
remove it from the archive?

Cheers,
Moritz

Bug#897573: You need to install the extra package

[Daniel Kobras]

Hi Mark!

On Mon, Jun 04, 2018 at 10:43:11AM +0100, Mark Brown wrote:
> On Mon, May 07, 2018 at 03:01:23PM +0200, Bastien ROUCARIES wrote: 
> > It is a feature you need to depends on extra package
> 
> It would have been rather more helpful if you were to mention which
> package this is.  It would also have been helpful to have made some
> effort to communicate this change to packages that build depend on yours
> when making the change rather than just letting them break with zero
> communication.

As far as I can tell, this seems to be a duplicate of #879849 (the
libmagickcore...-extra packages lack a dependency on librsvg2-bin),
ie. a bug rather than an intentional change. (The build error occured
despite usbview already build-depending on ...-extra.)

Kind regards,

Daniel 

Bug#896403: marked as done (python-fake-factory: faker fails to import)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 20:48:35 +
with message-id 
and subject line Bug#896403: fixed in faker 0.7.7-2.1
has caused the Debian Bug report #896403,
regarding python-fake-factory: faker fails to import
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.)


-- 
896403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-fake-factory
Version: 0.7.7-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-fake-factory importing the module faker
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/faker/__init__.py", line 4, in 
from faker.factory import Factory
  File "/usr/lib/python2.7/dist-packages/faker/factory.py", line 10, in 
from faker.config import DEFAULT_LOCALE, PROVIDERS, AVAILABLE_LOCALES
  File "/usr/lib/python2.7/dist-packages/faker/config.py", line 13, in 
AVAILABLE_LOCALES = find_available_locales(PROVIDERS)
  File "/usr/lib/python2.7/dist-packages/faker/utils/loading.py", line 19, in 
find_available_locales
provider_module = import_module(provider_path)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/usr/lib/python2.7/dist-packages/faker/providers/internet/__init__.py", 
line 5, in 
from ipaddress import ip_address, ip_network, IPV4LENGTH, IPV6LENGTH
ImportError: No module named ipaddress

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: faker
Source-Version: 0.7.7-2.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated faker 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, 03 Jun 2018 23:17:06 +0300
Source: faker
Binary: python-fake-factory python3-fake-factory faker
Architecture: source
Version: 0.7.7-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Adrian Bunk 
Description:
 faker  - Python program that generates fake data
 python-fake-factory - Faker is a Python library that generates fake data 
(Python 2)
 python3-fake-factory - Faker is a Python library that generates fake data 
(Python 3)
Closes: 896403
Changes:
 faker (0.7.7-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * python-fake-factory: Add the missing dependency
 on python-ipaddress. (Closes: #896403)
Checksums-Sha1:
 628c563ffe423c143dd7c62226b5c3cf53c925ad 2264 faker_0.7.7-2.1.dsc
 20f283c810ba7bf08b868b6c2591208c09f15dec 3616 faker_0.7.7-2.1.debian.tar.xz
Checksums-Sha256:
 d9444df199f2f01fc31bc49bb1617ae24467899a0cc381576a9dc596111c71ee 2264 
faker_0.7.7-2.1.dsc
 de2f93674a2706286e1f00761da3a872b8ae93c4d2fa5311102cfe888ddd6494 3616 
faker_0.7.7-2.1.debian.tar.xz
Files:
 875c6742b20878f56be9e09041d313c3 2264 python optional faker_0.7.7-2.1.dsc
 eec77eccbbabd6d26d7317c9ba7ee2c8 3616 python optional 
faker_0.7.7-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlsUTbsACgkQiNJCh6LY
mLHUkRAAu6LFqmlqQ1Btv5VSxSNImAQx3f6KoLcs9ZI9szjHowIINLmLxQYz4KOo
d5crq0wJTkcvEMiPPv22ZqWOt4YfffglDFgW7/EGi667wVc3XmrWz15Kq+INALHs
R/zUi+xqa9uOxxRCyaM3TgMW95C86lhtGHVmYpHDikT9Qg3k5HFtw8ccYxBXhM/C
+L/F9Z8ufR0uGITIrYj9YCAungB65LlZTlOxbuPbtUz3dp0WEMMyinVhvZmpqoYr
q3fahRRXMY5W3Zh9bSLH8Wcip3Q8UdblnFLFbKz68Oirt399nE+L0NP/7eSTUWgC
Z2YaGDFjIZ4vl6sEsYCl9mCaxIYV2FeKNqS6vQLbcEuJwZEo+M8FDWnb6WMX3s4E
kmmmlzMajTzNVd0Qe8eevW6I3nfG73w+loFWJIMw+L19

Bug#866857: marked as done (golang-github-docker-goamz FTBFS: FAIL: multi_test.go:262: S.TestPutAllZeroSizeFile)

[Debian Bug Tracking System]

Your message dated Tue, 5 Jun 2018 22:43:35 +0200
with message-id <20180605204335.6jq4dwywqqp7z...@fatal.se>
and subject line Re: golang-github-docker-goamz FTBFS: FAIL: multi_test.go:262: 
S.TestPutAllZeroSizeFile
has caused the Debian Bug report #866857,
regarding golang-github-docker-goamz FTBFS: FAIL: multi_test.go:262: 
S.TestPutAllZeroSizeFile
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.)


-- 
866857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-docker-goamz
Version: 0.0~git20160206.0.f0a21f5-1
Severity: serious

Some recent change in unstable makes golang-github-docker-goamz FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-docker-goamz.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-docker-goamz.html

...
FAIL: multi_test.go:262: S.TestPutAllZeroSizeFile

multi_test.go:295:
c.Assert(req.Header["Content-Length"], check.DeepEquals, []string{"0"})
... obtained []string = []string(nil)
... expected []string = []string{"0"}

OOPS: 60 passed, 29 skipped, 1 FAILED
--- FAIL: Test (60.55s)
FAIL
exit status 1
FAILgithub.com/docker/goamz/s3  60.584s
?   github.com/docker/goamz/s3/s3test   [no test files]
=== RUN   Test
OK: 28 passed
--- PASS: Test (0.07s)
PASS
ok  github.com/docker/goamz/sns 0.079s
=== RUN   Test
done

&{Method:POST URL:/ Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 
Header:map[Authorization:[AWS4-HMAC-SHA256 
Credential=abc/20170702//sqs/aws4_request, 
SignedHeaders=content-type;host;x-amz-date, 
Signature=ddeb7d81b9abfd17a209c2433faf682ae363a44bc24748021f9ed06f069bcdd0] 
Content-Type:[application/x-www-form-urlencoded] X-Amz-Date:[20170702T080302Z] 
Accept-Encoding:[gzip] User-Agent:[Go-http-client/1.1] Content-Length:[113]] 
Body:0xc420144dc0 GetBody: ContentLength:113 TransferEncoding:[] 
Close:false Host:localhost:4455 Form:map[Attribute.1.Name:[VisibilityTimeout] 
Attribute.1.Value:[30] QueueName:[testQueue] Version:[2012-11-05] 
Action:[CreateQueue]] PostForm:map[Action:[CreateQueue] 
Attribute.1.Name:[VisibilityTimeout] Attribute.1.Value:[30] 
QueueName:[testQueue] Version:[2012-11-05]] MultipartForm: Trailer:map[] 
RemoteAddr:127.0.0.1:44238 RequestURI:/ TLS: Cancel: Response: 
ctx:0xc420144e00}
OK: 16 passed
--- PASS: Test (0.09s)
PASS
ok  github.com/docker/goamz/sqs 0.104s
=== RUN   Test
OK: 3 passed
--- PASS: Test (0.08s)
PASS
ok  github.com/docker/goamz/sts 0.100s
?   github.com/docker/goamz/testutil[no test files]
dh_auto_test: go test -v -p 1 github.com/docker/goamz/autoscaling 
github.com/docker/goamz/autoscaling/astest github.com/docker/goamz/aws 
github.com/docker/goamz/cloudfront github.com/docker/goamz/dynamodb 
github.com/docker/goamz/dynamodb/dynamizer github.com/docker/goamz/ec2 
github.com/docker/goamz/ec2/ec2test github.com/docker/goamz/ecommerce 
github.com/docker/goamz/elasticache github.com/docker/goamz/elb 
github.com/docker/goamz/elb/elbtest github.com/docker/goamz/exp/mturk 
github.com/docker/goamz/exp/sdb github.com/docker/goamz/exp/ses 
github.com/docker/goamz/iam github.com/docker/goamz/iam/iamtest 
github.com/docker/goamz/kinesis github.com/docker/goamz/kms 
github.com/docker/goamz/rds github.com/docker/goamz/route53 
github.com/docker/goamz/s3 github.com/docker/goamz/s3/s3test 
github.com/docker/goamz/sns github.com/docker/goamz/sqs 
github.com/docker/goamz/sts github.com/docker/goamz/testutil returned exit code 
1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1
--- End Message ---
--- Begin Message ---
On Sun, Jul 02, 2017 at 11:48:56AM +0300, Adrian Bunk wrote:
> Source: golang-github-docker-goamz
> Version: 0.0~git20160206.0.f0a21f5-1
> Severity: serious
> 
> Some recent change in unstable makes golang-github-docker-goamz FTBFS:

Builds just fine for me, and ...

> 
> https://tests.reproducible-builds.org/debian/history/golang-github-docker-goamz.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-docker-goamz.html
[...]

... while I can't really make any sense of the information on these
pages they also seems to indicate the weather has improved.

I guess the "Some recent change in unstable" was just buggy and has
since been fixed.

Regards,
Andreas Henriksson--- End Message ---

Bug#841575: marked as done (docker-registry: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Tue, 5 Jun 2018 22:38:20 +0200
with message-id <20180605203820.fdyorfdnmibuh...@fatal.se>
and subject line Re: [pkg-go] Bug#841575: docker-registry: FTBFS: Tests failures
has caused the Debian Bug report #841575,
regarding docker-registry: FTBFS: Test failures
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.)


-- 
841575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: docker-registry
Version: 2.4.1~ds1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> PASS
> okgithub.com/docker/distribution/registry/storage/driver/swift38.958s
> ? github.com/docker/distribution/registry/storage/driver/testsuites   
> [no test files]
> ? github.com/docker/distribution/testutil [no test files]
> === RUN   TestUUID4Generation
> --- PASS: TestUUID4Generation (0.00s)
> === RUN   TestParseAndEquality
> --- PASS: TestParseAndEquality (0.01s)
> PASS
> okgithub.com/docker/distribution/uuid 0.011s
> ? 
> github.com/docker/distribution/vendor/github.com/Azure/azure-sdk-for-go/storage
>  [no test files]
> ? github.com/docker/distribution/vendor/github.com/docker/goamz/aws   
> [no test files]
> ? github.com/docker/distribution/vendor/github.com/docker/goamz/s3
> [no test files]
> ? github.com/docker/distribution/version  [no test files]
> dh_auto_test: go test -v -p 1 -test.short github.com/docker/distribution 
> github.com/docker/distribution/cmd/digest 
> github.com/docker/distribution/cmd/registry 
> github.com/docker/distribution/cmd/registry-api-descriptor-template 
> github.com/docker/distribution/configuration 
> github.com/docker/distribution/context 
> github.com/docker/distribution/contrib/token-server 
> github.com/docker/distribution/digest github.com/docker/distribution/health 
> github.com/docker/distribution/health/api 
> github.com/docker/distribution/manifest 
> github.com/docker/distribution/manifest/manifestlist 
> github.com/docker/distribution/manifest/schema1 
> github.com/docker/distribution/manifest/schema2 
> github.com/docker/distribution/notifications 
> github.com/docker/distribution/reference 
> github.com/docker/distribution/registry 
> github.com/docker/distribution/registry/api/errcode 
> github.com/docker/distribution/registry/api/v2 
> github.com/docker/distribution/registry/auth 
> github.com/docker/distribution/registry/auth/htpasswd 
> github.com/docker/distribution/registry/auth/silly 
> github.com/docker/distribution/registry/auth/token 
> github.com/docker/distribution/registry/client 
> github.com/docker/distribution/registry/client/auth 
> github.com/docker/distribution/registry/client/transport 
> github.com/docker/distribution/registry/listener 
> github.com/docker/distribution/registry/middleware/registry 
> github.com/docker/distribution/registry/middleware/repository 
> github.com/docker/distribution/registry/proxy 
> github.com/docker/distribution/registry/proxy/scheduler 
> github.com/docker/distribution/registry/storage 
> github.com/docker/distribution/registry/storage/cache 
> github.com/docker/distribution/registry/storage/cache/cachecheck 
> github.com/docker/distribution/registry/storage/cache/memory 
> github.com/docker/distribution/registry/storage/cache/redis 
> github.com/docker/distribution/registry/storage/driver 
> github.com/docker/distribution/registry/storage/driver/azure 
> github.com/docker/distribution/registry/storage/driver/base 
> github.com/docker/distribution/registry/storage/driver/factory 
> github.com/docker/distribution/registry/storage/driver/filesystem 
> github.com/docker/distribution/registry/storage/driver/gcs 
> github.com/docker/distribution/registry/storage/driver/inmemory 
> github.com/docker/distribution/registry/storage/driver/middleware 
> github.com/docker/distribution/registry/storage/driver/middleware/cloudfront 
> github.com/docker/distribution/registry/storage/driver/oss 
> github.com/docker/distribution/registry/storage/driver/s3-aws 
> github.com/docker/distribution/registry/storage/driver/s3-goamz 
> github.com/docker/distribution/registry/storage/driver/swift 
> github.com/docker/distribution/registry/storage/driver/testsuites 
> github.com/docker/distribution/testutil github.com/docker/distribution/uuid 
> github.com/docker/distribution/vendor/github.com/Azure/azure-sdk-for-go/storage

Bug#855942: anki: don't let the alpha version migrate to testing

[Alexandre Viau]

Do we really want to let upstream decide whether or not we should ship Anki?

The program works. It isn't really security critical so even if it has a
few bugs it can be useful to our users.

Cheers,

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



signature.asc
Description: OpenPGP digital signature

Processed: tagging 900375

[Debian Bug Tracking System]

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

> tags 900375 + sid buster
Bug #900375 [hg-fast-export] hg-fast-export: Incompatible with mercurial 4.6
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#900843: bouncycastle: CVE-2018-1000180

[Salvatore Bonaccorso]

Source: bouncycastle
Version: 1.54-1
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://www.bouncycastle.org/jira/browse/BJA-694

Hi,

The following vulnerability was published for bouncycastle.

CVE-2018-1000180[0]:
| Bouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier
| have a flaw in the Low-level interface to RSA key pair generator,
| specifically RSA Key Pairs generated in low-level API with added
| certainty may have less M-R tests than expected. This appears to be
| fixed in versions BC 1.60 beta 4 and later, BC-FJA 1.0.2 and later.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-1000180
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000180
[1] https://www.bouncycastle.org/jira/browse/BJA-694

Regards,
Salvatore

Processed: severity of 900375 is grave

[Debian Bug Tracking System]

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

> severity 900375 grave
Bug #900375 [hg-fast-export] hg-fast-export: Incompatible with mercurial 4.6
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#896207: marked as done (python-scruffy: scruffy fails to import)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 19:35:37 +
with message-id 
and subject line Bug#896207: fixed in python-scruffy 0.3.3-1.1
has caused the Debian Bug report #896207,
regarding python-scruffy: scruffy fails to import
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.)


-- 
896207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-scruffy
Version: 0.3.3-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-scruffy importing the module scruffy
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/scruffy/__init__.py", line 1, in 

from .env import Environment
  File "/usr/lib/python2.7/dist-packages/scruffy/env.py", line 8, in 
from .file import Directory
  File "/usr/lib/python2.7/dist-packages/scruffy/file.py", line 7, in 
import pkg_resources
ImportError: No module named pkg_resources

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-scruffy
Source-Version: 0.3.3-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated python-scruffy 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, 03 Jun 2018 21:53:39 +0300
Source: python-scruffy
Binary: python-scruffy python3-scruffy
Architecture: source
Version: 0.3.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Adrian Bunk 
Description:
 python-scruffy - framework for taking care of a bunch of boilerplate in 
Python2 ap
 python3-scruffy - framework for taking care of a bunch of boilerplate in 
Python3 ap
Closes: 896207 896374
Changes:
 python-scruffy (0.3.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add the missing dependencies on python{,3}-pkg-resources.
 (Closes: #896207, #896374)
Checksums-Sha1:
 0d606ede906fb0b5ffaa4d54916ce90d71fd41ea 2219 python-scruffy_0.3.3-1.1.dsc
 a5dc78cd67d5ad989942a78be2d69d454d3f8518 2452 
python-scruffy_0.3.3-1.1.debian.tar.xz
Checksums-Sha256:
 baad0a730de3f9b38a8de933df9ab9c265f8d4f190e8fba3d62744a2d4ba66c6 2219 
python-scruffy_0.3.3-1.1.dsc
 5eae585ba0578c2d5c0caa4095b7bdc18074c9908d642a51ec284cbdc5ef6a83 2452 
python-scruffy_0.3.3-1.1.debian.tar.xz
Files:
 131749dfeb3253957aeff2e31687133b 2219 python optional 
python-scruffy_0.3.3-1.1.dsc
 06bfdf92a02a4044391a56d47827b1e2 2452 python optional 
python-scruffy_0.3.3-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlsUOpgACgkQiNJCh6LY
mLHdMQ//cpCpZtmjLEpMcWOV2coMV7begWc8Zw3nvicTMZZNAalepcYjTTXcit4U
b5aM1hvutDiOQWSkyZ53WC7YWAPqyKvUxbtsBhAWsZ310t3/nEWhwi19e9iHJVdK
DkW3OkkYWEQ0ult5CdfHPtPnm+f++vbkJMfylJSnhJioFGOsoUy2t32unOar7wrc
8T1vDBeoXDAaWQIPvZbdLXSw7qs/9HGjHWFSqk/eyF30QdSHh6ANRLDyBczsQhM+
REjs+KMHGPsQm9608jk5F64y4Uw8wLiIgVaB28YFSs5bZJq5YwRQmEwYb2MUMb4Y
KV33S02hzciBW78LpI+FxseD4SCdvAOkE6dPnPp3EzTaTqFmAK5gcUK6qQSdCmHU
C3sIIkLF6Vwm9LFEdx0mRKDfPMO595Y7PT33sqSOprGtqvnWxqWqo4EUFVy1d7GG
CsUKuC3EZJC14gPUw0hj1NlrakXTUOPTV9/5Xh0JlKNzlHJK65ioK4kyaZe7qL5U
tvsREO5eHORo006W9cEDyav302ksPBWUZCGPczNDpi3yVu6vnpmoQA3HxnZCMaAI
g8VYLIaq8BpVkLQaTXpoFtbXQCUTeIGstDppUUjRC2NJ4lqdXMaBs2429llowcss
hjtXQvJomAlyVxwFZKwKi1JneYWBFzRnMuCJuh8/RSWbv1f3zc8=
=7Lb6
-END PGP SIGNATURE End Message ---

Bug#896374: marked as done (python3-scruffy: scruffy fails to import)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 19:35:38 +
with message-id 
and subject line Bug#896374: fixed in python-scruffy 0.3.3-1.1
has caused the Debian Bug report #896374,
regarding python3-scruffy: scruffy fails to import
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.)


-- 
896374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-scruffy
Version: 0.3.3-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-scruffy importing the module scruffy
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/scruffy/__init__.py", line 1, in 
from .env import Environment
  File "/usr/lib/python3/dist-packages/scruffy/env.py", line 8, in 
from .file import Directory
  File "/usr/lib/python3/dist-packages/scruffy/file.py", line 7, in 
import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-scruffy
Source-Version: 0.3.3-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated python-scruffy 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, 03 Jun 2018 21:53:39 +0300
Source: python-scruffy
Binary: python-scruffy python3-scruffy
Architecture: source
Version: 0.3.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Adrian Bunk 
Description:
 python-scruffy - framework for taking care of a bunch of boilerplate in 
Python2 ap
 python3-scruffy - framework for taking care of a bunch of boilerplate in 
Python3 ap
Closes: 896207 896374
Changes:
 python-scruffy (0.3.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add the missing dependencies on python{,3}-pkg-resources.
 (Closes: #896207, #896374)
Checksums-Sha1:
 0d606ede906fb0b5ffaa4d54916ce90d71fd41ea 2219 python-scruffy_0.3.3-1.1.dsc
 a5dc78cd67d5ad989942a78be2d69d454d3f8518 2452 
python-scruffy_0.3.3-1.1.debian.tar.xz
Checksums-Sha256:
 baad0a730de3f9b38a8de933df9ab9c265f8d4f190e8fba3d62744a2d4ba66c6 2219 
python-scruffy_0.3.3-1.1.dsc
 5eae585ba0578c2d5c0caa4095b7bdc18074c9908d642a51ec284cbdc5ef6a83 2452 
python-scruffy_0.3.3-1.1.debian.tar.xz
Files:
 131749dfeb3253957aeff2e31687133b 2219 python optional 
python-scruffy_0.3.3-1.1.dsc
 06bfdf92a02a4044391a56d47827b1e2 2452 python optional 
python-scruffy_0.3.3-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlsUOpgACgkQiNJCh6LY
mLHdMQ//cpCpZtmjLEpMcWOV2coMV7begWc8Zw3nvicTMZZNAalepcYjTTXcit4U
b5aM1hvutDiOQWSkyZ53WC7YWAPqyKvUxbtsBhAWsZ310t3/nEWhwi19e9iHJVdK
DkW3OkkYWEQ0ult5CdfHPtPnm+f++vbkJMfylJSnhJioFGOsoUy2t32unOar7wrc
8T1vDBeoXDAaWQIPvZbdLXSw7qs/9HGjHWFSqk/eyF30QdSHh6ANRLDyBczsQhM+
REjs+KMHGPsQm9608jk5F64y4Uw8wLiIgVaB28YFSs5bZJq5YwRQmEwYb2MUMb4Y
KV33S02hzciBW78LpI+FxseD4SCdvAOkE6dPnPp3EzTaTqFmAK5gcUK6qQSdCmHU
C3sIIkLF6Vwm9LFEdx0mRKDfPMO595Y7PT33sqSOprGtqvnWxqWqo4EUFVy1d7GG
CsUKuC3EZJC14gPUw0hj1NlrakXTUOPTV9/5Xh0JlKNzlHJK65ioK4kyaZe7qL5U
tvsREO5eHORo006W9cEDyav302ksPBWUZCGPczNDpi3yVu6vnpmoQA3HxnZCMaAI
g8VYLIaq8BpVkLQaTXpoFtbXQCUTeIGstDppUUjRC2NJ4lqdXMaBs2429llowcss
hjtXQvJomAlyVxwFZKwKi1JneYWBFzRnMuCJuh8/RSWbv1f3zc8=
=7Lb6
-END PGP SIGNATURE End Message ---

Processed: severity of 900840 is normal

[Debian Bug Tracking System]

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

> severity 900840 normal
Bug #900840 [thunderbird] thunderbird: does not start with apparmor errors and 
breaks X session
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#900840: thunderbird: does not start with apparmor errors and breaks X session

[Hannes Hörl]

Package: thunderbird
Version: 1:60.0~b6-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

thunderbird cannot be started anymore and breaks X. X does not update
the screen anymore, the cursor can still be moved and shows on the
screen while nothing can be clicked on or interacted with. Application
which e.g. play sound seem to still continue running, but cannot be
controlled fia the GUI anymore. The X-server needs to be completely
restarted to fix the issue.

With the last tested version (1:60.0~b6-1 from experimentsl) I see the
following in the syslog:

Jun  5 19:02:19 pfah kernel: [22845.000634] audit: type=1400 
audit(1528221739.361:49): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="thunderbird" pid=2979 comm="apparmor_parser"
Jun  5 19:02:19 pfah kernel: [22845.015315] audit: type=1400 
audit(1528221739.377:50): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="thunderbird//browser_java" pid=2979 
comm="apparmor_parser"
Jun  5 19:02:19 pfah kernel: [22845.016056] audit: type=1400 
audit(1528221739.377:51): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="thunderbird//browser_openjdk" pid=2979 
comm="apparmor_parser"
Jun  5 19:02:19 pfah kernel: [22845.016668] audit: type=1400 
audit(1528221739.377:52): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="thunderbird//gpg" pid=2979 comm="apparmor_parser"
Jun  5 19:02:19 pfah kernel: [22845.016920] audit: type=1400 
audit(1528221739.377:53): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="thunderbird//sanitized_helper" pid=2979 
comm="apparmor_parser"
Jun  5 19:04:27 pfah kernel: [22972.942931] audit: type=1400 
audit(1528221867.305:54): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=13506 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
Jun  5 19:04:27 pfah kernel: [22972.943282] audit: type=1400 
audit(1528221867.305:55): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=13506 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
Jun  5 19:04:27 pfah kernel: [22972.943288] audit: type=1400 
audit(1528221867.305:56): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=13506 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
Jun  5 19:04:27 pfah kernel: [22972.943292] audit: type=1400 
audit(1528221867.305:57): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=13506 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
Jun  5 19:04:27 pfah kernel: [22972.947864] audit: type=1400 
audit(1528221867.309:58): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=13506 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
Jun  5 19:04:27 pfah kernel: [22972.948154] audit: type=1400 
audit(1528221867.309:59): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=13506 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0


With the forner version I had (1:52.8.0-1 from sid) I see this in the
syslog:

Jun  5 18:33:38 pfah kernel: [21124.071163] audit: type=1400 
audit(1528220018.432:43): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=12543 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
Jun  5 18:33:38 pfah kernel: [21124.071195] audit: type=1400 
audit(1528220018.432:44): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=12543 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
Jun  5 18:33:38 pfah kernel: [21124.071268] audit: type=1400 
audit(1528220018.432:45): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=12543 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
Jun  5 18:33:38 pfah kernel: [21124.071312] audit: type=1400 
audit(1528220018.432:46): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=12543 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
Jun  5 18:33:38 pfah kernel: [21124.073642] audit: type=1400 
audit(1528220018.432:47): apparmor="DENIED" operation="open" 
profile="thunderbird" name="/sys/devices/pci:00/:00:02.0/vendor" 
pid=12543 comm="thunderbird" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
Jun  5 18:33:38 pfah kernel: [21124.073676] audit: type=1400 
audit(1528220018.432:48): apparmor="DENIED" operation="open" 
profile="thu

Bug#892508: marked as done (ruby-psych FTBFS with Ruby 2.5)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 19:05:38 +
with message-id 
and subject line Bug#892508: fixed in ruby-psych 3.0.3~pre1-1
has caused the Debian Bug report #892508,
regarding ruby-psych FTBFS with Ruby 2.5
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.)


-- 
892508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-psych
Version: 2.2.4-6
Severity: serious

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

...
   dh_auto_configure -O--buildsystem=ruby
dh_ruby --configure
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/build/1st/ruby-psych-2.2.4'
jruby -S rake compile
/usr/lib/ruby/vendor_ruby/psych.rb:6: warning: already initialized constant 
SNAKEYAML_VERSION
/usr/lib/ruby/vendor_ruby/psych.rb:6: warning: already initialized constant ANY
/usr/lib/ruby/vendor_ruby/psych.rb:6: warning: already initialized constant UTF8
/usr/lib/ruby/vendor_ruby/psych.rb:6: warning: already initialized constant 
UTF16LE
/usr/lib/ruby/vendor_ruby/psych.rb:6: warning: already initialized constant 
UTF16BE
/usr/share/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:59:in 
`require':
It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.
rake aborted!
LoadError: load error: psych -- java.lang.NoClassDefFoundError: Could not 
initialize class org.jruby.ext.psych.PsychEmitter
/build/1st/ruby-psych-2.2.4/Rakefile:1:in `(root)'
/build/1st/ruby-psych-2.2.4/Rakefile:13:in `block in (root)'
(See full trace by running task with --trace)
make[1]: *** [debian/rules:9: override_dh_auto_build-indep] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-psych
Source-Version: 3.0.3~pre1-1

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

Debian distribution maintenance software
pp.
Miguel Landaeta  (supplier of updated ruby-psych package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Jun 2018 18:50:08 +0100
Source: ruby-psych
Binary: ruby-psych libpsych-java
Architecture: source all amd64
Version: 3.0.3~pre1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Miguel Landaeta 
Description:
 libpsych-java - ruby-psych Java extension
 ruby-psych - libyaml wrapper for Ruby
Closes: 892508 900516
Changes:
 ruby-psych (3.0.3~pre1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #892508, #900516).
   * Refresh patches.
   * Bump DH compat level to 11.
   * Add versioned B-D on libyaml-snake-java (>= 1.21~).
   * Bump Standards-Version to 4.1.4. No changes were required.
   * Migrate Vcs-* URLs to salsa.d.o.
   * Update copyright info.
   * Update d/watch.
Checksums-Sha1:
 1ba18ba9c5d8caf046f08a0c15d003b074098de1 2227 ruby-psych_3.0.3~pre1-1.dsc
 823d964cb3b534aff8844de5cf53e8c8ebe8ac4f 133707 
ruby-psych_3.0.3~pre1.orig.tar.gz
 bff1b5f1a59d838bd7455ac67b8a8827f5f761db 8628 
ruby-psych_3.0.3~pre1-1.debian.tar.xz
 41a13f873f0749b4c4bdfae1bcb79445e2f78c6e 25824 
libpsych-java_3.0.3~pre1-1_all.deb
 a39166f3399724a29b26af4c20e3be2415c7b3ae 37180 
ruby-psych-dbgsym_3.0.3~pre1-1_amd64.deb
 246c464d5d6ba832a9cd93c3319504b750c2ff16 13632 
ruby-psych_3.0.3~pre1-1_amd64.buildinfo
 e2378cab84a322ddb43ccacebf8fcbff87527ce8 43748 
ruby-psych_3.0.3~pre1-1_amd64.deb
Checksums-Sha256:
 f5592cf0f9091a1461226b2f38683227ab324b42fbc896aa5d47bc47936a806b 2227 
ruby-psych_3.0.3~pre1-1.dsc
 d5faf6b6d70fc04193d700f3ee3dbf78a33d74519b919cf9be9ca5a3d53b38ff 133707 
ruby-psych_3.0.3~pre1.orig.tar.gz
 87afbb82abec6821659255921787eb7a616c21d7eff586d06906c89e9e4bbbad 8628 
ruby-psych_3.0.3~pre1-1.debian.tar.xz
 e9cde86bce87d6e5121e1f38aab14c220ae5c8b144e2bbb5a89450b822b7ea87 25824 
libpsych-java_3.0.3~pre1-1_all.deb
 f648330a4a3003e335ff9a86aa6deb00516301f0fb9065ba955eb4ae727f7ccc 37180 
ruby-psych-dbgsym_3.0.3~pre1-1_amd64.deb
 24bfaaa1e009856932c0e815fbd020466bad4827f

Bug#900756: [Rd] Byte-compilation failure on different architectures / low-memory systems

[Dirk Eddelbuettel]

On 4 June 2018 at 20:06, Tomas Kalibera wrote:
| thanks for the report. Access to the test system is not necessary, the 
| memory requirements of the byte-code compiler are usually 
| platform-independent and specifically with this package I can reproduce 
| they are very high. We'll have a look what we can do, certainly there 
| should at least be a way to recover and use the uncompiled version when 
| memory allocation fails, this is already done by the JIT but not when 
| compiling during installation. Before R or the package is patched, the 
| only workaround for memory constrained systems is probably to disable 
| byte-compilation of this package, as I read you are doing already.

Yes. And as a shortcut, we just turned it off unconditionally, ie on all
build architectures.  Worked fine as per

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

it has been built everywhere where we have R 3.5.0 (some 20 or so platforms).

The fix you suggest sounds ideal: if possible recover, and maybe WARN.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#898520: u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC

[Vagrant Cascadian]

On 2018-05-21, Vagrant Cascadian wrote:
> On 2018-05-12, Vagrant Cascadian wrote:
>> On 2018-05-12, Vagrant Cascadian wrote:
>>> Booting firefly-rk3288 seems to hang looking for environment:
>>>
>>>   U-Boot 2018.05+dfsg-1 (May 10 2018 - 20:24:57 +)
>>>   
>>>   Model: Firefly-RK3288
>>>   DRAM:  2 GiB
>>>   MMC:   dwmmc@ff0c: 1, dwmmc@ff0f: 0
>>>   Loading Environment from MMC...
>>>
>>> And just hangs there.

Still happening with v2018.07-rc1, too.


live well,
  vagrant

> I tried to bisect this, and got:
>
> commit 04a2ea248f58b3b6216d0cd0a6b8698df8b14355
> Author: Jean-Jacques Hiblot 
> Date:   Thu Sep 21 16:30:08 2017 +0200
>
> mmc: disable UHS modes if Vcc cannot be switched on and off
>
>
> But it fails in a slightly different way:
>
>   U-Boot 2018.01-00026-g04a2ea248f (May 21 2018 - 21:46:18 +)
>
>   Model: Firefly-RK3288
>   DRAM:  2 GiB
>   MMC:   dwmmc@ff0c: 1, dwmmc@ff0f: 0
>
> And just hangs without the "Loading Environment from MMC..."
> part...
>
>
> It is not a trivial revert on top of 2018.05, so I haven't been able to
> do that simple test.


signature.asc
Description: PGP signature

Bug#898468: debian-installer: black screen/long delay in graphical installer after switching from linux 4.15 to 4.16

[Cyril Brulebois]

Ben Hutchings  (2018-06-05):
> plymouth had the same problem, fixed in version 0.9.3-3.  You should be
> able to avoid it by running fc-cache as part of the initramfs build
> process.

\o/ \o/ \o/

Thanks for that extra hint! I'll look into it before finally switching
to more debugging (#900317).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#900750: thunderbird: Launching Thunderbird completely locks my Xwindow session

[Carsten Schoenert]

Hi,

On Mon, Jun 04, 2018 at 10:41:04AM +0200, g.gragnani wrote:
> f I launch thunderbird the whole xsession (XFCE) locks.
> I'm only able to move the mouse arrow (without any effect)
> and switching to a character console by using Cttrl-Alt-F1 etc.
> Killing thhunderbird does not solve the problem.
> 
> The same happens in an other machine, with a different set of installed
> packages, different hardware and running LXDE.

you have apparmor installed and it's likely it may causing issues.
Can you check the behaviour with a deactivated AppArmor profile and also
a removed AppAprmor package?

> Versions of packages thunderbird suggests:
> ii  apparmor  2.12-4

Other possible candidates are sometime the kernel. But without a small
set of logs it's quite impossible to track down the root of the issue.

Regards
Carsten

Bug#898468: debian-installer: black screen/long delay in graphical installer after switching from linux 4.15 to 4.16

[Ben Hutchings]

On Tue, 2018-06-05 at 19:20 +0200, Cyril Brulebois wrote:
> Hi,
> 
> Ben Hutchings  (2018-05-13):
> > This sounds similar to the regression seen in stable affecting gnome-
> > session.  libICE has a function for generating the MIT-MAGIC-COOKIE-1
> > cookie, which now uses libbsd's arc4random_buf() which now uses
> > getrandom().  getrandom() is documented to block (by default) when not
> > much entropy is available, but until recently it could return too early
> > after boot.
> > 
> > I don't know whether the cookie is generated this way when d-i starts
> > the X server.
> > 
> > I opened bug #898088 against libbsd because arc4random_buf() is
> > documented to return "very quickly".
> 
> Many thanks for the initial pointer and the libbsd bugfix. Unfortunately
> that wasn't our issue at all (we don't use libICE and there's no udeb
> for it anyway). I've documented my findings in a blog post:
>   
> https://debamax.com/blog/2018/05/25/debugging-black-screen-in-debian-installer/
> 
> 
> Summary: The issue is rather that we have fontconfig needing UUIDs for
> font handling, calling uuid_generate_random() from util-linux, which
> uses getrandom(), trying a few times with a little delay between each
> attempts when EAGAIN has been returned, before finally falling back to
> reading from /dev/{u,}random.
[...]

plymouth had the same problem, fixed in version 0.9.3-3.  You should be
able to avoid it by running fc-cache as part of the initramfs build
process.

Ben.

-- 
Ben Hutchings
Larkinson's Law: All laws are basically false.


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

Bug#898468: debian-installer: black screen/long delay in graphical installer after switching from linux 4.15 to 4.16

[Cyril Brulebois]

Hi,

Ben Hutchings  (2018-05-13):
> This sounds similar to the regression seen in stable affecting gnome-
> session.  libICE has a function for generating the MIT-MAGIC-COOKIE-1
> cookie, which now uses libbsd's arc4random_buf() which now uses
> getrandom().  getrandom() is documented to block (by default) when not
> much entropy is available, but until recently it could return too early
> after boot.
> 
> I don't know whether the cookie is generated this way when d-i starts
> the X server.
> 
> I opened bug #898088 against libbsd because arc4random_buf() is
> documented to return "very quickly".

Many thanks for the initial pointer and the libbsd bugfix. Unfortunately
that wasn't our issue at all (we don't use libICE and there's no udeb
for it anyway). I've documented my findings in a blog post:
  
https://debamax.com/blog/2018/05/25/debugging-black-screen-in-debian-installer/


Summary: The issue is rather that we have fontconfig needing UUIDs for
font handling, calling uuid_generate_random() from util-linux, which
uses getrandom(), trying a few times with a little delay between each
attempts when EAGAIN has been returned, before finally falling back to
reading from /dev/{u,}random.

I don't think making util-linux accept low entropy is the way to go,
even if I've checked that doing so makes this issue go away for the
graphical installer (see attached patch against util-linux, which
pretends that getrandom() isn't available), since it can be used in
things more critical than getting UUIDs for fonts…

Maybe fontconfig could be modified to use a different function to get
UUIDs (at least for its udeb build, in case uuid_generate_random() is
strongly preferred for its regular build) in its FcDirCacheCreateUUID()
function?

I'm adding util-linux and fontconfig maintainers to the loop for their
input/feedback.

Thanks for your time.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
Disable autodetection in configure, but also disable detection fallback
of both SYS_getrandom and __NR_getrandom to avoid accidental enabling
in lib/randutils.c
--- a/configure.ac
+++ b/configure.ac
@@ -462,7 +462,6 @@ AC_CHECK_FUNCS([ \
 	getdtablesize \
 	getexecname \
 	getmntinfo \
-	getrandom \
 	getrlimit \
 	getsgnam \
 	inotify_init \
--- a/lib/randutils.c
+++ b/lib/randutils.c
@@ -27,14 +27,14 @@
 
 #ifdef HAVE_GETRANDOM
 # include 
-#elif defined (__linux__)
+#elif 0
 # if !defined(SYS_getrandom) && defined(__NR_getrandom)
/* usable kernel-headers, but old glibc-headers */
 #  define SYS_getrandom __NR_getrandom
 # endif
 #endif
 
-#if !defined(HAVE_GETRANDOM) && defined(SYS_getrandom)
+#if 0
 /* libc without function, but we have syscal */
 #define GRND_NONBLOCK 0x01
 #define GRND_RANDOM 0x02


signature.asc
Description: PGP signature

Bug#900836: altree: FTBFS: fig2dev: not found

[Niko Tyni]

Source: altree
Version: 1.3.1-6
Severity: serious

This package fails to build from source on current sid/amd64.

   ==> building  fig/overview.pdftex <==
  /bin/sh: 1: fig2dev: not found
  make[4]: *** [LaTeX.mk:859: fig/overview.pdftex] Error 127
  make[4]: Leaving directory '/<>/Documentation'
  make[3]: *** [LaTeX.mk:805: manual.pdf_NEED_REBUILD] Error 2
  make[3]: Leaving directory '/<>/Documentation'
  make[2]: *** [LaTeX.mk:807: manual.pdf] Error 2
  make[2]: Leaving directory '/<>/Documentation'
  make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:8: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This was probably caused by

  latex-make (2.2.4-1) unstable; urgency=medium
   .
 * Replace transfig by fig2dev (package renamed) (Closes: #866153)
 * Move some dependency to recommends (not required if not using
   figlatex.sty or PS)
 * New upstream version
   + Reorganize pdfswitch
   + Fix python synxtax to be valid in 2.7 and 3
 
which relaxed its dependency on fig2dev to a recommendation.

 
https://salsa.debian.org/debian/latex-make/commit/4ed84338b64b7bd2fff6d6764f3236625c092043

-- 
Niko Tyni   nt...@debian.org

Bug#900835: magit-popup: Incomplete debian/copyright?

[Chris Lamb]

Source: magit-popup
Version: 2.12.3-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Rémi Vanicat 

Hi,

I just ACCEPTed magit-popup from NEW but noticed it was missing 
attribution in debian/copyright for at least magit-popup.org &
magit-popup.texi as it's missing Jonas Bernoulli attribution

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

Bug#900629: debian-edu-install: breaks installation of samba

[Holger Levsen]

On Tue, Jun 05, 2018 at 01:06:52PM +0200, Wolfgang Schweer wrote:
> > netbios name PROFITBRICKS-BUILD10-AMD64 is not a valid netbios name
> > ERROR: Invalid smb.conf
> > dpkg: error processing package samba-common-bin (--configure):
> >  installed samba-common-bin package post-installation script subprocess
> >  returned error exit status 255
> IMO this bug should/could be fixed in jenkins.d.n by setting a valid 
> netbios name via $(hostname).

no. 

installation must not fail just because the hostname is
profitbricks-build-amd64 or whatever.

> For Debian Edu the netbios name is set to TJENER, but at the moment 
> samba-common-bin gets installed, the vanilla smb.conf is tested (plus 
> preseeded values w/ netbios name not preseedable), replaced with the 
> Debian Edu one later (via Cfengine). So there's nothing Debian Edu can 
> do to fix this bug (afaict).

we can shorten the netbios name if using the hostname for the netbios
name is problematic because its too long.

> Please check the attached patch.

NACK, see above :)


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Processed: fixed 891515 in node-function-bind/1.1.1+ds-1

[Debian Bug Tracking System]

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

> fixed 891515 node-function-bind/1.1.1+ds-1
Bug #891515 [node-colormin] node-colormin : Depends: node-has (>= 1.0.1) but it 
is not installable
Marked as fixed in versions node-function-bind/1.1.1+ds-1.
> thanks
Stopping processing here.

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

Processed: closing 891515

[Debian Bug Tracking System]

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

> close 891515
Bug #891515 [node-colormin] node-colormin : Depends: node-has (>= 1.0.1) but it 
is not installable
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#900826: Fixed in upstream

[Juhani Numminen]

Control: forwarded -1 https://github.com/sabnzbd/sabnzbd/pull/1132
Control: tags -1 fixed-upstream

On Tue, 5 Jun 2018 11:30:34 -0400 BJ McCormick  wrote:
> I looked at the package available upstream (2.3.4) and the startup script
> seems to be fixed in that version. It will allow cheetah versions greater
> than 2.x.

Moreover, it seems to be fixed by the Debian maintainer of this package :)

Processed: Re: Bug#900826: Fixed in upstream

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/sabnzbd/sabnzbd/pull/1132
Bug #900826 [sabnzbdplus] sabnzbdplus does not start due to python cheetah 
version error
Set Bug forwarded-to-address to 'https://github.com/sabnzbd/sabnzbd/pull/1132'.
> tags -1 fixed-upstream
Bug #900826 [sabnzbdplus] sabnzbdplus does not start due to python cheetah 
version error
Added tag(s) fixed-upstream.

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

Bug#898060: Stall NFS clients: RPC request reserved 84 but used 272

[Harald Dunkel]

metoo

I have "rpc request reserved 84 but used 268", but I am not picky.


Regards
Harri

Bug#900826: Fixed in upstream

[BJ McCormick]

I looked at the package available upstream (2.3.4) and the startup script
seems to be fixed in that version. It will allow cheetah versions greater
than 2.x.

Bug#900826: sabnzbdplus does not start due to python cheetah version error

[BJ McCormick]

Package: sabnzbdplus
Version: 2.3.2+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

sabnzbdplus has stopped running on my testing system. When running from CLI i
get the following error:
~$ sabnzbdplus
Sorry, requires Python module Cheetah 2.0rc7 or higher.

Cheetah module is installed it is version 3.1.0-1. Startup script checks
cheetah version in a silly way.

try:
import Cheetah
if Cheetah.Version[0] != '2':
raise ValueError
except ValueError:
print "Sorry, requires Python module Cheetah 2.0rc7 or higher."
sys.exit(1)
except:
print "The Python module Cheetah is required"
sys.exit(1)

As you can see version 3 will not work...



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

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

Versions of packages sabnzbdplus depends on:
ii  libjs-bootstrap   3.3.7+dfsg-2
ii  libjs-excanvas0.r3-4
ii  libjs-jquery  3.2.1-1
ii  libjs-jquery-tablesorter  1:2.30.4+dfsg1-1
ii  libjs-jquery-ui   1.12.1+dfsg-5
ii  libjs-mochikit1.4.2-4
ii  libjs-moment  2.22.1+ds-1
ii  lsb-base  9.20170808
ii  python2.7.15~rc1-1
ii  python-cheetah3.1.0-1
ii  python-configobj  5.0.6-2
ii  python-sabyenc3.3.5-1
ii  python-six1.11.0-2

Versions of packages sabnzbdplus recommends:
ii  libavahi-compat-libdnssd1  0.7-4
ii  p7zip-full 16.02+dfsg-6
ii  par2   0.8.0-1
ii  python-cryptography2.1.4-1
ii  python-dbus1.2.8-2
ii  unrar  1:5.5.8-1

Versions of packages sabnzbdplus suggests:
ii  python-gtk22.24.0-5.1+b1
ii  python-notify  0.1.1-4

-- no debconf information

Bug#899868: marked as done (marisa: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 15:04:31 +
with message-id 
and subject line Bug#899868: fixed in marisa 0.2.5-1
has caused the Debian Bug report #899868,
regarding marisa: Invalid maintainer address 
pkg-ime-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.)


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

Dear uploader of marisa,

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

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: marisa
Source-Version: 0.2.5-1

We believe that the bug you reported is fixed in the latest version of
marisa, 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.
Boyuan Yang <073p...@gmail.com> (supplier of updated marisa package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Jun 2018 15:45:30 +0800
Source: marisa
Binary: libmarisa-dev libmarisa-perl libmarisa0 marisa python-marisa 
python3-marisa ruby-marisa
Architecture: source
Version: 0.2.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 libmarisa-dev - development files for libmarisa
 libmarisa-perl - Perl bindings for MARISA
 libmarisa0 - C++ library to provide an implementation of MARISA
 marisa - command line tools for libmarisa
 python-marisa - Python bindings for MARISA
 python3-marisa - Python3 bindings for MARISA
 ruby-marisa - Ruby bindings for MARISA
Closes: 808276 836374 898018 899868 900680
Changes:
 marisa (0.2.5-1) unstable; urgency=medium
 .
   [ Mitsuya Shibata ]
   * add dh-python to Build-Depends
   * remove no longer needed XS-Testsuite field
   * fix typo
 .
   [ Boyuan Yang ]
   * New upstream release with different upstream on GitHub.
 Closes: #900680.
   * debian: Apply "wrap-and-sort -abst" for unified format.
   * debian/control:
 - Add myself into uploaders list.
 - Bump Standards-Version to 4.1.4.
 - Add X-Python3-Version field as recommended.
 - Replace "Extra" package priority with "Optional" to fit policy
   requirement.

Bug#899205: numpy boolean subtract, the `-` operator, is deprecated, use the bitwise_xor, the `^` operator, or the logical_xor function instead (Was: Bug#899205: python-cogent: Test suite fails with l

[Daniele Nicolodi]

On 05/06/2018 01:00, Andreas Tille wrote:

> ==
> ERROR: test_consistent_gap_degen_handling 
> (test_core.test_sequence.ModelSequenceTests)
> gap degen character should be treated consistently
> --
> Traceback (most recent call last):
>   File 
> "/tmp/autopkgtest-lxc.5a99fnj6/downtmp/autopkgtest_tmp/tests/test_core/test_sequence.py",
>  line 660, in test_consistent_gap_degen_handling
> self.assertEqual(dna.stripBadAndGaps(), raw_ungapped)
>   File "/usr/lib/python2.7/dist-packages/cogent/core/sequence.py", line 1251, 
> in stripBadAndGaps
> valid_indices -= self._data == i
> TypeError: numpy boolean subtract, the `-` operator, is deprecated, use the 
> bitwise_xor, the `^` operator, or the logical_xor function instead.
> 
> ==
> 
> 
> I would be happy for some suggested patch how to solve this.  The line
> in question is
> 
>
> https://salsa.debian.org/med-team/python-cogent/blob/master/cogent/core/sequence.py
> 
>Line 1251
> 
> If my feeling is not totally wrong the correct patch would be 
> 
>valid_indices -= (self._data == i)
> 
> since the left value is rather an integer than boolean.
> 
> What do you think?

Without analyzing the code in the fine details, and assuming self._data
is a numpy array or a subclass, I think the name of the variable is
misleading.  Looking at the whole function it seems to be a bool array.
It should be easy to confirm this with pdb or simply inserting a print()
statement in the right place.

def stripBadAndGaps(self):
"""Returns copy of self with bad chars and gaps excised."""
gap_indices = map(self.Alphabet.index, self.MolType.Gaps)
valid_indices = self._data < len(self.Alphabet)
for i in gap_indices:
valid_indices -= self._data == i
result = compress(valid_indices, self._data)
return self.__class__(result, Info=self.Info)

The fix should be to replace the subtraction with:

valid_indices ^= self._data == i

Cheers,
Dan

Processed: Test suite failing

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 899124
Bug #900825 [src:cider] Test suite failing
900825 was not blocked by any bugs.
900825 was not blocking any bugs.
Added blocking bug(s) of 900825: 899124

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

Bug#900822: needs magit 2.12

[David Bremner]

Package: elpa-magithub
Version: 0.1.5-2
Severity: serious

Thanks to my upload, elpa-magithub is now uninstallable in sid.

I think it should also get a versioned depends to help with upgrades / 
migrations


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

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

Versions of packages elpa-magithub depends on:
ii  elpa-ghub+  0.2.1-2
ii  elpa-git-commit 2.11.0-1
ii  elpa-magit  2.11.0-1
ii  elpa-markdown-mode  2.3+154-1
ii  elpa-s  1.12.0-1
ii  emacsen-common  2.0.8

Versions of packages elpa-magithub recommends:
ii  emacs  47.0

elpa-magithub suggests no packages.

-- no debconf information

Bug#896386: marked as done (python3-srp: srp fails to import)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 13:36:51 +
with message-id 
and subject line Bug#896386: fixed in python-srp 1.0.14-1
has caused the Debian Bug report #896386,
regarding python3-srp: srp fails to import
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.)


-- 
896386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-srp
Version: 1.0.4-1.1+b2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-srp importing the module srp
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/srp/__init__.py", line 12, in 
import srp._ctsrp
  File "/usr/lib/python3/dist-packages/srp/_ctsrp.py", line 141, in 
dlls.append( ctypes.cdll.LoadLibrary('libssl.so') )
  File "/usr/lib/python3.6/ctypes/__init__.py", line 426, in LoadLibrary
return self._dlltype(name)
  File "/usr/lib/python3.6/ctypes/__init__.py", line 348, in __init__
self._handle = _dlopen(self._name, mode)
OSError: libssl.so: cannot open shared object file: No such file or directory

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-srp
Source-Version: 1.0.14-1

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

Debian distribution maintenance software
pp.
Micah Anderson  (supplier of updated python-srp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 05 Jun 2018 08:46:55 -0400
Source: python-srp
Binary: python-srp python3-srp
Architecture: source
Version: 1.0.14-1
Distribution: unstable
Urgency: medium
Maintainer: Ben Carrillo 
Changed-By: Micah Anderson 
Description:
 python-srp - Secure Remote Password protocol implementation
 python3-srp - Secure Remote Password protocol implementation (Python 3)
Closes: 896386
Changes:
 python-srp (1.0.14-1) unstable; urgency=medium
 .
   [ Micah Anderson ]
   * New upstream version (Closes: #896386)
   * Updated standards version: no changes
   * Add build-dep on python3-sphinx
   * Remove old X-Python-Version control fields
   * Update debian/watch
 .
   [ Antoine Beaupré ]
   * fix Homepage/Vcs fields
   * note that py3k patch was removed, factored in upstream
Checksums-Sha1:
 e97f78998f6cee876bfc845bdba5a908ca00b1b5 1599 python-srp_1.0.14-1.dsc
 6f153f6039614fb99ee696a6e3c49e374f76f3a1 19436 python-srp_1.0.14.orig.tar.gz
 2e8df487c3f94b90547ba6bd278e119ced8f04c9 3192 python-srp_1.0.14-1.debian.tar.xz
 578dad8ec23b7c355fc395d7f9b527a23b0a7cc8 7654 
python-srp_1.0.14-1_amd64.buildinfo
Checksums-Sha256:
 fd7ce06700843fd64c10c3d7b52b8a8e864168bdc91d6aec320b6dbee3aaf227 1599 
python-srp_1.0.14-1.dsc
 9f31750a204bff95ed16fd6ef8201f36c63e3f2967fb93b5a66ba455c1878ea8 19436 
python-srp_1.0.14.orig.tar.gz
 eb45dec8c4c31d2656dfc7e1ac92e79540c895934b6dc65da03d4d0743f8854f 3192 
python-srp_1.0.14-1.debian.tar.xz
 aec848e41cf02a885c21f0bc8544364f2c3feb1c068f7656341d15096562580d 7654 
python-srp_1.0.14-1_amd64.buildinfo
Files:
 6a6f98509a7522325c4b9a3a2f23abef 1599 python optional python-srp_1.0.14-1.dsc
 ef98f63fce6de2828620b94472a6f13c 19436 python optional 
python-srp_1.0.14.orig.tar.gz
 01f2f419f92c60a1c280085dc1a33b2f 3192 python optional 
python-srp_1.0.14-1.debian.tar.xz
 ecb6aface0ab70ddf407fab912538865 7654 python optional 
python-srp_1.0.14-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAlsWjAUACgkQPqHd3bJh
2Xu7gQgAkRQLWD+Fvc9v1N/hM1oE9Z+13KhIDLEzqJ7icBSGHqJWlfGKKn6HEAMt
JuDrItfl3RoQIZnKj0yJiwCZJb18mabfm21jp

Bug#885796: marked as done (etherape: Depends on libgnomecanvas)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 13:19:36 +
with message-id 
and subject line Bug#885796: fixed in etherape 0.9.18-1
has caused the Debian Bug report #885796,
regarding etherape: Depends on libgnomecanvas
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.)


-- 
885796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: etherape
Version: 0.9.15+hg20171110-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomecanvas
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomecanvas.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: etherape
Source-Version: 0.9.18-1

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated etherape package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 05 Jun 2018 15:05:20 +0200
Source: etherape
Binary: etherape etherape-data
Architecture: source all amd64
Version: 0.9.18-1
Distribution: unstable
Urgency: medium
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 etherape   - graphical network monitor
 etherape-data - graphical network monitor (data files)
Closes: 885796
Changes:
 etherape (0.9.18-1) unstable; urgency=medium
 .
   * New upstream release.
 - EtherApe is now ported from gnomecanvas to GooCanvas.
   Closes: #885796
   * Adjust build dependencies.
Checksums-Sha1:
 0ccc2c658c9511b706423136611bb74a5cab971b 1861 etherape_0.9.18-1.dsc
 a6a06512e483b68405c3f2e15ac7f019d92bb74c 1436265 etherape_0.9.18.orig.tar.gz
 b9d56e8b9d181806f6b86c37d9f22a0e861e4b1d 5824 etherape_0.9.18-1.debian.tar.xz
 ec36155eff36553481837ccd344c52be60a6d4f0 656676 etherape-data_0.9.18-1_all.deb
 28a2b49219c58a4c51b8e91566034e34184135c6 265272 
etherape-dbgsym_0.9.18-1_amd64.deb
 ccc0a8394796fb95912b4091f99b7b83bb63cee5 15353 
etherape_0.9.18-1_amd64.buildinfo
 0d94c02a0b263e601c5bfeb2fe44158e77709c98 86944 etherape_0.9.18-1_amd64.deb
Checksums-Sha256:
 5ab619b3a3716b3160eb244de24ce4ce1a379d89c4808c44a159b2f18efea8d7 1861 
etherape_0.9.18-1.dsc
 bbc24f47d6072cd8ee6ed31303d4ec31d842dc53291613a440fe971d0b732c79 1436265 
etherape_0.9.18.orig.tar.gz
 7af23d4858474aa4a643280b053f971d7c2a0a155ec14a73602d61b9dc22560b 5824 
etherape_0.9.18-1.debian.tar.xz
 d7f46292d9a5af943f66b2f93ab18688e7d70c3482305a337209a45149c69253 656676 
etherape-data_0.9.18-1_all.deb
 aed4e065a4b9e7289e128c84d35b4ac62cca41ce97bf74883d9055a2e0952acf 265272 
etherape-dbgsym_0.9.18-1_amd64.deb
 8978e3c57661ad4bd4ccebc10fd7cb1d2c0528a34de6c377fc120704db293508 15353 
etherape_0.9.18-1_amd64.buildinfo
 45371da4488e76686a0d89c4745ff5333f5e1519490279eada2b21a546ed17c4 86944 
etherape_0.9.18-1_amd64.deb
Files:
 c95346782ad63d40cca434039d629452 1861 gnome optional etherape_0.9.18-1.dsc
 6d6a6c03e03e2d6aae3a59cd42752ac1 1436265 gnome optional 
etherape_0.9.18.orig.tar.gz
 007451d851017b77f386509d4cb22d44 5824 gnome optional 
etherape_0.9.18-1.debian.tar.xz
 e60e77fa52abe5b91c76619d3bbd1cf2 656676 gnome optional 
etherape-data_0.9.18-1_all.deb
 8da6ab3b6b6e371a6264c4ed4daa8eec 265272 debug optional 
etherape-dbgsym_0.9.18-1_amd64.deb
 d9d1d27fac2c45b5421a2aa40851a5b4 15353 gnome optional 
etherape_0.9.18-1_amd64.buildinfo
 d53c03214f8d69e69936043237e512c1 86944 gnome optional 
etherape_0.9.18-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWKA9xYJCWk3IuQ4TEtmwSpDL2OQFAlsWi2cACgkQEtmwSpDL
2OQvCA/+JkRG+c0Qmcw+F9Ma8l08ihQppfxowN73SlUw1skzKmL4ajQw

Bug#898483: marked as done (physfs: setWriteDir creates an empty file)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 13:20:28 +
with message-id 
and subject line Bug#898483: fixed in libphysfs 3.0.1-2
has caused the Debian Bug report #898483,
regarding physfs: setWriteDir creates an empty file
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.)


-- 
898483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lincity-ng
Version: 2.9~git20150314-3
Severity: serious

Dear lincity-ng maintainer,

When there is no ~/.lincity-ng directory under user's home, lincity-ng
will fail on start.

~ ❯❯❯ lincity-ng
Starting lincity-ng (version 2.9.beta)...
Unexpected exception: Failed creating configuration directory 
'/home/lumin/.lincity-ng': unsupported

The user must manually delete the plain file ~/.lincity-ng, and manually
create the directory ~/.lincity-ng to make it work.

For a user who doesn't know the way to fix, the package is totally
unusable, hence I'm marking this bug as RC.

Best,
--- End Message ---
--- Begin Message ---
Source: libphysfs
Source-Version: 3.0.1-2

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated libphysfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 05 Jun 2018 14:28:17 +0200
Source: libphysfs
Binary: libphysfs-dev libphysfs1
Architecture: source amd64
Version: 3.0.1-2
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 libphysfs-dev - filesystem abstraction library for game programmers 
(development
 libphysfs1 - filesystem abstraction library for game programmers
Closes: 898483
Changes:
 libphysfs (3.0.1-2) unstable; urgency=high
 .
   * Move package to my own repository.
   * Bump Standards-Version to 4.1.4.
   * Move source.lintian-overrides file to source directory.
   * Add upstream patch 01-setwritedir to fix a bug in the setWriteDir function.
 Much thanks Gianfranco Costamagna for taking care of this.
 Closes: #898483
   * Bump debian/compat to level 11.
   * Adjust lintian overrides.
Checksums-Sha1:
 aac2ae1f10539fa33b61fd354f3e6721c3d9e191 1838 libphysfs_3.0.1-2.dsc
 d8a752b0618f53e83b82adc36a2665d185e40a4d 7116 libphysfs_3.0.1-2.debian.tar.xz
 060fe55af26ee6a4a290963422d84d6d2381cf40 25712 
libphysfs-dev-dbgsym_3.0.1-2_amd64.deb
 84144410e0556225a49b42235d93f6f25a483ed5 101744 libphysfs-dev_3.0.1-2_amd64.deb
 e92f947f916c9ac78724e6647f42cf7175a26796 180612 
libphysfs1-dbgsym_3.0.1-2_amd64.deb
 540dfb10e294a47ed34dffcb1fe357c583d74cc1 69112 libphysfs1_3.0.1-2_amd64.deb
 eb954e8c9c96ff3483936f7ec6e5431abd93e061 8055 libphysfs_3.0.1-2_amd64.buildinfo
Checksums-Sha256:
 c5e1e8d0f8596d84d59ba7bf930f0ca358ca22fafe33a0839a167aec86e7b2f8 1838 
libphysfs_3.0.1-2.dsc
 b8b2cf111c4bd6597e7ff7f57f54f8e4dc5012187897b0cd12669d4f3b752f8f 7116 
libphysfs_3.0.1-2.debian.tar.xz
 137e2203e4d2ba7fb4490b390b7062578e4fa794b70b2ef132b038b0f132f484 25712 
libphysfs-dev-dbgsym_3.0.1-2_amd64.deb
 bb5bc4f33feaa387a7f60efe4f5e7ecd3e6c7cf1ff3218cdea37f8b7ee8ebd0e 101744 
libphysfs-dev_3.0.1-2_amd64.deb
 74dde5087afd9f0321c673083984cf61983ca4155355f6a525c322632671b271 180612 
libphysfs1-dbgsym_3.0.1-2_amd64.deb
 88c00c099cd749e2b2c6f5763a3530abdaebc9fad6e6e2c3c44585cd3b9af81b 69112 
libphysfs1_3.0.1-2_amd64.deb
 a14382ae661d7a68c1c47f17139f45d0945549e79c05af70d1a05d0852b81124 8055 
libphysfs_3.0.1-2_amd64.buildinfo
Files:
 3126063ad216d2ad3f80b99486da6840 1838 libs optional libphysfs_3.0.1-2.dsc
 12daf84d4296d330bc107e0b36b8aa09 7116 libs optional 
libphysfs_3.0.1-2.debian.tar.xz
 34ee995ad687a66257eaf6fd5127a393 25712 debug optional 
libphysfs-dev-dbgsym_3.0.1-2_amd64.deb
 083a12d29d70ce7dac8fc03774dfdd5f 101744 libdevel optional 
libphysfs-dev_3.0.1-2_amd64.deb
 45c5607c48df6808d3ba1aab618e2631 180612 debug optional 
libphysfs1-dbgsym_3.0.1-2_amd64.deb
 3c9174596837917f9c63301d96f0e06e 69112 libs optional 
libphysfs1_3.0.1-2_amd64.deb
 75785872fc0560fcb72a02e8499d39e4 8055 l

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

[Sean Whitton]

Hello Vasudev,

On Sat, Jun 02, 2018 at 05:16:05PM +0530, Vasudev Kamath wrote:
>
> I read through and prepared a version to experimental which symlinks
> fa-solid-900.ttf as fontawesome-webfont.ttf. I've uploaded it to
> experimental, can you please check if this helps?.
>
> @Others Please let me know if this new version in experimental with
> suggestion from Thomas improves situation in your cases.

This does not help the mkdocs-bootstrap case.  That appears to need the
.woff2 font.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#900811: Acknowledgement (libadios-dev: adios_config pkg-config typo: "adiso")

[Axel Huebl]

It's likely that report

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894165

is caused by this bug.



signature.asc
Description: OpenPGP digital signature

Bug#899956: marked as done (ibus-array: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 11:20:16 +
with message-id 
and subject line Bug#899956: fixed in ibus-array 0.2.1-1
has caused the Debian Bug report #899956,
regarding ibus-array: Invalid maintainer address 
pkg-ime-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.)


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

Dear uploader of ibus-array,

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

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: ibus-array
Source-Version: 0.2.1-1

We believe that the bug you reported is fixed in the latest version of
ibus-array, 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.
Keng-Yu Lin  (supplier of updated ibus-array package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Jun 2018 18:24:24 +0800
Source: ibus-array
Binary: ibus-array
Architecture: source amd64
Version: 0.2.1-1
Distribution: unstable
Urgency: low
Maintainer: Keng-Yu Lin 
Changed-By: Keng-Yu Lin 
Description:
 ibus-array - Array 30 input engine for iBus
Closes: 899956
Changes:
 ibus-array (0.2.1-1) unstable; urgency=low
 .
   * New upstream release
   * Remove pkg-ime-de...@lists.alioth.debian.org (Closes: 899956)
Checksums-Sha1:
 f8642f8fad491dc36f599b4695a60fe00be79aaf 2086 ibus-array_0.2.1-1.dsc
 06c7bbc4506e6035bc7c2a5cc825b7cdaed03f22 2841528 ibus-array_0.2.1.orig.tar.gz
 288df84a6229c9bb4c28746aeec02a6c1dd1d2d3 3232 ibus-array_0.2.1-1.debian.tar.xz
 5108ab05e7413da7fefe37557142d1204157e480 25604 
ibus-array-dbgsym_0.2.1-1_amd64.deb
 b8c0933a804925606f8595f41a6b7026a94254ea 8494 
ibus-array_0.2.1-1_amd64.buildinfo
 a899703a899548f79b795adbeb81be5d197b2f2a 1239448 ibus-array_0.2.1-1_amd64.deb
Checksums-Sha256:
 af03ba36b40bb7b3a7333bd9d63254604b27b8c7cfd169a87f2ca1bf23f8f094 2086 
ibus-array_0.2.1-1.dsc
 aabcb1218cfb8008fe505f03e6866af88d8d5cf7cac0492d0f3a66720a453237 2841528 
ibus-array_0.2.1.orig.tar.gz
 6e0cebf7b910a45fe6b5397d355a6b4ae9a0bfd00c3c7b3ab314f1d392a04c2a 3232 
ibus-array_0.2.1-1.debian.tar.xz
 f29d3a67e43d3a029d35f1dfbf

Bug#900629: debian-edu-install: breaks installation of samba

[Wolfgang Schweer]

On Sat, Jun 02, 2018 at 11:33:36AM +0200, Holger Levsen wrote:
> Package: debian-edu-install
> Version: 2.10.9
> Severity: serious
[..] 
> Setting up samba-common-bin (2:4.8.2+dfsg-1) ...
> Checking smb.conf
> WARNING: The "syslog" option is deprecated
> netbios name PROFITBRICKS-BUILD10-AMD64 is not a valid netbios name
> ERROR: Invalid smb.conf
> dpkg: error processing package samba-common-bin (--configure):
>  installed samba-common-bin package post-installation script subprocess
>  returned error exit status 255

IMO this bug should/could be fixed in jenkins.d.n by setting a valid 
netbios name via $(hostname).

For Debian Edu the netbios name is set to TJENER, but at the moment 
samba-common-bin gets installed, the vanilla smb.conf is tested (plus 
preseeded values w/ netbios name not preseedable), replaced with the 
Debian Edu one later (via Cfengine). So there's nothing Debian Edu can 
do to fix this bug (afaict).

Please check the attached patch.

Wolfgang
From d17fd2986931dc72f65f840aff77ff286506d408 Mon Sep 17 00:00:00 2001
From: Wolfgang Schweer 
Date: Tue, 5 Jun 2018 10:51:14 +0200
Subject: [PATCH] Use netbios compliant hostname.

---
 hosts/profitbricks-build10-amd64/etc/hosts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hosts/profitbricks-build10-amd64/etc/hosts b/hosts/profitbricks-build10-amd64/etc/hosts
index b363feea..00c5f6cd 100644
--- a/hosts/profitbricks-build10-amd64/etc/hosts
+++ b/hosts/profitbricks-build10-amd64/etc/hosts
@@ -1,5 +1,5 @@
 127.0.0.1	localhost
-127.0.1.1	profitbricks-build10-amd64
+127.0.1.1	p-build10-amd64
 
 10.2.1.1	local-http-proxy
 
-- 
2.17.1



signature.asc
Description: PGP signature

Bug#900811: libadios-dev: adios_config pkg-config typo: "adiso"

[Axel Huebl]

Package: libadios-dev
Version: 1.11.0-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the file `adios_config` added in the Debian packages contains a typo in line
"83" reading:

if [ "$OPT_SEQ" == "yes" ]; then
CFLAGS=`pkg-config adiso --variable ADIOS_SEQ_INC`
else
CFLAGS=`pkg-config adios --variable ADIOS_INC`
fi

The first branch of the if should read `adios` as well, not `adiso`.

This typo makes the tool `adios_config` not usable for downstream developers
which call it.

Also, the script `adios_config` depends on `pkg-config` so `pkg-config` should
be a dependency for `libadios-dev`.


Best regards and thanks for your great support with packaging ADIOS!
Axel



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

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

libadios-dev depends on no packages.

Versions of packages libadios-dev recommends:
ii  libadios-bin  1.11.0-1+b1

libadios-dev suggests no packages.

-- no debconf information

Bug#900754: marked as done (idjc: missing dependency on libogg)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 10:34:54 +
with message-id 
and subject line Bug#900754: fixed in idjc 0.8.17-1
has caused the Debian Bug report #900754,
regarding idjc: missing dependency on libogg
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.)


-- 
900754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: idjc
Version: 0.8.16-1
Severity: serious
Forwarded: https://sourceforge.net/p/idjc/bugs/99/

Hi,

idjc (specifically the idjc.so library) uses symbols from libogg, but
does not declare a dependency on that package.

> $ readelf --dyn-sym /usr/lib/idjc/idjc.so | grep 'UND ogg_'
> 34:  0 FUNCGLOBAL DEFAULT  UND ogg_sync_wrote
> 47:  0 FUNCGLOBAL DEFAULT  UND ogg_sync_reset
> 54:  0 NOTYPE  GLOBAL DEFAULT  UND 
> ogg_stream_flush_fill
> 94:  0 NOTYPE  GLOBAL DEFAULT  UND ogg_page_eos
>102:  0 NOTYPE  GLOBAL DEFAULT  UND 
> ogg_stream_packetpeek
>114:  0 NOTYPE  GLOBAL DEFAULT  UND 
> ogg_stream_reset_serialno
>120:  0 NOTYPE  GLOBAL DEFAULT  UND ogg_page_continued
>160:  0 FUNCGLOBAL DEFAULT  UND ogg_page_granulepos
>165:  0 FUNCGLOBAL DEFAULT  UND ogg_stream_clear
>168:  0 FUNCGLOBAL DEFAULT  UND ogg_stream_init
>189:  0 NOTYPE  GLOBAL DEFAULT  UND ogg_page_pageno
>195:  0 NOTYPE  GLOBAL DEFAULT  UND ogg_packet_clear
>210:  0 FUNCGLOBAL DEFAULT  UND 
> ogg_stream_packetout
>233:  0 FUNCGLOBAL DEFAULT  UND ogg_sync_init
>238:  0 FUNCGLOBAL DEFAULT  UND ogg_sync_buffer
>248:  0 FUNCGLOBAL DEFAULT  UND ogg_sync_clear
>256:  0 FUNCGLOBAL DEFAULT  UND ogg_stream_reset
>273:  0 FUNCGLOBAL DEFAULT  UND ogg_stream_flush
>293:  0 FUNCGLOBAL DEFAULT  UND ogg_stream_packetin
>302:  0 FUNCGLOBAL DEFAULT  UND ogg_page_serialno
>303:  0 FUNCGLOBAL DEFAULT  UND ogg_sync_pageout
>327:  0 FUNCGLOBAL DEFAULT  UND ogg_page_bos
>346:  0 NOTYPE  GLOBAL DEFAULT  UND ogg_page_packets
>354:  0 NOTYPE  GLOBAL DEFAULT  UND ogg_sync_pageseek
>368:  0 FUNCGLOBAL DEFAULT  UND ogg_stream_pageout
>391:  0 FUNCGLOBAL DEFAULT  UND ogg_stream_pagein

This probably happens because idjc.so is not linked against libogg
> $ readelf --dynamic /usr/lib/idjc/idjc.so | grep ogg

Other evidence from the build logs:
>dh_shlibdeps -a -O--parallel
> dpkg-shlibdeps: warning: debian/idjc/usr/lib/idjc/idjc.so contains an 
> unresolvable reference to symbol ogg_stream_flush_fill: it's probably a plugin
> dpkg-shlibdeps: warning: 25 other similar warnings have been skipped (use -v 
> to see them all)

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: idjc
Source-Version: 0.8.17-1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated idjc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Jun 2018 11:12:34 +0100
Source: idjc
Binary: idjc
Architecture: source
Version: 0.8.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: James Cowgill 
Description:
 idjc   - graphical shoutcast/icecast client
Closes: 831630 888330 900754
Changes:
 idjc (0.8.17-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Sebastian Ramacher ]
   * New upstream release.
 - Fixes FTBFS with FFmpeg 4.0. (Closes: #888330)
 .
   * d/control

Bug#890646: python3-postgresql: Connect to postgresql-Database Version 10 (buster) fails with an python error

[Johann Spies]

Package: python3-postgresql
Version: 1.1.0-2+b4
Followup-For: Bug #890646

Dear Maintainer,

This is not a problem with python3.5 but happens on 3.6.


   * What led up to the situation?

 In [2]: import postgresql

 In [3]: db = postgresql.open('pq://js:x.js@localhost:5432/js')
Traceback (most recent call last):

  File "", line 1, in 
db = postgresql.open('pq://js:x.js@localhost:5432/js')

  File "/usr/lib/python3/dist-packages/postgresql/__init__.py", line 94, in open
c.connect()

  File "/usr/lib/python3/dist-packages/postgresql/driver/pq3.py", line 2422, in 
connect
self._establish()

  File "/usr/lib/python3/dist-packages/postgresql/driver/pq3.py", line 2554, in 
_establish
self.version_info = pg_version.normalize(pg_version.split(sv))

  File "/usr/lib/python3/dist-packages/postgresql/versionstring.py", line 28, 
in split
vlist = [int(x or '0') for x in v[:-1]]

  File "/usr/lib/python3/dist-packages/postgresql/versionstring.py", line 28, 
in 
vlist = [int(x or '0') for x in v[:-1]]

ValueError: invalid literal for int() with base 10: '4 (Debian 10'

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?
No



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

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

Versions of packages python3-postgresql depends on:
ii  libc6  2.27-3
ii  libjs-jquery   3.2.1-1
ii  libjs-underscore   1.8.3~dfsg-1
ii  libpython3-stdlib  3.6.5-3
ii  python33.6.5-3

python3-postgresql recommends no packages.

python3-postgresql suggests no packages.

-- no debconf information
The integrity and confidentiality of this e-mail is governed by these terms / 
Die integriteit en vertroulikheid van hierdie e-pos word deur die volgende 
bepalings gereël. http://www.sun.ac.za/emaildisclaimer

Processed: Re: Bug#900189: kdenlive: graphical issue on ppc64el architecture

[Debian Bug Tracking System]

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

> severity #900189 important
Bug #900189 [kdenlive] kdenlive: graphical issue on ppc64el architecture
Severity set to 'important' from 'critical'
> tag #900189 + moreinfo
Bug #900189 [kdenlive] kdenlive: graphical issue on ppc64el architecture
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#900750: Vanilla thunderbird works

[G. L. Gragnani]

As in the title: the executable downloaded from the Mozilla site, works 
perfectly.

Best regards.

--
Gian Luigi Gragnani
Diten - University of Genoa
Via Opera Pia 11A, 16145 Genova, Italy
phone: + 39 010 353 2244

Bug#888095: pinging again

[Andy Li]

I would like to ping again in hope that it will be fixed soon.

Best regards,
Andy

Bug#900754: Bug #900754 in idjc marked as pending

[jcowgill]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/idjc/commit/16679635d6476d4a1994c5ea64beac0d9a4c5415


Add patch ensuring idjc.so is linked against libogg

Closes: #900754



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/900754

Processed: Bug #900754 in idjc marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #900754 [idjc] idjc: missing dependency on libogg
Added tag(s) pending.

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

Bug#900615: marked as done (libpostgresql-jdbc-java: no Depends on libscram-java)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2018 08:37:58 +
with message-id 
and subject line Bug#900615: fixed in libpgjava 42.2.2-3
has caused the Debian Bug report #900615,
regarding libpostgresql-jdbc-java: no Depends on libscram-java
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.)


-- 
900615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: osmosis
version: 0.46-3
severity: serious

While building with protobuf 3.5.2 from experimental, this build failed,
but I think this is unrelated to protobuf change.

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all dependencies for configuration
':osmosis-hstore-jdbc:compileClasspath'.
> Could not resolve com.ongres.scram:client:debian.
  Required by:
  project :osmosis-hstore-jdbc > org.postgresql:postgresql:debian
   > No cached version of com.ongres.scram:client:debian available for
offline mode.

* Try:
Run with --debug option to get more log output.

* Exception is:
org.gradle.api.artifacts.ResolveException: Could not resolve all
dependencies for configuration ':osmosis-hstore-jdbc:compileClasspath'.
at
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration.rethrowFailure(DefaultLenientConfiguration.java:178)
at
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$1.collectFiles(DefaultLenientConfiguration.java:127)
at
org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.doGetFiles(DefaultConfiguration.java:516)
at
org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.getFiles(DefaultConfiguration.java:367)
at
org.gradle.api.internal.artifacts.configurations.DefaultConfiguration_Decorated.getFiles(Unknown
Source)
at
org.gradle.api.internal.file.AbstractFileCollection.iterator(AbstractFileCollection.java:68)
at
org.gradle.api.internal.changedetection.state.AbstractFileCollectionSnapshotter$FileCollectionVisitorImpl.visitCollection(AbstractFileCollectionSnapshotter.java:133)
at
org.gradle.api.internal.file.AbstractFileCollection.visitRootElements(AbstractFileCollection.java:234)
at
org.gradle.api.internal.file.CompositeFileCollection.visitRootElements(CompositeFileCollection.java:185)
at
org.gradle.api.internal.changedetection.state.AbstractFileCollectionSnapshotter.snapshot(AbstractFileCollectionSnapshotter.java:71)
at
org.gradle.api.internal.changedetection.rules.AbstractNamedFileSnapshotTaskStateChanges.buildSnapshots(AbstractNamedFileSnapshotTaskStateChanges.java:87)
at
org.gradle.api.internal.changedetection.rules.AbstractNamedFileSnapshotTaskStateChanges.(AbstractNamedFileSnapshotTaskStateChanges.java:54)
at
org.gradle.api.internal.changedetection.rules.InputFilesTaskStateChanges.(InputFilesTaskStateChanges.java:28)
at
org.gradle.api.internal.changedetection.rules.TaskUpToDateState.(TaskUpToDateState.java:55)
at
org.gradle.api.internal.changedetection.changes.DefaultTaskArtifactStateRepository$TaskArtifactStateImpl.getStates(DefaultTaskArtifactStateRepository.java:164)
at
org.gradle.api.internal.changedetection.changes.DefaultTaskArtifactStateRepository$TaskArtifactStateImpl.isUpToDate(DefaultTaskArtifactStateRepository.java:79)
at
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:51)
at
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)
at
org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:46)
at
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:51)
at
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at
org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.execute(DefaultTaskGraphExecuter.java:236)
at
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.execute(DefaultTaskGr

Bug#900615: Bug #900615 in libpostgresql-jdbc-java marked as pending

[myon]

Control: tag -1 pending

Hello,

Bug #900615 in libpostgresql-jdbc-java reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/java-team/libpostgresql-jdbc-java/commit/ee6082d017b30bcb79993ad4083e4b9360596045


pgjdbc/pom.xml: Manually patch scram dependency scope to be "provided" instead 
of relying on maven.rules. (Closes: #900615, induced by #900763, thanks 
Emmanuel Bourg.)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/900615

Processed: Bug #900615 in libpostgresql-jdbc-java marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #900615 [src:libpgjava] libpostgresql-jdbc-java: no Depends on libscram-java
Added tag(s) pending.

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

Processed: numpy boolean subtract, the `-` operator, is deprecated, use the bitwise_xor, the `^` operator, or the logical_xor function instead (Was: Bug#899205: python-cogent: Test suite fails with la

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #899205 [python-cogent] python-cogent: Test suite fails with latest 
matplotlib
Added tag(s) help.

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

Bug#899205: numpy boolean subtract, the `-` operator, is deprecated, use the bitwise_xor, the `^` operator, or the logical_xor function instead (Was: Bug#899205: python-cogent: Test suite fails with l

[Andreas Tille]

Control: tags -1 help

Hi,

I have reported the issue upstream but no response so far.  While the
error message contains some hint how to solve the issue I would like
to backup this by some competent advise.


==
ERROR: test_consistent_gap_degen_handling 
(test_core.test_sequence.ModelSequenceTests)
gap degen character should be treated consistently
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.5a99fnj6/downtmp/autopkgtest_tmp/tests/test_core/test_sequence.py",
 line 660, in test_consistent_gap_degen_handling
self.assertEqual(dna.stripBadAndGaps(), raw_ungapped)
  File "/usr/lib/python2.7/dist-packages/cogent/core/sequence.py", line 1251, 
in stripBadAndGaps
valid_indices -= self._data == i
TypeError: numpy boolean subtract, the `-` operator, is deprecated, use the 
bitwise_xor, the `^` operator, or the logical_xor function instead.

==


I would be happy for some suggested patch how to solve this.  The line
in question is

   
https://salsa.debian.org/med-team/python-cogent/blob/master/cogent/core/sequence.py

   Line 1251

If my feeling is not totally wrong the correct patch would be 

   valid_indices -= (self._data == i)

since the left value is rather an integer than boolean.

What do you think?

Kind regards

Andreas.

-- 
http://fam-tille.de