Bug#862604: dh-make-elpa: extending create_docs{}

[Lev Lamberov]

Пн 19 мар 2018 @ 20:43 Sean Whitton :
> On Sat, Mar 17 2018, Lev Lamberov wrote:
>
>> Please, find the patch attached.
>
> Thank you for working on this!
>
> If you've tested the patch and it works, please go ahead and apply to
> the repository and add a changelog entry closing this bug.

Done.

Do you think the bug should be closed? As I understand, this change is
what you'd like to have compared to a more complex change with multiple
docs files for multiple "binaries"?

Cheers!
Lev

Bug#893588: /boot/vmlinuz-4.9.0-6-amd64: JMicron JMS56x series USB 3.0 dock problems

[Sam Kuper]

Package: src:linux
Version: 4.9.82-1+deb9u3
Severity: normal
File: /boot/vmlinuz-4.9.0-6-amd64

Dear Maintainer,

I bought a Startech SDOCK2U33EB USB 3.0 / eSATA HDD dock (
https://www.startech.com/HDD/Docking/usb-3-esata-dual-drive-dock~SDOCK2U33EB).

I did not use the eSATA functionality of that dock. This bug report is
just about the USB functionality.

Under Jessie:

- when connected to a USB 2.0 socket, the dock worked fine as a USB
  2.0 to SATA bridge. I.e. it behaved as desired.

- when connected to a USB 3.0 socket, the dock defaulted to UASP mode
  and worked fine as a USB 3.0 to SATA bridge. I.e. it behaved as
  desired.

Under Stretch:

- when connected to a USB 2.0 socket, the dock worked fine as a USB
  2.0 to SATA bridge. I.e. it behaved as desired.

- when connected to a USB 3.0 socket, I expected the dock to work as it
  did when connected to a USB 3.0 socket on a Jessie machine. However,
  it instead behaved strangely. Even simply attempting to `cd` into a
  directory on an attached HDD resulted in indefinite wait that caused
  my terminal to hang.

Here are the relevant syslog messages from connection until removal of
the dock, with an 8TB HDD inserted:

```
Mar 19 16:29:45 zian1 kernel: [222139.487157] usb 2-1: new SuperSpeed
USB device number 2 using xhci_hcd
Mar 19 16:29:45 zian1 kernel: [222139.508151] usb 2-1: New USB device
found, idVendor=152d, idProduct=9561
Mar 19 16:29:45 zian1 kernel: [222139.508157] usb 2-1: New USB device
strings: Mfr=1, Product=2, SerialNumber=5
Mar 19 16:29:45 zian1 kernel: [222139.508160] usb 2-1: Product: JMS56x
Series
Mar 19 16:29:45 zian1 kernel: [222139.508162] usb 2-1: Manufacturer:
JMicron
Mar 19 16:29:45 zian1 kernel: [222139.508165] usb 2-1: SerialNumber:

Mar 19 16:29:45 zian1 kernel: [222139.511758] scsi host7: uas
Mar 19 16:29:45 zian1 kernel: [222139.512970] scsi 7:0:0:0:
Direct-Access ST8000AS 0002-1NA17Z  0107 PQ: 0 ANSI: 6
Mar 19 16:29:46 zian1 mtp-probe: checking bus 2, device 2:
"/sys/devices/pci:00/:00:14.0/usb2/2-1"
Mar 19 16:29:46 zian1 mtp-probe: bus: 2, device: 2 was not an MTP device
Mar 19 16:29:46 zian1 kernel: [222139.547815] sd 7:0:0:0: [sde]
15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
Mar 19 16:29:46 zian1 kernel: [222139.547819] sd 7:0:0:0: Attached scsi
generic sg4 type 0
Mar 19 16:29:46 zian1 kernel: [222139.548834] sd 7:0:0:0: [sde] Write
Protect is off
Mar 19 16:29:46 zian1 kernel: [222139.548839] sd 7:0:0:0: [sde] Mode
Sense: 67 00 10 08
Mar 19 16:29:46 zian1 kernel: [222139.549229] sd 7:0:0:0: [sde] Write
cache: enabled, read cache: enabled, supports DPO and FUA
Mar 19 16:29:46 zian1 kernel: [222139.572450] sd 7:0:0:0: [sde] Attached
SCSI disk
Mar 19 16:30:31 zian1 kernel: [222184.684857] sd 7:0:0:0: [sde] tag#0
uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
Mar 19 16:30:31 zian1 kernel: [222184.684865] sd 7:0:0:0: [sde] tag#0
CDB: Read(16) 88 00 00 00 00 00 00 00 11 10 00 00 00 f0 00 00
Mar 19 16:30:31 zian1 kernel: [222184.685020] scsi host7:
uas_eh_bus_reset_handler start
Mar 19 16:30:31 zian1 kernel: [222184.685088] usb 2-1: cmd cmplt err -2
Mar 19 16:30:31 zian1 kernel: [222184.805203] usb 2-1: reset SuperSpeed
USB device number 2 using xhci_hcd
Mar 19 16:30:31 zian1 kernel: [222184.826665] scsi host7:
uas_eh_bus_reset_handler success
Mar 19 16:31:01 zian1 systemd-udevd[413]: seq 2701
'/devices/virtual/block/dm-6' is taking a long time
Mar 19 16:31:01 zian1 kernel: [15.406024] sd 7:0:0:0: [sde] tag#2
uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN
Mar 19 16:31:01 zian1 kernel: [15.406032] sd 7:0:0:0: [sde] tag#2
CDB: Read(16) 88 00 00 00 00 03 a3 81 27 d8 00 00 00 28 00 00
Mar 19 16:31:01 zian1 kernel: [15.406163] sd 7:0:0:0: [sde] tag#1
uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
Mar 19 16:31:01 zian1 kernel: [15.406170] sd 7:0:0:0: [sde] tag#1
CDB: Read(16) 88 00 00 00 00 03 a3 81 27 28 00 00 00 a8 00 00
Mar 19 16:31:01 zian1 kernel: [15.406281] sd 7:0:0:0: [sde] tag#0
uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
Mar 19 16:31:01 zian1 kernel: [15.406289] sd 7:0:0:0: [sde] tag#0
CDB: Read(16) 88 00 00 00 00 03 a3 81 27 00 00 00 00 20 00 00
Mar 19 16:31:01 zian1 kernel: [15.406442] scsi host7:
uas_eh_bus_reset_handler start
Mar 19 16:31:01 zian1 kernel: [15.406492] usb 2-1: cmd cmplt err -2
Mar 19 16:31:01 zian1 kernel: [15.526147] usb 2-1: reset SuperSpeed
USB device number 2 using xhci_hcd
Mar 19 16:31:02 zian1 kernel: [15.547771] scsi host7:
uas_eh_bus_reset_handler success
Mar 19 16:31:02 zian1 udisksd[3921]: Unlocked LUKS device /dev/sde as
/dev/dm-6
Mar 19 16:31:02 zian1 kernel: [15.997256] EXT4-fs (dm-6): mounted
filesystem with ordered data mode. Opts: (null)
Mar 19 16:31:02 zian1 udisksd[3921]: Mounted /dev/dm-6 at
/media//8tb_02 on behalf of uid 1000
Mar 19 16:31:02 zian1 dbus-daemon[3762]: Activating service
name='org.gnome.Shell.HotplugSniffer'
Mar 19 16:31:02 zian1 dbus-daemon[3762]: Successfully 

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

[tony mancill]

On Sun, Mar 18, 2018 at 04:28:26PM +0100, gregor herrmann wrote:
> > > You can run
> > > JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> > Something is wrong here. Did openjdk-8 changed a bit?
> 
> Hm ...
>  
> > $ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> > Exception in thread "main" java.lang.NoSuchMethodError:
> > java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer; at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:292)
> > at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:303)
> > at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.closeOutputStream(OutputStreamManager.java:308)
> > at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.releaseSub(OutputStreamManager.java:137)
> > at
> > org.apache.logging.log4j.core.appender.AbstractManager.stop(AbstractManager.java:86)
> > at
> > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:142)
> > at
> > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:136)
> > at
> > org.apache.logging.log4j.core.config.AbstractConfiguration.stop(AbstractConfiguration.java:359)
> > at
> > org.apache.logging.log4j.core.AbstractLifeCycle.stop(AbstractLifeCycle.java:136)
> > at
> > org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:550)
> > at
> > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
> > at
> > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
> > at
> > org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
> > at
> > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
> > at
> > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
> > at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
> > at
> > org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122)
> > at
> > org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
> > at
> > org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46)
> > at
> > org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
> > at
> > org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
> > at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655) at
> > net.sf.jabref.JabRefMain.(JabRefMain.java:37)
> 
> Ouch, I have to confirm that I get the same errors.
> 
> Maybe that's caused by the recent update of liblog4j2-java 2.8.2-2 -> 2.10.0-1
> 
> Indeed, downgrading liblog4j2-java to 2.8.2-2 helps.
> 
> Not sure if this is a jabref problem or a liblog4j2-java issue; let's
> hope the java experts can shed some light on this bug.

Ouch indeed!  I'm pretty certain that this is an issue with how
liblog4j2-java is being built for Debian.  There is some discussion of
the issue here [1].  Basically, we need to take precautions when
building libraries with JDK 9 that are expected to run with JDK 8
runtimes.

That said, so far I'm not able to build a liblog4j2-java from the
2.10.0-1 source package that will play nicely with jabref, but I'll keep
looking at that and other options (aside from suggesting that we start
recommending a stretch chroot for jabref...)

Cheers,
tony

[1] https://github.com/plasma-umass/doppio/issues/497


signature.asc
Description: PGP signature

Bug#893587: ITP: peruse -- Comic book reader by KDE

[Simon Quigley]

Package: wnpp
Severity: wishlist
Owner: Simon Quigley 

* Package name: peruse
  Version : 1.2
  Upstream Author : Dan Leinir Turthra Jensen 
* URL : https://peruse.kde.org/
* License : GPL
  Programming Lang: C, C++, QML
  Description : Comic book reader by KDE

This is a simple comic book reader by KDE that supports a wide range of
formats.

I plan on maintaining this package under the Qt/KDE Team umbrella.

--
Simon Quigley
tsimo...@ubuntu.com
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4



signature.asc
Description: OpenPGP digital signature

Bug#892431: AppArmor denies access for libvirt to nova instances directory

[aradian]

On 2018-03-18 11:00, intrigeri wrote:

Thanks for the bug report + debugging + solution!
I'm reassigning to the package that ships the faulty profile.

Let's submit this to libvirt upstream
(https://www.redhat.com/mailman/listinfo/libvir-list). Do you want to
do it yourself or shall I?


It might be best if you could do that, since you're probably much more 
familiar with the interaction between AppArmor and libvirt (and the 
bug-reporting process) than I am.



Now, one question before we move this upstream: does virt-aa-helper
really need write access to /var/lib/nova/instances/**?
Knowing a little bit what this helper does, I can't imagine why it
would; and in your logs I see only denied_mask="r".



You're right. I did some testing and found that only one rule needed 
(for QCOW backing files):


/var/lib/nova/instances/_base/* r

It seems the instance disk images are covered by the existing rule:

/**/disk{,.*} r

Probably it would be more appropriate to put that in a separate 
profile?


I think it's fine to add these lines to usr.lib.libvirt.virt-aa-helper.



OK. I wasn't sure, since these rules are specific to Nova.

Bug#893586: pioneers FTCBFS: does not pass --host to ./configure

[Helmut Grohne]

Source: pioneers
Version: 15.5-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

pioneers fails to cross build from source, because it does not pass
--host to ./configure. It does so, because it runs ./configure through
./autogen.sh as that's convenient. We can disable that feature by
setting NOCONFIGURE and then letting dh_auto_configure do its job. After
doing so, pioneers cross builds successfully. Please consider applying
the attached patch.

Helmut
diff --minimal -Nru pioneers-15.5/debian/changelog 
pioneers-15.5/debian/changelog
--- pioneers-15.5/debian/changelog  2018-03-14 17:44:00.0 +0100
+++ pioneers-15.5/debian/changelog  2018-03-20 06:04:25.0 +0100
@@ -1,3 +1,10 @@
+pioneers (15.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass its flags. (closes: #-1)
+
+ -- Helmut Grohne   Tue, 20 Mar 2018 06:04:25 +0100
+
 pioneers (15.5-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru pioneers-15.5/debian/rules pioneers-15.5/debian/rules
--- pioneers-15.5/debian/rules  2018-03-07 16:58:25.0 +0100
+++ pioneers-15.5/debian/rules  2018-03-20 06:04:24.0 +0100
@@ -9,7 +9,8 @@
dh $@
 
 override_dh_auto_configure:
-   ./autogen.sh --prefix=/usr --bindir=/usr/games --mandir=/usr/share/man \
+   NOCONFIGURE=1 ./autogen.sh
+   dh_auto_configure -- --bindir=/usr/games \
--enable-warnings \
--disable-dependency-tracking \
--disable-deprecation-checks

Bug#893564: dmidecode has priority important

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Christian,

thank you for spending your time helping to make Debian better with
this bug report.

Dmidecode is used at install to dectect the hardware, e.g. a laptop.

Therefore, the priority of the Debian Policy is prescribed.

CU
Jörg 


- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlqwl6AACgkQCfifPIyh
0l0uDhAAk7/mToSOMGfJJKL9dAAS6ARWqXhGbJe84N19LQN6Ygja4Wpc0NoR4K3k
0QV2irCxU8x1j3wpBRJ3eg9cxKIxnSg5xcDUQIghnY7CXXtbGlM2UicKU5HnDgMi
ZtyQIZSd+m1mqKK8cYMzG+nJTTK/xDcQHBHUdkq5jKizciNzoJHxSm9kZM084ozd
l9djI4uCTtF4YpTqY+wQPZHQAJPNV/YgkxL0AGnJvo73YdwVmtrWfp5YbFYRlZYR
eaJnWBAmc1waq8T74mXpYTJ2fvkI9ZjiUji5ELSXEjtnOzptHkpP9DYwJH+Rl6hg
x3QrngUAXV2lyAvJauDZVdGEnj72nzKve9D+Hls1sc2096zCrt7tE6z1sE1rmztL
zj63b92g/sC0nafwaOBK+Mw1uoZAZdzjwuEEvXq2PG3aARZ98nDvveXe/uuirL1N
iQwhZELmTi2EhTXHib9yZwicwiTNuQPyXEP36s32BKYeWCH8MvkII4OX1tGNnYgV
/G5ADyuc2K3hSx36zmihl74v96i7mw1om+59TSgjMtM8EhX0vkqvu8KcSkFu0DZk
GIKhsq//hTHmlmI55lR06IXW3FS+myvXH19x6EZHmJps6iBw1vHKfeLhwEUGVdCP
VoCDKhRH6dDbVY4UT8Q/oLmi4e7p6ZraOqZcDgGVbwzG+qmQqG8=
=/z8d
-END PGP SIGNATURE-

Bug#889872: show-ip: load fails: TypeError: Object is NM.IPAddress.prototype, not an object instance - cannot convert to a boxed instance

[Paul Wise]

Control: tags -1 + fixed-upstream
Control: forwarded -1 
https://github.com/sgaraud/gnome-extension-show-ip/commit/a2857aea4a38bb7737e1954e2bca20c35959156b

On Tue, 20 Feb 2018 16:03:37 +0800 Paul Wise wrote:

> Hmm, I'll try it with a fresh user account.

I still get the same error with a fresh user account:

Mar 20 12:55:29 chianamo gnome-shell[3054]: 
((libnm-core/nm-setting-ip-config.c:210)): assertion '' failed
Mar 20 12:55:29 chianamo gnome-shell[3054]: 
((libnm-core/nm-setting-ip-config.c:210)): assertion '' failed
Mar 20 12:55:29 chianamo gnome-shell[3054]: Extension 
"show...@sgaraud.github.com" had error: TypeError: Object is 
NM.IPAddress.prototype, not an object instance - cannot convert to a boxed 
instance

Looks like this was fixed upstream, see the URL above.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#875346: checkstyle no longer FTBFS due to tools.jar

[tony mancill]

Since the update of checkstyle to 8.8 which includes this upstream fix
[1], tools.jar is no longer an issue.  However, it is affected by the
ant javadoc "--ignore-source-errors" issue (same as 893530 [2]).

I'm inclined to close this bug in favor of a new one to track the
javadoc problem.

Cheers,
tony

[1] https://github.com/checkstyle/checkstyle/issues/2905
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893530


signature.asc
Description: PGP signature

Bug#893585: ITP: ruby-sshkey -- SSH private/public key generator in Ruby

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

from rubygems.org/gems/sshkey

dependency of gitlab 10.6















signature.asc
Description: OpenPGP digital signature

Bug#893584: gource FTCBFS: broken embedded copy of AX_BOOST_SYSTEM

[Helmut Grohne]

Source: gource
Version: 0.47-1
User: helm...@debian.org
Usertags: rebootstrap

gource fails to cross build from source, because it ships a broken
embedded copy of AX_BOOST_SYSTEM. The problem in the macro is described
at https://bugs.debian.org/872256. Please remove embedded copies or get
them registered, see https://wiki.debian.org/EmbeddedCodeCopies. Most
likely, it is sufficient to rm m4/ax_boost_*.m4 before autoreconf.

Helmut

Bug#893547: ant: please do not emit --ignore-source-errors on Java 9

[tony mancill]

On Mon, Mar 19, 2018 at 09:16:24PM +0100, Ole Streicher wrote:
> Package: ant
> Version: 1.9.9-6
> Severity: serious
> 
> Dear maintainer,
> 
> to fix #884187, ant added the option "--ignore-source-errors" to
> javadoc. This option is however not available on Java 9, which leads to
> FTBFS on some packages: starjava-topcat, starjava-tools. I will merge
> the relevant bug reports.

Ah, this is also the cause for the current FTBFS state of checkstyle.

I'm in the midst of preparing an update for ant.  Is there any context
in which we want to add "--ignore-source-errors" to the ant javadoc
task, or should this patch [1] be removed entirely?

Thanks,
tony

[1] 
https://anonscm.debian.org/cgit/pkg-java/ant.git/commit/debian/patches/0013-auto-adjust-target.patch?id=2897cc4feed5a7d5bb431096602efecd143c0a78


signature.asc
Description: PGP signature

Bug#893583: linssid FTCBFS: upstream build system forces the build architecture compiler

[Helmut Grohne]

Source: linssid
Version: 2.9-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

linssid fails to cross build from source, because the upstream build
system forces the build architecture compiler. After removing the bad
assignments it cross builds successfully. Please consider applying the
attached patch.

Helmut
Index: linssid-2.9/linssid-app/linssid-app.pro
===
--- linssid-2.9.orig/linssid-app/linssid-app.pro
+++ linssid-2.9/linssid-app/linssid-app.pro
@@ -15,8 +15,6 @@
 MOC_DIR = 
 RCC_DIR = 
 UI_DIR = 
-QMAKE_CC = gcc
-QMAKE_CXX = g++
 DEFINES += 
 INCLUDEPATH += /usr/include/boost
 INCLUDEPATH += /usr/include/qt5

Bug#893573: auto-apt-proxy: autopkgtest assumes clean proxy environment

[Steve Langasek]

Package: auto-apt-proxy
Version: 8
Followup-For: Bug #893573
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Take two of the patch, now with valid shell syntax. ;)

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru auto-apt-proxy-8/debian/tests/apt-integration 
auto-apt-proxy-8ubuntu2/debian/tests/apt-integration
--- auto-apt-proxy-8/debian/tests/apt-integration   2017-11-27 
07:50:22.0 -0800
+++ auto-apt-proxy-8ubuntu2/debian/tests/apt-integration2018-03-19 
20:50:40.0 -0700
@@ -2,6 +2,11 @@
 
 set -eu
 
+if [ -n "$no_proxy" ]; then
+   echo "no_proxy variable is set, skipping test"
+   exit 0
+fi
+
 cd ${AUTOPKGTEST_TMP:-/tmp}
 apt-get source auto-apt-proxy
 

Bug#893508: qtcreator: please use dh_auto_configure

[Helmut Grohne]

On Mon, Mar 19, 2018 at 10:30:31PM +0100, Pino Toscano wrote:
> In data lunedì 19 marzo 2018 15:10:43 CET, Helmut Grohne ha scritto:
> > diff --minimal -Nru qtcreator-4.5.2/debian/rules 
> > qtcreator-4.5.2/debian/rules
> > --- qtcreator-4.5.2/debian/rules2018-03-17 17:26:40.0 +0100
> > +++ qtcreator-4.5.2/debian/rules2018-03-19 14:37:33.0 +0100
> > @@ -5,15 +5,6 @@
> >  
> >  DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
> >  
> > -export CFLAGS := $(shell dpkg-buildflags --get CFLAGS) $(shell 
> > dpkg-buildflags --get CPPFLAGS)
> > -export CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS) $(shell 
> > dpkg-buildflags --get CPPFLAGS)
> > -export LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS) -Wl,--as-needed
> 
> Your patch drops the as-needed linking mode.

Yes, it does so intentionally. I checked the build logs (on amd64) and
saw that the qmake debhelper build system passes -Wl,--as-needed anyway.
Thus I concluded that explicit passing was unnecessary. Is there
anything I could miss here?

Regarding Lisandro's complaint regarding out-of-source builds: dh
forwards the --builddirectory to dh_auto_configure. It's still
out-of-source.

Helmut

Bug#893582: telepathy-accounts-signon FTCBFS: uses the build architecture compiler as linker

[Helmut Grohne]

Source: telepathy-accounts-signon
Version: 1.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

telepathy-accounts-signon fails to cross build from source, because it
uses the build architecture compiler as linker. It does so via
QMAKE_LINK_C, which is not supplied by debhelper unlike other tools such
as QMAKE_CC. Dmitry Shachnev said that only two packages need
QMAKE_LINK_C, so I'm suggesting that we provide that variable here.
Please consider applying the attached patch.

Helmut
diff --minimal -Nru telepathy-accounts-signon-1.0/debian/changelog 
telepathy-accounts-signon-1.0/debian/changelog
--- telepathy-accounts-signon-1.0/debian/changelog  2015-09-19 
23:45:41.0 +0200
+++ telepathy-accounts-signon-1.0/debian/changelog  2018-03-20 
04:26:48.0 +0100
@@ -1,3 +1,10 @@
+telepathy-accounts-signon (1.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass QMAKE_LINK_C to qmake. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 20 Mar 2018 04:26:48 +0100
+
 telepathy-accounts-signon (1.0-1) unstable; urgency=low
 
   [ Rohan Garg ]
diff --minimal -Nru telepathy-accounts-signon-1.0/debian/rules 
telepathy-accounts-signon-1.0/debian/rules
--- telepathy-accounts-signon-1.0/debian/rules  2015-09-19 23:45:23.0 
+0200
+++ telepathy-accounts-signon-1.0/debian/rules  2018-03-20 04:25:55.0 
+0100
@@ -2,11 +2,15 @@
 #export DH_VERBOSE = 1
 
 include /usr/share/dpkg/default.mk
+-include /usr/share/dpkg/buildtools.mk
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 export QT_SELECT=qt5
 
 %:
dh $@ --buildsystem qmake
 
+override_dh_auto_configure:
+   dh_auto_configure -- 'QMAKE_LINK_C=$(CC)'
+
 override_dh_install:
dh_install --list-missing

Bug#862604: dh-make-elpa: extending create_docs{}

[Sean Whitton]

Hello Lev,

On Sat, Mar 17 2018, Lev Lamberov wrote:

> Please, find the patch attached.

Thank you for working on this!

If you've tested the patch and it works, please go ahead and apply to
the repository and add a changelog entry closing this bug.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#893581: qpdf: rules calls dh_missing but build dependency requires only debhelper 10

[Sean Whitton]

Package: qpdf
Version: 8.0.2-1
Severity: normal

Dear maintainer,

qpdf's debian/rules calls dh_missing, which was introduced in debhelper
10.3.  However, qpdf declares a build-dependency only on debhelper (>> 10~).

Please tighten this build dependency to reflect the use of dh_missing.

I note that this blocks a clean backport of qpdf to stretch.

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: i386 (i686)

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

Versions of packages qpdf depends on:
ii  libc62.24-11+deb9u1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libqpdf187.1.1-1~bpo9+1
ii  libstdc++6   6.3.0-18+deb9u1
ii  zlib1g   1:1.2.8.dfsg-5

qpdf recommends no packages.

qpdf suggests no packages.

-- no debconf information

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#893580: ITP: keystone-engine -- Lightweight multi-architecture assembler framework

[Christian Sharpsten]

Package: wnpp
Severity: wishlist
Owner: Christian Sharpsten 

* Package name: keystone-engine
  Version : 0.9.1
  Upstream Author : Nguyen Anh Quynh 
* URL : http://www.keystone-engine.org/
* License : GPL-2
  Programming Lang: C, C++
  Description : Lightweight multi-architecture assembler framework

 Keystone is a lightweight multi-platform, multi-architecture assembler
 framework.
 .
 Features:
  - Supports hardware architectures: ARM, ARM64 (AArch64/Armv8), Hexagon, Mips,
 PowerPC, Sparc, SystemZ, & X86 (16/32/64bit).
  - Clean/simple/lightweight/intuitive architecture-neutral API.
  - Implemented in C/C++ languages, with bindings for Masm, Visual Basic, C#,
 PowerShell, Perl, Python, NodeJS, Ruby, Go, Rust, Haskell & OCaml available.
  - Native support for Windows & *nix (with Mac OSX, Linux, *BSD & Solaris
 confirmed).
  - Thread-safe by design.

I use this package regularly and it provides an easy to use assembler that can
be called from multiple source languages. I plan to maintain it myself and
will need a sponsor as this is my first package.

Bug#893464: RM: gcompris -- RoQA; dead upstream, replaced by src:gcompris-qt

[Jeremy Bicha]

Control: tags -1 moreinfo

I am setting the moreinfo tag since this removal can't be processed
until the blocking bug is fixed.

Thanks,
Jeremy Bicha

Bug#893285: stretch-pu: package docbook-to-man/1:2.0.0-35+deb9u1

[Chris Lamb]

retitle 893285 stretch-pu: package docbook-to-man/1:2.0.0-35+deb9u1
reassign 893285 release.debian.org
severity 893285 normal
tags 893285 + stretch
user release.debian@packages.debian.org
usertags 893285 pu
thanks

Hi,

I'd like update docbook-to-man in stable to fix an issue with corrupted
output due to incorrect use of memcpy vs memmove as originally outlined
in #842635 and #858389

The diff is attached (modulo the changelog entry), but just to quote the
relevant portion here:

  --- a/Instant/main.c
  +++ b/Instant/main.c
  @@ -796,7 +796,7 @@ ReadESIS(
if ( ! buf[2] )
break;
buf[0] = ' ';
  - memcpy([1], [2], strlen(buf)-1);
  + memmove([1], [2], strlen(buf)-1);
}
   
cont[ncont].ch.data = strdup(buf);

(This would also make a number of packages reproducible.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for docbook-to-man-2.0.0 docbook-to-man-2.0.0

 12-Prevent-undefined-behaviour-in-memcpy-parameter-over.patch |   29 ++
 series|1 
 2 files changed, 30 insertions(+)

diff -Nru 
docbook-to-man-2.0.0/debian/patches/12-Prevent-undefined-behaviour-in-memcpy-parameter-over.patch
 
docbook-to-man-2.0.0/debian/patches/12-Prevent-undefined-behaviour-in-memcpy-parameter-over.patch
--- 
docbook-to-man-2.0.0/debian/patches/12-Prevent-undefined-behaviour-in-memcpy-parameter-over.patch
   1969-12-31 19:00:00.0 -0500
+++ 
docbook-to-man-2.0.0/debian/patches/12-Prevent-undefined-behaviour-in-memcpy-parameter-over.patch
   2016-09-17 21:03:42.0 -0400
@@ -0,0 +1,29 @@
+From: Chris Lamb 
+Date: Fri, 12 May 2017 10:58:54 +0200
+Subject: Prevent undefined behaviour in memcpy parameter overlap.
+
+On i386 (but not armhf or amd64), docbook-to-man inserts random
+characters into the output. e.g. it will sometimes generate an "I"
+instead of a literal tab.
+
+Thanks to Chris West  and Yuri Gribov
+
+
+Debian-Bugs: #842635 #858389
+---
+ Instant/main.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/Instant/main.c b/Instant/main.c
+index 64a5e96..0341670 100644
+--- a/Instant/main.c
 b/Instant/main.c
+@@ -796,7 +796,7 @@ ReadESIS(
+   if ( ! buf[2] )
+   break;
+   buf[0] = ' ';
+-  memcpy([1], [2], strlen(buf)-1);
++  memmove([1], [2], strlen(buf)-1);
+   }
+ 
+   cont[ncont].ch.data = strdup(buf);
diff -Nru docbook-to-man-2.0.0/debian/patches/series 
docbook-to-man-2.0.0/debian/patches/series
--- docbook-to-man-2.0.0/debian/patches/series  2016-09-17 21:03:42.0 
-0400
+++ docbook-to-man-2.0.0/debian/patches/series  2016-09-17 21:03:42.0 
-0400
@@ -7,3 +7,4 @@
 07-remove-timestamp.patch
 10-better-checking-of-return-value-of-Split-function.patch
 11-remove-sp-dependency.patch
+12-Prevent-undefined-behaviour-in-memcpy-parameter-over.patch

Bug#893508: qtcreator: please use dh_auto_configure

[Lisandro Damián Nicanor Pérez Meyer]

El 19 mar. 2018 6:33 p.m., "Pino Toscano"  escribió:

In data lunedì 19 marzo 2018 15:10:43 CET, Helmut Grohne ha scritto:
> diff --minimal -Nru qtcreator-4.5.2/debian/rules
qtcreator-4.5.2/debian/rules
> --- qtcreator-4.5.2/debian/rules2018-03-17 17:26:40.0
+0100
> +++ qtcreator-4.5.2/debian/rules2018-03-19 14:37:33.0
+0100
> @@ -5,15 +5,6 @@
>
>  DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
>
> -export CFLAGS := $(shell dpkg-buildflags --get CFLAGS) $(shell
dpkg-buildflags --get CPPFLAGS)
> -export CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS) $(shell
dpkg-buildflags --get CPPFLAGS)
> -export LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS) -Wl,--as-needed

Your patch drops the as-needed linking mode.


Good catch. I'll have to revert the patch then.

Bug#791445: ceph: uses bundled "libjerasure" library again

[Shengjing Zhu]

Source: ceph
Followup-For: Bug #791445
X-Debbugs-CC: z...@debian.org

Dear Maintainer,

Things are getting better now, upstream gf-complete now supports runtime
SIMD detection, 
http://lab.jerasure.org/jerasure/gf-complete/commit/4339569f14c95a8895a347845f8ed6e18b345ace

And ceph since 11.0.1 replies on this feature, and removed the multiple
versions jerasure for different CPU.
https://github.com/ceph/ceph/pull/11086

The legacy .so names(libec_jerasure_xx.so) are still there for
compatibility. But they just give warning and use the runtime detection
one.

Now we're preparing Ceph 12.x release, I suggest we unbundle it again.

For gf-complete, since upstream doesn't have a tag for the new version,
I'll ask the maintainers to bump to a snapshot(so CC zigo here).


signature.asc
Description: PGP signature

Bug#893324: diffoscope: terminology used in docs about exclusion options

[Paul Wise]

On Mon, 2018-03-19 at 07:46 +, Holger Levsen wrote:

> "Exclude/ignore" doesnt read nicely. Given the option is called
> 'exclude...' already, we could probably just explain that this causing
> 'ignore', so people will still find it using both terms.

How about removing the "/ignore" and adding sentences like these:

Use this option to ignore files based on their names.
Use this option to disable commands that use a lot of resources.
Use this option to ignore permissions, timestamps, xattrs etc.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#893579: cron.8: Some fixes in the manual

[Bjarni Ingi Gislason]

Package: cron
Version: 3.0pl1-130
Severity: minor
Tags: patch

Dear Maintainer,

  (The patch is in the attachment.)

Input file is cron.8

mandoc: cron.8:17:4: STYLE: whitespace at end of input line
mandoc: cron.8:19:4: STYLE: whitespace at end of input line
mandoc: cron.8:48:16: STYLE: whitespace at end of input line
mandoc: cron.8:83:27: STYLE: whitespace at end of input line
mandoc: cron.8:92:62: STYLE: whitespace at end of input line
mandoc: cron.8:94:72: STYLE: whitespace at end of input line
mandoc: cron.8:96:38: STYLE: whitespace at end of input line
mandoc: cron.8:108:76: STYLE: whitespace at end of input line
mandoc: cron.8:111:62: STYLE: whitespace at end of input line
mandoc: cron.8:114:18: STYLE: whitespace at end of input line
mandoc: cron.8:129:7: STYLE: whitespace at end of input line
mandoc: cron.8:145:68: STYLE: whitespace at end of input line
mandoc: cron.8:159:30: STYLE: whitespace at end of input line
mandoc: cron.8:160:16: STYLE: whitespace at end of input line
mandoc: cron.8:167:75: STYLE: whitespace at end of input line
mandoc: cron.8:179:51: STYLE: whitespace at end of input line
mandoc: cron.8:193:34: STYLE: whitespace at end of input line
mandoc: cron.8:222:57: STYLE: whitespace at end of input line
mandoc: cron.8:225:66: STYLE: whitespace at end of input line
mandoc: cron.8:228:12: STYLE: whitespace at end of input line
mandoc: cron.8:236:3: STYLE: whitespace at end of input line
mandoc: cron.8:240:58: STYLE: whitespace at end of input line
mandoc: cron.8:241:17: STYLE: whitespace at end of input line
mandoc: cron.8:245:82: STYLE: whitespace at end of input line
mandoc: cron.8:254:9: STYLE: whitespace at end of input line
mandoc: cron.8:261:59: STYLE: whitespace at end of input line
mandoc: cron.8:262:54: STYLE: whitespace at end of input line
mandoc: cron.8:266:34: STYLE: whitespace at end of input line
mandoc: cron.8:268:18: STYLE: whitespace at end of input line
mandoc: cron.8:269:7: STYLE: whitespace at end of input line
mandoc: cron.8:271:23: STYLE: whitespace at end of input line
mandoc: cron.8:276:10: STYLE: whitespace at end of input line
mandoc: cron.8:281:83: STYLE: whitespace at end of input line
mandoc: cron.8:286:35: STYLE: whitespace at end of input line
mandoc: cron.8:292:37: STYLE: whitespace at end of input line
mandoc: cron.8:294:74: STYLE: whitespace at end of input line
mandoc: cron.8:295:26: STYLE: whitespace at end of input line
mandoc: cron.8:303:43: STYLE: whitespace at end of input line
mandoc: cron.8:20:12: WARNING: cannot parse date, using it verbatim: 19 April 
2010

###

Input file is cron.8

Test nr. 1:

Remove space at end of lines to simplify other automatic tests to improve
typesetting.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

17:.\" 
19:.\" 
48:.B -L loglevel 
83:Debian, see the note under 
92:follow the special format of that file, i.e. they include the 
94:field). However, they are independent of /etc/crontab: they do not, for 
96:specific to Debian see the note under 
108:provided that both the symlink and the file it points to are owned by root. 
111:/etc/cron.weekly and /etc/cron.monthly do, as they are run by 
114:.IR run-parts(8) 
129:on the 
145:run in the time that was skipped will be run soon after the change. 
159:controlled using the standard 
160:.IR syslogd(8) 
167:daemon localisation settings environment can be managed through the use of 
179:on how to modify the environment of tasks, consult 
193:Debian introduces some changes to 
222:of the /etc/crontab file (see the system-wide example in 
225:day, every week and every month. Each of these tasks will execute 
228:.B anacron 
236:of 
240:not conform to these requirements will not be executed by 
241:.BR run-parts . 
245:/etc/cron.d/ as configuration files (i.e. files ending in .dpkg-dist, 
.dpkg-orig, 
254:.I cron 
261:(they are configuration files, just like /etc/crontab) and 
262:must conform to the same naming convention as used by 
266:and hyphens. This means that they 
268:contain any dots. 
269:If the 
271:option is specified to 
276:option in 
281:finer control of their scheduling than the 
/etc/cron.{hourly,daily,weekly,monthly} 
286:Also, the default configuration of 
292:daemon. This file determines whether 
294:will read the system's environment variables and makes it possible to add 
295:additional options to the 
303:Paul Vixie  is the author of 

#

Test nr. 2:

Enable and fix warnings from 'test-groff'.

Input file is /tmp/cron.8

:114 (macro IR): only 1 argument, but more are expected
:130 (macro IR): only 1 argument, but more are expected
:160 (macro IR): only 1 argument, but more are expected
:180 (macro IR): only 1 argument, but more are expected

chk_manuals: Output is from: test-groff -Tutf8 -b -e -mandoc -rF0 -t -w w -z 




#

Test nr. 8:

Protect a full stop (.) with "\&", if it has a blank (white-space) in front
of or (ignoring transparent characters to 

Bug#892810: RFS: zeroc-ice/3.7.0-1 -- New Ice 3.7.0 release

[Adam Borowski]

On Mon, Mar 19, 2018 at 09:17:32PM +0100, Jose Gutierrez de la Concha wrote:
> I have fixed the package to depend on JDK 8 and use it for the build,
> there is already a bug to upgrade gradle for JDK 9 support [1]
> 
> I have also fixed a few other warnings that show up with lintian and have
> to reimort the upstream source to exclude some non DFSG files
> 
> [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873227

I'm afraid that the new version loses a lot of entries from the changelog.
I haven't checked yet whether the actual changes are preserved, but even
lacking just the changelog will confuse BTS version tracking, making it
consider past bugs to still apply to the new version.


-zeroc-ice (3.6.4-1+buster) unstable; urgency=medium
+zeroc-ice (3.7.0-1) unstable; urgency=medium
 
-  * Removed icegridgui patch, no longer necessary with 3.6.4
-  * Set iceBuilderClassPath to use the local Ice Builder plug-in
-  * Add class path entries to JAR files
-  * Renamed zeroc-icegrid.icegridnode.service
-  * Enable jarsClassPath see ICE-8444
-  * Imported Upstream version 3.6.4
+  * Updated version to 3.7.0
 
- -- José Gutiérrez de la Concha   Fri, 08 Sep 2017 20:36:13 
+0200
-
-zeroc-ice (3.6.3-6) unstable; urgency=medium
-
-  * Add python2 packages
-  * Update obsolete standards version
-  * Fix usage of deprecated operator < in dependencies
-  * Update .gitignore file
-  * Rebuild libzeroc-ice3.6 with G++ 7 and bump symbols
-  * Update git-buildpackage configuration for 3.6-sid branch
-
- -- José Gutiérrez de la Concha   Thu, 10 Aug 2017 10:48:29 
+
-
-zeroc-ice (3.6.3-5) unstable; urgency=medium
-
-  * Do not install libIceStormService.so (Closes: #857219)
-  * Fix libzeroc-ice3.6-java install to use 3.6 name
-
- -- Jose   Thu, 09 Mar 2017 16:22:39 +0100
-
-zeroc-ice (3.6.3-4) unstable; urgency=medium
-
-  * Move javahelper to Build-Depends to fix Bug#847010
-
- -- Jose   Mon, 05 Dec 2016 09:37:57 +0100
-
-zeroc-ice (3.6.3-3) unstable; urgency=medium
-
-  * Missing Jgoodies dependencies in zeroc-icegridgui
-  * Do not use JGoodies PlasticLookAndFeel. We avoid using
-JGoodies PlasticLookAndFeel as it is triggering a
-bug in JFileChooser that causes an application crash
-
- -- Jose   Thu, 01 Dec 2016 22:39:10 +0100
-
-zeroc-ice (3.6.3-2) unstable; urgency=medium
-
-  * Fix package upgrade from stretch
-
- -- Jose   Fri, 14 Oct 2016 17:26:35 +
-
-zeroc-ice (3.6.3-1) unstable; urgency=medium
-
-  * Ice-3.6.3 release
-  * Added Ice for Python package python3-zeroc-ice
-  * Remove javafx dependency
-  * Fix service packaging
-
- -- José Gutiérrez de la Concha   Tue, 11 Oct 2016 13:21:56 
+0200
+ -- José Gutiérrez de la Concha   Mon, 19 Mar 2018 17:35:41 
+


It'd be also nice to fix problems reporting by lintian:
W: zeroc-ice source: debian-rules-ignores-make-clean-error line 126
W: zeroc-icegridgui: classpath-contains-relative-path 
usr/share/java/icegridgui.jar:
file:/usr/share/java/ice-3.7.0.jar,
file:/usr/share/java/icessl-3.7.0.jar,
file:/usr/share/java/icelocatordiscovery-3.7.0.jar,
file:/usr/share/java/icebox-3.7.0.jar,
file:/usr/share/java/icestorm-3.7.0.jar,
file:/usr/share/java/glacier2-3.7.0.jar,
file:/usr/share/java/icegrid-3.7.0.jar,
file:/usr/share/maven-repo/com/jgoodies/jgoodies-looks/debian/jgoodies-looks-debian.jar,
file:/usr/share/maven-repo/com/jgoodies/jgoodies-forms/debian/jgoodies-forms-debian.jar,
file:/usr/share/maven-repo/com/jgoodies/jgoodies-common/1.x/jgoodies-common-1.x.jar
W: libzeroc-ice3.7: dev-pkg-without-shlib-symlink 
usr/lib/x86_64-linux-gnu/libIceXML.so.3.7.0 
usr/lib/x86_64-linux-gnu/libIceXML.so
W: libzeroc-ice3.7: dev-pkg-without-shlib-symlink 
usr/lib/x86_64-linux-gnu/libIceDB.so.3.7.0 usr/lib/x86_64-linux-gnu/libIceDB.so
W: libzeroc-ice3.7: dev-pkg-without-shlib-symlink 
usr/lib/x86_64-linux-gnu/libGlacier2CryptPermissionsVerifier.so.3.7.0 
usr/lib/x86_64-linux-gnu/libGlacier2CryptPermissionsVerifier.so


Also, FYI: the new version makes your only reverse-dependence, mumble,
fail to build (full log attached):

slice2cpp --checksum -I/usr/local/share/Ice -I/usr/share/Ice/slice 
-I/usr/share/slice -I/usr/share/Ice-3.4.1/slice/ -I/usr/share/Ice-3.3.1/slice/ 
-I/usr/share/Ice-3.4.2/slice/ Murmur.ice
[libprotobuf WARNING google/protobuf/compiler/parser.cc:547] No syntax 
specified for the proto file: Mumble.proto. Please use 'syntax = "proto2";' or 
'syntax = "proto3";' to specify a syntax version. (Defaulted to proto2 syntax.)
/<>/src/murmur/Murmur.ice:9: error: Can't open include file 
"Ice/SliceChecksumDict.ice"
#include 

Obviously, you first need to get the new version of zeroc in, but the
transition will need to take care of mumble, thus the heads up.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.

Bug#893578: [zfs-linux] Please package 0.7.7

[Antonio Russo]

Package: zfs-linux
Version: 0.7.6-1
Severity: normal
Tags: patch

--- Please enter the report below this line. ---

0.7.7 [1] adds official support for Linux 4.16, in addition to
addressing several longstanding issues. Packaging it ahead of
Debian release of 4.16 would ease the transition for users.

The new release adds a file enum-extract.pl that must be
installed alongside the DKMS source. The attached patch
works for DKMS builds (though I have not tested any other
kernel module build styles).

[1] https://github.com/zfsonlinux/zfs/releases
commit 0ae71a1b149a1589c766270391e160781a916ff7
Author: Antonio Russo 
Date:   Sun Feb 25 21:18:10 2018 -0500

Install enum-extract.pl with dkms

diff --git a/debian/not-installed b/debian/not-installed
index f54fe731..a008985c 100644
--- a/debian/not-installed
+++ b/debian/not-installed
@@ -1,3 +1,4 @@
+usr/share/zfs/enum-extract.pl
 usr/share/zfs/zfs-helpers.sh
 etc/init.d
 etc/sudoers.d
diff --git a/debian/rules b/debian/rules
index cc47a74a..f74e18de 100755
--- a/debian/rules
+++ b/debian/rules
@@ -80,7 +80,8 @@ override_dh_auto_install:
 
 	@# Install the DKMS source.
 	@# We only want the files needed to build the modules
-	mkdir -p '$(CURDIR)/debian/tmp/usr/src/$(NAME)-$(DEB_VERSION_UPSTREAM)'
+	mkdir -p '$(CURDIR)/debian/tmp/usr/src/$(NAME)-$(DEB_VERSION_UPSTREAM)/scripts'
+	cp '$(CURDIR)/scripts/enum-extract.pl' '$(CURDIR)/debian/tmp/usr/src/$(NAME)-$(DEB_VERSION_UPSTREAM)/scripts'
 	$(foreach file,$(DKMSFILES),mv '$(CURDIR)/$(NAME)-$(DEB_VERSION_UPSTREAM)/$(file)' '$(CURDIR)/debian/tmp/usr/src/$(NAME)-$(DEB_VERSION_UPSTREAM)' || exit 1;)
 	@# Hellish awk line:
 	@#  * Deletes from configure.ac the parts not needed for building the kernel module

Bug#891391: ITP: python-hsluv -- Python implementation of HSLuv (Human-friendly HSL)

[Paul Wise]

On Tue, 2018-03-20 at 08:39 +0800, Yao Wei (魏銘廷) wrote:

> In the screenshot provided in the issue the code seems to be pretty
> different, so I am wondering that does it count as an
> "reimplementation" of hsluv?

To me it looks fairly similar and the changes seem mechanical, they
could probably even be done with automatic Python AST modification.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#893577: sbuild-debian-developer-setup: Should not rely on files in /usr/share/doc

[Stuart Prescott]

Package: sbuild-debian-developer-setup
Version: 0.74.0-1
Severity: serious
Justification: Policy 12.3 Packages must not require the existence of any files 
in /usr/share/doc/ in order to function.

Dear Maintainer,

Thanks for adding sbuild-debian-developer-setup - it indeed looks like a good
way of a new user getting started with sbuild.

At the end of the script, it runs

symlink("/usr/share/doc/sbuild/examples/sbuild-update-all", 
"/etc/cron.daily/sbuild-debian-developer-setup-update-all");

which requires the file in /usr/share/doc to be present. Policy 12.3 says that
packages can't do that and says that such files should be in /usr/share/package
with a symlink into /usr/share/doc/package/ as appropriate.

regards
Stuart

Bug#893576: crontab.1: Some fixes in the manual

[Bjarni Ingi Gislason]

Package: cron
Version: 3.0pl1-130
Severity: minor
Tags: patch

Dear Maintainer,

  (The patch is in the attachment.)

Input file is crontab.1

mandoc: crontab.1:46:35: STYLE: whitespace at end of input line
mandoc: crontab.1:50:56: STYLE: whitespace at end of input line
mandoc: crontab.1:52:25: STYLE: whitespace at end of input line
mandoc: crontab.1:54:35: STYLE: whitespace at end of input line
mandoc: crontab.1:56:50: STYLE: whitespace at end of input line
mandoc: crontab.1:75:12: STYLE: whitespace at end of input line
mandoc: crontab.1:86:15: STYLE: whitespace at end of input line
mandoc: crontab.1:110:60: STYLE: whitespace at end of input line
mandoc: crontab.1:119:17: STYLE: whitespace at end of input line
mandoc: crontab.1:122:55: STYLE: whitespace at end of input line
mandoc: crontab.1:161:16: STYLE: whitespace at end of input line
mandoc: crontab.1:171:43: STYLE: whitespace at end of input line
mandoc: crontab.1:20:15: WARNING: cannot parse date, using it verbatim: 19 
April 2010

###

Input file is crontab.1

Test nr. 1:

Remove space at end of lines to simplify other automatic tests to improve
typesetting.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

46:file in order to use this command. 
50:command, or all users will be able to use this command. 
52:If both files exist then 
54:takes precedence. Which means that 
56:is not considered and your user must be listed in 
75:.IR su (8) 
86:the note under 
110:is to display the three line "DO NOT EDIT THIS FILE" header 
119:behaviour of the 
122:original behaviour by setting the environment variable 
161:The files under 
171:Paul Vixie  is the author of 

#

Test nr. 6:

Change two HYPHEN-MINUSES (code 0x055, 2D) to an em-dash (\[em]), if one
is intended.  An en-dash is usually surrounded by a space, while an em-dash
is used without spaces. "man" (1 byte characters) transforms an en-dash
(\[en] to one HYPHEN-MINUS, and an em-dash to two HYPHEN-MINUSES without
considering the space around it.

117:non-idempotent -- you keep adding copies of the header. This causes

#

Test nr. 24:

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

65:.I -u
77:.I -u
84:.I -l
91:.I -r
95:.I -e
104:.I -i
109:.I crontab -l
120:.B -l
125:.I crontab -l

#

Test nr. 27:

Split lines longer than 80 characters into two or more
lines.  Apropriate break points are the end of a sentence or subordinate
clause.

crontab.1: line 166 length 84

#

Test nr. 28:

Wrong distance between sentences or protect the indicator.

1) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) and "info groff".

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.

The "indicator" is an "end-of-sentence character" (.!?).

54:takes precedence. Which means that 
67:used (when listing) or modified (when editing). If this option is not given,
85:option causes the current crontab to be displayed on standard output. See
99:from the editor, the modified crontab will be installed automatically. If
112:beginning of the crontab when it is installed. The problem is that
117:non-idempotent -- you keep adding copies of the header. This causes
118:pain to scripts that use sed to edit a crontab. Therefore, the default
121:option has been changed to not output such header. You may obtain the
137:directory. Users are not allowed to edit the files under that directory
156:cron requires that each entry in a crontab end in a newline character. If 
the
164:are named based on the user's account name. Crontab jobs will not be run for
173:and original creator of this manual page. This page has also been modified 
for

#

Test nr. 30:

Surround a block of comments with the macros ".ig" and "..".
The .\" (\#) at the beginning of each line is then not needed.
Makes it easier to add and remove text and adjust lengtxh of lines.

NO PATCH

1:.\"/* Copyright 1988,1990,1993 by Paul Vixie
2:.\" * All rights reserved
3:.\" *
4:.\" * Distribute freely, except: don't remove my name from the source or
5:.\" * documentation (don't take credit for my work), mark your changes (don't
6:.\" * get me blamed for your possible bugs), don't alter or remove this
7:.\" * notice.  May be sold if buildable source is provided to buyer.  No
8:.\" * warrantee of any kind, express or implied, is included with this
9:.\" * software; use at your own risk, responsibility for damages (if any) to
10:.\" * anyone resulting from the use of this software rests entirely with the
11:.\" * user.
12:.\" *
13:.\" * Send bug reports, bug fixes, enhancements, requests, flames, etc., and
14:.\" * I'll try to keep a version up to date.  I can be reached as follows:
15:.\" * Paul Vixie    uunet!decwrl!vixie!paul
16:.\" */
17:.\"
18:.\" $Id: crontab.1,v 2.4 1993/12/31 10:47:33 vixie Exp $
19:.\"

#

Bug#893575: crontab.5: Some fixes in the manual

[Bjarni Ingi Gislason]

Package: cron
Version: 3.0pl1-130
Severity: minor
Tags: patch

Dear Maintainer,

  (The patch is in the attachment)

Input file is crontab.5

mandoc: crontab.5:19:4: STYLE: whitespace at end of input line
mandoc: crontab.5:59:14: STYLE: whitespace at end of input line
mandoc: crontab.5:61:10: STYLE: whitespace at end of input line
mandoc: crontab.5:78:76: STYLE: whitespace at end of input line
mandoc: crontab.5:88:75: STYLE: whitespace at end of input line
mandoc: crontab.5:107:47: STYLE: whitespace at end of input line
mandoc: crontab.5:115:62: STYLE: whitespace at end of input line
mandoc: crontab.5:125:77: STYLE: whitespace at end of input line
mandoc: crontab.5:134:65: STYLE: whitespace at end of input line
mandoc: crontab.5:270:74: STYLE: whitespace at end of input line
mandoc: crontab.5:272:21: STYLE: whitespace at end of input line
mandoc: crontab.5:277:59: STYLE: whitespace at end of input line
mandoc: crontab.5:346:67: STYLE: whitespace at end of input line
mandoc: crontab.5:348:50: STYLE: whitespace at end of input line
mandoc: crontab.5:364:4: STYLE: whitespace at end of input line
mandoc: crontab.5:376:64: STYLE: whitespace at end of input line
mandoc: crontab.5:379:13: STYLE: whitespace at end of input line
mandoc: crontab.5:395:43: STYLE: whitespace at end of input line
mandoc: crontab.5:20:15: WARNING: cannot parse date, using it verbatim: 19 
April 2010
mandoc: crontab.5:152:6: WARNING: tab in filled text
mandoc: crontab.5:154:6: WARNING: tab in filled text
mandoc: crontab.5:156:7: WARNING: tab in filled text
mandoc: crontab.5:158:5: WARNING: tab in filled text
mandoc: crontab.5:160:13: WARNING: tab in filled text
mandoc: crontab.5:162:6: WARNING: tab in filled text
mandoc: crontab.5:164:12: WARNING: tab in filled text
mandoc: crontab.5:216:7: WARNING: tab in filled text
mandoc: crontab.5:218:7: WARNING: tab in filled text
mandoc: crontab.5:220:8: WARNING: tab in filled text
mandoc: crontab.5:222:8: WARNING: tab in filled text
mandoc: crontab.5:224:10: WARNING: tab in filled text
mandoc: crontab.5:226:9: WARNING: tab in filled text
mandoc: crontab.5:228:8: WARNING: tab in filled text
mandoc: crontab.5:230:7: WARNING: tab in filled text
mandoc: crontab.5:232:10: WARNING: tab in filled text
mandoc: crontab.5:234:8: WARNING: tab in filled text

###

Test nr. 1:

Remove space at end of lines to simplify other automatic tests to improve
typesetting.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

19:.\" 
59:be used. The  
61:string is 
78:many shells will treat the tilde(~) as substitution of $HOME, so if you use 
88:SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd 
107:module, and loads the environment specified by 
115:override the settings described above nor any settings in the 
125:variables are set, or the locale specified by the LC_* environment 
variables 
134:followed by a command, followed by a newline character ('\\n').  
270:All the above examples run non-interactive programs. If you wish to run a 
272:environment variable 
277:.\" work in all systems, as notify-send might require also 
346:daemon runs with a defined timezone. It currently does not support 
348:configured timezone. Even if a user specifies the 
364:The 
376:required. Useful tools that could be used for date analysis are 
379:.I calendar 
395:Paul Vixie  is the author of 

#

Test nr. 2:

Enable and fix warnings from 'test-groff'.

Input file is /tmp/crontab.5

:108 (macro IR): only 1 argument, but more are expected

chk_manuals: Output is from: test-groff -Tutf8 -b -e -mandoc -rF0 -t -w w -z 

#

Test nr. 5:

Change '-' to '\(en' (en-dash) for a numeric range.

crontab.5:156:minute0-59
crontab.5:158:hour  0-23
crontab.5:160:day of month  1-31
crontab.5:162:month 1-12 (or names, see below)
crontab.5:164:day of week   0-7 (0 or 7 is Sun, or use names)
crontab.5:171:8-11 for an ``hours'' entry specifies execution at hours 8, 9, 10
crontab.5:175:separated by commas.  Examples: ``1,2,5,9'', ``0-4,8-12''.
crontab.5:179:through the range.  For example, ``0-23/2'' can be used in the 
hours
crontab.5:260:0 22 * * 1-5mail \-s "It's 10pm" joe%Joe,%%Where are your 
kids?%
crontab.5:261:23 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., 
everyday"
crontab.5:266:0 4 8-14 * *test $(date +\\%u) \-eq 6 && echo "2nd Saturday"
crontab.5:326:Lists and ranges are allowed to co-exist in the same field.  
"1-3,7-9" would
crontab.5:327:be rejected by AT or BSD cron -- they want to see "1-3" or 
"7,8,9" ONLY.
crontab.5:329:Ranges can include "steps", so "1-9/2" is the same as "1,3,5,7,9".
crontab.5:384:0 4 * * Sat   [ "$(date +\\%e)" = "$(LANG=C ncal | sed -n 's/^Sa 
.* \\([0-9]\\+\\) *$/\\1/p')" ] && echo "Last Saturday" && program_to_run

#

Test nr. 6:

Change two HYPHEN-MINUSES (code 0x055, 2D) to an em-dash (\[em]), if one
is intended.  An en-dash is usually surrounded by a 

Bug#891391: ITP: python-hsluv -- Python implementation of HSLuv (Human-friendly HSL)

[魏銘廷]

I am filing an issue as question to the upstream:

https://github.com/hsluv/hsluv-python/issues/10

In the screenshot provided in the issue the code seems to be pretty
different, so I am wondering that does it count as an "reimplementation"
of hsluv?

On 03/20/2018 08:26 AM, Paul Wise wrote:
> If that is the case, then it could be possible to automate this
> conversion and drop the generated and then modified file from git.



signature.asc
Description: OpenPGP digital signature

Bug#891297: gnome-keyring: Incomplete debian/copyright?

[Chris Lamb]

Hey,

> To provide a bit more reasoning for my change today, this issue isn't
> new to version 3.27 and shouldn't prevent 3.27 or 3.28 from reaching
> Testing.

Nod. :)

> I think it is a huge waste of time to add the names of every person
> mentioned in the translations headers to debian/copyright 

Perhaps that is so; I was just missing some context to the
downgrade -- thank you for clarifying.


Best wishes,

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

Bug#891297: gnome-keyring: Incomplete debian/copyright?

[Jeremy Bicha]

To provide a bit more reasoning for my change today, this issue isn't
new to version 3.27 and shouldn't prevent 3.27 or 3.28 from reaching
Testing.

I think it is a huge waste of time to add the names of every person
mentioned in the translations headers to debian/copyright and at any
rate, it's not something I'm going to be working on right now.

Someone else is of course free to work on this bug.

Thanks,
Jeremy Bicha

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Jeremy Bicha]

On Mon, Mar 19, 2018 at 8:15 PM, Chris Lamb  wrote:
>> I'm lowering the severity here, but […]
>
> No strong objection, just curious why?  You're very reticent in your
> BTS messages it seems! ;-)

I don't really see how mentioning a few names of people who happen to
be mentioned in the headers of files really helps Debian much. There
are lots of other contributors to this package (include the current
maintainer) that aren't listed in those headers.

Debian Policy § 12.5 is not so specific to make this particular case
an RC issue. The severity of this issue isn't very important (since
it's already fixed in the VCS) except that it prevented newer versions
from reaching Testing which I consider to be a more important issue.

Thanks,
Jeremy Bicha

Bug#890335: [Pkg-privacy-maintainers] Bug#890335: torbrowser-launcher: couldn't upload

[Georg Faerber]

Hi intrigeri,

On 18-03-18 10:14:31, intrigeri wrote:
> Georg Faerber:
> >> When trying to upload to any site got crash:
> >> 
> >> "Gah. Your tab just crashed."
> >> 
> >> While there are no such problem with firefox of the same version.
> 
> > I guess this is due to AppArmor.
> 
> > dmesg reads:
> >> [91740.737822] audit: type=1400 audit(1521316491.662:281): 
> >> apparmor="DENIED"
> >> operation="file_receive" profile="torbrowser_plugin_container"
> >> name="/home/georg/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/Desktop/foo"
> >> pid=21414 comm="Chrome_ChildThr" requested_mask="r" denied_mask="r" 
> >> fsuid=1000
> >> ouid=1000
> >> [91740.737923] Chrome_ChildThr[21417]: segfault at 0 ip 55dc7d269a05 
> >> sp 7fa025bfe390 error 6 in plugin-container[55dc7d264000+2]
> 
> At first glance, the AppArmor profiles we ship do not grant access to
> that Desktop directory.
> 
> Can you please try uploading a file from the Tor Browser's "Downloads"
> directory, that is likely:
> 
>   
> $HOME/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/Downloads/
> 
> ?

I would like to, but I've hit #893308. I'm not able to currently run it
at all, I'm happy to take any pointers over there. (I didn't debugged
this further, time was limited, and I also didn't check if this happens
on a clean install as well.)

Cheers,
Georg


signature.asc
Description: Digital signature

Bug#891391: ITP: python-hsluv -- Python implementation of HSLuv (Human-friendly HSL)

[Paul Wise]

On Mon, Mar 19, 2018 at 10:04 PM, Yao Wei wrote:

> [1]: https://github.com/hsluv/hsluv-python/blob/master/hsluv.py

I quote from that file:

""" This module is generated by transpiling Haxe into Python and cleaning
the resulting code by hand, e.g. removing unused Haxe classes. To try it
yourself, clone https://github.com/hsluv/hsluv and run:
haxe -cp haxe/src hsluv.Hsluv -python hsluv.py """

If that is the case, then it could be possible to automate this
conversion and drop the generated and then modified file from git.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#893542: ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped when ntp is purged

[Richard Laager]

On 03/19/2018 02:42 PM, Julian Gilbey wrote:
> Package: ntpsec-ntpviz
> Version: 1.0.0+dfsg1-5
> Severity: serious
> 
> I installed the ntpsec suite, then purged the ntp packages.
> Unfortunately, this zapped the /var/log/ntpstats directory, which is
> needed by ntpsec-ntpviz.  There needs to either been some agreement
> between ntp and ntpsec about the use of this directory, or ntpsec
> needs to use a different log directory.

We have the same situation in reverse too, it seems.

Keeping the same log directory between ntp and ntpsec is desirable, for
several reasons:

- The log format is the same.
- Logs are not lost on conversions from ntp to ntpsec or ntpsec to ntp.
- ntpsec-ntpviz is co-installable with ntp and works. This might be
desirable, if someone wants to continue using ntp but use ntpviz to
create useful graphs.
- IIRC, the default /etc/ntp.conf from ntp references this path, so
keeping the logging path the same means we don't need to change
/etc/ntp.conf on conversions from ntp<->ntpsec.

Likewise for /var/lib/ntp, where the drift file is stored. There again,
it is very desirable to keep the same drift file upon conversions from
ntp<->ntpsec. Otherwise, accuracy is lost until the new ntpd has a
chance to recalculate the drift value.

Related, there's the issue of the ntp user (and ntp group). Those should
not be removed until /var/log/ntpstats is gone. The ntpsec-ntpviz
package also needs the ntp user and group, so coordination is required
there too.

An alternative would be to _copy_ the log files and drift file on
initial installation of ntpsec. This has some downsides:
- Only ntp -> ntpsec conversions benefit. If someone goes the other way,
or goes to ntpsec and then back, logs are still lost, unless ntp also
adopts a copying approach (but then why copy instead of share?).
- ntpsec needs to sed /etc/ntp.conf to change the paths. This breaks
logging if someone moves back to ntp, unless ntp also seds the config
file (again then why not just share?).
- This breaks anything else that someone might be doing with the log
files (and drift file, but that seems unlikely).
- We still need to coordinate on the ntp user (and group), unless ntpsec
uses a different user (and group) too. If so, then I'm deviating from
upstream naming (and years of user history with ntp).

Another alternative would be for both packages to simply _not_ delete
any of these things.

I have wrapped the `rm -rf` with a check for ntp. Here is what I have in
ntpsec.postrm now:

if ! LANG=C dpkg -s ntp > /dev/null 2>&1
then
rm -rf /var/lib/ntp/
rm -rf /var/log/ntpstats/
fi
if ! LANG=C dpkg -s ntpsec-ntpviz 2> /dev/null | \
 grep -qE "^Status: (hold|install)"; then
deluser --system --quiet ntp || true
fi


I suggest the same for ntp.postrm, but with "ntp" changed to "ntpsec":

if ! LANG=C dpkg -s ntpsec > /dev/null 2>&1
then
rm -rf /var/lib/ntp/
rm -rf /var/log/ntpstats/
fi
if ! LANG=C dpkg -s ntpsec-ntpviz 2> /dev/null | \
 grep -qE "^Status: (hold|install)"; then
deluser --system --quiet ntp || true
fi


Is this acceptable on the ntp side? If not, can you propose a different
solution?

-- 
Richard

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Chris Lamb]

Hi Jeremy,

> I'm lowering the severity here, but […]

No strong objection, just curious why?  You're very reticent in your
BTS messages it seems! ;-)


Best wishes,

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

Bug#890873: lintian: gcc-8-cross-ports makes lintian fork-bomb, consume all memory and fill the disk

[Olly Betts]

On Tue, Feb 20, 2018 at 07:48:31AM +0100, Niels Thykier wrote:
> Seen twice on lindsay.d.o in the last 24 hours.  The exact reason is
> unknown, but it is probably during the unpacker (last non-error in the
> log is lintian starting the unpack, plus previously we had a race-condition
> in the unpacker that could trigger a similar fork-bomp situation).
> 
> Most likely we never fixed this condition and only made it
> "sufficiently unlikely" until gcc-8-cross-ports showed up.
> 
> For now, I have disabled the crontab on lindsay.d.o to avoid it taking
> down our host.

I tried to build the wxwidgets3.0 3.0.4+dfsg-1 in an unstable chroot a
couple of days ago.  I use sbuild and it's configured to run lintian in
the chroot on the built packages.  However lintian ran out of disk space
in the chroot, which isn't something I have hit before.  And I would
expect the build itself to need more disk space than lintian (assuming
that the debian/rules clean target is run before lintian is).  Lintian
appeared to be slowly failing on each binary package in turn, so I just
hit Ctrl-C on it.

I asked on #debian-devel in case this was a known problem, and lamby
pointed out this ticket and suggested adding a note in case this is the
same underlying issue, so I'm doing so.  I didn't attempt to investigate
further yet.

Cheers,
Olly

Bug#893574: gnome-shell: Suspend after 20 minutes even there is activity on a seat

[floris]

Package: gnome-shell
Version: 3.28.0-1
Severity: important

Dear Maintainer,

Since version 3.27.90 the default action is to suspend after 20 minutes of
inactivity. Unfortunately, the system also suspend when there is activity on a
seat while the other is idle.

   * What led up to the situation?

create a multiseat setup with the "loginctl attach seat1" command

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

Leave seat1 on the gdm3 login screen and go away.
Login on seat0 and play.

   * What was the outcome of this action?

The system go to sleep after 20 minutes

   * What outcome did you expect instead?

The system stays awake

When both seats are active the system doesn't go to sleep.

journalctl
mrt 20 00:42:21 Jessica gnome-shell[1403]: Screen lock is locked down, not
locking
mrt 20 00:42:21 Jessica kernel: PM: suspend entry (deep)
mrt 20 00:42:21 Jessica gnome-shell[3700]: Screen lock is locked down, not
locking
mrt 20 00:42:21 Jessica NetworkManager[896]:   [1521502941.3440] manager:
sleep: sleep requested (sleeping: no  enabled: yes)
mrt 20 00:42:21 Jessica NetworkManager[896]:   [1521502941.3440] manager:
NetworkManager state is now ASLEEP
mrt 20 00:42:21 Jessica systemd[1]: Reached target Sleep.
mrt 20 00:42:21 Jessica systemd[1]: Starting Suspend...
mrt 20 00:42:21 Jessica systemd-sleep[6914]: Suspending system...

See also Gnome bug 681869 https://bugzilla.gnome.org/show_bug.cgi?id=681869



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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-3
ii  evolution-data-server3.26.5-2
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2-atspi-2.0 2.28.0-1
ii  gir1.2-freedesktop   1.56.0-1
ii  gir1.2-gcr-3 3.28.0-1
ii  gir1.2-gdesktopenums-3.0 3.28.0-1
ii  gir1.2-gdm-1.0   3.28.0-1
ii  gir1.2-geoclue-2.0   2.4.7-1
ii  gir1.2-glib-2.0  1.56.0-1
ii  gir1.2-gnomebluetooth-1.03.28.0-2
ii  gir1.2-gnomedesktop-3.0  3.28.0-1
ii  gir1.2-gtk-3.0   3.22.29-1
ii  gir1.2-gweather-3.0  3.28.0-2
ii  gir1.2-ibus-1.0  1.5.17-3
ii  gir1.2-mutter-2  3.28.0-2
ii  gir1.2-nm-1.01.10.6-2
ii  gir1.2-nma-1.0   1.8.10-2
ii  gir1.2-pango-1.0 1.40.14-1
ii  gir1.2-polkit-1.00.105-18
ii  gir1.2-rsvg-2.0  2.40.20-2
ii  gir1.2-soup-2.4  2.62.0-1
ii  gir1.2-upowerglib-1.00.99.7-2
ii  gjs  1.52.0-1
ii  gnome-backgrounds3.28.0-1
ii  gnome-settings-daemon3.28.0-1
ii  gnome-shell-common   3.28.0-1
ii  gsettings-desktop-schemas3.28.0-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libc62.27-2
ii  libcairo21.15.10-2
ii  libcanberra-gtk3-0   0.30-6
ii  libcanberra0 0.30-6
ii  libcroco30.6.12-2
ii  libecal-1.2-19   3.26.5-2
ii  libedataserver-1.2-223.26.5-2
ii  libgcr-base-3-1  3.28.0-1
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libgirepository-1.0-11.56.0-1
ii  libgjs0g [libgjs0-libmozjs-52-0] 1.52.0-1
ii  libglib2.0-0 2.56.0-2
ii  libglib2.0-bin   2.56.0-2
ii  libgstreamer1.0-01.12.4-1
ii  libgtk-3-0   3.22.29-1
ii  libical3 3.0.1-5
ii  libjson-glib-1.0-0   1.4.2-3
ii  libmutter-2-03.28.0-2
ii  libnm0   1.10.6-2
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libpolkit-agent-1-0  0.105-18
ii  

Bug#892096: gcc-snapshot: AddressSanitizer uses glibc internal functions

[Vincent Lefevre]

Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84761
Control: tags -1 fixed-upstream

in the sense that this will be OK at least up to glibc 2.27.

See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84761#c9

Author: jakub
Date: Mon Mar 19 20:47:29 2018
New Revision: 258663

URL: https://gcc.gnu.org/viewcvs?rev=258663=gcc=rev
Log:
PR sanitizer/84761
* sanitizer_common/sanitizer_linux_libcdep.cc (__GLIBC_PREREQ):
Define if not defined.
(DL_INTERNAL_FUNCTION): Don't define.
(InitTlsSize): For __i386__ if not compiled against glibc 2.27+
determine at runtime whether to use regparm(3), stdcall calling
convention for older glibcs or normal calling convention for
newer glibcs for call to _dl_get_tls_static_info.

Modified:
trunk/libsanitizer/ChangeLog
trunk/libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cc

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

Bug#891391: ITP: python-hsluv -- Python implementation of HSLuv (Human-friendly HSL)

[Paul Wise]

On Mon, Mar 19, 2018 at 10:04 PM, Yao Wei wrote:

> I am having a situation that this code is said to be "transpiled" from
> HSLuv written in Haxe [1], the code seems to be gone though a lot of
> overhaul from the generated code that cannot be diffed.  I believe the
> code written in Python is preferred form of making modifications for
> hsluv-python project.  However, I need consensus on this mattter.

I suggest you dig through the git history of both HSLuv and
Python-HSLuv to develop an intuition about how the upstreams are
developing both projects and then clarify the details of their
development processes with upstream.

Personally, I find the thought of modifying generated code to be
horrible and would have either stuck with building from Haxe or
reimplementing the code in Python.

At the end of the day, what matters is that there is equality of
access to the work between the upstream authors and users of Debian
derivatives. i.e., make sure upstream aren't keeping something secret
or using something proprietary and make sure Debian passes on what we
receive from upstream.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#893573: auto-apt-proxy: autopkgtest assumes clean proxy environment

[Steve Langasek]

Package: auto-apt-proxy
Version: 8
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch autopkgtest

Hi Antonio,

The autopkgtests for auto-apt-proxy 8 have been failing in Ubuntu because
they assume that installing apt-cacher-ng is sufficient to cause apt to use
it for apt downloads:

[...]
autopkgtest [03:00:15]: test apt-integration: [---
Reading package lists...
NOTICE: 'auto-apt-proxy' packaging is maintained in the 'Git' version control sy
stem at:
https://anonscm.debian.org/git/users/terceiro/auto-apt-proxy.git
Please use:
git clone https://anonscm.debian.org/git/users/terceiro/auto-apt-proxy.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 17.1 kB of source archives.
Get:1 http://ftpmaster.internal/ubuntu bionic-proposed/universe auto-apt-proxy 8
 (dsc) [1786 B]
Get:2 http://ftpmaster.internal/ubuntu bionic-proposed/universe auto-apt-proxy 8
 (tar) [15.3 kB]
dpkg-source: info: extracting auto-apt-proxy in auto-apt-proxy-8
dpkg-source: info: unpacking auto-apt-proxy_8.tar.xz
Fetched 17.1 kB in 0s (932 kB/s)
autopkgtest [03:00:16]: test apt-integration: ---]
autopkgtest [03:00:16]: test apt-integration:  - - - - - - - - - - results - - -
 - - - - - - -
apt-integration  FAIL non-zero exit status 1
[...]

  http://autopkgtest.ubuntu.com/packages/a/auto-apt-proxy/bionic/amd64

The failing part of the test is the grep for auto-apt-proxy in
/var/log/apt-cacher-ng/apt-cacher.log.  The reason this grep returns no
results is that the Ubuntu autopkgtest environment sets a no_proxy variable
which matches the configured apt mirrors; therefore, apt-cacher-ng's
configuration has no effect because apt rightly bypasses it according to the
environment setting.

The attached patch allows the auto-apt-proxy autopkgtest to pass by making
it a no-op when $no_proxy is present.  You might prefer instead to unset it
and run the test, but in that case apt-cacher-ng must itself honor the
no_proxy setting, which it may or may not do.

Please consider including this or a similar patch in Debian.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru auto-apt-proxy-8/debian/tests/apt-integration 
auto-apt-proxy-8ubuntu1/debian/tests/apt-integration
--- auto-apt-proxy-8/debian/tests/apt-integration   2017-11-27 
07:50:22.0 -0800
+++ auto-apt-proxy-8ubuntu1/debian/tests/apt-integration2018-03-19 
16:40:51.0 -0700
@@ -2,6 +2,11 @@
 
 set -eu
 
+if -n [ "$no_proxy" ]; then
+   echo "no_proxy variable is set, skipping test"
+   exit 0
+fi
+
 cd ${AUTOPKGTEST_TMP:-/tmp}
 apt-get source auto-apt-proxy
 

Bug#893572: tracker.debian.org: Debian Maintainer display: [dm] links empty, should be uppercase and use parentheses

[Paul Wise]

Package: tracker.debian.org
Severity: minor
Tags: newcomer

On the libgit2 page there is a link next to the Maintainer:


[dm]


https://tracker.debian.org/pkg/libgit2

I think these changes are needed:

 * the dm should be uppercase (possibly in smallcaps), because it is an
   acronym for Debian Maintainer
 * use an acronym tag, because DM is an acronym for Debian Maintainer
 * use "Debian Maintainer upload allowed" for the explanation title, inthat 
case the abbrev tag should be used instead of the acronym tag
 * use parentheses instead of crotchets/brackets to differentiate it
   from the DMD link a bit and because the PTS used that
 * the link should be removed or changed to dm.txt since that is the
   only source of information about DM upload permissions.

Here is how these changes should look in the HTML:


(https://ftp-master.debian.org/dm.txt; 
title="">DM)


Or:


(DM)


-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#753541: FTBFS with clang instead of gcc

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

since release 5.1.0 the file app/wlib/gtklib/gtkhelp.c dosn't exist.

So I close this bug.

CU
Jörg
- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlqwROIACgkQCfifPIyh
0l1FiQ//eJU3VYJw1Gaw4Au9NjIbXPY+8lgVSxchL+egAODfrTsi1yPTewuNQBCK
Jm8Y2yDq/xhMlYCXBt1QIZXIlT6XdLC5cX729njV8FMEIeDZGN51veLKUL6oAmF8
TMxuIm43WJ4FOxMbPZ8B9sJydlb9CJfyAh+3oTzmS6IBTefwSALyvKkcxXTZO4Hl
/dshagGBKU3lImpGvH7h95mZKip5sK5+s9xiwmsSgzIGg43O4dN0KBvYXcMP7uHD
JTFCcr6v7yLtG06Jl7zFETUbpDmH4qrpjORjBeGvvin0kBtZD+jKCWR3+yF6TP9v
RMEFbUnw4c2QsteldulqvVsZv/nP6t1yptiyNWEtrglhrUWrZ6Iw2/qqPfb8a2DF
iQD50HySqIj0L1airaAfzIFjh5Ft3Yc+rkdAlXXLHDf339XMU9VdrsdIr5RB5Pzy
EzvTE+haGXoMuj3bZmCIBwxs2Uyp0CH0ZalBU5/E6zv3i98IqzJgwPlFge2RPlLA
QKVfIlejDZs+U5uqsFVSd+X2HRpZvOD+kybskzQA+VYO9OQp2G0L2t4f44QuI/Fh
fIejSOXS13YbQSE5YQ6HnOWnm6nthjCrRzobvHurTfDycNdtmBEAk0//yj/Mu48D
n4YXP26AXgqNeBmOSfJakWIsGQ30VgP3UQUZAiUBDFCxloXwYiE=
=6sq8
-END PGP SIGNATURE-

Bug#888479: Confirm for bug on stretch

[Alexander M. Wirtz]

Hi all,

I have recently switched to stretch and I'm experiencing similar  
behaviour, segfaults when typing ö, ä, ü, ß, §, usw.


tcsh 6.20.00 (Astron) 2016-11-24 (i686-intel-linux) options  
wide,nls,dl,al,kan,sm,rh,nd,color,filec


Happy to support the hunt, please advise.

Best,
Alexander

Bug#780706: Arduino packaging

[Geert Stappers]

On Mon, Mar 19, 2018 at 11:13:33AM -0300, Ignacio Losiggio wrote:
> Sorry for my delayed response (i'm on university exams week) :P

Thanks for the heart beat. Yes, please focus on the exams.

 
> >  * liblistSerials
> >  * arduino-builder
> > - golang-go-errors-errors
> 
> Nice work!

Yes.
And the review of liblistSerials is going smoothly.  \o/


> I think that org.bouncycastle.util.Iterable is in `libbcprov-java`, you can
> see the dependency list i've come up with while trying to package arduino
> [here](https://github.com/HuayraLinux/pkg-arduino/blob/master/debian/control),
> i thin it's pretty complete (i use a clean pbuilder chroot to make packages
> :P).

Seen the URL.
Closer looking will be done after listserialportsc upload.


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Jeremy Bicha]

Control: severity -1 important

I'm lowering the severity here, but the important part is that this
will be fixed with our next upload which should be soon…

Thanks,
Jeremy Bicha

Bug#893571: RFS: xtrkcad/1:5.1.0-1 RC

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: sponsorship-requests
Severity: important

Dear mentors,

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

   Package name: xtrkcad
   Version : 1:5.1.0-1
   Upstream Author : XTrkCAD Developers 

   URL : http://xtrkcad.org/
   License : GPL-2+, Expat, permissive, public-domain
   Section : editors

  It builds those binary packages:

 xtrkcad- CAD program for designing model railroad layouts
 xtrkcad-common - CAD program for designing model railroad layouts (common 
files)

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

  https://mentors.debian.net/package/xtrkcad
  git://anonscm.debian.org/collab-maint/xtrkcad.git


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

dget -x 
https://mentors.debian.net/debian/pool/main/x/xtrkcad/xtrkcad_5.1.0-1.dsc


  Changes since the last upload:

[ Jörg Frings-Fürst ]
  * New upstream release.
- Remove from the upstream applied patches:
  + debian/patches/0700-info_file.patch
  + debian/patches/0705-help_path.patch
  + debian/patches/0100-gtk.patch
- Refresh patches:
  + debian/patches/0900-spelling-errors.patch
- Refresh debian/copyright.
- debian/xtrkcad.docs: Rename Readme.txt to Readme.md.
- debian/xtrkcad.install: Remove Readme.txt.
- debian/control: Remove not longer used libwebkitgtk-1.0-0
  (Closes: #790221).
  * debian/control:
- Add Daniel E. Markle as maintainer again.
- Add myself as uploader.
- Use http for the homepage because https isn't available.
  * Declare compliance with Debian Policy 4.1.3 (No changes needed).
  * Migrate to debhelper 11:
- Change debian/compat to 11.
- Bump minimum debhelper version in debian/control to >= 11.
- Remove --parallel from debian/rules.
  * debian/changelog, debian/control: Remove trailing whitespaces.
  * Change to my new mail address:
- debian/control,
- debian/copyright

  Regards,
   Jörg Frings-Fürst




- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlqwQS8ACgkQCfifPIyh
0l36xRAAnDM//Y0WN4n9YHbG60P6BoD4ZMjQtmMKuFxmLc5+J0LHQ9yPh33YieUN
ptP7gJIHJpqIfefOmVIGHKojKd32/gLe3UqY6VgzCAMavtVzGdkf2tdo+EueeAjF
TTCALlsTiyIQ9stWesOMAkk/0pzsbsObBknohzcPhSC/xKX1p/CPshrOhTTRPiTo
Gq4/wKfxN2IxCFXj5ymNv0XQVkKxUIkJ1nCgL0qHnzFM33jg6G4P6gH+z9E6IGiZ
dI5ejpkPVktXapwN/VNItmqHQxl0ZUMufdzFzwif55Upn9fxZwmSG/+m63iLvK6a
tEhjazdTjlDa9yBiWyxxbwIh/Nznz6KS0igUS4yJigkuQ0FzjzbMzxgo69K/vJnN
3XzRmIyzRIWLLYIp3AhsFUa7CirbLLR+WHkM3fLh4be8osZvy/bcOgTUiN4EQPYF
LZZNOUlyp2PaxW2snVGWahxUM/jFuPHqqBDBJQ/cAn82TlcQXJx7M4qzZWks3UUB
OIrNex6SkyHfdiP7m4KUCNA03MjQkNxrxfjbMIm/7ug4bRmwpbv8V+nxXaSPlfwC
Hfv+9nGVfWA6oQ6F6Pq84cpVi5SP7IrXWWUjTx4aeJP4YjWdSnDgqip10kUQD73F
ooEN7670866zWytxUrbnezDyfIv/qDNTccoFfZf0x18cU+NhKEQ=
=FLzG
-END PGP SIGNATURE-

Bug#893120: debian-edu-install: uninstallable on ahrd disk thrice the size mentioned in manual

[Wolfgang Schweer]

On Mon, Mar 19, 2018 at 01:21:33PM +, Holger Levsen wrote:
> isnt this bug a manifestation of three bugs:

As far as I can tell: only sort of. In the first place the bug shows 
that communicating how to install different profiles could be better. 
Maybe there should be BIG and FAT hints; but it might be wishful 
thinking this could make a difference.
 
> 1. netinst image needs to be redone to include updated packages.
Yes, this would solve the problem for now.
>(can we build images using stable-proposed-updates?)
No idea; also: is there enough space available on ftp.s.no? In general 
it would be nice to have the ISOs updated after each stable point 
release.

> 2. ltsp default should be lxde clients
LTSP thin clients need LXDE (or another lightweiht DE like Xfce or MATE) 
on the server side as well; so IMO the recommondatation in the manual 
install chapter (use 'desktop=lxde') is already the right solution.
 
> 3. insufficient diskspace^wfree space on partitions, in general and esp.
>for kde ltsp clients
IMO this is only a follow-up problem (and affecting only Stretch).
 
Wolfgang


signature.asc
Description: PGP signature

Bug#660903: munin: Issue was fixed in v2.0.7

[Lars Kruse]

Package: munin
Followup-For: Bug #660903

Dear Maintainer,

this issue was fixed in munin v2.07 (see commit c6262ac93b):
* http://munin-monitoring.org/ticket/1276

Cheers,
Lars

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Jeremy Bicha]

Control: notfound -1 3.20.1-2

On Mon, Mar 19, 2018 at 6:44 PM, Chris Lamb  wrote:
> Oh, did I file with the wrong version, or..?

Oops. I meant to adjust https://bugs.debian.org/891297 (where the
copyright issue isn't new and shouldn't prevent a package from
migrating to testing).

Thanks,
Jeremy Bicha

Bug#891297: gnome-keyring: Incomplete debian/copyright?

[Jeremy Bicha]

Control: found -1 3.20.1-2

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Chris Lamb]

Hi Jeremy,

> Control: found -1 3.20.1-2

Oh, did I file with the wrong version, or..?


Regards,

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

Bug#893561: libtablelayout-java: license does not seem to meet the DFSG

[Adrian Bunk]

On Mon, Mar 19, 2018 at 10:28:13PM +0100, Francesco Poli (wintermute) wrote:
>...
> The debian/copyright file states, in part:
> 
> | The source code has been modified to make the package suitable for main (see
> | license III. 4.). The package namespace has been changed from
> | info.clearthought.layout to org.debian.tablelayout.
> 
> Personally, I don't think that applying a patch that changes the namespace
> is enough to make the package suitable for Debian main.
> I mean: it's true that it is now possible to create drop-in replacements
> for the Debian package (without further changing the namespace), but it is
> still forbidden to create a modified version that changes the namespace
> back to "info.clearthought".
> 
> I think that this restriction goes beyond what is allowed by DFSG#4.
>...

In https://lists.debian.org/debian-legal/2005/01/msg00142.html you 
agreed entirely that it is OK when software is made DFSG-free through
renaming to avoid trademark violations.

What difference would it make whether our users are forbidden to change
the namespace back to "info.clearthought" due to
1. trademark
2. licence
3. both

The precedent of Firefox and Thunderbird in Debian followed your advice 
that it is OK for 1., and I don't see anything in the DFSG that would 
imply that it would matter whether it is 1. or 2. or 3. that prevents 
our users from changing the namespace back to "info.clearthought".

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#893570: libc6: After update:libc6 my wvdial crashes:utils/wvtask.cc:303:static int WvTaskMan::yield(int): Assertion `*current_

[Yosa]

Package: libc6
Version: 2.24-11+deb9u1
Severity: important

Dear Maintainer,

1.I've updated the following packages:

libc-dev-bin (2.24-11+deb9u1) to 2.24-11+deb9u3
libc6 (2.24-11+deb9u1) to 2.24-11+deb9u3
libc6-dev (2.24-11+deb9u1) to 2.24-11+deb9u3

2.Then I launched WVDIAL

root@debian:/home/mydebi# wvdial
--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT+CGDCONT=1,"IP","x"
AT+CGDCONT=1,"IP","x"
OK
--> Modem initialized.
--> Sending: ATD*99#
--> Waiting for carrier.
ATD*99#
CONNECT 1
--> Carrier detected.  Starting PPP immediately.
--> Starting pppd at Mon Mar 11 18:03:04 2018
--> Pid of pppd: 1616
wvdial: utils/wvtask.cc:303: static int WvTaskMan::yield(int): Assertion
`*current_task->stack_magic == WVTASK_MAGIC' failed.
Aborted

The connection has been established, the internet works but this nasty message
:(
wvdial: utils/wvtask.cc:303: static int WvTaskMan::yield(int): Assertion
`*current_task->stack_magic == WVTASK_MAGIC' failed.
Aborted

3.The dependency analysis indicated that the above two files: libc6 and
libc6-dev appear as dependencies in libwvstreams4.6-base (my version is:
4.6.1-11).

4.I've tried two different USB modems. To work normally, I returned to version:
libc-dev-bin (2.24-11+deb9u1)
libc6 (2.24-11+deb9u1)
libc6-dev (2.24-11+deb9u1)

5. !!! CONCLUSION !!!. The problem (error) is probably in the updated files:
libc6 or libc6-dev or libc-dev-bin, hmmm ??... or in the absence of
actualization the libwvstreams4.6-base file (my version is: 4.6.1-11)

Debian GNU/Linux 9.4 (stretch)
Kernel: Linux 4.9.0-6-amd64

Versions of packages libwvstreams4.6-base (ver. 4.6.1-11) depends:
libwvstreams4.6-extras ver. 4.6.1-11
libc6 ver. 2.24-11+deb9u3 (PROBLEM !) 2.24-11+deb9u1 (NO PROBLEM)
libgcc1 ver. 1:6.3.0-18+deb9u1
libstdc++6 ver.6.3.0-18+deb9u1
zlib1g ver.1:1.2.8.dfsg-5



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

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

Versions of packages libc6 depends on:
ii  libgcc1  1:6.3.0-18+deb9u1

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.61
pn  glibc-doc  
ii  libc-l10n  2.24-11+deb9u3
ii  locales2.24-11+deb9u3

-- debconf information excluded

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Jeremy Bicha]

Control: found -1 3.20.1-2

Bug#893557: thin-provisioning-tools: FTBFS with glibc 2.17

[Steve Langasek]

Package: thin-provisioning-tools
Version: 0.7.4-2
Followup-For: Bug #893557
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Control: retitle -1 thin-provisioning-tools: FTBFS with -O3
Control: severity -1 minor
Control: tags -1 + patch

Ok, after some trial and error, I've determined that the reason my earlier
test succeeded was because I had built the test preload.so without the
benefit of dpkg-buildflags, which means -O3, which is used by default for
ppc64el on Ubuntu, was missing from the commandline.

The attached patch supersedes the previous one, and fixes the build failure
on Ubuntu ppc64el.  Please consider including it in Debian as well for
benefit of anyone who happens to be using -O3 in dpkg-buildflags (not
actually relevant in the distro case in Debian).

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru thin-provisioning-tools-0.7.4/debian/control 
thin-provisioning-tools-0.7.4/debian/control
--- thin-provisioning-tools-0.7.4/debian/control2017-11-01 
14:50:39.0 -0700
+++ thin-provisioning-tools-0.7.4/debian/control2018-03-19 
15:31:50.0 -0700
@@ -1,8 +1,7 @@
 Source: thin-provisioning-tools
 Section: admin
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian LVM Team 

+Maintainer: Debian LVM Team 
 Uploaders: Bastian Blank 
 Build-Depends:
  debhelper (>= 9),
diff -Nru thin-provisioning-tools-0.7.4/debian/rules 
thin-provisioning-tools-0.7.4/debian/rules
--- thin-provisioning-tools-0.7.4/debian/rules  2017-11-01 14:50:39.0 
-0700
+++ thin-provisioning-tools-0.7.4/debian/rules  2018-03-19 15:30:07.0 
-0700
@@ -15,7 +15,9 @@
--with-optimisation=-O2
 
 override_dh_auto_test:
-   $(MAKE) -C debian/unit-tests all
+   $(MAKE) -C debian/unit-tests all \
+   CFLAGS="$$(env DEB_CFLAGS_MAINT_STRIP=-O3 \
+   dpkg-buildflags --get CFLAGS)"
+LD_PRELOAD=$(CURDIR)/debian/unit-tests/preload.so $(MAKE) unit-test 
GMOCK_DIR=/usr/src/googletest
 
 override_dh_auto_clean:

Bug#893569: barman: Mail from /etc/cron.d/barman should be delivered to root

[Matthew Woodcraft]

Package: barman
Version: 2.1-1
Severity: normal

The barman package installs /etc/cron.d/barman, which runs a command as
user barman.

At present the package doesn't take any special action to control where
mail from cron is sent, so if there is any error output it will normally
end up in /var/mail/barman where it's unlikely anyone will see it.

I think the more usual approach in Debian packages is to arrange for
this mail to be delivered to root, either by setting MAILTO=root in the
cron.d file itself or by adding an entry in /etc/aliases for user barman
from postinst.

(The logcheck package provides an example of both of these things.)

Bug#893568: ITP: puppet-module-openstack-extras -- add useful utilities for composing and deploying OpenStack

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: puppet-module-openstack-extras
  Version : 12.3.0
  Upstream Author : OpenStack Foundation 
* URL : https://github.com/openstack/puppet-openstack_extras
* License : Apache-2.0
  Programming Lang: Puppet
  Description : add useful utilities for composing and deploying OpenStack

 Puppet lets you centrally manage every important aspect of your system using a
 cross-platform specification language that manages all the separate elements
 normally aggregated in different files, like users, cron jobs, and hosts,
 along with obviously discrete elements like packages, services, and files.
 .
 This module is used to add useful utilities for composing and deploying
 OpenStack.

Bug#893567: gdm3: Unable to input some special characters in password entry

[Thiago Bellini Ribeiro]

Package: gdm3
Version: 3.28.0-1
Severity: important

After the update to 3.28.0-1 I'm unable to input some special characters in the
password entry, which means that I'm unable to login in my user.

I have a ~ in my password and gdm wont input it. I use "Portuguese (Brazil)"
input source so I have to double-tap the ~ for it to be inputed or press it
once and follow by a space. This would probably happen with the "English US
intl. with dead keys" too since it functions the same for those accents.

Also, I noticed that the "Login Screen" option in "Region & Language" tab in
gnome control center is set to "No input selected". It doesn't matter if I set
one, when I restart my computer if will loose it again. Don't know if that is
related.



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

Kernel: Linux 4.14.0-3-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

Versions of packages gdm3 depends on:
ii  accountsservice   0.6.45-1
ii  adduser   3.117
ii  dconf-cli 0.26.1-3
ii  dconf-gsettings-backend   0.26.1-3
ii  debconf [debconf-2.0] 1.5.66
ii  gir1.2-gdm-1.03.28.0-1
ii  gnome-session [x-session-manager] 3.27.92-1
ii  gnome-session-bin 3.27.92-1
ii  gnome-settings-daemon 3.26.2-1+b1
ii  gnome-shell   3.27.92-2
ii  gnome-terminal [x-terminal-emulator]  3.27.92-1
ii  gsettings-desktop-schemas 3.27.92-1
ii  libaccountsservice0   0.6.45-1
ii  libaudit1 1:2.8.2-1
ii  libc6 2.27-2
ii  libcanberra-gtk3-00.30-6
ii  libcanberra0  0.30-6
ii  libgdk-pixbuf2.0-02.36.11-1
ii  libgdm1   3.28.0-1
ii  libglib2.0-0  2.54.3-2
ii  libglib2.0-bin2.54.3-2
ii  libgtk-3-03.22.28-1
ii  libkeyutils1  1.5.9-9.2
ii  libpam-modules1.1.8-3.7
ii  libpam-runtime1.1.8-3.7
ii  libpam-systemd238-2
ii  libpam0g  1.1.8-3.7
ii  librsvg2-common   2.40.20-2
ii  libselinux1   2.7-2+b1
ii  libsystemd0   238-2
ii  libwrap0  7.6.q-27
ii  libx11-6  2:1.6.4-3
ii  libxau6   1:1.0.8-1+b2
ii  libxcb1   1.13-1
ii  libxdmcp6 1:1.1.2-3
ii  lsb-base  9.20170808
ii  metacity [x-window-manager]   1:3.26.0-1
ii  mutter [x-window-manager] 3.28.0-1
ii  policykit-1   0.105-18
ii  ucf   3.0038
ii  x11-common1:7.7+19
ii  x11-xserver-utils 7.7+7+b1
ii  xterm [x-terminal-emulator]   331-1

Versions of packages gdm3 recommends:
ii  at-spi2-core2.28.0-1
ii  desktop-base9.0.5
ii  x11-xkb-utils   7.7+3+b1
ii  xserver-xephyr  2:1.19.6-1
ii  xserver-xorg1:7.7+19
ii  zenity  3.28.0-1

Versions of packages gdm3 suggests:
ii  gnome-orca3.26.0-5
pn  libpam-fprintd
ii  libpam-gnome-keyring  3.20.1-2

-- debconf information:
  gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3

Bug#893566: linux-image-4.9.0-6-amd64: Logitech wireless mouse freezes with linux-image-4.9.0-6-amd64 (4.9.0-5 worked)

[Paolo Giannozzi]

Package: src:linux
Version: 4.9.82-1+deb9u3
Severity: normal

Dear Maintainer

after updating to debian 9.4, my Logitech wireless mouse (via USB) freezes more
often than not. If I remove and reinsert the battery, the mouse works for some
time (ot much) before freezing again. I downgraded (from the boot menu) to 
kernel linux-image-4.9.0-5-amd64 and the mouse works perfectly again.

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

** Model information
sys_vendor: Acer
product_name: TravelMate P253
product_version: V2.07
chassis_vendor: Acer
chassis_version: V2.07
bios_vendor: Acer
bios_version: V2.07
board_vendor: Acer
board_name: BA51_HC_CR
board_version: Type2 - Board Version

** Network interface configuration:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor DRAM 
Controller [1025:064b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ivb_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:064b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C216 
Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Acer Incorporated [ALI] 7 Series/C216 Chipset Family MEI 
Controller [1025:064b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family 
USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] 7 Series/C216 Chipset Family USB 
Enhanced Host Controller [1025:064b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 Chipset Family 
High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Acer Incorporated [ALI] 7 Series/C216 Chipset Family High 
Definition Audio Controller [1025:064b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset Family PCI 
Express Root Port 1 [8086:1e10] (rev c4) (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: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 2 [8086:1e12] (rev c4) (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: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family 
USB Enhanced Host Controller #1 [8086:1e26] (rev 04) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] 7 Series/C216 Chipset Family USB 
Enhanced Host Controller [1025:064b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1f.0 ISA bridge [0601]: Intel Corporation HM77 Express Chipset LPC 
Controller [8086:1e57] (rev 

Bug#893533: Pending fixes for bugs in the qdox2 package

[pkg-java-maintainers]

tag 893533 + pending
thanks

Some bugs in the qdox2 package are closed in revision
2969244f835e1af4519d4129cd8d98526b22419a in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/qdox2.git/commit/?id=2969244

Commit message:

Ignore the test failure for now but forward the issue upstream.

Closes: #893533

Bug#893564: dmidecode has priority important

[Christian Göttsche]

Package: dmidecode

Version: 3.1-1
Severity: wishlist

Could you consider lowering the priority of dmidecode from important
to standard?
Packages using dmidecode should depend on it and the change would help
keeping minimal systems clean.

Bug#893565: debconf-i18n has priority important

[Christian Göttsche]

Package: debconf-i18n
Version: 1.5.66
Severity: wishlist

Could you consider lowering the priority of debconf-i18n from
important to standard?
This change would help keeping minimal systems clean.

Bug#893557: thin-provisioning-tools: FTBFS with glibc 2.17

[Steve Langasek]

Control: tags -1 - patch
Control: severity -1 serious

On Mon, Mar 19, 2018 at 02:19:40PM -0700, Steve Langasek wrote:
> Package: thin-provisioning-tools
> Version: 0.7.4-2
> Severity: important
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu bionic ubuntu-patch

> Hi Bastian,

> In Ubuntu, thin-provisioning-tools 0.7.4-2 fails to build on ppc64el with an
> ICE in the compiler while building the test suite.  An strace implies that
> this is because your LD_PRELOAD wrapper has interposed open(), but not
> openat().

> If I extend the wrapper as in the attached patch to cover openat(), the
> package now builds.

> This build failure is probably not reproducible yet in Debian, but I expect
> it will be once Debian moves to glibc 2.17.

Hmm, sorry, several corrections:

- the correct glibc version number in 2.27, not 2.17.
- Debian also has 2.27 now, so the build failure probably is reproducible in
  Debian.
- I managed to accidentally create and test this patch against
  thin-provisioning-tools 0.6.1-4 only, the last version that successfully
  built in Ubuntu.  The patch solves the build failure there... but does not
  solve the build failure in 0.7.4, for reasons that currently elude me.

> I briefly looked at whether your custom LD_PRELOAD wrapper could be replaced
> with libeatmydata, but I see that libeatmydata only handles O_SYNC and
> O_DSYNC, not O_DIRECT.  Do you think it would make sense to ask libeatmydata
> to filter O_DIRECT as well, to reduce the need for maintaining this separate
> .so?
> 
> -- 
> Steve Langasek   Give me a lever long enough and a Free OS
> Debian Developer   to set it on, and I can move the world.
> Ubuntu Developerhttp://www.debian.org/
> slanga...@ubuntu.com vor...@debian.org

> diff -Nru thin-provisioning-tools-0.7.4/debian/control 
> thin-provisioning-tools-0.7.4/debian/control
> --- thin-provisioning-tools-0.7.4/debian/control  2017-11-01 
> 14:50:39.0 -0700
> +++ thin-provisioning-tools-0.7.4/debian/control  2018-03-19 
> 14:10:28.0 -0700
> @@ -1,8 +1,7 @@
>  Source: thin-provisioning-tools
>  Section: admin
>  Priority: optional
> -Maintainer: Ubuntu Developers 
> -XSBC-Original-Maintainer: Debian LVM Team 
> 
> +Maintainer: Debian LVM Team 
>  Uploaders: Bastian Blank 
>  Build-Depends:
>   debhelper (>= 9),
> diff -Nru thin-provisioning-tools-0.7.4/debian/unit-tests/preload.c 
> thin-provisioning-tools-0.7.4/debian/unit-tests/preload.c
> --- thin-provisioning-tools-0.7.4/debian/unit-tests/preload.c 2017-11-01 
> 14:50:39.0 -0700
> +++ thin-provisioning-tools-0.7.4/debian/unit-tests/preload.c 2018-03-19 
> 14:10:17.0 -0700
> @@ -4,13 +4,17 @@
>  #include 
>  #include 
>  
> -static int (*orig_open)(const char *pathname, int flags, int mode);
> +static int (*orig_open)(const char *pathname, int flags, mode_t mode);
> +static int (*orig_openat)(int dirfd, const char *pathname, int flags, mode_t 
> mode);
>  
>  __attribute__((constructor))
>  static void constructor() {
>orig_open = dlsym(RTLD_NEXT, "open");
>if (!orig_open)
>  abort();
> +  orig_openat = dlsym(RTLD_NEXT, "openat");
> +  if (!orig_openat)
> +abort();
>  }
>  
>  int open(const char *file, int oflag, ...) {
> @@ -51,3 +55,34 @@
>  int __open64_2(const char *file, int oflag) {
>return orig_open(file, (oflag & ~O_DIRECT) | O_LARGEFILE, 0);
>  }
> +
> +int openat(int dirfd, const char *file, int oflag, ...) {
> +  int mode = 0;
> +
> +  oflag &= ~O_DIRECT;
> +
> +  if (oflag & O_CREAT) {
> +va_list arg;
> +va_start(arg, oflag);
> +mode = va_arg(arg, int);
> +va_end(arg);
> +  }
> +
> +  return orig_openat(dirfd, file, oflag, mode);
> +}
> +
> +int openat64(int dirfd, const char *file, int oflag, ...) {
> +  int mode = 0;
> +
> +  oflag |= O_LARGEFILE;
> +  oflag &= ~O_DIRECT;
> +
> +  if (oflag & O_CREAT) {
> +va_list arg;
> +va_start(arg, oflag);
> +mode = va_arg(arg, int);
> +va_end(arg);
> +  }
> +
> +  return orig_openat(dirfd, file, oflag, mode);
> +}


-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#892226: [Pkg-fonts-devel] Bug#892226: fonts-noto-unhinted: mathematical and arrow symbols missing, that existed previously

[Ciaran Power]

Hi Jonas,

2018-03-06 22:40 GMT-03:00 Jonas Smedegaard :
> Since you mention previously using unhinted fonts, could you please try
> fetch the current _unhinted_ fonts from upstream and check if the
> symbols are missing there as well?  If so, then we should maybe consider
> packaging the unhinted fonts too.

I don't see what I'm looking for in either the hinted or unhinted
fonts in noto-fonts on github.


It seems a bunch of symbols were moved from Google's noto-fonts
repository into noto-fonts-alpha around commit
bc9353da6f625b7a47035de952c2e8fd9e3ae889 (in noto-fonts). I think this
is really a regression, and shouldn't have been pulled into Debian.
Symbols that were previously in "NotoFontsSymbols-*" are no longer
found in noto-fonts, but are in noto-fonts-alpha.

A list of the glyphs I am using, which are no longer found (with some
exceptions scattered about) in the .deb (probably not the complete
set, just what I noticed):
↑ U+2191 UPWARDS ARROW
→ U+2192 RIGHTWARDS ARROW
↓ U+2193 DOWNWARDS ARROW
↦ U+21A6 RIGHTWARDS ARROW FROM BAR
↶ U+21B6 ANTICLOCKWISE TOP SEMICIRCLE ARROW
⇐ U+21D0 LEFTWARDS DOUBLE ARROW
⇑ U+21D1 UPWARDS DOUBLE ARROW
⇒ U+21D2 RIGHTWARDS DOUBLE ARROW
⇓ U+21D3 DOWNWARDS DOUBLE ARROW
⇔ U+21D4 LEFT RIGHT DOUBLE ARROW
⇞ U+21DE UPWARDS ARROW WITH DOUBLE STROKE
⇟ U+21DF DOWNWARDS ARROW WITH DOUBLE STROKE
⇠ U+21E0 LEFTWARDS DASHED ARROW
⇡ U+21E1 UPWARDS DASHED ARROW
⇢ U+21E2 RIGHTWARDS DASHED ARROW
⇣ U+21E3 DOWNWARDS DASHED ARROW
⇥ U+21E5 RIGHTWARDS ARROW TO BAR
⇱ U+21F1 NORTH WEST ARROW TO CORNER
⇲ U+21F2 SOUTH EAST ARROW TO CORNER
∀ U+2200 FOR ALL
∂ U+2202 PARTIAL DIFFERENTIAL
∃ U+2203 THERE EXISTS
∅ U+2205 EMPTY SET
∇ U+2207 NABLA
∈ U+2208 ELEMENT OF
− U+2212 MINUS SIGN
∘ U+2218 RING OPERATOR
√ U+221A SQUARE ROOT
∝ U+221D PROPORTIONAL TO
∞ U+221E INFINITY
∡ U+2221 MEASURED ANGLE
∥ U+2225 PARALLEL TO
∧ U+2227 LOGICAL AND
∨ U+2228 LOGICAL OR
∩ U+2229 INTERSECTION
∪ U+222A UNION
∫ U+222B INTEGRAL
⊂ U+2282 SUBSET OF
⊥ U+22A5 UP TACK
⌦ U+2326 ERASE TO THE RIGHT
⌧ U+2327 X IN A RECTANGLE BOX
⌫ U+232B ERASE TO THE LEFT
⎀ U+2380 INSERTION SYMBOL
⏎ U+23CE RETURN SYMBOL
␣ U+2423 OPEN BOX
♀ U+2640 FEMALE SIGN
♂ U+2642 MALE SIGN
⚥ U+26A5 MALE AND FEMALE SIGN
⟨ U+27E8 MATHEMATICAL LEFT ANGLE BRACKET
⟩ U+27E9 MATHEMATICAL RIGHT ANGLE BRACKET


I feel that Debian should go back to the previous version of the
NotoSansSymbols* files, but I understand that needs to be balanced
against the additional work/problems with packaging an older version.
The symbols I have listed are probably not used by many, but on the
other hand users probably expect a relatively complete set of symbols
from noto ("no tofu").


For my purposes I can get what I need from the following unhinted
files in github/noto-fonts-alpha:
NotoSansSymbols-Regular.ttf
NotoSansSymbols2-Regular.ttf
NotoSansMathGX.ttf
which is a bit more work for me, but not too bad.

Thanks,
Ciarán

Bug#889027: quodlibet: New upstream version (4.0.2) available (Python 3 support)

[Michael Gardner]

Ondřej, could you confirm you're still actively maintaining this package?

Bug#893563: whiptail has priority important

[Christian Göttsche]

Package: whiptail
Version: 0.52.20-3
Severity: wishlist

Could you consider lowering the priority of whiptail from important to standard?
Packages using whiptail should depend on it and the change would help
keeping minimal systems clean.

Bug#721358: bug#28574: coreutils: use dummy man when cross build

[Karsten Merker]

Control: user debian-ri...@lists.debian.org
Control: usertag -1 + riscv64

[coreutils not cross-buildable due to help2man issues]

On Sat, Sep 30, 2017 at 08:56:53PM -0700, Pádraig Brady wrote:
> On 23/09/17 20:18, Peter Bohning wrote:
> > Cross compiling for aarch64 from amd64
> >  
> > Is there no way to disable the man pages in configure options?  Thanks.
> >  
> > https://lists.gnu.org/archive/html/coreutils/2014-11/msg0.html
> 
> I've seen this issue in various places now (CC'd).
> 
> We should probably reinstate distribution of man pages
> since these generated pages are so similar on various systems.
> Also given the amount of old ChangeLogs removed recently
> I don't think the addition of 273K (uncompressed) is prohibitive.
> 
> The attached was tested in these modes:
>  git repo build
>  tarball build with/without help2man
>  tarball vpath build with/without help2man
>  make distcheck
>  make install  (and ensure only enabled program man pages installed)
> 
> I've not applied this yet, but hope to soon after a bit more testing.
> 
> cheers,
> Pádraig

Hello,

we are currently in the process of bootstrapping a new Debian
architecture (riscv64, https://wiki.debian.org/RISC-V) and
therefore affected by this problem.  The underlying issue has
been solved in upstream coreutils 8.29, so I would like to ask
whether it would perhaps be possible for you to update coreutils
in unstable to version 8.29.

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

Bug#893508: qtcreator: please use dh_auto_configure

[Pino Toscano]

In data lunedì 19 marzo 2018 15:10:43 CET, Helmut Grohne ha scritto:
> diff --minimal -Nru qtcreator-4.5.2/debian/rules qtcreator-4.5.2/debian/rules
> --- qtcreator-4.5.2/debian/rules2018-03-17 17:26:40.0 +0100
> +++ qtcreator-4.5.2/debian/rules2018-03-19 14:37:33.0 +0100
> @@ -5,15 +5,6 @@
>  
>  DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
>  
> -export CFLAGS := $(shell dpkg-buildflags --get CFLAGS) $(shell 
> dpkg-buildflags --get CPPFLAGS)
> -export CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS) $(shell 
> dpkg-buildflags --get CPPFLAGS)
> -export LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS) -Wl,--as-needed

Your patch drops the as-needed linking mode.

-- 
Pino Toscano

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

Bug#893458: libundead depends on cruft packages.

[Matthias Klumpp]

2018-03-19 9:29 GMT+01:00 Andreas Tille :
> Hi,
>
> On Mon, Mar 19, 2018 at 02:51:38AM +, peter green wrote:
>> Package: libundead
>> Version: 1.0.9-1
>> Severity: serious
>>
>> libundead-dev depends on libphobos2-ldc-dev
>> libundead0 depends on libphobos2-ldc76
>>
>> Neither of these packages is built by ldc anymore. They seem to have been 
>> replaced by  libphobos2-ldc-shared-dev and libphobos2-ldc-shared78
>>
>> It seems there has not been an attempt to been an attempt to binnmu 
>> libundead for this transition in Debian. When we binnmu'd it in raspbian the 
>> dependency on libphobos2-ldc76 was replaced by libphobos2-ldc-shared78 but 
>> the dependency on libphobos2-ldc-dev remained.
>
> The depencency on libphobos2-ldc-dev was explicitly added by Matthias
> Klumpp.  I guess it needs to be replaced by libphobos2-ldc-shared-dev
> but want to let Matthias confirm this assumption before uploading.

Adding that explicit dependency was a mistake on my side - since it is
the compiler's standard library, and since we don't actually ship any
D code that doesn't depend on it, having that explicit dependency
doesn't make sense. And even if you compile without Phobos, any D
compiler will pull it in on Debian anyway, so if you have a D
compiler, you have Phobos too.

I dropped the dependency in Git, and also made the package use
dh-dlang to pick the right compiler and compiler flags.
Feel free to upload the changes if you want to, and thanks for asking
about the dependency!

Cheers,
Matthias


-- 
I welcome VSRE emails. See http://vsre.info/

Bug#893540: telegram-desktop: Fails to build with Qt 5.10

[Коля Гурьев]

Hi,

To build the package in chroot, mount /dev/shm directory using the next
command:

sudo mount --bind /dev/shm /path/to/chroot/dev/shm

I hope this will fix the configuring error.

Bug#893562: please add -static-libstdc++ and -static-libgcc to target

[Gianluigi Tiesi]

Package: gdb-mingw-w64-target
Version: 10.5
Severity: wishlist

Hi, it would be nice to have libgcc and libstdc++ static linked on
the target gdbserver, it's more easy to debug without two additional
dll, I've added:

-static-libstdc++ -static-libgcc

to

DEB_LDFLAGS_MAINT_APPEND

the executable size is increased by rougly 100-200k

Regards



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

Kernel: Linux 4.9.0-6-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: sysvinit (via /sbin/init)

Bug#893561: libtablelayout-java: license does not seem to meet the DFSG

[Francesco Poli (wintermute)]

Package: libtablelayout-java
Version: 20090826-3
Severity: serious
Justification: Policy 2.2.1

Hello!
Thanks for maintaining this package in Debian.

I noticed that the license was
[discussed](https://lists.debian.org/debian-legal/2009/06/msg00050.html)
on debian-legal a long time ago.
My
[opinion](https://lists.debian.org/debian-legal/2009/06/msg00053.html)
was that at least two clauses fail to meet the DFSG.

The debian/copyright file states, in part:

| The source code has been modified to make the package suitable for main (see
| license III. 4.). The package namespace has been changed from
| info.clearthought.layout to org.debian.tablelayout.

Personally, I don't think that applying a patch that changes the namespace
is enough to make the package suitable for Debian main.
I mean: it's true that it is now possible to create drop-in replacements
for the Debian package (without further changing the namespace), but it is
still forbidden to create a modified version that changes the namespace
back to "info.clearthought".

I think that this restriction goes beyond what is allowed by DFSG#4.

Additionally, the license is clearly GPL-incompatible, which may
be an issue for other packages that link with this library.


Is it possible to persuade the upstream copyright holder to
drop clauses III.3 and III.4?
Or, even better, to re-license the library under well-vetted and
clearly DFSG-free terms, such as the
[Expat/MIT license](http://www.jclark.com/xml/copying.txt)
or the
[zlib license](http://www.zlib.net/zlib_license.html)
?

I hope this can be done.
Thanks for your time and helpfulness!

Bug#869986: pacemaker FTBFS: missing symbols

[Ferenc Wágner]

Control: fixed 869986 1.1.18~rc3-1
Control: done 869986

Pacemaker builds again for some time, looks like the new upload was
enough to fix this breakage after all.
-- 
Feri

Bug#893560: gnucash: Gnucash does not update currency EUR/USD

[Olivier]

Package: gnucash
Version: 1:2.6.18-1
Severity: normal
Tags: upstream

Dear Maintainer,

I'm using Gnucash with EUR as defaut currency.
I would like to use currency download (throught Perl:Finance:Quote), in order
to automaticaly convert USD account balanceq to EUR.

Procedure:
- ISSUE 1:
Start gnucash with :
LANG=C gnucash
Tools / Security editor / Currency / Select USD / Edit
 Select Get Online Quote + Single + Currency
 Click on OK
Tool / Price Editor / Get quote
 On "Currencies / Euro" or "Currency / USD", there is no quote update
 => Issue


- ISSUE 2:
If I try to use an another currency source :
Tools / Security editor / Currency / Select USD / Edit
 Select Get Online Quote
 Select Multiple
 Select any possible source
 Click on OK
 Click on Edit
 => "Single + Currency" are still selected, instead of "Multiple + any source"
 Try to update currency : Same issue as upper, no currency updated


- ISSUE 3:
Start gnucash with :
LANG=fr_FR.UTF-8 gnucash
Tool / Price Editor / Get quote
 On "Currencies / Euro" or "Currency / USD", there is no quote update
 A french dialog box error message with "Not possible to download quotes for
elements:
 CURRENCY:USD
 Do you wan to continue by using only good quotation ?"
 YES / No button


According to upper message, I guess that gnucash does not send to "gnc-fq-dump"
the good parameter.
Indeed, If I run manually :

$ gnc-fq-dump yahoo_json EURUSD
Finance::Quote fields Gnucash uses:
symbol: EURUSD   <=== required
  date: ** missing **<=== recommended
  currency: ** missing **<=== required
  last:  <=\
   nav:  <=== one of these
 price:  <=/
  timezone:  <=== optional

** This stock quote cannot be used by GnuCash!

=> FAILURE

The good usage is :

$ gnc-fq-dump yahoo_json EURUSD=X
Finance::Quote fields Gnucash uses:
symbol: EURUSD=X <=== required
  date: 03/19/2018   <=== recommended
  currency: USD  <=== required
  last: 1.2341108<=\
   nav:  <=== one of these
 price:  <=/
  timezone:  <=== optional


This is match with Yahoo web site : https://finance.yahoo.com/quote/EURUSD=X



If I create a new gnucash file "from scratch", issue is the same.

I don't have currency update since mid-2016, so issue may appear many months
before.

On the other hand, quote update for standard Yahoo quote are working fine, by
selecting "Yahoo as JSON" source.

Thanks for your help !

Configuration:
Debian testing
Gnucash 1:2.6.18-1  (unstable)
libfinance-quote-perl   1.47-1  (testing + unstable)

Best regards,

  Olivier




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

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

Versions of packages gnucash depends on:
ii  gnucash-common 1:2.6.18-1
ii  guile-2.0  2.0.13+1-4+b1
ii  guile-2.0-libs 2.0.13+1-4+b1
ii  libaqbanking35 5.7.8-1
ii  libaqbanking35-plugins 5.7.8-1
ii  libc6  2.27-2
ii  libcairo2  1.15.10-1
ii  libcrypt-ssleay-perl   0.73.04-2+b2
ii  libdate-manip-perl 6.70-1
ii  libdbi10.9.0-5
ii  libfinance-quote-perl  1.47-1
ii  libgdk-pixbuf2.0-0 2.36.11-1
ii  libglib2.0-0   2.54.3-2
ii  libgnomecanvas2-0  2.30.3-3
ii  libgoffice-0.8-8   0.8.17-8
ii  libgtk2.0-02.24.32-1
ii  libgwengui-gtk2-0  4.20.0-1
ii  libgwenhywfar604.20.0-1
ii  libhtml-tableextract-perl  2.15-1
ii  libhtml-tree-perl  5.07-1
ii  libktoblzcheck1v5  1.49-4
ii  libofx71:0.9.12-1
ii  libpango-1.0-0 1.40.14-1
ii  libpangocairo-1.0-01.40.14-1
ii  libpython2.7   2.7.14-6
ii  libsecret-1-0  0.18.5-6
ii  libwebkitgtk-1.0-0 2.4.11-3
ii  libwww-perl6.31-1
ii  libx11-6   2:1.6.4-3
ii  libxml22.9.4+dfsg1-6.1
ii  libxslt1.1 1.1.29-5
ii  perl   5.26.1-5
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages gnucash recommends:
ii  dbus1.12.6-2
ii  dbus-x111.12.6-2
ii  gnucash-docs2.6.17-1
ii  python-gnucash  1:2.6.18-1
ii  yelp3.26.0-2

Versions of packages gnucash suggests:
pn  libdbd-mysql
pn  libdbd-pgsql
pn  libdbd-sqlite3  

-- no debconf information

Bug#893559: solaar: Graphical UI (panel icon) report "no receiver", "solaar-cli show -v" works

[Alf]

Package: solaar
Version: 0.9.2+dfsg-8
Severity: important

Dear Maintainer,

   * What led up to the situation?
Installing solaar in Debian-testing under XFCE with icon theme "Tango" and
adding it to the startup list in XFCE settings.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
There is no way to get it working with icon theme Tango.

Situation is somewhat
better with icon theme "Adwaita", however still it happens that it does not
find a receiver. If now I quit solaar, run "solaar show -v" in a X-term and
start solaar again it works perfectly - until I logout and -in again.
Then I have to call solaar-cli again to get the UI work.

As said, wit icon theme Tango there is no way to get it work.
In Stretch all warks fine also with Tango.

For completeness here the output of soolar-cli:
Unifying Receiver
   Device path  : /dev/hidraw2
   USB id   : 046d:c52b
   Serial   : 4A6A9FA2
 Firmware   : 12.03.B0025
 Bootloader : 02.15
 Other  : AA.AA
   Has 1 paired device(s) out of a maximum of 6 .
   Notifications: 0x000900 = wireless, software present
   Device activity counters: 1=204

1: Wireless Trackball M570
   Codename : M570
   Kind : mouse
   Wireless PID : 1028
   Protocol : HID++ 1.0
   Polling rate : 8 ms
   Serial number: BD48472C
Firmware: 26.00.B0003
  Bootloader: 02.06
   Other: 00.01
   The power switch is located on the base.
   Notifications: 0x10 = battery status.
   Battery: 65%, discharging,


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

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

Versions of packages solaar depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.66
ii  gir1.2-gtk-3.0 3.22.28-1
ii  passwd 1:4.5-1
ii  python 2.7.14-4
ii  python-gi  3.26.1-2
ii  python-pyudev  0.21.0-1
ii  udev   238-2

Versions of packages solaar recommends:
ii  gir1.2-notify-0.7  0.7.7-3
ii  python-dbus1.2.6-1
ii  systemd238-2
ii  upower 0.99.7-2

Versions of packages solaar suggests:
pn  gir1.2-appindicator3-0.1  
pn  solaar-gnome3 

-- Configuration Files:
/etc/xdg/autostart/solaar.desktop changed:
[Desktop Entry]
Name=Solaar
Comment=Logitech Unifying Receiver peripherals manager
Exec=solaar
Icon=solaar
StartupNotify=false
Terminal=false
Type=Application
Keywords=logitech;unifying;receiver;mouse;keyboard;
Categories=Utility;GTK;


-- debconf information:
* solaar/use_plugdev_group: true

Bug#893236: activemq FTBFS with openjdk-9

[Markus Koschany]

clone 893236 -1
reassign -1 src:openjdk-9
retitle -1 openjdk9: NullPointerException when building MethodSubHeader
forwarded -1 https://bugs.openjdk.java.net/browse/JDK-8199307
thanks

The NullPointerException looks like an OpenJDK bug to me. This was
already reported upstream. The doclint feature is already set to "none"
in activemq, so I would expect that any javadoc warning is not treated
as an error. Currently the only way to work around this for activemq is
to disable the documentation completely.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#893557: thin-provisioning-tools: FTBFS with glibc 2.17

[Steve Langasek]

Package: thin-provisioning-tools
Version: 0.7.4-2
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Hi Bastian,

In Ubuntu, thin-provisioning-tools 0.7.4-2 fails to build on ppc64el with an
ICE in the compiler while building the test suite.  An strace implies that
this is because your LD_PRELOAD wrapper has interposed open(), but not
openat().

If I extend the wrapper as in the attached patch to cover openat(), the
package now builds.

This build failure is probably not reproducible yet in Debian, but I expect
it will be once Debian moves to glibc 2.17.

I briefly looked at whether your custom LD_PRELOAD wrapper could be replaced
with libeatmydata, but I see that libeatmydata only handles O_SYNC and
O_DSYNC, not O_DIRECT.  Do you think it would make sense to ask libeatmydata
to filter O_DIRECT as well, to reduce the need for maintaining this separate
.so?

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru thin-provisioning-tools-0.7.4/debian/control 
thin-provisioning-tools-0.7.4/debian/control
--- thin-provisioning-tools-0.7.4/debian/control2017-11-01 
14:50:39.0 -0700
+++ thin-provisioning-tools-0.7.4/debian/control2018-03-19 
14:10:28.0 -0700
@@ -1,8 +1,7 @@
 Source: thin-provisioning-tools
 Section: admin
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian LVM Team 

+Maintainer: Debian LVM Team 
 Uploaders: Bastian Blank 
 Build-Depends:
  debhelper (>= 9),
diff -Nru thin-provisioning-tools-0.7.4/debian/unit-tests/preload.c 
thin-provisioning-tools-0.7.4/debian/unit-tests/preload.c
--- thin-provisioning-tools-0.7.4/debian/unit-tests/preload.c   2017-11-01 
14:50:39.0 -0700
+++ thin-provisioning-tools-0.7.4/debian/unit-tests/preload.c   2018-03-19 
14:10:17.0 -0700
@@ -4,13 +4,17 @@
 #include 
 #include 
 
-static int (*orig_open)(const char *pathname, int flags, int mode);
+static int (*orig_open)(const char *pathname, int flags, mode_t mode);
+static int (*orig_openat)(int dirfd, const char *pathname, int flags, mode_t 
mode);
 
 __attribute__((constructor))
 static void constructor() {
   orig_open = dlsym(RTLD_NEXT, "open");
   if (!orig_open)
 abort();
+  orig_openat = dlsym(RTLD_NEXT, "openat");
+  if (!orig_openat)
+abort();
 }
 
 int open(const char *file, int oflag, ...) {
@@ -51,3 +55,34 @@
 int __open64_2(const char *file, int oflag) {
   return orig_open(file, (oflag & ~O_DIRECT) | O_LARGEFILE, 0);
 }
+
+int openat(int dirfd, const char *file, int oflag, ...) {
+  int mode = 0;
+
+  oflag &= ~O_DIRECT;
+
+  if (oflag & O_CREAT) {
+va_list arg;
+va_start(arg, oflag);
+mode = va_arg(arg, int);
+va_end(arg);
+  }
+
+  return orig_openat(dirfd, file, oflag, mode);
+}
+
+int openat64(int dirfd, const char *file, int oflag, ...) {
+  int mode = 0;
+
+  oflag |= O_LARGEFILE;
+  oflag &= ~O_DIRECT;
+
+  if (oflag & O_CREAT) {
+va_list arg;
+va_start(arg, oflag);
+mode = va_arg(arg, int);
+va_end(arg);
+  }
+
+  return orig_openat(dirfd, file, oflag, mode);
+}

Bug#861343: debootstrap: hardcodes mawk as awk provider

[Raphael Hertzog]

Hi Hideki,

On Mon, 19 Mar 2018, Hideki Yamane wrote:
>  However, in scripts/*, there's unnecessary mawk hardcode line and
>  we can remove it safely as attached patch.
[...]
> - ln -sf mawk "$TARGET/usr/bin/awk"
> + ln -sf awk "$TARGET/usr/bin/awk"

Huh? This doesn't make any sense. You are creating a symlink named "awk" that
points to itself. And you will have broken everything.

The problem is the lack of /usr/bin/awk because that file is handled by
update-alternatives which can't be run in the early steps. So it's
manually created and it needs to point to the awk alternative that
has been unpacked earlier.

At best you can try to match /usr/bin/*awk to try to guess how the
awk executable is named and use that to look up the package name
(for the x_core_install call that also hardcodes the mawk name)
and create the appropriate symlink (which will get replaced by
the update-alternatives managed one).

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

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

Bug#888244: apparmor: Convert quilt patch series to per-topic subdirectories managed by gbp-pq

[Tyler Hicks]

On 03/18/2018 09:24 AM, intrigeri wrote:
> Hi,
> 
> Tyler Hicks:
>>> 3. Give me the go ahead and then I'll:
>>>
>>>- refresh the {debian,ubuntu}/gbp-pq branches
>>>- merge the {debian,ubuntu}/gbp-pq branches respectively into
>>>  {debian,ubuntu}/master
>>>- push {debian,ubuntu}/master
>>>- release & upload to Debian sid
>>>- ask you to release & upload to Ubuntu
> 
>> I've taken a quick look at the gbp-pq branches and it sounds like Steve
>> did, as well. I see the value there so you've got the go ahead. :)
> 
> Done. So check the current ubuntu/master and if suitable, upload
> to Ubuntu.

I've finalized, tagged, and pushed ubuntu/master. I've also uploaded to
Ubuntu Bionic.

Tyler



signature.asc
Description: OpenPGP digital signature

Bug#893556: libusb-0.1-4 has priority important

[Christian Göttsche]

Package: libusb-0.1-4
Version: 2:0.1.12-31
Severity: Important

Are there any reasons why this library has a priority of important?
If not, please lower to optional.

Bug#893555: matlab2tikz: autopkgtest failure with new versions of octave

[Graham Inggs]

Source: matlab2tikz
Version: 1.1.0-1
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest
Tags: patch

Hi Maintainer

Since octave 4.2.1-2 was uploaded to unstable on 2017-06-30,
matlab2tikz's autopkgtests have been failing [1].

Łukasz 'sil2100' Zemczak prepared a patch (attached) and forwarded it
upstream [2].
Since the upload of octave 4.2.2-1, an additional test (errorBars2)
fails.  Also attached is a patch I prepared for that.

Regards
Graham


[1] https://ci.debian.net/packages/m/matlab2tikz/unstable/amd64/
[2] https://github.com/matlab2tikz/matlab2tikz/pull/996
Description: Refresh test result hashes for newer octave
 Due to changes in octave 4.2.1, the resulting .tex files now have an
 additional batch of styles for axes. To accomodate this change we need to
 use different test result hashes - and for this reason we create a new test
 suite file.
 The forwarded change to upstream has different hashes as the develop branch
 has different tests than those we have in the current Ubuntu release.
Author: Łukasz 'sil2100' Zemczak 
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/matlab2tikz/+bug/1699176
Forwarded: https://github.com/matlab2tikz/matlab2tikz/pull/996
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/

--- /dev/null
+++ b/test/suites/ACID.Octave.4.2.0.md5
@@ -0,0 +1,87 @@
+alphaImage : a51ff2c6514fb5606ee2fcb732edc7ea
+alphaTest : 0aabea57e8351373e2c3090fa1929435
+annotationAll : 5139104b005a70d3650c6dedb8f1dc7e
+annotationSubplots : 3da2ff3cadd2167ab1726c88f18a8a63
+annotationText : efe23b1567345ec24564b598c0d2c146
+annotationTextUnits : 0c874e12ee2167ffe041b48ab2124417
+areaPlot : cdb88d8449ea9275c7eeed21c236e055
+axesColors : 45751a2a4fd30e0c888237721c0ae018
+axesLocation : 27dd4473cb5871188a20d7e6cbc0d171
+bars : 15a269e905602896394eabd367040ce1
+besselImage : 0ffc3e10adb87029b44cbeb4bc435e07
+colorbarLabelTitle : 272a4d2f645b296e43c01f4ab2ae25a4
+colorbarLogplot : cb326bbb54e486a40d387acfe82f1b72
+colorbarManualLocationLeftIn : d2d90ddaa56b9f13d009a595c21e9601
+colorbarManualLocationLeftOut : dea8de2bdf0d866dc3f4f2b8327ea494
+colorbarManualLocationRightIn : c8866d76fee1a0876cf3f46aa5bb5761
+colorbarManualLocationRightOut : 81b67065a6281c3de6c1a9181d4dfcbc
+colorbars : 13b6b31da1f9aef218ef68a6a2c4bbc5
+compassplot : 94efa27f5503d3a56e6b40a0ca0f75d1
+contourPenny : fbd639280f4c31dcce7d463e4eac27f4
+customLegend : 7b0d1d80a2f72bc920d869151ffe96c1
+decayingharmonic : a5551e12b79edd8f32bd5d91ae5fa561
+double_axes : 125855bab62dbd8a599bfb6d9d2a041f
+double_axes2 : 6cd1b9ea3b7ae29801738674446e5f64
+errorBars : 52e1abac8c4ba10d9427cebc9e6845db
+errorBars2 : 3b9d45c6f5e37317a1a869cc961880d9
+herrorbarPlot : 92c6a3ebd7e6194362b31117b1e52d92
+imageOrientation_PNG : 8086dd5610c028cf75501954cbaccf2c
+imageOrientation_inline : 02c0fb3e810aab39cb690e0fa3f8b7eb
+imagescplot : 88328b4f32c5ed1cc4e0ad09ea7f47cb
+imagescplot2 : 39ce8c49f28f3ce90a6bd5a9d0f1cd42
+latexInterpreter : 73b51aed59a6644c15f1561e51ecbf6d
+latexmath2 : 5359827e1d218311bf80228f89deffdf
+legendplot : 5f351094a8e4cd2192fe7cbb2859fd5c
+legendplotBoxoff : 2654de1ee49ac8f4d2546eb6f254952f
+legendsubplots : 17c08345bafc58e1562984b37d4e01c9
+linesWithOutliers : 0aa11947614995837eb1ce45265b45f5
+logbaseline : f23182b1e230b1b21244ad9364475863
+logicalImage : 82e9e5ed998aa1ecd78b514d801dc914
+logplot : 5d5c676b2a3338558939d0407171edc6
+manualAlignment : ff6a5307120276310c01fb6f9c223d77
+many_random_points : 44f79b07c32fe2d334cb4d41bb245a2a
+markerSizes : c80e1e82fcd9d7cbcb52265cd966273b
+markerSizes2 : 2bc71206cca5fecdd89ee0ca6e7dec9a
+meshPlot : 390a65be331e6aeab8f4164b36b85e30
+mixedBarLine : 124b6efc0a9b4d350e0f179bdcc794c9
+multiline_labels : 113098f446ba5b37be05b2e495753a38
+multipleAxes : c7c64c5f627f8633ee89ae02ba0b487e
+multiplePatches : 4d77a30b4a6b14772505e0e9c2a727cf
+overlappingPlots : 714f8029c2ad4fc86a8fb5323f35b0e4
+pColorPlot : ce623ad5a9ebf4b3c74d5954027f0631
+parameterCurve3d : ce2a304c64eb5283a40779f6f410d6ba
+peaks_contour : a08b52735b11941aef4194d42c50ca95
+peaks_contourf : bae99cfb0c6d76fbb9eda7cf3253c861
+pixelLegend : 2afe53d2be6f01a41b74c5bd892fda83
+plain_cos : defebe18ad95f9f1b1f823ad96bd12bd
+plotyyLegends : 96cb3c09f470251db4ddf24f59e8e9f4
+polarplot : a663c1b56d3073601536d4dacae5e8a0
+quiver3plot : 5dd5d89ff4c5d3de0c000a999814d10a
+quiveroverlap : f446d413254f3f1e8e4ec449b8a7f813
+quiverplot : 22d70477697462b313c3d56ef78ac9c8
+randomWithLines : 9857814e260c4a929f5f0e9e92ba896d
+rectanglePlot : 045df69771942ea322873279a61c7b9f
+removeOutsideMarker : f9330795ff85ba1ce4753a700825ab8c
+roseplot : 526bbf61758a3ac158b2f1de6a39de73
+scatter3Plot : cede4e9f5248013f47b95e589d805ea8
+scatterPlotMarkers : b9f6262dba1b2035eb14abda46194ba7
+scatterPlotRandom : 4b47c90b5493c5e53c3e60a4681e93fd
+sine_with_annotation : 0b0f9823c6c36cae49d5053d8b984884
+sine_with_markers : 2cf4b72e72482e4b192012c4165ef5b5
+spherePlot : 5b0e48733101f43996cc70c2962b52d8

Bug#893554: range-v3 FTBFS

[Adrian Bunk]

Source: range-v3
Version: 0.3.5-1
Severity: serious

Some recent change in unstable makes range-v3 FTBFS:

https://tests.reproducible-builds.org/debian/history/range-v3.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/range-v3.html

...
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: no 
matching function for call to 'initializer_list(const volatile 
std::initializer_list&)'
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:32: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:47:11: note: candidate: constexpr 
std::initializer_list::initializer_list(const std::initializer_list&) 

 class initializer_list
   ^~~~
/usr/include/c++/7/initializer_list:47:11: note:   conversion of argument 1 
would be ill-formed:
In file included from 
/build/1st/range-v3-0.3.5/include/range/v3/range_fwd.hpp:21:0,
 from 
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:22,
 from /build/1st/range-v3-0.3.5/include/range/v3/core.hpp:17,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:12:
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: binding 
reference of type 'const std::initializer_list&' to 'const volatile 
std::initializer_list' discards qualifiers
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:32: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:47:11: note: candidate: constexpr 
std::initializer_list::initializer_list(std::initializer_list&&) 

 class initializer_list
   ^~~~
/usr/include/c++/7/initializer_list:47:11: note:   conversion of argument 1 
would be ill-formed:
In file included from 
/build/1st/range-v3-0.3.5/include/range/v3/range_fwd.hpp:21:0,
 from 
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:22,
 from /build/1st/range-v3-0.3.5/include/range/v3/core.hpp:17,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:12:
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: cannot 
bind rvalue reference of type 'std::initializer_list&&' to lvalue of type 
'const volatile std::initializer_list'
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:32: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:89:5: note:   initializing argument 1 of 
'constexpr const _Tp* std::begin(std::initializer_list<_Tp>) [with _Tp = int]'
 begin(initializer_list<_Tp> __ils) noexcept
 ^
In file included from 
/build/1st/range-v3-0.3.5/include/range/v3/range_fwd.hpp:21:0,
 from 
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:22,
 from /build/1st/range-v3-0.3.5/include/range/v3/core.hpp:17,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:12:
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: no 
matching function for call to 'initializer_list(const volatile 
std::initializer_list&)'
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:45: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
 ^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:47:11: note: candidate: constexpr 
std::initializer_list::initializer_list(const std::initializer_list&) 

 class initializer_list
   ^~~~
/usr/include/c++/7/initializer_list:47:11: 

Bug#893553: visualvm FTBFS with openjdk-9

[Adrian Bunk]

Source: visualvm
Version: 1.3.9-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/visualvm.html

...
compile:
 [nb-javac] Compiling 15 source files to 
/build/1st/visualvm-1.3.9/netbeans/profiler.oql/build/classes
[parseprojectxml] warning: [options] bootstrap class path not set in 
conjunction with -source 1.6
[parseprojectxml] warning: [options] source value 1.6 is obsolete and will be 
removed in a future release
[parseprojectxml] warning: [options] target value 1.6 is obsolete and will be 
removed in a future release
[parseprojectxml] warning: [options] To suppress warnings about obsolete 
options, use -Xlint:-options.
[parseprojectxml] 
/build/1st/visualvm-1.3.9/netbeans/nbbuild/build/public-package-jars/org-netbeans-api-annotations-common.jar(/org/netbeans/api/annotations/common/NonNull.class):
 warning: Cannot find annotation method 'when()' in type 'Nonnull': class file 
for javax.annotation.Nonnull not found
[parseprojectxml] error: java.nio.file.NoSuchFileException: 
/build/1st/visualvm-1.3.9/netbeans/profiler.oql/build/classes/META-INF/services/org.netbeans.modules.profiler.spi.IconsProvider
[parseprojectxml] warning: No processor claimed any of these annotations: 
org.netbeans.api.annotations.common.NonNull
[parseprojectxml] 
/build/1st/visualvm-1.3.9/netbeans/nbbuild/build/public-package-jars/org-netbeans-api-annotations-common.jar(/org/netbeans/api/annotations/common/NonNull.class):
 warning: Cannot find annotation method 'when()' in type 'Nonnull': class file 
for javax.annotation.Nonnull not found
[parseprojectxml] 1 error
[parseprojectxml] 7 warnings

BUILD FAILED
/build/1st/visualvm-1.3.9/netbeans/nbbuild/templates/projectized.xml:123: The 
following error occurred while executing this line:
/build/1st/visualvm-1.3.9/netbeans/nbbuild/templates/common.xml:220: Compile 
failed; see the compiler error output for details.

Total time: 28 seconds
make[1]: *** [debian/rules:32: override_dh_auto_build] Error 1

Bug#893552: lcm FTBFS with openjdk-9

[Adrian Bunk]

Source: lcm
Version: 1.3.1+repack1-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lcm.html

...
Making all in lcm-java
make[3]: Entering directory '/build/1st/lcm-1.3.1+repack1/lcm-java'
chmod 755 lcm-logplayer-gui
chmod 755 lcm-spy
mkdir -p /build/1st/lcm-1.3.1+repack1/lcm-java/build
CLASSPATH=/build/1st/lcm-1.3.1+repack1/lcm-java/build:.//build/1st/lcm-1.3.1+repack1/lcm-java/build${CLASSPATH:+":$CLASSPATH"}
 /usr/bin/javac -d /build/1st/lcm-1.3.1+repack1/lcm-java/build  -source 1.5 
-target 1.5 -classpath /usr/share/java/jchart2d.jar  lcm/lcm/Provider.java 
lcm/lcm/LogFileProvider.java lcm/lcm/LCMDataOutputStream.java 
lcm/lcm/TCPService.java lcm/lcm/URLParser.java lcm/lcm/LCM.java 
lcm/lcm/MessageAggregator.java lcm/lcm/MemqProvider.java 
lcm/lcm/TCPProvider.java lcm/lcm/LCMSubscriber.java lcm/lcm/LCMEncodable.java 
lcm/lcm/UDPMulticastProvider.java lcm/lcm/LCMDataInputStream.java 
lcm/spy/ObjectPanel.java lcm/spy/SpyPlugin.java lcm/spy/LCMTypeDatabase.java 
lcm/spy/Spy.java lcm/spy/ChannelData.java lcm/spy/ChartData.java 
lcm/spy/ZoomableChartScrollWheel.java lcm/util/ColorMapper.java 
lcm/util/ClassDiscoverer.java lcm/util/ParameterListener.java 
lcm/util/JImage.java lcm/util/BufferedRandomAccessFile.java 
lcm/util/ParameterGUI.java lcm/util/TableSorter.java 
lcm/logging/LogDiagnostic.java lcm/logging/JScrubberListener.java 
lcm/logging/Log.java lcm/logging/LogPlayer.java lcm/logging/JScrubber.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[3]: *** [Makefile:415: classnoinst.stamp] Error 2

Bug#893551: [RFP] listserialportsc

[Geert Stappers]

Package: wnpp
Severity: wishlist

Request for Packaging:  listserialportsc
Which is a build dependency for "arduino"

URL: https://github.com/arduino/listSerialPortsC/
License: GPL3+
Language: C

In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780706#100
is announced some work is allready done.

So expect that this 'RFP' will be soon an 'ITP'.

 
Groeten
Geert Stappers
DD
-- 
Leven en laten leven

Bug#893550: stretch-pu: package astroml-addons/0.2.2-4~deb9u1

[Adrian Bunk]

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

Fix the python3-astroml-addons dependencies:
Depends: {+python3 (<< 3.6), python3 (>= 3.5~), python3:any (>= 3.3.2-2~),+} 
libc6 (>= 2.4), python3-astroml
diff -Nru astroml-addons-0.2.2/debian/changelog 
astroml-addons-0.2.2/debian/changelog
--- astroml-addons-0.2.2/debian/changelog   2016-05-09 23:20:06.0 
+0300
+++ astroml-addons-0.2.2/debian/changelog   2018-03-19 22:27:33.0 
+0200
@@ -1,3 +1,20 @@
+astroml-addons (0.2.2-4~deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for stretch.
+
+ -- Adrian Bunk   Mon, 19 Mar 2018 22:27:33 +0200
+
+astroml-addons (0.2.2-4) unstable; urgency=medium
+
+  * Push Standards-Version to 4.0.0. No changes needed.
+
+  [ Scott Kitterman ]
+  * Correct substitution variable for python3 binary so correct python3
+interpreter depends are provided. Closes: #867243
+
+ -- Ole Streicher   Wed, 05 Jul 2017 09:37:04 +0200
+
 astroml-addons (0.2.2-3) unstable; urgency=low
 
   * Create Python 3 package
diff -Nru astroml-addons-0.2.2/debian/control 
astroml-addons-0.2.2/debian/control
--- astroml-addons-0.2.2/debian/control 2016-05-09 23:17:07.0 +0300
+++ astroml-addons-0.2.2/debian/control 2017-07-05 10:37:04.0 +0300
@@ -16,7 +16,7 @@
python3-nose,
   python3-numpy,
python3-setuptools
-Standards-Version: 3.9.8
+Standards-Version: 4.0.0
 Homepage: http://astroml.github.com/
 Vcs-Git: 
https://anonscm.debian.org/git/debian-astro/packages/astroml-addons.git
 Vcs-Browser: 
https://anonscm.debian.org/cgit/debian-astro/packages/astroml-addons.git
@@ -36,7 +36,7 @@
 
 Package: python3-astroml-addons
 Architecture: any
-Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}, python3-astroml
+Depends: ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends}, 
python3-astroml
 Description: Python 3 Machine Learning library for astronomy (performance 
addons)
  AstroML is a Python module for machine learning and data mining built on
  numpy, scipy, scikit-learn, and matplotlib. It contains a growing library of

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

[c.buhtz]

Dear Gregor,

thank you very much for your fast reply.

> True, this is already reported as #890905/#893138.
> I ('m trying to) merge those two bugs.

Sorry, for reporting again. I noticed that bugs. But as a
Java-foreigner it wasn't clear for me if they address the same issue.

> You can run
> JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref

Something is wrong here. Did openjdk-8 changed a bit?

$ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
Exception in thread "main" java.lang.NoSuchMethodError:
java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer; at
org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:292)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:303)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.closeOutputStream(OutputStreamManager.java:308)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.releaseSub(OutputStreamManager.java:137)
at
org.apache.logging.log4j.core.appender.AbstractManager.stop(AbstractManager.java:86)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:142)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:136)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.stop(AbstractConfiguration.java:359)
at
org.apache.logging.log4j.core.AbstractLifeCycle.stop(AbstractLifeCycle.java:136)
at
org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:550)
at
org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
at
org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
at
org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
at
org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122)
at
org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
at
org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46)
at
org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
at
org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655) at
net.sf.jabref.JabRefMain.(JabRefMain.java:37)



signature.asc
Description: Digital Signature

Bug#829361: clang-x.y-doc: Fix the lintian error 'privacy-breach-uses-embedded-file' [was: Re: Processed: affects 829361]

[Nicholas D Steeves]

Hi Sylvestre,

Thank you for the ping!  Reply follows below.

On Mon, Feb 26, 2018 at 11:02:25PM +0100, Sylvestre Ledru wrote:
> 
> Le 26/02/2018 à 22:51, Nicholas D Steeves a écrit :
> > Hi Sylvestre,
> >
> > On Sun, Feb 11, 2018 at 09:32:17AM +0100, Sylvestre Ledru wrote:
> >> Le 11/02/2018 à 03:17, Nicholas D Steeves a écrit :
> >>> On Sat, Feb 10, 2018 at 09:42:29AM +0100, Sylvestre Ledru wrote:
>  This is caused by a recent change in gold I think.
> 
>  Just add a ; XFAIL: * at in the test to silent it.
> 
>  BTW, in the future, please don't attach the full build log:
>  We just need the error message.
> 
> 
>  S
> 
> 
> >>> Thank you for the tip!  With the two attached patches I'm able to
> >>> continue working towards solving this bug. (really just implementing
> >>> your suggestion, plus a patch refresh)
> >>>
> >>> Oh, and I xzipped them to try to atone for sending uncompressed build
> >>> logs ;-) I'll send only what I suspect are the relevant portions
> >>> (errors) in the future.
> >> Thanks but they were already merged upstream...
> >>
> >> Sylvestre
> > I've been able to solve this by patching various Doxyfile, conf.py,
> > and doxygen.cfg.in.  Before I did that I also:
> >
> > -html_static_path = []
> > +html_static_path = ['_static']
> >
> > for the affected sections.
> >
> > Do you approve of this approach and should I work on patching rules to
> > not fail with this new configuration or would you prefer another
> > approach?
> 
> Sounds good. What are you concerns about this solution?

I'm concerned that it's difficult to debug, and also that the
build-doc target doesn't work...that's one reason why progress has
been so slow!  I've tried a number of methods and I can't get the
llvm-toolchain-5.0 to build at all right now; it hangs indefinitely in
self-tests and dmesg shoes a bunch of segfaults...so I've decided to
just attach my patches for the docs.  IIRC d/rules still needs some
more work to accommodate
d/patches/0048-Set-html_static_path-_static-everywhere.patch

IIRC this patch is part of the commit represented by:
0002-Add-patches-to-use-static-docs-using-Debian-provided.patch


Sincerely,
Nicholas
From e1cb74ef6331b8633589751bea5a9a53eb0d1707 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sat, 10 Feb 2018 20:26:49 -0500
Subject: [PATCH 1/3] Add libjs-mathjax to Build-Depends and to clang-x.y-doc
 Depends.

Signed-off-by: Nicholas D Steeves 
---
 debian/control | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 31dea016..b83de924 100644
--- a/debian/control
+++ b/debian/control
@@ -10,6 +10,7 @@ Build-Depends: debhelper (>= 11~), flex, bison, dejagnu, tcl, expect,
 libjsoncpp-dev, pkg-config,
 lcov, procps, help2man, zlib1g-dev,
 g++-multilib [amd64 i386 kfreebsd-amd64 mips mips64 mips64el mipsel powerpc ppc64 s390 s390x sparc sparc64 x32],
+libjs-mathjax
 #ocaml-nox [amd64 arm64 armel armhf i386],
 #ocaml-findlib [amd64 arm64 armel armhf i386],
 #libctypes-ocaml-dev [amd64 arm64 armel armhf i386],
@@ -84,7 +85,7 @@ Description: clang-based C++ linter tool
 Package: clang-5.0-doc
 Architecture: all
 Section: doc
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, libjs-mathjax
 Description: C, C++ and Objective-C compiler - Documentation
  Clang project is a C, C++, Objective C and Objective C++ front-end
  based on the LLVM compiler. Its goal is to offer a replacement to the
-- 
2.14.2

From 26cc1ca675872273c4732f35854c58ccfc3e000a Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sat, 10 Feb 2018 21:07:21 -0500
Subject: [PATCH 2/3] Add patches to use static docs using Debian-provided
 MathJax

Signed-off-by: Nicholas D Steeves 
---
 ...8-Set-html_static_path-_static-everywhere.patch |  63 +++
 ...49-Use-Debian-provided-MathJax-everywhere.patch | 122 +
 debian/patches/series  |   3 +
 3 files changed, 188 insertions(+)
 create mode 100644 debian/patches/0048-Set-html_static_path-_static-everywhere.patch
 create mode 100644 debian/patches/0049-Use-Debian-provided-MathJax-everywhere.patch

diff --git a/debian/patches/0048-Set-html_static_path-_static-everywhere.patch b/debian/patches/0048-Set-html_static_path-_static-everywhere.patch
new file mode 100644
index ..10663a82
--- /dev/null
+++ b/debian/patches/0048-Set-html_static_path-_static-everywhere.patch
@@ -0,0 +1,63 @@
+From: Nicholas D Steeves 
+Date: Sat, 10 Feb 2018 21:00:55 -0500
+Subject: Set html_static_path = ['_static'] everywhere.
+
+---
+ clang-tools-extra/docs/conf.py | 2 +-
+ clang/docs/analyzer/conf.py| 2 +-
+ clang/docs/conf.py | 2 +-
+ polly/docs/conf.py | 2 +-
+ 4 files changed, 4 insertions(+), 4 deletions(-)
+
+diff --git 

Bug#893549: stretch-pu: package python-django-contact-form/1.3-1+deb9u1

[Adrian Bunk]

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

Fix python3-django-contact-form dependencies:
Depends: [-python-django-] {+python3:any (>= 3.3.2-2~), python3-django+} (>= 
1.0)
diff -Nru python-django-contact-form-1.3/debian/changelog 
python-django-contact-form-1.3/debian/changelog
--- python-django-contact-form-1.3/debian/changelog 2016-12-24 
22:36:37.0 +0200
+++ python-django-contact-form-1.3/debian/changelog 2018-03-19 
22:19:02.0 +0200
@@ -1,3 +1,11 @@
+python-django-contact-form (1.3-1+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Fix incorrect dependencies for
+python3-django-contact-form (Closes: #867426).
+
+ -- Adrian Bunk   Mon, 19 Mar 2018 22:19:02 +0200
+
 python-django-contact-form (1.3-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru python-django-contact-form-1.3/debian/control 
python-django-contact-form-1.3/debian/control
--- python-django-contact-form-1.3/debian/control   2016-12-24 
22:36:12.0 +0200
+++ python-django-contact-form-1.3/debian/control   2018-03-19 
22:19:02.0 +0200
@@ -34,7 +34,7 @@
 Package: python3-django-contact-form
 Architecture: all
 Recommends: python-django-contact-form-doc
-Depends: ${misc:Depends}, ${python:Depends}, python-django (>= 1.0)
+Depends: ${misc:Depends}, ${python3:Depends}, python3-django (>= 1.0)
 Description: extensible contact-form application for Django (Python 3)
  This is a reusable application which simplifies including a contact form 
within
  Django, the Python web framework. It provides a basic contact form which, once

Bug#892590: Review graphite2

[Moritz Mühlenhoff]

On Mon, Mar 19, 2018 at 05:04:17PM +0100, Rene Engelhard wrote:
> I am not going over the .-release procedure for this, I'd have uploaded
> to security, though, but...
> 
> I don't think we should special-case our oldest,
> soon-to-be-not-supported release.

Agreed, it doesn't make sense to fix this bug on it's own. We can
simply piggyback it on the next more severe graphite update.

Cheers,
Moritz

Bug#892810: RFS: zeroc-ice/3.7.0-1 -- New Ice 3.7.0 release

[Jose Gutierrez de la Concha]

Hi,

I have fixed the package to depend on JDK 8 and use it for the build,
there is already a bug to upgrade gradle for JDK 9 support [1]

I have also fixed a few other warnings that show up with lintian and have
to reimort the upstream source to exclude some non DFSG files

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


On Mon, Mar 19, 2018 at 9:47 AM, Jose Gutierrez de la Concha  wrote:

> Hi Adam,
>
> The problem is your build is picking JDK 9 that is not supported by gradle
> 3.x included in SID this requires at least  gradle 4.2.1 [1].
> I guess I should update the package to depend in JDK 8 and ensure this is
> used until gradle 4.2.1 is available
>
> [1] https://blog.gradle.org/java-9-support-update
>
> On Sat, Mar 17, 2018 at 6:08 PM, Adam Borowski 
> wrote:
>
>> On Tue, Mar 13, 2018 at 10:32:29AM +0100, Jose Gutierrez de la Concha
>> wrote:
>> > * Package name: zeroc-ice
>> >   Version : 3.7.0-1
>> >
>> > I requesting sponsor upload for 3.7.0 version for zeroc-ice package it
>> > includes the following
>> > new binary packages and I as DM cannot upload the new version if it
>> > contains new package:
>> >
>> >   ACL dm: NEW uploads are not allowed
>> >
>> >  https://github.com/zeroc-ice/ice-debian-packaging/
>>
>> Alas, it fails to build for me:
>> Could not determine java version from '9.0.4'.
>>
>> Full build log attached.
>>
>>
>> Meow!
>> --
>> ⢀⣴⠾⠻⢶⣦⠀
>> ⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
>> ⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
>> ⠈⠳⣄ A master species delegates.
>>
>
>
>
> --
> José Gutiérrez de la Concha
> ZeroC, Inc.
>



-- 
José Gutiérrez de la Concha
ZeroC, Inc.

Bug#893548: stretch-pu: package python-icalendar/3.8-1+deb9u1

[Adrian Bunk]

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

Fix the python3-icalendar dependencies:
Depends: {+python3-pkg-resources,+} python3-tz, {+python3:any (>= 3.3.2-2~),+} 
python3-dateutil
diff -Nru python-icalendar-3.8/debian/changelog 
python-icalendar-3.8/debian/changelog
--- python-icalendar-3.8/debian/changelog   2014-07-17 08:25:31.0 
+0300
+++ python-icalendar-3.8/debian/changelog   2018-03-19 22:00:53.0 
+0200
@@ -1,3 +1,10 @@
+python-icalendar (3.8-1+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix the python3-icalendar dependencies. (Closes: #867436)
+
+ -- Adrian Bunk   Mon, 19 Mar 2018 22:00:53 +0200
+
 python-icalendar (3.8-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru python-icalendar-3.8/debian/control 
python-icalendar-3.8/debian/control
--- python-icalendar-3.8/debian/control 2014-07-17 08:22:48.0 +0300
+++ python-icalendar-3.8/debian/control 2018-03-19 21:58:29.0 +0200
@@ -50,7 +50,7 @@
 Architecture: all
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- ${python:Depends},
+ ${python3:Depends},
  python3-tz,
  python3-dateutil
 Provides: ${python:Provides}

Bug#893547: ant: please do not emit --ignore-source-errors on Java 9

[Ole Streicher]

Package: ant
Version: 1.9.9-6
Severity: serious

Dear maintainer,

to fix #884187, ant added the option "--ignore-source-errors" to
javadoc. This option is however not available on Java 9, which leads to
FTBFS on some packages: starjava-topcat, starjava-tools. I will merge
the relevant bug reports.

Best regards

Ole

Bug#893546: curl: CVE-2018-1000120 CVE-2018-1000121 CVE-2018-1000122

[Salvatore Bonaccorso]

Source: curl
Version: 7.38.0-4
Severity: serious
Tags: patch security upstream fixed-upstream
Justification: regression with respect to stable with security fixes
Control: fixed -1 7.38.0-4+deb8u10
Control: fixed -1 7.52.1-5+deb9u5

Hi,

the following vulnerabilities were published for curl.

CVE-2018-1000120[0]:
| A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0
| in the FTP URL handling that allows an attacker to cause a denial of
| service or worse.

CVE-2018-1000121[1]:
| A NULL pointer dereference exists in curl 7.21.0 to and including curl
| 7.58.0 in the LDAP code that allows an attacker to cause a denial of
| service

CVE-2018-1000122[2]:
| A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0
| in the RTSP+RTP handling code that allows an attacker to cause a
| denial of service or information leakage

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-1000120
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000120
[1] https://security-tracker.debian.org/tracker/CVE-2018-1000121
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000121
[2] https://security-tracker.debian.org/tracker/CVE-2018-1000122
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000122

Regards,
Salvatore

Bug#892898: reportbug crashes due with UnicodeDecodeError

[Mikulas Patocka]

On Sat, 17 Mar 2018, Nis Martensen wrote:

> control: tags -1 patch
> 
> Thank you for the report. This should fix the crash:
> https://salsa.debian.org/reportbug-team/reportbug/merge_requests/2
> 
> I could not reproduce the problem, though. What does
> DEBCONF_SYSTEMRC=1 DEBCONF_NOWARNINGS=yes debconf-show console-setup
> output on your system?  Is the output not in a consistent encoding?

On Debian-Stretch:
$ DEBCONF_SYSTEMRC=1 DEBCONF_NOWARNINGS=yes debconf-show console-setup
  console-setup/fontsize: 11x22
  console-setup/codeset47: # Latin2 - central Europe and Romanian
  console-setup/fontface47: TerminusBold
  console-setup/charmap47: ISO-8859-2
  console-setup/fontsize-fb47: 11x22 (pouze framebuffer)
  console-setup/use_system_font:
  console-setup/store_defaults_in_debconf_db: true
  console-setup/codesetcode: Lat2
  console-setup/guess_font:
  console-setup/fontsize-text47: 11x22 (pouze framebuffer)
  console-setup/framebuffer_only:

On Debian-Sid:
$ DEBCONF_SYSTEMRC=1 DEBCONF_NOWARNINGS=yes debconf-show console-setup
  console-setup/guess_font:
  console-setup/codesetcode: Lat2
  console-setup/framebuffer_only:
  console-setup/fontsize-text47: 10x20 (pouze framebuffer)
  console-setup/fontsize-fb47: 10x20 (pouze framebuffer)
  console-setup/charmap47: UTF-8
  console-setup/use_system_font:
  console-setup/fontface47: TerminusBold
  console-setup/codeset47: # Latin2 - central Europe and Romanian
  console-setup/store_defaults_in_debconf_db: true
  console-setup/fontsize: 10x20

On Debian-Jessie (the bug also shows up in Jessie, I was wrong in the report):
$ DEBCONF_SYSTEMRC=1 DEBCONF_NOWARNINGS=yes debconf-show console-setup
  console-setup/fontsize-fb47: 11x22 (pouze framebuffer)
  console-setup/fontface47: TerminusBold
  console-setup/use_system_font:
  console-setup/fontsize-text47: 11x22 (pouze framebuffer)
  console-setup/guess_font:
  console-setup/charmap47: ISO-8859-2
  console-setup/framebuffer_only:
  console-setup/store_defaults_in_debconf_db: true
  console-setup/codeset47: # Latin2 - central Europe and Romanian
  console-setup/fontsize: 11x22
  console-setup/codesetcode: Lat2

On Debian Wheezy:
$ DEBCONF_SYSTEMRC=1 DEBCONF_NOWARNINGS=yes debconf-show console-setup
  console-setup/codeset47: # Latin2 - central Europe and Romanian
  console-setup/framebuffer_only:
  console-setup/guess_font:
  console-setup/store_defaults_in_debconf_db: true
  console-setup/use_system_font:
  console-setup/fontsize: 8x16
  console-setup/fontface47: TerminusBold
  console-setup/fontsize-text47: 8x16
  console-setup/charmap47: ISO-8859-2
  console-setup/codesetcode: Lat2
  console-setup/fontsize-fb47: 8x16



But I think the problem is with the 'keyboard-configuration' package - 
reportbug also queries it when reporting a bug for console-setup and it 
shows some non-ascii characters. The resulting encoding is independent on 
the LANG variable.

On Debian-Stretch:
$ DEBCONF_SYSTEMRC=1 DEBCONF_NOWARNINGS=yes /usr/bin/debconf-show 
keyboard-configuration
  keyboard-configuration/variant: Anglické (USA)<--- iso-8859-2
  keyboard-configuration/xkb-keymap: us
  keyboard-configuration/model: Obecné PC 105klávesové (mez.)   <--- iso-8859-2
  keyboard-configuration/layoutcode: us
  keyboard-configuration/variantcode:
  keyboard-configuration/optionscode:
  keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/store_defaults_in_debconf_db: true
  keyboard-configuration/altgr: The default for the keyboard layout
  debian-installer/console-setup-udeb/title:
  keyboard-configuration/modelcode: pc105
  keyboard-configuration/layout:
  keyboard-configuration/other:
  keyboard-configuration/compose: No compose key
  keyboard-configuration/unsupported_layout: true
  keyboard-configuration/unsupported_options: true
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/switch: No temporary switch
  keyboard-configuration/unsupported_config_layout: true
  keyboard-configuration/toggle: No toggling

On Debian-Sid:
$ DEBCONF_SYSTEMRC=1 DEBCONF_NOWARNINGS=yes /usr/bin/debconf-show 
keyboard-configuration
  keyboard-configuration/ctrl_alt_bksp: false
* keyboard-configuration/modelcode: pc104
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/store_defaults_in_debconf_db: true
  debian-installer/console-setup-udeb/title:
* keyboard-configuration/layoutcode: us
* keyboard-configuration/xkb-keymap: us
* keyboard-configuration/other:
  keyboard-configuration/unsupported_layout: true
* keyboard-configuration/model: Obecné PC 104klávesové  <--- 
iso-8859-2
  keyboard-configuration/unsupported_config_options: true
* keyboard-configuration/optionscode:
  keyboard-configuration/unsupported_options: true
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/variant: Anglické (USA)   

Bug#893545: stretch-pu: package nagiosplugin/1.2.2-1+deb9u1

[Adrian Bunk]

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

Fix the dependencies of python3-nagiosplugin from empty to:
Depends: python3:any (>= 3.3.2-2~)
diff -Nru nagiosplugin-1.2.2/debian/changelog 
nagiosplugin-1.2.2/debian/changelog
--- nagiosplugin-1.2.2/debian/changelog 2014-06-04 22:16:17.0 +0300
+++ nagiosplugin-1.2.2/debian/changelog 2018-03-19 21:47:27.0 +0200
@@ -1,3 +1,10 @@
+nagiosplugin (1.2.2-1+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * * Fix the python3-nagiosplugin dependencies. (Closes: #867410)
+
+ -- Adrian Bunk   Mon, 19 Mar 2018 21:47:27 +0200
+
 nagiosplugin (1.2.2-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru nagiosplugin-1.2.2/debian/control nagiosplugin-1.2.2/debian/control
--- nagiosplugin-1.2.2/debian/control   2014-03-20 06:42:36.0 +0200
+++ nagiosplugin-1.2.2/debian/control   2018-03-19 21:47:25.0 +0200
@@ -42,7 +42,7 @@
 
 Package: python3-nagiosplugin
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: Python class library for writing Nagios (Icinga) plugins (Python 
3)
  nagiosplugin is a Python class library which helps writing Nagios
  (or Icinga) compatible plugins easily in Python. It cares for much of