Bug#804523: Patch available

[Edward Betts]

control: tag -1 patch

I sent a github pull request with a fix to upstream.

https://github.com/rakshasa/libtorrent/pull/93

https://github.com/EdwardBetts/libtorrent/commit/8f3f1a794903bcf3ddc755462d0b38106f4b5d1f

-- 
Edward.

Bug#804503: [Pkg-sysvinit-devel] Bug#804503: startpar: Please add Multi-Arch: foreign

[Elrond]

tags 804503 patch
end


Hi,


On Mon, Nov 09, 2015 at 09:13:49 +0100, Petter Reinholdtsen wrote:
> [Elrond]
> > Hi,
> >
> > startpar AFAIK offers an architecture independent (process level)
> > interface to its users. Would you mind setting it to Multi-Arch:
> > foreign?
> 
> Not at all.  Do you have time to provide a tested patch?

Patch is straight forward (attached).

I have build a fresh .deb on an amd64 lxc and installed it
into an i386 lxc and rebooted that. Still seems to work for
me.


Cheers

Elrond
--- debian/control~	2014-04-11 19:14:31.0 +0200
+++ debian/control	2015-11-09 13:00:41.191097992 +0100
@@ -24,6 +24,7 @@
 Suggests: insserv, sysv-rc
 Breaks: sysvinit-utils (<< 2.88dsf-52)
 Replaces: sysvinit-utils (<< 2.88dsf-52)
+Multi-Arch: foreign
 Description: run processes in parallel and multiplex their output
  Used by the sysv-rc boot system executor to run init.d scripts in parallel
  while making sure the script output is not completely messed up.

Bug#804546: piuparts.debian.org: piu-slave-bm-a's stunnel4 process dies (or gets killed) regularly

[Julien Cristau]

Package: piuparts.debian.org
Severity: normal

$ grep -c piu-slave-bm-a.*stunnel4.*CRITICAL.*0.processes 
irclogs/debian/#debian-admin-bots/2015-* 
irclogs/debian/#debian-admin-bots/2015-02.log:0
irclogs/debian/#debian-admin-bots/2015-03.log:0
irclogs/debian/#debian-admin-bots/2015-04.log:0
irclogs/debian/#debian-admin-bots/2015-05.log:0
irclogs/debian/#debian-admin-bots/2015-06.log:0
irclogs/debian/#debian-admin-bots/2015-07.log:0
irclogs/debian/#debian-admin-bots/2015-08.log:20
irclogs/debian/#debian-admin-bots/2015-09.log:8
irclogs/debian/#debian-admin-bots/2015-10.log:75
irclogs/debian/#debian-admin-bots/2015-11.log:25

No idea why it dies like that, but this seems to be the only host where
it happens.

Cheers,
Julien


signature.asc
Description: PGP signature

Bug#804548: python-shade: scm URL is invalid

[Antoine Musso]

Package: python-shade
Version: 0.6.1-1

The python-shade source package has an invalid SCM URL pointing to
Debian subversion:

http://svn.debian.org/wsvn/python-modules/python-shade
svn://svn.debian.org/python-modules/packages/python-shade

That directory does not exist.


It would probably be fine to upload the files to the git repository
under python-modules/packages/python-shade


Seems the documentation to create a new git is:
https://wiki.debian.org/Python/GitPackaging#Creating_new_repositories

Using an alioth account that should be:

$ ssh git.debian.org
$ cd /git/python-modules
$ ./setup-repository python-shade "python-shade packaging"
$ exit

Then amend debian/control to point to the new git URL :-)

-- 
Antoine "hashar" Musso

Bug#538717: Support SVN repositories

[Osamu Aoki]

On Sun, Nov 08, 2015 at 05:16:06PM +0100, Axel Beckert wrote:
> Hi,
> 
> Osamu Aoki wrote:
> > Also, in the upcoming multitar branch, I have implemented pagemangle
> > rule which can do any string substitution of web page. This may be
> > good enough because it allows to change " > upstream only provides subversion tag as the release mechanism.
> 
> Yes, I saw that and think it should suffice for the mentioned case.
> Haven't tried it yet, though.

It is not even merged to main yet.

Anyway, I will mark this fixed in changelog of pagemangle after updating
manpahge.  Thanks.

Osamu

Bug#801413: polarssl: CVE-2015-5291: Remote attack on clients using session tickets or SNI

[James Cowgill]

Hi,

On Tue, 2015-10-27 at 22:29 +0100, Moritz Mühlenhoff wrote:
> On Wed, Oct 21, 2015 at 01:43:26PM +0100, James Cowgill wrote:
> > Hi,
> > 
> > On Tue, 2015-10-20 at 19:37 +0200, Florian Weimer wrote:
> > > * James Cowgill:
> > [...]
> > > > One thing which was suggested was to use 1.3.14 and then disable at
> > > > compile time all the new features which may affect the ABI and then
> > > > revert the SONAME change, but is doing that actually allowed for the
> > > > security archive or will the update be too big?
> > > 
> > > We can do that, but I don't know if it is a good idea to patch
> > > cryptographic software in such extensive ways.
> > > 
> > > We can live with the addition of new symbols, but removal of symbols,
> > > changes in struct sizes or offsets, and so on, would be hugely
> > > problematic.  For are start, you could just build both the old and new
> > > versions and run libabigail on them, to get an idea what actually did
> > > change.
> > 
> > So I checked the ABI and had to revert a few commits. I've attached the
> > original libabigail diff (all against upstream versions) and the diff
> > after my patches. The variables don't look to me like they were ever
> > intended to be part of the public ABI so I don't think they're that
> > important.
> 
> Could you test that the reverse build deps in jessie still build?
> If so, I'd be fine with that approach for jessie.

Sorry it took a little longer than I expected, but here is a patch for
jessie. It can be applied on top of 1.3.14 in experimental.

The patch reverts the library rename in 1.3.14-0.1, applies the
compatability patch, and adds a call to dh_makeshlibs to ensure any
reverse dependencies emit a (>= 1.3.14) dependency since a small number
of symbols have been added in 1.3.14.

All the reverse dependencies build in jessie chroots except for
mongrel2 which FTBFS for unrelated reasons (see #804331 and #804385).

> For wheezy we can probably only make it end-of-life? There's
> only two reverse deps (pdns and gatling).

Upstream have bumped the SONAME of 1.2 as well do doing the same here
for wheezy could be a lot of work.

For this particular bug the fix seems to be a lot simpler though:
https://github.com/ARMmbed/mbedtls/commit/13ca8951f96f00750c9fda9928a9affcddcd342c

I also notice the above commit has been applied to squeeze-lts already.

Thanks,
Jamesdiff --git a/debian/changelog b/debian/changelog
index 4f62031..2bbcad4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-polarssl (1.3.14-0.1) experimental; urgency=high
+polarssl (1.3.14-0.1~deb8u1) jessie-security; urgency=high
 
   * Non-maintainer upload.
   * New upstream release. (Closes: #787324)
@@ -10,10 +10,12 @@ polarssl (1.3.14-0.1) experimental; urgency=high
 - Fixes mips64el bignum implementation. (Closes: #773306)
 - Fixes parsing of certain PCKS#3 files. (Closes: #781840)
 
-  * Rename libpolarssl7 package to libmbedtls9 due to SONAME bump.
+  * Patch added to maintain ABI compatibility with libpolarssl7 in jessie.
   * Drop CVE-2015-1182.patch - applied upstream.
+  * Ensure reverse dependencies emit a (>= 1.3.14) dependency due to new
+symbols introduced in 1.3.14.
 
- -- James Cowgill   Fri, 23 Oct 2015 21:49:24 +0100
+ -- James Cowgill   Mon, 09 Nov 2015 14:14:26 +
 
 polarssl (1.3.9-2.1) unstable; urgency=high
 
diff --git a/debian/control b/debian/control
index 4507611..b96a728 100644
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,7 @@ Homepage: http://polarssl.org
 Package: libpolarssl-dev
 Architecture: any
 Section: libdevel
-Depends: libc6-dev, ${misc:Depends}, libmbedtls9 (= ${binary:Version})
+Depends: libc6-dev, ${misc:Depends}, libpolarssl7 (= ${binary:Version})
 Description: lightweight crypto and SSL/TLS library
  PolarSSL is a lean open source crypto library for providing SSL and TLS
  support in your programs. It offers an intuitive API and documented header
@@ -46,7 +46,7 @@ Description: lightweight crypto and SSL/TLS library
  .
  This package contains the runtime executables.
 
-Package: libmbedtls9
+Package: libpolarssl7
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
diff --git a/debian/libmbedtls9.lintian-overrides b/debian/libmbedtls9.lintian-overrides
deleted file mode 100644
index ce2276d..000
--- a/debian/libmbedtls9.lintian-overrides
+++ /dev/null
@@ -1,3 +0,0 @@
-# For compatability and to avoid conflicting with the libmbedtls-dev
-# package, the shlib symlink is called 'libpolarssl.so'
-libmbedtls9 binary: dev-pkg-without-shlib-symlink usr/lib/libmbedtls.so.9 usr/lib/libmbedtls.so
diff --git a/debian/libpolarssl-dev.links b/debian/libpolarssl-dev.links
index 1aacf15..3225358 100644
--- a/debian/libpolarssl-dev.links
+++ b/debian/libpolarssl-dev.links
@@ -1 +1 @@
-usr/lib/libmbedtls.so.9 usr/lib/libpolarssl.so
+usr/lib/libpolarssl.so.7 usr/lib/libpolarssl.so
diff --git a/debian/libmbedtls9.install 

Bug#804239: marked as pending

[Osamu Aoki]

Hi,

On Mon, Nov 09, 2015 at 10:47:38AM +, Robie Basak wrote:
> Hi Osamu,
> 
> Thank you for the quick update. Did you intend to commit this to the
> "multitar" branch?

It was commited to the multitar branch.

You mean that I merge multitar to main.  Yes, I am asking if that is OK.

> I have managed to get uscan to work with your recent commits. Thank you!

Good.  Please check if there is any sytrange thing.  Also. please read
the new improved manpage.

> For the record, this is what works for me:

If I were you, I do the following with multitar

I did not understand why /?\? part in gpg\/?\?file of downloadurlmangle
Also why not bump to version 4

So not-tested but I think following is what you want

version=4
opts="downloadurlmangle=s/\/downloads\/gpg\/\?file=(mysql-([\d\.]*).tar.gz)/\/get\/Downloads\/MySQL-5.6\/$1/,\
  
pgpsigurlmangle=s/\/get\/Downloads\/MySQL-5.6\/(mysql-([\d\.]*).tar.gz)/\/downloads\/gpg\/?file=$1/,\
  
filenamemangle=s/\/downloads\/gpg\/?\?file=mysql\-([\d\.]*)\.tar\.gz/mysql-$1.tar.gz/"
 \
  http://dev.mysql.com/downloads/mysql/5.6.html?os=src \
  /downloads/gpg/\?file=mysql-([\d\.]*).tar.gz

Or use non-/ to make it more readable

version=4
opts="downloadurlmangle=s&/downloads/gpg/\?file=(mysql-([\d\.]*).tar.gz)&/get/Downloads/MySQL-5.6/$1&,\
  
pgpsigurlmangle=s&/get/Downloads/MySQL-5.6/(mysql-([\d\.]*).tar.gz)&/downloads/gpg/?file=$1&,\
  
filenamemangle=s&/downloads/gpg/?\?file=mysql\-([\d\.]*)\.tar\.gz$1.tar.gz&"
 \
  http://dev.mysql.com/downloads/mysql/5.6.html?os=src \
  /downloads/gpg/\?file=mysql-([\d\.]*).tar.gz

Interesting dancing using sig file and downloadurlmangle etc.

Osamu

Bug#799369: swift update for jessie

[Thomas Goirand]

On 11/09/2015 09:34 AM, Adam D. Barratt wrote:
> On 2015-11-09 8:20, Thomas Goirand wrote:
>> This patch has been prepared a long time ago. I've been waiting for the
>> release team's approval since the 18th of September. This is more than a
>> month and a half. I'm by the way disappointed to see no reply at all
>> from the release team for so long
> 
> If we're in a grumbling and disappointed mood

Please don't take it this way. I've also wrote that I was comprehensive
since the release team has so much work.

> #750010 has been waiting
> for you to reply since September *last year*.

I opened this one on 31 May 2014, and only got a reply on 20 Sep 2014,
then I focused on the newer release of Debian rather than the older.
Sorry, I should have write about it in the bug report.

> #719632 also has questions
> to you from Moritz dated December 2013 that don't appear to have ever
> received a response.

Well, I still had no reply from the release team about this update. I
was hoping to get a first approval, get the update done, then work on
the next step (ie: reply to Moritz and check for the other CVEs).

So those 2 examples are also showing my lack of motivation for doing
these upgrades after a reply from the release team which was quite long.

BTW, we're now way past the support of OpenStack Essex, which for a long
long time, has lost security support from upstream. Even OpenStack
Icehouse, currently in Jessie, has no support upstream, and I have to do
security fix backports by myself. Doing them for a package which is 2
years older (so, 6 releases before what's currently supported) is too
hard. So I'm not working on this old version of the package anymore, but
only on what is currently in Jessie and Sid. I hope you understand why.

At this point, therefore, it is my view that #750010 and #719632 should
be closed without further action, unless someone steps in to do the work.

It is my view that all of this is very frustrating from all sides. :(

Let's all of us try to make things better. Could you approve or reject
this update for Swift?

Cheers,

Thomas Goirand (zigo)

Bug#804543: rkhunter: unhide.rb moved to new pathname, and the whitelist entry should be adapted

[Eriberto]

Thanks for your message Christoph.

I am adding Francois in Cc.

I suggested (as sponsor) to Giovani to move the unhide.rb from
/usr/bin to /usr/sbin, because to get a full reply from the OS, you
need some privileges. Other fact is the upstream manpage is level 8,
signaling this situation. Also, the unhide (other package) is at
/usr/sbin.

Francois, can you update the SCRIPTWHITELIST entry? Do you agree with my POV?

Thanks guys!

Cheers,

Eriberto




2015-11-09 11:30 GMT-02:00 Christoph Anton Mitterer :
> Package: rkhunter
> Version: 1.4.2-4
> Severity: normal
>
>
> Hi.
>
> Apparently unhide.rb moved from /usr/bin to /usr/sbin, even though
> its changelog doesn't tell this (CCing Giovani therefore, so he
> can tell whether this is permanent or just by accident).
>
> Therefore rkhunter's previous SCRIPTWHITELIST entry won't work
> anymore and should be adapted.
>
>
> Cheers,
> Chris.
>
> ___
> forensics-devel mailing list
> forensics-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#804561: GCC can't compile a program using RDSEED intrinsics

[Jeffrey Walton]

Package: g++
Version: 4:5.2.1-4
Severity: normal
Control: tags jessie sid
Tags: jessie sid

**

Another Debian specific bug... GCC can't compile a program using
RDSEED intrinsics. It results in an error "error: ‘_rdseed64_step’ was
not declared in this scope".

According the Intel (which the GCC told me to follow), RDSEED
intrinsics are available in . Confer,
http://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=rdseed.

The same program, using RDRAND, compiles fine.

**

$ cat rdseed.cxx
#include 
#include 

int main()
{
  unsigned long long val = 0;
  _rdseed64_step();
  _rdseed32_step();
  _rdseed16_step();

  std::cout << val << std::endl;

  return !val;
}

$ g++ -mrdseed rdseed.cxx -o rdseed.exe
rdseed.cxx: In function ‘int main()’:
rdseed.cxx:7:22: error: ‘_rdseed64_step’ was not declared in this scope
   _rdseed64_step();
  ^
rdseed.cxx:8:22: error: ‘_rdseed32_step’ was not declared in this scope
   _rdseed32_step();
  ^
rdseed.cxx:9:22: error: ‘_rdseed16_step’ was not declared in this scope
   _rdseed16_step();
  ^

**

$ g++ --version
g++ (Debian 5.2.1-20) 5.2.1 20151002

$ uname -a
Linux debian-8-x64 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u5
(2015-10-09) x86_64 GNU/Linux


**

$ apt-cache show g++
Package: g++
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 17
Maintainer: Debian GCC Maintainers 
Architecture: amd64
Source: gcc-defaults (1.145)
Version: 4:5.2.1-4
Provides: c++-compiler
Depends: cpp (>= 4:5.2.1-4), gcc (>= 4:5.2.1-4), g++-5 (>= 5.2.1-13~),
gcc-5 (>= 5.2.1-13~)
Suggests: g++-multilib
Description-en: GNU C++ compiler
 This is the GNU C++ compiler, a fairly portable optimizing compiler for C++.
 .
 This is a dependency package providing the default GNU C++ compiler.
Description-md5: 4d44b18774ae5123b7c3f70d940cf655

Package: g++
Source: gcc-defaults (1.136)
Version: 4:4.9.2-2
Installed-Size: 34
Maintainer: Debian GCC Maintainers 
Architecture: amd64
Provides: c++-compiler
Depends: cpp (>= 4:4.9.2-2), gcc (>= 4:4.9.2-2), g++-4.9 (>=
4.6.4-1~), gcc-4.9 (>= 4.6.4-1~)
Suggests: g++-multilib
Description-en: GNU C++ compiler
 This is the GNU C++ compiler, a fairly portable optimizing compiler for C++.
 .
 This is a dependency package providing the default GNU C++ compiler.
Description-md5: 4d44b18774ae5123b7c3f70d940cf655
Build-Essential: yes
Tag: devel::compiler, devel::lang:c++, implemented-in::c,
 interface::commandline, role::dummy, role::metapackage, suite::gnu,
 works-with::software:source
Section: devel
Priority: optional
Filename: pool/main/g/gcc-defaults/g++_4.9.2-2_amd64.deb
Size: 1530
MD5sum: cd4aa68ba8cf582df806c324988e6a00
SHA1: 82a50c84e1105e1f0c767da82c09f2398ac2d4b2
SHA256: 6fb9842c6a0ad0cd5445b9f2f2cb3f738abcc83a6b8e0900aad441574f5cecee

Bug#804412: libwebkit2gtk-4.0-37: Please avoid dependency on GTK+ 2

[Alberto Garcia]

On Sun, Nov 08, 2015 at 11:35:47AM +0300, Dmitry Shachnev wrote:

> I currently cannot remove GTK+ 2 from my system because of the following
> dependency chain:
> 
>   mutter → zenity → libwebkit2gtk-4.0-37 → libgtk2.0-0
> 
> I see that libwebkit2gtk-4.0-37 ships a binary named
> WebKitPluginProcess2, which which is linked against
> libgtk-x11-2.0.so.

That file is necessary in order to load plugins that depend on GTK+
2, for example the Adobe Flash Player or the Google Talk / Hangouts
plugin.

But it's true that the GTK+2 dependency is otherwise not essential, so
I think we can remove it.

Thanks for the report,

Berto

Bug#804543: rkhunter: unhide.rb moved to new pathname, and the whitelist entry should be adapted

[Christoph Anton Mitterer]

Package: rkhunter
Version: 1.4.2-4
Severity: normal


Hi.

Apparently unhide.rb moved from /usr/bin to /usr/sbin, even though
its changelog doesn't tell this (CCing Giovani therefore, so he
can tell whether this is permanent or just by accident).

Therefore rkhunter's previous SCRIPTWHITELIST entry won't work
anymore and should be adapted.


Cheers,
Chris.

Bug#738628: Reproduced on Gentoo

[Benda Xu]

The failing point is exim4.orig provides exim4, in the deptree, exim4 is
essentially overridden by exim4.orig.  But runlevel refers the file
"exim4".  Such inconsistency is the cause.

In Gentoo, a package rarely provides something.  So the bug is not so
severe there.

Example:

# rc-status
Runlevel: default
 sshd [  started  ]
 tincd [  started  ]
 local [  started  ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed
Dynamic Runlevel: manual

cp /tmp/local.orig /etc/init.d; head -11 /etc/init.d/local.orig

> #!/sbin/openrc-run
> # Copyright (c) 2007-2008 Roy Marples 
> # Released under the 2-clause BSD license.

> description="Executes user programs in /etc/local.d"

> depend()
> {
> after *
> keyword -timeout
> provide local
  ~

provide is crucial here.

# rc-status
 * Caching service dependencies ... [ ok ]
Runlevel: default
 sshd [  started  ]
 tincd [  started  ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed
Dynamic Runlevel: manual

Bug#804552: API reference mostly empty

[Yuri D'Elia]

Package: python-pandas-doc
Version: 0.17.0+git8-gcac4ad2-2
Severity: normal

The "API reference" (/usr/share/doc/python-pandas-doc/html/api.html) in the
current package is mostly empty. For example, "General functions" contains no
links at all except for section titles.

Looks like there's some problem while generating the documentation.

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

Kernel: Linux 4.2.0-1-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 python-pandas-doc depends on:
ii  libjs-jquery  1.11.3+dfsg-4

python-pandas-doc recommends no packages.

Versions of packages python-pandas-doc suggests:
ii  python-pandas  0.17.0+git8-gcac4ad2-2

Bug#804542: Use apt-ftparchive instead of dpkg-scansources

[Joachim Breitner]

Package: local-apt-repository
Version: 0.3
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi myself,

Felipe Sateler writes in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796549#43
how to use ftp-aptarchive here, which is supposedly better. I should
look into this the next time I work on the code.

Thanks Felipe,
Joachim

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.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 local-apt-repository depends on:
ii  dpkg-dev 1.18.3
ii  init-system-helpers  1.24
ii  systemd  227-2

local-apt-repository recommends no packages.

local-apt-repository suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlZAnzIACgkQ9ijrk0dDIGweKwCfeaGVGaf96vsN8hrDuMqXUR62
5sYAnRHw2Zfa4KKDCrvqRI/xVcd77WZa
=Orml
-END PGP SIGNATURE-

Bug#790120: praat: sound playback delay, random freeze after about 10-20 playbacks

[Rafael Laboissiere]

Control: tags -1 moreinfo

Hi Jakob,

Could you please check whether the bug persists in version 6.0.4-2 of the 
package?


Thanks,

Rafael

* Jakob Wiedner  [2015-06-27 14:04]:


Package: praat
Version: 5.4.0-1
Severity: important

Dear Maintainer,

when playing back a sound file (i tried wav and mp3) in the View/Edit window 
there is a considerable delay of several seconds. After 2nd or 3rd time the 
delay disappears and it works fine for several times. Rondomly after 10-20 
times, praat freezes entirely and can just be closed by killing it.


Terminal output as follows:

FIRST PLAYBACK: 
ALSA lib pcm_dsnoop.c:618:(snd_pcm_dsnoop_open) unable to open slave 
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave 
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear 
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe 
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side 
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave 
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred 
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred 
SECOND PLAYBACK: 
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred 
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred


After that no more delays when playback immediately after.



-- System Information: 
Debian Release: 8.1 
 APT prefers stable 
 APT policy: (500, 'stable') 
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: systemd (via /run/systemd/system)

Versions of packages praat depends on: 
ii  libasound2   1.0.28-1 
ii  libatk1.0-0  2.14.0-1 
ii  libc62.19-18 
ii  libcairo21.14.0-2.1 
ii  libfontconfig1   2.11.0-6.3 
ii  libfreetype6 2.5.2-3 
ii  libgcc1  1:4.9.2-10 
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1 
ii  libglib2.0-0 2.42.1-1 
ii  libgtk2.0-0  2.24.25-3 
ii  libpango-1.0-0   1.36.8-3 
ii  libpangocairo-1.0-0  1.36.8-3 
ii  libpangoft2-1.0-01.36.8-3 
ii  libstdc++6   4.9.2-10 
ii  oss-compat   6 
ii  python   2.7.9-1


Versions of packages praat recommends: 
ii  xfonts-100dpi 1:1.0.3 
ii  xfonts-100dpi-transcoded  1:1.0.3 
ii  xfonts-75dpi  1:1.0.3 
ii  xfonts-75dpi-transcoded   1:1.0.3


praat suggests no packages.

-- no debconf information

Bug#804547: [nvidia-driver] Alien: Isolation needs driver version 355.11

[Bogdan Vatra]

Package: nvidia-driver
Version: 340.93-7
Severity: normal

Dear maintainer(s),

Alien: Isolation was released, but sadly it needs nvidia driver version 355.11 
or better which is not available yet on Debian.
I'm using debian's nvidia packages instead of official nvidia one, because it 
just works (you've done and still doing a GREAT job!) and I'd like to keep 
using yours ;-).

So, I humbly request you to update nvidia driver (push it to experimental?).

Thank you!

Yours,
BogDan.

Bug#756090: ITA: irker -- submission tools for IRC notifications

[Antoine Beaupré]

On 2015-11-09 05:25:35, Neil Muller wrote:
> Has anything further happened here?
>
> I'm interested in seeing irker stay in debian, and would be willing to
> help maintain the package.

You're welcome to take over this ITP!

A.
-- 
Si l'image donne l'illusion de savoir
C'est que l'adage pretend que pour croire,
L'important ne serait que de voir
- Lofofora

Bug#740611: [PKG-OpenRC-Debian] Bug#740611: A revised description

[Thomas Goirand]

On 11/07/2015 06:19 AM, Benda Xu wrote:
> Hi Justin,
> 
> Thank you for your input.
> 
> I suggest update the description as
> 
>  OpenRC is a dependency based init system. It provides support for System V
>  init, for booting, changing runlevels, starting and stopping services, and
>  shutting down.
> 
>  Originally written as a Gentoo project, OpenRC aims at being
>  platform-agnostic.  It works equally well on Linux, BSD and Hurd.  It
>  supports the traditional init system in Debian in addition to many
>  alternatives.  OpenRC is implemented in C in a small, simple and
>  efficient way, making it easy to understand, extend and reuse.
> 
> @Thomas, @Roger: Comments?
> 
> Benda

Fine for me.

Thomas

Bug#681884: are there any workarounds for schroot+systemd in jessie?

[Alexandra N. Kossovsky]

Are there any workarounds available for this bug for schroot+systemd in
jessie?  Or the only workaround is "don't use systemd"?

-- 
Alexandra N. Kossovsky
OKTET Labs (http://www.oktetlabs.ru/)

Bug#798213: [Pkg-monitoring-maintainers] Bug#798213: ganglia-web: CVE-2015-6816: auth bypass

[Daniel Pocock]

On 08/11/15 18:11, Salvatore Bonaccorso wrote:
> Hi,
>
> On Sun, Sep 06, 2015 at 10:45:29PM +0200, Salvatore Bonaccorso wrote:
>> Source: ganglia-web
>> Version: 3.6.1-1
>> Severity: important
>> Tags: security patch upstream
>>
>> Hi,
>>
>> the following vulnerability was published for ganglia-web.
>>
>> CVE-2015-6816[0]:
>> ganglia-web auth bypass
>>
>> If you fix the vulnerability please also make sure to include the
>> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>>
>> For further information see:
>>
>> [0] https://security-tracker.debian.org/tracker/CVE-2015-6816
>> [1] https://github.com/ganglia/ganglia-web/issues/267
> *ping*?


I did a review of the latest upstream releases (both ganglia-web and the
ganglia agent) and there are some new JavaScript dependencies that need
to be packaged

https://cdnjs.cloudflare.com/ajax/libs/cubism/1.6.0/cubism.v1.min.js
https://cdnjs.cloudflare.com/ajax/libs/protovis/3.3.1/protovis.min.js
https://cdnjs.cloudflare.com/ajax/libs/jstree/3.2.1/jstree.min.js



Given that we have given users of this package a disclaimer[1] about
security support and advised them to protect the web interface with an
ACL or HTTP authentication, how urgent is resolving this bug?

Regards,

Daniel


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

Bug#775850: timblserver: FTBFS in unstable: error: 'class Timbl::GetOptClass' has no member named 'getLogFile'

[Joost van Baal-Ilić]

Hi Andreas e.a.,

On Mon, Nov 09, 2015 at 01:07:44PM +0100, Andreas Beckmann wrote:
> On Mon, 14 Sep 2015 14:11:40 +0200 Joost van =?utf-8?Q?Baal-Ili=C4=87?=
>  wrote:
> > On Mon, Sep 14, 2015 at 12:21:34PM +0100, Peter Green wrote:
> > > >
> > > >  timblserver (1.8-1) experimental; urgency=low
> > > >  .
> > > >* New upstream release.
> > > >  - Fixes "timblserver: FTBFS in unstable: error: 'class 
> > > > Timbl::GetOptClass'
> > > How come this was uploaded to experimental and not unstable?
> > > 
> > 
> > I'm not quite sure if uploading to unstable wouldn't introduce even more RC
> > bugs.  Don't have the time to find out about that now.  I'll likely be able 
> > to
> > allocate more time to it within about one month.
> 
> Did you find some time to look at this issue?

Nope.  Hrm, I guess I can state: if there hasn't been done done any
substantial work on this by february 1, 2016; feel free to remove this stuff
from the archive.  I expect I'll have been able to allocate some time on this
before that date.

> > btw: you're welcome to nmu if you're convinced that will fix bugs.
> 
> In unstable currently the whole reverse-build-deps set of timblserver is
> unbuildable and uninstallable.

Yes...  :(

Thanks for pinging me.

Bye,

Joost

Bug#804246: transition: gsl

[Dirk Eddelbuettel]

On 9 November 2015 at 10:02, Andreas Beckmann wrote:
| On Sun, 8 Nov 2015 19:38:36 -0600 Dirk Eddelbuettel  wrote:
| > 
| > On 9 November 2015 at 01:12, Emilio Pozuelo Monfort wrote:
| > | > edd@max:~$ bts block 802246 by 804495 804496 804497 804498 804499 
804500 804501 804502
| > | > edd@max:~$ 
| > | > 
| > | > Thanks *so much* for your very timely and very lucid help. Much 
appreciated.
| > | 
| > | It doesn't look like that worked. Maybe you don't have a MTA configured. 
Adding
| > | the blocks now.
| > 
| > Hmpf.
| > 
| > Shouldn't bts talk to the default MTA on my box?  Works for all other 
apps...
| 
| It worked fine, just went to the wrong bug :-) (a closed one in my packages)

Of course.  Now I see the command-line.

Correctly copying six digits is apparently above my cognitive threshold. :-/

Dirk

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

Bug#570623: reprepro: please add multiple version management

[David Kleuker]

we would really like to have this. any updates?

Bug#804550: python-shade: should honor DEB_BUILD_OPTIONS=nocheck

[Antoine Musso]

Package: python-shade
Version: 0.6.1-1

debian/control should honor DEB_BUILD_OPTIONS=nocheck so we can skip
running the tests when building the package.


It should be all about using:

  override_dh_auto_test:
+ ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
python setup.py testr --slowest
+ endif



-- 
Antoine "hashar" Musso

Bug#760849: transition: glew

[Matteo F. Vescovi]

Hi again!

I need to follow-up to my previous mail, adding the following info:

On Mon, Nov 9, 2015 at 10:17 AM, Matteo F. Vescovi  wrote:
> [...]
>  * libreoffice_1:5.0.3~rc1-2 => CHECK <= this can be set to OK
> [...]
>  * tulip_4.7.0dfsg-2 => FTBFS <= it's a FTBFS (no glew-related)
> [...]

Cheers.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A

Bug#785052: Uploading 8.2 to experimental?

[Marco d'Itri]

On Nov 09, David Prévot  wrote:

> Any hint to deal with encryption would be welcome, I might upload to
> experimental if I go the path of failing install if encryption is enable
> in preinst unless there is a better solution (and I hope there is…).
Upload it straight to unstable with this check, since you can implement 
it easily and it will allow people to use the package.
If a more complex solution will prove to be needed and it will be 
possible to implement it then you can always add it later.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#804554: fonts-hack-otf: new upstream release 2.018

[Fabian Greffrath]

Package: fonts-hack-otf
Version: 2.015-1
Severity: wishlist

Hi there,

a new upstream version of the Hack font has been released.
Please consider packaging this one.

Thanks,

 - Fabian


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

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

-- no debconf information

Bug#804555: lxctl: typos in manpage

[Christian T. Steigies]

Subject: lxctl: typos in manpage
Package: lxctl
Version: 0.3.1+debian-3
Severity: minor

Dear Maintainer,
lxctl --help and the manpage have a few typos (some are corrected in the
manpage but not in the lxctl script):

--- lxctl--help.orig2015-11-09 14:55:58.654233218 +0100
+++ l   2015-11-09 14:56:32.756511148 +0100
@@ -4,7 +4,7 @@
 See lxctl --man or lxctl --help for more info
 
 Options:
---help  Print a breif help message and exists
+--help  Print a brief help message and exits
 
 --man   Prints the manual page and exits.
 
@@ -52,7 +52,7 @@
 
 --searchdomain - set a custom searchdomain in 
/etc/resolv.conf
 
---macaddr - set the custom mac adress of the container
+--macaddr - set the custom mac address of the container
 
 --autostart - autostart container each reboot host machine
 
@@ -76,7 +76,7 @@
 
 --rootsz - increment of size of logical volume for root FS
 
---ipaddr - IP address if the machine
+--ipaddr - IP address of the machine
 
 --mask/netmask - network mask of the machine
 
@@ -88,11 +88,11 @@
 
 --searchdomain - set a custom searchdomain in 
/etc/resolv.conf
 
---macaddr - set the custom mac adress if the machine
+--macaddr - set the custom mac address of the machine
 
 --userpasswd user:passwd - sets password for given user
 
---onboot {yes,no} - makes containet [do not] start at boot
+--onboot {yes,no} - makes container [do not] start at boot
 
 --tz - set custom timezone (Europe/Moscow, UTC, etc)
 
 
Some descriptions could be improved, for example --empty.

The --man action does not seem to work. It requires root rights to run and
with sudo it returns Unsupported command?

cts@nunzio:~>lxctl --man
Error: you are not root!
Unsupported command!
Usage:
lxctl [action] [vmname] [options]

See lxctl --man or lxctl --help for more info
cts@nunzio:~>sudo lxctl --man
Unsupported command!
Usage:
lxctl [action] [vmname] [options]

See lxctl --man or lxctl --help for more info


Christian

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 lxctl depends on:
ii  libipc-system-simple-perl  1.25-2
ii  liblinux-lvm-perl  0.17-2
ii  libnet-ssh2-perl   0.53-2+b1
ii  libossp-uuid-perl  1.6.2-1.5+b1
ii  libyaml-tiny-perl  1.64-1
ii  lxc1:1.0.6-6+deb8u1

Versions of packages lxctl recommends:
ii  bridge-utils  1.5-9
ii  lvm2  2.02.111-2.2
ii  perl-doc  5.20.2-3+deb8u1

Versions of packages lxctl suggests:
ii  bash-completion  1:2.1-4

-- no debconf information

Bug#804530: [Pkg-haproxy-maintainers] Bug#804530: Bug#804530: haproxy: Ensure stop action works on pre-systemd versions of Debian (and Ubuntu)

[Vincent Bernat]

 ❦  9 novembre 2015 11:51 GMT, James Page  :

> How would you feel about using:
>
> for pid in $(cat $PIDFILE); do
> if start-stop-daemon --help | grep -q "\-\-pid "; then
> start-stop-daemon --quiet --oknodo --stop \
> --retry 5 --pid $pid --exec $HAPROXY || ret=$?
> else
> if kill -0 $pid 2> /dev/null; then
> /bin/kill $pid || ret=4
> fi
> fi
> done
>
> This would preserve use of stop-start-daemon if the version installed
> supported --pid, and drop back to the kill approach if not.

Personally, I find this too hacky and not worth it. For example, if
start-stop-daemon sends its output to stderr (unlikely, but...), this
will break. Or if start-stop-daemon reduces its help message to only a
mention of the manual page.

Apollon, what do you think?
-- 
If one cannot enjoy reading a book over and over again, there is no use
in reading it at all.
-- Oscar Wilde


signature.asc
Description: PGP signature

Bug#804541: lvm2 Build-depends on obsolete package libcorosync-dev

[peter green]

Package: lvm2
Version: 2.02.133-1
Severity: serious
Tags: patch

Your package build-depends on libcorosync-dev which is no longer built 
by the corosync source package.


I replaced the build-depends on libcorosync-dev with 
libcorosync-core-dev and tried a build in a raspbian stretch-staging 
environment. Through build-testing I found I also needed to add 
libquorum-dev, libcmap-dev and libcpg-dev to get a sucessful build.


I have uploaded this to raspbian, a debdiff is available at 
http://debdiffs.raspbian.org/main/l/lvm2/lvm2_2.02.133-1%2brpi1.debdiff 
no intent to NMU in Debian.

Bug#804540: bzr: obsolete conffile /etc/bash_completion.d/bzr

[Jakub Wilk]

Package: bzr
Version: 2.6.0+bzr6606-1
User: debian...@lists.debian.org
Usertags: adequate obsolete-conffile

The package left obsolete conffile after upgrade:
/etc/bash_completion.d/bzr

Please consult http://wiki.debian.org/DpkgConffileHandling for 
instructions on how to remove conffiles properly.




This bug was brought to you by adequate:
https://packages.debian.org/unstable/main/adequate



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

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

Versions of packages bzr depends on:
ii  python-bzrlib  2.6.0+bzr6606-1
pn  python:any 

--
Jakub Wilk

Bug#804530: [Pkg-haproxy-maintainers] Bug#804530: Bug#804530: Bug#804530: haproxy: Ensure stop action works on pre-systemd versions of Debian (and Ubuntu)

[Apollon Oikonomopoulos]

On 15:01 Mon 09 Nov , Apollon Oikonomopoulos wrote:
> If we're going to support this, I would like to avoid parsing program 
> output. We could check the dpkg version (e.g. using dpkg 
> --compare-versions) and fall back to the kill loop if dpkg is older 
> than 1.17.6, or we could keep the loop as is but create a temporary 
> pidfile for each PID and pass the temporary pidfile to 
> start-stop-daemon with `--pidfile` instead of `--pid`. Both approaches 
> sound a bit hackish, but the second is probably less so.

IOW, something along these lines:

diff --git a/debian/haproxy.init b/debian/haproxy.init
index 35af505..2852efa 100644
--- a/debian/haproxy.init
+++ b/debian/haproxy.init
@@ -62,8 +62,10 @@ haproxy_stop()
 
ret=0
for pid in $(cat $PIDFILE); do
+   tmppid="$(mktemp)"
start-stop-daemon --quiet --oknodo --stop \
-   --retry 5 --pid $pid --exec $HAPROXY || ret=$?
+   --retry 5 --pidfile "$tmppid" --exec $HAPROXY || ret=$?
+   rm -f "$tmppid"
done
 
[ $ret -eq 0 ] && rm -f $PIDFILE


Note that s-s-d has a '--remove-pidfile' option, but this is again too new (>= 
1.17.19).

Bug#804530: [Pkg-haproxy-maintainers] Bug#804530: Bug#804530: Bug#804530: haproxy: Ensure stop action works on pre-systemd versions of Debian (and Ubuntu)

[Apollon Oikonomopoulos]

Hi James, Vincent,

On 13:13 Mon 09 Nov , Vincent Bernat wrote:
>  ❦  9 novembre 2015 11:51 GMT, James Page  :
> 
> > How would you feel about using:
> >
> > for pid in $(cat $PIDFILE); do
> > if start-stop-daemon --help | grep -q "\-\-pid "; then
> > start-stop-daemon --quiet --oknodo --stop \
> > --retry 5 --pid $pid --exec $HAPROXY || ret=$?
> > else
> > if kill -0 $pid 2> /dev/null; then
> > /bin/kill $pid || ret=4
> > fi
> > fi
> > done
> >
> > This would preserve use of stop-start-daemon if the version installed
> > supported --pid, and drop back to the kill approach if not.
> 
> Personally, I find this too hacky and not worth it. For example, if
> start-stop-daemon sends its output to stderr (unlikely, but...), this
> will break. Or if start-stop-daemon reduces its help message to only a
> mention of the manual page.
> 
> Apollon, what do you think?

The reason for using start-stop-daemon is two-fold: first of all, it 
reliably matches the PID with the executable and won't kill unrelated 
processes. Second, it waits until the process exits, making the 
initscripts behavior more reliable. IMHO, both reasons are important 
enough to not revert to the kill loop.

If we're going to support this, I would like to avoid parsing program 
output. We could check the dpkg version (e.g. using dpkg 
--compare-versions) and fall back to the kill loop if dpkg is older than 
1.17.6, or we could keep the loop as is but create a temporary pidfile 
for each PID and pass the temporary pidfile to start-stop-daemon with 
`--pidfile` instead of `--pid`. Both approaches sound a bit hackish, but 
the second is probably less so.

Cheers,
Apollon

Bug#804544: please document the --no-dereference option in the man page

[Marvin Renich]

Package: diffutils
Version: 1:3.3-2
Severity: minor

The --no-dereference option is documented in the info docn and in the
--help output, but not in the man page.  Perhaps help2man was not run
recently enough?

Thanks...Marvin


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

Kernel: Linux 4.2.0-1-amd64 (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: sysvinit (via /sbin/init)

Versions of packages diffutils depends on:
ii  libc6  2.19-22

diffutils recommends no packages.

Versions of packages diffutils suggests:
pn  diffutils-doc  
ii  wdiff  1.2.2-1

-- no debconf information

Bug#804545: patch jessie version for use with Chromium

[Daniel Pocock]

Package: libsrtp0
Version: 1.4.5~20130609~dfsg-1.1
Severity: important
Tags: security

As described in #770659, Chromium is having problems with the standard
version of libsrtp0 on jessie.

Chromium upstream uses a bundled and patched version of libsrtp0. 
Chromium packages uploaded to jessie as security updates are not built
with the bundled version from upstream though.

There is a patch[2] for libsrtp0 that could be adapted for a stable update.

Users have been disabling the sandbox in Chromium to work around this
issue, hence the security tag has been used.

1.
http://anonscm.debian.org/cgit/pkg-chromium/pkg-chromium.git/tree/debian/rules#n61
2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770659#124

Bug#642458: libfarstream-0.2-2 continues with this

[Elrond]

reassign 642458 libfarstream-0.2-2 0.2.4-1
reopen 642458
thanks

Bug#804542: Use apt-ftparchive instead of dpkg-scansources

[Felipe Sateler]

On Mon, 09 Nov 2015 14:27:16 +0100 Joachim Breitner  wrote:
> Package: local-apt-repository
> Version: 0.3
> Severity: wishlist
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi myself,
>
> Felipe Sateler writes in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796549#43
> how to use ftp-aptarchive here, which is supposedly better. I should
> look into this the next time I work on the code.

Attaching full patch here for completeness.

Saludos
From d3d993e3fc23510ceddc352ae1ee15f0b7ca8cf4 Mon Sep 17 00:00:00 2001
From: Felipe Sateler 
Date: Mon, 9 Nov 2015 10:37:02 -0300
Subject: [PATCH] Use apt-ftparchive from apt-utils

The generated Release file was not valid. Use apt-ftparchive to
offload the responsibility to apt itself.

Since we are now using apt-ftparchive, also use it to generate
both Packages and Sources.

Drop dependency on dpkg-dev as we no longer use anything from there.

Closes: #804542
---
 debian/control |  2 +-
 rebuild| 16 ++--
 2 files changed, 7 insertions(+), 11 deletions(-)

diff --git a/debian/control b/debian/control
index 4234139..d82e98e 100644
--- a/debian/control
+++ b/debian/control
@@ -14,7 +14,7 @@ Package: local-apt-repository
 Architecture: all
 Depends:
  systemd,
- dpkg-dev,
+ apt-utils,
  ${misc:Depends},
 Description: Ready to use local apt repository
  With this package installed, every Debian package (i.e. a *.deb file) dropped
diff --git a/rebuild b/rebuild
index 9878c47..966a417 100755
--- a/rebuild
+++ b/rebuild
@@ -39,8 +39,8 @@ else
 
   # Relative paths work better than absolute
   (cd $REPO
-  dpkg-scanpackages -m ../../../$DEBS > $REPO/Packages
-  dpkg-scansources ../../../$DEBS > $REPO/Sources
+  apt-ftparchive packages ../../../$DEBS > $REPO/Packages
+  apt-ftparchive sources ../../../$DEBS > $REPO/Sources
   ) || true
   # ^ this can fail during a partial write to the directory (which
   #   would be detected by the loop), so ignore errors here
@@ -51,12 +51,8 @@ else
 
 fi
 
-cat > $REPO/Release <<__END__
-Description: Local repository created by local-apt-repository
-Origin: local-apt-repository
-Components: .
-MD5Sum:
- $(md5sum $REPO/Packages|cut -d\  -f1) $(wc -c $REPO/Packages|cut -d\  -f1) Packages
- $(md5sum $REPO/Sources|cut -d\  -f1) $(wc -c $REPO/Sources|cut -d\  -f1) Sources
-__END__
+apt-ftparchive \
+	-o "APT::FTPArchive::Release::Origin=local-apt-repository" \
+	-o "APT::FTPArchive::Release::Description=Local repository created by local-apt-repository" \
+	release $REPO > $REPO/Release
 
-- 
2.6.2

Bug#804530: [Pkg-haproxy-maintainers] Bug#804530: Bug#804530: Bug#804530: haproxy: Ensure stop action works on pre-systemd versions of Debian (and Ubuntu)

[Vincent Bernat]

 ❦  9 novembre 2015 15:09 +0200, Apollon Oikonomopoulos  :

>> If we're going to support this, I would like to avoid parsing program 
>> output. We could check the dpkg version (e.g. using dpkg 
>> --compare-versions) and fall back to the kill loop if dpkg is older 
>> than 1.17.6, or we could keep the loop as is but create a temporary 
>> pidfile for each PID and pass the temporary pidfile to 
>> start-stop-daemon with `--pidfile` instead of `--pid`. Both approaches 
>> sound a bit hackish, but the second is probably less so.
>
> IOW, something along these lines:
>
> diff --git a/debian/haproxy.init b/debian/haproxy.init
> index 35af505..2852efa 100644
> --- a/debian/haproxy.init
> +++ b/debian/haproxy.init
> @@ -62,8 +62,10 @@ haproxy_stop()
>  
> ret=0
> for pid in $(cat $PIDFILE); do
> +   tmppid="$(mktemp)"
> start-stop-daemon --quiet --oknodo --stop \
> -   --retry 5 --pid $pid --exec $HAPROXY || ret=$?
> +   --retry 5 --pidfile "$tmppid" --exec $HAPROXY || 
> ret=$?
> +   rm -f "$tmppid"
> done
>  
> [ $ret -eq 0 ] && rm -f $PIDFILE
>
>
> Note that s-s-d has a '--remove-pidfile' option, but this is again too
> new (>= 1.17.19).

This one seems good for me too.
-- 
Make your program read from top to bottom.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#804545: patch jessie version for use with Chromium

[Jonas Smedegaard]

Quoting Daniel Pocock (2015-11-09 14:32:51)
> As described in #770659, Chromium is having problems with the standard 
> version of libsrtp0 on jessie.

The problem it has is that it a) rely on libSRTP to provide randomness, 
and b) block the underlying calls done internally in libSRTP to get 
randomness from other sources.

> Users have been disabling the sandbox in Chromium to work around this 
> issue, hence the security tag has been used.

The very use of libSRTP is a security issue: libSRTP does *not* provide 
cryptographically secure randomness, and next major release of libSRTP 
will _stop_ offer that unreliable randomness API.

Therefore I believe the way forward with this is to get Chromium to get 
randomness via some other API than the bad libSRTP approach used now, 
and then when that is in place try backport the proper approach to the 
Chromium in Debian stable.

I do not like to change the libSRTP code in Debian stable.  The patch 
itself is tiny, but just as the very Chromium issue demonstrates, can 
nevertheless have big consequences.


 - Jonas

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

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


signature.asc
Description: signature

Bug#804551: xorg: Killed process 1772 (Xorg)

[Miguel Negrao]

Package: xorg
Version: 1:7.7+12
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

Already 2 or 3 tims it has happened that after resume from suspend on my
laptop, when I login again back into gdm3, xorg gets killed by the kernel due
to lack of memory. I loose any unsaved work and have to reboot system to become
usable again. I have 8GB of memory and no swap. For 2 years using ubuntu, I had
never had issues with lack of memory killing xorg. It might have killed some
other process, but that was fine with me. I understand that lack of swap
causing a process to be killed is expected, what I find unexpected is that xorg
can take 8GB of memory, if indeed that is what is happening, or if it is some
other process using the memory, then xorg shouldn't be sacrified given how
important it is. This makes my system unusable, as I live in fear that xorg,
and everything else, can be killed at any moment...

miguel@miguel-MacBookPro:~$ cat /etc/apt/sources.list
deb http://snapshot.debian.org/archive/debian/20151105T095352Z/ testing non-
free contrib main
deb http://snapshot.debian.org/archive/debian-security/20151104T192310Z/
testing/updates non-free contrib main


Nov 07 11:52:54 miguel-MacBookPro kernel: Killed process 1772 (Xorg) total-
vm:1833300kB, anon-rss:1228904kB, file-rss:106980kB
Nov 07 11:52:54 miguel-MacBookPro kernel: Out of memory: Kill process 1772
(Xorg) score 165 or sacrifice child
Nov 07 11:52:54 miguel-MacBookPro kernel: [ 4699] 7  469920733  226
45   30 0 dbus
Nov 07 11:52:54 miguel-MacBookPro kernel: [ 4691] 0  469124461 1413
52   40 0 cupsd
Nov 07 11:52:54 miguel-MacBookPro kernel: [ 4688]33  4688   102032 2248
124   30 0 apache2
Nov 07 11:52:54 miguel-MacBookPro kernel: [ 4687]33  4687   102032 2248
124   30 0 apache2
Nov 07 11:52:54 miguel-MacBookPro kernel: [ 4686]33  4686   102032 2248
124   30 0 apache2
Nov 07 11:52:54 miguel-MacBookPro kernel: [ 4685]33  4685   102032 2248
124   30 0 apache2
Nov 07 11:52:54 miguel-MacBookPro kernel: [ 4684]33  4684   102032 2248
124   30 0 apache2
Nov 07 11:52:54 miguel-MacBookPro kernel: [29338] 0 29338 3755  270
14   30 0 dhclient
Nov 07 11:52:54 miguel-MacBookPro kernel: [28829]  1000 28829 5874  598
16   30 0 bash
Nov 07 11:52:54 miguel-MacBookPro kernel: [28788] 0 28788 5485  209
15   30 0 bash
Nov 07 11:52:54 miguel-MacBookPro kernel: [28787] 0 2878717929  173
39   30 0 su
Nov 07 11:52:54 miguel-MacBookPro kernel: [28786] 0 2878617507  215
37   30 0 sudo
Nov 07 11:52:54 miguel-MacBookPro kernel: [28752]  1000 28752 5858  580
16   30 0 bash
Nov 07 11:52:54 miguel-MacBookPro kernel: [28051]  1000 28051   12365511432
110   30 0 ghc
Nov 07 11:52:54 miguel-MacBookPro kernel: [28032]  1000 28032 5858  523
16   30 0 bash
Nov 07 11:52:54 miguel-MacBookPro kernel: [24666]  1000 24666  115810934455
284   80 0 java
Nov 07 11:52:54 miguel-MacBookPro kernel: [24587]  1000 24587 3319  124
11   30 0 smartgit.sh
Nov 07 11:52:54 miguel-MacBookPro kernel: [20899]  1000 20899   132256 4532
182   40 0 qjackctl
Nov 07 11:52:54 miguel-MacBookPro kernel: [19436]  1000 19436   792205   137070
531   60 0 sclang
Nov 07 11:52:54 miguel-MacBookPro kernel: [19388]  1000 19388   69318174737
401   60 0 scide
Nov 07 11:52:54 miguel-MacBookPro kernel: [32588]  1000 32588   124219 1493
107   30 0 gvfsd-recent
Nov 07 11:52:54 miguel-MacBookPro kernel: [32436]  1000 32436   182550 9279
270   90 0 plugin-containe
Nov 07 11:52:54 miguel-MacBookPro kernel: [29157]  1000 29157   627107   182356
1038   60 0 iceweasel
Nov 07 11:52:54 miguel-MacBookPro kernel: [10804] 0 1080417301  331
38   30 0 gconfd-2
Nov 07 11:52:54 miguel-MacBookPro kernel: [24012]  1000 24012   367285   109358
294   40 0 tracker-miner-f
Nov 07 11:52:54 miguel-MacBookPro kernel: [14825]  1000 14825   12675212633
163   50 0 tomboy
Nov 07 11:52:54 miguel-MacBookPro kernel: [13754]  1000 13754   120054 2454
78   30 0 jackdbus
Nov 07 11:52:54 miguel-MacBookPro kernel: [ 7725] 0  772544585  262
24   30 0 dconf-service
Nov 07 11:52:54 miguel-MacBookPro kernel: [ 6855] 0  685513013  197
28   30 0 dbus-daemon
Nov 

Bug#804549: simpleburn: segmentation fault

[Christophe Alonso]

Package: simpleburn
Version: 1.7.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Start simpleburn, then click "analiser le media" (analyze medium ?)



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

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

Versions of packages simpleburn depends on:
ii  cdrdao   1:1.2.3-2+b1
ii  cdrskin  1.4.0-3
ii  icedax   9:1.1.11-3
ii  libatk1.0-0  2.18.0-1
ii  libc62.19-22
ii  libcairo21.14.4-1
ii  libcdio-utils0.83-4.2
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.6-2
ii  libgdk-pixbuf2.0-0   2.32.1-1
ii  libglib2.0-0 2.46.1-2
ii  libgtk2.0-0  2.24.28-1
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpangoft2-1.0-01.38.1-1
ii  xorriso  1.4.0-3

Versions of packages simpleburn recommends:
ii  flac 1.3.1-4
ii  mencoder 2:1.2-1
ii  mpg123   1.22.4-1
ii  mplayer  2:1.2-1
ii  normalize-audio  0.7.7-13
ii  vorbis-tools 1.4.0-7

simpleburn suggests no packages.

-- no debconf information

Bug#785052: Uploading 8.2 to experimental?

[David Prévot]

On Thu, Aug 20, 2015 at 03:57:01PM +0200, David Prévot wrote:

> It’s almost ready to be uploaded to experimental. I need to figure out
> if the encryption upgrade can be automated first.

I keep updating the VCS to the latest upstream releases, and publish
packages to people.d.o, but unfortunately, I have still no clue how to
manage an upgrade with encryption enabled (i.e., following upstream
documentation doesn’t get me to migrate manually to the new encryption,
even going threw the “normal” process – upgrading to latest 8.0, then
latest 8.1, etc. –), so I don’t really know how to proceed from here.

A first step could be to fail the upgrade in preinst with a big fat
warning if encryption is enable, maybe even decrypt everything in
preinst if possible (note that it may take a lot of time depending on
the amount of data, and possibly expose data to third party, so I don’t
think such behaviour should be the default).

Any hint to deal with encryption would be welcome, I might upload to
experimental if I go the path of failing install if encryption is enable
in preinst unless there is a better solution (and I hope there is…).

Regards

David


signature.asc
Description: PGP signature

Bug#804530: haproxy: Updated debdiff for stop action

[James Page]

Source: haproxy
Version: 1.6.2-2
Followup-For: Bug #804530

Revise debdiff based on discussion; main work is from Louis Bouchard (see 
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737).

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

Kernel: Linux 4.2.0-16-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 haproxy-1.6.2/debian/haproxy.init haproxy-1.6.2/debian/haproxy.init
--- haproxy-1.6.2/debian/haproxy.init	2015-11-03 20:21:36.0 +
+++ haproxy-1.6.2/debian/haproxy.init	2015-11-09 14:35:13.0 +
@@ -29,6 +29,13 @@
 [ -f /etc/default/rcS ] && . /etc/default/rcS
 . /lib/lsb/init-functions
 
+tmp_pidfile=$(tempfile -s .haproxy.init)
+
+clean()
+{
+	rm -f $tmp_pidfile
+}
+trap clean EXIT
 
 check_haproxy_config()
 {
@@ -62,8 +69,9 @@
 
 	ret=0
 	for pid in $(cat $PIDFILE); do
-		start-stop-daemon --quiet --oknodo --stop \
-			--retry 5 --pid $pid --exec $HAPROXY || ret=$?
+		echo $pid > $tmp_pidfile
+  		start-stop-daemon --quiet --oknodo --stop \
+			--retry 5 --pidfile $tmp_pidfile --exec $HAPROXY || ret=$?
 	done
 
 	[ $ret -eq 0 ] && rm -f $PIDFILE

Bug#804545: patch jessie version for use with Chromium

[Daniel Pocock]

On 9 November 2015 14:16:56 GMT+00:00, Jonas Smedegaard  wrote:
>Quoting Daniel Pocock (2015-11-09 14:32:51)
>> As described in #770659, Chromium is having problems with the
>standard 
>> version of libsrtp0 on jessie.
>
>The problem it has is that it a) rely on libSRTP to provide randomness,
>
>and b) block the underlying calls done internally in libSRTP to get 
>randomness from other sources.
>
>> Users have been disabling the sandbox in Chromium to work around this
>
>> issue, hence the security tag has been used.
>
>The very use of libSRTP is a security issue: libSRTP does *not* provide
>
>cryptographically secure randomness, and next major release of libSRTP 
>will _stop_ offer that unreliable randomness API.
>
>Therefore I believe the way forward with this is to get Chromium to get
>
>randomness via some other API than the bad libSRTP approach used now, 
>and then when that is in place try backport the proper approach to the 
>Chromium in Debian stable.
>
>I do not like to change the libSRTP code in Debian stable.  The patch 
>itself is tiny, but just as the very Chromium issue demonstrates, can 
>nevertheless have big consequences.
>
>


The patch could be adapted so it only tries the alternative (fopen) in 
situations where open fails.

Do you think this would reduce risk?

I would prefer to see Chromium provide a more definitive solution too, but it 
has been like this for a long time now and because it is silently failing 
without explanation it is one of those things that causes user frustration and 
can be wrongly perceived as a Debian fault.

Bug#804553: do not max my CPU once a week

[Antoine Beaupr��]

Package: dhelp
Version: 0.6.21+nmu6
Severity: wishlist

I don't quite understand why, but every once in a while, what I think is
this package maxes out my CPU in what seems to be an attempt at
rebuilding a documentation index. According to top, it looks like this:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+   COMMAND
29460 root  20   0  187092 172884   2736 R  80,0  4,7   1:57.14 index++

And ps axfu is like this:

USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 22706  0.0  0.0  12644  1928 ?Ss   nov08   0:00 
/usr/sbin/anacron -dsq
root 29439  0.0  0.0   4328   748 ?S09:11   0:00  \_ /bin/sh -c 
run-parts --report /etc/cron.weekly
root 29445  0.0  0.0   4216   692 ?S09:11   0:00  \_ 
run-parts --report /etc/cron.weekly
root 29453  0.0  0.0   4328   804 ?S09:11   0:00  \_ 
/bin/sh /etc/cron.weekly/dhelp
root 29458  0.1  0.5  80148 18828 ?Sl   09:11   0:00  
\_ /usr/bin/ruby -w /usr/sbin/dhelp_parse -i
root 29460 29.3  4.7 187092 172888 ?   S09:11   2:11
  \_ /usr/bin/index++ --config-file /usr/share/dhelp/config/swish++.conf 
--index-file /var/lib/dhelp/documents.index --follow-links -

Sometimes it's ghostscript that maxes out the CPU, but it's within the
same cronjob:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+   COMMAND
10112 root  20   0  110836  21172   9268 R  99,7  0,6   0:00.74 gs

The job takes about 12 minutes to complete.

I am pretty sure the package list hasn't changed. I haven't done
upgrades or changed the documentation set that warrants a full rebuild
of the documentation. Why is this happening?

And why is this happening in a cronjob and not as part of a trigger or
something similar?

Because this is running weekly, new packages will not be picked up for a
week, which may cause confusion...

The dhelp cronjob file doesn't explain its purpose either, it would be
nice if it was at least possible to turn the thing off easily.

A.
-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages dhelp depends on:
ii  doc-base0.10.6
ii  libdata-page-perl   2.02-1
ii  libhtml-parser-perl 3.71-1+b3
ii  liblocale-gettext-perl  1.05-8+b1
ii  libtemplate-perl2.24-1.2+b1
ii  liburi-perl 1.64-1
ii  perl-modules5.20.2-3+deb8u1
ii  poppler-utils   0.26.5-2
ii  pstotext1.9-6+b1
ii  ruby1:2.1.5+deb8u1
ii  ruby-bdb0.6.6-1+b2
ii  ruby-debian 0.3.9
ii  ruby-gettext3.1.2-1
ii  ruby2.1 [ruby-interpreter]  2.1.5-2+deb8u2
ii  swish++ 6.1.5-2.2
ii  ucf 3.0030

Versions of packages dhelp recommends:
ii  chromium [www-browser]  46.0.2490.71-1~deb8u1
ii  epiphany-browser [www-browser]  3.14.1-1
ii  html2text   1.3.2a-18
ii  iceweasel [www-browser] 38.4.0esr-1~deb8u1
ii  lynx-cur [www-browser]  2.8.9dev1-2+deb8u1

Versions of packages dhelp suggests:
pn  catdvi  
pn  info2www
pn  man2html
ii  nginx-full [httpd-cgi]  1.6.2-5

-- no debconf information

Bug#804557: python-jmespath: FTBFS: ImportError: No module named nose.tools

[Chris Lamb]

Source: python-jmespath
Version: 0.4.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

python-jmespath fails to build from source in unstable/amd64:

  [..]
  
  ==
  ERROR: tests.test_compliance (unittest.loader.ModuleImportFailure)
  --
  ImportError: Failed to import test module: tests.test_compliance
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in
_find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in
_get_module_from_name
  __import__(name)
File "tests/test_compliance.py", line 6, in 
  from nose.tools import assert_equal
  ImportError: No module named nose.tools
  
  
  --
  Ran 76 tests in 0.030s
  
  FAILED (errors=1)
  E: pybuild pybuild:274: test: plugin distutils failed with: exit
  code=1: cd /build/python-jmespath-0.4.1/.pybuild/pythonX.Y_2.7/build;
  python2.7 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir .
  returned exit code 13
  debian/rules:11: recipe for target 'build' failed
  make: *** [build] Error 25
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/python-jmespath_0.4.1-1.build1.log.gz


Regards,

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


python-jmespath.0.4.1-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#804559: puppet: Typo in lib/puppet/ssl/host.rb: certficate -> certificate

[Santiago Vila]

Package: puppet
Version: 3.8.3-1
Severity: minor
Tags: patch

The patch says it all.

Thanks.--- a/lib/puppet/ssl/host.rb
+++ b/lib/puppet/ssl/host.rb
@@ -218,7 +218,7 @@ DOC
   raise Puppet::Error, <

Bug#804558: tweepy: FTBFS: ImportError: No module named {unittest2,vcr}

[Chris Lamb]

Source: tweepy
Version: 3.4.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

tweepy fails to build from source in unstable/amd64:

  [..]

  ==
  ERROR: tests.test_streaming (unittest.loader.ModuleImportFailure)
  --
  ImportError: Failed to import test module: tests.test_streaming
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in
_find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in
_get_module_from_name
  __import__(name)
File "tests/test_streaming.py", line 3, in 
  from .config import tape
File "tests/config.py", line 3, in 
  import vcr
  ImportError: No module named vcr
  
  
  ==
  ERROR: tests.test_utils (unittest.loader.ModuleImportFailure)
  --
  ImportError: Failed to import test module: tests.test_utils
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in
_find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in
_get_module_from_name
  __import__(name)
File "tests/test_utils.py", line 5, in 
  import unittest2 as unittest
  ImportError: No module named unittest2
  
  
  --
  Ran 7 tests in 0.001s
  
  FAILED (errors=7)
  E: pybuild pybuild:274: test: plugin distutils failed with: exit
  code=1: cd /build/tweepy-3.4.0/.pybuild/pythonX.Y_2.7/build; python2.7
  -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir .
  returned exit code 13
  debian/rules:5: recipe for target 'build' failed
  make: *** [build] Error 25
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/tweepy_3.4.0-1.build1.log.gz


Regards,

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


tweepy.3.4.0-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#804556: datanommer.models: FTBFS: StatementError: raised as a result of Query-invoked autoflush

[Chris Lamb]

Source: datanommer.models
Version: 0.6.4-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

datanommer.models fails to build from source in unstable/amd64:

  [..]

File
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py",
line 174, in save_obj
  mapper, table, insert)
File
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py",
line 785, in _emit_insert_statements
  execute(statement, params)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py",
line 914, in execute
  return meth(self, multiparams, params)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/sql/elements.py",
line 323, in _execute_on_connection
  return connection._execute_clauseelement(self, multiparams,
  params)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py",
line 1010, in _execute_clauseelement
  compiled_sql, distilled_params
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py",
line 1078, in _execute_context
  None, None)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py",
line 1341, in _handle_dbapi_exception
  exc_info
File "/usr/lib/python2.7/dist-packages/sqlalchemy/util/compat.py",
line 199, in raise_from_cause
  reraise(type(exception), exception, tb=exc_tb)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py",
line 1073, in _execute_context
  context = constructor(dialect, self, conn, *args)
File
"/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py",
line 569, in _init_compiled
  self._process_executesingle_defaults()
File
"/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py",
line 1014, in _process_executesingle_defaults
  val = self.get_insert_default(c)
File
"/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py",
line 966, in get_insert_default
  return self._exec_default(column.default, column.type)
File
"/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py",
line 952, in _exec_default
  return default.arg(self)
File "datanommer/models/__init__.py", line 155, in
source_version_default
  dist = pkg_resources.get_distribution("datanommer.models")
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 551, in get_distribution
  dist = get_provider(dist)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 431, in get_provider
  return working_set.find(moduleOrReq) or
  require(str(moduleOrReq))[0]
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 952, in require
  needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 839, in resolve
  raise DistributionNotFound(req, requirers)
  StatementError: (raised as a result of Query-invoked autoflush;
  consider using a session.no_autoflush block if this flush is occurring
  prematurely) (pkg_resources.DistributionNotFound) The
  'datanommer.models' distribution was not found and is required by the
  application [SQL: u'INSERT INTO messages (msg_id, i, topic, timestamp,
  certificate, signature, category, source_name, source_version, _msg)
  VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)'] [parameters: [{'category':
  'git', 'certificate': 'blah', 'i': 1, 'timestamp':
  datetime.datetime(2012, 8, 7, 2, 47, 30, 886738), '_msg':
  '{"commit":{"branch":"master","email":"m...@redhat.com","message":"Clear
  CFLAGS CXXFLAGS LDFLAGS.\\nThis is a bit of a
  hammer.","name":"Mark
  
Wielaard","rev":"7a98f80d9b61ce167e4ef8129c81ed9284ecf4e1","stats":{"files":{"valgrind.spec":{"deletions":2,"insertions":1,"lines":3}},"total":{"deletions":2,"files":1,"insertions":1,"lines":3}},"summary":"Clear
  CFLAGS CXXFLAGS LDFLAGS.","username":"mjw"}}', 'msg_id': None,
  'topic': 'org.debian.prod.git.receive.valgrind.master', 'signature':
  'blah'}]]
  
  --
  Ran 12 tests in 1.241s
  
  FAILED (errors=8)
  E: pybuild pybuild:274: test: plugin distutils failed with: exit
  code=1: cd
  /build/datanommer.models-0.6.4/.pybuild/pythonX.Y_2.7/build; python2.7
  -m nose tests
  dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7
  --dir . returned exit code 13
  debian/rules:3: recipe for target 'build' failed
  make: *** [build] Error 25
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/datanommer.models_0.6.4-2.build1.log.gz


Regards,

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

Bug#804612: RFP: tensorflow -- Library for numerical computation using data flow graphs

[Kjetil Kjernsmo]

Package: wnpp
Severity: wishlist

* Package name: tensorflow
  Version : 0.5.0
  Upstream Author : Google Brain Team
* URL : http://www.tensorflow.org/
* License : Apache 2.0
  Programming Lang: C++, Python
  Description : Library for numerical computation using data flow graphs

TensorFlow is Google's machine for deep learning, a prominent
direction in Artificial Intelligence. It was just released as Free
Software and this is really bound to get big.

They describe it as:

TensorFlow™ is an open source software library for numerical
computation using data flow graphs. Nodes in the graph represent
mathematical operations, while the graph edges represent the
multidimensional data arrays (tensors) communicated between them. The
flexible architecture allows you to deploy computation to one or more
CPUs or GPUs in a desktop, server, or mobile device with a single API.

Bug#804285: transition: ode

[Leopold Palomo-Avellaneda]

El Dilluns, 9 de novembre de 2015, a les 19:11:05, Emilio Pozuelo Monfort va 
escriure:
> Control: tags -1 confirmed
> 
> On 06/11/15 23:53, Leopold Palomo-Avellaneda wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Dear Release Team,
> > 
> > I'm filing this bug for a new transition of ode (Open Dynamics Engine).
> > 
> > In Debian we have a version too old (0.11.1-4.1, 2009-05-25). The package
> > has been rewritten and a new version has been uploaded to experimental
> > (0.13.1+git20150309-1). This version has been tested with the ode build
> > dependencies with this result:
> > 
> > darkplaces: ok, built
> > k3d: ok, built
> > mokomaze: ok, built
> > mu-cade: ok built
> > ompl: ok built
> > pyepl: ok built
> > pyode: ok built
> > soya: too old the debian version. Upstream didn't test the new version
> > with 0.13.x ode taoframework: ok, built
> > stormbaancoureur: ok. built
> > xmoto: ok, built
> 
> You can go ahead with this.
> 
> Note that a couple of packages (mokomaze, soya) build-depend on the old
> libode-sp-dev. Please file bugs with severity serious against those two
> packages and make them block this bug.

Sorry. I don't understand it.

Are you asking me that I fill a bug against a package because FTBFS "before" 
upload it to unstable or "after" upload it and it failed?


-- 
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?


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

Bug#804595: unzip: Regression caused by DSA-3386-1 when extracting 0-byte files

[Santiago Vila]

On Mon, Nov 09, 2015 at 08:45:40PM +0100, Salvatore Bonaccorso wrote:
> Source: unzip
> Version: 6.0-19
> Severity: important
> Control: found -1 6.0-16+deb8u1
> 
> Hi
> 
> One patch to address the issues in DSA-3386-1 introduced a regression
> when when extracting 0-byte files, cf.
> http://www.ubuntu.com/usn/usn-2788-2/
> 
> (I can apply the fixed patch for jessie- and wheezy-security, and as
> well sid in case needed).

Hello Salvatore. I've just uploaded a fix for sid, which should appear
in incoming.debian.org in short.

Please go ahead with jessie and wheezy.

Thanks a lot.

Bug#804614: kicad: 'TO_SOT_Packages_SMD.pretty' and 'TO_SOT_Packages_THT.pretty' does not exist

[Jonas]

Package: kicad
Version: 4.0.0~rc1-2
Severity: normal

Dear Maintainer,

When I open Cvpcb I have an error

Errors were encountered loading footprints
IO_ERROR: footprint library path
'/usr/share/kicad/modules/TO_SOT_Packages_SMD.pretty' does not exist
from /home/georgesk/developpement/kicad/kicad-4.0.0~rc1/pcbnew/kicad_plugin.cpp
: FootprintEnumerate() : line 1758
IO_ERROR: footprint library path
'/usr/share/kicad/modules/TO_SOT_Packages_THT.pretty' does not exist
from /home/georgesk/developpement/kicad/kicad-4.0.0~rc1/pcbnew/kicad_plugin.cpp
: FootprintEnumerate() : line 1758

I have a same error when I select a fooprint since Eschema (key F on a
Component -> Select). After on library selector TO_SOT_Packages_SMD
TO_SOT_Packages_THT don't work



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

Kernel: Linux 4.3.0-0.slh.1-aptosid-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kicad depends on:
ii  kicad-common4.0.0~rc1-2
ii  libboost-context1.58.0  1.58.0+dfsg-4
ii  libboost-date-time1.58.01.58.0+dfsg-4
ii  libboost-filesystem1.58.0   1.58.0+dfsg-4
ii  libboost-iostreams1.58.01.58.0+dfsg-4
ii  libboost-locale1.58.0   1.58.0+dfsg-4
ii  libboost-program-options1.58.0  1.58.0+dfsg-4
ii  libboost-regex1.58.01.58.0+dfsg-4
ii  libboost-system1.58.0   1.58.0+dfsg-4
ii  libboost-thread1.58.0   1.58.0+dfsg-4
ii  libc6   2.19-22
ii  libgcc1 1:5.2.1-23
ii  libgl1-mesa-glx [libgl1]11.0.4-1
ii  libglu1-mesa [libglu1]  9.0.0-2.1
ii  libgomp15.2.1-23
ii  libstdc++6  5.2.1-23
ii  libwxbase3.0-0v53.0.2+dfsg-1.2
ii  libwxgtk3.0-0v5 3.0.2+dfsg-1.2

kicad recommends no packages.

Versions of packages kicad suggests:
pn  extra-xdg-menus  
pn  kicad-doc-en | kicad-doc-fr | kicad-doc-it | kicad-doc-ja | kicad-d  

-- no debconf information

Bug#804487: [Pkg-openssl-devel] Bug#804487: openssl_1.0.2d-3 breaks mumble and mumble-server after binNMU

[Kurt Roeckx]

On Mon, Nov 09, 2015 at 09:36:46PM +, Chris Knadle wrote:
> Kurt Roeckx:
> > On Mon, Nov 09, 2015 at 07:58:30PM +, Chris Knadle wrote:
> >>
> >> Everybody dealing with the mumble bug agrees that SSL should be initialized
> >> before making SSL calls -- the reason I opened #804487 is to try to figure
> >> out /what/ caused mumble_1.2.10-2+b1 to break, when mumble_1.2.10-2 works.
> >> And I just tested -- mumble_1.2.10-2 works with openssl_1.0.2d-3.
> >> snapshot.debian.org has the before-and-after binNMU here:
> > 
> > I assume you mean 1.0.2d-1 there.  The soname changed between -1
> > and -3 you actually get a different binary package.
> 
> Let me be more specific: mumble_1.2.10-2 that was built with
> openssl_1.0.2d-1 works fine with openssl 1.0.2d-3 installed -- yet
> mumble_1.2.10-2+b1 that was /built/ with openssl_1.0.2d-3 does not.

Please note the "openssl" binary package version doesn't change
anything.  You don't depend on it, you use the library.

Mumble_1.2.10-2 uses the binary package "libssl1.0.0" (version
1.0.2d-1) while mumble_1.2.10-2+b1 uses libssl1.0.2 (version
1.0.2d-3).


Kurt

Bug#791794: UUID not found for root

[Martin Michlmayr]

* Ian Campbell  [2015-11-06 16:03]:
> I've just pushed this change to flash-kenrel.git, so it will be in the
> next upload.

Thanks!

Can we also get this into a stable update?  I believe some of the
reports were about stable.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#804315: [ralph.amis...@gmail.com: outrageous, thievery]

[Ed Dixon]

Be sure to share Daniels story via social media using the buttons on his
blog. I hope it wakes up the entire community to what happens when you
actually do something right around here! https://t.co/NwWs9AfW87 Thanks,

On Mon, Nov 9, 2015 at 2:15 PM Richard Newton  wrote:

> I agree, shame on those responsible. I have been using Debian for almost
> 15 years and this is the first time I have been ashamed. Add my name to the
> record "of conscientious objection."
>
> RIchard Newton
>
> On Mon, Nov 9, 2015 at 11:42 AM, Ralph Amissah 
> wrote:
>
>> I post not in anger but sadness, I should not let my voice go uncounted.
>>
>> Attached is my note to Daniel of earlier today, before his posting of
>> "an abrupt end to Debian Live". Debian Live which he said Debian should
>> have (as a Debian developer) in 2006 and went on to deliver, rather
>> nicely (with (and without) help).
>>
>> - Forwarded message from Ralph Amissah 
>> -
>>
>> From: Ralph Amissah 
>> To: Daniel Baumann
>> Subject: outrageous, thievery
>> Date: Mon, 9 Nov 2015 09:28:44 -0500
>> Message-ID: <20151109142844.GA28261@niu>
>> User-Agent: Mutt/1.5.24 (2015-08-30)
>>
>> Daniel, (already one of the more active Debian Developers then) I
>> remember you telling Debian at Debconf 2006, Mexico about how "we"[1]
>> needed a live-maker within the project. I said then that I thought this
>> one of the most important projects within Debian (I was surprised that
>> there was not more interest and effort offered by others at the time,
>> though there was some, those so keen now did not seem to pay attention
>> then).  Already then it was clear that it would one day be able to and
>> possibly be the preferred way to do a Debian install... as I said,
>> important. I saw how you contributed to Debian then, and I know how you
>> have contributed since. Instead of welcoming you and your work, there
>> seems to have been an effort to isolate you.
>>
>> Well clearly others have seen the fruits of your labor as a threat and
>> with envy, and ripe for their plucking!
>>
>> Outrageous! Disgusting. It is nasty. A bit strange to think that I
>> "know" some of those guys.
>>
>> My interest in Debian proper, dropped with your earlier treatment, it
>> took away the desire to be a closer part of it. At least that took out
>> much of any idealized notion of the inner workings of it. And there have
>> been other moves since. I continue to be amazed by the politics of
>> groups within Debian.  This though has the feel of blatant thievery.
>> Chals characterization of a dictatorial coup would seem to be most
>> accurate.
>>
>> It has no doubt to do with power (perhaps indirectly money is involved
>> as well), your work & work area being seen as strategically important.
>> They do it because they can, & justify it whatever which way they will.
>>
>> I am sorry. I feel pretty bruised on your behalf.
>>
>> We have not spoken in a long while. I hope we have the chance to talk in
>> happier times.
>>
>> Greetings.
>> Ralph
>>
>> P.S. We are ok, not much to report.
>>
>> - End forwarded message -
>> [edits: addition of footnote, &; s/picking/plucking/]
>>
>> Indeed I am a friend of Daniel and primarily a user of Debian (a minor
>> contributor of a package (sisu[2]) that I wrote that I am happy to have in
>> Debian). In other circumstances I would consider myself at least an
>> admirer of individuals involved on the other side of this. Indeed I (use
>> use some of your software daily and) have met a number of you over the
>> years at a number of Debconfs and have fond memories for example of
>> visits to Cambridge when I lived in the U.K. and of being "introduced"
>> to Debian by Debian insiders.
>>
>> Thanks to all who have stood up for Daniel, he is a wonderful, generous,
>> (and capable) person. And yes, I do think him "wronged" by "Debian".
>> There are others that know him pretty well, who have followed a fairly
>> long sequence of events who must be outraged as well.
>>
>> Of course I wish Debian well, but I do not see your "handling" of Daniel
>> as its finest hour. This will no doubt "blow over" as it must ultimately
>> for the good of the project, but it sticks in my craw as it no doubt
>> does others, and there should be some record of conscientious objection.
>>
>> Ralph Amissah
>>
>> [1] to be clear, "we" was Debian.
>> [2] http://www.sisudoc.org/
>> https://qa.debian.org/developer.php?login=s...@lists.sisudoc.org
>>
>>
>
>
> --
> CONFIDENTIALITY NOTICE: This electronic communication with its contents
> may contain confidential and/or privileged information. It is solely for
> the use of the intended recipient(s). Unauthorized interception, review,
> use, or disclosure is prohibited and may violate applicable laws including
> the Electronic Communications Privacy Act. If you are not the intended
> recipient, or authorized to receive for the intended 

Bug#804506: RFS: attic 0.16-1

[Caitlin Matos]

Thank you for your feedback! I have updated the package and pushed the 
changes to git. Note that I have removed the debian/0.16-1 tag until the 
package is approved. Please see my notes below.


On 09/11/15 05:19 AM, Gianfranco Costamagna wrote:

Control: tags -1 moreinfo
Control: owner -1 !


Hi, please use this watch file

1) http://pypi.debian.net/attic/watch

I tried a uscan --debug --force-download and the current watch file in git just 
doesn't work


I have changed the watch file to the one you recommended, which does 
work. However, the previous one was also working.


uscan --force-download --debug
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile line:
   opts="pgpsigurlmangle=s/$/.asc/" 
https://pypi.python.org/simple/attic/ 
../../packages/source/A/Attic/Attic-(.*).tar.gz#md5=.*

uscan debug: last pristine tarball version: 0.16
uscan debug: last pristine tarball version: 0.16
uscan debug: dversionmangled last version: 0.16
uscan debug: Last pristine tarball version (dversionmangled): 0.16
uscan debug: requesting URL https://pypi.python.org/simple/attic/
uscan debug: received content:
Links for atticvalue="2" />Links for attichref="../../packages/source/A/Attic/Attic-0.10.tar.gz#md5=6d10d44ab7a2036da54c01c2b3e4c089" 
rel="internal">Attic-0.10.tar.gz
href="../../packages/source/A/Attic/Attic-0.11.tar.gz#md5=bbc92d78895c9792417f4c9539db8a07" 
rel="internal">Attic-0.11.tar.gz
href="../../packages/source/A/Attic/Attic-0.12.tar.gz#md5=2c81a7380268d659e213f599c48b170b" 
rel="internal">Attic-0.12.tar.gz
href="../../packages/source/A/Attic/Attic-0.13.tar.gz#md5=2c9d4723ec42295472ae5bfe443d2a19" 
rel="internal">Attic-0.13.tar.gz
href="../../packages/source/A/Attic/Attic-0.14.tar.gz#md5=34fa12b5acff370b2558f4b0e9490b4c" 
rel="internal">Attic-0.14.tar.gz
href="../../packages/source/A/Attic/Attic-0.15.tar.gz#md5=6c73819782c496bdd6f9ca9380b2a84c" 
rel="internal">Attic-0.15.tar.gz
href="../../packages/source/A/Attic/Attic-0.16.tar.gz#md5=9c767c883f7f48bf95e7e5307ce6b5ea" 
rel="internal">Attic-0.16.tar.gz
href="../../packages/source/A/Attic/Attic-0.6.1.tar.gz#md5=73ecbe0c8310dafc33ffb05c3bf8647d" 
rel="internal">Attic-0.6.1.tar.gz
href="../../packages/source/A/Attic/Attic-0.6.tar.gz#md5=308c0c7601df03fc4be63071f5ae5c6f" 
rel="internal">Attic-0.6.tar.gz
href="../../packages/source/A/Attic/Attic-0.7.tar.gz#md5=57fc1ebbadafeedced8e75e3f6f10635" 
rel="internal">Attic-0.7.tar.gz
href="../../packages/source/A/Attic/Attic-0.8.1.tar.gz#md5=dad271a1c86bc18fd392eb9b26d1d4b3" 
rel="internal">Attic-0.8.1.tar.gz
href="../../packages/source/A/Attic/Attic-0.8.tar.gz#md5=67455f1ef7fa585b1cd367475cc67190" 
rel="internal">Attic-0.8.tar.gz
href="../../packages/source/A/Attic/Attic-0.9.tar.gz#md5=a8466f4040e8b1e0fd9e7b2810d2fea0" 
rel="internal">Attic-0.9.tar.gz


