Bug#834626: python-lockfile must build-depend on python{3,}-pbr >= 1.8

[Ben Finney]

Control: tags -1 confirmed pending

On 17-Aug-2016, Thomas Goirand wrote:

> Building a python-lockfile backport may fail if not using a
> backported version of PBR. This leads to this when building with PBR
> 0.8.2-1:
> 
> dh_auto_clean
> I: pybuild base:170: python2.7 setup.py clean 
> Download error on https://pypi.python.org/simple/pbr/: [Errno 111] Connection 
> refused -- Some packages may not be found!
> Couldn't find index page for 'pbr' (maybe misspelled?)
> Download error on https://pypi.python.org/simple/: [Errno 111] Connection 
> refused -- Some packages may not be found!
> No local packages or download links found for pbr>=1.8
> […]

Right, the upstream build system (in ‘setup.py’) declares the
versioned dependency, but the Debian source package does not.

I'll correct this in the next release of the package.

-- 
 \   “The future always arrives too fast, and in the wrong order.” |
  `\—Alvin Toffler |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#829640: iptables-persistent: diff for NMU version 1.0.4+nmu1

[gustavo panizzo (gfa)]

Control: tags 829640 + patch
Control: tags 829640 + pending

Dear maintainer,

I've prepared an NMU for iptables-persistent (versioned as 1.0.4+nmu1),
I'll look for an sponsor and upload it.

I worked with the git repo but I didn't push to alioth until you agree or the
updated package is on the archive.

I've tested this change on machines with different configurations IPv4,
IPv6, DCHP, SLAAC and it worked fine.
My firewall rules set the DROP policy, this change should not disrupt
any user that allows ESTABLISHED and RELATED connections.

Regards.

--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa
diff -Nru iptables-persistent-1.0.4/debian/changelog iptables-persistent-1.0.4+nmu1/debian/changelog
--- iptables-persistent-1.0.4/debian/changelog	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/debian/changelog	2016-08-21 13:05:39.0 +0800
@@ -1,3 +1,11 @@
+iptables-persistent (1.0.4+nmu1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Loads the firewall before network-pre.target, as suggested by systemd
+upstream. (Closes: #829640).
+
+ -- gustavo panizzo   Sun, 21 Aug 2016 13:05:39 +0800
+
 iptables-persistent (1.0.4) unstable; urgency=medium
 
   * [d52b9e] During flush, set policy before flushing rules (Closes: #749790)
diff -Nru iptables-persistent-1.0.4/debian/compat iptables-persistent-1.0.4+nmu1/debian/compat
--- iptables-persistent-1.0.4/debian/compat	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/debian/compat	2016-08-21 13:05:06.0 +0800
@@ -1 +1 @@
-7
+9
diff -Nru iptables-persistent-1.0.4/debian/control iptables-persistent-1.0.4+nmu1/debian/control
--- iptables-persistent-1.0.4/debian/control	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/debian/control	2016-08-21 13:05:06.0 +0800
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Jonathan Wiltshire 
 Build-Depends: debhelper (>= 7.0.50~), dh-systemd, po-debconf
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
 Vcs-Browser: http://anonscm.debian.org/cgit/collab-maint/iptables-persistent.git/
 Vcs-Git: git://anonscm.debian.org/collab-maint/iptables-persistent.git
 
diff -Nru iptables-persistent-1.0.4/debian/rules iptables-persistent-1.0.4+nmu1/debian/rules
--- iptables-persistent-1.0.4/debian/rules	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/debian/rules	2016-08-21 13:05:06.0 +0800
@@ -4,5 +4,5 @@
 	dh_installinit -- start 37 S . stop 37 0 1 6 .
 
 %:
-	dh --with systemd $@
+	dh $@ --with systemd
 
diff -Nru iptables-persistent-1.0.4/plugins/15-ip4tables iptables-persistent-1.0.4+nmu1/plugins/15-ip4tables
--- iptables-persistent-1.0.4/plugins/15-ip4tables	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/plugins/15-ip4tables	2016-08-21 13:05:06.0 +0800
@@ -35,8 +35,8 @@
 	if [ ! -f /proc/net/ip_tables_names ]; then
 		echo "Warning: skipping IPv4 (no modules loaded)"
 	elif [ -x /sbin/iptables-save ]; then
-touch /etc/iptables/rules.v4
-chmod 0640 /etc/iptables/rules.v4
+		touch /etc/iptables/rules.v4
+		chmod 0640 /etc/iptables/rules.v4
 		iptables-save > /etc/iptables/rules.v4
 		if [ $? -ne 0 ]; then
 			rc=1
diff -Nru iptables-persistent-1.0.4/plugins/25-ip6tables iptables-persistent-1.0.4+nmu1/plugins/25-ip6tables
--- iptables-persistent-1.0.4/plugins/25-ip6tables	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/plugins/25-ip6tables	2016-08-21 13:05:06.0 +0800
@@ -35,8 +35,8 @@
 	if [ ! -f /proc/net/ip6_tables_names ]; then
 		log_action_cont_msg "Warning: skipping IPv6 (no modules loaded)"
 	elif [ -x /sbin/ip6tables-save ]; then
-touch /etc/iptables/rules.v6
-chmod 0640 /etc/iptables/rules.v6
+		touch /etc/iptables/rules.v6
+		chmod 0640 /etc/iptables/rules.v6
 		ip6tables-save > /etc/iptables/rules.v6
 		if [ $? -ne 0 ]; then
 			rc=1
diff -Nru iptables-persistent-1.0.4/systemd/netfilter-persistent.service iptables-persistent-1.0.4+nmu1/systemd/netfilter-persistent.service
--- iptables-persistent-1.0.4/systemd/netfilter-persistent.service	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/systemd/netfilter-persistent.service	2016-08-21 13:05:39.0 +0800
@@ -1,7 +1,8 @@
 [Unit]
 Description=netfilter persistent configuration
 DefaultDependencies=no
-Before=network.target
+Before=network-pre.target
+Wants=network-pre.target
 Wants=systemd-modules-load.service local-fs.target
 After=systemd-modules-load.service local-fs.target
 


signature.asc
Description: PGP signature

Bug#834969: ITP: librt-extension-repeatticket-perl -- Perl module for repeating tickets in RT (Request Tracker) based on schedule

[Joost van Baal-Ilić]

Package: wnpp
Severity: wishlist

* Package name: librt-extension-repeatticket-perl
* URL : https://metacpan.org/release/RT-Extension-RepeatTicket
* License : GPL-2
  Description : Perl module for repeating tickets in RT (Request Tracker) 
based on schedule

 The RepeatTicket extension for the Request Tracker trouble-ticket tracking
 system allows you to set up recurring tickets so new
 tickets are automatically created based on a schedule. The new tickets are
 populated with the subject and initial content of the original ticket in the
 recurrence.
 .
 After you activate the plugin by adding it to your RT_SiteConfig.pm file, all
 tickets will have a Recurrence tab on the create and edit pages. To set up a
 repeating ticket, click the checkbox to "Enable Recurrence" and fill out the
 schedule for the new tickets.
 .
 New tickets are created when you initially save the recurrence, if new
 tickets are needed, and when your daily cron job runs the rt-repeat-ticket
 script.

I've chosen to name this package "librt-extension-repeatticket-perl", following
naming convention of CPAN packages.  I am aware of the rt4-extension-* packages
(like e.g. rt4-extension-calendar), but feel the name
librt-extension-repeatticket-perl is more suitable to fit in pkg-perl policy.
People looking for this package will find it anyway.

I'll work on the packaging using pkg-perl's git at Alioth
https://anonscm.debian.org/cgit/pkg-perl/packages/librt-extension-repeatticket-perl.git/
.

Bye,

Joost



signature.asc
Description: Digital signature

Bug#779970: ITP: corefx -- .NET Core Libraries

[Adam Baxter]

On Sun, 8 Mar 2015 10:55:59 -0300 Henrique de Moraes Holschuh
 wrote:
> Shouldn't this package and its sister packages be under a common prefix,
> such as dotnet-corefx ?
>
> namespacing is good.
>

I agree. If you look at http://www.dotnetfoundation.org/netcore, there
are 3 distinct packages mentioned.

FWIW - think about something like dotnet-corefx (although it could
also be libdotnet), dotnet-coreclr and dotnet-cli. Someone should ask
upstream at this point as they have already created unofficial
packages for some projects.

Hopping on this bug as it is probably required for #834756 (I have no
idea how to mark bugs as related).

--Adam

Bug#834968: apt-cacher: Fails to run due to curl errors

[Helge Kreutzmann]

Package: apt-cacher
Version: 1.7.13
Severity: normal

I wanted to use apt-cacher-ng. I installed it and set up the data as I
assumed appropriate.

However, when trying to "apt-get update" I get the following error:
root@samd:/var/log/apt-cacher# LC_ALL=C apt-get update
Ign:1 http://172.16.18.51:/debian testing InRelease
Ign:2 http://172.16.18.51:/debian testing Release
Ign:3 http://172.16.18.51:/debian testing/main amd64 Packages
Ign:4 http://172.16.18.51:/debian testing/main all Packages
Ign:5 http://172.16.18.51:/debian testing/main Translation-en
Ign:6 http://172.16.18.51:/debian testing/main Translation-de_DE
Ign:7 http://172.16.18.51:/debian testing/main Translation-de
Ign:8 http://172.16.18.51:/debian testing/main amd64 DEP-11 Metadata
Ign:9 http://172.16.18.51:/debian testing/main all DEP-11 Metadata
Ign:10 http://172.16.18.51:/debian testing/main DEP-11 64x64 Icons
Ign:11 http://172.16.18.51:/debian testing/main amd64 Contents (deb)
Ign:12 http://172.16.18.51:/debian testing/main all Contents (deb)
Ign:3 http://172.16.18.51:/debian testing/main amd64 Packages
Ign:4 http://172.16.18.51:/debian testing/main all Packages
Ign:5 http://172.16.18.51:/debian testing/main Translation-en
Ign:6 http://172.16.18.51:/debian testing/main Translation-de_DE
Ign:7 http://172.16.18.51:/debian testing/main Translation-de
Ign:8 http://172.16.18.51:/debian testing/main amd64 DEP-11 Metadata
Ign:9 http://172.16.18.51:/debian testing/main all DEP-11 Metadata
Ign:10 http://172.16.18.51:/debian testing/main DEP-11 64x64 Icons
Ign:11 http://172.16.18.51:/debian testing/main amd64 Contents (deb)
Ign:12 http://172.16.18.51:/debian testing/main all Contents (deb)
Ign:3 http://172.16.18.51:/debian testing/main amd64 Packages
Ign:4 http://172.16.18.51:/debian testing/main all Packages
Ign:5 http://172.16.18.51:/debian testing/main Translation-en
Ign:6 http://172.16.18.51:/debian testing/main Translation-de_DE
Ign:7 http://172.16.18.51:/debian testing/main Translation-de
Ign:8 http://172.16.18.51:/debian testing/main amd64 DEP-11 Metadata
Ign:9 http://172.16.18.51:/debian testing/main all DEP-11 Metadata
Ign:10 http://172.16.18.51:/debian testing/main DEP-11 64x64 Icons
Ign:11 http://172.16.18.51:/debian testing/main amd64 Contents (deb)
Ign:12 http://172.16.18.51:/debian testing/main all Contents (deb)
Ign:3 http://172.16.18.51:/debian testing/main amd64 Packages
Ign:4 http://172.16.18.51:/debian testing/main all Packages
Ign:5 http://172.16.18.51:/debian testing/main Translation-en
Ign:6 http://172.16.18.51:/debian testing/main Translation-de_DE
Ign:7 http://172.16.18.51:/debian testing/main Translation-de
Ign:8 http://172.16.18.51:/debian testing/main amd64 DEP-11 Metadata
Ign:9 http://172.16.18.51:/debian testing/main all DEP-11 Metadata
Ign:10 http://172.16.18.51:/debian testing/main DEP-11 64x64 Icons
Ign:11 http://172.16.18.51:/debian testing/main amd64 Contents (deb)
Ign:12 http://172.16.18.51:/debian testing/main all Contents (deb)
Ign:3 http://172.16.18.51:/debian testing/main amd64 Packages
Ign:4 http://172.16.18.51:/debian testing/main all Packages
Ign:5 http://172.16.18.51:/debian testing/main Translation-en
Ign:6 http://172.16.18.51:/debian testing/main Translation-de_DE
Ign:7 http://172.16.18.51:/debian testing/main Translation-de
Ign:8 http://172.16.18.51:/debian testing/main amd64 DEP-11 Metadata
Ign:9 http://172.16.18.51:/debian testing/main all DEP-11 Metadata
Ign:10 http://172.16.18.51:/debian testing/main DEP-11 64x64 Icons
Ign:11 http://172.16.18.51:/debian testing/main amd64 Contents (deb)
Ign:12 http://172.16.18.51:/debian testing/main all Contents (deb)
Err:3 http://172.16.18.51:/debian testing/main amd64 Packages
  502  apt-cacher: libcurl error: Peer certificate cannot be authenticated with 
given CA certificates
Ign:4 http://172.16.18.51:/debian testing/main all Packages
Ign:5 http://172.16.18.51:/debian testing/main Translation-en
Ign:6 http://172.16.18.51:/debian testing/main Translation-de_DE
Ign:7 http://172.16.18.51:/debian testing/main Translation-de
Ign:8 http://172.16.18.51:/debian testing/main amd64 DEP-11 Metadata
Ign:9 http://172.16.18.51:/debian testing/main all DEP-11 Metadata
Ign:10 http://172.16.18.51:/debian testing/main DEP-11 64x64 Icons
Ign:11 http://172.16.18.51:/debian testing/main amd64 Contents (deb)
Ign:12 http://172.16.18.51:/debian testing/main all Contents (deb)
Reading package lists... Done
W: The repository 'http://172.16.18.51:/debian testing Release' does not 
have a Release file.
N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
E: Failed to fetch 

Bug#832801: [mlt_pool] out of memory

[Kingsley G. Morse Jr.]

Oops!

I forgot to mention that

[mlt_pool] out of memory

also appears on the console when kdenlive hangs.

Sorry,
Kingsley

-- 
Time is the fire in which we all burn.

Bug#833419: downgrading midori 0.5.12~wk2-exp1 to 0.5.11-ds1-4 makes it work on Thinkpad R32

[Sergio Durigan Junior]

On Sunday, August 21 2016, 積丹尼 Dan Jacobson wrote:

> OK downgrading 0.5.12~wk2-exp1 to 0.5.11-ds1-4 makes it work on Thinkpad R32.

Good to know.  Keep in mind that 0.5.11-ds1-4 is compiled against
GTK-2 and WebKit 1, which the experimental one is compiled against GTK-3
and WebKit 2.  I'm not saying Midori is not the culprit of your bug, but
this gives a lot of options for culprits...

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Bug#834898: propellor: problem with the new gpg2

[Johannes Schauer]

Hi,

Quoting Sean Whitton (2016-08-20 19:58:49)
> On Sat, Aug 20, 2016 at 06:56:59PM +0200, Johannes Schauer wrote:
> > You might want to open another bug against propellor to ask it not to 
> > generate
> > the key anymore if the propellor maintainers agree that that they don't 
> > want to
> > support squeeze chroots anymore.
> 
> We've got one open here: 
> http://propellor.branchable.com/todo/updates_for_sbuild_0.70.0-1/

that page conflates two "issues" which roughly happened at the same time:

 1. gnupg2 went from experimental to unstable replacing gnupg1 as the default
implementation. This lead to incompatibilities between generated key pairs as
well as problems with remaining gpg-agent versions.

 2. apt stopped depending on gnupg. This meant that gpg wasn't available
anymore in the chroot and thus, users who still wanted to do signing had to
install it manually or disable signing.

So in fact, sbuild never ever installed gnupg into the chroot. It just so
happened that äround the time that sbuild 0.70.0 was released, apt stopped
depending on it in unstable and thus there is no gnupg anymore in Debian
unstable chroots. If you use sbuild to create a Debian jessie chroot then you
will see that it will contain gnupg as expected. This is not a property of
sbuild. Sbuild never did install gnupg into the chroot explicitly and thus
never stopped doing so either.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#832801: Moving kdenlive's config file fixed another bug

[Kingsley G. Morse Jr.]

For what it's worth, the workaround I described
above

$ rm .config/kdenliverc

basically seems to have fixed another bug.

Here's what happened:

$ export MESA_EXTENSION_OVERRIDE=-GL_ARB_draw_indirect ; kdenlive

  kdenlive->File->Open recent->(a kdenlive project)

  kdenlive->mute a track's audio

  move the mouse pointer to about 3 minutes on
  kdenlive's time line and click

  play the project starting at that point
  (if I recall correctlym by pressing the key
  board's space bar)

  It plays back in the preview monitor for a
  few seconds, then freezes.

  An error message *somewhat* *like*

nouveau: kernel rejected pushbuf: Invalid argument 
nouveau: ch3: krec 0 pushes 1 bufs 1 relocs 0
nouveau: ch3: buf  000b 0006 0006 

  appeared on the console, and

[883948.153199] nouveau :01:00.0: kdenlive[16711]: multiple 
instances of buffer 36 on validation list
[883948.153208] nouveau :01:00.0: kdenlive[16711]: validate_init
[883948.153210] nouveau :01:00.0: kdenlive[16711]: validate: -22

  appeared in dmesg.

I'm happy to report

a.) moving kdenlive's config file with

$ mv .config/kdenliverc tmp

seems to have worked around this bug too,
and

b.) I saved a copy of the config file.


My question?

Is there somethink like "lint"[1] that can check
kdenliverc files for corruption?

It seems to me that knowing which part of my
kdenliverc is corrupted might facilitate fixing
a bug or two.

Thanks,
Kingsley

[1] Lint (software)
https://en.wikipedia.org/wiki/Lint_%28software%29



-- 
Time is the fire in which we all burn.

Bug#834788: singularity-container: FTBFS: most platforms unsupported

[Aaron M. Ucko]

Yaroslav Halchenko  writes:

> Upstream has intent to look into compatibility with other
> architectures, next builds will remove some arch checks etc. So we
> will just stay inline with current policy for arch any, and possibly
> later restrict to a subset...

Great, thanks!

FTR, I don't favor a priori or otherwise gratuitous architecture
restrictions, just honest indications of the architectures on which
automatic builds have a reasonable prospect of succeeding now or at
least in the near future.  (I see no point in bothering to start
automatic builds on architectures for which a package would need a major
overhaul unless such an overhaul is actually forthcoming.)

-- 
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#833419: downgrading midori 0.5.12~wk2-exp1 to 0.5.11-ds1-4 makes it work on Thinkpad R32

[積丹尼 Dan Jacobson]

OK downgrading 0.5.12~wk2-exp1 to 0.5.11-ds1-4 makes it work on Thinkpad R32.

Bug#834967: say -t is different than /

[積丹尼 Dan Jacobson]

Package: aptitude
Version: 0.8.3-1
Severity: wishlist
File: /usr/share/man/man8/aptitude-curses.8.gz

At

   -t , --target-release 
   Set the release from which packages should be installed. For
   instance, "aptitude -t experimental ..."  will install packages
   from the experimental distribution unless you specify otherwise.

   This will affect the default candidate version of packages
   according to the rules described in apt_preferences(5).

   This corresponds to the configuration item APT::Default-Release.

please remind the user that -t is not the same as "/"

   To select a particular version of the package, append "="
   to the package name: for instance, "aptitude install apt=0.3.1".
   Similarly, to select a package from a particular archive, append
   "/" to the package name: for instance, "aptitude install
   apt/experimental". You cannot specify both an archive and a version
   for a package.

and that they should use "/" for cases like:


# apt-cache policy $@
midori:
  Installed: 0.5.12~wk2-exp1
  Candidate: 0.5.12~wk2-exp1
  Version table:
 *** 0.5.12~wk2-exp1 990
990 http://free.nchc.org.tw/debian experimental/main i386 Packages
100 /var/lib/dpkg/status
 0.5.11-ds1-4 500
500 http://free.nchc.org.tw/debian unstable/main i386 Packages
# aptitude -t unstable install $@
midori is already installed at the requested version (0.5.12~wk2-exp1)
midori is already installed at the requested version (0.5.12~wk2-exp1)
The following packages will NOT be UPGRADED:
  debian-reference-en  libcurses-perl{a}  libnet-ssleay-perl{a}
  libperl5.22{a} (R: libarchive-tar-perl, R: libcompress-raw-bzip2-perl, R: 
libcompress-raw-zlib-perl, R: libcompress-zlib-perl, R: libdigest-md5-perl, R: 
libdigest-sha-perl, R: libencode-perl, R: libio-compress-base-perl, R: 
libio-compress-bzip2-perl, R: libio-compress-perl, R: libio-compress-zlib-perl, 
R: libmime-base64-perl, R: libmodule-corelist-perl, R: libstorable-perl, R: 
libsys-syslog-perl, R: libthreads-perl, R: libthreads-shared-perl, R: 
libtime-hires-perl, R: libtime-piece-perl, R: perl, R: perl-base)
  libxml-libxml-perl{a}  perl  perl-base  perl-doc
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]

Current status: 0 (+0) broken, 8 (+0) upgradable, 52313 (+0) new.


# aptitude -t unstable reinstall $@
The following packages will be REINSTALLED:
  midori
The following packages will NOT be UPGRADED:
  debian-reference-en  libcurses-perl{a}  libnet-ssleay-perl{a}
  libperl5.22{a} (R: libarchive-tar-perl, R: libcompress-raw-bzip2-perl, R: 
libcompress-raw-zlib-perl, R: libcompress-zlib-perl, R: libdigest-md5-perl, R: 
libdigest-sha-perl, R: libencode-perl, R: libio-compress-base-perl, R: 
libio-compress-bzip2-perl, R: libio-compress-perl, R: libio-compress-zlib-perl, 
R: libmime-base64-perl, R: libmodule-corelist-perl, R: libstorable-perl, R: 
libsys-syslog-perl, R: libthreads-perl, R: libthreads-shared-perl, R: 
libtime-hires-perl, R: libtime-piece-perl, R: perl, R: perl-base)
  libxml-libxml-perl{a}  perl  perl-base  perl-doc
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 8 not 
upgraded.
Need to get 0 B/1,097 kB of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]
(Reading database ... 138223 files and directories currently installed.)
Preparing to unpack .../midori_0.5.12~wk2-exp1_i386.deb ...
Unpacking midori (0.5.12~wk2-exp1) over (0.5.12~wk2-exp1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Setting up midori (0.5.12~wk2-exp1) ...
Processing triggers for libc-bin (2.24-0experimental1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...

Current status: 0 (+0) broken, 8 (+0) upgradable, 52313 (+0) new.

Bug#834881: onboard: new upstream release 1.3.0

[Jeremy Bicha]

On Sat, Aug 20, 2016 at 5:49 AM, Ritesh Raj Sarraf  wrote:
> There's a new release of onboard, 1.3.0. This release sounds exciting
> from its NEWS entry, as it states initial Wayland support.

Sorry to disappoint you but… although onboard 1.3.0 looks nicer in
Wayland than onboard 1.2 does, I don't think it's actually usable in
Wayland yet.

Thanks,
Jeremy Bicha

Bug#829926: Bug#831144: Fix for the goffice-0.8 FTBFS

[Dmitry Smirnov]

On Friday, 19 August 2016 5:31:40 PM AEST Adrian Bunk wrote:
> the attached patch fixes #831144 (and #829926) in goffice-0.8.

Thank you very much, Adrian. :)

-- 
Cheers,
 Dmitry Smirnov.

---

The surest way to corrupt a youth is to instruct him to hold in higher
esteem those who think alike than those who think differently.
-- Friedrich Nietzsche


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

Bug#834966: mirror submission for mirror.lstn.net

[Logan Vig]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: mirror.lstn.net
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x 
Archive-ftp: /debian/
Archive-http: /debian/
Archive-rsync: debian/
CDImage-ftp: /debian-cd/
CDImage-http: /debian-cd/
CDImage-rsync: debian-cd/
IPv6: yes
Archive-upstream: mirrors.kernel.org
CDImage-upstream: mirrors.kernel.org
Updates: four
Maintainer: Logan Vig 
Country: US United States
Location: Dallas, TX
Sponsor: Limestone Networks Inc. https://www.limestonenetworks.com
Comment: Redundant mirror infrastructure in Dallas, TX with 40Gbps of aggregate 
internet connectivity.
 
 We can change the upstream mirror from kernel.org to whatever the project 
would prefer if necessary. Just let us know where we should be mirroring from. 
 
 

Bug#833115: Sponsoring hashid.

[Samuel Henrique]

Hi Hugo,

I've just created the git repo. and pushed hashid, i didn't push any tags
because i believe we will only tag hashid when we update the manpage, if i
did something wrong please feel free to point out.

Thanks.

Samuel Henrique O. P. [samueloph]

2016-08-20 17:19 GMT-03:00 Hugo Lefeuvre :

> Hi Samuel,
>
> > I believe the manpage update should be made in form of a PR on the
> > project's github page, and because it's not practical to wait for another
> > release, we can patch the new manpage with quilt until we get a new
> release.
>
> I agree. Let's patch the manpage in our Debian release and submit the diff
> to the upstream.
>
> Concerning signed releases, opening an issue on GitHub will be enough. This
> document[0] explains very well how to proceed to create signed releases, so
> it may be interesting to mention it.
>
> > I would be glad to have someone more experienced co-maintaining the
> > package, you're more than welcome.
> >
> > I'm already a member of the team and have my ssh keys ready, i will
> create
> > the package's repository and then we can work there, please feel free to
> > contact me.
> >
> > From what i see, we have to update the manpage and then we're ready to
> > release, we also have to ask for signed releases but this is a non-block
> > issue.
>
> Nice ! Well, drop me an e-mail when you're done with the repository and
> I'll do a last review before building & uploading the package.
>
> Cheers,
>  Hugo
>
> [0] https://wiki.debian.org/Creating%20signed%20GitHub%20releases
>
> --
>  Hugo Lefeuvre (hle)|www.owl.eu.com
> 4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E
>

Bug#834213: perlcritic: some code causes a perltidy.ERR file to be created or overwritten

[Paul Wise]

On Sat, 2016-08-20 at 17:37 +0200, Salvatore Bonaccorso wrote:

> I think perlcritic/perltidy is behaving here as documented.

I see, thanks for the pointers.

It seems like it would be possible to override the default using two
configuration files and one option to perlcritic, that has the downside
of disabling the users' own perlcritic/perltidy configuration files.
I also don't really want check-all-the-things to add many overrides
for other tools before they work in a safe-by-default way.

> One can argue that the default value is not a safe one, and rather
> pertidy should by default should use -se, and only if overwritten to
> write to a somefile.pl.ERR.

I agree that the default is not safe and should be changed.

> But if so, this would need to be changed upstream, and not diverged in
> the Debian packaging.

Would it be possible for you to forward the bug report upstream?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#834965: virtualbox-guest-utils: should not recommend virtualbox-guest-x11

[Afif Elghraoui]

Package: virtualbox-guest-utils
Version: 5.0.24-dfsg-1
Severity: normal

Hello,

The description of virtualbox-guest-utils perfectly fits the expectation of
what someone would want on text-only VM. Unfortunately, it recommends the
virtualbox-guest-x11 package, which pulls in a ton of graphics libraries as
dependencies. Using no-install-recommends is not ideal, because the other
recommends are important. I believe virtualbox-guest-x11 should just be
downgraded to "Suggests" for this package.

Thanks and regards
Afif

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

[Leo L. Schwab]

Package: python-coherence
Version: 0.6.6.2-8
Followup-For: Bug #824238

Seeing this here as well when trying to run the program
'upnp-inspector':


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

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


I have 'python-twisted' v16.3.0-1 installed, which pulls in
'python-twisted-core' v16.3.0-1.  'python-twisted-web' v16.3.0-1 is a dummy
package, whose description says that all the code has been moved to
'python-twisted-core'.

Schwab


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

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 python-coherence depends on:
ii  python2.7.11-2
ii  python-axiom  0.7.5-1
ii  python-configobj  5.0.6-2
ii  python-gst0.100.10.22-3
ii  python-louie  1.1-2
ii  python-pkg-resources  25.2.0-1
ii  python-tagpy  2013.1-5+b1
ii  python-zope.interface [python-zopeinterface]  4.2.0-2

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

Versions of packages python-coherence suggests:
ii  python-qt4  4.11.4+dfsg-2

-- no debconf information

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

[gregor herrmann]

Control: tag -1 + unreproducible

On Sun, 21 Aug 2016 01:41:03 +0200, Santiago Vila wrote:

> Package: src:libdaemon-generic-perl
> Version: 0.84-1
> Severity: serious
> 
> Dear maintainer:
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

Builds fine for me (amd64 sind cowbuilder).


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Diana Krall: The Boulevard Of Broken Dreams


signature.asc
Description: Digital Signature

Bug#828271: OpenSSL 1.10 compatibility

[Oleg Moskalenko]

I am going to add compatibility in the next package release. We still
have to support the previous OpenSSL versions, so that is somewhat
ugly.

Bug#834505: arm64 boot failure with large physical memory range

[Ben Hutchings]

On Fri, 2016-08-19 at 13:42 +0100, Leif Lindholm wrote:
> On Fri, Aug 19, 2016 at 12:50:49PM +0100, Ben Hutchings wrote:
> > 
> > > 
> > > > 
> > > > > 
> > > > > > 
> > > > > > > 
> > > > > > > everything using mozilla-js).
> > > > [...]
> > > > 
> > > > Could we possibly work around that by reducing
> > > > CONFIG_ARCH_MMAP_RND_BITS_MAX?  (That's not directly configurable; it
> > > > requires patching arch/arm64/Kconfig.)
> > > 
> > > I think this would be opening up a real can of worms. Not all sizes
> > > are supported by the architecture, and only certain VA_BITS/pagesize
> > > combinations work in the kernel.
> > > 
> > > We could switch to 42-bit VA, but that would require switching to 64K
> > > pagesize, which would be an even huger can.
> > 
> > I'm not suggesting using any unusual page table configuration. Just
> > reducing the ASLR range that is currently implied by a 48-bit VA.
> 
> But would that help anything?
> Even if you don't allocate to the top bits, if they're used for
> tagging, you'll still segfault.

I seem to remember that AArch64 has the ill-advised rule that VA bits
outside the range of the current page table format are ignored, so
presumably you're concerned that the code relies on this.  But since
other 64-bit architectures (at least x86, PowerPC and SPARC) behave
otherwise, I would expect semi-portable code to mask out the tag bits.

Ben.

-- 
Ben Hutchings
It's easier to fight for one's principles than to live up to them.


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

Bug#834956: ircd-irc2: please make the build reproducible

[Chris Lamb]

Kurt Roeckx wrote:

> > ++if test -n "$SOURCE_DATE_EPOCH"
> > ++then
> > ++  now=`LC_ALL=C date --utc --date="@$SOURCE_DATE_EPOCH"`
> > ++else
> > ++  now=`date`
> 
> That should probably also use LC_ALL=C

I usually patch that as:

a) I don't want to change existing behaviour so that it is easier,
politically, to get it merged upstream.

b) The value will vary on timezone and — of course — the current time,
so fixing the language doesn't really do much. It could even be argued
it therefore makes patch misleading in that it only goes "half way".

Hope that helps.


Regards,

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

Bug#832417: shotwell: Shotwell crashes when videos are imported

[Jörg Frings-Fürst]

tags 832417 + unreproducible
tags 832417 + moreinfo
thanks

Hello Karl,

thank you for spending your time helping to make Debian better with
this bug report. 


I have tested the import of mov video files several times without any
crash.

Please can you install the shotwell-dbg and debug the package? You find
a how-to at [1][2].

Or can you send me a link to one of the crashed video files?

Many thanks.


CU
Jörg


[1] 
http://www-numi.fnal.gov/offline_software/srt_public_context/WebDocs/Companion/intro_talks/gdb/gdb.html
[2] http://www.tutorialspoint.com/de/gnu_debugger/gdb_debugging_example1.htm
[3] https://wiki.debian.org/AutomaticDebugPackages


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:libdaemon-generic-perl
Version: 0.84-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Daemon::Generic
Writing MYMETA.yml and MYMETA.json
   dh_auto_build -i
make -j1

[... snipped ...]

ok 28 - process 31310 is alive - event
ok 29 - config ok - event
ok 30 - running
ok 31 - kill message
ok 32 - process is dead - event
ok 33 - config ok
ok 34 - not running
ok 35 - restart message - start - event
ok 36 - restart message - kill
ok 37 - restart message - start - event
ok 38 - check
ok 39 - stop message
ok 40 - check - event
ok 41 - start message - anyevent
ok 42 - pid
ok 43 - counter1 - anyevent
ok 44 - logged output
ok 45 - daemonized
ok 46 - reconfig message
ok 47 - counter2
ok 48 - process 31381 is alive - anyevent
ok 49 - config ok - anyevent
ok 50 - running
ok 51 - kill message
ok 52 - process is dead - anyevent
ok 53 - config ok
ok 54 - not running
ok 55 - restart message - start - anyevent
ok 56 - restart message - kill
ok 57 - restart message - start - anyevent
ok 58 - check
ok 59 - stop message
ok 60 - check - anyevent
ok 61 - finished
1..61
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/61 subtests 

Test Summary Report
---
t/daemon.t (Wstat: 256 Tests: 61 Failed: 1)
  Failed test:  4
  Non-zero exit status: 1
Files=1, Tests=61, 33 wallclock secs ( 0.03 usr  0.01 sys +  1.78 cusr  0.18 
csys =  2.00 CPU)
Result: FAIL
Failed 1/1 test programs. 1/61 subtests failed.
Makefile:858: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense, and the fact that I was
doing "dpkg-buildpackage -A" does not mean anything special.

I attach three build logs. There are more here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libdaemon-generic-perl.html

Thanks.

libdaemon-generic-perl_0.84-1_amd64-20160814T1442Z.gz
Description: application/gzip


libdaemon-generic-perl_0.84-1_amd64-20160816T2138Z.gz
Description: application/gzip


libdaemon-generic-perl_0.84-1_amd64-20160820T223119Z.gz
Description: application/gzip

Bug#834961: libvitacilina-perl: FTBFS too much often (configure fails)

[Santiago Vila]

Package: src:libvitacilina-perl
Version: 0.2-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl Makefile.PL INSTALLDIRS=vendor create_packlist=0
Checking if your kit is complete...
Looks good
'CREATE_PACKLIST' is not a known MakeMaker parameter name.
"\x{00c2}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00a1}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00c3}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00a9}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00c2}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00a1}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
"\x{00f0}" does not map to ascii at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm 
line 1187.
panic: sv_setpvn called with negative strlen -1 at 
/usr/share/perl/5.22/ExtUtils/MakeMaker.pm line 1187.
Close with partial character at /usr/share/perl/5.22/ExtUtils/MakeMaker.pm line 
1187.
Generating a Unix-style Makefile
Writing Makefile for Vitacilina
dh_auto_configure: perl Makefile.PL INSTALLDIRS=vendor create_packlist=0 
returned exit code 25
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense, and the fact that I was
doing "dpkg-buildpackage -A" does not mean anything special.

I attach two build logs. There are more here:

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

Thanks.

libvitacilina-perl_0.2-1_amd64-20160814T2319Z.gz
Description: application/gzip


libvitacilina-perl_0.2-1_amd64-20160819T153557Z.gz
Description: application/gzip

Bug#834964: testresources: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:testresources
Version: 1.0.0-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,python3
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions

[... snipped ...]

testresources.tests.test_test_resource.TestTestResource.testFinishedWithMarksNonDirty
 ... ok
testresources.tests.test_test_resource.TestTestResource.testFinishedWithResetsCurrentResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetActivityForResourceWithExtensions
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetActivityForResourceWithoutExtensions
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceCallsMakeResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceDoesntDirty
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceIncrementsUses
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceResetsUsedResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceReturnsMakeResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceSetsCurrentResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceTwiceReturnsIdenticalResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testInitiallyNoCurrentResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testInitiallyNotDirty 
... ok
testresources.tests.test_test_resource.TestTestResource.testInitiallyUnused ... 
ok
testresources.tests.test_test_resource.TestTestResource.testIsDirty ... ok
testresources.tests.test_test_resource.TestTestResource.testIsDirtyIsTrueIfDependenciesAreDirty
 ... ok
testresources.tests.test_test_resource.TestTestResource.testIsDirtyIsTrueIfDependenciesChanged
 ... ok
testresources.tests.test_test_resource.TestTestResource.testIsResetIfDependenciesAreDirty
 ... ok
testresources.tests.test_test_resource.TestTestResource.testRepeatedGetResourceCallsMakeResourceOnceOnly
 ... ok
testresources.tests.test_test_resource.TestTestResource.testResetActivityForResourceWithExtensions
 ... ok
testresources.tests.test_test_resource.TestTestResource.testResetActivityForResourceWithoutExtensions
 ... ok
testresources.tests.test_test_resource.TestTestResource.testResourceAvailableBetweenFinishedWithCalls
 ... ok
testresources.tests.test_test_resource.TestTestResource.testUnimplementedGetResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testUsedResourceResetBetweenUses
 ... ok
testresources.tests.test_test_resource.TestTestResource.testUsingTwiceMakesAndCleansTwice
 ... ok
testresources.tests.test_test_resource.TestTestResource.testneededResourcesClosure
 ... ok
testresources.tests.test_test_resource.TestTestResource.testneededResourcesDefault
 ... ok
testresources.tests.test_test_resource.TestTestResource.testneededResourcesDependenciesFirst
 ... ok
testresources.tests.test_test_resource.test_suite ... ok

==
FAIL: 
testresources.tests.test_optimising_test_suite.TestGraphStuff.testBasicSortTests
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/<>/testresources/tests/test_optimising_test_suite.py", 
line 527, in testBasicSortTests
"failed with permutation %s" % (permutation,))
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 356, in 
assertIn
self.assertThat(haystack, Contains(needle), message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: [test_three, test_one, test_two, 
test_four] not in [[test_one, test_two, test_three, test_four], [test_three, 
test_two, test_one, test_four]]: failed with permutation [test_one, test_two, 
test_three, 

Bug#834956: ircd-irc2: please make the build reproducible

[Kurt Roeckx]

On Sun, Aug 21, 2016 at 12:07:38AM +0100, Chris Lamb wrote:
> --- a/debian/patches/02_reproducible_build.patch  1970-01-01 
> 01:00:00.0 +0100
> --- b/debian/patches/02_reproducible_build.patch  2016-08-21 
> 00:06:08.338196876 +0100
> @@ -0,0 +1,21 @@
> +Description: Make the build reproducible
> +Author: Chris Lamb 
> +Last-Update: 2016-08-20
> +
> +--- ircd-irc2-2.11.2p3~dfsg.orig/ircd/version.c.SH.in
>  ircd-irc2-2.11.2p3~dfsg/ircd/version.c.SH.in
> +@@ -20,7 +20,13 @@ sumhash="`(cd ../ircd; @SUM@ hash.c)`"
> + sumsmisc="`(cd ../ircd; @SUM@ s_misc.c)`"
> + sumircd="`(cd ../ircd; @SUM@ ircd.c)`"
> + 
> +-creation=`date | \
> ++if test -n "$SOURCE_DATE_EPOCH"
> ++then
> ++  now=`LC_ALL=C date --utc --date="@$SOURCE_DATE_EPOCH"`
> ++else
> ++  now=`date`

That should probably also use LC_ALL=C

Bug#834963: ruby-protected-attributes: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:ruby-protected-attributes
Version: 1.1.3-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_testdir -i -O--buildsystem=ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby

[... snipped ...]

/usr/lib/ruby/vendor_ruby/active_support/callbacks.rb:555:in `block (2 
levels) in compile'
/usr/lib/ruby/vendor_ruby/active_support/callbacks.rb:505:in `call'
/usr/lib/ruby/vendor_ruby/active_support/callbacks.rb:92:in 
`__run_callbacks__'
/usr/lib/ruby/vendor_ruby/active_support/callbacks.rb:778:in 
`_run_save_callbacks'
/usr/lib/ruby/vendor_ruby/active_record/callbacks.rb:302:in 
`create_or_update'
/usr/lib/ruby/vendor_ruby/active_record/persistence.rb:120:in `save'
/usr/lib/ruby/vendor_ruby/active_record/validations.rb:37:in `save'
/usr/lib/ruby/vendor_ruby/active_record/attribute_methods/dirty.rb:21:in 
`save'
/usr/lib/ruby/vendor_ruby/active_record/transactions.rb:286:in `block (2 
levels) in save'
/usr/lib/ruby/vendor_ruby/active_record/transactions.rb:351:in `block in 
with_transaction_returning_status'

