Bug#904266: gir1.2-gstreamer-1.0: Install the typelibs into a multi-arch directory

[Sebastian Dröge]

On Wed, 2018-08-08 at 12:37 +, Hugh McMaster wrote:
> Hi Sebastian,
> 
> On Monday, 30 July 2018 16:32:27 +1000, Sebastian Dröge wrote:
> > Are gobject-introspection and all the bindings actually looking in
> > that
> > directory too?
> 
> The typelibs for gobject-introspection are now installed in 
> /usr/lib//gobject-introspection/giscanner.

Thanks, I'll take a look at that together with the next upload unless
you'd like to provide a patch for this already.

Same thing for the other related bug, the proposed solution seems fine.


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

Bug#898935: Tomcat 8 security issues in Stretch

[Bogdan Veringioiu]

Thank you!

Bogdan


On 25.08.2018 00:05, Markus Koschany wrote:

A security update has been sent to Debian's security team and we expect
that the current open issues in Stretch will be fixed in due time.
Please note that Tomcat 7 in Stretch is not vulnerable to any of those
issues because we only build the servlet API.

Regards,

Markus

Bug#906447: tomcat8: Errors thrown when connecting

[Per Lundberg]

On 8/26/18 12:46 AM, Markus Koschany wrote:


I believe we should tighten the dependency on default-jre-headless. We
currently have for tomcat8-common:

default-jre-headless | java8-runtime-headless | java8-runtime

We should simply change that to

default-jre-headless (>= 10) | java10-runtime-headless | java10-runtime


Why can't we just compile it with OpenJDK 8? There are some of us who 
are still stuck on Java 8 for various reasons (because of dependencies 
of other projects), and I think it would be more convenient to let the 
package be compiled for Java 8 for the time being. As long as Tomcat 
doesn't actually use any Java 10 features, I don't really see the big 
benefit of compiling it with OpenJDK 10 at this stage.

--
Best regards,
Per

Bug#907354: apparmor-profiles-extra: unable to open help in Totem

[intrigeri]

Good catch!

FTR this got reported to Tails as well a couple days ago:
https://labs.riseup.net/code/issues/15841

I expect this will be fixed upstream by Tails folks soon
and then the fix will flow into Debian sid and eventually testing.

Bug#907373: debsecan: regards -dbgsym packages as obsolete

[Paul Wise]

Package: debsecan
Version: 0.4.19
Severity: normal

In the daily report, debsecan seems to regard -dbgsym packages as
obsolete. These packages are not obsolete, they are just from a suite and repo 
that is different from the rest of the installed packages.

For example, before installing pngcrush-dbgsym:

CVE-2015-7700 Double-free vulnerability in the sPLT chunk structure...
  
  - pngcrush (remotely exploitable, high urgency)

After installing pngcrush-dbgsym:

CVE-2015-7700 Double-free vulnerability in the sPLT chunk structure...
  
  - pngcrush (remotely exploitable, high urgency)
  - pngcrush-dbgsym (remotely exploitable, high urgency, obsolete)

$ apt policy pngcrush-dbgsym
pngcrush-dbgsym:
  Installed: 1.7.85-1+b2
  Candidate: 1.7.85-1+b2
  Version table:
 *** 1.7.85-1+b2 900
900 https://deb.debian.org/debian-debug testing-debug/main amd64 
Packages
800 https://deb.debian.org/debian-debug unstable-debug/main amd64 
Packages
100 /var/lib/dpkg/status
$ apt policy pngcrush
pngcrush:
  Installed: 1.7.85-1+b2
  Candidate: 1.7.85-1+b2
  Version table:
 *** 1.7.85-1+b2 900
900 https://deb.debian.org/debian testing/main amd64 Packages
800 https://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages debsecan depends on:
ii  ca-certificates20170717
ii  debconf [debconf-2.0]  1.5.69
ii  python 2.7.15-3
ii  python-apt 1.6.2

Versions of packages debsecan recommends:
ii  cron   3.0pl1-130
ii  exim4  4.91-6
ii  exim4-daemon-light [mail-transport-agent]  4.91-6

debsecan suggests no packages.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#907372: needrestart: complains about microcode updates on systems with microcode for multiple CPUs in initramfs

[Paul Wise]

Package: needrestart
Version: 3.3-1
Severity: normal
File: /usr/lib/needrestart/iucode-scan-versions

I have a system that changes between two different CPUs occasionally.
I have a system that boots a different computer at almost every boot.

To get the right microcode loaded, both turn off CPU scanning:

/etc/default/intel-microcode:
IUCODE_TOOL_SCANCPUS=no

The first one also restricts installed microcode to the used CPUs:

/etc/default/intel-microcode:
IUCODE_TOOL_EXTRA_OPTIONS="-s 0x000X,0xXX -s 0x000X,0xXX"

For both of these, the needrestart microcode checking complains
that the running microcode is at a different revision to the initrd
microcode. The revision that the first system prints is the revision
for the other CPU that is not currently booted. The revision that the
second system prints is a revision for the another random CPU.

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages needrestart depends on:
ii  binutils   2.31.1-4
ii  dpkg   1.19.0.5+b1
ii  gettext-base   0.19.8.1-7
ii  libintl-perl   1.26-2
ii  libmodule-find-perl0.13-1
ii  libmodule-scandeps-perl1.24-1
ii  libproc-processtable-perl  0.55-1
ii  libsort-naturally-perl 1.03-2
ii  libterm-readkey-perl   2.37-1+b2
ii  perl   5.26.2-7
ii  xz-utils   5.2.2-1.3

Versions of packages needrestart recommends:
ii  libpam-systemd  239-7

Versions of packages needrestart suggests:
ii  iucode-tool  2.3.1-1
ii  libnotify-bin0.7.7-3
ii  needrestart-session  0.3-5

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#907371: gnome-packagekit FTBFS with nocheck profile: xvfb-run: Command not found

[Helmut Grohne]

Source: gnome-packagekit
Version: 3.28.0-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

Hi,

It is super nice that you think of tagging Build-Depends with 
where appropriate. Unfortunately, it doesn't quite work that way yet. A
nocheck build fails finding xvfb-run. If you run "xvfb-run
dh_auto_test", dh_auto_test checks whether checks are disabeld in an
environment provided by xvfb-run. So to actually make xvfb optional, you
must check DEB_BUILD_OPTIONS yourself. Please consider applying the
attached patch.

Helmut
diff --minimal -Nru gnome-packagekit-3.28.0/debian/changelog 
gnome-packagekit-3.28.0/debian/changelog
--- gnome-packagekit-3.28.0/debian/changelog2018-03-17 23:23:02.0 
+0100
+++ gnome-packagekit-3.28.0/debian/changelog2018-08-27 06:06:46.0 
+0200
@@ -1,3 +1,10 @@
+gnome-packagekit (3.28.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Only run xvfb, when it is available. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 27 Aug 2018 06:06:46 +0200
+
 gnome-packagekit (3.28.0-2) unstable; urgency=medium
 
   * Update 01_prefer-software-properties.patch to also prefer update-manager
diff --minimal -Nru gnome-packagekit-3.28.0/debian/rules 
gnome-packagekit-3.28.0/debian/rules
--- gnome-packagekit-3.28.0/debian/rules2018-03-17 23:23:02.0 
+0100
+++ gnome-packagekit-3.28.0/debian/rules2018-08-27 06:06:44.0 
+0200
@@ -28,7 +28,9 @@
dh_missing --fail-missing
 
 override_dh_auto_test:
+ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),)
xvfb-run dh_auto_test
+endif
 
 override_dh_installdocs:
dh_installdocs

Bug#907026: cups-filters: filter failed on Ricoh MP 3554 SP after upgrading to 1.21.0-1

[Ben Caradoc-Davies]

Also affects Brother MFC-L2740DW with Generic PCL 6/PCL XL Printer 
Foomatic/pxlcolor from foomatic-db-compressed-ppds 20180604-1. Confirmed 
fixed by downgrading cups-browsed, cups-filters, 
cups-filters-core-drivers, libcupsfilters1, and libfontembed1 to 1.20.4-1.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#907263: dh-golang: Failed to build with gccgo-8

[Shengjing Zhu]

On Mon, Aug 27, 2018 at 10:03:57AM +1200, Michael Hudson-Doyle wrote:
> It's available in go list as well, e.g.
> 
> $ go list -f '{{if not .Standard}}{{ .ImportPath }}{{end}}'
> github.com/snapcore/snapd/snap bytes
> github.com/snapcore/snapd/snap
> $

That's much simpler, so the second patch is attached.

-- 
Shengjing Zhu
From 389d176cfef89a41b495b4af4578780b48d01972 Mon Sep 17 00:00:00 2001
From: Shengjing Zhu 
Date: Mon, 27 Aug 2018 11:55:01 +0800
Subject: [PATCH] Fix index out of range when using gccgo

Signed-off-by: Shengjing Zhu 
---
 script/dh_golang | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/script/dh_golang b/script/dh_golang
index 73ded48..4baef7f 100755
--- a/script/dh_golang
+++ b/script/dh_golang
@@ -78,6 +78,12 @@ my @godeps = exec_single(qq{go list -f '$tmpl'}, @targets);
 
 my $gofiletmpl = '\
 {{ .Dir }}/{{ index (or .GoFiles .CgoFiles .TestGoFiles .XTestGoFiles .IgnoredGoFiles) 0 }}';
+
+# gccgo can't find standard libraries files #907263
+if (grep /gccgo/, exec_single(q{go version})) {
+$gofiletmpl = '{{if not .Standard}}' . $gofiletmpl . '{{end}}';
+}
+
 my @gofiles = exec_chunked(qq{go list -f '$gofiletmpl'}, uniq(@godeps));
 
 my @realpath;
-- 
2.18.0



signature.asc
Description: PGP signature

Bug#907370: TypeError: object of type 'int' has no len()

[Antoine Beaupre]

Package: python3-sh
Version: 1.11-1
Severity: grave

I found a regression in the python3-sh package. I have yet to find
exactly what is going on, but it looks to me like something changed in
Python 3.6 that broke the sh module in some way:

$ lwn get -o blog/2017-12-13-kubecon-overview.mdwn 
https://lwn.net/Articles/741301/
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
  File "/usr/lib/python3.6/threading.py", line 864, in run
self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3/dist-packages/sh.py", line 1453, in input_thread
done = stdin.write()
  File "/usr/lib/python3/dist-packages/sh.py", line 1799, in write
self.log.debug("got chunk size %d: %r", len(proc_chunk),
TypeError: object of type 'int' has no len()

The source for the `lwn` command is here:

https://gitlab.com/anarcat/lwn/blob/master/lwn.py

It's totally unclear to me, from the backtrace, from *where* exactly
sh is being called, so I am having a hard time writing a
reproducer... But I am *guessing* it's this call:

result = sh.pandoc(filter_args, _in=content)

But really, I have no frigging clue.

Any brilliant idea of what could possibly be going on here? This used
to work fine in Debian stretch (which has the same version of
python3-sh, so probably no change there).

My best guess so far is something changed in some standard library,
but I really have no idea...

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

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

Versions of packages python3-sh depends on:
ii  python3  3.6.5-3

python3-sh recommends no packages.

python3-sh suggests no packages.

-- debconf-show failed

Bug#906731: gimp: liblcms2-2 dependancy should be >= 2.9 not 2.2x.

[Omari Stephens]

I just upgraded to gimp 2.10.6 and saw this as well.

--xsdg

Bug#906302:

[Michael Ott]

Hi Jeremy!

I have this problem also with version 3.29.91-1 of gnome-online-
accounts

CU
  Michael

Bug#807866: uploading github-hub? (was: Bug#807866: RFP: github-hub -- hub helps you win at git)

[Antoine Beaupré]

Control: tag -1 +pending +patch

Hi Anthony!

I noticed on Salsa that you have worked on the Debian package for the
hub program:

https://salsa.debian.org/go-team/packages/hub

Are there any plans to upload that package into the archive? It would be
very useful... It seems to work here although it currently FTBFS because
of an incorrect dependency. The attached patch fixes that.

Thanks for any update,

A.

>From 3d72160700b43218557ad15f12633a2eb9568119 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= 
Date: Sun, 26 Aug 2018 23:06:42 -0400
Subject: [PATCH] fix build dependency

The ruby-ronn package does not ship the ronn program anymore
---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 7d80a46..0103fac 100644
--- a/debian/control
+++ b/debian/control
@@ -20,7 +20,7 @@ Build-Depends: debhelper (>= 11),
golang-github-ogier-pflag-dev,
golang-golang-x-crypto-dev,
golang-gopkg-yaml.v2-dev,
-   ruby-ronn
+   ronn
 Standards-Version: 4.1.4
 Vcs-Browser: https://salsa.debian.org/go-team/packages/hub
 Vcs-Git: https://salsa.debian.org/go-team/packages/hub.git
-- 
2.18.0

Bug#905289: unattended-upgrade: Manual page missing some options.

[Paul Wise]

Package: unattended-upgrades
Version: 1.5
Followup-For: Bug #905289
Control: usertags -1 + bittenby

In addition the --verbose option is missing from the manual page.

I would suggest using sphinxcontrib-autoprogram or sphinx-argparse in
order to automatically generate the manual page options documentation
from the code for parsing the options.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#881406: apt-file: drop Contents header removal?

[Paul Wise]

On Sat, 11 Nov 2017 19:00:39 +0800 Paul Wise wrote:

> I noticed that reprepro (#881405) still has a header.

This has now been fixed.

> Unfortunately the reprepro header is not compatible with the current
> workaround in apt-file. We could fix that by replacing the first
> match with line 1. Alternatively we could just drop the workaround,
> removing it should speed up apt-file by not invoking sed. I guess
> most apt-file users aren't using reprepro generated repositories that
> also have Contents files available. Also, the header from reprepro
> doesn't cause quite as bad issues as the dak and launchpad header, it
> just means that there is a package called FILE with a single file in
> it called LOCATION.

Given all this (especially the speed-up) I think the workaround should
now be removed from apt-file.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#904407: Please modify the debian/copyright to follow DEP-5

[Yanhao Mo]

Hi, it is been one month since I submitted this merge request,
Do you have any plan on it, please let me know. And if still
cannot get any replying one week after. I will make a nmu.

Look forward to your replying.

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#907057: neverball: Constant fsync calls seriously degrade performance

[Uoti Urpala]

On Sun, 2018-08-26 at 17:59 +0200, Markus Koschany wrote:
> On Thu, 23 Aug 2018 17:56:01 +0300 Uoti Urpala 
> wrote:
> > Neverball automatically saves a replay of the latest run on disk while
> > playing. In the Debian package, the binary constantly calls fsync() on
> > this file, which very seriously degrades performance. If the issue is
> > not obvious when trying to reproduce, try on a machine with as slow a
> > spinning disk as possible.
> > 
> > This is likely a libphysfs issue. Neverball code contains no direct
> > fsync() calls. Neverball upstream has changed the default filesystem
> > backend to be stdio instead of libphysfs, and current upstream code
> > (with no physfs) does not display the problem.

> Why did you report this bug against neverball instead of libphysfs when
> all the issues you describe are related to libphysfs?

Neverball is broken so at least a bug blocked by a physfs bug would be
appropriate in any case, and I assume that the easiest way to fix the
problem would be to change the Neverball package to stop using
libphysfs.

Bug#907369: g++-mingw-w64-i686: Including filesystem header results in compilation errors

[Vadim Zeitlin]

Package: g++-mingw-w64-i686
Version: 8.2.0-1+21~exp2
Severity: normal

Including filesystem header results in compilation errors, e.g.:

% echo '#include ' | i686-w64-mingw32-g++ -std=c++17 -x c++ -
In file included from 
/usr/lib/gcc/i686-w64-mingw32/8.2-win32/include/c++/filesystem:37,
 from fs.cpp:6:
/usr/lib/gcc/i686-w64-mingw32/8.2-win32/include/c++/bits/fs_path.h: In member 
function ‘std::filesystem::__cxx11::path& 
std::filesystem::__cxx11::path::operator/=(const 
std::filesystem::__cxx11::path&)’:
/usr/lib/gcc/i686-w64-mingw32/8.2-win32/include/c++/bits/fs_path.h:237:47: 
error: no match for ‘operator!=’ (operand types are 
‘std::filesystem::__cxx11::path’ and ‘std::filesystem::__cxx11::path’)
|| (__p.has_root_name() && __p.root_name() != root_name()))
   ^~
...

This is due to the fact that Windows-specific code in this header uses
operator==(path, path) which is only defined later, so the error makes
sense.

I'm not sure where exactly does this code come from as it differs from the
upstream code (in gcc repository), but I can't find the Debian patch with
it neither. FWIW it looks like using the upstream version would fix this
problem.


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

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages g++-mingw-w64-i686 depends on:
ii  gcc-mingw-w64-base  8.2.0-1+21~exp2
ii  gcc-mingw-w64-i686  8.2.0-1+21~exp2
ii  libc6   2.27-5
ii  libgcc1 1:8.2.0-4
ii  libgmp102:6.1.2+dfsg-3
ii  libisl190.20-2
ii  libmpc3 1.1.0-1
ii  libmpfr64.0.1-1
ii  libstdc++6  8.2.0-4
ii  zlib1g  1:1.2.11.dfsg-1

g++-mingw-w64-i686 recommends no packages.

Versions of packages g++-mingw-w64-i686 suggests:
pn  gcc-8-locales  

-- no debconf information


pgp4yPuHK3UdM.pgp
Description: PGP signature

Bug#891960: nvidia-driver 390.25

[Peter Becich]

Hi Andreas,

Sorry for my late response.

It is still an issue with driver 390.77 from Backports.  Kernel is 
4.17.0-0.bpo.1-amd64.  I have a fresh installation since our last 
discussion.


Thanks,

  Peter

On Mon, 9 Jul 2018 12:25:56 +0200 Andreas Beckmann  wrote:

> Control: tag -1 moreinfo
>
> On 2018-03-03 21:28, Peter Becich wrote:
> > Thanks.  My mistake.  I have now read the nvidia-driver README and have
> > moved my report to this thread on the Nvidia Linux forum:
> > 
https://devtalk.nvidia.com/default/topic/1029683/suspend-swap-group-failed-resume-swap-group-failed-nvidia-390-25/

>
> Is this still an issue with the latest driver (390.67) available in sid,
> buster, and stretch-backports?
>
> The forum thread is a bit unconclusive.
>
>
> Andreas
>
>

Bug#907218: yapf: autopkgtest regression

[Ana C. Custura]

Hi Paul,
Thank you for this, will do an upload soon.

Regards,
Ana
On Fri, Aug 24, 2018, at 8:56 PM, Paul Gevers wrote:
> Source: yapf
> Version: 0.22.0-3
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Dear maintainers,
> 
> With the upload of 0.22.0-3 the autopkgtest of your package started to
> fail in testing. I copied the output below.
> 
> Currently this regression is contributing to the delay of the migration
> to testing [1]. Could you please investigate the situation and fix it?
> It seems that the first test is just missing a test dependency on
> python-nose.
> 
> 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=yapf
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/y/yapf/874882/log.gz
> 
> autopkgtest [04:39:09]: test command1: set -e ; cp -r yapftests
> "$AUTOPKGTEST_TMP" ; for py in $(pyversions -r 2>/dev/null) ; do cd
> "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -m nose --exclude
> "yapftests.pytree_unwrapper_test.MatchBracketsTest" ; done
> autopkgtest [04:39:09]: test command1: [---
> Testing with python2.7:
> /usr/bin/python2.7: No module named nose
> autopkgtest [04:39:10]: test command1: ---]
> 
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

Bug#907368: thunderbolt-tools: Please publish Debian packaging git

[Ross Vandegrift]

Package: thunderbolt-tools
Version: 0.9.3-3
Severity: normal

thunderbolt-tools has a gbp.conf, but I can't find the proper git repo on the
internet.  d/control doesn't have Vcs-Git.  Homepage points to upstream's git,
but that doesn't have the debian branch.

Thanks,
Ross

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

Kernel: Linux 4.18.0-rc4-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 thunderbolt-tools depends on:
ii  libboost-filesystem1.62.0  1.62.0+dfsg-8
ii  libboost-system1.62.0  1.62.0+dfsg-8
ii  libc6  2.27-5
ii  libgcc11:8.2.0-3
ii  libstdc++6 8.2.0-3

thunderbolt-tools recommends no packages.

thunderbolt-tools suggests no packages.

-- no debconf information

Bug#907367: thunderbolt-tools: Add thunderbolt support to initramfs

[Ross Vandegrift]

Package: thunderbolt-tools
Version: 0.9.3-3
Severity: wishlist
Tags: patch

Hello,

This patch adds thunderbolt support to initramfs.  It is enabled by installing
a new package: thunderbolt-tools-initramfs.  This allows me to enter my
cryptsetup password with a keyboard plugged into a tb3 dock.

Thanks,
Ross

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

Kernel: Linux 4.18.0-rc4-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 thunderbolt-tools depends on:
ii  libboost-filesystem1.62.0  1.62.0+dfsg-8
ii  libboost-system1.62.0  1.62.0+dfsg-8
ii  libc6  2.27-5
ii  libgcc11:8.2.0-3
ii  libstdc++6 8.2.0-3

thunderbolt-tools recommends no packages.

thunderbolt-tools suggests no packages.

-- no debconf information
>From 57fc7029b73ee1eef8a4c0dc87732da1f0f08657 Mon Sep 17 00:00:00 2001
From: Ross Vandegrift 
Date: Sun, 26 Aug 2018 18:01:06 -0700
Subject: [PATCH] Add support for activating thunderbolt in initramfs

---
 debian/README.Debian  | 13 
 debian/changelog  |  7 
 debian/control| 11 +++
 debian/copyright  |  6 
 debian/initramfs/hooks/thunderbolt-tools  | 33 +++
 debian/thunderbolt-tools-initramfs.install|  2 ++
 debian/{install => thunderbolt-tools.install} |  0
 7 files changed, 72 insertions(+)
 create mode 100644 debian/README.Debian
 create mode 100755 debian/initramfs/hooks/thunderbolt-tools
 create mode 100644 debian/thunderbolt-tools-initramfs.install
 rename debian/{install => thunderbolt-tools.install} (100%)

diff --git a/debian/README.Debian b/debian/README.Debian
new file mode 100644
index 000..4d8d9ab
--- /dev/null
+++ b/debian/README.Debian
@@ -0,0 +1,13 @@
+thunderbolt-tools initramfs support
+---
+
+thunderbolt-tools-initramfs provides scripts to built thunderbolt
+support into an initramfs.  Support is enabled by default.  It can be
+disabled /etc/initramfs/conf.d/thunderbolt-tools with THUNDERBOLT=n.
+
+This supports secure-mode thunderbolt and ACLs by using the tbtacl
+data.  All devices you wish to use at boot must have been authorized
+already: new devices can't be authorized in the initramfs.  Re-run
+update-initramfs after changing authorized devices.
+
+ -- Ross Vandegrift , Sun, 26 Aug 2018 17:59:55 -0700
diff --git a/debian/changelog b/debian/changelog
index b7174bf..5970a3f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+thunderbolt-tools (0.9.3-4) unstable; urgency=medium
+
+  * thunderbolt-tools-initramfs: Add support for udev thunderbolt
+activation in initramfs.  See README.Debian for details.
+
+ -- Ross Vandegrift   Sun, 26 Aug 2018 17:58:27 -0700
+
 thunderbolt-tools (0.9.3-3) unstable; urgency=medium
 
   * Remove redundant copy of udev rules (LP: #1762187)
diff --git a/debian/control b/debian/control
index b3ad7ca..9161d78 100644
--- a/debian/control
+++ b/debian/control
@@ -20,3 +20,14 @@ Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Intel Thunderbolt userspace components
  Provides components for using Intel Thunderbolt controllers with
  security level features
+
+Package: thunderbolt-tools-initramfs
+Architecture: all
+Depends: ${misc:Depends},
+initramfs-tools (>= 0.129) | linux-initramfs-tool,
+thunderbolt-tools
+Description: Intel Thunderbolt userspace components - initramfs integration
+ Provides components for using Intel Thunderbolt controllers with
+ security level features
+ .
+ This package provides initramfs integration for thunderbolt-tools.
diff --git a/debian/copyright b/debian/copyright
index 6224da8..8353d0d 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -29,8 +29,14 @@ License: BSD-3-clause
  OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
  OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
+Files: debian/initramfs/*
+Copyright: 2018 Ross Vandegrift 
+License: GPL-2+
+
 Files: debian/*
 Copyright: 2016 Mario Limonciello 
+License: GPL-2+
+
 License: GPL-2+
  This package is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
diff --git a/debian/initramfs/hooks/thunderbolt-tools 
b/debian/initramfs/hooks/thunderbolt-tools
new file mode 100755
index 000..02354e8
--- /dev/null
+++ b/debian/initramfs/hooks/thunderbolt-tools
@@ -0,0 +1,33 @@
+#!/bin/sh
+
+PREREQ=""
+
+prereqs()
+{
+echo "$PREREQ"
+}
+
+case "$1" in
+prereqs)
+   prereqs
+   exit 0
+  

Bug#907366: O: krb5-sync -- MIT Kerberos Active Directory synchronization plugin

[Russ Allbery]

Package: wnpp
Severity: normal

I intend to orphan the krb5-sync package.  I no longer use the package and
it doesn't seem likely that I will again soon, so I'm no longer a good
maintainer for it.

The package builds two binary packages.  krb5-sync-plugin's description:
 This plugin synchronizes passwords changed via kadmin or kpasswd to a
 foreign realm via the Kerberos password change protocol (normally, but
 not necessarily, an Active Directory realm).  It can also propagate
 changes to the DISALLOW_ALL_TIX flag to Windows Active Directory using
 LDAP.

 This package provides a plugin for the MIT Kerberos KDC and will not work
 with Heimdal.

krb5-sync-tools's description:
 Provides tools to enable, disable, and set the password of an account in
 a Windows Active Directory using the same configuration used by the
 krb5-sync-plugin package.  These supporting tools are normally used to
 handle queued changes created by the plugin that failed due to a
 temporary error, but can be used on their own.

Note that the package is also orphaned upstream (I was also the upstream
maintainer).  It is a limited and specialized piece of software and may
require local changes to be useful, but it does seem to get some use and I
was originally asked to package it for Debian instead of just for Stanford.

Bug#825970: pypy: Please package pypy3 as well now

[Stefano Rivera]

Hi Jeroen (2018.07.26_12:46:39_+0100)
> > Python2 is dying. Is there any reason so that pypy3 shouldn't be
> > compiled and uploaded? If you lack time and need help, please just ask.

It's mostly been time, yes.

> I'd also like to see pypy3 packaged. Is there already any work done on
> packaging pypy3? If not then we should probably start with creating a
> pypy3 source package based on the pypy2 packaging.

I've had something mostly ready to go for a year or so :/

https://salsa.debian.org/debian/pypy3

amd64 builds: https://people.debian.org/~stefanor/pypy3/
(which I'll update with 6.0.0, shortly)

The remaining issue that I know of, is figuring out a plan for
byte-compilation. I'll bring it up on the debian-python list...

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#762346: RFP: pypy3 -- fast alternative implementation of Python3 - PyPy interpreter

[Stefano Rivera]

Control: retitle -1 ITP: pypy3 -- fast alternative implementation of Python3 - 
PyPy interpreter
Control: owner -1 stefa...@debian.org

Yeah, I've had it mostly-packaged for a couple of years, just a couple
more kinks to sort out...

https://salsa.debian.org/debian/pypy3

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#907365: should depend on libibverbs-dev

[Dmitry Eremin-Solenikov]

Package: libdpdk-dev
Version: 17.11.3-3
Severity: normal

libdpdk-dev should depend on libibverbs-dev, otherwise linking in
mlx4/ml5 pmd drivers statically will fail with linker being unable to
find -lmlx4/-lmlx5 -libverbs.

-- 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-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libdpdk-dev depends on:
ii  libpcap-dev   1.8.1-6
ii  librte-acl17.11   17.11.3-3
ii  librte-bitratestats17.11  17.11.3-3
ii  librte-bus-pci17.11   17.11.3-3
ii  librte-bus-vdev17.11  17.11.3-3
ii  librte-cfgfile17.11   17.11.3-3
ii  librte-cmdline17.11   17.11.3-3
ii  librte-cryptodev17.11 17.11.3-3
ii  librte-distributor17.11   17.11.3-3
ii  librte-eal17.11   17.11.3-3
ii  librte-efd17.11   17.11.3-3
ii  librte-ethdev17.1117.11.3-3
ii  librte-eventdev17.11  17.11.3-3
ii  librte-flow-classify17.11 17.11.3-3
ii  librte-gro17.11   17.11.3-3
ii  librte-gso17.11   17.11.3-3
ii  librte-hash17.11  17.11.3-3
ii  librte-ip-frag17.11   17.11.3-3
ii  librte-jobstats17.11  17.11.3-3
ii  librte-kni17.11   17.11.3-3
ii  librte-kvargs17.1117.11.3-3
ii  librte-latencystats17.11  17.11.3-3
ii  librte-lpm17.11   17.11.3-3
ii  librte-mbuf17.11  17.11.3-3
ii  librte-member17.1117.11.3-3
ii  librte-mempool-octeontx17.11  17.11.3-3
ii  librte-mempool-ring17.11  17.11.3-3
ii  librte-mempool-stack17.11 17.11.3-3
ii  librte-mempool17.11   17.11.3-3
ii  librte-meter17.11 17.11.3-3
ii  librte-metrics17.11   17.11.3-3
ii  librte-net17.11   17.11.3-3
ii  librte-pci17.11   17.11.3-3
ii  librte-pdump17.11 17.11.3-3
ii  librte-pipeline17.11  17.11.3-3
ii  librte-pmd-af-packet17.11 17.11.3-3
ii  librte-pmd-ark17.11   17.11.3-3
ii  librte-pmd-avp17.11   17.11.3-3
ii  librte-pmd-bnxt17.11  17.11.3-3
ii  librte-pmd-bond17.11  17.11.3-3
ii  librte-pmd-crypto-scheduler17.11  17.11.3-3
ii  librte-pmd-cxgbe17.11 17.11.3-3
ii  librte-pmd-e1000-17.1117.11.3-3
ii  librte-pmd-ena17.11   17.11.3-3
ii  librte-pmd-enic17.11  17.11.3-3
ii  librte-pmd-failsafe17.11  17.11.3-3
ii  librte-pmd-fm10k17.11 17.11.3-3
ii  librte-pmd-i40e17.11  17.11.3-3
ii  librte-pmd-ixgbe17.11 17.11.3-3
ii  librte-pmd-kni17.11   17.11.3-3
ii  librte-pmd-lio17.11   17.11.3-3
ii  librte-pmd-mlx4-17.11 17.11.3-3
ii  librte-pmd-mlx5-17.11 17.11.3-3
ii  librte-pmd-nfp17.11   17.11.3-3
ii  librte-pmd-null-crypto17.11   17.11.3-3
ii  librte-pmd-null17.11  17.11.3-3
ii  librte-pmd-octeontx-ssovf17.1117.11.3-3
ii  librte-pmd-octeontx17.11  17.11.3-3
ii  librte-pmd-pcap17.11  17.11.3-3
ii  librte-pmd-qede17.11  17.11.3-3
ii  librte-pmd-ring17.11  17.11.3-3
ii  librte-pmd-sfc-efx17.11   17.11.3-3
ii  librte-pmd-skeleton-event17.1117.11.3-3
ii  librte-pmd-softnic17.11   17.11.3-3
ii  librte-pmd-sw-event17.11  17.11.3-3
ii  librte-pmd-tap17.11   17.11.3-3
ii  librte-pmd-thunderx-nicvf17.1117.11.3-3
ii  librte-pmd-vhost17.11 17.11.3-3
ii  librte-pmd-virtio17.1117.11.3-3
ii  librte-pmd-vmxnet3-uio17.11   17.11.3-3
ii  librte-port17.11  17.11.3-3
ii  librte-power17.11 17.11.3-3
ii  librte-reorder17.11   17.11.3-3
ii  librte-ring17.11  17.11.3-3
ii  librte-sched17.11 17.11.3-3
ii  librte-security17.11  17.11.3-3
ii  librte-table17.11 17.11.3-3
ii  librte-timer17.11 17.11.3-3
ii  librte-vhost17.11 17.11.3-3
ii  zlib1g-dev1:1.2.11.dfsg-1

libdpdk-dev recommends no packages.

libdpdk-dev suggests no packages.

-- no debconf information

Bug#907364: src:mozjs52: FTBFS on i386: several test failures for Spidermonkey 60 build

[Tim Lunn]

Package: src:mozjs52
Version: 60.1.0-1
Severity: normal

I ran a test build of spidermonkey 60.1.0-1 package on the Ubuntu PPA builders 
and had the following test failures on i386 build

## non262/Date/timeclip.js: rc = 3, run time = 0.048487
747197: TimeClip behavior for very large numbers
non262/Date/timeclip.js:19:1 Error: Assertion failed: got true, expected false
Stack:
  @non262/Date/timeclip.js:19:1
TEST-UNEXPECTED-FAIL | non262/Date/timeclip.js | (args: "") [0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test": 
"non262/Date/timeclip.js", "thread": "main", "time": 1535249793.461725}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source": 
"jstests", "status": "FAIL", "test": "non262/Date/timeclip.js", "thread": 
"main", "time": 1535249793.510212}

## test262/language/types/number/S8.5_A2.1.js: rc = 3, run time = 0.04355
uncaught exception: Test262Error: #1: var x = 9007199254740994.0; var y = 1.0 - 
1/65536.0; var z = x + y; var d = z - x; d === 0. Actual: 2
TEST-UNEXPECTED-FAIL | test262/language/types/number/S8.5_A2.1.js | (args: "") 
[0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test": 
"test262/language/types/number/S8.5_A2.1.js", "thread": "main", "time": 
1535249586.113185}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source": 
"jstests", "status": "FAIL", "test": 
"test262/language/types/number/S8.5_A2.1.js", "thread": "main", "time": 
1535249586.156735}

## test262/language/types/number/S8.5_A2.2.js: rc = 3, run time = 0.044356
uncaught exception: Test262Error: #1: var x = 9007199254740994.0; var y = 1.0 - 
1/65536.0; var z = x + y; var d = z - x; d !== 2
TEST-UNEXPECTED-FAIL | test262/language/types/number/S8.5_A2.2.js | (args: "") 
[0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test": 
"test262/language/types/number/S8.5_A2.2.js", "thread": "main", "time": 
1535249586.0153189}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source": 
"jstests", "status": "FAIL", "test": 
"test262/language/types/number/S8.5_A2.2.js", "thread": "main", "time": 
1535249586.059675}

Full logs
https://launchpadlibrarian.net/385368114/buildlog_ubuntu-cosmic-i386.mozjs60_60.1.0-ppa1_BUILDING.txt.gz

Bug#907363: src:mozjs52: FTBFS on i386: various test failures

[Tim Lunn]

Package: src:mozjs52
Version: 60.1.0-1
Severity: normal

I ran a test build of Spidermonkey 60.1.0-1 on the Ubuntu ppa builders and had 
the following test failures:

## non262/Date/timeclip.js: rc = 3, run time = 0.048487
747197: TimeClip behavior for very large numbers
non262/Date/timeclip.js:19:1 Error: Assertion failed: got true, expected false
Stack:
  @non262/Date/timeclip.js:19:1
TEST-UNEXPECTED-FAIL | non262/Date/timeclip.js | (args: "") [0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test": 
"non262/Date/timeclip.js", "thread": "main", "time": 1535249793.461725}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source": 
"jstests", "status": "FAIL", "test": "non262/Date/timeclip.js", "thread": 
"main", "time": 1535249793.510212}

## test262/language/types/number/S8.5_A2.1.js: rc = 3, run time = 0.04355
uncaught exception: Test262Error: #1: var x = 9007199254740994.0; var y = 1.0 - 
1/65536.0; var z = x + y; var d = z - x; d === 0. Actual: 2
TEST-UNEXPECTED-FAIL | test262/language/types/number/S8.5_A2.1.js | (args: "") 
[0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test": 
"test262/language/types/number/S8.5_A2.1.js", "thread": "main", "time": 
1535249586.113185}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source": 
"jstests", "status": "FAIL", "test": 
"test262/language/types/number/S8.5_A2.1.js", "thread": "main", "time": 
1535249586.156735}

## test262/language/types/number/S8.5_A2.2.js: rc = 3, run time = 0.044356
uncaught exception: Test262Error: #1: var x = 9007199254740994.0; var y = 1.0 - 
1/65536.0; var z = x + y; var d = z - x; d !== 2
TEST-UNEXPECTED-FAIL | test262/language/types/number/S8.5_A2.2.js | (args: "") 
[0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test": 
"test262/language/types/number/S8.5_A2.2.js", "thread": "main", "time": 
1535249586.0153189}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source": 
"jstests", "status": "FAIL", "test": 
"test262/language/types/number/S8.5_A2.2.js", "thread": "main", "time": 
1535249586.059675}

full logs:
https://launchpadlibrarian.net/385368114/buildlog_ubuntu-cosmic-i386.mozjs60_60.1.0-ppa1_BUILDING.txt.gz

upstream bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=1486328

Bug#891329: ibus-pinyin: deprecate ibus-pinyin in favour of ibus-libpinyin

[Boyuan Yang]

On Sat, 24 Feb 2018 22:34:26 +0800 Michael Tsang  wrote:
> Package: ibus-pinyin
> Version: 1.5.0-4
> Severity: normal
> 
> Dear Maintainer,
> 
> ibus-pinyin seems to be no longer maintained and updated, and ibus-libpinyin 
is
> a more recent fork for it. Please deprecate this package and upgrade users 
to
> ibus-libpinyin.

I agree with it. What about removing ibus-pinyin after Buster release?

--
Regards,
Boyuan Yang


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

Bug#907362: fwbuilder-dbg is empty

[Adrian Bunk]

Package: fwbuilder-dbg
Version: 5.3.7-2
Severity: grave

Both fwbuilder-dbgsym (with proper contents)
and an empty fwbuilder-dbg exist:

$ dpkg -L fwbuilder-dbg
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/fwbuilder-dbg
/usr/share/doc/fwbuilder-dbg/changelog.Debian.gz
/usr/share/doc/fwbuilder-dbg/changelog.gz
/usr/share/doc/fwbuilder-dbg/copyright
$


Please drop the empty fwbuilder-dbg.

Bug#906253: linpsk: FTBFS: invalid use of incomplete type 'class QButtonGroup'

[Reiner Herrmann]

Control: tags -1 + patch

Hi,

the attached patch fixes the FTBFS by including the missing header for
the class QButtonGroup.

Regards,
  Reiner
diff -Nru linpsk-1.3.5/debian/patches/qt5.11.patch linpsk-1.3.5/debian/patches/qt5.11.patch
--- linpsk-1.3.5/debian/patches/qt5.11.patch	1970-01-01 01:00:00.0 +0100
+++ linpsk-1.3.5/debian/patches/qt5.11.patch	2018-08-27 01:20:29.0 +0200
@@ -0,0 +1,13 @@
+Author: Reiner Herrmann 
+Description: Include missing header for QButtonGroup
+
+--- a/gui/modemenu.cpp
 b/gui/modemenu.cpp
+@@ -23,6 +23,7 @@
+ #include "parameter.h"
+ #include "crxchannel.h"
+ 
++#include 
+ 
+ extern Parameter settings;
+ 
diff -Nru linpsk-1.3.5/debian/patches/series linpsk-1.3.5/debian/patches/series
--- linpsk-1.3.5/debian/patches/series	2017-07-18 18:24:41.0 +0200
+++ linpsk-1.3.5/debian/patches/series	2018-08-27 01:18:31.0 +0200
@@ -1,3 +1,4 @@
 we_have_hamlib.patch
 typo.patch
 ftbfs-clang.patch
+qt5.11.patch


signature.asc
Description: PGP signature

Bug#868525: guile-2.0: New upstream version available

[Rob Browning]

Sebastien Bacher  writes:

> Hey there,
>
> Is that 2.0 update still planned?

I'll try to get to it this week, but I can't recall -- did I already ask
if guile-gnome-platform might be able to move to 2.2?

If we're talking about buster, I'd really like to remove guile-2.0
before the release.

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

Bug#907361: O: libpam-afs-session -- PAM module to set up a PAG and obtain AFS tokens

[Russ Allbery]

Package: wnpp
Severity: normal

I intend to orphan the libpam-afs-session package.  I no longer use the
package and it doesn't seem likely that I will again soon, so I'm no
longer a good maintainer for it.

The package description is:
 AFS is a distributed network file system.  It uses in-kernel credentials
 (AFS tokens) obtained from Kerberos tickets for authentication and access
 control, and controls access to those credentials via PAGs (process
 authentication groups).  This module provides a PAM session
 implementation that puts new logins in separate PAGs and optionally runs
 an external program (usually aklog) to obtain tokens from Kerberos
 tickets.  It is designed to work with a Kerberos PAM module that obtains
 the initial Kerberos tickets.

Note that the package is also orphaned upstream (I was also the upstream
maintainer).  It's very stable and hasn't needed significant changes in
some years, but it does have some poor interactions with systemd-managed
user sessions with modern desktop environments because the environment
variable specifying the location of the Kerberos ticket cache is not exposed
to the PAM session and thus this PAM module does not work correctly.

Bug#856282: ARIA should be used to communicate the status of collapsable content under the Action Needed heading to assistive technologies

[Raphael Hertzog]

Control: tag -1 + moreinfo

Hello,

On Mon, 27 Feb 2017 08:22:52 -0500 am_d...@fastmail.fm wrote:
> Currently, when selecting the Toggle Details buttons with a screen
> reader like gnome-orca, nothing is spoken as the content after these
> buttons in the DOM expands or collapses. I suggest adding the
> aria-expanded attribute to all of these buttons. All of the collapsed
> elements should be set to aria-expanded="false" and all of the expanded
> elements should be set to aria-expanded="true". When the button is
> selected by the user, the state of the aria-expanded attribute should be
> changed as the content expands or collapses. This will cause the correct
> expanded and collapsed notifications to be fired to assistive
> technologies by web browsers.

In the mean time, we changed the rendering of those action items
to use the  tag which is standard HTML5. Is something like
this still required?

I would expect standard HTML to be friendly with screen readers and
other assistive tools. But I might be wrong.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#907360: RM: php-cli-prompt -- ROM; Useless in Debian

[David Prévot]

Package: ftp.debian.org
Severity: normal

Hi,

As documented in #904964, there is AFAICT no point in keeping
php-cli-prompt in Debian.

Thanks in advance.

David


signature.asc
Description: PGP signature

Bug#891063:

[Vincent Lefevre]

On 2018-08-24 18:04:29 -0700, Chris Waters wrote:
> Blaming emacs for a problem with su which is documented by the su man
> page, though, is simply not reasonable. If you're going to insist on
> using su instead of sudo, then it's your job to vet all your
> environment variables to make sure you don't get this sort of
> well-documented side effect. Which can affect all sorts of
> programs--not just emacs.

And you're suggesting sudo while there will be the same issue. From
its man page:

 -e, --edit  Edit one or more files instead of running a command.
[...]
which is precisely what one would use if one just wants to edit a file.

[...]
 If the specified file does not exist, it will be
 created.  Note that unlike most commands run by
 sudo, the editor is run with the invoking user's
   ^^
 environment unmodified.  [...]
 ^^

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

Bug#907359: minify-maven-plugin: FTBFS in buster/sid (Could not resolve dependencies for project com.samaxes.maven:minify-maven-plugin:maven-plugin:1.7.4)

[Santiago Vila]

Package: src:minify-maven-plugin
Version: 1.7.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 --buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_autoreconf -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
mh_patchpoms -plibminify-maven-plugin-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO] 
[INFO] ---< com.samaxes.maven:minify-maven-plugin >
[INFO] Building Minify Maven Plugin 1.7.4
[INFO] [ maven-plugin ]
[WARNING] The POM for org.json:json:jar:debian is missing, no dependency 
information available
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.469 s
[INFO] Finished at: 2018-08-26T12:24:35Z
[INFO] 
[ERROR] Failed to execute goal on project minify-maven-plugin: Could not 
resolve dependencies for project 
com.samaxes.maven:minify-maven-plugin:maven-plugin:1.7.4: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.json:json:jar:debian has not been downloaded from it before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#907358: ncbi-vdb: fix broken library on i386

[Steve Langasek]

Package: ncbi-vdb
Version: 2.9.1-1+dfsg-1
Severity: grave
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic ubuntu-patch

Dear Andreas,

The libncbi-vdb2 library is broken on i386, because while it has managed to
build, it has unresolvable references:

$ ldd -d -r /usr/lib/i386-linux-gnu/libncbi-vdb.so.2
linux-gate.so.1 (0xf7f0d000)
libmbedx509.so.0 => /usr/lib/i386-linux-gnu/libmbedx509.so.0 
(0xf7a33000)
libmbedtls.so.10 => /usr/lib/i386-linux-gnu/libmbedtls.so.10 
(0xf7a03000)
libmbedcrypto.so.1 => /usr/lib/i386-linux-gnu/libmbedcrypto.so.1 
(0xf7999000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf797a000)
libbz2.so.1.0 => /lib/i386-linux-gnu/libbz2.so.1.0 (0xf7968000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7963000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7944000)
libxml2.so.2 => /usr/lib/i386-linux-gnu/libxml2.so.2 (0xf7757000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7655000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7479000)
/lib/ld-linux.so.2 (0xf7f0f000)
libicuuc.so.60 => /usr/lib/i386-linux-gnu/libicuuc.so.60 (0xf72b8000)
liblzma.so.5 => /lib/i386-linux-gnu/liblzma.so.5 (0xf728c000)
libicudata.so.60 => /usr/lib/i386-linux-gnu/libicudata.so.60 
(0xf58e2000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf575b000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf573d000)
undefined symbol: uint64_msbit  (/usr/lib/i386-linux-gnu/libncbi-vdb.so.2)
$

This is because there is no implementation of uint64_msbit for the gcc/i386
target.

However, there doesn't appear to be anything about the gcc/x86_64
implementation which is 64-bit-specific, so attached is a patch that fixes
this bug by simply copying the x86_64 implementation to the i386 file.

This problem was discovered because it caused a build failure for sra-sdk on
i386 in Ubuntu when trying to link against the library at build time.  The
same build failure appears to exist in Debian.

It would also be perfectly reasonable to drop i386 as a supported
architecture for ncbi-vdb if you prefer; but I suggest you then make sure to
actually do this, rather than shipping a broken library package on i386.

Also, this broken library package would have been detectable at build time
if you were building with -Wl,-z,defs in LDFLAGS, as that would have
prevented ever generating a shared library with missing symbols.  That's a
good idea to do anyway, but in particular it would mean that if you didn't
want to support i386 anymore, you could just add this to build flags and not
have to worry about changing the architecture list explicitly.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ncbi-vdb-2.9.1-1+dfsg/debian/patches/i386-uint64_msbit.patch 
ncbi-vdb-2.9.1-1+dfsg/debian/patches/i386-uint64_msbit.patch
--- ncbi-vdb-2.9.1-1+dfsg/debian/patches/i386-uint64_msbit.patch
1969-12-31 16:00:00.0 -0800
+++ ncbi-vdb-2.9.1-1+dfsg/debian/patches/i386-uint64_msbit.patch
2018-08-26 14:57:18.0 -0700
@@ -0,0 +1,25 @@
+Description: add missing implementation of uint64_msbit for i386
+ Without this definition, we get a "successful" library build with undefined
+ symbols on i386.  We can use the same implementation of this function as on
+ x86_64.
+Author: Steve Langasek 
+Last-Modified: 2018-08-26
+
+Index: ncbi-vdb-2.9.1-1+dfsg/interfaces/cc/gcc/i386/arch-impl.h
+===
+--- ncbi-vdb-2.9.1-1+dfsg.orig/interfaces/cc/gcc/i386/arch-impl.h
 ncbi-vdb-2.9.1-1+dfsg/interfaces/cc/gcc/i386/arch-impl.h
+@@ -127,6 +127,13 @@ int32_t uint32_msbit ( uint32_t self )
+ return rtn;
+ }
+ 
++static __inline__
++int32_t uint64_msbit ( uint64_t self )
++{
++if (self==0) return -1;
++return 63 - __builtin_clzll ( self );
++}
++
+ typedef struct int128_t int128_t;
+ struct int128_t
+ {
diff -Nru ncbi-vdb-2.9.1-1+dfsg/debian/patches/series 
ncbi-vdb-2.9.1-1+dfsg/debian/patches/series
--- ncbi-vdb-2.9.1-1+dfsg/debian/patches/series 2018-06-27 20:41:16.0 
-0700
+++ ncbi-vdb-2.9.1-1+dfsg/debian/patches/series 2018-08-26 14:58:11.0 
-0700
@@ -9,3 +9,4 @@
 add_-msse2.patch
 use_debian_packaged_libmbedx.patch
 mbedtls_ssl_init.patch
+i386-uint64_msbit.patch

Bug#901783: Bug#907250: RFS: ms-gsl/1.0.0-2 [RC]

[Boyuan Yang]

On Sat, 25 Aug 2018 14:57:24 +0300 Коля Гурьев  wrote:
> Dear mentors,
> 
> I am looking for a sponsor for my package "ms-gsl"
> 
>  Package name: ms-gsl
>  Version : 1.0.0-2
>  Upstream Author : Microsoft Corporation
>  URL : https://github.com/Microsoft/GSL
>  License : Expat (MIT)
>  Section : libdevel
> [...]
> 
>   https://salsa.debian.org/debian/ms-gsl/merge_requests/1/diffs
> 
> Changes since the last upload:
> 
>   * Add Catch-Classic-Workaround.patch (closes: #906385).
>- Redefine a macro for compatibility with Catch 1.x.x.

Reviewed and sponsored. This is another sign that we need a separate catch2 
package since some software is already using catch 2.x without keeping 
compatibility with catch 1.x.

--
Regards,
Boyuan Yang

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

Bug#907263: [pkg-go] Bug#907263: Bug#907263: dh-golang: Failed to build with gccgo-8

[Michael Hudson-Doyle]

It's available in go list as well, e.g.

$ go list -f '{{if not .Standard}}{{ .ImportPath }}{{end}}'
github.com/snapcore/snapd/snap bytes
github.com/snapcore/snapd/snap
$

Cheers,
mwh

On Mon, 27 Aug 2018 at 03:33, Michael Stapelberg 
wrote:

> There is a way, dh-make-golang does it:
> https://github.com/Debian/dh-make-golang/blob/f0afc0f7169eb4f261449d8c4bd6fc7950583617/make.go#L177-L192
>
> On Sun, Aug 26, 2018 at 12:34 PM, Shengjing Zhu  wrote:
>
>> On Sun, Aug 26, 2018 at 5:44 PM Michael Hudson-Doyle
>>  wrote:
>> >
>> > I've forgotten everything about this code even though I wrote it, but
>> wouldn't it be better to filter out the standard library dependencies?
>> >
>>
>> For golang-go, currently it uses std library to producing the
>> Built-Using for golang-go compiler. For gccgo, there's no such need
>> because it will depends libgo.
>> So for gccgo, it's true that we can filter out the std library. But I
>> doubt if there's clean way...
>>
>> --
>> Best regards,
>> Shengjing Zhu
>>
>> ___
>> Pkg-go-maintainers mailing list
>> pkg-go-maintain...@alioth-lists.debian.net
>>
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
>
>
>
>
> --
> Best regards,
> Michael
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers

Bug#891063:

[Vincent Lefevre]

On 2018-08-24 18:04:29 -0700, Chris Waters wrote:
> Ok, sorry that I can't remember *all* the ways that "su" without a
> login option is broken. Even with that, it's still plenty broken, as
> you have observed,

No, it had worked very well for *years*, until it got broken by
dconf. That's dconf that introduced the breakage.

> which is why the man page for su recommends *not using it without
> the login option*.

Because of the breakage introduced by dconf. The man page under
Debian/stable doesn't even recommend that.

BTW, the su with the login option is also broken since it keeps
the TERM value without the TERMINFO one (most users don't need
one, but this is still a bug).

> There are simply too many things that can break when you have random
> environment variables left around pointing who-knows-where.

In general, that's the problem of the end user. The problem here is
that environment variables are set behind his back.

> Blaming emacs for a problem with su which is documented by the su man
> page, though, is simply not reasonable. If you're going to insist on
> using su instead of sudo, then it's your job to vet all your
> environment variables to make sure you don't get this sort of
> well-documented side effect. Which can affect all sorts of
> programs--not just emacs.

I've reported a bug against su:

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

so that the environment is cleaned up more to work with these
applications that introduced a breakage.

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

Bug#863972: Is it fixed?

[Amorfio Máximo Troleo]

Checking the latest build logs (
https://buildd.debian.org/status/fetch.php?pkg=mesa=amd64=18.1.6-1=1534235311=0
), I see the flag --enable-nine is not present. Judging by the performance
of some games with Proton, I can assume Gallium Nine has indeed not been
enabled. Could anyone confirm whether this bug needs to be reopened? Thank
you.

Bug#907357: O: ssslscan-- sslscan tests SSL/TLS enabled services to discover supported cipher suites

[Marvin Stark]

Package: wnpp

severity: normal

I request an adopter for this package. I'm not able to maintain it in
the future and also do not use it anymore. Furthermore upstream has
indicated that they won't port it to openssl 1.1.

Best Regards

Marvin

-- 
 .""`. Marvin Stark 
: :"  :Homepage: www.der-marv.de
`. `"`
  `-  Debian - when you have better things to do than fix a system 




signature.asc
Description: OpenPGP digital signature

Bug#859719: sslscan: Please migrate to openssl1.1 in Buster

[Marvin Stark]

Hi Sebastian,

I'll orphan the package and I think it should be removed.

See bug=905862.

Feel free to adopt the package :)


On 06/14/2018 11:36 PM, Sebastian Andrzej Siewior wrote:
> Marvin, do you have any plans here? Upstream made it clear that they
> won't support openssl 1.1.0+ and I doubt that an embedded copy of the
> ssl library will work here (not saying it won't, it is not my
> decision).
>
> Sebastian
>

-- 
 .""`. Marvin Stark 
: :"  :Homepage: www.der-marv.de
`. `"`
  `-  Debian - when you have better things to do than fix a system 




signature.asc
Description: OpenPGP digital signature

Bug#907356: ITP: docker-etchosts -- Manage hosts file entries for docker containers

[Leo Antunes]

Package: wnpp
Severity: wishlist
Owner: Leo Antunes 

* Package name: docker-etchosts
  Version : 0.1.0
  Upstream Author : Leo Antunes 
* URL : https://github.com/costela/docker-etchosts
* License : GPLv3
  Programming Lang: Go
  Description : Manage hosts file entries for docker containers

Deamon to automatically manage /etc/hosts entries for running local containers.
It listens for events from the docker daemon and creates or removes entries
accordingly.

- end description -

I'd like to maintain this as a part of the golang packaging team, and
will probably need a sponsor since my old key has been removed from the
keyring and I never got around to re-adding a new one :/


Cheers

Bug#907329: marked as done (Move "INSPECTING THE HISTORY")

[Ian Jackson]

Control: fixed -1 6.11
Control: notfixed -1 6.10

Bug#907350: Fix available

[Federico Ceratto]

Hi zigo,

The repo you created does not contain the history of my packaging repo. Do
you mind if I recreate it?
I'll then do the upload

On Sun, Aug 26, 2018 at 9:39 PM Thomas Goirand  wrote:

> Hi,
>
> I've pushed the needed work in a "zigo" branch on Alioth. Basically,
> it's just changing version in debian/changelog, and removing the patch I
> added in my previous upload (as it's applied upstream in 0.3.10).
>
> Please let me know if I can upload that, and merge in the debian/master
> branch. Thanks in advance.
>
> Cheers,
>
> Thomas Goirand (zigo)
>


-- 
Federico

Bug#905862: Re; RM: sslscan -- RoQA; incompatible with OpenSSL 1.1, won't get ported

[Marvin Stark]

Hello,

yes please remove sslscan. I'will not further support it, as you can see
on the package maintenance.

Best Regards,

Marvin

-- 
 .""`. Marvin Stark 
: :"  :Homepage: www.der-marv.de
`. `"`
  `-  Debian - when you have better things to do than fix a system 

Bug#902437: xwayland: Firefox crashes Wayland on some web pages

[Hector Oron]

Hello,
Missatge de Lars Wirzenius  del dia dt., 26 de juny 2018 a
les 19:51:
>
> Package: xwayland
> Version: 2:1.20.0-2
> Severity: important

> After much headbanging and wailing, I've manged to find way to
> reproduce the crash. I use Firefox as my web browser, and certain web
> pages trigger the crash reproducibly. One such web page is here:
>
> http://johannesbrodwall.com/2018/06/24/forget-about-clean-code-lets-embrace-compassionate-code/

Using xwayland 2:1.20.0-3 I have been able to reproduce by opening
above pointer on X220 machine.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#907355: ITP: golang-github-gregjones-httpcache -- Transport for http.Client that will cache responses

[Dr. Tobias Quathamer]

Package: wnpp
Severity: wishlist
Owner: Dr. Tobias Quathamer 

* Package name: golang-github-gregjones-httpcache
  Version : 0.0~git20180305.9cad4c3-1
  Upstream Author : Greg Jones
* URL : https://github.com/gregjones/httpcache
* License : Expat
  Programming Lang: Go
  Description : Transport for http.Client that will cache responses

The package httpcache provides a http.RoundTripper implementation that
works as a mostly RFC 7234 compliant cache for http responses.
.
It is only suitable for use as a 'private' cache (i.e. for
a web-browser or an API-client and not for a shared proxy).


This package is needed for the new upstream version of dh-make-golang.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#907266: RM: sra-sdk [i386] -- ROM; Does not build fir i386 any more - please remove old version of arch i386

[Andreas Tille]

Hi Bernhard,

On Sun, Aug 26, 2018 at 10:41:13PM +0200, Bernhard Übelacker wrote:
> Hello,
> just tried to find out why the i386 build is failing.

Thanks a lot for the investigation.
 
> I think the fault lies in libncbi-vdb-dev, as it does not
> supply an implementation for i386 for function uint64_msbit,
> like it does for x86_64.
> (And it should probably use something like "-Wl,--no-undefined".)
> 
> The implementation for amd64 is inside this file:
> ./ncbi-vdb-2.9.1-1+dfsg/interfaces/cc/gcc/x86_64/arch-impl.h
> 
> And should probably be also here:
> ./ncbi-vdb-2.9.1-1+dfsg/interfaces/cc/gcc/i386/arch-impl.h
> 
> I am not sure, but is there something specific to x86_64 in this
> implementation or does it fit also for i386?

I admit I have no idea.  However, usually upstream of this type of
software is concentrating on amd64 exclusively since this is what is
practically used for gene sequencing.
 
> But even if this implementation is copied then later a file atomic64.h
> is missing, that exists for x86_64 but not i386.

Am I understand correctly that this might be a good reason to make
ncbi-vdb amd64 only?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#906536: RFS: cavestory-nx/1.2.0-1 [ITP] -- Nostalgic side action adventure game

[Carlos Donizete Froes]

Hi,

> I briefly also browsed your package, and one question immediatly came
> up: Where does data/StageMeta/LICENSE-JSON.txt come from?
> The complete directory is exactly the same as nxengine-evo' git repo,
> minus this file.

Thank you for reviewing the package. This "data/StageMeta" directory
has no commitment to the cavestory-nx project.

This directory was placed just out of curiosity, and I just forgot
to remove it.

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780


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

Bug#907329: Move "INSPECTING THE HISTORY"

[Ian Jackson]

Version: 6.10

Sean Whitton writes ("Bug#907329: Move "INSPECTING THE HISTORY""):
> I'm very happy to see this information published somewhere.  I do not
> like having it as a top level heading in dgit-maint-debrebase(7),
> however -- I do not see it as part of the core workflow described by the
> other top level headings.
> 
> I would like to suggest demoting it into the HINTS AND TIPS section of
> that manpage.  Here are patches.

NP, applied.  (I forgot to add the Closes: tag, so doing that now.)

> We might move it to git-debrebase(7) at a later date if we found other
> things to write about in that page.

OK.

Regards,
Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#907354: apparmor-profiles-extra: unable to open help in Totem

[John Scott]

Package: apparmor-profiles-extra
Version: 1.20
Severity: normal
Control: affects -1 totem

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Choosing Help causes Totem attempt to open Yelp,
which the profile doesn't allow.

apparmor="DENIED" operation="exec" profile="/usr/bin/totem" 
name="/usr/bin/yelp" comm="totem" requested_mask="x" denied_mask="x"

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

Kernel: Linux 4.17.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 apparmor-profiles-extra depends on:
ii  apparmor  2.13-8

apparmor-profiles-extra recommends no packages.

apparmor-profiles-extra suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEJwCMxdBfG24Y2trvfWFEpid5MHIFAluDERQACgkQfWFEpid5
MHLs6wf/YmRpL0ChMLwlPDT0u6ecDrFcdQpx7jVV816JGDLli/VJavL3QPIAVVQw
RV6OOnGUz59YdofEWut5bgxd1niCus8UihLMyk5QfYO3/8qITflM//vFgAxyFW1a
ugksYl/04tVtQYlqrHtielAtVcEwhmwwzL+NnhGlJmFGkabOCmyV3e5V5ZgGkO2h
ulpmkXff7cuQzNC8f0AanniNIozSLqoSr6G/pzZe8LqWHK7XClCgonil790NH2F1
HeXD9AqEBrY39+lAuiV76SfZW4WCWN39okcBhpFkr7BNt47nI7XktTm/Hb7XrRCn
VEUYaNP8nvGaOEMVxGkxNw3jcWhd5Q==
=PF2N
-END PGP SIGNATURE-

Bug#907266: RM: sra-sdk [i386] -- ROM; Does not build fir i386 any more - please remove old version of arch i386

[Bernhard Übelacker]

Hello,
just tried to find out why the i386 build is failing.

I think the fault lies in libncbi-vdb-dev, as it does not
supply an implementation for i386 for function uint64_msbit,
like it does for x86_64.
(And it should probably use something like "-Wl,--no-undefined".)

The implementation for amd64 is inside this file:
./ncbi-vdb-2.9.1-1+dfsg/interfaces/cc/gcc/x86_64/arch-impl.h

And should probably be also here:
./ncbi-vdb-2.9.1-1+dfsg/interfaces/cc/gcc/i386/arch-impl.h

I am not sure, but is there something specific to x86_64 in this
implementation or does it fit also for i386?

But even if this implementation is copied then later a file atomic64.h
is missing, that exists for x86_64 but not i386.

Kind regards,
Bernhard

Bug#907353: ITP: libcrypt-perl-perl -- Perl module implementing cryptography functions in pure Perl

[Salvatore Bonaccorso]

Package: wnpp
Owner: Salvatore Bonaccorso 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libcrypt-perl-perl
  Version : 0.29
  Upstream Author : Felipe Gasper with contributions from Mohammad S Anwar
* URL : https://metacpan.org/release/Crypt-Perl
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Perl module implementing cryptography functions in pure Perl

Just as it sounds: cryptography with no non-core XS dependencies! This is
useful if you don't have access to other tools that do this work like
OpenSSL|http://openssl.org, CryptX, etc. Of course, if you do have access to
one of those tools, they may suit your purpose better.

See submodules for usage examples of:

 * Key generation
 * Key parsing
 * Signing & verification
 * Encryption & decryption
 * Import (Crypt::Perl::PK) from & export to JSON Web Key format
 * JWK thumbprints
 * Certificate Signing Request (PKCS #10) generation (Crypt::Perl::PKCS10)
 * SSL/TLS certificate (X.509) generation (Crypt::Perl::X509v3), including a
   broad variety of extensions

This description was automagically extracted from the module by dh-make-perl.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.

Bug#907350: Fix available

[Thomas Goirand]

Hi,

I've pushed the needed work in a "zigo" branch on Alioth. Basically,
it's just changing version in debian/changelog, and removing the patch I
added in my previous upload (as it's applied upstream in 0.3.10).

Please let me know if I can upload that, and merge in the debian/master
branch. Thanks in advance.

Cheers,

Thomas Goirand (zigo)

Bug#906536: Sponsor for my package "cavestory-nx"

[Phil Morrell]

(dropping list from CC)

On Sun, Aug 26, 2018 at 05:04:36PM -0300, Carlos Donizete Froes wrote:
> Hi,
> 
> > You cannot just drop paragraphs from d/copyright at will, it needs to
> > be backed up by a statement of the copyright owners.
> 
> Sorry, I did not understand the previously replied email
> and I ended up removing it.
> 

Yes, you misunderstood me on this occasion. I tried to do two things:
a) highlight that there was some desire from the author for NC license
that needs confirming, e.g. maybe they want it to be CC-BY-NC?
b) point out, as Tobi did, that you need some public documentation of
the authors intent in order to document that in the copyright

> > Can you, by change, forward the original statement of "pixel", on which
> > basis you wrote d/copyright, to this bug/list?
> 
> Yes, follows the forwarded message.

What we're looking for here is an unambiguous public declaration of the
license from Pixel. I'm afraid the forwarded email doesn't satisfy that.
It's confusing regarding Cave Story/Vorbis and MIT/BSD and nothing in it
mentions Public Domain.

It seems theres some language barrier here, but first you need to find
out what terms the author is after (I'm assuming here that it's art and
not software), the most basic starting point is this:

https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensors

Only after the author has decided on terms can they go about choosing a
license, which may or may not be public domain, but if it is, there
needs to be a clear public statement of that, e.g. the CC0 waiver I
linked.


signature.asc
Description: PGP signature

Bug#907352: please make texinfo generation reproducible

[Nicholas D Steeves]

Package: python3-sphinx
Version: 1.7.7-1
Severity: important

Dear Sphinx maintainers,

Thank you for maintaining python3-sphinx.  I've set the severity of
this bug to important, because I believe this bug affects all packages
that generate info pages using Sphinx.

Here is an example of the unreproducibility on DebCI:
  https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/elpy.html

I'm using this in debian/rules:
PYTHONPATH=. sphinx-build -N -btexinfo docs/ build/info 
makeinfo --no-split build/info/Elpy.texi -o build/info/elpy.info

Stuart Prescott helped me identify the cause on #debian-python and mentioned 
that it also affects "python-bumps", and I've CCed him.

In #debian-mentors Jakub Wilk mentioned that it's possible to
workaround with something like: PYTHONHASHSEED=0

It follows that a temporary workaround using a date stamp from the
most recent changelog entry as a hash seed might not be terrible, but
it would be much better if the root cause was addressed.

Cheers,
Nicholas

Bug#907351: tor: TLS error while constructing a TLS context: dh key too small (in SSL routines:ssl3_ctx_ctrl:---)

[Francois Marier]

Package: tor
Version: 0.3.3.9-1
Severity: normal

I get the following error in my logs approximately every 2 hours:

  Aug 26 05:05:01 hostname Tor[25963]: TLS error while constructing a TLS 
context: dh key too small (in SSL routines:ssl3_ctx_ctrl:---)

I tried upgrading to the version in experimental and it also has this
problem.

Francois

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

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

Versions of packages tor depends on:
ii  adduser 3.117
ii  libc6   2.27-5
ii  libcap2 1:2.25-1.2
ii  libevent-2.1-6  2.1.8-stable-4
ii  liblzma55.2.2-1.3
ii  libseccomp2 2.3.3-3
ii  libssl1.1   1.1.1~~pre9-1
ii  libsystemd0 239-7
ii  libzstd11.3.5+dfsg-1
ii  lsb-base9.20170808
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages tor recommends:
ii  logrotate3.14.0-3
ii  tor-geoipdb  0.3.3.9-1
ii  torsocks 2.2.0-2

Versions of packages tor suggests:
ii  apparmor-utils   2.13-8
pn  mixmaster
pn  obfs4proxy   
pn  socat
pn  tor-arm  
pn  torbrowser-launcher  

-- Configuration Files:
/etc/apparmor.d/system_tor changed:
profile system_tor flags=(attach_disconnected) {
  #include 
  #include 
  #include 
}


-- no debconf information

Bug#905927: [Pkg-postgresql-public] Bug#905927: postgresql-10 breaks pglogical autopkgtest:

[Christoph Berg]

Re: Paul Gevers 2018-08-11 <3524a3a7-0c49-ba8e-9e44-ce3d53bd9...@debian.org>
> With a recent upload of postgresql-10 the autpkgtest of pglogical
> started to fail in unstable and testing. I copied the output of the
> second test below, the fist test is killed because it times out and
> doesn't seem to show anything suspicious why. Probably it doesn't handle
> an error case properly and keeps waiting, because normally the test
> isn't even close to the time out time (3 minutes versus 2:45 hours).

To post some update here: The problem is rumored to be some internal
ABI change (inside PostgreSQL, not in some .so) which is fixed by
recompiling pglogical against the latest PG minors. Though in my tests
this didn't make the problem go away, the first autopkgtest was still
very slow, and the other autopkgtest still died.

I'll post another update once upstream has released any details. (They
promised to do that last week, but I haven't seen anything yet.)

Christoph

Bug#907350: Please package 0.3.10

[Thomas Goirand]

Package: src:freezegun
Severity: important

Hi,

The next version of OpenStack, called Rocky, needs freezegun 0.3.10. Could you
please package it ASAP? Alternatively, would you accept that I do the work as
an NMU?

Cheers,

Thomas Goirand (zigo)

Bug#907214: OMEMO-encrypted file is not unencrypted before saving

[forenjunkie]

Hi,

I tried with pix-art and could not reproduce the problem.

Could you please try starting gajim from console with "-v" switch and 
provide logs from the point on when you receive the message


regards

lovetox

Bug#906536: Sponsor for my package "cavestory-nx"

[Carlos Donizete Froes]

Hi,

> You cannot just drop paragraphs from d/copyright at will, it needs to
> be backed up by a statement of the copyright owners.

Sorry, I did not understand the previously replied email
and I ended up removing it.

> Can you, by change, forward the original statement of "pixel", on which
> basis you wrote d/copyright, to this bug/list?

Yes, follows the forwarded message.

 Mensagem encaminhada 
De: Pixel 
Para: Carlos Donizete Froes 
Assunto: Re: Requesting to add a readme or a simple license to your projects
Data: Sat, 14 Jul 2018 19:44:16 +0900

> Ogg Vorbis is BSD License in this sidte.
> 
> https://en.wikipedia.org/wiki/Vorbis
> 
> So DropEncoderOgg doesn't need have "MIT License".
> I'm wrong?
> 
> Thank you.
> 
> 
> 2018-07-14 4:37 GMT+09:00 Carlos Donizete Froes :
> > Can you add a simple license to Cave Story and other games?
> > 
> > Both me and other users of your games will be less concerned about
> > disclosing and redistributing them on other sites.
> > 
> > Create a readme.txt (text in english) within the 'data' directory, a
> > short and simple permissive license, with conditions that require only
> > copyright preservation.
> > 
> > Thanks!
> > 
> > 
> > Em 13-07-2018 11:17, Pixel escreveu:
> > > DropEncoderOgg should have ReadMe with MIT License's text.
> > > -Is that because of DropEncoderOgg use OggVorbis?
> > > 
> > > Cave Story don't use OggVorbis.
> > > Thank you.
> > > 
> > > 2018-07-11 17:39 GMT+09:00 Carlos Donizete Froes :
> > > > Hi Pixel.
> > > > 
> > > > Yes, could you add this ReadMe.txt that has in 'DropEncoderOgg' also in 
> > > > your
> > > > games?
> > > > 
> > > > Model: 洞窟物語(Cave Story) do not have this ReadMe.txt, could you create 
> > > > it for the
> > > > game?
> > > > 
> > > > Thanks!
> > > > 
> > > > Em qua, 2018-07-11 às 11:41 +0900, Pixel escreveu:
> > > > > Hi, Carlos.
> > > > > 
> > > > > I don't know English well.
> > > > > so I don't think I understood everything of your message.
> > > > > 
> > > > > Do you mean "Pixel should print MIT License in the ReadMe"?
> > > > > which application's is it? "DropEncoderOgg" ?
> > > > > 
> > > > > Thank you for your mail.
> > > > > 
> > > > > 
> > > > > 2018-07-11 4:42 GMT+09:00 Carlos Donizete Froes :
> > > > > > Hi Pixel,
> > > > > > 
> > > > > > Congratulations on your great projects.
> > > > > > 
> > > > > > I have verified that all your files do not have readme or license in
> > > > > > your projects[1].
> > > > > > 
> > > > > > [1] http://studiopixel.sakura.ne.jp/archives/index.html
> > > > > > 
> > > > > > You don’t have to do anything to not offer a license. You may 
> > > > > > however
> > > > > > wish to add a copyright notice and statement that you are not 
> > > > > > offering
> > > > > > any license in a prominent place (e.g., your project’s README) so 
> > > > > > that
> > > > > > users don’t assume you made an oversight.
> > > > > > 
> > > > > > It would be possible to add a readme by placing only simple 
> > > > > > copyright
> > > > > > restrictions or by adding an license.txt?
> > > > > > 
> > > > > > License model:
> > > > > > 
> > > > > > - MIT License[2] - A short and simple permissive license with 
> > > > > > conditions
> > > > > > only requiring preservation of copyright and license notices. 
> > > > > > Licensed
> > > > > > works, modifications, and larger works may be distributed under
> > > > > > different terms and without source code.
> > > > > > 
> > > > > > [2] https://choosealicense.com/licenses/mit
> > > > > > 
> > > > > > I await your response.
> > > > > > 
> > > > > > Thanks!
> > 
> > --
> > ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
> > ⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
> > ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
> > ⠈⠳⣄⠀⠀⠀  2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780
-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780


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

Bug#907349: mirror listing update for ftp.plusline.de

[FTP-Admin]

Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: ftp.plusline.de
Type: leaf
Archive-architecture: amd64 i386
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: FTP-Admin 
Country: DE Germany
Location: Frankfurt
Sponsor: Plus.line AG https://www.plusline.net
Comment: New ftp server name is ftp.plusline.net, please change it.




Trace Url: http://ftp.plusline.de/debian/project/trace/
Trace Url: http://ftp.plusline.de/debian/project/trace/ftp-master.debian.org
Trace Url: http://ftp.plusline.de/debian/project/trace/ftp.plusline.de

Bug#907348: dateutils FTBFS on 32bit: test failures

[Adrian Bunk]

Source: dateutils
Version: 0.4.4-1
Severity: serious
Tags: ftbfs

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

...
FAIL: dtcore-conv
=

  VALUES DIFFER 1341100836 v 1341100833
  VALUES DIFFER 1341100837 v 1341100835
FAIL dtcore-conv (exit status: 1)

FAIL: dtconv.024


$ dconv '2012-03-01 00:00:00' -z TAI
--- "expected output  5b88a553" 2018-08-26 16:07:27.682809364 +
+++ "actual output  5b88a553"   2018-08-26 16:07:27.682809364 +
@@ -1 +1 @@
-2012-03-01T00:00:34
+2012-03-01T00:00:37
$? 1
FAIL dtconv.024.clit (exit status: 1)

FAIL: dtconv.026


$ dconv '2012-03-01 00:00:00' -z GPS
--- "expected output  5b881603" 2018-08-26 16:07:27.702809312 +
+++ "actual output  5b881603"   2018-08-26 16:07:27.702809312 +
@@ -1 +1 @@
-2012-03-01T00:00:15
+2012-03-01T00:00:18
$? 1
FAIL dtconv.026.clit (exit status: 1)

FAIL: dtconv.027


$ dconv '2012-03-01 00:00:00' --from-zone TAI
--- "expected output  5b8820a2" 2018-08-26 16:07:27.714809281 +
+++ "actual output  5b8820a2"   2018-08-26 16:07:27.714809281 +
@@ -1 +1 @@
-2012-02-29T23:59:26
+2012-02-29T23:59:23
$? 1
FAIL dtconv.027.clit (exit status: 1)

FAIL: dtconv.029


$ dconv '2012-03-01 00:00:00' --from-zone GPS
--- "expected output  5b899088" 2018-08-26 16:07:27.734809230 +
+++ "actual output  5b899088"   2018-08-26 16:07:27.734809230 +
@@ -1 +1 @@
-2012-02-29T23:59:45
+2012-02-29T23:59:42
$? 1
FAIL dtconv.029.clit (exit status: 1)

FAIL: dtconv.030


$ dconv '1970-01-01 00:00:00' -z TAI
--- "expected output  5b89b895" 2018-08-26 16:07:27.746809199 +
+++ "actual output  5b89b895"   2018-08-26 16:07:27.746809199 +
@@ -1 +1 @@
-1970-01-01T00:00:10
+1970-01-01T00:00:37
$? 1
FAIL dtconv.030.clit (exit status: 1)

FAIL: dtconv.031


$ dconv '1972-01-01 00:00:00' -z TAI
--- "expected output  5b89402a" 2018-08-26 16:07:27.754809178 +
+++ "actual output  5b89402a"   2018-08-26 16:07:27.754809178 +
@@ -1 +1 @@
-1972-01-01T00:00:10
+1972-01-01T00:00:37
$? 1
FAIL dtconv.031.clit (exit status: 1)

FAIL: dtconv.032


$ dconv '1972-01-01 00:00:01' -z TAI
--- "expected output  5b8967c5" 2018-08-26 16:07:27.766809147 +
+++ "actual output  5b8967c5"   2018-08-26 16:07:27.766809147 +
@@ -1 +1 @@
-1972-01-01T00:00:11
+1972-01-01T00:00:38
$? 1
FAIL dtconv.032.clit (exit status: 1)

FAIL: dtadd.030
===

$ dadd '2012-06-30 23:59:30' 30rs
--- "expected output  5b8a5636" 2018-08-26 16:07:35.554789033 +
+++ "actual output  5b8a5636"   2018-08-26 16:07:35.554789033 +
@@ -1 +1 @@
-2012-06-30T23:59:60
+2012-07-01T00:00:00
$? 1
FAIL dtadd.030.clit (exit status: 1)

FAIL: dtadd.031
===

$ dadd '2012-06-30 23:59:30' 31rs
--- "expected output  5b8a7e58" 2018-08-26 16:07:35.566789002 +
+++ "actual output  5b8a7e58"   2018-08-26 16:07:35.566789002 +
@@ -1 +1 @@
-2012-07-01T00:00:00
+2012-07-01T00:00:01
$? 1
FAIL dtadd.031.clit (exit status: 1)

FAIL: dtadd.034
===

$ dadd '2012-07-01 00:00:05' -6rs
--- "expected output  5b8bf7d2" 2018-08-26 16:07:35.598788920 +
+++ "actual output  5b8bf7d2"   2018-08-26 16:07:35.598788920 +
@@ -1 +1 @@
-2012-06-30T23:59:60
+2012-06-30T23:59:59
$? 1
FAIL dtadd.034.clit (exit status: 1)

FAIL: dtadd.035
===

$ dadd '2012-07-01 00:00:05' -7rs
--- "expected output  5b8b9fe9" 2018-08-26 16:07:35.606788899 +
+++ "actual output  5b8b9fe9"   2018-08-26 16:07:35.606788899 +
@@ -1 +1 @@
-2012-06-30T23:59:59
+2012-06-30T23:59:58
$? 1
FAIL dtadd.035.clit (exit status: 1)

FAIL: dtdiff.019


$ ddiff '2012-06-30 23:59:00' '2012-07-01 00:00:00' -f '%rSs'
--- "expected output  5b86f62a" 2018-08-26 16:07:36.270787184 +
+++ "actual output  5b86f62a"   2018-08-26 16:07:36.270787184 +
@@ -1 +1 @@
-61s
+60s
$? 1
FAIL dtdiff.019.clit (exit status: 1)

FAIL: dtdiff.021


$ ddiff '2012-06-30 23:59:00' '2012-07-01 00:00:00' -f '%rT'
--- "expected output  5b86a6e9" 2018-08-26 16:07:36.290787133 +
+++ "actual output  5b86a6e9"   2018-08-26 16:07:36.290787133 +
@@ -1 +1 @@
-61s
+60s
$? 1
FAIL dtdiff.021.clit (exit status: 1)


Testsuite summary for dateutils 0.4.4

# TOTAL: 853
# PASS:  839
# SKIP:  0
# XFAIL: 0
# FAIL:  14
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to https://github.com/hroptatyr/dateutils/issues

make[6]: *** [Makefile:1227: test-suite.log] Error 1

Bug#907332: ghostscript has a new code execution issue, even when used with -dSAFER

[Salvatore Bonaccorso]

Hi,

On Sun, Aug 26, 2018 at 06:08:58PM +0100, Nicolas Braud-Santoni wrote:
> Tavis Ormandy disclosed a new ghoscript security issue, leading directly to 
> code
> execution:  http://openwall.com/lists/oss-security/2018/08/21/2

There are actually several issues, see the whole thread. For now since
you filled this bug will track all those with this bug entry. Proper
evaluation though is still pending (and Moritz is taking care of
strech, adding this note to dsa-needed file ("needs some research on
issues found by Tavis").

See

https://www.kb.cert.org/vuls/id/332928

the current set of fixes:

http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=b575e1ec
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=8e9ce501
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=241d9111
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=c432131c
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=e01e77a3
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=0edd3d6c
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=a054156d
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=0d390118
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=c3476dde
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=b326a716
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=78911a01
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=5516c614

Regards,
Salvatore

Bug#907049: openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable

[Wolfgang Walter]

This version of openssl also eventually breaks unbound-control of package 
unbound for some people:

unbound-control 

may gives an error:
140493601018752:error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too 
small:../ssl/ssl_rsa.c:310

outcommenting
#CipherString = DEFAULT@SECLEVEL=2

fixes this.

The real fix is probably to generate new keys for unbound-control and unbound 
with unbound-control-setup. Just calling unbound-control-setup is not enough, 
though, as unbound-control does not create new ones if these keys already 
exists. So the existing ones have to be removed first.

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

Bug#906077: plotly: offline drawing missing /usr/lib/python3/dist-packages/plotly/package_data/plotly.min.js

[Josue Ortega]

On Tue, Aug 14, 2018 at 12:08:04AM +0200, Petter Reinholdtsen wrote:
> 
> Package: plotly
> Version: 1.13.0+dfsg-1
> 
> I tested plotly for the first time, and it fail to work.  I started with
> an example from https://plot.ly/python/line-charts/ >, which fail
> to work because I do not have login credentials on some cloud service.
> As I want my graph to work locally, not depend on some cloud service, I
> tried to modify the example to draw using the offline mode.  When I run
> the modified script, I get this error:
> 
> Traceback (most recent call last):
>   File "./infograph", line 35, in 
> py.plot(data, filename='line-mode.html')
>   File "/usr/lib/python3/dist-packages/plotly/offline/offline.py", line 461, 
> in plot
> get_plotlyjs(),
>   File "/usr/lib/python3/dist-packages/plotly/offline/offline.py", line 49, 
> in get_plotlyjs
> plotlyjs = resource_string('plotly', path).decode('utf-8')
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1210, 
> in resource_string
> self, resource_name
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1452, 
> in get_resource_string
> return self._get(self._fn(self.module_path, resource_name))
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1572, 
> in _get
> with open(path, 'rb') as stream:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/usr/lib/python3/dist-packages/plotly/package_data/plotly.min.js'
> 
> Is there a file missing in the binary package?
> 
> This is the script I am using:
> 
> #!/usr/bin/python3
> 
> import plotly.offline.offline as py
> import plotly.graph_objs as go
> 
> # Create random data with numpy
> import numpy as np
> 
> N = 100
> random_x = np.linspace(0, 1, N)
> random_y0 = np.random.randn(N)+5
> random_y1 = np.random.randn(N)
> random_y2 = np.random.randn(N)-5
> 
> # Create traces
> trace0 = go.Scatter(
> x = random_x,
> y = random_y0,
> mode = 'lines',
> name = 'lines'
> )
> trace1 = go.Scatter(
> x = random_x,
> y = random_y1,
> mode = 'lines+markers',
> name = 'lines+markers'
> )
> trace2 = go.Scatter(
> x = random_x,
> y = random_y2,
> mode = 'markers',
> name = 'markers'
> )
> data = [trace0, trace1, trace2]
> py.plot(data, filename='line-mode.html')
> 
> 
> --
> Happy hacking
> Petter Reinholdtsen


Hi Petter,

Unfortunately the current version in Stable does not work with the offline mode
since only the minified version javascript was provided by upstream which does
not comply with de DFSG §2.
I have uploaded a version (2.1.0+dfsg-1~bpo9+1) with the unminified javascript 
to
Stretch Backports repository[1], This version works with offline mode

Best Regards

[1]: https://packages.debian.org/source/stretch-backports/plotly


signature.asc
Description: PGP signature

Bug#907327: Correction

[David Buckley]

Rereading that patch (sorry, I've not actually tested it; my home
network isn't fast enough to trigger the bug, but it compiles!), I
notice I wrote

  if (nrepeats < INT_MAX) {
  
where I meant

  if (tsum < INT_MAX) {

which is actually the thing that can overflow.

-- 
David Buckley

Bug#907347: Can't start with old daemon key

[Andrey Rahmatullin]

Package: deluged
Version: 1.3.15-2
Severity: important

Recently deluged started crashing on launch with

[ERROR   ] 00:42:04 rpcserver:378 [('SSL routines', 'SSL_CTX_use_certificate',
'ee key too small')]

I've fixed this by deleting ~/.config/deluge/ssl/daemon.{cert,pkey} which were
created in 2009.



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

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

Versions of packages deluged depends on:
ii  adduser3.117
ii  deluge-common  1.3.15-2
ii  lsb-base   9.20170808
ii  python 2.7.15-3
ii  python-libtorrent  1.1.5-1+b1

deluged recommends no packages.

deluged suggests no packages.

Bug#907234: gnupg warns that an email was signed by a key that expired... in 2018

[Nicolas Braud-Santoni]

Control: retitle -1 gnupg should correctly deal with multiple keyrings

Hi Alexandre,

Thanks for finding this mail on gnupg-users; it was indeed that my public
keyring didn't have your updated key (with the new subkey expiration).

The second entry was from /usr/share/keyrings/debian-keyring.gpg, which was
more up-to-date.


Best,

  nicoo

On Fri, Aug 24, 2018 at 09:59:12PM -0400, Alexandre Viau wrote:
> On 2018-08-24 09:54 PM, Alexandre Viau wrote:
> > It looks like the signature should be accepted and that there should not
> > be two entries for 0xDA82830E3CCC3A3A, as they are the same key. Am I
> > missing something?
> 
> This might be relevant:
>  - https://lists.gnupg.org/pipermail/gnupg-users/2004-January/021284.html
> 
> [[
> 
> > The second key correspond to a previous state of my key (before I
> > added the second encryption key 1CF0D39E).
> >
> > Shouldn't the keyring merge these two keys ?
> 
> No, if you have a keyring with a duplicate key, the merge happens on
> import.  Since the keys are already there, the way to fix it is:
> 
> * export both keys to a file
> * delete the keys on the keyring.
> * import the keys again.  They will be merged.
> 
> Make a backup first, just in case
> 
> ]]
> 
> Cheers,
> 
> -- 
> Alexandre Viau
> av...@debian.org
> 





signature.asc
Description: PGP signature

Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time

[Paul Gevers]

Hi all,

On Sat, 4 Aug 2018 18:48:44 +0200 Aurelien Jarno 
wrote:
> On 2018-07-23 22:17, Paul Gevers wrote:
> > On Sun, 01 Apr 2018 21:56:33 +0200 Florian Weimer  
> > wrote:
> > > > I have no idea. On a fast 4-cores amd64 machine and for the 3 flavours
> > > > built on amd64, the glibc takes around 20 minutes to build and the
> > > > testsuite around 2h to run.
> > > 
> > > This is still rather slow.  I see native builds on relatively current
> > > hardware taking 2 minutes, plus 12 to 15 minutes to build and run the
> > > test suite (all with parallel make, although parallel make for tests
> > > is disabled automatically for some subdirectories).  200 minutes on
> > > current (amd64) hardware sounds quite excessive.
> > 
> > I just did a retry on our infrastructure and it ran in 57 minutes. But
> > it ran on one of the two big workers (8 cores and 30 GB memory). We want
> > to make all workers equal and we are going down to 2 cores and 7.2 GB.
> > 
> > Could it be that the memory is the actual problem and/or also an issue?
> 
> I don't think think the memory is really a problem, at least not for the
> values you give. A few tests might be memory hungry, but 4GB should be
> enough.

I retried another time, now that all the workers are equivalent. The
current test suite runs in around 2:10 on our infrastructure. Albeit
long, I will remove glibc from the blacklist.

However, we would still appreciate it when the test can be made smarter.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#906845: claws-mail-dillo-viewer: include option to open link with system browser, please

[Ricardo Mones]

control: forwarded -1 
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4080

Hi Bert,

On Tue, Aug 21, 2018 at 10:23:11AM -0600, Bert Riding wrote:
> Package: claws-mail-dillo-viewer
> Version: 3.17.0-1
> Severity: wishlist
> 
> Dear Maintainer,
> Thank you for offering an html browser plugin for claws mail after a long 
> wait.
> I would like to be able to click on a link in dillo and have it open in
> my system browser, instead of using dillo.  This was possible in the old
> days, at least with the fancy plugin.

Not sure if it's easily doable, but looks like a good idea. Forwarding
upstream.

Thanks for reporting,
-- 
  Ricardo Mones 
  ~
  15:14 <@mones> you're overconfident today :) 
  15:14 <@claws> i will be this way forever nowSeen on #claws



signature.asc
Description: PGP signature

Bug#644169: libapache2-mod-perl2: PerlOptions -Sections not permitted in server config, but should be

[Salvatore Bonaccorso]

Hi

The MITRE CVE entry for CVE-2011-2767 is now populated:

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2767

Regards,
Salvatore

Bug#907346: slic3r FTBFS on big endian: #error "admesh works correctly on little endian machines only!"

[Adrian Bunk]

Source: slic3r
Version: 1.3.0+dfsg1-1
Severity: serious
Tags: ftbfs

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

...
In file included from src/libslic3r/TriangleMesh.hpp:5:0,
 from src/libslic3r/Model.hpp:9,
 from src/libslic3r/Print.hpp:14,
 from src/libslic3r/GCode.hpp:11,
 from src/libslic3r/GCode/SpiralVase.hpp:5,
 from src/libslic3r/GCode/SpiralVase.cpp:1:
src/admesh/stl.h:32:2: error: #error "admesh works correctly on little endian 
machines only!"
 #error "admesh works correctly on little endian machines only!"
  ^


This looks similar to the fixed #869638 in slic3r-prusa.

Bug#907345: After upgrading from 5.10.1+dfsg-6 to 5.10.1+dfsg-7 akonadi imap stops working

[Wolfgang Walter]

Package: qtbase-opensource-src
Version: 5.10.1+dfsg-7
Severity: important

After upgrading from version 5.10.1+dfsg-6 to version  5.10.1+dfsg-7  
akonadi's imap resource does not work any more (at least with IPv6 + TLS). It 
permanently tries to establish a connection but fails to do so.

It logs:
org.kde.pim.kimap: Connection to server lost  0

On the server side one can see that akonadi establish a connection but then 
close it immediately and then tires again ...

Dowgrading to  5.10.1+dfsg-6  fixes the problem.

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

Bug#907344: ruby-kramdown: move /usr/bin/kramdown into a Multi-Arch: foreign package

[Helmut Grohne]

Package: ruby-kramdown
Version: 1.15.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:espeak-ng

espeak-ng fails to cross build from source, because its dependeny on
ruby-kramdown is unsatisfiable. In general, Architecture: all packages
can never satisfy cross Build-Depends unless marked Multi-Arch: foreign.
In the case of ruby-kramdown, such a marking would be fatal, because the
kramdown library builds on architecture-dependent ruby extensions and
that architecture-dependence would be masked by the marking. Bummer.

The issue here is that the ruby-kramdown package ships both a library
and a tool. That's something the Debian policy advises against.
Splitting library and tool into separate binary packages solves the
issue: A separate "kramdown" package containing the kramdown command can
be marked Multi-Arch: foreign.

Please consider applying the attached patch.

Helmut
diff --minimal -Nru ruby-kramdown-1.15.0/debian/changelog 
ruby-kramdown-1.15.0/debian/changelog
--- ruby-kramdown-1.15.0/debian/changelog   2017-10-01 15:38:06.0 
+0200
+++ ruby-kramdown-1.15.0/debian/changelog   2018-08-26 20:52:27.0 
+0200
@@ -1,3 +1,11 @@
+ruby-kramdown (1.15.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Split kramdown command into a separate Multi-Arch: foreign package.
+(Closes: #-1)
+
+ -- Helmut Grohne   Sun, 26 Aug 2018 20:52:27 +0200
+
 ruby-kramdown (1.15.0-1) unstable; urgency=medium
 
   * Team upload
diff --minimal -Nru ruby-kramdown-1.15.0/debian/control 
ruby-kramdown-1.15.0/debian/control
--- ruby-kramdown-1.15.0/debian/control 2017-10-01 15:38:06.0 +0200
+++ ruby-kramdown-1.15.0/debian/control 2018-08-26 20:52:27.0 +0200
@@ -27,7 +27,6 @@
 Architecture: all
 XB-Ruby-Versions: ${ruby:Versions}
 Depends: libjs-jquery,
- ruby | ruby-interpreter,
  ruby-coderay,
  ruby-prawn,
  ruby-prawn-table,
@@ -36,7 +35,7 @@
  ${misc:Depends},
  ${shlibs:Depends}
 Suggests: libjs-mathjax
-Description: Fast, pure-Ruby Markdown-superset converter
+Description: Fast, pure-Ruby Markdown-superset converter - ruby library
  The kramdown is a fast, pure Ruby, Markdown parser and converter, using
  a strict syntax definition and supporting several common
  extensions.
@@ -47,3 +46,27 @@
  supported formats:
* input formats: kramdown (a Markdown superset), Markdown, HTML
* output formats: HTML, kramdown, LaTeX (and therefore PDF)
+ .
+ This package contains the ruby library.
+
+Package: kramdown
+Architecture: all
+Multi-Arch: foreign
+Depends: ruby | ruby-interpreter,
+ruby-kramdown (= ${binary:Version}),
+ ${misc:Depends},
+Breaks: ruby-kramdown (<< 1.15.0-1.1~)
+Replaces: ruby-kramdown (<< 1.15.0-1.1~)
+Description: Fast, pure-Ruby Markdown-superset converter - kramdown command
+ The kramdown is a fast, pure Ruby, Markdown parser and converter, using
+ a strict syntax definition and supporting several common
+ extensions.
+ .
+ The kramdown library is mainly written to support the kramdown-to-HTML
+ conversion chain. However, due to its flexibility it supports other
+ input and output formats as well. Here is a list of the
+ supported formats:
+   * input formats: kramdown (a Markdown superset), Markdown, HTML
+   * output formats: HTML, kramdown, LaTeX (and therefore PDF)
+ .
+ This package contains the kramdown command.
diff --minimal -Nru ruby-kramdown-1.15.0/debian/kramdown.install 
ruby-kramdown-1.15.0/debian/kramdown.install
--- ruby-kramdown-1.15.0/debian/kramdown.install1970-01-01 
01:00:00.0 +0100
+++ ruby-kramdown-1.15.0/debian/kramdown.install2018-08-26 
20:52:27.0 +0200
@@ -0,0 +1 @@
+usr/bin
diff --minimal -Nru ruby-kramdown-1.15.0/debian/kramdown.manpages 
ruby-kramdown-1.15.0/debian/kramdown.manpages
--- ruby-kramdown-1.15.0/debian/kramdown.manpages   1970-01-01 
01:00:00.0 +0100
+++ ruby-kramdown-1.15.0/debian/kramdown.manpages   2017-10-01 
15:38:06.0 +0200
@@ -0,0 +1 @@
+man/man1/kramdown.1
diff --minimal -Nru ruby-kramdown-1.15.0/debian/ruby-kramdown.install 
ruby-kramdown-1.15.0/debian/ruby-kramdown.install
--- ruby-kramdown-1.15.0/debian/ruby-kramdown.install   2017-10-01 
15:38:06.0 +0200
+++ ruby-kramdown-1.15.0/debian/ruby-kramdown.install   2018-08-26 
20:52:27.0 +0200
@@ -1 +1,2 @@
 data/kramdown usr/share
+usr/lib
diff --minimal -Nru ruby-kramdown-1.15.0/debian/ruby-kramdown.manpages 
ruby-kramdown-1.15.0/debian/ruby-kramdown.manpages
--- ruby-kramdown-1.15.0/debian/ruby-kramdown.manpages  2017-10-01 
15:38:06.0 +0200
+++ ruby-kramdown-1.15.0/debian/ruby-kramdown.manpages  1970-01-01 
01:00:00.0 +0100
@@ -1 +0,0 @@
-man/man1/kramdown.1
diff --minimal -Nru ruby-kramdown-1.15.0/debian/rules 
ruby-kramdown-1.15.0/debian/rules
--- ruby-kramdown-1.15.0/debian/rules   2017-10-01 15:38:06.0 +0200
+++ ruby-kramdown-1.15.0/debian/rules   

Bug#907343: os-prober creates fedora 28 default menu entry with rescuedisc

[J. Scheurich]

Package: os-prober
Version: 1.76~deb9u1
Severity: normal

When using debian 9 grub/osprober it creates a menu including fedora 28.
But when using the default menu entry (not advanced options) it looks
the fedora rescue image is has been bootet. fedora 28 then comes
without WLAN access (cause of missing firmware ?).

After booting fedora 28, the following command is used:

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-0-rescue-452f77a28c3d47509b4f5ff2d0ce50e0 
root=/dev/sda6

When using the Ubuntu 18.04 grub/os-prober, fedora28 boots with
WLAN acces and

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.17.14-202.fc28.x86_64 root=/dev/sda6

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

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

Versions of packages os-prober depends on:
ii  grub-common  2.02~beta3-5
ii  libc62.24-11+deb9u3

os-prober recommends no packages.

os-prober suggests no packages.

-- no debconf information

Bug#906857: stretch-pu: package fuse/2.9.7-1+deb9u2

[GCS]

On Sun, Aug 26, 2018 at 3:54 PM Adam D. Barratt
 wrote:
> Control: tags -1 + confirmed
>
> On 2018-08-21 19:07, László Böszörményi wrote:
> > There was a security issue in FUSE (Filesystem in Userspace),
> > CVE-2018-10906 which was fixed soon. Unfortunately it caused a
> > regression, autofs and FAT filesystems can not be mounted anymore[1].
> > Upstream patched these upstream and the fixes were uploaded to Sid and
> > migrated to Buster.
[...]
> Please go ahead.
 Uploaded and in stable-new now.

Regards,
Laszlo/GCS

Bug#907313: Lack of guidelines on purging conffiles in stateless packages

[Russ Allbery]

Gioele Barabucci  writes:

> For instance, apache (the application) is configured by some stub conf
> in `/etc/apache` that loads *.conf files from directories such as
> `/etc/apache2/sites-enabled/`. The real files are usually in
> `/etc/apache2/sites-available/`.

> The purge process for the apache (the package) removes the configuration
> files it has installed and the symlinks it has created but leaves the
> configuration files written by the sysadmin alone.

Yeah, this is a very interesting example.  If the administrator puts a
bunch of local configuration in /etc/apache2/sites-available and related
directories, those are pretty clearly intended to be configuration files
of Apache, but should we delete everything in those directories on purge?
I can imagine someone being *quite* surprised by that.

Another thing that makes this less obvious is that this mechanism is
frequently used for cross-package cooperation.  In a sense, everything
under /etc/apache2 is a configuration file for Apache, but a bunch of
other packages do install files into that hierarchy (including things that
don't strongly depend on Apache), so running rm -rf in postrm purge isn't
necessarily correct.

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

Bug#905927: postgresql-10 breaks pglogical autopkgtest:

[Paul Gevers]

Control: reassign -1 src:pglogical 2.2.0-1
Control: retitle -1 pglogical: autopkgtest times out

Dear all,

On 11-08-18 21:29, Paul Gevers wrote:
> I copied the output of the
> second test below, the fist test is killed because it times out and
> doesn't seem to show anything suspicious why. Probably it doesn't handle
> an error case properly and keeps waiting, because normally the test
> isn't even close to the time out time (3 minutes versus 2:45 hours).

As this is wasting a lot of time on our infrastructure, I am going to
blacklist pglogical now that postgresql-10 migrated. We'll lift the
block once this bug is closed.

Paul

Bug#907313: Lack of guidelines on purging conffiles in stateless packages

[Russ Allbery]

Julien Cristau  writes:

> Second, policy 10.7.3 seems pretty clear to me that purge ought to
> remove the package's configuration files, whether they're conffiles or
> not.

I just looked at this, and I think that's the *intent*, but I don't think
we succeed in being quite as clear as we might have intended.  The key
sentence seems to be this one:

configuration files must be preserved when the package is removed, and
only deleted when the package is purged.

That doesn't quite say that configuration files must be deleted when the
package is purged, only that they *shouldn't* be deleted when the package
*isn't* purged.

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

Bug#813222: New upstream version (1.4.4) - Help for maintenance ?

[Sebastien Badia]

Hi,

Thanks for this reminder,
Just in order to update this bug, the 1.7.6-1 is currently in the NEW queue, and
rspamd packaging is available on salsa :-)

  https://ftp-master.debian.org/new/rspamd_1.7.6-1.html
  https://salsa.debian.org/debian/rspamd

Cheers,


signature.asc
Description: PGP signature

Bug#907313: Lack of guidelines on purging conffiles in stateless packages

[Russ Allbery]

Holger Levsen  writes:

> I don't think this (nice) new paradigm changes anything and do think
> that all types of configuration files should be treated the same.

> I'd suggest to close this bug as 'wontfix'.

If we do want to recommend removing those files, we shouldn't close this
bug as wontfix, since that's not particularly obvious from Policy at
present.  Those files are not conffiles of the package, and we're not
entirely explicit that either they are configuration files of the package
(I think they are, but it feels useful to clearly say this) or that all
configuration files should be removed by the postrm script on purge (we
sort of say this, but not as clearly as we could, at least in a quick
check).

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

Bug#907342: transition: octave

[Sébastien Villemot]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-octave.html

Dear Release Team,

Please schedule a transition for octave. The latest minor release (4.4.1)
bumped the SOVERSION of liboctave.

Since this ABI change, though not backward compatible, is minimal, the
transition should be straightforward. In any case, we stand ready to fix issues
and NMU if needed.

The new version of octave is already in experimental.

Best,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org

Bug#906536: Sponsor for my package "cavestory-nx"

[Tobias Frost]

On Sun, 2018-08-26 at 15:44 -0300, Carlos Donizete Froes wrote:
> Hi Phil,
> 
> > I believe this is the problematic section of debian/copyright? I
> > also
> > found https://wiki.debian.org/DFSGLicenses#Public_Domain helpful.
> 
> I would like the section of this game to be "contrib/games",
> but because of this problem I left it as a "non-free/games".
> 
> > Files: data/*
> > Copyright: not applicable
> > Author: 2004 Studio Pixel 
> > License: public-domain
> >  This software was written by Daisuke Amaya also known by his art
> > name 'Pixel'.
> >  .
> >  You absolutely can't use these in anything commercial; the work is
> > not subject
> >  to copyright in any jurisdiction.
> >  .
> >  This file is in the public domain. It is provided "as is", without
> > warranty of
> >  any kind. Use at your own risk.
> > 
> > The second paragraph is self-contradicting - if it's not subject to
> > copyright, then it's use can't be restricted to NC. Perhaps the
> > author
> > would prefer a different license? (any form of NC is still non-
> > free)
> 
> Removed this second paragraph from the copyright.

> > To avoid future disputes, after a private email conversation it is
> > necessary to have a public record of the conclusion. Perhaps the
> > author
> > would be happy to email a CC0 style waiver:
> > https://creativecommons.org/choose/zero/waiver
> > 
> > * For public-domain "Copyright" line means who had the authority to
> >   license the work, i.e. the author, not "not applicable"
> > * Since the full name is known, I would put that in the copyright
> > line
> >   e.g Daisuke "Pixel" Amaya 
> 
> Many thanks for the tip, and modified according to the instructions.

You cannot just drop paragraphs from d/copyright at will, it needs to
be backed up by a statement of the copyright owners.
Can you, by change, forward the original statement of "pixel", on which
basis you wrote d/copyright, to this bug/list?

Thanks!

-- 
tobi

Bug#906617: autopkgtest: Please consider defining directory environment variables

[Paul Gevers]

Hi Paul,

On 26-08-18 04:33, Paul Hardy wrote:
> First of all, I would like to say that I know that Martin has file an
> RFH for autopkgtest because he no longer has the time he used to have
> for its maintenance, so I sincerely appreciate the detailed reply that
> he sent to me.

Ack. Several people have stepped up since then, including me, but more
help is still nice.

> On Sat, Aug 25, 2018 at 1:06 PM Paul Gevers  wrote:
>>
>> Hi Paul,
>>
>> On 25-08-18 03:02, Paul Hardy wrote:
>> ...
>> Patches to the documentation are always welcome, especially to cover
>> blind spots in our minds, even if only to get us in the right direction
>> of what you are really looking for. However, as Martin already
>> mentioned, try to do this not too specific for make as there are so many
>> other frameworks.
> 
> I would have already done that, but felt anything I wrote would have
> been conjecture.  My stumbling block is that I do not understand all
> the virtual runtime environments that autopkgtest supports.
> 
> I can suggest additional text as a patch here, re-opening the bug (I
> didn't want to do that before).  Then you can accept or reject the
> text I suggest, and close the bug again.

If you feel more happy with that, please do (please retitle the bug if
you do). Third option is to use your text as starting point and amend it
before acceptance.

>> Also, I am trying to collect these kind of things and related stuff
>> (which may be framework specific) here:
>> https://wiki.debian.org/ContinuousIntegration/AutopkgtestBestPractices
>> Feel free to add your remarks there.
> 
> I will be glad to do that once I think I have my facts straight.  In
> the meantime though, with my less than perfect autopkgtest
> understanding, I will load experimental packages and make sure the CI
> stuff works first.

Please, don't wait too long. Just update it. If there is stuff wrong
we'll fix it. And just a note about adding autopkgtest to your packages,
you are aware that you can test it on our infrastructure from
experimental? And you know that if it fails from the beginning, it
doesn't change anything with respect to not having a test? So feel free
to just start adding it, even if unsure. You can always seek help on
#debci or on our mailing list.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#906536: RFS: cavestory-nx/1.2.0-1 [ITP] -- Nostalgic side action adventure game

[Tobias Frost]

Hallo coringao,

I just want to ensure that this remakr is not lost [from 1, #16],
because it has not been addressed properly back then. 

in [1] #16 I wrote:
- as you've seem have to forked from nxegine-evo [2], can you go a bit
  into the reasons of your fork. As far as I can see the changes are
  minor, to the level of fixing spelling errors in comments and
variable names.

in [1] #30: you wrote:
> Yes, I made a fork with this engine where I made minor changes. I've
already
> mentioned this mechanism in this package.

Frankly, you should only fork for important reasons. Minor changes are
not. Instead, work together with cavestory-nx and get your fixes
merged.

-- end of quote --

I briefly also browsed your package, and one question immediatly came
up: Where does data/StageMeta/LICENSE-JSON.txt come from?
The complete directory is exactly the same as nxengine-evo' git repo,
minus this file. 

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

[2] https://github.com/nxengine/nxengine-evo

-- 
tobi

Bug#907042: opam 1.2.0 is deprecated (jessie)

[Ben Hutchings]

On Sun, 2018-08-26 at 16:40 +0100, Nicolas Braud-Santoni wrote:
> Dear LTS contributors,
> 
> I'm a co-maintainer of opam, the OCaml-specific dependencies manager, which
> is currently broken in olstable: the version in Jessie is 1.2.0 and does
> not support the current opam repository format[0], meaning that users
> cannot install new OPAM packages, get updates, ... (see #907042)
> 
> I would like to propose an update in Jessie to 1.2.2, the same version as
> in Stretch, and Ben suggested that I ask here to check nobody would be
> opposed to it, and to get advise on the process to follow.
> 
> Please note that upstream is planning a change to a new repository format
> (as part of releasing 2.0.0, which is currently in NEW) [1], but they plan
> to keep a branch of the repository in 1.2 format, and accept important
> updates there, so opam 1.2 will keep working for users of stable and LTS.

This seems OK in principle, but:

* Looking at the upstream CHANGES file, there seem to be quite large
non-bugfix changes between 1.2.0 and 1.2.2.  Are they definitely
backward-compatible?

* The Build-Depends for the version in stretch are not satisfiable in
jessie (specifically libdose3-ocaml-dev (>= 4.0.1-2~), libcmdliner-
ocaml-dev (>= 0.9.7~), ibjsonm-ocaml-dev).  It looks like you will need
to revert several of the packaging changes.

Ben.
 
-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
   A fail-safe circuit will destroy others.



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

Bug#907341: umockdev: autopkgtest regression: g_path_get_dirname: assertion 'file_name != NULL' failed

[Paul Gevers]

Source: umockdev
Version: 0.12-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With the upload of 0.12-1 the autopkgtest of your package started to
fail in testing and unstable. I copied the output below.

Currently this regression is contributing to the delay of the migration
to testing [1]. Could you please investigate the situation and fix it?
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=umockdev

https://ci.debian.net/data/autopkgtest/testing/amd64/u/umockdev/884405/log.gz


==  Running test-umockdev-record test against installed system ==

(tests/.libs/test-umockdev-record:13849): GLib-CRITICAL **:
15:13:01.604: g_path_get_dirname: assertion 'file_name != NULL' failed
/bin/bash: line 1: 13849 Trace/breakpoint trap   INSTALLED_TEST=1
umockdev-wrapper $NO_LT

(/tmp/autopkgtest-lxc.cor8a1_g/downtmp/build.9xo/src/tests/.libs/test-umockdev-record:13850):
GLib-CRITICAL **: 15:13:01.639: g_path_get_dirname: assertion 'file_name
!= NULL' failed
/bin/bash: line 1: 13850 Trace/breakpoint trap   INSTALLED_TEST=1
umockdev-wrapper $f
make: *** [Makefile:2211: check-installed] Error 133



signature.asc
Description: OpenPGP digital signature

Bug#906536: Sponsor for my package "cavestory-nx"

[Carlos Donizete Froes]

Hi Phil,

> I believe this is the problematic section of debian/copyright? I also
> found https://wiki.debian.org/DFSGLicenses#Public_Domain helpful.

I would like the section of this game to be "contrib/games",
but because of this problem I left it as a "non-free/games".

> Files: data/*
> Copyright: not applicable
> Author: 2004 Studio Pixel 
> License: public-domain
>  This software was written by Daisuke Amaya also known by his art name 
> 'Pixel'.
>  .
>  You absolutely can't use these in anything commercial; the work is not 
> subject
>  to copyright in any jurisdiction.
>  .
>  This file is in the public domain. It is provided "as is", without warranty 
> of
>  any kind. Use at your own risk.
> 
> The second paragraph is self-contradicting - if it's not subject to
> copyright, then it's use can't be restricted to NC. Perhaps the author
> would prefer a different license? (any form of NC is still non-free)

Removed this second paragraph from the copyright.

> To avoid future disputes, after a private email conversation it is
> necessary to have a public record of the conclusion. Perhaps the author
> would be happy to email a CC0 style waiver:
> https://creativecommons.org/choose/zero/waiver
> 
> * For public-domain "Copyright" line means who had the authority to
>   license the work, i.e. the author, not "not applicable"
> * Since the full name is known, I would put that in the copyright line
>   e.g Daisuke "Pixel" Amaya 

Many thanks for the tip, and modified according to the instructions.

> > > Why do you have 3 sponsorship-requests bugs open for the same package?
> > > Please close two of them and re-title the bug you leave open to the new
> > > version.
> > 
> > Okay, I'll close these open requests.
> 
> As well as closing 903872 & 905984 for the old version, it would help if
> 906536 blocks the ITP but lose the "[ITP]" in the subject. FWIW these
> days I don't bother with sponsorship-requests for games and just post
> directly to the mailing list and only if I get no response raise an RFS.

I'm sorry for my mistakes made with "sponsorship-requests",
in the next packages I'll be more careful. :(

Closed 903872 & 905984 in d/changelog.
Retitled Short Description: #906536

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780


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

Bug#907227: equalx: FTBFS with Qt 5.11

[Juhani Numminen]

Control: tags -1 patch
Control: forwarded -1 https://bugs.launchpad.net/equalx/+bug/1789117

Dear maintainer,

I have a one-line patch for this and I've sent it upstream as well.

Regards,
Juhani

Bug#907340: qtbase-opensource-src breaks purpose autopkgtest possibly due to new openssl

[Paul Gevers]

Source: qtbase-opensource-src, purpose
Version: qtbase-opensource-src/5.11.1+dfsg-7
Version: purpose/5.47.0-1
X-Debbugs-CC: debian...@lists.debian.org, open...@packages.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Control: block 907015 by -1

Dear maintainers,

With a recent upload of qtbase-opensource-src the autopkgtest of purpose
started to fail in testing. I copied the output below.

I suspect that this regression is due to the fact that
qtbase-opensource-src was build with the 1.1.1* version of openssl which
incorporates changes regarding the default minimum level of security,
hence the CC. I suggest to discuss with the openssl maintainers how to
best fix this situation. I added a block relation on a tracking bug for
this as well.

Currently this regression is contributing to the delay of the migration
of qtbase-opensource-src to testing [1] and I assigned this bug to both
source packages (qtbase-opensource-src, purpose). Could you please
investigate the situation and reassign the bug to the right package? If
needed, please change the bug's severity as appropriate. I just filed a
similar bug against the qtbase-opensource-src, kdeconnect combination;
#907339, if both these issue are fully due to qtbase-opensource-src,
they should probably be merged)

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=qtbase-opensource-src

https://ci.debian.net/data/autopkgtest/testing/amd64/p/purpose/883222/log.gz

autopkgtest [05:31:24]: test testsuite: [---
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
libKF5Parts.so.5 was not found.
libKF5Plasma.so.5 was not found.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 20788, result = 0
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :99
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.d450qx99/downtmp/build.4qo/src/obj-x86_64-linux-gnu
Start 1: alternativesmodeltest
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
kf5.kio.kio_http: Can't communicate with kded_kcookiejar!
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: PID 20805 terminated.
kdeinit5: PID 20817 terminated.
kdeinit5: PID 20806 terminated.
1/2 Test #1: alternativesmodeltest ***Failed5.40 sec
* Start testing of AlternativesModelTest *
Config: Using QtTest library 5.11.1, Qt 5.11.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.2.0)
PASS   : AlternativesModelTest::initTestCase()
QDEBUG : AlternativesModelTest::runJobTest() missing mandatory argument
"destinationPath"
QDEBUG : AlternativesModelTest::runJobTest() missing mandatory argument
"destinationPath"
QWARN  : AlternativesModelTest::runJobTest() kf5.kservice.services:
KMimeTypeTrader: couldn't find service type "KParts/ReadOnlyPart"
Please ensure that the .desktop file for it is installed; then run
kbuildsycoca5.
FAIL!  : AlternativesModelTest::runJobTest() 's.count() || s.wait()'
returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.d450qx99/downtmp/build.4qo/src/autotests/alternativesmodeltest.cpp(74)]
PASS   : AlternativesModelTest::bigBufferTest()
PASS   : AlternativesModelTest::disablePluginTest()
PASS   : AlternativesModelTest::blacklistTest()
PASS   : AlternativesModelTest::cleanupTestCase()
Totals: 5 passed, 1 failed, 0 skipped, 0 blacklisted, 5383ms
* Finished testing of AlternativesModelTest *

Start 2: menutest
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
kf5.kio.kio_http: Can't communicate with kded_kcookiejar!
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch

Bug#894865: RFS: cavestory-nx/1.0.0-1 [ITP] -- Nostalgic side action adventure game

[Tobias Frost]

Control: tags -1 -fixed
Control: forcemerge 894865 906536

Bug#907337: WIP packaging VCS

[David Bremner]

In case someone is interested, there is some beginnings of packaging at

   https://salsa.debian.org/bremner/dateparser.git

it is not currently in a state suitable for the archive, but it might be
a place to start.

Or you could run debmake yourself.

Bug#907210: fixed in libfastahack 0.0+git20160702.bbc645f+dfsg-3

[Ivo De Decker]

Control: reopen -1

Hi Andreas,

On Sat, Aug 25, 2018 at 04:04:19PM +, Andreas Tille wrote:
> Subject: Bug#907210: fixed in libfastahack 0.0+git20160702.bbc645f+dfsg-3
> 
> Source: libfastahack
> Source-Version: 0.0+git20160702.bbc645f+dfsg-3

It seems libfastahack still FTBFS on mips64el and ppc64el.

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

Cheers,

Ivo

Bug#907339: qtbase-opensource-src breaks kdeconnect autopkgtest possibly due to new openssl

[Paul Gevers]

Source: qtbase-opensource-src, kdeconnect
Version: qtbase-opensource-src/5.11.1+dfsg-7
Version: kdeconnect/1.3.1-1
X-Debbugs-CC: debian...@lists.debian.org, open...@packages.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Control: block 907015 by -1

Dear maintainers,

With a recent upload of qtbase-opensource-src the autopkgtest of
kdeconnect started to fail in testing. I copied the output below.

I suspect that this regression is due to the fact that
qtbase-opensource-src was build with the 1.1.1* version of openssl which
incorporates changes regarding the default minimum level of security,
hence the CC. I suggest to discuss with the openssl maintainers how to
best fix this situation. I added a block relation on a tracking bug for
this as well.

Currently this regression is contributing to the delay of the migration
of qtbase-opensource-src to testing [1] and I assigned this bug to both
source packages (qtbase-opensource-src, kdeconnect). Could you please
investigate the situation and reassign the bug to the right package? If
needed, please change the bug's severity as appropriate. I suspect that
in the current state, you want to block migration of
qtbase-opensource-src to testing.

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=qtbase-opensource-src

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kdeconnect/883103/log.gz

autopkgtest [04:09:56]: test testsuite: [---
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
kbuildsycoca5 running...
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.at0u7euo/downtmp/build.Gev/src/obj-x86_64-linux-gnu
  Start  1: pluginloadtest
 1/10 Test  #1: pluginloadtest ...   Passed0.16 sec
  Start  2: sendfiletest
 2/10 Test  #2: sendfiletest .   Passed0.14 sec
  Start  3: networkpackettests
 3/10 Test  #3: networkpackettests ...   Passed0.01 sec
  Start  4: testsocketlinereader
 4/10 Test  #4: testsocketlinereader .   Passed0.02 sec
  Start  5: testsslsocketlinereader
 5/10 Test  #5: testsslsocketlinereader ..***Exception: Child
aborted309.65 sec
* Start testing of TestSslSocketLineReader *
Config: Using QtTest library 5.11.1, Qt 5.11.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.2.0)
PASS   : TestSslSocketLineReader::initTestCase()
FAIL!  : TestSslSocketLineReader::testTrustedDevice()
'm_clientSocket->isEncrypted()' returned FALSE. (Client is not encrypted)
   Loc:
[/tmp/autopkgtest-lxc.at0u7euo/downtmp/build.Gev/src/tests/testsslsocketlinereader.cpp(134)]

=== Received signal at function time: 30ms, total time: 309636ms,
dumping stack ===
=== End of stack trace ===
QFATAL : TestSslSocketLineReader::testUntrustedDevice() Test function
timed out
FAIL!  : TestSslSocketLineReader::testUntrustedDevice() Received a fatal
error.
   Loc: [Unknown file(0)]
Totals: 1 passed, 2 failed, 0 skipped, 0 blacklisted, 309637ms
* Finished testing of TestSslSocketLineReader *

  Start  6: kdeconnectconfigtest
 6/10 Test  #6: kdeconnectconfigtest .   Passed0.07 sec
  Start  7: lanlinkprovidertest
 7/10 Test  #7: lanlinkprovidertest ..***Failed   19.93 sec
* Start testing of LanLinkProviderTest *
Config: Using QtTest library 5.11.1, Qt 5.11.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.2.0)
QDEBUG : LanLinkProviderTest::initTestCase() kdeconnect.core: onStart
PASS   : LanLinkProviderTest::initTestCase()
QDEBUG : LanLinkProviderTest::pairedDeviceTcpPacketReceived()
kdeconnect.core: Preventing duplicate broadcasts
QDEBUG : LanLinkProviderTest::pairedDeviceTcpPacketReceived()
kdeconnect.core: Broadcasting identity packet
QDEBUG : LanLinkProviderTest::pairedDeviceTcpPacketReceived()
kdeconnect.core: Starting client ssl (but I'm the server TCP socket)
FAIL!  : LanLinkProviderTest::pairedDeviceTcpPacketReceived()
'spy3.wait()' returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.at0u7euo/downtmp/build.Gev/src/tests/lanlinkprovidertest.cpp(141)]
FAIL!  : LanLinkProviderTest::pairedDeviceUdpPacketReceived()
'!spy.isEmpty() || spy.wait()' returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.at0u7euo/downtmp/build.Gev/src/tests/lanlinkprovidertest.cpp(168)]
QDEBUG : LanLinkProviderTest::unpairedDeviceTcpPacketReceived()
kdeconnect.core: Broadcasting identity packet
QDEBUG : LanLinkProviderTest::unpairedDeviceTcpPacketReceived()
kdeconnect.core: Starting client ssl (but I'm the server TCP socket)
FAIL!  : LanLinkProviderTest::unpairedDeviceTcpPacketReceived()
'spy3.wait()' returned FALSE. ()
   Loc:

Bug#907338: tracker.debian.org: confusion between keyword and keywordall

[shirish शिरीष]

Package: tracker.debian.org
Severity: normal

Dear Maintainer,

First of all thank you for the work being done in making distro tracker better.

According to https://qa.pages.debian.net/distro-tracker/usage/mailbot.html
one can interact with the tracker via email, while some parts work,
some parts don't .

To test the system I sent a few emails to cont...@tracker.debian.org -

1. which [myemail id] - This one worked and sent me a list of all the
packages I have subscribed to.

2. keyword [email id] - This one worked as well and sent me a list of
all the keywords I'm accepting, unfortunately it tole me I'm accepting
all the keywords.

Here's the default list of accepted keywords for [myemail]
* archive
* bts
* bts-control
* build
* contact
* default
* summary
* upload-source

Now I tried various methods to just have 'summary' for all the
packages I'm subscribed to.

The one which worked was -

keyword [myemailid] = summary

I tried using keywordall but for some reason that didn't work. Is this
to be used by a team or by a user, it's not clear :(

>From 
>https://qa.pages.debian.net/distro-tracker/usage/mailbot.html#mailbot-commands-reference

keyword [email] +|-|= list of keywords

Accept (+) or refuse (-) mails classified under the given
keyword(s). Define the list (=) of accepted keywords. This changes the
default set of keywords accepted by a user.

Examples:

keyword + vcs derivatives
keyword u...@example.net - bts bts-control
keyword = default contact upload-source

keywordall [email] +|-|= list of keywords
Accept (+) or refuse (-) mails classified under the given
keyword(s). Define the list (=) of accepted keywords. This changes the
set of accepted keywords of all the currently active subscriptions of
a user.

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

-- 
  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#907337: RFP: python3-dateparser -- Date parsing library designed to parse dates from HTML pages

[David Bremner]

Package: wnpp
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: dateparser
  Version : 0.7.0
  Upstream Author : Scrapinghub
* URL : https://github.com/scrapinghub/dateparser
* License : BSD 3 Clause
  Programming Lang: python
  Description : Date parsing library designed to parse dates from HTML pages

This is a dependency for webmacs (#907331). I'd rather not get into
the python module packaging business, but I guess I will if no-one
else takes it up.


-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAluC5dgACgkQ8gKXHaSn
niyPVwv7BXH3ZA+/fVyPcOlExaIzbs8bZGrO2XWIGh1WdAaBjDgZTIjr1tsxX9XW
5d6sqkAFR815ZS/U3uR2TrnIXxN6yf4RPPkPSxDRqZCt1XUQ4HaVLONt8VAe2Dwt
YO0hw8ccd6Ir1MK4tMSK1weuUym/v0dXrNY98LXWzhXE5L75V2rsrAP7R2qSpDLM
Rbr3yAHiTitWLDIIMLRlwW+U1lcY5aEUKGyCDonYsIxEi505aAy7n/g9nFFb6q0i
bdij11OZAszrEyAsN+etdVlXwdmREOrE1wgfIndZY09RNFAKQ5k50RyjI2CGZuGW
lQQ/Z+KqQx1kbOZVXg6cfNcDJqoZNYvRZAC3NQNSjuHWUt1utN39ovinublr0a7Q
w5qgmeef7/NIpLzxbPhYOuX0ESWKsjtuw25NFJKi/azMfCUN+5L/dHQcoysxMd4p
sB0/WFoqtrtHBup3hSej6M216XIBTujpxyvPl2cVhgTacRtvwG+yeJU1e/GwaCUq
0ZtBECRc
=0ePe
-END PGP SIGNATURE-