Bug#830751: supertuxkart-data: contains Ubuntu Font Family fonts

[Vincent Cheng]

Package: supertuxkart-data
Version: 0.9.2-1
Severity: serious
Justification: non DFSG file in the source package

supertuxkart/0.9.2-1 ships with the following files in the source tarball:

data/ttf/Ubuntu-B.ttf
data/ttf/Ubuntu-R.ttf

...which get installed into binary package supertuxkart-data:

/usr/share/games/supertuxkart/data/ttf/Ubuntu-B.ttf
/usr/share/games/supertuxkart/data/ttf/Ubuntu-R.ttf

These ttf files are Ubuntu Font Family fonts, which are not
DFSG-compatible as per ftpmasters' decision [1], with rationale
provided at [2]; further discussion can be found at [3]. These fonts
files will need to be replaced in Debian; I intend to also forward
this bug report upstream.

Regards,
Vincent

[1] 
http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/2011-April/006515.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603157#30
[3] https://bugs.launchpad.net/ubuntu-font-licence/+bug/769874

Bug#830750: photofloat: traceback on run

[Mark Eichin]

Package: photofloat
Version: 0~20120917+dfsg-3
Severity: normal

Tried a run based on the instructions in /usr/share/doc/photofloat/README.Debian

$ mkdir photo
$ cd photo
$ mkdir albums cache
$ ln -s /usr/share/photofloat/web/* .
$ mkdir albums/flickr
$ ln $(kpa-grep --tag flickr) albums/flickr/
$ photofloat albums cache

2016-07-10T20:36:15.950083   |  |--[thumbing]  img_418-0601.jpg -> 1024px
2016-07-10T20:36:16.907571   |--[caching]   flickr
Traceback (most recent call last):
  File "/usr/bin/photofloat", line 21, in 
main()
  File "/usr/bin/photofloat", line 15, in main
TreeWalker(sys.argv[1], sys.argv[2])
  File "/usr/share/photofloat/scanner/TreeWalker.py", line 16, in __init__
self.walk(self.album_path)
  File "/usr/share/photofloat/scanner/TreeWalker.py", line 55, in walk
album.add_album(self.walk(entry))
  File "/usr/share/photofloat/scanner/TreeWalker.py", line 76, in walk
album.cache(self.cache_path)
  File "/usr/share/photofloat/scanner/PhotoAlbum.py", line 68, in cache
self._sort()
  File "/usr/share/photofloat/scanner/PhotoAlbum.py", line 51, in _sort
self._photos.sort()
  File "/usr/share/photofloat/scanner/PhotoAlbum.py", line 318, in __cmp__
date_compare = cmp(self.date, other.date)
TypeError: can't compare datetime.datetime to unicode

Running it again is faster (presumably it's not regenerating the cached
thumbnails, though it still prints all of the names) and ends with the
same traceback.

This appears to have been mentioned, but not responded to, elsewhere:
https://lists.zx2c4.com/pipermail/photofloat/2013-November/28.html
https://lists.zx2c4.com/pipermail/photofloat/2014-January/29.html

with a possible patch:
https://lists.zx2c4.com/pipermail/photofloat/2014-February/42.html
http://lists.zx2c4.com/pipermail/photofloat/attachments/20140207/f14817be/attachment.patch

(It looks like that's followed by release discussion, but just thought
I'd still add the "doesn't work out of the box" data point.)

-- System Information:
Debian Release: 8.5
  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_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages photofloat depends on:
ii  lmodern 2.004.4-5
ii  python-imaging  2.6.1-2+deb8u2
ii  python  2.7.9-1

Versions of packages photofloat recommends:
ii  libjs-jquery 1.7.2+dfsg-3.2
ii  libjs-jquery-mousewheel  10-1

Versions of packages photofloat suggests:
pn  libapache2-mod-php5 | php5-fpm | php5-cgi  
ii  nginx-light [nginx]1.6.2-5+deb8u2+b1

-- no debconf information

Bug#830749: libssw-java: please provide maven artifacts

[tony mancill]

Package: libssw-java
Severity: wishlist
Tags: patch

Dear Maintainer,

Please consider providing maven artifact information with
maven-repo-helper to allow other the maven-based build systems
of other packages that depend upon libssw-java to automatically
resolve dependency information.

The attached patch(es) can be applied with 'git am' accomplish this.
(You can ignore the second patch and modify the debian/changelog as
you deem fit.  Alternately, I can perform an NMU upload if you would
prefer.)

Cheers,
tony
From 959c73dfa0d9dedaf5711179c9b0b5611d9b5e79 Mon Sep 17 00:00:00 2001
From: tony mancill 
Date: Sun, 10 Jul 2016 21:31:25 -0700
Subject: [PATCH 1/2] install maven-repo coordinates for ssw.jar

This commit modifies the package build to use maven-repo-helper
to install a POM file beneath /usr/share/maven-repo/ssw/.
---
 debian/control | 3 ++-
 debian/libssw-java-1.0.pom | 8 
 debian/libssw-java.poms| 1 +
 debian/rules   | 2 +-
 4 files changed, 12 insertions(+), 2 deletions(-)
 create mode 100644 debian/libssw-java-1.0.pom
 create mode 100644 debian/libssw-java.poms

diff --git a/debian/control b/debian/control
index ff3101a..39d5fda 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,8 @@ Build-Depends: debhelper (>= 9),
javahelper,
dh-autoreconf,
help2man,
-   zlib1g-dev
+   zlib1g-dev,
+   maven-repo-helper
 Standards-Version: 3.9.8
 Testsuite: autopkgtest
 Vcs-Browser: https://anonscm.debian.org/cgit/debian-med/libssw.git
diff --git a/debian/libssw-java-1.0.pom b/debian/libssw-java-1.0.pom
new file mode 100644
index 000..0ddf236
--- /dev/null
+++ b/debian/libssw-java-1.0.pom
@@ -0,0 +1,8 @@
+
+http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; xmlns="http://maven.apache.org/POM/4.0.0;
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
+  4.0.0
+  ssw
+  ssw
+  1.0
+
diff --git a/debian/libssw-java.poms b/debian/libssw-java.poms
new file mode 100644
index 000..1c02394
--- /dev/null
+++ b/debian/libssw-java.poms
@@ -0,0 +1 @@
+debian/libssw-java-1.0.pom --usj-name=ssw
diff --git a/debian/rules b/debian/rules
index 9ba2f1a..6ba50ff 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,7 +6,7 @@ DEBVERS := $(shell dpkg-parsechangelog | sed -n -e 's/^Version: //p')
 PKG_VERSION := $(shell echo '$(DEBVERS)' | sed -e 's/^[[:digit:]]*://' -e 's/-.*//')
 
 %:
-	dh $@
+	dh $@ --with javahelper --with jh_maven_repo_helper
 
 override_dh_auto_clean:
 	rm -f debian/libssw*install debian/libssw*links debian/ssw-align.1
-- 
2.8.1

From ef80ee0a8ce9e908aeba1ca883ddebce28671e8c Mon Sep 17 00:00:00 2001
From: tony mancill 
Date: Sun, 10 Jul 2016 21:33:15 -0700
Subject: [PATCH 2/2] interim changelog

---
 debian/changelog | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index c6e8aa1..19a1d56 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+libssw (1.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install maven-repo artifacts.
+- Build-depend on maven-repo-helper
+- Add debian/libssw-java-1.0.pom and debian/libssw-java.poms
+- Update debian/rules to build with jh_maven_repo_helper
+
+ -- tony mancill   Sun, 10 Jul 2016 21:07:21 -0700
+
 libssw (1.0-2) unstable; urgency=medium
 
   * adjust list of architectures to only include SSE2 capable ones
-- 
2.8.1



signature.asc
Description: PGP signature

Bug#830748: supertuxkart: FTBFS on arm64, mips/mips64/mipsel, ppc64el, s390x

[Vincent Cheng]

Package: supertuxkart
Version: 0.9.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

supertuxkart/0.9.2-1 FTBFS on arm64, mips/mips64/mipsel, ppc64el, and
s390x; full build log at [1], and here's the relevant part of the log:

[  9%] Building CXX object
lib/irrlicht/CMakeFiles/stkirrlicht.dir/source/Irrlicht/CGUIMeshViewer.cpp.o
cd /«PKGBUILDDIR»/obj-aarch64-linux-gnu/lib/irrlicht && /usr/bin/c++
-DGLEW_NO_GLU -DIRRLICHT_EXPORTS=1 -DNDEBUG=1
-DNO_IRR_LINUX_X11_VIDMODE_ -DPNG_NO_MMX_CODE -DPNG_NO_MNG_FEATURES
-DPNG_THREAD_UNSAFE_OK -D_IRR_LINUX_X11_RANDR_
-I/«PKGBUILDDIR»/lib/bullet/src -I/«PKGBUILDDIR»/lib/glew/include
-I/«PKGBUILDDIR»/lib/irrlicht/include  -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
-Wall -pipe -O3  -fno-exceptions  -fstrict-aliasing
-I/usr/X11R6/include -Wall -pipe -O3  -fno-exceptions
-fstrict-aliasing -I/usr/X11R6/include -fexpensive-optimizations -O2
-DNDEBUG   -o CMakeFiles/stkirrlicht.dir/source/Irrlicht/CGUIMeshViewer.cpp.o
-c /«PKGBUILDDIR»/lib/irrlicht/source/Irrlicht/CGUIMeshViewer.cpp
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp: In
function 'asQWORD X64_CallFunction(const asQWORD*, int, funcptr_t,
asQWORD&, bool)':
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%rcx' in 'asm'
 "%rdi", "%rsi", "%rax", "%rdx", "%rcx", "%r8", "%r9", "%r10",
"%r11", "%r15");

   ^
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%rdx' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%rax' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%rsi' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%rdi' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm7' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm6' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm5' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm4' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm3' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm2' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm1' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm0' in 'asm'


It looks like angelscript is misdetecting certain architectures as x86
and hence applying the wrong assembly directives. It's worth checking
first to see if there's a fix for this in upstream angelscript before
fixing it in supertuxkart. I'll take a look at this when I have time,
but help is greatly appreciated if someone has a chance to tackle this
before I do.

Regards,
Vincent

[1] https://buildd.debian.org/status/package.php?p=supertuxkart=unstable

Bug#827423: marked as pending

[Sven Joachim]

Control: found -1 2:3.3.12-1
Control: tags -1 + patch

On 2016-07-02 02:01 +, Craig Small wrote:

> tag 827423 pending
> thanks
>
> Hello,
>
> Bug #827423 reported by you has been fixed in the Git repository. You can
> see the changelog below, and you can check the diff of the fix at:
>
> http://git.debian.org/?p=collab-maint/procps.git;a=commitdiff;h=470320f
>
> ---
> commit 470320fc76a7c278ead02d1900f92f73740bafd9
> Author: Craig Small 
> Date:   Sat Jul 2 11:59:12 2016 +1000
>
> Dont run init on install
> 
> Sometimes on install or upgrade the sysctl part fails. The kernel
> variable should be installed at startup time, not some arbitarily
> time afterwards (and over and over).
> 
> Closes: #827423

Unfortunately this fix does not work, since there was already an
existing override for dh_installinit which overrides (no pun intended)
the one you committed here.  Seen on the build logs:

,
| debian/rules:98: warning: overriding recipe for target 
'override_dh_installinit'
| debian/rules:54: warning: ignoring old recipe for target 
'override_dh_installinit'
`

Here is a patch to remove the second override.  I think it does not
matter whether dh runs dh_installinit on non-Linux architectures since
there is no init script there anyway, so it's a no-op.

--8<---cut here---start->8---
diff --git a/debian/rules b/debian/rules
index 944809f..0534f9d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -93,11 +93,6 @@ endif
 override_dh_installchangelogs:
dh_installchangelogs NEWS
 
-override_dh_installinit:
-ifeq ($(DEB_HOST_ARCH_OS), linux)
-   dh_installinit 
-endif
-
 override_dh_makeshlibs:
dh_makeshlibs -V 'libprocps6'
 
--8<---cut here---end--->8---

Cheers,
   Sven

Bug#830614: docker-compose: New version

[Felipe Sateler]

On 9 July 2016 at 14:39, Joern Heissler  wrote:
> Package: docker-compose
> Version: 1.5.2-1
> Severity: normal
>
> Hi,
> I would like to use the new config syntax (Version 2) of docker-compose, but
> documentation says it's only available since version 1.6.0+.
> Could you please upload a new release?
>
> https://github.com/docker/compose/releases

I'm waiting for a new upstream release of python-docker to be uploaded
to debian[1], as the new version requires the new python-docker. After
that I should be able to upload the new version.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830172

-- 
Saludos,
Felipe Sateler

Bug#830683: Missing dependency on module-udev?

[Felipe Sateler]

On 10 July 2016 at 17:22, Patrick Winnertz  wrote:
>
> thanks
>
> I know that this split was done by purpose. However even if the split was
> done on purpose, this split shouldn't break existing systems - which
> actually happened.
> It would be nice if you wouldn't close the bug without
> actually thinking about a solution for this problem, as this will lead for
> sure to problems during dist-upgrade later on.

Do you have disabled installation of Recommends?

-- 

Saludos,
Felipe Sateler

Bug#830747: RM: golang-github-cheggaaa-pb -- ROM; superseded by golang-gopkg-cheggaaa-pb.v1

[Peter Colberg]

Package: ftp.debian.org
Severity: normal

Dear ftpmasters,

On behalf of the Debian Go Packaging Team (Cc'd), I am requesting
the removal of the source package golang-github-cheggaaa-pb from
unstable. This package has been renamed to follow the Debian golang
naming policy and is superseded by golang-gopkg-cheggaaa-pb.v1.

https://bugs.debian.org/824601

The only package with a dependency on golang-github-cheggaaa-pb-dev
was etcd, which has been resolved by removing the dependency.

https://bugs.debian.org/829048

Regards,
Peter


signature.asc
Description: PGP signature

Bug#830746: jaligner: please provide maven coordinates

[tony mancill]

Package: jaligner
Severity: wishlist
Tags: patch

Dear Debian Med Team,

Please consider providing maven artifact information with
maven-repo-helper to allow other the maven-based build systems
of other packages that depend upon jaligner to automatically resolve
dependency information.

The attached patch(es) can be applied with 'git am' accomplish this.
(You can ignore the second patch and modify the debian/changelog as
you deem fit.  Alternately, I can perform an NMU upload if you would
prefer.)

NB: The mhap pom.xml refers to jaligner with groupId 'com.jaligner'.
However, the groupId for jaligner should simply be 'jaligner',
which corresponds to the actual classpath (and is how others [1]
resolve it).  Therefore, the mhap source package should be modified
to auto-resolve jaligner by adding the following to debian/maven.rules:

   s/com.jaligner/jaligner/ jaligner * * * *

Cheers,
tony
From a300a8975fc2c8dae8240bcce9b505b337fd001d Mon Sep 17 00:00:00 2001
From: tony mancill 
Date: Sun, 10 Jul 2016 18:28:59 -0700
Subject: [PATCH 1/2] install maven coordinates for jaligner.jar

This commit modifies the package build to use maven-repo-helper
to install a POM file beneath /usr/share/maven-repo/jaligner/.
---
 debian/control  | 3 ++-
 debian/jaligner-1.0.pom | 8 
 debian/jaligner.poms| 1 +
 debian/rules| 2 +-
 4 files changed, 12 insertions(+), 2 deletions(-)
 create mode 100644 debian/jaligner-1.0.pom
 create mode 100644 debian/jaligner.poms

diff --git a/debian/control b/debian/control
index 70175bc..21d762f 100644
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,8 @@ Build-Depends: debhelper (>= 9),
 Build-Depends-Indep: junit4,
  javahelper,
  icedtea-netx-common,
- asciidoctor
+ asciidoctor,
+ maven-repo-helper
 Standards-Version: 3.9.8
 Vcs-Browser: https://anonscm.debian.org/cgit/debian-med/jaligner.git
 Vcs-Git: https://anonscm.debian.org/git/debian-med/jaligner.git
diff --git a/debian/jaligner-1.0.pom b/debian/jaligner-1.0.pom
new file mode 100644
index 000..2e3bd6a
--- /dev/null
+++ b/debian/jaligner-1.0.pom
@@ -0,0 +1,8 @@
+
+http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; xmlns="http://maven.apache.org/POM/4.0.0;
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
+  4.0.0
+  jaligner
+  jaligner
+  1.0
+
diff --git a/debian/jaligner.poms b/debian/jaligner.poms
new file mode 100644
index 000..04220ac
--- /dev/null
+++ b/debian/jaligner.poms
@@ -0,0 +1 @@
+debian/jaligner-1.0.pom --usj-name=jaligner
diff --git a/debian/rules b/debian/rules
index 844b6be..054ed1c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -7,7 +7,7 @@
 export CLASSPATH=/usr/share/icedtea-web/netx.jar
 
 %:
-	dh $@ --with javahelper
+	dh $@ --with javahelper --with jh_maven_repo_helper
 
 override_dh_auto_build:
 	#cp -a debian/images/*.gif src/jaligner/ui/images/gifs
-- 
2.8.1

From 8de1687c08982ba1867bad8610fd4d37b8b3c124 Mon Sep 17 00:00:00 2001
From: tony mancill 
Date: Sun, 10 Jul 2016 18:29:20 -0700
Subject: [PATCH 2/2] interim changelog

---
 debian/changelog | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index a2b3cf3..e11014f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+jaligner (1.0+dfsg-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add maven coordinates:
+- Add build-dependency upon maven-repo-helper
+- Add debian/jaligner.pom
+- Update debian/rules to build with jh_maven_repo_helper
+
+ -- tony mancill   Sun, 10 Jul 2016 18:23:34 -0700
+
 jaligner (1.0+dfsg-3) unstable; urgency=medium
 
   * flip the reproducible switch for asciidoctor
-- 
2.8.1



signature.asc
Description: PGP signature

Bug#829617: [DSE-Dev] Bug#829617: selinux-policy-default not available for stable

[Russell Coker]

We can backport the POLICY from the latest refpolicy package with the hooks for 
the versions of the tools in Jessie.

What's the procedure for getting this done? I can easily build the package in 
question as I have it running on all my own servers.

On 5 July 2016 7:24:45 PM AEST, Laurent Bigonville  wrote:
>severity 829617 wishlist
>tag 829617 + jessie
>thanks
>
>Le 04/07/16 à 20:37, Klaus Ethgen a écrit :
>> selinux-policy-default is not available for stable (jessie) than only
>> for old-stable and testing (and unstable).
>
>Yes the policy was considered too buggy when stable has been released 
>and thus has been removed.
>
>We could backport the refpolicy currently in testing, but we might need
>
>to backport the userspace as well as they changed the way the policy
>was 
>loaded.
>
>
>> Without this policy, all selinux tools and kernel support makes no
>sense
>> at all. (True, I can compile my own policy but this is fare behind a
>> casual admin.)
>
>TBH, even with a policy in the archive, I think it would require 
>adjustment from the administrator anyway
>
>>
>> So please provide that policy again.
>>
>> See also [0].
>>
>> [0] https://wiki.debian.org/SELinux/Setup#Steps_to_setup_SELinux
>
>___
>SELinux-devel mailing list
>selinux-de...@lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/selinux-devel

-- 
Sent from my Nexus 6P with K-9 Mail.

Bug#829302: dh-golang: Respect "--parallel" and "--max-parallel" options

[Michael Hudson-Doyle]

On 9 July 2016 at 13:32, Dmitry Smirnov  wrote:
> On Friday, 8 July 2016 3:39:54 PM AEST Michael Hudson-Doyle wrote:
>> I haven't tried it properly, but does this not limit the parallelism
>> and slow builds by default?
>
> Yes it does. Parallel build should be explicitly enabled by "--parallel"
> passed to DH. I think we should make this change in order to make build
> system consistent.
> Most packages would build marginally slower by default.
> For few others it is not hard to add "--parallel" to "debian/rules".
>
> Arguably ignoring parallel build options is a bug. dh-golang should have
> respected debhelper options from very beginning so I'm not too concerned
> about behaviour change. After all there will be a note in changelog about it
> and if you think it is not enough then we can even add a NEWS file.
>
>
>> (I don't know how this works and
>> apparently have not got around to reading up on it in the week since
>> the bug was filed, so I'll ask a potentially silly question)
>
> Debhelper takes care of parsing "--parallel" and "--max-parallel" so we just
> need to take value returned by "get_parallel()" and convert it into
> parameters to "go build" and to "go test" (I've forgotten to include similar
> change to "test()" function).

Makes sense to me. Feel free to commit and upload as far as I'm concerned.

Cheers,
mwh

Bug#829654: src:fcgiwrap: Co-maintaining fcgiwrap

[Peter Colberg]

On Mon, Jul 11, 2016 at 02:51:00AM +0200, Jordi Mallach wrote:
> Ok. Any pointer where I should be advocating you?

In fact you do not need to do anything regarding collab-maint.

I found the instructions: DMs can apply on their own with a signed mail.

https://wiki.debian.org/Alioth/PackagingProject#Collaborative_maintenance_of_a_single_package

Peter


signature.asc
Description: PGP signature

Bug#830472: postal: FTBFS: smtp.h:28:58: error: 'hash' was not declared in this scope

[Logan Rosen]

Package: postal
Version: 0.74
Followup-For: Bug #830472
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

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

  * Fix FTBFS:
- smtp.h:
  + Qualify std::tr1::hash.
  + Include .
  + Use rand() instead of random().
- postal.cpp: Include .
- bhmusers.h: Qualify std::tr1::hash.
- bhmusers.cpp: Include .
- bhm.cpp: Include .

Thanks for considering the patch.

Logan Rosen

-- 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.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru postal-0.74/bhm.cpp postal-0.74ubuntu1/bhm.cpp
--- postal-0.74/bhm.cpp	2016-06-30 05:04:24.0 -0400
+++ postal-0.74ubuntu1/bhm.cpp	2016-07-10 20:47:47.0 -0400
@@ -14,6 +14,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include "postal.h"
 #include "logit.h"
diff -Nru postal-0.74/bhmusers.cpp postal-0.74ubuntu1/bhmusers.cpp
--- postal-0.74/bhmusers.cpp	2008-04-09 21:36:27.0 -0400
+++ postal-0.74ubuntu1/bhmusers.cpp	2016-07-10 20:44:21.0 -0400
@@ -2,6 +2,7 @@
 #include 
 #include 
 #include "expand.h"
+#include 
 
 BHMUsers::BHMUsers(const char *userListFile)
 {
diff -Nru postal-0.74/bhmusers.h postal-0.74ubuntu1/bhmusers.h
--- postal-0.74/bhmusers.h	2016-06-30 04:57:25.0 -0400
+++ postal-0.74ubuntu1/bhmusers.h	2016-07-10 20:43:48.0 -0400
@@ -18,7 +18,7 @@
   int sync_time;
 } BHM_DATA;
 
-typedef std::tr1::unordered_map NAME_MAP;
+typedef std::tr1::unordered_map NAME_MAP;
 
 class BHMUsers
 {
diff -Nru postal-0.74/changes.txt postal-0.74ubuntu1/changes.txt
--- postal-0.74/changes.txt	2016-06-30 05:04:53.0 -0400
+++ postal-0.74ubuntu1/changes.txt	2016-07-10 20:53:58.0 -0400
@@ -1,3 +1,17 @@
+postal (0.74ubuntu1) yakkety; urgency=medium
+
+  * Fix FTBFS:
+- smtp.h:
+  + Qualify std::tr1::hash.
+  + Include .
+  + Use rand() instead of random().
+- postal.cpp: Include .
+- bhmusers.h: Qualify std::tr1::hash.
+- bhmusers.cpp: Include .
+- bhm.cpp: Include .
+
+ -- Logan Rosen   Sun, 10 Jul 2016 20:29:41 -0400
+
 postal (0.74) unstable; urgency=medium
 
   * Add -b option to bind to an address to bhm
diff -Nru postal-0.74/postal.cpp postal-0.74ubuntu1/postal.cpp
--- postal-0.74/postal.cpp	2014-08-18 13:24:20.0 -0400
+++ postal-0.74ubuntu1/postal.cpp	2016-07-10 20:41:32.0 -0400
@@ -10,6 +10,7 @@
 #include 
 #include "postal.h"
 #include "logit.h"
+#include 
 #ifdef USE_GNUTLS
 #include 
 #if GNUTLS_VERSION_NUMBER <= 0x020b00
diff -Nru postal-0.74/smtp.cpp postal-0.74ubuntu1/smtp.cpp
--- postal-0.74/smtp.cpp	2016-06-30 04:11:35.0 -0400
+++ postal-0.74ubuntu1/smtp.cpp	2016-07-10 20:39:42.0 -0400
@@ -9,6 +9,7 @@
 #include "logit.h"
 #include "results.h"
 #include 
+#include 
 
 smtpData::smtpData()
  : m_quit("QUIT\r\n")
@@ -66,7 +67,7 @@
 return;
 
   for(int i = 0; i < MAP_SIZE; i++)
-m_randBuf[i] = m_randomLetters[random() % m_randomLen];
+m_randBuf[i] = m_randomLetters[rand() % m_randomLen];
   m_timeLastAction = time(NULL);
 }
 
@@ -76,7 +77,7 @@
 return;
   if(len > 2)
   {
-int offset = random() % (MAP_SIZE - (len - 2));
+int offset = rand() % (MAP_SIZE - (len - 2));
 memcpy(buf, _randBuf[offset], len - 2);
   }
   strcpy(buf + len - 2, "\r\n");
@@ -88,7 +89,7 @@
 {
   while(len)
   {
-int line_len = random() % max_line_len;
+int line_len = rand() % max_line_len;
 if(line_len < 2)
   line_len = 2;
 if(len - line_len < 2)
@@ -106,7 +107,7 @@
   time_t t = time(NULL);
   struct tm broken;
 
-  t += 60 - random() % 600;
+  t += 60 - rand() % 600;
 
   if(!gmtime_r(, ) || !strftime(buf, 34, "%a, %d %b %Y %H:%M:%S %z\r\n", ))
 strcpy(buf, "Error making date");
@@ -161,7 +162,7 @@
   else if(m_msgsPerConnection < 0)
 msgs = 0;
   else
-msgs = random() % m_msgsPerConnection + 1;
+msgs = rand() % m_msgsPerConnection + 1;
 
   if(rc)
 msgs = 0;
@@ -285,7 +286,7 @@
   int rc;
   int size = 0;
   if(m_maxMsgSize > m_minMsgSize)
-size = random() % (m_maxMsgSize - m_minMsgSize) + m_minMsgSize;
+size = rand() % (m_maxMsgSize - m_minMsgSize) + m_minMsgSize;
   else
 size = m_maxMsgSize;
   m_md5.init();
@@ -318,7 +319,7 @@
 subject += " ";
   char subj_buf[61];
   // random string from 2 to buffer len
-  int subj_len = random() % (sizeof(subj_buf) - 3) + 2;
+  int subj_len = rand() % (sizeof(subj_buf) - 3) + 2;
   

Bug#826838:

[Marlin Cremers]

Control: owner -1 !
Control: retitle -1 ITP: ipsilon -- Identity Provider server and toolkit

I've been working on this package over at
https://mentors.debian.net/package/ipsilon.

Met vriendelijke groet,

Marlin Cremers

*Chief Technical Officer*

[ Hert 3a, 5991PA Baarlo
[ +31 (0)77 369 0513

Bug#820235: RM: softhsm -- ROM; superseded by softhsm2

[Andreas Beckmann]

Control: tag -1 - moreinfo

On Sat, 09 Apr 2016 00:57:22 -0400 Scott Kitterman 
wrote:
> Please remove the moreinfo tag once the two blocking bugs have been resolved.

That has happened in the meantime.


Andreas

Bug#829654: src:fcgiwrap: Co-maintaining fcgiwrap

[Jordi Mallach]

Hi Peter,

On Sat, Jul 09, 2016 at 11:53:21PM -0400, Peter Colberg wrote:
> Hi Jordi,
> 
> On Wed, Jul 06, 2016 at 09:18:49AM +0200, Jordi Mallach wrote:
> > This is all good news! I still use fcgiwrap myself so co-maintaining
> > sounds about right (although I'm happy to downgrade myself to Uploader
> > and have you as the main Maintainer if you want).
> 
> Great! I would be fine either way, but Maintainer might be better for
> the sake of hinting (when the time comes) that I am ready to become DD.
> 
> > Also happy about svn → git, it's something that's been on the list for
> > all of my packages but I've never come around to it.
> 
> Please take a close look at the carefully restored history:
> 
> git clone https://anonscm.debian.org/git/users/pc-guest/fcgiwrap.git
> 
> I have split the larger svn commits into multiple git commits so that
> each commit corresponds to one changelog entry. I verified that the
> debian/ tags match exactly the versions in snapshot.debian.org.

Woa, you've spent quite a bit doing this right? I can't spot a single
nitpick here. Nice!

> Would you be fine if we generate the changelog using "gbp dch" only
> right before each upload? This keeps the history simple and avoids
> potential merge conflicts in the changelog.

Yeah, that's fine. Whatever, if it's the recommended way in DEP14. As
in this case there's no strong recommendation, I can be convinced to do
gbp dch. I really hope I won't forget, as editing the changelog has been
part of my workflow for 15+ years. :)

> > I can give you the DM upload permissions straight away; I'm very happy
> > about you joining and caring about fcgiwrap!
> 
> Yes, that would be nice.
> 
> Could you also advocate for me to join collab-maint? I sent a request
> myself on alioth, but so far my account (pc-guest) has not been added.

Ok. Any pointer where I should be advocating you?

> That would be my next step after uploading the current version. I will
> see how to best integrate our patches and file pull requests upstream.
> 
> There is an open pull request [1] for a multi-instance systemd unit,
> which would allow running fcgiwrap under multiple users using the same
> systemd template, instead of running everything under www-data. In
> case of a serious bug in one CGI app, this separation prevents the
> hijacking of other CGI apps or the webserver itself.

That sounds useful, yes!

> [1] https://github.com/gnosek/fcgiwrap/pull/17

Jordi

-- 
Jordi Mallach Pérez  --  Debian developer http://www.debian.org/
jo...@sindominio.net jo...@debian.org http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/


signature.asc
Description: PGP signature

Bug#830745: vlc: Freeze after the end of a video when the file is not here anymore and repeat is enabled

[Léo Andrès]

Package: vlc
Version: 1:2.2.4-dmo1
Severity: normal
Tags: upstream

Dear Maintainer,

When downloading a video, I had a foo.flv file, which stays empty until
the
download is done ; and a foo.flv.part file, in which the video is
stored until
the download is done, then it's moved to foo.flv and deleted.

As I didn't want to wait until the end of the download, I open the
foo.flv.part
file with vlc. The video plays correctly.

Unfortunately, at the end of the video, if the "repeat" function is
enabled in
vlc, vlc will freeze: I have to reboot the system the hard way.

I guess vlc tries to load the file foo.flv.part which is not here
anymore.

The correct behavior should be vlc not trying to load the file if it's
not here
anymore - or looking for foo.flv if the file is named foo.flv.part, but
IMHO
it's not the best thing to do.

Cheers,



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

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 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 vlc depends on:
ii  dpkg    1.18.7
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libavcodec57    10:3.0.2-dmo2
ii  libavutil55 10:3.0.2-dmo2
ii  libc6   2.22-12
ii  libcaca0    0.99.beta19-2+b1
ii  libegl1-mesa [libegl1-x11]  11.2.2-1
ii  libfreerdp-client1.1    1.1.0~git20140921.1.440916e+dfsg1-10
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-10
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-10
ii  libfreetype6    2.6.3-3+b1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:6.1.1-7
ii  libgl1-mesa-glx [libgl1]    11.2.2-1
ii  libpulse0   8.0-2+b2
ii  libqtcore4  4:4.8.7+dfsg-8
ii  libqtgui4   4:4.8.7+dfsg-8
ii  libsdl-image1.2 1.2.12-5+b6
ii  libsdl1.2debian 1.2.15+dfsg1-4
ii  libstdc++6  6.1.1-7
ii  libva-drm1  1.7.1-1
ii  libva-x11-1 1.7.1-1
ii  libva1  1.7.1-1
ii  libvlccore8 1:2.2.4-dmo1
ii  libvncclient1   0.9.10+dfsg-3+b1
ii  libx11-6    2:1.6.3-1
ii  libxcb-composite0   1.11.1-1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.11.1-1
ii  libxcb-shm0 1.11.1-1
ii  libxcb-xv0  1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxext6    2:1.3.3-1
ii  libxinerama1    2:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 1:2.2.4-dmo1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  1:2.2.4-dmo1
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

-- no debconf information

-- 



Léo ANDRÈS


4, route de la CuréeHameau de Pilvernier77570, Mondreville
Tél. +33 (0) 6 45 96 43 45
E-Mail: l...@ndrs.fr
Web-site: www.ndrs.fr
GitHub: zapashcanon


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

Bug#830742: src:fcgiwrap: Relicense Debian packaging to allow upstreaming of patches

[Jordi Mallach]

On Sun, Jul 10, 2016 at 06:46:36PM -0400, Peter Colberg wrote:
> Package: src:fcgiwrap
> Version: 1.1.0-6
> Severity: wishlist
> 
> Hi Jordi, hi Sergio,
> 
> The Debian packaging is currently licensed under GPL version 3 with
> you as the copyright holders. This is a perfectly fine choice, but
> usually the Debian packaging is licensed under the same terms as the
> upstream software, which in this case is the Expat license.
> 
> Would you agree to relicense the Debian packaging for fcgiwrap to the
> Expat license? This will allow us to submit Debian patches upstream.

Oops. Yes, no objection.

Jordi
-- 
Jordi Mallach Pérez  --  Debian developer http://www.debian.org/
jo...@sindominio.net jo...@debian.org http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/


signature.asc
Description: PGP signature

Bug#826838:

[Marlin Cremers]

I'm currently working on a Ipsilon package for Debian.

Met vriendelijke groet,

Marlin Cremers

*Chief Technical Officer*

[ Hert 3a, 5991PA Baarlo
[ +31 (0)77 369 0513

Bug#830744: flint: FTBFS on *-i386: testsuite timeout

[Andreas Beckmann]

Source: flint
Version: 2.5.2-7
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

flint FTBFS on *-i386, the testsuite hangs and the build gets terminated
after it reaches the inactivity timeout.

https://buildd.debian.org/status/fetch.php?pkg=flint=i386=2.5.2-7=1467982677

make[3]: Entering directory '/«PKGBUILDDIR»/d_mat'
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-mul_classical.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-mul_classical 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF 
../build/d_mat/test/t-mul_classical.d -MT "../build/d_mat/test/t-mul_classical" 
-MT "../build/d_mat/test/t-mul_classical.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-qr.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-qr 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-qr.d -MT 
"../build/d_mat/test/t-qr" -MT "../build/d_mat/test/t-qr.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-is_empty.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-is_empty 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-is_empty.d 
-MT "../build/d_mat/test/t-is_empty" -MT "../build/d_mat/test/t-is_empty.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-is_square.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-is_square 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF 
../build/d_mat/test/t-is_square.d -MT "../build/d_mat/test/t-is_square" -MT 
"../build/d_mat/test/t-is_square.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-init_clear.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-init_clear 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF 
../build/d_mat/test/t-init_clear.d -MT "../build/d_mat/test/t-init_clear" -MT 
"../build/d_mat/test/t-init_clear.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-zero.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-zero 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-zero.d -MT 
"../build/d_mat/test/t-zero" -MT "../build/d_mat/test/t-zero.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-entry.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-entry 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-entry.d 
-MT "../build/d_mat/test/t-entry" -MT "../build/d_mat/test/t-entry.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-equal.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-equal 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-equal.d 
-MT "../build/d_mat/test/t-equal" -MT "../build/d_mat/test/t-equal.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-one.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-one 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF ../build/d_mat/test/t-one.d -MT 
"../build/d_mat/test/t-one" -MT "../build/d_mat/test/t-one.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-transpose.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-transpose 
-L/«PKGBUILDDIR» -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lflint 
-lmpfr -lgmp -lm -lntl -lpthread  -MMD -MP -MF 
../build/d_mat/test/t-transpose.d -MT "../build/d_mat/test/t-transpose" -MT 
"../build/d_mat/test/t-transpose.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -I/«PKGBUILDDIR» test/t-gso.c 
../build/d_mat/../../test_helpers.o -o ../build/d_mat/test/t-gso 
-L/«PKGBUILDDIR» -L/usr/local/lib 

Bug#830209: [pkg-go] Bugs: "accesses the internet during build" -- strongly disagree on severity

[Dmitry Smirnov]

On Sunday, 10 July 2016 11:28:07 AM AEST Chris Lamb wrote:
> Severity: serious
> Justification: Policy 4.9
> User: la...@debian.org
> Usertags: network-access

Hi Chris,

Thank you for submitting those bugs. I agree that it is a legitimate problem 
that needs addressing. However I strongly disagree with severity of those 
bugs. Obviously packages should not download anything during build for 
security and reproducibility reasons. But here post-build tests attempt to 
access internet which is relatively harmless in this context. Indeed tests 
trying to access internet from offline environment is hardly a "serious" 
problem regardless of what policy says.
Thanks to your bug reports we will eventually address and fix those problems. 
In the mean time this should not block testing migrations so I'm lowering 
severity of those bugs and I recommend submitting similar bugs with severity 
not higher than "important".

-- 
All the best,
 Dmitry Smirnov.

---

The most fatal blow to progress is slavery of the intellect. The most
sacred right of humanity is the right to think, and next to the right to
think is the right to express that thought without fear.
-- Helen H. Gardner, "Men, Women and Gods"


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

Bug#819703: SV: Blessing!‏

[Anders Olausson]

Från: Anders Olausson
Skickat: den 11 juli 2016 00:37
Till: Anders Olausson
Ämne: Blessing!‏

I, Liliane Donated 2,000,000 Dollars to you, Contact me on ( 
lbetten...@outlook.pt ) for more details.

Bug#827669: Confusion with minetest-mod-mobf

[Markus Koschany]

On 09.07.2016 12:08, Julien Puydt wrote:
> Hi,
> 
> according to bug #827669 the current minetest-mod-mobf packaging is
> buggy/incomplete with a debian/ directory shipped within and probably
> missing directories ; in #830493 I pointed out that one of the missing
> directories was really a missing package on which to depend.
> 
> After some more poking around, I found out that in fact the situation is
> worse than what I thought, as what is in minetest-mod-mobf isn't mobf at
> all : it really should be named minetest-mod-animals. We don't ship mobf
> at all in Debian!
> 
> To fix things I propose:
[...]

Hi,

I haven't checked all the information, so here are just a few general
thoughts of mine. I provide my own public minetest server and I'd rather
like to see some kind of modpack (like the most popular mods) in Debian
that is properly maintained upstream instead of many single mod packages
which all need to be touched from time to time. Or a new game mode like
capture the flag:

https://github.com/rubenwardy/capturetheflag

I've made the experience that it is rather simple to create a customized
server with many different mods. For instance I copy everything into

/var/games/minetest-server/worlds/$server_name/world/worldmods

which even overrides default mods. On the other hand a lot of these mods
are in a constant state of flux and some of them can easily crash your
server. Thus I'm currently not up for packaging more minetest mods
because I would rather like to see that the game gets more stabilized
and more focus is put into making it a playable and fun game instead of
just a good engine.


> - here there's a hole in my plan because I think we also need doors,
> fire, vessels and wool -- and I'm not sure where to find those.

These mods are already part of minetest_game and are installed by default.

See

/usr/share/games/minetest/games/minetest_game/mods

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Bug#830733: procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000

[Aaron M. Ucko]

Craig Small  writes:

> Can you apply this patch to your setup and see if it checks? You really
> only need to compile lib/test_strod_nol and run it.

With that patch, it succeeds on 123 but then proceeds to fail on 12.34
in my i386 chroot.  However, it succeeds fully if I add 0.5 before
casting to obtain rounding rather than truncation.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

diff --git a/lib/test_strtod_nol.c b/lib/test_strtod_nol.c
index 0be798c..43265ea 100644
--- a/lib/test_strtod_nol.c
+++ b/lib/test_strtod_nol.c
@@ -33,8 +33,8 @@ int main(int argc, char *argv[])
 double val;
 
 for(i=0; tests[i].string != NULL; i++) {
-if(strtod_nol_or_err(tests[i].string, "Cannot parse number") !=
-   tests[i].result) {
+if((int)(strtod_nol_or_err(tests[i].string, "Cannot parse number")*100+0.5) !=
+   (int)(tests[i].result * 100 + 0.5)) {
 fprintf(stderr, "FAIL: strtod_nol_or_err(\"%s\") != %f\n",
 tests[i].string, tests[i].result);
 return EXIT_FAILURE;

Bug#830743: mypy: FTBFS: error: invalid Python installation: unable to open /usr/lib/python3.5/config-3.5m-x86_64-linux-gnu/Makefile

[Andreas Beckmann]

Source: mypy
Version: 0.4.2-1
Severity: serious
Justification: fails to build from source

Hi,

mypy FTBFS on the arch:all buildd:

https://buildd.debian.org/status/fetch.php?pkg=mypy=all=0.4.2-1=1465515666

 fakeroot debian/rules binary-indep
dh binary-indep --with python3 --buildsystem=pybuild
   dh_testroot -i -O--buildsystem=pybuild
   dh_prep -i -O--buildsystem=pybuild
   dh_auto_install -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py install --root 
/«PKGBUILDDIR»/debian/mypy 
running install
error: invalid Python installation: unable to open 
/usr/lib/python3.5/config-3.5m-x86_64-linux-gnu/Makefile (No such file or 
directory)
E: pybuild pybuild:274: install: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py install --root /«PKGBUILDDIR»/debian/mypy 
dh_auto_install: pybuild --install -i python{version} -p 3.5 --dest-dir 
/«PKGBUILDDIR»/debian/mypy returned exit code 13
debian/rules:9: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 25


Andreas

Bug#830734: procps: FTBFS[!linux]: 'HOST_NAME_MAX' undeclared

[Aaron M. Ucko]

Craig Small  writes:

> local_lim.h is part of libc6-dev version 2.19-18+deb8u4
> So what version are you using and why did the definition go away?

unstable has 2.23-1, which dropped this definition on hurd-i386 and
kfreebsd-*.  It's not clear why it went away, or whether the change was
even intentional; copying debian-glibc for clarification.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#830742: src:fcgiwrap: Relicense Debian packaging to allow upstreaming of patches

[Peter Colberg]

Package: src:fcgiwrap
Version: 1.1.0-6
Severity: wishlist

Hi Jordi, hi Sergio,

The Debian packaging is currently licensed under GPL version 3 with
you as the copyright holders. This is a perfectly fine choice, but
usually the Debian packaging is licensed under the same terms as the
upstream software, which in this case is the Expat license.

Would you agree to relicense the Debian packaging for fcgiwrap to the
Expat license? This will allow us to submit Debian patches upstream.

Regards,
Peter


signature.asc
Description: PGP signature

Bug#830733: procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000

[Aaron M. Ucko]

Craig Small  writes:

> Yeah, amd64 doesn't have this problem, I'll probably have to make it
> "almost equal" but that's pretty bad way to run tests.

For floating point, that can be a necessary evil. :-/

> Ah so you're running i386 kfreebsd (you didn't report it in the other bug
> report)

Not personally, just looking at buildd logs.

At any rate, thanks for the quick reply!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#830733: procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000

[Craig Small]

Can you apply this patch to your setup and see if it checks? You really
only need to compile lib/test_strod_nol and run it.

 - Craig


On Mon, Jul 11, 2016 at 8:00 AM Craig Small  wrote:

> On Mon, Jul 11, 2016 at 7:33 AM Aaron M. Ucko  wrote:
>
>> Source: procps
>> Version: 2:3.3.12-1
>> Severity: serious
>> Justification: fails to build from source (but built successfully in the
>> past)
>>
>> The i386 build of procps failed with a test suite error (presumably
>> stemming from a small floating-point discrepancy):
>>
> Yeah, amd64 doesn't have this problem, I'll probably have to make it
> "almost equal" but that's pretty bad way to run tests.
> Alternatively I might just detect its on something that doesn't do the
> conversion right and skip them.
>
>
>> I suspect the hurd-i386 and kfreebsd-i386 builds would have failed in
>> the same fashion if they hadn't hit a compilation error, which I'll
>> report separately.
>>
> Ah so you're running i386 kfreebsd (you didn't report it in the other bug
> report)
> So.. kfreebsd amd64 has the host definition and kfreebsd i386 does not.
> As I said, kfreebsd has include problems all the time (most of the ifdefs
> are for it)
>
>  - Craig
> --
> Craig Small (@smallsees)   http://dropbear.xyz/ csmall at : enc.com.au
> Debian GNU/Linux   http://www.debian.org/   csmall at : debian.org
> GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5
>
> --
Craig Small (@smallsees)   http://dropbear.xyz/ csmall at : enc.com.au
Debian GNU/Linux   http://www.debian.org/   csmall at : debian.org
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5
diff --git a/lib/test_strtod_nol.c b/lib/test_strtod_nol.c
index 0be798c..71a5756 100644
--- a/lib/test_strtod_nol.c
+++ b/lib/test_strtod_nol.c
@@ -33,8 +33,8 @@ int main(int argc, char *argv[])
 double val;
 
 for(i=0; tests[i].string != NULL; i++) {
-if(strtod_nol_or_err(tests[i].string, "Cannot parse number") !=
-   tests[i].result) {
+if((int)(strtod_nol_or_err(tests[i].string, "Cannot parse number")*100) !=
+   (int)(tests[i].result * 100)) {
 fprintf(stderr, "FAIL: strtod_nol_or_err(\"%s\") != %f\n",
 tests[i].string, tests[i].result);
 return EXIT_FAILURE;

Bug#830261: RM: fpc [powerpc] -- ROM; package needs rebootstrapping and fails to install now

[Scott Kitterman]

On Fri, 8 Jul 2016 13:07:52 +0200 Paul Gevers  wrote:
> Hi Scott,
> 
> On 07-07-16 22:54, Scott Kitterman wrote:
> > How big is the stack of affected rdepends?
> 
> I used dak (albeit probably not with the smartest commands) to get me
> the following list (powerpc binaries build from the following source
> packages):
> lazarus
> cqrlog
> ddrescueview
> dozzaqueux
> easymp3gain
> gearhead
> gearhead2
> hedgewars
> imapcopy
> libqt4pas
> libqtpas
> mricron
> nbc
> optgeo
> pasdoc
> transgui
> tuxcmd
> vmg
> winff
> ztex-bmp

I chatted with infinity and he indicated the bug in fpc should be fixed soon.  
Rather than rm the rdepends (which are uninstallable on powerpc anyway), I 
think it's better to leave them and then do binNMUs once fpc is fixed.

Scott K

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

Bug#823085: vnstat: FTBFS on hurd-i386

[Scott Kitterman]

On Sunday, July 10, 2016 09:56:29 PM Andreas Beckmann wrote:
> Control: reassign -1 ftp.debian.org
> Control: severity -1 normal
> Control: retitle -1 RM: vnstat [hurd-i386] -- RoQA; FTBFS, tests fail
> 
> On Sat, 30 Apr 2016 17:03:38 +0200 Andreas Beckmann  wrote:
> > since version 1.12, vnstat FTBFS on hurd-i386:
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=vnstat=hurd-i386=1
> > .14-1=1448190114
> > 
> > gcc -Wl,-z,relro vnstat_tests.o common_tests.o database_tests.o
> > config_tests.o ifinfo_tests.o misc_tests.o daemon_tests.o common.o
> > ifinfo.o dbshow.o dbaccess.o dbcache.o cfg.o ibw.o misc.o daemon.o -lm
> > -lcheck -lrt -lpthread -lsubunit -o vnstat_tests ./vnstat_tests
> > Running suite(s): vnStat
> > 85%: Checks: 207, Failures: 30, Errors: 0
> > 
> > If this cannot be fixed trivially, please request decrufting of the
> > outdated binary packages.
> 
> No reaction in the last two months, requesting the decrufting now.

Checking reverse dependencies...
# Broken Depends:
acm: acm
alsaplayer: alsaplayer-nas
gbsplay: gbsplay
mpg123: mpg123
mplayer: mplayer
 mplayer-gui
qt4-x11: libqtgui4
speech-dispatcher: speech-dispatcher-audio-plugins
timidity: timidity
xfaces: xfaces

The broken depends list is significant.  Please resolve those and then remove 
the moreinfo tag once they are done.

Scott K

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

Bug#830527: [Piuparts-devel] Bug#830527: piuparts should ignore /var/log/apt/eipp.log.xz in purge test

[Sean Whitton]

Hello,

On Sat, Jul 09, 2016 at 07:26:19AM +, Holger Levsen wrote:
> > 2m6.4s ERROR: FAIL: Package purging left files on system:
> >   /var/log/apt/eipp.log.xz   not owned
>  
> I don't see this in my sid schroot. When+why does apt create it?

I'm not sure when and why it gets created, but try building and then
testing the source package cluster-gesture_0.0.2.1-7.1, currently in the
deferred upload queue, or possibly in the archive by the time you read
this.

> > This file can be created by the latest version of apt, and it
> > shouldn't be considered a purge failure since it's unrelated to the
> > package being tested.
> 
> and then I wonder why this shouldn't be a cleaned up by apt itself…

Yeah.  I wasn't sure whether to report this bug against piuparts or apt.
However, doesn't piuparts ignore changes to other dpkg and apt log files
already, like the main dpkg status file?

-- 
Sean Whitton

Bug#830741: mrpt: FTBFS on sparc64: TopographyReconstructPathFrom3RTK bus error

[Aaron M. Ucko]

Source: mrpt
Version: 1:1.4.0-3
Severity: important
Justification: fails to build from source

Thanks for fixing the sparc64 mrpt compilation error!  Alas, the build
still fails, this time with a test suite error:

  [ RUN  ] TopographyReconstructPathFrom3RTK.sampleDataset
  Bus error

Could you please take a look?  ("Bus error" typically indicates
insufficiently aligned data.)

Thanks!

Bug#830740: mrpt: FTBFS on hppa: parse_NMEA_RMC assertion failure

[Aaron M. Ucko]

Source: mrpt
Version: 1:1.4.0-3
Severity: important
Justification: fails to build from source

Thanks for looking into the build failures I previously reported.
mrpt builds are in much better shape now, but the hppa build still fails:

  [ RUN  ] CGPSInterface.parse_NMEA_RMC
  unknown file: Failure
  C++ exception with description "
  
   === MRPT EXCEPTION =
  void mrpt::system::timestampToParts(mrpt::system::TTimeStamp, 
mrpt::system::TTimeParts&, bool), line 120:
  Assert condition failed: sec_frac<1.0
  " thrown in the test body.
  [  FAILED  ] CGPSInterface.parse_NMEA_RMC (8 ms)

Could you please take a look?

Thanks!

Bug#830739: mpi-testsuite: FTBFS on non-Linux: 'override_dh_auto_configure' failed

[Aaron M. Ucko]

Source: mpi-testsuite
Version: 3.2+dfsg-1
Severity: important
Justification: fails to build from source

Builds of mpi-testsuite on kFreeBSD and the Hurd have been failing:

  config.status: executing default-4 commands
  for i in `find . -name "testlist" | grep -v ^..build`;\
  do\
if [ ! -e build-openmpi/$i ];   \
then\
  ln -s `pwd`/$i `pwd`/build-openmpi/$i;\
fi; \
  done
  ln: failed to create symbolic link 
'/«BUILDDIR»/mpi-testsuite-3.2+dfsg/build-openmpi/./.pc/disable_large_tests.patch/group/testlist':
 No such file or directory
  debian/rules:14: recipe for target 'override_dh_auto_configure' failed

The error from ln also appears on Linux, so it's probably a red
herring; it's not clear from the log what the actual problem is.

Could you please take a look?

Thanks!

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

Kernel: Linux 4.6.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)

Bug#830738: mpi-testsuite: FTBFS: test suite times out (hangs?)

[Aaron M. Ucko]

Source: mpi-testsuite
Version: 3.2+dfsg-1
Severity: important
Justification: fails to build from source

Builds of mpi-testsuite for most architectures failed with test suite
timeouts, as detailed at
https://buildd.debian.org/status/logs.php?pkg=mpi-testsuite=3.2%2Bdfsg-1

The last test started varies by architecture, so there may actually be
several bugs here.

  arm64:lockcontention
  armel:win_shared_gacc_flush_load
  armhf:nonblocking
* hppa: win_shared_cas_flush_load
  i386: win_shared_gacc_flush_load
  mips: cartzero
  mips64el: nonblocking
  mipsel:   nonblocking
  powerpc:  nonblocking_inpf
* ppc64:nonblocking
  ppc64el:  adlb_mimic1
  s390x:commcreate1
* sparc64:  cartzero

* Not a release architecture.

Non-Linux builds failed at the configuration stage; I'll report that
bug separately.

Could you please take a look?

BTW, the message

  Could not execute ps command

came up pretty frequently.  You might want to declare a build
dependency on procps, if only to cut down on noise.

Thanks!

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

Kernel: Linux 4.6.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)

Bug#830737: RM: sensord lm-sensors [kfreebsd-amd64 kfreebsd-i386] -- RoQA; ANAIS; restricted to linux-any

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

Hi,

please remove the sensord and lm-sensors binary packages from
kfreebsd-*, these are only built for linux nowadays.
Do not remove the remaining binary packages built from src:lm-sensors.


Andreas

Bug#830733: procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000

[Craig Small]

On Mon, Jul 11, 2016 at 7:33 AM Aaron M. Ucko  wrote:

> Source: procps
> Version: 2:3.3.12-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the
> past)
>
> The i386 build of procps failed with a test suite error (presumably
> stemming from a small floating-point discrepancy):
>
Yeah, amd64 doesn't have this problem, I'll probably have to make it
"almost equal" but that's pretty bad way to run tests.
Alternatively I might just detect its on something that doesn't do the
conversion right and skip them.


> I suspect the hurd-i386 and kfreebsd-i386 builds would have failed in
> the same fashion if they hadn't hit a compilation error, which I'll
> report separately.
>
Ah so you're running i386 kfreebsd (you didn't report it in the other bug
report)
So.. kfreebsd amd64 has the host definition and kfreebsd i386 does not.
As I said, kfreebsd has include problems all the time (most of the ifdefs
are for it)

 - Craig
-- 
Craig Small (@smallsees)   http://dropbear.xyz/ csmall at : enc.com.au
Debian GNU/Linux   http://www.debian.org/   csmall at : debian.org
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

Bug#830736: apt-cacher-ng: FTBFS on !linux: fileio.cc:168:22: error: 'string' does not name a type

[Andreas Beckmann]

Package: apt-cacher-ng
Version: 0.9.3.1-1
Severity: important

Hi,

apt-cacher-ng FTBFS on hurd-* and kfreebsd-*, but the previous versions
up to 0.9.2-1 successfully built there:

https://buildd.debian.org/status/fetch.php?pkg=apt-cacher-ng=kfreebsd-amd64=0.9.3.1-1=1465428570

[ 60%] Building CXX object source/CMakeFiles/acngstuff.dir/fileio.cc.o
cd /«PKGBUILDDIR»/obj-x86_64-kfreebsd-gnu/source && /usr/bin/c++-g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  
-I/«PKGBUILDDIR»/obj-x86_64-kfreebsd-gnu -I/«PKGBUILDDIR» 
-I/«PKGBUILDDIR»/include-D_FILE_OFFSET_BITS=64 -pthread -Wall -Wextra 
-Wno-unused-parameter -fvisibility-inlines-hidden -fvisibility=hidden 
-fdata-sections -ffunction-sections -std=gnu++11 -flto   -o 
CMakeFiles/acngstuff.dir/fileio.cc.o -c /«PKGBUILDDIR»/source/fileio.cc
/«PKGBUILDDIR»/source/fileio.cc:168:22: error: 'string' does not name a type
 void mkbasedir(const string & path)
  ^

Without looking at the code my guess is that there is either a 'std::'
or a '#include ' missing.


Andreas

Bug#830734: procps: FTBFS[!linux]: 'HOST_NAME_MAX' undeclared

[Craig Small]

On Mon, Jul 11, 2016 at 7:39 AM Aaron M. Ucko  wrote:

> Source: procps
> Version: 2:3.3.12-1
> Severity: important
> Justification: fails to build from source (but built successfully in the
> past)
>
> Builds of procps for kFreeBSD and the Hurd have been failing:
>
Builds on mine, I tested specifically on freebsd because its usually a
problem child.


>   watch.c: In function 'output_header':
>   watch.c:375:16: error: 'HOST_NAME_MAX' undeclared (first use in this
> function)
> char hostname[HOST_NAME_MAX + 1];
>
So, this a case of broken kFreeBSD includes again?
csmall@freebsd1:~$ grep '[[:space:]]HOST_NAME_MAX[[:space:]]' `find
/usr/include -type f`
/usr/include/x86_64-linux-gnu/bits/local_lim.h:#define HOST_NAME_MAX 64

local_lim.h is part of libc6-dev version 2.19-18+deb8u4
So what version are you using and why did the definition go away?

 - Craig

Bug#830735: stun: FTBFS on kfreebsd-amd64: #error Need some way to seed the random number generator

[Andreas Beckmann]

Source: stun
Version: 0.97~dfsg-2.1
Severity: important

Hi,

stun FTBFS on kfreebsd-amd64, but the previous versions built there
successfully:

https://buildd.debian.org/status/fetch.php?pkg=stun=kfreebsd-amd64=0.97~dfsg-2.1=1455478440

g++  -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -g -O -Wall stun.cxx -o stun.o
stun.cxx:681:7: error: #error Need some way to seed the random number generator


Andreas

Bug#787654: openstack-trove: CVE-2015-3156: multiple insecure /tmp file usage issues

[Andreas Beckmann]

Hi,

could you please fix up the found/fixed versions - right now the found
version is later than the fixed one. Or reopen the bug.

Thanks


Andreas

Bug#488231: closed by Andreas Beckmann <a...@debian.org> (closing bugs reported against ancient python versions)

[Enrico Zini]

On Sun, Jul 10, 2016 at 05:09:09PM +, Debian Bug Tracking System wrote:

> This bug has been reported against an ancient version of
> python (2.5/3.1), that was last released with Debian 6.0 (squeeze). But
> even squeeze-lts has now reached end-of-life and is no longer supported.
> The bug is assumed to be fixed (or no longer relevant) in newer python
> releases and therefore I'm closing this report now. If the problem is
> still reproducible in the currently supported versions (python2.7,
> python3.5/python3.6), feel free to provide more information, reopen
> and reassign this bug report.

It's still there, in 
file:///usr/share/doc/python2.7-doc/html/library/urllib.html
with the same phrasing, and no mention of urllib2 in python2, only a
mention of it for python3..


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 


signature.asc
Description: PGP signature

Bug#830734: procps: FTBFS[!linux]: 'HOST_NAME_MAX' undeclared

[Aaron M. Ucko]

Source: procps
Version: 2:3.3.12-1
Severity: important
Justification: fails to build from source (but built successfully in the past)

Builds of procps for kFreeBSD and the Hurd have been failing:

  watch.c: In function 'output_header':
  watch.c:375:16: error: 'HOST_NAME_MAX' undeclared (first use in this function)
char hostname[HOST_NAME_MAX + 1];
  ^
  watch.c:375:16: note: each undeclared identifier is reported only once for 
each function it appears in
  Makefile:1373: recipe for target 'watch.o' failed
  make[3]: *** [watch.o] Error 1

Please account for the possibility that HOST_NAME_MAX will be
undefined and supply a reasonable fallback where necessary.

Thanks!

Bug#830733: procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000

[Aaron M. Ucko]

Source: procps
Version: 2:3.3.12-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The i386 build of procps failed with a test suite error (presumably
stemming from a small floating-point discrepancy):

  FAIL: lib/test_strtod_nol
  =
  
  FAIL: strtod_nol_or_err("123") != 123.00
  FAIL lib/test_strtod_nol (exit status: 1)

I suspect the hurd-i386 and kfreebsd-i386 builds would have failed in
the same fashion if they hadn't hit a compilation error, which I'll
report separately.

Could you please take a look?

Thanks!

Bug#830683: Missing dependency on module-udev?

[Patrick Winnertz]

reopen 830683

thanks

I know that this split was done by purpose. However even if the split was done 
on purpose, this split shouldn't break existing systems - which actually 
happened. It would be nice if you wouldn't close the bug without actually 
thinking about a solution for this problem, as this will lead for sure to 
problems during dist-upgrade later on.


Greetings

Patrick

ps: please don't tell me what's the purpose of a recommendation - i know that. 
Hower this recommendation breaks existing systems.

> Felipe Sateler  hat am 10. Juli 2016 um 23:09 
> geschrieben:
> 
> 
> 
> On 10 Jul 2016 7:45 a.m., "Patrick Winnertz"  mailto:win...@debian.org > wrote:
> >
> > Hey,
> > I was able to resolve this issue by installing the recommendation: 
> pulseaudio-module-udev
> >
> > Maybe it would be wise to make it a dependency instead, if the 
> functionality/playback stops working during upgrade without this recommended 
> package.
> >
> 
> The split was done on purpose, to allow installing without udev (eg, on 
> containers).
> 
> Recommends are packages that should be installed except on exceptional 
> circumstances, a Depends is too strict.
> 
> Saludos
> 

Bug#830732: libindi: FTBFS on kfreebsd-*: termio.h not found

[Andreas Beckmann]

Source: libindi
Version: 1.2.0-1
Severity: important

Hi,

libindi FTBFS on kfreebsd-*, but previously it built there successfully:

https://buildd.debian.org/status/fetch.php?pkg=libindi=kfreebsd-i386=1.2.0-1=1461694853
https://buildd.debian.org/status/fetch.php?pkg=libindi=kfreebsd-amd64=1.2.0-1=1461691013

make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-kfreebsd-gnu'
/usr/bin/cmake -E cmake_progress_report 
/«PKGBUILDDIR»/obj-x86_64-kfreebsd-gnu/CMakeFiles 55
[ 45%] Building CXX object 
CMakeFiles/indi_smartfocus_focus.dir/drivers/focuser/smartfocus.cpp.o
/usr/bin/c++-std=c++0x -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  
-I/«PKGBUILDDIR»/obj-x86_64-kfreebsd-gnu -I/«PKGBUILDDIR» -I/«PKGBUILDDIR»/libs 
-I/«PKGBUILDDIR»/libs/indibase -I/usr/include/libnova-o 
CMakeFiles/indi_smartfocus_focus.dir/drivers/focuser/smartfocus.cpp.o -c 
/«PKGBUILDDIR»/drivers/focuser/smartfocus.cpp
/«PKGBUILDDIR»/drivers/focuser/smartfocus.cpp:23:20: fatal error: termio.h: No 
such file or directory
compilation terminated.
CMakeFiles/indi_smartfocus_focus.dir/build.make:57: recipe for target 
'CMakeFiles/indi_smartfocus_focus.dir/drivers/focuser/smartfocus.cpp.o' failed
make[3]: *** 
[CMakeFiles/indi_smartfocus_focus.dir/drivers/focuser/smartfocus.cpp.o] Error 1
make[3]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-kfreebsd-gnu'


If this issue is not trivially fixable, please request decrufting
of the outdated binary packages.


Andreas

Bug#830617: apt: "apt-get clean" makes apt-cache slow

[Jakub Wilk]

* Julian Andres Klode , 2016-07-09, 23:51:

(or we could regenerate the cache during  clean...)


Yes, please regenerate it.

--
Jakub Wilk

Bug#804992: [debian-mysql] Bug#804992: Bug#804992: mysql-server-5.6: Please drop dependency on initscripts package

[Michael Biebl]

Hi Otto,

Am 09.07.2016 um 13:41 schrieb Otto Kekäläinen:
> 2016-07-09 11:08 GMT+03:00 Michael Biebl :
>>> We're expecting to upload 5.7 to experimental very soon now. If somebody
>>> wants to cherry-pick this to 5.6 and upload, I have no particular
>>> objection (though please push to VCS too; we haven't moved 5.6 into the
>>> unified repo yet, so it'd be mysql-5.6.git).
>>>
>>
>> I'd be happy to make an NMU for mysql-5.6, simply because I have it
>> installed on my system and would like to see the dependency go as soon
>> as possible. Since I don't have commit access to pkg-mysql though, I can
>> only send you a debdiff. Would that be fine?
> 
> If you need quick fixes, then upload current mysql-5.6 with these commits 
> added:
> http://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=526dbaff5888344c35e1be413fabe3ea7b186afc
> http://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=65f1a907b695fcfed8e245e733709ed0289cdf7b
> 
> Ideally all work would be gone using the team's git repositories. Do
> you plan to contribute to MySQL/MariaDB packaging in the future too?
> In that case I could add you to the team, you are a DD after all.

I appreciate the offer, but I have to decline because there's already
too much on my plane. I basically just want a fix for mysql-5.6 in
unstable, so I'd keep the diff as minimal as possible. I can add the
above two commit if you want (assuming they can easily be
cherry-picked). Will have a look.

Regards,
Michael




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



signature.asc
Description: OpenPGP digital signature

Bug#830731: espeak: bad pronunciation of "unary"

[Jakub Wilk]

Package: espeak
Version: 1.48.04+dfsg-3
Usertags: anorack

espeak pronunces "unary" as:
[[Vn'A@r-i]]

I believe the correct pronunciation is:
[[j'un@ri]]


-- 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.6.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 espeak depends on:
ii  libc6   2.23-1
ii  libespeak1  1.48.04+dfsg-3
ii  libgcc1 1:6.1.1-9
ii  libstdc++6  6.1.1-9

--
Jakub Wilk

Bug#830730: espeak: EWMH, UCS, UTF, UUID acronyms

[Jakub Wilk]

Source: espeak
Version: 1.48.04+dfsg-3
Usertags: anorack

These acronyms are currently not pronounced correctly:
EWMH, UCS, UTF, UUID

I hoped that the attached patch would fix it, but it didn't make any 
difference. :-/ Does the package rebuild the data files from source?


--
Jakub Wilk
--- a/dictsource/en_list
+++ b/dictsource/en_list
@@ -572,6 +572,7 @@
 eur	jU@	$only
 evga	$abbrev
 exe	$abbrev
+ewmh	$abbrev
 ftaa	$abbrev
 fyi	$abbrev
 ghz	gIg@h3:ts
@@ -650,6 +651,7 @@
 thu	T3:// Thursday
 ?5 thu	TIR// Thursday
 ucla	$abbrev
+ucs	$abbrev
 ufo	$abbrev
 ui	$abbrev
 uk	$abbrev
@@ -663,7 +665,9 @@
 usda	$abbrev
 ussr	$abbrev
 utc $abbrev
+utf	$abbrev
 uucp	$abbrev
+uuid	$abbrev
 uv	$abbrev
 VI  $abbrev
 wwii	dVb@Lju:dVb@Lju:t'u:

Bug#534058: build-depends not available on amd64

[Steve Langasek]

Hi Ansgar,

On Sun, Jul 10, 2016 at 12:26:49PM +0200, Ansgar Burchardt wrote:
> Steve Langasek  writes:
> > There is now a provisional field that you can include in debian/control to
> > indicate which architecture an architecture: all package needs to be built
> > on: XS-Build-Indep-Architecture.

> I thought it was going to be "Build-Architecture-Indep" from some
> discussion in -devel@[1]?  Any reason why this was changed?

> Ansgar

>   [1] 

Bug#830718: nvidia-kernel-dkms: dkms builds nvidia kernel modules without module_layout version

[Luca Boccassi]

On Sun, 2016-07-10 at 21:54 +0200, Peter Keel wrote:
> Hi
> 
> * on the Sun, Jul 10, 2016 at 08:23:23PM +0100, Luca Boccassi wrote:
> > I am running the same driver with 4.6 from Jessie backports, and I'm not
> > seeing that problem. Are you sure it's not due to the custom kernel?
> 
> Pretty sure, as it did work maybe two weeks ago with 4.5.7 and the
> same kernel config. And I also tried to recompile it now with the
> old kernel 4.5.7, it also has no versions anymore.
> 
> I think it's something that changed in the toolchain within debian/sid.
> Not necessarily the nvidia-kernel-dkms package (because I didn't 
> change that one neither) but that's probably where it would need to
> be mitigated, so I reported the bug there.
> 
> > Could you please try with the kernel from the repositories so that we
> > can narrow it down a bit more?
> 
> I'll look into that. 

Just tried in a sid chroot with 367.27 from SVN and the latest kernel
headers, all seems fine:

root@luca-desktop:/# modprobe --dump-modversions 
/lib/modules/4.6.0-1-amd64/updates/dkms/nvidia-current.ko 
0xa435bbb2  module_layout
0x6bc3fbc0  __unregister_chrdev
0x5150c634  acpi_bus_register_driver

Kind regards,
Luca Boccassi


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

Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

[Chris Lamb]

Source: golang-github-mitchellh-go-homedir
Version: 0.0~git20150831.0.df55a15-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,

golang-github-mitchellh-go-homedir fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  golang-github-mitchellh-go-homedir
   Version:  0.0~git20150831.0.df55a15-1
   Build architecture:   amd64
   Date: Sun, 10 Jul 2016 22:26:38 +0200
   Hostname: 4562cafc3410
   Uname:Linux 4562cafc3410 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 
(2016-06-25) x86_64 GNU/Linux
   /etc/timezone:Africa/Johannesburg
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'golang-github-mitchellh-go-homedir-build-deps' in 
'../golang-github-mitchellh-go-homedir-build-deps_0.0~git20150831.0.df55a15-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package 
golang-github-mitchellh-go-homedir-build-deps.
  (Reading database ... 23116 files and directories currently installed.)
  Preparing to unpack 
golang-github-mitchellh-go-homedir-build-deps_0.0~git20150831.0.df55a15-1_all.deb
 ...
  Unpacking golang-github-mitchellh-go-homedir-build-deps 
(0.0~git20150831.0.df55a15-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-golang golang-1.6-go golang-1.6-src golang-go golang-src
  Suggested packages:
bzr ca-certificates mercurial subversion
  Recommended packages:
pkg-config
  The following NEW packages will be installed:
dh-golang golang-1.6-go golang-1.6-src golang-go golang-src
  0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 26.5 MB of archives.
  After this operation, 191 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 dh-golang all 1.18 
[9278 B]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-src amd64 
1.6.2-2 [6784 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-go amd64 
1.6.2-2 [19.7 MB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 golang-src amd64 
2:1.6.1+1 [2974 B]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 golang-go amd64 
2:1.6.1+1 [21.9 kB]
  Fetched 26.5 MB in 0s (121 MB/s)
  Selecting previously unselected package dh-golang.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23120 files and directories currently installed.)
  Preparing to unpack .../dh-golang_1.18_all.deb ...
  Unpacking dh-golang (1.18) ...
  Selecting previously unselected package golang-1.6-src.
  Preparing to unpack .../golang-1.6-src_1.6.2-2_amd64.deb ...
  Unpacking golang-1.6-src (1.6.2-2) ...
  Selecting previously unselected package golang-1.6-go.
  Preparing to unpack .../golang-1.6-go_1.6.2-2_amd64.deb ...
  Unpacking golang-1.6-go (1.6.2-2) ...
  Selecting previously unselected package golang-src.
  Preparing to unpack .../golang-src_2%3a1.6.1+1_amd64.deb ...
  Unpacking golang-src (2:1.6.1+1) ...
  Selecting previously unselected package golang-go.
  Preparing to unpack .../golang-go_2%3a1.6.1+1_amd64.deb ...
  Unpacking golang-go (2:1.6.1+1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up dh-golang (1.18) ...
  Setting up golang-1.6-src (1.6.2-2) ...
  Setting up golang-src (2:1.6.1+1) ...
  Setting up golang-1.6-go (1.6.2-2) ...
  Setting up golang-go 

Bug#830728: golang-github-mattn-go-shellwords: FTBFS: shellwords_test.go:57: fork/exec : no such file or directory

[Chris Lamb]

Source: golang-github-mattn-go-shellwords
Version: 1.0.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,

golang-github-mattn-go-shellwords fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  golang-github-mattn-go-shellwords
   Version:  1.0.0-1
   Build architecture:   amd64
   Date: Sun, 10 Jul 2016 22:26:17 +0200
   Hostname: b7cc84410cb6
   Uname:Linux b7cc84410cb6 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 
(2016-06-25) x86_64 GNU/Linux
   /etc/timezone:Africa/Johannesburg
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'golang-github-mattn-go-shellwords-build-deps' in 
'../golang-github-mattn-go-shellwords-build-deps_1.0.0-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package 
golang-github-mattn-go-shellwords-build-deps.
  (Reading database ... 23116 files and directories currently installed.)
  Preparing to unpack 
golang-github-mattn-go-shellwords-build-deps_1.0.0-1_all.deb ...
  Unpacking golang-github-mattn-go-shellwords-build-deps (1.0.0-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-golang golang-1.6-go golang-1.6-src golang-go golang-src
  Suggested packages:
bzr ca-certificates mercurial subversion
  Recommended packages:
pkg-config
  The following NEW packages will be installed:
dh-golang golang-1.6-go golang-1.6-src golang-go golang-src
  0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 26.5 MB of archives.
  After this operation, 191 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 dh-golang all 1.18 
[9278 B]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-src amd64 
1.6.2-2 [6784 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-go amd64 
1.6.2-2 [19.7 MB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 golang-src amd64 
2:1.6.1+1 [2974 B]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 golang-go amd64 
2:1.6.1+1 [21.9 kB]
  Fetched 26.5 MB in 0s (89.9 MB/s)
  Selecting previously unselected package dh-golang.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23120 files and directories currently installed.)
  Preparing to unpack .../dh-golang_1.18_all.deb ...
  Unpacking dh-golang (1.18) ...
  Selecting previously unselected package golang-1.6-src.
  Preparing to unpack .../golang-1.6-src_1.6.2-2_amd64.deb ...
  Unpacking golang-1.6-src (1.6.2-2) ...
  Selecting previously unselected package golang-1.6-go.
  Preparing to unpack .../golang-1.6-go_1.6.2-2_amd64.deb ...
  Unpacking golang-1.6-go (1.6.2-2) ...
  Selecting previously unselected package golang-src.
  Preparing to unpack .../golang-src_2%3a1.6.1+1_amd64.deb ...
  Unpacking golang-src (2:1.6.1+1) ...
  Selecting previously unselected package golang-go.
  Preparing to unpack .../golang-go_2%3a1.6.1+1_amd64.deb ...
  Unpacking golang-go (2:1.6.1+1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up dh-golang (1.18) ...
  Setting up golang-1.6-src (1.6.2-2) ...
  Setting up golang-src (2:1.6.1+1) ...
  Setting up golang-1.6-go (1.6.2-2) ...
  Setting up golang-go (2:1.6.1+1) ...
  Setting up golang-github-mattn-go-shellwords-build-deps (1.0.0-1) ...
  
  

Bug#830727: golang-github-magiconair-properties: FTBFS: go test -v github.com/magiconair/properties [..] circular reference

[Chris Lamb]

Source: golang-github-magiconair-properties
Version: 1.7.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,

golang-github-magiconair-properties fails to build from source in 
unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  golang-github-magiconair-properties
   Version:  1.7.0-1
   Build architecture:   amd64
   Date: Sun, 10 Jul 2016 22:25:55 +0200
   Hostname: b6fcc713193c
   Uname:Linux b6fcc713193c 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 
(2016-06-25) x86_64 GNU/Linux
   /etc/timezone:Africa/Johannesburg
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'golang-github-magiconair-properties-build-deps' 
in '../golang-github-magiconair-properties-build-deps_1.7.0-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package 
golang-github-magiconair-properties-build-deps.
  (Reading database ... 23116 files and directories currently installed.)
  Preparing to unpack 
golang-github-magiconair-properties-build-deps_1.7.0-1_all.deb ...
  Unpacking golang-github-magiconair-properties-build-deps (1.7.0-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-golang golang-1.6-go golang-1.6-src golang-any golang-check.v1-dev
golang-go golang-gopkg-check.v1-dev golang-src
  Suggested packages:
bzr ca-certificates mercurial subversion
  Recommended packages:
pkg-config
  The following NEW packages will be installed:
dh-golang golang-1.6-go golang-1.6-src golang-any golang-check.v1-dev
golang-go golang-gopkg-check.v1-dev golang-src
  0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 26.6 MB of archives.
  After this operation, 191 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 dh-golang all 1.18 
[9278 B]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-src amd64 
1.6.2-2 [6784 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-go amd64 
1.6.2-2 [19.7 MB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 golang-src amd64 
2:1.6.1+1 [2974 B]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 golang-go amd64 
2:1.6.1+1 [21.9 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 golang-any amd64 
2:1.6.1+1 [3100 B]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 
golang-gopkg-check.v1-dev all 0.0+git20160105.0.4f90aea-2 [29.9 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 golang-check.v1-dev 
all 0.0+git20160105.0.4f90aea-2 [3068 B]
  Fetched 26.6 MB in 0s (101 MB/s)
  Selecting previously unselected package dh-golang.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23120 files and directories currently installed.)
  Preparing to unpack .../dh-golang_1.18_all.deb ...
  Unpacking dh-golang (1.18) ...
  Selecting previously unselected package golang-1.6-src.
  Preparing to unpack .../golang-1.6-src_1.6.2-2_amd64.deb ...
  Unpacking golang-1.6-src (1.6.2-2) ...
  Selecting previously unselected package golang-1.6-go.
  Preparing to unpack .../golang-1.6-go_1.6.2-2_amd64.deb ...
  Unpacking golang-1.6-go (1.6.2-2) ...
  Selecting previously unselected package golang-src.
  Preparing to unpack .../golang-src_2%3a1.6.1+1_amd64.deb ...
  Unpacking golang-src (2:1.6.1+1) ...
  

Bug#830726: xtrlock does not block multitouch events

[Antoine Amarilli]

Package: xtrlock
Version: 2.8
Severity: normal
Tags: upstream

Dear Maintainer,

xtrlock appears not to block multitouch events when the session is locked, so
that any user stumbling upon a locked session can still input multitouch events.

One could imagine that this could constitute a security vulnerability (requiring
physical access to the machine).

Steps to reproduce (on a computer with a suitably configured touchscreen):

1. Open chromium (my example of a program that processes multitouch events) and
put it in fullscreen mode.
2. Check that you can pinch and zoom (put two fingers of the screen and move
them closer or further apart to change the zoom level).
3. Run xtrlock to lock the session.
4. With xtrlock running, put one finger on the screen and leave it there (the
mouse pointer with the xtrlock lock icon follows that finger). While doing this,
perform the pinch and zoom with two other fingers.

Observed result:

The pinch and zoom is taken into account by chromium even though the session is
locked.

Expected result:

The event should not be seen by chromium while the session is locked.

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

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

Versions of packages xtrlock depends on:
ii  libc6 2.22-13
ii  libx11-6  2:1.6.3-1

xtrlock recommends no packages.

xtrlock suggests no packages.

-- debconf-show failed

Bug#830725: amanda: please make the build reproducible

[Chris Lamb]

Source: amanda
Version: 1:3.3.8-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the "reproducible builds" effort [0], we noticed that amanda 
could not be built reproducibly.

Patch attached.

 [0] https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build 1970-01-01 02:00:00.0 +0200
--- b/debian/patches/reproducible-build 2016-07-10 21:47:23.940480073 +0200
@@ -0,0 +1,20 @@
+--- amanda-3.3.8.orig/common-src/Makefile.am
 amanda-3.3.8/common-src/Makefile.am
+@@ -10,6 +10,8 @@ INCLUDES =  -I$(top_srcdir)/gnulib
+ AM_CFLAGS = $(AMANDA_WARNING_CFLAGS)
+ AM_LDFLAGS = $(AMANDA_STATIC_LDFLAGS) $(AS_NEEDED_FLAGS)
+ 
++BUILD_DATE = $(shell date --utc --date="@${SOURCE_DATE_EPOCH:-$(shell date 
+%s)}")
++
+ amlib_LTLIBRARIES =   libamanda.la
+ 
+ sbin_PROGRAMS = amservice
+@@ -157,7 +159,7 @@ genversion.$(OBJEXT): $(genversion_SOURC
+ genversion.h: $(top_builddir)/config.status
+   -rm -f $@ $@.new
+   echo '#define CC "$(CC)"' > $@.new
+-  echo '#define BUILT_DATE "'`date`'"' >> $@.new
++  echo '#define BUILT_DATE "'$(BUILD_DATE)'"' >> $@.new
+   echo '#define BUILT_MACH "$(target)"' >> $@.new
+   mv $@.new $@
+ 
--- a/debian/patches/series 2016-07-10 21:08:23.359900761 +0200
--- b/debian/patches/series 2016-07-10 21:20:57.931784960 +0200
@@ -10,3 +10,4 @@
 fix-amgtar-exclude
 fix-lintian-miss-spelling-amanda.conf.5.xml
 fix-lintian-miss-spelling-amanda-changers.7.xml
+reproducible-build

Bug#815265: kinect-audio-setup: FTBFS on kfreebsd: implicit declaration of function 'libusb_set_auto_detach_kernel_driver'

[Andreas Beckmann]

On 2016-07-10 20:51, Antonio Ospite wrote:
> just out of curiosity: was the issue ever reported upstream?
> Steven Chamberlain offered to do that but I don't know if he actually
> managed to.

I do not know either. But Steven implemented the stub function.


Andreas

Bug#830718: nvidia-kernel-dkms: dkms builds nvidia kernel modules without module_layout version

[Peter Keel]

Hi

* on the Sun, Jul 10, 2016 at 08:23:23PM +0100, Luca Boccassi wrote:
> I am running the same driver with 4.6 from Jessie backports, and I'm not
> seeing that problem. Are you sure it's not due to the custom kernel?

Pretty sure, as it did work maybe two weeks ago with 4.5.7 and the
same kernel config. And I also tried to recompile it now with the
old kernel 4.5.7, it also has no versions anymore.

I think it's something that changed in the toolchain within debian/sid.
Not necessarily the nvidia-kernel-dkms package (because I didn't 
change that one neither) but that's probably where it would need to
be mitigated, so I reported the bug there.

> Could you please try with the kernel from the repositories so that we
> can narrow it down a bit more?

I'll look into that. 

Cheers
Seegras
-- 
"Those who give up essential liberties for temporary safety deserve 
neither liberty nor safety." -- Benjamin Franklin
"It's also true that those who would give up privacy for security are 
likely to end up with neither." -- Bruce Schneier

Bug#830724: RFS: minetest-mod-mobf-core (ITP)

[Julien Puydt]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "minetest-mod-mobf-core"

 * Package name: minetest-mod-mobf-core
   Version : 2.5.1-1
   Upstream Author : sapier
 * URL : https://github.com/sapier/mobf_core
 * License : CC-BY-SA-3.0
   Section : games

  It builds those binary packages:

minetest-mod-mobf-core - Minetest modpack providing a framework for 
creating mobs

 minetest-mod-mobf-trap - Minetest mod providing traps for mobs

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


  https://mentors.debian.net/package/minetest-mod-mobf-core


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

dget -x 
https://mentors.debian.net/debian/pool/main/m/minetest-mod-mobf-core/minetest-mod-mobf-core_2.5.1-1.dsc


  It is packaged within the Debian Games Team as:
Vcs-Git: https://anonscm.debian.org/git/pkg-games/minetest-mod-mobf-core.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-games/minetest-mod-mobf-core.git


  Notice that minetest-mod-mobf-trap depends on 
minetest-mod-animalmaterials which is another package I'm preparing (and 
which in turn depends on the binary minetest-mod-mobf-core!).


  Regards,
   Julien Puydt

Bug#823085: vnstat: FTBFS on hurd-i386

[Andreas Beckmann]

Control: reassign -1 ftp.debian.org
Control: severity -1 normal
Control: retitle -1 RM: vnstat [hurd-i386] -- RoQA; FTBFS, tests fail

On Sat, 30 Apr 2016 17:03:38 +0200 Andreas Beckmann  wrote:
> since version 1.12, vnstat FTBFS on hurd-i386:
> 
> https://buildd.debian.org/status/fetch.php?pkg=vnstat=hurd-i386=1.14-1=1448190114
> 
> gcc -Wl,-z,relro vnstat_tests.o common_tests.o database_tests.o 
> config_tests.o ifinfo_tests.o misc_tests.o daemon_tests.o common.o ifinfo.o 
> dbshow.o dbaccess.o dbcache.o cfg.o ibw.o misc.o daemon.o -lm -lcheck -lrt 
> -lpthread -lsubunit -o vnstat_tests
> ./vnstat_tests
> Running suite(s): vnStat
> 85%: Checks: 207, Failures: 30, Errors: 0

> If this cannot be fixed trivially, please request decrufting of the outdated
> binary packages.

No reaction in the last two months, requesting the decrufting now.

Andreas

Bug#815351: gvfs: FTBFS on hurd-i386: unsatisfiable B-D: libsmbclient-dev

[Andreas Beckmann]

On Sun, 1 May 2016 00:16:56 +0200 Michael Biebl  wrote:
> A build is fine, I'm more interested if the GNOME stack is actually
> usable on Hurd though. Have you done any runtime testing
> 
> Otherwise I don't see a point in making it buildable if we don't have
> any actual users.

I do not know - I do not run HURD myself, just doing QA. And fixing the
build seemed easier than recursively requesting removal of the outdated
gvfs and its rdeps from hurd-i386.


Andreas

Bug#827391: nvidia-driver: Add support to Nvidia GeForce 10xx GPUs w/ driver 367.27

[Luca Boccassi]

On Sun, 2016-07-10 at 18:56 +0200, hikaru.deb...@web.de wrote:
> > Yes it should be made clearer, if you are on amd64 and want the 32 bit
> > libraries, not all packages should be installed.
> > 
> > Basically you'll want to install libgl1-nvidia-glx-i386 (or
> > nvidia-driver-libs-i386 depending on the branch) and their dependencies.
> > 
> > I've updated the wiki.
> 
> Thanks! But that isn't the problem.
> fyi, I've switched the test system from i386 to amd64, but the basic problem
> remains.
> 
> Maybe I should also tell you some things about my system setup:
> The test system is Jessie/amd64 on a USB stick. It is currently plugged into a
> computer with a GT218 chip. I know this isn't supportd by 367 anymore, but I
> merely want to make sure the driver installation works fine, because later I
> want to plug the USB stick into a computer with a GTX 1070 card. I only have
> access to this actual target computer sporadically, hence the test system.
> 
> What I did was to install Jessie's nvidia-driver and the X-Server works. I
> wanted to use this package list as a template for what I actually need from
> 367:
> 
> # dpkg -l | grep nvidia
> ii  glx-alternative-nvidia0.5.1   
>  amd64allows the selection of NVIDIA as GLX provider
> ii  libegl1-nvidia:amd64  340.96-1
>  amd64NVIDIA binary EGL libraries
> ii  libgl1-nvidia-glx:amd64   340.96-1
>  amd64NVIDIA binary OpenGL libraries
> ii  libgles1-nvidia:amd64 340.96-1
>  amd64NVIDIA binary OpenGL|ES 1.x libraries
> ii  libgles2-nvidia:amd64 340.96-1
>  amd64NVIDIA binary OpenGL|ES 2.x libraries
> ii  libnvidia-eglcore:amd64   340.96-1
>  amd64NVIDIA binary EGL core libraries
> ii  libnvidia-ml1:amd64   340.96-1
>  amd64NVIDIA Management Library (NVML) runtime library
> ii  nvidia-alternative340.96-1
>  amd64allows the selection of NVIDIA as GLX provider
> ii  nvidia-driver 340.96-1
>  amd64NVIDIA metapackage
> ii  nvidia-driver-bin 340.96-1
>  amd64NVIDIA driver support binaries
> ii  nvidia-installer-cleanup  20141201+1  
>  amd64cleanup after driver installation with the nvidia-installer
> ii  nvidia-kernel-common  20141201+1  
>  amd64NVIDIA binary kernel module support files
> ii  nvidia-kernel-dkms340.96-1
>  amd64NVIDIA binary kernel module DKMS source
> ii  nvidia-modprobe   340.46-1
>  amd64utility to load NVIDIA kernel modules and create device nodes
> ii  nvidia-settings   340.46-2
>  amd64tool for configuring the NVIDIA graphics driver
> ii  nvidia-support20141201+1  
>  amd64NVIDIA binary graphics driver support files
> ii  nvidia-vdpau-driver:amd64 340.96-1
>  amd64Video Decode and Presentation API for Unix - NVIDIA driver
> ii  xserver-xorg-video-nvidia 340.96-1
>  amd64NVIDIA binary Xorg driver
> 
> 
> Since apt's dependency resolution isn't available with the self-made packages,
> I then wanted to replace all these packages at once via dpkg, which failed due
> to dependency problems. To track these down, I wanted to atomize the process.
> nvidia-driver seemed to be a good starting point, however it complains during
> the installation:
> 
> # dpkg -i nvidia-driver_367.27-1_amd64.deb
> dpkg: regarding nvidia-driver_367.27-1_amd64.deb containing nvidia-driver, 
> pre-dependency problem:
>  nvidia-driver pre-depends on nvidia-legacy-check (>= 343)
>   nvidia-legacy-check is not installed.
> 
> dpkg: error processing archive nvidia-driver_367.27-1_amd64.deb (--install):
>  pre-dependency problem - not installing nvidia-driver
> Errors were encountered while processing:
>  nvidia-driver_367.27-1_amd64.deb
> 
> 
> So I successfully installed nvidia-legacy-check first:
> 
> # dpkg -i nvidia-legacy-check_367.27-1_amd64.deb
> Selecting previously unselected package nvidia-legacy-check.
> (Reading database ... 131797 files and directories currently installed.)
> Preparing to unpack nvidia-legacy-check_367.27-1_amd64.deb ...
> *** The following unsupported devices are present in the machine:
> 03:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [ION] 
> [10de:0a64] (rev a2)
> Unpacking nvidia-legacy-check (367.27-1) 

Bug#821347: libsecret porting for s390x

[Andreas Henriksson]

Hello Bastian Blank.

On Sun, Jul 10, 2016 at 12:33:12PM +0200, Bastian Blank wrote:
> On Sun, Jun 26, 2016 at 10:12:31PM +0200, Andreas Henriksson wrote:
> > I'd like to ask for your help with looking at the problems building
> > libsecret on s390x. It's currently the only (release-)architecture
> > not building and blocking testing migration for a long time. :(
> 
> What was the result of your manual build on the s390x porter machine?

Building on a porter box (zelenka) seems to run into the same issue
and build gets stuck after:
PASS: test-collection 27 /collection/search-secrets-async

Same as in:
https://buildd.debian.org/status/fetch.php?pkg=libsecret=s390x=0.18.5-1=1462961523

Regards,
Andreas Henriksson

Bug#830717: Re : Bug#830717: kio: Can’t view directories.

[nicolas . patrois]

Le 10/07/2016 20:25:02, Diederik de Haas a écrit :

> This seems to be another case of mixed framework package versions,
> 5.22 en 5.23.

Yes, I have a mix of 5.22 and 5.23.
OK, I’ll wait for the upgrade.

nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des 
humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...

Bug#830718: nvidia-kernel-dkms: dkms builds nvidia kernel modules without module_layout version

[Luca Boccassi]

Control: severity -1 normal
Control: tags -1 moreinfo

On Sun, 2016-07-10 at 20:19 +0200, Peter Keel wrote:
> Package: nvidia-kernel-dkms
> Version: 367.27-1
> Severity: serious
> Justification: 6
> 
> Dear Maintainer,
> 
> Installing a new kernel 4.6.3 (self-compiled), and installing the
> experimental nvidia-drivers a few days later, led to the drivers
> compiled without module versions. 
> 
> 
> Commandline used: 
> dkms install nvidia-current -v 367.27 -k 4.6.3 --force --verbose 
> 
> Note that this was working on the earlier 4.5.7 kernel for which the
> symbols were generated. So I expect either compiler or compile-chain
> to be the culprit. 
> 
> 
> What happened is this: 
> 
> /lib/modules/4.6.3/updates/dkms# modprobe --dump-modversions 
> nvidia-current.ko 
> /lib/modules/4.6.3/updates/dkms#
> 
> There are no versions. Normal modules (ALSO dkms ones, for the same kernel)
> look like this: 
> 
> /lib/modules/4.6.3/updates/dkms# modprobe --dump-modversions 
> compat_xtables.ko 
> 0x83ca59d8module_layout
> 0x449ad0a7memcmp
> /lib/modules/4.6.3/updates/dkms#
> 
>* What was the outcome of this action?
> 
> [   68.125562] nvidia: no symbol version for module_layout
> 
>* What outcome did you expect instead?
> 
> [  978.452077] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  367.27  Thu 
> Jun  9 18:53:27 PDT 2016
> 
> (This I actually did by allowing the kernel to force-load modules; and to 
> load the same unversioned module via "modprobe --force" -- not a 
> sustainable solution. 

I am running the same driver with 4.6 from Jessie backports, and I'm not
seeing that problem. Are you sure it's not due to the custom kernel?

Could you please try with the kernel from the repositories so that we
can narrow it down a bit more?

Kind regards,
Luca Boccassi


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

Bug#830721: Failed to load module "nv" (module does not exist, 0)

[Andreas Beckmann]

Hi Karsten,

You are missing a xorg.conf - see README.Debian
(or use the driver packages from jessie-backports, these automatically
configure Xorg)


Andreas

Bug#830721: Failed to load module "nv" (module does not exist, 0)

[Luca Boccassi]

Control: tags -1 moreinfo

On Sun, 2016-07-10 at 20:36 +0200, Karsten Malcher wrote:
> Package: nvidia-driver
> Version: 340.96-1
> Severity: normal
> 
> 
> Hello,
> 
> i changed the card from ATI to NVIDIA after the ATI card died.
> After that i uninstalled all ATI stuff.
> Then i reinstalled the xserver and the nvidia-driver.
> It says it was compiling the nvidia driver and did report no error.
> 
> But it is not working - there is no driver!
> 
> Why graphics is such a pain in original Debian?
> When i boot Knoppix i always have a running X!
> 
> Cheers
> Karsten

How did you install the drivers? Make sure you reboot afterwards to
unload and blacklist nouveau!

Logs show that:

1) You have a very old 304.125 module loaded. Remove any *legacy-304xx
packages, and make sure the kernel modules from dkms are gone too
2) Xorg is still loading nouveau, so make sure update-alt is correct:

- "sudo update-alternatives --config glx" should have /usr/lib/nvidia
- "sudo update-alternatives --config nvidia" should
have /usr/lib/nvidia/current

Kind regards,
Luca Boccassi


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

Bug#830527: [Piuparts-devel] piuparts should ignore /var/log/apt/eipp.log.xz in purge test

[Paul Hardy]

--

On Sun, Jul 10, 2016 at 11:57 AM, Paul Hardy  wrote:
>
> piuparts is failing for the same reason with the ttf-unifont package.
> The end of the piuparts output is:
>
> ...
> 2m1.1s ERROR: FAIL: Package purging left files on system:
>   /var/log/apt/eipp.log.xz not owned
>

Now that piuparts has finished, the file /var/log/apt/eipp.log.xy is
no longer on my system.  I was going to see what was inside it and
found it is no longer there.  So something is removing it, but later
than piuparts expects.

Thank you,


Paul Hardy

Bug#830723: When X server start fails it ends up in an endless loop

[Karsten Malcher]

Package: xserver-xorg
Version: 1:7.7+7
Severity: important

Hello,

for more than one time i have the problem that when the X server fails to start 
it ends up in an loop to try to start!
When you have a damaged vga card and change it you never get a simple console 
again.
Sometimes the system doesn't react any more because it is somehow locked by the 
X server.

Why this loop?

In the past the X server tried to start and when it fails it prompted the error 
and you land on the console.
Now the system behaviour is like in windows where the system get's unusable 
without an graphical frontend!

Cheers
Karsten



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jun 21  2015 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2401376 Feb 11  2015 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 
430] [10de:0de1] (rev a1)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian
3.16.7-ckt11-1+deb8u2 (2015-07-17)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 42479 Dec  4  2010 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 35553 Jun 19 12:29 /var/log/Xorg.1.log
-rw-r--r-- 1 root root  8004 Jul 10 21:04 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[   309.595]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[   309.595] X Protocol Version 11, Revision 0
[   309.595] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[   309.595] Current Operating System: Linux PC8 3.16.0-4-amd64 #1 SMP Debian 
3.16.7-ckt11-1+deb8u2 (2015-07-17) x86_64
[   309.595] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=22e85ef8-276b-4cdd-bfd9-bc76e4f12e56
ro quiet
[   309.595] Build Date: 11 February 2015  12:32:02AM
[   309.596] xorg-server 2:1.16.4-1 (http://www.debian.org/support)
[   309.596] Current version of pixman: 0.32.6
[   309.596]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   309.596] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   309.597] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 10 21:04:34 
2016
[   309.597] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   309.598] (==) No Layout section.  Using the first Screen section.
[   309.598] (==) No screen section available. Using defaults.
[   309.598] (**) |-->Screen "Default Screen Section" (0)
[   309.598] (**) |   |-->Monitor ""
[   309.598] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   309.598] (==) Automatically adding devices
[   309.598] (==) Automatically enabling devices
[   309.598] (==) Automatically adding GPU devices
[   309.598] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   309.598]Entry deleted from font path.
[   309.598] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   309.598] (==) ModulePath set to "/usr/lib/xorg/modules"
[   309.598] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   309.598] (II) Loader magic: 0x7fe8ba921d80
[   309.598] (II) Module ABI versions:
[   309.598]X.Org ANSI C Emulation: 0.4
[   309.598]X.Org Video Driver: 18.0
[   309.598]X.Org XInput driver : 21.0
[   309.598]X.Org Server Extension : 8.0
[   309.598] (II) xfree86: Adding drm device (/dev/dri/card0)
[   309.600] (--) PCI:*(0:2:0:0) 10de:0de1:: rev 161, Mem @ 
0xfd00/16777216, 0xf000/134217728,
0xfa00/33554432, I/O @ 0xe800/128, BIOS @ 0x/524288
[   309.600] (II) LoadModule: "glx"
[   309.600] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   309.601] (II) Module glx: vendor="X.Org Foundation"
[   309.601]compiled for 1.16.4, module version = 1.0.0
[   309.601]ABI class: X.Org Server Extension, version 8.0
[   309.601] (==) AIGLX enabled
[   309.601] (==) Matched nouveau as autoconfigured driver 0
[   309.601] (==) Matched nv 

Bug#830708: RFP: coz-profiler -- Finding Code that Counts with Causal Profiling

[Petter Reinholdtsen]

The package depend on libelfin, https://github.com/ccurtsinger/libelfin >,
to work, and will fail to build without it.

Surprisingly enough, the build will clone the git repository and make the source
available, so the problem is not too abvious when building the code for the 
first
time.

In addition, the build will download and build several example programs, but
I suspect those failures will not be a fatal problem in the build process.

-- 
Happy hacking
Petter Reinholdtsen

Bug#830722: systemd: systemctl aborts with "No Such Method"

[Michael Biebl]

Am 10.07.2016 um 20:39 schrieb Peter Gossner:
> Package: systemd
> Version: 230-7
> Severity: important
> 
> Dear Maintainer,
> Attempting to (re)understand systemd ...
> ~$ systemctl
> Failed to list units: No such method 'ListUnitsFiltered'
>  other options also fail
>  e.g.
> sudo systemctl try-restart exim4
> Failed to try-restart exim4.service: No such method 'TryRestartUnit'
> See system logs and 'systemctl status exim4.service' for details.
> 
> I also see logind errors and have been having dbus session issues which may 
> all be related to a pam module.
> 
> At other times systemd has attempted to rename network interfaces, screw up 
> diplay manager,  hang without console access , fail to start real consoles at 
> all  deep fry kittens ...  

interesting

> Init: sysvinit (via /sbin/init)

So, apparently you are still using sysvinit. Have you filed the bug
report from a different system then the one you experience the problems?

Michael



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



signature.asc
Description: OpenPGP digital signature

Bug#830703: gnome-software exits with "Timeout was reached"

[Sajith T S]

An update: I have been trying to reproduce the behavior I have
reported, but it no longer can be reproduced if you do `killall
gnome-software` once and then relaunch gnome-software.

I have also tried logging out and logging back in, and rebooting, but
I still can't reproduce the problem.

I'm guessing that regular users of gnome-software will not encounter
the problem I've seen, because they will normally be using "reboot and
install" option.  I use apt-get upgrade.

-- 
"the lyf so short, the craft so long to lerne."
 -- Chaucer.

Bug#803456: Digikam 5.0.0 uploaded

[Steve M. Robbins]

Hi,

I wanted to make people aware that I have uploaded Digikam 5.0.0 packages to 
Debian earlier today.

I uploaded to experimental for staging for a few reasons:

1. To work through the build issues on various architectures. 

2. The configuration files are in a new location, but digikam does no migration 
[1].  To the user, it appears you are starting from scratch and there is a 
risk of confusion -- the referenced bug is from someone who thought 
(mistakenly) that a migration procedure was required.  The bug also references 
possibly using a KF5 function KConfig::copyTo() to migrate the files, but then 
concludes that some digikam 4 settings cause digikam 5 to crash.  At this 
point, it seems that automatic migration is unsafe but that the initial 
configuration wizard should be augmented with text that describes the upgrade-
from-4.x scenario better.  I'm seeking suggestions on what might be the best 
approach here.

3. The showfoto internationalized docs are missing due to an upstream bug [2].  
 
The bug is now patched upstream; however, the fix re-structures the source 
tarball so it is unclear whether this is easy to port into the current 
version; or better to wait for upstream 5.1.0 source tarball.

Thanks,
-Steve

[1] https://bugs.kde.org/show_bug.cgi?id=364258
[2] https://bugs.kde.org/show_bug.cgi?id=365135



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

Bug#830527: [Piuparts-devel] piuparts should ignore /var/log/apt/eipp.log.xz in purge test

[Paul Hardy]

thanks

piuparts is failing for the same reason with the ttf-unifont package.
The end of the piuparts output is:

...[about 800 lines of output snipped]
2m0.7s DEBUG: Command ok: ['chroot', '/tmp/tmpjEd7Ei', 'eatmydata',
'dpkg-divert', '--list']
2m0.7s DEBUG: Starting command: ['chroot', '/tmp/tmpjEd7Ei',
'eatmydata', 'apt-get', 'clean']
2m0.7s DEBUG: Command ok: ['chroot', '/tmp/tmpjEd7Ei', 'eatmydata',
'apt-get', 'clean']
2m1.1s ERROR: FAIL: Package purging left files on system:
  /var/log/apt/eipp.log.xz not owned

2m1.1s ERROR: FAIL: Installation and purging test.
2m1.3s DEBUG: Starting command: ['chroot', '/tmp/tmpjEd7Ei',
'eatmydata', 'umount', '/proc']
2m1.3s DEBUG: Command ok: ['chroot', '/tmp/tmpjEd7Ei', 'eatmydata',
'umount', '/proc']
2m1.3s DEBUG: Starting command: ['rm', '-rf', '--one-file-system',
'/tmp/tmpjEd7Ei']
2m1.4s DEBUG: Command ok: ['rm', '-rf', '--one-file-system', '/tmp/tmpjEd7Ei']
2m1.4s DEBUG: Removed directory tree at /tmp/tmpjEd7Ei
2m1.4s ERROR: piuparts run ends.


I used debuild with no arguments to create ".deb" files from the main
"unifont" directory, then I ran "sudo /usr/sbin/piuparts" with no
arguments on the ttf-unifont ".deb" file to produce the above error.

Thank you,


Paul Hardy

Bug#823065: nas: FTBFS on hurd-i386: debian/tmp/usr/bin/nasd: No such file or directory

[Andreas Beckmann]

Control: reassign -1 ftp.debian.org
Control: severity -1 normal
Control: retitle -1 RM: nas [hurd-i386] -- RoQA; FTBFS - nasd not built

On Sat, 30 Apr 2016 15:19:36 +0200 Andreas Beckmann  wrote:
> nasd FTBFS on hurd-i386, but older version sof the package built there
> successfully:

> cp: cannot stat 'debian/tmp/usr/bin/nasd': No such file or directory
> dh_install: cp --reflink=auto -a debian/tmp/usr/bin/nasd debian/nas//usr/bin/ 
> returned exit code 1

> If this is not trivially fixable, please request decrufting
> of the outdated binary packages.

No reaction within 2 months, requesting the decrufting now.

Andreas

Bug#827842: release.debian.org: nmu: ncurses_6.0+20160319-2

[Emilio Pozuelo Monfort]

On 10/07/16 20:02, Sven Joachim wrote:
> On 2016-06-22 08:11 +0200, Julien Cristau wrote:
> 
>> On Tue, Jun 21, 2016 at 17:53:40 +0200, Sven Joachim wrote:
>>
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian@packages.debian.org
>>> Usertags: binnmu
>>>
>>> Due to findutils bug #827724, ncurses-bin ended up empty on various
>>> architectures, see #827797.  Rebuilding with non-broken findutils should
>>> fix that.
>>>
>>> nmu ncurses_6.0+20160319-2 . amd64 i386 mips powerpc kfreebsd-i386
>>> . unstable . -m "Rebuild with findutils 4.6.0+git+20160517-4"
>>>
>>> The amd64 package is not actually affected, but having amd64 and i386
>>> out of sync is going to cause a lot of complaints from multiarch users
>>> that I'd rather not deal with.
>>>
>> jcristau@wuiet:~$ wb nmu ncurses . ANY -x32 . -m 'Rebuild with fixed
>> findutils (#827724)' --extra-depends 'findutils (>=
>> 4.6.0+git+20160517-4)'
>>
>> Scheduled.
> 
> Thanks.  Unfortunately, ncurses is now in BD-Uninstallable state on
> alpha and hurd-i386, because findutils FTBFS there (the broken findutils
> versions also did not build on these arches).
> 
> Could you please take out the findutils Extra-Depends?

Dropped.

Cheers,
Emilio

Bug#828052: Please update Ports wiki page

[Holger Wansing]

Hi,

John Paul Adrian Glaubitz  wrote:
> On 07/08/2016 07:20 PM, Holger Wansing wrote:
> > You are right, strictly spoken.
> > But there are several "old and removed" ports in the "unofficial ports" 
> > section,
> > like alpha or arm or hppa.
> > To solve this, we would need to create a third section like "Old/Removed 
> > ports",
> > or the like.
> 
> Both alpha and hppa still exist, they have just become ports. Neither ia64 nor
> sparc exist anywhere. That's a difference.
> 
> To see what targets in Debian are currently supported, both as release 
> architectures
> and as ports, look at a random buildd page [1]. As you can see, neither 
> "sparc"
> nor "ia64" are nowhere to be found while "alpha", "hppa" and "sparc64" are
> preset - every architecture that is grayed out is currently unofficial, thus
> a ports architecture.

Ok, understood.
To deal with this, I propose to change
"List of unofficial ports" into "List of unofficial/old ports".


I have attached a new diff and the new resulting html file.
Again the changings as an overview:

- "List of unofficial ports" -> "List of unofficial/old ports"
- move ia64, kfreebsd-amd64, kfreebsd-i386, s390 and sparc to the 
"unofficial/old 
  ports" section
- set ia64 from "released" to "discontinued" and added a sentence to document
  this change.
- kfreebsd-amd64: added a sentence to document the current, non-official status
- kfreebsd-i386: added a sentence to document the current, non-official status
- set m68k from "discontinued/being revived" to "in progress"
- set s390 from "released" to "replaced by s390x" and added a sentence to 
  document this change.
- set sparc from "released" to "replaced by sparc64" and added a sentence to 
  document this change.
- sh: changed port name from "sh" to "sh4". And added a sentence to mention
  the J-Core processor.


Holger

-- 

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

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

Index: english/ports/index.wml
===
RCS file: /cvs/webwml/webwml/english/ports/index.wml,v
retrieving revision 1.129
diff -u -r1.129 index.wml
--- english/ports/index.wml	8 Jun 2016 17:29:42 -	1.129
+++ english/ports/index.wml	10 Jul 2016 18:38:32 -
@@ -97,32 +97,6 @@
 released
 
 
-ia64
-Intel Itanium IA-64
-First officially released with Debian 3.0. This is a port to Intel's
-first 64-bit architecture. Note: this should not be confused with the
-latest Intel 64-bit extensions for Pentium 4 and Celeron processors,
-called Intel 64; for these, see the AMD64 port.
-released
-
-
-kfreebsd-amd64
-64-bit PC (amd64)
-First officially released with Debian 6.0 as a technology preview and
-the first non-Linux port released by Debian. Port of the Debian GNU
-system to the kernel of FreeBSD.
-released
-
-
-kfreebsd-i386
-32-bit PC (i386)
-First officially released with Debian 6.0 as a technology preview and
-the first non-Linux port released by Debian. Port of the Debian GNU
-system to the kernel of FreeBSD.
-released
-
-
 mips
 MIPS (big-endian mode)
 First officially released with Debian 3.0. Debian is being ported to
@@ -154,30 +128,15 @@
 released
 
 
-s390
-S/390 and zSeries
-First officially released with Debian 3.0. This is a port to IBM
-S/390 servers.
-released
-
-
-s390x
+s390x
 System z
-First officially released with Debian 7.0. A 64-bit userland for IBM System z mainframes
+First officially released with Debian 7.0. A 64-bit userland for IBM System z mainframes.
 released
 
-
-sparc
-Sun SPARC
-First officially released with Debian 2.1. This port runs on the Sun
-UltraSPARC series of workstations, as well as some of their successors
-in the sun4 architectures.
-released
-
 
 
 
-List of unofficial ports
+List of unofficial/old ports
 
 
 
@@ -234,6 +193,34 @@
 in progress
 
 
+ia64
+Intel Itanium IA-64
+First officially released with Debian 3.0. This is a port to Intel's
+first 64-bit architecture. Note: this should not be confused with the
+latest Intel 64-bit extensions for Pentium 4 and Celeron processors,
+called Intel 64; for these, see the AMD64 port. With Debian 8 ia64 was
+removed from the release due to insufficient developer support.
+discontinued
+
+
+kfreebsd-amd64
+64-bit PC (amd64)
+First officially released with Debian 6.0 as a technology preview and
+the first non-Linux port released by Debian. Port of the Debian GNU
+system to the kernel of FreeBSD. Is no longer part of the official release
+since Debian 8.
+in progress
+
+
+kfreebsd-i386
+32-bit PC (i386)
+First officially released with Debian 6.0 as a technology preview and
+the first non-Linux port released by Debian. Port of the Debian GNU
+system to the kernel of FreeBSD. Is no longer part of the official release
+since Debian 8.
+in progress
+
+
 

Bug#830722: systemd: systemctl aborts with "No Such Method"

[Peter Gossner]

Package: systemd
Version: 230-7
Severity: important

Dear Maintainer,
Attempting to (re)understand systemd ...
~$ systemctl
Failed to list units: No such method 'ListUnitsFiltered'
 other options also fail
 e.g.
sudo systemctl try-restart exim4
Failed to try-restart exim4.service: No such method 'TryRestartUnit'
See system logs and 'systemctl status exim4.service' for details.

I also see logind errors and have been having dbus session issues which may all 
be related to a pam module.

At other times systemd has attempted to rename network interfaces, screw up 
diplay manager,  hang without console access , fail to start real consoles at 
all  deep fry kittens ...  

Fortunately this is a humble home desktop and not a production server.
At some point soon I will do a fresh install, Its proabably something to do 
with my bent view of networking or black roosters or something.

 



-- Package-specific info:

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

Kernel: Linux 4.6.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3
ii  libapparmor12.10.95-4
ii  libaudit1   1:2.6.3-1
ii  libblkid1   2.28-5
ii  libc6   2.23-1
ii  libcap2 1:2.25-1
ii  libcap2-bin 1:2.25-1
ii  libcryptsetup4  2:1.7.0-2
ii  libgcc1 1:6.1.1-9
ii  libgcrypt20 1.7.1-2
ii  libgpg-error0   1.23-1
ii  libidn111.32-3.1
ii  libkmod222-1.1
ii  liblzma55.1.1alpha+20120614-2.1
ii  libmount1   2.28-5
ii  libpam0g1.1.8-3.3
ii  libseccomp2 2.3.1-2
ii  libselinux1 2.5-3
ii  libsystemd0 230-7
ii  mount   2.28-5
ii  util-linux  2.28-5

Versions of packages systemd recommends:
ii  dbus1.10.8-1
ii  libpam-systemd  230-7

Versions of packages systemd suggests:
ii  policykit-10.105-15
ii  systemd-container  230-7
ii  systemd-ui 3-4

Versions of packages systemd is related to:
ii  udev  230-6

-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
NAutoVTs=6
ReserveVT=6
KillUserProcesses=true
KillExcludeUsers=root
InhibitDelayMaxSec=5
HandlePowerKey=poweroff
IdleAction=ignore
RemoveIPC=yes


-- no debconf information
[EXTENDED]   /lib/systemd/system/systemd-resolved.service -> 
/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
[EXTENDED]   /lib/systemd/system/systemd-timesyncd.service -> 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[EXTENDED]   /lib/systemd/system/rc-local.service -> 
/lib/systemd/system/rc-local.service.d/debian.conf

3 overridden configuration files found.
==> /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket

==> 
/var/lib/systemd/deb-systemd-helper-enabled/netfilter-persistent.service.dsh-also
 <==
/etc/systemd/system/multi-user.target.wants/netfilter-persistent.service

==> /var/lib/systemd/deb-systemd-helper-enabled/cgmanager.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/cgmanager.service

==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/ssh.service
/etc/systemd/system/sshd.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sysinit.target.wants/console-setup.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sysinit.target.wants/keyboard-setup.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sysinit.target.wants/lvm2-lvmetad.socket
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/ulogd2.service.dsh-also <==
/etc/systemd/system/ulogd.service
/etc/systemd/system/multi-user.target.wants/ulogd2.service

==> /var/lib/systemd/deb-systemd-helper-enabled/netscript.service.dsh-also <==
/etc/systemd/system/basic.target.wants/netscript.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/suspend.target.wants/anacron-resume.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation-early.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/default.target.wants/watchdog.service
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/epmd.service.dsh-also <==
/etc/systemd/system/sockets.target.wants/epmd.socket
/etc/systemd/system/multi-user.target.wants/epmd.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/rpcbind.socket 
<==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/acpid.socket 
<==

==> 

Bug#830721: Failed to load module "nv" (module does not exist, 0)

[Karsten Malcher]

Package: nvidia-driver
Version: 340.96-1
Severity: normal


Hello,

i changed the card from ATI to NVIDIA after the ATI card died.
After that i uninstalled all ATI stuff.
Then i reinstalled the xserver and the nvidia-driver.
It says it was compiling the nvidia driver and did report no error.

But it is not working - there is no driver!

Why graphics is such a pain in original Debian?
When i boot Knoppix i always have a running X!

Cheers
Karsten


-- Package-specific info:
uname -a:
Linux PC8 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1 (2016-07-04) x86_64 GNU/Linux

/proc/version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian
3.16.36-1 (2016-07-04)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.125  Mon Dec  1 19:58:28 
PST 2014
GCC version:  gcc version 4.8.4 (Debian 4.8.4-1)

lspci 'VGA compatible controller [0300]':
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 
430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [128 v1] Power Budgeting 
Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=024 
Kernel driver in use: nvidia

dmesg:
[0.00] AGP: No AGP bridge found
[0.00] AGP: Checking aperture...
[0.00] AGP: No AGP bridge found
[0.00] AGP: Node 0: aperture [bus addr 0x4d9a00-0x4d9bff] (32MB)
[0.00] Console: colour VGA+ 80x25
[0.201784] vgaarb: setting as boot device: PCI::02:00.0
[0.201784] vgaarb: device added: 
PCI::02:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.201784] vgaarb: loaded
[0.201784] vgaarb: bridge control possible :02:00.0
[0.926641] Linux agpgart interface v0.103
[4.832218] snd_hda_intel :02:00.1: Handle VGA-switcheroo audio client
[4.962472] nvidia: module license 'NVIDIA' taints kernel.
[4.986801] vgaarb: device changed decodes: 
PCI::02:00.0,olddecodes=io+mem,decodes=none:owns=none
[4.987257] [drm] Initialized nvidia-drm 0.0.0 20140818 for :02:00.0 on 
minor 0
[4.987263] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  304.125  Mon Dec 
 1 19:58:28 PST 2014
[5.620508] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:02.0/:02:00.1/sound/card0/input7
[5.620575] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:02.0/:02:00.1/sound/card0/input8
[5.620637] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:02.0/:02:00.1/sound/card0/input9
[5.620695] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:02.0/:02:00.1/sound/card0/input10

Device node permissions:
crw-rw+ 1 root video 226,   0 Jul 10 20:11 /dev/dri/card0
crw-rw+ 1 root video 195,   0 Jul 10 20:11 /dev/nvidia0
crw-rw+ 1 root video 195, 255 Jul 10 20:11 /dev/nvidiactl
video:x:44:karsten,multimedia

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jul 10 19:56 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Jul 10 19:56 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   41 Jul 10 19:56 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu ->
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   41 Jul 10 19:56 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu ->
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Jul 10 19:56 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Jul 10 19:56 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   50 Jul 10 19:56 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   50 Jul 10 19:56 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   47 Jul 10 19:56 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu ->
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 root root   47 Jul 10 19:56 

Bug#830720: tripwire: FTBFS on !linux since the libc packages are named differently

[Andreas Beckmann]

Source: tripwire
Version: 2.4.3.1-1
Severity: important

tripwire now FTBFS on kfreebsd-any. This is a regression intruced by the
fix for #769347 "tripwire: statically linked against libc6 without a
Built-Using: field". The libc packages are called differently on
kfreebsd-* (and hurd-*), so version retrieval fails and generates an
invalid Build-Using field:

https://buildd.debian.org/status/fetch.php?pkg=tripwire=kfreebsd-amd64=2.4.3.1-1=1463053619

  dh_gencontrol -- -VBuilt-Using="libc6 (= ), gcc-6 (= 6.1.1-2), "
  dpkg-gencontrol: warning: Depends field of package tripwire: unknown 
substitution variable ${shlibs:Depends}
  dpkg-gencontrol: warning: can't parse dependency libc6 (= )
  dpkg-gencontrol: error: error occurred while parsing Built-Using field: libc6 
(= ), gcc-6 (= 6.1.1-2), 

Also the Built-Using field should reference source packages instead of
binary packages. I.e. glibc instead of libc6.


Andreas

Bug#830713: digikam: Missing dependancy on libjasper

[Steve M. Robbins]

On Sunday, July 10, 2016 5:07:08 PM CDT you wrote:
> Package: digikam
> Version: 4:4.14.0-5+b1
> Severity: normal
> 
> Dear Maintainer,
> 
> Digikam is missing a dependancy on libjasper. Without this package
> installed, it will not start:
> 
> digikam: error while loading shared libraries: libjasper.so.1: cannot
> open shared object file: No such file or directory

The build-time check for Jasper was removed in revision -5 and the rev -5+b1 
build for amd [1] shows jasper was not used:

--  libjasper found.. NO  (optional)
--  digiKam will be compiled without JPEG2000 support.
--  Please install the libjasper (version >= 1.7.0) development package.

[1] https://buildd.debian.org/status/fetch.php?
pkg=digikam=amd64=4%3A4.14.0-5%2Bb1=1467109625


So I'm puzzled by your report.  As a test, I just downloaded the package, 
extracted digikam, and verified that it is not linked:

steve@riemann{Downloads}dpkg-deb --extract digikam_4.14.0-5+b1_amd64.deb dk
steve@riemann{Downloads}ldd dk/usr/bin/digikam |grep -i jasper
steve@riemann{Downloads}

Additionally, I installed it onto a machine without libjasper1 and it runs for 
me.  Are you certain you are running rev -5+b1?  


-Steve


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

Bug#830719: Document the removal of upstart, suggest switch to supported init

[Michael Biebl]

Package: release-notes
Severity: normal

The upstart init system has been removed from unstable/testing, so it
looks like it won't be part of the upcoming stretch release.
I raised this issue on debian-devel [1] and one recommendation was, that
this fact should be mentioned in the release notes. We should suggest
that users switch to a supported alternative because post-stretch it's
likely that maintainers start removing native upstart jobs.

Regards,
Michael

[1] https://lists.debian.org/debian-devel/2016/06/msg00025.html
-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#830717: kio: Can’t view directories.

[Diederik de Haas]

On zondag 10 juli 2016 20:12:58 CEST Nicolas Patrois wrote:
> Gwenview can’t read the content of directories, klauncher complains about
> /usr/lib/i386-linux-gnu/qt5/plugins/kf5/kio/file.so but this file is here.

This seems to be another case of mixed framework package versions, 5.22 en 
5.23.

Can you try whether the fix described in https://lists.debian.org/debian-kde/
2016/07/msg00065.html fixes your issue too?

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

Bug#830718: nvidia-kernel-dkms: dkms builds nvidia kernel modules without module_layout version

[Peter Keel]

Package: nvidia-kernel-dkms
Version: 367.27-1
Severity: serious
Justification: 6

Dear Maintainer,

Installing a new kernel 4.6.3 (self-compiled), and installing the
experimental nvidia-drivers a few days later, led to the drivers
compiled without module versions. 


Commandline used: 
dkms install nvidia-current -v 367.27 -k 4.6.3 --force --verbose 

Note that this was working on the earlier 4.5.7 kernel for which the
symbols were generated. So I expect either compiler or compile-chain
to be the culprit. 


What happened is this: 

/lib/modules/4.6.3/updates/dkms# modprobe --dump-modversions nvidia-current.ko 
/lib/modules/4.6.3/updates/dkms#

There are no versions. Normal modules (ALSO dkms ones, for the same kernel)
look like this: 

/lib/modules/4.6.3/updates/dkms# modprobe --dump-modversions compat_xtables.ko 
0x83ca59d8  module_layout
0x449ad0a7  memcmp
/lib/modules/4.6.3/updates/dkms#

   * What was the outcome of this action?

[   68.125562] nvidia: no symbol version for module_layout

   * What outcome did you expect instead?

[  978.452077] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  367.27  Thu Jun  
9 18:53:27 PDT 2016

(This I actually did by allowing the kernel to force-load modules; and to 
load the same unversioned module via "modprobe --force" -- not a 
sustainable solution. 


-- Package-specific info:
uname -a:
Linux malaclypse 4.6.3 #3 SMP PREEMPT Sun Jul 10 19:25:09 CEST 2016 x86_64 
GNU/Linux

/proc/version:
Linux version 4.6.3 (root@malaclypse) (gcc version 5.4.0 20160609 (Debian 
5.4.0-6) ) #3 SMP PREEMPT Sun Jul 10 19:25:09 CEST 2016

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.27  Thu Jun  9 18:53:27 PDT 
2016
GCC version:  gcc version 5.4.0 20160609 (Debian 5.4.0-6) 

lspci 'VGA compatible controller [0300]':
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM206 [GeForce GTX 
960] [10de:1401] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GM206 [GeForce GTX 960] [1043:8528]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.301582] vgaarb: setting as boot device: PCI::02:00.0
[0.301825] vgaarb: device added: 
PCI::02:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.302071] vgaarb: loaded
[0.302313] vgaarb: bridge control possible :02:00.0
[0.703278] input: HDA NVidia HDMI as 
/devices/pci:00/:00:1c.0/:02:00.1/sound/card1/input9
[0.703788] input: HDA NVidia HDMI as 
/devices/pci:00/:00:1c.0/:02:00.1/sound/card1/input10
[   16.719776] nvidia: no symbol version for module_layout
[   20.015902] nvidia: no symbol version for module_layout
[   20.217410] nvidia: no symbol version for module_layout
[   66.328866] nvidia: no symbol version for module_layout
[   66.621957] nvidia: no symbol version for module_layout
[   67.316399] nvidia: no symbol version for module_layout
[   67.518177] nvidia: no symbol version for module_layout
[   67.752621] nvidia: no symbol version for module_layout
[   68.125562] nvidia: no symbol version for module_layout
[  966.013512] nvidia: no symbol version for module_layout
[  978.445325] nvidia: module_layout: kernel tainted.
[  978.445820] nvidia: module license 'NVIDIA' taints kernel.
[  978.451295] vgaarb: device changed decodes: 
PCI::02:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[  978.451818] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 251
[  978.452077] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  367.27  Thu Jun  
9 18:53:27 PDT 2016
[ 1029.698669] nvidia: no symbol version for module_layout
[ 1030.206358] nvidia: no symbol version for module_layout
[ 1194.668680] nvidia: no symbol version for module_layout
[ 1194.737218] nvidia: no symbol version for module_layout
[ 1233.295775] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  367.27  Thu Jun  9 18:24:10 PDT 2016
[ 1240.223880] [drm] [nvidia-drm] [GPU ID 0x0200] Loading driver
[ 1244.695924] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 
250
[ 1253.431488] nvidia-modeset: Allocated GPU:0 
(GPU-54f639d8-fa76-0a78-802e-f2ecb47445f1) @ PCI::02:00.0

Device node permissions:
crw-rw+ 1 root video 226,   0 Jul 10 19:54 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Jul 10 19:54 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Jul 10 19:54 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Jul 10 19:50 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Jul 10 19:50 /dev/nvidiactl
video:x:44:vdr,seegras,mythtv

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 root root 3814 Oct  6  2015 /etc/X11/xorg.conf
lrwxrwxrwx 1 root root   15 Apr 26 21:08 /etc/alternatives/glx -> 

Bug#814352: ITP: veracrypt -- Cross-platform on-the-fly encryption

[Mike Gabriel]

Control: close -1
Control: tags -1 wontfix

Hi Eriberto,

On  So 10 Jul 2016 00:05:12 CEST, Eriberto Mota wrote:


Hi,

What is the current status of this package?

Regards,

Eriberto


Unfortunately, the ftp master team rejected the upload due to the  
dodgy license history of Veracrypt / Truecrypt:


On  Fr 08 Jul 2016 02:00:09 CEST, Thorsten Alteholz wrote:


Hi Mike,

unfortunately I have to reject your package.
According to [1] "(...)TrueCrypt seems to be reserving the right to sue
any licensee for copyright infringement, no matter whether they comply
with the conditions of the license or not. Based on this, our counsel
advised that above and beyond being non-free, software under this
license is not safe to use. (...)"

So as Veracrypt is basically licensed with the TrueCrypt license, I think
it is better for Debian to not distribute such software, even in non-free.

 Thorsten


Thus closing this ITP and tagging as "won't fix". Unfortunately...

Mike


[1]  
https://lists.freedesktop.org/archives/distributions/2008-October/000276.html


--

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

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



pgpGrVtJb27GA.pgp
Description: Digitale PGP-Signatur

Bug#830244: auditd: Crash at startup

[cruncher]

Package: auditd
Version: 1:2.6.3-1
Followup-For: Bug #830244

Addition:
I noticed that today the service suddenly started, but only with the standard
rules file.
As soon as i add anythign to it or use my own separate rules file, the service
wont start anymore.

But i found out that when using "log_format = ENRICHED" (instead of RAW) then
the service starts normally.
Maybe this could be used as a workaround until it is fixed.



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

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

Versions of packages auditd depends on:
ii  gawk 1:4.1.3+dfsg-0.1
ii  init-system-helpers  1.37
ii  libaudit11:2.6.3-1
ii  libauparse0  1:2.6.3-1
ii  libc62.23-1
ii  libgssapi-krb5-2 1.14.2+dfsg-1
ii  libkrb5-31.14.2+dfsg-1
ii  libwrap0 7.6.q-25
ii  lsb-base 9.20160629
ii  mawk 1.3.3-17

auditd recommends no packages.

Versions of packages auditd suggests:
pn  audispd-plugins  

-- Configuration Files:
/etc/audisp/audispd.conf [Errno 13] Permission denied: 
u'/etc/audisp/audispd.conf'
/etc/audisp/plugins.d/af_unix.conf [Errno 13] Permission denied: 
u'/etc/audisp/plugins.d/af_unix.conf'
/etc/audisp/plugins.d/syslog.conf [Errno 13] Permission denied: 
u'/etc/audisp/plugins.d/syslog.conf'
/etc/audit/audit-stop.rules [Errno 13] Permission denied: 
u'/etc/audit/audit-stop.rules'
/etc/audit/auditd.conf [Errno 13] Permission denied: u'/etc/audit/auditd.conf'
/etc/audit/rules.d/audit.rules [Errno 13] Permission denied: 
u'/etc/audit/rules.d/audit.rules'

-- no debconf information

Bug#830717: kio: Can’t view directories.

[Nicolas Patrois]

Package: kio
Version: 5.22.0-1
Severity: important

Dear Maintainer,

Gwenview can’t read the content of directories, klauncher complains about 
/usr/lib/i386-linux-gnu/qt5/plugins/kf5/kio/file.so but this file is here.

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

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

Versions of packages kio depends on:
ii  libacl1   2.2.52-3
ii  libc6 2.22-13
ii  libgcc1   1:6.1.1-8
ii  libgssapi-krb5-2  1.14.2+dfsg-1
ii  libkf5archive55.23.0-1
ii  libkf5codecs5 5.23.0-1
ii  libkf5completion5 5.23.0-1
ii  libkf5configcore5 5.23.0-1
ii  libkf5configwidgets5  5.22.0-1
ii  libkf5coreaddons5 5.23.0-1
ii  libkf5dbusaddons5 5.23.0-1
ii  libkf5i18n5   5.22.1-1
ii  libkf5itemviews5  5.23.0-1
ii  libkf5kiocore55.22.0-1
ii  libkf5kiontlm55.22.0-1
ii  libkf5kiowidgets5 5.22.0-1
ii  libkf5notifications5  5.23.0-1
ii  libkf5service-bin 5.22.0-1
ii  libkf5service55.22.0-1
ii  libkf5solid5  5.23.0-1
ii  libkf5textwidgets55.22.0-1
ii  libkf5wallet-bin  5.22.0-1
ii  libkf5wallet5 5.22.0-1
ii  libkf5widgetsaddons5  5.23.0-1
ii  libkf5windowsystem5   5.23.0-1
ii  libqt5core5a  5.6.1+dfsg-3
ii  libqt5dbus5   5.6.1+dfsg-3
ii  libqt5gui55.6.1+dfsg-3
ii  libqt5network55.6.1+dfsg-3
ii  libqt5script5 5.6.1+dfsg-2
ii  libqt5widgets55.6.1+dfsg-3
ii  libqt5x11extras5  5.6.1-2
ii  libqt5xml55.6.1+dfsg-3
ii  libstdc++66.1.1-8
ii  libxml2   2.9.3+dfsg1-1.2
ii  libxslt1.11.1.28-4

kio recommends no packages.

kio suggests no packages.

-- no debconf information

Bug#830716: tiger: 1:3.2.3-14.1 NMU

[Francois Marier]

Package: tiger
Version: 1:3.2.3-14.1
Severity: normal
Tags: patch

Attached is the debdiff for the 3.2.3-14.1 NMU I uploaded back in January.
Apologies for forgetting to open a bug.

It addresses bug 791352.

Francois

-- 
https://fmarier.org/
diff -u tiger-3.2.3/debian/changelog tiger-3.2.3/debian/changelog
--- tiger-3.2.3/debian/changelog
+++ tiger-3.2.3/debian/changelog
@@ -1,3 +1,10 @@
+tiger (1:3.2.3-14.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Teach tiger about tracefs (Closes: #791352)
+
+ -- Francois Marier   Sat, 16 Jan 2016 20:41:02 -0800
+
 tiger (1:3.2.3-14) unstable; urgency=low
 
   * debian/control: Add Vcs-Browser and Vcs-Git
diff -u tiger-3.2.3/systems/Linux/2/gen_mounts tiger-3.2.3/systems/Linux/2/gen_mounts
--- tiger-3.2.3/systems/Linux/2/gen_mounts
+++ tiger-3.2.3/systems/Linux/2/gen_mounts
@@ -69,6 +69,7 @@
 # Linux/2/gen_mounts - 22/11/2015 - Fix typo in sshfs definition (Debian bug 7680867)
 # - Added aufs (Debian bug 781171)
 # - Added fuse.s3fs (Debian bug 799753)
+# Linux/2/gen_mounts - 05/12/2015 - Added tracefs (Debian bug 791352)
 #--
 #
 
@@ -210,6 +211,7 @@
   [ "$1" = "vmblock" ] && LOCAL=1   # Vmware filesystem
   [ "$1" = "debugfs" ] && LOCAL=1   # Debugging filesystem see 
 # http://lwn.net/Articles/115405/
+  [ "$1" = "tracefs" ] && LOCAL=1
   [ "$1" = "configfs" ] && LOCAL=1
   [ "$1" = "davfs" ] && LOCAL=1
   [ "$1" = "pstore" ] && LOCAL=1# Platform dependen persisten storage

Bug#827842: release.debian.org: nmu: ncurses_6.0+20160319-2

[Sven Joachim]

On 2016-06-22 08:11 +0200, Julien Cristau wrote:

> On Tue, Jun 21, 2016 at 17:53:40 +0200, Sven Joachim wrote:
>
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: binnmu
>> 
>> Due to findutils bug #827724, ncurses-bin ended up empty on various
>> architectures, see #827797.  Rebuilding with non-broken findutils should
>> fix that.
>> 
>> nmu ncurses_6.0+20160319-2 . amd64 i386 mips powerpc kfreebsd-i386
>> . unstable . -m "Rebuild with findutils 4.6.0+git+20160517-4"
>> 
>> The amd64 package is not actually affected, but having amd64 and i386
>> out of sync is going to cause a lot of complaints from multiarch users
>> that I'd rather not deal with.
>> 
> jcristau@wuiet:~$ wb nmu ncurses . ANY -x32 . -m 'Rebuild with fixed
> findutils (#827724)' --extra-depends 'findutils (>=
> 4.6.0+git+20160517-4)'
>
> Scheduled.

Thanks.  Unfortunately, ncurses is now in BD-Uninstallable state on
alpha and hurd-i386, because findutils FTBFS there (the broken findutils
versions also did not build on these arches).

Could you please take out the findutils Extra-Depends?

Cheers,
   Sven

Bug#815488: bcpp: FTBFS on hurd-i386: error: 'PATH_MAX' was not declared in this scope

[Andreas Beckmann]

Followup-For: Bug #815488
Control: reassign -1 ftp.debian.org
Control: severity -1 normal
Control: retitle -1 RM: bcpp [hurd-i386] -- RoQA; FTBFS: PATH_MAX undeclared

No maintainer reaction so far, requesting the decrufting.


Andreas

Bug#830715: musescore not installable

[Sachin]

Package: musescore
Version: 2.0.2+dfsg-2
Severity: normal

Dear Maintainer,

Musescore is not installable in testing and sid because qtbase-abi-5-5-1 is not 
available.


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

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

Versions of packages musescore depends on:
ii  desktop-file-utils   0.23-1
ii  libasound2   1.1.1-2
ii  libc62.22-13
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.1.1-8
ii  libogg0  1.3.2-1
ii  libportaudio219+svn20140130-1
ii  libpulse08.0-2+b2
pn  libqt5concurrent5
ii  libqt5core5a 5.6.1+dfsg-3
ii  libqt5designer5  5.6.1-2
ii  libqt5gui5   5.6.1+dfsg-3
ii  libqt5help5  5.6.1-2
ii  libqt5network5   5.6.1+dfsg-3
ii  libqt5printsupport5  5.6.1+dfsg-3
ii  libqt5qml5   5.6.1-4
ii  libqt5quick5 5.6.1-4
pn  libqt5quickwidgets5  
ii  libqt5sql5   5.6.1+dfsg-3
ii  libqt5sql5-sqlite5.6.1+dfsg-3
ii  libqt5svg5   5.6.1-2
ii  libqt5test5  5.6.1+dfsg-3
ii  libqt5webkit55.6.1+dfsg-4
ii  libqt5widgets5   5.6.1+dfsg-3
ii  libqt5xml5   5.6.1+dfsg-3
pn  libqt5xmlpatterns5   
ii  libsndfile1  1.0.25-10
ii  libstdc++6   6.1.1-8
ii  libvorbis0a  1.3.5-3
ii  libvorbisfile3   1.3.5-3
pn  musescore-common 
pn  qml-module-qtquick-controls  
pn  qml-module-qtquick-layouts   
pn  qml-module-qtquick2  
pn  qtbase-abi-5-5-1 
ii  shared-mime-info 1.6-1
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages musescore recommends:
ii  pulseaudio-utils  8.0-2+b2

Versions of packages musescore suggests:
pn  fluid-soundfont-gm  
pn  timgm6mb-soundfont  

Bug#830163: isoquery: : French manpage translation

[Dr. Tobias Quathamer]

Control: tag -1 pending
Control: found -1 3.0.1-1

On Wed, Jul 06, 2016 at 10:11:50PM +0200, Baptiste Jammet wrote:
> Dear Maintainer,
> 
> Please find attached the updated manpage translation for isoquery,
> proofread by the french l10n team.

Hi,

thanks a lot for this update, it's now in git and will be part of the
next release.

-- 
Regards,
Tobias


signature.asc
Description: PGP signature

Bug#830714: tiger: 1:3.2.3-14.2 NMU

[Francois Marier]

Package: tiger
Version: 1:3.2.3-14.2
Severity: normal
Tags: patch

Attached is the debdiff for the 3.2.3-14.2 NMU I prepared. It addresses bug 
829643.

I uploaded the packaged I prepared to the DELAYED/7 queue.

Francois

-- 
https://fmarier.org/
diff -u tiger-3.2.3/debian/changelog tiger-3.2.3/debian/changelog
--- tiger-3.2.3/debian/changelog
+++ tiger-3.2.3/debian/changelog
@@ -1,3 +1,10 @@
+tiger (1:3.2.3-14.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Teach tiger about fuse.lxcfs (Closes: #829643)
+
+ -- Francois Marier   Sun, 10 Jul 2016 10:21:22 -0700
+
 tiger (1:3.2.3-14.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u tiger-3.2.3/systems/Linux/2/gen_mounts tiger-3.2.3/systems/Linux/2/gen_mounts
--- tiger-3.2.3/systems/Linux/2/gen_mounts
+++ tiger-3.2.3/systems/Linux/2/gen_mounts
@@ -152,6 +152,7 @@
   [ "$1" = "fuse.gvfs-fuse-daemon" ] && LOCAL=1 # Used in Ubuntu 'hardy'
   [ "$1" = "fuse.gvfsd-fuse" ] && LOCAL=1   # Used in Ubuntu 13.10 (Saucy Salamander) replaces fuse.gvfs-fuse-daemon
   [ "$1" = "fuse.ltspfs" ] && LOCAL=0 		# Used by LTSP 5.x
+  [ "$1" = "fuse.lxcfs" ] && LOCAL=0
   [ "$1" = "ecryptfs" ] && LOCAL=0  # Encrypted filesystem used by ecryptfs-utils
   [ "$1" = "xenfs" ] && LOCAL=0 # Virtual fs for Xen
   [ "$1" = "cgroup" ] && LOCAL=0# General access point to Kernel Control Groups

Bug#817092: [Pkg-javascript-devel] Bug#817092: this browserified

[Jonas Smedegaard]

Quoting Pirate Praveen (2016-07-10 18:40:53)
> This is not a minified file, only browserified. Though ideally we 
> should browserify it in debian, grunt is still not packaged. Since its 
> still a human readable and modifiable format, I don't think DFSG 
> applies here.

The requirement of source format of redistributed code is not about it 
being possible/easy to edit by those receiving it¹, but about it being 
in the format preferred by _upstream_ to edit - e.g. for passing patches 
upstream.

If "browserifying" is a process simple to apply and revert, then ship 
the code _not_ browserified and browserify during install (yes, I 
understand that the tool upstream uses for that process is not yet in 
Debian - which either means you need to imitate that process or that it 
is _not such simple process).


 - Jonas


¹ If that was the case, then minified code - unlike compiled code - 
could be processed through a beatifier (e.g. "uglifyjs --beautify").

-- 
 * 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#820894: ocserv: RADIUS support not included

[Mike Miller]

On Wed, Apr 13, 2016 at 08:26:37 -0400, Tony Zhou wrote:
> It seems that RADIUS support is not included in the current release
> (0.11.1-1) of ocserv. When starting
> ocserv with configuration that uses radius for authentication, it gives
> the following error:
> 
> tony@vpn:~$ sudo ocserv -f -c /etc/ocserv/ocserv.conf
> Unknown or unsupported auth method:
> radius[config=/etc/radcli/radiusclient.conf]
> 
> Also, it seems that libradcli4 dependency has been removed. Please
> consider re-include radius support.

Confirmed, also shown in the build logs:

https://buildd.debian.org/status/fetch.php?pkg=ocserv=i386=0.11.1-1=1460003584

This is due to #820920, libradcli-dev does not install its pkg-config
file. Until that is fixed, ocserv could be built with RADCLI_CFLAGS and
RADCLI_LIBS specified explicitly as a workaround.

-- 
mike

Bug#830161: isoquery: : French translation

[Dr. Tobias Quathamer]

Control: found -1 3.0.1-1
Control: tag -1 pending

On Wed, Jul 06, 2016 at 10:08:47PM +0200, Baptiste Jammet wrote:
> Dear Maintainer,
> 
> Please find attached the updated po file for isoquery, 
> proofread by the french l10n team.

Hi,

thanks a lot for the update, it's now in git and will be part of the
next release.

-- 
Regards,
Tobias


signature.asc
Description: PGP signature

Bug#825974: [Pkg-mc-devel] Bug#825974: mc: subshell no longer sees correct terminal size

[Yury V. Zaytsev]

On Mon, 2016-06-06 at 21:30 -0400, Michael Gold wrote:
> 
> Thank you.  Reverting the linked changeset and applying that diff
> fixed
> the problem.  I've attached an automated regression test.  (If running
> without installing, prepend the build directory to $PATH.)

Oh wow, thank you very much! I've forwarded it upstream and I hope we'll
eventually get to integrating it into the check runnner.

-- 
Sincerely yours,
Yury V. Zaytsev

Bug#757760: debian-policy: please document build profiles

[Javier Serrano Polo]

On Sat, 09 Jul 2016 23:56:03 +0200 Johannes Schauer 
wrote:
> I'm CC-ing debian-dpkg@.

I cannot CC lists.debian.org. You will not see my messages in
https://lists.debian.org/debian-policy/2016/07/threads.html .

> I suspect you want to express "this package has to be built when no
> profiles are active as well as when the pkg.linux.zlib profile is
> active"?

Yes.

> If so, then why do you need the Build-Profiles field at all?

Because the package should not be built if other pkg.linux.* profiles
are active.

> What is your use case?

There is an introduction at https://bugs.debian.org/830524 . The goal is
to build a subset of binary packages. For instance, the linux source
package should have a way to build only linux-image-4.6.0-1-686 (profile
pkg.linux.686), only linux-image-4.6.0-1-rt-686-pae (profile
pkg.linux.rt-686-pae), etc. The nodebug profile would be useful to not
build *-dbg packages.

> > I gather that the Built-For-Profiles field is written to
> > DEBIAN/control

> Why do you want to avoid this field? Why would this be useful?

Binary packages should be exactly the same as if built without active
profiles. This helps making and checking a subset of reproducible
packages.


smime.p7s
Description: S/MIME cryptographic signature