Bug#890374: lirc: 'pre' and 'post' in *.conf is ignored if no 'pre_data', 'post_data'

[Andreas Christ]

Package: lirc
Version: 0.9.4c-9
Severity: normal
Tags: patch

Dear Maintainer,

In a configuration file for a remote control, I use 'post' to send a pulse
(30 us) and a space (460 us) after the data, then ptrail for a trailing pulse.
The 'post' cannot be part of 'data' as the space of 'zero' and 'one' is 650 us
and 830 us (not 460 us). The pulse and space configured in 'post' is, however,
not sent, i.e., the 'post' directive is silently ignored.

Looking into the source code I found the issue in lib/transmit.c:
'post' (i.e., a pulse and a space of specific lengths) is only sent if also
'post_data' (i.e., a sequence of 'zero' and 'one') is configured. The function
send_post(remote) checks if has_post(remote) is true; this is only true if
remote->post_data_bits > 0.

Same applies to 'pre' and 'pre_data'. 

This limitation is not described in the documentation
(see http://www.lirc.org/html/lircd.conf.html). Thus, I suggest to either
update the documentation or fix the code. I prefer the latter as I see no logic
why a directive should be ignored. I attach a patch.

For my specific use case, I have a workaround: I replace 'ptrail' by a single
bit 'post_data'. This only works because the 'ptrail' pulse happens to have
the same duration as the pulse of 'one'. Thus, I now have 'post_data' and
therefore 'post' is no longer ignored. My workaround results in having two
spaces at the end (the space of the 'one' from 'post_data' and the 'gap'); this
does no harm.

I have not found a generic workaround that can be used if the trailing pulse
has a different duration than 'one' and 'zero', nor for repeat sequences.

Best regards

Andreas

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 9.3 (stretch)
Release:9.3
Codename:   stretch
Architecture: armv7l

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

Versions of packages lirc depends on:
ii  init-system-helpers  1.48
ii  libasound2   1.1.3-5+rpi3
ii  libc62.24-11+deb9u1
ii  libftdi1-2   1.3-2
ii  libgcc1  1:6.3.0-18+rpi1
ii  liblirc-client0  0.9.4c-9
ii  liblirc0 0.9.4c-9
ii  libportaudio219.6.0-1
ii  libstdc++6   6.3.0-18+rpi1
ii  libsystemd0  232-25+deb9u1
ii  libudev1 232-25+deb9u1
ii  libusb-0.1-4 2:0.1.12-30
ii  libusb-1.0-0 2:1.0.21-1
ii  lsb-base 9.20161125+rpi1
ii  python3  3.5.3-1

Versions of packages lirc recommends:
pn  gir1.2-vte
ii  python3-gi3.22.0-2
ii  python3-yaml  3.12-1

Versions of packages lirc suggests:
pn  ir-keytable  
pn  lirc-compat-remotes  
pn  lirc-doc 
pn  lirc-drv-irman   
pn  lirc-x   
pn  setserial

-- no debconf information
diff --git a/lib/transmit.c b/lib/transmit.c
index 178e889..28a4af4 100644
--- a/lib/transmit.c
+++ b/lib/transmit.c
@@ -302,20 +302,20 @@ static void send_pre(struct ir_remote* remote)
 {
if (has_pre(remote)) {
send_data(remote, remote->pre_data, remote->pre_data_bits, 0);
+}
if (remote->pre_p > 0 && remote->pre_s > 0) {
send_pulse(remote->pre_p);
send_space(remote->pre_s);
}
-   }
 }
 
 static void send_post(struct ir_remote* remote)
 {
-   if (has_post(remote)) {
if (remote->post_p > 0 && remote->post_s > 0) {
send_pulse(remote->post_p);
send_space(remote->post_s);
}
+if (has_post(remote)) {
send_data(remote, remote->post_data, remote->post_data_bits, 
remote->pre_data_bits + remote->bits);
}
 }

Bug#890373: debhelper: Please fix indendation in postinst-systemd-restart

[Christoph Biedl]

Package: debhelper
Version: 11.1.4
Severity: minor

Dear Maintainer,

while checking the debhelper sniplets created by dh_systemd_* I got
quite confused by the indentation, making me believe it's some
malformatted or even invalid shell script.

Please apply the attached (as it contains tab characters) diff when
convenient.

Regards,

Christoph
diff --git a/autoscripts/postinst-systemd-restart b/autoscripts/postinst-systemd-restart
index a619055..048e968 100644
--- a/autoscripts/postinst-systemd-restart
+++ b/autoscripts/postinst-systemd-restart
@@ -1,6 +1,6 @@
 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
-		if [ -d /run/systemd/system ]; then
-			systemctl --system daemon-reload >/dev/null || true
+	if [ -d /run/systemd/system ]; then
+		systemctl --system daemon-reload >/dev/null || true
 		if [ -n "$2" ]; then
 			_dh_action=restart
 		else


signature.asc
Description: PGP signature

Bug#890372: ddnet: FTBFS on 32bit architectures

[Boyuan Yang]

Source: ddnet
Version: 10.8.6-3
Severity: serious

According to https://buildd.debian.org/status/package.php?p=ddnet , DDNet will
FTBFS on 32bit architectures.

This should be caused by hardcoded path with architecture info as written in
debian/ddnet-tools.install files.

--
Regards,
Boyuan Yang

Bug#887192: singularity-container should depend on e2fsprogs explicitly

[Afif Elghraoui]

على الإثنين 12 شباط 2018 ‫12:02، كتب Andreas Henriksson:
> On Sun, Jan 14, 2018 at 08:11:26PM +0100, Helmut Grohne wrote:
>> Package: singularity-container
> [...]
>> /usr/lib/x86_64-linux-gnu/singularity/cli/image.create.exec contains 
>> mkfs.ext3. According to file it is a Bourne-Again shell script, ASCII text 
>> executable
>> /usr/lib/x86_64-linux-gnu/singularity/cli/image.expand.exec contains e2fsck 
>> and resize2fs. According to file it is a Bourne-Again shell script, ASCII 
>> text executable
> [...]
> 
> Looks to me like there should be a dependency added here for sure.
> 
> Would be great to hear from the maintainers on this!
> 

I would say it should rather be a Recommends. The old default container
image format was based on ext3. It's still supported, but it's just one
of a few possible options.

If that's no problem to you, we can go ahead and make it happen.

Thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#890371: dialign-t FTCBFS: passes -mmmx for !x86 builds

[Helmut Grohne]

Source: dialign-t
Version: 1.0.2-9
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

dialign-t fails to cross build from source, because it determines
compiler flags from the build architecture rather than the host
architecture. Thus cross building for e.g. mips can include -mmmx.

The attached patch goes a little further than s/BUILD/HOST/. It removes
the need to invoke the shell for each make invocation by relying on
dpkg's architecture.mk. It also enables -mmmx for more architectures
that may be relevant by matching on the cpu. It will enable these flags
on e.g.:
 * x32
 * kfreebsd-amd64
 * hurd-i386
 * musl-linux-i386

Please consider applying it.

Helmut
diff --minimal -Nru dialign-t-1.0.2/debian/changelog 
dialign-t-1.0.2/debian/changelog
--- dialign-t-1.0.2/debian/changelog2016-12-17 12:49:37.0 +0100
+++ dialign-t-1.0.2/debian/changelog2018-02-14 07:52:36.0 +0100
@@ -1,3 +1,10 @@
+dialign-t (1.0.2-9.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: fix build/host confusion. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 14 Feb 2018 07:52:36 +0100
+
 dialign-t (1.0.2-9) unstable; urgency=medium
 
   * Team upload.
diff --minimal -Nru dialign-t-1.0.2/debian/rules dialign-t-1.0.2/debian/rules
--- dialign-t-1.0.2/debian/rules2016-12-17 11:36:41.0 +0100
+++ dialign-t-1.0.2/debian/rules2018-02-14 07:52:36.0 +0100
@@ -2,7 +2,10 @@
 
 SRCDIR=$(CURDIR)/source
 
-export SSEFLAGS := $(shell if [ `dpkg-architecture -qDEB_BUILD_ARCH` = amd64 
-o `dpkg-architecture -qDEB_BUILD_ARCH` = i386 ] ; then echo "-mfpmath=sse 
-msse -mmmx" ; fi)
+include /usr/share/dpkg/architecture.mk
+ifneq ($(filter $(DEB_HOST_ARCH_CPU),amd64 i386),)
+export SSEFLAGS = -mfpmath=sse -msse -mmmx
+endif
 export DEB_BUILD_MAINT_OPTIONS += hardening=+all
 
 %:

Bug#808211: saxonhe: Versions 9.6 and 9.7 should be installable at the same time

[Eugene Zhukov]

On Wed, Feb 14, 2018 at 6:50 AM, tony mancill  wrote:
> Hello Eugene,
>
> I'm working on packaging checkstyle 8.8 which requires SaxonHE 9.8.  I
> put together a package for the newer saxonhe (in experimental) and I can
> successful build the r-deps within Debian using ratt.  However,
> comparing the 9.7 and 9.8 libraries with japi-compliance-checker, I'm
> reluctant to upload the package to unstable because there are so many
> breaking changes between the versions.
>
> Do you have any advice or thoughts about what we should do for buster?
>
Hi tony,

Thanks for working on this!
I think we need to ping upstream about missing hej/data folder in the
last tag. Without it xml-maven-plugin or epubcheck won't work [0].
My other concern is Schematron upgrade [1]. We might actually want to
package SaxonHE 9.8.0.7 or newer to support both XSLT 1.0 and 2.0.

[0] https://github.com/IDPF/epubcheck/issues/674#issuecomment-348102028
[1] https://github.com/Schematron/schematron/issues/55

Eugene

Bug#889028: fixed in minissdpd 1.5.20161216-2

Hi,  
  
AFAIK I never changed the file in /etc/default. And even if I did so, the 
package installation should not just abruptlly stop, some sort of problem 
resolution shall be presented to the user.  
I had 0.0.0.0, and minissdpd was not happy with it. Maybe it has been fixed 
since then, since I changed to my wlan interface.  
Will test again with 0.0.0.0  
  
Regards,  
Geoffrey  
  
  
- - - - - -

  


Geoffrey Merck  
F4FXL / KC3FRA  
[http://www.f4fxl.org](http://www.f4fxl.org "Geoffrey Merck Website")  
  
  

> On 02/02/2018 08:34 PM, f4...@f4fxl.org wrote:   
>  > Hi,   
>  >   
>  > I beg your pardon, but this looks like a half baked feature.   
>  > IMHO package is missing some sort of migration from previous versions.   
>  > Packages are not supposed to require manual steps or shall prompt the   
>  > user what to do during update.   
>   
>  Could you explain what's wrong with the migration ? The file is in   
>  /etc/default, so it's marked as CONFFILES, and as such, if you changed   
>  it, dpkg will do a prompt. In my case, it did:   
>   
>  Setting up minissdpd (1.5.20161216-2~bpo9+1) ...   
>  Installing new version of config file /etc/default/minissdpd ...   
>  Installing new version of config file /etc/init.d/minissdpd ...   
>   
>  I don't see any trouble here...   
>   
>  If you do, please explain.   
>   
>  > Previous version seemed to accept 0.0.0.0 to listen on all interfaces,   
>  > it is unclear what is required to achieve the same.   
>   
>  As much as I understand, you're supposed to just configure one interface   
>  or IP pool, and miniupnpd will listen on all IPs on that device / pool.   
>   
>  /usr/sbin/minissdpd --help explains this.   
>   
>  If you just enter an interface name, like let's say eth0, then it will   
>  listen on that. If you enter 0.0.0.0/0, then it will listen on   
>  everything, no mater what. I tried putting 0.0.0.0 without the trailing   
>  /0, and it looks like also working.   
>   
>  > Moreover, entering a   
>  > valid address like the example specified in the error message also fails.  
>  
>   
>  Contributions, suggestions, ideas are more than welcome for improving   
>  the package.   
>   
>  Cheers,   
>   
>  Thomas Goirand (zigo)
  

Bug#890370: borgbackup: Installing borgbackup package from sid can break qgis 2.18.16 and qgis 2.99

[blackwhitekez]

Package: borgbackup
Version: 1.1.4-2
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
qgis 2.18.16 has been installed and used on the system for a considerable 
period. borgbackup was installed from the stretch repository and functioned 
correctly without any problems.
To get the latest version of borgbackup I have installed the sid package. This 
caused all installed versions of qgis to be uninstalled from the system and 
they could not be reinstalled.
I have been able to reinstall both borgbackup and qgis on a new installation of 
Debian 3, using the borgbackup package from testing instead.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Installed borgbackup from sid repository
   * What was the outcome of this action?
qgis 2.18 and 2.99 packages were uninstalled by apt in the course of installing 
borg 1.1.4
   * What outcome did you expect instead?
the Qgis packages should not have been removed

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


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

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

Versions of packages borgbackup depends on:
ii  fuse   2.9.7-1
ii  libacl12.2.52-3+b1
ii  libb2-10.97+git20171226-2
ii  libc6  2.26-6
ii  liblz4-1   0.0~r131-2+b1
ii  libssl1.1  1.1.0f-3+deb9u1
ii  libzstd1   1.3.3+dfsg-1
ii  python33.6.4-1
ii  python3-llfuse 1.3.2+dfsg-2
ii  python3-msgpack0.4.8-1+b1
ii  python3-pkg-resources  33.1.1-1

borgbackup recommends no packages.

Versions of packages borgbackup suggests:
pn  borgbackup-doc  

-- no debconf information

Bug#890369: libfm FTCBFS: tries to run host arch tools while building documentation

[Helmut Grohne]

Source: libfm
Version: 1.2.5-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libfm fails to cross build from source, because it tries and fails to
run /<>/docs/reference/libfm/libfm-scan. That's part of the
documentation, which resides in an Arch:all package and poses the
question why we run it at all in an arch-only build. The build
unconditionally passes --enable-gtk-doc to configure. I suggest changing
it to only pass that when libfm-doc is built. This can be complex
involving arch-only/indep-only/both builds and stage1 interaction. Thus
the easiest way is to let dh_listpackages tell whether we actually build
libfm-doc and only then pass the flag. Please consider applying the
attached patch. Testing it was not fully possible due to #876614.

Helmut
diff --minimal -Nru libfm-1.2.5/debian/changelog libfm-1.2.5/debian/changelog
--- libfm-1.2.5/debian/changelog2016-12-10 01:05:48.0 +0100
+++ libfm-1.2.5/debian/changelog2018-02-14 06:23:37.0 +0100
@@ -1,3 +1,10 @@
+libfm (1.2.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Only build documentation (--enable-gtk-doc) when we need it. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 14 Feb 2018 06:23:37 +0100
+
 libfm (1.2.5-1) unstable; urgency=medium
 
   * Removing --enable-debug from configure, that enables optimization.
diff --minimal -Nru libfm-1.2.5/debian/rules libfm-1.2.5/debian/rules
--- libfm-1.2.5/debian/rules2016-12-10 00:54:28.0 +0100
+++ libfm-1.2.5/debian/rules2018-02-14 06:23:37.0 +0100
@@ -4,10 +4,16 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+DOPACKAGES = $(shell dh_listpackages)
 ifneq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
 CONFIGURE_OPTIONS = --with-extra-only
 else
-CONFIGURE_OPTIONS = --enable-gtk-doc --enable-udisks
+CONFIGURE_OPTIONS = --enable-udisks
+endif
+ifneq ($(filter libfm-doc,$(DOPACKAGES)),)
+CONFIGURE_OPTIONS += --enable-gtk-doc
+else
+CONFIGURE_OPTIONS += --disable-gtk-doc
 endif
 
 %:

Bug#890365: Further tests on this issue.

[Eduardo Guerras Valera]

Setting frequencies equal or greater than 800 MHz seems to work fine, so
you need a CPU able to go below that in order to reveal the bug.

This one should go down to 400 MHz, and it does with the older kernel.

If, instead of trying to set a fixed frequency, one sets the governor
powersave (cpufreq-set -c 0 -g powersave) then a variable frequency is set,
but it should remain at the lowest frequency (as it does with the older
kernel).

Thanks

Bug#890368: wah-plugins FTCBFS: upstream Makefile hard codes the build architecture compiler for linking

[Helmut Grohne]

Source: wah-plugins
Version: 0.1.0-4
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

wah-plugins fails to cross build from source, because the upstream
Makefile hard codes the build architecture compiler for linking. After
making it substitutable, it cross builds successfully. Please consider
applying the attached patch.

Helmut
Index: wah-plugins-0.1.0/Makefile
===
--- wah-plugins-0.1.0.orig/Makefile
+++ wah-plugins-0.1.0/Makefile
@@ -33,7 +33,7 @@
 WAHPLUGINS_H = ladspaplugin.h autowah.h
 
 autowah.so:	$(WAHPLUGINS_O)
-	g++ -shared $(LDFLAGS) -o autowah.so $(WAHPLUGINS_O)
+	$(CXX) -shared $(LDFLAGS) -o autowah.so $(WAHPLUGINS_O)
 
 $(WAHPLUGINS_O):	$(WAHPLUGINS_H)
 

Bug#808211: saxonhe: Versions 9.6 and 9.7 should be installable at the same time

[tony mancill]

Hello Eugene,

I'm working on packaging checkstyle 8.8 which requires SaxonHE 9.8.  I
put together a package for the newer saxonhe (in experimental) and I can
successful build the r-deps within Debian using ratt.  However,
comparing the 9.7 and 9.8 libraries with japi-compliance-checker, I'm
reluctant to upload the package to unstable because there are so many
breaking changes between the versions.

Do you have any advice or thoughts about what we should do for buster?

Thank you,
tony


signature.asc
Description: PGP signature

Bug#888807: RFS: qstardict/1.3-1

[Boyuan Yang]

Control: tags -1 - moreinfo

在 2018年2月2日星期五 CST 下午11:25:11，Tobias Frost 写道：
> But two things escaped your eyes:
> - Left-tover "Comments:" on line 69
> - license-reconsile finds that in the libqxt is BSD-licensed (eg.
>   qxt/qxtglobal.cpp)

OK. Fixed now.

> > > - don't install README.md -- it does not have extra information beyond
> > > 
> > >   a package  description and compilation instructions (which are useless
> > >   for the users of the binary package)
> > >   There is also a slight bug in it: The URLs at the bottom seems
> > >   outdated, they will forward to the github project from the watch file.
> > >   Maybe at least report that to upstream.)
> > 
> > Done. The typo was forwarded upstream and got fixed in trunk code.
> 
> Ok. You should reflect this in the dep3 header though.
> Forwarded: no is not what you want, the measning for this field is
> when it is a Debian specific patch (value not-needed) or if you did not
> bother to forward it (yet) -- then it is "no",
> Here You Want(tm) "Applied-Upstream"
> followed by either the commit-id or the URL pointing to it.
> (see the dep3 spec for details))
> 
> (This is also valid for the other patches you mentioned below)

I updated those patches and replaced the Forwarded: field with Applied-
Upstream: field as decribed in dep3.

> > > - The embedded libqxt -- can you use the Debian packaged version?
> > 
> > Sorry but nope -- If we take a look into libqxt in Debian, #875027 says
> > that libqxt is unmaintained upstream and will be removed from Debian
> > archive soon. Upstream git repository also suggested that all projects
> > previously using libqxt should either migrate away from libqxt or embed
> > part of its code to fit their own need. [1] That is exactly what
> > qstardict
> > upstream is doing,
> > see also the GitHub issue [2].
> > 
> > [1] https://bitbucket.org/libqxt/libqxt/wiki/Home
> > [2] https://github.com/a-rodin/qstardict/issues/16
> 
> Well, this is not exactly how we deal with embedded code copies.
> When a library is gonna be removed from Debian this is not a valid excuse to
> have an embedded code copy of the same in another package. So the right
> thing is (as you've done already) to bring it to upstreams' attention to
> get that fixed before QT4 will be removed within this development cycle.
> In this case the effort is probably not required to patch the buildsystem to
> use the packaged version, as long as available, but when you follow the
> instructions here: https://wiki.debian.org/EmbeddedCodeCopies
> Keep me CC in the mail you send the notice to the security team.

After some investigation, I found that embedded libqxt is becoming a general 
problem thus here the post is:

https://lists.debian.org/debian-security-tracker/2018/02/msg00019.html


> OK, round 2 done :)
> Its almost good, let me know when done!

I've updated the git repository on Salsa as well as its source package on 
mentors.debian.net .

--
Thanks,
Boyuan Yang



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

Bug#890365: Narrowed a bit in which kernel the bug was introduced

[Eduardo Guerras Valera]

I have tested the cpufreq-set -f 400MHz command for several kernels in
Debian 9, and here is the result:

Kernels 4.9.0-3 to 4.9.0-5: CPU scaling is OK (but hibernation fails)
Kernels 4.13.0-0 CPU scaling fails to achieve constant lowest frequency
available (but hibernation seems to work).

So it seems the bug in the CPU frequency scaling was introducing after
4.9.0-5 and before 4.13.0-0

I don't know how to test any kernel between those two because they are not
in Backports. I am willing to test them if you could provide any link where
I can find instructions on how to get those kernels.

Thanks.

-- 


Eduardo Guerras Valera
Homer L. Dodge Department of Physics and Astronomy
440 W. Brooks St. - Norman, OK 73019-0225 - USA

Bug#883640: symfony dependency changes

[Nish Aravamudan]

FYI, this seems like it might be resolved in 4.7.25 upstream.

https://lab.civicrm.org/dev/core/issues/3#note_2974

Bug#890367: Reassign to ftp.debian.org

[Simon Quigley]

Control: reassign -1 ftp.debian.org



signature.asc
Description: OpenPGP digital signature

Bug#890367: (no subject)

[Simon Quigley]

Control: reassign -1 ftp.debian.org



signature.asc
Description: OpenPGP digital signature

Bug#890367: RM: lxqt-common -- ROM; split upstream; obsolete

[Simon Quigley]

Package: lxqt-common
Severity: normal

lxqt-common was split apart in the 0.12 release of LXQt, and is
obsoleted (thus no longer maintained). Please remove the source package
and binaries from Sid.

-- 
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#890366: dub: Segmentation fault when searching for dependencies

[Alex Kerr]

Package: dub
Version: 1.7.0-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

'dub build' and similar operations result in a segmentation fault when searching
for dependencies, making the package unusable for building projects. More
information is available at , however
it seems this issue only affects Debian.

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

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

Versions of packages dub depends on:
ii  default-d-compiler  0.3
ii  libc6   2.25-3
ii  libcurl3-gnutls 7.58.0-2
ii  libgcc1 1:8-20180207-2
ii  zlib1g  1:1.2.8.dfsg-5

dub recommends no packages.

dub suggests no packages.

-- no debconf information

Bug#876796: unattended-upgrades: stop including Python syntax in the report

[Paul Wise]

Version: 0.99

In addition to the issues above, I found another one:

Calling ['apt-get', '-qq', 'changelog', 'libgcj17=6.4.0-12'] to retrieve 
changelog

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#890365: linux-image 4.14 messing up with CPU frequency

[Eduardo Guerras Valera]

Package: linux-image-4.14.0-0.bpo.3-amd64
Distro: Debian 9 Stretch

When I try to set CPU frequency to the minimum, it doesn't work. This works
perfectly with kernel 4.9.5 (but with 4.9.5 I cannot hibernate).

Steps to reproduce the bug:

Have this in your grub: GRUB_CMDLINE_LINUX_DEFAULT="intel_pstate=disable"

su
cpufreq-set -c 0 -g userspace
cpufreq-set -c 0 -f 400MHz

With kernel 4.9 this resulted in the cpu running cold and silently at 400
MHz (check with cpufreq-info or with mate indicator applet).

After updating to 4.14 (linux-image-4.14.0-0.bpo.3-amd64 and corresponding
linux-header) the above mentioned use of cpufreq-set sets a variable
frequency policy.

Remark: this is happening too in Ubuntu 16.04 with kernel 4.10 and 4.13, so
probably the bug was introduced in 4.10.

(remark: reportbug is crashing in my system and that is why I send an
email. See screen capture at
https://unix.stackexchange.com/questions/424037/how-do-i-report-a-bug-to-debian-when-reportbug-crashes-because-it-has-itself-an
)

Please send further instructions to provide any kind of log you need.

Thanks.


-- 


Eduardo Guerras Valera
Homer L. Dodge Department of Physics and Astronomy
440 W. Brooks St. - Norman, OK 73019-0225 - USA

Bug#890355: man: nroff: Bad system call

[Thorsten Glaser]

Hrm.…

> Sure, it’s attached, and it seems really weird…

… I had thought someone had defined NULL as just 0
(although dalias makes a good argument for it) and
it was passed as a too-short sentinel, but it uses
execve, so that was not it.

But I see a lot of seccomp stuff in there, which,
obviously, is not there when I just run it from the
shell. Syscall numbers on x32 differ, so perhaps,
that is already the culprit?

bye,
//mirabilos
-- 
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the program, which is as sensible as putting all the prepositions
in English text in bold font.   -- Rob Pike in "Notes on Programming in C"

Bug#873951: xpdf: new major upstream version 4.x

[Vincent Lefevre]

On 2018-02-13 23:39:09 +0100, Florian Schlichting wrote:
> xpdf 4.00 switched from motif to QT. IMHO this eliminates the only
> reason to use xpdf instead of evince,

Not really. One problem with evince is that its UI is designed for
GNOME only:

  https://bugzilla.gnome.org/show_bug.cgi?id=745854

(libgtk3-nocsd0 is a workaround, but that's suboptimal and the use of
LD_PRELOAD conflicts with some commands).

Then, about Motif vs Qt, I don't know. I don't like very much how
the focus works with Motif (or perhaps this is specific to xpdf),
for instance with "Find".

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

Bug#890356: lintian.d.o: maintainer reports (particular "full" ones) grows without bounds in size

[Russ Allbery]

Niels Thykier  writes:

> The maintainer reports (notably the "full" reports) quickly grows in
> size (disk space used) and without any bounds.  At the moment, the
> lintian.d.o has a complete size usage of ~1GB - half of that is "full
> reports" - the second runner up is the uncompressed lintian.log (at
> 250MB), which will disappear soon.

I use my maintainer full report all the time.

I think a lot of the explosion has been the inclusion of the purely
informational tags in the maintainer reports, which I think are fairly
useless and add a ton of space because even entirely Lintian-clean
packages have several of them.  Maybe just suppress those from the
maintainer report and see what things look like then?

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

Bug#855336: make hangs when synchronizing output and redirecting to null

[Manoj Srivastava]

Hi,

I looked into this. The relevant bits appear in output.c:

--8<---cut here---start->8---
/* Obtain the lock for writing output.  */
static void *
acquire_semaphore (void)
{
  static struct flock fl;

  fl.l_type = F_WRLCK;
  fl.l_whence = SEEK_SET;
  fl.l_start = 0;
  fl.l_len = 1;
  if (fcntl (sync_handle, F_SETLKW, ) != -1)
return 
  perror ("fcntl()");
  return NULL;
}
--8<---cut here---end--->8---

So this does look like make explicitly will wait for the lock to
 be released (F_SETLKW instead of F_SETLK). The open question is whether
 the current behaviour is undesireable, and what the ramifications might
 be of not waiting for a lock.

manoj
-- 
"I believe that Ronald Reagan will someday make this country what it
once was... an arctic wilderness."-- Steve Martin
Manoj Srivastava  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


smime.p7s
Description: S/MIME cryptographic signature

Bug#890316: neovim: cmd line shows special chars like":]2 q" instead of ":"

[James McCoy]

On Tue, Feb 13, 2018 at 12:11:47PM +0100, Luffah wrote:
>When i open `nvim -u NONE` and i press ':' command line
>shows special chars like":]2 q" instead of ":" .

Quoting from upstream's [FAQ]:

> This is a bug in your terminal emulator. It happens because Nvim sends
> cursor-shape termcodes by default, if the terminal appears to be
> xterm-compatible (TERM=xterm-256color).
>
> To workaround the issue, you can:
>
>   * Use a different terminal emulator
>   * Disable guicursor in your Nvim config:
>
>   set guicursor=

What terminal emulator are you using?

[FAQ]: 
https://github.com/neovim/neovim/wiki/FAQ#nvim-shows-weird-symbols-2-q-when-changing-modes

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#852478: make: Implicit rule for yacc does not handle the header file

[Manoj Srivastava]

severity 852478 wishlist
thanks

Hi,

Indeed, this is true. However, in the info file, this is
 documented, and the catalogue of implicit rules just contains the
 implicit rule for the .c file, and not for the header.

manoj

-- 
We can found no scientific discipline, nor a healthy profession on the
technical mistakes of the Department of Defense and IBM.  -- Edsger
Dijkstra
Manoj Srivastava  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


smime.p7s
Description: S/MIME cryptographic signature

Bug#855336: I can’t reproduce this bug outside of docker

[Manoj Srivastava]

tags 855336 +unreproducible
thanks

Hi,

With the new version of make (4.2.1), I tried to reproduce
 this.
--8<---cut here---start->8---
> cat >Makefile <<'EOF'
heredoc> # run with
heredoc> # 
heredoc> # rm -rf subdir
heredoc> # make -O >/dev/null
heredoc> #
heredoc> # add -j2, then you can' t even terminate it 
heredoc> 
heredoc> FILE := a b
heredoc> 
heredoc> all: $(addprefix subdir/,$(FILE))
heredoc> 
heredoc> $(addprefix subdir/,$(FILE)):
heredoc>echo "$@"
heredoc>mkdir -p $(dir $@); touch $@
heredoc> EOF
> make -O >/dev/null
> ls -asCF
total 532
  4 ./  520 ../4 Makefile4 subdir/
--8<---cut here---end--->8---

manoj
-- 
Surly to bed, surly to rise, makes you about average.
Manoj Srivastava  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


smime.p7s
Description: S/MIME cryptographic signature

Bug#890363: ITP: sfnt2woff-zopfli -- Create WOFF files with Zopfli compression

[Paride Legovini]

Package: wnpp
Severity: wishlist
Owner: Paride Legovini 

* Package name: sfnt2woff-zopfli
  Version : 1.1.0
  Upstream Author : Bram Stein 
* URL : https://github.com/bramstein/sfnt2woff-zopfli
* License : Apache and (MPL or GPL or LGPL)
  Programming Lang: C
  Description : Create WOFF files with Zopfli compression

This is a modified version of the sfnt2woff utility that uses Zopfli as
a compression algorithm instead of zlib. This results in compression
gains of, on average, 5-8% compared to regular WOFF files. Zopfli
generates compressed output that is compatible with regular zlib
compression so the resulting WOFF files can be used everywhere.

This package provides two tools:
 * sfnt2woff-zopfli: convert OpenType fonts to WOFF
 * woff2sfnt-zopfli: convert WOFF fonts to OpenType

sfnt2woff-zopfli is a build-dependency for a newer version of another
package I maintain: fonts-hack.

I plan to maintain it in the Debian Fonts team.
I will need a sponsor for the upload.

Paride

Bug#890364: pybind11-dev: Request migration to unstable

[Shane Loretz]

Package: pybind11-dev
Version: 2.2.1-1
Severity: wishlist

Dear Maintainer,

Would the maintainer be willing to migrate 2.2.1 from experimental to unstable? 
I'm a user of a distribution based on debian unstable. I have been using 
pybind11 from pip previously. The package in experimental appears to be working 
flawlessly for my usecase and has some nice new features not in the version 
currently in unstable.


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

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

pybind11-dev depends on no packages.

pybind11-dev recommends no packages.

Versions of packages pybind11-dev suggests:
pn  libeigen3-dev  
pn  pybind11-doc   

-- no debconf information

Bug#890355: man: nroff: Bad system call

[Colin Watson]

On Tue, Feb 13, 2018 at 09:55:36PM +0100, Thorsten Glaser wrote:
> tglase@tglase:~ $ man ls
> man: nroff: Bad system call
>  Manual page ls(1) line ?/? (END) (press h for help or q to quit)

This test case works fine for me; perhaps there's something about x32
that matters here.  Could you please try this, which will hopefully also
fail, and then attach man-ls.trace to this bug?

  strace -f -o man-ls.trace -s 1024 man ls

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]

Bug#879504: cyreposurgeon: undefined symbol: PyFPE_jbuf

[Andreas Gnau]

On Sun, 22 Oct 2017 13:03:21 +0200 Jakub Wilk  wrote:
> Package: reposurgeon
> Version: 3.42-2
> 
> $ cyreposurgeon
> cyreposurgeon: symbol lookup error: cyreposurgeon: undefined symbol: 
> PyFPE_jbuf

This is "fixed" upstream by now longer supporting Cython and using PyPy instead 
which according to upstream provides better performance.

Bug#864875: [request-tracker-maintainers] Bug#864875: request-tracker4: frontend exists with status 10 after last upgrade

[Dominic Hargreaves]

On Thu, Nov 23, 2017 at 04:38:53PM +0100, Franz Georg Köhler wrote:
> Here is the requested output. /var/cache is on tmpfs on this machine and
> gets deleted on every reboot. Maybe this is related to the problem?
> 
> root@orion:~# cp /var/cache/debconf/config.dat /tmp
> 
> root@orion:~# /var/lib/dpkg/info/request-tracker4.config
> + set -e
> + RTVER=4
> + RT=request-tracker4
> + . /usr/share/debconf/confmodule
> + [ !  ]
> + PERL_DL_NONLAZY=1
> + export PERL_DL_NONLAZY
> + [  ]
> + exec /usr/share/debconf/frontend
> /var/lib/dpkg/info/request-tracker4.config
> debconf (db): making DbDriver of type File
> debconf (db config): started; filename is /var/cache/debconf/config.dat
> debconf (db config): loading database
> debconf (db): making DbDriver of type File
> debconf (db passwords): started; filename is
> /var/cache/debconf/passwords.dat
> 
> [...]
> + IFS=
>  read -r _db_internal_line
> debconf (developer): <-- CAPB backup
> debconf (developer): --> 0 multiselect escape backup
> + RET=multiselect escape backup
> + return 0
> + [  != configure ]
> + [  != reconfigure ]
> + return 0
> + db_get request-tracker4/dbconfig-install
> + _db_cmd GET request-tracker4/dbconfig-install
> + _db_internal_IFS=   
> 
> + IFS=
> + printf %s\n GET request-tracker4/dbconfig-install
> debconf (developer): <-- GET request-tracker4/dbconfig-install
> debconf (developer): --> 10 request-tracker4/dbconfig-install doesn't exist
> + IFS=
> 
> + IFS=
>  read -r _db_internal_line
> + RET=10 request-tracker4/dbconfig-install doesn't exist
> + return 10
> debconf (db config): saving database
> debconf (db passwords): no database changes, not saving
> debconf (db templatedb): saving database
> root@orion:~# echo $?
> 10
> 
> root@orion:~# diff -u /tmp/config.dat /var/cache/debconf/config.dat
> root@orion:~# md5sum /var/cache/debconf/config.dat
> 5582bfe5c3a834733a8c39f5e0320fde  /var/cache/debconf/config.dat
> root@orion:~# md5sum /tmp/config.dat
> 5582bfe5c3a834733a8c39f5e0320fde  /tmp/config.dat

Hi,

Apologies for the delay in responding. I recall testing this
at the time and not being able to reproduce - however perhaps you could
let us know whether changing /var/cache to not be a tmpfs makes a
difference? If so, I would think that would be a bug either in
debconf or dbconfig-common.

Thanks,
Dominic.

Bug#889181: closed by Paul Gevers <elb...@debian.org> (Bug#889181: fixed in cacti 1.1.34+ds1-1)

[Nish Aravamudan]

On Tue, Feb 13, 2018 at 3:26 PM, Nish Aravamudan
 wrote:
> While this update did fix the bug in question, it still doesn't pass
> DEP8, whereas my backport did :/ Any ideas?

My fault, I see 1.1.35+ds1-1 was uploaded with the fix. I'll sync that
down. Sorry for the noise!

-Nish

> On Tue, Feb 6, 2018 at 1:54 PM, Debian Bug Tracking System
>  wrote:
>> This is an automatic notification regarding your Bug report
>> which was filed against the cacti package:
>>
>> #889181: cacti changes for PHP7.2 and dep8 tests
>>
>> It has been closed by Paul Gevers .
>>
>> Their explanation is attached below along with your original report.
>> If this explanation is unsatisfactory and you have not received a
>> better one in a separate message then please contact Paul Gevers 
>>  by
>> replying to this email.
>>
>>
>> --
>> 889181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889181
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>>
>> -- Forwarded message --
>> From: Paul Gevers 
>> To: 889181-cl...@bugs.debian.org
>> Cc:
>> Bcc:
>> Date: Tue, 06 Feb 2018 21:50:45 +
>> Subject: Bug#889181: fixed in cacti 1.1.34+ds1-1
>> Source: cacti
>> Source-Version: 1.1.34+ds1-1
>>
>> We believe that the bug you reported is fixed in the latest version of
>> cacti, which is due to be installed in the Debian FTP archive.
>>
>> A summary of the changes between this version and the previous one is
>> attached.
>>
>> Thank you for reporting the bug, which will now be closed.  If you
>> have further comments please address them to 889...@bugs.debian.org,
>> and the maintainer will reopen the bug report if appropriate.
>>
>> Debian distribution maintenance software
>> pp.
>> Paul Gevers  (supplier of updated cacti package)
>>
>> (This message was generated automatically at their request; if you
>> believe that there is a problem with it please contact the archive
>> administrators by mailing ftpmas...@ftp-master.debian.org)
>>
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Format: 1.8
>> Date: Tue, 06 Feb 2018 22:31:34 +0100
>> Source: cacti
>> Binary: cacti
>> Architecture: source
>> Version: 1.1.34+ds1-1
>> Distribution: unstable
>> Urgency: medium
>> Maintainer: Cacti Maintainer 
>> Changed-By: Paul Gevers 
>> Description:
>>  cacti  - web interface for graphing of monitoring systems
>> Closes: 889181
>> Changes:
>>  cacti (1.1.34+ds1-1) unstable; urgency=medium
>>  .
>>* New upstream version 1.1.34
>>  - Includes updates for php7.2 (Closes: #889181)
>> Checksums-Sha1:
>>  69a571f90eb6bd8e11890db947876b3acaa9fefe 2144 cacti_1.1.34+ds1-1.dsc
>>  a6b13c3611423cc2e706b60d5bb7cfdb026d00b1 66580 
>> cacti_1.1.34+ds1.orig-docs-source.tar.xz
>>  df446350a1e7c53db2b94bc7c0d35fa2163ca66d 3824107 
>> cacti_1.1.34+ds1.orig.tar.gz
>>  44eff5fedf4dd898942b1956b9566a79f44e7a03 51712 
>> cacti_1.1.34+ds1-1.debian.tar.xz
>> Checksums-Sha256:
>>  faf9ed2bf37a916c527b3e1a80a4091f26ef48e72b3b86435407b76339e68d4c 2144 
>> cacti_1.1.34+ds1-1.dsc
>>  4e93415bb3e4d4cb126a8ea027378827214bf93e80e73f8718906a94acc7a318 66580 
>> cacti_1.1.34+ds1.orig-docs-source.tar.xz
>>  1ff8fc4273b6ff6f167bbb1214dd92a71ecfa3dea8a5085c08ca3bb4ddd3e1a0 3824107 
>> cacti_1.1.34+ds1.orig.tar.gz
>>  56f7f11a4f2a54479b53dc39553a17b2e94ad44b1226890068b4daed4339cf62 51712 
>> cacti_1.1.34+ds1-1.debian.tar.xz
>> Files:
>>  64d7b2736e67c98da799984bf3b4f820 2144 web optional cacti_1.1.34+ds1-1.dsc
>>  9f41c097f6beab7281874a473bbf3a86 66580 web optional 
>> cacti_1.1.34+ds1.orig-docs-source.tar.xz
>>  56d2d16363ad5f7771edafebc0a49a62 3824107 web optional 
>> cacti_1.1.34+ds1.orig.tar.gz
>>  4a92b0ec3ce56c015797d8db08e474b5 51712 web optional 
>> cacti_1.1.34+ds1-1.debian.tar.xz
>>
>> -BEGIN PGP SIGNATURE-
>>
>> iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlp6Hz0ACgkQnFyZ6wW9
>> dQrp4gf7BNa9muSi3z2zOmzHiwXFnN4lMUybML5PZe6R7kJhVcOwcQOuIJEs06Zf
>> wKI9MyB0Lo+n3HvrrRqyIv7woZPHsAkDC1xHmgjfFuqYqWFXAbuxR2NNFG7HLMLz
>> T/Xq5mpiG+oVBiHYDBIbbeQPyK0QOr9zZ/bzK8xxQXMlVg7P/FLhCVRExyTLRjBr
>> TipNCpDpheD8I87euvdE+ExJ6AtJey1vEtWtm2ka6dav/nm3lxJBGzumOcxn+151
>> ZS/7HTOdb5AViU4Bi4IZsCOc0ivFJg7me4VVEinmPkOyt+BylGRm2IjGnXY7ZejN
>> 9EsR/qhEVCA4vDIflWFCS1CxpmXd6g==
>> =rn75
>> -END PGP SIGNATURE-
>>
>> -- Forwarded message --
>> From: Nishanth Aravamudan 
>> To: Debian Bug Tracking System 
>> Cc:
>> Bcc:
>> Date: Fri, 2 Feb 2018 22:25:24 -0800
>> Subject: cacti changes for PHP7.2 and dep8 tests
>> Package: cacti
>> Version: 1.1.31+ds1-1
>> Severity: normal
>> Tags: patch
>> User: ubuntu-de...@lists.ubuntu.com
>> Usertags: origin-ubuntu bionic ubuntu-patch
>>
>> Dear Maintainer,
>>
>>
>> In Ubuntu, the attached patch was applied to achieve the following:
>>

Bug#833146: [62ca792] Fix for Bug#833146 committed to git

[Manoj Srivastava]

tags 833146 + pending
thanks
Hi,

 The following change has been committed for this bug by
 Manoj Srivastava  on the branch 
 master at Tue, 13 Feb 2018 15:26:36 -0800.

 The fix will be in the next upload. 
=
[master]: New bug fixing release

Fixes the cross compilation issue that resurfaced. Closes: Bug#833146

Signed-off-by: Manoj Srivastava 
=

Bug#889181: closed by Paul Gevers <elb...@debian.org> (Bug#889181: fixed in cacti 1.1.34+ds1-1)

[Nish Aravamudan]

While this update did fix the bug in question, it still doesn't pass
DEP8, whereas my backport did :/ Any ideas?

On Tue, Feb 6, 2018 at 1:54 PM, Debian Bug Tracking System
 wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the cacti package:
>
> #889181: cacti changes for PHP7.2 and dep8 tests
>
> It has been closed by Paul Gevers .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Paul Gevers 
>  by
> replying to this email.
>
>
> --
> 889181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889181
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Paul Gevers 
> To: 889181-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 06 Feb 2018 21:50:45 +
> Subject: Bug#889181: fixed in cacti 1.1.34+ds1-1
> Source: cacti
> Source-Version: 1.1.34+ds1-1
>
> We believe that the bug you reported is fixed in the latest version of
> cacti, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 889...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Paul Gevers  (supplier of updated cacti package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Tue, 06 Feb 2018 22:31:34 +0100
> Source: cacti
> Binary: cacti
> Architecture: source
> Version: 1.1.34+ds1-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Cacti Maintainer 
> Changed-By: Paul Gevers 
> Description:
>  cacti  - web interface for graphing of monitoring systems
> Closes: 889181
> Changes:
>  cacti (1.1.34+ds1-1) unstable; urgency=medium
>  .
>* New upstream version 1.1.34
>  - Includes updates for php7.2 (Closes: #889181)
> Checksums-Sha1:
>  69a571f90eb6bd8e11890db947876b3acaa9fefe 2144 cacti_1.1.34+ds1-1.dsc
>  a6b13c3611423cc2e706b60d5bb7cfdb026d00b1 66580 
> cacti_1.1.34+ds1.orig-docs-source.tar.xz
>  df446350a1e7c53db2b94bc7c0d35fa2163ca66d 3824107 cacti_1.1.34+ds1.orig.tar.gz
>  44eff5fedf4dd898942b1956b9566a79f44e7a03 51712 
> cacti_1.1.34+ds1-1.debian.tar.xz
> Checksums-Sha256:
>  faf9ed2bf37a916c527b3e1a80a4091f26ef48e72b3b86435407b76339e68d4c 2144 
> cacti_1.1.34+ds1-1.dsc
>  4e93415bb3e4d4cb126a8ea027378827214bf93e80e73f8718906a94acc7a318 66580 
> cacti_1.1.34+ds1.orig-docs-source.tar.xz
>  1ff8fc4273b6ff6f167bbb1214dd92a71ecfa3dea8a5085c08ca3bb4ddd3e1a0 3824107 
> cacti_1.1.34+ds1.orig.tar.gz
>  56f7f11a4f2a54479b53dc39553a17b2e94ad44b1226890068b4daed4339cf62 51712 
> cacti_1.1.34+ds1-1.debian.tar.xz
> Files:
>  64d7b2736e67c98da799984bf3b4f820 2144 web optional cacti_1.1.34+ds1-1.dsc
>  9f41c097f6beab7281874a473bbf3a86 66580 web optional 
> cacti_1.1.34+ds1.orig-docs-source.tar.xz
>  56d2d16363ad5f7771edafebc0a49a62 3824107 web optional 
> cacti_1.1.34+ds1.orig.tar.gz
>  4a92b0ec3ce56c015797d8db08e474b5 51712 web optional 
> cacti_1.1.34+ds1-1.debian.tar.xz
>
> -BEGIN PGP SIGNATURE-
>
> iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlp6Hz0ACgkQnFyZ6wW9
> dQrp4gf7BNa9muSi3z2zOmzHiwXFnN4lMUybML5PZe6R7kJhVcOwcQOuIJEs06Zf
> wKI9MyB0Lo+n3HvrrRqyIv7woZPHsAkDC1xHmgjfFuqYqWFXAbuxR2NNFG7HLMLz
> T/Xq5mpiG+oVBiHYDBIbbeQPyK0QOr9zZ/bzK8xxQXMlVg7P/FLhCVRExyTLRjBr
> TipNCpDpheD8I87euvdE+ExJ6AtJey1vEtWtm2ka6dav/nm3lxJBGzumOcxn+151
> ZS/7HTOdb5AViU4Bi4IZsCOc0ivFJg7me4VVEinmPkOyt+BylGRm2IjGnXY7ZejN
> 9EsR/qhEVCA4vDIflWFCS1CxpmXd6g==
> =rn75
> -END PGP SIGNATURE-
>
> -- Forwarded message --
> From: Nishanth Aravamudan 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Fri, 2 Feb 2018 22:25:24 -0800
> Subject: cacti changes for PHP7.2 and dep8 tests
> Package: cacti
> Version: 1.1.31+ds1-1
> Severity: normal
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu bionic ubuntu-patch
>
> Dear Maintainer,
>
>
> In Ubuntu, the attached patch was applied to achieve the following:
>
>   * debian/patches/php72_count_bc_changes.patch: PHP7.2 has deprecated
> count() of non-Countable objects.
>   * debian/patches/update-cactisql.patch: Update cacti.sql for
> readstring to community change.
>
> Note that even with this change, the DEP8 tests fail on Ubuntu 18.04,
> with:
>
> Unexpected output in 

Bug#888220: ignition-math4: FTBFS on mips(el) and hppa: UNIT_Helpers_TEST fails badly

[Jose Luis Rivero]

Thanks very much James for the research and the patch.

I've sent it upstream:
https://bitbucket.org/ignitionrobotics/ign-math/pull-requests/232/bug-in-pairing-function-insde-helperscc/diff

On Wed, Jan 24, 2018 at 9:14 AM, James Cowgill  wrote:

> Control: tags -1 patch
>
> Hi,
>
> On 23/01/18 23:48, Aaron M. Ucko wrote:
> > Source: ignition-math4
> > Version: 4.0.0+dfsg1-1
> > Severity: important
> > Tags: upstream
> > Justification: fails to build from source
> > User: debian-m...@lists.debian.org
> > Usertags: mips mipsel
> >
> > Builds of ignition-math4 for mips, mipsel, and the non-release
> > architecture hppa have been failing as detailed at
> >
> > https://buildd.debian.org/status/fetch.php?pkg=ignition-
> math4=mips=4.0.0%2Bdfsg1-1=1516376024=0
> > https://buildd.debian.org/status/fetch.php?pkg=ignition-
> math4=mipsel=4.0.0%2Bdfsg1-1=1516373688=0
> > https://buildd.debian.org/status/fetch.php?pkg=ignition-
> math4=hppa=4.0.0%2Bdfsg1-1=1516373442=0
> >
> > On mips, this test manages to make ctest itself to run out of memory:
> >
> > Start 11: UNIT_Helpers_TEST
> >   terminate called after throwing an instance of 'std::bad_alloc'
> > what():  std::bad_alloc
> >   Makefile:143: recipe for target 'test' failed
> >   make[2]: *** [test] Aborted
> >
> > On mipsel and hppa, HelpersTest.Pair spews millions(!) of errors and
> > then hits a timeout:
> >
> >   11/75 Test #11: UNIT_Helpers_TEST ..***Timeout
> 240.12 sec
> >   [...]
> >   [ RUN  ] HelpersTest.Pair
> >   /<>/ignition-math4-4.0.0+dfsg1/src/Helpers_TEST.cc:516:
> Failure
> > Expected: a
> > Which is: 4294962295
> >   To be equal to: c
> > Which is: 4294962296
>
> This is caused by the pairing function in src/Helpers.cc
>
> Firstly, I am not sure I understand why anyone would need this pairing
> function exactly. The point of a pairing function is that the inputs can
> be infinitely big, but the inputs to these functions are 32-bit
> integers. As long as you don't need the specific algorithm, you could
> implement something similar using a single shift and an add.
>
> I think the issue is this code relies on infinite floating point
> precision in calculating the "sqrt" variable:
> > std::tuple Unpair(const PairOutput _key)
> > {
> >   // Must explicitly cast so that the _key is not auto cast to a
> double
> >   uint64_t sqrt = static_cast(
> >   std::floor(std::sqrt(static_cast(_key;
> >   uint64_t sq = sqrt * sqrt;
> >
> >   return ((_key - sq) >= sqrt) ?
> > std::make_tuple(static_cast(sqrt),
> > static_cast(_key - sq - sqrt)) :
> > std::make_tuple(static_cast(_key - sq),
> > static_cast(sqrt));
> > }
>
> On architectures with > 64-bit long doubles (like Linux x86_64) you get
> away with this. On other architectures where long double == double, the
> cast to long double and sqrt is too inaccurate to implement this properly.
>
> The attached patch is based on a more accurate integer square root I
> found on stack overflow. You should be able to drop your
> 0004_test_failures_in_non_x64_arches.patch after applying this and
> possibly some other #ifdefs I noticed that upstream have added.
>
> James
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
> debian-science-maintainers
>

Bug#890361: lintian: handling of new source override location possibly buggy

[Thorsten Glaser]

Hi Chris,

>I think you're right. Here's one patch - can you quickly test it works
>for you?

sorry, I don’t even have a testcase. I only noticed it during
looking at the source, trying to figure out whether a symlink
in the new position was good enough.

>  +last if $file;

But this is probably it, yes.

>… but, just for giggles, here's another silly one:

That looks also good ;-)

>Compat level 5 (!).

Well, 5 was the standard/minimum for a long time,
and I don’t use the newer features anyway (not those
visible to the user; those in the background, such
as using gzip’s -n option, are, of course, used),
so I’d just use compat 5 and get whatever version
the target distro had with whatever of its fixes.

>(What's wrong with the  debhelper versions in
>backports, out of interest?)

I try to keep backports dependencies out if possible.

I also maintain, in my own (public) repo and in the
private one of my employer, backports much far back
than oldoldstable, for those who are still running
such systems or chroots someplace. This started out
with back to etch (but, back then, lenny was stable,
so it was not that much of a, well, stretch (no pun
intended)), but eventually we discovered a sarge sy‐
stem somewhere at the workplace, so I targetted that
with a handful of packages until we could upgrade it
(it’s long gone, thankfully, but it’s no effort to
keep what I already *have* working in the old versions,
working in those; though I don’t create new backports
to such old versions). It’s also a portability exercise…

bye,
//mirabilos
-- 
13:22⎜«neurodamage» mira, what's up man? I have a CVS question for you in #cvs
13:22⎜«neurodamage» since you're so good w. it │ «neurodamage:#cvs» i love you
17:14⎜ Thanks big help you are :-)mira|nwt: ty again
18:36⎜«ThunderChicken:#cvs» mirabilos FTW!  23:03⎜«mithraic:#cvs» aaah. thanks

Bug#882944: php-monolog FTBFS with phpunit 6.4.4-2

[Nishanth Aravamudan]

Package: php-monolog
Version: 1.23.0-1
Followup-For: Bug #882944
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Maintainer,


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


  * debian/patches/phpunit6_compatibility_changes.patch: PHPUnit 6 is
not backwards compatible in various ways.  Closes LP: #1749001.
  * debian/patches/mongodb_fixes.patch: Multiple upstream MongoDB
handler changes.

I had to backport a lot of changes from upstream to get the build to
succeed and to get the DEP8 tests to pass.

I'm most unhappy with the redis/predis stuff, but I think it's actually
a bug in libphp-predis, which does not ship an autoload.php file?


Thanks for considering the patch.

*** /tmp/tmpXKFgpx/php-monolog_1.23.0-1ubuntu1.debdiff
diff -Nru php-monolog-1.23.0/debian/patches/mongodb_fixes.patch 
php-monolog-1.23.0/debian/patches/mongodb_fixes.patch
--- php-monolog-1.23.0/debian/patches/mongodb_fixes.patch   1969-12-31 
16:00:00.0 -0800
+++ php-monolog-1.23.0/debian/patches/mongodb_fixes.patch   2018-02-12 
21:09:52.0 -0800
@@ -0,0 +1,207 @@
+Description: Multiple upstream MongoDB handler changes
+Author: Nishanth Aravamudan 
+Origin: upstream, 
https://github.com/Seldaek/monolog/commit/ad37c8e6638d6d21cf4deaca1aafb8c4a29a6d1b.patch
+Origin: upstream, 
https://github.com/Seldaek/monolog/commit/f6a9fdbb2c9ad9ef7f26269a1edb1de1c3b6d3cc.patch
+Origin: upstream, 
https://github.com/Seldaek/monolog/commit/d860b763cb0419930e9bce71cec7408f215d5a6d.patch
+Origin: upstream, 
https://github.com/Seldaek/monolog/commit/aa6ab660bdb32f4568514ad8ed0167b86a57809b.patch
+Forwarded: Will be done by Nishanth Aravamudan
+Last-Update: 2018-02-13
+
+--- a/composer.json
 b/composer.json
+@@ -38,8 +38,8 @@
+ "ruflin/elastica": "Allow sending log messages to an Elastic Search 
server",
+ "php-amqplib/php-amqplib": "Allow sending log messages to an AMQP 
server using php-amqplib",
+ "ext-amqp": "Allow sending log messages to an AMQP server (1.0+ 
required)",
+-"ext-mongo": "Allow sending log messages to a MongoDB server",
+-"mongodb/mongodb": "Allow sending log messages to a MongoDB server 
via PHP Driver",
++"ext-mongodb": "Allow sending log messages to a MongoDB server (via 
driver)",
++"mongodb/mongodb": "Allow sending log messages to a MongoDB server 
(via library)",
+ "aws/aws-sdk-php": "Allow sending log messages to AWS services like 
DynamoDB",
+ "rollbar/rollbar": "Allow sending log messages to Rollbar",
+ "php-console/php-console": "Allow sending log messages to Google 
Chrome"
+--- a/src/Monolog/Handler/MongoDBHandler.php
 b/src/Monolog/Handler/MongoDBHandler.php
+@@ -11,41 +11,66 @@
+ 
+ namespace Monolog\Handler;
+ 
++use MongoDB\Driver\BulkWrite;
++use MongoDB\Driver\Manager;
++use MongoDB\Client;
+ use Monolog\Logger;
+ use Monolog\Formatter\NormalizerFormatter;
+ 
+ /**
+  * Logs to a MongoDB database.
+  *
+- * usage example:
++ * Usage example:
+  *
+- *   $log = new Logger('application');
+- *   $mongodb = new MongoDBHandler(new \Mongo("mongodb://localhost:27017"), 
"logs", "prod");
++ *   $log = new \Monolog\Logger('application');
++ *   $client = new \MongoDB\Client('mongodb://localhost:27017');
++ *   $mongodb = new \Monolog\Handler\MongoDBHandler($client, 'logs', 'prod');
+  *   $log->pushHandler($mongodb);
+  *
+- * @author Thomas Tourlourat 
++ * The above examples uses the MongoDB PHP library's client class; however, 
the
++ * MongoDB\Driver\Manager class from ext-mongodb is also supported.
+  */
+ class MongoDBHandler extends AbstractProcessingHandler
+ {
+-protected $mongoCollection;
++private $collection;
++private $manager;
++private $namespace;
+ 
+-public function __construct($mongo, $database, $collection, $level = 
Logger::DEBUG, $bubble = true)
++/**
++ * Constructor.
++ *
++ * @param Client|Manager $mongodbMongoDB library or driver client
++ * @param string $database   Database name
++ * @param string $collection Collection name
++ * @param int$level  The minimum logging level at which 
this handler will be triggered
++ * @param Boolean$bubble Whether the messages that are 
handled can bubble up the stack or not
++ */
++public function __construct($mongodb, $database, $collection, $level = 
Logger::DEBUG, $bubble = true)
+ {
+-if (!($mongo instanceof \MongoClient || $mongo instanceof \Mongo || 
$mongo instanceof \MongoDB\Client)) {
+-throw new \InvalidArgumentException('MongoClient, Mongo or 
MongoDB\Client instance required');
++if (!($mongodb instanceof Client || $mongodb instanceof Manager)) {
++throw new \InvalidArgumentException('MongoDB\Client or 
MongoDB\Driver\Manager instance required');
+ }
+ 
+-

Bug#889469: check of the code

[Tomas Pospisek]

Hi Andreas,

I'd be interested in an lsmount (i.e. something that formats and filters 
`mount` nicely).


I had cursory glance at the code in 
https://github.com/Llandon/lsmount/tree/master/src. My interest was 
spotting any weird things. I want to point out this: as far as I know 
`mount` will list stuff that's mountable by plain users. So you have via 
the mount parameters data flow from userspace to potentially root-space. 
So in case handling of that data flow had a weakness, then you'd have a 
local root exploit.


*t

Bug#885103: rename: "-n" option is ignored

[Dominic Hargreaves]

Control: forwarded -1 https://rt.cpan.org/Ticket/Display.html?id=124421

On Sun, Dec 24, 2017 at 09:36:59PM +0100, Peter De Wachter wrote:
> Hello Dominic,
> 
> [Resending with bugs.debian.org in Cc]
> 
> I feel that in Debian the expected behavior is that options and other
> arguments can be mixed. Sure, no program bothers explicitly
> documenting that, but why would they? It's simply the normal behavior
> of glibc's getopt(3) after all. Programs that don't allow this are
> exceptions.
> 
> Given that the previous version of rename allowed this and given that
> it's expected behavior on Debian, I feel that this is a valid bug.
> 
> If on the other hand you really don't want to support this, I feel
> it's necessary to give an explicit error message in this situation
> ("fatal: option -n must come before non-option arguments").

Hi,

It's a fair point. I've proposed a change upstream: 

https://rt.cpan.org/Ticket/Display.html?id=124421

Cheers,
Dominic.

Bug#873951: xpdf: new major upstream version 4.x

[Florian Schlichting]

xpdf 4.00 switched from motif to QT. IMHO this eliminates the only
reason to use xpdf instead of evince, given that both are based on
poppler in Debian. I think we should keep maintaining 3.04 as a fork as
long as this is feasible, although anyone is of course welcome to
backport fixes and features.

Bug#890361: lintian: handling of new source override location possibly buggy

[Chris Lamb]

tags 890361 + patch
thanks

Hey Thorsten!

> I’m fairly sure the code around lines 56-62 of
> /usr/share/lintian/collection/override-file
> does NOT prefer the first (cf. line 44ff.)
> but the last override file found.

I think you're right. Here's one patch - can you quickly test it works
for you?

  diff --git a/collection/override-file b/collection/override-file
  index 04c43fc6d..70ad1fb35 100755
  --- a/collection/override-file
  +++ b/collection/override-file
  @@ -59,6 +59,7 @@ sub collect {
   } elsif (-f "$override.gz") {
   $file = "$override.gz";
   }
  +last if $file;
   }
   

… but, just for giggles, here's another silly one:

  diff --git a/collection/override-file b/collection/override-file
  index 04c43fc6d..b6bad50a5 100755
  --- a/collection/override-file
  +++ b/collection/override-file
  @@ -41,14 +41,14 @@ sub collect {
   unlink("$dir/override");
   }
   
  -# Pick the first of these files that exists.  Prefer
  +# Pick the last of these files that exists.  Prefer
   # source/lintian-overrides to source.lintian-overrides for source
   # packages.
   my (@overrides, $file);
   if ($type eq 'source') {
   @overrides = (
  -"$dir/unpacked/debian/source/lintian-overrides",
   "$dir/unpacked/debian/source.lintian-overrides"
  +"$dir/unpacked/debian/source/lintian-overrides",
   );
   } else {
   @overrides = ("$dir/unpacked/usr/share/lintian/overrides/$pkg");


> I’m a tad annoyed at such incompatible changes,
> but also (not scope of this bugreport) having to
> jump to the latest debhelper version when 5 is
> enough for me.

Compat level 5 (!).  (What's wrong with the  debhelper versions in
backports, out of interest?)


Regards,

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

Bug#890361: lintian: handling of new source override location possibly buggy

[Thorsten Glaser]

Package: lintian
Version: 2.5.74
Severity: minor

I’m fairly sure the code around lines 56-62 of
/usr/share/lintian/collection/override-file
does NOT prefer the first (cf. line 44ff.)
but the last override file found.

I think there’s a break missing in lines 58 and 60.
(Or, well, the Perl equivalent; I don’t speak Perl.)

It’s also a bit unfortunate that, if I have both
(one being a symlink to the other), I still have¹
to override that the old location is used. I prefer
my packages backportable with ease, which is why
I’m a tad annoyed at such incompatible changes,
but also (not scope of this bugreport) having to
jump to the latest debhelper version when 5 is
enough for me.

① live example: git clone \
https://evolvis.org/anonscm/git/alioth/jupp.git
  (dump http transport, so may take a minute)

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

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

Versions of packages lintian depends on:
ii  binutils  2.30-4
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1
ii  dpkg  1.19.0.5
ii  file  1:5.32-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.60-1
ii  libclass-accessor-perl0.51-1
ii  libclone-perl 0.39-1
ii  libdigest-sha-perl6.01-1
ii  libdpkg-perl  1.19.0.5
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.1-4+b1
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.73-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.69+repack-1
ii  man-db2.8.1-1
ii  patchutils0.3.4-2
ii  perl  5.26.1-4+b1
ii  t1utils   1.41-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.19.0.5
ii  libhtml-parser-perl3.72-3+b2
pn  libtext-template-perl  

-- no debconf information

Bug#890362: Add @MATCH

[積丹尼 Dan Jacobson]

Package: perl-doc
Version: 5.26.1-4
Severity: wishlist
File: /usr/share/man/man1/perlvar.1.gz

I see good progress is being made in finally exposing these.

   @{^CAPTURE}
   An array which exposes the contents of the capture buffers, if 
any, of
   the last successful pattern match, not counting patterns
   matched in nested blocks that have been exited already.

But I found one that is still missing.

There is

   $MATCH
   $&  The string matched by the last successful pattern match.

But what still needs to be added is a

   @MATCH
   @&  The array  matched by the last successful m/.../g pattern match.


OR, please add to the explanation of $&, that unlike m/.../, m/.../g's
array can always be obtained by my @F = m/.../g and thus isn't even
stored in memory, even though plain m/.../g in void context does not
trigger any warnings...

Bug#884115: r-cran-rmarkdown_1.8+dfsg-1_amd64.changes REJECTED

[Andreas Tille]

Hi Thorsten,

On Tue, Feb 13, 2018 at 10:00:10PM +, Thorsten Alteholz wrote:
> 
> the license text for ionicons.css doesn't really look like the MIT license.

This is the license text from the file:

  Ionicons, v2.0.0
  Created by Ben Sperry for the Ionic Framework, http://ionicons.com/
  https://twitter.com/benjsperry  https://twitter.com/ionicframework
  MIT License: https://github.com/driftyco/ionicons

  Android-style icons originally built by Google’s
  Material Design Icons: https://github.com/google/material-design-icons
  used under CC BY http://creativecommons.org/licenses/by/4.0/
  Modified icons to fit ionicon’s grid from original.


If you do not consider this "not really MIT" could you please give
some pointer how the license paragraph should look like?

Kind regards and thanks for your work as ftpmaster

 Andreas.


-- 
http://fam-tille.de

Bug#863118: devscripts needs proper configuration file parsing

[Nicolas Boulenguez]

Package: devscripts
Followup-For: Bug #863118
Control: tags -1 + patch

Hi.

The attached changes fix this bug.
They are intrusive and probably introduce new bugs,
but they should ease the maintenance in the long run.

Regards.


suggestions.tar.gz
Description: application/gzip

Bug#890360: RFP: vlc-plugin-bittorrent -- Bittorrent plugin for VLC

[Petter Reinholdtsen]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: Debian Multimedia Maintainers 


* Package name: vlc-plugin-bittorrent
  Version : n/a, no tags in git
  Upstream Author : Johan Gunnarsson
* URL : https://github.com/johang/vlc-bittorrent
* License : GPL
  Description : Bittorrent plugin for VLC

 VLC is the VideoLAN project's media player.
 .
 This plugin adds support streaming content using bittorrent, either by
 specifying a torrent file, or by providing a magnet link.

I've tested the code and made a draft package, and the plugin work.  I
contacted the author in
https://github.com/johang/vlc-bittorrent/issues/1 >, asking if he
want to get the source packaged.  If so, I hope he can be convinced to
tag releases and quickly fix bugs we discovver.

-- 
Happy hacking
Petter Reinholdtsen

Bug#890358: lintian could warn when using dh --parallel in compat level >= 10

[Chris Lamb]

tags 890358 + pending
thanks

Good idea. Fixed in Git, pending upload:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=6a98ddc78b2e8a1822cfc48ebb5385ff61ccb7e7


Regards,

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

Bug#890359: binutils: Fix GOT relocation overflow on SPARC

[John Paul Adrian Glaubitz]

Source: binutils
Version: 2.30-4
Severity: normal
Tags: patch upstream
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hi!

binutils upstream contains another fix for sparc64 which we
need to address some memory corruption issues for the generated
binaries.

In particular, the fix is necessary to further unbreak the rust
compiler on sparc64, with one other fix necessary to completely
fix rustc on sparc64.

Since this particular bug causes the generated binaries to be
corrupted, it's rather important to have this patch soonish.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
Description: Fix GOT relocation overflow on SPARC.
 There are 2 failures left in the linker testsuite on SPARC64/Linux and
 they are caused by 2 different issues leading to the same end effect:
 the overflow of the relocation section for the GOT, i.e. the linker
 generates too many dynamic relocations for the GOT wrt the size of the
 relocation section, leading to memory corruption and missing relocations
 in the final binary.
 .
 The first issue was introduced by:
  https://sourceware.org/ml/binutils/2017-06/msg00368.html
 which makes the linker generate more R_SPARC_RELATIVE relocations for
 the GOT without adjusting the size of the relocation section.  This is
 fixed by (1) preventively adjusting this size in allocate_dynrelocs and
 (2) generating R_SPARC_NONE if needed when R_SPARC_GOTDATA_OP is relaxed.
 .
 The second issue is that we generate a GOT relocation for an undefined
 weak symbol with non-default visibility in a PIC binary without accounting
 for that  in the size of the relocation section.  Since the address of the
 symbol should resolve to 0 at run time, it is fixed by not generating the
 relocation at all, i.e. leaving the GOT entry zeroed.
 .
Author: Eric Botcazou 
Last-Update: 2018-02-11

--- binutils-2.30.orig/bfd/elfxx-sparc.c
+++ binutils-2.30/bfd/elfxx-sparc.c
@@ -673,9 +673,9 @@ _bfd_sparc_elf_info_to_howto (bfd *abfd
   ((EH)->elf.root.type == bfd_link_hash_undefweak  \
&& bfd_link_executable (INFO)   \
&& (_bfd_sparc_elf_hash_table (INFO)->interp == NULL\
-   || !(EH)->has_got_reloc \
+   || !(INFO)->dynamic_undefined_weak  \
|| (EH)->has_non_got_reloc  \
-   || !(INFO)->dynamic_undefined_weak))
+   || !(EH)->has_got_reloc))
 
 /* SPARC ELF linker hash entry.  */
 
@@ -750,6 +750,7 @@ sparc_elf_append_rela (bfd *abfd, asecti
   bfd_byte *loc;
 
   bed = get_elf_backend_data (abfd);
+  BFD_ASSERT (s->reloc_count * bed->s->sizeof_rela < s->size);
   loc = s->contents + (s->reloc_count++ * bed->s->sizeof_rela);
   bed->s->swap_reloca_out (abfd, rel, loc);
 }
@@ -1310,8 +1311,7 @@ _bfd_sparc_elf_copy_indirect_symbol (str
   eind->dyn_relocs = NULL;
 }
 
-  if (ind->root.type == bfd_link_hash_indirect
-  && dir->got.refcount <= 0)
+  if (ind->root.type == bfd_link_hash_indirect && dir->got.refcount <= 0)
 {
   edir->tls_type = eind->tls_type;
   eind->tls_type = GOT_UNKNOWN;
@@ -2004,8 +2004,8 @@ _bfd_sparc_elf_adjust_dynamic_symbol (st
   if (h->plt.refcount <= 0
  || (h->type != STT_GNU_IFUNC
  && (SYMBOL_CALLS_LOCAL (info, h)
- || (ELF_ST_VISIBILITY (h->other) != STV_DEFAULT
- && h->root.type == bfd_link_hash_undefweak
+ || (h->root.type == bfd_link_hash_undefweak
+ && ELF_ST_VISIBILITY (h->other) != STV_DEFAULT
{
  /* This case can occur if we saw a WPLT30 reloc in an input
 file, but the symbol was never referred to by a dynamic
@@ -2124,12 +2124,11 @@ allocate_dynrelocs (struct elf_link_hash
  && h->def_regular
  && h->ref_regular))
 {
-  /* Make sure this symbol is output as a dynamic symbol.
-Undefined weak syms won't yet be marked as dynamic.  */
-  if (h->dynindx == -1
- && !h->forced_local
+  /* Undefined weak syms won't yet be marked as dynamic.  */
+  if (h->root.type == bfd_link_hash_undefweak
  && !resolved_to_zero
- && h->root.type == bfd_link_hash_undefweak)
+ && h->dynindx == -1
+ && !h->forced_local)
{
  if (! bfd_elf_link_record_dynamic_symbol (info, h))
return FALSE;
@@ -2237,12 +2236,11 @@ allocate_dynrelocs (struct elf_link_hash
   bfd_boolean dyn;
   int tls_type = _bfd_sparc_elf_hash_entry(h)->tls_type;
 
-  /* Make sure this symbol is output as a dynamic symbol.
-Undefined weak syms won't yet be marked as dynamic.  */
-  if (h->dynindx == -1
- && !h->forced_local
+  /* Undefined weak syms won't yet be marked as 

Bug#890345: Pending fixes for bugs in the jflex package

[pkg-java-maintainers]

tag 890345 + pending
thanks

Some bugs in the jflex package are closed in revision
caae45e2eef3779fc526f21acfd071e78e91136e in branch 'master' by Markus
Koschany

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

Commit message:

Change dependency from default-jre to default-jre-headless |

java7-runtime-headless.

Closes: #890345
Thanks: Kai-Chung Yan for the report.

Bug#890358: lintian could warn when using dh --parallel in compat level >= 10

[Nicolas Braud-Santoni]

Package: lintian
Version: 2.5.73
Severity: wishlist

Hi,

When using debhelper in compatibility mode 10 or higher,
the --parallel option is enabled by default.

Please consider making lintian warn about redundant use of --parallel.


Best,

  nicoo


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable')
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) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lintian depends on:
ii  binutils  2.29.1-13
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.19.0.5
ii  file  1:5.32-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.60-1
ii  libclass-accessor-perl0.51-1
ii  libclone-perl 0.39-1
ii  libdpkg-perl  1.19.0.5
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.1-4
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.73-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.69+repack-1
ii  man-db2.7.6.1-4
ii  patchutils0.3.4-2
ii  perl  5.26.1-4
ii  t1utils   1.41-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.19.0.5
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.47-1

-- no debconf information


signature.asc
Description: PGP signature

Bug#887284: autofs should depend on e2fsprogs explicitly

[Andreas Henriksson]

Control: retitle -1 autofs should build-depend and recommend e2fsprogs
Control: tags -1 + confirmed

On Sun, Jan 14, 2018 at 08:02:46PM +0100, Helmut Grohne wrote:
> Package: autofs
[...]
> /usr/lib/x86_64-linux-gnu/autofs/mount_ext2.so contains fsck.ext2, fsck.ext3 
> and fsck.ext4. According to file it is a ELF 64-bit LSB shared object, 
> x86-64, version 1 (SYSV)
[...]

Other filesystem specific mount modules has the package for their
respective tools in the Recommends field so I would say that's
where e2fsprogs belongs as well. (But someone might decide to make
it a stronger Depends just because ext is somehow special.)

Additionally the configure script tries to look up the full path
for the tools, so e2fsprogs should likely also be added to
build-depends to make sure the tools are around and can be
detected at build-time.

I'm CCing Laurent Bigonville who has done the previous QA upload
and also has a pending change in the packaging repository hoping
he can upload both of them at the same time.

Regards,
Andreas Henriksson

Bug#879458: inputlirc: diff for NMU version 23-2.1

[Christoph Biedl]

Control: tags 879458 + patch
Control: tags 879458 + pending

Ingo Schneider wrote...

> Package: inputlirc
> Version: 23-2+b2
> Severity: grave
> Tags: patch
> Justification: renders package unusable

Dear maintainer,

as I got confirmation from another side this patch fixes the issue, I've
prepared an NMU for inputlirc (versioned as 23-2.1) and uploaded it to
DELAYED/2. Please feel free to tell me if I should delay it longer.

Additionally, I'd also like to see this fixed in an upcoming stretch
point release and might start the procedure on my own as well. Any "go"
or "no go" is appreciated.

Regards.

Christoph

diff -u inputlirc-23/debian/changelog inputlirc-23/debian/changelog
--- inputlirc-23/debian/changelog
+++ inputlirc-23/debian/changelog
@@ -1,3 +1,11 @@
+inputlirc (23-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Include input-event-codes.h instead of input.h. Closes: #879458
+Thanks to Ingo Schneider for reporting the bug and providing the fix.
+
+ -- Christoph Biedl   Tue, 13 Feb 2018 
22:16:20 +0100
+
 inputlirc (23-2) unstable; urgency=medium
 
   * Set Architecture: linux-any, since inputlirc depends on the Linux input
only in patch2:
unchanged:
--- inputlirc-23.orig/Makefile
+++ inputlirc-23/Makefile
@@ -27,7 +27,7 @@
 
 all: $(SBIN)
 
-names.h: /usr/include/linux/input.h gennames
+names.h: /usr/include/linux/input-event-codes.h gennames
./gennames $< > $@
 
 inputlircd: inputlircd.c /usr/include/linux/input.h names.h


signature.asc
Description: PGP signature

Bug#878834: still broken in discord

[tony]

I understand if this is not that relevant since discord is not in the 
official repos, but the rendering there is still broken.


According to their support chat the rendering in discord is fine with 
libfreetype2.9 so they won't fix it on their end like thunderbird did.


I guess my question is when will we get the next version of this package?

Thanks,
Tony

Bug#890188: workaround

[Iain Learmonth]

Hi,

For a workaround, I've found adding:

from dput.util import get_interface

in /usr/lib/python2.7/dist-packages/dput/command.py amongst the other
imports seems to fix this.

Thanks,
Iain.



signature.asc
Description: OpenPGP digital signature

Bug#872112: linaro-image-tools NMU uploaded to DELAYED/5

[Andreas Henriksson]

Control: tags -1 + pending

Hello,

I've uploaded the attached debdiff as an NMU to DELAYED/5.

Regards,
Andreas Henriksson
diff -Nru linaro-image-tools-2016.05/debian/changelog 
linaro-image-tools-2016.05/debian/changelog
--- linaro-image-tools-2016.05/debian/changelog 2016-09-27 23:43:55.0 
+0200
+++ linaro-image-tools-2016.05/debian/changelog 2018-02-13 22:13:39.0 
+0100
@@ -1,3 +1,17 @@
+linaro-image-tools (2016.05-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Andreas Henriksson ]
+  * Add fdisk dependency and build-depedency (Closes: #872112)
+  * Add e2fsprogs dependency (Closes: #887174)
+  * Add e2fsprogs build-dependency for test-suite (Closes: #887301)
+
+  [ Nicholas D Steeves ]
+  * Change Recommends: btrfs-tools to btrfs-progs (Closes: #878913)
+
+ -- Andreas Henriksson   Tue, 13 Feb 2018 22:13:39 +0100
+
 linaro-image-tools (2016.05-1) unstable; urgency=medium
 
   * New upstream release. (Closes: #747300, #806068, #820454)
diff -Nru linaro-image-tools-2016.05/debian/control 
linaro-image-tools-2016.05/debian/control
--- linaro-image-tools-2016.05/debian/control   2016-09-27 23:43:55.0 
+0200
+++ linaro-image-tools-2016.05/debian/control   2018-02-13 22:11:41.0 
+0100
@@ -4,6 +4,8 @@
 Build-Depends: apt-utils,
debhelper (>= 8.1.3~),
dh-python,
+   e2fsprogs,
+   fdisk | util-linux (<< 2.29.2-3~),
dosfstools,
python (>= 2.6.6-3~),
python-all (>= 2.6.6-3~),
@@ -27,6 +29,8 @@
 Architecture: linux-any
 Depends: apt-utils,
  dosfstools,
+ e2fsprogs,
+ fdisk | util-linux (<< 2.29.2-3~),
  gdisk,
  parted,
  python (>= 2.6.6-3~),
@@ -40,7 +44,7 @@
  u-boot-tools | uboot-mkimage,
  ${misc:Depends},
  ${python:Depends}
-Recommends: btrfs-tools,
+Recommends: btrfs-progs,
 command-not-found,
 qemu-user-static | qemu-kvm-extras-static,
 udisks2 [linux-any]

Bug#890356: lintian.d.o: maintainer reports (particular "full" ones) grows without bounds in size

[Niels Thykier]

Package: lintian
Version: 2.5.73
Severity: normal

Hi,

The maintainer reports (notably the "full" reports) quickly grows in
size (disk space used) and without any bounds.  At the moment, the
lintian.d.o has a complete size usage of ~1GB - half of that is "full
reports" - the second runner up is the uncompressed lintian.log (at
250MB), which will disappear soon.

Individual reports have exploded and the top 10 ranges from ~7.5 to
30MB in raw HTML size[1].  These pages are so painful to low that it
feels like the browser is about to croak on the load/pressure.  I
doubt anyone is reading these reports (I certainly would not at that
scale).

I think we need some better way to deal with these reports.  My best
idea to date is to extract the package reports into a separate report
page and just link to them from the maintainer pages.  However, that
will make the maintainer pages rather useless/boring on their own (but
at least they would probably be "loadable").

Thanks,
~Niels

[1]
$ ls -hlarS reports-directory/www/full | tail
-rw-r--r-- 1 lintian lintian  7.3M Feb 13 04:20 
python-modules-t...@lists.alioth.debian.org.html
-rw-r--r-- 1 lintian lintian  9.7M Feb 13 04:20 
pkg-haskell-maintain...@lists.alioth.debian.org.html
-rw-r--r-- 1 lintian lintian   11M Feb 13 04:20 debian-...@lists.debian.org.html
-rw-r--r-- 1 lintian lintian   12M Feb 13 04:20 
pkg-perl-maintain...@lists.alioth.debian.org.html
-rw-r--r-- 1 lintian lintian   14M Feb 13 04:21 d...@debian.org.html
-rw-r--r-- 1 lintian lintian   17M Feb 13 04:22 than...@debian.org.html
-rw-r--r-- 1 lintian lintian   18M Feb 13 04:21 calcu...@rezozer.net.html
-rw-r--r-- 1 lintian lintian   18M Feb 13 04:21 julien.pu...@laposte.net.html
-rw-r--r-- 1 lintian lintian   18M Feb 13 04:22 infini...@debian.org.html
-rw-r--r-- 1 lintian lintian   30M Feb 13 04:20 
debian-science-maintain...@lists.alioth.debian.org.html

Bug#890355: man: nroff: Bad system call

[Thorsten Glaser]

Package: man-db
Version: 2.8.1-1
Severity: grave
Justification: renders package unusable

-begin screenshot-
tglase@tglase:~ $ man ls
man: nroff: Bad system call
 Manual page ls(1) line ?/? (END) (press h for help or q to quit)
-end screenshot-

This one works, though:
tglase@tglase:~ $ zcat /usr/share/man/man1/ls.1.gz | nroff -mandoc


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

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

Versions of packages man-db depends on:
ii  bsdmainutils   11.1.2
ii  debconf [debconf-2.0]  1.5.65
ii  dpkg   1.19.0.5
ii  groff-base 1.22.3-10
ii  libc6  2.26-6
ii  libgdbm5   1.14.1-3
ii  libpipeline1   1.5.0-1
ii  libseccomp22.3.1-2.1
ii  zlib1g 1:1.2.8.dfsg-5

man-db recommends no packages.

Versions of packages man-db suggests:
pn  apparmor
ii  dillo [www-browser] 3.0.5-4
ii  groff   1.22.3-10
ii  less487-0.1
ii  links2 [www-browser]2.14-5
ii  lynx [www-browser]  2.8.9dev16-2
ii  opera-static [www-browser]  9.64.2480.gcc4.qt3

-- debconf information:
  man-db/install-setuid: false
  man-db/auto-update: true

Bug#872375: lirc: irrecord segfaults when recording a button

[Alec Leamas]

On Sun, 11 Feb 2018 10:07:02 -0800 James Bottomley
 wrote:
> I'm getting this same segfault as well.  My old remote fell apart, so I
> was trying to train the IR receiver on a new one (well, the unused VCR
> section of the current TV remote.

> This is what I get:

[cut]

> Usually you should not create a new config file for devinput
> devices. LIRC is installed with a devinput.lircd.conf file which 
> is built for the current system which works with all remotes 
> supported by the kernel. There might be a need to update 
> this file so it matches the current kernel. For this, use the 
> lirc-make-devinput(1) script.
>
> Press RETURN to continue.


This message really says it all: using irrecord  with the devinput
driver is a useless and dangerous idea. See my other replies in the bug
for more.


Cheers!

--alec

Bug#890354: ITP: nm-tray -- a simple NetworkManager front end written in KF5/Qt

[Alf Gaida]

Package: wnpp
Severity: wishlist
Owner: Alf Gaida 

* Package name: nm-tray
  Version : 0.3.0
  Upstream Author : Palo Kisa 
* URL : https://github.com/palinek/nm-tray
* License : GPL-2.0+
  Programming Lang: C++
  Description : a simple NetworkManager front end written in KF5/Qt

nm-tray is a simple NetworkManager front end with information icon residing in
system tray (like e.g. nm-applet). It's a pure Qt application. For interaction
with NetworkManager it uses API provided by KF5::NetworkManagerQt -> plain DBus
communication.

Qt-Frontend for network-manager - there is no alternative, unless one will see
cmst as connman-frontend as an alternative. The LXQt team will maintain the 
package.

Bug#890353: ftp.debian.org: RM: angband-doc -- ROM Obsolete

[Manoj Srivastava]

Package: ftp.debian.org
Severity: normal

The information packaged here is obsolete; the built in documentation in
newer releases of Angband  is a better source these days.

manoj
-- 
Diogenes went to look for an honest lawyer. "How's it going?", someone
asked him, after a few days. "Not too bad", replied Diogenes. "I still
have my lantern."
Manoj Srivastava  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


smime.p7s
Description: S/MIME cryptographic signature

Bug#887295: tomb should depend on e2fsprogs explicitly

[Andreas Henriksson]

Control: forwarded -1 
https://salsa.debian.org/pkg-security-team/tomb/merge_requests/1
Control: tags -1 + patch

Hello,

the required change has been sent as a merge request on salsa which
seems to be the current home for the packaging of tomb.

Looking forward to see the maintainers review, merge and upload
this soon. Please speak up if you're busy and would like help
with a non-maintainer upload!

Regards,
Andreas Henriksson

Bug#890352: activemq: CVE-2017-15709: information leak

[Salvatore Bonaccorso]

Source: activemq
Version: 5.14.3-3
Severity: important
Tags: security upstream

Hi,

the following vulnerability was published for activemq, filling the
bug based on the information available from [0] and [1].

CVE-2017-15709[0]:
| When using the OpenWire protocol in ActiveMQ versions 5.14.0 to 5.15.2
| it was found that certain system details (such as the OS and kernel
| version) are exposed as plain text.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15709
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15709
[1] http://www.openwall.com/lists/oss-security/2018/02/13/4

Regards,
Salvatore

Bug#890351: remmina: Suggest Remmina plugins

[John Scott]

Source: remmina
Version: 1.2.0-rcgit.26+dfsg-1
Severity: wishlist
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The Remmina source package builds several plugins that are not usually
installed by default, though these plugins do not have any reverse
dependencies. In order to install these, they must be marked manually
installed despite the fact that they serve no purpose on their own.

That's silly, so I'm including a patch to make things right. 

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

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

- -- no debconf information

*** patch.diff
diff --git a/debian/control b/debian/control
index b316bd8..9c374fd 100644
- --- a/debian/control
+++ b/debian/control
@@ -39,6 +39,12 @@ Depends:
 Recommends:
  remmina-plugin-rdp,
  remmina-plugin-vnc
+Suggests:
+ remmina-plugin-xdmcp,
+ remmina-plugin-nx,
+ remmina-plugin-spice,
+ remmina-plugin-telepathy,
+ remmina-plugin-secret
 Description: GTK+ Remote Desktop Client
  Remmina is a remote desktop client written in GTK+, aiming to be
  useful for system administrators and travellers, who need to work

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEJwCMxdBfG24Y2trvfWFEpid5MHIFAlqDSc4SHGpzY290dEBw
b3N0ZW8ubmV0AAoJEH1hRKYneTByXQAH/i2++TV1vETvdB0AzL1T9pGyYi6zBwUC
iC+8duIquXkHoMq4+S/oOVGkJKswitVNpjT1CWMKoYyaoO437rGlEs39aMuQp0j7
VIzzyZe78XWgEd3JZK0ULYdQC058nrrwycSXa+jpWf8cOdhK5XiU+RwJd3qL0azC
+yBLA8IE9khF8+ArgbZJoMSSb028TUwJRUGnkHC9HJc+eF10bQ5aUi6SfjM6GxBe
n98VcjpvdURcAG0ZrlFX/3vyRQ3t5q/0FapAK/gGTNYneqmHlIwSbbgCEmE/5M6e
pMD82GH55md0tWNpZshlZhMVmnmfMVEXzwVM+Hh9f5glpkXW+Oqy/BI=
=yif2
-END PGP SIGNATURE-

Bug#887834: [Pkg-mpd-maintainers] Bug#887834: mpd installation fails, cannot open /var/lib/mpd/tag_cache, /run/mpd/pid

[Florian Schlichting]

Control: tags 887834 + moreinfo


Hi Guillaume,

> When attempting to install the mpd package from Debian testing, it fails
> with the following errors:
> 
> > Setting up mpd (0.20.14-1) ...
> > Job for mpd.service failed because the control process exited with error 
> > code.
> > See "systemctl status mpd.service" and "journalctl -xe" for details.
> > invoke-rc.d: initscript mpd, action "start" failed.
> > ● mpd.service - Music Player Daemon
> >Loaded: loaded (/lib/systemd/system/mpd.service; disabled; vendor 
> > preset: enabled)

if this is a first install, why would mpd.service be disabled?

> >Active: failed (Result: exit-code) since Sat 2018-01-20 12:37:07 CET; 
> > 16ms ago
> >  Docs: man:mpd(1)
> >man:mpd.conf(5)
> >file:///usr/share/doc/mpd/user-manual.html
> >   Process: 5411 ExecStart=/usr/bin/mpd --no-daemon $MPDCONF (code=exited, 
> > status=1/FAILURE)
> >  Main PID: 5411 (code=exited, status=1/FAILURE)
> > 
> > Jan 20 12:37:06 sark systemd[1]: Starting Music Player Daemon...
> > Jan 20 12:37:07 sark mpd[5411]: Jan 20 12:37 : exception: Failed to open 
> > /var/lib/mpd/tag_cache: No such file or directory
> > Jan 20 12:37:07 sark mpd[5411]: Jan 20 12:37 : fatal_error: Failed to 
> > create pid file "/run/mpd/pid": No such file or directory

This is the fatal error: /run/mpd does not exist. It is created through
/usr/lib/tmpfiles.d/mpd.conf; any idea why this didn't happen in your
case?

Florian

Bug#887240: bootstrap-vz should depend on e2fsprogs explicitly

[Andreas Henriksson]

Control: tags -1 + pending

Hello,

It seems the bootstrap-vz package has been imported to salsa.debian.org
(and had it's repository on alioth removed).
The relevant change for this bug report seems to also have been
committed:

https://salsa.debian.org/cloud-team/bootstrap-vz/commit/157c0270ce95efa0b517a2fb958c1966b3c114a4

I'm thus tagging this bug report pending and hoping the maintainer(s)
will be uploading the fixed version soon.

Regards,
Andreas Henriksson

Bug#887209: debootstick should depend on e2fsprogs explicitly

[Andreas Henriksson]

Hello Etienne Dublé,

On Tue, Feb 13, 2018 at 08:16:31PM +0100, Etienne DUBLE wrote:
> Hi,
> I am the maintainer of debootstick, sorry for the silence.

Thanks for your reply now though!

> Yes, I uploaded a fixed version at:
> https://mentors.debian.net/package/debootstick
> My sponsor (Vincent Danjean) should review it shortly.

Thanks for this information. If Vincent Danjean is too busy at the
moment please feel free to reach out for temporary help with sponsorship!

> Is it an urgent matter? I mean, what is the expected date for the
> removal of e2fsprogs from essentials?

We're aiming at getting this done before buster goes into freeze.
For a change to the base system like this, the change (in e2fsprogs
package) needs to happen well before the freeze date. There's no strict
date for when all the bug reports Helmut filed needs to be done though,
but the sooner the better. The most important part is knowing that
maintainers have a plan for their package so we can identify the
packages which needs help being taken care of.

Regards,
Andreas Henriksson

Bug#890345: Depending on "default-jre-headless" Should be Sufficient

[Markus Koschany]

Am 13.02.2018 um 19:26 schrieb 殷啟聰 | Kai-Chung Yan:
> Package: jflex
> Version: 1.6.1-2
> Severity: wishlist
> 
> "jflex" seems to me a commandline program, thus depending on 
> "default-jre-headless" should be sufficient. Right now it depends on 
> "default-jre" and "pbuilder" always fetches the whole graphical stack while 
> building "libsmali-java".


For building packages it doesn't bother me much but I agree that it
should depend on default-jre-headless at runtime. I can change that.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#887264: sbuild should depend on e2fsprogs explicitly

[Andreas Henriksson]

On Sun, Jan 14, 2018 at 08:11:17PM +0100, Helmut Grohne wrote:
> Package: sbuild
[...]
> /usr/share/sbuild/create-chroot contains mkfs.ext4 and tune2fs. According to 
> file it is a Bourne-Again shell script, ASCII text executable
[...]

The create-chroot script uses the mkfs.ext4 and tune2fs commands if and
only if the script is called with the optional volume-group argument
specified.

I can not find any other part of sbuild that calls the create-chroot
script.

I'm not sure what the rationale is for installing the script in the
location where it's shipped (rathen than just putting it in /usr/sbin
or similar).

https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit?id=18512e3303f56a55841719e393c3e5a4653c9b70

https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/bin/create-chroot?h=debian/unstable=f5c642e0786356ccb58d141dda0dbebf0778227a


https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/bin/create-chroot?h=debian/unstable=1dff84941e8294158a1a4346996556d39bcf8d3c

https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit?h=debian/unstable=a0b923fccf6fea35becb330b47ccd14b9d36b012

Please note that there's also a completely separate sbuild-createchroot
command which seems to do a similar job. (Maybe 'create-chroot' is an
ancient leftover kept around for legacy reasons?)

My conclusion is that a dependency on e2fsprogs is likely not strictly
needed. A Recommends or Suggests might be considered, but given
e2fsprogs will be installed in *any* system except where the admin
has explicitly uninstalled it, I think that gives very little benefit.

It would be great to hear from maintainers on this!

Regards,
Andreas Henriksson

Bug#885939: [marionnet] Crash on startup: fixed in sid (0.90.6+bzr508)

[nodiscc]

The bug looks fixed in marionnet_0.90.6+bzr508.orig.tar.gz. Though I
have not actually tested this version, only checked the source
tarball.

https://deb.debian.org/debian/pool/main/m/marionnet/marionnet_0.90.6+bzr457.orig.tar.gz/usr/share/marionnet/images/launcher-icons/marionnet-launcher.png
is corrupted for me and some people on #debian IRC. The one in
marionnet_0.90.6+bzr508.orig.tar.gz works fine.

After applying the fix I suggested earlier (optipng), the program
starts but displays a bunch of other error messages and UI items are
missing. At this point I'll assume it's unusable for me on stable,
I'll wait for the next release.

Bug#887209: debootstick should depend on e2fsprogs explicitly

[Etienne DUBLE]

Hi,
I am the maintainer of debootstick, sorry for the silence.
Yes, I uploaded a fixed version at:
https://mentors.debian.net/package/debootstick
My sponsor (Vincent Danjean) should review it shortly. Is it an urgent
matter? I mean, what is the expected date for the removal of e2fsprogs from
essentials?
Regards
Etienne Dublé


2018-02-13 17:25 GMT+01:00 Andreas Henriksson :

> Control: tags -1 + pending
>
> Hello again,
>
> After spending time on analysing and writing a followup on the bug
> report I noticed the package tracker saying there's a new version
> in the git repository that claims to have this issue fixed (and
> the version release to unstable on 31 jan 2018!).
>
> I'm thus tagging the bug as pending and hoping we'll soon see the
> version actually be part of the debian archive.
>
> Regards,
> Andreas Henriksson
>

Bug#889968: RFS: inotify-tools/3.14-4

[Sean Whitton]

Hello Dmitry,

On Tue, Feb 13 2018, kact...@gnu.org wrote:

> [2018-02-12 13:07] Sean Whitton 
>> > Last version is at bacef877c2f9293f9e1fd624b32d5306d7bc3c27 Maybe,
>> > you could try again?
>>
>> Still FTBFSs.  Log attached.
>>
>> I suspect that the debomatic sid chroot is out-of-date.
>
> Stange. Just did 'sbuild-update -udcar', and still fails to reproduce.
> I have same version of build-essential, by the way.
>
> Added debomatic admin into CC, maybe he has any opinion about
> situation.  If not, I could remove sanitize support, although I am not
> so happy with it. Or maybe you could tar.gz your chroot and upload
> somewhere?

I tried deleting and rebuilding my chroot and disabling ccache and
tmpfs, and I tried building on my i386 machine, again after rebuilding,
disabling ccache and disabling tmpfs.

In all cases the package FTBFS.  I attach my i386 log..

I'm not sure how to proceed.  I can't upload this if I can't build it,
and my configuration seems sufficiently standard that even if you are
able to build it, we shouldn't upload.  Maybe we should try disabling
sanitize support for now.

-- 
Sean Whitton


inotify-tools_3.14-4_i386-2018-02-13T19:12:26Z.build
Description: Binary data


signature.asc
Description: PGP signature

Bug#890350: splint: Internal Bug constraintGeneration.c: llassert failed: exprNode_isDefined(t1) [errno: 25]

[Shea Newton]

Package: splint
Version: 3.1.2.dfsg1-2
Severity: normal

Dear Maintainer,

I've run into some C syntax that causes the `splint` program to report an 
"Internal Bug".

Here is the exact command and its output.

```
$ splint constant.c  
Splint 3.1.2 --- 03 May 2009 

constraintGeneration.c:1381: at source point 
constant.c:9:2: *** Internal Bug at constraintGeneration.c:1381: 
  llassert failed: exprNode_isDefined(t1) [errno: 25] 
*** Please report bug to sub...@bugs.debian.org (via reportbug) *** 
  (attempting to continue, results may be incorrect) 

Finished checking --- no warnings 
  1 internal bugs reported

```

And here is the reduced program that causes this report.

```
/*
 * constant.c
 */

int main(void)
{
const int * const const_val = &(int){ 1234 };
return *const_val;
}
```

Thank you.

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

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

Versions of packages splint depends on:
ii  libc62.23-0ubuntu10
ii  splint-data  3.1.2.dfsg1-2

splint recommends no packages.

Versions of packages splint suggests:
pn  splint-doc-html  

-- no debconf information

Bug#883573: Call for vote on waiving libpam-systemd dependencies' ordering

[Tollef Fog Heen]

]] Didier 'OdyX' Raboud 

> === Resolution ===
> 
> In 2014, it was resolved in #746578 that the libpam-systemd binary package 
> alternative dependency on systemd-shim and systemd-sysv shall be set in that 
> order, in order to avoid unwanted init system changes accross upgrades. 
> Debian 
> Stretch has since been released.
> 
> The Committee therefore resolves that:
> 
> 1. The Technical Commitee decision from 2014-11-15 in bug #746578 is repealed.
> 
> This means Debian's normal policies and practices take over and the
> libpam-systemd package's dependencies are set free from specific ordering 
> constraints.  The migration should be managed according to Debian's usual 
> backwards-compatibility arrangements.
> 
> === End Resolution ===
> 
> R: Approve resolution and repeal the TC decision from 2014-11-15 in #746578.
> F: Further Discussion

I vote R > F.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#889968: RFS: inotify-tools/3.14-4

[Sean Whitton]

Hello,

On Tue, Feb 13 2018, Luca Falavigna wrote:

> 2018-02-13 4:18 GMT+01:00 :
>>> I suspect that the debomatic sid chroot is out-of-date.
>
> amd64 chroot was updated on Sunday, February 11, 2018 4:20:10 PM UTC
> (1518366010.2514317).

Thanks for the feedback!

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#889668: util-linux: diff for NMU version 2.31.1-0.2

[Laurent Bigonville]

Dear maintainer,

You will find here a 2nd version of the patch to fix the bug #889668.

The previous version was not taking into account the non-linux architectures.

Regards.
diff -Nru util-linux-2.31.1/debian/changelog util-linux-2.31.1/debian/changelog
--- util-linux-2.31.1/debian/changelog  2018-02-09 19:16:51.0 +0100
+++ util-linux-2.31.1/debian/changelog  2018-02-13 12:19:06.0 +0100
@@ -1,3 +1,11 @@
+util-linux (2.31.1-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install fstrim.timer and fstrim.service without enabling it by default
+(for now), see discussion in #732054 (Closes: #889668)
+
+ -- Laurent Bigonville   Tue, 13 Feb 2018 12:19:06 +0100
+
 util-linux (2.31.1-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru util-linux-2.31.1/debian/rules util-linux-2.31.1/debian/rules
--- util-linux-2.31.1/debian/rules  2018-02-09 19:16:51.0 +0100
+++ util-linux-2.31.1/debian/rules  2018-02-13 12:19:06.0 +0100
@@ -157,6 +157,12 @@
 override_dh_fixperms:
dh_fixperms -i -a -Xusr/bin/wall -Xbin/mount -Xbin/umount
 
+ifeq (linux,$(DEB_HOST_ARCH_OS))
+override_dh_installsystemd:
+   dh_installsystemd -putil-linux --no-enable --no-start fstrim.timer 
fstrim.service
+   dh_installsystemd --remaining-packages
+endif
+
 override_dh_auto_test:
 ifeq ($(DEB_HOST_ARCH_OS), linux)
dh_auto_test --max-parallel=1
diff -Nru util-linux-2.31.1/debian/util-linux.install 
util-linux-2.31.1/debian/util-linux.install
--- util-linux-2.31.1/debian/util-linux.install 2018-02-09 19:16:51.0 
+0100
+++ util-linux-2.31.1/debian/util-linux.install 2018-02-12 18:03:47.0 
+0100
@@ -7,8 +7,8 @@
 [linux-any] sbin/mkswap
 [!linux-any] debian/tmp/sbin/mkswap => /sbin/mkswap.linux
 # weekly fstrim only available on linux
-[linux-any] lib/systemd/system/fstrim.timer => 
/usr/share/doc/util-linux/examples/fstrim.timer
-[linux-any] lib/systemd/system/fstrim.service => 
/usr/share/doc/util-linux/examples/fstrim.service
+[linux-any] lib/systemd/system/fstrim.timer
+[linux-any] lib/systemd/system/fstrim.service
 bin/findmnt
 bin/more
 bin/mountpoint

Bug#890348: epstool FTBFS on ia64: error: 'TRAP_TRACE' undeclared here

[Adrian Bunk]

Source: epstool
Version: 3.08+repack-6
Severity: important
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=epstool=ia64=3.08+repack-6=1518522907=0

...
In file included from /usr/include/ia64-linux-gnu/bits/siginfo-consts.h:184:0,
 from /usr/include/signal.h:58,
 from /usr/include/ia64-linux-gnu/sys/wait.h:36,
 from ./src/epstool.c:42:
/usr/include/ia64-linux-gnu/bits/siginfo-consts-arch.h:39:17: error: 
'TRAP_TRACE' undeclared here (not in a function); did you mean '_SC_TRACE'?
   TRAP_BRANCH = TRAP_TRACE + 1,
 ^~
 _SC_TRACE
./src/epstool.c: In function 'calc_device_size':
./src/epstool.c:1716:9: warning: variable 'code' set but not used 
[-Wunused-but-set-variable]
 int code = 0;
 ^~~~
./src/epstool.c: In function 'epstool_dcs2_composite':
./src/epstool.c:1909:9: warning: variable 'hires_bbox_valid' set but not used 
[-Wunused-but-set-variable]
 int hires_bbox_valid = 0;
 ^~~~
src/common.mak:205: recipe for target 'epsobj/epstool.o' failed
make[1]: *** [epsobj/epstool.o] Error 1



Fix attached.
Description: src/cplat.h: Don't define __USE_GNU
 There were two things wrong with it:
 - __USE_GNU is glibc-internal, the external
   define is _GNU_SOURCE
 - defining such macros after the first include
   is wrong, in this case it caused FTBFS on ia64
 .
 An option would be to to pass -D_GNU_SOURCE
 when building, but as far as I can see the
 define was not (anymore?) needed at all.
Author: Adrian Bunk 

--- epstool-3.08+repack.orig/src/cplat.h
+++ epstool-3.08+repack/src/cplat.h
@@ -114,7 +114,6 @@ typedef struct POINT_s {
 typedef struct _GdkRgbCmap GdkRgbCmap;
 # endif
 # include 
-# define __USE_GNU /* we might need recursive mutex */
 # include 
 # include 
 # define ZLIBNAME "libz.so"

Bug#890349: override: gnome-orca/oldlibs

[Jeremy Bicha]

Package: ftp.debian.org

Please move the transitional package gnome-orca to oldlibs.
debian/control has already been updated.

Thanks,
Jeremy Bicha

Bug#890347: override: gnome-tweak-tool/oldlibs

[Jeremy Bicha]

Package: ftp.debian.org

Please move the transitional package gnome-tweak-tool to oldlibs.
debian/control has already been updated.

Thanks,
Jeremy Bicha

Bug#887262: dtc-xen nmu pending

[Andreas Henriksson]

Control: tags -1 + pending

Hello,

I've uploaded a NMU fixing this bug report. Please see attached debdiff.

Please see lintian warnings for additional work that this package would
likely highly benefit from. For example this one points to something
which seems very peculiar:
W: dtc-xen-firewall: command-with-path-in-maintainer-script postinst:44 
/sbin/service

The 'service' command is supposed to be a local administrator command
and maintainer scripts should use invoke-rc.d according to Debian
policy. On the other hand, the invokation is guarded by 
if [ -e /etc/redhat-release ] ; then
which will (normally) never be true on Debian. So something funky
is going on here. 

Please also see the other thing spotted by lintian which should really
also be fixed.


Regards,
Andreas Henriksson
diff -u dtc-xen-0.5.17/debian/changelog dtc-xen-0.5.17/debian/changelog
--- dtc-xen-0.5.17/debian/changelog
+++ dtc-xen-0.5.17/debian/changelog
@@ -1,3 +1,16 @@
+dtc-xen (0.5.17-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Andreas Henriksson ]
+  * Add e2fsprogs dependency (Closes: #887262)
+
+  [ Jeroen Schot ]
+  * updated Dutch translation of the dtc-xen debconf templates
+(Closes: #659704)
+
+ -- Andreas Henriksson   Tue, 13 Feb 2018 19:39:02 +0100
+
 dtc-xen (0.5.17-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u dtc-xen-0.5.17/debian/control dtc-xen-0.5.17/debian/control
--- dtc-xen-0.5.17/debian/control
+++ dtc-xen-0.5.17/debian/control
@@ -10,7 +10,7 @@
 
 Package: dtc-xen
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}, apache2-utils, debconf, rrdtool, 
python-soappy, python-crypto, python-sqlite, openssh-server, m2crypto, 
debootstrap, openssl, sudo, adduser, sysstat, lsb-base, yum, net-tools, lvm2, 
ipcalc, makedev
+Depends: ${misc:Depends}, ${python:Depends}, apache2-utils, debconf, rrdtool, 
python-soappy, python-crypto, python-sqlite, openssh-server, m2crypto, 
debootstrap, openssl, sudo, adduser, sysstat, lsb-base, yum, net-tools, lvm2, 
e2fsprogs, ipcalc, makedev
 Recommends: dtc-xen-firewall, sysfsutils
 Suggests: xen-utils-common
 Description: SOAP daemon and scripts to allow control panel management for Xen 
VMs
diff -u dtc-xen-0.5.17/debian/po/nl.po dtc-xen-0.5.17/debian/po/nl.po
--- dtc-xen-0.5.17/debian/po/nl.po
+++ dtc-xen-0.5.17/debian/po/nl.po
@@ -1,21 +1,21 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
-# This file is distributed under the same license as the PACKAGE package.
-# FIRST AUTHOR , YEAR.
+# Dutch translation of dtc-xen debconf templates.
+# Copyright (C) 2008-2012 THE PACKAGE'S COPYRIGHT HOLDER
+# This file is distributed under the same license as the dtc-xen package.
+# Bart Cornelis , 2008.
+# Jeroen Schot , 2012.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: dtc-xen\n"
+"Project-Id-Version: dtc-xen 0.5.15-1\n"
 "Report-Msgid-Bugs-To: dtc-...@packages.debian.org\n"
 "POT-Creation-Date: 2010-09-29 14:06+\n"
-"PO-Revision-Date: 2008-02-25 19:57+0100\n"
-"Last-Translator: Bart Cornelis \n"
-"Language-Team: debian-l10n-dutch \n"
-"Language: \n"
+"PO-Revision-Date: 2012-02-13 12:20+0100\n"
+"Last-Translator: Jeroen Schot \n"
+"Language-Team: Debian l10n Dutch \n"
+"Language: nl\n"
 "MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Poedit-Language: Dutch\n"
 
 #. Type: string
 #. Description
@@ -26,16 +26,16 @@
 #. Type: string
 #. Description
 #: ../dtc-xen.templates:1001
-#, fuzzy
 msgid ""
 "Dtc-xen will start it's Python based SOAP server to listen for incoming "
 "requests over a TCP socket. A remote application (like the dtc web hosting "
 "control panel) can then connect to it in order to start, stop, create and "
 "destroy a VPS."
 msgstr ""
-"Dtc-xen bindt zich aan een SOAP-Pythonserver (waaraan een dtc-paneel "
-"verbonden kan worden waarmee u een een VPS kunt starten, stoppen, aanmaken, "
-"of vernietigen)."
+"Dtc-xen zal zijn SOAP-Pythonserver opstarten om te luisteren naar "
+"binnenkomende verzoeken op een TCP-socket. Een andere applicatie (zoals het "
+"dtc-webhosting-controlepaneel) kan dan verbinding maken om een VPS te "
+"starten, stoppen, aanmaken of vernietigen."
 
 #. Type: string
 #. Description
@@ -163,8 +163,8 @@
 "Please enter the kernel version number as it appears with the 'uname -a' "
 "command."
 msgstr ""
-"Wat is het kernel-versienummer (zoals dit teruggegeven wordt in de uitvoer "
-"van het commando 'uname -a')?"
+"Wat is het kernel-versienummer zoals dit teruggegeven wordt in de uitvoer "
+"van het commando 'uname -a'?"
 
 #. Type: string
 #. Description
@@ -178,11 +178,13 @@
 "(voorbeeld: vmlinuz-2.6.16.27-xenU) en de overeenkomstige modules dienen "

Bug#889526: [Pkg-freeipa-devel] Bug#889526: Bug#889526: pki-server: Dogtag stopped starting after libnss3 upgrade to 2:3.35-2

[Timo Aaltonen]

Michal Kašpar kirjoitti 13.02.2018 klo 08:38:
> Hallo.
> Thank you for the explanation.
> 
> On 02/05/2018 11:18 AM, Timo Aaltonen wrote:
>> nss 3.35 apparently changed the default DB format to SQL..
>> certmonger, dogtag, mod_nss and freeipa all need changes to
>> support/migrate to that, but that's not upstream yet.
>>
> 
> After last update of pki-server (to 10.5.5-1), the problem with jss
> appears even with older verison of nss. Is it connected with this
> problem or something different?

Huh, shouldn't be.. The Debian CI shows that at least new PKI instances
are set up just fine. IPA server setup is busted though, but is
unrelated to this bug.


-- 
t

Bug#876459: needrestart: Non-interactive mode not being detected properly

[Dominik George]

Control: severity -1 serious
Control: tags -1 + fixed-in-experimental stretch

Hi,

> the problem described in the archived bug #803249 still exists in
> 2.11-3 (Debian 9.1). When needrestart is run without a tty AND with
> DEBIAN_FRONTEND=noninteractive, it still tries to work interactively
> rather than fall back to "list only" mode. In some cases it causes
> unwanted restarts. The easiest way to reproduce it is to run
> needrestart from cron, redirecting the output to a file.

I regularly see this bug cause important PostgreSQL databases to be
restarted on Debian stable.

Can you please make sure to provide an update for the next Debian point
release? If you need help doing so, feel free to say that.

-nik


signature.asc
Description: PGP signature

Bug#890346: RFS: luakit/2017.08.10 [ITA]

[Grégory DAVID]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

 * Package name: luakit
   Version : 2017.08.10
   Upstream Author : Aidan Holm 
 * URL : https://luakit.github.io/
 * License : GPL-3.0+
   Section : web

  It builds those binary packages:

luakit - fast and small web browser extensible by Lua, WebKit2 based

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


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


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


dget -x 
https://mentors.debian.net/debian/pool/main/l/luakit/luakit_2017.08.10.dsc


More information about luakit can be obtained from https://luakit.github.io/.

  Regards,
   Grégory David

--
DAVID Grégory
02.43.82.33.49
groo...@groolot.net
Compositeur de musique électronique
Artiste numérique
Directeur artistique des projets Groolot en vrai et Plébiscite

http://www.plebiscite.it
   (Les Hommes construisent trop de murs et pas assez de ponts)
http://en-vrai.groolot.net
   (Poésie électronique post-industrielle)
http://tchernobyl.groolot.net
   (Installation radioactive)

GPG : 0x4437F8A1

smime.p7s
Description: S/MIME Cryptographic Signature

Bug#890345: Depending on "default-jre-headless" Should be Sufficient

[殷啟聰 | Kai-Chung Yan]

Package: jflex
Version: 1.6.1-2
Severity: wishlist

"jflex" seems to me a commandline program, thus depending on 
"default-jre-headless" should be sufficient. Right now it depends on 
"default-jre" and "pbuilder" always fetches the whole graphical stack while 
building "libsmali-java".



signature.asc
Description: OpenPGP digital signature

Bug#887241: faumachine-data should depend on e2fsprogs explicitly

[Andreas Henriksson]

On Sun, Jan 14, 2018 at 08:04:39PM +0100, Helmut Grohne wrote:
> Package: faumachine-data
[...]
> /usr/share/faumachine/experiments/test-fi-smart-step2/gen_results.sh contains 
> badblocks. According to file it is a POSIX shell script, ASCII text executable
> /usr/share/faumachine/experiments/test-fi-smart-step2/generate.in contains 
> badblocks. According to file it is a ASCII text
> /usr/share/faumachine/experiments/test-fi-smart-step2/summary.txt contains 
> badblocks. According to file it is a ASCII text
[...]

The package description indicate that FAUmachine is a PC emulatior which
does (hardware related) fault injection and can run a test-suite on a
machine installed from an iso image.

Based on this I would assume the badblocks should be available inside
the emulated machines operating system, rather than on the host where
faumachine is installed. Thus a package relationship might not be
suitable here at all.

Would be great to get some feedback on this from the package maintainer
who hopefully understands what's going on much better than me.

Regards,
Andreas Henriksson

Bug#887228: puppet-module-swift should depend on e2fsprogs explicitly

[Andreas Henriksson]

On Sun, Jan 14, 2018 at 08:09:16PM +0100, Helmut Grohne wrote:
> Package: puppet-module-swift
[...]
> /usr/share/puppet/modules.available/swift/manifests/storage/ext4.pp contains 
> mkfs.ext4. According to file it is a ASCII text
[...]

https://sources.debian.org/src/puppet-module-swift/9.4.4-1/manifests/storage/ext4.pp/#L36

The above looks like using the mkfs.ext4 command is a crutial part of
the functionality provided by this file.

I can't find anything else in the source that points to this file
actually being used anywhere.

As a comparison there's also a xfs.pp in the same directory, but the
package does not declare any relationship against xfsprogs.

I have no puppet knowledge so it's very hard for me to tell what
the correct solution is. Judging from the first part above
I'd probably lean towards "better safe then sorry -> add e2fsprogs dep",
but given the xfs comparison I'm torn

Would be great to hear the maintainers view on this!

Regards,
Andreas Henriksson

Bug#889942: ITP: ignition-fuel-tools -- Classes and tools for interacting with Ignition Fuel

[Jose Luis Rivero]

Patch for the robotics blend

diff --git a/tasks/robotics-dev b/tasks/robotics-dev
index e16ee7d..1e91940 100644
--- a/tasks/robotics-dev
+++ b/tasks/robotics-dev
@@ -51,6 +51,8 @@ Depends: libignition-math2-dev, libignition-math4-dev

 Depends: libignition-msgs-dev

+Depends: libignition-fuel-tools-dev
+
 Depends: libkido-dev

 Depends: ros-desktop-full-dev,

On Thu, Feb 8, 2018 at 3:55 PM, Jose Luis Rivero 
wrote:

> Package: wnpp
> Severity: wishlist
> Owner: Jose Luis Rivero 
>
> * Package name: ignition-fuel-tools
>   Version : 1.0.0
>   Upstream Author : Open Robotics
> * URL : https://ignitionrobotics.org/libs/fuel_tools
> * License : Apache 2
>   Programming Lang: C++
>   Description : Classes and tools for interacting with Ignition Fuel
> Servers
>
> Ignition Fuel Tools is composed by a client library and command line
> tools for interacting with Ignition Fuel servers. These servers host and
> manage different 3D robotics models.
>
>

Bug#890344: the patches

[David Rabel]

Attached please find the patches.

Yours
  David

-- 
⚑ libertⒶd ⚑
From a0f705a4279aca573f34c1fba2267d896bae30ec Mon Sep 17 00:00:00 2001
From: David Rabel 
Date: Tue, 13 Feb 2018 18:25:31 +0100
Subject: [PATCH 1/2] Bump debhelper compat version to v11

---
 debian/changelog | 7 +++
 debian/compat| 2 +-
 debian/control   | 2 +-
 3 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 73b0780..d88411e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+vim-addon-manager (0.5.8) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Bum dephelper compat version to v11
+
+ -- David Rabel   Tue, 13 Feb 2018 18:23:25 +0100
+
 vim-addon-manager (0.5.7) unstable; urgency=medium
 
   [ David Rabel ]
diff --git a/debian/compat b/debian/compat
index ec63514..b4de394 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-9
+11
diff --git a/debian/control b/debian/control
index 48bd588..c6c8605 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ Maintainer: Debian Vim Maintainers 
 Uploaders: Antonio Terceiro ,
James McCoy 
 Build-Depends: cucumber,
-   debhelper (>= 9),
+   debhelper (>= 11),
gem2deb,
rake,
rdtool,
-- 
2.16.1

From cf00f5f786d01c503a7d57acf5c2ebd9b7fad059 Mon Sep 17 00:00:00 2001
From: David Rabel 
Date: Tue, 13 Feb 2018 18:32:32 +0100
Subject: [PATCH 2/2] Fix format URI in d/copyright

---
 debian/changelog | 7 ---
 debian/copyright | 2 +-
 2 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index d88411e..e533eb2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,10 @@
-vim-addon-manager (0.5.8) UNRELEASED; urgency=medium
+vim-addon-manager (0.5.9) UNRELEASED; urgency=medium
 
   * Team upload.
-  * Bum dephelper compat version to v11
+  * Bump dephelper compat version to v11
+  * Fix format URI in d/copyright
 
- -- David Rabel   Tue, 13 Feb 2018 18:23:25 +0100
+ -- David Rabel   Tue, 13 Feb 2018 18:31:56 +0100
 
 vim-addon-manager (0.5.7) unstable; urgency=medium
 
diff --git a/debian/copyright b/debian/copyright
index 5542c6e..bb943c1 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,4 +1,4 @@
-Format: http://dep.debian.net/deps/dep5/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Source: http://git.debian.org/?p=pkg-vim/vim-addon-manager.git
 
 Files: *
-- 
2.16.1



signature.asc
Description: OpenPGP digital signature

Bug#887218: mock should depend on e2fsprogs explicitly

[Andreas Henriksson]

On Sun, Jan 14, 2018 at 08:08:04PM +0100, Helmut Grohne wrote:
> Package: mock
[...]
> /usr/lib/python3/dist-packages/mockbuild/util.py contains chattr. According 
> to file it is a C++ source, ASCII text
[...]

https://sources.debian.org/src/mock/1.3.2-2/py/mockbuild/util.py/#L167

Interestingly the chattr system invokation seems to be used in
an exception handler. There seems to be many other ways that may
be used to deal with this. The overall function seems to be a helper
to remove a directory tree.

If chattr is not available this should not have a greater impact
than the rmtree function simply not being able to do 'chattr -R -i ...'
to try to get a file removed. Other methods should still be tried etc.

It does thus not seem vital to have a e2fsprogs dependency.

I have no idea how important the util.py file and the rmtree
functionality is to mock, which might turn the expectation even lower.

As it looks to me mock should at most Recommend e2fsprogs.

Would be great to hear maintainers opinion about if this bug report
should simply be closed without any action or if a Recommends sounds
appropriate.

Regards,
Andreas Henriksson

Bug#890344: vim-addon-manager: Make the package lintian-clean

[David Rabel]

Package: vim-addon-manager
Severity: wishlist

Dear Maintainer,

I include a patch to get rid of two lintian warnings.

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

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

Versions of packages vim-addon-manager depends on:
ii  ruby1:2.5~1
ii  vim-common  2:8.0.1453-1

Versions of packages vim-addon-manager recommends:
ii  vim  2:8.0.1453-1

vim-addon-manager suggests no packages.

Bug#890343: systemd: Debian could use the fq_codel network queuing algorithm by default

[Laurent Bonnaud]

On 2/13/18 6:29 PM, Felipe Sateler wrote:

> Changelog has this by Marco d'Itri:
> 
>>  * Do not install sysctl.d/50-default.conf because the systemd package
>>should not change kernel policies, at least until it will become
>>the only supported init system.

Thanks for pointing this out!  I did not find it with "grep codel".

> And it makes sense: why would some users get this but others don't?

Indeed.  I will therefore reassign this bug to the kernel...

Thanks again,

-- 
Laurent.

Bug#887216: rear should depend on e2fsprogs explicitly

[Andreas Henriksson]

On Sun, Jan 14, 2018 at 08:10:35PM +0100, Helmut Grohne wrote:
> Package: rear
[...]
> /usr/share/rear/conf/GNU/Linux.conf contains e2fsck, fsck.ext2, fsck.ext3, 
> fsck.ext4, mke2fs, mkfs.ext2, mkfs.ext3, mkfs.ext4 and tune2fs. According to 
> file it is a ASCII text, with very long lines

The commands are listed in the PROGS variable, which also lists commands
like ifconfig, etc. and their respective package is not listed in any
relationship specified in the package. I'm thus assuming there's
no need to explicitly list e2fsprogs either for this occurance.


> /usr/share/rear/conf/examples/SLE12-SP1-btrfs-example.conf contains chattr 
> and lsattr. According to file it is a ASCII text
> /usr/share/rear/conf/examples/SLE12-SP2-btrfs-example.conf contains chattr 
> and lsattr. According to file it is a ASCII text, with very long lines

Example files (for Suse?) are likely not important to consider.

> /usr/share/rear/format/USB/default/300_format_usb_disk.sh contains tune2fs. 
> According to file it is a ASCII text
> /usr/share/rear/format/USB/default/350_label_usb_disk.sh contains e2label. 
> According to file it is a ASCII text

The above two executes the command and calls the Error function if
failing.

> /usr/share/rear/layout/prepare/GNU/Linux/130_include_filesystem_code.sh 
> contains tune2fs. According to file it is a ASCII text

The command is both used directly and written to a generate script.

> /usr/share/rear/layout/prepare/GNU/Linux/130_include_mount_subvolumes_code.sh 
> contains chattr. According to file it is a ASCII text

The command is written to a generated script.

> /usr/share/rear/layout/save/GNU/Linux/230_filesystem_layout.sh contains 
> chattr, e2label, lsattr and tune2fs. According to file it is a ASCII text

Commands are executed directly and there doesn't seem to be any real
fault handling. The commands seems to be expected to be in place
and work.

> /usr/share/rear/skel/default/etc/fstab contains debugfs. According to file it 
> is a ASCII text
[...]

This mostly seem to be an example of mounting debugfs filesystem. Not
using the debugfs command.

My conclusion is based on the above that e2fsprogs should indeed
be a dependency.

Would be great to hear maintainers view on this!

Regards,
Andreas Henriksson

Bug#890343: systemd: Debian could use the fq_codel network queuing algorithm by default

[Felipe Sateler]

On Tue, Feb 13, 2018 at 1:58 PM, Laurent Bonnaud  wrote:
>
> Package: systemd
> Version: 237-2
> Severity: normal
>
>
> Dear Maintainer,
>
> by default Debian uses the pfifo_fast network queuing algorithm:
>
> # tc -s qdisc show
> [...]
> qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap  1 2 2 2 1 2 0 0 1 
> 1 1 1 1 1 1 1
>  Sent 413728102 bytes 475015 pkt (dropped 0, overlimits 0 requeues 785)
>  backlog 0b 0p requeues 785
>
> The systemd source package contains this file:
>
>   ./systemd-237/sysctl.d/50-default.conf:net.core.default_qdisc = fq_codel
>
> whose purpose is to set the default queuing algorithm to fq_codel.  According 
> to the NEWS file, this is a better alternative:
>
> * The default sysctl.d/ snippets will now set:
>
> net.core.default_qdisc = fq_codel
>
>   This selects Fair Queuing Controlled Delay as the default
>   queuing discipline for network interfaces. fq_codel helps
>   fight the network bufferbloat problem. It is believed to be
>   a good default with no tuning required for most workloads.
>   Downstream distributions may override this choice. On 10Gbit
>   servers that do not do forwarding, "fq" may perform better.
>   Systems without a good clocksource should use "pfifo_fast".
>
> However the 50-default.conf file is not in the Debian binary package.
> Is this intentional or an omission?
> Could it be possible to enable fq_codel by default?
>

Changelog has this by Marco d'Itri:

>  * Do not install sysctl.d/50-default.conf because the systemd package
>should not change kernel policies, at least until it will become
>the only supported init system.

And it makes sense: why would some users get this but others don't?

-- 

Saludos,
Felipe Sateler

Bug#798258: still an issue in stretch

[Andreas B. Mundt]

Hi,

I ran into the same issue yesterday on stretch.  On a new server
installation (no desktop) the package 'time' providing '/usr/bin/time'
is not installed by default.  Instead the shell keyword 'time' results
in an empty string in "time_bin=`which time`".

A dependency on the package 'time' providing '/usr/bin/time' should
solve the issue (and installtion of 'time' fixed the issue for me.)

Thanks and best regards,

   Andi

Bug#890343: systemd: Debian could use the fq_codel network queuing algorithm by default

[Laurent Bonnaud]

Package: systemd 
Version: 237-2 
Severity: normal


Dear Maintainer,

by default Debian uses the pfifo_fast network queuing algorithm:

# tc -s qdisc show
[...]
qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap  1 2 2 2 1 2 0 0 1 1 
1 1 1 1 1 1
 Sent 413728102 bytes 475015 pkt (dropped 0, overlimits 0 requeues 785)
 backlog 0b 0p requeues 785

The systemd source package contains this file:

  ./systemd-237/sysctl.d/50-default.conf:net.core.default_qdisc = fq_codel

whose purpose is to set the default queuing algorithm to fq_codel.  According 
to the NEWS file, this is a better alternative:

* The default sysctl.d/ snippets will now set:

net.core.default_qdisc = fq_codel

  This selects Fair Queuing Controlled Delay as the default
  queuing discipline for network interfaces. fq_codel helps
  fight the network bufferbloat problem. It is believed to be
  a good default with no tuning required for most workloads.
  Downstream distributions may override this choice. On 10Gbit
  servers that do not do forwarding, "fq" may perform better.
  Systems without a good clocksource should use "pfifo_fast".

However the 50-default.conf file is not in the Debian binary package.
Is this intentional or an omission?
Could it be possible to enable fq_codel by default?


-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.117
ii  libacl1  2.2.52-3+b1
ii  libapparmor1 2.12-2
ii  libaudit11:2.8.2-1
ii  libblkid12.31.1-0.1
ii  libc62.27-0experimental0
ii  libcap2  1:2.25-1.2
ii  libcryptsetup12  2:2.0.1-1
ii  libgcrypt20  1.8.2-1
ii  libgpg-error01.27-6
ii  libidn11 1.33-2.1
ii  libip4tc01.6.2-1
ii  libkmod2 25-1
ii  liblz4-1 0.0~r131-2+b1
ii  liblzma5 5.2.2-1.3
ii  libmount12.31.1-0.1
ii  libpam0g 1.1.8-3.7
ii  libseccomp2  2.3.1-2.1
ii  libselinux1  2.7-2+b1
ii  libsystemd0  237-2
ii  mount2.31.1-0.1
ii  procps   2:3.3.12-4
ii  util-linux   2.31.1-0.1

Versions of packages systemd recommends:
ii  dbus1.13.0-1
ii  libpam-systemd  237-2

Versions of packages systemd suggests:
ii  policykit-10.113-6
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 237-2

-- 
Laurent.

Bug#887952: Pending fixes for bugs in the golang-github-jacobsa-crypto package

[pkg-go-maintainers]

tag 887952 + pending
thanks

Some bugs in the golang-github-jacobsa-crypto package are closed in
revision 100f3aab420298fe40fa4397384e3bcda41725d8 in branch 'debian'
by Felix Lechner

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-jacobsa-crypto.git/commit/?id=100f3aa

Commit message:

Added changelog entry for revision 9
Fixed pointer size detection in autopkgtest
Marked package Arch:all (Closes: #887952)
Removed unused lintian override
Marked changelog for release

Bug#762180: flex FTCBFS again

[Helmut Grohne]

Control: reopen -1
Control: found -1 2.6.4-1

The patch in this bug report was dropped in the 2.6.4-1 upload and now
the failure mode is back. The patch still applies somewhat with some
rebasing and flex still Build-Depends: flex  for it.

Also can you please just stop using help2man? The manual page is
useless. Having a static page telling to use flex --help and the info
documentation would be much better in addition to solving this problem.

Helmut

Bug#890224: udftools: Cannot be upgraded inside a chroot due to udevadm call in postinst

[Chris Lamb]

tags 890224 + pending
thanks

Fixed in Git, pending upload:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=213777e48ba1ee4f1945bdb9eebefc74458df472

Patches welcome for any possible improvements to the long description.


Best wishes,

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

Bug#890342: fonts-open-sans: missing opentype support for fonts-open-sans

[shirish शिरीष]

Package: fonts-open-sans
Version: 1.11-1
Severity: normal

Dear Maintainer,

telegram-desktop complains about opentype-support from
fonts-open-sans. Could you
please add that support.

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

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

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8