Processed: Lower severity

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 820060 normal
Bug #820060 [python-biom-format] python-biom-format: broken on big-endian 
architectures
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
820060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840488: Bareos crashes on "status dir"

[Traugott Simon]

Hello guys,

some news on this. The backups itself keep continuing, so the problem just hits 
the director i think.

Greetings

Bug#840701: emacs25: FTBFS: tests fail or time out

[Rob Browning]

"Aaron M. Ucko"  writes:

> Automated builds of emacs25 on Linux encountered test failures (and a
> hang on arm64), as detailed at
>
> https://buildd.debian.org/status/logs.php?pkg=emacs25=25.1%2B1-1
>
> Could you please take a look?

Definitely.  I saw that earlier, and noticed at least one build-dep
that's missing, though I don't know why my pdebuild run here didn't hit
the same issue.  In any case, I should have time to work on it this
weekend.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#840575: [buildd-tools-devel] Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode

[Johannes Schauer]

Hi,

Quoting Daniel Kahn Gillmor (2016-10-13 00:31:28)
> > On Wed, Oct 12, 2016 at 11:42:15PM +0200, Thomas Goirand wrote:
> >> gpg: Invalid option "--pinentry-mode"
> 
> … it sounds like sbuild should at least have declared a versioned
> dependency on gnupg (>= 2.1), when --pinentry-mode was introduced.

this is indeed a real bug. Thanks for reopening this so that I don't forget to
handle this for my next upload.

> Alternately, maybe the requirement to run --keygen could be relaxed?

That would require some version detection mechanism I suppose. I don't think it
is useful to have sbuild in stable be able to run with old gnupg as the next
stable release will have the correct gnupg version available. So if the
requirement is relaxed, then it is purely useful for sbuild in backports. I
don't know if our current sbuild backporter Luca (in CC) would be willing to
write such a patch, especially considering that

 - it is a feature of sbuild since version 0.67.0 (I corrected the wiki page
   accordingly) to *not* require signing of the internal dummy repository (and
   thus you don't need to run sbuild-update --keygen anymore) and that
 - the next stable release is not far away.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#840711: golang-github-appc-docker2aci: CVE-2016-8579

[Salvatore Bonaccorso]

Source: golang-github-appc-docker2aci
Version: 0.12.0+dfsg-1
Severity: grave
Tags: security upstream patch
Forwarded: https://github.com/appc/docker2aci/issues/203

Hi,

the following vulnerability was published for golang-github-appc-docker2aci.

CVE-2016-8579[0]:
infinite loop in deps walking

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8579
[1] https://github.com/appc/docker2aci/issues/203
[2] 
https://github.com/lucab/docker2aci/commit/54331ec7020e102935c31096f336d31f6400064f

Regards,
Salvatore

Bug#840691: libgs9: security update DSA-3691-1 breaks zathura, evince, ... in jessie

[Salvatore Bonaccorso]

Control: affects -1 security.debian.org
Control: tags -1 + help

Hi Francesco,

On Thu, Oct 13, 2016 at 11:56:22PM +0200, Francesco Poli (wintermute) wrote:
> Package: libgs9
> Version: 9.06~dfsg-2+deb8u3
> Severity: grave
> Tags: security
> Justification: renders package unusable
> 
> Hello!
> 
> I had a bad surprise today in jessie.
> After the security update:
> 
>   [UPGRADE] libgs9:amd64 9.06~dfsg-2+deb8u1 -> 9.06~dfsg-2+deb8u3
>   [UPGRADE] libgs9-common:amd64 9.06~dfsg-2+deb8u1 -> 9.06~dfsg-2+deb8u3
> 
> I was unable to use zathura or evince (maybe other PS viewers are
> affected):
> 
>   $ zathura foo.eps
>   warning: Failed to loads bookmarks.
>   invalidaccess -7
>   error: Rendering failed (page 1)
>   $ evince foo.eps
>   invalidaccess -7
>   invalidaccess -7
>   Segmentation fault
> 
> After downgrading back to libgs9/9.06~dfsg-2+deb8u1 and
> libgs9-common/9.06~dfsg-2+deb8u1, everything is back to normal
> and the two PS viewers work again.
> 
> What went wrong?
> If this is indeed a regression (as it seems to be), please fix it
> as soon as possible!

This was indeed not spotted in my testing of the update for the DSA.
The blame for this should solely go to myself (not the team). We
should find the cause asap and find a fix. I can reproduce it with
evince.

Regards,
Salvatore

Processed: Re: Bug#840691: libgs9: security update DSA-3691-1 breaks zathura, evince, ... in jessie

[Debian Bug Tracking System]

Processing control commands:

> affects -1 security.debian.org
Bug #840691 [libgs9] libgs9: security update DSA-3691-1 breaks zathura, evince, 
... in jessie
Added indication that 840691 affects security.debian.org
> tags -1 + help
Bug #840691 [libgs9] libgs9: security update DSA-3691-1 breaks zathura, evince, 
... in jessie
Added tag(s) help.

-- 
840691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840701: emacs25: FTBFS: tests fail or time out

[Aaron M. Ucko]

Source: emacs25
Version: 25.1+1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Automated builds of emacs25 on Linux encountered test failures (and a
hang on arm64), as detailed at

https://buildd.debian.org/status/logs.php?pkg=emacs25=25.1%2B1-1

Could you please take a look?

(Non-Linux builds failed for another reason, which I'll report separately
in a moment.)

Thanks!

FYI, even though emacs25 is new, I'm classifying this bug as a regression
because I strongly suspect it would also strike binNMUs on amd64.

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

Bug#840699: ninix-aya: does not work with ruby-gnome2 3.0.9-1

[HIGUCHI Daisuke (VDR dai)]

Package: ninix-aya
Version: 4.999.2-1
Severity: serious
Tags: experimental

Dear Maintainer,

I plan to upload ruby-gnome2 3.0.9 into unstable.
Before I do so, I test rdep packages in experimental uploading.
ninix-aya does not work with ruby-gnome2 3.0.9-1.

-
:
/usr/lib/ruby/vendor_ruby/ninix/menu.rb:836:in `new': 
'Gtk::MenuItem#initialize(label, use_underline=false)' style has been 
deprecated. Use 'Gtk::MenuItem#initialize(:label => label, :use_underline => 
use_underline)' style.
/usr/lib/ruby/vendor_ruby/ninix/menu.rb:836:in `new': 
'Gtk::MenuItem#initialize(label, use_underline=false)' style has been 
deprecated. Use 'Gtk::MenuItem#initialize(:label => label, :use_underline => 
use_underline)' style.
/usr/lib/ruby/vendor_ruby/ninix/pix.rb:266:in `pixbuf_new_from_file': 
'Gdk::Pixbuf' has been deprecated. Use 'GdkPixbuf::Pixbuf'.
/usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': 
GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => 
path) instead.
/usr/lib/ruby/vendor_ruby/glib2/deprecatable.rb:112:in `const_missing': 
uninitialized constant GdkPixbuf::Pixbuf::InterpType
Did you mean?  GdkPixbuf::InterpType
 from /usr/lib/ruby/vendor_ruby/ninix/pix.rb:279:in `create_icon_pixbuf'
 from /usr/lib/ruby/vendor_ruby/ninix/menu.rb:661:in 
`create_ghost_menuitem'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:812:in `create_menuitem'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:472:in `call'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:472:in `handle_request'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:367:in `create_menuitem'
 from /usr/lib/ruby/vendor_ruby/ninix/metamagic.rb:103:in `baseinfo='
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1227:in `add_sakura'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:535:in `do_install'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1571:in 
`open_file_chooser'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1563:in `call'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1563:in `response'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1441:in `block in 
initialize'
 from /usr/lib/ruby/vendor_ruby/gobject-introspection/loader.rb:114:in 
`invoke'
 from /usr/lib/ruby/vendor_ruby/gobject-introspection/loader.rb:114:in 
`block in define_singleton_method'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:950:in `run'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:132:in `main'
 from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1795:in `'
:
-

Can you fix it to work with ruby-gnome2 3.0.9-1 ?
I want to make ruby-gnome2 3.0.9-1 in time for stretch freeze (2016-Nov-05).
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E

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

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

Versions of packages ninix-aya depends on:
ii  ruby1:2.3.0+4
ii  ruby-gettext3.2.2-1
ii  ruby-gio2   3.0.9-1
ii  ruby-gstreamer  3.0.9-1
ii  ruby-gtk3   3.0.9-1
ii  ruby-narray 0.6.1.1-2+b3
ii  ruby-zip1.2.0-1

ninix-aya recommends no packages.

Versions of packages ninix-aya suggests:
pn  kawari8  

-- no debconf information


signature.asc
Description: PGP signature

Bug#840698: xnetcardconfig: does not work with ruby-gnome2 3.0.9-1

[HIGUCHI Daisuke (VDR dai)]

Package: xnetcardconfig
Version: 0.3.0-1
Severity: serious
Tags: experimental

Dear Maintainer,

I plan to upload ruby-gnome2 3.0.9 into unstable.
Before I do so, I test rdep packages in experimental uploading.
xnetcardconfig does not work with ruby-gnome2 3.0.9-1.

% xnetcardconfig
/usr/bin/xnetcardconfig.real:845:in `': undefined method `init' for 
Gtk:Module (NoMethodError)
%

Can you fix it to work with ruby-gnome2 3.0.9-1 ?
I want to make ruby-gnome2 3.0.9-1 in time for stretch freeze (2016-Nov-05).
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E

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

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

Versions of packages xnetcardconfig depends on:
ii  gksu   2.0.2-9
ii  pump   0.8.24-7
ii  ruby   1:2.3.0+4
ii  ruby-gdk3  3.0.9-1
ii  ruby-gtk3  3.0.9-1
ii  sudo   1.8.17p1-2

xnetcardconfig recommends no packages.

xnetcardconfig suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Processed: tagging 823447

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 823447 + pending
Bug #823447 [src:gtest] gtest: FTBFS with g++-6 and glibc 2.23: Test failure
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840639: marked as done (axiom: FTBFS on arm64, mips64el and mipsel)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 00:20:00 +
with message-id 
and subject line Bug#840639: fixed in axiom 20140801-12
has caused the Debian Bug report #840639,
regarding axiom: FTBFS on arm64, mips64el and mipsel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: axiom
Version: 20140801-11
Severity: serious

Hi,

Your package failed to build on arm64, mipsel and mips64el.

Full logs at https://buildd.debian.org/status/package.php?p=axiom

Emilio

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: axiom
Source-Version: 20140801-12

We believe that the bug you reported is fixed in the latest version of
axiom, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated axiom package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 13 Oct 2016 19:29:19 +
Source: axiom
Binary: axiom axiom-source axiom-test axiom-doc axiom-databases axiom-tex 
axiom-graphics axiom-graphics-data axiom-hypertex axiom-hypertex-data
Architecture: source all amd64
Version: 20140801-12
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Description:
 axiom  - General purpose computer algebra system: main binary and modules
 axiom-databases - General purpose computer algebra system: generated text 
databases
 axiom-doc  - General purpose computer algebra system: documentation
 axiom-graphics - General purpose computer algebra system: graphics subsystem
 axiom-graphics-data - General purpose computer algebra system: graphics 
subsystem
 axiom-hypertex - General purpose computer algebra system: hypertex subsystem
 axiom-hypertex-data - General purpose computer algebra system: hypertex 
subsystem
 axiom-source - General purpose computer algebra system: source files
 axiom-test - General purpose computer algebra system: regression test inputs
 axiom-tex  - General purpose computer algebra system: style file for TeX
Closes: 840639
Changes:
 axiom (20140801-12) unstable; urgency=medium
 .
   * build dep against latest gcl
   * Bug fix: "FTBFS on arm64, mips64el and mipsel", thanks to Emilio
 Pozuelo Monfort (Closes: #840639).
Checksums-Sha1:
 0339dec6019ab409f078c5231ec251be7b60423d 2444 axiom_20140801-12.dsc
 07a85eaaa287b0a32b0c862824597e5f3bec81c0 741708 axiom_20140801-12.debian.tar.xz
 f81f517bab96de25e95c59e95811ad55b0ae1473 877828 
axiom-databases_20140801-12_all.deb
 fca21d9ced6463d00226da8f006dc9238a3ceb4c 13474 
axiom-dbgsym_20140801-12_amd64.deb
 1bf2efd250887d683dae8f9a7866e497a7d2 82917060 axiom-doc_20140801-12_all.deb
 b1fa3d098c9dbb87b10c78267f92a1246f88781f 1562332 
axiom-graphics-data_20140801-12_all.deb
 fa54d49679fc0e033452bc6a7fce6414037d3148 15438 
axiom-graphics-dbgsym_20140801-12_amd64.deb
 0f8f8382e090147a3d1129d6b76d2c3497ddc50b 254854 
axiom-graphics_20140801-12_amd64.deb
 4a7e58aa1837c11c193d5735ac57aaff357d 26521966 
axiom-hypertex-data_20140801-12_all.deb
 a9a3af0d95f21c1102c3847b35c230305264be37 13452 
axiom-hypertex-dbgsym_20140801-12_amd64.deb
 51ef2990d7dbe4d4b1cf380e1cc1156bcbc1e4ce 223732 
axiom-hypertex_20140801-12_amd64.deb
 b6a4cff4024676e13eddaa5537c36091543be95c 137502 
axiom-source_20140801-12_all.deb
 f2c3c58096efbe07da1537c65246fe5f60057940 9592156 axiom-test_20140801-12_all.deb
 d38539592b19d9e98b34ce2bdf2a3d5964ad4df8 158034 axiom-tex_20140801-12_all.deb
 3b7100187c4c7d94144fa0e1fbdd22b1826dd14c 40621446 axiom_20140801-12_amd64.deb

Bug#840680: [pkg-gnupg-maint] Bug#840680: dirmngr: Dirmngr not always responding

[Daniel Kahn Gillmor]

Control: tags 840680 + unreproducible moreinfo
Control: severity 840680 important

hi Shengjing--

Thanks for this report.  it sounds frustrating!  I hope we can debug it:

On Thu 2016-10-13 15:12:44 -0400, Shengjing Zhu wrote:
> After upgrade to 2.1.15-4, I find dirmngr is not always responding
> which makes command like `gpg --refresh-keys` stuck.

is this "always not responding" or "sometimes not responding"?  I
haven't observed the same behavior with dirmngr myself, so i'm not sure
how to best proceed...

> I test dirmngr with the following steps:
>
> First run `gpg-connect-agent --dirmngr /bye`
> It should immediately return but it's stuck.
>
> But I open another shell to run `gpg-connect-agent --dirmngr /bye`
> again. The first gpg-connect-agent returns and the second still is
> stuck.
>
> And I run again `gpg-connect-agent` and the previous one returns.

this is definitely strange behavior!  have you tried attaching strace to
the dirmngr process to see what it's doing while it's not answering you?
or have you tried increasing the logging of dirmngr to see what it's
doing while it's not responding?

if the process id of dirmngr is $DIRMNGR_PID, you can use:

strace -o dirmngr.strace -f -tt -T -p $DIRMNGR_PID

to get an strace dump.

You can increase the logging by adding these lines to
~/.gnupg/dirmngr.conf and then restarting dirmngr:

log-file /tmp/dirmngr.log
debug-level advanced

If you've got dirmgnr logs or strace output that you think might be
worth sharing, but are maybe too sensitive to post to this public bug
report, feel free to send them privately to me (you can encrypt to
0EE5BE979282D80B9F7540F1CCD2ED94D21739E9 if you like).

> So I guess only another process access to the dirmngr socket, the
> previous connect will be got processed.

I'm not sure what you mean by this.  can you explain?

  --dkg


signature.asc
Description: PGP signature

Processed: Re: [pkg-gnupg-maint] Bug#840680: dirmngr: Dirmngr not always responding

[Debian Bug Tracking System]

Processing control commands:

> tags 840680 + unreproducible moreinfo
Bug #840680 [dirmngr] dirmngr: Dirmngr not always responding
Added tag(s) unreproducible and moreinfo.
> severity 840680 important
Bug #840680 [dirmngr] dirmngr: Dirmngr not always responding
Severity set to 'important' from 'grave'

-- 
840680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#831591: ffmpeg: kodi crash

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #831591 {Done: Bálint Réczey } [ffmpeg] ffmpeg: 
kodi crash
Bug #832364 {Done: Bálint Réczey } [ffmpeg] kodi: 
Crashes on trying to play any TV recording
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ffmpeg/7:3.1.3-1.
No longer marked as fixed in versions ffmpeg/7:3.1.3-1.
> reassign -1 kodi 16.1+dfsg1-2
Bug #831591 [ffmpeg] ffmpeg: kodi crash
Bug #832364 [ffmpeg] kodi: Crashes on trying to play any TV recording
Bug reassigned from package 'ffmpeg' to 'kodi'.
Bug reassigned from package 'ffmpeg' to 'kodi'.
No longer marked as found in versions ffmpeg/7:3.1.1-2.
No longer marked as found in versions ffmpeg/7:3.1.1-2.
Ignoring request to alter fixed versions of bug #831591 to the same values 
previously set
Ignoring request to alter fixed versions of bug #832364 to the same values 
previously set
Bug #831591 [kodi] ffmpeg: kodi crash
Bug #832364 [kodi] kodi: Crashes on trying to play any TV recording
Marked as found in versions kodi/16.1+dfsg1-2.
Marked as found in versions kodi/16.1+dfsg1-2.
> severity -1 important
Bug #831591 [kodi] ffmpeg: kodi crash
Bug #832364 [kodi] kodi: Crashes on trying to play any TV recording
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'

-- 
831591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831591
832364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#831591: ffmpeg: kodi crash

[Andreas Cadhalpun]

Control: reopen -1
Control: reassign -1 kodi 16.1+dfsg1-2
Control: severity -1 important

Hi,

The relevant backtrace from the kodi_crashlog is:

Thread 1 (Thread 0x7f1b6bffe700 (LWP 16893)):
#0  0x7f1ba92991c8 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x7f1ba929a64a in __GI_abort () at abort.c:89
#2  0x7f1ba92d4f4a in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7f1ba93cdb30 "*** Error in `%s': %s: 0x%s ***\n") at 
../sysdeps/posix/libc_fatal.c:175
#3  0x7f1ba92da6b6 in malloc_printerr (action=3, str=0x7f1ba93ca909 
"free(): invalid pointer", ptr=, ar_ptr=) at 
malloc.c:5004
#4  0x7f1ba92dae9e in _int_free (av=0x7f1ba9601b20 , 
p=, have_lock=0) at malloc.c:3865
#5  0x7f1baa6d4a9d in av_buffer_unref () from 
/usr/lib/x86_64-linux-gnu/libavutil.so.55
#6  0x7f1baa6e15d2 in av_frame_unref () from 
/usr/lib/x86_64-linux-gnu/libavutil.so.55
#7  0x7f1bab93cf10 in avcodec_decode_video2 () from 
/usr/lib/x86_64-linux-gnu/libavcodec.so.57
#8  0x0090b26c in CDVDDemuxFFmpeg::ParsePacket(AVPacket*) ()
#9  0x0090d0c2 in CDVDDemuxFFmpeg::Read() ()
#10 0x01079b53 in CDVDPlayer::ReadPacket(DemuxPacket*&, CDemuxStream*&) 
()
#11 0x0107ecd7 in CDVDPlayer::Process() ()
#12 0x012103ff in CThread::Action() ()
#13 0x012106bf in CThread::staticThread(void*) ()
#14 0x7f1bb23e5464 in start_thread (arg=0x7f1b6bffe700) at 
pthread_create.c:333
#15 0x7f1ba934d30d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Looking at the ParsePacket function reveals [1]:
AVFrame picture;
memset(, 0, sizeof(AVFrame));
picture.pts = picture.pkt_dts = picture.pkt_pts = 
picture.best_effort_timestamp = AV_NOPTS_VALUE;
picture.pkt_pos = -1;
picture.key_frame = 1;
picture.format = -1;

This is using non-public ABI, e.g. the size of AVFrame, while the documentation
explicitly says "sizeof(AVFrame) is not a part of the public ABI" [2].
What's worse is that it doesn't use av_frame_alloc as required [3]:
"AVFrame must be allocated using av_frame_alloc()."

The whole block quoted above should be replaced with:
AVFrame *picture = av_frame_alloc().

Then the following code should use picture instead of :
avcodec_decode_video2(st->codec, picture, _picture, pkt);

And at the end it can be freed (instead of using av_frame_unref) with:
av_frame_free();

In the experimental kodi branch there is another occurrence of this bug
in xbmc/cores/VideoPlayer/VideoRenderers/HwDecRender/MMALRenderer.cpp.

Best regards,
Andreas


1: 
https://anonscm.debian.org/cgit/pkg-multimedia/kodi.git/tree/xbmc/cores/dvdplayer/DVDDemuxers/DVDDemuxFFmpeg.cpp?id=8d5cf423001aa4e7f850c20b158b2811e637e607#n1665
2: 
https://anonscm.debian.org/cgit/pkg-multimedia/ffmpeg.git/tree/libavutil/frame.h?id=87b93f4e3ee2b6253ab9f5a166860a1ff18877d5#n174
3: 
https://anonscm.debian.org/cgit/pkg-multimedia/ffmpeg.git/tree/libavutil/frame.h?id=87b93f4e3ee2b6253ab9f5a166860a1ff18877d5#n154

Bug#840679: marked as done ({qterminal, libfm-qt, liblxqt}-l10n: fails to upgrade from 'sid' - trying to overwrite /usr/share/*/translations/*.qm)

[Debian Bug Tracking System]

Your message dated Thu, 13 Oct 2016 22:56:32 +
with message-id 
and subject line Bug#840679: fixed in lxqt-l10n 0.11.0-19-g717bd7e-2
has caused the Debian Bug report #840679,
regarding {qterminal, libfm-qt, liblxqt}-l10n: fails to upgrade from 'sid' - 
trying to overwrite /usr/share/*/translations/*.qm
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qterminal-l10n,libfm-qt-l10n,liblxqt-l10n
Version: 0.11.0-19-g717bd7e-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package qterminal-l10n.
  Preparing to unpack .../2-qterminal-l10n_0.11.0-19-g717bd7e-1_all.deb ...
  Unpacking qterminal-l10n (0.11.0-19-g717bd7e-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-rCQMhn/2-qterminal-l10n_0.11.0-19-g717bd7e-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/qterminal/translations/qterminal_cs.qm', 
which is also in package qterminal 0.6.1~102-g58f4f72-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-rCQMhn/2-qterminal-l10n_0.11.0-19-g717bd7e-1_all.deb

  Selecting previously unselected package libfm-qt-l10n.
  Preparing to unpack .../2-libfm-qt-l10n_0.11.0-19-g717bd7e-1_all.deb ...
  Unpacking libfm-qt-l10n (0.11.0-19-g717bd7e-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Q6Pam2/2-libfm-qt-l10n_0.11.0-19-g717bd7e-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/libfm-qt/translations/libfm-qt_ar.qm', which 
is also in package libfm-qt3:amd64 0.11.0-2+b1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Q6Pam2/2-libfm-qt-l10n_0.11.0-19-g717bd7e-1_all.deb

  Selecting previously unselected package liblxqt-l10n.
  Preparing to unpack .../2-liblxqt-l10n_0.11.0-19-g717bd7e-1_all.deb ...
  Unpacking liblxqt-l10n (0.11.0-19-g717bd7e-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-nVQdhO/2-liblxqt-l10n_0.11.0-19-g717bd7e-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/lxqt/translations/liblxqt/liblxqt_ar.qm', 
which is also in package liblxqt0:amd64 0.10.0-5
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-nVQdhO/2-liblxqt-l10n_0.11.0-19-g717bd7e-1_all.deb


cheers,

Andreas


qterminal=0.6.1~102-g58f4f72-1_qterminal-l10n=0.11.0-19-g717bd7e-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lxqt-l10n
Source-Version: 0.11.0-19-g717bd7e-2

We believe that the bug you reported is fixed in the latest version of
lxqt-l10n, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated lxqt-l10n package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 13 Oct 2016 21:49:35 +0200
Source: lxqt-l10n
Binary: compton-conf-l10n libfm-qt-l10n liblxqt-l10n lximage-qt-l10n 
lxqt-about-l10n lxqt-admin-l10n lxqt-config-l10n lxqt-globalkeys-l10n 
lxqt-notificationd-l10n lxqt-openssh-askpass-l10n lxqt-panel-l10n 
lxqt-policykit-l10n lxqt-powermanagement-l10n lxqt-runner-l10n 
lxqt-session-l10n lxqt-sudo-l10n obconf-qt-l10n pavucontrol-qt-l10n 
pcmanfm-qt-l10n qterminal-l10n
Architecture: source
Version: 0.11.0-19-g717bd7e-2
Distribution: experimental
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Alf Gaida 
Description:
 compton-conf-l10n - Language package for compton-conf
 libfm-qt-l10n - Language package for libfm-qt
 liblxqt-l10n - Language package for liblxqt
 

Bug#840358: marked as done (Multiple security issues in libiberty)

[Debian Bug Tracking System]

Your message dated Thu, 13 Oct 2016 22:56:25 +
with message-id 
and subject line Bug#840358: fixed in ht 2.1.0+repack1-1
has caused the Debian Bug report #840358,
regarding Multiple security issues in libiberty
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ht
Severity: grave
Tags: security

ht embeds a copy of libiberty, which was affected by several
vulneranbilities:

https://security-tracker.debian.org/tracker/CVE-2016-6131
https://security-tracker.debian.org/tracker/CVE-2016-4493
https://security-tracker.debian.org/tracker/CVE-2016-4492
https://security-tracker.debian.org/tracker/CVE-2016-4491
https://security-tracker.debian.org/tracker/CVE-2016-4490
https://security-tracker.debian.org/tracker/CVE-2016-4489
https://security-tracker.debian.org/tracker/CVE-2016-4488
https://security-tracker.debian.org/tracker/CVE-2016-4487
https://security-tracker.debian.org/tracker/CVE-2016-2226

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: ht
Source-Version: 2.1.0+repack1-1

We believe that the bug you reported is fixed in the latest version of
ht, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated ht package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 13 Oct 2016 23:24:45 +0200
Source: ht
Binary: ht
Architecture: source
Version: 2.1.0+repack1-1
Distribution: unstable
Urgency: critical
Maintainer: Anton Gladky 
Changed-By: Anton Gladky 
Description:
 ht - Viewer/editor/analyser (mostly) for executables
Closes: 840358
Changes:
 ht (2.1.0+repack1-1) unstable; urgency=critical
 .
   * [384c0d4] New upstream version 2.1.0+repack1
   * [38ec499] Use packaged version of libiberty instead of embedded.
   (Closes: #840358)
   CVE-2016-4487 CVE-2016-4488 CVE-2016-4489 CVE-2016-4490
   CVE-2016-4491 CVE-2016-4492 CVE-2016-4493 CVE-2016-2226
   CVE-2016-6131
   * [b2c2049] Remove info-file.
   * [19ad75b] Set flags in Makefile to link packaged libiberty.
   * [60f8762] Apply cme fix-dpkg.
Checksums-Sha1:
 8729b12ba6575bd11e2bc383855cfebef1a9985e 1893 ht_2.1.0+repack1-1.dsc
 c4690a8b07ce457d66a5f5b466fd42059e34adb3 676472 ht_2.1.0+repack1.orig.tar.xz
 464adf77b02533736f8c4ace49880d67465c5e94 7944 ht_2.1.0+repack1-1.debian.tar.xz
Checksums-Sha256:
 4247e12782df14d12ffca975ba79e20ef124278de68084105ebf76ff9092f370 1893 
ht_2.1.0+repack1-1.dsc
 0b593019a42ddca5f494dc47c239577a281c87089abd66991a1258fc6ca67dac 676472 
ht_2.1.0+repack1.orig.tar.xz
 500c3a7dd01ab97ec9cede4ab74f76ea74f237e00533b44b3f537fdc92f4d130 7944 
ht_2.1.0+repack1-1.debian.tar.xz
Files:
 db7131ed25e873d865be668e242b1551 1893 devel optional ht_2.1.0+repack1-1.dsc
 325319dd02eb3b730e44da74c22276fd 676472 devel optional 
ht_2.1.0+repack1.orig.tar.xz
 0941b80bd01d78aad8ee41008715e9c2 7944 devel optional 
ht_2.1.0+repack1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX//0BAAoJENPhc4PPp/8GImMP/A1yvrBXI2qfXeStTj7Z8Mjl
jha5iF7dsGl16YcxfxSM/nGS807NQAPdOXNgfMQNqY/UqeIUgNg3Al6XTSd7aDyd
4pVL/FP5pUB6tKd4onhW42Z/vmL6Wwe8GHvRfufWCxXmwpw9D5vF5zFraY/3Eea8
GAkOt0m6+KXMKSBuZfy+3pmigdrU3N010sl4aML70mk/lz7wwJudm8yqmUFZ5s3+
FtBD/feVNQwXBslJpUpnQOMpaNSXlcab2b993n5L6jHKN4hS6PZXqHdD/1BSCE7H
4jv54CMh0w7yaA5Iv22i6s7twF3uu+oNceiAfAMEnlxXJodz/3f7+bN5/gyRKEZw
aZPF+smKeRpuYMCeQht5hukOAy8UlXckOomRpWfS6f3Z6c0Vd9eCdmf27jabz8xa
Cv30WVup685ffE+pJABdMRmP4dtqqk/6p5PdkX4lREHrF3HIwQMRO/mjbOiPHgAr
cgmTAKQAUgCv4rEhOsiTfyaKbVM+xGM6SNe4PueT/YJYw928MDSHvFIiKJPldvIp
g7J+WtdwTEoPiYuLvA8CzknLWTRgK2+J5jqtnmFG5DU0zaOeqhnK/5IqLxD+TufV
0SBgxqcnWmk/C3bCNJcSfF557dkpPEKcal4xVJMOuSTe7P9iPzyhB3zDVL07MRPG
67U+DpMu7BEOR4zM52jO
=nKXd
-END PGP SIGNATURE End Message ---

Bug#840666: marked as done (firebird3.0: FTBFS on powerpc, segfaults during build)

[Debian Bug Tracking System]

Your message dated Thu, 13 Oct 2016 22:50:17 +
with message-id 
and subject line Bug#840666: fixed in firebird3.0 3.0.1.32609.ds4-7
has caused the Debian Bug report #840666,
regarding firebird3.0: FTBFS on powerpc, segfaults during build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firebird3.0
Version: 3.0.1.32609.ds4-6
Severity: serious
Tags: upstream
Justification: fails to build from source
User: debian-powe...@lists.debian.org
Usertags: powerpc

Hello!

firebird3.0 currently fails to build from source since the gpre
command segfaults during build:

sh -x -c "lockfile -1 /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock && 
/«PKGBUILDDIR»/gen/Release/firebird/bin/gpre_current -m -z -n 
/«PKGBUILDDIR»/src/yvalve/blob.epp /«PKGBUILDDIR»/temp/Release/yvalve/blob.cpp; 
res=\$?; rm -f /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock; exit 
\$res"
+ lockfile -1 /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock
+ /«PKGBUILDDIR»/gen/Release/firebird/bin/gpre_current -m -z -n 
/«PKGBUILDDIR»/src/yvalve/blob.epp /«PKGBUILDDIR»/temp/Release/yvalve/blob.cpp
gpre version LI-V3.0.1.32609 Firebird 3.0
Segmentation fault
+ res=139
+ rm -f /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock
+ exit 139

I have done some debugging and from the backtrace it's obvious that
the crash occurs in glibc:

(sid_powerpc-dchroot)glaubitz@partch:~/firebird3.0-3.0.1.32609.ds4$ gdb 
/home/glaubitz/firebird3.0-3.0.1.32609.ds4/gen/Release/firebird/bin/gpre_boot
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/home/glaubitz/firebird3.0-3.0.1.32609.ds4/gen/Release/firebird/bin/gpre_boot...done.
(gdb) run
Starting program: 
/home/glaubitz/firebird3.0-3.0.1.32609.ds4/gen/Release/firebird/bin/gpre_boot
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
gpre:  no source file named.

Program received signal SIGSEGV, Segmentation fault.
0x0fa79960 in _IO_wsetb () from /lib/powerpc-linux-gnu/libc.so.6
(gdb) bt
#0  0x0fa79960 in _IO_wsetb () from /lib/powerpc-linux-gnu/libc.so.6
#1  0x0fa88dac in ?? () from /lib/powerpc-linux-gnu/libc.so.6
#2  0x0fa3cd58 in ?? () from /lib/powerpc-linux-gnu/libc.so.6
#3  0x0fa3ce30 in exit () from /lib/powerpc-linux-gnu/libc.so.6
#4  0x10027f28 in CPR_exit (stat=263831632) at ./src/gpre/gpre.cpp:978
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)

This looks similar to the FTBFS of lua5.3 on powerpc [1] which is
triggered by the use of a version script for the linker and, in
fact, firebird3.0 is using such scripts. Now, this actually reminded
me of another similar problem we had on sparc back then [2] which
is the missing _IO_stdin_used symbol in the version script. lua5.2
was affected by that problem as well and Aurelien Jarno fixed that
by adding that symbol to the version script [3].

I tried the fix from [3] in firebird3.0, but unfortunately it
doesn't help. Currently, I'm out of ideas but it would be great
to see this fixed as this also affects m68k for which I have
added platform support to firebird upstream [4,5].

Thanks,

Adrian

> [1] https://bugs.launchpad.net/ubuntu/+source/lua5.3/+bug/1570055
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634261
> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816059
> [4] https://github.com/FirebirdSQL/firebird/pull/51
> [5] https://github.com/FirebirdSQL/firebird/pull/52

--
 .''`.  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
--- End Message ---
--- Begin Message ---
Source: firebird3.0
Source-Version: 

Bug#840107: marked as done (beignet: FTBFS with libdrm-intel 2.4.71)

[Debian Bug Tracking System]

Your message dated Thu, 13 Oct 2016 22:49:58 +
with message-id 
and subject line Bug#840107: fixed in beignet 1.2.0-2
has caused the Debian Bug report #840107,
regarding beignet: FTBFS with libdrm-intel 2.4.71
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: beignet
Severity: serious
Control: tags -1 upstream patch

beignet started using drm_intel_get_pooled_eu and 
drm_intel_get_min_eu_in_pool if available early in their development, 
before their interface was finalized, and hence does not build with the 
released version (libdrm-intel 2.4.71).


A fix is being discussed upstream:
https://lists.freedesktop.org/archives/beignet/2016-October/008053.html

[ 29%] Building C object src/CMakeFiles/cl.dir/intel/intel_driver.c.o
cd /tmp/buildd/beignet-1.2.0/obj-x86_64-linux-gnu/src && 
/usr/lib/ccache/cc  -DGEN7_SAMPLER_CLAMP_BORDER_WORKAROUND -DLLVM_38 
-Dcl_EXPORTS -I/tmp/buildd/beignet-1.2.0/obj-x86_64-linux-gnu 
-I/tmp/buildd/beignet-1.2.0 -I/tmp/buildd/beignet-1.2.0/include 
-I/usr/include/libdrm -I/tmp/buildd/beignet-1.2.0/src 
-I/usr/include/libdrm/.. 
-I/tmp/buildd/beignet-1.2.0/src/../backend/src/backend 
-I/tmp/buildd/beignet-1.2.0/src/../include -I/usr/lib/llvm-3.8/include 
-DHAS_MIN_EU_IN_POOL -DHAS_POOLED_EU -DHAS_SUBSLICE_TOTAL -DHAS_EU_TOTAL 
-DHAS_USERPTR -DHAS_OCLIcd -DHAS_X11 -g -O2 
-fdebug-prefix-map=/tmp/buildd/beignet-1.2.0=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DGBE_DEBUG=1   -funroll-loops -fstrict-aliasing 
-fPIC -Wall -Wcast-align -Wl,-E -fPIC   -o 
CMakeFiles/cl.dir/intel/intel_driver.c.o   -c 
/tmp/buildd/beignet-1.2.0/src/intel/intel_driver.c
/tmp/buildd/beignet-1.2.0/src/intel/intel_driver.c: In function 
'intel_update_device_info':
/tmp/buildd/beignet-1.2.0/src/intel/intel_driver.c:893:7: error: too 
many arguments to function 'drm_intel_get_pooled_eu'
if(!drm_intel_get_pooled_eu(driver->fd, _pooled_eu) && 
has_pooled_eu)

^~~
In file included from 
/tmp/buildd/beignet-1.2.0/src/intel/intel_driver.h:56:0,
  from 
/tmp/buildd/beignet-1.2.0/src/intel/intel_driver.c:60:

/usr/include/libdrm/intel_bufmgr.h:276:5: note: declared here
  int drm_intel_get_pooled_eu(int fd);
  ^~~
/tmp/buildd/beignet-1.2.0/src/intel/intel_driver.c:899:25: error: too 
many arguments to function 'drm_intel_get_min_eu_in_pool'
if (has_pooled_eu && !drm_intel_get_min_eu_in_pool(driver->fd, 
_eu)) {

  ^~~~
In file included from 
/tmp/buildd/beignet-1.2.0/src/intel/intel_driver.h:56:0,
  from 
/tmp/buildd/beignet-1.2.0/src/intel/intel_driver.c:60:

/usr/include/libdrm/intel_bufmgr.h:277:5: note: declared here
  int drm_intel_get_min_eu_in_pool(int fd);
  ^~~~
src/CMakeFiles/cl.dir/build.make:1673: recipe for target 
'src/CMakeFiles/cl.dir/intel/intel_driver.c.o' failed

make[4]: *** [src/CMakeFiles/cl.dir/intel/intel_driver.c.o] Error 1
--- End Message ---
--- Begin Message ---
Source: beignet
Source-Version: 1.2.0-2

We believe that the bug you reported is fixed in the latest version of
beignet, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rebecca N. Palmer  (supplier of updated beignet 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 13 Oct 2016 19:28:41 +0100
Source: beignet
Binary: beignet-opencl-icd beignet-dev beignet
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers 
Changed-By: Rebecca N. Palmer 
Description:
 beignet- OpenCL library for Intel GPUs - transitional dummy package
 beignet-dev - OpenCL for Intel GPUs (development files and documentation)
 beignet-opencl-icd - OpenCL 

Bug#840692: nemo-python: plugin is not recognized or loaded by Nemo

[Nathan Osman]

Package: nemo-python
Version: 3.0.0-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The nemo-python extension is not displayed in the "Extensions" list under
Edit->Plugins. This is further confirmed by the fact that none of the Python
extensions I have installed work. Running Nemo under KDE, Gnome, and Cinnamon
doesn't appear to make any difference.


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

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

Versions of packages nemo-python depends on:
ii  gir1.2-nemo-3.0  3.0.6-3
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-3
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.1-1
ii  libgtk-3-0   3.22.1-1
ii  libnemo-extension1   3.0.6-3
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpython2.7 2.7.12-3+b1

nemo-python recommends no packages.

nemo-python suggests no packages.

-- no debconf information

Bug#840691: libgs9: security update DSA-3691-1 breaks zathura, evince, ... in jessie

[Francesco Poli (wintermute)]

Package: libgs9
Version: 9.06~dfsg-2+deb8u3
Severity: grave
Tags: security
Justification: renders package unusable

Hello!

I had a bad surprise today in jessie.
After the security update:

  [UPGRADE] libgs9:amd64 9.06~dfsg-2+deb8u1 -> 9.06~dfsg-2+deb8u3
  [UPGRADE] libgs9-common:amd64 9.06~dfsg-2+deb8u1 -> 9.06~dfsg-2+deb8u3

I was unable to use zathura or evince (maybe other PS viewers are
affected):

  $ zathura foo.eps
  warning: Failed to loads bookmarks.
  invalidaccess -7
  error: Rendering failed (page 1)
  $ evince foo.eps
  invalidaccess -7
  invalidaccess -7
  Segmentation fault

After downgrading back to libgs9/9.06~dfsg-2+deb8u1 and
libgs9-common/9.06~dfsg-2+deb8u1, everything is back to normal
and the two PS viewers work again.

What went wrong?
If this is indeed a regression (as it seems to be), please fix it
as soon as possible!

Thanks for your time.


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

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

Versions of packages libgs9 depends on:
ii  libc6   2.19-18+deb8u6
ii  libcups21.7.5-11+deb8u1
ii  libcupsimage2   1.7.5-11+deb8u1
ii  libfontconfig1  2.11.0-6.3+deb8u1
ii  libfreetype62.5.2-3+deb8u1
ii  libgs9-common   9.06~dfsg-2+deb8u3
ii  libidn111.29-1+deb8u2
ii  libijs-0.35 0.35-10
ii  libjasper1  1.900.1-debian1-2.4+deb8u1
ii  libjbig2dec00.11+20120125-1
ii  libjpeg62-turbo 1:1.3.1-12
ii  liblcms2-2  2.6-3+b3
ii  libpaper1   1.1.24+nmu4
ii  libpng12-0  1.2.50-2+deb8u2
ii  libtiff54.0.3-12.3+deb8u1
ii  poppler-data [gs-cjk-resource]  0.4.7-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

libgs9 recommends no packages.

libgs9 suggests no packages.

-- no debconf information

Bug#839884: [Pkg-utopia-maintainers] Bug#839884: network-manager: Confirmed here

[Manuel Bilderbeek]

Hi,

It just happened again, apparently a new version got in testing:
Unpacking network-manager (1.4.2-1+b1) over (1.4.2-1) ...

and it still hangs;
Setting up network-manager (1.4.2-1+b1) ...



The information you requested:

$ systemctl status NetworkManager-dispatcher.service
● NetworkManager-dispatcher.service - Network Manager Script Dispatcher 
Service
   Loaded: loaded 
(/lib/systemd/system/NetworkManager-dispatcher.service; enable

   Active: inactive (dead)

ps output again:

root  7664  4248  0 23:18 pts/100:00:00 /usr/bin/dpkg 
--status-fd 80 --no-triggers --configure --pending
root  8266  7664  0 23:19 pts/100:00:00 /bin/sh 
/var/lib/dpkg/info/network-manager.postinst configure 1.4.2-1
root  8332 1  0 23:19 ?00:00:00 /usr/sbin/NetworkManager 
--no-daemon
root  8419  8266  0 23:19 pts/100:00:00 /bin/systemctl 
try-restart NetworkManager-dispatcher.service
root  8423  8419  0 23:19 pts/100:00:00 
/bin/systemd-tty-ask-password-agent --watch



HTH!

On 06-10-16 23:37, Michael Biebl wrote:

Am 06.10.2016 um 21:42 schrieb Manuel Bilderbeek:

Package: network-manager
Version: 1.4.2-1
Followup-For: Bug #839884

Dear Maintainer,

I also see the hangup:

Setting up libkf5widgetsaddons-data (5.26.0-1) ...
Setting up network-manager (1.4.2-1) ...

and then nothing. ps -Af says:

root  4897  2663  0 21:35 pts/200:00:00 /usr/bin/dpkg --status-fd 80 
--configure --pending
root  4906  4897  0 21:35 pts/200:00:00 /bin/sh 
/var/lib/dpkg/info/network-manager.postinst configure 1.4.0-4
root  4972 1  0 21:35 ?00:00:00 /usr/sbin/NetworkManager 
--no-daemon
root  5060  4906  0 21:35 pts/200:00:00 /bin/systemctl try-restart 
NetworkManager-dispatcher.service
root  5061  5060  0 21:35 pts/200:00:00 
/bin/systemd-tty-ask-password-agent --watch



What's the output of systemctl status NetworkManager-dispatcher.service


--
Grtjs, Manuel

Bug#840685: tomcat8: DSA-3670 incomplete

[paul . szabo]

Dear Markus,

>> [ I contacted t...@security.debian.org about this, but no response ... ]
> ... Please send them to the security team
> first and not to a public mailing list.

I did. They did not reply within what seemed a reasonable timeframe.

>> Recently DSA-3670 was released, and /etc/init.d/tomcat8 modified so...
> No, we did not modify this part in /etc/init.d/tomcat8. ...

Whoops, sorry, you are right. Now checking, I do not see how I got
confused. This is a separate, maybe new issue.

> ... more information and a working proof
> of concept code are appreciated. ...

Maybe the security team will understand (recognize, accept) the issue
without a PoC. If they reply with such a need, then I will write one.

You or they might accept the suggested patch/fix: mkdir without -p,
chown with -h.

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia

Processed: bug 840689 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=118371

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 840689 https://rt.cpan.org/Ticket/Display.html?id=118371
Bug #840689 [libterm-readline-gnu-perl] libterm-readline-gnu-perl: FTBFS on 
64-bit big endian architectures
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=118371'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840690: ruby-foreman: FTBFS: Failed examples: rspec ./spec/foreman/export/inittab_spec.rb:17 # Foreman::Export::Inittab exports to the filesystem

[Chris Lamb]

Source: ruby-foreman
Version: 0.82.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-foreman fails to build from source in unstable/amd64:

  [..]

NoMethodError:
  undefined method `stub' for 
#
# /usr/lib/ruby/vendor_ruby/rspec/matchers.rb:967:in `method_missing'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:747:in 
`method_missing'
# ./spec/foreman/export/upstart_spec.rb:14:in `block (2 levels) in '
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:443:in `instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:443:in `instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:350:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:507:in `block in 
run_owned_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:506:in `each'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:506:in 
`run_owned_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:593:in `block in 
run_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:592:in `reverse_each'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:592:in 
`run_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:462:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:490:in 
`run_before_example'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:253:in `block in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in `block in 
with_around_and_singleton_context_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in `block in 
with_around_example_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `block in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:602:in 
`run_around_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in 
`with_around_example_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in 
`with_around_and_singleton_context_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:627:in `block 
in run_examples'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in 
`run_examples'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:589:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `block 
in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (3 
levels) in run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (2 
levels) in run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1835:in 
`with_suite_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:112:in `block in 
run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:77:in `report'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:111:in `run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
# /usr/bin/rspec:4:in `'
  
37) Foreman::Export::Upstart with a formation exports to the filesystem 
with concurrency
Failure/Error: before(:each) { stub(upstart).say }
  
NoMethodError:
  undefined method `stub' for 
#
# /usr/lib/ruby/vendor_ruby/rspec/matchers.rb:967:in `method_missing'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:747:in 
`method_missing'
# ./spec/foreman/export/upstart_spec.rb:14:in `block (2 levels) in '
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:443:in `instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:443:in `instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:350:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:507:in `block in 
run_owned_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:506:in `each'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:506:in 
`run_owned_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:593:in `block in 
run_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:592:in `reverse_each'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:592:in 
`run_example_hooks_for'
# 

Bug#840685: tomcat8: DSA-3670 incomplete

[Markus Koschany]

On 13.10.2016 22:22, Paul Szabo wrote:
> Package: tomcat8
> Version: 8.0.14-1+deb8u3
> Severity: critical
> Tags: security
> Justification: root security hole
> 
> 
> [ I contacted t...@security.debian.org about this, but no response ... ]

I am CCing the security team in case they want to chime in here.

> 
> Recently DSA-3670 was released, and /etc/init.d/tomcat8 modified so:
> 
> ...
> NAME=tomcat8
> ...
> JVM_TMP=/tmp/tomcat8-$NAME-tmp
> ...
>   # Remove / recreate JVM_TMP directory
>   rm -rf "$JVM_TMP"
>   mkdir -p "$JVM_TMP" || {
>   log_failure_msg "could not create JVM temporary 
> directory"
>   exit 1
>   }
>   chown $TOMCAT8_USER "$JVM_TMP"
> ...

No, we did not modify this part in /etc/init.d/tomcat8. We fixed
CVE-2016-1240 by applying this patch

https://anonscm.debian.org/cgit/pkg-java/tomcat8.git/commit/?h=jessie=9a9fd4f1cae13304beed6d4e445d1be8a3917fe0


> That suffers from a TOCTOU race condition.
> 
> An attacker can, after the "rm -rf", create a symlink to /etc. Then
> "mkdir -p" returns success (though does nothing); and chown follows
> the symlink. That is "game over": ability to replace /etc/passwd.
> 
> The attacker can use inotify and act quickly, and have a good chance
> of winning the race to create the symlink before the init.d script
> starts a new mkdir process.
> 
> Do you need some working PoC code?

I don't understand how this affects our solution for CVE-2016-1240. If
you claim this is a new issue, then more information and a working proof
of concept code are appreciated. Please send them to the security team
first and not to a public mailing list.





signature.asc
Description: OpenPGP digital signature

Bug#840689: libterm-readline-gnu-perl: FTBFS on 64-bit big endian architectures

[Emilio Pozuelo Monfort]

Package: libterm-readline-gnu-perl
Version: 1.34-1
Severity: serious

Hi,

On a rebuild against libreadline7, your package failed to build on
big-endian, 64-bit architectures:

# 2.4 History Variables
ok 86 - history_inhibit_expansion_function
ok 87
ok 88
ok
Use of uninitialized value in string eq at t/readline.t line 119.
Use of uninitialized value in string eq at t/readline.t line 119.

#   Failed test 'readline_state'
#   at t/readline.t line 152.

Full logs at:

https://buildd.debian.org/status/package.php?p=libterm-readline-gnu-perl

Emilio

Processed: Re: xul-ext-nosquint is dead, long live nosquint

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 840569 nosquint should not be in stretch
Bug #840569 [src:nosquint] xul-ext-nosquint is dead, long live nosquint
Changed Bug title to 'nosquint should not be in stretch' from 'xul-ext-nosquint 
is dead, long live nosquint'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: limit source to firebird3.0, tagging 840666, tagging 840684

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source firebird3.0
Limiting to bugs with field 'source' containing at least one of 'firebird3.0'
Limit currently set to 'source':'firebird3.0'

> tags 840666 + pending
Bug #840666 [src:firebird3.0] firebird3.0: FTBFS on powerpc, segfaults during 
build
Added tag(s) pending.
> tags 840684 + pending
Bug #840684 [src:firebird3.0] firebird3.0: Please add patch to add m68k 
platform support
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840666
840684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840685: tomcat8: DSA-3670 incomplete

[Paul Szabo]

Package: tomcat8
Version: 8.0.14-1+deb8u3
Severity: critical
Tags: security
Justification: root security hole


[ I contacted t...@security.debian.org about this, but no response ... ]

Recently DSA-3670 was released, and /etc/init.d/tomcat8 modified so:

...
NAME=tomcat8
...
JVM_TMP=/tmp/tomcat8-$NAME-tmp
...
# Remove / recreate JVM_TMP directory
rm -rf "$JVM_TMP"
mkdir -p "$JVM_TMP" || {
log_failure_msg "could not create JVM temporary 
directory"
exit 1
}
chown $TOMCAT8_USER "$JVM_TMP"
...

That suffers from a TOCTOU race condition.

An attacker can, after the "rm -rf", create a symlink to /etc. Then
"mkdir -p" returns success (though does nothing); and chown follows
the symlink. That is "game over": ability to replace /etc/passwd.

The attacker can use inotify and act quickly, and have a good chance
of winning the race to create the symlink before the init.d script
starts a new mkdir process.

Do you need some working PoC code?

---

The script should be made more robust by using "chown -h". (This would
protect against the above attack.)

The script should use plain mkdir without "-p": not needed as we create
a single directory, and should not be used to let mkdir return failure.
(This may make it safe.)

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia



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

Kernel: Linux 3.16.36-pk07.24-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages tomcat8 depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.56
ii  tomcat8-common 8.0.14-1+deb8u3
ii  ucf3.0030

Versions of packages tomcat8 recommends:
pn  authbind  

Versions of packages tomcat8 suggests:
pn  libtcnative-1 
pn  tomcat8-admin 
pn  tomcat8-docs  
pn  tomcat8-examples  
pn  tomcat8-user  

-- Configuration Files:
/etc/init.d/tomcat8 changed [not included]
/etc/tomcat8/catalina.properties [Errno 13] Permission denied: 
u'/etc/tomcat8/catalina.properties'
/etc/tomcat8/context.xml [Errno 13] Permission denied: 
u'/etc/tomcat8/context.xml'
/etc/tomcat8/logging.properties [Errno 13] Permission denied: 
u'/etc/tomcat8/logging.properties'
/etc/tomcat8/policy.d/01system.policy [Errno 13] Permission denied: 
u'/etc/tomcat8/policy.d/01system.policy'
/etc/tomcat8/policy.d/02debian.policy [Errno 13] Permission denied: 
u'/etc/tomcat8/policy.d/02debian.policy'
/etc/tomcat8/policy.d/03catalina.policy [Errno 13] Permission denied: 
u'/etc/tomcat8/policy.d/03catalina.policy'
/etc/tomcat8/policy.d/04webapps.policy [Errno 13] Permission denied: 
u'/etc/tomcat8/policy.d/04webapps.policy'
/etc/tomcat8/policy.d/50local.policy [Errno 13] Permission denied: 
u'/etc/tomcat8/policy.d/50local.policy'
/etc/tomcat8/server.xml [Errno 13] Permission denied: u'/etc/tomcat8/server.xml'
/etc/tomcat8/tomcat-users.xml [Errno 13] Permission denied: 
u'/etc/tomcat8/tomcat-users.xml'
/etc/tomcat8/web.xml [Errno 13] Permission denied: u'/etc/tomcat8/web.xml'

-- debconf information excluded

Bug#840679: [pkg-lxqt-devel] Bug#840679: {qterminal, libfm-qt, liblxqt}-l10n: fails to upgrade from 'sid' - trying to overwrite /usr/share/*/translations/*.qm

[Alf Gaida]

Good catch, thank you very much - the breaks and replaces was in place, 
but some package names and versions

was messed up.

Cheers Alf

Bug#840571: marked as done (python-txaio: FTBFS (ValueError: Empty module name))

[Debian Bug Tracking System]

Your message dated Thu, 13 Oct 2016 19:50:31 +
with message-id 
and subject line Bug#840571: fixed in python-txaio 
2.5.1+2016.10.03.git.623ef68776-1
has caused the Debian Bug report #840571,
regarding python-txaio: FTBFS (ValueError: Empty module name)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-txaio
Version: 2.5.1-2
Severity: serious

Dear maintainer:

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


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

[... snipped ...]

_reraise(*ex)  # noqa
  File "/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", 
line 264, in __init__
self.result = func()
  File "/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", 
line 596, in execute
res = hook_impl.function(*args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 882, in 
pytest_cmdline_parse
self.parse(args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 1032, in parse
self._preparse(args, addopts=addopts)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 1003, in 
_preparse
args=args, parser=self._parser)
  File "/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", 
line 724, in __call__
return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
  File "/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", 
line 338, in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
  File "/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", 
line 333, in 
_MultiCall(methods, kwargs, hook.spec_opts).execute()
  File "/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", 
line 595, in execute
return _wrapped_call(hook_impl.function(*args), self.execute)
  File "/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", 
line 253, in _wrapped_call
return call_outcome.get_result()
  File "/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", 
line 279, in get_result
_reraise(*ex)  # noqa
  File "/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", 
line 264, in __init__
self.result = func()
  File "/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", 
line 596, in execute
res = hook_impl.function(*args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 928, in 
pytest_load_initial_conftests
self.pluginmanager._set_initial_conftests(early_config.known_args_namespace)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 287, in 
_set_initial_conftests
self._try_load_conftest(current)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 295, in 
_try_load_conftest
self._getconftestmodules(x)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 315, in 
_getconftestmodules
mod = self._importconftest(conftestpath)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 351, in 
_importconftest
self.consider_conftest(mod)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 375, in 
consider_conftest
self.consider_module(conftestmodule)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 385, in 
consider_module
self._import_plugin_specs(plugins)
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 392, in 
_import_plugin_specs
self.import_plugin(import_spec)
  File 

Bug#840666: firebird3.0: FTBFS on powerpc, segfaults during build

[John Paul Adrian Glaubitz]

On 10/13/2016 09:38 PM, John Paul Adrian Glaubitz wrote:
> On 10/13/2016 09:36 PM, Damyan Ivanov wrote:
>>> PS: If you agree, I can NMU the fixed package using the patch I just 
>>> posted right away to fix the bug :).
>>
>> I'll upload soon (hours) anyway because of a fix for kfreebsd.
> 
> Alright, thanks.

Oh, and could I ask you for an additional favor? Could please add the attached
patch to add platform support for Linux/m68k? I would highly appreciate that!

Thanks,
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
Description: Add platform support for Linux/m68k
Author: John Paul Adrian Glaubitz 

--- firebird3.0-3.0.1.32609.ds4.orig/configure.ac
+++ firebird3.0-3.0.1.32609.ds4/configure.ac
@@ -361,6 +361,17 @@ dnl CPU_TYPE=ppc64
SHRLIB_EXT=so
;;
 
+  m68k*-*-linux*)
+   MAKEFILE_PREFIX=linux_generic
+   INSTALL_PREFIX=linux
+   PLATFORM=LINUX
+   AC_DEFINE(LINUX, 1, [Define this if OS is Linux])
+   AC_DEFINE(M68K, 1, [Define this if CPU is M68k])
+   LOCK_MANAGER_FLG=Y
+   EDITLINE_FLG=Y
+   SHRLIB_EXT=so
+   ;;
+
   *-*-linux* | *-*-gnu*)
 MAKEFILE_PREFIX=linux_generic
 INSTALL_PREFIX=linux
@@ -997,10 +1008,11 @@ AC_CHECK_MEMBER([struct dirent.d_type],
 dnl EKU: try to determine the alignment of long and double
 dnl  replaces FB_ALIGNMENT and FB_DOUBLE_ALIGN in src/jrd/common.h
 AC_MSG_CHECKING(alignment of long)
-AC_RUN_IFELSE([AC_LANG_SOURCE([[main () {
+AC_RUN_IFELSE([AC_LANG_SOURCE([[#include 
+main () {
   struct s {
 char a;
-long long b;
+union { long long x; sem_t y; } b;
   };
   exit((int)&((struct s*)0)->b);
 }]])],[ac_cv_c_alignment=$ac_status],[ac_cv_c_alignment=$ac_status],[])
--- firebird3.0-3.0.1.32609.ds4.orig/src/common/classes/DbImplementation.cpp
+++ firebird3.0-3.0.1.32609.ds4/src/common/classes/DbImplementation.cpp
@@ -48,6 +48,7 @@ static const UCHAR CpuHppa = 13;
 static const UCHAR CpuAlpha = 14;
 static const UCHAR CpuArm64 = 15;
 static const UCHAR CpuPowerPc64el = 16;
+static const UCHAR CpuM68k = 17;
 
 static const UCHAR OsWindows = 0;
 static const UCHAR OsLinux = 1;
@@ -87,7 +88,8 @@ const char* hardware[] = {
 	"HPPA",
 	"Alpha",
 	"ARM64",
-	"PowerPC64el"
+	"PowerPC64el",
+	"M68k"
 };
 
 const char* operatingSystem[] = {
@@ -128,8 +130,8 @@ const UCHAR backwardTable[FB_NELEM(hardw
 
 const UCHAR backEndianess[FB_NELEM(hardware)] =
 {
-//	Intel	AMD		Sparc	PPC		PPC64	MIPSEL	MIPS	ARM		IA64	s390	s390x	SH		SHEB	HPPA	Alpha	ARM64	PowerPC64el
-	0,		0,		1,		1,		1,		0,		1,		0,		0,		1,		1,		0,		1,		1,		0,		0,		0
+//	Intel	AMD		Sparc	PPC		PPC64	MIPSEL	MIPS	ARM		IA64	s390	s390x	SH		SHEB	HPPA	Alpha	ARM64	PowerPC64el	M68k
+   0,		0,		1,		1,		1,		0,		1,		0,		0,		1,		1,		0,		1,		1,		0,		0,		0,		1
 };
 
 } // anonymous namespace
--- firebird3.0-3.0.1.32609.ds4.orig/src/common/common.h
+++ firebird3.0-3.0.1.32609.ds4/src/common/common.h
@@ -195,6 +195,10 @@
 #define FB_CPU CpuPowerPc64
 #endif /* PPC64 */
 
