Bug#904460: RM: php-apigen -- RoQA; Useless in Debian

[David Prévot]

Package: ftp.debian.org
Severity: normal

Hi,

As documented in #816796, and agreed in #883386#10, there is AFAICT no
point in keeping php-apigen in Debian.

Thanks in advance.

David



signature.asc
Description: PGP signature

Bug#904459: netdata: modifies conffiles (policy 10.7.3): /etc/netdata/health_alarm_notify.conf

[Andreas Beckmann]

Package: netdata
Version: 1.10.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/#configuration-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

  /etc/netdata/health_alarm_notify.conf


cheers,

Andreas


netdata_1.10.0+dfsg-1.log.gz
Description: application/gzip

Bug#904458: libwandio1: libwandio 4 is available upstream

[Stéphane Bortzmeyer]

Package: libwandio1
Version: 3.0.21-1+b1
Severity: normal

Dear Maintainer,

Upstream is now at version 4 (now separated from libtrace) and it
would be cool to have it.

Please build it with 'configure --with-http' as some programs (like
bgpstream ) require it.

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

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

Versions of packages libwandio1 depends on:
ii  libbz2-1.0  1.0.6-8.1
ii  libc6   2.24-11+deb9u3
ii  liblzma55.2.2-1.2+b1
ii  zlib1g  1:1.2.8.dfsg-5

libwandio1 recommends no packages.

libwandio1 suggests no packages.

-- no debconf information

Bug#898814: When I log in, it hangs until crng init done

[Vincent Lefevre]

On 2018-05-16 14:55:07 +0800, 積丹尼 Dan Jacobson wrote:
> I am also experiencing:
> https://unix.stackexchange.com/questions/442698/when-i-log-in-it-hangs-until-crng-init-done

I have the same problem (when logging via lightdm).

One of the answers says "Apparently updating util-linux 2.32 should
fix the issue" but this is not true since I have util-linux 2.32-0.1.

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

Bug#904457: tasksel: please (re)add libreoffice-kde5 to task-kde-desktop

[Rene Engelhard]

Package: tasksel
Version: 3.44
Severity: wishlist
Tags: patch

Hi,

libreoffice-kde got removed from the kde-desktop task once because it
was not built anymore because it was for Qt4/KDE4.

Now with LibreOffice 6.1 it's available again (as libreoffice-kde5, -kde
was readded as a transitional package). So please (re)add
libreoffice-kde5 to the task.

In alioth I had commit rights but in salsa I don't have (yet) so this
bug and:

Patch/MR at http://salsa.debian.org/installer-team/tasksel/merge_requests/2

Regards,

Rene

Bug#904456: clang-6.0: Stack traces displayed by sanitizers do not display debug symbols even though excecutable is built with them

[Valentin]

Package: clang-6.0
Version: 1:6.0.1-2
Severity: normal

Dear Maintainer,

I am building a trivial executable (for example the first example from
http://clang.llvm.org/docs/MemorySanitizer.html) with -g
-fno-omit-frame-pointer and for examples -fsanitize=memory. When running
the executable the sanitizer correctly reports a problem with a stack
trace but the stack trace does not include funciton names and source
code line numbers (as seen in the previous link). This information
should be shown

I remember using the sanitizers about a month ago at which point I did
not encounter the problem.

I encountered a similar issue with the valgrind package which I could
fix by building valgrind from source. There is an open bug on the
valgrind package for this problem
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701480) in which a
user mentions that the problem is related to binutils.


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

Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages clang-6.0 depends on:
ii  binutils 2.31.1-1
ii  libc62.27-5
ii  libc6-dev2.27-5
ii  libclang-common-6.0-dev  1:6.0.1-2
ii  libclang1-6.01:6.0.1-2
ii  libgcc-7-dev 7.3.0-25
ii  libgcc1  1:8.1.0-10
ii  libjsoncpp1  1.7.4-3
ii  libllvm6.0   1:6.0.1-2
ii  libobjc-7-dev7.3.0-25
ii  libstdc++-7-dev  7.3.0-25
ii  libstdc++6   8.1.0-10

Versions of packages clang-6.0 recommends:
ii  libomp-dev6.0.1-1
ii  llvm-6.0-dev  1:6.0.1-2
ii  python2.7.15-3

Versions of packages clang-6.0 suggests:
pn  clang-6.0-doc  
pn  gnustep
pn  gnustep-devel  

-- no debconf information

Bug#904455: r-cran-rredlist: autopkgtest regression: there is no package called 'vcr'

[Paul Gevers]

Source: r-cran-rredlist
Version: 0.5.0-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With the upload of version 0.5.0-1, your package started to fail its
autopkgtest. I copied the output below.

Could you please investigate? Does the test or the package miss a (test)
dependency? Currently this failure is delaying the migration to testing
by 13 days.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-rredlist/662706/log.gz

> test_check("rredlist")
Loading required package: rredlist
Error in library("vcr") : there is no package called 'vcr'
Calls: test_check ... source_dir -> lapply -> FUN -> eval -> eval -> library
Execution halted



signature.asc
Description: OpenPGP digital signature

Bug#904454: python-stem: please build a package for pypy

[Iain R. Learmonth]

Package: python-stem
Version: 1.6.0-2
Severity: wishlist

Hi,

Please build a pypy package for stem. This will have to happen after the next
upstream release due to tor#26207 [0].

I have attached a patch for the control and rules file. Feel free to
ignore it if you prefer to implement this differently.

I am looking at packaging for vanguards [1] and this blocks that work.

Thanks,
Iain.

[0] https://trac.torproject.org/projects/tor/ticket/26207
[1] https://github.com/mikeperry-tor/vanguards
diff --git a/debian/control b/debian/control
index 2632df1..4b7906a 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: python-stem
 Section: python
 Priority: optional
 Maintainer: Ulises Vitulli 
-Build-Depends: debhelper (>= 9), python-all (>= 2.6.6-6), python3-all, 
dh-python
+Build-Depends: debhelper (>= 9), python-all (>= 2.6.6-6), python3-all, pypy, 
dh-python
 Standards-Version: 4.1.1.1
 Homepage: https://gitweb.torproject.org/stem.git
 X-Python-Version: >= 2.7
@@ -26,3 +26,11 @@ Description: Tor control library for Python 3 series
  Stem is a Python controller library for Tor. With it you can use
  Tor's control protocol to script against the Tor process and read
  descriptor data relays publish about themselves.
+
+Package: pypy-stem
+Architecture: all
+Depends: ${pypy:Depends}, ${misc:Depends}
+Description: Tor control library for PyPy
+ Stem is a Python controller library for Tor. With it you can use
+ Tor's control protocol to script against the Tor process and read
+ descriptor data relays publish about themselves.
diff --git a/debian/rules b/debian/rules
index 992ed9e..bb02423 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,7 +6,7 @@ export DH_VERBOSE=1
 export PYBUILD_NAME=stem
 
 %:
-   dh $@ --with python2,python3  --buildsystem=pybuild
+   dh $@ --with python2,python3,pypy  --buildsystem=pybuild
 
 override_dh_auto_clean:
dh_auto_clean

Bug#904393: qemu-kvm: CLOCK_MONOTONIC jumps during suspend of the host Linux

[Michael Tokarev]

24.07.2018 02:26, Ryutaroh Matsumoto пишет:
> Package: qemu-kvm
> Version: 1:2.12+dfsg-3
> Severity: normal
> 
> Dear Maintainer,
> 
> CLOCK_MONOTONIC should not jump during sleep, according to the systemd 
> developer
> https://github.com/systemd/systemd/issues/9538#issuecomment-405901335

It is best to address this upstream. Due to too specific of an issue I highly
doubt I'll be able to act on this bugreport in any sensible way, even checking
if the bug is still present after new qemu version is problematic.

Thanks,

/mjt

Bug#904453: python3-sleekxmpp: Syntax error on installation with Python 3.7

[Dominik George]

Package: python3-sleekxmpp
Version: 1.3.3-3
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The code uses reserved keywords as funtion names:

  File "/usr/lib/python3/dist-packages/sleekxmpp/plugins/xep_0009/remote.py", 
line 430
def async(self, callback):
^
SyntaxError: invalid syntax


async cannot be a name in Python 3.7 and onwards, thus installation fails
with Python 3.7 as default python3.


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

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), 
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:da:sv (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-sleekxmpp depends on:
ii  libjs-sphinxdoc 1.7.6-1
ii  python3 3.6.6-1
ii  python3-dnspython   1.15.0-1
ii  python3-pyasn1  0.4.2-3
ii  python3-pyasn1-modules  0.2.1-0.2

Versions of packages python3-sleekxmpp recommends:
ii  python3-dateutil  2.6.1-1
ii  python3-gnupg 0.4.3-1
ii  python3-socks 1.6.5-1

python3-sleekxmpp suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKJBAEBCABzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAltXLGUxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTylixPD/9mwqzw
5Swn5xlv07vLxogI7JKJu/9ZS/J/eH2N7HF4+kS7UtNwpb9MpyM+u2aTm+4HXGje
Rth48S8zL0mv/6jRonmeuM6AhbGzpX4l58iDWX7N+q9mcnVmUjpm3XEr7TstfaHl
V2Zf4FPRDs7S59+fVBYoEzYDqHaBRd3jE81rx6BRxY3vgscw7Og1NRJk8eubTBmT
P57b8j4EEluJJXS6eEj5+AT8OymaYaPOcaV0STiici5Ugtc8PvauumcEnjnICbCa
SY1uqY+A5oHET61Js3lmZP7VfDngt4hJNJpos4tRWjg4WJWPE12Ml+fdRMIBqEvE
WutpIL4tHCC8mBaXXk1w2EN6J7bXegtZLAr8QbbG20yW9Qmhedg//rIeVuBWrZFR
3W/g5Xm2RGrOMdrSHw/VPTXwxrtqNULT2tnaOf6gd2ioHjrfRiMqopJ4QC5jUBsn
ymnfP0ZqPsNynLcaJ+Re/UvllQJVafvV34Ag+ufBg5UtkZMaLAJB7gPCzEOJoMwv
SLwSRV6xmmlmy1P21AQP56yrZXwUpaSo4Oju4Mb/Vvwyz7OW362qRM7giS6SWP6I
q+JYR+YhWzkLdsY1V3HMk15FYyPzIHdyYn0v1hfWl/4zYDLYUNwwcAhHKeV0dQ47
q9Z93A9opg0Us01ipSI4UXwkBr0SiAhgI1OjQA==
=6M3H
-END PGP SIGNATURE-

Bug#901943: Bug is forwarded and fixed upstream

[Andrius Merkys]

Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86278
Control: tags -1 + fixed-upstream

Bug#901943: (no subject)

[Andrius Merkys]

Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86278
Control: tags -1 + fixed-upstream

Bug#904452: pango1.0: flaky autopkgtest: pango_layout_set_markup_with_accel: Error on line 2 char 28

[Paul Gevers]

Source: pango1.0
Version: 1.42.1-1
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

While inspecting regressions in autopkgtest results¹, I noticed that
your package failed multiple times² without apparent changes and passed
later again. Recent cases had the error that I copied below, I haven't
checked older history. The last regression was involved in delaying
the migration of fribidi.

Could you please investigate and make your autopkgtest more robust?
Please contact me if you need help and you think I can provide that (I
am not subscribed to this bug). Note that we recently added the "flaky"
restriction to autopkgtest. If you can't really fix the test, but still
want it run, you can mark it as not suitable for gating.

Recent discussion of gating migration by autopkgtests on debian-devel³
noted that if this is going to work, and in particular if we are going
to *block* migration when it causes autopkgtest regressions rather than
merely delaying it, intermittent autopkgtest failures are likely to have
to be considered RC due to their impact on the tested package's
dependencies and time unaware people are going to waist on looking into
the issue; for now I've filed it as important.

Paul

¹ https://ci.debian.net/packages/p/pango1.0
²
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pango1.0/610952/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pango1.0/662717/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pango1.0/331745/log.gz
³ https://lists.debian.org/debian-devel/2018/05/msg00061.html

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pango1.0/610952/log.gz

/layout/valid-1.markup:
(/usr/lib/pango1.0/installed-tests/pango/test-layout:1983):
Pango-WARNING **: 09:16:42.416: pango_layout_set_markup_with_accel:
Error on line 2 char 28: Invalid UTF-8 encoded text in name - not valid
'\xf0U<'
FAIL: pango/test-layout.test (Child process killed by signal 5)

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pango1.0/662717/log.gz

/layout/valid-1.markup:
(/usr/lib/pango1.0/installed-tests/pango/test-layout:1987):
Pango-WARNING **: 09:15:23.974: pango_layout_set_markup_with_accel:
Error on line 2 char 28: 'VU<' is not a valid name: '<'
FAIL: pango/test-layout.test (Child process killed by signal 5)



signature.asc
Description: OpenPGP digital signature

Bug#904450: libredis-fast-perl: Incomplete debian/copyright?

[Chris Lamb]

Source: libredis-fast-perl
Version: 0.21-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Marc Haber 

Hi,

I just ACCEPTed libredis-fast-perl from NEW but noticed it was 
missing attribution in debian/copyright for at least the hiredis
code copy under "deps".

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload. :)


Regards,

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

Bug#904449: Forward BTS mails to tracker.debian.org, not packages.qa.debian.org

[Raphael Hertzog]

Package: bugs.debian.org
Severity: important

Hello Don, it's been multiple years since I announced the need to
use tracker.debian.org instead of packages.qa.debian.org to forward
mails to package tracker subscribers:
https://lists.debian.org/debian-devel-announce/2015/12/msg1.html

We discussed this last year before DebConf and you planned to work on
it during DebConf, alas nothing happened. I'm now filing a bug report
to have a trace of former discussions and considerations.

I won't be at DebConf this year either but I'd love to see this fixed
in the not-too-distant future.

[2017-06-20 16:41:39]  People keep asking me about an "official switch" 
from packages.qa to tracker.d.o but for me the switch is done, it's just that 
the BTS and packages.d.o are the last services linking to it
[2017-06-20 16:43:49]  OK; does tracker.debian.org also now 
handle subscriptions? Or is tha t still packages.qa.debian.org?
[2017-06-20 16:44:34]  tracker.d.o handles all the subscriptions and all 
the mails, yes
[2017-06-20 16:44:57]  awesome; that's super easy then.
[2017-06-20 16:45:38]  In what way was that question relevant? Is there 
some way the BTS is relying on PTS subscriptions?
[2017-06-20 16:46:01]  the BTS sends emails to 
p...@packages.qa.debian.org
[2017-06-20 16:46:17]  so now it will instead send to 
p...@tracker.debian.org
[2017-06-20 16:46:34]  Please send it to dispa...@tracker.debian.org.
[2017-06-20 16:46:38]  uh...
[2017-06-20 16:47:19]  Or dispatch+@tracker.debian.org if you 
really want to indicate the source package, but the code figures it out already 
with the headers that you are adding.
[2017-06-20 16:48:11]  ah; OK. this is going to require some 
engineering time
[2017-06-20 16:48:14]  sorry. :(
[2017-06-20 16:48:29]  
https://lists.debian.org/debian-devel-announce/2015/12/msg1.html 
[2017-06-20 16:49:20]  got it; thanks
[2017-06-20 16:51:09]  I'll try to work on that shortly
[2017-06-20 16:51:10]  In that case, can you please update the web links 
quickly and handle the mail part when you have more time?
[2017-06-20 16:51:20]  they're combined
[2017-06-20 16:51:24]  ah, ok
[2017-06-20 16:51:59]  probably should fix that so they're not too
[2017-06-20 16:54:51]  How do you feel about not handling the list of 
maintainers yourself so that you would only send mails to a generic email 
instead of the email documented in Maintainer?
[2017-06-20 16:55:39]  * buxy would like to get rid of the discrepancy between 
maintainers and uploaders and handle all subscriptions at the package tracker 
level
[2017-06-20 16:58:51]  I'll have to keep the feature, but we 
could certainly make it configurable
[2017-06-20 16:59:37]  are you going to be at debconf?
[2017-06-20 16:59:50]  Cool. No, not this year unfortunately.
[2017-06-20 16:59:54]  ah, ok.
[2017-06-20 17:00:33]  might be good to hash out a plan to 
migrate to that so maintainers/developers/interested parties can manage their 
package subscriptions in a single place
[2017-06-20 17:03:40]  definitely, http://dep.debian.net/deps/dep2/ could 
be it but the scope I gave it a long-long-time ago is a bit large 
[2017-06-20 17:10:28]  makes sense
[2017-06-20 17:10:45]  I'll try to figure that all out, and if I 
have questions, I'll bug you
[2017-06-22 03:44:35]  thinking about this some more, is there 
any reason why you couldn't just subscribe to debian-bugs-dist?
[2017-06-22 03:45:09]  then I could just change the link on the 
web page, disable the Cc: to pack...@packages.qa.debian.org, and wham-bam, 
we're done.
[2017-06-22 08:57:06]  I don't think it's that easy. How are handled 
mails which are cced to multiple bugs on different packages? or those that are 
control replies affecting multiple packages?
[2017-06-22 08:58:33]  Hum, if we have X-Debian-PR-Source with all the 
sources packages, then it would work, yes.
[2017-06-22 08:58:46]  I already coded distro tracker that way.
[2017-06-22 08:59:10]  But then we need a single copy of the mail with 
multiple values in that field.
[2017-06-22 21:40:15]  hrm; I'll have to double check that; I 
don't know of those mails get all of the headers.


FWIW I'm not a big fan of having an explicit mail subscription, the subscription
could be ended by a malicious request or by some  automatic bounce handling in
case we have a temporary mail configuration issue. And at that point we will
take a lot of time to remember that there is a subscription and to figure out
that the subscription is in fact gone.

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#904337: neovim: and not working any more

[James McCoy]

Control: reassign -1 src:ncurses 6.1+20180714-1
Control: retitle -1 Incompatible change of extended storage format in terminfo 
db
Control: affects -1 libunibilium4 neovim

On Mon, Jul 23, 2018 at 02:50:50PM +0200, Philipp Marek wrote:
> Since today morning (this update)  and  do not work in neovim
> any more. In another tmux window, or suspending neovim and trying on the
> bash commandline, makes both work.
> 
> The keys are broken in Insert, Cmdline, and Normal mode.

This is due to the terminfo db changing the format of extended storage
section of the db, where extended capabilities are stored.  That broke
unibilium's parsing of the db, since it's validation of the headers
fails.

Ironically, the change in format was prompted by comments that upstream
saw in unibilium's source code.

If this change is going to stay, then I have a patch I can apply to
unibilium to adapt to the new format.  However, the change is to remove
one of the consistency checks since the new format requires not only
header data but also parsing one of the offset lists to make the same
sort of consistency check that was being performed.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#903514: Related to openblas?

[Benedict Geihe]

Hi all!

 

I was following this report as I had exactly the same issue. Then i found this

 

https://bbs.archlinux.org/viewtopic.php?id=238684

 

Indeed I had upgraded openblas recently and switching to the common blas, lapack solved the issue for me.

 

Bug#904448: Make requests to read the documentation friendlier

[Sean Whitton]

Package: dgit
Version: 5.10

Hello,

Both at this year's DebConf and at last year's, a potential user of dgit
told me that they found it very offputting when they found themselves in
a dgit corner case and dgit told them to "RTFM".

I think we could do better, e.g.

You have found yourself in a dgit corner case, but don't worry, the
docs explain what you need to do.  Please dig into dgit(1) 

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#897736: dbusada: ftbfs with GCC-8

[Nicolas Boulenguez]

Hello.
The attachment contains the same suggestions,
presented as commits to the two branches for your convenience.
The problem in tests was caused by ahven and has been fixed there.


dbusada-commits.tar.gz
Description: application/gzip

Bug#904447: mirror submission for repo.ialab.dsu.edu

[DSU-IALab]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: repo.ialab.dsu.edu
Type: leaf
Archive-architecture: amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386
Archive-http: /debian/
Maintainer: DSU-IALab 
Country: US United States
Location: Madison, SD
Sponsor: Daktoa State University https://dsu.edu




Trace Url: http://repo.ialab.dsu.edu/debian/project/trace/
Trace Url: http://repo.ialab.dsu.edu/debian/project/trace/ftp-master.debian.org
Trace Url: http://repo.ialab.dsu.edu/debian/project/trace/repo.ialab.dsu.edu

Bug#904446: (no subject)

[Sylvestre Ledru]

severity 904446 normal
thanks

Hello

I don't know about that (and it is just a warning, so, I won't investigate...)
But this isn't an "important" bug, just a normal one.

Sorry,
Sylvestre

Bug#702744: autocad dxf

[Gürkan Myczko]

i guess this bug should get closed:

according to the current cad magic file the mentioned versions are all 
supported

https://github.com/file/file/blob/f41622e34563337e0be2a501c3e3947decb3c5a7/magic/Magdir/cad

thanks,

Bug#904332: Enable Linux capabilities support

[Paul Gevers]

Hi Sven,

On 23-07-18 13:31, Sven Hartge wrote:
> Please enable support for Linux capabilities in spine.

Thanks for the suggestion.

> This is useful so one can use the "ICMP Ping" uptime checker in spine
> without needing to set spine setuid-root, just cap_net_raw is enough to
> get this working.

Sounds cool. I have zero knowledge of Linux capabilities though. Could
you provide a link to some good (for the noob) documentation on this?

> Currently this is not enabled because libcap-dev is missing as
> build-dependency.

Is that all that's needed?

> An additional dependency on libcap2-bin is necessary to allow "setcap
> cap_net_raw+ep /usr/sbin/spine" to work in postinst.

Can you elaborate? I guess you mean the binary package needs that
dependency manually added by me. And I guess that I should add some code
to the postinst. Where should it go (or doesn't it matter)? Any
drawbacks of doing this for all systems?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#904446: clang-6.0: fails to link a sanitized binary with gold

[Sylvain Joubert]

Package: clang-6.0
Version: 1:6.0.1-2
Severity: important

Dear Maintainer,

First, I'm not really sure clang is at fault here since this issue requires a
specific combination involving the clang++ compiler, the gold linker and the
sanitizers options.
Basically, with a specific combination of these tools the link step produces a
warning, which may result in a link error if '-Wl,--fatal-warnings' is used.

  $ cat main.cpp
  int main(){ return 0; }

  $ /usr/bin/clang++-6.0 -o main.o -c main.cpp -fsanitize=address

  $ /usr/bin/clang++-6.0 -o main main.o -fsanitize=address -fuse-ld=gold
  /usr/bin/ld.gold: warning: discarding version information for
__libc_stack_end@GLIBC_2.2.5, defined in unused shared library
/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 (linked with --as-needed)

* Using clang-6.0 (as a C compiler) or clang++-7 (1:7~svn331965-1) does not
solve the issue
* Using g++-8 instead of clang++-6.0 works fine
* Using '-fuse-ld=bfd', '-fuse-ld=lld' or no flags (bfd default) works fine
* Using another ('undefined', 'thread' or 'memory') sanitizer is also broken
while no sanitizers works fine

Sylvain



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'stable-updates'), (800, 'stable'), (700, 
'unstable'), (90, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages clang-6.0 depends on:
ii  binutils 2.31.1-1
ii  libc62.27-5
ii  libc6-dev2.27-5
ii  libclang-common-6.0-dev  1:6.0.1-2
ii  libclang1-6.01:6.0.1-2
ii  libgcc-7-dev 7.3.0-25
ii  libgcc1  1:8.1.0-10
ii  libjsoncpp1  1.7.4-3
ii  libllvm6.0   1:6.0.1-2
ii  libobjc-7-dev7.3.0-25
ii  libstdc++-7-dev  7.3.0-25
ii  libstdc++6   8.1.0-10

Versions of packages clang-6.0 recommends:
ii  libomp-dev6.0.1-1
ii  llvm-6.0-dev  1:6.0.1-2
ii  python2.7.15-3

Versions of packages clang-6.0 suggests:
pn  clang-6.0-doc  
pn  gnustep
pn  gnustep-devel  

-- no debconf information

Bug#904445: haskell-src-exts: use xgot for mips64/mips64r6el/mips64r6el

[YunQiang Su]

Package: src:haskell-src-exts
Version: 1.20.2-2

mips64/mips64r6/mips64r6el also need -mxgot option.
Please add them to debian/rules

-- 
YunQiang Su

Bug#904417: [Pkg-utopia-maintainers] Bug#904417: Fwd: Bug#904417: network-manager fails to check connectivity and fills disk

[Michael Biebl]

Control: reassign 903996 network-manager
Control: forcemerge -1 903996

Am 24.07.2018 um 13:49 schrieb Marko Samirić:
> Hi
> 
> I have the same issue on two installations and used workaround by
> disabling connectivity check until this is getting fixed.
> 
> sudo tee /etc/NetworkManager/conf.d/connectivity.conf << EOF > /dev/null
> [connectivity]
> uri=""
> interval=0
> EOF

Simply uninstalling the network-manager-config-connectivity-debian
package in this case might be a better idea.




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



signature.asc
Description: OpenPGP digital signature

Bug#904444: trnascan-se: FTBFS during arch-indep build

[Andreas Beckmann]

Source: trnascan-se
Version: 2.0.0-1
Severity: serious
Justification: fails to build from source

Hi,

trnascan-se FTBFS when built with dpkg-buildpackage -A:

   dh_auto_build -i
make -j4
make[1]: Entering directory '/build/trnascan-se-2.0.0'
make  all-am
make[2]: Entering directory '/build/trnascan-se-2.0.0'
sed -e 's,\@bindir\@,/usr/bin,g' -e 's,\@pkgdatadir\@,/usr/share/trnascan-se,g' 
-e 's,[@]PERL[@],/usr/bin/perl,g' -e 's,\@INFERNAL\@,,g' -e 
's,\@sysconfdir\@,/etc,g' < ./src/sstofa.in > bin/sstofa
sed -e 's,\@bindir\@,/usr/bin,g' -e 's,\@pkgdatadir\@,/usr/share/trnascan-se,g' 
-e 's,[@]PERL[@],/usr/bin/perl,g' -e 's,\@INFERNAL\@,,g' -e 
's,\@sysconfdir\@,/etc,g' < ./src/fasta2gsi.in > bin/fasta2gsi
/bin/bash: bin/sstofa: No such file or directory
make[2]: *** [Makefile:1102: bin/sstofa] Error 1


Andreas


trnascan-se_2.0.0-1_indep.log.gz
Description: application/gzip

Bug#903972: [nico...@debian.org: update of pcscada]

[Nicolas Boulenguez]

Hello.

The attachment replaces the previous pcscada.tar.gz. It should be more
convenient since the changes are commits to the master branch instead
of commits to the debian branch creating debian/patches/*.diff.

Please review the patches for the master branch, edit and commit the
ones you approve.

If you release a new upstream version, please use tar --exclude-vcs
option in order to stop embedding .gitignore and similar files into
the released archive.
Else, transforming git commits back into debian/patches/ should be easy.


pcscada-commits.tar.gz
Description: application/gzip

Bug#904417: Fwd: Bug#904417: network-manager fails to check connectivity and fills disk

[Marko Samirić]

Hi

I have the same issue on two installations and used workaround by disabling
connectivity check until this is getting fixed.

sudo tee /etc/NetworkManager/conf.d/connectivity.conf << EOF > /dev/null
[connectivity]
uri=""
interval=0
EOF

best regards
Marko Samirić

Bug#828050: firefox-esr: Can not set default homepage

[Leszek Lesner]

The issue seems to be more severe.

Firefox-esr is basically ignoring the whole /etc/firefox-esr directory
altogether.

So even the firefox-esr.js settings aren't loaded.

Linking /etc/firefox-esr to
/usr/lib/firefox-esr/brower/defaults/preferences makes those configs
work again.

Issue still happens with 52.9.0esr-1

Hope that helps finding and fixing the issue.


Greetings

Leszek Lesner

-- 
ZevenOS / Neptune Team
https://neptuneos.com
Leszek Lesner 

Bug#904443: RFP: python3-asciitree -- draw tree structures using (ASCII or Unicode) characters

[Thorsten Glaser]

Package: wnpp
Severity: wishlist

* Package name: python3-asciitree
  Version : 0.3.3
  Upstream Author : Marc Brinkmann 
* URL : g...@github.com:mbr/asciitree.git
* Licence : MIT
  Programming Lang: Python 2/3
  Description : draw tree structures using (ASCII or Unicode) characters

 This package contains functions to draw a tree structure,
 similar to the tree Debian package, from arbitrary nested
 Python data structures, with configurable layout, sets of
 characters (ASCII or various Unicode line drawing), etc.
 It includes predefined structure traversal methods for
 (optionally ordered) dictionaries but allows the user to
 write their own to traverse custom data structures.

This was recently very helpful at $dayjob, and it would be
good to have it in Debian, although I do not intend to maintain
it myself a coworker will surely (*wink*) since it probably
can be done on the clock.

The documentation included in the package itself is extremely
sparse; there’s a link to https://pythonhosted.org/asciitree/
(the contents of which I’d suggest including in the binary
package under /usr/share/doc/ somewhere), but I had to look
into the source to figure out how to best use it.

Bug#904442: gnome-shell-extension-system-monitor: fills system journal with errors about accessing Schema object

[Pedro Ângelo]

Package: gnome-shell-extension-system-monitor
Version: 35-1
Severity: normal

Dear Maintainer,

although the extension appears to work normally, gnome-shell is
continuously sending the attached messages to the system journal.

These seem to be related to accesses to the Schema object which is
initialised on line 2233 in extension.js. 

Please let me know if I can be of any further assistance.

Best regards,
P.

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

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

Versions of packages gnome-shell-extension-system-monitor depends on:
ii  gir1.2-clutter-1.0  1.26.2+dfsg-4
ii  gir1.2-gtop-2.0 2.38.0-2
ii  gnome-shell 3.28.2-2

gnome-shell-extension-system-monitor recommends no packages.

gnome-shell-extension-system-monitor suggests no packages.

-- no debconf information

Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: == Stack trace for context 
0x55aa9ef90330 ==
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #0 0x55aa9f36f7c0 i   
/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1936
 (0x7fe1541e2918 @ 39)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #1 0x7ffd153332a0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe1704b5de0 @ 71)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #2 0x7ffd15333a90 b   
/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:928
 (0x7fe1541deb38 @ 70)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #3 0x7ffd15333b50 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe1704b5de0 @ 71)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #4 0x7ffd15333c00 b   
self-hosted:913 (0x7fe1704f1230 @ 346)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: == Stack trace for context 
0x55aa9ef90330 ==
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #0 0x55aa9f36f7c0 i   
/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1951
 (0x7fe1541e2918 @ 235)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #1 0x7ffd153332a0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe1704b5de0 @ 71)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #2 0x7ffd15333a90 b   
/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:928
 (0x7fe1541deb38 @ 70)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #3 0x7ffd15333b50 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe1704b5de0 @ 71)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #4 0x7ffd15333c00 b   
self-hosted:913 (0x7fe1704f1230 @ 346)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: == Stack trace for context 
0x55aa9ef90330 ==
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #0 0x55aa9f36f7c0 i   
/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1957
 (0x7fe1541e2a28 @ 83)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #1 0x7ffd153332a0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe1704b5de0 @ 71)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #2 0x7ffd15333a90 b   
/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:929
 (0x7fe1541deb38 @ 85)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #3 0x7ffd15333b50 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe1704b5de0 @ 71)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #4 0x7ffd15333c00 b   
self-hosted:913 (0x7fe1704f1230 @ 346)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: == Stack trace for context 
0x55aa9ef90330 ==
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #0 0x55aa9f36f7c0 i   
/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:943
 (0x7fe1541dec48 @ 23)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #1 0x7ffd153332a0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe1704b5de0 @ 71)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #2 0x7ffd15333a90 b   
/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:931
 (0x7fe1541deb38 @ 121)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #3 0x7ffd15333b50 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fe1704b5de0 @ 71)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #4 0x7ffd15333c00 b   
self-hosted:913 (0x7fe1704f1230 @ 346)
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: == Stack trace for context 
0x55aa9ef90330 ==
Jul 24 12:04:40 rae org.gnome.Shell.desktop[1819]: #0 0x55aa9f36f7c0 i   
/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:2009
 (0x7fe1541e2d58 @ 39)
Jul 24 12:04:40 rae 

Bug#892953: autofs-5.1.2-3 crashes on hppa architecture

[Helge Deller]

It seems it was a generic kernel bug which was fixed between 4.17.6 and 4.17.8.

Bug#904439: fuse: CVE-2018-10906: Restriction bypass of the "allow_other" option when SELinux is active

[Salvatore Bonaccorso]

On Tue, Jul 24, 2018 at 01:12:50PM +0200, Salvatore Bonaccorso wrote:
> I have prepared an update for stretch (not yet released), although as
> said, its a problem only with active SELinux, which is not by default
> in Debian.

Attaching debdiff.

Regards,
Salvatore
diff -Nru fuse-2.9.7/debian/changelog fuse-2.9.7/debian/changelog
--- fuse-2.9.7/debian/changelog 2016-06-23 20:54:56.0 +0200
+++ fuse-2.9.7/debian/changelog 2018-07-23 20:50:41.0 +0200
@@ -1,3 +1,11 @@
+fuse (2.9.7-1+deb9u1) stretch-security; urgency=high
+
+  * Non-maintainer upload by the Security Team.
+  * Restriction bypass of the "allow_other" option when SELinux is active
+(CVE-2018-10906)
+
+ -- Salvatore Bonaccorso   Mon, 23 Jul 2018 20:50:41 +0200
+
 fuse (2.9.7-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru 
fuse-2.9.7/debian/patches/CVE-2018-10906/0001-fusermount-prevent-silent-truncation-of-mount-option.patch
 
fuse-2.9.7/debian/patches/CVE-2018-10906/0001-fusermount-prevent-silent-truncation-of-mount-option.patch
--- 
fuse-2.9.7/debian/patches/CVE-2018-10906/0001-fusermount-prevent-silent-truncation-of-mount-option.patch
1970-01-01 01:00:00.0 +0100
+++ 
fuse-2.9.7/debian/patches/CVE-2018-10906/0001-fusermount-prevent-silent-truncation-of-mount-option.patch
2018-07-23 20:50:41.0 +0200
@@ -0,0 +1,98 @@
+From: Jann Horn 
+Date: Fri, 13 Jul 2018 14:51:17 -0700
+Subject: [1/5] fusermount: prevent silent truncation of mount options
+Origin: 
https://github.com/libfuse/commit/34c62ee90c69b07998629f6b5a06ab0120be681c
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-10906
+Bug: https://github.com/libfuse/libfuse/pull/268
+
+Currently, in the kernel, copy_mount_options() copies in one page of
+userspace memory (or less if some of that memory area is not mapped).
+do_mount() then writes a null byte to the last byte of the copied page.
+This means that mount option strings longer than PAGE_SIZE-1 bytes get
+truncated silently.
+
+Therefore, this can happen:
+
+user@d9-ut:~$ _FUSE_COMMFD=1 fusermount -o "$(perl -e 'print ","x4000')" 
mount
+sending file descriptor: Bad file descriptor
+user@d9-ut:~$ grep /mount /proc/mounts
+/dev/fuse /home/user/mount fuse 
rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
+user@d9-ut:~$ fusermount -u mount
+user@d9-ut:~$ _FUSE_COMMFD=1 fusermount -o "$(perl -e 'print ","x4050')" 
mount
+sending file descriptor: Bad file descriptor
+user@d9-ut:~$ grep /mount /proc/mounts
+/dev/fuse /home/user/mount fuse 
rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0
+user@d9-ut:~$ fusermount -u mount
+user@d9-ut:~$ _FUSE_COMMFD=1 fusermount -o "$(perl -e 'print ","x4051')" 
mount
+sending file descriptor: Bad file descriptor
+user@d9-ut:~$ grep /mount /proc/mounts
+/dev/fuse /home/user/mount fuse 
rw,nosuid,nodev,relatime,user_id=1000,group_id=10 0 0
+user@d9-ut:~$ fusermount -u mount
+user@d9-ut:~$ _FUSE_COMMFD=1 fusermount -o "$(perl -e 'print ","x4052')" 
mount
+sending file descriptor: Bad file descriptor
+user@d9-ut:~$ grep /mount /proc/mounts
+/dev/fuse /home/user/mount fuse 
rw,nosuid,nodev,relatime,user_id=1000,group_id=1 0 0
+user@d9-ut:~$ fusermount -u mount
+
+I'm not aware of any context in which this is actually exploitable - you'd
+still need the UIDs to fit, and you can't do it if the three GIDs of the
+process don't match (in the case of a typical setgid binary), but it does
+look like something that should be fixed.
+
+I also plan to try to get this fixed on the kernel side.
+[carnil: Refresh patch to apply cleanly for context in 2.9.7]
+---
+ util/fusermount.c | 23 ---
+ 1 file changed, 20 insertions(+), 3 deletions(-)
+
+--- a/util/fusermount.c
 b/util/fusermount.c
+@@ -712,6 +712,23 @@ static int get_string_opt(const char *s,
+   return 1;
+ }
+ 
++/* The kernel silently truncates the "data" argument to PAGE_SIZE-1 
characters.
++ * This can be dangerous if it e.g. truncates the option "group_id=1000" to
++ * "group_id=1".
++ * This wrapper detects this case and bails out with an error.
++ */
++static int mount_notrunc(const char *source, const char *target,
++   const char *filesystemtype, unsigned long mountflags,
++   const char *data) {
++  if (strlen(data) > sysconf(_SC_PAGESIZE) - 1) {
++  fprintf(stderr, "%s: mount options too long\n", progname);
++  errno = EINVAL;
++  return -1;
++  }
++  return mount(source, target, filesystemtype, mountflags, data);
++}
++
++
+ static int do_mount(const char *mnt, char **typep, mode_t rootmode,
+   int fd, const char *opts, const char *dev, char **sourcep,
+   char **mnt_optsp, off_t rootsize)
+@@ -836,7 +853,7 @@ static int do_mount(const char *mnt, cha
+   else
+   strcpy(source, subtype ? subtype : dev);
+ 
+-  res = mount(source, mnt, type, flags, optbuf);
++  res = 

Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot

[Julian Calaby]

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

Dear Maintainer,

Linux 4.17.0-1-amd64 (4.17.8-1) causes my laptop (Thinkpad X200) to fail to
boot.

During a boot with Systemd the disk gets stopped erroneously approximately
after udev "coldplugs" anything that hasn't been autodetected already.

This causes the kernel to stop the system disk causing the machine to hang
with all SATA requests eventually timing out and all startup processes
eventually failing.

FROM MEMORY, the last disk related messages are:

sda: Synchronising SCSI cache
sda: Stopping disk

Please note that as I cannot boot that kernel, this bug report was compiled on
4.16.0-2-amd64 (4.16.16-2) instead.

Severity is relatively low as this laptop is the only computer I maintain that
has shown this behaviour (so far) which makes me think it's related to the
specific drivers I'm using, not something "generic" to this kernel version.

Please let me know if there's any further details you need about my hardware
or system configuration.

Thanks,

Julian Calaby


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

** Model information
sys_vendor: LENOVO
product_name: 7454CTO
product_version: ThinkPad X200
chassis_vendor: LENOVO
chassis_version: Not Available
bios_vendor: LENOVO
bios_version: 7XET72WW (3.22 )
board_vendor: LENOVO
board_name: 7454CTO
board_version: Not Available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub [8086:2a40] (rev 07)
Subsystem: Lenovo Mobile 4 Series Chipset Memory Controller Hub 
[17aa:20e0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series 
Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA 
controller])
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics 
Controller [17aa:20e4]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller [8086:2a43] (rev 07)
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics 
Controller [17aa:20e4]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series 
Chipset MEI Controller [8086:2a44] (rev 07)
Subsystem: Lenovo Mobile 4 Series Chipset MEI Controller [17aa:20e6]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 Ethernet controller [0200]: Intel Corporation 82567LF Gigabit Network 
Connection [8086:10bf] (rev 03)
Subsystem: Lenovo 82567LF Gigabit Network Connection [17aa:20ee]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: e1000e
Kernel modules: e1000e

00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 [8086:2937] (rev 03) (prog-if 00 [UHCI])
Subsystem: Lenovo 82801I (ICH9 Family) USB UHCI Controller [17aa:20f0]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd

00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 [8086:2938] (rev 03) (prog-if 00 [UHCI])
Subsystem: Lenovo 82801I (ICH9 Family) USB UHCI Controller [17aa:20f0]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd

00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 [8086:2939] (rev 03) (prog-if 00 [UHCI])
Subsystem: Lenovo 82801I (ICH9 Family) USB UHCI Controller [17aa:20f0]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 

Bug#904440: ITP: nsync -- C library that exports various synchronization primitives, such as mutexes [TF deps]

[lumin]

Package: wnpp
Severity: wishlist
Owner: lumin 

* Package name: nsync
  Version : 1.20.0
  Upstream Author : google
* URL : https://github.com/google/nsync
* License : Apache-2.0
  Programming Lang: C
  Description : C library that exports various synchronization primitives, 
such as mutexes

tensorflow dependency

Bug#904098: Confirmed

[Frankie Robertson]

Hi,

I can confirm this bug also occurs for me after upgrading yesterday. I am
running a Dell Inspiron 7559.

Regards,
Frankie

Bug#904439: fuse: CVE-2018-10906: Restriction bypass of the "allow_other" option when SELinux is active

[Salvatore Bonaccorso]

Source: fuse
Version: 2.9.7-1
Severity: important
Tags: patch security upstream
Forwarded: https://github.com/libfuse/libfuse/pull/268

Hi,

The following vulnerability was published for fuse.

CVE-2018-10906[0]:
Restriction bypass of the "allow_other" option when SELinux is active

To exploit it, SELinux nedds to be active (including in permissive
mode).

I have prepared an update for stretch (not yet released), although as
said, its a problem only with active SELinux, which is not by default
in Debian.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-10906
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10906
[1] https://github.com/libfuse/libfuse/pull/268
[2] https://sourceforge.net/p/fuse/mailman/message/36374753/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#904436: [pkg-apparmor] Bug#904436: apparmor-notify: aa-notify is referring to wiki.ubuntu.com by default

[Christian Boltz]

Hello,

Am Dienstag, 24. Juli 2018, 12:35:44 CEST schrieb Clément Hermann:
> aa-notify refers to wiki.ubuntu.com in the notifications.
> We should make sure it's using a debian page instead - this is
> actually configurable via message_footer in latest upstream version

Yes, this is possible now, but would mean to carry a distro-specific 
patch for notify.conf that (obviously) can never be upstreamed.

A more "boring" solution would be to change the upstream default message 
to point to a page on wiki.apparmor.net

... says the openSUSE AppArmor maintainer ;-)


Regards,

Christian Boltz
-- 
[ Yes ] [ No ]  


   
... used for harmless errors or simple questions: "It's high time you   


   
had your cup of coffee! Would you like your KDE to prepare one for you?"


   
[Lukas Ocilka in opensuse-factory - YaST2 button styleguide]


   

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

Bug#874759: vips: New release 8.5 available, project relocated to github

[Jonathan Dowland]

On Fri, Jun 08, 2018 at 12:31:45PM +0200, Sebastian Ramacher wrote:

Any news on the new upstream release? 8.5 and 8.6 has many new
interesting features that I'd like to see packaged.


Echo this, I just discovered that Debian's vips lacks "smartcrop", and I
was surprised to see how behind the package version is.

Laszlo, are you still maintaining vips?  you did a recent upload but
only for a CVE fix and 8.5 was already out at that time.  I see it's
neither in team maintenance nor are you marked LowNMU. Do you need help
with the package?


--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄

Bug#904111: [Pkg-clamav-devel] Bug#904111: Bug#904111: clamav-daemon causing deadlocks/blocking I/O.

[Scott Kitterman]

On July 24, 2018 10:42:44 AM UTC, richard lucassen  
wrote:
>On Tue, 24 Jul 2018 08:19:15 +0200
>Sebastian Andrzej Siewior  wrote:
>
>> Is the kernel complaining about something like in the other report
>> where it claimed something about a deadlock?
>
>No, no words like fanotify, deadlock or blocked appear in the logs.
>
>I blocked and upgraded one of the (production) servers. After
>upgrade clamd is running but as soon as a mail is received, it exits. I
>ran an "strace -f -p " on a running clamd and sent a mail. The
>output is here:
>
>http://tmp.xaq.nl/clamd.strace
>
>$ dpkg --get-selections | grep clam
>clamav  install
>clamav-base install
>clamav-daemon   install
>clamav-freshclaminstall
>libclamav7:i386 install
>libclamunrar7   install
>
>plus a vanilla install of clamav-unofficial-sigs.

That looks like a different issue.  Does it still happen if you remove 
clamav-unofficial-sigs?

Scott K

Bug#904438: rozofs: FTBFS during arch-indep build

[Andreas Beckmann]

Source: rozofs
Version: 2.6.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

rozofs fails while building with dpkg-buildpackage -A:

   debian/rules override_dh_install
make[1]: Entering directory '/build/rozofs-2.6.2'
dh_install -prozofs-doc --sourcedir=/build/rozofs-2.6.2/obj-x86_64-linux-gnu 
doc/users_guide_sphinx/html  /usr/share/doc/rozofs-doc
dh_install
# Manually avoid conflict with inn2 (#846571) until
# https://github.com/rozofs/rozofs/issues/142 is fixed
mv debian/rozofs-storaged/usr/share/man/man5/storage.conf.5 
debian/rozofs-storaged/usr/share/man/man5/rozofs-storage.conf.5
mv: cannot stat 'debian/rozofs-storaged/usr/share/man/man5/storage.conf.5': No 
such file or directory
make[1]: *** [debian/rules:26: override_dh_install] Error 1
make[1]: Leaving directory '/build/rozofs-2.6.2'
make: *** [debian/rules:12: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Maybe you need override_dh_install-arch instead?


Andreas


rozofs_2.6.2-1_indep.log.gz
Description: application/gzip

Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O.

[richard lucassen]

On Tue, 24 Jul 2018 08:19:15 +0200
Sebastian Andrzej Siewior  wrote:

> Is the kernel complaining about something like in the other report
> where it claimed something about a deadlock?

No, no words like fanotify, deadlock or blocked appear in the logs.

I blocked and upgraded one of the (production) servers. After
upgrade clamd is running but as soon as a mail is received, it exits. I
ran an "strace -f -p " on a running clamd and sent a mail. The
output is here:

http://tmp.xaq.nl/clamd.strace

$ dpkg --get-selections | grep clam
clamav  install
clamav-base install
clamav-daemon   install
clamav-freshclaminstall
libclamav7:i386 install
libclamunrar7   install

plus a vanilla install of clamav-unofficial-sigs.

R.

-- 
richard lucassen
http://contact.xaq.nl/

Bug#904437: Fix for pin mapping on HP EliteBook x360 1020 G2

[Enrico Zini]

Package: alsa-utils
Version: 1.1.6-1
Severity: normal

Hello,

I have this issue in my EliteBook as well:
https://ubuntuforums.org/showthread.php?t=2317239
that is, when plugging in headphones, the audio for the speakers is not
muted, only lowered a bit.

I tried hda-analyzer and generated this pin mapping fix script:

   #!/usr/bin/env python
   
   import os
   import struct
   from fcntl import ioctl
   
   def __ioctl_val(val):
 # workaround for OverFlow bug in python 2.4
 if val & 0x8000:
   return -((val^0x)+1)
 return val
   
   IOCTL_INFO = __ioctl_val(0x80dc4801)
   IOCTL_PVERSION = __ioctl_val(0x80044810)
   IOCTL_VERB_WRITE = __ioctl_val(0xc0084811)
   
   def set(nid, verb, param):
 verb = (nid << 24) | (verb << 8) | param
 res = ioctl(FD, IOCTL_VERB_WRITE, struct.pack('II', verb, 0))  
   
   FD = os.open("/dev/snd/hwC0D0", os.O_RDONLY)
   info = struct.pack('Ii64s80si64s', 0, 0, '', '', 0, '')
   res = ioctl(FD, IOCTL_INFO, info)
   name = struct.unpack('Ii64s80si64s', res)[3]
   if not name.startswith('HDA Codec'):
 raise IOError, "unknown HDA hwdep interface"
   res = ioctl(FD, IOCTL_PVERSION, struct.pack('I', 0))
   version = struct.unpack('I', res)
   if version < 0x0001: # 1.0.0
 raise IOError, "unknown HDA hwdep version"
   
   # initialization sequence starts here...
   
   set(0x17, 0x701,   0x01) # 0x17070101 (SET_CONNECT_SEL)
   
   os.close(FD)


I'd like to report this so that it can eventually make its way upstream.
I don't know what extra information to provide to that end.

I tried https://bugtrack.alsa-project.org/alsa-bug (linked from
https://bugtrack.alsa-project.org/main/index.php/Main_Page) but it gives
error 404, so I'm falling back here.


Enrico

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

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

Versions of packages alsa-utils depends on:
ii  kmod  25-1
ii  libasound21.1.6-1
ii  libc6 2.27-5
ii  libfftw3-single3  3.3.8-1
ii  libncursesw6  6.1+20180714-1
ii  libsamplerate00.1.9-2
ii  libtinfo6 6.1+20180714-1
ii  lsb-base  9.20170808
ii  whiptail  0.52.20-5

alsa-utils recommends no packages.

alsa-utils suggests no packages.

-- no debconf information

Bug#712451: Please support AppArmor network rules

[intrigeri]

intrigeri:
> John, could you please tell me how I can benefit from the network
> socket mediation feature that was merged into Linux 4.17?

John answered my question on IRC:

- "you can't yet. You will need an apparmor 3.0 beta which keeps
  getting delayed"
- "for various reasons, I won't let the network patches into the wild
  without the tie to the feature abi work"

So let's put this on the back burner until there's userspace available
to benefit from the new kernel feature.

Bug#904435: Prevent emacs-goodies-el from migrating to testing

[Sean Whitton]

Source: emacs-goodies-el
Version: 39.0
Severity: serious

The latest emacs-goodies-el is in an inconsistent state (for example,
emacs-goodies-el.texi lists packages that are no longer in the archive)
and should not be in a stable release until the breaking up has been
completed, or things like emacs-goodies-el.texi have been fixed.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904436: apparmor-notify: aa-notify is referring to wiki.ubuntu.com by default

[Clément Hermann]

Package: apparmor-notify
Version: 2.12-5
Severity: normal

aa-notify refers to wiki.ubuntu.com in the notifications.
We should make sure it's using a debian page instead - this is actually
configurable via message_footer in latest upstream version (used to be
hardcoded).

Cheers,


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

Versions of packages apparmor-notify depends on:
ii  libapparmor-perl  2.12-5
ii  libnotify-bin 0.7.7-3
ii  perl  5.26.2-6

apparmor-notify recommends no packages.

apparmor-notify suggests no packages.

-- no debconf information

Bug#712451: Please support AppArmor network rules

[intrigeri]

Hi,

(John, one question for you below, please search for your name :)

Vincas Dargis:
> On 7/22/18 3:48 PM, intrigeri wrote:
>> Vincas Dargis:
>>> I've managed to install 4.17.0-rc3 and 4.18.0-rc4 with equivs hack, and I 
>>> did not see
>>> any immediate problems with some lightweight testing.
>>
>> Great.
>>
>> Both on Stretch, right?

> Yes.

>> Did you disable feature-set pinning entirely or update the feature-set
>> to enable the new features? If the latter, can you please share the
>> exact feature-set you've used?

> I have feature-set commented out.

OK!

I'm now running 4.17 from sid without feature set pinning and did not
notice any breakage either.

*But* I don't think that just upgrading to 4.17 actually gives me
network socket mediation. I have this in parser.conf:

  warn=rule-not-enforced
  warn=rule-downgraded

… and when compiling policy, I see "network rules not enforced" all
over the place.

Then I've read somewhere that network socket mediation might need
newer userspace (I'm running 2.13 from Debian experimental).

John, could you please tell me how I can benefit from the network
socket mediation feature that was merged into Linux 4.17?

>>> Though it would be really nice to have some sort of integration test suite 
>>> for
>>> apparmor-confined packages to do some serious testing before releasing 
>>> upgrades...
>>
>> Absolutely.

> Does Debian packages has infrastructure for integration tests that maintainer 
> could run after building?

Yes: autopkgtest. If you're interested in working on this, please
start a dedicated thread on the team ML or on a new bug report :)

Cheers,
-- 
intrigeri

Bug#904433: tesseract-ocr: please mark as Multi-Arch: foreign

[Yuriy M. Kaminskiy]

Package: tesseract-ocr
Version: 4.00~git2481-555f6ffc-1
Severity: normal
Tags: patch

Dear Maintainer,

tesseract-ocr package provides arch-independent service (cli), please
mark it as Multi-Arch: foreign; (trivial) patch attached.

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'stable')

Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R), 
LANGUAGE=ru_RU.KOI8-R (charmap=KOI8-R)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tesseract-ocr depends on:
ii  libc62.24-11+deb9u3
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libglib2.0-0 2.50.3-2
ii  libgomp1 6.3.0-18+deb9u1
ii  libicu57 57.1-6+deb9u2
ii  liblept5 1.74.1-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libstdc++6   6.3.0-18+deb9u1
ii  libtesseract44.00~git2439-c3ed6f03-1~bpo9+1
ii  tesseract-ocr-eng4.00~git28-f7a4c12-1~bpo9+1
ii  tesseract-ocr-osd4.00~git28-f7a4c12-1~bpo9+1

tesseract-ocr recommends no packages.

tesseract-ocr suggests no packages.

-- no debconf information

--- tesseract_4.00~git2481-555f6ffc-1.debian/debian/control.orig
2018-05-22 07:30:43.0 +0300
+++ tesseract_4.00~git2481-555f6ffc-1.debian/debian/control 2018-07-24 
12:01:39.965380307 +0300
@@ -13,6 +13,7 @@
 
 Package: tesseract-ocr
 Architecture: any
+Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends},
  tesseract-ocr-eng (>= 4.00~), tesseract-ocr-osd (>= 4.00~), libtesseract4 (>= 
4.00~)
 Replaces: tesseract-ocr-data
@@ -87,6 +88,7 @@
 
 Package: tesseract-ocr-all
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}, tesseract-ocr,
 tesseract-ocr-bul, tesseract-ocr-cat, tesseract-ocr-ces, 
tesseract-ocr-dan,
 tesseract-ocr-deu, tesseract-ocr-ell, tesseract-ocr-eng, 
tesseract-ocr-fin,

Bug#904432: devscripts: bts: unable to download mbox from debbugs.gnu.org

[Vagrant Cascadian]

Package: devscripts
Version: 2.18.3
Severity: normal

I am unable to download the mbox for bugs from debbugs.gnu.org:

  $ bts --bts-server=https://debbugs.gnu.org --mbox --mailreader 'true %s' show 
22883
  bts: could not read mbox file 
/tmp/tmp.EqlaeupuPL/.cache/devscripts/bts/22883.mbox!

Without using --mbox, it attempts to open a browser and works fine.

I've tested both with the devscripts version in backports and sid, and
they behave the same.


live well,
  vagrant

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
Not present

-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (500, 'stable'), (120, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, arm64

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

Versions of packages devscripts depends on:
ii  dpkg-dev  1.18.25
ii  libc6 2.24-11+deb9u3
ii  libfile-homedir-perl  1.00-1
ii  perl  5.24.1-3+deb9u4
ii  python3   3.5.3-1
ii  sensible-utils0.0.9+deb9u1

Versions of packages devscripts recommends:
ii  apt 1.4.8
ii  at  3.1.20-3
ii  curl7.52.1-5+deb9u6
ii  dctrl-tools 2.24-2+b1
ii  debian-keyring  2018.06.24
ii  dput-ng [dput]  1.13+deb9u1
ii  equivs  2.0.9+nmu1
ii  fakeroot1.21-3.1
ii  file1:5.30-1+deb9u2
ii  gnupg   2.1.18-8~deb9u2
ii  gnupg2  2.1.18-8~deb9u2
ii  libdistro-info-perl 0.14
ii  libdpkg-perl1.18.25
ii  libencode-locale-perl   1.05-1
ii  libgit-wrapper-perl 0.047-1
ii  liblist-compare-perl0.53-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.20-1
ii  libstring-shellquote-perl   1.03-1.2
ii  libtry-tiny-perl0.28-1
ii  liburi-perl 1.71-1
ii  libwww-perl 6.15-1
ii  licensecheck3.0.29-1
ii  lintian 2.5.88~bpo9+1
ii  man-db  2.7.6.1-2
ii  patch   2.7.5-1+deb9u1
ii  patchutils  0.3.4-2
ii  python3-apt 1.4.0~beta3
ii  python3-debian  0.1.30
ii  python3-magic   1:5.30-1+deb9u2
ii  python3-requests2.12.4-1
pn  python3-unidiff 
ii  python3-xdg 0.25-4
ii  strace  4.15-2
ii  unzip   6.0-21
ii  wdiff   1.2.2-2
ii  wget1.18-5+deb9u2
ii  xz-utils5.2.2-1.2+b1

Versions of packages devscripts suggests:
pn  adequate 
ii  autopkgtest  4.4
pn  bls-standalone   
ii  bsd-mailx [mailx]8.1.2-0.20160123cvs-4
ii  build-essential  12.3
pn  check-all-the-things 
pn  cvs-buildpackage 
pn  devscripts-el
pn  diffoscope   
pn  disorderfs   
ii  dose-extra   5.0.1-8+deb9u1
pn  duck 
pn  faketime 
pn  gnuplot  
ii  gpgv 2.1.18-8~deb9u2
pn  how-can-i-help   
ii  libauthen-sasl-perl  2.1600-1
ii  libfile-desktopentry-perl0.22-1
pn  libnet-smtps-perl
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
pn  mozilla-devscripts   
ii  mutt 1.7.2-1
ii  openssh-client [ssh-client]  1:7.4p1-10+deb9u3
pn  piuparts 
pn  postgresql-client
ii  quilt0.63-8
pn  ratt 
pn  reprotest
pn  svn-buildpackage 
ii  w3m  0.5.3-34+deb9u1

-- no debconf information


signature.asc
Description: PGP signature

Bug#848256: lastpass-cli: lpass segfaults attempting to log in

[Chris Lamb]

Chris Lamb wrote:

> > lastpass-cli: lpass segfaults attempting to log in
> 
> Can you folks reproduce this in lastpass-cli 1.3.1?

Gentle ping on this? I cannot reproduce it.


Best wishes,

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

Bug#904430: thunderbird: Saved passwords lost after upgrading from 1:52.9.1-1 to 60.0~b10-1 and Thunderbird won't ask password it needs

[intrigeri]

Package: thunderbird
Version: 1:60.0~b10-1
Severity: normal

Hi,

I've upgraded to thunderbird/experimental and Thunderbird does not
manage to download nor send email:

 - When trying to receive email I see "connected to $server" in the
   status bar, netstat confirms a TCP connection is open, but nothing
   else happens AFAICT.

 - When trying to send email, I see an error dialog that tells me that
   Thunderbird does not know any password for my SMTP account. But it
   won't ask me what the password is.

 - The Thunderbird password manager indeed lists no password. It does
   not seem to allow me to add any.

 - Atom/RSS feeds work just fine.

I've disabled AppArmor confinement but that does not help. I see no
AppArmor denials in my logs that would indicate it broke some
migration process.

I've tried to create a minimal reproducer (create an account with
thunderbird 52.9.1, upgrade to 60.0~b10) but failed: I mean that
worked just fine. Hence severity = normal.

So I have two questions:

1. How can I fix that problem for my specific situation? Is there
   a file I should move away or something, to reset what seems to be
   badly migrated state?

2. Do you think we should debug this further, in case it affects other
   people as well? If you do, then I'll need instructions :)

Cheers,
-- 
intrigeri

Bug#904431: ahven: Incomplete debian/copyright?

[Chris Lamb]

Source: ahven
Version: 2.7~1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Nicolas Boulenguez 

Hi,

I just ACCEPTed ahven from NEW but noticed it was missing attribution 
in debian/copyright for at least gnat_linux/comfignat*.

(This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

[Yuri D'Elia]

Package: apt
Version: 1.6.3
Followup-For: Bug #879786

I second that apt-secure should mention the use of "apt" and, in detail,
"apt-get --allow-releaseinfo-change" as well (pointing to apt-get for
more details on the various finger-graned flags) since the manpage of
apt(1) doesn't include any relevant information on metadata changes.

I don't ever use "apt", I mostly use "aptitude" or directly "apt-get"
when needed. aptitude doesn't have support for prompting for releaseinfo
changes, and apt-get does neither. The error message is somewhat
puzzling, since apt-secure(8) contains mostly redundand information for
those who know already something about the signing infrastructure and
just want to acknowledge the change.

Thanks.

Bug#900210: thunderbird: Thunderbird AppArmor config disables ability to send entirely

[intrigeri]

Control: retitle -1 Thunderbird AppArmor config breaks stuff with custom $TMPDIR
Control: severity -1 minor

(Retitling to clarify which condition is needed to trigger the bug,
downgrading severity as this AppArmor profile is disabled by default.)

Bug#892058: debian-keyring: please automatically send reminder emails to people whose keys will expire soon

[Markus Koschany]

Hello,

On Mon, 5 Mar 2018 10:04:22 + Jonathan McDowell 
wrote:
> On Sun, Mar 04, 2018 at 08:02:35PM +0100, Ximin Luo wrote:
> 
> > For security, I set a short validity period on my key and renew this
> > every year by repeatedly extending the expiry date. However I keep
> > forgetting to send the key to keyring.debian.org, and it's the second
> > time this has happened. Since the keyring-maint team usually updates
> > debian-keyring once a month, it means I can't do any uploads for a
> > month, which is pretty inconvenient.

I would like to second this request because I recently made the same
mistake. Although I had uploaded my public key to the keyserver network
months ago, it was never synced with keyring.debian.org. I naively
assumed it would happen automatically. I followed the instructions on
https://keyring.debian.org/ and now I'm waiting for the keypush. In the
meantime I cannot upload any packages.

> We've discussed this internally in the past (we have scripts/chk_expiry
> already which probably needs a bit of cleanup for gpg2) and never come
> up with a solution that we actually rolled out. I have a few unanswered
> questions about doing such a thing:
> 
> *) What email address do we email from? The keyring-maint role address?
>Something else where we can just drop the bounces?

Either this one or from a completely new address which is only meant for
sending out those emails but is not supposed to receive messages.

> *) Which email address do we notify about the key expiry? The primary
>UID (not always well specified)? All UIDs? The @debian.org address
>associated with the key (where available, doesn't work for DDs)?

In doubt I would suggest to notify all email addresses / UIDs, just to
be sure.

> *) How often do we email? Both in terms of how often do we run the
>checks, and how often do we alter someone about an upcoming expiry.
>Should it be something we do from a regular cron job, or something
>done after a keyring update?

Once per week, three months before the key will expire. Both, a regular
cron job or after a keyring update, would work I guess as long as the
keyring push happens approximately once per month. This will give active
people enough time to react.

> *) Why is it keyring-maint's responsibility to manage key expiry
>notifications for people?

It isn't but I believe you would help to improve this service. Some
people like me didn't know that updated public keys are not
automatically synced, others forget it completely. In any case an
automated email would help to prevent those situations, which could mean
that DM/DDs are unable to upload for a month or longer.

> *) [Related, but a one off]: How do we handle long expired keys? There
>are keys that have been expired for nearly 3 years. Is there a point
>where we should submit them to MIA? If we're sending notifications
>perhaps there's an MIA notification as part of the same script?

If they have been expired for three years, it is very likely that the
developer in question is MIA. I believe it would be helpful to inform
the MIA team about it and ask them to check the situation. This
could/should? be handled differently.

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Bug#904382: python3-doublex: fails to install with Python 3.7

[David Villa]

Hi Andreas:

I just fixed this issue with this module and it's available in the upstream
repository [1]. Unfortunately when the Debian Python Modules Team changed
the package building system to git-buildpackage, I stopped maintaining my
packages for Debian. I have not had time to understand and apply the new
system. I would appreciate some help in making the conversion to the new
package building system.

Thank you

[1] https://bitbucket.org/DavidVilla/python-doublex

El lun., 23 jul. 2018 a las 20:45, Andreas Beckmann ()
escribió:

> Package: python3-doublex
> Version: 1.8.2-1
> Severity: serious
> Tags: sid buster
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: block 902788 with -1
>
> Hi,
>
> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.
>
> From the attached log (scroll to the bottom...):
>
>   Setting up python3-doublex (1.8.2-1) ...
> File "/usr/lib/python3/dist-packages/doublex/matchers.py", line 129
>   def async(self, timeout):
>   ^
>   SyntaxError: invalid syntax
>
> File
> "/usr/lib/python3/dist-packages/doublex/test/async_race_condition_test.py",
> line 39
>   assert_that(spy.write, called().async(1))
>   ^
>   SyntaxError: invalid syntax
>
> File "/usr/lib/python3/dist-packages/doublex/test/unit_tests.py", line
> 1333
>   assert_that(spy.write, called().async(timeout=1))
>   ^
>   SyntaxError: invalid syntax
>
>   dpkg: error processing package python3-doublex (--configure):
>installed python3-doublex package post-installation script subprocess
> returned error exit status 1
>   Errors were encountered while processing:
>python3-doublex
>
>
> "async" has become a reserved keyword in Python 3.7
>
>
> cheers,
>
> Andreas
>
-- 
David Villa Alises
Grupo ARCO (Arquitectura y Redes de Computadores)
Escuela Superior de Informática - Ciudad Real
Universisdad de Castilla-La Mancha
GPG KeyID: 0x201B8868

Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work

[Phil Wyett]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 2018-07-24 at 11:21 +0300, Alex Berg wrote:
> I confirm this bug in release 67.0.3396.87-1
> 
> youtube video worked
> but html5, and movies no longer work
> 
> Install the older version from stable (stretch) - all worked fine
> 

Could you provide an example of what doe snot work.

Regards

Phil

- -- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

IRC: kathenas

Web: https://kathenas.org

Github: https://github.com/kathenas

GitLab: https://gitlab.com/kathenas

Twitter: kathenasorg

GPG: A0C3 4C6A AC2B B8F4 F1E5 EDF4 333F 60DC B0B9 BB77
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJbVuagAAoJEDM/YNywubt3MFAP/jH3nfcsOA+hSGgNSPf/2lCZ
CjkdqwKwCltXbG8aZtJa/cKhji8xfNHwn+qI/r+/Sv618js8x//2WXN5VBSB+z8P
159ViHobeKTs6AULuRGnA8x4aQXZVGFSs1pGn6uBsEbESbsmyplQO/Q0IvWBozoa
hr44Dhnjt+8jppvjVo29sXHyDOjeoa+z5KeP96sfTLtub5FzvyxwU68YLILWRlEh
Y2zSvsCuBh/U7Nizi8SoQw2dSodPWzH3xFJqkiXJVeo29sqPUOpDmUvv5UX5H47/
vW5dEeeNK8gNzU48Dd6bn+QAuAUHqGrPdfEBu3Ti5JOY8GFgPNuKLENUBg1Vsvl4
q7JU4QNgyHStr1gQrz/2h3KjaoOhEIeaZXZ9oKxr+LV2xqKApEc/GT7T1/Z/Ec4m
H3qgrXE4LWTYOoZsLs/5TrofFtfWRLZiOaeiCjDwzj3b8/cG03WQWx+Jt59iHcnp
45USbxo1fGoZ9inyuPbX/tkHMD9Gs/plps3lOMbjSEqngY84ewlb9hMopbCZxR68
KS2VZN+YwHLd5edjB0QP34Wtv6hMw6O8ZPCkLVjm7wo0Kf4o805kWO9SMDkmy+X8
FxpyGQnOPZntr0MNnME/dllS3RvVu+Ubmj5LYSt5gDMUOEw6VSwY60usoR515Br+
UO8azBApbIi9u/DUxCJp
=PaVM
-END PGP SIGNATURE-

Bug#904427: ltsp: Please consider to use NFS by default again

[Vagrant Cascadian]

On 2018-07-24, Wolfgang Schweer  wrote:
> while testing Debian Edu Buster I tried to use NFS instead of NBD to 
> speed things up and to save disk space; NFS seems to work with recent 
> kernels (linux-image-4.17.0-1-amd64 atm): no issues as far as I can 
> tell.

Glad to hear it!


> As the switch from NFS to NBD (commit 9aba277) happened some time ago 
> due to an incompatibility between the kernel overlay filesystem and NFS, 
> it might now be possible to switch back.

Since the defaults have changed, I'm not sure it's a good idea to switch
back. In particular, The chrootless(LTSP-PNP) method has been
recommended by LTSP developers for many years doesn't really work with
NFS in production environments, since you'd have to export "/" over NFS!

I would, of course, be interested in bug fixes for NFS support, but I
don't forsee making it the default again.

live well,
  vagrant

Bug#904429: libpam-u2f: Console applications waiting on pam-u2f cannot be interrupted

[Nicolas Braud-Santoni]

Package: libpam-u2f
Version: 1.0.7-1
Severity: important
Tags: upstream

Using pam-u2f with sudo (and likely other applications), I cannot interrupt
it when waiting on a U2F device, whereas Ctrl-C works as expected when I am
prompted for a password.

> $ sudo id
> Please touch the device.
> ^C^C^C^C^C^C^C^K^K^K^K^K^K^K


Here is my PAM configuration for sudo:

> # /etc/pam.d/sudo 
> #%PAM-1.0
> 
> # here are the per-package modules (the "Primary" block)
> auth sufficient pam_u2f.so authfile=/etc/auth/u2f_sudo cue
> @include common-auth
> @include common-account
> @include common-session-noninteractive


Best,

  nicoo

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

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

Versions of packages libpam-u2f depends on:
ii  libc6   2.27-3
ii  libpam0g1.1.8-3.7
ii  libu2f-host01.1.5-1
ii  libu2f-server0  1.1.0-2

Versions of packages libpam-u2f recommends:
ii  pamu2fcfg  1.0.7-1

libpam-u2f suggests no packages.

-- no debconf information

Bug#904420: lintian: Warn about empty fields in source package control files

[David Bremner]

Chris Lamb  writes:

>
> Naturally, this could also be indicative of a problem with the
> packaging. Very happy to entertain a request to raising the severity
> though; fancy retitling the bug to match?

Done.

Bug#892374: RedHat has a patch for minor nfs version in options

[Alexandra N. Kossovsky]

RedHat has a patch for minor nfs version in autofs options:
https://bugzilla.redhat.com/show_bug.cgi?id=1486035
https://bugzilla.redhat.com/attachment.cgi?id=1319207

This patch solves the issue for me.

--
Alexandra N. Kossovsky
OKTET Labs (http://www.oktetlabs.ru/)

Bug#904428: linux-image-4.17.0-1-amd64: sound pops/clicks with snd_hda_intel unless power saving is disabled

[Gard Spreemann]

Package: src:linux
Version: 4.17.8-1
Severity: important
Tags: upstream

Dear Maintainer,

After upgrading from linux-image-4.16.0-2-amd64 to
linux-image-4.17.0-1-amd64, my computer's sound card exhibits an
audible and annoying pop or click when an audio stream is about to
play or stop playing. The pop/click was not present with earlier
kernels.

Turning off power saving with

 options snd_hda_intel power_save=0 power_save_controller=N

as per Redhat bug 1525104 [1] works around the problem (no pop/click).

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1525104


-- Package-specific info:
** Version:
Linux version 4.17.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.17.8-1 (2018-07-20)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.17.0-1-amd64 
root=UUID=546f4738-0d40-4e33-b17a-29b58fe436dd ro

** Not tainted

Bug#904420: lintian: please raise severity of warning for empty source package fields

[Chris Lamb]

tags 904420 + pending
thanks

Fixed in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/185c8266ce65f0c20caeef42d56e83f0f43bede0

  checks/control-file.desc | 2 +-
  debian/changelog | 4 
  t/tests/control-has-empty-field/debian/debian/control.in | 4 
  t/tests/control-has-empty-field/tags | 8 ++--
  4 files changed, 15 insertions(+), 3 deletions(-)


Regards,

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

Bug#904427: ltsp: Please consider to use NFS by default again

[Wolfgang Schweer]

Source:   ltsp
Version:  5.18.04-2
Severity: wishlist
User: debian-...@lists.debian.org
Usertags: debian-edu


Hi,

while testing Debian Edu Buster I tried to use NFS instead of NBD to 
speed things up and to save disk space; NFS seems to work with recent 
kernels (linux-image-4.17.0-1-amd64 atm): no issues as far as I can 
tell.

As the switch from NFS to NBD (commit 9aba277) happened some time ago 
due to an incompatibility between the kernel overlay filesystem and NFS, 
it might now be possible to switch back.

Please test.

Wolfgang


signature.asc
Description: PGP signature

Bug#904426: O: dbus-cpp -- header-only dbus-binding leveraging C++-11

[Chris Lamb]

Package: wnpp
Severity: normal

I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see salsa. :)

The binary packages are:
  
  Package: libdbus-cpp5
  Architecture: any
  Multi-Arch: same
  Depends: ${misc:Depends},
   ${shlibs:Depends},
  Description: header-only dbus-binding leveraging C++-11 (runtime libraries)
   A header-only dbus-binding leveraging C++-11, relying on compile-time
   polymorphism to integrate with arbitrary type systems. Runtime portions to
   bind to different event loops.
  
  Package: dbus-cpp-bin
  Section: libdevel
  Architecture: any
  Multi-Arch: foreign
  Depends: ${misc:Depends},
   ${shlibs:Depends},
   libdbus-cpp5 (= ${binary:Version})
  Description: header-only dbus-binding leveraging C++-11 (tools)
   Protocol compiler and generator to automatically generate protocol headers
   from introspection XML.
   .
   D-Bus is a message bus used for sending messages between applications.
   .
   This package contains runtime binaries.
  
  Package: libdbus-cpp-dev
  Section: libdevel
  Architecture: any
  Multi-Arch: same
  Depends: ${misc:Depends},
   ${shlibs:Depends},
   dbus,
   libdbus-cpp5 (= ${binary:Version})
  Replaces: dbus-cpp-dev
  Conflicts: dbus-cpp-dev
  Provides: dbus-cpp-dev
  Description: header-only dbus-binding leveraging C++-11 (development files)
   A header-only dbus-binding leveraging C++-11, relying on compile-time
   polymorphism to integrate with arbitrary type systems.
   .
   D-Bus is a message bus used for sending messages between applications.
  
  Package: dbus-cpp-dev-examples
  Section: x11
  Architecture: any
  Multi-Arch: same
  Depends: ${misc:Depends},
   ${shlibs:Depends},
  Description: header-only dbus-binding leveraging C++-11 (examples)
   A header-only dbus-binding leveraging C++-11, relying on compile-time
   polymorphism to integrate with arbitrary type systems.
   .
   D-Bus is a message bus used for sending messages between applications.
   .
   This package provides examples.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org
   `-

Bug#904425: O: process-cpp -- C++11 library for handling processes

[Chris Lamb]

Package: wnpp
Severity: normal

I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.

The binary packages are:

  Package: libprocess-cpp3
  Architecture: any
  Multi-Arch: same
  Pre-Depends:
   ${misc:Pre-Depends}
  Depends:
   ${misc:Depends},
   ${shlibs:Depends}
  Description: C++11 library for handling processes (runtime libraries)
   process-cpp is a simple and straightforward wrapper around process creation
   and control. It helps both with handling child processes and with interacting
   with the current process. Some of its features include:
   .
- Thread-safe get/set/unset operation on the current process's environment.
- Throwing and non-throwing overloads of functions when system calls are
  involved.
- Seamless redirection of input, output and error streams of child 
processes.
- Type-safe interaction with the virtual proc filesystem, both for reading &
  writing.
   .
   The library's main purpose is to assist in testing and when a software
   component needs to carry out process creation/control tasks, e.g., a 
graphical
   shell. To this end, the library is extensively tested and tries to ensure
   fail-safe operation as much as possible.
   .
   This package includes the process-cpp runtime libraries.
  
  Package: libprocess-cpp-dev
  Section: libdevel
  Architecture: any
  Multi-Arch: same
  Recommends:
   libprocess-cpp-doc
  Depends:
   libprocess-cpp3 (= ${binary:Version}),
   libproperties-cpp-dev,
   ${misc:Depends}
  Description: C++11 library for handling processes (dev headers and libraries)
   process-cpp is a simple and straightforward wrapper around process creation
   and control. It helps both with handling child processes and with interacting
   with the current process. Some of its features include:
   .
- Thread-safe get/set/unset operation on the current process's environment.
- Throwing and non-throwing overloads of functions when system calls are
  involved.
- Seamless redirection of input, output and error streams of child 
processes.
- Type-safe interaction with the virtual proc filesystem, both for reading &
  writing.
   .
   This package includes all the development headers and libraries for
   process-cpp.
  
  Package: libprocess-cpp-doc
  Section: doc
  Architecture: all
  Depends:
   ${misc:Depends}
  Suggests:
   libprocess-cpp-dev
  Description: C++11 library for handling processes (documentation)
   process-cpp is a simple and straightforward wrapper around process creation
   and control. It helps both with handling child processes and with interacting
   with the current process. Some of its features include:
   .
- Thread-safe get/set/unset operation on the current process's environment.
- Throwing and non-throwing overloads of functions when system calls are
  involved.
- Seamless redirection of input, output and error streams of child 
processes.
- Type-safe interaction with the virtual proc filesystem, both for reading &
  writing.
   .
   This package includes documentation files for the libprocess-cpp development.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org
   `-

Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work

[Alex Berg]

I confirm this bug in release 67.0.3396.87-1

youtube video worked
but html5, and movies no longer work

Install the older version from stable (stretch) - all worked fine

-- 
Sincerely
Oleksandr Shtalinberg

Bug#904424: python-meshio: autopkgtest regression: ModuleNotFoundError: No module named 'lxml'

[Paul Gevers]

Source: python-meshio
Version: 2.0.4-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With the upload of version 2.0.4-1, your package started to fail its
autopgktest in testing. I copied the output below.

Could you please investigate? Does the test or the package miss a (test)
dependency? Currently this failure is delaying the migration to testing
by 13 days. Mind you, currently also the python3.7 transition¹ is going
on, which means that python3.7 is added to the supported python3
versions. Since python3-defaults added python3.7 support, your
autopkgtest has been failing, but that seems due to h5py not being
rebuild properly yet. The error I report now is different and AFAICT not
related.

Paul

¹ https://release.debian.org/transitions/html/python3.7.html

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

=== FAILURES
===
 test_io[mesh0]


mesh = Number of points: 4
Number of elements:
  triangle: 2

@pytest.mark.parametrize(
"mesh",
[
helpers.tri_mesh,
helpers.tet_mesh,
helpers.add_cell_data(helpers.tri_mesh, 1, dtype=float),
helpers.add_cell_data(helpers.tri_mesh, 1, dtype=numpy.int32),
],
)
def test_io(mesh):
>   helpers.write_read(meshio.dolfin_io.write,
meshio.dolfin_io.read, mesh, 1.0e-15)

test/test_dolfin.py:21:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
test/helpers.py:230: in write_read
writer(filepath, input_mesh)
/usr/lib/python3/dist-packages/meshio/dolfin_io.py:216: in write
_write_mesh(filename, mesh.points, cell_type, mesh.cells)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

filename = '/tmp/tmpd66a1ykw/test.dat'
points = array([[0., 0., 0.],
   [0., 0., 0.],
   [0., 0., 0.],
   [0., 0., 0.]])
cell_type = 'triangle'
cells = {'triangle': array([[0, 1, 2],
   [0, 2, 3]])}

def _write_mesh(filename, points, cell_type, cells):
>   from lxml import etree as ET
E   ModuleNotFoundError: No module named 'lxml'

/usr/lib/python3/dist-packages/meshio/dolfin_io.py:116: ModuleNotFoundError
-- Captured log call
---
dolfin_io.py   208 WARNING  Dolfin's XML is a legacy format.
Consider using XDMF instead.
 test_io[mesh1]


mesh = Number of points: 5
Number of elements:
  tetra: 2

@pytest.mark.parametrize(
"mesh",
[
helpers.tri_mesh,
helpers.tet_mesh,
helpers.add_cell_data(helpers.tri_mesh, 1, dtype=float),
helpers.add_cell_data(helpers.tri_mesh, 1, dtype=numpy.int32),
],
)
def test_io(mesh):
>   helpers.write_read(meshio.dolfin_io.write,
meshio.dolfin_io.read, mesh, 1.0e-15)

test/test_dolfin.py:21:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
test/helpers.py:230: in write_read
writer(filepath, input_mesh)
/usr/lib/python3/dist-packages/meshio/dolfin_io.py:216: in write
_write_mesh(filename, mesh.points, cell_type, mesh.cells)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

filename = '/tmp/tmpy57apeci/test.dat'
points = array([[0., 0., 0.],
   [0., 0., 0.],
   [0., 0., 0.],
   [0., 0., 0.],
   [0.1667, 0.1667, 0.1667]])
cell_type = 'tetra'
cells = {'tetra': array([[0, 1, 2, 4],
   [0, 2, 3, 4]])}

def _write_mesh(filename, points, cell_type, cells):
>   from lxml import etree as ET
E   ModuleNotFoundError: No module named 'lxml'

/usr/lib/python3/dist-packages/meshio/dolfin_io.py:116: ModuleNotFoundError
-- Captured log call
---
dolfin_io.py   208 WARNING  Dolfin's XML is a legacy format.
Consider using XDMF instead.
 test_io[mesh2]


mesh = Number of points: 4
Number of elements:
  triangle: 2
Cell data: a, b

@pytest.mark.parametrize(
"mesh",
[
helpers.tri_mesh,
helpers.tet_mesh,
helpers.add_cell_data(helpers.tri_mesh, 1, dtype=float),
helpers.add_cell_data(helpers.tri_mesh, 1, dtype=numpy.int32),
],
)
def test_io(mesh):
>   helpers.write_read(meshio.dolfin_io.write,
meshio.dolfin_io.read, mesh, 1.0e-15)

test/test_dolfin.py:21:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
test/helpers.py:230: in write_read
 

Bug#904420: lintian: Warn about empty fields in source package control files

[Chris Lamb]

Hi David,

> >> Vcs-Browser: has only whitespace, and Vcs-Git: is empty
[..]
> > (These are all pedantic tags; are you perhaps not running at that
> > level?)
> >
> I am not running at pedantic level. For me these errors deserve at least
> a warning.

So, I probably just added the tag at an artificially lower severity to
avoid tedious pushback and to ensure it was working properly, rather
than it being a reflection of my personal opinion.

I can't think of any useful reason except for the case where generating
an empty field via some kind of debian/control.in-like mechanism is
considered perfectly "valid" for that source package's complicated
arrangements.

Naturally, this could also be indicative of a problem with the
packaging. Very happy to entertain a request to raising the severity
though; fancy retitling the bug to match?


Regards,

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

Bug#904423: irqbalance: initscript refers to typo'd IRCBALANCE_ARGS variable

[AJ Jordan]

Package: irqbalance
Version: 1.1.0-2.3
Severity: normal
Tags: patch

Attached is a patch to fix what I assume is a typo in
/etc/init.d/irqbalance. I would send a version control patch, but I
was unable to find source control for the irqbalance Debian
packaging. Instead I have generated a unified diff (or you could just
make the change yourself; it's pretty trivial).

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

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

Versions of packages irqbalance depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  init-system-helpers1.48
ii  libc6  2.24-11+deb9u3
ii  libcap-ng0 0.7.7-3+b1
ii  libglib2.0-0   2.50.3-2
ii  libnuma1   2.0.11-2.1
ii  libsystemd0232-25+deb9u4
ii  lsb-base   9.20161125

irqbalance recommends no packages.

irqbalance suggests no packages.

-- debconf information excluded

Bug#904420: lintian: Warn about empty fields in source package control files

[David Bremner]

Chris Lamb  writes:

> tags 904420 + moreinfo
> thanks
>
> Hi David,
>
>> Vcs-Browser: has only whitespace, and Vcs-Git: is empty
>
> Unless I'm missing something, this should already be warned by "debian-
> control-has-empty-field" as well as "file-contains-trailing-whitespace".
>
> (These are all pedantic tags; are you perhaps not running at that
> level?)
>

I am not running at pedantic level. For me these errors deserve at least
a warning. Are there legit reasons for empty source package fields, and
specifically for empty Vcs-* fields?

Bug#903698: fixed in dh-python 3.20180723

[Paul Gevers]

Control: reopen -1

Dear Piotr,

On Mon, 23 Jul 2018 13:34:11 + =?utf-8?q?Piotr_O=C5=BCarowski?=
 wrote:
>* dh_python{2,3}:
>  - fix \.so.* symlink renaming for non-default Python versions
>(closes: 739500, 903698)

Thanks for the fix. It worked on all arches where sphinxbase was rebuild
except for mipsel64el (see below), hence I reopen the bug.

https://buildd.debian.org/status/fetch.php?pkg=sphinxbase=mips64el=0.8%2B5prealpha%2B1-2%2Bb2=1532363016=0

Get:68 http://ftp.at.debian.org/debian unstable/main mips64el dh-python
all 3.20180723 [94.2 kB]

But...

  This package contains Python3 bindings for libsphinxbase.

drwxr-xr-x root/root 0 2018-07-23 16:12 ./
drwxr-xr-x root/root 0 2018-07-23 16:12 ./usr/
drwxr-xr-x root/root 0 2018-07-23 16:12 ./usr/lib/
drwxr-xr-x root/root 0 2018-07-23 16:12 ./usr/lib/python3.7/
drwxr-xr-x root/root 0 2018-07-23 16:12
./usr/lib/python3.7/site-packages/
drwxr-xr-x root/root 0 2018-07-23 16:12
./usr/lib/python3.7/site-packages/sphinxbase/
lrwxrwxrwx root/root 0 2018-07-23 16:12
./usr/lib/python3.7/site-packages/sphinxbase/_sphinxbase.so ->
_sphinxbase.so.0.0.0
drwxr-xr-x root/root 0 2018-07-23 16:12 ./usr/lib/python3/
drwxr-xr-x root/root 0 2018-07-23 16:12
./usr/lib/python3/dist-packages/
drwxr-xr-x root/root 0 2018-07-23 16:12
./usr/lib/python3/dist-packages/sphinxbase/
-rw-r--r-- root/root  1811 2018-07-23 16:12
./usr/lib/python3/dist-packages/sphinxbase/__init__.py
-rw-r--r-- root/root108232 2018-07-23 16:12
./usr/lib/python3/dist-packages/sphinxbase/_sphinxbase.cpython-36m-mips64el-linux-gnuabi64.so
lrwxrwxrwx root/root 0 2018-07-23 16:12
./usr/lib/python3/dist-packages/sphinxbase/_sphinxbase.so.0 ->
_sphinxbase.so.0.0.0
-rw-r--r-- root/root108232 2018-07-23 16:12
./usr/lib/python3/dist-packages/sphinxbase/_sphinxbase.so.0.0.0
-rw-r--r-- root/root 25529 2018-07-23 16:12
./usr/lib/python3/dist-packages/sphinxbase/sphinxbase.py

Thanks
Paul



signature.asc
Description: OpenPGP digital signature

Bug#904420: lintian: Warn about empty fields in source package control files

[Chris Lamb]

tags 904420 + moreinfo
thanks

Hi David,

> Vcs-Browser: has only whitespace, and Vcs-Git: is empty

Unless I'm missing something, this should already be warned by "debian-
control-has-empty-field" as well as "file-contains-trailing-whitespace".

(These are all pedantic tags; are you perhaps not running at that
level?)


Best wishes,

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

Bug#870418: How much longer should Shutter remain in sid?

[Dominique Dumont]

On Tuesday, 24 July 2018 04:32:22 CEST you wrote:
>  [...] and proposed to give Dominique
>access to the upstream BZR repo so he can fix stuff directly there
>(and de facto become the only person active upstream with
>development skills). Dominique did not reply to this offer.

Hmm, I don't remember seeing this offer. No matter.

Shutter also needs to be ported on the replacement of libgoocanvas-perl.

All in all, I guess that 2 or 3 weeks of full time work are required to port 
shutter to more recent libraries. I don't have that kind of free time.

Sadly, I think the only option left is to remove shutter from Debian.

All the best

Bug#890968: Works in 1.8.2-1

[Raúl Sánchez Siles]

  Hello:

  Any chance the working version is backported to stretch where problem still 
exists?

  Thanks

-- 

*Raúl Sánchez Siles* 

Bug#904422: npm: complains about too-new nodejs

[Matthias Urlichs]

Package: npm
Version: 5.8.0+ds-1
Severity: minor

npm WARN npm npm does not support Node.js v10.4.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 
8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/

-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (800, 'stable'), (750, 'testing'), (700, 'unstable'), (200, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages npm depends on:
ii  node-abbrev1.0.9-1
ii  node-ansi  0.3.0-2
ii  node-ansi-color-table  1.0.0-1
ii  node-ansi-regex2.0.0-1
ii  node-ansistyles0.1.3-1
ii  node-aproba1.2.0-1
ii  node-archy 1.0.0-1
ii  node-are-we-there-yet  1.1.4-1
ii  node-aws-sign2 0.7.1-1
ii  node-block-stream  0.0.9-1
ii  node-bluebird  3.5.1+dfsg2-2
ii  node-caseless  0.12.0-1
ii  node-chalk 1.1.3-2
ii  node-config-chain  1.1.11-1
ii  node-detect-indent 5.0.0-1
ii  node-editor1.0.0-1
ii  node-encoding  0.1.12-2
ii  node-fs-vacuum 1.2.10-2
ii  node-fstream   1.0.10-1
ii  node-fstream-ignore0.0.6-2
ii  node-gauge 2.7.4-1
ii  node-github-url-from-git   1.4.0-1
ii  node-glob  7.1.1-1
ii  node-graceful-fs   4.1.11-1
ii  node-gyp   3.4.0-1
ii  node-har-validator 5.0.2-1
ii  node-has-unicode   2.0.1-2
ii  node-hawk  6.0.1+dfsg-1
ii  node-hosted-git-info   2.1.5-1
ii  node-iferr 1.0.0-1
ii  node-import-lazy   3.0.0.REALLY.2.1.0-1
ii  node-inflight  1.0.6-1
ii  node-inherits  2.0.3-1
ii  node-ini   1.3.4-1
ii  node-is-npm1.0.0-1
ii  node-is-typedarray 1.0.0-2
ii  node-isstream  0.1.2+dfsg-1
ii  node-jsonstream1.0.3-4
ii  node-latest-version3.1.0-1
ii  node-lazy-property 1.0.0-1
ii  node-lockfile  0.4.1-1
ii  node-lru-cache 4.0.2-1
ii  node-minimatch 3.0.3-1
ii  node-mkdirp0.5.1-1
ii  node-move-concurrently 1.0.1-1
ii  node-nopt  3.0.6-3
ii  node-normalize-package-data2.3.5-2
ii  node-npmlog4.1.2-1
ii  node-once  1.4.0-2
ii  node-opener1.4.3-1
ii  node-osenv 0.1.0-1
ii  node-path-is-inside1.0.2-1
ii  node-performance-now   2.1.0+debian-1
ii  node-promise-inflight  1.0.1-1
ii  node-read  1.0.7-1
ii  node-read-package-json 1.2.4-1
ii  node-readable-stream   2.3.6-1
ii  node-request   2.26.1-1
ii  node-retry 0.6.0-1
ii  node-rimraf2.6.2-1
ii  node-safe-buffer   5.1.2-1
ii  node-semver5.3.0-1
ii  node-semver-diff   2.1.0-2
ii  node-set-blocking  2.0.0-1
ii  node-sha   1.2.3-1
ii  node-slide 1.1.4-1
ii  node-sorted-object 2.0.1-1
ii  node-stringstream  0.0.6-1
ii  node-strip-ansi3.0.1-1
ii  node-tar   4.4.4+ds1-1
ii  node-tough-cookie  2.3.2+dfsg-1
ii  node-uid-number0.0.6-1
ii  node-underscore1.8.3~dfsg-1
ii  node-unique-filename   1.1.0+ds-2
ii  node-unpipe1.0.0-1
ii  node-validate-npm-package-license  3.0.1-1
ii  node-which 1.2.11-1
ii  node-wrappy1.0.2-1
ii  node-yargs 6.4.0-2
ii  nodejs 10.4.0~dfsg-1

npm recommends no packages.

npm suggests no packages.

-- no debconf information

Bug#904421: installation-report

[Jordan Jones]

Package: installation-reports

Boot method: DVD-1
Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.5.0-amd64-netinst.iso
Date: 23 July 2018, 03:30 UTC

Machine: Fujitsu Lifebook T4410
Processor: Intel(R) Core(TM)2 Duo CPU P8700  @ 2.53GHz
Memory: 4GB
Partitions:FilesystemType 1K-blocks  Used
Available Use% Mounted on
udev  devtmpfs   197 0   197   0% /dev
tmpfs tmpfs   398148 11380386768   3% /run
/dev/mapper/jdeb--vg-root ext4 148479768  44795480  96072284  32% /
tmpfs tmpfs  1990736277064   1713672  14% /dev/shm
tmpfs tmpfs 5120 4  5116   1% /run/lock
tmpfs tmpfs  1990736 0   1990736   0%
/sys/fs/cgroup
/dev/sda1 ext2240972 37468191063  17% /boot
tmpfs tmpfs   39814416398128   1%
/run/user/118
tmpfs tmpfs   39814448398096   1%
/run/user/1000


Output of lspci -knn (or lspci -nn):00:00.0 Host bridge [0600]: Intel
Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40]
(rev 07)
Subsystem: Fujitsu Limited. Mobile 4 Series Chipset Memory Controller
Hub [10cf:144e]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4
Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
Subsystem: Fujitsu Limited. Mobile 4 Series Chipset Integrated
Graphics Controller [10cf:1458]
Kernel driver in use: i915
Kernel modules: i915
00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series
Chipset Integrated Graphics Controller [8086:2a43] (rev 07)
Subsystem: Fujitsu Limited. Mobile 4 Series Chipset Integrated
Graphics Controller [10cf:1458]
00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #4 [8086:2937] (rev 03)
Subsystem: Fujitsu Limited. 82801I (ICH9 Family) USB UHCI Controller
[10cf:1472]
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #5 [8086:2938] (rev 03)
Subsystem: Fujitsu Limited. 82801I (ICH9 Family) USB UHCI Controller
[10cf:1472]
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #6 [8086:2939] (rev 03)
Subsystem: Fujitsu Limited. 82801I (ICH9 Family) USB UHCI Controller
[10cf:1472]
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB2 EHCI Controller #2 [8086:293c] (rev 03)
Subsystem: Fujitsu Limited. 82801I (ICH9 Family) USB2 EHCI Controller
[10cf:1473]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD
Audio Controller [8086:293e] (rev 03)
Subsystem: Fujitsu Limited. 82801I (ICH9 Family) HD Audio Controller
[10cf:1475]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 1 [8086:2940] (rev 03)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 2 [8086:2942] (rev 03)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 3 [8086:2944] (rev 03)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #1 [8086:2934] (rev 03)
Subsystem: Fujitsu Limited. 82801I (ICH9 Family) USB UHCI Controller
[10cf:1472]
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #2 [8086:2935] (rev 03)
Subsystem: Fujitsu Limited. 82801I (ICH9 Family) USB UHCI Controller
[10cf:1472]
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #3 [8086:2936] (rev 03)
Subsystem: Fujitsu Limited. 82801I (ICH9 Family) USB UHCI Controller
[10cf:1472]
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB2 EHCI Controller #1 [8086:293a] (rev 03)
Subsystem: Fujitsu Limited. 82801I (ICH9 Family) USB2 EHCI Controller
[10cf:1473]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
[8086:2448] (rev 93)
00:1f.0 ISA bridge 

Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O

[Sebastian Andrzej Siewior]

On 2018-07-23 17:54:44 [+0900], Marc Dequènes wrote:
> Quack,
Hi,

> I just upgraded and cannot reproduce this problem. I'm not using the
> ScanOnAccess feature.

just to confirm: you can not reproduce the problem.

> Follows collected config info.
> \_o<

Sebastian

Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O.

[Sebastian Andrzej Siewior]

On 2018-07-23 18:26:04 [+0200], Richard Lucassen wrote:
> Same here (6 Postfix front-end servers), non-systemd, non-GUI system
> running Debian Stretch. Downgrading to 0.99 is a workaround.
> ScanOnAccess is set to false.

Is the kernel complaining about something like in the other report where
it claimed something about a deadlock?

> R.

Sebastian

Bug#904420: lintian: Warn about empty fields in source package control files

[David Bremner]

Package: lintian
Version: 2.5.93
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I just encountered a source package with

Vcs-Browser: 
Vcs-Git:

(Vcs-Browser: has only whitespace, and Vcs-Git: is empty). This seems
like something lintian should complain about.

This is related to, but I think simpler than #879809

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

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

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

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b4

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

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAltWxA0ACgkQ8gKXHaSn
niwE+Av/d3La9jmFiNp1RA8ccohQ+dgT+Io+buv0+jZpYTt2Pq3nJjcSXdK71Az+
zC43LG3GVhdHhBGm7wpXXrplasOCzPkLYA99MXOnYPB76VMe2kaC6QlcJ/RFa65b
CvalN/SZHAgLpC4SUfYJomIU6sAN8jDPGm+aXgU3rMKS+Vf6cc52tb0SCA8YtTL+
a39soBf0NW+px1Bkpp2HzUk8hHHIo18s/qM7+osDFEOytkXxJGBVGtrJB0/E1yqI
dfONMQM1+PgUkGLtBkoccdNMU4CAxvWvrO4MDb3PwSJDH5O4gYSzIMIrWOaZOlDC
T6w8HwsRbDKLVyBk7znQKfAv+gismv4JArSjvgfi3AP0Hzj4E4/vrMWF/+6i7Vwo
eU4gOHKcSenWGDNYNNLWaB9c+Hbeu0EV+qhcJyxlYDi09gDld3iS8irUav7UBsY1
tn242lLB2Yl1eGvnv5weqVHvOIqWbeRHyesNwlXryQlR7+dC+iF9QMgYt1XkuUfe
sLkk4cRX
=/st/
-END PGP SIGNATURE-

Bug#901726: RFS: json-c/0.13.1+dfsg-1 [QA] -- JSON manipulation library

[Nicolas Braud-Santoni]

Hi Gianfranco !

Sorry for getting back to you so late, I was a bit broken and overburdened
by some non-Debian difficulties  :(


On Sun, Jun 17, 2018 at 08:58:00PM +, Gianfranco Costamagna wrote:
> 1) why are you repacking it? is really bundled jquery a "dfsg" problem?
> In general, repack with dfsg is done to solve licensing issues, not because 
> of bundled deps.
> You might use "ds" (Debian source), if you think you can save useful bits, 
> but I think 
> this is not really the case.

The issue is that it's a bundled, build artefact of jquery, not the jquery
source, and there is no indication I could find of which version of jquery it
comes from.

I believe this violates DFSG's rule number 2 (inclusion & distribution of
source code).


> 2) missing copyrights:
> + * Copyright (c) 2016 Alexandru Ardelean.
> + * Copyright (c) 2016 Eric Haszlakiewicz
> (and probably more)

Thanks for the catch; I will address this in a second upload to experimental.


> also, don't forget to request a transition slot!

Done, and this bug was X-Debbugs-CC'd.


Greetings from Hsinchu,

  nicoo


signature.asc
Description: PGP signature

Bug#904419: RM: php-zend-db -- NPOASR; Useless in Debian

[David Prévot]

Package: ftp.debian.org
Severity: normal

Hi,

As documented in #835902, there is AFAICT no point in keeping
php-zend-db in Debian, it’s not even been part of any stable release.

Thanks in advance.

David


signature.asc
Description: PGP signature

Bug#904418: transition: json-c

[Nicolas Braud-Santoni]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Control: block 844452 by -1
Control: retitle 844452 Orphan json-c

Hi,

I need to request a transition slot for json-c; the autogenerated tracker
[0] seems correct, and I will also need someone to schedule binNMUs for
impacted packages (on all architectures) once the transition starts.


While I didn't yet rebuild all impacted packages, I expect all (or most) to
rebuild cleanly as the removed APIs have been deprecated for a while.

The reason for the transition is an API change upstream (and resulting soname
change).  Note that this is a QA upload, and also orphans the package.



Best,

  nicoo

[0]: https://release.debian.org/transitions/html/auto-json-c.html