Bug#913350: chmod: changing permissions of '/.../body_neg100.so': Operation not permitted

[Noah Meyerhans]

> I don't recall executing sa-compile as root, but that could have happened of
> course. The file in question is cruft from an older version sa-compile. So 
> could
> the scripts at least be fixed to ignore curft?

It may be reasonable to completely remove /var/lib/spamassassin/compiled
after we're determined that we need to run sa-compile, but before
actually doing so. If anybody thinks this would be a bad idea, please
say so.

> 
> Also, would it be possible for sa-compile to remove year old cruft on 
> upgrades?
> 

Yes, /var/lib/spamassassin/compiled should be removed on package
upgrade. Starting with 3.4.2-2:
https://salsa.debian.org/debian/spamassassin/commit/2ba0392535e47a1db329131c584d08a92a5a6340



signature.asc
Description: PGP signature

Bug#916058: chromium: Widevine not working in chromium 71 and now 72

[Christian Marillat]

Hi,

It's a shame you have uploaded 72.0.3626.7 without fixing this bug.

Christian

Bug#916672: libzvbi-chains.so: undefined symbols: needs -ldl

[Paul Wise]

Package: libzvbi0
Version: 0.2.35-15
Severity: normal
File: /usr/lib/x86_64-linux-gnu/libzvbi-chains.so.0.0.0
User: debian...@lists.debian.org
Usertags: undefined-symbol adequate

libzvbi-chains.so needs to link with -ldl, see the output of adequate,
symtree and objdump below. I detected this on amd64 but the Debian
build log scanner also detected dpkg-buildpackage complaining about it
on most architectures, see the w3m/getbuildlog output below.

I filed this bug at severity minor since I'm not sure if there are any
programs using the zvbi-chains lib or if they already use the libdl
symbols and link with the -ldl flag or not.

This bug report brought to you by adequate:

http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ adequate libzvbi0
libzvbi0:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libzvbi-chains.so.0.0.0 => dlsym

$ man adequate | grep -A4  undefined-symbol
   undefined-symbol
   The symbol has not been found in the libraries linked with the 
binary.
   Either the binary either needs to be linked with an additional 
shared library,
   or the dependency on the shared library package that provides this 
symbol is too weak.

   References: Debian Policy §3.5, §8.6, §10.2.

$ lddtree /usr/lib/x86_64-linux-gnu/libzvbi-chains.so.0.0.0
libzvbi-chains.so.0.0.0 => /usr/lib/x86_64-linux-gnu/libzvbi-chains.so.0.0.0 
(interpreter => none)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
ld-linux-x86-64.so.2 => /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6

$ symtree /usr/lib/x86_64-linux-gnu/libzvbi-chains.so.0.0.0
/usr/lib/x86_64-linux-gnu/libzvbi-chains.so.0.0.0
libpthread.so.0 => 
pthread_testcancel,accept,recv,connect,__errno_location,send
libm.so.6 => !?! useless link !?!
libpng16.so.16 => !?! useless link !?!
libz.so.1 => !?! useless link !?!
libc.so.6 => 
socket,fflush,strcpy,gai_strerror,strrchr,dcgettext,connect,__fdelt_chk,inet_ntoa,time,__stack_chk_fail,__lxstat,unlink,listen,select,realloc,getpid,strdup,strftime,chmod,__assert_fail,gmtime,strtol,mmap,calloc,strlen,send,openlog,getaddrinfo,__errno_location,bind,getnameinfo,__syslog_chk,getsockopt,__fprintf_chk,gethostbyaddr,fputc,recv,fputs,memcpy,memcpy,__vsnprintf_chk,setsockopt,malloc,__ctype_b_loc,getenv,stderr,munmap,__snprintf_chk,readlink,strncasecmp,fwrite,gettimeofday,__memcpy_chk,accept,__strcpy_chk,__cxa_finalize,freeaddrinfo,__vasprintf_chk,strcmp,strerror,__asprintf_chk,free
WEAK => _ITM_deregisterTMCloneTable,__gmon_start__,_ITM_registerTMCloneTable
UNRESOLVED => dlsym

$ objdump -T /lib/x86_64-linux-gnu/libdl.so.2 | grep -E "($(symtree 
/usr/lib/x86_64-linux-gnu/libzvbi-chains.so.0.0.0 | sed -n 's/UNRESOLVED => 
//p' | tr , '|'))$"
13b0 gDF .text  00b9  GLIBC_2.2.5 dlsym

$ w3m -dump https://qa.debian.org/bls/packages/z/zvbi.html | grep -A2 symbol
  • W shlibs-symbol-not-found (alpha, amd64, arm64, armel, armhf, hppa, i386,
ia64, m68k, mips, mips64el, mipsel, powerpc, powerpcspe, ppc64, ppc64el,
riscv64, s390x, sh4, sparc64, x32)

$ w3m -dump https://qa.debian.org/bls/bytag/W-shlibs-symbol-not-found.html | 
grep -A12 description
description

The build logs contains a like like

dpkg-shlibdeps: warning: symbol NAME used by BINARY found in none of the 
libraries.

Possible reasons:

  • A library not linked with a library needed.
While this can sometimes make sense in order to allow the using binary to
decide which of multiple available implementations to use, it means that
dependency information might be incorrect, optimisations like prelinking
might fail and stuff like that.

$ chronic getbuildlog zvbi last

$ grep 'dpkg-shlibdeps: warning: symbol .* used by .* found in none of the 
libraries' *.log
zvbi_0.2.35-15_alpha.log:dpkg-shlibdeps: warning: symbol dlsym used by 
debian/libzvbi0/usr/lib/alpha-linux-gnu/libzvbi-chains.so.0.0.0 found in none 
of the libraries
zvbi_0.2.35-15_amd64.log:dpkg-shlibdeps: warning: symbol dlsym used by 
debian/libzvbi0/usr/lib/x86_64-linux-gnu/libzvbi-chains.so.0.0.0 found in none 
of the libraries
zvbi_0.2.35-15_arm64.log:dpkg-shlibdeps: warning: symbol dlsym used by 
debian/libzvbi0/usr/lib/aarch64-linux-gnu/libzvbi-chains.so.0.0.0 found in none 
of the libraries
zvbi_0.2.35-15_armel.log:dpkg-shlibdeps: warning: symbol dlsym used by 
debian/libzvbi0/usr/lib/arm-linux-gnueabi/libzvbi-chains.so.0.0.0 found in none 
of the libraries
zvbi_0.2.35-15_armhf.log:dpkg-shlibdeps: warning: symbol dlsym used by 
debian/libzvbi0/usr/lib/arm-linux-gnueabihf/libzvbi-chains.so.0.0.0 found in 
none of the libraries
zvbi_0.2.35-15_hppa.log:dpkg-shlibdeps: warning: symbol dlsym used by 
debian/libzvbi0/usr/lib/hppa-linux-gnu/libzvbi-chains.so.0.0.0 found 

Bug#916671: ITP: ruby-discordrb-webhooks-blackst0ne -- Webhook client for discordrb. Fork by blackst0ne

[Pirate Praveen]

package: wnpp
severity: wishlist
owner: Pirate Praveen 

from rubygems.org/gems/discordrb-webhooks-blackst0ne
dependency of gitlab 11.6.x

















signature.asc
Description: OpenPGP digital signature

Bug#916669: (no subject)

[pavel]

Subject: cryptsetup: ERROR: Couldn't resolve device rootfs
Package: src:linux
Version: 4.18.20-2
Severity: important

Dear Maintainer,

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

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

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


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: HP
product_name: ProLiant DL360 G5
product_version: 
chassis_vendor: HP
chassis_version: 
bios_vendor: HP
bios_version: P58

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 5000P Chipset Memory Controller 
Hub [8086:25d8] (rev 93)
Subsystem: Hewlett-Packard Company 5000P Chipset Memory Controller Hub 
[103c:31fd]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] MSI: Enable- Count=1/2 Maskable- 64bit-
Address: fee0  Data: 
Capabilities: [6c] Express (v1) Root Port (Slot-), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE-
DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 256 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x4, ASPM L0s, Exit 
Latency L0s unlimited, L1 unlimited
ClockPM- Surprise+ LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt- ABWMgmt-
RootCtl: ErrCorrectable- ErrNon-Fatal+ ErrFatal+ PMEIntEna+ 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
Capabilities: [100 v1] Advanced Error Reporting
UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk:  DLP- SDES+ TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
UESvrt: DLP+ SDES- TLP+ FCP+ CmpltTO+ CmpltAbrt+ UnxCmplt+ 
RxOF+ MalfTLP+ ECRC- UnsupReq+ ACSViol-
CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk:  RxErr+ BadTLP+ BadDLLP+ Rollover+ Timeout+ NonFatalErr-
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Kernel driver in use: pcieport
Kernel modules: shpchp

00:03.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 
Port 3 [8086:25e3] (rev 93) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] MSI: Enable- Count=1/2 Maskable- 64bit-
Address: fee0  Data: 
Capabilities: [6c] Express (v1) Root Port (Slot-), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE-
DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 256 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #3, Speed 2.5GT/s, Width x4, ASPM L0s, Exit 
Latency L0s unlimited, L1 unlimited
ClockPM- Surprise+ LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt- ABWMgmt-
  

Bug#916105: lxqt-panel: menu-button opens ~5.5cm above panel (on portrait display, normal on landscape

[Chris Guiver]

I just noticed; if I enter a search term, the menu instantly drops
down to just above the panel. Erasing the entered text so search field
is blank doesn't return the menu up on screen (to ~5.5cm above panel),
but it stays low touching bottom panel.

So touching menu on panel bottom of my portrait display causes menu to
open ~5.5cm above the panel with my prior display showing underneath
menu.  entering T & BACKSPACE (as if searching  for terminal & then
changing my mind) causes the MENU to re-draw touching the panel
without the ~5.5cm gap.

Bug#916668: ITP: buildstream -- toolset for the BuildStream project

[Jeremy Bicha]

Package: wnpp
Severity: wishlist
Owner: jbi...@debian.org
X-Debbugs-CC: debian-de...@lists.debian.org, debian-gtk-gn...@lists.debian.org

Package Name: buildstream
Version: 1.2.3
Upstream Authors: Codethink, Tristan Van Berkom, Jürg Billeter
License : LGPL-2+
Programming Lang: Python3
Homepage: https://buildstream.build/
Description:  toolset for the Buildstream project
 BuildStream is a GNOME project to improve the continuous integration of
 complex systems and applications. The project aims to pay special
 attention to those developers and integrators who care about the
 maintainability of their projects during a long period of time.
 .
 BuildStream is also a powerful and flexible software integration toolset.
 It has been designed to create different outputs out of a unique input
 and, at the same time, it is able to adapt to complex workflows, even
 when additional build tools are required. An important part of
 BuildStream is a sister project called BuildGrid, that allows
 BuildStream to build at scale.

Other Info
--
Note that this package installs a new 3-letter binary: /usr/bin/bst

I intend to maintain this with the Debian GNOME Team.

Initial packaging is at https://salsa.debian.org/gnome-team/buildstream/

Docs are at https://buildstream.gitlab.io/buildstream/

BuildStream is sort of, but not really, a replacement for jhbuild.
BuildStream is used to build GNOME releases (since GNOME 3.28) and the
Freedesktop SDKs. The GNOME and KDE Flatpak runtimes depend on the
Freedesktop SDKs.

Thanks,
Jeremy Bicha

Bug#911997: git: Apply diff from Ubuntu

[Jeremy Bicha]

Hi, I thought you might have forgotten about this bug and proposed
patch since it hasn't been included in your recent Debian releases for
git.

Thanks,
Jeremy Bicha

Bug#704005: git cvsimport: reads /tmp/.gitattributes

[Helmut Grohne]

Hi Jonathan,

On Sun, Dec 16, 2018 at 01:45:48PM -0800, Jonathan Nieder wrote:
> > git-cvsimport invokes git-hash-object in a way that causes it to read
> > /tmp/.gitattributes. This patch avoids the behaviour by passing 
> > --no-filters to
> > git-hash-object. An alternative approach would be to put create a temporary
> > directory call git-hash-object on files withing that private directory.
> >
> > --- git-cvsimport.orig  2013-04-03 09:53:47.0 +0200
> > +++ git-cvsimport   2013-04-03 09:51:20.0 +0200
> > @@ -1030,7 +1030,7 @@
> > my $pid = open(my $F, '-|');
> > die $! unless defined $pid;
> > if (!$pid) {
> > -   exec("git", "hash-object", "-w", $tmpname)
> > +   exec("git", "hash-object", "--no-filters", "-w", 
> > $tmpname)
> > or die "Cannot create object: $!\n";
> > }
> > my $sha = <$F>;
> 
> Sorry for the very long silence.  May I forge your sign-off when passing
> this upstream?  See
> https://www.kernel.org/pub/software/scm/git/docs/SubmittingPatches.html#sign-off
> for more details about what this means.

Yes please.

Helmut

Bug#915469: [Pkg-electronics-devel] Bug#915469: gwave FTBFS: error: found development files for Guile 2.0, but /usr/bin/guile has effective version 2.2

[أحمد المحمودي]

reassign 915469 g-wrap 1.9.15-0.2
quit

On Tue, Dec 04, 2018 at 12:36:38AM +0200, Adrian Bunk wrote:
> checking for GUILE... yes
> checking for guile... /usr/bin/guile
> configure: error: found development files for Guile 2.0, but /usr/bin/guile 
> has effective version 2.2
---end quoted text---

The problem is in g-wrap package which depends on guile-library (which in 
turn pulls guile-2.2)

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#915584: dicoweb: fails to install with python 3.7

[أحمد المحمودي]

On Wed, Dec 05, 2018 at 03:15:59AM +0100, Andreas Beckmann wrote:
>   Setting up python3 (3.7.1-2) ...
>   [Errno 2] No such file or directory: '/usr/share/dicoweb/settings.py'
---end quoted text---

'/usr/share/dicoweb/settings.py' is a symlink to 
/etc/dicoweb/settings.py , could this be the cause of the problem ? If 
so, what should be done?

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#909952: RFP: bitlbee-mastodon -- Mastodon plugin for bitlbee IRC gateway

[Antoine Beaupre]

Just uploaded 1.4.0-1 into Debian, and it should hit NEW soon. Source is
also on Salsa here:

https://salsa.debian.org/debian/bitlbee-mastodon

A.

On Fri, Dec 14, 2018 at 09:50:12AM -0500, Antoine Beaupre wrote:
> Control: retitle -1 ITP: bitlbee-mastodon -- Mastodon plugin for bitlbee
> 
> Now that 1.4.0 works reliably here, I am probably going to package this
> for Debian unless someone else is working on it already.

-- 
We don't need any more heroes.
We just need someone to take out recycling.
- Banksy


signature.asc
Description: PGP signature

Bug#916667: RFP: node-gulp-replace -- A string replace plugin for gulp

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-gulp-replace
  Version : 1.0.0
  Upstream Author : Larry Davis
* URL : https://notabug.org/makenotabuggreatagain/gulp-replace
* License : MIT
  Programming Lang: javascript
  Description : A string replace plugin for gulp 3

Can be called with a string, function or regex.
Dependency of node-semantic-ui ( #915062 )

Bug#916666: python-pip's autopkg tests are failing (blocking python3.7)

[Matthias Klose]

Package: src:pythonn-pip
Version: 18.1-2
Severity: serious
Tags: sid buster

python-pip's autopkg tests are failing (blocking python3.7):

autopkgtest [14:05:30]:  summary
pip2-root.sh PASS
pip3-root.sh PASS
pip2-user.sh FAIL stderr:   The script world is installed in
'/tmp/autopkgtest-lxc.a8273n4w/downtmp/autopkgtest_tmp/.local/bin' which is not
on PATH.
pip3-user.sh FAIL stderr:   The script world is installed in
'/tmp/autopkgtest-lxc.a8273n4w/downtmp/autopkgtest_tmp/.local/bin' which is not
on PATH.
pip3-editable.sh PASS

Bug#916493: autopkgtest-build-qemu builds image which does not successfully boot

[Michael Biebl]

Am 17.12.18 um 02:36 schrieb Michael Biebl:
> The reason for the timeout seems to be, that / is never remounted rw. As
> a result, lots of services fail to start and will eventually time out,
> including networking.service.
> 
> Begin: Loading essential drivers ... done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top
> ... done.
> Begin: Running /scripts/local-premount ... done.
> Warning: fsck not present, so skipping root file system
> [1.477685] EXT4-fs (sda1): mounted filesystem with ordered data
> mode. Opts: (null)
> 
> That looks suspicious...

Looking further into this, it turned out that /etc/fstab was empty.
As a result, / was never remount rw.

Not sure if this is a bug in vmdb2 or autopkgtest-build-qemu

Unfortunately there is no documentation for vmdb2


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



signature.asc
Description: OpenPGP digital signature

Bug#916665: Update tkgate (version 2.1)

[Alexey Loginov]

Package: tkgate
Version: 2.0

Version 2.0 was released many years ago.
Current version is 2.1.
Url: https://bitbucket.org/starling13/tkgate

Bug#916664: RFP: node-gulp-watch -- File watcher that uses super-fast chokidar and emits vinyl objects.

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-gulp-watch
  Version : 5.0.1
  Upstream Author : (c) 2014 Vsevolod Strukchinsky 
* URL : https://notabug.org/makenotabuggreatagain/gulp-watch
* License : Expat
  Programming Lang: javascript
  Description : File watcher that uses super-fast chokidar and emits vinyl 
objects.

"Watch, that actually is an endless stream"

This is a prerequisite to node-semantic-ui ( #915062 ).

Bug#916649: [pkg-cryptsetup-devel] Bug#916649: crytpsetup:

[Guilhem Moulin]

Control: retitle  -1 `/etc/init.d/cryptdisks stop` should ignore devices 
holding / and /usr
Control: severity -1 wishlist

Hi,

On Sun, 16 Dec 2018 at 13:28:37 -0800, r...@riseup.net wrote:
> When shuting down my Devuan LVM + LUKS install, it hangs just at the end
> of the shutdown sequence presenting messages like "sda5_crypt is busy"
> and "sdb_crypt is busy". Only after 30 seconds or so pass, it acatully
> shuts down.

https://tracker.debian.org/news/181876/accepted-lvm2-20284-3-source-amd64/

> Aplying one the patchs available at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792552#5 or

Which patch?  something equivalent to #5 is already present in 2:1.7.3-4


https://sources.debian.org/src/cryptsetup/2:1.7.3-4/debian/cryptdisks.functions/#L765

Or do you mean `dmsetup remove_all` from #24?  Like for

> https://bugs.devuan.org//cgi/bugreport.cgi?bug=237 fixes the problems
> just fine for me.

/etc/init.d/lvm2 no longer deactivates LVs on shutdown since lvm2
≥2.02.84-3.  But I don't see which doing so should be the job of
/etc/init.d/cryptsetup instead.

Regardless, we won't be able to lock devices holding / or /usr.  AFAICT
that's where `/etc/init.d/cryptdisks stop` is choking with the repeated
“… is busy” messages.  For these devices the script might as well return
failure immediately and not try again.

Cheers,
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#916493: autopkgtest-build-qemu builds image which does not successfully boot

[Michael Biebl]

The reason for the timeout seems to be, that / is never remounted rw. As
a result, lots of services fail to start and will eventually time out,
including networking.service.

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top
... done.
Begin: Running /scripts/local-premount ... done.
Warning: fsck not present, so skipping root file system
[1.477685] EXT4-fs (sda1): mounted filesystem with ordered data
mode. Opts: (null)

That looks suspicious...


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



signature.asc
Description: OpenPGP digital signature

Bug#916662: all_perl_files_ok should skip .git

[Russ Allbery]

Submitted upstream as https://github.com/manwar/Test-Strict/issues/26.

-- 
Russ Allbery (r...@debian.org)   

Bug#916663: libc6-udeb segfaults in buster alpha 4

[Vincent McIntyre]

Package: libc6-udeb
Version: 2.28-2
Severity: important

Trying to install with the netinst image from [1]

The hardware is a Dell Optiplex with 64-bit Intel processor.
There is an old install of jessie on the disk, which is two
SSDs in software raid-1. One partition for /, the rest is LVM.

I am doing the interactive install.
Set country = AU, keyboard = US, TZ location = New South Wales
Set up root password and default user account.
Set mirror to: ftp.au.debian.org, also tried deb.debian.org.

Right after libc6-udeb is downloaded I get a segfault.

Below is a transcription of the console (alt-f4) at the point
where the failure occurs. Once the segfault starts, I can't
run any commands at all, not even --.

Dec 16 23:59:50 anna-install: Installing partman-auto-lvm
Dec 16 23:59:50 anna[4872] DEBUG: retrieving libc6-udeb 2.28-2
Dec 16 23:59:51 anna[4072] 2018-12-16 23:59:21 
URL:http://cdn-fastly.deb.debian.org/debian//pool/main/glibc/libc6_udeb_2.28-2_amd64.udeb
 [1323560/1323560] -> 
"/var/cache/anna/_fetch-url_libc6-udeb_2.28-2_amd64.udeb.4878" [1]
Dec 16 23:59:51 kernel: [  149.467327] sh[4906]: segfault at 401d2460 ip 
7175b54b207 sp 7ffdf4711990 error 4 in libc-2.28.so[7f75b54a7000+148000]
Dec 16 23:59:51 kernel: [  149.467332] Code: 66 45 85 c0 0f 84 71 01 00 00 4c 
8b 41 10 4d 85 6d 01 00 00 4c 39 cd 0f 84 70 01 00 00 0f 1f 00 48 83 c7 04 83 
c0 01  47 fc 01 75 83 89 c1 48 8d 0c 49 49 8d 0c ca 44 0f b7 41 06 66

In case this is a repeat of whatever 837123 was (it seems different)
I tried booting a stretch netinst image on the same hardware, using
the same tftp server, deb.debian.org as mirror. All seems fine, the
installer dropped me into the partitioner so I left it at that.

I tried on different hardware, to check.
This was similar to the first system (Dell Optiplex 990),
but running stretch. Single 1Tb SATA disk, separate / and the rest LVM.
I see the same segfault at the same point the installation process.

Kind regards
Vince

[1] 
http://ftp.us.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/debian-installer/amd64

-- 

Bug#916662: all_perl_files_ok should skip .git

[Russ Allbery]

Package: libtest-strict-perl
Version: 0.47-1
Severity: normal

Test::Strict::all_perl_files_ok contains hard-coded logic to exclude
CVS and .svn directories, but doesn't skip .git directories.  It does
provide a way to pass in a list of files to skip, but that is applied
as a filter to the list of individual files, so it cannot be used to
skip directories.

This means that if there are Perl files in .git (which may be the case
if one has used dgit from this checkout, since it makes its own private
copy of the unpacked source package), they will be picked up and tested
incorrectly by this module.

The quick fix is that .git should be added to the hard-coded skip list
in the module.  A better, complementary fix would be to move processing
of $Test::Skip::TEST_SKIP into $want_sub in _all_files and use it to
prune directories as well.  I think it's safe to assume this is what the
caller would want if they list a directory in TEST_SKIP.

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

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

Versions of packages libtest-strict-perl depends on:
ii  libdevel-cover-perl  1.31-1+b2
ii  perl 5.28.1-3

libtest-strict-perl recommends no packages.

libtest-strict-perl suggests no packages.

-- no debconf information

Bug#916379: kbtin FTCBFS: uses the wrong pkg-config

[Adam Borowski]

Control: tags -1 +pending

On Thu, Dec 13, 2018 at 08:33:13PM +0100, Helmut Grohne wrote:
> kbtin fails to cross build from source, because AC_ARG_LIB hard codes
> the build architecture pkg-config. The attached patch fixes that. Please
> consider applying it.

> --- kbtin-1.0.19.orig/ac_arg_lib.m4
> +++ kbtin-1.0.19/ac_arg_lib.m4

Great; applied to [upstream] git.  Thanks!


Meow.
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Ivan was a worldly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄ to the city of his birth to die.

Bug#916661: libc6:amd64: Please document transcendental functions (cos, log, tan, atan2, pow, ...) accuracy

[Witold Baryluk]

Package: libc6
Version: 2.27-8
Severity: normal


AFAIK, accuracy of transcendental functions in libm, like

sin
cos
atan
exp
log
pow
tan
atan2

is completly undocumented, and do not conform to IEEE 784-2008 chapter
9.2, table 9.1. These are recommended ("optional"), and not mandatory. It
is understood that adhering fully to this chapter even for some of the
recommended functions, would come at the performance cost without proper
hardware support, or hardware tricks to make library implementations fast
(i.e. like libultim, or CRlibm).

However, documenting properly accuracy and rounding behaviour of glibc
provided mathematical functions would serve people very well. At the
moment, it is a complete blackbox, and depends on a target hardware too.

Best regards,
Witold



-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/32 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libc6:amd64 depends on:
ii  libgcc1  1:8.2.0-9

libc6:amd64 recommends no packages.

Versions of packages libc6:amd64 suggests:
ii  debconf [debconf-2.0]  1.5.69
pn  glibc-doc  
ii  libc-l10n  2.27-8
ii  locales2.27-8

-- debconf information:
  glibc/restart-failed:
  glibc/disable-screensaver:
  glibc/kernel-not-supported:
  libraries/restart-without-asking: false
  glibc/upgrade: true
  glibc/kernel-too-old:
  glibc/restart-services:

Bug#645439: obsolete conffiles not removed on upgrades

[Gabriel F. T. Gomes]

The next upload will fix this problem.  The relevant commits in the git
repository are:

https://salsa.debian.org/debian/bash-completion/commit/c9203c53ea75d6fe708bf2deb82f1341072a97db
https://salsa.debian.org/debian/bash-completion/commit/e55d81a56ae89ee0b9cd3bc1e6fc683a33c17991
https://salsa.debian.org/debian/bash-completion/commit/7d413831f1a8ac1181f21efdae594fc8ac5ec0f3
https://salsa.debian.org/debian/bash-completion/commit/2c23594b23c00a663e396d185922e577881e7d16
https://salsa.debian.org/debian/bash-completion/commit/e1319b586bca130e9fbd6e1c927e3ae8fb970a94

Bug#905342: [pkg-apparmor] Bug#905342: apache fpm not working anymore

[Ivan Sergio Borgonovo]

On 12/16/18 9:23 PM, intrigeri wrote:

Hi,

intrigeri:

Ivan Sergio Borgonovo:

As you said probably apparmor seems not to be the culprit.



Nov 04 20:21:13 kerberos audit[1280]: AVC apparmor="DENIED" operation="mount" info="failed type match" error=-13 
profile="lxc-container-default-cgns" name="/sys/fs/cgroup/unified/" pid=1280 comm="systemd" fstype="cgroup2" 
srcname="cgroup2" flags="rw, nosuid, nodev, noexec"



This one looks like a bug in the LXC AppArmor profiles, please report
it against the lxc package.




[...]
… and many more processes confined under the
lxc-container-default-cgns profile.



Are you actually running dovecot, tor, postgres, sshd, smdb, Postfix,
dhclient etc. in LXC containers? Or is the lxc-container-default-cgns
profile somehow erroneously applied to these processes?


Gentle ping on this?


Sorry.

Yes, I'm actually running tor, postgres, samba, postfix, dovecot, 
spamassassin/spamd...


The problem is still there eg.

Dec 16 15:01:57 caronte systemd[1]: Starting The PHP 7.0 FastCGI Process 
Manager
Dec 16 15:04:36 caronte systemd[1]: Started The PHP 7.0 FastCGI Process 
Manager.



--
Ivan Sergio Borgonovo
https://www.webthatworks.it https://www.borgonovo.net

Bug#916660: luola: FTBFS with ld --as-needed

[Logan Rosen]

Package: luola
Version: 1.3.2-11
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

Dear Maintainer,

luola currently fails to build from source with ld --as-needed, which is
enabled by default in Ubuntu. This linker option requires that
libraries be placed after the objects that require them, but the current
logic to add -lm to LDFLAGS adds it near the beginning of the command
with the linker options.

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

  * d/p/link_against_libm: Use Autotools to find/link against libm instead of
manually appending -lm to LDFLAGS to fix FTBFS with ld --as-needed.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.18.0-12-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru luola-1.3.2/debian/patches/link_against_libm 
luola-1.3.2/debian/patches/link_against_libm
--- luola-1.3.2/debian/patches/link_against_libm1969-12-31 
19:00:00.0 -0500
+++ luola-1.3.2/debian/patches/link_against_libm2018-12-16 
19:15:32.0 -0500
@@ -0,0 +1,10 @@
+--- a/configure.ac
 b/configure.ac
+@@ -73,6 +73,7 @@
+ #AC_CHECK_LIB(pthread, main,, AC_MSG_ERROR(SDL needs pthread !))
+ AC_CHECK_LIB([SDL_image],[main],[],AC_MSG_ERROR(SDL_image is needed))
+ AC_CHECK_LIB([z],[main],[],AC_MSG_ERROR(libz is needed))
++AC_SEARCH_LIBS([hypot],[m],[],AC_MSG_ERROR(libm is needed))
+ 
+ AC_CONFIG_FILES([Makefile
+  contrib/Makefile
diff -Nru luola-1.3.2/debian/patches/series luola-1.3.2/debian/patches/series
--- luola-1.3.2/debian/patches/series   2018-09-13 17:50:13.0 -0400
+++ luola-1.3.2/debian/patches/series   2018-12-16 19:12:42.0 -0500
@@ -2,3 +2,4 @@
 luola-manpage
 remove_implicit_declaration
 hurd_path_max
+link_against_libm
diff -Nru luola-1.3.2/debian/rules luola-1.3.2/debian/rules
--- luola-1.3.2/debian/rules2018-09-13 17:50:13.0 -0400
+++ luola-1.3.2/debian/rules2018-12-16 19:15:38.0 -0500
@@ -5,7 +5,6 @@
 export DH_VERBOSE=1
 
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
-export DEB_LDFLAGS_MAINT_APPEND = -lm
 
 %:
dh $@

Bug#916659: nailgun 1.0.0 depends on JUnit5

[Hideki Yamane]

Package: nailgun
Severity: normal

 Just note, nailgun 1.0.0 depends on JUnit5 that is not packaged yet.
 So, I cannot update nailgun from 0.9.3 to 1.0.0...


-- 
Hideki Yamane 

Bug#741883: /usr/share/gitweb/static/gitweb.js: gitweb blame does not work correctly when $feature{'javascript-actions'} is enabled

[Jonathan Nieder]

forwarded 741883 https://public-inbox.org/git/20181216232429.gj75...@google.com/
quit

Hi,

In March, 2014, Robert Luberda wrote:

> The following setting in gitweb.conf
>  $feature{'javascript-actions'}{'default'} = [1];
> breaks the gitweb's blame page: clicking on line numbers displayed in
> the second column on the page does absolutelly nothing (at least
> in iceweasel and chromium browsers). Without this setting, clicking on
> line numbers loads the previous version of the line.
>
> The patch below fixes the issue:

Thanks for the thoughtful report and patch.  Let's take this upstream.

Sincerely,
Jonathan

Bug#916658: RFS: apt-listbugs/0.1.26

[Francesco Poli (wintermute)]

Package: sponsorship-requests
Severity: normal

Hello everybody!

I prepared a new version of the apt-listbugs package (0.1.26):
it is ready to be uploaded to Debian unstable.
Could someone please build the package from commit
[c04fcb88ed8ba0f87c62d5711f394dd455231754], and sponsor its upload to
sid?

[c04fcb88ed8ba0f87c62d5711f394dd455231754]: 


The changes since the last upload are:

  * fixed "executes xdg-open as root user": implemented a way to drop root
privileges when invoking querybts or a browser, if we can figure out
which regular user became root (via "su -", "sudo", ...) and if
package s6 is installed (Closes: #910122)
  * added xdg-open to the list of possible ways to invoke an appropriate
web browser
  * enhanced interface consistency regarding external program (querybts
and web browser) invocation
  * enhanced error handling consistency regarding external program invocation
  * converted README.Debian into README.md (in markdown syntax) and
improved the document a bit
  * created FAQ.md by taking some parts from README.md
  * updated German translation, thanks to Chris Leick! (Closes: #914703)
  * updated Russian translation, thanks to Sergey Alyoshin! (Closes: #915374)
  * updated Portuguese translation, thanks to Miguel Figueiredo!
(Closes: #915802)
  * updated Italian translation, thanks to Luca Monducci!
  * updated Dutch translation, thanks to Frans Spiesschaert! (Closes: #916365)
  * updated Danish translation, thanks to Morten Bo Johansen! (Closes: #916384)
  * updated French translation, thanks to Jean-Baka Domelevo Entfellner!
(Closes: #916509)


Thank you so much for your time and dedication!
Bye.

Bug#916656: Requalifying severity from serious to important

[Emmanuel Halbwachs]

Severity: important

I red about bug severities and I feel 'important' is more appropriate
for this bug than 'serious', so this is an attempt to requalify.

Thanks,

-- 
Emmanuel

Bug#916657: qtscript-opensource-src: Segmentation fault in libQt5Script.so.5.11.2 building qbs

[John David Anglin]

Source: qtscript-opensource-src
Version: 5.11.2+dfsg-2
Severity: normal
Tags: patch

Dear Maintainer,

Please look at analysis for qbs build failure here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916626

The segementation fault occurs because the code in currentThreadStackBase()
incorrectly adds the stack size to the stack address returned by
pthread_attr_getstack().  The stack on hppa grows up.

With the attached patch, I had a successful build of qtscript-opensource-src:
https://buildd.debian.org/status/fetch.php?pkg=qtscript-opensource-src=hppa=5.11.2%2Bdfsg-2%2Bb1=1545000897=0

The patch probably fixes the bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880034

Regards,
Dave Anglin

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

Kernel: Linux 4.14.88+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Index: 
qtscript-opensource-src-5.11.2+dfsg/src/3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp
===
--- 
qtscript-opensource-src-5.11.2+dfsg.orig/src/3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp
+++ 
qtscript-opensource-src-5.11.2+dfsg/src/3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp
@@ -672,7 +672,12 @@ static inline void* currentThreadStackBa
 pthread_attr_destroy();
 stackThread = thread;
 }
+#if defined(__hppa__)
+// Stack grows up.
+return static_cast(stackBase);
+#else
 return static_cast(stackBase) + stackSize;
+#endif
 #else
 #error Need a way to get the stack base on this platform
 #endif

Bug#916589: telegram-desktop: Attachment dialog opens behind the parent window

[Keyikedalube Ndang]

GNOME desktop environment.

Bug#916655: postgresql-11: Please depend on locales | locales-all

[Elrond]

Package: postgresql-11
Version: 11.1-1
Severity: wishlist

Hi,

postgresql-11 currently "Depends: locales" and "Suggests:
locales-all".  Installing locales-all probably makes
installing locales unnecessary.  So I guess, only
installing one of the two is enough?

If so, the Depends should be changed to "locales |
locales-all".


Cheers

Elrond

Bug#916654: vdr-plugin-epgsearch 2.2.0+git20170817-2

[klak]

Package:vdr-plugin-epgsearch 
Version:2.2.0+git20170817-2


Dear maintainer, after the daily update of testing the vdr-plugin-epgsearch 
kills vdr.

Dec 16 17:28:12 debt27 kernel: [ 2024.332571] EPGSearch: conf[2261]: segfault 
at 130 ip 7f7952441f75 sp 7f7934df7a50 error 4 in 
libvdr-epgsearch.so.2.4.0[7f79523f1000+fc000] 
Dec 16 17:28:12 debt27 systemd[1]: vdr.service: Main process exited, 
code=killed, status=11/SEGV 
Dec 16 17:28:12 debt27 systemd[1]: vdr.service: Failed with result 'signal'. 
Dec 16 17:28:12 debt27 systemd[1]: vdr.service: Service RestartSec=100ms 
expired, scheduling restart. 
Dec 16 17:28:12 debt27 systemd[1]: vdr.service: Scheduled restart job, restart 
counter is at 5. 
Dec 16 17:28:12 debt27 systemd[1]: vdr.service: Start request repeated too 
quickly. 
Dec 16 17:28:12 debt27 systemd[1]: vdr.service: Failed with result 'signal'.

Update:

Paketaktualisierung (Upgrade) wird berechnet...
Die folgenden Pakete sind zurückgehalten worden:
  iptables isc-dhcp-client libip4tc0 libip6tc0 libiptc0 libxtables12
Die folgenden Pakete werden aktualisiert (Upgrade):
  bsdutils cpp-7 cpp-8 dash dbus exim4 exim4-base exim4-config
  exim4-daemon-light fdisk g++-8 gcc-7 gcc-7-base gcc-8 gcc-8-base grep
  grub-common grub-pc grub-pc-bin grub2-common gtk-update-icon-cache
  isc-dhcp-common libasan4 libasan5 libatomic1 libblkid1 libc-bin libc-dev-bin
  libc-l10n libc6 libc6-dev libcc1-0 libcilkrts5 libcryptsetup12 libcups2
  libdbus-1-3 libfdisk1 libgcc-7-dev libgcc-8-dev libgcc1 libgomp1 libhogweed4
  libitm1 liblsan0 libmariadbclient18 libmount1 libmpx2 libnettle6
  libpam-systemd libpython3.6-minimal libpython3.6-stdlib libquadmath0
  librsvg2-2 librsvg2-common libsmartcols1 libsqlite3-0 libstdc++-8-dev
  libstdc++6 libsystemd0 libtsan0 libubsan0 libubsan1 libudev1 libuuid1
  libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-render0
  libxcb-shm0 libxcb-sync1 libxcb-xfixes0 libxcb1 libzvbi-common libzvbi0
  locales mount multiarch-support python3.6 python3.6-minimal systemd
  systemd-sysv sysvinit-utils telnet udev util-linux
86 aktualisiert, 0 neu installiert, 0 zu entfernen und 6 nicht aktualisiert.
Es müssen 80,9 MB an Archiven heruntergeladen werden.

Paketaktualisierung (Upgrade) wird berechnet...
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
  libdns-export1102 libisc-export169 libnftnl7
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
Die folgenden NEUEN Pakete werden installiert:
  libdns-export1104 libisc-export1100 libnftnl11
Die folgenden Pakete werden aktualisiert (Upgrade):
  iptables isc-dhcp-client libip4tc0 libip6tc0 libiptc0 libxtables12
6 aktualisiert, 3 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 2.421 kB an Archiven heruntergeladen werden.


Greets klak

Bug#740154: permission warning on repo access: unable to access '/root/.config/git/attributes'

[Jonathan Nieder]

Hi,

In February, 2014, martin f krafft wrote:

> $HOME seems unset when git-daemon starts, which causes
>
>   remote: warning: unable to access '/root/.config/git/attributes': 
> Permission denied
>
> to be printed on cloning.
>
> exporting $HOME e.g. to gitdaemon's home directory, or
> $GIT_DAEMON_BASE_PATH fixes this. Maybe the init.d script could do
> that?

Thanks for reporting, and sorry for the slow reply.  gitdaemon's home
directory is /nonexistent, so do you mean something like

diff --git i/debian/git-daemon-sysvinit.git-daemon.init 
w/debian/git-daemon-sysvinit.git-daemon.init
index cc98a00bad..e1ab4b3947 100644
--- i/debian/git-daemon-sysvinit.git-daemon.init
+++ w/debian/git-daemon-sysvinit.git-daemon.init
@@ -49,8 +49,10 @@ do_start()
#   0 if daemon has been started
#   1 if daemon was already running
#   2 if daemon could not be started
+   HOME=/nonexistent \
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON 
--test > /dev/null \
|| return 1
+   HOME=/nonexistent \
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
$DAEMON_ARGS \
|| return 2

(plus the analogous change for git-daemon-run)?

Sincerely,
Jonathan

Bug#916653: please package upstream 20181120 release

[Russ Allbery]

Package: perltidy
Version: 20180220-1
Severity: normal

Upstream has released 20181120, which improves perltidy's ability to
detect consecutive variable assignments that should be aligned.  This
unfortunately means that there is some code that passes with 20180220
and fails with 20181120 which, when fixed for 20181120, fails with
20180220.  This makes mismatches of versions particularly painful.

Since Travis-CI pulls directly from CPAN, this means that I have to
choose between skipping Travis-CI tests for perltidy (by way of
Perl::Critic), which I don't want to do because they're useful for
pull requests, and having tests fail on my local system.

Could you package the 20181120 release?  I'm also happy to help if you
would like.

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

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

Versions of packages perltidy depends on:
ii  perl  5.28.1-3

perltidy recommends no packages.

perltidy suggests no packages.

-- no debconf information

Bug#916626: Acknowledgement (qbs: FTBFS on hppa: Segmentation fault (core dumped))

[John David Anglin]

On 2018-12-16 1:54 p.m., John David Anglin wrote:
> On 2018-12-16 1:21 p.m., John David Anglin wrote:
>> It looks to me as if the test "p != e" should be "p < e".
> 
> On further thought, I think gcc has miscompiled this function.

No, the bug is in currentThreadStackBase().  The stack grows up on hppa
and the base is incorrectly calculated.

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

Bug#916652: lintian: incorrectly complains about 'missing-debian-source-format'

[Holger Wansing]

Package: lintian
Severity: normal

I found under
https://lintian.debian.org/full/debian-b...@lists.debian.org.html#installation-guide_20180923
that lintian says "debian source format file is missing" for the
installation-guide package, while the file is there indeed!
And it contains

ned@t520:~/deb_holgerw/debian-installer/trunk/installation-guide$ cat 
debian/source/format 
3.0 (native)

So there is apparently a chance to gain false possitives here :-)


Holger



-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#916651: gbp initial push needs deterministic order

[Tong Sun]

Package: git-buildpackage
Version: 0.9.10+nmu1
Severity: minor

Hi Guido,

It appears that the initial gbp push is pushing branches in a
non-deterministic order. The details are described below:

https://lists.debian.org/debian-go/2018/12/msg00023.html
https://lists.debian.org/debian-go/2018/12/msg00022.html

Why it matters is that, according to Alexandre Viau at

https://lists.debian.org/debian-go/2018/10/msg00024.html

When we initially creating the repositories, it is important to push the
debian/sid branch first, as

The first branch pushed will be the default branch on salsa.

He "had to change them in the gitlab gui. We wouldn't have to do that
if you pushed
the debian branches first."

So please consider pushing the current branch first for the initial gbp push.

Thanks

Tong

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git-buildpackage depends on:
ii  devscripts 2.17.6+deb9u1
ii  git1:2.11.0-3+deb9u3
ii  man-db 2.7.6.1-2
ii  python33.5.3-1
ii  python3-dateutil   2.6.1-1
ii  python3-pkg-resources  33.1.1-1
ii  sensible-utils 0.0.9+deb9u1

Versions of packages git-buildpackage recommends:
ii  pbuilder  0.228.7
ii  pristine-tar  1.38
ii  python3-requests  2.12.4-1
ii  sbuild0.77.1-2

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
ii  sudo 1.8.19p1-2.1
ii  unzip6.0-21

-- no debconf information

Bug#914392: transition: coin3

[Leopold Palomo-Avellaneda]

El 28/11/18 a les 19:12, Emilio Pozuelo Monfort ha escrit:
> On 22/11/2018 23:33, Leopold Palomo-Avellaneda wrote:
>> Subject: transition: coin3
>> Package: release.debian.org
>> User: release.debian@packages.debian.org
>> Usertags: transition
>> Severity: normal
>>
>> Dear release team,
>>
>> I would like to ask a transition slot for the coin3 library. The package
>> has been reworked and a new version of the upstream has been packaged.
>>
>> Upstream have changed the build system to CMake and this has been used
>> for the package. This has an implication that it will break with FTBFS
>> the packages that use it: pivy, freecad, openscenegraph-3.4 and soqt, I
>> have contacted with all the maintainers and they are aware about it and
>> we are preparing patches or simple disable in any case.
> 
> Where are you discussing that? I don't see bug reports for those packages.
> Please file bugs so that we can track the status and decide when to start this
> transition based on the disruption that it will cause. Also please make those
> bugs block this one.
Dear release team,

we have two packages in new with versions that built against coin3 in
experimental:

https://ftp-master.debian.org/new/soqt_1.6.0~ea5cd76+ds1-1~exp1.html
https://ftp-master.debian.org/new/pivy_0.6.4-1~exp1.html

both are the version more problematic and FTBFS without these new
versions. Please, could you push coin3 to unstable to initiate the
transition to make all this versions be built?

freecad needs both. We have built freecad with both and works perfectly.

Best regards,

Leopold


-- 
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Bug#916650: stretch-pu: package liquidsoap/1.1.1-7.2

[Kyle Robbertze]

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

The current liquidsoap package in stable segfaults imediately on run.
Details are in bug #812591. The segfault is due to Ocaml version 4.02
which is present in stable. The fix upstream has been applied here
(sourced from Ubuntu where it has been working since 17.10). It is part
of the version currently in buster and unstable.

I have tested it within a stable chroot (install and execution of simple
scripts).

Please accept the attached patch if possible. I have someone willing to
sponsor the upload.

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_ZA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru liquidsoap-1.1.1/debian/changelog liquidsoap-1.1.1/debian/changelog
--- liquidsoap-1.1.1/debian/changelog   2016-11-29 21:37:34.0 +
+++ liquidsoap-1.1.1/debian/changelog   2018-12-01 18:41:23.0 +
@@ -1,3 +1,9 @@
+liquidsoap (1.1.1-7.2+deb9u1) stretch; urgency=medium
+
+  * Fix compilation with Ocaml 4.02 (Closes: #812591)
+  * Added new uploader
+
+ -- Kyle Robbertze   Sat, 01 Dec 2018 20:41:23 +0200
+
 liquidsoap (1.1.1-7.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru liquidsoap-1.1.1/debian/control liquidsoap-1.1.1/debian/control
--- liquidsoap-1.1.1/debian/control 2016-11-29 21:35:41.0 +
+++ liquidsoap-1.1.1/debian/control 2018-12-01 18:38:23.0 +
@@ -3,6 +3,7 @@
 Priority: optional
 Maintainer: Debian OCaml Maintainers 
 Uploaders:
+ Kyle Robbertze ,
  Romain Beauxis ,
  Samuel Mimram 
 Build-Depends:
diff -Nru liquidsoap-1.1.1/debian/files liquidsoap-1.1.1/debian/files
--- liquidsoap-1.1.1/debian/files   2016-11-29 21:37:34.0 +
+++ liquidsoap-1.1.1/debian/files   1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-liquidsoap_1.1.1-7.2_source.buildinfo sound optional
diff -Nru 
liquidsoap-1.1.1/debian/patches/bf0640779b2e7095e01755d3660c7e3f0865171d.patch 
liquidsoap-1.1.1/debian/patches/bf0640779b2e7095e01755d3660c7e3f0865171d.patch
--- 
liquidsoap-1.1.1/debian/patches/bf0640779b2e7095e01755d3660c7e3f0865171d.patch  
1970-01-01 00:00:00.0 +
+++ 
liquidsoap-1.1.1/debian/patches/bf0640779b2e7095e01755d3660c7e3f0865171d.patch  
2018-12-01 18:37:32.0 +
@@ -0,0 +1,456 @@
+From bf0640779b2e7095e01755d3660c7e3f0865171d Mon Sep 17 00:00:00 2001
+From: Romain Beauxis 
+Date: Thu, 14 May 2015 14:38:40 -0500
+Subject: [PATCH] More stuff to compile with 3.12.1 -> 4.03.0
+
+---
+ src/Makefile |  2 +-
+ src/decoder/decoder.ml   |  6 +--
+ src/decoder/image_decoder.ml |  2 +-
+ src/decoder/ogg_decoder.ml   |  2 +-
+ src/encoder/encoder.ml   |  2 +-
+ src/encoder/taglib_id3v2.ml  |  2 +-
+ src/lang/lang_builtins.ml|  8 ++--
+ src/lang/lang_encoders.ml| 86 
+ src/lang/lang_pp.ml  |  2 +-
+ src/lang/lang_types.ml   |  2 +-
+ src/operators/frei0r_op.ml   |  2 +-
+ src/operators/setvol.ml  |  2 +-
+ src/outputs/harbor_output.camlp4 |  2 +-
+ src/outputs/harbor_output.ml |  6 +--
+ src/outputs/icecast2.ml  |  2 +-
+ src/playlists/playlist_basic.ml  |  2 +-
+ src/protocols/mpd.ml |  2 +-
+ src/request.ml   |  2 +-
+ src/stream/frame.ml  |  2 +-
+ src/tools/harbor.camlp4  | 12 +++---
+ src/tools/harbor.ml  | 17 +---
+ src/tools/http.ml|  8 ++--
+ src/tools/plug.ml|  4 +-
+ src/tools/utils.ml   | 60 ++--
+ 24 files changed, 147 insertions(+), 90 deletions(-)
+
+Index: liquidsoap-1.1.1/src/Makefile
+===
+--- liquidsoap-1.1.1.orig/src/Makefile
 liquidsoap-1.1.1/src/Makefile
+@@ -173,7 +173,7 @@ $(call conditional_compilation,io,$(W_OS
+ $(call conditional_compilation,io,$(W_PULSEAUDIO),io/pulseaudio_io.ml)
+ $(call conditional_compilation,io,$(W_PORTAUDIO),io/portaudio_io.ml)
+ 
+-tools = tools/stdlib.ml tools/doc.ml tools/plug.ml tools/utils.ml \
++tools = tools/stdlib.ml tools/doc.ml tools/utils.ml tools/plug.ml \
+   $(if $(W_DYNLINK),tools/dyntools.ml) \
+   tools/rqueue.ml \
+   $(if $(W_LAME_DYN),tools/lame_dynlink.ml) \
+Index: liquidsoap-1.1.1/src/decoder/decoder.ml
+===
+--- liquidsoap-1.1.1.orig/src/decoder/decoder.ml
 liquidsoap-1.1.1/src/decoder/decoder.ml
+@@ -277,7 +277,7 @@ let get_image_file_decoder filename =
+   with
+   | Pervasives.Exit -> 

Bug#887371: nemo: crash/segfault whilst manipulating files in a folder

[N G]

Package: nemo
Version: 3.2.2-3
Followup-For: Bug #887371

Hello there,

I've been experiencing something similar since I installed debian stretch early
this year. If I drag and drop, copy, cut and/or paste a few times several files
(in this case from 50/500 or more jpg/png/gif/webm files).

I am able to reproduce this bug anytime, by moving several images (or any other
file with a thumbnail) from folder to folder, each folder with several files as
well, after moving several times a random number of files, it'll crash when
visiting different folders.
But I don't know how to trace further information like a log or something with
more info about the crash.
If somebody can point me how to get more info, I can reproduce it again,
thanks.

I only have this journald message
dic 16 16:40:22 phoenix kernel: nemo[1815]: segfault at ee10130254 ip
7f3902c0e23b sp 7fff907aa5f0 error 4 in
libgtk-3.so.0.2200.11[7f3902889000+70]
dic 16 16:40:22 phoenix kernel: Code: 83 c4 08 5b 5d c3 66 0f 1f 84 00 00 00 00
00 55 53 48 89 fb 48 83 ec 08 e8 e2 75 ff ff 48 85 db 74 1c 48 8b 13 48 85 d2
74 05 <48> 3b 02 74 30 48 89 c6 48 89 df e8 f5 16 d0 ff 85 c0 75 21 48 83









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

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

Versions of packages nemo depends on:
ii  desktop-file-utils 0.23-1
ii  gsettings-desktop-schemas  3.22.0-1
ii  gvfs   1.30.4-1
ii  libatk1.0-02.22.0-1
ii  libc6  2.24-11+deb9u3
ii  libcairo-gobject2  1.14.8-1
ii  libcairo2  1.14.8-1
ii  libcinnamon-desktop4   3.2.4-4
ii  libexempi3 2.4.1-1
ii  libexif12  0.6.21-2+b2
ii  libgail-3-03.22.11-1
ii  libgdk-pixbuf2.0-0 2.36.5-2+deb9u2
ii  libglib2.0-0   2.50.3-2
ii  libglib2.0-data2.50.3-2
ii  libgtk-3-0 3.22.11-1
ii  libnemo-extension1 3.2.2-3
ii  libnotify4 0.7.7-2
ii  libpango-1.0-0 1.40.5-1
ii  libpangocairo-1.0-01.40.5-1
ii  libx11-6   2:1.6.4-3+deb9u1
ii  libxml22.9.4+dfsg1-2.2+deb9u2
ii  nemo-data  3.2.2-3
ii  shared-mime-info   1.8-1+deb9u1

Versions of packages nemo recommends:
ii  cinnamon-l10n3.2.2-2
ii  gvfs-backends1.30.4-1
ii  gvfs-fuse1.30.4-1
ii  librsvg2-common  2.40.16-1+b1
ii  nemo-fileroller  3.2.1-2

Versions of packages nemo suggests:
pn  eog  
ii  evince [pdf-viewer]  3.22.1-3+deb9u1
ii  totem3.22.1-1
ii  xdg-user-dirs0.15-2+b1

-- no debconf information

Bug#868563: apparmor-profiles: Apparmor profiles for postfix programs have incorrect path

[intrigeri]

Hi,

Julian Andres Klode:
> It needs some more changes, I'll try to get them fixed up
> this weekend, so I can roll out my server in enforced mode.

Did your https://gitlab.com/apparmor/apparmor/merge_requests/284 fix
all the incorrect paths this bug was about?

(I'd like to update this bug's metadata accordingly :)

Cheers,
-- 
intrigeri

Bug#704005: git cvsimport: reads /tmp/.gitattributes

[Jonathan Nieder]

Hi Helmut,

In April, 2013, Helmut Grohne wrote:

> I verified that the attached patch solves this particular issue.
>
> Helmut

> Description: Avoid reading /tmp/.gitattributes
> Author: Helmut Grohne
> Last-Update: 2013-04-03
> Bug-Debian: http://bugs.debian.org/704005
>
> git-cvsimport invokes git-hash-object in a way that causes it to read
> /tmp/.gitattributes. This patch avoids the behaviour by passing --no-filters 
> to
> git-hash-object. An alternative approach would be to put create a temporary
> directory call git-hash-object on files withing that private directory.
>
> --- git-cvsimport.orig2013-04-03 09:53:47.0 +0200
> +++ git-cvsimport 2013-04-03 09:51:20.0 +0200
> @@ -1030,7 +1030,7 @@
>   my $pid = open(my $F, '-|');
>   die $! unless defined $pid;
>   if (!$pid) {
> - exec("git", "hash-object", "-w", $tmpname)
> + exec("git", "hash-object", "--no-filters", "-w", 
> $tmpname)
>   or die "Cannot create object: $!\n";
>   }
>   my $sha = <$F>;

Sorry for the very long silence.  May I forge your sign-off when passing
this upstream?  See
https://www.kernel.org/pub/software/scm/git/docs/SubmittingPatches.html#sign-off
for more details about what this means.

Sincerely,
Jonathan

Bug#915046: [debian-mysql] Bug#915046: mariadb-10.3: Please build with -latomic where necessary

[John Paul Adrian Glaubitz]

On 12/16/18 10:07 PM, Otto Kekäläinen wrote:
>>> We already have 21 patches and maintaining them year after year has
>>> its price, so I am more strict nowadays on making sure all patches are
>>> also on their way to upstream.
>> Well, it's a trivial bug and it fixes an FTBFS on release architectures :).
> 
> It looks like the libmysqld/CMakeLists.txt section does not apply.
> What did you rebase this on? How should this be corrected?

That's odd. I rebased it against the latest mariadb-10.3 package in
experimental, i.e. version 1:10.3.11-1~exp1.

> WIP at 
> https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/c3bc7ec9634f8601a860602ccc6237630bda77ca

Ok, I'll open a pull request in salsa.

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#916621: [Python-modules-team] Bug#916621: djangorestframework’s mkdocs theme is incompatible with mkdocs 1.0

[Dmitry Shachnev]

Hi Brian!

On Mon, Dec 17, 2018 at 08:05:06AM +1100, Brian May wrote:
> > Will you mind if I update the packaging and change the theme from custom
> > to default?
> >
> > That will also give me the ability to symlink the JS/CSS/fonts files to
> > the packaged versions (the custom theme uses Bootstrap 2 which is removed
> > from Debian, the default theme uses Bootstrap 3 and will use Bootstrap 4
> > in the next release).
>
> All this seems fine with me.

Thanks for the quick response!

I will do a team upload once the other related packages are ready.

By the way I have written a helper tool, dh_mkdocs, which takes care of
symlinking static files and removing external references, so I will use it
here.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#870697: Please provide systemd service file which doesn't require the SysV init script

[intrigeri]

intrigeri:
> My initial draft seems to be working fine at first glance:

Updated my already outdated upstream MR (merge conflicts: my MR
prompted other upstream folks to take a look at the affected file… and
themselves submit a bunch of other MRs to remove obsolete bits :)
+ pinged those I'd like a review from.

Now, if these reviews take too long I'll do whatever it takes to get
this into Buster.

Bug#916639: LXC AppArmor confinement breaks systemd v240

[intrigeri]

Michael Biebl:
> Fwiw, I agree with your assessment here.

Thanks for your input.

> That said, I guess #911806 could be closed now (with #916639 and #916644
> having been filed, thanks for that btw).

I'm hereby closing it, then. I only kept it open in case _you_ still
saw value in your original request ("provide a way to opt out of
AppArmor confinement when running tests"). The 2 bug reports I've
filed today are on our radar via usertags already.

Cheers,
-- 
intrigeri

Bug#916649: crytpsetup:

[rsev]

Package: cryptsetup
Version: 2:1.7.3-4
Severity: normal

Dear Maintainer,

When shuting down my Devuan LVM + LUKS install, it hangs just at the end
of the shutdown sequence presenting messages like "sda5_crypt is busy"
and "sdb_crypt is busy". Only after 30 seconds or so pass, it acatully
shuts down.

Aplying one the patchs available at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792552#5 or
https://bugs.devuan.org//cgi/bugreport.cgi?bug=237 fixes the problems
just fine for me.


Regards,

Rodrigo


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.18.0-0.bpo.1-amd64 root=/dev/mapper/cinza--vg-root
ro quiet

-- /etc/crypttab
sda5_crypt UUID=70c51778-8972-4ccd-b554-3377e25087a3 none luks
sdb_crypt UUID=42730e90-3b0c-4c8e-a8de-ade923baddb6
/root/.sdb_crypt.keyfile luks


-- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name
devices
# that works even if disks are added and removed. See fstab(5).
#
#
/dev/mapper/cinza--vg-root /   ext4errors=remount-ro 0  
1
# /boot was on /dev/sda1 during installation
UUID=18c90b2d-2409-4717-8ecf-c39f2d3c3484 /boot   ext2   
defaults0   2
/dev/mapper/cinza--vg-home /home   ext4defaults0
  2
/dev/mapper/cinza--vg-tmp /tmpext4defaults0 
 2
/dev/mapper/cinza--vg-var /varext4defaults0 
 2
/dev/mapper/cinza--vg-swap_1 noneswapsw  0  
0
/dev/vg2/vm /vm ext4 defaults 0 2


-- lsmod
Module  Size  Used by
ctr16384  2
ccm20480  3
appletalk  40960  0
psnap  16384  1 appletalk
llc16384  1 psnap
ax25   65536  0
cmac   16384  1
bnep   24576  2
cpufreq_conservative16384  0
cpufreq_userspace  16384  0
cpufreq_powersave  16384  0
bbswitch   16384  0
snd_hda_codec_realtek   110592  1
snd_hda_codec_generic86016  1 snd_hda_codec_realtek
arc4   16384  2
intel_rapl 24576  0
x86_pkg_temp_thermal16384  0
intel_powerclamp   16384  0
iwldvm159744  0
btusb  53248  0
coretemp   16384  0
btrtl  16384  1 btusb
btbcm  16384  1 btusb
kvm_intel 237568  0
btintel24576  1 btusb
mac80211  827392  1 iwldvm
i915 1732608  5
bluetooth 630784  26 btrtl,btintel,btbcm,bnep,btusb
kvm   733184  1 kvm_intel
uvcvideo  114688  0
videobuf2_vmalloc  16384  1 uvcvideo
videobuf2_memops   16384  1 videobuf2_vmalloc
iwlwifi   229376  1 iwldvm
snd_hda_intel  45056  3
videobuf2_v4l2 28672  1 uvcvideo
irqbypass  16384  1 kvm
drbg   28672  1
videobuf2_common   49152  2 videobuf2_v4l2,uvcvideo
asus_nb_wmi28672  0
snd_hda_codec 151552  3
snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_realtek
asus_wmi   32768  1 asus_nb_wmi
iTCO_wdt   16384  0
ansi_cprng 16384  0
videodev  217088  3 videobuf2_v4l2,uvcvideo,videobuf2_common
intel_cstate   16384  0
iTCO_vendor_support16384  1 iTCO_wdt
sparse_keymap  16384  1 asus_wmi
wmi_bmof   16384  0
mxm_wmi16384  0
snd_hda_core   94208  4
snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
intel_uncore  135168  0
media  45056  2 videodev,uvcvideo
drm_kms_helper196608  1 i915
ecdh_generic   24576  2 bluetooth
snd_hwdep  20480  1 snd_hda_codec
joydev 24576  0
cfg80211  782336  3 iwldvm,iwlwifi,mac80211
intel_rapl_perf16384  0
snd_pcm   118784  3 snd_hda_intel,snd_hda_codec,snd_hda_core
evdev  28672  15
snd_timer  36864  1 snd_pcm
drm   475136  6 drm_kms_helper,i915
pcspkr 16384  0
serio_raw  16384  0
snd98304  13
snd_hda_codec_generic,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
rfkill 28672  5 asus_wmi,bluetooth,cfg80211
soundcore  16384  1 snd
mei_me 45056  0
i2c_algo_bit   16384  1 i915
acpi_als   16384  0
mei   110592  1 mei_me
lpc_ich28672  0
kfifo_buf  16384  1 acpi_als
wmi28672  3 asus_wmi,wmi_bmof,mxm_wmi
battery24576  0
industrialio   81920  2 acpi_als,kfifo_buf
video  45056  2 asus_wmi,i915
button 16384  1 i915
asus_wireless  16384  0
ac 16384  0

Bug#916640: Changes to GAP necessary for sagemath

[Bill Allombert]

On Sun, Dec 16, 2018 at 08:25:17PM +0100, Tobias Hansen wrote:
> Package: src:gap
> Version: 4r10p0-2
> Severity: wishlist
> Tags: sid buster patch
> Control: block 912980 by -1
> 
> Hi Bill,
> 
> the sagemath developers managed to get sagemath to work with gap 4.10
> [1], however they require some changes to GAP. I'm filing this bug in
> order to discuss how we can get a gap in Debian before the buster
> freeze that works with sagemath. I updated the sagemath package in git
> and it works fine when I apply the attached patch to gap. This debdiff
> applies three patches and installs libgap to /usr/lib/triplet, so that
> it can be found.

Hello Tobias,

As you see, I still did not manage to get GAP 4.9 in testing...

Do you not also need some kind of symbol mangling to avoid conflicts with
other Sage component ?

The Sage patches change the interface to the library. However it seems
likely libgap in Debian will only be used by Sagemath in Buster, so
maybe we could arrange for those patches to be applied only to libgap
and not to /usr/bin/gap. However the side effect is that each time you
will need to update those extra patches, I will need to reupload gap.

So there might be benefits to have a separate source package.

On the other hand, if we decide against a separate source package,
then we need to get 4.10 updated as soon as possible at least in
experimental.

Does that answer your questions ?

> +  * Install libgap to /usr/lib/triplet.

Do you need this now ? When the interface to libgap has stabilized, then
probably we will split libgap from gap-dev and move it to
/usr/lib/triplet, but as long as it is an experimental feature it is
best to keep it in a subdirectory.

> +From: "Erik M. Bray" 
> +Date: Tue, 4 Dec 2018 12:44:23 +
> +Subject: [PATCH 1/3] a version of the writeandcheck.patch from Sage that 
> works
> + against 4.10

This patch looks extremly fragile. This is likely to break /usr/bin/gap.

> diff -Nru 
> gap-4r10p0/debian/patches/0002-kernel-add-helper-function-for-writing-error-message.patch
>  
> gap-4r10p0/debian/patches/0002-kernel-add-helper-function-for-writing-error-message.patch
> --- 
> gap-4r10p0/debian/patches/0002-kernel-add-helper-function-for-writing-error-message.patch
>  1970-01-01 01:00:00.0 +0100
> +++ 
> gap-4r10p0/debian/patches/0002-kernel-add-helper-function-for-writing-error-message.patch
>  2018-12-07 16:20:43.0 +0100
> @@ -0,0 +1,122 @@
> +From 0cecb79ff97c73a24acacf8afdc3edba93507661 Mon Sep 17 00:00:00 2001
> +From: "Erik M. Bray" 
> +Date: Thu, 22 Nov 2018 10:53:31 +0100
> +Subject: [PATCH 2/3] kernel: add helper function for writing error messages 
> to
> + the file/stream referenced by the ERROR_OUTPUT global variable

This one changes the interface to the library.

> +From: "Erik M. Bray" 
> +Date: Thu, 6 Dec 2018 16:11:35 +
> +Subject: [PATCH 3/3] Prototype for GAP_Enter/Leave macros to bracket use of
> + libgap and stack local GAP objects in code which embeds libgap

This one also changes the interface to the library.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#887601: libcamlimages-ocaml: Detect freetype using pkg-config

[Kyle Robbertze]

Control: tags -1 + pending

On 2018/12/11 13:40, Hideki Yamane wrote:
> Hi,
> 
> On Thu, 18 Jan 2018 11:19:18 + Hugh McMaster  
> wrote:
>> Package: libcamlimages-ocaml
>> Version: 1:4.2.0-1.1+b3
>> Severity: important
>>
>> Dear Maintainer,
>>
>> The next version of libfreetype6-dev will *not* ship the 'freetype-config'
>> script.
>>
>> Please use pkg-config to detect the freetype headers and libraries instead.
> 
>  I've prepared patches (and more update) at
>  https://salsa.debian.org/ocaml-team/camlimages/merge_requests/2
> 
>  I'm not sure why but I cannot detect freetype header files with
>  Check_header_library, so just specified pkg-config checks returns
>  "true".
> 
>  Anyway, please check it.

Merged, and it will be included in the next upload when I have finished
working on the new upstream version.

Cheers
Kyle




signature.asc
Description: OpenPGP digital signature

Bug#916621: [Python-modules-team] Bug#916621: djangorestframework’s mkdocs theme is incompatible with mkdocs 1.0

[Brian May]

Dmitry Shachnev  writes:

> Upstream seems to have no interest in porting the theme to newer mkdocs
> versions. They just depend on mkdocs 0.16 for now.

Unfortunate :-(

> Will you mind if I update the packaging and change the theme from custom
> to default?
>
> That will also give me the ability to symlink the JS/CSS/fonts files to
> the packaged versions (the custom theme uses Bootstrap 2 which is removed
> from Debian, the default theme uses Bootstrap 3 and will use Bootstrap 4
> in the next release).

All this seems fine with me.

Thanks!
-- 
Brian May 

Bug#916614: mkdocs-bootswatch: Incompatible with mkdocs 0.17

[Brian May]

Dmitry Shachnev  writes:

> Please either upgrade this package or request its removal. It has no reverse
> dependencies, so the latter should be possible.

The only reason this was packaged, was because once upon a time mkdocs
required it.

If it is not needed anymore, and nobody has the time to maintain it,
might be best to remove it.
-- 
Brian May 

Bug#884243: djmount status, two patches and about conversion to libupnp 1.8

[Uwe Kleine-König]

Hello,

On Wed, May 23, 2018 at 05:31:08PM +0200, Dario Minnucci wrote:
> Sorry for the delay and thanks to invest time on this issue.
> 
> On 18/05/18 23:30, Uwe Kleine-König wrote:
> > Hello Dario,
> > 
> > On Tue, Jan 09, 2018 at 09:17:35PM +0100, Rémi wrote:
> > > you are right, I have not been active on djmount for quite some time now.
> > > I tried to find a volonteer to maintain it at the time, but it didn't
> > > happen.
> > > 
> > > I am sorry I don't have the right setup to validate these patches :-/
> > > So removing should be considered, unless a maintainer can be found.
> > 
> > What is your POV on this? Is djmount worth fixing, or should we remove
> > it? If the former, can you give test feedback on the patches I already
> > sent?
> > 
> 
> 
> I need to setup an environment to include libupnp10 (upnp 1.8) and
> implement provided patches.
> 
> I lack of free time right now, but will engage on this as soon as I
> can.
> 
> Again sorry for the delay.

The current situation is that djmount is the last package that is using
libupnp6. (Well, there is still linux-igd, but this is about to be
removed -> #916643)

djmount was already removed from testing. I wonder if we should also
remove it from unstable given that there happened nothing to make
djmount build with libupnp-1.8 for a year.

Best regards
Uwe


signature.asc
Description: PGP signature

Bug#916344: chromium not available anymore on testing

[Gregor Riepl]

chromium from unstable is also not installable on testing due to a dependency
on glibc-2.28 - there seems to be an ongoing transition.

Will this package be added back to testing before the soft freeze for buster
starts on January 12?

I see that there are a number of RC bugs and build errors on several
architectures. Does the Chromium team need help with fixing them?

Bug#915046: [debian-mysql] Bug#915046: mariadb-10.3: Please build with -latomic where necessary

[Otto Kekäläinen]

su 16. jouluk. 2018 klo 22.10 John Paul Adrian Glaubitz
(glaub...@physik.fu-berlin.de) kirjoitti:
>
> On 12/16/18 9:04 PM, Otto Kekäläinen wrote:
> > Can you please provide a link to where you upstreamed it?
>
> It's in the "Forwarded" field of this bug report. It's pointing to:
>
> > https://github.com/MariaDB/server/pull/979

Right. I added it into the patch itself now so that it is easy to track.

> > We already have 21 patches and maintaining them year after year has
> > its price, so I am more strict nowadays on making sure all patches are
> > also on their way to upstream.
> Well, it's a trivial bug and it fixes an FTBFS on release architectures :).

It looks like the libmysqld/CMakeLists.txt section does not apply.
What did you rebase this on? How should this be corrected?

WIP at 
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/c3bc7ec9634f8601a860602ccc6237630bda77ca

Bug#916648: rinetd: logrotate exits with error after package removal

[Andreas Beckmann]

Package: rinetd
Version: 0.62.1sam-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package's logrotate
configuration causes logrotate to exit with an error after
the package has been removed.

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

0m30.0s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts/tmp/tmpjsNx7n', '/usr/sbin/logrotate', '/etc/logrotate.d/rinetd']
  error: stat of /var/log/rinetd.log failed: No such file or directory


cheers,

Andreas

Bug#916513: bug 916513 invalid

[contact smxi]

You can close this bug because it is invalid. The bug poster neglected to read either the help 
options or the man page, where it clearly states:


 -f, --flags  All CPU flags. Triggers -C. Not shown with -F to avoid spamming.

Note that the help text could be a bit more clear for -Cx in terms of flags, I'll add the (short 
list) to it..


The man text is clear:

-x -C  - Adds bogomips on CPU (if available)
- Adds CPU Flags (short list).

Default -Cx behavior is to show only a subset of flags, which used to be more a more relevant 
feature, for example, it will show flags that matter for default cases, like pae.


In general before stating that something is missing, bug posters should read the manual to make sure 
they are right.

Bug#916647: net-acct: logrotate exits with error after package removal

[Andreas Beckmann]

Package: net-acct
Version: 0.71-9
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package's logrotate
configuration causes logrotate to exit with an error after
the package has been removed.

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

0m32.3s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts/tmp/tmpqqProe', '/usr/sbin/logrotate', 
'/etc/logrotate.d/net-acct']
  error: stat of /var/log/net-acct/net-acct.log failed: No such file or 
directory
  error: stat of /var/log/net-acct/net-acct.debug failed: No such file or 
directory


cheers,

Andreas


net-acct_0.71-9+b2.log.gz
Description: application/gzip

Bug#916639: LXC AppArmor confinement breaks systemd v240

[Michael Biebl]

Am 16.12.18 um 20:22 schrieb intrig...@debian.org:
> If Buster is going to be released with LXC 3.0.x, IMO we need to
> either apply these patches or disable AppArmor by default for new LXC
> containers. 

Fwiw, I agree with your assessment here.
If we can't get AppArmor/LXC fixed in time for buster, then it's best to
disable AA-confinement for LXC completely and not just do it in debci
(as I suggested in #911806)

That said, I guess #911806 could be closed now (with #916639 and #916644
having been filed, thanks for that btw).
Unless you see value in keeping #911806 open (e.g. as tracking bug)

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#916582: parl-desktop depends on the removed xfce4-linelight-plugin

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, 2018-12-16 at 12:06 +0200, Adrian Bunk wrote:
> Package: parl-desktop
> Version: 1.9.16
> Severity: serious
> 
> The following packages have unmet dependencies:
>  parl-desktop : Depends: xfce4-linelight-plugin but it is not installable

Ouch, sorry for that. I've requested removal of linelight plugin recently
because it's unmaintained upstream and didn't see a release in ages (and I'm
doing some pre-freeze cleaning).

Somehow I managed to miss the dependency from parl-desktop.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlwWuYMACgkQ3rYcyPpX
RFuYXQgAsbJ64UkyvLQ+xqg6WAFPTmGF/hgHPskY66Pp3eEEct5o9mrt/lJ0IkTA
H8kc8nAm/aNtz13yM7ZNo7yEXBkI+JUiAtrQc1J2RYTJ3ehXR6r4nta7KO/sTe9I
13Bc/ctOYQHkwilfNeTqrcTXmnAEW/J48wyrecQ287MNMugT1Lq6cgRltoMSlIyM
KjMs3PQNqUtxkOsUkgSWOVmSGhIVAR6byQlvozb2CWOxHGutK2yAxRTRbAYRR+D6
cqQxhbhdlc2atONDVqs+Nh7CWdirrHgfNiLYMCG1eeJEGWZUknMUVQdQRkLdl3dF
+GyNeT/83Nj3+OVx4I3GdCeHPqR/zA==
=cTUI
-END PGP SIGNATURE-

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

[H. Elmann]

Hello Christian,

we are currently facing the same problem as described by Herbert at our 
institute. Manual configuration as described by you works. Of course, 
this hack will not survive a reboot. As a workaround, we wrote a custom 
start script which initializes the export. It works, but is still some 
kind of an awkward hack. Thus, a Debian compliant implementation would 
be a nice Christmas present for us tape library users ... :-)


Thanks in advance and kind regards,
H. Elmann.

Bug#904042: dovecot-sieve: Failed to initialize script execution: Invalid postmaster_address

[Marco Emilio Poleggi]

Hi there,

It doesn't work for me with v2.3.4-2 from testing. I see the logic:

  # doveconf -x postmaster_address
  postmaster_address = postmaster@%{if;%d;ne;;%d;%{hostname}}

but it doesn't expand to full address. Error is the same.

Cheers,

  Marco


On Sun, 25 Nov 2018 20:16:22 +0200 Apollon Oikonomopoulos 
wrote:
> Control: tags -1 + moreinfo upstream
> 
> Hi,
> 
> On 19:45 Wed 18 Jul , Graham Cobb wrote:
> > The problem appears to be that the default dovecot configuration 
> > (/etc/dovecot/conf.d/15-lda.conf)
> > allows the postmaster_address setting to default. The default value is 
> > postmaster@%d.
> > Unfortunately in some contexts the domain (%d) is not known and so the 
> > postmaster_address
> > ends up with the invalid value 'postmaster@'.
> 
> Thanks for the report! The default was changed in 2.3.4 to expand to 
> postmaster@ if %d is empty. Can you check if it works for you 
> so that I can close the bug?
> 
> Thanks,
> Apollon
> 
> 

-- 
**
#!·p·r·o·f·e·s·s·i·o·n·a·l·*·e·t·h·0·s
**
Marco Emilio Poleggi
10 Rue Cavour
1203 Genève
Suisse
**
 Tél. +41 79 697 71 91
www.professional-eth0s.com

Bug#905342: [pkg-apparmor] Bug#905342: apache fpm not working anymore

[intrigeri]

Hi,

intrigeri:
> Ivan Sergio Borgonovo:
>> As you said probably apparmor seems not to be the culprit.

>> Nov 04 20:21:13 kerberos audit[1280]: AVC apparmor="DENIED" 
>> operation="mount" info="failed type match" error=-13 
>> profile="lxc-container-default-cgns" name="/sys/fs/cgroup/unified/" pid=1280 
>> comm="systemd" fstype="cgroup2" srcname="cgroup2" flags="rw, nosuid, nodev, 
>> noexec"

> This one looks like a bug in the LXC AppArmor profiles, please report
> it against the lxc package.


> [...]
> … and many more processes confined under the
> lxc-container-default-cgns profile.

> Are you actually running dovecot, tor, postgres, sshd, smdb, Postfix,
> dhclient etc. in LXC containers? Or is the lxc-container-default-cgns
> profile somehow erroneously applied to these processes?

Gentle ping on this?

Cheers,
-- 
intrigeri

Bug#916646: perl6-zef: fails to remove: No such file or directory at /usr/share/perl6/rakudo-helper.pl line 70.

[Andreas Beckmann]

Package: perl6-zef
Version: 0.5.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + perl6

Hi,

during a test with piuparts I noticed your package fails to remove.

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

[...]
  Removing perl6 (6.d-1) ...
  Removing perl6-zef (0.5.3-1) ...
  could not open file in removal of module perl6-zef: No such file or directory 
at /usr/share/perl6/rakudo-helper.pl line 70.
  dpkg: error processing package perl6-zef (--remove):
   installed perl6-zef package post-removal script subprocess returned error 
exit status 2
  Removing curl (7.62.0-1) ...
  Removing libcurl4:amd64 (7.62.0-1) ...
  Removing perl6-tap-harness (0.20180925-1) ...
  could not open file in removal of module perl6-tap-harness: No such file or 
directory at /usr/share/perl6/rakudo-helper.pl line 70.
  dpkg: error processing package perl6-tap-harness (--remove):
   installed perl6-tap-harness package post-removal script subprocess returned 
error exit status 2
  Removing rakudo (2018.11-1) ...
  dpkg: warning: while removing rakudo, directory '/usr/lib/perl6/vendor' not 
empty so not removed
[...]


Please reassign if I did not select the correct package.


cheers,

Andreas


perl6_6.d-1.log.gz
Description: application/gzip

Bug#916645: ITP: lablgtk3 -- OCaml bindings for gtk+ version 3

[Ralf Treinen]

Package: wnpp
Severity: wishlist
Owner: Ralf Treinen 

* Package name: lablgtk3
  Version : 3.0
  Upstream Author : Jacques Garrigue 
* URL : http://lablgtk.forge.ocamlcore.org/
* License : LGPL 2.1
  Programming Lang: OCaml
  Description : OCaml bindings for gtk+ version 3

This package provides OCaml bindings (development libraries,
dynamic libraries) for gtk+ version3.

This package is needed to bring back the graphical interface to
some important OCaml applications, in particular coq, why3, alt-ergo,
and frama-c

It will be maintained by the Debian OCaml team.

Bug#915046: [debian-mysql] Bug#915046: mariadb-10.3: Please build with -latomic where necessary

[John Paul Adrian Glaubitz]

On 12/16/18 9:04 PM, Otto Kekäläinen wrote:
> Can you please provide a link to where you upstreamed it?

It's in the "Forwarded" field of this bug report. It's pointing to:

> https://github.com/MariaDB/server/pull/979

> We already have 21 patches and maintaining them year after year has
> its price, so I am more strict nowadays on making sure all patches are
> also on their way to upstream.
Well, it's a trivial bug and it fixes an FTBFS on release architectures :).

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#915046: [debian-mysql] Bug#915046: mariadb-10.3: Please build with -latomic where necessary

[Otto Kekäläinen]

> Attaching an updated version of the patch.
>
> Please note, without the patch, mariadb-10.3 will not build on mips32 and
> several other 32-bit platforms.

Thanks!

Can you please provide a link to where you upstreamed it?

We already have 21 patches and maintaining them year after year has
its price, so I am more strict nowadays on making sure all patches are
also on their way to upstream.

Bug#887552: tox: new version available upstream

[Faidon Liambotis]

On Wed, Jan 17, 2018 at 03:06:34PM -0500, Jeff Cliff wrote:
> https://github.com/tox-dev/tox/releases
> if that is accurate, the version in debian dates from Nov 16, 2016, 11 
> releases ago.

Upstream is now at 3.5.0, and that's even a couple months old now. This
package hasn't seen an upload for 2 years now despite an active
upstream, and looks abandoned. Maybe it should be orphaned?

I'd start a salvaging process[1], but I don't think I have the time to
take care of it on a permanent basis. Would be happy to help and/or
sponsor someone that would feel like doing that, however!

Regards,
Faidon

1: 
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging

Bug#911806: Please provide a way to opt out of AppArmor confinement when running tests

[intrigeri]

> 1. Ask the src:lxc maintainers to apply these 3 upstream patches
>until they upgrade the package to 3.1.0+.

#916639

> 2. Ask the debci maintainers to use the config described above
>for LXC containers used to run autopkgtests, once they upgrade
>to Buster.

#916644

Bug#916636: ODP: Bug#916636: RFS: smplayer-themes/1:18.6.0-1

[Michał Giza]

Gratulacje 






Od: Mateusz Łukasik 
Wysłane: Sunday, December 16, 2018 7:53:02 PM
Do: debian-bts
Temat: Bug#916636: RFS: smplayer-themes/1:18.6.0-1

Package: sponsorship-requests
Severity: normal

   Dear mentors,

   I am looking for a sponsor for my package "smplayer-themes"

  * Package name: smplayer-themes
Version : 1:18.6.0-1
Upstream Author : Ricardo Villalba 
  * URL : http://smplayer.sf.net
  * License : GPL-2.0+
Section : video

   It builds those binary packages:

 smplayer-themes - complete front-end for MPlayer - icon themes

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

   https://mentors.debian.net/package/smplayer-themes

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

 dget -x
https://mentors.debian.net/debian/pool/main/s/smplayer-themes/smplayer-themes_18.6.0-1.dsc

   Changes since the last upload:
   [ Alf Gaida ]
   * New upstream release 18.6.0.
   * Added myself to uploaders.
   * Bumped compat to 11
   * Bumped debhelpers to >= 11.
   * Bumped Standards-Version to 4.2.1, no changes needed.
   * Added lintian-overrides for theme descriptions
   * Fixed debian/copyright
   * Added debian/upstream/metadata

   [ Mateusz Łukasik ]
   * Fix debian/gbp.conf.

   Regards,
Mateusz Łukasik

Bug#916644: Adjust LXC containers' AppArmor configuration once ci.debian.net runs Buster

[intrigeri]

Source: debci
Severity: wishlist

Hi,

Once ci.debian.net runs Buster, to avoid AppArmor breaking
autopkgtests such as the systemd ones, the LXC containers will need
this config:

  lxc.apparmor.profile = generated
  lxc.apparmor.allow_nesting = 1

This is assuming LXC is fixed in Buster with the patches I've provided
on #916639.

Context: https://bugs.debian.org/911806

Cheers,
-- 
intrigeri

Bug#916643: RM: linux-igd -- RoQA; orphaned, ftbfs

[Uwe Kleine-König]

Package: ftp.debian.org
Severity: normal

linux-igd is orphaned: https://bugs.debian.org/857247

and currently fails to build from source since the libupnp transition:
https://bugs.debian.org/912066

When linux-igd is removed this is a step forward to also remove libupnp
from sid.

Best regards
Uwe

Bug#916140: python3-matplotlib-dbg: missing Breaks+Replaces: python-matplotlib-dbg (<< 3)

[Sandro Tosi]

Hey Andreas,

On Mon, Dec 10, 2018 at 12:57 PM Andreas Beckmann  wrote:
>
> Control: retitle -1 python3-matplotlib-dbg: missing Breaks+Replaces: 
> python-matplotlib-dbg (<< 2.2.3-3)
>
> On 2018-12-10 17:47, Sandro Tosi wrote:
> > On Mon, Dec 10, 2018 at 11:06 AM Andreas Beckmann  wrote:
> >  is this right approach? there is a new src:matplotlib2 in experimetal
> > NEW to drop py3k packages (so src:matplotlib2 will only ship python2
> > and src:matplotlib will only ship py3k package), so that should remove
> > the incompatibility?
>
> This will probably not change anything, but lets see what happens once
> they clear new.

src:matplotlib2 (producing python-matplotlib*) has been accepted into
experimental - mind giving this another try? thanks!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#916642: Long list of binNMUs for golang packages

[Dr. Tobias Quathamer]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal

Dear release team,

in order to get rid of older copies of golang-1.10 and earlier, I'd like
to ask for several binNMUs. The binaries produced by golang are statically
linked, so that we have quite a few older versions in the archive, due
to Built-Using and Extra-Source-Only. Please find below the packages
which would need a rebuild with the current golang-1.10 version.

If this list is too long, I'd like to ask for binNMUs for really old
golang compiler versions. That list would be shorter, please tell me
if you'd like that list instead.

Regards,
Tobias


  nmu abci_0.0~git20170124.0.f94ae5e-2 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu acbuild_0.4.0+dfsg-3 . ANY . -m 'Rebuild with current golang-1.10'
  nmu ace_0.0.5-3 . ANY . -m 'Rebuild with current golang-1.10'
  nmu acmetool_0.0.62-3 . ANY . -m 'Rebuild with current golang-1.10'
  nmu amber_0.0~git20171010.cdade1c-1 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu appc-spec_0.8.11+dfsg-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu aptly_1.3.0+ds1-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu aptly-api_1.3.0+ds1-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu arduino-builder_1.3.25-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu autodeb-server_0.20.0-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu autodeb-worker_0.20.0-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu burrow_1.1.0-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu cadvisor_0.27.1+dfsg2-4 . ANY . -m 'Rebuild with current golang-1.10'
  nmu canid_0.0~git20180613.007c9af-2 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu certspotter_0.9-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu chasquid_0.06-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu chroma_0.5.0-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu cli-spinner_0.0~git20150423.610063b-4 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu cobra_0.0.3-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu codesearch_0.0~hg20120502-3 . ANY . -m 'Rebuild with current golang-1.10'
  nmu consul_1.0.7~dfsg1-5 . ANY . -m 'Rebuild with current golang-1.10'
  nmu consulfs_0.2-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu continuity_0.0~git20180216.d8fb858-1 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu coyim_0.3.8+ds-5 . ANY . -m 'Rebuild with current golang-1.10'
  nmu debiman_0.0~git20180905.9955035-1 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu debos_1.0.0+git20181105.b02e058-1 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu dh-make-golang_0.0~git20180827.d94f0cb-1 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu dnscrypt-proxy_2.0.19+ds1-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu dnss_0.0~git20180721.0.2de63ab0-1 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu docker2aci_0.17.2+dfsg-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu docker.io_18.06.1+dfsg1-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu docker-registry_2.6.2~ds1-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu ebnflint_0.0~git20181112.a3060d4-1 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu elvish_0.12+ds1-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu etcd-client_3.2.18+dfsg-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu etcd-fs_0.0+git20140621.0.395eacb-4 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu etcd-server_3.2.18+dfsg-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu ethflux_1.0-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu fakemachine_0.0~git20181105.9316584-1 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu fdroidcl_0.4.0-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu fscrypt_0.2.4-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu fzf_0.17.5-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu genxdr_2.0.1-5 . ANY . -m 'Rebuild with current golang-1.10'
  nmu gitaly_0.129.0+debian-3 . ANY . -m 'Rebuild with current golang-1.10'
  nmu git-sizer_1.2.0+dfsg-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu gobgpd_1.33-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu go-bindata_3.0.7+git20151023.72.a0ff256-3 . ANY . -m 'Rebuild with 
current golang-1.10'
  nmu gobuster_1.4.1-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu gocode_20170907-3 . ANY . -m 'Rebuild with current golang-1.10'
  nmu gocryptfs_1.6.1-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu go-cve-dictionary_0.1.1+git20180404.0.4ee71e8-1 . ANY . -m 'Rebuild with 
current golang-1.10'
  nmu go-dep_0.5.0-1 . ANY . -m 'Rebuild with current golang-1.10'
  nmu gogoprotobuf_1.0.0+git20180330.1ef32a8b-1 . ANY . -m 'Rebuild with 
current golang-1.10'
  nmu gogottrpc_0.0~git20180205.d452837-1 . ANY . -m 'Rebuild with current 
golang-1.10'
  nmu goi18n_1.10.0-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu goiardi_0.11.8-2 . ANY . -m 'Rebuild with current golang-1.10'
  nmu 

Bug#916641: jaxb: leaves alternatives after purge: /usr/bin/{schemagen,xjc}

[Andreas Beckmann]

Package: jaxb
Version: 2.3.0.1-7
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8:

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-removal-and-or-configuration-purging

The leftover files are actually alternatives that were installed by the
package but have not been properly removed.

While there is ongoing discussion how to remove alternatives correctly
(see https://bugs.debian.org/71621 for details) the following strategy
should work for regular cases:
* 'postinst configure' always installs the alternative
* 'prerm remove' removes the alternative
* 'postrm remove' and 'postrm disappear' remove the alternative
In all other cases a maintainer script is invoked (e.g. upgrade,
deconfigure) the alternatives are not modified to preserve user
configuration.
Removing the alternative in 'prerm remove' avoids having a dangling link
once the actual file gets removed, but 'prerm remove' is not called in
all cases (e.g. unpacked but not configured packages or disappearing
packages) so the postrm must remove the alternative again
(update-alternatives gracefully handles removal of non-existing
alternatives).

Note that the arguments for adding and removing alternatives differ, for
removal it's 'update-alternatives --remove  '.

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

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

0m50.4s ERROR: WARN: Broken symlinks:
  /usr/share/man/man1/xjc.1 -> /etc/alternatives/xjc.1
  /usr/share/man/man1/schemagen.1 -> /etc/alternatives/schemagen.1
  /usr/bin/xjc -> /etc/alternatives/xjc
  /usr/bin/schemagen -> /etc/alternatives/schemagen
  /etc/alternatives/xjc.1 -> /usr/share/jaxb/man/xjc.1
  /etc/alternatives/xjc -> /usr/share/jaxb/bin/xjc.zip.sh
  /etc/alternatives/schemagen.1 -> /usr/share/jaxb/man/schemagen.1
  /etc/alternatives/schemagen -> /usr/share/jaxb/bin/schemagen.zip.sh

0m52.7s INFO: Warning: Package purging left files on system:
  /etc/alternatives/schemagen -> /usr/share/jaxb/bin/schemagen.zip.shnot 
owned
  /etc/alternatives/schemagen.1 -> /usr/share/jaxb/man/schemagen.1   not 
owned
  /etc/alternatives/xjc -> /usr/share/jaxb/bin/xjc.zip.shnot owned
  /etc/alternatives/xjc.1 -> /usr/share/jaxb/man/xjc.1   not owned
  /usr/bin/schemagen -> /etc/alternatives/schemagen  not owned
  /usr/bin/xjc -> /etc/alternatives/xjc  not owned
  /usr/share/man/man1/schemagen.1 -> /etc/alternatives/schemagen.1   not 
owned
  /usr/share/man/man1/xjc.1 -> /etc/alternatives/xjc.1   not owned


cheers,

Andreas


jaxb_2.3.0.1-7.log.gz
Description: application/gzip

Bug#916639: LXC AppArmor confinement breaks systemd v240

[intrigeri]

Package: lxc
Version: 1:3.0.3-1
Severity: normal
Tags: patch
X-Debbugs-Cc: Michael Biebl , Wolfgang Bumiller 

User: pkg-apparmor-t...@lists.alioth.debian.org
Usertags: buggy-profile

Hi,

as discussed on https://bugs.debian.org/911806 the current LXC
AppArmor support breaks systemd v240, which now refuses to start units
if it can't set up various sandboxing features, while previously it
would merely start the units without the configured sandboxing.
Michael Biebl originally reported this failure in the context of the
systemd autopkgtests but I expect the same problem will affect regular
full-system containers as well.

Testing confirms that this problem is fixed by backporting 3 commits
(e6ec0a9, e7311a84 and 1800f92) from LXC 3.1.0. I'm attaching the
resulting backported patches. Credit goes to Wolfgang Bumiller who did
the work upstream and to Michael Biebl who reported the problem in
great details.

If Buster is going to be released with LXC 3.0.x, IMO we need to
either apply these patches or disable AppArmor by default for new LXC
containers. And if we're going to ship with LXC 3.1.0 or newer, then
feel free to disregard this request and close this bug with the first
upload of LXC 3.1.0+ :)

Cheers,
-- 
intrigeri

From: Wolfgang Bumiller 
Date: Wed, 25 Jul 2018 12:11:31 +0200
Subject: apparmor: profile generation

This copies lxd's apparmor profile generation. This tries to
detect features such as cgroup namespaces, apparmor
namespaces and stacking support, and has profile parts
conditionally for unprivileged containers.

This introduces the following changes to the configuration:
  lxc.apparmor.profile = generated
The fixed value 'generated' will cause this
functionality to be used, otherwise there should be no
functional changes happening unless specifically
requested with the next key:
  lxc.apparmor.allow_nesting
This is a boolean which, if enabled, causes the
following changes: When generated apparmor profiles are
used, they will contain the necessary changes to allow
creating a nested container. In addition to the usual
mount points, /dev/.lxc/proc and /dev/.lxc/sys will
contain procfs and sysfs mount points without the lxcfs
overlays, which, if generated apparmor profiles are
being used, will not be read/writable directly.
  lxc.apparmor.raw
A list of raw apparmor profile lines to append to the
profile. Only valid when using generated profiles.

The following apparmor profile lines have not been copied
from lxd:

  mount /var/lib/lxd/shmounts/ -> /var/lib/lxd/shmounts/,
  mount none -> /var/lib/lxd/shmounts/,
  mount options=bind /var/lib/lxd/shmounts/** -> /var/lib/lxd/**,

They should be added via lxc.apparmor.raw entries by lxd.

In order for apparmor_parser's cache to be of use, this adds
a --with-apparmor-cache-dir ./configure option.

Signed-off-by: Wolfgang Bumiller 
---
 configure.ac   |   8 +
 src/lxc/Makefile.am|   1 +
 src/lxc/conf.c |  43 ++-
 src/lxc/conf.h |   8 +-
 src/lxc/confile.c  |  95 +
 src/lxc/criu.c |   3 +-
 src/lxc/lsm/apparmor.c | 974 ++---
 src/lxc/lsm/lsm.c  |  30 +-
 src/lxc/lsm/lsm.h  |   8 +-
 src/lxc/lsm/nop.c  |   2 +-
 src/lxc/lsm/selinux.c  |   4 +-
 src/lxc/start.c|  14 +-
 12 files changed, 1134 insertions(+), 56 deletions(-)

diff --git a/configure.ac b/configure.ac
index 950c8dd..4dee8bb 100644
--- a/configure.ac
+++ b/configure.ac
@@ -485,6 +485,13 @@ AC_ARG_WITH([cgroup-pattern],
 		[pattern for container cgroups]
 	)], [], [with_cgroup_pattern=['lxc/%n']])
 
+# The path for the apparmor_parser's cache for generated apparmor profiles
+AC_ARG_WITH([apparmor-cache-dir],
+	[AC_HELP_STRING(
+		[--with-apparmor-cache-dir=dir],
+		[path for apparmor_parser cache]
+	)], [], [with_apparmor_cache_dir=['${localstatedir}/cache/lxc/apparmor']])
+
 # Container log path.  By default, use $lxcpath.
 AC_MSG_CHECKING([Whether to place logfiles in container config path])
 AC_ARG_ENABLE([configpath-log],
@@ -531,6 +538,7 @@ AS_AC_EXPAND(LXCBINHOOKDIR, "$libexecdir/lxc/hooks")
 AS_AC_EXPAND(LXCINITDIR, "$libexecdir")
 AS_AC_EXPAND(LOGPATH, "$with_log_path")
 AS_AC_EXPAND(RUNTIME_PATH, "$with_runtime_path")
+AS_AC_EXPAND(APPARMOR_CACHE_DIR, "$with_apparmor_cache_dir")
 AC_SUBST(DEFAULT_CGROUP_PATTERN, ["$with_cgroup_pattern"])
 
 # We need the install path so criu knows where to reference the hook scripts.
diff --git a/src/lxc/Makefile.am b/src/lxc/Makefile.am
index 08e2fab..463ee8d 100644
--- a/src/lxc/Makefile.am
+++ b/src/lxc/Makefile.am
@@ -187,6 +187,7 @@ AM_CFLAGS = -DLXCROOTFSMOUNT=\"$(LXCROOTFSMOUNT)\" \
 	-DDEFAULT_CGROUP_PATTERN=\"$(DEFAULT_CGROUP_PATTERN)\" \
 	-DRUNTIME_PATH=\"$(RUNTIME_PATH)\" \
 	-DSBINDIR=\"$(SBINDIR)\" \
+	-DAPPARMOR_CACHE_DIR=\"$(APPARMOR_CACHE_DIR)\" \
 	-I $(top_srcdir)/src \
 	-I $(top_srcdir)/src/lxc \
 	-I $(top_srcdir)/src/lxc/storage \
diff 

Bug#913715: simulide: terminates with segfault sometimes, when trying to undo changes

[Bernhard Übelacker]

Hello Nils Jarle Haugen,
these instructions are great to reproduce the crash.

Below is the backtrace with debug symbols installed.
It looks like the vector m_boardLed->m_pin contains invalid
data, and therefore we crash when calling methods on an
element retrieved from it.

Valgrind shows the same backtrace, while the accessed element
got free'd before.

This should probably be forwarded to upstream developers.
Upstream commit [1] might be related, but does not apply
cleanly to 0.1.7+dfsg-2.

Kind regards,
Bernhard



[1] https://sourceforge.net/p/simulide/svnrepo/434/




Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x5588dcda66e5 in Arduino::initialize (this=0x5588de934280) at 
../src/gui/circuitwidget/components/mcu/arduino.cpp:173
173 m_boardLed->getEpin(0)->setEnode(enod);
[Current thread is 1 (Thread 0x7f4e80ab3f80 (LWP 12035))]
(gdb) set width 0
(gdb) set pagination off
(gdb) directory /home/benutzer/simulide/orig/simulide-0.1.7+dfsg/src
Source directories searched: 
/home/benutzer/simulide/orig/simulide-0.1.7+dfsg/src:$cdir:$cwd
(gdb) bt
#0  0x5588dcda66e5 in Arduino::initialize (this=0x5588de934280) at 
../src/gui/circuitwidget/components/mcu/arduino.cpp:173
#1  0x5588dcdfee62 in Simulator::runContinuous (this=0x5588de808c30) at 
../src/simulator/simulator.cpp:176
#2  0x5588dcd321bf in Circuit::undo (this=this@entry=0x5588de808ba0) at 
../src/gui/circuitwidget/circuit.cpp:602
#3  0x5588dcd36230 in Circuit::keyPressEvent (this=0x5588de808ba0, 
event=0x7ffc53072c50) at ../src/gui/circuitwidget/circuit.cpp:999
#4  0x7f4e8912a567 in QGraphicsScene::event (this=0x5588de808ba0, 
event=0x7ffc53072c50) at graphicsview/qgraphicsscene.cpp:3387
#5  0x7f4e88e1a491 in QApplicationPrivate::notify_helper 
(this=this@entry=0x5588de7832c0, receiver=receiver@entry=0x5588de808ba0, 
e=e@entry=0x7ffc53072c50) at kernel/qapplication.cpp:3727
#6  0x7f4e88e21ad0 in QApplication::notify (this=0x7ffc53072ea0, 
receiver=0x5588de808ba0, e=0x7ffc53072c50) at kernel/qapplication.cpp:3486
#7  0x7f4e8832d039 in QCoreApplication::notifyInternal2 
(receiver=0x5588de808ba0, event=event@entry=0x7ffc53072c50) at 
../../include/QtCore/5.11.2/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307
#8  0x7f4e89146f87 in QCoreApplication::sendEvent (event=0x7ffc53072c50, 
receiver=) at 
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234
#9  QGraphicsView::keyPressEvent (this=0x5588de85a9e0, event=0x7ffc53072c50) at 
graphicsview/qgraphicsview.cpp:3161
#10 0x7f4e88e58de7 in QWidget::event (this=this@entry=0x5588de85a9e0, 
event=event@entry=0x7ffc53072c50) at kernel/qwidget.cpp:8940
#11 0x7f4e88efbdee in QFrame::event (this=this@entry=0x5588de85a9e0, 
e=e@entry=0x7ffc53072c50) at widgets/qframe.cpp:550
#12 0x7f4e88efea04 in QAbstractScrollArea::event (this=0x5588de85a9e0, 
e=0x7ffc53072c50) at widgets/qabstractscrollarea.cpp:1168
#13 0x7f4e88e1a491 in QApplicationPrivate::notify_helper 
(this=this@entry=0x5588de7832c0, receiver=receiver@entry=0x5588de85a9e0, 
e=e@entry=0x7ffc53072c50) at kernel/qapplication.cpp:3727
#14 0x7f4e88e22a59 in QApplication::notify (this=, 
receiver=0x5588de85a9e0, e=0x7ffc53072c50) at kernel/qapplication.cpp:3121
#15 0x7f4e8832d039 in QCoreApplication::notifyInternal2 
(receiver=0x5588de85a9e0, event=0x7ffc53072c50) at 
../../include/QtCore/5.11.2/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307
#16 0x7f4e88e75e79 in QWidgetWindow::event (event=0x7ffc53072c50, 
this=0x5588de92ce80) at kernel/qwidgetwindow.cpp:274
#17 QWidgetWindow::event (this=0x5588de92ce80, event=0x7ffc53072c50) at 
kernel/qwidgetwindow.cpp:224
#18 0x7f4e88e1a491 in QApplicationPrivate::notify_helper 
(this=this@entry=0x5588de7832c0, receiver=receiver@entry=0x5588de92ce80, 
e=e@entry=0x7ffc53072c50) at kernel/qapplication.cpp:3727
#19 0x7f4e88e21ad0 in QApplication::notify (this=0x7ffc53072ea0, 
receiver=0x5588de92ce80, e=0x7ffc53072c50) at kernel/qapplication.cpp:3486
#20 0x7f4e8832d039 in QCoreApplication::notifyInternal2 
(receiver=receiver@entry=0x5588de92ce80, event=event@entry=0x7ffc53072c50) at 
../../include/QtCore/5.11.2/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307
#21 0x7f4e8872e388 in QCoreApplication::sendSpontaneousEvent 
(event=0x7ffc53072c50, receiver=0x5588de92ce80) at 
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:237
#22 QGuiApplicationPrivate::processKeyEvent (e=0x7f4e78028cb0) at 
kernel/qguiapplication.cpp:2207
#23 0x7f4e88733a05 in QGuiApplicationPrivate::processWindowSystemEvent 
(e=e@entry=0x7f4e78028cb0) at kernel/qguiapplication.cpp:1822
#24 0x7f4e8870dd8b in QWindowSystemInterface::sendWindowSystemEvents 
(flags=...) at kernel/qwindowsysteminterface.cpp:1032
#25 0x7f4e80a0585b in QPAEventDispatcherGlib::processEvents 
(this=0x5588de775ef0, flags=...) at qeventdispatcher_glib.cpp:70
#26 0x7f4e8832bd0b in 

Bug#916640: Changes to GAP necessary for sagemath

[Tobias Hansen]

Package: src:gap
Version: 4r10p0-2
Severity: wishlist
Tags: sid buster patch
Control: block 912980 by -1

Hi Bill,

the sagemath developers managed to get sagemath to work with gap 4.10 [1], 
however they require some changes to GAP. I'm filing this bug in order to 
discuss how we can get a gap in Debian before the buster freeze that works with 
sagemath. I updated the sagemath package in git and it works fine when I apply 
the attached patch to gap. This debdiff applies three patches and installs 
libgap to /usr/lib/triplet, so that it can be found.

The three patches all have corresponding pull requests, one of them is already 
merged:

0001-a-version-of-the-writeandcheck.patch-from-Sage-that-.patch - 
https://github.com/gap-system/gap/pull/3102 (open)
0002-kernel-add-helper-function-for-writing-error-message.patch - 
https://github.com/gap-system/gap/pull/3043 (merged)
0003-Prototype-for-GAP_Enter-Leave-macros-to-bracket-use-.patch - 
https://github.com/gap-system/gap/pull/3096 (open)

Please let me know how we can proceed with this.

Best,
Tobias

[1] https://trac.sagemath.org/ticket/22626
diff -Nru gap-4r10p0/debian/changelog gap-4r10p0/debian/changelog
--- gap-4r10p0/debian/changelog 2018-12-03 20:53:59.0 +0100
+++ gap-4r10p0/debian/changelog 2018-12-16 15:06:41.0 +0100
@@ -1,3 +1,11 @@
+gap (4r10p0-2.2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Include three patches from sagemath.
+  * Install libgap to /usr/lib/triplet.
+
+ -- Tobias Hansen   Sun, 16 Dec 2018 14:06:41 +
+
 gap (4r10p0-2) experimental; urgency=medium
 
   * New patch fix-test-bigendian: fix test on bigendian systems.
diff -Nru 
gap-4r10p0/debian/patches/0001-a-version-of-the-writeandcheck.patch-from-Sage-that-.patch
 
gap-4r10p0/debian/patches/0001-a-version-of-the-writeandcheck.patch-from-Sage-that-.patch
--- 
gap-4r10p0/debian/patches/0001-a-version-of-the-writeandcheck.patch-from-Sage-that-.patch
   1970-01-01 01:00:00.0 +0100
+++ 
gap-4r10p0/debian/patches/0001-a-version-of-the-writeandcheck.patch-from-Sage-that-.patch
   2018-12-07 16:20:32.0 +0100
@@ -0,0 +1,74 @@
+From 163b8aae99b1b206e5ae85763e21f47b7651f9c4 Mon Sep 17 00:00:00 2001
+From: "Erik M. Bray" 
+Date: Tue, 4 Dec 2018 12:44:23 +
+Subject: [PATCH 1/3] a version of the writeandcheck.patch from Sage that works
+ against 4.10
+
+---
+ src/sysfiles.c | 18 +-
+ 1 file changed, 13 insertions(+), 5 deletions(-)
+
+diff --git a/src/sysfiles.c b/src/sysfiles.c
+index 2250784..45b4347 100644
+--- a/src/sysfiles.c
 b/src/sysfiles.c
+@@ -159,21 +159,23 @@ SYS_SY_BUFFER syBuffers[32];
+ /* utility to check return value of 'write'  */
+ ssize_t echoandcheck(int fid, const char *buf, size_t count) {
+   int ret;
++  static int depth = 0;
++  depth++;
+   if (syBuf[fid].type == gzip_socket) {
+   ret = gzwrite(syBuf[fid].gzfp, buf, count);
+-  if (ret < 0)
++  if (ret < 0 && depth == 1)
+   ErrorQuit(
+   "Could not write to compressed file, see 
'LastSystemError();'\n",
+   0L, 0L);
+   }
+   else {
+   ret = write(syBuf[fid].echo, buf, count);
+-  if (ret < 0)
++  if (ret < 0 && depth == 1)
+   ErrorQuit("Could not write to file descriptor %d, see "
+ "'LastSystemError();'\n",
+ syBuf[fid].fp, 0L);
+   }
+-
++  depth--;
+   return ret;
+ }
+ 
+@@ -1636,21 +1638,27 @@ Int SyWrite(Int fid, const void * ptr, size_t len)
+ static ssize_t SyWriteandcheck(Int fid, const void * buf, size_t count)
+ {
+ int ret;
++static int depth = 0;
++depth++;
+ if (syBuf[fid].type == gzip_socket) {
+ ret = gzwrite(syBuf[fid].gzfp, buf, count);
+-if (ret < 0)
++if (ret < 0 && depth == 1) {
+ ErrorQuit(
+ "Cannot write to compressed file, see 'LastSystemError();'\n",
+ 0L, 0L);
++}
+ }
+ else {
+ ret = write(syBuf[fid].fp, buf, count);
+-if (ret < 0)
++if (ret < 0 && depth == 1) {
+ ErrorQuit("Cannot write to file descriptor %d, see "
+   "'LastSystemError();'\n",
+   syBuf[fid].fp, 0L);
++}
+ }
+ 
++depth--;
++
+ return ret;
+ }
+ 
+-- 
+1.9.1
+
diff -Nru 
gap-4r10p0/debian/patches/0002-kernel-add-helper-function-for-writing-error-message.patch
 
gap-4r10p0/debian/patches/0002-kernel-add-helper-function-for-writing-error-message.patch
--- 
gap-4r10p0/debian/patches/0002-kernel-add-helper-function-for-writing-error-message.patch
   1970-01-01 01:00:00.0 +0100
+++ 
gap-4r10p0/debian/patches/0002-kernel-add-helper-function-for-writing-error-message.patch
   2018-12-07 16:20:43.0 +0100
@@ -0,0 +1,122 @@
+From 0cecb79ff97c73a24acacf8afdc3edba93507661 Mon Sep 17 00:00:00 2001
+From: "Erik M. Bray" 
+Date: Thu, 22 Nov 2018 10:53:31 +0100
+Subject: [PATCH 2/3] kernel: add helper function for writing error messages to

Bug#916632: stretch-pu: package nvidia-graphics-drivers/390.87-4~deb9u1

[Andreas Beckmann]

Followup-For: Bug #916632

the compressed debdiff


ngd-390.87-4~deb9u1.diff.gz
Description: application/gzip

Bug#916638: ITP : dragonfly-reverb - an audio reverb software

[trebmuh]

Package: wnpp
Severity: whishlist
Owner: 'Olivier Humbert' 

* Package name: dragonfly-reverb
  Version : 1.1.2
  Upstream Author : Michael Willis
* URL : https://github.com/michaelwillis/dragonfly-reverb/
* License : GPL-3
  Description : A very nice and easy-to-use reverb available in LV2, 
VST, and jack-standalone formats.

Bug#916626: Acknowledgement (qbs: FTBFS on hppa: Segmentation fault (core dumped))

[John David Anglin]

Yes, it's is a bug in libqt5script5:

(gdb) break QTJSC::Heap::markConservatively(QTJSC::MarkStack&, void*, void*)
Breakpoint 1 at 0xf65219c0: file
../3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp, line 791.
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/dave/debian/qbs/qbs-1.12.2+dfsg/bin/qbs build
--settings-dir qbsres/settings -f
/home/dave/debian/qbs/qbs-1.12.2+dfsg/qbs.qbs -d qbsres -p 'qbs
resources' project.withCode:false project.withDocumentation:false
profile:none
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/hppa-linux-gnu/libthread_db.so.1".
[New Thread 0xef7e7440 (LWP 1788)]
[New Thread 0xee582440 (LWP 1789)]
Restoring build graph from disk
[Detaching after fork from child process 1790]
[New Thread 0xedd81440 (LWP 1791)]
[Thread 0xee582440 (LWP 1789) exited]
Building for configuration default
[Switching to Thread 0xedd81440 (LWP 1791)]

Thread 4 "QThread" hit Breakpoint 1, QTJSC::Heap::markConservatively (
this=0xf8b53c78, markStack=..., start=0xed5826c8, end=0xedd81000)
at ../3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp:791
791 ../3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp:
No such file or directory.

The address 0xedd81000 is the end of the stack.

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

Bug#916625: Please call dh_installsystemd and bump debhelper compat to 12

[Laurent Bigonville]

On Sun, 16 Dec 2018 18:44:07 +0100 Laurent Bigonville  
wrote:


> Hi,
>
> Currently qemu is using debhelper compat version 9 and is calling
> dh_installinit for qemu-guest-agent.

Please find the attached patch

The package builds fine and qemu-guest-agent package can be installed on 
a physical machine.


diff -Nru qemu-3.1+dfsg/debian/compat qemu-3.1+dfsg/debian/compat
--- qemu-3.1+dfsg/debian/compat	2018-12-02 17:10:27.0 +0100
+++ qemu-3.1+dfsg/debian/compat	2018-12-16 17:43:20.0 +0100
@@ -1 +1 @@
-9
+12
diff -Nru qemu-3.1+dfsg/debian/control qemu-3.1+dfsg/debian/control
--- qemu-3.1+dfsg/debian/control	2018-12-02 17:10:27.0 +0100
+++ qemu-3.1+dfsg/debian/control	2018-12-16 17:43:20.0 +0100
@@ -6,7 +6,7 @@
 Uploaders: Aurelien Jarno ,
 	Riku Voipio ,
 	Michael Tokarev 
-Build-Depends: debhelper (>= 9),
+Build-Depends: debhelper (>= 11),
 # In comments below we also specify (system-specific) arguments
 # to qemu's configure script, -- optional features which depend
 # on build-dependencies.
@@ -430,6 +430,7 @@
 Architecture: any
 Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base (>= 3.0-6)
+Pre-Depends: ${misc:Pre-Depends}
 Description: Guest-side qemu-system agent
  QEMU is a fast processor emulator: currently the package supports
  ARM, CRIS, i386, M68k (ColdFire), MicroBlaze, MIPS, PowerPC, SH4,
diff -Nru qemu-3.1+dfsg/debian/control-in qemu-3.1+dfsg/debian/control-in
--- qemu-3.1+dfsg/debian/control-in	2018-12-02 17:10:27.0 +0100
+++ qemu-3.1+dfsg/debian/control-in	2018-12-16 17:43:20.0 +0100
@@ -7,7 +7,7 @@
 Uploaders: Aurelien Jarno ,
 	Riku Voipio ,
 	Michael Tokarev 
-Build-Depends: debhelper (>= 9),
+Build-Depends: debhelper (>= 11),
 # In comments below we also specify (system-specific) arguments
 # to qemu's configure script, -- optional features which depend
 # on build-dependencies.
@@ -440,6 +440,7 @@
 Architecture: any
 Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base (>= 3.0-6)
+Pre-Depends: ${misc:Pre-Depends}
 Description: Guest-side qemu-system agent
  QEMU is a fast processor emulator: currently the package supports
  ARM, CRIS, i386, M68k (ColdFire), MicroBlaze, MIPS, PowerPC, SH4,
diff -Nru qemu-3.1+dfsg/debian/rules qemu-3.1+dfsg/debian/rules
--- qemu-3.1+dfsg/debian/rules	2018-12-02 17:10:27.0 +0100
+++ qemu-3.1+dfsg/debian/rules	2018-12-16 17:43:20.0 +0100
@@ -259,7 +259,7 @@
 endif	# enable_linux_user
 
 # install whole thing so --list-missing works right
-	dh_install --list-missing
+	dh_install
 # install the rest for arch/indep as needed
 	dh_installdocs ${ai} -Nqemu-user-binfmt
 	dh_installchangelogs ${ai} -Nqemu-user-binfmt
@@ -273,12 +273,14 @@
 		debian/qemu-system-common/etc/qemu-ifup
 endif
 	dh_installinit -pqemu-guest-agent
+	dh_installsystemd -pqemu-guest-agent --no-start --no-enable
 endif
 	dh_link ${ai}
 	dh_lintian ${ai}
 	dh_strip ${ai}
 	dh_compress ${ai}
 	dh_fixperms ${ai}
+	dh_missing --list-missing ${ai}
 	dh_shlibdeps ${ai}
 	dh_installdeb ${ai}
 ifeq ($(enable_linux_user),enable)

Bug#916499: autopkgtest: Something™ in autopkgtest 5.7 breaks something™ in at least libhtml-formfu-perl's autopkgtests

[Niko Tyni]

Control: tag -1 patch

On Sat, Dec 15, 2018 at 09:53:54PM +0200, Niko Tyni wrote:
> On Sat, Dec 15, 2018 at 03:52:58AM +0100, gregor herrmann wrote:
> > Package: autopkgtest
> > Version: 5.7
> > Severity: normal
> 
> > autopkgtest [03:29:08]: ERROR: "chmod -R go+rwX -- 
> > /tmp/autopkgtest.ES3bLl/autopkgtest-satdep.deb" failed with stderr 
> > "/bin/chmod: cannot access 
> > '/tmp/autopkgtest.ES3bLl/autopkgtest-satdep.deb': No such file or directory
 
> It looks to me like a race where the TempPath destructor for
> autopkgtest-satdep.deb gets run after the next test has created a new
> TempPath object for the same filename.

I see a few different ways to fix this.

A. Find out why the TempPath.__del__ finalizer gets called late

   I suppose there must be a reference cycle involved but I can't see
   it offhand. This seems to be enough of a heisenbug that just 'import gc'
   makes it go away for my test case, making debugging hard.

B. Remove the TempPath.__del__ finalizer and add explicit cleanup calls

   It looks like there are only two uses with autoclean enabled in the
   code, so this seems doable.

C. Make TempPath use unique file names so collisions don't matter

   It would probably be best to do this only when autoclean is enabled,
   so that anything saved in the output dir (= autoclean disabled)
   would keep its current name.

The attached patch implements C as a minimal change.
-- 
Niko
>From 8c39a1dd0942e265ab48ce5b7a418b7ce435d451 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sun, 16 Dec 2018 20:10:54 +0200
Subject: [PATCH] Ensure that autocleaned TempPath file names are unique

In some circumstances the TempPath.__del__() finalizer may get
run late enough that a new TempPath instance has been created
with the same name.

Prepend a running counter to the actual file names used to prevent
collisions.

Closes: #916499
---
 lib/adt_testbed.py | 8 
 1 file changed, 8 insertions(+)

diff --git a/lib/adt_testbed.py b/lib/adt_testbed.py
index f46a4df..4fe8874 100644
--- a/lib/adt_testbed.py
+++ b/lib/adt_testbed.py
@@ -1484,6 +1484,10 @@ class TempPath(Path):
 
 These are only guaranteed to exit within one testbed run.
 '''
+
+# private; used to make sure the names of autocleaned files don't collide
+_filename_prefix = 1
+
 def __init__(self, testbed, name, is_dir=False, autoclean=True):
 '''Create a temporary Path object.
 
@@ -1507,6 +1511,10 @@ class TempPath(Path):
 else:
 host = testbed.output_dir
 self.autoclean = autoclean
+if autoclean:
+name = str(self._filename_prefix) + '-' + name
+TempPath._filename_prefix += 1
+
 Path.__init__(self, testbed, os.path.join(host, name),
   os.path.join(testbed.scratch, name),
   is_dir)
-- 
2.20.0

Bug#911806: Please provide a way to opt out of AppArmor confinement when running tests

[intrigeri]

Hi,

Michael Biebl:
> $ ./make-dsc
> 

It took me a while to get back to this thread; obviously upstream
master has moved on since you wrote this, so:

I had to update Use-Debian-specific-config-files.patch to make it
apply and use helper functions in a way that's compatible with their
current API. Updated patch attached, in case it may save you
some time.

I've also added two patches to BLACKLIST (refreshing them seemed
non-trivial as I'm not a C developer):
Revert-udev-network-device-renaming-immediately-give.patch
fsckd-daemon-for-inter-fsckd-communication.patch

> lxc.aa_profile = unconfined

FTR with LXC 3.x that's now:

  lxc.apparmor.profile = unconfined

> There are currently two, known failures with AA turned off:
> - dnsmasq 2.80 introduced a regression in networkd-test.py
> - test-bpf failing

Confirmed with lxc 1:3.0.3-1 from sid.

> With AA turned on, the list of failing tests is too long to list here.

Confirmed with lxc 1:3.0.3-1 from sid: the exact same tests pass/fail
as in your logs. I see lots of mount operations denied by AppArmor.
That's expected because the AppArmor vs. systemd fixes are in LXC
3.1.0, that was released a few days ago, but not in LXC 3.0.3.

Then I've cherry-picked on top of lxc 3.0.3-1 the 3 upstream commits
that implement the nested containers vs. AppArmor fixes; and in the
config of the LXC container I use for autopkgtests I've set:

  lxc.apparmor.profile = generated
  lxc.apparmor.allow_nesting = 1

With this configuration, the systemd autopkgtests work just as well
as unconfined \o/

My current plan is thus:

1. Ask the src:lxc maintainers to apply these 3 upstream patches
   until they upgrade the package to 3.1.0+.

2. Ask the debci maintainers to use the config described above
   for LXC containers used to run autopkgtests, once they upgrade
   to Buster.

3. Let you decide what to do with the request this bug report was
   originally about.

> Hope this helpful.

This was *very* helpful and saved me lots of time :)

Thanks for your patience,
cheers,
-- 
intrigeri

>From 035ef2dcad71f449835c41387672ed680fc54dac Mon Sep 17 00:00:00 2001
From: Michael Biebl 
Date: Thu, 18 Jul 2013 20:11:02 +0200
Subject: [PATCH 01/19] Use Debian specific config files

Use /etc/default/locale instead of /etc/locale.conf for locale settings.

Use /etc/default/keyboard instead of /etc/X11/xorg.conf.d/00-keyboard.conf for
keyboard configuration.

Read/write /etc/timezone if /etc/localtime does not exist.

Gbp-Pq: Topic debian
Gbp-Pq: Name Use-Debian-specific-config-files.patch
---
 src/basic/time-util.c|  21 +++-
 src/core/locale-setup.c  |  22 
 src/locale/keymap-util.c | 210 +++
 src/timedate/timedated.c |  10 ++
 4 files changed, 156 insertions(+), 107 deletions(-)

diff --git a/src/basic/time-util.c b/src/basic/time-util.c
index 557c75debc..ea5f6a4491 100644
--- a/src/basic/time-util.c
+++ b/src/basic/time-util.c
@@ -1382,8 +1382,25 @@ int get_timezone(char **tz) {
 int r;
 
 r = readlink_malloc("/etc/localtime", );
-if (r < 0)
-return r; /* returns EINVAL if not a symlink */
+if (r < 0) {
+if (r != -EINVAL)
+return r; /* returns EINVAL if not a symlink */
+
+r = read_one_line_file("/etc/timezone", );
+if (r < 0) {
+if (r != -ENOENT)
+log_warning_errno(r, "Failed to read /etc/timezone: %m");
+return -EINVAL;
+}
+
+if (!timezone_is_valid(t, LOG_DEBUG))
+return -EINVAL;
+z = strdup(t);
+if (!z)
+return -ENOMEM;
+*tz = z;
+return 0;
+}
 
 e = PATH_STARTSWITH_SET(t, "/usr/share/zoneinfo/", "../usr/share/zoneinfo/");
 if (!e)
diff --git a/src/core/locale-setup.c b/src/core/locale-setup.c
index 584fb220a1..3d3cb641de 100644
--- a/src/core/locale-setup.c
+++ b/src/core/locale-setup.c
@@ -59,6 +59,28 @@ int locale_setup(char ***environment) {
 log_warning_errno(r, "Failed to read /etc/locale.conf: %m");
 }
 
+   if (r <= 0) {
+   r = parse_env_file(NULL, "/etc/default/locale",
+  "LANG",  [VARIABLE_LANG],
+  "LANGUAGE",  [VARIABLE_LANGUAGE],
+  "LC_CTYPE",  [VARIABLE_LC_CTYPE],
+  "LC_NUMERIC",[VARIABLE_LC_NUMERIC],
+  "LC_TIME",   [VARIABLE_LC_TIME],
+  "LC_COLLATE",[VARIABLE_LC_COLLATE],
+  "LC_MONETARY",   [VARIABLE_LC_MONETARY],
+  "LC_MESSAGES",   [VARIABLE_LC_MESSAGES],
+  "LC_PAPER",

Bug#916637: libupnp: keep out of testing

[Uwe Kleine-König]

Source: libupnp
Severity: serious

libupnp should be removed, it is about to be dropped from testing. This
bug is there to prevent it reentering testing.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (500, 'unstable-debug'), 
(500, 'testing-debug'), (500, 'stable'), (499, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#916636: RFS: smplayer-themes/1:18.6.0-1

[Mateusz Łukasik]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "smplayer-themes"

 * Package name: smplayer-themes
   Version : 1:18.6.0-1
   Upstream Author : Ricardo Villalba 
 * URL : http://smplayer.sf.net
 * License : GPL-2.0+
   Section : video

  It builds those binary packages:

smplayer-themes - complete front-end for MPlayer - icon themes

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


  https://mentors.debian.net/package/smplayer-themes

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

dget -x 
https://mentors.debian.net/debian/pool/main/s/smplayer-themes/smplayer-themes_18.6.0-1.dsc


  Changes since the last upload:
  [ Alf Gaida ]
  * New upstream release 18.6.0.
  * Added myself to uploaders.
  * Bumped compat to 11
  * Bumped debhelpers to >= 11.
  * Bumped Standards-Version to 4.2.1, no changes needed.
  * Added lintian-overrides for theme descriptions
  * Fixed debian/copyright
  * Added debian/upstream/metadata

  [ Mateusz Łukasik ]
  * Fix debian/gbp.conf.

  Regards,
   Mateusz Łukasik

Bug#916635: Subject: RFS: spacefm/1.0.6-4 [RC]

[Mateusz Łukasik]

Package: sponsorship-requests
Severity: important

  Dear mentors,

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

 * Package name: spacefm
   Version : 1.0.6-4
   Upstream Author : IgnorantGuru 
 * URL : https://github.com/IgnorantGuru/spacefm
 * License : GPL-3+
   Section : utils

  It builds those binary packages:

spacefm- Multi-panel tabbed file manager - GTK2 version
 spacefm-common - Multi-panel tabbed file manager - common files
 spacefm-gtk3 - Multi-panel tabbed file manager - GTK3 version

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


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


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

dget -x 
https://mentors.debian.net/debian/pool/main/s/spacefm/spacefm_1.0.6-4.dsc


  Changes since the last upload:

  * debian/patches:
+ Add 0001-glibc-2.28-compatibility.patch for fix FTBFS with
glibc 2.28. (Closes: #916007)
  * debian/control:
+ Bump to Standards-Version to 4.2.1.

  Regards,
   Mateusz Łukasik

Bug#916634: RFS: smplayer/18.10.0~ds0-1

[Mateusz Łukasik]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: smplayer
   Version : 18.10.0~ds0-1
   Upstream Author : Ricardo Villalba 
 * URL : http://smplayer.sf.net
 * License : GPL-2+
   Section : video

  It builds those binary packages:

smplayer   - Complete front-end for MPlayer and mpv
 smplayer-l10n - Complete front-end for MPlayer and mpv - translation files

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


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


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

dget -x 
https://mentors.debian.net/debian/pool/main/s/smplayer/smplayer_18.10.0~ds0-1.dsc


  Changes since the last upload:

   [ Alf Gaida ]
  * New upstream release
  * Added myself to uploaders
  * Patches reviewed
  * Bumped Standards-Version to 4.2.1, no changes needed
  * Improved d/rules:
- Set language to C.UTF-8
- Improved linker flags
- Added override_dh_missing
- Removed some extra licenses and not wished docs
  * Install the desktop files from debian/tmp
  * Added Files-Excluded: zlib to d/copyright
  * Removed no longer needed repack-scripts
  * Modified the watch file for the new repack
  * Added debian/upstream/metadata
  * Cleaned up d/copyright

  [ Helmut Grohne ]
  * Fix FTCBFS: (Closes: #916096)
   + Pass a cross qmake along.
   + Missing Build-Depends: qt5-qmake:native for lrelease.

  [ Mateusz Łukasik ]
  * Fix debian/gbp.conf.

  Regards,
   Mateusz Łukasik

Bug#916626: Acknowledgement (qbs: FTBFS on hppa: Segmentation fault (core dumped))

[John David Anglin]

On 2018-12-16 1:21 p.m., John David Anglin wrote:
> It looks to me as if the test "p != e" should be "p < e".

On further thought, I think gcc has miscompiled this function.

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

Bug#909498: Jessie version works here too on armhf

[anthonyf947]

Hello

60.4.0esr-1~deb9u1 still crashes on startup (armhf), but jessie's 
60.4.0esr-1~deb8u1 does indeed work nicely on stretch:)


(Thank you Debian LTS https://wiki.debian.org/LTS/Using )

Anthony

Bug#916632: stretch-pu: package nvidia-graphics-drivers/390.87-4~deb9u1

[Andreas Beckmann]

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

Hi,

I'd like to update the non-free nvidia-graphics-drivers in stretch to a
new major upstream release: 384 -> 390
But with that we finally reached a new legacy branch that will receive
updates from NVIDIA until the end of 2022. So any future updates in
stretch will only come from the 390 series and (hopefully) require no or
only minimal changes to the packaging. (Going beyond 390 will be a major
step: i386 and armhf driver support are dropped).

There is currently no CVE known to be fixed with this new release, but I
expect updates for CVE‑2018‑6260 soon.

This is a rebuild of the package in sid with some inappropriate changes
removed. As usual the diff is not minimal compared the the version
currently in stable, but to the versions in sid (this driver series is
also available as nvidia-graphics-drivers-legacy-390xx in sid and (soon)
stretch-backports). This will allow us to keep the packaging of the many
releases in sync and ease propagating future changes through all
packages.

The 390 driver has been available in stretch backports for a long
time already and we are not aware of any regressions.

There is infrastructure to generate debian/control - that will be made
use of in buster, for stretch it just regenerates the exisiting control
file (with comments removed).

We will be dropping three packages (*wayland*) that were only introduced
in a stretch point release. They have no users in stretch and for buster
the functionality will be provided by a separate source package in main.

The debdiff (excluding the blob parts) will be sent in a separate mail
due to size.

This pu needs to go into stable together with glx-alternatives (#916627)
for some changes in the diversions and alternatives.

I'll prepare further updates for nvidia-settings, nvidia-xconfig,
nvidia-modprobe, nvidia-persistenced to the 390.xx release series, too,
to keep the major version in sync with the driver - otherwise we may be
running an unsupported and untested combination of versions (which might
also confuse users due to the significant version skew).
But this will wait until after a new driver release has been published
(I'll either update this pu request or open a new one, depending on
progress) or until the next point release deadlines are announced.
But I'd prefer to see 390.xx in stretch-pu soon, to give it some early
exposure and have more time for testing, even if it means to have two
nvidia-graphics-drivers uploads to stretch-pu for the next point
release.


Andreas

Bug#916631: libwildmidi-dev: Please ship pkg-config file in -dev package

[Tim Müller]

Package: libwildmidi-dev
Version: 0.4.2-1
Severity: wishlist


Hello,

I believe recent versions of wildmidi ship a .pc file on Linux.

It would be great if you could ship that.

Thanks!

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libwildmidi-dev depends on:
ii  libwildmidi2  0.4.2-1

libwildmidi-dev recommends no packages.

libwildmidi-dev suggests no packages.

-- no debconf information

Bug#916626: Acknowledgement (qbs: FTBFS on hppa: Segmentation fault (core dumped))

[John David Anglin]

On 2018-12-16 1:04 p.m., John David Anglin wrote:
> Thread 4 "QThread" hit Breakpoint 1, QTJSC::Heap::markConservatively (
> this=0xf8b53c78, markStack=..., start=0xed5826c8, end=0xedd81000)
> at ../3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp:791
> 791 ../3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp:
> No such file or directory.
> 
> The address 0xedd81000 is the end of the stack.

void Heap::markConservatively(MarkStack& markStack, void* start, void* end)
{
if (start > end) {
void* tmp = start;
start = end;
end = tmp;
}

ASSERT((static_cast(end) - static_cast(start)) <
0x100);
ASSERT(isPointerAligned(start));
ASSERT(isPointerAligned(end));

char** p = static_cast(start);
char** e = static_cast(end);

CollectorBlock** blocks = m_heap.blocks;
while (p != e) {

It looks to me as if the test "p != e" should be "p < e".

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

Bug#916630: terminology: Remote execution via special escape codes that handle unknown media types

[Ross Vandegrift]

Package: terminology
Version: 1.3.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Owner: r...@kallisti.us
Forwarded: https://phab.enlightenment.org/T7504

Terminology 1.3.1 has been released to fix a remote code execution
vulnerability in special escape handling.  This can be mitigated by unchecking
Settings -> Enable special Terminology escape codes.  I'm preparing a release.


Details from upstream bug report:
The \e}pn sequence allows a user to display media like an image or open a
web page. However, all unknown media types are handled with the
media_unknown_handle function which executes xdg-open against the file type.
This creates a large attack surface that allows a remotely introduced
executable file to be executed when that file's MIME type is registered for
xdg-open.

See the linked bug for full info.

Ross

Bug#916629: command-not-found: Today, I run startx command and a few minutes later computer frozen i reboot the computer but it loop in login screen and i started in root mode and i checkedjournalctl

[Mert]

Package: command-not-found
Version: 18.04.5-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation? I think startx and lightdm
   * What exactly did you do (or not do) that was effective (or
 ineffective)? i run update-command-not-found command but nothing effected 
   * What was the outcome of this action? Nothing happened
   * What outcome did you expect instead? I expected it solved

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


-- System Information:
Distributor ID: Parrot
Description:Parrot GNU/Linux 4.4
Release:4.4
Codename:   n/a
Architecture: x86_64

Kernel: Linux 4.18.0-parrot20-amd64 (SMP w/4 CPU cores)
Locale: LANG=tr_TR.UTF-8, LC_CTYPE=tr_TR.UTF-8 (charmap=UTF-8), 
LANGUAGE=tr_TR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages command-not-found depends on:
ii  apt-file 3.1.6
ii  lsb-release  10.2018112800
ii  python3  3.6.7-1
ii  python3-apt  1.7.0+parrot1

command-not-found recommends no packages.

Versions of packages command-not-found suggests:
ii  snapd  2.30-5+b1

-- no debconf information

Bug#916556: qtbase-opensource-src: Upstream no longer uses name "qtbase-opensource-src" since 5.10

[Lisandro Damián Nicanor Pérez Meyer]

El sábado, 15 de diciembre de 2018 17:44:41 -03 Kai Pastor escribió:
> Source: qtbase-opensource-src
> Severity: normal
> 
> Dear Maintainer,
> 
> I noticed that debian/copyright for the latest qtbase-opensource-src starts
> with:
> 
> Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> Upstream-Name: qtbase-opensource-src
> Source: https://download.qt.io/official_releases/qt/*/submodules/
> 
> 
> However, since Qt 5.10, the upstream source tarballs are called qtbase-
> everywhere-src-... (and similar for the other modules).
> (There are qt-opensource-... binaries, but qtbase-opensource-src seems to no
> longer be a "name upstream uses for the software".

Rightm there is no gain for us to change to source name. But I guess debian/
copyright need to be updated.
 
> In addition, while the given "Source" will work at the time of the release,
> the "official release" is just a temporary place.
> The permanent location is https://download.qt.io/archive/qt/*/submodules/

Interesting, maybe that was not the case before?

We will surely fix this for 5.12.

-- 
Without us [Free Software developers], people would study computer science
and programming without ever having seen a real program in its entirety.
That's like becoming writers without ever having read a complete book.
  Matthias Ettrich, founder of the KDE project.
  http://www.efytimes.com/efytimes/25412/news.htm

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


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

Bug#916628: flrig: missing build dependency on pkg-config

[Adrian Bunk]

Source: flrig
Version: 1.3.41-1
Severity: serious
Tags: ftbfs

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

...
checking for fltk-config... /usr/bin/fltk-config
checking for fluid... no
./configure: line 6246: syntax error near unexpected token `X,'
./configure: line 6246: `PKG_CHECK_MODULES(X, x11, ac_cv_[]x=yes, 
ac_cv_[]x=no)'

Bug#916627: stretch-pu: package glx-alternatives/0.8.8~deb9u1

[Andreas Beckmann]

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

Hi,

I'd like to upgrade the non-free nvidia-graphics-drivers package in
stretch to the 390.xx legacy branch. As a prerequisite we need an
updated version of glx-alternatives to support the changed handling of
the libGLX_indirect.so.0 symlink. It also comes with some bugfixes.

The updated package has been in stretch-backports for quite some time
already.

This pu needs to go in together with the new driver version, as it
breaks the older driver version currently in stretch.


Andreas
diff --git a/debian/changelog b/debian/changelog
index d5e1a19..653f3bc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,44 @@
+glx-alternatives (0.8.8~deb9u1) stretch; urgency=medium
+
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sun, 16 Dec 2018 16:53:20 +0100
+
+glx-alternatives (0.8.8) unstable; urgency=medium
+
+  * glx-diversions: Put all packages that had shared libraries diverted into
+triggers-awaited state to ensure the triggers in glx-alternative-mesa
+setting up the glx alternative get processed earlier.  (Closes: #905908)
+  * Bump Standards-Version to 4.2.1. No changes needed.
+
+ -- Andreas Beckmann   Wed, 05 Sep 2018 12:04:55 +0200
+
+glx-alternatives (0.8.7) unstable; urgency=medium
+
+  * Update validation of the diverted libGL.so symlink.
+
+ -- Andreas Beckmann   Tue, 31 Jul 2018 17:27:59 +0200
+
+glx-alternatives (0.8.6) unstable; urgency=medium
+
+  * glx-alternative-mesa: libGLX_mesa.so.0 is not diverted and therefore not
+an indicator to install the alternative.  (Closes: #904486)
+
+ -- Andreas Beckmann   Thu, 26 Jul 2018 13:55:24 +0200
+
+glx-alternatives (0.8.5) unstable; urgency=medium
+
+  * Avoid confusing diagnostic message if no nvidia alternative is available.
+
+ -- Andreas Beckmann   Wed, 18 Jul 2018 19:30:23 +0200
+
+glx-alternatives (0.8.4) unstable; urgency=medium
+
+  * Add diversion and alternative for libGLX_indirect.so.0.
+  * Bump Standards-Version to 4.1.5. No changes needed.
+
+ -- Andreas Beckmann   Mon, 16 Jul 2018 16:26:25 +0200
+
 glx-alternatives (0.8.3~deb9u1) stretch; urgency=medium
 
   * Rebuild for stretch.
diff --git a/debian/control b/debian/control
index 316d36f..d69216a 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@ Uploaders:
 Build-Depends:
  debhelper (>= 9),
 Rules-Requires-Root: no
-Standards-Version: 4.1.3
+Standards-Version: 4.2.1
 Vcs-Browser: https://salsa.debian.org/nvidia-team/glx-alternatives
 Vcs-Git: https://salsa.debian.org/nvidia-team/glx-alternatives.git
 
@@ -60,6 +60,9 @@ Recommends:
  glx-diversions,
 Suggests:
  libgl1-mesa-glx | libgl1,
+Breaks:
+# libGLX_indirect.so.0 alternative
+ nvidia-alternative (<< 390.67-3~),
 Description: allows the selection of MESA as GLX provider
  In setups with several GLX providers (e.g. the free MESA implementation and
  proprietary graphics hardware vendor implementations) this metapackage
@@ -88,7 +91,7 @@ Breaks:
 # does not use the nvidia/bumblebee glx alternative
  bumblebee-nvidia (<< 3.2.1-10~),
 # old-style modprobe configuration snippets
- nvidia-alternative (<< 352.55),
+# nvidia-alternative (<< 352.55),
  nvidia-legacy-340xx-alternative (<< 340.93-2~),
  nvidia-legacy-304xx-alternative (<< 304.132-1~),
 # ancient drivers
@@ -96,6 +99,8 @@ Breaks:
  nvidia-alternative-legacy-173xx (<< 304),
  nvidia-alternative-legacy-96xx (<< 304),
  nvidia-alternative-legacy-71xx (<< 304),
+# libGLX_indirect.so.0 alternative
+ nvidia-alternative (<< 390.67-3~),
 Description: allows the selection of NVIDIA as GLX provider
  In setups with several GLX providers (e.g. the free MESA implementation and
  proprietary graphics hardware vendor implementations) this metapackage
diff --git a/debian/glx-alternative-mesa.postinst 
b/debian/glx-alternative-mesa.postinst
index 9625595..6c70db7 100644
--- a/debian/glx-alternative-mesa.postinst
+++ b/debian/glx-alternative-mesa.postinst
@@ -26,6 +26,7 @@ add_multiarch_slave()
source_dir="$4"
source_sub_dir="$5"
prefix="$6"
+   srcfile="${7:-$file}"
 
for triplet in $TRIPLETS ; do
# s|/$||; s|^/|-|;
@@ -34,7 +35,7 @@ add_multiarch_slave()
add_slave \
"${target_dir}${triplet}${target_sub_dir}${file}" \
"${prefix}${file}${suffix}" \
-   "${source_dir}${triplet}${source_sub_dir}${file}"
+   "${source_dir}${triplet}${source_sub_dir}${srcfile}"
done
 }
 
@@ -53,9 +54,13 @@ setup_alternatives()
$(add_multiarch_slave /usr/lib "" libGLESv1_CM.so.1 
/usr/lib/mesa-diverted)
$(add_multiarch_slave /usr/lib "" libGLESv2.so.2 
/usr/lib/mesa-diverted)
 "
+   slave_indirect=
+   if ! update-alternatives --query nvidia 2>/dev/null | grep -q 
nvidia--libGLX_indirect.so.0- ; then
+   slave_indirect="$(add_multiarch_slave