+#ifdef M68K
+#define FB_CPU CpuM68k
+#endif /* M68K */
+
 #endif /* LINUX */
 
 
--- firebird3.0-3.0.1.32609.ds4.orig/src/jrd/inf_pub.h
+++ firebird3.0-3.0.1.32609.ds4/src/jrd/inf_pub.h
@@ -241,6 +241,7 @@ enum  info_db_implementations
 	isc_info_db_impl_linux_arm64 = 84,
 	isc_info_db_impl_linux_ppc64el = 85,
 	isc_info_db_impl_linux_ppc64 = 86,
+	isc_info_db_impl_linux_m68k = 87,
 
 
 	isc_info_db_impl_last_value   // Leave this LAST!


signature.asc
Description: OpenPGP digital signature

Bug#840666: firebird3.0: FTBFS on powerpc, segfaults during build

[John Paul Adrian Glaubitz]

On 10/13/2016 09:36 PM, Damyan Ivanov wrote:
>> PS: If you agree, I can NMU the fixed package using the patch I just 
>> posted right away to fix the bug :).
> 
> I'll upload soon (hours) anyway because of a fix for kfreebsd.

Alright, thanks.

Btw, my patch might actually fix mips64el as well, see [1].

Adrian

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

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



signature.asc
Description: OpenPGP digital signature

Bug#840666: firebird3.0: FTBFS on powerpc, segfaults during build

[Damyan Ivanov]

-=| John Paul Adrian Glaubitz, 13.10.2016 21:30:14 +0200 |=-
> On 10/13/2016 09:29 PM, John Paul Adrian Glaubitz wrote:
> > It has to be added to the script template in build/posix/vers.sh.in. I'm
> > attaching a complete debdiff which fixes the issue for me in powerpc. I
> > have also opened two PRs upstream, these also include patches for m68k
> > and an additional patch.

Great. Thanks!

