Bug#822232: closed by m...@debian.org (Matteo F. Vescovi) (Bug#822232: fixed in gtkpod 2.1.5-2)

[Matteo F. Vescovi]

Hi Adrian!

Il 23/apr/2016 00:21, "John Paul Adrian Glaubitz" <
glaub...@physik.fu-berlin.de> ha scritto:
>
> Hi Matteo!
>
> I think you took my advise too literally. I didn't mean you should
> just apply the diff as you did [1] but just use the information
> from the diff to update the symbols file.

Ahah! :-)
Sorry about that, had to make it quick because of work stuff so I didn't
check the info, actually.

Gonna fix it later today.

Cheers.

mfv

Bug#822294: [Pkg-utopia-maintainers] Bug#822294: network-manager: new upstream release (1.2.0)

[Paul Wise]

On Sat, 2016-04-23 at 07:01 +0200, Michael Biebl wrote:

> Sure, I'm very well aware of the new upstream release and you probably
> noticed that Debian already ships the last RC. The final 1.2.0 will
> follow shortly.

Great :)

> from version 2.4. The wpasupplicant version in Debian is unforunately too old

I was under the impression it needs 2.3 not 2.4:

https://blogs.gnome.org/lkundrak/2016/01/18/networkmanger-and-tracking-protection-in-wi-fi-networks/

> the reasons for not updating [1] seem odd. I have no idea
> why Stefan thinks this is somehow blocked by systemd(-networkd).
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806889

Hmm, ok.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#822294: [Pkg-utopia-maintainers] Bug#822294: network-manager: new upstream release (1.2.0)

[Michael Biebl]

Am 23.04.2016 um 05:40 schrieb Paul Wise:
> Package: network-manager
> Severity: wishlist
> 
> There is a new upstream release: 1.2.0
> 
> It has some privacy enhancing features that would be nice to have:
> 
> https://blogs.gnome.org/lkundrak/2016/04/20/networkmanager-1-2-is-here/

Sure, I'm very well aware of the new upstream release and you probably
noticed that Debian already ships the last RC. The final 1.2.0 will
follow shortly.

Bad news though regarding those privacy enhancing features: they require
newer versions of wpasupplicant, like e.g.


* add support for MAC address randomization in scans with nl80211

from version 2.4. The wpasupplicant version in Debian is unforunately
too old and the reasons for not updating [1] seem odd. I have no idea
why Stefan thinks this is somehow blocked by systemd(-networkd).

Regards,
Michael


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

-- 
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#822296: spyder and spyder3 man pages are content-free boilerplate

[Stuart Prescott]

Package: spyder
Version: 2.3.1+dfsg-1
Severity: minor

Dear Maintainer,

The spyder and spyder3 man pages are only boilerplate templates. They do not
contain any useful information beyond the one sentence summary in the NAME
section; the balance of the page is quite literally about 'foo' and 'bar',
left over from dh-make or some similar template.

cheers
Stuart



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

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

Versions of packages spyder depends on:
ii  python2.7.9-1
ii  python-spyderlib  2.3.1+dfsg-1
pn  python:any

spyder recommends no packages.

spyder suggests no packages.

Versions of packages python-spyderlib depends on:
ii  libjs-jquery   1.7.2+dfsg-3.2
ii  libjs-mathjax  2.4-2
ii  python-qt4 4.11.2+dfsg-1
pn  python:any 
ii  spyder-common  2.3.1+dfsg-1

Versions of packages python-spyderlib recommends:
ii  ipython-qtconsole 2.3.0-2
ii  pep8  1.5.7-2
ii  pyflakes  0.8.1-1
ii  pylint1.3.1-3
ii  python-jedi   0.8.1-1
ii  python-matplotlib 1.4.2-3.1
ii  python-numpy  1:1.8.2-2
ii  python-pandas 0.17.1-3~themill8+1
ii  python-psutil 2.1.1-1+b1
ii  python-rope   0.10.2-1
ii  python-scipy  0.14.0-2
ii  python-sphinx 1.2.3+dfsg-1
ii  python-spyderlib-doc  2.3.1+dfsg-1

Versions of packages python-spyderlib suggests:
ii  gitk1:2.1.4-2.1+deb8u2
pn  tortoisehg  

Versions of packages python-qt4 depends on:
ii  libc6  2.19-18+deb8u4
ii  libgcc11:4.9.2-10
ii  libpython2.7   2.7.9-2
ii  libqt4-dbus4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-declarative 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-designer4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-help4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-script  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-scripttools 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-test4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-xmlpatterns 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtassistantclient4  4.6.3-6
ii  libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui4  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtwebkit4   2.3.4.dfsg-3
ii  libstdc++6 4.9.2-10
ii  python 2.7.9-1
ii  python-sip [sip-api-11.1]  4.16.4+dfsg-1

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

-- no debconf information

Bug#800309: gkrellm-radio: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: gkrellm-radio
Version: 2.0.4-1.1
Followup-For: Bug #800309
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

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

  * debian/rules:
- Remove legacy DH_COMPAT export.
- Don't allow $(MAKE) clean to ignore errors.
- Replace dh_clean -k with dh_prep.
  * debian/compat: Specify compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-18-generic (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)
diff -u gkrellm-radio-2.0.4/debian/control gkrellm-radio-2.0.4/debian/control
--- gkrellm-radio-2.0.4/debian/control
+++ gkrellm-radio-2.0.4/debian/control
@@ -2,14 +2,14 @@
 Section: sound
 Priority: optional
 Maintainer: Sjoerd Simons 
-Build-Depends: debhelper (>> 3.0.0), liblircclient-dev, gkrellm (>= 2.0.0), libgtk2.0-dev
+Build-Depends: debhelper (>= 9), liblircclient-dev, gkrellm (>= 2.0.0), libgtk2.0-dev
 Standards-Version: 3.5.7
 
 Package: gkrellm-radio
 Architecture: any
 Replaces: gkrellm-radio2
 Conflicts: gkrellm-radio2
-Depends: gkrellm (>> 2.0.0), ${shlibs:Depends}
+Depends: ${misc:Depends}, gkrellm (>> 2.0.0), ${shlibs:Depends}
 Description: FM radio tuner for GKrellM 
  A gkrellm plugin to control radio tuners on linux. It allows you to define
  and jump between a number of radio stations.  With a mouse wheel you can dial
diff -u gkrellm-radio-2.0.4/debian/rules gkrellm-radio-2.0.4/debian/rules
--- gkrellm-radio-2.0.4/debian/rules
+++ gkrellm-radio-2.0.4/debian/rules
@@ -7,9 +7,6 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-# This is the debhelper compatability version to use.
-export DH_COMPAT=3
-
 configure: configure-stamp
 configure-stamp:
 	dh_testdir
@@ -31,14 +28,14 @@
 	rm -f build-stamp configure-stamp 
 
 	# Add here commands to clean up after the build process.
-	-enable_nls=1 WITH_LIRC=1 $(MAKE) clean
+	enable_nls=1 WITH_LIRC=1 $(MAKE) clean
  
 	dh_clean
 
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 
 	 enable_nls=1 WITH_LIRC=1 $(MAKE) install \
only in patch2:
unchanged:
--- gkrellm-radio-2.0.4.orig/debian/compat
+++ gkrellm-radio-2.0.4/debian/compat
@@ -0,0 +1 @@
+9

Bug#800215: gkrellkam: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: gkrellkam
Version: 2.0.0-1.1
Followup-For: Bug #800215
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

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

  * debian/rules:
- Remove legacy DH_COMPAT export.
- Replace dh_clean -k with dh_prep.
- Don't allow $(MAKE) clean to ignore errors.
  * debian/compat: Indicate compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-18-generic (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)
diff -u gkrellkam-2.0.0/debian/rules gkrellkam-2.0.0/debian/rules
--- gkrellkam-2.0.0/debian/rules
+++ gkrellkam-2.0.0/debian/rules
@@ -5,9 +5,6 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-# This is the debhelper compatability version to use.
-export DH_COMPAT=3
-
 configure: configure-stamp
 configure-stamp:
 	dh_testdir
@@ -30,14 +27,14 @@
 	rm -f build-stamp configure-stamp
 
 	# Add here commands to clean up after the build process.
-	-$(MAKE) clean
+	$(MAKE) clean
 
 	dh_clean
 
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 
 	# Add here commands to install the package into debian/gkrellkam.
diff -u gkrellkam-2.0.0/debian/control gkrellkam-2.0.0/debian/control
--- gkrellkam-2.0.0/debian/control
+++ gkrellkam-2.0.0/debian/control
@@ -2,12 +2,12 @@
 Section: x11
 Priority: optional
 Maintainer: paul cannon 
-Build-Depends: debhelper (>> 3.0.0), gkrellm (>= 2.0.0), libgtk2.0-dev, libglib2.0-dev
+Build-Depends: debhelper (>= 9), gkrellm (>= 2.0.0), libgtk2.0-dev, libglib2.0-dev
 Standards-Version: 3.5.8
 
 Package: gkrellkam
 Architecture: any
-Depends: gkrellm (>= 2.0.0), ${shlibs:Depends}
+Depends: ${misc:Depends}, gkrellm (>= 2.0.0), ${shlibs:Depends}
 Recommends: wget
 Description: GKrellM plugin that displays a periodically updating image
  GKrellKam is basically wmGrabImage in a GKrellM panel, except that it
only in patch2:
unchanged:
--- gkrellkam-2.0.0.orig/debian/compat
+++ gkrellkam-2.0.0/debian/compat
@@ -0,0 +1 @@
+9

Bug#800297: gkrellm-mailwatch: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: gkrellm-mailwatch
Version: 2.4.3-1
Followup-For: Bug #800297
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

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

  * debian/rules:
- Remove legacy DH_COMPAT export.
- Don't allow $(MAKE) clean to ignore errors.
- Replace dh_clean -k with dh_prep.
  * debian/compat: Specify compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-18-generic (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)
diff -u gkrellm-mailwatch-2.4.3/debian/control gkrellm-mailwatch-2.4.3/debian/control
--- gkrellm-mailwatch-2.4.3/debian/control
+++ gkrellm-mailwatch-2.4.3/debian/control
@@ -1,7 +1,7 @@
 Source: gkrellm-mailwatch
 Section: mail
 Priority: optional
-Build-Depends: debhelper, gkrellm (>= 2.0.0), libgtk2.0-dev
+Build-Depends: debhelper (>= 9), gkrellm (>= 2.0.0), libgtk2.0-dev
 Maintainer: Sjoerd Simons 
 Standards-Version: 3.1.1
 
@@ -9,7 +9,7 @@
 Architecture: any
 Replaces: gkrellm-mailwatch2
 Conflicts: gkrellm-mailwatch2
-Depends: gkrellm (>= 2.0.0), ${shlibs:Depends}
+Depends: ${misc:Depends}, gkrellm (>= 2.0.0), ${shlibs:Depends}
 Description: GKrellM plugin to watch mailboxes in multiple panels 
  A GKrellM plugin to monitor mbox, maildir and MH style mailboxes in
  multiple gkrellm panels.
diff -u gkrellm-mailwatch-2.4.3/debian/rules gkrellm-mailwatch-2.4.3/debian/rules
--- gkrellm-mailwatch-2.4.3/debian/rules
+++ gkrellm-mailwatch-2.4.3/debian/rules
@@ -5,8 +5,6 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-# This is the debhelper compatability version to use.
-export DH_COMPAT=3
 
 
 ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
@@ -39,14 +37,14 @@
 	rm -f build-stamp configure-stamp
 
 	# Add here commands to clean up after the build process.
-	-$(MAKE) clean
+	$(MAKE) clean
 
 	dh_clean
 
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 
 	# Add here commands to install the package into debian/tmp.
only in patch2:
unchanged:
--- gkrellm-mailwatch-2.4.3.orig/debian/compat
+++ gkrellm-mailwatch-2.4.3/debian/compat
@@ -0,0 +1 @@
+9

Bug#800226: python-imaging-doc-handbook: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: python-imaging-doc-handbook
Version: 1.1.2-1.1
Followup-For: Bug #800226
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

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

  * debian/rules: Remove legacy DH_COMPAT export.
  * debian/compat: Indicate compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-18-generic (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)
diff -u python-imaging-doc-handbook-1.1.2/debian/control python-imaging-doc-handbook-1.1.2/debian/control
--- python-imaging-doc-handbook-1.1.2/debian/control
+++ python-imaging-doc-handbook-1.1.2/debian/control
@@ -2,11 +2,12 @@
 Section: doc
 Priority: optional
 Maintainer: Simon Richter 
-Build-Depends: debhelper (>> 3.0.0)
+Build-Depends: debhelper (>= 9)
 Standards-Version: 3.5.2
 
 Package: python-imaging-doc-html
 Architecture: all
+Depends: ${misc:Depends}
 Description: Documentation for the Python Imaging Library.
  The Python Imaging Library (PIL) adds an image object to your
  Python interpreter. You can load image objects from a variety of file
@@ -16,6 +17,7 @@
 
 Package: python-imaging-doc-pdf
 Architecture: all
+Depends: ${misc:Depends}
 Suggests: pdf-viewer
 Description: Documentation for the Python Imaging Library.
  The Python Imaging Library (PIL) adds an image object to your
diff -u python-imaging-doc-handbook-1.1.2/debian/rules python-imaging-doc-handbook-1.1.2/debian/rules
--- python-imaging-doc-handbook-1.1.2/debian/rules
+++ python-imaging-doc-handbook-1.1.2/debian/rules
@@ -5,9 +5,6 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-# This is the debhelper compatability version to use.
-export DH_COMPAT=3
-
 configure:
 # Nothing to do
 
@@ -23,7 +20,7 @@
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 
 	for i in *.htm *.css *.gif; do \
only in patch2:
unchanged:
--- python-imaging-doc-handbook-1.1.2.orig/debian/compat
+++ python-imaging-doc-handbook-1.1.2/debian/compat
@@ -0,0 +1 @@
+9

Bug#760787: Please provide a backport of latest release

[anarcat]

Control: found -1 5.20151208-1~bpo8+1
Control: found -1 5.20141125

This is still an issue for me. I'm looking at a workaround for this bug:

https://git-annex.branchable.com/bugs/git_annex_get_fails_from_read-only_repository/

.. and it seems it needs at least a 2016 version to get this fix.

Can we get a new backport uploaded?

Thanks!

-- 
The history of any one part of the earth, like the life of a soldier,
consists of long periods of boredom and short periods of terror.
   - British geologist Derek V. Ager


signature.asc
Description: Digital signature

Bug#822229: jessie-pu: package autofs/5.0.8-2.1

[Salvatore Bonaccorso]

Hi Jonathan,