/usr/lib/ruby/vendor_ruby/active_record/connection_adapters/abstract/database_statements.rb:213:in
 `block in transaction'

/usr/lib/ruby/vendor_ruby/active_record/connection_adapters/abstract/transaction.rb:184:in
 `within_new_transaction'

/usr/lib/ruby/vendor_ruby/active_record/connection_adapters/abstract/database_statements.rb:213:in
 `transaction'
/usr/lib/ruby/vendor_ruby/active_record/transactions.rb:220:in `transaction'
/usr/lib/ruby/vendor_ruby/active_record/transactions.rb:348:in 
`with_transaction_returning_status'
/usr/lib/ruby/vendor_ruby/active_record/transactions.rb:286:in `block in 
save'
/usr/lib/ruby/vendor_ruby/active_record/transactions.rb:301:in 
`rollback_active_record_state!'
/usr/lib/ruby/vendor_ruby/active_record/transactions.rb:285:in `save'

/<>/lib/active_record/mass_assignment_security/persistence.rb:46:in
 `create'
/<>/test/attribute_sanitization_test.rb:1076:in 
`test_has_one_create_without_protection'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:799:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:322:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:309:in `each'
/usr/lib/ruby/vendor_ruby/minitest.rb:309:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest.rb:335:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:308:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:158:in `block in __run'
/usr/lib/ruby/vendor_ruby/minitest.rb:158:in `map'
/usr/lib/ruby/vendor_ruby/minitest.rb:158:in `__run'
/usr/lib/ruby/vendor_ruby/minitest.rb:135:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:62:in `block in autorun'

203 runs, 728 assertions, 0 failures, 1 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/accessible_params_wrapper_test.rb" "test/attribute_sanitization_test.rb" 
"test/mass_assignment_security/black_list_test.rb" 
"test/mass_assignment_security/permission_set_test.rb" 
"test/mass_assignment_security/sanitizer_test.rb" 
"test/mass_assignment_security/strong_parameters_fallback_test.rb" 
"test/mass_assignment_security/white_list_test.rb" 
"test/mass_assignment_security_test.rb" "test/test_helper.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install 
/<>/debian/ruby-protected-attributes returned exit code 1
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep 

Bug#834958: canl-java: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:canl-java
Version: 2.4.0-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibcanl-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[INFO] 

[... snipped ...]

Testing file 75680d2e.signing_policy
Testing file a87d9192.signing_policy
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.037 sec - in 
eu.emi.security.authn.x509.ns.GlobusParserTest
Running eu.emi.security.authn.x509.proxy.PathRetrievalTest
FAILED The following validation errors were found:
error at position 0 in chain, problematic certificate subject: 
CN=1888300600,CN=limited rfc proxy,CN=trusted 
client,OU=Relaxation,O=Utopia,L=Tropic,C=UG (category: 
INCONSISTENT_PROXY_CHAIN): The proxy chain contains an unlimited proxy 
certificate after a limited proxy certificate
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.547 sec - in 
eu.emi.security.authn.x509.proxy.PathRetrievalTest
Running eu.emi.security.authn.x509.proxy.ProxyGenerationTest
Running func:proxy-make functional test
Running regression:proxy-time-overflow test
Got: 361921609
Should be earlier: 3619216089353
Should be later: 3619216091461
OK
OK
FAILED The following validation errors were found:
error at position 0 in chain, problematic certificate subject: 
CN=64077,CN=PDPTest Server,O=Testing Organization,L=Testing City,C=EU 
(category: X509_BASIC): Certificate has expired on: 1/1/70 4:25 AM
Running func:proxy-make-withCustomExt functional test
Running func:proxy-delegate functional test
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.95 sec - in 
eu.emi.security.authn.x509.proxy.ProxyGenerationTest
Running eu.emi.security.authn.x509.proxy.ExtensionsTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
eu.emi.security.authn.x509.proxy.ExtensionsTest

Results :

Failed tests: 
  OpensslValidatorStressTest.opensslValidationShouldBeParallel:85 
Expected: is 
 but: was 

Tests run: 261, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:29 min
[INFO] Finished at: 2016-08-21T00:34:05+02:00
[INFO] Final Memory: 16M/50M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project canl: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/target/surefire-reports for the 
individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
debian/rules:5: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave 

Bug#834962: ruby-diaspora-vines: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:ruby-diaspora-vines
Version: 0.2.0.develop.4-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_testdir -i -O--buildsystem=ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby

[... snipped ...]

not working probably


  3) Skipped:
Vines::Stanza::Message::when addressed to an offline user#test_0001_raises a 
service-unavailable stanza error 
[/<>/test/stanza/message_test.rb:75]:
Skipped, no message given


  4) Skipped:
Vines::Cluster::Subscriber::when receiving a stanza routed to my 
node#test_0001_writes the stanza to the connected user streams 
[/<>/test/cluster/subscriber_test.rb:81]:
This fails randomly! Skipping it for later investigations.


  5) Error:
Vines::Cluster::Publisher::#route#test_0001_publishes the message to just one 
cluster node:
MockExpectationError: No more expects available for :id: []
/usr/lib/ruby/vendor_ruby/minitest/mock.rb:121:in `method_missing'

/<>/debian/ruby-diaspora-vines/usr/lib/ruby/vendor_ruby/vines/cluster/publisher.rb:34:in
 `route'
/<>/test/cluster/publisher_test.rb:37:in `block (3 levels) in 
'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:799:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:322:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:309:in `each'
/usr/lib/ruby/vendor_ruby/minitest.rb:309:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest.rb:335:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:308:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:158:in `block in __run'
/usr/lib/ruby/vendor_ruby/minitest.rb:158:in `map'
/usr/lib/ruby/vendor_ruby/minitest.rb:158:in `__run'
/usr/lib/ruby/vendor_ruby/minitest.rb:135:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:62:in `block in autorun'

428 runs, 933 assertions, 0 failures, 1 errors, 4 skips
After_run hook deleted test.db
rake aborted!
Command failed with status (1): [ruby -I"test:test/storage"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/cluster/publisher_test.rb" "test/cluster/sessions_test.rb" 
"test/cluster/subscriber_test.rb" "test/config/host_test.rb" 
"test/config/pubsub_test.rb" "test/config_test.rb" "test/contact_test.rb" 
"test/error_test.rb" "test/jid_test.rb" "test/kit_test.rb" 
"test/router_test.rb" "test/stanza/iq/disco_info_test.rb" 
"test/stanza/iq/disco_items_test.rb" "test/stanza/iq/private_storage_test.rb" 
"test/stanza/iq/roster_test.rb" "test/stanza/iq/session_test.rb" 
"test/stanza/iq/vcard_test.rb" "test/stanza/iq/version_test.rb" 
"test/stanza/iq_test.rb" "test/stanza/message_test.rb" 
"test/stanza/presence/probe_test.rb" "test/stanza/presence/subscribe_test.rb" 
"test/stanza/pubsub/create_test.rb" "test/stanza/pubsub/delete_test.rb" 
"test/stanza/pubsub/publish_test.rb" "test/stanza/pubsub/subscribe_test.rb" 
"test/stanza/pubsub/unsubscribe_test.rb" "test/stanza_test.rb" "test/storage/lo
 cal_test.rb" "test/storage/null_test.rb" "test/storage/sql_test.rb" 
"test/store_test.rb" "test/stream/client/auth_test.rb" 
"test/stream/client/ready_test.rb" "test/stream/client/session_test.rb" 
"test/stream/component/handshake_test.rb" "test/stream/component/ready_test.rb" 
"test/stream/component/start_test.rb" "test/stream/http/auth_test.rb" 
"test/stream/http/ready_test.rb" "test/stream/http/request_test.rb" 
"test/stream/http/sessions_test.rb" "test/stream/http/start_test.rb" 
"test/stream/parser_test.rb" "test/stream/sasl_test.rb" 
"test/stream/server/auth_method_test.rb" "test/stream/server/auth_test.rb" 
"test/stream/server/outbound/auth_dialback_result_test.rb" 
"test/stream/server/outbound/auth_external_test.rb" 
"test/stream/server/outbound/auth_restart_test.rb" 

Bug#834957: flashrom: please make the build reproducible

[Chris Lamb]

Source: flashrom
Version: 0.9.9+r1954-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], I noticed
that flashrom could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible_build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible_build.patch   2016-08-21 00:31:50.946279306 
+0100
@@ -0,0 +1,17 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-21
+
+--- flashrom-0.9.9+r1954.orig/util/getrevision.sh
 flashrom-0.9.9+r1954/util/getrevision.sh
+@@ -116,7 +116,9 @@ timestamp() {
+   # freebsd   date [-jnu]  [-d dst] [-r seconds] [-f fmt date | 
[cc]yy]mm]dd]HH]MM[.ss]] [+format] [...]
+   # dragonflybsd  date [-jnu]  [-d dst] [-r seconds] [-f fmt date | 
[cc]yy]mm]dd]HH]MM[.ss]] [+format] [...]
+   # openbsd   date [-aju]  [-d dst] [-r seconds] [+format] 
[[cc]yy]mm]dd]HH]MM[.SS]] [...]
+-  if svn_is_file_tracked "$2" ; then
++  if [ -n "$SOURCE_DATE_EPOCH" ] ; then
++  t=$(date -u -d "@$SOURCE_DATE_EPOCH" "$1")
++  elif svn_is_file_tracked "$2" ; then
+   if svn_has_local_changes "$2"; then
+   t=$(date -u "$1")
+   else
--- a/debian/patches/series 1970-01-01 01:00:00.0 +0100
--- b/debian/patches/series 2016-08-21 00:19:29.846542413 +0100
@@ -0,0 +1 @@
+reproducible_build.patch

Bug#834889: jwm: New version 2.3.6

[Samuel Henrique]

Hi Charles,

Thank you for this report.

I am aware of this new version and i was waiting sometime to upload because
i wanted to set up the packaging git before, as i will drop some patches
that i created on the package and upstream implemented (there was also a
licensing change: GPL2+ -> MIT [Expat]), the next releases should be
packaged by me as soon as they're released unless big changes to the
packaging are needed.

I should upload the new version today on mentors, but i believe it will
take some days until reaching unstable (i have to wait for a sponsor, as
i'm not a DM).



Samuel Henrique O. P. [samueloph]

2016-08-20 8:05 GMT-03:00 Charles Malaheenee :

> Package: jwm
> Version: 2.3.5-2
> Severity: wishlist
> Tags: upstream
>
> Dear Maintainer!
>
> A new version of jwm has been released 2016-08-12. This release includes
> some
> features, like aerosnap or task-list styles.
>
> Can you build it asap, please? Thank you
>
> Best regards,
> Malaheenee
>
> P.S. Yes, I've built it already, but 'make install' isn't Debian-way :)
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages jwm depends on:
> ii  libc62.23-4
> ii  libcairo21.14.6-1+b1
> ii  libfribidi0  0.19.7-1
> ii  libglib2.0-0 2.48.1-3
> ii  libjpeg62-turbo  1:1.5.0-1
> ii  libpng16-16  1.6.24-2
> ii  librsvg2-2   2.40.16-1
> ii  libx11-6 2:1.6.3-1
> ii  libxext6 2:1.3.3-1
> ii  libxft2  2.3.2-1
> ii  libxinerama1 2:1.1.3-1+b1
> ii  libxmu6  2:1.1.2-2
> ii  libxpm4  1:3.5.11-1+b1
> ii  libxrender1  1:0.9.9-2
> ii  xterm [x-terminal-emulator]  325-1
>
> Versions of packages jwm recommends:
> pn  menu  
>
> Versions of packages jwm suggests:
> pn  x11-apps  
>
> -- no debconf information
>
>

Bug#834956: ircd-irc2: please make the build reproducible

[Chris Lamb]

Source: ircd-irc2
Version: 2.11.2p3~dfsg-4
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], I noticed
that ircd-irc2 could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/02_reproducible_build.patch1970-01-01 
01:00:00.0 +0100
--- b/debian/patches/02_reproducible_build.patch2016-08-21 
00:06:08.338196876 +0100
@@ -0,0 +1,21 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-20
+
+--- ircd-irc2-2.11.2p3~dfsg.orig/ircd/version.c.SH.in
 ircd-irc2-2.11.2p3~dfsg/ircd/version.c.SH.in
+@@ -20,7 +20,13 @@ sumhash="`(cd ../ircd; @SUM@ hash.c)`"
+ sumsmisc="`(cd ../ircd; @SUM@ s_misc.c)`"
+ sumircd="`(cd ../ircd; @SUM@ ircd.c)`"
+ 
+-creation=`date | \
++if test -n "$SOURCE_DATE_EPOCH"
++then
++  now=`LC_ALL=C date --utc --date="@$SOURCE_DATE_EPOCH"`
++else
++  now=`date`
++fi
++creation=`echo $now | \
+ awk '{if (NF == 6) \
+  { print $1 " "  $2 " " $3 " "  $6 " at " $4 " " $5 } \
+ else \
--- a/debian/patches/series 2016-08-20 23:50:45.260647520 +0100
--- b/debian/patches/series 2016-08-20 23:55:07.311345098 +0100
@@ -1 +1,2 @@
 01_manpages.patch
+02_reproducible_build.patch

Bug#834955: transition: x265

[Sebastian Ramacher]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Control: forwarded -1 https://release.debian.org/transitions/html/auto-x265.html

x265 bumped its SONAME again and needs a transition. The new version is staged
in experimental and all reverse dependencies build fine against the new version.

Please let me know when it's okay to start the transition.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#833236: shotwell: Please install shotwell-settings-migrator and shotwell-video-thumbnailer in /usr/lib/shotwell

[Jörg Frings-Fürst]

tags 833236 + pending
thanks

Hello Laurent,

in the current upstream release both files are oonstalled at
/usr/lib/shotwell.


CU 
Jörg 


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#815025: Adopting python-braintree

[Hugo Lefeuvre]

retitle 815025 ITA: python-braintree -- Braintree Python library
owner 815025 Hugo Lefeuvre 
thanks

Hi Alessio,

I'll adopt python-braintree.

Cheers,
 Hugo

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E


signature.asc
Description: PGP signature

Bug#671179: git annex copy silently does nothing if no local copy is available

[Daniel Shahaf]

Control: found -1 6.20160719-1

Reviving an old thread:

Joey Hess wrote on Wed, May 02, 2012 at 12:14:59 -0400:
> Enrico Zini wrote:
> > first of all, thank you for git-annex.
> > 
> > I have three repositories:
> > 
> >   laptop (my laptop)
> >   archive (the big 2T archive USB disk)
> >   desktop (my old desktop, which I'm using mostly as a backup)
> > 
> > And a file I care about:
> > 
> >   laptop:/store$ git annex whereis file.ext
> >   whereis file.ext (1 copy) 
> > ---- -- archive (Archivio 2T 
> > usb drive)
> >   ok
> > 
> > I'm on my laptop and I'd like a copy of file.ext to be backed up to my old
> > desktop:
> > 
> >   laptop:/store$ git annex copy file.ext --to=desktop
> >   laptop:/store$ echo $?
> >   0
> > 
> > This said nothing and did nothing, successfully :(
> 
> Yes, all git-annex commands silenty skip files they can't or don't need
> to act on. This is done because it's not uncommon to have a lot of files
> in a tree, many of which are really present, and many not; it's then
> nice to be able to copy/drop all the ones that are present, or get all
> the ones that are not without manually specifying, and without drowning
> in warning messages.
> 
> I think that this becomes clear once you get used to it and see that
> it always says what it's doing, so a silent output like this
> was a no-op. I can see how it can be initially confusing though.
> 
> Perhaps you can suggest some documentation improvements in this area?

Yes, I do have a docs change to suggest: I believe the "quite please"
paragraph in the walkthrough updated is inaccurate, as it currently says
no output means "nothing needs to be done".  It would be more accurate
for that paragraph to say say what your email says: that no output means
that either nothing needs to be done, or the file is not present in the
current repository.

However, I would like to suggest a behaviour change, that I believe will
address your concern about not drowning the user in warnings: warn only
once per invocation of git-annex, rather than once per file.  For
example:

% git annex list
here
|remote
||elsewhere
|||web
bittorrent
|
X foo1.txt
__X__ foo2.txt
__X__ foo3.txt
__X__ foo4.txt
__X__ foo5.txt
__X__ foo6.txt
__X__ foo7.txt
X foo8.txt
% git annex copy foo{1,2,3,4,5,6,7,8}.txt --to=remote
move foo1.txt (to remote...) ok
move foo8.txt (to remote...) ok
(Recording state in git...)
git-annex: some files weren't copied because they are not present in this 
repository

The warning would only be generated if, following the copy operation, at
least one of the files named on the command line is not present in the
remote repository (the destination of the copy).

WDYT?

Cheers,

Daniel

[1] http://git-annex.branchable.com/walkthrough/#index14h2

Bug#822825: luasocket segfault

[David Jones]

This bug causes CorsixTH to crash when it checks for updates. Not sure if
updates are enabled by default for the Debian package, but they are when
built by source, and are if the user enables them

See https://github.com/CorsixTH/CorsixTH/issues/1091

Bug#834954: kwin-x11: +depends plasma-framework

[HJ]

Package: kwin-x11
Version: 4:5.7.0-1
Severity: important

Dear Maintainer,

kwin depends now on plasma-framework, otherwise the user won't be able to
select any kwin theme(kcmshell kwindecoration)



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

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)

Versions of packages kwin-x11 depends on:
ii  kwin-common   4:5.7.0-1
ii  libc6 2.23-4
ii  libepoxy0 1.3.1-1
ii  libgcc1   1:6.1.1-12
ii  libkf5configcore5 5.23.0-1
ii  libkf5coreaddons5 5.23.0-1
ii  libkf5crash5  5.23.0-1
ii  libkf5i18n5   5.23.0-1
ii  libkf5windowsystem5   5.23.0-1
ii  libkwinglutils8   4:5.7.0-1
ii  libkwinxrenderutils8  4:5.7.0-1
ii  libqt5core5a  5.6.1+dfsg-3+b1
ii  libqt5gui55.6.1+dfsg-3+b1
ii  libqt5widgets55.6.1+dfsg-3+b1
ii  libqt5x11extras5  5.6.1-2
ii  libstdc++66.1.1-12
ii  libx11-6  2:1.6.3-1
ii  libxcb-randr0 1.11.1-1.1
ii  libxcb1   1.11.1-1.1

kwin-x11 recommends no packages.

kwin-x11 suggests no packages.

-- no debconf information

Bug#834953: ams: Should this package be removed?

[Reinhard Tartler]

Package: ams
Severity: normal

Hi,

The package "ams" hasn't seen an upstream release since April 2014
(cf. http://alsamodular.sourceforge.net/). The last upload to debian
was on 2014-04-12.

It currently has one RC bug, and if I read popcon correctly, 46
installations: https://qa.debian.org/popcon.php?package=ams

I also checked that there are currently no reverse dependencies:

siretart@coccia:~$ dak rm -Rn ams
Will remove the following packages from unstable:

   ams |2.1.1-1 | source, amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x

Maintainer: Debian Multimedia Maintainers 


--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


I would recommend removing this package. If you agree, please reassign
this bug to the "ftp.debian.org" pseudo package and retitle "RoM: dead upstream"

Thanks,
Reinhard

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

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#834952: firebird3.0-server: please split "core" stuff out

[Rene Engelhard]

Package: firebird3.0-server
Version: 3.0.0.32483.ds4-5
Severity: wishlist

Dear Maintainer,

LibreOffice 5.3 updates it's firebird to 3.0 and apparently needs
libEngine12.so (also at build/test time).

This means I added a Build-Depends and a Depends on firebird3.0-server.

But on a dist-upgrade this happens:

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be REMOVED:
  firebird2.5-common firebird2.5-server-common libfbembed2.5
The following NEW packages will be installed:
  firebird3.0-server firebird3.0-utils
The following packages will be upgraded:
  libreoffice libreoffice-avmedia-backend-gstreamer libreoffice-base
  libreoffice-base-core libreoffice-base-drivers libreoffice-calc
  libreoffice-common libreoffice-core libreoffice-draw libreoffice-impress
  libreoffice-java-common libreoffice-math libreoffice-report-builder-bin
  libreoffice-sdbc-firebird libreoffice-sdbc-hsqldb libreoffice-style-galaxy
  libreoffice-writer python3-uno uno-libs3 ure
20 upgraded, 2 newly installed, 3 to remove and 0 not upgraded.
Need to get 0 B/85.7 MB of archives.
After this operation, 27.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 file:/home/rene/LibreOffice/git/apt ./ uno-libs3 
5.3.0~alpha0~git20160819-1 [868 kB]
Get:2 file:/home/rene/LibreOffice/git/apt ./ ure 5.3.0~alpha0~git20160819-1 
[1696 kB]
Get:3 file:/home/rene/LibreOffice/git/apt ./ libreoffice-calc 
1:5.3.0~alpha0~git20160819-1 [6468 kB]
Get:4 file:/home/rene/LibreOffice/git/apt ./ libreoffice-impress 
1:5.3.0~alpha0~git20160819-1 [917 kB]
Get:5 file:/home/rene/LibreOffice/git/apt ./ libreoffice-draw 
1:5.3.0~alpha0~git20160819-1 [2445 kB]
Get:6 file:/home/rene/LibreOffice/git/apt ./ libreoffice-writer 
1:5.3.0~alpha0~git20160819-1 [7617 kB]
Get:7 file:/home/rene/LibreOffice/git/apt ./ python3-uno 
1:5.3.0~alpha0~git20160819-1 [187 kB]
Get:8 file:/home/rene/LibreOffice/git/apt ./ libreoffice-style-galaxy 
1:5.3.0~alpha0~git20160819-1 [1557 kB]
Get:9 file:/home/rene/LibreOffice/git/apt ./ libreoffice-java-common 
1:5.3.0~alpha0~git20160819-1 [1941 kB]
Get:10 file:/home/rene/LibreOffice/git/apt ./ libreoffice-base 
1:5.3.0~alpha0~git20160819-1 [1495 kB]
Get:11 file:/home/rene/LibreOffice/git/apt ./ libreoffice-core 
1:5.3.0~alpha0~git20160819-1 [29.4 MB]
Get:12 file:/home/rene/LibreOffice/git/apt ./ libreoffice-common 
1:5.3.0~alpha0~git20160819-1 [25.0 MB]
Get:13 file:/home/rene/LibreOffice/git/apt ./ libreoffice-sdbc-hsqldb 
1:5.3.0~alpha0~git20160819-1 [109 kB]
Get:14 file:/home/rene/LibreOffice/git/apt ./ libreoffice-base-core 
1:5.3.0~alpha0~git20160819-1 [710 kB]
Get:15 file:/home/rene/LibreOffice/git/apt ./ libreoffice-report-builder-bin 
1:5.3.0~alpha0~git20160819-1 [764 kB]
Get:16 file:/home/rene/LibreOffice/git/apt ./ libreoffice 
1:5.3.0~alpha0~git20160819-1 [3728 B]
Get:17 file:/home/rene/LibreOffice/git/apt ./ libreoffice-math 
1:5.3.0~alpha0~git20160819-1 [355 kB]
Get:18 file:/home/rene/LibreOffice/git/apt ./ libreoffice-sdbc-firebird 
1:5.3.0~alpha0~git20160819-1 [118 kB]
Get:19 file:/home/rene/LibreOffice/git/apt ./ 
libreoffice-avmedia-backend-gstreamer 1:5.3.0~alpha0~git20160819-1 [23.6 kB]
Get:20 file:/home/rene/LibreOffice/git/apt ./ libreoffice-base-drivers 
1:5.3.0~alpha0~git20160819-1 [508 kB]
apt-listchanges: Reading changelogs...
Preconfiguring packages ...

(Reading database ... 422408 files and directories currently installed.)
Preparing to unpack .../00-uno-libs3_5.3.0~alpha0~git20160819-1_amd64.deb ...
Unpacking uno-libs3 (5.3.0~alpha0~git20160819-1) over (5.2.0-2) ...
Preparing to unpack .../01-ure_5.3.0~alpha0~git20160819-1_amd64.deb ...
Unpacking ure (5.3.0~alpha0~git20160819-1) over (5.2.0-2) ...
Preparing to unpack 
.../02-libreoffice-calc_5.3.0~alpha0~git20160819-1_amd64.deb ...
Unpacking libreoffice-calc (1:5.3.0~alpha0~git20160819-1) over (1:5.2.0-2) ...
Preparing to unpack 
.../03-libreoffice-impress_5.3.0~alpha0~git20160819-1_amd64.deb ...
Unpacking libreoffice-impress (1:5.3.0~alpha0~git20160819-1) over (1:5.2.0-2) 
...
Preparing to unpack 
.../04-libreoffice-draw_5.3.0~alpha0~git20160819-1_amd64.deb ...
Unpacking libreoffice-draw (1:5.3.0~alpha0~git20160819-1) over (1:5.2.0-2) ...
Preparing to unpack 
.../05-libreoffice-writer_5.3.0~alpha0~git20160819-1_amd64.deb ...
Unpacking libreoffice-writer (1:5.3.0~alpha0~git20160819-1) over (1:5.2.0-2) ...
Preparing to unpack .../06-python3-uno_5.3.0~alpha0~git20160819-1_amd64.deb ...
Unpacking python3-uno (1:5.3.0~alpha0~git20160819-1) over (1:5.2.0-2) ...
Preparing to unpack 
.../07-libreoffice-style-galaxy_5.3.0~alpha0~git20160819-1_all.deb ...
Unpacking libreoffice-style-galaxy (1:5.3.0~alpha0~git20160819-1) over 
(1:5.2.0-2) ...
Preparing to unpack 
.../08-libreoffice-java-common_5.3.0~alpha0~git20160819-1_all.deb ...
Unpacking libreoffice-java-common (1:5.3.0~alpha0~git20160819-1) over 
(1:5.2.0-2) ...
Preparing to unpack 

Bug#834777: ITP: python-blosc -- official Python bindings for Blosc

[Daniel Stender]

On Fri, 19 Aug 2016 06:45:58 +0100 Sandro Tosi  wrote:
> On Fri, Aug 19, 2016 at 12:35 AM, Daniel Stender  wrote:
> > I'm going to maintain this within the DPMT. The binary is going to be
> > python3-blosc (maybe also a Python 2 package).
> 
> yes please keep providing a python2 package - thanks!

Yes, absolutely no problem.

DS

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/



signature.asc
Description: OpenPGP digital signature

Bug#834950: limnoria: FTBFS when using eatmydata

[Santiago Vila]

On Sat, Aug 20, 2016 at 11:05:26PM +0200, Val Lorentz wrote:

> On 20/08/2016 22:45, Santiago Vila wrote:
> > AFAIK, it's the dynamic linker (ld.so) who shows the error, not ping
> > itself.
> 
> Probably because ping uses setuid.
> http://stackoverflow.com/a/11148167/539465

Actually, in Debian it's no longer setuid as it uses capabilities
instead:

# ls -l /bin/ping
-rwxr-xr-x 1 root root 57048 ago 20 22:43 /bin/ping
# getcap /bin/ping
/bin/ping = cap_net_raw+ep

(But I have no idea how ld.so behaves regarding capabilities).

Bug#834950: limnoria: FTBFS when using eatmydata

[Val Lorentz]

On 20/08/2016 22:45, Santiago Vila wrote:
> AFAIK, it's the dynamic linker (ld.so) who shows the error, not ping
> itself.

Probably because ping uses setuid.
http://stackoverflow.com/a/11148167/539465

> Could maybe the test suite discard all lines from stderr containing
> the string "libeatmydata.so" before checking if it's empty o not?

Actually, it's the main code which raises the error, and I don't like
the idea of adding a special case for this.

However, this would fix your problem if it gets merged:
https://sourceware.org/bugzilla/show_bug.cgi?id=20172
And Limnoria would not even need to be patched, as environment variables
for the subprocess are inherited.


An other possibility would be to add an option to tell the test suite to
skip tests which use setuid binaries.
This feature could also be useful in some other contexts, for instance
on environment which forbid setuid executables (like Travis CI, although
it whitelisted ping since)



signature.asc
Description: OpenPGP digital signature

Bug#834950: limnoria: FTBFS when using eatmydata

[Mattia Rizzolo]

On Sat, Aug 20, 2016 at 10:30:22PM +0200, Valentin Lorentz wrote:
> Hello, upstream here

Hi Valentin, Santiano :)

> $ eatmydata ping -W 1 -c 1 127.0.0.1 > /dev/null
> ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be
> preloaded (cannot open shared object file): ignored.

This is interesting indeed..

I do use eatmydata in my pbuilder chroot, and we use it in reproducible
builds (in armhf and i386 builders only though), and it does work.

Now, in my host system:

mattia@chase ~ % export LD_PRELOAD=libeatmydata.so
mattia@chase ~ % echo $LD_PRELOAD
libeatmydata.so
mattia@chase ~ % echo $LD_LIBRARY_PATH

mattia@chase ~ % ping -W 1 -c 1 127.0.0.1 > /dev/null

ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
mattia@chase ~ % 


within the chroot:


root@chase:/build/limnoria-2016.08.07# echo $LD_PRELOAD
libeatmydata.so
root@chase:/build/limnoria-2016.08.07# #echo 
root@chase:/build/limnoria-2016.08.07# echo $LD_LIBRARY_PATH
/usr/lib/libeatmydata
root@chase:/build/limnoria-2016.08.07# ping -W 1 -c 1 127.0.0.1 > /dev/null
root@chase:/build/limnoria-2016.08.07# 


Now, the LD_LIBRARY_PATH there is useful only for using a chroot with
eatmydata < 82 (i.e. before multiarch support and converting the package
to the one of a "shared library" (I do hope nobody treats it as a shared
lib of course…))

> I believe this is the appropriate behavior, and that the bug is actually
> in ping.
> What do you think?

As santiago said, the error is rather raised by ld

On 2016-08-20 08:48 PM Santiago Vila wrote:
> Could maybe the test suite discard all lines from stderr containing
> the string "libeatmydata.so" before checking if it's empty o not?
> 
> I don't know what the "proper" or "right" fix would be, but for me a
> simple workaround like that would be more than enough.

well, I do hope nobody will actually add such a ugly workaround :)
rather than that, I'd be a little bit happier to remove libeatmydata.so
from LD_PRELOAD before calling the tests..

Though, the right question is imho: WHY does that error occour?
libeatmydata.so is definitely in the default path for ld.
Do you know whether ping messes with dynamic linking options and stuff?
And why it doesn't happen in pbuilder (this is really wtf for me).

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#834951: gnome-shell: Mixed localizations

[Andreas Kloeckner]

Package: gnome-shell
Version: 3.20.3-1+b1
Severity: minor

Dear Maintainer,

as of recently, gnome-shell has started interspersing English strings with the
localized strings that I have otherwise set for my system, leading to
bizarre-looking menus like the following:

https://tiker.net/tmp/gnome-shell-mixed-localization.png

Functionally, everything seems unaffected, but it's certainly not fantastic to 
look at.

Thanks for your efforts in maintaining GNOME in Debian!

Andreas

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

Kernel: Linux 4.7.0-rc7-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)

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  evolution-data-server3.20.4-2+b1
ii  gir1.2-accountsservice-1.0   0.6.40-3
ii  gir1.2-atspi-2.0 2.20.2-1
ii  gir1.2-caribou-1.0   0.4.21-1
ii  gir1.2-clutter-1.0   1.26.0-2
ii  gir1.2-freedesktop   1.48.0-3
ii  gir1.2-gcr-3 3.20.0-2
ii  gir1.2-gdesktopenums-3.0 3.20.0-3
ii  gir1.2-gdm-1.0   3.20.1-1
ii  gir1.2-glib-2.0  1.48.0-3
ii  gir1.2-gnomebluetooth-1.03.20.0-1
ii  gir1.2-gnomedesktop-3.0  3.20.2-1
ii  gir1.2-gtk-3.0   3.20.7-1
ii  gir1.2-gweather-3.0  3.20.1-1
ii  gir1.2-ibus-1.0  1.5.11-1
ii  gir1.2-mutter-3.03.20.3-2
ii  gir1.2-networkmanager-1.01.2.4-2
ii  gir1.2-nmgtk-1.0 1.2.4-1
ii  gir1.2-pango-1.0 1.40.1-1
ii  gir1.2-polkit-1.00.105-16
ii  gir1.2-soup-2.4  2.54.1-1
ii  gir1.2-telepathyglib-0.120.24.1-1.1
ii  gir1.2-telepathylogger-0.2   0.8.2-1
ii  gir1.2-upowerglib-1.00.99.4-3
ii  gjs  1.45.4-1
ii  gnome-backgrounds3.20-1
ii  gnome-settings-daemon3.20.1-2
ii  gnome-shell-common   3.20.3-1
ii  gsettings-desktop-schemas3.20.0-3
ii  libatk-bridge2.0-0   2.20.1-3
ii  libatk1.0-0  2.20.0-1
ii  libc62.23-4
ii  libcairo21.14.6-1+b1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libclutter-1.0-0 1.26.0-2
ii  libcogl-pango20  1.22.0-2
ii  libcogl201.22.0-2
ii  libcroco30.6.11-1
ii  libdbus-glib-1-2 0.106-1
ii  libecal-1.2-19   3.20.4-2+b1
ii  libedataserver-1.2-213.20.4-2+b1
ii  libgcr-base-3-1  3.20.0-2
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libgirepository-1.0-11.48.0-3
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.45.4-1
ii  libglib2.0-0 2.48.1-2
ii  libgstreamer1.0-01.8.2-1
ii  libgtk-3-0   3.20.7-1
ii  libical2 2.0.0-0.5+b1
ii  libicu57 57.1-2
ii  libjson-glib-1.0-0   1.2.2-1
ii  libmozjs-24-024.2.0-3.1
ii  libmutter0h  3.20.3-2
ii  libnm-glib4  1.2.4-2
ii  libnm-util2  1.2.4-2
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpolkit-agent-1-0  0.105-16
ii  libpolkit-gobject-1-00.105-16
pn  libpulse-mainloop-glib0  
pn  libpulse0
ii  libsecret-1-00.18.3-1
ii  libstartup-notification0 0.12-4
ii  libsystemd0  230-7
ii  libtelepathy-glib0   0.24.1-1.1
ii  libx11-6 2:1.6.3-1
ii  libxfixes3   1:5.0.2-1
ii  mutter   

Bug#834950: limnoria: FTBFS when using eatmydata

[Santiago Vila]

On Sat, Aug 20, 2016 at 10:30:22PM +0200, Valentin Lorentz wrote:
> Hello, upstream here
> 
> This issue is caused by the test suite calling a command which uses
> ping. Calling ping from a shell shows the same error:
> 
> $ eatmydata ping -W 1 -c 1 127.0.0.1 > /dev/null
> ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be
> preloaded (cannot open shared object file): ignored.
> 
> Limnoria detects ping's stderr is not empty, so it raises this error.
> 
> I believe this is the appropriate behavior, and that the bug is actually
> in ping.
> What do you think?

AFAIK, it's the dynamic linker (ld.so) who shows the error, not ping
itself.

Could maybe the test suite discard all lines from stderr containing
the string "libeatmydata.so" before checking if it's empty o not?

I don't know what the "proper" or "right" fix would be, but for me a
simple workaround like that would be more than enough.

Thanks.

Bug#834950: limnoria: FTBFS when using eatmydata

[Valentin Lorentz]

Hello, upstream here

This issue is caused by the test suite calling a command which uses
ping. Calling ping from a shell shows the same error:

$ eatmydata ping -W 1 -c 1 127.0.0.1 > /dev/null
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be
preloaded (cannot open shared object file): ignored.

Limnoria detects ping's stderr is not empty, so it raises this error.

I believe this is the appropriate behavior, and that the bug is actually
in ping.
What do you think?

Best regards,
Valentin

On 20/08/2016 22:19, Santiago Vila wrote:
> Package: limnoria
> Version: 2016.06.29-2
> Severity: wishlist
> 
> Hello Mattia.
> 
> I can't build this package from source when using eatmydata.
> 
> I'm using sbuild and a file /etc/schroot/chroot.d/stretch like this:
> 
> [stretch]
> type=directory
> description=Debian stretch
> directory=/chroot/stretch
> groups=sbuild
> root-groups=sbuild
> preserve-environment=true
> command-prefix=eatmydata
> 
> Sample build log attached.
> 
> Would be possible to forward this upstream? Being able to build a
> package with eatmydata is always a very good thing.
> 
> Thanks.
> 



signature.asc
Description: OpenPGP digital signature

Bug#834950: limnoria: FTBFS when using eatmydata

[Santiago Vila]

Package: limnoria
Version: 2016.06.29-2
Severity: wishlist

Hello Mattia.

I can't build this package from source when using eatmydata.

I'm using sbuild and a file /etc/schroot/chroot.d/stretch like this:

[stretch]
type=directory
description=Debian stretch
directory=/chroot/stretch
groups=sbuild
root-groups=sbuild
preserve-environment=true
command-prefix=eatmydata

Sample build log attached.

Would be possible to forward this upstream? Being able to build a
package with eatmydata is always a very good thing.

Thanks.

limnoria_2016.06.29-2_amd64-20160809T0526Z.gz
Description: application/gzip

Bug#833115: Sponsoring hashid.

[Hugo Lefeuvre]

Hi Samuel,

> I believe the manpage update should be made in form of a PR on the
> project's github page, and because it's not practical to wait for another
> release, we can patch the new manpage with quilt until we get a new release.

I agree. Let's patch the manpage in our Debian release and submit the diff 
to the upstream.

Concerning signed releases, opening an issue on GitHub will be enough. This
document[0] explains very well how to proceed to create signed releases, so 
it may be interesting to mention it.

> I would be glad to have someone more experienced co-maintaining the
> package, you're more than welcome.
> 
> I'm already a member of the team and have my ssh keys ready, i will create
> the package's repository and then we can work there, please feel free to
> contact me.
> 
> From what i see, we have to update the manpage and then we're ready to
> release, we also have to ask for signed releases but this is a non-block
> issue.

Nice ! Well, drop me an e-mail when you're done with the repository and
I'll do a last review before building & uploading the package.

Cheers,
 Hugo

[0] https://wiki.debian.org/Creating%20signed%20GitHub%20releases

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E


signature.asc
Description: PGP signature

Bug#834949: lshell: Shell outbreak due to bad syntax parse

[Vladislav Yarmak]

Package: lshell
Version: 0.9.16-1
Severity: grave
Tags: security upstream
Justification: user security hole

lshell fails to parse shell syntax correctly and restrictions can be overrun:

root@debian:~# getent passwd testuser
testuser:x:1001:1001:,,,:/home/testuser:/usr/bin/lshell
root@debian:~# su - testuser
You are in a limited shell.
Type '?' or 'help' to get the list of allowed commands
testuser:~$ ?
cd  clear  echo  exit  help  history  ll  lpath  ls  lsudo
testuser:~$ bash
*** forbidden command: bash
testuser:~$ echo && 'bash'

testuser@debian:~$ ps -f
UIDPID  PPID  C STIME TTY  TIME CMD
testuser  4000  3999  0 23:12 pts/100:00:00 /usr/bin/python /usr/bin/lshell
testuser  4001  4000  0 23:12 pts/100:00:00 sh -c set -m; echo && 'bash'
testuser  4002  4001  0 23:12 pts/100:00:00 bash
testuser  4007  4002  0 23:13 pts/100:00:00 ps -f