> PS: If you agree, I can NMU the fixed package using the patch I just 
> posted right away to fix the bug :).

I'll upload soon (hours) anyway because of a fix for kfreebsd.

-- Damyan


signature.asc
Description: Digital signature

Processed: Re: Bug#833741: pepperflashplugin-nonfree: Feature request?: Download from Adobe instead of Google.

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 833741 grave
Bug #833741 [pepperflashplugin-nonfree] pepperflashplugin-nonfree: Feature 
request?: Download from Adobe instead of Google.
Severity set to 'grave' from 'wishlist'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
833741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840666: firebird3.0: FTBFS on powerpc, segfaults during build

[John Paul Adrian Glaubitz]

On 10/13/2016 09:29 PM, John Paul Adrian Glaubitz wrote:
> It has to be added to the script template in build/posix/vers.sh.in. I'm
> attaching a complete debdiff which fixes the issue for me in powerpc. I
> have also opened two PRs upstream, these also include patches for m68k
> and an additional patch.

PS: If you agree, I can NMU the fixed package using the patch I just posted
right away to fix the bug :).

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



signature.asc
Description: OpenPGP digital signature

Bug#840666: firebird3.0: FTBFS on powerpc, segfaults during build

[John Paul Adrian Glaubitz]

Hi Damyan!

On 10/13/2016 09:09 PM, Damyan Ivanov wrote:
> -=| John Paul Adrian Glaubitz, 13.10.2016 18:35:31 +0200 |=-
>> Source: firebird3.0
>> Version: 3.0.1.32609.ds4-6
>> Severity: serious
> 
> Shouldn't this be important instead? According to 
> https://release.debian.org/stretch/arch_qualify.html powerpc is not 
> a release candidate.

Well, currently, powerpc is still a release architecture, so I set the severity
accordingly. Also, I'm quite confident that mips64el is failing because of the
same problem.

> Of course, I am eager to find solution to the crash regardless, just 
> arguing about it affecting the potential migration of firebird3.0 to 
> testing.

I found the issue :), see below.

> Where did you add that _IO_stdin_used entry? There are several *.vers 
> files in the source. I'll try with all of them and also 
> _IO_std{err,out}_used.

It has to be added to the script template in build/posix/vers.sh.in. I'm
attaching a complete debdiff which fixes the issue for me in powerpc. I
have also opened two PRs upstream, these also include patches for m68k
and an additional patch.