[End of received content]
uscan debug: matching pattern(s) 
(?:(?:https://pypi.python.org)?\/simple\/attic\/)?../../packages/source/A/Attic/Attic-(.*).tar.gz#md5=.*

-- Found the following matching hrefs:

../../packages/source/A/Attic/Attic-0.10.tar.gz#md5=6d10d44ab7a2036da54c01c2b3e4c089 
(0.10)


../../packages/source/A/Attic/Attic-0.11.tar.gz#md5=bbc92d78895c9792417f4c9539db8a07 
(0.11)


../../packages/source/A/Attic/Attic-0.12.tar.gz#md5=2c81a7380268d659e213f599c48b170b 
(0.12)


../../packages/source/A/Attic/Attic-0.13.tar.gz#md5=2c9d4723ec42295472ae5bfe443d2a19 
(0.13)


../../packages/source/A/Attic/Attic-0.14.tar.gz#md5=34fa12b5acff370b2558f4b0e9490b4c 
(0.14)


../../packages/source/A/Attic/Attic-0.15.tar.gz#md5=6c73819782c496bdd6f9ca9380b2a84c 
(0.15)


../../packages/source/A/Attic/Attic-0.16.tar.gz#md5=9c767c883f7f48bf95e7e5307ce6b5ea 
(0.16)


../../packages/source/A/Attic/Attic-0.6.1.tar.gz#md5=73ecbe0c8310dafc33ffb05c3bf8647d 
(0.6.1)


../../packages/source/A/Attic/Attic-0.6.tar.gz#md5=308c0c7601df03fc4be63071f5ae5c6f 
(0.6)


../../packages/source/A/Attic/Attic-0.7.tar.gz#md5=57fc1ebbadafeedced8e75e3f6f10635 
(0.7)


../../packages/source/A/Attic/Attic-0.8.1.tar.gz#md5=dad271a1c86bc18fd392eb9b26d1d4b3 
(0.8.1)


../../packages/source/A/Attic/Attic-0.8.tar.gz#md5=67455f1ef7fa585b1cd367475cc67190 
(0.8)


../../packages/source/A/Attic/Attic-0.9.tar.gz#md5=a8466f4040e8b1e0fd9e7b2810d2fea0 
(0.9)

uscan debug: new version 0.16
uscan debug: new filename 
../../packages/source/A/Attic/Attic-0.16.tar.gz#md5=9c767c883f7f48bf95e7e5307ce6b5ea
uscan debug: filenamemangled new filename 
Attic-0.16.tar.gz#md5=9c767c883f7f48bf95e7e5307ce6b5ea
uscan debug: downloadurlmangled upstream URL 
https://pypi.python.org/simple/attic/../../packages/source/A/Attic/Attic-0.16.tar.gz#md5=9c767c883f7f48bf95e7e5307ce6b5ea

uscan debug: pgpsigurlmangle rule s/$/.asc/
uscan debug: pgpsigurlmangled upstream URL 
https://pypi.python.org/simple/attic/../../packages/source/A/Attic/Attic-0.16.tar.gz#md5=9c767c883f7f48bf95e7e5307ce6b5ea.asc

Newest version on remote site is 0.16, local version is 0.16
 => Package is up to date

Bug#804608: freedombox-setup: [PATCH] Configure ssh server

[James Valleroy]

On 11/09/2015 04:58 PM, Petter Reinholdtsen wrote:
> [Bob Mottram]
>> This patch adds some extra hardening to the ssh server settings, in
>> accordance with the recommendations on bettercrypto.org.
> This approach, editing the file /etc/ssh/sshd_config after installation,
> will very likely cause conffile question during upgrades when the
> package maintainer version of the file changes in the openssh-server
> deb.  This will cause upgrade problems for non-technical users.
>
> Because of this, it is probably better to convince the openssh package
> maintainer to change the Debian default settings the way you propose to
> change the FreedomBox setup.
>
> Perhaps this bug should be reassigned to openssh-server or be cloned and
> a copy reassigned to openssh-server?
>
I think sshd_config is not a conffile. It seems to be produced by the
postinst:
https://sources.debian.net/src/openssh/1:6.9p1-2/debian/openssh-server.postinst/#L150

And if I'm reading that postinst correctly, it seems like they do
attempt to handle upgrades of this file properly.

That said, I do agree that we should try to improve Debian default settings.

--
James



signature.asc
Description: OpenPGP digital signature

Bug#804601: arc-gui-clients: FTBFS: requires -std=c++11 or -std=gnu++11 but pkg-config missing

[Chris West (Faux)]

Source: arc-gui-clients
Version: 0.4.6-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

In file included from /usr/include/c++/5/type_traits:35:0,
 from /usr/include/sigc++-2.0/sigc++/visit_each.h:22,
 from /usr/include/sigc++-2.0/sigc++/functors/slot.h:6,
 from /usr/include/sigc++-2.0/sigc++/slot.h:19,
 from /usr/include/arc/DateTime.h:7,
 from /usr/include/arc/UserConfig.h:11,
 from /arc-gui-clients-0.4.6/src/common/arctools.h:7,
 from /arc-gui-clients-0.4.6/src/common/arctools.cpp:1:
/usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file requires 
compiler and library support for the ISO C++ 2011 standard. This support is 
currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 
compiler options.
 #error This file requires compiler and library support for the \
  ^

This was supposedly fixed in libsigc++-2.0, if you're using pkgconfig:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800371

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/arc-gui-clients.html

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

Bug#804487: [Pkg-openssl-devel] Bug#804487: openssl_1.0.2d-3 breaks mumble and mumble-server after binNMU

[Kurt Roeckx]

On Mon, Nov 09, 2015 at 07:58:30PM +, Chris Knadle wrote:
> 
> Everybody dealing with the mumble bug agrees that SSL should be initialized
> before making SSL calls -- the reason I opened #804487 is to try to figure
> out /what/ caused mumble_1.2.10-2+b1 to break, when mumble_1.2.10-2 works.
> And I just tested -- mumble_1.2.10-2 works with openssl_1.0.2d-3.
> snapshot.debian.org has the before-and-after binNMU here:

I assume you mean 1.0.2d-1 there.  The soname changed between -1
and -3 you actually get a different binary package.

>http://snapshot.debian.org/package/mumble/1.2.10-2/
> 
> I'm looking at and comparing the build logs, and one of the things I see is
> that the build pulled in both libssl1.0.0 and libssl1.0.2, where the prior
> build only pulled in libssl1.0.0.  ldd shows that only libssl1.0.2 is linked
> in the resulting 'mumble' binary.  That doesn't sound right.

It's one of your build dependencies that was probably still using
libssl1.0.0 and probably isn't anymore.  That shouldn't case any
issue.


Kurt

Bug#804603: courier: FTBFS: undefined reference to `SSLv3_method'

[Chris West (Faux)]

Source: courier
Version: 0.73.1-1.6
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build, as openssl have dropped sslv3 support:

./.libs/libcouriertls.a(libcouriertls.o): In function `tls_create':
/courier-0.73.1/libs/tcpd/libcouriertls.c:530: undefined reference to 
`SSLv3_method'
collect2: error: ld returned 1 exit status
Makefile:524: recipe for target 'couriertls' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/courier.html

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

Bug#804060: iceweasel: SIGPIPE when running under KDE

[Arthur Marsh]

Package: iceweasel
Version: 38.4.0esr-1
Followup-For: Bug #804060

Dear Maintainer,

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

Problem has returned... will try running under gdb again soon.

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


-- Package-specific info:

-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled

Name: Certificate Patrol
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/certpat...@psyc.eu
Package: xul-ext-certificatepatrol
Status: enabled

Name: ChatZilla
Location: ${PROFILE_EXTENSIONS}/{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}
Status: enabled

Name: Default theme
Location: 
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled

Name: Easy Youtube Video Downloader Express
Location: ${PROFILE_EXTENSIONS}/{b9acf540-acba-11e1-8ccb-001fd0e08bd4}.xpi
Status: enabled

Name: English (GB) Language Pack locale
Location: 
/usr/lib/iceweasel/browser/extensions/langpack-en...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-en-gb
Status: enabled

Name: Flashblock
Location: ${PROFILE_EXTENSIONS}/{3d7eb24f-2740-49df-8937-200b1cc08f8a}
Status: enabled

Name: Furigana Inserter
Location: ${PROFILE_EXTENSIONS}/furiganainser...@zorkzero.net
Status: user-disabled

Name: Japanese Language Pack locale
Location: 
/usr/lib/iceweasel/browser/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-ja
Status: enabled

Name: NetVideoHunter
Location: ${PROFILE_EXTENSIONS}/netvideohun...@netvideohunter.com
Status: user-disabled

Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
Status: enabled

Name: Rikaichan
Location: ${PROFILE_EXTENSIONS}/{0AA9101C-D3C1-4129-A9B7-D778C6A17F82}
Status: enabled

Name: Rikaichan Japanese Names Dictionary File
Location: ${PROFILE_EXTENSIONS}/rikaichan-jpna...@polarcloud.com
Status: enabled

Name: Rikaichan Japanese-English Dictionary File
Location: ${PROFILE_EXTENSIONS}/rikaichan-j...@polarcloud.com
Status: enabled

Name: Sage
Location: ${PROFILE_EXTENSIONS}/{a6ca9b3b-5e52-4f47-85d8-cca35bb57596}.xpi
Status: enabled

Name: Sage-Too
Location: ${PROFILE_EXTENSIONS}/{0f9daf7e-2ee2-4fcf-9d4f-d43d93963420}
Status: app-disabled

Name: ShowIP
Location: ${PROFILE_EXTENSIONS}/{3e9bb2a7-62ca-4efa-a4e6-f6f6168a652d}.xpi
Status: enabled

Name: Tab Restore
Location: ${PROFILE_EXTENSIONS}/tabrest...@plugin.xpi
Status: enabled

Name: Tree Style Tab
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/treestyle...@piro.sakura.ne.jp
Package: xul-ext-treestyletab
Status: user-disabled

-- Plugins information
Name: IcedTea-Web Plugin (using IcedTea-Web 1.5.2 (1.5.2-1.1))
Location: /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-7-plugin:amd64
Status: enabled

Name: Shockwave Flash (11.2.202.508)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled


-- Addons package information
ii  icedtea-7-plug 1.5.2-1.1amd64web browser plugin based on OpenJ
ii  iceweasel  38.4.0esr-1  amd64Web browser based on Firefox
ii  iceweasel-l10n 1:38.4.0esr- all  English (United Kingdom) language
ii  iceweasel-l10n 1:38.4.0esr- all  Japanese language package for Ice
ii  xul-ext-certif 2.0.14-4 all  Certificate Monitor for Iceweasel
ii  xul-ext-treest 0.15.2015090 all  Show browser tabs like a tree

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

Kernel: Linux 4.3.0+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages iceweasel depends on:
ii  debianutils   4.5.1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.29-1
ii  libatk1.0-0   2.18.0-1
ii  libc6 2.19-22
ii  libcairo2 1.14.4-1
ii  libdbus-1-3   1.10.2-1.0nosystemd1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-3
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6-2
ii  libgcc1   1:5.2.1-23
ii  libgdk-pixbuf2.0-02.32.1-1
ii  libglib2.0-0  2.46.1-2
ii  libgtk2.0-0   2.24.28-1
ii  libhunspell-1.3-0 1.3.3-3+b1
ii  libnspr4  2:4.10.10-1
ii  libnss3   2:3.20.1-1
ii  libpango-1.0-01.38.1-1
ii  libsqlite3-0  3.9.2-1
ii  libstartup-notification0  0.12-4
ii  libstdc++65.2.1-23
ii  libvpx2   1.4.0-4
ii  libx11-6  2:1.6.3-1
ii  

Bug#804604: fetchmail: FTBFS: undefined reference to `SSLv3_client_method'

[Chris West (Faux)]

Source: fetchmail
Version: 6.3.26-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build, as openssl have dropped sslv3 support:

socket.o: In function `SSLOpen':
/fetchmail-6.3.26/socket.c:917: undefined reference to `SSLv3_client_method'
collect2: error: ld returned 1 exit status
Makefile:699: recipe for target 'fetchmail' failed
make[3]: *** [fetchmail] Error 1

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/fetchmail.html

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

Bug#804610: nordugrid-arc: FTBFS: error: 'SSLv3_client_method' was not declared in this scope

[Chris West (Faux)]

Source: nordugrid-arc
Version: 5.0.3-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

PayloadTLSMCC.cpp: In constructor 
'ArcMCCTLS::PayloadTLSMCC::PayloadTLSMCC(Arc::MCCInterface*, const 
ArcMCCTLS::ConfigTLSMCC&, Arc::Logger&)':
PayloadTLSMCC.cpp:241:46: error: 'SSLv3_client_method' was not declared in this 
scope
  sslctx_=SSL_CTX_new(SSLv3_client_method());
  ^
PayloadTLSMCC.cpp: In constructor 
'ArcMCCTLS::PayloadTLSMCC::PayloadTLSMCC(Arc::PayloadStreamInterface*, const 
ArcMCCTLS::ConfigTLSMCC&, Arc::Logger&)':
PayloadTLSMCC.cpp:328:46: error: 'SSLv3_server_method' was not declared in this 
scope
  sslctx_=SSL_CTX_new(SSLv3_server_method());
  ^
Makefile:742: recipe for target 'libmcctls_la-PayloadTLSMCC.lo' failed
make[7]: *** [libmcctls_la-PayloadTLSMCC.lo] Error 1
make[7]: Leaving directory '/nordugrid-arc-5.0.3/src/hed/mcc/tls'
Makefile:803: recipe for target 'all-recursive' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/nordugrid-arc.html

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

Bug#804613: spamassassin: FTBFS: undefined reference to `SSLv3_client_method'

[Chris West (Faux)]

Source: spamassassin
Version: 3.4.1-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

spamc/libspamc.c: In function ‘message_filter’:
spamc/libspamc.c:1217:11: warning: assignment discards ‘const’ qualifier from 
pointer target type [-Wdiscarded-qualifiers]
  meth = TLSv1_client_method();
   ^
spamc/libspamc.c:1219:13: warning: implicit declaration of function 
‘SSLv3_client_method’ [-Wimplicit-function-declaration]
  meth = SSLv3_client_method(); /* default */
 ^
spamc/libspamc.c:1219:11: warning: assignment makes pointer from integer 
without a cast [-Wint-conversion]
  meth = SSLv3_client_method(); /* default */
   ^
spamc/libspamc.c: In function ‘message_tell’:
spamc/libspamc.c:1607:7: warning: assignment makes pointer from integer without 
a cast [-Wint-conversion]
  meth = SSLv3_client_method();
   ^
