Bug#886171: qwt: FTBFS on armhf: symbols

[Sebastiaan Couwenberg]

Control: tags -1 patch

The attached debdiff fixes the symbols, and overrides dh_makeshlibs to
not fail again in the future.

Please note the RFS for qwt (6.1.3-1) in #886501, that should also fix
this issue.

Kind Regards,

Bas
diff -Nru qwt-6.1.2/debian/changelog qwt-6.1.2/debian/changelog
--- qwt-6.1.2/debian/changelog  2016-09-05 14:05:19.0 +0200
+++ qwt-6.1.2/debian/changelog  2018-01-11 07:47:48.0 +0100
@@ -1,3 +1,13 @@
+qwt (6.1.2-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update symbols files with buildds' logs. Yet again.
+(closes: #886171)
+  * Override dh_makeshlibs to not fail on symbols changes,
+and set upstream version.
+
+ -- Bas Couwenberg   Thu, 11 Jan 2018 07:47:48 +0100
+
 qwt (6.1.2-6) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru qwt-6.1.2/debian/libqwt6abi1.symbols 
qwt-6.1.2/debian/libqwt6abi1.symbols
--- qwt-6.1.2/debian/libqwt6abi1.symbols2016-09-05 14:01:51.0 
+0200
+++ qwt-6.1.2/debian/libqwt6abi1.symbols2018-01-11 07:47:48.0 
+0100
@@ -1,4 +1,4 @@
-# SymbolsHelper-Confirmed: 6.1.2 alpha amd64 arm64 armel armhf hppa hurd-i386 
i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc powerpcspe ppc64 
ppc64el s390x sparc64 x32
+# SymbolsHelper-Confirmed: 6.1.2 alpha amd64 arm64 armel armhf hppa hurd-i386 
i386 kfreebsd-amd64 kfreebsd-i386 m68k mips mips64el mipsel powerpc powerpcspe 
ppc64 ppc64el s390x sh4 sparc64 x32
 libqwt.so.6abi1 libqwt6abi1 #MINVER#
  _Z11qwtTickListRK11QwtScaleDiv@Base 6.1.2
  _Z15qwtBoundingRectRK13QwtSeriesDataI10QwtPoint3DEii@Base 6.1.2
@@ -10,7 +10,7 @@
  (optional=templinst|arch=!mips 
!mipsel)_Z16qwtBoundingRectTI10QwtPoint3DE6QRectFRK13QwtSeriesDataIT_Eii@Base 
6.1.2
  
(optional=templinst)_Z16qwtBoundingRectTI12QwtSetSampleE6QRectFRK13QwtSeriesDataIT_Eii@Base
 6.1.2
  
(optional=templinst)_Z16qwtBoundingRectTI13QwtOHLCSampleE6QRectFRK13QwtSeriesDataIT_Eii@Base
 6.1.2
- (optional=templinst|arch=alpha amd64 arm64 armel armhf hppa hurd-i386 i386 
kfreebsd-amd64 kfreebsd-i386 mips64el powerpc powerpcspe ppc64 ppc64el s390x 
sparc64 
x32)_Z16qwtBoundingRectTI13QwtPointPolarE6QRectFRK13QwtSeriesDataIT_Eii@Base 
6.1.2
+ (optional=templinst|arch=alpha amd64 arm64 armel armhf hppa hurd-i386 i386 
kfreebsd-amd64 kfreebsd-i386 m68k mips64el powerpc powerpcspe ppc64 ppc64el 
s390x sh4 sparc64 
x32)_Z16qwtBoundingRectTI13QwtPointPolarE6QRectFRK13QwtSeriesDataIT_Eii@Base 
6.1.2
  
(optional=templinst)_Z16qwtBoundingRectTI17QwtIntervalSampleE6QRectFRK13QwtSeriesDataIT_Eii@Base
 6.1.2
  (optional=templinst|arch=!mips 
!mipsel)_Z16qwtBoundingRectTI7QPointFE6QRectFRK13QwtSeriesDataIT_Eii@Base 6.1.2
  _Z19qwtNormalizeDegreesd@Base 6.1.2
@@ -25,8 +25,8 @@
  _Z9qwtGetMinPKdi@Base 6.1.2
  _ZGVZNK18QwtPlainTextEngine11PrivateData10findAscentERK5QFontE5dummy@Base 
6.1.2
  _ZGVZNK18QwtPlainTextEngine11PrivateData10findAscentERK5QFontE5white@Base 
6.1.2
- (arch=alpha armel armhf mips mips64el mipsel s390x)_ZN10QByteArrayD1Ev@Base 
6.1.2
- (arch=alpha armel armhf mips mips64el mipsel s390x)_ZN10QByteArrayD2Ev@Base 
6.1.2
+ (arch=alpha armel armhf m68k mips mips64el mipsel 
s390x)_ZN10QByteArrayD1Ev@Base 6.1.2
+ (arch=alpha armel armhf m68k mips mips64el mipsel 
s390x)_ZN10QByteArrayD2Ev@Base 6.1.2
  _ZN10QwtClipper10clipCircleERK6QRectFRK7QPointFd@Base 6.1.2
  _ZN10QwtClipper11clipPolygonERK5QRectRK8QPolygonb@Base 6.1.2
  _ZN10QwtClipper11clipPolygonERK6QRectFRK8QPolygonb@Base 6.1.2
@@ -233,8 +233,8 @@
  
(optional=templinst)_ZN12QtConcurrent41VoidStoredConstMemberFunctionPointerCall4Iv18QwtPlotSpectrogramRK11QwtScaleMapS2_S4_S2_RK5QRectS5_P6QImageS9_ED1Ev@Base
 6.1.2
  
(optional=templinst)_ZN12QtConcurrent41VoidStoredConstMemberFunctionPointerCall4Iv18QwtPlotSpectrogramRK11QwtScaleMapS2_S4_S2_RK5QRectS5_P6QImageS9_ED2Ev@Base
 6.1.2
  _ZN12QwtLegendMap12removeWidgetEPK7QWidget@Base 6.1.2
- (optional=gccinternal|arch=!alpha !arm64 !armel !armhf !hppa !mips !mips64el 
!mipsel !powerpc !powerpcspe !ppc64 !ppc64el !s390x 
!sparc64)_ZN12QwtLegendMap5EntryD1Ev@Base 6.1.2
- (optional=gccinternal|arch=!alpha !arm64 !armel !armhf !hppa !mips !mips64el 
!mipsel !powerpc !powerpcspe !ppc64 !ppc64el !s390x 
!sparc64)_ZN12QwtLegendMap5EntryD2Ev@Base 6.1.2
+ (optional=gccinternal|arch=!alpha !arm64 !armel !armhf !hppa !m68k !mips 
!mips64el !mipsel !powerpc !powerpcspe !ppc64 !ppc64el !s390x !sh4 
!sparc64)_ZN12QwtLegendMap5EntryD1Ev@Base 6.1.2
+ (optional=gccinternal|arch=!alpha !arm64 !armel !armhf !hppa !m68k !mips 
!mips64el !mipsel !powerpc !powerpcspe !ppc64 !ppc64el !s390x !sh4 
!sparc64)_ZN12QwtLegendMap5EntryD2Ev@Base 6.1.2
  _ZN12QwtLegendMap6insertERK8QVariantRK5QListIP7QWidgetE@Base 6.1.2
  _ZN12QwtLegendMap6removeERK8QVariant@Base 6.1.2
  _ZN12QwtMagnifier10setEnabledEb@Base 6.1.2
@@ -1313,8 +1313,8 @@
  _ZN21QwtIntervalSeriesDataD1Ev@Base 6.1.2
  _ZN21QwtIntervalSeriesDataD2Ev@Base 6.1.2
  

Bug#886501: RFS: qwt/6.1.3-1

[Sebastiaan Couwenberg]

Hi Gudjon,

Please also fix #886171 with qwt (6.1.3-1) by incorporating the attached
changes, specifically the dh_makeshlibs override.

Kind Regards,

Bas
diff -Nru qwt-6.1.2/debian/changelog qwt-6.1.2/debian/changelog
--- qwt-6.1.2/debian/changelog  2016-09-05 14:05:19.0 +0200
+++ qwt-6.1.2/debian/changelog  2018-01-11 07:47:48.0 +0100
@@ -1,3 +1,13 @@
+qwt (6.1.2-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update symbols files with buildds' logs. Yet again.
+(closes: #886171)
+  * Override dh_makeshlibs to not fail on symbols changes,
+and set upstream version.
+
+ -- Bas Couwenberg   Thu, 11 Jan 2018 07:47:48 +0100
+
 qwt (6.1.2-6) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru qwt-6.1.2/debian/libqwt6abi1.symbols 
qwt-6.1.2/debian/libqwt6abi1.symbols
--- qwt-6.1.2/debian/libqwt6abi1.symbols2016-09-05 14:01:51.0 
+0200
+++ qwt-6.1.2/debian/libqwt6abi1.symbols2018-01-11 07:47:48.0 
+0100
@@ -1,4 +1,4 @@
-# SymbolsHelper-Confirmed: 6.1.2 alpha amd64 arm64 armel armhf hppa hurd-i386 
i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc powerpcspe ppc64 
ppc64el s390x sparc64 x32
+# SymbolsHelper-Confirmed: 6.1.2 alpha amd64 arm64 armel armhf hppa hurd-i386 
i386 kfreebsd-amd64 kfreebsd-i386 m68k mips mips64el mipsel powerpc powerpcspe 
ppc64 ppc64el s390x sh4 sparc64 x32
 libqwt.so.6abi1 libqwt6abi1 #MINVER#
  _Z11qwtTickListRK11QwtScaleDiv@Base 6.1.2
  _Z15qwtBoundingRectRK13QwtSeriesDataI10QwtPoint3DEii@Base 6.1.2
@@ -10,7 +10,7 @@
  (optional=templinst|arch=!mips 
!mipsel)_Z16qwtBoundingRectTI10QwtPoint3DE6QRectFRK13QwtSeriesDataIT_Eii@Base 
6.1.2
  
(optional=templinst)_Z16qwtBoundingRectTI12QwtSetSampleE6QRectFRK13QwtSeriesDataIT_Eii@Base
 6.1.2
  
(optional=templinst)_Z16qwtBoundingRectTI13QwtOHLCSampleE6QRectFRK13QwtSeriesDataIT_Eii@Base
 6.1.2
- (optional=templinst|arch=alpha amd64 arm64 armel armhf hppa hurd-i386 i386 
kfreebsd-amd64 kfreebsd-i386 mips64el powerpc powerpcspe ppc64 ppc64el s390x 
sparc64 
x32)_Z16qwtBoundingRectTI13QwtPointPolarE6QRectFRK13QwtSeriesDataIT_Eii@Base 
6.1.2
+ (optional=templinst|arch=alpha amd64 arm64 armel armhf hppa hurd-i386 i386 
kfreebsd-amd64 kfreebsd-i386 m68k mips64el powerpc powerpcspe ppc64 ppc64el 
s390x sh4 sparc64 
x32)_Z16qwtBoundingRectTI13QwtPointPolarE6QRectFRK13QwtSeriesDataIT_Eii@Base 
6.1.2
  
(optional=templinst)_Z16qwtBoundingRectTI17QwtIntervalSampleE6QRectFRK13QwtSeriesDataIT_Eii@Base
 6.1.2
  (optional=templinst|arch=!mips 
!mipsel)_Z16qwtBoundingRectTI7QPointFE6QRectFRK13QwtSeriesDataIT_Eii@Base 6.1.2
  _Z19qwtNormalizeDegreesd@Base 6.1.2
@@ -25,8 +25,8 @@
  _Z9qwtGetMinPKdi@Base 6.1.2
  _ZGVZNK18QwtPlainTextEngine11PrivateData10findAscentERK5QFontE5dummy@Base 
6.1.2
  _ZGVZNK18QwtPlainTextEngine11PrivateData10findAscentERK5QFontE5white@Base 
6.1.2
- (arch=alpha armel armhf mips mips64el mipsel s390x)_ZN10QByteArrayD1Ev@Base 
6.1.2
- (arch=alpha armel armhf mips mips64el mipsel s390x)_ZN10QByteArrayD2Ev@Base 
6.1.2
+ (arch=alpha armel armhf m68k mips mips64el mipsel 
s390x)_ZN10QByteArrayD1Ev@Base 6.1.2
+ (arch=alpha armel armhf m68k mips mips64el mipsel 
s390x)_ZN10QByteArrayD2Ev@Base 6.1.2
  _ZN10QwtClipper10clipCircleERK6QRectFRK7QPointFd@Base 6.1.2
  _ZN10QwtClipper11clipPolygonERK5QRectRK8QPolygonb@Base 6.1.2
  _ZN10QwtClipper11clipPolygonERK6QRectFRK8QPolygonb@Base 6.1.2
@@ -233,8 +233,8 @@
  
(optional=templinst)_ZN12QtConcurrent41VoidStoredConstMemberFunctionPointerCall4Iv18QwtPlotSpectrogramRK11QwtScaleMapS2_S4_S2_RK5QRectS5_P6QImageS9_ED1Ev@Base
 6.1.2
  
(optional=templinst)_ZN12QtConcurrent41VoidStoredConstMemberFunctionPointerCall4Iv18QwtPlotSpectrogramRK11QwtScaleMapS2_S4_S2_RK5QRectS5_P6QImageS9_ED2Ev@Base
 6.1.2
  _ZN12QwtLegendMap12removeWidgetEPK7QWidget@Base 6.1.2
- (optional=gccinternal|arch=!alpha !arm64 !armel !armhf !hppa !mips !mips64el 
!mipsel !powerpc !powerpcspe !ppc64 !ppc64el !s390x 
!sparc64)_ZN12QwtLegendMap5EntryD1Ev@Base 6.1.2
- (optional=gccinternal|arch=!alpha !arm64 !armel !armhf !hppa !mips !mips64el 
!mipsel !powerpc !powerpcspe !ppc64 !ppc64el !s390x 
!sparc64)_ZN12QwtLegendMap5EntryD2Ev@Base 6.1.2
+ (optional=gccinternal|arch=!alpha !arm64 !armel !armhf !hppa !m68k !mips 
!mips64el !mipsel !powerpc !powerpcspe !ppc64 !ppc64el !s390x !sh4 
!sparc64)_ZN12QwtLegendMap5EntryD1Ev@Base 6.1.2
+ (optional=gccinternal|arch=!alpha !arm64 !armel !armhf !hppa !m68k !mips 
!mips64el !mipsel !powerpc !powerpcspe !ppc64 !ppc64el !s390x !sh4 
!sparc64)_ZN12QwtLegendMap5EntryD2Ev@Base 6.1.2
  _ZN12QwtLegendMap6insertERK8QVariantRK5QListIP7QWidgetE@Base 6.1.2
  _ZN12QwtLegendMap6removeERK8QVariant@Base 6.1.2
  _ZN12QwtMagnifier10setEnabledEb@Base 6.1.2
@@ -1313,8 +1313,8 @@
  _ZN21QwtIntervalSeriesDataD1Ev@Base 6.1.2
  _ZN21QwtIntervalSeriesDataD2Ev@Base 6.1.2
  _ZN21QwtStyleSheetRecorder11updateStateERK17QPaintEngineState@Base 6.1.2
- (optional=gccinternal|arch=!alpha !arm64 !armel !armhf !hppa 

Bug#886815: Help with libgit2 needed to strip code copy from r-cran-git2r

[Andreas Tille]

Hi Aaron,

On Wed, Jan 10, 2018 at 06:37:17PM -0500, Aaron M. Ucko wrote:
> Andreas Tille  writes:
> 
> > Hi,
> 
> Hi, Andreas.
> 
> > gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -I. -I/usr/include/git2  
> > -DGIT_ARCH_64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DGIT_OPENSSL 
> > -DLIBGIT2_NO_FEATURES_H -DGIT_SHA1_OPENSSL - DGIT_SSH -DGIT_CURL 
> > -DGIT_USE_STAT_MTIM -DGIT_USE_NSEC -DHAVE_FUTIMENS -DHAVE_QSORT_R  
> > -fpic  -g -O2 -fdebug-prefix-map=/build/r-base-3.4.3=. 
> > -fstack-protector-strong -Wformat - Werror=format-security -Wdate-time 
> > -D_FORTIFY_SOURCE=2 -g  -c git2r.c -o git2r.o
> 
> Please try leaving off -I/usr/include/git2 to avoid this unwanted
> shadowing.  (git2.h includes the other headers as "git2/*.h", so you
> shouldn't need that flag.)

If I leave this of it ends up in a missing include refs.h (which is
in /usr/include/git2.

Kind regards

  Andreas.

PS: I also tried the other proposed solution - see my answer there.


-- 
http://fam-tille.de

Bug#886907: libgadu: ftbfs due to -Werror and gnutls_compression_get_name deprecated

[YunQiang Su]

Package: libgadu
Version: 1:1.12.2-2
Severity: serious

With recent rebuild libgadu, it failed to build, as it use -Werror,
and gnutls_compression_get_name, while this function is marked as
deprecated now.

-- 
YunQiang Su

Bug#886908: systemd enabled services unable to access shares

[Hannu Laitinen]

Package: systemd
Version: 236-2
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
- After system has booted up and systemd services have started, the 
applications are unable to access media/shares/what not after the startup.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
- My system starts with openvpn, plexmediaserver etc. After the system has 
booted up I mount smb shares from vpn tunnel and files are accessable via 
normal commandline and can browse them without any problems. But files are 
inaccessable from services that are loaded during startup. I tried to startup 
some services with init.d(or similar) and fileshares are available and all 
works as it should. 

   * What was the outcome of this action?
- Files are not showing up or are browseable.
 
  * What outcome did you expect instead?
- I should be able to browse files without issues in systemds services. This 
issue also appears with LUKS encrpyted drives and Samba. (unencrpyt after 
bootup->sambashares are not working)



-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser 3.116
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.1-4
ii  libaudit1   1:2.8.2-1
ii  libblkid1   2.30.2-0.1
ii  libc6   2.25-5
ii  libcap2 1:2.25-1.2
ii  libcryptsetup4  2:1.7.5-1
ii  libgcrypt20 1.8.1-4
ii  libgpg-error0   1.27-5
ii  libidn111.33-2.1
ii  libip4tc0   1.6.1-2+b1
ii  libkmod224-1
ii  liblz4-10.0~r131-2+b1
ii  liblzma55.2.2-1.3
ii  libmount1   2.30.2-0.1
ii  libpam0g1.1.8-3.6
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.7-2
ii  libsystemd0 236-2
ii  mount   2.30.2-0.1
ii  procps  2:3.3.12-3
ii  util-linux  2.30.2-0.1

Versions of packages systemd recommends:
ii  dbus1.12.2-1
ii  libpam-systemd  236-2

Versions of packages systemd suggests:
pn  policykit-1
pn  systemd-container  

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

-- no debconf information

Bug#886728:

[Dmitry]

The issue #886728 is related to display of Russian text in the "text
object" and ability to render russian characters in default
installation of Blender. GUI of Blender is able to display Russian text
correctly from the start. I think it is different from #833962 where
from the description it is more about UI. 

Default font Bfont, that Blender is using for render preview is a .pfb
and doesn't have international support. The report about not being able
to enter text into "text object" has been accepted in the to-do list
for future blender releases. https://developer.blender.org/T53744

I believe this bug is not related to debian.
Although if we can patch the blender code to use international font by
default, bfont.ttf (that is part of distribution) we could resolve this
 issue faster. Please decide if you consider this still a bug for
Debian Blender package. 

Please note that Debian related patch https://anonscm.debian.org/cgit/p
kg-multimedia/blender.git/tree/debian/patches/0006-
look_for_dejavu_ttf_with_fontconfig.patch?h=debian/2.79%2bdfsg0-2
for Blender is looking for "Dejavu" font, while should be looking for
"DejaVu". I don't think this is part of any reported bug so far. Please
advise if you think this deserves another bug ID.  

Bug#886901: base-files: FTBFS: cannot remove '/etc/debian_version'

[Niels Thykier]

On Wed, 10 Jan 2018 21:05:51 -0800 Daniel Schepler 
wrote:
> Source: base-files
> Version: 10
> Severity: serious
> 
> From my pbuilder build log:
> 
> ...
>  debian/rules build
> dh build
>   dh_update_autotools_config
>   debian/rules override_dh_auto_build
> make[1]: Entering directory '/build/base-files-10'
> sh debian/check-md5sum-etc profile
> sed -e 

Bug#886906: RM: libkexiv2 -- ROM; old version, no more used

[Pino Toscano]

Package: ftp.debian.org
Severity: normal

Hi,

please remove src:libkexiv2, as it is no more used by the Qt4 sources
in the archive.

Thanks,
-- 
Pino

Bug#884648: mate-panel occasionally crashes with segfault

[Vlad Orlov]

Hi,

Can you also install the debug packages [1] and use "bt full" command in gdb?
The debug packages are needed for libgtk-3, libglib-2.0, mate-panel.

This will show function names, line numbers, variable values and other useful 
info
to determine where and why the crash happens.


[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

Bug#886905: RM: konsole4 -- ROM; old version, no more required

[Pino Toscano]

Package: ftp.debian.org
Severity: normal

Hi,

please remove src:konsole4, as it is the last Qt4-based version of
konsole, and it was needed only for kile.  Since kile was switched to
its KF5 beta version, konsole4 is no more needed.

Thanks,
-- 
Pino

Bug#886777: crashes with Mustek scanner which worked before

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

tags 886777 + moreinfo
thanks


Hello Martin,


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

Do you have update the kernel after the last successful scan?

If yes please can you test with the old kernel?

Many thanks.


CU
Jörg 


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

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

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

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

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

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

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlpW/aQACgkQCfifPIyh
0l2o5xAA1hnKQL37zIIc5uTT34lPV1J+XzrlV0mFafrsR7lf8/uP7ng5LRdX4oqT
7Skuhm8lxZ8PQq6KobH+oIgr/wMbSc6A7Mjhu3gaSh4aZd0vDjfE44YBDXO2hXNI
bn0kWz1lrsb2AgpmSthC6z6ZnYbIBVp6hBe8lnuR5ZPrkrw7DEGn2cvjdPXkG+Ho
BQQG6jy+Kn6Ee1aL3/dY+Y3JFA+LYuk1T2tjbWKyHiBuZfhp8xOBgCV37MSfN3Qf
edyhu90EUk4Q0XQzx28FmtX6G2EEnNDaU5cDYNQ19jX/I6Ws8CrehIzAZkYZrwGP
gDxkDq3I5zeHDl1T5R0mNXmHS5LvIlaeN7xcsoSvnp+Uas9aYn0MUu4FSMziNz6D
09c6y3VpbX+kz402bia6oML57lEtXBnOUxSaUY4jibI+V86ua+MWdgSuoI5YibtZ
V6ItSWC36RxT2/cA+jrDRSf6hshglSluSQx81ib4LHyLRIkoYMQph09JCv20UwxK
u9ijwnFVWvXFhJ1yX2nySYdb7rHYob9kKTehk5OPyavV54ot49kLH91KbhQEYXTt
EkKjUlcUrp1zi/V0xyZTTqmjKkInJafmXoE01pwlvB6gBjeGsd8E5f52SPH6DJ9u
Jqv/nVS2CVcEKSiLZmmhNVIHua4YqlTNMUrXUd3mc68VF51Qruc=
=Q3Uo
-END PGP SIGNATURE-

Bug#886904: steam: Clicking desktop icon steam fails to launch with error libkdeinit5_steam: cannot open shared object file: No such file or directory

[Andrew Lawrence DeMarsh]

Package: steam
Version: 1.0.0.54-3
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

 Clicking on the generated desktop Steam Icon

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

 Launching from steam itself works. launching via "steam 
steam://rungameid/#" fails.

   * What was the outcome of this action?

 Game works on Internal steam play but desktop icon fails.

   * What outcome did you expect instead?

 It to Work.



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

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

Versions of packages steam depends on:
ii  debconf [debconf-2.0]1.5.65
ii  libc62.26-2
ii  libgl1-mesa-dri  17.3.1-1
ii  libgl1-mesa-glx  17.3.1-1
ii  libgpg-error01.27-5
ii  libstdc++6   7.2.0-19
ii  libtxc-dxtn-s2tc [libtxc-dxtn0]  1.0+git20151227-2
ii  libudev1 236-2
ii  libx11-6 2:1.6.4-3
ii  libxinerama1 2:1.1.3-1+b3
ii  xz-utils 5.2.2-1.3

Versions of packages steam recommends:
ii  fonts-liberation  1:1.07.4-5
ii  gnome-terminal [x-terminal-emulator]  3.26.2-2
ii  konsole [x-terminal-emulator] 4:17.08.3-1
ii  libxss1   1:1.2.2-1+b2
ii  mate-terminal [x-terminal-emulator]   1.18.2-1
ii  mlterm-tiny [x-terminal-emulator] 3.8.4-1
ii  xfce4-terminal [x-terminal-emulator]  0.8.6-1
ii  xterm [x-terminal-emulator]   331-1
ii  zenity3.26.0-2

Versions of packages steam suggests:
ii  steam-devices  1.0.0.54-3

-- debconf information:
* steam/question: I AGREE
  steam/purge:
* steam/license:

Bug#881063: apt-pinning information

[Osamu Aoki]

Hi,

I think there is serious lack of documentation on how apt system works. 

On Wed, Jan 10, 2018 at 04:31:14PM +0100, Vincent Lefevre wrote:
> Hi,
> 
> On 2018-01-10 23:11:07 +0900, Osamu Aoki wrote:
> >  do you still think your statement:
> > 
> > This is incorrect, as not compatible with multiarch. The following
> > should be used for the Package line:
> > 
> > |   Package: *:any
> > | 
> > | As far as I see the discussion referenced:
> > |https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881047#10
> > 
> > There is "this matches the documented behavior".
> 
> With the use of a ":". What is said is that:
> 
> As a special exception to the architecture wildcard rules, apt
> also accepts * in place of any, so you can write:
> 
>   /libfreetype6/:linux-*
>   /libfreetype6/:*
> 
> And this matches the documented behavior: [...]"
> 
> i.e. if you want to match all packages of any architecture, *:* is
> OK just like *:any, but * alone is not.

"*" alone seems to be treated as "*:native" (??and  "*:all"??)
architectures.  (apt-pkg/cacheset.cc)

> > At least as I see apt-doc, it is still having apt line like mine.
> 
> The apt documentation has still not been fixed.

That is where we need update first.

Other than these multiarch related syntax and regex syntax, I don't see
"Obsoletes" mentioned in dependency documentation but I see it in the
source.

The most interesing information source were:
   https://wiki.debian.org/Multiarch/HOWTO
   https://wiki.ubuntu.com/MultiarchCross

> > So where is this documentation referenced.
> > 
> > Also, does this match arch all package?
> 
> The issue is that there is currently no mention of multiarch at all in
> the apt_preferences(5) man page. I've added the APT Development Team
> to Cc.

Someone knowledgeable needs to update:
 doc/apt_preferences.5.xml
 doc/guide.dbk

Osamu

Bug#886743: virtualbox-dkms now requires package libelf-dev to work

[Chris Lamb]

Hi,

> virtualbox-dkms now requires package libelf-dev to work

Indeed, for at least 4.14.0-2-amd64.


Regards,

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

Bug#886903: gpm: FTBFS: undefined reference to `__sigemptyset'

[Daniel Schepler]

Source: gpm
Version: 1.20.4-6.2
Severity: serious

>From my pbuilder build log:

...
gcc -I. -I/build/gpm-1.20.4/src -DHAVE_CONFIG_H -include
headers/config.h -Wall -DSYSCONFDIR="\"/etc\""
-DSBINDIR="\"/usr/sbin\""  -Wall -g -D_REENTRANT -O2 -Wall -g
-D_REENTRANT -O2 -c -o prog/gpm-root.o prog/gpm-root.c
/build/gpm-1.20.4/src/prog/gpm-root.y: In function 'scr_restore':
/build/gpm-1.20.4/src/prog/gpm-root.y:963:10: warning: variable 'y'
set but not used [-Wunused-but-set-variable]
   int x,y, dumpfd;
 ^
/build/gpm-1.20.4/src/prog/gpm-root.y:963:8: warning: variable 'x' set
but not used [-Wunused-but-set-variable]
   int x,y, dumpfd;
   ^
/build/gpm-1.20.4/src/prog/gpm-root.y: In function 'postmenu':
/build/gpm-1.20.4/src/prog/gpm-root.y:1030:32: warning: pointer
targets in assignment differ in signedness [-Wpointer-sign]
#define PUTS(s,f,b)   for(curr2=s;*curr2;PUTC(*(curr2++),f,b))
   ^
/build/gpm-1.20.4/src/prog/gpm-root.y:1045:10: note: in expansion of
macro 'PUTS'
 PUTS(draw->title,draw->head,draw->back);
 ^~~~
/build/gpm-1.20.4/src/prog/gpm-root.y:1030:32: warning: pointer
targets in assignment differ in signedness [-Wpointer-sign]
#define PUTS(s,f,b)   for(curr2=s;*curr2;PUTC(*(curr2++),f,b))
   ^
/build/gpm-1.20.4/src/prog/gpm-root.y:1053:10: note: in expansion of
macro 'PUTS'
 PUTS(item->name,draw->fore,draw->back); i+=strlen(item->name);
 ^~~~
/build/gpm-1.20.4/src/prog/gpm-root.y: In function 'main':
/build/gpm-1.20.4/src/prog/gpm-root.y:1200:4: warning: implicit
declaration of function '__sigemptyset'; did you mean 'sigemptyset'?
[-Wimplicit-function-declaration]
   __sigemptyset(_mask);
   ^
   sigemptyset
At top level:
/build/gpm-1.20.4/src/prog/gpm-root.y:446:12: warning: 'f_debug_one'
defined but not used [-Wunused-function]
static int f_debug_one(FILE *f, Draw *draw)
   ^~~
gcc -L/build/gpm-1.20.4/src  -o prog/gpm-root prog/gpm-root.o   lib/libgpm.so.2
prog/gpm-root.o: In function `main':
/build/gpm-1.20.4/src/prog/gpm-root.y:1200: undefined reference to
`__sigemptyset'
collect2: error: ld returned 1 exit status
Makefile:151: recipe for target 'prog/gpm-root' failed
make[2]: *** [prog/gpm-root] Error 1
rm prog/display-coords.o prog/hltest.o prog/mev.o prog/disable-paste.o
prog/display-buttons.o
make[2]: Leaving directory '/build/gpm-1.20.4/src'
Makefile:62: recipe for target 'do-all' failed
make[1]: *** [do-all] Error 1
make[1]: Leaving directory '/build/gpm-1.20.4'
debian/rules:46: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
-- 
Daniel Schepler

Bug#785665: ntp: support for atom driver not included

[Daniel M. Weeks]

On Wed, 8 Nov 2017 05:00:50 -0600 Richard Laager  wrote:
> I recommend *against* enabling ATOM support.
> 
> It is much better to use SHM to talk to gpsd. Here are a whole bunch of
> details:
> http://www.catb.org/gpsd/gpsd-time-service-howto.html
> 

Richard,

There is nothing in that document that discourages ATOM. In fact, it
explains KPPS can be stable to +/- 1 uS. Most replies here so far are
talking about using the Raspberry Pi GPIO for KPPS.

Enabling ATOM at build time does not force it on users. As Robin pointed
out, this is only a matter of adding --with-ATOM and then users are free
to use it if they desire.

-- 
Daniel M. Weeks

Bug#886902: clanlib: please make the build reproducible

[Chris Lamb]

Hi,

> clanlib: please make the build reproducible

Looks like upstream have changed how the documentation was
generated in 2003 (in a87b9749) so this cannot go upstream...


Regards,

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

Bug#886902: clanlib: please make the build reproducible

[Chris Lamb]

Source: clanlib
Version: 1.0~svn3827-7
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that clanlib could not be built reproducibly.

This is because it loops over the filesystem in a nondeterminstic
order when generating the docs.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/500_reproducible_build.patch   1970-01-01 
05:30:00.0 +0530
--- b/debian/patches/500_reproducible_build.patch   2018-01-11 
10:14:04.026954819 +0530
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2018-01-11
+
+--- clanlib-1.0~svn3827.orig/Documentation/Reference/pce2.in
 clanlib-1.0~svn3827/Documentation/Reference/pce2.in
+@@ -142,7 +142,7 @@ sub EXEC {
+ 
+   ("init");
+ 
+-  foreach $file (@filelist) {
++  foreach $file (sort @filelist) {
+ $buffer="";
+ print "Reading $file\n" if ($::verbose);
+ $::currentfile=$file;
--- a/debian/patches/series 2018-01-11 08:33:07.045187651 +0530
--- b/debian/patches/series 2018-01-11 10:14:02.890947069 +0530
@@ -8,3 +8,4 @@
 430_privacy.patch
 440_makepair.patch
 450_unescaped_left_brace.patch
+500_reproducible_build.patch

Bug#886901: base-files: FTBFS: cannot remove '/etc/debian_version'

[Daniel Schepler]

Source: base-files
Version: 10
Severity: serious

>From my pbuilder build log:

...
 debian/rules build
dh build
  dh_update_autotools_config
  debian/rules override_dh_auto_build
make[1]: Entering directory '/build/base-files-10'
sh debian/check-md5sum-etc profile
sed -e 

Bug#886878: fwupd service startup fails.

[Mario.Limonciello]

The 4.14 kernel you are running, does it have the various spectre and meltdown 
fixes integrated already?

If so, could you please check with an older kernel without them to see if it's 
also affected?  I'm wondering if those might be causing a problem.

Bug#868891: select-default-wordlist

[Carlo Stemberger]

Hi,

this issue can be reproduced by running:

# select-default-wordlist

Best regards,

Carlo

--
 ,= ,-_-. =./  .-. _   _ ___  ___ _ __
((_/)o o(\_))  /   oo|| | | / __|/ _ \ '__|
 `-'(. .)`-'  /   /`'\| |_| \__ \  __/ |
 \_/ /   (\_;/)\__,_|___/\___|_|

Bug#886900: RFP: python-epub -- Python2 Library to open and read files in the epub version 2

[Виталий]

Package: wnpp
Severity: wishlist

Library to open and read files in the epub version 2

It only needs to be packaged according to Debian Python guidelines.

Required for: recoll

Bug#886899: recoll: epub-filter broken, requires 'python-epub' which is not packaged

[Виталий]

Package: recoll
Version: 1.22.4-1
Severity: normal

On indexing, when .epub files are met, the mime mapping redirects
execution to the epub filter, which requires the 'epub' library.

The 'epub' library, which would be packaged as 'python-epub' does not
exist at the current time. So every epub file is skipped and not
indexed like they should be.

Solution would be using an alternative library, meaning a significant
rewrite, or packaging the required library.

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

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

Versions of packages recoll depends on:
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5network55.7.1+dfsg-3+b1
ii  libqt5printsupport5   5.7.1+dfsg-3+b1
ii  libqt5webkit5 5.7.1+dfsg-1
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5xml55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-18
ii  libx11-6  2:1.6.4-3
ii  libxapian30   1.4.3-2
ii  python2.7.13-2
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages recoll recommends:
ii  aspell 0.60.7~20110707-3+b2
ii  xdg-utils  1.1.1-1
pn  xsltproc   

Versions of packages recoll suggests:
ii  antiword0.37-11+b1
pn  catdoc  
ii  ghostscript 9.20~dfsg-3.2+deb9u1
pn  libimage-exiftool-perl  
ii  poppler-utils   0.48.0-2+deb9u1
pn  pstotext
pn  python-chm  
ii  python-mutagen  1.36-1
pn  unrtf   
pn  untex   

-- no debconf information

Bug#886898: dtkwm: please make the build reproducible

[Chris Lamb]

Source: dtkwm
Version: 2.0.5-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that dtkwm could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2018-01-11 08:30:29.660547728 +0530
--- b/debian/rules  2018-01-11 08:34:59.809657210 +0530
@@ -20,3 +20,6 @@
 
 override_dh_auto_configure:
dh_auto_configure -- LIB_INSTALL_DIR=/usr/lib/$(DEB_HOST_MULTIARCH)
+
+override_dh_installexamples:
+   dh_installexamples -XMakefile

Bug#886897: samba: samba cannot export LUKs encrypted disks mounted manually after systemd boot

[David Maslen]

Package: samba
Version: 2:4.7.3+dfsg-1
Severity: important

Dear Maintainer,

I recently added a LUKS encrypted data disk to my system working system.
I have samba configured to share some of the directories from that disk,
mounted at /mnt/crypt.

By default, when my system boots I am prompted to enter my LUKs
password. When I do, the systemd boots and samba serves the /mnt/crypt
directories. My encrypted disks is mounted via the fstab, via the cryptab.

However the server is generally headless, so it suited me better to boot
the machine remotely, then ssh in and mount the encypted data disk
manually.

To achieve this I added "noauto" to the relevant line in /etc/crypttab
and /etc/fstab.

Once logged in I could run
# cryptdisks_start mydisk

followed by

# mount /mnt/crypt

While this appear to work, I noticed that I got errors when attempting
to mount the samba directories on my macbook. The connection would time
out with an error about files not not found.

Samba logs showed this error
[2018/01/11 11:14:10.716971,  0] 
../source3/smbd/service.c:774(make_connection_snum)
  canonicalize_connect_path failed for service multimedia, path 
/mnt/crypt/multimedia
[2018/01/11 11:14:14.121656,  0] 
../source3/param/loadparm.c:3066(check_usershare_stat)
  check_usershare_stat: file /var/lib/samba/usershares/ owned by uid 0 is not a 
regular file

Reverting back to unlocking the LUKS disk during the init everything
works again.

I think the difference in the two startup methods is that this
mnt-crypt.mount service is only created when I enter the LUKs password
at boot, and for some reason the Samba service depends on it having been
mounted by systemd rather than manually, post boot.

# systemctl |grep mnt-crypt
systemctl |grep mnt-crypt
  mnt-crypt.mount   
 loaded active mounted   
/mnt/crypt   


This is an inconvenience to me as it causes samba to fail without a
useful error message.

I have classified the bug as important, because it may simply appear
that samba wont export shares with underlying encryption to others.

I can reproduce this bug.

-- Package-specific info:
* /etc/samba/smb.conf present, but not attached
* /etc/samba/dhcp.conf present, but not attached

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

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

Versions of packages samba depends on:
ii  adduser   3.116
ii  dpkg  1.19.0.4
ii  libattr1  1:2.4.47-2+b2
ii  libbsd0   0.8.6-3
ii  libc6 2.26-2
ii  libldb1   2:1.2.2-2
ii  libpam-modules1.1.8-3.6
ii  libpam-runtime1.1.8-3.6
ii  libpopt0  1.16-10+b2
ii  libpython2.7  2.7.14-4
ii  libtalloc22.1.10-2
ii  libtdb1   1.3.15-2
ii  libtevent00.9.34-1
ii  lsb-base  9.20170808
ii  procps2:3.3.12-3
ii  python2.7.14-4
ii  python-dnspython  1.15.0-1
ii  python-samba  2:4.7.3+dfsg-1
ii  python2.7 2.7.14-4
ii  samba-common  2:4.7.3+dfsg-1
ii  samba-common-bin  2:4.7.3+dfsg-1
ii  samba-libs2:4.7.3+dfsg-1
ii  tdb-tools 1.3.15-2

Versions of packages samba recommends:
ii  attr1:2.4.47-2+b2
ii  logrotate   3.11.0-0.1
ii  samba-dsdb-modules  2:4.7.3+dfsg-1
ii  samba-vfs-modules   2:4.7.3+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.11.2+dfsg-5
ii  bind9utils 1:9.11.2+dfsg-5
ii  ctdb   2:4.7.3+dfsg-1
ii  ldb-tools  2:1.2.2-2
ii  ntp1:4.2.8p10+dfsg-5
ii  smbldap-tools  0.9.9-1
pn  ufw
ii  winbind2:4.7.3+dfsg-1

-- debconf information:
  samba/run_mode: daemons
  samba-common/title:

Bug#885943: Fails to start: GLX version not found

[Vasil Velichkov]

Hi Baruch,

On Sun, 31 Dec 2017 20:28:18 +0200 Baruch Even  wrote:
> Package: gr-osmosdr
> Version: 0.1.4-14
> Severity: grave
>
> I installed gr-osmosdr and tried to run it only to get an error:
>
> wx._core.PyAssertionError: C++ assertion "ok" failed at
> ../src/unix/glx11.cpp(589) in GetGLXVersion(): GLX version not found

This indicates a problem with the video drivers or packages

Please post the output of

glxinfo
dpkg -l | grep glx

Similar problems on Raspberry Pi had been resolved by installing 
/libgl1-mesa-swx11


https://medium.com/@rxseger/sdr-first-project-initial-setup-node-hackrf-gnu-radio-on-linux-os-x-rpi-3-w-fm-tuner-ee16cdc8fd82
https://www.rs-online.com/designspark/taking-the-raspberry-pi-2-for-a-test-drive-with-gnu-radio-2
https://github.com/rxseger/linuxproblems/issues/3
/

Bug#886896: rkhunter: false positive warning sshd protocol 1

[Gregor Horvath]

Package: rkhunter
Version: 1.4.2-6+deb9u1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

   $ rkhunter -s -sk

   reports:

   Checking if SSH protocol v1 is allowed   [ Warning ]

   Although it seems v1 is disallowed at compile time in Debian Stretch

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

 change  ALLOW_SSH_PROT_V1=2   in /etc/rkhunter.conf removed the wrong 
warning

   * What was the outcome of this action?

   * What outcome did you expect instead?




-- System Information:
Debian Release: 9.3
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages rkhunter depends on:
ii  binutils   2.28-5
ii  debconf [debconf-2.0]  1.5.61
ii  file   1:5.30-1+deb9u1
ii  lsof   4.89+dfsg-0.1
ii  net-tools  1.60+git20161116.90da8a0-1
ii  perl   5.24.1-3+deb9u2
ii  ucf3.0036

Versions of packages rkhunter recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4
ii  curl   7.52.1-5+deb9u3
ii  exim4-daemon-light [mail-transport-agent]  4.89-2+deb9u2
ii  iproute2   4.9.0-1+deb9u1
ii  unhide 20130526-1
ii  unhide.rb  22-2
ii  wget   1.18-5+deb9u1

Versions of packages rkhunter suggests:
ii  liburi-perl 1.71-1
ii  libwww-perl 6.15-1
ii  powermgmt-base  1.31+nmu1

-- Configuration Files:
/etc/default/rkhunter changed:
CRON_DAILY_RUN="yes"
CRON_DB_UPDATE="yes"
DB_UPDATE_EMAIL="false"
REPORT_EMAIL="root"
APT_AUTOGEN=""
NICE="0"
RUN_CHECK_ON_BATTERY="false"

/etc/logcheck/ignore.d.server/rkhunter [Errno 13] Keine Berechtigung: 
'/etc/logcheck/ignore.d.server/rkhunter'
/etc/rkhunter.conf changed:
UPDATE_MIRRORS=0
MIRRORS_MODE=1
TMPDIR=/var/lib/rkhunter/tmp
DBDIR=/var/lib/rkhunter/db
SCRIPTDIR=/usr/share/rkhunter/scripts
UPDATE_LANG="en"
LOGFILE=/var/log/rkhunter.log
USE_SYSLOG=authpriv.warning
AUTO_X_DETECT=1
ALLOW_SSH_PROT_V1=2
ENABLE_TESTS=all
DISABLE_TESTS=suspscan hidden_procs deleted_files packet_cap_apps apps
HASH_CMD=sha256sum
SCRIPTWHITELIST=/bin/egrep
SCRIPTWHITELIST=/bin/fgrep
SCRIPTWHITELIST=/bin/which
SCRIPTWHITELIST=/usr/bin/ldd
SCRIPTWHITELIST=/usr/sbin/adduser
WEB_CMD="/bin/false"
DISABLE_UNHIDE=1
INSTALLDIR=/usr


-- debconf-show failed

Bug#886849: ITP: node-puka -- Safely pass strings through shells - Node.js module

[Paul Wise]

On Wed, Jan 10, 2018 at 9:56 PM, Paolo Greppi wrote:

>  A Node.js module that provides a simple and platform-agnostic way
>  to build shell commands with arguments that pass through your shell
>  unaltered and with no unsafe side effects, whether you are running
>  on Windows or a Unix-based OS.

Uh, it would be much better to bypass the shell and use
child_process.execFile().
Please ask anything depending on node-puka to instead use that.

http://bonedaddy.net/pabs3/log/2014/02/17/pid-preservation-society/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#886895: xfsprogs: xfs_fsr option -t is being misinterpreted

[Klaus-J. Wolf]

Package: xfsprogs
Version: 4.9.0+nmu1
Severity: normal

Option -t to xfs_fsr leads to the program run for some time, but
it's 63% longer than it should.

Example:

# xfs_fsr -t 1800
xfs_fsr -m /proc/mounts -t 1800 -f /var/tmp/.fsrlast_xfs ...
...
xfs_fsr startpass 0, endpass 0, time 2933 seconds

-- System Information:
Debian Release: 9.3
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.76-kj (SMP w/6 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xfsprogs depends on:
ii  libblkid1 2.29.2-1
ii  libc6 2.24-11+deb9u1
ii  libreadline5  5.2+dfsg-3+b1
ii  libuuid1  2.29.2-1

xfsprogs recommends no packages.

Versions of packages xfsprogs suggests:
ii  acl  2.2.52-3+b1
ii  attr 1:2.4.47-2+b2
pn  quota
ii  xfsdump  3.1.6+nmu2+b1

-- no debconf information

Bug#886894: do not use daemon when systemd is available

[Antoine Beaupre]

Package: mtail
Version: 3.0.0~rc2-1
Severity: wishlist

daemon duplicates the functionality of "daemon". One shouldn't need to
install yet another "daemon" program if systemd is already installed
(and one is willing to use it of course).

Like prometheus-node-exporter, the dependency should be "daemon |
systemd-sysv" so that systemd-enabled systems do not need to install
the dependency.

There is the problem of what to do with the /etc/default/mtail
file. There are two options here:

 1. take the same route as prometheus-node-exporter and reuse the file
as an EnvironmentFile. that will be messy because there are a lot
of variables and it may make it difficult to port the
file. furthermore, it will encounter similar issues there, like
#886891

 2. just specify a sane set of default settings that can be overriden
using normal systemd mechanisms, for example:

https://askubuntu.com/a/659268

I believe it should be possible to replace the `daemon` dependency for
mtail without problems. The templating features of systemd can also
make it possible to easily start multiple instances of mtail, by the
way...

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

Kernel: Linux 4.9.0-5-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 mtail depends on:
ii  adduser  3.115
pn  daemon   
ii  libc62.24-11+deb9u1

mtail recommends no packages.

mtail suggests no packages.

Bug#886893: document how to hook into prometheus

[Antoine Beaupre]

Package: mtail
Severity: wishlist

So I have figured out that mtail can send out metrics as Prometheus
wants them, under /prometheus. But I did this mostly by having my hand
held by the maintainer - there is very little documentation in the
Debian package itself on how to configure it.

It would be nice to have a simple README.Debian file that would say
how to deploy config files (and where) and how to hook it into
Prometheus.

I'm particularly interested in understanding how I can register mtail
in Prometheus under the same host as an already existing node_exporter
instance, so that they can be displayed in (say) the same column in a
Grafana dashboard.

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

Kernel: Linux 4.9.0-5-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 mtail depends on:
ii  adduser  3.115
pn  daemon   
ii  libc62.24-11+deb9u1

mtail recommends no packages.

mtail suggests no packages.

Bug#886892: evince: Prints n^2 copies if multiple copies selected

[Peter Chubb]

Package: evince
Version: 3.26.0-2
Severity: normal

Dear Maintainer,

On some PDF or PS documents, attempting to print more than 10 copies
results in n*n copies being printed instead.  The printer is a Kyocera
network-connected printer; cups says it's driverless.

I suspect that Evince is rewriting the printable file to say print n
times, and also asking CUPS to print n times.

Peter C

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64

Kernel: Linux 4.15.0-rc7+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages evince depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-2
ii  evince-common3.26.0-2
ii  gsettings-desktop-schemas3.24.1-2
ii  libatk1.0-0  2.26.1-2
ii  libc62.26-1
ii  libcairo-gobject21.15.8-3
ii  libcairo21.15.8-3
ii  libevdocument3-4 3.26.0-2
ii  libevview3-3 3.26.0-2
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.54.2-5
ii  libgnome-desktop-3-123.26.2-4
ii  libgtk-3-0   3.22.26-2
ii  libnautilus-extension1a  3.26.2-1
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libsecret-1-00.18.5-5
ii  shared-mime-info 1.9-2

Versions of packages evince recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.2-1
ii  dbus-x11 [dbus-session-bus]   1.12.2-1

Versions of packages evince suggests:
ii  gvfs 1.34.1-2
pn  nautilus-sendto  
ii  poppler-data 0.4.8-2
ii  unrar1:5.5.8-1

-- no debconf information

Bug#886891: working default config in systemd (no extra backquotes)

[Antoine Beaupre]

Package: prometheus-node-exporter
Version: 0.15.2+ds-1
Severity: wishlist

It would be nice not to have to edit the
/etc/default/prometheus-node-exporter file when we use systemd. It is,
after all, the default configuration and it would seem to me better to
have a default config that works there.

I understand the desire to support other init systems, however, so
what I would propose is to find a way to make this work with both
configurations, by default. There are good ways in systemd to override
default configurations, for example:

https://askubuntu.com/a/659268

So maybe the systemd config should not use the /etc/default file,
which should be reserved for the init script. Instead, the defaults
should be written directly in the .service file and then can be
overriden in the normal way, as needed.

Why aren't those defaults set in the source anyways? It seems to me it
would be better to just have sane defaults there... 

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

Kernel: Linux 4.9.0-5-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 prometheus-node-exporter depends on:
ii  libc6 2.24-11+deb9u1
ii  systemd-sysv  232-25+deb9u1

prometheus-node-exporter recommends no packages.

prometheus-node-exporter suggests no packages.

-- Configuration Files:
/etc/default/prometheus-node-exporter changed:
ARGS="--collector.diskstats.ignored-devices=^(ram|loop|fd|(h|s|v|xv)d[a-z]|nvmed+nd+p)d+$
 \
  --collector.filesystem.ignored-mount-points=^/(sys|proc|dev|run)($|/) \
  --collector.netdev.ignored-devices=^lo$ \
  --collector.ntp \
  --collector.logind \
  --collector.systemd \
  --collector.textfile.directory=/var/lib/prometheus/node-exporter"


-- no debconf information

Bug#886890: Fix for found typos

[Sebastian Rasmussen]

Package: debian-policy
Version: 4.1.3.0

While reading the Debian policy document I was inspired to look
for typos. Attached is a patch that fixes the ones that I found.

 / Sebastian
From 349e88beaffbb429731a4ac1b8f1c00a6cfe2af0 Mon Sep 17 00:00:00 2001
From: Sebastian Rasmussen 
Date: Thu, 11 Jan 2018 02:14:36 +0100
Subject: [PATCH] Fix a few typos.

---
 README.md  | 2 +-
 copyright-format-1.0.xml   | 2 +-
 historical/README.shlibdeps| 2 +-
 perl-policy.xml| 2 +-
 policy/ch-opersys.rst  | 2 +-
 tools/policy-bug-report| 2 +-
 virtual-package-names-list.txt | 4 ++--
 7 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 3896275..bcad4d8 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@ Link Up: https://www.debian.org/
 + Request tracker:: 
 
 Debian Policy uses a formal procedure and a set of user tags to manage
-the lifecycle of change proposals. For definitions of those tags and
+the life cycle of change proposals. For definitions of those tags and
 proposal states and information about what the next step is for each
 phase, see [Policy changes process](./Process.md).
 
diff --git a/copyright-format-1.0.xml b/copyright-format-1.0.xml
index 58d7c49..0423202 100644
--- a/copyright-format-1.0.xml
+++ b/copyright-format-1.0.xml
@@ -591,7 +591,7 @@ Copyright 2009, 2010 Angela Watts
 
   Only the wildcards * and ?
   apply; the former matches any number of characters (including
-  none), the latter a single character.  Both match slashs
+  none), the latter a single character.  Both match slashes
   (/) and leading dots, unlike shell globs.
   The pattern *.in therefore matches any
   file whose name ends in .in anywhere in
diff --git a/historical/README.shlibdeps b/historical/README.shlibdeps
index 34a4285..e09261d 100644
--- a/historical/README.shlibdeps
+++ b/historical/README.shlibdeps
@@ -31,7 +31,7 @@ libraries according to ldd:
 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)
 
 Now if we leek a bit closed we see that xcdrgtk actually only links to
-a couple of those libraries directly. The actual depencies are a tree
+a couple of those libraries directly. The actual dependencies are a tree
 which looks something like this: (anyone interested in writing a tool
 to make such a graph?)
 
diff --git a/perl-policy.xml b/perl-policy.xml
index 9888287..4471d68 100644
--- a/perl-policy.xml
+++ b/perl-policy.xml
@@ -560,7 +560,7 @@ $(MAKE) OPTIMIZE="-O2 -g -Wall"
 As with modules, packages using debhelper may
 use
 dh_perl1
-to automatically generate dependences (see ).
   
 
diff --git a/policy/ch-opersys.rst b/policy/ch-opersys.rst
index 3e3a1c7..a6a3114 100644
--- a/policy/ch-opersys.rst
+++ b/policy/ch-opersys.rst
@@ -67,7 +67,7 @@ Debian Policy. The following exceptions to the FHS apply:
 5.  The requirement that ``/usr/local/share/man`` be "synonymous" with
 ``/usr/local/man`` is relaxed to a recommendation
 
-6.  The requirement that windowmanagers with a single configuration file
+6.  The requirement that window managers with a single configuration file
 call it ``system.*wmrc`` is removed, as is the restriction that the
 window manager subdirectory be named identically to the window
 manager name itself.
diff --git a/tools/policy-bug-report b/tools/policy-bug-report
index 5d68617..110b6ac 100755
--- a/tools/policy-bug-report
+++ b/tools/policy-bug-report
@@ -36,7 +36,7 @@ sub die_soap {
 die "SOAP error: $error\n";
 }
 
-# Initialize the SOAP::Lite object with the currect URL and namespace and
+# Initialize the SOAP::Lite object with the correct URL and namespace and
 # return it.
 sub init_soap {
 my $soap = SOAP::Lite->uri ($NAMESPACE)->proxy ($URL);
diff --git a/virtual-package-names-list.txt b/virtual-package-names-list.txt
index 4f82f88..30f1996 100644
--- a/virtual-package-names-list.txt
+++ b/virtual-package-names-list.txt
@@ -31,7 +31,7 @@ The procedure for updating the list is as follows:
 
 3. Mail the maintainer of the virtual package name list (which is the
Debian Policy list ) notifying them
-   of the consensus reached (or your suggestions if noone objected).
+   of the consensus reached (or your suggestions if no one objected).
Please update the bug report at the same time.
 
Please include a proposed brief description of the new virtual name(s)
@@ -68,7 +68,7 @@ Database
  virtual-mysql-client-core  a MySQL-database-compatible client core package
  virtual-mysql-server   a MySQL-database-compatible server package
  virtual-mysql-server-core  a MySQL-database-compatible server core package
- virtual-mysql-testsuitea MySQL-database-compatible test suite packag
+ virtual-mysql-testsuitea 

Bug#835210: May be using the Grafana Debian package for help?

[Antoine Beaupre]

On Mon, May 08, 2017 at 03:33:27PM +0200, Stephane Bortzmeyer wrote:
> Dmitry said "I'm not sure if I can make it happen as Grafana became
> very difficult to package". Well, upstream provides Debian packages so
> they probably can be used to unstuck this very old issue.
> 
> http://docs.grafana.org/installation/debian/#apt-repository

I confirm this package works well. I have installed in Debian Stretch
to graph a Prometheus instance and it worked flawlessly.

I strongly recommend we merge with that work.

A.


signature.asc
Description: PGP signature

Bug#886886: ros-bond-core: FTBFS on m68k: timeout generating Python from MSG bond/Constants

[Aaron M. Ucko]

John Paul Adrian Glaubitz  writes:

> Hi Aaron!

Hi, Adrian.

> Either way, thanks for spotting this issue. I will look into it and will
> file a qemu-m68k bug if my initial suspicion turns out to be right.

Great, thanks.  Your hypothesis would certainly explain why this package
suddenly broke.

Meanwhile, what's your take on
https://buildd.debian.org/status/fetch.php?pkg=tinyssh=m68k=20180101-1=1515027549=0?
More qemu lossage or an actual tinyssh bug?

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#886889: Fix insecure password generation in stretch

[Joel Johnson]

Package: qtpass
Version: 1.1.6-1
Tags: security
Severity: important

It is noted in the changelog for version 1.2.1-1, but shouldn't the fix 
be applied to the stretch package as well?


Per QtPass upstream (open disclosure), passwords generated from within 
the application are insecure due to not being properly seeded.


github issue
https://github.com/IJHack/QtPass/issues/338

github PR with released fix in 1.2.1 for applying to stretch version
https://github.com/IJHack/QtPass/pull/342

CVE
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18021

Bug#886888: monitoring-plugins-basic: check_smtp bug with custom command and SSL

[Iustin Pop]

Package: monitoring-plugins
Version: 2.2-3
Severity: important
Tags: patch

Hi,

The check_smtp command has a bug when both SSL is enable and check
command (-C) are passed.

The code for check commands is:

while (n < ncommands) {
xasprintf (_str, "%s%s", commands[n], "\r\n");
my_send(cmd_str, strlen(cmd_str));

…

And this works when SSL is not used, because n in initialized at the
start of main, and not used until this block. However, when SSL is
enabled, n is assigned the size of the server's second EHLO response (I
think in bytes), which will usually be significantly higher than the
command passed. As such, no commands are executed and no responses are
checked, which - silently - defeats the desired checks and results in a
success value.

I've attached a trivial patch which simply initializes n before it is
used, and marked as important because of the silent data loss and
triviality of fixing this. Would appreciate if you can apply and forward
upstream.

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

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

Versions of packages monitoring-plugins depends on:
ii  monitoring-plugins-basic 2.2-3
ii  monitoring-plugins-standard  2.2-3

monitoring-plugins recommends no packages.

Versions of packages monitoring-plugins suggests:
ii  icinga2 2.7.0-1
ii  nagios-plugins-contrib  21.20170222

-- no debconf information
Description: Fix check_smtp handling of custom commands with SSL
Author: Iustin Pop 
--- a/plugins/check_smtp.c
+++ b/plugins/check_smtp.c
@@ -293,6 +293,7 @@
printf("%s", buffer);
}
 
+   n = 0;
while (n < ncommands) {
xasprintf (_str, "%s%s", commands[n], "\r\n");
my_send(cmd_str, strlen(cmd_str));

Bug#886807: Acknowledgement (gnuradio: QT GUI fails with AttributeError: 'NoneType' object has no attribute 'toByteArray')

[Vasil Velichkov]

Tags: patch

Here is my attempt to fix this bug

На 10.01.2018 в 05:12, Debian Bug Tracking System написа:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 886807: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886807.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  A. Maitland Bottoms 

If you wish to submit further information on this problem, please
send it to 886...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.



>From 80997947ce9278b1be5caf1f17afed164e32af85 Mon Sep 17 00:00:00 2001
From: Vasil Velichkov 
Date: Thu, 11 Jan 2018 00:32:37 +
Subject: [PATCH] Fix AttributeError: 'NoneType' object has no attribute
 'toByteArray'

Debian Bug #886807
---
 gr-uhd/apps/uhd_fft| 6 +++---
 gr-uhd/apps/uhd_siggen_gui | 4 ++--
 grc/blocks/options.xml | 2 +-
 grc/core/generator/flow_graph.tmpl | 2 +-
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/gr-uhd/apps/uhd_fft b/gr-uhd/apps/uhd_fft
index 44bd270..fc944de 100755
--- a/gr-uhd/apps/uhd_fft
+++ b/gr-uhd/apps/uhd_fft
@@ -40,7 +40,7 @@ import sip
 import threading
 import time
 from distutils.version import StrictVersion
-from PyQt5 import Qt
+from PyQt5 import Qt, QtCore
 from gnuradio import eng_notation
 from gnuradio import eng_arg
 from gnuradio import gr
@@ -60,7 +60,7 @@ class uhd_fft(gr.top_block, Qt.QWidget, UHDApp):
 """
 def __init__(self, args):
 gr.top_block.__init__(self, "UHD FFT")
-Qt.QWidget.__init__(self)
+Qt.QWidget.__init__(self, args=args)
 UHDApp.__init__(self, args=args, prefix="UHD FFT")
 ##
 # Init QT App
@@ -82,7 +82,7 @@ class uhd_fft(gr.top_block, Qt.QWidget, UHDApp):
 self.top_grid_layout = Qt.QGridLayout()
 self.top_layout.addLayout(self.top_grid_layout)
 self.settings = Qt.QSettings("GNU Radio", "uhd_fft")
-self.restoreGeometry(self.settings.value("geometry").toByteArray())
+self.restoreGeometry(self.settings.value("geometry", type=QtCore.QByteArray))
 
 ##
 # Parameters
diff --git a/gr-uhd/apps/uhd_siggen_gui b/gr-uhd/apps/uhd_siggen_gui
index 52c0182..16f472f 100755
--- a/gr-uhd/apps/uhd_siggen_gui
+++ b/gr-uhd/apps/uhd_siggen_gui
@@ -39,7 +39,7 @@ import threading
 import time
 from distutils.version import StrictVersion
 from PyQt5 import Qt
-from PyQt5.QtCore import pyqtSlot
+from PyQt5.QtCore import pyqtSlot, QByteArray
 from gnuradio import analog
 from gnuradio import eng_notation
 from gnuradio import gr
@@ -85,7 +85,7 @@ class uhd_siggen_gui(Qt.QWidget):
 self.top_grid_layout = Qt.QGridLayout()
 self.top_layout.addLayout(self.top_grid_layout)
 self.settings = Qt.QSettings("GNU Radio", "uhd_siggen_gui")
-self.restoreGeometry(self.settings.value("geometry").toByteArray())
+self.restoreGeometry(self.settings.value("geometry", type=QByteArray))
 
 ##
 # Widgets + Controls
diff --git a/grc/blocks/options.xml b/grc/blocks/options.xml
index 1ef1e9d..414a167 100644
--- a/grc/blocks/options.xml
+++ b/grc/blocks/options.xml
@@ -16,7 +16,7 @@ from grc_gnuradio import wxgui as grc_wxgui
 import wx
 #end if
 #if $generate_options() == 'qt_gui'
-from PyQt5 import Qt
+from PyQt5 import Qt, QtCore
 import sys
 #end if
 #if not $generate_options().startswith('hb')
diff --git a/grc/core/generator/flow_graph.tmpl b/grc/core/generator/flow_graph.tmpl
index 9fdc1fb..8b18184 100644
--- a/grc/core/generator/flow_graph.tmpl
+++ b/grc/core/generator/flow_graph.tmpl
@@ -118,7 +118,7 @@ class $(class_name)(gr.top_block, Qt.QWidget):
 self.top_layout.addLayout(self.top_grid_layout)
 
 self.settings = Qt.QSettings("GNU Radio", "$class_name")
-self.restoreGeometry(self.settings.value("geometry").toByteArray())
+self.restoreGeometry(self.settings.value("geometry", type=QtCore.QByteArray))
 #elif $generate_options == 'no_gui'
 
 
-- 
2.15.1

Bug#839880: proftpd-basic: proftpd server instance crashed with signal 11

[Олег Мороз]

Thank a lot. Will subscribe.

09.01.2018 19:45, Hilmar Preuße пишет:

forwarded 839880 http://bugs.proftpd.org/4334
stop

Am 09.01.2018 um 09:24 teilte Олег Мороз mit:

Hi Олег,

I've escalated the bug to here [1]. Feel to subscribe to the bug to 
get informed about news.


Hilmar

[1] http://bugs.proftpd.org/4334


Have tried

root@sim-ng-data:/home/vniiem# cat /var/log/proftpd/proftpd.log
...
...
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): -BEGIN STACK TRACE-
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): [0] /usr/sbin/proftpd(+0x1f3b0) 
[0x563c3354f3b0]
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): [1] /usr/sbin/proftpd(+0x1f3b0) 
[0x563c3354f3b0]



root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 0x1f3b0
./src/pool.c:546

but () gives error

root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 
0x563c3354f3b0()

bash: syntax error near unexpected token `('

and

root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 
(0x563c3354f3b0)

bash: syntax error near unexpected token `('


03.01.2018 15:47, Hilmar Preuße пишет:

Am 03.01.2018 um 09:39 teilte Олег Мороз mit:

Hi Oleg,

Happy new year!

according to my knowledge the most top line of the stack trace is 
the relevant one.


Your first addr2line command leads me to line 1312 in 
./contrib/mod_sftp/auth.c. This line just contains a call to 
function pr_cmd_dispatch_phase(). This function however is 
implemented in ./src/main.c . So to learn in which part of the 
function the crash happens one has to go one line up in the stack 
trace.


So please repeat the command for the most upper line in your stack 
trace and send me the output. Please use the addresses in the (), 
I've no clue why the 64bit addresses can't be used.


Many thanks!
  Hilmar


So sorry for delay, i'm on vacation.

I believe that problem is in mod_sftp.so

part of proftpd.log stack trace
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [5] 
/usr/lib/proftpd/mod_sftp.so(+0x3c7ef) [0x7f5e93b9d7ef]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [6] 
/usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f5e93b9dc31]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [7] 
/usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363) 
[0x7f5e93b7c9ad]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07) 
[0x7f5e93b70a07]



# addr2line -e /usr/lib/proftpd/mod_sftp.so 0x3c7ef
./contrib/mod_sftp/auth.c:1312


# addr2line -e /usr/lib/proftpd/mod_sftp.so +0xfa07
./contrib/mod_sftp/mod_sftp.c:247


unfortunatelly i cant use 64 bit addresses like 0x7f5e93b9d7ef , 
because in that case addr2line gives ??:0




Log Files snipped.

Bug#858398: curl: Please migrate to openssl1.1 in Buster

[Alessandro Ghedini]

On Sun, Dec 17, 2017 at 11:16:29PM +0200, Adrian Bunk wrote:
> On Fri, Dec 08, 2017 at 05:44:55PM +0100, Ondřej Surý wrote:
> > Hi,
> > 
> > just innocent bystander here with an observation:
> > 
> > These two options:
> > 
> > a)
> > > I do agree it's the correct solution though, and it would be a good 
> > > opportunity
> > > to finally sync SONAME with upstream
> > 
> > b)
> > > Because of 1 I think we should change the package name (and SONAME) for
> > > libcurl3.  I don't think 2 is appropriate.
> > 
> > are mutually exclusive, so even if we rename the share library packages
> > to libcurl4*, they would have to conflict with libcurl3* because they
> > would contain same files.
> > 
> > And the SONAME is already libcurl.so.4 (at least on stretch):
> > 
> > $ objdump -p /usr/lib/x86_64-linux-gnu/libcurl* | grep SONAME
> >   SONAME   libcurl-gnutls.so.4
> >   SONAME   libcurl-gnutls.so.4
> >   SONAME   libcurl-gnutls.so.4
> >   SONAME   libcurl.so.4
> >   SONAME   libcurl.so.4
> >   SONAME   libcurl.so.4
> > 
> > So in this case, unfortunately, bumping the SONAME is actually something
> > different than changing package name to match to SONAME of the library. 
> >...
> 
> Similar to all the v5 postfixed packages in Debian for C++ ABI changes 
> in GCC 5, what matter here is actually not the SONAME but the package
> name and that the new package conflicts with the old package.
> 
> This is sufficient to fix the issue for all packages using curl.
> 
> And different from breaks on specific packages, it will also force an
> upgrade of packages from backports.
> 
> Non-packaged software is a different topic, but the whole OpenSSL 
> situation in stretch is already a mess for that.
> 
> This whole transition looks pretty straightforward to me,
> please let me know if there is anything where I could help.

Following Adrian's comment, I prepated a patch that:

 * Renames *all* lincurl3* packages to libcurl4* (with Conflicts+Replaces)
 * Removes the hacks for old SONAME and updates symbols (as Ondrej correctly
   pointed out, the SONAME doesn't actually change as ww already ship a
   "libcurl.so.4", but the lib symlinks and the symbols do)
 * Makes the OpenSSL libcurl build against OpenSSL 1.1

I think this satisfies all the requirements for the OpenSSL migration, as well
as finally cleaning up the mess from the last botched transition as an added
bonus.

Thoughts?

The patch is at https://salsa.debian.org/debian/curl/merge_requests/2

Cheers


signature.asc
Description: PGP signature

Bug#858398: Proposed (lib)curl switch to openssl 1.1

[Alessandro Ghedini]

On Sat, Dec 02, 2017 at 06:09:39PM +0100, Julien Cristau wrote:
> On Thu, Nov 23, 2017 at 15:49:26 +, Ian Jackson wrote:
> > Reasons I am aware that it *might* be a bad idea are:
> > 
> > 1. libcurl exposes parts of the openssl ABI, via
> >CURLOPT_SSL_CTX_FUNCTION, and this would be an implicit ABI break
> >without libcurl soname change.  This is not good, but it seems like
> >the alternative would be to diverge our soname from everyone else's
> >for the same libcurl.
> > 
> > 2. For the reason just mentioned, it might be a good idea to put in a
> >Breaks against old versions of packages using
> >CURLOPT_SSL_CTX_FUNCTION.  However, (a) I am not sure if this is
> >actually necessary (b) in any case I don't have a good list of all
> >the appropriate versions (c) maybe this would need coordination.
> > 
> > 3. This might be an implicit a "transition" (in the Debian release
> >management sense) which I would be mishandling, or starting without
> >permission, or something.
> > 
> Because of 1 I think we should change the package name (and SONAME) for
> libcurl3.  I don't think 2 is appropriate.

Following discussion on the ticket (#858398) it was suggested to follow the
strategy used for the GCC 5 C++ ABI transition, that is, rename the libcurl
package and add Conflicts+Replaces for teh old package.

Due to the fact that the previous transition (libcurl3 -> libcurl4) was
partially reverted (in 2007 according to the changelog), I'd also like to
taeke this opportunity to finally complete that as well, so I made a patch
to not only rename libcurl3 -> libcurl4, but also (libcurl3-gnutls,
libcurl3-nss) -> (libcurl4-gnutls, libcurl4-nss), and remove the hacks needed
to keep compatibility with the previous ABI.

Thoughts?

The patch is at https://salsa.debian.org/debian/curl/merge_requests/2

CHeers


signature.asc
Description: PGP signature

Bug#886886: ros-bond-core: FTBFS on m68k: timeout generating Python from MSG bond/Constants

[John Paul Adrian Glaubitz]

Hi Aaron!

On 01/11/2018 12:48 AM, Aaron M. Ucko wrote:
>   [ 54%] Generating Python from MSG bond/Constants
>   cd /<>/obj-m68k-linux-gnu/bond && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/bond/msg/Constants.msg -Ibond:/<>/bond/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o 
> /<>/obj-m68k-linux-gnu/devel/lib/python2.7/dist-packages/bond/msg
>   E: Build killed with signal TERM after 600 minutes of inactivity

Please note that such stalls are likely to indicate a bug in qemu. In fact,
I'm rather confident that this is a qemu issue and not a problem with this
particular package as we have had similar issues in the past many times.

Also, the last successful build was on December 26th while I updated the
qemu version used on the m68k buildds with a qemu-m68k snapshot on December
28th. So, I think it's very likely that we have run into a qemu regression
here.

Either way, thanks for spotting this issue. I will look into it and will
file a qemu-m68k bug if my initial suspicion turns out to be right.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#886877: stretch-pu: package gosa-plugin-pwreset/0.99.4-1+deb9u1

[Holger Levsen]

On Wed, Jan 10, 2018 at 09:27:38PM +0100, Mike Gabriel wrote:
> We identified a deprecated constructor call in the PHP package 
> gosa-plugin-pwreset.

to be clear, this is:

>++ Add 0001_fix-deprecated-constructor-call.patch. (Closes: #886848).

(which is fixed in sid).


-- 
cheers,
Holger (not involved in this at all, except reading d-edu mail)


signature.asc
Description: PGP signature

Bug#886886: ros-bond-core: FTBFS on m68k: timeout generating Python from MSG bond/Constants

[Aaron M. Ucko]

Source: ros-bond-core
Version: 1.8.1-2
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: m68k

Builds of ros-bond-core 1.8.1-2 for m68k (admittedly not a release
architecture) have been failing, per the below excerpt from [1]:

  [ 54%] Generating Python from MSG bond/Constants
  cd /<>/obj-m68k-linux-gnu/bond && 
../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
/<>/bond/msg/Constants.msg -Ibond:/<>/bond/msg 
-Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o 
/<>/obj-m68k-linux-gnu/devel/lib/python2.7/dist-packages/bond/msg
  E: Build killed with signal TERM after 600 minutes of inactivity

This version already received a second build attempt, so the problem
wasn't just a one-off glitch, and builds are otherwise generally
quick.  (The only other instance I see on [2] of taking more than an
hour was an m68k build of 1.7.16-3+b1 in February of 2016 that took
about 9.5 hours; most other builds were well under an hour.)

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=ros-bond-core=m68k=1.8.1-2=1515504032=0
[2] https://buildd.debian.org/status/logs.php?pkg=ros-bond-core

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#886815: Help with libgit2 needed to strip code copy from r-cran-git2r

[Aaron M. Ucko]

Andreas Tille  writes:

> Hi,

Hi, Andreas.

> gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -I. -I/usr/include/git2  
> -DGIT_ARCH_64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DGIT_OPENSSL 
> -DLIBGIT2_NO_FEATURES_H -DGIT_SHA1_OPENSSL - DGIT_SSH -DGIT_CURL 
> -DGIT_USE_STAT_MTIM -DGIT_USE_NSEC -DHAVE_FUTIMENS -DHAVE_QSORT_R  -fpic  
> -g -O2 -fdebug-prefix-map=/build/r-base-3.4.3=. -fstack-protector-strong 
> -Wformat - Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c 
> git2r.c -o git2r.o

Please try leaving off -I/usr/include/git2 to avoid this unwanted
shadowing.  (git2.h includes the other headers as "git2/*.h", so you
shouldn't need that flag.)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#878971: [libjaxb-java] libjaxb-java cause guacamole start fail

[Takuya Ono]

I am testing libjaxb-java 2.3.0-3. Recently, jaxb-impl.jar was divided
into jaxb-runtime.jar and jaxb-core.jar. And, jaxb-impl.jar just
symbolic link to jaxb-runtime.jar. But, it does not include jaxb-core.jar.
The other hand, guacamole 0.9.9 reference only jaxb-impl.jar.

Workaround:
Make symbolic link to jaxb-core.jar on
/usr/share/guacamole/guacamole/WEB-INF/lib/.

Example:
root:/usr/share/guacamole/guacamole/WEB-INF/lib# ln -s
../../../../java/jaxb-core.jar

> How shoud we resolve this problem? change libjaxb-java or guacmole?

I believe that the root cause is libjaxb-java's specification change.

Ref: We discussed on my blog. http://on-o.com/page/diary/20171009.html
(Japanese)
--
Takuya Ono  

Bug#759533: alien: Converted rpm won't be installed on Fedora system

[Martin Dorey]

Following a similar report

, I found that much the same thing has been reported upstream as Generated
RPM files un-necessarily conflict with package "filesystem"
.  The raiser
supplied a fix which the "new" upstream maintainer seems to have accepted,
though the ticket is still open and there hasn't been a release in the
intervening year.

Bug#886878: fwupd service startup fails.

[Abhijit Hoskeri]

This is what I see:



Jan 10 13:45:17 ahoskeri-lnx systemd[1]: Starting Firmware update daemon...
Jan 10 13:45:17 ahoskeri-lnx fwupd[23072]: /usr/lib/fwupd/fwupd: error while 
loading shared libraries: libffi.so.6: cannot enable executable stack as shared 
object requires: Operation not permitted


In the systemd service file:



[Service]
Type=dbus
BusName=org.freedesktop.fwupd
ExecStart=/usr/lib/fwupd/fwupd
MemoryDenyWriteExecute=yes
^^^ this is the problem. I need to change this to no to have it work.



the process will start correctly if started outside of systemd - since it would 
not run with that restriction. Also perhaps a newer kernel is required to 
systemd to actually enforce this? I am running linux 4.14 from debian unstable.





Thanks, Abhijit.

On Jan 10, 2018, at 01:40 PM, mario.limoncie...@dell.com wrote:


I couldn't reproduce this myself. As far as I'm aware there is no FFI generated 
code in fwupd.

I think we'll need to see some more logs and/or journal output to figure out 
what's going on for you.

Also filed this upstream, so please feel free to discuss there as well.
https://github.com/hughsie/fwupd/issues/359



-Original Message-
From: Limonciello, Mario
Sent: Wednesday, January 10, 2018 2:47 PM
To: 'Abhijit Hoskeri' ; '886...@bugs.debian.org'
<886...@bugs.debian.org>; Debian Bug Tracking System

Subject: RE: Bug#886878: fwupd service startup fails.


Thanks for filing this.


Can you please share the associated journal output when it tries to launch?
Does it hang?


Or does it just not launch at all?



-Original Message-
From: Abhijit Hoskeri [mailto:abhijithosk...@icloud.com]
Sent: Wednesday, January 10, 2018 1:40 PM
To: Debian Bug Tracking System 
Subject: Bug#886878: fwupd service startup fails.

Package: fwupd
Version: 1.0.3-1
Severity: important

Dear Maintainer,

fwupd startup fails with the default systemd service configuation - the
service seems to require libffi generated code, and the systemd
directive 'MemoryDenyWriteExecute=yes' prevents libffi from executing
generated code.

Disabling this in the systemd service MemoryDenyWriteExecute allows the
service startup to proceed as expected.

Thanks,
Abhijit


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

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

Versions of packages fwupd depends on:
ii libappstream-glib8 0.7.4-1
ii libarchive13 3.2.2-3.1
ii libc6 2.26.9000+20180108.401311cf-0experimental0
ii libcolorhug2 1.3.3-2
ii libefivar1 32-2
ii libelf1 0.170-0.2
ii libfwup1 10-1
ii libfwupd2 1.0.3-1
ii libglib2.0-0 2.54.3-1
ii libgnutls30 3.6.1-1
ii libgpg-error0 1.27-5
ii libgpgme11 1.10.0-1
ii libgudev-1.0-0 232-1
ii libgusb2 0.2.11-1
ii libpolkit-gobject-1-0 0.113-6
ii libsmbios2 2.3.1-2
ii libsoup2.4-1 2.60.2-2
ii libsqlite3-0 3.21.0-1
ii libuuid1 2.30.2-0.1

Versions of packages fwupd recommends:
ii fwupdate 10-1
ii python3 3.6.4-1

fwupd suggests no packages.

-- no debconf information

Bug#886852: NVidia driver : upgrade to version 384.111

[Andreas Beckmann]

On 2018-01-10 15:25, Luca Boccassi wrote:
> I'm a little confused as what their blobs could possible have to do
> with spectre/meltdown to be honest

meltdown does not seem to be an issue, but for spectre it is not
neccessarily the GPU bits being fixed, but the CPU side of the driver -
which can run untrusted user supplied code (e.g. compiling shaders) ...
that could be comparable to the sandboxed javascript in the browser
accessing all the browser memory.

> - but in general it sounds like a
> good idea to move 384 to stable-p-u, since it's won't be the last CVE
> we get and as you said 375 is dead and buried.
> 
> Andreas, what do you think?

Just uploaded to stretch-backports, will need to go through backports-new.
Untested on my side - please try it out :-)


Andreas

Bug#880170: (no subject)

[wei hong]

I can also confirm this issue with apt. It appears the upstream file does not 
exist and that may be causing the error.

apt: 1.6~alpha6

E: Failed to fetch 
https://deb.debian.org/debian-security/dists/stable/updates/contrib/i18n/Translation-en

If you follow that URL you will get a 404. This returns an error to apt and may 
cause the hash to be null or miscalculated.

Bug#886777: Acknowledgement (crashes with Mustek scanner which worked before)

[W. Martin Borgert]

Just checked again: It is already broken in stretch, but works fine in jessie.
Workaround: chroot to jessie...

Bug#886885: gcc-snapshot: "internal compiler error" for invalid input

[Bernardo Dal Seno]

Package: gcc-snapshot
Version: 20180107-1
Severity: normal

Dear Maintainer,

I should have reported this upstream, but creating an account on GCC Bugzilla
takes a day. In the meantime...

This sample C++ program

$ cat broken.cc
struct Rect {
  int width;
};

void f() {
  const Rect rect = {11};  // This should be constexpr
  char str[1][rect.width+1] = {
{"12345678901"},
  };
}


fails compilation with this error:

$ /usr/lib/gcc-snapshot/bin/g++ -std=c++17 -c broken.cc
broken.cc: In function 'void f()':
broken.cc:9:3: internal compiler error: in process_init_constructor_array, at
cp/typeck2.c:1318
   };
   ^
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.


If I've understood the standard correctly, the expression used as the size of
the array should be a constexpr, and the compiler should complain about it.
Asking the user to file a bug report instead of fixing their code is the wrong 
response.

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

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

Versions of packages gcc-snapshot depends on:
ii  binutils2.29.1-12
ii  lib32z1 1:1.2.8.dfsg-5
ii  libc6   2.25-5
ii  libc6-dev   2.25-5
ii  libc6-dev-i386  2.25-5
ii  libc6-dev-x32   2.25-5
ii  libc6-i386  2.25-5
ii  libc6-x32   2.25-5
ii  libgc1c21:7.4.2-8
ii  libgmp102:6.1.2+dfsg-1.1
ii  libisl150.18-1
ii  libmpc3 1.0.3-2
ii  libmpfr43.1.6-1
ii  python  2.7.14-4
ii  zlib1g  1:1.2.8.dfsg-5

gcc-snapshot recommends no packages.

Versions of packages gcc-snapshot suggests:
ii  binutils [binutils-gold]  2.29.1-12

-- no debconf information

Bug#826214: SysV init scripts using init-d-script are not properly redirected to systemctl

[Mert Dirik]

On Wed, 10 Jan 2018 22:49:17 +0300 Mert Dirik  wrote:
> On 01/10/18 21:20, Petter Reinholdtsen wrote:
> > [Mert Dirik]
> >> Please forgive my naivety, but simply moving the argument shift 
part before

> >> sourcing /lib/lsb/init-functions seems to successfully redirect to
> >> systemctl.
> > Interesting. This seem like a very good idea. :)
> I'm happy to hear that.
> >
> >> The only variable leaking to /lib/lsb/init-functions is "script", 
which can be

> >> easily renamed and namespaced in case of a possible problem.
> > Perhaps good to give it some init-d-script related prefix, to 
reduce the

> > chance of a future collision?
> Maybe "__init_d_script_path"?
> >
> >> Is there anything wrong with this approach?
> > Nothing I could think of from the top of my head. :)
> >
> Great :) I'll test it again in stretch or sid and I'll post the result
> here. (previous test was done in jessie)
>

I've tested the attached patch in a sid lxc container and the issue 
seems to be fixed there.

Here is a relevant output:


root@sid:~# cat /etc/init.d/sleep-daemon
#!/bin/sh
# kFreeBSD do not accept scripts as interpreters, using #!/bin/sh and 
sourcing.

if [ true != "$INIT_D_SCRIPT_SOURCED" ] ; then
    set "$0" "$@"; INIT_D_SCRIPT_SOURCED=true . /lib/init/init-d-script
fi
### BEGIN INIT INFO
# Provides:  sleep-daemon
# Required-Start:    $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop:  0 1 6
# Short-Description: Sleep daemon
# Description:   Sleep daemon
### END INIT INFO

# Author: Foo Bar 

DESC="Sleep daemon"
DAEMON=/bin/sleep
DAEMON_ARGS=120
START_ARGS="--background --make-pidfile"

root@sid:~# /etc/init.d/sleep-daemon start
[ ok ] Starting sleep-daemon (via systemctl): sleep-daemon.service.
root@sid:~# systemctl status sleep-daemon | cat
● sleep-daemon.service - LSB: Sleep daemon
   Loaded: loaded (/etc/init.d/sleep-daemon; generated; vendor preset: 
enabled)

   Active: active (running) since Wed 2018-01-10 22:35:58 UTC; 2s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 1467 ExecStop=/etc/init.d/sleep-daemon stop (code=exited, 
status=0/SUCCESS)
  Process: 1513 ExecStart=/etc/init.d/sleep-daemon start (code=exited, 
status=0/SUCCESS)

    Tasks: 1 (limit: 4915)
   CGroup: /lxc/sid/system.slice/sleep-daemon.service
   └─1529 /bin/sleep 120

Jan 10 22:35:58 sid systemd[1]: Starting LSB: Sleep daemon...
Jan 10 22:35:58 sid systemd[1]: Started LSB: Sleep daemon.
root@sid:~#



--- init-d-script.orig	2018-01-11 01:04:11.340881210 +0300
+++ init-d-script	2018-01-11 01:10:20.426711408 +0300
@@ -1,6 +1,11 @@
 #!/bin/sh
 # See init-d-script(5) for instructions on how to use this library.
 #=
+
+# Shift arguments early to fix #826214
+__init_d_script_name="$1"
+shift
+
 # Define LSB log_* functions.
 # Depend on lsb-base (>= 3.2-14) to ensure that this file is present
 # and status_of_proc is working.
@@ -153,12 +158,10 @@
 set -x
 fi
 
-SCRIPTNAME=$1
-scriptbasename="$(basename $1)"
+SCRIPTNAME="$__init_d_script_name"
+scriptbasename="$(basename "$__init_d_script_name")"
 if [ "$scriptbasename" != "init-d-script" ] ; then
-script="$1"
-shift
-. $script
+. "$__init_d_script_name"
 else
 exit 0
 fi

Bug#741148: Proposed patch

[Mathieu Parent]

Control: tag -1 + patch

Hello,

Here is a quick (i.e not a git-am) patch to pass "--upstream-version" to uscan.

Works for me...

Regards

-- 
Mathieu Parent
diff -ur ../gbp/deb/uscan.py /usr/lib/python3/dist-packages/gbp/deb/uscan.py
--- ../gbp/deb/uscan.py 2017-11-28 08:13:55.0 +0100
+++ /usr/lib/python3/dist-packages/gbp/deb/uscan.py 2018-01-10 
23:15:11.618821062 +0100
@@ -174,16 +174,16 @@
 msg = "Uscan failed - debug by running 'uscan --verbose'"
 raise UscanError(msg)
 
-def scan(self, destdir='..'):
+def scan(self, destdir='..', download_version=None):
 """
 Invoke uscan to fetch a new upstream version
 
 @returns: C{True} if a new version was downloaded
 """
-p = subprocess.Popen(['uscan', '--symlink', '--destdir=%s' % destdir,
-  '--dehs'],
- cwd=self._dir,
- stdout=subprocess.PIPE)
+cmd = ['uscan', '--symlink', '--destdir=%s' % destdir, '--dehs']
+if download_version:
+cmd += ['--download-version', download_version]
+p = subprocess.Popen(cmd, cwd=self._dir, stdout=subprocess.PIPE)
 out = p.communicate()[0].decode()
 # uscan exits with 1 in case of uptodate and when an error occurred.
 # Don't fail in the uptodate case:
diff -ur ../gbp/scripts/import_orig.py 
/usr/lib/python3/dist-packages/gbp/scripts/import_orig.py
--- ../gbp/scripts/import_orig.py   2017-11-28 12:22:49.0 +0100
+++ /usr/lib/python3/dist-packages/gbp/scripts/import_orig.py   2018-01-10 
23:19:35.634064363 +0100
@@ -264,7 +264,7 @@
 return (sourcepackage, version)
 
 
-def find_upstream(use_uscan, args):
+def find_upstream(use_uscan, args, version=None):
 """Find the main tarball to import - either via uscan or via command line 
argument
 @return: upstream source filename or None if nothing to import
 @rtype: string
@@ -292,7 +292,7 @@
 uscan = Uscan()
 gbp.log.info("Launching uscan...")
 try:
-if not uscan.scan():
+if not uscan.scan(download_version=version):
 gbp.log.info("package is up to date, nothing to do.")
 return None
 except UscanError as e:
@@ -553,7 +553,7 @@
 if options.download:
 upstream = download_orig(args[0])
 else:
-upstream = find_upstream(options.uscan, args)
+upstream = find_upstream(options.uscan, args, options.version)
 if not upstream:
 return ExitCodes.uscan_up_to_date
 

Bug#886815: Help with libgit2 needed to strip code copy from r-cran-git2r

[Andreas Tille]

Hi,

r-cran-git2r was rejected by ftpmaster[1] due to the code copy of
libgit2.  I intended to fix this by removing the code copy and linking
against the Debian packaged libgit2.  The attempt to do so can be found
in Git[2].  Unfortunately that seems to be not as simple as I was
hoping for since I'm running into:

...
configure: creating ./config.status
config.status: creating src/Makevars
** libs
make[1]: Entering directory '/build/r-cran-git2r-0.21.0+dfsg/src'
gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -I. -I/usr/include/git2  
-DGIT_ARCH_64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DGIT_OPENSSL 
-DLIBGIT2_NO_FEATURES_H -DGIT_SHA1_OPENSSL - DGIT_SSH -DGIT_CURL 
-DGIT_USE_STAT_MTIM -DGIT_USE_NSEC -DHAVE_FUTIMENS -DHAVE_QSORT_R  -fpic  
-g -O2 -fdebug-prefix-map=/build/r-base-3.4.3=. -fstack-protector-strong 
-Wformat - Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c 
git2r.c -o git2r.o
In file included from /usr/include/git2/common.h:29:0,
 from /usr/include/git2/annotated_commit.h:10,
 from /usr/include/git2.h:11,
 from git2r.c:32:
/usr/include/git2/inttypes.h:33:2: error: #error "Use this header only with 
Microsoft Visual C++ compilers!"
 #error "Use this header only with Microsoft Visual C++ compilers!"
  ^
In file included from /usr/include/git2/inttypes.h:46:0,
 from /usr/include/git2/common.h:29,
 from /usr/include/git2/annotated_commit.h:10,
 from /usr/include/git2.h:11,
 from git2r.c:32:
/usr/include/git2/stdint.h:33:2: error: #error "Use this header only with 
Microsoft Visual C++ compilers!"
 #error "Use this header only with Microsoft Visual C++ compilers!"
  ^
In file included from /usr/include/git2/inttypes.h:46:0,
 from /usr/include/git2/common.h:29,
 from /usr/include/git2/annotated_commit.h:10,
 from /usr/include/git2.h:11,
 from git2r.c:32:
/usr/include/git2/stdint.h:89:30: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'int64_t'
 typedef signed __int64   int64_t;
  ^~~
/usr/include/git2/stdint.h:90:30: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'uint64_t'
 typedef unsigned __int64 uint64_t;
  ^~~~
/usr/include/git2/stdint.h:101:9: error: unknown type name 'uint64_t'
 typedef uint64_t  uint_least64_t;
 ^~~~
/usr/include/git2/stdint.h:111:9: error: unknown type name 'uint64_t'
 typedef uint64_t  uint_fast64_t;
 ^~~~
/usr/include/git2/stdint.h:124:9: error: unknown type name 'uint64_t'
 typedef uint64_t  uintmax_t;
 ^~~~
In file included from /usr/include/git2/common.h:29:0,
 from /usr/include/git2/annotated_commit.h:10,
 from /usr/include/git2.h:11,
 from git2r.c:32:
/usr/include/git2/inttypes.h:282:1: error: unknown type name '_inline'; did you 
mean '__nlink_t'?
 _inline
 ^~~
 __nlink_t
/usr/include/git2/inttypes.h:284:11: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '__cdecl'
 imaxdiv_t __cdecl imaxdiv(intmax_t numer, intmax_t denom)
   ^~~
/usr/include/git2/inttypes.h:284:11: error: unknown type name '__cdecl'
/usr/lib/R/etc/Makeconf:159: recipe for target 'git2r.o' failed
make[1]: *** [git2r.o] Error 1
make[1]: Leaving directory '/build/r-cran-git2r-0.21.0+dfsg/src'
...


I admit I have no idea why the includes delivered by libgit2 do
not work here.  Any idea for a correct fix?

Kind regards

   Andreas.

[1] 
http://lists.alioth.debian.org/pipermail/debian-science-maintainers/2018-January/056928.html
[2] https://salsa.debian.org/r-pkg-team/r-cran-git2r.git

-- 
http://fam-tille.de

Bug#886848: gosa-plugin-pwreset: fails to provide the promised web interface

[Mike Gabriel]

Control: reassign #886830 gosa-plugin-pwreset
Control: forcemerge -1 #886830
Control: notfound -1 0.99-4
Control: found -1 0.99.4-1
Control: fixed -1 0.99.5-1

On  Mi 10 Jan 2018 21:13:42 CET, Mike Gabriel wrote:

I already files a similar bug today. Unfortunately against the wrong  
package name.


Thus, force-merging...


First force-merge failed, trying again and fixing version issues with it.

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



pgpVXhYYk7BtV.pgp
Description: Digitale PGP-Signatur

Bug#886880: dh-buildinfo: diff for NMU version 0.11+nmu2

[Niels Thykier]

On Wed, 10 Jan 2018 21:27:30 + Niels Thykier  wrote:
> Package: dh-buildinfo
> Version: 0.11+nmu1
> Severity: normal
> Tags: patch pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for dh-buildinfo (versioned as 0.11+nmu2) and
> uploaded it to DELAYED/10. Please feel free to tell me if I
> should delay it longer.
> 
> Regards.
> [...]

Apologies; I forgot the delay and my attempts to cancel the upload fail
with "no such file". :-/

I have filed #886881 against dput-ng to avoid repeating this mistake.

Thanks,
~Niels

Bug#886884: zsh crashes when it receives a SIGQUIT signal while saving the history

[Vincent Lefevre]

Package: zsh
Version: 5.3.1-4+b2
Severity: important

zsh crashes when it receives a SIGQUIT signal while saving the history.
Thus one loses the session data.

The backtrace:

Core was generated by `-zsh'.
Program terminated with signal SIGQUIT, Quit.
#0  zhandler (sig=2) at ../../Src/signals.c:568
568 ../../Src/signals.c: No such file or directory.
(gdb) bt
#0  zhandler (sig=2) at ../../Src/signals.c:568
#1  
#2  0x7f4edd4df760 in __write_nocancel ()
at ../sysdeps/unix/syscall-template.S:84
#3  0x7f4edd4767e7 in _IO_new_file_write (f=0x562b9ed8aa40, 
data=0x562b9ed846d0, n=27) at fileops.c:1271
#4  0x7f4edd475b32 in new_do_write (fp=0x562b9ed8aa40, 
data=0x562b9ed846d0 ": 1515614009:0;e cine/TODO\n\236+V", 
to_do=to_do@entry=27) at fileops.c:526
#5  0x7f4edd4778a9 in _IO_new_do_write (fp=, 
data=, to_do=27) at fileops.c:502
#6  0x7f4edd475948 in _IO_new_file_sync (fp=0x562b9ed8aa40)
at fileops.c:882
#7  0x7f4edd46b00c in __GI__IO_fflush (fp=0x562b9ed8aa40) at iofflush.c:40
#8  0x562b9d6377ca in savehistfile (
fn=fn@entry=0x562b9eb5dba0 "/srv/d_joooj/home/vinc17/.zhistory", 
err=err@entry=0, writeflags=32787, writeflags@entry=32784)
at ../../Src/hist.c:2872
#9  0x562b9d635857 in hend (prog=prog@entry=0x7f4ede2f8560)
at ../../Src/hist.c:1544
#10 0x562b9d637dd2 in loop (toplevel=toplevel@entry=1, 
justonce=justonce@entry=0) at ../../Src/init.c:166
#11 0x562b9d63b826 in zsh_main (argc=, argv=)
at ../../Src/init.c:1692
#12 0x7f4edd4242b1 in __libc_start_main (main=0x562b9d605300 , 
argc=1, argv=0x7ffe05cda158, init=, fini=, 
rtld_fini=, stack_end=0x7ffe05cda148)
at ../csu/libc-start.c:291
#13 0x562b9d60533a in _start ()

-- Package-specific info:

Packages which provide vendor completions:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  curl   7.52.1-5+deb amd64command line tool for transferrin
ii  systemd232-25+deb9u amd64system and service manager
ii  udev   232-25+deb9u amd64/dev/ and hotplug management daem

dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/


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

Kernel: Linux 4.9.0-5-amd64 (SMP w/1 CPU core)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages zsh depends on:
ii  dpkg1.18.24
ii  libc6   2.24-11+deb9u1
ii  libcap2 1:2.25-1
ii  libtinfo5   6.0+20161126-1+deb9u1
ii  zsh-common  5.3.1-4

Versions of packages zsh recommends:
ii  libc6 2.24-11+deb9u1
ii  libncursesw5  6.0+20161126-1+deb9u1
ii  libpcre3  2:8.39-3

Versions of packages zsh suggests:
ii  zsh-doc  5.3.1-4

-- no debconf information

Bug#886883: RFP: clazy -- Qt oriented code checker based on clang framework

[Frederik Schwarzer]

Package: wnpp
Severity: wishlist

* Package name: clazy
  Version : 1.3
  Upstream Author : Sergio Martins 
* URL : https://github.com/KDE/clazy/
* License : (LGPLv2)
  Programming Lang: (C++)
  Description : Qt oriented code checker based on clang framework

Bug#886882: meson: mesonconf, mesonintrospect and mesontest are broken

[James Cowgill]

Package: meson
Version: 0.44.0-3
Severity: normal

Hi,

The above binaries are broken. Running one of them gives:
> $ mesonconf
> Traceback (most recent call last):
>   File "/usr/bin/mesonconf", line 17, in 
> from mesonbuild import mesonmain
>   File "/usr/share/meson/mesonbuild/mesonmain.py", line 18, in 
> from . import environment, interpreter, mesonlib
>   File "/usr/share/meson/mesonbuild/environment.py", line 17, in 
> from . import coredata
>   File "/usr/share/meson/mesonbuild/coredata.py", line 20, in 
> from .mesonlib import MesonException, commonpath
>   File "/usr/share/meson/mesonbuild/mesonlib.py", line 60, in 
> meson_command = python_command + [detect_meson_py_location()]
>   File "/usr/share/meson/mesonbuild/mesonlib.py", line 51, in 
> detect_meson_py_location
> raise RuntimeError('Could not determine how to run Meson. Please file a 
> bug with details.')
> RuntimeError: Could not determine how to run Meson. Please file a bug with 
> details.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#886878: fwupd service startup fails.

[Mario.Limonciello]

I couldn't reproduce this myself.  As far as I'm aware there is no FFI 
generated code in fwupd.

I think we'll need to see some more logs and/or journal output to figure out 
what's going on for you.

Also filed this upstream, so please feel free to discuss there as well.
https://github.com/hughsie/fwupd/issues/359


> -Original Message-
> From: Limonciello, Mario
> Sent: Wednesday, January 10, 2018 2:47 PM
> To: 'Abhijit Hoskeri' ; '886...@bugs.debian.org'
> <886...@bugs.debian.org>; Debian Bug Tracking System
> 
> Subject: RE: Bug#886878: fwupd service startup fails.
> 
> Thanks for filing this.
> 
> Can you please share the associated journal output when it tries to launch?
> Does it hang?
> 
> Or does it just not launch at all?
> 
> > -Original Message-
> > From: Abhijit Hoskeri [mailto:abhijithosk...@icloud.com]
> > Sent: Wednesday, January 10, 2018 1:40 PM
> > To: Debian Bug Tracking System 
> > Subject: Bug#886878: fwupd service startup fails.
> >
> > Package: fwupd
> > Version: 1.0.3-1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > fwupd startup fails with the default systemd service configuation - the
> > service seems to require libffi generated code, and the systemd
> > directive 'MemoryDenyWriteExecute=yes' prevents libffi from executing
> > generated code.
> >
> > Disabling this in the systemd service MemoryDenyWriteExecute allows the
> > service startup to proceed as expected.
> >
> > Thanks,
> > Abhijit
> >
> >
> > -- System Information:
> > Debian Release: buster/sid
> >   APT prefers unstable-debug
> >   APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
> > 'unstable'), (500,
> > 'testing'), (1, 'experimental-debug'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> > LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> >
> > Versions of packages fwupd depends on:
> > ii  libappstream-glib8 0.7.4-1
> > ii  libarchive13   3.2.2-3.1
> > ii  libc6  2.26.9000+20180108.401311cf-0experimental0
> > ii  libcolorhug2   1.3.3-2
> > ii  libefivar1 32-2
> > ii  libelf10.170-0.2
> > ii  libfwup1   10-1
> > ii  libfwupd2  1.0.3-1
> > ii  libglib2.0-0   2.54.3-1
> > ii  libgnutls303.6.1-1
> > ii  libgpg-error0  1.27-5
> > ii  libgpgme11 1.10.0-1
> > ii  libgudev-1.0-0 232-1
> > ii  libgusb2   0.2.11-1
> > ii  libpolkit-gobject-1-0  0.113-6
> > ii  libsmbios2 2.3.1-2
> > ii  libsoup2.4-1   2.60.2-2
> > ii  libsqlite3-0   3.21.0-1
> > ii  libuuid1   2.30.2-0.1
> >
> > Versions of packages fwupd recommends:
> > ii  fwupdate  10-1
> > ii  python3   3.6.4-1
> >
> > fwupd suggests no packages.
> >
> > -- no debconf information

Bug#886881: dput-ng: Please provide a hook to catch NMU without explicit --delayed parameter

[Niels Thykier]

Package: dput-ng
Version: 1.15
Severity: wishlist

Hi,

I think it would be great if dput-ng could remind me that I am about
to do an NMU without an explicit delay (ideally overridable in the
off-hand case that I actually need to do a zero-delay NMU - which I
think is different from --delayed 0).

Thanks,
~Niels

Bug#885749: I plan to ask for removal of gnomekiss from the achive

[Juhani Numminen]

Hi,

Markus Koschany kirjoitti 10.01.2018 klo 18:46:

> there are even more candidates. I don't intend to port them to Gnome 3
> and will eventually request their removal from Debian. There is still
> time until the next freeze if someone wants to maintain them though.
> 
> Packages at risk from being removed:
>...
> pegsolitaire

I intend to maintain pegsolitaire. I have already eliminated libgnome*
and libglade dependencies, but haven't ported it to gtk3 yet – I still
have to figure out how to replace GdkGC with cairo.
The code is hosted at https://github.com/jnumm/pegsolitaire .

I'd like to have a "pegsolitaire" repository under debiangames-team at
Salsa for the packaging, could someone create it for me? Thanks :)
(Not related to this thread, but could you then also create a repository
for "pentobi", under debiangames-team as well, I will update it to a
new upstream version)

Pegsolitare was maintained using svn on alioth. I'm going to convert
that to git, so hopefully these instructions are still ok:
https://wiki.debian.org/Games/VCS/git/converting-from-svn


Regards,
Juhani

Bug#886880: dh-buildinfo: diff for NMU version 0.11+nmu2

[Niels Thykier]

Package: dh-buildinfo
Version: 0.11+nmu1
Severity: normal
Tags: patch pending

Dear maintainer,

I've prepared an NMU for dh-buildinfo (versioned as 0.11+nmu2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru dh-buildinfo-0.11+nmu1/debian/changelog 
dh-buildinfo-0.11+nmu2/debian/changelog
--- dh-buildinfo-0.11+nmu1/debian/changelog 2016-04-03 21:00:26.0 
+
+++ dh-buildinfo-0.11+nmu2/debian/changelog 2018-01-10 20:54:32.0 
+
@@ -1,3 +1,20 @@
+dh-buildinfo (0.11+nmu2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Replace call to Dh_Lib::buildarch() with Dh_Lib::hostarch() to
+avoid a deprecation warning.  Thanks to Clint Adams for the
+patch.  (Closes: #882334)
+  * Replace manual uses of install(1) with debhelper's install_dir
+and install_file.  They are faster and support "Rules-Requires-Root"
+out of the box.  Thanks to Clint Adams for the patch.
+(Closes: #881421)
+  * Add the (now) mandatory "build-arch" and "build-indep" targets
+(plus add "install-arch" and "install-indep" for consistency).
+  * Set "Rules-Requires-Root: no" as dh-buildinfo does not require
+(fake)root to build (after the above changes).
+
+ -- Niels Thykier   Wed, 10 Jan 2018 20:54:32 +
+
 dh-buildinfo (0.11+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dh-buildinfo-0.11+nmu1/debian/control 
dh-buildinfo-0.11+nmu2/debian/control
--- dh-buildinfo-0.11+nmu1/debian/control   2014-05-17 21:10:44.0 
+
+++ dh-buildinfo-0.11+nmu2/debian/control   2018-01-10 20:54:32.0 
+
@@ -4,6 +4,7 @@
 Build-Depends-Indep: perl, build-essential (>= 7)
 Build-Depends: debhelper (>= 9)
 Maintainer: Yann Dirson 
+Rules-Requires-Root: no
 Standards-Version: 3.5.1
 
 Package: dh-buildinfo
diff -Nru dh-buildinfo-0.11+nmu1/debian/rules 
dh-buildinfo-0.11+nmu2/debian/rules
--- dh-buildinfo-0.11+nmu1/debian/rules 2016-04-03 21:01:14.0 +
+++ dh-buildinfo-0.11+nmu2/debian/rules 2018-01-10 20:54:32.0 +
@@ -18,7 +18,7 @@
 endif
 TMP =`pwd`/debian/$(PACKAGE)
 
-build: build-stamp
+build build-indep: build-stamp
 build-stamp:
dh_testdir
 
@@ -36,7 +36,8 @@
 
dh_clean
 
-install: 
+install: install-indep
+install-indep: build-indep
dh_testdir
dh_testroot
dh_prep
@@ -47,12 +48,9 @@
mv $(TMP)/usr/share/perl5/buildinfo.pm 
$(TMP)/usr/share/perl5/Debian/Debhelper/Sequence/
# not the tip of elegance but I don't know how to install this properly 
with Module::Build
 
-# Build architecture-dependent files here.
-binary-arch: build install
-# We have nothing to do by default.
 
 # Build architecture-independent files here.
-binary-indep: build install
+binary-indep: install-indep
dh_testdir
dh_testroot
dh_installdocs buildinfo.html
@@ -72,4 +70,5 @@
@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+# binary-arch, install-arch and build-arch are no-ops.
+.PHONY: build clean binary-indep binary-arch binary build-arch install-arch
diff -Nru dh-buildinfo-0.11+nmu1/dh_buildinfo 
dh-buildinfo-0.11+nmu2/dh_buildinfo
--- dh-buildinfo-0.11+nmu1/dh_buildinfo 2014-05-17 21:15:03.0 +
+++ dh-buildinfo-0.11+nmu2/dh_buildinfo 2018-01-10 20:54:32.0 +
@@ -20,7 +20,7 @@
 use Debian::Debhelper::Dh_Lib;
 use BuildDeps;
 
-my $buildarch = Debian::Debhelper::Dh_Lib::buildarch();
+my $hostarch = Debian::Debhelper::Dh_Lib::hostarch();
 
 =head1 SYNOPSIS
 
@@ -78,7 +78,7 @@
next unless /^Status: .*ok installed$/m;
 
 # do not include foreign archs
-next unless /^Architecture: ($buildarch|all)$/m;
+next unless /^Architecture: ($hostarch|all)$/m;
 
my ($package) = /^Package: (.*)$/m;
push @{$providers{$package}}, $package;
@@ -337,11 +337,11 @@
 # If this is a symlink, leave it alone.
 if ( ! -d "$tmp/usr/share/doc/$package" &&
 ! -l "$tmp/usr/share/doc/$package") {
-  doit("install","-g",0,"-o",0,"-d","$tmp/usr/share/doc/$package");
+  install_dir("$tmp/usr/share/doc/$package");
 }
 
 if ( ! -l "$tmp/usr/share/doc/$package") {
-  
doit("install","-g",0,"-o",0,"-m0644","debian/buildinfo.gz","$tmp/usr/share/doc/$package/buildinfo_$arch.gz");
+  
install_file("debian/buildinfo.gz","$tmp/usr/share/doc/$package/buildinfo_$arch.gz");
 }
 
   }

Bug#886238: Build-Profiles purpose, mechanism vs policy (was Re: Bug#886238: Please introduce official nosystemd build profile)

[Steve Langasek]

On Tue, Jan 09, 2018 at 01:23:32PM +0100, Guillem Jover wrote:
> On Mon, 2018-01-08 at 18:37:11 +, Wookey wrote:
> > On 2018-01-03 13:30 +, Simon McVittie wrote:
> > > On Wed, 03 Jan 2018 at 15:12:51 +0300, Hleb Valoshka wrote:
> > > > Please introduce official nosystemd build profile so downstream
> > > > distributions can send patches to package maintainers with
> > > > systemd-less build instead of keep them in home.

> > > In general, build profiles are not meant
> > > to result in functional changes to packages
> > > (),

> > This is correct for the mechanism's main/original purpose of
> > bootstrapping/removing cyclic dependencies.  The idea is that you
> > can't change functionality and still use a dependency with the same
> > name, if you actually want to automate the bootstrap process (because
> > you don't know which features of a package the depending-on package
> > uses).

> Exactly, pretty much because otherwise doing automatic bootstrapping
> (reusing existing package names and dependency relationships) becomes
> either very hard or impossible to handle or reason about.

So, the folks who are working on bootstrappability have made their decision
about the semantics of these profiles, and those that do the work get to
decide, and all that.  But I don't agree that there's anything difficult to
reason about here.

The sole requirement that a stage1 package *must* fulfill is that it's
usable for bootstrapping any stage2 packages that require this package (or,
if no such stage2 packages exist, then "final" packages).  The requirement
that this be done in such a way that the list of files within the stage1
package is no different than the list of files within a final package is an
additional, artificial constraint.  I don't believe it fundamentally makes
the bootstrapping problem any easier than if this were done ad-hoc.

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


signature.asc
Description: PGP signature

Bug#848220: g++-4.9/g++-5 show floating point diff to g++-6/g++-7

[Steffen Möller]

Hello,

I just introduced g++-5 as a build dependency to 
https://packages.qa.debian.org/b/boinc-app-eah-brp.html because of small 
- but very present - runtime differences. It had helped me a lot to have 
g++-5 in unstable so I could just go and test. You certainly have 
reasons to remove it, but please be aware of this downside. I can well 
imagine that for many industrial settings the parallel availability of 
both versions is helping the transition.


Cheers,

Steffen

Bug#886879: RM: kde-baseapps -- ROM; manual decruft needed

[Pino Toscano]

Package: ftp.debian.org
Severity: normal

Hi,

please decruft the old binaries of src:kde-baseapps, which seem to not
have been removed automatically:
dolphin4 konqueror-nsplugins libkonqsidebarplugin-dev, libkonqsidebarplugin4a 
kde-baseapps-data

Thanks,
-- 
Pino

Bug#886878: fwupd service startup fails.

[Mario.Limonciello]

Thanks for filing this.

Can you please share the associated journal output when it tries to launch?
Does it hang?

Or does it just not launch at all?

> -Original Message-
> From: Abhijit Hoskeri [mailto:abhijithosk...@icloud.com]
> Sent: Wednesday, January 10, 2018 1:40 PM
> To: Debian Bug Tracking System 
> Subject: Bug#886878: fwupd service startup fails.
> 
> Package: fwupd
> Version: 1.0.3-1
> Severity: important
> 
> Dear Maintainer,
> 
> fwupd startup fails with the default systemd service configuation - the
> service seems to require libffi generated code, and the systemd
> directive 'MemoryDenyWriteExecute=yes' prevents libffi from executing
> generated code.
> 
> Disabling this in the systemd service MemoryDenyWriteExecute allows the
> service startup to proceed as expected.
> 
> Thanks,
> Abhijit
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
> 'unstable'), (500,
> 'testing'), (1, 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages fwupd depends on:
> ii  libappstream-glib8 0.7.4-1
> ii  libarchive13   3.2.2-3.1
> ii  libc6  2.26.9000+20180108.401311cf-0experimental0
> ii  libcolorhug2   1.3.3-2
> ii  libefivar1 32-2
> ii  libelf10.170-0.2
> ii  libfwup1   10-1
> ii  libfwupd2  1.0.3-1
> ii  libglib2.0-0   2.54.3-1
> ii  libgnutls303.6.1-1
> ii  libgpg-error0  1.27-5
> ii  libgpgme11 1.10.0-1
> ii  libgudev-1.0-0 232-1
> ii  libgusb2   0.2.11-1
> ii  libpolkit-gobject-1-0  0.113-6
> ii  libsmbios2 2.3.1-2
> ii  libsoup2.4-1   2.60.2-2
> ii  libsqlite3-0   3.21.0-1
> ii  libuuid1   2.30.2-0.1
> 
> Versions of packages fwupd recommends:
> ii  fwupdate  10-1
> ii  python3   3.6.4-1
> 
> fwupd suggests no packages.
> 
> -- no debconf information

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

[Michael Biebl]

Control: tags -1 + moreinfo

On Wed, 10 Jan 2018 18:12:46 + Ben Hutchings 
wrote:
> Control: reassign -1 systemd
> 
> On Tue, 2018-01-09 at 11:50 +0100, Marc-Robin Wendt wrote:
> > Package: src:linux
> > Version: 4.9.65-3+deb9u1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > since linux-image-4.9.0-3-amd64 DKMS sends my system into suspend.
> 
> I guess you mean DPMS (Display Power Management System).
> 
> > Switching off the monitor causes suspend of the system. 
> > With Kernel-Versions linux-image-4.9.0-1-amd64 and linux-image-4.9.0-2-
> > amd64 I had no problems.
> > This problem is rather annoying, when my system starts the screensaver
> > after 10 min, the monitor switches off and sends the system into
> > suspend. Screensaver is not meant to send the system into suspend.
> 
> The standard Linux kernel does not decide when to suspend.  This is
> usually controlled by systemd-logind.

Ben, were there any DRM related changes in the kernel which would
explain, why 4.9.0-2 behaves differently then 4.9.0-1?

Marc-Robin, can you run (as root)
systemd-analyze set-log-level debug
then run journalctl -f
and then trigger a suspend by letting the screensaver kick in.
Then attach the output of journalctl.

Which graphics gard and desktop environment do you use?

-- 
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#886238: Please introduce official nosystemd build profile

[Steve Langasek]

On Mon, Jan 08, 2018 at 08:36:50PM -0500, Michael Stone wrote:
> On Mon, Jan 08, 2018 at 12:09:09PM -0800, Steve Langasek wrote:
> > Top-posting to just say +1, and that I was going to reply with much the
> > same.

> > I don't even think the requirement for the bootstrap profiles to not
> > functionally change the packages is necessary, but it's the way the folks
> > working on bootstrappability have chosen to do it, so it's their call.  But
> > that's definitely not a binding precedent on other build profiles that might
> > be implemented.

> How, then, would you tell by looking at the package name+version which kind
> of package you have? If you're going to change the name or version string
> anyway, why use some complicated profile system instead of just applying a
> patch? This seems overly complicated for simple cases and overly fragile for
> complex cases.

The fact that this information is no longer exposed in the binary control
file is news to me, and very disappointing.  It seems clear to me that one
*should* be able to determine what profile(s) a package was built with by
looking at the package itself.

As a policy, I think it's clear that packages built with non-default
profiles should never be included in the Debian archive; and segregating
packages into archives by stage is a sensible way to do this for
bootstrapping.  I don't know /what/ one should expect in a world where
profiles are used for other purposes but aren't documented in the binary
control; I guess it just reinforces the fact that you can't trust
third-party deb packages...

In any case, I think the value actually accrues primarily to the simple
cases; because if you want to maintain a package over time, setting a flag
and rebuilding requires much less human involvement than having to
repeatedly merge changes into a package.

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


signature.asc
Description: PGP signature

Bug#886878: fwupd service startup fails.

[Abhijit Hoskeri]

Package: fwupd
Version: 1.0.3-1
Severity: important

Dear Maintainer,

fwupd startup fails with the default systemd service configuation - the
service seems to require libffi generated code, and the systemd
directive 'MemoryDenyWriteExecute=yes' prevents libffi from executing
generated code.

Disabling this in the systemd service MemoryDenyWriteExecute allows the
service startup to proceed as expected.

Thanks,
Abhijit


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

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

Versions of packages fwupd depends on:
ii  libappstream-glib8 0.7.4-1
ii  libarchive13   3.2.2-3.1
ii  libc6  2.26.9000+20180108.401311cf-0experimental0
ii  libcolorhug2   1.3.3-2
ii  libefivar1 32-2
ii  libelf10.170-0.2
ii  libfwup1   10-1
ii  libfwupd2  1.0.3-1
ii  libglib2.0-0   2.54.3-1
ii  libgnutls303.6.1-1
ii  libgpg-error0  1.27-5
ii  libgpgme11 1.10.0-1
ii  libgudev-1.0-0 232-1
ii  libgusb2   0.2.11-1
ii  libpolkit-gobject-1-0  0.113-6
ii  libsmbios2 2.3.1-2
ii  libsoup2.4-1   2.60.2-2
ii  libsqlite3-0   3.21.0-1
ii  libuuid1   2.30.2-0.1

Versions of packages fwupd recommends:
ii  fwupdate  10-1
ii  python3   3.6.4-1

fwupd suggests no packages.

-- no debconf information

Bug#852494: wine: Add libwine.so and libwine.so.1 alternatives

[Javier Serrano Polo]

> There are no reverse dependencies of libwine, so it is not clear to me
> how this would actually be helpful.

Sorry, I missed your message. lmms-vst-server depends on wine, but I
cannot help with lmms-related packaging right now.

El dc 10 de 01 de 2018 a les 19:51 +0100, Jens Reyer va escriure:
> I'm not sure if you suggest to make libwine (instead of wine) the
> alternatives-master for all Wine packages - I think that wouldn't work,
> because each arch has its own libwine, so we'd have multiple master.
> Feel free to prove me wrong.

Then make libwine depend on a wine-alternatives package that ships the
update-wine-alternatives script.


smime.p7s
Description: S/MIME cryptographic signature

Bug#886877: stretch-pu: package gosa-plugin-pwreset/0.99.4-1+deb9u1

[Mike Gabriel]

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

We identified a deprecated constructor call in the PHP package 
gosa-plugin-pwreset.

The attached .debdiff fixes that.

Please ACK for upload to stretch-pu.

Thanks,
Mike


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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru gosa-plugin-pwreset-0.99.4/debian/changelog 
gosa-plugin-pwreset-0.99.4/debian/changelog
--- gosa-plugin-pwreset-0.99.4/debian/changelog 2017-01-11 20:47:54.0 
+0100
+++ gosa-plugin-pwreset-0.99.4/debian/changelog 2018-01-10 21:24:39.0 
+0100
@@ -1,3 +1,10 @@
+gosa-plugin-pwreset (0.99.4-1+deb9u1) stretch; urgency=medium
+
+  * debian/patches:
++ Add 0001_fix-deprecated-constructor-call.patch. (Closes: #886848).
+
+ -- Mike Gabriel   Wed, 10 Jan 2018 21:24:39 
+0100
+
 gosa-plugin-pwreset (0.99.4-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru 
gosa-plugin-pwreset-0.99.4/debian/patches/0001_fix-deprecated-constructor-call.patch
 
gosa-plugin-pwreset-0.99.4/debian/patches/0001_fix-deprecated-constructor-call.patch
--- 
gosa-plugin-pwreset-0.99.4/debian/patches/0001_fix-deprecated-constructor-call.patch
1970-01-01 01:00:00.0 +0100
+++ 
gosa-plugin-pwreset-0.99.4/debian/patches/0001_fix-deprecated-constructor-call.patch
2018-01-10 21:23:13.0 +0100
@@ -0,0 +1,23 @@
+From 314da53ab9316754894eda74d1fa6ed6a10fe199 Mon Sep 17 00:00:00 2001
+From: bzapiec 
+Date: Tue, 28 Nov 2017 10:23:23 +0100
+Subject: [PATCH] fix deprecated constructor call
+
+---
+ addons/pwreset/tabs_pwreset.inc | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/addons/pwreset/tabs_pwreset.inc b/addons/pwreset/tabs_pwreset.inc
+index bd7f889..f01214c 100644
+--- a/addons/pwreset/tabs_pwreset.inc
 b/addons/pwreset/tabs_pwreset.inc
+@@ -24,7 +24,7 @@ class pwresettab extends tabs
+ 
+   function __construct($config, $data, $dn)
+   {
+-tabs::tabs($config, $data, $dn);
++tabs::__construct($config, $data, $dn);
+   }
+ 
+   function save_object($save_current= FALSE)
+
diff -Nru gosa-plugin-pwreset-0.99.4/debian/patches/README 
gosa-plugin-pwreset-0.99.4/debian/patches/README
--- gosa-plugin-pwreset-0.99.4/debian/patches/README1970-01-01 
01:00:00.0 +0100
+++ gosa-plugin-pwreset-0.99.4/debian/patches/README2016-11-02 
08:38:06.0 +0100
@@ -0,0 +1,4 @@
+0xxx: Grabbed from upstream development.
+1xxx: Possibly relevant for upstream adoption.
+2xxx: Only relevant for official Debian release.
+
diff -Nru gosa-plugin-pwreset-0.99.4/debian/patches/series 
gosa-plugin-pwreset-0.99.4/debian/patches/series
--- gosa-plugin-pwreset-0.99.4/debian/patches/series1970-01-01 
01:00:00.0 +0100
+++ gosa-plugin-pwreset-0.99.4/debian/patches/series2018-01-10 
21:23:31.0 +0100
@@ -0,0 +1 @@
+0001_fix-deprecated-constructor-call.patch

Bug#886767: two packages of https://github.com/jessevdk/go-flags

[Héctor Orón Martínez]

Hello,

On Wed, 10 Jan 2018 13:54:02 +0100 Geert Stappers 
wrote:
> Control: retitle -1  two packages of https://github.com/jessevdk/go-flags
> 
> On Wed, Jan 10, 2018 at 01:47:06PM +0100, Geert Stappers wrote:
> > On Wed, Jan 10, 2018 at 07:47:20AM +1300, Michael Hudson-Doyle wrote:
> > > On 10/01/2018 7:08 AM, "Hector Oron"  wrote:
> > > > Package: wnpp
> > > > 
> > > > * Package name: go-flags
> > > >   Upstream Author : Jesse van den Kieboom
> > > > * URL : https://github.com/jessevdk/go-flags
> > > > * License : BSD-3-clause
> > > >   Programming Lang: Go
> > > >   Description : go command line option parser
> > > > 
> > > >  go-flags: Go library for parsing command line arguments
> > > >
> > > This is already packaged, as golang-go-flags-dev or something like that.
> > 
> > https://tracker.debian.org/pkg/golang-go-flags
> > 
> > and there is also
> > 
> > https://tracker.debian.org/pkg/golang-github-svent-go-flags
> > 
> > both originate from https://github.com/jessevdk/go-flags
> > 
> > both packages are maintaint by pkg-go-maintain...@lists.alioth.debian.org
> > 
> > 
> > Closing this ITP  could be an option.
> 
> Using this bugreport for discussion what to do with
> the "duplicate" is another option.

FWIW, for now I'll use a build dependency on `golang-go-flags-dev`.
However, according to Go packaging policy, I understand the proper
package should be named `golang-github-jessevdk-go-flags`.

What do you think? Should we rename them all to
`golang-github-jessevdk-go-flags` and keep only one copy in the archive?

Best regards,
-- 
Héctor Orón Martínez

Collabora Ltd
The Platinum Building
St John's Innovation Park, Cambridge
CB4 0DS, United Kingdom
Telephone: +44 (0)1223 362967
Fax: +44 (0) 1223 351966

   
   Visit Collabora on the Web at https://www.collabora.com/
   Follow Collabora on Twitter https://twitter.com/collabora
   



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#886848: gosa-plugin-pwreset: fails to provide the promised web interface

[Mike Gabriel]

Control: forcemerge -1 #886830

Hi,

On  Mi 10 Jan 2018 14:45:52 CET, Wolfgang Schweer wrote:


Package: gosa-plugin-pwreset
Version: 0.99-4
Severity: important

Hi Mike,

while testing the pwreset plugin with Debian Edu Buster, it failed.

I've got it working w/ this patch applied:

--- a/tabs_pwreset.inc  2017-01-11 20:44:03.0 +0100
+++ b/tabs_pwreset.inc  2018-01-10 13:58:05.556759356 +0100
@@ -24,7 +24,7 @@

   function __construct($config, $data, $dn)
   {
-tabs::tabs($config, $data, $dn);
+tabs::__construct($config, $data, $dn);
   }

   function save_object($save_current= FALSE)

Please check and upload a fixed gosa-plugin-pwreset package.

Wolfgang


I already files a similar bug today. Unfortunately against the wrong  
package name.


Thus, force-merging...

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



pgp0WKnRMvgqV.pgp
Description: Digitale PGP-Signatur

Bug#755809: Ping

[Nikolaus Rath]

Hi,

*ping* It would be very nice to have this patch applied. Trying to
disable a monitor by following the instructions in the current manpage
is frustrating.
Best,
-Nikolaus

--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

Bug#826214: SysV init scripts using init-d-script are not properly redirected to systemctl

[Mert Dirik]

On 01/10/18 21:20, Petter Reinholdtsen wrote:

[Mert Dirik]

Please forgive my naivety, but simply moving the argument shift part before
sourcing /lib/lsb/init-functions seems to successfully redirect to
systemctl.

Interesting.  This seem like a very good idea. :)

I'm happy to hear that.



The only variable leaking to /lib/lsb/init-functions is "script", which can be
easily renamed and namespaced in case of a possible problem.

Perhaps good to give it some init-d-script related prefix, to reduce the
chance of a future collision?

Maybe "__init_d_script_path"?



Is there anything wrong with this approach?

Nothing I could think of from the top of my head. :)

Great :) I'll test it again in stretch or sid and I'll post the result 
here. (previous test was done in jessie)

Bug#884116: linux-image-4.9.0-4-amd64: screen atrifacts then crash

[Sylvain]

Hi,

I also get screen artifacts with the new -4 and -5 kernels:
- display going on/off/on regularly, usually on first key press after
switching between different screens in a multi-display setup
- current window briefly flickering, usually on first key press after
switching between different screens in a multi-display setup
- main display's left origin briefly shifted to the right causing a
"wrapping" effect

I didn't experience a system crash though.

Cheers!
Sylvain

Bug#872039: why the severity?

[John Paul Adrian Glaubitz]

> Please tell me why this would be serious: any filesystem from this millenium
> can handle unclean shutdown fine -- especially if there's a sync before
> reboot/poweroff.

That's hardly an argument. There is still very much the possibility that
this bug causes data-loss, so the severity is definitely justified.

On the other hand, only a very small minority are still using sysvinit on
Debian, so this I think it's ok to have the severity set to serious.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#886643: ed help request

[Nicolas Boulenguez]

Hello.

The attached suggestions will hopefully help packaging 1.14.2.

You should also have received a carbon copy of a question to
http://lists.gnu.org/archive/html/bug-ed about the GPL version change
in the source headers.


suggestions.tar.gz
Description: application/gzip

Bug#886665: Can not view files inside a commercial audio CD-ROM

[Simon McVittie]

Control: reassign 886665 gvfs 1.34.1-2

On Wed, 10 Jan 2018 at 18:50:42 +0100, Gilles CHARABOT wrote:
> #3  0x75bcbe9a in g_simple_async_result_propagate_error () at 
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> #4  0x7fffd42008e7 in  () at 
> /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
> #5  0x77223fe0 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #6  0x7fffd42003b0 in  () at 
> /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
> #7  0x75bde1a3 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> #8  0x75bdebc6 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0

Looks like a bug in libgioremote-volume-monitor.so, which is part of gvfs.

Please could you repeat the backtrace with gvfs-dbgsym, libgtk-3-0-dbgsym
and libglib2.0-0-dbgsym installed? See
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
if you don't know how to install -dbgsym packages.

smcv

Bug#886508: ITP: paper-icon-theme

[Jeremy Bicha]

Hi,

I created a git repo for you if you want to use the Desktop Themes
Team like we did with obsidian-icon-theme.

https://salsa.debian.org/desktop-themes-team/paper-icon-theme

Can you use git-buildpackage to do the initial import?

Thanks,
Jeremy Bicha

Bug#886875: maven-archiver FTBFS: test failure

[Adrian Bunk]

Source: maven-archiver
Version: 3.2.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=maven-archiver=all=3.2.0-1=1515540053=0

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.apache.maven.archiver.MavenArchiverTest
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy-defaults.jar
[INFO] Building jar: /<>/target/test/dummy-explicit-simple.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: 
/<>/target/test/dummy-custom-layout-repo-non-unique.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummyWithDashes.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy-custom-layout-simple.jar
[INFO] Building jar: /<>/target/test/dummy-custom-layout-repo.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: 
/<>/target/test/dummy-custom-layout-simple-non-unique.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[ERROR] Tests run: 27, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.464 
s <<< FAILURE! - in org.apache.maven.archiver.MavenArchiverTest
[ERROR] testRecreation(org.apache.maven.archiver.MavenArchiverTest)  Time 
elapsed: 0.382 s  <<< FAILURE!
java.lang.AssertionError: expected:<1515540046000> but was:<1515539986000>
at 
org.apache.maven.archiver.MavenArchiverTest.testRecreation(MavenArchiverTest.java:248)

[INFO] Running org.apache.maven.archiver.MavenArchiveConfigurationTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.apache.maven.archiver.MavenArchiveConfigurationTest
[INFO] Running org.apache.maven.archiver.ManifestConfigurationTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s 
- in org.apache.maven.archiver.ManifestConfigurationTest
[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   MavenArchiverTest.testRecreation:248 expected:<1515540046000> but 
was:<1515539986000>
[INFO] 
[ERROR] Tests run: 34, Failures: 1, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 4.620 s
[INFO] Finished at: 2018-01-09T23:20:48Z
[INFO] Final Memory: 9M/217M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
project maven-archiver: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/target/surefire-reports for the 
individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test 
returned exit code 1
debian/rules:4: recipe for target 'build-indep' faile

Bug#886876: golang-go-patricia FTBFS: dh_install: golang-github-tchap-go-patricia-dev missing files: usr/share/gocode

[Adrian Bunk]

Source: golang-go-patricia
Version: 2.2.6-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=golang-go-patricia=all=2.2.6-2=1515538994=0

...
   dh_install -i -O--buildsystem=golang
dh_install: Cannot find (any matches for) "usr/share/gocode" (tried in ., 
debian/tmp)

dh_install: golang-github-tchap-go-patricia-dev missing files: usr/share/gocode
dh_install: missing files, aborting
debian/rules:4: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 25

Bug#886874: pacapt FTBFS: a2x: ERROR: "xmllint" --nonet --noout --valid "/build/1st/pacapt-2.3.14/debian/pacapt.1.xml" returned non-zero exit status 4

[Adrian Bunk]

Source: pacapt
Version: 2.3.14-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=pacapt=all=2.3.14-1=1515571646=0

...
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/1st/pacapt-2.3.14'
mkdir -p /build/1st/pacapt-2.3.14/debian/bak
cp /build/1st/pacapt-2.3.14/pacapt /build/1st/pacapt-2.3.14/debian/bak
cat debian/*manpages | sed 's/$/.txt/p' | xargs -n 1 a2x 
--attribute=footer-style=none --doctype manpage --format manpage
a2x: ERROR: "xmllint" --nonet --noout --valid 
"/build/1st/pacapt-2.3.14/debian/pacapt.1.xml" returned non-zero exit status 4
a2x: ERROR: "xmllint" --nonet --noout --valid 
"/build/1st/pacapt-2.3.14/debian/pacapt.1.xml" returned non-zero exit status 4
debian/rules:12: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 123

Bug#886873: ITP: node-normalize-url -- Normalize a URL - Node.js module

[Paolo Greppi]

Package: wnpp
Severity: wishlist
Owner: Paolo Greppi 

* Package name: node-normalize-url
  Version : 2.0.1
  Upstream Author : Sindre Sorhus  (sindresorhus.com)
* URL : https://github.com/sindresorhus/normalize-url#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Normalize a URL - Node.js module

 This Node.js module normalizes URLs, i.e. modifies and standardizes them in
 a consistent manner.
 Normalized URLs can be displayed, stored, deduplicated, sorted, compared,
 while taking into account that certain syntactically different URLs are in
 fact equivalent.
 .
 Node.js is an event-based server-side JavaScript engine.

This is required for node-yarnpkg, see ITP:
https://bugs.debian.org/843021

My intention is to package it within the JavaScript maintainers team.

The repo will be on salsa:
https://salsa.debian.org/js-team/node-normalize-url

Paolo

Bug#886872: agrep: does not properly clean after build

[Andreas Beckmann]

Source: agrep
Version: 4.17-9
Severity: serious
Tags: sid buster
Justification: fails to build from source

agrep does not properly clean up after a successful build, preventing
the package to build twice in a row:

 fakeroot debian/rules clean
dh clean
   dh_auto_clean
make -j1 clean
make[1]: Entering directory '/build/agrep-4.17'
rm -f ./libagrep.a follow.o asearch.o asearch1.o agrep.o bitap.o checkfile.o 
compat.o maskgen.o parse.o checksg.o preprocess.o delim.o asplit.o recursive.o 
sgrep.o newmgrep.o utilities.o dummyfilters.o main.o core a.out agrep
make[1]: Leaving directory '/build/agrep-4.17'
   debian/rules override_dh_clean
make[1]: Entering directory '/build/agrep-4.17'
#   The original sources contain *.orig and *.rej files
#   that must not be cleaned.
#   So do *not* run 'dh_clean' commands.
rm -rf debian/agrep debian/.#* debian/*[~#]
rm -f debian/files debian/*.log debian/*.substvars
[ ! -f Makefile ] || /usr/bin/make clean
make[2]: Entering directory '/build/agrep-4.17'
rm -f ./libagrep.a follow.o asearch.o asearch1.o agrep.o bitap.o checkfile.o 
compat.o maskgen.o parse.o checksg.o preprocess.o delim.o asplit.o recursive.o 
sgrep.o newmgrep.o utilities.o dummyfilters.o main.o core a.out agrep
make[2]: Leaving directory '/build/agrep-4.17'
make[1]: Leaving directory '/build/agrep-4.17'
 dpkg-source -b agrep-4.17
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: error: unwanted binary file: 
debian/.debhelper/agrep/dbgsym-root/usr/lib/debug/.build-id/be/89a6191e4c4a9a03b6705832d691ef157f9292.debug
dpkg-source: error: detected 1 unwanted binary file (add it in 
debian/source/include-binaries to allow its inclusion).
dpkg-buildpackage: error: dpkg-source -b agrep-4.17 subprocess returned exit 
status 29


Given that the source package format is already 3.0 (quilt),
deleting the superfluous *.orig and *.rej files is not really a
problem - dpkg-source will just ignore the deletion.
Therefore override_dh_clean could be dropped without bad effects
and would fix this bug.


Andreas


agrep_4.17-9_twice.log.gz
Description: application/gzip

Bug#876759: daisy-player: Broken autopkgtest

[Paul Gevers]

Control: retitle -1 daisy-player: please add autopkgtest
Control: severity -1 wishlist

On Mon, 25 Sep 2017 11:32:04 -0400 Jeremy Bicha  wrote:
> daisy-player's autopkgtest does not work:

So I disabled it in version 11.2-1.

But it would be nice re-enable it once we know how to run it without
having autopkgtest hang on it.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#886871: postgresql-common: perl error in pg_createcluster

[Mark Eichin]

Package: postgresql-common
Version: 189

While diagnosing an unrelated problem with pg_upgradecluster, got the
"Configuring already existing cluster" message and chased down the code
to this, starting at line 351:

if ($existingver = $version) {
print "Configuring already existing cluster (configuration: $confdir, 
data: $datadir, owner: $owneruid:$ownergid)\n";
} else {

Perl, like C, allows assignments in expressions; also like C, this is
often incorrect/unintended code, as it is in this case.  (The preceding
lines set $existingver and it is obviously intended that they be
compared, not overwritten without ever examining the value; this isn't
subtle, it's just that you probably don't see this message unless
something *else* has already gone wrong, which is why it appears to have
been present since 2008.)

(Version 189 in sid is the newest version I could easily find to report
against.)

Bug#886870: ldapvi FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: ldapvi
Version: 1.7-10
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

ldapvi fails to cross build from source, because it hard codes the build
architecture pkg-config and fails to consider $ac_tool_prefix. The
attached patch fixes that. Please consider applying it.

Helmut
Index: ldapvi-1.7/configure.in
===
--- ldapvi-1.7.orig/configure.in
+++ ldapvi-1.7/configure.in
@@ -46,8 +46,8 @@
 AC_CHECK_LIB([readline],[readline],,AC_MSG_ERROR([libreadline not found]))
 
 # pkg-config
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
-if test "x$PKG_CONFIG" = "xno"; then AC_MSG_ERROR([pkg-config not found]); fi
+PKG_PROG_PKG_CONFIG
+if test "x$PKG_CONFIG" = "x"; then AC_MSG_ERROR([pkg-config not found]); fi
 
 # glib
 LIBS="`$PKG_CONFIG --libs glib-2.0` $LIBS"

Bug#886869: ITP: node-query-string -- Parse and stringify URL query strings - Node.js module

[Paolo Greppi]

Package: wnpp
Severity: wishlist
Owner: Paolo Greppi 

* Package name: node-query-string
  Version : 5.0.1
  Upstream Author : Sindre Sorhus  (sindresorhus.com)
* URL : https://github.com/sindresorhus/query-string#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Parse and stringify URL query strings - Node.js module

 This Node.js module can parse query strings (the part of a URL that follows
 the path, containing form parameters data) to JS dictionaries.
 And it can convert those dictionaries back to query string format (stringify).
 .
 Node.js is an event-based server-side JavaScript engine.

This is required by normalize-url which in turn is required for node-yarnpkg, 
see ITP:
https://bugs.debian.org/843021

My intention is to package it within the JavaScript maintainers team.

The repo will be on salsa:
https://salsa.debian.org/js-team/node-query-string

Paolo

Bug#852494: wine: Add libwine.so and libwine.so.1 alternatives

[Jens Reyer]

Hi Javier and Mike,


On 06/17/2017 11:16 PM, Michael Gilbert wrote:
> control: tag -1 moreinfo
> 
>> Please add a libwine.so.1 alternative to libwine packages, and
>> libwine.so to libwine-dev ones.
> 
> There are no reverse dependencies of libwine, so it is not clear to me
> how this would actually be helpful.  Do you have a specific problem
> where it would be, if so what is it?

AFAIK Javier needs it for lmms.


On 01/24/2017 11:15 PM, Javier Serrano Polo wrote:
> The alternatives should not be slaves in the wine package. I suggest to
> move the slave alternatives from wine package to their respective
> packages (wine32-tools and such), and to depend on an
> update-wine-alternatives script (in libwine) that runs
> update-alternatives for the installed packages.

I'm not sure if you suggest to make libwine (instead of wine) the
alternatives-master for all Wine packages - I think that wouldn't work,
because each arch has its own libwine, so we'd have multiple master.
Feel free to prove me wrong.

Alternatively you might ask for the libwine-alternatives to be separate
from the other Wine-alternatives - I don't feel comfortable about having
main Wine and libwine potentially pointing to different Wine versions.

So why not make libwine a slave of wine and let it recommend wine, like
I did for the other packages?  AFAIK "recommends" are not installed for
build-dependencies, so you'd need to explicitly build-depend on wine in
lmms - but imo that's acceptable.  Of course you would have wine, and
wine32 or wine64 (or both if e.g. i386 is available on the build-daemon)
installed unnecessarily then - but their installed size is very small
compared to libwine (and its dependencies).  The only real drawback I
can think of is having potentially unwanted Wine binaries on PATH.
Still, that's what I'd suggest.

Having said all this, I have no experience with packaging system
libraries.  Can we just stay with soversion .0, or do we have to check
if the Wine API changes (sounds strange since Wine is supposed to
provide a stable (!?) Windows API)?  What do others think?

Greets
jre

Bug#882486: unnecessarily scary warning under Wayland

[Rebecca N. Palmer]

Control: tags -1 fixed-upstream patch

Upstream agree that this is expected under Wayland.  The warning can be 
disabled with 
https://cgit.freedesktop.org/beignet/commit/?id=d1b99a1da56757971753288986419f1b8b9d55f4

Bug#886024: [Pkg-emacsen-addons] Bug#886024: a scenario with site file breaking installation of elpa packages

[David Bremner]

"H.-Dirk Schmitt"  writes:

> Just another motivation to skip the site file on emacs addon package
> installations
>
> 1. A software/configuration roll out has been issued.
> 2. Per site file „Company Mode“ has been enabled per default in our
> organisational site file.
> 3. „apt-get“ step  is running and find the missing dependency for elpa-
> company
>

Yes, see bug 886253

d

Bug#886868: RM: libjs-handlebars -- ROM obsolete source package, node-handlebars replaces it

[Pirate Praveen]

Package: ftp.debian.org
Severity: normal

node-handlebars source package now produces handlebars, libjs-handlebars
and libjs-handlebars.runtime binary packages making libjs-handlebars
source package obsolete, please remove it.



signature.asc
Description: OpenPGP digital signature

Bug#886799:

[Jonathan Lent]

I want to confirm that we’re seeing this on multiple Jessie systems as well, 
when building for 3.16.0-5-amd64:


Building initial module for 3.16.0-5-amd64
Error! Bad return status for module build on kernel: 3.16.0-5-amd64 (x86_64)
Consult /var/lib/dkms/openafs/1.6.9/build/make.log for more information.


  CC [M]  
/var/lib/dkms/openafs/1.6.9/build/src/libafs/MODLOAD-3.16.0-5-amd64-SP/osi_file.o
/var/lib/dkms/openafs/1.6.9/build/src/libafs/MODLOAD-3.16.0-5-amd64-SP/osi_file.c:
 In function 'osi_UFSTruncate':
/var/lib/dkms/openafs/1.6.9/build/src/libafs/MODLOAD-3.16.0-5-amd64-SP/osi_file.c:187:5:
 error: implicit declaration of function 'inode_change_ok' 
[-Werror=implicit-function-declaration]
     code = inode_change_ok(inode, );
     ^
cc1: some warnings being treated as errors

Bug#886867: okular should Depends: kinit (or at least Recommends: kinit)

[Don Armstrong]

Package: okular
Severity: normal
Control: tag -1 patch

kdeinit5 (in kinit) appears necessary for the proper functioning of
okular; failing to have it installed results in errors like:

QXcbConnection: XCB error: 3 (BadWindow), sequence: 1506, resource id: 6295547, 
major code: 40 (TranslateCoords), minor code: 0
Can not find 'kdeinit5' executable at  
"/home/don/bin:/usr/local/bin:/usr/bin:/bin:/usr/games" "/usr/bin, 
/usr/lib/qt5/bin"
Can not find 'kdeinit5' executable at  
"/home/don/bin:/usr/local/bin:/usr/bin:/bin:/usr/games" "/usr/bin, 
/usr/lib/qt5/bin"
Can not find 'kdeinit5' executable at  
"/home/don/bin:/usr/local/bin:/usr/bin:/bin:/usr/games" "/usr/bin, 
/usr/lib/qt5/bin"
kf5.kio.core: couldn't create slave: "Cannot talk to klauncher: The name 
org.kde.klauncher5 was not provided by any .service files"

when trying to save PDF files.

Installing kinit fixes the issue. [This isn't a huge deal, because most
people with KDE desktops will already have this package, but it caught
me out, since I just use some KDE apps, like okular.]

The attached trivial patch fixes this issue.


-- 
Don Armstrong  https://www.donarmstrong.com

Taxes are not levied for the benefit of the taxed.
 -- Robert Heinlein _Time Enough For Love_ p250
From 192e159f9b32b5b637f6f44f39fd991db8aa336a Mon Sep 17 00:00:00 2001
From: Don Armstrong 
Date: Wed, 10 Jan 2018 10:34:36 -0800
Subject: [PATCH] Depend on kinit for kdeinit5 launcher

---
 debian/changelog | 6 ++
 debian/control   | 1 +
 2 files changed, 7 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 688aa87..d5bccbb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+okular (4:17.08.3-3) unstable; urgency=medium
+
+  * Depend on kinit for kdeinit5 launcher (Closes: #)
+
+ --
+
 okular (4:17.08.3-2) unstable; urgency=medium
 
   * Team upload.
diff --git a/debian/control b/debian/control
index f5f2360..5f91c14 100644
--- a/debian/control
+++ b/debian/control
@@ -66,6 +66,7 @@ Depends: libokular5core7 (= ${binary:Version}),
  qml-module-qt-labs-folderlistmodel,
  qml-module-qtgraphicaleffects,
  qml-module-qtquick-controls,
+ kinit,
  ${misc:Depends},
  ${shlibs:Depends},
 Recommends: cups-bsd
-- 
2.15.1

Bug#886833: [gweled] Not compatable with recent gtk

[Stephen Kitt]

Control: tag -1 + moreinfo

Hi David,

On Wed, 10 Jan 2018 13:23:02 +0200, David Baron  wrote:
> Can no longer use the program. Error from CLI:
> 
> ~$ gweled 
> *WARNING* **: Locale not supported by C library. 
> *WARNING* **: GError set over the top of a previous GError or uninitializ

The locale warning suggests a configuration issue on your end; could you
check the output of the “locale” command?

> Debian Release: buster/sid
>   500 yakkety ppa.launchpad.net 
>   500 unstableftp.us.debian.org 
>   500 testing ftp.us.debian.org 
>   500 sid linux.dropbox.com 
>   500 lucid   ppa.launchpad.net 
>   100 jessie-backports ftp.us.debian.org 
> 1 experimentalftp.us.debian.org 

That’s an interesting mix...

> Depends   (Version) | Installed
> ===-+-
> libatk1.0-0 (>= 1.12.4) | 
> libc6 (>= 2.15) | 
> libcairo2(>= 1.2.4) | 
> libfontconfig1(>= 2.11) | 
> libfreetype6 (>= 2.2.1) | 
> libgdk-pixbuf2.0-0  (>= 2.22.0) | 
> libglib2.0-0(>= 2.37.3) | 
> libgtk2.0-0 (>= 2.20.0) | 
> libmikmod3   (>= 3.3.3) | 
> libpango-1.0-0  (>= 1.14.0) | 
> libpangocairo-1.0-0 (>= 1.14.0) | 
> libpangoft2-1.0-0   (>= 1.14.0) | 
> librsvg2-2  (>= 2.14.4) | 

Could you send the full reportbug report, including the installed versions?

Thanks,

Stephen


pgpm62FnBtYqt.pgp
Description: OpenPGP digital signature

Bug#886866: ITP: node-dnscache -- Dns cache for Node.js

[Paolo Greppi]

Package: wnpp
Severity: wishlist
Owner: Paolo Greppi 

* Package name: node-dnscache
  Version : 1.0.1
  Upstream Author : Vinit Sacheti 
* URL : https://github.com/yahoo/dnscache#readme
* License : BSD
  Programming Lang: JavaScript
  Description : Dns cache for Node.js

 This Node.js module wraps the dns module methods and caches the
 most used/most recent dns calls, to avoid the network delay and
 improve the performance.
 .
 Every call to a dns method is first looked into the local cache,
 in case of cache hit the value from cache is returned,
 in case of cache miss the original dns call is made and the
 return value is cached in the local cache.
 .
 Node.js is an event-based server-side JavaScript engine.

This is required for node-yarnpkg, see ITP:
https://bugs.debian.org/843021

My intention is to package it within the JavaScript maintainers team.

The repo will be on salsa:
https://salsa.debian.org/js-team/node-dnscache

Paolo