On Fri, Apr 22, 2016 at 11:24:02PM +0100, Jonathan Wiltshire wrote:
> Control: tag -1 confirmed
> 
> On Fri, Apr 22, 2016 at 11:22:59AM +0200, Salvatore Bonaccorso wrote:
> > +autofs (5.0.8-2.1) jessie; urgency=medium
> > +
> > +  * Non-maintainer upload.
> > +  * Remove macro debugging prints from macro_setenv (Closes: #755019)
> > +
> > + -- Salvatore Bonaccorso   Fri, 22 Apr 2016 10:34:58 
> > +0200
> 
> The version is slightly unusual. I would normally suggest 5.0.8-2+deb8u1
> even for an NMU, but I don't feel terribly strongly about it.

No, sorry this was an error on my side finalizing the debdiff. Will do
5.0.8-2+deb8u1.

> Please go ahead.

Thanks, uploaded!

Regards,
Salvatore


signature.asc
Description: PGP signature

Bug#800308: gkrellmwireless: Please migrate a supported debhelper compat level

[Logan Rosen]

Package: gkrellmwireless
Version: 2.0.3-1
Followup-For: Bug #800308
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

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

  * debian/rules:
- Remove legacy DH_COMPAT export.
- Don't allow $(MAKE) clean to ignore errors.
- Replace dh_clean -k with dh_prep.
  * debian/compat: Indicate compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-18-generic (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)
diff -u gkrellmwireless-2.0.3/debian/control gkrellmwireless-2.0.3/debian/control
--- gkrellmwireless-2.0.3/debian/control
+++ gkrellmwireless-2.0.3/debian/control
@@ -1,7 +1,7 @@
 Source: gkrellmwireless
 Section: x11
 Priority: optional
-Build-Depends: debhelper (>> 3.0.0), gkrellm (>= 2.0.0), libgtk2.0-dev
+Build-Depends: debhelper (>= 9), gkrellm (>= 2.0.0), libgtk2.0-dev
 Maintainer: Sjoerd Simons 
 Standards-Version: 3.5.7
 
@@ -9,7 +9,7 @@
 Conflicts: gkrellmwireless2
 Replaces: gkrellmwireless2
 Architecture: any
-Depends: gkrellm (>= 2.0.0), ${shlibs:Depends}
+Depends: ${misc:Depends}, gkrellm (>= 2.0.0), ${shlibs:Depends}
 Description: 802.11 wireless link monitor plugin for GKrellM
  This GKrellM plugin allows you to monitor the status of an 802.11 wireless
  ethernet link.
diff -u gkrellmwireless-2.0.3/debian/rules gkrellmwireless-2.0.3/debian/rules
--- gkrellmwireless-2.0.3/debian/rules
+++ gkrellmwireless-2.0.3/debian/rules
@@ -5,9 +5,6 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-# This is the debhelper compatability version to use.
-export DH_COMPAT=3
-
 ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
   CFLAGS += -g
 endif
@@ -33,13 +30,13 @@
 	rm -f build-stamp configure-stamp
 
 	# Add here commands to clean up after the build process.
-	-$(MAKE) clean
+	$(MAKE) clean
 	dh_clean
 
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 
 	# Add here commands to install the package into debian/tmp.
only in patch2:
unchanged:
--- gkrellmwireless-2.0.3.orig/debian/compat
+++ gkrellmwireless-2.0.3/debian/compat
@@ -0,0 +1 @@
+9

Bug#822295: staden: fix implicit pointer conversions

[Logan Rosen]

Package: staden
Version: 2.0.0+b10-4
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Dear Maintainer,

staden currently has a number of implicit pointer conversions that can cause
serious issues with the package, especially on 64-bit architectures. You can
see the build log check errors here:
https://qa.debian.org/bls/packages/s/staden.html

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

  * debian/patches/include_xalloc.patch: Include "xalloc.h" in a few more
files that use xcalloc.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-18-generic (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)
diff -Nru staden-2.0.0+b10/debian/patches/include_xalloc.patch staden-2.0.0+b10/debian/patches/include_xalloc.patch
--- staden-2.0.0+b10/debian/patches/include_xalloc.patch	1970-01-01 00:00:00.0 +
+++ staden-2.0.0+b10/debian/patches/include_xalloc.patch	2016-01-05 08:45:42.0 +
@@ -0,0 +1,31 @@
+Description: Include "xalloc.h" in a few more files that use xcalloc
+Author: Colin Watson 
+Forwarded: no
+Last-Update: 2016-01-05
+
+Index: b/hetins/hetins.c
+===
+--- a/hetins/hetins.c
 b/hetins/hetins.c
+@@ -9,6 +9,8 @@
+ #include 
+ #include 
+ 
++#include "xalloc.h"
++
+ #define FULL_TEST 2
+ #define TEST 1
+ 
+Index: b/stops/stops.c
+===
+--- a/stops/stops.c
 b/stops/stops.c
+@@ -13,6 +13,8 @@
+ #include 
+ #include 
+ 
++#include "xalloc.h"
++
+ void do_nothing(void) {}
+ 
+ /* johnt 1/6/99 must explicitly import globals from DLLs with Visual C++*/
diff -Nru staden-2.0.0+b10/debian/patches/series staden-2.0.0+b10/debian/patches/series
--- staden-2.0.0+b10/debian/patches/series	2016-02-23 08:36:00.0 +
+++ staden-2.0.0+b10/debian/patches/series	2016-03-26 20:56:21.0 +
@@ -8,3 +8,4 @@
 enable_setting_stadenroot.patch
 spelling.patch
 cope_with_modern_windowmanager.patch
+include_xalloc.patch

Bug#822294: network-manager: new upstream release (1.2.0)

[Paul Wise]

Package: network-manager
Severity: wishlist

There is a new upstream release: 1.2.0

It has some privacy enhancing features that would be nice to have:

https://blogs.gnome.org/lkundrak/2016/04/20/networkmanager-1-2-is-here/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#538067: status of the opencpn PPA for inclusion in Debian

[Paul Wise]

On Fri, 2016-04-22 at 16:20 -0300, Pavel Kalian wrote:

> Unfortunately I still did not receive any useful feedback from
> anybody, neither on Debian GIS mailing list, or any information on
> where I should submit something for review.

Generally it works like this:

https://mentors.debian.net/intro-maintainers

Here is a review of this package:

https://launchpad.net/~nohal/+archive/ubuntu/opencpn/+files/opencpn_4.2.0-0~xenial1.dsc

Based on my review, not much has been fixed since I last reviewed it.

In my opinion these issues block the upload of this package:

Others may accept the package despite these issues but I wouldn't.

All the embedded code copies (wxSVG etc) need to be removed from the
upstream VCS repo and tarballs and packaged separately (some are now).
For folks on other platforms they could provide a dependencies tarball.

https://wiki.debian.org/EmbeddedCodeCopies

I encourage de-forking the modified embedded code copies (zygrib etc).

I encourage de-duplicating the duplicated embedded code copies (wxJSON etc).

I encourage removing the non-free embedded code copies (unrar) and
replacing them with dependencies on free equivalents (unar).

There are some generated files in the source package (see the
licensecheck output below), these should be removed from the upstream
VCS repo and tarballs and created at build time by the upstream build
system instead.

Some of the generated PNG images have got out of sync with their SVG
source, upstream needs to investigate this.

Some of the generated PNG images (pkg_background.jpg for eg) look like
they were generated from proprietary maps.

Some of the generated files (MathJax.js and *.min.*) do not have their
corresponding source available in the package. This may be either a GPL
violation or a DFSG violation depending on the license of those files.

Helvetica.txf seems to have been generated from a proprietary font.

There are some Depends/Recommends that need to be packaged and uploaded
before opencpn can be uploaded.

The debian/copyright file is not accurate, it needs to document the
copyright and licenses of all the files in the source package.

https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html

In my opinion these issues would be nice to fix:

Please pass Debian's guide for upstreams along to the OpenCPN devs: 

https://wiki.debian.org/UpstreamGuide

data/license.txt is a copy of the GPL, there is no need to install that
in the package via debian/docs since it is in the common licenses dir.

/usr/share/common-licenses/

The new location for DEP-5 is on the Debian website:

https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

I suggest upgrading to debhelper compat 10 and using dh instead of
CDBS, but those are my personal preferences.

I suggest wrapping and sorting the debian/ dir using this command:

wrap-and-sort --short-indent --wrap-always --sort-binary-packages 
--trailing-comma --verbose

Is there any reason not to uncomment the OpenGL ES dependencies?

#For the ARM build, perhaps add: , libdri2-dev [armhf],libgles1-mesa-dev [armhf]

OpenGL ES is available on all Debian packages of Mesa so you don't need
to restrict it to armhf though.

The commented out Vcs-* URLs don't exist, I would remove them.

The URL in the Homepage field redirects to here:

http://opencpn.org/ocpn/

The package description doesn't need to mention the license because
that is in debian/copyright. It doesn't need to mention that opencpn is
free software because it would be in Debian main if accepted.

You might want to update the package to the latest Standards-Version:

http://www.debian.org/doc/debian-policy/upgrading-checklist

How are you creating/editing debian/changelog? The normal method (dch)
inserts a blank line between the entries.

Some of the SVG files in the plugin dirs seem to be duplicated in the
src/ and data/ subdirs.

If possible I would recommend the screenshots be generated at build
time so that they represent the current platform being built for and
also so they don't get outdated as UI elements change.

data/copyright and data/changelog.Debian.gz look like an aborted
attempt at Debian packaging and should be removed.

Please add a debian/watch file:

https://wiki.debian.org/debian/watch

Please add some upstream metadata:

https://wiki.debian.org/UpstreamMetadata

Please consider fuzz testing any installed programs that could parse
untrusted input using zzuf and afl.

I would suggest upstream remove uncontrolled advertising from their
download page, especially if it is hijacking downloads.

Automated checks:

build

lots of compiler warnings
lots of dpkg-shlibdeps warnings

lintian

P: opencpn source: duplicate-in-relation-field in source build-depends: 
libgtk2.0-dev, libgtk2.0-dev
P: opencpn source: insane-line-length-in-source-file 
plugins/chartdldr_pi/data/doc/MathJax.js line length is 32123 

Bug#538067: status of the opencpn PPA for inclusion in Debian

[Paul Wise]

On Fri, 2016-04-22 at 16:20 -0300, Pavel Kalian wrote:

> (yes, the stuff present in the upstream git tree and not needed to
> build on linux is stripped from them)

I forgot to mention that you should use Files-Excluded in
debian/copyright so that others can reproduce your removals:

https://wiki.debian.org/UscanEnhancements
https://wiki.debian.org/debian/watch

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#799939: chromium: does not build / is not available for armhf

[Michael Gilbert]

control: reopen -1

I tested the experimental package on armhf, and it always crashed, so
I didn't include this in the latest upload.

This will need to wait for a more reliable patch.

Best wishes,
Mike

Bug#822224: [Python-modules-team] Bug#822224: Further changes

[Brian May]

Neil Williams  writes:

> python-django and python-django-tables2 from jessie work but if either
> one is pulled in from jessie-backports without the other, restarting
> apache2 causes a HTTP500.

I am not sure I see how adding the Breaks header helps resolve this?
-- 
Brian May 

Bug#819703: my suggestion: change de message

[Fred Maranhão]

I would like to suggest the change of the annoying message.

alter

"This version of XScreenSaver is very old! Please upgrade!"

to

"This version of XScreenSaver is very old! Please don't send bugreports!"

and I prefer to see this message in debconf, not in every login.

Bug#822293: password-gorilla: Cannot save new passwords

[Neil Roeth]

Package: password-gorilla
Version: 1.5.3.7-1
Severity: grave

I have recently been unable to save new entries in Password Gorilla.  I
get an error about not being able to run ifconfig.  This occurs because
Password Gorilla uses the Tcl package uuid which way deep inside calls
ifconfig (full stack below).  On my Debian unstable system, the ifconfig
program is located in /sbin which is not in my PATH as a non-root user.

There are some workarounds:
* Add /sbin to your PATH (not a great idea)
* Create a symbolic link from /sbin/ifconfig to a directory in your PATH.
* Create a shell script in your PATH called ifconfig that does something
similar, like call "ip a" or "hostname -I". I don't really know what the
Tcl uuid package requires from ifconfig, so it is difficult to say what
is an appropriate substitute, but this worked for me.

Possible solutions:
* Change Password Gorilla to use some other method for generating UUIDs.
* Change the Tcl uuid package not to use ifconfig.

I set the severity to grave because this prevents saving password
entries which is the core function of Password Gorilla.

Error message stack:

couldn't execute "ifconfig": no such file or directory
couldn't execute "ifconfig": no such file or directory
while executing
"exec ifconfig"
(procedure "dump" line 2)
invoked from within
"dump"
(procedure "::nettool::mac_list" line 3)
invoked from within
"::nettool::mac_list"
(procedure "::nettool::hwid_list" line 3)
invoked from within
"::nettool::hwid_list"
(procedure "generate_tcl_machinfo" line 36)
invoked from within
"generate_tcl_machinfo"
(procedure "generate_tcl" line 7)
invoked from within
"generate_tcl"
(procedure "generate" line 6)
invoked from within
"generate"
(procedure "uuid::uuid" line 7)
invoked from within
"uuid::uuid generate"
(procedure "PopulateRecord" line 20)
invoked from within
"PopulateRecord [ set newrn [ $::gorilla::db createRecord ] ] "
(procedure "Ok" line 30)
invoked from within
"Ok"
(in namespace inscope "::gorilla::LoginDialog::0" script line 1)
invoked from within
"namespace inscope ::gorilla::LoginDialog::0 Ok"
invoked from within
".nmLoginDialog0.bf.top.ok invoke "
invoked from within
".nmLoginDialog0.bf.top.ok instate !disabled { .nmLoginDialog0.bf.top.ok
invoke } "
invoked from within
".nmLoginDialog0.bf.top.ok instate pressed { .nmLoginDialog0.bf.top.ok
state !pressed; .nmLoginDialog0.bf.top.ok instate !disabled {
.nmLoginDialog0.bf..."
(command bound to event)


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

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

Versions of packages password-gorilla depends on:
ii  itcl3   3.4.3-1
ii  tcl8.5  8.5.19-2
ii  tcllib  1.18-dfsg-2
ii  tk8.5   8.5.19-1
ii  tklib   0.6-3

password-gorilla recommends no packages.

password-gorilla suggests no packages.

-- no debconf information


-- 
Neil Roeth

Bug#822292: RFS: nauty/2.6r5+ds-1 [NEWRELEASE] - library for graph automorphisms

[Jerome Benoit]

Package: sponsorship-requests
Severity: normal

Dear Sponsors,

I am looking for sponsorship for the Debian package nauty [1]. This 
package
mainly brings to Debian the lastest release of nauty. nauty stands for
`No AUTomorphisms, Yes?'.

Thanks in advance,
Jerome

[1] https://anonscm.debian.org/cgit/debian-science/packages/nauty.git

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

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

Bug#821791: [Letsencrypt-devel] Bug#821791: acme-tiny: Source package includes modified source in .orig.tar.gz

[Jeremías Casteglione]

Hi Tomaž:

Thanks for reporting this!

On Tue, 19 Apr 2016 12:06:17 +0200
Tomaž Šolc  wrote:

> Package: acme-tiny
> Version: 20151229-4
> Severity: normal
> 
> Dear Maintainer,
> 
> it appears that acme-tiny source package includes Debian-specific
> modifications in .orig.tar.gz:
> 
> "setup.py" file as packaged does not appear in the upstream
> repository at https://github.com/diafygi/acme-tiny and acme_tiny.py
> appears to be modified as well (__check_deps, __entry_point
> functions).
> 
> These changes should be packaged as quilt patches under
> debian/patches and ..orig.tar.gz should contain unmodified upstream
> source.

When I started to build the package I asked in #d-devel about the best
way to proceed when there wasn't a setup.py provided by upstream; as
py2dsc needs it. It was mentioned there that the best would be to
create one and forward the patches to upstream, and base the package on
the new upstream release including the patches.

I then forked upstream's repo at github and generated a pull request [0]
providing my modifications to create a setup.py file.

 0: https://github.com/diafygi/acme-tiny/pull/86

I started to work on the package then using my fork of upstream's
repo with the setup.py file. Hoping the PR was going to be merged
sometime, but I could start to work in the meantime.

My PR was closed by upstream as duplicate of another PR providing a
setup.py file [1] too. But this PR wasn't merged yet either, so the
package is still based on my fork of upstream repo [2], which doesn't
introduce too many changes either [3].

 1: https://github.com/diafygi/acme-tiny/pull/59
 2: https://github.com/jrmsgit/acme-tiny/tree/jrms/setuptools
 3:
 
https://github.com/diafygi/acme-tiny/compare/master...jrmsgit:jrms/setuptools.patch

I'm waiting for upstream to merge any PR providing setuptools
integration, so I create a new release of the package, so until that
happens I think this could be a 'wontfix'.

Cheers,


-- 
Jeremías

Bug#820724: tp-smapi: The modules don't build against 4.6-rc? kernels

[Paul Wise]

On Fri, 15 Apr 2016 22:36:21 +0200 Elimar Riesebieter wrote:
> * Evgeni Golov [2016-04-15 17:31 +0200]:
> > [1] https://github.com/evgeni/tp_smapi/commit/8f40fcf3d9a4bfb9c3dae
1caa2107ea3a367a609
> 
> Builds fine with 4.4.6, 4.5.0 and 4.6.0-rc3.

I confirm that it works with Linux 4.6 from experimental and the
resulting module loads and hdapsd works with it.

Could we get this uploaded to Debian?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#821761: linux-image-4.5.0-1-amd64: [regression] switching from gdm Xorg vt to normal virtual console corrupts display until reboot

[Paul Wise]

Control: reopen -1

On Thu, 2016-04-21 at 13:04 +0800, Paul Wise wrote:

> I will reopen if I see this next time I reboot.

I did a bunch of reboot testing with Linux 4.6 from experimental and on
about two-thirds of the reboots I got the problem occurring. During one
boot where the problem did not occur I stopped gdm and started it again
and the problem occurred again. Any thoughts about debugging this?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#820995: jessie-pu: package lvm2/2.02.111-2.2

[Cyril Brulebois]

Hi,

Jonathan Wiltshire  (2016-04-22):
> Control: tag -1 moreinfo d-i
> 
> On Thu, Apr 14, 2016 at 02:18:47PM +0200, Bastian Blank wrote:
> > +lvm2 (2.02.111-3) UNRELEASED; urgency=medium
> > +
> > +  * Set default pid directory to /run. (closes: #783120)
> > +
> > + -- Bastian Blank   Thu, 14 Apr 2016 11:35:55 +
> > +
> 
> Seems sensible, but the version should be 2.02.111-2+deb8u1, and the
> udeb needs a d-i ack. Ccing Cyril.

The fact it's been added only for the deb build, while the udeb one has
a separate set of options, makes me think d-i shouldn't be affected; so
no objections.


KiBi.


signature.asc
Description: Digital signature

Bug#822291: postfix: after upgrade to 3.1.0-3 connections timeout

[Robin Cook]

Package: postfix
Version: 3.1.0-3
Severity: normal

Dear Maintainer,

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

Use apt-get to do a system upgrade and after install the postfix timeouts on 
connection for both inbound and outbound mail.

These are the only log messages I can find.  The log is getting filled with the 
exit status 127 and throttling messages.

postfix[32296]: Postfix is running with backwards-compatible default settings
postfix[32296]: See http://www.postfix.org/COMPATIBILITY_README.html for details
postfix[32296]: To disable backwards compatibility use "postconf 
compatibility_level=2" and "postfix reload"
postfix/master[32301]: warning: Postfix library version mis-match: wanted 
3.0.3, found 3.1.0
postfix/master[32333]: warning: Postfix library version mis-match: wanted 
3.0.3, found 3.1.0
postfix/master[32333]: warning: process /usr/libexec/postfix/smtpd pid 32563 
exit status 127
postfix/master[32333]: warning: /usr/libexec/postfix/smtpd: bad command startup 
-- throttling

postconf -v

2bounce_notice_recipient = postmaster
access_map_defer_code = 450
access_map_reject_code = 554
address_verify_cache_cleanup_interval = 12h
address_verify_default_transport = $default_transport
address_verify_local_transport = $local_transport
address_verify_map = btree:$data_directory/verify_cache
address_verify_negative_cache = yes
address_verify_negative_expire_time = 3d
address_verify_negative_refresh_time = 3h
address_verify_pending_request_limit = 5000
address_verify_poll_count = ${stress?{1}:{3}}
address_verify_poll_delay = 3s
address_verify_positive_expire_time = 31d
address_verify_positive_refresh_time = 7d
address_verify_relay_transport = $relay_transport
address_verify_relayhost = $relayhost
address_verify_sender = $double_bounce_sender
address_verify_sender_dependent_default_transport_maps = 
$sender_dependent_default_transport_maps
address_verify_sender_dependent_relayhost_maps = 
$sender_dependent_relayhost_maps
address_verify_sender_ttl = 0s
address_verify_service_name = verify
address_verify_transport_maps = $transport_maps
address_verify_virtual_transport = $virtual_transport
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
allow_mail_to_commands = alias, forward
allow_mail_to_files = alias, forward
allow_min_user = no
allow_percent_hack = yes
allow_untrusted_routing = no
alternate_config_directories =
always_add_missing_headers = no
always_bcc =
anvil_rate_time_unit = 60s
anvil_status_update_time = 600s
append_at_myorigin = yes
append_dot_mydomain = no
application_event_drain_time = 100s
authorized_flush_users = static:anyone
authorized_mailq_users = static:anyone
authorized_submit_users = static:anyone
backwards_bounce_logfile_compatibility = yes
berkeley_db_create_buffer_size = 16777216
berkeley_db_read_buffer_size = 131072
best_mx_transport =
biff = no
body_checks =
body_checks_size_limit = 51200
bounce_notice_recipient = postmaster
bounce_queue_lifetime = 5d
bounce_service_name = bounce
bounce_size_limit = 5
bounce_template_file =
broken_sasl_auth_clients = no
bsmtp_delivery_slot_cost = $default_delivery_slot_cost
bsmtp_delivery_slot_discount = $default_delivery_slot_discount
bsmtp_delivery_slot_loan = $default_delivery_slot_loan
bsmtp_destination_concurrency_failed_cohort_limit = 
$default_destination_concurrency_failed_cohort_limit
bsmtp_destination_concurrency_limit = $default_destination_concurrency_limit
bsmtp_destination_concurrency_negative_feedback = 
$default_destination_concurrency_negative_feedback
bsmtp_destination_concurrency_positive_feedback = 
$default_destination_concurrency_positive_feedback
bsmtp_destination_rate_delay = $default_destination_rate_delay
bsmtp_destination_recipient_limit = $default_destination_recipient_limit
bsmtp_extra_recipient_limit = $default_extra_recipient_limit
bsmtp_initial_destination_concurrency = $initial_destination_concurrency
bsmtp_minimum_delivery_slots = $default_minimum_delivery_slots
bsmtp_recipient_limit = $default_recipient_limit
bsmtp_recipient_refill_delay = $default_recipient_refill_delay
bsmtp_recipient_refill_limit = $default_recipient_refill_limit
bsmtp_time_limit = $command_time_limit
bsmtp_transport_rate_delay = $default_transport_rate_delay
canonical_classes = envelope_sender, envelope_recipient, header_sender, 
header_recipient
canonical_maps =
cleanup_service_name = cleanup
command_directory = /usr/sbin
command_execution_directory =
command_expansion_filter = 
1234567890!@%-_=+:,./abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
command_time_limit = 1000s
compatibility_level = 0
config_directory = /etc/postfix
confirm_delay_cleared = no
connection_cache_protocol_timeout = 5s
connection_cache_service_name = scache
connection_cache_status_update_time = 600s
connection_cache_ttl_limit = 2s
content_filter =
cyrus_sasl_config_path =
daemon_directory = /usr/libexec/postfix
daemon_table_open_error_is_fatal = no
daemon_timeout = 18000s
data_directory = 

Bug#800413: Helping

[Junior Santos]

How can I help you?

I'am noob in packagin Debian.

https://qa.debian.org/developer.php?login=j.s.junior%40live.com

[]`s
JJ


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#818687: RFS: btrfs-progs/4.4.1-1.1 [NMU]

[Nicholas D Steeves]

Hi Gianfranco,

Here is a link to the latest version, which uses triggers instead of
postinst and postrm.  I think it's ready to upload, but please double
check :-)

