Bug#824248: RFS: pickleshare/0.7.2-1

[Julien Puydt]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "pickleshare"

 * Package name: pickleshare
   Version : 0.7.2-1
   Upstream Author : Ville Vainio
 * URL : https://github.com/pickleshare/pickleshare
 * License : Expat
   Section : python

  It builds those binary packages:

python-pickleshare - File system based database that uses Python 
pickles for Python 2
 python3-pickleshare - File system based database that uses Python 
pickles for Python 3


  To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/pickleshare


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/pickleshare/pickleshare_0.7.2-1.dsc


  Changes since the last upload:
pickleshare (0.7.2-1) unstable; urgency=medium

  * New upstream version.
  * Bump standards-version up.
  * Use https for Vcs-* fields.

Thanks,

Snark on #debian-python

Bug#824247: RM: php-pager -- ROM; PHP 7.0 Transition

[Mathieu Parent]

Package: ftp.debian.org
Severity: normal

Dear ftp-team,

One more PEAR package to drop.

Thanks

Mathieu Parent

Bug#802224: Upstream is now up to 0.5.6

[Julien Puydt]

Hi,

I modified the debian/watch and debian/copyright files to suppress the 
bench/ directory, and updated to 0.5.6. Pushed my changes to git.


What do you think of the current package? Is it worth an upload? [If so, 
notice I can't do it as I'm no DD (yet)]


Thanks,

Snark on #debian-js

Bug#811827: prank: FTBFS with GCC 6: no match for

[Andreas Tille]

Hi Ari,

Sascha Steinbiss has found a patch for this problem which you can find
here:


https://anonscm.debian.org/viewvc/debian-med/trunk/packages/prank/trunk/debian/patches/

I'd also recommend to apply the hardening patch.

Kind regards

  Andreas.