Problem exists in current upstream code. There are opened issue on Github but 
no reaction yet: https://github.com/ghantoos/lshell/issues/147.

Command parser in this shell is beyound of recovery. I recommend to replace 
this shell with symlink to /usr/sbin/nologin.

-- 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/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lshell depends on:
ii  adduser  3.113+nmu3
ii  python   2.7.9-1

lshell recommends no packages.

lshell suggests no packages.

-- no debconf information

Bug#834948: xonsh: missing parser_table.py

[Frederic Peters]

Package: xonsh
Version: 0.4.4+dfsg-1
Severity: normal

Hi,

Identified in https://github.com/xonsh/xonsh/issues/1521 against the Arch
package but the same issue affects the Debian package:

  "
  I am pretty sure that this sleep is just a block waiting for the PLY parser
  to be constructed. This makes me think that the parser_table.py file is not
  in your install, and so it has to create it new each time. Can you check if
  this file exists in your install?
  "

And parser_table.py is not present in the Debian package.



Cheers,
Frederic

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

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

Versions of packages xonsh depends on:
ii  python3-pkg-resources  25.2.0-1
ii  python3-ply3.7-1
ii  python3-venv   3.5.1-4
pn  python3:any

Versions of packages xonsh recommends:
ii  python3-prompt-toolkit  1.0.3-1
ii  python3-pygments2.1.3+dfsg-1
ii  python3-setproctitle1.1.8-1+b2

Versions of packages xonsh suggests:
ii  xonsh-doc  0.4.4+dfsg-1

-- no debconf information

Bug#834946: lshell: Shell outbreak with multiline commands

[Vladislav Yarmak]

Package: lshell
Version: 0.9.16-1
Severity: grave
Tags: security upstream
Justification: user security hole

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Vladislav Yarmak 
To: Debian Bug Tracking System 
Subject: lshell: Shell outbreak with multiline commands
Message-ID: <20160820194404.1737.15528.reportbug@debian>
X-Mailer: reportbug 6.6.3
Date: Sat, 20 Aug 2016 22:44:04 +0300
X-Debbugs-Cc: Debian Security Team ,
 Debian Testing Security Team
 

Package: lshell
Version: 0.9.16-1
Severity: grave
Tags: security upstream
Justification: user security hole

Just type  after any allowed command and then type desired 
restricted command:

root@debian:~# getent passwd testuser
testuser:x:1001:1001:,,,:/home/testuser:/usr/bin/lshell
root@debian:~# su - testuser
You are in a limited shell.
Type '?' or 'help' to get the list of allowed commands
testuser:~$ ?
cd  clear  echo  exit  help  history  ll  lpath  ls  lsudo
testuser:~$ bash
*** forbidden command: bash
testuser:~$ echo
bash

testuser@debian:~$ ps -f
UIDPID  PPID  C STIME TTY  TIME CMD
testuser  1641  1640  0 22:27 pts/100:00:00 /usr/bin/python /usr/bin/lshell
testuser  1642  1641  0 22:27 pts/100:00:00 sh -c set -m; echo bash
testuser  1643  1642  0 22:27 pts/100:00:00 bash
testuser  1648  1643  0 22:27 pts/100:00:00 ps -f

Problem exists in current upstream code. There are opened issue on Github but 
no reaction yet: https://github.com/ghantoos/lshell/issues/149.

Command parser in this shell is beyound of recovery. I recommend to replace 
this shell with symlink to /usr/sbin/nologin.

-- 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/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lshell depends on:
ii  adduser  3.113+nmu3
ii  python   2.7.9-1

lshell recommends no packages.

lshell suggests no packages.

-- no debconf information

*** outbreak.txt
root@debian:~# getent passwd testuser
testuser:x:1001:1001:,,,:/home/testuser:/usr/bin/lshell
root@debian:~# su - testuser
You are in a limited shell.
Type '?' or 'help' to get the list of allowed commands
testuser:~$ ?
cd  clear  echo  exit  help  history  ll  lpath  ls  lsudo
testuser:~$ bash
*** forbidden command: bash
testuser:~$ echo
bash

testuser@debian:~$ ps -f
UIDPID  PPID  C STIME TTY  TIME CMD
testuser  1641  1640  0 22:27 pts/100:00:00 /usr/bin/python /usr/bin/lshell
testuser  1642  1641  0 22:27 pts/100:00:00 sh -c set -m; echo bash
testuser  1643  1642  0 22:27 pts/100:00:00 bash
testuser  1648  1643  0 22:27 pts/100:00:00 ps -f

-- 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/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lshell depends on:
ii  adduser  3.113+nmu3
ii  python   2.7.9-1

lshell recommends no packages.

lshell suggests no packages.

-- no debconf information

Bug#834947: libreoffice-base: Screen redraw problems: no navigation block and random redraw failures

[Joe Rowan]

Package: libreoffice-base
Version: 1:5.2.0-2
Severity: normal

Dear Maintainer,

When displaying a data grid of table or query results, the block of navigation 
buttons is missing, just a white area, and there are random errors in redraw, 
lines missing between records, record selector sometimes showing white block or 
text. Have also seen this happen with a Windows version, but have no details. 
I'm afraid I haven't used Base for some time, I don't know when this began. 
This sid is updated almost every day. There doesn't seem any similar issue with 
Calc spreadsheets, if that's relevant.

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

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

Versions of packages libreoffice-base depends on:
ii  dpkg  1.18.10
ii  libc6 2.23-4
ii  libgcc1   1:6.1.1-12
ii  libreoffice-base-core 1:5.2.0-2
ii  libreoffice-base-drivers  1:5.2.0-2
ii  libreoffice-core  1:5.2.0-2
ii  libstdc++66.1.1-12
ii  uno-libs3 5.2.0-2
ii  ure   5.2.0-2

Versions of packages libreoffice-base recommends:
ii  default-jre [java5-runtime]2:1.8-57
ii  libreoffice-java-common1:5.2.0-2
ii  libreoffice-writer 1:5.2.0-2
ii  openjdk-8-jre [java5-runtime]  8u102-b14.1-2

Versions of packages libreoffice-base suggests:
pn  libreoffice-gcj 
ii  libreoffice-report-builder  1:5.2.0-2
ii  unixodbc2.3.1-4.1

Versions of packages libreoffice-core depends on:
ii  fontconfig2.11.0-6.5
ii  fonts-opensymbol  2:102.7+LibO5.2.0-2
ii  libboost-date-time1.61.0  1.61.0+dfsg-2.1
ii  libc6 2.23-4
ii  libcairo2 1.14.6-1+b1
ii  libclucene-contribs1v52.3.3.4-4.2
ii  libclucene-core1v52.3.3.4-4.2
ii  libcmis-0.5-5v5   0.5.1+git20160603-1
ii  libcups2  2.1.4-4
ii  libcurl3-gnutls   7.50.1-1
ii  libdbus-1-3   1.10.10-1
ii  libdbus-glib-1-2  0.106-1
ii  libdconf1 0.26.0-1
ii  libeot0   0.01-3
ii  libexpat1 2.2.0-1
ii  libexttextcat-2.0-0   3.4.4-1
ii  libfontconfig12.11.0-6.5
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-12
ii  libgl1-mesa-glx [libgl1]  11.2.2-1
ii  libglew1.13   1.13.0-2
ii  libglib2.0-0  2.48.1-3
ii  libgltf-0.0-0v5   0.0.2-4+b1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgraphite2-31.3.8-1
ii  libharfbuzz-icu0  1.2.7-1+b1
ii  libharfbuzz0b 1.2.7-1+b1
ii  libhunspell-1.4-0 1.4.1-2
ii  libhyphen02.8.8-3
ii  libice6   2:1.0.9-1+b1
ii  libicu57  57.1-3
ii  libjpeg62-turbo   1:1.5.0-1
ii  liblangtag1   0.5.7-2
ii  liblcms2-22.7-1
ii  libldap-2.4-2 2.4.42+dfsg-2+b2
ii  libmythes-1.2-0   2:1.2.4-1
ii  libneon27-gnutls  0.30.1-5
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26-1
ii  libodfgen-0.1-1   0.1.6-1
ii  libpcre3  2:8.39-2
ii  libpng16-16   1.6.24-2
ii  librdf0   1.0.17-1+b1
ii  libreoffice-common1:5.2.0-2
ii  librevenge-0.0-0  0.0.4-5
ii  libsm62:1.2.2-1+b1
ii  libssl1.0.2   1.0.2h-1
ii  libstdc++66.1.1-12
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxml2   2.9.4+dfsg1-1+b1
ii  libxrandr22:1.5.0-1
ii  libxrender1   1:0.9.9-2
ii  libxslt1.11.1.29-1
ii  uno-libs3 5.2.0-2
ii  ure   5.2.0-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages libreoffice-core recommends:
ii  libpaper-utils  1.1.24+nmu4

Versions of packages libreoffice-base is related to:
ii  libmyodbc5.1.10-3
ii  libmysql-java5.1.39-1
pn  libpg-java   
pn  libsapdbc-java   
ii  libsqliteodbc0.9994-1
ii  mdbtools 0.7.1-4
pn  odbc-postgresql  
pn  tdsodbc  
ii  unixodbc 2.3.1-4.1

-- no debconf information

Bug#796360: libical: please make the build reproducible

[Chris Lamb]

> The patch does not seem to be applied upstream

There hasn't seem to be any update on this bug in 67 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#827684: cgoban: please make the build reproducible

[Chris Lamb]

Dear Maintainer,

> Source: cgoban
> Version: 1.9.14-15
> Tags: patch

There hasn't seem to be any update on this bug in 62 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Bug#834945: libquvi: please make the build reproducible

[Chris Lamb]

Source: libquvi
Version: 0.9.3-1.2
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], I noticed
that libquvi could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible-build.patch   2016-08-20 20:55:08.815575170 
+0100
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-20
+
+--- libquvi-0.9.3.orig/configure.ac
 libquvi-0.9.3/configure.ac
+@@ -71,7 +71,7 @@ AS_IF([test x"$A2X" = "xno" && test -d "
+   AC_MSG_ERROR([a2x is required to create man pages when building from git])])
+ 
+ AC_PATH_PROG([DATE], [date], [no])
+-AS_IF([test x"$DATE" != "xno"], [build_time=`$DATE +"%F %T %z"`])
++AS_IF([test x"$DATE" != "xno" && test x"$SOURCE_DATE_EPOCH" = "x" ], 
[build_time=`$DATE +"%F %T %z"`])
+ AC_DEFINE_UNQUOTED([BUILD_TIME], ["$build_time"], [We have build time])
+ 
+ BUILD_TIME="$build_time"
--- a/debian/patches/series 2016-08-20 20:46:01.745852673 +0100
--- b/debian/patches/series 2016-08-20 20:55:18.035657334 +0100
@@ -1,2 +1,3 @@
 doxygen.patch
 lua52.patch
+reproducible-build.patch

Bug#834944: qemu: CVE-2016-6836: Information leak in vmxnet3_complete_packet

[Salvatore Bonaccorso]

Source: qemu
Version: 1:2.1+dfsg-11
Severity: normal
Tags: security upstream

Hi,

the following vulnerability was published for qemu.

CVE-2016-6836[0]:
Information leak in vmxnet3_complete_packet

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-6836

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#834943: caja: Caja segfaults when leaving trash

[G. Heine]

Package: caja
Version: 1.14.1-1
Severity: normal

Dear Maintainer,

after having opened trash in caja it is not possible to use this window for
further actions.
When clicking some place or device in Places or trying to go backwards (to a
folder already used before trash) the window is closed.

The typical entry in syslog is:

caja[8631]: segfault at 18 ip 7f48bf12c6b0 sp 7ffc9403a348 error 4 in
libgtk-3.so.0.2000.7[7f48bedb9000+6cf000]

Yours
Günter Heine



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (700, 'testing')
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)

Versions of packages caja depends on:
ii  caja-common   1.14.1-1
ii  desktop-file-utils0.23-1
ii  gvfs  1.28.3-1
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.23-4
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libcaja-extension11.14.1-1
ii  libexempi32.3.0-2
ii  libexif12 0.6.21-2
ii  libgail-3-0   3.20.7-1
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.1-2
ii  libglib2.0-data   2.48.1-2
ii  libgtk-3-03.20.7-1
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.14.1-1
ii  libpango-1.0-01.40.1-1
ii  libpangocairo-1.0-0   1.40.1-1
ii  libselinux1   2.5-3
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-3.0-0   3.0.2-2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-1
ii  libxrender1   1:0.9.9-2
ii  mate-desktop  1.14.1-1
ii  shared-mime-info  1.6-1

Versions of packages caja recommends:
ii  gvfs-backends  1.28.3-1

Versions of packages caja suggests:
ii  engrampa1.14.1-1
pn  gstreamer1.0-tools  
pn  meld

-- no debconf information

Bug#834911: libconfig-model-dpkg-perl: FTBFS too much often (Failed 2/12 test programs)

[Santiago Vila]

Control: tag -1 - unreproducible

As Niko has correctly inferred from the build log, the bug is
reproducible in stretch.

Bug#834851: does not serve out-of-tree symlinks

[Ron]

On Sat, Aug 20, 2016 at 10:11:16AM +0200, Marc Haber wrote:
> On Sat, Aug 20, 2016 at 08:42:09AM +0930, Ron wrote:
> > I think I'm going to call this one not-a-bug, see below ...
> 
> Yes, you're right of course, but it should not try serving a zero-byte
> file then.
> 
> Feel free to re-open if you think that serving a file that is
> different from what the customer asked for is a bug.

Does it actually serve a file, or is that just a side-effect of
the client side behaviour when it fails to serve anything at all?

  Ron

Bug#834942: debian-installer: Can't boot via serial console in qemu

[Simon Ruderich]

Package: debian-installer
Version: 8.5.0
Severity: normal

Hello,

I can't boot the debian installer via serial console in qemu:

qemu-system-x86_64 -boot d -cdrom debian-8.5.0-amd64-netinst.iso -nographic

I'd expect a prompt from isolinux on the serial console which
lets me change the boot parameters.

I have no real system to verify this, but IIRC then it worked in
the past. Am I using qemu or the installer incorrectly or did
this behavior change?

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: PGP signature

Bug#833789: debhelper: improve cross build support with the cmake buildsystem: multiarch and pkg-config

[Niels Thykier]

Hi CMake maintainers,

I received the following feature request against debhelper (quoted below
in full for your convenience).  Let me know if you have any comments
about it/them or if you prefer some of them to be done in cmake itself
(notably the pkg-config might be trivial and mroe beneficial to do in
cmake itself).

(NB: Please remember to CC Helmut and Julian on replies if you want them
to react)

Thanks,
~Niels

On Mon, 8 Aug 2016 18:17:57 +0200 Helmut Grohne  wrote:
> Package: debhelper
> Version: 9.20160709
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> Hi Niels et al,
> 
> Julian was kind enough to prepare an experimental apt release that uses
> CMake as its build system, so I could get my hands on it and test cross
> build it. That worked pretty well with two problems both of which we'd
> like to solve in debhelper.
> 
>  * By default CMake's `find_package(PkgConfig)` will not consider cross
>tools and default to using plain 'pkg-config'. Since Debian's
>pkg-config has a proper cross wrapper now, not using the
>triplet-prefixed means that CMake will fail to find libraries.
> 
>There are a number of options to tell CMake about the right
>pkg-config. For instance, setting the environment variable
>PKG_CONFIG=-pkg-config is sufficient. In this patch, we pass
>it as -DPKG_CONFIG_EXECUTABLE=... to keep consistency with other
>options. Also note that this variable requires an absolute path.
> 
>  * CMake has logic to place libraries in multiarch paths on Debian
>systems. That logic is disabled for cross compilation. Thus CMake
>puts libraries in /usr/lib durin cross compilation, which makes e.g.
>apt fail to cross build. It's not clear what is the best place to fix
>this, but debhelper certainly is one where this is possible.
>Arguably, it's a good place, because CMake has no good way to
>determine whether the host system will be a Debian system.
> 
> The patch is joint work with Julian.
> 
> Helmut

