Bug#829293: libatk-wrapper-java: Can't create new web project in Netbeans 8.1 when AtkWrapper is activated

[Ismael]

Package: libatk-wrapper-java
Version: 0.33.3-7
Severity: important

Dear Maintainer,

   * What led up to the situation?

When trying to create a new project the wizard can't finish

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

1. File/New Project/Java Web/Web Application, press next
2. Complete Name and Location, press next
3. Choose GlassFish as deployment Server, press next
4. Framework choose none, press finish

   * What was the outcome of this action?

The wizard didn't close, and all buttons appears disabled (except the help 
button).
The Esc closes the dialog, but the project does not appear in the IDE.
The new project created can be added manually.

A silent error notification appears in the status bar.

Disabling assistive_technology from /etc/java-8-openjdk/accessibility.properties
makes the error disappear.

The silent error notification says "Unexpected Exception", the details show 
this stack trace.


java.lang.NullPointerException
at 
org.GNOME.Accessibility.AtkWrapper$4.propertyChange(AtkWrapper.java:584)
at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335)
at 
java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327)
at 
java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263)
at 
javax.accessibility.AccessibleContext.firePropertyChange(AccessibleContext.java:768)
at 
java.awt.Component$AccessibleAWTComponent$AccessibleAWTComponentHandler.componentHidden(Component.java:9074)
at 
java.awt.AWTEventMulticaster.componentHidden(AWTEventMulticaster.java:190)
at java.awt.Component.processComponentEvent(Component.java:6370)
at java.awt.Component.processEvent(Component.java:6315)
at java.awt.Container.processEvent(Container.java:2236)
at java.awt.Component.dispatchEventImpl(Component.java:4891)
at java.awt.Container.dispatchEventImpl(Container.java:2294)
at java.awt.Component.dispatchEvent(Component.java:4713)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at 
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at 
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.awt.EventQueue$4.run(EventQueue.java:731)
at java.awt.EventQueue$4.run(EventQueue.java:729)
at java.security.AccessController.doPrivileged(Native Method)
at 
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
at org.netbeans.core.TimableEventQueue.dispatchEvent(Unknown Source)
[catch] at 
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at 
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at 
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:109)
at java.awt.WaitDispatchSupport$2.run(WaitDispatchSupport.java:184)
at java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:229)
at java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:227)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.WaitDispatchSupport.enter(WaitDispatchSupport.java:227)
at java.awt.Dialog.show(Dialog.java:1084)
at org.netbeans.core.windows.services.NbPresenter.superShow(Unknown 
Source)
at org.netbeans.core.windows.services.NbPresenter.doShow(Unknown Source)
at org.netbeans.core.windows.services.NbPresenter.run(Unknown Source)
at org.netbeans.core.windows.services.NbPresenter.run(Unknown Source)
at 
org.netbeans.modules.openide.util.NbMutexEventProvider$Event.doEventAccess(Unknown
 Source)
at 
org.netbeans.modules.openide.util.NbMutexEventProvider$Event.readAccess(Unknown 
Source)
at 
org.netbeans.modules.openide.util.LazyMutexImplementation.readAccess(Unknown 
Source)
at org.openide.util.Mutex.readAccess(Unknown Source)
at org.netbeans.core.windows.services.NbPresenter.show(Unknown Source)
at java.awt.Component.show(Component.java:1673)
at java.awt.Component.setVisible(Component.java:1625)
at java.awt.Window.setVisible(Window.java:1014)
at java.awt.Dialog.setVisible(Dialog.java:1005)
at 
org.netbeans.core.windows.services.DialogDisplayerImpl$1AWTQuery.showDialog(Unknown
 Source)
at 
org.netbeans.core.windows.services.DialogDisplayerImpl$1AWTQuery.run(Unknown 
Source)
at 

Bug#829291: qemu-system-x86: missing object iothread

[westlake]

Package: qemu-system-x86
Version:  1:2.5+dfsg-4~bpo8+1
Severity: important

x-data-plane is now known as iothread and is missing from this build of qemu

Bug#829292: autoconf-archive: new upstream version 2016.03.20

[Paul Wise]

Package: autoconf-archive
Version: 20150925-1
Severity: wishlist

The latest upstream version 2016.03.20 has some changes to AX_CHECK_GL
that would appear to fix macOS support. The MacPorts/chromium-bsu
maintainer encountered bugs in the version in Debian unstable:

https://sourceforge.net/p/chromium-bsu/bugs/26/

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

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

Versions of packages autoconf-archive depends on:
ii  dpkg  1.18.7

Versions of packages autoconf-archive recommends:
ii  autoconf  2.69-10

autoconf-archive suggests no packages.

-- no debconf information

-- 

bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#829290: RM: baloo-widgets -- ROM; dead upstream, no more used

[Pino Toscano]

Package: ftp.debian.org
Severity: normal

Hi,

please remove baloo-widgets, since it's part of the unmaintained
Baloo stack in KDE/Plasma 4.

Thanks,
-- 
Pino

Bug#829288: please convert org-mode to use dh_elpa

[Sébastien Delafond]

tags + 829288 confirmed pending
thanks

Excellent suggestion, thanks: I'll convert it this week.

Cheers,

--Seb

On Jul/02, Sean Whitton wrote:
> Source: org-mode
> Severity: wishlist
> Version: 8.3.4-1
> 
> Dear maintainer,
> 
> It would be great if you could convert org-mode to use the new dh_elpa
> infrastructure for Emacs Lisp addons. [1]
> 
> This would allow it to interoperate better with other packages.  It
> would also allow a call to `package-initialize' to load up org-mode and
> packages depending on it without any workarounds.
> 
> I would be willing to adopt the package if you don't have time to do
> this.
> 
> [1] http://pkg-emacsen.alioth.debian.org/elpa-hello/
> 
> -- 
> Sean Whitton
> 

Bug#829289: [mysql-server-5.6] upgrade from 5.5 fails: "cp: cannot overwrite directory ?/var/lib/mysql-upgrade/DATADIR.link/mysql? with non-directory"

[Dmitry Smirnov]

Package: mysql-server-5.6
Version: 5.6.30-1~bpo8+1
Severity: normal

Since Squeeze (or even earlier) I have MySQL set-up with 
symlink "/var/lib/mysql" pointing to another partition with data.

This configuration survived several MySQL (and Debian) upgrades until today
when I tried to install MySQL from jessie-backports that failed to upgrade 
"mysql-server-5.5" (5.5.49-0+deb8u1) as follows:

cp: cannot overwrite directory ‘/var/lib/mysql-upgrade/DATADIR.link/mysql’ 
with non-directory

-- 
Cheers,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


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

Bug#811758: presage: FTBFS with GCC 6: narrowing conversion

[Kentaro Hayashi]

I hope that attached patch solves this issue.

The attached one is minimum patch to fix it, so it may not be ideal solution.

> This package fails to build with GCC 6.  GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.
Description: Fix FTBFS by g++-6
Author: Kentaro Hayashi 
Forwarded: No
--- a/src/lib/core/charsets.h
+++ b/src/lib/core/charsets.h
@@ -42,7 +42,7 @@
 const char PAGE_DOWN   = 128;
 
 
-const char DEFAULT_WORD_CHARS[]={
+const unsigned char DEFAULT_WORD_CHARS[]={
 'A',
 'B',
 'C',
--- a/src/lib/core/context_tracker/contextTracker.cpp
+++ b/src/lib/core/context_tracker/contextTracker.cpp
@@ -37,11 +37,11 @@
 ContextTracker::ContextTracker(Configuration* config,
 			   PredictorRegistry* registry,
 			   PresageCallback* callback,
-			   const char wChars[],
+			   const unsigned char wChars[],
 			   const char tChars[],
 			   const char bChars[],
 			   const char cChars[])
-: wordChars  (wChars),
+: wordChars  (reinterpret_cast(wChars)),
   separatorChars (tChars),
   blankspaceChars(bChars),
   controlChars   (cChars),
--- a/src/lib/core/context_tracker/contextTracker.h
+++ b/src/lib/core/context_tracker/contextTracker.h
@@ -157,7 +157,7 @@
 ContextTracker(Configuration* config,
 		   PredictorRegistry* predictorRegistry,
 		   PresageCallback* callback,
-		   const char[]=DEFAULT_WORD_CHARS,
+		   const unsigned char[]=DEFAULT_WORD_CHARS,
const char[]=DEFAULT_SEPARATOR_CHARS,
const char[]=DEFAULT_BLANKSPACE_CHARS,
const char[]=DEFAULT_CONTROL_CHARS );
--- a/test/lib/core/context_tracker/contextChangeDetectorTest.cpp
+++ b/test/lib/core/context_tracker/contextChangeDetectorTest.cpp
@@ -30,7 +30,7 @@
 
 void ContextChangeDetectorTest::setUp()
 {
-detector = new ContextChangeDetector(DEFAULT_WORD_CHARS,
+detector = new ContextChangeDetector(reinterpret_cast(DEFAULT_WORD_CHARS),
 	 DEFAULT_SEPARATOR_CHARS,
 	 DEFAULT_BLANKSPACE_CHARS,
 	 DEFAULT_CONTROL_CHARS,
--- a/test/lib/predictors/predictorsTestMockObjects.cpp
+++ b/test/lib/predictors/predictorsTestMockObjects.cpp
@@ -31,7 +31,7 @@
 ContextTracker::ContextTracker(Configuration* config,
 			   PredictorRegistry* predictorRegistry,
 			   PresageCallback* callback,
-			   const char wc[],
+			   const unsigned char wc[],
 			   const char sc[],
 			   const char bc[],
 			   const char cc[])


pgp7u8OXN_Jb9.pgp
Description: PGP signature

Bug#829208: RFS: evil-paredit-el/0.0.2-1 ITP

[Sean Whitton]

Hello,

On Sat, Jul 02, 2016 at 03:06:41AM +0300, Dmitry Bogatov wrote:
> > 2. evil-paredit.el declares a dependency on paredit version "25beta".
> >But we have version 24 in Debian.[1]  Have you tested that it works with
> >paredit 24?  I have noticed that the current generation of Elisp
> >hackers declare dependencies newer than they actually need so maybe
> >we are in luck.
> 
> Relaxed dependency. Works for me.

I had at upstream's commit history and it seems that they have added
compatibility code so that it works with various versions of paredit.

You should definitely forward the dependency relaxation upstream: they
shouldn't be declaring so tight a dependency if they have the
compatibility code.

-- 
Sean Whitton

Bug#829288: please convert org-mode to use dh_elpa

[Sean Whitton]

Source: org-mode
Severity: wishlist
Version: 8.3.4-1

Dear maintainer,

It would be great if you could convert org-mode to use the new dh_elpa
infrastructure for Emacs Lisp addons. [1]

This would allow it to interoperate better with other packages.  It
would also allow a call to `package-initialize' to load up org-mode and
packages depending on it without any workarounds.

I would be willing to adopt the package if you don't have time to do
this.

[1] http://pkg-emacsen.alioth.debian.org/elpa-hello/

-- 
Sean Whitton

Bug#828166: RFS: speedcrunch/0.11-1 [ITA]

[Sean Whitton]

Hello,

On Sat, Jul 02, 2016 at 01:03:01AM +, Felix Krull wrote:
> I must say I'm a bit confused about how the Developer Reference
> suggests to "concentrate on describing significant and user-visible
> changes," but the informal advice I've heard on changelog entries was
> always to be very detailed and granular, which to me seems more like a
> job for VCS history than a changelog.

It's true that debian-mentors@lists.d.o has a culture of very detailed
changelogs.  I suspect that it is because it makes reviewing RFSs much
easier.  It is also good practice for team-maintained packages, which
these days is a lot of them -- there were probably far fewer
team-maintained packages when that part of the Developer's Reference was
written.

When deciding whether to add a changelog entry, I try to imagine that
I'm someone trying to perform an NMU or team upload.  What information
would I want to know if I was doing that?  That's a helpful heuristic.

-- 
Sean Whitton

Bug#734237: btrfs-tools: btrfs lockup with RT kernel

[Osamu Aoki]

Hi,
On Tue, Jun 28, 2016 at 04:16:57PM -0400, Nicholas D Steeves wrote:
> Hi Osamu,
> 
> Is this bug still present in linux-image-4.6.0-1-rt-amd64=4.6.2-2?

I have not been using btrfs recently.  So I do not know.

Unless someone object, please close this bug since it does not help
anyone.  (And I think it probably fixed by now in the upstream.)

Regards,

Osamu

Bug#828478: [PATCH v2] ovs-pki: Use SHA-512 instead of SHA-1 as message digest.

[Ben Pfaff]

The upcoming OpenSSL 1.1.0 release disables use of SHA-1, which breaks the
OVS unit tests, which use SHA-1.  We last tried to switch to SHA-512 in
2014 with commit 9ff33ca75e9fcc ("ovs-pki: Use SHA-512 instead of MD5 as
message digest."), but we had to downgrade to SHA-1 in commit 4a1f9610682d
("ovs-pki: Use SHA-1 instead of SHA-512 as message digest.") because
XenServer did not support SHA-512.  It has been a few years, so let's try
again.

CC: 828...@bugs.debian.org
Reported-at: https://bugs.debian.org/828478
Reported-by: Kurt Roeckx 
Signed-off-by: Ben Pfaff 
---
v1->v2: Suggested by Kurt Roeckx;
  - Use sha512 unconditionally.
  - Drop AUTHORS update.
  - Add NEWS update.

 NEWS | 4 
 utilities/ovs-pki.in | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/NEWS b/NEWS
index 802e7f8..e7b43d2 100644
--- a/NEWS
+++ b/NEWS
@@ -75,6 +75,10 @@ Post-v2.5.0
  watch with tcpdump
- Introduce --no-self-confinement flag that allows daemons to work with
  sockets outside their run directory.
+   - ovs-pki: Changed message digest algorithm from SHA-1 to SHA-512 because
+ SHA-1 is no longer secure and some operating systems have started to
+ disable it in OpenSSL.
+
 
 v2.5.0 - 26 Feb 2016
 -
diff --git a/utilities/ovs-pki.in b/utilities/ovs-pki.in
index 9b2b5aa..7a992a5 100755
--- a/utilities/ovs-pki.in
+++ b/utilities/ovs-pki.in
@@ -274,7 +274,7 @@ private_key= $dir/private/cakey.pem# CA private key
 RANDFILE   = $dir/private/.rand# random number file
 default_days   = 3650  # how long to certify for
 default_crl_days= 30   # how long before next CRL
-default_md = sha1  # message digest to use
+default_md = sha512# message digest to use
 policy = policy# default policy
 email_in_dn= no# Don't add the email into cert DN
 name_opt   = ca_default# Subject name display option
-- 
2.1.3

Bug#828166: RFS: speedcrunch/0.11-1 [ITA]

[Felix Krull]

Thanks for the reviews!

On Mon, 27 Jun 2016 at 15:23 Gianfranco Costamagna 
wrote:

> please try to be more verbose in changelog:
> >bump std-version (maybe extract in a new changelog entry)
>
>
> copyright in machine readable format
>

I'm not sure what you mean by that? But I extended the changelog somewhat.

I must say I'm a bit confused about how the Developer Reference suggests to
"concentrate on describing significant and user-visible changes," but the
informal advice I've heard on changelog entries was always to be very
detailed and granular, which to me seems more like a job for VCS history
than a changelog.

d/p/0001: did you forward it upstream?
>

That was backported from upstream, so not necessary. I added an Origin
header field to the patch to make that explicit (also changed to a more
concise file name).


>
> >override_dh_auto_clean:
> > dh_auto_clean
> > rm -f speedcrunch.1 speedcrunch.xpm
>
>
> I usually like more
>
>
> echo -e "speedcrunch.1\nspeedcrunch.xpm" > debian/clean
>

other stuff LGTM!
>
> thanks for the nice cleanup :)
>
> also, why do you force buildsystem and builddirectory?
>