Cheers,
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
diff -Nru firebird3.0-3.0.1.32609.ds4/debian/changelog firebird3.0-3.0.1.32609.ds4/debian/changelog
--- firebird3.0-3.0.1.32609.ds4/debian/changelog	2016-10-12 10:57:51.0 +0200
+++ firebird3.0-3.0.1.32609.ds4/debian/changelog	2016-10-13 21:04:46.0 +0200
@@ -1,3 +1,11 @@
+firebird3.0 (3.0.1.32609.ds4-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add fix-version-script.patch to patch linker version script
+to export the _IO_stdin_used symbol (Closes: #840666)
+
+ -- John Paul Adrian Glaubitz   Thu, 13 Oct 2016 21:04:46 +0200
+
 firebird3.0 (3.0.1.32609.ds4-6) unstable; urgency=medium
 
   * add RuntimeDirectory= to server's service files
diff -Nru firebird3.0-3.0.1.32609.ds4/debian/patches/fix-version-script.patch firebird3.0-3.0.1.32609.ds4/debian/patches/fix-version-script.patch
--- firebird3.0-3.0.1.32609.ds4/debian/patches/fix-version-script.patch	1970-01-01 01:00:00.0 +0100
+++ firebird3.0-3.0.1.32609.ds4/debian/patches/fix-version-script.patch	2016-10-13 21:04:42.0 +0200
@@ -0,0 +1,13 @@
+Description: Fix version script to export the _IO_stdin_used symbol
+Author: John Paul Adrian Glaubitz 
+
+--- firebird3.0-3.0.1.32609.ds4.orig/builds/posix/vers.sh.in
 firebird3.0-3.0.1.32609.ds4/builds/posix/vers.sh.in
+@@ -57,6 +57,7 @@ platform_linux() {
+ 		echo "${TAB}$i;"
+ 	done
+ 
++	echo "${TAB}_IO_stdin_used;"
+ 	echo 'local:'
+ 	echo "${TAB}*;"
+ 	echo '};'
diff -Nru firebird3.0-3.0.1.32609.ds4/debian/patches/series firebird3.0-3.0.1.32609.ds4/debian/patches/series
--- firebird3.0-3.0.1.32609.ds4/debian/patches/series	2016-10-05 12:59:43.0 +0200
+++ firebird3.0-3.0.1.32609.ds4/debian/patches/series	2016-10-13 21:03:39.0 +0200
@@ -10,3 +10,4 @@
 packaged-boost.patch
 deb/no-suse.init.patch
 deb/gen-ids.patch
+fix-version-script.patch


signature.asc
Description: OpenPGP digital signature

Bug#840394: motif: FTBFS: relocation R_X86_64_PC32 against symbol `exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC

[Graham Inggs]

Hi Bas

On 13 October 2016 at 20:07, Sebastiaan Couwenberg  wrote:
> Are you sure about that timing?

I'm not sure exactly when that is happening.

> The failed motif builds are preventing the grass rebuilds for the
> readline7 transition (#838234), waiting for the above may not be such a
> good idea.

Waiting for the GCC6 upload enabling PIE by default can be avoided by
fixing #837658 directly, i.e. by uploading flex with
DEB_BUILD_MAINT_OPTIONS=hardening=+all, or similar.

Regards
Graham

Bug#840679: {qterminal, libfm-qt, liblxqt}-l10n: fails to upgrade from 'sid' - trying to overwrite /usr/share/*/translations/*.qm

[Andreas Beckmann]

Package: qterminal-l10n,libfm-qt-l10n,liblxqt-l10n
Version: 0.11.0-19-g717bd7e-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package qterminal-l10n.
  Preparing to unpack .../2-qterminal-l10n_0.11.0-19-g717bd7e-1_all.deb ...
  Unpacking qterminal-l10n (0.11.0-19-g717bd7e-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-rCQMhn/2-qterminal-l10n_0.11.0-19-g717bd7e-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/qterminal/translations/qterminal_cs.qm', 
which is also in package qterminal 0.6.1~102-g58f4f72-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-rCQMhn/2-qterminal-l10n_0.11.0-19-g717bd7e-1_all.deb

  Selecting previously unselected package libfm-qt-l10n.
  Preparing to unpack .../2-libfm-qt-l10n_0.11.0-19-g717bd7e-1_all.deb ...
  Unpacking libfm-qt-l10n (0.11.0-19-g717bd7e-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Q6Pam2/2-libfm-qt-l10n_0.11.0-19-g717bd7e-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/libfm-qt/translations/libfm-qt_ar.qm', which 
is also in package libfm-qt3:amd64 0.11.0-2+b1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Q6Pam2/2-libfm-qt-l10n_0.11.0-19-g717bd7e-1_all.deb

  Selecting previously unselected package liblxqt-l10n.
  Preparing to unpack .../2-liblxqt-l10n_0.11.0-19-g717bd7e-1_all.deb ...
  Unpacking liblxqt-l10n (0.11.0-19-g717bd7e-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-nVQdhO/2-liblxqt-l10n_0.11.0-19-g717bd7e-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/lxqt/translations/liblxqt/liblxqt_ar.qm', 
which is also in package liblxqt0:amd64 0.10.0-5
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-nVQdhO/2-liblxqt-l10n_0.11.0-19-g717bd7e-1_all.deb


cheers,

Andreas


qterminal=0.6.1~102-g58f4f72-1_qterminal-l10n=0.11.0-19-g717bd7e-1.log.gz
Description: application/gzip

Bug#840666: firebird3.0: FTBFS on powerpc, segfaults during build

[Damyan Ivanov]

-=| John Paul Adrian Glaubitz, 13.10.2016 18:35:31 +0200 |=-
> Source: firebird3.0
> Version: 3.0.1.32609.ds4-6
> Severity: serious

Shouldn't this be important instead? According to 
https://release.debian.org/stretch/arch_qualify.html powerpc is not 
a release candidate.

Of course, I am eager to find solution to the crash regardless, just 
arguing about it affecting the potential migration of firebird3.0 to 
testing.

> Tags: upstream
> Justification: fails to build from source
> User: debian-powe...@lists.debian.org
> Usertags: powerpc
> 
> firebird3.0 currently fails to build from source since the gpre
> command segfaults during build:
> 
> sh -x -c "lockfile -1 /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock 
> && /«PKGBUILDDIR»/gen/Release/firebird/bin/gpre_current -m -z -n 
> /«PKGBUILDDIR»/src/yvalve/blob.epp 
> /«PKGBUILDDIR»/temp/Release/yvalve/blob.cpp; res=\$?; rm -f 
> /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock; exit \$res"
> + lockfile -1 /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock
> + /«PKGBUILDDIR»/gen/Release/firebird/bin/gpre_current -m -z -n 
> /«PKGBUILDDIR»/src/yvalve/blob.epp /«PKGBUILDDIR»/temp/Release/yvalve/blob.cpp
> gpre version LI-V3.0.1.32609 Firebird 3.0
> Segmentation fault
> + res=139
> + rm -f /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock
> + exit 139

Hmm. I have seen this on amd64 when gcc switched to version 6. Getting 
it built required adding -std=gnu++98 -fno-lifetime-dse 
-fno-delete-null-pointer-checks -fno-strict-aliasing to the compiler 
flags. Probably unrelated.

> I have done some debugging and from the backtrace it's obvious that
> the crash occurs in glibc:
> 
> (sid_powerpc-dchroot)glaubitz@partch:~/firebird3.0-3.0.1.32609.ds4$ gdb 
> /home/glaubitz/firebird3.0-3.0.1.32609.ds4/gen/Release/firebird/bin/gpre_boot
> GNU gdb (Debian 7.11.1-2) 7.11.1
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "powerpc-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from 
> /home/glaubitz/firebird3.0-3.0.1.32609.ds4/gen/Release/firebird/bin/gpre_boot...done.
> (gdb) run
> Starting program: 
> /home/glaubitz/firebird3.0-3.0.1.32609.ds4/gen/Release/firebird/bin/gpre_boot
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library 
> "/lib/powerpc-linux-gnu/libthread_db.so.1".
> gpre:  no source file named.
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x0fa79960 in _IO_wsetb () from /lib/powerpc-linux-gnu/libc.so.6
> (gdb) bt
> #0  0x0fa79960 in _IO_wsetb () from /lib/powerpc-linux-gnu/libc.so.6
> #1  0x0fa88dac in ?? () from /lib/powerpc-linux-gnu/libc.so.6
> #2  0x0fa3cd58 in ?? () from /lib/powerpc-linux-gnu/libc.so.6
> #3  0x0fa3ce30 in exit () from /lib/powerpc-linux-gnu/libc.so.6
> #4  0x10027f28 in CPR_exit (stat=263831632) at ./src/gpre/gpre.cpp:978
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> (gdb)
> 
> This looks similar to the FTBFS of lua5.3 on powerpc [1] which is
> triggered by the use of a version script for the linker and, in
> fact, firebird3.0 is using such scripts. Now, this actually reminded
> me of another similar problem we had on sparc back then [2] which
> is the missing _IO_stdin_used symbol in the version script. lua5.2
> was affected by that problem as well and Aurelien Jarno fixed that
> by adding that symbol to the version script [3].

This is interesting. I was trying to debug a similar issue today on 
the mips64el porterbox. One of the command-line utilities of firebird 
produces garbage upon exit breaking a database verification at the end 
of the build process. (Build log: 
https://buildd.debian.org/status/fetch.php?pkg=firebird3.0=mips64el=3.0.1.32609.ds4-6=1476281685)
There is random garbage emitted by the firebird source preprocessor 
(gpre) which is visible earlier in the build log.
Alpha is also affected.

> I tried the fix from [3] in firebird3.0, but unfortunately it
> doesn't help. Currently, I'm out of ideas but it would be great
> to see this fixed as this also affects m68k for which I have
> added platform support to firebird upstream [4,5].

Where did you add that _IO_stdin_used entry? There are several *.vers 
files in the source. I'll try with all of them and also 
_IO_std{err,out}_used.

(15 minutes later) Oh, it helps! The invocations of gpre no longer 
dump sources. Let's see how far this goes.

-- Damyan

> > 

Bug#840680: dirmngr: Dirmngr not always responding

[Shengjing Zhu]

Package: dirmngr
Version: 2.1.15-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrade to 2.1.15-4, I find dirmngr is not always responding
which makes command like `gpg --refresh-keys` stuck.

I test dirmngr with the following steps:

First run `gpg-connect-agent --dirmngr /bye`
It should immediately return but it's stuck.

But I open another shell to run `gpg-connect-agent --dirmngr /bye`
again. The first gpg-connect-agent returns and the second still is
stuck.

And I run again `gpg-connect-agent` and the previous one returns.

So I guess only another process access to the dirmngr socket, the
previous connect will be got processed.

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

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

Versions of packages dirmngr depends on:
ii  adduser3.115
ii  libassuan0 2.4.3-1
ii  libc6  2.24-3
ii  libgcrypt201.7.3-1
ii  libgnutls303.5.4-2
ii  libgpg-error0  1.24-1
ii  libksba8   1.3.5-2
ii  libldap-2.4-2  2.4.42+dfsg-2+b3
ii  libnpth0   1.2-3
ii  lsb-base   9.20160629

Versions of packages dirmngr recommends:
ii  gnupg  2.1.15-4

Versions of packages dirmngr suggests:
pn  tor  

-- no debconf information


signature.asc
Description: PGP signature

Bug#840677: zeroc-icegridgui: fails to upgrade from 'testing' - trying to overwrite /usr/bin/icegridgui

[Andreas Beckmann]

Package: zeroc-icegridgui
Version: 3.6.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package zeroc-icegridgui.
  Preparing to unpack .../15-zeroc-icegridgui_3.6.3-1_all.deb ...
  Unpacking zeroc-icegridgui (3.6.3-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-7YiD10/15-zeroc-icegridgui_3.6.3-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/icegridgui', which is also in package 
zeroc-ice-utils-java 3.6.2-stretch-51-gba6baa6-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-7YiD10/15-zeroc-icegridgui_3.6.3-1_all.deb


cheers,

Andreas


zeroc-ice-utils-java=3.6.2-stretch-51-gba6baa6-2_zeroc-icegridgui=3.6.3-1.log.gz
Description: application/gzip

Bug#840666: firebird3.0: FTBFS on powerpc, segfaults during build

[John Paul Adrian Glaubitz]

On 10/13/2016 08:17 PM, John Paul Adrian Glaubitz wrote:
> Ok, the following patch fixes the crash above:
> 
> glaubitz@partch:~/firebird$ git diff builds/posix/vers.sh.in
> diff --git a/builds/posix/vers.sh.in b/builds/posix/vers.sh.in
> index 69bd656..15d86a7 100644
> --- a/builds/posix/vers.sh.in
> +++ b/builds/posix/vers.sh.in
> @@ -57,6 +57,7 @@ platform_linux() {
> echo "${TAB}$i;"
> done
> 
> +   echo "${TAB}_IO_stdin_used;"
> echo 'local:'
> echo "${TAB}*;"
> echo '};'
> glaubitz@partch:~/firebird$
> 
> However, it crashes still when running isql during build:

Ok, turns out the second crash affects Firebird from git/master only. The patch
above really fixes the problem for the firebird3.0 package in Debian :).

Will prepare a patch shortly and follow up. This *might* also fix the
testsuite failure on mips64el as it apparently also has problems when
_IO_stdin_used is missing.

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#840666: firebird3.0: FTBFS on powerpc, segfaults during build

[John Paul Adrian Glaubitz]

On 10/13/2016 06:35 PM, John Paul Adrian Glaubitz wrote:
> I tried the fix from [3] in firebird3.0, but unfortunately it
> doesn't help. Currently, I'm out of ideas but it would be great
> to see this fixed as this also affects m68k for which I have
> added platform support to firebird upstream [4,5].

Ok, the following patch fixes the crash above:

glaubitz@partch:~/firebird$ git diff builds/posix/vers.sh.in
diff --git a/builds/posix/vers.sh.in b/builds/posix/vers.sh.in
index 69bd656..15d86a7 100644
--- a/builds/posix/vers.sh.in
+++ b/builds/posix/vers.sh.in
@@ -57,6 +57,7 @@ platform_linux() {
echo "${TAB}$i;"
done

+   echo "${TAB}_IO_stdin_used;"
echo 'local:'
echo "${TAB}*;"
echo '};'
glaubitz@partch:~/firebird$

However, it crashes still when running isql during build:

make gpre
make[3]: Entering directory '/home/glaubitz/firebird/gen'
rm -f metadata.fdb
/home/glaubitz/firebird/gen/Release/firebird/bin/isql -q -i 
/home/glaubitz/firebird/src/dbs/metadata.sql
Makefile:339: recipe for target 'metadata.fdb' failed
make[3]: *** [metadata.fdb] Segmentation fault
make[3]: *** Deleting file 'metadata.fdb'
make[3]: Leaving directory '/home/glaubitz/firebird/gen'
Makefile:180: recipe for target 'master_process' failed
make[2]: *** [master_process] Error 2
make[2]: Leaving directory '/home/glaubitz/firebird/gen'
Makefile:74: recipe for target 'firebird' failed
make[1]: *** [firebird] Error 2
make[1]: Leaving directory '/home/glaubitz/firebird/gen'
Makefile:6: recipe for target 'firebird' failed
make: *** [firebird] Error 2

But calling the isql command line directly doesn't trigger a crash:

(sid_powerpc-dchroot)glaubitz@partch:~/firebird$ export 
LD_LIBRARY_PATH=/home/glaubitz/firebird/gen/Release/firebird/lib
(sid_powerpc-dchroot)glaubitz@partch:~/firebird$ 
/home/glaubitz/firebird/gen/Release/firebird/bin/isql -q -i 
/home/glaubitz/firebird/src/dbs/metadata.sql
can't format message 17:0 -- message file /usr/local/firebird/firebird.msg not 
found
Unable to complete network request to host "localhost".
-Failed to establish a connection.
can't format message 17:120 -- message file /usr/local/firebird/firebird.msg 
not found
(sid_powerpc-dchroot)glaubitz@partch:~/firebird$

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#840382: [Pkg-samba-maint] Bug#840382: samba (2:4.4.6+dfsg-2) still crashes with libtevent0-0.31

[Rene Hogendoorn]

On Wednesday, October 12, 2016 9:12:57 PM CEST Mathieu Parent wrote:
> (please keep the bug in CC).
> 
> Hi,
> 
> 2016-10-12 16:29 GMT+02:00 Rene Hogendoorn :
> [...]
> 
> > Thanks for the quick response.
> > Please, find a backtrace below.
> 
> Thanks
> 
> > Note, that there are several backtraces in the file because the daemon
> > kept
> > being restarted and, subsequently, failing.
> 
> yes systemd is restarting the service. Too fast IMO.
> 
> > I hope this will help you locating the issue.
> 
> This is strange, I'm not able to reproduce it anymore (since
> 4.4.6+dbsg-2). Are you sure that you upgraded all the samba packages?
> 
> Does nmbd crash too?
> 
> Regards

Mathieu,

I certainly agree with the restart issue (over a 1000 emails about the crash 
event).
I did the upgrade with apt update; apt upgrade and, yes, nmbd also crashes (see 
below).
Package versions:


Regards,

Rene

---

[2016/10/12 11:41:19.240894,  0] ../source3/nmbd/nmbd.c:58(terminate) 

Bug#840394: motif: FTBFS: relocation R_X86_64_PC32 against symbol `exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC

[Sebastiaan Couwenberg]

On Tue, 11 Oct 2016 09:57:18 +0200 Graham Inggs wrote:
> I believe this will be fixed by a binNMU of flex [1] after GCC 6 is
> uploaded with PIE enabled by default [2].
> This should be happening Real Soon Now.

Are you sure about that timing?

The failed motif builds are preventing the grass rebuilds for the
readline7 transition (#838234), waiting for the above may not be such a
good idea.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: jessie-ignore for "maintainer address bounces" bugs?

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 803003 jessie-ignore wheezy-ignore
Bug #803003 {Done: Dirk Eddelbuettel } [ess] ess: Maintainer 
field points to moderated mailing list
Added tag(s) jessie-ignore and wheezy-ignore.
> tag 813778 jessie-ignore wheezy-ignore
Bug #813778 [openwince-jtag] Maintainer address bounces
Added tag(s) jessie-ignore and wheezy-ignore.
> tag 813776 jessie-ignore wheezy-ignore
Bug #813776 [openwince-include] Maintainer address bounces
Added tag(s) jessie-ignore and wheezy-ignore.
> tag 813775 jessie-ignore wheezy-ignore
Bug #813775 {Done: Andreas Henriksson } [linux-atm] 
Maintainer address bounces
Added tag(s) wheezy-ignore and jessie-ignore.
> tag 833327 jessie-ignore wheezy-ignore
Bug #833327 [src:xmldiff] xmldiff: maintainer address bounces
Added tag(s) jessie-ignore and wheezy-ignore.
> tag 809843 jessie-ignore wheezy-ignore
Bug #809843 {Done: Adam Borowski } [src:autopsy] autopsy: 
maintainer address bounces
Added tag(s) wheezy-ignore and jessie-ignore.
> tag 832329 jessie-ignore
Bug #832329 {Done: Hugo Lefeuvre } [src:python-qrcode] 
python-qrcode: maintainer address bounces
Added tag(s) jessie-ignore.
> tag 838228 jessie-ignore wheezy-ignore
Bug #838228 [src:lakai] src:lakai: maintainer address bounces
Added tag(s) jessie-ignore and wheezy-ignore.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
803003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803003
809843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809843
813775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813775
813776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813776
813778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813778
832329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832329
833327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833327
838228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840355: marked as done (Failed to create spool file /var/spool/exim4//input//...-D: Permission denied)

[Debian Bug Tracking System]

Your message dated Thu, 13 Oct 2016 17:40:20 +
with message-id 
and subject line Bug#840355: fixed in exim4 4.88~RC2-2
has caused the Debian Bug report #840355,
regarding Failed to create spool file /var/spool/exim4//input//...-D: 
Permission denied
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exim4
Version: 4.88~RC2-1
Severity: grave

Can't send mail, because:
2016-10-11 04:30:53 Failed to create spool file 
/var/spool/exim4//input//1bthDp-0002gq-Fy-D: Permission denied

-- Package-specific info:
Exim version 4.88 #2 built 09-Oct-2016 15:37:08
Copyright (c) University of Cambridge, 1995 - 2016
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2016
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM DNSSEC Event 
OCSP PRDR SOCKS
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated
dc_eximconfig_configtype='smarthost'
dc_other_hostnames='jidanni2.jidanni.org;jidanni3.jidanni.org;jidanni4.jidanni.org;jidanni5.jidanni.org;jidanni6.jidanni.org'
dc_readhost='jidanni.org'
dc_relay_domains=''
dc_minimaldns='true'
dc_relay_nets=''
dc_smarthost='homie.mail.dreamhost.com::587'
dc_local_interfaces=''
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='false'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:jidanni.org

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

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

Versions of packages exim4 depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  exim4-base 4.88~RC2-1
ii  exim4-daemon-light 4.88~RC2-1

exim4 recommends no packages.

exim4 suggests no packages.

-- debconf information:
  exim4/drec:
--- End Message ---
--- Begin Message ---
Source: exim4
Source-Version: 4.88~RC2-2

We believe that the bug you reported is fixed in the latest version of
exim4, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated exim4 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Oct 2016 19:25:07 +0200
Source: exim4
Binary: exim4-base exim4-config exim4-daemon-light exim4 exim4-daemon-heavy 
eximon4 exim4-dbg exim4-daemon-light-dbg exim4-daemon-heavy-dbg exim4-dev
Architecture: source
Version: 4.88~RC2-2
Distribution: experimental
Urgency: medium
Maintainer: Exim4 Maintainers 
Changed-By: Andreas Metzler 
Closes: 840355
Description: 
 exim4-base - support files for all Exim MTA (v4) packages
 exim4-config - configuration for the Exim MTA (v4)
 exim4-daemon-heavy-dbg - debugging symbols for the Exim MTA "heavy" daemon
 exim4-daemon-heavy - Exim MTA (v4) daemon with extended features, including 
exiscan-ac
 exim4-daemon-light-dbg - debugging symbols for the Exim MTA "light" daemon
 exim4-daemon-light - lightweight Exim MTA (v4) daemon
 exim4-dbg  - debugging symbols for the Exim MTA (utilities)
 exim4-dev  - header files for the Exim MTA (v4) packages
 exim4  - metapackage to ease Exim MTA (v4) installation
 eximon4- monitor application for the Exim MTA (v4) (X11 interface)
Changes:
 exim4 (4.88~RC2-2) experimental; urgency=medium
 .
   * 75_01-Fix-check-for-commandline-macro-definition.patch - Fix permission
 problems on 

Bug#840575: [buildd-tools-devel] Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode

[Thomas Goirand]

On 10/13/2016 12:58 PM, Johannes Schauer wrote:
> Hi,
> 
> Quoting Thomas Goirand (2016-10-12 23:42:15)
>> Dear backport maintainer,
>>
>> Since the upload of sbuild 0.71.0-2~bpo8+1 to stable backport, running
>> sbuild-update --keygen leads to this error message:
>>
>> gpg: Invalid option "--pinentry-mode"
>>
>> Indeed, it looks like --pinentry-mode isn't available in gnupg 1.4.18-7 which
>> is in Jessie. Since there's no backport of gnupg 2.1.x, this makes sbuild 
>> from
>> jessie-bpo completely broken, considering one need to run sbuild-update 
>> --keygen
>> to start using sbuild.
> 
> You do not need to run sbuild-update --keygen to start using sbuild with the
> sbuild versions after 0.69.0.
> 
> So until this bug is fixed, just don't run that command.

Thanks for the hint. I've edited https://wiki.debian.org/sbuild to add
this information.

Cheers,

Thomas Goirand (zigo)

Processed: found 840107 in 1.2.0-1, tagging 840177, found 840417 in 1:20161005~dfsg-1, tagging 840329 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 840107 1.2.0-1
Bug #840107 [src:beignet] beignet: FTBFS with libdrm-intel 2.4.71
Marked as found in versions beignet/1.2.0-1.
> tags 840177 + sid stretch
Bug #840177 [src:qconf] qconf: FTBFS: mkdir: cannot create directory 
'/usr/share/qconf/': Permission denied
Added tag(s) sid and stretch.
> found 840417 1:20161005~dfsg-1
Bug #840417 [libfontforge-dev] pdf2htmlex: FTBFS with new release of fontforge
Marked as found in versions fontforge/1:20161005~dfsg-1.
> tags 840329 + sid stretch
Bug #840329 [src:taglib-extras] taglib-extras: FTBFS: CMake Error at 
cmake/modules/FindTaglib.cmake:132 (message):   Could not find Taglib
Added tag(s) sid and stretch.
> found 840393 0.0.080507-4
Bug #840393 [src:mensis] mensis: FTBFS with newly released fontforge
Marked as found in versions mensis/0.0.080507-4.
> tags 840393 + sid stretch
Bug #840393 [src:mensis] mensis: FTBFS with newly released fontforge
Added tag(s) sid and stretch.
> tags 840428 + sid stretch
Bug #840428 [src:pythonmagick] pyhonmagick: FTBS with newer experimental 
version of imagemagick
Added tag(s) sid and stretch.
> tags 840346 + sid stretch
Bug #840346 [src:qjoypad] qjoypad: FTBFS: install: cannot create regular file 
'/usr/bin/qjoypad': Permission denied
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840107
840177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840177
840329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840329
840346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840346
840393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840393
840417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840417
840428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840666: firebird3.0: FTBFS on powerpc, segfaults during build

[John Paul Adrian Glaubitz]

Source: firebird3.0
Version: 3.0.1.32609.ds4-6
Severity: serious
Tags: upstream
Justification: fails to build from source
User: debian-powe...@lists.debian.org
Usertags: powerpc

Hello!

firebird3.0 currently fails to build from source since the gpre
command segfaults during build:

sh -x -c "lockfile -1 /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock && 
/«PKGBUILDDIR»/gen/Release/firebird/bin/gpre_current -m -z -n 
/«PKGBUILDDIR»/src/yvalve/blob.epp /«PKGBUILDDIR»/temp/Release/yvalve/blob.cpp; 
res=\$?; rm -f /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock; exit 
\$res"
+ lockfile -1 /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock
+ /«PKGBUILDDIR»/gen/Release/firebird/bin/gpre_current -m -z -n 
/«PKGBUILDDIR»/src/yvalve/blob.epp /«PKGBUILDDIR»/temp/Release/yvalve/blob.cpp
gpre version LI-V3.0.1.32609 Firebird 3.0
Segmentation fault
+ res=139
+ rm -f /«PKGBUILDDIR»/gen/Release/firebird/bin/build-db.lock
+ exit 139

I have done some debugging and from the backtrace it's obvious that
the crash occurs in glibc:

(sid_powerpc-dchroot)glaubitz@partch:~/firebird3.0-3.0.1.32609.ds4$ gdb 
/home/glaubitz/firebird3.0-3.0.1.32609.ds4/gen/Release/firebird/bin/gpre_boot
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/home/glaubitz/firebird3.0-3.0.1.32609.ds4/gen/Release/firebird/bin/gpre_boot...done.
(gdb) run
Starting program: 
/home/glaubitz/firebird3.0-3.0.1.32609.ds4/gen/Release/firebird/bin/gpre_boot
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
gpre:  no source file named.

Program received signal SIGSEGV, Segmentation fault.
0x0fa79960 in _IO_wsetb () from /lib/powerpc-linux-gnu/libc.so.6
(gdb) bt
#0  0x0fa79960 in _IO_wsetb () from /lib/powerpc-linux-gnu/libc.so.6
#1  0x0fa88dac in ?? () from /lib/powerpc-linux-gnu/libc.so.6
#2  0x0fa3cd58 in ?? () from /lib/powerpc-linux-gnu/libc.so.6
#3  0x0fa3ce30 in exit () from /lib/powerpc-linux-gnu/libc.so.6
#4  0x10027f28 in CPR_exit (stat=263831632) at ./src/gpre/gpre.cpp:978
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)

This looks similar to the FTBFS of lua5.3 on powerpc [1] which is
triggered by the use of a version script for the linker and, in
fact, firebird3.0 is using such scripts. Now, this actually reminded
me of another similar problem we had on sparc back then [2] which
is the missing _IO_stdin_used symbol in the version script. lua5.2
was affected by that problem as well and Aurelien Jarno fixed that
by adding that symbol to the version script [3].

I tried the fix from [3] in firebird3.0, but unfortunately it
doesn't help. Currently, I'm out of ideas but it would be great
to see this fixed as this also affects m68k for which I have
added platform support to firebird upstream [4,5].

Thanks,

Adrian

> [1] https://bugs.launchpad.net/ubuntu/+source/lua5.3/+bug/1570055
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634261
> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816059
> [4] https://github.com/FirebirdSQL/firebird/pull/51
> [5] https://github.com/FirebirdSQL/firebird/pull/52

--
 .''`.  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#725768: tkcvs: tk depends

[Teppo Mäenpää]

Hi,

I am also fan of tkdiff. I downloaded the source package, manually edited 
tk-x.y dependency to plain tk , build without any traces of problems and have 
then used extensively for months since then without problems.

Almost trivial change.

Does the maintainer wish to fix this before Stretch freeze? If not, what other 
options are there?

Regards,


Teppo Mäenpää

Bug#840664: ruby-faker: FTBFS randomly (failing tests)

[Santiago Vila]

Package: src:ruby-faker
Version: 1.5.0-1
Severity: serious

Dear maintainer:

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

The package builds ok, but then the tests fail randomly, because they
are not designed to never fail (as they should).

At least the following tests seem to be wrongly designed:

  => 14: assert Faker::Internet.email.match(/.+@[^.].+\.\w+/)
  => 70: assert period_range.include?(result.hour.to_i), 
"\"#{result.hour}\" expected to be included in 
Faker::Time::TIME_RANGES[:#{period}] range"

so I suggest that they are just disabled.

I'm attaching 9 different build logs. Sorry, I can't provide a way to
"reproduce" this because the failures are random, but if you look at
the build logs and look at the code, maybe you could tell why they
fail without having to build this package yourself a lot of times.

Thanks.

ruby-faker_1.5.0-1_amd64-20161012T212217Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161012T213114Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161012T213145Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161012T213155Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161013T153231Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161013T153254Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161013T153256Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161013T153315Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161013T153320Z.gz
Description: application/gzip

Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode

[Daniel Kahn Gillmor]

Control: reopen 840575
Control: found 840575 0.71.0-2
Control: retitle 840575 sbuild should Depends: gnupg (>= 2.1)
Control: affects 840575 src:gnupg2

On Wed 2016-10-12 18:07:39 -0400, James Clarke wrote:
> Bugs in backported packages should not be sent to the BTS, but to
> debian-backports (CC'ed for your convenience).

While i agree with James here…

> On Wed, Oct 12, 2016 at 11:42:15PM +0200, Thomas Goirand wrote:
>> Package: sbuild
>> Version: 0.71.0-2~bpo8+1
>> Severity: grave
>> Tags: patch
>>
>> Dear backport maintainer,
>>
>> Since the upload of sbuild 0.71.0-2~bpo8+1 to stable backport, running
>> sbuild-update --keygen leads to this error message:
>>
>> gpg: Invalid option "--pinentry-mode"

… it sounds like sbuild should at least have declared a versioned
dependency on gnupg (>= 2.1), when --pinentry-mode was introduced.

>> Indeed, it looks like --pinentry-mode isn't available in gnupg 1.4.18-7 which
>> is in Jessie. Since there's no backport of gnupg 2.1.x, this makes sbuild 
>> from
>> jessie-bpo completely broken, considering one need to run sbuild-update 
>> --keygen
>> to start using sbuild.

Alternately, maybe the requirement to run --keygen could be relaxed?

Regards,

 --dkg


signature.asc
Description: PGP signature

Processed: Re: Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode

[Debian Bug Tracking System]

Processing control commands:

> reopen 840575
Bug #840575 {Done: James Clarke } [sbuild] sbuild bpo: uses 
non-available option gnupg --pinentry-mode
Bug reopened
Ignoring request to alter fixed versions of bug #840575 to the same values 
previously set
> found 840575 0.71.0-2
Bug #840575 [sbuild] sbuild bpo: uses non-available option gnupg --pinentry-mode
Marked as found in versions sbuild/0.71.0-2.
> retitle 840575 sbuild should Depends: gnupg (>= 2.1)
Bug #840575 [sbuild] sbuild bpo: uses non-available option gnupg --pinentry-mode
Changed Bug title to 'sbuild should Depends: gnupg (>= 2.1)' from 'sbuild bpo: 
uses non-available option gnupg --pinentry-mode'.
> affects 840575 src:gnupg2
Bug #840575 [sbuild] sbuild should Depends: gnupg (>= 2.1)
Added indication that 840575 affects src:gnupg2

-- 
840575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#839580: [request-tracker-maintainers] Bug#839580: request-tracker4: FTBFS in testing (failed tests)

[Dominic Hargreaves]

On Tue, Oct 11, 2016 at 11:48:15PM -0400, Daniel Kahn Gillmor wrote:
> Does any of you RT hackers know how to run specific tests manually
> without needing to re-run the entire ~10 minute suite so i can reduce
> the cycle time as i'm debugging this stuff and trying to propose fixes?

./configure --with-my-user-group  --enable-layout=inplace --with-db-type=SQLite 
--enable-developer
[...]
prove -l t/TESTNAME.t

should be enough to get you running on most tests, I think.

Cheers,
Dominic.

Bug#840639: axiom: FTBFS on arm64, mips64el and mipsel

[Emilio Pozuelo Monfort]

Source: axiom
Version: 20140801-11
Severity: serious

Hi,

Your package failed to build on arm64, mipsel and mips64el.

Full logs at https://buildd.debian.org/status/package.php?p=axiom

Emilio

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

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

Processed: severity of 840325 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 840325 important
Bug #840325 [keepass2] keepass2: Conflict with light-locker, which renders 
program unusable
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#835360: rkt: FTBFS on several architectures

[Luca BRUNO]

On Thursday, 13 October 2016 13:59:27 UTC Andreas Henriksson wrote:
 
> Fwiw, there's a chain of {build-,}dependencies that would need to be
> removed on ppc64el

Ah, when I wrote my previous answer I didn't realize that.
Upon further inspection, it looks like it may be just enough to cherry-pick
this fix on top of gopsutil:
https://github.com/shirou/gopsutil/pull/261
 
Ciao, Luca

-- 
«Доверяй, но проверяй»


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

Processed: fixed 839493 in mono/4.6.1.3+dfsg-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 839493 mono/4.6.1.3+dfsg-1
Bug #839493 {Done: Jo Shields } [src:mono] keepass2: 
FTBFS: System.IO.FileNotFoundException: Could not find file "/etc/localtime"
Marked as fixed in versions mono/4.6.1.3+dfsg-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
839493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 839493 to src:mono

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 839493 src:mono
Bug #839493 {Done: Jo Shields } [src:keepass2] 
keepass2: FTBFS: System.IO.FileNotFoundException: Could not find file 
"/etc/localtime"
Bug reassigned from package 'src:keepass2' to 'src:mono'.
No longer marked as found in versions keepass2/2.34+dfsg-1.
No longer marked as fixed in versions mono/4.6.1.3+dfsg-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
839493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#834685: marked as done (python-reno: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Thu, 13 Oct 2016 13:19:28 +
with message-id 
and subject line Bug#834685: fixed in python-reno 1.3.0-6
has caused the Debian Bug report #834685,
regarding python-reno: FTBFS in testing (failing tests)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
834685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-reno
Version: 1.3.0-3
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils 
--with python2,python3,sphinxdoc
dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: 
binary binary-arch binary-indep build build-arch build-indep clean install 
install-arch install-indep)
dh build-indep --buildsystem=python_distutils --with python2,python3,sphinxdoc
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

  File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory


==
FAIL: reno.tests.test_scanner.UniqueIdTest.test_modern
reno.tests.test_scanner.UniqueIdTest.test_modern
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "reno/tests/test_scanner.py", line 178, in setUp
self.useFixture(GPGKeyFixture())
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 679, in 
useFixture
reraise(*exc_info)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 666, in 
useFixture
fixture.setUp()
  File "reno/tests/test_scanner.py", line 67, in setUp
cwd=tempdir.path)
  File "reno/utils.py", line 44, in check_output
raw = subprocess.check_output(*args, **kwds)
  File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory


--
Ran 27 tests in 0.372s

FAILED (failures=22)
debian/rules:29: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.
--- End Message ---
--- Begin Message ---
Source: python-reno
Source-Version: 1.3.0-6

We believe that the bug you reported is fixed in the latest version of
python-reno, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If 

Bug#840318: marked as done (susv4: download url has changed)

[Debian Bug Tracking System]

Your message dated Thu, 13 Oct 2016 12:49:59 +
with message-id 
and subject line Bug#840318: fixed in sus 7.20161013
has caused the Debian Bug report #840318,
regarding susv4: download url has changed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: susv4
Version: 7.20160312~deb8u1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package susv4.
  (Reading database ... 
(Reading database ... 7653 files and directories currently installed.)
  Preparing to unpack .../susv4_7.20160312~deb8u1_all.deb ...
  Unpacking susv4 (7.20160312~deb8u1) ...
  Setting up susv4 (7.20160312~deb8u1) ...
  Fetching file...
  converted 
'http://pubs.opengroup.org/onlinepubs/9699919799/download/susv4tc1.tar.bz2' 
(ANSI_X3.4-1968) -> 
'http://pubs.opengroup.org/onlinepubs/9699919799/download/susv4tc1.tar.bz2' 
(UTF-8)
  --2016-10-09 10:34:47--  
http://pubs.opengroup.org/onlinepubs/9699919799/download/susv4tc1.tar.bz2
  Resolving localhost (localhost)... 127.0.0.1
  Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
  Proxy request sent, awaiting response... 404 Not Found
  2016-10-09 10:34:48 ERROR 404: Not Found.
  
  dpkg: error processing package susv4 (--configure):
   subprocess installed post-installation script returned error exit status 8
  Errors were encountered while processing:
   susv4


cheers,

Andreas


susv4_7.20160312~deb8u1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sus
Source-Version: 7.20161013

We believe that the bug you reported is fixed in the latest version of
sus, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Weinehall  (supplier of updated sus package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 13 Oct 2016 14:15:32 +0300
Source: sus
Binary: susv2 susv3 susv4
Architecture: source all
Version: 7.20161013
Distribution: unstable
Urgency: medium
Maintainer: David Weinehall 
Changed-By: David Weinehall 
Description:
 susv2  - Fetch and install SUSv2
 susv3  - Fetch and install SUSv3
 susv4  - Fetch and install SUSv4 (POSIX.1-2008)
Closes: 840318
Changes:
 sus (7.20161013) unstable; urgency=medium
 .
   * New upstream release: contains SUSv4 TC2; update checksum
 (Closes: #840318)
   * urgency=medium since susv4 is no longer installable
   * debian/compat: Use debheloper v10
   * debian/control:
 - Bump Standards-Version to 3.9.8 (No changes needed)
Checksums-Sha1:
 947a63d7d5eec67125eecf9a7759be091c342efd 1451 sus_7.20161013.dsc
 81f313b55d78d76fcc91e86b962a413b400bab9c 3076 sus_7.20161013.tar.xz
 89fe388d7878540741ed7785114a158ed8beea1c 3174 susv2_7.20161013_all.deb
 9662413d32da565145d381ae6409ec29eb65a9d5 3278 susv3_7.20161013_all.deb
 67331d09c2401015c73d49dfc99b876393ef88af 3278 susv4_7.20161013_all.deb
Checksums-Sha256:
 f29738a98c71f21c3f16855cb1cfc0af49ce984775bec1e540b945e897e6ff82 1451 
sus_7.20161013.dsc
 853398c1fde2ef395ec3612a5b663dbb38973bc35ec16f37bca4d79382a96cf8 3076 
sus_7.20161013.tar.xz
 b81ad376cb8d9572114e1e5b7785d82a9acf649949d127ec315d4dcf6f955d27 3174 
susv2_7.20161013_all.deb
 ed9de8feb34960552f6e8d68af396ae03a4e8fc664c19af131b72a8894080382 3278 
susv3_7.20161013_all.deb
 78866f83e95ceb036b08c7b66549035808704f4cf23e90e52e3f921e2b7ecdbf 3278 
susv4_7.20161013_all.deb
Files:
 514745cf82eee53b0fdaf346c41ad982 1451 contrib/doc extra sus_7.20161013.dsc
 5314845a1bd9932cd5e9764cbf70dd49 3076 contrib/doc extra sus_7.20161013.tar.xz
 a963de14c787bd800e92c4bf0a5a0d0c 3174 contrib/doc extra 
susv2_7.20161013_all.deb
 

Processed: severity of 840477 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 840477 serious
Bug #840477 [cryptsetup] cryptsetup: initramfs hook cryptroot fails if root is 
lvm and spans multiple devices/nodes
Bug #840480 [cryptsetup] cryptsetup initramfs hook warning with multiple 
encrypted physical volumes
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840477
840480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#835360: rkt: FTBFS on several architectures

[Andreas Henriksson]

Hello all.

On Thu, Oct 13, 2016 at 10:42:37AM +, Luca BRUNO wrote:
> On Thursday, 13 October 2016 21:18:07 UTC Dmitry Smirnov wrote:
> > Rkt 1.16.0 FTBFS on ppc64el and s390x:
> > 
> > https://buildd.debian.org/status/package.php?p=rkt
> > 
> > Any ideas what we can do about it?
> 
> s390(x) is not supported upstream for the moment, but this shouldn't be a 
> blocker as it has never been built there before anyway.
> 
> Regarding ppc64el, it looks like you hit again
> https://github.com/shirou/gopsutil/issues/230
> Given that upstream is not planning to fix it anytime soon, I'd recommend to
> ask for a removal for rkt (1.9.1+dfsg-1) on ppc64el for now, so that it can 
> transition to stretch without being blocked by that arch until some porters
> get to it.

Fwiw, there's a chain of {build-,}dependencies that would need to be
removed on ppc64el which if I'm not mistaken looks like this:

golang-github-coreos-rkt-dev (from src:rkt)
<-(dep)-
golang-github-google-cadvisor-dev (from src:cadvisor)
<-(build-dep)-
gitlab-ci-multi-runner

(src:cadvisor has no other {build-}dependencies)

So as far as I can tell a asking for removal of ppc64 binaries for
cadvisor, gitlab-ci-multi-runner and rkt should be doable.
(AFAIK those processing removal requests prefer/require separate RM bug
reports per source package, so 3 RM bug reports.)

Regards,
Andreas Henriksson

Bug#840573: unicon: DFSG-incompatible license

[Santiago Vila]

On Thu, Oct 13, 2016 at 08:42:39AM -0300, Eriberto Mota wrote:

> I suggest to see if unicon builds without the file. I did a primitive
> test and yes, builds. However is needed a better test.

Yes, I was going to suggest exactly that.

Apparently, this package just needs a repack excluding the non-free files.

Thanks.

Bug#840573: unicon: DFSG-incompatible license

[Eriberto Mota]

Hi,

2016-10-13 6:58 GMT-03:00 Santiago Vila :
> On Wed, 12 Oct 2016, Joao Eriberto Mota Filho wrote:
>
>> Source: unicon
>> Severity: serious
>> Tags: upstream
>> Justification: Policy 2.2.1
>>
[...]
>>
>> There is a restriction for commercial use.
>
> Probably not the intent (as this is an old license), but certainly
> it's the letter.
>
> BTW: There is a similar wording in the Perl license: "You may not
> charge a fee for this Package itself."
>
> This is an orphaned package (maintained by "Debian QA"). In case you
> use this package yourself, would you like to forward this bug upstream
> (just to see if author would be willing to change the license), or
> should we just move this to non-free?
>
> I'm Cc:ing Balint, who made the last QA upload (maybe he uses the
> package himself, I don't).


I don't use this package. The file in focus was taken by upstream from
other source code.

The source unicon provides unicon-imc2. It is a dependency for zhcon.
It is a recomend for task-chinese-s, task-korean and task-chinese-t.
These are recommeds for live-task-localisation.

The popcon for unicon-imc2 and for zhcon are 1481 and 1484.

I suggest to see if unicon builds without the file. I did a primitive
test and yes, builds. However is needed a better test.

Regards,

Eriberto


Useful UDDs:

Help a package: https://people.debian.org/~eriberto/help_a_package.html
Uploaders ranking:https://people.debian.org/~eriberto/uploaders_ranking.html
Top 500 NEW packages: https://people.debian.org/~eriberto/top_500_new.html

Bug#840573: unicon: DFSG-incompatible license

[Bálint Réczey]

Hi,

2016-10-13 11:58 GMT+02:00 Santiago Vila :
> On Wed, 12 Oct 2016, Joao Eriberto Mota Filho wrote:
>
>> Source: unicon
>> Severity: serious
>> Tags: upstream
>> Justification: Policy 2.2.1
>>
>> Dear Maintainer,
>>
>> The file unicon/ImmModules/cxterm/utils/HZtable.h has the following license:
>>
>> Copyright 1994,1995 by Yongguang Zhang.  All Rights Reserved
>>
>> Permission to retain, use, modify, copy, and distribute CXTERM 5.0
>> in source or binary and its documentation (hereafter, the Software)
>> for non-commercial purpose is hereby granted to you without a fee,
>> provided that this entire copyright and permission notice appear in
>> all such copies, that no charge be associated with such copies,
>> that distribution of derivative works (including value-added
>> distributions such as with additional input dictionaries or fonts)
>> include clarification that such added or derived parts are not from
>> the original Software, and that the names of the author(s) not be
>> used to endorse or promote such works.
>>
>> THE AUTHOR(S) DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
>> ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL
>> THE AUTHOR(S) BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR
>> ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
>> WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
>> ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
>>
>> There is a restriction for commercial use.
>
> Probably not the intent (as this is an old license), but certainly
> it's the letter.
>
> BTW: There is a similar wording in the Perl license: "You may not
> charge a fee for this Package itself."
>
> This is an orphaned package (maintained by "Debian QA"). In case you
> use this package yourself, would you like to forward this bug upstream
> (just to see if author would be willing to change the license), or
> should we just move this to non-free?
>
> I'm Cc:ing Balint, who made the last QA upload (maybe he uses the
> package himself, I don't).

I don't use the package either.

I don't think moving it to non-free is a reasonable solution because this
license is incompatible with GPL thus unicon as a whole can't be licensed
under GPL thus it looks like it does not have a valid license.

One could argue that .h files can't be licensed, but HZutil.c also share the
same license.

One option would be asking the cxterm upstream to relicense the files under
GPL if it fails and the unicon package is not usable without those files then
it should probably be removed from the archive. :-(

Cheers,
Balint

Bug#839486: marked as done (lhasa: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Thu, 13 Oct 2016 11:05:38 +
with message-id 
and subject line Bug#839486: fixed in lhasa 0.3.1-2
has caused the Debian Bug report #839486,
regarding lhasa: FTBFS: Tests failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
839486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lhasa
Version: 0.3.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> Please report to frag...@gmail.com
> 
> Makefile:783: recipe for target 'test-suite.log' failed
> make[5]: *** [test-suite.log] Error 1
> make[5]: Leaving directory '/<>/test'
> Makefile:889: recipe for target 'check-TESTS' failed
> make[4]: *** [check-TESTS] Error 2
> make[4]: Leaving directory '/<>/test'
> Makefile:1025: recipe for target 'check-am' failed
> make[3]: *** [check-am] Error 2
> make[3]: Leaving directory '/<>/test'
> Makefile:468: recipe for target 'check-recursive' failed
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory '/<>'
> dh_auto_test: make -j1 check VERBOSE=1 VERBOSE=true returned exit code 2
> debian/rules:9: recipe for target 'override_dh_auto_test' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/01/lhasa_0.3.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: lhasa
Source-Version: 0.3.1-2

We believe that the bug you reported is fixed in the latest version of
lhasa, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 839...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Dowland  (supplier of updated lhasa package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Oct 2016 23:07:29 +0100
Source: lhasa
Binary: lhasa liblhasa-dev liblhasa0
Architecture: source
Version: 0.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Dowland 
Changed-By: Jonathan Dowland 
Description:
 lhasa  - lzh archive decompressor
 liblhasa-dev - lzh decompression library - development files
 liblhasa0  - lzh archive decompression library
Closes: 823671 839486
Changes:
 lhasa (0.3.1-2) unstable; urgency=medium
 .
   * Add tzdata to build-depends. Thanks James Cowgill. Closes: #839486.
   * ship the .pc file in our dev package. Closes: #823671.
   * Bump standards version (no changes required)
Checksums-Sha1:
 c5dc19b61375db3f6dc4b5c53ff7cc3f57281424 1992 lhasa_0.3.1-2.dsc
 7ac9819bc1baaca7624f4a7fb9a9d13f3ccbaa86 3632 lhasa_0.3.1-2.debian.tar.xz
Checksums-Sha256:
 74205db5d379d1b7e1d1dd92a58c483d6d8a606ff52f160376dfc2809462699e 1992 
lhasa_0.3.1-2.dsc
 5d61f5b518e29f4a2c876aa1d082d937863da7e8929a04c3d764d2921b2dbc9a 3632 
lhasa_0.3.1-2.debian.tar.xz
Files:
 70366e33c1e64342e75c19d940e10d83 1992 utils optional lhasa_0.3.1-2.dsc
 072d0f943b50723f1ff522d94baca3ca 3632 utils optional 
lhasa_0.3.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Processed: Serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #840428 [src:pythonmagick] pyhonmagick: FTBS with newer experimental 
version of imagemagick
Severity set to 'serious' from 'important'

-- 
840428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#839486: lhasa: FTBFS: Tests failures

[Jonathan Dowland]

On Tue, Oct 11, 2016 at 12:46:46PM +0100, James Cowgill wrote:
> Control: tags -1 patch

Thanks for looking at this!

-- 
Jonathan Dowland


signature.asc
Description: Digital signature

Bug#840575: [buildd-tools-devel] Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode

[Johannes Schauer]

Hi,

Quoting Thomas Goirand (2016-10-12 23:42:15)
> Dear backport maintainer,
> 
> Since the upload of sbuild 0.71.0-2~bpo8+1 to stable backport, running
> sbuild-update --keygen leads to this error message:
> 
> gpg: Invalid option "--pinentry-mode"
> 
> Indeed, it looks like --pinentry-mode isn't available in gnupg 1.4.18-7 which
> is in Jessie. Since there's no backport of gnupg 2.1.x, this makes sbuild from
> jessie-bpo completely broken, considering one need to run sbuild-update 
> --keygen
> to start using sbuild.

You do not need to run sbuild-update --keygen to start using sbuild with the
sbuild versions after 0.69.0.

So until this bug is fixed, just don't run that command.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#840605: marked as done (bubblewrap: CVE-2016-8659)

[Debian Bug Tracking System]

Your message dated Thu, 13 Oct 2016 10:54:32 +
with message-id 
and subject line Bug#840605: fixed in bubblewrap 0.1.2-2
has caused the Debian Bug report #840605,
regarding bubblewrap: CVE-2016-8659
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bubblewrap
Version: 0.1.2-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerability was published for bubblewrap.

CVE-2016-8659[0].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8659
[1] http://www.openwall.com/lists/oss-security/2016/10/12/5

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bubblewrap
Source-Version: 0.1.2-2

We believe that the bug you reported is fixed in the latest version of
bubblewrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated bubblewrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 13 Oct 2016 11:12:38 +0100
Source: bubblewrap
Binary: bubblewrap
Architecture: source
Version: 0.1.2-2
Distribution: unstable
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Simon McVittie 
Description:
 bubblewrap - setuid wrapper for unprivileged chroot and namespace manipulation
Closes: 840605
Changes:
 bubblewrap (0.1.2-2) unstable; urgency=high
 .
   * Revert addition of --set-hostname as a short-term fix for
 CVE-2016-8659 (Closes: #840605)
Checksums-Sha1:
 da87c8e0ba6e6984d4a8b4a94e9a909e8a6c590e 2071 bubblewrap_0.1.2-2.dsc
 dfb31e8c478dc330a6a3d00a5899c46b1e606450 5676 bubblewrap_0.1.2-2.debian.tar.xz
Checksums-Sha256:
 162b2e238f3f74797e94ee3dc6170e74799a1500991d4e96d1e33c3dd20640de 2071 
bubblewrap_0.1.2-2.dsc
 33de5ad850c2efeb5409636d8c23089d8a00dd4dfe564457e8de59ff9a1d 5676 
bubblewrap_0.1.2-2.debian.tar.xz
Files:
 ab81b20f39f29fb4b9a74304d36ceb85 2071 admin optional bubblewrap_0.1.2-2.dsc
 39c13d7833f8eb79e44bf756044f15d3 5676 admin optional 
bubblewrap_0.1.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX/2B5AAoJEE3o/ypjx8yQJvMQAJtQyb0sWadxoQmPjoJ9MP7v
tkyZhqVWH5qPqZJYE23T2+1RyOSYrvt05UB5Lhvo7s2dE8PttxeUedO6YhAfBxjm
DbGPM39z+BzK+4hm5TJo2sDKQ5+by3678TAt3FKlQnrvjlc6WdYoGFiP3cLqGS5O
+lbiPJZOSsPNoOlVoGRmziLn5HRkn2rg9Mq2708mJxyxpDtkkq35ANFlaV4FrKKb
kQNbdpMQgSwijpQy7gQFj5O4d12bwz+V8+gHSlbjD7ua13nmGPgyuI0QA2wSbXQs
XCvolp/oXK4X9u7UTXcAHPq02TfdIGugCVDOQgkyOdbJT7oMMP2T2APON2ZzznaU
HCpUI+i/J4ZJYWdjbLIGPe0Wi5HkANokgrBpaW0qBkV3pzp+4qltRQiJgphrZqRT
YVD+AuVLF2Kq7gIqQ8h2Ges19YpCeGlgieBNSxt4Y0fTfHWf/1K9C+bfEAD2viH4
Wej0O79IXwBH/dBqUWP0qnCPp1t0eJnPj97NuqcM2KovipvWUaSH/DWNWECUIobT
dttd5uoCXrivae7hfC9cp+PcmsyaRprJ1J0TkvlS93Pm2k0e5iPku2YPD/qjQkAr
DNZQAtBL1Gs6Ya6IPyg5M/PZTz8bT0Y/Kz1eiASkREq3fhW2m+JwAwbBplnIiwc9
fLo8s8Gp1wudKENxI6sT
=ym9q
-END PGP SIGNATURE End Message ---

Bug#835360: rkt: FTBFS on several architectures

[Luca BRUNO]

On Thursday, 13 October 2016 21:18:07 UTC Dmitry Smirnov wrote:
> Rkt 1.16.0 FTBFS on ppc64el and s390x:
> 
> https://buildd.debian.org/status/package.php?p=rkt
> 
> Any ideas what we can do about it?

s390(x) is not supported upstream for the moment, but this shouldn't be a 
blocker as it has never been built there before anyway.

Regarding ppc64el, it looks like you hit again
https://github.com/shirou/gopsutil/issues/230
Given that upstream is not planning to fix it anytime soon, I'd recommend to
ask for a removal for rkt (1.9.1+dfsg-1) on ppc64el for now, so that it can 
transition to stretch without being blocked by that arch until some porters
get to it.

Cheers, Luca

-- 
«Доверяй, но проверяй»


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

Bug#840581: vim-conque: ConqueTerm doesn't appear to load into vim

[Jakub Wilk]

Hi David!

* David Cantrell , 2016-10-12, 22:59:

Having installed the vim-conque package, I start vim:

 $ vim

and then try to start bash within it:

 :ConqueTerm bash

and just get this error:

 E492: Not an editor command: ConqueTerm bash

It looks like a bunch of files got installed in /usr/share/vim-conque, but 
they don't seem to get loaded when vim starts.


As per Debian Packaging Policy for Vim, vim addons are not enabled by default. 
You have to enable it yourself with vim-addon-manager (or by manually creating 
appropriate symlinks). This is documented in README.Debian.


--
Jakub Wilk

Bug#835360: rkt: FTBFS on several architectures

[Dmitry Smirnov]

Rkt 1.16.0 FTBFS on ppc64el and s390x:

https://buildd.debian.org/status/package.php?p=rkt

Any ideas what we can do about it?

-- 
Cheers,
 Dmitry Smirnov.

---

Free speech is the bedrock of liberty and a free society. And yes, it
includes the right to blaspheme and offend.
-- Ayaan Hirsi Ali, 2010


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

Processed: bug 840605 is forwarded to https://github.com/projectatomic/bubblewrap/issues/107

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 840605 https://github.com/projectatomic/bubblewrap/issues/107
Bug #840605 [src:bubblewrap] bubblewrap: CVE-2016-8659
Set Bug forwarded-to-address to 
'https://github.com/projectatomic/bubblewrap/issues/107'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 839486

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 839486 + pending
Bug #839486 [src:lhasa] lhasa: FTBFS: Tests failures
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
839486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840573: unicon: DFSG-incompatible license

[Santiago Vila]

On Wed, 12 Oct 2016, Joao Eriberto Mota Filho wrote:

> Source: unicon
> Severity: serious
> Tags: upstream
> Justification: Policy 2.2.1
> 
> Dear Maintainer,
> 
> The file unicon/ImmModules/cxterm/utils/HZtable.h has the following license:
> 
> Copyright 1994,1995 by Yongguang Zhang.  All Rights Reserved
> 
> Permission to retain, use, modify, copy, and distribute CXTERM 5.0
> in source or binary and its documentation (hereafter, the Software)
> for non-commercial purpose is hereby granted to you without a fee,
> provided that this entire copyright and permission notice appear in
> all such copies, that no charge be associated with such copies,
> that distribution of derivative works (including value-added
> distributions such as with additional input dictionaries or fonts)
> include clarification that such added or derived parts are not from
> the original Software, and that the names of the author(s) not be
> used to endorse or promote such works.
> 
> THE AUTHOR(S) DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
> ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL
> THE AUTHOR(S) BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR
> ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
> WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
> ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
> 
> There is a restriction for commercial use.

Probably not the intent (as this is an old license), but certainly
it's the letter.

BTW: There is a similar wording in the Perl license: "You may not
charge a fee for this Package itself."

This is an orphaned package (maintained by "Debian QA"). In case you
use this package yourself, would you like to forward this bug upstream
(just to see if author would be willing to change the license), or
should we just move this to non-free?

I'm Cc:ing Balint, who made the last QA upload (maybe he uses the
package himself, I don't).

Thanks.

Bug#840605: bubblewrap: CVE-2016-8659

[Salvatore Bonaccorso]

Source: bubblewrap
Version: 0.1.2-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerability was published for bubblewrap.

CVE-2016-8659[0].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8659
[1] http://www.openwall.com/lists/oss-security/2016/10/12/5

Regards,
Salvatore

Bug#840207: dependency formats are not converted

[Pirate Praveen]

On Sun, 9 Oct 2016 20:36:06 +0530 Pirate Praveen 
wrote:
> ^1.1.0 and similar should be converted to debian format like >= 1.1.0

node-formatio uses >= 1.x for samsam dependency, it should be converted
to 1.0



signature.asc
Description: OpenPGP digital signature

Processed: found 839659 in 2.1.0-5

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 839659 2.1.0-5
Bug #839659 [src:libgd2] libgd2: CVE-2016-7568: Integer overflow in 
gdImageWebpCtx
Marked as found in versions libgd2/2.1.0-5.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
839659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems