Bug#907723: link package versions on security-tracker to source packages

[Paul Wise]

On Sat, Sep 1, 2018 at 5:48 AM, Mike Gabriel wrote:

> when working for the LTS team, I regularly need to download source packages
> from the LTS version of Debian. My development machine normally runs a newer
> Debian version, having deb-src URLs for Debian LTS in sources.list is
> possible but not a good option (for me) as it increases latency for apt
> update.

I would suggest you use either apt-venv or chdist (from devscripts) to
enable you to have the apt metadata for LTS and stable releases so
that you can easily download the source using apt. I do this and have
a cron job to automatically run apt update for each chdist.

> So, I always go to [1] with my web browser, copy the URL of the .dsc file
> and then dget that .dsc file.

This misses out verifying apt signatures.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#907668: dicoweb: Search feature does not work

[Власенко Михаил Викторович]

> dicoweb depends on python-memcache, which in turns *suggests* memcached, 
> probably I need to add memcached to depends or recommends ?

As I understand it, dicoweb depends on memcached. After all, he is practically 
non-working without him. Therefore, given my suffering, my answer is: you need 
to add memcached to depends.

... Michael

Bug#907736: smartmontools: smartd starts on every boot, ignoring /etc/default/smartmontools

[Bob Bib]

Package: smartmontools
Version: 6.5+svn4324-1
Severity: normal

Dear Maintainer,

on my system, smartd starts on every boot,
no matter what I put into "/etc/default/smartmontools",
commenting the relevant parameter out:

#start_smartd=yes

or explicitly assigning a "no" value to it:

start_smartd=no



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

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

Versions of packages smartmontools depends on:
ii  debianutils  4.8.4
ii  init-system-helpers  1.51
ii  libc62.27-3
ii  libcap-ng0   0.7.9-1
ii  libgcc1  1:8-20180425-1
ii  libselinux1  2.7-2+b2
ii  libstdc++6   8-20180425-1
ii  lsb-base 9.20170808

Versions of packages smartmontools recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4

Versions of packages smartmontools suggests:
ii  gsmartcontrol   1.1.3-1
pn  smart-notifier  

-- Configuration Files:
/etc/default/smartmontools changed:
start_smartd=no


-- no debconf information

--
Best wishes,
Bob

Bug#907722: youtube-dl unable to download channels

[Rogério Brito]

I am very far from my computer (with my keys to sign uploads) until
September 12th, so, if anybody is interested in doing an NMU, please go
ahead and send me a debdiff after making sure that it is fixed upstream.

Regards, Rogério Brito.

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Em sex, 31 de ago de 2018 17:45, shirish शिरीष 
escreveu:

> Package: youtube-dl
> Version: 2018.06.18-1.1
> Severity: normal
>
> Dear Maintainer,
> Tried couple of playlists getting the same thing -
>
> $ youtube-dl -v -c -f 22
> "https://www.youtube.com/playlist?list=PLhk2InOhK1bccqgUhR31u2Sqffmwv9iLv;
> [debug] System config: []
> [debug] User config: []
> [debug] Custom config: []
> [debug] Command-line args: ['-v', '-c', '-f', '22',
> 'https://www.youtube.com/playlist?list=PLhk2InOhK1bccqgUhR31u2Sqffmwv9iLv
> ']
> [debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
> [debug] youtube-dl version 2018.06.18
> [debug] Python version 3.6.6 (CPython) -
> Linux-4.17.0-3-amd64-x86_64-with-debian-buster-sid
> [debug] exe versions: ffmpeg 4.0.2-1, ffprobe 4.0.2-1, phantomjs
> 2.1.1, rtmpdump 2.4
> [debug] Proxy map: {}
> [youtube:playlist] PLhk2InOhK1bccqgUhR31u2Sqffmwv9iLv: Downloading webpage
> [download] Downloading playlist: Mist Survival - Click here for the
> Playlist (S01)(Gameplay/Let's Play)
> [youtube:playlist] playlist Mist Survival - Click here for the
> Playlist (S01)(Gameplay/Let's Play): Downloading 22 videos
> [download] Downloading video 1 of 22
> [youtube] pTzKz8gJMWg: Downloading webpage
> [youtube] pTzKz8gJMWg: Downloading video info webpage
> [debug] Invoking downloader on
> '
> https://r3---sn-gwpa-o5br.googlevideo.com/videoplayback?mm=31%2C29=sn-gwpa-o5br%2Csn-cvh7knes=o-AAhdE7BYPVL8-Ff-k7U-jQb4xOIY4libUC8MJ8SVkUQd=1535773169=dur%2Cei%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cpl%2Cratebypass%2Crequiressl%2Csource%2Cexpire=video%2Fmp4=2405%3A204%3A931c%3Aa6b1%3Ad9b8%3Ab1d6%3Aff41%3Afd7d=yt6=1576.054=22=36=youtube=m=au%2Crdu=WEB=yes=0=26=yes=518AD0E0C3433F36B414CB6B0F9AC77964728267.2C4177F0769EF42C30975E3B03602405812C6A56=1534584031733220=1535751458=kbWJW_zbM8SYoAPz_rnYCA=3
> '
> [download] Resuming download at byte 741038
>
>
> ERROR: Did not get any data blocks
>   File "/usr/bin/youtube-dl", line 11, in 
> load_entry_point('youtube-dl==2018.6.18', 'console_scripts',
> 'youtube-dl')()
>   File "/usr/lib/python3/dist-packages/youtube_dl/__init__.py", line
> 477, in main
> _real_main(argv)
>   File "/usr/lib/python3/dist-packages/youtube_dl/__init__.py", line
> 467, in _real_main
> retcode = ydl.download(all_urls)
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 2001, in download
> url, force_generic_extractor=self.params.get('force_generic_extractor',
> False))
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 803, in extract_info
> return self.process_ie_result(ie_result, download, extra_info)
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 1002, in process_ie_result
> extra_info=extra)
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 864, in process_ie_result
> extra_info=extra_info)
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 803, in extract_info
> return self.process_ie_result(ie_result, download, extra_info)
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 857, in process_ie_result
> return self.process_video_result(ie_result, download=download)
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 1635, in process_video_result
> self.process_info(new_info)
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 1908, in process_info
> success = dl(filename, info_dict)
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 1847, in dl
> return fd.download(name, info)
>   File "/usr/lib/python3/dist-packages/youtube_dl/downloader/common.py",
> line 364, in download
> return self.real_download(filename, info_dict)
>   File "/usr/lib/python3/dist-packages/youtube_dl/downloader/http.py",
> line 342, in real_download
> return download()
>   File "/usr/lib/python3/dist-packages/youtube_dl/downloader/http.py",
> line 312, in download
> self.report_error('Did not get any data blocks')
>   File "/usr/lib/python3/dist-packages/youtube_dl/downloader/common.py",
> line 165, in report_error
> self.ydl.report_error(*args, **kargs)
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 620, in report_error
> self.trouble(error_message, tb)
>   File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
> 582, in trouble
> tb_data = traceback.format_list(traceback.extract_stack())
>
> Just using 

Bug#705344: pwgen: please implement the diceware password generation scheme

[Paul Wise]

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

On Fri, 2018-08-31 at 16:22 -0400, Antoine Beaupre wrote:

> I don't think pwgen should be rewritten that way when there are
> alternatives like diceware and xkcdpass in the archive now.

That seems OK, especially considering the age of this feature request.

> So I think this bug should be closed.

Doing that with this mail.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#907735: new upstream release 0.9.2

[Sanford Rockowitz]

Package: ddcutil
Version: 0.9.2-1
Severity: Normal

New upstream release. Tarball at www.ddcutil.com/releases/ddcutil-0.9.2.tar.gz

Bug#907734: package-contains-documentation-outside-usr-share-doc false positive

[Russ Allbery]

Package: lintian
Version: 2.5.99
Severity: minor

On a personal package of a documentation tool (not in Debian yet):

I: docknot: package-contains-documentation-outside-usr-share-doc 
usr/share/perl5/auto/share/module/App-DocKnot/templates/readme-md.tmpl
I: docknot: package-contains-documentation-outside-usr-share-doc 
usr/share/perl5/auto/share/module/App-DocKnot/templates/readme.tmpl

Either the .tmpl extension or the templates directory might be good ways
of detecting this false positive.

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

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

Versions of packages lintian depends on:
ii  binutils   2.31.1-5
ii  bzip2  1.0.6-9
ii  diffstat   1.61-1+b1
ii  dpkg   1.19.0.5+b1
ii  file   1:5.34-2
ii  gettext0.19.8.1-7
ii  intltool-debian0.35.0+20060710.4
ii  libapt-pkg-perl0.1.34
ii  libarchive-zip-perl1.63-1
ii  libclass-accessor-perl 0.51-1
ii  libclone-perl  0.39-1
ii  libdpkg-perl   1.19.0.5
ii  libemail-valid-perl1.202-1
ii  libfile-basedir-perl   0.08-1
ii  libipc-run-perl20180523.0-1
ii  liblist-moreutils-perl 0.416-1+b3
ii  libparse-debianchangelog-perl  1.2.0-12
ii  libtext-levenshtein-perl   0.13-1
ii  libtimedate-perl   2.3000-2
ii  liburi-perl1.74-1
ii  libxml-simple-perl 2.25-1
ii  libyaml-libyaml-perl   0.72+repack-1
ii  man-db 2.8.4-2
ii  patchutils 0.3.4-2
ii  perl [libdigest-sha-perl]  5.26.2-7
ii  t1utils1.41-2
ii  xz-utils   5.2.2-1.3

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

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

-- no debconf information

Bug#907668: dicoweb: Search feature does not work

[أحمد المحمودي]

On Sat, Sep 01, 2018 at 02:21:59AM +0600, Власенко Михаил Викторович wrote:
> I fixed search bug by installation memcached.
---end quoted text---

dicoweb depends on python-memcache, which in turns *suggests* memcached, 
probably I need to add memcached to depends or recommends ?

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#892183:

[Hashem Nasarat]

I packaged a new version which fixes this bug and also addressed some other
small issues
kanashiro on irc mentioned that they'd help me with sponsorship, but just
for documentation, here's the package out for review.
https://mentors.debian.net/package/ruby-rbpdf

Bug#907733: RFA: curlpp

[Ximin Luo]

Package: wnpp
Severity: normal

I no longer have interest in maintaining this package.

There are 2 RC bugs which are fairly simple to fix but I'd like to focus my 
attention elsewhere.

If someone is interested in becoming a Debian contributor, these two RC bugs 
are pretty easy to fix, and are a good "starter material" to get you on board 
with Debian packaging.

X

Bug#907732: maildir-utils: May need versioned depend on libxapian30

[Mark J. Nelson]

Package: maildir-utils
Version: 1.0-6
Severity: normal

Dear Maintainer,

After upgrading maildir-utils from 1.0-5 to 1.0-6, some 'mu' commands stopped 
working with the following error message:

mu: symbol lookup error: mu: undefined symbol: _ZN6Xapian4MSetaSEOS0_

Since I suspected this was some kind of mu/xapian version mismatch error, I 
upgraded libxapian30 from 1.4.5-1 to 1.4.7-2, which fixed the issue. Therefore 
I suspect that a more narrowly 
versioned depends is necessary.

-Mark 

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

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

Versions of packages maildir-utils depends on:
ii  dpkg1.19.0.5+b1
ii  guile-2.2-libs  2.2.3+1-3+b1
ii  install-info6.5.0.dfsg.1-2+b1
ii  libc6   2.27-3
ii  libgc1c21:7.4.2-8.3
ii  libgcc1 1:8.2.0-4
ii  libglib2.0-02.56.1-2
ii  libgmime-2.6-0  2.6.23+dfsg1-1
ii  libstdc++6  8.2.0-4
ii  libxapian30 1.4.7-2

maildir-utils recommends no packages.

maildir-utils suggests no packages.

-- no debconf information

Bug#907731: steam-devices: Steam Controller undetected in Steam due to incorrect udev rules from steam-devices package

[Evan Goers]

Package: steam-devices

Version: 1.0.0.55-1

Severity: normal


Dear Maintainer,


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

ineffective)?

Uninstalled the steam-devices package and used the recommended udev rules
from the Steam community. The recommended rules suggest 0666 for Valve's
controllers, instead of 0660 as is used in the steam-devices rules.

* What was the outcome of this action?

The controller was detected by Steam(big picture mode).


It seems that changing the permissions MODE from 0660 to 0666 for

Valve's devices in /lib/udev/rules.d/99-steam-controller-perms.rules allows
the

devices to work as expected. It may be necessary to change them all to 0666
to

allow them to function normally. I can only test the Steam Controller as I

don't have any of the rest listed. 0666 may be required now due to recent
changes in Steam.

-- System Information:

Debian Release: buster/sid

APT prefers testing

APT policy: (500, 'testing')

Architecture: amd64 (x86_64)

Foreign Architectures: i386


Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)

Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash

Init: systemd (via /run/systemd/system)

LSM: AppArmor: enabled


steam-devices depends on no packages.


Versions of packages steam-devices recommends:

ii steam 1.0.0.55-1


steam-devices suggests no packages.

Bug#907729: knot-resolver: kresd fails on arm64 with "PANIC: unprotected error in call to Lua API (bad light userdata pointer)"

[Daniel Kahn Gillmor]

Package: knot-resolver
Version: 3.0.0-4
Tags: upstream, help
Control: affects -1 hddemux

On the arm64 build daemons, kresd fails with the error:

 PANIC: unprotected error in call to Lua API (bad light userdata pointer)

https://buildd.debian.org/status/fetch.php?pkg=knot-resolver=arm64=3.0.0-4=1535740254=0

This happens despite all the official upstream test suites passing.

This same failure causes the test suite for hddemux 0.4-5 to fail on
this platform, which is why i'm marking this bug as affecting hddemux.

The error message seems to be derived from LJ_ERR_BADLU, which i think
is raised by the checklightudptr within luajit, from either
lua_pushlightuserdata() or lua_cpcall() [0].  i have not tracked down
the specific instance yet (i'm not on an arm64 machine at the moment).
But as the knot-resolver codebase never invokes lua_cpcall(), i suspect it
is lua_pushlightuserdata() that is causing the crash.

I welcome any help in trying to diagnose or fix this issue, as i'm
pretty far out of my depth here!

  --dkg

[0] see 
https://codesearch.debian.net/search?q=checklightudptr+package%3A%5CQluajit%5CE


signature.asc
Description: PGP signature

Bug#907730: knot-resolver: kresd fails on armhf with Bus error

[Daniel Kahn Gillmor]

Package: knot-resolver
Version: 3.0.0-4
Tags: help

When running debian/tests/roundtrip on the armhf buildd arm-arm-01,
kresd fails with:

debian/tests/roundtrip: line 82: 19523 Bus error   "$kresd" 
"${kresd_args[@]}" "$d" 2> "$d/kresd.err"

The process doesn't even get to the point of emitting anything to stdout
or stderr -- it appears to be a bug reported by the shell itself.

here is the full log:


https://buildd.debian.org/status/fetch.php?pkg=knot-resolver=armhf=3.0.0-4=1535747186=0

I'm not at an armhf machine right now, and am not on a network where it
is convenient to get to a porterbox, so i'd be happy to have any help
diagnosing or debugging the problem.

   --dkg



signature.asc
Description: PGP signature

Bug#907728: please package new upstream version 1.4.0

[Steinar H. Gunderson]

Package: cubemap
Version: 1.3.2-1
Severity: wishlist

Hi,

After a long time, I found some new features I wanted to put into Cubemap, so
there's a new release 1.4.0 out :-) It features TLS support (via kTLS;
given that buster seems to release with 4.17, that should be a great match),
HLS/fMP4 support for Nageru streams, and also a bugfix for UDP inputs.

Do note that 1.4.0 contains an embedded copy of TLSe (very lightly patched,
since glibc doesn't have kTLS symbols yet); it's not optimal, but it's the way
upstream intents their library to be used, so there's not much of a choice
(and this is one of the cases where Policy says embedding is allowed).

-- System Information:
Debian Release: 9.5
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500, 
'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages cubemap depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u3
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libprotobuf103.0.0-9
pn  libprotobuf9 
ii  libstdc++6   6.3.0-18+deb9u1
ii  libsystemd0  232-25+deb9u4
ii  lsb-base 9.20161125

cubemap recommends no packages.

Versions of packages cubemap suggests:
ii  logrotate   3.11.0-0.1
ii  munin-node  2.0.33-1

Bug#885781: petri-foo: Depends on libgnomecanvas

[trebmuh]

For information, there is someone working on porting petri-foo out of 
libgnomecanvas.

See :
- https://github.com/petri-foo/Petri-Foo/issues/37
- https://github.com/petri-foo/Petri-Foo/pull/40

Olivier

Bug#891700: Converting ll-scope bug to a removal bug

[Jeremy Bicha]

Control: retitle -1 RM: ll-scope -- RoQA; unmaintained for years, depend on 
libglademm2.4
Control: reassign -1 ftp.debian.org
Control: severity -1 normal

ll-scope was removed from Testing in January because it depends on the 
unmaintained libglademm2.4.

ll-scope's last upload was in 2011 and it appears to have been abandoned 
upstream years ago.

I warned the maintainers 6 months ago that I was planning to file a removal bug 
but received no response.

Thanks,
Jeremy Bicha

Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.

[Geoff Levand]

Hi,

I've rebased my two kernel config patches, attached, to the latest
v4.17.17-1 buster kernel.  These patches enable kernel features for
newer ARM64 servers. 

  0001-arm64-Use-default-of-CONFIG_ACPI_NFIT-m.patch
  0002-arm64-Updates-for-ACPI-servers.patch

The issue that Riku brought up of how to support HPE m400 moonshot
systems when ACPI_APEI is enabled has been resolved on the
arm-kernel ML [1].  In summary, the latest released m400 firmware
did not support APEI, and so no special work-around or kernel quirk
support is needed.

With the resolution of that issue I feel these patches are ready to
apply.  Please consider.

[1] https://www.spinics.net/lists/arm-kernel/msg670446.html (efi: add contents 
of LinuxExtraArgs EFI var to command line)

-Geoff
 

>From 7d93f2d534f3ba60b94402b337e165d34e1caf25 Mon Sep 17 00:00:00 2001
From: Geoff Levand 
Date: Wed, 13 Jun 2018 10:50:57 -0700
Subject: [PATCH 1/7] [arm64] Use default of CONFIG_ACPI_NFIT=m

Commit ed497f3cb706d0e0f63844b064d9ebbf6f33b052 (Add server and 96boards options)
added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but the
commit message mentions nothing about why this was done.

Remove the arm64 specific setting and use the default of module build.

Cc: Riku Voipio 
Signed-off-by: Geoff Levand 
---
 debian/config/arm64/config | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/config/arm64/config b/debian/config/arm64/config
index adf3e60bd9f5..72f2dadc16e3 100644
--- a/debian/config/arm64/config
+++ b/debian/config/arm64/config
@@ -71,7 +71,7 @@ CONFIG_ACPI_NUMA=y
 ##
 ## file: drivers/acpi/nfit/Kconfig
 ##
-CONFIG_ACPI_NFIT=y
+CONFIG_ACPI_NFIT=m
 
 ##
 ## file: drivers/android/Kconfig
-- 
2.14.1


>From 10f4c4399f54d99f293047c3d6dfeba08849526e Mon Sep 17 00:00:00 2001
From: Geoff Levand 
Date: Wed, 13 Jun 2018 10:50:57 -0700
Subject: [PATCH 2/7] [arm64] Updates for ACPI servers

o Enable CONFIG_SCHED_SMT for hyperthreading processors.
o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors.
o Enable a number of ACPI options likely to be available on servers.
o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting.

Signed-off-by: Geoff Levand 
---
 debian/config/arm64/config | 29 -
 1 file changed, 24 insertions(+), 5 deletions(-)

diff --git a/debian/config/arm64/config b/debian/config/arm64/config
index 72f2dadc16e3..250395babf59 100644
--- a/debian/config/arm64/config
+++ b/debian/config/arm64/config
@@ -9,6 +9,7 @@ CONFIG_ARM64_ERRATUM_834220=y
 CONFIG_ARM64_VA_BITS_48=y
 ## end choice
 CONFIG_SCHED_MC=y
+CONFIG_SCHED_SMT=y
 CONFIG_NR_CPUS=256
 CONFIG_NUMA=y
 CONFIG_SECCOMP=y
@@ -24,6 +25,7 @@ CONFIG_RANDOMIZE_BASE=y
 CONFIG_RANDOMIZE_MODULE_REGION_FULL=y
 CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y
 CONFIG_COMPAT=y
+CONFIG_ARM64_LSE_ATOMICS=y
 
 ##
 ## file: arch/arm64/crypto/Kconfig
@@ -67,6 +69,21 @@ CONFIG_ARCH_XGENE=y
 ##
 CONFIG_ACPI=y
 CONFIG_ACPI_NUMA=y
+CONFIG_ACPI_PCI_SLOT=y
+CONFIG_ACPI_HED=y
+CONFIG_ACPI_BGRT=y
+CONFIG_ACPI_WATCHDOG=y
+CONFIG_ACPI_CONFIGFS=m
+
+##
+## file: drivers/acpi/apei/Kconfig
+##
+CONFIG_ACPI_APEI=y
+CONFIG_ACPI_APEI_GHES=y
+CONFIG_ACPI_APEI_PCIEAER=y
+CONFIG_ACPI_APEI_SEA=y
+CONFIG_ACPI_APEI_MEMORY_FAILURE=y
+CONFIG_ACPI_APEI_EINJ=m
 
 ##
 ## file: drivers/acpi/nfit/Kconfig
@@ -222,6 +239,12 @@ CONFIG_EXTCON_USB_GPIO=m
 ##
 CONFIG_RASPBERRYPI_FIRMWARE=y
 
+##
+## file: drivers/firmware/efi/Kconfig
+##
+CONFIG_UEFI_CPER=y
+CONFIG_UEFI_CPER_ARM=y
+
 ##
 ## file: drivers/gpio/Kconfig
 ##
@@ -1097,6 +1120,7 @@ CONFIG_VIRTIO_MMIO=m
 ## file: drivers/watchdog/Kconfig
 ##
 CONFIG_GPIO_WATCHDOG=m
+CONFIG_WDAT_WDT=m
 CONFIG_ARM_SP805_WATCHDOG=m
 CONFIG_ARM_SBSA_WATCHDOG=m
 CONFIG_DW_WATCHDOG=m
@@ -1107,11 +1131,6 @@ CONFIG_MESON_GXBB_WATCHDOG=m
 CONFIG_MESON_WATCHDOG=m
 CONFIG_BCM2835_WDT=m
 
-##
-## file: fs/pstore/Kconfig
-##
-CONFIG_PSTORE=y
-
 ##
 ## file: mm/Kconfig
 ##
-- 
2.14.1

Bug#907727: source-contains-empty-directory when a patch adds a file to that directory

[Russ Allbery]

Package: lintian
Version: 2.5.99
Severity: minor

xfonts-jmk 3.0-22 (just now uploaded to the archive) receives the tag:

P: xfonts-jmk source: source-contains-empty-directory neep/ascii/

but a patch in the quilt series adds a file to that directory.  I believe
this addresses the concerns described in that tag, and will ensure that
any view of the source package will contain that directory.

(Upstream is defunct, so this won't be fixed upstream unless I give up and
decide to become upstream.)

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

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

Versions of packages lintian depends on:
ii  binutils   2.31.1-4
ii  bzip2  1.0.6-9
ii  diffstat   1.61-1+b1
ii  dpkg   1.19.0.5+b1
ii  file   1:5.34-2
ii  gettext0.19.8.1-7
ii  intltool-debian0.35.0+20060710.4
ii  libapt-pkg-perl0.1.34
ii  libarchive-zip-perl1.63-1
ii  libclass-accessor-perl 0.51-1
ii  libclone-perl  0.39-1
ii  libdpkg-perl   1.19.0.5
ii  libemail-valid-perl1.202-1
ii  libfile-basedir-perl   0.08-1
ii  libipc-run-perl20180523.0-1
ii  liblist-moreutils-perl 0.416-1+b3
ii  libparse-debianchangelog-perl  1.2.0-12
ii  libtext-levenshtein-perl   0.13-1
ii  libtimedate-perl   2.3000-2
ii  liburi-perl1.74-1
ii  libxml-simple-perl 2.25-1
ii  libyaml-libyaml-perl   0.72+repack-1
ii  man-db 2.8.4-2
ii  patchutils 0.3.4-2
ii  perl [libdigest-sha-perl]  5.26.2-7
ii  t1utils1.41-2
ii  xz-utils   5.2.2-1.3

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

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

-- no debconf information

Bug#905908: libGL.so.1: cannot open shared object file: No such file or directory when updating to 4.4.1~rc2-3

[Andreas Beckmann]

On Sat, 11 Aug 2018 16:00:18 +0200 Kyle Robbertze 
wrote:
> When updating octave to 4.4.1~rc2-3, I received the following error:
> 
> Setting up octave (4.4.1~rc2-3) ...
> /usr/bin/octave-cli: error while loading shared libraries: libGL.so.1: cannot 
> open shared object file: No such file or directory
> dpkg: error processing package octave (--configure):
>  installed octave package post-installation script subprocess returned error 
> exit status 127

Do you still have the full transcript from that upgrade session?
Check /var/log/apt/term.log*
I'm primarily interested in the things that happened before the failure.

Why does it need libGL.so.1 in a maintainer script anyway?


Andreas

Bug#907726: virtualenv: automatically downloads untrusted code

[Benjamin Moody]

Package: virtualenv
Version: 15.1.0+ds-1
Severity: normal

Dear Maintainer,

The man page for virtualenv does not mention the --no-download option,
and does not indicate that the program's default behavior - i.e., upon
invoking 'virtualenv foo' - is to automatically download and install
code from the Internet.  (Whether or not virtualenv per se actually
executes any of that code, I'm not sure.)

This default behavior is a bad idea, to begin with...

 - there's no guarantee that the code downloaded is free software

 - there's no guarantee that the code downloaded won't change its
   behavior from one day to the next

 - there isn't even any authentication of the code's authorship,
   beyond verifying the TLS certificate of 'pypi.python.org'

...which of course are also problems with many typical uses of pip,
but in that case the user is at least arguably making a deliberate
choice.

This is a major change in behavior, compared to the behavior of
virtualenv in jessie; and it's one that violates (at least) my
expectations as a Debian user.

That said, I'm sure some people would say that this is exactly what
virtualenv is "supposed" to do.

At a minimum, this behavior should be documented, along with the
option needed to obtain the old sane behavior.


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

Kernel: Linux 4.9.0-8-amd64 (SMP w/40 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 virtualenv depends on:
ii  python3 3.5.3-1
ii  python3-virtualenv  15.1.0+ds-1

virtualenv recommends no packages.

virtualenv suggests no packages.

-- debconf-show failed

Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.

[Geoff Levand]

Hi,

I've rebased my two kernel config patches, attached, to the latest
v4.17.17-1 buster kernel.  These patches enable kernel features for
newer ARM64 servers. 

  0001-arm64-Use-default-of-CONFIG_ACPI_NFIT-m.patch
  0002-arm64-Updates-for-ACPI-servers.patch

The issue that Riku brought up of how to support HPE m400 moonshot
systems when ACPI_APEI is enabled has been resolved on the
arm-kernel ML [1].  In summary, the latest released m400 firmware
did not support APEI, and so no special work-around or kernel quirk
support is needed.

With the resolution of that issue I feel these patches are ready to
apply.  Please consider.

[1] https://www.spinics.net/lists/arm-kernel/msg670446.html (efi: add contents 
of LinuxExtraArgs EFI var to command line)

-Geoff
 
>From 7d93f2d534f3ba60b94402b337e165d34e1caf25 Mon Sep 17 00:00:00 2001
From: Geoff Levand 
Date: Wed, 13 Jun 2018 10:50:57 -0700
Subject: [PATCH 1/7] [arm64] Use default of CONFIG_ACPI_NFIT=m

Commit ed497f3cb706d0e0f63844b064d9ebbf6f33b052 (Add server and 96boards options)
added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but the
commit message mentions nothing about why this was done.

Remove the arm64 specific setting and use the default of module build.

Cc: Riku Voipio 
Signed-off-by: Geoff Levand 
---
 debian/config/arm64/config | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/config/arm64/config b/debian/config/arm64/config
index adf3e60bd9f5..72f2dadc16e3 100644
--- a/debian/config/arm64/config
+++ b/debian/config/arm64/config
@@ -71,7 +71,7 @@ CONFIG_ACPI_NUMA=y
 ##
 ## file: drivers/acpi/nfit/Kconfig
 ##
-CONFIG_ACPI_NFIT=y
+CONFIG_ACPI_NFIT=m
 
 ##
 ## file: drivers/android/Kconfig
-- 
2.14.1

>From 10f4c4399f54d99f293047c3d6dfeba08849526e Mon Sep 17 00:00:00 2001
From: Geoff Levand 
Date: Wed, 13 Jun 2018 10:50:57 -0700
Subject: [PATCH 2/7] [arm64] Updates for ACPI servers

o Enable CONFIG_SCHED_SMT for hyperthreading processors.
o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors.
o Enable a number of ACPI options likely to be available on servers.
o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting.

Signed-off-by: Geoff Levand 
---
 debian/config/arm64/config | 29 -
 1 file changed, 24 insertions(+), 5 deletions(-)

diff --git a/debian/config/arm64/config b/debian/config/arm64/config
index 72f2dadc16e3..250395babf59 100644
--- a/debian/config/arm64/config
+++ b/debian/config/arm64/config
@@ -9,6 +9,7 @@ CONFIG_ARM64_ERRATUM_834220=y
 CONFIG_ARM64_VA_BITS_48=y
 ## end choice
 CONFIG_SCHED_MC=y
+CONFIG_SCHED_SMT=y
 CONFIG_NR_CPUS=256
 CONFIG_NUMA=y
 CONFIG_SECCOMP=y
@@ -24,6 +25,7 @@ CONFIG_RANDOMIZE_BASE=y
 CONFIG_RANDOMIZE_MODULE_REGION_FULL=y
 CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y
 CONFIG_COMPAT=y
+CONFIG_ARM64_LSE_ATOMICS=y
 
 ##
 ## file: arch/arm64/crypto/Kconfig
@@ -67,6 +69,21 @@ CONFIG_ARCH_XGENE=y
 ##
 CONFIG_ACPI=y
 CONFIG_ACPI_NUMA=y
+CONFIG_ACPI_PCI_SLOT=y
+CONFIG_ACPI_HED=y
+CONFIG_ACPI_BGRT=y
+CONFIG_ACPI_WATCHDOG=y
+CONFIG_ACPI_CONFIGFS=m
+
+##
+## file: drivers/acpi/apei/Kconfig
+##
+CONFIG_ACPI_APEI=y
+CONFIG_ACPI_APEI_GHES=y
+CONFIG_ACPI_APEI_PCIEAER=y
+CONFIG_ACPI_APEI_SEA=y
+CONFIG_ACPI_APEI_MEMORY_FAILURE=y
+CONFIG_ACPI_APEI_EINJ=m
 
 ##
 ## file: drivers/acpi/nfit/Kconfig
@@ -222,6 +239,12 @@ CONFIG_EXTCON_USB_GPIO=m
 ##
 CONFIG_RASPBERRYPI_FIRMWARE=y
 
+##
+## file: drivers/firmware/efi/Kconfig
+##
+CONFIG_UEFI_CPER=y
+CONFIG_UEFI_CPER_ARM=y
+
 ##
 ## file: drivers/gpio/Kconfig
 ##
@@ -1097,6 +1120,7 @@ CONFIG_VIRTIO_MMIO=m
 ## file: drivers/watchdog/Kconfig
 ##
 CONFIG_GPIO_WATCHDOG=m
+CONFIG_WDAT_WDT=m
 CONFIG_ARM_SP805_WATCHDOG=m
 CONFIG_ARM_SBSA_WATCHDOG=m
 CONFIG_DW_WATCHDOG=m
@@ -1107,11 +1131,6 @@ CONFIG_MESON_GXBB_WATCHDOG=m
 CONFIG_MESON_WATCHDOG=m
 CONFIG_BCM2835_WDT=m
 
-##
-## file: fs/pstore/Kconfig
-##
-CONFIG_PSTORE=y
-
 ##
 ## file: mm/Kconfig
 ##
-- 
2.14.1

Bug#907725: xfonts packages are not using the x11 section in practice

[Russ Allbery]

Package: lintian
Version: 2.5.99
Severity: normal

In #878609, xfonts packages were reclassified to be in the x11 section,
resulting in the wrong-section-according-to-package-name tag being
issued if they go to the fonts section.  This was based on the text in
https://packages.debian.org/en/sid/, namely:

X Window System software
  X servers, libraries, fonts, window managers, terminal emulators and
  many related applications.

However, this is not what (essentially) anyone does:

wanderer:~$ grep-aptavail -F Package -s Section -r ^xfonts- | sort | uniq -c
 73 Section: fonts
  1 Section: non-free/fonts
  2 Section: x11

Given that packages.debian.org also says:

Fonts
  Font packages.

with no qualifications or exceptions for X fonts, I don't think it makes
sense to tag all of these packages and ask them to change.  Given existing
practice in the archive, if anything it seems like it would be better to
standardize the other direction and fix packages.debian.org to remove
"fonts" from the definition of the x11 section.  I think this also fits the
general classification rubric of preferring the narrower, less general
section when a package could fall into multiple sections.

(I'm not sure where to report the packages.debian.org bug.  Do you know?)

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

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

Versions of packages lintian depends on:
ii  binutils   2.31.1-4
ii  bzip2  1.0.6-9
ii  diffstat   1.61-1+b1
ii  dpkg   1.19.0.5+b1
ii  file   1:5.34-2
ii  gettext0.19.8.1-7
ii  intltool-debian0.35.0+20060710.4
ii  libapt-pkg-perl0.1.34
ii  libarchive-zip-perl1.63-1
ii  libclass-accessor-perl 0.51-1
ii  libclone-perl  0.39-1
ii  libdpkg-perl   1.19.0.5
ii  libemail-valid-perl1.202-1
ii  libfile-basedir-perl   0.08-1
ii  libipc-run-perl20180523.0-1
ii  liblist-moreutils-perl 0.416-1+b3
ii  libparse-debianchangelog-perl  1.2.0-12
ii  libtext-levenshtein-perl   0.13-1
ii  libtimedate-perl   2.3000-2
ii  liburi-perl1.74-1
ii  libxml-simple-perl 2.25-1
ii  libyaml-libyaml-perl   0.72+repack-1
ii  man-db 2.8.4-2
ii  patchutils 0.3.4-2
ii  perl [libdigest-sha-perl]  5.26.2-7
ii  t1utils1.41-2
ii  xz-utils   5.2.2-1.3

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

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

-- no debconf information

Bug#901605: minissdpd: lots of "peer ... is not from a LAN" messages

[Vinicius Couto]

Package: minissdpd
Version: 1.5.20180223-3
Followup-For: Bug #901605

Dear Maintainer,

In my computer, after some time, the wired connection shows that is connected, 
but sometimes blocks the IPv4, other times all the IPvX connection.
This not happen in the wireless connection in the same network in the same 
computer.

Reggards.

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

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

Versions of packages minissdpd depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  libc6  2.27-5
ii  libnfnetlink0  1.0.1-3+b1
ii  lsb-base   9.20170808

minissdpd recommends no packages.

minissdpd suggests no packages.

-- Configuration Files:
/etc/default/minissdpd changed:
START_DAEMON=1
MiniSSDPd_INTERFACE_ADDRESS=0.0.0.0
MiniSSDPd_OTHER_OPTIONS=""


-- debconf information:
* minissdpd/start_daemon: true
  minissdpd/ip6: false
* minissdpd/listen: 0.0.0.0

Bug#907723: link package versions on security-tracker to source packages

[Mike Gabriel]

Control: close -1
Control: tags -1 wontfix

HI Moritz,

On  Fr 31 Aug 2018 23:59:07 CEST, Moritz Mühlenhoff wrote:


On Fri, Aug 31, 2018 at 09:48:52PM +, Mike Gabriel wrote:

Package: security-tracker
Severity: wishlist
X-Debbugs-Cc: debian-...@lists.debian.org

Hi,

when working for the LTS team, I regularly need to download source packages
from the LTS version of Debian. My development machine normally runs a newer
Debian version, having deb-src URLs for Debian LTS in sources.list is
possible but not a good option (for me) as it increases latency for apt
update.

So, I always go to [1] with my web browser, copy the URL of the .dsc file
and then dget that .dsc file.

However, for the actual CVE tracking work, I browse the
security-tracker.debian.org platform. This could be my only web tool to use,
if it allowed me to download source packages directly from there.
Unfortunately, this is not (yet) possible.

On a page like this [2] all package versions of the given package in Debian
are listed, so it should be easy to make these version strings clickable
hyperrefs that either link to the corresponding page on [1] or even directly
to the .dsc file of that version in the package archive (the latter would be
my preferred choice).

Is that something that would be helpful to others using the
security-tracker? What would be the preferred linking target, if so, then?

Looking forward to some feedback from Security team members and LTS members.
I'd be happy to put some work into this, if liked by others.


The PTS does exactly that and the Security already links there. Adding this
to the Security would be a duplication of effort and also out of scope.

Cheers,
Moritz


Ah... I see. I oversaw the PTS links. And there I now found the .dsc  
URL links.


Nice and sufficient.

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



pgpV5oNdErnO4.pgp
Description: Digitale PGP-Signatur

Bug#907696: Plasma system tray icon and notification missing after recently upgrades of plasmashell

[Bernhard Übelacker]

Hello,
this sounds like it could be a duplicate of bug #907301 [1][2].

There are currently two workarounds:
- either rebuild plasma-workspace locally.
- or (probably easier) install packages from unstable:
  libkf5runner5_5.49.0-1_amd64.deb libkf5plasma5_5.49.0-1_amd64.deb 

Kind regards,
Bernhard

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

Bug#907723: link package versions on security-tracker to source packages

[Moritz Mühlenhoff]

On Fri, Aug 31, 2018 at 09:48:52PM +, Mike Gabriel wrote:
> Package: security-tracker
> Severity: wishlist
> X-Debbugs-Cc: debian-...@lists.debian.org
> 
> Hi,
> 
> when working for the LTS team, I regularly need to download source packages
> from the LTS version of Debian. My development machine normally runs a newer
> Debian version, having deb-src URLs for Debian LTS in sources.list is
> possible but not a good option (for me) as it increases latency for apt
> update.
> 
> So, I always go to [1] with my web browser, copy the URL of the .dsc file
> and then dget that .dsc file.
> 
> However, for the actual CVE tracking work, I browse the
> security-tracker.debian.org platform. This could be my only web tool to use,
> if it allowed me to download source packages directly from there.
> Unfortunately, this is not (yet) possible.
> 
> On a page like this [2] all package versions of the given package in Debian
> are listed, so it should be easy to make these version strings clickable
> hyperrefs that either link to the corresponding page on [1] or even directly
> to the .dsc file of that version in the package archive (the latter would be
> my preferred choice).
> 
> Is that something that would be helpful to others using the
> security-tracker? What would be the preferred linking target, if so, then?
> 
> Looking forward to some feedback from Security team members and LTS members.
> I'd be happy to put some work into this, if liked by others.

The PTS does exactly that and the Security already links there. Adding this
to the Security would be a duplication of effort and also out of scope.

Cheers,
Moritz

Bug#901123: xfonts-jmk: Add Unicode 7.0 runic characters to neep

[Russ Allbery]

Ben Wong  writes:

> The neep font has surprisingly good Unicode coverage, but it is
> missing some characters. In particular, I noticed it is missing the
> eight RUNIC LETTERS, U+16F1 to U+16F8, that were added in Unicode 7.0
> a few years ago. These glyphs are necessary for rendering things like
> the Franks Casket, Tolkein's moon-letters, and certain video games. 

> I have created glyphs for both the 10x20 and 6x13 sizes. To use them,
> simply apply the attached runicupdate.patch to the files in
> xfonts-jmk/neep/iso10646-1-parts/.

> cd xfonts-jmk
> patch -p0 < runicupdate.patch
> fakeroot dh binary
> sudo dpkg -i ../xfonts-jmk*deb
> xset fp rehash

Thank you!  This is great.  Now applied and will be included in the next
release, which I'm working on right now.

> Note: I only added the extra runes to the three variants of Neep that
> already had runes in that region: 10x20, 10x20-bold, and 6x13. I did
> not touch 6x13-bold, 8x15, nor 8x15-bold.

Yup, totally understood.  Derek Upham did a ton of work on incorporating
Unicode characters from other fonts, but only did 6x13 and the two 10x20
fonts.  I think that's all we'll have unless someone else decides to
extend all of that hard work.

> (Also note: moon-letters may not be visible until viewed under
> starlight or moonlight. This is not a bug.)

:)

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

Bug#907724: Don't ship with buster

[Moritz Muehlenhoff]

Source: twitter-bootstrap
Severity: serious

src:twitter-bootstrap is a 6.5 year old version of Bootstrap which is orphaned
since 2013. "Current" packages are in the archive as src:twitter-bootstrap3.
The vintage version should not be in buster, reverse deps should migrate to
src:twitter-bootstrap3 or get removed (if they're only compatible with such
an old version, they're apparently dead as well).

Cheers,
Moritz

Bug#302584: [installation-guide] Problems with the hppa installer-manual

[Holger Wansing]

Control: tags -1 + wontfix


> I just took a little time to review the sarge installation manual
> at http://www.debian.org/releases/testing/hppa/ .
> It's a big improvement over the woody one!
> I do have some nits I'd like fixed before release:


Since hppa is not a release architecture for years, I'm tagging this bug
as wont-fix


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#248261: [installation-guide] Problem in hppa.xml

[Holger Wansing]

Control: tags -1 + wontfix


> Subject: Problem in hppa.xml
> Date: Monday 10 May 2004 03:52
> From: "Bruno Barrera C." 
> To: debian-b...@lists.debian.org
> 
> Hello,
> 
> Reading
> "installer/doc/manual/en/partitioning/partition/hppa.xml" I found this:
> 
> "This is where the boot loader and an optional kernel
> and RAMdisk will be stored, so make it big enough for that -- at least
> 4Mb (I like 8-16Mb).  An additional requirement of the firmware is that
> the Linux kernel must reside within the first 2GB of the disk.  This
> is typically achieved by making the root ext2 partition fit entirely
> within the first 2GB of the disk. Alternatively you can create a small
> ext2 partition near the start of the disk and mount that on..."
> 
> Really this needs to be an ext2 partition? Isn't an anachronism
> about when the debian kernels didn't use initrd to load the driver
> of the filesystem, required to mount the root filesystem?

Since hppa is not a release architecture for years, I'm tagging this bug
as wont-fix


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#907723: link package versions on security-tracker to source packages

[Mike Gabriel]

Package: security-tracker
Severity: wishlist
X-Debbugs-Cc: debian-...@lists.debian.org

Hi,

when working for the LTS team, I regularly need to download source  
packages from the LTS version of Debian. My development machine  
normally runs a newer Debian version, having deb-src URLs for Debian  
LTS in sources.list is possible but not a good option (for me) as it  
increases latency for apt update.


So, I always go to [1] with my web browser, copy the URL of the .dsc  
file and then dget that .dsc file.


However, for the actual CVE tracking work, I browse the  
security-tracker.debian.org platform. This could be my only web tool  
to use, if it allowed me to download source packages directly from  
there. Unfortunately, this is not (yet) possible.


On a page like this [2] all package versions of the given package in  
Debian are listed, so it should be easy to make these version strings  
clickable hyperrefs that either link to the corresponding page on [1]  
or even directly to the .dsc file of that version in the package  
archive (the latter would be my preferred choice).


Is that something that would be helpful to others using the  
security-tracker? What would be the preferred linking target, if so,  
then?


Looking forward to some feedback from Security team members and LTS  
members. I'd be happy to put some work into this, if liked by others.


Thanks+Greets,
Mike

[1] https://packages.debian.org/source//
[1] https://security-tracker.debian.org/tracker/CVE-2018-10873
--

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



pgpAgmJbrdHgo.pgp
Description: Digitale PGP-Signatur

Bug#900936: Problem solved

[Arnaud Courtès]

Everything is fine again since the last geoclue-2 update. Redshift works 
like a charm.


Thank you !

Bug#907722: youtube-dl unable to download channels

[shirish शिरीष]

Package: youtube-dl
Version: 2018.06.18-1.1
Severity: normal

Dear Maintainer,
Tried couple of playlists getting the same thing -

$ youtube-dl -v -c -f 22
"https://www.youtube.com/playlist?list=PLhk2InOhK1bccqgUhR31u2Sqffmwv9iLv;
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '-c', '-f', '22',
'https://www.youtube.com/playlist?list=PLhk2InOhK1bccqgUhR31u2Sqffmwv9iLv']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.06.18
[debug] Python version 3.6.6 (CPython) -
Linux-4.17.0-3-amd64-x86_64-with-debian-buster-sid
[debug] exe versions: ffmpeg 4.0.2-1, ffprobe 4.0.2-1, phantomjs
2.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[youtube:playlist] PLhk2InOhK1bccqgUhR31u2Sqffmwv9iLv: Downloading webpage
[download] Downloading playlist: Mist Survival - Click here for the
Playlist (S01)(Gameplay/Let's Play)
[youtube:playlist] playlist Mist Survival - Click here for the
Playlist (S01)(Gameplay/Let's Play): Downloading 22 videos
[download] Downloading video 1 of 22
[youtube] pTzKz8gJMWg: Downloading webpage
[youtube] pTzKz8gJMWg: Downloading video info webpage
[debug] Invoking downloader on
'https://r3---sn-gwpa-o5br.googlevideo.com/videoplayback?mm=31%2C29=sn-gwpa-o5br%2Csn-cvh7knes=o-AAhdE7BYPVL8-Ff-k7U-jQb4xOIY4libUC8MJ8SVkUQd=1535773169=dur%2Cei%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cpl%2Cratebypass%2Crequiressl%2Csource%2Cexpire=video%2Fmp4=2405%3A204%3A931c%3Aa6b1%3Ad9b8%3Ab1d6%3Aff41%3Afd7d=yt6=1576.054=22=36=youtube=m=au%2Crdu=WEB=yes=0=26=yes=518AD0E0C3433F36B414CB6B0F9AC77964728267.2C4177F0769EF42C30975E3B03602405812C6A56=1534584031733220=1535751458=kbWJW_zbM8SYoAPz_rnYCA=3'
[download] Resuming download at byte 741038


ERROR: Did not get any data blocks
  File "/usr/bin/youtube-dl", line 11, in 
load_entry_point('youtube-dl==2018.6.18', 'console_scripts', 'youtube-dl')()
  File "/usr/lib/python3/dist-packages/youtube_dl/__init__.py", line
477, in main
_real_main(argv)
  File "/usr/lib/python3/dist-packages/youtube_dl/__init__.py", line
467, in _real_main
retcode = ydl.download(all_urls)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
2001, in download
url, force_generic_extractor=self.params.get('force_generic_extractor',
False))
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
803, in extract_info
return self.process_ie_result(ie_result, download, extra_info)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
1002, in process_ie_result
extra_info=extra)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
864, in process_ie_result
extra_info=extra_info)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
803, in extract_info
return self.process_ie_result(ie_result, download, extra_info)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
857, in process_ie_result
return self.process_video_result(ie_result, download=download)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
1635, in process_video_result
self.process_info(new_info)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
1908, in process_info
success = dl(filename, info_dict)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
1847, in dl
return fd.download(name, info)
  File "/usr/lib/python3/dist-packages/youtube_dl/downloader/common.py",