http://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.4.1-1.1.dsc

Cheers,
Nicholas

Bug#800413: Helping

[Junior Santos]

How can I help you?

I'am noob in packagin Debian.

https://qa.debian.org/developer.php?login=j.s.junior%40live.com

[]`s
JJ


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#786515: nautilus: any news ?

[gpe92]

Package: nautilus
Version: 3.18.5-1
Followup-For: Bug #786515

Dear Maintainer,

Do you have any news about this nasty bug?

BR

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

Kernel: Linux 4.5.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 nautilus depends on:
ii  desktop-file-utils 0.22-1
ii  gsettings-desktop-schemas  3.18.1-1
ii  gvfs   1.28.1-1
ii  libatk1.0-02.20.0-1
ii  libc6  2.22-6
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libexempi3 2.3.0-2
ii  libexif12  0.6.21-2
ii  libgail-3-03.18.9-1
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libglib2.0-0   2.48.0-1
ii  libglib2.0-data2.48.0-1
ii  libgnome-desktop-3-12  3.18.2-1
ii  libgtk-3-0 3.18.9-1
ii  libnautilus-extension1a3.18.5-1
ii  libpango-1.0-0 1.40.1-1
ii  libpangocairo-1.0-01.40.1-1
ii  libselinux12.4-3+b1
ii  libtracker-sparql-1.0-01.8.0-2+b1
ii  libx11-6   2:1.6.3-1
ii  libxml22.9.3+dfsg1-1
ii  nautilus-data  3.18.5-1
ii  shared-mime-info   1.5-2

Versions of packages nautilus recommends:
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-sushi3.18.0-1
ii  gvfs-backends  1.28.1-1
ii  librsvg2-common2.40.15-1

Versions of packages nautilus suggests:
ii  acroread [pdf-viewer]  9.5.5-dmo2
ii  brasero3.12.1-1
ii  eog3.18.2-1
ii  evince [pdf-viewer]3.20.0-1
ii  totem  3.18.1-2+b1
ii  tracker1.8.0-2+b1
ii  vlc [mp3-decoder]  1:2.2.2-dmo6
ii  vlc-nox [mp3-decoder]  1:2.2.2-dmo6
ii  xdg-user-dirs  0.15-2

-- no debconf information

Bug#822290: colorpicker: disturbing text of license grant

[Dmitry Smirnov]

Source: colorpicker
Version: 1.0.0-2
Severity: normal
Usertags: dfsg

Some files have fairly disturbing text of license grant:


 You may not use, copy or modify this software, except in
 accordance with the license agreement you entered into with
 Jeremy Wood. For details see accompanying license terms.


I'm not even sure if this is a reference to modified BSD-3-Clause license 
from "License.html" as the latter does not mention Jeremy Wood in the text of 
the license.

I believe this text of license grant is not DFSG compliant as (most) users 
are unlikely to be in any direct license agreement with copyright owner.

Please investigate.

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


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

Bug#816169: RFS: fake-factory/0.5.3-1

[Mattia Rizzolo]

any news on this? :)
nearly a month passed, and the "problematic" thing has been merged
upstream.

On Sun, Mar 27, 2016 at 12:45:37PM +, Mattia Rizzolo wrote:
> On Sun, Mar 27, 2016 at 10:49:55AM +0100, Christopher Baines wrote:
> > On 20/03/16 03:12, Mattia Rizzolo wrote:
> > >> The issues that you commented on above are fixed in this repository.
> > >>
> > >> 1: https://anonscm.debian.org/cgit/python-modules/packages/faker.git
> > > 
> > > of what I wrote before these still need fixing:
> > > 
> > > * debian/control:
> > >   + I: fake-factory source: duplicate-long-description 
> > > python-fake-factory python3-fake-factory
> > >   + I: python-fake-factory: extended-description-is-probably-too-short
> > >   + I: python3-fake-factory: extended-description-is-probably-too-short
> > 
> > I have added the Python version to the extended description, which fixes
> > these lintian issues.
> 
> Yes, that's probably the most common fix for duplicate-long-description
> :)
> 
> > > did you manually fix this in the build manpage by any chance?
> > 
> > Yes
> 
> I see.
> 
> > I have made a pull request to the upstream project, improving the help
> > output in a way that will fix these issues [1]. Its a bit awkward, but
> > is the best step to take next, to wait for upstream to do a release with
> > these changes?
> > 
> > A possible alternative would be to include a manpage made with help2man,
> > and not generate it for this version (and switch to generating it later)?
> > 
> > 1: https://github.com/joke2k/faker/pull/342
> 
> This pull request looks cool to me.
> 
> I'd probably just include that patch in the package (either after
> waiting an ACK from upstream or not, your call).
> 
> -- 
> regards,
> Mattia Rizzolo
> 
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  http://mapreri.org  : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-



-- 
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#822269: lintian: version-substvar-for-external-package on multiarch relationship

[Javier Serrano Polo]

The error is:
E: lmms source: version-substvar-for-external-package lmms -> i386


smime.p7s
Description: S/MIME cryptographic signature

Bug#822269: lintian: version-substvar-for-external-package on multiarch relationship

[Javier Serrano Polo]

Control: tag -1 + patch

Here it is the proposed solution.
--- a/checks/version-substvars.pm	2016-03-15 07:32:05.0 +0100
+++ b/checks/version-substvars.pm	2016-04-23 01:28:17.0 +0200
@@ -66,7 +66,7 @@
 tag 'substvar-source-version-is-deprecated', $pkg1;
 }
 if (
-m/ ($PKGNAME_REGEX)(?: :any)? \s*   # pkg-name $1
+m/ ($PKGNAME_REGEX)(?: :[-a-z0-9]+)? \s*# pkg-name $1
\(\s*[\>\<]?[=\>\<]\s*  # REL 
 \$[{](?:Source-|source:|binary:)Version[}] # {subvar}
  /x


smime.p7s
Description: S/MIME cryptographic signature

Bug#818687: RFS: btrfs-progs/4.4.1-1.1 [NMU]

[Nicholas D Steeves]

Hi Dimitri,

On 22 April 2016 at 19:20, Dimitri John Ledkov  wrote:
> I haven't looked closely, but i have a lot dubious emails about btrfs package.
> (a) i do not maintain backports, anybody is free to do those
> (b) all of my packages are lowNMU, meaning I trust any/all DDs to do
> sensible things
> (c) I do not trust any other developers, meaning that nobody should be
> granting DM and/or changing Uploaders/Maintainers fields etc
> (d) any other fixes is fine to be uploaded, and if things break I am
> on the hook to fix things up afterwards =)
>
> http://blog.surgut.co.uk/2013/01/thoughts-on-debian-package-policies.html

Yes!  I've been wondering about this for quite some time!

Thank you,
Nicholas

Bug#822289: ITP: golang-github-docker-go-events -- Composable event distribution for Go

[Potter, Tim (HPE Linux Support)]

Package: wnpp
Severity: wishlist
Owner: Tim Potter 
X-Debbugs-CC: debian-de...@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org

* Package name: golang-github-docker-go-events
  Version : 0.0~git20160331.0.882f161-1
  Upstream Author : Stephen Day and Andrea Luzzardi
* URL : https://github.com/docker/go-events
* License : Apache-2.0
  Programming Lang: Go
  Description : Composable event distribution for Go

The go-events package implements a composable event distribution
package for Go. It was originally created to implement the
notifications in Docker Registry 2, but is now used in other
components of the Docker ecosystem.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#822288: dh --buildsystem=ruby ignores hardening=+bindnow

[Jean-Michel Vourgère]

Package: libruby2.3
Version: 2.3.0-5
Severity: normal

Hello

When building package rrdtool, I tried adding in my d/rules:
export DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow

lintian stop complaining about "hardening-no-bindnow" for all packages but
one: ruby-rrd.

The package uses this extconf.rb:
-- 8< ---
require 'mkmf'
dir_config("rrd",['$(ABS_TOP_BUILDDIR)/src', 
'$(ABS_TOP_SRCDIR)/src'],'$(ABS_TOP_BUILDDIR)/src/.libs')
have_library("rrd", "rrd_create")
create_makefile("RRD")
-- 8< ---

and the compilation is:

gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.3.0 
-I/usr/include/ruby-2.3.0/ruby/backward
-I/usr/include/ruby-2.3.0 -I. -I/<>/src -I/<>/src 
-Wdate-time
-D_FORTIFY_SOURCE=2   -fPIC -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -fPIC  -o main.o -c main.c
gcc -shared -o RRD.so main.o -L. -L/usr/lib/x86_64-linux-gnu 
-L/<>/src/.libs
-L. -Wl,-z,relro -fstack-protector -rdynamic -Wl,-export-dynamic
-lruby-2.3 -lrrd
-lpthread -lgmp -ldl -lcrypt -lm   -lc

As you can see, "-Wl,-z,now" is missing from the LDFLAGS.

If I add to my extconf.rb:
 $CFLAGS = ENV['CFLAGS']
 $CPPFLAGS = ENV['CPPFLAGS']
 $CXXFLAGS = ENV['CXXFLAGS']
 $LDFLAGS = ENV['LDFLAGS']
or
 $CFLAGS << ' ' + ENV['CFLAGS']
 $CPPFLAGS << ' ' + ENV['CPPFLAGS']
 $CXXFLAGS << ' ' + ENV['CXXFLAGS']
 $LDFLAGS << ' ' + ENV['LDFLAGS']
then debhelper uses the correct flags.

I have the feeling all the flags are hard-coded from
/usr/lib/x86_64-linux-gnu/ruby/2.3.0/rbconfig.rb
which is the wrong thing to do.

Any chance this can be fixed globally?

Bug#822277: gdk-pixbuf is not binNMU safe and becomes uninstallable on every package update

[Matthias Klose]

On 23.04.2016 01:16, Michael Biebl wrote:

Am 23.04.2016 um 01:10 schrieb Matthias Klose:

Control: reopen -1

On 23.04.2016 01:07, Michael Biebl wrote:

Am 23.04.2016 um 01:02 schrieb Matthias Klose:

On 23.04.2016 00:50, Michael Biebl wrote:

Am 23.04.2016 um 00:09 schrieb Matthias Klose:

Package: src:gdk-pixbuf
Version: 2.34.0-1
Severity: important

$ apt-cache show libgdk-pixbuf2.0-0|grep Depends
Depends: libgdk-pixbuf2.0-common (= 2.34.0-1)

In this form the package cannot be binNMUed


Sure it can.
Using = ${source:Version} between a arch: any to arch: all package is
totally safe.


but this shows up every time as uninstallability when the gdk-pixbuf is
not yet built on some archs, and I'm trying to build either gcc or
openjdk.


So what? That just means the dependencies work as intended. We don't
want any version skew. Once the buildds have picked up, your package
will build just fine.


well, you're artificially delaying archive builds.


We aren't. And it's really a non-issue. It's not like gdk-pixbuf is
uploaded every other day or takes days to build. So the most delay you
will get is about 6 hours.


yes, and likely another six hours for any other of such build dependencies.

Bug#822286: libvulkan1: calls ldconfig multiple times

[James Cowgill]

Package: libvulkan1
Version: 1.0.8.0+dfsg1-1
Severity: minor

Hi,

Another minor bug I just noticed :)

libvulkan1 ships a postinst and postrm to call ldconfig, but the call
to ldconfig is already handled by debhelper through a dpkg trigger.
This means that installing libvulkan1 ends up calling ldconfig 3 times
instead of once.

Removing the maintainer scripts should solve this.

Thanks,
James

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

Bug#822287: [golang-github-armon-go-metrics] Please update to latest snapshot

[Potter, Tim (HPE Linux Support)]

Package: golang-github-armon-go-metrics
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest snapshot of the golang-github-armon-go-metrics package,
0.0~git20160307.0.f303b03.  I've already packaged this in the repo on alioth.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#818687: RFS: btrfs-progs/4.4.1-1.1 [NMU]

[Dimitri John Ledkov]

On 23 April 2016 at 00:06, Nicholas D Steeves  wrote:
> On 21 April 2016 at 08:33, Christian Seiler  wrote:
>> Hi Gianfranco,
>>
>> On 04/21/2016 09:48 AM, Gianfranco Costamagna wrote:
 activate update-initramfs
>>> do you think it is worth adding to the current NMU or it is better to leave 
>>> it for
>>> a future upload?
>>
>> I'm not sure if you meant to ask me, but just in case: I would suggest
>> you do so, but it's not my decision, as it's not my package. ;-)
>>
>>> the change looks good, I think it has no side effects,
>
> I really like this change to using a trigger!  It also works fine on
> Jessie, meaning it won't complicate maintaining a backport.  As I'm
> not listed in Uploaders, Maintainers, or Changed-by, would making this
> change be considered a package hijack?


I haven't looked closely, but i have a lot dubious emails about btrfs package.
(a) i do not maintain backports, anybody is free to do those
(b) all of my packages are lowNMU, meaning I trust any/all DDs to do
sensible things
(c) I do not trust any other developers, meaning that nobody should be
granting DM and/or changing Uploaders/Maintainers fields etc
(d) any other fixes is fine to be uploaded, and if things break I am
on the hook to fix things up afterwards =)

http://blog.surgut.co.uk/2013/01/thoughts-on-debian-package-policies.html


-- 
Regards,

Dimitri.

Bug#818687: RFS: btrfs-progs/4.4.1-1.1 [NMU]

[Nicholas D Steeves]

On 21 April 2016 at 03:53, Jakub Wilk  wrote:
> Policy §10.4 says that /bin/sh script need to follow SUSv3 + some
> extensions. Both "hash" and "command -v" are optional in SUSv3 (but they are
> mandatory in SUSv4), so in theory you shouldn't use them. In practice,
> however, "command -v" is probably more portable than anything else.
>
> "which" is not standardized, but you can rely on it as far as Debian in
> concerned, because it's shipped by an essential package.
>
> Related bugs: #747320, #733511

Thank you very much for the reference.  Also, this is the first time
I've seen the section symbol "§".  So just to clarify, both "command
-v" and "which" are acceptable for Debian work, and which one I use is
a matter of preference?  I consulted the Policy, which recommended
checking the script with "checkbashisms."  Checkbashisms reports:
possible bashism in btrfs-progs.postinst line 7 ('command' with option
other than -p)

I assume this can be disregarded, but it makes me wonder if "which" is
most Debian-correct in the strictest sense, because it can be relied
on "because it's shipped by an essential package" and because there is
no possible conflict with Policy § 10.4.

>> In this case, I think it broke on piuparts because piuparts used bash; so
>> I think this was an dashism rather than a bashism ;-)
>
>
> You can't rely on the output format of argumentless "hash"; but other than
> that it works fine in both dash and bash.

Guilty as charged!

Cheers,
Nicholas

Bug#822277: gdk-pixbuf is not binNMU safe and becomes uninstallable on every package update

[Michael Biebl]

Am 23.04.2016 um 01:10 schrieb Matthias Klose:
> Control: reopen -1
> 
> On 23.04.2016 01:07, Michael Biebl wrote:
>> Am 23.04.2016 um 01:02 schrieb Matthias Klose:
>>> On 23.04.2016 00:50, Michael Biebl wrote:
 Am 23.04.2016 um 00:09 schrieb Matthias Klose:
> Package: src:gdk-pixbuf
> Version: 2.34.0-1
> Severity: important
>
> $ apt-cache show libgdk-pixbuf2.0-0|grep Depends
> Depends: libgdk-pixbuf2.0-common (= 2.34.0-1)
>
> In this form the package cannot be binNMUed

 Sure it can.
 Using = ${source:Version} between a arch: any to arch: all package is
 totally safe.
>>>
>>> but this shows up every time as uninstallability when the gdk-pixbuf is
>>> not yet built on some archs, and I'm trying to build either gcc or
>>> openjdk.
>>
>> So what? That just means the dependencies work as intended. We don't
>> want any version skew. Once the buildds have picked up, your package
>> will build just fine.
> 
> well, you're artificially delaying archive builds. 

We aren't. And it's really a non-issue. It's not like gdk-pixbuf is
uploaded every other day or takes days to build. So the most delay you
will get is about 6 hours.


-- 
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#822275: Acknowledgement (RFP: crystal -- Compiler of the Crystal object-oriented programming language)

[Luc Sarzyniec]

An issue has been opened on the Crystal's project issue tracker:
https://github.com/crystal-lang/crystal/issues/2499 .

Bug#822284: vulkan: split validation layers out of libvulkan1

[James Cowgill]

Source: vulkan
Version: 1.0.8.0+dfsg1-1
Severity: wishlist

Hi,

Firstly I haven't be using Vulkan that long so I might not have this
totally right but...

It seems to me that the validation layer files (*.json, libVkLayer_*.so
and liblayer_utils.so) are not required to actually run Vulkan
applications but are only used during development. These files should
therefore be in a separate package, possibly depended or recommended on
by libvulkan-dev. This would shave about 9M off the installed package
size as well.

Thanks,
James

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

Bug#822277: gdk-pixbuf is not binNMU safe and becomes uninstallable on every package update

[Matthias Klose]

Control: reopen -1

On 23.04.2016 01:07, Michael Biebl wrote:

Am 23.04.2016 um 01:02 schrieb Matthias Klose:

On 23.04.2016 00:50, Michael Biebl wrote:

Am 23.04.2016 um 00:09 schrieb Matthias Klose:

Package: src:gdk-pixbuf
Version: 2.34.0-1
Severity: important

$ apt-cache show libgdk-pixbuf2.0-0|grep Depends
Depends: libgdk-pixbuf2.0-common (= 2.34.0-1)

In this form the package cannot be binNMUed


Sure it can.
Using = ${source:Version} between a arch: any to arch: all package is
totally safe.


but this shows up every time as uninstallability when the gdk-pixbuf is
not yet built on some archs, and I'm trying to build either gcc or openjdk.


So what? That just means the dependencies work as intended. We don't
want any version skew. Once the buildds have picked up, your package
will build just fine.


well, you're artificially delaying archive builds.  Imagine I would add such a 
dependency in one of the GCC runtime libraries. So there is an issue.


> Not being binNMU safe means something completely different.

well, how should the issue be renamed?

Bug#822277: gdk-pixbuf is not binNMU safe and becomes uninstallable on every package update

[Michael Biebl]

Am 23.04.2016 um 01:02 schrieb Matthias Klose:
> On 23.04.2016 00:50, Michael Biebl wrote:
>> Am 23.04.2016 um 00:09 schrieb Matthias Klose:
>>> Package: src:gdk-pixbuf
>>> Version: 2.34.0-1
>>> Severity: important
>>>
>>> $ apt-cache show libgdk-pixbuf2.0-0|grep Depends
>>> Depends: libgdk-pixbuf2.0-common (= 2.34.0-1)
>>>
>>> In this form the package cannot be binNMUed
>>
>> Sure it can.
>> Using = ${source:Version} between a arch: any to arch: all package is
>> totally safe.
> 
> but this shows up every time as uninstallability when the gdk-pixbuf is
> not yet built on some archs, and I'm trying to build either gcc or openjdk.

So what? That just means the dependencies work as intended. We don't
want any version skew. Once the buildds have picked up, your package
will build just fine.
Not being binNMU safe means something completely different.

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#803423: #803423 libqt5gui5: Ugly GUI (no icons) / Weird interpretation of XDG_CURRENT_DESKTOP and GNOME_DESKTOP_SESSION_ID

[Lisandro Damián Nicanor Pérez Meyer]

On Friday 22 April 2016 16:23:04 Dmitry Shachnev wrote:
> Hi Lisandro,
[snip] 
> On X11, there *is* a (semi-)DE-independent way to figure out the icon theme
> name: it's the XSettings mechanism (supported by at least GNOME, Unity, Xfce
> and LXDE). There even exists an XSettings implementation in the latest
> qtbase versions, it just needs to be used by QGenericUnixTheme's
> themeHint() method.

But that doesn't seems to solve the ssh problem, right? For example one could 
run wireshark trough X port forwarding without a DE.

-- 
"With great power comes great responsibility."
  Peter Parker's uncle.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#818687: RFS: btrfs-progs/4.4.1-1.1 [NMU]

[Nicholas D Steeves]

On 21 April 2016 at 08:33, Christian Seiler  wrote:
> Hi Gianfranco,
>
> On 04/21/2016 09:48 AM, Gianfranco Costamagna wrote:
>>> activate update-initramfs
>> do you think it is worth adding to the current NMU or it is better to leave 
>> it for
>> a future upload?
>
> I'm not sure if you meant to ask me, but just in case: I would suggest
> you do so, but it's not my decision, as it's not my package. ;-)
>
>> the change looks good, I think it has no side effects,

I really like this change to using a trigger!  It also works fine on
Jessie, meaning it won't complicate maintaining a backport.  As I'm
not listed in Uploaders, Maintainers, or Changed-by, would making this
change be considered a package hijack?

Cheers,
Nicholas

Bug#813935: Acknowledgement (gtk+3.0: FTBFS from source on hppa: "randrom" failure of reftests)

[John David Anglin]

With 3.20.3-1, we have one fixed test and one new fail.  See:
https://buildd.debian.org/status/fetch.php?pkg=gtk%2B3.0=hppa=3.20.3-1=1461285606

The color-transition test no longer fails.  But the button-wrapping test now 
fails.

The previous patch doesn't work because the known failure patch has been 
removed.

Dave
--
John David Anglin   dave.ang...@bell.net

Bug#822277: gdk-pixbuf is not binNMU safe and becomes uninstallable on every package update

[Matthias Klose]

On 23.04.2016 00:50, Michael Biebl wrote:

Am 23.04.2016 um 00:09 schrieb Matthias Klose:

Package: src:gdk-pixbuf
Version: 2.34.0-1
Severity: important

$ apt-cache show libgdk-pixbuf2.0-0|grep Depends
Depends: libgdk-pixbuf2.0-common (= 2.34.0-1)

In this form the package cannot be binNMUed


Sure it can.
Using = ${source:Version} between a arch: any to arch: all package is
totally safe.


but this shows up every time as uninstallability when the gdk-pixbuf is not yet 
built on some archs, and I'm trying to build either gcc or openjdk.

Bug#800762: Java problem when upgrading pixelmed

[Andreas Tille]

On Fri, Apr 22, 2016 at 09:50:24AM +0200, Markus Koschany wrote:
> Hi,
> 
> pixelmed is the last package that blocks the removal of
> libcommons-net2-java. What is the status?

I tried to build current SVN status but was running into


...
export JAVAVERSIONTARGETJARFILE=/usr/lib/jvm/default-java/jre/lib/rt.jar; javac 
-O -target 1.7 -source 1.7 -bootclasspath ${JAVAVERSIONTARGETJARFILE} -encoding 
"UTF8" -Xlint:deprecation -XDignore.symbol.file \
-classpath 
../../..:/usr/share/java/hsqldb.jar:/usr/share/java/commons-net2.jar:/usr/share/java/pixelmed_codec.jar:/usr/share/java/javax.json-api-1.0.jar
 \
-sourcepath ../../.. MergeFunctionalGroups.java
export JAVAVERSIONTARGETJARFILE=/usr/lib/jvm/default-java/jre/lib/rt.jar; javac 
-O -target 1.7 -source 1.7 -bootclasspath ${JAVAVERSIONTARGETJARFILE} -encoding 
"UTF8" -Xlint:deprecation -XDignore.symbol.file \
-classpath 
../../..:/usr/share/java/hsqldb.jar:/usr/share/java/commons-net2.jar:/usr/share/java/pixelmed_codec.jar:/usr/share/java/javax.json-api-1.0.jar
 \
-sourcepath ../../.. SetCharacteristicsFromSummary.java
SetCharacteristicsFromSummary.java:41: error: package javax.json does not exist
import javax.json.Json;
 ^
SetCharacteristicsFromSummary.java:42: error: package javax.json does not exist
import javax.json.JsonArray;
 ^
SetCharacteristicsFromSummary.java:43: error: package javax.json does not exist
import javax.json.JsonObject;
 ^
SetCharacteristicsFromSummary.java:44: error: package javax.json does not exist
import javax.json.JsonReader;
 ^
SetCharacteristicsFromSummary.java:45: error: package javax.json does not exist
import javax.json.JsonString;
 ^
SetCharacteristicsFromSummary.java:46: error: package javax.json does not exist
import javax.json.JsonValue;
 ^


Any help would be welcome.

Kind regards

Andreas.


-- 
http://fam-tille.de

Bug#820193: jessie-pu: package quota/4.01-8

[Jonathan Wiltshire]

Control: tag -1 moreinfo

On Wed, Apr 06, 2016 at 02:37:16PM +0200, Michael Meskes wrote:
> +quota (4.01-8+deb8u1) stable-proposed-updates; urgency=medium
> +
> +  * Change invocation of quota services, so systemd takes over most of the 
> work.
> +Only the initial check is still performed by the service file provide by
> +quota.
> +
> + -- Michael Meskes   Wed, 06 Apr 2016 14:12:06 +0200

Could you add Closes for appropriate bugs please?

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#822283: libvulkan1: typo in package description

[James Cowgill]

Package: libvulkan1
Version: 1.0.8.0+dfsg1-1
Severity: minor
Tags: patch

Hi,

The package description for libvulkan1 claims to include the
"vulkaninfo" binary, but it does not - it's in vulkan-utils instead.

While looking at the control file I also noticed that vulkan-utils
depends on libvulkan1 which seemed strange (since it's added
automatically) so I removed it, but feel free to ignore that bit of the
patch if you want.

Thanks,
Jamesdiff -ur a/debian/control b/debian/control
--- a/debian/control	2016-04-14 11:57:06.0 +0100
+++ b/debian/control	2016-04-22 23:06:30.906063978 +0100
@@ -25,7 +25,7 @@
  this, it dispatches API calls to the correct driver, and to the correct
  layers, based on the GPU object selected by the application.
  .
- This package includes the loader library and vulkaninfo binary.
+ This package includes the loader library.
 
 Package: libvulkan-dev
 Section: libdevel
@@ -45,6 +45,5 @@
 Architecture: any
 Section: graphics
 Depends: ${shlibs:Depends}, ${misc:Depends},
- libvulkan1,
 Description: Miscellaneous Vulkan utilities
  This package provides utilities for Vulkan, including vulkaninfo.


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

Bug#822282: mention that -p also prints an IGNORED class of items without exiting non-zero

[積丹尼 Dan Jacobson]

Package: e2fsprogs
Version: 1.43~WIP.2016.03.15-2
Severity: wishlist
File: /usr/share/man/man8/e2fsck.8.gz

We see:

   -p Automatically repair ("preen") the  file  system.   This  option
  will  cause  e2fsck to automatically fix any filesystem problems
  that can be safely fixed without human intervention.  If  e2fsck
  discovers  a  problem which may require the system administrator
  to take  additional  corrective  action,  e2fsck  will  print  a
  description  of the problem and then exit with the value 4 logi-
  cally or'ed into the exit code.  (See the  EXIT  CODE  section.)
  This  option  is normally used by the system's boot scripts.  It
  may not be specified at the same time as the -n or -y options.

OK but also mention that some items will be also printed along with
"IGNORED" and exit value 0.

# fsck -C -V -f -a /cf
fsck from util-linux 2.28
[/sbin/fsck.ext4 (1) -- /mnt/usb/cf] fsck.ext4 -f -a -C0 /dev/sdc2
Inode 65395 extent tree (at level 1) could be shorter.  IGNORED.
/dev/sdc2: 914/128016 files (1.4% non-contiguous), 73617/512000 blocks

To fix them one must use e.g., -y.

If one does not fix them they will just be printed the next time.

Bug#822281: lintian: support for Build-Depends-Arch & Build-Conflicts-Arch

[Mattia Rizzolo]

Package: lintian
Version: 2.5.43
Severity: wishlist
Tags: patch

so, I noticed that even if lintian has support in for B-D-A
actually it really doesn't deal with it, rising tags about unknown
fields instead of actually checking them.

Attached there is a first patch adding something for it.
I'm very bad at inventing names, and I'm sure you have better ideas for
the name of what I named
build-depends-arch-without-arch-dependant-binary :>

While pondering, keep in mind that dpkg has support for those since
2012, sbuild since 2011, but policy know nothing about it yet.  Also,
currently 5 packages only in the whole archive use B-D-A, but none uses
B-C-A.
No need to say, I'd like to use it, and split B-D into B-D-I+B-D-A
everywhere I can.

-- 
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  `-
From 4b3ffb48693c1698a7b1ae18c27bf1ce1a5ffe78 Mon Sep 17 00:00:00 2001
From: Mattia Rizzolo 
Date: Fri, 22 Apr 2016 22:36:41 +
Subject: [PATCH] first support for Build-Depends-Arch and Build-Conflicts-Arch

---
 checks/fields.desc  |  6 ++
 checks/fields.pm|  9 ++---
 data/common/source-fields   |  2 ++
 .../fields-dep-without-arch-dep-binary/debian/Makefile  |  5 +
 .../debian/debian/control.in| 17 +
 t/tests/fields-dep-without-arch-dep-binary/desc |  6 ++
 t/tests/fields-dep-without-arch-dep-binary/tags |  1 +
 7 files changed, 43 insertions(+), 3 deletions(-)
 create mode 100644 t/tests/fields-dep-without-arch-dep-binary/debian/Makefile
 create mode 100644 t/tests/fields-dep-without-arch-dep-binary/debian/debian/control.in
 create mode 100644 t/tests/fields-dep-without-arch-dep-binary/desc
 create mode 100644 t/tests/fields-dep-without-arch-dep-binary/tags

diff --git a/checks/fields.desc b/checks/fields.desc
index 8495abb..f187b9e 100644
--- a/checks/fields.desc
+++ b/checks/fields.desc
@@ -705,6 +705,12 @@ Ref: policy 7.7
 Info: The control file specifies source relations for architecture-independent
  packages, but no architecture-independent packages are built.
 
+Tag: build-depends-arch-without-arch-dependant-binary
+Severity: important
+Certainty: certain
+Info: The control file specifies source relations for architecture-dependant
+ packages, but not architecture-dependant packages are built.
+
 Tag: build-conflicts-with-build-dependency
 Severity: important
 Certainty: certain
diff --git a/checks/fields.pm b/checks/fields.pm
index ec86f84..aca887c 100644
--- a/checks/fields.pm
+++ b/checks/fields.pm
@@ -946,15 +946,18 @@ sub run {
 tag 'build-depends-indep-without-arch-indep'
   if (defined $info->field('build-depends-indep')
 && $arch_indep_packages == 0);
+tag 'build-depends-arch-without-arch-dependant-binary'
+  if (defined $info->field('build-depends-arch')
+&& $arch_dep_packages == 0);
 
 my $is_dep_field = sub {
-any { $_ eq $_[0] } qw(build-depends build-depends-indep);
+any { $_ eq $_[0] } qw(build-depends build-depends-indep build-depends-arch);
 };
 
 my $restrictions_used = 0;
 my %depend;
 for my $field (
-qw(build-depends build-depends-indep build-conflicts build-conflicts-indep)
+qw(build-depends build-depends-indep build-depends-arch build-conflicts build-conflicts-indep build-conflicts-arch)
   ) {
 if (defined $info->field($field)) {
 #Get data and clean it
@@ -1113,7 +1116,7 @@ sub run {
 }
 
 # Make sure build dependencies and conflicts are consistent.
-for ($depend{'build-conflicts'}, $depend{'build-conflicts-indep'}) {
+for ($depend{'build-conflicts'}, $depend{'build-conflicts-indep'}, $depend{'build-conflicts-arch'}) {
 next unless $_;
 for my $conflict (split /\s*,\s*/, $_) {
 if ($build_all->implies($conflict)) {
diff --git a/data/common/source-fields b/data/common/source-fields
index df1aa7d..8886812 100644
--- a/data/common/source-fields
+++ b/data/common/source-fields
@@ -6,8 +6,10 @@ autobuild
 binary
 bugs
 build-conflicts
+build-conflicts-arch
 build-conflicts-indep
 build-depends
+build-depends-arch
 build-depends-indep
 checksums-md5
 checksums-sha1
diff --git a/t/tests/fields-dep-without-arch-dep-binary/debian/Makefile b/t/tests/fields-dep-without-arch-dep-binary/debian/Makefile
new file mode 100644
index 000..6df56c1
--- /dev/null
+++ b/t/tests/fields-dep-without-arch-dep-binary/debian/Makefile
@@ -0,0 +1,5 @@
+all:
+
+install:
+	install -d -m 0755 

Bug#820995: jessie-pu: package lvm2/2.02.111-2.2

[Jonathan Wiltshire]

Control: tag -1 moreinfo d-i

On Thu, Apr 14, 2016 at 02:18:47PM +0200, Bastian Blank wrote:
> +lvm2 (2.02.111-3) UNRELEASED; urgency=medium
> +
> +  * Set default pid directory to /run. (closes: #783120)
> +
> + -- Bastian Blank   Thu, 14 Apr 2016 11:35:55 +
> +

Seems sensible, but the version should be 2.02.111-2+deb8u1, and the udeb
needs a d-i ack. Ccing Cyril.


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#822280: linux-image-4.5.0-1-amd64: No brightness control in Asus EEE Seashell netbook (worked in ver. 4.4.0)

[Oleg Shalaev]

Package: src:linux
Version: 4.5.1-1
Severity: minor

Brightness control works with older debian package linux-image-4.4.0-1-amd64.
It also works with my manually compiled kernel 4.4.6.
Before linux-image-4.5.0-1-amd64 appeared I tried to compile it manually, but I 
always had this brightness control problem.
Now I see that the same problem appears with the Debian 
linux-image-4.5.0-1-amd64 package,
so probably this is just a kernel bug.

-- Package-specific info:
** Version:
Linux version 4.5.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160409 (Debian 5.3.1-14) ) #1 SMP Debian 4.5.1-1 (2016-04-14)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.5.0-1-amd64 
root=UUID=d4981108-a8ca-478b-941d-ed56c1920b75 ro apparmor=1 security=apparmor

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[   13.976152] [drm] Initialized drm 1.1.0 20060810
[   14.005594] input: PC Speaker as /devices/platform/pcspkr/input/input10
[   14.227928] usbcore: registered new interface driver btusb
[   14.301997] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1c.0/:04:00.1/sound/card1/input11
[   14.307779] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1c.0/:04:00.1/sound/card1/input12
[   14.308429] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1c.0/:04:00.1/sound/card1/input13
[   14.308975] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1c.0/:04:00.1/sound/card1/input14
[   14.446137] asus_wmi: ASUS WMI generic driver loaded
[   14.479617] asus_wmi: Initialization: 0x0
[   14.479838] asus_wmi: BIOS WMI version: 0.8
[   14.480274] asus_wmi: SFUN value: 0x0
[   14.482428] input: Eee PC WMI hotkeys as 
/devices/platform/eeepc-wmi/input/input15
[   14.482992] asus_wmi: Number of fans: 1
[   14.559323] iTCO_vendor_support: vendor-support=0
[   14.703860] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   14.704180] iTCO_wdt: Found a NM10 TCO device (Version=2, TCOBASE=0x0860)
[   14.859116] media: Linux media interface: v0.10
[   14.875053] Linux video capture interface: v2.00
[   14.955974] nouveau :04:00.0: NVIDIA GT218 (0a8780b1)
[   14.974515] audit: type=1400 audit(1461357425.240:2): apparmor="STATUS" 
operation="profile_load" name="gst_plugin_scanner" pid=361 
comm="apparmor_parser"
[   14.995530] nouveau :04:00.0: bios: version 70.18.82.00.07
[   14.999083] nouveau :04:00.0: fb: 512 MiB DDR3
[   15.054684] [TTM] Zone  kernel: Available graphics memory: 1025922 kiB
[   15.054809] [TTM] Initializing pool allocator
[   15.054935] [TTM] Initializing DMA pool allocator
[   15.055085] nouveau :04:00.0: DRM: VRAM: 512 MiB
[   15.055200] nouveau :04:00.0: DRM: GART: 1048576 MiB
[   15.055321] nouveau :04:00.0: DRM: TMDS table version 2.0
[   15.055437] nouveau :04:00.0: DRM: DCB version 4.0
[   15.03] nouveau :04:00.0: DRM: DCB outp 00: 01000323 00010034
[   15.055672] nouveau :04:00.0: DRM: DCB outp 01: 02011300 
[   15.055790] nouveau :04:00.0: DRM: DCB outp 02: 02022362 00020010
[   15.055908] nouveau :04:00.0: DRM: DCB conn 00: 0040
[   15.056077] nouveau :04:00.0: DRM: DCB conn 01: 0100
[   15.056200] nouveau :04:00.0: DRM: DCB conn 02: 1261
[   15.074262] uvcvideo: Found UVC 1.00 device USB2.0 UVC VGA WebCam (13d3:5702)
[   15.088352] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   15.088488] [drm] Driver supports precise vblank timestamp query.
[   15.093298] uvcvideo 1-6:1.0: Entity type for entity Processing 2 was not 
initialized!
[   15.093520] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not 
initialized!
[   15.093729] uvcvideo 1-6:1.0: Entity type for entity Extension 4 was not 
initialized!
[   15.094296] input: USB2.0 UVC VGA WebCam as 
/devices/pci:00/:00:1d.7/usb1/1-6/1-6:1.0/input/input16
[   15.094818] usbcore: registered new interface driver uvcvideo
[   15.094975] USB Video Class driver (1.1.1)
[   15.161433] nouveau :04:00.0: DRM: MM: using COPY for buffer copies
[   15.504984] audit: type=1400 audit(1461357425.772:3): apparmor="STATUS" 
operation="profile_load" name="/usr/bin/irssi" pid=361 comm="apparmor_parser"
[   15.545678] audit: type=1400 audit(1461357425.812:4): apparmor="STATUS" 
operation="profile_load" name="/usr/bin/pidgin" pid=361 comm="apparmor_parser"
[   15.545954] audit: type=1400 audit(1461357425.812:5): apparmor="STATUS" 
operation="profile_load" name="launchpad_integration" pid=361 
comm="apparmor_parser"
[   15.546224] audit: type=1400 audit(1461357425.812:6): apparmor="STATUS" 
operation="profile_load" name="sanitized_helper" pid=361 comm="apparmor_parser"
[   15.597692] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   15.656753] audit: type=1400 audit(1461357425.924:7): apparmor="STATUS" 
operation="profile_load" name="/usr/bin/yandex-disk" pid=361 
comm="apparmor_parser"
[   15.990775] Adding 2096308k swap on /dev/sda2.  

Bug#821239: jessie-pu: package ledgersmb/1.3.47-1~deb8u1

[Jonathan Wiltshire]

Control: tag -1 moreinfo

On Sat, Apr 16, 2016 at 06:52:45PM -0400, Robert James Clay wrote:
> Please accept ledgersmb_1.3.47-1~deb8u1 for the next Jessie point release. It 
> resolves the issues with the current version of ledgersmb in 'jessie' 
> (1.3.40-1) of the package failing to complete an install without errors.

Could you expand on the details please? The proposed patch is 139K and:

 97 files changed, 1286 insertions(+), 623 deletions(-)

Quite a lot, and the changelog includes words like "New upstream release"
which immediately rings alarm bells.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#821877: python3.5.1-11 causes a 90 second delay to startup time on cinnamon desktop

[Christian Kastner]

On Wed, 20 Apr 2016 07:21:45 +0100 peter  wrote:
> using current installed version  3.5.1-10 of all the above my startup 
> time to
> login screen,
> as shown by the first line of systemd-analyze critical-chain is :
> graphical.target @2.918s
> 
> If I upgrade them all to version 3.5.1-11 my system boots to a black screen
> until eventually the login screen appears.
> The first line of systemd-analyze critical-chain now shows  : 
> graphical.target
> @1min 32.408s

FTR, this also seems to have affected autopkgtest, see #821778.



signature.asc
Description: OpenPGP digital signature

Bug#822279: kdenlive: missing dependency

[Thomas Perret]

Package: kdenlive
Version: 16.04.0-1
Severity: grave


This kdenlive version depends on qml-module-qtquick-controls which leads
to a segmentation fault at startup:

$ kdenlive
qrc:/qml/kdenliveclipmonitor.qml:2:1: module "QtQuick.Controls.Styles" is not 
installed
qrc:/qml/kdenliveclipmonitor.qml:1:1: module "QtQuick.Controls" is not installed
qrc:/qml/kdenliveclipmonitor.qml:2:1: module "QtQuick.Controls.Styles" is not 
installed
qrc:/qml/kdenliveclipmonitor.qml:1:1: module "QtQuick.Controls" is not installed
Erreur de segmentation

Manually installing the package solves the issue.


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

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

Versions of packages kdenlive depends on:
ii  ffmpeg7:3.0.1-3
ii  kded5 5.16.0-1
ii  kdenlive-data 16.04.0-1
ii  kinit 5.16.0-1
ii  kio   5.16.0-1
ii  libc6 2.22-7
ii  libgcc1   1:5.3.1-14
ii  libgl1-mesa-glx [libgl1]  11.1.3-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libkf5archive55.16.0-1
ii  libkf5attica5 5.16.0-1
ii  libkf5auth5   5.16.0-1
ii  libkf5bookmarks5  5.16.0-1
ii  libkf5codecs5 5.16.0-1
ii  libkf5completion5 5.16.0-1
ii  libkf5configcore5 5.16.0-1
ii  libkf5configgui5  5.16.0-1
ii  libkf5configwidgets5  5.16.0-1
ii  libkf5coreaddons5 5.16.0-1
ii  libkf5crash5  5.16.0-1
ii  libkf5dbusaddons5 5.16.0-1
ii  libkf5filemetadata3   5.16.0-1+b1
ii  libkf5guiaddons5  5.16.0-1
ii  libkf5i18n5   5.16.0-1
ii  libkf5iconthemes5 5.16.0-1
ii  libkf5itemviews5  5.16.0-1
ii  libkf5jobwidgets5 5.16.0-1
ii  libkf5kiocore55.16.0-1
ii  libkf5kiofilewidgets5 5.16.0-1
ii  libkf5kiontlm55.16.0-1
ii  libkf5kiowidgets5 5.16.0-1
ii  libkf5newstuff5   5.16.0-1
ii  libkf5notifications5  5.16.0-1
ii  libkf5notifyconfig5   5.16.0-1
ii  libkf5plotting5   5.16.0-1
ii  libkf5service-bin 5.16.0-1
ii  libkf5service55.16.0-1
ii  libkf5solid5  5.16.0-1
ii  libkf5sonnetui5   5.16.0-1
ii  libkf5textwidgets55.16.0-1
ii  libkf5widgetsaddons5  5.16.0-1
ii  libkf5xmlgui5 5.16.0-1
ii  libmlt++3 6.2.0-1
ii  libmlt6   6.2.0-1
ii  libqt5concurrent5 5.5.1+dfsg-16+b1
ii  libqt5core5a  5.5.1+dfsg-16+b1
ii  libqt5dbus5   5.5.1+dfsg-16+b1
ii  libqt5gui55.5.1+dfsg-16+b1
ii  libqt5network55.5.1+dfsg-16+b1
ii  libqt5qml55.5.1-3
ii  libqt5quick5  5.5.1-3
ii  libqt5script5 5.5.1+dfsg-2
ii  libqt5svg55.5.1-2
ii  libqt5widgets55.5.1+dfsg-16+b1
ii  libqt5xml55.5.1+dfsg-16+b1
ii  libstdc++65.3.1-14
ii  libv4l-0  1.10.0-2
ii  melt  6.2.0-1
ii  oxygen-icon-theme 4:4.14.0-1
ii  qml-module-qtquick2   5.5.1-3

Versions of packages kdenlive recommends:
ii  dvdauthor0.7.0-1.4+b1
ii  dvgrab   3.5-2+b3
ii  frei0r-plugins   1.4-3+b1
ii  genisoimage  9:1.1.11-3
ii  recordmydesktop  0.3.8.1+svn602-1+b1
ii  swh-plugins  0.4.15+1-8

Versions of packages kdenlive suggests:
pn  khelpcenter  

-- no debconf information

Bug#822229: jessie-pu: package autofs/5.0.8-2.1

[Jonathan Wiltshire]

Control: tag -1 confirmed

On Fri, Apr 22, 2016 at 11:22:59AM +0200, Salvatore Bonaccorso wrote:
> +autofs (5.0.8-2.1) jessie; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Remove macro debugging prints from macro_setenv (Closes: #755019)
> +
> + -- Salvatore Bonaccorso   Fri, 22 Apr 2016 10:34:58 +0200

The version is slightly unusual. I would normally suggest 5.0.8-2+deb8u1
even for an NMU, but I don't feel terribly strongly about it.

Please go ahead.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#822232: closed by m...@debian.org (Matteo F. Vescovi) (Bug#822232: fixed in gtkpod 2.1.5-2)

[John Paul Adrian Glaubitz]

Hi Matteo!

I think you took my advise too literally. I didn't mean you should
just apply the diff as you did [1] but just use the information
from the diff to update the symbols file.

Anyway, I'm attaching my debdiff which I actually forgot to provide
earlier today.

Cheers,
Adrian

> [1]
http://anonscm.debian.org/cgit/pkg-gtkpod/packages/gtkpod.git/commit/?id=511d70ede4bf09986b6a295b85480001b0b49775

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
diff -Nru gtkpod-2.1.5/debian/changelog gtkpod-2.1.5/debian/changelog
--- gtkpod-2.1.5/debian/changelog	2015-06-09 22:14:51.0 +0200
+++ gtkpod-2.1.5/debian/changelog	2016-04-22 13:42:58.0 +0200
@@ -1,3 +1,11 @@
+gtkpod (2.1.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/libatomicparsley0.symbols:
+- Update for sparc64. (Closes: #822232)
+
+ -- John Paul Adrian Glaubitz   Fri, 22 Apr 2016 13:41:53 +0200
+
 gtkpod (2.1.5-1) unstable; urgency=medium
 
   * New upstream stable release
diff -Nru gtkpod-2.1.5/debian/libatomicparsley0.symbols gtkpod-2.1.5/debian/libatomicparsley0.symbols
--- gtkpod-2.1.5/debian/libatomicparsley0.symbols	2015-06-09 21:52:00.0 +0200
+++ gtkpod-2.1.5/debian/libatomicparsley0.symbols	2016-04-22 13:41:40.0 +0200
@@ -1,4 +1,4 @@
-# SymbolsHelper-Confirmed: 0.0.1 alpha amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc ppc64 s390x sparc
+# SymbolsHelper-Confirmed: 0.0.1 alpha amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc ppc64 s390x sparc sparc64
 libatomicparsley.so.0 libatomicparsley0 #MINVER#
  AP_read_lyrics@Base 0.0.1
  AP_read_metadata@Base 0.0.1
@@ -33,8 +33,8 @@
  _Z13UTF8ToUTF16LEPhiPKhi@Base 0.0.1
  _Z13UTF8Toisolat1PhiPKhi@Base 0.0.1
  _Z13char4TOuint32jPc@Base 0.0.1
- (arch=alpha amd64 arm64 ia64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el s390x)_Z13char8TOuint64mPc@Base 0.0.1
- (arch=!alpha !amd64 !arm64 !ia64 !kfreebsd-amd64 !mips64 !mips64el !ppc64 !ppc64el !s390x)_Z13char8TOuint64yPc@Base 0.0.1
+ (arch=alpha amd64 arm64 ia64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el s390x sparc64)_Z13char8TOuint64mPc@Base 0.0.1
+ (arch=!alpha !amd64 !arm64 !ia64 !kfreebsd-amd64 !mips64 !mips64el !ppc64 !ppc64el !s390x !sparc64)_Z13char8TOuint64yPc@Base 0.0.1
  _Z13isolat1ToUTF8PhiPKhi@Base 0.0.1
  _Z13sha1_init_ctxP8sha1_ctx@Base 0.0.1
  _Z13sha1_read_ctxPK8sha1_ctxPv@Base 0.0.1
@@ -82,8 +82,8 @@
  _Z19UInt16FromBigEndianPKc@Base 0.0.1
  _Z19UInt32FromBigEndianPKc@Base 0.0.1
  _Z19UInt64FromBigEndianPKc@Base 0.0.1
- (arch=alpha amd64 arm64 ia64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el s390x)_Z20APar_AtomizeFileInfojjmPchhhjtP11uuid_vitals@Base 0.0.1
- (arch=!alpha !amd64 !arm64 !ia64 !kfreebsd-amd64 !mips64 !mips64el !ppc64 !ppc64el !s390x)_Z20APar_AtomizeFileInfojjyPchhhjtP11uuid_vitals@Base 0.0.1
+ (arch=alpha amd64 arm64 ia64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el s390x sparc64)_Z20APar_AtomizeFileInfojjmPchhhjtP11uuid_vitals@Base 0.0.1
+ (arch=!alpha !amd64 !arm64 !ia64 !kfreebsd-amd64 !mips64 !mips64el !ppc64 !ppc64el !s390x !sparc64)_Z20APar_AtomizeFileInfojjyPchhhjtP11uuid_vitals@Base 0.0.1
  _Z20APar_ExtractDataAtomi@Base 0.0.1
  _Z20APar_ExtractPicPrefsPc@Base 0.0.1
  _Z20APar_FindValueInAtomPcP8_IO_FILEsjj@Base 0.0.1


signature.asc
Description: OpenPGP digital signature

Bug#822278: espeak: not speaking german "umlaute" encoded with U+0308 COMBINING DIAERESIS correctly

[treaki]

Package: espeak
Version: 1.48.04+dfsg-1
Severity: important

hi,

I am using espeak a lot to hear text instead of reading it. Today i came across 
a 
problem that i have never heard before:

The german Umlaute (äöü) where spoken as (aou).

I then took a closer look and found out that in the text i was "reading" they 
weren't encoded the usual way (U+00E4, U+00F6, U+00FC) but with the usage of
U+0308 COMBINING DIAERESIS. (U+0061 and U+0308)

that leaded into not right pronouncing of this letters.

I would appreciate if you could fix that issue so that we would hear this 
things pronounced the right way.

thanks in advance

treaki

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

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

Versions of packages espeak depends on:
ii  libc6   2.19-18+deb8u4
ii  libespeak1  1.48.04+dfsg-1
ii  libgcc1 1:4.9.2-10
ii  libstdc++6  4.9.2-10

espeak recommends no packages.

espeak suggests no packages.

-- no debconf information

Bug#822174: exim4: Please add hosts_require_tls = REMOTE_SMTP_SMARTHOST_HOSTS_REQUIRE_TLS

[Marc Haber]

On Fri, Apr 22, 2016 at 01:31:33PM +0200, Samuel Thibault wrote:
> Marc Haber, on Fri 22 Apr 2016 12:53:59 +0200, wrote:
> > On Thu, Apr 21, 2016 at 10:06:38PM +0200, Samuel Thibault wrote:
> > > Due to network hickups, some of my mails couldn't go through TLS to my
> > > smarthost, and exim4 reverted to an unencrypted send:
> > > 
> > > 2016-04-16 10:39:58 1arJcE-00020M-Cx H=sonata.ens-lyon.org 
> > > [140.77.166.138] TLS error on connection (gnutls_handshake): timed out
> > > 2016-04-16 10:39:58 1arJcE-00020M-Cx TLS session failure: delivering 
> > > unencrypted to sonata.ens-lyon.org [140.77.166.138] (not in 
> > > hosts_require_tls)
> > > 
> > > But this got rejected by the smarthost:
> > > 
> > > 2016-04-16 10:40:06 1arJcE-00020M-Cx ** d...@mielke.cc R=smarthost 
> > > T=remote_smtp_smarthost H=sonata.ens-lyon.org [140.77.166.138]: SMTP 
> > > error from remote mail server after MAIL 
> > > FROM: SIZE=1944: 530 5.7.0 Must issue a 
> > > STARTTLS command first
> > 
> > Ouch. The smarthost sohuldn't advertise AUTH capabilities before
> > STARTTLS if it doesn't want to authenticate in clear text.
> 
> Well, no, it doesn't:
> 
> brl$ telnet smtp.ens-lyon.org 587
> Trying 140.77.166.138...
> Connected to sonata.ens-lyon.org.
> Escape character is '^]'.
> 220 sonata.ens-lyon.org ESMTP Postfix (Debian/GNU)
> ehlo brl.thefreecat.org 
> 250-sonata.ens-lyon.org
> 250-PIPELINING
> 250-SIZE 5120
> 250-VRFY
> 250-ETRN
> 250-STARTTLS
> 250-ENHANCEDSTATUSCODES
> 250-8BITMIME
> 250 DSN
> auth
> 530 5.7.0 Must issue a STARTTLS command first

Ah. Exim shouldnt try authenticating then. But the Postfix there gives
the same answer to a MAIL FROM, which is probably the case here.

The workaround given in my first question would still be valid though.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#822277: gdk-pixbuf is not binNMU safe and becomes uninstallable on every package update

[Matthias Klose]

Package: src:gdk-pixbuf
Version: 2.34.0-1
Severity: important

$ apt-cache show libgdk-pixbuf2.0-0|grep Depends
Depends: libgdk-pixbuf2.0-common (= 2.34.0-1)

In this form the package cannot be binNMUed, and packages build-depending on 
libgdk-pixbuf2.0-0 are not buildable until all architectures are in sync again, 
delaying builds like gcc or openjdk.  Please consider relaxing this dependency 
or making the -common package Arch: any.

Bug#822276: epiphany-browser: Selected text and controls not visible

[Michael Biebl]

Am 22.04.2016 um 23:59 schrieb Pr0metheus:
> Package: epiphany-browser
> Version: 3.20.1-1
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
> After upgrading to Gnome 3.20 (from 3.18) selected text and controls
> (like check boxes and radio buttons) are not visible on web pages.
> 
> 
> * Suggested solution from #gnome (IRC)
> 
> Compile epiphany-browser against GTK v3.20 and NOT against 3.18 as it
> is now.

epiphany has been compiled against gtk 3.20.
The problem most likely is that webkit2 is compiled against gtk 3.18.




-- 
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#822271: gnome-control-center: No touchpad section in mouse settings

[Michael Biebl]

Hi Giacomo!

Am 22.04.2016 um 22:25 schrieb Giacomo Mulas:
> Package: gnome-control-center
> Version: 1:3.20.1-1
> Severity: normal
> 
> Dear Maintainer,
> 
> with the transition to gnome 3.20 the possibility to enable tap-clicking,
> middle button emulation, and/or any other multitouch or zone-related
> behaviour of the touchpad was lost.  The gnome-control-center mouse/touchpad
> properties do not show anything about it, and not even the gnome-tweak-tool
> permits to enable/disable these features. I even tried to set them by hand 
> using gconf-editor, but the new gnome version seems to ignore whatever I 
> may set in desktop/gnome/peripherals/touchpad.
> 
> Of course, all of this worked perfectly with the 3.18 gnome version.
> Why on earth are gnome developers taking out functionality and/or 
> configurability with each new release?


Do you have xserver-xorg-input-libinput installed? If not, please do.

Related to that is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821354
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821352

-- 
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#822276: epiphany-browser: Selected text and controls not visible

[Pr0metheus]

Package: epiphany-browser
Version: 3.20.1-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

After upgrading to Gnome 3.20 (from 3.18) selected text and controls
(like check boxes and radio buttons) are not visible on web pages.


* Suggested solution from #gnome (IRC)

Compile epiphany-browser against GTK v3.20 and NOT against 3.18 as it
is now.



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

Kernel: Linux 4.5.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 epiphany-browser depends on:
ii  dbus-x11 1.10.8-1
ii  epiphany-browser-data3.20.1-1
ii  gnome-icon-theme 3.12.0-1
ii  gnome-icon-theme-symbolic3.12.0-1
ii  gsettings-desktop-schemas3.20.0-3
ii  iso-codes3.67-1
ii  libatk1.0-0  2.20.0-1
ii  libavahi-client3 0.6.32~rc+dfsg-1
ii  libavahi-common3 0.6.32~rc+dfsg-1
ii  libavahi-gobject00.6.32~rc+dfsg-1
ii  libc62.22-7
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libgck-1-0   3.20.0-2
ii  libgcr-base-3-1  3.20.0-2
ii  libgcr-ui-3-13.20.0-2
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.0-1
ii  libgnome-desktop-3-123.20.1-1
ii  libgtk-3-0   3.20.3-1
ii  libjavascriptcoregtk-4.0-18  2.12.1-1
ii  libnotify4   0.7.6-2
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.23-2
ii  libp11-kit0  0.23.2-3
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libsecret-1-00.18.5-1
ii  libsoup2.4-1 2.54.0.1-1
ii  libsqlite3-0 3.12.2-1
ii  libwebkit2gtk-4.0-37 2.12.1-1
ii  libwnck-3-0  3.14.1-2
ii  libx11-6 2:1.6.3-1
ii  libxml2  2.9.3+dfsg1-1
ii  libxslt1.1   1.1.28-2.1

Versions of packages epiphany-browser recommends:
ii  ca-certificates  20160104
ii  evince   3.20.0-1
ii  yelp 3.20.1-1

epiphany-browser suggests no packages.

-- no debconf information

Bug#803275: yt: FTBFS: tests fail on several architectures

[Aaron M. Ucko]

notfixed 803275 3.2.1-2.2
found 803275 3.2.1-2.2
thanks

"Aaron M. Ucko"  writes:

> Thanks for fixing yt's Build-Depends setting!  Automated builds are
> doing better, but several have failed with test suite errors, and I
> suspect more will follow.  Could you please take a look?  You can find
> the logs at https://buildd.debian.org/status/logs.php?pkg=yt=3.2.1-2 .

Per https://buildd.debian.org/status/logs.php?pkg=yt=3.2.1-2.2 ,
there are still test suite errors (except on architectures that were
already okay, at least so far).  Could you please take another look?

Thanks!

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

Bug#822275: RFP: crystal -- Compiler of the Crystal object-oriented programming language

[Luc Sarzyniec]

Package: wnpp
Severity: wishlist

* Package name: crystal
  Version : 0.15.0
  Upstream Author : Manas Technology Solutions 
* URL : http://crystal-lang.org/
* License : Apache-2.0
  Programming Lang: Crystal
  Description : Compiler of the Crystal object-oriented programming language


 The Crystal's language syntax is inspired by Ruby, the language is statically
 type-checked but does not require that the type of variables or method
 arguments be specified.

The project's sources are hosted on GitHub [0].

I started to work on the Debian packaging of the project [1], but I still have
some issues to address. The first one: the compiler is written in Crystal so
crystal has to be specified in the package's build dependencies - I don't
really know how to handle it. This work may be used as a base to build
something cleaner.

> More information from the website:
"Crystal is a programming language with the following goals:
* Have the same syntax as Ruby, or at least as similar as possible.
* Statically type-checked but without having to specify the type of
variables or method arguments.
* Be able to call C code by writing bindings to it in Crystal.
* Have compile-time evaluation and generation of code, to avoid
boilerplate code.
* Compile to efficient native code.

Why?

We love Ruby's efficiency for writing code.
We love C's efficiency for running code.
We want the best of both worlds.
We want the compiler to understand what we mean without having to
specify types everywhere.
We want full OOP.
Oh, and we don't want to write C code to make the code run faster.

Status
--
* The project is in alpha stage: we are still tweaking the language
and standard library.
* The compiler is written in Crystal."


Links:
  [0] https://github.com/crystal-lang/crystal
  [1] https://github.com/olbat/debian-crystal
  [2] http://xmailserver.org/libpcl.html
  [3] https://tracker.debian.org/pkg/libpcl1

Bug#822274: golang-github-hpcloud-tail: FTBFS in unstable: cannot find package "golang.org/x/sys/unix"

[Santiago Vila]

Package: golang-github-hpcloud-tail
Version: 1.0.0+git20160415.b294095-1
Severity: serious

Dear maintainer:

This package fails to build from source in unstable:
--
 go install -v github.com/hpcloud/tail github.com/hpcloud/tail/cmd/gotail 
github.com/hpcloud/tail/ratelimiter github.com/hpcloud/tail/util 
github.com/hpcloud/tail/watch
src/gopkg.in/fsnotify.v1/inotify.go:19:2: cannot find package 
"golang.org/x/sys/unix" in any of:
  /usr/lib/go/src/golang.org/x/sys/unix (from $GOROOT)
  
/<>/golang-github-hpcloud-tail-1.0.0+git20160415.b294095/obj-x86_64-linux-gnu/src/golang.org/x/sys/unix
 (from $GOPATH)
 dh_auto_build: go install -v github.com/hpcloud/tail 
github.com/hpcloud/tail/cmd/gotail github.com/hpcloud/tail/ratelimitr 
github.com/hpcloud/tail/util github.com/hpcloud/tail/watch returned exit code 1
--

The build was made on a virtual machine running stretch with sbuild
and a sid chroot. The full build log is attached.

Thanks.

golang-github-hpcloud-tail_1.0.0+git20160415.b294095-1_amd64-20160422-2328.gz
Description: application/gzip

Bug#821834: wheezy-pu: package libcrypto++/5.6.1-6+deb7u2

[Adam D. Barratt]

Control: tags -1 + pending

On Tue, 2016-04-19 at 22:03 +0200, László Böszörményi wrote:
> On Tue, Apr 19, 2016 at 9:27 PM, Adam D. Barratt
>  wrote:
> > Control: tags -1 + confirmed
> >
> > On Tue, 2016-04-19 at 19:19 +0200, László Böszörményi wrote:
> >> There's a vulnerability in Crypto++, the C++ class library of
> >> cryptographic schemes.
> [...]
> > Please go ahead.
>  Thanks, just uploaded.

Flagged for acceptance.

Regards,

Adam

Bug#821757: wheezy-pu: package xapian-core/1.2.12-2

[Adam D. Barratt]

Control: tags -1 + pending

On Tue, 2016-04-19 at 23:13 +0100, Olly Betts wrote:
> On Tue, Apr 19, 2016 at 08:47:15PM +0100, Adam D. Barratt wrote:
> > Please go ahead.
> 
> Thanks, now uploaded.

Flagged for acceptance.

Regards,

Adam

Bug#822218: [pkg-go] Bug#822218: Please update to latest upstream release 0.3.3

[Potter, Tim (HPE Linux Support)]

On 23 Apr 2016, at 7:23 AM, Dmitry Smirnov  wrote:
> 
> On Friday, 22 April 2016 5:23:27 AM AEST Potter, Tim (HPE Linux Support)
> wrote:
>> I've already pushed a change to alioth for this - all it needs is a review
>> and upload.
> 
> Tim, when packaging new upstream releases please always remember to compare
> last and new tarballs, file by file and update "copyright" file accordingly.

OK - will add that to my checklist.

> Also I'd love to see package name in subjects of "Please update to latest
> upstream release" bugs...

I thought that the BTS did that, but obviously not.

Thanks for the tips!


Tim.

> 
> Thanks.
> 
> --
> Cheers,
> Dmitry Smirnov.
> 
> ---
> 
> I hate all sports as rabidly as a person who likes sports hates common
> sense.
>-- H. L. Mencken



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#822258: Pending fixes for bugs in the rkt package

[pkg-go-maintainers]

tag 822258 + pending
thanks

Some bugs in the rkt package are closed in revision
6677532bc8517e4a4fc896e4f5bd9e2ac073f04b in branch 'master' by Dmitry
Smirnov

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/rkt.git/commit/?id=6677532

Commit message:

Promoted "systemd-container" to Depends (Closes: #822258).

Bug#822265: apt-listbugs does not properly handle backports

[Francesco Poli]

On Fri, 22 Apr 2016 20:05:08 +0200 Rainer Dorsch wrote:

> Package: apt-listbugs
> Version: 0.1.16
> Severity: normal
> 
> Dear Maintainer,

Hello Rainer,
thanks for your bug report!

> 
> I updated libreoffice from jessie-backports recently. apt-listbugs listed 
> #820657 as 
> critical bug, which is supposed to be solved in version libreoffice/1:5.1.2-3.
> The installation candidate was 1:5.1.2-3~bpo8+1, i.e. the version in which 
> the bug was
> solved.

Mmmmh, this is caused by the fact that version 1:5.1.2-3~bpo8+1 is
meant to be considered (and is indeed considered) as earliest than
version 1:5.1.2-3 ...

  $ dpkg --compare-versions 1:5.1.2-3~bpo8+1 lt 1:5.1.2-3 && echo yes
  yes

Back-port versions are built this way, in order to keep the upgrade
path safe [1][2].

[1] http://backports.debian.org/FAQ/
[2] https://www.debian.org/doc/debian-policy/footnotes.html#f37

So, in a sense, the issue you experienced could be considered as
inherent in the back-port policy.


Maybe some special handling of back-port version numbers could be
introduced in apt-listbugs, but I have to think about it a little bit.
I would like to avoid introducing some subtle bug, by messing up with
the version compare rules.

I'll let you know, after I make up my mind.

Bye.

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


pgpf5lBuVMWOg.pgp
Description: PGP signature

Bug#822218: [pkg-go] Bug#822218: Please update to latest upstream release 0.3.3

[Dmitry Smirnov]

On Friday, 22 April 2016 5:23:27 AM AEST Potter, Tim (HPE Linux Support) 
wrote:
> I've already pushed a change to alioth for this - all it needs is a review
> and upload.

Tim, when packaging new upstream releases please always remember to compare 
last and new tarballs, file by file and update "copyright" file accordingly.

Also I'd love to see package name in subjects of "Please update to latest 
upstream release" bugs...

Thanks.

-- 
Cheers,
 Dmitry Smirnov.

---

I hate all sports as rabidly as a person who likes sports hates common
sense.
-- H. L. Mencken


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

Bug#822164: golang-google-api: please update google-api-go-client

[Daniel Stender]

Tim Potter already prepared a new snapshot (20160408.9737cc9).

ratt run:

$ ratt -sbuild_dist unstable golang-google-api_0.0~git20160408-1_amd64.changes 
2016/04/22 22:12:57 Loading changes file 
"golang-google-api_0.0~git20160408-1_amd64.changes"
2016/04/22 22:12:57  - 1 binary packages: golang-google-api-dev
2016/04/22 22:12:57  - corresponding .debs (will be injected when building):
2016/04/22 22:12:57 golang-google-api-dev_0.0~git20160408-1_all.deb
2016/04/22 22:13:00 Figuring out reverse build dependencies using dose-ceve(1). 
This might take a while
2016/04/22 22:13:00 dose-ceve(1) failed (exec: "dose-ceve": executable file not 
found in $PATH), falling back to interpreting Sources directly
2016/04/22 22:13:00 Loading sources index 
"/var/lib/apt/lists/ftp.de.debian.org_debian_dists_unstable_main_source_Sources"
2016/04/22 22:13:02 Loading sources index 
"/var/lib/apt/lists/ftp.de.debian.org_debian_dists_unstable_contrib_source_Sources"
2016/04/22 22:13:02 Loading sources index 
"/var/lib/apt/lists/ftp.de.debian.org_debian_dists_unstable_non-free_source_Sources"
2016/04/22 22:13:02 Building golang-github-jacobsa-gcloud_0.0~git20150709-1 
(commandline: [sbuild --arch-all --dist=unstable --nolog 
golang-github-jacobsa-gcloud_0.0~git20150709-1 
--extra-package=golang-google-api-dev_0.0~git20160408-1_all.deb])
2016/04/22 22:13:39 Building 
golang-github-seandolphin-bqschema_0.0~git20150424.0.f92a08f-1 (commandline: 
[sbuild --arch-all --dist=unstable --nolog 
golang-github-seandolphin-bqschema_0.0~git20150424.0.f92a08f-1 
--extra-package=golang-google-api-dev_0.0~git20160408-1_all.deb])
2016/04/22 22:13:48 building 
golang-github-seandolphin-bqschema_0.0~git20150424.0.f92a08f-1 failed: exit 
status 3
2016/04/22 22:13:48 Building cadvisor_0.22.2+dfsg-1 (commandline: [sbuild 
--arch-all --dist=unstable --nolog cadvisor_0.22.2+dfsg-1 
--extra-package=golang-google-api-dev_0.0~git20160408-1_all.deb])
2016/04/22 22:15:20 Building fleet_0.11.7+dfsg1-1 (commandline: [sbuild 
--arch-all --dist=unstable --nolog fleet_0.11.7+dfsg1-1 
--extra-package=golang-google-api-dev_0.0~git20160408-1_all.deb])
2016/04/22 22:16:39 Build results:
2016/04/22 22:16:39 PASSED: cadvisor_0.22.2+dfsg-1
2016/04/22 22:16:39 PASSED: fleet_0.11.7+dfsg1-1
2016/04/22 22:16:39 PASSED: golang-github-jacobsa-gcloud_0.0~git20150709-1
2016/04/22 22:16:39 FAILED: 
golang-github-seandolphin-bqschema_0.0~git20150424.0.f92a08f-1 (see 
buildlogs/golang-github-seandolphin-bqschema_0.0~git20150424.0.f92a08f-1)


The single fail of golang-github-seandolphin-bqschema comes from that: 
https://bugs.debian.org/822273 (ratt: please include --resolve-alternatives 
switch)

With a local hack and it's allright:

2016/04/22 22:55:42 Building fleet_0.11.7+dfsg1-1 (commandline: [sbuild 
--arch-all --resolve-alternatives --dist=unstable --nolog fleet_0.11.7+dfsg1-1 
--extra-package=golang-google-api-dev_0.0~git20160408-1_all.deb])
2016/04/22 22:56:55 Building golang-github-jacobsa-gcloud_0.0~git20150709-1 
(commandline: [sbuild --arch-all --resolve-alternatives --dist=unstable --nolog 
golang-github-jacobsa-gcloud_0.0~git20150709-1 
--extra-package=golang-google-api-dev_0.0~git20160408-1_all.deb])
2016/04/22 22:57:35 Building 
golang-github-seandolphin-bqschema_0.0~git20150424.0.f92a08f-1 (commandline: 
[sbuild --arch-all --resolve-alternatives --dist=unstable --nolog 
golang-github-seandolphin-bqschema_0.0~git20150424.0.f92a08f-1 
--extra-package=golang-google-api-dev_0.0~git20160408-1_all.deb])
2016/04/22 22:58:07 Building cadvisor_0.22.2+dfsg-1 (commandline: [sbuild 
--arch-all --resolve-alternatives --dist=unstable --nolog 
cadvisor_0.22.2+dfsg-1 
--extra-package=golang-google-api-dev_0.0~git20160408-1_all.deb])
2016/04/22 22:59:25 Build results:
2016/04/22 22:59:25 PASSED: 
golang-github-seandolphin-bqschema_0.0~git20150424.0.f92a08f-1
2016/04/22 22:59:25 PASSED: cadvisor_0.22.2+dfsg-1
2016/04/22 22:59:25 PASSED: fleet_0.11.7+dfsg1-1
2016/04/22 22:59:25 PASSED: golang-github-jacobsa-gcloud_0.0~git20150709-1


I'm going to upload this as team upload.

DS

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

Bug#819658: jessie-pu: package hexchat/2.10.1-1

[Jonathan Wiltshire]

Control: tag -1 confirmed

On Mon, Apr 11, 2016 at 01:26:45PM -0600, Jesse Rhodes wrote:
> After discussion in IRC, I now understand that a bug can be closed
> more than once, which seems a little counter-intuitive at first, but I
> get why.
> Here's the updated debdiff with the bug close included. Hopefully this
> is the final one. Apologies for the extra noise.

This bit confused me a bit:

+ struct chiper_info {
+ char version[16];
+-char chiper[24];
++char chiper[48];
+ int chiper_bits;
+ };

I assume this is cipher stuff. At least there is consistency, I suppose.

Please go ahead.


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#816796: php-apigen: Useless in Debian

[David Prévot]

Hi Florian,

Le 22/04/2016 à 16:09, Florian Schlichting a écrit :
> On Wed, Apr 20, 2016 at 04:00:40PM -0400, David Prévot wrote:
>> Le 20/04/2016 à 15:43, Florian Schlichting a écrit
>>> So if it's not too difficult to maintain with PHP 7, I'd love for
>>> php-apigen to be kept in Debian in the future!
>>
>> Feel free to take it over (with its dependency chain).
> 
> OK, I'll have a look at php-apigen and dependencies, preparing updates
> for PHP 7. Can I keep you in Uploaders, or would you rather be removed?

Please, remove me (I’m still around the team, and willing to help for
general or specific issues, but don’t wish to be part of the main
contacts for packages I don’t use anymore).

> I may need a hand or
> helpful hint getting used to the pkg-php tools, though, so if you see me
> doing something stupid please do tell!

The  should be the good place to
ask for advice in doubt, I won’t the only one willing to help.

> I have requested to join pkp-php on alioth.

I’m not an admin, but those are usually dealt with in a timely manner,
so welcome!

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#818528: madplay: diff for NMU version 0.15.2b-8.1

[Paul Gevers]

Control: tags 818528 + patch
Control: tags 818528 + pending

Dear maintainer,

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

Regards.
diff -u madplay-0.15.2b/debian/rules madplay-0.15.2b/debian/rules
--- madplay-0.15.2b/debian/rules
+++ madplay-0.15.2b/debian/rules
@@ -8,7 +8,7 @@
 DEB_AUTO_UPDATE_AUTOHEADER:=1.11
 DEB_AUTO_UPDATE_AUTOMAKE:=1.11
 DEB_AUTO_UPDATE_AUTOCONF:=yes
-DEB_AUTOMAKE_ARGS:=--foreign
+DEB_AUTOMAKE_ARGS:=--foreign --add-missing

 include /usr/share/cdbs/1/rules/buildcore.mk
 include /usr/share/cdbs/1/rules/debhelper.mk
diff -u madplay-0.15.2b/debian/changelog madplay-0.15.2b/debian/changelog
--- madplay-0.15.2b/debian/changelog
+++ madplay-0.15.2b/debian/changelog
@@ -1,3 +1,10 @@
+madplay (0.15.2b-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS by --add-missing to automake call (Closes: #818528)
+
+ -- Paul Gevers   Fri, 22 Apr 2016 21:58:24 +0200
+
 madplay (0.15.2b-8) unstable; urgency=high

   * Fix buffer overflow in the alsa output code (Closes: #619341)



signature.asc
Description: OpenPGP digital signature

Bug#822273: ratt: please include --resolve-alternatives switch

[Daniel Stender]

Package: ratt
Version: 0.0~git20150816.0.b060319-1
Severity: wishlist

Hi Michael,

could you please include the --resolve-alternatives switch for Sbuild 
(optional? could
pass sbuild switches in general?), there are packages which have alternative 
build-deps
like golang-github-seandolphin-bqschema [1], which fail in the test builds 
because
of that.

Thanks,
Daniel

[1] 
https://sources.debian.net/src/golang-github-seandolphin-bqschema/0.0~git20150424.0.f92a08f-1/debian/control/

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

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

Versions of packages ratt depends on:
ii  libc6  2.22-6

ratt recommends no packages.

ratt suggests no packages.

-- no debconf information

Bug#820059: jessie-pu: package xapian-core/1.2.19-1

[Adam D. Barratt]

Control: tags -1 + pending

On Tue, 2016-04-19 at 23:12 +0100, Olly Betts wrote:
> On Tue, Apr 19, 2016 at 08:38:11PM +0100, Adam D. Barratt wrote:
> > Please go ahead.
> 
> Thanks, now uploaded.

Flagged for acceptance.

Regards,

Adam

Bug#819797: jessie-pu: package libreoffice/1:4.3.3-2+deb8u2

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2016-04-17 at 13:50 +0200, Rene Engelhard wrote:
> Hi,
> 
> On Sat, Apr 16, 2016 at 07:17:33PM +0100, Adam D. Barratt wrote:
> > It wasn't really very clear from your original report when the openjdk
> > change happened, particularly given how recently #819375 was filed.
> 
> Sure. Because I didn't exactly know either. :)
> 
> That's exactly why I rechecked with a "standard" stable.
> 
> > Anyway, thanks for confirming; please feel free to upload.
> 
> OK, running.

Flagged for acceptance.

Regards,

Adam

Bug#821326: jessie-pu: package initramfs-tools/0.120+deb8u2

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2016-04-17 at 18:56 +0100, Ben Hutchings wrote:
> This update fixes:
> 
> - Regression when upgrading Linux to version 4.4+ if / or /usr is on
>   an NVMe device (#807000)
> - Regression in version 0.119 if there are non-scripts (such as
>   .svn directories) under /etc/initramfs-tools/scripts (#814965)
> 
> Both of these regressions cause boot failure on the affected systems.

Flagged for acceptance.

Regards,

Adam

Bug#821835: jessie-pu: package libcrypto++/5.6.1-6+deb8u2

[Adam D. Barratt]

Control: tags -1 + pending

On Tue, 2016-04-19 at 22:28 +0200, László Böszörményi wrote:
> On Tue, Apr 19, 2016 at 9:27 PM, Adam D. Barratt
>  wrote:
> > Control: tags -1 + confirmed
> >
> > On Tue, 2016-04-19 at 19:19 +0200, László Böszörményi wrote:
> >> There's a vulnerability in Crypto++, the C++ class library of
> >> cryptographic schemes.
> [...]
> > Please go ahead.
>  Just uploaded the package.

Flagged for acceptance.

Regards,

Adam

Bug#821205: jessie-pu: package gitolite3/3.6.1-2

[Adam D. Barratt]

Control: tags -1 + pending

On Tue, 2016-04-19 at 20:40 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sat, 2016-04-16 at 13:24 -0300, David Bremner wrote:
> > This is a fix for a missing functionality bug (819841) in jessie.  The
> > fix has been in several subsequent upstream releases, so it should be
> > safe, even if it does involve regex-soup.
> 
> As regex-soup goes, that's fairly clean. :-)
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#820540: jessie-pu: package bareos/14.2.1+20141017gitc6c5b56-3+deb8u2

[Adam D. Barratt]

Control: tags -1 + pending

On Tue, 2016-04-19 at 20:44 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sat, 2016-04-09 at 18:32 +0200, Felix Geyer wrote:
> > I'd like to update bareos in jessie to fix bug #819807 (TLS completely 
> > broken).
> > This involves backporting 3 commits from upstream.
> > Similar changes are in the 14.2.6-3 upload but for jessie another 
> > backported commit
> > is necessary.
> > 
> > The debdiff is attached. Most of the diff is the addition of tls 
> > autopkgtests.
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#822272: aptitude: No more forgets reinstallation instruction after reinstallation has happened

[Axel Beckert]

Package: aptitude
Version: 0.8-1
Severity: normal

If I select a package for reinstallation by pressing "L" in the TUI and
then press 2x "g", the package will be reinstalled.

Afterwards at "Press Return to continue, 'q' followed by Return to
quit."  I press  (not Ctrl-C) and it still lists that package for
reinstallation.

-- Package-specific info:
Terminal: eterm-color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8
Compiler: g++ 5.3.1 20160409
Compiled against:
  apt version 5.0.0
  NCurses version 6.0
  libsigc++ version: 2.8.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20160319
  cwidget version: 0.5.17
  Apt version: 5.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffd84b48000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f8c2dfbf000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f8c2dd8f000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f8c2db64000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f8c2d95d000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f8c2d66)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f8c2d365000)
libboost_iostreams.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.58.0 (0x7f8c2d14b000)
libboost_filesystem.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.58.0 (0x7f8c2cf32000)
libboost_system.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.58.0 (0x7f8c2cd2d000)
libxapian.so.22 => /usr/lib/x86_64-linux-gnu/libxapian.so.22 
(0x7f8c2c929000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f8c2c70c000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f8c2c39)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f8c2c092000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f8c2be7c000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f8c2bad7000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7f8c2b8d4000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8c2b6d)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f8c2b4b8000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f8c2b29d000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f8c2b08d000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f8c2ae69000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f8c2ac57000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f8c2aa4e000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f8c2a849000)
/lib64/ld-linux-x86-64.so.2 (0x5586b9272000)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common0.8-1
ii  libapt-pkg5.0  1.2.10
ii  libboost-filesystem1.58.0  1.58.0+dfsg-5+b1
ii  libboost-iostreams1.58.0   1.58.0+dfsg-5+b1
ii  libboost-system1.58.0  1.58.0+dfsg-5+b1
ii  libc6  2.22-7
ii  libcwidget3v5  0.5.17-4+b1
ii  libgcc11:5.3.1-14
ii  libncursesw5   6.0+20160319-1
ii  libsigc++-2.0-0v5  2.8.0-1
ii  libsqlite3-0   3.12.2-1
ii  libstdc++6 5.3.1-14
ii  libtinfo5  6.0+20160319-1
ii  libxapian22v5  1.2.23-1

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-8
ii  sensible-utils 0.0.9

Versions of packages aptitude suggests:
ii  apt-xapian-index0.47+nmu2
ii  aptitude-doc-en [aptitude-doc]  0.8-1
ii  debtags 2.0.2
ii  tasksel 3.34

-- no debconf information

Bug#822266: paraview: FTBFS on kfreebsd-* but previously did: dilib.c:5462:18: error: storage size of 'mytime' isn't known

[Mattia Rizzolo]

On Fri, Apr 22, 2016 at 08:50:51PM +0200, Tobias Frost wrote:
> Relevant snippet:
> 
> /«BUILDDIR»/paraview-5.0.1+dfsg1/Plugins/CDIReader/cdilib.c:5277:62: warning: 
> macro "__DATE__" might prevent reproducible builds [-Wdate-time]
>  static const char file_libvers[] = STRING(LIBVERSION) " of " __DATE__ " " 
> __TIME__;
>   ^
> /«BUILDDIR»/paraview-5.0.1+dfsg1/Plugins/CDIReader/cdilib.c:5277:75: warning: 
> macro "__TIME__" might prevent reproducible builds [-Wdate-time]
>  static const char file_libvers[] = STRING(LIBVERSION) " of " __DATE__ " " 
> __TIME__;
>^
> /«BUILDDIR»/paraview-5.0.1+dfsg1/Plugins/CDIReader/cdilib.c: In function 
> 'file_time':

this is not the failure, it's actually a line below :)

/«BUILDDIR»/paraview-5.0.1+dfsg1/Plugins/CDIReader/cdilib.c: In function 
'file_time':
/«BUILDDIR»/paraview-5.0.1+dfsg1/Plugins/CDIReader/cdilib.c:5462:18: error: 
storage size of 'mytime' isn't known
   struct timeval mytime;
  ^

anyway yes, it wouldn't be bad to patch out __DATE__ __TIME__ and
improve reproducibility of this package (looks like there are also other
bits that prever full reproducibility, ftr).

> I'm trying to find a patch for this, and if successful, I will NMU it.

Consider give some time to the maintainer, gladk is usually very quick
at uploading new releases when asked to :)

-- 
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#822271: gnome-control-center: No touchpad section in mouse settings

[Giacomo Mulas]

Package: gnome-control-center
Version: 1:3.20.1-1
Severity: normal

Dear Maintainer,

with the transition to gnome 3.20 the possibility to enable tap-clicking,
middle button emulation, and/or any other multitouch or zone-related
behaviour of the touchpad was lost.  The gnome-control-center mouse/touchpad
properties do not show anything about it, and not even the gnome-tweak-tool
permits to enable/disable these features. I even tried to set them by hand 
using gconf-editor, but the new gnome version seems to ignore whatever I 
may set in desktop/gnome/peripherals/touchpad.

Of course, all of this worked perfectly with the 3.18 gnome version.
Why on earth are gnome developers taking out functionality and/or 
configurability with each new release?

Thanks in advance
Giacomo Mulas


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

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

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.40-3
ii  apg2.2.3.dfsg.1-3
ii  colord 1.3.2-1
ii  desktop-file-utils 0.22-1
ii  gnome-control-center-data  1:3.20.1-1
ii  gnome-desktop3-data3.20.1-1
ii  gnome-settings-daemon  3.20.1-1
ii  gsettings-desktop-schemas  3.20.0-3
ii  libaccountsservice00.6.40-3
ii  libatk1.0-02.20.0-1
ii  libc6  2.22-7
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libcanberra-gtk3-0 0.30-3
ii  libcanberra0   0.30-3
ii  libcheese-gtk253.20.1-1
ii  libcheese8 3.20.1-1
ii  libclutter-1.0-0   1.26.0-2
ii  libclutter-gtk-1.0-0   1.8.0-1
ii  libcolord-gtk1 0.1.26-1
ii  libcolord2 1.3.2-1
ii  libcups2   2.1.3-5
ii  libdbus-glib-1-2   0.106-1
ii  libfontconfig1 2.11.0-6.4
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libgl1-mesa-glx [libgl1]   11.1.3-1
ii  libglib2.0-0   2.48.0-1
ii  libgnome-bluetooth13   3.18.3-1
ii  libgnome-desktop-3-12  3.20.1-1
ii  libgoa-1.0-0b  3.18.4-1
ii  libgoa-backend-1.0-1   3.18.4-1
ii  libgrilo-0.3-0 0.3.0-1.1
ii  libgtk-3-0 3.20.3-1
ii  libgtop-2.0-10 2.34.0-1
ii  libgudev-1.0-0 230-3
ii  libibus-1.0-5  1.5.11-1
ii  libkrb5-3  1.13.2+dfsg-5
ii  libmm-glib01.4.14-1
ii  libnm-glib-vpn11.1.94-1
ii  libnm-glib41.1.94-1
ii  libnm-gtk0 1.1.93-1
ii  libnm-util21.1.94-1
ii  libpango-1.0-0 1.40.1-1
ii  libpangocairo-1.0-01.40.1-1
ii  libpolkit-gobject-1-0  0.105-15
ii  libpulse-mainloop-glib08.0-2+b2
ii  libpulse0  8.0-2+b2
ii  libpwquality1  1.2.3-1
ii  libsmbclient   2:4.3.8+dfsg-1
ii  libsoup2.4-1   2.54.0.1-1
ii  libupower-glib30.99.4-2
ii  libwacom2  0.18-1
ii  libx11-6   2:1.6.3-1
ii  libxi6 2:1.7.6-1
ii  libxml22.9.3+dfsg1-1

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime 2.9.2-1+b2
ii  cups-pk-helper   0.2.5-2+b1
ii  gkbd-capplet 3.6.0-1
ii  gnome-online-accounts3.18.4-1
ii  gnome-user-guide 3.20.1-1
ii  gnome-user-share 3.18.1-1
ii  iso-codes3.67-1
ii  libnss-myhostname229-4
ii  mesa-utils   8.3.0-1
ii  mousetweaks  3.12.0-1
ii  network-manager-gnome1.1.93-1
ii  policykit-1  0.105-15
ii  pulseaudio-module-bluetooth  8.0-2+b2
ii  realmd   0.16.2-2
ii  rygel0.28.3-1
ii  rygel-tracker0.28.3-1
ii  system-config-printer1.5.7-1

Versions of packages gnome-control-center suggests:
ii  gstreamer1.0-pulseaudio  1.8.1-1
ii  libcanberra-gtk-module   0.30-3
ii  libcanberra-gtk3-module  0.30-3
ii  x11-xserver-utils7.7+7

-- no debconf information

Bug#817091: Acmetool Review

[Peter Colberg]

Hi Harlan,

On Sun, Apr 17, 2016 at 08:48:09PM -0400, Harlan Lieberman-Berg wrote:
> Took a look at the acmetool package, and it looks pretty good.

Thank you for taking the time to review the package!

Please pull from the git repository for commit 771996d, which adds a
patch for a security vulnerability reported upstream. This mitigates a
DOS by a malicious ACME server or intermediary sending a huge response
to exhaust the client’s memory. (This may affect other Let’s Encrypt
clients, too.)

> You might want to suppress the lintian warnings for some of the
> hardening flags; it's my understanding (please correct me if I'm wrong
> -- I'm far from a Golang expert) that Golang simply doesn't support many
> kinds of hardening flags on its output -- PIE just doesn't work, and
> since it produces statically linked binaries, some of the other stuff
> doesn't work either.

The Go compiler supports a -buildmode=pie since version 1.6, but
currently dh_golang triggers a bug that prevents its use in Debian.

https://bugs.debian.org/821454

I would like to keep the lintian warnings both for PIE and BINDNOW,
since these should be taken seriously and fixed rather than muted.

> There's also a newer version that's been released since you first
> packaged acmetool; it should be updated prior to upload.

Could you upload the package as of commit 771996d?

The newer versions (0.0.50 and 0.0.51) switched to versioned import
paths for some of the dependencies, which was in fact triggered by
Dmitry's and my requests to properly tag versions.

Go imports packages by URL, but does not support versioning natively.
The Go community set up a redirector service http://gopkg.in as a
work-around that allows importing packages by major version using

gopkg.in/user/pkg.v3 → github.com/user/pkg   (branch/tag v3, v3.N, or v3.N.M)

Unfortunately that means the corresponding Debian packages have
to be re-uploaded with new source and binary package names, e.g.,
golang-github-user-pkg becomes golang-gopkg-user-pkg.v3.

I have included all security and bug fixes from versions 0.0.50 and
0.0.51 as patches to avoid needing to upload further Go packages,
which is a painful process when depending only on sponsorship.

Getting to this stage at all was possible only thanks to the tireless
work of Dmitry Smirnov. I hope to get my first GnuPG signatures from
two Debian developers passing through the city in May, and apply to
become Debian maintainer to at least be able to upload new versions.

Regards,
Peter

Bug#822257: linux-image-4.5.0-1-amd64: Since the upgrade to kernel 4.5.0-1 i can't login at all!!!

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

At what does the boot or login process fail?  Do you see any error
messages?

If you are using a graphical login screen, have you tried switching to
a text terminal (Ctrl-Alt-F2) and logging in there?  Does that still
work?

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson


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

Bug#819284: jessie-pu: package ext4magic/0.3.2-2

[Jonathan Wiltshire]

Control: tag -1 confirmed

On Fri, Mar 25, 2016 at 10:40:37PM -0300, Giovani Augusto Ferreira wrote:
> The ext4magic has a misinterpretation of the physical block addresses and
> block lengths of ext4 inode.
> The error is permanent and 100% reproducible (also on i386)
> The upstream provides a patch to fix this problem and this problem has
> been fixed en unstable/testing.

Please go ahead.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#814779: Bug #814779: new mailing list debian-events-apac

[Laura Arjona Reina]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi
I support the creation of mailing list debian-events-apac
It would be a nice place to point to people wanting to gather
together in the Asia-Pacific area, and jump from users to contributors
.

It's been FOSSAsia this year and hopefully more events in the future.

Best regards
- -- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQGcBAEBCAAGBQJXGoUeAAoJEEw4Yb3McGt0bicL/0L76uAoXlqYpMu3AIAxZJow
JNWmNtiahW28sVvccb9iapQwYmhO9DUcdns3/WOXZbHKnZKmo6zLSsP++F7rcYEw
bv1BS+8E64EQkLgZhielcz+7zfRgMXX5eL6UWrMi3H7plKQMv0deAVAx2+hWnzkh
Jz2aYFS0T+Eob0NtJtPqDZnpeAiLtz6025tIS4bueHsrhP/fyHKNO0E9zCF1zI8+
bKUsNzUpjfU6tkYMq5Exly+VEWZKeZeS4LZcyntli3rI6oM8dkiPd5CAdvbwL5S2
yCeJdJ/+XJu9sruS6GuUoAaSqAe5wxucvGlRZVGpHzkcZTY33DZ5dIiTvQnoTzpu
mq9oQ6fz+YH5l0XKZ3ld7izM0Sjd0xVCZ2qlxu5lcOxnFNkSTDlzBvKlwJOwwCJE
N7jxLhc29ItIxj9+8phE9wd6tRnGIzWbGCDGCpRRgSN6U28d8cQt1B6J9fed09j6
bZdQuIYAucN5WSk47dHODdglgfuEuTLVXPQtuIDQJQ==
=iqPv
-END PGP SIGNATURE-

Bug#816796: php-apigen: Useless in Debian

[Florian Schlichting]

Hi David,

On Wed, Apr 20, 2016 at 04:00:40PM -0400, David Prévot wrote:
> Le 20/04/2016 à 15:43, Florian Schlichting a écrit
> > So if it's not too difficult to maintain with PHP 7, I'd love for
> > php-apigen to be kept in Debian in the future!
> 
> Feel free to take it over (with its dependency chain).

OK, I'll have a look at php-apigen and dependencies, preparing updates
for PHP 7. Can I keep you in Uploaders, or would you rather be removed?

> My main concern is about security support during the stable lifetime:
> it???s PHP, so there will be problems/stuff to fix. Relying on the
> packaging team to take care of that on one???s behalf is not an option (it
> won???t scale, and I don???t want to be the one doing the clean up during
> the stable lifetime, hence those RC-bugs prior to the release).

Thanks for clarifying. I will consider that when looking at the
packages, but I think I can handle the workload. I may need a hand or
helpful hint getting used to the pkg-php tools, though, so if you see me
doing something stupid please do tell!

I have requested to join pkp-php on alioth.

Florian

Bug#821884: please provide a shortcut to delete previous/next word

[Benno Schulenberg]

On 2016-04-20 09:44, Arturo Borrero Gonzalez wrote:
> In bash-like shells there are two nice shortcuts:
>  * CTRL+w (delete previous word)
>  * ALT+d (delete next word)
> 
> Is there any chance that similar shortcuts gets implemented in nano?

You mean that you would like the functions cutwordleft and cutwordright
to be bound by default?  So that you can rely on them being available
on any machine with a modern nano installed without needing any kind
of configuration in ~/.nanorc?

That would indeed by nice, but we don't have any free keys left -- at
least not ones that one might be able to remember.  The best I can come
up with would be an option, say -M/--modern, which would put some keys
to better use.  For example, the toggles M-F and M-B have no place in
the main menu (but the owner of nano uses the M-F toggle, so there is
no chance of changing those in the default config) -- M-F belongs only
in the Read File menu, and M-B in the Write Out menu, where they already
exist, so those keys can be taken without loss of any functionality.

And if it were up to me, I would also remove the M-O toggle (one is
either used to having this blank line or not, one wouldn't want to
toggle between one state and the other, it is not like the help lines).
The same for the M-S toggle.  And the M-T function is such a convenience
thing and so easily done with M-A, M-/, ^K, that it's not worth it taking
up a key.

So, if we have those keys freed up, M-B, M-F, M-O, M-S, M-T, and
of course ^S and ^Q, which key strokes would you prefer to use for
cutwordleft and cutwordright?

Benno

Bug#822179: xorg: X.Org X Server starts normally, crashes with Segmentation fault on starting any application

[Julien Cristau]

Control: tags -1 moreinfo help

On Thu, Apr 21, 2016 at 23:16:02 +0200, Matthias wrote:

> Package: xorg
> Version: 1:7.7+14
> Severity: normal
> 
> Dear Maintainer,
> 
> X crashes instantly when starting any application, e.g. FF or system 
> configuration settings or display settings. The Xorg.0.log file states, 
> xorg-server version is 2:1.18.3-1 . System is Debian testing running under 
> hurd.
> 
This would have to be looked at by a hurd person.  (Also, there's no
such thing as debian testing for hurd, afaik, only unstable)

Cheers,
Julien

> 
> -- Package-specific info:
> X server symlink status:
> 
> lrwxr-xr-x 1 root root 13 Dec 28 11:32 /etc/X11/X -> /usr/bin/Xorg
> -rwxr-xr-x 1 root root 274 Apr  5 11:40 /usr/bin/Xorg
> 
> VGA-compatible devices on PCI bus:
> --
> 
> Xorg X server configuration file status:
> 
> -rw-r--r-- 1 root root 131 Dec 28 11:38 /etc/X11/xorg.conf
> 
> Contents of /etc/X11/xorg.conf:
> ---
> Section "InputDevice"
>Identifier "Generic Keyboard"
>Driver "kbd"
>Option "XkbOptions" "terminate:ctrl_alt_bksp"
> EndSection
> 
> /etc/X11/xorg.conf.d does not exist.
> 
> /etc/modprobe.d contains no KMS configuration files.
> 
> Kernel version (/proc/version):
> ---
> Linux version 2.6.1 (GNU 0.7 GNU-Mach 1.6+git20160311-486/Hurd-0.7 i686-AT386)
> 
> Xorg X server log files on system:
> --
> -rw-r--r-- 1 root root 29974 Apr 21 22:45 /var/log/Xorg.0.log
> 
> Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
> -
> [982589.873] 
> X.Org X Server 1.18.3
> Release Date: 2016-04-04
> [982589.873] X Protocol Version 11, Revision 0
> [982589.873] Build Operating System: GNU 0.7 i686-AT386 Debian
> [982589.873] Current Operating System: GNU debian 0.7 GNU-Mach 
> 1.6+git20160311-486/Hurd-0.7 i686-AT386
> [982589.873] Build Date: 05 April 2016  09:20:21AM
> [982589.873] xorg-server 2:1.18.3-1 (http://www.debian.org/support) 
> [982589.873] Current version of pixman: 0.33.6
> [982589.873]  Before reporting problems, check http://wiki.x.org
>   to make sure that you have the latest version.
> [982589.873] Markers: (--) probed, (**) from config file, (==) default 
> setting,
>   (++) from command line, (!!) notice, (II) informational,
>   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [982589.873] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 21 22:44:30 
> 2016
> [982589.883] (==) Using config file: "/etc/X11/xorg.conf"
> [982589.883] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> [982589.883] (==) No Layout section.  Using the first Screen section.
> [982589.883] (==) No screen section available. Using defaults.
> [982589.883] (**) |-->Screen "Default Screen Section" (0)
> [982589.883] (**) |   |-->Monitor ""
> [982589.893] (==) No monitor specified for screen "Default Screen Section".
>   Using a default monitor configuration.
> [982589.893] (==) Not automatically adding devices
> [982589.893] (==) Not automatically enabling devices
> [982589.893] (==) Not automatically adding GPU devices
> [982589.893] (==) Max clients allowed: 256, resource mask: 0x1f
> [982589.893] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
> exist.
> [982589.893]  Entry deleted from font path.
> [982589.903] (==) FontPath set to:
>   /usr/share/fonts/X11/misc,
>   /usr/share/fonts/X11/100dpi/:unscaled,
>   /usr/share/fonts/X11/75dpi/:unscaled,
>   /usr/share/fonts/X11/Type1,
>   /usr/share/fonts/X11/100dpi,
>   /usr/share/fonts/X11/75dpi,
>   built-ins
> [982589.903] (==) ModulePath set to "/usr/lib/xorg/modules"
> [982589.903] (==) |-->Input Device ""
> [982589.903] (==) |-->Input Device "Generic Keyboard"
> [982589.903] (==) No Layout section. Using the default mouse configuration.
> [982589.903] (==) No Layout section. Using the first keyboard device.
> [982589.903] (II) Loader magic: 0x273500
> [982589.903] (II) Module ABI versions:
> [982589.903]  X.Org ANSI C Emulation: 0.4
> [982589.903]  X.Org Video Driver: 20.0
> [982589.903]  X.Org XInput driver : 22.1
> [982589.903]  X.Org Server Extension : 9.0
> [982591.283] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 
> 0xe800/134217728, 0xfe00/8388608, I/O @ 0x10d0/16, BIOS @ 
> 0x/65536
> [982591.283] (II) LoadModule: "glx"
> [982591.293] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
> [982591.313] (II) Module glx: vendor="X.Org Foundation"
> [982591.313]  compiled for 1.18.3, module version = 1.0.0
> [982591.313]  ABI class: X.Org Server Extension, version 9.0
> [982591.313] (==) AIGLX enabled
> [982591.313] (==) Matched vmware as autoconfigured driver 0
> [982591.313] (==) Matched fbdev as autoconfigured driver 1
> [982591.313] (==) Matched vesa 

Bug#538067: status of the opencpn PPA for inclusion in Debian

[Pavel Kalian]

Antoine…

Unfortunately I still did not receive any useful feedback from anybody, neither 
on Debian GIS mailing list, or any information on where I should submit 
something for review.

If you know what to look at, you may have a look at the launchpad sources at 
opencpn_4.2.0.orig.tar.xz 

 and tell me what they miss to be usable on debian (yes, the stuff present in 
the upstream git tree and not needed to build on linux is stripped from them)

Pavel
 
> On Apr 22, 2016, at 16:09, Antoine Beaupré  wrote:
> 
> Hi Pavel,
> 
> Is there any progress on the OpenCPN packaging?
> 
> It would be great to see this in stretch!
> 
>> From what I remember, the next step here is to publish your source tree
> somewhere we can review, or just reuse the Ubuntu PPA.
> 
> How does that sound?
> 
> a.
> 
> -- 
> Lorsque l'on range des objets dans des tiroirs, et que l'on a plus
> d'objets que de tiroirs, alors un tiroir au moins contient deux
> objets.
>- Lejeune-Dirichlet, Peter Gustav
> 

Bug#822183: ITP: crossbar -- WAMP application router, WAMP??

[Orestis Ioannou]

Hey,

On 04/22/2016 08:04 AM, Geert Stappers wrote:
> On Thu, Apr 21, 2016 at 11:46:00PM +0200, Orestis Ioannou wrote:
>> * Package name: crossbar
>>   Description : WAMP application router
>>
>> Crossbar.io is a networking platform for distributed and microservice
>> applications.
>> It is feature rich, scalable, robust and secure.
>> It takes care of the hard parts of messaging so you can focus on your app's
>> features.
> 
> That description might go into the Debian control file.
> 
> If so, please add what WAMP means in the context of crossbar.
> 
> I'm asking because I'm about LAMP / WAMP.
> 
> If WAMP means Windows Apache MySQL P{ython,erl,HP}, just tell.
> 
> 

Ok i noted this.
FYI it means Web Application Messaging Platform

Orestis