/tmp/cccJRbQ7.o: In function `message_tell':
/spamassassin-3.4.1/spamc/libspamc.c:1607: undefined reference to 
`SSLv3_client_method'
/tmp/cccJRbQ7.o: In function `message_filter':
/spamassassin-3.4.1/spamc/libspamc.c:1219: undefined reference to 
`SSLv3_client_method'
collect2: error: ld returned 1 exit status
spamc/Makefile:43: recipe for target 'spamc/spamc' failed
make[2]: *** [spamc/spamc] Error 1
make[2]: Leaving directory '/spamassassin-3.4.1'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/spamassassin.html

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

Bug#804591: Requested `iscsistart -f` output

[David Britton]

ubuntu@admirable-dad:/etc/network/interfaces.d$ sudo iscsistart -f
# BEGIN RECORD 2.0-873
iface.initiatorname = maas-compute-2-a
iface.transport_name = tcp
iface.hwaddress = 00:25:b5:aa:50:c0
iface.bootproto = STATIC
iface.ipaddress = 10.10.10.201
iface.subnet_mask = 255.255.255.0
iface.gateway = 10.10.10.1
iface.primary_dns = 0.0.0.0
iface.secondary_dns = 0.0.0.0
iface.vlan_id = 0
iface.net_ifacename = eth0
node.name = iqn.2014-12.com.cisco.pod-controller.maas-compute-2
node.conn[0].address = 10.10.10.10
node.conn[0].port = 3260
node.boot_lun = 0100
# END RECORD



-- 
David Britton 

Bug#804616: sslscan: FTBFS: undefined reference to `SSLv3_client_method'

[Chris West (Faux)]

Source: sslscan
Version: 1.8.2-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

/tmp/cc9BAqDL.o: In function `testCipher':
/sslscan-1.8.2/sslscan.c:578: undefined reference to `SSLv3_client_method'
/tmp/cc9BAqDL.o: In function `defaultCipher':
/sslscan-1.8.2/sslscan.c:706: undefined reference to `SSLv3_client_method'
/tmp/cc9BAqDL.o: In function `testHost':
/sslscan-1.8.2/sslscan.c:1205: undefined reference to `SSLv3_client_method'
/sslscan-1.8.2/sslscan.c:1215: undefined reference to `SSLv3_client_method'
/tmp/cc9BAqDL.o: In function `main':
/sslscan-1.8.2/sslscan.c:1431: undefined reference to `SSLv3_client_method'
/tmp/cc9BAqDL.o:/sslscan-1.8.2/sslscan.c:1440: more undefined references to 
`SSLv3_client_method' follow
collect2: error: ld returned 1 exit status

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/sslscan.html

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

Bug#804591: [Pkg-iscsi-maintainers] Bug#804591: open-iscsi: iscsi_auto flag should use iscsistart --fwparam_network in addition to -b

[Scott Moser]

> > If we were to invoke 'iscsistart --fwparam_network' after having done
> > configure_networking, then the iscsi parameters would be in affect.
> > Its may be arguable that this is simply misconfiguration of the ip=
> > parameter.
>
> On the other hand, one could argue that one might want to overwrite
> the parameters set in the firmware with an explicit kernel commmand
> line.

Agreed.

> I think the case is definitely clear if iscsi_auto is specified
> without an ip= parameter, then iscsistart should take care of it.

Definitely.  Unfortunately, the case that I'm working on is with MAAS
which specifies a ip= command line to its provided iscsi server.  The
install environment is then provided over read-only iscsi.

It seems reasonable that you might have 'ip=' on the kernel command line
for reasons unrelated to iscsi entirely, and possibly referencing
different network devices.

> Btw. is there any way to test this in a VM? I don't have access to
> the corresponding hardware that sets these values, so I can't
> really test this myself.

Luckily, you *can* do it entirely within qemu and ipxe with a few minor
limitations.  Figuring out how to do that is non-trivial, but I've managed
my way through it.

I'll try to collect my notes and post back here.

>
> > Also of note, /run/net-.conf will not be written if iscsistart
> > configures the networking as opposed to 'ipconfig' doing it.
>
> Could you give me the output of
>
> iscsistart -f
>
> on a system with iBFT? I think I could write a trivial POSIX
> shell parser for that that creates the corresponding
> /run/net-*.conf files. From the open-iscsi source I'm pretty
> confident I know what the output looks like, but I'd rather
> have real data to test that with.

Right, that was my thought too.  I  might suggest not reading iscsistart
-f, but rather the files from /sys/firmware/ibft.  Here is some output
from each, for those not adventuresome enough to try on their own. Note, i
added a carriage return to subnet mask that did not have one.

This system was booted with an pxe config that looked like this and
'break=top' on the kernel command line.  The values jsut then collected
from the initramfs:
#!ipxe
dhcp
set iscsi-host 192.168.1.131
set base-url http://192.168.1.131:/
sanhook --drive 0x80 iscsi:${iscsi-host}::3260:1:inst-000-1
sanhook --drive 0x81 iscsi:${iscsi-host}::3260:1:inst-000-2
kernel ${base-url}/boot-kernel break=top
initrd ${base-url}/boot-initrd
boot

(initramfs) iscsistart --fwparam_print
# BEGIN RECORD 2.0-873
iface.initiatorname =
iqn.2010-04.org.ipxe:----
iface.transport_name = tcp
iface.hwaddress = 52:54:00:12:34:56
iface.bootproto = STATIC
iface.ipaddress = 10.0.2.16
iface.subnet_mask = 255.255.255.0
iface.gateway = 10.0.2.2
iface.primary_dns = 10.0.2.3
iface.vlan_id = 0
iface.net_ifacename = eth0
node.name = inst-000-2
node.conn[0].address = 192.168.1.131
node.conn[0].port = 3260
node.boot_lun = 0100
# END RECORDk

(initramfs) ipconfig eth0
IP-Config: eth0 hardware address 52:54:00:12:34:56 mtu 1500 DHCP RARP
IP-Config: eth0 guessed broadcast address 10.0.2.255
IP-Config: eth0 complete (dhcp from 10.0.2.2):
 address: 10.0.2.15broadcast: 10.0.2.255   netmask:
255.255.255.0
 gateway: 10.0.2.2 dns0 : 10.0.2.3 dns1   : 0.0.0.0
 rootserver: 10.0.2.2 rootpath:
 filename  :


(initramfs) for f in $(find /sys/firmware/ibft/ -type f); do echo == $f ==; cat 
$f; done
== /sys/firmware/ibft/target0/lun ==
0100
== /sys/firmware/ibft/target0/port ==
3260
== /sys/firmware/ibft/target0/target-name ==
inst-000-2
== /sys/firmware/ibft/target0/flags ==
3
== /sys/firmware/ibft/target0/index ==
0
== /sys/firmware/ibft/target0/chap-type ==
0
== /sys/firmware/ibft/target0/nic-assoc ==
0
== /sys/firmware/ibft/target0/ip-addr ==
192.168.1.131
== /sys/firmware/ibft/initiator/flags ==
3
== /sys/firmware/ibft/initiator/index ==
0
== /sys/firmware/ibft/initiator/initiator-name ==
iqn.2010-04.org.ipxe:----
== /sys/firmware/ibft/ethernet0/mac ==
52:54:00:12:34:56
== /sys/firmware/ibft/ethernet0/vlan ==
0
== /sys/firmware/ibft/ethernet0/flags ==
3
== /sys/firmware/ibft/ethernet0/index ==
0
== /sys/firmware/ibft/ethernet0/primary-dns ==
10.0.2.3
== /sys/firmware/ibft/ethernet0/subnet-mask ==
255.255.255.0
== /sys/firmware/ibft/ethernet0/gateway ==
10.0.2.2
== /sys/firmware/ibft/ethernet0/origin ==
1
== /sys/firmware/ibft/ethernet0/ip-addr ==
10.0.2.16

Bug#804614: Acknowledgement (kicad: 'TO_SOT_Packages_SMD.pretty' and 'TO_SOT_Packages_THT.pretty' does not exist)

[Jonas]

If I add  
https://github.com/KiCad/TO_SOT_Packages_THT.pretty
and
https://github.com/KiCad/TO_SOT_Packages_SMD.pretty
in
/usr/share/kicad/modules
it's work !
Le lundi 09 novembre 2015 à 21:36 +, Debian Bug Tracking System a
écrit :
> Thank you for filing a new Bug report with Debian.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due
> course.
> 
> Your message has been sent to the package maintainer(s):
>  Georges Khaznadar 
> 
> If you wish to submit further information on this problem, please
> send it to 804...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 

Bug#804606: httest: FTBFS: undefined reference to `SSLv3_server_method'

[Chris West (Faux)]

Source: httest
Version: 2.4.8-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build, as openssl have dropped support for sslv3:

ssl_module.o: In function `worker_set_server_method':
/httest-2.4.8/src/ssl_module.c:785: undefined reference to `SSLv3_server_method'
ssl_module.o: In function `worker_set_client_method':
/httest-2.4.8/src/ssl_module.c:738: undefined reference to `SSLv3_client_method'
collect2: error: ld returned 1 exit status

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/httest.html

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

Bug#804617: xchat-gnome: FTBFS: error: implicit declaration of function 'SSLv3_server_method'

[Chris West (Faux)]

Source: xchat-gnome
Version: 1:0.30.0~git20131003.d20b8d-3
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

ssl.c: In function '_SSL_context_init':
ssl.c:73:30: error: implicit declaration of function 'SSLv3_server_method' 
[-Werror=implicit-function-declaration]
  ctx = SSL_CTX_new (server ? SSLv3_server_method() : SSLv3_client_method ());
  ^
ssl.c:73:2: warning: nested extern declaration of 'SSLv3_server_method' 
[-Wnested-externs]
  ctx = SSL_CTX_new (server ? SSLv3_server_method() : SSLv3_client_method ());
  ^
ssl.c:73:54: error: implicit declaration of function 'SSLv3_client_method' 
[-Werror=implicit-function-declaration]
  ctx = SSL_CTX_new (server ? SSLv3_server_method() : SSLv3_client_method ());
  ^
ssl.c:73:2: warning: nested extern declaration of 'SSLv3_client_method' 
[-Wnested-externs]
  ctx = SSL_CTX_new (server ? SSLv3_server_method() : SSLv3_client_method ());
  ^
ssl.c:73:21: warning: passing argument 1 of 'SSL_CTX_new' makes pointer from 
integer without a cast [-Wint-conversion]
  ctx = SSL_CTX_new (server ? SSLv3_server_method() : SSLv3_client_method ());
 ^
In file included from ssl.c:20:0:
/usr/include/openssl/ssl.h:2131:10: note: expected 'const SSL_METHOD * {aka 
const struct ssl_method_st *}' but argument is of type 'int'
 SSL_CTX *SSL_CTX_new(const SSL_METHOD *meth);
  ^
ssl.c: In function '_SSL_get_cipher_info':
ssl.c:205:4: warning: assignment discards 'const' qualifier from pointer target 
type [-Wdiscarded-qualifiers]
  c = SSL_get_current_cipher (ssl);
^
ssl.c: In function '_SSL_socket':
ssl.c:284:18: warning: comparison between pointer and integer

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/xchat-gnome.html

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

Bug#804591: [Pkg-iscsi-maintainers] Bug#804591: open-iscsi: iscsi_auto flag should use iscsistart --fwparam_network in addition to -b

[Christian Seiler]

Hi,

On 11/09/2015 10:40 PM, Scott Moser wrote:
>>> If we were to invoke 'iscsistart --fwparam_network' after having done
>>> configure_networking, then the iscsi parameters would be in affect.
>>> Its may be arguable that this is simply misconfiguration of the ip=
>>> parameter.
>>
>> On the other hand, one could argue that one might want to overwrite
>> the parameters set in the firmware with an explicit kernel commmand
>> line.
> 
> Agreed.
> 
>> I think the case is definitely clear if iscsi_auto is specified
>> without an ip= parameter, then iscsistart should take care of it.
> 
> Definitely.  Unfortunately, the case that I'm working on is with MAAS
> which specifies a ip= command line to its provided iscsi server.  The
> install environment is then provided over read-only iscsi.

Does the ip= match here or is there some problem with it? If
there's no problem and you are just mentioning it to be
cautious: I think it's fair to ask our users to not
misconfigure their network in initramfs. I mean, without
iscsi_auto and manual iSCSI config a wrong ip=  will also lead
to an unbootable system.

> It seems reasonable that you might have 'ip=' on the kernel command line
> for reasons unrelated to iscsi entirely, and possibly referencing
> different network devices.

Then maybe we should do the following: if iscsi_auto is specified,
call iscsistart -N first, then configure the network regularly.
Then ip= will always override iBFT, but other devices will also
be activated.

>> Btw. is there any way to test this in a VM? I don't have access to
>> the corresponding hardware that sets these values, so I can't
>> really test this myself.
> 
> Luckily, you *can* do it entirely within qemu and ipxe with a few minor
> limitations.  Figuring out how to do that is non-trivial, but I've managed
> my way through it.

Oh great, I don't have time today anymore (I'm in time zone UTC+01,
so it's quite late here ;-)), but I'll take a look at it during
the next few days.

> Right, that was my thought too.  I  might suggest not reading iscsistart
> -f, but rather the files from /sys/firmware/ibft.

The problem there is matching against the right network interface
name - it's certainly possible, but parsing the output of
iscsistart is probably a lot simpler.

> Here is some output
> from each, for those not adventuresome enough to try on their own. Note, i
> added a carriage return to subnet mask that did not have one.

Where exactly did it not have a carriage return? According to
the open-iscsi source, all values printed have \n there
(at least Debian's git snapshot, maybe that was a bug in the
version that was fixed between the version you use and the
version I have).

> [lots of output]

Thanks a lot!

I've created a VERY simple parser in POSIX shell that reads
the input of iscsistart -f and pseudo-creates the /run/net-
file and attached it to this email. If you don't have any
objections to it, I'll integrate that into the initramfs hook.

Regards,
Christian


parse_iscsistart.sh
Description: application/shellscript


signature.asc
Description: OpenPGP digital signature

Bug#784070: mdadm: diff for NMU version 3.3.2-5.1

[Bryan Christ]

Yann,

Thanks for the instructions.  I am happy to say that I was able to remove
one of the 3 drives in my raid-1 configuration and boot just find with the
degraded array.  At least for me, this change fixes the problem.

On Fri, Nov 6, 2015 at 2:18 AM, Yann Soubeyrand <
yann-externe.soubeyr...@edf.fr> wrote:

> On Thu, 5 Nov 2015 14:17:11 -0600 Bryan Christ 
> wrote:
> > I'll be glad to test this if someone will provide me instructions on how
> to
> > apply the fixes.  I've downloaded all the files from here:
> >
> > http://mentors.debian.net/debian/pool/main/m/mdadm/
> >
> > I have also extracted mdadm_3.3.2-5.1.dsc with this:
> >
> > dpkg-source -x mdadm_3.3.2-5.1.dsc
> >
> > It's pretty unclear what to do next.  A few steps of instructions would
> be
> > helpful.
>
> Make sure to install the build-essential package plus all the build
> dependencies listed in the .dsc file (Build-Depends: debhelper (>=
> 6.0.7~), po-debconf, groff-base), then execute the command
> dpkg-buildpackage -us -uc inside the source tree you extracted earlier
> using dpkg-source -x.
>
> If you want to learn more about package building you can refer to
> https://www.debian.org/doc/manuals/maint-guide/build.en.html.
>
> Cheers
>
> Yann
>



-- 
Bryan
<><

Bug#804602: canl-c: FTBFS: undefined reference to `SSLv3_client_method'

[Chris West (Faux)]

Source: canl-c
Version: 2.1.6-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build, due to openssl dropping sslv3:

libtool: compile:  gcc -Wall -g -I./src/proxy -I. -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
-c ./examples/canl_sample_server.c -Wall -g -I./src -I. -o canl_sample_server.o 
>/dev/null 2>&1
libtool --mode=link gcc -Wl,-z,relro canl_sample_server.lo -L. -lcanl_c -o 
server
libtool: link: gcc -Wl,-z -Wl,relro .libs/canl_sample_server.o -o .libs/server  
-L. /canl-c-2.1.6/.libs/libcanl_c.so 
/canl-c-2.1.6/.libs/libcanl_c.so: undefined reference to `SSLv3_client_method'
collect2: error: ld returned 1 exit status
Makefile:134: recipe for target 'server' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/canl-c.html

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

Bug#804315: [ralph.amis...@gmail.com: outrageous, thievery]

[Richard Newton]

I agree, shame on those responsible. I have been using Debian for almost 15
years and this is the first time I have been ashamed. Add my name to the
record "of conscientious objection."

RIchard Newton

On Mon, Nov 9, 2015 at 11:42 AM, Ralph Amissah 
wrote:

> I post not in anger but sadness, I should not let my voice go uncounted.
>
> Attached is my note to Daniel of earlier today, before his posting of
> "an abrupt end to Debian Live". Debian Live which he said Debian should
> have (as a Debian developer) in 2006 and went on to deliver, rather
> nicely (with (and without) help).
>
> - Forwarded message from Ralph Amissah  -
>
> From: Ralph Amissah 
> To: Daniel Baumann
> Subject: outrageous, thievery
> Date: Mon, 9 Nov 2015 09:28:44 -0500
> Message-ID: <20151109142844.GA28261@niu>
> User-Agent: Mutt/1.5.24 (2015-08-30)
>
> Daniel, (already one of the more active Debian Developers then) I
> remember you telling Debian at Debconf 2006, Mexico about how "we"[1]
> needed a live-maker within the project. I said then that I thought this
> one of the most important projects within Debian (I was surprised that
> there was not more interest and effort offered by others at the time,
> though there was some, those so keen now did not seem to pay attention
> then).  Already then it was clear that it would one day be able to and
> possibly be the preferred way to do a Debian install... as I said,
> important. I saw how you contributed to Debian then, and I know how you
> have contributed since. Instead of welcoming you and your work, there
> seems to have been an effort to isolate you.
>
> Well clearly others have seen the fruits of your labor as a threat and
> with envy, and ripe for their plucking!
>
> Outrageous! Disgusting. It is nasty. A bit strange to think that I
> "know" some of those guys.
>
> My interest in Debian proper, dropped with your earlier treatment, it
> took away the desire to be a closer part of it. At least that took out
> much of any idealized notion of the inner workings of it. And there have
> been other moves since. I continue to be amazed by the politics of
> groups within Debian.  This though has the feel of blatant thievery.
> Chals characterization of a dictatorial coup would seem to be most
> accurate.
>
> It has no doubt to do with power (perhaps indirectly money is involved
> as well), your work & work area being seen as strategically important.
> They do it because they can, & justify it whatever which way they will.
>
> I am sorry. I feel pretty bruised on your behalf.
>
> We have not spoken in a long while. I hope we have the chance to talk in
> happier times.
>
> Greetings.
> Ralph
>
> P.S. We are ok, not much to report.
>
> - End forwarded message -
> [edits: addition of footnote, &; s/picking/plucking/]
>
> Indeed I am a friend of Daniel and primarily a user of Debian (a minor
> contributor of a package (sisu[2]) that I wrote that I am happy to have in
> Debian). In other circumstances I would consider myself at least an
> admirer of individuals involved on the other side of this. Indeed I (use
> use some of your software daily and) have met a number of you over the
> years at a number of Debconfs and have fond memories for example of
> visits to Cambridge when I lived in the U.K. and of being "introduced"
> to Debian by Debian insiders.
>
> Thanks to all who have stood up for Daniel, he is a wonderful, generous,
> (and capable) person. And yes, I do think him "wronged" by "Debian".
> There are others that know him pretty well, who have followed a fairly
> long sequence of events who must be outraged as well.
>
> Of course I wish Debian well, but I do not see your "handling" of Daniel
> as its finest hour. This will no doubt "blow over" as it must ultimately
> for the good of the project, but it sticks in my craw as it no doubt
> does others, and there should be some record of conscientious objection.
>
> Ralph Amissah
>
> [1] to be clear, "we" was Debian.
> [2] http://www.sisudoc.org/
> https://qa.debian.org/developer.php?login=s...@lists.sisudoc.org
>
>


-- 
CONFIDENTIALITY NOTICE: This electronic communication with its contents may
contain confidential and/or privileged information. It is solely for the
use of the intended recipient(s). Unauthorized interception, review, use,
or disclosure is prohibited and may violate applicable laws including the
Electronic Communications Privacy Act. If you are not the intended
recipient, or authorized to receive for the intended recipient, please
contact the sender and destroy all copies of the communication. Thank you
for your consideration.

Bug#804608: freedombox-setup: [PATCH] Configure ssh server

[Bob Mottram]

Package: freedombox-setup
Severity: wishlist

It seems odd sending a patch as a bug report, but freedombox-discuss just
gives me "550 Administrative prohibition".

This patch adds some extra hardening to the ssh server settings, in
accordance with the recommendations on bettercrypto.org.

Possibly /bin/bash could be /bin/sh


---
 setup.d/15_ssh_server | 36 
  1 file changed, 36 insertions(+)
   create mode 100755 setup.d/15_ssh_server

diff --git a/setup.d/15_ssh_server b/setup.d/15_ssh_server
new file mode 100755
index 000..0685a95
--- /dev/null
+++ b/setup.d/15_ssh_server
@@ -0,0 +1,36 @@
+#!/bin/bash
+
+# This script hardens the ssh server settings, using recommendations
+# from bettercrypto.org
+
+SSH_CIPHERS="chacha20-poly1...@openssh.com,aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes128-ctr"
+SSH_MACS="hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160"
+SSH_KEX="curve25519-sha...@libssh.org,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1"
+
+sed -i 's/Protocol .*/Protocol 2/g' /etc/ssh/sshd_config
+sed -i 's/StrictModes.*/StrictModes yes/g' /etc/ssh/sshd_config
+sed -i 's/PermitEmptyPasswords.*/PermitEmptyPasswords no/g' 
/etc/ssh/sshd_config
+sed -i 's/PermitRootLogin.*/PermitRootLogin no/g' /etc/ssh/sshd_config
+sed -i 's/X11Forwarding.*/X11Forwarding no/g' /etc/ssh/sshd_config
+sed -i 's/ServerKeyBits.*/ServerKeyBits 4096/g' /etc/ssh/sshd_config
+if ! grep -q '#HostKey' /etc/ssh/sshd_config; then
+   sed -i 's|HostKey /etc/ssh/ssh_host_dsa_key|#HostKey 
/etc/ssh/ssh_host_dsa_key|g' /etc/ssh/sshd_config
+   sed -i 's|HostKey /etc/ssh/ssh_host_ecdsa_key|#HostKey 
/etc/ssh/ssh_host_ecdsa_key|g' /etc/ssh/sshd_config
+fi
+if grep -q 'Ciphers' /etc/ssh/sshd_config; then
+sed -i "s|Ciphers.*|Ciphers ${SSH_CIPHERS}|g" /etc/ssh/sshd_config
+else
+echo "Ciphers ${SSH_CIPHERS}" >> /etc/ssh/sshd_config
+fi
+if grep -q 'MACs' /etc/ssh/sshd_config; then
+sed -i "s|MACs.*|MACs ${SSH_MACS}|g" /etc/ssh/sshd_config
+else
+echo "MACs ${SSH_MACS}" >> /etc/ssh/sshd_config
+fi
+if grep -q 'KexAlgorithms' /etc/ssh/sshd_config; then
+sed -i "s|KexAlgorithms.*|KexAlgorithms ${SSH_KEX}|g" /etc/ssh/sshd_config
+else
+echo "KexAlgorithms ${SSH_KEX}" >> /etc/ssh/sshd_config
+fi
+
+echo "Done configuring ssh server."
--
2.4.1


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

Kernel: Linux 3.16.0-4-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)

Bug#804609: netty-tcnative: FTBFS: error: implicit declaration of function 'SSLv3_client_method'

[Chris West (Faux)]

Source: netty-tcnative
Version: 1.1.33.Fork9-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build, probably because openssl have disabled sslv3:

src/sslcontext.c: In function 'Java_org_apache_tomcat_jni_SSLContext_make':
src/sslcontext.c:135:31: error: implicit declaration of function 
'SSLv3_client_method' [-Werror=implicit-function-declaration]
 ctx = SSL_CTX_new(SSLv3_client_method());
   ^
src/sslcontext.c:135:31: error: passing argument 1 of 'SSL_CTX_new' makes 
pointer from integer without a cast [-Werror=int-conversion]
In file included from src/ssl_private.h:46:0,
 from src/sslcontext.c:31:
/usr/include/openssl/ssl.h:2131:10: note: expected 'const SSL_METHOD * {aka 
const struct ssl_method_st *}' but argument is of type 'int'
 SSL_CTX *SSL_CTX_new(const SSL_METHOD *meth);
  ^

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/netty-tcnative.html

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

Bug#804611: socat: FTBFS: undefined reference to `SSLv3_client_method'

[Chris West (Faux)]

Source: socat
Version: 1.7.3.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

ranlib libxio.a
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_GNU_SOURCE -Wall -Wno-parentheses  -DHAVE_CONFIG_H -I. -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -o socat socat.o libxio.a -lwrap -lrt -lutil  -lssl -lcrypto
libxio.a(sslcls.o): In function `sycSSLv3_client_method':
/socat-1.7.3.0/sslcls.c:61: undefined reference to `SSLv3_client_method'
libxio.a(sslcls.o): In function `sycSSLv3_server_method':
/socat-1.7.3.0/sslcls.c:69: undefined reference to `SSLv3_server_method'
collect2: error: ld returned 1 exit status
Makefile:115: recipe for target 'socat' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/socat.html

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

Bug#804595: unzip: Regression caused by DSA-3386-1 when extracting 0-byte files

[Salvatore Bonaccorso]

Hi Santiago,

On Mon, Nov 09, 2015 at 08:45:40PM +0100, Salvatore Bonaccorso wrote:
> One patch to address the issues in DSA-3386-1 introduced a regression
> when when extracting 0-byte files, cf.
> http://www.ubuntu.com/usn/usn-2788-2/
> 
> (I can apply the fixed patch for jessie- and wheezy-security, and as
> well sid in case needed).

wheezy-security and jessie-security regression update is on it's way
to security-master and building.

Salvatore

Bug#804349: mplayer2: pulseaudio output poor quality

[Michal Suchanek]

Package: mplayer2
Followup-For: Bug #804349

Hello,

installing an USB sound card resolves the problem with ALSA sound driver
and alsa can be used for non-bluetooth oputput. With pulse/ALSA there is
no problem. So the problem is specific to using pulse/OSS.

Thanks