line 364, in download
return self.real_download(filename, info_dict)
  File "/usr/lib/python3/dist-packages/youtube_dl/downloader/http.py",
line 342, in real_download
return download()
  File "/usr/lib/python3/dist-packages/youtube_dl/downloader/http.py",
line 312, in download
self.report_error('Did not get any data blocks')
  File "/usr/lib/python3/dist-packages/youtube_dl/downloader/common.py",
line 165, in report_error
self.ydl.report_error(*args, **kargs)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
620, in report_error
self.trouble(error_message, tb)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line
582, in trouble
tb_data = traceback.format_list(traceback.extract_stack())

Just using youtube-dl -F playlist shows that the video format is
supported and all, something else seems to be at work :(

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

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

Versions of packages youtube-dl depends on:
ii  python33.6.5-3
ii  

Bug#907721: [lxde] black screen after resume

[Christa Grüttmüller]

Package: lxde
Version: 9
Severity: normal

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

I recently installed Debian 9.5.0 on a Dell Latitude E5400. The 
following error now occurs:


When I press the moon key or close the lid to suspend the laptop and 
later press the power key or open the lid in order to make the laptop 
resume, the screen will be black. This only happens within a LXDE 
session; at the LXDM login screen or within an IceWM session, suspend 
and resume work normally.


When the error occurs, switching to another TTY works perfectly. 
Switching back to TTY 7 (the X session) still shows a black screen. When 
X is killed and restarted, the screen is normal again, but this is not a 
solution.


The problem did not occur in an older Debian installation on the same 
laptop.


Thanks in advance for any advice. :-)

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

Debian Release: 9.5
500 stable-updates ftp.de.debian.org
500 stable security.debian.org
500 stable ftp.de.debian.org

--- Package information. ---
Depends (Version) | Installed
==-+-===
galculator | 2.1.4-1+b1
OR gnome-calculator |
gpicview | 0.2.5-2+b1
leafpad | 0.8.18.1-5
lxappearance | 0.6.3-1
lxappearance-obconf | 0.2.3-1
lxde-core | 9
lxde-icon-theme | 0.5.1-2
lxhotkey-gtk | 0.1.0-1
lxinput | 0.3.5-1
lxrandr | 0.3.1-1
lxsession-edit | 0.5.3-2
lxterminal | 0.3.0-2
xarchiver | 1:0.5.4-7


Recommends (Version) | Installed
-+-===
clipit | 1.4.2-1.2
deluge | 1.3.13+git20161130.48cedf63-3
OR transmission-gtk |
evince | 3.22.1-3+deb9u1
OR pdf-viewer |
gnome-disk-utility | 3.22.1-1
smplayer | 16.11.0~ds0-1+deb9u1
OR vlc | 3.0.3-1-0+deb9u1
OR mplayer-gui |
gnome-system-tools | 3.0.0-6
gucharmap | 1:9.0.2-1
firefox-esr | 52.9.0esr-1~deb9u1
OR firefox |
OR www-browser |
lightdm | 1.18.3-1
OR x-display-manager |
lxmusic |
OR audacious | 3.7.2-1+b1
lxpolkit | 0.5.3-2
menu-xdg | 0.5
usermode | 1.109-1+b2
wicd | 1.7.4+tb2-4
OR network-manager-gnome | 1.4.4-1
xserver-xorg | 1:7.7+19


Suggests (Version) | Installed
==-+-===
gimp | 2.8.18-1+deb9u1
libreoffice | 1:5.2.7-1+deb9u4
lxlauncher |
lxtask | 0.1.8-1
pidgin |
pk-update-icon |
xfce4-power-manager |

Bug#907720: cminpack: autopkgtest fails with glibc 2.28 due to precision changes

[Adam Conrad]

Package: cminpack
Version: 1.3.6-2
Severity: normal

In Ubuntu, as we've moved on the glibc 2.28, we've seen the cminpack[1]
test suite "fail", due to what appears to be improved precision in the
results.

While this can be fixed by adjusting the ref files (as upstream has done
more than once in the past, it looks like), I question if this test as
it's executed is actually an appropriate autopkgtest.  It fails on most
architectures due to slightly different precision, and it will "regress"
on amd64 every time upstream improves precision there.

It might be a more appropriate test if it had a filter between running
the examples and examining the results that allowed for jitter tolerance
rather than just a plain diff looking for identical reference results.

If that's not feasible, maybe a more lightweight test that just makes
sure the package isn't entirely broken, but doesn't run the examples and
look for specific outputs might be a saner autopkgtest.

... Adam

[1] http://autopkgtest.ubuntu.com/packages/c/cminpack

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

Kernel: Linux 4.17.0-7-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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

Bug#907676: autopkgtests fail with LO 6.1 because LibreOfficeKit writes to stderr

[Olly Betts]

On Fri, Aug 31, 2018 at 11:18:37AM +0200, Olivier Tilloy wrote:
> Looks like I was too fast in assuming that Debian suffered the same
> issue as observed on Ubuntu.
> 
> Tests seem to pass at
> https://ci.debian.net/packages/l/lloconv/unstable/amd64/, no output
> observed on stderr. Except for one test run on 2018-08-24 03:42:33 UTC
> (https://ci.debian.net/data/autopkgtest/unstable/amd64/l/lloconv/872144/log.gz).
> I wonder what changed between that test run and the next one that
> passed. Not the version of libreoffice in any case.

I see this message locally in some cases on Debian unstable - e.g. it's
present with my example here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906715#20

But I don't get it if I run the autopkgtest commands locally.  It's
unclear to me what triggers it.

Ideally we wouldn't spew useless messages to stderr, but that's really
down to libreoffice and I don't think we want to get into trying to
filter its stderr output (and throwing it all away seems unhelpful).

So I'd agree that adding allow-stderr makes sense.  I'll add it in the
next upload (also happy for someone to NMU this fix).

Cheers,
Olly

Bug#907668: dicoweb: Search feature does not work

[Власенко Михаил Викторович]

Package: dicoweb
Version: 2.3-2
Followup-For: Bug #907668

I fixed search bug by installation memcached.

... Michael

Bug#705344: pwgen: please implement the diceware password generation scheme

[Antoine Beaupre]

I don't think pwgen should be rewritten that way when there are
alternatives like diceware and xkcdpass in the archive now.

So I think this bug should be closed.


signature.asc
Description: PGP signature

Bug#907659: nageru: FTBFS against x264 0.155

[Steinar H. Gunderson]

On Fri, Aug 31, 2018 at 08:19:31AM +0200, Sebastian Ramacher wrote:
> The attached (untested) patch should be enough to adopt to this change.

I didn't use your patch, but it was useful in making my own -- I wanted
things ever so slightly differently. :-) Upload coming, thanks for the help.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#907719: stretch-pu: package libtirpc/0.2.5-1.2+deb9u1

[Salvatore Bonaccorso]

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

Hi

libtirpc is affected by a flaw which got assigned CVE-2018-14622,
#907608 but we won't issue a DSA for it. Qutoing the SUSE report:

> libtirpc has a built-in limit on the file descriptors it can handle, because 
> it
> relies on select() with its associated FD_SETSIZE limit.
> 
> When you register a TCP transport, incoming connections will be handled by a
> function calledd rendezvous_request(), which does this:
> 
> newxprt = makefd_xprt(sock, r->sendsize, r->recvsize);
> if (!__rpc_set_netbuf(>xp_rtaddr, , len))
> return (FALSE);
> 
> makefd_xprt in turn has this little safety built in:
> 
> if (fd >= FD_SETSIZE) {
> warnx("svc_vc: makefd_xprt: fd too high\n");
> xprt = NULL;
> goto done;
> }
> [...]
> done:
> return (xprt);
> 
> That combination is not a healthy one.

Upstream fix:
http://git.linux-nfs.org/?p=steved/libtirpc.git;a=commitdiff;h=1c77f7a869bdea2a34799d774460d1f9983d45f0
. The issue is fixed for us in the experimental version, not yet at
the poing of this writing in unstable, but I have proposed a NMU and
uploaded to delayed/10 queue, cf. #907608.

Attaching the full debdiff.

Changelog entry:

> libtirpc (0.2.5-1.2+deb9u1) stretch; urgency=medium
> 
>   * Non-maintainer upload.
>   * rendezvous_request: check the makefd_xprt return value (CVE-2018-14622)
> (Closes: #907608)
> 
>  -- Salvatore Bonaccorso   Fri, 31 Aug 2018 21:56:01 +0200

Regards,
Salvatore
diff -Nru libtirpc-0.2.5/debian/changelog libtirpc-0.2.5/debian/changelog
--- libtirpc-0.2.5/debian/changelog 2017-05-05 17:24:41.0 +0200
+++ libtirpc-0.2.5/debian/changelog 2018-08-31 21:56:01.0 +0200
@@ -1,3 +1,11 @@
+libtirpc (0.2.5-1.2+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * rendezvous_request: check the makefd_xprt return value (CVE-2018-14622)
+(Closes: #907608)
+
+ -- Salvatore Bonaccorso   Fri, 31 Aug 2018 21:56:01 +0200
+
 libtirpc (0.2.5-1.2) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru 
libtirpc-0.2.5/debian/patches/12-rendezvous_request-check-the-makefd_xprt-return-valu.patch
 
libtirpc-0.2.5/debian/patches/12-rendezvous_request-check-the-makefd_xprt-return-valu.patch
--- 
libtirpc-0.2.5/debian/patches/12-rendezvous_request-check-the-makefd_xprt-return-valu.patch
 1970-01-01 01:00:00.0 +0100
+++ 
libtirpc-0.2.5/debian/patches/12-rendezvous_request-check-the-makefd_xprt-return-valu.patch
 2018-08-31 21:56:01.0 +0200
@@ -0,0 +1,34 @@
+From: Ditang Chen 
+Date: Mon, 13 Jul 2015 10:36:16 -0400
+Subject: rendezvous_request: check the makefd_xprt return value
+Origin: 
http://git.linux-nfs.org/?p=steved/libtirpc.git;a=commit;h=1c77f7a869bdea2a34799d774460d1f9983d45f0
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-14622
+Bug-Debian: https://bugs.debian.org/907608
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1620293
+Bug-SUSE: https://bugzilla.novell.com/show_bug.cgi?id=968175
+
+xprt may return NULL, so check the return value is necessary.
+
+Reviewed-by: Chuck Lever 
+Signed-off-by: Ditang Chen 
+Signed-off-by: Steve Dickson 
+---
+ src/svc_vc.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/src/svc_vc.c b/src/svc_vc.c
+index 6848c098f055..3cddcbceebae 100644
+--- a/src/svc_vc.c
 b/src/svc_vc.c
+@@ -337,6 +337,8 @@ again:
+*/
+ 
+   newxprt = makefd_xprt(sock, r->sendsize, r->recvsize);
++  if (!newxprt)
++  return (FALSE);
+ 
+   if (!__rpc_set_netbuf(>xp_rtaddr, , len))
+   return (FALSE);
+-- 
+2.18.0
+
diff -Nru libtirpc-0.2.5/debian/patches/series 
libtirpc-0.2.5/debian/patches/series
--- libtirpc-0.2.5/debian/patches/series2017-05-05 17:24:41.0 
+0200
+++ libtirpc-0.2.5/debian/patches/series2018-08-31 21:56:01.0 
+0200
@@ -5,3 +5,4 @@
 09-autogen.sh.diff
 10-CVE-2016-4429.diff
 11-CVE-2017-8779.diff
+12-rendezvous_request-check-the-makefd_xprt-return-valu.patch

Bug#907608: libtirpc: diff for NMU version 0.2.5-1.3

[Salvatore Bonaccorso]

Control: tags 907608 + pending


Dear maintainer,

I've prepared an NMU for libtirpc (versioned as 0.2.5-1.3) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards,
Salvatore
diff -Nru libtirpc-0.2.5/debian/changelog libtirpc-0.2.5/debian/changelog
--- libtirpc-0.2.5/debian/changelog	2017-05-05 17:24:41.0 +0200
+++ libtirpc-0.2.5/debian/changelog	2018-08-31 21:47:58.0 +0200
@@ -1,3 +1,11 @@
+libtirpc (0.2.5-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * rendezvous_request: check the makefd_xprt return value (CVE-2018-14622)
+(Closes: #907608)
+
+ -- Salvatore Bonaccorso   Fri, 31 Aug 2018 21:47:58 +0200
+
 libtirpc (0.2.5-1.2) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru libtirpc-0.2.5/debian/patches/12-rendezvous_request-check-the-makefd_xprt-return-valu.patch libtirpc-0.2.5/debian/patches/12-rendezvous_request-check-the-makefd_xprt-return-valu.patch
--- libtirpc-0.2.5/debian/patches/12-rendezvous_request-check-the-makefd_xprt-return-valu.patch	1970-01-01 01:00:00.0 +0100
+++ libtirpc-0.2.5/debian/patches/12-rendezvous_request-check-the-makefd_xprt-return-valu.patch	2018-08-31 21:47:58.0 +0200
@@ -0,0 +1,34 @@
+From: Ditang Chen 
+Date: Mon, 13 Jul 2015 10:36:16 -0400
+Subject: rendezvous_request: check the makefd_xprt return value
+Origin: http://git.linux-nfs.org/?p=steved/libtirpc.git;a=commit;h=1c77f7a869bdea2a34799d774460d1f9983d45f0
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-14622
+Bug-Debian: https://bugs.debian.org/907608
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1620293
+Bug-SUSE: https://bugzilla.novell.com/show_bug.cgi?id=968175
+
+xprt may return NULL, so check the return value is necessary.
+
+Reviewed-by: Chuck Lever 
+Signed-off-by: Ditang Chen 
+Signed-off-by: Steve Dickson 
+---
+ src/svc_vc.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/src/svc_vc.c b/src/svc_vc.c
+index 6848c098f055..3cddcbceebae 100644
+--- a/src/svc_vc.c
 b/src/svc_vc.c
+@@ -337,6 +337,8 @@ again:
+ 	 */
+ 
+ 	newxprt = makefd_xprt(sock, r->sendsize, r->recvsize);
++	if (!newxprt)
++		return (FALSE);
+ 
+ 	if (!__rpc_set_netbuf(>xp_rtaddr, , len))
+ 		return (FALSE);
+-- 
+2.18.0
+
diff -Nru libtirpc-0.2.5/debian/patches/series libtirpc-0.2.5/debian/patches/series
--- libtirpc-0.2.5/debian/patches/series	2017-05-05 17:24:41.0 +0200
+++ libtirpc-0.2.5/debian/patches/series	2018-08-31 21:47:58.0 +0200
@@ -5,3 +5,4 @@
 09-autogen.sh.diff
 10-CVE-2016-4429.diff
 11-CVE-2017-8779.diff
+12-rendezvous_request-check-the-makefd_xprt-return-valu.patch

Bug#907493: ghostscript breaks cups autopkgtest: test times out

[Paul Gevers]

Hi Jonas,

On 31-08-18 16:19, Jonas Smedegaard wrote:
> Currently¹ I cannot (easily) setup a CUPS testing environment, so would 
> appreciate if someone else can confirm if the version now in testing 
> _also_ causes this same failure - and if so then please help ensure that 
> this issue does not block the security fix now in unstable to enter 
> testing.

The cups test with only packages from testing is successfully running.
It has been tried two times over the last two days, visible with the
trigger "migration-reference/0" here:
https://ci.debian.net/packages/c/cups/testing/amd64/

I have requested the cups test in testing with ghostscript from
experimental. I hasn't finished yet, albeit it probably started soon
after I requested it at 2018-08-31 19:20:50 UTC, so this isn't looking
good. Feel free to check in 2:30 hours or so, it should be visible at
the page linked above with the trigger "elbrus ghostscript from
experimental". If that ran for 2:47 and failed it probably timed out
(which you can confirm by looking at the bottom of the test log).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#907655: xserver-xorg-video-mga: X don't start with the latest package version

[Davide Prina]

On 31/08/2018 17:15, Julien Cristau wrote:


Please provide the full Xorg logs from the working and not-working cases.


I attached the following Xorg.0.log:
* bad_var_log_Xorg.0.log is /var/log/Xorg.0.log
* good_local_share_xorg_Xorg.0.log is ~/.local/share/xorg/Xorg.0.log
* good_var_log_Xorg.0.log is /var/log/Xorg.0.log

"good" is when X works correctly and "bad" what the screen hung up. Note 
that there is not a bad for .local/share/xorg because it written only in 
the "good" case.


Ciao
Davide
[  1680.867] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[  1680.888] X Protocol Version 11, Revision 0
[  1680.894] Build Operating System: Linux 4.9.0-5-amd64 i686 Debian
[  1680.902] Current Operating System: Linux debian-eeepc 4.17.0-3-686-pae #1 SMP Debian 4.17.17-1 (2018-08-18) i686
[  1680.902] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-3-686-pae root=UUID=0a5125b0-7623-41ad-9924-f86564311fe3 ro single
[  1680.917] Build Date: 26 January 2018  05:11:03PM
[  1680.924] xorg-server 2:1.19.6-1 (https://www.debian.org/support) 
[  1680.932] Current version of pixman: 0.34.0
[  1680.948] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  1680.948] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1680.981] (==) Log file: "/home/davide/.local/share/xorg/Xorg.0.log", Time: Thu Aug 30 20:11:16 2018
[  1681.003] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1681.066] (==) No Layout section.  Using the first Screen section.
[  1681.066] (==) No screen section available. Using defaults.
[  1681.066] (**) |-->Screen "Default Screen Section" (0)
[  1681.066] (**) |   |-->Monitor ""
[  1681.066] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[  1681.067] (==) Automatically adding devices
[  1681.067] (==) Automatically enabling devices
[  1681.067] (==) Automatically adding GPU devices
[  1681.067] (==) Max clients allowed: 256, resource mask: 0x1f
[  1681.135] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  1681.135] 	Entry deleted from font path.
[  1681.196] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[  1681.196] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1681.196] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[  1681.197] (II) Loader magic: 0x770720
[  1681.197] (II) Module ABI versions:
[  1681.197] 	X.Org ANSI C Emulation: 0.4
[  1681.197] 	X.Org Video Driver: 23.0
[  1681.197] 	X.Org XInput driver : 24.1
[  1681.197] 	X.Org Server Extension : 10.0
[  1681.218] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
[  1681.218] (++) using VT number 1

[  1681.222] (II) xfree86: Adding drm device (/dev/dri/card0)
[  1681.241] (--) PCI:*(0:0:2:0) 8086:8108:1043:83ce rev 7, Mem @ 0xf3f8/524288, 0xd000/268435456, 0xf3f4/262144, I/O @ 0xc880/8, BIOS @ 0x/131072
[  1681.241] (II) LoadModule: "glx"
[  1681.254] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1681.369] (II) Module glx: vendor="X.Org Foundation"
[  1681.369] 	compiled for 1.19.6, module version = 1.0.0
[  1681.369] 	ABI class: X.Org Server Extension, version 10.0
[  1681.369] (==) Matched psb as autoconfigured driver 0
[  1681.369] (==) Matched psb_drv as autoconfigured driver 1
[  1681.369] (==) Matched psb as autoconfigured driver 2
[  1681.369] (==) Matched psb_drv as autoconfigured driver 3
[  1681.369] (==) Matched modesetting as autoconfigured driver 4
[  1681.369] (==) Matched fbdev as autoconfigured driver 5
[  1681.369] (==) Matched vesa as autoconfigured driver 6
[  1681.370] (==) Assigned the driver to the xf86ConfigLayout
[  1681.370] (II) LoadModule: "psb"
[  1681.371] (WW) Warning, couldn't open module psb
[  1681.371] (II) UnloadModule: "psb"
[  1681.371] (II) Unloading psb
[  1681.371] (EE) Failed to load module "psb" (module does not exist, 0)
[  1681.371] (II) LoadModule: "psbdrv"
[  1681.373] (WW) Warning, couldn't open module psbdrv
[  1681.373] (II) UnloadModule: "psbdrv"
[  1681.373] (II) Unloading psbdrv
[  1681.373] (EE) Failed to load module "psbdrv" (module does not exist, 0)
[  1681.373] (II) LoadModule: "modesetting"
[  1681.373] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1681.374] (II) Module modesetting: vendor="X.Org Foundation"
[  1681.374] 	compiled for 1.19.6, module version = 1.19.6
[  1681.374] 	Module class: X.Org Video Driver
[  1681.374] 	ABI class: 

Bug#907718: python-dateutil breaks python-vobject autopkgtest

[Paul Gevers]

Source: python-dateutil, python-vobject
Control: found -1 python-dateutil/2.7.3-1
Control: found -1 python-vobject/0.9.5-2
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of python-dateutil the autopkgtest of
python-vobject started to fail in testing. I copied some of the output
below.

Currently this regression is contributing to the delay of the migration
of python-dateutil to testing [1]. Due to the nature of this issue, I
filed it against both packages. Could you please investigate the
situation and reassign the bug to the right package? If needed, please
change the bug's severity as appropriate.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=python-dateutil

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-vobject/911079/log.gz


autopkgtest [04:58:43]: test command2: cd debian/tests && ./test.sh 3
autopkgtest [04:58:43]: test command2: [---
.{name} {levelname} {message}
sE
==
ERROR: test_recurrence (__main__.TestIcalendar)
--
Traceback (most recent call last):
  File "./tests.py", line 754, in test_recurrence
dates = list(cal.vevent.getrruleset())
  File "/usr/lib/python3/dist-packages/vobject/icalendar.py", line 453,
in getrruleset
ignoretz=isinstance(dtstart, datetime.date))
  File "/usr/lib/python3/dist-packages/dateutil/rrule.py", line 1667, in
__call__
return self._parse_rfc(s, **kwargs)
  File "/usr/lib/python3/dist-packages/dateutil/rrule.py", line 1550, in
_parse_rfc
tzinfos=tzinfos)
  File "/usr/lib/python3/dist-packages/dateutil/rrule.py", line 1509, in
_parse_rfc_rrule
return rrule(dtstart=dtstart, cache=cache, **rrkwargs)
  File "/usr/lib/python3/dist-packages/dateutil/rrule.py", line 464, in
__init__
'RRULE UNTIL values must be specified in UTC when DTSTART '
ValueError: RRULE UNTIL values must be specified in UTC when DTSTART is
timezone-aware

--
Ran 39 tests in 0.229s

FAILED (errors=1, skipped=1)
autopkgtest [04:58:44]: test command2: ---]




signature.asc
Description: OpenPGP digital signature

Bug#868179: xserver-xorg-video-radeon: SEGV when starting X11

[bartek 'basz' szurgot]

On 08/07/2018 11:21 AM, Simon McVittie wrote:
> On Sat, 15 Jul 2017 at 12:13:34 +0900, Michel Dänzer wrote:
>> On 15/07/17 03:57 AM, bartek 'basz' szurgot wrote:
>>> knowing the exact conditions under which SEGV occurs
>>> (i.e. rotated screen in xorg.conf), i agree it is not a "grave" bug.
>> It's even more specific than that: The crash only happens if xorg.conf
>> contains rotation and a Virtual stanza (which BTW is probably useless in
>> this case anyway).
> Downgrading to important based on this reasoning, and retitling to be more
> specific.

+1

>>> when the fix is expected to arrive to the xserver-xorg-video-radeon
>>> package in Debian-testing?
>> I have to defer to the Debian packagers on that. Upstream it'll likely
>> only be in the 7.10.0 release.
> The 18.0.1 release (xserver-xorg-video-ati/1:18.0.1-1) is now available in
> Debian testing and unstable. bartek, does that resolve this crash for you?

i works stable for me for quite some time now. recently there was short
time when i had to downgrade driver again:
/apt-get install xserver-xorg-video-radeon=1:7.8.0-1+b1
xserver-xorg-core=2:1.19.2-1+deb9u2/
to make 2nd screen operational. but before i managed to find time to
report, it got back to normal. today i've upgraded and everything works
fine with:
xserver-xorg-core 2:1.20.1-1 amd64
xserver-xorg-video-radeon 1:18.0.1-2 amd64

i think we can close the ticket.

-- 
pozdrawiam serdecznie / best regards,
bartek 'basz' szurgot
/* https://www.baszerr.eu */
/* https://www.baszerr.eu/misc/pgp.txt */




signature.asc
Description: OpenPGP digital signature

Bug#907681: lintian: false positive source-only-upload-to-non-free-without-autobuild

[Chris Lamb]

Hi Andreas,

> source-only-upload-to-non-free-without-autobuild does not seem to work
> as intended ... it flags the nvidia-graphics-drivers package which has
> been autobuilt for years ...

Ah, whoops, we are checking the .changes file instead of the .dsc.


Regards,

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

Bug#905586: lxc: diff for NMU version 1:2.0.9-6.1

[Salvatore Bonaccorso]

Hi Antonio,

On Fri, Aug 31, 2018 at 04:07:56PM -0300, Antonio Terceiro wrote:
> On Fri, Aug 31, 2018 at 02:42:15PM +0200, Salvatore Bonaccorso wrote:
> > Hi Antonio,
> > 
> > On Fri, Aug 31, 2018 at 08:14:57AM -0300, Antonio Terceiro wrote:
> > > On Thu, Aug 30, 2018 at 10:06:15PM +0200, Salvatore Bonaccorso wrote:
> > > > Control: tags 905586 + pending
> > > > 
> > > > 
> > > > Dear maintainer,
> > > > 
> > > > I've prepared an NMU for lxc (versioned as 1:2.0.9-6.1) and
> > > > uploaded it to DELAYED/5.
> > > 
> > > Thanks!
> > > 
> > > > Please feel free to tell me if I should delay it longer.
> > > 
> > > on the contrary: please feel free to make it an immediate upload. I will
> > > import your diff in the git repository
> > 
> > Thank you, I just have rescheduled it.
> > 
> > if you prefer to have the single commits they are attached to this
> > mail. I realize you probably would have prefered a proper merge
> > request, but I did not start working from the salsa repo but from a
> > gbp import-dsc git repo.
> 
> I had already applied the original diff that you posted before I
> replied.

Perfect, thanks a lot!

Regards,
Salvatore

Bug#906380: libtool: FTBFS in buster/sid

[shirish शिरीष]

at bottom :-

On 31/08/2018, Juhani Numminen  wrote:
> Dear Shirish,
>
> shirish शिरीष kirjoitti 31.08.2018 klo 07:58:> Could you upload the built
> libtool binary somewhere so I could install
>> it and see if the issue goes away ?
>
> I've now put the build sources and binaries there:
> https://drive.google.com/drive/folders/1t1eGf3J5Febr71oW859lmirkA3ddtxIK
>
> shirish शिरीष kirjoitti 30.08.2018 klo 17:48:
>> Wish I could help but cannot even install dget i.e. devscripts due to
>> the libtool and other bugs
>>
>> $ sudo aptitude install devscripts -y
> [snip]
>> Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
>> n
>
> Could you answer Y here? apt-listbugs shouldn't prevent you from installing
> packages, it is just giving you a heads-up before the install.
>
>> Btw, thank you for sharing the updated instructions, have bookmarked it
>> :)
>
> You're welcome!
>
>
> Juhani
>

Dear Juhani,

Thank you for sharing your expertise .

I was able to (finally) do everything as needed -

Sharing the test results and you have already done everything beforehand.

Just one thing I had to modify your command while building to

$ sudo cowbuilder --build ../libtool_2.4.6-2.1local1.dsc

instead of

$ sudo cowbuilder --build ../libtool_2.4.6-2.1+local1.dsc and it worked.

I do have the updated results in

/var/cache/pbuilder/result$ ls
libltdl7_2.4.6-2.1local1_amd64.deb
libtool_2.4.6-2.1local1_amd64.build  libtool_2.4.6-2.1local1.dsc
libltdl7-dbgsym_2.4.6-2.1local1_amd64.deb
libtool_2.4.6-2.1local1_amd64.buildinfo
libtool-bin_2.4.6-2.1local1_amd64.deb
libltdl-dev_2.4.6-2.1local1_amd64.deb
libtool_2.4.6-2.1local1_amd64.changes
libtool-doc_2.4.6-2.1local1_all.deb
libtool_2.4.6-2.1local1_all.deblibtool_2.4.6-2.1local1.debian.tar.xz

I was also able to install the newly locally built deb packages
without an issue -

$ sudo dpkg -i *.deb
[sudo] password for shirish:
.xxx
Preparing to unpack libltdl7_2.4.6-2.1local1_amd64.deb ...
Unpacking libltdl7:amd64 (2.4.6-2.1local1) over (2.4.6-2.1) ...
Selecting previously unselected package libltdl7-dbgsym:amd64.
Preparing to unpack libltdl7-dbgsym_2.4.6-2.1local1_amd64.deb ...
Unpacking libltdl7-dbgsym:amd64 (2.4.6-2.1local1) ...
Preparing to unpack libltdl-dev_2.4.6-2.1local1_amd64.deb ...
Unpacking libltdl-dev:amd64 (2.4.6-2.1local1) over (2.4.6-2.1) ...
Preparing to unpack libtool_2.4.6-2.1local1_all.deb ...
Unpacking libtool (2.4.6-2.1local1) over (2.4.6-2.1) ...
Selecting previously unselected package libtool-bin.
Preparing to unpack libtool-bin_2.4.6-2.1local1_amd64.deb ...
Unpacking libtool-bin (2.4.6-2.1local1) ...
Selecting previously unselected package libtool-doc.
Preparing to unpack libtool-doc_2.4.6-2.1local1_all.deb ...
Unpacking libtool-doc (2.4.6-2.1local1) ...
Setting up libltdl7:amd64 (2.4.6-2.1local1) ...
Setting up libltdl7-dbgsym:amd64 (2.4.6-2.1local1) ...
Setting up libltdl-dev:amd64 (2.4.6-2.1local1) ...
Setting up libtool (2.4.6-2.1local1) ...
Setting up libtool-bin (2.4.6-2.1local1) ...
Setting up libtool-doc (2.4.6-2.1local1) ...
Processing triggers for libc-bin (2.27-5) ...
Processing triggers for man-db (2.8.4-2) ...
Processing triggers for install-info (6.5.0.dfsg.1-4) ...

Just not sharing the number of files and directories involved.

Now just the maintainer needs to look at your patch and the work done.

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


libtoolize-build-tests
Description: Binary data

Bug#892183: ruby-rbpdf: FTBFS and Debci failure with Ruby 2.5

[Hashem Nasarat]

I made some good progress with packaging a new version of ruby-rbpdf:
https://salsa.debian.org/hnasarat-guest/ruby-rbpdf/network/master

Now to find a sponsor?

Bug#905586: lxc: diff for NMU version 1:2.0.9-6.1

[Antonio Terceiro]

On Fri, Aug 31, 2018 at 02:42:15PM +0200, Salvatore Bonaccorso wrote:
> Hi Antonio,
> 
> On Fri, Aug 31, 2018 at 08:14:57AM -0300, Antonio Terceiro wrote:
> > On Thu, Aug 30, 2018 at 10:06:15PM +0200, Salvatore Bonaccorso wrote:
> > > Control: tags 905586 + pending
> > > 
> > > 
> > > Dear maintainer,
> > > 
> > > I've prepared an NMU for lxc (versioned as 1:2.0.9-6.1) and
> > > uploaded it to DELAYED/5.
> > 
> > Thanks!
> > 
> > > Please feel free to tell me if I should delay it longer.
> > 
> > on the contrary: please feel free to make it an immediate upload. I will
> > import your diff in the git repository
> 
> Thank you, I just have rescheduled it.
> 
> if you prefer to have the single commits they are attached to this
> mail. I realize you probably would have prefered a proper merge
> request, but I did not start working from the salsa repo but from a
> gbp import-dsc git repo.

I had already applied the original diff that you posted before I
replied.


signature.asc
Description: PGP signature

Bug#907717: linux-image-4.17.0-0.bpo.3-amd64: random backtrace caused by refcount on Xorg

[m . alfaeko]

Package: src:linux
Version: 4.17.17-1~bpo9+1
Severity: normal

Dear Maintainer,

I had installed new kernel from debian backports repository, but im experiencing
some backtrace logs in system kern.log file. This does not affect systems
stability. Backtrace is caused by refcount and its affecting Xorg process.
My machine is running with nonfree firmware for APU and other devices which
require nonfree firmware to function properly.

Thank you for your time and i hope this helps improve debians stability

-- Package-specific info:
** Version:
Linux version 4.17.0-0.bpo.3-amd64 (debian-ker...@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.17.17-1~bpo9+1 
(2018-08-27)

** Command line:
BOOT_IMAGE=/vmlinuz-4.17.0-0.bpo.3-amd64 root=/dev/mapper/debian--stretch-root 
ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 3401
board_vendor: ASUSTeK COMPUTER INC.
board_name: PRIME A320M-K
board_version: Rev X.0x

** Loaded modules:
pci_stub
vboxpci(O)
vboxnetadp(O)
vboxnetflt(O)
vboxdrv(O)
xt_tcpudp
xt_conntrack
iptable_nat
nf_conntrack_ipv4
nf_defrag_ipv4
nf_nat_ipv4
nf_nat
nf_conntrack
iptable_filter
binfmt_misc
dm_thin_pool
amdkfd
dm_persistent_data
dm_bio_prison
dm_bufio
libcrc32c
amdgpu
eeepc_wmi
wmi_bmof
snd_hda_codec_realtek
asus_wmi
snd_hda_codec_hdmi
snd_hda_codec_generic
sparse_keymap
rfkill
snd_hda_intel
snd_hda_codec
chash
edac_mce_amd
snd_hda_core
kvm_amd
gpu_sched
ttm
snd_hwdep
snd_pcm
ccp
rng_core
drm_kms_helper
snd_timer
kvm
drm
snd
sg
soundcore
irqbypass
shpchp
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
k10temp
evdev
serio_raw
fam15h_power
i2c_algo_bit
sp5100_tco
pcspkr
video
button
wmi
pcc_cpufreq
acpi_cpufreq
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
dm_mod
sr_mod
cdrom
sd_mod
hid_generic
uas
usbhid
usb_storage
hid
crc32c_intel
aesni_intel
aes_x86_64
ahci
xhci_pci
crypto_simd
libahci
cryptd
glue_helper
xhci_hcd
libata
usbcore
i2c_piix4
r8169
mii
scsi_mod
usb_common
gpio_amdpt
gpio_generic

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:1576]
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Carrizo [1002:9874] (rev e2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Carrizo [1043:8719]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: amdgpu

00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini 
HDMI/DP Audio [1002:9840]
Subsystem: ASUSTeK Computer Inc. Kabini HDMI/DP Audio [1043:8719]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:157b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:157b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:09.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:157d]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: snd_hda_intel