On Wed, Jan 20, 2016 at 03:10:09PM +0200, Ari Löytynoja wrote:
> Hi,
> 
> I'm using gcc 5.2.1 on Ubuntu 15.10. Is it possible to check the 
> compatibility 
> with this version of gcc? If not, is there gcc-6 available for Wily? I only 
> found a repository with gcc-6 for the next Ubuntu release:
>  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test/
> 
> Regards, Ari
> 
> On Wednesday 20 January 2016 11:42:00 Andreas Tille wrote:
> > Hi Ari,
> > 
> > yes, that source tarball from
> >   http://wasabiapp.org/download/prank/prank.source.150803.tgz
> > is used for the packaging.
> > 
> > Thanks a lot for your quick reply
> > 
> >  Andreas.
> > 
> > On Wed, Jan 20, 2016 at 12:32:01PM +0200, Ari Löytynoja wrote:
> > > Hi,
> > > Which version of PRANK is that? The latest one is here
> > > http://wasabiapp.org/download/prank/prank.source.150803.tgz
> > > 
> > > Regards, Ari
> > > 
> > > On Wednesday 20 January 2016 11:04:46 Andreas Tille wrote:
> > > > Hi,
> > > > 
> > > > the Debian package for prank failed to build when using gcc version 6 as
> > > > you can read below in the bug report.  Feel free to contact us via the
> > > > bug e-mail address (see To of this mail).
> > > > 
> > > > Kind regards
> > > > 
> > > >Andreas.
> > > > 
> > > > On Tue, Jan 19, 2016 at 06:22:00PM -0800, Martin Michlmayr wrote:
> > > > > Package: prank
> > > > > Version: 0.0.150803-1
> > > > > Severity: important
> > > > > User: debian-...@lists.debian.org
> > > > > Usertags: ftbfs-gcc-6 gcc-6-no-match
> > > > > 
> > > > > This package fails to build with GCC 6.  GCC 6 has not been released
> > > > > yet, but it's expected that GCC 6 will become the default compiler for
> > > > > stretch.
> > > > > 
> > > > > Note that only the first error is reported; there might be more.  You
> > > > > can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
> > > > > you can set CC=gcc-6 CXX=g++-6 explicitly.
> > > > > 
> > > > > You may be able to find out more about this issue at
> > > > > https://gcc.gnu.org/gcc-6/changes.html
> > > > > 
> > > > > > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
> > > > > 
> > > > > ...
> > > > > 
> > > > > > g++ -c -g -O2 -fstack-protector-strong -Wformat
> > > > > > -Werror=format-security
> > > > > > -pipe -O3  -I. -I/usr/include -o bppancestors.o bppancestors.cpp
> > > > > > hmmodel.cpp: In member function 'void
> > > > > > HMModel::alignmentModel(AncestralNode*)': hmmodel.cpp:1513:57:
> > > > > > error:
> > > > > > no match for 'operator<<' (operand types are
> > > > > > 'std::basic_ostream'
> > > > > > and 'std::ostream {aka std::basic_ostream}')> >
> > > > > > 
> > > > > >  cout<<"HMModel::alignmentModel: impossible 'as'"< > > > > >  ^~
> > > > > > 
> > > > > > hmmodel.cpp:1513:57: note: candidate: operator<<(int, int)
> > > > > > 
> > > > > > hmmodel.cpp:1513:57: note:   no known conversion for argument 2 from
> > > > > > 'std::ostream {aka std::basic_ostream}' to 'int' In file
> > > > > > included
> > > > > > from /usr/include/c++/6/istream:39:0,
> > > > > > 
> > > > > >  from /usr/include/c++/6/fstream:38,
> > > > > > 
> > > > > >  from hmmodel.cpp:24:
> > > > > > /usr/include/c++/6/ostream:108:7: note: candidate:
> > > > > > std::basic_ostream<_CharT, _Traits>::__ostream_type&
> > > > > > std::basic_ostream<_CharT,
> > > > > > _Traits>::operator<<(std::basic_ostream<_CharT,
> > > > > > _Traits>::__ostream_type& (*)(std::basic_ostream<_CharT,
> > > > > > _Traits>::__ostream_type&)) [with _CharT = char; _Traits =
> > > > > > std::char_traits; std::basic_ostream<_CharT,
> > > > > > _Traits>::__ostream_type = std::basic_ostream]> >
> > > > > > 
> > > > > >operator<<(__ostream_type& (*__pf)(__ostream_type&))
> > > > > >^~~~
> > > > > > 
> > > > > > /usr/include/c++/6/ostream:108:7: note:   no known conversion for
> > > > > > argument 1 from 'std::ostream {aka std::basic_ostream}' to
> > > > > > 'std::basic_ostream::__ostream_type&
> > > > > > (*)(std::basic_ostream::__ostream_type&) {aka
> > > > > > std::basic_ostream& (*)(std::basic_ostream&)}'
> > > > > > /usr/include/c++/6/ostream:117:7: note: candidate:
> > > > > > std::basic_ostream<_CharT, _Traits>::__ostream_type&
> > > > > > std::basic_ostream<_CharT,
> > > > > > _Traits>::operator<<(std::basic_ostream<_CharT,
> > > > > > _Traits>::__ios_type&
> > > > > > (*)(std::basic_ostream<_CharT, _Traits>::__ios_type&)) [with _CharT
> > > > > > =
> > > > > > char; _Traits = std::char_traits; std::basic_ostream<_CharT,
> > > > > > _Traits>::__ostream_type = std::basic_ostream;
> > > > > > std::basic_ostream<_CharT, 

Bug#824246: RFS: ptyprocess/0.5.1-1

[Julien Puydt]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "ptyprocess"

 * Package name: ptyprocess
   Version : 0.5.1-1
   Upstream Author : Thomas Kluyver
 * URL : https://github.com/pexpect/ptyprocess
 * License : ISC
   Section : python

  It builds those binary packages:

python-ptyprocess - Run a subprocess in a pseudo terminal from Python 2
 python3-ptyprocess - Run a subprocess in a pseudo terminal from Python 3

  To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/ptyprocess


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/ptyprocess/ptyprocess_0.5.1-1.dsc


  Changes since the last upload:
ptyprocess (0.5.1-1) unstable; urgency=medium

  * New upstream release.
  * Pushed standards-version up.
  * Use https in Vcs-* fields.


Thanks,

Snark on #debian-python

Bug#824245: debian-security-support: [INTL:ru] Russian debconf templates translation update

[Yuri Kozlov]

Package: debian-security-support
Version: 2016.05.11
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

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

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

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

Russian debconf templates translation update is attached.

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

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


ru.po.gz
Description: application/gzip

Bug#814570: debdiff: Bash completion on a filename parameter fails if a leading directory specified

[Ben Finney]

Control: found -1 devscripts/2.16.4
Control: owner -1 !
Control: retitle -1 debdiff: Bash completion on a filename parameter fails if a 
leading directory specified

On 13-Feb-2016, Salvatore Bonaccorso wrote:

> Recently (I think since 2.15.10 where bash completions were
> reorganized), debdiff cannot bash complete anymore to files if they
> are not in the current directory.

The test case is even simpler: specify a path with *any* directory,
even the current (‘.’) directory, leading the path.

$ ls -l *.deb
foo_1.2.3-1_all.deb

$ debdiff foo# result: completes the package name.

$ debdiff ./foo  # result: no completion found.

I will attempt fixing this.

-- 
 \  “The shortest distance between two points is under |
  `\  construction.” —Noelie Alito |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#824244: libfilesys-notify-simple-perl: fails to notify on moves with inotify

[Eric Wong]

Package: libfilesys-notify-simple-perl
Version: 0.08-1
Severity: normal

I tried to have this watch some Maildirs but it fails to
detect rename() calls.  So this probably should watch for
IN_MOVED_TO and IN_MOVED_FROM events from inotify.

I also tried 0.12-1 from jessie with the same effect.

Bug#824243: RFS: twinkle/1:1.9.0+git20160321.0.64a0816+dfsg-1 [RC] -- Voice over Internet Protocol (VoIP) SIP Phone

[Peter Colberg]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for the package "twinkle":

  git clone https://anonscm.debian.org/git/pkg-voip/twinkle.git
  cd twinkle && pristine-tar checkout 
../twinkle_1.9.0+git20160321.0.64a0816+dfsg.orig.tar.xz

For verification, these are the current branch heads:

  git show-ref --heads
  a544eebc919e6f78067b73c2cc54fb438e6f5666 refs/heads/master
  961140e91690333a33b3dd0e7ef5ad1333195f6a refs/heads/pristine-tar
  8916774a5c74898e4bcc5f4f9c9b0e3cd5fd4d5e refs/heads/upstream

It builds these binary packages:

  twinkle - Voice over Internet Protocol (VoIP) SIP Phone

More information about twinkle can be obtained from http://twinkle.dolezel.info.

Changes since the last upload:

twinkle (1:1.9.0+git20160321.0.64a0816+dfsg-1) unstable; urgency=medium

  * New upstream snapshot (Closes: #821234).
  * Drop patches applied upstream.
  * Drop build dependency on qtquick1-5-dev (Closes: #810708).
  * Enable hardening build flags.
  * Bump Standards-Version to 3.9.8.

 -- Peter Colberg   Fri, 13 May 2016 07:14:44 -0400

If you decide to sponsor this package, please upload the source only
so that buildd logs are available for all archs. I will push a release
tag to the git repository after the package has been uploaded.

Regards,
Peter

Bug#824204: libyajl-dev: Static linking doesn't work

[John Stamp]

Hi George,

It looks like it's just a problem with the link order of the sample
command that you provided.

Can you confirm that this works?

  gcc -o p parse_config.c -lyajl_s

John

Bug#823895: RFS: lsm/1.0.4-1

[Lucas Castro]

On 13-05-2016 11:46, Adam Borowski wrote:
>> On 10-05-2016 02:43, Lucas Castro wrote
>>> I am looking for a sponsor for my package "lsm"
>>>
>>> * Package name: lsm
>>>   Upstream Author : Mika Ilmaranta 
>>> * URL : http://lsm.foobar.fi/
>>>
>>> dget -x 
>>> https://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.4-1.dsc
> From a superficial review:
>
> 1. Please delete (or fill out) debian/README.source
removed.
> 2. The manpage seems mangled:
>
>While simple to configure, provides easy way reconfigure routes, 
> calling notifyscript
>
>lsmVery configurable, but doesn't support domain names yet.
Thanks, fixed.
>
> 3. Typo: exectuble.
if you mean man page typo, fixed.
>
> Meow!
Done.



signature.asc
Description: OpenPGP digital signature

Bug#824242: RFP: refind -- a official succesor of the rEFIt boot manager

[Osamu Aoki]

Package: wnpp
Severity: wishlist

* Package name: rEFInd
  Version : 0.10.3
  Upstream Author : Roderick W. Smith 
* URL : https://sourceforge.net/projects/refind/
* License : BSD-3-clause and GPL-3+
  Programming Lang: C
  Description : boot manager for EFI-based computers

 A graphical boot manager for EFI- and UEFI-based computers, such as all
 Intel-based Macs and recent (most 2011 and later) PCs. rEFInd presents a
 boot menu showing all the EFI boot loaders on the EFI-accessible
 partitions, and optionally BIOS-bootable partitions on Macs and BIOS boot
 entries on UEFI PCs with CSMs. EFI-compatbile OSes, including Linux,
 provide boot loaders that rEFInd can detect and launch. rEFInd can launch
 Linux EFI boot loaders such as ELILO, GRUB Legacy, GRUB 2, and 3.3.0 and
 later kernels with EFI stub support. EFI filesystem drivers for ext2/3/4fs,
 ReiserFS, Btrfs, NTFS, HFS+, and ISO-9660 enable rEFInd to read boot
 loaders from these filesystems, too. rEFInd's ability to detect boot
 loaders at runtime makes it very easy to use, particularly when paired with
 Linux kernels that provide EFI stub support.

Ubuntu needs-packaging:
 https://bugs.launchpad.net/ubuntu/+bug/1136112
  rEFInd is a fork of the rEFIt boot manager. Like rEFIt, rEFInd can
  auto-detect your installed EFI boot loaders and it presents a pretty GUI
  menu of boot options. rEFInd goes beyond rEFIt in that rEFInd better
  handles systems with many boot loaders, gives better control over the
  boot loader search process, and provides the ability for users to define
  their own boot loader entries.

Ubuntu PPA package offered by the upstream
 https://launchpad.net/~rodsmith/+archive/ubuntu/refind
  Last updated: 2016-04-24
  Very nice work :-)  compat=9 and DEP-5 copyright
  Really, it seems we only need to rebuild to upload.

Upstream:
 Rod Smith is also the upstream of gdisk aleady packaged in Debian and
 has extensive knowledge on booting related topcs as documented in:
  http://www.rodsbooks.com/
  http://www.rodsbooks.com/refind/
  http://www.rodsbooks.com/gdisk/

== NOTE ==
Debian removed refit due to FTBFS:
 https://tracker.debian.org/pkg/refit
 This was a popular Mactel boot selector.
The original refit web site recommens to use refined now:
 http://refit.sourceforge.net/
  2013-03-29: As you may have noticed, rEFIt is no longer actively
  maintained. Please check out rEFInd, a fork that is maintaned and
  under active development.

Bug#824241: RM: github-backup [powerpc] -- ROM; New dependencies aren't building on ppc yet

[James McCoy]

Package: ftp.debian.org
Severity: normal

The new github-backup version pulled in a new chain of dependencies, one
of which isn't currently building on powerpc (due to an internal error
in ghc).  This is preventing the fix for #821305 from being able to
migrate to testing.

Therefore, I'd like to request removing the old github-backup binary on
powerpc as an interim solution while the ghc bug is investigated.
Sacrifice a little powerpc for the good of the rest of the archs.

Bug#786498: poco: please upgrade to v1.7.1 or later

[Nicolas Braud-Santoni]

Control: retitle -1 poco: please upgrade to v1.7.1 or later

Hi Rene,

I contacted the maintainers.

In the absence of any answer, I will push an update to the packaging repo
  and request a sponsored NMU.


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#824240: ITP: python-onvif -- Python Client for ONVIF Cameras

[Jelmer Vernooij]

Package: wnpp
Severity: wishlist
Owner: "Jelmer Vernooij" 

* Package name: python-onvif
  Version : 0.1.1
  Upstream Author : Cherish Chen 
* URL : https://github.com/quatanium/python-onvif
* License : MIT
  Programming Lang: Python
  Description : Python Client for ONVIF Camera

This is Python implementation of the ONVIF standard. ONVIF provides a
standard interface to physical IP-based security products

Bug#824239: [DLA] fixes for dla-20,38,53,54

[victory]

Package: www.debian.org
Severity: normal
Tags: patch
X-Debbugs-CC: debian-...@lists.debian.org

* wrong references in dla-20
* missing wireshirk advisory (dla-38), no one sent to d-d-a
* wrong dla ID for "dla-54" sent and created as dla-53
* missing "real" dla-54

see the bottom of the mail

p.s.: 
scripts are not all-round genius;
scripts cannot decide if the source is valid,
scripts cannot fix issues in the source,
scripts do just as instructed.
then, YOU NEED CHECK AND FIX YOURSELF THE GENERATED CONTENTS

-- 
victory
no need to CC me :-)

Index: english/security/2014/dla-20.wml
===
--- english/security/2014/dla-20.wml(revision 193)
+++ english/security/2014/dla-20.wml(working copy)
@@ -8,9 +8,9 @@
   (Closes: #679897), closes https://security-tracker.debian.org/tracker/CVE-2012-3512;>CVE-2012-3512.
 plugins: use runtime $ENV{MUNIN_PLUGSTATE}. So all properly written
   plugins will use /var/lib/munin-node/plugin-state/$uid/$some_file now   
please report plugins that are still using /var/lib/munin/plugin-state/   as 
those  might pose a security risk!
-Validate multigraph plugin name, https://security-tracker.debian.org/tracker/CVE-2013-6048;>CVE-2013-6048.
 Don't abort data collection for a node due to malicious node, fixing
-  munin#1397, https://security-tracker.debian.org/tracker/CVE-2013-6359;>CVE-2013-6359.
+  munin#1397, https://security-tracker.debian.org/tracker/CVE-2013-6048;>CVE-2013-6048.
+Validate multigraph plugin name, https://security-tracker.debian.org/tracker/CVE-2013-6359;>CVE-2013-6359.
 
 
 For Debian 6 Squeeze, these issues have been fixed in munin version 
1.4.5-3+deb6u1
Index: english/security/2014/dla-38.data
===
--- english/security/2014/dla-38.data   (nonexistent)
+++ english/security/2014/dla-38.data   (working copy)
@@ -0,0 +1,10 @@
+DLA-38-1 wireshark
+2014-8-20
+CVE-2014-5161 CVE-2014-5162 CVE-2014-5163
+wireshark
+yes
+yes
+no
+
+#use wml::debian::security
+
Index: english/security/2014/dla-38.wml
===
--- english/security/2014/dla-38.wml(nonexistent)
+++ english/security/2014/dla-38.wml(working copy)
@@ -0,0 +1,25 @@
+LTS security update
+
+
+
+https://security-tracker.debian.org/tracker/CVE-2014-5161;>CVE-2014-5161,
+https://security-tracker.debian.org/tracker/CVE-2014-5162;>CVE-2014-5162:
+
+The Catapult DCT2000 and IrDA dissectors could underrun a buffer.
+It may be possible to make Wireshark crash by injecting a malformed packet 
onto 
+the wire or by convincing someone to read a malformed packet trace 
file.
+
+https://security-tracker.debian.org/tracker/CVE-2014-5163;>CVE-2014-5163:
+
+The GSM Management dissector could crash.
+It may be possible to make Wireshark crash by injecting a malformed packet 
onto
+the wire or by convincing someone to read a malformed packet trace 
file.
+
+
+For Debian 6 Squeeze, these issues have been fixed in wireshark 
version 1.2.11-6+squeeze15
+
+
+
+# do not modify the following line
+#include "$(ENGLISHDIR)/security/2014/dla-38.data"
+# $Id: $
Index: english/security/2014/dla-53.data
===
--- english/security/2014/dla-53.data   (revision 193)
+++ english/security/2014/dla-53.data   (working copy)
@@ -1,10 +1,10 @@
-DLA-53-1 gnupg
-2014-9-14
-CVE-2014-5270
-gnupg
-yes
-yes
-no
-
-#use wml::debian::security
-
+DLA-53-1 apt
+2014-9-3
+CVE-2014-0487 CVE-2014-0488 CVE-2014-0489
+apt
+yes
+yes
+no
+
+#use wml::debian::security
+
Index: english/security/2014/dla-53.wml
===
--- english/security/2014/dla-53.wml(revision 193)
+++ english/security/2014/dla-53.wml(working copy)
@@ -1,15 +1,16 @@
 LTS security update
 
-Genkin, Pipman and Tromer discovered a side-channel attack on Elgamal
-encryption subkeys (https://security-tracker.debian.org/tracker/CVE-2014-5270;>CVE-2014-5270).
+It was discovered that APT, the high level package manager, does not
+properly invalidate unauthenticated data (https://security-tracker.debian.org/tracker/CVE-2014-0488;>CVE-2014-0488),
+performs incorrect verification of 304 replies (https://security-tracker.debian.org/tracker/CVE-2014-0487;>CVE-2014-0487)
+and does not perform the checksum check when the Acquire::GzipIndexes option 
is used
+(https://security-tracker.debian.org/tracker/CVE-2014-0489;>CVE-2014-0489).
 
-In addition, this update hardens GnuPG's behaviour when treating keyserver
-responses; GnuPG now filters keyserver responses to only accepts those
-keyids actually requested by the user.
-
-For Debian 6 Squeeze, these issues have been fixed in gnupg version 
1.4.10-4+squeeze6
+For Debian 6 Squeeze, these issues have been fixed in apt version 
0.8.10.3+squeeze3
 
 
 # do not modify the following line
 #include 

Bug#824238: [Pkg-utopia-maintainers] Bug#824238: python-coherence: fails comparing twisted versions

[Michael Biebl]

Control: tags -1 + patch fixed-upstream
Control: forwarded -1
https://github.com/coherence-project/Coherence/issues/25

Am 14.05.2016 um 03:51 schrieb Jelmer Vernooij:
> With current version of python-coherence in Unstable, I get a traceback:
> 
> Traceback (most recent call last):
>   File "/usr/bin/upnp-inspector", line 23, in 
> from coherence import __version__ as coherence_version
>   File "/usr/lib/python2.7/dist-packages/coherence/__init__.py", line 27, in 
> 
> if twisted_web_version < Version("twisted.web", 2, 5, 0):
>   File "/usr/lib/python2.7/dist-packages/twisted/python/versions.py", line 
> 145, in __cmp__
> % (self.package, other.package))
> twisted.python.versions.IncomparableVersions: 'twisted' != 'twisted.web'


https://github.com/coherence-project/Coherence/issues/25
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#824238: python-coherence: fails comparing twisted versions

[Jelmer Vernooij]

Package: python-coherence
Version: 0.6.6.2-8
Severity: normal

With current version of python-coherence in Unstable, I get a traceback:

Traceback (most recent call last):
  File "/usr/bin/upnp-inspector", line 23, in 
from coherence import __version__ as coherence_version
  File "/usr/lib/python2.7/dist-packages/coherence/__init__.py", line 27, in 

if twisted_web_version < Version("twisted.web", 2, 5, 0):
  File "/usr/lib/python2.7/dist-packages/twisted/python/versions.py", line 145, 
in __cmp__
% (self.package, other.package))
twisted.python.versions.IncomparableVersions: 'twisted' != 'twisted.web'

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

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

Versions of packages python-coherence depends on:
ii  python2.7.11-1
ii  python-axiom  0.7.5-1
ii  python-configobj  5.0.6-2
ii  python-gst0.100.10.22-3
ii  python-louie  1.1-2
ii  python-pkg-resources  20.10.1-1
ii  python-tagpy  2013.1-5
ii  python-zope.interface [python-zopeinterface]  4.1.3-1+b1

Versions of packages python-coherence recommends:
pn  libgdata-google1.2-1  
ii  python-mechanize  1:0.2.5-3

Versions of packages python-coherence suggests:
pn  python-qt4  

-- no debconf information

Bug#824237: debian-maintainers: Annual ping for Riley Baird

[Riley Baird]

Package: debian-maintainers
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Here's my annual ping
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXNn6yAAoJEADsp2GWio3uXtgQAJnZPm/33eftoG48MgB+8DaX
/gZ0bY+MAXTikkFK8oDi0lvbkLzn1cSI1rz9DLYzXoQ3cojpyiW+yEiYjcoSIBOI
p1fq+SjNK3T68D8UcUoHWWH1g6TI41ZlJ7eUgz2EkzNnNfSV8RMniSHge5MiKheX
tBdEx+DYS5FCoLhzFJl3uGaBnfu9Rs0TkbMvFRYHA8x7tDt/wU47Ej8RnS9E1rdE
JrmCY5Q4M1kzaBzXk5k8LpuHOuPeXLBr+OzhkBvrqrOD8WkhixLo4Q4slWkmI3pi
WXSPKTyKux3XxVcLDH+NipMD351uRfVtqvInjalKIYd+9W84lcAXm2ccCNNTo17G
/3TbQz6O8L/M8iHQa5fkF9d2WsZx7SdkfBgj0CQb5gHE4RwJmOWFwn5FwydakWYe
JUH1OWCvOlfmQc/I3GheVGTIAh1qkvF9EwqBz24mO3A1Q/M/2nHZXlyfGKC6CrDL
qBAW+DJgA2u0KXlr3zVKeb1BDDY/x39RfOsvRdvlytFa3KXClrjlvVjbq7qw94r+
aqnUQ5pB7mRrc5OgliDeIfkypmQBj5XsUg8+nRbkD2f722Hr+TSQMloSrba0j6pB
TF0EvpVdrKcb2SdzRpCwzvA4wpoMGZM2qKxcCl2qbXMucswJEvnaJmSw1JDCIWtn
AROgtuYjsRHVOumYZPeV
=ABYb
-END PGP SIGNATURE-

Bug#823815: [php-maint] Bug#823815: php7.0-common: Provides "php-gettext" without Breaks/Replaces

[Marcelo Jorge Vieira]

Hi Ondřej,

On Mon, 2016-05-09 at 13:29 +0200, Ondřej Surý wrote:
> So the other option might be to rename php-gettext written in PHP to
> php-php-gettext (same as f.e. Fedora has) and fix those 6 packages.
> Marcelo, what do you think? Does this seem viable to you?

Sounds good for me, I will rename the package.


Cheers,

-- 
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com



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

Bug#798053: Bug#824079: qgis: FTBFS on non-Linux: 'TCGETS' was not declared in this scope

[aga...@siduction.org]

Hi Bas, thanks for the patch - i will integrate it upstream.
> [0]
>
https://anonscm.debian.org/cgit/pkg-grass/qgis.git/tree/debian/patches/qtermwidget-kfreebsd.patch?h=debian/2.14.2%2bdfsg-2
> [1] https://github.com/qgis/QGIS/pull/3068

I will close this bug with the next upload - and leave the hurd unfixed
- if one think that is is important to have qtermwidget available for
the hurd please open a new bug and provide a tested patch, i would be
happy to apply it upstream, but i will not take any further action to
solve this myself.

Cheers Alf

-- 
Alf Gaida
BDBF C688 EFAD BA89 5A9F  464B CD28 0A0B 4D72 827C



signature.asc
Description: OpenPGP digital signature

Bug#824213: closed by Paul Gevers <elb...@debian.org> (Re: liferea: Dependency Failure - Not Installable)

[Stephen Allen]

On Fri, May 13, 2016 at 07:39:11PM +, Debian Bug Tracking System wrote:
> Version: 1.10.19-2
> 
> On Fri, 13 May 2016 15:06:32 -0400 Stephen 
> wrote:
> > Cannot install the upgrade in SID for Liferea due to required dependency 
> > not being available in 
> > Debian repository:  libpeas-1.0-0-python2loader. Please fix.
> 
> Date: Fri, 13 May 2016 11:49:36 +
> To: 
> From: David Michael Smith 
> Subject: Accepted liferea 1.10.19-2 (source) into unstable
> Signed by: Paul Gevers 
> 
> This issue was fixed in 1.10.19-2 which was uploaded before you filed
> this bug.
 
It may have been uploaded prior but wasn't available in the repo before
my bug report. Thanks for the quick response!

Bug#824234: Please build mythes-sv

[Gunnar Hjalmarsson]

Patch attached. Even if it's small, it involves both a change to d/rules
and the addition of d/mythes-sv.links. This illustrates that the
resolution of  introduced two new
moments to consider when new dictionaries are added via upstream or by
'unblacklisting' existing ones.

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj
commit 7f1c13101fa6d72c48ad603ed59c973d987df1ff
Author: Gunnar Hjalmarsson 
Date:   Sat May 14 01:50:50 2016 +0200

Build mythes-sv; closes #824234

diff --git a/debian/helper.py b/debian/helper.py
index 6be794f..459ea5d 100755
--- a/debian/helper.py
+++ b/debian/helper.py
@@ -53,7 +53,6 @@ blacklisted_packages = [
  "mythes-de-ch",# openthesaurus
  "mythes-it",   # mythes-it
  "mythes-pl",   # openoffice.org-thesaurus-pl
- "mythes-sv",   # mythes-sv
 ]
 
 provides = {
diff --git a/debian/mythes-sv.links b/debian/mythes-sv.links
new file mode 100644
index 000..0eeb821
--- /dev/null
+++ b/debian/mythes-sv.links
@@ -0,0 +1,2 @@
+usr/share/mythes/th_sv_SE_v2.dat usr/share/mythes/th_sv_FI_v2.dat
+usr/share/mythes/th_sv_SE_v2.idx usr/share/mythes/th_sv_FI_v2.idx
diff --git a/debian/rules b/debian/rules
index d78dfd5..d814650 100755
--- a/debian/rules
+++ b/debian/rules
@@ -47,6 +47,7 @@ override_dh_install:
 	$(call rename_mythes_files,es,  th_es_ANY_v2,  th_es_ES_v2 )
 	$(call rename_mythes_files,gl,  thesaurus_gl,  th_gl_ES_v2 )
 	$(call rename_mythes_files,is,  th_is, th_is_IS_v2 )
+	$(call rename_mythes_files,sv,  th_sv_SE,  th_sv_SE_v2 )
 	$(call rename_mythes_files,uk,  th_uk_UA,  th_uk_UA_v2 )
 
 override_dh_clean:

Bug#824236: xul-ext-searchload-options: please add firefox dependencies

[Christoph Anton Mitterer]

Package: xul-ext-searchload-options
Version: 0.8.0-3
Severity: wishlist

Hi.

Now that Iceweasel is gone and iceweasel a transitional package,
please add proper dependencies, like e.g.:
iceweasel | firefox | firefox-esr

Thanks,
Chris.


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

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

Versions of packages xul-ext-searchload-options depends on:
ii  iceweasel  45.1.1esr-1

xul-ext-searchload-options recommends no packages.

xul-ext-searchload-options suggests no packages.

-- no debconf information

Bug#824235: xul-ext-y-u-no-validate: please add firefox dependencies

[Christoph Anton Mitterer]

Package: xul-ext-y-u-no-validate
Version: 2013052407-1
Severity: wishlist


Hi.

Now that Iceweasel is gone and iceweasel a transitional package,
please add proper dependencies, like e.g.:
iceweasel | firefox | firefox-esr

Thanks,
Chris.

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

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

Versions of packages xul-ext-y-u-no-validate depends on:
ii  iceweasel  45.1.1esr-1

xul-ext-y-u-no-validate recommends no packages.

xul-ext-y-u-no-validate suggests no packages.

-- no debconf information

Bug#814563: Abandoned upstream

[Christoph Anton Mitterer]

Hey.

I'd want to object here.

I think this is any extremely helpful add-on, and just because there is
(currently) no active upstream, doesn't mean it must necessarily be
removed.

I think the last version for this add-on was from FF29,... ages ago,...
and it still works just nicely.
Even if FF would change so that this plugin doesn't work any longer
immediately, it's a very simple plugin and could probably be rather
easily adapted.


So pleas refrain from dropping it, unless there would be no way around
it in some point in the future.

Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#824068: sympytexpackage: documentation is non-free

[Norbert Preining]

Hi Francesco,

> I see that you dropped sympytexpackage.pdf from the package: this is
> understandable, in order to remove the serious issue for the time being.
...
> Once the re-licensing is done, sympytexpackage.pdf will be reintroduced
> into the Debian package, I suppose.

Yes.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#824069: sympytexpackage: please include example.tex along with example.pdf

[Norbert Preining]

On Fri, 13 May 2016, Francesco Poli wrote:
> I see that you dropped example.pdf from the Debian package...

Yes, I do not digress from upstream, there too we will remove
example.pdf.

The original author needs to upload a new package to CTAN if
example.pdf (and .tex) should be included.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#824234: Please build mythes-sv

[Gunnar Hjalmarsson]

Package: src:libreoffice-dictionaries
Version: 1:5.1.3-1
Severity: wishlist

As a step in the efforts to make lo-dicts *the* source package for
writing aids in Debian/Ubuntu, I suggest that mythes-sv is built by
lo-dicts. It would install the very same Swedish thesaurus as the
mythes-sv source package currently does, but if someone updates the
thesaurus in the future, it's most convenient that the update lands in
Debian/Ubuntu via lo-dicts.

This will kill the only package I own, but I'll try to live with that. ;)

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

Bug#818432: espresso: FTBFS on armel: hangs during the build

[peter green]

My guess would be that the testsuite is just extremely slow on armel 
(which uses software floating point).


Would it be possible to disable longer-running tests or is the testsuite 
an all-or-nothing thing?

Bug#824233: kmail: all mail data lost after trying to move folder

[Maria]

rl  5.20.2-3+deb8u4

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.26-6
ii  gnupg22.0.26-6
ii  pinentry-gtk2 [pinentry-x11]  0.8.3-2

Versions of packages kmail suggests:
pn  clamav | f-prot-installer
ii  kaddressbook 4:4.14.1-1
ii  kleopatra4:4.14.1-1
ii  procmail 3.22-24
pn  spamassassin | bogofilter | annoyance-filter | spambayes | bsfi  

-- no debconf information

*** /home/poetic-terrorist/Dokumente/akonadi-selftest-report-20160513.txt
Akonadi Server Self-Test Report
===

Test 1:  SUCCESS


Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server
configuration and was found on your system.

File content of '/home/user/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-user.OtpsVc/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


Test 2:  SUCCESS


Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the
recommended setup for a secure system.

Test 3:  SUCCESS


MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server
'/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure
you have the necessary read and execution rights on the server executable. The
server executable is typically called 'mysqld'; its location varies depending
on the distribution.

Test 4:  SUCCESS


MySQL server is executable.
Details: MySQL server found: 160513 13:57:52 [Warning] Using unique option
prefix key_buffer instead of key_buffer_size is deprecated and will be removed
in a future release. Please use the full name instead.
/usr/sbin/mysqld  Ver 5.5.49-0+deb8u1 for debian-linux-gnu on x86_64 ((Debian))


Test 5:  ERROR


MySQL server log contains errors.
Details: The MySQL server error log file /home/user/.local/share/akonadi/db_data/mysql.err
contains errors.

File content of '/home/user/.local/share/akonadi/db_data/mysql.err':
160513  4:42:56 [Note] Plugin 'FEDERATED' is disabled.
160513  4:42:56 InnoDB: The InnoDB memory heap is disabled
160513  4:42:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160513  4:42:56 InnoDB: Compressed tables use zlib 1.2.8
160513  4:42:56 InnoDB: Using Linux native AIO
160513  4:42:56 InnoDB: Initializing buffer pool, size = 80.0M
160513  4:42:56 InnoDB: Completed initialization of buffer pool
160513  4:42:56 InnoDB: highest supported file format is Barracuda.
160513  4:42:56  InnoDB: Waiting for the background threads to start
160513  4:42:57 InnoDB: 5.5.49 started; log sequence number 1813497
160513  4:42:57 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.49-0+deb8u1'  socket: '/tmp/akonadi-user.OtpsVc/mysql.socket'
port: 0  (Debian)


Test 6:  SUCCESS


MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is
readable at /etc/akonadi/mysql-
global.conf.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <k...@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#
sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of
data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for
debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM
information_schema.tables WHERE table_schema not in ("mysql",
"information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show
global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other
internal data structures (default:1M)
# Deprecated i

Bug#824232: RFS: emacs-buttercup/1.5-2 -- behaviour-driven testing for Emacs Lisp packages

[Sean Whitton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for a new version of emacs-buttercup.

Buttercup is an alternative framework for writing test suites for Emacs
Lisp addons that various addons are adopting in preference or in
addition to the ERT testing framework that comes with Emacs.

* Package name: emacs-buttercup
  Version : 1.5-2
  Upstream Author : Jorgen Schaefer 
* URL : https://github.com/jorgenschaefer/emacs-buttercup/
* License : GPL-3+
  Section : lisp

Changes since the last upload:

  * Add patch to fix regexp so that /usr/bin/buttercup ignores tests in
hidden directories in the root of a source tree.
In particular, this ignores phantom tests found in the .pc/ directory.
  * Bump standards version to 3.9.8 (no changes required).

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/e/emacs-buttercup/emacs-buttercup_1.5-2.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/emacs-buttercup.git
cd emacs-buttercup
gbp buildpackage

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#758888: lmms: Provide links to LADSPA plugins in /usr/lib/ladspa

[Javier Serrano Polo]

The vocoder plug-in is included upstream of swh-plugins. It should be
packaged in a new version of swh-plugins; I have filed
https://bugs.debian.org/824211 . Let us wait some days for an answer.


smime.p7s
Description: S/MIME cryptographic signature

Bug#814438: stealth: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

tags 814438 + patch
thanks

The following patch switches debian/rules to "dh" and also fixes this
bug as a side effect.

Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -14,56 +14,22 @@ export LDFLAGS += -lpthread
 
 export CXX = g++
 
-build: build-arch build-indep
+%:
+   dh $@
 
-build-arch:
-   dh_testdir
+override_dh_auto_build-arch:
./build program
./build man
 
-build-indep:
+override_dh_auto_build-indep:
./build uguide
 
-clean:
-   dh_testdir
-   dh_testroot
+override_dh_clean:
./build distclean
dh_clean
 
-install:
-   dh_testdir
-   dh_testroot
-   dh_prep
-   dh_installdirs
-
-   # Add here commands to install the package into debian/stealth.
+override_dh_install-arch:
./build install bdm debian/stealth
 
-binary-indep:
-
-binary-arch: build-arch install
-
+override_dh_install-indep:
./build install au debian/stealth-doc
-
-   dh_testdir
-   dh_testroot
-   dh_installdocs
-   dh_installexamples
-   dh_installmenu
-   dh_installcron
-   dh_installman
-   dh_installinfo
-   dh_installchangelogs
-   dh_link
-   dh_strip
-   dh_compress
-   dh_fixperms
-   dh_installdeb
-   dh_shlibdeps
-   dh_gencontrol
-   dh_md5sums
-   dh_builddeb
-
-binary: binary-arch binary-indep
-.PHONY: build build-indep build-arch clean binary-indep binary-arch binary \
-   install-indep install-arch

Bug#824231: RFS: dh-elpa/0.0.21 -- Debian helper tools for packaging emacs lisp extensions

[Sean Whitton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for an update to dh-elpa.  It fixes two bugs
introduced in the previous upload.

* Package name: dh-elpa
  Version : 0.0.21
  Upstream Author : David Bremner & Sean Whitton
* URL : http://pkg-emacsen.alioth.debian.org/
* License : GPL-3+
  Section : lisp

Changes since the last upload:

  * Actually exclude .pc/ and debian/ directories from ERT tests.
  * Fix Vcs-Git: URI.

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/d/dh-elpa/dh-elpa_0.0.21.dsc

Or build it with gbp:

git clone https://anonscm.debian.org/git/pkg-emacsen/pkg/dh-elpa.git
cd dh-elpa
gbp buildpackage

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#824230: graphite-web: update readme (syncdb is obsolete)

[Javier Barroso]

Package: graphite-web
Version: 0.9.15+debian-1
Severity: wishlist

Dear Maintainer,

It seems like you need to graphite-manage migrate , syncdb has been
deprecated, could be both mentioned

Thank you!


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

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

Versions of packages graphite-web depends on:
ii  adduser3.114
ii  libjs-prototype1.7.1-3
ii  libjs-scriptaculous1.9.0-2
ii  python-cairo   1.8.8-2
ii  python-django  1.9.6-1
ii  python-django-tagging  1:0.4.1-1
ii  python-pyparsing   2.0.3+dfsg1-1
ii  python-simplejson  3.8.2-2
ii  python-tz  2015.7+dfsg-0.1
ii  python-whisper 0.9.15-1
pn  python:any 

graphite-web recommends no packages.

Versions of packages graphite-web suggests:
ii  graphite-carbon  0.9.15-1
ii  libapache2-mod-wsgi  4.3.0-1.1+b1
pn  python-ldap  
pn  python-memcache  
pn  python-mysqldb   

-- Configuration Files:
/etc/graphite/local_settings.py changed [not included]

-- no debconf information

Bug#824173: Info received (Subject: AttributeError: type object 'QUrl' has no attribute 'None')

[Juanjo Benages]

== begin patch

--- book_details.py2016-05-13 18:04:35.620779396 +0200
+++ book_details_new.py2016-05-13 18:05:34.092476918 +0200
@@ -478,7 +478,7 @@
 self._link_clicked = True
 if unicode(link.scheme()) in ('http', 'https'):
 return open_url(link)
-link = unicode(link.toString(QUrl.None))
+link = unicode(link.toString())
 self.link_clicked.emit(link)

 def turnoff_scrollbar(self, *args):

== end patch

Bug#811827: prank: FTBFS with GCC 6: no match for

[Sascha Steinbiss]

Hi all,

I fixed this in svn and also updated hardening and some other minor things.

Cheers
Sascha

On Tue, 19 Jan 2016 18:22:00 -0800 Martin Michlmayr  wrote:
> Package: prank
> Version: 0.0.150803-1
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-no-match
> 
> This package fails to build with GCC 6.  GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.
> 
> Note that only the first error is reported; there might be more.  You
> can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
> you can set CC=gcc-6 CXX=g++-6 explicitly.
> 
> You may be able to find out more about this issue at
> https://gcc.gnu.org/gcc-6/changes.html
> 
> > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
> ...
> > g++ -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> > -pipe -O3  -I. -I/usr/include -o bppancestors.o bppancestors.cpp
> > hmmodel.cpp: In member function 'void 
> > HMModel::alignmentModel(AncestralNode*)':
> > hmmodel.cpp:1513:57: error: no match for 'operator<<' (operand types are 
> > 'std::basic_ostream' and 'std::ostream {aka 
> > std::basic_ostream}')
> >  cout<<"HMModel::alignmentModel: impossible 'as'"< >  ^~
> > 
> > hmmodel.cpp:1513:57: note: candidate: operator<<(int, int) 
> > hmmodel.cpp:1513:57: note:   no known conversion for argument 2 from 
> > 'std::ostream {aka std::basic_ostream}' to 'int'
> > In file included from /usr/include/c++/6/istream:39:0,
> >  from /usr/include/c++/6/fstream:38,
> >  from hmmodel.cpp:24:
> > /usr/include/c++/6/ostream:108:7: note: candidate: 
> > std::basic_ostream<_CharT, _Traits>::__ostream_type& 
> > std::basic_ostream<_CharT, _Traits>::operator<<(std::basic_ostream<_CharT, 
> > _Traits>::__ostream_type& (*)(std::basic_ostream<_CharT, 
> > _Traits>::__ostream_type&)) [with _CharT = char; _Traits = 
> > std::char_traits; std::basic_ostream<_CharT, _Traits>::__ostream_type 
> > = std::basic_ostream]
> >operator<<(__ostream_type& (*__pf)(__ostream_type&))
> >^~~~
> > 
> > /usr/include/c++/6/ostream:108:7: note:   no known conversion for argument 
> > 1 from 'std::ostream {aka std::basic_ostream}' to 
> > 'std::basic_ostream::__ostream_type& 
> > (*)(std::basic_ostream::__ostream_type&) {aka 
> > std::basic_ostream& (*)(std::basic_ostream&)}'
> > /usr/include/c++/6/ostream:117:7: note: candidate: 
> > std::basic_ostream<_CharT, _Traits>::__ostream_type& 
> > std::basic_ostream<_CharT, _Traits>::operator<<(std::basic_ostream<_CharT, 
> > _Traits>::__ios_type& (*)(std::basic_ostream<_CharT, 
> > _Traits>::__ios_type&)) [with _CharT = char; _Traits = 
> > std::char_traits; std::basic_ostream<_CharT, _Traits>::__ostream_type 
> > = std::basic_ostream; std::basic_ostream<_CharT, _Traits>::__ios_type 
> > = std::basic_ios]
> >operator<<(__ios_type& (*__pf)(__ios_type&))
> >^~~~
> > 
> > /usr/include/c++/6/ostream:117:7: note:   no known conversion for argument 
> > 1 from 'std::ostream {aka std::basic_ostream}' to 
> > 'std::basic_ostream::__ios_type& 
> > (*)(std::basic_ostream::__ios_type&) {aka std::basic_ios& 
> > (*)(std::basic_ios&)}'
> > /usr/include/c++/6/ostream:127:7: note: candidate: 
> > std::basic_ostream<_CharT, _Traits>::__ostream_type& 
> > std::basic_ostream<_CharT, _Traits>::operator<<(std::ios_base& 
> > (*)(std::ios_base&)) [with _CharT = char; _Traits = std::char_traits; 
> > std::basic_ostream<_CharT, _Traits>::__ostream_type = 
> > std::basic_ostream]
> >operator<<(ios_base& (*__pf) (ios_base&))
> >^~~~
> > 
> > /usr/include/c++/6/ostream:127:7: note:   no known conversion for argument 
> > 1 from 'std::ostream {aka std::basic_ostream}' to 'std::ios_base& 
> > (*)(std::ios_base&)'
> > /usr/include/c++/6/ostream:166:7: note: candidate: 
> > std::basic_ostream<_CharT, _Traits>::__ostream_type& 
> > std::basic_ostream<_CharT, _Traits>::operator<<(long int) [with _CharT = 
> > char; _Traits = std::char_traits; std::basic_ostream<_CharT, 
> > _Traits>::__ostream_type = std::basic_ostream]
> >operator<<(long __n)
> >^~~~
> > 
> > /usr/include/c++/6/ostream:166:7: note:   no known conversion for argument 
> > 1 from 'std::ostream {aka std::basic_ostream}' to 'long int'
> > /usr/include/c++/6/ostream:170:7: note: candidate: 
> > std::basic_ostream<_CharT, _Traits>::__ostream_type& 
> > std::basic_ostream<_CharT, _Traits>::operator<<(long unsigned int) [with 
> > _CharT = char; _Traits = std::char_traits; std::basic_ostream<_CharT, 
> > _Traits>::__ostream_type = std::basic_ostream]
> >operator<<(unsigned long __n)
> >^~~~
> > 
> > /usr/include/c++/6/ostream:170:7: note:   no known conversion for argument 
> > 1 from 'std::ostream {aka std::basic_ostream}' to 'long unsigned int'
> > 

Bug#824229: metapixel-prepare fails - metapixel: rwpng.c:199: open_png_file_writing: Assertion `0' failed.

[Christian Gerth]

Package: metapixel
Version: 1.0.2-7.4+b1
Severity: normal

Hi,

I'm trying to create a metapixel library using the command

metapixel-prepare path/to/src/files metapixel_lib

but I'm getting the error message

libpng error: Invalid palette
metapixel: rwpng.c:199: open_png_file_writing: Assertion `0' failed.
Aborted
Error running metapixel - skipping file path/to/src/files/foo.jpg

for each file in the source directory.



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

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

Versions of packages metapixel depends on:
ii  libc62.22-7
ii  libgif7  5.1.4-0.1
ii  libjpeg62-turbo  1:1.4.2-2
ii  libpng16-16  1.6.21-4
ii  zlib1g   1:1.2.8.dfsg-2+b1

metapixel recommends no packages.

metapixel suggests no packages.

-- no debconf information

Bug#824215: Wrong url

[Denys]

Sorry. I missed an url. This is correct one:
https://quickgit.kde.org/?p=baloo.git=commitdiff=06
efd6c05c15a64b53daac9e598666af584488ec[1] 



[1] 
https://quickgit.kde.org/?p=baloo.git=commitdiff=06
efd6c05c15a64b53daac9e598666af584488ec

Bug#824228: diamond: python-configobj depend is missing

[Javier Barroso]

Package: diamond
Version: 4.0.195-1
Severity: important

Dear Maintainer,

I need to install python-configobj, if it is not installed, diamond will
not start:

$ sudo systemctl status diamond
● diamond.service - diamond - A system statistics collector for graphite
   Loaded: loaded (/usr/lib/systemd/system/diamond.service; disabled;
vendor preset: enabled)
   Active: failed (Result: exit-code) since vie 2016-05-13 23:56:04 CEST; 3s ago
  Process: 15430 ExecStart=/usr/bin/python /usr/bin/diamond
--log-stdout --foreground (code=exited, status=1/FAILURE)
 Main PID: 15430 (code=exited, status=1/FAILURE)


Thank you very much

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

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

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


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

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

Versions of packages diamond depends on:
ii  adduser 3.114
ii  python-diamond  4.0.195-1
pn  python:any  

diamond recommends no packages.

diamond suggests no packages.

-- Configuration Files:
/etc/diamond/diamond.conf.example [Errno 2] No existe el fichero o el
directorio: u'/etc/diamond/diamond.conf.example'

-- no debconf information

Bug#805112: zorp: FTBFS: SSLv3 method removed

[Sebastian Andrzej Siewior]

On 2015-11-14 21:50:33 [+0100], Kurt Roeckx wrote:
> The SSLv3 methods in the openssl package have been removed and as
> a result your package can't be build anymore.

SZALAY, do you plan to look at this?
The 3.9.5 release is from 2012, there is 3.9.8 from 2014 and v6.0.7 from
2015. Would it make sense to remove this from unstable and upload a
newer version?
Would someone like to see this fixed? I am currently unsure if we would
be better off with or without it.

Sebastian

Bug#803550: [Debian-med-packaging] Bug#803550: rsem: uninstallable on architectures without bowtie

[Michael Crusoe]

Thanks Sascha!
Pe 13 mai 2016 11:45 p.m., "Sascha Steinbiss"  a
scris:

> Hi all,
>
> I re-introduced the build dependency on bowtie and also did some minor
> housekeeping. Committed the fix in git.
>
> Cheers
> Sascha
>
> > On 19 Mar 2016, at 14:34, Andreas Beckmann  wrote:
> >
> > Package: rsem
> > Followup-For: Bug #803550
> >
> > Hi,
> >
> > the
> >  B-D: bowtie | bowtie2
> > was dropped in the last upload, causing uninstallable rsem packages
> > being produced for many architectures, again.
> >
> >
> > Andreas
> >
> > ___
> > Debian-med-packaging mailing list
> > debian-med-packag...@lists.alioth.debian.org
> >
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>
>

Bug#824210: grilo-plugins-0.3: SEGV in glib when grilo-plugins is enabled

[Alberto Garcia]

Control: reassign -1 rhythmbox

On Fri, May 13, 2016 at 11:36:21AM -0700, Diane Trout wrote:

> Rhythmbox in unstable under wayland crashes either a few moments
> after its loaded if grilo-plugins are enabled, or immediately upon
> enabling grilo if it was disabled on startup.

Thanks for the bug report.

However, from the backtrace that you attach and from the comments on
the upstream bugzilla it seems that the problem is not in Grilo but in
Rhythmbox.

I'm reassigning the bug then.

Thanks,

Berto

Bug#824059: plasma-desktop: When used with pulseaudio, can make people deaf

[Maximiliano Curia]

Control: severity -1 important

Hi,

I agree that this bug is important, and I'm aware that it's been around for 
quite sometime now, although I thought it was fixed.


Currently, I'm not being able to reproduce it. Digging into the code I found 
that the knotifications mangling of the volumes was fixed back in frameworks 
5.6, and the kde4 notifications were fixed in kde-runtime 4:15.04. The 
notifications I've tested don't trigger a volume change, I've tested this 
using the gstreamer backend and the vlc backend.


Could you please provide as much detail as possible with regards to how you 
configured the notifications and which notifications are triggering this?


Also please show the output of apt policy kde-runtime, and any other 
information that you consider valuable.


Thanks!

Happy hacking,
--
"Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs, and the Universe trying to produce
bigger and better idiots. So far, the Universe is winning."
-- Rich Cook
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#823105: mock depends on usermode

[Holger Levsen]

Hi,

mock depends on usermode, so please don't remove it.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#258096: My Dear

[Patrick]

Hi
  I hope you are good today. I am the Executive Accountant in the Energy 
Ministry of Kenya. We have some money ready for investment in your country. If 
you are willing to partner with us ,kindly write me an email at 
(p.muth...@yandex.com ) ,for more briefing.  

Thank you.  

Dr Patrick Muthola.

Bug#824071: closed by Norbert Preining <prein...@debian.org> (Bug#824071: fixed in texlive-extra 2016.20160512-1)

[Francesco Poli]

On Thu, 12 May 2016 10:27:17 + Debian Bug Tracking System wrote:

[...]
>* adjust sympytex python path (Closes: #824071)
[...]

Thanks a lot for applying my patch!

Bye.

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpv_wNh2gKJ7.pgp
Description: PGP signature

Bug#797867: libzypp: ABI transition needed for libstdc++ v5

[Sebastian Andrzej Siewior]

On 2015-10-30 15:56:38 [+0100], Emilio Pozuelo Monfort wrote:
> This is a friendly ping wrt the libstdc++ ABI transition. Your package is 
> listed
> as needing a transition but has seen no action. It'd be good to get things 
> going
> so we can finish the transition soon.

Mike, this package didn't complete the libstdc++ v5 transition. From #797869 it
reads like it does not provide a stable ABI/symbols. Upstream has a
newer version sitting (15.22.0).
Would you mind to remove it from unstable until the two RC bugs are
resolved? libzypp also depends on libssl1.0.0 which I am trying to decruft.

> Cheers,
> Emilio

Sebastian

Bug#803550: [Debian-med-packaging] Bug#803550: rsem: uninstallable on architectures without bowtie

[Sascha Steinbiss]

Hi all,

I re-introduced the build dependency on bowtie and also did some minor 
housekeeping. Committed the fix in git.

Cheers
Sascha

> On 19 Mar 2016, at 14:34, Andreas Beckmann  wrote:
> 
> Package: rsem
> Followup-For: Bug #803550
> 
> Hi,
> 
> the
>  B-D: bowtie | bowtie2
> was dropped in the last upload, causing uninstallable rsem packages
> being produced for many architectures, again.
> 
> 
> Andreas
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging

Bug#824069: sympytexpackage: please include example.tex along with example.pdf

[Francesco Poli]

On Thu, 12 May 2016 09:50:46 +0900 Norbert Preining wrote:

> Hi Francesco,
> 
> > [1] https://github.com/tmolteno/SympyTeX/blob/master/example.tex
> 
> Indeed, also this needs to be included or the pdf removed. Also 
> contacted the author.

Hello again,
I see that you dropped example.pdf from the Debian package...

But example.tex (source for example.pdf) is distributed under the GNU
GPL v2 or later, and hence the two files are perfectly fine for Debian
main (as long as example.tex is included in the Debian source package,
of course).

What I suggested in my bug report was to also ship example.tex in the
Debian binary package (installed in the same directory as example.pdf),
since it's useful as documentation.

Could this be done, please?

Thanks for your time and patience.
Bye.

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpfgKqK4Cpa4.pgp
Description: PGP signature

Bug#824227: ITP: galileo -- Utility to securely synchronize a Fitbit device with the Fitbit web service

[Dylan]

Package: wnpp
Severity: wishlist
Owner: Dylan Aïssi 

Package name: galileo
URL: https://bitbucket.org/benallard/galileo/
License: LGPL-3+
Description: Utility to securely synchronize a Fitbit device with the
Fitbit web service
 Galileo is a Python utility to securely synchronize a Fitbit device
with the Fitbit web service. It allows you to browse your data on
their website, and compatible applications.

This package will be maintained by the Debian Med team at:
https://anonscm.debian.org/git/debian-med/galileo.git

Bug#824068: sympytexpackage: documentation is non-free

[Francesco Poli]

On Thu, 12 May 2016 09:44:13 +0900 Norbert Preining wrote:

> Hi Francesco,
> 
> > The Creative Commons Attribution-NonCommercial-ShareAlike v3.0 license
> 
> Indeed, thanks. I have contacted the author as well as TeX Live upstream.
> Either it will be relicened or we remove it from TeX Live (upstream)
> and then also from Debian.

Hello Norbert,
thanks for your very quick reaction!   :-)
I see that you dropped sympytexpackage.pdf from the package: this is
understandable, in order to remove the serious issue for the time being.

Needless to say, I really hope the author of sympytexpackage may be
persuaded to re-license the documentation under the same license as the
rest of sympytexpackage (GNU GPL v2 or later).
I think that having documentation under the same terms as the
executable code is important, especially in the case of TeX literate
programming that mixes the two parts so much...

Once the re-licensing is done, sympytexpackage.pdf will be reintroduced
into the Debian package, I suppose.

Thanks again.
Bye.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgponpZr9LMVQ.pgp
Description: PGP signature

Bug#788324: Unsupported on arches besides i386 and amd64

[Joachim Breitner]

Hi,

Am Freitag, den 13.05.2016, 18:40 + schrieb Jurica Stanojkovic:
> There is a solution proposed on upstream.
> https://github.com/bos/criterion/commit/0673606c70ba22234b8908a8f30e8
> ea588c6d776
> 
> With solution proposed on upstream I was able to build package
> successfully on mips, mipsel, amd64 and i386.

thanks for testing.

> However this solution is using assembly code on amd64 and not for
> i386 and other archs.
> 
> If you think that we could remove assembly code completely, 
> I am sending a patch that use proposed solution but does not include
> assembly code.

Why do you want to remove the (presumably faster) code on amd64? I
don’t see a reason to diverge from upstream here.

We should simply upgrade the package to 1.1.1.0 to get the fix.

Greetings,
Joachim
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


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

Bug#824226: openjdk-8-jre: ATK bridge causes segfault when loading JR

[D Haley]

Package: openjdk-8-jre
Version: 8u91-b14-2
Severity: normal

Dear Maintainer,

When attempting to launch Jabref after updating openjdk from ( i believe, based 
upon apt history) 7u91-2.6.3-1 to 8u91-b14-2, i found that the following 
segfault occured:


** (java:13536): WARNING **: Couldn't register with accessibility bus: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7fe243798a42, pid=13536, tid=140609524610816
#
# JRE version: OpenJDK Runtime Environment (8.0_91-b14) (build 
1.8.0_91-8u91-b14-2-b14)
# Java VM: OpenJDK 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 
compressed oops)
# Problematic frame:
# C  [libatk-bridge-2.0.so.0+0x10a42]
#
# Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/username/hs_err_pid13536.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted

This appears to have been reported elsewhere in bug 798131 for freemind. , when 
following the suggestion to disable the ATK bridge line int 
/etc/java-8-openjdk/accessibility.properties , the program was able to run 
successfully.  I am running XFCE, as per one commenter in 798131m, however  
ulike in that bug report, I have assitive technologies in XFCE enabled.


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages openjdk-8-jre depends on:
ii  libasound21.1.0-1
ii  libatk-wrapper-java-jni   0.33.3-6+b1
ii  libc6 2.22-7
ii  libgif7   5.1.4-0.1
ii  libgl1-mesa-glx [libgl1]  11.1.3-1
ii  libgtk2.0-0   2.24.30-1.1
ii  libjpeg62-turbo   1:1.4.2-2
ii  libpng16-16   1.6.21-4
ii  libpulse0 8.0-2+b2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxrandr22:1.5.0-1
ii  openjdk-8-jre-headless8u91-b14-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages openjdk-8-jre recommends:
ii  fonts-dejavu-extra  2.35-1
ii  libgconf-2-43.2.6-3
ii  libgnome-2-02.32.1-5
ii  libgnomevfs2-0  1:2.24.4-6.1+b1

Versions of packages openjdk-8-jre suggests:
pn  icedtea-8-plugin  

-- no debconf information

Bug#824225: ITP: lxqt-l10n -- Language packages for LXQt

[Alf Gaida]

Package: wnpp
Severity: wishlist
Owner: Alf Gaida 

* Package name: lxqt-l10n
  Version : 0.10.9~beta
  Upstream Author : LXQt team 
* URL : https://github.com/lxde/translations
* License : (LGPL)
  Programming Lang: (etc.)
  Description : Language packages for LXQt
 
The package will provide all localisations for the LXQt packages. 
The package will be team maintained by the LXQt packaging team.

Bug#824196: [Pkg-clamav-devel] Bug#824196: clamav-daemon: clamd crashes daily

[Sebastian Andrzej Siewior]

On 2016-05-13 14:06:27 [-0600], Will Aoki wrote:

> That's it. A space is logged after the colon, but nothing else.

interresting. The source says that there should be more.
Your bug report says you run i386. Is this the case for the server or
just the machine you made the report?

> May 13 08:56:05 skunk clamd[12310]: accept() failed:
> May 13 08:56:05 skunk clamd: Last message 'accept() failed: ' repeated 198 
> times, suppressed by syslog-ng on [the loghost]
> May 13 08:56:11 skunk clamd[12310]: accept() failed:
> May 13 08:56:11 skunk clamd: Last message 'accept() failed: ' repeated 199 
> times, suppressed by syslog-ng on [the loghost]

Ah right, there two loops. So clamd tries mutliple times and somehow
always runto into the same error.

> I've noticed that /tmp is filling up with directories named e.g.
> clamav-fe97224f9fa888d6e2d47ddfee0ca573.tmp

Those are created by some filetypes during scan but should have been
cleaned up. You can remove them. But this looks like it terminated in a
hurry.

Could you enable debug loglevel? Maybe it logs something usefull. 
Also would it be possible to enable core dumps and see if it dumps
something? Could start clamd from commandline in foreground so you can
log its exit code? Ah. And could please check with top or something if
the memory of clamd grows overtime? In case it has a memory leak
somewhere.

If you manage to give me something to reproduce it locally (like a VM
image) I might try it when I have some time.

Sebastian

Bug#819122: diff NMU for elixir-lang_1.1.0-1.1

[Anton Gladky]

tags 819122 +pending +patch
thanks

Dear maintainer,

I have prepared an NMU (versioned as 1.1.0-1.1) and
uploaded to DELAYED/2.

Please fell free to tell me if I should delay it longer, cancel
or reschedule. Diff is attached.

Best regards

Anton


nmu.debdiff
Description: Binary data

Bug#824158: Installing allegro4 and allegro5 side-by-side in Debian

[Mason]

Hello,

I've had a chat with the Allegro devs, and they are positive
that allegro4 and allegro5 can coexist (otherwise it's a bug
that needs fixing).

So the fix seems trivial: to remove the relevant "Conflicts"
clauses. Tobias, Andreas, what do you think?

Regards.


Patch for git://anonscm.debian.org/pkg-games/allegro5.git

diff --git a/debian/control b/debian/control
index 832c49a..69fd61a 100644
--- a/debian/control
+++ b/debian/control
@@ -63,7 +63,7 @@ Depends: ${misc:Depends},
  libxinerama-dev,
  libxpm-dev,
  libxrandr-dev
-Conflicts: liballegro-dev, liballegro4-dev
+Conflicts: liballegro-dev
 Recommends: liballegro-acodec5-dev,
 liballegro-audio5-dev,
 liballegro-dialog5-dev,


Patch for git://anonscm.debian.org/pkg-games/allegro4.4.git

diff --git a/debian/control b/debian/control
index f557573..75ddbb9 100644
--- a/debian/control
+++ b/debian/control
@@ -54,7 +54,7 @@ Depends: ${misc:Depends},
  libxxf86vm-dev,
  libxcursor-dev
 Provides: liballegro4.2-dev, liballegro-dev
-Conflicts: liballegro-dev-common, liballegro4a, liballegro-dev, 
liballegro4.2-dev, liballegro5-dev
+Conflicts: liballegro-dev-common, liballegro4a, liballegro-dev, 
liballegro4.2-dev
 Replaces: liballegro-dev-common, liballegro4a, liballegro-dev, 
liballegro4.2-dev
 Description: development files for the Allegro library
  This package contains the development headers for the Allegro library.

Bug#813313: [planet-venus] fails on SNI enabled websites

[Antoine Beaupré]

> The faulty code in planet venus itself is in planet/spider.py, around
> line 300, in the httpThread function. It *looks* like it could be fairly
> easy to convert it to requests, as the API usage is fairly superficial.

Well, "easy"... There's only a few calls to httplib itself, but it makes
heavy use of the API it turns out. It uses the resp object extensively,
and even uses the cache. So it will need to be cleaned up and use
cachecontrol:

https://github.com/ionrock/cachecontrol

... which is not in stable...

Hopefully, httplib2 will just fix this?

a.
-- 
Marijuana grows naturally on the planet.
Mushrooms grows naturally on the planet.
Don't you think making nature against the law is a bit... unnatural?
- Bill Hicks

Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]‏

[Gianfranco Costamagna]

Hi,

>Isn't I'm supposed to raise the version number? or is "+nmu1" enough? 



I'm not sure, but in fact dch --nmu is not raising it, so I guess
1.8.2+nmu1 is fine, so the maintainer can still bump and release an NMU 
acknowledge
called 1.8.3


>It part of the fix, but not needed to fix #818540 (as I understand).


not a problem
>No file attached here? You talking about this file correct?
>https://patches.ubuntu.com/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.2ubuntu1.patch


yes
>I did as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818540#39 
>suggested, do you disagree with that solution? Is the original solution 
>preferred?


it is fine, I just want to know your opinion.

>Just pushed to mentors.


seems still not working completely...
this is what I get on a clean pbuilder environment
ERROR: failed to retrieve status information from google : W: 
http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by 
key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak digest algorithm (SHA1)
W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by 
key 3B068FB4789ABE4AEFA3BB491397BC53640DB551 uses weak digest algorithm (SHA1)


the ubuntu version prints the warning but starts the download anyway.

what do you think about?

G.



> Date: Fri, 13 May 2016 19:41:25 +
> From: locutusofb...@debian.org
> To: klausenb...@hotmail.com; ba...@debian.org; 824...@bugs.debian.org
> Subject: Re: Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]‏
>
> control: owner -1 !
> control: tags -1 moreinfo
>
>
> Hi, some questions about versioning and changelog:
>
> 1) why 1.8.3+nmu1 and not 1.8.2+nmu1?
> 2) why UNRELEASED? please set unstable
>
> "* Validate deb file with sha256sum." <-- isn't this part of the fix for bug 
> #818540?
>
> the other stuff LGTM, I hope to sponsor it soon :)
>
> BTW did you see the ubuntu diff?
> you might want to take some bits
>
> (attaching the debdiff between debian and ubuntu, I'm not talking about 
> fields like changelog entries
> and maintainer field, more about the update script)
>
> thanks!
>
> G.
>
>
> Il Venerdì 13 Maggio 2016 15:39, Kristian Klausen  
> ha scritto:
> Package: sponsorship-requests
> Severity: important
>
> Dear mentors,
>
> I am looking for a sponsor for my package "pepperflashplugin-nonfree":
>
> * Package name : pepperflashplugin-nonfree
> Version : 1.8.3+nmu1
> Upstream Author : Bart Martens 
> * URL : http://wiki.debian.org/PepperFlashPlayer
> * License : GPL3
> Section : Browser plugin
>
> It builds those binary packages:
>
> pepperflashplugin-nonfree
>
> To access further information about this package, please visit the following 
> URL:
>
> https://mentors.debian.net/package/pepperflashplugin-nonfree
>
>
> Alternatively, one can download the package with dget using this command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/contrib/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.3+nmu1.dsc
>
>
> Changes since the last upload:
>
> pepperflashplugin-nonfree (1.8.3+nmu1) UNRELEASED; urgency=medium
>
> * Non-maintainer upload.
> * Update Google public key. Closes: #823005.
> * Remove 32 bit support. Closes: #816848.
> * Don't treat `apt-get update` warnings as errors. Closes: #818540.
> * Validate deb file with sha256sum.
>
> -- Kristian Klausen  Fri, 13 May 2016 14:44:52 +0200
>
>
> Regards,
> Kristian Klausen

Bug#823568: krb5-auth-dialog: Don't autostart for non-Kerberos users

[Daniel Richard G.]

On Fri, 2016 May 13 12:22+0200, Guido Günther wrote:
> > 
> > I can just click on the little systray icon. How is the notification
> > necessary for me to get a ticket? (I am using the program under
> > Xfce, if that makes a difference.)
>
> Only if there is such an icon. E.g. GNOME relies solely on
> notifiations (which, at least there, is a good thing).

Oh. Okay. That's a different way of doing things...

> Yeah, I agree that the startup case should better indicate that the
> user does not have any creds, not that they're expired.

That would be great.

On a similar note, regarding the man page description for the --auto
option:

If this option is specified, krb5-auth-dialog will exit if it finds
that the user has no Kerberos credentials.

This could be misread as stating that the program will exit at a later
time when the user's credentials expire. I would at least add the words
"at startup" or "when it starts." Alternately, I'd suggest this
elaborated wording:

If this option is specified, krb5-auth-dialog will start only if it
finds that the user has Kerberos credentials. This may be used to
ensure that only users who actually use Kerberos see the program.
(Note that in some settings, users may authenticate to Kerberos at a
later time even if they do not have Kerberos credentials initially.)

> The Systray icon is a bandaid. On a proper integrated desktop it
> should not be needed to get a ticket.

Xfce may not be that, but in that environment, the systray icon works
perfectly :]

Bug#824224: coccinelle: Typo in the package description

[Thomas Vincent]

Source: coccinelle
Severity: minor

Dear Maintainer,

I spotted a typo in the description of coccinelle while translating it to 
french.
"Coccinelle" is indeed mispelled "Cocinelle" and should be corrected.

Please note that the coccinelle-doc package is also affected.

Thanks for your work on coccinelle,
Thomas


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

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

Bug#815670: kalarm: Some KDE applications do not autorstart properly

[Maximiliano Curia]

Control: severity -1 normal
Control: fixed -1 4:15.08.3-1
Control: tag -1 + upstream
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=358027

Hi,

As mentioned in the upstream bug, the bug is particular to the way the kde4 
version of kalarm used to autostart itself, and is fixed in a new upstream 
release. I'm tagging the corresponding fixed version, and downgrading the 
severity as this doesn't seem to be a broader issue.


Happy hacking,
--
"If the code and the comments disagree, then both are probable wrong."
-- Norm Schryer
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#824223: letsencrypt.sh: Provide more automatism for letsencrypt.sh

[Cord Beermann]

Package: letsencrypt.sh
Version: 0.1.0-2
Severity: wishlist

I continue the discussion from Bug#822493 here:

Please provide a cron based automatism for refreshing certificates.

It would be nice that users only need to provide the hostname(s) they 
want to get a certificate for in /etc/letsencrypt.sh/ and a cronjob 
that runs letsencrypt.sh -c takes care for refreshing it before it expires.

That script would also need hooks to reload daemons that need to know 
about a certificate-change.

Debconf could ask if automatic refresh is activated. 

Cord

Bug#823186: chromium: crashes on many websites

[Boris Pek]

Hi,

I have tested Chromium 50.0.2661.94-1 on few other PCs and laptop and there are
such results:
* it works absolutely fine on PC and laptop with amd64 Debian Sid systems
* it crashes at tested web sites on PC with i686 Debian Sid system
  (as well as on my laptop with i686 Debian Sid system)

It looks that something is broken on 32-bit systems. Probably it is related with
discontinuing of support of Google Chrome for 32-bit Linux-based systems...

Best regards,
Boris

Bug#824222: [debian-refcard] change build mechanism to dblatex for ar, hi, ml

[Holger Wansing]

Package: debian-refcard
Tags: patch
thanks


The attached patch switches the build chain for ar, hi and ml, to use dblatex
instead of xmlroff (patch by victory, thanks).

Please note, that the patch is only a draft, maybe other fonts would be
better. To sort this out, proofreaders for the respective languages are
needed and info from them, which fonts they prefer.
Since I didn't got answers from translators for this languages, I store the
draft as a bugreport.



Holger


-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Index: Makefile
===
--- Makefile	(Revision 11166)
+++ Makefile	(Arbeitskopie)
@@ -50,7 +50,7 @@
 ifeq ($(USE_DBLATEX),2)
 	XMLROFF_LANGS=
 else
-	XMLROFF_LANGS=ar he hi ml
+	XMLROFF_LANGS=he
 endif
 else
 XMLROFF_LANGS=$(A4_LANGS)
Index: dblatex.xsl
===
--- dblatex.xsl	(Revision 11166)
+++ dblatex.xsl	(Arbeitskopie)
@@ -23,6 +23,21 @@
 	\setsansfont{HanaMinA}
 	\setmonofont{HanaMinA}
 
+
+\setmainfont{Samanata}
+\setsansfont{Samanata}
+\setmonofont{Samanata}
+
+
+\setmainfont{AnjaliOldLipi}
+\setsansfont{Suruma}
+\setmonofont{AnjaliOldLipi}
+
+
+\setmainfont{Amiri}
+\setsansfont{Amiri}
+\setmonofont{Amiri}
+
 
 \setmainfont{DejaVu Serif}
 \setsansfont{DejaVu Sans}
Index: debian/control
===
--- debian/control	(Revision 11166)
+++ debian/control	(Arbeitskopie)
@@ -10,6 +10,9 @@
dia,
docbook-xsl,
fonts-hanazono,
+   fonts-deva-extra,
+   fonts-smc,
+   fonts-hosny-amiri
ghostscript,
lmodern,
pdfjam,

Bug#813313: [planet-venus] fails on SNI enabled websites

[anarcat]

Control: forwarded -1 https://github.com/jcgregorio/httplib2/issues/233 

On Wed, Feb 10, 2016 at 01:05:59AM +0100, Jakub Wilk wrote:
> * anarcat , 2016-02-09, 09:33:
> >This is typical of Python apps that depend only on urllib and so on.
> 
> Not really. Python's stdlib supports SNI since 2.7.9, which was the first
> version that enabled certificate verification by default, and what's in
> jessie.
> 
> Here the culrprit is httplib2: [...]

You're right of course. Here's the upstream bug:

https://github.com/jcgregorio/httplib2/issues/233

httplib2 folks say that the problem doesn't appear in Python3, so maybe
Venus could run in Py3k? I actually doubt it, considering that software
hasn't been updated since well, 2010 or so...

The number of failed hosts keeps on growing in the meantime:

$ grep -c 'Server presented certificate that does not match host' planet.log.0
22

Note that those are not all let's encrypt certs, but they are probably
mostly SNI.

Those wishing to reproduce the issue can follow the instructions on the
wiki page here:

https://wiki.debian.org/PlanetDebian#test

Or simply run the bootstrap script:

http://anonscm.debian.org/viewvc/planet-debian/trunk/planet-bootstrap.sh?view=co=text%2Fplain

The faulty code in planet venus itself is in planet/spider.py, around
line 300, in the httpThread function. It *looks* like it could be fairly
easy to convert it to requests, as the API usage is fairly superficial.

A.


signature.asc
Description: Digital signature

Bug#824196: [Pkg-clamav-devel] Bug#824196: clamav-daemon: clamd crashes daily

[Will Aoki]

On Fri, May 13, 2016 at 09:35:07PM +0200, Sebastian Andrzej Siewior wrote:
> On 2016-05-13 09:43:24 [-0600], Will Aoki wrote:
> > Before crashing, the daemon spews the message
> > 
> >accept() failed:
> This is it? Nothing more? There should be an error message included
> after the colon.

That's it. A space is logged after the colon, but nothing else.

May 13 08:56:05 skunk clamd[12310]: accept() failed:
May 13 08:56:05 skunk clamd: Last message 'accept() failed: ' repeated 198 
times, suppressed by syslog-ng on [the loghost]
May 13 08:56:11 skunk clamd[12310]: accept() failed:
May 13 08:56:11 skunk clamd: Last message 'accept() failed: ' repeated 199 
times, suppressed by syslog-ng on [the loghost]

I've noticed that /tmp is filling up with directories named e.g.
clamav-fe97224f9fa888d6e2d47ddfee0ca573.tmp

> You mean you gave a "normal" file and it was reported as a virus?

It's a test we run to make sure that the our exclusions of two PUA
signatures work. We want most PUA signatures, but we don't want to use
these two.

We added the exclusion and the test earlier this week, after the crashes
had started.

Bug#824221: debhelper: Standards-Version 3.9.7 recommends to install additional docs under the main package

[Sandro Knauß]

Package: debhelper
Version: 9.20160403
Severity: normal

Hey,

Standard-Version 3.9.7 recommends that additional documentation is installed 
under 
/usr/share/doc/ instaed of /usr/share/doc/-doc

It would be nice if debhelper can handle this in a nice way.
* For example an additional option to install all files in -doc.docs 
under /usr/share/doc/
* adding a second coloum to *docs file with the pacakagename where to install

It would help a lot to comply with Standards-Version 3.9.7. Because the only 
way to comply sofar is to install everywith with the .install files.

Regards,

sandro

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

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

Versions of packages debhelper depends on:
ii  autotools-dev20160430.1
ii  binutils 2.26-9
ii  dh-autoreconf12
ii  dh-strip-nondeterminism  0.016-1
ii  dpkg 1.18.7
ii  dpkg-dev 1.18.7
ii  file 1:5.25-2
ii  libdpkg-perl 1.18.7
ii  man-db   2.7.5-1
ii  perl 5.22.2-1
ii  po-debconf   1.0.19

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201606

-- no debconf information

Bug#824220: RFS: ws-butler/0.3+git.a998a23-1 [ITP] -- unobtrusively remove trailing whitespace in Emacs

[Sean Whitton]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package ws-butler.

This package provides ws-butler-mode and ws-butler-global-mode.  Upon
saving a file in Emacs, these modes delete trailing whitespace on lines
of the buffer that have been edited.

As compared with simply calling delete-trailing-whitespace in your
before-save-hook, ws-butler has the advantage of not cluttering up
version control commits with whitespace cleanup outside of the part of
the file you have edited.

I am packaging version 0.3+git.a998a23 because since version 0.3
upstream has refactored ws-butler's code quite significantly.  This
version is not unstable -- upstream just haven't tagged a release for a
while.

I intend to maintain this as part of the pkg-emacsen team.

* Package name: ws-butler
  Version : 0.3+git.a998a23-1
  Upstream Author : Le Wang
* URL : https://github.com/lewang/ws-butler
* License : GPL-3+
  Section : lisp

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/w/ws-butler/ws-butler_0.3+git.a998a23-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/ws-butler.git
cd ws-butler
gbp buildpackage

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#824219: Missing dependency on libcgi-pm-perl

[Iustin Pop]

Package: dhelp
Version: 0.6.21+nmu6
Severity: normal

My autopkg tests which use dhelp are failing, and I can confirm this is
a fresh chroot install:

$ apt-get install dhelp
(installs recommends as well)
$ dhelp foobar
Can't locate CGI.pm in @INC (you may need to install the CGI module)
(@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.2
/usr/local/share/perl/5.22.2 /usr/lib/x86_64-linux-gnu/perl5/5.22
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22
/usr/share/perl/5.22 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base) at /usr/lib/cgi-bin/dsearch line
27.
BEGIN failed--compilation aborted at /usr/lib/cgi-bin/dsearch line 27.

Indeed, dquery imports CGI, but there's no dependency declared on it.

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

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

Versions of packages dhelp depends on:
ii  doc-base  0.10.7
ii  libdata-page-perl 2.02-1
ii  libhtml-parser-perl   3.72-1
ii  liblocale-gettext-perl1.07-1+b1
ii  libtemplate-perl  2.24-1.2+b2
ii  liburi-perl   1.71-1
ii  perl-modules-5.22 [perl-modules]  5.22.2-1
ii  poppler-utils 0.38.0-3
ii  pstotext  1.9-6+b1
ii  ruby  1:2.3.0+4
ii  ruby-bdb  0.6.6-2+b3
ii  ruby-debian   0.3.9+b6
ii  ruby-gettext  3.1.7-1
ii  ruby2.1 [ruby-interpreter]2.1.5-4
ii  ruby2.2 [ruby-interpreter]2.2.4-1
ii  ruby2.3 [ruby-interpreter]2.3.1-1
ii  swish++   6.1.5-3
ii  ucf   3.0036

Versions of packages dhelp recommends:
ii  chromium [www-browser] 50.0.2661.94-1
ii  firefox-esr [www-browser]  45.1.1esr-1
ii  html2text  1.3.2a-18+b1
ii  lynx [www-browser] 2.8.9dev9-1
ii  w3m [www-browser]  0.5.3-27

Versions of packages dhelp suggests:
pn  catdvi 
pn  httpd-cgi  
pn  info2www   
pn  man2html   

-- no debconf information

Bug#824218: RFS: ebib/2.5.4-1 [ITP] -- BibTeX database manager for Emacs

[Sean Whitton]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package ebib.

ebib is a useful editor for .bib files in Emacs.  It integrates with
RefTeX and LaTeX-mode to easily add bibliographic references to your
documents.

I intend to maintain this as part of the pkg-emacsen team.

* Package name: ebib
  Version : 2.5.4-1
  Upstream Author : Joost Kremers 
* URL : https://github.com/joostkremers/ebib
* License : BSD-3-clause
  Section : lisp

Download with dget:

dget -x http://mentors.debian.net/debian/pool/main/e/ebib/ebib_2.5.4-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/ebib.git
cd ebib
gbp buildpackage

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#822493: letsencrypt.sh: config file refers to nonexisting documentation

[Mattia Rizzolo]

On Fri, May 13, 2016 at 09:44:31PM +0200, Daniel Beyer wrote:
> On Fri, 2016-05-13 at 20:16 +0200, Cord Beermann wrote:
> > PS: It would also be nice if you add a cronjob to the package for refreshing
> > the configured certificates.
> 
> Of course, we have this in mind, too. But it will take some time to get
> this in place. Feel free to open a separate bug for this in BTS.

Also, consider how hard can be to provide a cronjob that works for all
kind of setup.  I run my letsencrypt.sh under a 'letsencrypt' user, but
clearly that's not everybody's setup.  IMHO before providing such
cronjob we should also provide a full setup, including a system user
that runs letsencrypt.sh.

So, feel free to open a new bug for it, but also to provide some
thoughts on the matter.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#824216: RFS: smex/3.0-1 [ITP] -- M-x interface with Ido-style fuzzy matching

[Sean Whitton]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package smex.

> Smex is a M-x enhancement for Emacs. Built on top of Ido, it provides
> a convenient interface to your recently and most frequently used
> commands.

Smex is a very widely used Emacs addon that it would be nice to have in
Debian.  I intend to maintain it as part of the pkg-emacsen team.

* Package name: smex
  Version : 3.0-1
  Upstream Author : Cornelius Mika
* URL : http://github.com/nonsequitur/smex/
* License : GPL-3+
  Section : lisp

Download with dget:

dget -x http://mentors.debian.net/debian/pool/main/s/smex/smex_3.0-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/smex.git
cd smex
gbp buildpackage

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]‏

[Kristian Klausen]

Hi again G :)

> 1) why 1.8.3+nmu1 and not 1.8.2+nmu1?
Isn't I'm supposed to raise the version number? or is "+nmu1" enough? 

> 2) why UNRELEASED? please set unstable
I didn't noticed it.

> "* Validate deb file with sha256sum." <-- isn't this part of the fix for bug 
> #818540?
It part of the fix, but not needed to fix #818540 (as I understand).

> (attaching the debdiff between debian and ubuntu, I'm not talking about 
> fields like changelog entries
No file attached here? You talking about this file correct?
https://patches.ubuntu.com/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.2ubuntu1.patch

I did as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818540#39 suggested, 
do you disagree with that solution? Is the original solution preferred?


Just pushed to mentors.

- Kristian


> Date: Fri, 13 May 2016 19:41:25 +
> From: locutusofb...@debian.org
> To: klausenb...@hotmail.com; ba...@debian.org; 824...@bugs.debian.org
> Subject: Re: Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]‏
>
> control: owner -1 !
> control: tags -1 moreinfo
>
>
> Hi, some questions about versioning and changelog:
>
> 1) why 1.8.3+nmu1 and not 1.8.2+nmu1?
> 2) why UNRELEASED? please set unstable
>
> "* Validate deb file with sha256sum." <-- isn't this part of the fix for bug 
> #818540?
>
> the other stuff LGTM, I hope to sponsor it soon :)
>
> BTW did you see the ubuntu diff?
> you might want to take some bits
>
> (attaching the debdiff between debian and ubuntu, I'm not talking about 
> fields like changelog entries
> and maintainer field, more about the update script)
>
> thanks!
>
> G.
>
>
> Il Venerdì 13 Maggio 2016 15:39, Kristian Klausen  
> ha scritto:
> Package: sponsorship-requests
> Severity: important
>
> Dear mentors,
>
> I am looking for a sponsor for my package "pepperflashplugin-nonfree":
>
> * Package name : pepperflashplugin-nonfree
> Version : 1.8.3+nmu1
> Upstream Author : Bart Martens 
> * URL : http://wiki.debian.org/PepperFlashPlayer
> * License : GPL3
> Section : Browser plugin
>
> It builds those binary packages:
>
> pepperflashplugin-nonfree
>
> To access further information about this package, please visit the following 
> URL:
>
> https://mentors.debian.net/package/pepperflashplugin-nonfree
>
>
> Alternatively, one can download the package with dget using this command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/contrib/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.3+nmu1.dsc
>
>
> Changes since the last upload:
>
> pepperflashplugin-nonfree (1.8.3+nmu1) UNRELEASED; urgency=medium
>
> * Non-maintainer upload.
> * Update Google public key. Closes: #823005.
> * Remove 32 bit support. Closes: #816848.
> * Don't treat `apt-get update` warnings as errors. Closes: #818540.
> * Validate deb file with sha256sum.
>
> -- Kristian Klausen  Fri, 13 May 2016 14:44:52 +0200
>
>
> Regards,
> Kristian Klausen
  

Bug#824217: RFS: parsebib/1.0.5-1 [ITP] -- Emacs Lisp library for parsing .bib files

[Sean Whitton]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package parsebib.

I am packaging this library as a dependency of ebib, another ITP of
mine.  I intend to maintain it as part of the pkg-emacsen team.

* Package name: parsebib
  Version : 1.0.5-1
  Upstream Author : Joost Kremers 
* URL : https://github.com/joostkremers/parsebib
* License : BSD-3-clause
  Section : lisp

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/p/parsebib/parsebib_1.0.5-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/parsebib.git
cd parsebib
gbp buildpackage

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#749887: Willing to package Go dependencies

[Andreas Noteng]

On 13. mai 2016 17:54, Alexandre Viau wrote:
> Hello,
> 
> I am a member of the Golang Packaging team and I would be willing to
> package all of the Go dependencies.
> 
> If I do that. Would you move foward with the packaging? I am impatient
> to see Syncthing in Debian as I consider that this is a very important
> project.

I can look into it again later. For now my schedule is too busy, at
least until the end of May. If the bug is still open by the time I
finish all of my exams I'll pick it up again.

Andreas



signature.asc
Description: OpenPGP digital signature

Bug#824201: tldp: Test suite fails when run as root.

[Martin A. Brown]

Hello there,

>Hi Martin, I sponsored the package, but with some differences.
>(attaching the Debian directory to this email).
>
>1) the -12 version is already on new queue, so you have to start a new 
>changelog entry
>on top of that one

Right.  Shoot.  I knew that.  Thanks for correcting.

>2) you need to close this particular bug in that changelog entry

Noted.  I see:  (Closes: #xx)

>3) you did make a wrong day in the changelog entry, probably a copy-paste, and 
>probably you didn't
>use dch or date -R to get the correct timestamp.

Your assumption was correct.  Thanks for fixing.  Adjusted my 
sources.

>4) thanks Mattia for being subscribed to unknown packages :)

Agreed.

>thanks for the new version!

And, thank you.

>> >   APT_CONFIG=/var/lib/sbuild/apt.conf
>> >   HOME=/sbuild-nonexistent
>> >   LC_ALL=POSIX
>> >   LOGNAME=root
>> >   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>> >   SCHROOT_ALIAS_NAME=unstable-amd64-debomatic
>> >   SCHROOT_CHROOT_NAME=unstable-amd64-debomatic
>> >   SCHROOT_COMMAND=env
>> >   SCHROOT_GID=0
>> >   SCHROOT_GROUP=root
>> >   
>> > SCHROOT_SESSION_ID=unstable-amd64-debomatic-ec0767d2-2cee-45af-a819-ff581f252f97
>> >   SCHROOT_UID=0
>> >   SCHROOT_USER=root
>> >   SHELL=/bin/sh
>> >   USER=root
>> >   XDG_RUNTIME_DIR=/run/user/0
>> >   XDG_SESSION_ID=c31191
>> > 
>> > When I ran my test suite as the root user on any ol' box, I was able to
>> > reproduce the errors that were showing up in the debomatic build log.  So, 
>> > I
>> > adjusted my test suite and now it succeeds.
>> 
>> o.O this is totally unexpected.
>> Building as root is a so bad thing.

I completely agree!  It surprised the heck out of me, too.

Bye for now and have a good weekend!

-Martin

-- 
Martin A. Brown
http://linux-ip.net/

Bug#822493: [Letsencrypt-devel] Bug#822493: letsencrypt.sh: config file refers to nonexisting documentation

[Daniel Beyer]

Hi Cord,

On Fri, 2016-05-13 at 20:16 +0200, Cord Beermann wrote:
> Package: letsencrypt.sh
> Version: 0.1.0-2
> Followup-For: Bug #822493
> 
> Hello,
> 
> I'd also prefer some more information how this package works. 
> 

The still missing README.Debian is to blame on me. I'll sit down
tomorrow and finally write an initial draft.

> The file could also contain information how to migrate from letsencrypt (the
> python-based package) to letsencrypt.sh, which is the problem i'm
> looking into now.

Upstream provides some information on this topic [1]. It might be worth
to integrate it somehow in letsencrypt.sh.

[1] 
https://github.com/lukas2511/letsencrypt.sh/wiki/Import-from-official-letsencrypt-client


> It should contain information how the conf.d directory has to be used (as far
> as i see files have to be *.sh?) and what format they should have.

Yes, this is the main reason we want to have a README.Debian. I'll post
a link to the draft as soon it is in our packaging repository.


> PS: It would also be nice if you add a cronjob to the package for refreshing
> the configured certificates.

Of course, we have this in mind, too. But it will take some time to get
this in place. Feel free to open a separate bug for this in BTS.


Greetings
Daniel


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

Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]‏

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo


Hi, some questions about versioning and changelog:

1) why 1.8.3+nmu1 and not 1.8.2+nmu1?
2) why UNRELEASED? please set unstable

"* Validate deb file with sha256sum." <-- isn't this part of the fix for bug 
#818540?

the other stuff LGTM, I hope to sponsor it soon :)

BTW did you see the ubuntu diff?
you might want to take some bits

(attaching the debdiff between debian and ubuntu, I'm not talking about fields 
like changelog entries
and maintainer field, more about the update script)

thanks!

G.


Il Venerdì 13 Maggio 2016 15:39, Kristian Klausen  ha 
scritto:
Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "pepperflashplugin-nonfree":

 * Package name: pepperflashplugin-nonfree
 Version : 1.8.3+nmu1
 Upstream Author : Bart Martens 
 * URL : http://wiki.debian.org/PepperFlashPlayer
 * License : GPL3
 Section : Browser plugin

It builds those binary packages:

  pepperflashplugin-nonfree

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/pepperflashplugin-nonfree


Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/contrib/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.3+nmu1.dsc


Changes since the last upload:

pepperflashplugin-nonfree (1.8.3+nmu1) UNRELEASED; urgency=medium

  * Non-maintainer upload.
  * Update Google public key. Closes: #823005.
  * Remove 32 bit support. Closes: #816848.
  * Don't treat `apt-get update` warnings as errors. Closes: #818540.
  * Validate deb file with sha256sum.

 -- Kristian Klausen   Fri, 13 May 2016 14:44:52 +0200


Regards,
Kristian Klausen

Bug#824196: [Pkg-clamav-devel] Bug#824196: clamav-daemon: clamd crashes daily

[Sebastian Andrzej Siewior]

On 2016-05-13 09:43:24 [-0600], Will Aoki wrote:
> After upgrading from 0.98.7+dfsg-0+deb7u1 to 0.99+dfsg-0+deb7u2 two
> months ago, clamd on one of our servers has crashed approximately daily.
> It's rarely stayed running for more than 24 hours. 
> 
> Before crashing, the daemon spews the message
> 
>accept() failed:
This is it? Nothing more? There should be an error message included
after the colon.

> The kernel is not reporting segfaults or OOM.

Correct. Based on the source code the `accapt()' function failed and
therefore the daemon terminated.

> On this particular server, clamd is used by clamav-milter. A Nagios
> check script also runs clamdscan about every five minutes against a CAB,
> an EXE, a bzip2'd EXE and a zip file that alll contain
> "Clamav.Test.File-6". As of a Monday (long after the problem starte),
> the script has started scanning another file we've had false-positive
> problems with.

You mean you gave a "normal" file and it was reported as a virus?

Sebastian

Bug#803423: #803423 libqt5gui5: Ugly GUI (no icons) / Weird interpretation of XDG_CURRENT_DESKTOP and GNOME_DESKTOP_SESSION_ID

[Dmitry Shachnev]

Hi Vladimir,

On Fri, May 13, 2016 at 10:20:48PM +0300, Vladimir K wrote:
> Another issue in current Qt theming:
> I have Vivacious-Dark-Graphite icon theme seleced in GTK, it has inheritance 
> sequence:
> Vivacious-Colors-Dark,Vivacious-Colors,ubuntu-mono-dark,gnome,hicolor
>
> GTK applications (like volti mixer) correctly use icons from 
> Vivacious-Color-Dark
> (i.e. 
> /usr/share/icons/Vivacious-Colors-Dark/status/24/audio-volume-medium.png) 
> Qt5 applications (at least qasmixer which is the reason I'm here) seem to 
> skip one and get
> icons from Vivacious-Colors (i.e. 
> /usr/share/icons/Vivacious-Colors/status/24/audio-volume-medium.png)

Better report this upstream to https://bugreports.qt.io.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#824201: tldp: Test suite fails when run as root.

[Gianfranco Costamagna]

Hi Martin, I sponsored the package, but with some differences.
(attaching the Debian directory to this email).

1) the -12 version is already on new queue, so you have to start a new 
changelog entry
on top of that one
2) you need to close this particular bug in that changelog entry
3) you did make a wrong day in the changelog entry, probably a copy-paste, and 
probably you didn't
use dch or date -R to get the correct timestamp.
4) thanks Mattia for being subscribed to unknown packages :)

thanks for the new version!

G.

On Fri, 13 May 2016 17:38:08 + Mattia Rizzolo  wrote:
> On Fri, May 13, 2016 at 10:29:14AM -0700, Martin A. Brown wrote:
> > >BTW, debomatic doesn't run the build as root...
> > 
> > From the downloadable debomatic build log, I saw this:
> > 
> >   User Environment
> >   
> >   
> >   APT_CONFIG=/var/lib/sbuild/apt.conf
> >   HOME=/sbuild-nonexistent
> >   LC_ALL=POSIX
> >   LOGNAME=root
> >   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> >   SCHROOT_ALIAS_NAME=unstable-amd64-debomatic
> >   SCHROOT_CHROOT_NAME=unstable-amd64-debomatic
> >   SCHROOT_COMMAND=env
> >   SCHROOT_GID=0
> >   SCHROOT_GROUP=root
> >   
> > SCHROOT_SESSION_ID=unstable-amd64-debomatic-ec0767d2-2cee-45af-a819-ff581f252f97
> >   SCHROOT_UID=0
> >   SCHROOT_USER=root
> >   SHELL=/bin/sh
> >   USER=root
> >   XDG_RUNTIME_DIR=/run/user/0
> >   XDG_SESSION_ID=c31191
> > 
> > When I ran my test suite as the root user on any ol' box, I was able to
> > reproduce the errors that were showing up in the debomatic build log.  So, I
> > adjusted my test suite and now it succeeds.
> 
> o.O this is totally unexpected.
> Building as root is a so bad thing.
> TBH, my was an assumption, as I've never heard of sbuild running the
> build as root, and so assumed debomatic didn't either.
> 
> Gianfranco: do you know if this is something new or it always did that?
> otherwise I'm going to file a bug for it...
> It's just a plain security hole :|
> 
> > Sorry to be causing you extra work Mattia, but I do appreciate the support
> > from you and Gianfranco.
> 
> meh, don't worry for it :)
> 
> -- 
> regards,
> Mattia Rizzolo
> 
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


tldp_0.7.13-1.debian.tar.xz
Description: application/xz


signature.asc
Description: OpenPGP digital signature

Bug#824215: baloo-kf5: Baloo don`t indexing files with mime type "text/plain" if they hasn`t got extension *.txt

[Denys]

Package: baloo-kf5
Version: 5.16.0-1
Severity: normal
Tags: patch

Dear Maintainer, this bug was fixed in upstream:

https://quickgit.kde.org/?p=baloo.git=commitdiff=467c7ad563b505a9ad7a4f717f479eebd7ba624e

Could you possibly fix it in current sid version if you don`t want to move
baloo packages from experimental to sid soon?



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

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

Versions of packages baloo-kf5 depends on:
ii  libc62.22-7
ii  libkf5baloo5 5.16.0-1
ii  libkf5balooengine5   5.16.0-1
ii  libkf5configcore55.16.0-1
ii  libkf5coreaddons55.16.0-1
ii  libkf5crash5 5.16.0-1
ii  libkf5dbusaddons55.16.0-1
ii  libkf5filemetadata3  5.16.0-1+b1
ii  libkf5i18n5  5.16.0-1
ii  libkf5idletime5  5.16.0-1
ii  libkf5kiocore5   5.16.0-1.1
ii  libkf5solid5 5.16.0-1
ii  libqt5core5a 5.5.1+dfsg-16+b1
ii  libqt5dbus5  5.5.1+dfsg-16+b1
ii  libqt5gui5   5.5.1+dfsg-16+b1
ii  libqt5qml5   5.5.1-3
ii  libqt5widgets5   5.5.1+dfsg-16+b1
ii  libstdc++6   6.1.1-3

baloo-kf5 recommends no packages.

baloo-kf5 suggests no packages.

-- no debconf information

Bug#803423: #803423 libqt5gui5: Ugly GUI (no icons) / Weird interpretation of XDG_CURRENT_DESKTOP and GNOME_DESKTOP_SESSION_ID

[Vladimir K]

Another issue in current Qt theming:
I have Vivacious-Dark-Graphite icon theme seleced in GTK, it has inheritance 
sequence:
Vivacious-Colors-Dark,Vivacious-Colors,ubuntu-mono-dark,gnome,hicolor

GTK applications (like volti mixer) correctly use icons from 
Vivacious-Color-Dark
(i.e. /usr/share/icons/Vivacious-Colors-Dark/status/24/audio-volume-medium.png) 
Qt5 applications (at least qasmixer which is the reason I'm here) seem to skip 
one and get
icons from Vivacious-Colors (i.e. 
/usr/share/icons/Vivacious-Colors/status/24/audio-volume-medium.png)

Bug#824214: ITP: PGObject::Util::DBAdmin - PostgreSQL Database Management Facilities for PGObject

[Robert James Clay]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org

* Package name: libpgobject-util-dbadmin-perl
  Version: 0.08
  Upstream Author : Chris Travers 
* URL or Web page : https://metacpan.org/release/PGObject-Util-DBAdmin
* License   : BSD (3 clause)
  Description : PGObject::Util::DBAdmin -  PostgreSQL Database Management
  Facilities for PGObject

This module provides an interface to basic PostgreSQL Database Facilities for 
PGObject including new, export, connect, server_version, list_dbs, create,
copy_of, run_file, backup, backup_globals, restore, & drop.


Robert James Clay
j...@rocasa.us

Bug#824213: liferea: Dependency Failure - Not Installable

[Stephen]

Package: liferea
Version: 1.10.19-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Cannot install the upgrade in SID for Liferea due to required dependency not 
being available in 
Debian repository:  libpeas-1.0-0-python2loader. Please fix.

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

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

Versions of packages liferea depends on:
ii  dbus-x11 1.10.8-1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  gir1.2-gtk-3.0   3.20.4-1
ii  gir1.2-peas-1.0  1.18.0-2
ii  libatk1.0-0  2.20.0-1
ii  libc62.22-9
ii  libcairo21.14.6-1+b1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libgirepository-1.0-11.48.0-2
ii  libglib2.0-0 2.48.1-1
ii  libgtk-3-0   3.20.4-1
ii  libindicate5 0.6.92-3
ii  libjson-glib-1.0-0   1.2.0-1
ii  libnotify4   0.7.6-2
ii  libpango-1.0-0   1.40.1-1
ii  libpeas-1.0-01.18.0-2
pn  libpeas-1.0-0-python2loader  
ii  libsoup2.4-1 2.54.1-1
ii  libsqlite3-0 3.12.2-1
ii  libwebkitgtk-3.0-0   2.4.11-1
ii  libxml2  2.9.3+dfsg1-1
ii  libxslt1.1   1.1.28-3
ii  liferea-data 1.10.19-1
ii  python-gi3.20.1-1
pn  python:any   

Versions of packages liferea recommends:
ii  gir1.2-gnomekeyring-1.0  3.12.0-1+b1
ii  gnome-icon-theme 3.12.0-1
ii  gnome-keyring3.20.0-1

Versions of packages liferea suggests:
pn  kget 
ii  network-manager  1.2.2-1

-- no debconf information

Bug#822617: Missing symlinks to match locales

[Gunnar Hjalmarsson]

Thank *you*, Mattia! Needless to say I'm the impatient kind of guy. ;)

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

Bug#824212: dovecot-core: mail_access_groups must be set on Debian

[Francois Gouget]

Package: dovecot-core
Version: 1:2.2.23-1
Severity: normal

On Debian the mail inboxes belong to the mail group as per the
SystemGroups policy:
https://wiki.debian.org/SystemGroups

| * mail: Mailboxes in /var/mail are owned by group mail, as explained
|   in policy. The user and group are used for other purposes by
|   various MTA's as well. 

Furthermore their permissions are 0660 which is the only value that
makes sense. So with the default configuration dovecot cannot access
the inboxes and fails with the following error:

May 13 20:23:00 amboise dovecot: imap(fgouget): Error: 
fchown(/home/fgouget/mail/.imap/INBOX, group=8(mail)) failed: Operation not 
permitted (egid=1000(fgouget), group based on /var/mail/fgouget - see 
http://wiki2.dovecot.org/Errors/ChgrpNoPerm)


The fix is to set 'mail_access_groups = mail' in
/etc/dovecot/conf.d/10-mail.conf, which should be the default for the
Debian package.


-- Package-specific info:

dovecot configuration
-
# 2.2.23 (806d709): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.13 (7b14904)
# OS: Linux 4.5.0-1-amd64 x86_64 Debian stretch/sid 
mail_access_groups = mail
mail_location = mbox:~/mail:INBOX=/var/mail/%u
namespace inbox {
  inbox = yes
  location = 
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
}
passdb {
  driver = pam
}
protocols = " imap"
ssl = required
ssl_cert = 
ii  dovecot-imapd 1:2.2.23-1
pn  dovecot-ldap  
pn  dovecot-lmtpd 
pn  dovecot-lucene
pn  dovecot-managesieved  
pn  dovecot-mysql 
pn  dovecot-pgsql 
pn  dovecot-pop3d 
pn  dovecot-sieve 
pn  dovecot-solr  
pn  dovecot-sqlite
ii  ntp   1:4.2.8p7+dfsg-3

Versions of packages dovecot-core is related to:
ii  dovecot-core [dovecot-common]  1:2.2.23-1
pn  dovecot-dbg
pn  dovecot-dev
pn  dovecot-gssapi 
ii  dovecot-imapd  1:2.2.23-1
pn  dovecot-ldap   
pn  dovecot-lmtpd  
pn  dovecot-managesieved   
pn  dovecot-mysql  
pn  dovecot-pgsql  
pn  dovecot-pop3d  
pn  dovecot-sieve  
pn  dovecot-sqlite 

-- no debconf information

Bug#824211: swh-plugins: Package new upstream version

[Javier Serrano Polo]

Package: swh-plugins
Version: 0.4.15+1-8
Severity: wishlist

The upstream project is maintained at https://github.com/swh/ladspa . It
includes a vocoder plug-in that is shipped with the lmms package. To
reuse this plug-in, lmms could put it under /usr/lib/ladspa, but that
would conflict with a new version of swh-plugins. Could you tell if you
will package a new upstream version, which is preferable, or if lmms can
publish this plug-in in the meantime?


smime.p7s
Description: S/MIME cryptographic signature

Bug#786810: ITA: xl2tpd -- layer 2 tunneling protocol implementation

[Vincent Zweije]

On Wed, May 11, 2016 at 10:50:06PM -0400, Roberto C. Sánchez wrote:

||  http://anonscm.debian.org/cgit/users/roberto/xl2tpd.git/

I've cloned it, thanks.

||  As far as the upstream repository goes, upstream previously tried to
||  always merge my Debian packaging into their repository.  Of course, they
||  did it on the master branch (probably owing to the fact that they were
||  probably still on Subversion when they began this practice).  In any
||  event, it caused problems every time I tried to make a new upstream
||  release.  If you look in the debian/ directory if repo I just published,
||  you will see a repack.sh script.  That script removes upstream's debian/
||  directory and a non-free RFC text that they ship in their tarball.

It looks like things have got easier for me:
* Upstream has incorporated the changes you had in quilt patches, removing the
  need for quilt.
* Upstream has removed the RFC text, removing the need for repacking.
* Upstream has modified its debian directory to *almost* work, except that the
  changelog file is bogus.

That last point doesn't matter really, as upstream's debian directory
is discarded by dpkg-source -x anyway. Still, their changes to their
debian directory can be taken over.

Am I correct in concluding that you were importing upstream releases
whenever they came out, and not using git to merge their sources?

I'm considering stopping repacking upstream sources. Is there a concensus
in Debian on whether it is better not to repack and be as close to
upstream as possible, or to repack to get the debian directory out of
there and save some space? Or is it just left up to the maintainer?

Do you have a close contact with upstream, or should I go through the
regular channels? This in connection with forwarding the RC bug upstream.

Vincent.
-- 
Vincent Zweije    | "If you're flamed in a group you
  | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] |-- Paul Tomblin on a.s.r.


signature.asc
Description: PGP signature

Bug#820854: fsm-lite_1.0-1_amd64.changes REJECTED

[Andreas Tille]

On Fri, May 13, 2016 at 07:36:15PM +0200, Thorsten Alteholz wrote:
> Hi Andreas,
> 
> On Fri, 13 May 2016, Andreas Tille wrote:
> >Sorry, but what do you mean?  Isn't "any later version" the "+"?
> 
> please read some more lines of the license text. The first occurence started
> with an "if" and the second one ist just an example.

Fixed and uploaded

Thanks for checking

  Andreas.

-- 
http://fam-tille.de

Bug#824210: grilo-plugins-0.3: SEGV in glib when grilo-plugins is enabled

[Diane Trout]

Package: grilo-plugins-0.3
Version: 0.3.1-1
Severity: important

Dear Maintainer,

Rhythmbox in unstable under wayland crashes either a few moments after its
loaded if grilo-plugins are enabled, or immediately upon enabling grilo if it
was disabled on startup.

I have coredumps in a different part of grilo-tracker from grilo-plugins-0.3.0,
but after updating to grilo-plugins-0.3.1 I still had a SEGV, but the backtrace
seemed to be in a different place.

Diane Trout



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

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

Versions of packages grilo-plugins-0.3 depends on:
ii  libarchive13 3.1.2-11+b1
ii  libavahi-client3 0.6.32~rc+dfsg-1
ii  libavahi-common3 0.6.32~rc+dfsg-1
ii  libavahi-glib1   0.6.32~rc+dfsg-1
ii  libavahi-gobject00.6.32~rc+dfsg-1
ii  libc62.22-7
ii  libdmapsharing-3.0-2 2.9.34-1
ii  libgdata22   0.17.4-1
ii  libglib2.0-0 2.48.1-1
ii  libgmime-2.6-0   2.6.20-1+b1
ii  libgoa-1.0-0b3.20.1-1
ii  libgom-1.0-0 0.3.2-1
ii  libgrilo-0.3-0   0.3.0-1.1
ii  libgstreamer1.0-01.8.1-1
ii  libjson-glib-1.0-0   1.2.0-1
ii  liblua5.3-0  5.3.1-1
ii  libmediaart-2.0-01.9.0-2
ii  liboauth01.0.1-1
ii  libsoup2.4-1 2.54.1-1
ii  libsqlite3-0 3.12.2-1
ii  libtotem-plparser18  3.10.6-4
ii  libtracker-sparql-1.0-0  1.8.0-2+b1
ii  libxml2  2.9.3+dfsg1-1

Versions of packages grilo-plugins-0.3 recommends:
ii  dleyna-server  0.4.0-1

grilo-plugins-0.3 suggests no packages.

-- no debconf information
#0  g_type_check_instance_is_fundamentally_a (
type_instance=type_instance@entry=0x7fffc75fc0d8, 
fundamental_type=fundamental_type@entry=80)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gtype.c:4033
No locals.
#1  0x7389905b in g_object_get (_object=0x7fffc75fc0d8, 
first_property_name=0x7fffc75fc41d "db")
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gobject.c:2319
_g_boolean_var_ = 
object = 0x7fffc75fc0d8
var_args = 
__func__ = "g_object_get"
#2  0x7fffc75fbdb2 in rb_grilo_source_new ()
   from /usr/lib/rhythmbox/plugins/grilo/libgrilo.so
No symbol table info available.
#3  0x7fffc75f8e73 in ?? () from 
/usr/lib/rhythmbox/plugins/grilo/libgrilo.so
No symbol table info available.
#4  0x73890fa5 in g_closure_invoke (closure=0x1318fa0, 
return_value=return_value@entry=0x0, n_param_values=2, 
param_values=param_values@entry=0x7fffb350, 
invocation_hint=invocation_hint@entry=0x7fffb2d0)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gclosure.c:804
marshal = 
marshal_data = 
in_marshal = 0
real_closure = 0x1318f80
__func__ = "g_closure_invoke"
#5  0x738a2fc1 in signal_emit_unlocked_R (node=node@entry=0xb58440, 
detail=detail@entry=0, instance=instance@entry=0x85f190, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffb350)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gsignal.c:3629
tmp = 
handler = 0x1316100
accumulator = 0x0
emission = {next = 0x7fffbf20, instance = 0x85f190, ihint = 
{signal_id = 511, 
detail = 0, run_type = G_SIGNAL_RUN_FIRST}, state = EMISSION_RUN, 
chain_type = 4}
handler_list = 0x1316100
return_accu = 0x0
accu = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong 
= 0, 
  v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 
0x0}, {
  v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, 
v_uint64 = 0, 
  v_float = 0, v_double = 0, v_pointer = 0x0}}}
signal_id = 511
max_sequential_handler_number = 30638
return_value_altered = 0
#6  0x738abd5c in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffb510)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gsignal.c:3385
instance_and_params = 0x7fffb350
signal_return_type = 
param_values = 0x7fffb368
i = 
n_params = 
__func__ = "g_signal_emit_valist"
#7  0x738ac08f in g_signal_emit (instance=instance@entry=0x85f190, 
signal_id=, detail=detail@entry=0)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./gobject/gsignal.c:3441
var_args = 
#8  0x7fffc73cc22e in grl_registry_register_source 
(registry=registry@entry=0x85f190, 
plugin=plugin@entry=0x132cea0, 

Bug#824208: RFS: node-jsesc/1.0.0-1

[Julien Puydt]

Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package "node-jsesc"

 * Package name: node-jsesc
   Version : 1.0.0-1
   Upstream Author : Mathias Bynens
 * URL : http://mths.be/jsesc
 * License : Expat
   Section : web

  It builds those binary packages:

node-jsesc - Escape JavaScript strings, with short output (Node.js 
module)


  To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/node-jsesc


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/n/node-jsesc/node-jsesc_1.0.0-1.dsc


  Changes since the last upload:
node-jsesc (1.0.0-1) unstable; urgency=medium

  * New upstream version.
  * Bump standards-version up.
  * Use https for Vcs-* fields.

Thanks,

Snark on #debian-js

Bug#824209: RFS: path.py/8.2.1+dfsg-1

[Julien Puydt]

Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package "path.py"

 * Package name: path.py
   Version : 8.2.1+dfsg-1
   Upstream Author : Mikhail Gusarov
 * URL : https://github.com/jaraco/path.py
 * License : Expat
   Section : python

  It builds those binary packages:

python-path - module wrapper for os.path for Python 2
 python3-path - module wrapper for os.path for Python 3

  To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/path.py


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/path.py/path.py_8.2.1+dfsg-1.dsc


  Changes since the last upload:
path.py (8.2.1+dfsg-1) unstable; urgency=medium

  [ Ondřej Nový ]
  * Fixed VCS URL (https)

  [ Julien Puydt ]
  * New upstream release.
  * Bump standards-version.

Thanks,

Snark on #debian-python

Bug#824207: ghostscript: Segmentation fault when printing in color mode

[Andreas Messer]

Package: ghostscript
Version: 9.06~dfsg-2+deb8u1
Severity: normal

Dear Maintainer,

when trying to make a print using colors from any application (gimp, 
inkscape...)
no printing happens. Ghostscript segfaults due to mutex issue in glibc. The 
problem is related to an already fixed bug in ghostscript's recursive mutex 
handling:

http://bugs.ghostscript.com/show_bug.cgi?id=695862

The problem only occurs on Intel Skylake based machines supporting TSX memory 
like 
XEON cpus. (Supporting hardware accelerated mutexes) These mutexes are 
sensitive 
to wrong usage, e.g. double unlocking which actually happens in ghostscript due 
to the buggy implementation

Here is a backtrace:

Core was generated by `/usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH 
-dNOINTERPOLATE -sDEVICE='.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fc4823de140 in __lll_unlock_elision () from 
/lib/x86_64-linux-gnu/libpthread.so.0
(gdb) bt
#0  0x7fc4823de140 in __lll_unlock_elision () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7fc48506c409 in gp_monitor_leave (mona=0x1fbece8) at 
./base/gp_psync.c:197
#2  0x7fc48502571a in gsicc_get_link_profile (pis=, 
dev=, 
gs_input_profile=0x1fe2600, gs_output_profile=0x1fe2600, 
rendering_params=0x7ffe6ab60850, 
memory=, devicegraytok=1) at ./base/gsicc_cache.c:797
#3  0x7fc485025b8b in gsicc_get_link (pis=0x1e485d8, dev_in=0x20e1c58, 
pcs_in=0x1fbece8, 
pcs_in@entry=0x20f3860, output_colorspace=0x1, 
rendering_params=0x7ffe6ab60850, memory=0x0)
at ./base/gsicc_cache.c:537
#4  0x7fc485020cf9 in gx_remap_ICC (pcc=0x20f2f30, pcs=0x20f3860, 
pdc=0x20f32e8, pis=0x1e485d8, 
dev=0x20e1c58, select=gs_color_select_texture) at ./base/gsicc.c:353
#5  0x7fc4851a1d4c in gx_remap_color (pgs=0x1e485d8) at ./base/gxcmap.c:558
#6  0x7fc48518efb8 in do_stroke (pgs=0x1e485d8) at ./base/gspaint.c:402
#7  gs_stroke (pgs=0x1e485d8) at ./base/gspaint.c:495
#8  0x7fc484f89b0a in interp (pi_ctx_p=0x1e4d518, pref=0x1e64730, 
perror_object=0x1fbece8, 
perror_object@entry=0x7ffe6ab61420) at ./psi/interp.c:1287
#9  0x7fc484f8a84b in gs_call_interp (perror_object=0x7ffe6ab61420, 
pexit_code=0x7ffe6ab6141c, 
user_errors=1, pref=0x7ffe6ab612a0, pi_ctx_p=) at 
./psi/interp.c:501
#10 gs_interpret (pi_ctx_p=, pref=pref@entry=0x7ffe6ab613e0, 
user_errors=1, 
pexit_code=0x7ffe6ab6141c, perror_object=0x7ffe6ab61420) at 
./psi/interp.c:459
#11 0x7fc484f7fcf8 in gs_main_interpret (perror_object=, 
pexit_code=, 
user_errors=, pref=0x7ffe6ab613e0, minst=) at 
./psi/imain.c:241
#12 gs_main_run_string_end (minst=, user_errors=, 
pexit_code=, 
perror_object=) at ./psi/imain.c:607
#13 0x7fc484f81169 in run_string (minst=minst@entry=0x1e21770, 
str=str@entry=0x7fc4852036a0 ".runstdin", 
options=options@entry=2) at ./psi/imainarg.c:834
#14 0x7fc484f8181e in swproc (minst=minst@entry=0x1e21770, 
arg=0x7ffe6ab62c80 "", 
arg@entry=0x7ffe6ab62c7e "-_", pal=pal@entry=0x7ffe6ab61be0) at 
./psi/imainarg.c:293
#15 0x7fc484f82770 in gs_main_init_with_args (minst=0x1e21770, 
argc=argc@entry=22, 
argv=argv@entry=0x7ffe6ab62708) at ./psi/imainarg.c:211
#16 0x7fc484f8363b in gsapi_init_with_args (lib=, 
argc=argc@entry=22, 
argv=argv@entry=0x7ffe6ab62708) at ./psi/iapi.c:174
#17 0x00400a0f in main (argc=22, argv=0x7ffe6ab62708) at 
./psi/dxmainc.c:86

Updating to ghostscript package from stretch fixes the issue for me.

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

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

Versions of packages ghostscript depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  gsfonts1:8.11+urwcyr1.0.7~pre44-4.2
ii  libc6  2.21-9
ii  libgs9 9.06~dfsg-2+deb8u1

ghostscript recommends no packages.

Versions of packages ghostscript suggests:
ii  ghostscript-x  9.06~dfsg-2+deb8u1

-- no debconf information

Bug#822493: letsencrypt.sh: config file refers to nonexisting documentation

[Cord Beermann]

Package: letsencrypt.sh
Version: 0.1.0-2
Followup-For: Bug #822493

Hello,

I'd also prefer some more information how this package works. 

The file could also contain information how to migrate from letsencrypt (the
python-based package) to letsencrypt.sh, which is the problem i'm
looking into now.

It should contain information how the conf.d directory has to be used (as far
as i see files have to be *.sh?) and what format they should have.

Cord

PS: It would also be nice if you add a cronjob to the package for refreshing
the configured certificates.

Bug#824206: dmidecode: Fix decoding of SMBIOS 3.0 tables (LP: #1578022)

[Colin Ian King]

Package: dmidecode
Version: 3.0-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

The current dmidecode requires some upstream fixes to enable it
do decode SMBIOS 3.0 tables that are now appearing on the market.

This fix has been tested and fixes a SMBIOS 3.0 decode issue, and
I believe it is useful for Debian to pick up the changes that
I've applied to dmidecode in Ubuntu.

*** /tmp/tmpnZdydp/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

  * Fix decoding of SMBIOS 3.0 tables (LP: #1578022)
- Pull in upstream fixes to allow dmidecode to decode
  SMBIOS 3.0 tables, 4 upstream fixes:
  + Fix 'No SMBIOS nor DMI entry point found' on SMBIOS3
  + Let read_file return the actual data size of the entry point
  + Use read_file() to read the DMI table from sysfs
  + Use DWORD for Structure table maximum size in SMBIOS3


Thanks for considering the patch.

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

Kernel: Linux 4.4.0-22-generic (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru dmidecode-3.0/debian/patches/0001-dmidecode-Use-read_file-to-read-the-DMI-table-from-s.patch dmidecode-3.0/debian/patches/0001-dmidecode-Use-read_file-to-read-the-DMI-table-from-s.patch
--- dmidecode-3.0/debian/patches/0001-dmidecode-Use-read_file-to-read-the-DMI-table-from-s.patch	2016-05-13 13:32:16.0 +0100
+++ dmidecode-3.0/debian/patches/0001-dmidecode-Use-read_file-to-read-the-DMI-table-from-s.patch	1970-01-01 01:00:00.0 +0100
@@ -1,82 +0,0 @@
-From 364055211b1956539c6a6268e111e244e1292c8c Mon Sep 17 00:00:00 2001
-From: Jean Delvare 
-Date: Mon, 2 Nov 2015 09:45:31 +0100
-Subject: [PATCH] dmidecode: Use read_file() to read the DMI table from sysfs
-
-We shouldn't use mem_chunk() to read the DMI table from sysfs. This
-will fail for SMBIOS v3 implementations which specify a maximum length
-for the table rather than its exact length. The kernel will trim the
-table to the actual length, so the DMI file will be shorter than the
-length announced in entry point.
-
-read_file() fits the bill in this case, as it deals with end of file
-nicely.
-
-This also helps with corrupted DMI tables, as the kernel will not
-export the part of the table that it wasn't able to parse, effectively
-trimming it.
-
-This fixes bug #46176:
-https://savannah.nongnu.org/bugs/?46176
-Unexpected end of file error

- CHANGELOG   |  3 +++
- dmidecode.c | 29 +
- 2 files changed, 24 insertions(+), 8 deletions(-)
-
-Index: dmidecode-3.0/CHANGELOG
-===
 dmidecode-3.0.orig/CHANGELOG
-+++ dmidecode-3.0/CHANGELOG
-@@ -2,6 +2,9 @@
- 
- 	* dmidecode.c, util.c, util.h: Let read_file return the actual data
- 	  size.
-+	* dmidecode.c: Use read_file to read the DMI table from sysfs.
-+	  This fixes Savannah bug #46176:
-+	  https://savannah.nongnu.org/bugs/?46176
- 
- 2015-10-21  Xie XiuQi  
- 
-Index: dmidecode-3.0/dmidecode.c
-===
 dmidecode-3.0.orig/dmidecode.c
-+++ dmidecode-3.0/dmidecode.c
-@@ -4521,16 +4521,29 @@ static void dmi_table(off_t base, u32 le
- 		printf("\n");
- 	}
- 
--	/*
--	 * When we are reading the DMI table from sysfs, we want to print
--	 * the address of the table (done above), but the offset of the
--	 * data in the file is 0.  When reading from /dev/mem, the offset
--	 * in the file is the address.
--	 */
- 	if (flags & FLAG_NO_FILE_OFFSET)
--		base = 0;
-+	{
-+		/*
-+		 * When reading from sysfs, the file may be shorter than
-+		 * announced. For SMBIOS v3 this is expcted, as we only know
-+		 * the maximum table size, not the actual table size. For older
-+		 * implementations (and for SMBIOS v3 too), this would be the
-+		 * result of the kernel truncating the table on parse error.
-+		 */
-+		size_t size = len;
-+		buf = read_file(, devmem);
-+		if (!(opt.flags & FLAG_QUIET) && num && size != (size_t)len)
-+		{
-+			printf("Wrong DMI structures length: %u bytes "
-+"announced, only %lu bytes available.\n",
-+len, (unsigned long)size);
-+		}
-+		len = size;
-+	}
-+	else
-+		buf = mem_chunk(base, len, devmem);
- 
--	if ((buf = mem_chunk(base, len, devmem)) == NULL)
-+	if (buf == NULL)
- 	{
- 		fprintf(stderr, "Table is unreachable, sorry."
- #ifndef USE_MMAP
diff -Nru dmidecode-3.0/debian/patches/0001-Fix-No-SMBIOS-nor-DMI-entry-point-found-on-SMBIOS3.patch dmidecode-3.0/debian/patches/0001-Fix-No-SMBIOS-nor-DMI-entry-point-found-on-SMBIOS3.patch
--- 

Bug#655889: offer to help with munin packaging

[Holger Levsen]

Hi Dominic!

On Thu, May 12, 2016 at 12:21:55PM +0100, Dominic Hargreaves wrote:
> Not that I have vast amounts of free time, but I do care about
> munin packaging, so I can offer to put a little bit of time into a
> team effort.
 
that would be much welcome! \o/

> What's the current status, thuough? The last update on the rfh bug
> is a few years ago, so I want to know what I'm letting myself in for :)

well, the package is maintained by Stig (ssm) and myself and in the last 1.5
years not much has been done, as we have been waiting for the upstream
3.0 release… (which was said to be immiment for quite some time now :/

Because of this we also didnt bother to send bugs upstream, as most if
not all bugs in the BTS are filed against munin 1.4 or 2.0 and quite
some bugs have been fixed upstream in the 3.0 development phase…

> What are the main tasks/priorities other than bug squashing? Is an
> upload of the current development branch to experimental useful, for
> example?

yes, absolutly. once that is done, I suppose it would also be sensible
to go through the current list of bugs and investigate whether they
still happen with munin 2.999.2.

We (ssm and upstream) hang out on #munin on OFTC, though the same
channel is also available on freenode. (it's mirrored/piped.)

Please do feel very much invited to work in the git repo and also do
uploads, if you feel confident to do so :) Also I believe your work will
have a motivation effect on us :) Also upstream (hi Steve) is reading
the debian BTS too and having more 3.0 testing might convince them to
release 3.0.0 rather sooner than later.

It's starting getting late to have 3.0 in stretch.


-- 
cheers,
Holger


signature.asc
Description: Digital signature