Bug#895263: RM: bpfcc/0.3.0-4

[Adam D. Barratt]

Control: reassign -1 ftp.debian.org

On Mon, 2018-04-09 at 09:25 +0530, Ritesh Raj Sarraf wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: rm
> 
> Please remove bpfcc version 0.3.0-4 from the archives. These are
> outdated binaries on unsupported architectures.
> 
> With newer 0.5.0 release, we have narrowed down the list of
> architectures where bpfcc can be run. 0.5.0 is already in Unstable.
> 

They need removing from unstable, which is ftp-master's territory; re-
assigning.

Regards,

Adam

Bug#895017: [Pkg-deepin-devel] Bug#895017: deepin-picker: wrong homepage

[Yangfl]

2018-04-06 18:07 GMT+08:00 Jonas Smedegaard :
> Package points to Github as its homepage.
>
> That is wrong in two ways: Github page lists itself at first line as a mirror 
> only, and canonical page is not really Homepage for the code project, only 
> revision control location.
>
> Correct homepage is https://www.deepin.org/en/original/deepin-picker/
>
> Please adjust the package metadata.
>
>  - Jonas

As you can see, the page is poorly maintained and less informational,
except the URLs for external resources. And this homepage URL is
approved by Deepin developer team, see
https://github.com/linuxdeepin/deepin-system-monitor/blob/master/debian/control
.

The github is a mirror in the sense of a mirror of deepin cr site. The
deepin cr site has a relatively low bandwidth and experiences out of
service from time to time, so that is not recommended for public
download.

So we believe the github page might be the better nomination for the
homepage field. But if you think it's still wrong, this is discussable
and feel free to reply and give your opinions.

G.

Bug#893174: Pending fixes for bugs in the libcommons-compress-java package

[pkg-java-maintainers]

tag 893174 + pending
thanks

Some bugs in the libcommons-compress-java package are closed in
revision e16c99b56d29473b064ce3351b66cedf721a8bc8 in branch 'master'
by tony mancill

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

Commit message:

Apply patch for CVE-2018-1324 (Closes: #893174)

Bug#895264: new upstream release (and maintainer)

[Antoine Beaupre]

Package: taffybar
Version: 0.4.6-5+b2
Severity: wishlist

Upstream shared access to a new maintainer who published a new (1.0!)
release:

https://github.com/travitch/taffybar/releases/tag/v1.0.0

Discussion:

https://github.com/travitch/taffybar/issues/179

Lots of good stuff in there, including support for:

 * i3
 * multiple monitors
 * multiple batteries
 * vertical bars
 * images in workspace switcher
 * multiple NICs
 * volume widget

... and more! The thing was also ported to GTK3 which involves some
configuration changes to the rc file, replaced by a CSS file.

It would be great to see this in Debian. Any plans on doing so?

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

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

Versions of packages taffybar depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u3
ii  libcairo21.14.8-1
ii  libffi6  3.2.1-6
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgmp10 2:6.1.2+dfsg-1
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages taffybar recommends:
ii  libghc-taffybar-dev  0.4.6-5+b2
pn  libghc-taffybar-doc  

taffybar suggests no packages.

-- no debconf information

Bug#895263: RM: bpfcc/0.3.0-4

[Ritesh Raj Sarraf]

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

Please remove bpfcc version 0.3.0-4 from the archives. These are
outdated binaries on unsupported architectures.

With newer 0.5.0 release, we have narrowed down the list of
architectures where bpfcc can be run. 0.5.0 is already in Unstable.

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

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

Bug#894429: Please create new list debian-deepin

[Yanhao Mo]

Hi Alexander,

I am a member of pkg-deepin.

Process porting all deepin softwares (include the whole Deepin Desktop
Environment as well as deepin applications) are still active, and there
are still a lot of work need to be done. As a work team(pkg-deepin team)
we want our all packages under one umbrella to make the whole process easy
to track. And we also need this list for communicate between our
members, that will make our work easier. Although there are few messages
now on pkg-deepin-de...@lists.alioth.debian.org now, but if the Deepin
softwares gaining more debian users, we need a list for users seeking
help from us conveniently. And if we lose it, we will have to pay
much of extra attentions to find an workaround. That's painful. So
since the coming of shutdown of Alioth we really need a new mail list
to make our work still smoothly as before.

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#895262: RFS: deepin-menu/3.3.2-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "deepin-menu"

* Package name: deepin-menu
  Version : 3.3.2-1
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://github.com/linuxdeepin/deepin-menu
* License : GPL-3+
  Section : x11

It builds those binary packages:

  deepin-menu - Deepin menu service

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

  https://mentors.debian.net/package/deepin-menu

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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-menu/deepin-menu_3.3.2-1.dsc

More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-menu

Changes since the last upload:
  * New upstream release.
  * d/control: add new uploader Yanhao Mo 
  * d/control: Use Salsa platform for Vcs field.
  * debian/control: Update Standers-Version to 4.1.4.
  * debian/compat: Switch compat to level 11.

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#894997: [PATCH] git-svn: avoid warning on undef readline()

[Junio C Hamano]

Eric Wong  writes:

> Ævar Arnfjörð Bjarmason  wrote:
>> See https://public-inbox.org/git/86h8oobl36@phe.ftfl.ca/ for the
>> original report.
>
> Thanks for taking a look at this.  Also https://bugs.debian.org/894997
>
>> --- a/perl/Git.pm
>> +++ b/perl/Git.pm
>> @@ -554,7 +554,7 @@ sub get_record {
>>  my ($fh, $rs) = @_;
>>  local $/ = $rs;
>>  my $rec = <$fh>;
>> -chomp $rec if defined $rs;
>> +chomp $rec if defined $rs and defined $rec;
>
> I'm struggling to understand the reason for the "defined $rs"
> check.  I think it was a braino on my part and meant to use:
>
>   chomp $rec if defined $rec;

That sounds quite plausible, so if there is no further discussion,
let me queue a version that does s/rs/rec/ on that line myself
(bypassing a pull from your repository at bogomips.org/).

Thanks.

Bug#895261: RFS: dbus-broker/11-1 [ITP] -- Linux D-Bus Message Broker

[Daniele Nicolodi]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my "dbus-broker" package

* Package name: dbus-broker
  Version : 11
  Upstream Author : David Herrmann  et al.
* URL : https://github.com/bus1/dbus-broker/
* License : Apache-2.0
  Section : admin
  Programming Lang: C
  Description : Linux D-Bus Message Broker

It builds those binary packages:

  dbus-broker - Linux D-Bus Message Broker

To access further information about this package, please visit the
following URL: https://mentors.debian.net/package/dbus-broker

Alternatively, one can download the package with dget:

  dget -x
https://mentors.debian.net/debian/pool/main/d/dbus-broker/dbus-broker_11-1.dsc

Or from the repository:

  https://salsa.debian.org/dnn-guest/dbus-broker

Cheers,
Dan

Bug#895171: Acknowledgement (enlightenment: No thunderbird icon with scale 1.4 1.45 1.5)

[sergio]

On 08/04/18 23:52, Ross Vandegrift wrote:


Do you have libevas-loaders installed?


Thank you! All works fine after libevas-loaders installation.



--
sergio.

Bug#893523: transition: qtbase-opensource-src

[Lisandro Damián Nicanor Pérez Meyer]

El domingo, 8 de abril de 2018 22:14:42 -03 Lisandro Damián Nicanor Pérez 
Meyer escribió:
> Packages that can be binNMUed without qttools/qtwebkit done:
> 
> deepin-qt5dxcb-plugin fcitx-qt5 gcin gsettings-qt hime qtstyleplugins-src
> telegram-desktop uim xdg-desktop-portal-kde
> 
> If qttools is ready then the whole dependency level 2 can be binNMUed (yes,
> that's the obvious part ;-) )

On a second thought all dependency level 2 can be binNMUed against qtbase 
5.10.1 because the old qttools version won't get installed, so buildds will 
wait for qttools to be done.

-- 
En 1975, a los 99 años, muere Leonor Acevedo de Borges. En el velorio, una
mujer da el pésame a Borges y comenta: "Pobre Leonorcita, morirse tan poquito
antes de cumplir los 100 años. Si hubiera esperado un poquito más...".
Borges responde: "Veo, señora, que es usted devota del sistema decimal".
  Jorge Luis Borges, en "Borges habla de su madre". http://2tu.us/2i7d

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


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

Bug#893523: transition: qtbase-opensource-src

[Lisandro Damián Nicanor Pérez Meyer]

Packages that can be binNMUed without qttools/qtwebkit done:

deepin-qt5dxcb-plugin fcitx-qt5 gcin gsettings-qt hime qtstyleplugins-src 
telegram-desktop uim xdg-desktop-portal-kde

If qttools is ready then the whole dependency level 2 can be binNMUed (yes, 
that's the obvious part ;-) )

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


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

Bug#893515: digikam: FTBFS with kdepim 17.12.2

[Steve Robbins]

On Sunday, April 8, 2018 1:25:42 PM CDT Simon Frei wrote:
> I totally understand that, I am just trying to get infos to you as
> debian maintainer from my (at the moment admittedly almost non-existing)
> involvement upstream. Exiv2 0.26 will likely not get into testing.
> Upstream does backport a lot of security fixes to 0.26, but negated
> creating a dot release on request, and is focussing on 0.27. It was
> planned to release an rc in early 2018, but from what I read in the
> issue tracker, that's not going to happen asap.

Yes, fair enough.   I'm not entirely opposed to patching digikam to accept the 
older exiv2.  That was going to be my Plan B in any case, but you make a good 
case to do it immediately and work on updating exiv2 in parallel.

-S
 


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

Bug#895260: kde-cli-tools: Hard dependency on sudo, which weakens system security

[Alex Hvostov]

Package: kde-cli-tools
Version: 4:5.10.5-2
Severity: important

Dear Maintainer,

kde-cli-tools 4:5.12.4-1 has a hard dependency on kdesu, which
indirectly depends on sudo, making it impossible to upgrade KDE without
creating a serious, unnecessary security risk.

Frankly, I consider it a bug that sudo is available in Debian at all.
Others obviously disagree, but that's no reason to tie unrelated
packages to it like this.

Please move kdesu into its own package, and make it optional again.

In the mean time, others with my concern can mitigate this risk by
neutralizing sudo before installing it. To do that, run the following
command (as root) before installing sudo:

# dpkg-statoverride --add root root 644 /usr/bin/sudo



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

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 kde-cli-tools depends on:
ii  kde-cli-tools-data4:5.10.5-2
ii  kio   5.37.0-2
ii  libc6 2.26-6
ii  libkf5completion5 5.37.0-2
ii  libkf5configcore5 5.37.0-2
ii  libkf5configwidgets5  5.37.0-2
ii  libkf5coreaddons5 5.37.0-3
ii  libkf5i18n5   5.37.0-2
ii  libkf5iconthemes5 5.37.0-2
ii  libkf5kcmutils5   5.37.0-2
ii  libkf5kiocore55.37.0-2
ii  libkf5kiowidgets5 5.37.0-2
ii  libkf5service-bin 5.37.0-2
ii  libkf5service55.37.0-2
ii  libkf5su-bin  5.37.0-2
ii  libkf5su5 5.37.0-2
ii  libkf5widgetsaddons5  5.37.0-2
ii  libkf5windowsystem5   5.37.0-2
ii  libqt5core5a  5.9.2+dfsg-9
ii  libqt5dbus5   5.9.2+dfsg-9
ii  libqt5gui55.9.2+dfsg-9
ii  libqt5svg55.9.2-3
ii  libqt5widgets55.9.2+dfsg-9
ii  libqt5x11extras5  5.9.2-1
ii  libstdc++67.3.0-1
ii  libx11-6  2:1.6.4-3

kde-cli-tools recommends no packages.

kde-cli-tools suggests no packages.

-- no debconf information

Bug#894750: Checking compatibility of add-ons takes forever

[W. Martin Borgert]

On 2018-04-04 13:47, Alex ARNAUD wrote:
> Could you give me the complete list?

xul-ext-itsalltext
xul-ext-scrapbook
xul-ext-ublock-origin
xul-ext-useragentswitcher

> To help us to figure out this issue,
> could you remove all your add-ons, downgrade Firefox and upgrade it? And
> after that, could you tell us if the issue still happen? If no, could you do
> the downgrade of Firefox, install one add-on and upgrade Firefox to check
> which add-on could be the culprit?

Unfortunately, I currently cannot reproduce the behaviour.
The window saying "checking" etc. appears only less than a second now.

(I tested with a separate test account, though, maybe the
behaviour is different because of this.)

Bug#892458: Fwd: [Debian-astro-maintainers] ftools update

[Sam Fowler]

On Wed, 14 Mar 2018 16:22:19 +0100 Ole Streicher  wrote:
> FYI
> 
> 
>  Forwarded Message 
> Subject: [Debian-astro-maintainers] ftools update
> Date: Wed, 14 Mar 2018 10:42:25 -0400
> From: Michael Arida 
> To: debian-astro-maintain...@lists.alioth.debian.org
> 
> 
> Dear Debian Astro Maintainers,
> 
> As you may have noticed CFITSIO was updated Friday (March 2) for a
> major bug fix.  Since you have a software bundle that uses what we
> assume is CFITSIO somewhere under the hood, we wanted to let you know
> that you should update that code.  We are also expecting another
> update in April.
> 
> If you have any questions or concerns, feel free to contact me.
> 
> Regards,
>  Mike Arida
> 
> Michael Arida (ADNET) ASD/HEASARC
> 301.286.2291/1215 (voice/fax)  Code 660, NASA/GSFC
> michael.ar...@nasa.gov Greenbelt, MD 20771
> 
> ___
> Debian-astro-maintainers mailing list
> debian-astro-maintain...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/debian-astro-maintainers

This has been assigned has been assigned CVE-2018-1000166.

Regards,
-- 
Sam Fowler, Red Hat Product Security

Bug#895259: libzstd: FTBFS on riscv64: undefined reference to `__atomic_compare_exchange_1'

[Adam Borowski]

Source: libzstd
Version: 1.3.3+dfsg-1
Severity: normal
Tags: patch
User: debian-ri...@lists.debian.org
Usertags: riscv64

Hi!
Here's a patch to fix FTBFS on riscv64.

Submitted upstream as https://github.com/facebook/zstd/pull/1103, but as
this library has some interesting rbdeps, it'd be nice if you could apply
this without waiting for an official release.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: riscv64

Kernel: Linux 4.16.1+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
--- libzstd-1.3.3+dfsg.orig/contrib/pzstd/Makefile
+++ libzstd-1.3.3+dfsg/contrib/pzstd/Makefile
@@ -50,7 +50,7 @@ GTEST_LIB  = -L googletest/build/googlem
 LIBS   =
 
 # Compilation commands
-LD_COMMAND  = $(CXX) $^  $(ALL_LDFLAGS) $(LIBS) -lpthread -o $@
+LD_COMMAND  = $(CXX) $^  $(ALL_LDFLAGS) $(LIBS) -pthread -o $@
 CC_COMMAND  = $(CC)  $(DEPFLAGS) $(ALL_CFLAGS)   -c $<  -o $@
 CXX_COMMAND = $(CXX) $(DEPFLAGS) $(ALL_CXXFLAGS) -c $<  -o $@
 

Bug#895257: firebird3.0: Please add support for new architecture "riscv64" (RISC-V 64 bits little-endian)

[Manuel A. Fernandez Montecelo]

Source: firebird3.0
Version: 3.0.3.32900.ds4-2
Severity: normal
Tags: patch upstream fixed-upstream
User: debian-ri...@lists.debian.org
Usertags: riscv64

Hello,

We need support in this package for the riscv64 architecture.

There is a patch from upstream:

  
https://github.com/FirebirdSQL/firebird/commit/1e8e7858db84750a77006d307bf28e9686f9414e

It needs some modifications (file attached) to be applied in the current version
of this package in unstable:

  + removed hunk fixing typo in "encyption", fixed separately (in another
patch of the series applied to the package in Debian)
  + removed extra tab in the second line after "backEndianess" (there are
only two tabs before the last character, a '1' in the line; in the
patch from upstream there are 3, so lines don't match)
  + fixed whitespace in the hunk for configure.ac
  + refresh

The build didn't finish yet, we will confirm later when it works, or will send
further fixes.

It would be great if, upon confirmation that it works, you could include it as a
patch and release a new version for unstable as soon as possible, since there
are very important packages depending on this package (php7, graphviz on php7,
and many packages needing graphviz for their documentation).

If you need any assistance, please let me/us know.


Thanks and cheers.
--
Manuel A. Fernandez Montecelo 
>From 1e8e7858db84750a77006d307bf28e9686f9414e Mon Sep 17 00:00:00 2001
From: AlexPeshkoff 
Date: Wed, 21 Mar 2018 15:19:20 +0300
Subject: [PATCH] Patch for CORE-5779: support for riscv64, also some code
 fixes related with prior ports

---
 configure.ac| 12 
 src/common/classes/DbImplementation.cpp | 29 -
 src/common/common.h |  4 
 src/include/gen/msgs.h  |  2 +-
 src/jrd/inf_pub.h   |  2 +-
 5 files changed, 34 insertions(+), 15 deletions(-)

--- a/configure.ac
+++ b/configure.ac
@@ -251,6 +251,18 @@
 libdir=/usr/lib64
 ;;
 
+  riscv64*-*-linux*)
+MAKEFILE_PREFIX=linux_riscv64
+INSTALL_PREFIX=linux
+PLATFORM=LINUX
+AC_DEFINE(LINUX, 1, [Define this if OS is Linux])
+EDITLINE_FLG=Y
+SHRLIB_EXT=so
+STD_EDITLINE=true
+STD_ICU=true
+libdir=/usr/lib64
+;;
+
   powerpc64le-*-linux*)   
 MAKEFILE_PREFIX=linux_powerpc64el
 INSTALL_PREFIX=linux
--- a/src/common/classes/DbImplementation.cpp
+++ b/src/common/classes/DbImplementation.cpp
@@ -49,6 +49,7 @@
 static const UCHAR CpuArm64 = 15;
 static const UCHAR CpuPowerPc64el = 16;
 static const UCHAR CpuM68k = 17;
+static const UCHAR CpuRiscV64 = 18;
 
 static const UCHAR OsWindows = 0;
 static const UCHAR OsLinux = 1;
@@ -89,7 +90,8 @@
"Alpha",
"ARM64",
"PowerPC64el",
-   "M68k"
+   "M68k",
+   "RiscV64"
 };
 
 const char* operatingSystem[] = {
@@ -116,22 +118,23 @@
 // This table lists pre-fb3 implementation codes
 const UCHAR backwardTable[FB_NELEM(hardware) * FB_NELEM(operatingSystem)] =
 {
-// Intel   AMD Sparc   PPC 
PPC64   MIPSEL  MIPSARM IA64s390s390x   SH  
SHEBHPPAAlpha   ARM64   PowerPC64el
-/* Windows */  50, 68, 0,  0,  
0,  0,  0,  0,  0,  
0,  0,  0,  0,  0,  
0,  0,  0,
-/* Linux */60, 66, 65, 69, 
86, 71, 72, 75, 76, 
79, 78, 80, 81, 82, 83, 
84, 85,
-/* Darwin */   70, 73, 0,  63, 
77, 0,  0,  0,  0,  
0,  0,  0,  0,  0,  
0,  0,  0,
-/* Solaris */  0,  0,  30, 0,  
0,  0,  0,  0,  0,  
0,  0,  0,  0,  0,  
0,  0,  0,
-/* HPUX */ 0,  0,  0,  0,  
0,  0,  0,  0,  0,  
0,  0,  0,  0,  31, 
0,  0,  0,
-/* AIX */  0,  0,  0,  
35, 0,  0,  0,  0,  
0,  0,  0,  0,  0,  
0,  0,  0,  

Bug#895258: installation-reports: installer fails to report missing NIC firmware

[Celejar]

Package: installation-reports
Severity: important
Tags: d-i

Dear Maintainer,

The installation went mostly okay, except that I spent a while quite
frustrated with mysterious network configuration failures. I assumed that
the problem was with my cabling or DHCP configuration, until it finally
occurred to me to check the logs (with Alt+F4), where I discovered that
my new R210 II's NICs [Broadcom Limited NetXtreme II BCM5716 Gigabit
Ethernet (rev 20), driven by the bnx2 driver] required non-free
firmware, which the installer could not provide.

I am perfectly satisfied with the Debian policy to not include such
firmware in the installer, but the user should be notified in this case,
and not simply be provided with the almost useless message "Network
configuration failure". The logs make the problem very clear, but the
main installer screen doesn't provide even a hint about the real issue.

Thanks, however, for the greatness that is Debian!

-- Package-specific info:

Boot method: usb flash drive
Image version: 9.3, 9.4 netinstall images
Date: 

Machine: Dell PowerEdge R210 II

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O ]
Detect network card:[O ]
Configure network:  [E ]
Detect CD:  [O ]
Load installer modules: [O ]
Clock/timezone setup:   [O ]
User/password setup:[O ]
Detect hard drives: [ O]
Partition hard drives:  [ O]
Install base system:[ O]
Install tasks:  [ O]
Install boot loader:[ O]
Overall install:[ E]

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20170615+deb9u3"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux alice 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 
Processor Family DRAM Controller [8086:0108] (rev 09)
lspci -knn: Subsystem: Dell Device [1028:04dd]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
lspci -knn: Subsystem: Dell Device [1028:04dd]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04)
lspci -knn: Subsystem: Dell Device [1028:04dd]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev a4)
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation C202 Chipset Family 
LPC Controller [8086:1c52] (rev 04)
lspci -knn: Subsystem: Dell Device [1028:04dd]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 
Series Chipset Family SATA AHCI Controller [8086:1c02] (rev 04)
lspci -knn: Subsystem: Dell Device [1028:04dd]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series 
Chipset Family SMBus Controller [8086:1c22] (rev 04)
lspci -knn: Subsystem: Dell Device [1028:04dd]
lspci -knn: 01:00.0 Ethernet controller [0200]: Broadcom Limited NetXtreme II 
BCM5716 Gigabit Ethernet [14e4:163b] (rev 20)
lspci -knn: Subsystem: Dell Device [1028:04dd]
lspci -knn: Kernel driver in use: bnx2
lspci -knn: Kernel modules: bnx2
lspci -knn: 01:00.1 Ethernet controller [0200]: Broadcom Limited NetXtreme II 
BCM5716 Gigabit Ethernet [14e4:163b] (rev 20)
lspci -knn: Subsystem: Dell Device [1028:04dd]
lspci -knn: Kernel driver in use: bnx2
lspci -knn: Kernel modules: bnx2
lspci -knn: 02:03.0 VGA compatible controller [0300]: Matrox Electronics 
Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
lspci -knn: Subsystem: Dell Device [1028:04dd]
usb-list: 
usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.9.0-6-amd64 ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 01 Device 02: EHCI Host Controller [8087:0024]
usb-list:Level 01 Parent 01 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 01 Device 03: USB Composite Device-0 

Bug#857351: Pending fixes for bugs in the jabref package

[pkg-java-maintainers]

tag 857351 + pending
thanks

Some bugs in the jabref package are closed in revision
1b8b418f78c66e8650c30f0c4e6edf0cd69e1f3f in branch 'master' by tony
mancill

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

Commit message:

Apply upstream patch for file perms (Closes: #857351)

Bug#895256: WARN Could not locate file AUTHORS/DOCUMENTERS/LICENSE

[Laurent Bigonville]

Package: gnucash
Version: 1:3.0-1
Severity: normal

Hi,

When opening the about dialog, I see the following message in
/tmp/gnucash.trace:

* 00:50:59  WARN  Could not locate file AUTHORS
* 00:50:59  WARN  Could not locate file DOCUMENTERS
* 00:50:59  WARN  Could not locate file LICENSE

Using strace, I see:

stat("/usr/share/doc/gnucash/AUTHORS", 0x7ffc306a0870) = -1 ENOENT (No such 
file or directory)
stat("/usr/share/doc/gnucash/DOCUMENTERS", 0x7ffc306a0870) = -1 ENOENT (No such 
file or directory)
stat("/usr/share/doc/gnucash/LICENSE", 0x7ffc306a0890) = -1 ENOENT (No such 
file or directory)

Problem seems to be a mix of missing file and a compressed one

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages gnucash depends on:
ii  gnucash-common   1:3.0-1
ii  guile-2.22.2.3+1-3
ii  guile-2.2-libs   2.2.3+1-3
ii  libaqbanking35   5.7.8-1
ii  libaqbanking35-plugins   5.7.8-1
ii  libatk1.0-0  2.28.1-1
ii  libboost-date-time1.62.0 1.62.0+dfsg-5
ii  libboost-filesystem1.62.01.62.0+dfsg-5
ii  libboost-locale1.62.01.62.0+dfsg-5
ii  libboost-regex1.62.0 1.62.0+dfsg-5
ii  libboost-system1.62.01.62.0+dfsg-5
ii  libc62.27-3
ii  libcairo-gobject21.15.10-2
ii  libcairo21.15.10-2
ii  libcrypt-ssleay-perl 0.73.06-1
ii  libdate-manip-perl   6.70-1
ii  libdbi1  0.9.0-5
ii  libfinance-quote-perl1.47-1
ii  libfribidi0  0.19.7-2
ii  libgc1c2 1:7.4.2-8.2
ii  libgcc1  1:8-20180402-1
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.0-6
ii  libgtk-3-0   3.22.29-3
ii  libgwenhywfar60  4.20.0-1
ii  libhtml-tableextract-perl2.15-1
ii  libhtml-tree-perl5.07-1
ii  libicu57 57.1-9
ii  libjavascriptcoregtk-4.0-18  2.20.0-2
ii  libktoblzcheck1v51.49-4
ii  libofx7  1:0.9.12-1
ii  libpango-1.0-0   1.42.1-1
ii  libpangocairo-1.0-0  1.42.1-1
ii  libsoup2.4-1 2.62.0-1
ii  libstdc++6   8-20180402-1
ii  libwebkit2gtk-4.0-37 2.20.0-2
ii  libwww-perl  6.33-1
ii  libxml2  2.9.4+dfsg1-6.1
ii  libxslt1.1   1.1.29-5
ii  perl 5.26.1-5
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages gnucash recommends:
ii  gnucash-docs 2.6.19-1
ii  python3-gnucash  1:3.0-1
ii  yelp 3.28.0-1

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

-- no debconf information

Bug#845938: pulseaudio: bt headset: a2dp sink is not selectable - only hsp/hfp works

[Stefan Monnier]

> This is still an issue in Debian stretch: the gdm3 package runs
> pulseaudio, which takes over the bluetooth device and makes it
> impossible for regular users to connect to their bluetooth device
> using the hifi A2DP sink.  See #805414 for more details on that
> side.  There's a workaround for gdm3 (disabling the BT sink in gdm), so
> I'll leave that aside for now and focus on the basic issue here.

The problem is not limited to GDM, tho.

If you have several users logged in at the same time, only one of them
gets to use the bluetooth speaker, and once he gets it, the only way to
"free" the speaker (so another user can use it) seems to be to kill that
user's pulseaudio daemon.

The worst part is that the bluetooth speaker can easily get awarded to
a user who hasn't actually played any sound at all.

Currently, I work around this by manually removing bluetooth from the
pulseaudio config of all users except for the lucky one who is "more
deserving".  But it's a real PITA.


Stefan

Bug#894917: procps: pgrep -u UID segfaults

[Craig Small]

The bug is actually worse than this. Any time pgrep is run without a
process name and it matches nothing it segfaults.

The fix is a one liner already applied upstream.

 - Craig

-- 
Craig Small https://dropbear.xyz/ csmall at : dropbear.xyz
Debian GNU/Linuxhttps://www.debian.org/   csmall at : debian.org
Mastodon: @smalls...@social.dropbear.xyz Twitter: @smallsees
GPG fingerprint:  5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

Bug#895255: gnuradio: grcc: ImportError: No module named _runtime_swig

[Vasil Velichkov]

Package: gnuradio
Version: 3.7.11-8
Severity: normal

Dear Maintainer,

grcc always fails with the following error

# grcc 
Traceback (most recent call last):
  File "/usr/bin/grcc", line 29, in 
from gnuradio import gr
  File "/usr/lib/python2.7/dist-packages/gnuradio/gr/__init__.py", line 41, 
in 
from runtime_swig import *
  File "/usr/lib/python2.7/dist-packages/gnuradio/gr/runtime_swig.py", line 
17, in 
_runtime_swig = swig_import_helper()
  File "/usr/lib/python2.7/dist-packages/gnuradio/gr/runtime_swig.py", line 
16, in swig_import_helper
return importlib.import_module('_runtime_swig')
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
ImportError: No module named _runtime_swig

It's because libvolk.so.1.3 could not be found

# ldd 
/usr/lib/python2.7/dist-packages/gnuradio/gr/_runtime_swig.x86_64-linux-gnu.so 
linux-vdso.so.1 (0x7ffe651fe000)
libpython2.7.so.1.0 => /lib/x86_64-linux-gnu/libpython2.7.so.1.0 
(0x7ffa79dce000)
libgnuradio-runtime.so.3.7.11 => 
/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.7.11 (0x7ffa79ada000)
liblog4cpp.so.5 => /lib/x86_64-linux-gnu/liblog4cpp.so.5 
(0x7ffa7989c000)
libgnuradio-pmt.so.3.7.11 => 
/lib/x86_64-linux-gnu/libgnuradio-pmt.so.3.7.11 (0x7ffa79648000)
libvolk.so.1.3 => not found
libboost_date_time.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_date_time.so.1.62.0 (0x7ffa79437000)
libboost_program_options.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_program_options.so.1.62.0 (0x7ffa791b6000)
libboost_filesystem.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7ffa78f9d000)
libboost_system.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7ffa78d99000)
libboost_regex.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_regex.so.1.62.0 (0x7ffa78a83000)
libboost_thread.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_thread.so.1.62.0 (0x7ffa7885b000)
libboost_chrono.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_chrono.so.1.62.0 (0x7ffa78654000)
libboost_atomic.so.1.62.0 => 
/lib/x86_64-linux-gnu/libboost_atomic.so.1.62.0 (0x7ffa7845)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ffa78232000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7ffa7802a000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7ffa77ca5000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ffa77912000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7ffa776fa000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ffa7733e000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7ffa77124000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ffa76f2)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7ffa76d1d000)
libvolk.so.1.3 => not found
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7ffa76b05000)
libicudata.so.57 => /lib/x86_64-linux-gnu/libicudata.so.57 
(0x7ffa75086000)
libicui18n.so.57 => /lib/x86_64-linux-gnu/libicui18n.so.57 
(0x7ffa74c12000)
libicuuc.so.57 => /lib/x86_64-linux-gnu/libicuuc.so.57 
(0x7ffa7486d000)
/lib64/ld-linux-x86-64.so.2 (0x55e9a390e000)


