Bug#804694: libqt5xcbqpa5 SIGSEGV crashes sporadically at QXcbWindow::handleClientMessageEvent
Package: libqt5xcbqpa5 Version: 5.5.1+dfsg-6 Severity: important Applications that are based on QT can crash with a SIGSEGV. This happens for me on owncloud-client and quasselclient, others maybe as well, but not yet stacktraced. Here is a backtrace for quasselclient. I'll happily supply more details if required. But I'm not very deep into QT. Cheers Markus Program received signal SIGSEGV, Segmentation fault. 0x7fffe1a6e94f in QXcbWindow::handleClientMessageEvent(xcb_client_message_event_t const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 (gdb) bt #0 0x7fffe1a6e94f in QXcbWindow::handleClientMessageEvent(xcb_client_message_event_t const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #1 0x7fffe1a59b2b in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #2 0x7fffe1a5a053 in QXcbConnection::processXcbEvents() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #3 0x72e777f1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7373c9dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x73741ea6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x72e47dbb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x72e4a1b6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x72e9e163 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x708bdfe7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x708be240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x708be2ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x72e9e56f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x72e4554a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x72e4d62c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x55671736 in main () -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libqt5xcbqpa5 depends on: ii libc62.19-22 ii libegl1-mesa [libegl1-x11] 10.6.8-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.6-2 ii libgcc1 1:5.2.1-23 ii libgl1-mesa-glx [libgl1] 10.6.8-1 ii libglib2.0-0 2.46.1-2 ii libice6 2:1.0.9-1+b1 ii libqt5core5a [qtbase-abi-5-5-1] 5.5.1+dfsg-6 ii libqt5dbus5 5.5.1+dfsg-6 ii libqt5gui5 5.5.1+dfsg-6 ii libsm6 2:1.2.2-1+b1 ii libstdc++6 5.2.1-23 ii libx11-6 2:1.6.3-1 ii libx11-xcb1 2:1.6.3-1 ii libxcb-glx0 1.10-3+b1 ii libxcb-icccm40.4.1-1 ii libxcb-image00.4.0-1 ii libxcb-keysyms1 0.4.0-1 ii libxcb-randr01.10-3+b1 ii libxcb-render-util0 0.3.9-1 ii libxcb-render0 1.10-3+b1 ii libxcb-shape01.10-3+b1 ii libxcb-shm0 1.10-3+b1 ii libxcb-sync1 1.10-3+b1 ii libxcb-xfixes0 1.10-3+b1 ii libxcb-xkb1 1.10-3+b1 ii libxcb1 1.10-3+b1 ii libxi6 2:1.7.5-1 ii libxkbcommon-x11-0 0.5.0-1 ii libxkbcommon00.5.0-1 ii libxrender1 1:0.9.9-2 libqt5xcbqpa5 recommends no packages. libqt5xcbqpa5 suggests no packages. -- no debconf information
Bug#804693: Broken symlink: engine_pkcs11.so -> ../ssl/engines/engine_pkcs11.so
Package: libengine-pkcs11-openssl Version: 0.2.0-1 Severity: serious The package has a links file that says: usr/lib/ssl/engines/engine_pkcs11.so usr/lib/engines/engine_pkcs11.so However, with the latest version, the original file has been renamed to: usr/lib/ssl/engines/pkcs11.so >From https://packages.debian.org/sid/amd64/libengine-pkcs11-openssl/filelist : /usr/lib/engines/engine_pkcs11.so /usr/lib/ssl/engines/libpkcs11.la /usr/lib/ssl/engines/libpkcs11.so /usr/share/doc/libengine-pkcs11-openssl/changelog.Debian.alpha.gz /usr/share/doc/libengine-pkcs11-openssl/changelog.Debian.gz /usr/share/doc/libengine-pkcs11-openssl/copyright This should be a simple fix to the links file, but in the meantime it leads to brokenness for packages trying to use /usr/lib/engines/engine_pkcs11.so, so please fix it. Thanks! Marga -- Cheers, Marga
Bug#804315: [Vmdebootstrap-devel] Namespace issues
Hi, On Tue, Nov 10, 2015 at 12:13:54AM +0100, Julian Andres Klode wrote: > May I suggest debian-cd-live or debian-live-cd as a name? That would > be close in name to debian-cd, highlighting its use case. I would advise against these suggestions, because using debian in the name of a loosely-coupled sub-project (and due to the nature of Debian, all sub-projects are loosely-coupled) is it implies a sense of "officialness" above and beyond other software that might co-exist, either now or in the future. (Consider if/when we decide that debhelper, d-i and various other things need to be replaced in the future, we will face a similar problem). For that reason, I think it would be good to avoid using the project name in software names. As such: > Or vmdebootstrap-live if you want to focus on vmdebootstrap name-wise (you > being maintainer here). Would be fine. (although vmdebootstrap is an accretion on top of debootstrap in the first place and I'd rather that wasn't the case either, mutter mutter cognitive burden of Debian tooling proliferation mutter mutter) On Tue, Nov 10, 2015 at 12:13:54AM +0100, Julian Andres Klode wrote: > Well, people seem to be happy to "invade" other namespaces, just look > at how much packages start with "apt-" ;) [which confuses users, because > they think the APT team is the right team to talk to]. Yes, the *apt* "namespace" is a good example of why *not* to do this. (See also git-buildpackage, which managed to invade two namespaces at the same time - although since fixed it seems) > But we don't have the replacement problem, there is no apt-ng package > or similar. ...yet :) It seems Iain has opted for live-wrapper now, which IMHO does not have the problems of live-build-ng. Clashing with "live-build" is considered rude, but OTOH "live*" is too-wide a namespace for live-build to claim to itself. -- Jonathan Dowland
Bug#804255: Please update initramfs in postinst
Control: tag -1 +patch On Sun, Nov 08, 2015 at 07:00:20PM -0500, Nathan Scott wrote: >Hi Steve, > >- Original Message - >> Package: xfsprogs >> Version: 3.2.1 >> Severity: important >> Tags: d-i >> >> To make this work well, all filesystem tools packages for filesystems >> that are likely to be used for / and/or /usr should call >> "update-initramfs -u" in their postinst. This will > >OK. > >> I've checked your package and I don't see any update-initramfs >> calls. > >(yep, xfsprogs has no postinst at all IIRC) > >> Please add one. If you'd like help doing that postinst work, I >> can supply a patch - just ask! > >That would be great, if you don't mind Steve? Many thanks! Here's a debdiff of what I've just built. Ignore the NMU version in the changelog... -- Steve McIntyre, Cambridge, UK.st...@einval.com The two hard things in computing: * naming things * cache invalidation * off-by-one errors -- Stig Sandbeck Mathisen diff -Nru xfsprogs-4.2.0/debian/changelog xfsprogs-4.2.0.1/debian/changelog --- xfsprogs-4.2.0/debian/changelog 2015-09-11 01:51:36.0 + +++ xfsprogs-4.2.0.1/debian/changelog 2015-11-10 16:35:45.0 + @@ -1,3 +1,11 @@ +xfsprogs (4.2.0.1) unstable; urgency=low + + * NMU + * * Add a postinst to update the initramfs on install/upgrade. +(Closes: #804255) + + -- Steve McIntyre <93...@debian.org> Tue, 10 Nov 2015 16:33:59 + + xfsprogs (4.2.0) unstable; urgency=low * New upstream release diff -Nru xfsprogs-4.2.0/debian/postinst xfsprogs-4.2.0.1/debian/postinst --- xfsprogs-4.2.0/debian/postinst 1970-01-01 00:00:00.0 + +++ xfsprogs-4.2.0.1/debian/postinst2015-11-10 16:35:20.0 + @@ -0,0 +1,25 @@ +#!/bin/sh + +set -e + +case "${1}" in + configure) + if [ -x /usr/sbin/update-initramfs ] && [ -e /etc/initramfs-tools/initramfs.conf ] + then + update-initramfs -u + fi + ;; + + abort-upgrade|abort-remove|abort-deconfigure) + + ;; + + *) + echo "postinst called with unknown argument \`${1}'" >&2 + exit 1 + ;; +esac + +#DEBHELPER# + +exit 0
Bug#802702: CVE-2011-5325: busybox: Directory traversal via crafted tar file which contains a symlink pointing outside of the current directory
tags 802702 - patch forwarded 802702 https://bugs.busybox.net/8411 thanks (Small issues with patch; see upstream tracker) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#804686: Fwd: Please update p7zip to latest upstream version in Debian unstable
Package: p7zip Courriel original Objet: Please update p7zip to latest upstream version in Debian unstable Date: 2015-11-02 00:25 De: Amr IbrahimÀ: adn+...@diwi.org Dear Mohammed, Could you please update p7zip https://tracker.debian.org/pkg/p7zip and p7zip-rar https://tracker.debian.org/pkg/p7zip-rar to the latest upstream versions in Debian unstable? Thanks a lot! Amr
Bug#804683: josm: Please switch to fonts-noto from fonts-droid
Hi Bas, Bas Couwenbergwrites: > Control: tags -1 upstream > Control: forwarded -1 https://josm.openstreetmap.de/ticket/12085 > > Hi Vasudev, > > On 2015-11-10 16:46, Vasudev Kamath wrote: >> Since Android upstream stopped shipping Droid fonts and its been >> declared that Noto fonts will be superseding the Droid¹² we in >> "Debian Fonts Task Force" team decided to drop fonts-droid package. >> >> One of your package josm either >> Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly >> request you to do the switch to fonts-noto instead. > > The josm package uses the font-droid package in favor of the embedded > copies included in the JOSM source tree, I've created an issue in the > upstream tracker requesting them to switch to the Noto fonts too. This > should keep the divergence of the Debian package to a minimum. > > I'll update JOSM package to use the Noto fonts whether or not upstream > decides to adopt them too. Thanks for the quick response.! Cheers,
Bug#800698: libqtgui4: GUI applications are unusable on amd64 systems
Hi, I was hit by this as well. It looks like it's the same issue as https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1511395 However I cannot find out what exactly is the fix applied in ubuntu and whether it's applied in debian as well. Kind regards, Yves
Bug#804697: RFS: libsass-python/0.9.1-1 [ITP] -- libsass-python -- SASS for Python
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libsass-python" Package name: libsass-python Version : 0.9.1-1 Upstream Author : Hong Minhee URL : http://hongminhee.org/libsass-python License : MIT Section : python It builds those binary packages: pysassc- SASS for Python: command line utility for libsass python-libsass - SASS for Python: a straightforward binding of libsass for Python python3-libsass - SASS for Python 3: a straightforward binding of libsass for Python3 To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libsass-python Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libs/libsass-python/libsass-python_0.9.1-1.dsc More information about libsass-python can be obtained from http://hongminhee.org/libsass-python. Note: I'd like some help on test part with pybuild that fails at the moment. Regards, Frederic Bonnard
Bug#801755: cqrlog: prompting due to modified conffiles
Nothing from upstream yet. I'll prod him again. Colin
Bug#804700: ITP: intel-cmt-cat -- Intel cache monitoring and allocation technology config tool
Package: wnpp Severity: wishlist Owner: Colin Ian King* Package name: intel-cmt-cat Version : 0.1.3 Upstream Author : Tomasz Kantecki * URL : Tomasz Kantecki * License : BSD-3-Clause Programming Lang: C Description : Intel cache monitoring and allocation technology config tool Intel cache monitoring and allocation technology config tool intel-cmt-cat provides monitoring and configuration of Intel Cache Monitoring Technology (CMT), Memory Bandwidth Monitoring (MBM) and Cache Allocation Technology (CAT) features on modern Intel (R) Xeon (R) processors. This is useful for cache configuration especially in the VM space where it can be advantageous to configure cache and pin it to specific Virtual Machines on modern Xeon CPUs.
Bug#804692: wesnoth-1.13-data: Please switch to fonts-noto from fonts-droid
Package: wesnoth-1.13-data Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package wesnoth-1.13-data either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804676: rpcbind: diff for NMU version 0.2.3-0.1
Package: rpcbind Version: 0.2.1-6.1 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for rpcbind (versioned as 0.2.3-0.1). The diff is attached to this message. Regards. diff -Nru rpcbind-0.2.1/debian/changelog rpcbind-0.2.3/debian/changelog --- rpcbind-0.2.1/debian/changelog 2015-09-24 17:11:52.0 +0200 +++ rpcbind-0.2.3/debian/changelog 2015-11-10 13:51:46.0 +0100 @@ -1,3 +1,21 @@ +rpcbind (0.2.3-0.1) unstable; urgency=low + + * Non-maintainer upload. + * New upstream release +- Enable systemd socket activation support (Closes: #679716) + * Override init.d-script-not-included-in-package and +init.d-script-not-marked-as-conffile lintian warnings/errors + * Add systemd and tmpfiles.d files (Closes: #748074) + * Add 07-Delete-the-unix-socket-only-if-we-have-created-it.patch: rpcbind +daemon shouldn't try to remove its socket if it as been socket activated + * Include some upstart jobs changes from Ubuntu (Closes: #747134) +- debian/rpcbind.rpcbind-boot.upstart: document that this job emits the + start-rpcbind event. +- Don't pass -w to rpcbind on boot up, since the files won't be there to + be read. + + -- Laurent BigonvilleTue, 10 Nov 2015 13:36:12 +0100 + rpcbind (0.2.1-6.1) unstable; urgency=high * Non-maintainer upload. diff -Nru rpcbind-0.2.1/debian/control rpcbind-0.2.3/debian/control --- rpcbind-0.2.1/debian/control2015-09-24 17:11:52.0 +0200 +++ rpcbind-0.2.3/debian/control2015-11-05 16:35:47.0 +0100 @@ -2,7 +2,7 @@ Section: net Priority: standard Maintainer: Anibal Monsalve Salazar -Build-Depends: dpkg-dev (>= 1.16.1~), debhelper (>= 9), autotools-dev, pkg-config, libtirpc-dev (>= 0.2.4-2~), libwrap0-dev +Build-Depends: dpkg-dev (>= 1.16.1~), debhelper (>= 9), dh-systemd (>= 1.5), autotools-dev, pkg-config, libtirpc-dev (>= 0.2.4-2~), libwrap0-dev, libsystemd-dev [linux-any] Standards-Version: 3.9.5 Homepage: http://sourceforge.net/projects/rpcbind/ diff -Nru rpcbind-0.2.1/debian/patches/07-Delete-the-unix-socket-only-if-we-have-created-it.patch rpcbind-0.2.3/debian/patches/07-Delete-the-unix-socket-only-if-we-have-created-it.patch --- rpcbind-0.2.1/debian/patches/07-Delete-the-unix-socket-only-if-we-have-created-it.patch 1970-01-01 01:00:00.0 +0100 +++ rpcbind-0.2.3/debian/patches/07-Delete-the-unix-socket-only-if-we-have-created-it.patch 2015-11-10 13:00:38.0 +0100 @@ -0,0 +1,48 @@ +From a9b7ffb4061dcddaa4f2387124fc8efc932c6074 Mon Sep 17 00:00:00 2001 +From: Laurent Bigonville +Date: Mon, 9 Nov 2015 22:14:26 +0100 +Subject: [PATCH] Delete the unix socket only if we have created it + +If systemd has created the unix socket on our behalf, we shouldn't try +to delete it. + +https://bugzilla.redhat.com/show_bug.cgi?id=1279076 + +Signed-off-by: Laurent Bigonville +--- + src/rpcbind.c | 5 - + 1 file changed, 4 insertions(+), 1 deletion(-) + +diff --git a/src/rpcbind.c b/src/rpcbind.c +index 045daa1..c4265cd 100644 +--- a/src/rpcbind.c b/src/rpcbind.c +@@ -87,6 +87,7 @@ static inline void __nss_configure_lookup(const char *db, const char *s) {} + int debugging = 0;/* Tell me what's going on */ + int doabort = 0; /* When debugging, do an abort on errors */ + int dofork = 1; /* fork? */ ++int createdsocket = 0; /* Did I create the socket or systemd did it for me? */ + + rpcblist_ptr list_rbl;/* A list of version 3/4 rpcbind services */ + +@@ -445,6 +446,7 @@ init_transport(struct netconfig *nconf) + memset(, 0, sizeof sun); + sun.sun_family = AF_LOCAL; + unlink(_PATH_RPCBINDSOCK); ++ createdsocket = 1; /* We are now in the process of creating the unix socket */ + strcpy(sun.sun_path, _PATH_RPCBINDSOCK); + addrlen = SUN_LEN(); + sa = (struct sockaddr *) +@@ -846,7 +848,8 @@ static void + terminate(int dummy /*__unused*/) + { + close(rpcbindlockfd); +- unlink(_PATH_RPCBINDSOCK); ++ if(createdsocket) ++ unlink(_PATH_RPCBINDSOCK); + unlink(RPCBINDDLOCK); + #ifdef WARMSTART + write_warmstart(); /* Dump yourself */ +-- +2.6.2 + diff -Nru rpcbind-0.2.1/debian/patches/series rpcbind-0.2.3/debian/patches/series --- rpcbind-0.2.1/debian/patches/series 2015-09-24 17:11:52.0 +0200 +++ rpcbind-0.2.3/debian/patches/series 2015-11-10 13:01:01.0 +0100 @@ -3,3 +3,4 @@ 04-610718-non-linux.patch run-migration CVE-2015-7236.patch +07-Delete-the-unix-socket-only-if-we-have-created-it.patch diff -Nru rpcbind-0.2.1/debian/rpcbind.lintian-overrides rpcbind-0.2.3/debian/rpcbind.lintian-overrides --- rpcbind-0.2.1/debian/rpcbind.lintian-overrides 1970-01-01 01:00:00.0 +0100 +++ rpcbind-0.2.3/debian/rpcbind.lintian-overrides 2015-11-10 13:30:28.0 +0100 @@
Bug#804536: gcc-5: [mips,mipsel] regression in optimization causes FTBFS for gsoap
control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68273 On 2015-11-10 13:22, Aurelien Jarno wrote: > On 2015-11-09 11:53, Mattias Ellert wrote: > > Package: gcc-5 > > Version: 5.2.1-23 > > Severity: serious > > Justification: causes gsoap to FTBFS > > Control: affects -1 gsoap > > Control: block 804455 by -1 > > X-Debbugs-Cc: debian-m...@lists.debian.org > > > > Hi! > > > > The binnmu of gsoap 2.8.22-1 due to the openssl transition failed on > > mips and mipsel, but succeeded on the other architectures. > > > > https://buildd.debian.org/status/package.php?p=gsoap > > > > (It also succeeded on mip64le - but the mips64el build used gcc-5 > > 5.2.1-21 while mips and mipsel used 5.2.1-23. I am not sure if this is > > relevant information.) > > > > The failure is a segmentation fault when running the soapcpp2 binary > > that has been compiled as part of the build. The soapcpp2 binary is not > > linked to openssl, so the issue is not due to the new openssl library > > that triggered the binnmu rebuild. > > > > I can reproduce the failure on the eder.debian.org porterbox. > > > > However, if I on the porterbox reduce the optimization from -O2 to -O1, > > the build succeeds. This therefore looks like a regression in > > mips/mipsel optimization. > > The wrongly compiled code is in soapcpp2_yacc.y (generated from > soapcpp2.y) on line 2272 and following: > > | case 34: > | #line 436 "soapcpp2_yacc.y" /* yacc.c:1646 */ > | { if ((yyvsp[-1].rec).sto & Stypedef) > | { sprintf(errbuf, "invalid typedef qualifier > for '%s'", (yyvsp[0].sym)->name); > | semwarn(errbuf); > | } > | printf("%p\n", (yyvsp[0].sym)); > | p = enter(sp->table, (yyvsp[0].sym)); > | p->info.typ = (yyvsp[-1].rec).typ; > | p->info.sto = (yyvsp[-1].rec).sto; > | p->info.hasval = False; > | p->info.offset = sp->offset; > | if (sp->grow) > | sp->offset += p->info.typ->width; > | else if (p->info.typ->width > sp->offset) > | sp->offset = p->info.typ->width; > | sp->entry = p; > | } > | #line 2290 "soapcpp2_yacc.c" /* yacc.c:1646 */ > | break; > > The call to enter is translated into the following code: > > | $L129: > | .loc 1 436 0 > | lw $2,-60($20) > | sw $2,188($sp) > | andi$2,$2,0x10 > | bne $2,$0,$L384 > | lui $7,%hi($LC36) > | > | lw $6,0($20) > | $LVL335 = . > | $L385: > | .loc 1 440 0 > | lw $22,%got(sp)($28) > | lw $25,%call16(enter)($28) > | lw $2,0($22) > | .reloc 1f,R_MIPS_JALR,enter > | 1: jalr$25 > | lw $4,0($2) > > Register a2 ($6) is loaded with (yyvsp[0].sym) instead of a1 ($5). > > I still have to check if it is reproducible with trunk and to find the > optimization option causing the issue. Then we can report the bug > upstream. Bug submitted upstream as PR68273. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: Digital signature
Bug#804315: live-build-ng -- live image builder built on vmdebootstrap
In the world of Debian, I'm a nobody. I happily use it for a multitude of reasons, one of them being live-build. As a casual user I don't see much of the politics that make up an organization such as Debian. I don't think I need that kind of clarity, however, to see that this is being handled in about the worst way possible. Out of the blue, someone rolls up, kicks in your door and demands you leave your house. Exactly what kind of response did you think you were going to get to that, Iain? I see Daniel hasn't responded to you and I don't blame him. I wouldn't either. Why I appreciate your contributions to Debian, this is just sad. What a jerk.
Bug#636272: Tentative date for upload of libre
Vasudev Kamathwrites: > Vasudev Kamath writes: > >>> If you are looking at baresip and librem, would you be interested in >>> being in the Uploaders: field for libre as well? I could surely use >>> help here, and since they share upstream and discussion mailing list, >>> you will probably know everything I know about the package too. >> >> Sure. I can add you as uploaders to librem and baresip but only problem >> is I use CDBS for packaging. > > Let me provide clarification for word *problem*. I'm not saying I've > problem with CDBS. I use it because I like it. What I wanted to tell > Simon is "hey if using CDBS is not a problem for you, are you okay to be > in uploaders field for librem and baresip too?" I've added you now. I'm unfortunately using cdbs for some packages too, so I know a bit about it. However, for new packages like this, why don't you start from scratch and use dh? I'm happy to do the conversion if you want. I think this will save time and reduce frustration going forward. /Simon signature.asc Description: PGP signature
Bug#804680: gnome-shell-pomodoro-data: Please switch to fonts-noto from fonts-droid
Package: gnome-shell-pomodoro-data Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package gnome-shell-pomodoro-data either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#636272: Tentative date for upload of libre
Simon Josefssonwrites: > Vasudev Kamath writes: > >> Vasudev Kamath writes: >> If you are looking at baresip and librem, would you be interested in being in the Uploaders: field for libre as well? I could surely use help here, and since they share upstream and discussion mailing list, you will probably know everything I know about the package too. >>> >>> Sure. I can add you as uploaders to librem and baresip but only problem >>> is I use CDBS for packaging. >> >> Let me provide clarification for word *problem*. I'm not saying I've >> problem with CDBS. I use it because I like it. What I wanted to tell >> Simon is "hey if using CDBS is not a problem for you, are you okay to be >> in uploaders field for librem and baresip too?" > > I've added you now. I'm unfortunately using cdbs for some packages too, > so I know a bit about it. However, for new packages like this, why > don't you start from scratch and use dh? I'm happy to do the conversion > if you want. I think this will save time and reduce frustration going > forward. Hehe I actually like CDBS and I don't feel like using anything else. So no conversions please :-). And yes lets stop at this, I just don't want to attract unwanted attention/friction for a tool.
Bug#804684: libgs9-common: Please switch to fonts-noto from fonts-droid
Package: libgs9-common Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package libgs9-common either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804687: request-tracker4: Please switch to fonts-noto from fonts-droid
Package: request-tracker4 Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package request-tracker4 either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804685: performous: Please switch to fonts-noto from fonts-droid
Package: performous Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package performous either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804689: signing-party: Please switch to fonts-noto from fonts-droid
Package: signing-party Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package signing-party either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804688: fso-frameworkd: spurious dependency on "2.7"
Package: fso-frameworkd Version: 0.10.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: fso-frameworkd/amd64 unsatisfiable Depends: 2.7 fso-frameworkd/i386 unsatisfiable Depends: 2.7 Looks like a package and version have been separated by a comma ... Cheers, Andreas
Bug#668571: Fixed in stretch
Hi, while this typo is still present in jessie, it seems to be fixed in stretch. The arp manpage in net-tools 1.60+git20150829.73cef8a-1 does not contain the typo anymore. Best, Sebastian
Bug#694634: reportbug dies on "Querying Debian BTS ..." in case of server error
Package: reportbug Version: 6.6.3 Followup-For: Bug #694634 I can reproduce this: [997]anarcat@angela:~$ reportbug wnpp *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using '"Antoine Beaupré"' as your from address. Will send report to Debian (per lsb_release). What sort of request is this? (If none of these things mean anything to you, or you are trying to report a bug in an existing package, please press Enter to exit reportbug.) 1 ITP This is an `Intent To Package'. Please submit a package description along with copyright and URL in such a report. 2 OThe package has been `Orphaned'. It needs a new maintainer as soon as possible. 3 RFA This is a `Request for Adoption'. Due to lack of time, resources, interest or something similar, the current maintainer is asking for someone else to maintain this package. They will maintain it in the meantime, but perhaps not in the best possible way. In short: the package needs a new maintainer. 4 RFH This is a `Request For Help'. The current maintainer wants to continue to maintain this package, but they needs some help to do this, because their time is limited or the package is quite big and needs several maintainers. 5 RFP This is a `Request For Package'. You have found an interesting piece of software and would like someone else to maintain it for Debian. Please submit a package description along with copyright and URL in such a report. Choose the request type: 5 Please enter the proposed package name: muchsync Checking status database... Please briefly describe this package; this should be an appropriate short description for the eventual package: > synchronize maildirs and notmuch databases Querying Debian BTS for reports on wnpp (source)... Traceback (most recent call last): File "/usr/bin/reportbug", line 2211, in main() File "/usr/bin/reportbug", line 1081, in main return iface.user_interface() File "/usr/bin/reportbug", line 1703, in user_interface latest_first=self.options.latest_first) File "/usr/lib/python2.7/dist-packages/reportbug/ui/text_ui.py", line 517, in handle_bts_query source=source, http_proxy=http_proxy, archived=archived) File "/usr/lib/python2.7/dist-packages/reportbug/debbugs.py", line 1275, in get_reports stats = debianbts.get_status(bugs) File "/usr/lib/pymodules/python2.7/debianbts.py", line 179, in get_status reply = server.get_status(*nr) File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 545, in __call__ return self.__r_call(*args, **kw) File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 567, in __r_call self.__hd, self.__ma) File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 430, in __call timeout = self.timeout) File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 318, in call raise HTTPError(code, msg) SOAPpy.Errors.HTTPError: The workaround is, of course, to use the `-b` flag and lookup the bug list on the web interface (which worked during my tests). -- Package-specific info: ** Environment settings: EDITOR="/home/anarcat/bin/e" DEBEMAIL="anar...@debian.org" DEBFULLNAME="Antoine Beaupré" INTERFACE="text" ** /home/anarcat/.reportbugrc: reportbug_version "4.12.6" mode expert ui text email "anar...@debian.org" -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt 1.0.9.8.1 ii python2.7.9-1 ii python-reportbug 6.6.3 pn python:any reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail ii debconf-utils 1.5.56 pn debsums ii dlocate 1.02+nmu3 ii emacs24-bin-common 24.4+1-5 ii file1:5.22+15-2 ii gnupg 1.4.18-7 ii postfix [mail-transport-agent] 2.11.3-1 ii python-gtk2 2.24.0-4 pn python-gtkspell pn python-urwid ii python-vte 1:0.28.2-5 ii xdg-utils 1.1.0~rc1+git20111210-7.4 Versions of packages python-reportbug depends on: ii apt 1.0.9.8.1 ii python-debian 0.1.27 ii python-debianbts 1.12 pn python:any python-reportbug suggests no packages. -- no debconf information
Bug#804679: [Pkg-fonts-devel] [pkg-cinnamon] Bug#804679: cinnamon-desktop-environment: Please switch to fonts-noto from fonts-droid
Quoting Vasudev Kamath (2015-11-10 17:02:49) > [Adding pkg-fonts-devel in Cc so others can share their suggestion] > Maximiliano Curiawrites: >> On 10/11/15 16:17, Vasudev Kamath wrote: >>> Since Android upstream stopped shipping Droid fonts and its been >>> declared that Noto fonts will be superseding the Droid¹² we in >>> "Debian Fonts Task Force" team decided to drop fonts-droid package. >>> One of your package cinnamon-desktop-environment either >>> Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly >>> request you to do the switch to fonts-noto instead. >>> If you are using Fallback variants of Droid fonts, I would like note >>> that these fonts will still be shipped as part of new >>> fonts-droid-fallback package. >> >> Cinnamon has no strong usage of the droid fonts, only a couple of svg >> files that use it, but then, are you planning to provide a fontconfig >> file to use the Noto fonts as a replacement of the Droid ones? > > I had never thought about that option. But since we are completely > dropping fonts-droid and all fonts in it, I wonder if providing a > fontconfig file will make sense. > > Dear pkg-fonts team, > > I don't have much experience with writing fontconfig files. Can you guys > please share your thoughts on above option?. Either Droid is dead and upstream simply point to Noto as an alternative with similar features as the dead one, or Droid _is_ now called Noto. Only if the latter is the case does it make sense IMO to register as replacement in fontconfig. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#605090: [RFC] Proposal for a new linux-grsec source package
On Tue, 2015-11-10 at 10:42 +0100, Yves-Alexis Perez wrote: > On sam., 2015-11-07 at 14:54 +, Ben Hutchings wrote: > > I've given this a quick review and found a few issues: > > Thanks! > > > > 1. linux-grsec-{source,support} are included in debian/control but not > > built by debian/rules.real. I think these should be built; the latter > > will be needed to build metapackages as in linux-latest. > > Done. Right now the package name is hardcoded in debian/rules.real, I'll see > if there's a way to get it from the configuration somehow (after I get more > info from the #3 and #4 replies). This seems to work: --- a/debian/rules.real +++ b/debian/rules.real @@ -13,6 +13,7 @@ DEB_HOST_MULTIARCH:= $(shell dpkg-architecture -a'$(ARCH)' -qDEB_HOST_MULTIARCH) DEB_BUILD_ARCH:= $(shell dpkg-architecture -a'$(ARCH)' -qDEB_BUILD_ARCH) endif MAINTAINER := $(shell sed -ne 's,^Maintainer: .[^<]*<\([^>]*\)>,\1,p' debian/control) +SOURCE_PACKAGE_NAME := $(shell dpkg-parsechangelog -SSource) DISTRIBUTION := $(shell dpkg-parsechangelog -SDistribution) SOURCE_DATE := $(shell dpkg-parsechangelog -SDate) SOURCE_DATE_UTC_ISO := $(shell date -u -d '$(SOURCE_DATE)' +%Y-%m-%d) @@ -191,7 +192,7 @@ install-dummy: dh_prep +$(MAKE_SELF) install-base -install-doc: PACKAGE_NAME = linux-doc-$(VERSION) +install-doc: PACKAGE_NAME = $(SOURCE_PACKAGE_NAME)-doc-$(VERSION) install-doc: DIR = $(BUILD_DIR)/build-doc install-doc: PACKAGE_DIR = debian/$(PACKAGE_NAME) install-doc: OUT_DIR = $(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME) @@ -210,7 +211,7 @@ install-doc: $(STAMPS_DIR)/build-doc gzip -9nqfr $(OUT_DIR)/Documentation +$(MAKE_SELF) install-base -install-manual: PACKAGE_NAME = linux-manual-$(VERSION) +install-manual: PACKAGE_NAME = $(SOURCE_PACKAGE_NAME)-manual-$(VERSION) install-manual: DIR=$(BUILD_DIR)/build-doc install-manual: DH_OPTIONS = -p$(PACKAGE_NAME) install-manual: $(STAMPS_DIR)/build-doc @@ -329,7 +330,7 @@ install-libc-dev_$(ARCH): +$(MAKE_SELF) install-base -install-support: PACKAGE_NAME = linux-support-$(ABINAME) +install-support: PACKAGE_NAME = $(SOURCE_PACKAGE_NAME)-support-$(ABINAME) install-support: DH_OPTIONS = -p$(PACKAGE_NAME) install-support: PACKAGE_DIR = debian/$(PACKAGE_NAME) install-support: PACKAGE_ROOT = /usr/share/$(PACKAGE_NAME) @@ -440,7 +441,7 @@ install-udeb_$(ARCH): dh_gencontrol dh_builddeb -install-source: PACKAGE_NAME = linux-source-$(VERSION) +install-source: PACKAGE_NAME = $(SOURCE_PACKAGE_NAME)-source-$(VERSION) install-source: DH_OPTIONS = -p$(PACKAGE_NAME) install-source: $(BUILD_DIR)/linux-source-$(UPSTREAMVERSION).tar.xz $(foreach FEATURESET,$(filter-out none,$(ALL_FEATURESETS)),$(BUILD_DIR)/linux-patch-$(UPSTREAMVERSION)-$(FEATURESET).patch.xz) dh_testdir --- a/debian/templates/control.main.in +++ b/debian/templates/control.main.in @@ -1,4 +1,4 @@ -Package: linux-source-@version@ +Package: @source_package@-source-@version@ Build-Profiles: Architecture: all Section: kernel @@ -13,7 +13,7 @@ Description: Linux kernel source for version @version@ with Debian patches features that have already been (or are believed to be) accepted by the upstream maintainers. -Package: linux-doc-@version@ +Package: @source_package@-doc-@version@ Build-Profiles: Architecture: all Depends: ${misc:Depends} @@ -27,7 +27,7 @@ Description: Linux kernel specific documentation for version @version@ /usr/share/doc/linux-doc-@version@/Documentation/00-INDEX for the detailed description of the contents. -Package: linux-manual-@version@ +Package: @source_package@-manual-@version@ Build-Profiles: Architecture: all Depends: ${misc:Depends} @@ -46,7 +46,7 @@ Description: Linux kernel API manual pages for version @version@ may be installed at a time. The linux-doc package containing the documentation in other formats is free from such restriction. -Package: linux-support-@abiname@ +Package: @source_package@-support-@abiname@ Build-Profiles: Architecture: all Section: devel --- END --- [...] > > 3. The changes to gencontrol.py and rules.real to disable most arch:all > > packages should depend on configuration, not the source package name. > > They would then be acceptable for inclusion on the master branch. > > By “configuration”, I guess you mean stuff in debian/config/featureset- > grsec/defines? Unfortunately some of the stuff I touch in gencontrol.py and > rules.real is not run when featureset is defined, but is more generic than > that. > > Or do you mean I would then modify debian/config/defines (and not the one > under the featureset-grsec folder) in src;linux-grsec? You would modify debian/config/defines. > > 4. There's no need to remove the templates for packages you don't > > build. However, if you leave them in place, you'll need to override > > do_extra() in gencontrol.py to omit the extra packages dependent on the > > configuration (as for (3)). > > Ok, I'll check
Bug#736824: New release of POSIX manpages
On Mon, 27 Jan 2014 09:33:55 +0100 Francesco Paolo Loverginewrote: > Package: manpages-posix > Version: 2.16-1 > Severity: wishlist I wrote script to help package update. This makes manpages-posix-2.17 with patched debian/ for 2.17. Please update this package. #!/bin/sh NEW=man-pages-posix-2013-a NEW_TAR=$NEW.tar.xz OLD_VER=2.16 OLD_DEB=manpages-posix-$OLD_VER NEW_DEB=manpages-posix-2.17 # get new version wget https://www.kernel.org/pub/linux/docs/man-pages/man-pages-posix/$NEW_TAR # get original package apt-get source manpages-posix # prepare new package tar xf $NEW_TAR mv $NEW $NEW_DEB # copy debian/ cp -a $OLD_DEB/debian $NEW_DEB # remove original package rm -rf $OLD_DEB* manpages-posix_$OLD_VER* cd $NEW_DEB # make .orig.tar.xz echo s | dh_make -f ../$NEW_TAR # modify for 2.17 cat <<'EOF' | patch -p1 diff -urNp a/debian/changelog b/debian/changelog --- a/debian/changelog 2005-12-13 19:56:41.0 +0900 +++ b/debian/changelog 2015-11-10 22:49:01.907770018 +0900 @@ -1,3 +1,9 @@ +manpages-posix (2.17-1) unstable; urgency=medium + + * New upstream release. (IEEE Std 1003.1, 2013 Edition) + + -- Francesco Paolo Lovergine Tue, 10 Nov 2015 13:07:09 +0100 + manpages-posix (2.16-1) unstable; urgency=low * Alligned to linux main manpages edition. diff -urNp a/debian/clean b/debian/clean --- a/debian/clean 1970-01-01 09:00:00.0 +0900 +++ b/debian/clean 2015-11-10 22:36:58.065770242 +0900 @@ -0,0 +1,4 @@ +*~ +*.orig +#* +debian/*~ diff -urNp a/debian/compat b/debian/compat --- a/debian/compat 1970-01-01 09:00:00.0 +0900 +++ b/debian/compat 2015-11-10 21:19:29.114402873 +0900 @@ -0,0 +1 @@ +9 diff -urNp a/debian/control b/debian/control --- a/debian/control 2005-12-13 20:00:05.0 +0900 +++ b/debian/control 2015-11-10 22:31:33.781326635 +0900 @@ -2,8 +2,8 @@ Source: manpages-posix Section: non-free/doc Priority: optional Maintainer: Francesco Paolo Lovergine -Standards-Version: 3.6.2 -Build-Depends-Indep: debhelper (>= 4.0.0) +Build-Depends: debhelper (>= 9) +Standards-Version: 3.9.6 Package: manpages-posix Architecture: all diff -urNp a/debian/copyright b/debian/copyright --- a/debian/copyright 2004-08-21 23:18:51.0 +0900 +++ b/debian/copyright 2015-11-10 21:09:38.306383201 +0900 @@ -2,7 +2,7 @@ This package was debianized by Francesco Sat, 21 Aug 2004 15:41:06 +0100. Packaged based partially on manpages in main section. -It was downloaded from ftp://ftp.win.tue.nl/pub/linux-local/manpages +It was downloaded from https://www.kernel.org/pub/linux/docs/man-pages/man-pages-posix/ Authors: The Institute of Electrical and Electronics Engineers (IEEE) and The Open Group @@ -19,20 +19,20 @@ In the following statement, the phrase ` portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form -in the linux-manpages package, from IEEE Std 1003.1 (TM), 2003 Edition, -Standard for Information Technology -- Portable Operating System -Interface (POSIX (R)), The Open Group Base Specifications Issue 6, -Copyright (C) 2001-2003 by the Institute of Electrical and Electronics -Engineers, Inc and The Open Group. In the event of any discrepancy -between these versions and the original IEEE and The Open Group -Standard, the original IEEE and The Open Group Standard is the referee -document. The original Standard can be obtained online at -http://www.opengroup.org/unix/online.html . +from IEEE Std 1003.1, 2013 Edition, Standard for Information Technology +-- Portable Operating System Interface (POSIX), The Open Group Base +Specifications Issue 7, Copyright (C) 2013 by the Institute of Electri- +cal and Electronics Engineers, Inc and The Open Group. (This is +POSIX.1-2008 with the 2013 Technical Corrigendum 1 applied.) In the +event of any discrepancy between this version and the original IEEE and +The Open Group Standard, the original IEEE and The Open Group Standard +is the referee document. The original Standard can be obtained online +at http://www.unix.org/online.html . This notice shall appear on any product containing this material. Redistribution of this material is permitted so long as this notice and the corresponding notices within each POSIX manual page are retained on -any distribution, and the nroff source is included. Modifications to +any distribution, and the nroff source is included. Modifications to the text are permitted so long as any conflicts with the standard are clearly marked as such in the text. diff -urNp a/debian/inst b/debian/inst --- a/debian/inst 2004-08-23 06:08:14.0 +0900 +++ b/debian/inst 2015-11-10 21:08:25.349392461 +0900 @@ -39,5 +39,3 @@ for i in man[013]p; do gzip -9 debian/$p/usr/share/man/man$d/*.?posix echo done - - diff -urNp a/debian/readme b/debian/readme --- a/debian/readme 2004-08-21 21:51:28.0 +0900 +++ b/debian/readme 2015-11-10 21:09:19.586128995 +0900 @@ -1,6 +1,6
Bug#804691: wesnoth-1.12-data: Please switch to fonts-noto from fonts-droid
Package: wesnoth-1.12-data Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package wesnoth-1.12-data either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804679: [pkg-cinnamon] Bug#804679: cinnamon-desktop-environment: Please switch to fonts-noto from fonts-droid
[Adding pkg-fonts-devel in Cc so others can share their suggestion] Maximiliano Curiawrites: > Control: tag -1 + pending > > On 10/11/15 16:17, Vasudev Kamath wrote: >> Since Android upstream stopped shipping Droid fonts and its been >> declared that Noto fonts will be superseding the Droid¹² we in >> "Debian Fonts Task Force" team decided to drop fonts-droid package. >> One of your package cinnamon-desktop-environment either >> Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly >> request you to do the switch to fonts-noto instead. >> If you are using Fallback variants of Droid fonts, I would like note >> that these fonts will still be shipped as part of new >> fonts-droid-fallback package. > Cinnamon has no strong usage of the droid fonts, only a couple of svg > files that use it, but then, are you planning to provide a fontconfig > file to use the Noto fonts as a replacement of the Droid ones? I had never thought about that option. But since we are completely dropping fonts-droid and all fonts in it, I wonder if providing a fontconfig file will make sense. Dear pkg-fonts team, I don't have much experience with writing fontconfig files. Can you guys please share your thoughts on above option?. > Happy hacking, Thanks,
Bug#804079: reportbug dump
Hi ! Below is the attachment of reportbug dump from the original machine. Kind regards, Jan Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: rootTo: Debian Bug Tracking System Subject: linux-image-3.16.0-4-amd64: Kernel panic on Xen virtualisation in Debian Bcc: root Package: src:linux Version: 3.16.7-ckt11-1+deb8u5 Severity: important -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) ** Command line: root=/dev/mapper/vg0-dom0_root earlyprintk=xen debug loglevel=8 acpi_rsdp=0x7f7fe014 console=tty1 console=hvc0 ** Not tainted ** Kernel log: ** Model information sys_vendor: IBM product_name: System x3550 M3 -[7944F2G]- product_version: 00 chassis_vendor: IBM chassis_version: none bios_vendor: IBM Corp. bios_version: -[D6E159AUS-1.17]- board_vendor: IBM board_name: 69Y4438 board_version: (none) ** Loaded modules: xt_set ip_set_hash_ip ip_set nfnetlink xt_LOG xt_limit xt_physdev xen_acpi_processor xen_pciback xen_netback xen_blkback xen_gntalloc xen_gntdev xen_evtchn xenfs xen_privcmd openvswitch gre vxlan xt_multiport ip6table_filter ip6_tables ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables ext4 crc16 mbcache jbd2 jc42 fuse intel_powerclamp coretemp crc32_pclmul ghash_clmulni_intel iTCO_wdt iTCO_vendor_support ipmi_devintf ttm drm_kms_helper aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse pcspkr serio_raw cdc_ether usbnet mii drm i2c_algo_bit i2c_i801 i2c_core evdev joydev lpc_ich mfd_core ioatdma i7core_edac ipmi_si dca edac_core tpm_tis tpm ipmi_msghandler button processor thermal_sys shpchp xfs libcrc32c btrfs dm_mod raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 ata_generic hid_generic usbhid sg sd_mod crc_t10dif hid crct10dif_generic ata_piix crct10dif_pclmul crct10dif_common crc32c_intel libata ehci_pci uhci_hcd ehci_hcd megaraid_sas scsi_mod usbcore usb_common md_mod e1000e ptp pps_core bnx2 xen_blkfront ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22) Subsystem: IBM Device [1014:7270] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 22) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Subsystem: IBM Device [1014:3408] Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit- Address: 0020 Data: Masking: Pending: Capabilities: [90] Express (v2) Root Port (Slot-), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ Unsupported- RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 5GT/s, Width x2, ASPM not supported, Exit Latency L0s <512ns, L1 <64us ClockPM- Surprise+ LLActRep+ BwNot+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch+ ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s, Width x2, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal+ ErrFatal+ PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range BCD, TimeoutDis+, LTR-, OBFF Not Supported ARIFwd+ DevCtl2: Completion Timeout: 260ms to 900ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [e0] Power Management version 3 Flags: PMEClk- DSI- D1- D2-
Bug#804695: kodi: Please switch to fonts-noto from fonts-droid
Source: kodi Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package kodi either Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804683: josm: Please switch to fonts-noto from fonts-droid
Control: tags -1 upstream Control: forwarded -1 https://josm.openstreetmap.de/ticket/12085 Hi Vasudev, On 2015-11-10 16:46, Vasudev Kamath wrote: Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package josm either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. The josm package uses the font-droid package in favor of the embedded copies included in the JOSM source tree, I've created an issue in the upstream tracker requesting them to switch to the Noto fonts too. This should keep the divergence of the Debian package to a minimum. I'll update JOSM package to use the Noto fonts whether or not upstream decides to adopt them too. Kind Regards, Bas
Bug#804676: rpcbind: diff for NMU version 0.2.3-0.2
Package: rpcbind Followup-For: Bug #804676 Hi Please find here the patch for my 2nd NMU 0.2.3-0.2 Cheers, Laurent Bigonville -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rpcbind depends on: ii init-system-helpers 1.24 ii initscripts 2.88dsf-59.2 ii insserv 1.14.0-5 ii libc62.19-22 ii libsystemd0 227-2 ii libtirpc10.2.5-1 ii libwrap0 7.6.q-25 ii lsb-base 9.20150917 rpcbind recommends no packages. rpcbind suggests no packages. -- no debconf information diff -Nru rpcbind-0.2.3/debian/changelog rpcbind-0.2.3/debian/changelog --- rpcbind-0.2.3/debian/changelog 2015-11-10 13:51:46.0 +0100 +++ rpcbind-0.2.3/debian/changelog 2015-11-10 17:07:31.0 +0100 @@ -1,3 +1,11 @@ +rpcbind (0.2.3-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rpcbind.service: Set Type=notify and ask the daemon to not +daemonize itself, rpcbind daemon is calling sd_notify() when ready. + + -- Laurent BigonvilleTue, 10 Nov 2015 17:07:03 +0100 + rpcbind (0.2.3-0.1) unstable; urgency=low * Non-maintainer upload. diff -Nru rpcbind-0.2.3/debian/rpcbind.service rpcbind-0.2.3/debian/rpcbind.service --- rpcbind-0.2.3/debian/rpcbind.service 2015-11-05 17:23:45.0 +0100 +++ rpcbind-0.2.3/debian/rpcbind.service 2015-11-10 17:01:19.0 +0100 @@ -8,10 +8,10 @@ [Service] Environment="OPTIONS=-w" -ExecStart=/sbin/rpcbind $OPTIONS +ExecStart=/sbin/rpcbind -f $OPTIONS EnvironmentFile=-/etc/rpcbind.conf EnvironmentFile=-/etc/default/rpcbind -Type=forking +Type=notify KillMode=process Restart=on-failure
Bug#804591: [Pkg-iscsi-maintainers] Bug#804591: open-iscsi: iscsi_auto flag should use iscsistart --fwparam_network in addition to -b
On Mon, 9 Nov 2015, Christian Seiler wrote: > Hi, > > On 11/09/2015 10:40 PM, Scott Moser wrote: > >>> If we were to invoke 'iscsistart --fwparam_network' after having done > >>> configure_networking, then the iscsi parameters would be in affect. > >>> Its may be arguable that this is simply misconfiguration of the ip= > >>> parameter. > >> > >> On the other hand, one could argue that one might want to overwrite > >> the parameters set in the firmware with an explicit kernel commmand > >> line. > > > > Agreed. > > > >> I think the case is definitely clear if iscsi_auto is specified > >> without an ip= parameter, then iscsistart should take care of it. > > > > Definitely. Unfortunately, the case that I'm working on is with MAAS > > which specifies a ip= command line to its provided iscsi server. The > > install environment is then provided over read-only iscsi. > > Does the ip= match here or is there some problem with it? If > there's no problem and you are just mentioning it to be > cautious: I think it's fair to ask our users to not > misconfigure their network in initramfs. I mean, without > iscsi_auto and manual iSCSI config a wrong ip= will also lead > to an unbootable system. in the specific case, the ip= was for eth0 and 2 other nics would be configured per the iBFT. I was just listing it as an example of where you would possibly have ip= *and* want iscsistart --fwparam_network. > > It seems reasonable that you might have 'ip=' on the kernel command line > > for reasons unrelated to iscsi entirely, and possibly referencing > > different network devices. > > Then maybe we should do the following: if iscsi_auto is specified, > call iscsistart -N first, then configure the network regularly. > Then ip= will always override iBFT, but other devices will also > be activated. > > >> Btw. is there any way to test this in a VM? I don't have access to > >> the corresponding hardware that sets these values, so I can't > >> really test this myself. > > > > Luckily, you *can* do it entirely within qemu and ipxe with a few minor > > limitations. Figuring out how to do that is non-trivial, but I've managed > > my way through it. > > Oh great, I don't have time today anymore (I'm in time zone UTC+01, > so it's quite late here ;-)), but I'll take a look at it during > the next few days. > > > Right, that was my thought too. I might suggest not reading iscsistart > > -f, but rather the files from /sys/firmware/ibft. > > The problem there is matching against the right network interface > name - it's certainly possible, but parsing the output of > iscsistart is probably a lot simpler. > > > Here is some output > > from each, for those not adventuresome enough to try on their own. Note, i > > added a carriage return to subnet mask that did not have one. > > Where exactly did it not have a carriage return? According to > the open-iscsi source, all values printed have \n there > (at least Debian's git snapshot, maybe that was a bug in the > version that was fixed between the version you use and the > version I have). the /sys interface did not have a subnet mask. ie, /sys/firmware/ibft/ethernet0/subnet-mask had no trailing carriage return. > > I've created a VERY simple parser in POSIX shell that reads > the input of iscsistart -f and pseudo-creates the /run/net- > file and attached it to this email. If you don't have any > objections to it, I'll integrate that into the initramfs hook. it seems to look fine. reading from /sys isnt terribly hard, though. the mapping of nic name from ibft to current linux nic name is easily enough made through: /sys/class/net//address == /sys/firmware/ibft/ethernet0/mac your parser seems fine, and only incurs one subshell, so that is nice. > > Regards, > Christian >
Bug#800698: Exhausts X11 shared memory
Hello, I was hit by this bug in oldstable (wheezy), after upgrading to openjdk-7-jdk (and related packages) version 7u85-2.6.1-6~deb7u1 in the wheezy-security repository. After a while using tomcat and netbeans the Qt applications start losing textures. Also, other applications complain about not having enough shared memory (specifically, an Oracle DBMS instance refused to start because of this). I downgraded to 7u79-2.5.6-1~deb7u1, which was the last version I had in cache and everything worked fine again.
Bug#804677: bash-completion: Bad completions for _longopt and "/'/"
Package: bash-completion Version: 1:2.1-4.2 Severity: minor Setup: # . /etc/bash_completion # complete -p | grep tail complete -F _longopt tail and "_longopt" from /usr/share/bash-completion/bash_completion I can see this behaviour: # tail /'/ gives # tail /'// gives # tail /'/// gives # tail /' gives # tail /'/ etc. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bash-completion depends on: ii bash 4.3-14 ii dpkg 1.18.3 bash-completion recommends no packages. bash-completion suggests no packages. -- no debconf information
Bug#804079: Additional information
Hello Ian ! Thanks for looking into the bug. Regarding your question whether it happend once: yes and no, it happened several times last summer, but that was an older kernel version, debians linux-image-3.14-2-amd64 back then and self-built 3.15.7, both with xen 4.4.0 Will try to include more information regarding this bug later, from the "reportbug" application. If there is any other application to be tested with, you can suggest it to me. Kind regards, Jan
Bug#804679: [pkg-cinnamon] Bug#804679: cinnamon-desktop-environment: Please switch to fonts-noto from fonts-droid
Control: tag -1 + pending On 10/11/15 16:17, Vasudev Kamath wrote: > Since Android upstream stopped shipping Droid fonts and its been > declared that Noto fonts will be superseding the Droid¹² we in > "Debian Fonts Task Force" team decided to drop fonts-droid package. > One of your package cinnamon-desktop-environment either > Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly > request you to do the switch to fonts-noto instead. > If you are using Fallback variants of Droid fonts, I would like note > that these fonts will still be shipped as part of new > fonts-droid-fallback package. Cinnamon has no strong usage of the droid fonts, only a couple of svg files that use it, but then, are you planning to provide a fontconfig file to use the Noto fonts as a replacement of the Droid ones? Happy hacking,
Bug#804698: RFP: muchsync -- synchronize maildirs and notmuch databases
Package: wnpp Severity: wishlist * Package name: muchsync Version : 2 Upstream Author : David Mazieres* URL : http://www.muchsync.org/ * License : GPL-2+ Programming Lang: C++ Description : synchronize maildirs and notmuch databases Muchsync brings notmuch to all of your computers by synchronizing your mail messages and notmuch tags across machines. The protocol is heavily pipelined to work efficiently over high-latency networks such as mobile broadband. Muchsync supports arbitrary pairwise synchronization among replicas. A version-vector-based algorithm allows it to exchange only the minimum information necessary to bring replicas up to date regardless of which pairs have previously synchronized. This package is pretty awesome, and is a perfect candidate for inclusion in Debian: * it requires compilation by hand, so is not easily distributed right now, which is a requirement as it needs to be installed on both ends * it depends on notmuch libraries, commonly packaged in Debian * it works! or at least i think it does: i'm testing it right now The thing compiles out of the box using autoconf tools and needs libxapian-dev and libnotmuch-dev. I'd be happy to co-maintain this but since there are already notmuch maintainers right now, i'd like them to take this over. Plus i'm lazy. Thanks!
Bug#804596: pdns-server: New version fails to sign axfrs
Hello, On 10 Nov 2015, at 17:25, James Cloos wrote: "PvD" == Peter van Dijkwrites: So it looks like running check-all-zones changed something. PvD> That doesn’t make any sense :( check-all-zones is a readonly PvD> operation. That is what I had previously presumed but something changed. I only changed two of the zones based on the check-all-zones output and that allowed all of the zones to *start* working again. Ah, so more happened than just the running of check-all-zones. That is a bit less confusing at least. Perhaps the issue then is that the geoip backend changed its name and thus failed to upgrade with the server and the pg backend. Although my config didn't load the geo backend... geo did not change its name - geoip is a different backend. I noticed when I grabbed the old debs from the pool that the package name changed from pdns-backend-geo to pdns-backend-geoip. After Christian's first reply I manually removed the geo backend, fixed the couple of errors reported by check (a couple of duplicate CNAME records and an OPENPGPKEY records in raw syntax from when I was trying to add support back before the stroke). Ah yes, raw syntax for a type we support is a known bug, sorry about that. Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/
Bug#636272: Tentative date for upload of libre
Vasudev Kamathwrites: >> If you are looking at baresip and librem, would you be interested in >> being in the Uploaders: field for libre as well? I could surely use >> help here, and since they share upstream and discussion mailing list, >> you will probably know everything I know about the package too. > > Sure. I can add you as uploaders to librem and baresip but only problem > is I use CDBS for packaging. Let me provide clarification for word *problem*. I'm not saying I've problem with CDBS. I use it because I like it. What I wanted to tell Simon is "hey if using CDBS is not a problem for you, are you okay to be in uploaders field for librem and baresip too?" Hope that clarifies (/me looks at Jonas)
Bug#804679: cinnamon-desktop-environment: Please switch to fonts-noto from fonts-droid
Package: cinnamon-desktop-environment Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package cinnamon-desktop-environment either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804678: blender: Please switch from fonts-droid to fonts-noto
Package: blender Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package blender either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804682: dolphin: Dolphin starts on wrong virtual desktop
Package: dolphin Version: 4:15.08.2-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Dolphin is one of the programs I keep open on a virtual desktop permanently. I use desktop 3 for Dolphin. However since upgrading to plasma 5 desktop, Dolphin starts on Desktop 1 and I have to move it Desktop 3. This is a minor annoyance that becomes more than an annoyance when it covers Icedove, which sometimes launches before the network share where I keep my mail folders is mounted (but that is a separate issue). * 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 *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dolphin depends on: ii libc6 2.19-22 ii libdolphinvcs5 4:15.08.2-1 ii libkf5baloo5 5.15.0+-1 ii libkf5baloowidgets515.08.0-2 ii libkf5bookmarks5 5.15.0-1 ii libkf5codecs5 5.15.0-1 ii libkf5completion5 5.15.0-1 ii libkf5configcore5 5.15.0-1 ii libkf5configgui5 5.15.0-1 ii libkf5configwidgets5 5.15.0-1 ii libkf5coreaddons5 5.15.0-1 ii libkf5dbusaddons5 5.15.0-1 ii libkf5filemetadata35.15.0-1 ii libkf5i18n55.15.0-1 ii libkf5iconthemes5 5.15.0-1 ii libkf5itemviews5 5.15.0-1 ii libkf5jobwidgets5 5.15.0-1 ii libkf5kcmutils55.15.0-1 ii libkf5kiocore5 5.15.0-1 ii libkf5kiofilewidgets5 5.15.0-1 ii libkf5kiowidgets5 5.15.0-1 ii libkf5newstuff55.15.0-1 ii libkf5notifications5 5.15.0-1 ii libkf5parts5 5.15.0-1 ii libkf5service-bin 5.15.0+-1 ii libkf5service5 5.15.0+-1 ii libkf5solid5 5.15.0-1 ii libkf5textwidgets5 5.15.0-1 ii libkf5widgetsaddons5 5.15.0-1 ii libkf5windowsystem55.15.0-1 ii libkf5xmlgui5 5.15.0-1 ii libphonon4qt5-44:4.8.3-2 ii libqt5core5a 5.5.1+dfsg-6 ii libqt5dbus55.5.1+dfsg-6 ii libqt5gui5 5.5.1+dfsg-6 ii libqt5widgets5 5.5.1+dfsg-6 ii libqt5xml5 5.5.1+dfsg-6 ii libstdc++6 5.2.1-23 ii phonon4qt5 4:4.8.3-2 Versions of packages dolphin recommends: ii ruby 1:2.1.5.1 Versions of packages dolphin suggests: ii dolphin-plugins 4:15.08.2-1 -- no debconf information
Bug#804683: josm: Please switch to fonts-noto from fonts-droid
Package: josm Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package josm either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804135: first draft
Here is a first draft on mentors : http://mentors.debian.net/package/libsass-python I need to improve a few things though. F.
Bug#804696: icedove: Icedove accounts, folders and e-mail sometimes missing on launch
Package: icedove Version: 38.3.0-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Sometimes when I start Icedove, I get nothing in any of the panels. The only thing that may be unusual about my setup is my mail folders are stored on an NFS share. * What exactly did you do (or not do) that was effective (or ineffective)? If I change the folder view to unread then restart Icedove and change it back to All, the accounts, folders, etc. return. * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages icedove depends on: ii debianutils 4.5.1 ii fontconfig2.11.0-6.3 ii libasound21.0.29-1 ii libatk1.0-0 2.18.0-1 ii libc6 2.19-22 ii libcairo2 1.14.4-1 ii libdbus-1-3 1.10.2-1 ii libdbus-glib-1-2 0.102-1 ii libevent-2.0-52.0.21-stable-2+b1 ii libffi6 3.2.1-3 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.6-2 ii libgcc1 1:5.2.1-23 ii libgdk-pixbuf2.0-02.32.1-1 ii libglib2.0-0 2.46.1-2 ii libgtk2.0-0 2.24.28-1 ii libhunspell-1.3-0 1.3.3-3+b1 ii libnspr4 2:4.10.10-1 ii libnss3 2:3.20.1-1 ii libpango-1.0-01.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libpangoft2-1.0-0 1.38.1-1 ii libpixman-1-0 0.33.4-1 ii libsqlite3-0 3.9.1-2 ii libstartup-notification0 0.12-4 ii libstdc++65.2.1-23 ii libvpx2 1.4.0-4 ii libx11-6 2:1.6.3-1 ii libxcomposite11:0.4.4-1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes31:5.0.1-2+b2 ii libxrender1 1:0.9.9-2 ii libxt61:1.1.5-1 ii psmisc22.21-2.1 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages icedove recommends: ii hunspell-en-us [hunspell-dictionary] 20070829-6 ii iceowl-extension 38.3.0-2 Versions of packages icedove suggests: ii fonts-lyx 2.1.4-2 ii libgssapi-krb5-2 1.13.2+dfsg-4 -- no debconf information
Bug#804596: pdns-server: New version fails to sign axfrs
> "PvD" == Peter van Dijkwrites: >> So it looks like running check-all-zones changed something. PvD> That doesn’t make any sense :( check-all-zones is a readonly PvD> operation. That is what I had previously presumed but something changed. I only changed two of the zones based on the check-all-zones output and that allowed all of the zones to *start* working again. Perhaps the issue then is that the geoip backend changed its name and thus failed to upgrade with the server and the pg backend. Although my config didn't load the geo backend... I noticed when I grabbed the old debs from the pool that the package name changed from pdns-backend-geo to pdns-backend-geoip. After Christian's first reply I manually removed the geo backend, fixed the couple of errors reported by check (a couple of duplicate CNAME records and an OPENPGPKEY records in raw syntax from when I was trying to add support back before the stroke). After those changes all of the zones worked again. Before them none of the zones worked. Non AXFR requests worked, though. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#517637: Standard Tarball Suffixes
One security issue would be if someone slipped a specially crafted tarball into the upstream site: that tarball could maybe do bad things in a shell script that is extracting the version string. This would put the shell script and everything it uses into the "code should be secure against malformed input" category. On the other hand, it is always nice to automate any kind of "do this scan periodically" process.
Bug#804681: konsole doesn't launch on startup
Package: konsole Version: 4:15.08.2-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I keep konsole open on a virtual desktop at all times. I have 3 tabs open in Konsole in different directories for various purposes. Prior to the plasma5 desktop, Konsole would launch when I logged in, with the various tabs and directories preserved. It no longer does this. I have to manually launch Konsole, create the tabs and change to the directories. While not a serious flaw, it is annoying. Other programs that I keep active like Iceweasel, Kontact, gkrellm and dolphin start up on login and have their settings preserved. * 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 *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages konsole depends on: ii konsole-kpart 4:15.08.2-1 ii konsole4-kpart 4:4.14.2-3 ii libc6 2.19-22 ii libkf5completion5 5.15.0-1 ii libkf5configcore5 5.15.0-1 ii libkf5configgui55.15.0-1 ii libkf5configwidgets55.15.0-1 ii libkf5coreaddons5 5.15.0-1 ii libkf5i18n5 5.15.0-1 ii libkf5iconthemes5 5.15.0-1 ii libkf5kdelibs4support5 5.15.0-1 ii libkf5kiowidgets5 5.15.0-1 ii libkf5notifyconfig5 5.15.0-1 ii libkf5widgetsaddons55.15.0-1 ii libkf5windowsystem5 5.15.0-1 ii libkf5xmlgui5 5.15.0-1 ii libqt5core5a5.5.1+dfsg-6 ii libqt5gui5 5.5.1+dfsg-6 ii libqt5widgets5 5.5.1+dfsg-6 ii libstdc++6 5.2.1-23 konsole recommends no packages. konsole suggests no packages. -- no debconf information
Bug#804690: texlive-fonts-extra: Please switch to fonts-noto from fonts-droid
Package: texlive-fonts-extra Severity: normal User: pkg-fonts-de...@lists.alioth.debian.org Usertags: droid-migration Dear Maintainer, Since Android upstream stopped shipping Droid fonts and its been declared that Noto fonts will be superseding the Droid¹² we in "Debian Fonts Task Force" team decided to drop fonts-droid package. One of your package texlive-fonts-extra either Depends/Recommends/Suggests/Build-Depends on fonts-droid. I kindly request you to do the switch to fonts-noto instead. If you are using Fallback variants of Droid fonts, I would like note that these fonts will still be shipped as part of new fonts-droid-fallback package. ¹ https://github.com/googlei18n/noto-fonts/issues/555 ² http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151031/011f4334/attachment.mht Best Regards,
Bug#804100: RFS: rhythmbox-plugin-alternative-toolbar/0.14.0-1~debian [ITP]
Hi Gianfranco, quick question - I received what looks like some sort of automated emails - not sure what these mean - do I need to-do anything? thanks in advance. "> block 804192 by 804100 Bug #804192 [wnpp] ITP: rhythmbox-plugin-alternative-toolbar -- Replace the Rhythmbox large toolbar with a Client-Side Decorated or Compact Toolbar which can be hidden 804192 was not blocked by any bugs. 804192 was not blocking any bugs. Added blocking bug(s) of 804192: 804100 > stop Stopping processing here." and "Processing commands for cont...@bugs.debian.org: > retitle 804100 RFS: rhythmbox-plugin-alternative-toolbar/0.14.1-1 [ITP] Bug #804100 [sponsorship-requests] RFS: rhythmbox-plugin-alternative-toolbar/0.14.0-1~debian [ITP] Changed Bug title to 'RFS: rhythmbox-plugin-alternative-toolbar/0.14.1-1 [ITP]' from 'RFS: rhythmbox-plugin-alternative-toolbar/0.14.0-1~debian [ITP]' > stop Stopping processing here. Please contact me if you need assistance." On 7 November 2015 at 00:35, foss.freedomwrote: > Gianfranco, > > as you have recommended I have revamped the package. This has been > uploaded to mentors.debian.net > > dget -x > http://mentors.debian.net/debian/pool/main/r/rhythmbox-plugin-alternative-toolbar/rhythmbox-plugin-alternative-toolbar_0.14.1-1.dsc > > > The package now just uses the Github tarball - I no longer build this > separately. > > The change log has a close statement with the ITP WNPP bug number > > The control description and extended description fields have been > reworked. > > In terms of the my Githhub repository - again as you have recommended, > the debian subfolder and gentoo subfolders are now in their own branches. > This should make maintenance of the package easier moving forward. > > thanks > > David (fossfreedom) > > On 6 November 2015 at 13:50, Gianfranco Costamagna < > costamagnagianfra...@yahoo.it> wrote: > >> Hi, >> >> >"Description: Show or hide the main toolbar for Rhythmbox" >> > >> >Maybe something like this is better? >> > >> >"Description: a Rhythmbox 3.x plugin that provides an enhanced toolbar >> capability. >> > A compact toolbar with enhanced song seek capabilities. >> > A revised graphical interface using the Gnome Headerbar is also >> available. >> > >> > A new simpler sidebar with refreshed icons is optionally available." >> >> >> yes, the problem is the extended description, that should have something >> (look at some packages in the archive for references) >> >> >The Git tarball as far as I understand it is a snapshot of the >> particular commit - e.g. v0.14.1 >> >> >> yes, the tag >> >This tarball would include all the sourcetree files including the files >> you said I shouldnt include in the debian package - the .git folder, the >> tar.gz file etc. >> >> >> there arent any tar.gz or git files AFAIK (well, one single tar.gz file >> but we can leave with it). >> >> I would suggest you moving gentoo and debian in separate branches, to >> avoid the need to release a new upstream release when a packaging bug is >> fixed. >> >> I can live with some useless files in the source tarball, as long as no >> repackage is needed (and it seems to be not the case) >> >> >> >Maybe I'm just building the debian package in the wrong manner. I'm >> doing the following at the moment: >> > >> > >> >git clone https://github.com/fossfreedom/alternative-toolbar >> > >> >cd alternative-toolbar >> > >> >dch -i >> > >> > add the new upstream version and change log >> > >> >cd .. >> > >> >cd rhythmbox-plugin-alternative-toolbar-0.14.1 >> > >> >dh_make --createorig >> > >> >debuild -S -k0x[gpg key] >> > >> > >> >should I miss out the dh_make --createorig step that creates the package >> tarball but instead download the GitHub tag tarball (.tar.gz file) and >> rename it >appropriately? >> >> >> yes. >> >> download the tarball (uscan does this for you when you have a watch file) >> >> >> call it something like >> >> rhythmbox-plugin-alternative-toolbar_0.14.1.orig.tar.gz >> >> >> extract, copy the debian directory inside (if you start to have a >> separate branch) >> >> debuild -S or dpkg-buildpackage -S or whatever >> >> live happy :) >> >> >Then within the folder rhythmbox-plugin-alterative-toolbar-0.14.1 delete >> the files and folders you have recommended that should not packaged? >> >> nope, they are a few kb of files, you can leave them >> >> >I thought debuild would then complain because the package contents no >> longer match the tarball contents - or is there a debuild option here that >> can help? >> >> >> this is true for modifications, not for deletions. >> >> >thanks >> >> >> yw >> >> G. >> >> >> On 6 November 2015 at 12:35, Gianfranco Costamagna < >> costamagnagianfra...@yahoo.it> wrote: >> >> Hi, >> > >> > >> >>I've never heard of pyflakes and pyflakes3 - so thanks for introducing >> me to these tools. I've run these and they no longer throw errors out. >> > >> > >> >wonderful >> >>I've run your PEP8 command. The vast
Bug#804699: rhythmbox-plugins: Please demote the Depends to Recommends
Package: rhythmbox-plugins Version: 3.2.1-1 Severity: wishlist The problem with the current relationship for the plugins is that one needs to install all the plugins. For example, zeitgeist. That, afaik, is not even a GNOME project. I'd suggest you put all current Depends into Recommends. This, for generic users, will pull all the standard packages. Where as for us, it'll still allow flexibility to hand pick some -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#683848: pbuilder: revised binNMU patches for git am
On Mon, Nov 09, 2015 at 10:33:28AM +0100, Andreas Beckmann wrote: > On 2015-07-22 14:48, Andreas Beckmann wrote: > > I attach revised and rebased patches for adding binNMU support that > > should apply cleanly with git am. > > The patches still apply fine to current git, although there is a minor > issue: > > A binNMU with --distribution experimental ends up in sid due to a > distribution override for experimental in pbuilder-checkparams which is > "required for raw pbuilder (create/update) only" but applied always > . I just uploaded 0.220 without any of this, but this will be definitely something in 0.221, also given the load of requests :) I'll take a look at all of the patches in the coming weeks. Thanks for the patches! -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://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#736824: New release of POSIX manpages
On Tue, 10 Nov 2015 23:30:12 +0900 OGAWA Hirofumiwrote: > On Mon, 27 Jan 2014 09:33:55 +0100 Francesco Paolo Lovergine > wrote: > > Package: manpages-posix > > Version: 2.16-1 > > Severity: wishlist > > I wrote script to help package update. This makes manpages-posix-2.17 > with patched debian/ for 2.17. > > Please update this package. This update fixes bugs (#470841, #522292, #705032). And maybe (#520162)? -- OGAWA Hirofumi
Bug#795719: Adopting phantomjs?
On Thu, 15 Oct 2015 01:05:11 +0100 Tim Retoutwrote: > Hello Dominik! > > On 14 October 2015 at 12:33, Dominik George wrote: > > > As I am now sitting here at my dayjob with resources to get this package > > straight, can you please update me on the current status and what I can > > do to get a working version into Debian real soon? Do we still fix the > > old package, or should I start creating a new package for 2.0.0 to > > replace this? If not, what is left to test and fix to make the package > > fit for sid and then create a backport after migration to testing? > > > > My take on this is not positive, as my understanding now is that phantomjs > upstream itself is under-resourced compared to the scale of the problem > they're tackling. :/ In a similar position at my day job, we are migrating > our test suite from ghostdriver to chromedriver, which is both faster and > maintained by the Chromium team. If you are using a lot of the Javascript > API that phantomjs provides, I can imagine that this would not be possible, > however. > > To fix the package in Debian, you need to get some v2.x version working, > because this is the only route to building with system Qt and webkit. So > far, however, takaki says the git snapshot doesn't compile. > I also need to do this for $dayjob and will have a go over the next few hours. Please catch me on IRC if there's any special details that I should know. > Because I've found a workaround for $dayjob, I'm not actively working on > this any more, I'm afraid. > Yes, my current workaround is to just use 'xvfb-run karma --browsers Chrome' and be done with it. Much easier than using "drivers", which are usually slightly different from what end-users run, anyhow. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
Bug#804596: pdns-server: New version fails to sign axfrs
* James Cloos[151110 18:46]: > > "PvD" == Peter van Dijk writes: > > PvD> geo did not change its name - geoip is a different backend. > > Sorry for forgetting that. I now recall that again. So I should have > written about the one backend replacing the other, and as such apt left > the old one there. > > The geoip deb needs to have an annotation that it replaces the geo deb > given that there is no 3.4.7 deb for geo. > > That should have been done when 3.4.6-3 was uploaded, based on the > files currently in pool. The thing is: the geoip backend does not replace the geo backend. If you previously had config for the geo backend, it won't be compatible. Therefore, -geoip not replacing -geo is intentional and IMO correct. What could be added is a Conflicts: pdns-backend-geo on pdns-server, but even that is not actually true per the Conflicts specification. It's simply 'no longer available'. (And it's noted in the NEWS.Debian file.) -- ,''`. Christian Hofstaedtler : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `-
Bug#800681: Esc+ doesn't work twice in a row
On 4 November 2015 at 17:29, Arturo Borrero Gonzalezwrote: > On 4 November 2015 at 17:27, Benno Schulenberg wrote: >> >> What does 'echo $TERM' say in your xfce4-terminal? >> > > % echo $TERM > xterm > Hi, What are your plans for this bug? are you reporting upstream or something? Might I expect a fix? thanks, best regards. -- Arturo Borrero González
Bug#694634: [Reportbug-maint] Bug#694634: reportbug dies on "Querying Debian BTS ..." in case of server error
control: reassign -1 python-debianbts > File "/usr/lib/pymodules/python2.7/debianbts.py", line 179, in get_status > reply = server.get_status(*nr) > File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 545, in > __call__ > return self.__r_call(*args, **kw) > File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 567, in > __r_call > self.__hd, self.__ma) > File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 430, in > __call > timeout = self.timeout) > File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 318, in call > raise HTTPError(code, msg) > SOAPpy.Errors.HTTPError: to fix this, python-debianbts needs updating in stable, reassigning. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi
Bug#804703: gnome-keyring: The race with SessionManager initialization
Package: gnome-keyring Version: 3.18.2-1 Severity: normal Hi, When I start gnome-session (not sure if startx is important to reproduce) by $ startx Current gnome-keyring has the race with org.gnome.SessionManager initialization of gnome-session. Because dbus doesn't seem to make the name available to others immediately. The sequence of the race is: gnome-session gnome-keyring .SessionManager init run autostart apps start by autostart call .SessionManager.Setenv call .SessionManager.ClientPrivate .SessionManager available This race becomes the cause of random Setenv failure for SSH_AUTH_SOCK for example like following. ** Message: couldn't register in session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files To fix this, the attached patch starts to watch .NameOwnerChanged before calling .SessionManager. With this, if .SessionManager is not available yet, callings are done via .NameOwnerChanged notification. Then, after makes sure calling of .SessionManager was done, this removes watch of .NameOwnerChanged. -- System Information: Debian Release: stretch/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.24 (SMP w/8 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages gnome-keyring depends on: ii dbus-x11 1.10.2-1 ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii gcr 3.18.0-1 ii libc62.19-22 ii libcap-ng0 0.7.7-1 ii libcap2-bin 1:2.24-12 ii libgck-1-0 3.18.0-1 ii libgcr-base-3-1 3.18.0-1 ii libgcrypt20 1.6.4-3 ii libglib2.0-0 2.46.1-2 ii p11-kit 0.23.1-3 ii pinentry-gnome3 0.9.6-4 Versions of packages gnome-keyring recommends: ii libpam-gnome-keyring 3.18.2-1 gnome-keyring suggests no packages. -- no debconf information -- OGAWA HirofumiCurrent gnome-keyring has the race with org.gnome.SessionManager initialization of gnome-session. Because dbus doesn't make the name available to others immediately. The sequence of the race is: gnome-session gnome-keyring .SessionManager init run autostart apps start by autostart call .SessionManager.Setenv call .SessionManager.ClientPrivate .SessionManager available This race becomes the cause of random Setenv failure for SSH_AUTH_SOCK for example like following. ** Message: couldn't register in session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files To fix this, this starts to watch .NameOwnerChanged before calling .SessionManager. With this, if .SessionManager is not available yet, callings are done via .NameOwnerChanged notification. Then, after makes sure calling of .SessionManager was done, this removes watch of .NameOwnerChanged. --- daemon/dbus/gkd-dbus-environment.c |9 ++- daemon/dbus/gkd-dbus-session.c | 89 ++-- daemon/dbus/gkd-dbus.c |1 3 files changed, 92 insertions(+), 7 deletions(-) diff -puN daemon/dbus/gkd-dbus-environment.c~session-race-fix daemon/dbus/gkd-dbus-environment.c --- gnome-keyring-3.18.2/daemon/dbus/gkd-dbus-environment.c~session-race-fix 2015-10-29 20:37:32.812933216 +0900 +++ gnome-keyring-3.18.2-hirofumi/daemon/dbus/gkd-dbus-environment.c 2015-10-29 20:38:12.196871701 +0900 @@ -103,6 +103,7 @@ on_watch_environment (gpointer data, gpo void gkd_dbus_environment_init (GDBusConnection *conn) { + static gboolean watch_installed = FALSE; const gchar **envp; /* @@ -114,6 +115,10 @@ gkd_dbus_environment_init (GDBusConnecti for (; *envp; ++envp) setenv_request (conn, *envp); - gkd_util_watch_environment (on_watch_environment, g_object_ref (conn), -(GDestroyNotify) g_object_unref); + if (!watch_installed) { + watch_installed = TRUE; + gkd_util_watch_environment (on_watch_environment, + g_object_ref (conn), + (GDestroyNotify) g_object_unref); + } } diff -puN daemon/dbus/gkd-dbus-session.c~session-race-fix daemon/dbus/gkd-dbus-session.c --- gnome-keyring-3.18.2/daemon/dbus/gkd-dbus-session.c~session-race-fix
Bug#804704: ITP: python-munch -- A dot-accessible dictionary similar to JavaScript objects
Package: wnpp Severity: wishlist Owner: Clint Byrum* Package name: python-munch Version : 2.0.4 Upstream Author : Rotem Yaari * URL : https://github.com/infinidat/munch * License : MIT Programming Lang: Python Description : A dot-accessible dictionary similar to JavaScript objects Munch is a fork of David Schoonover’s Bunch package, providing similar functionality. 99% of the work was done by him, and the fork was made mainly for lack of responsiveness for fixes and maintenance on the original code. Munch is a dictionary that supports attribute-style access, a la JavaScript. I intend to maintain this in the context of the Debian Python Modules Team.
Bug#804712: ITP: pd-nusmuk -- a random collection of useful Pd objects
Package: wnpp Severity: wishlist Owner: IOhannes m zmoelnig* Package name: pd-nusmuk Version : 1.2 Upstream Author : * URL : https://puredata.info * License : GPL Programming Lang: Pd, C Description : a random collection of useful Pd objects The nusmuk library contains object targeted at high-quality audio synthesis like band-limited synthesizers, audio filters and effects and interpolating table lookups. It also includes a number of general purpose utilities, ranging from simple shorthand abstractions to higher mathematics (random generators). I intend to maintain this under the pkg-multimedia-maintainers umbrella.
Bug#803997: transition: polarssl
On 09/11/15 20:49, James Cowgill wrote: > Hi, > > On Mon, 2015-11-09 at 19:19 +0100, Emilio Pozuelo Monfort wrote: >> On 04/11/15 04:02, James Cowgill wrote: >>> Package: release.debian.org >>> User: release.debian@packages.debian.org >>> Usertags: transition >>> Severity: normal >>> Forwarded: https://release.debian.org/transitions/html/auto-polarssl.html >>> X-Debbugs-CC: polar...@packages.debian.org >>> >>> Hi, >>> >>> polarssl needs a library transition. The name of the upstream project >>> changed to 'mbedtls' so the SONAME has become 'libmbedtls9'. I've kept >>> the name of the dev package as 'libpolarssl-dev' for the 1.3 series so >>> every package doesn't need to be changed. >> >> Shouldn't there be a new libmbedtls-dev package, with libpolarssl-dev >> becoming a >> transitional one? >> >> Shouldn't the source be renamed? > > Earlier this year (in 1.3.10) upstream renamed the project mbedTLS. In > the 1.3 series they changed the soname, but not the API (ie all the > headers, functions, etc are still called "polarssl"). > > A few months later they released 2.0 which completely changed the API > by renaming all the functions and doing various cleanups to the API > which would brake many programs. > > The new 2.0 series is in NEW right now and called 'mbedtls' and > contains a libmbedtls-dev package. > > I didn't want to rename the dev package since it would end up > conflicting with the new 2.0 series and although the "brand" name is > mbedTLS, it still follows polarssl's API. Makes sense. >>> The new version of polarssl fixes a grave security bug (#801413). I >>> havn't got a response from the package maintainer at all in dealing >>> with this so I NMUed the version currently in experimental. >> >> Doing this transition as a NMU seems a bit odd to me. Though hijacking the >> package seems a bit premature since that bug was opened only a month ago. >> If you renamed the source, then maybe you could get away with it :p > > Okay sorry I didn't mean to hijack anyone's package, I was just trying > to fix this security bug affecting one of my packages and nothing > seemed to be happening on it. Although my upload of mbedtls 2 does now > feel like a bit of a hijack :/ No problem. Such a security sensitive package should be well maintained, by someone who has the time to take care of security uploads to (old)stable. So I'd say go ahead with that, and if the previous maintainer wants to help, then that's great. > Thinking about this, I could probably avoid this transition by waiting > for mbedtls to pass NEW, porting all the rdeps, and then having > polarssl removed from the archive. This would be the "end" goal anyway. I'd prefer that. We can let polarssl get auto-removed from testing (or I may just remove it together with the rdeps). As for stable, if the package is FUBAR then you can request a removal from there in a separate bug. > This transition is effectively a temporary fix since I don't know how > long that will take, and in the mean time there will be a grave > security bug affecting polarssl. > > If you're wondering why a transition has to happen to fix this bug at > all, upstream basically said "do not try to backport any of these > commits" when I asked them about the security bug (see some of the > links in #801413). Ack. Cheers, Emilio
Bug#804711: ITP: pd-puremapping -- Pd library for complex data mappings
Package: wnpp Severity: wishlist Owner: IOhannes m zmoelnig* Package name: pd-puremapping Version : 1.1 Upstream Author : Cyrille Henry * URL : https://puredata.info * License : GPL Programming Lang: Pd Description : Pd library for complex data mappings This collection of abstractions for Pure Data (Pd)are made to facilitate the use of sensors and to create complex relations between input and output of a dynamic system. Puremapping is based on the (discontinued) 'la-kitchen' library, and the 'mapping' library. Most object of puremapping should be compatible with the 'mapping' lib object. I intend to maintain this under the pkg-multimedia-maintainers umbrella.
Bug#804707: wpa: CVE-2015-5310: wpa_supplicant unauthorized WNM Sleep Mode GTK control
Source: wpa Version: 2.2-1 Severity: important Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for wpa. CVE-2015-5310[0]: wpa_supplicant unauthorized WNM Sleep Mode GTK control 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-2015-5310 Regards, Salvatore
Bug#804709: iptraf: please add support for predictable interface names as of udev >= 197
Package: iptraf Version: 3.0.0-8.1 Severity: wishlist Tags: patch Patch attached. -- System Information: Debian Release: stretch/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages iptraf depends on: ii libc62.19-22 ii libncurses5 6.0+20151024-2 ii libtinfo56.0+20151024-2 iptraf recommends no packages. iptraf suggests no packages. -- no debconf information -- Antonio Terceirodiff -u iptraf-3.0.0/src/ifaces.c iptraf-3.0.0/src/ifaces.c --- iptraf-3.0.0/src/ifaces.c +++ iptraf-3.0.0/src/ifaces.c @@ -32,7 +32,7 @@ #include "error.h" extern int accept_unsupported_interfaces; -#define NUM_SUPPORTED_IFACES 28 +#define NUM_SUPPORTED_IFACES 30 extern int daemonized; @@ -40,7 +40,7 @@ { "lo", "eth", "sl", "ppp", "ippp", "plip", "fddi", "isdn", "dvb", "pvc", "hdlc", "ipsec", "sbni", "tr", "wvlan", "wlan", "sm2", "sm3", "pent", "lec", "brg", "tun", "tap", "cipcb", "tunl", "vlan", "ath", -"ra" +"ra", "en", "wl" }; char *ltrim(char *buf) diff -u iptraf-3.0.0/src/packet.c iptraf-3.0.0/src/packet.c --- iptraf-3.0.0/src/packet.c +++ iptraf-3.0.0/src/packet.c @@ -78,6 +78,8 @@ case ARPHRD_ETHER: if (strncmp(ifname, "eth", 3) == 0) result = LINK_ETHERNET; + else if (strncmp(ifname, "en", 2) == 0) +result = LINK_ETHERNET; else if (strncmp(ifname, "ath", 3) == 0) result = LINK_ETHERNET; else if (strncmp(ifname, "plip", 4) == 0) @@ -91,7 +93,7 @@ else if (strncmp(ifname, "ipsec", 5) == 0) result = LINK_ETHERNET; else if ((strncmp(ifname, "wvlan", 5) == 0) - || (strncmp(ifname, "wlan", 4) == 0)) + || (strncmp(ifname, "wl", 2) == 0)) result = LINK_ETHERNET; else if ((strncmp(ifname, "sm2", 3) == 0) || (strncmp(ifname, "sm3", 3) == 0)) diff -u iptraf-3.0.0/src/promisc.c iptraf-3.0.0/src/promisc.c --- iptraf-3.0.0/src/promisc.c +++ iptraf-3.0.0/src/promisc.c @@ -81,6 +81,7 @@ */ if ((strncmp(buf, "eth", 3) == 0) || + (strncmp(buf, "en", 2) == 0) || (strncmp(buf, "ath", 3) == 0) || (strncmp(buf, "fddi", 4) == 0) || (strncmp(buf, "tr", 2) == 0) || signature.asc Description: PGP signature
Bug#804708: wpa: CVE-2015-5314 CVE-2015-5315: EAP-pwd missing last fragment length validation
Source: wpa Version: 2.2-1 Severity: important Tags: security upstream patch fixed-upstream Hi, the following vulnerabilities were published for wpa. CVE-2015-5314[0]: hostapd: EAP-pwd missing last fragment length validation CVE-2015-5315[1]: wpa_supplicant: EAP-pwd missing last fragment length validation If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-5314 [1] https://security-tracker.debian.org/tracker/CVE-2015-5315 Regards, Salvatore
Bug#804710: wpa: CVE-2015-5316: EAP-pwd peer error path failure on unexpected Confirm message
Source: wpa Version: 2.3-1 Severity: important Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for wpa. CVE-2015-5316[0]: EAP-pwd peer error path failure on unexpected Confirm message 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-2015-5316 Regards, Salvatore
Bug#789077: ruby2.2 transition: about to switch the default in unstable
On 09/11/15 10:21, Emilio Pozuelo Monfort wrote: > On 08/11/15 23:44, Christian Hofstaedtler wrote: >> FTR, we're now down to just subversion, uwsgi and zeroc-ice. >> >> James and Antonio are making some progress with subversion in >> #803589, but it appears to be more tricky (and upstream has no fix >> yet). >> >> zeroc-ice has an upstream fix, but the delta is too large for me to >> backport it as part of an NMU. >> >> Haven't heard back yet from the uwsgi team. > > Thanks for the update. > > You can make those bugs serious now as this is imminent. Let us know once > subversion is fixed. You can go ahead with the default switch. Cheers, Emilio
Bug#804702: ITP: ruby-state-machines -- Creating state machines for attributes on any Ruby class
Package: wnpp Severity: wishlist Owner: Abhijith PA* Package name: ruby-state-machines Version : 0.4.0 Upstream Author : Abdelkader Boudih Aaron Pfeifer * URL : https://github.com/state-machines/state_machines * License : MIT Programming Lang: Ruby Description : Creating state machines for attributes on any Ruby class -- അഭിജിത്ത് signature.asc Description: OpenPGP digital signature
Bug#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
Hi, The bug still seem to be present, as tried with the most recent Jessie netboot image. [ ]netboot.tar.gz 01-Sep-2015 18:32 18M Following is the output from network-console at the time of issue: --8<---cut here---start->8--- ~ # fdisk -l /dev/sda Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: C89CD80E-7C84-42CD-BD07-ED7F424CBB73 Device Start End Sectors Size Type /dev/sda1 2048499711497664 243M Linux filesystem /dev/sda2 499712 8499199 7999488 3.8G Linux swap /dev/sda3 8499200 488396799 479897600 228.9G Linux filesystem ~ # fdisk -l /dev/sda3 Disk /dev/sda3: 228.9 GiB, 245707571200 bytes, 479897600 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Device Boot Start End Sectors Size Id Type /dev/sda3p1 2048 479897599 479895552 228.9G 83 Linux ~ # tail /var/log/syslog Nov 10 16:47:17 kernel: [ 69.492652] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-de...@redhat.com Nov 10 16:47:17 partman: No matching physical volumes found Nov 10 16:47:17 partman: Reading all physical volumes. This may take a while... Nov 10 16:47:17 partman: No volume groups found Nov 10 16:47:17 partman-lvm: No volume groups found Nov 10 16:47:18 kernel: [ 70.632238] sda: sda1 sda2 sda3 Nov 10 16:47:18 kernel: [ 70.749050] Adding 3999740k swap on /dev/sda2. Priority:-1 extents:1 across:3999740k FS Nov 10 16:47:18 partman: mke2fs 1.42.12 (29-Aug-2014) Nov 10 16:47:18 partman: mke2fs 1.42.12 (29-Aug-2014) Nov 10 16:47:18 partman: Found a dos partition table in /dev/sda3 # ps |grep ext 8529 root 4668 S{50format_ext3} /bin/sh /lib/partman/commit.d/50format_ext3 8559 root 6308 Slog-output -t partman --pass-stdout mkfs.ext4 /dev/sda3 8560 root 17260 Smkfs.ext4 /dev/sda3 --8<---cut here---end--->8--- To workaround in my case, I'd to SIGKILL the mkfs.ext4 process, and then had to do 'mkfs.ext4 -F /dev/sda3', and after that went back to debian-installer screen, and chose "Detect Disks" menu item, and now installation is going on. HTH -- Ashish SHUKLA “Yeah, sure. Babies learn their mother tongue by reading the great philosophers…“ (Pascal Bourguignon, comp.lang.lisp) Sent from my Emacs signature.asc Description: PGP signature
Bug#804626: override: libgsound0:libs/optional
Control: reassign -1 ftp.debian.org Control: retitle -1 override: libgsound0:libs/optional Am 10.11.2015 um 00:13 schrieb Ben Finney: > Package: libgsound0 > Version: 1.0.1-3 > Severity: minor > > Dear Maintainer, > > The section “gnome” is for packages that are “part of the GNOME > environment or closely integrated into it”. > > The package ‘libgsound0’ installs primarily a shared object library > for programs, not something that would be installed except as a > dependency of some other package providing a program. By the section > descriptions, this package belongs in the “libs” section. > > Please set the field “Section: libs”. > The deb says libs. So this needs to be fixed on the ftp-master side, thus re-assigning Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#804642: (no subject)
Hi Andreas, thx for this bug report. I think I have patch ready once I'll test it I'll ask sponsor for upload. Hopefully it's not going to be too long. BTW can you share what tool allowed you to discover this bug? -- |_|0|_| | |_|_|0| "Heghlu'Meh QaQ jajVam" | |0|0|0| kuLa - | gpg --keyserver pgp.mit.edu --recv-keys 0x58C338B3 3DF1 A4DF C732 4688 38BC F121 6869 30DD 58C3 38B3 signature.asc Description: PGP signature
Bug#804567: libaccounts-glib: FTBFS on s390x
Hello, Looking through the build log it looks like its the test case that is failing. Would you happen to know if DBus behaves different on the s390x compared to the other architectures? (E.g. is it particularly slow?) Diane
Bug#804701: fotoxx: userguide-en.html is in both fotoxx and fotoxx-common 15.11.1-2
Package: fotoxx Version: 15.11.1-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? aptitude Performing actions... (Reading database ... 698312 files and directories currently installed.) Preparing to unpack .../fotoxx_15.11.1-2_amd64.deb ... Unpacking fotoxx (15.11.1-2) over (14.10.2-1+b1) ... Preparing to unpack .../fotoxx-common_15.11.1-2_all.deb ... Unpacking fotoxx-common (15.11.1-2) over (14.10.2-1) ... dpkg: error processing archive /var/cache/apt/archives/fotoxx-common_15.11.1-2_all.deb (--unpack): trying to overwrite '/usr/share/doc/fotoxx/userguide-en.html', which is also in package fotoxx 15.11.1-2 Processing triggers for mime-support (3.59) ... Processing triggers for desktop-file-utils (0.22-1) ... Processing triggers for menu (2.1.47) ... Processing triggers for doc-base (0.10.6) ... Processing 1 changed doc-base file, 2 added doc-base files... Error while merging /usr/share/doc-base/kino-en with /usr/share/doc-base/kino-fr: format html already defined. Registering documents with scrollkeeper... Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: /var/cache/apt/archives/fotoxx-common_15.11.1-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: dpkg: dependency problems prevent configuration of fotoxx: fotoxx depends on fotoxx-common (= 15.11.1-2); however: Version of fotoxx-common on system is 14.10.2-1. dpkg: error processing package fotoxx (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: fotoxx Press Return to continue. * 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 *** -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages fotoxx depends on: ii dcraw 9.21-0.2+b2 ii fotoxx-common 14.10.2-1 ii libc6 2.19-22 ii libcairo2 1.14.4-1 ii libgcc1 1:5.2.1-23 ii libgdk-pixbuf2.0-0 2.32.1-1 ii libglib2.0-02.46.2-1 ii libgtk-3-0 3.18.2-1 ii libimage-exiftool-perl 10.05-1 ii liblcms2-2 2.6-3+b3 ii libpango-1.0-0 1.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libpng12-0 1.2.50-2+b2 ii libstdc++6 5.2.1-23 ii libtiff54.0.5-1 ii xdg-utils 1.1.1-1 Versions of packages fotoxx recommends: ii ufraw 0.20-3+b1 Versions of packages fotoxx suggests: pn brasero ii chromium [www-browser] 46.0.2490.71-1 ii dillo [www-browser] 3.0.5-1+b1 ii dwb [www-browser]20150419git-1 ii gimp 2.8.14-1.2 ii hugin2015.0.0~rc3+dfsg-1+b2 ii iceweasel [www-browser] 38.4.0esr-1 ii imagemagick 8:6.8.9.9-6 ii konqueror [www-browser] 4:15.08.2-1 ii lynx-cur [www-browser] 2.8.9dev6-4 ii midori [www-browser] 0.5.11-2 ii rawtherapee 4.2-4 ii uzbl [www-browser] 0.0.0~git.20120514-1.1 ii w3m [www-browser]0.5.3-25+b1 -- no debconf information
Bug#804596: pdns-server: New version fails to sign axfrs
> "PvD" == Peter van Dijkwrites: PvD> geo did not change its name - geoip is a different backend. Sorry for forgetting that. I now recall that again. So I should have written about the one backend replacing the other, and as such apt left the old one there. The geoip deb needs to have an annotation that it replaces the geo deb given that there is no 3.4.7 deb for geo. That should have been done when 3.4.6-3 was uploaded, based on the files currently in pool. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#804705: use smbcontrol in logrotate
Package: samba Version: 2:4.3.0+dfsg-2 That has been suggested on https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1385868 (the Ubuntu package had a bug after the upstart->systemd transition, which has been fixed now, the change might still make sense though) "using "smbcontrol all reload-config". This command doesn't return an error if the services aren't running." https://launchpadlibrarian.net/210929997/0001-Use-smbcontrol-for-log-rotation.patch Suggested logrotate script "/var/log/samba/log.smbd /var/log/samba/log.nmbd { weekly missingok rotate 7 sharedscripts postrotate smbcontrol all reload-config endscript compress notifempty }" Cheers, Sebastien Bacher
Bug#804591: [Pkg-iscsi-maintainers] Bug#804591: open-iscsi: iscsi_auto flag should use iscsistart --fwparam_network in addition to -b
On Mon, 9 Nov 2015, Christian Seiler wrote: > >> Btw. is there any way to test this in a VM? I don't have access to > >> the corresponding hardware that sets these values, so I can't > >> really test this myself. > > > > Luckily, you *can* do it entirely within qemu and ipxe with a few minor > > limitations. Figuring out how to do that is non-trivial, but I've managed > > my way through it. > > Oh great, I don't have time today anymore (I'm in time zone UTC+01, > so it's quite late here ;-)), but I'll take a look at it during > the next few days. https://gist.github.com/smoser/810d59f0dd580b1c1256 That docs a lot of it.
Bug#804567: libaccounts-glib: FTBFS on s390x
On 10/11/15 19:25, Diane Trout wrote: > Hello, > > Looking through the build log it looks like its the test case that is > failing. > Would you happen to know if DBus behaves different on the s390x compared to > the other architectures? (E.g. is it particularly slow?) Not AFAIK. Emilio
Bug#804521: Undefined Behavior cleared upstream
tags 804521 + upstream tags 804521 + fixed Jonathan Wakely cleared this issue upstream. See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56158.
Bug#696856:
I also have this issue on a fully updated jessie installation. postfix 2.11.3-1 postfix-mysql 2.11.3-1 spamass-milter0.3.2-1+b1 spamassassin 3.4.0-6 Ayke
Bug#804713: ITP: python-requestsexceptions -- Import exceptions from potentially bundled packages in requests
Package: wnpp Severity: wishlist Owner: Clint Byrum* Package name: python-requestsexceptions Version : 1.1.1 Upstream Author : James Blair * URL : https://pypi.python.org/pypi/requestsexceptions * License : Apache 2.0 Programming Lang: Python Description : Import exceptions from potentially bundled packages in requests The python requests library bundles the urllib3 library, however, some software distributions modify requests to remove the bundled library. This makes some operations, such as supressing the “insecure platform warning” messages that urllib emits difficult. This is a simple library to find the correct path to exceptions in the requests library regardless of whether they are bundled. I plan to maintain this package in the context of the Debian Python Modules Team.
Bug#804706: qpdf 5.2.0 breaks ABI
Package: qpdf Version: 5.2.0-1 Severity: grave Tags: upstream Justification: causes non-serious data loss qpdf 5.2.0 breaks ABI compatibility. I am releasing qpdf 6.0.0 and am uploading a new version of 5.2.0 that reverts the ABI change.
Bug#619545: pvcreate: man page should list dataalignment default
Matt Taggart wrote on 24 Mar 2011: [snip] The vgcreate(8) man page does list a default of 4 MB for --physicalextentsize but does it really use that as the default always FWIW: it does as of lvm 2.02.95-8/wheezy *t
Bug#411979: aptitude: can't suspend
On 2015-11-08 15:18 +, Manuel A. Fernandez Montecelo wrote: > Control: tags -1 + moreinfo > Any occurence since then? I cannot reproduce this now. Then again, things have changed quite a bit :-) For one thing, I almost always run aptitude in an X terminal emulator now; I think back when I reported this I still used a dedicated Linux VT. -- Please *no* private copies of mailing list or newsgroup messages. Rule 420: All persons more than eight miles high to leave the court.
Bug#804715: RFS: sfcgal/1.2.1
Package: sponsorship-requests Severity: normal Hello, I have just uploaded a new version of the library package sfcgal which fixes bug #804589 * Package name: sfcgal Version : 1.2.1-1~exp1 Upstream Author : Mickael Borne (IGN), Hugo Mercier (Oslandia), Vincent Mora (Oslandia), Olivier Courtin (Oslandia) * URL : http://www.sfcgal.org/ * License : LGPL-2+ Section : science Sources have been uploaded to alioth and are availabe via the following URL: git+ssh://git.debian.org/git/pkg-grass/sfcgal.git Regards Sven
Bug#789899: evolution-ews: Office 365 account creation unsuccessful
Package: evolution-ews Version: 3.18.0-3 Severity: grave Followup-For: Bug #789899 After a conversation with jelmer on IRC, it seems that this issue might not be related to -mapi after all. That being said, it is still clearly extant, even in the version in sid. I don't experience a hang; the Evolution client opens, but it refuses to actually add an EWS account. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-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 evolution-ews depends on: ii evolution 3.18.1-1 ii libatk1.0-0 2.18.0-1 ii libc6 2.19-22 ii libcairo-gobject2 1.14.2-2 ii libcairo2 1.14.2-2 ii libcamel-1.2-54 3.18.1-1 ii libebackend-1.2-10 3.18.1-1 ii libebook-contacts-1.2-2 3.18.1-1 ii libecal-1.2-19 3.18.1-1 ii libedata-book-1.2-253.18.1-1 ii libedata-cal-1.2-28 3.18.1-1 ii libedataserver-1.2-21 3.18.1-1 ii libedataserverui-1.2-1 3.18.1-1 ii libevolution3.18.1-1 ii libgdk-pixbuf2.0-0 2.32.1-1 ii libglib2.0-02.46.1-1 ii libgtk-3-0 3.18.2-1 ii libical1a 1.0.1-0.1 ii libjavascriptcoregtk-3.0-0 2.4.9-2+b1 ii libmspack0 0.5-1 ii libnspr42:4.10.9-2 ii libnss3 2:3.20-1 ii libpango-1.0-0 1.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libsecret-1-0 0.18.3-1 ii libsoup2.4-12.52.1-1 ii libsqlite3-03.9.1-2 ii libwebkitgtk-3.0-0 2.4.9-2+b1 ii libxml2 2.9.2+zdfsg1-4 evolution-ews recommends no packages. evolution-ews suggests no packages. -- no debconf information
Bug#804315: Seriously?
Joerg Jaspert dixit: >not official", thats just wrong. You may not like its maintainer, you >may not want that particular software and want to get your own. Thats >all fine, but this action is not. This becomes especially ridiculous when one considers that certain people/parties/cabals inside Debian, which some of the people involved this time may or may not belong to, deny other then-developers the ability to want a particular piece of software, instead of that one they wanted. Why is it that some people can declare other peoples’ work “not official” and thus less worth than their own, while that work is still used with official releases? Right. Debian, as a social ecosystem, isn’t a welcoming place any more. I just am surprised that not more people leave it. bye, //mirabilos -- “The final straw, to be honest, was probably my amazement at the volume of petty, peevish whingeing certain of your peers are prone to dish out on d-devel, telling each other how to talk more like a pretty princess, as though they were performing some kind of public service.” (someone to me, privately)
Bug#804714: jsurf-alggeo: new upstream version
Package: jsurf-alggeo Version: 0.1.4+ds-1 Severity: wishlist Hello Folks: A new upstream version for jsurf-alggeo is available. For the record, Jerome -- System Information: Debian Release: Jessie* APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.7-ckt11-amd64-mbp62 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages jsurf-alggeo depends on: ii antlr33.2-10 ii default-jre [java7-runtime] 2:1.7-52 ii libcommons-cli-java 1.2-3 ii libvecmath-java 1.5.2-5 ii openjdk-7-jre [java7-runtime] 7u85-2.6.1-6+deb8u1 ii openjdk-8-jre [java7-runtime] 8u66-b17-1~bpo8+1 ii oracle-java7-jdk [java7-runtime] 7u76 ii oracle-java8-jdk [java7-runtime] 8u40 jsurf-alggeo recommends no packages. Versions of packages jsurf-alggeo suggests: pn graphicsmagick-imagemagick-compat -- no debconf information
Bug#788708: iceweasel: GStreamer causes segmentation fault
On Mon, Nov 09, 2015 at 09:32:58PM +0100, Sebastian Dröge wrote: > On Mo, 2015-11-09 at 18:45 +0100, Agustin Martin wrote: > > Hi, gstreamer plugins maintainers > > > > I have unarchived this bug report to add more info on it. Not yet > > reopened it for jessie because I am not fully sure that is is the one > > to blame. > > > > I am having some problems in jessie similar to those reported in > > this > > bug report, although they are not yet as reproducible. > > > > Using iceweasel=38.4.0esr-1~deb8u1 and > > gstreamer1.0-plugins-bad+libgstreamer-plugins-bad1.0-0=1.4.4- > > 2.1+b1 I have been finding some problems about iceweasel sudden > > closure. I have build a personal gstreamer1.0-plugins-bad=1.4.4- > > 2.1.0.0+amd1 package including the patch that fixed this problem and > > it seemed to disappear. The reason why I am not yet reopening this > > bug report for jessie is that after reverting to current jessie > > versions (1.4.4-2.1(+b1)) I am not reproducing it, so I cannot > > discard that there is something else involved. > > That seems weird. Do you happen to have a backtrace of one of these > crashes still, ideally with debug symbols? Hi, It happened in a box where I do not have regular access. May be able to try again next weekend if I can still reproduce it. PS: I also unarchived this bug report because of other iceweasel bug report that seems to be exactly the same (should have really unarchived #797227). Just about to mail #799632 submitter cc'ing this unarchived bug report. Regards, -- Agustin
Bug#733993: loudmouth: please package github snapshot of loudmouth
Am 09.11.2015 um 20:23 schrieb Mikael Berthe: > Hi, > > We (the MCabber team) have released a new version of Loudmouth. > > Please see https://mcabber.com/files/loudmouth/ABOUT > or our announcement on the JDEV Jabber/XMPP mailing list: > http://mail.jabber.org/pipermail/jdev/2015-November/090136.html Thanks for getting in touch with us, Mikael. The latest loudmouth version we ship in Debian is 1.4.3 from [1]. Is you fork based on that? Since the old upstream website [2] is spam nowadays, does the project have a new website? The Debian package shipped a couple of patches [3]. As new upstream, you might have a look at incorporating those as you see fit. I haven't actually checked 1.5.1 yet, maybe this already happened. Cheers, Michael [1] ftp://ftp.gnome.org/pub/gnome/sources/loudmouth/ [2] http://www.loudmouth-project.org/ [3] http://anonscm.debian.org/viewvc/pkg-gnome/packages/unstable/loudmouth/debian/patches/ -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#804718: SIGABRT from typing/deleting characters
Package: plasma-workspace Version: 4:5.4.2-1+b1 Severity: important File: /usr/bin/krunner I think everything is 5.5, so this shouldn't be the mixed 5.4/5.5 crash. I have a shell script I'm trying to run called 'go-mysql'. As I was typing it, I made a typo, and it crashed krunner (not only from this script—seems to crash a lot...). Anyway, typing 'go-mys' s s... repeatedly crashes it. Attached is a log. Interesting, if I run `krunner` under valgrind, it *doesn't* crash, or even print errors. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (150, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0 (SMP w/8 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 plasma-workspace depends on: ii dbus-x111.10.2-1 ii frameworkintegration5.15.0-1+b1 ii gdb 7.10-1 ii kactivities 5.15.0-1 ii kde-cli-tools 4:5.4.2-1 ii kded5 5.15.0-1 ii kinit 5.15.0-1 ii kio 5.15.0-1 ii libc6 2.19-22 ii libcln6 1.3.4-1 ii libdbusmenu-qt5-2 0.9.3+15.10.20150604-1 ii libgcc1 1:5.2.1-23 ii libgps223.15-2 ii libice6 2:1.0.9-1+b1 ii libkf5activities5 5.15.0-1 ii libkf5auth5 5.15.0-1 ii libkf5baloo55.15.0+-1 ii libkf5bookmarks55.15.0-1 ii libkf5completion5 5.15.0-1 ii libkf5configcore5 5.15.0-1 ii libkf5configgui55.15.0-1 ii libkf5configwidgets55.15.0-1 ii libkf5coreaddons5 5.15.0-1 ii libkf5crash55.15.0-1 ii libkf5dbusaddons5 5.15.0-1 ii libkf5declarative5 5.15.0-1 ii libkf5globalaccel-bin 5.15.0-1 ii libkf5globalaccel5 5.15.0-1 ii libkf5guiaddons55.15.0-1 ii libkf5i18n5 5.15.0-1 ii libkf5iconthemes5 5.15.0-1 ii libkf5idletime5 5.15.0-1 ii libkf5itemviews55.15.0-1 ii libkf5jobwidgets5 5.15.0-1 ii libkf5js5 5.15.0-1 ii libkf5jsembed5 5.15.0-1 ii libkf5kdelibs4support5 5.15.0-1 ii libkf5kiocore5 5.15.0-1 ii libkf5kiofilewidgets5 5.15.0-1 ii libkf5kiowidgets5 5.15.0-1 ii libkf5networkmanagerqt6 5.15.0-1 ii libkf5newstuff5 5.15.0-1 ii libkf5notifications55.15.0-1 ii libkf5notifyconfig5 5.15.0-1 ii libkf5package5 5.15.0-1 ii libkf5plasma5 5.15.0-1 ii libkf5plasmaquick5 5.15.0-1 ii libkf5quickaddons5 5.15.0-1 ii libkf5runner5 5.15.0-1 ii libkf5screen6 4:5.4.2-1 ii libkf5service-bin 5.15.0+-1 ii libkf5service5 5.15.0+-1 ii libkf5solid55.15.0-1 ii libkf5su5 5.15.0-1 ii libkf5texteditor5 5.15.0-1 ii libkf5textwidgets5 5.15.0-1 ii libkf5wallet-bin5.15.0-1 ii libkf5wallet5 5.15.0-1 ii libkf5waylandclient54:5.4.2-1 ii libkf5waylandserver54:5.4.2-1 ii libkf5webkit5 5.15.0-1 ii libkf5widgetsaddons55.15.0-1 ii libkf5windowsystem5 5.15.0-1 ii libkf5xmlgui5 5.15.0-1 ii libkf5xmlrpcclient5 5.15.0-1 ii libksgrd7 4:5.4.2-1 ii libkworkspace5-54:5.4.2-1+b1 ii libpam0g1.1.8-3.1 ii libphonon4qt5-4 4:4.8.3-2 ii libplasma-geolocation-interface54:5.4.2-1+b1 ii libprocesscore7 4:5.4.2-1 ii libprocessui7 4:5.4.2-1 ii libqalculate5v5 0.9.7-9.1 ii libqt5core5a5.5.1+dfsg-6 ii libqt5dbus5 5.5.1+dfsg-6 ii libqt5gui5 5.5.1+dfsg-6 ii libqt5network5 5.5.1+dfsg-6 ii libqt5qml5 5.5.1-3 ii libqt5quick55.5.1-3 ii libqt5script5 5.5.1+dfsg-2 ii libqt5sql5 5.5.1+dfsg-6 ii
Bug#804719: cross-gcc-defaults: please add s390x to the targets
Package: cross-gcc-defaults Version: 0.9 Please add s390x to the TARGET_LIST while creating the source package. gcc-5-s390x-linux-gnu is in the archive… Sebastian
Bug#804351: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue
Thanks to all those that replied. Due to lack of time to debug this properly I just reverted to a jessie image via recovery mode: http://www.cyrius.com/debian/kirkwood/qnap/ts-219/recovery/ All is fine again... Cheers On 2015-11-10 21:36, Ian Campbell wrote: On Tue, 2015-11-10 at 01:08 +, Ben Hutchings wrote: On Mon, 2015-11-09 at 14:18 -0800, Martin Michlmayr wrote: > * Ian Campbell[2015-11-09 08:37]: > > It might be the same issue as this recent installation report: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804351 > > > > I've not had a chance to dig into what is going on there. Often this > > kind of thing turns out to be an upstream change to the modules > > (different config options, splitting modules into more fine grained > > parts) which requires tweaks to the kernel config, or initramfs -tools > > or to the kernel udebs for the installer. > > There was a report on the QNAP forum about a QNAP no longer booting > after an update. The logs says: > > [8.697480] sdb: sdb1 > [8.702144] sda: sda1 sda2 sda3 > [8.705613] sd 1:0:0:0: [sdb] Attached SCSI disk > [8.713159] sd 0:0:0:0: [sda] Attached SCSI disk > Begin: Loading essential drivers ... modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:NgpioTCmarvell,orion-gpio not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:NgpioTCmarvell,orion-gpio not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module platform:reg-dummy not found in modules.dep > done. > Begin: Running /scripts/init-premount ... done. > ... > [ and then the UUID is not found ] > > Any idea what these messages about modules.dep are about? All those modaliases correspond to devices whose drivers are built-in. So it's not surprising that they're not found in modules.dep, and I don't think this has anything to do with the failure. Indeed, I've been seeing them for a while and I don't believe they are anything more than a cosmetic issue. Ian.
Bug#794232: updated patch for 1.0.1-1
Hey Lazslo, I updated seamlik's patch to work with the 1.0.1 version of this package. It adds libzopfli1 and libzopfli-dev based on upstream's Makefile. We really need this for the android-tools work. I can upload a v1.0.1-1.1 as an NMU if you want, or just let you do it. .hc diff -Nru zopfli-1.0.1/debian/changelog zopfli-1.0.1/debian/changelog --- zopfli-1.0.1/debian/changelog 2015-10-22 16:54:35.0 +0200 +++ zopfli-1.0.1/debian/changelog 2015-11-10 20:53:36.0 +0100 @@ -1,3 +1,10 @@ +zopfli (1.0.1-2) UNRELEASED; urgency=low + + * New packages: libzopfli1 and libzopfli-dev + * Drop hardened_build.patch: No longer needed + + -- Kai-Chung YanFri, 31 Jul 2015 20:06:30 +0800 + zopfli (1.0.1-1) unstable; urgency=low * New upstream release. diff -Nru zopfli-1.0.1/debian/control zopfli-1.0.1/debian/control --- zopfli-1.0.1/debian/control 2015-10-22 16:45:52.0 +0200 +++ zopfli-1.0.1/debian/control 2015-11-10 20:52:13.0 +0100 @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Laszlo Boszormenyi (GCS) -Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~) +Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), dh-exec Standards-Version: 3.9.6 Homepage: https://github.com/google/zopfli @@ -14,3 +14,27 @@ compressor. This compressor takes more time (~100x slower), but compresses around 5% better than zlib and better than any other zlib-compatible compressor we have found. + +Package: libzopfli1 +Architecture: any +Section: libs +Depends: ${shlibs:Depends}, ${misc:Depends} +Description: zlib (gzip, deflate) compatible compressor library + Zopfli Compression Algorithm is a new zlib (gzip, deflate) compatible + compressor. This compressor takes more time (~100x slower), but compresses + around 5% better than zlib and better than any other zlib-compatible + compressor we have found. + . + This package contains the dynamic library version of zopfli. + +Package: libzopfli-dev +Architecture: any +Section: libdevel +Depends: libzopfli1 (= ${binary:Version}), ${misc:Depends} +Description: zlib (gzip, deflate) compatible compressor library - Development files + Zopfli Compression Algorithm is a new zlib (gzip, deflate) compatible + compressor. This compressor takes more time (~100x slower), but compresses + around 5% better than zlib and better than any other zlib-compatible + compressor we have found. + . + This package contains the development files. \ No newline at end of file diff -Nru zopfli-1.0.1/debian/libzopfli1.install zopfli-1.0.1/debian/libzopfli1.install --- zopfli-1.0.1/debian/libzopfli1.install 1970-01-01 01:00:00.0 +0100 +++ zopfli-1.0.1/debian/libzopfli1.install 2015-11-10 21:45:09.0 +0100 @@ -0,0 +1,3 @@ +#!/usr/bin/dh-exec + +libzopfli.so.* usr/lib/${DEB_HOST_MULTIARCH} \ No newline at end of file diff -Nru zopfli-1.0.1/debian/libzopfli1.links zopfli-1.0.1/debian/libzopfli1.links --- zopfli-1.0.1/debian/libzopfli1.links1970-01-01 01:00:00.0 +0100 +++ zopfli-1.0.1/debian/libzopfli1.links2015-11-10 21:45:09.0 +0100 @@ -0,0 +1,3 @@ +#!/usr/bin/dh-exec + +usr/lib/${DEB_HOST_MULTIARCH}/libzopfli.so.1.0.1 usr/lib/${DEB_HOST_MULTIARCH}/libzopfli.so.1 \ No newline at end of file diff -Nru zopfli-1.0.1/debian/libzopfli-dev.install zopfli-1.0.1/debian/libzopfli-dev.install --- zopfli-1.0.1/debian/libzopfli-dev.install 1970-01-01 01:00:00.0 +0100 +++ zopfli-1.0.1/debian/libzopfli-dev.install 2015-11-10 21:45:09.0 +0100 @@ -0,0 +1,4 @@ +#!/usr/bin/dh-exec + +libzopfli.ausr/lib/${DEB_HOST_MULTIARCH} +src/zopfli/*.h usr/include/zopfli \ No newline at end of file diff -Nru zopfli-1.0.1/debian/libzopfli-dev.links zopfli-1.0.1/debian/libzopfli-dev.links --- zopfli-1.0.1/debian/libzopfli-dev.links 1970-01-01 01:00:00.0 +0100 +++ zopfli-1.0.1/debian/libzopfli-dev.links 2015-11-10 21:45:09.0 +0100 @@ -0,0 +1,3 @@ +#!/usr/bin/dh-exec + +usr/lib/${DEB_HOST_MULTIARCH}/libzopfli.so.1.0.1 usr/lib/${DEB_HOST_MULTIARCH}/libzopfli.so \ No newline at end of file diff -Nru zopfli-1.0.1/debian/patches/generate-static-lib.patch zopfli-1.0.1/debian/patches/generate-static-lib.patch --- zopfli-1.0.1/debian/patches/generate-static-lib.patch 1970-01-01 01:00:00.0 +0100 +++ zopfli-1.0.1/debian/patches/generate-static-lib.patch 2015-11-10 20:57:56.0 +0100 @@ -0,0 +1,10 @@ +--- a/Makefile b/Makefile +@@ -26,6 +26,7 @@ zopfli: + libzopfli: + $(CC) $(ZOPFLILIB_SRC) $(CFLAGS) -fPIC -c + $(CC) $(ZOPFLILIB_OBJ) $(CFLAGS) -shared -Wl,-soname,libzopfli.so.1 -o libzopfli.so.1.0.1 ++ $(AR) rs libzopfli.a $(ZOPFLILIB_OBJ) + + # ZopfliPNG binary + zopflipng: diff -Nru zopfli-1.0.1/debian/patches/hardened_build.patch zopfli-1.0.1/debian/patches/hardened_build.patch --- zopfli-1.0.1/debian/patches/hardened_build.patch2015-10-22 16:48:38.0 +0200
Bug#804722: git-buildpackage: import-dsc creates impractical merge commits after new upstream releases
Package: git-buildpackage Version: 0.7.0 Severity: normal Dear Maintainer, import-dsc create merge commits instead of normal commits for the first Debian patch after a new upstream release. This is very impractical. These commits are continuous sources of conflicts and this makes doing rebasing operations (for example for cosmetic purposes or to add changelogs in the commit message like suggested in bug #577810) very time consuming or practically impossible for packages with longer histories. import-dsc will create an history like this: ``` * 244a2a6 (HEAD -> master, tag: debian/0.9b-2) Imported Debian patch 0.9b-2 * 82a9cf5 (tag: debian/0.9b-1.1) Imported Debian patch 0.9b-1.1 * 2531e71 (tag: debian/0.9b-1) Imported Debian patch 0.9b-1 |\ | * 255de2b (tag: upstream/0.9b, upstream) Imported Upstream version 0.9b * | a7bfdf7 (tag: debian/0.8b-1) Imported Debian patch 0.8b-1 |/ * ce22f3b (tag: upstream/0.8b) Imported Upstream version 0.8b ``` It should instead act like import-orig does in the normal case, creating an history like the following: ``` * 244a2a6 (HEAD -> master, tag: debian/0.9b-2) Imported Debian patch 0.9b-2 * 82a9cf5 (tag: debian/0.9b-1.1) Imported Debian patch 0.9b-1.1 * 2531e71 (tag: debian/0.9b-1) Imported Debian patch 0.9b-1 * xxx Merge tag 'upstream/0.9b' |\ | * 255de2b (tag: upstream/0.9b, upstream) Imported Upstream version 0.9b * | a7bfdf7 (tag: debian/0.8b-1) Imported Debian patch 0.8b-1 |/ * xxx Merge tag 'upstream/0.8b' * ce22f3b (tag: upstream/0.8b) Imported Upstream version 0.8b ``` In this way each Debian patch is represented by a normal commit and operations like cherry-picking and rebasing became feasible.
Bug#804717: plasma-widgets-addons: (fuzzy clock) copy current date/time into clipboard
Package: plasma-widgets-addons Version: 4:5.4.2-1 Severity: wishlist Tags: upstream Earlier versions of the fuzzy clock would let you right click and copy the current date or time in various formats to the clipboard so you could paste them easily. The menu would offer a lot of formats you could choose from but I'd be pretty happy with just copying the current time (12:34) and date (2015-11-10) or both together. I can't even begin to count how many times I've used this features so it would be highly appreciated. I think the normal clock would probably benefit from having it also. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/8 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 plasma-widgets-addons depends on: ii kdeplasma-addons-data 4:5.4.2-1 ii kpackagetool5 5.15.0-1 ii libc6 2.19-22 ii libkf5archive5 5.15.0-1 ii libkf5completion5 5.15.0-1 ii libkf5configcore5 5.15.0-1 ii libkf5configgui55.15.0-1 ii libkf5coreaddons5 5.15.0-1 ii libkf5i18n5 5.15.0-1 ii libkf5kiocore5 5.15.0-1 ii libkf5kiowidgets5 5.15.0-1 ii libkf5newstuff5 5.15.0-1 ii libkf5notifications55.15.0-1 ii libkf5plasma5 5.15.0-1 ii libkf5widgetsaddons55.15.0-1 ii libkf5windowsystem5 5.15.0-1 ii libkf5xmlgui5 5.15.0-1 ii libqt5core5a5.5.1+dfsg-6 ii libqt5gui5 5.5.1+dfsg-6 ii libqt5qml5 5.5.1-3 ii libqt5quick55.5.1-3 ii libqt5widgets5 5.5.1+dfsg-6 ii libstdc++6 5.2.1-23 ii plasma-dataengines-addons 4:5.4.2-1 ii plasma-framework5.15.0-1 ii plasma-workspace4:5.4.2-1+b1 ii qml-module-org-kde-draganddrop 5.15.0-1 ii qml-module-org-kde-kcoreaddons 5.15.0-1 ii qml-module-org-kde-kio 5.15.0-1 ii qml-module-qtgraphicaleffects 5.5.1-2 ii qml-module-qtwebkit 5.5.1+dfsg-2 plasma-widgets-addons recommends no packages. Versions of packages plasma-widgets-addons suggests: pn plasma-widget-kimpanel -- no debconf information
Bug#785924: wxwidgets3.0: Please update to GStreamer 1.x
On Sun, Nov 01, 2015 at 11:14:55AM +0200, Sebastian Dröge wrote: > On Sa, 2015-10-31 at 20:39 +, Olly Betts wrote: > > Status is stalled, essentially. > > > > I gather from what slomo said that the current patch isn't suitable > > for applying. > > The first remark is a minor memory leak, the second is just cleanup > (and usage of the correct API) but at this time has no functional > difference (but might in the future). I'd be happier not to leave potential timebombs around, but you haven't given enough information about this for me to address it... > The leak you can fix by adding a simple gst_caps_unref() for the caps > in that function. OK. > Does the patch work otherwise? If so, just get it in after adding that > one line mentioned above :) I haven't tried to test it yet - I've been short of time lately and it's a non-trivial amount of work to do so, and my understanding was that the patch wasn't suitable as-is. I'll try to find time to test it. Also happy for someone else to test the amended patch and NMU if it works, but please keep me in the loop to avoid duplicating effort. (If someone does NMU, you could usefully drop `--enable-sdl` in debian/rules to close #802770 - there's no corresponding BD so this doesn't affect the built result in a clean chroot). Cheers, Olly
Bug#800681: Esc+ doesn't work twice in a row
On Tue, Nov 10, 2015, at 20:10, Arturo Borrero Gonzalez wrote: > What are your plans for this bug? I was still waiting for your answer to this question: >>And when you start an xterm, and run there an unpatched nano, >>do Ctrl-Left/Right work there? I mean the program 'xterm', which opens an ugly terminal window. > are you reporting upstream or something? I am the current upstream maintainer. :) > Might I expect a fix? Probably yes. But there is a problem. Your xfce4-terminal generates for Ctrl-Right the same code as the pantheon-terminal for Ctrl-Down. So, when I accept this patch into nano, it would mean that on a pantheon-terminal both Ctrl-Right and Ctrl-Down do a 'nextword'. That's a bit weird. But more importantly, it would mean that I then can't give new meanings to Ctrl-Up and Ctrl-Down (which currently don't do anything special, just the same as Up and Down. Also, I've tried this on an old KDE Konsole, and that terminal produces 0x203 and 0x205 for Ctrl-Left and Ctrl-Right -- still other codes. Do all terminals produce different codes? I have to find out first. And I need to understand where these codes come from. I haven't been able to find them in the source of xfce4-terminal nor of pantheon-terminal. Nor are the defined anywhere in ncurses. So... do I simply have to try all kinds of terminals and add all those codes to nano? Puzzles... For now you can use your patched nano, no? Benno -- http://www.fastmail.com - Or how I learned to stop worrying and love email again