Bug#825727: python-babel: FTBFS: assert 'GMT+00:00' == 'GMT-01:59'

[Jakub Wilk]

* Chris Lamb , 2016-05-29, 10:54:

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


https://github.com/python-babel/babel/issues/441 is probably the bug 
that triggers on reproducible-builds infrastructure.


It remains mystery to me why it also fails in Chris's environment.

--
Jakub Wilk

Bug#834911: libconfig-model-dpkg-perl: FTBFS too much often (Failed 2/12 test programs)

[Santiago Vila]

On Sat, 20 Aug 2016, Niko Tyni wrote:

> > So I guess we can close this bug?
> 
> Either that, or reassign it to src:apt to track 1.3~rc2 testing migration
> I guess.
> 
> I don't mind much, but maybe Santiago (cc'd) does? (given you seem to be
> rebuilding stretch not sid)

Hello.

Yes, I am building on stretch, using (of course) packages also on stretch.

I don't mind that this bug is closed if it's really fixed, but from
the point of view of Quality Assurance, please help me to determine
how this bug reached testing in the first place and how we could have
avoided it to happen in testing.

For example, if it's really a bug in apt, then please do a reassign
but ensure that the bug is serious (as it breaks other packages), and
that it has an "affects" on this package.

In such case, also, a versioned build-depends on the fixed apt would
help, as it is always a lot better to get an error like
"build-dependencies may not be met" (i.e. a dep-wait in wanna-build
speak) than an error like the one reported here.

Thanks.

Bug#833187: RFS: yuma123/2.8-1 [ITP] -- netconf/YANG toolchain

[Vincent Bernat]

 ❦ 20 août 2016 13:27 CEST, Vladimir Vassilev  :

> Vincent,
>
> I just uploaded a new 2.9-1 package - 
> https://mentors.debian.net/package/yuma123

I don't see any remaining problem. Uploaded.
-- 
Debian package sponsoring guidelines:
 https://vincent.bernat.im/en/debian-package-sponsoring.html


signature.asc
Description: PGP signature

Bug#834895: fatal: refusing to merge unrelated histories

[Sean Whitton]

Hello,

On Sat, Aug 20, 2016 at 05:30:51PM +, PICCA Frederic-Emmanuel wrote:
> Yes, but usually, I prepare my configuration on the targetted machine. (a 
> jessie machine)
> So if I can not run propello on jessie I will be really sad ;)

So you're installing the .deb from stretch on your jessie machine?

I suggest that you install the /usr/bin/propellor wrapper from the
jessie repos, and then use a more recent ~/.propellor.  E.g.:

cd ~/.propellor
git remote add upstream https://github.com/joeyh/propellor # github for 
https
git merge 3.1.1

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#834922: gnupg: No more able to sign with my 4096R key since the switch to GnuPG 2.x, but still able to sign with my old 1024D key

[Werner Koch]

Hi Axel,

can you please run 

  echo foo | gpg --clearsign -v --debug ipc

which shows the communication with gpg-agent.  It won't show passphrases
or secret key material, but if you prefer, send the output to my by PM.

You may also want to kill a running gpg-agent first so that gpg can
restart a new one.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
 /* Join us at OpenPGP.conf   */

Bug#834911: libconfig-model-dpkg-perl: FTBFS too much often (Failed 2/12 test programs)

[Niko Tyni]

On Sat, Aug 20, 2016 at 07:56:56PM +0200, gregor herrmann wrote:
> On Sat, 20 Aug 2016 20:51:51 +0300, Niko Tyni wrote:
> 
> > > >  flAbsPath on /var/lib/apt/var/lib/dpkg/status failed - realpath (2: No 
> > > > such file or directory)
> > > >  Could not open file  - open (2: No such file or directory)
> > > >  Problem opening 
> > > >  The package lists or status file could not be parsed or opened.

> > I can reproduce it with libapt-pkg5.0_1.3~rc1, and it goes away with
> > libapt-pkg5.0_1.3~rc2. The build logs have 1.3~rc1. (Looks like they
> > may be testing stretch not sid.)
> 
> Ah! That explains.
>  
> > Maybe this change in ~rc2?
> > 
> >   * default to Dir=/ in dpkg/status file finding magic
> 
> Right, and this was also mentioned in #833656 by one of the apt
> maintainers.
> 
> So I guess we can close this bug?

Either that, or reassign it to src:apt to track 1.3~rc2 testing migration
I guess.

I don't mind much, but maybe Santiago (cc'd) does? (given you seem to be
rebuilding stretch not sid)
-- 
Niko Tyni   nt...@debian.org

Bug#834933: libcmis package description is not understandable

[Rene Engelhard]

reassign 834933 src:libcmis
found 834933 0.5.1-4
thanks

Hi,

On Sat, Aug 20, 2016 at 08:59:45PM +0300, Adrian Bunk wrote:
> libreoffice (1:5.2.0-2) unstable; urgency=medium
>   * debian/rules, debian/shlibs.override.libcmis: bump libcmis dependency
> to (>= 0.5.1+git20160603) to assure the advertised google 2-factor-auth
> stuff is present
> 
> That's why I wondered what libcmis is.

Yeah, the above is for the Google Drive support in LO, LOs internal libcmis
copy got patched to support 2-factor auth there but this didn't end up in a
released libcmis yet, so...

> > I'd have understood if you filed this against cmis-client, but people don't
> > need to know what CMIS is when they install LibreOffice and use this library
> > via trying to connect to Google Drive etc.
> 
> I forgot to mention this explicitely, but since this part is shared 
> between all binary packages the improved text should be in all of them.

Sure, of course.
(But shouldn't you have filed it against src:libcmis then? :))

> > > Please add something like "accessing documents on a document
> > > management system" (or whatever is technically correct)
> > > to the package description.
> > 
> > Well, this is (admittedly badly written) already said with ECM ("Enterprise
> > Content Management"), but maybe. (And also mention Google Drive etc.)
> 
> The background of this bug report is that after reading the package 
> description I had to use Wikipedia just for understanding that this
> is about content management.

Or accessing Google Drive etc.

Regards,

Rene

Bug#834941: privoxy segfaults with listen-address :8118

[Marvin Renich]

Package: privoxy
Version: 3.0.25-1
Severity: normal

Dear Maintainer,

If the config file contains

listen-address :8118

privoxy starts, correctly listens on all interfaces (as shown by lsof -i -n),
but terminates with a segfault when a connection is attempted from other than
localhost.  Changing the listen-address to *:8118 resolves the problem, but
privoxy should not segfault with :8118.  Either it should refuse to start,
giving an appropriate error message, or, preferably, it should treat :port and
*:port as synonyms.

Thanks...Marvin


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/1 CPU core)
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 privoxy depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.59
ii  init-system-helpers1.42
ii  libc6  2.23-4
ii  libpcre3   2:8.39-1
ii  logrotate  3.8.7-2
ii  lsb-base   9.20160629
ii  ucf3.0036
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages privoxy recommends:
pn  doc-base  

privoxy suggests no packages.

-- debconf information:
  privoxy/listen-address: 127.0.0.1:8118 [::1]:8118

Bug#834940: ITP: lambda-align -- Local Aligner for Massive Biological DatA

[Sascha Steinbiss]

Package: wnpp
Severity: wishlist
Owner: Sascha Steinbiss 

* Package name: lambda-align
  Version : 1.0.0
  Upstream Author : Hannes Hauswedell 
* URL : https://seqan.github.io/lambda
* License : GPL
  Programming Lang: C++
  Description : Local Aligner for Massive Biological DatA

Lambda is a local biosequence aligner optimized for many query sequences
and searches in protein space. It is compatible to the de facto standard tool
BLAST, but often outperforms the best currently available alternatives at
reproducing BLAST’s results and is the fastest compared with the current
state of the art at comparable levels of sensitivity.

This package will be maintained under the umbrella of the Debian Med Team.

Bug#796414: ITP: vertex-theme -- Vertex themes for GTK 2/3

[James Lu]

Hi Jack,

Creating a CRX file looks a bit problematic because it requires a key
signature, ideally from upstream. I don't think signing on behalf of
upstream developers (or Debian itself) is something that can be easily done.

The closest example I found of packing a Chromium/Chrome extension in
Debian was https://packages.debian.org/sid/chromium-lwn4chrome. There,
it looks like assets (*.png, *.js*, and _locales) are installed raw into
/usr/share/chromium/extensions/lwn4chrome, and a custom loader named
lwn4chrome is installed into /etc/chromium.d/

Below is the contents of the loader (debian/loader/lwn4chrome in the
source). It looks fairly straightforward, working by appending
--load-extension to the flags chromium starts with.

# lwn4chrome extension loader
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS
--load-extension=/usr/share/chromium/extensions/lwn4chrome"

For what it's worth, it might be useful to split up the Firefox and
Chrome-specific themes into separate binaries, and have those recommend
firefox | firefox-esr (depending on which versions are supported) and
chromium respectively. That way, people who aren't using those specific
browsers don't have to install extras they don't need.

Best,
James

On 19/08/2016 2:28 PM, Jack Henschel wrote:
> Hi James,
> 
> thanks for your suggestions!
> 
> I have updated the dependencies and fixed the spelling errors.
> Also, thanks for hinting at README.Debian, that is indeed a better place for 
> these setup instruction (although fewer people might look there).
> 
> I'll still have to look at packaging the Chrome theme.
> The Firefox is no problem, since it is just plain CSS (I have already 
> included it in vertex-theme.install).
> However the Chrome theme (in extra/Chrome) features CRX files [0] as well as 
> a source directive.
> Maybe I can figure out how to 'create' those CRX files and then ship them.
> 
> Best Regards,
> Jack Henschel
> 
> On 08/18/2016 02:32 AM, James Lu wrote:
>> (Disclaimer: I'm not a DD with upload privileges or anything, just a
>> customization enthusiast with a bit of packaging knowledge.)
>>
>> But, some notes anyways on a first glance:
>>
>> * https://github.com/horst3180/vertex-theme lists gnome-themes-standard
>> as a dependency, but that's missing from debian/control
>>
>> * A man page for something like a theme set seems a bit odd to me;
>> aren't those usually for binaries or config files? AFAIK,  README.debian
>> is the most common way of writing notes such as how to configure extras:
>> see https://www.debian.org/doc/manuals/maint-guide/dother.en.html#readme
>>
>> * I noticed some typos in the man page: enviroments instead of
>> environments (line 8), IceWeasel instead of Iceweasel (line 9)
>>
>> Other than that, the package looks fine to me :)
>>
>> Best,
>> James
>>
>> On 17/08/2016 2:48 PM, Jack Henschel wrote:
>>> My progress is now in collab-maint (vertex-theme):
>>>
>>>  https://anonscm.debian.org/git/collab-maint/vertex-theme.git
>>>  git://anonscm.debian.org/collab-maint/vertex-theme.git
>>>
>>> I'm using gbp with the branches master, upstream and pristine-tar.
>>>
>>> What still needs to be done:
>>>
>>>  * Check dependencies
>>>  * Complete and verify manpage
>>>
>>> Oh, and also I still need to fix all the other mistakes I probably made :-)
>>>
>>
> 



signature.asc
Description: OpenPGP digital signature

Bug#834898: propellor: problem with the new gpg2

[Sean Whitton]

Hello,

On Sat, Aug 20, 2016 at 06:56:59PM +0200, Johannes Schauer wrote:
> another way would be to change propellor not to run $(sbuild-update --keygen)
> anymore at all. Doing this is only required if you want to use sbuild for
> chroots containing Debian squeeze or older. If you only build for newer Debian
> releases, then signing the internal dummy repository will serve no purpose
> other than making your builds slower and requiring lots of entropy during the
> one-time setup...
> 
> You might want to open another bug against propellor to ask it not to generate
> the key anymore if the propellor maintainers agree that that they don't want 
> to
> support squeeze chroots anymore.

We've got one open here: 
http://propellor.branchable.com/todo/updates_for_sbuild_0.70.0-1/

> Also note, that there is a possibility that I will mark this bug as
> wontfix.  For a reasoning, please refer to the thread on debian-devel
> starting at [1].

Ah, good to know about that possibility.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#834914: libur-perl: FTBFS too much often (Failed 1/269 test programs)

[Niko Tyni]

On Sat, Aug 20, 2016 at 06:38:03PM +0200, gregor herrmann wrote:
> Control: tag -1 + unreproducible
> 
> On Sat, 20 Aug 2016 17:18:29 +0200, Santiago Vila wrote:
> 
> > Package: src:libur-perl
> > Version: 0.440-3
> > Severity: serious

> #   Failed test 'Got second object from the file'
> #   at t/URT/t/04e_file_track_open_close.t line 89.
> Can't call method "name" on an undefined value at 
> t/URT/t/04e_file_track_open_close.t line 90,  line 3.

> FWIW, I can't reproduce it (sid amd64 cowbuilder).

Running the test manually in a loop makes it fail every now and
then. Presumably it's a race condition in the test suite.
-- 
Niko Tyni   nt...@debian.org

Bug#834933: libcmis package description is not understandable

[Adrian Bunk]

On Sat, Aug 20, 2016 at 06:56:52PM +0200, Rene Engelhard wrote:
> Hi,

Hi Rene,

> On Sat, Aug 20, 2016 at 07:44:31PM +0300, Adrian Bunk wrote:
> > Package: libcmis-0.5-5v5 
> [...]
> > Description-en: CMIS protocol client library
> >  LibCMIS is a C++ client library for the CMIS interface.
> >  .
> >  This allows C++ applications to connect to any ECM behaving as a CMIS 
> > server
> >  like Alfresco, Nuxeo.
> > 
> > 
> > The average Debian user does not know what ECM or CMIS are.
> 
> And this does matter why? I mean, people won't install this _library_
> on their own.

libreoffice (1:5.2.0-2) unstable; urgency=medium
  * debian/rules, debian/shlibs.override.libcmis: bump libcmis dependency
to (>= 0.5.1+git20160603) to assure the advertised google 2-factor-auth
stuff is present

That's why I wondered what libcmis is.

> I'd have understood if you filed this against cmis-client, but people don't
> need to know what CMIS is when they install LibreOffice and use this library
> via trying to connect to Google Drive etc.

I forgot to mention this explicitely, but since this part is shared 
between all binary packages the improved text should be in all of them.

