Processed: reassign 912817 to libasound2-plugins, forcibly merging 912680 912817

[Debian Bug Tracking System]

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

> reassign 912817 libasound2-plugins
Bug #912817 [alsa-utils] ALSA lib conf.c:4013:(snd_config_update_r) hooks 
failed, removing configuration
Bug reassigned from package 'alsa-utils' to 'libasound2-plugins'.
No longer marked as found in versions alsa-utils/1.1.7-1.
Ignoring request to alter fixed versions of bug #912817 to the same values 
previously set
> forcemerge 912680 912817
Bug #912680 {Done: Elimar Riesebieter } [libasound2-plugins] 
libasound2-plugins: broken symlinks in /etc/alsa/conf.d
Bug #912721 {Done: Elimar Riesebieter } [libasound2-plugins] 
libasound2-plugins: Sound no longer works after latest update
Bug #912726 {Done: Elimar Riesebieter } [libasound2-plugins] 
alsa-lib: update created /etc/alsa/conf.d directory filled with broken symlinks 
to /usr/share/alsa/alsa.conf.d
Bug #912755 {Done: Elimar Riesebieter } [libasound2-plugins] 
cannot access file /etc/alsa/conf.d/10-rate-lav.conf
Bug #912763 {Done: Elimar Riesebieter } [libasound2-plugins] 
libasound2: Total loss of sound on Debian Sid with Intel sound
Bug #912766 {Done: Elimar Riesebieter } [libasound2-plugins] 
alsa-utils: Dummy outupt after update
Bug #912817 [libasound2-plugins] ALSA lib conf.c:4013:(snd_config_update_r) 
hooks failed, removing configuration
Marked Bug as done
Marked as fixed in versions alsa-plugins/1.1.7-2.
Marked as found in versions alsa-plugins/1.1.7-1.
Bug #912721 {Done: Elimar Riesebieter } [libasound2-plugins] 
libasound2-plugins: Sound no longer works after latest update
Bug #912726 {Done: Elimar Riesebieter } [libasound2-plugins] 
alsa-lib: update created /etc/alsa/conf.d directory filled with broken symlinks 
to /usr/share/alsa/alsa.conf.d
Bug #912755 {Done: Elimar Riesebieter } [libasound2-plugins] 
cannot access file /etc/alsa/conf.d/10-rate-lav.conf
Bug #912763 {Done: Elimar Riesebieter } [libasound2-plugins] 
libasound2: Total loss of sound on Debian Sid with Intel sound
Bug #912766 {Done: Elimar Riesebieter } [libasound2-plugins] 
alsa-utils: Dummy outupt after update
Merged 912680 912721 912726 912755 912763 912766 912817
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
912680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912680
912721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912721
912726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912726
912755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912755
912763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912763
912766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912766
912817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Samuel Thibault, le lun. 29 oct. 2018 01:01:34 +0100, a ecrit:
> I looked deeper in fs.py, and I found that in the succeeding
> case, the main loop inside share_files sees _sphinbase.so before
> _sphinxbase.so.0.0.0, and thus renames it, and in the failing case, that
> loop sees _sphinxbase.so.0.0.0 before _sphinxbase.so.0, and when it
> looks at _sphinxbase.so.0, exits() fails, because the target was moved,
> and thus the symlink is now broken.

Interestingly enough, this is caught by the reproducible build test, as
currently seen on

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/diffoscope-results/sphinxbase.html

Samuel

Processed (with 1 error): forcibly merging 912680 912817

[Debian Bug Tracking System]

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

> forcemerge 912680 912817
Bug #912680 {Done: Elimar Riesebieter } [libasound2-plugins] 
libasound2-plugins: broken symlinks in /etc/alsa/conf.d
Bug #912721 {Done: Elimar Riesebieter } [libasound2-plugins] 
libasound2-plugins: Sound no longer works after latest update
Bug #912726 {Done: Elimar Riesebieter } [libasound2-plugins] 
alsa-lib: update created /etc/alsa/conf.d directory filled with broken symlinks 
to /usr/share/alsa/alsa.conf.d
Bug #912755 {Done: Elimar Riesebieter } [libasound2-plugins] 
cannot access file /etc/alsa/conf.d/10-rate-lav.conf
Bug #912763 {Done: Elimar Riesebieter } [libasound2-plugins] 
libasound2: Total loss of sound on Debian Sid with Intel sound
Bug #912766 {Done: Elimar Riesebieter } [libasound2-plugins] 
alsa-utils: Dummy outupt after update
Unable to merge bugs because:
package of #912817 is 'alsa-utils' not 'libasound2-plugins'
Failed to forcibly merge 912680: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
912680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912680
912721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912721
912726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912726
912755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912755
912763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912763
912766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912766
912817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840305: libatteanx-store-memorytriplestore-perl: depends on unavailable AtteanX::RDFQueryTranslator

[Jonas Smedegaard]

Quoting intrigeri (2018-11-03 12:50:42)
> Dear Jonas,
> 
> gregor herrmann:
> > On Mon, 10 Oct 2016 14:42:29 +0200, Andreas Beckmann wrote:
> >> Can't locate AtteanX/RDFQueryTranslator.pm in @INC (you may need to 
> >> install the AtteanX::RDFQueryTranslator module) (@INC contains: 
> >> /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl 
> >> /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
> >> /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
> >> /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
> >> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
> >> t/planning.t line 12,  line 1.
> 
> > AtteanX/RDFQueryTranslator.pm was in libattean-perl but according to
> > its d/changelog:
> 
> > + Remove AtteanX::RDFQueryTranslator (split into a new package) and
> >   all other references to RDF::Query.
> 
> > So someone would need to package the now separate
> > AtteanX::RDFQueryTranslator.
> 
> This package has only been available in experimental since its initial
> (and last) batch of uploads three years ago. Its popcon is 1. It has
> started to FTBFS two years ago. So you won't be astonished that it
> popped up on my "candidate for removal" radar. But it's mostly
> harmless so there's of course no hurry :)  Still:
> 
> Is it still useful to keep this package in the archive, albeit in
> experimental only? Are you still interested in working on this and
> perhaps upload the missing dependency? If not, I propose we remove it
> from the archive; happy to deal with the paperwork myself (except
> moving to "attic" or whatever it's called in the Salsa days, which
> I've consistently forgotten).

Please drop it.  Thanks!


 - Jonas

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

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


signature.asc
Description: signature

Bug#912817: ALSA lib conf.c:4013:(snd_config_update_r) hooks failed, removing configuration

[積丹尼 Dan Jacobson]

Package: alsa-utils
Version: 1.1.7-1
Severity: grave

$ alsamixer
ALSA lib conf.c:3639:(config_file_open) cannot access file 
/etc/alsa/conf.d/10-rate-lav.conf
ALSA lib conf.c:3559:(snd_config_hooks_call) function snd_config_hook_load 
returned error: No such file or directory
ALSA lib conf.c:4013:(snd_config_update_r) hooks failed, removing configuration
cannot open mixer: No such file or directory

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

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 23:25:24 +
with message-id 
and subject line Bug#899543: fixed in ibus-kkc 1.5.22-2
has caused the Debian Bug report #899543,
regarding ibus-kkc: 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.)


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

Dear uploader of ibus-kkc,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package ibus-kkc 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-kkc
Source-Version: 1.5.22-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 18:35:36 -0400
Source: ibus-kkc
Binary: ibus-kkc
Architecture: source
Version: 1.5.22-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 ibus-kkc   - Japanese Kana Kanji input engine for IBus
Closes: 899543
Changes:
 ibus-kkc (1.5.22-2) unstable; urgency=medium
 .
   * Team upload.
   * debian: Modernize packaging.
 + Apply "wrap-and-sort -abst".
   * debian/control:
 + Set maintainer to Debian Input Method Team (Closes: #899543).
 + Bump debhelper compat to v11.
 + Bump Standards-Version to 4.2.1.
 + Update Vcs-* fields and use git repo under Salsa Debian Input
   Method Team group.
 + Drop -dbg package in favour of -dbgsym automatic debug package.
   * debian/copyright:
 + Use secure uri for Format: field.
   * debian/rules: Use "dh_missing --fail-missing".
   * debian/install: Removed, not needed with single binary package.
Checksums-Sha1:
 0ede9764ae71f82f7b9eceb4c9b1584baa60eeb2 2072 ibus-kkc_1.5.22-2.dsc
 9c1284b4c29ff88c9fb0a3eec657d34af979c953 4464 ibus-kkc_1.5.22-2.debian.tar.xz
 44119abf74267dfd40c4d61889a05149b4ec276e 15005 
ibus-kkc_1.5.22-2_amd64.buildinfo
Checksums-Sha256:
 

Bug#912726: marked as done (alsa-lib: update created /etc/alsa/conf.d directory filled with broken symlinks to /usr/share/alsa/alsa.conf.d)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 23:19:40 +
with message-id 
and subject line Bug#912721: fixed in alsa-plugins 1.1.7-2
has caused the Debian Bug report #912721,
regarding alsa-lib: update created /etc/alsa/conf.d directory filled with 
broken symlinks to /usr/share/alsa/alsa.conf.d
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.)


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

Dear Maintainer,
I had noticed I upgraded my laptop and I was trying to bug test why my audio
stopped working (i got a dummy input), googling did not help. I decided to
check the /etc/alsa folder for clues. i found /etc/alsa/conf.d filled with
symlinks and checked a few, they all led to /usr/share/alsa/alsa.conf.d files
that did not exist (that folder only contains pulse.conf, which strangly is not
referenced at all, not even by the similar 50-pulseaudio.conf)

i have to assume by mistake that /usr/share/alsa/alsa.conf.d was not populated.
I know /etc/alsa/conf.d folder had not existed prior by testing this with my
desktop PC, also running sid, checking both folders prior to upgrading, and
then upgrading. suddenly i have an /etc/alsa/conf.d folder filled with broken
symlinks.

as a temporary fix, deleting these symlinks restores functionality.




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

Kernel: Linux 4.18.0-2-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: alsa-plugins
Source-Version: 1.1.7-2

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

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

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

Debian distribution maintenance software
pp.
Elimar Riesebieter  (supplier of updated alsa-plugins 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 12:22:24 +0100
Source: alsa-plugins
Binary: libasound2-plugins
Architecture: source
Version: 1.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ALSA Maintainers 
Changed-By: Elimar Riesebieter 
Description:
 libasound2-plugins - ALSA library additional plugins
Closes: 912721
Changes:
 alsa-plugins (1.1.7-2) unstable; urgency=medium
 .
   * Install conf files in /u/s/a/conf.d (Closes: #912721)
Checksums-Sha1:
 26c04cf524f48a4a0f0af40cebcb4f25da88ce7c 2295 alsa-plugins_1.1.7-2.dsc
 6ca1649643ed4287f105e1bbfe677950b85dc1fe 8064 
alsa-plugins_1.1.7-2.debian.tar.xz
 bd946cba35ac11a2134d2b7a879e542a6589368b 6882 
alsa-plugins_1.1.7-2_source.buildinfo
Checksums-Sha256:
 14dfff529870739c20ff70943e98fb9faa17ce398cf4b022c31b507e8f0ef463 2295 
alsa-plugins_1.1.7-2.dsc
 a092a38e47c916d1dd721771696eb371c8936833a22b80a2b2530d483e976c42 8064 
alsa-plugins_1.1.7-2.debian.tar.xz
 871f7210628ed2ef00e5e5d753a0c6d09f46af724fa3b01d6fa297701485f878 6882 
alsa-plugins_1.1.7-2_source.buildinfo
Files:
 4bd1619a0a99aac10fe076245fcae3f2 2295 libs optional alsa-plugins_1.1.7-2.dsc
 0a9815eae7039be7f790851e9b3d57d2 8064 libs optional 
alsa-plugins_1.1.7-2.debian.tar.xz
 cb038a10248192dcddbfa0084171a186 6882 libs optional 
alsa-plugins_1.1.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAlveJLcSHGpvcmRpQG1h
bGxhY2gubmV0AAoJECVQL2/L48sExkQQAK6xth6d9ki0HxwbfEHAMTrnomlWVDKv
+jiELh1uFNJgl3PiYkJo234fZppyN34MYneNDdJ5weMBsh3aSCdOgteBf6BbX1kb
vr3B9sm/CzdxJCwC6hy/JX07HPUZHPsLV6czxbYrpGUe+WWnSUZwELV+QmSHTcwQ
bxb2ZQ0cPlJjBPtDvOvuXgDxrY7T6gLBPW6pShCjPxiEp0/2tInaT75gPqef9Tm3
jsXogUtChiI5Frb+AVn+PwLI6xw/ecaS9o7URmndr+bMksYPD7XlSp59wpztMkiE
QylGFsy+msa5H7Mx5vqlDS72Q7TjOaXcXBNvGyxvK/WuLav1lFKXrSnJ5g70ZwjE
c4oHo4z493Xv5kPruFBuqAX8kiRg50uJx3vRbzyQRh4Kh1dFf6ipbyabgBjk4jmj
H4K67wVyy+aVLvsd+O2s2X0c42vo9+MuTD8DQ740pXLLdSe+SbOOmUgyQFoOriYY

Bug#912680: marked as done (libasound2-plugins: broken symlinks in /etc/alsa/conf.d)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 23:19:40 +
with message-id 
and subject line Bug#912721: fixed in alsa-plugins 1.1.7-2
has caused the Debian Bug report #912721,
regarding libasound2-plugins: broken symlinks in /etc/alsa/conf.d
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.)


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

Dear Maintainer,

I lost a symlink today (I don’t know how or why).

> pulseaudio -D gives:
nov. 02 20:14:19 nicolas.home pulseaudio[13754]: Failed to find a working
profile.
nov. 02 20:14:19 nicolas.home pulseaudio[13754]: Failed to load module "module-
alsa-card" (argument: "device_id="1" name="pci-_01_00.1"
card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes
fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes
card_properties="module-udev-detect.discovered=1""): initialization failed.
nov. 02 20:14:19 nicolas.home pulseaudio[13754]: Failed to find a working
profile.
nov. 02 20:14:19 nicolas.home pulseaudio[13754]: Failed to load module "module-
alsa-card" (argument: "device_id="0" name="pci-_00_14.2"
card_name="alsa_card.pci-_00_14.2" namereg_fail=false tsched=yes
fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes
card_properties="module-udev-detect.discovered=1""): initialization failed.
nov. 02 20:14:19 nicolas.home pulseaudio[13754]: Failed to register as a
handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown:
The name org.ofono was not provided by any .service files

As root, service alsa status gives:
● alsa-utils.service
   Loaded: masked (Reason: Unit alsa-utils.service is masked.)
   Active: inactive (dead)

I can’t unmask the service even with the right command to systemctl and I found
that there is no alsa directory in /etc/systemd/system/.
In fact, when I try to launch alsamixer:
> alsamixer
ALSA lib conf.c:3639:(config_file_open) cannot access file
/etc/alsa/conf.d/10-rate-lav.conf
ALSA lib conf.c:3559:(snd_config_hooks_call) function snd_config_hook_load
returned error: Aucun fichier ou dossier de ce type
ALSA lib conf.c:4013:(snd_config_update_r) hooks failed, removing configuration
le mixeur ne peut pas être ouvert: Aucun fichier ou dossier de ce type

/etc/alsa/conf.d/10-rate-lav.conf is a broken symlink to
/usr/share/alsa/alsa.conf.d/10-rate-lav.conf.
It seems that even if it’s a pulseaudio issue because this file is not from
alsa.
In fact, I was not able to find precisely from which package this file comes
from.

Moreover, in Audacious:
* The pulseaudio output accepts to play but the output is dummy (no sound
plays, the vumeter works).
* The alsa output simply crashes (ALSA error: snd_pcm_open failed: No such file
or directory.)
* The OSS3 output works fine but with a crack on startup.
* The SDL output does as pulseaudio.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

Kernel: Linux 4.17.0-3-686-pae (SMP w/3 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  libasound2   1.1.7-1
ii  libasound2-plugins   1:1.1.7-dmo1
ii  libc62.27-8
ii  libcap2  1:2.25-1.2
ii  libdbus-1-3  1.12.10-1
ii  libgcc1  1:8.2.0-9
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-6
ii  liborc-0.4-0 1:0.4.28-3
ii  libpulse012.2-2
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.28-4
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   8.2.0-9
ii  libsystemd0  239-11
ii  libtdb1  1.3.16-1
ii  libudev1 239-11
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20170808
ii  pulseaudio-utils 12.2-2

Versions of packages pulseaudio 

Bug#912721: marked as done (libasound2-plugins: Sound no longer works after latest update)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 23:19:40 +
with message-id 
and subject line Bug#912721: fixed in alsa-plugins 1.1.7-2
has caused the Debian Bug report #912721,
regarding libasound2-plugins: Sound no longer works after latest update
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.)


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

After updating to the latest version of libasound2-plugins, sound on
my system stopped working. Trying to start `alsamixer' failed as well
with the following error message:

ALSA lib conf.c:3639:(config_file_open) cannot access file
/etc/alsa/conf.d/10-rate-lav.conf

It turns out that libasound2-plugins installs broken symlinks in
/etc/alsa/conf.d. All symlinks installed by libasound2-plugins in
/etc/alsa/conf.d are broken, because the corresponding files in
/usr/share/alsa/alsa.conf.d do not exist.

Best regards,
Matthias

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: alsa-plugins
Source-Version: 1.1.7-2

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

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

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

Debian distribution maintenance software
pp.
Elimar Riesebieter  (supplier of updated alsa-plugins 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 12:22:24 +0100
Source: alsa-plugins
Binary: libasound2-plugins
Architecture: source
Version: 1.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ALSA Maintainers 
Changed-By: Elimar Riesebieter 
Description:
 libasound2-plugins - ALSA library additional plugins
Closes: 912721
Changes:
 alsa-plugins (1.1.7-2) unstable; urgency=medium
 .
   * Install conf files in /u/s/a/conf.d (Closes: #912721)
Checksums-Sha1:
 26c04cf524f48a4a0f0af40cebcb4f25da88ce7c 2295 alsa-plugins_1.1.7-2.dsc
 6ca1649643ed4287f105e1bbfe677950b85dc1fe 8064 
alsa-plugins_1.1.7-2.debian.tar.xz
 bd946cba35ac11a2134d2b7a879e542a6589368b 6882 
alsa-plugins_1.1.7-2_source.buildinfo
Checksums-Sha256:
 14dfff529870739c20ff70943e98fb9faa17ce398cf4b022c31b507e8f0ef463 2295 
alsa-plugins_1.1.7-2.dsc
 a092a38e47c916d1dd721771696eb371c8936833a22b80a2b2530d483e976c42 8064 
alsa-plugins_1.1.7-2.debian.tar.xz
 871f7210628ed2ef00e5e5d753a0c6d09f46af724fa3b01d6fa297701485f878 6882 
alsa-plugins_1.1.7-2_source.buildinfo
Files:
 4bd1619a0a99aac10fe076245fcae3f2 2295 libs optional alsa-plugins_1.1.7-2.dsc
 0a9815eae7039be7f790851e9b3d57d2 8064 libs optional 
alsa-plugins_1.1.7-2.debian.tar.xz
 cb038a10248192dcddbfa0084171a186 6882 libs optional 
alsa-plugins_1.1.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAlveJLcSHGpvcmRpQG1h
bGxhY2gubmV0AAoJECVQL2/L48sExkQQAK6xth6d9ki0HxwbfEHAMTrnomlWVDKv
+jiELh1uFNJgl3PiYkJo234fZppyN34MYneNDdJ5weMBsh3aSCdOgteBf6BbX1kb
vr3B9sm/CzdxJCwC6hy/JX07HPUZHPsLV6czxbYrpGUe+WWnSUZwELV+QmSHTcwQ
bxb2ZQ0cPlJjBPtDvOvuXgDxrY7T6gLBPW6pShCjPxiEp0/2tInaT75gPqef9Tm3
jsXogUtChiI5Frb+AVn+PwLI6xw/ecaS9o7URmndr+bMksYPD7XlSp59wpztMkiE
QylGFsy+msa5H7Mx5vqlDS72Q7TjOaXcXBNvGyxvK/WuLav1lFKXrSnJ5g70ZwjE
c4oHo4z493Xv5kPruFBuqAX8kiRg50uJx3vRbzyQRh4Kh1dFf6ipbyabgBjk4jmj
H4K67wVyy+aVLvsd+O2s2X0c42vo9+MuTD8DQ740pXLLdSe+SbOOmUgyQFoOriYY
H09onuo9qSAZ2wlz24ajVRsVPovYawvCrsNl2Yw8M2sU3x4KthHR7EKOGlLyIuvG
ZlM9vywi3EKO1hdj9IQ5LFIsmfcycAg4eaG4qGRhOeZdR4CfNczEVjJaFSTXuvdm
t9jr+tsK613eyi/NoKIo4oJaDGuwxyIsQyXZITO31OF3KYC9p+a1wNX1zbE08nbP
P+RU4bOROBGM
=uUx5
-END PGP SIGNATURE End Message ---

Bug#912755: marked as done (cannot access file /etc/alsa/conf.d/10-rate-lav.conf)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 23:19:40 +
with message-id 
and subject line Bug#912721: fixed in alsa-plugins 1.1.7-2
has caused the Debian Bug report #912721,
regarding cannot access file /etc/alsa/conf.d/10-rate-lav.conf
to be marked as done.

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

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


-- 
912721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alsa-utils
Version: 1.1.7-1
Severity: important

Hello, when I run alsamixer, I get this error message

$ LANG=C alsamixer
ALSA lib conf.c:3639:(config_file_open) cannot access file 
/etc/alsa/conf.d/10-rate-lav.conf
ALSA lib conf.c:3559:(snd_config_hooks_call) function snd_config_hook_load 
returned error: No such file or directory
ALSA lib conf.c:4013:(snd_config_update_r) hooks failed, removing configuration
cannot open mixer: No such file or directory


I looked at the /etc files and it seems that there is a bunch of broken links

$ cd /etc/alsa/conf.d/
:/etc/alsa/conf.d$ ls -l
total 4
lrwxrwxrwx 1 root root  44 nov.   3 00:35 10-rate-lav.conf -> 
/usr/share/alsa/alsa.conf.d/10-rate-lav.conf
lrwxrwxrwx 1 root root  46 nov.   3 00:35 10-samplerate.conf -> 
/usr/share/alsa/alsa.conf.d/10-samplerate.conf
lrwxrwxrwx 1 root root  45 nov.   3 00:35 10-speexrate.conf -> 
/usr/share/alsa/alsa.conf.d/10-speexrate.conf
lrwxrwxrwx 1 root root  48 nov.   3 00:35 50-arcam-av-ctl.conf -> 
/usr/share/alsa/alsa.conf.d/50-arcam-av-ctl.conf
lrwxrwxrwx 1 root root  40 nov.   3 00:35 50-jack.conf -> 
/usr/share/alsa/alsa.conf.d/50-jack.conf
lrwxrwxrwx 1 root root  39 nov.   3 00:35 50-oss.conf -> 
/usr/share/alsa/alsa.conf.d/50-oss.conf
lrwxrwxrwx 1 root root  46 nov.   3 00:35 50-pulseaudio.conf -> 
/usr/share/alsa/alsa.conf.d/50-pulseaudio.conf
lrwxrwxrwx 1 root root  47 nov.   3 00:35 60-a52-encoder.conf -> 
/usr/share/alsa/alsa.conf.d/60-a52-encoder.conf
lrwxrwxrwx 1 root root  41 nov.   3 00:35 60-upmix.conf -> 
/usr/share/alsa/alsa.conf.d/60-upmix.conf
lrwxrwxrwx 1 root root  44 nov.   3 00:35 60-vdownmix.conf -> 
/usr/share/alsa/alsa.conf.d/60-vdownmix.conf
lrwxrwxrwx 1 root root  46 nov.   3 00:35 98-usb-stream.conf -> 
/usr/share/alsa/alsa.conf.d/98-usb-stream.conf
-rw-r--r-- 1 root root 201 nov.   3 00:35 99-pulseaudio-default.conf.example


all but 99 are broken

And Indeed I have no sound.

cheers


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

Kernel: Linux 4.18.0-2-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages alsa-utils depends on:
ii  dialog1.3-20181022-1
ii  kmod  25-1
ii  libasound21.1.7-1
ii  libc6 2.27-8
ii  libfftw3-single3  3.3.8-2
ii  libncursesw6  6.1+20181013-1
ii  libsamplerate00.1.9-2
ii  libtinfo6 6.1+20181013-1
ii  lsb-base  9.20170808
ii  whiptail  0.52.20-8

alsa-utils recommends no packages.

alsa-utils suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: alsa-plugins
Source-Version: 1.1.7-2

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

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

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

Debian distribution maintenance software
pp.
Elimar Riesebieter  (supplier of updated alsa-plugins 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 12:22:24 +0100
Source: alsa-plugins
Binary: libasound2-plugins
Architecture: source
Version: 1.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ALSA Maintainers 
Changed-By: Elimar Riesebieter 
Description:
 libasound2-plugins - ALSA library additional plugins
Closes: 912721
Changes:
 alsa-plugins (1.1.7-2) unstable; urgency=medium
 .
   * Install conf files in /u/s/a/conf.d (Closes: #912721)
Checksums-Sha1:
 

Bug#912763: marked as done (libasound2: Total loss of sound on Debian Sid with Intel sound)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 23:19:40 +
with message-id 
and subject line Bug#912721: fixed in alsa-plugins 1.1.7-2
has caused the Debian Bug report #912721,
regarding libasound2: Total loss of sound on Debian Sid with Intel sound
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.)


-- 
912721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libasound2
Version: 1.1.7-1
Severity: normal

Dear Maintainer,

After libasound2 and libasound2-data were updated on my Sid installation, I
suffered a total loss of sound.





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

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

Versions of packages libasound2 depends on:
ii  libasound2-data  1.1.7-1
ii  libc62.27-8

libasound2 recommends no packages.

Versions of packages libasound2 suggests:
ii  libasound2-plugins  1.1.7-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: alsa-plugins
Source-Version: 1.1.7-2

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

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

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

Debian distribution maintenance software
pp.
Elimar Riesebieter  (supplier of updated alsa-plugins 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 12:22:24 +0100
Source: alsa-plugins
Binary: libasound2-plugins
Architecture: source
Version: 1.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ALSA Maintainers 
Changed-By: Elimar Riesebieter 
Description:
 libasound2-plugins - ALSA library additional plugins
Closes: 912721
Changes:
 alsa-plugins (1.1.7-2) unstable; urgency=medium
 .
   * Install conf files in /u/s/a/conf.d (Closes: #912721)
Checksums-Sha1:
 26c04cf524f48a4a0f0af40cebcb4f25da88ce7c 2295 alsa-plugins_1.1.7-2.dsc
 6ca1649643ed4287f105e1bbfe677950b85dc1fe 8064 
alsa-plugins_1.1.7-2.debian.tar.xz
 bd946cba35ac11a2134d2b7a879e542a6589368b 6882 
alsa-plugins_1.1.7-2_source.buildinfo
Checksums-Sha256:
 14dfff529870739c20ff70943e98fb9faa17ce398cf4b022c31b507e8f0ef463 2295 
alsa-plugins_1.1.7-2.dsc
 a092a38e47c916d1dd721771696eb371c8936833a22b80a2b2530d483e976c42 8064 
alsa-plugins_1.1.7-2.debian.tar.xz
 871f7210628ed2ef00e5e5d753a0c6d09f46af724fa3b01d6fa297701485f878 6882 
alsa-plugins_1.1.7-2_source.buildinfo
Files:
 4bd1619a0a99aac10fe076245fcae3f2 2295 libs optional alsa-plugins_1.1.7-2.dsc
 0a9815eae7039be7f790851e9b3d57d2 8064 libs optional 
alsa-plugins_1.1.7-2.debian.tar.xz
 cb038a10248192dcddbfa0084171a186 6882 libs optional 
alsa-plugins_1.1.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAlveJLcSHGpvcmRpQG1h
bGxhY2gubmV0AAoJECVQL2/L48sExkQQAK6xth6d9ki0HxwbfEHAMTrnomlWVDKv
+jiELh1uFNJgl3PiYkJo234fZppyN34MYneNDdJ5weMBsh3aSCdOgteBf6BbX1kb
vr3B9sm/CzdxJCwC6hy/JX07HPUZHPsLV6czxbYrpGUe+WWnSUZwELV+QmSHTcwQ
bxb2ZQ0cPlJjBPtDvOvuXgDxrY7T6gLBPW6pShCjPxiEp0/2tInaT75gPqef9Tm3
jsXogUtChiI5Frb+AVn+PwLI6xw/ecaS9o7URmndr+bMksYPD7XlSp59wpztMkiE
QylGFsy+msa5H7Mx5vqlDS72Q7TjOaXcXBNvGyxvK/WuLav1lFKXrSnJ5g70ZwjE
c4oHo4z493Xv5kPruFBuqAX8kiRg50uJx3vRbzyQRh4Kh1dFf6ipbyabgBjk4jmj
H4K67wVyy+aVLvsd+O2s2X0c42vo9+MuTD8DQ740pXLLdSe+SbOOmUgyQFoOriYY
H09onuo9qSAZ2wlz24ajVRsVPovYawvCrsNl2Yw8M2sU3x4KthHR7EKOGlLyIuvG
ZlM9vywi3EKO1hdj9IQ5LFIsmfcycAg4eaG4qGRhOeZdR4CfNczEVjJaFSTXuvdm
t9jr+tsK613eyi/NoKIo4oJaDGuwxyIsQyXZITO31OF3KYC9p+a1wNX1zbE08nbP
P+RU4bOROBGM
=uUx5
-END PGP SIGNATURE End Message ---

Bug#912766: marked as done (alsa-utils: Dummy outupt after update)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 23:19:40 +
with message-id 
and subject line Bug#912721: fixed in alsa-plugins 1.1.7-2
has caused the Debian Bug report #912721,
regarding alsa-utils: Dummy outupt after update
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.)


-- 
912721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alsa-utils
Version: 1.1.7-1
Severity: important

Dear Maintainer,

I updated the alsa-utils and i did its reboot.
After this, the speakers not make sound and in the configuration, it says that 
sound card is dummy output.
inserting the alsactl init command:

ALSA lib conf.c:3639:(config_file_open) cannot access file 
/etc/alsa/conf.d/10-rate-lav.conf
ALSA lib conf.c:3559:(snd_config_hooks_call) function snd_config_hook_load 
returned error: No such file or directory
ALSA lib conf.c:4013:(snd_config_update_r) hooks failed, removing configuration

I have a Realtek onboard sound card, but only appears the Intel CPU sound card.

Regardds.

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

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

Versions of packages alsa-utils depends on:
ii  kmod  25-1
ii  libasound21.1.7-1
ii  libc6 2.27-8
ii  libfftw3-single3  3.3.8-2
ii  libncursesw6  6.1+20181013-1
ii  libsamplerate00.1.9-2
ii  libtinfo6 6.1+20181013-1
ii  lsb-base  9.20170808
ii  whiptail  0.52.20-8

alsa-utils recommends no packages.

alsa-utils suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: alsa-plugins
Source-Version: 1.1.7-2

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

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

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

Debian distribution maintenance software
pp.
Elimar Riesebieter  (supplier of updated alsa-plugins 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 12:22:24 +0100
Source: alsa-plugins
Binary: libasound2-plugins
Architecture: source
Version: 1.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ALSA Maintainers 
Changed-By: Elimar Riesebieter 
Description:
 libasound2-plugins - ALSA library additional plugins
Closes: 912721
Changes:
 alsa-plugins (1.1.7-2) unstable; urgency=medium
 .
   * Install conf files in /u/s/a/conf.d (Closes: #912721)
Checksums-Sha1:
 26c04cf524f48a4a0f0af40cebcb4f25da88ce7c 2295 alsa-plugins_1.1.7-2.dsc
 6ca1649643ed4287f105e1bbfe677950b85dc1fe 8064 
alsa-plugins_1.1.7-2.debian.tar.xz
 bd946cba35ac11a2134d2b7a879e542a6589368b 6882 
alsa-plugins_1.1.7-2_source.buildinfo
Checksums-Sha256:
 14dfff529870739c20ff70943e98fb9faa17ce398cf4b022c31b507e8f0ef463 2295 
alsa-plugins_1.1.7-2.dsc
 a092a38e47c916d1dd721771696eb371c8936833a22b80a2b2530d483e976c42 8064 
alsa-plugins_1.1.7-2.debian.tar.xz
 871f7210628ed2ef00e5e5d753a0c6d09f46af724fa3b01d6fa297701485f878 6882 
alsa-plugins_1.1.7-2_source.buildinfo
Files:
 4bd1619a0a99aac10fe076245fcae3f2 2295 libs optional alsa-plugins_1.1.7-2.dsc
 0a9815eae7039be7f790851e9b3d57d2 8064 libs optional 
alsa-plugins_1.1.7-2.debian.tar.xz
 cb038a10248192dcddbfa0084171a186 6882 libs optional 
alsa-plugins_1.1.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAlveJLcSHGpvcmRpQG1h
bGxhY2gubmV0AAoJECVQL2/L48sExkQQAK6xth6d9ki0HxwbfEHAMTrnomlWVDKv
+jiELh1uFNJgl3PiYkJo234fZppyN34MYneNDdJ5weMBsh3aSCdOgteBf6BbX1kb
vr3B9sm/CzdxJCwC6hy/JX07HPUZHPsLV6czxbYrpGUe+WWnSUZwELV+QmSHTcwQ
bxb2ZQ0cPlJjBPtDvOvuXgDxrY7T6gLBPW6pShCjPxiEp0/2tInaT75gPqef9Tm3
jsXogUtChiI5Frb+AVn+PwLI6xw/ecaS9o7URmndr+bMksYPD7XlSp59wpztMkiE
QylGFsy+msa5H7Mx5vqlDS72Q7TjOaXcXBNvGyxvK/WuLav1lFKXrSnJ5g70ZwjE

Bug#912814: Messes up newsreader cache and history

[vitaminx]

Package: wallstreet
Version: 1.14-1
Severity: grave

I just installed this package out of curiosity and found that it messes up my 
newsreader's cache (I'm using newsbeuter).
All downloaded newsfeeds are completely gone and everything new appears as 
unread.

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

Kernel: Linux 4.18.0-2-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: sysvinit (via /sbin/init)

Versions of packages wallstreet depends on:
ii  byobu  5.112-1.1

Versions of packages wallstreet recommends:
pn  caca-utils  
ii  newsbeuter  2.9-8+b1
ii  python3 3.6.7-1
pn  rsstail 
pn  ticker  
ii  w3m 0.5.3-36+b1
ii  wget1.19.5-2

wallstreet suggests no packages.

-- no debconf information

Bug#909536: mozjs60: FTBFS on s390x: around 80% of tests crash

[Simon McVittie]

Control: severity -1 important

On Mon, 24 Sep 2018 at 21:18:47 +0100, Simon McVittie wrote:
> We can't upgrade gjs to a version that uses mozjs60 until either this is
> fixed somehow, or gjs and its dependencies (notably GNOME Shell) are
> removed from s390x. The architecture-specific removal seems a more likely
> short term solution; if this is done I'll downgrade this bug to important.

Doing so now.

smcv

Processed: Re: Bug#909536: mozjs60: FTBFS on s390x: around 80% of tests crash

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #909536 [src:mozjs60] mozjs60: FTBFS on s390x: around 80% of tests crash
Severity set to 'important' from 'serious'

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

Bug#912154: marked as done (repsnapper: build-depends on libvmmlib-dev, which is not in testing)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 23:02:51 +
with message-id 
and subject line Bug#912154: fixed in repsnapper 2.5a5-2
has caused the Debian Bug report #912154,
regarding repsnapper: build-depends on libvmmlib-dev, which is not in testing
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.)


-- 
912154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:repsnapper
version: 2.5a5-1
severity: serious

Hi,

Last year, vmmlib was removed from testing. As repsnapper build-depends on
libvmmlib-dev, this mean it can no longer be built in testing. If this is not
fixed, repsnapper will have to be removed from testing as well.

Please note that vmmlib currently FTBFS in unstable
(https://bugs.debian.org/834472) and also makes repsnapper FTBFS
(https://bugs.debian.org/897845).

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: repsnapper
Source-Version: 2.5a5-2

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

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

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated repsnapper 
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, 04 Nov 2018 02:23:28 +0800
Source: repsnapper
Binary: repsnapper
Architecture: source amd64
Version: 2.5a5-2
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 repsnapper - STL to GCode Converter and print software for RepRap machines
Closes: 885747 912154
Changes:
 repsnapper (2.5a5-2) unstable; urgency=low
 .
   * debian/control: Build-Depends on libpolyclipping-dev (Closes: #912154)
   * Add patches/0001-configure.ac-fix-detection-of-external-clipper-libra.patch
 - Detect libpolyclipping-dev correctly
   * Bump dh compat to 10.
 - fix debhelper-tools-from-autotools-dev-are-deprecated
 - remove unnecessary build dependencies
   * Add debian/patches/03_fix_appdata.patch to fix appdata format and path
   * Remove libpangox build dependencies. Use libpangomm. (Closes: #885747)
Checksums-Sha1:
 16719d820789ab019e7c273a385bfd09d6571be4 2014 repsnapper_2.5a5-2.dsc
 69d01fbf9c178932a9a2d4d82ed68cc1c08f49c7 9988 repsnapper_2.5a5-2.debian.tar.xz
 f87e5f28a57b0bc203469a1745f6e0adc11d5ff5 11127336 
repsnapper-dbgsym_2.5a5-2_amd64.deb
 03754a4ba7e0de8bcd65d797228bb078d55b1b21 14666 
repsnapper_2.5a5-2_amd64.buildinfo
 48489e5411a0202c0f78e5bff615ef3e8cd7ee41 704764 repsnapper_2.5a5-2_amd64.deb
Checksums-Sha256:
 d9340a687d15c7c3cf18bcb773dac2253d5338ffa8bdaa0cc7caf99217f90d8a 2014 
repsnapper_2.5a5-2.dsc
 8b4942f8257d29dcf45a29a92fbd7f665cd6526269942dd4fcc885a009662e10 9988 
repsnapper_2.5a5-2.debian.tar.xz
 4c38bf5efda4f53c1c71678ab558d5e603f8fba4ec4a40de3cb77ea4b7ca2065 11127336 
repsnapper-dbgsym_2.5a5-2_amd64.deb
 53a40f31f65beea188b2406abd3b2df6f8bf186f92c25705ceaac150edc8dcd4 14666 
repsnapper_2.5a5-2_amd64.buildinfo
 37b69b42ba98717addf3512ed49f873aa0924dfe77937874511d0b4c7414b17c 704764 
repsnapper_2.5a5-2_amd64.deb
Files:
 7194fb3ff109b143e66714eb1c41dba3 2014 utils optional repsnapper_2.5a5-2.dsc
 bf81ac9682d517c2f39f43b92919b248 9988 utils optional 
repsnapper_2.5a5-2.debian.tar.xz
 5c5c161a8964e5a70ff2b93eae2f7d6c 11127336 debug optional 
repsnapper-dbgsym_2.5a5-2_amd64.deb
 e58b3b8069fc8ac547849efb29279cae 14666 utils optional 
repsnapper_2.5a5-2_amd64.buildinfo
 16ae9ddbe4490ee8b5169e594e21ffac 704764 utils optional 
repsnapper_2.5a5-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAlveITATHHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiG99D/9aCtOcQNI6048rMt0OP1+hZk7R3T3f
8zJaCv7rGJ4AT/n5MaB6nLqdJlK5A04q8V5Lk3vlBSeuKj5broRWkrbR8Mx9YjQp
D4e0hTZFHdyTAGZyHKB3bNJDmMZnpP6MuPq+KCemQs9foEF5NFw0JQmg1TO/+MbP
hB5kYJN01UdOf2HptvidTHzJCJTvQ4QKZ5zqOUbIIsyVGFJvzJ4PTOgqMKQZ2as+
L0VQoBCrLDSlat6sBnE0hIfV68dOVbNQniJP/w6a3BKWlJr2mchRRZnc2+ldKUd5
A90yTllHAJqPv1G2k27HJqe+aEYftbmQ1p8isiVrNt1MFBChwmWSj99Mo+pz9Nxe
0kqXBRR3riSaUbJUHT4DLxQxVfUvODA1GkxwQBZmb1s90esvRiR5bFYylx75UngR

Bug#912394: marked as done (rsyntaxtextarea: FTBFS with Java 11 due to SecurityManager.checkSystemClipboardAccess() removal)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 23:02:59 +
with message-id 
and subject line Bug#912394: fixed in rsyntaxtextarea 2.5.8-1
has caused the Debian Bug report #912394,
regarding rsyntaxtextarea: FTBFS with Java 11 due to 
SecurityManager.checkSystemClipboardAccess() removal
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.)


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

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

...
[javac] 
/build/1st/rsyntaxtextarea-2.5.0/src/org/fife/ui/rsyntaxtextarea/RSyntaxTextArea.java:613:
 error: cannot find symbol
[javac] sm.checkSystemClipboardAccess();
[javac]   ^
[javac]   symbol:   method checkSystemClipboardAccess()
[javac]   location: variable sm of type SecurityManager
--- End Message ---
--- Begin Message ---
Source: rsyntaxtextarea
Source-Version: 2.5.8-1

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated rsyntaxtextarea package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 23:11:52 +0100
Source: rsyntaxtextarea
Binary: librsyntaxtextarea-java librsyntaxtextarea-java-doc
Architecture: source
Version: 2.5.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 librsyntaxtextarea-java - Java library for syntax highlighting text component
 librsyntaxtextarea-java-doc - Java library for syntax highlighting text 
component (documentatio
Closes: 912394
Changes:
 rsyntaxtextarea (2.5.8-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
 - Build with Gradle instead of Ant
   * Fixed the build failure with Java 11 (Closes: #912394)
   * Standards-Version updated to 4.2.1
   * Switch to debhelper level 11
   * Use salsa.debian.org Vcs-* URLs
   * Track and download the new releases from GitHub
Checksums-Sha1:
 80ba7a3c9b1fc6acebeb7fa2acf97030f0f32c19 2229 rsyntaxtextarea_2.5.8-1.dsc
 c55ebedf723aca5efcdde5031b74ee289f7bad76 1196809 
rsyntaxtextarea_2.5.8.orig.tar.gz
 eb916547e00bd754ef1b4ca293abe64b842d777b 3736 
rsyntaxtextarea_2.5.8-1.debian.tar.xz
 83f628f8cc15658bf2bba567d214ab3ca4e8c3ef 16617 
rsyntaxtextarea_2.5.8-1_source.buildinfo
Checksums-Sha256:
 886b33552ea34d27dc55aaf0fd7f2216e7341e30bed2d7b00f568f1e415bd802 2229 
rsyntaxtextarea_2.5.8-1.dsc
 df6430cf15bfcb7612b52d4c3b961c8b7bf0b848c7c251e6d405d2598484b698 1196809 
rsyntaxtextarea_2.5.8.orig.tar.gz
 fb5a154afff732f42a5672ea0289de0469f306b4affa00e680694fa103e00a1e 3736 
rsyntaxtextarea_2.5.8-1.debian.tar.xz
 6096c5c0b94f6054bafcf20697db9d7741732cd39cc871ea5159154d93a6f4e9 16617 
rsyntaxtextarea_2.5.8-1_source.buildinfo
Files:
 b8ab467dc57a957e5f5172d763e7363b 2229 java optional rsyntaxtextarea_2.5.8-1.dsc
 c6d123155aa9130df148f609f248c2e5 1196809 java optional 
rsyntaxtextarea_2.5.8.orig.tar.gz
 ff4bb0c85e1dc6f8859ea6fe30118298 3736 java optional 
rsyntaxtextarea_2.5.8-1.debian.tar.xz
 f3508e6b53f4e4870d16b8981d8ca7a8 16617 java optional 
rsyntaxtextarea_2.5.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlveHbwSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsr0EQAJO5h+vLifEsTX+7L6YyorWRvgcyscjQ
guZCzZHrZlTNI8yy054wGPVSMcD38F/OmBXbQA+EUsvv1UTHe3q1OmBpcVpMQrF9
UoGloBGB3sVwyf6BugDHgdRErkwSvFKB0bfYzB5vNaTXMM/ngL47VayVpVlF0Oe4
OAkJ0CGNh9OKIkTnz4AcWvITQGEXINrpC6fWlmzC50wcWhX1eJjAjSSPY2roVb/B
wfJYBwhFRvTL7RdWudiZEwbjNHXzWH8+0xB2sWduRdpNE9V1uDL+Tu5AeMCRRx4I
HCYzaU3qVdY/OAbSihXJQXIwQ/HbSFbqefTf6lqAOZVytYJ8Q+UxX4DlPMpNz9r3
k6MJ31jhI9NIC1EkHmwUQ9yO6TTJtqiJBJ0MCPpdwnvklbUfmQ1nsp4lrA6NvjZH
HYS4FSAMKsDjJhEpA3k2bl2SaK/tO3aovXh+eLlyfaj28/s2UP4j43pQuX+e+ngn
CJUSBDZhC6cWhe4TOlZ9kWFtEA/1N/CuRjbCmirSLMAYMilMxIoRDgvnF+yOgqM9

Bug#912394: Bug #912394 in rsyntaxtextarea marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #912394 in rsyntaxtextarea 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/rsyntaxtextarea/commit/4303425acf2308c9a61178b4877389971a19f538


Fixed the build failure with Java 11 (Closes: #912394)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912394

Processed: Bug #912394 in rsyntaxtextarea marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912394 [src:rsyntaxtextarea] rsyntaxtextarea: FTBFS with Java 11 due to 
SecurityManager.checkSystemClipboardAccess() removal
Added tag(s) pending.

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

Bug#912806: redmine: Could not find public_suffix error with current testing packages

[Soren Stoutner]

Package: redmine
Version: 3.4.6-1
Severity: grave
Justification: renders package unusable

After upgrading to the current packages in Debian testing, Redmine produces the 
following error in /var/log/apache2/error.log
every time a page is loaded:

[ 2018-11-03 01:08:23.2570 28268/7f74e1b3f700 
age/Cor/Con/CheckoutSession.cpp:285 ]: [Client 1-48] Cannot checkout session 
because a spawning error occurred.
The identifier of the error is 44685d16. Please see earlier logs for details 
about the error.
App 16470 stdout:
App 16470 stdout:
[ 2018-11-03 01:08:33.6710 28268/7f74d9779700 
age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application 
/usr/share/redmine:
An error occurred while starting up the preloader.
  Error ID: 1303ae00
  Error details saved to: /tmp/passenger-error-19WGeg.html
  Message from application: It looks like Bundler could not find a gem. 
Maybe you didn't install all the gems that this application needs.
To install your gems, please run:

  bundle install

If that didn't work, then the problem is probably caused by your application 
being run under a different environment than it's supposed to.
Please check the following:


  Is this app supposed to be run as the www-data user?
  Is this app being run on the correct Ruby interpreter? Below you will
  see which Ruby interpreter Phusion Passenger attempted to use.


 The exception is as follows: ---
Could not find public_suffix-2.0.5 in any of the sources (Bundler::GemNotFound)
  /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:88:in `block in 
materialize
  /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:82:in `map!
  /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:82:in `materialize
  /usr/lib/ruby/vendor_ruby/bundler/definition.rb:170:in `specs
  /usr/lib/ruby/vendor_ruby/bundler/definition.rb:237:in `specs_for
  /usr/lib/ruby/vendor_ruby/bundler/definition.rb:226:in `requested_specs
  /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:108:in `block in 
definition_method
  /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:20:in `setup
  /usr/lib/ruby/vendor_ruby/bundler.rb:107:in `setup
  /usr/lib/ruby/vendor_ruby/bundler/setup.rb:20:in `top (required)
  /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require
  /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require
  /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:430:in 
`activate_gem
  /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:297:in 
`block in run_load_path_setup_code
  /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:435:in 
`running_bundler
  /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:296:in 
`run_load_path_setup_code
  /usr/share/passenger/helper-scripts/rack-preloader.rb:100:in `preload_app
  /usr/share/passenger/helper-scripts/rack-preloader.rb:156:in 
`module:App
  /usr/share/passenger/helper-scripts/rack-preloader.rb:30:in 
`module:PhusionPassenger
  /usr/share/passenger/helper-scripts/rack-preloader.rb:29:in 
`main


Debian testing has ruby-public-suffix version 3.0.3+ds-1.  Redmine is looking 
for version 2.0.5.

2.0.5 can be manually installed by going to the /usr/share/redmine directory 
and running `sudo bundle install`.
But that isn't a good Debian solution because it directly downloads the gem 
file which will not be managed by apt-get for automatic update or removal.

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

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

Versions of packages redmine depends on:
ii  dbconfig-common 2.0.10
ii  debconf [debconf-2.0]   1.5.69
ii  libjs-raphael   2.1.0-1
ii  redmine-mysql   3.4.6-1
ii  ruby1:2.5.1
ii  ruby-actionpack-action-caching  1.2.0-2
ii  ruby-actionpack-xml-parser  1.0.2-3
ii  ruby-bundler1.16.1-3
ii  ruby-coderay1.1.2-2
ii  ruby-i18n   0.7.0-2
ii  ruby-jquery-rails   4.3.3-1
ii  ruby-mime-types 3.2.2-1
ii  ruby-mimemagic  0.3.2+dfsg-1
ii  ruby-net-ldap   0.16.1-1
ii  ruby-openid 2.7.0debian-1
ii  ruby-protected-attributes   1.1.3-2
ii  ruby-rack   1.6.4-5
ii  ruby-rack-openid1.4.2-1
ii  ruby-rails  2:4.2.10-1
ii  ruby-rails-observers0.1.5-1
ii  ruby-rbpdf  1.19.5+ds.1-1
ii  ruby-redcarpet  3.4.0-4+b1
ii  ruby-request-store  1.3.0-1
ii  ruby-rmagick2.16.0-4+b1
ii  ruby-roadie-rails   1.3.0-1

Versions of packages redmine recommends:
ii  

Bug#906682: marked as done (llvmlite: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 21:35:01 +
with message-id 
and subject line Bug#906682: fixed in llvmlite 0.25.0-1
has caused the Debian Bug report #906682,
regarding llvmlite: FTBFS when built with dpkg-buildpackage -A
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild

[... snipped ...]

   dh_link -i -O--buildsystem=pybuild
   dh_strip_nondeterminism -i -O--buildsystem=pybuild
   dh_compress -i -O--buildsystem=pybuild
   dh_fixperms -i -O--buildsystem=pybuild
   dh_missing -i -O--buildsystem=pybuild
   dh_installdeb -i -O--buildsystem=pybuild
   debian/rules override_dh_gencontrol
make[1]: Entering directory '/<>'
dh_gencontrol
dpkg-gencontrol: warning: package llvmlite-doc: unused substitution variable 
${sphinxdoc:Built-Using}
echo "Conflicts: python3-llvmlite-dbgsym" >> 
debian/.debhelper/python-llvmlite/dbgsym-root/DEBIAN/control
/bin/sh: 1: cannot create 
debian/.debhelper/python-llvmlite/dbgsym-root/DEBIAN/control: Directory 
nonexistent
make[1]: *** [debian/rules:27: override_dh_gencontrol] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


To reproduce, please try "dpkg-buildpackage -A".

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

Note: Please consider uploading in source-only form (dpkg-buildpackage -S)
so that this kind of bugs never propagate to testing. We would also get
official build logs for the "all" architecture here:

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: llvmlite
Source-Version: 0.25.0-1

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

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated llvmlite package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 20:35:01 +0100
Source: llvmlite
Binary: python-llvmlite python3-llvmlite llvmlite-doc
Architecture: source all amd64
Version: 0.25.0-1
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Daniel Stender 
Description:
 llvmlite-doc - LLVM Python binding for writing JIT compilers (docs)
 python-llvmlite - LLVM Python binding for writing JIT compilers
 python3-llvmlite - LLVM Python 3 binding for writing JIT compilers
Closes: 906682
Changes:
 llvmlite (0.25.0-1) unstable; urgency=medium
 .
   * New upstream release:
 + unfuzz use-system-six.patch.
   * deb/control:
 + build with default python interpreters.
 + use python3 package for sphinx and rtd-theme.
 + bump standards to 4.2.1 (no further changes needed).
   * deb/rules:
 + build with DH_VERBOSE=1 (according to standards 4.2.0)
 + drop unnecessary export line for DEB_BUILD_OPTIONS.
 + add check before injecting mutual conflicts for dbg
   packages (Closes: #906682).
   * add build profile switches:
 + deb/control: add !nodoc switch to b-deps and package description.
 + deb/rules: don't run sphinxdoc dh extension in deb/control if
   DEB_BUILD_PROFILES contains nodoc.
   * build with dh level 11 (changes in deb/compat and deb/control).
Checksums-Sha1:
 11da8a1f12feedad9b6898fe32f30bf2ab18f53f 2350 

Bug#908162: grub-efi-amd64-signed: cryptdisk support missing

[Alex Griffin]

I don't think this is fixed yet. After switching to the signed grub on 
my system with an encrypted boot partition, I get dropped into the grub 
command line. From here, the cryptomount command appears to be a no-op.

I'm not sure what the problem is, but I noticed that there is also a 
luks module which is not included. Maybe that's the issue? For now I 
have switched back to unsigned grub.

-- 
Alex Griffin

Processed: forcibly merging 912695 912709

[Debian Bug Tracking System]

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

> forcemerge 912695 912709
Bug #912695 [apt-show-versions] apt-show-versions: breaks "apt-get update" and 
uninstallable after Perl 5.28 upgrade
Bug #912709 [apt-show-versions] Max. recursion depth with nested structures 
exceeded
Severity set to 'critical' from 'grave'
Merged 912695 912709
> thanks
Stopping processing here.

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

Bug#912315: marked as done (audacious-plugins >= 3.10 missed)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 19:49:14 +
with message-id 
and subject line Bug#912315: fixed in audacious-plugins 3.10-1
has caused the Debian Bug report #912315,
regarding audacious-plugins >= 3.10 missed
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.)


-- 
912315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: audacious
Version: 3.10-1
Severity: grave


The following packages have unmet dependencies:
 audacious : Depends: audacious-plugins (>= 3.10) but 3.9-1+b6 is to be 
installed

Please consider to upload plugins asap. Ping me if you need help.

Cheers Alf

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

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

Versions of packages audacious depends on:
ii  audacious-plugins 3.9-1+b6
ii  dbus  1.12.10-1
ii  dbus-user-session [default-dbus-session-bus]  1.12.10-1
ii  dbus-x11 [dbus-session-bus]   1.12.10-1
ii  gtk2-engines-pixbuf   2.24.32-3
ii  libaudcore5   3.10-1
ii  libc6 2.27-8
ii  libgcc1   1:8.2.0-8
ii  libglib2.0-0  2.58.1-2
ii  libstdc++68.2.0-8

Versions of packages audacious recommends:
ii  unzip  6.0-21

audacious suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: audacious-plugins
Source-Version: 3.10-1

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

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

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

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated audacious-plugins package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 20:22:13 +0100
Source: audacious-plugins
Binary: audacious-plugins audacious-plugins-data
Architecture: source
Version: 3.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Alf Gaida 
Description:
 audacious-plugins - Base plugins for audacious
 audacious-plugins-data - Data files for Audacious plugins
Closes: 912315
Changes:
 audacious-plugins (3.10-1) unstable; urgency=medium
 .
   * Cherry-picked upstream version 3.10
 (Closes: #912315)
   * debian/control
 - Bumped debhelper to >= 11.
 - Bumped compat to 11.
 - Bumped Standards to 4.2.1, no changes needed.
 - Use secure homepage uri.
 - Added myself to uploaders.
 - Fixed Breaks to audacious (<< 3.10)
   * debian/rules:
 - Added override_dh_missing.
 - Fixed host OS query.
   * Fixed watch file, use secure uri
   * Added upstream metadata
   * Updated debian/copyright
Checksums-Sha1:
 202ca1490b29e2ad97d998bb907e20429d59f183 3074 audacious-plugins_3.10-1.dsc
 459107a3f61c738b70e5d59f0b07f86ab884c1d1 1701877 
audacious-plugins_3.10.orig.tar.bz2
 1f9c1d8908556a335404f23aac076145f434ec36 12748 
audacious-plugins_3.10-1.debian.tar.xz
Checksums-Sha256:
 f34132b99c06a0012d7782d0cba8a6cd4b2ba2ad36a3288b1e5a6db3dfc35473 3074 
audacious-plugins_3.10-1.dsc
 5061ebb20169eb4d3f15aafbe83b43363762dc8d19ca0cd83f5556dc577e618f 1701877 
audacious-plugins_3.10.orig.tar.bz2
 9dcba63f8dda7438196d192d56400cb9e6ef82c4b488e368114eb6bf8a6d9d6c 12748 
audacious-plugins_3.10-1.debian.tar.xz
Files:
 1ca4fa86c8dcc3a64eae5dc572adfb81 3074 sound optional 
audacious-plugins_3.10-1.dsc
 26268359f4f21171de35cc10d0545733 1701877 sound optional 
audacious-plugins_3.10.orig.tar.bz2
 

Bug#911136: marked as done (javatools: FTBFS with Java 11 due to MANIFEST.MF wrapping change)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 19:04:25 +
with message-id 
and subject line Bug#911136: fixed in javatools 0.71
has caused the Debian Bug report #911136,
regarding javatools: FTBFS with Java 11 due to MANIFEST.MF wrapping change
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.)


-- 
911136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: javatools
Severity: important
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java11

javatools has a test failing with Java 11. It looks like Java 11 now wraps
the attributes in MANIFEST.MF after 72 characters instead of 70 in the
previous versions:

  prove -Ilib  t
  t/critic.t ... skipped: Only UNRELEASED versions are criticised
  t/minimum-version.t .. ok
  t/strict.t ... ok
  All tests successful.
  Files=3, Tests=50,  3 wallclock secs ( 0.03 usr  0.00 sys +  2.88 cusr  0.13 
csys =  3.04 CPU)
  Result: PASS
  cd tests && ./tests.sh
  Running: perl -I./lib ./jh_manifest "/build/javatools-0.70/tests/test.jar"
  Running: perl -I./lib ./jh_manifest "/build/javatools-0.70/tests/test.jar"
  ERROR: difference detected:
  --- long-out2014-09-10 19:33:53.0 +
  +++ META-INF/MANIFEST.MF2018-10-16 09:21:38.0 +
  @@ -1,11 +1,10 @@
   Manifest-Version: 1.0
  -Class-Path: /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /u
  - sr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java
  - /hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar
  - /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/ja
  - va/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.ja
  - r /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/
  - java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.
  - jar
  +Class-Path: /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr
  + /share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hex
  + dump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/s
  + hare/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdu
  + mp.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/sha
  + re/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump
  + .jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar
   Created-By: 1.6.0_06 (Sun Microsystems Inc.)
--- End Message ---
--- Begin Message ---
Source: javatools
Source-Version: 0.71

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated javatools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 19:48:36 +0100
Source: javatools
Binary: jarwrapper javahelper java-propose-classpath
Architecture: source
Version: 0.71
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 jarwrapper - Run executable Java .jar files
 java-propose-classpath - Helper script to suggest a classpath for jar files
 javahelper - Helper scripts for packaging Java programs
Closes: 911136 912751
Changes:
 javatools (0.71) unstable; urgency=medium
 .
   * Fixed jh_installjavadoc when the target is specified (Closes: #912751)
   * Fixed the build failure with Java 11 (Closes: #911136)
Checksums-Sha1:
 a32c8658db3ec027a2130cbf0e60eac640c370ab 1886 javatools_0.71.dsc
 99506a5388691f1b4dc68fdb5a0f3f7590208232 53748 javatools_0.71.tar.xz
 8327a628eb6e8318ea02da7fa11d27c8d8d1e261 11875 javatools_0.71_source.buildinfo
Checksums-Sha256:
 14dc6065f351f6d6e3132aabd8a9298e65b09360528d5b1b16346d0fc1723c11 1886 
javatools_0.71.dsc
 b681816f3982f97f303f34e3a1952a7b2b96d53951c2dd16fc7569d870e9ead6 53748 
javatools_0.71.tar.xz
 e66a9e5d7bfee602997b88ae4727ca15bbd1e5647dfd7c6ece466c792f5540f0 11875 
javatools_0.71_source.buildinfo
Files:
 481812b173a04b4d25197b101c6dcbfc 1886 java optional javatools_0.71.dsc

Processed: Re: [Pkg-alsa-devel] Bug#912766: alsa-utils: Dummy outupt after update

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libasound2-plugins 1.1.7-1
Bug #912766 [alsa-utils] alsa-utils: Dummy outupt after update
Bug reassigned from package 'alsa-utils' to 'libasound2-plugins'.
No longer marked as found in versions alsa-utils/1.1.7-1.
Ignoring request to alter fixed versions of bug #912766 to the same values 
previously set
Bug #912766 [libasound2-plugins] alsa-utils: Dummy outupt after update
Marked as found in versions alsa-plugins/1.1.7-1.
> forcemerge 912721 -1
Bug #912721 [libasound2-plugins] libasound2-plugins: Sound no longer works 
after latest update
Bug #912680 [libasound2-plugins] libasound2-plugins: broken symlinks in 
/etc/alsa/conf.d
Bug #912726 [libasound2-plugins] alsa-lib: update created /etc/alsa/conf.d 
directory filled with broken symlinks to /usr/share/alsa/alsa.conf.d
Bug #912755 [libasound2-plugins] cannot access file 
/etc/alsa/conf.d/10-rate-lav.conf
Bug #912763 [libasound2-plugins] libasound2: Total loss of sound on Debian Sid 
with Intel sound
Bug #912766 [libasound2-plugins] alsa-utils: Dummy outupt after update
Severity set to 'grave' from 'important'
Bug #912680 [libasound2-plugins] libasound2-plugins: broken symlinks in 
/etc/alsa/conf.d
Bug #912726 [libasound2-plugins] alsa-lib: update created /etc/alsa/conf.d 
directory filled with broken symlinks to /usr/share/alsa/alsa.conf.d
Bug #912755 [libasound2-plugins] cannot access file 
/etc/alsa/conf.d/10-rate-lav.conf
Bug #912763 [libasound2-plugins] libasound2: Total loss of sound on Debian Sid 
with Intel sound
Merged 912680 912721 912726 912755 912763 912766

-- 
912680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912680
912721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912721
912726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912726
912755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912755
912763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912763
912766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#895723: marked as done (librsvg: FTBFS on powerpc arches)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 19:04:38 +
with message-id 
and subject line Bug#895723: fixed in librsvg 2.44.8-3
has caused the Debian Bug report #895723,
regarding librsvg: FTBFS on powerpc arches
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.)


-- 
895723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librsvg
Version: 2.42.3-1
Severity: important
Tags: upstream

Building 2.42.3 on Debian experimental ppc64el. powerpc and ppc64  seem to have 
the same issues.

Possibly due to linking with --as-needed . However not sure why this only 
affects the powerpc arches.

Full ppc64el logs: 
https://buildd.debian.org/status/fetch.php?pkg=librsvg=ppc64el=2.42.3-1=1522565714=0

error: linking with `cc` failed: exit code: 1
  |
  = note: "cc" "-Wl,--as-needed" "-Wl,-z,noexecstack" "-m64" "-L" 
"/usr/lib/rustlib/powerpc64le-unknown-linux-gnu/lib" 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.102je7u62sm4kcw.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.10tn6hsfx4oyxjjj.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.114xigf1yyw2gcw0.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.120svpnd23nxqi5a.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.121owdsfzatxhhbm.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.12f5ifttr58vfevz.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.12um7e2pna88us0m.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.155oupk9ie2lc4fq.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.15dl3imwo0d8mnfv.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1686o3u9d63jdfh.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.16g72hl54zgn1037.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.16u6js6g0l3k1ic6.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.17d4cze32tp9xnyn.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1aoz9ryfspmhujr6.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1bcme1fmkrokil8a.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1chjqw8w9cqnfli7.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1epb5nyi41no37ob.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1g1d239vtessmzk5.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1ghfiig2h76dl8qp.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1hkyhrtkifakvrh4.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1i2m4tc5uehwthvl.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1im38lueib99jsk0.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1iyvqxtdjb3fwkh7.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1jnlhyxj59jycbjv.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1kzmobth8vrv86p7.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1liaz5pb3qsa45z.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1mbrod7fypeh96bo.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1mvmz58owquyropc.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1nyfdlp3jd783n7g.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1o6b1la7g4jnv39b.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1owmwuuo26nlf4g0.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1q8ffos2d96smbjs.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1r8x652sazw5kewv.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1rmm85xvb873qftb.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1s9l6wh3i035yuij.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1uacw3k3wfmrurex.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1wjzcbl1bqerhxx0.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1y16o1qfye96o7m0.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1y4ds2ij7sm8xk5g.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1ygj72qs8o1veaeq.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1ynya56gfonq4yrh.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1zeawhkbeobww1zn.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1zwd8n7bcl3vhvvh.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.20v6ib4511rnk9ng.rcgu.o"
 

Bug#912768: hplip-data: hp-toolbox fsck

[Brian Potkin]

severity 912768 normal
thanks



On Sat 03 Nov 2018 at 19:20:42 +0100, Cristian Ionescu-Idbohrn wrote:

> Package: hplip-data
> Version: 3.18.10+dfsg0-1
> Severity: grave
> Justification: renders package unusable


If you would explain why this is grave, we could adjust the severity.

Regards,

Brian.

Processed: Re: Bug#912768: hplip-data: hp-toolbox fsck

[Debian Bug Tracking System]

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

> severity 912768 normal
Bug #912768 [hplip-data] hplip-data: hp-toolbox fsck
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#911136: Bug #911136 in javatools marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #911136 in javatools 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/javatools/commit/18419d72a98136687d66e9bb2f4c879eef13


Fixed the build failure with Java 11 (Closes: #911136)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/911136

Processed: Bug #911136 in javatools marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #911136 [src:javatools] javatools: FTBFS with Java 11 due to MANIFEST.MF 
wrapping change
Added tag(s) pending.

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

Bug#905379: Bug explanation

[Julian Gilbey]

On Sat, Nov 03, 2018 at 01:46:49PM +0100, Roland Hieber wrote:
> On Fri, 26 Oct 2018 16:09:19 +0100 Julian Gilbey  wrote:
> > I've just uploaded a version based on git to unstable
> > (2.1.5+dfsg+2.1.6-test.20181026.b4f4e65c-1) so you can test it.  Does
> > this version work for you? 
> 
> Thanks! At least it shows a functional UI without any warnings, and
> editing and studying decks works, so I guess that's a yes :-)

Super - thanks for letting me know!  So I'll close this bug report
when 2.1.6 is released.

Best wishes,

   Julian

Processed: Re: Bug#912765: hplip: hp-doctor broken

[Debian Bug Tracking System]

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

> severity 912765 normal
Bug #912765 [hplip] hplip: hp-doctor broken
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#912765: hplip: hp-doctor broken

[Brian Potkin]

severity 912765 normal
thanks



On Sat 03 Nov 2018 at 19:02:37 +0100, Cristian Ionescu-Idbohrn wrote:

> Package: hplip
> Version: 3.18.10+dfsg0-1
> Severity: grave
> Justification: renders package unusable
> 
> $ hp-doctor
> Traceback (most recent call last):
>   File "/usr/bin/hp-doctor", line 42, in 
> check_extension_module_env('cupsext')
>   File "/usr/share/hplip/base/g.py", line 339, in check_extension_module_env
> python_ver = xint((sys.version).split(' ')[0])  #find the 
> current python version ; xint() to convert string to int, returns a list
>   File "/usr/share/hplip/base/g.py", line 331, in xint
> return l
> UnboundLocalError: local variable 'l' referenced before assignment

Thank you for your bug report, Cristian, but your severity level is much
too high. hp-doctor is only a diagnostic utility. I expect printer and
scanner setup are ok. Please contact upstream
at

https://bugs.launchpad.net/hplip

to get an opinion on this aspect of their code.

Regards,

Brian.

Bug#912768: hplip-data: hp-toolbox fsck

[Till Kamppeter]

I have fixed this bug and two others one in the HPLIP package for Ubuntu 
Cosmic (18.10). Simply overtake the two patches which I have added.


https://launchpad.net/ubuntu/+source/hplip/+changelog
https://launchpad.net/ubuntu/+source/hplip/3.18.7+dfsg1-2ubuntu2
https://launchpad.net/ubuntu/+source/hplip/3.18.7+dfsg1-2ubuntu1

https://launchpad.net/bugs/1789184

   Till


On 03/11/2018 19:20, Cristian Ionescu-Idbohrn wrote:

Package: hplip-data
Version: 3.18.10+dfsg0-1
Severity: grave
Justification: renders package unusable

$ hp-toolbox

HP Linux Imaging and Printing System (ver. 3.18.10)
HP Device Manager ver. 15.0

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-cii'   
   \Traceback (most recent call last):
   File "/usr/bin/hp-toolbox", line 280, in 
 toolbox = ui.DevMgr5(__version__, device_uri,  None)
   File "/usr/share/hplip/ui5/devmgr5.py", line 253, in __init__
 self.initUI()
   File "/usr/share/hplip/ui5/devmgr5.py", line 324, in initUI
 self.DiagnoseQueueAction.setIcon(QIcon(load_pixmap('warning', '16x16')))
AttributeError: 'DevMgr5' object has no attribute 'DiagnoseQueueAction'

Patch here:

https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1789184/comments/7

seems to help.

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

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

Versions of packages hplip-data depends on:
ii  python3   3.6.7-1
ii  xz-utils  5.2.2-1.3

hplip-data recommends no packages.

Versions of packages hplip-data suggests:
ii  hplip  3.18.10+dfsg0-1

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/hplip/ui5/devmgr5.py (from hplip-data package)


Cheers,

Processed: Re: [Pkg-alsa-devel] Bug#912763: libasound2: Total loss of sound on Debian Sid with Intel sound

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libasound2-plugins 1.1.7-1
Bug #912763 [libasound2] libasound2: Total loss of sound on Debian Sid with 
Intel sound
Bug reassigned from package 'libasound2' to 'libasound2-plugins'.
No longer marked as found in versions alsa-lib/1.1.7-1.
Ignoring request to alter fixed versions of bug #912763 to the same values 
previously set
Bug #912763 [libasound2-plugins] libasound2: Total loss of sound on Debian Sid 
with Intel sound
Marked as found in versions alsa-plugins/1.1.7-1.
> forcemerge 912721 -1
Bug #912721 [libasound2-plugins] libasound2-plugins: Sound no longer works 
after latest update
Bug #912680 [libasound2-plugins] libasound2-plugins: broken symlinks in 
/etc/alsa/conf.d
Bug #912726 [libasound2-plugins] alsa-lib: update created /etc/alsa/conf.d 
directory filled with broken symlinks to /usr/share/alsa/alsa.conf.d
Bug #912755 [libasound2-plugins] cannot access file 
/etc/alsa/conf.d/10-rate-lav.conf
Bug #912763 [libasound2-plugins] libasound2: Total loss of sound on Debian Sid 
with Intel sound
Severity set to 'grave' from 'normal'
Bug #912680 [libasound2-plugins] libasound2-plugins: broken symlinks in 
/etc/alsa/conf.d
Bug #912726 [libasound2-plugins] alsa-lib: update created /etc/alsa/conf.d 
directory filled with broken symlinks to /usr/share/alsa/alsa.conf.d
Bug #912755 [libasound2-plugins] cannot access file 
/etc/alsa/conf.d/10-rate-lav.conf
Merged 912680 912721 912726 912755 912763

-- 
912680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912680
912721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912721
912726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912726
912755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912755
912763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#912768: hplip-data: hp-toolbox fsck

[Cristian Ionescu-Idbohrn]

Package: hplip-data
Version: 3.18.10+dfsg0-1
Severity: grave
Justification: renders package unusable

$ hp-toolbox

HP Linux Imaging and Printing System (ver. 3.18.10)
HP Device Manager ver. 15.0

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-cii'   
   \Traceback (most recent call last):
  File "/usr/bin/hp-toolbox", line 280, in 
toolbox = ui.DevMgr5(__version__, device_uri,  None)
  File "/usr/share/hplip/ui5/devmgr5.py", line 253, in __init__
self.initUI()
  File "/usr/share/hplip/ui5/devmgr5.py", line 324, in initUI
self.DiagnoseQueueAction.setIcon(QIcon(load_pixmap('warning', '16x16')))
AttributeError: 'DevMgr5' object has no attribute 'DiagnoseQueueAction'

Patch here:

https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1789184/comments/7

seems to help.

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

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

Versions of packages hplip-data depends on:
ii  python3   3.6.7-1
ii  xz-utils  5.2.2-1.3

hplip-data recommends no packages.

Versions of packages hplip-data suggests:
ii  hplip  3.18.10+dfsg0-1

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/hplip/ui5/devmgr5.py (from hplip-data package)


Cheers,

-- 
Cristian

Bug#912755: Temp fix

[david]

In another, merged, report Amy Kos suggested:

mv /etc/alsa/conf.d /etc/alsa/conf.d.bak

This worked for me.

Bug#910751: marked as done (python3-tinycss: fails to build python3 extension for python3.7)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 18:04:27 +
with message-id 
and subject line Bug#910751: fixed in python-tinycss 0.4-2
has caused the Debian Bug report #910751,
regarding python3-tinycss: fails to build python3 extension for python3.7
to be marked as done.

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

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


-- 
910751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-tinycss
Version: 0.4-1
Severity: important

Hi,

Your package attempts to build the python3 extension for python3.7 (which
is a supported python3 version). However, that fails as the shipped .c
file was built with an old version of cython that didn't support 3.7:

building 'tinycss.speedups' extension
creating build/temp.linux-i386-3.7
creating build/temp.linux-i386-3.7/tinycss
i686-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python3.7m -c tinycss/speedups.c -o 
build/temp.linux-i386-3.7/tinycss/speedups.o
tinycss/speedups.c: In function '__Pyx__ExceptionSwap':
tinycss/speedups.c:6591:24: error: 'PyThreadState {aka struct _ts}' has no 
member named 'exc_type'; did you mean 'curexc_type'?
 tmp_type = tstate->exc_type;
^~~~
curexc_type
[...]
***
WARNING: The extension could not be compiled, speedups are not enabled.
Failure information, if any, is above.
Retrying the build without the Cython extension now.
***

It'd be good to get speedups.c regenerated with a newer cython, or
even better to regenerate it during the build.

Cheers,
Emilio

Full log: 
https://buildd.debian.org/status/fetch.php?pkg=python-tinycss=i386=0.4-1%2Bb3=1530354240=0

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

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

Versions of packages python3-tinycss depends on:
ii  libc62.27-5
ii  python3  3.6.6-1

python3-tinycss recommends no packages.

Versions of packages python3-tinycss suggests:
pn  python-tinycss-doc  
--- End Message ---
--- Begin Message ---
Source: python-tinycss
Source-Version: 0.4-2

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

Debian distribution maintenance software
pp.
Felix Krull  (supplier of updated python-tinycss package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 16:06:59 +
Source: python-tinycss
Binary: python-tinycss python3-tinycss python-tinycss-doc
Architecture: source
Version: 0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Felix Krull 
Description:
 python-tinycss - complete yet simple CSS parser (Python2 version)
 python-tinycss-doc - complete yet simple CSS parser (Documentation)
 python3-tinycss - complete yet simple CSS parser (Python3 version)
Closes: 910751
Changes:
 python-tinycss (0.4-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
 .
   [ Felix Krull ]
   * d/clean: remove bundled speedups.c before building (closes: #910751)
   * d/control: add myself (Felix Krull) to Uploaders
Checksums-Sha1:
 

Bug#912765: hplip: hp-doctor broken

[Cristian Ionescu-Idbohrn]

Package: hplip
Version: 3.18.10+dfsg0-1
Severity: grave
Justification: renders package unusable

$ hp-doctor
Traceback (most recent call last):
  File "/usr/bin/hp-doctor", line 42, in 
check_extension_module_env('cupsext')
  File "/usr/share/hplip/base/g.py", line 339, in check_extension_module_env
python_ver = xint((sys.version).split(' ')[0])  #find the 
current python version ; xint() to convert string to int, returns a list
  File "/usr/share/hplip/base/g.py", line 331, in xint
return l
UnboundLocalError: local variable 'l' referenced before assignment


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

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

Versions of packages hplip depends on:
ii  adduser3.118
ii  cups   2.2.8-5
ii  hplip-data 3.18.10+dfsg0-1
ii  libc6  2.27-6
ii  libcups2   2.2.8-5
ii  libdbus-1-31.12.10-1
ii  libhpmud0  3.18.10+dfsg0-1
ii  libsane-hpaio  3.18.10+dfsg0-1
ii  libsane1   1.0.27-3
ii  libsnmp30  5.7.3+dfsg-4+b1
ii  libusb-1.0-0   2:1.0.22-2
ii  lsb-base   9.20170808
ii  printer-driver-hpcups  3.18.10+dfsg0-1
ii  python33.6.7-1
ii  python3-dbus   1.2.8-2+b1
ii  python3-gi 3.30.1-2
ii  python3-pexpect4.6.0-1
ii  python3-pil5.3.0-1
ii  python3-reportlab  3.5.9-1
ii  wget   1.19.5-2
ii  xz-utils   5.2.2-1.3

Versions of packages hplip recommends:
pn  avahi-daemon  
ii  policykit-1   0.105-21
pn  printer-driver-postscript-hp  
ii  sane-utils1.0.27-3

Versions of packages hplip suggests:
pn  hplip-doc  
ii  hplip-gui  3.17.10+repack0-7
ii  python3-notify20.3-3
ii  system-config-printer  1.5.11-3

-- no debconf information


Cheers,

-- 
Cristian

Bug#876251: marked as done (typo in initscript makes rdm_test_server fail to start)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 18:02:09 +
with message-id 
and subject line Bug#876251: fixed in ola 0.10.3.nojsmin-2+deb9u1
has caused the Debian Bug report #876251,
regarding typo in initscript makes rdm_test_server fail to start
to be marked as done.

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

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


-- 
876251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ola-rdm-tests
Version: 0.10.3.nojsmin-1
Severity: serious
Tags: patch

There is a typo in the rdm_test_server initscript. The line

DAEMON_ARGS="--world-writable"

should be

DAEMON_ARGS="--world-writeable"

without this fix, the daemon fails to start and the init script is
useless.

This is a regression from jessie.

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

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

Versions of packages ola-rdm-tests depends on:
ii  libjs-jquery 3.2.1-1
ii  libjs-jquery-ui  1.12.1+dfsg-5
ii  lsb-base 9.20170808
ii  ola  0.10.5.nojsmin-2
ii  ola-python   0.10.5.nojsmin-2
ii  python   2.7.14-1
ii  python-numpy 1:1.13.1-1

ola-rdm-tests recommends no packages.

Versions of packages ola-rdm-tests suggests:
ii  bash-completion  1:2.1-4.3

-- Configuration Files:
/etc/init.d/rdm_test_server changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ola
Source-Version: 0.10.3.nojsmin-2+deb9u1

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

Debian distribution maintenance software
pp.
Wouter Verhelst  (supplier of updated ola 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, 31 Oct 2018 17:02:06 +0100
Source: ola
Binary: libola-dev ola-python ola-rdm-tests ola libola1
Architecture: source amd64 all
Version: 0.10.3.nojsmin-2+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Wouter Verhelst 
Changed-By: Wouter Verhelst 
Description:
 libola-dev - Open Lighting Architecture - development libraries
 libola1- Open Lighting Architecture - shared libraries
 ola- Open Lighting Architecture
 ola-python - Open Lighting Architecture - Python Classes
 ola-rdm-tests - Open Lighting Architecture - RDM Responder Tests
Closes: 876251 912713
Changes:
 ola (0.10.3.nojsmin-2+deb9u1) stretch; urgency=medium
 .
   * Fix typo in /etc/init.d/rdm_test_server; Closes: #876251.
   * Fix filename for jquery in rdm test server static HTML files;
 Closes: #912713.
Checksums-Sha1:
 1f9d4704beafd7d678c726d2f2c56b7f24b67395 2384 ola_0.10.3.nojsmin-2+deb9u1.dsc
 7cb997ca68766e8a7face82d97d18a3f87c343c1 22120 
ola_0.10.3.nojsmin-2+deb9u1.debian.tar.xz
 f9750d01ed7f175d5b5e120251f6c02660188ad5 3179392 
libola-dev_0.10.3.nojsmin-2+deb9u1_amd64.deb
 c85c45de74ce554c7b06d89526ba205201fa2a46 756646 
libola1-dbgsym_0.10.3.nojsmin-2+deb9u1_amd64.deb
 c685d1a13e4a1aadf7e56f91077e7c15ee05adcd 2114294 
libola1_0.10.3.nojsmin-2+deb9u1_amd64.deb
 4c666108c8e2cbf19d7ec5bd130817ff8beabbd2 79034 
ola-dbgsym_0.10.3.nojsmin-2+deb9u1_amd64.deb
 1ff3b2c6a78abac99f41856139d452d21fef69c8 43554 
ola-python_0.10.3.nojsmin-2+deb9u1_all.deb
 4a560e73711f14dd7c8e1d57864a24a128b2c9dc 94306 
ola-rdm-tests_0.10.3.nojsmin-2+deb9u1_all.deb
 ce8725de0664ce7b1c482ca631602a2531fbfab2 9928 
ola_0.10.3.nojsmin-2+deb9u1_amd64.buildinfo
 9af1432f803b58f1441002a492292173b59b6799 449754 
ola_0.10.3.nojsmin-2+deb9u1_amd64.deb
Checksums-Sha256:
 c01b8c5b92de39b541e54a57a5529a79090324465843290f63032c28fd3c3fa9 2384 
ola_0.10.3.nojsmin-2+deb9u1.dsc
 5d78fc41d7ce4e4d57263f2977237d6615b6d9a5048e94934cd51e94d4e5d3b1 22120 

Bug#912713: marked as done (Incorrect filename for jquery-ui makes rdm test server not work properly)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 18:02:09 +
with message-id 
and subject line Bug#912713: fixed in ola 0.10.3.nojsmin-2+deb9u1
has caused the Debian Bug report #912713,
regarding Incorrect filename for jquery-ui makes rdm test server not work 
properly
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.)


-- 
912713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ola-rdm-tests
Version: 0.10.3.nojsmin-2
Severity: serious

The replacement of the jquery-ui code by the Debian-packaged version was
done incorrectly; as a result, jquery-ui is not found by the rdm test
server's HTML interface. This means that nothing works the way it
should.
--- End Message ---
--- Begin Message ---
Source: ola
Source-Version: 0.10.3.nojsmin-2+deb9u1

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

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

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

Debian distribution maintenance software
pp.
Wouter Verhelst  (supplier of updated ola 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, 31 Oct 2018 17:02:06 +0100
Source: ola
Binary: libola-dev ola-python ola-rdm-tests ola libola1
Architecture: source amd64 all
Version: 0.10.3.nojsmin-2+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Wouter Verhelst 
Changed-By: Wouter Verhelst 
Description:
 libola-dev - Open Lighting Architecture - development libraries
 libola1- Open Lighting Architecture - shared libraries
 ola- Open Lighting Architecture
 ola-python - Open Lighting Architecture - Python Classes
 ola-rdm-tests - Open Lighting Architecture - RDM Responder Tests
Closes: 876251 912713
Changes:
 ola (0.10.3.nojsmin-2+deb9u1) stretch; urgency=medium
 .
   * Fix typo in /etc/init.d/rdm_test_server; Closes: #876251.
   * Fix filename for jquery in rdm test server static HTML files;
 Closes: #912713.
Checksums-Sha1:
 1f9d4704beafd7d678c726d2f2c56b7f24b67395 2384 ola_0.10.3.nojsmin-2+deb9u1.dsc
 7cb997ca68766e8a7face82d97d18a3f87c343c1 22120 
ola_0.10.3.nojsmin-2+deb9u1.debian.tar.xz
 f9750d01ed7f175d5b5e120251f6c02660188ad5 3179392 
libola-dev_0.10.3.nojsmin-2+deb9u1_amd64.deb
 c85c45de74ce554c7b06d89526ba205201fa2a46 756646 
libola1-dbgsym_0.10.3.nojsmin-2+deb9u1_amd64.deb
 c685d1a13e4a1aadf7e56f91077e7c15ee05adcd 2114294 
libola1_0.10.3.nojsmin-2+deb9u1_amd64.deb
 4c666108c8e2cbf19d7ec5bd130817ff8beabbd2 79034 
ola-dbgsym_0.10.3.nojsmin-2+deb9u1_amd64.deb
 1ff3b2c6a78abac99f41856139d452d21fef69c8 43554 
ola-python_0.10.3.nojsmin-2+deb9u1_all.deb
 4a560e73711f14dd7c8e1d57864a24a128b2c9dc 94306 
ola-rdm-tests_0.10.3.nojsmin-2+deb9u1_all.deb
 ce8725de0664ce7b1c482ca631602a2531fbfab2 9928 
ola_0.10.3.nojsmin-2+deb9u1_amd64.buildinfo
 9af1432f803b58f1441002a492292173b59b6799 449754 
ola_0.10.3.nojsmin-2+deb9u1_amd64.deb
Checksums-Sha256:
 c01b8c5b92de39b541e54a57a5529a79090324465843290f63032c28fd3c3fa9 2384 
ola_0.10.3.nojsmin-2+deb9u1.dsc
 5d78fc41d7ce4e4d57263f2977237d6615b6d9a5048e94934cd51e94d4e5d3b1 22120 
ola_0.10.3.nojsmin-2+deb9u1.debian.tar.xz
 961a9b26d2a6d589caf747ae85be04ef97dd14865c09e5fce8b5307320f785c6 3179392 
libola-dev_0.10.3.nojsmin-2+deb9u1_amd64.deb
 bbf815b2efe472a69c882708d54bd4d408a622b48a50b85981fc5369827eb3b5 756646 
libola1-dbgsym_0.10.3.nojsmin-2+deb9u1_amd64.deb
 d29e8f766347a8bc02a53bfafb96569768639b0381a5f86b9d10eda38157dbad 2114294 
libola1_0.10.3.nojsmin-2+deb9u1_amd64.deb
 91adcfea707ff7f4c543cda4274b9690f563720e49ac6f68fb3e15fbc85be708 79034 
ola-dbgsym_0.10.3.nojsmin-2+deb9u1_amd64.deb
 e27128d73dbace3829abb2d4f1c8a4c16ecec2b3e3834fed33b3150650dde239 43554 
ola-python_0.10.3.nojsmin-2+deb9u1_all.deb
 53d32c93a1b8b7a5adf1432155fc3297ff9a90c2c6410a167bc0a692b5cca028 94306 
ola-rdm-tests_0.10.3.nojsmin-2+deb9u1_all.deb
 7ac7231e31db09b0b3dbb60052bd7dfb6124584b9b34db13b990d8867de03271 9928 
ola_0.10.3.nojsmin-2+deb9u1_amd64.buildinfo
 dfe46ed3c11ca5800a97fb062b7d79ce557591ae8178d6f5847ded56470fd10c 449754 
ola_0.10.3.nojsmin-2+deb9u1_amd64.deb
Files:
 770071bbe60f0455a2d34db5e3bc8621 2384 libs extra 

Bug#909000: marked as done (Enigmail 2.0 needed in Stretch after Thunderbird 60 upload)

[Jonas Meurer]

Hi dkg,

Am 03.11.18 um 18:06 schrieb Debian Bug Tracking System:
> Source: enigmail
> Source-Version: 2:2.0.8-5~deb9u1
> 
> We believe that the bug you reported is fixed in the latest version of
> enigmail, which is due to be installed in the Debian FTP archive.
>> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Mon, 29 Oct 2018 00:41:43 -0400
> Source: enigmail
> Binary: enigmail
> Architecture: source
> Version: 2:2.0.8-5~deb9u1
> Distribution: stretch
> Urgency: medium
> Maintainer: Debian Mozilla Extension Maintainers 
> 
> Changed-By: Daniel Kahn Gillmor 
> Description:
>  enigmail   - GPG support for Thunderbird and Debian Icedove
> Closes: 909000
> Changes:
>  enigmail (2:2.0.8-5~deb9u1) stretch; urgency=medium
>  .
>* Rebuild for stretch (Closes: #909000)

Thanks a ton for your hard work on getting this solved, dkg!

I really appreciate it, and a lot of other enigmail users on Debian
Stretch as well, I'm sure.

Cheers
 jonas



signature.asc
Description: OpenPGP digital signature

Processed: block 908112 with 908612

[Debian Bug Tracking System]

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

> block 908112 with 908612
Bug #908112 [ganeti] ganeti: Unable to move an instance to an other node
908112 was not blocked by any bugs.
908112 was not blocking any bugs.
Added blocking bug(s) of 908112: 908612
> thanks
Stopping processing here.

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

Bug#906075: marked as done (gnunet: missing build dependency on python)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 17:29:50 +
with message-id 
and subject line Bug#906075: fixed in gnunet 0.11.0~pre666-1
has caused the Debian Bug report #906075,
regarding gnunet: missing build dependency on python
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.)


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

$ head -1 src/util/gnunet-qr.py.in
#!@PYTHON@
$


When python was not installed during the build, what happens is:

https://buildd.debian.org/status/fetch.php?pkg=gnunet=amd64=0.10.1-4+b1=1499160551=0

...
checking for a Python interpreter with version >= 2.6... python3
...


This makes /usr/bin/gnunet-qr start with
#!/usr/bin/python3


It is unclear whether or not the script might work with python3,
it already fails with

$ cd /tmp/
bunk@localhost:/tmp$ gnunet-qr
  File "/usr/bin/gnunet-qr", line 9
print 'Cannot run gnunet-qr, please install zbar-python'
   ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print('Cannot 
run gnunet-qr, please install zbar-python')?
$

This is currently unfixable due to lack of python3-zbar (#888303).


With python installed dring the build gnunet-qr
will use the correct interpreter.
--- End Message ---
--- Begin Message ---
Source: gnunet
Source-Version: 0.11.0~pre666-1

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

Debian distribution maintenance software
pp.
Bertrand Marc  (supplier of updated gnunet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Nov 2018 17:24:53 +0100
Source: gnunet
Binary: gnunet gnunet-dev
Architecture: source amd64
Version: 0.11.0~pre666-1
Distribution: experimental
Urgency: medium
Maintainer: Bertrand Marc 
Changed-By: Bertrand Marc 
Description:
 gnunet - GNU's framework for secure peer-to-peer networking (meta)
 gnunet-dev - GNU's framework for secure peer-to-peer networking (development)
Closes: 906075
Changes:
 gnunet (0.11.0~pre666-1) experimental; urgency=medium
 .
   [ Bertrand Marc ]
   * New upstream version 0.11.0pre666.
   * Build-depend on dh-python2 to ensure gnunet-qr has the correct header
 (Closes: #906075).
   * Move the package to salsa and update Vcs-browser and Vcs-git accordingly.
   * Add Christian Grothoff's new key to debian/upstream/signing-key.asc.
   * Update build-dependencies according to README:
 + update minimum versions.
 + build-depends on libpq-dev, libjansson-dev, libbluetooth-dev, texinfo.
   * debian/patches:
 + remove build_against_libcurl, included upstream.
 + remove conversation_libexecdir, included upstream.
 + remove gnunet_PATHMAX.patch, included upstream.
 + remove kfreebsd_malloc_np.patch, included upstream.
 + remove noinst_set.diff, included upstream.
 + refresh fix-bashism.patch.
 + refresh and add new fixes in typos.diff.
   * The file testbed_test.c is not available anymore, so add a patch to remove
 it from the documentation.
   * debian/rules: gnunet-gns-import.sh does not exist anymore.
   * libnss_gns* was moved from /lib/$triplet to /usr/lib/$triplet/gnunet/nss/.
   * Drop lintian override about python, not used anymore.
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field.
   * d/changelog: Remove trailing whitespaces.
Checksums-Sha1:
 a9eb403d37c408c9d091b8b1a58039de6fdfe14e 2503 gnunet_0.11.0~pre666-1.dsc
 356724f9e38162984bff602fea30ce524f502201 7487985 
gnunet_0.11.0~pre666.orig.tar.gz
 04f936babe3f126e76ce3d0e96d3dced1a25e484 40288 
gnunet_0.11.0~pre666-1.debian.tar.xz
 3b17e0c893529988e5b8009df2c0d4bf9ced2d4d 5912144 
gnunet-dbgsym_0.11.0~pre666-1_amd64.deb
 92292fe5b9a0a63ff81880623919ac6e1a7a07b5 256304 
gnunet-dev_0.11.0~pre666-1_amd64.deb
 6ab885df77b9da410a3ec71b874d0e5afaddb218 13283 
gnunet_0.11.0~pre666-1_amd64.buildinfo
 24f1e5add1bfb6642a74a0bf8d549ce837e3e31c 2921088 

Bug#895723: marked as done (librsvg: FTBFS on powerpc arches)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 17:30:17 +
with message-id 
and subject line Bug#895723: fixed in librsvg 2.44.8-2
has caused the Debian Bug report #895723,
regarding librsvg: FTBFS on powerpc arches
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.)


-- 
895723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librsvg
Version: 2.42.3-1
Severity: important
Tags: upstream

Building 2.42.3 on Debian experimental ppc64el. powerpc and ppc64  seem to have 
the same issues.

Possibly due to linking with --as-needed . However not sure why this only 
affects the powerpc arches.

Full ppc64el logs: 
https://buildd.debian.org/status/fetch.php?pkg=librsvg=ppc64el=2.42.3-1=1522565714=0

error: linking with `cc` failed: exit code: 1
  |
  = note: "cc" "-Wl,--as-needed" "-Wl,-z,noexecstack" "-m64" "-L" 
"/usr/lib/rustlib/powerpc64le-unknown-linux-gnu/lib" 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.102je7u62sm4kcw.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.10tn6hsfx4oyxjjj.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.114xigf1yyw2gcw0.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.120svpnd23nxqi5a.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.121owdsfzatxhhbm.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.12f5ifttr58vfevz.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.12um7e2pna88us0m.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.155oupk9ie2lc4fq.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.15dl3imwo0d8mnfv.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1686o3u9d63jdfh.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.16g72hl54zgn1037.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.16u6js6g0l3k1ic6.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.17d4cze32tp9xnyn.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1aoz9ryfspmhujr6.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1bcme1fmkrokil8a.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1chjqw8w9cqnfli7.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1epb5nyi41no37ob.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1g1d239vtessmzk5.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1ghfiig2h76dl8qp.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1hkyhrtkifakvrh4.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1i2m4tc5uehwthvl.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1im38lueib99jsk0.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1iyvqxtdjb3fwkh7.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1jnlhyxj59jycbjv.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1kzmobth8vrv86p7.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1liaz5pb3qsa45z.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1mbrod7fypeh96bo.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1mvmz58owquyropc.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1nyfdlp3jd783n7g.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1o6b1la7g4jnv39b.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1owmwuuo26nlf4g0.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1q8ffos2d96smbjs.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1r8x652sazw5kewv.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1rmm85xvb873qftb.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1s9l6wh3i035yuij.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1uacw3k3wfmrurex.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1wjzcbl1bqerhxx0.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1y16o1qfye96o7m0.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1y4ds2ij7sm8xk5g.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1ygj72qs8o1veaeq.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1ynya56gfonq4yrh.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1zeawhkbeobww1zn.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.1zwd8n7bcl3vhvvh.rcgu.o"
 
"/<>/target/debug/deps/rsvg_internals-465b402de8c64098.20v6ib4511rnk9ng.rcgu.o"
 

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 912680 912721
Bug #912680 [libasound2-plugins] libasound2-plugins: broken symlinks in 
/etc/alsa/conf.d
Bug #912680 [libasound2-plugins] libasound2-plugins: broken symlinks in 
/etc/alsa/conf.d
Marked as found in versions alsa-plugins/1.1.7-1.
Bug #912721 [libasound2-plugins] libasound2-plugins: Sound no longer works 
after latest update
Bug #912726 [libasound2-plugins] alsa-lib: update created /etc/alsa/conf.d 
directory filled with broken symlinks to /usr/share/alsa/alsa.conf.d
Bug #912755 [libasound2-plugins] cannot access file 
/etc/alsa/conf.d/10-rate-lav.conf
Merged 912680 912721 912726 912755
> thanks
Stopping processing here.

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

Processed (with 1 error): re: libasound2-plugins: broken symlinks in /etc/alsa/conf.d

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #912680 [pulseaudio] pulseaudio: No sound anymore (broken symlink)
Severity set to 'grave' from 'important'
> reassign -1 libasound2-plugins
Bug #912680 [pulseaudio] pulseaudio: No sound anymore (broken symlink)
Bug reassigned from package 'pulseaudio' to 'libasound2-plugins'.
No longer marked as found in versions pulseaudio/12.2-2.
Ignoring request to alter fixed versions of bug #912680 to the same values 
previously set
> retitle -1 libasound2-plugins: broken symlinks in /etc/alsa/conf.d
Bug #912680 [libasound2-plugins] pulseaudio: No sound anymore (broken symlink)
Changed Bug title to 'libasound2-plugins: broken symlinks in /etc/alsa/conf.d' 
from 'pulseaudio: No sound anymore (broken symlink)'.
> found 1 1.1.7-1
Failed to add found on 1: Unable to read any bugs successfully.


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

Bug#859784: NMU for validns

[Christoph Biedl]

Sebastian Andrzej Siewior wrote...

> BN_bin2bn() and EVP_MD_CTX_new() which were introduced as part of this
> patch may return NULL. Not a single instance in the patch checks the
> return value. This is just sloppy.

As I'd still like to fix validns for Debian: Mind I ask you for review
of the updated patch below? Are there more flaky things in the openssl
adjustment patch beside those you've mentioned?

As this is a NMU, I'd like to keep the change small, hence I blatantly
ignored "The whole locking callbacks and memory allocation is not
required for 1.1" remark since, as far as I understand it, this does
no harm. Marking pthreads_thread_id and pthreads_locking_callback as
non-static is required to avoid a compiler error.

Changes:

* Adjust whitespace to upstream form
* Catch failure from library calls in three places

By the way, #897882 will see a nicer solution as well.

Regards,

Christoph

Subject: Build against openssl 1.1.
Author: Chris West 
Bug: https://github.com/tobez/validns/pull/64
Bug-Debian: https://bugs.debian.org/859784
Last-Update: 2018-11-03

--- a/dnskey.c
+++ b/dnskey.c
@@ -154,6 +154,7 @@
unsigned int e_bytes;
unsigned char *pk;
int l;
+   BIGNUM *n, *e;
 
rsa = RSA_new();
if (!rsa)
@@ -174,11 +175,14 @@
if (l < e_bytes) /* public key is too short */
goto done;
 
-   rsa->e = BN_bin2bn(pk, e_bytes, NULL);
+   e = BN_bin2bn(pk, e_bytes, NULL);
+   if (e == NULL) goto done;
pk += e_bytes;
l -= e_bytes;
 
-   rsa->n = BN_bin2bn(pk, l, NULL);
+   n = BN_bin2bn(pk, l, NULL);
+   if (n == NULL) goto done;
+   RSA_set0_key(rsa, n, e, NULL);
 
pkey = EVP_PKEY_new();
if (!pkey)
--- a/nsec3checks.c
+++ b/nsec3checks.c
@@ -28,7 +28,7 @@
 static struct binary_data name2hash(char *name, struct rr *param)
 {
 struct rr_nsec3param *p = (struct rr_nsec3param *)param;
-   EVP_MD_CTX ctx;
+   EVP_MD_CTX *ctx;
unsigned char md0[EVP_MAX_MD_SIZE];
unsigned char md1[EVP_MAX_MD_SIZE];
unsigned char *md[2];
@@ -45,22 +45,24 @@
 
/* XXX Maybe use Init_ex and Final_ex for speed? */
 
-   EVP_MD_CTX_init();
-   if (EVP_DigestInit(, EVP_sha1()) != 1)
+   ctx = EVP_MD_CTX_new();
+   if (ctx == NULL) return r;
+   if (EVP_DigestInit(ctx, EVP_sha1()) != 1)
return r;
-   digest_size = EVP_MD_CTX_size();
-   EVP_DigestUpdate(, wire_name.data, wire_name.length);
-   EVP_DigestUpdate(, p->salt.data, p->salt.length);
-   EVP_DigestFinal(, md[mdi], NULL);
+   digest_size = EVP_MD_CTX_size(ctx);
+   EVP_DigestUpdate(ctx, wire_name.data, wire_name.length);
+   EVP_DigestUpdate(ctx, p->salt.data, p->salt.length);
+   EVP_DigestFinal(ctx, md[mdi], NULL);
 
for (i = 0; i < p->iterations; i++) {
-   if (EVP_DigestInit(, EVP_sha1()) != 1)
+   if (EVP_DigestInit(ctx, EVP_sha1()) != 1)
return r;
-   EVP_DigestUpdate(, md[mdi], digest_size);
+   EVP_DigestUpdate(ctx, md[mdi], digest_size);
mdi = (mdi + 1) % 2;
-   EVP_DigestUpdate(, p->salt.data, p->salt.length);
-   EVP_DigestFinal(, md[mdi], NULL);
+   EVP_DigestUpdate(ctx, p->salt.data, p->salt.length);
+   EVP_DigestFinal(ctx, md[mdi], NULL);
}
+   EVP_MD_CTX_free(ctx);
 
r.length = digest_size;
r.data = getmem(digest_size);
--- a/rrsig.c
+++ b/rrsig.c
@@ -26,7 +26,7 @@
 struct verification_data
 {
struct verification_data *next;
-   EVP_MD_CTX ctx;
+   EVP_MD_CTX *ctx;
struct rr_dnskey *key;
struct rr_rrsig *rr;
int ok;
@@ -180,7 +180,7 @@
if (d) {
int r;
d->next = NULL;
-   r = EVP_VerifyFinal(>ctx, (unsigned char 
*)d->rr->signature.data, d->rr->signature.length, d->key->pkey);
+   r = EVP_VerifyFinal(d->ctx, (unsigned char 
*)d->rr->signature.data, d->rr->signature.length, d->key->pkey);
if (r == 1) {
d->ok = 1;
} else {
@@ -232,7 +232,7 @@
} else {
int r;
G.stats.signatures_verified++;
-   r = EVP_VerifyFinal(>ctx, (unsigned char 
*)d->rr->signature.data, d->rr->signature.length, d->key->pkey);
+   r = EVP_VerifyFinal(d->ctx, (unsigned char 
*)d->rr->signature.data, d->rr->signature.length, d->key->pkey);
if (r == 1) {
d->ok = 1;
} else {
@@ -250,21 +250,21 @@
struct rr *signed_rr;
int i;
 
-   EVP_MD_CTX_init(>ctx);
+   d->ctx = EVP_MD_CTX_new();
   

Bug#912755: Same here

[david]

I too have no sound since upgrading alsa packages today. All the files
linked to from /etc/alsa/conf.d/ to /usr/share/alsa/alsa.conf.d/ do not
exist. This is on a Devuan PC. Three other Debian PCs do NOT have
an /etc/alsa/conf.d/ folder but work OK. They have not been updated
today.

davcefai

Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O

[Scott Kitterman]

On Wed, 25 Jul 2018 22:03:46 +0200 Sebastian Andrzej Siewior 
 wrote:
> On 2018-07-25 12:14:17 [+0900], Marc Dequènes (duck) wrote:
> > Quack,
> > 
> > I did not try to switch on ScanOnAccess on my production system, but with my
> > configuration, which is not that different, I do not have the problem.
> > 
> > I just tried loading Adam's configuration on another system to test the
> > ScanOnAccess, copied a clamav test file in one of the protected directory
> > and hit the problem. After that the whole machine becomes totally
> > unresponsive in a few seconds.
> 
> okay, that is good to know.
> 
> > I am using kernel 4.16.16-2~bpo9+1 on this machine.
> 
> Yeah. That "deadlock" message is only printed on Debian's kernel.

Does anyone still have this problem with 0.100.2?  It's been out awhile and 
this bug has gone quiet.

Scott K

Bug#909225: marked as done (enigmail cannot be installed on stretch)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 17:02:08 +
with message-id 
and subject line Bug#909000: fixed in enigmail 2:2.0.8-5~deb9u1
has caused the Debian Bug report #909000,
regarding enigmail cannot be installed on stretch
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.)


-- 
909000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: enigmail
Version: enigmail cannot be installed on stretch
Severity: important

Dear Maintainer,

since the recent security update of thunderbird 52 -> 60, enigmail can no
longer be installed on stretch because
enigmail (currently version 1.9.9) requires thunderbird >=52, but thunderbird
60 breaks enigmail <2

Thanks, Daniel



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

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

Versions of packages enigmail depends on:
ii  gnupg  2.1.18-8~deb9u2
ii  gnupg-agent2.1.18-8~deb9u2
ii  thunderbird [icedove]  1:60.0-3~deb9u1

Versions of packages enigmail recommends:
ii  pinentry-gnome3 [pinentry-x11]  1.0.0-2
ii  pinentry-gtk2 [pinentry-x11]1.0.0-2

enigmail suggests no packages.
--- End Message ---
--- Begin Message ---
Source: enigmail
Source-Version: 2:2.0.8-5~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated enigmail 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 00:41:43 -0400
Source: enigmail
Binary: enigmail
Architecture: source
Version: 2:2.0.8-5~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Daniel Kahn Gillmor 
Description:
 enigmail   - GPG support for Thunderbird and Debian Icedove
Closes: 909000
Changes:
 enigmail (2:2.0.8-5~deb9u1) stretch; urgency=medium
 .
   * Rebuild for stretch (Closes: #909000)
Checksums-Sha1:
 3179afe9772c04a2e314989354a4496dd1613123 1574 enigmail_2.0.8-5~deb9u1.dsc
 eb6b4a590625f3cffde5fcc23cc08f385d47cec7 55500 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 589707c57c82901212582785a8a13062d5fbd9ac 6969 
enigmail_2.0.8-5~deb9u1_source.buildinfo
Checksums-Sha256:
 842309c8db3788a6ed6470e62cd1f46876b24200eb88bf20d467b60156d4b215 1574 
enigmail_2.0.8-5~deb9u1.dsc
 b5bf9f929027788c769a079275b0c6a03795205c56ba4a6852c79c94e087d31e 55500 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 6beb8124f299e3f1e8703b7eb8a4b1045e676a5a7f3d9d337b22e9e22b766e65 6969 
enigmail_2.0.8-5~deb9u1_source.buildinfo
Files:
 62712022b6ab37c993ebb4fa53c5190f 1574 mail optional enigmail_2.0.8-5~deb9u1.dsc
 c769509dfc927696baa182e1a27c8528 55500 mail optional 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 a79cb4e717ac0a3b865d9568b2868516 6969 mail optional 
enigmail_2.0.8-5~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCW9jHpwAKCRBsHx7ezFD6
UzWjAP9l0FKYJTeygogT9xpN+vEcQKmxcgcnxKKuBPcfKw3AjAEA9yWevofPb1xd
Rnc9P3Uo4tWiX4bD5vbsCmUuITw7FgI=
=Ubu3
-END PGP SIGNATURE End Message ---

Bug#909816: marked as done (dependency issues - enigmail : Depends: thunderbird (>= 1:52.0) but it is not going to be installed or)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 17:02:08 +
with message-id 
and subject line Bug#909000: fixed in enigmail 2:2.0.8-5~deb9u1
has caused the Debian Bug report #909000,
regarding dependency issues - enigmail : Depends: thunderbird (>= 1:52.0) but 
it is not going to be installed or
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.)


-- 
909000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: enigmail
Severity: grave
X-Debbugs-CC: whonix-de...@whonix.org

Happening on Debian stretch.

sudo apt-get install enigmail
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 enigmail : Depends: thunderbird (>= 1:52.0) but it is not going to be
installed or
 icedove (>= 1:52.0)
E: Unable to correct problems, you have held broken packages.
--- End Message ---
--- Begin Message ---
Source: enigmail
Source-Version: 2:2.0.8-5~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated enigmail 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 00:41:43 -0400
Source: enigmail
Binary: enigmail
Architecture: source
Version: 2:2.0.8-5~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Daniel Kahn Gillmor 
Description:
 enigmail   - GPG support for Thunderbird and Debian Icedove
Closes: 909000
Changes:
 enigmail (2:2.0.8-5~deb9u1) stretch; urgency=medium
 .
   * Rebuild for stretch (Closes: #909000)
Checksums-Sha1:
 3179afe9772c04a2e314989354a4496dd1613123 1574 enigmail_2.0.8-5~deb9u1.dsc
 eb6b4a590625f3cffde5fcc23cc08f385d47cec7 55500 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 589707c57c82901212582785a8a13062d5fbd9ac 6969 
enigmail_2.0.8-5~deb9u1_source.buildinfo
Checksums-Sha256:
 842309c8db3788a6ed6470e62cd1f46876b24200eb88bf20d467b60156d4b215 1574 
enigmail_2.0.8-5~deb9u1.dsc
 b5bf9f929027788c769a079275b0c6a03795205c56ba4a6852c79c94e087d31e 55500 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 6beb8124f299e3f1e8703b7eb8a4b1045e676a5a7f3d9d337b22e9e22b766e65 6969 
enigmail_2.0.8-5~deb9u1_source.buildinfo
Files:
 62712022b6ab37c993ebb4fa53c5190f 1574 mail optional enigmail_2.0.8-5~deb9u1.dsc
 c769509dfc927696baa182e1a27c8528 55500 mail optional 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 a79cb4e717ac0a3b865d9568b2868516 6969 mail optional 
enigmail_2.0.8-5~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCW9jHpwAKCRBsHx7ezFD6
UzWjAP9l0FKYJTeygogT9xpN+vEcQKmxcgcnxKKuBPcfKw3AjAEA9yWevofPb1xd
Rnc9P3Uo4tWiX4bD5vbsCmUuITw7FgI=
=Ubu3
-END PGP SIGNATURE End Message ---

Bug#909000: marked as done (Enigmail 2.0 needed in Stretch after Thunderbird 60 upload)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 17:02:08 +
with message-id 
and subject line Bug#909000: fixed in enigmail 2:2.0.8-5~deb9u1
has caused the Debian Bug report #909000,
regarding Enigmail 2.0 needed in Stretch after Thunderbird 60 upload
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.)


-- 
909000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: enigmail
Version: 2:1.9.9-1~deb9u1
Severity: grave

Dear maintainers,

yesterday, Thunderbird 1:60.0-2~deb9u1 got uploaded to Stretch (via
security). This thunderbird version breaks enigmail (<< 2:2~), which
leads to uninstallable/unusable Enigmail in Debian Stretch.

May I suggest to backport Enigmail 2.0 to Debian Stretch as well?

Cheers
 jonas

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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: enigmail
Source-Version: 2:2.0.8-5~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated enigmail 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 00:41:43 -0400
Source: enigmail
Binary: enigmail
Architecture: source
Version: 2:2.0.8-5~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Daniel Kahn Gillmor 
Description:
 enigmail   - GPG support for Thunderbird and Debian Icedove
Closes: 909000
Changes:
 enigmail (2:2.0.8-5~deb9u1) stretch; urgency=medium
 .
   * Rebuild for stretch (Closes: #909000)
Checksums-Sha1:
 3179afe9772c04a2e314989354a4496dd1613123 1574 enigmail_2.0.8-5~deb9u1.dsc
 eb6b4a590625f3cffde5fcc23cc08f385d47cec7 55500 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 589707c57c82901212582785a8a13062d5fbd9ac 6969 
enigmail_2.0.8-5~deb9u1_source.buildinfo
Checksums-Sha256:
 842309c8db3788a6ed6470e62cd1f46876b24200eb88bf20d467b60156d4b215 1574 
enigmail_2.0.8-5~deb9u1.dsc
 b5bf9f929027788c769a079275b0c6a03795205c56ba4a6852c79c94e087d31e 55500 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 6beb8124f299e3f1e8703b7eb8a4b1045e676a5a7f3d9d337b22e9e22b766e65 6969 
enigmail_2.0.8-5~deb9u1_source.buildinfo
Files:
 62712022b6ab37c993ebb4fa53c5190f 1574 mail optional enigmail_2.0.8-5~deb9u1.dsc
 c769509dfc927696baa182e1a27c8528 55500 mail optional 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 a79cb4e717ac0a3b865d9568b2868516 6969 mail optional 
enigmail_2.0.8-5~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCW9jHpwAKCRBsHx7ezFD6
UzWjAP9l0FKYJTeygogT9xpN+vEcQKmxcgcnxKKuBPcfKw3AjAEA9yWevofPb1xd
Rnc9P3Uo4tWiX4bD5vbsCmUuITw7FgI=
=Ubu3
-END PGP SIGNATURE End Message ---

Bug#909081: marked as done ([enigmail] impossible install enigmail)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 17:02:08 +
with message-id 
and subject line Bug#909000: fixed in enigmail 2:2.0.8-5~deb9u1
has caused the Debian Bug report #909000,
regarding [enigmail] impossible install enigmail
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.)


-- 
909000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: enigmail
Version: 2:1.9.9-1~deb9u1
Severity: important

--- Please enter the report below this line. ---

dear All,
the last upgrade has removed the enigmail package and it is impossible
to install it using apt!

Command 1131 of 12 #apt install enigmail
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 thunderbird : Breaks: enigmail (< 2:2~) but 2:1.9.9-1~deb9u1 is to be
installed
   Recommends: lightning (= 1:60.0-3~deb9u1) but it is not
going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held packages.


Command 1134 of 15 #apt-show-versions thunderbird
thunderbird:amd64/stretch 1:60.0-3~deb9u1 uptodate
thunderbird:i386 not installed

Please resolve the problem.

Best
Marco

--- System information. ---
Architecture: Kernel:   Linux 4.9.0-8-amd64

Debian Release: 9.5
  500 xenial  updates.signal.org   500 stable-updates
ftp.it.debian.org   500 stable  security.debian.org   500 stable
 repo.skype.com   500 stable  packages.microsoft.com
500 stable  ftp.it.debian.org   500 stable  deb.debian.org
--- Package information. ---
Depends(Version) | Installed
-+-=
gnupg(>= 2)  | 2.1.18-8~deb9u2
 OR gnupg2   | 2.1.18-8~deb9u2
gnupg-agent  | 2.1.18-8~deb9u2
thunderbird (>= 1:52.0)  | 1:60.0-3~deb9u1
 OR icedove  (>= 1:52.0) |

Recommends(Version) | Installed
===-+-===
pinentry-x11|

Package's Suggests field is empty.


-- 
Think Marco, think different
--- End Message ---
--- Begin Message ---
Source: enigmail
Source-Version: 2:2.0.8-5~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated enigmail 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 00:41:43 -0400
Source: enigmail
Binary: enigmail
Architecture: source
Version: 2:2.0.8-5~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Daniel Kahn Gillmor 
Description:
 enigmail   - GPG support for Thunderbird and Debian Icedove
Closes: 909000
Changes:
 enigmail (2:2.0.8-5~deb9u1) stretch; urgency=medium
 .
   * Rebuild for stretch (Closes: #909000)
Checksums-Sha1:
 3179afe9772c04a2e314989354a4496dd1613123 1574 enigmail_2.0.8-5~deb9u1.dsc
 eb6b4a590625f3cffde5fcc23cc08f385d47cec7 55500 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 589707c57c82901212582785a8a13062d5fbd9ac 6969 
enigmail_2.0.8-5~deb9u1_source.buildinfo
Checksums-Sha256:
 842309c8db3788a6ed6470e62cd1f46876b24200eb88bf20d467b60156d4b215 1574 
enigmail_2.0.8-5~deb9u1.dsc
 b5bf9f929027788c769a079275b0c6a03795205c56ba4a6852c79c94e087d31e 55500 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 6beb8124f299e3f1e8703b7eb8a4b1045e676a5a7f3d9d337b22e9e22b766e65 6969 
enigmail_2.0.8-5~deb9u1_source.buildinfo
Files:
 62712022b6ab37c993ebb4fa53c5190f 1574 mail optional enigmail_2.0.8-5~deb9u1.dsc
 c769509dfc927696baa182e1a27c8528 55500 mail optional 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 a79cb4e717ac0a3b865d9568b2868516 6969 mail optional 

Bug#909001: marked as done (enigmail: Enigmail get uninstalled while upgrading thunderbird (60.0-3~deb9u1))

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 17:02:08 +
with message-id 
and subject line Bug#909000: fixed in enigmail 2:2.0.8-5~deb9u1
has caused the Debian Bug report #909000,
regarding enigmail: Enigmail get uninstalled while upgrading thunderbird 
(60.0-3~deb9u1)
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.)


-- 
909000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: enigmail
Version: 2:1.9.9-1~deb9u1
Severity: important

Dear Maintainer,


Today, all my users have trouble reading their encrypted emails, because
the last upgrade of thunderbird from security.debian.org on 16/09/2018 breaks 
enigmail (and a lot of other things). 

apt show thunderbird
[...]
Breaks: [...]  enigmail (<<2:2~), [...]
[...]

Automatic Upgrade of my systems removed enigmail everywhere. 

An upgrade would be usefull.

Cheers

Pierre


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

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

Versions of packages enigmail depends on:
ii  gnupg  2.1.18-8~deb9u2
ii  gnupg-agent2.1.18-8~deb9u2
ii  gnupg2 2.1.18-8~deb9u2
ii  icedove1:60.0-3~deb9u1
ii  thunderbird [icedove]  1:60.0-3~deb9u1

Versions of packages enigmail recommends:
ii  pinentry-gnome3 [pinentry-x11]  1.0.0-2
ii  pinentry-gtk2 [pinentry-x11]1.0.0-2

enigmail suggests no packages.
--- End Message ---
--- Begin Message ---
Source: enigmail
Source-Version: 2:2.0.8-5~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated enigmail 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 00:41:43 -0400
Source: enigmail
Binary: enigmail
Architecture: source
Version: 2:2.0.8-5~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Daniel Kahn Gillmor 
Description:
 enigmail   - GPG support for Thunderbird and Debian Icedove
Closes: 909000
Changes:
 enigmail (2:2.0.8-5~deb9u1) stretch; urgency=medium
 .
   * Rebuild for stretch (Closes: #909000)
Checksums-Sha1:
 3179afe9772c04a2e314989354a4496dd1613123 1574 enigmail_2.0.8-5~deb9u1.dsc
 eb6b4a590625f3cffde5fcc23cc08f385d47cec7 55500 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 589707c57c82901212582785a8a13062d5fbd9ac 6969 
enigmail_2.0.8-5~deb9u1_source.buildinfo
Checksums-Sha256:
 842309c8db3788a6ed6470e62cd1f46876b24200eb88bf20d467b60156d4b215 1574 
enigmail_2.0.8-5~deb9u1.dsc
 b5bf9f929027788c769a079275b0c6a03795205c56ba4a6852c79c94e087d31e 55500 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 6beb8124f299e3f1e8703b7eb8a4b1045e676a5a7f3d9d337b22e9e22b766e65 6969 
enigmail_2.0.8-5~deb9u1_source.buildinfo
Files:
 62712022b6ab37c993ebb4fa53c5190f 1574 mail optional enigmail_2.0.8-5~deb9u1.dsc
 c769509dfc927696baa182e1a27c8528 55500 mail optional 
enigmail_2.0.8-5~deb9u1.debian.tar.xz
 a79cb4e717ac0a3b865d9568b2868516 6969 mail optional 
enigmail_2.0.8-5~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCW9jHpwAKCRBsHx7ezFD6
UzWjAP9l0FKYJTeygogT9xpN+vEcQKmxcgcnxKKuBPcfKw3AjAEA9yWevofPb1xd
Rnc9P3Uo4tWiX4bD5vbsCmUuITw7FgI=
=Ubu3
-END PGP SIGNATURE End Message ---

Bug#895723: Bug #895723 in librsvg marked as pending

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #895723 in librsvg 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/gnome-team/librsvg/commit/3b1ea4152032f7c377688703d78fcb944be9


Workaround for tests compilation failure on powerpc arches (Closes: #895723)

Forcing incremental build only for tests that fail to build.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/895723

Processed: Bug #895723 in librsvg marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #895723 [src:librsvg] librsvg: FTBFS on powerpc arches
Added tag(s) pending.

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

Bug#897845: marked as done (repsnapper: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 16:24:19 +
with message-id 
and subject line Bug#897845: fixed in vmmlib 1.0-2.1
has caused the Debian Bug report #897845,
regarding repsnapper: ftbfs with GCC-8
to be marked as done.

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

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


-- 
897845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:repsnapper
Version: 2.5a5-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/repsnapper_2.5a5-1_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
^
/usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:60:8: warning: unnecessary 
parentheses in declaration of '__gtk_reserved2' [-Wparentheses]
   void (*__gtk_reserved2);
^
/usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:61:8: warning: unnecessary 
parentheses in declaration of '__gtk_reserved3' [-Wparentheses]
   void (*__gtk_reserved3);
^
/usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:62:8: warning: unnecessary 
parentheses in declaration of '__gtk_reserved4' [-Wparentheses]
   void (*__gtk_reserved4);
^
/usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:63:8: warning: unnecessary 
parentheses in declaration of '__gtk_reserved5' [-Wparentheses]
   void (*__gtk_reserved5);
^
/usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:64:8: warning: unnecessary 
parentheses in declaration of '__gtk_reserved6' [-Wparentheses]
   void (*__gtk_reserved6);
^
/usr/include/gtk-2.0/gtk/gtkfilechooserbutton.h:65:8: warning: unnecessary 
parentheses in declaration of '__gtk_reserved7' [-Wparentheses]
   void (*__gtk_reserved7);
^
In file included from /usr/include/gtk-2.0/gtk/gtk.h:173,
 from /usr/include/gtkmm-2.4/gtkmm/box.h:44,
 from /usr/include/gtkmm-2.4/gtkmm.h:91,
 from src/stdafx.h:54,
 from src/transform3d.h:22,
 from src/transform3d.cpp:21:
/usr/include/gtk-2.0/gtk/gtkstatusicon.h:76:8: warning: unnecessary parentheses 
in declaration of '__gtk_reserved1' [-Wparentheses]
   void (*__gtk_reserved1);
^
/usr/include/gtk-2.0/gtk/gtkstatusicon.h:77:8: warning: unnecessary parentheses 
in declaration of '__gtk_reserved2' [-Wparentheses]
   void (*__gtk_reserved2);
^
In file included from /usr/include/vmmlib/vmmlib.hpp:26,
 from src/stdafx.h:59,
 from src/transform3d.h:22,
 from src/transform3d.cpp:21:
/usr/include/vmmlib/quaternion.hpp: In member function 'void 
vmml::quaternion::operator-=(const vmml::vector<3, T>&)':
/usr/include/vmmlib/quaternion.hpp:760:10: error: return-statement with a 
value, in function returning 'void' [-fpermissive]
  return *this;
  ^~~~
make[4]: *** [Makefile:1758: src/repsnapper-transform3d.o] Error 1
make[4]: Leaving directory '/<>'
make[3]: *** [Makefile:2417: all-recursive] Error 1
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:860: all] Error 2
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: vmmlib
Source-Version: 1.0-2.1

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

A summary of the changes between this 

Bug#910448: marked as done (mgetty: CVE-2018-16741)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 16:23:50 +
with message-id 
and subject line Bug#910448: fixed in mgetty 1.2.1-1
has caused the Debian Bug report #910448,
regarding mgetty: CVE-2018-16741
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.)


-- 
910448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mgetty
Version: 1.1.36-1
Severity: grave
Tags: patch security upstream
Control: fixed -1 1.1.36-3+deb9u1

Hi,

The following vulnerability was published for mgetty.

CVE-2018-16741[0]:
| An issue was discovered in mgetty before 1.2.1. In fax/faxq-helper.c,
| the function do_activate() does not properly sanitize shell
| metacharacters to prevent command injection. It is possible to use the
| ||, , or  characters within a file created by the "faxq-helper
| activate jobid" command.

The issue was fixed in DSA-4291-1 with 1.1.36-3+deb9u1 but not yet in
unstable and for buster, thus filling an RC bug to avoid the
regression for buster.

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-16741
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16741

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mgetty
Source-Version: 1.2.1-1

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

Debian distribution maintenance software
pp.
Andreas Barth  (supplier of updated mgetty package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Oct 2018 22:17:07 +0200
Source: mgetty
Binary: mgetty mgetty-fax mgetty-viewfax mgetty-voice mgetty-pvftools 
mgetty-docs
Architecture: source all
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Andreas Barth 
Changed-By: Andreas Barth 
Description:
 mgetty - Smart Modem getty replacement
 mgetty-docs - Documentation Package for mgetty
 mgetty-fax - Faxing tools for mgetty
 mgetty-pvftools - Programs for listening and manipulating pvf and rmd files
 mgetty-viewfax - Program for displaying Group-3 Fax files under X
 mgetty-voice - Voicemail handler for mgetty
Closes: 910448
Changes:
 mgetty (1.2.1-1) unstable; urgency=medium
 .
   * Bump upstream version to 1.2.1, amongst others:
 Harden faxq and faxrunq and others, fixes
 CVE-2018-16745, CVE-2018-16744, CVE-2018-16741, CVE-2018-16743, 
CVE-2018-16742.
 Closes: #910448
Checksums-Sha1:
 089ad42d3ce039bd8f0928943ad4e6a74c1773ec 1456 mgetty_1.2.1-1.dsc
 0c10b1e47101bebefcf01505b4fd537a4f66a2a7 1236903 mgetty_1.2.1-1.tar.gz
 c583cf091f6199ebf99b3ab6ebf42f3930869d97 517244 mgetty-docs_1.2.1-1_all.deb
Checksums-Sha256:
 c0daa01eb52ab56da8ca72dd0394434dac1e69d3d1c9e174adb9dc7305a314c0 1456 
mgetty_1.2.1-1.dsc
 72c3ba7671a6534ac67f710199d7a746c22bec60416c9d60583fd0bf7e6ca2fe 1236903 
mgetty_1.2.1-1.tar.gz
 49244dbfc7bccc9c512f6e78c8df69b6e096d2d43976d2adfe3a22726aeb81dd 517244 
mgetty-docs_1.2.1-1_all.deb
Files:
 013c33bb14fe71846c2e8ff363b5e3a1 1456 comm optional mgetty_1.2.1-1.dsc
 a78bf8b2e264d68369fedb642ac3dd22 1236903 comm optional mgetty_1.2.1-1.tar.gz
 d8fd7bedd8f2f17afe595f2d061435f9 517244 doc optional 
mgetty-docs_1.2.1-1_all.deb

-BEGIN PGP SIGNATURE-

iQFDBAEBCAAtFiEEwDoy7x/3mxHvqB7o2u/AWm2EZI4FAlvdw8gPHGFiYUBkZWJp
YW4ub3JnAAoJENrvwFpthGSO/d0H/1ATXFnm2vshasVpPY7fSuF1UTT42TK2SsJ6
PVBShw+scdQAOY+0qv3iCPRMHX3nB8Jx8fWZ1Jly1aInCMeyERtFoWES5Btyto+J
uxlKS3YrbcFkFkNmOrI+r6GfZl1N5BXIQWwRGLZyEjFhpMMMQAIzBJjKEUHTVMoz
JzTMgfRZ1+/yT206Z1SAxrCQoJK9f0cGCsjf6R1BVs7MZEoHKFmuxcuKLb+JRd4I
1mdghOQg5o7oy3u0No9xgNLF+IRFWDav+sx06o+wVHGBpC8wnFHpA1W8rzhok8ri
jgjFm741Jz/u+NgkYGD7xcDB+BQheQjdAh4yeQmnKoJD10KGkNI=
=7htZ
-END PGP SIGNATURE End Message ---

Bug#834472: marked as done (vmmlib: FTBFS: stdlib.h:774:12: error: expected unqualified-id before 'int')

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 16:24:19 +
with message-id 
and subject line Bug#834472: fixed in vmmlib 1.0-2.1
has caused the Debian Bug report #834472,
regarding vmmlib: FTBFS: stdlib.h:774:12: error: expected unqualified-id before 
'int'
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.)


-- 
834472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vmmlib
Version: 1.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

vmmlib fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  vmmlib
   Version:  1.0-2
   Build architecture:   amd64
   Date: Tue, 16 Aug 2016 01:17:41 +0100
   Hostname: bfbc6cea94fe
   Uname:Linux bfbc6cea94fe 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 
(2016-07-18) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'vmmlib-build-deps' in 
'../vmmlib-build-deps_1.0-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package vmmlib-build-deps.
  (Reading database ... 23237 files and directories currently installed.)
  Preparing to unpack vmmlib-build-deps_1.0-2_all.deb ...
  Unpacking vmmlib-build-deps (1.0-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
gfortran gfortran-6 libblas-common libblas-dev libblas3 libf2c2 libf2c2-dev
libgfortran-6-dev libgfortran3 liblapack-dev liblapack3
  Suggested packages:
gfortran-multilib gfortran-doc gfortran-6-multilib gfortran-6-doc
libgfortran3-dbg libcoarrays-dev liblapack-doc-man liblapack-doc
  The following NEW packages will be installed:
gfortran gfortran-6 libblas-common libblas-dev libblas3 libf2c2 libf2c2-dev
libgfortran-6-dev libgfortran3 liblapack-dev liblapack3
  0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 36.6 MB of archives.
  After this operation, 177 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 libgfortran3 amd64 
6.1.1-11 [265 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libblas-common amd64 
3.6.1-2 [13.9 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libblas3 amd64 
3.6.1-2 [157 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libgfortran-6-dev 
amd64 6.1.1-11 [296 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 gfortran-6 amd64 
6.1.1-11 [31.7 MB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 gfortran amd64 
4:6.1.1-1 [1352 B]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libblas-dev amd64 
3.6.1-2 [18.9 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 liblapack3 amd64 
3.6.1-2 [1963 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 liblapack-dev amd64 
3.6.1-2 [1977 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 libf2c2 amd64 
20130926-2 [123 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 libf2c2-dev amd64 
20130926-2 [129 kB]
  Fetched 36.6 MB in 0s (49.3 MB/s)
  Selecting previously unselected package libgfortran3:amd64.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading 

Bug#911361: FTBFS in Debian unstable

[Guido Günther]

Hi,
On Fri, Oct 19, 2018 at 06:03:41AM +, Ondřej Surý wrote:
> Package: src:kopanocore
> Version: 8.6.5-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> the gcc transition made the package FTBFS again due changed symbols:
> 
> dpkg-gensymbols: warning: the generated symbols file is empty

This is caused by the changes in 911360.
 -- Guido

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

Processed: forcibly merging 911360 911361

[Debian Bug Tracking System]

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

> forcemerge 911360 911361
Bug #911360 [src:kopanocore] FTBFS every time default PHP version is changed
Bug #911361 [src:kopanocore] FTBFS in Debian unstable
Merged 911360 911361
> thanks
Stopping processing here.

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

Processed: Re: [Pkg-alsa-devel] Bug#912755: cannot access file /etc/alsa/conf.d/10-rate-lav.conf

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libasound2-plugins 1.1.7-1
Bug #912755 [alsa-utils] cannot access file /etc/alsa/conf.d/10-rate-lav.conf
Bug reassigned from package 'alsa-utils' to 'libasound2-plugins'.
No longer marked as found in versions alsa-utils/1.1.7-1.
Ignoring request to alter fixed versions of bug #912755 to the same values 
previously set
Bug #912755 [libasound2-plugins] cannot access file 
/etc/alsa/conf.d/10-rate-lav.conf
Marked as found in versions alsa-plugins/1.1.7-1.
> forcemerge 912721 -1
Bug #912721 [libasound2-plugins] libasound2-plugins: Sound no longer works 
after latest update
Bug #912726 [libasound2-plugins] alsa-lib: update created /etc/alsa/conf.d 
directory filled with broken symlinks to /usr/share/alsa/alsa.conf.d
Bug #912755 [libasound2-plugins] cannot access file 
/etc/alsa/conf.d/10-rate-lav.conf
Severity set to 'grave' from 'important'
Bug #912726 [libasound2-plugins] alsa-lib: update created /etc/alsa/conf.d 
directory filled with broken symlinks to /usr/share/alsa/alsa.conf.d
Merged 912721 912726 912755

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

Bug#909818: firefox: Web Content is eating nearly 100% CPU, several of them

[Dirk Griesbach]

Package: fontconfig
Version: 2.13.1-1
Followup-For: Bug #909818

Progress. I had the same problem here(TM). Deleting global and local 
fontconfig cache did not solve the problem.

After clearing the local fontconfig cache, that cache would be recreated 
and it would get an additional amount of cache entries, e.g. every time 
I would start Firefox. In the end, ~/.cache/fontconfig contained around 
38000 files. Looking at their content, they pointed to 
~/.local/share/fonts.

I used custom fonts stored in ~/.local/share/fonts back then but 
currently the directory is empty. After deletion of 
~/.local/share/fonts, the number of files in ~/.cache/fontconfig (After 
clearing this one a final time) stays small and constant and Firefox is 
reacting normal again.

Regards,
Dirk

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

Kernel: Linux 4.19.0 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages fontconfig depends on:
ii  fontconfig-config  2.13.1-1
ii  libc6  2.27-8
ii  libfontconfig1 2.13.1-1
ii  libfreetype6   2.8.1-2

fontconfig recommends no packages.

fontconfig suggests no packages.

-- no debconf information

Bug#912541: marked as done (libjackson-json-java: FTBFS with Java 11 due to javax.activation and JAXB removal)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 15:19:21 +
with message-id 
and subject line Bug#912541: fixed in libjackson-json-java 1.9.2-10
has caused the Debian Bug report #912541,
regarding libjackson-json-java: FTBFS with Java 11 due to javax.activation and 
JAXB removal
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.)


-- 
912541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjackson-json-java
Version: 1.9.2-9
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libjackson-json-java.html

...
compile.xc:
[javac] Using javac -source 1.5 is no longer supported, switching to 6
[javac] Using javac -target 1.5 is no longer supported, switching to 6
[javac] Compiling 7 source files to 
/build/1st/libjackson-json-java-1.9.2/build/classes/xc
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/DataHandlerJsonDeserializer.java:8:
 error: package javax.activation does not exist
[javac] import javax.activation.DataHandler;
[javac]^
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/DataHandlerJsonDeserializer.java:9:
 error: package javax.activation does not exist
[javac] import javax.activation.DataSource;
[javac]^
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/DataHandlerJsonDeserializer.java:20:
 error: cannot find symbol
[javac] extends StdScalarDeserializer
[javac]   ^
[javac]   symbol: class DataHandler
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/DataHandlerJsonDeserializer.java:25:
 error: cannot find symbol
[javac] public DataHandler deserialize(JsonParser jp, 
DeserializationContext ctxt)
[javac]^
[javac]   symbol:   class DataHandler
[javac]   location: class DataHandlerJsonDeserializer
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/DataHandlerJsonSerializer.java:8:
 error: package javax.activation does not exist
[javac] import javax.activation.DataHandler;
[javac]^
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/DataHandlerJsonSerializer.java:20:
 error: cannot find symbol
[javac] public class DataHandlerJsonSerializer extends 
SerializerBase
[javac]   ^
[javac]   symbol: class DataHandler
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/DataHandlerJsonSerializer.java:25:
 error: cannot find symbol
[javac] public void serialize(DataHandler value, JsonGenerator jgen, 
SerializerProvider provider)
[javac]   ^
[javac]   symbol:   class DataHandler
[javac]   location: class DataHandlerJsonSerializer
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/JaxbAnnotationIntrospector.java:8:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBElement;
[javac]  ^
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/JaxbAnnotationIntrospector.java:10:
 error: package javax.xml.bind.annotation.adapters does not exist
[javac] import javax.xml.bind.annotation.adapters.XmlAdapter;
[javac]  ^
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/JaxbAnnotationIntrospector.java:11:
 error: package javax.xml.bind.annotation.adapters does not exist
[javac] import javax.xml.bind.annotation.adapters.XmlJavaTypeAdapter;
[javac]  ^
[javac] 
/build/1st/libjackson-json-java-1.9.2/src/xc/java/org/codehaus/jackson/xc/JaxbAnnotationIntrospector.java:12:
 error: package javax.xml.bind.annotation.adapters does not exist
[javac] import javax.xml.bind.annotation.adapters.XmlJavaTypeAdapters;
[javac]

Bug#911194: libbtm-java: FTBFS with Java 11 due to javax.rmi removal

[Markus Koschany]

libbtm-java looks like a removal candidate for me. Last release was in
2012, project looks pretty much stalled.

https://github.com/bitronix/btm

The only r-dep is ehcache which uses libbtm-java for its tests.



signature.asc
Description: OpenPGP digital signature

Bug#910218: marked as done (libapache2-mod-proxy-uwsgi: copyright file missing after upgrade (policy 12.5))

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 14:53:37 +
with message-id 
and subject line Bug#910218: fixed in apache2 2.4.37-1
has caused the Debian Bug report #910218,
regarding libapache2-mod-proxy-uwsgi: copyright file missing after upgrade 
(policy 12.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.)


-- 
910218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-proxy-uwsgi
Version: 2.4.34-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  stretch -> buster

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

0m43.3s ERROR: WARN: Inadequate results from running adequate!
  libapache2-mod-proxy-uwsgi: missing-copyright-file 
/usr/share/doc/libapache2-mod-proxy-uwsgi/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libapache2-mod-proxy-uwsgi/copyright
  # ls -lad /usr/share/doc/libapache2-mod-proxy-uwsgi
  drwxr-xr-x 2 root root 40 Aug  2 15:26 
/usr/share/doc/libapache2-mod-proxy-uwsgi
  # ls -la /usr/share/doc/libapache2-mod-proxy-uwsgi/
  total 0
  drwxr-xr-x   2 root root   40 Aug  2 15:26 .
  drwxr-xr-x 140 root root 2940 Aug  2 15:26 ..

Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libapache2-mod-proxy-uwsgi_2.4.34-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.37-1

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

Debian distribution maintenance software
pp.
Stefan Fritsch  (supplier of updated apache2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 14:26:31 +0100
Source: apache2
Binary: apache2 apache2-data apache2-bin apache2-utils apache2-suexec-pristine 
apache2-suexec-custom apache2-doc apache2-dev apache2-ssl-dev apache2-dbg 
libapache2-mod-md libapache2-mod-proxy-uwsgi
Architecture: source amd64 all
Version: 2.4.37-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Apache Maintainers 
Changed-By: Stefan Fritsch 
Description:
 apache2- Apache HTTP Server
 apache2-bin - Apache HTTP Server (modules and other binary files)
 apache2-data - Apache HTTP Server (common files)
 apache2-dbg - Apache debugging symbols
 apache2-dev - Apache HTTP Server (development headers)
 apache2-doc - Apache HTTP Server (on-site documentation)
 apache2-ssl-dev - Apache HTTP Server (mod_ssl development headers)
 apache2-suexec-custom - Apache HTTP Server configurable suexec program for 
mod_suexec
 apache2-suexec-pristine - Apache HTTP Server standard suexec program for 
mod_suexec
 apache2-utils - Apache HTTP Server (utility programs for web servers)
 libapache2-mod-md - transitional package
 libapache2-mod-proxy-uwsgi - transitional package
Closes: 910218
Changes:
 apache2 (2.4.37-1) unstable; urgency=medium
 .
   * New upstream version
 - mod_ssl: Add support for TLSv1.3
   * Add docs symlink for libapache2-mod-proxy-uwsgi.  Closes: #910218
   * Update test-framework to r1845652
   * Fix test suite to actually run by 

Bug#910979: marked as done (libapache2-mod-proxy-uwsgi: copyright file missing after upgrade (policy 12.5))

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 14:53:37 +
with message-id 
and subject line Bug#910218: fixed in apache2 2.4.37-1
has caused the Debian Bug report #910218,
regarding libapache2-mod-proxy-uwsgi: copyright file missing after upgrade 
(policy 12.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.)


-- 
910218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-proxy-uwsgi
Version: 2.4.34-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  stretch -> buster

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

0m43.3s ERROR: WARN: Inadequate results from running adequate!
  libapache2-mod-proxy-uwsgi: missing-copyright-file 
/usr/share/doc/libapache2-mod-proxy-uwsgi/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libapache2-mod-proxy-uwsgi/copyright
  # ls -lad /usr/share/doc/libapache2-mod-proxy-uwsgi
  drwxr-xr-x 2 root root 40 Aug  2 15:26 
/usr/share/doc/libapache2-mod-proxy-uwsgi
  # ls -la /usr/share/doc/libapache2-mod-proxy-uwsgi/
  total 0
  drwxr-xr-x   2 root root   40 Aug  2 15:26 .
  drwxr-xr-x 140 root root 2940 Aug  2 15:26 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libapache2-mod-proxy-uwsgi_2.4.34-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.37-1

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

Debian distribution maintenance software
pp.
Stefan Fritsch  (supplier of updated apache2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 14:26:31 +0100
Source: apache2
Binary: apache2 apache2-data apache2-bin apache2-utils apache2-suexec-pristine 
apache2-suexec-custom apache2-doc apache2-dev apache2-ssl-dev apache2-dbg 
libapache2-mod-md libapache2-mod-proxy-uwsgi
Architecture: source amd64 all
Version: 2.4.37-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Apache Maintainers 
Changed-By: Stefan Fritsch 
Description:
 apache2- Apache HTTP Server
 apache2-bin - Apache HTTP Server (modules and other binary files)
 apache2-data - Apache HTTP Server (common files)
 apache2-dbg - Apache debugging symbols
 apache2-dev - Apache HTTP Server (development headers)
 apache2-doc - Apache HTTP Server (on-site documentation)
 apache2-ssl-dev - Apache HTTP Server (mod_ssl development headers)
 apache2-suexec-custom - Apache HTTP Server configurable suexec program for 
mod_suexec
 apache2-suexec-pristine - Apache HTTP Server standard suexec program for 
mod_suexec
 apache2-utils - Apache HTTP Server (utility programs for web servers)
 libapache2-mod-md - transitional package
 libapache2-mod-proxy-uwsgi - transitional package
Closes: 910218
Changes:
 apache2 (2.4.37-1) unstable; urgency=medium
 .
   * New upstream version
 - mod_ssl: Add support for TLSv1.3
   * Add docs symlink for libapache2-mod-proxy-uwsgi.  Closes: #910218
   * Update test-framework to r1845652
   * Fix test suite to actually run 

Bug#880047: marked as done (postgrey doesn't start because it can't write its pid)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 14:50:12 +
with message-id 
and subject line Bug#880047: fixed in postgrey 1.36-3+deb9u1
has caused the Debian Bug report #880047,
regarding postgrey doesn't start because it can't write its pid
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.)


-- 
880047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgrey
Version: 1.36-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The default init script that comes with Postgrey on Debian 9 fails to start 
after a reboot. The installer creates /var/run/postgrey and writes its pid 
there but /var/run is a tmpfs file system and so on a reboot /var/run/postgrey 
ceases to exist. The init script for Postgrey does not attempt to create 
/var/run/postgrey and just fails to start when it can't write to 
/var/run/postgrey. When postgrey fails to start then Postfix starts complaining 
that it is misconfigured and begins bouncing emails. I was able to fix this by 
adding these lines to the do_start function in the init script:

# Assure that /var/run/postgrey exists
[ -d /var/run/postgrey ] || mkdir -p /var/run/postgrey

if [ "$DAEMON_USER" != "root" ]; then
chown "$DAEMON_USER" /var/run/postgrey
fi


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

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

Versions of packages postgrey depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.61
pn  libberkeleydb-perl 
pn  libnet-dns-perl
pn  libnet-server-perl 
pn  libnetaddr-ip-perl 
ii  perl   5.24.1-3+deb9u2
ii  ucf3.0036

Versions of packages postgrey recommends:
pn  libnet-rblclient-perl  
pn  libparse-syslog-perl   
ii  postfix3.1.6-0+deb9u1

postgrey suggests no packages.
--- End Message ---
--- Begin Message ---
Source: postgrey
Source-Version: 1.36-3+deb9u1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated postgrey package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Sep 2018 22:01:59 +0300
Source: postgrey
Binary: postgrey
Architecture: source
Version: 1.36-3+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Antonio Radici 
Changed-By: Adrian Bunk 
Description:
 postgrey   - greylisting implementation for Postfix
Closes: 756813 880047
Changes:
 postgrey (1.36-3+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * debian/postgrey.init: create /var/run/postgrey if it
 does not exist, patch provided by Laurent Bigonville .
 (Closes: 756813, 880047)
Checksums-Sha1:
 7be0963abbb1f4b000f85483e1782227810428dc 1957 postgrey_1.36-3+deb9u1.dsc
 fd54c77f7099d82406b5a2518e7a488d1a9c4ed2 22180 
postgrey_1.36-3+deb9u1.debian.tar.xz
Checksums-Sha256:
 04fd4cb604e32500776d459431504d3020f7e7cc52cbcf3338f0f03fe7c93392 1957 
postgrey_1.36-3+deb9u1.dsc
 ab687ddf91a27b294516e7800fe8eea9557f36ff7ee0854782034227d58c2cc5 22180 
postgrey_1.36-3+deb9u1.debian.tar.xz
Files:
 b6f5a3d843ca83fa2a2d88ced66308a4 1957 mail optional postgrey_1.36-3+deb9u1.dsc
 0acf92595cccf03841bfba480b33cf6e 22180 mail optional 
postgrey_1.36-3+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAluesBkACgkQiNJCh6LY
mLGTjA//SIp1qaipXmFsSisF/pIyHPi5W0f6jseF18hvoHblBLmYxEJPpSgg4o+G
O8EZntgfNIZZA+jNwd9wItD+j3kaYIP2cIs5mE4gGvNse4CGdGGJWCkwgXcUWK1m
dkn0mdS8OHyC4fOSlTc/dAq1EzCRF/n/M9NO1laUC8Rklvl1mUdw189Hf3K5WwlQ
WYEkzN6DhZuGKy980wNcaj7c4J6zaSO0kEKrUCWmonpIxUqS3Hlv4xOPcY+GQIPf

Bug#910229: python-gitlab: File conflict with ruby-gitlab

[Jeremy Bicha]

In my opinion, python-gitlab and ruby-gitlab have "different
functionality" because I believe you can't use the same syntax for
each "gitlab". Therefore, the part about Conflicts or alternatives
doesn't apply here.

Thanks,
Jeremy Bicha

Processed: Bug #912541 in libjackson-json-java marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912541 [src:libjackson-json-java] libjackson-json-java: FTBFS with Java 11 
due to javax.activation and JAXB removal
Added tag(s) pending.

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

Bug#912541: Bug #912541 in libjackson-json-java marked as pending

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #912541 in libjackson-json-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/libjackson-json-java/commit/7cd50d1820dbe82e8a199b18eb0c8b459dcb46b1


Fix FTBFS with OpenJDK 11 by build-depending on libactivation-java.

Closes: #912541



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912541

Processed: Re: python-gitlab: File conflict with ruby-gitlab

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #910229 {Done: Federico Ceratto } [src:python-gitlab] 
python-gitlab: File conflict with ruby-gitlab
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-gitlab/1:1.6.0-2.

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

Bug#910229: python-gitlab: File conflict with ruby-gitlab

[Jeremy Bicha]

Control: reopen -1

Respectfully, this is not an acceptable fix.

It should be possible to have both python-gitlab and ruby-gitlab
installed. Debian Policy § 7.4 says "Having similar functionality or
performing the same tasks as another package is not sufficient reason
to declare Breaks or Conflicts with that package." [1]

Please read the first paragraph of Debian Policy § 10.1  [2]

[1] https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts
[2] https://www.debian.org/doc/debian-policy/ch-files.html#s-binaries

Thanks,
Jeremy Bicha

Bug#912721: temporarily workaround

[Amy Kos]

mv /etc/alsa/conf.d /etc/alsa/conf.d.bak

Processed: tagging 910218

[Debian Bug Tracking System]

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

> tags 910218 + pending
Bug #910218 [libapache2-mod-proxy-uwsgi] libapache2-mod-proxy-uwsgi: copyright 
file missing after upgrade (policy 12.5)
Bug #910979 [libapache2-mod-proxy-uwsgi] libapache2-mod-proxy-uwsgi: copyright 
file missing after upgrade (policy 12.5)
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#905379: Bug explanation

[Roland Hieber]

On Fri, 26 Oct 2018 16:09:19 +0100 Julian Gilbey  wrote:
> I've just uploaded a version based on git to unstable
> (2.1.5+dfsg+2.1.6-test.20181026.b4f4e65c-1) so you can test it.  Does
> this version work for you? 

Thanks! At least it shows a functional UI without any warnings, and
editing and studying decks works, so I guess that's a yes :-)

 - Roland

Bug#910229: marked as done (python-gitlab: File conflict with ruby-gitlab)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 12:50:45 +
with message-id 
and subject line Bug#910229: fixed in python-gitlab 1:1.6.0-2
has caused the Debian Bug report #910229,
regarding python-gitlab: File conflict with ruby-gitlab
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.)


-- 
910229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gitlab
Version: 1:1.6.0-1
Severity: serious
Affects: src:ruby-gitlab

Both ruby-gitlab and gitlab-cli ship /usr/bin/gitlab and
/usr/share/man/man1/gitlab.1.gz

This is a violation of the first paragraph of Debian Policy § 10.1

https://www.debian.org/doc/debian-policy/ch-files.html

I suggest that both packages rename their scripts. How about
ruby-gitlab and python-gitlab?

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: python-gitlab
Source-Version: 1:1.6.0-2

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated python-gitlab 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Nov 2018 12:28:55 +
Source: python-gitlab
Binary: python-gitlab python-gitlab-doc python3-gitlab gitlab-cli
Architecture: source all
Version: 1:1.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Description:
 gitlab-cli - GitLab command-line client
 python-gitlab - Python GitLab API client library
 python-gitlab-doc - Python 3 GitLab API client library - documentation
 python3-gitlab - Python 3 GitLab API client library
Closes: 910229
Changes:
 python-gitlab (1:1.6.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
 .
   [ Federico Ceratto ]
   * Set Conflicts: ruby-gitlab header (Closes: #910229)
Checksums-Sha1:
 e9e476f546dc253aa26bfc290b096fe85bf47c85 2316 python-gitlab_1.6.0-2.dsc
 be11f5e0bcc653de9fc93071020c75ecee2a1825 3456 
python-gitlab_1.6.0-2.debian.tar.xz
 dc0e4c47abdb6718978c77e244812624efe607cd 11792 gitlab-cli_1.6.0-2_all.deb
 b9d784057f505e27f0656fe7973805d42450 135280 
python-gitlab-doc_1.6.0-2_all.deb
 4e0b815c4403863203d0611fd33b4b22b8fa211d 53536 python-gitlab_1.6.0-2_all.deb
 df58f9eeaea5693a7369bc03ea945695d155f3f2 8994 
python-gitlab_1.6.0-2_amd64.buildinfo
 bf52bab01c4b72f8efb2bb3293867d3316eac1f1 48032 python3-gitlab_1.6.0-2_all.deb
Checksums-Sha256:
 cad3286867b76929b48435f7bf4f0e076f2eb715e9e30d0ac18082bedd3adc26 2316 
python-gitlab_1.6.0-2.dsc
 f53f262a8284957392fc3d110567e14ef8cde7f7691822c4b6b9aa139f73bd19 3456 
python-gitlab_1.6.0-2.debian.tar.xz
 05bb3e4a9d59bb289d2cb98cbd5a1a0f1780ea0b364ca1359b2f7bfe67c2c1ce 11792 
gitlab-cli_1.6.0-2_all.deb
 f1fca4625bd3b3a9ad753f62ee40e950cef3e9b8e48a5ff7b5de2dae7652265e 135280 
python-gitlab-doc_1.6.0-2_all.deb
 f37ad047a9f11f95c62857ad3dddcc52839baf2907ef35fc6bfd3fcc73dad15e 53536 
python-gitlab_1.6.0-2_all.deb
 320a31a7423dca205d411332eab2d6f0dd47453168da2aa2362d94c061ec89ba 8994 
python-gitlab_1.6.0-2_amd64.buildinfo
 93bb44d0b85c7df2b776324d969194aeea5b01073dcef93df8f3976a65886d15 48032 
python3-gitlab_1.6.0-2_all.deb
Files:
 ec55f258334479e121fa9e79d71f4365 2316 python optional python-gitlab_1.6.0-2.dsc
 3ea5b1d5301d1945e46507a80dc69236 3456 python optional 
python-gitlab_1.6.0-2.debian.tar.xz
 7a584a8e57d11714868177414c54c344 11792 utils optional 
gitlab-cli_1.6.0-2_all.deb
 b375060505f7845b2f59ce8b36009c4e 135280 doc optional 
python-gitlab-doc_1.6.0-2_all.deb
 d2d526e8f9852e7fda897d9b2383b422 53536 python optional 
python-gitlab_1.6.0-2_all.deb
 045062e095ceea0feeac764a5d9b06c2 8994 python optional 
python-gitlab_1.6.0-2_amd64.buildinfo
 e9a486ca14dc2e6c0dc12bc98afd6eeb 48032 python optional 
python3-gitlab_1.6.0-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAlvdlbIACgkQbzG8RPUX

Bug#912721: (no subject)

[Bert]

I can confirm the issue, however, I still get no sound after copying
the .conf file from the source package to /usr/share/alsa/alsa.conf.d
like Matthias suggested. Still investigating... 

Bug#832127: Test::Aggregate: pending removal from Debian

[intrigeri]

Hi,

as announced in July, I've requested the removal of this package from
sid: #912744

Cheers,
-- 
intrigeri

Bug#912747: ruby-kubeclient FTBFS with openssl 1.1.1

[Pirate Praveen]

Package: ruby-kubeclient
Version: 3.0.0-3
severity: serious
Control: forwarded -1 https://github.com/abonas/kubeclient/issues/359

Autopkgtest is also failing
https://ci.debian.net/data/packages/unstable/amd64/r/ruby-kubeclient/latest-autopkgtest/log.gz



signature.asc
Description: OpenPGP digital signature

Bug#840305: libatteanx-store-memorytriplestore-perl: depends on unavailable AtteanX::RDFQueryTranslator

[intrigeri]

Dear Jonas,

gregor herrmann:
> On Mon, 10 Oct 2016 14:42:29 +0200, Andreas Beckmann wrote:
>> Can't locate AtteanX/RDFQueryTranslator.pm in @INC (you may need to install 
>> the AtteanX::RDFQueryTranslator module) (@INC contains: 
>> /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl 
>> /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
>> /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
>> /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
>> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
>> t/planning.t line 12,  line 1.

> AtteanX/RDFQueryTranslator.pm was in libattean-perl but according to
> its d/changelog:

> + Remove AtteanX::RDFQueryTranslator (split into a new package) and
>   all other references to RDF::Query.

> So someone would need to package the now separate
> AtteanX::RDFQueryTranslator.

This package has only been available in experimental since its initial
(and last) batch of uploads three years ago. Its popcon is 1. It has
started to FTBFS two years ago. So you won't be astonished that it
popped up on my "candidate for removal" radar. But it's mostly
harmless so there's of course no hurry :)  Still:

Is it still useful to keep this package in the archive, albeit in
experimental only? Are you still interested in working on this and
perhaps upload the missing dependency? If not, I propose we remove it
from the archive; happy to deal with the paperwork myself (except
moving to "attic" or whatever it's called in the Salsa days, which
I've consistently forgotten).

Cheers,
-- 
intrigeri

Processed: ruby-kubeclient FTBFS with openssl 1.1.1

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/abonas/kubeclient/issues/359
Bug #912747 [ruby-kubeclient] ruby-kubeclient FTBFS with openssl 1.1.1
Set Bug forwarded-to-address to 
'https://github.com/abonas/kubeclient/issues/359'.

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

Bug#912746: volumeicon-alsa: volumeicon causes machine to overheat

[allan grossman]

Package: volumeicon-alsa
Version: 0.5.1+git20170117-1
Severity: grave
Justification: renders package unusable

dear maintainer,

Ran apt full-upgrade this morning; had been holding off because of Perl upgrade
but apt said I was good to go this morning.

After rebooting both machines (both Dell Precision laptops, one first-gen and
one fourth-gen i7) for a kernel upgrade I noticed CPU temps above 85°C.

Ran glances to find out what the problem was and found a single core running at
100% on both machines.  Killed volumeicon on both machines and temps returned
to normal.  Restarting volumeicon caused temps to rise again.



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

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

Versions of packages volumeicon-alsa depends on:
ii  libasound2  1.1.7-1
ii  libc6   2.27-8
ii  libcairo2   1.16.0-1
ii  libgdk-pixbuf2.0-0  2.38.0+dfsg-6
ii  libglib2.0-02.58.1-2
ii  libgtk-3-0  3.24.1-2
ii  libnotify4  0.7.7-3
ii  libx11-62:1.6.7-1

volumeicon-alsa recommends no packages.

Versions of packages volumeicon-alsa suggests:
pn  alsamixergui | aumix-gtk | kmix | gnome-alsamixer  
pn  notify-osd | xfce4-notifyd | notification-daemon   

-- no debconf information

Bug#909764: marked as done (lizardfs FTBFS with spdlog 1:1.1.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 03 Nov 2018 11:35:58 +
with message-id 
and subject line Bug#909764: fixed in lizardfs 3.12.0+dfsg-2
has caused the Debian Bug report #909764,
regarding lizardfs FTBFS with spdlog 1:1.1.0-1
to be marked as done.

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

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


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

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

...
/build/1st/lizardfs-3.12.0+dfsg/src/common/slogger.cc: In function 'bool 
lzfs::add_log_file(const char*, lzfs::log_level::LogLevel, int, int)':
/build/1st/lizardfs-3.12.0+dfsg/src/common/slogger.cc:67:30: error: 
'rotating_logger_mt' is not a member of 'spdlog'
   LoggerPtr logger = spdlog::rotating_logger_mt(path, path, max_file_size, 
max_file_count);
  ^~
/build/1st/lizardfs-3.12.0+dfsg/src/common/slogger.cc: In function 'bool 
lzfs::add_log_syslog()':
/build/1st/lizardfs-3.12.0+dfsg/src/common/slogger.cc:89:11: error: 
'syslog_logger' is not a member of 'spdlog'
   spdlog::syslog_logger("syslog");
   ^
/build/1st/lizardfs-3.12.0+dfsg/src/common/slogger.cc:89:11: note: suggested 
alternative: 'register_logger'
   spdlog::syslog_logger("syslog");
   ^
   register_logger
/build/1st/lizardfs-3.12.0+dfsg/src/common/slogger.cc: In function 'bool 
lzfs::add_log_stderr(lzfs::log_level::LogLevel)':
/build/1st/lizardfs-3.12.0+dfsg/src/common/slogger.cc:100:30: error: 
'stderr_color_mt' is not a member of 'spdlog'
   LoggerPtr logger = spdlog::stderr_color_mt("stderr");
  ^~~
...
--- End Message ---
--- Begin Message ---
Source: lizardfs
Source-Version: 3.12.0+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated lizardfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Nov 2018 21:20:16 +1100
Source: lizardfs
Binary: lizardfs-common lizardfs-master lizardfs-metalogger 
lizardfs-chunkserver lizardfs-client lizardfs-adm lizardfs-cgi lizardfs-cgiserv
Architecture: source amd64 all
Version: 3.12.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 lizardfs-adm - LizardFS - administration tools
 lizardfs-cgi - LizardFS - CGI monitor
 lizardfs-cgiserv - simple CGI-capable HTTP server to run LizardFS CGI monitor
 lizardfs-chunkserver - LizardFS - data server
 lizardfs-client - LizardFS - client tools and mount utility
 lizardfs-common - LizardFS - common files
 lizardfs-master - LizardFS - master server
 lizardfs-metalogger - LizardFS - metalogger server
Closes: 909764
Changes:
 lizardfs (3.12.0+dfsg-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Dmitry Smirnov ]
   * New patch to fix FTBFS with spdlog >= 1.1.0 (Closes: #909764).
   * Build-Depends:
 = libspdlog-dev (>= 1:1.2.0~)
   * Standards-Version: 4.2.1.
   * rules: removed explicit "--parallel".
Checksums-Sha1:
 3cfc8dffda5aeb85d63826be171f0da51dca0095 2725 lizardfs_3.12.0+dfsg-2.dsc
 a399b0640b0d0f1e349cc926fd28f2ecbd29e612 20316 
lizardfs_3.12.0+dfsg-2.debian.tar.xz
 bd1704e0c0b935453e5675ac4de525278f94324d 12423128 
lizardfs-adm-dbgsym_3.12.0+dfsg-2_amd64.deb
 ab0689f67655dc3a4cfdb34912054edc43f38232 175632 
lizardfs-adm_3.12.0+dfsg-2_amd64.deb
 5f757c5aadf02e83c1721d06276957d621848403 40324 
lizardfs-cgi_3.12.0+dfsg-2_all.deb
 e657c66c082d159555854687a1f1efe464d1bede 24052 
lizardfs-cgiserv_3.12.0+dfsg-2_amd64.deb
 d7e92cc26fe8c4dcbe91f3d4dc7f2094e224a50b 15135420 
lizardfs-chunkserver-dbgsym_3.12.0+dfsg-2_amd64.deb
 cda6e505c31b29fcf0c6624fbec5e6dc60929ef3 317148 
lizardfs-chunkserver_3.12.0+dfsg-2_amd64.deb
 

Bug#825231: Devel-BeginLift: pending removal from Debian

[intrigeri]

Hi,

as announced in July, I've requested this package to be removed from
sid: https://bugs.debian.org/912743

Cheers,
-- 
intrigeri

Processed: Bug #912315 in audacious-plugins marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912315 [audacious] audacious-plugins >= 3.10 missed
Added tag(s) pending.

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

Bug#912315: Bug #912315 in audacious-plugins marked as pending

[Alf Gaida]

Control: tag -1 pending

Hello,

Bug #912315 in audacious-plugins 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/audacious-plugins/commit/0ba51cbd33fffd21e0407d43bd34ccd843410ff6


Closes: #912315  audacious-plugins >= 3.10 missed



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912315

Bug#912737: [Pkg-openssl-devel] Bug#912737: openssl: SSL_read: error:1408F119:SSL routines:ssl3_get_record:decryption failed

[Kurt Roeckx]

On Sat, Nov 03, 2018 at 11:12:37AM +0100, Julien Lecomte wrote:
> Package: openssl
> Version: 1.1.1-2
> Severity: serious
> Justification: makes unrelated software on the system (or the whole system) 
> break
> 
> Dear Maintainer,
> 
> On a fresh install of Debian/Buster via the alpha3 dvd ISO, when I try to 
> access some SSL URLs, openssl fails to download said resource.
> 
> ~~~bash
> julien@desktop:/tmp$ curl  
> https://download.lenovo.com/pccbbs/mobiles/n1wuj23w.exe --output file
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
>   0 8169k0 278000 0   268k  0  0:00:30 --:--:--  0:00:30  268k
> curl: (56) OpenSSL SSL_read: error:1408F119:SSL 
> routines:ssl3_get_record:decryption failed or bad record mac, errno 0
> ~~~
> 
> URL above issues error "/tmp/mozilla_julien0/5wQP3KKa.bin.part could not be 
> saved, because the source file could not be read." under firefox-esr.

It works for me.

Are you saying it gives an error both with firefox and curl? Then
it would be 2 different TLS implementaitons saying something is
wrong.

Does it work when you add --tls-max 1.2?

I suspect there is some middlebox that breaks things for you.


Kurt

Bug#912740: ruby2.3: FTBFS on mips and armhf in stretch

[Salvatore Bonaccorso]

Source: ruby2.3
Version: 2.3.3-1+deb9u3
Severity: serious
Justification: FTBFS
Control: found -1 2.3.3-1+deb9u4
Control: affects -1 release.debian.org,security.debian.org

Hi

There is a regression for rub2.3 in stretch which is FTBFS on mips
and armhf. Buildlogs from the last security upload (DSA-4332-1) build
attached.

Regards,
Salvatore


ruby2.3_2.3.3-1+deb9u4_mips-2018-11-03T06:56:01Z.gz
Description: application/gzip


ruby2.3_2.3.3-1+deb9u4_armhf-2018-11-03T06:56:29Z.gz
Description: application/gzip

Processed: ruby2.3: FTBFS on mips and armhf in stretch

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.3.3-1+deb9u4
Bug #912740 [src:ruby2.3] ruby2.3: FTBFS on mips and armhf in stretch
The source 'ruby2.3' and version '2.3.3-1+deb9u4' do not appear to match any 
binary packages
Marked as found in versions ruby2.3/2.3.3-1+deb9u4.
> affects -1 release.debian.org,security.debian.org
Bug #912740 [src:ruby2.3] ruby2.3: FTBFS on mips and armhf in stretch
Added indication that 912740 affects release.debian.org and security.debian.org

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

Bug#909764: Bug #909764 in lizardfs marked as pending

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #909764 in lizardfs 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/lizardfs/commit/bfcd5bcf1679d5e113e5c88946d2c9446db7de55


New patch to fix FTBFS with spdlog >= 1.1.0 (Closes: #909764).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909764

Processed: Bug #909764 in lizardfs marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909764 [src:lizardfs] lizardfs FTBFS with spdlog 1:1.1.0-1
Added tag(s) pending.

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

Bug#912737: openssl: SSL_read: error:1408F119:SSL routines:ssl3_get_record:decryption failed

[Julien Lecomte]

Package: openssl
Version: 1.1.1-2
Severity: serious
Justification: makes unrelated software on the system (or the whole system) 
break

Dear Maintainer,

On a fresh install of Debian/Buster via the alpha3 dvd ISO, when I try to 
access some SSL URLs, openssl fails to download said resource.

~~~bash
julien@desktop:/tmp$ curl  
https://download.lenovo.com/pccbbs/mobiles/n1wuj23w.exe --output file
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 8169k0 278000 0   268k  0  0:00:30 --:--:--  0:00:30  268k
curl: (56) OpenSSL SSL_read: error:1408F119:SSL 
routines:ssl3_get_record:decryption failed or bad record mac, errno 0
~~~

URL above issues error "/tmp/mozilla_julien0/5wQP3KKa.bin.part could not be 
saved, because the source file could not be read." under firefox-esr.

/etc/ssl/openssl.cnf is pristine (md5sum: 30432a49dc82df6e74619ca2b8506c8a)

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

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

Versions of packages openssl depends on:
ii  libc6  2.27-8
ii  libssl1.1  1.1.1-2

openssl recommends no packages.

Versions of packages openssl suggests:
ii  ca-certificates  20170717

-- no debconf information

Bug#912721: libasound2-plugins: Sound no longer works after latest update

[Vincent Lefevre]

Package: libasound2-plugins
Version: 1.1.7-1
Followup-For: Bug #912721

I can confirm; ogg123 segfaults.

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

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

Versions of packages libasound2-plugins:amd64 depends on:
ii  libasound21.1.7-1
ii  libavcodec58  7:4.0.2-2+b2
ii  libavresample47:4.0.2-2+b2
ii  libavutil56   7:4.0.2-2+b2
ii  libc6 2.27-8
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2
ii  libpulse0 12.2-2
ii  libsamplerate00.1.9-2

libasound2-plugins:amd64 recommends no packages.

libasound2-plugins:amd64 suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: found 912695 in 0.22.8

[Debian Bug Tracking System]

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

> found 912695 0.22.8
Bug #912695 [apt-show-versions] apt-show-versions: breaks "apt-get update" and 
uninstallable after Perl 5.28 upgrade
Marked as found in versions apt-show-versions/0.22.8.
> thanks
Stopping processing here.

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

Bug#881971: fixed in lightbeam 2.1.0-1

[Moritz Mühlenhoff]

On Thu, Oct 04, 2018 at 01:55:46AM +1000, Dmitry Smirnov wrote:
> On Thursday, 4 October 2018 1:19:56 AM AEST Moritz Mühlenhoff wrote:
> > On Wed, Jul 25, 2018 at 04:19:18AM +, Dmitry Smirnov wrote:
> > >* New upstream release [February 2018].
> > >
> > >  + WebExtensions version (Closes: #881971).
> > 
> > lightbeam is also broken in stretch, do you plan to update it
> > there or should it be removed from stable?
> 
> Unfortunately I have no capacity to take care of it in Stretch...
> 
> Removal remains an option unless a team member prepares an upload...

The next stretch point release is happening soon, so I filed a removal
request from stretch. If someone wants to re-add the web extension
to stretch, it can happen in the subsequent point release.

Cheers,
Moritz

Processed: notfound 912695 in apt-show-versions

[Debian Bug Tracking System]

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

> notfound 912695 apt-show-versions
Bug #912695 [apt-show-versions] apt-show-versions: breaks "apt-get update" and 
uninstallable after Perl 5.28 upgrade
There is no source info for the package 'apt-show-versions' at version 
'apt-show-versions' with architecture ''
Unable to make a source version for version 'apt-show-versions'
No longer marked as found in versions apt-show-versions.
> thanks
Stopping processing here.

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

Bug#912721: libasound2-plugins: Sound no longer works after latest update

[Matthias Liertzer]

I installed the corresponding .conf files from the source package to
/usr/share/alsa/alsa.conf.d and sound started working again after a
restart. So all that needs to be done is to add the files to the package.

Best regards,
Matthias

On 03/11/2018 09:56, Matthias Liertzer wrote:
> Package: libasound2-plugins
> Severity: grave
> Justification: renders package unusable
> 
> After updating to the latest version of libasound2-plugins, sound on
> my system stopped working. Trying to start `alsamixer' failed as well
> with the following error message:
> 
> ALSA lib conf.c:3639:(config_file_open) cannot access file
> /etc/alsa/conf.d/10-rate-lav.conf
> 
> It turns out that libasound2-plugins installs broken symlinks in
> /etc/alsa/conf.d. All symlinks installed by libasound2-plugins in
> /etc/alsa/conf.d are broken, because the corresponding files in
> /usr/share/alsa/alsa.conf.d do not exist.
> 
> Best regards,
> Matthias
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
> 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>