# dpkg -L libvolk1.3
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libvolk.so.1.3.1

A simple rebuild of gnuradio with libvolk1.3 1.3.1-1 should fix the problem

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

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

Versions of packages gnuradio depends on:
ii  libasound21.1.3-5
ii  libboost-atomic1.62.0 1.62.0+dfsg-5
ii  libboost-chrono1.62.0 1.62.0+dfsg-5
ii  libboost-date-time1.62.0  1.62.0+dfsg-5
ii  libboost-filesystem1.62.0 1.62.0+dfsg-5
ii  libboost-program-options1.62.01.62.0+dfsg-5
ii  libboost-regex1.62.0  1.62.0+dfsg-5
ii  libboost-system1.62.0 1.62.0+dfsg-5
ii  libboost-thread1.62.0 1.62.0+dfsg-5
ii  libc6 2.27-3
ii  libcodec2-0.7 0.7-1
ii  libcomedi00.10.2-4+b5
ii  libfftw3-single3  3.3.7-1
ii  libgcc1   1:8-20180402-1
ii  libgnuradio-analog3.7.11  3.7.11-8
ii  libgnuradio-atsc3.7.113.7.11-8
ii  libgnuradio-audio3.7.11   3.7.11-8
ii  libgnuradio-blocks3.7.11  3.7.11-8
ii  libgnuradio-channels3.7.113.7.11-8

Bug#742025: network-manager-gnome: Systray icon too small

[Christophe Troestler]

On  8 April 2018 at 16:45 GMT, Michael Biebl wrote:
>
> Control: tags -1 + moreinfo
>
> On Tue, 18 Mar 2014 14:11:46 +0100 Christophe Troestler
>  wrote:
>> Package: network-manager-gnome
>> Version: 0.9.8.4-1
>> Severity: normal
>> 
>> Dear Maintainer,
>> 
>> When starting nm-applet
>> 
>> pkill nm-applet
>> nm-applet &
>> 
>> the systray icon (in fluxbox) is too small (see nm_small.png attached).
>> If I restart the network manager
>> 
>> /etc/init.d/network-manager restart
>> 
>> the icon has its normal size (see nm.png attached).
>
> Is this still an issue on an up-to-date stretch or sid system?
> If so, what tray application do you use?

I'm not using fluxbox anymore.

Bug#877799: groovy: GCJ java.lang.ArrayIndexOutOfBoundsException

[Emmanuel Bourg]

Control: tags -1 + wontfix
Control: close -1

GCJ is gone.

Bug#880516:

[Scarlett Clark]

Control: retitle -1 *ITP: qtscxml-opensource-src -- Qt module for
creating state machines from SCXML files*

Bug#895253: ITP: elisa -- Simple music player with a focus on Plasma desktop integration and privacy

[Adam Borowski]

On Sun, Apr 08, 2018 at 11:47:54PM +0200, Adam Borowski wrote:
> On Sun, Apr 08, 2018 at 11:34:29PM +0200, Aurélien COUDERC wrote:
> > * Package name: elisa
> > * URL : https://community.kde.org/Elisa
> >   Description : Simple music player with a focus on Plasma desktop
> > integration and privacy
> [...]
> >  Elisa is developed using modern KDE technologies and aims to be reliable
> >  and respectful of users’ privacy. As such, it favors online services where
> >  users are in control of their data.
> 
> While I need online music services about as much as I need an additional
> hole in the head, this raises a good point: why do music players shipped in
> Debian default to grabbing lyrics, "LastFM stats", tags, and what not, even
> when playing local media?

Just to make this more obvious: this is not a dig on _elisa_, this is a dig
on everything else.

As for elisa, it would be nice if you could make it obvious what the
upstream writes: that online services are not a development priority -- this
player is supposed to be good for offline music, which is exactly what I
want.  The current description makes it seem to be a tool for online stuff
_only_, merely with some respect for privacy.

(Re-added CC to the bug -- wrt my wish for the description.)


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ 
⢿⡄⠘⠷⠚⠋⠀ ... what's the frequency of that 5V DC?
⠈⠳⣄

Bug#895254: pacpl: Fails to convert wma (asf) files

[Javier Barroso]

Package: pacpl
Version: 5.1.0-1
Severity: normal

Please apply (at Debian, because the upstream is against the patch
(which is working at least for me)), the patch located at bug
https://sourceforge.net/p/pacpl/bugs/18/

Thanks you !

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

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

Versions of packages pacpl depends on:
ii  libaudio-flac-header-perl 2.4-3
ii  libaudio-scan-perl0.99-1
ii  libcddb-get-perl  2.28-2
ii  libcddb-perl  1.222-1
ii  libmp3-tag-perl   1.13-1.1
ii  libparallel-forkmanager-perl  1.19-1
ii  perl  5.26.1-5
ii  vorbis-tools  1.4.0-10.1

Versions of packages pacpl recommends:
ii  cdparanoia3.10.2+debian-13
ii  faad  2.8.8-1
ii  ffmpeg7:3.4.2-1+b1
ii  flac  1.3.2-1
ii  lame  3.100-2
ii  mplayer   2:1.3.0-7+b3
ii  musepack-tools2:0.1~r495-1+b1
ii  normalize-audio   0.7.7-14+b1
ii  opus-tools0.1.10-1
ii  sndfile-programs  1.0.28-4
ii  sox   14.4.2-3
ii  speex 1.2~rc1.2-1+b2
ii  wavpack   5.1.0-2

Versions of packages pacpl suggests:
pn  faac 
pn  flake
pn  twolame  

-- no debconf information

Bug#870835: ddraw is Windows-only

[Adam Borowski]

> I changed the output value from surface to ddraw (listed in the comments,
> I'm sure it's not a mispelling) and launched dosbox.  Instead of running
> as expected, I receive the error:
>
> "ddraw" is not a valid value for variable: output.
> It might now be reset it to default value: surface.
>
> I have the same version of dosbox on a windows machine and it accepts
> "ddraw" as an output value with no problem.  I don't know why it'd do
> this, but it's certainly not an expected (and desired) behaviour.

DirectDraw is an ancient (and since removed) part of DirectX, Microsoft's
Windows-only (well, emulated on Wine too) proprietary API.  There are
multiple portable or Unix-only APIs, DirectDraw is not one of them.

It's gone even from Windows: it was last released with DirectX 7, it's gone
even from Microsoft's headers since 2010.  You can still install the library
on new Windows, but your mileage may wary.

Thus, ddraw not being present on Linux is not an error.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ 
⢿⡄⠘⠷⠚⠋⠀ ... what's the frequency of that 5V DC?
⠈⠳⣄

Bug#895175: lintian: Argument "Users" isn't numeric in int at ...

[Chris Lamb]

tags 895175 + pending
thanks

Fixed in Git, pending upload:

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

This was due to a space in the orig tarball permissions:

   -rw-r--r-- dowling/ANT\Domain Users667 2015-09-09 18:32 
guzzle_sphinx_theme-0.7.11/setup.py

Our call to split (ie.):

  ($perm,$ownership,$size,$date,$time,$name)=split(' ', $line, 6);

... then sets $ownership to "dowling/ANT\Domain" and $size to "Users".

There is no foolproof fix here as long as we are still relying on the
output of tar; even if we allow arbitrary spaces here, you can still
"inject" date-like strings into the filename. Or maybe we could use
tar's --quoting-style argument...


Regards,

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

Bug#826994: [Pkg-zfsonlinux-devel] Bug#826994: Updated Patch for 0.7.6-1

[Chris Dos]

On 04/08/2018 12:37 AM, Aron Xu wrote:
> Hi,
> 
> This patch modifies upstream source code directly which is undesired.
> Would you mind to submit the change upstream?
> 
> 
> Regards,
> Aron Xu
> 

Bug report opened for ZFSonLinux upstream:
https://github.com/zfsonlinux/zfs/issues/7412

Chris

Bug#895253: ITP: elisa -- Simple music player with a focus on Plasma desktop integration and privacy

[Aurélien COUDERC]

Package: wnpp
Severity: wishlist
Owner: Aurélien COUDERC 

* Package name: elisa
  Version : 0.1
  Upstream Author : KDE Community
* URL : https://community.kde.org/Elisa
* License : GPL-3 with Qt exception, LGPL-3
  Programming Lang: C++, QML
  Description : Simple music player with a focus on Plasma desktop
integration and privacy

 Elisa is a music player developed by the KDE community that strives to be
 simple and nice to use. It tries to be flexible to account for different
 workflows and use-cases. It focuses on a very good integration with the
 Plasma desktop of the KDE community without compromising the support for
 other environments.
 .
 Elisa is developed using modern KDE technologies and aims to be reliable
 and respectful of users’ privacy. As such, it favors online services where
 users are in control of their data.

Bug#895252: dosbox: tiny image even on lowDPI (scalers only up to x3)

[Adam Borowski]

Package: dosbox
Version: 0.74-4.3
Severity: normal
Tags: patch


Hi!
For historic reasons, scalers are limited only to x3.  Upstream's logic was
that there's no way software scaling could manage a bigger resolution while
still having an acceptable frame rate.

But that was over an decade ago.  Since then, monitors below 1920x1080 don't
really exist, and even crummiest ARM SoCs available for purchase today can
handle that size well.  On the other hand, driver support for OpenGL for
such machines tends to be inexistant.

On DosBox's website, one of forum threads includes a patch to add normal4x,
normal5x and normal6x scalers.  This patch makes the output work well:
320x200 times five is 1600x1000, which fits within a 1920x1080 area.  In
this case, not stretching too much horizontally is good: most modern
monitors and TVs have extremely bad aspect ratios such as 16x9; the typical
DOS resolution of 320x200 already has non-square pixels but distorting them
to square happens to be a reasonable compromise between keeping shapes and
not wasting too much screen area.  For those who want accurate proportions,
DosBox has aspect control.

Tested by sister's rugrats on some random big TV, using my Pine64: normal5x
works fine, trying to emulate OpenGL results in a slideshow.

Patch attached, all I've done was to fix whitespace.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 4.16.0-00199-ge68d78e24cde (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dosbox depends on:
ii  libasound2   1.1.3-5
ii  libc62.27-3
ii  libgcc1  1:8-20180402-1
ii  libgl1   1.0.0+git20180308-1
ii  libpng16-16  1.6.34-1
ii  libsdl-net1.21.2.8-5
ii  libsdl-sound1.2  1.0.3-8
ii  libsdl1.2debian  1.2.15+dfsg2-0.1
ii  libstdc++6   8-20180402-1
ii  libx11-6 2:1.6.5-1
ii  zlib1g   1:1.2.8.dfsg-5

dosbox recommends no packages.

dosbox suggests no packages.

-- no debconf information
>From fa28854405684f179ae34fe8b85e4c14532e7f28 Mon Sep 17 00:00:00 2001
From: Adam Borowski 
Date: Fri, 30 Mar 2018 23:13:50 +0200
Subject: [PATCH] allow scaling 4x, 5x, 6x (normal scaler only)

Patch origin: https://www.vogons.org/viewtopic.php?f=41=43899
---
 src/dosbox.cpp |   2 +-
 src/gui/render.cpp |  19 
 src/gui/render_scalers.cpp | 119 ++
 src/gui/render_scalers.h   |   7 ++
 src/gui/render_simple.h|  36 +++
 src/gui/render_templates.h | 199 +
 6 files changed, 381 insertions(+), 1 deletion(-)

diff --git a/src/dosbox.cpp b/src/dosbox.cpp
index a4bf564..fdc3064 100644
--- a/src/dosbox.cpp
+++ b/src/dosbox.cpp
@@ -381,7 +381,7 @@ void DOSBOX_Init(void) {
Pstring = 
Pmulti->GetSection()->Add_string("type",Property::Changeable::Always,"normal2x");
 
const char *scalers[] = { 
-   "none", "normal2x", "normal3x",
+   "none", "normal2x", "normal3x", "normal4x", "normal5x", 
"normal6x",
 #if RENDER_USE_ADVANCED_SCALERS>2
"advmame2x", "advmame3x", "advinterp2x", "advinterp3x", "hq2x", 
"hq3x", "2xsai", "super2xsai", "supereagle",
 #endif
diff --git a/src/gui/render.cpp b/src/gui/render.cpp
index 1ba6097..682a94b 100644
--- a/src/gui/render.cpp
+++ b/src/gui/render.cpp
@@ -288,6 +288,12 @@ static void RENDER_Reset( void ) {
simpleBlock = 
else if (render.scale.size == 3)
simpleBlock = 
+   else if (render.scale.size == 4)
+   simpleBlock = 
+   else if (render.scale.size == 5)
+   simpleBlock = 
+   else if (render.scale.size == 6)
+   simpleBlock = 
else
simpleBlock = 
/* Maybe override them */
@@ -348,8 +354,18 @@ static void RENDER_Reset( void ) {
}
 #endif
} else if (dblw) {
+   if ((render.scale.size == 2) && (render.scale.forced))
+   simpleBlock = 
+   else if ((render.scale.size == 3) && (render.scale.forced))
+   simpleBlock = 
+   else
simpleBlock = 
} else if (dblh) {
+   if ((render.scale.size == 2) && (render.scale.forced))
+   simpleBlock = 
+   else if ((render.scale.size == 3) && (render.scale.forced))
+   simpleBlock = 
+   else
simpleBlock = 
} else  {
 forcenormal:
@@ -597,6 +613,9 @@ void RENDER_Init(Section * sec) {
if (scaler == "none") { render.scale.op = 

Bug#895236: Pending fixes for bugs in the maven-javadoc-plugin package

[pkg-java-maintainers]

tag 895236 + pending
thanks

Some bugs in the maven-javadoc-plugin package are closed in revision
b61bd254e6fef9a6558f1d383bffc29085bdbc9a in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/maven-javadoc-plugin.git/commit/?id=b61bd25

Commit message:

Modified the patches to work with Java 9 or later (Closes: #895236)

Bug#895171: Acknowledgement (enlightenment: No thunderbird icon with scale 1.4 1.45 1.5)

[Ross Vandegrift]

On Sun, Apr 08, 2018 at 07:27:32AM +0300, sergio wrote:
> Same for pavucontrol.

Both work for me.  Do you have libevas-loaders installed?  What versions of
libeina1a and thunderbird packages?

Thanks,
Ross

Bug#894605: systemd: System fails to suspend.

[Michael Biebl]

Control: tags -1 + moreinfo

Am 02.04.2018 um 23:37 schrieb Michael Biebl:
> Am 02.04.2018 um 10:20 schrieb Hubert Golembiowski:
>> Package: systemd
>> Version: 238-3
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> Following issue observed:
>> - Select "Suspend" from UI or close laptop lid (closing lid is set to trigger
>> suspend)
>> - System doesn't suspend but instead:
>> - screen goes blank
>> - keyboard stops to take input
>> - pc is still running (fans, leds are on, etc.)
>> - The only way to get out if that state is hard reset
>> - This used to work without any problem, issue appeared 4-5 days ago
> 
> What happens if you run (as root)
> echo "mem" > /sys/power/state
> 
> Did you upgrade other packages the last couple of days, like say the
> kernel? Does the failure to suspend correlate with a certain package update?

Ping




signature.asc
Description: OpenPGP digital signature

Bug#895239: [systemd] suspend works 1st time

[Michael Biebl]

Am 08.04.2018 um 19:56 schrieb Ted To:
> Package: systemd
> Version: 232-25+deb9u3
> Severity: important
> 
> --- Please enter the report below this line. ---
> 
> Suspend only works first time.  It worked fine on an ancient Acer Aspire
> One.  Now on an Acer S7 392, suspend works on its first try but
> afterwards fails.  Currently running the backports kernel but didn't
> work with stable either.

If you simply run (as root)
echo mem > /sys/power/state

can you suspend/resume multiple times?

If not, it's most likely a kernel problem and not a systemd problem.





signature.asc
Description: OpenPGP digital signature

Bug#894770: [becker...@gmail.com: Bug#894769: Java error message and permission on serial port]

[Geert Stappers]

now in this bugreport

- Forwarded message from becker...@gmail.com -

Date: Sun, 08 Apr 2018 19:12:56 +0200
From: becker...@gmail.com
To: 894...@bugs.debian.org
Subject: Bug#894769: Java error message and permission on serial port

Hi,

I have the same issue, this is what I've found so far:

- after plugging in the Arduino and starting the IDE, the status line reports 
the correct 
settings (board type and serial device selected in a previous session)

- just klicking on the 'Tools' menu throws the error message:
java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver

- the user running the Arduino IDE is in the dialout group, I tried if chmod 
666 on the serial 
device would help but it didn't

- tried to send a sketch to the Arduino, this produced the following two lines  
repeatedly:

java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver
PORTS {} / {} => {}

then followed by:

processing.app.debug.RunnerException: Couldn???t find a Leonardo on the 
selected port. 
Check that you have the correct port selected.  If it is correct, try pressing 
the board's reset 
button after initiating the upload.
at 
processing.app.debug.AvrdudeUploader.uploadViaBootloader(AvrdudeUploader.java:154)
at 
processing.app.debug.AvrdudeUploader.uploadUsingPreferences(AvrdudeUploader.java:67)
at processing.app.Sketch.upload(Sketch.java:1671)
at processing.app.Sketch.exportApplet(Sketch.java:1627)
at processing.app.Sketch.exportApplet(Sketch.java:1599)
at processing.app.Editor$DefaultExportHandler.run(Editor.java:2380)
at java.base/java.lang.Thread.run(Thread.java:844)


-- System Information: 


- End forwarded message -


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#666743: draft implementation for a Multi-Arch: foreign interface to gcc

[Helmut Grohne]

Control: reopen -1
Control: reassign -1 src:gcc-8

Hi Matthias,

you requested that I send my unfinished work and here it goes. I've seen
that you have quickly applied my previous patches towards this matter
and would like to thank you. The attached patch was last tested on
8-20180402-1.  I performed the following test methods thus far:
 * native build (reduced using nolang=...)
 * lintian
 * piuparts
 * looking at package contents
 * manually installing and testing the resulting packages (thus
   discovering #891289)

Caveats:
 * The patch still contains temporary Breaks/Replaces versions. You'll
   find them by searching for /0TODO/ in debian/control.m4. These need
   to be updated before uploading (as we are moving files to new
   packages).
 * You'll go through NEW of course.
 * I did not perform cross builds or cross compiler builds.
 * I did not perform non-dfsg builds.
 * I did not perform gcc-snapshot builds.

I had to make a number of bike coloring decision during the
implementation. If you want something different, I'm happy to change
that and will try to update the patch in a timely manner.
 * "arch_gnutype_map" gets passed to control.m4 as "ARCH_GNUTYPE_MAP".
 * The target suffix of the new packages is passed as a substvar called
   "target:suffix".
 * The make variables for these packages are called "p_${tool}n" and
   "d_${tool}n".
 * The new targets are called "$(binary_stamp)-$(tool)-nat".

I would like to thank James Clarke his advice during the planning stage
and for reviewing an earlier version of this patch.

I'd also be interested in learning which test build configurations are
particularly relevant to you.

I'v Cced d-cross@l.d.o to have more eyeballs on this difficult piece of
code.

Helmut
--- a/debian/control.m4
+++ b/debian/control.m4
@@ -35,6 +35,13 @@
 '))
 define(`TARGET_PACKAGE',`X-DH-Build-For-Type: target
 ')
+define(`_for_each',`ifelse(`$3',`',`',`pushdef(`$1',`$3')$2`'popdef(`$1')`'$0(`$1',`$2',shift(shift(shift($@')')
+define(`for_each_arch',`_for_each(`_arch',`dnl
+pushdef(`arch_deb',`patsubst(_arch,`=.*',`')')dnl
+pushdef(`arch_gnu',`patsubst(_arch,`.*=',`')')dnl
+pushdef(`arch_gnusuffix',`-patsubst(arch_gnu,`_',`-')')dnl
+$1`'popdef(`arch_gnusuffix')popdef(`arch_gnu')popdef(`arch_deb')',dnl
+patsubst(ARCH_GNUTYPE_MAP,`\s+',`,'))')
 
 divert`'dnl
 dnl --
@@ -700,21 +707,22 @@
 ')`'dnl x32dev
 ')`'dnl cdev
 
-ifenabled(`cdev',`
-Package: gcc`'PV`'TS
-Architecture: any
-ifdef(`TARGET',`Multi-Arch: foreign
-')dnl
+ifenabled(`cdev',`dnl
+for_each_arch(`
+Package: gcc`'PV`'arch_gnusuffix
+Architecture: ifdef(`TARGET',`any',arch_deb)
+Multi-Arch: foreign
 Section: devel
 Priority: optional
-Depends: cpp`'PV`'TS (= ${gcc:Version}),ifenabled(`gccbase',` BASEDEP,')
+Depends: cpp`'PV`'arch_gnusuffix (= ${gcc:Version}),ifenabled(`gccbase',` BASEDEP,')
   ifenabled(`gccxbase',` BASEDEP,')
   ${dep:libcc1},
-  binutils`'TS (>= ${binutils:Version}),
+  binutils`'arch_gnusuffix (>= ${binutils:Version}),
   ${dep:libgccdev}, ${shlibs:Depends}, ${misc:Depends}
 Recommends: ${dep:libcdev}
-Replaces: gccgo-8 (<< ${gcc:Version}), cpp`'PV`'TS (<< 7.1.1-8)
-Suggests: ${gcc:multilib}, gcc`'PV-doc (>= ${gcc:SoftVersion}),
+Replaces: gccgo-8 (<< ${gcc:Version}), cpp`'PV`'arch_gnusuffix (<< 7.1.1-8), gcc`'PV (<< 999:0TODO)
+Breaks: cpp`'PV (<< 0TODO)
+Suggests: gcc`'PV-doc (>= ${gcc:SoftVersion}),
  gcc`'PV-locales (>= ${gcc:SoftVersion}),
  libdbgdep(gcc`'GCC_SO-dbg,,>=,${libgcc:Version}),
  libdbgdep(gomp`'GOMP_SO-dbg,),
@@ -729,15 +737,44 @@
 ')`'dnl
  libdbgdep(mpx`'MPX_SO-dbg,),
  libdbgdep(quadmath`'QMATH_SO-dbg,)
-Provides: c-compiler`'TS
+Provides: c-compiler`'arch_gnusuffix
 ifdef(`TARGET',`Conflicts: gcc-multilib
 ')`'dnl
 BUILT_USING`'dnl
-Description: GNU C compiler`'ifdef(`TARGET)',` (cross compiler for TARGET architecture)', `')
+Description: GNU C compiler for the arch_gnu architecture
+ This is the GNU C compiler for the arch_gnu architecture, a fairly portable
+ optimizing compiler for C.
+')`'dnl for_each_arch
+ifdef(`TARGET',`',`
+Package: gcc`'PV
+Architecture: any
+Section: devel
+Priority: optional
+Depends: gcc`'PV`'${target:suffix} (= ${gcc:Version}),ifenabled(`gccbase',` BASEDEP,')
+  ifenabled(`gccxbase',` BASEDEP,')
+  binutils (>= ${binutils:Version}),
+  ${misc:Depends}
+Recommends: ${dep:libcdev}
+Replaces: gccgo-8 (<< ${gcc:Version}), cpp`'PV (<< 7.1.1-8)
+Suggests: ${gcc:multilib}, gcc`'PV-doc (>= ${gcc:SoftVersion}),
+ gcc`'PV-locales (>= ${gcc:SoftVersion}),
+ libdbgdep(gcc`'GCC_SO-dbg,,>=,${libgcc:Version}),
+ libdbgdep(gomp`'GOMP_SO-dbg,),
+ libdbgdep(itm`'ITM_SO-dbg,),
+ libdbgdep(atomic`'ATOMIC_SO-dbg,),
+ libdbgdep(asan`'ASAN_SO-dbg,),
+ libdbgdep(lsan`'LSAN_SO-dbg,),
+ libdbgdep(tsan`'TSAN_SO-dbg,),
+ libdbgdep(ubsan`'UBSAN_SO-dbg,),
+ifenabled(`libvtv',`',`
+ libdbgdep(vtv`'VTV_SO-dbg,),
+')`'dnl
+ libdbgdep(mpx`'MPX_SO-dbg,),
+ libdbgdep(quadmath`'QMATH_SO-dbg,)
+Provides: 

Bug#894772: RFS: deepin-system-monitor/1.4.3-1 [ITP]

[Adam Borowski]

On Wed, Apr 04, 2018 at 01:00:30PM +0800, Yanhao Mo wrote:
> * Package name: deepin-system-monitor
>   Version : 1.4.3-1

>   deepin-system-monitor - System monitor for Deepin Desktop Environment

Hi!
As for the packaging itself, the nethogs/ subproject is not included in the
copyright file; it seems to be already packaged separately, too.

But, that's easy to fix.  I found a bigger problem though:

The program has a long list of caps (with a fallback to setuid), that allow
any user perform most of root-only actions.  For example one of menus allows
anyone to kill/suspend/resume any process in the system.  No authentication
of any kind, no policy, just kill any process, period.

It's not just the GUI user who can do this, it's easy enough to simulate a
GUI to have deepin-system-monitor do what any process, by any uid, wants.

And if you say "most computers don't have untrusted users", then well -- you
still don't want some random thing running as another uid to have full
control over the system.  And, most schools/etc will install a bunch of
available desktop environments so individual users can choose; if Deepin is
one of these environments, you can take over anyone else.

And even if deepin-system-monitor had appropriate access control, it's still
a thoroughly bad idea to grant caps to a GUI process.  d-s-m crashed for me
twice (segfault) while casually perusing it, I imagine it'd be trivial to do
so intentionally.  And even if your code is 100% perfectly correct and
solid, d-s-m uses many many libraries, any of which can have bugs that can
be easy to subvert; various plugins can be loaded into the process, etc.
There's no way this could be done securely: thus, the security boundary must
be elsewhere.  Be it a small helper program, some kind of RPC, etc -- the
privileged action can't be done by the GUI program.

Thus, I'm afraid that deepin-system-monitor can't go into Debian without
some serious rethinking.  I cannot adequately assist you here, as I don't
know the way such policies are done these days, you'd need to ask someone
more knowledgeable than me.

I seriously hope I'm failing to understand something here...


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ 
⢿⡄⠘⠷⠚⠋⠀ ... what's the frequency of that 5V DC?
⠈⠳⣄

Bug#855918: Merging bugs

[Mathieu Parent]

Hi,

Just a quick note that #855918 and #873073 have the same cause and are
not a samba bug but the consequence of "network-online.target" not
working on stretch.

Keeping those opens for reference.

Regards

-- 
Mathieu Parent

Bug#879439: want to adopt x11vnc

[Adrian Bunk]

On Sun, Apr 08, 2018 at 10:34:38PM +0300, Nikita Youshchenko wrote:
> Hello Andrian.

Hi Nikita,

> I'm considering adoption of x11vnc debian package which is currently orphaned 
> [1].
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879439
> 
> You have recently uploaded a version of that package, on behalf of debian-qa 
> [2]. Thus, before retitling bug 879439 to ITA, I'm asking if you are ok with 
> that.

All I did was an upload to fix that x11vnc was using a non-default JDK.

I have no interest in adopting x11vnc,
and I would be glad if you adopt it.

> [2] 
> https://tracker.debian.org/news/944321/accepted-x11vnc-0913-3-source-into-unstable/
> 
> WBR,
> Nikita Yushchenko

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#879439: want to adopt x11vnc

[Nikita Youshchenko]

Hello Andrian.

I'm considering adoption of x11vnc debian package which is currently orphaned 
[1].

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

You have recently uploaded a version of that package, on behalf of debian-qa 
[2]. Thus, before retitling bug 879439 to ITA, I'm asking if you are ok with 
that.

[2] 
https://tracker.debian.org/news/944321/accepted-x11vnc-0913-3-source-into-unstable/

WBR,
Nikita Yushchenko



signature.asc
Description: OpenPGP digital signature

Bug#895251: gcc-8: use triplet-prefixed binutils

[Helmut Grohne]

Source: gcc-8
Version: 8-20180218-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: block 666743 by -1

While working on coinstallable toolchains I ran into another problem.
When we want to install two native toolchains for different
architectures, we also want two native binutils for these architectures.
Thus /usr/bin/as is ambiguous and must not be used. Thus a
triplet-prefixed compiler must not use plain as or plain ld, but that's
what happens when you configure gcc for a native build.

The attached patch adds the --with-as and --with-ld options pointing to
the triplet-prefixed versions of these tools such that we can later
switch the binutils dependency to binutils-$targettriplet.

I hope I found the right place to insert these options.

Helmut
--- a/debian/rules2
+++ b/debian/rules2
@@ -184,7 +184,9 @@
 CONFARGS += \
 	--enable-languages=$(subst $(SPACE),$(COMMA),$(enabled_languages)) \
 	--prefix=/$(PF) \
-	--with-gcc-major-version-only
+	--with-gcc-major-version-only \
+	--with-as=/usr/bin/$(DEB_TARGET_GNU_TYPE)-as \
+	--with-ld=/usr/bin/$(DEB_TARGET_GNU_TYPE)-ld

 ifeq ($(versioned_packages),yes)
   CONFARGS += --program-suffix=-$(BASE_VERSION)

Bug#895250: fix some build issues

[Matthias Klose]

Package: src:botan
Version: 2.4.0-5
Tags: sid buster patch
Severity: important

the botan build system is rather strange. instead of relying on some standard
tools it decides to do everything itself. nyi ...

Please apply these patches for your next upload. Allows to build to build botan
on Ubuntu/armhf.

patch at
http://launchpadlibrarian.net/363824926/botan_2.4.0-5_2.4.0-5ubuntu1.diff.gz

Bug#895249: libart-lgpl: Intent to Adopt

[Adrian Bunk]

Source: libart-lgpl
Version: 2.3.21-3
Severity: serious
Control: block 895247 by -1

I hereby declare my intent to adopt pygtk.

libart-lgpl is a dependency of libgnomecanvas.

This is about keeping software that is long dead upstream but
has reverse dependencies longer on life support.

The goal is that the package works in buster not worse than
it did in stretch, it is clear that spending much effort on
maintainance upstream or in Debian would be a waste of time.

Bug#895247: libgnomecanvas: Intent to Adopt

[Adrian Bunk]

Source: libgnomecanvas
Version: 2.30.3-3
Severity: serious
Tags: buster sid

17:37 < jbicha> how about this for a next step: someone who wants to maintain 
libgnomecanvas can file a severity: serious bug against Debian's 
libgnomecanvas with the title Intent to Adopt
17:37 < jbicha> we can discuss things more on that bug

I hereby declare my intent to adopt libgnomecanvas,
mostly triggered by #893770 (amide).

This is about keeping software that is long dead upstream but
has reverse dependencies longer on life support.

The goal is that the package works in buster not worse than
it did in stretch, it is clear that spending much effort on
maintainance upstream or in Debian would be a waste of time.

Bug#895248: pygtk: Intent to Adopt

[Adrian Bunk]

Source: pygtk
Version: 2.24.0-5.1
Severity: serious
Tags: buster sid

I hereby declare my intent to adopt pygtk.

pygtk still has many (including popular) reverse dependencies.
Python 2 will be removed in bullseye, and there is no clear
reason why pygtk has to be removed one release earlier.

This is about keeping software that is long dead upstream but
has reverse dependencies longer on life support.

The goal is that the package works in buster not worse than
it did in stretch, it is clear that spending much effort on
maintainance upstream or in Debian would be a waste of time.

Bug#895245: libxml2: CVE-2017-18258: Set memory limit for LZMA decompression

[Salvatore Bonaccorso]

Source: libxml2
Version: 2.9.1+dfsg1-5
Severity: important
Tags: patch security upstream
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=786696
Control: fixed -1 2.9.7+dfsg-1
Control: block -1 by 895195

Hi,

The following vulnerability was published for libxml2.

CVE-2017-18258[0]:
| The xz_head function in xzlib.c in libxml2 before 2.9.6 allows remote
| attackers to cause a denial of service (memory consumption) via a
| crafted LZMA file, because the decoder functionality does not restrict
| memory usage to what is required for a legitimate file.

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

It's important though to not apply the upstream commit
e2a9122b8dde53d320750451e9907a7dcb2ca8bb without adressing the
upstream issue https://bugzilla.gnome.org/show_bug.cgi?id=794914
(otherwise libxml2 will be opened to CVE-2018-9251 as it is now the
case for the libxml2 upload to experimental, thus i added a block to
indicate that).

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-18258
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18258
[1]  https://bugzilla.gnome.org/show_bug.cgi?id=786696
[2] 
https://git.gnome.org/browse/libxml2/commit/?id=e2a9122b8dde53d320750451e9907a7dcb2ca8bb

Regards,
Salvatore

Bug#895246: gconf: Intent to Adopt

[Adrian Bunk]

Source: gconf
Version: 3.2.6-4.1
Severity: serious

I hereby declare my intent to adopt gconf.

It is not a good service to our users to rip gconf support
out of many packages for buster.

This is about keeping software that is long dead upstream but
has reverse dependencies longer on life support.

The goal is that the package works in buster not worse than
it did in stretch, it is clear that spending much effort on
maintainance upstream or in Debian would be a waste of time.

Bug#887666: jh_linkjars: Invalid option: N

[Niels Thykier]

Emmanuel Bourg:
> Le 08/04/2018 à 12:57, Niels Thykier a écrit :
> 
>> I had a go and it failed (presumably because I do not have write access)
> 
> You have to join back the team then ;)
> 

Ok, requested access. :)

Let me know once it has been progressed.

Thanks,
~Niels

Bug#895195: libxml2: CVE-2018-9251

[Salvatore Bonaccorso]

Control: severity -1 serious

On Sun, Apr 08, 2018 at 11:42:11AM +0200, Salvatore Bonaccorso wrote:
> I'm currently clarifying the scope for CVE-2018-9251 with MITRE.
> Basically before e2a9122b8dde53d320750451e9907a7dcb2ca8bb upstrema
> commit the limiter was disabled effecitively. I'm trying to clarify if
> thus the scope CVE-2018-9251 should be consider only for libxml2
> version which did apply e2a9122b8dde53d320750451e9907a7dcb2ca8bb. The
> question on e2a9122b8dde53d320750451e9907a7dcb2ca8bb is another one,
> since it has potential for denial of service, and asked for if that
> should get a separate CVE id.

This has been clarified. So CVE-2018-9251 is only an issue if upstream
commit e2a9122b8dde53d320750451e9907a7dcb2ca8bb has been applied. See
details in https://bugzilla.gnome.org/show_bug.cgi?id=794914 .

I'm raising the severity to RC so that (since it only affects
experimental), does not enter unstable in this form.

There is though no upstream fix accepted yet, although the reporter
has proposed a solution.

Regards,
Salvatore

Bug#895244: ocrmypdf seems to have a flaky autopkgtest

[Paul Gevers]

Source: ocrmypdf
Version: 5.5-2
Severity: normal
User: ci-t...@tracker.debian.org
Usertags: flaky

Hi Sean,

While inspecting regressions in autopkgtest results¹², I noticed that
your package ocrmypdf fails regularly, without obvious changes. At times
when these tests fail, they also take considerably longer, i.e. more
than 1 hour instead of around 15 minutes.

While it maybe so that your latest version fixes the issue, I didn't
spot anything in the changelog to warrant that, so I am filing this bug
to prevent us from forgetting it. If you believe the issue is fixed,
please don't hesitate to close this bug immediately.

Paul

¹ https://ci.debian.net/packages/o/ocrmypdf/unstable/amd64/
² https://ci.debian.net/packages/o/ocrmypdf/testing/amd64/



signature.asc
Description: OpenPGP digital signature

Bug#891288: tiff / CVE-2018-7456

[Hugo Lefeuvre]

Hi,

I didn't get any feedback on the bug report. I have reworked my patch
and issued a merge requested on Gitlab[0].

Regards,
 Hugo

[0] https://gitlab.com/libtiff/libtiff/merge_requests/27

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA


signature.asc
Description: PGP signature

Bug#892356: fslint: findutils on testing breaks fslint recursive search

[jEsuSdA 8)]

El 06/04/18 a las 06:52, Pádraig Brady escribió:

On 02/04/18 08:57, jEsuSdA 8) wrote:

El 10/03/18 a las 14:09, Pádraig Brady escribió:

I just tried find from git (not a debian package)
and I don't see the issue.
Perhaps it's already fixed in find upstream?
Can you give more details of the breakage?


I found the problem:

fslint does not do recursive duplicate searching when the FOLDER is a
SYMBOLIC LINK

For example:

/folder/main-folder/lot-of-pics

Where lot-of-pics has duplicate files.


ln -s /folder/main-folder /folder/symlink-folder


If you try to find duplicate pics intro /folder/symlink-folder DOES NOT
WORK.


If you try /folder/main-folder/, fslint founds duplicate files inside
lot-of-pics

If you try /folder/symlink-folder/lot-of-pics, fslint works as expected.

So, I think, if route ends on symlink, fslint treats this folder as a
file. If the route ends on regular folder, it works fine.


Can you confirm this?
Thanks a lot!!!


I think this is already fixed in git. See:
https://github.com/pixelb/fslint/commit/9efd7fff

thanks,
Pádraig



Great news!
Thank you so much!!!

Bug#895154: ffmpeg: FTBFS - make[2]: write error: stdout

[James Cowgill]

Control: tags -1 pending

Hi,

On 08/04/18 11:18, Niels Thykier wrote:
> On Sat, 7 Apr 2018 21:38:53 +0100 James Cowgill  wrote:
>> Source: ffmpeg
>> Version: 7:3.4.1-1
>> Severity: serious
>> Tags: sid buster
>>
>> For some reason ffmpeg has started FTBFS with this error:
>>> TESTvsynth2-zlib
>>> /<>/tests/fate-run.sh fate-vsynth2-zlib "" "" 
>>> "/<>/debian/standard" 'enc_dec "rawvideo -s 352x288 -pix_fmt 
>>> yuv420p " tests/data/vsynth2.yuv avi "-c zlib " rawvideo "-s 352x288 
>>> -pix_fmt yuv420p -vsync 0 " -keep ""' '' 
>>> '/<>/tests/ref/vsynth/vsynth2-zlib' '' '1' '' '' '' '' '' '1' 
>>> '' '' ''
>>>  /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all -f 
>>> rawvideo -s 352x288 -pix_fmt yuv420p -threads 1 -idct simple -flags 
>>> +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -hwaccel none 
>>> -threads 1 -thread_type frame+slice -i 
>>> /<>/debian/standard/tests/data/vsynth2.yuv -threads 1 -idct 
>>> simple -dct fastint -c zlib -flags +bitexact -sws_flags 
>>> +accurate_rnd+bitexact -fflags +bitexact -f avi -y 
>>> /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi
>>>  /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all 
>>> -threads 1 -idct simple -flags +bitexact -sws_flags +accurate_rnd+bitexact 
>>> -fflags +bitexact -hwaccel none -threads 1 -thread_type frame+slice -i 
>>> /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi -threads 
>>> 1 -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 -flags 
>>> +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f rawvideo 
>>> -y 
>>> /<>/debian/standard/tests/data/fate/vsynth2-zlib.out.rawvideo
>>> make[2]: Leaving directory '/<>/debian/standard'
>>> make[2]: write error: stdout
>>> dh_auto_test: cd debian/standard && make -j4 -O check -k returned exit code 
>>> 1
>>> make[1]: *** [debian/rules:231: override_dh_auto_test-arch] Error 25
>>> make[1]: Leaving directory '/<>'
>>> make: *** [debian/rules:192: binary] Error 2
>>> dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
>>> status 2
>>
>> This can be seen on the reproducible builds first seen 2018-03-15
>> affecting 3.4 and 3.5 in experimental.
>>
>> I'm guessing this has something to do with "make -O" which was enabled
>> recently in debhelper, but I haven't checked.
>>
>> James
> 
> Hi James,
> 
> In a recent upload, debhelper started using -Oline instead of -O.  Does
> that solve this problem for you?  (It was done unrelated to this bug,
> but looking at the documentation for -O, I suspect it might help here as
> well)

As me and Adrian said on IRC, it does not. The problem was nodejs
leaving stderr in non-blocking mode and I've committed this to fix it.
So no bugs in debhelper here.

https://salsa.debian.org/multimedia-team/ffmpeg/commit/71b483f31e5a411a02717278e0a30323965c2c88

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#895243: primer3: autopkgtest fails since 2.4.0-1 while it succeeded in the past

[Paul Gevers]

Source: primer3
Version: 2.4.0-1
Severity: normal
User: ci-t...@tracker.debian.org
Usertags: regression

Since the upload of primer3 version 2.4.0-1 the autopkgtests¹ have
failed with the following error:

run-unit-testFAIL stderr: ../src/primer3_core: Cannot open
../settings_files/primer3_v1_1_4_default_settings.txt
autopkgtest [23:11:12]: test run-unit-test:  - - - - - - - - - - stderr
- - - - - - - - - -
../src/primer3_core: Cannot open
../settings_files/primer3_v1_1_4_default_settings.txt
../src/primer3_core: Cannot open
../settings_files/primer3web_v0_4_0_default_settings.txt
../src/primer3_core: Cannot open
../settings_files/primer3web_v3_0_0_default_settings.txt
../src/primer3_core: Cannot open
../settings_files/primer3web_v4_0_0_default_settings.txt
autopkgtest [23:11:12]:  summary
run-unit-testFAIL stderr: ../src/primer3_core: Cannot open
../settings_files/primer3_v1_1_4_default_settings.txt

If this message is harmless, the stderr message can be ignore by adding
the allow-stderr to the Restrictions of autopkgtest.

Paul

¹ https://ci.debian.net/packages/p/primer3/unstable/amd64/



signature.asc
Description: OpenPGP digital signature

Bug#895242: [apt] apt-cache search with multiple distinct keywords miss some packages

[Abdullah Ramazanoglu]

Package: apt
Version: 1.6~beta1
Severity: minor

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

In Buster, with apt 1.6~alpha7 and 1.6~beta1, apt-cache search produces
an incomplete list. However, the missing packages can be seen by
apt-cache by means other than "search" (e.g. show, showpkg, pkgnames,
etc.). All the packages missing from the list are install candidates
(#600010 not applicable)

$ apt-cache search continuous integration
debci-worker - continuous integration system for Debian (worker daemon)
fwupd-tests - Test suite for firmware update daemon
lava-dispatcher - Linaro Automated Validation Architecture dispatcher
lava-lxc-mocker - Linaro Automated Validation Architecture LXC Mocker
lavacli - LAVA XML-RPC command line interface
libtap-formatter-junit-perl - Perl module for converting TAP output to
JUnit XML output
ocrmypdf - add an OCR text layer to PDF files
trac-bitten - continuous integration plugin for Trac
trac-bitten-slave - continuous integration plugin for Trac

This list is incomplete. For instance,

~$ apt-cache pkgnames debci
debci-collector
debci-worker
debci

All these debci* packages have the phrase "continuous integration" in
their descriptions, but the search reveals only debci-worker. Here,
debci is just an example. There are other missing packages in the list,
too.

OTOH, phrase searching reveals a better hit rate than searching with
multiple distinct keywords, while normally the opposite should have
been true.

~$ apt-cache search "continuous integration"
libgradle-android-plugin-java - Android Plugin for Gradle
libgradle-android-plugin-java-doc - Android Plugin for Gradle -
Documentations
buildnotify - cruise control CI build monitor
debci - continuous integration system for Debian
debci-collector - continuous integration system for Debian (collector
daemon)
debci-worker - continuous integration system for Debian (worker
daemon)
python-pytest-timeout - Pytest plugin to abort hanging tests -
Python 2.X
python3-pytest-timeout - Pytest plugin to abort hanging
tests - Python 3.X
trac-bitten - continuous integration plugin for Trac
trac-bitten-slave - continuous integration plugin for Trac
python-xmlrunner - PyUnit-based test runner with JUnit like XML
reporting
node-vows - asynchronous BDD & continuous integration for Node


--- System information. ---
Architecture: 
Kernel:   Linux 4.9.0-4-amd64

Debian Release: buster/sid
  500 testing ftp.tr.debian.org 

--- Package information. ---
Depends (Version) | Installed
=-+-===
adduser   | 3.117
gpgv  | 2.2.4-3
 OR gpgv2 | 
 OR gpgv1 | 
debian-archive-keyring| 2017.7
libapt-pkg5.0  (>= 1.6~beta1) | 1.6~beta1
libc6   (>= 2.15) | 2.27-2
libgcc1(>= 1:3.0) | 1:8-20180218-1
libgnutls30(>= 3.5.6) | 3.5.18-1
libseccomp2(>= 1.0.1) | 2.3.1-2.1
libstdc++6   (>= 5.2) | 8-20180218-1


Recommends   (Version) | Installed
==-+-===
ca-certificates| 20170717


Suggests (Version) | Installed
==-+-
apt-doc| 
aptitude   | 
 OR synaptic   | 0.84.2
 OR wajig  | 
dpkg-dev   (>= 1.17.2) | 
gnupg  | 2.2.4-3
 OR gnupg2 | 
 OR gnupg1 | 
powermgmt-base | 1.31+nmu1


--- Output from package bug script ---


-- 
Abdullah Ramazanoglu

Bug#895238: postfix: consider changing the default mailer type to "Local only" instead of "Internet site"

[Raphaël Halimi]

Le 08/04/2018 à 20:26, Scott Kitterman a écrit :
> Your example isn't relevant to Debian.  In Ubuntu, Postfix is the
> default MTA.  In Debian, it's not.  If a non-default MTA is being
> pulled in by a package that only needs a generic MTA, then it's buggy
> and should be fixed.

Ah, sorry, I don't use Ubuntu, so I didn't know.

Feel free to close the bug then, if you think it's not relevant.

Regards,

-- 
Raphaël Halimi

Bug#893515: digikam: FTBFS with kdepim 17.12.2

[Simon Frei]

I totally understand that, I am just trying to get infos to you as
debian maintainer from my (at the moment admittedly almost non-existing)
involvement upstream. Exiv2 0.26 will likely not get into testing.
Upstream does backport a lot of security fixes to 0.26, but negated
creating a dot release on request, and is focussing on 0.27. It was
planned to release an rc in early 2018, but from what I read in the
issue tracker, that's not going to happen asap.



signature.asc
Description: OpenPGP digital signature

Bug#895104: why3: skip cvc4 autopkgtest on architectures without cvc4

[Ralf Treinen]

Hi again,

On Fri, Apr 06, 2018 at 09:12:09PM -0700, Steve Langasek wrote:

> In addition to bug #895103, the why3 autopkgtests also fail on non-x86
> architectures in Ubuntu because the test dependencies for the why3+cvc4 test
> cannot be satisfied.  The attached patch makes the test dependency
> architecture-specific and lets it pass as a no-op on architectures without
> cvc4.

sorry but I do not agree to apply this patch. I don't think that
hardcoding in the why3 package the list of architectures on which cvc4
currently builds is the right way to solve this issue. Note that cvc4 is
only one in a list of alternative dependencies.

This rather looks to me like a missing feature in autopkgtest: we would
need a tag in the test control file that states that failure to satisfy
the build-dependencies of a test is not to be considered fatal.

At the base of this there is an interesting problem with alternative
dependencies: if your tool can interact with any of a list of packages
than it is sufficient to install one of these to make your tool work.
However, one might want to test that your tool interoperates correctly
with *all* packages among the alternatives.

Cheers -Ralf.

Bug#895238: postfix: consider changing the default mailer type to "Local only" instead of "Internet site"

[Scott Kitterman]

On April 8, 2018 5:41:37 PM UTC, "Raphaël Halimi"  
wrote:
>Package: postfix
>Version: 3.3.0-1
>Severity: wishlist
>
>Hi,
>
>I report this bug following my own advice in [1].
>
>I have set the severity to wishlist, but from a security point of view,
>it could be considered much higher.
>
>The default Postfix configuration, when keeping the default debconf
>answers, listens on all network interfaces. Unlike what's said in
>#418511, this doesn't make it an open relay though, since mynetworks is
>restricted to localhost. Nevertheless, OP in [1] is IMHO quite right,
>this is still a "network-exposed attack surface".
>
>My rationale is : until Stretch, the "standard" installation comprised
>exim4-daemon-light, which fulfilled all dependencies on the
>"mail-transport-agent" virtual package, which in turn implicated that
>users installing Postfix did so manually, and knew what they were
>doing.
>
>Unfortunately, from Stretch onward, now that no MTA is present in the
>standard installation, some dependencies chains can end up installing a
>random MTA "unexpectedly" (I put quotes around "unexpectedly", because
>one should always carefully read the list of installed dependencies
>when
>installing a package, but we all know that users are not always that
>careful).
>
>IMHO it would be wise to change the default answer to the debconf
>question "postfix/main_mailer_type" to "Local only" instead of
>"Internet
>site", in order to limit the security risk in case Postfix was
>installed
>"unexpectedly" due of an overlooked dependency chain.
>
>[1] https://bugs.launchpad.net/debian/+source/tlp/+bug/1758798
>
>Regards,

Your example isn't relevant to Debian.  In Ubuntu, Postfix is the default MTA.  
In Debian, it's not.  If a non-default MTA is being pulled in by a package that 
only needs a generic MTA, then it's buggy and should be fixed.

Scott K

Bug#895103: why3 server broken on multiple architectures

[Ralf Treinen]

Hi Steve,

On Fri, Apr 06, 2018 at 09:00:44PM -0700, Steve Langasek wrote:

> The attached patch fixes the trivial portability issue in why3, and as seen
> at http://autopkgtest.ubuntu.com/packages/w/why3 the tests are now passing
> for 0.88.3 on all architectures where they previously passed.

Thanks a lot for the patch. Applied and forwarded to upstream -Ralf.

Bug#893515: digikam: FTBFS with kdepim 17.12.2

[Steve Robbins]

On Sunday, April 8, 2018 1:03:29 PM CDT Simon Frei wrote:
> Digikam still works with exiv2 0.25. It's just that a lot of fixes have
> gone into 0.26 that prevent crashs in digikam, that's why its cmake file
> has a >=0.26 dependency.

Well, the digikam build with 0.25 just stops with an error -- as you say, its 
from the cmake file.  It's possible this is just to "prevent crashes", but I 
hate to second-guess upstream.  Moreover, preventing crashes is good.  So I'd 
prefer to focus on getting exiv2 0.26 into Debian.

-Steve


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

Bug#895241: ITP: snapcast -- multi-room client-server audio player

[Felix Geyer]

Package: wnpp
Severity: wishlist
Owner: Felix Geyer 

* Package name: snapcast
  Version : 0.13.0
  Upstream Author : Johannes Pohl
* URL : https://github.com/badaix/snapcast
* License : GPL
  Description : multi-room client-server audio player

Snapcast is a multi-room client-server audio player, where all clients are
time synchronized with the server to play perfectly synced audio. It's not a
standalone player, but an extension that turns your existing audio player into
a Sonos-like multi-room solution.

Bug#895240: ITP: fontpens -- Classes implementing Pen protocol for manipulating UFO glyphs

[魏銘廷]

Package: wnpp
Severity: wishlist
Owner: Yao Wei (魏銘廷) 
X-Debbugs-CC: debian-fo...@lists.debian.org

* Package name: fontpens
  Version : 0.1.0
  Upstream Author : The RoboFabs Developers
* URL : https://github.com/robofab-developers/fontPens
* License : BSD-3-Clause
  Programming Lang: Python
  Description : Classes implementing Pen protocol for manipulating UFO 
glyphs

fontPens implements Pen protocol, which are instructions to draw glyphs.  This
protocol is established by RoboFabs, and this library is the reference
implementation of the protocol, which is for manipulating UFO files.

The API is also compatible with FontForge Python API and FontLab VI Python
API.

The main reason packaging this is the ufoLib's optional dependency for
some contour manipulations like correcting the direction.

This should be maintained in Debian Fonts Task Force.


signature.asc
Description: PGP signature

Bug#895239: [systemd] suspend works 1st time

[Ted To]

Package: systemd
Version: 232-25+deb9u3
Severity: important

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

Suspend only works first time.  It worked fine on an ancient Acer Aspire
One.  Now on an Acer S7 392, suspend works on its first try but
afterwards fails.  Currently running the backports kernel but didn't
work with stable either.

$ sudo journalctl -u suspend.target
[sudo] password for tct:
-- Logs begin at Sun 2018-04-08 12:17:50 EDT, end at Sun 2018-04-08
13:49:23 EDT. --
Apr 08 12:48:07 okeeffe systemd[1]: Reached target Suspend.
Apr 08 12:48:07 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 12:48:07 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 12:48:09 okeeffe systemd[1]: Reached target Suspend.
Apr 08 12:48:09 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 12:48:09 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 13:02:36 okeeffe systemd[1]: Reached target Suspend.
Apr 08 13:02:36 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 13:02:36 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 13:28:28 okeeffe systemd[1]: Reached target Suspend.
Apr 08 13:28:28 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 13:28:28 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 13:29:24 okeeffe systemd[1]: Reached target Suspend.
Apr 08 13:29:24 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 13:29:24 okeeffe systemd[1]: Stopped target Suspend.

and relevant portions of syslog:

Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4718]
manager: sleep requested (sleeping: no  enabled: yes)
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4719]
manager: sleeping...
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4720]
manager: NetworkManager state is now ASLEEP
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4724]
device (wlp1s0): state change: activated -> deactivating (reason
'sleeping') [100 110 37]
Apr  8 13:50:09 debian dbus[521]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service'
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4770]
device (wlp1s0): state change: deactivating -> disconnected (reason
'sleeping') [110 30 37]
Apr  8 13:50:09 debian systemd[1]: Starting Network Manager Script
Dispatcher Service...
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fd21:9228:e650::b2e on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
2601:14d:4101:380b::b2e on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fd21:9228:e650:0:889d:b57e:e0cc:c4b2 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fd21:9228:e650:0:5e51:4fff:fef2:d5b9 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address fd21:9228:e650:0:5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:889d:b57e:e0cc:c4b2.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
2601:14d:4101:380b:889d:b57e:e0cc:c4b2 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:889d:b57e:e0cc:c4b2.
Apr  8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
2601:14d:4101:380b:5e51:4fff:fef2:d5b9 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group
on interface wlp1s0.IPv6 with address fe80::5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Registering new address record
for fe80::5e51:4fff:fef2:d5b9 on wlp1s0.*.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fe80::5e51:4fff:fef2:d5b9 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address fe80::5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Interface wlp1s0.IPv6 no
longer relevant for mDNS.
Apr  8 13:50:09 debian dbus[521]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
Apr  8 13:50:09 debian systemd[1]: Started Network Manager Script
Dispatcher Service.
Apr  8 13:50:09 debian nm-dispatcher: req:1 'connectivity-change': new
request (2 scripts)
Apr  8 13:50:09 debian nm-dispatcher: req:1 'connectivity-change': start
running ordered scripts...
Apr  8 13:50:09 debian NetworkManager[533]:   

Bug#893515: digikam: FTBFS with kdepim 17.12.2

[Simon Frei]

Digikam still works with exiv2 0.25. It's just that a lot of fixes have
gone into 0.26 that prevent crashs in digikam, that's why its cmake file
has a >=0.26 dependency.



signature.asc
Description: OpenPGP digital signature

Bug#895188: asciidoctor: E-mail addresses are rendered twice [manpage backend]

[Christoph Biedl]

Joseph Herlant wrote...

> To achieve your goal you would need to use the following:
> mailto:debian.a...@manchmal.in-ulm.de[Christoph Biedl]
(...)
> Is that acceptable?

Certainly.

Christoph, should actually be able to read documentation on his own


signature.asc
Description: PGP signature

Bug#885204: gnucash: please migrate to guile-2.2

[Rob Browning]

Dmitry Smirnov  writes:

> Hi Rob,
>
> On Tuesday, 26 December 2017 9:17:34 AM AEDT Rob Browning wrote:
>> I'd like to remove guile-2.0 before the buster release, so please
>> migrate to guile-2.2 when you can.
>
> I tried to build Gnucash with "guile-2.2" but "dh_strip" failed as follows:
>
> 
> dh_strip --dbgsym-migration='gnucash-dbg (<< 1:2.6.13~)'
> strip: Unable to recognise the format of the input file `debian/gnucash/usr/
> lib/x86_64-linux-gnu/gnucash/gnucash/scm/ccache/2.2/report.go'
> dh_strip: strip --remove-section=.comment --remove-section=.note --strip-
> unneeded debian/gnucash/usr/lib/x86_64-linux-gnu/gnucash/gnucash/scm/ccache/
> 2.2/report.go returned exit code 1
> 
>
> There is no such problem with "guile-2.0"...
>
> Any ideas what could be done about that?

dh_strip just needs to ignore guile's .go files -- its guess is
uncorrect .  They're not normal object files, they just use the ELF
format.

Although it might be too general, I wonder if "dh_strip ... -X.go" would
work, as long as you don't have any other files with .go in the name
that should be stripped.  What we'd really need is dh_strip globbing,
i.e. "*.go".

Alternately, you can just override the dh_strip target and only
(manually) strip the relevant *.so, etc. files in the override.

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

Bug#895152: cinnamon-screensaver: cinnamon-screesaver-command only locks the screen the first time it is called

[Pitxyoki]

Hi,

I could also reproduce with your simpler example.
Having this isolated to such simple cases was pretty hard for me, as
it was not clear where the root cause could be.

So, yes, this seems to be as you described and the two cases in this
report seem to be the same:
 * In the first case, I just wasn't waiting long enough for the
timeout to appear.
 * In the second case it makes sense that the stack traces only start
appearing after the 10th attempt as 30 seconds passed by then and
that's probably the "g-io-error-quark" timeout. So, the error doesn't
seem to be caused by some piling up of repeated requests in this case,
as I initially thought.

Note that this is similar to #895150 but in that one I expect the
command not to hang when it fails. In this, I'd expect this error not
to occur when the screensaver is already active. I suppose adding an
atomic check for a running screensaver before trying to launch it
should not be too hard.

Thanks and regards,
-- 
Luís Picciochi Oliveira

Bug#861261: nginx.service: Please change "network.target" to "network-online.target"

[David Härdeman]

Source: nginx
Followup-For: Bug #861261

I was also hit by this bug, nginx refused to start after reboot after
doing a dist-upgrade.

One fix (that I haven't tried) is changing
/proc/sys/net/ipv4/ip_nonlocal_bind and
/proc/sys/net/ipv6/ip_nonlocal_bind.

Temporary fix:

create /etc/systemd/system/nginx.service with the following
content:

.include /lib/systemd/system/nginx.service

[Unit]
After=network-online.target
Wants=network-online.target

Then run "systemctl daemon-reload", and also, according to:
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/

You might want to run e.g. "systemctl enable
systemd-networkd-wait-online.service" (if you're using networkd).

After that, and a reboot later, nginx is working as expected.

Ideally, the nginx service unit should be changed and nginx itself
should consider using the IP_FREEBIND sockopt functionality (though a
patch to do so seems to have been shot down, see for example:
https://forum.nginx.org/read.php?29,248807,248807#msg-248807 )

-- 
David Härdeman

Bug#880169: Please enable Indicator support and build against Ayatana Indicators

[Mike Gabriel]

Hi Michael,

On  So 08 Apr 2018 16:30:06 UTC, Michael Biebl wrote:


On Mon, 30 Oct 2017 10:36:23 +0100 Mike Gabriel
 wrote:

Source: network-manager-applet
Version: 1.8.4-1
Severity: wishlist
Tags: upstream patch
User: pkg-ayatana-de...@lists.alioth.debian.org
Usertags: ayatanaindicators

Dear maintainer,

attached you find a .debdiff that enables Indicator support in Network
Manager Applet (GNOME) on Debian.

The Debian + Ubuntu MATE Packaging Team are currently working on porting
Ubuntu Indicators to a distro-independent state. This is done under a new
upstream umbrella (https://github.com/AyatanaIndicators).

For Network Manager Applet (GNOME), we would love to see Indicator
support being enabled on Debian systems. As the Ubuntu Indicators in
Debian are severely unmaintained, please switch to Ayatana Indicators
when enabling Indicator support for your package.

A Network Manager Applet that has been built against Ayatana Indicators will
also work as-is on top of Ubuntu Indicators as found in Ubuntu.


Would you consider forwarding this request upstream?
I don't really want to maintain this as a downstream patch.


Sure, I can do that. In fact, my bug report has two parts: enable  
AppIndicator support and switch over from Ubuntu AppIndicator to  
Ayatana AppIndicator.


Don't expect any more work on that before the 16th Apr, I am currently  
on garden VAC.


Applications that support AppIndicator / SNI will enhance multiple  
desktops: Kde5, Gnome (with extension), Budgie, MATE, Xfce. LXQt is  
currently looking into SNI support, too.


So, application indicators are more commonly spread than system  
indicators. Network Manager Applet is in the realm of applicatipn  
indicators.


The system indicators (sound, session, datetime, keyboard, etc.) can  
enhance MATE, XFCE and Budgie for now. LXQt people are looking into  
that, too, afaih. Unity7 can't work without system indicators. The  
people from UBports (Unity8) also rely on system indicators. In  
Unity8, a switch to Ayatana Indicators is under investigation.



That aside, which desktops in Debian would benefit from Ayatana
Indicators support?


Answered above...


Regards,
Michael


Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

Bug#895238: postfix: consider changing the default mailer type to "Local only" instead of "Internet site"

[Raphaël Halimi]

Package: postfix
Version: 3.3.0-1
Severity: wishlist

Hi,

I report this bug following my own advice in [1].

I have set the severity to wishlist, but from a security point of view,
it could be considered much higher.

The default Postfix configuration, when keeping the default debconf
answers, listens on all network interfaces. Unlike what's said in
#418511, this doesn't make it an open relay though, since mynetworks is
restricted to localhost. Nevertheless, OP in [1] is IMHO quite right,
this is still a "network-exposed attack surface".

My rationale is : until Stretch, the "standard" installation comprised
exim4-daemon-light, which fulfilled all dependencies on the
"mail-transport-agent" virtual package, which in turn implicated that
users installing Postfix did so manually, and knew what they were doing.

Unfortunately, from Stretch onward, now that no MTA is present in the
standard installation, some dependencies chains can end up installing a
random MTA "unexpectedly" (I put quotes around "unexpectedly", because
one should always carefully read the list of installed dependencies when
installing a package, but we all know that users are not always that
careful).

IMHO it would be wise to change the default answer to the debconf
question "postfix/main_mailer_type" to "Local only" instead of "Internet
site", in order to limit the security risk in case Postfix was installed
"unexpectedly" due of an overlooked dependency chain.

[1] https://bugs.launchpad.net/debian/+source/tlp/+bug/1758798

Regards,

-- 
Raphaël Halimi

Bug#895219: lebiniou: Erreur premier lancement

[Olivier Girondel]

On 04/08/2018 03:05 PM, Nicolas GODBERT wrote:
> Package: lebiniou
> Version: 3.24-1
> Severity: minor
> 
> Bonjour Olivier,
> 
> Je viens d'installer le paquet lebiniou sur ma Debian testing mais lors du 
> lancement du programme, j'ai le message d'erreur ci-dessous :
> 
> nicolas@celine:~$ lebiniou
> [!] System error: creat: Permission denied
> nicolas@celine:~$ lebiniou -v
> Le Biniou version 3.24

Bonjour,

Si le crash apparaît si tôt, c'est sûrement un problème avec le plugin
d'entrée (ALSA par défaut sous Debian), essayez avec une autre source ?

Pour voir la liste des sources:
$ lebiniou -h

Sinon pour avoir un peu plus de logs,
$ strace lebiniou

--
Olivier

Bug#895150: cinnamon-screensaver-command: Crashes and hangs when unable to grab the keyboard/mouse

[Pitxyoki]

Hi Margarita,

I want to force the screen to get locked after some time has passed,
regardless of the user being idle or not. I think I'd rather have the
script returning with an error without retrying.
Given that retrying may never work (as mentioned in #895149), maybe
it's better not to do it and just let the caller be aware of the
failure.

I agree with lowering the severity level.

Thanks and regards,
-- 
Luís Picciochi Oliveira

Bug#895237: certbot: Stop/start Apache using systemctl instead of apachectl

[Jan Heitkötter]

Package: certbot
Version: 0.21.1-1~bpo9+1
Severity: normal

Dear Maintainer,

on certificate renewal certbot will stop Apache and start it afterwards. 
The relevant commands are pre_hook and post_hook in 
/etc/letsencrypt/renewal/CERTNAME.conf.

Default behaviour is do stop/start Apache using apachectl which fails in 
installations running systemd. Apache will stop, but not start again.

Fix: use systemctl to start/stop Apache.

Regards

Jan


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

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

Versions of packages certbot depends on:
ii  python3  3.5.3-1
ii  python3-certbot  0.21.1-1~bpo9+1

certbot recommends no packages.

Versions of packages certbot suggests:
pn  python-certbot-doc  
ii  python3-certbot-apache  0.21.1-1~bpo9+1
pn  python3-certbot-nginx   

-- no debconf information

Bug#895061: exclusions and dh_missing

[Nicolas Boulenguez]

My understanding (so far) is that there are three unselection
mechanisms, and I have the feeling that only one is worth supporting.


It is useful to provide at least a sensible way to overrides hardcoded
or autodetected paths.
  override_dh_link:
dh_link --exclude=/non/standard/symlink
  override_dh_compress:
dh_compress --exclude=/non/standard/format


The --exclude option has a second, distinct, and arguable usage:
to extend the expressivity of glob patterns, like in:
  override_dh_installexamples:
dh_installexamples --exclude=foo/bar foo

It allows the caller to express two contradictory wishes, leading
debhelper to guess the actual intention (should dh_missing complain?).

It mixes two kinds of matching patterns in an inconsistent interface.
* dh_installexamples 'foo*' --exclude=foo
  seems to install foobar but does not.
* dh_installexamples foo --exclude=foo/bar
  seems to install foo/foo/bar but does not.
Good documentation is only a work-around.

For more fun, the incompatible wishes may be in different locations:
'foo*' in debian/examples and '--exclude=foo' in debian/rules.

It forces debhelper to be less performant, as each existing path must
be matched against two distinct kinds of patterns in the end.
Also, --exclude prevents a simple 'chmod -a' for directories.

It forces debhelper to contain code that is hard to write, maintain
and test. Factorization like EXCLUDE_FIND is only a work-around, it
does not change that a Perl script generates a Shell command
describing a find request compiling regular expressions translated
from command-line arguments usually transmited by a Shell launched by
Make. Who would bet that all special characters are handled correctly
in all corner cases ?

Now consider that all this can be replaced with an explicit debian/examples
  foo/baz
  foobar
or if the list keeps varying by an executable debian/examples with
  #!/bin/sh
  find foo -mindepth 1 -maxdepth 1 -not -name bar
(and of course foo/bar in debian/not-installed).


To some extent, the same concern applies to --ignore.
  override_dh_foo:
dh_foo --package=pkg --ignore=debian/pkg.cfg
dh_foo --remaining-packages
The now common source format 3.0 has made the original motivation
obsolete (if upstream tarball contains a debian/ subdirectory, it is
not extracted by dpkg-source at all).
If necessary, the maintainer can remove debian/pkg.cfg, rename it, or
add it to debian/clean.
Is it worth to slow down each call to pkgfile() to handle this?
However, the performance and complexity costs are way smaller, so the
balance with the burden of removing an option is probably different.

Bug#895236: maven-javadoc-plugin checks SystemUtils.IS_JAVA_1_9, but not for 10 and 11

[Matthias Klose]

Package: src:maven-javadoc-plugin
Version: 3.0.0-3
Severity: important
Tags: sid buster

maven-javadoc-plugin only checks SystemUtils.IS_JAVA_1_9 and fails with 10 and
11.  It should check for 10 and 11 as well.

This needs an update for libcommons-lang3-java first.

Bug#895219: lebiniou: Erreur premier lancement

[Olivier Girondel]

On 04/08/2018 03:05 PM, Nicolas GODBERT wrote:
> Package: lebiniou
> Version: 3.24-1
> Severity: minor
> 
> Bonjour Olivier,
> 
> Je viens d'installer le paquet lebiniou sur ma Debian testing mais lors du 
> lancement du programme, j'ai le message d'erreur ci-dessous :
> 
> nicolas@celine:~$ lebiniou
> [!] System error: creat: Permission denied
> nicolas@celine:~$ lebiniou -v
> Le Biniou version 3.24
> 
> Est-il possible d'identifier le problème svp ?
> Je ne vois rien de particulier dans les logs.

Un souci visiblement à la création du PID file (/tmp/lebiniou.pid)

Vérifiez si il existe et/ou changez les permissions (il devrait être
créé avec l'utilisateur courant)

--
Olivier

Bug#894769: Java error message and permission on serial port

[beckert . j]

Hi,

I have the same issue, this is what I've found so far:

- after plugging in the Arduino and starting the IDE, the status line reports 
the correct 
settings (board type and serial device selected in a previous session)

- just klicking on the 'Tools' menu throws the error message:
java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver

- the user running the Arduino IDE is in the dialout group, I tried if chmod 
666 on the serial 
device would help but it didn't

- tried to send a sketch to the Arduino, this produced the following two lines  
repeatedly:

java.lang.NullPointerException thrown while loading gnu.io.RXTXCommDriver
PORTS {} / {} => {}

then followed by:

processing.app.debug.RunnerException: Couldn’t find a Leonardo on the selected 
port. 
Check that you have the correct port selected.  If it is correct, try pressing 
the board's reset 
button after initiating the upload.
at 
processing.app.debug.AvrdudeUploader.uploadViaBootloader(AvrdudeUploader.java:154)
at 
processing.app.debug.AvrdudeUploader.uploadUsingPreferences(AvrdudeUploader.java:67)
at processing.app.Sketch.upload(Sketch.java:1671)
at processing.app.Sketch.exportApplet(Sketch.java:1627)
at processing.app.Sketch.exportApplet(Sketch.java:1599)
at processing.app.Editor$DefaultExportHandler.run(Editor.java:2380)
at java.base/java.lang.Thread.run(Thread.java:844)


-- System Information: 

Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

[Adrian Bunk]

Source: sugar-toolkit-gtk3
Version: 0.112-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sugar-toolkit-gtk3.html

...
d-shlibmove --commit \
--multiarch \
--exclude-la --exclude-a \
--devunversioned --ignorelibdep \
--movedev debian/tmp/usr/share/gir-1.0 usr/share/ \
--extralib 
debian/tmp/usr/lib/x86_64-linux-gnu/libsugar-eventcontroller.so \
debian/tmp/usr/lib/x86_64-linux-gnu/libsugarext.so
Library package automatic movement utility
 --> libasound2-dev package exists.
 --> libatk1.0-dev package exists.
 --> libcairo-dev is provided by a package.
 --> libcairo2-dev package exists.
devlibs error: There is no package matching [libfribidi0-dev] and noone 
provides it, please report bug to d-shlibs maintainer
 --> libglib2.0-dev package exists.
 --> libgtk-3-dev package exists.
 --> libgtk2.0-dev package exists.
 --> libice-dev package exists.
 --> libpango1.0-dev package exists.
 --> librsvg2-dev package exists.
 --> libsm-dev package exists.
 --> libx11-dev package exists.
 --> libxfixes-dev package exists.
 --> libxi-dev package exists.
make: *** [debian/rules:118: debian/stamp-local-shlibs-libsugarext] Error 1

Bug#895224: pdf-presenter-console: [regression] after upgrading to GStreamer 1.14.0, fails to play movies

[Francesco Poli]

On Sun, 08 Apr 2018 15:45:07 +0200 Francesco Poli (wintermute) wrote:

[...]
> It now seems that no movie can be played at all,
[...]

Mmmmh, I am trying to rebuild the binary package from the source
package, but I get some weird messages, among which:

  dpkg-gencontrol: warning: Depends field of package pdf-presenter-console: 
unknown substitution variable ${shlibs:Depends}

and I obtain a basically empty package with _no_ compiled executable
pdfpc (by looking at the .build file, it seems to me that no
compilation was performed)...

Do you happen to know of any fix needed to rebuild the package on
current sid?


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


pgpc_mFU_Wl_l.pgp
Description: PGP signature

Bug#895234: libcommons-lang3-java: update for OpenJDK 10 and OpenJDK 11

[Matthias Klose]

Package: src:libcommons-lang3-java
Version: 3.5-1
Severity: important
Tags: patch sid buster

Please either apply the following patches for 10 and 11, or update to the
upstream 3.6 release, and only apply the latter patch for 11 (which will be in
3.7 upstream).

https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=commitdiff_plain;h=a618b844c5a261ced37385ab3947de6e215d46f7

https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=patch;h=50ce8c44e1601acffa39f5568f0fc140aade0564

Bug#893515: digikam: FTBFS with kdepim 17.12.2

[Steve Robbins]

On Monday, March 19, 2018 10:48:38 AM CDT you wrote:

> digikam 5.6.0-4 can't be compiled with KDE Pim 17.12.2, it failes
> because kcalcore was been refactored to use QDateTime instead of
> KDateTime. 

I have DigiKam 5.9.0 compiled locally and it works.  Unfortunately, it depends 
on exiv2 0.26 that only exists in experimental.  So the digikam upload will 
also be to experimental.

-Steve


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

Bug#893418: Corrupted package names in by_vote.gz

[Bill Allombert]

On Fri, Mar 23, 2018 at 04:18:28PM +0100, Bill Allombert wrote:
> On Fri, Mar 23, 2018 at 03:35:01PM +0100, Bill Allombert wrote:
> > On Fri, Mar 23, 2018 at 02:24:39PM +0100, Enrico Zini wrote:
> > > On Fri, Mar 23, 2018 at 02:10:07PM +0100, Bill Allombert wrote:
> > > 
> > > > > Probably. Is the format of that file documented somewhere?
> > > > This is a list of key/value pair in RFC822 style.
> > > > See /usr/share/doc/popularity-contest/examples/bin/README.examples
> > > > for the format of the Package line.
> > > 
> > > I have a few questions:
> > > 
> > > How is the package name separated from the integer fields? It does not
> > > look like a fixed-width field:
> > > 
> > > Package: abev-form-obhgepi-fpk-nav  0 0 0 2
> > > Package: abev-form-obhgepi-fpk-nav-egyeb 0 0 0 2
> > > 
> > > If it is instead space-separated, currently I didn't see package names
> > > that contained spaces, but is there a guarantee that the package name
> > > won't contain spaces?
> > 
> > It is garanteed that package name will not contain spaces.
> > 
> > > Alternatively, should the parsing instead be done by splitting on \s+
> > > from the right with a maximum of 4 splits?
> > > 
> > > Some package names seem to be truncated, like this one:
> > > 
> > > Package: apache-openoffice-4.1.4-linux-x86-install-rpm-de 0 0 
> > > 0 1
> > 
> > The server should not truncate anything. I will check what happened.
> 
> The package name is truncated in the submitter report already.
> Maybe dpkg-query truncated it, maybe it was truncated even before.

In fact there is no truncation: -de is the language code for german!


Apparently a number of non-official packages use the character _ in their
name.

I have fixed the corruptions caused by truncated reports.

Do you still see corrupted entries?

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#895233: linux-image-4.15.0-2-amd64: [regression] Dell XPS 15 9560 can't be suspended (freezes on suspend)

[Leandro Lucarella]

Package: src:linux
Version: 4.15.11-1
Severity: important

Dear Maintainer,

With the kernel 4.15.0 my laptop is unable to suspend to RAM anymore.
With kernel linux-image-4.14.0-3-amd64  4.14.17-1 it worked (and still
works) perfectly.

It just freezes when trying to suspend. Not even SysRq commands work, so
I have to hard-reset it to recover it.

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

** Model information
sys_vendor: Dell Inc.
product_name: XPS 15 9560
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 1.7.1
board_vendor: Dell Inc.
board_name: 05FFDN
board_version: A00

** Network interface configuration:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5910] (rev 05)
Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers [1028:07be]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) 
[8086:1901] (rev 05) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:591b] (rev 04) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:07be]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Skylake 
Processor Thermal Subsystem [8086:1903] (rev 05)
Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Thermal Subsystem [1028:07be]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 
xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI])
Subsystem: Dell Sunrise Point-H USB 3.0 xHCI Controller [1028:07be]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-H Thermal subsystem [8086:a131] (rev 31)
Subsystem: Dell Sunrise Point-H Thermal subsystem [1028:07be]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal

00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-H Serial IO I2C Controller #0 [8086:a160] (rev 31)
Subsystem: Dell Sunrise Point-H Serial IO I2C Controller [1028:07be]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-H Serial IO I2C Controller #1 [8086:a161] (rev 31)
Subsystem: Dell Sunrise Point-H Serial IO I2C Controller [1028:07be]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H 
CSME HECI #1 [8086:a13a] (rev 31)
Subsystem: Dell Sunrise Point-H CSME HECI [1028:07be]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel 

Bug#725855: network-manager-gnome: nm-applet no longer started at session start in gnome classic

[Michael Biebl]

Control: tags -1 + moreinfo

On Wed, 09 Oct 2013 09:37:43 +0200 Olivier Berger
 wrote:
> Package: network-manager-gnome
> Version: 0.9.8.4-1
> Severity: normal
> 
> Hi.
> 
> nm-applet used to be started when I logged in to gnome classic.
> 
> For a few days now, it doesn't.
> 
> I have to manually start $ nm-applet&
> 
> Dunno why that happens.
> 

Is this still an issue on an up-to-date stretch or sid system?

Keep in mind, that in stretch, nm-applet does not start under gnome
classic by design. It's only supposed to start in gnome fallback.

Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#742025: network-manager-gnome: Systray icon too small

[Michael Biebl]

Control: tags -1 + moreinfo

On Tue, 18 Mar 2014 14:11:46 +0100 Christophe Troestler
 wrote:
> Package: network-manager-gnome
> Version: 0.9.8.4-1
> Severity: normal
> 
> Dear Maintainer,
> 
> When starting nm-applet
> 
> pkill nm-applet
> nm-applet &
> 
> the systray icon (in fluxbox) is too small (see nm_small.png attached).
> If I restart the network manager
> 
> /etc/init.d/network-manager restart
> 
> the icon has its normal size (see nm.png attached).

Is this still an issue on an up-to-date stretch or sid system?
If so, what tray application do you use?

Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#895188: asciidoctor: E-mail addresses are rendered twice [manpage backend]

[Joseph Herlant]

Hi,

I think this is due to the way the links are rendered in general.

To achieve your goal you would need to use the following:
mailto:debian.a...@manchmal.in-ulm.de[Christoph Biedl]

instead of:
Christoph Biedl 

See: https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/#links

Is that acceptable?

Thanks
Joseph

Bug#880169: Please enable Indicator support and build against Ayatana Indicators

[Michael Biebl]

On Mon, 30 Oct 2017 10:36:23 +0100 Mike Gabriel
 wrote:
> Source: network-manager-applet
> Version: 1.8.4-1
> Severity: wishlist
> Tags: upstream patch
> User: pkg-ayatana-de...@lists.alioth.debian.org
> Usertags: ayatanaindicators
> 
> Dear maintainer,
> 
> attached you find a .debdiff that enables Indicator support in Network
> Manager Applet (GNOME) on Debian.
> 
> The Debian + Ubuntu MATE Packaging Team are currently working on porting
> Ubuntu Indicators to a distro-independent state. This is done under a new
> upstream umbrella (https://github.com/AyatanaIndicators).
> 
> For Network Manager Applet (GNOME), we would love to see Indicator
> support being enabled on Debian systems. As the Ubuntu Indicators in
> Debian are severely unmaintained, please switch to Ayatana Indicators
> when enabling Indicator support for your package.
> 
> A Network Manager Applet that has been built against Ayatana Indicators will
> also work as-is on top of Ubuntu Indicators as found in Ubuntu.

Would you consider forwarding this request upstream?
I don't really want to maintain this as a downstream patch.

That aside, which desktops in Debian would benefit from Ayatana
Indicators support?

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



signature.asc
Description: OpenPGP digital signature

Bug#842918: network-manager-gnome: network-manager gnome not supporting appindicator

[Michael Biebl]

Control: tags -1 + moreinfo

On Wed, 02 Nov 2016 11:42:24 +0100 Mark Dickie 
wrote:
> Package: network-manager-gnome
> Version: 1.4.2-1
> Severity: wishlist
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***
> 
> Running enlightenment E21, xembed is not supported in the systray. A version 
> of
> n-m-gnome built with the --with-appindicator configure option would be
> beneficial in systems which have moved away from old xembed system to
> appindicator.

TTBOMK, appindicator is no longer actively maintained (by Ubuntu) and
also unmaintained in Debian.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818019

I'm thus very reluctant to enable support for it.

-- 
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#895152: cinnamon-screensaver: cinnamon-screesaver-command only locks the screen the first time it is called

[Margarita Manterola]

control: retitle -1 cinnamon-screensaver-command hungs if locking 
already locked screen


Hi,

I have been able to reproduce this issue.  I believe it's very similar 
to the other one you reported.


In my test, I waited long enough with the screen locked, that just one 
second call to cinnamon-screensaver-command failed:


marga@penelope:~$ date; cinnamon-screensaver-command -l; date; 
cinnamon-screensaver-command -l; date

dom abr  8 18:04:50 CEST 2018
dom abr  8 18:04:51 CEST 2018
Traceback (most recent call last):
  File 
"/usr/share/cinnamon-screensaver/cinnamon-screensaver-command.py", line 
73, in on_client_ready

self.perform_action()
  File 
"/usr/share/cinnamon-screensaver/cinnamon-screensaver-command.py", line 
90, in perform_action

self.client.proxy.call_lock_sync(self.message)
GLib.Error: g-io-error-quark: Se alcanzó el tiempo de expiración (24)

<... and it hungs there forever ...>

So, what I see happening here is that cinnamon-screensaver-command is 
trying to lock a screen that is already locked. It times out and then 
hungs, like when it can't lock because of a popup.  It's likely that 
this bug is the same as 895150. In other words, 
cinnamon-screensaver-command misbehaves when it fails to lock the 
screen, regardless of why it fails.


--
Regards,
Marga

Bug#882426: i8kutils: No effect on Latitude E7440

[Jérémie Liénard]

Hi,


It's needed to override the BIOS control. You can take a look here :
'https://github.com/vitorafsr/i8kutils/issues/6'


In the past you have to use "smm" to override the BIOS fan control (like
here
'https://wiki.archlinux.org/index.php/Fan_speed_control#Dell_laptops'),
but it's some ASM code and command. There is a security risk and the
maintainer and developer of i8kutils remove SMM.


The problem is still pending, and unfortunately I didn't found an
alternative to SMM.


I hope a solution will be found, my e7440 is very noisy, CPU at 49°C and
more than 6000rpm for the fan...


Bests regards,


-- 
Ce courrier électronique, et éventuellement ses pièces jointes, peuvent 
contenir des informations confidentielles et/ou  personnelles et a été envoyé 
uniquement à l'usage de la personne ou de l'entité citée ci-dessus. Si vous 
receviez ce courrier électronique par erreur, merci de bien vouloir en avertir 
l'expéditeur immédiatement par la réponse en retour à ce courrier et effacer 
l'original et détruire toute copie enregistrée dans un ordinateur, ou imprimée 
ou encore sauvegardée sur un disque. Toute revue, retransmission ou toute autre 
forme d'utilisation de ce courrier électronique par toute autre personne que le 
destinataire prévue est strictement interdite. Internet ne permettant pas 
d'assurer l'intégrité de ce message, l'expéditeur décline toute responsabilité 
au cas où il aurait été intercepté ou modifié par quiconque.

This e-mail and possibly any attachment may contain confidential and/or 
privileged information and is intended only for the use of the individual or 
entity named above. If you have received it in error, please advise the sender 
immediately by reply e-mail and delete  and destroy all copies including all 
copies stored in the recipient's computer, printed or saved to disk. Any 
review, retransmission, or further use of this e-mail by persons or entities 
other than the intended recipientis strictly  prohibited. Because of the nature 
of Internet the sender is not in a position to ensure the integrity of this 
message, therefore the sender disclaims any liability whatsoever, in the event 
of this message having been intercepted and/or altered.

Bug#895150: cinnamon-screensaver-command: Crashes and hangs when unable to grab the keyboard/mouse

[Margarita Manterola]

control: severity -1 normal

Hi!

Thanks for the report.  I have been able to reproduce and I agree that 
this is a bug, although definitely not an "important" bug.


I understand that you are trying to script your screensaver 
interactions, but the screensaver already ships with builtin 
functionality for triggering after idle time, etc, so a misbehavior in 
the cinnamon-screensaver-command does not justify severity important.


Regarding the actual bug, I guess the code needs to be modified to catch 
the exception and either retry or exit with error, but not hang as it 
does here.


--
Regards,
Marga

Bug#895232: Please do not force --ignore-installed behaviour for non-root users

[Max Bowsher]

Package: src:python-pip
Version: 9.0.1-2

Currently, there is a Debian-specific patch "set_user_default.patch" 
which changes various behaviour if the invoker is not root.


Whilst I understand the sense in defaulting to --user in this case, I 
would like to request that you not force --ignore-installed too, with no 
way to opt out.


As a user, I want to be able to install within ~/.local/, packages I 
need for ad-hoc development, but I do not want to needlessly accumulate 
duplicate installs which could equally have been satisfied using 
packages already installed in the system Python installation.


This bug report complements, but does not wholly duplicate #876145, 
which reports problems caused by forcing --ignore-installed in other 
scenarios.


Thanks,
Max.

Bug#895167: bgpdump: move out of asciidoc

[Joseph Herlant]

Hi  Christoph,


> Switching to asciidoctor was the obvious thing to do although it's not a
> simple drop-in replacment for a2x. Probably "asciidoctor --attribute
> reproducible --backend=manpage" does the trick.

Yes, that's the command to generate manpages in asciidoctor.

> But I'm stuck with several regressions, see above. Also, given the fact
> #884213 hasn't been addressed in months raises concerns whether using
> asciidoctor was a wise decision.

Fair point, thanks for pointing that out. I'll try to help the current
asciidoctor maintainers fix those.

I'll let you know when that's done.

Thanks
Joseph

Bug#887666: jh_linkjars: Invalid option: N

[Emmanuel Bourg]

Le 08/04/2018 à 12:57, Niels Thykier a écrit :

> I had a go and it failed (presumably because I do not have write access)

You have to join back the team then ;)

Bug#895231: ITP: golang-github-linuxdeepin-go-gir-generator -- Go bindings of GObject/Gtk libraries

[Yanhao Mo]

Package: wnpp
Severity: wishlist
Owner: Yanhao Mo 

* Package name: go-gir-generator
  Version : 1.0.3
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://github.com/linuxdeepin/go-gir-generator
* License : GPL-3+
  Programming Lang: golang
  Description : Go bindings of GObject/Gtk libraries

go-gir-generator can adapt to the newest version of GObject
without changing one single line of code, which makes it
less painful to write Go code with GObject.