> > Please add something like "accessing documents on a document
> > management system" (or whatever is technically correct)
> > to the package description.
> 
> Well, this is (admittedly badly written) already said with ECM ("Enterprise
> Content Management"), but maybe. (And also mention Google Drive etc.)

The background of this bug report is that after reading the package 
description I had to use Wikipedia just for understanding that this
is about content management.

Writing the full names instead of only the acronyms would already 
be an improvement.

> Regards,
> 
> Rene

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#834911: libconfig-model-dpkg-perl: FTBFS too much often (Failed 2/12 test programs)

[gregor herrmann]

On Sat, 20 Aug 2016 20:51:51 +0300, Niko Tyni wrote:

> > >  flAbsPath on /var/lib/apt/var/lib/dpkg/status failed - realpath (2: No 
> > > such file or directory)
> > >  Could not open file  - open (2: No such file or directory)
> > >  Problem opening 
> > >  The package lists or status file could not be parsed or opened.
> > > 
> > > which suggests this is #833656.
> > 
> > Ack, that was my first idea as well after reading the logs.
> > But still, the tests pass for me when I build the package (as well as
> > the autopkgtests).
> 
> I can reproduce it with libapt-pkg5.0_1.3~rc1, and it goes away with
> libapt-pkg5.0_1.3~rc2. The build logs have 1.3~rc1. (Looks like they
> may be testing stretch not sid.)

Ah! That explains.
 
> Maybe this change in ~rc2?
> 
>   * default to Dir=/ in dpkg/status file finding magic

Right, and this was also mentioned in #833656 by one of the apt
maintainers.

So I guess we can close this bug?


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Dire Straits: Down To The Waterline


signature.asc
Description: Digital Signature

Bug#834911: libconfig-model-dpkg-perl: FTBFS too much often (Failed 2/12 test programs)

[Niko Tyni]

On Sat, Aug 20, 2016 at 07:27:22PM +0200, gregor herrmann wrote:
> On Sat, 20 Aug 2016 20:14:41 +0300, Niko Tyni wrote:
> 
> > > FWIW, the package builds fine for me (amd64 sid cowbuilder).
> > 
> > The failures seem to be related to these log entries:
> > 
> >  flAbsPath on /var/lib/apt/var/lib/dpkg/status failed - realpath (2: No 
> > such file or directory)
> >  Could not open file  - open (2: No such file or directory)
> >  Problem opening 
> >  The package lists or status file could not be parsed or opened.
> > 
> > which suggests this is #833656.
> 
> Ack, that was my first idea as well after reading the logs.
> But still, the tests pass for me when I build the package (as well as
> the autopkgtests).

I can reproduce it with libapt-pkg5.0_1.3~rc1, and it goes away with
libapt-pkg5.0_1.3~rc2. The build logs have 1.3~rc1. (Looks like they
may be testing stretch not sid.)

Maybe this change in ~rc2?

  * default to Dir=/ in dpkg/status file finding magic
-- 
Niko Tyni   nt...@debian.org

Bug#834939: Allow to set default policy for debdelta-upgrade

[Yuri D'Elia]

Package: debdelta
Version: 0.55
Severity: wishlist

When I'm using debdelta-upgrade I'm generally behind a slow connection. As a
consequence I never want to download full packages (stuff like tetex would take
months and cost me a fortune).

I'm always using --deb-policy '' to enforce this behavior, but this policy
would better be set somewhere in a configuration file, as it doesn't seem
something that you would change from one invocation to the other.

Thanks

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

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)

Versions of packages debdelta depends on:
ii  binutils2.27-6
ii  bzip2   1.0.6-8
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.23-4
ii  python  2.7.11-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages debdelta recommends:
ii  bsdiff   4.3-15
ii  gnupg-agent  2.1.14-5
ii  gnupg2   2.1.14-5
ii  python-apt   1.1.0~beta4
ii  python-debian0.1.29
ii  xdelta   1.1.3-9.1
ii  xdelta3  3.0.11-dfsg-1
ii  xz-utils [lzma]  5.1.1alpha+20120614-2.1

Versions of packages debdelta suggests:
ii  debdelta-doc  0.55

-- Configuration Files:
/etc/debdelta/sources.conf changed [not included]

Bug#834895: fatal: refusing to merge unrelated histories

[PICCA Frederic-Emmanuel]

> It means you need git 2.9 on the system you run `propellor --spin`, but
> it shouldn't break anything on the host you are trying to configure.


Yes, but usually, I prepare my configuration on the targetted machine. (a 
jessie machine)
So if I can not run propello on jessie I will be really sad ;)

Cheers

Bug#834911: libconfig-model-dpkg-perl: FTBFS too much often (Failed 2/12 test programs)

[gregor herrmann]

On Sat, 20 Aug 2016 20:14:41 +0300, Niko Tyni wrote:

> > FWIW, the package builds fine for me (amd64 sid cowbuilder).
> 
> The failures seem to be related to these log entries:
> 
>  flAbsPath on /var/lib/apt/var/lib/dpkg/status failed - realpath (2: No such 
> file or directory)
>  Could not open file  - open (2: No such file or directory)
>  Problem opening 
>  The package lists or status file could not be parsed or opened.
> 
> which suggests this is #833656.

Ack, that was my first idea as well after reading the logs.
But still, the tests pass for me when I build the package (as well as
the autopkgtests).


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Tom Waits: The One That Got Away


signature.asc
Description: Digital Signature

Bug#834912: libfile-tee-perl: FTBFS too much often (Failed 1/2 test programs)

[Niko Tyni]

On Sat, Aug 20, 2016 at 06:49:21PM +0200, gregor herrmann wrote:
> Control: tag -1 + sid stretch unreproducible
> On Sat, 20 Aug 2016 17:18:10 +0200, Santiago Vila wrote:
> 
> > ok 24 - missing end of line - missing end of line...
> > ok 25 - missing end of line - missing end of line... c
> > ok 26
> > not ok 27
> > Failed 24/50 subtests 
> 
> 
> FWIW, the package builds fine for me (amd64 sid cowbuilder).

Looks like https://rt.cpan.org/Public/Bug/Display.html?id=101278 ;
quoting Slaven:

  So it seems that the completion of the fork() call is quite slow in
  this case. Setting $SIG{INT} to IGNORE did not happen yet in the child,
  so it was unexpectedly killed, and the next write() call caused a
  SIGPIPE in the parent

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

Bug#834906: [Pkg-mozext-maintainers] Bug#834906: xul-ext-adblock-plus: please support conkeror

[David Prévot]

Control: tag -1 upstream

Hi David,

Thank you for your report.

Le 20/08/2016 à 04:15, David Bremner a écrit :
> Package: xul-ext-adblock-plus
> Version: 2.7.3+dfsg-1
> Severity: wishlist
[…]
> I know very little about mozilla extensions, but I _think_ it just
> needs an entry in
> 
> /usr/share/mozilla/extensions/{a79fe89b-6662-4ff4-8e88-09950ad4dfde}

Whatever the fix is, I guess it is worth pushing it upstream. Can you
open (or is there already) an issue upstream about it?

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#834911: libconfig-model-dpkg-perl: FTBFS too much often (Failed 2/12 test programs)

[Niko Tyni]

On Sat, Aug 20, 2016 at 06:54:58PM +0200, gregor herrmann wrote:
> Control: tag -1 + unreproducible
> 
> > Test Summary Report
> > ---
> > t/dependency-check.t   (Wstat: 65280 Tests: 1 Failed: 0)
> >   Non-zero exit status: 255
> >   Parse errors: No plan found in TAP output
> > t/model_tests.t(Wstat: 65280 Tests: 2 Failed: 0)
> >   Non-zero exit status: 255
> >   Parse errors: No plan found in TAP output
> > Files=12, Tests=88,  9 wallclock secs ( 0.07 usr  0.01 sys +  8.99 cusr  
> > 0.59 csys =  9.66 CPU)
> > Result: FAIL

> FWIW, the package builds fine for me (amd64 sid cowbuilder).

The failures seem to be related to these log entries:

 flAbsPath on /var/lib/apt/var/lib/dpkg/status failed - realpath (2: No such 
file or directory)
 Could not open file  - open (2: No such file or directory)
 Problem opening 
 The package lists or status file could not be parsed or opened.

which suggests this is #833656.
-- 
Niko Tyni   nt...@debian.org

Bug#834936: texlive-htmlxml should conflict with tex4ht-common

[Norbert Preining]

> texlive-htmlxml should conflict with tex4ht-common, having two

Thanks, will be in the next upload.

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#834901: texlive-full: biber is missing

[Norbert Preining]

> I had to install it manually with "apt install biber".
> But shouldn't it come with "texlive-full"?

next upload will have texlive-full depending on biber.

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#832704: RFS: nixnote2/2.0~beta8+20160727+ds-1 [ITP] -- Open Source Evernote client

[Sean Whitton]

control: tag -1 +moreinfo

Hello,

It seems that you force-pushed your GitHub repo that you mentioned in an
earlier e-mail.  I tried to use `git pull` to get your latest work, but
that failed.

Please don't edit published history -- I wanted to use `git diff` to
check the changes you had made in response to my review, but now I have
to just check the whole package from scratch.

Could you confirm that https://github.com/hosiet/nixnote2 is the version
that should be reviewed, please?

(I can obtain the tarball from mentors, but you might consider adding it
to your git repository using pristine-tar(1).)

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#834937: sipml5: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: sipml5
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature

Bug#834938: libwiki-toolkit-perl: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: libwiki-toolkit-perl
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature

Bug#834936: texlive-htmlxml should conflict with tex4ht-common

[Adrian Bunk]

Package: texlive-htmlxml
Version: 2016.20160819-1
Severity: normal

texlive-htmlxml should conflict with tex4ht-common, having two
slightly different copies of these 17MB files on the same machine
is not good.

Bug#834898: propellor: problem with the new gpg2

[Johannes Schauer]

Hi Frederic,

On Sat, 20 Aug 2016 14:51:11 +0200 picca  wrote:
> when I run propellor_cronjob, I get this error now
> 
> mordor replace /var/cache/ccache-sbuild/sbuild-setup ... ok
> mordor /var/cache/ccache-sbuild/sbuild-setup mode 365 ... ok
> [2016-08-20 14:46:57 CEST] read: apt-cache ["policy","sbuild"]
> [2016-08-20 14:46:58 CEST] process done ExitSuccess
> [2016-08-20 14:46:58 CEST] call: sbuild-update ["--keygen"]
> Generating archive key.
> gpg: agent_genkey failed: Operation cancelled
> gpg: key generation failed: Operation cancelled
> Exiting from key generation with status 2.
> [2016-08-20 14:47:01 CEST] process done ExitFailure 1
> mordor piuparts schroot conf for System (Debian Linux Unstable) X86_32 ... 
> failed
> 
> 
> Indeed the archive generation is an interactive process now.
> 
> The question is how do we have to deal with this  ?
> 
> Maybe it is possible to create the key non-interactivelly.  Or better provide
> a way to give the sbuild setup the gpg key to use in order to sign the
> archive.

another way would be to change propellor not to run $(sbuild-update --keygen)
anymore at all. Doing this is only required if you want to use sbuild for
chroots containing Debian squeeze or older. If you only build for newer Debian
releases, then signing the internal dummy repository will serve no purpose
other than making your builds slower and requiring lots of entropy during the
one-time setup...

You might want to open another bug against propellor to ask it not to generate
the key anymore if the propellor maintainers agree that that they don't want to
support squeeze chroots anymore.

Also note, that there is a possibility that I will mark this bug as wontfix.
For a reasoning, please refer to the thread on debian-devel starting at [1].

Nevertheless, as I pointed out in the thread, patches are welcome if people
care a lot about keeping squeeze support in sbuild!

Thanks!

cheers, josch

[1] http://lists.debian.org/147145469115.17176.12916309740145620869@localhost


signature.asc
Description: signature

Bug#834933: libcmis package description is not understandable

[Rene Engelhard]

Hi,

On Sat, Aug 20, 2016 at 07:44:31PM +0300, Adrian Bunk wrote:
> Package: libcmis-0.5-5v5 
[...]
> Description-en: CMIS protocol client library
>  LibCMIS is a C++ client library for the CMIS interface.
>  .
>  This allows C++ applications to connect to any ECM behaving as a CMIS server
>  like Alfresco, Nuxeo.
> 
> 
> The average Debian user does not know what ECM or CMIS are.

And this does matter why? I mean, people won't install this _library_
on their own.

I'd have understood if you filed this against cmis-client, but people don't
need to know what CMIS is when they install LibreOffice and use this library
via trying to connect to Google Drive etc.

> Please add something like "accessing documents on a document
> management system" (or whatever is technically correct)
> to the package description.

Well, this is (admittedly badly written) already said with ECM ("Enterprise
Content Management"), but maybe. (And also mention Google Drive etc.)

Regards,

Rene

Bug#834911: libconfig-model-dpkg-perl: FTBFS too much often (Failed 2/12 test programs)

[gregor herrmann]

Control: tag -1 + unreproducible

> Test Summary Report
> ---
> t/dependency-check.t   (Wstat: 65280 Tests: 1 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output
> t/model_tests.t(Wstat: 65280 Tests: 2 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output
> Files=12, Tests=88,  9 wallclock secs ( 0.07 usr  0.01 sys +  8.99 cusr  0.59 
> csys =  9.66 CPU)
> Result: FAIL
> Failed 2/12 test programs. 0/88 subtests failed.
> dh_auto_test: perl Build test --verbose 1 returned exit code 255
> debian/rules:13: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 2
> make[1]: Leaving directory '/<>'
> debian/rules:6: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> 
> 


FWIW, the package builds fine for me (amd64 sid cowbuilder).


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Tom Waits: I Wish I Was In New Orleans


signature.asc
Description: Digital Signature

Bug#834934: refind: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: refind
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature

Bug#834935: makedumpfile: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: makedumpfile
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature

Bug#834912: libfile-tee-perl: FTBFS too much often (Failed 1/2 test programs)

[gregor herrmann]

Control: tag -1 + sid stretch unreproducible

On Sat, 20 Aug 2016 17:18:10 +0200, Santiago Vila wrote:

> [... snipped ...]
> 
> # hello world (7)
> # hello world (8)
> # hello world (9)
> # hello world (10)
> # missing end of line...'
> t/File-Tee.t .. 
> 1..50
> ok 1
> ok 2 - print 0 t
> ok 3 - print 0 c
> ok 4 - print 1 t
> ok 5 - print 1 c
> ok 6 - print 2 t
> ok 7 - print 2 c
> ok 8 - print 3 t
> ok 9 - print 3 c
> ok 10 - print 4 t
> ok 11 - print 4 c
> ok 12 - print 5 t
> ok 13 - print 5 c
> ok 14 - print 6 t
> ok 15 - print 6 c
> ok 16 - print 7 t
> ok 17 - print 7 c
> ok 18 - print 8 t
> ok 19 - print 8 c
> ok 20 - print 9 t
> ok 21 - print 9 c
> ok 22 - print 10 t
> ok 23 - print 10 c
> ok 24 - missing end of line - missing end of line...
> ok 25 - missing end of line - missing end of line... c
> ok 26
> not ok 27
> Failed 24/50 subtests 


FWIW, the package builds fine for me (amd64 sid cowbuilder).


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Supertramp: Waiting So Long


signature.asc
Description: Digital Signature

Bug#831458: tidy: adds too much vertical space

[Francesco Poli]

On Sat, 16 Jul 2016 13:12:44 +0200 Francesco Poli (wintermute) wrote:

[...]
> Hello again,
> besides bug #830066, another thing that I noticed after the upgrade
> 
>   [UPGRADE] tidy:amd64 20091223cvs-1.5 -> 1:5.2.0-1.1
> 
> is that tidy started to add too much vertical space.

Hello!

Thanks for fixing the other bug (#830066).
What's the status of this bug (#831458), on the other hand?
Is there any progress?
Has it been forwarded upstream, by chance?

Please let me know, thanks for your time!


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


pgpm6DOZTdWkx.pgp
Description: PGP signature

Bug#834933: libcmis package description is not understandable

[Adrian Bunk]

Package: libcmis-0.5-5v5
Version: 0.5.1-4
Severity: minor

Description-en: CMIS protocol client library
 LibCMIS is a C++ client library for the CMIS interface.
 .
 This allows C++ applications to connect to any ECM behaving as a CMIS server
 like Alfresco, Nuxeo.


The average Debian user does not know what ECM or CMIS are.

Please add something like "accessing documents on a document
management system" (or whatever is technically correct)
to the package description.

Bug#834914: libur-perl: FTBFS too much often (Failed 1/269 test programs)

[gregor herrmann]

Control: tag -1 + unreproducible

On Sat, 20 Aug 2016 17:18:29 +0200, Santiago Vila wrote:

> Package: src:libur-perl
> Version: 0.440-3
> Severity: serious
> 
> Dear maintainer:
> 
> I tried to build this package with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

For the record, the actual error is:

#   Failed test 'Got second object from the file'
#   at t/URT/t/04e_file_track_open_close.t line 89.
Can't call method "name" on an undefined value at 
t/URT/t/04e_file_track_open_close.t line 90,  line 3.
# Looks like you planned 100 tests but ran 8.
# Looks like you failed 1 test of 8 run.
# Looks like your test exited with 255 just after 8.
t/URT/t/04e_file_track_open_close.t ... 
1..100
ok 1 - Got an object from the file
ok 2 - it has the correct name
ok 3 - new() was called on the file handle
ok 4 - open() was called on the file handle
ok 5 - close() was not called on the file handle
ok 6 - seek() was called on the file handle
ok 7 - seek() was to the correct position
not ok 8 - Got second object from the file
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 93/100 subtests 


FWIW, I can't reproduce it (sid amd64 cowbuilder).


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Johann Strauss: Donauwalzer


signature.asc
Description: Digital Signature