Originally, "why not" :) But forcing CMake prevents dh from picking up the
.pro file in the same directory and using qmake. "--builddirectory" was,
indeed, unnecessary.


> and last thing:
> BLD_VERBOSE=1
>
> please export it, we have tools (blhc) scanning build logs for missing
> flags,
> so please make the build verbose (I don't care about DH_VERBOSE)
>

Good point, I changed it.

(I'm assuming that uploading a new package with the same version is an
acceptable way to use mentors.d.n, mostly because it didn't stop me.)

Bug#829287: ITP: cava -- terminal audio visualiser

[Nicolas Braud-Santoni]

X-Debbugs-Cc: debian-de...@lists.debian.org
Package: wnpp
Severity: wishlist
Owner: Nicolas Braud-Santoni 

* Package name: cava
  Version : 0.4.1
  Upstream Author : Karl Stravestrand 
* URL : http://karlstav.github.io/cava
* License : Expat
  Programming Lang: C
  Description : Curses-like audio visualizer

C.A.V.A. is a bar spectrum audio visualizer for the terminal,
using ALSA, pulseaudio or fifo buffer for input.

This program is not intended for scientific use.
It's written to look responsive and aesthetic when used on music. 

Bug#828478: [PATCH] ovs-pki: Use SHA-512 message digest when available.

[Ben Pfaff]

On Sun, Jun 26, 2016 at 08:55:04PM +0200, Kurt Roeckx wrote:
> On Sun, Jun 26, 2016 at 11:05:35AM -0700, Ben Pfaff wrote:
> > The upcoming OpenSSL 1.1.0 release disables use of SHA-1, which breaks the
> > OVS unit tests, which use SHA-1.  We last tried to switch to SHA-512 in
> > 2014 with commit 9ff33ca75e9fcc ("ovs-pki: Use SHA-512 instead of MD5 as
> > message digest."), but we had to downgrade to SHA-1 in commit 4a1f9610682d
> > ("ovs-pki: Use SHA-1 instead of SHA-512 as message digest.") because
> > XenServer did not support SHA-512.
> > 
> > This commit detects support for SHA-512 and uses it if available, so it
> > should avoid the problem encountered previously.
> 
> Note that openssl has supported SHA-512 for a while.  It's been
> supported since 0.9.8 which was released in 2005.  So that support
> detection doesn't look like a good idea.
> 
> You indicated that XenServer didn't support it.  Did that change?

I don't know.

I guess we could always just try again and see if XenServer folks
complain again.

Honestly I'd prefer to have a fixed choice.

> From what I understand of the log it's that the certificate still
> using a weak digest.  I guess we started to rejected SHA-1 by
> default now, which is actually a good thing.  The browsers should
> stop supporting it soon too.
> 
> I suggest you just switch to SHA-256 or SHA-512 by default.
> 
> > diff --git a/AUTHORS b/AUTHORS
> > index 704ba40..a893330 100644
> > --- a/AUTHORS
> > +++ b/AUTHORS
> > @@ -367,6 +367,7 @@ Konstantin Khorenko khore...@openvz.org
> >  Kris zhang  zhang.k...@gmail.com
> >  Krishna Miriyalakris...@nicira.com
> >  Krishna Mohan Elluruelluru.kri.mo...@hpe.com
> > +Kurt Roeckx k...@roeckx.be
> 
> There really is no reason to add me, it's not like I contributed
> anything, someone else tried to build it and I just filed bugs
> based on that.

OK.  I habitually add people who report bugs, since bug reporting is a
kind of public service.  I'll drop it for v2.

Thanks,

Ben.

Bug#829208: RFS: evil-paredit-el/0.0.2-1 ITP

[Sergio Durigan Junior]

On Friday, July 01 2016, Dmitry Bogatov wrote:

>> 1. In d/copyright, the license should be called "Expat" not "MIT" since
>>"MIT" is ambiguous between several different licenses.
>
> Is it true? AFAIC, there are 3 versions of BSD (2,3,4 clauses) and only
> one MIT.

Debian uses Expat instead of MIT.  There are unfortunately many "MIT
licenses" and the interpretation is ambiguous:

  

  

See also DEP5:

  

Cheers,

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


signature.asc
Description: PGP signature

Bug#792505: Please remove .pth from your package

[Iain R. Learmonth]

Control: tags -1 + moreinfo

Hi,

On Wed, 15 Jul 2015 15:43:58 +0200 Thomas Goirand  wrote:
> Please remove the .pth file.

I've produced a new version for this package (0.8-0.1) and was unable to
reproduce this issue with that. Once it's cleared NEW, please let me
know if you still have this problem.

Thanks,
Iain.

Bug#829208: RFS: evil-paredit-el/0.0.2-1 ITP

[Dmitry Bogatov]

> 1. In d/copyright, the license should be called "Expat" not "MIT" since
>"MIT" is ambiguous between several different licenses.

Is it true? AFAIC, there are 3 versions of BSD (2,3,4 clauses) and only
one MIT.

> 2. evil-paredit.el declares a dependency on paredit version "25beta".
>But we have version 24 in Debian.[1]  Have you tested that it works with
>paredit 24?  I have noticed that the current generation of Elisp
>hackers declare dependencies newer than they actually need so maybe
>we are in luck.

Relaxed dependency. Works for me.

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Web-Site: sinsekvu.github.io

Bug#829286: RFS: newlisp/10.7.0-2

[Sergio Durigan Junior]

Package: sponsorship-requests
Severity: normal

Hi,

I'd like to get a few changes I've made to newlisp uploaded.  They
basically fix two bugs: 828805 and 828806.

The changes are:

- Support GNU/kFreeBSD builds (by creating the necessary makefiles and
  adjusting source files accordingly), and

- Do not use -m32/-m64 when building.

I have also updated the Vcs-* links in order to reflect the use of
collab-maint instead of my personal git server.

I'm Cc'ing Andrey Rahmatullin on this message because he is the DD who
sponsored the package first, so I believe I should give him "precedence"
(also because I'd like to get DM rights on newlisp, so it's easier if I
work with just one person).

The package can be found at:

  

And can be downloaded with:

  dget -x 
https://mentors.debian.net/debian/pool/main/n/newlisp/newlisp_10.7.0-2.dsc

Thanks,

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


signature.asc
Description: PGP signature

Bug#829208: RFS: evil-paredit-el/0.0.2-1 ITP

[Sean Whitton]

control: owner -1 !
control: tag -1 +moreinfo

Hello Dmitry,

Here is a preliminary review (haven't tried installing and using yet,
due to item (2) below).

1. In d/copyright, the license should be called "Expat" not "MIT" since
   "MIT" is ambiguous between several different licenses.

2. evil-paredit.el declares a dependency on paredit version "25beta".
   But we have version 24 in Debian.[1]  Have you tested that it works with
   paredit 24?  I have noticed that the current generation of Elisp
   hackers declare dependencies newer than they actually need so maybe
   we are in luck.

If it works with paredit 24 you will need to either add a patch, or
remove ${elpa:Depends} and specify the two elpa-* dependencies manually.

[1] I found a copy of paredit 25beta and it says "THIS FILE IS SUBJECT
TO CHANGE, AND NOT SUITABLE FOR DISTRIBUTION BY PACKAGE MANAGERS
SUCH AS APT" so it looks like we'll be on 24 for a while.

-- 
Sean Whitton

Bug#828190: [pulseaudio] sometimes locks up with emu10k1 sink

[Felipe Sateler]

Hi,

On 1 July 2016 at 16:04, Michał Mirosław  wrote:
> On Wed, Jun 29, 2016 at 12:03:40PM -0300, Felipe Sateler wrote:
>> On 25 June 2016 at 18:48, Michał Mirosław  wrote:
>> > On Sun, Jun 26, 2016 at 12:36:42AM +0200, Michał Mirosław wrote:
>> >> This stopped (resulting in working sound) after I changed
>> >> /etc/pulse/daemon.conf's default-sample-rate from 48000 to 44100,
>> >> commented alternate-sample-rate 44100 line and killed pulseaudio.
>> >> The problem didn't reappear after reverting the changes and killing
>> >> pulseaudio again, though.
>> >
>> > It locked up again. Commenting out alternate-sample-rate works
>> > as a workaround.
>> Could you attach a verbose log of the problem appearing? Instructions
>> to do so are here: https://wiki.ubuntu.com/PulseAudio/Log
>
> Logs attached: first buggy, then working.

Did this ever work? Could you try with a different kernel (in
particular, with the stock ones debian provides)? Looks like a driver
bug to me, as the driver for some reason can be successfully changed
one time, but not after suspend-resume:

(  27.938|   0.000) D: [pulseaudio] sink-input.c: Negotiated format:
pcm, format.sample_format = "\"s16le\""  format.rate = "44100"
format.channels = "2"  format.channel_map =
"\"front-left,front-right\""
(  27.938|   0.000) I: [pulseaudio] sink-input.c: Trying to change sample rate
(  27.938|   0.000) D: [pulseaudio] sink.c: Suspending sink
alsa_output.pci-_07_01.0.analog-stereo due to changing the sample
rate.
(  27.938|   0.000) I: [pulseaudio] alsa-sink.c: Updating rate for
device front:1, new rate is 44100
(  27.938|   0.000) D: [pulseaudio] source.c: Suspending source
alsa_output.pci-_07_01.0.analog-stereo.monitor due to changing the
sample rate.
(  27.938|   0.000) I: [pulseaudio] source.c: Changed sampling rate successfully
(  27.938|   0.000) I: [pulseaudio] sink.c: Changed sampling rate successfully
(  27.938|   0.000) I: [pulseaudio] sink-input.c: Rate changed to 44100 Hz
(  27.938|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring
volume for sink input sink-input-by-application-name:MPlayer.
(  27.938|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring
mute state for sink input sink-input-by-application-name:MPlayer.
(  27.938|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink
alsa_output.pci-_07_01.0.analog-stereo becomes busy, resuming.
(  27.938|   0.000) D: [pulseaudio] sink.c: Suspend cause of sink
alsa_output.pci-_07_01.0.analog-stereo is 0x, resuming
(  27.938|   0.000) D: [pulseaudio] reserve-wrap.c: Successfully
acquired reservation lock on device 'Audio1'
(  27.938|   0.000) I: [alsa-sink-emu10k1] alsa-sink.c: Trying resume...
(  27.939|   0.000) I: [alsa-sink-emu10k1] alsa-util.c: Cannot disable
ALSA period wakeups
(  27.939|   0.000) D: [alsa-sink-emu10k1] alsa-util.c: Maximum hw
buffer size is 341 ms
(  27.939|   0.000) D: [alsa-sink-emu10k1] alsa-util.c: Set buffer
size first (to 17832 samples), period size second (to 17832 samples).
(  27.939|   0.000) I: [alsa-sink-emu10k1] alsa-util.c: Device front:1
doesn't support 44100 Hz, changed to 48000 Hz.


Also, please give a try to the pulseaudio version in experimental, to
see if that improves the issue.

There may still be a pulseaudio bug, in that it should probably not
keep getting stuck in the suspend-resume loop...

-- 

Saludos,
Felipe Sateler

Bug#821409: Processed: severity of 821409 is important

[Adrian Bunk]

On Sat, Jul 02, 2016 at 12:52:36AM +0200, Michael Biebl wrote:
> Hi Adrian

Hi Michael,

> Am 02.07.2016 um 00:30 schrieb Adrian Bunk:
> > At least one bug in src:gtk+3.0 really has to stay RC when an upgrade of 
> > this library causes widespread breakage at the level of "all toolbar 
> > icons in emacs disappeared" - I cannot imagine any scenario where
> > such a widespread breakage would not be considered a blocker for
> > a release, and having a "release critical" bug makes that visible.
> 
> The point is, that this isn't really a bug in gtk+3.0, i.e. something
> which can be fixed in gtk+3.0 itself.

Part of the fix has to be in the gtk+3.0 packages:

There must be Breaks on the unfixed versions of the packages that need 
fixing after they are fixed - otherwise partial upgrades and testing 
users might still observe the problem, and this also makes it easier
for distributions like Ubuntu to avoid non-working package
combinations.

> By bumping this bug to RC, this
> bug will show up for all users e.g. via apt-listbugs, even if they don't
> use emacs (or one of the 3rd party themes). I don't think we really want
> that.

Why do you not want that?

I worked around the problem on my computer by manually downgrading
to 3.18 and not planning to upgrade again before all this got fixed.

Everything that warns users will reduce the number of users who 
discover this the hard way.

> Regards,
> Michael

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#828807: newlisp: FTBFS on powerpc: test suite segmentation fault

[Sergio Durigan Junior]

Control: tags -1 + unreproducible

On Monday, June 27 2016, Aaron M. Ucko wrote:

> newlisp's compilation succeeded on powerpc, but the test suite
> proceeded to crash:
>
>make check | grep '>>>'
>make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent 
> make rule.
>make[2]: *** [check] Segmentation fault
>
> I don't have further details, but perhaps you can reproduce the
> problem on a porterbox.

I can't reproduce this.  I believe it may have something to do with the
machine it was built.  I'll upload a fix for the other bugs soon, and
see how the ppc build performs.  Depending on the results I'll close
this bug.

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


signature.asc
Description: PGP signature

Bug#829285: python3-mock: Missing dependency on python3-funcsigs

[Jeremy Bicha]

Package: python3-mock
Version: 2.0.0-1

python3-mock from experimental (2.0.0-1) does not depend on
python3-funcsigs but python3-mock 1.3.0-2.1 did.

This led to a build failure of python-acme in Ubuntu yakkety (which
synced python-mock from experimental) where it was expecting
python3-funcsigs to be installed.

https://packages.debian.org/unstable/python3-mock
https://packages.debian.org/experimental/python3-mock

https://launchpad.net/ubuntu/+source/python-acme/0.8.1-1/+build/10198484

Thanks,
Jeremy Bicha

Bug#829284: git: determine mainline in cherry-pick by reachability

[Simon Richter]

Package: git
Version: 1:2.1.4-2.1+deb8u2
Severity: wishlist
Tags: upstream

Hi,

I'm trying to cherry-pick merges in a script, and the manual page says that
in order to do that, I need to pass the number of the "mainline" ancestor
in the list of parents.

This is rather annoying to use from a script, especially as it should be
easy to determine automatically: the mainline is the commit that is
reachable from the current mainline branch.

So it would be nice to have an option that allows me to treat a certain
commit-ish as the mainline, with the expectation that only one of the
parent commits of the merge commit being cherry-picked will be reachable
from that revision.

If that isn't possible for some reason, it would be nice if I could at
least use a commit ID instead of an index into a list of commit IDs -- that
would make scripting a lot easier.

   Simon

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

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

Versions of packages git depends on:
ii  git-man  1:2.1.4-2.1+deb8u2
ii  libc62.19-18+deb8u4
ii  libcurl3-gnutls  7.38.0-4+deb8u3
ii  liberror-perl0.17-1.1
ii  libexpat12.1.0-6+deb8u3
ii  libpcre3 2:8.35-3.3+deb8u4
ii  perl-modules 5.20.2-3+deb8u5
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages git recommends:
ii  less 458-3
ii  openssh-client [ssh-client]  1:6.7p1-5+deb8u2
ii  patch2.7.5-1
ii  rsync3.1.1-3

Versions of packages git suggests:
ii  gettext-base  0.19.3-2
pn  git-arch  
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
pn  git-el
ii  git-email 1:2.1.4-2.1+deb8u2
pn  git-gui   
pn  git-mediawiki 
ii  git-svn   1:2.1.4-2.1+deb8u2
pn  gitk  
pn  gitweb

-- no debconf information

Bug#823612: rescue-mode should mount /boot/efi if it's available

[Ben Hutchings]

On Fri, 2016-07-01 at 23:05 +0100, Steve McIntyre wrote:
> On Fri, Jul 01, 2016 at 11:41:58PM +0200, Ben Hutchings wrote:
> > On Fri, 2016-07-01 at 21:56 +0100, Steve McIntyre wrote:
> > > On Tue, Jun 28, 2016 at 09:13:25PM +0200, Ben Hutchings wrote:
> > > > 
> > > > I wonder why we offer to mount /boot but not /usr (more and more
> > > > programs live there), /var (some of them might need state there) or
> > > > /tmp (don't want to create files there that will never be cleaned
> > > > up).
> > > 
> > > Maybe, yes. For now I've made the code here much more generic to make
> > > it easier to ask about other filesystems, and added a check for
> > > /boot/efi too.
> > > 
> > > > Also, does the question about mounting /boot really merit critical
> > > > priority?  Is 'yes' not a good default?
> > > 
> > > *If* the /boot fs is broken, attempting to auto-mount is probably not
> > > a good plan.
> > 
> > That's true.  Perhaps the sensible thing is perhaps to mount /usr and
> > the virtual filesystems unconditionally, and then ask whether to mount
> > all the other local filesystem ('mount -a -O no_network').
> 
> How are /usr and any other disk-based filesystems likely to be any
> different to /boot here?

/usr should be mounted unconditionally because binaries on the root
filesystem may in practice depend on it or there may not even be any
binaries on the root filesystem (https://wiki.debian.org/UsrMerge).

For the other local filesystems, I'm proposing that we ask a single
question whether to mount them rather than asking separately about
/boot, /boot/efi, etc.

> I'd agree about the virtual fsen...

And the essential virtual filesystems do already get mounted
unconditionally.

Ben.

-- 

Ben Hutchings
Never attribute to conspiracy what can adequately be explained by
stupidity.


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

Bug#820877: votca-csg-scripts: depends on unknown package perl5

[Steve Langasek]

Control: tags -1 patch pending

Hi folks,

This bug was already fixed once in NMU (1.2.4-2.1, bug #808321); but it
seems this fix was never included in the maintainer repository and has been
dropped in the latest upload.

I'm uploading a new NMU for this, directly to unstable (not delayed), with
the attached patch.  Please consider applying this fix in subversion as
well, so that your future uploads will be releasable :-)

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru votca-csg-1.3.0/debian/changelog votca-csg-1.3.0/debian/changelog
--- votca-csg-1.3.0/debian/changelog	2016-03-02 23:59:44.0 +
+++ votca-csg-1.3.0/debian/changelog	2016-07-01 22:36:33.0 +
@@ -1,3 +1,10 @@
+votca-csg (1.3.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Depend on perl, not perl5 which is long obsolete.  Closes: #820877.
+
+ -- Steve Langasek   Fri, 01 Jul 2016 22:36:32 +
+
 votca-csg (1.3.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru votca-csg-1.3.0/debian/control votca-csg-1.3.0/debian/control
--- votca-csg-1.3.0/debian/control	2016-03-02 23:59:24.0 +
+++ votca-csg-1.3.0/debian/control	2016-07-01 22:36:25.0 +
@@ -52,7 +52,7 @@
 
 Package: votca-csg-scripts
 Architecture: all
-Depends: bash (>= 4), perl5, ${misc:Depends}, ${python:Depends}
+Depends: bash (>= 4), perl, ${misc:Depends}, ${python:Depends}
 Description: VOTCA's coarse-graining scripts
  VOTCA is a software package which focuses on the analysis of molecular
  dynamics data, the development of systematic coarse-graining techniques as


signature.asc
Description: PGP signature

Bug#821409: Processed: severity of 821409 is important

[Michael Biebl]

Hi Adrian

Am 02.07.2016 um 00:30 schrieb Adrian Bunk:
> did you accidentially also lower the severity of 824891?
> 
> At least one bug in src:gtk+3.0 really has to stay RC when an upgrade of 
> this library causes widespread breakage at the level of "all toolbar 
> icons in emacs disappeared" - I cannot imagine any scenario where
> such a widespread breakage would not be considered a blocker for
> a release, and having a "release critical" bug makes that visible.

The point is, that this isn't really a bug in gtk+3.0, i.e. something
which can be fixed in gtk+3.0 itself. By bumping this bug to RC, this
bug will show up for all users e.g. via apt-listbugs, even if they don't
use emacs (or one of the 3rd party themes). I don't think we really want
that.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#817778: info-beamer: nmu 1.0~pre3+dfsg-0.1

[James Cowgill]

Hi,

On Thu, 2016-06-30 at 19:56 +0200, Noël Köthe wrote:
> Hello James,
> 
> Am Mittwoch, den 29.06.2016, 02:14 +0100 schrieb James Cowgill:
> 
> > I have uploaded an NMU to DELAYED/10 to fix the following bugs.
> > Please tell me if I should cancel / delay it.
> >  #817778 silkscreen font is not DFSG compliant
> >  #826288 info-beamer: please use glfw3
> 
> Thanks for your work! You can upload it again without delay if you
> like.

Thanks, I've rescheduled the NMU to the 0-day queue so it should be
processed anytime now.

James

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

Bug#826240: maradns: diff for NMU version 2.0.13-1.1

[Christian Hofstaedtler]

Control: tags 826240 + patch
Control: tags 826240 + pending

Dear maintainer,

I've prepared an NMU for maradns (versioned as 2.0.13-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Best,
Christian

diff -Nru maradns-2.0.13/debian/changelog maradns-2.0.13/debian/changelog
--- maradns-2.0.13/debian/changelog 2015-10-03 09:37:13.0 +0200
+++ maradns-2.0.13/debian/changelog 2016-07-01 17:38:52.0 +0200
@@ -1,3 +1,11 @@
+maradns (2.0.13-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Setup nss-lookup.target dependency for systemd, providing the
+equivalent of the $named insserv facility. (Closes: #826240)
+
+ -- Christian Hofstaedtler   Fri, 01 Jul 2016 17:35:39 +0200
+
 maradns (2.0.13-1) unstable; urgency=medium
 
   * Imported Upstream version 2.0.13
diff -Nru maradns-2.0.13/debian/maradns.install 
maradns-2.0.13/debian/maradns.install
--- maradns-2.0.13/debian/maradns.install   2015-10-03 09:37:13.0 
+0200
+++ maradns-2.0.13/debian/maradns.install   2016-07-01 17:38:52.0 
+0200
@@ -1,5 +1,6 @@
 debian/maradns-insserv etc/insserv.conf.d
 debian/mararc etc/maradns
+debian/nss-lookup.target.conf lib/systemd/system/maradns.service.d
 server/maradns usr/sbin
 tcp/fetchzone usr/sbin
 tcp/getzone usr/sbin
diff -Nru maradns-2.0.13/debian/nss-lookup.target.conf 
maradns-2.0.13/debian/nss-lookup.target.conf
--- maradns-2.0.13/debian/nss-lookup.target.conf1970-01-01 
01:00:00.0 +0100
+++ maradns-2.0.13/debian/nss-lookup.target.conf2016-07-01 
17:38:52.0 +0200
@@ -0,0 +1,6 @@
+# Add nss-lookup.target to automatically generated service, providing
+# the equivalent of the $named facility.
+
+[Unit]
+Wants=nss-lookup.target

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#828083: [Pkg-clamav-devel] Bug#828083: bind9: clamav with openssl 1.1: Doesn't find openssl

[Sebastian Andrzej Siewior]

control: forwarded -1 https://bugzilla.clamav.net/show_bug.cgi?id=11594
control: tags -1 + patch

On 2016-06-24 21:20:07 [+0200], Kurt Roeckx wrote:

> Your package is FTBFS with openssl 1.1:
…
> Kurt

Sebastian
>From f6e66c4b73cc4a0ce813c19ee210c8d974cf0787 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Sat, 2 Jul 2016 00:12:01 +0200
Subject: [PATCH] make it compile against openssl 1.1.0

- SSL_library_init() is no longer a function but a define invoking
  another function with parameters. Thus a link check against this
  function will fail. As a fix AC_LINK_IFELSE is used so the header file
  can be included.

- X509_CRL is opaque and needs an accessor. X509_CRL_get_nextUpdate() is
  around since OpenSSL 0.9.1c. X509_cmp_current_time() seems to be
  around since SSLeay 0.8.1b.

BTS: https://bugs.debian.org/828083

Signed-off-by: Sebastian Andrzej Siewior 
---
 libclamav/crypto.c| 21 ++---
 m4/reorganization/libs/openssl.m4 | 12 +---
 2 files changed, 15 insertions(+), 18 deletions(-)

diff --git a/libclamav/crypto.c b/libclamav/crypto.c
index c62c65a..4be900f 100644
--- a/libclamav/crypto.c
+++ b/libclamav/crypto.c
@@ -1096,7 +1096,6 @@ X509_CRL *cl_load_crl(const char *file)
 {
 X509_CRL *x=NULL;
 FILE *fp;
-struct tm *tm;
 
 if (!(file))
 return NULL;
@@ -1110,21 +1109,13 @@ X509_CRL *cl_load_crl(const char *file)
 fclose(fp);
 
 if ((x)) {
-tm = cl_ASN1_GetTimeT(x->crl->nextUpdate);
-if (!(tm)) {
-X509_CRL_free(x);
-return NULL;
-}
+	ASN1_TIME *tme;
 
-#if !defined(_WIN32)
-if (timegm(tm) < time(NULL)) {
-X509_CRL_free(x);
-free(tm);
-return NULL;
-}
-#endif
-
-free(tm);
+	tme = X509_CRL_get_nextUpdate(x);
+	if (!tme || X509_cmp_current_time(tme) < 0) {
+		X509_CRL_free(x);
+		return NULL;
+	}
 }
 
 return x;
diff --git a/m4/reorganization/libs/openssl.m4 b/m4/reorganization/libs/openssl.m4
index 78e2c23..45ee02d 100644
--- a/m4/reorganization/libs/openssl.m4
+++ b/m4/reorganization/libs/openssl.m4
@@ -26,12 +26,13 @@ save_LDFLAGS="$LDFLAGS"
 save_CFLAGS="$CFLAGS"
 save_LIBS="$LIBS"
 
-SSL_LIBS="-lssl -lcrypto -lz"
+SSL_LIBS="$LIBS -lssl -lcrypto -lz"
+LIBS="$LIBS $SSL_LIBS"
 
 if test "$LIBSSL_HOME" != "/usr"; then
 SSL_LDFLAGS="-L$LIBSSL_HOME/lib"
 SSL_CPPFLAGS="-I$LIBSSL_HOME/include"
-LDFLAGS="-L$LIBSSL_HOME/lib $SSL_LIBS"
+LDFLAGS="-L$LIBSSL_HOME/lib"
 CFLAGS="$SSL_CPPFLAGS"
 else
 SSL_LDFLAGS=""
@@ -41,7 +42,12 @@ fi
 have_ssl="no"
 have_crypto="no"
 
-AC_CHECK_LIB([ssl], [SSL_library_init], [have_ssl="yes"], [AC_MSG_ERROR([Your OpenSSL installation is misconfigured or missing])], [-lcrypto -lz])
+AC_LINK_IFELSE(
+	   [AC_LANG_PROGRAM([[#include ]],
+[[SSL_library_init();]])],
+	   [have_ssl="yes";],
+	   [AC_MSG_ERROR([Your OpenSSL installation is misconfigured or missing])])
+
 
 AC_CHECK_LIB([crypto], [EVP_EncryptInit], [have_crypto="yes"], [AC_MSG_ERROR([Your OpenSSL installation is misconfigured or missing])], [-lcrypto -lz])
 
-- 
2.8.1

Bug#829283: totem failed to read video with nvidia driver

[gpe92]

Package: totem
Version: 3.20.1-3
Severity: normal

Dear Maintainer,


   * What led up to the situation?

Trying to read a video

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

totem 

   * What was the outcome of this action?

A dialog box with an error from ffmpeg, or the sound during few seconds
but without any image.
An error message when launch from a terminal:
totem P6040272.mov 
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0

(totem:4549): Gtk-WARNING **: Drawing a gadget with negative dimensions. Did 
you forget to allocate a size? (node slider owner GtkScale)

(totem:4549): Cogl-WARNING **: driver/gl/cogl-framebuffer-gl.c:157: GL error 
(1280): Invalid enumeration value


   * What outcome did you expect instead?

Playing the video ...

Regards


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

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

Versions of packages totem depends on:
ii  grilo-plugins-0.3   0.3.2-1
ii  gsettings-desktop-schemas   3.20.0-3
ii  gstreamer1.0-clutter-3.03.0.18-1
ii  gstreamer1.0-plugins-bad1:1.8.2-dmo1
ii  gstreamer1.0-plugins-base   1.8.2-1
ii  gstreamer1.0-plugins-good   1.8.2-1
ii  gstreamer1.0-x  1.8.2-1
ii  libc6   2.22-11
ii  libcairo2   1.14.6-1+b1
ii  libgdk-pixbuf2.0-0  2.34.0-1
ii  libglib2.0-02.48.1-1
ii  libgstreamer-plugins-base1.0-0  1.8.2-1
ii  libgstreamer1.0-0   1.8.2-1
ii  libgtk-3-0  3.20.6-2
ii  libnautilus-extension1a 3.20.1-3
ii  libpango-1.0-0  1.40.1-1
ii  libpangocairo-1.0-0 1.40.1-1
ii  libtotem-plparser18 3.10.6-4
ii  libtotem0   3.20.1-3
ii  libx11-62:1.6.3-1
ii  totem-common3.20.1-3

Versions of packages totem recommends:
ii  gstreamer1.0-libav 1:1.8.2-dmo1
ii  gstreamer1.0-plugins-ugly  1.8.2-1
ii  gstreamer1.0-pulseaudio1.8.2-1
ii  totem-plugins  3.20.1-3

Versions of packages totem suggests:
pn  gnome-codec-install  

-- no debconf information

Bug#821409: Processed: severity of 821409 is important

[Adrian Bunk]

On Fri, Jul 01, 2016 at 10:15:05PM +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
> > severity 821409 important
> Bug #821409 [src:gtk+3.0] gtk+3.0: gtk3 apps seem to be graphically broken 
> since the most recent updates
> Bug #824891 [src:gtk+3.0] gtk+3.0: latest version breaks external themes
> Severity set to 'important' from 'serious'
> Severity set to 'important' from 'serious'
> > thanks
> Stopping processing here.
> 
> Please contact me if you need assistance.

Hi Michael,

did you accidentially also lower the severity of 824891?

At least one bug in src:gtk+3.0 really has to stay RC when an upgrade of 
this library causes widespread breakage at the level of "all toolbar 
icons in emacs disappeared" - I cannot imagine any scenario where
such a widespread breakage would not be considered a blocker for
a release, and having a "release critical" bug makes that visible.

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#829281: firefox-esr: full screen video breaks event processing

[Simon Richter]

Package: firefox-esr
Version: 45.2.0esr-1~deb8u1
Severity: important

Hi,

switching to full screen video completely breaks event processing for me.
Tested with MOZILLA_DISABLE_EXTENSIONS=1 and -safe-mode.

Video file showing the problem is at http://psi5.com/~geier/firefox.ogv

I go to youtube.com, select an arbitrary video. No flash is installed, the
HTML5 video player is used. I click on "full screen", the video keeps
playing in the small window as before, but video controls no longer
respond.

When I click on "New Tab", nothing happens initially. When I then click on
the hamburger menu, the "new tab" event is processed, and the menu then
opens. Switching to the first tab again requires me to open the menu
(alternatively, I can change to another window and back). Likewise, the
scroll bar and keyboard scrolling are only handled after either clicking
the menu or switching windows.

In addition, not all tabs are displayed in the tab bar, and video keeps
playing in a closed tab (sound can still be heard).

The window manager I use is ratpoison. The "iceweasel" package before the
last system update (38.8.0esr) worked.

   Simon

-- Package-specific info:

-- Extensions information
Name: Default theme
Location: 
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: Easy Screenshot
Location: ${PROFILE_EXTENSIONS}/jid0-snuiiiyrmnnmhuklu6vk8dqk...@jetpack.xpi
Status: enabled

Name: Firefox Hello Beta
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled

Name: HTTPS-Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywhere-...@eff.org
Status: enabled

Name: Kassi - Kodi/XBMC Remote Control
Location: ${PROFILE_EXTENSIONS}/jid1-xjowf7m9ffg...@jetpack.xpi
Status: user-disabled

Name: OverbiteFF
Location: ${PROFILE_EXTENSIONS}/overbit...@floodgap.com.xpi
Status: enabled

Name: Send to XBMC
Location: ${PROFILE_EXTENSIONS}/jid0-ycm0p5wlcgjvbjczhausq5h2...@jetpack.xpi
Status: user-disabled

Name: SoundCloud Downloader - SC DOWNLOADER
Location: ${PROFILE_EXTENSIONS}/jid1-mw7iua66ny8...@jetpack.xpi
Status: enabled

Name: Stylish
Location: ${PROFILE_EXTENSIONS}/{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}.xpi
Status: user-disabled

-- Plugins information

-- Addons package information
ii  firefox-esr45.2.0esr-1~ amd64Mozilla Firefox web browser - Ext

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.4+b1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u4
ii  libcairo2 1.14.0-2.1+deb8u1
ii  libdbus-1-3   1.8.20-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.1-2+b2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libglib2.0-0  2.42.1-1+b1
ii  libgtk2.0-0   2.24.25-3+deb8u1
ii  libhunspell-1.3-0 1.3.3-3
ii  libpango-1.0-01.36.8-3
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-10
ii  libx11-6  2:1.6.2-3
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  procps2:3.3.9-9
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages firefox-esr recommends:
ii  gstreamer1.0-libav 1.4.4-2
ii  gstreamer1.0-plugins-good  1.4.4-2

Versions of packages firefox-esr suggests:
ii  fonts-lmodern  2.004.4-5
ii  fonts-stix [otf-stix]  1.1.1-1
ii  libcanberra0   0.30-2.1
pn  libgnomeui-0   
ii  libgssapi-krb5-2   1.12.1+dfsg-19+deb8u2
pn  mozplugger 

-- no debconf information

Bug#829282: ITP: pathspider -- Internet path transparency measurement tool

[Iain R. Learmonth]

Package: wnpp
Severity: wishlist
Owner: "Iain R. Learmonth" 

* Package name: pathspider
  Version : 0.9.0
  Upstream Author : MAMI Project
* URL : https://pathspider.mami-project.eu/
* License : GPL-2+
  Programming Lang: Python
  Description : Internet path transparency measurement tool

PATHspider is a tool for performing experimental path transparency
measurements and is extensible using a plugin architecture. The
PATHspider distribution includes a set of plugins for measuring path
transparency to signalling used by explicit-congestion notification and
TCP Fast Open.



This package is to be maintained within the Internet Measurement
Packaging Team .

This packaging work is being performed as part of the European Union's
Horizon 2020 project MAMI. This project has received funding from the
European Union's Horizon 2020 research and innovation programme under
grant agreement No 688421. The opinions expressed and arguments employed
reflect only the authors' view. The European Commission is not
responsible for any use that may be made of that information.

-- 

Bug#829280: initramfs-tools: "cannot stat '/etc/modprobe.d/*'" warning from empty /etc/modprobe.d/

[Christoph Biedl]

Source: initramfs-tools
Version: Warning upon empty /etc/modprobe.d/
Severity: minor

Dear Maintainer,

when /etc/modprobe.d/ exists but is empty, update-initramfs issues
a warning:

| # update-initramfs  -k all -u
| update-initramfs: Generating /boot/initrd.img-4.6.0-1-amd64
| cp: cannot stat '/etc/modprobe.d/*': No such file or directory

Besides cosmetical issues I wonder what happens if there are files that
just are a reminder of dpkg conffile handling, like e.g.

/etc/modprobe.d/pptpd.conf.dpkg-remove

since appearently update-initramfs happily processes them. Which is
probably not the right thing to do.

Christoph

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

Kernel: Linux 4.4.13 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect



signature.asc
Description: Digital signature

Bug#829279: ITP: node-quickselect -- JavaScript selection algorithm

[Bas Couwenberg]

Package: wnpp
Severity: wishlist
Owner: Bas Couwenberg 

* Package name: node-quickselect
  Version : 1.0.0
  Upstream Author : Vladimir Agafonkin 
* URL : https://github.com/mourner/quickselect
* License : ISC
  Programming Lang: JavaScript
  Description : JavaScript selection algorithm

quickselect is a tiny and fast selection algorithm in JavaScript,
implementing Floyd-Rivest selection.


The package is required for node-rbush >= 2.0.0 and will be maintained
alongside node-rbush in the Debian GIS team.

Bug#829278: dh-systemd: "my" variable $service masks earlier declaration warning

[Christoph Biedl]

Package: dh-systemd
Version: 1.36
Severity: minor

Dear Maintainer,

building a package in sid, dh-system gave a warning:

| dh_systemd_enable --no-enable
| "my" variable $service masks earlier declaration in same scope at 
/usr/bin/dh_systemd_enable line 150.

Fix is pretty obvious.

Christoph


signature.asc
Description: Digital signature

Bug#829277: RM: golang-gopkg-dancannon-gorethink.v1 -- ROM; no longer needed

[Alexandre Viau]

Package: ftp.debian.org
Severity: normal

golang-gopkg-dancannon-gorethink.v1 is no longer needed by any package
and is superseded by golang-gopkg-dancannon-gorethink.v2, which will
eventually be packaged for telegraf.

Please remove it from the archive.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#823612: rescue-mode should mount /boot/efi if it's available

[Steve McIntyre]

On Fri, Jul 01, 2016 at 11:41:58PM +0200, Ben Hutchings wrote:
>On Fri, 2016-07-01 at 21:56 +0100, Steve McIntyre wrote:
>> On Tue, Jun 28, 2016 at 09:13:25PM +0200, Ben Hutchings wrote:
>> > 
>> > I wonder why we offer to mount /boot but not /usr (more and more
>> > programs live there), /var (some of them might need state there) or
>> > /tmp (don't want to create files there that will never be cleaned
>> > up).
>> 
>> Maybe, yes. For now I've made the code here much more generic to make
>> it easier to ask about other filesystems, and added a check for
>> /boot/efi too.
>> 
>> > Also, does the question about mounting /boot really merit critical
>> > priority?  Is 'yes' not a good default?
>> 
>> *If* the /boot fs is broken, attempting to auto-mount is probably not
>> a good plan.
>
>That's true.  Perhaps the sensible thing is perhaps to mount /usr and
>the virtual filesystems unconditionally, and then ask whether to mount
>all the other local filesystem ('mount -a -O no_network').

How are /usr and any other disk-based filesystems likely to be any
different to /boot here?

I'd agree about the virtual fsen...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< liw> everything I know about UK hotels I learned from "Fawlty Towers"

Bug#829276: mesa-demos: enable es2gears_wayland

[Héctor Orón Martínez]

Source: mesa-demos
Version: 8.3.0-1
Severity: wishlist
Tags: patch

Hello,

  Please I would love to see es2gears_wayland being shipped in Debian.
  Find patch attached.

Regards

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

Kernel: Linux 4.5.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u mesa-demos-8.3.0/debian/changelog mesa-demos-8.3.0/debian/changelog
--- mesa-demos-8.3.0/debian/changelog
+++ mesa-demos-8.3.0/debian/changelog
@@ -1,3 +1,11 @@
+mesa-demos (8.3.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: enable wayland in configure
+  * debian/mesa-utils-extra.install: install es2gears_wayland
+
+ -- Héctor Orón Martínez   Fri, 01 Jul 2016 22:36:38 +0200
+
 mesa-demos (8.3.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -u mesa-demos-8.3.0/debian/mesa-utils-extra.install mesa-demos-8.3.0/debian/mesa-utils-extra.install
--- mesa-demos-8.3.0/debian/mesa-utils-extra.install
+++ mesa-demos-8.3.0/debian/mesa-utils-extra.install
@@ -2,2 +2,3 @@
 usr/bin/es2gears_x11
+usr/bin/es2gears_wayland
 usr/bin/es2tri
diff -u mesa-demos-8.3.0/debian/rules mesa-demos-8.3.0/debian/rules
--- mesa-demos-8.3.0/debian/rules
+++ mesa-demos-8.3.0/debian/rules
@@ -3,7 +3,7 @@
 	dh $@ --with=quilt,autoreconf --parallel
 
 override_dh_auto_configure:
-	dh_auto_configure -- --disable-silent-rules
+	dh_auto_configure -- --disable-silent-rules --enable-wayland
 
 override_dh_auto_install:
 	dh_auto_install --destdir=debian/tmp

Bug#798774: pptpd: kernel NAT helper loader file added to the wrong directory

[Christoph Biedl]

Norman Rasmussen wrote...

> update-initramfs emits the following error several times:
> 
> libkmod: ERROR ../libkmod/libkmod-config.c:635 kmod_config_parse: 
> /etc/modprobe.d/pptpd.conf line 1: ignoring bad line starting with 
> 'nf_nat_pptp'
> 
> I think that bug #780181 should have added the file to
> modules-load.d not modprobe.d.
> 
> Also according to the man page for modules-load.d the file should be in
> /lib/modules-load.d (as /etc is reserved for the local administrator)

 and it didn't even load the module. Thanks for the catch.

Christoph


signature.asc
Description: Digital signature

Bug#828147: midori ruined

[積丹尼 Dan Jacobson]

SDJ> Thanks, Dan.  Can you also check the other bugs you've opened recently
SDJ> against the experimental package as well, please?

Actually I'll reopen this.
Its a big mystery why it only happens on my account.
It even happens when I do chmod 0 ~
and then HOME=...
So it must be something to do with icewm interaction.
All a mystery. As far as the other bugs... all I can
do is respond to each when you ask it.

Bug#823612: rescue-mode should mount /boot/efi if it's available

[Ben Hutchings]

On Fri, 2016-07-01 at 21:56 +0100, Steve McIntyre wrote:
> On Tue, Jun 28, 2016 at 09:13:25PM +0200, Ben Hutchings wrote:
> > 
> > I wonder why we offer to mount /boot but not /usr (more and more
> > programs live there), /var (some of them might need state there) or
> > /tmp (don't want to create files there that will never be cleaned
> > up).
> 
> Maybe, yes. For now I've made the code here much more generic to make
> it easier to ask about other filesystems, and added a check for
> /boot/efi too.
> 
> > Also, does the question about mounting /boot really merit critical
> > priority?  Is 'yes' not a good default?
> 
> *If* the /boot fs is broken, attempting to auto-mount is probably not
> a good plan.

That's true.  Perhaps the sensible thing is perhaps to mount /usr and
the virtual filesystems unconditionally, and then ask whether to mount
all the other local filesystem ('mount -a -O no_network').

Ben.

>  This is about the only sensible way to allow people to
> control that, I guess.
> 
-- 

Ben Hutchings
All extremists should be taken out and shot.


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

Bug#829274: search the web gone from right click menu

[積丹尼 Dan Jacobson]

Package: midori
Version: 0.5.12~wk2-exp1

Highlight some text and right click.
'Search the web' is no longer shown.

Bug#829273: about:version just eats CPU

[積丹尼 Dan Jacobson]

Package: midori
Version: 0.5.12~wk2-exp1

$ midori about:version
Just eats CPU.

Bug#821053: UEFI Secure Boot support in d-i build

[Ben Hutchings]

On Fri, 15 Apr 2016 01:04:15 +0100 Steve McIntyre 
wrote:
> Package: debian-installer
> Severity: important
> Control: block 820036 with -1
> 
> Check what changes will be needed in the d-i build scripts to support
> signed modules etc. for UEFI Secure Boot.

I think the answer is 'nothing at all', as udebs will be built with
signed binaries and their names won't change.  This is implemented in
linux-signed/experimental.

Ben.
 
-- 

Ben Hutchings
All extremists should be taken out and shot.


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

Bug#829265: ark: Fix RAR-related dependencies

[Alex Henry]

Thank you for the great package :) I extend my thoughts on the original bug
report towards the Debian KDE team as well! Happy to help!

On 1 July 2016 at 17:30, Scott Kitterman  wrote:

> On Friday, July 01, 2016 04:59:55 PM Alex Henry wrote:
> > Package: ark
> > Version: 4:16.04.2-1
> > Severity: normal
> >
> > Hi, I opened a bug on Ark's bug tracker today about not opening
> > RAR files and it is now clear that the dependencies for this
> > package are outdated. Please see the developer's reply on the bug
> > report for more information:
> >
> > https://bugs.kde.org/show_bug.cgi?id=364976
>
> Thanks for the great bug report.  The fix is committed to our packaging
> repository for the next upload.
>
> Scott K
>

Bug#829272: Missing accessors

[Mattias Ellert]

Package: openssl
Version: 1.1.0~pre5-4
Severity: important
Control: block 828316 by -1
Control: block 828318 by -1
Control: block 828595 by -1

Hi!

I got a lot of bugs filed about packages FTBFS with openssl 1.1.0.
I started to look at some of them, and many of them are due too
structures having been made opaque. In many cases accessors already
exists, but definitely not for all.

Here is a list of accessors I so far have identified as missing. The
filenames given in the "Add to ..." comments below are suggestions
based on where similar functions are defined and implemented.


/* Add to include/openssl/x509_vfy.h : */

typedef int (*X509_STORE_CTX_get_issuer)(X509 **issuer, X509_STORE_CTX *ctx, 
X509 *x);
typedef int (*X509_STORE_CTX_check_issued)(X509_STORE_CTX *ctx, X509 *x, X509 
*issuer);

void X509_STORE_CTX_set_get_issuer(X509_STORE_CTX *ctx,
   X509_STORE_CTX_get_issuer get_issuer);
X509_STORE_CTX_get_issuer X509_STORE_CTX_get_get_issuer(X509_STORE_CTX *ctx);
void X509_STORE_CTX_set_check_issued(X509_STORE_CTX *ctx,
 X509_STORE_CTX_check_issued check_issued);
X509_STORE_CTX_check_issued X509_STORE_CTX_get_check_issued(X509_STORE_CTX 
*ctx);


/* Add to crypto/x509/x509_vfy.c : */

void X509_STORE_CTX_set_get_issuer(X509_STORE_CTX *ctx,
   X509_STORE_CTX_get_issuer get_issuer)
{
ctx->get_issuer = get_issuer;
}

X509_STORE_CTX_get_issuer X509_STORE_CTX_get_get_issuer(X509_STORE_CTX *ctx)
{
return ctx->get_issuer;
}

void X509_STORE_CTX_set_check_issued(X509_STORE_CTX *ctx,
 X509_STORE_CTX_check_issued check_issued)
{
ctx->check_issued = check_issued;
}

X509_STORE_CTX_check_issued X509_STORE_CTX_get_check_issued(X509_STORE_CTX *ctx)
{
return ctx->check_issued;
}


/* Add to include/openssl/x509v3.h */

void X509_set_extension_flags(X509 *x, uint32_t ex_flags);
void X509_clear_extension_flags(X509 *x, uint32_t ex_flags);


/* Add to crypto/x509v3/v3_purp.c */

void X509_set_extension_flags(X509 *x, uint32_t ex_flags)
{
x->ex_flags |= ex_flags;
}

void X509_clear_extension_flags(X509 *x, uint32_t ex_flags)
{
x->ex_flags &= ~ex_flags;
}


Regarding the new locking. Do I understand it correctly that e.g.

  CRYPTO_w_lock(CRYPTO_LOCK_X509_STORE);

should be replaced by something like

  CRYPTO_THREAD_write_lock(X509_STORE_get_lock(ctx));

But then the accessors to get hold of the lock objects in the opaque
structs are missing. E.g.

/* Add to some header file */

CRYPTO_RWLOCK *X509_STORE_get_lock(X509_STORE *ctx);

/* Add to some implementation file */

/* Add to crypto/x509/x509_lu.c */

CRYPTO_RWLOCK *X509_STORE_get_lock(X509_STORE *v)
{
return v->lock;
}

Repeat for other relevant classes with locks.

Mattias


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

Bug#829271: Missing libqt4-svg depency

[Georg Baum]

Package: lyx

Version: 2.2.0-1


Hi,

LyX requires the qt SVG module to display toolbar icons correctly since 
version 2.2.0. Since qt loads this at runtime it is not picked up 
automatically when building the package. Please add a manual dependency 
on libqt4-svg.


Note: This was reported originally on the LyX users list: 
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg103465.html



Thanks,


Georg

Bug#823612: rescue-mode should mount /boot/efi if it's available

[Steve McIntyre]

On Tue, Jun 28, 2016 at 09:13:25PM +0200, Ben Hutchings wrote:
>
>I wonder why we offer to mount /boot but not /usr (more and more
>programs live there), /var (some of them might need state there) or
>/tmp (don't want to create files there that will never be cleaned up).

Maybe, yes. For now I've made the code here much more generic to make
it easier to ask about other filesystems, and added a check for
/boot/efi too.

>Also, does the question about mounting /boot really merit critical
>priority?  Is 'yes' not a good default?

*If* the /boot fs is broken, attempting to auto-mount is probably not
a good plan. This is about the only sensible way to allow people to
control that, I guess.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/

Bug#829269: ufw: fails with ERROR: initcaps, dmesg: ip6_tables: disagrees about version of symbol xt_compat_match_from_user in a fresh install

[PulM]

Source: ufw
Version: 0.33-2
Severity: grave
Tags: ipv6
Justification: renders package unusable

when enable ufw:
ERROR: initcaps
[Errno 2] modprobe: ERROR: could not insert 'ip6_tables': Unknown symbol in 
module, or unknown parameter (see dmesg)
ip6tables v1.4.21: can't initialize ip6tables table `filter': Table does not 
exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.

dmesg output:
ip6_tables: disagrees about version of symbol xt_compat_match_from_user
ip6_tables: Unknown symbol xt_compat_match_from_user (err -22)
ip6_tables: Unknown symbol xt_compat_check_entry_offsets (err 0)
ip6_tables: Unknown symbol xt_check_entry_offsets (err 0)
ip6_tables: Unknown symbol xt_copy_counters_from_user (err 0)
ip6_tables: disagrees about version of symbol xt_compat_match_from_user
ip6_tables: Unknown symbol xt_compat_match_from_user (err -22)
ip6_tables: Unknown symbol xt_compat_check_entry_offsets (err 0)
ip6_tables: Unknown symbol xt_check_entry_offsets (err 0)
ip6_tables: Unknown symbol xt_copy_counters_from_user (err 0)
ip6_tables: disagrees about version of symbol xt_compat_match_from_user
ip6_tables: Unknown symbol xt_compat_match_from_user (err -22)
ip6_tables: Unknown symbol xt_compat_check_entry_offsets (err 0)
ip6_tables: Unknown symbol xt_check_entry_offsets (err 0)
ip6_tables: Unknown symbol xt_copy_counters_from_user (err 0)

Solution that work for me:
I edited /etc/default/ufw and change the option IPV6=yes to IPV6=no.


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=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#829270: tomsfastmath: please make the build reproducible

[Reiner Herrmann]

Source: tomsfastmath
Version: 0.13-2
Severity: wishlist
Tags: patch upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that tomsfastmath could not be built reproducibly.
A list of object files is unsorted, which causes a non-deterministic
linking order.

The attached patch fixes this.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/reproducible-build.patch b/debian/patches/reproducible-build.patch
new file mode 100644
index 000..9537d06
--- /dev/null
+++ b/debian/patches/reproducible-build.patch
@@ -0,0 +1,14 @@
+Author: Reiner Herrmann 
+Description: Sort object files for deterministic linking order
+
+--- a/makefile.shared
 b/makefile.shared
+@@ -88,7 +88,7 @@
+ 	$(LTCOMPILE) $(CFLAGS) $(LDFLAGS) -o $@ -c $<
+ 
+ $(LIBNAME): $(OBJECTS)
+-	libtool --mode=link --tag=CC $(CC) $(CFLAGS) $(LDFLAGS) `find . -type f | grep "[.]lo" | xargs` -o $(LIBNAME) -rpath $(LIBPATH) -version-info $(VERSION) -export-symbols libtfm.symbols
++	libtool --mode=link --tag=CC $(CC) $(CFLAGS) $(LDFLAGS) `find . -type f | LC_ALL=C sort | grep "[.]lo" | xargs` -o $(LIBNAME) -rpath $(LIBPATH) -version-info $(VERSION) -export-symbols libtfm.symbols
+ 
+ install: $(LIBNAME)
+ 	install -d -g $(GROUP) -o $(USER) $(DESTDIR)$(LIBPATH)
diff --git a/debian/patches/series b/debian/patches/series
index bd25769..60e9c1d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 tfm-make-a-few-functions-static.patch
 tfm-remove--siltent-argument.patch
+reproducible-build.patch


signature.asc
Description: Digital signature

Bug#404082: Share data beween frontend and real package

[Paul Gevers]

Hmm

> Am 30. Juni 2016 16:39:23 MESZ, schrieb Paul Gevers :
>> So I think this bug can be closed as already supported. Would be great
>> if somebody could check this (maybe I need a example package in this
>> area).

Now I think again about this, the request was to share the
configuration, not the database. That would be something clearly
different (and not trivial).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#829268: lyx: toolbar icons do not show up with upgrade to lyx-2.2.0; needed qt-svc not installed

[David L. Johnson]

Package: lyx
Version: 2.2.0-1
Severity: important

Dear Maintainer,

I just upgraded my system (debian testing), and an upgrade of lyx to 2.2.0 was
part of the upgrade.  I am a constant lyx user, so this is vital to my work.
When I ran the new version, the toolbar icons did not show up, instead showing
text descriptions --- they didn't fit on the space available, and were a mess.
The terminal window where I had started lyx had all sorts of error messages
about not being able to load icons.  I googled to find a similar problem
someone had (on ubuntu), and saw that it required qt-svg packages.  I installed
the packages libqt5svg5 qtsvg5-dbg libqtscript4-svg --- I am not sure they were
all needed, particularly the middle one), and then the icons displayed
correctly.

It looks like the package dependencies aren't quite right for this version of
lyx.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
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 lyx depends on:
ii  libboost-signals1.58.0  1.58.0+dfsg-5.1
ii  libc6   2.22-11
ii  libenchant1c2a  1.6.0-11+b1
ii  libgcc1 1:6.1.1-7
ii  libmagic1   1:5.25-2
ii  libmythes-1.2-0 2:1.2.4-1
ii  libqtcore4  4:4.8.7+dfsg-8
ii  libqtgui4   4:4.8.7+dfsg-8
ii  libstdc++6  6.1.1-7
ii  lyx-common  2.2.0-1
ii  xdg-utils   1.1.1-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages lyx recommends:
ii  dvipng   1.14-2+b2
ii  evince [pdf-viewer]  3.20.1-1
ii  fonts-lyx2.2.0-1
ii  ghostscript  9.19~dfsg-1+b1
ii  gv [pdf-viewer]  1:3.7.4-1
ii  imagemagick  8:6.8.9.9-7.1
ii  poppler-utils0.44.0-3
ii  preview-latex-style  11.87-3+deb8u1
ii  psutils  1.17.dfsg-2
ii  tex4ht   20090611-3
ii  texlive-fonts-recommended2016.20160623-1
ii  texlive-generic-extra2016.20160623-1
ii  texlive-generic-recommended  2016.20160623-1
ii  texlive-latex-extra  2016.20160623-1
ii  texlive-latex-recommended2016.20160623-1
ii  texlive-science  2016.20160623-1

Versions of packages lyx suggests:
ii  chktex1.7.4-1+b1
pn  etoolbox  
pn  gnuhtml2latex 
pn  groff 
pn  latex2rtf 
pn  librsvg2-bin | inkscape   
pn  libtiff-tools 
pn  linuxdoc-tools
pn  lyx-dbg   
pn  noweb 
pn  rcs   
pn  sgmltools-lite
ii  texlive-latex-recommended [latex-xcolor]  2016.20160623-1
ii  texlive-xetex 2016.20160623-1
pn  writer2latex  
pn  wv

-- no debconf information

Bug#829210: RM: netenv -- RoQA; orphaned; does not work with default init

[Scott Kitterman]

On Friday, July 01, 2016 09:13:54 PM Christian Hofstaedtler wrote:
> I didn't even see this message in #796639, but I'm not the only one
> thinking that the value of this package right now is ...
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796639#12

OK.  What would one use instead?  As long as there's an alternative, then I 
agree removal makes sense.

Scott K

Bug#829265: ark: Fix RAR-related dependencies

[Scott Kitterman]

On Friday, July 01, 2016 04:59:55 PM Alex Henry wrote:
> Package: ark
> Version: 4:16.04.2-1
> Severity: normal
> 
> Hi, I opened a bug on Ark's bug tracker today about not opening
> RAR files and it is now clear that the dependencies for this
> package are outdated. Please see the developer's reply on the bug
> report for more information:
> 
> https://bugs.kde.org/show_bug.cgi?id=364976

Thanks for the great bug report.  The fix is committed to our packaging 
repository for the next upload.

Scott K

Bug#829267: xul-ext-adblock-plus: no ui in jessie firefox-esr

[Stefan Handschuh]

Package: xul-ext-adblock-plus
Version: 2.6.6+dfsg-1

With the introduction of firefox-esr in debian jessie, the
adblock-plus plugin provided in the debian repositories seems to have
lost its user interface.
The plugin itself however seems to be working properly. The
firefox-menu entries are missing and I did not find a way to configure
the plugin using firefox-esr.

Version 2.7.3 appears to not have this issue.

Bug#821795: lttng-modules-dkms: module FTBFS in jessie against Linux 3.16: error: conflicting types for 'trace_mm_page_alloc_extfrag'

[Jon Bernard]

* Michael Jeanson  wrote:
> Hi,
> 
> Here is a debdiff against the current package fixing the build
> failure, I'll ask Jon to make a new upload.

Hey Michael,

I just attempted a build with your diff and I'm seeing the attached
errors.  It looks like the debian-specific ifdefs are not quite right,
does any of this look familiar?  I'll look at it closer over the holiday
if you don't get to it sooner.

Cheers,

-- 
Jon
DKMS make.log for lttng-modules-2.5.1 for kernel 3.16.0-4-amd64 (x86_64)
Fri Jul  1 20:22:45 GMT 2016
make: Entering directory '/usr/src/linux-headers-3.16.0-4-amd64'
Makefile:10: *** mixed implicit and normal rules: deprecated syntax
make[1]: Entering directory `/usr/src/linux-headers-3.16.0-4-amd64'
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lttng-ring-buffer-client-discard.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lttng-ring-buffer-client-overwrite.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lttng-ring-buffer-metadata-client.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lttng-ring-buffer-client-mmap-discard.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lttng-ring-buffer-client-mmap-overwrite.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lttng-ring-buffer-metadata-mmap-client.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-statedump-impl.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/wrapper/irqdesc.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/wrapper/fdtable.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-events.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-abi.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-probes.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-pid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-procname.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-prio.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-nice.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-vpid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-tid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-vtid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-ppid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-vppid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-calibrate.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-hostname.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/wrapper/random.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/probes/lttng.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-syscalls.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/probes/lttng-probe-user.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-context-perf-counters.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-tracepoint.o
  LD [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-tracer.o
  LD [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lttng-statedump.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lib/ringbuffer/ring_buffer_backend.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lib/ringbuffer/ring_buffer_frontend.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lib/ringbuffer/ring_buffer_iterator.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lib/ringbuffer/ring_buffer_vfs.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lib/ringbuffer/ring_buffer_splice.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lib/ringbuffer/ring_buffer_mmap.o
  CC [M]  
/var/lib/dkms/lttng-modules/2.5.1/build/lib/prio_heap/lttng_prio_heap.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lib/../wrapper/splice.o
  LD [M]  /var/lib/dkms/lttng-modules/2.5.1/build/lib/lttng-lib-ring-buffer.o
/var/lib/dkms/lttng-modules/2.5.1/build/probes/Makefile:30: File 
/usr/src/linux-headers-3.16.0-4-common/virt/kvm/iodev.h not found. Probe "kvm" 
x86-specific is disabled. Use full kernel source tree to enable it.
/var/lib/dkms/lttng-modules/2.5.1/build/probes/Makefile:142: Files 
/usr/src/linux-headers-3.16.0-4-common/fs/btrfs/*.h not found. Probe "btrfs" is 
disabled. Use full kernel source tree to enable it.
/var/lib/dkms/lttng-modules/2.5.1/build/probes/Makefile:158: Files 
/usr/src/linux-headers-3.16.0-4-common/fs/ext4/*.h not found. Probe "ext4" is 
disabled. Use full kernel source tree to enable it.
/var/lib/dkms/lttng-modules/2.5.1/build/probes/Makefile:214: 
CONFIG_KALLSYMS_ALL is disabled, therefore probe "writeback" is disabled. 
Rebuild your kernel with this configuration option enabled in order to trace 
this subsystem.
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/probes/lttng-probe-sched.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/probes/lttng-types.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/probes/lttng-probe-irq.o
  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/probes/lttng-probe-timer.o
  CC 

Bug#823049: patch works for me

[Tormod Volden]

tags 823049 pending
thanks

On Sat, Jun 11, 2016 at 5:10 AM, Adam Borowski wrote:
>> Can you (or anyone on Hurd) please verify that this patch fixes the
>> issue, and that the package now builds successfully?
>
> Just tried it: the package builds and appears to work.

Thanks a lot, Adam!

Tormod

Bug#828991: Turns out I do have an initrd that does not mount /usr => system unbootable

[Eric Valette]

So the fact that you have an initrd is not a sufficient warranty beacuse 
on some machine and setup it does not mount /usr...


-- eric

Bug#829266: libldm: Fix for uninitialized variable, seen when building with -O3

[Steve Langasek]

Package: libldm
Version: 0.2.3-4
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Hi Hilko,

libldm version 0.2.3-4 failed to build in Ubuntu on the ppc64el
architecture, with an uninitialized variable error:

 libtool: link: ( cd ".libs" && rm -f "libldm-1.0.la" && ln -s 
"../libldm-1.0.la" "libldm-1.0.la" )
 gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror 
-Wshadow -Wextra -Wno-unused-local-typedefs -Wno-unused-parameter 
-I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include 
-pthread -I/usr/include/json-glib-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -g -O3 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
ldmtool-ldmtool.o `test -f 'ldmtool.c' || echo './'`ldmtool.c
 ldmtool.c: In function ‘shell’:
 ldmtool.c:642:12: error: ‘result’ may be used uninitialized in this function 
[-Werror=maybe-uninitialized]
  if (result) json_builder_reset(jb);
 ^
 cc1: all warnings being treated as errors
 make[3]: *** [ldmtool-ldmtool.o] Error 1

(https://launchpadlibrarian.net/257939759/buildlog_ubuntu-yakkety-ppc64el.libldm_0.2.3-4_BUILDING.txt.gz)

The attached patch has been applied in Ubuntu to fix this build failure. 
Please consider applying it in Debian as well (and/or forwarding it
upstream); it doesn't directly impact Debian builds, but is still "correct"
and improves compatibility if anyone does want to build the Debian package
with -O3.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libldm-0.2.3/debian/patches/series libldm-0.2.3/debian/patches/series
--- libldm-0.2.3/debian/patches/series	2014-06-13 14:04:15.0 -0700
+++ libldm-0.2.3/debian/patches/series	2016-07-01 09:41:41.0 -0700
@@ -4,3 +4,4 @@
 0004-Don-t-call-g_type_init-when-compiling-with-newer-gli.patch
 0005-Cast-result-of-be64toh-to-uint64_t.patch
 0006-Avoid-shadowing-error-on-mips.patch
+uninitialized_variables.patch
diff -Nru libldm-0.2.3/debian/patches/uninitialized_variables.patch libldm-0.2.3/debian/patches/uninitialized_variables.patch
--- libldm-0.2.3/debian/patches/uninitialized_variables.patch	1969-12-31 16:00:00.0 -0800
+++ libldm-0.2.3/debian/patches/uninitialized_variables.patch	2016-07-01 09:52:09.0 -0700
@@ -0,0 +1,19 @@
+Author: Steve Langasek 
+Description: Fix build failure due to possible uninitialized variable
+ When building with -O3, as we do on ppc64el in Ubuntu, gcc is more
+ aggressive about detecting uninitialized variables.  Set a default value
+ for this (presumed) false-positive.
+
+Index: libldm-0.2.3/src/ldmtool.c
+===
+--- libldm-0.2.3.orig/src/ldmtool.c
 libldm-0.2.3/src/ldmtool.c
+@@ -624,7 +624,7 @@
+ history_len++;
+ free(line);
+ 
+-gboolean result;
++gboolean result = FALSE;
+ if (!do_command(ldm, argc, argv, , out, jg, jb)) {
+ if (g_strcmp0("quit", argv[0]) == 0 ||
+ g_strcmp0("exit", argv[0]) == 0)

Bug#829224: ruby-redis-actionpack: FTBFS: Could not find 'pkg-config' (~> 1.1.7) among 32 total gem(s) (Gem::LoadError)

[Antonio Terceiro]

Control: forcemerge 829175 829224
Control: forcemerge 829175 829225
Control: forcemerge 829175 829226
Control: forcemerge 829175 829227
Control: forcemerge 829175 829229
Control: forcemerge 829175 829234

All these issues have been fixed at their source which was
ruby-nokogiri. 1.6.8-1 missed a dependency and that was fixed in
1.6.8-2.


signature.asc
Description: PGP signature

Bug#829265: ark: Fix RAR-related dependencies

[Alex Henry]

Package: ark
Version: 4:16.04.2-1
Severity: normal

Hi, I opened a bug on Ark's bug tracker today about not opening
RAR files and it is now clear that the dependencies for this
package are outdated. Please see the developer's reply on the bug 
report for more information:

https://bugs.kde.org/show_bug.cgi?id=364976

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

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

Versions of packages ark depends on:
ii  libarchive13   3.1.2-11.1
ii  libc6  2.22-11
ii  libkf5archive5 5.23.0-1
ii  libkf5completion5  5.23.0-1
ii  libkf5configcore5  5.23.0-1
ii  libkf5configgui5   5.23.0-1
ii  libkf5configwidgets5   5.22.0-1
ii  libkf5coreaddons5  5.23.0-1
ii  libkf5crash5   5.23.0-1
ii  libkf5dbusaddons5  5.23.0-1
ii  libkf5i18n55.22.1-1
ii  libkf5iconthemes5  5.22.0-1
ii  libkf5jobwidgets5  5.23.0-1
ii  libkf5kiocore5 5.22.0-1
ii  libkf5kiofilewidgets5  5.22.0-1
ii  libkf5kiowidgets5  5.22.0-1
ii  libkf5parts5   5.22.0-1
ii  libkf5pty5 5.22.0-1
ii  libkf5service-bin  5.22.0-1
ii  libkf5service5 5.22.0-1
ii  libkf5widgetsaddons5   5.23.0-1
ii  libkf5xmlgui5  5.22.0-1
ii  libqt5core5a   5.6.1+dfsg-3
ii  libqt5dbus55.6.1+dfsg-3
ii  libqt5gui5 5.6.1+dfsg-3
ii  libqt5widgets5 5.6.1+dfsg-3
ii  libstdc++6 6.1.1-7

Versions of packages ark recommends:
ii  bzip2   1.0.6-8
ii  p7zip-full  15.14.1+dfsg-2
ii  unzip   6.0-20
ii  zip 3.0-11

Versions of packages ark suggests:
pn  rar 
ii  unrar-free  1:0.0.1+cvs20140707-1

-- no debconf information

Bug#811876: disulfinder: FTBFS with GCC 6: no matching function for call to

[Andreas Tille]

Hi Tanya,

On Fri, Jul 01, 2016 at 06:27:03PM +0300, merlettaia wrote:
> Thank you for notifying, I'll check.

Do you plan to do more significant work on the package?  I'm just
asking because I'd like to upload packages with RC bugs soon.  So
if you think you might need some more time (which is fine) I'm
tempted to upload the package as is and we might upload a package
with full test suite later giving you as much time as you might
need.

What do you think?

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#782157: rhn-client-tools: Certificate problems when registering

[Fabio Renault Monteiro]

Hello could post your workaround? It's been a year since you posted the bug 
here and there seems to be no interest in correcting.
--
Fabio Renault Monteiro | Analista de Tecnologia da Informação | GESUP
Instituto de Tecnologia de Informação e Comunicação do Estado do Espírito Santo 
- Prodest
fabio.monte...@prodest.es.gov.br | 
(27) 3636-7178


On Wed, 08 Apr 2015 17:55:53 +0100 =?utf-8?q?Mart=C3=ADn_Ferrari?= 
 wrote:
> Package: rhn-client-tools
> Version: 1.8.26-4
> Severity: important
>
> Hi,
>
> I want to report that the package does not really work out of the box, and I
> suspect that it does not work at all. There are two problems related to the CA
> certificate, the first one is that the default location for it does not match
> the installed path:
>
> Traceback (most recent call last):
>   File "/usr/sbin/rhnreg_ks", line 218, in 
> cli.run()
>   File "/usr/share/rhn/up2date_client/rhncli.py", line 96, in run
> sys.exit(self.main() or 0)
>   File "/usr/sbin/rhnreg_ks", line 90, in main
> rhnreg.getCaps()
>   File "/usr/share/rhn/up2date_client/rhnreg.py", line 237, in getCaps
> s = rhnserver.RhnServer()
>   File "/usr/share/rhn/up2date_client/rhnserver.py", line 165, in __init__
> self._server = rpcServer.getServer(serverOverride=serverOverride)
>   File "/usr/share/rhn/up2date_client/rpcServer.py", line 171, in getServer
> raise up2dateErrors.SSLCertificateFileNotFound(msg)
> :
>
> This is easy to solve, just changing a parameter in the config file:
>
> -sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
> +sslCACert=/usr/share/rhn/RHNS-CA-CERT
>
> But then, when that is fixed, I get this error:
>
> Traceback (most recent call last):
>   File "/usr/sbin/rhnreg_ks", line 218, in 
> cli.run()
>   File "/usr/share/rhn/up2date_client/rhncli.py", line 96, in run
> sys.exit(self.main() or 0)
>   File "/usr/sbin/rhnreg_ks", line 90, in main
> rhnreg.getCaps()
>   File "/usr/share/rhn/up2date_client/rhnreg.py", line 239, in getCaps
> s.capabilities.validate()
>   File "/usr/share/rhn/up2date_client/rhnserver.py", line 172, in 
> __get_capabilities
> self.registration.welcome_message()
>   File "/usr/share/rhn/up2date_client/rhnserver.py", line 63, in __call__
> return rpcServer.doCall(method, *args, **kwargs)
>   File "/usr/share/rhn/up2date_client/rpcServer.py", line 203, in doCall
> ret = method(*args, **kwargs)
>   File "/usr/lib/python2.7/xmlrpclib.py", line 1224, in __call__
> return self.__send(self.__name, args)
>   File "/usr/share/rhn/up2date_client/rpcServer.py", line 38, in _request1
> ret = self._request(methodname, params)
>   File "/usr/lib/python2.7/dist-packages/rhn/rpclib.py", line 381, in _request
> self._handler, request, verbose=self._verbose)
>   File "/usr/lib/python2.7/dist-packages/rhn/transports.py", line 167, in 
> request
> headers, fd = req.send_http(host, handler)
>   File "/usr/lib/python2.7/dist-packages/rhn/transports.py", line 698, in 
> send_http
> self._connection.connect()
>   File "/usr/lib/python2.7/dist-packages/rhn/connections.py", line 183, in 
> connect
> self.sock.init_ssl()



--

Antes de imprimir pense em seu compromisso com o meio ambiente.
As informações existentes nesta mensagem e em seus arquivos anexados são para 
uso restrito, sendo seu sigilo protegido por lei. Caso você não seja o 
destinatário, saiba que leitura, divulgação ou cópia são proibidas. Neste caso, 
favor notificar o remetente e apagar as informações. O uso impróprio destas 
informações será tratado conforme as normas da empresa e a legislação em vigor.

Bug#829264: php-horde-activesync: update for MySQL 5.7 compatibility by setting root password

[Nishanth Aravamudan]

Package: php-horde-activesync
Version: 2.34.0-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

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

  * Update test compatibility with MySQL 5.7 (LP: #1568015).

Thanks for considering the patch.

*** /tmp/tmpvIXQYx/php-horde-activesync_2.34.0-1ubuntu1.debdiff
diff -Nru php-horde-activesync-2.34.0/debian/tests/control 
php-horde-activesync-2.34.0/debian/tests/control
--- php-horde-activesync-2.34.0/debian/tests/control2016-06-08 
12:00:51.0 -0700
+++ php-horde-activesync-2.34.0/debian/tests/control2016-07-01 
12:28:02.0 -0700
@@ -1,3 +1,3 @@
 Tests: phpunit
-Restrictions: needs-recommends isolation-container
+Restrictions: needs-recommends needs-root isolation-container
 Depends: @, php-cli, php-horde-test, php-sqlite3, mysql-server, php-mysql
diff -Nru php-horde-activesync-2.34.0/debian/tests/phpunit 
php-horde-activesync-2.34.0/debian/tests/phpunit
--- php-horde-activesync-2.34.0/debian/tests/phpunit2016-06-08 
12:00:51.0 -0700
+++ php-horde-activesync-2.34.0/debian/tests/phpunit2016-07-01 
12:04:20.0 -0700
@@ -2,11 +2,11 @@
 
 set -e
 
-export 
ACTIVESYNC_SQL_MYSQL_TEST_CONFIG='{"activesync":{"sql":{"mysql":{"adapter":"mysql","host":"localhost","username":"root","password":"","dbname":"test","charset":"utf-8"'
-export 
ACTIVESYNC_SQL_MYSQLI_TEST_CONFIG='{"activesync":{"sql":{"mysqli":{"adapter":"mysqli","host":"localhost","username":"root","password":"","dbname":"test","charset":"utf-8"'
-export 
ACTIVESYNC_SQL_PDO_MYSQL_TEST_CONFIG='{"activesync":{"sql":{"pdo_mysql":{"adapter":"pdo_mysql","host":"localhost","username":"root","password":"","dbname":"test","charset":"utf-8"'
+export 
ACTIVESYNC_SQL_MYSQL_TEST_CONFIG='{"activesync":{"sql":{"mysql":{"adapter":"mysql","host":"localhost","username":"root","password":"r00t","dbname":"test","charset":"utf-8"'
+export 
ACTIVESYNC_SQL_MYSQLI_TEST_CONFIG='{"activesync":{"sql":{"mysqli":{"adapter":"mysqli","host":"localhost","username":"root","password":"r00t","dbname":"test","charset":"utf-8"'
+export 
ACTIVESYNC_SQL_PDO_MYSQL_TEST_CONFIG='{"activesync":{"sql":{"pdo_mysql":{"adapter":"pdo_mysql","host":"localhost","username":"root","password":"r00t","dbname":"test","charset":"utf-8"'
 
-mysql -e 'create database IF NOT EXISTS test;' -uroot
+mysql -e "create database IF NOT EXISTS test; ALTER USER 'root'@'localhost' 
IDENTIFIED WITH 'mysql_native_password' BY 'r00t';" -uroot
 
 cd Horde_ActiveSync*/test/./Horde/ActiveSync
 phpunit -v .


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

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

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd

Bug#829263: libmemcached-libmemcached-perl: please make the build reproducible

[Chris Lamb]

Source: libmemcached-libmemcached-perl
Version: 1.001801+dfsg-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

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

Thanks to s...@debian.org for assistance. (We are by the bar in UCT, with 
approximately 10 minutes until our drinks run out..)

Patch attached.

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


Regards,

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


libmemcached-libmemcached-perl.diff.txt
Description: Binary data

Bug#825359: Aw: Re: Re: sbuild: unrealistic figure about total space used

[Helge Deller]

Hi Johannes,

On 01.07.2016 17:06, Johannes Schauer wrote:
> I refactored the whole function calculating the space and things should be
> easier to understand now.
> 
> If you want, you can try if sbuild from git still fixes your problem.

Confirmed.
I tested the sbuild from your git tree and it reports the used size correctly.

Thanks!
Helge

Bug#829262: slashem: please make the build reproducible

[Reiner Herrmann]

Source: slashem
Version: 0.0.7E7F3-7
Severity: wishlist
Tags: patch upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps fileordering
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that slashem could not be built reproducibly.
It embeds the current build time into the binary.

The attached patch, which is based on a similar patch for src:nethack
3.6.0-2, fixes those issues.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/reproducible-build.patch b/debian/patches/reproducible-build.patch
new file mode 100644
index 000..9e14bfb
--- /dev/null
+++ b/debian/patches/reproducible-build.patch
@@ -0,0 +1,58 @@
+Author: Reiner Herrmann 
+Description: Enable reproducible builds
+ - Use C locale for sorting files while creating archive with dlb
+ - Honour SOURCE_DATE_EPOCH for embedded timestamp
+Origin: based on patch in src:nethack 3.6.0-2
+
+--- a/sys/unix/Makefile.top
 b/sys/unix/Makefile.top
+@@ -273,8 +273,8 @@
+ 
+ dlb:
+ 	( cd util ; $(MAKE) dlb )
+-	( cd dat ; ../util/dlb cf nhshare $(SHARE_DATDLB) )
+-	( cd dat ; ../util/dlb cf nhushare $(UNSHARE_DATDLB) )
++	( cd dat ; LC_ALL=C ../util/dlb cf nhshare $(SHARE_DATDLB) )
++	( cd dat ; LC_ALL=C ../util/dlb cf nhushare $(UNSHARE_DATDLB) )
+ 
+ # recover can be used when INSURANCE is defined in include/config.h
+ # and the checkpoint option is true
+--- a/util/makedefs.c
 b/util/makedefs.c
+@@ -598,7 +598,7 @@
+ do_date()
+ {
+ 	long clocktim = 0;
+-	char *c,  *cbuf, buf[BUFSZ];
++	char *c,  *cbuf, buf[BUFSZ], *source_date_epoch;
+ 	const char *ul_sfx;
+ 
+ 	cbuf = malloc(600);
+@@ -614,13 +614,12 @@
+ 	Fprintf(ofp,"/*\tSCCS Id: @(#)date.h\t3.4\t2002/02/03 */\n\n");
+ 	Fprintf(ofp,Dont_Edit_Code);
+ 
+-#ifdef KR1ED
+ 	(void) time();
+-	Strcpy(cbuf, ctime());
+-#else
+-	(void) time((time_t *));
+-	Strcpy(cbuf, ctime((time_t *)));
+-#endif
++	source_date_epoch = getenv("SOURCE_DATE_EPOCH");
++	if (source_date_epoch)
++		clocktim = strtoull(source_date_epoch, NULL, 10);
++	Strcpy(cbuf, asctime(gmtime()));
++
+ 	for (c = cbuf; *c; c++) if (*c == '\n') break;
+ 	*c = '\0';	/* strip off the '\n' */
+ #ifdef NHSTDC
+@@ -649,7 +648,7 @@
+ 		version_id_string(buf, cbuf));
+ #ifdef AMIGA
+ 	{
+-	struct tm *tm = localtime((time_t *) );
++	struct tm *tm = gmtime((time_t *) );
+ 	Fprintf(ofp,"#define AMIGA_VERSION_STRING ");
+ 	Fprintf(ofp,"\"\\0$VER: NetHack %d.%d.%d (%d.%d.%d)\"\n",
+ 		VERSION_MAJOR, VERSION_MINOR, PATCHLEVEL,
diff --git a/debian/patches/series b/debian/patches/series
index ba76b8a..ff7bd88 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@ fix-libpng15-ftbfs.patch
 spelling-error.patch
 slashem-debian.patch
 clang_FTBFS_Wreturn-type.patch
+reproducible-build.patch


signature.asc
Description: Digital signature

Bug#829210: RM: netenv -- RoQA; orphaned; does not work with default init

[Christian Hofstaedtler]

I didn't even see this message in #796639, but I'm not the only one
thinking that the value of this package right now is ...

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796639#12


-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#829261: passwordsafe: please make the build reproducible

[Reiner Herrmann]

Source: passwordsafe
Version: 0.98.1+dfsg-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: locale timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that passwordsafe could not be built reproducibly.
It embeds information from the build process into extra fields of help
zip files and writes C++ files in a locale-dependent way.

The attached patch fixes that by preventing extra fields be stored in
zip files and by using the default Perl-behavior for sorting keys.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/reproducible-build.patch b/debian/patches/reproducible-build.patch
new file mode 100644
index 000..d475f68
--- /dev/null
+++ b/debian/patches/reproducible-build.patch
@@ -0,0 +1,32 @@
+Author: Reiner Herrmann 
+Description: Make the build reproducible
+ - strip extra fields from zip file containg help files
+ - don't honour locale in rc2cpp.pl, or else keys written
+   into generated cpp source file will be sorted differently
+   under different locales.
+
+--- a/Misc/rc2cpp.pl
 b/Misc/rc2cpp.pl
+@@ -18,7 +18,6 @@
+ 
+ use strict;
+ use warnings;
+-use locale;
+ use File::Basename;
+ 
+ sub usage {
+--- a/help/Makefile.linux
 b/help/Makefile.linux
+@@ -6,10 +6,10 @@
+ all: default $(LANGS)
+ 
+ default:
+-	@cd default ; $(ZIP) -qr ../helpEN ./*
++	@cd default ; $(ZIP) -Xqr ../helpEN ./*
+ 
+ $(LANGS):
+-	@cd $(BASEDIRNAME)$@ ; $(ZIP) -qr ../help$@ ./*
++	@cd $(BASEDIRNAME)$@ ; $(ZIP) -Xqr ../help$@ ./*
+ 
+ clean:
+ 	$(RM) *.zip
diff --git a/debian/patches/series b/debian/patches/series
index 9e5563a..c8fc7a6 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@ edit_paths
 version_fix
 gmtime_fix
 fix_link
+reproducible-build.patch


signature.asc
Description: Digital signature

Bug#774012: Still is not fixed for jessie (Re: systemd: Program terminated with signal SIGFPE, Arithmetic exception)

[Michael Biebl]

On Sat, 16 Jan 2016 14:48:45 +0300 "Yuriy M. Kaminskiy"
 wrote:
> On 28.12.2015 16:15, Michael Biebl wrote:
> > Am 28.12.2015 um 13:33 schrieb Yuriy M. Kaminskiy:
> >> This bug is still present in jessie's systemd 215-17+deb8u1 (backtrace
> >> is same).
> > If someone, who is able to reproduce the issue, is willing to backport
> > the necessary changes to v215, I'd be willing to merge this patch for
> > stable, assuming the change is not too invasive.
> >
> This issue was claimed to be "probably fixed" by commit 
> 9c3349e23b14db27e7ba45f82cf647899c563ea9.
> I've cherry-picked that commit to v215, fixed conflicts, stripped out 
> cosmetic changes (and removed one chunk that was later reverted 
> upstream), see attached.
> Unfortunately, I have no idea how to reliable reproduce this issue (and 
> have no spare machine for tests), so it is completely untested.
> Given it is not clear if this issue is completely fixed, I'd rather 
> replace "assert()" with "return"; maybe, n_running_jobs==0 will break 
> something somewhere else, but at least it should not outright kill 
> systemd process with SIGFPE (or assert), see second patch.

Paul, Yuriy, could you apply this patch and run it for a while to see
whether the issue pops up again.
Please report back with your findings.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#829236: [Pkg-julia-devel] Bug#829236: utf8proc: FTBFS: line 16413: normalization failed for ? -> 配

[Peter Colberg]

On Fri, Jul 01, 2016 at 04:40:52PM +0200, Chris Lamb wrote:
>   test/normtest data/NormalizationTest.txt
>   line 16413: normalization failed for  -> 配

The test fails due to unicode-data having been updated to Unicode 9.0.

This has been resolved upstream but not released yet.

Peter

Bug#820991: gitlab: Fails to install with Failed to start gitlab.target: Unit gitlab.target is masked.

[Philip]

You can unmask gitlab.target with 

# systemctl unmask gitlab.target

As next umask gitlab-mailroom.service, gitlab-sidekiq.service, 
gitlab-workhorse.service

And gitlab can finish the installation.

Good luck

Bug#829260: FTCBFS for alpha

[James Clarke]

Package: src:guile-2.0
Version: 2.0.11
Severity: wishlist
Tags: patch
X-Debbugs-CC: h.gro...@intenta.de

Hi,
While rebootstrapping alpha, guile-2.0 FTCBFS as
module/system/base/target.scm does not have support for alpha (see log
below). I have attached a patch which I believe should work based on
what is needed for other architectures, but I have no easy way of
testing it short of performing a rebootstrap myself. Please consider
including it; if you don't want to include it because it hasn't been
tested, I believe Helmut intends to add it to rebootstrap next week and
see if it works.

Regards,
James

Rebootstrap log (taken from 
https://jenkins.debian.net/view/rebootstrap/job/rebootstrap_alpha_gcc5/101/console):
> ...
> Making all in module
> make[3]: Entering directory '/tmp/buildd/guile-2.0/guile-2.0-2.0.11+1/module'
> GUILE_INSTALL_LOCALE=1 GUILE_AUTO_COMPILE=0 \
> ../meta/uninstalled-env   \
> guild compile --target="alpha-unknown-linux-gnu" -Wunbound-variable 
> -Warity-mismatch -Wformat \
>   -L "/tmp/buildd/guile-2.0/guile-2.0-2.0.11+1/module" -L 
> "/tmp/buildd/guile-2.0/guile-2.0-2.0.11+1/module"   \
>   -L "/tmp/buildd/guile-2.0/guile-2.0-2.0.11+1/guile-readline"
> \
>   -o "ice-9/eval.go" "ice-9/eval.scm"
> ;;; note: source file /usr/share/guile/2.0/system/base/target.scm
> ;;;   newer than compiled 
> /usr/lib/x86_64-linux-gnu/guile/2.0/ccache/system/base/target.go
> Backtrace:
> In ice-9/boot-9.scm:
>  157: 9 [catch #t # ...]
> In unknown file:
>?: 8 [apply-smob/1 #]
> In ice-9/boot-9.scm:
>   63: 7 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
>  432: 6 [eval # #]
>  387: 5 [eval # #]
> In srfi/srfi-1.scm:
>  619: 4 [for-each # #]
> In scripts/compile.scm:
>  182: 3 [# 
> "ice-9/eval.scm"]
> In ice-9/eval.scm:
>  475: 2 [eval # #]
> In ice-9/boot-9.scm:
>  700: 1 [map # (# # #)]
> In unknown file:
>?: 0 [scm-error misc-error #f "~A ~S" ("unknown CPU endianness" "alpha") 
> #f]
>
> ERROR: In procedure scm-error:
> ERROR: unknown CPU endianness "alpha"
> Makefile:2179: recipe for target 'ice-9/eval.go' failed
> make[3]: Leaving directory '/tmp/buildd/guile-2.0/guile-2.0-2.0.11+1/module'
> make[3]: *** [ice-9/eval.go] Error 1
> Makefile:1830: recipe for target 'all-recursive' failed
> make[2]: Leaving directory '/tmp/buildd/guile-2.0/guile-2.0-2.0.11+1'
> make[2]: *** [all-recursive] Error 1
> Makefile:1716: recipe for target 'all' failed
> make[1]: Leaving directory '/tmp/buildd/guile-2.0/guile-2.0-2.0.11+1'
> make[1]: *** [all] Error 2
> dh_auto_build: make -j1 returned exit code 2
> debian/rules:78: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 2
> dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
> rebootstrap-error: dpkg-buildpackage failed with status 2
> ...
--- a/module/system/base/target.scm
+++ b/module/system/base/target.scm
@@ -65,7 +65,7 @@
   (cond ((string-match "^i[0-9]86$" cpu)
  (endianness little))
 ((member cpu '("x86_64" "ia64"
-   "powerpcle" "powerpc64le" "mipsel" "mips64el" 
"sh4"))
+   "powerpcle" "powerpc64le" "mipsel" "mips64el" "sh4" 
"alpha"))
  (endianness little))
 ((member cpu '("sparc" "sparc64" "powerpc" "powerpc64" "spu"
"mips" "mips64" "m68k" "s390x"))
@@ -105,7 +105,7 @@
   ((string-match "64$" cpu) 8)
   ((string-match "64_?[lbe][lbe]$" cpu) 8)
   ((member cpu '("sparc" "powerpc" "mips" "mipsel" "m68k" "sh4")) 4)
-  ((member cpu '("s390x")) 8)
+  ((member cpu '("s390x" "alpha")) 8)
   ((string-match "^arm.*" cpu) 4)
   (else (error "unknown CPU word size" cpu)
 


signature.asc
Description: PGP signature

Bug#829259: x11-xserver-utils: xrandr causes short screen pause

[Herbert Miller]

Package: x11-xserver-utils
Version: 7.7+7
Severity: minor

Dear Maintainer,

While observing HTML5 video playback in the Chromium web browser (tested 
against version 34 and 51), I noticed the xrandr command causes playback 
to hitch for a few frames (verified using the fps counter overlay in 
Chromium). I am running the command:


xrandr -d :0 -q

The particular devices we're seeing this on are an Intel NUC6i5SYH and a 
Dell Optiplex 3020. lspci shows:


NUC -
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated 
Graphics (rev 07)

Optiplex -
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller (rev 06)


The reasons we're bringing this to you is because I'm aware there have 
been issues with the Skylake chipset and we do not notice the issue on 
older hardware, such as an HP MP9 on which lspci shows:


00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller (rev 06)


What's odd is it only happens if a minute or so passes between calls. If 
I make consecutive calls frequently, it doesn't cause the pause.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
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 x11-xserver-utils depends on:
ii  cpp  4:4.9.2-4
ii  libc62.22-11
ii  libice6  2:1.0.9-1+b1
ii  libx11-6 2:1.6.3-1
ii  libxaw7  2:1.0.13-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxext6 2:1.3.3-1
ii  libxi6   2:1.7.6-1
ii  libxmu6  2:1.1.2-2
ii  libxmuu1 2:1.1.2-2
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxt6   1:1.1.5-1
ii  libxxf86vm1  1:1.1.4-1

x11-xserver-utils recommends no packages.

Versions of packages x11-xserver-utils suggests:
pn  cairo-5c
pn  nickle  
ii  xorg-docs-core  1:1.7.1-1

-- no debconf information


Herbert Miller Jr. :: Software Engineer/Developer
Phone: 877-344-8450 ext 158
Direct: 412-246-8970
E-mail: herbert.mil...@industryweapon.com
Digital Signage Made Simple

Bug#829246: [pkg-gnupg-maint] Bug#829246: gnupg2: fails to find signing subkey

[David Bremner]

Daniel Kahn Gillmor  writes:

> the text of your report says "default-user" (which doesn't exist in gpg)
> and the transcript says "local-user".  But i think there is also
> "default-key" -- hvae you tried with both default-key and local-user ?

Sorry that should have read default-key. And yes, I've tried both, it
doesn't seem to make a difference. The master key fails for both, and
the subkeyid works for both.

d


signature.asc
Description: PGP signature

Bug#828147: midori ruined

[Sergio Durigan Junior]

On Friday, July 01 2016, 積丹尼 Dan Jacobson wrote:

> SDJ> I've just uploaded midori_0.5.12~wk2 into experimental.
>
> OK this seems much better. Closing.

Thanks, Dan.  Can you also check the other bugs you've opened recently
against the experimental package as well, please?

Cheers,

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


signature.asc
Description: PGP signature

Bug#829258: stegosuite: Wrong section, should be in e.g. graphics, but not in java

[Axel Beckert]

Package: stegosuite
Severity: normal
Version: 0.7.3-1

Dear Maintainer,

stegosuite seems to be in the wrong package section: According to the
package description it has nothing to do with Java except that it's
written in it. But that's not what "Section: java" is meant for.

So please move the package to a different section. I suggest "graphics".

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

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

Bug#789381: libpoe-api-peek-perl: FTBFS with perl 5.22: test failures

[gregor herrmann]

On Fri, 01 Jul 2016 11:59:57 -0400, Prof. Ernesto Hernández-Novich wrote:

> They were not aware of the issue because they haven't tested WebGUI
> with 5.22. They will be reviewing the actual dependency to see if it is
> indeed needed or not. Perhaps we coud wait a week or so before removing
> the packages.

Sounds good to me, thanks for checking with them!

Maybe they also want to test their software with perl 5.24 which was
released almost 2 months ago :)


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
   `-   


signature.asc
Description: Digital Signature

Bug#822613: RFS: dynamic-graph/3.0.0-1

[Rohan Budhiraja]

Hi Gianfranco

Thanks for the mail ( and sorry for not replying sooner).

--I have fixed the pedantic issues

-- I have not yet found a clear solution to the embedded jquery issue. I 
found information on 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736360 which seems to 
suggest the problem was still contentious two years ago. Should I keep 
overriding this warning?


Regards,
Rohan

On 05/10/2016 09:56 PM, Gianfranco Costamagna wrote:

control: owner -1 !

Hi, please fix the Pedantic lintian issues
https://mentors.debian.net/package/dynamic-graph
(e.g. no dep5 copyright, old compat level, typos, missing harderning flags)

and then I'll have a look at the package.




Il Lunedì 25 Aprile 2016 18:42, Rohan Budhiraja  ha 
scritto:
Package: sponsorship-requests
Severity: wishlist [important for RC bugs, wishlist for new packages]

Dear mentors,

I am looking for a sponsor for my package "dynamic-graph"

   * Package name: dynamic-graph
 Version : 3.0.0-1
 Upstream Author : Thomas Moulard
  François Bleibel
  François Keith
Nicolas Mansard
   Olivier Stasse

   * URL : https://github.com/proyan/dynamic-graph
   * License : LGPL-3
 Section : libs

It builds those binary packages:

  libdynamic-graph-dev - Dynamic graph C++ library development package
   libdynamic-graph-doc - documentation for the dynamic graph C++ library
   libdynamic-graph3.0.0 - Dynamic graph C++ library

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

   http://stack-of-tasks.github.io/


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

  dget -x 
http://mentors.debian.net/debian/pool/main/d/dynamic-graph/dynamic-graph_3.0.0-1.dsc

Regards,
 Rohan Budhiraja

Bug#829245: /etc/os-release: Please specify VERSION_CODENAME

[Santiago Vila]

On Fri, 1 Jul 2016, Benjamin Drung wrote:

> > So why don't you just declare lsb-release required for that
> > particular feature to work?
> 
> It's not one particular feature. The salt minion has grains (variables)
> and oscodename is one grain that every minion has. So this value is
> wrong without lsb-release on all minion. Thus it's not just a broken
> feature, but broken for all.
> 
> I like to keep the list of dependencies small. So installing lsb-
> release is not my first choice.
> 
> > If you consider this a bug at all, your intended fix (rely on the
> > /etc/os-release file) would only half-fix it, because it would still
> > be wrong in testing and unstable.
> 
> I know, but we could use other fallbacks there.

Ok, but why reinvent the wheel? The maintainers of lsb-release already
took care of this, and lsb-release has an installed size of 62kB.

I can understand your desire to keep the dependency list "small", but
you should probably take in account the installed size as well.

BTW: I use salt myself, on systems running stable and testing, and the
package lsb-release is already installed as a dependency from
unattended-upgrades.

So at least in my case, I would not notice the difference at all.

The problem I see in your rationale (lsb-release is optional, while
base-files is essential) is precisely that it would make the codename
thing essential de-facto even if it's defined as optional in the specs.

When one needs a feature, the normal thing is to add a Depends on a
package providing the feature, not to ask for the feature to be in an
essential package.

Thanks.

Bug#829257: RFP: ndctl -- NVDIMM management utility

[Ben Hutchings]

Package: wnpp
Severity: wishlist

* Package name: ndctl
  Version : 53.1
  Upstream Author : Dan Williams 
* URL : https://github.com/pmem/ndctl
* License : LGPL 2.1
  Programming Lang: C
  Description : NVDIMM management utility

ndctl is a utility for managing the "libnvdimm" kernel subsystem.
This includes provisioning capacity (namespaces) and enumerating,
enabling and disabling the devices associated with an NVDIMM bus.

Bug#829254: asset:precompile error when updating diaspora to 0.5.9.1

[Pirate Praveen]

Full error message at 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829254

There was a similar error message with gitlab which was fixed by updating 
libjs-coffeescript. It could be an issue with sprockets as diaspora-installer 
works, which uses sprockets 2.12.4

I was able to reproduce the error in two systems. ruby-execjs, ruby-uglifier 
use same version as diaspora-installer. NodeJS is unlikely the cause.

Can anyone help?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#829245: /etc/os-release: Please specify VERSION_CODENAME

[Benjamin Drung]

Am Freitag, den 01.07.2016, 19:17 +0200 schrieb Santiago Vila:
> On Fri, 1 Jul 2016, Benjamin Drung wrote:
> 
> > Because lsb-release is not installed on all system, but base-files
> is.
> > My intention for getting VERSION_CODENAME defined for jessie is to
> > develop a proper fix for https://github.com/saltstack/salt/issues/3
> 4423
> 
> Let's see:
> 
>   On a Debian 8 (jessie) system where lsb-release is not installed,
> [...]
> 
> So why don't you just declare lsb-release required for that
> particular feature to work?

It's not one particular feature. The salt minion has grains (variables)
and oscodename is one grain that every minion has. So this value is
wrong without lsb-release on all minion. Thus it's not just a broken
feature, but broken for all.

I like to keep the list of dependencies small. So installing lsb-
release is not my first choice.

> If you consider this a bug at all, your intended fix (rely on the
> /etc/os-release file) would only half-fix it, because it would still
> be wrong in testing and unstable.

I know, but we could use other fallbacks there.

> BTW: In general, relying on the codename is a bad idea and it's
> something I would prefer not to encourage. We should rely on actual
> features being present or absent, not on the system being at a
> particular version.

I know. salt puts the codename in the oscodename pillar and user can
use it for whatever they want to. We use the oscodename pillar to
generate source.list entries.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL:  http://www.profitbricks.com

Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Andreas Gauger, Achim Weiss.

Bug#812041: thrift-compiler: diff for NMU version 0.9.1-2.1

[GCS]

Hi Tony,

On Fri, Jul 1, 2016 at 6:42 AM, tony mancill  wrote:
> I've prepared an NMU for thrift-compiler (versioned as 0.9.1-2.1) and
> uploaded it to DELAYED/10. Please feel free to tell me if I
> should delay it longer or if you would like me to dcut the upload.
 Sure, I should have fixed it before. Your update seems fine. I'm at
DebConf16 with a bad enough link; also I travel without my GnuPG key.
I can't do an update myself for the next ten days and even I don't
have any more fixes to add. Go ahead with your NMU as you wish.

> Also, I would be interested in collaborating on an update to a newer
> version of the thrift compiler.  Please let me know if you are amenable
> to that.
 Did you try the experimental package version from 'thrift' source? It
has a self-test issue on several architectures, but otherwise should
be fine and up-to-date.

Cheers,
Laszlo/GCS

Bug#829245: /etc/os-release: Please specify VERSION_CODENAME

[Santiago Vila]

On Fri, 1 Jul 2016, Benjamin Drung wrote:

> Because lsb-release is not installed on all system, but base-files is.
> My intention for getting VERSION_CODENAME defined for jessie is to
> develop a proper fix for https://github.com/saltstack/salt/issues/34423

Let's see:

  On a Debian 8 (jessie) system where lsb-release is not installed, [...]

So why don't you just declare lsb-release required for that
particular feature to work?

If you consider this a bug at all, your intended fix (rely on the
/etc/os-release file) would only half-fix it, because it would still
be wrong in testing and unstable.

OTOH, if you document that lsb_release is required for this feature to
work, then the bug will be fixed in stable, testing and unstable at
the same time, without corner cases.

BTW: In general, relying on the codename is a bad idea and it's
something I would prefer not to encourage. We should rely on actual
features being present or absent, not on the system being at a
particular version.

Thanks.

Bug#829256: RFS: caffe/1.0.0~rc3-2 [ITP]

[Lumin]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC:
​​
locutusofb...@debian.org

  Dear mentors,

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

 * Package name: caffe
   Version : 1.0.0~rc3-2
   Upstream Author :
​Berkeley Vision and Learning Center

 * URL :
​caffe.berkeleyvision.org

 * License :
​BSD

   Section : science

  It builds those binary packages:

caffe-cpu  - Fask, open framework for Deep Learning (meta)
​   ​
 caffe-doc  - Doxygen Document of Caffe
​   ​
 caffe-tools-cpu - Tools for fast, open framework for Deep Learning
(CPU_ONLY)
​   ​
 libcaffe-cpu-dev - development files for Caffe (CPU_ONLY)
​   ​
 libcaffe-cpu1 - library of Caffe, deep learning framework (CPU_ONLY)
​   ​
 python3-caffe-cpu - Python3 interface of Caffe (CPU_ONLY)

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

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


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

dget -x
https://mentors.debian.net/debian/pool/main/c/caffe/caffe_1.0.0~rc3-2.dsc


  Changes since the last upload:

​
caffe (1.0.0~rc3-2) experimental; urgency=low

  * d/control
- Rename binary package caffe-cpu to caffe-tools-cpu.
- Create metapackage "caffe-cpu".
- Update package descriptions.
- Add B-D: liboctave-dev, octave-pkg-dev.
- Bump python-caffe-cpu to python3-caffe-cpu.
- Suggest caffe-doc for libcaffe-cpu-dev.
  * d/rules
- Compile octave binary, however octave package is
  temporarily commented out bacause it's WIP.
- Include defs.make from package 'octave-pkg-dev' for Octave
  related variables.
- Bump from python2 build to python3 build.
- change the compiling target order of override_dh_auto_build-arch.
  * d/man
- Refresh manpage debian/man/caffe.1 , generated by txt2man with
  template file debian/man/caffe.txt
- Remove unnecessary man pages.
  * d/patch
- Update patches due to python2->python3 transition.
- Update forward status in patch headers.
- Add new patch cmake-octave-fix-library, which fixes python3
  library name for mkoctfile.
  * d/tests
- Add python3 interface B-D runtime-dependencies for testsuite.
- Add test suite: python3caffetestsuite .
- Update testsuite: simple .
  * Add install control files for octave-caffe-cpu.
  * Update debian/clean.
  * Update bash completion script for caffe.
  * Remove d/TODO.
  * Upload to experimental. The -1 version is an accident.

​

-- 
Best,
Lumin

Bug#825849: powerdns 100% CPU usage

[Martijn Bruinsma]

I have posted some more info on our setup at [1], hoping somebody will be able 
to reproduce it. If more info is needed, just let me know, no problem.

[1] https://github.com/PowerDNS/pdns/issues/3954

Thanks,
Martin

Bug#829245: /etc/os-release: Please specify VERSION_CODENAME

[Benjamin Drung]

Am Freitag, den 01.07.2016, 18:51 +0200 schrieb Santiago Vila:
> This field is defined as optional in the specification.

Because not every distribution has a codename and you might have
problems specifying it correctly (like on stretch/sid).

> Why do we need it in os-release when we can already use "lsb_release
> -c"
> to know the codename and it works in stable, testing and unstable?

Because lsb-release is not installed on all system, but base-files is.
My intention for getting VERSION_CODENAME defined for jessie is to
develop a proper fix for https://github.com/saltstack/salt/issues/34423

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL:  http://www.profitbricks.com

Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Andreas Gauger, Achim Weiss.

Bug#829245: /etc/os-release: Please specify VERSION_CODENAME

[Santiago Vila]

This field is defined as optional in the specification.

Why do we need it in os-release when we can already use "lsb_release -c"
to know the codename and it works in stable, testing and unstable?

Bug#824116: please reconsider enabling tests

[Daniel Stender]

Yes, sure that could be done. It's the other way around then, for quick builds,
DEB_BUILD_OPTIONS=nocheck could be exported. That what it's for, anyway.

I'm working on updating Theano and there are some problems towards build time
testing left which need some deeper investigation (Like "Unable to create
compiledir directory. Check the permissions). But it's coming up, soon.

Daniel

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

Bug#829246: [pkg-gnupg-maint] Bug#829246: gnupg2: fails to find signing subkey

[Daniel Kahn Gillmor]

Hi bremner--

Thanks for the report!

Just a clarification:

On Fri 2016-07-01 11:37:34 -0400, David Bremner wrote:
> I have a key with an offline master, and two signing subkeys.
> the first listed one is on v2 OpenGPG card. With gpg 1.4.20,
> I could specify the master keyid as e.g. the default-user, and
> gpg would find the key on the smartcard.
 [...]
> ╭─ maritornes:~ 
> ╰─% gpg --local-user 815B63982A79F8E7C72786C4762B57BB784206AD --sign test.tex
> File 'test.tex.gpg' exists. Overwrite? (y/N) y
> gpg: signing failed: No secret key
> gpg: signing failed: No secret key
>
> whereas specifying the subkeyid works
>
> % gpg --sign --local-user "F202971DA4A79E2C\!" test.tex

the text of your report says "default-user" (which doesn't exist in gpg)
and the transcript says "local-user".  But i think there is also
"default-key" -- hvae you tried with both default-key and local-user ?

All the best,

  --dkg

Bug#776999: efivar: broken 32-bit userland on 64-bit kernel

[D. Jared Dominguez]

Hi Adam,

Are you still seeing this bug in efivar 0.23-2?

--Jared


--
Jared Domínguez
OS Architect
Linux Engineering
Dell | Client Software Group

Bug#829245: /etc/os-release: Please specify VERSION_CODENAME

[Santiago Vila]

On Fri, 1 Jul 2016, Benjamin Drung wrote:

> PS: You might want to update VERSION_ID and VERSION to 8.5 in jessie
> too.

You might want to read archived base-files bugs where this issue was
already discussed. Short summary: This is how the release managers want it.

Thanks.

Bug#814914: NMU khronos-api: FTBFS due to missing build-dependencies

[Jens Reyer]

Hi Mike,

I'm currently at DebConf and got some sponsors around for fixing this
bug. Please find attached the debdiff. It will be uploaded in short time
nmu "delayed/10". Please let us know if we should delay it further.

Greets
jre
diff -Nru khronos-api-0~svn29735/debian/changelog 
khronos-api-0~svn29735/debian/changelog
--- khronos-api-0~svn29735/debian/changelog 2016-01-31 01:59:02.0 
+0100
+++ khronos-api-0~svn29735/debian/changelog 2016-07-01 18:05:56.0 
+0200
@@ -1,3 +1,11 @@
+khronos-api (0~svn29735-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload. "DebConf upload."
+  * Fix FTBFS. Add build-depends python-debian and python-dateutil
+(closes: #814914).
+
+ -- Jens Reyer   Fri, 01 Jul 2016 16:46:18 +0200
+
 khronos-api (0~svn29735-1) unstable; urgency=medium
 
   * Fix a lintian warning.
diff -Nru khronos-api-0~svn29735/debian/control 
khronos-api-0~svn29735/debian/control
--- khronos-api-0~svn29735/debian/control   2016-01-31 00:57:41.0 
+0100
+++ khronos-api-0~svn29735/debian/control   2016-07-01 18:20:09.0 
+0200
@@ -6,6 +6,8 @@
  debhelper (>= 9),
  doc-base,
  python-lxml,
+ python-debian,
+ python-dateutil,
  texlive-latex-extra,
  texlive-fonts-recommended,
  texlive-generic-recommended,

Bug#829245: /etc/os-release: Please specify VERSION_CODENAME

[Benjamin Drung]

Am Freitag, den 01.07.2016, 18:31 +0200 schrieb Santiago Vila:
> On Fri, 1 Jul 2016, Benjamin Drung wrote:
> 
> > Package: base-files
> > Version: 9.6
> > Severity: normal
> > 
> > Hi,
> > 
> > The os-release specification was updated in systemd > 230 to also
> > include a VERSION_CODENAME parameter:
> > https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434
> dd40d0dbdbac4d8
> > 
> > Please add VERSION_CODENAME to /etc/os-release, especially to the
> > stable release.
> 
> I'm not sure what do you mean by stable here. The current stable?
> The next stable? Whether this is suitable for jessie at this point
> would be for the release managers to decide, not me.

I mean jessie here.

> Also, I hope people will not really expect this variable to be
> "stretch" in stretch and "sid" in sid, because that's not possible
> given how migration from unstable to testing works.
> 
> What should we do if I put "stretch" and a user of sid says it's
> "wrong"?
> 
> Would you still consider the string useful in such case?

If VERSION_CODENAME is specified, it should be correct. So it should be
"stretch" on stretch and "sid" on sid, but I have no good idea how to
make it work for stretch/sid (due to the testing migrations).

So better not provide VERSION_CODENAME instead of a wrong one.

PS: You might want to update VERSION_ID and VERSION to 8.5 in jessie
too.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL:  http://www.profitbricks.com

Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Andreas Gauger, Achim Weiss.

Bug#829113: [Reproducible-builds] Bug#829113: Bug#829113: reprotest: Should unset $DISPLAY to avoid GUI popups from some build tools

[Mattia Rizzolo]

On Fri, Jul 01, 2016 at 06:00:24PM +0200, Jérémy Bobbio wrote:
> One take though, maybe reprotest should ensure that $HOME is set to an
> existing (temporary) directory; other building tools might get unhappy.

by some criteria I'm now too lazy to look up/remember, packages are not
supposed to require an existing writable directory (I assume that's
because don't really want a build process to temper your home¹), and to
impose that both sbuild and pbuilder sets HOME to a non-existing
directory.
Thus having packages FTBFSing with a non-existent HOME inside the
archive is highly improbable (probable set reduced to packages building
only arch-indep binaries that were always manually uploaded and not
built in sbuild (or recent pbuilder).

FTR, let me also remember you about debian policy §9.9 "A program must
not depend on environment variables to get reasonable defaults.".  Like
that, a out of context quote.


¹ I kinda agree though that building untrusted sources (or whatever,
  fwiw) in your home as your user, and expecting everything to go well
  it's naive.

-- 
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#810671: #810671: ifupdown-scripts-zg2: fails to install in chroot

[Christian Hofstaedtler]

ifupdown has stopped providing /etc/network/run in 2012. Apparently
on existing installs, the upgrade code did not work correctly so
most existing installs still have the compatibility symlink.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-