Bug#859485: O: eancheck -- Check digit validator for EAN/PLU/UPC barcode numbers
Package: wnpp The current maintainer of eancheck, Joe Baldwin, is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: eancheck Binary: eancheck Version: 1.0-1.1 Maintainer: Joe Baldwin Build-Depends: debhelper (>= 5) Architecture: any Standards-Version: 3.7.2 Format: 1.0 Files: 2ea7d22b0991aa6a868924c99f75bcdf 557 eancheck_1.0-1.1.dsc 7a42b41611e731d21ec8ea43b2b3106e 2777 eancheck_1.0.orig.tar.gz c30e682779943860db373aed7a9bc421 1472 eancheck_1.0-1.1.diff.gz Checksums-Sha256: 9d3ca900322ed676b120dbd717b8a88f4e289efe7334dd2c5451160f40db060d 557 eancheck_1.0-1.1.dsc 39fa16144ec5634882299977dc3624f49b2c7904ae870b59e501a50661f3750c 1472 eancheck_1.0-1.1.diff.gz 38e3938eb6a4ea8689ed60e59f7e830ee0c0b85185f620c194f5523779deaf67 2777 eancheck_1.0.orig.tar.gz Directory: pool/main/e/eancheck Priority: source Section: misc Package: eancheck Source: eancheck (1.0-1.1) Version: 1.0-1.1+b1 Installed-Size: 26 Maintainer: Joe Baldwin Architecture: amd64 Depends: libc6 (>= 2.2.5), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1) Description: Check digit validator for EAN/PLU/UPC barcode numbers Description-md5: 82469e14c5d6a5b9247e5e63c176eacc Tag: implemented-in::c++, role::program, use::checking Section: misc Priority: optional Filename: pool/main/e/eancheck/eancheck_1.0-1.1+b1_amd64.deb Size: 6344 MD5sum: 4591ea5451b8a917037a669814e469a0 SHA256: d9a1a0a6e4cfc48aa131941c55233b84f662f1078c7b7776036214ea2f08acaf -- 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#859484: RM: drift -- RoQA; RC buggy; lost upstream; unmaintained; low popcon
Package: ftp.debian.org X-Debbugs-Cc: dr...@packages.debian.org Please remove src:drift from the archive. Last maintainer upload 2008, popcon 8, RC buggy for 1,5 years, not in wheezy, jessie or stretch... -- 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#859483: RM: cook -- RoQA; RC buggy; umaintained; dead upstream; low popcon
Package: ftp.debian.org X-Debbugs-Cc: c...@packages.debian.org Control: block -1 by 859482 Please remove src:cook from the archive. The package has been RC buggy for quite some months, the maintainer looks unreachable. The upstream page doesn't load, and the package name makes hard for me to google for it. Also it seems like the last upstream release was 7+ years ago... popcon 25. -- 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#859389: ejabberd: SSL handshake fails in Pidgin and Yaxim after 2.1.10-4+deb7u2 update
Hi, if you care to look into the changelog, you'll see that the security upgrade disabled SSLv3. After that, only TLS 1.2 with a handful of ciphers is left, see https://lists.debian.org/debian-lts/2017/04/msg2.html If your clients are unable to connect, they're probably as outdated and insecure as your ejabberd. I haven't had problems with gajim and psi+, and Guido also tested a few other clients. As stated in above mail: If people want to be able to configure TLS versions and ciphers themselves, they'll have to upgrade to a newer ejabberd (which I would strongly recommend anyway). Two weeks ago I uploaded 14.07 to wheezy-backports and 16.09 to wheezy-backports-sloppy. Upstream has documented the update procedure here: https://docs.ejabberd.im/admin/upgrade/ If you want to keep your outdated and insecure ejabberd, simply put the package on hold. I doubt very much that another update of the wheezy package is going to happen. Regards, -- .''`. Philipp Huebner: :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#859482: RM: aegis -- RoQA; RC buggy; unmaintained; low popcon; dead upstream
Package: ftp.debian.org X-Debbugs-Cc: ae...@packages.debian.org Please remove aegis from the archive. Upstream last release has been in 2008, since then the progam only got more bugs. The last Debian upload was 5 years ago. The Debian maintainer also seems unresponsive. The RC bugginess and low popcon doesn't make for any better situation. -- 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#858174: Re: Bug#858174: Please provide an AppArmor profile for Firefox
Hi, Vincas Dargis: > 2017.03.20 11:23, intrigeri rašė: > Yes, they have profile in firefox package [0]. Thanks! But it ships disabled (or in complain mode) by default, right? >> 1. Find out which profile (if there are several, e.g. a non-upstream >>one shipped in Ubuntu's firefox package) is the best one, in terms >>of safety/usability trade-offs and maintenance level. > I guess we could try Ubuntu Firefox profile, it is more advanced compared to > profiles/apparmor/profiles/extras/usr.lib.firefox.firefox in AppArmor source. OK. So these improvements shall be upstreamed. We already had to deal with a situation when we shipped a profile from Ubuntu (Chromium) that was substantially different from upstream's, and it was a pain to maintain our own delta on top. >> 3. If it's good enough, consider having apparmor-profiles ship it >>(disabled by default) in /etc/apparmor.d/ instead of >>/usr/share/doc/apparmor-profiles/extras/, to improve the UX of >>enabling it and keeping it up-to-date wrt. upstream changes. > But should that profile be a base of Ubuntu Firefox profile (for example) with > ./debian/patches on top? No, please. > Or "fixed" old "profiles/apparmor/profiles/extras/usr.lib.firefox.firefox", > by sending patches upstream? Yes, please. And as written above, this doesn't prevent us from shipping it to /etc/apparmor.d (disabled by default) if it's good enough. >> 5. Consider enforcing the profile by default: can we do it? is it >>blocked by something else, like proper desktop notifications >>offering guidance whenever the AppArmor confinement >>blocks something? > There is that apparmor-notify, though I haven't tried it myself. Sadly, it's poorly integrated in Debian currently, iirc because it relies on parsing logs instead of using the relevant audit interface. I'm pretty sure we have bugs about it in the Debian and upstream bug tracking systems. > I would really like AppArmor to be more mainstream'ish... If app could > maybe get some kind of feedback directly and inform user that it could not > save > that .PDF into ~/ because AppArmor profile denied it, so could you try another > directory instead of just disabling AppAmrmor completely :-) , please? > Maybe if AppArmor profile had sort of tags or hints, specifying that this > "somepath/** rwk" rule is designed to be user-accesible downloaded/generated > content directory so user should really use that, hinted then by the app > itself > (with help of libapparmor or whatever). Anyway, these dreams are out of this > bug > scope I guess. Indeed. There's some work going on upstream about these topics, feel free to start a discussion about it on the upstream AppArmor mailing list :) Cheers, -- intrigeri
Bug#846418: contextfree: diff for NMU version 3.0.5+dfsg1-2.3
Control: tags 846418 + patch Control: tags 846418 + pending Dear maintainer, I've prepared an NMU for contextfree (versioned as 3.0.5+dfsg1-2.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- 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 `- diffstat for contextfree-3.0.5+dfsg1 contextfree-3.0.5+dfsg1 changelog |9 + control |4 ++-- dirs |1 - 3 files changed, 11 insertions(+), 3 deletions(-) diff -Nru contextfree-3.0.5+dfsg1/debian/changelog contextfree-3.0.5+dfsg1/debian/changelog --- contextfree-3.0.5+dfsg1/debian/changelog 2014-08-09 15:23:45.0 +0200 +++ contextfree-3.0.5+dfsg1/debian/changelog 2017-04-04 07:20:07.0 +0200 @@ -1,3 +1,12 @@ +contextfree (3.0.5+dfsg1-2.3) unstable; urgency=medium + + * Non-maintainer upload. + * Remove pointless debian/dirs file. + * Add libfl-dev to Build-Depends to fix FTBFS. Closes: #846418 + * Bump Standards-Version to 3.9.8, no changes needed. + + -- Mattia RizzoloTue, 04 Apr 2017 07:20:07 +0200 + contextfree (3.0.5+dfsg1-2.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru contextfree-3.0.5+dfsg1/debian/control contextfree-3.0.5+dfsg1/debian/control --- contextfree-3.0.5+dfsg1/debian/control 2014-08-09 14:31:00.0 +0200 +++ contextfree-3.0.5+dfsg1/debian/control 2017-04-04 07:19:34.0 +0200 @@ -3,8 +3,8 @@ Priority: extra Maintainer: Bram Senders Uploaders: Paul van Tilburg -Build-Depends: debhelper (>= 9), flex, bison, libpng-dev -Standards-Version: 3.9.5 +Build-Depends: debhelper (>= 9), flex, bison, libpng-dev, libfl-dev, +Standards-Version: 3.9.8 Homepage: http://contextfreeart.org/ Package: contextfree diff -Nru contextfree-3.0.5+dfsg1/debian/dirs contextfree-3.0.5+dfsg1/debian/dirs --- contextfree-3.0.5+dfsg1/debian/dirs 2013-11-29 20:04:33.0 +0100 +++ contextfree-3.0.5+dfsg1/debian/dirs 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -usr/bin signature.asc Description: PGP signature
Bug#856439: fakeroot doesn't detect and handle message queue and semaphore id collision
aha, it also failed two months ago (really, two builds ago, I haven't been running this often) at hour 5 with + fakeroot sh /tmp/maketar.sh.JQLvyH7VMj opt/blort/deps-32-11/ opt/blort/deps-32-11/include/ opt/blort/deps-32-11/include/x264_config.h opt/blort/deps-32-11/include/x264.h opt/blort/deps-32-11/bin/ opt/blort/deps-32-11/bin/x264 semop(1): encountered an error: Invalid argument /usr/bin/fakeroot: line 1: kill: (7959) - No such process Makefile:14: recipe for target 'all' failed make[1]: *** [all] Error 1 so maybe I'll try running fakeroot tar in a loop. On Mon, Apr 3, 2017 at 10:15 PM, Dan Kegelwrote: > I may have seen something similar with ubuntu core today on raspberry pi3 > (using the classic snap, which is at 16.04.2) > fakeroot is 1.20.2-1ubuntu1. > > Here's what I saw while packaging a version of graphicsmagick (about three > hours > into a script that > >dh_builddeb > dpkg-deb: building package 'blort-graphicsmagick' in > '../blort-graphicsmagick_XX.YY_armhf.deb'. > semop(1): encountered an error: Invalid argument > dpkg-deb: error: subprocess tar -cf returned error exit status 1 > dh_builddeb: dpkg-deb --build debian/blort-graphicsmagick .. returned > exit code 2 > semop(1): encountered an error: Identifier removed > dh_builddeb: dpkg-deb --build debian/blort-graphicsmagick-dbg .. > returned exit code 1 > debian/rules:4: recipe for target 'binary' failed > make: *** [binary] Error 1 > /usr/bin/fakeroot: line 1: kill: (8907) - No such process > dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status > 2 > debuild: fatal error at line 1376: > dpkg-buildpackage -rfakeroot -D -us -uc -b failed > program finished with exit code 29 > > I have not tried your patches or turning on debugging output yet. > I'm rerunning debuild now, but it's bedtime, I'll have to check in the morning > (raspberry pi rather dreadfully slow).
Bug#859389: ejabberd: SSL handshake fails in Pidgin and Yaxim after 2.1.10-4+deb7u2 update
Same problem when using Conversations on Android 4.x, though there are no problems with Conversations on Android 5 or newer. After downgrading to deb7u1, everythings works as usual.
Bug#859426: vim: Vim 8 cannot handle 'etags' format any more
Hello James, thanks for your time! > > When the file "tags" (or also "TAGS") was created with the 'etags' command, > > e.g. > > > >$ etags file.c > > Which etags is this? There are various packages that provide the etags > name. “update-alternatives --query etags” will tell you. It says: Name: etags Link: /usr/bin/etags Slaves: etags.1.gz /usr/share/man/man1/etags.1.gz Status: auto Best: /usr/bin/ctags-exuberant Value: /usr/bin/ctags-exuberant Alternative: /usr/bin/ctags-exuberant Priority: 10 Slaves: etags.1.gz /usr/share/man/man1/ctags-exuberant.1.gz It generates the same format as described in https://en.wikipedia.org/wiki/Ctags#Etags_2 with a header <\x0c> {src_file},{size_of_tag_definition_data_in_bytes} and lines formatted as {tag_definition_text}<\x7f>{tagname}<\x01>{line_number},{byte_offset} A typical file is then <\x0c> test.c,21 #define CCC(<\x7f>CCC<\x01>1,0 In fact, my own use case is not the 'etags' command, but the 'tags' files contained in (and generated at runtime by) the 'picolisp' package. This also uses the above format, and the PicoLisp 'vi' command calls 'vim', and broke in the described way. Therefore I tested also with the 'etags' command. It makes the problem easier to reproduce. 'vim' still claims to be compiled with '+emacs_tags'. In Debian Jessie (and before) it worked without problems. Best regards, - Alex
Bug#856439: fakeroot doesn't detect and handle message queue and semaphore id collision
I may have seen something similar with ubuntu core today on raspberry pi3 (using the classic snap, which is at 16.04.2) fakeroot is 1.20.2-1ubuntu1. Here's what I saw while packaging a version of graphicsmagick (about three hours into a script that dh_builddeb dpkg-deb: building package 'blort-graphicsmagick' in '../blort-graphicsmagick_XX.YY_armhf.deb'. semop(1): encountered an error: Invalid argument dpkg-deb: error: subprocess tar -cf returned error exit status 1 dh_builddeb: dpkg-deb --build debian/blort-graphicsmagick .. returned exit code 2 semop(1): encountered an error: Identifier removed dh_builddeb: dpkg-deb --build debian/blort-graphicsmagick-dbg .. returned exit code 1 debian/rules:4: recipe for target 'binary' failed make: *** [binary] Error 1 /usr/bin/fakeroot: line 1: kill: (8907) - No such process dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 debuild: fatal error at line 1376: dpkg-buildpackage -rfakeroot -D -us -uc -b failed program finished with exit code 29 I have not tried your patches or turning on debugging output yet. I'm rerunning debuild now, but it's bedtime, I'll have to check in the morning (raspberry pi rather dreadfully slow).
Bug#848015: ciphersaber: diff for NMU version 1.01-2.1
Control: tags 848015 + patch Control: tags 848015 + pending Dear maintainer, I've prepared an NMU for ciphersaber (versioned as 1.01-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- 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 `- diffstat for ciphersaber_1.01-2 ciphersaber_1.01-2.1 changelog |7 +++ control |4 ++-- copyright |4 ++-- 3 files changed, 11 insertions(+), 4 deletions(-) diff -u ciphersaber-1.01/debian/changelog ciphersaber-1.01/debian/changelog --- ciphersaber-1.01/debian/changelog +++ ciphersaber-1.01/debian/changelog @@ -1,3 +1,10 @@ +ciphersaber (1.01-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add build-dependency on libtest-warn-perl to fix FTBFS (Closes: #848015). + + -- Mattia RizzoloTue, 04 Apr 2017 06:59:05 +0200 + ciphersaber (1.01-2) unstable; urgency=medium * Add build dependency on libmodule-build-perl (Closes: #838670). diff -u ciphersaber-1.01/debian/control ciphersaber-1.01/debian/control --- ciphersaber-1.01/debian/control +++ ciphersaber-1.01/debian/control @@ -1,8 +1,8 @@ Source: ciphersaber Section: interpreters -Priority: optional +Priority: optional Maintainer: Stefan Hornburg (Racke) -Build-Depends: debhelper (>= 9), libmodule-build-perl +Build-Depends: debhelper (>= 9), libmodule-build-perl, libtest-warn-perl Build-Depends-Indep: perl Standards-Version: 3.9.8 diff -u ciphersaber-1.01/debian/copyright ciphersaber-1.01/debian/copyright --- ciphersaber-1.01/debian/copyright +++ ciphersaber-1.01/debian/copyright @@ -1,7 +1,7 @@ This package was debianized by Jerome Marant on Fri, 27 Apr 2001 14:11:37 +0200. -It was downloaded from http://www.cpan.org/authors/id/C/CH/CHROMATIC +It was downloaded from http://www.cpan.org/authors/id/C/CH/CHROMATIC Upstream Author: Chromatic @@ -25 +25 @@ -the Artistic Licence in `/usr/share/common-licenses/Artistic'. \ No newline at end of file +the Artistic Licence in `/usr/share/common-licenses/Artistic'. signature.asc Description: PGP signature
Bug#858802: [Letsencrypt-devel] Bug#858802: AttributeError: 'module' object has no attribute 'DependencyError'
Patrick Lamwrites: > I get a similar error on an upgraded stretch box: That's perplexing. I just ran an upgrade from jessie to stretch on a clean box, installed certbot -- works fine. I can't replicate this at all. What architecture are you running on? > The output of the command is empty. My guess is you're missing apt-rdepends. Can you install it and rerun the command please? Thanks, -- Harlan Lieberman-Berg ~hlieberman
Bug#859439: git-buildpackage: When merge fails due to untracked files, subsequent rollback also fails
Hi Matthijs, On Mon, Apr 03, 2017 at 07:33:49PM +0200, Matthijs Kooijman wrote: > Hi Guido, > > > The rollback overall doesn't fail, only the part that tries to undo the > > merge. Rollbacks are always best effort (roll back as much as you can) > > and so master, etc. end up on the correct revs. However we must not > > fail the merge rollback. > Yeah, exactly. > > > > Looking more closely at the original merge failure, it aborts because > > > there are untracked files that would be overwritten by the merge (which > > > likely means it never starts the merge, instead of starting and failing > > > later). Perhaps git merge returns different exit codes for these > > > situations? > > > > Sadly not but we can look for MERGE_HEAD. I've checked in a patch for > > that and it would be awesome if you could test it (or tell me which > > files it stumbled upon in openttd)? > I don't have a gbp build set up, so if you could test it, that would be > great. I haven't pushed the 1.7.0 changes to alioth yet, so you should > be able to test with: > > $ gbp clone https://anonscm.debian.org/git/collab-maint/openttd.git > $ cd openttd > $ touch bin/baseset/orig_extra.grf > $ gbp import-orig --uscan --verbose > > (not tested) That worked and helped. Thanks! -- Guido
Bug#859111: ariba: FTBFS: FAIL: Test run_bowtie2 unsorted
On Thu, Mar 30, 2017 at 06:20:16PM +0300, Adrian Bunk wrote: > Control: retitle -1 ariba FTBFS with bowtie2 2.3.1-1 [...] > This is actually not related to the ariba version but to the bowtie2 version, > ariba 2.6.1+ds-1 in stretch builds with the stretch bowtie2 2.3.0-2 but > FTBFS with the sid bowtie2 2.3.1-1 Do we already know whether the newer upstream version fixes this? Sascha: could you try to import it and pehaps upload it to unstable? Given there is already a difference between testing and unstable (2.6.1 vs 2.7.1) it shouldn't make much difference at this point even in the freeze… -- 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#856474: [PATCH] Kbuild.include: addtree: Remove quotes before matching path
Hi Sam, 2017-04-04 5:20 GMT+09:00 Sam Ravnborg: > On Mon, Apr 03, 2017 at 03:25:10PM +0200, Michal Marek wrote: >> On 2017-04-03 09:42, Masahiro Yamada wrote: >> > Each Makefile knows it wants to see >> > additional headers in the source tree, or objtree. >> > >> > I am guessing the right approach in a long run is, >> > we require -I to specify $(srctree) or $(objtree) explicitly. >> > >> > ccflags-y := -I$(srctree)/foo/bar/baz >> > >> > or >> > >> > ccflags-y := -I$(objtree)/foo/bar/baz >> > >> > >> > (For the latter, we can omit $(objtree)/ as it is ./) >> > >> > >> > Then, delete $(call flags,_c_flags) after the conversion. >> >> Agreed. The addtree function is more of a hack to make things just work >> with O=, but AFAIK there is no clean way to implement VPATH for -I >> arguments. So it's sensible to get rid of the hack. It looks like it's >> going to be lot of work though: >> >> $ git grep -e '-I' -- '*Makefile*' | wc -l >> 732 >> $ git grep -e '-I *\$(\(src\|obj\)tree)' -- '*Makefile*' | wc -l >> 166 > > There was a goal long time ago that moving the kernel source should > not trigger a rebuild. > Any hardcoded path would violate this (like $(srctree), $(objtree)) Even if we avoid hard-coding $(srctree) in each Makefile, "addtree" will modify the -I paths and the modified paths will be recorded in .*.cmd files. If we really want to achieve the goal, my old patch seemed to have a point: https://patchwork.kernel.org/patch/4511991/ This was rejected due to side effects, anyway. -- Best Regards Masahiro Yamada
Bug#839100: debian pybluez package version 0.22-1 uses upstream source code version 0.18
Oh dear. This means that python-bluez does not support python3 in Stretch, even though that support was added in v0.20 (released Jan 2014). That's quite bad. But apparently no-one noticed in time to fix it for Stretch. I'm looking to see how easy the update to the real 0.22 is. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: Digital signature
Bug#858904: openscad: opengl / x11 strange "hanging" error (also found in other packages)
ok yes after using openscad consistently for several days now, i get recurrence of this well-known behaviour quite frequently. if i was to put an arbitrary percentage on it, it would be about... 2% (1-in-50) of every attempted move/rotate operation with the mouse. anyway, main point of this bugreport is to alert you: it's not openscad, it's definitely a dependency *of* openscad. l.
Bug#859481: mariadb-10.0: N
Source: mariadb-10.0 Severity: wishlist Tags: l10n patch Dear Maintainer, Here's Japanese po-debconf templates translation (ja.po) file that reviewed by several Japanese Debian developers and users. Please copy the attachment into debian/po/ja.po. Kind regards. -- Takuma Yamada -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ja.po.gz Description: application/gzip
Bug#859480: ITP: fonts-source-han-serif -- set of OpenType/CFF Pan-CJK fonts
Just like Noto Sans CJK, Noto Serif CJK is also in Google noto-cjk repository, so we can just add this fonts into fonts-noto-cjk package instead of creating new package for it. [0] https://github.com/googlei18n/noto-cjk -- ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org http://czchen.info/ Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B signature.asc Description: PGP signature
Bug#859480: ITP: fonts-source-han-serif -- set of OpenType/CFF Pan-CJK fonts
Package: wnpp Severity: wishlist Owner: "ChangZhuo Chen (陳昌倬)"* Package name: fonts-source-han-serif Version : 1.000R Upstream Author : Adobe Inc. * URL : https://github.com/adobe-fonts/source-han-serif * License : SIL-1.1 Programming Lang: fonts Description : set of OpenType/CFF Pan-CJK fonts Source Han Serif is a set of OpenType/CFF Pan-CJK fonts. In addition to functional OpenType fonts, this open source project provides all of the source files that were used to build these OpenType fonts by using the AFDKO makeotf and otf2otc tools. This package will be maintained by Debian Fonts Task Force. -- ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org http://czchen.info/ Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B signature.asc Description: PGP signature
Bug#858617: Fails to load certain JPEG files
Control: forwarded -1 https://bugs.launchpad.net/inkscape/+bug/1679442 Control: tag -1 upstream On Fri, Mar 24, 2017 at 03:51:06PM +0100, Yuri D'Elia wrote: > inkscape fails to load (or import) the following 1.4Mb image file: > > https://gemex.eurac.edu/dl/?t=ada658ec062a8ff67c9360852058c3f1 > > This is a (seemingly) standard JPEG image produced by OpenCamera on Android. > Interestingly, it fails to load only in inkscape. weird bug. Thanks for it, I forwarded it upstream. You may follow eventual progress on the link above. -- 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#859479: qmidiarp's lv2 plug-ins not recognized by qtractor.They are installed in "/usr/lib/x86_64-linux-gnu" instead of "/usr/lib/lv2". The plug-ins are recognized when placed in "/usr/lib/lv2".
Package: qmidiarp Version: 0.6.4-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? installing from debian repos through synaptic. * What exactly did you do (or not do) that was effective (or ineffective)? moved plugins to correct directory. * What was the outcome of this action? fully functional. * What outcome did you expect instead? n/a *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.13-lowlatency (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qmidiarp depends on: ii libasound21.1.3-5 ii libc6 2.24-9 ii libgcc1 1:6.3.0-11 ii libjack-jackd2-0 [libjack-0.116] 2:1.9.11~20161209-1~kxstudio5v5 ii liblo70.28-5+b2 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5widgets55.7.1+dfsg-3+b1 ii libstdc++66.3.0-11 Versions of packages qmidiarp recommends: ii jackd 5 qmidiarp suggests no packages. -- no debconf information
Bug#859426: vim: Vim 8 cannot handle 'etags' format any more
On Mon, Apr 03, 2017 at 02:17:11PM +0200, Alexander Burger wrote: > When the file "tags" (or also "TAGS") was created with the 'etags' command, > e.g. > >$ etags file.c Which etags is this? There are various packages that provide the etags name. “update-alternatives --query etags” will tell you. Local experimentation would lead me to believe it's the one provided by exuberant-ctags, which generates a different format file than emacs' etags does. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#859238: RFS: microsoft-gsl/0.1~2017.03.20~git16a6a41-1
Control: owner -1 ! Control: tag -1 moreinfo On Sat, Apr 01, 2017 at 01:07:18AM +0300, Коля Гурьев wrote: > I am looking for a sponsor for my package "microsoft-gsl" Hi! > Package name: microsoft-gsl As others said already, 'microsoft' in the package name is a sad situation. Personally, is just a can of worms I do not want to open for so little, so please rename it to something else (I like 'ms-gsl'). > Version : 0.1~2017.03.20~git16a6a41-1 I recommend using 0 instead of 0.1 as base version. > dget -x > https://mentors.debian.net/debian/pool/main/m/microsoft-gsl/microsoft-gsl_0.1~2017.03.20~git16a6a41-1.dsc As I said privately, I'd enjoy having a git repository for this :) Here I feel you could enjoy even more baing the repo out of upstream git (see an example in the dehydrated package); or you can see my pencil2d package for an example of a thing building tarball out of upstream git, ready to be committed; as you prefer. * test building, I noticed it didn't take advantage of my quad-core system; why didn't you use compat level 10? * please send that UnitTest.patch upstream; that's clearly one of those cases their stupid system with a case-insensitive file system tricked them… * that empty directory tests/unittest-cpp, why didn't you remove it? -- 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#859478: offlineimap: 'maxage' comments are wrong, offlineimap DELETES your mails
Cyril Brulebois(2017-04-04): > Except… deleting a few mails from 2015 on the server with a little > python script using imaplib, and running offlineimap again leads to… > the same mails getting deleted from my laptop! Given the maxage > param was set to 90, I *think* 31-Dec-2015 happened before 90 days > ago, so clearly not a timezone thing. > > > Expected results: mails aren't on the server anymore (I deleted > them explicitly) BUT they're still on my laptop. Looking at the code, it seems “is that older than maxage?” is implemented by looking at the timestamp in the filename for local mails, which happens to be October 2016 for a mail received in 2015! I'm not sure what offlineimap did with the timestamps, but that's the bit of software responsible for all mails fetched over IMAP, so either timestamp handling is buggy or maxage implementation is buggy. Either way, it might make sense to be extra cautious when there are such bold claims in the documentation, we're talking about deletions here! KiBi. signature.asc Description: Digital signature
Bug#859268: debian-installer: French keyboard selected during install but QWERTY selected when logged in Gnome
Control: reassign -1 gnome-desktop c...@riseup.net, on sam. 01 avril 2017 16:17:00 +, wrote: > The installation was a standard one with encrypted LLVM and the French > keyboard layout selected. The installation ended successfully. When > booting, the French keyboard layout was used to type the passphrase to > unlock the disk and the password to login. > After login, the keyboard layout is QWERTY instead of the French layout, I can confirm the bug: I just installed with default options except french language (and thus France country and french keyboard layout) (no real need for LVM encrypted volume), and let it install the gnome desktop. The installed system does have /etc/default/keyboard containing XKBMODEL="pc105" XKBLAYOUT="fr" XKBVARIANT="latin9" XKBOPTIONS="" BACKSPACE="guess" The keyboard icon in the top right corner does propose between en and fr, but it defaults to en... Setting it to fr for the user fixes it for the user, but each new user gets the en default. Setting XKBVARIANT to "" instead of "latin9" does get fr enabled by default, but gnome should not require that: there are quite a few languages for which we do want to use the non-default variant, for various reasons. Other desktops (e.g. MATE) are not affected by the bug, thus reassigning. This is a very bad-looking bug for gnome... Samuel
Bug#859478: offlineimap: 'maxage' comments are wrong, offlineimap DELETES your mails
Package: offlineimap Version: 6.3.4-1+kibi1 Severity: critical Justification: causes serious data loss Hi, Looking at a way to stay below my mail quota, I've thought of using offlineimap's "maxage" feature, which is advertised like this: # Messages older than maxage days will not be synced, their flags will # not be changed, they will not be deleted etc. For offlineimap it will be like these # messages do not exist. This will perform an IMAP search in the case of IMAP or Gmail # and therefor requires that the server support server side searching. This will # calculate the earliest day that would be included in the search and include all # messages from that day until today. e.g. maxage = 3 to sync only the last 3 days mail Except… deleting a few mails from 2015 on the server with a little python script using imaplib, and running offlineimap again leads to… the same mails getting deleted from my laptop! Given the maxage param was set to 90, I *think* 31-Dec-2015 happened before 90 days ago, so clearly not a timezone thing. Expected results: mails aren't on the server anymore (I deleted them explicitly) BUT they're still on my laptop. KiBi.
Bug#859477: debian-live: Make desktop emit some sound on startup
Package: debian-live Severity: normal User: debian-accessibil...@lists.debian.org Usertags: a11y Hello, The debian live cd is accessible to blind people by pressing super-alt-s. It is however hard to know when one can press that shortcut. The desktop should thus emit some sound when it is ready to interpret shortcuts. Samuel -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.10.0 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#859476: onionbalance: onionbalance.service fails to add dependencies
Package: onionbalance Severity: important Tags: patch Dear Maintainer, systemd service fails, due to erroneous comma in `After` field: $ journalctl | grep onionbalance Mar 15 00:10:51 lab16 systemd[1]: [/lib/systemd/system/onionbalance.service:8] Failed to add dependency on network.target,, ignoring: Invalid argument $ cat /lib/systemd/system/onionbalance.service # OnionBalance systemd target [Unit] Description=OnionBalance - Tor Onion Service load balancer Documentation=man:onionbalance Documentation=file:///usr/share/doc/onionbalance/html/index.html Documentation=https://github.com/DonnchaC/onionbalance After=network.target, tor.target Wants=network-online.target ConditionPathExists=/etc/onionbalance/config.yaml [Service] Type=simple PIDFile=/run/onionbalance.pid Environment="ONIONBALANCE_LOG_LOCATION=/var/log/onionbalance/log" ExecStartPre=/usr/bin/install -Z -m 02750 -o onionbalance -g adm -d /var/run/onionbalance ExecStart=/usr/sbin/onionbalance -c /etc/onionbalance/config.yaml ExecReload=/usr/sbin/onionbalance reload ExecStop=-/sbin/start-stop-daemon --quiet --stop --retry=TERM/5/KILL/5 --pidfile /run/onionbalance.pid TimeoutStopSec=5 KillMode=mixed EnvironmentFile=-/etc/default/%p User=onionbalance PermissionsStartOnly=true Restart=on-abnormal RestartSec=2s LimitNOFILE=65536 # Hardening # AppArmorProfile=system_onionbalance # CapabilityBoundingSet=CAP_NET_BIND_SERVICE CAP_CHOWN CAP_FOWNER NoNewPrivileges=yes PrivateDevices=yes PrivateTmp=yes ProtectHome=yes ProtectSystem=full ReadOnlyDirectories=/ ReadWriteDirectories=-/proc ReadWriteDirectories=-/var/log/onionbalance ReadWriteDirectories=-/var/run [Install] WantedBy=multi-user.target The same typo (I assume it is just that) exists in all available Debian onionbalance packages I checked: jessie-backports 0.1.4-1~bpo8+1 stretch 0.1.6-1 sid 0.1.6-1 experimental 0.1.7-1 Proposed patch simply removes the erroneous comma. Originally filed as https://bugs.launchpad.net/ubuntu/+source/onionbalance/+bug/1672901 Regards. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100, 'xenial-backports') Architecture: amd64 (x86_64) Kernel: Linux 4.10.0-ck1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) --- a/lib/systemd/system/onionbalance.service +++ b/lib/systemd/system/onionbalance.service @@ -5,7 +5,7 @@ Documentation=man:onionbalance Documentation=file:///usr/share/doc/onionbalance/html/index.html Documentation=https://github.com/DonnchaC/onionbalance -After=network.target, tor.target +After=network.target tor.target Wants=network-online.target ConditionPathExists=/etc/onionbalance/config.yaml
Bug#768376: [libvirt-daemon-system]
Hi everyone Was upgrading one of my servers and noticed that libvirt broke completely. Turns out, "libvirt-daemon-system" could not be installed due to "policykit-1" dependency, which in turn depends on ...drum roll... "systemd", which is blacklisted on my systems. Manually extracting all the stuff from the package solved this for me. But it is kinda hacky way of doing it. Is it at least possible to separate initscripts to a separate package, not depending on systemd? TIA
Bug#859475: jessie-pu: package ndisc6/1.0.1-1+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi, the package rdnssd (from src:ndisc6) provides a daemon that listens to IPv6 RA messages containing RDNSS (recursive DNS servers) information, and adds this information to /etc/resolv.conf. It is automatically installed by d-i if this information is found during installation. If resolvconf is installed managing and merging of /etc/resolv.conf is handed over to it. However, if it is not installed the version in Jessie simply overwrites /etc/resolv.conf, which drops all search list information as well as IPv4 nameservers. This often leads to severe breakage of the installed system. This is tracked in Bug#767071 The proposed fix for Jessie will adjust the merge script to be the same as in current upstream and Stretch. The package builds a udeb, but the hook is only included in the "real" package. Best Regards, Bernhard diffstat for ndisc6_1.0.1-1 ndisc6_1.0.1-1+deb8u1 debian/changelog |7 +++ rdnssd/merge-hook.in | 51 --- 2 files changed, 55 insertions(+), 3 deletions(-) diff -u ndisc6-1.0.1/debian/changelog ndisc6-1.0.1/debian/changelog --- ndisc6-1.0.1/debian/changelog +++ ndisc6-1.0.1/debian/changelog @@ -1,3 +1,10 @@ +ndisc6 (1.0.1-1+deb8u1) jessie; urgency=medium + + * Use upstream default merge hook when resolvconf is not available +(Closes: #767071) + + -- Bernhard SchmidtTue, 04 Apr 2017 00:24:32 +0200 + ndisc6 (1.0.1-1) unstable; urgency=low * New upstream release: diff -u ndisc6-1.0.1/rdnssd/merge-hook.in ndisc6-1.0.1/rdnssd/merge-hook.in --- ndisc6-1.0.1/rdnssd/merge-hook.in +++ ndisc6-1.0.1/rdnssd/merge-hook.in @@ -20,9 +20,54 @@ -PATH=/sbin:/bin INPUT="/var/run/rdnssd/resolv.conf" +# Debian modification, use resolvconf if available if [ -x /sbin/resolvconf ]; then /sbin/resolvconf -a 000.rdnssd < "$INPUT" -else - cat -- "$INPUT" > "/etc/resolv.conf" + exit 0 fi +PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin + +# Max number of nameserver options taken into account. Should be as +# defined in +MAXNS=3 + +# This script tries to share available nameserver slots with IPv4 +# entries, for example to allow fallback to IPv4 if IPv6 fails. If +# there is not enough room for all IPv6 and IPv4 entries, this script +# will limit the IPv6 entries it adds to $RDNSS_LIMIT only. +RDNSS_LIMIT=$(($MAXNS - 1)) + +sysconfdir='@SYSCONFDIR@' +localstatedir='@LOCALSTATEDIR@' +resolvconf="$sysconfdir/resolv.conf" +myresolvconf="$localstatedir/run/rdnssd/resolv.conf" + +# These should be POSIX-compliant BREs +RE_NSV4='^nameserver *\([0-9]\{1,3\}\.\)\{3,3\}[0-9]\{1,3\} *$' +RE_NSV4OR6='^nameserver *[a-fA-F0-9:\.]\{1,46\}\(%[a-zA-Z0-9]\{1,\}\)\{,1\} *$' + +# Count how many IPv6 nameservers we can fit + +limit=$RDNSS_LIMIT + +nnsv4=`grep -c "$RE_NSV4" $resolvconf || [ $? -le 1 ]` +room=$(($MAXNS - $nnsv4)) + +if [ $limit -lt $room ]; then + limit=$room +fi + +# Merge and write the result. Let rdnssd assume ownership of all IPv6 +# nameservers, and remove extraneous IPv6 entries as expired. However +# DHCPv4 most often sets up search list entries, and rdnssd cannot +# clobber these lest it causes counterintuitive breakage. There is no +# easy way to properly merge and manage DNSSL entries here, so just drop +# them. +{ + sed -e "/$RE_NSV4OR6/d" < $resolvconf + grep -m $limit "$RE_NSV4OR6" < $myresolvconf || [ $? -le 1 ] + sed -ne "/$RE_NSV4/p" < $resolvconf +} > $resolvconf.tmp + +mv -f $resolvconf.tmp $resolvconf +
Bug#858784: aptitude: [INTL:it] Updated Italian translation of aptitude-doc po file
Control: tags -1 + pending 2017-03-26 21:05 Beatrice Torracca: Package: aptitude Version: 0.8.6-1 Severity: wishlist Tags: patch l10n Hi, I attach the updated Italian translation of the .po file of aptitude's manual. Please include it in your next upload, Applied, thanks! -- Manuel A. Fernandez Montecelo
Bug#858553: [Pkg-pascal-devel] Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files
Hi Lazarus Developers List, Can you please help on this issue? fpdoc fails when building Laazarus 1.6.2 documentation. This leads to a serious (RC) bug that may lead to remove Lazarus form next Debian release which will be really a pity. On Sat, 2017-04-01 at 21:45 +0200, Paul Gevers wrote: > First shot at debugging from my side. > > Because the error says: > Exception at 004BDB6C: EDOMError: > EDOMError in DOMDocument.CreateElement. > > I searched for "DOMDocument.CreateElement". Low and behold, I find > something interesting in fpcsrc/packages/fcl-xml/src/dom.pp: > > function TDOMDocument.CreateElement(const tagName: DOMString): TDOMElement; > begin > if not IsXmlName(tagName) then > raise EDOMError.Create(INVALID_CHARACTER_ERR, > 'DOMDocument.CreateElement'); > TDOMNode(Result) := Alloc(TDOMElement); > > Result.Create(Self); > Result.FNSI.QName := FNames.FindOrAdd(DOMPChar(tagName), Length(tagName)); > Result.AttachDefaultAttrs; > end; > > First idea that pops into my mind is: it looks like the source of > lazarus has characters that fp-docs can't convert. Apparently an error > is raised, but converted by fp-docs into exit code 0. > > Interesting to note, is the delta between 2.4.6 and 3.0.0: > - if not IsXmlName(tagName, FXMLVersion = xmlVersion11) then > + if not IsXmlName(tagName) then > which was done in this commit: > http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=revision=20422 > > Sending now as I am about to stop for today, but summary as I currently > suspect the situation is: > 1) fp-doc fails to create error exit code during error > 2) lazarus may have xml files that need updating. > > Probably the next time I spend time on this will be to bisect the > documentation creation to see which file(s) need fixing -> to > potentially solve issue 2 if that is indeed the issue. It looks like the file extctrls.pp or the corresponding xml is not supported by the used version of fpdoc. ]$fpdoc --content=lcl.xct --package=lcl --descr=../../xml/lcl/lcl.xml -- input='../../../lcl/extctrls.pp -Fi../../../lcl/include' --format=html -- descr=../../xml/lcl/extctrls.xmlFPDoc - Free Pascal Documentation ToolVersion 3.0.0 [2017/02/08](c) 2000 - 2003 Areca Systems GmbH / Sebastian Guenther, sg@fr eepascal.org(c) 2005 - 2012 various FPC contributors Writing 757 pages...Exception at 004BDACC: EDOMError:EDOMError in DOMDocument.CreateElement.While with an other page this leads to: $fpdoc --content=lcl.xct --package=lcl --descr=../../xml/lcl/lcl.xml -- input='../../../lcl/interfaces/gtk/gtkwsextctrls.pp -Fi../../../lcl/include' --format=html --descr=../../xml/lcl/interfaces/gtk/gtkwsextctrls.xmlFPDoc - Free Pascal Documentation ToolVersion 3.0.0 [2017/02/08](c) 2000 - 2003 Areca Systems GmbH / Sebastian Guenther, s...@freepascal.org(c) 2005 - 2012 various FPC contributors Writing 128 pages...Using built-in CSS fileCreating plus imageCreating minus imageDone.Here there are no errors. Just goes fine to end. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#729526: [Aptitude-devel] Bug#729526: ssh.deb: somewhat misleading description
Control: tags -1 - patch Not a patch for aptitude... -- Manuel A. Fernandez Montecelo
Bug#859474: Move mutter-restart-helper out to mutter-common
Package: mutter Version: 3.22.3-2 Severity: normal Hi, At the moment, mutter-restart-helper is included in the mutter package but this tool can be useful from outside mutter (e.g. GNOME Shell uses it via Meta.restart() (see [1]), so it would be probably a good idea to move it to mutter-common instead. We have been shipping this change in Endless for a while already (see [2]) and I think it would be nice to have it included in debian, as any other distro that might want to install just mutter-common would benefit of that. Thanks Mario [1] https://github.com/GNOME/gnome-shell/blob/d23bd4c4/js/ui/runDialog.js#L282 [2] https://github.com/endlessm/mutter/commit/46fa206c67ec8c0db40ed7c8a19b60d17447c152 -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.9-200.fc25.x86_64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages mutter depends on: ii gsettings-desktop-schemas 3.22.0-1 ii libc6 2.24-9 ii libglib2.0-0 2.50.3-2 ii libmutter0i3.22.3-2 ii libx11-6 2:1.6.4-3 ii libxcomposite1 1:0.4.4-2 ii mutter-common 3.22.3-2 ii zenity 3.22.0-1+b1 Versions of packages mutter recommends: ii gnome-session [x-session-manager] 3.22.3-1 Versions of packages mutter suggests: ii gnome-control-center 1:3.22.2-1 ii xdg-user-dirs 0.15-2+b1
Bug#729526: [Aptitude-devel] Bug#729526: ssh.deb: somewhat misleading description
Hi, First of all, and FWIW and on a personal note, I am happy with the current behaviour of aptitude, at least it's predictable :) , and forces me to think about the need of that package in my system. Judging by the bug reports that aptitude receives, one of the major complaints is when packages loose the auto-installed flag for whatever reason, even if leaving a package installed is harmless in most cases -- so I am not sure if changing this in the ways suggested would make (many) users more happy. Even with the current behaviour, in most cases the package will remain installed if it's recommended by other packages installed and so on, so the behaviour described in this bug report will not be triggered in many/most occasions even when the transitional package is removed (although maybe it's not very common to have dependencies on servers, as it's this case). Apart from all that, I am a bit confused about this whole bug report, because it's mentioned several times that the package is in "oldlibs" or that this is a "transitional" package and what happens when they are removed or "obsoleted", but "ssh" is neither. It's just, as the description says, a convenient (???) way to depend on both openssh-{client,server}, but it's not "transitioning to be removed" in any way, as far as I can see. Since it's not in "oldlibs" section, or "metapackages" or "obsolete" or anything of that sort, all the mechanisms that have been mentioned in previous messages of this bug report, such as Never-Markauto-Section, do not apply here. (And no, aptitude doesn't implement anything related with that variable at the moment). So this question instead is similar as to what happens when you have a "kde-desktop" or "kde-artwork" package depending on a bunch of default tools and data files -- should all those packages be marked as manually installed? Isn't then a hassle to go through 50 packages and explicitly remove them when you decide that you don't want KDE in your system after all? I think that there have been discussions about this in debian-devel not long ago, and I got the impression that there was no consensus on the matter. If we want the behaviour to be "installing kde-desktop is an alias to have all these packages installed" as a permanent action, so then we are able to remove that one while the others remain installed, perhaps it would be better to consider some different implementation, instead of "virtual metapackage" it would be something like "package actions". Otherwise, the idea of auto-installed package is completely unintuitive for these cases. "tasks" seem to fit well in this category, even the name is closer to "action" than to "meta-package". ...But then again, it's probably too big a change for a very small gain. So, in summary, I don't think that the solution proposed is better than the current behaviour [of aptitude]. I am not opposed to implement this, but in that case I would like to see some incipient consensus on the matter (or, if apt implements it in that way, I'm not that keen in overriding it). But for that to work properly, the "ssh" package would have to signal in some way that it's indeed a meta-package or intended to be obsoleted, for example being in section "oldlibs" (or even "metapackages"?) instead of simply "net", so at least package managers like apt and aptitude can infer something useful about it, rather than just try to guess whether the dependency on openssh-{client,server} is because it's a metapackage under cover. Lastly: 2017-04-02 11:55 David Kalnischkies: [...]. In case that isn't reimplemented in aptitude already, it might be a better idea to talk about this again at the start of buster as I want to move this out of the solver for a while now as we need that for the external solvers as well. It is just a matter of "how" API wise which probably will result in a bunch of code changes as well… so it is always "later". As a first step it might be interesting to figure out how the API would need to look for aptitude to be able to use it (or in which calls we can hide it to have no API for it at all as that is what we need to do for compat reasons for all other frontends). Perhaps as a simple boolean argument of a function, so a Remove() of "obsolete" / "oldlibs" package would consider keeping the dependencies based on APT::Never-MarkAuto-Sections and that flag (that is, setting the auto-installed bit on the dependencies to "manual", or not). Or perhaps no API exposure at all, just respecting that config option, and interested aptitude users would have to override the behaviour. Cheers. -- Manuel A. Fernandez Montecelo
Bug#847715: [Pkg-javascript-devel] Bug#847715: Plan to do a NMU
Here the diff, quite trivial diff --git a/debian/changelog b/debian/changelog index 8d6a8ec..25d57f9 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +node-resumer (0.0.0-2) unstable; urgency=medium + + * Team upload. + * Bug fix: "node-resumer depends on node-through2 (>= 2.3.4), but +only 2.0.3-1 is in unstable", thanks to Adrian Bunk (Closes: #847715). + + -- Bastien RoucarièsTue, 04 Apr 2017 00:12:33 +0200 + node-resumer (0.0.0-1) unstable; urgency=low * Initial release (Closes: #814286) diff --git a/debian/control b/debian/control index a06010f..9f4222e 100644 --- a/debian/control +++ b/debian/control @@ -15,7 +15,7 @@ Package: node-resumer Architecture: all Depends: ${misc:Depends}, nodejs, - node-through2 (>= 2.3.4) + node-through2 (>= 2.0) Description: through stream that starts paused and resumes on the next tick Return a through stream that starts out paused and resumes on the next tick, unless somebody called .pause(). On Tue, Apr 4, 2017 at 12:03 AM, Bastien ROUCARIES wrote: > Hi, > > I plan to do a NMU on this one. > > Do you want the diff ?. > > Bastien > > -- > Pkg-javascript-devel mailing list > pkg-javascript-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Bug#847715: Plan to do a NMU
Hi, I plan to do a NMU on this one. Do you want the diff ?. Bastien
Bug#859473: mate-desktop: have mate 1.18 in experimental
Package: mate-desktop Version: 1.16.1-1 Severity: wishlist Dear Maintainer, I know that Debian is in full-freeze at the current state of affairs so it probably is not possible to release the just released mate 1.18 on sid/unstable and hence maybe an attempt to release it to experimental can be made. The below blog post shares the changes between the new and the old versions - http://mate-desktop.org/blog/2017-03-13-mate-1-18-released/ Also with the recent new build of gtk+3.0 it might also make sense to have the new release in experimental https://tracker.debian.org/pkg/gtk+3.0 Looking forward to seeing mate 1.18 in experimental. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (600, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (1, 'experimental-debug'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mate-desktop depends on: ii hicolor-icon-theme0.15-1 ii libatk1.0-0 2.22.0-1 ii libc6 2.24-9 ii libcairo-gobject2 1.14.8-1 ii libcairo2 1.14.8-1 ii libgdk-pixbuf2.0-02.36.5-2 ii libglib2.0-0 2.50.3-2 ii libgtk-3-03.22.11-1 ii libmate-desktop-2-17 1.16.1-1 ii libpango-1.0-01.40.4-1 ii libpangocairo-1.0-0 1.40.4-1 ii libstartup-notification0 0.12-4+b2 ii libxrandr22:1.5.1-1 ii mate-desktop-common 1.16.1-1 ii python2.7.13-2 ii python-requests 2.12.4-1 Versions of packages mate-desktop recommends: ii mate-user-guide 1.16.0-1 mate-desktop suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#859472: khal FTBFS: tests/event_test.py:307: AssertionError
Source: khal Version: 0.9.4-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=khal=all=0.9.4-1=1491255368=0 ... debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' mkdir -p debian/tmp/locale/ localedef -f UTF-8 -i en_US ./debian/tmp/locale/en_US.UTF-8/ localedef -f UTF-8 -i de_DE ./debian/tmp/locale/de_DE.UTF-8/ localedef -f UTF-8 -i cs_CZ ./debian/tmp/locale/cs_CZ.UTF-8/ localedef -f UTF-8 -i el_GR ./debian/tmp/locale/el_GR.UTF-8/ export LOCPATH=/«PKGBUILDDIR»/debian/tmp/locale/ && \ export LC_ALL=en_US.UTF-8 && \ LC_ALL=en_US.UTF-8 dh_auto_test I: pybuild base:184: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build; python3.5 -m pytest tests = test session starts == platform linux -- Python 3.5.3, pytest-3.0.6, py-1.4.32, pluggy-0.4.0 rootdir: /«PKGBUILDDIR», inifile: collected 259 items tests/backend_test.py .. tests/cal_display_test.py ..s... tests/cli_test.py tests/configwizard_test.py . tests/controller_test.py tests/event_test.py ..F tests/khalendar_test.py . tests/khalendar_utils_test.py .s...s..s. tests/settings_test.py ... tests/terminal_test.py ... tests/utils_test.py ..ss... tests/vdir_test.py x.. tests/vtimezone_test.py ..F tests/ui/test_calendarwidget.py ..s tests/ui/test_editor.py . tests/ui/test_widgets.py . === FAILURES === __ test_event_no_dst ___ def test_event_no_dst(): """test the creation of a corect VTIMEZONE for timezones with no dst""" event_no_dst = _get_text('event_no_dst') cal_no_dst = _get_text('cal_no_dst') event = Event.fromString(event_no_dst, calendar='foobar', locale=LOCALE_BOGOTA) > assert normalize_component(event.raw) == normalize_component(cal_no_dst) E assert ('VCALENDAR',...enset())}))})) == ('VCALENDAR', ...enset())}))})) E At index 2 diff: frozenset({('VTIMEZONE', b'BEGIN:VTIMEZONE\r\nTZID:America/Bogota\r\nEND:VTIMEZONE\r\n', frozenset({('STANDARD', b'BEGIN:STANDARD\r\nDTSTART;VALUE=DATE-TIME:19930403T23\r\nTZNAME:-05\r\nTZOFFSETFROM:-0400\r\nTZOFFSETTO:-0500\r\nEND:STANDARD\r\n', frozenset())})), ('VEVENT', b'BEGIN:VEVENT\r\nSUMMARY:An Event\r\nDTSTART;TZID=America/Bogota;VALUE=DATE-TIME:20140409T093000\r\nDTEND;TZID=America/Bogota;VALUE=DATE-TIME:20140409T103000\r\nDTSTAMP;VALUE=DATE-TIME:20140401T234817Z\r\nUID:event_no_dst\r\nEND:VEVENT\r\n', frozenset())}) != frozenset({('VTIMEZONE', b'BEGIN:VTIMEZONE\r\nTZID:America/Bogota\r\nEND:VTIMEZONE\r\n', frozenset({('STANDARD', b'BEGIN:STANDARD\r\nDTSTART;VALUE=DATE-TIME:19930403T23\r\nTZNAME:COT\r\nTZOFFSETFROM:-0400\r\nTZOFFSETTO:-0500\r\nEND:STANDARD\r\n', frozenset())})), ('VEVENT', b'BEGIN:VEVENT\r\nSUMMARY:An Event\r\nDTSTART;TZID=America/Bogota;VALUE=DATE-TIME:20140409T093000\r\nDTEND;TZID=America/Bogota;VALUE=DATE-TIME:20140409T103000\r\nDTSTAMP;VALUE=DATE-TIME:20140401T234817Z\r\nUID:event_no_dst\r\nEND:VEVENT\r\n', frozenset())}) E Use -v to get the full diff E Detailed information truncated (-7 more lines), use "-vv" to show tests/event_test.py:307: AssertionError _ test_bogota __ def test_bogota(): vbogota = [b'BEGIN:VTIMEZONE', b'TZID:America/Bogota', b'BEGIN:STANDARD', b'DTSTART;VALUE=DATE-TIME:19930403T23', b'TZNAME:COT', b'TZOFFSETFROM:-0400', b'TZOFFSETTO:-0500', b'END:STANDARD', b'END:VTIMEZONE', b''] > assert create_timezone(bogota, atime, atime).to_ical().split(b'\r\n') > == vbogota E assert [b'BEGIN:VTIM...M:-0400', ...] == [b'BEGIN:VTIME...M:-0400', ...] E At index 4 diff: b'TZNAME:-05' != b'TZNAME:COT' E Use -v to get the full diff tests/vtimezone_test.py:75: AssertionError == 2 failed, 249 passed, 7 skipped, 1 xfailed in 8.06 seconds == E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build; python3.5 -m pytest tests dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned exit code 13 debian/rules:26: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 25 make[1]: Leaving directory '/«PKGBUILDDIR»' debian/rules:6: recipe for target 'build-indep' failed make: *** [build-indep] Error 2
Bug#859348: [Debian-ha-maintainers] Bug#859348: resource-agents: none
On Sun, Apr 02, 2017 at 06:11:30PM +0200, Guillaume Lécroart wrote: > - local vgchange_options=$(get_activate_options) > + local vgchange_options="$(get_activate_options)" Right, this line is fixed in 4.0.0~rc1, we'll need to upload that to backports. -- Valentin
Bug#798278: node-tape: team and good news
On Mon, Apr 3, 2017 at 6:11 PM, Bastien ROUCARIESwrote: > Hi, > > I achieved to package node-tape and it is relativly easy. > > It need patching in order to avoid some surprise but it is nice. > > Ross I am now a dd and I can upload but I need to upload a fixed resumer. > > Can I upload and add myself to resumer ? Hi, The git tree is here > > Thanks > > Bastien
Bug#798278: node-tape: team and good news
On Mon, Apr 3, 2017 at 11:43 PM, Bastien ROUCARIESwrote: > On Mon, Apr 3, 2017 at 6:11 PM, Bastien ROUCARIES > wrote: >> Hi, >> >> I achieved to package node-tape and it is relativly easy. >> >> It need patching in order to avoid some surprise but it is nice. >> >> Ross I am now a dd and I can upload but I need to upload a fixed resumer. >> >> Can I upload and add myself to resumer ? > > Hi, > > The git tree is here https://anonscm.debian.org/git/collab-maint/node-tape.git > > >> >> Thanks >> >> Bastien
Bug#61210: Comment
Hello, Perhaps this is a sight duplicate to Bug 36019? :wq! PoC
Bug#36019: Status of Hooks for adduser/deluser?
Hello, since there’s only infrequent updates on this one, I’d like to ask if there has been any progress on the topic? :wq! PoC
Bug#859471: unblock: swh-plugins/0.4.17-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, Please unblock package swh-plugins It fixes RC bug #859395 where one of the plugins was not linked correctly and ld.so refused to load it. I also fixed the Breaks / Replaces on vocoder-ladspa because 0.4.17-1 was so wrong I couldn't just leave it. I've moved it into the correct paragraph of the control file, and changed the package to "vocoder-ladspa" which was the actual package containing the vocoder plugin which was moved to swh-plugins (see #826110). Thanks, James unblock swh-plugins/0.4.17-2 -- System Information: Debian Release: 9.0 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.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru swh-plugins-0.4.17/debian/changelog swh-plugins-0.4.17/debian/changelog --- swh-plugins-0.4.17/debian/changelog 2016-11-05 04:47:12.0 + +++ swh-plugins-0.4.17/debian/changelog 2017-04-03 19:54:39.0 +0100 @@ -1,3 +1,12 @@ +swh-plugins (0.4.17-2) unstable; urgency=medium + + * Team upload. + * Link gsm_1215.so plugin against system libgsm. (Closes: #859395) + * Fix vocoder-ladspa Breaks/Replaces (replacing the faulty lmms +Breaks/Replaces). + + -- James CowgillMon, 03 Apr 2017 19:54:39 +0100 + swh-plugins (0.4.17-1) unstable; urgency=medium * Exclude .gitignore file from upstream tarball. diff -Nru swh-plugins-0.4.17/debian/control swh-plugins-0.4.17/debian/control --- swh-plugins-0.4.17/debian/control 2016-11-05 04:47:12.0 + +++ swh-plugins-0.4.17/debian/control 2017-04-03 19:54:39.0 +0100 @@ -16,11 +16,6 @@ libxml-parser-perl, libgsm1-dev, pkg-config -Replaces: - lmms (<= 1.1.3-2) - ${cdbs:Replaces} -Breaks: - lmms (<= 1.1.3-2) Standards-Version: 3.9.8 Homepage: http://plugin.org.uk/ Vcs-Git: https://anonscm.debian.org/git/pkg-multimedia/swh-plugins.git @@ -31,6 +26,11 @@ Depends: ${misc:Depends}, ${shlibs:Depends} +Replaces: + vocoder-ladspa (<< 1.1.3-3~), + ${cdbs:Replaces} +Breaks: + vocoder-ladspa (<< 1.1.3-3~) Provides: ladspa-plugin Description: Steve Harris's LADSPA plugins diff -Nru swh-plugins-0.4.17/debian/patches/08-gsm_plugin.patch swh-plugins-0.4.17/debian/patches/08-gsm_plugin.patch --- swh-plugins-0.4.17/debian/patches/08-gsm_plugin.patch 2016-06-02 00:32:48.0 +0100 +++ swh-plugins-0.4.17/debian/patches/08-gsm_plugin.patch 2017-04-03 19:54:39.0 +0100 @@ -45,7 +45,7 @@ sc4m_1916_la_LIBADD = -Lutil -ldb -lrms se4_1883_la_LIBADD = -Lutil -ldb -lrms -gsm_1215_la_LIBADD = gsm/libgsm.a -+#gsm_1215_la_LIBADD = gsm/libgsm.a ++gsm_1215_la_LIBADD = -lgsm gverb_1216_la_LIBADD = -Lgverb -lgverb lcr_delay_1436_la_DEPENDENCIES = util/biquad.h signature.asc Description: OpenPGP digital signature
Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files
On Sat, 2017-04-01 at 13:15 +0200, Paul Gevers wrote: > I don't remember seeing > any further information from Abou or upstream after the note I quoted above. Sorry, I was unable to look for this due to some personal issues. I'm going to dig in this this week and hope can get rid of it this WE. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#859437: unblock: util-linux/2.29.2-1
Andreas Henriksson(2017-04-03): > On Mon, Apr 03, 2017 at 10:52:13PM +0200, Cyril Brulebois wrote: > > No objections based on a quick read of the changelog, beware of “PT” > > (for GPT) in src/context.c and “entreis” (for entries) in src/gpt.c. > > As far as I can see PT (where used in code comments) are intentional > meaning "(any kind of) partition table", ie. MBR or GPT (or both) > not necessarily just GPT. If you think otherwise (and care to bother) > please point out the exact error more clearly (because I might just be > too tired to see it). ACK, sorry; just a wild guess since the gpt.c hunk was next. KiBi, shutting up. signature.asc Description: Digital signature
Bug#859470: unblock: flatpak/0.8.5-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package flatpak. This is a new upstream stable release; notably, it includes use-after-free and memory leak fixes in the D-Bus proxy (which is a security boundary), and protects against accidental or malicious downgrades. Filtered debdiff attached. The vast majority of the debdiff is accounted for by the fixes mentioned above; the rest is described in the changelog below. unblock flatpak/0.8.5-1 flatpak (0.8.5-1) unstable; urgency=medium * New upstream bugfix release * Upstream security fixes: - dbus-proxy: Fix a use-after-free (no specific exploit is known) and several memory leaks - system-helper: Correct the check that was meant to prevent unprivileged users from downgrading system-wide-installed apps - Do not allow downgrading apps to validly-signed older versions unless a specific older version is requested, so that a man-in-the-middle cannot cause a downgrade to an older app version with a vulnerability * Other upstream fixes: - Increase GLib build-dependency to 2.44 (in practice this was already required, there is a patch in jessie-backports to relax this) - Collect system extension references from all system directories, not just the first that exists (upstream issue 654) - Stop using ostree trivial-httpd, which is not available in post-stretch ostree (upstream issues 658, 723) - Be build-time compatible with post-stretch ostree (upstream issue 756) - Strip ?query suffix before detecting whether a URI points to a .flatpakref or .flatpakrepo file (upstream issue 659) - Fix a typo in help output * d/tests/control: most tests now require python, for the ostree-trivial-httpd replacement -- Simon McVittieMon, 03 Apr 2017 16:35:44 +0100 Thanks, S diffstat for flatpak-0.8.4 flatpak-0.8.5 NEWS | 30 app/flatpak-builtins-add-remote.c |2 app/flatpak-builtins-install.c|4 app/flatpak-builtins-update.c |2 common/flatpak-dir.c | 49 ++- common/flatpak-dir.h |1 common/flatpak-utils.c| 49 +++ common/flatpak-utils.h| 12 + configure.ac |8 - dbus-proxy/flatpak-proxy.c| 251 +- debian/changelog | 30 debian/control|2 debian/tests/control | 11 - lib/flatpak-version-macros.h |2 tests/Makefile.am.inc |1 tests/libtest.sh |5 tests/package_version.txt |2 tests/test-oci.sh |5 tests/test-run.sh | 15 ++ tests/test-webserver.sh | 21 +++ tests/testlibrary.c | 16 ++ 21 files changed, 355 insertions(+), 163 deletions(-) diff -Nru --exclude po --exclude Makefile.in --exclude html --exclude configure flatpak-0.8.4/app/flatpak-builtins-add-remote.c flatpak-0.8.5/app/flatpak-builtins-add-remote.c --- flatpak-0.8.4/app/flatpak-builtins-add-remote.c 2017-03-10 09:17:20.0 + +++ flatpak-0.8.5/app/flatpak-builtins-add-remote.c 2017-04-03 12:44:34.0 +0100 @@ -398,7 +398,7 @@ } if (opt_from || - g_str_has_suffix (location, ".flatpakrepo")) + flatpak_file_arg_has_suffix (location, ".flatpakrepo")) { load_options (location, _data); if (opt_url == NULL) diff -Nru --exclude po --exclude Makefile.in --exclude html --exclude configure flatpak-0.8.4/app/flatpak-builtins-install.c flatpak-0.8.5/app/flatpak-builtins-install.c --- flatpak-0.8.4/app/flatpak-builtins-install.c 2017-03-10 09:17:20.0 + +++ flatpak-0.8.5/app/flatpak-builtins-install.c 2017-04-03 12:46:15.0 +0100 @@ -440,9 +440,9 @@ if (!opt_bundle && !opt_from && !opt_oci && argc >= 2) { - if (g_str_has_suffix (argv[1], ".flatpakref")) + if (flatpak_file_arg_has_suffix (argv[1], ".flatpakref")) opt_from = TRUE; - if (g_str_has_suffix (argv[1], ".flatpak")) + if (flatpak_file_arg_has_suffix (argv[1], ".flatpak")) opt_bundle = TRUE; } diff -Nru --exclude po --exclude Makefile.in --exclude html --exclude configure flatpak-0.8.4/app/flatpak-builtins-update.c flatpak-0.8.5/app/flatpak-builtins-update.c --- flatpak-0.8.4/app/flatpak-builtins-update.c 2017-02-10 15:13:02.0 + +++ flatpak-0.8.5/app/flatpak-builtins-update.c 2017-04-03 12:29:24.0 +0100 @@ -60,7 +60,7 @@ { "app", 0, 0, G_OPTION_ARG_NONE, _app, N_("Look for app with the specified name"), NULL }, { "appstream", 0, 0, G_OPTION_ARG_NONE, _appstream, N_("Update appstream for remote"), NULL }, { "subpath", 0, 0, G_OPTION_ARG_FILENAME_ARRAY, _subpaths, N_("Only update this subpath"), N_("PATH") }, - {
Bug#787404: [pkg-ntp-maintainers] Bug#787404: ntp_intres.request: permission denied
On Mon, Apr 03, 2017 at 11:22:19PM +0200, Bernhard Schmidt wrote: > On Mon, Apr 03, 2017 at 11:15:35PM +0200, Kurt Roeckx wrote: > > HI, > > > > I tried to reproduce this with current Jessie and the future Stretch > > > release. As far as I can tell ntp handles this situation just fine. > > > > > > When ntpd starts up and cannot resolve the servers it logs > > > > > > ntpd[...]: Deferring DNS for 0.debian.pool.ntp.org 1 > > > ntpd_initres[...]: host name not found: 0.debian.pool.ntp.org > > > > > > as soon as DNS and/or network connectivity is available again (a couple > > > of minutes later) it logs > > > > > > ntpd_initres[...]: DNS 0.debian.pool.ntp.org -> IP > > > > > > and starts using this server. > > > > As far as I know, this only works with the "pool" command, not > > with any of the server commands. > > Don't think so, I've tested in on Jessie which still uses "server" in > the default configuration. Worked just fine. Sometimes it works, sometimes it fails, without changing any configuration. I think the case that fails is waiting a very long time to bring up the network. Kurt
Bug#787404: [pkg-ntp-maintainers] Bug#787404: ntp_intres.request: permission denied
On Mon, Apr 03, 2017 at 11:15:35PM +0200, Kurt Roeckx wrote: HI, > > I tried to reproduce this with current Jessie and the future Stretch > > release. As far as I can tell ntp handles this situation just fine. > > > > When ntpd starts up and cannot resolve the servers it logs > > > > ntpd[...]: Deferring DNS for 0.debian.pool.ntp.org 1 > > ntpd_initres[...]: host name not found: 0.debian.pool.ntp.org > > > > as soon as DNS and/or network connectivity is available again (a couple > > of minutes later) it logs > > > > ntpd_initres[...]: DNS 0.debian.pool.ntp.org -> IP > > > > and starts using this server. > > As far as I know, this only works with the "pool" command, not > with any of the server commands. Don't think so, I've tested in on Jessie which still uses "server" in the default configuration. Worked just fine. Bernhard signature.asc Description: Digital signature
Bug#859437: unblock: util-linux/2.29.2-1
Hi, On Mon, Apr 03, 2017 at 10:52:13PM +0200, Cyril Brulebois wrote: > No objections based on a quick read of the changelog, beware of “PT” > (for GPT) in src/context.c and “entreis” (for entries) in src/gpt.c. As far as I can see PT (where used in code comments) are intentional meaning "(any kind of) partition table", ie. MBR or GPT (or both) not necessarily just GPT. If you think otherwise (and care to bother) please point out the exact error more clearly (because I might just be too tired to see it). I've notified upstream about the "entreis" debug message typo. (Spotted "memu" myself recently, which I mentioned and it was swiftly fixed in upstream master branch...) Thanks. Regards, Andreas Henriksson
Bug#787404: [pkg-ntp-maintainers] Bug#787404: ntp_intres.request: permission denied
On Mon, Apr 03, 2017 at 10:59:07PM +0200, Bernhard Schmidt wrote: > Control: tags -1 + moreinfo unreproducible > > On Mon, Jun 01, 2015 at 09:16:05AM +0100, Klaus Ethgen wrote: > > > This is a successor of bug #571469. All is said there. NTP needs running > > DNS when it starts. Please add $named to Required-Start in init script. > > > > Funny thing, reportbug does include my changed init.d script below but > > not the changed part: > ># Required-Start: $network $remote_fs $syslog $named > > > > In my setup, ntp and dns was start at the same runlevel. But as > > "unbounce" comes lexically after "ntp", ntp was start first. With bind, > > that could work as "bind" is lexically earlier in the list. However, > > There is a dependency between ntp and dns so that dependency has to be > > configured correctly. > > I tried to reproduce this with current Jessie and the future Stretch > release. As far as I can tell ntp handles this situation just fine. > > When ntpd starts up and cannot resolve the servers it logs > > ntpd[...]: Deferring DNS for 0.debian.pool.ntp.org 1 > ntpd_initres[...]: host name not found: 0.debian.pool.ntp.org > > as soon as DNS and/or network connectivity is available again (a couple > of minutes later) it logs > > ntpd_initres[...]: DNS 0.debian.pool.ntp.org -> IP > > and starts using this server. As far as I know, this only works with the "pool" command, not with any of the server commands. Kurt
Bug#858860: RFS: arpwatch [ITA]
Hi security tools packaging team, On Mon, 27 Mar 2017 23:03:19 +0200 Lukas Schwaighoferwrote: > Gianfranco suggested also asking the pkg-security-team for possible > sponsors. It would be great if one of you could have a look and > provide guidance! If team maintenance is be possible, I'd like that > very much. I think arpwatch would be a good fit for the team. Is there somebody willing to review my packaging work? There is, of course, no rush. I would just like to know if somebody from pkg-security plans to look at the package eventually or if I should start looking someplace else for reviewers/sponsors. Thanks Lukas pgpml4vQjvHGW.pgp Description: OpenPGP digital signature
Bug#859468: unblock: libvpx/1.6.1-3
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Please unblock package libvpx. unblock libvpx/1.6.1-3 diffstat for libvpx-1.6.1 libvpx-1.6.1 changelog |9 + control |1 + rules |2 +- 3 files changed, 11 insertions(+), 1 deletion(-) diff -Nru libvpx-1.6.1/debian/changelog libvpx-1.6.1/debian/changelog --- libvpx-1.6.1/debian/changelog 2017-01-17 17:23:34.0 +0100 +++ libvpx-1.6.1/debian/changelog 2017-04-03 23:06:37.0 +0200 @@ -1,3 +1,12 @@ +libvpx (1.6.1-3) unstable; urgency=medium + + * Team upload. + * Mark libvpx-doc as Multi-Arch:foreign. + * Do not forcefully disable PIE anymore as -pie changed meaning. +(Closes: #859415) + + -- Mattia RizzoloMon, 03 Apr 2017 23:06:37 +0200 + libvpx (1.6.1-2) unstable; urgency=medium * Add arm64 native support diff -Nru libvpx-1.6.1/debian/control libvpx-1.6.1/debian/control --- libvpx-1.6.1/debian/control 2016-11-07 23:01:52.0 +0100 +++ libvpx-1.6.1/debian/control 2017-04-03 23:05:27.0 +0200 @@ -45,6 +45,7 @@ Package: libvpx-doc Section: doc Architecture: all +Multi-Arch: foreign Depends: ${misc:Depends} Recommends: lynx | www-browser Description: VP8 and VP9 video codec (API documentation) diff -Nru libvpx-1.6.1/debian/rules libvpx-1.6.1/debian/rules --- libvpx-1.6.1/debian/rules 2017-01-17 16:59:57.0 +0100 +++ libvpx-1.6.1/debian/rules 2017-04-03 23:06:19.0 +0200 @@ -1,6 +1,6 @@ #!/usr/bin/make -f -export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie +export DEB_BUILD_MAINT_OPTIONS = hardening=+all DEB_CFLAGS_MAINT_APPEND = -Wall DEB_CXXFLAGS_MAINT_APPEND = -Wall -- 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#859469: unblock: gnuplot/5.0.5+dfsg1-6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gnuplot unblock gnuplot/5.0.5+dfsg1-6 diffstat for gnuplot-5.0.5+dfsg1 gnuplot-5.0.5+dfsg1 changelog |9 + control |1 + rules |2 +- 3 files changed, 11 insertions(+), 1 deletion(-) diff -Nru gnuplot-5.0.5+dfsg1/debian/changelog gnuplot-5.0.5+dfsg1/debian/changelog --- gnuplot-5.0.5+dfsg1/debian/changelog2017-01-08 20:39:38.0 +0100 +++ gnuplot-5.0.5+dfsg1/debian/changelog2017-04-03 22:58:59.0 +0200 @@ -1,3 +1,12 @@ +gnuplot (5.0.5+dfsg1-6) unstable; urgency=medium + + * Team upload. + * [0f55a7f] Mark gnuplot-doc as Multi-Arch:foreign. + * [9be6254] Do not forcefully disable PIE anymore as -pie changed meaning. +(Closes: #859370) + + -- Mattia RizzoloMon, 03 Apr 2017 22:58:59 +0200 + gnuplot (5.0.5+dfsg1-5) unstable; urgency=medium [ Anton Gladky ] diff -Nru gnuplot-5.0.5+dfsg1/debian/control gnuplot-5.0.5+dfsg1/debian/control --- gnuplot-5.0.5+dfsg1/debian/control 2017-01-08 20:38:38.0 +0100 +++ gnuplot-5.0.5+dfsg1/debian/control 2017-04-03 22:56:25.0 +0200 @@ -62,6 +62,7 @@ Package: gnuplot-doc Architecture: all +Multi-Arch: foreign Section: doc Depends: ${misc:Depends} Breaks: gnuplot (<< 5.0.5+dfsg1-4~) diff -Nru gnuplot-5.0.5+dfsg1/debian/rules gnuplot-5.0.5+dfsg1/debian/rules --- gnuplot-5.0.5+dfsg1/debian/rules2016-11-16 20:16:02.0 +0100 +++ gnuplot-5.0.5+dfsg1/debian/rules2017-04-03 22:56:50.0 +0200 @@ -3,7 +3,7 @@ %: dh $@ --parallel -export DEB_BUILD_MAINT_OPTIONS := hardening=+all,-pie +export DEB_BUILD_MAINT_OPTIONS := hardening=+all export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed # Tell compiler where should find lua headers -- 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#599179: po4a: --rm-translations also updates PO/POT files
tag 599179 fixed-upstream tag 599179 pending thanks Hello, I just added a flag --no-update to the upstream version (not released yet). I think that this fixes the issue. I fully agree with Denis that this option is rather dangerous and that it will probably be misused by some people. But at the same time, that's not a reason to deprivate cleaver people from the right tool ;) Bye, Mt. -- Each language has its purpose, however humble. Each language expresses the Yin and Yang of Software. Each language has its place within the Tao. But do not program in PHP if you can avoid it. -- The Tao of Programming signature.asc Description: PGP signature
Bug#849249: fldigi: Icon improvements
Hi Jeremy- Thanks for these fldigi patches -- I'm applying 0001 to fix the icons, but not applying 0002 (the debian/rules cleanups), because this packaging is still debian/compat==7 so it really does need the special dpkg-buildflags handling to get build hardening. Moving up to debhelper 9 is surely a good idea, but lets handle that under separate cover -- I'll look at applying your 0002 patch again whenever I or you or someone else gets to that work. Thanks again for the icon fix! -Kamal On Fri, Dec 23, 2016 at 10:15 PM, Jeremy Bichawrote: > Package: fldigi > Version: 3.23.14-1 > Tags: patch > > .xpm app icons are not necessary any more. If a package contains .xpm > icons, it triggers an error in appstream. This means that fldigi does > not show up in the GNOME Software app which is installed by default in > the GNOME desktop in Debian stretch. > > https://appstream.debian.org/sid/main/issues/fldigi.html > https://wiki.debian.org/AppStream/Guidelines#Icon_best_practices > > The .png app icons are installed in the wrong directory. They should > be installed in a two-number directory like 64x64/ instead of a > one-number directory like 64/ > > There's some extra line in debian/rules. The dh_installdocs override > isn't needed since there's only one binary package. > --disable-silent-rules is the default as of debhelper 9.20150501. And > dpkg-buildflags should be passed automatically without you having to > do anything. > > I'm attaching patches for these. > > Thanks, > Jeremy > >
Bug#787404: ntp_intres.request: permission denied
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am Mo den 3. Apr 2017 um 21:59 schrieb Bernhard Schmidt: > ># Required-Start: $network $remote_fs $syslog $named > > > > In my setup, ntp and dns was start at the same runlevel. But as > > "unbounce" comes lexically after "ntp", ntp was start first. With bind, > > that could work as "bind" is lexically earlier in the list. However, > > There is a dependency between ntp and dns so that dependency has to be > > configured correctly. > > I tried to reproduce this with current Jessie and the future Stretch > release. As far as I can tell ntp handles this situation just fine. > > When ntpd starts up and cannot resolve the servers it logs > > ntpd[...]: Deferring DNS for 0.debian.pool.ntp.org 1 > ntpd_initres[...]: host name not found: 0.debian.pool.ntp.org > > as soon as DNS and/or network connectivity is available again (a couple > of minutes later) it logs > > ntpd_initres[...]: DNS 0.debian.pool.ntp.org -> IP > > and starts using this server. Well, my experiences are that ntp is not very graceful when dealing with not existing dns. It should handle that situation but fails to often. On the other hand, that "$named" in the Required-Start solves the problem and does no harm. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus EthgenFingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAljiubAACgkQpnwKsYAZ 9qwUowv/fM7D2GjFlbLNLUkvmLz0iVKuqtkFgEZjkELDJfJzzbD9QWMK6kfk/S01 A1bhQxSPNOkWG/iGQz4zjQf5jdZYChk9xV3z5PJ/l0YOqSu0vOq6t9RDOpzDHIpZ IZU3A47PkQdwFxE88ZQOFDoxPwQcqcH1SFU4TJlk+LXUYtDJ5VNpcHYSetKHIr59 OIPdDbYpsRH1cfOG2+egKe4NfUlBwnb08nswMW9Odn7YReneo/Io37I2SPzUFtxx wWBkkiaeD5yWhpv7+xLXylX2RdSjAi9aZlvtHcOM+he5Ihox+jFKAOuI/AjpGF15 1cRAQJU84+f1Ksrri8B3aaCRgNYf4jMzz4hqySRYQqm+C5YgwPUrSVsaklHvjq7J WdS0O3oNf//cxrENCGe7JAFEXQvDv+b8Yr527VsAa034LLG5QUNdf1Ctoo1BFyvi sZnpXDfOlOW6KHCTAXd+yJR/MIMEbfYBjxyZcm4tdkSrm7il8KQX+nCeW/fE9SFa pGnelNHG =Oy/3 -END PGP SIGNATURE-
Bug#787404: ntp_intres.request: permission denied
Control: tags -1 + moreinfo unreproducible On Mon, Jun 01, 2015 at 09:16:05AM +0100, Klaus Ethgen wrote: > This is a successor of bug #571469. All is said there. NTP needs running > DNS when it starts. Please add $named to Required-Start in init script. > > Funny thing, reportbug does include my changed init.d script below but > not the changed part: ># Required-Start: $network $remote_fs $syslog $named > > In my setup, ntp and dns was start at the same runlevel. But as > "unbounce" comes lexically after "ntp", ntp was start first. With bind, > that could work as "bind" is lexically earlier in the list. However, > There is a dependency between ntp and dns so that dependency has to be > configured correctly. I tried to reproduce this with current Jessie and the future Stretch release. As far as I can tell ntp handles this situation just fine. When ntpd starts up and cannot resolve the servers it logs ntpd[...]: Deferring DNS for 0.debian.pool.ntp.org 1 ntpd_initres[...]: host name not found: 0.debian.pool.ntp.org as soon as DNS and/or network connectivity is available again (a couple of minutes later) it logs ntpd_initres[...]: DNS 0.debian.pool.ntp.org -> IP and starts using this server. Bernhard signature.asc Description: Digital signature
Bug#859437: unblock: util-linux/2.29.2-1
Hi, Niels Thykier(2017-04-03): > > Please consider unblocking package util-linux > > > > It contains many bugfixes cherry-picked from the master branch, not > > very exciting stuff, fixes CVE-2017-2616 but since we don't build su > > from util-linux (yet) it's also *YAWN*. > > > > I've received no (negative) feedback since the upload. > > > > unblock util-linux/2.29.2-1 > > > > Ok with me, CC'ing KiBi for a d-i ack. No objections based on a quick read of the changelog, beware of “PT” (for GPT) in src/context.c and “entreis” (for entries) in src/gpt.c. KiBi. signature.asc Description: Digital signature
Bug#859467: lintian: check if a package contains a functional testsuite using autopkgtest
Package: lintian Version: 2.5.50.1 Severity: wishlist Tags: patch Dear Maintainer, I wish lintian could notify packages maintainers about the absence of a functional testsuite using autopkgtest, just as a reminder. It is important for quality assurance have these kind of tests in all packages, and I talked about it with some others DDs and some of them do not have any idea what I was saying. Nowadays, Debian CI covers almost 20% of the source packages in archive, the idea here is to increase this number. I attached a patch which I am verifying if the 'Testsuite' is in debian/control and if this field contains the string 'autopkgtest'. Now we have just autopkgtest* (with some teams wrappers) available, because of this I am trying to find this specific string. The other 2 patches attached try to fix the broken tests after this modification, the templates used did not have the 'Testsuite' field. I hope you consider the patches. Cheers. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lintian depends on: ii binutils 2.28-2 ii bzip2 1.0.6-8.1 ii diffstat 1.61-1+b1 ii file 1:5.29-3 ii gettext 0.19.8.1-2 ii intltool-debian 0.35.0+20060710.4 ii libapt-pkg-perl 0.1.32 ii libarchive-zip-perl 1.59-1 ii libclass-accessor-perl0.34-1 ii libclone-perl 0.38-2+b1 ii libdpkg-perl 1.18.23 ii libemail-valid-perl 1.202-1 ii libfile-basedir-perl 0.07-1 ii libipc-run-perl 0.94-1 ii liblist-moreutils-perl0.416-1+b1 ii libparse-debianchangelog-perl 1.2.0-12 ii libperl5.24 [libdigest-sha-perl] 5.24.1-2 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3000-2 ii liburi-perl 1.71-1 ii libyaml-libyaml-perl 0.63-2 ii man-db2.7.6.1-2 ii patchutils0.3.4-2 ii perl 5.24.1-2 ii t1utils 1.39-2 ii xz-utils 5.2.2-1.2+b1 Versions of packages lintian recommends: ii dpkg 1.18.23 ii libperlio-gzip-perl 0.19-1+b2 ii perl 5.24.1-2 ii perl-modules-5.24 [libautodie-perl] 5.24.1-2 Versions of packages lintian suggests: pn binutils-multiarch ii dpkg-dev 1.18.23 ii libhtml-parser-perl3.72-3 ii libtext-template-perl 1.46-1 -- no debconf information >From 7571fdf6dccff02733c5b620e8cb85aabb85004f Mon Sep 17 00:00:00 2001 From: Lucas KanashiroDate: Mon, 3 Apr 2017 17:21:03 -0300 Subject: [PATCH 2/3] add functional testsuite in tests templates --- t/runtests | 2 +- t/templates/tests/pedantic/debian/tests/control | 1 + t/templates/tests/pedantic/debian/tests/test| 2 ++ t/templates/tests/skel/debian/tests/control | 1 + t/templates/tests/skel/debian/tests/test| 2 ++ 5 files changed, 7 insertions(+), 1 deletion(-) create mode 100644 t/templates/tests/pedantic/debian/tests/control create mode 100755 t/templates/tests/pedantic/debian/tests/test create mode 100644 t/templates/tests/skel/debian/tests/control create mode 100755 t/templates/tests/skel/debian/tests/test diff --git a/t/runtests b/t/runtests index 020f3f8dc..dd4da7ed2 100755 --- a/t/runtests +++ b/t/runtests @@ -113,7 +113,7 @@ my $RUNNER_TS = (stat($0))[9]; chomp $ARCHITECTURE; our %TEMPLATES = ( -'tests' => ['debian/changelog', 'debian/control', 'debian/compat'], +'tests' => ['debian/changelog', 'debian/control', 'debian/compat', 'debian/tests'], 'debs' => ['changelog', 'control', 'Makefile'], 'source' => ['changelog', 'control', 'dsc.in'], ); diff --git a/t/templates/tests/pedantic/debian/tests/control b/t/templates/tests/pedantic/debian/tests/control new file mode 100644 index 0..b8562954d --- /dev/null +++ b/t/templates/tests/pedantic/debian/tests/control @@ -0,0 +1 @@ +Tests: test diff --git a/t/templates/tests/pedantic/debian/tests/test b/t/templates/tests/pedantic/debian/tests/test new file mode 100755 index 0..039e4d006 --- /dev/null +++ b/t/templates/tests/pedantic/debian/tests/test @@ -0,0 +1,2 @@ +#!/bin/sh +exit 0 diff --git a/t/templates/tests/skel/debian/tests/control b/t/templates/tests/skel/debian/tests/control new file mode 100644 index 0..b8562954d --- /dev/null +++ b/t/templates/tests/skel/debian/tests/control @@ -0,0 +1 @@
Bug#859466: unblock: mapnik/3.0.12+ds-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mapnik It fixes #859424 by enabling the PIE hardening buildflags. unblock mapnik/3.0.12+ds-3 Kind Regards, Bas diff -Nru mapnik-3.0.12+ds/debian/changelog mapnik-3.0.12+ds/debian/changelog --- mapnik-3.0.12+ds/debian/changelog 2016-11-05 14:15:44.0 +0100 +++ mapnik-3.0.12+ds/debian/changelog 2017-04-03 14:47:38.0 +0200 @@ -1,3 +1,11 @@ +mapnik (3.0.12+ds-3) unstable; urgency=medium + + * Update branch in gbp.conf & Vcs-Git URL. + * Enable PIE hardening buildflags. +(closes: #859424) + + -- Bas CouwenbergMon, 03 Apr 2017 14:47:38 +0200 + mapnik (3.0.12+ds-2) unstable; urgency=medium * Add patch to fix 'dependencies' typo. diff -Nru mapnik-3.0.12+ds/debian/control mapnik-3.0.12+ds/debian/control --- mapnik-3.0.12+ds/debian/control 2016-10-30 12:18:51.0 +0100 +++ mapnik-3.0.12+ds/debian/control 2017-04-03 14:45:40.0 +0200 @@ -33,7 +33,7 @@ zlib1g-dev Standards-Version: 3.9.8 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-grass/mapnik.git -Vcs-Git: https://anonscm.debian.org/git/pkg-grass/mapnik.git +Vcs-Git: https://anonscm.debian.org/git/pkg-grass/mapnik.git -b stretch Homepage: http://www.mapnik.org/ Package: libmapnik3.0 diff -Nru mapnik-3.0.12+ds/debian/gbp.conf mapnik-3.0.12+ds/debian/gbp.conf --- mapnik-3.0.12+ds/debian/gbp.conf2016-10-15 20:08:15.0 +0200 +++ mapnik-3.0.12+ds/debian/gbp.conf2017-04-03 14:45:48.0 +0200 @@ -6,7 +6,7 @@ # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). -debian-branch = master +debian-branch = stretch # git-import-orig uses the following names for the upstream tags. # Change the value if you are not using git-import-orig diff -Nru mapnik-3.0.12+ds/debian/rules mapnik-3.0.12+ds/debian/rules --- mapnik-3.0.12+ds/debian/rules 2016-11-05 14:13:46.0 +0100 +++ mapnik-3.0.12+ds/debian/rules 2017-04-03 14:46:26.0 +0200 @@ -4,9 +4,8 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 -# Enable hardening build flags, except: -# pie: causes python-mapnik build failure -export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie +# Enable hardening build flags +export DEB_BUILD_MAINT_OPTIONS=hardening=+all NJOBS := -j1 ifneq (,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS
Bug#859464: unblock: libhdf4/4.2.12-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libhdf4 It fixes #859413 by enabling the PIE hardening buildflags. unblock libhdf4/4.2.12-2 Kind Regards, Bas diff -Nru libhdf4-4.2.12/debian/changelog libhdf4-4.2.12/debian/changelog --- libhdf4-4.2.12/debian/changelog 2016-07-06 17:35:44.0 +0200 +++ libhdf4-4.2.12/debian/changelog 2017-04-03 14:28:06.0 +0200 @@ -1,3 +1,12 @@ +libhdf4 (4.2.12-2) unstable; urgency=medium + + * Team upload. + * Enable PIE hardening flags. +(closes: #859413) + * Drop unused lintian overrides for hardening-no-pie. + + -- Bas CouwenbergMon, 03 Apr 2017 14:28:06 +0200 + libhdf4 (4.2.12-1) unstable; urgency=medium * Team upload. diff -Nru libhdf4-4.2.12/debian/hdf4-tools.lintian-overrides libhdf4-4.2.12/debian/hdf4-tools.lintian-overrides --- libhdf4-4.2.12/debian/hdf4-tools.lintian-overrides 2016-05-20 18:11:05.0 +0200 +++ libhdf4-4.2.12/debian/hdf4-tools.lintian-overrides 1970-01-01 01:00:00.0 +0100 @@ -1,3 +0,0 @@ -# PIE breaks the build -hdf4-tools: hardening-no-pie * - diff -Nru libhdf4-4.2.12/debian/rules libhdf4-4.2.12/debian/rules --- libhdf4-4.2.12/debian/rules 2016-06-30 23:28:39.0 +0200 +++ libhdf4-4.2.12/debian/rules 2017-04-03 14:26:02.0 +0200 @@ -6,7 +6,7 @@ # # Enable hardening build flags -export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie +export DEB_BUILD_MAINT_OPTIONS=hardening=+all DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) @@ -24,9 +24,9 @@ CXX := g++ LIBS := -ljpeg -lz -lm -CFLAGS = $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie dpkg-buildflags --get CFLAGS) -CFLAGS += $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie dpkg-buildflags --get CPPFLAGS) -LDFLAGS = $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie dpkg-buildflags --get LDFLAGS) +CFLAGS = $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags --get CFLAGS) +CFLAGS += $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags --get CPPFLAGS) +LDFLAGS = $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags --get LDFLAGS) ifneq (,$(findstring verbose,$(DEB_BUILD_OPTIONS))) DH_VERBOSE=1
Bug#859409: kicad: Inconsistent footprint naming
Hello, On Mon, Apr 03, 2017 at 11:41:55AM +0100, markMLl wrote: > Apologies if I'm doing something obviously wrong, but this is the first time > I've > picked up Kicad for years and in the past it's "just worked". > > Progressing from eeschema via a netlist file to pcbnew, I get > > Error loading netlist. > IO_ERROR: Footprint library path '/usr/share/kicad/modules/ > Buttons_Switches_THT.pretty' does not exist > from /build/kicad-OLDpkC/kicad-4.0.5+dfsg1/pcbnew/ > kicad_plugin.cpp : Load(): line 283 > > The problem would appear to be that there are directories named like > > Buttons_Switches_ThroughHole.pretty > Capacitors_ThroughHole.pretty > > and so on, while the files femplate/fp-lib-table.for-pretty and > template/fp-lib-table.for-github have > > (lib (name Buttons_Switches_THT)(type KiCad)(uri > ${KISYSMOD}/Buttons_Switches_THT.pretty)(options "")(descr "Buttons and > switches, through hole")) > > and so on. unfortunately upstream has renamed some footprint libraries and also moved some footprint entries into other libaries that we wasn't aware while packaging 4.0.5. I prepared 4.0.6 some days ago which should solve this issue by symlinking the old libraries to the new ones. But the new package version needs to go through NEW as it contains a new binary package. You can change your local table ~/.config/kicad/fp-lib-table and add the correct names there or, if you haven't modified the table much, delete the file. KiCad will copy the default file with the new library names if you restart KiCad. In the end I wouldn't wait for a version 4.0.6 in the Stretch release. If the upload to NEW is going well we need to ask the release team if they would allow a upload to unstable and a unblock for migration to testing. After the release we could then make a upload to backports every time. Regards Carsten
Bug#859465: unblock: ogdi-dfsg/3.2.0+ds-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ogdi-dfsg It fixes #859433 by enabling the PIE hardening buildflags. unblock ogdi-dfsg/3.2.0+ds-2 Kind Regards, Bas diff -Nru ogdi-dfsg-3.2.0+ds/debian/changelog ogdi-dfsg-3.2.0+ds/debian/changelog --- ogdi-dfsg-3.2.0+ds/debian/changelog 2016-07-19 15:58:59.0 +0200 +++ ogdi-dfsg-3.2.0+ds/debian/changelog 2017-04-03 15:36:52.0 +0200 @@ -1,3 +1,12 @@ +ogdi-dfsg (3.2.0+ds-2) unstable; urgency=medium + + * Team upload. + * Enable PIE hardening buildflags. +(closes: #859433) + * Drop unused lintian overrides for hardening-no-pie. + + -- Bas CouwenbergMon, 03 Apr 2017 15:36:52 +0200 + ogdi-dfsg (3.2.0+ds-1) unstable; urgency=medium * Team upload. diff -Nru ogdi-dfsg-3.2.0+ds/debian/ogdi-bin.lintian-overrides ogdi-dfsg-3.2.0+ds/debian/ogdi-bin.lintian-overrides --- ogdi-dfsg-3.2.0+ds/debian/ogdi-bin.lintian-overrides2016-07-19 15:19:14.0 +0200 +++ ogdi-dfsg-3.2.0+ds/debian/ogdi-bin.lintian-overrides1970-01-01 01:00:00.0 +0100 @@ -1,3 +0,0 @@ -# PIE breaks the build -ogdi-bin: hardening-no-pie * - diff -Nru ogdi-dfsg-3.2.0+ds/debian/rules ogdi-dfsg-3.2.0+ds/debian/rules --- ogdi-dfsg-3.2.0+ds/debian/rules 2016-07-19 15:48:19.0 +0200 +++ ogdi-dfsg-3.2.0+ds/debian/rules 2017-04-03 15:36:52.0 +0200 @@ -5,7 +5,7 @@ #export DH_VERBOSE=1 # Enable hardening build flags -export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie +export DEB_BUILD_MAINT_OPTIONS=hardening=+all export TOPDIR=$(CURDIR) export CFG=debug
Bug#819738: apt plugin contains hard-coded package name
Control: severity -1 important Control: tag -1 + confirmed Hi Jon, sorry for the late reply, but I somehow oversaw your bug report and only discovered it now by accident. Jon Barber wrote: > Package: hobbit-plugins > Version: 20160122 It's still in there. > When checking packages with foreign architectures, the apt plugin > always tests against libgtkglext1 rather than the intended package. > > Line 74: > my $arch_unspecified = `dpkg --get-selections > libgtkglext1:$native_arch 2>/dev/null`; Argh! My fault: https://anonscm.debian.org/cgit/collab-maint/hobbit-plugins.git/commit/?id=aa766f83da831a39e76a87cb23d09048cc49d227 > --- orig-hobbit-plugins-20160122/src/usr/lib/xymon/client/ext/apt > 2015-11-10 14:35:20.0 + > +++ hobbit-plugins-20160122/src/usr/lib/xymon/client/ext/apt 2016-04-01 > 15:53:05.626870891 +0100 > @@ -74,7 +74,7 @@ > if (/^(\S+)\s+(\S+)/) { # pkg install/hold/... > next unless $2 eq "install" or $2 eq "hold"; > $packages{"$1:$foreign_arch"} = $2; > -my $arch_unspecified = `dpkg --get-selections > libgtkglext1:$native_arch 2>/dev/null`; > +my $arch_unspecified = `dpkg --get-selections $1:$native_arch > 2>/dev/null`; > unless ($arch_unspecified =~ /\sinstall$/) { > delete $packages{$1}; > } Looks sane on a first glance, thanks. Will have to check en detail though before requesting a freeze exception. Anyways, thanks for the report and the patch! Regards, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#859462: telepathy-qt FTBFS on ppc64el: undefined reference to QTest::qCompare
Source: telepathy-qt Version: 0.9.6.1-6 Severity: serious telepathy-qt FTBFS on ppc64el (originally reported by Frederic Bonnard): ... [ 93%] Linking CXX executable test-contacts-capabilities cd /home/bunk/build/telepathy-qt-0.9.6.1/build-qt5/tests/dbus && /usr/bin/cmake -E cmake_link_script CMakeFiles/test-contacts-capabilities.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -fdebug-prefix-map=/home/bunk/build/telepathy-qt-0.9.6.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wsign-compare -Wpointer-arith -Wformat-security -Winit-self -Wnon-virtual-dtor -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-local-typedefs -fPIC -O2 -ggdb -Wl,-z,relro -Wl,--no-add-needed CMakeFiles/test-contacts-capabilities.dir/contacts-capabilities.cpp.o -o test-contacts-capabilities -Wl,-rpath,/home/bunk/build/telepathy-qt-0.9.6.1/build-qt5/tests/lib/glib:/home/bunk/build/telepathy-qt-0.9.6.1/build-qt5/TelepathyQt -rdynamic /usr/lib/powerpc64le-linux-gnu/libQt5Test.so.5.7.1 ../lib/libtp-qt-tests.a ../lib/glib/libtp-glib-tests.so ../lib/glib-helpers/libtp-qt-tests-glib-helpers.a -lgio-2.0 -ldbus-1 ../lib/glib/call/libexample-cm-call.a ../lib/glib/callable/libexample-cm-callable.a ../lib/glib/contactlist/libexample-cm-contactlist.a ../lib/glib/echo/libexample-cm-echo.a ../li b/glib/echo2/libexample-cm-echo2.a ../lib/glib/future/extensions/libtp-glib-tests-future-extensions.a ../../TelepathyQt/libtelepathy-qt5.so.0.0.9.6.1 /usr/lib/powerpc64le-linux-gnu/libQt5DBus.so.5.7.1 /usr/lib/powerpc64le-linux-gnu/libQt5Network.so.5.7.1 /usr/lib/powerpc64le-linux-gnu/libQt5Xml.so.5.7.1 /usr/lib/powerpc64le-linux-gnu/libQt5Core.so.5.7.1 -ltelepathy-glib -lglib-2.0 -lgobject-2.0 -lglib-2.0 -ldbus-glib-1 CMakeFiles/test-contacts-capabilities.dir/contacts-capabilities.cpp.o: In function `TestContactsCapabilities::testCapabilities()': ./build-qt5/tests/dbus/./tests/dbus/contacts-capabilities.cpp:138: undefined reference to `bool QTest::qCompare(bool const&, int const&, char const*, char const*, char const*, int)' collect2: error: ld returned 1 exit status tests/dbus/CMakeFiles/test-contacts-capabilities.dir/build.make:121: recipe for target 'tests/dbus/test-contacts-capabilities' failed make[4]: *** [tests/dbus/test-contacts-capabilities] Error 1 Complete log is attached. LOG.telepathy-qt.gz Description: application/gzip
Bug#856474: [PATCH] Kbuild.include: addtree: Remove quotes before matching path
On Mon, Apr 03, 2017 at 03:25:10PM +0200, Michal Marek wrote: > On 2017-04-03 09:42, Masahiro Yamada wrote: > > Each Makefile knows it wants to see > > additional headers in the source tree, or objtree. > > > > I am guessing the right approach in a long run is, > > we require -I to specify $(srctree) or $(objtree) explicitly. > > > > ccflags-y := -I$(srctree)/foo/bar/baz > > > > or > > > > ccflags-y := -I$(objtree)/foo/bar/baz > > > > > > (For the latter, we can omit $(objtree)/ as it is ./) > > > > > > Then, delete $(call flags,_c_flags) after the conversion. > > Agreed. The addtree function is more of a hack to make things just work > with O=, but AFAIK there is no clean way to implement VPATH for -I > arguments. So it's sensible to get rid of the hack. It looks like it's > going to be lot of work though: > > $ git grep -e '-I' -- '*Makefile*' | wc -l > 732 > $ git grep -e '-I *\$(\(src\|obj\)tree)' -- '*Makefile*' | wc -l > 166 There was a goal long time ago that moving the kernel source should not trigger a rebuild. Any hardcoded path would violate this (like $(srctree), $(objtree)) I dunno if this is really something to aim for today. I have personally from time to time renamed the directory where I have kernel soruce (which is seen like moving the kernel source), and would not be happy if this always triggered a full rebuild. But this is frankly a corner case. Sam
Bug#858553: Re Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files
Hi, I finally found the file that is causing the issue. When I run the attached command (debug.sh) in the lazarus tree in the docs/html/lcl directory, with the attached inputfile.txt file, I get the same error as during the build. When I remove the line containing "../../../lcl/extctrls.pp -Fi../../../lcl/include" the build command is successful. Does anybody see what is wrong with that file? Paul By the way, the fpdoc command return exit code 0 on failure ../../../lcl/alllclunits.pp -Fi../../../lcl/include ../../../lcl/arrow.pp -Fi../../../lcl/include ../../../lcl/asyncprocess.pp -Fi../../../lcl/include ../../../lcl/buttonpanel.pas -Fi../../../lcl/include ../../../lcl/buttons.pp -Fi../../../lcl/include ../../../lcl/calendar.pp -Fi../../../lcl/include ../../../lcl/checklst.pas -Fi../../../lcl/include ../../../lcl/clipbrd.pp -Fi../../../lcl/include ../../../lcl/colorbox.pas -Fi../../../lcl/include ../../../lcl/comboex.pas -Fi../../../lcl/include ../../../lcl/comctrls.pp -Fi../../../lcl/include ../../../lcl/controls.pp -Fi../../../lcl/include ../../../lcl/customdrawncontrols.pas -Fi../../../lcl/include ../../../lcl/customdrawndrawers.pas -Fi../../../lcl/include ../../../lcl/customdrawn_android.pas -Fi../../../lcl/include ../../../lcl/customdrawn_common.pas -Fi../../../lcl/include ../../../lcl/customdrawn_winxp.pas -Fi../../../lcl/include ../../../lcl/customtimer.pas -Fi../../../lcl/include ../../../lcl/dbactns.pp -Fi../../../lcl/include ../../../lcl/dbctrls.pp -Fi../../../lcl/include ../../../lcl/dbextctrls.pp -Fi../../../lcl/include ../../../lcl/dbgrids.pas -Fi../../../lcl/include ../../../lcl/defaulttranslator.pas -Fi../../../lcl/include ../../../lcl/dialogs.pp -Fi../../../lcl/include ../../../lcl/dynamicarray.pas -Fi../../../lcl/include ../../../lcl/dynhasharray.pp -Fi../../../lcl/include ../../../lcl/dynqueue.pas -Fi../../../lcl/include ../../../lcl/editbtn.pas -Fi../../../lcl/include ../../../lcl/extctrls.pp -Fi../../../lcl/include ../../../lcl/extdlgs.pas -Fi../../../lcl/include ../../../lcl/extendedstrings.pas -Fi../../../lcl/include ../../../lcl/extgraphics.pas -Fi../../../lcl/include ../../../lcl/filectrl.pp -Fi../../../lcl/include ../../../lcl/forms.pp -Fi../../../lcl/include ../../../lcl/graphics.pp -Fi../../../lcl/include ../../../lcl/graphmath.pp -Fi../../../lcl/include ../../../lcl/graphtype.pp -Fi../../../lcl/include ../../../lcl/graphutil.pp -Fi../../../lcl/include ../../../lcl/grids.pas -Fi../../../lcl/include ../../../lcl/helpintfs.pas -Fi../../../lcl/include ../../../lcl/icnstypes.pas -Fi../../../lcl/include ../../../lcl/imagelistcache.pas -Fi../../../lcl/include ../../../lcl/imglist.pp -Fi../../../lcl/include ../../../lcl/industrialbase.pp -Fi../../../lcl/include ../../../lcl/inipropstorage.pas -Fi../../../lcl/include ../../../lcl/interfacebase.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkdef.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkfontcache.pas -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkglobals.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkint.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkmsgqueue.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkproc.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwinapiwindow.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwsbuttons.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwscalendar.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwschecklst.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwscomctrls.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwscontrols.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwsdialogs.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwsextctrls.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwsextdlgs.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwsforms.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwsgrids.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwsimglist.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwsmenus.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwspairsplitter.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwsspin.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/gtkwsstdctrls.pp -Fi../../../lcl/include ../../../lcl/interfaces/gtk/interfaces.pp -Fi../../../lcl/include ../../../lcl/interfaces/win32/win32int.pp -Fi../../../lcl/include ../../../lcl/intfgraphics.pas -Fi../../../lcl/include ../../../lcl/lazcanvas.pas -Fi../../../lcl/include ../../../lcl/lazdeviceapis.pas -Fi../../../lcl/include ../../../lcl/lazdialogs.pas -Fi../../../lcl/include ../../../lcl/lazfreetypeintfdrawer.pas -Fi../../../lcl/include ../../../lcl/lazhelphtml.pas -Fi../../../lcl/include ../../../lcl/lazhelpintf.pas -Fi../../../lcl/include ../../../lcl/lazlinkedlist.pas -Fi../../../lcl/include ../../../lcl/lazregions.pas -Fi../../../lcl/include ../../../lcl/lclclasses.pp -Fi../../../lcl/include
Bug#859461: xterm: seperate package for resize would be nice
Package: xterm Version: 312-2 Severity: wishlist Dear Maintainer, For those of us using a machine without a video card a serial console is quite useful, and in many cases that serial console is controled by xterm or similar terminal emulator (in my case it is almost always xterm and screen), due to the continued decrease in availability of hardware serial terminals (not much of a loss there). now one of the cool new features of using a modern terminal emulator with rs232 (in adition to utf8, 256 color, sixel graphics (sorry), etc.) is resizable terminal windows. This is not very dificult as long as you execute xterm's resize on the remote machine after each resize. (see: http://unix.stackexchange.com/questions/16578/resizable-serial-console-window) The one chalenge is in the case of machines that are not running any graphics software and do not need or want xterm installed, but do want xterm's resize. Which brings me to my request, split resize into a seprate package and depend on it to preserve existing functionality while allowing headless machines to install just resize.
Bug#859460: RM: glotski -- RoQA/RoM; superseded by gnome-klotski
Package: ftp.debian.org X-Debbugs-Cc: glot...@packages.debian.org Please remove glotski from the archive. It is an old GNOME2 app that is no longer developed. Users would be better off using gnome-klotski which is actively maintained in GNOME. I got approval from Hwei Sweng Teoh, the Debian maintainer for glotski, before filing this bug. Thanks, Jeremy Bicha
Bug#859435: linux-image-4.9.0-2-amd64: Total freeze of the PC at lightdm connexion screen
guy@debian:~$ apt list firmware-amd-graphics -a En train de lister... Fait firmware-amd-graphics/testing,testing,now 20161130-2 all [installé]
Bug#843513: Build DICOM
On Mon, Nov 07, 2016 at 11:02:05AM +0100, Mathieu Malaterre wrote: > Package: src:opencv > Version: 2.4.9.1+dfsg-2.1 > Severity: wishlist > > It would be nice to also build DICOM support: > > -DWITH_GDCM=ON \ This is not enough… DICOM support is only available since 3.2, which is not yet packaged. -- 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#854854: qcontrol: reboot/poweroff
Hi, On 16/03/2017 at 09:45:07 +0100, Uwe Kleine-König wrote: > Back then I prepared a backport to jessie (which still sits in a topic > branch in the debian-kernel repo[2]) but it seems I forgot to merge it into > the jessie kernel. > > I wonder if the better fix would be to fix this in linux-stable instead. > What do you think? > I agree that this should be backported to any stable kernel that is used by a distribution. I can ack the patch if you send one to stable@ -- Alexandre Belloni, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Bug#847282: Ping
On Mon, Apr 3, 2017 at 8:36 PM, Adrian Bunkwrote: > Control: severity -1 serious > > On Sun, Mar 12, 2017 at 03:51:29PM +0100, Bastien ROUCARIES wrote: >> n 2017-01-22 18:02, Bastien ROUCARIES wrote: >> > Let decrease the severity to something not RC. I need to know if the >> > problem is in dpkg or imagemagick. And I do not want to block the >> > security update of imagemagick. > > Raising severity again, so that this issue won't get lost for stretch. > >> ACK. I'll try to take a more detailed look at it ... ping me if I don't >> report back ... >> >> Ping thus > > Adding Andreas, replying to the bug does not Cc the submitter. For this one adrian I need help... I do not know where the problem lie. In dpkg maint script or in imagemagick Trace welcome > > cu > Adrian > > -- > >"Is there not promise of rain?" Ling Tan asked suddenly out > of the darkness. There had been need of rain for many days. >"Only a promise," Lao Er said. >Pearl S. Buck - Dragon Seed >
Bug#859458: console-setup: Setup font on initrd
Package: console-setup-linux Version: 1.163 Severity: wishlist Hi, I have a display with a high resolution (280 dpi) and use full disk encryption. For the frame buffer console, I've changed the font to CODESET="Lat15" FONTFACE="Terminus" FONTSIZE="16x32" But the prompt for the master password before the system starts (and after grub) is still the default and very small. To fix this, I've added these scripts to initramfs-tools: - /etc/initramfs-tools/hooks/setup-console - #!/bin/sh case $1 in prereqs) echo '' exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions # Begin real processing below this line copy_exec /bin/setfont cp /etc/console-setup/cached_Lat15-Terminus32x16.psf.gz "$DESTDIR"/etc/console-font.psf.gz - cat /etc/initramfs-tools/scripts/init-top/setup-console - #!/bin/sh case $1 in prereqs) echo "udev" exit 0 ;; esac . /scripts/functions # Begin real processing below this line if test -x /bin/setfont && test -e /etc/console-font.psf.gz then setfont /etc/console-font.psf.gz log_success_msg 'Set console font' fi - Can you add files like these to the package, please? Regards Jörg -- System Information: Debian Release: 9.0 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.10.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages console-setup-linux depends on: ii init-system-helpers 1.47 ii initscripts 2.88dsf-59.9 ii kbd 2.0.3-2+b1 ii keyboard-configuration 1.163 console-setup-linux recommends no packages. Versions of packages console-setup-linux suggests: ii console-setup 1.163 Versions of packages keyboard-configuration depends on: ii debconf 1.5.60 ii liblocale-gettext-perl 1.07-3+b1 Versions of packages console-setup depends on: ii debconf 1.5.60 ii keyboard-configuration 1.163 ii xkb-data2.19-1 Versions of packages console-setup suggests: ii locales 2.24-9 ii lsb-base 9.20161125 Versions of packages console-setup-linux is related to: ii console-common0.7.89 ii console-data 2:1.12-5 pn console-tools pn gnome-control-center ii kbd 2.0.3-2+b1 ii systemd 232-22 -- debconf information excluded signature.asc Description: PGP signature
Bug#859457: antlr4's grun tool misses to add . in the classpath
Package: antlr4 Version: 4.5.3-1 Severity: important Tags: newcomer Dear Maintainer, I've just installed antlr4 on Debian Strech in order to learn this tool. I carefully read the getting started instructions [1], which list the tool grun for first testing purposes. However, this tool does not work as expected. It just says "Can't load Hello as lexer or parser". This is a known issue (see [2]) and can be fixed by adding . (dot) to the classpath. Here is what grun (/usr/share/antlr4/grun) looks like on Debian: CLASSPATH=/usr/share/java/antlr4.jar:/usr/share/java/antlr4-runtime.jar exec java -cp $CLASSPATH org.antlr.v4.gui.TestRig "$@" Here is what grun looks like on MacOS (installed with brew): java -classpath /usr/local/Cellar/antlr/4.6/antlr-4.6-complete.jar:. org.antlr.v4.gui.TestRig "$@" Please update the grun script to include "." in the classpath. Thanks and BR Christoph [1] https://github.com/antlr/antlr4/blob/master/doc/getting-started.md [2] https://github.com/antlr/antlr4/blob/master/doc/faq/installation.md -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages antlr4 depends on: ii libantlr3-runtime-java 3.5.2-6 ii libantlr4-runtime-java 4.5.3-1 ii libstringtemplate4-java 4.0.8-2 ii libtreelayout-java 1.0.3-1 ii openjdk-8-jre-headless [java6-runtime-headless] 8u121-b13-4 antlr4 recommends no packages. antlr4 suggests no packages. -- no debconf information
Bug#859456: libarchive: CVE-2016-10209
Source: libarchive Version: 3.1.2-11 Severity: important Tags: upstream security Forwarded: https://github.com/libarchive/libarchive/issues/842 Hi, the following vulnerability was published for libarchive. CVE-2016-10209[0]: | The archive_wstring_append_from_mbs function in archive_string.c in | libarchive 3.2.2 allows remote attackers to cause a denial of service | (NULL pointer dereference and application crash) via a crafted archive | file. It was reported upstream at [1] and if I'm correct the fix should be [2]. Can you confirm that? If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2016-10209 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10209 [1] https://github.com/libarchive/libarchive/issues/842 [2] https://github.com/libarchive/libarchive/commit/42a3408ac7df1e69bea9ea12b72e14f59f7400c0 Please adjust the affected versions in the BTS as needed. Regarding an update, I do not think this would warrant a DSA on it's own but would be great once fixed for sid and stretch, if a fix can as well land in jessie (via a point release as well for the other issues marked currently no-dsa). Regards, Salvatore -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#858731: Doesn't this fix loose the bug?
On Mon, 2017-04-03 at 11:44 -0400, Lennart Sorensen wrote: > I was under the impression stretch would release with 4.9 kernel. Correct. > So fixing it in 4.10 and marking it done seems like it might loose the > bug report without ever getting it actually included in stretch. > > Will the config change in the 4.10 experimental automatically be included > in any updates to the 4.9 kernel going in unstable/testing? > > Just wondering. I still have this flagged for attention in my mailbox and will probably make the same change in the next upload to unstable. Ben. -- Ben Hutchings Tomorrow will be cancelled due to lack of interest. signature.asc Description: This is a digitally signed message part
Bug#760385: Unfixed old CVEs should really be RC
On Mon, Apr 03, 2017 at 09:13:56PM +0300, Adrian Bunk wrote: > On Mon, Apr 03, 2017 at 08:03:16PM +0200, Moritz Muehlenhoff wrote: > > On Tue, Feb 28, 2017 at 02:28:28PM +0200, Adrian Bunk wrote: > > > Control: severity -1 serious > > > > > > Dozens of unfixed CVEs, the oldest unfixed CVEs will be more than > > > 4 years old when stretch gets released. > > > > > > In the current state the package is really too buggy for shipping > > > in a new stable release. > > > > Note that nodejs will not be covered by security support in stretch (as it > > was > > done for jessie already). We had initially considered it, but with > > nodejs 6 not having it made into stretch, that's not realistic. > > > > So these can be downgraded to non-RC (or if the release team thinks > > nodejs should rather be remove from testing, removal is also an option > > of course). > > This is not even the normal Node.js, this is a version of V8 from an > upstream branch that is dead for 4 years already. Right. Initially there was some plan to provide a supported libv8 from src:nodejs, though. libv8 has never been covered by security support in any Debian release so far, upstream does no real security support apart from what lands in Chrome. Cheers, Moritz
Bug#859455: libarchive sometimes FTBFS on arm64/armhf: test_option_newer_than (4 failures)
Source: libarchive Version: 3.2.1-2 Severity: serious It doesn't always fail, and I do not know whether there is a reason or just luck that it doesn't seem to whow up on other architectures. https://buildd.debian.org/status/logs.php?pkg=libarchive=arm64 https://buildd.debian.org/status/logs.php?pkg=libarchive=armhf ... make check-TESTS make[4]: Entering directory '/«PKGBUILDDIR»' make[5]: Entering directory '/«PKGBUILDDIR»' PASS: bsdcat_test PASS: bsdcpio_test FAIL: bsdtar_test PASS: libarchive_test libarchive 3.2.2: ./test-suite.log # TOTAL: 4 # PASS: 3 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: bsdtar_test = If tests fail or crash, details will be in: /tmp/bsdtar_test.2017-04-03T15.56.16-000 Reference files will be read from: /«PKGBUILDDIR»/tar/test Running tests on: "/«PKGBUILDDIR»/bsdtar" Exercising: bsdtar 3.2.2 - libarchive 3.2.2 zlib/1.2.8 liblzma/5.2.2 bz2lib/1.0.6 liblz4/1.7.1 0: test_0 1: test_basic 2: test_copy 3: test_empty_mtree 4: test_extract_tar_Z 5: test_extract_tar_bz2 6: test_extract_tar_grz tar/test/test_extract_tar_grz.c:46: SKIPPING: It seems grzip is not supported on this platform 7: test_extract_tar_gz 8: test_extract_tar_lrz tar/test/test_extract_tar_lrz.c:46: SKIPPING: It seems lrzip is not supported on this platform 9: test_extract_tar_lz 10: test_extract_tar_lz4 11: test_extract_tar_lzma 12: test_extract_tar_lzo 13: test_extract_tar_xz 14: test_format_newc 15: test_help 16: test_leading_slash 17: test_missing_file 18: test_option_C_upper 19: test_option_H_upper 20: test_option_L_upper 21: test_option_O_upper 22: test_option_T_upper 23: test_option_U_upper 24: test_option_X_upper 25: test_option_a 26: test_option_b 27: test_option_b64encode 28: test_option_exclude 29: test_option_gid_gname 30: test_option_grzip tar/test/test_option_grzip.c:35: SKIPPING: grzip is not supported on this platform 31: test_option_j 32: test_option_k 33: test_option_keep_newer_files 34: test_option_lrzip tar/test/test_option_lrzip.c:35: SKIPPING: lrzip is not supported on this platform 35: test_option_lz4 36: test_option_lzma 37: test_option_lzop 38: test_option_n 39: test_option_newer_than tar/test/test_option_newer_than.c:62: File should exist: new.txt tar/test/test_option_newer_than.c:63: File should exist: a/b/new.txt tar/test/test_option_newer_than.c:72: File should exist: new.txt tar/test/test_option_newer_than.c:73: File should exist: a/b/new.txt 40: test_option_nodump tar/test/test_option_nodump.c:32: SKIPPING: Can't test nodump on this filesystem 41: test_option_older_than 42: test_option_passphrase 43: test_option_q 44: test_option_r 45: test_option_s 46: test_option_uid_uname 47: test_option_uuencode 48: test_option_xz 49: test_option_z 50: test_patterns 51: test_print_longpath 52: test_stdio 53: test_strip_components 54: test_symlink_dir 55: test_version 56: test_windows tar/test/test_windows.c:322: SKIPPING: Windows specific test Totals: Tests run: 57 Tests failed: 1 Assertions checked: 83406 Assertions failed:4 Skips reported: 6 Failing tests: 39: test_option_newer_than (4 failures) Details for failing tests: /tmp/bsdtar_test.2017-04-03T15.56.16-000 FAIL bsdtar_test (exit status: 1) Testsuite summary for libarchive 3.2.2 # TOTAL: 4 # PASS: 3 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to libarchive-disc...@googlegroups.com Makefile:13017: recipe for target 'test-suite.log' failed make[5]: *** [test-suite.log] Error 1
Bug#859435: linux-image-4.9.0-2-amd64: Total freeze of the PC at lightdm connexion screen
Control: tag -1 moreinfo On Mon, 2017-04-03 at 15:36 +0200, GT wrote: > Package: linux-image-4.9.0-2-amd64 > Version: linux-image-4.9.0-2-amd64 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > Use of linux-image-4.9.0-2-amd64 , other things equal on the PC except linux- > image-3.16.0-4-amd64 > * What exactly did you do (or not do) that was effective (or > ineffective)? > just boot on kernel linux-image-4.9.0-2-amd6 > * What was the outcome of this action? > Total freeze of the PC. keyboard and mouse unusable. Need to power off/ power > on the PC and use the kernel linux-image-3.16.0-4-amd64 > * What outcome did you expect instead? > To be able to give the password of user in lightdm screen > *** End of the template - remove these template lines *** Which version of firmware-amd-graphics is installed? Ben. -- Ben Hutchings Tomorrow will be cancelled due to lack of interest. signature.asc Description: This is a digitally signed message part
Bug#836127: Call for Votes for new CTTE Member
Philip Handswrites: > ===BEGIN > > The Technical Committee recommends that David Bremner be > appointed by the Debian Project Leader to the Technical Committee. > > A: Recommend to Appoint David Bremner > B: Further Discussion > > ===END I vote A > B -- -keith signature.asc Description: PGP signature
Bug#855094: [pkg-cryptsetup-devel] Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't
Hi intigeri, hi Guilhem, Am 02.04.2017 um 10:10 schrieb Guilhem Moulin: > On Sun, 02 Apr 2017 at 09:50:55 +0200, intrigeri wrote: >> So at this point, I suggest this bug is reassigned to cryptsetup, and >> option 3 is implemented there. But downgrading to non-RC and leaving >> things as-is seems acceptable to me as well. >> >> Thoughts? > > I think the proper fix would be to split cryptsetup's initramfs bits to > a separate package (depending on busybox), cf. #783297. It's > unfortunate that we didn't implement that in time for Stretch, but > considering the impact of this, I'd favor downgrading the severity and > merging the bugs for the time being. I fully agree with Guilhem here. We should split out cryptsetup-initramfs as soon as Stretch is released and make it depend on initramfs-tools and busybox. Cheers, jonas signature.asc Description: OpenPGP digital signature
Bug#859454: puppet: package upgrade fails due to preinst not stopping puppet daemon
Package: puppet Version: 4.8.2-3~bpo8+1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** It appears that there is no check for a running puppet daemon in the preinst phase of the package installation. The preinst phase should check whether the puppet daemon is running and stop it, but apparently it doesn't do that, so the upgrade fails at the end when it attempts to start the puppet daemon since the old daemon is still running. If I manually stop the daemon before upgrade, the upgrade proceeds without error, and the puppet agent is started at the end of the process. Note that I am using sysvinit (rather than systemd). Here are the errors from apt-get (following the running puppet agent's own attempt to install the packages; hence the "not fully installed" state): # apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up puppet (4.8.2-3~bpo8+1) ... [FAIL] Starting puppet agent failed! invoke-rc.d: initscript puppet, action "start" failed. dpkg: error processing package puppet (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of puppet-common: puppet-common depends on puppet; however: Package puppet is not configured yet. dpkg: error processing package puppet-common (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: puppet puppet-common -- System Information: Debian Release: 8.7 Architecture: amd64 (x86_64) Kernel: Linux 4.1.35-vs2.3.8.5.2-beng (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages puppet depends on: ii adduser 3.113+nmu3 ii facter 2.4.6-1~bpo8+1 ii hiera 1.3.4-1 ii init-system-helpers 1.22 ii lsb-base4.1+Debian13+nmu1 ii ruby1:2.1.5+deb8u2 ii ruby-augeas 0.5.0-2+b2 ii ruby-deep-merge 1.1.1-1~bpo8+1 ii ruby-rgen 0.7.0-1 ii ruby-safe-yaml 1.0.3-1 ii ruby-shadow 2.3.4-2 ii ruby2.1 [ruby-interpreter] 2.1.5-2+deb8u3 Versions of packages puppet recommends: ii debconf-utils 1.5.56 ii lsb-release4.1+Debian13+nmu1 ii ruby-selinux 2.3-2 Versions of packages puppet suggests: pn ruby-rrd -- Configuration Files: /etc/puppet/puppet.conf changed [not included] -- no debconf information
Bug#859428: unblock: libvpx/1.6.1-3 (pre-approval)
Control: tags -1 confirmed moreinfo Ondřej Nový: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > I would like to know your opinion about uploading this > change to unstable + unblocking for stretch. > > This change will enable PIE, which was disabled because > of bug which was passing -fPIE to the compiler even for > dynamic libraries. Debdiff attached. Closes bug #859415. > > Thanks. > > unblock libvpx/1.6.1-3 > > [...] Ack, please go ahead. ~Niels
Bug#847282: Ping
Control: severity -1 serious On Sun, Mar 12, 2017 at 03:51:29PM +0100, Bastien ROUCARIES wrote: > n 2017-01-22 18:02, Bastien ROUCARIES wrote: > > Let decrease the severity to something not RC. I need to know if the > > problem is in dpkg or imagemagick. And I do not want to block the > > security update of imagemagick. Raising severity again, so that this issue won't get lost for stretch. > ACK. I'll try to take a more detailed look at it ... ping me if I don't > report back ... > > Ping thus Adding Andreas, replying to the bug does not Cc the submitter. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#836127: Call for Votes for new CTTE Member
I vote: > ===BEGIN > > The Technical Committee recommends that David Bremner be > appointed by the Debian Project Leader to the Technical Committee. > > A: Recommend to Appoint David Bremner > B: Further Discussion > > ===END A > B Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Bug#836127: Call for Votes for new CTTE Member
Le lundi, 3 avril 2017, 20.15:46 h CEST Philip Hands a écrit : > ===BEGIN > > The Technical Committee recommends that David Bremner be > appointed by the Debian Project Leader to the Technical Committee. > > A: Recommend to Appoint David Bremner > B: Further Discussion > > ===END I vote A > B -- OdyX signature.asc Description: This is a digitally signed message part.
Bug#859453: dunst: Installing dunst does not ensure dbus is running
Package: dunst Version: 1.1.0-2+b1 Severity:normal Dear maintainer, For dunst to work a dbus session needs to be running for the user but currently if Xorg and a simple window manager is installed dbus is not running by default which causes dunst to fail with Name Lost. Is Another notification daemon running? I recommend setting dunst to depend on or to recommend the dbus-x11 package and/or the dbus-session-bus virtual package which among other things sets dbus to launch either when the X11 session starts or when a process tries to use dbus.
Bug#858883: nslcd : missing symbols : _nss_ldap_version and _nss_ldap_enablelookups
On Mon, 2017-04-03 at 19:02 +0200, Laurent Bonnaud wrote: > This system had libnss-ldap installed, indeed. I purged this > package, installed libnss-ldapd instead, but I still get the > warnings: Are you sure, can you run? dpkg -S /lib/x86_64-linux-gnu/libnss_ldap.so.2 dpkg --get-selections | grep ldap ldd /lib/x86_64-linux-gnu/libnss_ldap.so.2 > BTW I had LDAP working with libnss-ldap but now with libnss-ldapd it > does not work any longer (but this is for another bug report...) Having the wrong NSS module installed should also explain this. -- -- arthur - adej...@debian.org - https://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#849932: libindicate: FTBFS (Fields cannot have void type)
On Mon, 27 Mar 2017 22:43:32 +0200 Andreas Henrikssonwrote: > Hello Gilles Filippini, > > Thanks for your thorough investigations. > > On Fri, Feb 03, 2017 at 12:19:26AM +0100, Gilles Filippini wrote: > [...] > > > This is caused by gtk-sharp2 2.12.40 generating this line in file > > > ListenerServer.cs: > > > static void _gtype = new void > > > (indicate_listener_server_get_type(listener == null ? IntPtr.Zero : > > > listener.Handle, server == null ? IntPtr.Zero : server.Handle, > > > cb_wrapper.NativeDelegate, IntPtr.Zero)); > > > > > > This line doesn't appear when building against the previous gtk-sharp2 > > > release from snapshot.d.o (2.12.10). According to [1] it works with > > > gtk-sharp2 2.12.29 as well. A bisect between releases 2.12.29 and 2.12.40 > > > of gtk-sharp2 might give something. > [...] > > I have no idea what I'm doing here, but attached is my naive attempt. > The solution looked obvious enough based on all your previous input. > > Could you please test if this solves the issue with libindicate for you? Upstream has applied the patch to their 2.12 branch [1]. [1] https://github.com/mono/gtk-sharp/commit/f03881939ec60cb829177d2213c6189de94f4bb9 Thanks, _g. signature.asc Description: OpenPGP digital signature
Bug#631991: libmaven-ant-tasks-java is missing all its dependencies.
Control: severity -1 serious On Tue, Jun 28, 2011 at 04:30:33PM -0700, Phil Hagelberg wrote: > Package: libmaven-ant-tasks-java > Version: 2.0.10-1 > Severity: important > > > According to > http://search.maven.org/remotecontent?filepath=org/apache/maven/maven-ant-tasks/2.0.10/maven-ant-tasks-2.0.10.pom > the maven-ant-tasks library depends upon a number of libraries > including classworlds, ant, plexus, and an assortment of maven > libraries. However, the Debian package declares no dependencies > whatsoever. Missing dependencies are considered RC. Adding ${maven:Depends} to Depends adds dependencies that look correct, but someone should double-check whether this is the correct fix. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#859451: dbus: error messages on boot for systems with NSS LDAP
Control: tags -1 + wontfix On Mon, 03 Apr 2017 at 19:35:36 +0200, Laurent Bonnaud wrote: > - does dbus really need to query the NSS databases on boot? Yes: if any user or group mentioned in /etc/dbus/system.d/ comes from LDAP, then it needs to know who they are. I would not recommend using non-local NSS without some sort of cache (unscd, nss-updatedb or sssd), and doubly so if system users are in LDAP. Unfortunately, many commonly-used packages (e.g. BlueZ) still use the firewall-style policies found in /etc/dbus/system.d/ for group-based access control, instead of letting all users communicate with the service and then doing their own authorization via polkit (like NetworkManager does). > - would it be possible to order the dbus start after network is available? In general no, because some ways to get on the network require D-Bus (NetworkManager, ConnMan, wicd), so you would have a circular dependency. If you don't use any of those, then you can configure this locally by creating /etc/systemd/system/dbus.service.d/local.conf containing something like this (untested and quite possibly wrong, see systemd documentation): [Unit] Wants=network-online.target After=network-online.target Regards, S
Bug#858915: unblock: logtool/1.2.8-9
Hi Niels, On Mon, Apr 03, 2017 at 02:16:00PM +, Niels Thykier wrote: > Unblocked, thanks. Awesome, thanks. > Btw, I think you may have wanted to run clean before downgrading > debhelper. :) At least, I doubt you wanted to include the following > files in the source. > > debian/autoreconf.after | 104 > debian/autoreconf.before | 96 Oops. > We can fix them in a later upload (or post release if there is no other > reason for updating logtool in stretch) I doubt it -- I did two uploads the past week, thereby *doubling* the number of uploads I've done for logtool that have happened since july 2008. To say that it's "low maintenance" would be an understatement. It's always possible that I'll need another upload, of course, but I don't think so. It's cruft, but I don't think it'll have any influence on the released package. I'll do an upload to bump back to compat 10 post-stretch (or maybe 11 -- be prepared for five more years ;-) and clean up the cruft then. -- < ron> I mean, the main *practical* problem with C++, is there's like a dozen people in the world who think they really understand all of its rules, and pretty much all of them are just lying to themselves too. -- #debian-devel, OFTC, 2016-02-12
Bug#859410: libwebkit2gtk-4.0-37: Memory pressure relief renders system unusable
2017-04-03 13:52 GMT+02:00 Alberto Garcia: > On Mon, Apr 03, 2017 at 12:44:40PM +0200, Alessio Gaeta wrote: > >> Please, seriously consider to cherrypick the solution. >> >> Here the links to upstream bugs: >> >> https://bugs.webkit.org/show_bug.cgi?id=164052 > > ...but this was already cherry-picked in 2.14.3: Didn't noticed it... Quite strange, though, because I suffered the very same problem past week. Could we keep this bug open for a while, so to verify if I can reproduce it? Thanks -- Alessio
Bug#760385: Unfixed old CVEs should really be RC
On Mon, Apr 03, 2017 at 08:03:16PM +0200, Moritz Muehlenhoff wrote: > On Tue, Feb 28, 2017 at 02:28:28PM +0200, Adrian Bunk wrote: > > Control: severity -1 serious > > > > Dozens of unfixed CVEs, the oldest unfixed CVEs will be more than > > 4 years old when stretch gets released. > > > > In the current state the package is really too buggy for shipping > > in a new stable release. > > Note that nodejs will not be covered by security support in stretch (as it was > done for jessie already). We had initially considered it, but with > nodejs 6 not having it made into stretch, that's not realistic. > > So these can be downgraded to non-RC (or if the release team thinks > nodejs should rather be remove from testing, removal is also an option > of course). This is not even the normal Node.js, this is a version of V8 from an upstream branch that is dead for 4 years already. > Cheers, > Moritz cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#836127: Call for Votes for new CTTE Member
I call for votes on the following ballot to fill one of two vacancies in the CTTE. Voting will begin now, and end when the outcome is no longer in doubt or one week from now. ===BEGIN The Technical Committee recommends that David Bremner be appointed by the Debian Project Leader to the Technical Committee. A: Recommend to Appoint David Bremner B: Further Discussion ===END -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature