Bug#910251: Bug@910251 Confirmation of Fix
The delays and warning messages for my MPI programs on Sid were resolved by the workaround fix in libpsm2 11.2.68-2. You can close this one as far as I'm concerned. Thanks, Ron -- James Ronald Lovell Huntsville, AL, USA A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable. -Leslie Lamport
Bug#912711: ITP: python-backports.os -- Backports of new features in Python's os module
Package: wnpp Severity: wishlist Owner: Yao Wei (魏銘廷) * Package name: python-backports.os Version : 0.1.1 Upstream Author : Pi Delport * URL : https://github.com/pjdelport/backports.os/ * License : PSF-2 Programming Lang: Python Description : Backports of new features in Python's os module Hi, This package is a backports of the os.fsencode and os.fsdecode for older Python. This is a dependency for python-fs (2.1.1), and py3 version of this package is considered not needed. This package should be maintained under DPMT. The request of joining the team has been sent. Yao Wei signature.asc Description: PGP signature
Bug#912710: python3-dogpile.cache: syntaxerror during install, cannot install
Package: python3-dogpile.cache Version: 0.6.2-5 Severity: normal Dear Maintainer, while doing apt-get install vcdimager, I get the following error, the package fails to install. I don't know enough about python to understand what is wrong. Setting up python3-dogpile.cache (0.6.2-5) ... File "/usr/lib/python3/dist-packages/dogpile/lock.py", line 115 async = False ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/dogpile/util/readwrite_lock.py", line 26 self.async = 0 ^ SyntaxError: invalid syntax -- System Information: Debian Release: 9.5 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.16-041816-generic (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) Versions of packages python3-dogpile.cache depends on: ii python3 3.6.6-1 python3-dogpile.cache recommends no packages. python3-dogpile.cache suggests no packages. -- no debconf information
Bug#897344: libvisual-0.4-dev claims to be Multi-Arch: same but is not
Em ter, 1 de mai de 2018 às 11:15, Francois Gouget escreveu: > > Package: libvisual-0.4-dev > Version: 0.4.0-11 > Severity: normal > > Dear Maintainer, > > Trying to install the amd64 and i386 versions of this > package results in the following error: > > # apt-get install libvisual-0.4-dev:amd64 libvisual-0.4-dev:i386 > [...] > Unpacking libvisual-0.4-dev:i386 (0.4.0-11) ... > dpkg: error processing archive > /var/cache/apt/archives/libvisual-0.4-dev_0.4.0-11_i386.deb (--unpack): > trying to overwrite shared > '/usr/include/libvisual-0.4/libvisual/lvconfig.h', which is different from > other instances of package libvisual-0.4-dev:i386 > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) > Errors were encountered while processing: > /var/cache/apt/archives/libvisual-0.4-dev_0.4.0-11_i386.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages libvisual-0.4-dev depends on: > ii libc6-dev [libc-dev] 2.27-3 > ii libvisual-0.4-0 0.4.0-11 > ii pkg-config0.29-4+b1 > > libvisual-0.4-dev recommends no packages. > > libvisual-0.4-dev suggests no packages. > > -- no debconf information Hi Francois, I can't understand. libvisual-0.4-dev 0.4.0-11 already has Multi-Arch: same. See here[1]. Can you test again? [1] https://salsa.debian.org/debian/libvisual/commit/60e9cf0ff1a0ac2160311ecc0faa8ef041ef88f4 Regards, Eriberto
Bug#912453: sndio: Please set SONAME on !linux
That may be; I have not heard from Gianfranco (who has sponsored sndio before) yet.
Bug#907893: elpa-ess: R-initialize-on-start looks for .load.R in the wrong place
On 02/11/18 at 10:32, Dirk Eddelbuettel wrote: > > (You forgot to CC the Debian bug address. Added it back in.) I hit r. Forgot to hit R. Sorry. I did a rm -rf on /usr/share/emacs/site-lisp/ess and purged elpa-ess Reinstall it does the trick. M-x ess-version return: ess-version: 18.10-1 [Released git: 1c4253cb4700] (loaded from /usr/share/emacs/site-lisp/elpa/) You can run the command ‘ess-version’ with M-x ess-v RET ess-version: 18.10-1 [Released git: 1c4253cb4700] (loaded from /usr/share/emacs/site-lisp/elpa/) and M-x R loads R in the buffer as well! Thank you very much! -- Laia, ML
Bug#907893: elpa-ess: R-initialize-on-start looks for .load.R in the wrong place
(You forgot to CC the Debian bug address. Added it back in.) On 3 November 2018 at 00:24, Marcelo Laia wrote: | On 02/11/18 at 09:00, Dirk Eddelbuettel wrote: | > Hi Marcelo, | > | ess-version: 17.11 [] (loaded from /usr/share/emacs/site-lisp/) | > | > Then you have two different versions. | | I have purge ess and elpa-ess. Then, I reinstall they. | | root@me:/home/me# ls -l /usr/share/emacs/site-lisp/elpa-src/ess-18.10snapshot1/ | total 1732 | -rw-r--r-- 1 root root650 out 24 12:05 debian-autoloads.el | -rw-r--r-- 1 root root 2655 out 24 12:05 ess-arc-d.el | -rw-r--r-- 1 root root 28966 out 24 12:05 ess-autoloads.el | -rw-r--r-- 1 root root 16550 out 24 12:05 ess-bugs-d.el | -rw-r--r-- 1 root root 10527 out 24 12:05 ess-bugs-l.el | -rw-r--r-- 1 root root 106572 out 24 12:05 ess-custom.el | -rw-r--r-- 1 root root 7049 out 24 12:05 ess-dde.el | -rw-r--r-- 1 root root 7804 out 24 12:05 essd-els.el | -rw-r--r-- 1 root root 33431 out 24 12:05 ess.el | -rw-r--r-- 1 root root 6336 out 24 12:05 ess-font-lock.el | -rw-r--r-- 1 root root 4749 out 24 12:05 ess-generics.el | -rw-r--r-- 1 root root 25447 out 24 12:05 ess-gretl.el | -rw-r--r-- 1 root root 42459 out 24 12:05 ess-help.el | -rw-r--r-- 1 root root 141207 out 24 12:05 ess-inf.el | -rw-r--r-- 1 root root 14281 out 24 12:05 ess-jags-d.el | -rw-r--r-- 1 root root 18971 out 24 12:05 ess-julia.el | -rw-r--r-- 1 root root 2358 out 24 12:05 ess-lsp-l.el | -rw-r--r-- 1 root root 9442 out 24 12:05 ess-mouse.el | -rw-r--r-- 1 root root 4181 out 24 12:05 ess-noweb.el | -rw-r--r-- 1 root root 18644 out 24 12:05 ess-noweb-font-lock-mode.el | -rw-r--r-- 1 root root 77518 out 24 12:05 ess-noweb-mode.el | -rw-r--r-- 1 root root 3863 out 24 12:05 ess-omg-d.el | -rw-r--r-- 1 root root 14597 out 24 12:05 ess-omg-l.el | -rw-r--r-- 1 root root111 out 24 12:05 ess-pkg.el | -rw-r--r-- 1 root root 4920 out 24 12:05 ess-r-a.el | -rw-r--r-- 1 root root 23629 out 24 12:05 ess-r-completion.el | -rw-r--r-- 1 root root 19740 out 24 12:05 ess-rd.el | -rw-r--r-- 1 root root 17890 out 24 12:05 ess-rdired.el | -rw-r--r-- 1 root root 10138 out 24 12:05 ess-r-flymake.el | -rw-r--r-- 1 root root 9055 out 24 12:05 ess-r-gui.el | -rw-r--r-- 1 root root 93620 out 24 12:05 ess-r-mode.el | -rw-r--r-- 1 root root 36621 out 24 12:05 ess-roxy.el | -rw-r--r-- 1 root root 23517 out 24 12:05 ess-r-package.el | -rw-r--r-- 1 root root 52089 out 24 12:05 ess-r-syntax.el | -rw-r--r-- 1 root root 16664 out 24 12:05 ess-rutils.el | -rw-r--r-- 1 root root 5421 out 24 12:05 ess-r-xref.el | -rw-r--r-- 1 root root 2655 out 24 12:05 ess-s3-d.el | -rw-r--r-- 1 root root 10267 out 24 12:05 ess-s4-d.el | -rw-r--r-- 1 root root 65541 out 24 12:05 ess-sas-a.el | -rw-r--r-- 1 root root 12478 out 24 12:05 ess-sas-d.el | -rw-r--r-- 1 root root 82251 out 24 12:05 ess-sas-l.el | -rw-r--r-- 1 root root 4812 out 24 12:05 ess-site.el | -rw-r--r-- 1 root root 34902 out 24 12:05 ess-s-lang.el | -rw-r--r-- 1 root root 2692 out 24 12:05 ess-sp3-d.el | -rw-r--r-- 1 root root 20228 out 24 12:05 ess-sp4-d.el | -rw-r--r-- 1 root root 3537 out 24 12:05 ess-sp5-d.el | -rw-r--r-- 1 root root 8092 out 24 12:05 ess-sp6-d.el | -rw-r--r-- 1 root root 29088 out 24 12:05 ess-sp6w-d.el | -rw-r--r-- 1 root root 38509 out 24 12:05 ess-stata-lang.el | -rw-r--r-- 1 root root 6553 out 24 12:05 ess-stata-mode.el | -rw-r--r-- 1 root root 16273 out 24 12:05 ess-swv.el | -rw-r--r-- 1 root root 6736 out 24 12:05 ess-toolbar.el | -rw-r--r-- 1 root root 127755 out 24 12:05 ess-tracebug.el | -rw-r--r-- 1 root root 12457 out 24 12:05 ess-trns.el | -rw-r--r-- 1 root root 65817 out 24 12:05 ess-utils.el | -rw-r--r-- 1 root root 2568 out 24 12:05 ess-vst-d.el | -rw-r--r-- 1 root root 3326 out 24 12:05 ess-xls-d.el | drwxr-xr-x 5 root root 4096 nov 2 21:42 etc | -rw-r--r-- 1 root root 146275 out 24 12:05 julia-mode.el | -rw-r--r-- 1 root root 10972 out 24 12:05 make-regexp.el | -rw-r--r-- 1 root root 13736 out 24 12:05 mouseme.el | root@me:/home/me# | | me@me:~$ ls -l .emacs.d/ | total 48 | -rw-r--r-- 1 marcelo marcelo 2845 out 22 15:20 abbrev_defs | drwx-- 2 marcelo marcelo 4096 nov 2 23:26 auto-save-list | drwxr-xr-x 4 marcelo marcelo 4096 out 22 15:51 elpa | -rw-r--r-- 1 marcelo marcelo 8383 out 24 17:55 init_antigo_com_erros.el | -rw-r--r-- 1 marcelo marcelo 5612 nov 2 21:21 init.el | -rw-r--r-- 1 marcelo marcelo 5428 out 24 17:55 init.el~ | drwxr-xr-x 2 marcelo marcelo 4096 fev 10 2015 lisp | drwxr-xr-x 2 marcelo marcelo 4096 out 22 15:51 url | me@me:~$ | | In ~/.emacs.d/elpa/ there aren't nothing about ess or elpa-ess. | | > That the 17.11 is still there is suspicous. | | I think I found the reason. | | me@me:/usr/share/emacs/site-lisp/elpa-src/ess-18.10snapshot1$ locate ess-custom.el | grep -v home | /usr/share/emacs/site-lisp/elpa-src/ess-18.10snapshot1/ess-custom.el | /usr/share/emacs/site-lisp/elpa/ess-18.10snapshot1/ess-custom.el |
Bug#912709: Max. recursion depth with nested structures exceeded
Package: apt-show-versions Version: 0.22.8 Severity: grave # apt-show-versions Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux-gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. Works fine when non-root though. P.S., # apt-show-versions -i Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux-gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. -- System Information: Debian Release: buster/sid APT prefers experimental APT policy: (990, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages apt-show-versions depends on: ii apt 1.7.0 ii libapt-pkg-perl 0.1.34+b1 ii perl [libstorable-perl] 5.28.0-3 apt-show-versions recommends no packages. apt-show-versions suggests no packages. -- no debconf information
Bug#912687: libmspack0: Regression when extracting cabinets using -F option fixed upstream, needs to be patched
Quack, On 11/3/18 5:44 AM, Goatroth wrote: > I am requesting that the fix, located here: > https://github.com/kyz/libmspack/commit/2d86d4e70026cd03730ce0b00b12579c2e21620a > be ported into the buster/sid packages. And please do let me know if this > method of contact is inappropriate for this sort of thing, just trying to > figure my way through all of this. :) It's the right way to ask :-). Stuart, as this is an important bug I guess you'll be releasing soon? Could you ping me when ready? \_o< signature.asc Description: OpenPGP digital signature
Bug#912708: ITP: aiowsgi -- minimalist WSGI server implementation using async
Package: wnpp Severity: wishlist Owner: Jelmer Vernooij * Package name: aiowsgi Version : 0.0.7 Upstream Author : Gael Pasgrimaud * URL : https://github.com/gawel/aiowsgi * License : MIT Programming Lang: Python Description : minimalist WSGI server implementation using async This package provides a simple Python implementation of the WSGI interace using the waitress pure Python HTTP implementation. -- Jelmer Vernooij PGP Key: https://www.jelmer.uk/D729A457.asc signature.asc Description: PGP signature
Bug#912684: perl-modules-5.28 needs versioned Provides for modules it bundles
On Fri, 02 Nov 2018 22:03:43 +0200, Adrian Bunk wrote: > Package: perl-modules-5.28 > Version: 5.28.0-3 > Severity: serious > > perl-modules-5.28 has > Replaces+Breaks: libextutils-parsexs-perl (<< 3.39) > > This makes libextutils-parsexs-perl in unstable not installable. Right, thanks also for filing a bug against libextutils-parsexs-perl. (This happens for each release that some dual-lifed modules are newer in core than their separate equivalents on the CPAN. Either this fixes itself with a new separate release or we remove the package at some point.) > libextutils-parsexs-perl does have reverse dependencies > in unstable, including revers dependencies with versioned > dependencies. I checked all reverse (build) dependencies and didn't see any problems; all of them are either unversioned or have the form "perl (>= 5.x) | libextutils-parsexs-perl [(>= 3.x]). So I think we have no actual problem here. > Versioned Provides for such modules are required. That's a long story: https://bugs.debian.org/758100 As Niko wrote in #80: | These bugs are now fixed (and deployed on the Debian infrastructure), | so we could try again. | I think I want to do the 5.28 transition first, though. (Leaving handling of this bug to Niko/Dom.) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Rolling Stones: Lonely signature.asc Description: Digital Signature
Bug#912707: [ntfs-3g] cp -p from ext4 partition to ntfs partition mounted with default permission mappings produces wrong file permissions
Package: ntfs-3g Version: 1:2017.3.23-2 Severity: important --- Please enter the report below this line. --- I copy a directory tree from an ext4 partition to a NTFS one mounted with 'permissions' option using cp -r -p. For all files which have access permissions set to 755 their copies have access mask 700, similarily files with permissions 644 are copied with permissions 600. Oddly, files with setuid bit set are copied with correct permissions. Using chmod I can set for files on the NTFS partition whatever permissions I want. (Perhaps, the problem is aroused by simultaneously setting permissions and owner:group?) --- System information. --- Architecture: Kernel: Linux 4.18.0-2-amd64 Debian Release: buster/sid 500 unstablemirror.isoc.org.il 500 stable repo.skype.com 1 experimentalmirror.isoc.org.il --- Package information. --- Depends (Version) | Installed ===-+-== libc6 (>= 2.17) | 2.27-8 libgcrypt20 (>= 1.8.0) | 1.8.4-3 libgnutls30 (>= 3.5.0) | 3.5.19-1+b1 libgpg-error0 (>= 1.14) | 1.32-3 libntfs-3g88 (= 1:2017.3.23-2) | 1:2017.3.23-2 Package's Recommends field is empty. Package's Suggests field is empty.
Bug#852324: closed by Ben Hutchings (Re: [xen] x86/mm: Found insecure W+X mapping)
On Fri, 2018-11-02 at 04:53 +0100, Diederik de Haas wrote: > On woensdag 31 oktober 2018 04:27:04 CET you wrote: > > Version: 4.17~rc3-1~exp1 > > > > This was fixed upstream in Linux 4.17-rc1. > > > > Ben. > > You are awesome :) > > I was/am on the verge of upgrading that system from Stretch to Buster, which > would upgrade both Xen (to 4.11) and the kernel (some which would include the > fix). > Would it be useful to first upgrade just the kernel (and leave Xen at 4.8) to > verify it is indeed also fixed on my system? You should be able to do that if you want. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Bug#912692: httping FTCBFS: clang dependencies unsatisfiable
Hi. On 3 November 2018 3:02:29 AM IST, Helmut Grohne wrote: >Source: httping >Version: 2.5-3 >Tags: patch >User: helm...@debian.org >Usertags: rebootstrap > >httping fails to satisfy its cross build dependencies, because clang >cannot be satisfied. As it happens, httping uses scan-build from clang, >but it only does so for testing. When the build is performed with >DEB_BUILD_OPTIONS=nocheck (as is usually being done for cross >compilation), the dependency is not used. Please annotate the clang >dependencies accordingly. The attached patch implements that. > >Helmut Thanks for the patch. Please update the bug number in changelog and go ahead with NMU :) . I am little busy on this weekend. Thanks. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#907893: elpa-ess: R-initialize-on-start looks for .load.R in the wrong place
Hi Marcelo,
On 2 November 2018 at 22:02, Marcelo Laia wrote:
| Hi!
|
| I would like to contribute.
|
| dpkg -l elpa-ess
|
| ii elpa-ess 18.10-1-2all Emacs mode for statistical
programm
|
| M-x ess-version on emacs show me:
|
| ess-version: 17.11 [] (loaded from /usr/share/emacs/site-lisp/)
Then you have two different versions. The 18.10-1-2, ie my second revision in
packaging of 18.10-1 upstream, should show 18.10-1. It does for me:
ess-version: 18.10-1 [Released git: 1c4253cb4700] (loaded from
/usr/share/emacs25/site-lisp/elpa/)
| However, I continue having the issue:
|
| load ESSR: + + + Error in file(filename, "r", encoding = encoding) :
| cannot open the connection
| In addition: Warning message:
| In file(filename, "r", encoding = encoding) :
| cannot open file ’/usr/share/ess/etc/ESSR/R/.load.R’: No such file or
| directory
|
| A find in my debian testing box show:
|
| root@me:~# find / -name ".load.R"
| /usr/share/emacs/site-lisp/elpa-src/ess-18.10snapshot1/etc/ESSR/R/.load.R
| root@me:~#
|
| After do M-x R in emacs I try to search a help to a function. i.e. function
| apply
|
| > ?apply
|
| Error in .ess.help("apply") :
| não foi possível encontrar a função ".ess.help"
|
| In English is something like this:
|
| Error in .ess.help("apply") :
| is not possible to found function ".ess.help"
|
| Any workaround?
"Works here". On '?apply' I get the help page.
That the 17.11 is still there is suspicous. Did you ever install directly
from ELPA via 'M-x package-install' ? Can you look ing ~/.emacs.d/elpa/ ?
Also do an ls in the current ESS directory, ie
/usr/share/emacs/site-lisp/elpa-src/ess-18.10snapshot1/ and try 'locate' on
some of the files, ie 'locate ess-custom.el'. Do you have it somewhere else?
When I do that here (and block out /home and my Debian sources) I get
edd@rob:~$ locate ess-custom.el | grep -v home
/usr/share/emacs/site-lisp/elpa-src/ess-18.10snapshot1/ess-custom.el
/usr/share/emacs25/site-lisp/elpa/ess-18.10snapshot1/ess-custom.el
/usr/share/emacs25/site-lisp/elpa/ess-18.10snapshot1/ess-custom.elc
edd@rob:~$
which is normal: one installed, one sym-linked and one compiled to .elc.
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#912705: ITP: wsgiproxy2 -- A WSGI Proxy with various http client backends
Package: wnpp Severity: wishlist Owner: Jelmer Vernooij * Package name: wsgiproxy2 Version : 0.4.5 Upstream Author : Gael Pasgrimaud * URL : https://github.com/gawel/WSGIProxy2/ * License : MIT Programming Lang: Python Description : A WSGI Proxy with various http client backends WSGI Proxy implementation that provides a WSGI shim and forwards request over HTTP to another HTTP server. (This is an optional dependency of python3-webtest) -- Jelmer Vernooij PGP Key: https://www.jelmer.uk/D729A457.asc signature.asc Description: PGP signature
Bug#912706: mousepad: Checkmarks in View menu only appear on hover
Package: mousepad Version: 0.4.0-4 Severity: minor Dear Maintainer, Under the "View" menu, there are toggles for "Line Numbers", "Menubar", "Toolbar" and "Statusbar". When any of these are enabled, a checkmark is shown beside their respective label. However, the checkmarks only appear when the mouse cursor hovers over the respective buttons. When my cursor hovers over the button, a white checkmark appears. In my current environment, the dropdown menu's background is white, and items I hover over have a brown background. It is possible that the checkmark being rendered without the hover, but is white in colour, and thus invisible on a white background. In that case, making the checkmark black instead might be a suitable solution. -- System Information: Debian Release: 9.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-7-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mousepad depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1 ii libc62.24-11+deb9u3 ii libglib2.0-0 2.50.3-2 ii libgtk2.0-0 2.24.31-2 ii libgtksourceview2.0-02.10.5-3 ii libpango-1.0-0 1.40.5-1 mousepad recommends no packages. mousepad suggests no packages. -- no debconf information
Bug#911323: [Pkg-roundcube-maintainers] Bug#911323: Inline Images not displaying
On 2018-11-02 19:08, Guilhem Moulin wrote: Does your browser console mention that the site's CSP is blocking remote images? Yes, it does. Thank you! I am embarrassed to admit that my Content Security Policy was indeed the problem. I'm very sorry to have wasted your time. Please close this bug report. Thanks!
Bug#907260: [Pkg-roundcube-maintainers] Bug#907260: roundcube: database table `session` is never cleaned and grows without limit
Control: severity -1 wishlist
Control: retitle -1 roundcube: database table `session` is never cleaned and
grows without limit on nginx
Hi,
On Sat, 25 Aug 2018 at 16:19:06 +0200, Symphorien Gibol wrote:
> Debian disables it by setting session.gc_probability to 0
Upstream's ‘.htaccess’ file sets it to one, however:
$ grep -F session.gc_ .htaccess
php_value session.gc_maxlifetime 21600
php_value session.gc_divisor 500
php_value session.gc_probability 1
nginx doesn't honor that file, but it's not auto-configured by the
package's postinst script either, so nginx users are “on their own” in
that regard (hence lowering the severity to ‘wishlist’) :-P
I use the following snippet to pass these values to php-fpm and have one
every 500 requests (on average) trigger the GC and clean up expired
(>6h) sessions.
location = /index.php {
include snippets/fastcgi-php.conf;
fastcgi_param PHP_VALUE "[…]
session.gc_maxlifetime=21600
session.gc_divisor=500
session.gc_probability=1";
[…]
}
Cf. also https://github.com/roundcube/roundcubemail/issues/3573 .
Cheers,
--
Guilhem.
signature.asc
Description: PGP signature
Bug#911248: globus-gass-copy-progs: copy fails with some SSL errors
Hey Mattias. Thanks :-) Since you're also the voms-client maintainer, couldn't you perhaps modify that already so that it defaults to 2048 (or yet better 4096)? Cheers, Chris.
Bug#912557: Removal of British hyphenation patterns from TeX Live
The UK hyphenations patterns must stay within TeXlive, that's a given. So let's change the license on the pattern files. As co-creator of the file, I hereby agree with the MIT license. I don't know if Graham Toal, the person who worked with me on producing these patterns, can be reached. I'll try. I am certain it was Graham's intention, like mine, that these patterns should always be freely available to everyone. Since Phil Taylor is the official custodian of these patterns, perhaps he should also give his assent. Do you want me to edit the file appropriately? Or will Phil, or you, Mojca? Thanks for bringing this to my attention! Best, Dominik On Thu, 1 Nov 2018 at 06:11, Mojca Miklavec wrote: > Dear Dominik, > > According to Debian we will probably have to delete the British > hyphenation patterns from TeX Live unless the licence changes. See: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912557 > > In general it is becoming increasingly problematic to use custom > (free-text) licences for each individual file. (It's problematic > enough to keep up distributions of millions of different files with > well-established licences, let alone having each individual lawyer > check whether the licence in file X is compatible with the licence in > file Y for N^2 combinations of those and ever increasing N.) > > A while ago we started suggesting the pattern authors to agree with > the MIT licence, but some other licences might be acceptable as well > (note that LPPL in particular is not acceptable for a number of > projects). > > Best regards, > Mojca >
Bug#907893: elpa-ess: R-initialize-on-start looks for .load.R in the wrong place
Hi!
I would like to contribute.
dpkg -l elpa-ess
ii elpa-ess 18.10-1-2all Emacs mode for statistical programm
M-x ess-version on emacs show me:
ess-version: 17.11 [] (loaded from /usr/share/emacs/site-lisp/)
However, I continue having the issue:
load ESSR: + + + Error in file(filename, "r", encoding = encoding) :
cannot open the connection
In addition: Warning message:
In file(filename, "r", encoding = encoding) :
cannot open file ’/usr/share/ess/etc/ESSR/R/.load.R’: No such file or
directory
A find in my debian testing box show:
root@me:~# find / -name ".load.R"
/usr/share/emacs/site-lisp/elpa-src/ess-18.10snapshot1/etc/ESSR/R/.load.R
root@me:~#
After do M-x R in emacs I try to search a help to a function. i.e. function
apply
> ?apply
Error in .ess.help("apply") :
não foi possível encontrar a função ".ess.help"
In English is something like this:
Error in .ess.help("apply") :
is not possible to found function ".ess.help"
Any workaround?
--
Laia, ML
Bug#872381: dpkg-dev: optimize Makefile snippets for debian/rules
Package: dpkg-dev Version: 1.19.2 Followup-For: Bug #872381 Hi. This new version improves the readability in various aspects, and should be easyer to review. It fixes a difference with the current version in dpkg-dev by exporting all dpkg-architecture variables. Is there anything that I can do to help merging these changes? dpkg-patches2.tar.gz Description: application/gzip
Bug#912704: RFS: python-tinycss/0.4-2
Package: sponsorship-requests Severity: normal Hi, I'm looking for a sponsor to upload a new release 0.4-2 of python-tinycss. This fixes the speedups extension not building on Python 3.7 (see #910751). I uploaded the package to mentors: https://mentors.debian.net/package/python-tinycss The Git repository is here: https://salsa.debian.org/python-team/modules/python-tinycss Changes since the last upload: [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field * Convert git repository from git-dpm to gbp layout * Use 'python3 -m sphinx' instead of sphinx-build for building docs [ Felix Krull ] * d/rules: remove bundled speedups.c before building (closes: #910751) Regards, Felix
Bug#912703: CPU% is limit to 100% when real usage is above 600% because threads
Package: sysstat Version: 11.4.3-2 Severity: important A serious bug that limit CPU% to 100.0 was introduced in 11.3.2 commit of the bug ( https://github.com/sysstat/sysstat/commit/52977c479d3de1cb2535f896273d518326c26722 ) This change was reversed in 11.7.3 the resolution ( https://github.com/sysstat/sysstat/commit/a63e87996fd5a214ca7e7c511c713877d8d94300 ) More https://github.com/sysstat/sysstat/issues/73#issuecomment-377677466 Because of this, pidstat report 100% for a processs that use more than 100% of a core . -- Erwan MAS
Bug#912656: ITS: python-fs
Hi Mattia, I am currently not the team member of DPMT yet, hence the request. I am going to request to join the team right now. Though I am packaging several Python packages, these are maintained under Debian Fonts Task Force because those are packages to build fonts. Thanks, Yao Wei On Fri, Nov 02, 2018 at 05:27:09PM +0100, Mattia Rizzolo wrote: > I'm confused here, this package is already maintained by DPMT, with it > in Uploaders. Team members can already freely upload it; sure it is in > Uploaders only so you'd need to give the maintainer a heads up, but you > need not block on this, much less go through the ITS process. > > Also, the maintainer janos is already being tracked by the MIA team, > despite being not exactly responsive there either. > > I recommend you just go ahead and do a team upload, and if you really > wish so also move around Maintainer/Uploaders (and put yourself in it). signature.asc Description: PGP signature
Bug#912702: RFS: gnome-mastermind/0.3.1-3 [QA]
Package: sponsorhip-requests Severity: normal Dear mentors, I am looking for a sponsor for a QA upload of the package "gnome-mastermind". * Package name: gnome-mastermind Version : 0.3.1-3 Upstream Author : Filippo Argiolas * URL : https://www.autistici.org/gnome-mastermind/ * License : GPL-2+ Section : games It builds this binary package: gnome-mastermind - Mastermind™ clone for GNOME To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gnome-mastermind Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gnome-mastermind/gnome-mastermind_0.3.1-3.dsc Or obtain the Git repository with: git clone g...@salsa.debian.org:debian/gnome-mastermind.git Changes since the last upload: * QA upload. * debian/source/format: New file; set format to 3.0 (quilt). * debian/patches/01_docs.diff: Add description. Patch Makefile.am instead of Makefile.in. Add TODO to doc_DATA. * debian/patches/use-yelp-tools.patch: New; move away from the deprecated gnome-doc-utils (Closes: #829977). * debian/patches/gsettings-port.patch: New; switch from GConf to GSettings (Closes: #886075). * debian/patches/no-overlinking.patch: New; avoid linking the needed libraries twice. * debian/patches/gtk3-port.patch: New; port to GTK+ 3. * debian/patches/desktop-file.patch: New; make .desktop file valid. * debian/patches/series: New file. * debian/compat: Set to 11. * debian/control: Run wrap-and-sort -ast. (Maintainer): Set to the Debian QA Group (O: #826926). (Build-Depends): Bump debhelper requirement to >= 11. Remove cdbs, autotools-dev, docbook-xml, imagemagick, gnome-doc-utils, libxml-parser-perl and libgconf2-dev. Add intltool and yelp-tools. Replace libgtk2.0-dev with libgtk-3-dev. Remove obsolete version requirements for libglib2.0-dev and pkg-config. (Recommends): Add gconf2 for data migration's sake. (Description): Extend. (Vcs-Git, Vcs-Browser): Add. (Standards-Version): Claim compliance with 4.2.1 as of this release. * debian/rules: Rewrite for plain dh; enable hardening. * debian/install: Delete. * debian/menu: Delete as required by current Policy. * debian/gnome-mastermind.6: A brand new one. * debian/manpages: New file; install it. * debian/watch: Replace with a fake one as Gna! is gone. * debian/changelog: Whitespace cleanup. * debian/copyright: Rewrite in copyright-format 1.0.
Bug#912701: xul-ext-noscript: conffiles not removed
Package: xul-ext-noscript
Version: 10.1.9.6-1
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate
The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete conffiles on upgrade.
https://www.debian.org/doc/debian-policy/ch-files.html#s-config-fileshttps://manpages.debian.org/man/1/dh_installdeb
This bug report brought to you by adequate:
http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/
$ pkg=xul-ext-noscript ; adequate $pkg ; dpkg-query -W -f='${Conffiles}\n' $pkg
| grep obsolete
xul-ext-noscript: obsolete-conffile /etc/xul-ext/noscript.js
/etc/xul-ext/noscript.js 58cd7fa732bacd1b562c23f2d304d8d4 obsolete
-- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8),
LANGUAGE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages xul-ext-noscript depends on:
ii webext-noscript 10.1.9.6-1
xul-ext-noscript recommends no packages.
xul-ext-noscript suggests no packages.
-- no debconf information
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#911802: Re: Bug#911802: ITP: kovri -- C++ I2P router
> That is irrelevant because this new package won't go into Debian 9. Ok, that's good news then. Static compilation won't be necessary with a Boost 1.66+ system package. pEpkey.asc Description: application/pgp-keys
Bug#912700: how-can-i-help: add suggestions for helping fix security issues
Package: how-can-i-help Version: 16 Severity: wishlist The security tracker contains information about security issues. Not all of these issues will have bug reports and not all of the bugs will be RC, which means that many security issues will not be represented in the how-can-i-help output. Folks who are security-minded might be interested in helping out with fixing these issues. Another tool that looks at the security tracker data is debsecan, you could probably use the same data as it does. https://security-tracker.debian.org/ https://sources.debian.org/src/debsecan/unstable/ -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#912698: yowsup-cli: website link mentioned in manpage broken
Package: yowsup-cli Version: 2.5.7-4 Severity: minor Dear Maintainer, The first website mentioned in the yowsup-cli manpage (the mcclist one) no longer contains a mcclist, but just spam for bitcoin. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages yowsup-cli depends on: ii python3 3.6.7-1 ii python3-axolotl 0.1.42-1 ii python3-dateutil 2.7.3-1 ii python3-libxml2 2.9.4+dfsg1-7+b1 ii python3-yowsup2.5.7-4 yowsup-cli recommends no packages. yowsup-cli suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#912699: fontconfig: FTBFS on hurd-i386
Package: fontconfig
Version: 2.13.1-1
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
Hello,
fontconfig currently FTBFS on hurd-i386 due to inconditionnal PATH_MAX
usage. The attached patch fixes this.
The current fontconfig available for hurd-i386 segfaults during the d-i
build (see
https://d-i.debian.org/daily-images/hurd-i386/20181101-01:27/build_cdrom_grub.log
) while version 2.13.1-1 does not, so we'd like to have this fixed soon
enough :)
Samuel
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'),
(500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500,
'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1,
'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages fontconfig depends on:
ii fontconfig-config 2.13.1-1
ii libc6 2.27-6
ii libfontconfig1 2.13.1-1
ii libfreetype6 2.8.1-2
fontconfig recommends no packages.
fontconfig suggests no packages.
-- no debconf information
--
Samuel
t1 faich
les programmes ils segfaultent jamais quand on veut
-+- #ens-mim en plein débogage -+-
Index: fontconfig-2.13.1/src/fccfg.c
===
--- fontconfig-2.13.1.orig/src/fccfg.c
+++ fontconfig-2.13.1/src/fccfg.c
@@ -2231,7 +2231,7 @@ FcConfigRealFilename (FcConfig *config,
if (n)
{
- FcChar8 buf[PATH_MAX];
+ FcChar8 buf[FC_PATH_MAX];
ssize_t len;
if (sysroot)
Bug#911323: [Pkg-roundcube-maintainers] Bug#911323: Inline Images not displaying
Control: tag -1 moreinfo unreproducible Hi, On Thu, 18 Oct 2018 at 12:24:41 -0500, bkw+1539883...@70mpg.org wrote: > If I then click on the button that reads "Display images", next to the > text "To protect your privacy, remote images are blocked in this > message", the pink boxes go away, but the images are still not shown. This might suggest that your browser refuses to load the images due to a strict Content-Security-Policy. I'm not able to reproduce this with “img-src” CSP source list set to “* data:” [0], at least. Does your browser console mention that the site's CSP is blocking remote images? Cheers, -- Guilhem. [0] https://content-security-policy.com/#source_list signature.asc Description: PGP signature
Bug#907294: completions/dpkg: installing dctrl-tools breaks completion for held packages with -L/--listfiles
On Fri, 2018-11-02 at 14:58 -0300, Gabriel F. T. Gomes wrote: > I have reported the bug upstream [1], and I incorporated your patch to > the git repo of bash-completion [2], however I have not yet produced a > package with the fix... Excellent, thanks for adopting and working on bash-completion, it is an important package that needs to be well maintained. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#909442: outguess: patch for #909442
Em qua, 31 de out de 2018 às 06:33, Frédéric Bonnard escreveu: > > Hi Eriberto, > > the errors you see in the builds of 2018-10-29 are the same issues : I > initially tried to reproduce the bug but failed, so I asked a give back. > The new errors you see just occurred during that rebuild but are not > different issues. > So the merge request I sent should fix all the errors on amd64 and power > arches. > > F. Yeap! Thanks. I uploaded to experimental few days ago[1]. [1] https://buildd.debian.org/status/package.php?p=outguess=experimental Now, arm64 fails, so I can't upload to unstable. Do you think that it is a new issue from makefile.unix? Cheers, Eriberto
Bug#912697: libtwatch-perl: Homepage not valid
Package: libtwatch-perl Severity: minor Dear Maintainer, The homepage listed (http://twatch.rshadow.ru/) in the package is not available anymore. http://rshadow.ru does work, and following things a bit, I arreived to: https://github.com/rshadow/twatch, which would seem like an good homepage to state in the package. -- System Information: Debian Release: 7.11 APT prefers oldoldstable-updates APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash
Bug#912560: dh_auto_test: run `meson test` instead of `ninja test` in new compat level or with an option
On Thu, Nov 1, 2018 at 1:21 PM Simon McVittie wrote: > Note that because `ninja test` and `meson test` take different command-line > options, this would be an incompatible change unless the package maintainer > has opted in somehow, either with a compat level upgrade or a new > command-line option. `ninja test` actually does not take any command line arguments. You can only add arguments that would go to Ninja, not to the test suite runner (this is an intentional design principle of Ninja). > (X-Debbugs-Cc to Meson maintainers: do you agree that this would be a good > change?) Yes, this seems reasonable.
Bug#912401: network-manager 1.6.2-3+deb9u2 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: network-manager Version: 1.6.2-3+deb9u2 Explanation: fix out-of-bounds heap write in dhcpv6 option handling [CVE-2018-15688] and various other issues in the sd-network based dhcp=internal plugin
Bug#910821: python-django 1.10.7-2+deb9u3 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: python-django Version: 1.10.7-2+deb9u3 Explanation: default to supporting Spatialite >= 4.2
Bug#912462: xorg-server 1.19.2-1+deb9u5 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: xorg-server Version: 1.19.2-1+deb9u5 Explanation: glx: do not pick sRGB config for 32-bit RGBA visual - fixes various blending issues with kwin and Mesa >= 18.0 (i.e. Mesa from stretch-backports)
Bug#912169: systemd 232-25+deb9u6 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: systemd Version: 232-25+deb9u6 Explanation: dhcp6: Make sure we have enough space for the DHCP6 option header [CVE-2018-15688]
Bug#907865: python-imaplib2 2.55-1+deb9u2 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: python-imaplib2 Version: 2.55-1+deb9u2 Explanation: install the correct module for Python 3; don't use TIMEOUT_MAX
Bug#910065: libmail-deliverystatus-bounceparser-perl 1.542+repacked-1~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: libmail-deliverystatus-bounceparser-perl Version: 1.542+repacked-1~deb9u1 Explanation: remove non-distributable sample spam and viruses
Bug#909953: soundconverter 3.0.0~alpha1+git20151209-1+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: soundconverter Version: 3.0.0~alpha1+git20151209-1+deb9u1 Explanation: fix opus vbr setting
Bug#908357: libseccomp 2.3.1-2.1+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: libseccomp Version: 2.3.1-2.1+deb9u1 Explanation: add support for Linux 4.9 syscalls: preadv2, pwritev2, pkey_mprotect, pkey_alloc and pkey_free; add support for statx
Bug#912696: emacs: default emacs X11 window is very small
Package: emacs Version: 1:25.2+1-11 Severity: normal When starting emacs under X11, the default window is very small. The application creates the window with a size that seems to be consistent with previous releases of emacs, but it resizes to where only three lines of the welcome text are visible. The window can be manually resized using the mouse. The default sizing behavior, however, is new to this release of emacs v/s the version on stretch. I tested this with no ~/.Xresources, no ~/.emacs and no ~/.emacs.d to verify that this behavior is not caused by some customized setting. My X11 server is XQuartz 2.7.11 (xorg-server 1.18.4) on Mac OS 10.13.6. This X11 server works fine with the stretch version of emacs. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages emacs depends on: ii emacs-gtk 1:25.2+1-11 emacs recommends no packages. emacs suggests no packages. -- no debconf information
Bug#912170: grub2 2.02~beta3-5+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: grub2 Version: 2.02~beta3-5+deb9u1 Explanation: grub-mknetdir: Add support for ARM64 EFI; change the default TSC calibration method to pmtimer on EFI systems
Bug#910398: gnupg2 2.1.18-8~deb9u3 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: gnupg2 Version: 2.1.18-8~deb9u3 Explanation: security fixes; backport functionality required for new enigmail
Bug#912695: apt-show-versions: breaks "apt-get update" and uninstallable after Perl 5.28 upgrade
Package: apt-show-versions Version: apt-show-versions Severity: critical Justification: breaks unrelated software Dear Maintainer, after the Perl 5.28 upgrade, if apt-show-versions (0.22.8) is installed, "apt- get update" fails with: # apt-get update Hit:1 https://repo.skype.com/deb stable InRelease Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease Hit:3 http://ftp.debian.org/debian sid InRelease Hit:4 http://dl.google.com/linux/chrome/deb stable Release Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux- gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'test -x /usr/bin/apt-show-versions || exit 0 ; apt-show-versions -i' E: Sub-process returned an error code The error can be reproduced by running: # apt-show-versions -i Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux- gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. Workaround is to uninstall apt-show-versions with: apt-get purge apt-show-versions Following this removal, "apt-get update" works normally. Attempting to reinstall apt-show-versions fails with: # apt-get install apt-show-versions Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: apt-show-versions 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 32.1 kB of archives. After this operation, 93.2 kB of additional disk space will be used. Get:1 http://ftp.debian.org/debian sid/main amd64 apt-show-versions all 0.22.8 [32.1 kB] Fetched 32.1 kB in 3s (10.2 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done Selecting previously unselected package apt-show-versions. (Reading database ... 257503 files and directories currently installed.) Preparing to unpack .../apt-show-versions_0.22.8_all.deb ... Unpacking apt-show-versions (0.22.8) ... Setting up apt-show-versions (0.22.8) ... ** initializing cache. This may take a while ** Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux- gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. dpkg: error processing package apt-show-versions (--configure): installed apt-show-versions package post-installation script subprocess returned error exit status 25 Processing triggers for man-db (2.8.4-2+b1) ... Errors were encountered while processing: apt-show-versions E: Sub-process /usr/bin/dpkg returned an error code (1) Clean up with: apt-get purge apt-show-versions Kind regards, Ben. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-show-versions depends on: ii apt 1.7.0 ii libapt-pkg-perl 0.1.34+b1 ii perl [libstorable-perl] 5.28.0-3 apt-show-versions recommends no packages.
Bug#912629: stretch-pu: package espeakup/1:0.80-5+deb9u2
Adam D. Barratt, le ven. 02 nov. 2018 21:12:37 +, a ecrit: > I'm OK with this, but because espeakup builds a udeb this officially > needs a KiBi-ack (although fwiw I'm assuming the changes don't actually > end up affecting the installer's use). Indeed, the systemd service is not used inside the installer. Samuel
Bug#912694: psensor FTCBFS: perl dependency unsatisfiable
Source: psensor Version: 1.1.5-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap psensor fails to cross build from source, because its dependency on (the host architecture) perl is unsatisfiable. It produces a conflict with the build architecture perl required by essential. It actually does want a build architecture perl and cross builds successfully once you annotate the dependency with :native. Please consider applying the attached patch. Helmut diff --minimal -Nru psensor-1.1.5/debian/changelog psensor-1.1.5/debian/changelog --- psensor-1.1.5/debian/changelog 2016-06-06 20:25:02.0 +0200 +++ psensor-1.1.5/debian/changelog 2018-11-02 22:34:03.0 +0100 @@ -1,3 +1,10 @@ +psensor (1.1.5-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Annotate perl build dependency with :native. (Closes: #-1) + + -- Helmut Grohne Fri, 02 Nov 2018 22:34:03 +0100 + psensor (1.1.5-1) unstable; urgency=medium * New upstream release diff --minimal -Nru psensor-1.1.5/debian/control psensor-1.1.5/debian/control --- psensor-1.1.5/debian/control2016-06-06 20:24:39.0 +0200 +++ psensor-1.1.5/debian/control2018-11-02 22:34:01.0 +0100 @@ -22,7 +22,7 @@ libsensors4-dev, libudisks2-dev [!kfreebsd-any], libxnvctrl-dev [i386 amd64] | nvidia-settings [i386 amd64], - perl + perl:native Standards-Version: 3.9.8 Vcs-Browser: http://wpitchoune.net/gitweb/?p=psensor-pkg-debian.git Vcs-Git: git://git.wpitchoune.net/psensor-pkg-debian.git
Bug#912693: streamtuner2: Won't start - python crash
Package: streamtuner2
Version: 2.2.0+dfsg-1
Severity: normal
Dear Maintainer,
streamtuner2 didn't start from the Multimedia Applications menu. Trying to
start it from the command line showed this:
streamtuner2
Traceback (most recent call last):
File "/usr/bin/streamtuner2", line 12, in
import st2
File "/usr/share/streamtuner2/st2.py", line 55, in
from config import *
File "/usr/share/streamtuner2/config.py", line 374, in
conf = ConfigDict()
File "/usr/share/streamtuner2/config.py", line 85, in __init__
self.defaults()
File "/usr/share/streamtuner2/config.py", line 116, in defaults
"audio/mpeg": self.find_player(),
File "/usr/share/streamtuner2/config.py", line 179, in find_player
if find_executable(bin.split()[0]):
File "/usr/share/streamtuner2/compat2and3.py", line 72, in find_executable
exists = [os.path.exists(dir+"/"+bin) for dir in
os.environ.get("PATH").split(":")+["/"]]
NameError: name 'os' is not defined
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-2-amd64 (SMP w/2 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)
LSM: AppArmor: enabled
Versions of packages streamtuner2 depends on:
ii python3 3.6.7-1
ii python3-gi3.30.1-2
ii python3-lxml 4.2.5-1
ii python3-pil 5.3.0-1
ii python3-pyquery 1.2.9-3
ii python3-requests 2.20.0-2
streamtuner2 recommends no packages.
Versions of packages streamtuner2 suggests:
pn audacious
pn totem
ii vlc1:3.0.4-dmo4
-- no debconf information
Bug#912692: httping FTCBFS: clang dependencies unsatisfiable
Source: httping Version: 2.5-3 Tags: patch User: helm...@debian.org Usertags: rebootstrap httping fails to satisfy its cross build dependencies, because clang cannot be satisfied. As it happens, httping uses scan-build from clang, but it only does so for testing. When the build is performed with DEB_BUILD_OPTIONS=nocheck (as is usually being done for cross compilation), the dependency is not used. Please annotate the clang dependencies accordingly. The attached patch implements that. Helmut diff --minimal -Nru httping-2.5/debian/changelog httping-2.5/debian/changelog --- httping-2.5/debian/changelog2018-08-03 06:52:16.0 +0200 +++ httping-2.5/debian/changelog2018-11-02 22:17:08.0 +0100 @@ -1,3 +1,10 @@ +httping (2.5-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Annotate clang dependencies with . (Closes: #-1) + + -- Helmut Grohne Fri, 02 Nov 2018 22:17:08 +0100 + httping (2.5-3) unstable; urgency=medium * Switch build-depend back to (unversionned)clang-tools diff --minimal -Nru httping-2.5/debian/control httping-2.5/debian/control --- httping-2.5/debian/control 2018-08-03 06:52:16.0 +0200 +++ httping-2.5/debian/control 2018-11-02 22:17:08.0 +0100 @@ -4,8 +4,8 @@ Maintainer: Abhijith PA Build-Depends: debhelper (>= 11), libssl-dev, - clang, - clang-tools, + clang , + clang-tools , libncursesw5-dev, libncurses5-dev, libfftw3-dev,
Bug#892080: bash-completion: cvs log ($mode=log) case disappeared?
On 18 Mar 2018, Gabriel F. T. Gomes wrote: >Thanks for pointing this out. I sent a patch for upstream review at: >https://github.com/scop/bash-completion/pull/194. The pull request has been integrated, but since it's not in an upstream release, yet, I added the patch to Debian (notice that I still did not upload the package to the Debian Archive... this message is just to let you know that the fix is in the git repository [1] and will be available in version 2.8-2) [1] https://salsa.debian.org/debian/bash-completion/commit/7f8a7f05ec56055bc14f7d179b4022f7ddd3d586
Bug#865881: Adding ET to debian
Hey, We are working on supporting all shells in our v6 branch that you can track here: https://github.com/MisterTea/EternalTerminal/tree/v6 . We have thousands of users, so changing the protocol isn't something that we can do lightly, but we want to support fish and other shells, so we will definitely roll it out once it's ready. But, it would be a shame if we can't get this into Debian main just because we only support bash/zsh. That doesn't seem like a good reason to block the package. Jason Gauci.
Bug#904700: /etc/profiles.d/bash_completion.sh or the sourced script break sddm login
On 02 Nov 2018, Alf Gaida wrote: >Im fine with - i didn't really dig into it, d-qt-kde does an stopped >sourcing these files in case the shell is fish - that kind of solved >the issue, since fish is not posix compat if i understand it right. > >Thank you for getting back on this. Thank you for reporting. If you change your mind (or get more information about it), please do not hesitate to reopen the bug.
Bug#912629: stretch-pu: package espeakup/1:0.80-5+deb9u2
Control: tags -1 + confirmed d-i On Fri, 2018-11-02 at 00:49 +0100, Samuel Thibault wrote: > We would like to upload the attached change to espeakup in Stretch. > > The story is that the init.d script for espeakup used to avoid > starting espeakup if the kernel speakup_soft module is not loaded. > When a systemd service was introduced during for Stretch, that part > was not ported (making a service automatically disabled when a kernel > module is not loaded does not seem to be implemented in systemd), > which means that when installing the espeakup package on a system > which doesn't have speakup_soft loaded, the service start fails, and > thus the package fails to configure. We do not really want to make > the espeakup daemon itself stop reporting an error in such case, and > it seems that users' preference is that the espeakup service just > loads the require module itself anyway, which is what is implemented > in the attached changes and has been used in sid for a week then in > testing for a week. I'm OK with this, but because espeakup builds a udeb this officially needs a KiBi-ack (although fwiw I'm assuming the changes don't actually end up affecting the installer's use). Regards, Adam
Bug#912423: codelite: fails to start: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Control: reassign -1 libwxsqlite3-3.0-0 3.4.1~dfsg-2 Control: tags -1 - confirmed Control: retitle -1 libwxsqlite3-3.0-0: switch to gtk3 breaks the ABI Control: affects -1 src:codelite src:maitreya Hi, On 31/10/2018 13:15, James Cowgill wrote: > Control: severity -1 grave > Control: tags -1 confirmed > Control: retitle -1 codelite: fails to start: GTK+ 2.x symbols detected. > Using GTK+ 2.x and GTK+ 3 in the same process is not supported > > Hi, > > On 31/10/2018 11:50, Larus wrote: >> Package: codelite >> Version: 10.0+dfsg-3 >> Severity: important >> >> Dear Maintainer, >> when starting codelite the process shuts down directly when starting. >> Reason: >> (codelite:1081): Gtk-ERROR **: 12:48:04.992: GTK+ 2.x symbols detected. >> Using GTK+ 2.x and GTK+ 3 in the same process is not supported >> Sadly I haven't been able to resolve this. > > Indeed I cannot start codelite in unstable either. As well as the above, > I also get a lot of other errors when trying to run it (below). This was caused by wxsqlite3 switching to GTK+3. This comes into conflict with codelite which is built against GTK+2. As the error above states, you cannot load the GTK+2 and GTK+3 libraries into the same process. This change is pretty much guaranteed to break all reverse dependencies of wxsqlite3 (because any existing rdep must have been compiled against GTK+2 to function). I think it makes most sense to handle this like a normal package transition and either rename the package, or add extra packages (like wxwidgets3.0 did). If you don't do that, you'll need to add a Breaks for all your rdeps (but this won't help if any user programs outside Debian link against wxsqlite). In theory, codelite does support building against GTK+3, but I haven't tried it. The other rdep is maitreya which doesn't link against any GTK+ version directly, so in theory changing the build dependencies to the GTK+3 versions should "Just Work" :) This means you can probably get away with a rename instead of adding extra packages. It's unfortunate this took a month to discover. I guess there's not many people using these packages :/ James signature.asc Description: OpenPGP digital signature
Bug#912691: certmonger FTCBFS: configure.ac hard codes the wrong pkg-config
Source: certmonger
Version: 0.79.6-1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap
certmonger fails to cross build from source, because configure.ac hard
codes the wrong pkg-config in a few places. The attached patch fixes
that and makes certmonger cross buildable. Please consider applying it.
Helmut
--- certmonger-0.79.6.orig/configure.ac
+++ certmonger-0.79.6/configure.ac
@@ -152,6 +152,7 @@
AC_DEFINE_UNQUOTED(CM_DBUS_RECONNECT_TIMEOUT,30,
[Define to the amount of time to wait between attempts to reconnect to the message bus if we get disconnected.])
+PKG_PROG_PKG_CONFIG
if ! ${configure_dist_target_only:-false} ; then
AC_CHECK_HEADERS(sys/types.h sys/socket.h linux/types.h linux/netlink.h linux/rtnetlink.h,,,[
#ifdef HAVE_SYS_TYPES_H
@@ -175,13 +176,13 @@
AC_ARG_WITH(session-bus-services-dir,
AS_HELP_STRING([--with-session-bus-services-dir=],[directory to install session bus configuration]),
SESSIONBUSSERVICESDIR=$withval,
- SESSIONBUSSERVICESDIR=`pkg-config --variable=session_bus_services_dir dbus-1 2> /dev/null | sed -e "s|^${datadir}|\${datadir}|g" -e "s|^${datarootdir}|\${datarootdir}|g" -e "s|^${prefix}/share|\${datadir}|g"`)
+ SESSIONBUSSERVICESDIR=`$PKG_CONFIG --variable=session_bus_services_dir dbus-1 2> /dev/null | sed -e "s|^${datadir}|\${datadir}|g" -e "s|^${datarootdir}|\${datarootdir}|g" -e "s|^${prefix}/share|\${datadir}|g"`)
AC_SUBST(SESSIONBUSSERVICESDIR)
AM_CONDITIONAL(SESSIONBUS,test x$SESSIONBUSSERVICESDIR != xno)
AC_ARG_WITH(system-bus-services-dir,
AS_HELP_STRING([--with-system-bus-services-dir=],[directory to install system bus configuration]),
SESSIONBUSSERVICESDIR=$withval,
- SYSTEMBUSSERVICESDIR=`pkg-config --variable=system_bus_services_dir dbus-1 2> /dev/null | sed -e "s|^${datadir}|\${datadir}|g" -e "s|^${datarootdir}|\${datarootdir}|g" -e "s|^${prefix}/share|\${datadir}|g"`)
+ SYSTEMBUSSERVICESDIR=`$PKG_CONFIG --variable=system_bus_services_dir dbus-1 2> /dev/null | sed -e "s|^${datadir}|\${datadir}|g" -e "s|^${datarootdir}|\${datarootdir}|g" -e "s|^${prefix}/share|\${datadir}|g"`)
AC_SUBST(SYSTEMBUSSERVICESDIR)
AM_CONDITIONAL(SYSTEMBUS,test x$SYSTEMBUSSERVICESDIR != xno)
@@ -331,7 +332,7 @@
AM_CONDITIONAL(HAVE_OPENSSL,test x$withopenssl != xno)
if test x$withopenssl != xno ; then
- if pkg-config libcrypto 2> /dev/null ; then
+ if $PKG_CONFIG libcrypto 2> /dev/null ; then
PKG_CHECK_MODULES(OPENSSL,libcrypto)
PKG_CHECK_MODULES(OPENSSL_SSL,libssl libcrypto)
else
@@ -403,7 +404,7 @@
AM_CONDITIONAL(HAVE_NSS,test x$withnss != xno)
if test x$withnss != xno ; then
- if pkg-config mozilla-nss 2> /dev/null ; then
+ if $PKG_CONFIG mozilla-nss 2> /dev/null ; then
PKG_CHECK_MODULES(NSS,mozilla-nss)
else
PKG_CHECK_MODULES(NSS,nss)
@@ -531,7 +532,7 @@
AM_CONDITIONAL(SYSTEMD,test x$SYSTEMD != xno)
AC_SUBST(SYSTEMDSYSTEMUNITDIR)
if test x$SYSTEMD = xyes ; then
- SYSTEMDSYSTEMUNITDIR=`pkg-config --variable=systemdsystemunitdir systemd 2> /dev/null`
+ SYSTEMDSYSTEMUNITDIR=`$PKG_CONFIG --variable=systemdsystemunitdir systemd 2> /dev/null`
AC_MSG_RESULT(will install systemd unit files to $SYSTEMDSYSTEMUNITDIR)
fi
@@ -599,7 +600,7 @@
CFLAGS="$CFLAGSsave"
LIBS="$LIBSsave"
can_dsa=true
- if ! pkg-config --atleast-version=1.0 openssl ; then
+ if ! $PKG_CONFIG --atleast-version=1.0 openssl ; then
# CSR signing appears to be broken in 0.9.8e, so reject < 1.0
can_dsa=false
fi
@@ -800,7 +801,7 @@
PKG_CHECK_MODULES(UUID,uuid)
else
if test x$with_uuid != xno ; then
- if pkg-config uuid ; then
+ if $PKG_CONFIG uuid ; then
PKG_CHECK_MODULES(UUID,uuid)
uuid=yes
fi
Bug#912690: Define maintainer status of ycmd & vim-youcompleteme
Package: ycmd Version: 0+20181101+git600f54d-0.1 Severity: important Control: affects -1 vim-youcompleteme Hi, the recent upload(s) by Sylvestre Ledru were made to ultimatively reduce the amount of different clang versions in Debian. My upload just now tries to fix some problems surfaced by the long period of inactivity. I am going to brush up vim-youcompleteme in the same fashion so that we have a (hopefully) sane base to work with in the future. Still, we had talked about this in #893148 and I still think we have to define who the maintainer(s) of both packages will be in the long run as just placing it in the care of Debian Python Modules Team and hoping for the best might or might not work. @Onur Aslan: You are still recorded as the maintainer – but last time you said "next weekend" and that is a few months ago… :) So, if you intend to keep maintaining the packages no problem, close the bug and be hopefully not too annoyed by Sylvestres and my NMUs! Otherwise, or if you aren't sure, another option would be me officially taking over and managing uploads/pull requests and co – or perhaps someone else is reading this and wants to speak up & take over and me (or someone else) doing "just" upload sponsoring if needed. Either is fine by me, we should just get this sorted out – hence the bugreport (not because I like producing paperwork ;) ). Best regards David Kalnischkies signature.asc Description: PGP signature
Bug#912689: libppd FTCBFS: multiple reasons
Source: libppd
Version: 2:0.10-7.3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
libppd fails to cross build from source. The ./configure script is
invoked without the relevant --host flag. dh_auto_configure takes care
of that. Then install -s uses the wrong strip. It is best to avoid
stripping at install time as that breaks generation of -dbgsym packages
by dh_strip. The attached patch makes libppd cross buildable. Please
consider applying it.
Helmut
diff -u libppd-0.10/debian/changelog libppd-0.10/debian/changelog
--- libppd-0.10/debian/changelog
+++ libppd-0.10/debian/changelog
@@ -1,3 +1,12 @@
+libppd (2:0.10-7.4) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_configure pass --host to ./configure.
++ Defer all stripping to dh_strip.
+
+ -- Helmut Grohne Fri, 02 Nov 2018 21:54:39 +0100
+
libppd (2:0.10-7.3) unstable; urgency=medium
* Non-maintainer upload
diff -u libppd-0.10/debian/rules libppd-0.10/debian/rules
--- libppd-0.10/debian/rules
+++ libppd-0.10/debian/rules
@@ -21,9 +21,6 @@
else
CFLAGS += -O2
endif
-ifeq (,$(filter nostrip,$(DEB_BUILD_OPTIONS)))
- INSTALL_PROGRAM += -s
-endif
ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
MAKEFLAGS += -j$(NUMJOBS)
@@ -34,7 +31,7 @@
dh_testdir
# avoid time skews
dh_autoreconf
- ./configure --prefix=/usr --with-glib=2 --mandir=/usr/share/man
+ dh_auto_configure -- --with-glib=2 --libdir='$${prefix}/lib'
touch build-stamp
clean:
Bug#904700: /etc/profiles.d/bash_completion.sh or the sourced script break sddm login
Im fine with - i didn't really dig into it, d-qt-kde does an stopped sourcing these files in case the shell is fish - that kind of solved the issue, since fish is not posix compat if i understand it right. Thank you for getting back on this. Cheers Alf
Bug#912688: dopewars: broken, outdated, embedded copy of AM_PATH_GLIB_2_0
Source: dopewars Version: 1.5.12-19 Severity: important User: helm...@debian.org Usertags: rebootstrap dopewars fails to cross build from source, because it contains a broken, outdated, embedded copy of AM_PATH_GLIB_2_0. The version of the macro in the dopewars uses the wrong pkg-config. The problem is fixed upstream (in glib2.0). Please remove this copy from dopewars. If you insist on keeping it, please register it. See https://wiki.debian.org/EmbeddedCodeCopies for instructions on how to do so. In principle, just removing it from acinclude.m4 should work. Helmut
Bug#906438: nsd initscript improve stop action for chrooted daemon
Hi Harald, I have included your simple fix in git for the next release: https://salsa.debian.org/dns-team/nsd/commit/ea3dafa968dbc3768184fda5da9cc9c3c3506c83 Thanks! Best regards, Markus
Bug#912687: libmspack0: Regression when extracting cabinets using -F option fixed upstream, needs to be patched
Package: libmspack0 Version: 0.8-1 Severity: important Dear Maintainer, * What led up to the situation? A bug was introduced which led to a failure to properly extract cabinets when using -F. * What exactly did you do (or not do) that was effective (or ineffective)? I reported the bug which was then forwarded to the owner of the project. * What was the outcome of this action? The bug was fixed. I am requesting that the fix, located here: https://github.com/kyz/libmspack/commit/2d86d4e70026cd03730ce0b00b12579c2e21620a be ported into the buster/sid packages. And please do let me know if this method of contact is inappropriate for this sort of thing, just trying to figure my way through all of this. :) Thank you. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmspack0 depends on: ii libc6 2.27-8 libmspack0 recommends no packages. libmspack0 suggests no packages. -- no debconf information
Bug#912627: asymptote: Asymptote crashes on attempt to create pdf file
On 02.11.2018 00:22, Dmitry Bogatov wrote: Hi Dmitry, > draw((0, 0) -- (1, 1), opacity(0.7)); > > Here is error: > After removing the opacity statement... > Error: /undefined in .setopacityalpha > Operand stack: > 0.7 > The following line is missing when generating an eps file: 0.7 .setopacityalpha ..and the conversion works fine. I had a further look at google and found the information, that ghostscript recently [1] removed some non-standard extensions, unless option -nosafe is used. I'm not sure, when this happened, b/c my gs 9.20 in Debian stable fails to process this file too. Work around is described on [1] too. Also this function is still mentioned on [2]. The issue in asy is still in 2.47 (probably) and needs to be forwarded. Hilmar [1] https://sourceforge.net/p/asymptote/discussion/409349/thread/f2ecb64b19/?limit=25#f822 [2] https://www.ghostscript.com/doc/current/Language.htm -- #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Bug#905867: Fixed for me
The Wi-Fi card is now working for me with up-to-date packages from testing. I'm not sure which package update fixed it. -- Soren Stoutner Small Business Tech Solutions so...@smallbusinesstech.net 623-262-6169
Bug#912685: debian/rules is not binNMU safe
Source: net-snmp Version: 5.7.3+dfsg-4 Severity: serious Hi, In debian/rules you have the following: UPSTREAM_VERSION = $(shell dpkg-parsechangelog | egrep '^Version:' | cut -f 2 -d ':' | sed 's/ //' | sed 's/~dfsg.*$$//') COMPAT_VERSION = $(UPSTREAM_VERSION)~dfsg [...] override_dh_makeshlibs: dh_makeshlibs -plibsnmp$(LIB_VERSION) -V"libsnmp$(LIB_VERSION) (>= $(COMPAT_VERSION))" When a binNMU is scheduled, UPSTREAM_VERSION is set to 5.7.3+dfsg-4+b1 and then COMPAT_VERSION is set to 5.7.3+dfsg-4+b1~dfsg which is completely boggus All the reverse-dependency will have this boggus version in their generated dependency list. Why aren't you using "dh_makeshlibs -V" or the version macro that are present in /usr/share/dpkg/pkg-info.mk ? Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#912686: flint FTCBFS: configures for the wrong architecture
Source: flint Version: 2.5.2-18 Tags: patch User: helm...@debian.org Usertags: rebootstrap flint fails to cross build from source, because it uses the build architecture compilers. The attached patch fixes that by seeding them from dpkg's buildtools.mk and then passing them to ./configure. It makes flint cross buildable. Please consider applying it. Helmut diff --minimal -Nru flint-2.5.2/debian/changelog flint-2.5.2/debian/changelog --- flint-2.5.2/debian/changelog2018-04-24 23:51:04.0 +0200 +++ flint-2.5.2/debian/changelog2018-11-02 21:02:05.0 +0100 @@ -1,3 +1,10 @@ +flint (2.5.2-18.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Pass CC and CXX to ./configure. (Closes: #-1) + + -- Helmut Grohne Fri, 02 Nov 2018 21:02:05 +0100 + flint (2.5.2-18) unstable; urgency=medium * Add patch to fix FTBFS (Closes: #896470). diff --minimal -Nru flint-2.5.2/debian/rules flint-2.5.2/debian/rules --- flint-2.5.2/debian/rules2018-04-24 23:51:04.0 +0200 +++ flint-2.5.2/debian/rules2018-11-02 21:02:05.0 +0100 @@ -1,6 +1,7 @@ #!/usr/bin/make -f include /usr/share/dpkg/pkg-info.mk +-include /usr/share/dpkg/buildtools.mk EXTRA_SHARED_FLAGS=-Wl,-soname,libflint-$(DEB_VERSION_UPSTREAM).so MAKE_OVERRIDE = AT= QUIET_CXX= QUIET_CC= QUIET_AR= INCS=-I$(CURDIR) \ @@ -29,7 +30,7 @@ # inject flags using configure. let's hope CFLAGS will always be good enough # even for $(CXX) override_dh_auto_configure: - ./configure --prefix="/usr" --with-ntl CFLAGS='$(CPPFLAGS) $(CFLAGS)' + ./configure --prefix="/usr" --with-ntl CC='$(CC)' CXX='$(CXX)' CFLAGS='$(CPPFLAGS) $(CFLAGS)' sed -i Makefile -e "/^FLINT_LIB\>=/s/libflint/libflint-$(DEB_VERSION_UPSTREAM)/" override_dh_auto_build:
Bug#912684: perl-modules-5.28 needs versioned Provides for modules it bundles
Package: perl-modules-5.28 Version: 5.28.0-3 Severity: serious perl-modules-5.28 has Replaces+Breaks: libextutils-parsexs-perl (<< 3.39) This makes libextutils-parsexs-perl in unstable not installable. libextutils-parsexs-perl does have reverse dependencies in unstable, including revers dependencies with versioned dependencies. Versioned Provides for such modules are required.
Bug#911697: at-spi2-core: causes SIGSEGV because of improper quoting of G_LOG_DOMAIN
Hello, Jussi Pakkanen, le ven. 02 nov. 2018 21:38:01 +0200, a ecrit: > On Wed, Oct 24, 2018 at 10:32 AM Samuel Thibault wrote: > > > So the issue is in meson itself: it seems one can't get > > > > compile_args: [ '-DG_LOG_DOMAIN="dbind"' ], > > > > to be correctly interpreted as making G_LOG_DOMAIN #defined to "dbind" > > both for the binary compilation and for the documentation generation. > > > > FTR, this was working with meson 0.47.2-1 (see > > https://buildd.debian.org/status/fetch.php?pkg=at-spi2-core=amd64=2.30.0-2=1536983011=0 > > ), so I guess it's 0.48.0 which broke this. > > Can you test if the commit mentioned in > https://github.com/mesonbuild/meson/issues/4452#issuecomment-434870441 > fixes the issue for you? > > Simply running your build with current Meson trunk is enough to test the > issue. I simply applied the patch on top of my 0.48.1-1 package, and it fixed the documentation build without breaking the binary indeed. Samuel
Bug#912683: openlibm FTCBFS: make install rebuilds for the build architecture
Source: openlibm Version: 0.6.0+dfsg-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap openlibm fails to cross build from source. It successfully builds (dh_auto_build) and the rebuilds objects with the wrong compiler during make install. It turns out that dh_auto_install does not pass a cross compiler along. The Make.inc file derives the ARCH variable from the compiler and then uses that to construct a build directory. Given the unexpected change in $(ARCH), those files go missing and it starts building again (with the wrong compiler). Passing a CC to make install fixes that. Please consider applying the attached patch. Helmut diff --minimal -Nru openlibm-0.6.0+dfsg/debian/changelog openlibm-0.6.0+dfsg/debian/changelog --- openlibm-0.6.0+dfsg/debian/changelog2018-06-21 11:01:29.0 +0200 +++ openlibm-0.6.0+dfsg/debian/changelog2018-11-02 20:48:43.0 +0100 @@ -1,3 +1,10 @@ +openlibm (0.6.0+dfsg-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: make install needs to know CC. (Closes: #-1) + + -- Helmut Grohne Fri, 02 Nov 2018 20:48:43 +0100 + openlibm (0.6.0+dfsg-1) unstable; urgency=medium [ Peter Colberg ] diff --minimal -Nru openlibm-0.6.0+dfsg/debian/rules openlibm-0.6.0+dfsg/debian/rules --- openlibm-0.6.0+dfsg/debian/rules2018-06-21 10:31:16.0 +0200 +++ openlibm-0.6.0+dfsg/debian/rules2018-11-02 20:48:43.0 +0100 @@ -1,6 +1,10 @@ #!/usr/bin/make -f export DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow +-include /usr/share/dpkg/buildtools.mk %: dh $@ + +override_dh_auto_install: + dh_auto_install -- "CC=$(CC)"
Bug#912682: libextutils-parsexs-perl: version is older than Replaces+Breaks in perl-modules-5.28
Package: libextutils-parsexs-perl Version: 3.35-1 Severity: serious The following packages have unmet dependencies: perl-modules-5.28 : Breaks: libextutils-parsexs-perl (< 3.39)
Bug#910755: typo in last mail
s/built a debian/built a deb/
Bug#910128: bash-completion: diff for NMU version 1:2.8-1.1
On 02 Nov 2018, Gabriel F. T. Gomes wrote: >On 28 Oct 2018, Emmanouil Kampitakis wrote: > >>I've prepared an NMU for bash-completion (versioned as 1:2.8-1.1) and >>uploaded it to DELAYED/5. Please feel free to tell me if I >>should delay it longer. > >Thanks for doing this, and sorry for taking too long to act. I'll >incorporate your changes into the git repository [1]. Once it's >integrated, I'll let you know. Now in the git repository (notice that I will *not* upload a new version to Debian... this is just to let you know that your NMU has been incorporated and that it will keep its intended effect when I upload a new version): https://salsa.debian.org/debian/bash-completion/commit/32b4dc89e47bd20920ea84929d445d0f0812706c
Bug#908681: sane-backends: diff for NMU version 1.0.27-3.1
Control: tags 908681 + patch Control: tags 908681 + pending Dear maintainer, I've prepared an NMU for sane-backends (versioned as 1.0.27-3.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. The diff is too big to be included here, diffstat bellow: $ debdiff sane-backends_1.0.27-3.dsc sane-backends_1.0.27-3.1.dsc|diffstat TROUBLESHOOTING.Debian |4 changelog |8 control | 10 libsane.NEWS| 19 libsane.README.Debian | 172 libsane.dirs|1 libsane.docs|1 libsane.install |2 libsane.postinst| 24 libsane.symbols.alpha | 7314 +++ libsane.symbols.amd64 | 7363 libsane.symbols.arm64 | 7257 +++ libsane.symbols.armel | 7314 +++ libsane.symbols.armhf | 7314 +++ libsane.symbols.hppa| 7257 +++ libsane.symbols.i386| 7314 +++ libsane.symbols.kfreebsd-amd64 | 7361 +++ libsane.symbols.kfreebsd-i386 | 7361 +++ libsane.symbols.m68k| 7257 +++ libsane.symbols.mips| 7257 +++ libsane.symbols.mips64el| 7257 +++ libsane.symbols.mipsel | 7257 +++ libsane.symbols.powerpc | 7257 +++ libsane.symbols.powerpcspe | 7257 +++ libsane.symbols.ppc64 | 7257 +++ libsane.symbols.ppc64el | 7257 +++ libsane.symbols.s390x | 7257 +++ libsane.symbols.sh4 | 7257 +++ libsane.symbols.sparc64 | 7257 +++ libsane.symbols.x32 | 7314 +++ libsane1.NEWS | 19 libsane1.README.Debian | 172 libsane1.dirs |1 libsane1.docs |1 libsane1.install|2 libsane1.postinst | 24 libsane1.symbols.alpha | 7314 --- libsane1.symbols.amd64 | 7363 libsane1.symbols.arm64 | 7257 --- libsane1.symbols.armel | 7314 --- libsane1.symbols.armhf | 7314 --- libsane1.symbols.hppa | 7257 --- libsane1.symbols.i386 | 7314 --- libsane1.symbols.kfreebsd-amd64 | 7361 --- libsane1.symbols.kfreebsd-i386 | 7361 --- libsane1.symbols.m68k | 7257 --- libsane1.symbols.mips | 7257 --- libsane1.symbols.mips64el | 7257 --- libsane1.symbols.mipsel | 7257 --- libsane1.symbols.powerpc| 7257 --- libsane1.symbols.powerpcspe | 7257 --- libsane1.symbols.ppc64 | 7257 --- libsane1.symbols.ppc64el| 7257 --- libsane1.symbols.s390x | 7257 --- libsane1.symbols.sh4| 7257 --- libsane1.symbols.sparc64| 7257 --- libsane1.symbols.x32| 7314 --- rules |8 58 files changed, 153234 insertions(+), 153226 deletions(-) The source package will be available in https://ftp-master.debian.org/deferred/ Regards.
Bug#912681: tkgate FTCBFS: uses AC_RUN_IFELSE
Source: tkgate Version: 2.0~b10-6 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap tkgate fails to cross build from source. The ./configure script uses AC_RUN_IFELSE to compute a sizeof. That's much better done using AC_CHECK_SIZEOF as the latter is much easier to use and works with cross compilation. The attached patch fixes that and makes tkgate cross buildable. Please consider applying it. Helmut --- tkgate-2.0~b10.orig/acinclude.m4 +++ tkgate-2.0~b10/acinclude.m4 @@ -141,10 +141,8 @@ # # AC_DEFUN([TKG_WORDSIZE],[ - AC_CACHE_CHECK([word size], wordsize, -AC_RUN_IFELSE(AC_LANG_PROGRAM([#include #include ], [return sizeof(unsigned) == 8 ? 0 : 1;]), - [wordsize=64], [wordsize=32])) - if test $wordsize = 32; then + AC_CHECK_SIZEOF([unsigned]) + if test $ac_cv_sizeof_unsigned = 4; then AC_DEFINE(TKGATE_WORDSIZE, 32, [Word size of machine.]) else AC_DEFINE(TKGATE_WORDSIZE, 64, [Word size of machine.])
Bug#911697: at-spi2-core: causes SIGSEGV because of improper quoting of G_LOG_DOMAIN
On Wed, Oct 24, 2018 at 10:32 AM Samuel Thibault wrote: > So the issue is in meson itself: it seems one can't get > > compile_args: [ '-DG_LOG_DOMAIN="dbind"' ], > > to be correctly interpreted as making G_LOG_DOMAIN #defined to "dbind" > both for the binary compilation and for the documentation generation. > > FTR, this was working with meson 0.47.2-1 (see > https://buildd.debian.org/status/fetch.php?pkg=at-spi2-core=amd64=2.30.0-2=1536983011=0 > ), so I guess it's 0.48.0 which broke this. Can you test if the commit mentioned in https://github.com/mesonbuild/meson/issues/4452#issuecomment-434870441 fixes the issue for you? Simply running your build with current Meson trunk is enough to test the issue. Thanks,
Bug#912680: pulseaudio: No sound anymore (broken symlink)
Package: pulseaudio Version: 12.2-2 Severity: important Dear Maintainer, I lost a symlink today (I don’t know how or why). > pulseaudio -D gives: nov. 02 20:14:19 nicolas.home pulseaudio[13754]: Failed to find a working profile. nov. 02 20:14:19 nicolas.home pulseaudio[13754]: Failed to load module "module- alsa-card" (argument: "device_id="1" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. nov. 02 20:14:19 nicolas.home pulseaudio[13754]: Failed to find a working profile. nov. 02 20:14:19 nicolas.home pulseaudio[13754]: Failed to load module "module- alsa-card" (argument: "device_id="0" name="pci-_00_14.2" card_name="alsa_card.pci-_00_14.2" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. nov. 02 20:14:19 nicolas.home pulseaudio[13754]: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files As root, service alsa status gives: ● alsa-utils.service Loaded: masked (Reason: Unit alsa-utils.service is masked.) Active: inactive (dead) I can’t unmask the service even with the right command to systemctl and I found that there is no alsa directory in /etc/systemd/system/. In fact, when I try to launch alsamixer: > alsamixer ALSA lib conf.c:3639:(config_file_open) cannot access file /etc/alsa/conf.d/10-rate-lav.conf ALSA lib conf.c:3559:(snd_config_hooks_call) function snd_config_hook_load returned error: Aucun fichier ou dossier de ce type ALSA lib conf.c:4013:(snd_config_update_r) hooks failed, removing configuration le mixeur ne peut pas être ouvert: Aucun fichier ou dossier de ce type /etc/alsa/conf.d/10-rate-lav.conf is a broken symlink to /usr/share/alsa/alsa.conf.d/10-rate-lav.conf. It seems that even if it’s a pulseaudio issue because this file is not from alsa. In fact, I was not able to find precisely from which package this file comes from. Moreover, in Audacious: * The pulseaudio output accepts to play but the output is dummy (no sound plays, the vumeter works). * The alsa output simply crashes (ALSA error: snd_pcm_open failed: No such file or directory.) * The OSS3 output works fine but with a crack on startup. * The SDL output does as pulseaudio. -- Package-specific info: File '/etc/default/pulseaudio' does not exist -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.17.0-3-686-pae (SMP w/3 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr:en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pulseaudio depends on: ii adduser 3.118 ii libasound2 1.1.7-1 ii libasound2-plugins 1:1.1.7-dmo1 ii libc62.27-8 ii libcap2 1:2.25-1.2 ii libdbus-1-3 1.12.10-1 ii libgcc1 1:8.2.0-9 ii libice6 2:1.0.9-2 ii libltdl7 2.4.6-6 ii liborc-0.4-0 1:0.4.28-3 ii libpulse012.2-2 ii libsm6 2:1.2.2-1+b3 ii libsndfile1 1.0.28-4 ii libsoxr0 0.1.2-3 ii libspeexdsp1 1.2~rc1.2-1+b2 ii libstdc++6 8.2.0-9 ii libsystemd0 239-11 ii libtdb1 1.3.16-1 ii libudev1 239-11 ii libwebrtc-audio-processing1 0.3-1 ii libx11-6 2:1.6.7-1 ii libx11-xcb1 2:1.6.7-1 ii libxcb1 1.13.1-1 ii libxtst6 2:1.2.3-1 ii lsb-base 9.20170808 ii pulseaudio-utils 12.2-2 Versions of packages pulseaudio recommends: ii dbus-user-session 1.12.10-1 ii libpam-systemd 239-11 ii rtkit 0.11-6 Versions of packages pulseaudio suggests: pn paman pn paprefs ii pavucontrol 3.0-4 pn pavumeter ii udev 239-11 -- Configuration Files: /etc/pulse/default.pa changed: .fail load-module module-device-restore load-module module-stream-restore load-module module-card-restore load-module module-augment-properties load-module module-switch-on-port-available .ifexists module-udev-detect.so load-module module-udev-detect .else load-module module-detect .endif .ifexists module-jackdbus-detect.so .nofail load-module module-jackdbus-detect channels=2 .fail .endif .ifexists module-bluetooth-policy.so load-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so load-module
Bug#911597: sane-backends: diff for NMU version 1.0.27-3.1
Control: tags 911597 - patch Control: tags 911597 - pending On Fri, 02 Nov 2018 19:50:57 +0100 Laurent Bigonville wrote: > I've prepared an NMU for sane-backends (versioned as 1.0.27-3.1) and > uploaded it to DELAYED/3. Please feel free to tell me if I > should delay it longer. Ouupsie, that was for 908681, not 911597 ...
Bug#911597: sane-backends: diff for NMU version 1.0.27-3.1
Control: tags 911597 + patch Control: tags 911597 + pending Dear maintainer, I've prepared an NMU for sane-backends (versioned as 1.0.27-3.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. The diff is too big to be included here, diffstat bellow: $ debdiff sane-backends_1.0.27-3.dsc sane-backends_1.0.27-3.1.dsc|diffstat TROUBLESHOOTING.Debian |4 changelog |8 control | 10 libsane.NEWS| 19 libsane.README.Debian | 172 libsane.dirs|1 libsane.docs|1 libsane.install |2 libsane.postinst| 24 libsane.symbols.alpha | 7314 +++ libsane.symbols.amd64 | 7363 libsane.symbols.arm64 | 7257 +++ libsane.symbols.armel | 7314 +++ libsane.symbols.armhf | 7314 +++ libsane.symbols.hppa| 7257 +++ libsane.symbols.i386| 7314 +++ libsane.symbols.kfreebsd-amd64 | 7361 +++ libsane.symbols.kfreebsd-i386 | 7361 +++ libsane.symbols.m68k| 7257 +++ libsane.symbols.mips| 7257 +++ libsane.symbols.mips64el| 7257 +++ libsane.symbols.mipsel | 7257 +++ libsane.symbols.powerpc | 7257 +++ libsane.symbols.powerpcspe | 7257 +++ libsane.symbols.ppc64 | 7257 +++ libsane.symbols.ppc64el | 7257 +++ libsane.symbols.s390x | 7257 +++ libsane.symbols.sh4 | 7257 +++ libsane.symbols.sparc64 | 7257 +++ libsane.symbols.x32 | 7314 +++ libsane1.NEWS | 19 libsane1.README.Debian | 172 libsane1.dirs |1 libsane1.docs |1 libsane1.install|2 libsane1.postinst | 24 libsane1.symbols.alpha | 7314 --- libsane1.symbols.amd64 | 7363 libsane1.symbols.arm64 | 7257 --- libsane1.symbols.armel | 7314 --- libsane1.symbols.armhf | 7314 --- libsane1.symbols.hppa | 7257 --- libsane1.symbols.i386 | 7314 --- libsane1.symbols.kfreebsd-amd64 | 7361 --- libsane1.symbols.kfreebsd-i386 | 7361 --- libsane1.symbols.m68k | 7257 --- libsane1.symbols.mips | 7257 --- libsane1.symbols.mips64el | 7257 --- libsane1.symbols.mipsel | 7257 --- libsane1.symbols.powerpc| 7257 --- libsane1.symbols.powerpcspe | 7257 --- libsane1.symbols.ppc64 | 7257 --- libsane1.symbols.ppc64el| 7257 --- libsane1.symbols.s390x | 7257 --- libsane1.symbols.sh4| 7257 --- libsane1.symbols.sparc64| 7257 --- libsane1.symbols.x32| 7314 --- rules |8 58 files changed, 153234 insertions(+), 153226 deletions(-) The source package will be available in https://ftp-master.debian.org/deferred/ Regards.
Bug#912679: libmagickcore-6.q16-dev missing Depends: libmagickcore-6-arch-config
Package: libmagickcore-6.q16-dev Version: 8:6.9.10.14+dfsg-5 Severity: serious Justification: missing dependency Control: affects -1 + src:gem libmagickcore-6.q16-dev does not depend on libmagickcore-6-arch-config. It does depend on libmagickcore-6-headers, which depends on libmagickcore-6-arch-config, but libmagickcore-6-headers is Multi-Arch: foreign. So you get some libmagickcore-6-arch-config and not necessarily one with matching architecture. The dependency is too weak. When building gem, this can become fatal: | /bin/bash ../../libtool --tag=CXX --mode=compile aarch64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -DGEM_VERSION_CODENAME='""Debian/1:0.93.3-18""' -DPD -I/usr/include/pd -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -c -o gem_imageMAGICK_la-imageMAGICK.lo `test -f 'imageMAGICK.cpp' || echo './'`imageMAGICK.cpp | libtool: compile: aarch64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -DGEM_VERSION_CODENAME=\"\"Debian/1:0.93.3-18\"\" -DPD -I/usr/include/pd -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -c imageMAGICK.cpp -fPIC -DPIC -o .libs/gem_imageMAGICK_la-imageMAGICK.o | In file included from /usr/include/ImageMagick-6/Magick++/Include.h:14, | from /usr/include/ImageMagick-6/Magick++.h:10, | from imageMAGICK.cpp:21: | /usr/include/ImageMagick-6/magick/magick-config.h:21:10: fatal error: magick/magick-baseconfig.h: No such file or directory | #include "magick/magick-baseconfig.h" | ^~~~ | compilation terminated. | make[3]: *** [Makefile:613: gem_imageMAGICK_la-imageMAGICK.lo] Error 1 | make[3]: Leaving directory '/<>/plugins/imageMAGICK' | make[2]: *** [Makefile:489: all-recursive] Error 1 | make[2]: Leaving directory '/<>/plugins' | make[1]: *** [Makefile:598: all-recursive] Error 1 | make[1]: Leaving directory '/<>' | dh_auto_build: make -j1 returned exit code 2 | make: *** [debian/rules:82: binary-arch] Error 2 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 The dependency from libmagickcore-6-headers on libmagickcore-6-arch-config should be removed. It is always too week and needs to be lifted to a higher level. What can be done though is flipping the dependency. Have libmagickcore-6-arch-config depend on libmagickcore-6-headers and then replace any dependency on libmagickcore-6-headers with one on libmagickcore-6-arch-config. That should be fine, because both packages are considered implementation detail and do not have any reverse dependencies outside imagemagick. Helmut
Bug#912665: (geen onderwerp)
* Frederik Himpe: > FYI, this is where it crashes: > > #0 0x7fc0172239c6 in _IO_fgets (buf=0x7ffc9b2b1640 " > /dev/aivmhost3-vg/ceph-node1-storage:ceph-ff35163d-b03f-4dbf-a6ce-155730069dc0:4194304:-1:8:8:-1:4096:511:0:511:ZNexTV-ylVb-ltMP-T8Zu-ZklU-cN1I-dETf5o\n", > n=1024, fp=0x1a90030) > at iofgets.c:47 This is the first dereference of the file stream pointer in fgets, so this suggests a use-after-free application bug (or use-after-fclose in this case). It should be visible in valgrind as well. Thanks, Florian
Bug#910755: fixed in upstream 3.1
I built a debian from upstream version 3.1, and goobook is now working again for me. (Copied in debian dir, minor offset fix to get the one quilt patch to apply). Please consider uploading 3.1 to sid!
Bug#912678: xorg: Xorg got frozen each 3 seconds and everything got frozen within it.
Package: xorg Version: 1:7.7+19 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? When I have upgraded Xorg. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? I told. * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.18.0-kali2-686-pae (de...@kali.org) (gcc version 7.3.0 (Debian 7.3.0-29)) #1 SMP Debian 4.18.10-2kali1 (2018-10-09) Xorg X server log files on system: -- -rw-r--r-- 1 root root 34815 Nov 2 20:06 /var/log/Xorg.1.log -rw-r--r-- 1 root root 33300 Nov 2 20:46 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [28.779] X.Org X Server 1.20.3 X Protocol Version 11, Revision 0 [28.779] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian [28.779] Current Operating System: Linux karam 4.18.0-kali2-686-pae #1 SMP Debian 4.18.10-2kali1 (2018-10-09) i686 [28.779] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-kali2-686-pae root=UUID=ac6ea0b3-bd72-44ad-8cee-8659f68cf774 ro initrd=/install/gtk/initrd.gz quiet video=SVIDEO-1:d [28.779] Build Date: 25 October 2018 06:15:23PM [28.779] xorg-server 2:1.20.3-1 (https://www.debian.org/support) [28.779] Current version of pixman: 0.34.0 [28.779]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [28.780] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [28.780] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 2 20:11:44 2018 [28.823] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [28.907] (==) No Layout section. Using the first Screen section. [28.908] (==) No screen section available. Using defaults. [28.908] (**) |-->Screen "Default Screen Section" (0) [28.908] (**) | |-->Monitor "" [28.928] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [28.928] (==) Automatically adding devices [28.928] (==) Automatically enabling devices [28.928] (==) Automatically adding GPU devices [28.929] (==) Max clients allowed: 256, resource mask: 0x1f [28.988] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [28.988]Entry deleted from font path. [28.992] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [28.992] (==) ModulePath set to "/usr/lib/xorg/modules" [28.992] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [28.992] (II) Loader magic: 0x6e7740 [28.992] (II) Module ABI versions: [28.992]X.Org ANSI C Emulation: 0.4 [28.992]X.Org Video Driver: 24.0 [28.992]X.Org XInput driver : 24.1 [28.992]X.Org Server Extension : 10.0 [28.995] (++) using VT number 7 [28.995] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [28.998] (II) xfree86: Adding drm device (/dev/dri/card0) [29.041] (--) PCI:*(0@0:2:0) 8086:2a02:1028:0228 rev 12, Mem @ 0xfea0/1048576, 0xe000/268435456, I/O @ 0xefe8/8, BIOS @ 0x/131072 [29.041] (--) PCI: (0@0:2:1) 8086:2a03:1028:0228 rev 12, Mem @ 0xfeb0/1048576 [29.049] (II) LoadModule: "glx" [29.074] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [29.229] (II) Module glx: vendor="X.Org Foundation" [29.229]compiled for 1.20.3, module version = 1.0.0 [29.229]ABI class: X.Org Server Extension, version 10.0 [29.230] (==) Matched modesetting as autoconfigured driver 0 [29.230] (==) Matched fbdev as autoconfigured driver 1 [29.230] (==) Matched vesa as autoconfigured driver 2 [29.230] (==) Assigned the driver to the
Bug#912677: ITP: oci-systemd-hook - OCI systemd hook enables users to run systemd in OCI compatible runtimes
package: wnpp Severity: wishlist Owner: 'Qian Cai' *Package Name : oci-systemd-hook Version : 0.1.18 *URL : https://github.com/projectatomic/oci-systemd-hook *License : GPLv3 *Description : OCI systemd hook enables users to run systemd in docker and OCI compatible runtimes such as runc without requiring --privileged flag. This project produces a C binary that can be used with runc and Docker (with minor code changes). If you clone this branch and build/install oci-systemd-hook, a binary should be placed in /usr/libexec/oci/hooks.d named oci-systemd-hook. Running Docker or OCI runc containers with this executable, oci-systemd-hook is called just before a container is started and after it is provisioned. If the CMD to run inside of the container is init or systemd, this hook will configure the container image to run a systemd environment. For all other CMD's, this hook will just exit.
Bug#912599: [Pkg-nagios-devel] Bug#912599: icinga2-common: incinga2-common fails to install cleanly (hidden dep on icinga2)
On 11/2/18 6:58 PM, Lee Garrett wrote: > On 01/11/2018 20:15, Sebastiaan Couwenberg wrote:> Hi Lee, >> >> On 11/1/18 6:41 PM, Lee Garrett wrote: >>> installing icinga2-common on a system that does not have icinga2 installed >>> fails as follows: >>> >>> [...] >>> >>> Installing icinga2 directly, which pulls in icinga2-common, makes the >>> installation go through cleanly. >> >> Installing icinga2-common by itself makes no sense. > > I agree, though there might be corner cases where this might happen, like > during dist-upgrade. That's something piuparts would have found, and it didn't run into this issue. >>> Besides the policy violation it makes it hard to install icinga2 with the >>> chef >>> cookbook at https://supermarket.chef.io/cookbooks/icinga2, as it installs >>> every >>> package after each other (with a version number restriction). >> >> I have no sympathy for broken configuration management. The cookbook not >> working is something you need take up with its developer. > > Indeed, they unfortunately happen to be the cookbooks provided by upstream. > > Thanks for the quick fix! Note that only the version in unstable was fixed. The issue doesn't seem widespread enough to warrant a stable update. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#910128: bash-completion: diff for NMU version 1:2.8-1.1
Hi, Emmanouil, On 28 Oct 2018, Emmanouil Kampitakis wrote: >I've prepared an NMU for bash-completion (versioned as 1:2.8-1.1) and >uploaded it to DELAYED/5. Please feel free to tell me if I >should delay it longer. > >Previous diff was against stable. Attached diff is agains sid Thanks for doing this, and sorry for taking too long to act. I'll incorporate your changes into the git repository [1]. Once it's integrated, I'll let you know. [1] https://salsa.debian.org/debian/bash-completion/commits/master
Bug#912599: [Pkg-nagios-devel] Bug#912599: icinga2-common: incinga2-common fails to install cleanly (hidden dep on icinga2)
Hi Sebastiaan, On 01/11/2018 20:15, Sebastiaan Couwenberg wrote:> Hi Lee, > > On 11/1/18 6:41 PM, Lee Garrett wrote: >> installing icinga2-common on a system that does not have icinga2 installed fails >> as follows: >> >> [...] >> >> Installing icinga2 directly, which pulls in icinga2-common, makes the >> installation go through cleanly. > > Installing icinga2-common by itself makes no sense. I agree, though there might be corner cases where this might happen, like during dist-upgrade. > >> Besides the policy violation it makes it hard to install icinga2 with the >> chef >> cookbook at https://supermarket.chef.io/cookbooks/icinga2, as it installs >> every >> package after each other (with a version number restriction). > I have no sympathy for broken configuration management. The cookbook not > working is something you need take up with its developer. Indeed, they unfortunately happen to be the cookbooks provided by upstream. Thanks for the quick fix! Regards, Lee
Bug#907294: completions/dpkg: installing dctrl-tools breaks completion for held packages with -L/--listfiles
On 02 Nov 2018, Gabriel F. T. Gomes wrote: >Thanks for writing the fix... I'll apply it to the package and forward >this upstream. I have reported the bug upstream [1], and I incorporated your patch to the git repo of bash-completion [2], however I have not yet produced a package with the fix... Very recently, bash-completion was updated with an NMU [3], which I need to incorporate to the git repository [1], before producing the new package... I'm sorry that this NMU was necessary. I failed to properly follow the bug reporting for bash-completion. :( [1] https://github.com/scop/bash-completion/pull/250 [2] https://salsa.debian.org/debian/bash-completion/commit/985bca1882f9993df458421445ac334b94caf603 [3] https://bugs.debian.org/910128#36
Bug#911802: Re: Bug#911802: ITP: kovri -- C++ I2P router
On Fri, 2018-11-02 at 00:10 +, oneiric wrote: > [...] > > > You will need to have a very good reason to do this. It is recommended > > to use shared libraries in Debian packages where possible. > [...] > > Hi Ben, > > I would prefer shared libraries as well. > > The current alpha point release does not require static > compilation/linking, but we are planning to incorporate Boost.Beast into > the next release, which requires Boost 1.66+. > > Currently on Debian 9, the system package for Boost is 1.62. That is irrelevant because this new package won't go into Debian 9. Ben. > I checked the different repositories, and 1.62 looks like the latest > version. > > Thanks for your quick reply, sorry about the delay on my end. > > - oneiric > -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Bug#912656: ITS: python-fs
On Fri, Nov 02, 2018 at 05:27:09PM +0100, Mattia Rizzolo wrote: > Hi Yao Wei, > > On Fri, Nov 02, 2018 at 09:08:55PM +0800, Yao Wei wrote: > > There were another requests which maintainers didn't respond (#810800 > > [2], #890829 [3]), which was at least 6 months ago, with NMU request. > > > > I would like to upload the package. According to the package salvaging > > guide in Developers' Reference [4], I would like to co-maintain this > > package along with DPMT. > > I'm confused here, this package is already maintained by DPMT, with it > in Uploaders. Team members can already freely upload it; sure it is in > Uploaders only so you'd need to give the maintainer a heads up, but you > need not block on this, much less go through the ITS process. > > Also, the maintainer janos is already being tracked by the MIA team, > despite being not exactly responsive there either. > > > I recommend you just go ahead and do a team upload, and if you really > wish so also move around Maintainer/Uploaders (and put yourself in it). All this said, the listed comaintainer is actually quite active, even if he seem to have neglected this one package. I'm explicitly CCing him here. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#912333: openjdk-8-jdk: breaks maven-surefire-plugin (security-caused regression)
Dixi quod… > Note I haven’t finished building it yet so it’s untested. I’ve tested it now, on stretch. It works. > But I’d still love to see it uploaded to Debian proper. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#912676: wine-development-tools: depend on clang-6.0 on arm64
Package: wine-development Hello! It looks like winegcc expects clang-6.0 on arm64: ``` /usr/lib/wine-development/winegcc --help winegcc: clang-6.0 failed ``` Should wine[32|64]-development-tools depend on clang-6.0? Cheers, -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature
Bug#893870: RM: luakit -- RoQA; orphaned web browser; depends on unmaintained webkitgtk
Control: tags -1 -moreinfo On Fri, Mar 23, 2018 at 2:15 PM Scott Kitterman wrote: > On Fri, 23 Mar 2018 13:10:28 -0400 Jeremy Bicha wrote: > > On Fri, Mar 23, 2018 at 1:07 PM, Mason Larobina > > wrote: > > > Are you aware there is active luakit development again? > > > > Yes, I am aware that there was a new luakit release last year. The > > problem is that it is not well-maintained in Debian. > > Looking at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738447 is seems > there is a potential maintainer that needs some help with sponsoring/ > understanding how package updates work in Debian. > > I'm going to tag this moreinfo for now. Would someone who either: > > 1. Cares that luakit stays in the archive > > or > > 2. Cares that webkitgtk gets removed from the archive > > reach out to the individual and see if they are still interested and try to > help them if they are. If they are no longer interested or don't respond in a > reasonable time, then remove the moreinfo tag. If the package gets updated, > then please close the bug. Sorry. Like I said in this bug's original post, I don't have the energy and interest to be responsible for luakit. In the 6 months since your post, there has been no activity in getting luakit updated in Debian so I'm dropping the moreinfo tag again. There has been significant progress in updating eclipse recently so I think we'll be able to remove the old webkitgtk for good soon. Thanks, Jeremy Bicha
Bug#890246: New upstream available
Hi! I just wanted to nudge, since I just made another small release. This should be a really straightforward update, and the previous release fixed some long outstanding issues. Kjetil
Bug#912665: (geen onderwerp)
FYI, this is where it crashes: #0 0x7fc0172239c6 in _IO_fgets (buf=0x7ffc9b2b1640 " /dev/aivmhost3-vg/ceph-node1-storage:ceph-ff35163d-b03f-4dbf-a6ce-155730069dc0:4194304:-1:8:8:-1:4096:511:0:511:ZNexTV-ylVb-ltMP-T8Zu-ZklU-cN1I-dETf5o\n", n=1024, fp=0x1a90030) at iofgets.c:47
Bug#912675: prosody FTCBFS: configures for the build architecture
Source: prosody Version: 0.10.2-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap prosody fails to cross build from source, because it configures for the build architecture. For cross builds, one has to pass suitable tools for --c-compiler and --linker. The attached patch implements that and makes prosody cross build successfully. Please consider applying it. Helmut diff --minimal -Nru prosody-0.10.2/debian/changelog prosody-0.10.2/debian/changelog --- prosody-0.10.2/debian/changelog 2018-05-31 22:57:00.0 +0200 +++ prosody-0.10.2/debian/changelog 2018-11-02 17:38:23.0 +0100 @@ -1,3 +1,10 @@ +prosody (0.10.2-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Pass --c-compiler and --linker to ./configure. (Closes: #-1) + + -- Helmut Grohne Fri, 02 Nov 2018 17:38:23 +0100 + prosody (0.10.2-1) unstable; urgency=medium * Team upload. diff --minimal -Nru prosody-0.10.2/debian/rules prosody-0.10.2/debian/rules --- prosody-0.10.2/debian/rules 2018-05-31 22:51:25.0 +0200 +++ prosody-0.10.2/debian/rules 2018-11-02 17:38:21.0 +0100 @@ -3,12 +3,13 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/buildflags.mk +-include /usr/share/dpkg/buildtools.mk %: dh $@ override_dh_auto_configure: - ./configure --ostype=debian --prefix=/usr + ./configure --ostype=debian --prefix=/usr --c-compiler=$(CC) --linker=$(CC) override_dh_auto_build: dh_auto_build
Bug#912674: ImportError: cannot import name LogConfig
Package: docker-compose
Version: 1.8.0-2
Severity: normal
$ docker-compose up --build
Traceback (most recent call last):
File "/usr/bin/docker-compose", line 11, in
load_entry_point('docker-compose==1.8.0', 'console_scripts',
'docker-compose')()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 561,
in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2631,
in load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2291,
in load
return self.resolve()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2297,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python2.7/dist-packages/compose/cli/main.py", line 17, in
from ..bundle import get_image_digests
File "/usr/lib/python2.7/dist-packages/compose/bundle.py", line 14, in
from .service import format_environment
File "/usr/lib/python2.7/dist-packages/compose/service.py", line 13, in
from docker.utils import LogConfig
ImportError: cannot import name LogConfig
-- System Information:
Debian Release: 9.5
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.17.0-0.bpo.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:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages docker-compose depends on:
ii python 2.7.13-2
ii python-cached-property 1.3.0-2
ii python-docker 1.9.0-1
ii python-dockerpty0.4.1-1
ii python-docopt 0.6.2-1
ii python-enum34 1.1.6-1
ii python-jsonschema 2.5.1-6
ii python-requests 2.12.4-1
ii python-six 1.10.0-3
ii python-texttable0.8.4-2
ii python-websocket0.37.0-2
ii python-yaml 3.12-1
Versions of packages docker-compose recommends:
ii docker.io 1.13.1~ds2-3+b1
docker-compose suggests no packages.
-- no debconf information
Bug#912673: pepperflashplugin-nonfree: Misleading package description about Chrome download
Package: pepperflashplugin-nonfree Version: 1.8.3+nmu1 Severity: normal Dear Maintainer, the package description is currently stating the following: > This package will download Chrome from Adobe, and unpack it to make the > included Pepper Flash Player available for use with Chromium. However installing the package shows that not Chrome itself but the Flash Plugin for Chrome is downloaded from Adobe. The package description looks quite misleading to me and might prvent people from installing the package because they think Chrome will be downloaded.
