date:20180201

Source: magicrescue
Version: 1.1.9-4
Severity: serious
Tags: buster sid

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

...
Checking for ndbm.h... no
...

Bug#889042: lintian: Do not use dot as a separator in build profile names

2018-02-01 Thread Mattia Rizzolo

On Thu, Feb 01, 2018 at 06:21:00PM +, Niels Thykier wrote:
> Regarding the proposal: Lintian is not the one deciding the namespace
> rules for build-profiles.  We only emit tags based on the existing
> guidelines/namespace rules (https://wiki.debian.org/BuildProfileSpec).
>   I have CC'ed Helmut as he is more involved in the build-profiles work.

That's why I believe this bug should be closed as wontfix, until a clear
policy is set upon.  For example until something good comes out of
policy's bug #757760.
Or at least until https://wiki.debian.org/BuildProfileSpec is amended
and somebody from the relevant group of people (Helmut, Josch, Guillem
comes to my mind) ACKs it.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

signature.asc
Description: PGP signature

Bug#871142: Pending fixes for bugs in the commons-httpclient package

2018-02-01 Thread pkg-java-maintainers

tag 871142 + pending
thanks

Some bugs in the commons-httpclient package are closed in revision
80c2869b6f62682a120f7c48f5fe3344c20ac620 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/commons-httpclient.git/commit/?id=80c2869

Commit message:

Fix Manifest file and add missing OSGi metadata.

Closes: #871142

Bug#889102: [lintian] Please detect source missing .wasm file

2018-02-01 Thread Bastien ROUCARIÈS

Package: lintian
Version: 2.5.72
Severity: normal

wasm are a new javascript to rust stuff.

But source is still missing. See for instance node-source-map package under 
lib/*.wasm

File give:
mappings.wasm: WebAssembly (wasm) binary module version 0x1 (MVP)

Will take it


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

Bug#642458: libfarstream-0.2-5 continues with this

2018-02-01 Thread Elrond

reassign 642458 libfarstream-0.2-5 0.2.8-2
thanks

Bug#889080: dietlibc FTCBFS: dietlibc is difficult

2018-02-01 Thread Helmut Grohne

Source: dietlibc
Version: 0.34~cvs20160606-7
User: helm...@debian.org
Usertags: rebootstrap

dietlibc fails to cross build from source. The ultimate failure arises
when it tries to execute diet for the host architecture.

So I looked and what I found was very confusing. There are lots of
problems. Let me start by quoting the dietlibc FAQ[1]:

| Q: Do you have cross compiling support?
| A: Yes.  Just type something like "make ARCH=arm CROSS=arm-linux- all".
|For arm, alpha, mips, ppc, sparc and i386, shortcuts exist.  You can
|also use "make arm", for example.  You still use the same "diet"
|program as for normal compilation, but you can then say
|
|  $ diet sparc-linux-gcc -pipe -g -o t t.c
|
|Programs using autoconf can be configured like this:
|
|  $ CC="diet sparc-linux-gcc" ./configure --disable-nls

Unfortunately, the packaging gets this completely wrong. The FAQ says
that you should set ARCH, but the packaging sets MYARCH. In GNU
terminology, ARCH is the host architecture and MYARCH is the build
architecture. Thus the packaging confuses build and host here.

Next up, it doesn't pass CROSS. The value should be
"${DEB_HOST_GNU_TYPE}-".

The upstream Makefile expects to be in control of the CC variable.
Unfortunately, most other Makefiles expect not to be in control, so
dh_auto_build passes CC as a command line variable now. This renders
upstream statements such as

CC+=-D__dietlibc__

ineffective (and it should be using CFLAGS anyway). I'm afraid, we
cannot use dh_auto_build here without expecting breakage.

Then the build wants to run "bin-${MYARCH}/diet". But it doesn't build
that. For cross compiling, one needs another build pass where ARCH and
CROSS are not set.

Finally, when using dietlibc, one wants the diet program to come from
the build architecture and the library for the host architecture. The
packaging however stuffs both into the same binary package. The typical
fix is to split dietlibc-dev into another package dietlibc-dev-bin. Then
move the diet program there and move it into an architecture-independent
path. Mark dietlibc-dev-bin Multi-Arch: foreign and have dietlibc-dev
depend on it. You can turn the original architecture-dependent paths
into symlinks for backwards-compatibility.

I tried implementing what I sketched here, but it turned out I was
producing more and more stranger and stranger errors (presumably,
because I don't understand the packaging well enough). Thus I only write
down what I know and hope that you can fix at least some aspects. I'm
happy to help.

Unfortunately, dietlibc suddenly became part of the bootstrap problem
when gdbm started Build-Depending on it.

Helmut

[1] https://www.fefe.de/dietlibc/FAQ.txt

Bug#889083: RFA: python-applicationinsights -- Azure Application Insights API for Python 2.x

Package: wnpp
Severity: normal

I request an adopter for the python-applicationinsights package.

The package description is:
 This package provides an API for Azure Application Insights. Application
 Insights is a service that allows developers to keep their application
 available, performing and succeeding. This Python module will allow you to send
 telemetry of various kinds (event, trace, exception, etc.) to the Application
 Insights service where they can be visualized in the Azure Portal.

I no longer have the time to maintain this package, and I also no longer
have access to Azure via an MSDN subscription.

Bug#889081: RM: azure-cli -- ROM; no time to maintain, currently useless package

Package: ftp.debian.org
Severity: normal

Hi,

I do not have the time to maintain this in a useful way, others I have
asked were not interested.

I no longer even have an MSDN account to try this stuff out on Azure.

Thanks,
Iain.

Bug#889082: RFA: python-adal -- Azure Active Directory Authentication Library for Python 2.x

Package: wnpp
Severity: normal

I request an adopter for the python-adal package.

The package description is:
 The ADAL for Python library makes it easy for Python applications to
 authenticate to AAD in order to access AAD protected web resources.

I no longer have the time to maintain this package, and I also no longer
have access to Azure via an MSDN subscription.

Bug#889084: RFA: python-azure -- Microsoft Azure SDK for Python 2.x

Package: wnpp
Severity: normal

I request an adopter for the python-azure package.

The package description is:
 The Azure SDK provides a set of Python packages that make it easy to access
 the Microsoft Azure components such as ServiceManagement, Storage, and
 ServiceBug.

I no longer have the time to maintain this package, and I also no longer
have access to Azure via an MSDN subscription.

Bug#889002: Simple reboot reminder

2018-02-01 Thread Ben Hutchings

Control: reassign -1 needrestart

On Thu, 2018-02-01 at 17:29 +1300, martin f krafft wrote:
> Package: linux-base
> Version: 4.5
> Severity: wishlist
> 
> We use the following line from cron to remind us to reboot
> a machine, if the initrd for the currently running kernel has been
> updated:
> 
>   test /proc -nt /boot/initrd.img-$(uname -r) || echo reboot required
> 
> Would you be open to the idea to provide such functionality from
> linux-base?
> 
> I'd be happy to extend it to make it work for systems without
> initrd, as well as in the case of kernel version upgrades
> (configurable), but I'd want to gauge first if this is the right
> place for such a script.
> 
> If you don't think linux-base is the place for this, please
> reassign.

There are several packages that already check whether the running
kernel (and userland processes) match the installed versions, so it
doesn't make sense to me that linux-base would implement just this
check.

Reassigning this to needrestart as that's the one I'm familiar with and
it doesn't appear to do this.

Ben.

-- 
Ben Hutchings
All extremists should be taken out and shot.



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

Bug#888962: apt-cacher: apt config suggestion is incorrect

2018-02-01 Thread Nick

A correction,

> Viewing the /report page and copying its suggested apt config.

I was actually viewing '/reports' (by mistake instead of '/report'),
which appears to serve up the index page '/' where the suggested
config appears.
-- 
Nick

Bug#889098: enforce fs.protected_hardlinks in sysctl.d by default

2018-02-01 Thread Antoine Beaupré

Control: retitle 889098 enforce fs.protected_hardlinks in sysctl.d by default

Package: procps
Version: 2:3.3.12-3
Severity: normal
Tags: security

Following the disclosure of CVE-2017-18078, there was an elaborate
discussion on the #debian-devel and #debian-security IRC channels
regarding the scope of the vulnerability. It was then realized that
the impact of this was broader than just systemd: any time a command
like `chown -R` is ran over an untrusted directory, by root, the same
problem occurs.

This is of course mitigated by the fs.protected_hardlinks kernel
configuration, which is enforced through a patch on all the official
Debian kernels distributed by Debian, including in wheezy. See for
example:

https://sources.debian.org/src/linux/3.16.7-ckt20-1+deb8u3/debian/patches/debian/fs-enable-link-security-restrictions-by-default.patch/
https://sources.debian.org/src/linux/4.14.13-1/debian/patches/debian/fs-enable-link-security-restrictions-by-default.patch/

There are, however, people *not* running Debian-built kernels, and
sometimes for good reasons. This is a configuration that we should
still support.

Therefore, it seems to me we should enable this more broadly, for
example in /etc/sysctl.d/protected-hardlinks.conf. Configuring this in
user space is actually what is recommended by Linus Torvalds and the
upstream Linux kernel:

https://github.com/torvalds/linux/commit/561ec64ae67ef25cac8d72bb9c4bfc955edfd415

systemd ships this configuration as well, but this was deliberately
removed from Debian's systemd configuration:

https://salsa.debian.org/systemd-team/systemd/commit/3e1bfe0d84545557d268c1293fff0d5f3db3b5c7

I agree with the above perspective: systemd is not sufficient to
resolve that issue. We still have other init systems and we shouldn't
fix this in systemd, but in a broader package. This is why I am
proposing to fix this in procps, which ultimately owns /etc/sysctl.d/
(and /etc/sysctl.conf).

This is not a strong position: if people think this belongs in systemd
more than procps, or there is some more relevant place this can be
done *by default*, let's do it there and not quibble over that
peculiar bikeshed. :)

I would suggest adding the following configuration:

# Enable hard link protection
fs.protected_hardlinks = 1

Note that the original systemd config also enables softlink
protection:

https://salsa.debian.org/systemd-team/systemd/blob/master/sysctl.d/50-default.conf

I'm not sure if that's also relevant here so I'd keep this to
hardlinks for now to avoid unnecessary debate.

Incidentally, I wonder if we should remove the patch we have on the
Debian kernels to change the defaults, and instead rely on the
sysctl. I have added the kernel team in CC to have their input.

Thanks!

PS: sorry for the duplicate email, I had a copy-paste problem with
reportbug and forgot to re-set a subject.

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

Bug#886285: vim-runtime: tex syntax highlighting fails to enter math mode within align environment

2018-02-01 Thread Francesco Poli

On Wed, 31 Jan 2018 20:07:04 -0500 James McCoy wrote:

[...]
> There is no upstream to forward the request to.
> Someone has to volunteer to do the work to support the amsmath package
> and that person would then be the upstream.
> 
> Charles isn't upstream because he's explicitly restricted the scope of
> what syntax/tex.vim is going to cover.  Bram isn't upstream because he
> just aggregates runtime files from their maintainers when they request
> to have them included with Vim.
> 
> That's why there's no action that I can take on this.

OK, now it's much clearer.
Thanks for the explanation and the patience.

Bye!

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpO8FzwLY2P1.pgp
Description: PGP signature

Bug#790196: Please help porting rasmol to latest vte (Was: Bug#790196: rasmol: depends on vte which is deprecated)

2018-02-01 Thread Emilio Pozuelo Monfort

On 15/01/18 09:14, Andreas Tille wrote:
> Hi Jeremy,
> 
> On Sun, Jan 14, 2018 at 11:03:27PM -0500, Jeremy Bicha wrote:
>> I see that you pushed a commit to Build-Depend on libvte-2.91-dev. But
>> vte2.91 is gtk3 only so this bug is also a request to port rasmol to
>> gtk3.
> 
> Would you be able to give any better replacement for the deprecated
> libvte9 which does not require a gtk3 port?  Sorry for my very naive
> attempt but I simply have no idea about GTK porting issues.

There is a GTK+ 2 -> GTK+ 3 porting guide:

https://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html

Maybe that helps.

Cheers,
Emilio

Bug#889079: debian-live: In installed system keyboard almost doesn't work in taskbar if Russian layout is added and Live is used for installing

2018-02-01 Thread Askar Safin

Package: debian-live
Severity: important

THIS BUG FORCED me to reinstall my system!!!

I got Debian Live Stretch KDE using this link:
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/current-live/amd64/iso-hybrid/debian-live-9.3.0-amd64-kde+nonfree.iso
MD5 sum starts so: 11c5365e... I downloaded this image very recently (today is
2018-02-01 using my local time).
I installed it to fresh qemu virtual machine. Language: English, location:
Russian Federation, locale: en_US.UTF-8. Tasksel DID NOT run. It seems d-i did
COPYING of system and
not CREATING new system using debootstrap.
Then I did boot into installed system (Stretch KDE). Then I opened keyboard
layout configuration and added Russian layout. Then I configured "Switching
Policy" to "Application".
Then I opened "Advanced" tab and configured switching layouts using "Right Alt
(while pressed)". Then I did reboot (this virtual machine). Then I opened
application launcher,
clicked "Type to search..." and attempted to type something. But most letters
didn't appear. I. e. most of my keypresses was ignored. Same happens with
everything which comes
from taskbar, for example I cannot type Wi-Fi password in taskbar network
manager widget.
This bug report is sent from this virtual machine.

Also I created another virtual machine. I got Debian Installer Stretch DVD (not
Live!) using this link:
https://mirror.yandex.ru/debian-cd/current/amd64/iso-dvd/debian-9.3.0-amd64-DVD-1.iso
MD5 sum starts so: f49c3d1a... I downloaded this image very recently (today is
2018-02-01 using my local time).
I installed it to fresh qemu virtual machine. Language: English, location:
Russian Federation, locale: en_US.UTF-8. Tasksel DID run. And I tell tasksel
that I want KDE desktop
environment. It seems d-i did CREATING new system using debootstrap and not
COPYING.
Then I did boot into installed system (stretch KDE). Then I configured keyboard
layout the same as in that Live system. Then I did reboot. And then that
keyboard bug didn't
appear, so, it seems that this bug is Live-specific.

Also I installed debian using that live image to my physical computer (laptop
Dell Inspiron 15) and got the bug.

I mark this bug as important, because it makes installed system, well,
"poisoned". And I don't know to fix such installed system, so I see only way to
fix problem: reinstall
the system (using non-Live installer). So, this bug causes your users to
reinstall the system.

I would make the following suggestion on how to fix the bug: I recommend ALWAYS
perform installing using normal debootstrap. I. e. your Live installer should
install system
exactly same way as normal d-i does this. Because today Live installer is not
tested well. And who knows how many bugs it has?

-- 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/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#889085: RFA: python-azure-devtools -- Microsoft Azure Development Tools for Python 2.x

Package: wnpp
Severity: normal

I request an adopter for the python-azure-devtools package.

The package description is:
 This package contains tools to aid in developing Python-based Azure code.
 Currently it includes scenario_tests, a testing framework to handle much of
 the busywork associated with testing code that interacts with Azure.

I no longer have the time to maintain this package, and I also no longer
have access to Azure via an MSDN subscription.

Bug#889094: RFA: ruby-timeliness -- Fast date/time parser gem for Ruby

Package: wnpp
Severity: normal

I request an adopter for the ruby-timeliness package.

The package description is:
 Date/time parser for Ruby with the following features:
 .
  * Extensible with custom formats and tokens.
  * It's pretty fast. Up to 60% faster than Time/Date parse method.
  * Control the parser strictness.
  * Control behaviour of ambiguous date formats (US vs European e.g. mm/dd/yy,
dd/mm/yy).
  * I18n support (for months), if I18n gem loaded.
  * Fewer WTFs than Time/Date parse method.
 .
 Extracted from the validates_timeliness gem, it has been rewritten cleaner and
 much faster. It's most suitable for when you need to control the parsing
 behaviour. It's faster than the Time/Date class parse methods, so it has
 eneral appeal.

I packaged this as a dependency, but the original package is not a
package that I have time to maintain anymore and I have requested
removal. Still, this gem may be of use to others and so I'd like to
request it is adopted.

If it's not adopted after some months, then it should be removed and
hopefully I will remember to file the RM bug.

Bug#840104: Encrypted uploads to the security archive

2018-02-01 Thread Ansgar Burchardt

Philipp Kern writes:
> On 01.02.2018 10:30, Ansgar Burchardt wrote:
[...]
>> There is already a `buildd-uploader` role account on the upload hosts
>> both main and security archive, a `rsync-ssh-wrap` script, and someone
>> also set up authorized_keys.
>> 
>> I'm just not sure if it is already in use for security uploads?  I
>> believe it was used for uploads to the main archive already (not sure if
>> it currently is?).
>
> Indeed, it uses rsync over SSH through dupload. For security it uses
> FTP. Interestingly an rsync-security dupload.conf entry exists, but it
> doesn't seem to be used[1].

Hmm, maybe we should try if it does the right thing?  The wrapper script
should ignore the `chmod` call I mentioned in #876900, so the uploaded
files shouldn't even be readable by other DDs.

Please watch file permissions of the files on the upload host during
upload and after upload (before debianqueued processes them) if you try.

>> Hmm, another issue comes to mind:
>> 
>> If we care about encrypted buildd uploads, the buildds should probably
>> also download from the (private) security-buildd archive over an
>> encrypted connection, ideally with client authentication.  Otherwise
>> people could see the embargoed fixes in the source package.
>
> Well, I thought this was already the case at this point. I suppose it
> shouldn't be too hard to add https:// support at this point given that
> apt supports it natively. But I think client auth should be a weak
> requirement at this point.

If someone can read from the buildd <-> security-master connection, he
probably can also sent packages with the buildd's IP.  So just https://
doesn't bring much IMHO.  (It doesn't hurt either.)

>> Maybe a local proxy that translates http to https requests and which
>> provides a client certificate (so the chroot doesn't need it added)?
>> The proxy could also filter out other network requests we don't want by
>> default.
>
> It's the kind of solution that I'd propose as well, if the preconditions
> were different ones. Unless it's a pretty stock setup that can be run
> with default packages I don't see that happening.

I think squid can do that:

  tls_outgoing_options cert= key=: for client certificate
  url_rewrite_*: for http:// -> https:// rewrite

`url_rewrite_program` would need a simple script doing the rewriting.

Of course that still leaves managing the client certificates themselves.

For limiting network access (for programs respecting *_proxy environment
variables), one would need to know which URLs are okay.  That should
pretty much be the list of mirrors any chroot might end up using.  This
needs to be generated automatically as buildds use different mirrors.

I use squid for limiting network access for GitLab CI runners which
works quite nice.  I haven't used client certificates or URL rewriting
with squid so far.  Maybe I should try if it works as expected.

Ansgar

Bug#888978: developers-reference: 5.6.5 queued logfile

2018-02-01 Thread Thorsten Alteholz




On Thu, 1 Feb 2018, Guillem Jover wrote:

diff --git a/common.ent b/common.ent
index 1bbed6a..561af11 100644
--- a/common.ent
+++ b/common.ent
@@ -48,6 +48,7 @@
 
 
 
+


I think using ssh.upload.debian.org here would be the more correct fix?


Oh, yes, you are right.

  Thorsten

Bug#871142: eclipse: FTBFS: /<>/build.xml:413: Could not find suitable system JAR for org.apache.commons.httpclient_3.1.0.v201012070820.jar. Tried: /usr/share/java/commons-httpclient.jar

2018-02-01 Thread Emmanuel Bourg

Le 01/02/2018 à 23:02, Markus Koschany a écrit :

> This issue was caused by commons-httpclient due to the switch from Ant
> to Maven in version 3.1-13. The OSGi metadata is currently missing in
> the Manifest file. The data that is added by the 05_osgi_metadata patch
> is overridden by Maven later. I fixed this bug by using javahelper's
> jh_manifest tool. Eclipse builds fine from source again.

Good catch! Thank you for fixing this.

Emmanuel

Bug#889101: gcc-6: Allow to not build multilib packages

Source: gcc-6
Version: 6.4.0-12
Severity: wishlist

Please consider in the future supporting the nobiarch build profile if
multilib packages still exist. I have a patch for version 6.3.0-18.


smime.p7s
Description: S/MIME cryptographic signature

Bug#889103: gcc-6: Allow to run only one SSP test suite

Source: gcc-6
Version: 6.4.0-12
Severity: wishlist

Please consider to support a pkg.gcc-6.1ssp-check build profile that
only runs one SSP test suite, since the derivative run may not be
interesting and the test suite takes much time. I have a patch for
version 6.3.0-18.


smime.p7s
Description: S/MIME cryptographic signature

Bug#888972: lintian: false-positive embedded-javascript-library usr/share/xul-ext/*/bootstrap.js please use libjs-twitter-bootstrap

2018-02-01 Thread Chris Lamb

tags 888972 + pending
thanks

Fixed in Git, pending upload:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=5ea4c7ea6231d28b3d4247c3aeda2834ae2b


Regards,

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

Bug#889011: /run/chrony missing - no privileged commands possible

2018-02-01 Thread Vincent Blut

Control: severity -1 important
Control: tags -1 confirmed pending

Hi,

On Thu, Feb 01, 2018 at 09:43:31AM +0100, Christian Ehrhardt wrote:

Package: chrony
Version: 3.2-2

Hi,
I recently took a spike of activity on Chrony in Ubuntu with some
testing and checking older bugs on it. There are Ubuntu only changes
(like custom time servers), but some might qualify to be considered
for Debian as well.
So I wanted to open bugs for each of them to be discussed.
We currently have a merge proposal up for Ubuntu at [1], and I'll link
the fixes that are currently in review for you directly per-topic.

That’s great, thank you.

In case we modify the fixes due tot he review I'll keep you updated.

Description:
With the recent apparmor profile - when enforcing - I happened to find an issue.
From logs:
chronyd[3443]: Could not change ownership of /run/chrony : Operation
not permitted
chronyd[3443]: Could not access /run/chrony : No such file or directory
chronyd[3443]: Disabled command socket /run/chrony/chronyd.sock

After a few wrong assumptions :-) I found that this would be
created/chowned by chrony itself

Indeed, the whole logic can be found in util.c.

, but the apparmor caps do not allow it yet.
With that missing it won't be able to spawn the unix command socket
for privileged commands.

As I told you privately, nice catch as that was quite subtle!
I will release 3.2-3 with this fix included during the weekend
hopefully.

Ubuntu-Bug: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1746444
Fix-in-Review:
https://git.launchpad.net/~paelzer/ubuntu/+source/chrony/commit/?id=9d4873cc7296607a6e3696b5ffda0f2c431a5c80

[1]:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/336844

--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

Cheers,
Vincent

signature.asc
Description: PGP signature

Bug#889074: libreoffice: Libreoffice crashes on saving OOXML: undefined symbol

2018-02-01 Thread Örjan Ekeberg

Updating packages uno-libs3 and ure to version 6.0.0-1 to match the
libreoffice version seems to fix this.  The versioned depend on these
packages from libreoffice-core probably needs updating.

Bug#888271: Acknowledgement (libpanel-applet-dev,libpanel-applet-doc: both ship /usr/share/doc/libpanel-applet-dev/AUTHORS)

This is probably fixed in latest debhelper, #888294

Andreas

Bug#888301: Acknowledgement (appstream-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/appstream/NEWS.gz)

This is probably fixed in latest debhelper, #888294

Andreas

Bug#888526: RFS: dxf2gcode/20170925-5 [ITP] -- converts 2D drawings to G-code for CNC machines

2018-02-01 Thread Sebastian Kuzminsky


Control: tags -1 - moreinfo

--
Sebastian Kuzminsky

Bug#889095: RFA: ruby-haikunator -- Heroku-like random name generator

Package: wnpp
Severity: normal

I request an adopter for the ruby-haikunator package.

The package description is:
 This Ruby gem can generate memorable random names to use in your apps or
 anywhere else that are similar to those produced by the Heroku random name
 generator.

I packaged this as a dependency, but the original package is not a
package that I have time to maintain anymore and I have requested
removal. Still, this gem may be of use to others and so I'd like to
request it is adopted.

If it's not adopted after some months, then it should be removed and
hopefully I will remember to file the RM bug.

Bug#889006: [debhelper-devel] Bug#889006: dh-autoreconf is run before patching

2018-02-01 Thread Mattia Rizzolo

On Thu, Feb 01, 2018 at 07:01:00PM +, Niels Thykier wrote:
> Indeed, from my PoV we would ideally fix this issue in dpatch.  However,
> we need to handle backports as well and that puts quilt back the table
> as well.  I am not quite sure that I want to backport quilt and dpatch
> to provide further debhelper backports.

Can't we instead:
 * ignore this bug
 * have packages move away from dpatch (I believe now lintian even warns
   about quilt packages using it?  at least for 3.0 which is not this
   case but still)
 * don't worry about backports: new dh-autoreconf/debhelper won't be
   pulled automatically, and if a package from sid doesn't build in bpo
   isn't really a problem (this is of course different if a package
   already in bpo already pulling a bpo debhelper/dh-autoreconf would
   fail)

There are only 82 packages with a build-dep on dpatch, and I doubt there
are many that uses the dh addon AND autoreconf AND have a patch that
modifies the configure script.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

signature.asc
Description: PGP signature

Bug#889100: fizmo-sdl2: Segfaults on start-up

2018-02-01 Thread Peter De Wachter

Package: fizmo-sdl2
Version: 0.8.5-2
Severity: serious
Justification: package doesn't work at all

I just installed fizmo-sdl2. When I start it, it shows a black window
and then it segfaults. I tried it with a bunch of different z5 files.
(These crashes don't occur with fizmo-ncurses, that version works.)

Here's a backtrace:

$ gdb -q fizmo-sdl2
Reading symbols from fizmo-sdl2...Reading symbols from 
/usr/lib/debug/.build-id/40/bb3b897ba214fc701762c7b91c8715c1eec2d2.debug...done.
done.
(gdb) run curses.z5 
Starting program: /usr/games/fizmo-sdl2 curses.z5
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffecf6a700 (LWP 18815)]
[New Thread 0x7fffd96d2700 (LWP 18817)]
[New Thread 0x7fffd8cdf700 (LWP 18818)]

Thread 4 "fizmo-sdl2" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd8cdf700 (LWP 18818)]
0x5557b6e1 in tt_get_glyph_size ()
(gdb) bt
#0  0x5557b6e1 in tt_get_glyph_size ()
#1  0x55579e5a in link_interface_to_story ()
#2  0xec7c in fizmo_start ()
#3  0xace4 in interpreter_thread_function 
(UNUSED_ptr=UNUSED_ptr@entry=0x0) at fizmo-sdl2.c:1143
#4  0x77b3518c in SDL_RunThread (data=0x55c72f80) at 
./src/thread/SDL_thread.c:283
#5  0x77b8ba19 in RunThread (data=) at 
./src/thread/pthread/SDL_systhread.c:74
#6  0x771aa51a in start_thread (arg=0x7fffd8cdf700) at 
pthread_create.c:465
#7  0x75fbe3ef in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95



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

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

Versions of packages fizmo-sdl2 depends on:
ii  libc6  2.26-6
ii  libdrilbo-common   0.2.11-2
ii  libfizmo-common0.7.15-2
ii  libfreetype6   2.8.1-1
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libpixelif-common  0.8.4-2
ii  libpng16-161.6.34-1
ii  libsdl2-2.0-0  2.0.7+dfsg1-3
ii  libsndfile11.0.28-4
ii  libx11-6   2:1.6.4-3
ii  libxml22.9.4+dfsg1-6.1
ii  zlib1g 1:1.2.8.dfsg-5

fizmo-sdl2 recommends no packages.

fizmo-sdl2 suggests no packages.

-- no debconf information

Bug#889099: RM: cobbler -- ROM; no time for this package, nobody adopting, RC buggy

2018-02-01 Thread Thomas Goirand

Package: ftp.debian.org
Severity: normal

Hi,

I have delayed this for too long. I have no time and no interest for this
package anymore, and it's bit-rotting in the archive with some RC bugs.

I have opened an RFA for 3 months (see #880416), and nobody is picking-up
the package. Therefore, the interest appears too low to keep the package
in the archive, especially considering its current shape.

So please remove Cobbler from the archive.

Cheers,

Thomas Goirand (zigo)

Bug#889104: gcc-6: Add README.cross-hppa64 to justify gcc-6-hppa64-linux-gnu

Source: gcc-6
Version: 6.4.0-12
Severity: wishlist

Please consider adding a README.cross-hppa64 file that explains why
gcc-6-hppa64-linux-gnu is provided by gcc-6 instead of by
gcc-6-cross-ports. https://bugs.debian.org/800729 may be of interest.


smime.p7s
Description: S/MIME cryptographic signature

Bug#889097: nvidia-libopencl1: Missing NVidia OpenCL platform

On 2018-02-01 22:30, Krzysztof Marczak wrote:
> After lastest update to version nvidia-graphics-drivers 384.111-3 the OpenCL
> platform in no longer available in the system. clinfo command lists only other
> platforms (e.g. Intel).
> Just before this update everything worked properly.
> 
> I have tried to unistall (purge) all opencl-icd packages and install again, 
> but
> it did not help.
> 
> In actual state there is not possible to run any software using OpenCL with
> nvidia proprietary drivers.

Looks like a duplicate of #888952
Running clinfo as root helped there - is some module not loaded?

Which package version combination was working previously?


Andreas

Bug#888526: RFS: dxf2gcode/20170925-5 [ITP] -- converts 2D drawings to G-code for CNC machines

2018-02-01 Thread Sebastian Kuzminsky


On 02/01/2018 11:13 AM, Juhani Numminen wrote:

Control: tags -1 moreinfo

Sebastian Kuzminsky kirjoitti 26.01.2018 klo 20:15:

Dear Mentors/Sponsors,

I am looking for a Sponsor for my package "dxf2gcode":


Here's my short review of the package, but I can't sponsor it.


Thank you very much for this feedback.



I'm afraid the package cannot be built twice in a row (build log attached),
which indicates that the clean target is not functioning as it should.
(The relevant Debian Policy chapter is 4.9.)

One way to make the cleaning adequate is in build_twice.diff.
I added a patch to disable the pylupdate part because it is modifying
the *.ts files which is a bit problematic from our POV. If you go that
route, I suggest asking upstream to provide a way to disable pylupdate,
in order to keep Debian-specific changes to a minimum.


I've applied your patch, with the make_tr change modified to hopefully 
be more palatable to upstream.


Repeated builds succeed now.



Have you forwarded 
0001-install-AppStream-metadata-in-the-correct-directory.patch
upstream? Please also use DEP3 to document it in the patch file.
http://dep.debian.net/deps/dep3/


I added DEP3 tags to the appstream patch and to the modified version of 
you make_tr patch, and submitted them upstream:


https://groups.google.com/forum/#!topic/dxf2gcode-dev/vKUTXa9EgjQ



You have build-depends qt4-linguist-tools, which seems to work, but Qt5
linguist tools are in qttools5-dev-tools as indicated by this search:
https://packages.debian.org/file:lrelease


Oops!  Fixed.


I uploaded a new version of the package that I believe addresses all 
your review comments:


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



When you have resolved these, you can remove the moreinfo tag from the RFS.


Will do!


--
Sebastian Kuzminsky

Bug#889087: python-msrest: please remove me from maintainers

Source: python-msrest
Severity: wishlist

Hi,

I no longer have an MSDN subscription, nor the time to maintain this
package. Please remove me from the maintainers field on the next upload.

Thanks,
Iain.

Bug#889089: zziplib: CVE-2018-6484: Bus error in __zzip_fetch_disk_trailer

2018-02-01 Thread Salvatore Bonaccorso

Source: zziplib
Version: 0.13.62-3
Severity: important
Tags: security upstream

Hi,

the following vulnerability was published for zziplib.

CVE-2018-6484[0]:
| In ZZIPlib 0.13.67, there is a memory alignment error and bus error in
| the __zzip_fetch_disk_trailer function of zzip/zip.c. Remote attackers
| could leverage this vulnerability to cause a denial of service via a
| crafted zip file.

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-2018-6484
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6484

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#889086: python-azure-storage: please remove me from maintainers

Source: python-azure-storage
Severity: wishlist

Hi,

I no longer have an MSDN subscription, nor the time to maintain this
package. Please remove me from the maintainers field on the next upload.

Thanks,
Iain.

Bug#889088: python-msrestazure: please remove me from maintainers

Source: python-msrestazure
Severity: wishlist

Hi,

I no longer have an MSDN subscription, nor the time to maintain this
package. Please remove me from the maintainers field on the next upload.

Thanks,
Iain.

Bug#889092: RM: ruby-ms-rest-azure -- ROM; no time to maintain, useless currently

Package: ftp.debian.org
Severity: normal

Hi,

I've not updated this recently enough for the API to still match up with
the actual Azure API and I do not have the time to maintain this
currently.

Thanks,
Iain.

Bug#889042: lintian: Do not use dot as a separator in build profile names

El dj 01 de 02 de 2018 a les 22:16 +0100, Mattia Rizzolo va escriure:
> Or at least until https://wiki.debian.org/BuildProfileSpec is amended
> and somebody from the relevant group of people (Helmut, Josch, Guillem
> comes to my mind) ACKs it.

 Missatge reenviat 
De: Javier Serrano Polo 
Per a: 889...@bugs.debian.org
Data: Thu, 01 Feb 2018 20:05:19 +0100

We had some words at #debian-bootstrap. Helmut agrees. I will fix this
someday.


smime.p7s
Description: S/MIME cryptographic signature

Bug#871142: eclipse: FTBFS: /<>/build.xml:413: Could not find suitable system JAR for org.apache.commons.httpclient_3.1.0.v201012070820.jar. Tried: /usr/share/java/commons-httpclient.jar

2018-02-01 Thread Markus Koschany

Control: reassign -1 commons-httpclient
Control: retitle -1 Missing OSGi metadata breaks Eclipse
Control: tags -1 pending
Control: affects -1 src:eclipse

On Sun, 6 Aug 2017 17:55:36 -0400 Lucas Nussbaum  wrote:
> Source: eclipse
> Version: 3.8.1-10
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170805 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

[...]

This issue was caused by commons-httpclient due to the switch from Ant
to Maven in version 3.1-13. The OSGi metadata is currently missing in
the Manifest file. The data that is added by the 05_osgi_metadata patch
is overridden by Maven later. I fixed this bug by using javahelper's
jh_manifest tool. Eclipse builds fine from source again.

Markus

signature.asc
Description: OpenPGP digital signature

Bug#889098: (no subject)

2018-02-01 Thread Antoine Beaupre

Package: procps
Version: 2:3.3.12-3
Severity: normal
Tags: security

Following the disclosure of CVE-2017-18078, there was an elaborate
discussion on the #debian-devel and #debian-security IRC channels
regarding the scope of the vulnerability. It was then realized that
the impact of this was broader than just systemd: any time a command
like `chown -R` is ran over an untrusted directory, by root, the same
problem occurs.

This is of course mitigated by the fs.protected_hardlinks kernel
configuration, which is enforced through a patch on all the official
Debian kernels distributed by Debian, including in wheezy. See for
example:


https://sources.debian.org/src/linux/3.16.7-ckt20-1+deb8u3/debian/patches/debian/fs-enable-link-security-restrictions-by-default.patch/

https://sources.debian.org/src/linux/4.14.13-1/debian/patches/debian/fs-enable-link-security-restrictions-by-default.patch/

There are, however, people *not* running Debian-built kernels, and
sometimes for good reasons. This is a configuration that we should
still support.

Therefore, it seems to me we should enable this more broadly, for
example in /etc/sysctl.d/protected-hardlinks.conf. Configuring this in
user space is actually what is recommended by Linus Torvalds and the
upstream Linux kernel:


https://github.com/torvalds/linux/commit/561ec64ae67ef25cac8d72bb9c4bfc955edfd415

systemd ships this configuration as well, but this was deliberately
removed from Debian's systemd configuration:


https://salsa.debian.org/systemd-team/systemd/commit/3e1bfe0d84545557d268c1293fff0d5f3db3b5c7

I agree with the above perspective: systemd is not sufficient to
resolve that issue. We still have other init systems and we shouldn't
fix this in systemd, but in a broader package. This is why I am
proposing to fix this in procps, which ultimately owns /etc/sysctl.d/
(and /etc/sysctl.conf).

This is not a strong position: if people think this belongs in systemd
more than procps, or there is some more relevant place this can be
done *by default*, let's do it there and not quibble over that
peculiar bikeshed. :)

I would suggest adding the following configuration:

# Enable hard link protection
fs.protected_hardlinks = 1

Note that the original systemd config also enables softlink
protection:

https://salsa.debian.org/systemd-team/systemd/blob/master/sysctl.d/50-default.conf

I'm not sure if that's also relevant here so I'd keep this to
hardlinks for now to avoid unnecessary debate.

Incidentally, I wonder if we should remove the patch we have on the
Debian kernels to change the defaults, and instead rely on the
sysctl. I have added the kernel team in CC to have their input.

Thanks!

Bug#885548: winetricks: Don't recommend gksu

2018-02-01 Thread Jens Reyer

control: forwarded -1 https://github.com/Winetricks/winetricks/issues/912

> I won't be able to fix upstream for a few weeks, but I've filled a bug in
> the meantime:
> 
> https://github.com/Winetricks/winetricks/issues/912

There have been a few patches upstream, so I guess we'll have a solution
soon.

Greets
jre

Bug#888556: Acknowledgement (libetsf-io-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libetsf-io-dev/AUTHORS)

This is probably fixed in latest debhelper, #888294

Andreas

Bug#887912: Acknowledgement (python-parted-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/python-parted/HACKING.gz)

This is probably fixed in latest debhelper, #888294

Andreas

Bug#888816: Acknowledgement (libdbus-glib-1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libdbus-glib-1-dev/AUTHORS)

This is probably fixed in latest debhelper, #888294

Andreas

Bug#889091: RM: ruby-ms-rest -- ROM; no time to maintain, useless currently

Package: ftp.debian.org
Severity: normal

Hi,

I've not updated this recently enough for the API to still match up with
the actual Azure API and I do not have the time to maintain this
currently.

Thanks,
Iain.

Bug#889090: RM: ruby-azure-sdk -- ROM; no time to maintain, useless currently

Package: ftp.debian.org
Severity: normal

Hi,

I've not updated this recently enough for the API to still match up with
the actual Azure API and I do not have the time to maintain this
currently.

Thanks,
Iain.

Bug#889093: RM: vagrant-azure -- ROM; no time to maintain, useless currently

Package: ftp.debian.org
Severity: normal

Hi,

I've not updated this recently enough for the API to still match up with
the actual Azure API and I do not have the time to maintain this
currently.

Thanks,
Iain.

Bug#889096: zziplib: CVE-2018-6381: Invalid memory access in zzip_disk_fread

2018-02-01 Thread Salvatore Bonaccorso

Source: zziplib
Version: 0.13.62-3
Severity: important
Tags: security upstream
Forwarded: https://github.com/gdraheim/zziplib/issues/12

Hi,

the following vulnerability was published for zziplib.

CVE-2018-6381[0]:
| In ZZIPlib 0.13.67, there is a segmentation fault caused by invalid
| memory access in the zzip_disk_fread function (zzip/mmapped.c) because
| the size variable is not validated against the amount of file-stored
| data.

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-2018-6381
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6381
[1] https://github.com/gdraheim/zziplib/issues/12

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#871142: eclipse: FTBFS: /<>/build.xml:413: Could not find suitable system JAR for org.apache.commons.httpclient_3.1.0.v201012070820.jar. Tried: /usr/share/java/commons-httpclient.jar

2018-02-01 Thread Markus Koschany



Am 01.02.2018 um 23:29 schrieb Emmanuel Bourg:
> Le 01/02/2018 à 23:02, Markus Koschany a écrit :
> 
>> This issue was caused by commons-httpclient due to the switch from Ant
>> to Maven in version 3.1-13. The OSGi metadata is currently missing in
>> the Manifest file. The data that is added by the 05_osgi_metadata patch
>> is overridden by Maven later. I fixed this bug by using javahelper's
>> jh_manifest tool. Eclipse builds fine from source again.
> 
> Good catch! Thank you for fixing this.
> 
> Emmanuel

No problem. But now starts the real challenge... Let's see if it is
possible to split the package in smaller parts so that we can

a) remove swt-gtk from Debian
b) keep all reverse-dependencies that depend on eclipse-rcp,
eclipse-platform and eclipse-jdt in Debian

Hahaha, and after that squaring the circle should be a piece of cake.



signature.asc
Description: OpenPGP digital signature

Bug#888816: Acknowledgement (libdbus-glib-1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libdbus-glib-1-dev/AUTHORS)

2018-02-01 Thread Simon McVittie

On Fri, 02 Feb 2018 at 00:27:23 +0100, Andreas Beckmann wrote:
> This is probably fixed in latest debhelper, #888294

Thanks, but I think the dbus-glib one was actually my fault: I
bumped debhelper compat to 11, but didn't add Breaks/Replaces for the
documentation having moved around as a result. It seems fixed now, so
unless piuparts is still sad, I'm hoping not to touch dbus-glib again
for a while.

smcv

Bug#889109: konqueror: Almost unusable as web browser

2018-02-01 Thread Francesco

Package: konqueror
Version: 4:17.08.3-2
Severity: important

Dear Maintainer,


   * What led up to the situation?
   Latest updates rendered konqueror almost unusable as a normal web
   browser

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   I started the browser and opened normally web sites; it's slower and
   when inserting data in forms it don't show the input (e.g. open
   google and go for a search, the search bar will remain blank even if
   it has been correctly filled, when focus is lost text is displayed).
   When browsing it uses higher CPU and sometimes freezese and it's
   needed to kill it.

   If needed I can try to debug, just tell me what tools to use.


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

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

Versions of packages konqueror depends on:
ii  dolphin  4:17.08.3-2
ii  install-info 6.5.0.dfsg.1-1
ii  kio  5.37.0-2
ii  libc62.26-4
ii  libkf5archive5   5.37.0-2
ii  libkf5bookmarks5 5.37.0-2
ii  libkf5codecs55.37.0-2
ii  libkf5completion55.37.0-2
ii  libkf5configcore55.37.0-2
ii  libkf5configgui5 5.37.0-2
ii  libkf5configwidgets5 5.37.0-2
ii  libkf5coreaddons55.37.0-3
ii  libkf5dbusaddons55.37.0-2
ii  libkf5i18n5  5.37.0-2
ii  libkf5iconthemes55.37.0-2
ii  libkf5itemviews5 5.37.0-2
ii  libkf5jobwidgets55.37.0-2
ii  libkf5kcmutils5  5.37.0-2
ii  libkf5kdelibs4support5   5.37.0-2
ii  libkf5khtml5 5.37.0-3
ii  libkf5kiocore5   5.37.0-2
ii  libkf5kiofilewidgets55.37.0-2
ii  libkf5kiogui55.37.0-2
ii  libkf5kiowidgets55.37.0-2
ii  libkf5konq6  4:17.08.3-2
ii  libkf5parts5 5.37.0-2
ii  libkf5service-bin5.37.0-2
ii  libkf5service5   5.37.0-2
ii  libkf5sonnetcore55.37.0-2
ii  libkf5sonnetui5  5.37.0-2
ii  libkf5widgetsaddons5 5.37.0-2
ii  libkf5windowsystem5  5.37.0-2
ii  libkf5xmlgui55.37.0-2
ii  libqt5core5a 5.9.2+dfsg-7
ii  libqt5dbus5  5.9.2+dfsg-7
ii  libqt5gui5   5.9.2+dfsg-7
ii  libqt5network5   5.9.2+dfsg-7
ii  libqt5printsupport5  5.9.2+dfsg-7
ii  libqt5webenginewidgets5  5.9.2+dfsg-2
ii  libqt5widgets5   5.9.2+dfsg-7
ii  libqt5x11extras5 5.9.2-1
ii  libqt5xml5   5.9.2+dfsg-7
ii  libstdc++6   7.2.0-19

Versions of packages konqueror recommends:
ii  kfind  4:17.08.3-2

Versions of packages konqueror suggests:
ii  konq-plugins  4:17.08.3-2

-- no debconf information

Bug#889098: enforce fs.protected_hardlinks in sysctl.d by default

2018-02-01 Thread Ben Hutchings

On Thu, 2018-02-01 at 17:05 -0500, Antoine Beaupre wrote:
[...]
> Note that the original systemd config also enables softlink
> protection:
> 
> https://salsa.debian.org/systemd-team/systemd/blob/master/sysctl.d/50-default.conf
>
> I'm not sure if that's also relevant here so I'd keep this to
> hardlinks for now to avoid unnecessary debate.
> 
> Incidentally, I wonder if we should remove the patch we have on the
> Debian kernels to change the defaults, and instead rely on the
> sysctl. I have added the kernel team in CC to have their input.

I would rather have the secure default specified in both places.  If we
unpatch the kernel then there's a risk of re-enabling link attacks in a
partial upgrade or backporting.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug



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

Bug#883872: (no subject)

2018-02-01 Thread Michael Lustfield

Severity: 883872 serious

This /is/ a "serious" severity bug. The format be optional, but accurately
representing the licenses and copyright holder information is not. This file,
without question, is not an accurate representation.

-- 
Michael Lustfield

Bug#858709: live-config: Resolution changes and lost keystrokes, every 15 seconds

2018-02-01 Thread Robert Munyer

Control: reassign -1 live-config 5.20170112
Control: retitle -1 live-config: Resolution changes and lost keystrokes, every 
15 seconds

Bug#889108: libgtk2-appindicator-perl: Remove libgtk2-appindicator-perl during the Buster cycle

Package: libgtk2-appindicator-perl
Severity: important
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal
X-Debbugs-CC: a...@debian.org

libgtk2-appindicator-perl has no reverse-depends and its only
reverse-recommends is shutter. Although shutter is a popular package,
it is unmaintained and seems unlikely to be included in the Buster
release without major work to port it to gtk3.

See https://bugs.debian.org/870418

I don't think it makes sense to include a deprecated unmaintained
library in Debian with no reverse dependencies. The replacement is
GObject Introspection and either gir1.2-appindicator3-0.1 or
gir1.2-ayatanaappindicator3-0.1. That requires developers to use gtk3
instead of gtk2.

Thanks,
Jeremy Bicha

Bug#741097: octave: nox package of Octave

2018-02-01 Thread Mike Miller

On Thu, Feb 01, 2018 at 12:13:40 -0800, Mike Miller wrote:
> If this bug is still of interest, I think a useful first step would be
> for someone to adapt the octave source package and add the appropriate
> --without-X options. Once there are proof of concept binary packages
> built without any graphical dependencies, then a useful disk usage
> comparison can be done.

Here is an example of what I suggest interested parties can do quite
easily. Modify the source package as in the attached example patch. This
is not an example of a full solution, just a quick and dirty hack to
build octave with no graphical dependencies. Note that this will also be
a slightly crippled octave without any imread or imwrite capability.

With the resulting packages, I can compare the storage requirements in a
clean minbase installation:

# apt install --no-install-recommends octave
…
0 upgraded, 181 newly installed, 0 to remove and 0 not upgraded.
Need to get 88.3 MB of archives.
After this operation, 450 MB of additional disk space will be used.

versus

# apt install --no-install-recommends ./octave_4.2.1-6_amd64.deb \
  ./liboctave4_4.2.1-6_amd64.deb \
  ./octave-common_4.2.1-6_all.deb
…
0 upgraded, 69 newly installed, 0 to remove and 0 not upgraded.
Need to get 29.9 MB/38.9 MB of archives.
After this operation, 167 MB of additional disk space will be used.

So I have saved about 280 MB in storage by dropping all graphical
dependencies. That's about 5 MB in the octave binaries themselves and
the rest in the dropped dependencies. Octave will not have a GUI, will
not be able to plot anything, and will not be able to read or write
image file formats.

Is 0.25-0.3 GB on the order of the savings you are looking for? Is it
worth not being able to work with image files or plot anything, even
headless plotting?

-- 
mike
diff --git a/debian/control b/debian/control
index a98b3afee08d..fc2daca67cd0 100644
--- a/debian/control
+++ b/debian/control
@@ -22,31 +22,22 @@ Build-Depends: automake,
less,
libarpack2-dev,
libblas-dev,
+   libbz2-dev,
libcurl4-gnutls-dev,
libfftw3-dev,
-   libfltk1.3-dev,
-   libfontconfig1-dev,
-   libgl2ps-dev,
libglpk-dev,
-   libgraphicsmagick++1-dev,
libhdf5-dev,
liblapack-dev,
libncurses5-dev,
-   libosmesa6-dev,
libpcre3-dev,
libqhull-dev,
libqrupdate-dev,
-   libqscintilla2-qt5-dev,
-   libqt5opengl5-dev,
libreadline-dev,
librsvg2-bin,
libsndfile1-dev,
libsuitesparse-dev,
-   libxft-dev,
portaudio19-dev,
pstoedit,
-   qtbase5-dev,
-   qttools5-dev-tools,
texinfo,
texlive-generic-recommended,
texlive-fonts-recommended,
diff --git a/debian/rules b/debian/rules
index 5c3161594258..7c16dbf09efe 100755
--- a/debian/rules
+++ b/debian/rules
@@ -49,7 +49,14 @@ endif
 override_dh_auto_configure:
 	# Enforce generic BLAS (in order to avoid tying the binary to OpenBLAS or ATLAS)
 	# Also pass OpenMP flag (#631831)
-	dh_auto_configure -- --with-blas=blas --enable-openmp $(WITH_JAVA_FLAGS) $(JIT_FLAG) $(HDF5_FLAGS) $(DOC_FLAG)
+	dh_auto_configure -- \
+--without-fltk \
+--without-magick \
+--without-opengl \
+--without-OSMesa \
+--without-qt \
+--without-x \
+--with-blas=blas --enable-openmp $(WITH_JAVA_FLAGS) $(JIT_FLAG) $(HDF5_FLAGS) $(DOC_FLAG)

 # dh_auto_test tries to run "make test", so override it
 override_dh_auto_test:

signature.asc
Description: PGP signature

Bug#889105: chezscheme: Fails to build from source with glibc 2.26

Source: chezscheme
Version: 9.5+dfsg-1
Severity: serious

chezscheme fails to build from source with glibc 2.26.

Specifically, #include  won't work starting with that
version of glibc.

This can be clearly seen in the reproducible builds logs:

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

Thanks,
Jeremy Bicha

Bug#884717: libgl1: consider using a version that is higher than 1.2.0 for the libGL.so.1.0.0 filename

Control: tag -1 fixed-upstream

On 2018-01-25 17:22, Timo Aaltonen wrote:
>> Also give me a notice before uploading such a change s.t. I can adjust
>> glx-diversions accordingly and you can bump the Breaks against the
>> glx-diversions versions not knowing about the new filename.
>>
>> It may be worthwile suggesting such a rename to upstream, too.
> 
> Correction, it should go upstream _first_.

Upstream will bump all the filename versions to prevent accidently
mixing libglvnd and mesa libraries ...

https://github.com/NVIDIA/libglvnd/commit/212861e5e73927ec267244f5fc3040bb9b701c47

Please bump the Breaks against glx-diversions to (<< 0.8.3~) (I just
uploaded 0.8.3 to sid).


Thanks

Bug#228141: Have dh_clean remove temporary CVS files

2018-02-01 Thread Matt Zimmerman

It's no longer of interest to me, so feel free to close it. Thanks for
checking in.

On Jan 31, 2018 11:42, "Niels Thykier"  wrote:

> On Sun, 31 Dec 2017 22:53:00 + Niels Thykier 
> wrote:
> > Control: tags -1 moreinfo
> >
> > On Fri, 16 Jan 2004 15:26:55 -0500 Joey Hess  wrote:
> > > Matt Zimmerman wrote:
> > > > Yes, it does...seems like exactly the same reasons that an editor
> makes
> > > > backup files, and dh_clean deletes those.  But, if you don't like it,
> > > > whatever...
> > >
> > > I'm not unchangably opposed to it; I just don't know what's right.
> > >
> > > --
> > > see shy jo
> >
> > Hi Matt,
> >
> > It seems that 14 years have past on this bug without any reaction from
> > neither you nor Joey.
> >
> > I am pinging you to hear about your opinion on this bug.  If you still
> > think it is relevant and you think it is the proper thing to do, then I
> > am happy to apply the patch.
> >
> >   Disclaimer: I have zero-knowledge of this part of CVS, so I would be
> > trusting your judgement here.
> >
> > Alternatively, if you are no longer interested in this (e.g. because you
> > no longer use CVS), then I think I will take the liberty of closing the
> > bug as "wont do".
> >
> > Thanks,
> > ~Niels
> >
> >
> >
>
> Hi Matt,
>
> A friendly ping on this.
>
> If I have not heard from you (or anyone else with interest in this bug)
> by 2018-02-19, then I will consider this bug obsolete and close it
> without changing the behaviour of dh_clean.
>
> Thanks,
> ~Niels
>

Bug#886120: off to doxygen we go

2018-02-01 Thread Adam Borowski

Control: retitle -1 makes ctpp2 randomly FTBFS, syntax errors, hides problems
Control: tags -1 -moreinfo unreproducible
Control: reassign -1 doxygen
Control: affects 818379 + ctpp2

As I don't see anything obvious in the way ctpp2 calls doxygen + graphviz,
there's no point in having the bug stay here.  The culprit here is doxygen
as it's where the syntax errors come from.

Generating calError: 
/<>/doc/html/a00332_a3c04138a5bfe5d72780bb7e82a18e627_cgraph.dot: 
syntax error in line 67 near '-'
error: Problems running dot: exit code=1, command='dot', 
arguments='"/<>/doc/html/a00332_a3c04138a5bfe5d72780bb7e82a18e627_cgraph.dot"
 -Tsvg -o 
"/<>/doc/html/a00332_a3c04138a5bfe5d72780bb7e82a18e627_cgraph.svg"'
Running Error: 
/<>/doc/html/a00603_a6824947e6525f4afddb3bfa083f950d9_icgraph.dot: 
syntax error in line 8 near '-'
error: Problems running dot: exit code=1, command='dot', 
arguments='"/<>/doc/html/a00603_a6824947e6525f4afddb3bfa083f950d9_icgraph.dot"
 -Tsvg -o 
"/<>/doc/html/a00603_a6824947e6525f4afddb3bfa083f950d9_icgraph.svg"'
... and many others.

The other bug, succeeding most of the time due to usually ignoring errors is
obviously RC; but that's already filed as #818379 (severity: important).


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration
⣾⠁⢰⠒⠀⣿⡁ camps is back.  What about KL Warschau (operating until 1956)?
⢿⡄⠘⠷⠚⠋⠀ Zgoda?  Łambinowice?  Most ex-German KLs?  If those were "soviet
⠈⠳⣄ puppets", Bereza Kartuska?  Sikorski's camps in UK (thanks Brits!)?

Bug#889106: gcc-6: Support simpler multiarch systems

Source: gcc-6
Version: 6.4.0-12
Severity: wishlist
Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84173

One goal of a multiarch system is to make possible to run programs from
any other architecture. ELF executables depend on an interpreter that
should have a unique name; otherwise, loading the executable is
complicated.

Simpler multiarch systems use multiarch interpreter names. Thus, I ask
if Debian could support such systems. Also, I would appreciate
recommendations about proper interpreter names for Debian architectures.

Upstream does not want to support these systems. glibc Debian
maintainers, despite interoperability advantages, think these systems
are ugly and must not be supported in Debian.[1]

--
[1] https://bugs.debian.org/888073


smime.p7s
Description: S/MIME cryptographic signature

Bug#889107: libgdbm-compat-dev: missing Breaks: libgdbm-dev (<< 1.12-1) due to typo

Package: libgdbm-compat-dev
Version: 1.14.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.
...

The Breaks is actually intended to be there, but has a mistyped package
name (missing 'm').

This allows some broken partial upgrades + partial removals from stretch ...


Andreas

Bug#889112: wireless-regdb: Please merge changes from Ubuntu

Source: wireless-regdb
Version: 2016.06.10-1
Tags: patch

Please consider applying the patch I'm attaching in my follow-up email
to allow Ubuntu to autosync wireless-regdb from Debian.

Thanks,
Jeremy Bicha

Bug#821111: nginx: Failure to remove socket due to Debian's method of stopping

2018-02-01 Thread James Renken

SIGQUITs are still being sent, and sockets are not being cleaned up, as of 
1.10.3-1+deb9u1 and 1.13.3-1~bpo9+1.

Bug#883872: (no subject)

2018-02-01 Thread Wilmer van der Gaast

Severity: 883872 minor
stop

Please quote the part of
https://www.debian.org/doc/debian-policy/#copyright-information that
says "every single file must be mentioned in the copyright file". I
don't see it there nor would I see the point as per-file info is best
off stored in those very files.

Let me know if there's something actually serious like a *licence* not
being accounted for, or a (significant) author or group of authors (that
is not the currently mentioned me/dx/BitlBee team or Gaim team) not
mentioned.

Bug#889124: symfony FTBFS with PHP 7.2

Source: symfony
Version: 3.4.3+dfsg-1
Severity: serious

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

...
There was 1 skipped test:

1) Symfony\Bridge\Doctrine\Tests\ManagerRegistryTest
proxy-manager-bridge is not yet compatible with namespaced phpunit versions.

/build/1st/symfony-3.4.3+dfsg/src/Symfony/Bridge/Doctrine/Tests/ManagerRegistryTest.php:23

[30;43mOK, but incomplete, skipped, or risky tests![0m
[30;43mTests: 215[0m[30;43m, Assertions: 471[0m[30;43m, Skipped: 
1[0m[30;43m.[0m

Legacy deprecation notices (5)
debian/rules:70: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889122: phpdox FTBFS with PHP 7.2

Source: phpdox
Version: 0.10.1-2
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/phpdox-0.10.1'
ant test
Unable to locate tools.jar. Expected to find it in 
/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar
Buildfile: /build/1st/phpdox-0.10.1/build.xml

phpunit:
 [exec] PHPUnit 6.5.5 by Sebastian Bergmann and contributors.
 [exec] 
 [exec] Runtime:   PHP 7.2.1-1
 [exec] Configuration: /build/1st/phpdox-0.10.1/phpunit.xml.dist
 [exec] Error: No code coverage driver is available
 [exec] 
 [exec] E 
65 / 85 ( 76%)
 [exec]   
85 / 85 (100%)
 [exec] 
 [exec] Time: 4.59 seconds, Memory: 6.00MB
 [exec] 
 [exec] There was 1 error:
 [exec] 
 [exec] 1) 
TheSeer\phpDox\GlobalConfigTest::testGetCustomBootstrapFilesReturnsEmptyCollectionByDefault
 [exec] count(): Parameter must be an array or an object that implements 
Countable
 [exec] 
 [exec] /build/1st/phpdox-0.10.1/src/shared/FileInfoCollection.php:67
 [exec] /build/1st/phpdox-0.10.1/tests/Unit/config/GlobalConfigTest.php:127
 [exec] 
 [exec] ERRORS!
 [exec] Tests: 85, Assertions: 129, Errors: 1.

BUILD FAILED
/build/1st/phpdox-0.10.1/build.xml:28: exec returned: 2

Total time: 14 seconds
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889123: phpunit FTBFS with PHP 7.2

Source: phpunit
Version: 6.5.5-1
Severity: serious

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/phpunit-6.5.5'
# Build static classloader for shipping
phpab --output src/Autoload.php \
--template debian/Autoload.php.tpl src
phpab %development% - Copyright (C) 2009 - 2017 by Arne Blankerts and 
Contributors

Scanning directory src

Autoload file src/Autoload.php generated.

# Build classloader for tests
mkdir --parents vendor
phpab \
--output vendor/autoload.php \
--template debian/autoload.test.php.tpl \
--exclude tests/_files/BankAccountTest2.php \
--exclude tests/Regression/Trac/783/OneTest.php \
tests
phpab %development% - Copyright (C) 2009 - 2017 by Arne Blankerts and 
Contributors

Scanning directory tests

Autoload file vendor/autoload.php generated.

# Workaround to ensure the local class takes precedence during tests.
ln -s src PHPUnit
make[1]: Leaving directory '/build/1st/phpunit-6.5.5'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/phpunit-6.5.5'
./phpunit
Class 'DOMDocument' not found
debian/rules:28: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889111: bluez: Causes extreme non-stop CPU usage leading to notebook overheating quickly

Package: bluez
Version: 5.47-1+b1
Severity: critical
Justification: breaks the whole system

Hello, I initially reported this as a bug to udev/systemd but it resolved after 
removing the "bluez" package from my system,
with no other changes besides that. The original report has all the pertinent 
information:

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

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

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

Versions of packages bluez depends on:
ii  dbus  1.12.2-1
ii  kmod  25-1
ii  libasound21.1.3-5
ii  libc6 2.26-4
ii  libdbus-1-3   1.12.2-1
ii  libdw10.170-0.2
ii  libglib2.0-0  2.54.3-2
ii  libreadline7  7.0-3
ii  libudev1  236-3
ii  lsb-base  9.20170808
ii  udev  236-3

bluez recommends no packages.

Versions of packages bluez suggests:
pn  pulseaudio-module-bluetooth

Bug#889112: wireless-regdb: Please merge changes from Ubuntu


From 18e765a5b3c361e6bdcb7842c6d8d7a5350dcd70 Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Thu, 1 Feb 2018 22:55:20 -0500
Subject: [PATCH] Merge changes from Ubuntu (Closes: #889112)

* Add drop-home-from-key-generation.patch:
  - Fix key generation on buildds
* Generate a signing key for Ubuntu when built on Ubuntu
---
 debian/patches/drop-home-from-key-generation.patch | 23 ++
 debian/patches/series  |  1 +
 debian/rules   | 14 +
 3 files changed, 38 insertions(+)
 create mode 100644 debian/patches/drop-home-from-key-generation.patch

diff --git a/debian/patches/drop-home-from-key-generation.patch b/debian/patches/drop-home-from-key-generation.patch
new file mode 100644
index 000..dcf6b0f
--- /dev/null
+++ b/debian/patches/drop-home-from-key-generation.patch
@@ -0,0 +1,23 @@
+Description: drop home from key generation for buildd
+Author: Andy Whitcroft 
+
+--- wireless-regdb-2015.07.20.orig/Makefile
 wireless-regdb-2015.07.20/Makefile
+@@ -29,7 +29,7 @@ REGDB_AUTHOR ?= $(shell if [ -f $(DISTRO
+ 			echo custom-user; \
+ 		fi)
+ 
+-REGDB_PRIVKEY ?= $(HOME)/.wireless-regdb-$(REGDB_AUTHOR).key.priv.pem
++REGDB_PRIVKEY ?= .wireless-regdb-$(REGDB_AUTHOR).key.priv.pem
+ REGDB_PUBKEY ?= $(REGDB_AUTHOR).key.pub.pem
+ 
+ REGDB_UPSTREAM_PUBKEY ?= sforshee.key.pub.pem
+@@ -76,7 +76,7 @@ ifeq ($(MAKECMDGOALS),$(REGDB_PRIVKEY))
+ 	openssl genrsa -out $(REGDB_PRIVKEY) 2048
+ else
+ 	@echo "No private key found. To generate a private key, run:"
+-	@echo "make ~/.wireless-regdb-.key.priv.pem"
++	@echo "make .wireless-regdb-.key.priv.pem"
+ 	@echo "Your author-id is currently \"$(REGDB_AUTHOR)\"; set REGDB_AUTHOR to override this."
+ 	@exit 1
+ endif
diff --git a/debian/patches/series b/debian/patches/series
index d748e10..799f916 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@ dont_auto_create_keypair
 keep-setting-NO_IBSS-flag.patch
 enable_recording_and_using_an_external_signature.patch
 split_signature_generation.patch
+drop-home-from-key-generation.patch
diff --git a/debian/rules b/debian/rules
index b09f09e..b219714 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,16 +6,29 @@ export V = 1
 # prevent the build system from calling lsb_release
 export LSB_ID= Debian/Ubuntu
 
+ifeq (yes,$(shell dpkg-vendor --derives-from Ubuntu && echo yes))
+	export REGDB_AUTHOR  = ubuntu-devel-disc...@lists.ubuntu.com
+endif
+
 %:
 	dh ${@}
 
+
+override_dh_auto_build:
+	make .wireless-regdb-$(REGDB_AUTHOR).key.priv.pem
+	dh_auto_build
+
 override_dh_auto_configure:
 	cp debian/regulatory.bin.sig .
 
 override_dh_install:
 	make DESTDIR=debian/wireless-regdb install
 # crda will install public keys
+	rm -f debian/wireless-regdb/lib/crda/pubkeys/linville.key.pub.pem
+	rm -f debian/wireless-regdb/lib/crda/pubkeys/sforshee.key.pub.pem
+ifneq (yes,$(shell dpkg-vendor --derives-from Ubuntu && echo yes))
 	rm -r debian/wireless-regdb/lib/crda/pubkeys
+endif
 
 override_dh_auto_clean:
 	dh_auto_clean -- mrproper
@@ -26,3 +39,4 @@ sign: debian/regulatory.bin.sig
 debian/regulatory.bin.sig: db.txt
 	make regulatory.bin.sig
 	cp regulatory.bin.sig debian/
+	rm -f .wireless-regdb-$(REGDB_AUTHOR).key.priv.pem
-- 
2.15.1

Bug#889113: phpunit-object-enumerator dep8 tests need phpab

2018-02-01 Thread Nishanth Aravamudan

Package: phpunit-object-enumerator
Version: 3.0.3-2
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:


  * d/t/control: phpab is needed to run the DEP8 tests. 


Thanks for considering the patch.

*** /tmp/tmpq_42bg/phpunit-object-enumerator_3.0.3-2ubuntu3.debdiff
diff -Nru phpunit-object-enumerator-3.0.3/debian/tests/control 
phpunit-object-enumerator-3.0.3/debian/tests/control
--- phpunit-object-enumerator-3.0.3/debian/tests/control2017-08-23 
22:26:36.0 -0700
+++ phpunit-object-enumerator-3.0.3/debian/tests/control2018-02-01 
20:19:00.0 -0800
@@ -1,3 +1,3 @@
 Test-Command: mkdir --parents vendor && phpab --template 
debian/autoload.php.ci.in --output vendor/autoload.php tests/_fixture/ && 
phpunit
 Restrictions: rw-build-tree
-Depends: @, phpunit
+Depends: @, phpunit, phpab


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

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

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd

Bug#628157: Worklog maintainership

2018-02-01 Thread Adam Bilbrough

I contacted the author who has agreed to allow myself to be the new
upstream for worklog.  I will work on the package and the source and
upload to mentors with a fixed, clean package after my other ITAs are
done.  Worklog is useful to me so I have taken responsibility for it.

Sent using gmail as my encrypted email provider does not provide
plain-text emails.

Bug#889042: lintian: Do not use dot as a separator in build profile names

2018-02-01 Thread Helmut Grohne

On Thu, Feb 01, 2018 at 06:21:00PM +, Niels Thykier wrote:
> >> Please switch the dot to a suitable character, such as slash, in
> >> pkg.$sourcepackage.$anything build profile names, since dot is a valid
> >> character in package names.

I acknowledge that this is a weakness of the namespacing mechanism. A
different solution (without requiring any package to change) would be to
forbid dots in $anything.

Yes, Javier asked me on irc, but I didn't ack the change. I said that I
don't think it is worth fixing. When Guillem vaguely jumped in favour, I
said that he could drive the discussion forward.

> Regarding the proposal: Lintian is not the one deciding the namespace
> rules for build-profiles.  We only emit tags based on the existing
> guidelines/namespace rules (https://wiki.debian.org/BuildProfileSpec).
>   I have CC'ed Helmut as he is more involved in the build-profiles work.

I think we'd certainly need Joschs input.

So I state that:
1. I don't think this is worth fixing.
2. There is an alternative and simpler fix available. => No consensus.
3. The idea of changing the separator is not completely insane, but the
   cost of performing it is very high. Look, we still use DEB_STAGE (15
   packages) and DEB_BUILD_PROFILE (13 packages) in unstable.
4. You don't drive the discussion by filing bugs at lintian.
5. Discussion this has already wasted too much time better spent on
   fixing real bugs. Can we stop it now?

Helmut

Bug#889117: ruby2.3 FTBFS with tzdata 2018c-1

Source: ruby2.3
Version: 2.3.3-1
Severity: serious

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

...
  5) Failure:
TestTimeTZ#test_asia_tokyo [/<>/test/ruby/test_time_tz.rb:129]:
TZ=Asia/Tokyo Time.local(1951, 5, 6, 2, 0, 0).
<"1951-05-06 03:00:00 +1000"> expected but was
<"1951-05-06 02:00:00 +1000">.

  6) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_24 
[/<>/test/ruby/test_time_tz.rb:259]:
TZ=Asia/Tokyo Time.utc(1951, 5, 5, 16, 59, 59).localtime.
<"1951-05-06 01:59:59 +0900"> expected but was
<"1951-05-06 02:59:59 +1000">.

  7) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_27 
[/<>/test/ruby/test_time_tz.rb:259]:
TZ=Asia/Tokyo Time.utc(1951, 9, 7, 16, 0, 0).localtime.
<"1951-09-08 01:00:00 +0900"> expected but was
<"1951-09-08 02:00:00 +1000">.

  8) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_69 
[/<>/test/ruby/test_time_tz.rb:277]:
TZ=Asia/Tokyo Time.local(1951, 5, 6, 1, 59, 59).
<"1951-05-06 01:59:59 +0900"> expected but was
<"1951-05-06 01:59:59 +1000">.

  9) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_72 
[/<>/test/ruby/test_time_tz.rb:295]:
TZ=Asia/Tokyo Time.local(0, 0, 1, 8, 9, 1951, nil, nil, false, nil).
<"1951-09-08 01:00:00 +0900"> expected but was
<"1951-09-08 01:00:00 +1000">.
...


The same FTBFS in ruby2.5 was reported as #889046.

Additional unrelated failures in unstable caused by the
gdbm transition are handled in #832020.

I have reproduced this FTBFS with tzdata 2018c-1 in stretch,
and it is expected that tzdata >= 2018c will enter stretch.

Bug#889121: php-mail-mime FTBFS with PHP 7.2

Source: php-mail-mime
Version: 1.10.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-mail-mime.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-mail-mime-1.10.0'
cd Mail_Mime-* && pear run-tests tests
Running 39 tests
SKIP Test class filename (bug #24)[tests/class-filename.phpt](reason: This will 
be broken until Mail_Mime2)

Warning: count(): Parameter must be an array or an object that implements 
Countable in PEAR/RunTest.php on line 346
PHP Warning:  count(): Parameter must be an array or an object that implements 
Countable in /usr/share/php/PEAR/RunTest.php on line 346
PASS [ 2/39] Bug #2364   Tabs in 
Mail_mimePart::quotedPrintableEncode()[tests/encoding_case.phpt]
PASS [ 3/39] Multi-test for headers encoding using base64 and 
quoted-printable[tests/headers_with_mbstring.phpt]
SKIP Multi-test for headers encoding using base64 and 
quoted-printable[tests/headers_without_mbstring.phpt](reason: mbstring 
functions found!)

Warning: count(): Parameter must be an array or an object that implements 
Countable in PEAR/RunTest.php on line 346
PHP Warning:  count(): Parameter must be an array or an object that implements 
Countable in /usr/share/php/PEAR/RunTest.php on line 346
FAIL [ 5/39] Bug #3488   Sleep/Wakeup EOL Consistency - Part 
1[tests/sleep_wakeup_EOL-bug3488-part1.phpt]
FAIL [ 6/39] Bug #3488   Sleep/Wakeup EOL Consistency - Part 
2[tests/sleep_wakeup_EOL-bug3488-part2.phpt]
FAIL [ 7/39] Bug #3513   Support of RFC2231 in header fields. 
(ISO-8859-1)[tests/test_Bug_3513_1.phpt]
FAIL [ 8/39] Bug #3513   Support of RFC2231 in header fields. 
(UTF-8)[tests/test_Bug_3513_2.phpt]
FAIL [ 9/39] Bug #3513   Support of RFC2231 in header fields. 
(ISO-2022-JP)[tests/test_Bug_3513_3.phpt]
PASS [10/39] Bug #7561   Mail_mimePart::quotedPrintableEncode() misbehavior 
with mbstring overload[tests/test_Bug_7561_1.phpt]
FAIL [11/39] Bug #8386   HTML body not correctly encoded if attachments 
present[tests/test_Bug_8386_1.phpt]
PASS [12/39] Bug #8541   mimePart.php line delimiter is 
\r[tests/test_Bug_8541_1.phpt]
PASS [13/39] Bug #9722   quotedPrintableEncode does not encode dot at start of 
line on Windows platform[tests/test_Bug_9722_1.phpt]
FAIL [14/39] Bug #10596  Incorrect handling of text and html '0' 
bodies[tests/test_Bug_10596_1.phpt]
FAIL [15/39] Bug #10816  Unwanted linebreak at the end of 
output[tests/test_Bug_10816_1.phpt]
FAIL [16/39] Bug #10999  Bad Content-ID(cid) format[tests/test_Bug_10999_1.phpt]
FAIL [17/39] Bug #11381  Domain name is attached to content-id, trailing 
greater-than sign is not removed[tests/test_Bug_11381.phpt]
FAIL [18/39] Bug #11731  Full stops after soft line breaks are not 
encoded[tests/test_Bug_11731.phpt]
FAIL [19/39] Bug #12165  Dot at the end of the line 
disappeared[tests/test_Bug_12165.phpt]
FAIL [20/39] Bug #12385  Bad regex when replacing css style 
attachments[tests/test_Bug_12385_1.phpt]
FAIL [21/39] Bug #12411  RFC2047 encoded attachment 
filenames[tests/test_Bug_12411.phpt]
FAIL [22/39] Bug #12466  Content-Transfer-Encoding 
checking[tests/test_Bug_12466.phpt]
FAIL [23/39] Bug #13032  Proper (different) boundary for nested 
parts[tests/test_Bug_13032.phpt]
FAIL [24/39] Bug #9725   multipart/related & alternative wrong 
order[tests/test_Bug_13444.phpt]
PASS [25/39] Bug #13962  Multiple header support[tests/test_Bug_13962.phpt]
FAIL [26/39] Bug #14529  basename() workaround[tests/test_Bug_14529.phpt]
FAIL [27/39] Bug #14779  Proper header-body separator for empty 
attachment[tests/test_Bug_14779.phpt]
FAIL [28/39] Bug #14780  Invalid Content-Type when headers() is called before 
get()[tests/test_Bug_14780.phpt]
FAIL [29/39] Bug #15320  Charset parameter in Content-Type of mail 
parts[tests/test_Bug_15320.phpt]
PASS [30/39] Bug #16539  Headers longer than 998 
characters[tests/test_Bug_16539.phpt]
PASS [31/39] Bug #16539  Headers longer than 998 
characters[tests/test_Bug_17025.phpt]
FAIL [32/39] Bug #17175  Content-Description 
support+ecoding[tests/test_Bug_17175.phpt]
FAIL [33/39] Bug #18083  Separate charset for attachment's content and 
headers[tests/test_Bug_18083.phpt]
FAIL [34/39] Bug #18772  Text/calendar message[tests/test_Bug_18772.phpt]
FAIL [35/39] Bug #19497  Attachment filenames with a slash 
character[tests/test_Bug_19497.phpt]
PASS [36/39] Bug #20226  Mail_mimePart::encodeHeader() and ISO-2022-JP 
encoding[tests/test_Bug_20226.phpt]
PASS [37/39] Bug #20273  Mail_mimePart::encodeHeader() and TAB 
character[tests/test_Bug_20273.phpt]
PASS [38/39] Bug #20563   isMultipart() method tests[tests/test_Bug_20563.phpt]
PASS [39/39] Bug #20564   Unsetting headers[tests/test_Bug_20564.phpt]
wrote log to "/build/1st/php-mail-mime-1.10.0/Mail_Mime-1.10.0/run-tests.log"
TOTAL TIME: 00:07
12 PASSED TESTS
2 SKIPPED TESTS
25 FAILED TESTS:
/build/1st/php-mail-mime-1.10.0/Mail_Mime-1.10.0/tests/sleep_wakeup_EOL-bug3488-part1.phpt

Bug#889119: php-console-table FTBFS with PHP 7.2

Source: php-console-table
Version: 1.3.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-console-table.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-console-table-1.3.0'
pear run-tests Console_Table-*/tests
Running 15 tests
FAIL [ 1/15] Header and data as associative 
arrays.[Console_Table-1.3.0/tests/assoziative_arrays.phpt]
PASS [ 2/15] Border: default ASCII 
mode[Console_Table-1.3.0/tests/border-ascii.phpt]
PASS [ 3/15] Border: new custom 
mode[Console_Table-1.3.0/tests/border-custom.phpt]
PASS [ 4/15] Border: new custom mode, alternative 
style[Console_Table-1.3.0/tests/border-custom2.phpt]
PASS [ 5/15] Border: disable it[Console_Table-1.3.0/tests/border-disable.phpt]
PASS [ 6/15] Border: custom border 
character[Console_Table-1.3.0/tests/border-dot.phpt]
PASS [ 7/15] Border: empty 
character[Console_Table-1.3.0/tests/border-empty.phpt]
PASS [ 8/15] Bug #20181: setAlign() on non-zero 
column[Console_Table-1.3.0/tests/bug20181.phpt]
SKIP Data with ANSI color codes[Console_Table-1.3.0/tests/colors.phpt](reason: 
Console_Color2 not installed)

Warning: count(): Parameter must be an array or an object that implements 
Countable in PEAR/RunTest.php on line 346
PHP Warning:  count(): Parameter must be an array or an object that implements 
Countable in /usr/share/php/PEAR/RunTest.php on line 346
FAIL [10/15] Callback filters[Console_Table-1.3.0/tests/filters.phpt]
FAIL [11/15] Multibyte strings[Console_Table-1.3.0/tests/multibyte.phpt]
FAIL [12/15] Multiline table cells[Console_Table-1.3.0/tests/multiline.phpt]
FAIL [13/15] Table without header[Console_Table-1.3.0/tests/no_header.phpt]
PASS [14/15] Table without data[Console_Table-1.3.0/tests/no_rows.phpt]
FAIL [15/15] Horizontal rules[Console_Table-1.3.0/tests/rules.phpt]
wrote log to "/build/1st/php-console-table-1.3.0/run-tests.log"
TOTAL TIME: 00:10
8 PASSED TESTS
1 SKIPPED TESTS
6 FAILED TESTS:
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/assoziative_arrays.phpt
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/filters.phpt
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/multibyte.phpt
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/multiline.phpt
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/no_header.phpt
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/rules.phpt
Some tests failed
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889120: php-crypt-chap FTBFS with PHP 7.2

Source: php-crypt-chap
Version: 1.5.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-crypt-chap.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-crypt-chap-1.5.0'
pear run-tests Crypt_CHAP-*/tests
Running 1 tests
FAIL Crypt_CHAP: simple test[Crypt_CHAP-1.5.0/tests/Crypt_CHAP.phpt]
wrote log to "/build/1st/php-crypt-chap-1.5.0/run-tests.log"
TOTAL TIME: 00:00
0 PASSED TESTS
0 SKIPPED TESTS
1 FAILED TESTS:
/build/1st/php-crypt-chap-1.5.0/Crypt_CHAP-1.5.0/tests/Crypt_CHAP.phpt
Some tests failed
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889127: ggcov FTBFS: test failures

Source: ggcov
Version: 0.9-19
Severity: serious

Some recent change in unstable makes ggcov FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/ggcov-0.9'
(cd test && ./runtest)
Running tests
hostname: "profitbricks-build1-amd64"
date: "20180201T144325"
uname -s: "Linux"
uname -m: "x86_64"
uname -r: "4.9.0-5-amd64"
head -1 /etc/os-release: "PRETTY_NAME="Debian GNU/Linux buster/sid""
which gcc: "/usr/bin/gcc"
gcc --version: "gcc (Debian 7.3.0-5+really1.0~reproducible1) 7.3.0"
which g++: "/usr/bin/g++"
g++ --version: "g++ (Debian 7.3.0-5+really1.0~reproducible1) 7.3.0"
PASS: (test000) unit tests
ERROR: (test001) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test002) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test004) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test005.1) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test006) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test007) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test008.0) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test009) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test010) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test011.1) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test013) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test014) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test015.a001) tggcov failed, see log or re-run with -D all,verbose 
--no-log
ERROR: (test016.1) tggcov failed, see log or re-run with -D all,verbose --no-log
PASS: (test021) unit test for libpopt / fakepopt.c
ERROR: (test029) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test030) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test033) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test034) tggcov failed, see log or re-run with -D all,verbose --no-log
Total: 2/20 tests passed
debian/rules:34: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889110: udev: extremely high cpu usage (overheats notebook after a minute of use)

Here's the "bluez" issue report
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889111

Hopefully the maintainers for both packages can communicate to identify
responsibilities and solve the issue. Thank you!

On 2 February 2018 at 01:36, Alex Henry  wrote:

> After reading this thread I have managed to solve the issue
> https://bbs.archlinux.org/viewtopic.php?id=232890
>
> All it took was for me to remove the "bluetooth" package via aptitude,
> which depends on "bluez" - I will create an appropriate bug report for that
> package as well.
>
> On 2 February 2018 at 01:12, Alex Henry  wrote:
>
>> Package: udev
>> Version: 236-3
>> Severity: important
>>
>> Hello it's been a while since I update my Debian (testing) packages for
>> my laptop computer
>> but after updating all of them today it has been rendered unusable for
>> all intents and
>> purposes. The main issue is a process tree (systemd-udevd) hangs all my
>> CPUs, at least
>> one in 100% and the others at 50% or more consistently, non-stop.
>>
>> This causes my laptop to overheat anywhere between a minute or two
>> minutes of use.
>> The only way I'm able to write this is by issuing STOP signals to suspend
>> the processes
>> but it only lasts a couple minutes before it starts again on its own.
>> Needless to say,
>> this isn't what systemd should behave like and I can't even keep issuing
>> STOP long enough
>> for anything other than writing this message. My computer is practically
>> unusable at this
>> point unless I manually issue stop signals every couple of minutes before
>> it overheats.
>>
>> I have tens of thousands of lines like this when I run ""udevadm monitor
>> -k":
>>
>> KERNEL[675.883845] bind /devices/pci:00/:00:1
>> d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb)
>> KERNEL[675.884171] unbind   /devices/pci:00/:00:1
>> d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb)
>>
>> Pleae consider elevating this issue's priority to critical. In no way the
>> package in this current
>> state should hit stable for obvious reasons, even if they're not on an
>> overheating-prone machine.
>>
>> -- Package-specific info:
>>
>> -- System Information:
>> Debian Release: buster/sid
>>   APT prefers testing
>>   APT policy: (500, 'testing')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
>> LANGUAGE=en_US:en (charmap=UTF-8)
>> Shell: /bin/sh linked to /usr/bin/dash
>> Init: systemd (via /run/systemd/system)
>> LSM: AppArmor: enabled
>>
>> Versions of packages udev depends on:
>> ii  adduser  3.116
>> ii  libacl1  2.2.52-3+b1
>> ii  libblkid12.30.2-0.3
>> ii  libc62.26-4
>> ii  libkmod2 25-1
>> ii  libselinux1  2.7-2
>> ii  libudev1 236-3
>> ii  lsb-base 9.20170808
>> ii  procps   2:3.3.12-3
>> ii  util-linux   2.30.2-0.3
>>
>> udev recommends no packages.
>>
>> udev suggests no packages.
>>
>> Versions of packages udev is related to:
>> ii  systemd  236-3
>>
>> -- no debconf information
>>
>
>

Bug#889028: minissdpd: Fails to install on Debian unstable

2018-02-01 Thread Awtul

Package: minissdpd
Version: 1.5.20161216-1
Followup-For: Bug #889028

Dear Maintainer,

I just wanted to confirm the bug. 
So, upgrading from minissdpd:amd64 1.2.20130907-4.1 to  1.5.20161216-1 I got 
"Error: Sub-process /usr/bin/dpkg returned an error code (1)". Same error after 
purging the buggy pkg
and reinstalling it.
systemctl status minissdpd 
"Loaded: loaded (/lib/systemd/system/minissdpd.service; disabled; vendor 
preset: enabled)Active: inactive (dead)"

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

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

Versions of packages minissdpd depends on:
ii  libc6  2.26-6
ii  libnfnetlink0  1.0.1-3+b1
ii  lsb-base   9.20170808

minissdpd recommends no packages.

minissdpd suggests no packages.

-- no debconf information

Bug#889114: libdbus-c++-{ecore,glib}-1.so: undefined symbols: need -ldbus-c++-1

2018-02-01 Thread Paul Wise

Package: libdbus-c++-1-0v5
Version: 0.9.0-8.1
Severity: minor
File: /usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0
File: /usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0
User: debian...@lists.debian.org
Usertags: undefined-symbol adequate

libdbus-c++-ecore-1.so and libdbus-c++-glib-1.so need to link with
-ldbus-c++-1, see the output of adequate, symtree and objdump below.
I detected this on amd64 but the Debian build log scanner also detected
dpkg-buildpackage complaining about it on other architectures, see the
w3m and build log output below.

I filed this bug at severity minor since I'm guessing that any code
using the ecore/glib wrappers also already uses libdbus-c++-1.so or
that there is no code using the wrappers.

This bug report brought to you by adequate:

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

$ adequate libdbus-c++-1-0v5
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => _ZN4DBus9debug_logE
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZN4DBus7TimeoutC2EPNS0_8InternalE
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZN4DBus12DefaultMutexD1Ev
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZN4DBus5WatchC2EPNS0_8InternalE
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZNK4DBus5Watch5flagsEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZNK4DBus5Watch7enabledEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZNK4DBus5Watch10descriptorEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZNK4DBus7Timeout7enabledEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZN4DBus5Watch6handleEi
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZNK4DBus7Timeout8intervalEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZN4DBus12DefaultMutexC1Ev
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZN4DBus7Timeout6handleEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
_ZN4DBus10Dispatcher16dispatch_pendingEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => _ZN4DBus9debug_logE
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZN4DBus7TimeoutC2EPNS0_8InternalE
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZN4DBus12DefaultMutexD1Ev
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZN4DBus5WatchC2EPNS0_8InternalE
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => _ZNK4DBus5Watch5flagsEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZNK4DBus5Watch7enabledEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZNK4DBus5Watch10descriptorEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZNK4DBus7Timeout7enabledEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZN4DBus10Dispatcher25has_something_to_dispatchEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => _ZN4DBus5Watch6handleEi
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZNK4DBus7Timeout8intervalEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZN4DBus12DefaultMutexC1Ev
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZN4DBus7Timeout6handleEv
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 => 
_ZN4DBus10Dispatcher16dispatch_pendingEv

$ adequate libdbus-c++-1-0v5 | c++filt
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => DBus::debug_log
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
DBus::Timeout::Timeout(DBus::Timeout::Internal*)
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
DBus::DefaultMutex::~DefaultMutex()
libdbus-c++-1-0v5:amd64: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 => 
DBus::Watch::Watch(DBus::Watch::Internal*)

Bug#889115: pnetcdf FTBFS on 32bit: Building of Parallel NetCDF cannot continue due to the size of MPI_Offset being less than 8 bytes

Source: pnetcdf
Version: 1.9.0-1
Severity: serious

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

...
checking for MPI_Offset... yes
checking size of MPI_Offset... 4
configure: error: 
   ---
 Building of Parallel NetCDF cannot continue due to the size of
 MPI_Offset being less than 8 bytes. Please use an MPI library that
 supports large files. Abort.
   ---

Bug#889116: logcheck-database: enhance more wpasupplicant rules with optional regex group

2018-02-01 Thread Carl Suster

Package: logcheck-database
Version: 1.3.18
Severity: wishlist
Tags: patch

Logcheck output includes lines like:

Feb  2 15:53:18 local wpa_supplicant[777]: wlp4s0: CTRL-EVENT-EAP-STARTED EAP 
authentication started
Feb  2 15:53:18 local wpa_supplicant[777]: wlp4s0: 
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=26 -> NAK
Feb  2 15:53:18 local wpa_supplicant[777]: wlp4s0: 
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
Feb  2 15:53:18 local wpa_supplicant[777]: wlp4s0: CTRL-EVENT-EAP-METHOD EAP 
vendor 0 method 25 (PEAP) selected
Feb  2 15:53:18 local wpa_supplicant[777]: wlp4s0: CTRL-EVENT-EAP-SUCCESS EAP 
authentication completed successfully

There is already the following rule intended to capture these:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ wpa_supplicant\[[0-9]+\]: 
CTRL-EVENT-EAP-(STARTED EAP authentication started|SUCCESS EAP authentication 
completed successfully|METHOD EAP vendor 0 method (17 \(LEAP|25 \(PEAP)\) 
selected)$

However this is not capturing the "wlp4s0: " part. Some other rules in the file 
contain optional
regexp groups to capture this part in other log lines, e.g.:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ wpa_supplicant\[[0-9]+\]: 
((wlan[0-9]|wlp[0-9]s[0-9]): )?CTRL-EVENT-SUBNET-STATUS-UPDATE status=0$

So could we replace the first rule above with:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ wpa_supplicant\[[0-9]+\]: 
((wlan[0-9]|wlp[0-9]s[0-9]): )?CTRL-EVENT-EAP-(STARTED EAP authentication 
started|SUCCESS EAP authentication completed successfully|METHOD EAP vendor 0 
method (17 \(LEAP|25 \(PEAP)\) selected)$

Bug#889125: comidi-clojure FTBFS: test failure

Source: comidi-clojure
Version: 0.3.1-1
Severity: serious

Some recent change in unstable makes comidi-clojure FTBFS:

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

...
dh_auto_test
(cd test && find . -name "*.clj" | \
xargs --verbose clojure -cp 
/build/1st/comidi-clojure-0.3.1/comidi.jar:/usr/share/java/clojure.jar:/usr/share/java/clj-time.jar:/usr/share/java/bidi.jar:/usr/share/java/compojure.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/kitchensink.jar)
clojure -cp 
/build/1st/comidi-clojure-0.3.1/comidi.jar:/usr/share/java/clojure.jar:/usr/share/java/clj-time.jar:/usr/share/java/bidi.jar:/usr/share/java/compojure.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/kitchensink.jar
 ./puppetlabs/comidi_test.clj 
Exception in thread "main" clojure.lang.ExceptionInfo: Call to clojure.core/ns 
did not conform to spec:
In: [1] val: ((require [clojure.test :refer :all] [puppetlabs.comidi :as comidi 
:refer :all] [schema.test :as schema-test] [schema.core :as schema] 
[clojure.zip :as zip] [bidi.bidi :as bidi])) fails at: [:args] predicate: (cat 
:docstring (? string?) :attr-map (? map?) :clauses 
:clojure.core.specs/ns-clauses),  Extra input
:clojure.spec/args  (puppetlabs.comidi-test (require [clojure.test :refer :all] 
[puppetlabs.comidi :as comidi :refer :all] [schema.test :as schema-test] 
[schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as bidi]))
 #:clojure.spec{:problems [{:path [:args], :reason "Extra input", :pred (cat 
:docstring (? string?) :attr-map (? map?) :clauses 
:clojure.core.specs/ns-clauses), :val ((require [clojure.test :refer :all] 
[puppetlabs.comidi :as comidi :refer :all] [schema.test :as schema-test] 
[schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as bidi])), :via [], 
:in [1]}], :args (puppetlabs.comidi-test (require [clojure.test :refer :all] 
[puppetlabs.comidi :as comidi :refer :all] [schema.test :as schema-test] 
[schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as bidi]))}, 
compiling:(/build/1st/comidi-clojure-0.3.1/test/./puppetlabs/comidi_test.clj:1:1)
at clojure.lang.Compiler.load(Compiler.java:7442)
at clojure.lang.Compiler.loadFile(Compiler.java:7368)
at clojure.main$load_script.invokeStatic(main.clj:277)
at clojure.main$script_opt.invokeStatic(main.clj:337)
at clojure.main$script_opt.invoke(main.clj:332)
at clojure.main$main.invokeStatic(main.clj:423)
at clojure.main$main.doInvoke(main.clj:386)
at clojure.lang.RestFn.applyTo(RestFn.java:137)
at clojure.lang.Var.applyTo(Var.java:700)
at clojure.main.main(main.java:37)
Caused by: clojure.lang.ExceptionInfo: Call to clojure.core/ns did not conform 
to spec:
In: [1] val: ((require [clojure.test :refer :all] [puppetlabs.comidi :as comidi 
:refer :all] [schema.test :as schema-test] [schema.core :as schema] 
[clojure.zip :as zip] [bidi.bidi :as bidi])) fails at: [:args] predicate: (cat 
:docstring (? string?) :attr-map (? map?) :clauses 
:clojure.core.specs/ns-clauses),  Extra input
:clojure.spec/args  (puppetlabs.comidi-test (require [clojure.test :refer :all] 
[puppetlabs.comidi :as comidi :refer :all] [schema.test :as schema-test] 
[schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as bidi]))
 {:clojure.spec/problems [{:path [:args], :reason "Extra input", :pred (cat 
:docstring (? string?) :attr-map (? map?) :clauses 
:clojure.core.specs/ns-clauses), :val ((require [clojure.test :refer :all] 
[puppetlabs.comidi :as comidi :refer :all] [schema.test :as schema-test] 
[schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as bidi])), :via [], 
:in [1]}], :clojure.spec/args (puppetlabs.comidi-test (require [clojure.test 
:refer :all] [puppetlabs.comidi :as comidi :refer :all] [schema.test :as 
schema-test] [schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as 
bidi]))}
at clojure.core$ex_info.invokeStatic(core.clj:4725)
at clojure.spec$macroexpand_check.invokeStatic(spec.clj:697)
at clojure.spec$macroexpand_check.invoke(spec.clj:686)
at clojure.lang.AFn.applyToHelper(AFn.java:156)
at clojure.lang.AFn.applyTo(AFn.java:144)
at clojure.lang.Var.applyTo(Var.java:700)
at clojure.lang.Compiler.macroexpand1(Compiler.java:6816)
at clojure.lang.Compiler.macroexpand(Compiler.java:6888)
at clojure.lang.Compiler.eval(Compiler.java:6962)
at clojure.lang.Compiler.load(Compiler.java:7430)
... 9 more
debian/rules:32: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 123

Bug#889110: udev: extremely high cpu usage (overheats notebook after a minute of use)

Package: udev
Version: 236-3
Severity: important

Hello it's been a while since I update my Debian (testing) packages for my 
laptop computer
but after updating all of them today it has been rendered unusable for all 
intents and
purposes. The main issue is a process tree (systemd-udevd) hangs all my CPUs, 
at least
one in 100% and the others at 50% or more consistently, non-stop.

This causes my laptop to overheat anywhere between a minute or two minutes of 
use.
The only way I'm able to write this is by issuing STOP signals to suspend the 
processes
but it only lasts a couple minutes before it starts again on its own. Needless 
to say,
this isn't what systemd should behave like and I can't even keep issuing STOP 
long enough
for anything other than writing this message. My computer is practically 
unusable at this
point unless I manually issue stop signals every couple of minutes before it 
overheats.

I have tens of thousands of lines like this when I run ""udevadm monitor -k":

KERNEL[675.883845] bind 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb)
KERNEL[675.884171] unbind   
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb)

Pleae consider elevating this issue's priority to critical. In no way the 
package in this current
state should hit stable for obvious reasons, even if they're not on an 
overheating-prone machine.

-- Package-specific info:

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

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

Versions of packages udev depends on:
ii  adduser  3.116
ii  libacl1  2.2.52-3+b1
ii  libblkid12.30.2-0.3
ii  libc62.26-4
ii  libkmod2 25-1
ii  libselinux1  2.7-2
ii  libudev1 236-3
ii  lsb-base 9.20170808
ii  procps   2:3.3.12-3
ii  util-linux   2.30.2-0.3

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  236-3

-- no debconf information
P: /devices/LNXSYSTM:00
E: DEVPATH=/devices/LNXSYSTM:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXSYSTM:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8817452

P: /devices/LNXSYSTM:00/LNXCPU:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8846266

P: /devices/LNXSYSTM:00/LNXCPU:01
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=9028431

P: /devices/LNXSYSTM:00/LNXCPU:02
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=9029157

P: /devices/LNXSYSTM:00/LNXCPU:03
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=9028450

P: /devices/LNXSYSTM:00/LNXPWRBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00
E: DRIVER=button
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXPWRBN:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=9028947

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input9
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input9
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=10942676

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input9/event8
N: input/event8
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event8
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input9/event8
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: LIBINPUT_DEVICE_GROUP=19/0/1:LNXPWRBN/button
E: MAJOR=13
E: MINOR=72
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=13225691
E: XKBLAYOUT=br
E: XKBMODEL=pc105

P: /devices/LNXSYSTM:00/LNXSYBUS:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXSYBUS:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=9028692

P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00
E: DRIVER=ac
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:ACPI0003:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=9211374

P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/power_supply/AC
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/power_supply/AC
E: POWER_SUPPLY_NAME=AC
E: POWER_SUPPLY_ONLINE=1
E:

Bug#889110: udev: extremely high cpu usage (overheats notebook after a minute of use)

After reading this thread I have managed to solve the issue
https://bbs.archlinux.org/viewtopic.php?id=232890

All it took was for me to remove the "bluetooth" package via aptitude,
which depends on "bluez" - I will create an appropriate bug report for that
package as well.

On 2 February 2018 at 01:12, Alex Henry  wrote:

> Package: udev
> Version: 236-3
> Severity: important
>
> Hello it's been a while since I update my Debian (testing) packages for my
> laptop computer
> but after updating all of them today it has been rendered unusable for all
> intents and
> purposes. The main issue is a process tree (systemd-udevd) hangs all my
> CPUs, at least
> one in 100% and the others at 50% or more consistently, non-stop.
>
> This causes my laptop to overheat anywhere between a minute or two minutes
> of use.
> The only way I'm able to write this is by issuing STOP signals to suspend
> the processes
> but it only lasts a couple minutes before it starts again on its own.
> Needless to say,
> this isn't what systemd should behave like and I can't even keep issuing
> STOP long enough
> for anything other than writing this message. My computer is practically
> unusable at this
> point unless I manually issue stop signals every couple of minutes before
> it overheats.
>
> I have tens of thousands of lines like this when I run ""udevadm monitor
> -k":
>
> KERNEL[675.883845] bind /devices/pci:00/:00:
> 1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb)
> KERNEL[675.884171] unbind   /devices/pci:00/:00:
> 1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb)
>
> Pleae consider elevating this issue's priority to critical. In no way the
> package in this current
> state should hit stable for obvious reasons, even if they're not on an
> overheating-prone machine.
>
> -- Package-specific info:
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages udev depends on:
> ii  adduser  3.116
> ii  libacl1  2.2.52-3+b1
> ii  libblkid12.30.2-0.3
> ii  libc62.26-4
> ii  libkmod2 25-1
> ii  libselinux1  2.7-2
> ii  libudev1 236-3
> ii  lsb-base 9.20170808
> ii  procps   2:3.3.12-3
> ii  util-linux   2.30.2-0.3
>
> udev recommends no packages.
>
> udev suggests no packages.
>
> Versions of packages udev is related to:
> ii  systemd  236-3
>
> -- no debconf information
>

Bug#889110: udev: extremely high cpu usage (overheats notebook after a minute of use)

2018-02-01 Thread Michael Biebl

Am 02.02.2018 um 04:50 schrieb Alex Henry:
> Here's the "bluez" issue report
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889111
> 
> Hopefully the maintainers for both packages can communicate to identify
> responsibilities and solve the issue. Thank you!

Looks like neither a udev nor bluez issue but a kernel/driver bug to me.
Might also be faulty hardware.
systemd-udevd is simply reacting to the uevents that are generated by
the kernel here. And since apparently you are flooded with those
bind/unbind events, systemd-udevd keeps your CPU busy.

You might try rolling back to an older kernel and see if that fixes the
problem.


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



signature.asc
Description: OpenPGP digital signature

Bug#871443: Status?

2018-02-01 Thread Artem Popov

Hi Harlan, Tom!

Any updates on this? Tom, do you need any help with updating the package?

Cheers,
Artem

Bug#889006: [debhelper-devel] Bug#889006: dh-autoreconf is run before patching

On Thu, Feb 01, 2018 at 07:01:00PM +, Niels Thykier wrote:
>...
> Indeed, from my PoV we would ideally fix this issue in dpatch.  However,
> we need to handle backports as well and that puts quilt back the table
> as well.  I am not quite sure that I want to backport quilt and dpatch
> to provide further debhelper backports.

Why not?

dpatch is a mostly obsolete Debian native package,
most recent upload 2015.

quilt still has some upstream development, but nothing big.

It might still be easier to revert the change in dh-autoreconf,
but dpatch and quilt are not packages where I would see any
potential problems with making and supporting a backport.

> Thanks,
> ~Niels

cu
Adrian

-- 

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

Bug#875194: linux stopmotion has moved to qt5, just needs somebody to update the package and maybe uvvcapture as well.

2018-02-01 Thread shirish शिरीष

Dear all,

See 
https://sourceforge.net/p/linuxstopmotion/code/ci/23d60eb08b742746a91ab96876404b1e1b571b0b/

By this commit it was moved to QT5 so probably needs somebody to make
a new release.

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

Bug#889118: bitcoin FTBFS with gcc-7 7.3.0-1: symbols disappeared

Source: bitcoin
Version: 0.15.1~dfsg-1
Severity: serious

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

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/1st/bitcoin-0.15.1~dfsg'
dh_makeshlibs -- 
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libbitcoinconsensus0/DEBIAN/symbols doesn't 
match completely debian/libbitcoinconsensus0.symbols
--- debian/libbitcoinconsensus0.symbols 
(libbitcoinconsensus0_0.15.1~dfsg-1_amd64)
+++ dpkg-gensymbolsk5YxNq   2019-03-05 21:13:06.499223011 -1200
@@ -38,7 +38,7 @@
  _Z14ArithToUint256RK13arith_uint256@Base 0.14.2~dfsg
 #MISSING: 0.15.0~~# _Z14GetBlockWeightRK6CBlock@Base 0.14.2~dfsg
  
_Z14SanitizeStringRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base 
0.14.2~dfsg
- 
(optional=templinst|arch-bits=64)_Z14Serialize_implI13CSizeComputer5CTxInSaIS1_ES1_EvRT_RKSt6vectorIT0_T1_ERKT2_@Base
 0.15.0~~
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst|arch-bits=64)_Z14Serialize_implI13CSizeComputer5CTxInSaIS1_ES1_EvRT_RKSt6vectorIT0_T1_ERKT2_@Base
 0.15.0~~
  (arch-bits=64)_Z14SipHashUint256mmRK7uint256@Base 0.14.2~dfsg
  (arch-bits=32)_Z14SipHashUint256yyRK7uint256@Base 0.14.2~dfsg
  _Z14UintToArith256RK7uint256@Base 0.14.2~dfsg
@@ -47,7 +47,7 @@
  
(arch-bits=64)_Z15FormatParagraphRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEmm@Base
 0.14.2~dfsg
  
(arch-bits=64)_Z15ParseFixedPointRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiPl@Base
 0.14.2~dfsg
  
(arch-bits=32)_Z15ParseFixedPointRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiPx@Base
 0.14.2~dfsg
-#MISSING: 0.15.0~~# 
(optional=templinst)_Z16GetSerializeSizeI6CBlockE{size_t}RKT_ii@Base 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_Z16GetSerializeSizeI6CBlockE{size_t}RKT_ii@Base 0.14.2~dfsg
  _Z16SHA256AutoDetectB5cxx11v@Base 0.15.0~~
  
(optional=templinst|arch-bits=64)_Z16WriteCompactSizeI11CHashWriterEvRT_m@Base 
0.14.2~dfsg
  
(optional=templinst|arch-bits=32)_Z16WriteCompactSizeI11CHashWriterEvRT_y@Base 
0.14.2~dfsg
@@ -58,8 +58,8 @@
  _Z19ComputeMerkleBranchRKSt6vectorI7uint256SaIS0_EEj@Base 0.14.2~dfsg
  (subst)_Z19SipHashUint256Extra{uint64_t}{uint64_t}RK7uint256j@Base 0.15.0~~
 #MISSING: 0.15.0~~# _Z20GetTransactionWeightRK12CTransaction@Base 0.14.2~dfsg
-#MISSING: 0.15.0~~# 
(optional=templinst)_Z20SerializeTransactionI11CHashWriter12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
-#MISSING: 0.15.0~~# 
(optional=templinst)_Z20SerializeTransactionI13CSizeComputer12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_Z20SerializeTransactionI11CHashWriter12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_Z20SerializeTransactionI13CSizeComputer12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
  _Z22BlockWitnessMerkleRootRK6CBlockPb@Base 0.14.2~dfsg
  _Z22CheckSignatureEncodingRKSt6vectorIhSaIhEEjP13ScriptError_t@Base 
0.14.2~dfsg
  _Z27ComputeMerkleRootFromBranchRK7uint256RKSt6vectorIS_SaIS_EEj@Base 
0.14.2~dfsg
@@ -247,8 +247,8 @@
  (optional=templinst)_ZN9base_uintILj256EEmLERKS0_@Base 0.14.2~dfsg
  (optional=templinst)_ZN9base_uintILj256EEmLEj@Base 0.14.2~dfsg
  (optional=templinst)_ZN9base_uintILj256EErSEj@Base 0.14.2~dfsg
-#MISSING: 0.15.0~~# (optional=templinst)_ZN9prevectorILj28EhjiED1Ev@Base 
0.14.2~dfsg
-#MISSING: 0.15.0~~# (optional=templinst)_ZN9prevectorILj28EhjiED2Ev@Base 
0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# (optional=templinst)_ZN9prevectorILj28EhjiED1Ev@Base 
0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# (optional=templinst)_ZN9prevectorILj28EhjiED2Ev@Base 
0.14.2~dfsg
  _ZNK10CExtPubKey6DeriveERS_j@Base 0.11.0
  _ZNK10CExtPubKey6EncodeEPh@Base 0.11.0
  _ZNK10CSipHasher8FinalizeEv@Base 0.14.2~dfsg
@@ -314,14 +314,14 @@
  
(optional=templinst|arch-bits=32)_ZNSt6vectorI7uint256SaIS0_EE17_M_default_appendEj@Base
 0.14.2~dfsg
  
(optional=templinst|arch-bits=64)_ZNSt6vectorI7uint256SaIS0_EE17_M_default_appendEm@Base
 0.14.2~dfsg
  
_ZNSt6vectorI7uint256SaIS0_EE17_M_realloc_insertIJRKS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
 0.15.1~dfsg
- 
(optional=templinst)_ZNSt6vectorI7uint256SaIS0_EE19_M_emplace_back_auxIJRKS0_EEEvDpOT_@Base
 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_ZNSt6vectorI7uint256SaIS0_EE19_M_emplace_back_auxIJRKS0_EEEvDpOT_@Base
 0.14.2~dfsg
  
(optional=templinst)_ZNSt6vectorIS_IhSaIhEESaIS1_EE12emplace_backIJS1_EEEvDpOT_@Base
 0.14.2~dfsg
- 
(optional=templinst)_ZNSt6vectorIS_IhSaIhEESaIS1_EE13_M_insert_auxIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.14.2~dfsg
- 
(optional=templinst)_ZNSt6vectorIS_IhSaIhEESaIS1_EE13_M_insert_auxIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_ZNSt6vectorIS_IhSaIhEESaIS1_EE13_M_insert_auxIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.14.2~dfsg
+#MISSING:

Bug#889126: fswatch FTBFS with gcc-7 7.3.0-1: symbol differences