00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller [1022:7914] (rev 20) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8719]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- 

Bug#907715: lua-mode: FTBFS in buster/sid ("No buffer named *lua5.3*")

[Santiago Vila]

Package: src:lua-mode
Version: 20151025-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with elpa
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
Loading 00debian-vars...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading 00debian-vars...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading 00debian-vars...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...

[... snipped ...]

Indenting region...
Indenting region...done

  reindents according to luawiki examples

Hiding process buffer does not switch current window
  when process is active
  when process is active
  and does not signal when process is already killed
  and does not signal when process is already killed
  when process is not started
  when process is not started

Fontification in compilation buffer
  fontifies runtime error messages
  fontifies runtime error messages  
  fontifies syntax error messages
  fontifies syntax error messages  
  does not ask for file on "stdin:NN" errors
  does not ask for file on "stdin:NN" errors  FAILED

Test indent-new-comment-line
  works with -- ...
  works with -- ...
  works with  
  works with  
  doesn't recognize "--" inside strings and comments
  doesn't recognize "--" inside strings and comments
  works when the comment is empty
  works when the comment is empty


Fontification in compilation buffer does not ask for file on "stdin:NN" 
errors

Traceback (most recent call last):
  (unwind-protect (progn (save-current-buffer (setq buf (find-file fname)) (...
  (kill-buffer "*lua5.3*")
error: (error "No buffer named *lua5.3*")


Ran 59 out of 66 specs, 1 failed, in 0.2 seconds.

dh_elpa_test: buttercup -L . returned exit code 255
make: *** [debian/rules:4: build-indep] Error 255
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


This is just how the build ends and not necessarily the relevant part.
For full build logs please see:

https://people.debian.org/~sanvila/build-logs/lua-mode/

To reproduce, please try building with sbuild on a single-CPU machine, where
this error seems to happen 95% of the time.

Thanks.

Bug#907713: golang-github-fsouza-go-dockerclient: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-fsouza-go-dockerclient
Version: 1.2.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang --builddirectory=_build
   dh_update_autotools_config -i -O--buildsystem=golang 
-O--builddirectory=_build
   dh_autoreconf -i -O--buildsystem=golang -O--builddirectory=_build
   dh_auto_configure -i -O--buildsystem=golang -O--builddirectory=_build
   dh_auto_build -i -O--buildsystem=golang -O--builddirectory=_build
cd _build && go install 
-gcflags=\"-trimpath=/<>/_build/src\" 
-asmflags=\"-trimpath=/<>/_build/src\" -v -p 1 
github.com/fsouza/go-dockerclient github.com/fsouza/go-dockerclient/testing
github.com/opencontainers/go-digest
github.com/opencontainers/image-spec/specs-go
github.com/opencontainers/image-spec/specs-go/v1
github.com/docker/docker/api/types/registry
github.com/docker/docker/api/types/blkiodev
github.com/docker/docker/api/types/mount
github.com/docker/docker/api/types/strslice

[... snipped ...]

--- PASS: TestRenameContainer (0.00s)
=== CONT  TestCreateContainerImageNotFound
--- PASS: TestCreateContainerImageNotFound (0.00s)
=== CONT  TestCreateContainerInvalidName
--- PASS: TestCreateContainerInvalidName (0.00s)
=== CONT  TestCreateMultipleContainersEmptyName
--- PASS: TestCreateMultipleContainersEmptyName (0.00s)
=== CONT  TestCreateContainerDuplicateName
--- PASS: TestCreateContainerDuplicateName (0.00s)
=== CONT  TestCreateContainerInvalidBody
--- PASS: TestCreateContainerInvalidBody (0.00s)
=== CONT  TestCreateContainerWithNotifyChannel
--- PASS: TestCreateContainerWithNotifyChannel (0.00s)
=== CONT  TestCreateContainer
--- PASS: TestCreateContainer (0.00s)
=== CONT  TestListContainersFilterLabels
--- PASS: TestListContainersFilterLabels (0.00s)
=== CONT  TestListRunningContainers
--- PASS: TestListRunningContainers (0.00s)
=== CONT  TestListContainers
--- PASS: TestListContainers (0.00s)
=== CONT  TestCustomHandlerRegexp
--- PASS: TestCustomHandlerRegexp (0.00s)
=== CONT  TestCustomHandler
--- PASS: TestCustomHandler (0.00s)
=== CONT  TestSetHook
--- PASS: TestSetHook (0.00s)
=== CONT  TestHandleWithHook
--- PASS: TestHandleWithHook (0.00s)
=== CONT  TestServerURLNoListener
--- PASS: TestServerURLNoListener (0.00s)
=== CONT  TestServerURL
--- PASS: TestServerURL (0.00s)
=== CONT  TestServerStopNoListener
--- PASS: TestServerStopNoListener (0.00s)
=== CONT  TestServerStop
--- PASS: TestServerStop (0.00s)
=== CONT  TestNewTLSServer
2018/08/27 09:12:05 http: TLS handshake error from 127.0.0.1:52230: EOF
--- PASS: TestNewTLSServer (0.01s)
PASS
ok  github.com/fsouza/go-dockerclient/testing   1.575s
dh_auto_test: cd _build && go test -vet=off -v -p 1 
github.com/fsouza/go-dockerclient github.com/fsouza/go-dockerclient/testing 
returned exit code 1
make: *** [debian/rules:11: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


This is just how the build ends and not necessarily the relevant part.
For full build logs please see:

https://people.debian.org/~sanvila/build-logs/golang-github-fsouza-go-dockerclient/

I suspect of a race condition or something alike, because this failure
does not seem to happen in reproducible builds. However, I can
reproduce it 100% of the time, so if you could not reproduce it, I
would gladly offer a test machine where this happens (please contact
me privately for details).

Thanks.

Bug#907714: golang-x-text: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-x-text
Version: 0.3.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
golang.org/x/text golang.org/x/text/cases golang.org/x/text/collate 
golang.org/x/text/collate/build golang.org/x/text/currency 
golang.org/x/text/date golang.org/x/text/encoding 
golang.org/x/text/encoding/charmap golang.org/x/text/encoding/htmlindex 
golang.org/x/text/encoding/ianaindex golang.org/x/text/encoding/internal 
golang.org/x/text/encoding/internal/enctest 
golang.org/x/text/encoding/internal/identifier 
golang.org/x/text/encoding/japanese golang.org/x/text/encoding/korean 
golang.org/x/text/encoding/simplifiedchinese 
golang.org/x/text/encoding/traditionalchinese 
golang.org/x/text/encoding/unicode golang.org/x/text/encoding/unicode/utf32 
golang.org/x/text/feature/plural golang.org/x/text/internal 
golang.org/x/text/internal/catmsg golang.org/x/text/internal/cldrtree 
golang.org/x/text/internal/colltab golan
 g.org/x/text/internal/export/idna golang.org/x/text/internal/format 
golang.org/x/text/internal/gen golang.org/x/text/internal/number 
golang.org/x/text/internal/stringset golang.org/x/text/internal/tag 
golang.org/x/text/internal/testtext golang.org/x/text/internal/triegen 
golang.org/x/text/internal/ucd golang.org/x/text/internal/utf8internal 
golang.org/x/text/language golang.org/x/text/language/display 
golang.org/x/text/message golang.org/x/text/message/catalog 
golang.org/x/text/number golang.org/x/text/runes golang.org/x/text/search 
golang.org/x/text/secure golang.org/x/text/secure/bidirule 
golang.org/x/text/secure/precis golang.org/x/text/transform 
golang.org/x/text/unicode golang.org/x/text/unicode/bidi 
golang.org/x/text/unicode/cldr golang.org/x/text/unicode/norm 
golang.org/x/text/unicode/rangetable golang.org/x/text/unicode/runenames 
golang.org/x/text/width
golang.org/x/text
golang.org/x/text/internal/tag
golang.org/x/text/language
golang.org/x/text/internal
golang.org/x/text/transform
golang.org/x/text/unicode/norm
golang.org/x/text/cases

[... snipped ...]

=== RUN   TestNarrowSingleRunes
--- PASS: TestNarrowSingleRunes (0.03s)
=== RUN   TestNarrow
=== RUN   TestNarrow/empty
=== RUN   TestNarrow/short_source_1
=== RUN   TestNarrow/short_source_2
=== RUN   TestNarrow/incomplete_but_terminated_source_1
=== RUN   TestNarrow/incomplete_but_terminated_source_2
=== RUN   TestNarrow/exact_fit_dst
=== RUN   TestNarrow/exact_fit_dst_some_span
=== RUN   TestNarrow/empty_dst
=== RUN   TestNarrow/empty_dst_ascii
=== RUN   TestNarrow/short_dst_1
=== RUN   TestNarrow/short_dst_2
=== RUN   TestNarrow/ambiguous
=== RUN   TestNarrow/short_dst_fast_path
=== RUN   TestNarrow/short_dst_larger_buffer
=== RUN   TestNarrow/fast_path_alternation
--- PASS: TestNarrow (0.00s)
--- PASS: TestNarrow/empty (0.00s)
--- PASS: TestNarrow/short_source_1 (0.00s)
--- PASS: TestNarrow/short_source_2 (0.00s)
--- PASS: TestNarrow/incomplete_but_terminated_source_1 (0.00s)
--- PASS: TestNarrow/incomplete_but_terminated_source_2 (0.00s)
--- PASS: TestNarrow/exact_fit_dst (0.00s)
--- PASS: TestNarrow/exact_fit_dst_some_span (0.00s)
--- PASS: TestNarrow/empty_dst (0.00s)
--- PASS: TestNarrow/empty_dst_ascii (0.00s)
--- PASS: TestNarrow/short_dst_1 (0.00s)
--- PASS: TestNarrow/short_dst_2 (0.00s)
--- PASS: TestNarrow/ambiguous (0.00s)
--- PASS: TestNarrow/short_dst_fast_path (0.00s)
--- PASS: TestNarrow/short_dst_larger_buffer (0.00s)
--- PASS: TestNarrow/fast_path_alternation (0.00s)
=== RUN   ExampleTransformer_fold
--- PASS: ExampleTransformer_fold (0.00s)
=== RUN   ExampleTransformer_widen
--- PASS: ExampleTransformer_widen (0.00s)
=== RUN   ExampleTransformer_narrow
--- PASS: ExampleTransformer_narrow (0.00s)
PASS
ok  golang.org/x/text/width 0.109s
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
golang.org/x/text golang.org/x/text/cases golang.org/x/text/collate 
golang.org/x/text/collate/build golang.org/x/text/currency 
golang.org/x/text/date golang.org/x/text/encoding 
golang.org/x/text/encoding/charmap golang.org/x/text/encoding/htmlindex 
golang.org/x/text/encoding/ianaindex golang.org/x/text/encoding/internal 
golang.org/x/text/encoding/internal/enctest 
golang.org/x/text/encoding/internal/identifier 
golang.org/x/text/encoding/japanese golang.org/x/text/encoding/korean 
golang.org/x/text/encoding/simplifiedchinese 
golang.org/x/text/encoding/traditionalchinese 

Bug#907716: rpyc: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:rpyc
Version: 3.4.4-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config 
running config
/usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution 
option: 'tests_require'
  warnings.warn(msg)
/usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution 
option: 'test_suite'
  warnings.warn(msg)
/usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution 
option: 'install_requires'
  warnings.warn(msg)

[... snipped ...]

.S
==
ERROR: test (test_splitbrain.SplitbrainTest)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.6_rpyc/build/tests/test_splitbrain.py", 
line 36, in setUp
self.conn = rpyc.classic.connect(host, int(port))
  File 
"/<>/.pybuild/cpython3_3.6_rpyc/build/rpyc/utils/classic.py", line 
68, in connect
return factory.connect(host, port, SlaveService, ipv6 = ipv6, keepalive = 
keepalive)
  File 
"/<>/.pybuild/cpython3_3.6_rpyc/build/rpyc/utils/factory.py", line 
90, in connect
s = SocketStream.connect(host, port, ipv6 = ipv6, keepalive = keepalive)
  File "/<>/.pybuild/cpython3_3.6_rpyc/build/rpyc/core/stream.py", 
line 150, in connect
return cls(cls._connect(host, port, **kwargs))
  File "/<>/.pybuild/cpython3_3.6_rpyc/build/rpyc/core/stream.py", 
line 108, in _connect
s.connect(sockaddr)
ConnectionRefusedError: [Errno 111] Connection refused

==
ERROR: test (test_teleportation.TeleportationTest)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.6_rpyc/build/tests/test_teleportation.py",
 line 38, in setUp
self.conn = rpyc.classic.connect(host, int(port))
  File 
"/<>/.pybuild/cpython3_3.6_rpyc/build/rpyc/utils/classic.py", line 
68, in connect
return factory.connect(host, port, SlaveService, ipv6 = ipv6, keepalive = 
keepalive)
  File 
"/<>/.pybuild/cpython3_3.6_rpyc/build/rpyc/utils/factory.py", line 
90, in connect
s = SocketStream.connect(host, port, ipv6 = ipv6, keepalive = keepalive)
  File "/<>/.pybuild/cpython3_3.6_rpyc/build/rpyc/core/stream.py", 
line 150, in connect
return cls(cls._connect(host, port, **kwargs))
  File "/<>/.pybuild/cpython3_3.6_rpyc/build/rpyc/core/stream.py", 
line 108, in _connect
s.connect(sockaddr)
ConnectionRefusedError: [Errno 111] Connection refused
 >> begin captured logging << 
SLAVE/18812: INFO: server has terminated
SLAVE/18812: INFO: goodbye ('127.0.0.1', 53438)
- >> end captured logging << -

--
Ran 41 tests in 45.924s

FAILED (SKIP=9, errors=2)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.6_rpyc/build; python3.6 -m nose tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
make: *** [debian/rules:12: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


This is just how the build ends and not necessarily the relevant part.
For full build logs please see:

https://people.debian.org/~sanvila/build-logs/rpyc/

To reproduce, please try building with sbuild on a single-CPU machine, where
this error seems to happen 100% of the time.

Thanks.

Bug#907712: src:requestpolicy: please package upstream version 1.0.beta13.2

[Daniel Kahn Gillmor]

Package: src:requestpolicy
Version: 1.0.0~beta12.3+dfsg-1
Severity: wishlist

according to
https://github.com/RequestPolicyContinued/requestpolicy/releases a new
beta release has been available for nearly a year.  In git
(https://github.com/RequestPolicyContinued/requestpolicy) there are
many new commits on top of v1.0.beta13.2 as well, if you wanted to try
to make an experimental package from a git snapshot.

 --dkg

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

Kernel: Linux 4.17.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)

Bug#907711: libsdl2 FTCBFS: lintian tag autotools-pkg-config-macro-not-cross-compilation-safe

[Helmut Grohne]

Source: libsdl2
Version: 2.0.8+dfsg1-1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

libsdl2 fails to cross build from source, because it uses the build
architecture pkg-config and thus fails finding a number of dependencies.
Lintian has a more detailed explanation. The attached patch fixes that
and makes libsdl2 cross build successfully. Please consider applying it.

Helmut
--- libsdl2-2.0.8+dfsg1.orig/configure.in
+++ libsdl2-2.0.8+dfsg1/configure.in
@@ -56,6 +56,7 @@
 AC_PROG_INSTALL
 AC_PROG_MAKE_SET
 AC_CHECK_TOOL(WINDRES, [windres], [:])
+PKG_PROG_PKG_CONFIG
 
 dnl Make sure that srcdir is a full pathname
 case "$host" in
@@ -861,9 +862,8 @@
 
 JACK_REQUIRED_VERSION=0.125
 
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
 AC_MSG_CHECKING(for JACK $JACK_REQUIRED_VERSION support)
-if test x$PKG_CONFIG != xno; then
+if test x$PKG_CONFIG != x; then
 if $PKG_CONFIG --atleast-pkgconfig-version 0.7 && $PKG_CONFIG --atleast-version $JACK_REQUIRED_VERSION jack; then
 JACK_CFLAGS=`$PKG_CONFIG --cflags jack`
 JACK_LIBS=`$PKG_CONFIG --libs jack`
@@ -953,9 +953,8 @@
 
 PULSEAUDIO_REQUIRED_VERSION=0.9
 
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
 AC_MSG_CHECKING(for PulseAudio $PULSEAUDIO_REQUIRED_VERSION support)
-if test x$PKG_CONFIG != xno; then
+if test x$PKG_CONFIG != x; then
 if $PKG_CONFIG --atleast-pkgconfig-version 0.7 && $PKG_CONFIG --atleast-version $PULSEAUDIO_REQUIRED_VERSION libpulse-simple; then
 PULSEAUDIO_CFLAGS=`$PKG_CONFIG --cflags libpulse-simple`
 PULSEAUDIO_LIBS=`$PKG_CONFIG --libs libpulse-simple`
@@ -1165,9 +1164,8 @@
 
 FUSIONSOUND_REQUIRED_VERSION=1.1.1
 
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
 AC_MSG_CHECKING(for FusionSound $FUSIONSOUND_REQUIRED_VERSION support)
-if test x$PKG_CONFIG != xno; then
+if test x$PKG_CONFIG != x; then
 if $PKG_CONFIG --atleast-pkgconfig-version 0.7 && $PKG_CONFIG --atleast-version $FUSIONSOUND_REQUIRED_VERSION fusionsound; then
 FUSIONSOUND_CFLAGS=`$PKG_CONFIG --cflags fusionsound`
 FUSIONSOUND_LIBS=`$PKG_CONFIG --libs fusionsound`
@@ -1386,10 +1384,9 @@
   ,enable_video_wayland_qt_touch=yes)
 
 if test x$enable_video = xyes -a x$enable_video_wayland = xyes; then
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
 AC_MSG_CHECKING(for Wayland support)
 video_wayland=no
-if  test x$PKG_CONFIG != xno && \
+if  test x$PKG_CONFIG != x && \
 test x$video_opengl_egl = xyes && \
 test x$video_opengles_v2 = xyes; then
 if $PKG_CONFIG --exists wayland-client wayland-scanner wayland-protocols wayland-egl wayland-cursor egl xkbcommon ; then
@@ -1472,10 +1469,9 @@
   ,enable_video_mir=no)
 
 if test x$enable_video = xyes -a x$enable_video_mir = xyes; then
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
 AC_MSG_CHECKING(for Mir support)
 video_mir=no
-if test x$PKG_CONFIG != xno; then
+if test x$PKG_CONFIG != x; then
 if $PKG_CONFIG --exists mirclient egl xkbcommon ; then
 MIR_CFLAGS=`$PKG_CONFIG --cflags mirclient egl xkbcommon`
 MIR_LIBS=`$PKG_CONFIG --libs mirclient egl xkbcommon`
@@ -1571,8 +1567,7 @@
 AC_HELP_STRING([--enable-video-rpi], [use Raspberry Pi video driver [[default=yes]]]),
   , enable_video_rpi=yes)
 if test x$enable_video = xyes -a x$enable_video_rpi = xyes; then
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
-if test x$PKG_CONFIG != xno && $PKG_CONFIG --exists bcm_host; then
+if test x$PKG_CONFIG != x && $PKG_CONFIG --exists bcm_host; then
 RPI_CFLAGS=`$PKG_CONFIG --cflags bcm_host brcmegl`
 RPI_LDFLAGS=`$PKG_CONFIG --libs bcm_host brcmegl`
 elif test x$ARCH = xnetbsd; then
@@ -2112,8 +2107,7 @@
 DIRECTFB_REQUIRED_VERSION=1.0.0
 AC_PATH_PROGS(DIRECTFBCONFIG, directfb-config, no, [$prefix/bin:$PATH])
 if test x$DIRECTFBCONFIG = xno; then
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
-if test x$PKG_CONFIG != xno; then
+if test x$PKG_CONFIG != x; then
 if $PKG_CONFIG --atleast-pkgconfig-version 0.7 && $PKG_CONFIG --atleast-version $DIRECTFB_REQUIRED_VERSION directfb; then
 DIRECTFB_CFLAGS=`$PKG_CONFIG --cflags directfb`
 DIRECTFB_LIBS=`$PKG_CONFIG --libs directfb`
@@ -2194,8 +2188,7 @@
 LIBDRM_REQUIRED_VERSION=2.4.46
 LIBGBM_REQUIRED_VERSION=9.0.0
 
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
-if test x$PKG_CONFIG != xno; then
+if test x$PKG_CONFIG != x; then
 if $PKG_CONFIG --atleast-pkgconfig-version 0.7; then
 if $PKG_CONFIG --atleast-version $LIBDRM_REQUIRED_VERSION 

Bug#907706: devscripts: Incorrect output of dcontrol

[Adam D. Barratt]

Control: reassign -1 qa.debian.org

On Fri, 2018-08-31 at 20:18 +0300, Dmitry Bogatov wrote:
> I stumbled at following behaviour of `dcontrol' utility:

As per the manpage, dcontrol is an interface to https://qa.debian.org/c
gi-bin/dcontrol . If you perform the same queries via that script
directly, then you'll receive the same result, so dcontrol appears to
be behaving exactly correctly AFAICS.

>   $ dcontrol debhelper/sid
>   
>   Package: debhelper
>   Binary: debhelper, dh-systemd
>   Version: 11.3.5
[...]
>   Package: debhelper
>   Priority: optional
>   Section: devel
>   Installed-Size: 1520
>   Maintainer: Joey Hess 
>   Architecture: all
>   Version: 8.1.6
>
> Here it outputs information about multiple versions of debhelper,
> including rather old ones.

Indeed.

> Next:
> 
>   $ dcontrol debhelper/stretch
>   
> 
> Nothing. Why?

Because the CGI doesn't know about stretch, quite simply. Again, try
making queries via the https://qa.debian.org/cgi-bin/dcontrol
interface, and check the list of suites available in the dropdown.

> Maybe I just do not understand what `dcontrol' is expected
> to do, but I believe two mentioned queries are rather similar:
>
>  * I expect debhelper/sid report version in sid
> * I expect debhelper/stretch report version in stretch

As above, these both appears to be issues with the source data.

Regards,

Adam

Bug#906189: linux-image-4.17.0-1-amd64: Laptop does not suspend in 4.17 - worked up to 4.16

[Ben Hutchings]

Control: tag -1 moreinfo

On Wed, 2018-08-15 at 12:32 +0200, Christoph Haas wrote:
> Package: src:linux
> Version: 4.17.8-1
> Severity: important
> 
> Dear Maintainer,
> 
> I am using Debian Sid. Since the upgrade to linux-image-4.17.x I cannot
> suspend my Lenovo X230 laptop any more. I close the lid or run
> "systemctl suspend" to suspend the laptop but the laptop's power LED
> blinks and after a few seconds the laptop resumes automatically.
> This effect is easily reproducible.
> 
> Booting into 4.16.0-2-amd64 works well.
> 
> Linux kernel image 4.17.0-2 shows the mentioned problem.
> 
> It appears the multiple people on the internet ran into this problem. I
> did not find a workaround to this problem and will work with 4.16 now.
[...]

Has this been reported upstream (Bugzilla or an upstream mailing list)?

You didn't include any kernel log messages for the failed suspend,
which might help to explain this.

Ben.

-- 
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway.




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

Bug#907493: ghostscript breaks cups autopkgtest: test times out

[Paul Gevers]

Hi Jonas,

On 31-08-18 01:25, Jonas Smedegaard wrote:
> Do the freshly released experimental Ghostscript release help anything?

I'll trigger the test shortly and report back with the results.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#907493: ghostscript breaks cups autopkgtest: test times out

[Paul Gevers]

Dear all,

On 31-08-18 15:48, Till Kamppeter wrote:
> On 31/08/18 15:36, Didier 'OdyX' Raboud wrote:
>> Le vendredi, 31 août 2018, 01.25:24 h CEST Jonas Smedegaard a écrit :
>>> Do the freshly released experimental Ghostscript release help anything?
>>
>> It doesn't seem to, unfortunately. :-(
>>
>> To reproduce the issue; just run this as root:
>> /usr/share/cups/test-drivers

I tried this on my fully up-to-date testing/buster system and it fails
for a different reason:
lpinfo: Bad file descriptor

Not sure yet, what that means for any of this.

>> Surprisingly; it will fail when testing the _second_ printer, always.
>> Also, it
>> doesn't seem to get fixed with the ghostscript from testing.
>>
>> There's something fishy here, but I can't say with certainty that it's
>> ghostscript's fault :-(
> 
> Which driver is this second printer using?

As mentioned in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907493#26
DUMMY_PRINTER_NAME=test-printer0
driver=drv:///sample.drv/dymo.ppd

> Which version of cups-filters are you using? 1.21.0 has a bug in
> foomatic-rip which is fixed in 1.21.1. Please update to 1.21.1 if you
> have 1.21.0 currently.

I had none installed. I now try with 1.20.4-1 which is in testing, where
the bug was reported from and where cups fails with the ghostscript from
unstable. The autopkgtest ran successfully with cups-filters/1.21.0-1
and with cups-filters/1.21.1-1 so I assume they are both fine in this
respect.

On my laptop, lpinfo still fails.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#907709: cowbuilder should create directory when basepath is given

[shirish शिरीष]

Package: cowbuilder
Version: 0.87+b1
Severity: normal

Dear Maintainer,
I am a newbie to cowbuilder. A gentleman helped me to create the pbuilderrc -

~$ cat .pbuilderrc
BASEPATH="/var/cache/pbuilder/sid-amd64/base.cow"
DISTRIBUTION="sid"
MIRRORSITE="http://deb.debian.org/debian/;
# Enable build log
 PKGNAME_LOGFILE="yes"

which was then symlinked to root

sudo ln -s ~/.pbuilderrc /root/

now till here everything is/was good.

Then I tried -

$ sudo cowbuilder --create
I: Invoking pbuilder
I: forking: pbuilder create --buildplace
/var/cache/pbuilder/unstable-amd64/base.cow --mirror
http://deb.debian.org/debian/ --distribution unstable --no-targz
--extrapackages cowdancer
E: Directory /var/cache/pbuilder/unstable-amd64/base.cow does not exist
E: pbuilder create failed
I: forking: rm -rf /var/cache/pbuilder/unstable-amd64/base.cow

I then had to explicitly make the basepath as shared in

https://wiki.debian.org/cowbuilder

$ sudo mkdir /var/cache/pbuilder/sid-amd64 before I was able to make
the base chroot

/var/cache/pbuilder/sid-amd64$ ls
base.cow

I did see #820946 which shares somewhat the same concern, although in
my case when I have explicitly given the basepath.

Am I missing or mis-understanding something ?

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

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

Versions of packages cowbuilder depends on:
ii  cowdancer0.87+b1
ii  libc62.27-5
ii  libncurses6  6.1+20180714-1
ii  libtinfo66.1+20180714-1
ii  pbuilder 0.229.3

cowbuilder recommends no packages.

cowbuilder suggests no packages.

-- no debconf information

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

Bug#742624: Find it very annoying too

[Eric Valette]

file test_mime_type.vym
test_mime_type.vym: Zip archive data, at least v2.0 to extract

-- eric

Bug#907707: xfce4-sntray-plugin FTBFS with vala-panel 0.4.61

[Adrian Bunk]

Source: xfce4-sntray-plugin
Version: 0.4.10-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xfce4-sntray-plugin.html

...
/build/1st/xfce4-sntray-plugin-0.4.10/src/vala-panel-sntray-applet.vala:23.39-23.56:
 error: SNApplet: Classes cannot have multiple base classes 
(`ValaPanel.AppletPlugin' and `Peas.ExtensionBase')
public class SNApplet : AppletPlugin, Peas.ExtensionBase
  ^^
Compilation failed: 1 error(s), 0 warning(s)
make[3]: *** [src/CMakeFiles/sntray-valapanel.dir/build.make:74: 
src/sntray-valapanel_valac.stamp] Error 1

Bug#907706: devscripts: Incorrect output of dcontrol

[Dmitry Bogatov]

Package: devscripts
Version: 2.18.3
Severity: normal

Dear Maintainer,

I stumbled at following behaviour of `dcontrol' utility:

$ dcontrol debhelper/sid

Package: debhelper
Binary: debhelper, dh-systemd
Version: 11.3.5
Maintainer: Debhelper Maintainers 
Uploaders: Niels Thykier ,
Build-Depends: dpkg-dev (>= 1.18.0~), perl:any, po4a
Architecture: all
Standards-Version: 4.1.4
Format: 3.0 (native)
Files: d6d3877f0ae31653a5238ca1e8b53f7a 1689 debhelper_11.3.5.dsc
 82c28492f0b032e378c9819b1a40de80 467732 debhelper_11.3.5.tar.xz
Vcs-Browser: https://salsa.debian.org/debian/debhelper
Vcs-Git: https://salsa.debian.org/debian/debhelper.git
Checksums-Sha256: 
d1a142e4c29a3394f7472e8621e6966ebaf9f465e93571695622e5fc949470b0 1689 
debhelper_11.3.5.dsc
 34d7b4641757c1fbbb3497ff76fccd128409689cf8c7886a92d0c03621b69a95 
467732 debhelper_11.3.5.tar.xz
Package-List: debhelper deb devel optional arch=all
 dh-systemd deb oldlibs optional arch=all
Testsuite: autopkgtest-pkg-perl
Directory: pool/main/d/debhelper
Priority: source
Section: devel

Package: debhelper
Priority: optional
Section: devel
Installed-Size: 1520
Maintainer: Joey Hess 
Architecture: all
Version: 8.1.6
Depends: perl, perl-base (>= 5.10), file (>= 3.23), dpkg-dev (>= 
1.16.0), html2text, binutils, po-debconf, man-db (>= 2.5.1-1)
Suggests: dh-make
Conflicts: dpkg-cross (<< 1.18), python-central (<< 0.5.6), 
python-support (<< 0.5.3)
Filename: pool/main/d/debhelper/debhelper_8.1.6_all.deb
Size: 556788
MD5sum: 4dcf72d0c6c2dcf53e316bbb8a5308f3
SHA1: be6b2e1f7fec1e2e926d7f20b3b45c5380e66d5a
SHA256: f2a68b041f8c4a08c7b7d8becc4a3773a6c4e6b17d2cb5b7a0eafe33e8269b5b
Description: helper programs for debian/rules
 A collection of programs that can be used in a debian/rules file to
 automate common tasks related to building debian packages. Programs
 are included to install various files into your package, compress
 files, fix file permissions, integrate your package with the debian
 menu system, debconf, doc-base, etc. Most debian packages use debhelper
 as part of their build process.
Homepage: http://kitenet.net/~joey/code/debhelper/
Tag: devel::{buildtools,debian,packaging}, implemented-in::perl, 
interface::commandline, role::program, scope::utility, suite::debian, 
works-with::software:source

Package: debhelper
Version: 11.3.5
Installed-Size: 1554
Maintainer: Debhelper Maintainers 
Architecture: all
Replaces: dh-systemd (<< 1.38)
Provides: debhelper-compat (= 9), debhelper-compat (= 10), 
debhelper-compat (= 11)
Depends: autotools-dev, dh-autoreconf (>= 17~), dh-strip-nondeterminism 
(>= 0.028~), dpkg (>= 1.18.0~), dpkg-dev (>= 1.18.2~), dwz, file (>= 3.23), 
libdpkg-perl (>= 1.17.14), man-db, po-debconf, perl
Suggests: dh-make
Breaks: cmake (<< 3.9~), dh-systemd (<< 1.38), meson (<< 0.40.0~)
Description: helper programs for debian/rules
Multi-Arch: foreign
Description-md5: c3d35229c1ce392f77324206e097b92e
Tag: devel::buildtools, devel::debian, devel::packaging,
 implemented-in::perl, interface::commandline, role::program,
 scope::utility, suite::debian, works-with::software:source
Section: devel
Priority: optional
Filename: pool/main/d/debhelper/debhelper_11.3.5_all.deb
Size: 980868
MD5sum: cd67844714bef5d5544665422c8e61f5
SHA256: e663f5d2bc4901327bbab85d051fa2c5afc964b269400a8dc29a74f140b6f70a

Package: debhelper
Version: 9.20130921
Installed-Size: 991
Maintainer: Joey Hess 
Architecture: all
Depends: perl, file (>= 3.23), dpkg (>= 1.16.2), dpkg-dev (>= 1.16.2), 
binutils, po-debconf, man-db (>= 2.5.1-1)
Suggests: dh-make
Conflicts: automake (<< 1.11.2), dpkg-cross (<< 1.18), python-central 
(<< 0.5.6), python-support (<< 0.5.3)
Description: helper programs for debian/rules
Multi-Arch: foreign
Homepage: http://kitenet.net/~joey/code/debhelper/
Description-md5: 7f6c2c5e1519e9ecdd8a657cdb536c4c
Tag: devel::buildtools, devel::debian, devel::packaging,
 implemented-in::perl, interface::commandline, role::program,
 scope::utility, suite::debian, works-with::software:source
Section: devel
Priority: optional
Filename: pool/main/d/debhelper/debhelper_9.20130921_all.deb
Size: 687544
MD5sum: 374f5871a35dda879bbb8ec497c56559
SHA1: 34e699536da6bc2b15c6aeb4cba5c32752b3819c
SHA256: e26bb2b077f9946a54f88d2f45465ffb33265701911f6f4cf3683e34961540a3

Bug#907708: vala-panel-appmenu FTBFS with vala-panel 0.4.61

[Adrian Bunk]

Source: vala-panel-appmenu
Version: 0.6.94+repack1-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vala-panel-appmenu.html

...
/build/1st/vala-panel-appmenu-0.6.94+repack1/lib/valapanel-plugin-appmenu.vala:24.44-24.61:
 error: AppmenuApplet: Classes cannot have multiple base classes 
(`ValaPanel.AppletPlugin' and `Peas.ExtensionBase')
public class AppmenuApplet : AppletPlugin, Peas.ExtensionBase
   ^^
Compilation failed: 1 error(s), 0 warning(s)
make[4]: *** [lib/CMakeFiles/appmenu-valapanel.dir/build.make:74: 
lib/appmenu-valapanel_valac.stamp] Error 1

Bug#907705: ITP: mmm -- minimalistic media manager

[Felix C. Stegerman]

Package: wnpp
Severity: wishlist
Owner: "Felix C. Stegerman" 

* Package name: mmm
  Version : 0.4.1
  Upstream Author : Felix C. Stegerman 
* URL : https://github.com/obfusk/m
* License : GPLv3+
  Programming Lang: Python
  Description : minimalistic media manager

  m keeps track of which files you've played (or are still playing)
  and thus allows you to easily continue playing the next file (using
  vlc or mpv).

I'm the upstream author and I use it a lot myself (instead of kodi);
some of my friends do as well.  As a Debian user I wanted to be able
to install it as a Debian package, so I turned it into a native Debian
package.  It builds (reproducibly) using dpkg-buildpackage.

I'm hoping to eventually become a Debian Developer/Maintainer, but for
now I'd need a sponsor to get this into Debian.

Thanks.

- Felix

Bug#905377: Re%3A Bug#905377%3A kontact%3A Kontact opens introduction in konqueror on each start

[Dr Nicholas Bailey]

> El viernes, 3 de agosto de 2018 15:17:24 -03 Matt Stamp escribió:
> > Package: kontact
> > Version: 4:17.12.3-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > On upgrade kontact:amd64 4:17.08.3-1 to 4:17.12.3-1 I am now getting the
> > Konqueror introduction page on each start. I am unable to dismiss it as
> > the
> > 'Skip this introduciton' button throws an error 'Could not find any
> > application or handler for exec:/switch'. So I close the Konqueror window
> > only to have it open again.
> > 
> > My other machine does not have Konqueror installed and on each load I am
> > met
> > with 'File not found: data:text/html;charset=UTF-8,%3C%3Fxml
> > version%3D%221.0%22...'
> > 
> > Is there a way to disable the introduction outright in an rc file
> > somewhere?
> > It's a pain to have to close this each time.
> 
> Not that I know of, but we can try to update the kde pim stuff after the Qt
> transition. This will probably solve it.
> 
> Kinds regards, Lisandro.

This happened to me after a buster upgrade, which also broke a lot of things 
(system tray disappeared, couldn't be put back; couldn't search by typing app 
name in launch menu etc etc). I did a one-time upgrade to unstable which put 
most things right, but konqueror still appears every time kontact is launched 
with the errors give by Lisandro.

This isn't a show-stopper for me, but it is annoying.  As a work around I 
launch kmail, korganizer etc as required individually. Actually I'm starting 
to prefer that. But it's certainly bad for KDE advocacy.

Let's hope this bug fixes itself and filters through to testing. I don't mind 
installing some sid pacakges if anybody wants to know if it makes the bug go 
away.

Nick/.

Bug#907704: choose-mirror: default to deb.debian.org

[Julien Cristau]

Package: choose-mirror
Severity: wishlist
X-Debbugs-Cc: tfh...@debian.org

I think it's time for choose-mirror to stop asking by default.  AFAIK
deb.debian.org works well enough now that we don't need users to
manually select a mirror close to them.

PoC patch, completely untested:

diff --git a/choose-mirror.c b/choose-mirror.c
index 2662c5f..5463fa7 100644
--- a/choose-mirror.c
+++ b/choose-mirror.c
@@ -665,7 +665,7 @@ static int choose_mirror(void) {
debconf_subst(debconf, mir, "mirrors", list);
free(list);

-   debconf_input(debconf, "high", mir);
+   debconf_input(debconf, "medium", mir);
free(mir);
} else {
char *host = add_protocol("hostname");
diff --git a/debian/choose-mirror-bin.templates.http-in
b/debian/choose-mirror-bin.templates.http-in
index 785851e..2dc1f02 100644
--- a/debian/choose-mirror-bin.templates.http-in
+++ b/debian/choose-mirror-bin.templates.http-in
@@ -29,13 +29,14 @@ _Description: Debian archive mirror country:
 Template: mirror/http/mirror
 Type: select
 Choices: ${mirrors}
+Default: deb.debian.org
 # :sl1:
 _Description: Debian archive mirror:
  Please select a Debian archive mirror. You should use a mirror in
  your country or region if you do not know which mirror has the best
  Internet connection to you.
  .
- Usually, ftp..debian.org is a good choice.
+ Usually, deb.debian.org is a good choice.

 Template: mirror/http/hostname
 Type: string


Cheers,
Julien

Bug#907698: libdrm2: regression: breaks firefox WebGL

[Jörg-Volker Peetz]

Hi Julien,

thanks for taking care and the info which I obviously didn't know about :-(

Regards,
Jörg.

Bug#907703: ghostscript: Bug 699654(2): preserve LockSafetyParams in the nulldevice

[Salvatore Bonaccorso]

Source: ghostscript
Version: 9.22~dfsg-3
Severity: grave
Tags: patch security upstream
Control: found -1 9.20~dfsg-1

There is one more followup fix needed:

http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=79cccf641486
https://bugs.ghostscript.com/show_bug.cgi?id=699654

Decoupling this from #907332 as issues there adressed, should ease a
bit tracking for fixes.

Regards,
Salvatore

Bug#906012: libxcursor: CVE-2015-9262

[Julien Cristau]

Process questions are very much off-topic for this bug report, but...

On 08/30/2018 09:43 AM, Bjoern wrote:
> As I am clearly unfamiliar with your processes, I really would
> appreciate the clarification to better my understanding and perhaps
> quell my concerns:
> 
>  * How far away is the 9.6 point release (given that 9.5 was released
> just over 1.5 months ago)?
> 
The aim is to have point releases roughly every couple of months.  In
practice anywhere between 2 to 4 is common.

>  * Why could the issue not be dealt with by simply supplying the fix in
> the nearer term as a security update?  Would it not be better to err on
> the side of caution?
> 
Any change in stable comes with risk (e.g. of regressions), it comes
with a cost both to the security team and to all users who need to apply
the update.  So the security team and/or package maintainers make a
risk/cost vs benefit analysis for any given issue and decide whether to
leave it unfixed or fix it through in a point release or fix it through
security.debian.org.

Cheers,
Julien

Bug#907701: Unable to load GDM on hybrid system after switching to nvidia driver

[Anton Vorobyov]

Package: nvidia-driver
Version: 390.77-1

New laptop with hybrid video system.

Installed debian testing with Gnome desktop. GDM and gnome shell were 
functioning correctly until i installed nvidia-driver package (i do not know 
which driver system used at that point). Optimus packages are not installed.

After installing nvidia-driver package, GDM fails to launch. Console output it 
shown, then system attempts to launch display server, fails, a second later 
attempts to launch again. Sometimes it manages to load it. I do not know if 
it's connected to my activity (trying to switch ttys, for example, or maybe 
something else) or not. Chances to load successfully are very low per attempt 
nevertheless (<10%).

Info about system:

Kernel: Linux kreo 4.17.0-3-amd64 #1 SMP Debian 4.17.17-1 (2018-08-18) x86_64 
GNU/Linux

Graphics card lspci output:
00:02.0 Display controller: Intel Corporation Device 3e9b
01:00.0 VGA compatible controller: NVIDIA Corporation GP104M [GeForce GTX 1080] 
(rev a1)

Installed nvidia packages:
$ apt list --installed | grep nvidia
glx-alternative-nvidia/testing,unstable,now 0.8.7 amd64 [installed,automatic]
libegl-nvidia0/testing,unstable,now 390.77-1 amd64 [installed,automatic]
libegl1-nvidia/testing,unstable,now 390.77-1 amd64 [installed,automatic]
libgl1-nvidia-glx/testing,unstable,now 390.77-1 amd64 [installed,automatic]
libgles-nvidia1/testing,unstable,now 390.77-1 amd64 [installed,automatic]
libgles-nvidia2/testing,unstable,now 390.77-1 amd64 [installed,automatic]
libglx-nvidia0/testing,unstable,now 390.77-1 amd64 [installed,automatic]
libnvidia-cfg1/testing,unstable,now 390.77-1 amd64 [installed,automatic]
libnvidia-egl-wayland1/testing,unstable,now 390.77-1 amd64 [installed,automatic]
libnvidia-eglcore/testing,unstable,now 390.77-1 amd64 [installed,automatic]
libnvidia-glcore/testing,unstable,now 390.77-1 amd64 [installed,automatic]
libnvidia-ml1/testing,unstable,now 390.77-1 amd64 [installed,automatic]
nvidia-alternative/testing,unstable,now 390.77-1 amd64 [installed,automatic]
nvidia-driver/testing,unstable,now 390.77-1 amd64 [installed]
nvidia-driver-bin/testing,unstable,now 390.77-1 amd64 [installed,automatic]
nvidia-driver-libs-nonglvnd/testing,unstable,now 390.77-1 amd64 
[installed,automatic]
nvidia-egl-wayland-common/testing,unstable,now 390.77-1 amd64 
[installed,automatic]
nvidia-egl-wayland-icd/testing,unstable,now 390.77-1 amd64 [installed,automatic]
nvidia-installer-cleanup/testing,unstable,now 20151021+8 amd64 
[installed,automatic]
nvidia-kernel-common/testing,unstable,now 20151021+8 amd64 [installed,automatic]
nvidia-kernel-dkms/testing,unstable,now 390.77-1 amd64 [installed,automatic]
nvidia-kernel-support/testing,unstable,now 390.77-1 amd64 [installed,automatic]
nvidia-legacy-check/testing,unstable,now 390.77-1 amd64 [installed,automatic]
nvidia-modprobe/testing,unstable,now 390.25-1 amd64 [installed,automatic]
nvidia-nonglvnd-vulkan-common/testing,unstable,now 390.77-1 amd64 
[installed,automatic]
nvidia-nonglvnd-vulkan-icd/testing,unstable,now 390.77-1 amd64 
[installed,automatic]
nvidia-persistenced/testing,unstable,now 390.25-1 amd64 [installed,automatic]
nvidia-settings/testing,unstable,now 390.67-1 amd64 [installed,automatic]
nvidia-support/testing,unstable,now 20151021+8 amd64 [installed,automatic]
nvidia-vdpau-driver/testing,unstable,now 390.77-1 amd64 [installed,automatic]
xserver-xorg-video-nvidia/testing,unstable,now 390.77-1 amd64 
[installed,automatic]

Xorg log errors with some context:
...
[46.151] (II) Module nouveau: vendor="X.Org Foundation"
[46.151]compiled for 1.20.0, module version = 1.0.15
[46.151]Module class: X.Org Video Driver
[46.151]ABI class: X.Org Video Driver, version 24.0
[46.151] (II) LoadModule: "nv"
[46.151] (WW) Warning, couldn't open module nv
[46.151] (EE) Failed to load module "nv" (module does not exist, 0)
...
[46.870] (II) Module glamoregl: vendor="X.Org Foundation"
[46.870]compiled for 1.20.1, module version = 1.0.1
[46.870]ABI class: X.Org ANSI C Emulation, version 0.4
[46.875] (EE) modeset(G0): eglGetDisplay() failed
[46.875] (EE) modeset(G0): glamor initialization failed

Systemd journal errors (related or not, hard to judge for me):
Aug 31 15:03:17 kreo kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Aug 31 15:03:17 kreo kernel: iTCO_wdt iTCO_wdt: can't request region for 
resource [mem 0x00c5fffc-0x00c5]
Aug 31 15:03:17 kreo kernel: iTCO_wdt: probe of iTCO_wdt failed with error -16
...
Aug 31 15:03:17 kreo kernel: ath10k_pci :45:00.0: firmware: failed to load 
ath10k/pre-cal-pci-:45:00.0.bin (-2)
Aug 31 15:03:17 kreo kernel: firmware_class: See 
https://wiki.debian.org/Firmware for information about missing firmware
Aug 31 15:03:17 kreo kernel: ath10k_pci :45:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:45:00.0.bin failed with error -2
Aug 31 15:03:17 kreo kernel: ath10k_pci :45:00.0: firmware: failed to 

Bug#907702: iwd: drop libexecdir override once bumping to compat 12

[Andreas Henriksson]

Package: iwd
Version: 0.7-2
Severity: wishlist

Filing this as a reminder for the future, and as a followup on future
improvements beyond
https://salsa.debian.org/debian/iwd/commit/23998f71d84c82c71a48574321dba5e38b698ec3
" Properly escape libexecdir path configure argument "


I think it would make sense to move the 'iwd' binary to /usr/libexec
once (at the same time as) the iwd package moves to dh compat 12.
ie. drop the dh_auto_configure override from debian/rules when
debian/compat (and debhelper b-d version) is bumped to 12.


TL;DR debian policy 4.1.5 allows /usr/libexec (FHS 3.0) and dh compat 12
will use it by default.


Details:


feedback from jcristau:

https://www.debian.org/doc/debian-policy/upgrading-checklist.html#version-4-1-5
may have made it ok

http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html

... and the reason for the fhs change afaict is to allow longstanding redhat 
practice, more than anything else
i suppose we could add an fhs exception to make libexec verboten and go back to 
everything using /usr/lib/foo instead if we wanted


The libexec bit is explicitly mentioned in:
https://salsa.debian.org/dbnpolicy/policy/commit/5205d0a50465cf422f1040d9395d5ea83dbfde5f



Regarding 
https://salsa.debian.org/debian/iwd/commit/23998f71d84c82c71a48574321dba5e38b698ec3
 :
jcristau said: the triplet in libexecdir is typically wrong
mbiebl said: to be clear, I wasn't really suggesting you should use 
/usr/libexec, ..., tbh I haven't made up my mind yet if this is something I 
want to embrace or not
(mbiebl also previously suggested the triplet is not desired.)



mbiebl about relevant debhelper changes:

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

https://salsa.debian.org/debian/debhelper/commit/35734abe58c9a05317af8c905d9c4791c60f85bc


Regards,
Andreas Henriksson

Bug#907661: freecol: Does not start up with OpenJDK 10

[Markus Koschany]

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

On Thu, 30 Aug 2018 21:42:17 +0100 Johannes Kloos
 wrote:
> Package: freecol
> Version: 0.11.6+dfsg2-1
> Severity: important
> Tags: patch
> 
> Dear Maintainer,
> 
> The freecol package tries to start up the JVM for freecol with the
> JVM option -Xincgc. This option has been removed some time before
> OpenJDK 10, causing startup to fail.
> 
> Removing the option makes the game start on my machine.

Thanks for reporting! Fix is pending.

Cheers,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#907700: ITP: python-guizero -- tkinter wrapper to simplify GUI creation

[Nick Morrott]

Package: wnpp
Owner: Nick Morrott 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: python-guizero
  Version : 0.5.3
  Upstream Author : Laura Sach
* URL : https://github.com/lawsie/guizero
* License : BSD-3-clause
  Programming Lang: Python
  Description : tkinter wrapper to simplify GUI creation

The aim of guizero is to make the process of creating simple GUIs
quick, accessible and understandable for children:

- works with standard Python GUI library
- abstracts away details children find hard
- provides an accessible widget naming system
- is flexible enough to be used for projects up to A-Level standard
- provides comprehensive and accessible documentation with examples
- provides helpful error messages

guizero is a dependency of the mu-editor [1]

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

I plan to maintain this package in the Debian Python Modules Team.

Bug#892841: Opening a file with O_CREAT fails

[Alexander Volkov]

The fix is in the attached patch.
>From d4720c44fb2c8c2b891bd07fbf6d44a2333f8c56 Mon Sep 17 00:00:00 2001
From: Alexander Volkov 
Date: Wed, 29 Aug 2018 13:54:23 +0300
Subject: [PATCH] fix opening a file with O_CREAT and reading created files

FUSE calls fgetattr() for a created file which leads to calling
smbc_fstat() that fails. This is probably a bug in libsmbclient.
Besides smbc_read() fails for a file opened/created with smbc_create().

As a workaround don't register "create" function in FUSE, "open"
is sufficient.

https://bugs.debian.org/892841
---
 src/function.c | 14 --
 1 file changed, 14 deletions(-)

diff --git a/src/function.c b/src/function.c
index 3e88f42..5536209 100644
--- a/src/function.c
+++ b/src/function.c
@@ -90,19 +90,6 @@ static int function_open(const char *path, struct fuse_file_info *fi){
 return 0;
 }
 
-static int function_creat(const char *path, mode_t mode,
-			struct fuse_file_info *fi){
-samba_fd	fd;
-
-DPRINTF(5, "(%s, mode=%0x, flags=%o, fh=%llx)\n", path, mode,
-	fi->flags, (long long) fi->fh);
-if (smbitem_what_is(path) != SMBITEM_SMB_SHARE_ITEM) return -EINVAL;
-
-if ((fd = samba_creat(path, fi->flags)) == NULL) return -errno;
-function_store_fd(fi, fd);
-return 0;
-}
-
 static int function_read(const char *path, char *buf, size_t size, off_t offset,
 			struct fuse_file_info *fi){
 int		result;
@@ -589,7 +576,6 @@ static int function_statfs(const char *path, struct statvfs *stbuf){
 
 struct fuse_operations smb_oper = {
 .open	= function_open,
-.create	= function_creat,
 .read	= function_read,
 .write	= function_write,
 .release	= function_close,
-- 
2.17.0

Bug#907699: ITP: python-nudatus -- tool to remove comments from Python scripts

[Nick Morrott]

Package: wnpp
Owner: Nick Morrott 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: python-nudatus
  Version : 0.0.3
  Upstream Author : Zander Brown
* URL : https://github.com/ZanderBrown/nudatus
* License : Expat
  Programming Lang: Python
  Description : tool to remove comments from Python scripts

Nudatus is a tool to remove comments from Python scripts.

It was created to help squeeze longer programs onto the micro:bit
but it should be suitable for various environments with restricted
storage.

Nudatus was designed to be embedded within a greater tool
(e.g. uflash [1], mu-editor [2]) but also provides a CLI tool.

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

I plan to maintain this package in the Debian Python Modules Team.

Bug#907655: xserver-xorg-video-mga: X don't start with the latest package version

[Julien Cristau]

Control: tag -1 moreinfo

On 08/30/2018 09:10 PM, Davide Prina wrote:
> Package: xserver-xorg-video-mga
> Version: 1:1.6.5-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> upgrading the system to the latest version don't let X to start: screen
> black with a cursor not blinking at the upper left corner. Ctrl-Alt-Fx
> don't works. Magic keys work.
> 
> Restarting the system in recovery mode and accessing as root I was able
> to install previous version of xserver-xorg-video-mga and server-xorg-core:
> 
> # dpkg -i xserver-xorg-video-mga_1%3a1.6.5-1_i386.deb xserver-xorg-
> core_2%3a1.19.6-1_i386.deb
> 
> this fix the problem.
> 
> using the command
> $ grep --binary-files=text wdm /var/log/syslog
> 

[..]

> 
> Let me know if you need more info.
> 
Please provide the full Xorg logs from the working and not-working cases.

Cheers,
Julien

Bug#906189: linux-image-4.17.0-1-amd64: Laptop does not suspend in 4.17 - worked up to 4.16

[David Bremner]

Felix Hagemann  writes:

> Package: src:linux
> Version: 4.17.17-1
> Followup-For: Bug #906189
>
> Dear Maintainer,
>
> I do see exactly the same behaviour on a Thinkpad X1 Carbon (Gen. 2).
>

I had the same problem on my dell e7270, but it was fixed by a BIOS
upgrade. Something to try?

d

Bug#905722: gcovr: Missing runtime dependency - python-pkg-resources

[Julian Andres Klode]

Control: severity -1 serious

On Wed, Aug 08, 2018 at 03:40:44PM +, Bodo-Merle Sandor wrote:
> Package: gcovr
> Version: 4.1-1
> Severity: normal
> 
> Dear Maintainer,
> 
> Starting gcovr results in the following error:
> 
> # gcovr
> Traceback (most recent call last):
>   File "/usr/bin/gcovr", line 6, in 
> from pkg_resources import load_entry_point
> ImportError: No module named pkg_resources

This is a release critical bug, the package does not
specify the dependencies it needs as required by policy
section 3.5.

It's also breaking CI systems, such as
  https://salsa.debian.org/jak/apt/-/jobs/42393

It's also easy to fix.
-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#907698: libdrm2: regression: breaks firefox WebGL

[Julien Cristau]

Control: tag -1 upstream fixed-upstream patch
Control: severity -1 important

On 08/31/2018 04:46 PM, Jörg-Volker Peetz wrote:
> Package: libdrm2
> Version: 2.4.94-1
> Severity: normal
> 
> Dear Maintainer(s),
> 
> since update to version 2.4.93-1 the Hardware support in firefox is
> broken. Calling for example https://get.webgl.org/ shows the text
> 
> "While your browser seems to support WebGL, it is disabled or
> unavailable."
> 
> In the log file of xinit the following message appears:
> 
> libGL error: MESA-LOADER: failed to retrieve device information
> libGL error: Version 4 or later of flush extension not found
> libGL error: failed to load driver: i915
> libGL error: MESA-LOADER: failed to retrieve device information
> 
> I'm not sure if this is the package to blame, maybe it's libdrm-intel1
> or something else. Firefox is version 61.0.1-1, xorg-xserver is 2:1.20.1-1, 
> mesa
> is 18.1.7-1.
> 
Should be fixed in
https://gitlab.freedesktop.org/mesa/drm/commit/bcb9d976cd91c018aa4eef13563813288984601f
and separately in Firefox 62.

Cheers,
Julien

Bug#907686: npm2deb: chokes on parsing mocha when locale is C

[Pirate Praveen]

On 2018, ഓഗസ്റ്റ് 31 4:57:54 PM IST, Jonas Smedegaard  wrote:
>Package: npm2deb
>Version: 0.2.8-1
>Severity: normal
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA512
>
>Attempting to follow https://wiki.debian.org/Javascript/Nodejs/Tasks to
>resolve dependencies of node-server, in a limited environment (a
>cowbuilder chroot) with "C" a locale, caused the following failure:
>
>Traceback (most recent call last):
>  File "js_task_edit.py", line 230, in 
>main()
>  File "js_task_edit.py", line 213, in main
>build_deps = get_builddeps(module_name)
>  File "js_task_edit.py", line 161, in get_builddeps
>debian = get_debian(dep)
>  File "js_task_edit.py", line 80, in get_debian
>npm2deb_instance = _Npm2Deb(module_name)
>File "/usr/lib/python3/dist-packages/npm2deb/__init__.py", line 57, in
>__init__
>self.read_package_info()
>File "/usr/lib/python3/dist-packages/npm2deb/__init__.py", line 363, in
>read_package_info
>(self.name, self.version))
>  File "/usr/lib/python3.6/subprocess.py", line 517, in getstatusoutput
>data = check_output(cmd, shell=True, universal_newlines=True,
>stderr=STDOUT)
>  File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
>**kwargs).stdout
>  File "/usr/lib/python3.6/subprocess.py", line 405, in run
>stdout, stderr = process.communicate(input, timeout=timeout)
>  File "/usr/lib/python3.6/subprocess.py", line 830, in communicate
>stdout = self.stdout.read()
>  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
>return codecs.ascii_decode(input, self.errors)[0]
>UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
>26639: ordinal not in range(128)

See if setting LANG=C.UTF-8 fixes it. If not try LC_ALL=UTF-8.

Some node modules have metadata in Unicode and the locale should have UTF-8 
support.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#907697: fortunes-br: Inconsistent use of accents in fortunes-br

[Rafael Vargas]

Package: fortunes-br
Version: 20160820
Severity: minor

Dear Maintainer,

Throughout the entire fortune file, several phrases uses some accents
(mainly the tilde) but don't use the other accents needed to be
grammatically correct.

I could offer myself to correct the file, but I couldn't find the latest
sources in order to send a patch.

Thanks in advance for your time.

Rafael Vargas


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

Kernel: Linux 4.9.0-8-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 fortunes-br depends on:
ii  fortune-mod  1:1.99.1-7+b1

fortunes-br recommends no packages.

fortunes-br suggests no packages.

-- no debconf information

Bug#907698: libdrm2: regression: breaks firefox WebGL

[Jörg-Volker Peetz]

Package: libdrm2
Version: 2.4.94-1
Severity: normal

Dear Maintainer(s),

since update to version 2.4.93-1 the Hardware support in firefox is
broken. Calling for example https://get.webgl.org/ shows the text

"While your browser seems to support WebGL, it is disabled or
unavailable."

In the log file of xinit the following message appears:

libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information

I'm not sure if this is the package to blame, maybe it's libdrm-intel1
or something else. Firefox is version 61.0.1-1, xorg-xserver is 2:1.20.1-1, mesa
is 18.1.7-1.

The Hardware is Intel graphics. glxinfo shows among others

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4

Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2)  (0x5912)
Version: 18.1.7
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2

Any idea?

Regards,
Jörg.


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

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

Versions of packages libdrm2 depends on:
ii  libc6  2.27-5
ii  libdrm-common  2.4.94-1

libdrm2 recommends no packages.

libdrm2 suggests no packages.

ii  firefox61.0.1-1

-- no debconf information

Bug#907696: Plasma system tray icon and notification missing after recently upgrades of plasmashell

[M0xkLurk3r]

Package: kde-plasma-desktop
Version: 5:102
Severity: important

Dear maintainer:

my desktop loses ALL system tray icon and notifications after recently 
upgrades. seems the notification were *just* failed to show, i heard the bell 
ringing when new notification arrives.

and the desktop also had someelse strange behaves, i try to search
existed apps from Application Launcher but got nothing.

i tried to kill(1) plasmashell and re-run a new instance from a terminal and 
got thoses output, maybe helpful for figure out bugs.

-- log start

org.kde.plasmaquick: Applet preload policy set to 1
org.kde.plasma: Applet "org.kde.plasma.systemtray" could not be loaded.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:61:28:
 Unable to assign [undefined] to int
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:52:27:
 Unable to assign [undefined] to int
kf5.kpackage: No metadata file in the package, expected it at: 
"/home/anthony/Pictures/"
kf5.kpackage: No metadata file in the package, expected it at: 
"/home/anthony/Pictures/"
kf5.kpackage: No metadata file in the package, expected it at: 
"/home/anthony/Pictures/"
trying to show an empty dialog
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Trying to use rootObject before initialization is completed, whilst using 
setInitializationDelayed. Forcing completion
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
trying to show an empty dialog
Plasma Shell startup completed
org.kde.plasmaquick: New Applet  "Application Launcher" with a weight of 100
org.kde.plasmaquick: New Applet  "Digital Clock" with a weight of 51
trying to show an empty dialog
org.kde.plasmaquick: Delayed preload of  "Application Launcher" after 0 seconds
KAStatsFavoritesModel::setFavorites is ignored
KActivities: Database connection:  
"kactivities_db_resources_140701463875840_readonly" 
query_only:  QVariant(qlonglong, 1) 
journal_mode:QVariant(QString, "wal") 
wal_autocheckpoint:  QVariant(qlonglong, 100) 
synchronous: QVariant(qlonglong, 0)
Entry is not valid "kontact.desktop" 0x559b5dc4cba0
Entry is not valid "ktp-contactlist.desktop" 0x559b5dc4cba0
Entry is not valid "org.kde.discover.desktop" 0x559b5dc4cba0
Entry is not valid "kontact.desktop" 0x559b5dc4cba0
Entry is not valid "ktp-contactlist.desktop" 0x559b5dc4cba0
Entry is not valid "org.kde.discover.desktop" 0x559b5dc4cba0
Closing SQL connection:  "kactivities_db_resources_140701463875840_readonly"
trying to show an empty dialog
org.kde.plasmaquick: Applet "Application Launcher" loaded after 174 msec
org.kde.plasmaquick: Delayed preload of  "Digital Clock" after 1.883 seconds
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
org.kde.plasmaquick: Applet "Digital Clock" loaded after 101 msec

-- log ended


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

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

Versions of packages kde-plasma-desktop depends on:
ii  kde-baseapps  4:17.08.3+5.102
ii  plasma-desktop4:5.13.4-1
ii  plasma-workspace  4:5.13.4-1
ii  udisks2   2.7.6-3
ii  upower0.99.8-2

Versions of packages kde-plasma-desktop recommends:
ii  kwin-x11  4:5.13.4-1
ii  sddm  0.18.0-1
ii  xserver-xorg  1:7.7+19

Versions of packages kde-plasma-desktop suggests:
pn  kdeconnect  

-- no debconf information

Bug#907493: ghostscript breaks cups autopkgtest: test times out

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2018-08-31 15:43:28)
> Quoting Didier 'OdyX' Raboud (2018-08-31 15:36:09)
> > Le vendredi, 31 août 2018, 01.25:24 h CEST Jonas Smedegaard a écrit :
> > > Do the freshly released experimental Ghostscript release help anything?
> > 
> > It doesn't seem to, unfortunately. :-(
> > 
> > To reproduce the issue; just run this as root:
> > /usr/share/cups/test-drivers
> > 
> > Surprisingly; it will fail when testing the _second_ printer, always. 
> > Also, it doesn't seem to get fixed with the ghostscript from testing.
> > 
> > There's something fishy here, but I can't say with certainty that it's 
> > ghostscript's fault :-(
> 
> Uhm, if the ghostscript in _testing_ causes that test to fail, then this 
> bug should *not* block the ghostscript in unstable to enter testing!!!

Let me try again - I see that my previous message could easily be 
perceived as aggressive: Not intended at all. Sorry!

Thanks, Odyx, for checking against the various versions of Ghostscript.

Currently¹ I cannot (easily) setup a CUPS testing environment, so would 
appreciate if someone else can confirm if the version now in testing 
_also_ causes this same failure - and if so then please help ensure that 
this issue does not block the security fix now in unstable to enter 
testing.


 - Jonas

¹ I am at MMMfest, a week long festival near Paris.

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#907493: ghostscript breaks cups autopkgtest: test times out

[Till Kamppeter]

On 31/08/18 15:36, Didier 'OdyX' Raboud wrote:

Le vendredi, 31 août 2018, 01.25:24 h CEST Jonas Smedegaard a écrit :

Do the freshly released experimental Ghostscript release help anything?


It doesn't seem to, unfortunately. :-(

To reproduce the issue; just run this as root:
/usr/share/cups/test-drivers

Surprisingly; it will fail when testing the _second_ printer, always. Also, it
doesn't seem to get fixed with the ghostscript from testing.

There's something fishy here, but I can't say with certainty that it's
ghostscript's fault :-(


Which driver is this second printer using?

Which version of cups-filters are you using? 1.21.0 has a bug in 
foomatic-rip which is fixed in 1.21.1. Please update to 1.21.1 if you 
have 1.21.0 currently.


   Till

Bug#903010: golang-gopkg-inf.v0: No Breaks/Replaces/Conflics with golang-speter-go-exp-math-dec-inf-dev

[Sascha Steinbiss]

Hi Dmitry,

[...]
>> I guess it would then only need removing the obsolete b-dep from
>> golang-github-appc-spec-dev and an upload of the new golang-gopkg-inf.v0?
> 
> That's not enough unfortunately, as if somebody already have "golang-speter-
> go-exp-math-dec-inf-dev" installed they will experience error on attempt to 
> install "golang-gopkg-inf.v0". Therefore the latter must have Breaks/Replaces 
> anyway...

OK.
I have added Breaks and Replaces with regard to
golang-speter-go-exp-math-dec-inf-dev for golang-gopkg-inf.v0-dev in
version 0.9.0-3.

Cheers
Sascha




signature.asc
Description: OpenPGP digital signature

Bug#907493: ghostscript breaks cups autopkgtest: test times out

[Didier 'OdyX' Raboud]

Le vendredi, 31 août 2018, 01.25:24 h CEST Jonas Smedegaard a écrit :
> Do the freshly released experimental Ghostscript release help anything?

It doesn't seem to, unfortunately. :-(

To reproduce the issue; just run this as root:
/usr/share/cups/test-drivers

Surprisingly; it will fail when testing the _second_ printer, always. Also, it 
doesn't seem to get fixed with the ghostscript from testing.

There's something fishy here, but I can't say with certainty that it's 
ghostscript's fault :-(

(No more time to investigate this today, sorry)

-- 
OdyX

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

Bug#907493: ghostscript breaks cups autopkgtest: test times out

[Jonas Smedegaard]

Quoting Didier 'OdyX' Raboud (2018-08-31 15:36:09)
> Le vendredi, 31 août 2018, 01.25:24 h CEST Jonas Smedegaard a écrit :
> > Do the freshly released experimental Ghostscript release help anything?
> 
> It doesn't seem to, unfortunately. :-(
> 
> To reproduce the issue; just run this as root:
> /usr/share/cups/test-drivers
> 
> Surprisingly; it will fail when testing the _second_ printer, always. 
> Also, it doesn't seem to get fixed with the ghostscript from testing.
> 
> There's something fishy here, but I can't say with certainty that it's 
> ghostscript's fault :-(

Uhm, if the ghostscript in _testing_ causes that test to fail, then this 
bug should *not* block the ghostscript in unstable to enter testing!!!


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#906358: gimp-help: FTBFS in buster/sid (You must have automake 1.10 or newer installed)

[Juhani Numminen]

Control: forwarded 906358 https://bugzilla.gnome.org/show_bug.cgi?id=794819
Control: tags 906358 patch fixed-upstream

On Fri, 17 Aug 2018 11:19:44 + Santiago Vila  wrote:
> Package: src:gimp-help
> Version: 2.8.2-0.1
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:
> 
> [...]
> dh_autoreconf ./autogen.sh
> dh_autoreconf: Compatibility levels before 9 are deprecated (level 7 in use)
> Looking for latest automake version ... 
>   You must have automake 1.10 or newer installed to compile gimp-help-2.
>   Download the appropriate package for your distribution,
>   or get the source tarball at ftp://ftp.gnu.org/pub/gnu/automake/
> 
> Please install/upgrade the missing tools and call me again.
> 
> dh_autoreconf: ./autogen.sh returned exit code 1

The attached patch is the diff from
https://gitlab.gnome.org/GNOME/gimp-help/commit/6b6238801f86136f711b15c867b80fbcef8b7b01
with a DEP-3 header. It resolves the build failure for me.


Juhani
Description: autogen.sh - allow automake-1.16.
Origin: https://gitlab.gnome.org/GNOME/gimp-help/commit/6b6238801f86136f711b15c867b80fbcef8b7b01
Bug: https://bugzilla.gnome.org/794819
Bug-Debian: https://bugs.debian.org/906358
Last-Update: 2018-08-31

--- a/autogen.sh
+++ b/autogen.sh
@@ -21,7 +21,7 @@
 
 echo -n "Looking for latest automake version ... "
 required_automake_minor=10
-minor=15
+minor=16
 while [ $minor -ge $required_automake_minor ]; do
 ver=1.$minor
 if (automake-$ver --version) < /dev/null > /dev/null 2>&1; then

Bug#907695: ITP: python-metaextract -- collect metadata about a python module

[Thomas Bechtold]

Package: wnpp
Severity: wishlist
Owner: Thomas Bechtold 

* Package name: python-metaextract
  Version : 1.0.4
  Upstream Author : Thomas Bechtold 
* URL : https://pypi.org/project/metaextract/
* License : Apache-2.0
  Programming Lang: Python
  Description : collect metadata about a python module

metaextract is a tool to collect metadata about a python module. For example 
you may have a sdist tarball from the Python Package Index and you want to know 
it’s dependencies. metaextract can collect theses dependencies. The tool was 
first developed in py2pack but is now it’s own module to be useful for others, 
too.


The package is a dependency of py2pack which I also intent to package for 
Debian.

Bug#902716: (no subject)

[Brian Minton]

I just verified that this is still occurring for reportbugs.debian.org port
443 (certificate not valid for this hostname), and ports 587 and 25 using
STARTTLS (self-signed certificate).  I've reassigned the bug since it's not
really an issue with the reportbug package itself.

-- 
Brian Minton
brian at minton dot name https://brian.minton.name
Live long, and prosper longer!
OpenPGP fingerprint = 8213 71DD 4665 CF4F AE20  2206 0424 DC19 B678 A1A9


signature.asc
Description: PGP signature

Bug#907694: ITP: neutron-tempest-plugin -- OpenStack Integration Test Suite - Neutron plugin

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: neutron-tempest-plugin
  Version : 0.2.0
  Upstream Author : OpenStack Foundation 
* URL : https://github.com/openstack/neutron-tempest-plugin
* License : Apache-2.0
  Programming Lang: Python
  Description : OpenStack Integration Test Suite - Neutron plugin

 Tempest is a set of integration tests to be run against a live Openstack
 cluster in order to make sure that all components are working as expected.
 Tempest will start and stop virtual machine in order to check that your
 cloud is working as expected.
 .
 This package contains the OpenStack networking (aka: Neutron) plugin.

Note: this package is needed to run functional testing on upstream CI.

Bug#907693: RFP: exodus-standalone -- εxodus CLI client for local APK static analysis

[Pierre Rudloff]

Package: wnpp
Severity: wishlist

* Package name: exodus-standalone
* URL : https://github.com/Exodus-Privacy/exodus-standalone
* License : AGPL-3.0
  Programming Lang: Python
  Description : εxodus CLI client for local APK static analysis

exodus-standalone is a CLI tool to run static analysis on Android APKs in order
to find trackers.

Bug#896970: RFS: odp/1.19.0.0-1 [ITP]

[Dmitry Eremin-Solenikov]

Hello,

I've uploaded new 1.19.0.2-1 version to mentors.d.o.
I've added manpages, fixed copyright info, fixed alternatives
and enabled auto-tests. Could you please review it?

сб, 2 июн. 2018 г. в 7:08, Lumin :
>
> On Sat, Jun 02, 2018 at 03:24:07AM +, Lumin wrote:
> > Please fix the aforementioned problems. Hopefully we'll have the last
> > round of check next time. Thank you for working on this.
> >
> > [1] 
> > http://debomatic-amd64.debian.net/distribution#unstable/odp/1.19.0.1-1/buildlog
>
> Forgot to check the copyright ... The copyright looks incomplete. A
> simple search on the source tree would reveal many non-Linaro copyright
> holders:
>
>   grep -ri copyright | grep -vi linaro | grep -i copyright
>
> The package will be rejected by ftp-master if we don't fix the
> copyright.

Should be fixed now.

>
> When checking odp-dpdk, one more problem was found:
>
>   root@b69fed1c16e0 ~/odp-dpdk-1.19.0.0# update-alternatives --config 
> libodp-linux.so-x86_64-linux-gnu
>   There are 2 choices for the alternative libodp-linux.so-x86_64-linux-gnu 
> (providing /usr/lib/x86_64-linux-gnu/libodp-linux.so).
>
> SelectionPath   
> Priority   Status
>   
>   * 0/usr/lib/x86_64-linux-gnu/odp-generic/libodp-linux.so   40   
>  auto mode
> 1/usr/lib/x86_64-linux-gnu/odp-dpdk/libodp-linux.so  40   
>  manual mode
> 2/usr/lib/x86_64-linux-gnu/odp-generic/libodp-linux.so   40   
>  manual mode
>
>
>   * 0/usr/lib/x86_64-linux-gnu/odp-dpdk/libodp-linux.so.119  
> 60auto mode
> 1/usr/lib/x86_64-linux-gnu/odp-dpdk/libodp-linux.so.119  
> 60manual mode
> 2/usr/lib/x86_64-linux-gnu/odp-generic/libodp-linux.so.119   
> 40manual mode
>
> Taking BLAS as an example, the generic and slow libblas3 provides
> libblas.so.3 symlink with a priority of 10. Faster implementations
> provides the same symlink with higher priorities, e.g. 40 for openblas.
>
> Maybe you want to adjust the priority values in those postinst scripts?
> The exact value is up to you, as long as it helps to tell the difference
> among different implementations.

I'll fix odp-dpdk later.


-- 
With best wishes
Dmitry

Bug#905586: lxc: diff for NMU version 1:2.0.9-6.1

[Salvatore Bonaccorso]

Hi Antonio,

On Fri, Aug 31, 2018 at 08:14:57AM -0300, Antonio Terceiro wrote:
> On Thu, Aug 30, 2018 at 10:06:15PM +0200, Salvatore Bonaccorso wrote:
> > Control: tags 905586 + pending
> > 
> > 
> > Dear maintainer,
> > 
> > I've prepared an NMU for lxc (versioned as 1:2.0.9-6.1) and
> > uploaded it to DELAYED/5.
> 
> Thanks!
> 
> > Please feel free to tell me if I should delay it longer.
> 
> on the contrary: please feel free to make it an immediate upload. I will
> import your diff in the git repository

Thank you, I just have rescheduled it.

if you prefer to have the single commits they are attached to this
mail. I realize you probably would have prefered a proper merge
request, but I did not start working from the salsa repo but from a
gbp import-dsc git repo.

Regards,
Salvatore
>From d37ad7ef0f5d30b9dc94252726d338f1b44e746e Mon Sep 17 00:00:00 2001
From: Salvatore Bonaccorso 
Date: Wed, 29 Aug 2018 15:19:27 +0200
Subject: [PATCH 1/3] utils: add LXC_PROC_PID_FD_LEN

---
 debian/changelog  |  6 
 ...s-add-LXC_PROC_PID_FD_LEN_stable-2.0.patch | 35 +++
 debian/patches/series |  1 +
 3 files changed, 42 insertions(+)
 create mode 100644 debian/patches/0005-utils-add-LXC_PROC_PID_FD_LEN_stable-2.0.patch

diff --git a/debian/changelog b/debian/changelog
index e3a1393eabe6..ece65f3f2990 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+lxc (1:2.0.9-7) UNRELEASED; urgency=medium
+
+  * utils: add LXC_PROC_PID_FD_LEN
+
+ -- Salvatore Bonaccorso   Wed, 29 Aug 2018 15:19:41 +0200
+
 lxc (1:2.0.9-6) unstable; urgency=medium
 
   * 0004-debian-Use-iproute2-instead-of-iproute.patch: fix creation of
diff --git a/debian/patches/0005-utils-add-LXC_PROC_PID_FD_LEN_stable-2.0.patch b/debian/patches/0005-utils-add-LXC_PROC_PID_FD_LEN_stable-2.0.patch
new file mode 100644
index ..300264419c2e
--- /dev/null
+++ b/debian/patches/0005-utils-add-LXC_PROC_PID_FD_LEN_stable-2.0.patch
@@ -0,0 +1,35 @@
+From f96f5f3c1341e73ee51c8b49bef4ba571c562d8c Mon Sep 17 00:00:00 2001
+From: Christian Brauner 
+Date: Fri, 4 May 2018 11:59:11 +0200
+Subject: [PATCH] utils: add LXC_PROC_PID_FD_LEN
+
+Signed-off-by: Christian Brauner 
+---
+ src/lxc/utils.h | 11 +++
+ 1 file changed, 11 insertions(+)
+
+diff --git a/src/lxc/utils.h b/src/lxc/utils.h
+index a2bad89db..e4d8519db 100644
+--- a/src/lxc/utils.h
 b/src/lxc/utils.h
+@@ -99,6 +99,17 @@
+ #define LXC_NUMSTRLEN64 21
+ #define LXC_LINELEN 4096
+ #define LXC_IDMAPLEN 4096
++/* /proc/   =6
++ *+
++ *  =   LXC_NUMSTRLEN64
++ *+
++ * /fd/ =4
++ *+
++ *   =   LXC_NUMSTRLEN64
++ *+
++ * \0   =1
++ */
++#define LXC_PROC_PID_FD_LEN (6 + LXC_NUMSTRLEN64 + 4 + LXC_NUMSTRLEN64 + 1)
+ 
+ /* returns 1 on success, 0 if there were any failures */
+ extern int lxc_rmdir_onedev(char *path, const char *exclude);
+-- 
+2.17.1
+
diff --git a/debian/patches/series b/debian/patches/series
index 43c8fba2388b..5ebb5b167444 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@
 0002-lxc-debian-don-t-write-C.-locales-to-etc-locale.gen.patch
 0003-lxc-debian-don-t-hardcode-valid-releases.patch
 0004-debian-Use-iproute2-instead-of-iproute.patch
+0005-utils-add-LXC_PROC_PID_FD_LEN_stable-2.0.patch
-- 
2.18.0

>From 23be076be26591f506acc929586ce7fa37569400 Mon Sep 17 00:00:00 2001
From: Salvatore Bonaccorso 
Date: Wed, 29 Aug 2018 15:20:25 +0200
Subject: [PATCH 2/3] CVE 2018-6556: verify netns fd in lxc-user-nic

Closes: #905586
---
 debian/changelog  |   1 +
 ...-lxc-user-nic-verify-file-descriptor.patch | 101 ++
 debian/patches/series |   1 +
 3 files changed, 103 insertions(+)
 create mode 100644 debian/patches/0006-stable-2.0-lxc-user-nic-verify-file-descriptor.patch

diff --git a/debian/changelog b/debian/changelog
index ece65f3f2990..438982ff7e8d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 lxc (1:2.0.9-7) UNRELEASED; urgency=medium
 
   * utils: add LXC_PROC_PID_FD_LEN
+  * CVE 2018-6556: verify netns fd in lxc-user-nic (Closes: #905586)
 
  -- Salvatore Bonaccorso   Wed, 29 Aug 2018 15:19:41 +0200
 
diff --git a/debian/patches/0006-stable-2.0-lxc-user-nic-verify-file-descriptor.patch b/debian/patches/0006-stable-2.0-lxc-user-nic-verify-file-descriptor.patch
new file mode 100644
index ..c877483af596
--- /dev/null
+++ b/debian/patches/0006-stable-2.0-lxc-user-nic-verify-file-descriptor.patch
@@ -0,0 +1,101 @@
+From d183654ec1a2cd1149bdb92601ccb7246bddb14e Mon Sep 17 00:00:00 2001
+From: Christian Brauner 
+Date: Wed, 25 Jul 2018 19:56:54 +0200
+Subject: [PATCH] CVE 2018-6556: verify netns fd in lxc-user-nic
+
+Signed-off-by: Christian Brauner 
+---
+ src/lxc/lxc_user_nic.c | 35 ---
+ src/lxc/utils.c| 12 
+ src/lxc/utils.h  

Bug#907692: Feature request for CMST and/or Connman/Connman-VPN

[scrap]

Package: cmst
Version: 2016.10.03-2

Actually this is more a feature request, not a bug. Because of the fact
that CMST is also relevant for the Connman-developers I also put its
maintainers as recipients in here.

While browsing through the internet I found an interesting entry on
StackExchange where a user has reported the same issue with Connman-VPN
that I have experienced many times by myself.

The challenge is: When using Connman with a OpenConnect VPN-connection
some VPN servers request user authentication via cookie. This cookie has
to be generated before connecting to the VPN.

Hereby in most cases the cookie is only valid for a few hours, but not
for a longer period of time. Therefore the user has to renew his cookie
all few hours manually by hand. While Connman's "competitor"
NetworkManager can handle those regenerations of the cookie by himself,
in Connman it is necessary to do this by hand.

To do so, every time you want to connect to the VPN you have to execute
a little command in shell that will do the job for you. This script is
generating the cookie and writes the new cookie into the VPN
provisioning file /var/lib/connman-vpn/vpnname.config. Afterwards you
can connect to the VPN successfully.

-

My idea now is:

Would it be possible to add some option into CMST to run a small script
every time when clicking on "Connect"? Just an additional input field
where you can enter some custom code that has to be executed when
clicking on "Connect"? This code could execute the renewing process of
the cookie, either by launching a small external *.sh bash-script or by
immediate insertion of this code into the custom field.

Another idea on how to call this command:

Maybe it would be possible to insert this command into the VPN
provisioning file /var/lib/connman-vpn/vpnname.config directly and tell
CMST that it has to execute this command first before connecting to the
VPN. Just an additional variable line called "ExecuteCodeWhenConnecting
= blablabla" or similar.

You can have a look at the more detailed explanation of this issue here:

https://unix.stackexchange.com/questions/449174/connman-how-to-set-up-openconnect-vpn-with-csd-wrapper-correctly

A function like that would gain huge improvements in user comfort.

What do you think about it?

I am very happy to hear from you!

With best regards
Daniel