Michal

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (990, 'stable'), (500, 'oldstable'), (171, 
'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 mplayer2 depends on:
ii  liba52-0.7.4  0.7.4-18
ii  libasound21.0.29-1
ii  libass5   0.13.0-1
ii  libavcodec56  6:11.4-1~deb8u1
ii  libavformat56 6:11.4-1~deb8u1
ii  libavresample26:11.4-1~deb8u1
ii  libavutil54   6:11.4-1~deb8u1
ii  libbluray11:0.9.0-1
ii  libbs2b0  3.1.0+dfsg-2.1
ii  libc6 2.19-22
ii  libcaca0  0.99.beta19-2
ii  libcdio-cdda1 0.83-4.2
ii  libcdio-paranoia1 0.83-4.2
ii  libcdio13 0.83-4.2
ii  libdca0   0.0.5-7
ii  libdirectfb-1.2-9 1.2.10.0-5.1
ii  libdv41.0.0-6
ii  libdvdread4   5.0.3-1
ii  libenca0  1.16-2
ii  libfaad2  2.8.0~cvs20150510-1
ii  libgif4   4.1.6-11
ii  libgl1-mesa-glx [libgl1]  11.0.4-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  libjpeg62-turbo   1:1.4.1-2
ii  liblcms2-22.6-3+b3
ii  liblircclient00.9.0~pre1-1.2
ii  libmad0   0.15.1b-8
ii  libmpg123-0   1.22.4-1
ii  libogg0   1.3.2-1
ii  libpng12-01.2.50-2+b2
ii  libpostproc52 6:0.git20120821-4
ii  libpulse0 7.0-1+b1
ii  libquvi7  0.4.1-3
ii  libsdl1.2debian   1.2.15-12
ii  libsmbclient  2:4.1.17+dfsg-4
ii  libspeex1 1.2~rc1.2-1
ii  libswscale3   6:11.4-1~deb8u1
ii  libtheora01.1.1+dfsg.1-7
ii  libtinfo5 6.0+20151024-1
ii  libvdpau1 1.1.1-3
ii  libvorbis0a   1.3.4-3
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxss1   1:1.2.2-1
ii  libxv12:1.0.10-1+b1
ii  libxvidcore4  2:1.3.4-1
ii  libxxf86vm1   1:1.1.4-1
ii  zlib1g1:1.2.8.dfsg-2+b1

mplayer2 recommends no packages.

mplayer2 suggests no packages.

-- no debconf information

Bug#804315: Seriously?

[Joerg Jaspert]

Hi,

seriously? You are kidding, right? This *IS* a namespace invasion and a
bad one at that. The live-* is in Debian, scrap arguments of "its
not official", thats just wrong. You may not like its maintainer, you
may not want that particular software and want to get your own. Thats
all fine, but this action is not.

Use a different name or politely ask the originals name owner if they
care to give it to you.

-- 
bye, Joerg
Our lives are in the hands of men no smarter than you or I. Many of them
incompetent boobs. I know this because I’ve worked alongside them, gone
bowling with them, watch them pass me over for promotions time and
again.


signature.asc
Description: PGP signature

Bug#798734: gsound-tools: Section should be “sound”

[Ben Finney]

Control: reassign -1 gsound-tools
Control: found -1 gsound-tools/1.0.1-2

On 09-Nov-2015, Michael Biebl wrote:
> On Sat, 12 Sep 2015 14:01:42 +1000 Ben Finney
>  wrote:
> > Package: gsound
> > Version: 1.0.1-2
> > Severity: minor
> > 
> > The section “gnome” is for packages that are “part of the GNOME
> > environment or closely integrated into it”.

(As an aside: Michael, your mail system is evidently corrupting
character encoding of messages. The original 2015-11-09 message was
encoded as UTF-8, and shows up correctly in the Debian BTS; something
apart from that has corrupted it between that and your reply.)

> Do you mean the gsound-tools binary package here or the source
> package?

I meant the ‘gsound-tools’ binary package, and I'm reassigning this
bug report now. Thank you for pointing out my mistake.

On closer inspection, it seems one could argue that ‘gsound-tools’ be
considered “part of the GNOME environment or closely integrated into
it”.

I still think ‘gsound-tools’ is sufficiently independent of GNOME that
it would be a better fit in “Section: sound”; I'm not overly familiar
with it though, and I defer to your consideration. If you consider the
matter, and think that's not right, I won't object if you close this
report as “notfound -1 gsound-tools/1.0.1-2”.

-- 
 \  “A lie can be told in a few words. Debunking that lie can take |
  `\   pages. That is why my book… is five hundred pages long.” —Chris |
_o__)Rodda, 2011-05-05 |
Ben Finney 


signature.asc
Description: PGP signature

Bug#804386: [htcondor-debian] Bug#804386: condor: FTBFS on arm64 ppc64el and s390x: conflicting declaration 'typedef long unsigned int uint64_t'

[Todd Tannenbaum]

Thanks for the report, John (TJ) Knoeller  (cc-ed) 
is an upstream HTCondor developer and is looking into the below build 
failure.


regards,
Todd

On 11/7/2015 5:25 PM, Emilio Pozuelo Monfort wrote:

Package: condor
Version: 8.4.0~dfsg.1-1
Severity: serious

Your package failed to build on arm64, s390x and ppc64el:

In file included from /usr/lib/gcc/aarch64-linux-gnu/5/include/stdint.h:9:0,
  from /usr/include/c++/5/cstdint:41,
  from /usr/include/c++/5/bits/char_traits.h:380,
  from /usr/include/c++/5/string:40,
  from /«PKGBUILDDIR»/src/condor_utils/condor_event.h:36,
  from /«PKGBUILDDIR»/src/condor_utils/read_user_log.h:45,
  from 
/«PKGBUILDDIR»/src/condor_userlog/condor_userlog_job_counter.cpp:30:
/usr/include/stdint.h:55:27: error: conflicting declaration 'typedef long 
unsigned int uint64_t'
  typedef unsigned long int uint64_t;
^
In file included from 
/«PKGBUILDDIR»/src/condor_userlog/condor_userlog_job_counter.cpp:30:0:
/«PKGBUILDDIR»/src/condor_utils/read_user_log.h:38:31: note: previous 
declaration as 'typedef long long unsigned int uint64_t'
 typedef unsigned long long uint64_t;
^

Full logs at
https://buildd.debian.org/status/logs.php?pkg=condor=8.4.0~dfsg.1-1

Emilio
___
htcondor-debian mailing list
htcondor-deb...@cs.wisc.edu
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-debian




--
Todd Tannenbaum  University of Wisconsin-Madison
Center for High Throughput Computing   Department of Computer Sciences
HTCondor Technical Lead1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132  Madison, WI 53706-1685

Bug#804634: cowbuilder: conffiles not removed

[Paul Wise]

Package: cowbuilder
Version: 0.75
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate

The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by dh_installdeb
to remove these obsolete conffiles on upgrade.

https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
http://manpages.debian.org/man/1/dh_installdeb

This bug report brought to you by adequate:

http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ pkg=cowbuilder ; adequate $pkg ; dpkg-query -W -f='${Conffiles}\n' $pkg | 
grep obsolete
cowbuilder: obsolete-conffile /etc/bash_completion.d/cowbuilder
 /etc/bash_completion.d/cowbuilder 9f595b0df026c12fbcf68b9bb5e7c1dc obsolete

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (850, 
'buildd-testing-proposed-updates'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages cowbuilder depends on:
ii  cowdancer  0.75
ii  libc6  2.19-22
ii  pbuilder   0.219

cowbuilder recommends no packages.

cowbuilder suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#804635: qemubuilder: conffiles not removed

[Paul Wise]

Package: qemubuilder
Version: 0.75
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate

The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by dh_installdeb
to remove these obsolete conffiles on upgrade.

https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
http://manpages.debian.org/man/1/dh_installdeb

This bug report brought to you by adequate:

http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ pkg=qemubuilder ; adequate $pkg ; dpkg-query -W -f='${Conffiles}\n' $pkg | 
grep obsolete
qemubuilder: obsolete-conffile /etc/bash_completion.d/qemubuilder
 /etc/bash_completion.d/qemubuilder ddce89c97154a8b1329457d305c4c3da obsolete

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (850, 
'buildd-testing-proposed-updates'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages qemubuilder depends on:
ii  debootstrap 1.0.74
ii  libc6   2.19-22
ii  pbuilder0.219
ii  qemu-kvm [kvm]  1:2.4+dfsg-4

qemubuilder recommends no packages.

qemubuilder suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#804643: python-tldap: ships /usr/lib/python2.7/dist-packages/docs/__init__.py

[Andreas Beckmann]

Package: python-tldap
Version: 0.3.13-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

/usr/lib/python2.7/dist-packages/docs/__init__.py is a very generic
name that is prone to file overwrite conflicts between packages
(which caused its detection).


Andreas

Bug#804515: xfonts-mona: build-depends on obsolete ttf-kochi-gothic fonts

[Nobuhiro Iwamatsu]

Hi,

2015-11-09 11:43 GMT+09:00 Andreas Beckmann :
> Package: xfonts-mona
> Version: 2.90-7
> Severity: normal
> Control: block 726382 with -1
>
> Hi,
>
> xfonts-mona build-depends on the obsolete package ttf-kochi-gothic
> which has been requested to be removed [1]. There are
> replacements available from src:fonts-ipafont.
>
> [1] https://bugs.debian.org/726382
>

When viewed from fonts-ipafont., ttf-kochi-gothic will be target to
replacement. But fonts-ipafont
can not be replaced by xfonts-mona. Font applications of fonts-ipafon
of fonts and xfonts-mona is is different.
That ttf-kochi-gothic is already old font I understand. I will
consider a method of providing a font that does not
use ttf-kochi-gothic. I think that it can reply in this regard at the
end of this week.

>
> Andreas

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#804638: kde-plasma-desktop: "The window switcher installation is broken"

[Alex Henry]

Package: kde-plasma-desktop
Version: 5:90
Severity: minor

I have installed KDE via kde-plasma-desktop (plus kwin-x11) instead of 
kde-standard which has too many applications I 
don't use. This way I have more freedom over what is installed in my system.

If I am doing things the wrong way please close this bug report. Otherwise:

The problem is that when I go to Window Manager Settings (right-clicking on any 
window title bar) if I choose Task Switcher
and have a visualization enabled (like Cover Switch or Flip Switch from the 
drop box) the next time I do an ALT+TAB I will
get a message saying:

The Window Switcher installation is broken, resources are missing. 
Contact your distribution about this.

If I disable the transition effects (using the disable button to the left of 
the drop box) then the error no longer 
appears so this isn't a grave problem - probably just a missing dependency 
which would be nice to have fixed in order to 
be able to enjoy the transition effects whenever kde-plasma-desktop is 
installed.

Please let me know if there is a better package this bug could be reported 
against. Thanks!


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

Kernel: Linux 3.16.0-4-amd64 (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 kde-plasma-desktop depends on:
ii  kde-baseapps  4:15.08.1-1
ii  kde-runtime   4:15.08.2-1
ii  plasma-desktop4:5.4.2-1
ii  plasma-workspace  4:5.4.2-1+b1
ii  udisks2   2.1.6-2
ii  upower0.99.3-1+b2

Versions of packages kde-plasma-desktop recommends:
ii  sddm  0.12.0-5
ii  xserver-xorg  1:7.7+12

Versions of packages kde-plasma-desktop suggests:
pn  kde-l10n  

-- no debconf information

Bug#804640: iceweacel update - stackwalker.cc:125: INFO: Couldn't load symbols for: /usr/lib/iceweasel/libxul.so

[Weber]

package: iceweasel
version:  31.8.0


i send again this error.
it happend  after I updated on  2015-09-24

after the update pocess was finished ,the root shell window chrashed.
it was a su shell under normal user


then i started firefox.



user33@debian:/usr/bin$ firefox
*** UTM:SVC TimerManager:registerTimer - id: browser-cleanup-thumbnails
console.error:
  [CustomizableUI]
  Custom widget with id loop-button does not return a valid node
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols for: |
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols
for: /lib/i386-linux-gnu/libglib-2.0.so.0|1DACD275C7698050A777B0F35BEBF45B0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb724d800
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols
for: /usr/lib/iceweasel/libxul.so|4BB5BA704A08E45760868FC0A471326D0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72c3500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb74996e0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xbfa9bfec
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb722ae80
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72c34c0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7fff
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72c3500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72238e4
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb722ae80
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xae851680
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72df110
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols
for: /usr/lib/iceweasel/libnspr4.so|771155C5C020D5F1DCB6CFF8283322F40
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xbfa9c038
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x319
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x117a16b1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x5014
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72238e0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb722ba50
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xc1acd
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x14
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1482b01
2015-09-24 22:57:25: 

Bug#801601: libgrss: Please update to 0.7.0

[Hideki Yamane]

>>Give me until the end of today.  If I don't have an update posted by
>>then, then feel free to upload this version.  Thank you for the work.

Nice :)
I'm happy you maintainer update it, thank you!

-- 
Hideki Yamane

Bug#804634: ack

[Iain R. Learmonth]

Hi,

I am preparing a new upload for cowbuilder that should be ready at the end
of this week. This is already fixed in my local VCS.

It's nice to know we have a tool for detecting these though. (:

Thanks,
Iain.

-- 

Bug#804639: gnome-keyring: Uses way too much CPU

[Martín Ferrari]

Package: gnome-keyring
Version: 3.18.2-1
Severity: normal

I am using the gnome-keyring integration for Iceweasel, and since a while ago,
I noticed that when loading pages gnome-keyring-daemon starts consuming close
to 100% CPU. I don't know what's causing this, if I kill the daemon I notice I
get many prompts about unblocking the 'mozilla' keystore, so it seems that
Iceweasel is querying it pretty often, but still not enough to warrant such a
CPU usage.

Maybe it is due to some DB glitch?


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

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

Versions of packages gnome-keyring depends on:
ii  dbus-x11 1.10.2-1
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gcr  3.18.0-1
ii  libc62.19-22
ii  libcap-ng0   0.7.7-1
ii  libcap2-bin  1:2.24-12
ii  libgck-1-0   3.18.0-1
ii  libgcr-base-3-1  3.18.0-1
ii  libgcrypt20  1.6.4-3
ii  libglib2.0-0 2.46.1-1
ii  p11-kit  0.23.1-3
ii  pinentry-gnome3  0.9.6-4

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring  3.18.2-1

gnome-keyring suggests no packages.

-- no debconf information

Bug#804618: znc: FTBFS: error: ‘SSLv3_client_method’ was not declared in this scope

[Alexey Sokolov]

Hi,
This is fixed upstream in upcoming 1.6.2. I hope to release it in several days.
Upstream reference: https://github.com/znc/znc/issues/1146

2015-11-09 21:25 GMT+00:00 Chris West (Faux) :
> Source: znc
> Version: 1.6.1-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
>
> Dear Maintainer,
>
> The package fails to build:
>
> src/Csocket.cpp: In member function ‘virtual bool Csock::SSLClientSetup()’:
> src/Csocket.cpp:1467:48: error: ‘SSLv3_client_method’ was not declared in 
> this scope
>m_ssl_ctx = SSL_CTX_new( SSLv3_client_method() );
> ^
> src/Csocket.cpp: In member function ‘SSL_CTX* Csock::SetupServerCTX()’:
> src/Csocket.cpp:1589:43: error: ‘SSLv3_server_method’ was not declared in 
> this scope
>pCTX = SSL_CTX_new( SSLv3_server_method() );
>^
> Makefile:116: recipe for target 'src/Csocket.o' failed
> make[2]: *** [src/Csocket.o] Error 1
> make[2]: Leaving directory '/znc-1.6.1'
>
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/znc.html
>
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>

Bug#804636: kde-plasma-desktop: Should depend on kwin-x11

[Alex Henry]

Package: kde-plasma-desktop
Version: 5:90
Severity: normal

Honorable maintainer,

First let me apologize if this is the wrong package for my report but I'll 
explain why I thought it would be.

In the past I had used the kdm package as a package that would install a 
bare-bones KDE system on a computer.
It would bring the window manager, the startup hooks and etc, without 
also installing every single KDE application.
The kdm package is gone so I tried kde-plasma-desktop. It worked 
perfectly except for the fact that it didn't install the 'kwin-x11' 
package, which left me with a functioning plasma desktop without proper 
windows or window management.

I can't see why someone would want a kde-plasma-desktop without KWin or 
X so please consider depending on that package.
I can understand there could be some use cases I'm not able to see - in 
which case please consider using "recommends kwin-x11" or at least a 
x-window-manager virtual package, if that would make sense.

If this is absolutely the wrong package to ask for that please let me know 
so I can redirect it properly.



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

Kernel: Linux 3.16.0-4-amd64 (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 kde-plasma-desktop depends on:
ii  kde-baseapps  4:15.08.1-1
ii  kde-runtime   4:15.08.2-1
ii  plasma-desktop4:5.4.2-1
ii  plasma-workspace  4:5.4.2-1+b1
ii  udisks2   2.1.6-2
ii  upower0.99.3-1+b2

Versions of packages kde-plasma-desktop recommends:
ii  sddm  0.12.0-5
ii  xserver-xorg  1:7.7+12

Versions of packages kde-plasma-desktop suggests:
pn  kde-l10n  

-- no debconf information

Bug#783269: gdm3: when trying to login with gnome on wayland session, the sysytem logout me

[Mauro Fontana]

​I'm having this problem too, but using gdm (and gnome-shell) in its 3.18
version.​
​

On Fri, 24 Apr 2015 23:28:37 +0200 Tiziano Casavecchia <
t.casavecc...@gmail.com> wrote:
> Package: gdm3
> Version: 3.14.1-7
> Severity: important
>
> Dear Maintainer,
>
> I try to login with gnome on wayland and the system log me out each time.
Also
> in the login gdm window the button to choose session disapperars after
being
> logged out.
>

Bug#802032: gazebo: Don't depend on robot-player-dev (libgazebo5-dev)

[Anton Gladky]

2015-11-10 0:15 GMT+01:00 Jose Luis Rivero :
> Oh, I promised to the player maintainer to help with this package as it
> has been quite used by the robotics community some years ago and I think
> that it has still some users (part of them from gazebo support).
>
> Looks like patches are floating around to fix the serious bugs. Would
> you mind if I import it to debian-science and patch the whole thing?

Yes, if you want to maintain player, please contact its maintainer and feel
free to move the package under debian-science after his agreement
Anyway, if gazebo is not using this package, it would be good to drop
it from its build-depends.

Cheers

Anton

Bug#804642: bootstrap-vz: ships /usr/lib/python2.7/dist-packages/docs/__init__.py

[Andreas Beckmann]

Package: bootstrap-vz
Version: 0.9.9-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

/usr/lib/python2.7/dist-packages/docs/__init__.py is a very generic
name that is prone to file overwrite conflicts between packages
(which caused its detection).


Andreas

Bug#790120: praat: sound playback delay, random freeze after about 10-20 playbacks

[Джонатан Вашингтон]

The latest version of praat downloaded directly from the praat website
(6.0.05) has this problem fixed for me.  I'm having some package
conflicts atm, so can't test whatever's in Debian unstable, but I
imagine packaging the latest versions will solve these issues for a
range of users.

-- 
Jonathan

On 9 November 2015 at 08:00, Rafael Laboissiere  wrote:
> Control: tags -1 moreinfo
>
> Hi Jakob,
>
> Could you please check whether the bug persists in version 6.0.4-2 of the
> package?
>
> Thanks,
>
> Rafael
>
> * Jakob Wiedner  [2015-06-27 14:04]:
>
>> Package: praat
>> Version: 5.4.0-1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> when playing back a sound file (i tried wav and mp3) in the View/Edit
>> window there is a considerable delay of several seconds. After 2nd or 3rd
>> time the delay disappears and it works fine for several times. Rondomly
>> after 10-20 times, praat freezes entirely and can just be closed by killing
>> it.
>>
>> Terminal output as follows:
>>
>> FIRST PLAYBACK: ALSA lib pcm_dsnoop.c:618:(snd_pcm_dsnoop_open) unable to
>> open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
>> ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA
>> lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA
>> lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib
>> pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib
>> pcm.c:7843:(snd_pcm_recover) underrun occurred ALSA lib
>> pcm.c:7843:(snd_pcm_recover) underrun occurred SECOND PLAYBACK: ALSA lib
>> pcm.c:7843:(snd_pcm_recover) underrun occurred ALSA lib
>> pcm.c:7843:(snd_pcm_recover) underrun occurred
>>
>> After that no more delays when playback immediately after.
>>
>>
>>
>> -- System Information: Debian Release: 8.1  APT prefers stable  APT
>> policy: (500, 'stable') 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: systemd (via /run/systemd/system)
>>
>> Versions of packages praat depends on: ii  libasound2   1.0.28-1
>> ii  libatk1.0-0  2.14.0-1 ii  libc62.19-18 ii
>> libcairo21.14.0-2.1 ii  libfontconfig1   2.11.0-6.3 ii
>> libfreetype6 2.5.2-3 ii  libgcc1  1:4.9.2-10 ii
>> libgdk-pixbuf2.0-0   2.31.1-2+b1 ii  libglib2.0-0 2.42.1-1 ii
>> libgtk2.0-0  2.24.25-3 ii  libpango-1.0-0   1.36.8-3 ii
>> libpangocairo-1.0-0  1.36.8-3 ii  libpangoft2-1.0-01.36.8-3 ii
>> libstdc++6   4.9.2-10 ii  oss-compat   6 ii  python
>> 2.7.9-1
>>
>> Versions of packages praat recommends: ii  xfonts-100dpi
>> 1:1.0.3 ii  xfonts-100dpi-transcoded  1:1.0.3 ii  xfonts-75dpi
>> 1:1.0.3 ii  xfonts-75dpi-transcoded   1:1.0.3
>>
>> praat suggests no packages.
>>
>> -- no debconf information
>>
>
> --
> To unsubscribe, send mail to 790120-unsubscr...@bugs.debian.org.

Bug#804633: npm: Please update npm to v3.x.x, at least for sid.

[Zane Tu]

Package: npm
Version: 1.4.21+ds-2
Severity: wishlist

Dear Maintainer,

It's been more than a year since this package was last updated. Now the lastest
version is v3.4.0 and even v2.x.x can cause problems (eg
https://github.com/feross/webtorrent/issues/481#issuecomment-155241196). Please
update it at your earliest convenience.

Regards,
Zane



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

Kernel: Linux 3.14-2-amd64 (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 npm depends on:
ii  node-abbrev   1.0.5-2
ii  node-ansi 0.3.0-2
ii  node-ansi-color-table 1.0.0-1
ii  node-archy0.0.2-1
ii  node-block-stream 0.0.7-1
ii  node-fstream  0.1.24-1
ii  node-fstream-ignore   0.0.6-2
ii  node-github-url-from-git  1.1.1-1
ii  node-glob 4.0.5-1
ii  node-graceful-fs  3.0.2-1
ii  node-gyp  3.0.3-2
ii  node-inherits 2.0.1-3
ii  node-ini  1.1.0-1
ii  node-lockfile 0.4.1-1
ii  node-lru-cache2.3.1-1
ii  node-minimatch1.0.0-1
ii  node-mkdirp   0.5.0-1
ii  node-nopt 3.0.1-1
ii  node-npmlog   0.0.4-1
ii  node-once 1.1.1-1
ii  node-osenv0.1.0-1
ii  node-read 1.0.5-1
ii  node-read-package-json1.2.4-1
ii  node-request  2.26.1-1
ii  node-retry0.6.0-1
ii  node-rimraf   2.2.8-1
ii  node-semver   2.1.0-2
ii  node-sha  1.2.3-1
ii  node-slide1.1.4-1
ii  node-tar  1.0.3-2
ii  node-underscore   1.7.0~dfsg-1
ii  node-which1.0.5-2
ii  nodejs4.2.2~dfsg-1+b1

npm recommends no packages.

npm suggests no packages.