Bug#840720: installation-report: stretch/testing setup inside qemu/kvm with virt-manager
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.62
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
- -- Package-specific info:
Boot method: iso-img
Image version:
http://gensho.acc.umu.se/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 2016-10-13
Machine: kvm vm, see attachment
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev devtmpfs500520 0500520 0% /dev
tmpfs tmpfs 1020283420 98608 4% /run
/dev/vda1 xfs 11523072 3138444 8384628 28% /
tmpfs tmpfs 510132 68510064 1% /dev/shm
tmpfs tmpfs 5120 4 5116 1% /run/lock
tmpfs tmpfs 510132 0510132 0% /sys/fs/cgroup
tmpfs tmpfs 102024 12102012 1% /run/user/1000
tmpfs tmpfs 102024 4102020 1% /run/user/109
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [o]
Detect network card:[o]
Configure network: [o]
Detect CD: [o]
Load installer modules: [o]
Clock/timezone setup: [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives: [o]
Install base system:[o]
Install tasks: [o]
Install boot loader:[o]
Overall install:[o]
Comments/Problems:
This is actually not an installer-problem, but one with libvirt or virt-manager
respectively, there is fix necessary in order to be able to start up existing
virtual
machines:
This is the problem:
> Error starting domain: Requested operation is not valid: network 'default' is
> not active
>
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in
> cb_wrapper
> callback(asyncjob, *args, **kwargs)
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 127, in tmpcb
> callback(*args, **kwargs)
> File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in startup
> self._backend.create()
> File "/usr/lib/python2.7/dist-packages/libvirt.py", line 999, in create
> if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: Requested operation is not valid: network 'default' is not
> active
This is the fix:
> root@dop58:/home/remosrv# cd /etc/libvirt/qemu/networks/autostart
> root@dop58:/etc/libvirt/qemu/networks/autostart# ln -s ../default.xml
> default.xml
> root@dop58:/etc/libvirt/qemu/networks/autostart# ls -la
> total 4
> drwxr-xr-x 1 root root 22 Oct 10 13:48 .
> drwxr-xr-x 1 root root 40 Oct 10 13:45 ..
> lrwxrwxrwx 1 root root 14 Oct 10 13:48 default.xml -> ../default.xml
> root@dop58:/etc/libvirt/qemu/networks/autostart# cat default.xml
>
> default
>
>
>
>
>
>
>
>
>
> root@dop58:/etc/libvirt/qemu/networks/autostart# service libvirtd restart
I also disabled the bridge-netfilter, now I am able to log in to the host with
SSH,
see:
> $$ man sysctl.d
VM-configuration attached, also kernel-bootup messages [dmesg-output]
There is a message at bootup. saying that hardware-support for kvm is missing
inside the
guest, so this would most probably require nested virtualisation, the other
issue is,
that there is a 90 seconds grace-period at startup while systemd waits for
Network-Manager, which ist not really required inside a VM.
- --
Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.
Once you have filled out this report, mail it to sub...@bugs.debian.org.
==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20161003-00:06"
X_INSTALLATION_MEDIUM=cdrom
==
Installer hardware-summary:
==
uname -a: Linux stretchtst 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26)
x86_64
GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX -
82441FX PMC
[Natoma] [8086:1237] (rev 02) lspci -knn: Subsystem: Red Hat, Inc Device
[1af4:1100] lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB
PIIX3 ISA
[Natoma/Triton II] [8086:7000] lspci -knn: Subsystem: Red Hat, Inc Device
[1af4:1100] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB
PIIX3 IDE
[Natoma/Triton II
Bug#840719: apt command should have clean parameter shortcut to run apt-get clean
Package: apt Version: 1.0.9.8.3 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: -- (no /etc/apt/preferences present) -- -- (/etc/apt/sources.list present, but not submitted) -- -- System Information: Debian Release: 8.6 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=es_ES@euro, LC_CTYPE=es_ES@euro (charmap=ISO-8859-15) (ignored: LC_ALL set to es_ES@euro) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages apt depends on: ii debian-archive-keyring 2014.3 ii gnupg 1.4.18-7+deb8u3 ii libapt-pkg4.12 1.0.9.8.3 ii libc6 2.19-18+deb8u6 ii libgcc1 1:4.9.2-10 ii libstdc++6 4.9.2-10 apt recommends no packages. Versions of packages apt suggests: pn apt-doc ii aptitude0.6.11-1+b1 ii dpkg-dev1.17.27 ii python-apt 0.9.3.12 -- no debconf information -- .. //\/ e t . \/ i c i o u s ..
Bug#840575: [buildd-tools-devel] Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode
On Fri 2016-10-14 01:36:56 -0400, Johannes Schauer wrote: > - it is a feature of sbuild since version 0.67.0 (I corrected the wiki page >accordingly) to *not* require signing of the internal dummy repository (and >thus you don't need to run sbuild-update --keygen anymore) and that awesome, thanks for this improvement (and thanks for all your work on sbuild)! Regards, --dkg
Bug#839542: typo: Send/Que command to all matching filters
On Thu, Oct 13, 2016 at 11:29 PM, Andreas Cadhalpun wrote: > Control: forwarded -1 > https://ffmpeg.org/pipermail/ffmpeg-devel/2016-October/201062.html > > Hi Mathieu, > > On 01.10.2016 21:14, Mathieu Malaterre wrote: >> I do not believe this is proper english. Patch attached. > > Thanks for reporting this. I've forwarded the fix upstream together > with a couple of other spelling fixes. I hope you don't mind that. This is the only way to have it fixed in the long term, so definitely: thanks for doing it ! :)
Bug#840718: ITP: node-test -- (Un)CommonJS test runner
Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-de...@lists.debian.org * Package name: node-test Version : 0.6.0 Upstream Author : Irakli Gozalishvili (http://jeditoolkit.com) * URL : https://github.com/Gozala/test-commonjs/ * License : Expat Programming Lang: JavaScript Description : (Un)CommonJS test runner
Bug#840669: [pkg-gnupg-maint] Bug#840669: Need way to avoid agent, or reliable way to kill agent
Hi Ian-- Thanks for this note, there's a lot in here. On Thu 2016-10-13 12:47:14 -0400, Ian Jackson wrote: > The dgit test suite involves setting up a dummy home directory with > some dummy keys and making and verifying some dummy signatures. There > is one of these per test. > > When the test suite is run under adt-run --- adt-virt-schroot, the > agents are automatically started but nothing kills them. > > This results in problems: schroot cannot unmount the chroot and cannot > clean up properly. > > I haven't checked but I am pretty sure that if I run the test suite > natively with gnupg2, it will leak enormous numbers of gpg agent > processes. Right, i can see why this might be a problem :) Does your test suite delete its test homedirs after it is finished? If not, would you be willing to include removal of the test homedirs as part of the tests, or as a final post-test cleanup phase? I ask because upstream intends for gpg-agent and dirmngr to auto-terminate when their sockets are removed, and those patches have been backported into 2.1.15-4 (see debian/patches/0015-agent-Terminate-on-deletion-of-the-socket-file-Linux.patch and debian/patches/0016-dirmngr-Terminate-on-deletion-of-the-socket-file-Lin.patch ). However, hmm, this doesn't seem to work properly; i just tested with: export GNUPGHOME=$(mktemp -d) gpg-connect-agent 'getinfo pid' /bye rm -rf "$GNUPGHOME" sleep 1 pidof gpg-agent I've just reported this problem upstream: https://bugs.gnupg.org/gnupg/issue2756 One thing worth observing is that if the agent's socket is deleted, it will eventually terminate itself after a minute or two anyway. This will happen even without inotify (but obviously the inotify trigger should really work to automate cleanup on platforms that support inotify) > IMO: there should be a way to get gnupg2 to do everything synchronously; > that is, if it needs an agent, to spawn one which does not listen on a > socket, but rather just has an existing connection to its parent and > which will die when the parent does. This could potentially complicate the agent -- at the moment, i think the agent expects to be the only process dealing with $GNUPGHOME/private-keys-v1.d/, and that means that two gpg processes using this approach could potentially trample on each other. > Also gpg agent processes should automatically exit if their HOME > ceases to exist (or if they cease to be the process listening on their > socket for some other reason) yes, this is upstream's intended behavior, and it happens (after some delay), but it's not instantaneous. Getting the inotify stuff fixed will make it much closer to instantaneous. > This problem, and how to deal with it, should be better documented. > (I looked in gpg-agent(1). I searched for "agent" and didn't find > any information that looked helpful; I did find information that > suggests that `drmngr' may be troublesome too.) NB gpg-agent(1) > refers to gpg2(1) and gpgsm(1) which do not exist. The reference to gpg2(1) is an error, and i've sent a patch upstream to gnupg-devel. gpgsm(1) is correct, but you probably don't have the gpgsm package installed. > In particular, `gpgconf --kill gpg-agent' should be documented. Where would you like it documented? it's in gpgconf(1): --kill [component] Kill the given component. Components which support killing are gpg-agent and scdaemon. Components which don't support reload‐ ing are ignored. Note that as of now reload and kill have the same effect for scdaemon. If you can suggest what the text should say and where a reasonable person might look for it, i'll happily write a patch and encourage its adoption by upstream. > NB that I don't think that expecting the dgit test suite to run > `gpgconf --kill-agent' after every test is reasonable. Currently > there is _no_ code for running a specific positive command after > running a test. Given the nature of test suites and indeed the nature > of error handling on posix systems, it's not clear that such a thing > would be sensible. If you're not willing to do *anything* (including deletion of the temporary $GNUPGHOME or some sort of session termination event) upon completing the test suite, but before tearing down your builder instance, then i don't know if there's a solution. But at the moment i suspect getting the inotify stuff fixed is the sanest and simplest approach on the platform you and i probably care most about :) --dkg signature.asc Description: PGP signature
Bug#840716: RFS: dh-sysuser/0.2
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "dh-sysuser" * Package name: dh-sysuser Version : 0.2 Upstream Author : Dmitry Bogatov * Url : https://anonscm.debian.org/cgit/users/kaction-guest/dh-sysuser.git * Licenses: GPL-3+ Section : admin It builds those binary packages: * dh-sysuser To access futher information about this package, visit the following URL: http://mentors.debian.net/package/dh-sysuser Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/d/dh-sysuser/dh-sysuser_0.2.dsc Alternatively, you can access package debian/ directory via git from URL: https://anonscm.debian.org/cgit/users/kaction-guest/dh-sysuser.git More information about dh-sysuser can be obtained from https://anonscm.debian.org/cgit/users/kaction-guest/dh-sysuser.git Changes since last upload: * Remove empty 'debian/docs' file * Fix typo in 'debian/copyright' * Add dependency on perl, which is required for `deluser --remove-home' (Closes: #840469) * Delete user with --force flag, allowing removing users, which have running processed. Regards, Dmitry Bogatov
Bug#840097: sysprof ppc binaries removed
Control: severity -1 important Hello! The old powerpc binaries has now been removed from unstable. Porter assistance with identifying if this is a real issue or a testcase problem would be welcome. Regards, Andreas Henriksson
Bug#840717: make libquvi-scripts-0.9.pc discoverable during cross building
Package: libquvi-scripts-0.9 Version: 0.9.20131130-1.1 Tags: patch User: helm...@debian.org Usertags: rebootstrap Control: affects -1 + src:libquvi libquvi fails to cross build from source, because it cannot find libquvi-scripts-0.9.pc. During cross compilation, pkg-config does not consider /usr/lib/pkgconfig. So move the .pc file to /usr/share/pkgconfig as it really is architecture independent. Please consider applying the attached patch. Helmut diff --minimal -Nru libquvi-scripts-0.9.20131130/debian/changelog libquvi-scripts-0.9.20131130/debian/changelog --- libquvi-scripts-0.9.20131130/debian/changelog 2016-02-18 16:56:33.0 +0100 +++ libquvi-scripts-0.9.20131130/debian/changelog 2016-10-14 08:19:20.0 +0200 @@ -1,3 +1,10 @@ +libquvi-scripts (0.9.20131130-1.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Make pkg-config file discoverable to cross compilation (Closes: #-1) + + -- Helmut Grohne Fri, 14 Oct 2016 08:18:50 +0200 + libquvi-scripts (0.9.20131130-1.1) unstable; urgency=medium * Non-maintainer upload with maintainer permission. diff --minimal -Nru libquvi-scripts-0.9.20131130/debian/patches/pkgconfig.diff libquvi-scripts-0.9.20131130/debian/patches/pkgconfig.diff --- libquvi-scripts-0.9.20131130/debian/patches/pkgconfig.diff 1970-01-01 01:00:00.0 +0100 +++ libquvi-scripts-0.9.20131130/debian/patches/pkgconfig.diff 2016-10-14 08:21:03.0 +0200 @@ -0,0 +1,17 @@ +From: Helmut Grohne +Subject: move pkg-config file to /usr/share/pkgconfig + +During cross compilation /usr/lib/pkgconfig is not considered. +Index: libquvi-scripts-0.9.20131130/Makefile.am +=== +--- libquvi-scripts-0.9.20131130.orig/Makefile.am libquvi-scripts-0.9.20131130/Makefile.am +@@ -6,7 +6,7 @@ + SUBDIRS+= doc + endif + +-pkgconfigdir= $(libdir)/pkgconfig ++pkgconfigdir= $(datadir)/pkgconfig + pkgconfig_DATA= libquvi-scripts-0.9.pc + + .PHONY: doc test stamp_scripts ChangeLog VERSION diff --minimal -Nru libquvi-scripts-0.9.20131130/debian/patches/series libquvi-scripts-0.9.20131130/debian/patches/series --- libquvi-scripts-0.9.20131130/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ libquvi-scripts-0.9.20131130/debian/patches/series 2016-10-14 08:17:38.0 +0200 @@ -0,0 +1 @@ +pkgconfig.diff
Bug#840715: ispell FTCBFS: build system overrides maintainer supplied CC
Source: ispell Version: 3.4.00-5 Tags: patch User: helm...@debian.org Usertags: rebootstrap ispell fails to cross build from source, because the build system overrides the maintainer supplied cross compiler with the build architecture compiler. Please consider applying the attached patch. Helmut diff --minimal -Nru ispell-3.4.00/debian/changelog ispell-3.4.00/debian/changelog --- ispell-3.4.00/debian/changelog 2016-03-04 08:34:39.0 +0100 +++ ispell-3.4.00/debian/changelog 2016-10-14 08:11:38.0 +0200 @@ -1,3 +1,10 @@ +ispell (3.4.00-5.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: 0037-CC-from-environment.patch (Closes: #-1) + + -- Helmut Grohne Fri, 14 Oct 2016 08:08:00 +0200 + ispell (3.4.00-5) unstable; urgency=medium * Add 0035-Force-text-grep-in-munchlist.patch to pass the `-a' flag to grep diff --minimal -Nru ispell-3.4.00/debian/patches/0037-CC-from-environment.patch ispell-3.4.00/debian/patches/0037-CC-from-environment.patch --- ispell-3.4.00/debian/patches/0037-CC-from-environment.patch 1970-01-01 01:00:00.0 +0100 +++ ispell-3.4.00/debian/patches/0037-CC-from-environment.patch 2016-10-14 08:11:24.0 +0200 @@ -0,0 +1,24 @@ +From: Helmut Grohne +Subject: Use CC from environment + +Index: ispell-3.4.00/Makefile +=== +--- ispell-3.4.00.orig/Makefile ispell-3.4.00/Makefile +@@ -536,7 +536,7 @@ + + config.sh: config.X defhash.h local.h Makefile + set $(SHELLDEBUG); \ +- for var in BAKEXT BINDIR CC COUNTSUFFIX DEFDICT DEFHASH \ ++ for var in BAKEXT BINDIR COUNTSUFFIX DEFDICT DEFHASH \ + DEFLANG EXEEXT HASHSUFFIX INSTALL \ + LANGUAGES LIBDIR LIBES LINK LINT LINTFLAGS LOOK_XREF \ + MAKE_SORTTMP MAN1DIR MAN1EXT MAN45DIR MAN45EXT MAN45SECT MASTERHASH \ +@@ -548,6 +548,7 @@ + | sed -e 's/"[^"]*$$/'"'/" -e "s/=/='/" -e 's/\\"/"/g' \ + | sed -n -e '$$p'; \ + done > config.sh; \ ++ echo "CC='$(CC)'" >> config.sh; \ + echo "CFLAGS='$(CFLAGS)'" >> config.sh; \ + echo 'case "$$MAKE_SORTTMP" in "") \ + SORTTMP="-e /!!SORTTMP!!/s/=.*$$/=/";; *) SORTTMP=;; esac' \ diff --minimal -Nru ispell-3.4.00/debian/patches/series ispell-3.4.00/debian/patches/series --- ispell-3.4.00/debian/patches/series 2016-03-04 08:34:39.0 +0100 +++ ispell-3.4.00/debian/patches/series 2016-10-14 08:10:19.0 +0200 @@ -25,3 +25,4 @@ 0034-Fix-munchlist-failure.patch 0035-Force-text-grep-in-munchlist.patch 0036-Reproducible-hashes.patch +0037-CC-from-environment.patch
Bug#839701: #839701: native GTK3 print dialog crashes
On Fri, Oct 14, 2016 at 10:36:28AM +0800, Drew Parsons wrote: > Should be fixed in 5.2.4. Yeah, thanks. bts-link already told me yesterday :) and it's tagged pending already (for 5.3.0 alpha1 and 5.2.4 rc1). Regards, Rene
Bug#840714: bind9 FTCBFS: python3 dependency, missing --host flags, bad configure checks, etc
Source: bind9 Version: 1:9.10.3.dfsg.P4-10.1 Tags: patch User: helm...@debian.org Usertags: rebootstrap bind9 fails to cross build from source for lots of different reasons. It starts out with trying to execute the host architecture python3 (which is not installable as its postinst fails for too foreign architectures). Then there are lots of fiddly things that go wrong in ./configure and finally gost wasn't busted consistently leading to conflicting declarations. Please consider applying the attached patch or taking parts of it and requesting more information on why the rest is necessary. You can test cross compiling bind9 in unstable with the following sbuild invocation: export ac_cv_file__dev_random=yes sbuild -d sid --host=$DEB_HOST_ARCH --add-depends="libc-dev, libstdc++-dev" something.dsc The environment variable is needed (with the patch) for linux, kfreebsd and hurd and needs to be allowed in sbuild's environment_filter. It should transition to whatever replaces dpkg-cross. The --add-depends is necessary to work around #815172. Helmut diff --minimal -Nru bind9-9.10.3.dfsg.P4/debian/changelog bind9-9.10.3.dfsg.P4/debian/changelog --- bind9-9.10.3.dfsg.P4/debian/changelog 2016-07-02 14:34:12.0 +0200 +++ bind9-9.10.3.dfsg.P4/debian/changelog 2016-10-14 06:59:35.0 +0200 @@ -1,3 +1,16 @@ +bind9 (1:9.10.3.dfsg.P4-10.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: (Closes: #-1) ++ Annotate python3 dependency with :any ++ Let dh_auto_configure pass cross flags such as --host ++ 80_cross.diff: Enable cross compiling without --random-dev ++ Tell ./configure about openssl's features ++ export BUILD_CC ++ Consistently bust gost + + -- Helmut Grohne Fri, 14 Oct 2016 06:59:28 +0200 + bind9 (1:9.10.3.dfsg.P4-10.1) unstable; urgency=medium * Non-maintainer upload. diff --minimal -Nru bind9-9.10.3.dfsg.P4/debian/control bind9-9.10.3.dfsg.P4/debian/control --- bind9-9.10.3.dfsg.P4/debian/control 2016-05-04 01:40:36.0 +0200 +++ bind9-9.10.3.dfsg.P4/debian/control 2016-10-14 06:59:26.0 +0200 @@ -14,7 +14,7 @@ libcap2-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], libgeoip-dev (>= 1.4.6.dfsg-5), dpkg-dev (>= 1.16.1~), - python3, + python3:any, dh-systemd, autotools-dev, dh-autoreconf diff --minimal -Nru bind9-9.10.3.dfsg.P4/debian/patches/80_cross.diff bind9-9.10.3.dfsg.P4/debian/patches/80_cross.diff --- bind9-9.10.3.dfsg.P4/debian/patches/80_cross.diff 1970-01-01 01:00:00.0 +0100 +++ bind9-9.10.3.dfsg.P4/debian/patches/80_cross.diff 2016-10-14 07:20:49.0 +0200 @@ -0,0 +1,24 @@ +From: Helmut Grohne +Subject: improve configure's cross build support + +configure explicitly fails cross compilation when not passing --with-randomdev +even though it could just continue. In the non-cross case, it uses +AC_CHECK_FILE, which can be preseeded with a config cache. There is no reason +to fail here. + +Index: bind9-9.10.3.dfsg.P4/configure.in +=== +--- bind9-9.10.3.dfsg.P4.orig/configure.in bind9-9.10.3.dfsg.P4/configure.in +@@ -1009,11 +1009,6 @@ + + case "$use_randomdev" in + unspec) +- case "$cross_compiling" in +- yes) +- AC_MSG_RESULT(unspecified) +- AC_MSG_ERROR([ need --with-randomdev=PATH or --with-randomdev=no]) +- esac + case "$host" in + *-openbsd*) + devrandom=/dev/arandom diff --minimal -Nru bind9-9.10.3.dfsg.P4/debian/patches/series bind9-9.10.3.dfsg.P4/debian/patches/series --- bind9-9.10.3.dfsg.P4/debian/patches/series 2016-05-04 01:40:36.0 +0200 +++ bind9-9.10.3.dfsg.P4/debian/patches/series 2016-10-14 07:16:46.0 +0200 @@ -10,3 +10,4 @@ 34_prepare_native_pkcs11.diff 70_precise_time.diff 75_ctxstart_no_sighandling.diff +80_cross.diff diff --minimal -Nru bind9-9.10.3.dfsg.P4/debian/rules bind9-9.10.3.dfsg.P4/debian/rules --- bind9-9.10.3.dfsg.P4/debian/rules 2016-05-04 01:40:36.0 +0200 +++ bind9-9.10.3.dfsg.P4/debian/rules 2016-10-14 07:49:37.0 +0200 @@ -27,6 +27,10 @@ ifeq ($(DEB_HOST_ARCH_OS),kfreebsd) EXTRA_FEATURES=--disable-linux-caps --disable-threads endif +ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH)) +EXTRA_FEATURES += --with-ecdsa=yes --with-gost=yes +export BUILD_CC ?= cc +endif stamps/prepare: dh_testdir @@ -40,7 +44,7 @@ cp -r lib/dns lib/dns-pkcs11 patch -p1 < debian/patches/extra-add_native_pkcs11.diff # disable GOST, can't use openssl with native pkcs11 anyway - sed -i 's/HAVE_OPENSSL_GOST/GOSTBUSTERS/' lib/dns-pkcs11/*.[ch] + sed -i 's/HAVE_OPENSSL_GOST/GOSTBUSTERS/' lib/dns-pkcs11/*.[ch] lib/dns/dst_gost.h dh_autotools-dev_updateconfig dh_autoreconf @mkdir -p stamps @@ -50,10 +54,7 @@ dh_testdir
Bug#840713: ITP: node-ansi-font -- ANSI font styling utils
Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-de...@lists.debian.org * Package name: node-ansi-font Version : 0.0.2 Upstream Author : Irakli Gozalishvili (http://jeditoolkit.com) * URL : https://github.com/Gozala/ansi-font * License : Expat Programming Lang: JavaScript Description : ANSI font styling utils
Bug#840712: ITP: node-ex-parser -- parser for jison
Package: wnpp Severity: wishlist Owner: Pirate Praveen X-Debbugs-CC: debian-de...@lists.debian.org From https://github.com/zaach/lex-parser signature.asc Description: OpenPGP digital signature
Bug#840488: Bareos crashes on "status dir"
Hello guys, some news on this. The backups itself keep continuing, so the problem just hits the director i think. Greetings
Bug#840701: emacs25: FTBFS: tests fail or time out
"Aaron M. Ucko" writes: > Automated builds of emacs25 on Linux encountered test failures (and a > hang on arm64), as detailed at > > https://buildd.debian.org/status/logs.php?pkg=emacs25&ver=25.1%2B1-1 > > Could you please take a look? Definitely. I saw that earlier, and noticed at least one build-dep that's missing, though I don't know why my pdebuild run here didn't hit the same issue. In any case, I should have time to work on it this weekend. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#840702: emacs25: FTBFS on non-Linux: ALSA sound support requested but not found.
"Aaron M. Ucko" writes: > Please either conditionalize the use of --with-sound=alsa or > build-depend on the ALSA emulation library on these architectures. Certainly. I don't know kFreeBSD well, so do you know what the preferred solution might be there? It looks like these are the --with-sound options: yes no alsa oss bsd-ossaudio Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#840424: RFS: verilog-mode/0:20160910.debfc6d.vpo-1
On Fri, Oct 14, 2016 at 12:54 PM, Kiwamu Okabe wrote: > However, I can't see following web page: > > https://anonscm.debian.org/cgit/pkg-emacsen/pkg/verilog-mode.git/ I see the page, now! I think I should simply wait someone finding that. Thanks, -- Kiwamu Okabe at METASEPI DESIGN
Bug#840711: golang-github-appc-docker2aci: CVE-2016-8579
Source: golang-github-appc-docker2aci Version: 0.12.0+dfsg-1 Severity: grave Tags: security upstream patch Forwarded: https://github.com/appc/docker2aci/issues/203 Hi, the following vulnerability was published for golang-github-appc-docker2aci. CVE-2016-8579[0]: infinite loop in deps walking If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2016-8579 [1] https://github.com/appc/docker2aci/issues/203 [2] https://github.com/lucab/docker2aci/commit/54331ec7020e102935c31096f336d31f6400064f Regards, Salvatore
Bug#840575: [buildd-tools-devel] Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode
Hi, Quoting Daniel Kahn Gillmor (2016-10-13 00:31:28) > > On Wed, Oct 12, 2016 at 11:42:15PM +0200, Thomas Goirand wrote: > >> gpg: Invalid option "--pinentry-mode" > > … it sounds like sbuild should at least have declared a versioned > dependency on gnupg (>= 2.1), when --pinentry-mode was introduced. this is indeed a real bug. Thanks for reopening this so that I don't forget to handle this for my next upload. > Alternately, maybe the requirement to run --keygen could be relaxed? That would require some version detection mechanism I suppose. I don't think it is useful to have sbuild in stable be able to run with old gnupg as the next stable release will have the correct gnupg version available. So if the requirement is relaxed, then it is purely useful for sbuild in backports. I don't know if our current sbuild backporter Luca (in CC) would be willing to write such a patch, especially considering that - it is a feature of sbuild since version 0.67.0 (I corrected the wiki page accordingly) to *not* require signing of the internal dummy repository (and thus you don't need to run sbuild-update --keygen anymore) and that - the next stable release is not far away. Thanks! cheers, josch signature.asc Description: signature
Bug#840709: parted: Prevent crash resizing FAT with very deep directories
Package: parted Version: 3.2-16+b1 Severity: wishlist Tags: patch Dear Maintainer, Could you please apply the patch from upstream to prevent crash resizing FAT with very deep directories: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=6242ad71d855be62d99ec345e52393be86ca9900 The patch was applied in GParted live and confirmed to work well: https://bugzilla.gnome.org/show_bug.cgi?id=762448 Thank you very much. Steven -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages parted depends on: ii libc6 2.24-3 ii libparted23.2-16+b1 ii libreadline7 7.0-1 ii libtinfo5 6.0+20160917-1 parted recommends no packages. Versions of packages parted suggests: pn parted-doc -- no debconf information -- Steven Shiau Public Key Server PGP Key ID: 4096R/47CF935C Fingerprint: 0240 1FEB 695D 7112 62F0 8796 11C1 12DA 47CF 935C
Bug#840710: parted: Fix recognition of FAT file system after resizing
Package: parted Version: 3.2-16+b1 Severity: wishlist Tags: patch Dear Maintainer, Could you please apply the patch from upstream to fix recognition of FAT file system after resizing: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=c0d394abac4d6d2ce35c98585b6ecb33aea48583 This patch was applied in GParted live and confirmed to work well: https://bugzilla.gnome.org/show_bug.cgi?id=759916 Thank you very much. Steven -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages parted depends on: ii libc6 2.24-3 ii libparted23.2-16+b1 ii libreadline7 7.0-1 ii libtinfo5 6.0+20160917-1 parted recommends no packages. Versions of packages parted suggests: pn parted-doc -- no debconf information -- Steven Shiau Public Key Server PGP Key ID: 4096R/47CF935C Fingerprint: 0240 1FEB 695D 7112 62F0 8796 11C1 12DA 47CF 935C
Bug#840708: spykeviewer: Please support spyder 3.x
Package: spykeviewer Version: 0.4.4-1 Severity: important Dear Maintainer, the new spyder 3.x series, renamed the spyderlib python ,module into spyder Could you fix spykeviewer inorder to support it. The spyder 3.x is available into experimental. You can also replace python(3)-spyderlib with python(3)-spyder once it is done. thanks Frederic -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.7.0-1-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages spykeviewer depends on: ii python2.7.11-2 ii python-guidata1.7.6-1 ii python-guiqwt 3.0.3-1 ii python-matplotlib 1.5.3-1 ii python-neo0.3.3-2 ii python-nose 1.3.7-2 ii python-scipy 0.18.1-1 ii python-sphinx 1.4.8-1 ii python-spyder [python-spyderlib] 3.0.0+dfsg1-1~exp1 ii python-spyderlib 3.0.0+dfsg1-1~exp1 ii python-spykeutils 0.4.3-1 ii python-tables 3.2.2-3 Versions of packages spykeviewer recommends: ii ipython-qtconsole 4.2.1-1 ii libjs-jquery 1.12.4-1 ii libjs-underscore 1.8.3~dfsg-1 spykeviewer suggests no packages. -- no debconf information
Bug#840707: trietool is installed for the host architecture during cross compilation
Package: libdatrie1-bin
Version: 0.2.10-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:libthai src:swath
The packages listed above fail to cross build from source, because
executing trietool-2.0 fails. When satisfying their Build-Depends,
libdatrie1-bin is installed for the host architecture and thus no binary
from it can be executed. A solution to problem is marking libdatrie1-bin
Multi-Arch: foreign.
I believe that marking it Multi-Arch: foreign is correct, because its
inupts and outputs are processed in an architecture-agnostic way. For
instance, it specifically handles endianess when writing integers. I
also tried to run trietool on different architectures to see whether its
output would differ and my tests agree with the source code inspection.
Thus I think it really should be marked Multi-Arch: foreign.
Please consider applying the attached patch.
Helmut
diff --minimal -Nru libdatrie-0.2.10/debian/changelog
libdatrie-0.2.10/debian/changelog
--- libdatrie-0.2.10/debian/changelog 2016-02-01 16:08:51.0 +0100
+++ libdatrie-0.2.10/debian/changelog 2016-10-14 06:50:48.0 +0200
@@ -1,3 +1,10 @@
+libdatrie (0.2.10-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Mark libdatrie1-bin Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne Fri, 14 Oct 2016 06:50:19 +0200
+
libdatrie (0.2.10-2) unstable; urgency=medium
* Use system jquery.js for doc package [lintian].
diff --minimal -Nru libdatrie-0.2.10/debian/control
libdatrie-0.2.10/debian/control
--- libdatrie-0.2.10/debian/control 2016-02-01 16:08:51.0 +0100
+++ libdatrie-0.2.10/debian/control 2016-10-14 06:50:16.0 +0200
@@ -38,6 +38,7 @@
Section: misc
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
+Multi-Arch: foreign
Description: Programs for double-array trie library
Trie is a kind of digital search tree, an efficient indexing method with
O(1) time complexity for searching. Comparably as efficient as hashing,
Bug#840691: libgs9: security update DSA-3691-1 breaks zathura, evince, ... in jessie
Control: affects -1 security.debian.org Control: tags -1 + help Hi Francesco, On Thu, Oct 13, 2016 at 11:56:22PM +0200, Francesco Poli (wintermute) wrote: > Package: libgs9 > Version: 9.06~dfsg-2+deb8u3 > Severity: grave > Tags: security > Justification: renders package unusable > > Hello! > > I had a bad surprise today in jessie. > After the security update: > > [UPGRADE] libgs9:amd64 9.06~dfsg-2+deb8u1 -> 9.06~dfsg-2+deb8u3 > [UPGRADE] libgs9-common:amd64 9.06~dfsg-2+deb8u1 -> 9.06~dfsg-2+deb8u3 > > I was unable to use zathura or evince (maybe other PS viewers are > affected): > > $ zathura foo.eps > warning: Failed to loads bookmarks. > invalidaccess -7 > error: Rendering failed (page 1) > $ evince foo.eps > invalidaccess -7 > invalidaccess -7 > Segmentation fault > > After downgrading back to libgs9/9.06~dfsg-2+deb8u1 and > libgs9-common/9.06~dfsg-2+deb8u1, everything is back to normal > and the two PS viewers work again. > > What went wrong? > If this is indeed a regression (as it seems to be), please fix it > as soon as possible! This was indeed not spotted in my testing of the update for the DSA. The blame for this should solely go to myself (not the team). We should find the cause asap and find a fix. I can reproduce it with evince. Regards, Salvatore
Bug#840706: libdatrie FTCBFS: does not honour DEB_BUILD_OPTIONS=nocheck
Source: libdatrie Version: 0.2.10-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap libdatrie fails to cross build from source, because it runs tests even when running tests is disabled via DEB_BUILD_OPTIONS=nocheck. Tests are usually disabled, because running host architecture executables cannot be run (without an emulator). Please consider applying the attached patch. Helmut diff --minimal -Nru libdatrie-0.2.10/debian/changelog libdatrie-0.2.10/debian/changelog --- libdatrie-0.2.10/debian/changelog 2016-02-01 16:08:51.0 +0100 +++ libdatrie-0.2.10/debian/changelog 2016-10-14 06:28:47.0 +0200 @@ -1,3 +1,10 @@ +libdatrie (0.2.10-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Support DEB_BUILD_OPTIONS=nocheck. (Closes: #-1) + + -- Helmut Grohne Fri, 14 Oct 2016 06:28:31 +0200 + libdatrie (0.2.10-2) unstable; urgency=medium * Use system jquery.js for doc package [lintian]. diff --minimal -Nru libdatrie-0.2.10/debian/rules libdatrie-0.2.10/debian/rules --- libdatrie-0.2.10/debian/rules 2016-02-01 16:08:51.0 +0100 +++ libdatrie-0.2.10/debian/rules 2016-10-14 06:28:27.0 +0200 @@ -21,8 +21,10 @@ # No test for doc override_dh_auto_test-indep: +ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),) override_dh_auto_test-arch: $(MAKE) -C tests check +endif override_dh_auto_install-indep: $(MAKE) -C doc install DESTDIR=$(CURDIR)/debian/tmp
Bug#840472: apt-listbugs: [INTL:de] Updated German debconf translation
Francesco Poli: > Chris Leick wrote: > > Francesco Poli: > > > Chris Leick wrote: > > > > Hi Francesco, > > > > " -T : filtert nach Markierungen, die Sie sehen wollen.\n > > I basically know almost nothing about the German language, so I > apologize in advance, in case I am completely wrong. > But... why do you still translate "" as ""? Oups. Sorry. This mus be " -T : filtert nach Markierungen, die Sie sehen wollen.\n" (Abbreviation of Markierung) Regards, Chris
Bug#840424: RFS: verilog-mode/0:20160910.debfc6d.vpo-1
Hi Sean, I simply move the verilog-mode.git repo as following: $ slogin kiwamu-gu...@git.debian.org git.debian.org$ set -u git.debian.org$ umask 002 git.debian.org$ cd /git/pkg-emacsen/pkg git.debian.org$ mv /git/collab-maint/verilog-mode.git . Now I can clone the code from git repo: $ git clone git://anonscm.debian.org/pkg-emacsen/pkg/verilog-mode.git However, I can't see following web page: https://anonscm.debian.org/cgit/pkg-emacsen/pkg/verilog-mode.git/ Some one like setup-repository is needed to view the web page? Best regards, -- Kiwamu Okabe at METASEPI DESIGN
Bug#840646: [debian-mysql] Bug#840646: mariadb-10.0: please move mysql_installdb to core package
2016-10-13 23:48 GMT+03:00 Robie Basak : > Note that I have a note > (https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1612647) about > trying to keep binaries between MariaDB and MySQL synced, to try and > avoid the kind of error in that bug. I don't think that is in conflict > with this request at all, but it would probably be worth adding to a > list of rearrangements and Breaks/Replaces to add, then doing everything > at once. Agree -- Otto Kekäläinen https://keybase.io/ottok Seravo Oy and MariaDB Foundation
Bug#840680: [pkg-gnupg-maint] Bug#840680: dirmngr: Dirmngr not always responding
> Thanks for this report. it sounds frustrating! I hope we can debug it:
>
> is this "always not responding" or "sometimes not responding"? I
> haven't observed the same behavior with dirmngr myself, so i'm not sure
> how to best proceed...
>
I find it is 'sometimes'. To describe it, I use vlc to record a video of
my desktop, see https://www.youtube.com/watch?v=cOLuUKh-_nA
The video describes the problem, but the timestamp is not the same with
the log files I attached.
> this is definitely strange behavior! have you tried attaching strace to
> the dirmngr process to see what it's doing while it's not answering you?
> or have you tried increasing the logging of dirmngr to see what it's
> doing while it's not responding?
>
> if the process id of dirmngr is $DIRMNGR_PID, you can use:
>
> strace -o dirmngr.strace -f -tt -T -p $DIRMNGR_PID
>
I have attach a dirmngr.strace.
> to get an strace dump.
>
> You can increase the logging by adding these lines to
> ~/.gnupg/dirmngr.conf and then restarting dirmngr:
>
> log-file /tmp/dirmngr.log
> debug-level advanced
>
I have attach a dirmngr.log
In the dirmngr.log:
11:36:50 I launch dirmngr by `gpg-connect-agent --dirmngr /bye`
But this `gpg-connect-agent` is stuch.
11:38:20 I attach strace to dirmngr, and the `gpg-connect-agent`
returns.
11:39:52 I start second `gpg-connect-agent`, and stuck too
(In strace log, it seems dirmngr already writed to S.dirmngr)
11:40:15 I start third `gpg-connect-agent`, and the second returns.
Then I send `ctrl-c`
It seems no sensitive log, so I publish it to the BTS.
I don't know whether the config file is needed:
dirmngr.conf
keyserver hkp://sks.ustclug.org
hkp-cacert /usr/share/gnupg2/sks-keyservers.netCA.pem
hkp-cacert ~/.gnupg/trusted-certs/DST_Root_CA_X3.pem
log-file /tmp/dirmngr.log
debug-level advanced
gpg-agent.conf
enable-ssh-support
gpg.conf
default-key 7DFBB2F2
2016-10-14 11:36:50 dirmngr[20597] listening on socket
'/run/user/1000/gnupg/S.dirmngr'
2016-10-14 11:36:50 dirmngr[20598.0] permanently loaded certificates: 0
2016-10-14 11:36:50 dirmngr[20598.0] runtime cached certificates: 0
2016-10-14 11:38:20 dirmngr[20598.1] handler for fd 1 started
2016-10-14 11:38:20 dirmngr[20598.1] DBG: chan_1 -> # Home: /home/zsj/.gnupg
2016-10-14 11:38:20 dirmngr[20598.1] DBG: chan_1 -> # Config:
/home/zsj/.gnupg/dirmngr.conf
2016-10-14 11:38:20 dirmngr[20598.1] DBG: chan_1 -> OK Dirmngr 2.1.15 at your
service
2016-10-14 11:38:20 dirmngr[20598.1] connection from process 20595 (1000:1000)
2016-10-14 11:38:20 dirmngr[20598.1] DBG: chan_1 <- [eof]
2016-10-14 11:38:20 dirmngr[20598.1] handler for fd 1 terminated
2016-10-14 11:39:52 dirmngr[20598.1] handler for fd 1 started
2016-10-14 11:39:52 dirmngr[20598.1] DBG: chan_1 -> # Home: /home/zsj/.gnupg
2016-10-14 11:39:52 dirmngr[20598.1] DBG: chan_1 -> # Config:
/home/zsj/.gnupg/dirmngr.conf
2016-10-14 11:39:52 dirmngr[20598.1] DBG: chan_1 -> OK Dirmngr 2.1.15 at your
service
2016-10-14 11:39:52 dirmngr[20598.1] connection from process 20745 (1000:1000)
2016-10-14 11:39:52 dirmngr[20598.1] DBG: chan_1 <- [eof]
2016-10-14 11:39:52 dirmngr[20598.1] handler for fd 1 terminated
2016-10-14 11:40:15 dirmngr[20598.2] handler for fd 2 started
2016-10-14 11:40:15 dirmngr[20598.2] DBG: chan_2 -> # Home: /home/zsj/.gnupg
2016-10-14 11:40:15 dirmngr[20598.2] Assuan accept problem: Broken pipe
2016-10-14 11:40:15 dirmngr[20598.2] handler for fd 2 terminated
20600 11:38:20.134818 futex(0x7fa74998d200,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
20599 11:38:20.134970 pselect6(1, [], NULL, NULL, {1, 56253895}, {NULL, 8}
20600 11:38:20.135039 <... futex resumed> ) = -1 EAGAIN (Resource temporarily
unavailable) <0.89>
20600 11:38:20.135122 mmap(NULL, 134217728, PROT_NONE,
MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0
20598 11:38:20.135189 pselect6(5, [0 4], NULL, NULL, {0, 91526580}, {[], 8}
20600 11:38:20.135265 <... mmap resumed> ) = 0x7fa73e0e2000 <0.92>
20600 11:38:20.135524 munmap(0x7fa73e0e2000, 32628736) = 0 <0.000110>
20600 11:38:20.135737 munmap(0x7fa74400, 34480128) = 0 <0.35>
20600 11:38:20.135833 mprotect(0x7fa74000, 135168, PROT_READ|PROT_WRITE) =
0 <0.33>
20600 11:38:20.136019 stat("/etc/localtime", {st_mode=S_IFREG|0644,
st_size=414, ...}) = 0 <0.48>
20600 11:38:20.136247 write(3, "2016-10-14 11:38:20 dirmngr[2059"..., 53) = 53
<0.42>
20600 11:38:20.136359 write(3, " started\n", 9) = 9 <0.35>
20600 11:38:20.136576 getsockopt(1, SOL_SOCKET, SO_PEERCRED, {pid=20595,
uid=1000, gid=1000}, [12]) = 0 <0.32>
20600 11:38:20.136702 stat("/etc/localtime", {st_mode=S_IFREG|0644,
st_size=414, ...}) = 0 <0.39>
20600 11:38:20.136834 write(3, "2016-10-14 11:38:20 dirmngr[2059"..., 42) = 42
<0.29>
20600 11:38:20.136920 write(3, "chan_1 -> # Home: /home/zsj/.gnu"..., 35) = 35
<0.29>
20600 11:38:20.137018 futex(0x7fa74998d200, FUTEX_WAKE_PRIVATE, 1) = 0
<0.28>
Bug#836903: RFS: qevercloud/3.0.3+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt
X-Debbugs-CC: a...@debian.org
Hello Sean,
在 2016年10月13日星期四 CST 下午6:41:17，Sean Whitton 写道：
> control: tag -1 + confirmed - moreinfo
> control: noowner -1
>
> Hello,
>
> I'm going away for the weekend, so I'm marking this as confirmed as the
> only remaining issue is extremely minor (see below).
>
> I think that commit 240db346c4abfd3d6ccb1c9db36c7880db289f6a is ready
> for upload to Debian, though it would be nice if the below is fixed.
Thank you for all your patience and kind review!
Maybe it is the right time for me to seek for a DD to sponsor this package.
This package ("src:qevercloud") is a Qt library that provides access to
Evernote Cloud API. It is supposed to act as the dependency of package
"nixnote2" (RFS: #832704, ITP: #609849), which is an unofficial Qt-based
feature-rich Evernote client for Linux.
Working Git repository: https://github.com/hosiet/qevercloud
mentors.d.n: https://mentors.debian.net/package/qevercloud
prebuilt package on deb-o-matic-amd64:
http://debomatic-amd64.debian.net/distribution#unstable/qevercloud/
3.0.3+ds-1/buildlog
P.S. Please ignore the piuparts warning on debomatic.d.o, which is a false
alarm due to the site's network error.
> You should put the comments above the warning (currently below). That
> way, they are associated together.
I read articles from lintian.d.o again and confirmed the correct grammar. The
new git commit 2dcb474cb2dc2b977b0ba5f1363fd321d3cd28ac has fixed this
problem.
All related files/packages on GitHub / debian-mentors / deb-o-matic has been
updated to latest commit.
Thanks!
Sincerely,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part.
Bug#840704: supple: FTBFS on non-Linux: socketpair():Protocol not supported
Source: supple Version: 1.0.5-1 Severity: important Justification: fails to build from source Builds of supple for kFreeBSD and the Hurd failed: lua5.2: ...ld/supple-YExMLq/supple-1.0.5/5.2-supple/supple/host.lua:67: Unable to launch subprocess, could not prepare socketpair():Protocol not supported stack traceback: [C]: in function 'error' ...ld/supple-YExMLq/supple-1.0.5/5.2-supple/supple/host.lua:67: in function 'run_wrapper' ...ld/supple-YExMLq/supple-1.0.5/5.2-supple/supple/host.lua:109: in function 'run' example/simple-example.lua:83: in main chunk [C]: in ? If supporting these architectures isn't feasible, please restrict supple's Architecture field to linux-any so that non-Linux autobuilders don't bother trying to build it. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#840703: supple: FTBFS on i386: Want OK, got FAIL
Source: supple Version: 1.0.5-1 Severity: important Justification: fails to build from source The i386 build of supple hit a test suite error: Test: example/simple-example.lua [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] Want OK, got FAIL /usr/share/dh-lua/make/dh-lua.Makefile.single:306: recipe for target 'test-lua-dynamic-real' failed make[2]: *** [test-lua-dynamic-real] Error 1 Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#840705: libtest-compile-perl: all_pl_files_ok() fails if blib/ directory missing
Package: libtest-compile-perl
Version: 0.17-1
Severity: normal
Dear Maintainer,
I was working on my Perl library when I noticed that
Test::Compile::all_pl_files_ok() failed if the blib/ directory did not
exist:
2016-10-13 19:47:31 dpchrist@t7400 ~/src/Dpchrist-Lib2
$ cat t/compile_pl.t
use Test::More;
eval "use Test::Compile 0.09";
plan skip_all => "Test::Compile 0.09 required for testing compilation"
if $@;
all_pl_files_ok();
2016-10-13 19:47:43 dpchrist@t7400 ~/src/Dpchrist-Lib2
$ perl -Ilib t/compile_pl.t
1..3
not ok 1 - Compile test for script/tsv-to-pdf
# Failed test 'Compile test for script/tsv-to-pdf'
# at /usr/share/perl5/Test/Compile.pm line 82.
# script/tsv-to-pdf does not compile
not ok 2 - Compile test for script/tsv-derive-mailing-label-fields
# Failed test 'Compile test for script/tsv-derive-mailing-label-fields'
# at /usr/share/perl5/Test/Compile.pm line 82.
# script/tsv-derive-mailing-label-fields does not compile
not ok 3 - Compile test for script/tsv-select-all-by-colno-value
# Failed test 'Compile test for script/tsv-select-all-by-colno-value'
# at /usr/share/perl5/Test/Compile.pm line 82.
# script/tsv-select-all-by-colno-value does not compile
# Looks like you failed 3 tests of 3.
But if I run 'make' first to create the blib/ directory, then
all_pl_files_ok() works:
2016-10-13 19:47:53 dpchrist@t7400 ~/src/Dpchrist-Lib2
$ perl Makefile.PL
Checking if your kit is complete...
Warning: the following files are missing in your kit:
README
Please inform the author.
Generating a Unix-style Makefile
Writing Makefile for Dpchrist::Lib2
Writing MYMETA.yml and MYMETA.json
2016-10-13 19:47:59 dpchrist@t7400 ~/src/Dpchrist-Lib2
$ make 2>&1 > /dev/null
2016-10-13 19:48:13 dpchrist@t7400 ~/src/Dpchrist-Lib2
$ perl t/compile_pl.t
1..3
ok 1 - Compile test for script/tsv-to-pdf
ok 2 - Compile test for script/tsv-derive-mailing-label-fields
ok 3 - Compile test for script/tsv-select-all-by-colno-value
So I downloaded the Debian source for Test::Compile:
2016-10-13 19:41:15 dpchrist@t7400 ~/sandbox/debian/wheezy/libtest-compile-perl
$ apt-get source libtest-compile-perl
I made a change to the code set determines the library path when
compiling scripts:
2016-10-13 19:56:29 dpchrist@t7400
~/sandbox/debian/wheezy/libtest-compile-perl/libtest-compile-perl-0.17/lib/Test
$ diff -u `locate Compile.pm` Compile.pm
--- /usr/share/perl5/Test/Compile.pm2012-02-27 13:50:36.0 -0800
+++ Compile.pm 2016-10-13 19:56:29.347378684 -0700
@@ -140,7 +140,7 @@
} else {
my @perl5lib = split(':', ($ENV{PERL5LIB}||""));
my $taint = _is_in_taint_mode($file);
-unshift @perl5lib, 'blib/lib';
+unshift @perl5lib, (-e 'blib' ? 'blib/lib' : 'lib');
system($^X, (map { "-I$_" } @perl5lib), "-c$taint", $file);
return ($? ? 0 : 1);
}
I made, tested, and installed the patched distribution (I use
local::lib). Now all_pl_files_ok() works when blib/ does not exist:
2016-10-13 19:49:27 dpchrist@t7400 ~/src/Dpchrist-Lib2
$ l blib
ls: cannot access blib: No such file or directory
2016-10-13 19:59:58 dpchrist@t7400 ~/src/Dpchrist-Lib2
$ perl -Ilib t/compile_pl.t
1..3
ok 1 - Compile test for script/tsv-to-pdf
ok 2 - Compile test for script/tsv-derive-mailing-label-fields
ok 3 - Compile test for script/tsv-select-all-by-colno-value
David
-- System Information:
Debian Release: 7.11
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages libtest-compile-perl depends on:
ii libuniversal-require-perl 0.13-1
ii perl 5.14.2-21+deb7u4
libtest-compile-perl recommends no packages.
libtest-compile-perl suggests no packages.
-- no debconf information
Bug#840702: emacs25: FTBFS on non-Linux: ALSA sound support requested but not found.
Source: emacs25 Version: 25.1+1-1 Severity: important Justification: fails to build from source Builds of emacs25 on kFreeBSD and the Hurd failed: checking for ALSA... no configure: error: ALSA sound support requested but not found. debian/rules:353: recipe for target 'override_dh_auto_configure' failed Please either conditionalize the use of --with-sound=alsa or build-depend on the ALSA emulation library on these architectures. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#840701: emacs25: FTBFS: tests fail or time out
Source: emacs25 Version: 25.1+1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Automated builds of emacs25 on Linux encountered test failures (and a hang on arm64), as detailed at https://buildd.debian.org/status/logs.php?pkg=emacs25&ver=25.1%2B1-1 Could you please take a look? (Non-Linux builds failed for another reason, which I'll report separately in a moment.) Thanks! FYI, even though emacs25 is new, I'm classifying this bug as a regression because I strongly suspect it would also strike binNMUs on amd64. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#833346: wodim --devices" does not work
Tags: patch
Without following the discussion in detail, since life is too short, I
will note only that a cursory web search reveals people having this
problem at least as far back as 2008, and being advised to use a
symlink, config option, command line option, command alias, etc, to
force wodim to check /dev/sr* devices. I consider that such actions
should only be necessary in unusual cases; while peculiar situations
may exist (I don't know if they do or not) in which scanning for
/dev/sr* may be undesirable, with a vanilla setup it is not only
desirable but necessary, and resorting to reconfiguration should be a
step required only in the unusual cases.
Based on the statement (source forgotten) that there is supposed to be
a one-to-one correspondence between /dev/sr* and /dev/scd*, I submit
the attached trivial patch against cdrkit-1.1.11-3 to make it scan
for both.
--
Pigeon
Be kind to pigeons - - Pigeon's Nest: http://pigeonsnest.co.uk/
GPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F
--- cdrkit-1.1.11.orig/libusal/scsi-linux-sg.c 2008-02-26 08:02:13.0 +
+++ cdrkit-1.1.11/libusal/scsi-linux-sg.c 2016-10-14 02:59:05.867695082 +0100
@@ -508,8 +508,9 @@
else {
/* scan and maybe keep one open, sg_setup decides */
#define HDX 0
-#define SCD 1
-#define SG 2
+#define SR 1
+#define SCD 2
+#define SG 3
int h;
/*
retry_scan_open:
@@ -525,6 +526,15 @@
last='z';
break;
}
+case(SR):
+ {
+ if(!check_linux_26())
+ continue;
+ pattern="/dev/sr%d";
+ first=0;
+ last=255;
+ break;
+ }
case(SCD):
{
if(!check_linux_26())
signature.asc
Description: Digital signature
Bug#840700: g-brief2: 'Command \c@blockzahl already defined' on multiple inclusions
Package: texlive-latex-extra
Version: 2016.20161008-1
Severity: minor
Tags: patch
Hi,
g-brief2 currently does not support multiple inclusions. This would be helpful
for bulk letters and is trivial to fix.
Reproducing the issue:
> $ cat simple.tex
> \documentclass[ngerman]{g-brief2}
> \Gruss {}{1cm} % this can't be left out due to a potential another bug
> \begin{document}
>
> \begin{g-brief}
> page one
> \end{g-brief}
>
> %\newpage
> %\begin{g-brief}
> %page two
> %\end{g-brief}
>
> \end{document}
> $ pdflatex simple.tex; echo $?
> ...
> 0
> $ sed -i 's/^%//' simple.tex
> $ cat simple.tex
> \documentclass[ngerman]{g-brief2}
> \Gruss {}{1cm} % this can't be left out due to a potential another bug
> \begin{document}
>
> \begin{g-brief}
> page one
> \end{g-brief}
>
> \newpage
> \begin{g-brief}
> page two
> \end{g-brief}
>
> \end{document}
> $ pdflatex simple.tex; echo $?
> ...
>
> ! LaTeX Error: Command \c@blockzahl already defined.
>Or name \end... illegal, see p.192 of the manual.
>
> See the LaTeX manual or LaTeX Companion for explanation.
> Type H for immediate help.
> ...
>
> l.14 \end{document}
>
> ? ^\Quit
> 131
> $
A trivial patch ensures that the counter is not defined multiple times and
reset if needed:
> --- /usr/share/texlive/texmf-dist/tex/latex/g-brief/g-brief2.cls
> 2016-10-13 23:10:26.630778157 +0200
> +++ /usr/share/texlive/texmf-dist/tex/latex/g-brief/g-brief2.cls
> 2016-10-13 23:10:31.726871803 +0200
> @@ -333,7 +333,7 @@
> \unitlength1mm
> \begin{picture}(0,0)
>\put(-9,0){\parbox{180mm}{
> -\tiny \newcounter{blockzahl} \def\@blockbreite{170mm}
> +\tiny
> \ifdef{\theblockzahl}{\setcounter{blockzahl}{0}}{\newcounter{blockzahl}}
> \def\@blockbreite{170mm}
> \iftrennlinien \rule{180mm}{0.5pt} \fi
> \ifthenelse{
>\equal{\namezeilea}{\empty} \and \equal{\namezeileb}{\empty} \and
Please include that patch. Thanks!
All the best,
Julius
Bug#839701: #839701: native GTK3 print dialog crashes
Should be fixed in 5.2.4.
Bug#840699: ninix-aya: does not work with ruby-gnome2 3.0.9-1
Package: ninix-aya Version: 4.999.2-1 Severity: serious Tags: experimental Dear Maintainer, I plan to upload ruby-gnome2 3.0.9 into unstable. Before I do so, I test rdep packages in experimental uploading. ninix-aya does not work with ruby-gnome2 3.0.9-1. - : /usr/lib/ruby/vendor_ruby/ninix/menu.rb:836:in `new': 'Gtk::MenuItem#initialize(label, use_underline=false)' style has been deprecated. Use 'Gtk::MenuItem#initialize(:label => label, :use_underline => use_underline)' style. /usr/lib/ruby/vendor_ruby/ninix/menu.rb:836:in `new': 'Gtk::MenuItem#initialize(label, use_underline=false)' style has been deprecated. Use 'Gtk::MenuItem#initialize(:label => label, :use_underline => use_underline)' style. /usr/lib/ruby/vendor_ruby/ninix/pix.rb:266:in `pixbuf_new_from_file': 'Gdk::Pixbuf' has been deprecated. Use 'GdkPixbuf::Pixbuf'. /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => path) instead. /usr/lib/ruby/vendor_ruby/glib2/deprecatable.rb:112:in `const_missing': uninitialized constant GdkPixbuf::Pixbuf::InterpType Did you mean? GdkPixbuf::InterpType from /usr/lib/ruby/vendor_ruby/ninix/pix.rb:279:in `create_icon_pixbuf' from /usr/lib/ruby/vendor_ruby/ninix/menu.rb:661:in `create_ghost_menuitem' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:812:in `create_menuitem' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:472:in `call' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:472:in `handle_request' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:367:in `create_menuitem' from /usr/lib/ruby/vendor_ruby/ninix/metamagic.rb:103:in `baseinfo=' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1227:in `add_sakura' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:535:in `do_install' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1571:in `open_file_chooser' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1563:in `call' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1563:in `response' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1441:in `block in initialize' from /usr/lib/ruby/vendor_ruby/gobject-introspection/loader.rb:114:in `invoke' from /usr/lib/ruby/vendor_ruby/gobject-introspection/loader.rb:114:in `block in define_singleton_method' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:950:in `run' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:132:in `main' from /usr/lib/ruby/vendor_ruby/ninix_main.rb:1795:in `' : - Can you fix it to work with ruby-gnome2 3.0.9-1 ? I want to make ruby-gnome2 3.0.9-1 in time for stretch freeze (2016-Nov-05). -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ninix-aya depends on: ii ruby1:2.3.0+4 ii ruby-gettext3.2.2-1 ii ruby-gio2 3.0.9-1 ii ruby-gstreamer 3.0.9-1 ii ruby-gtk3 3.0.9-1 ii ruby-narray 0.6.1.1-2+b3 ii ruby-zip1.2.0-1 ninix-aya recommends no packages. Versions of packages ninix-aya suggests: pn kawari8 -- no debconf information signature.asc Description: PGP signature
Bug#840698: xnetcardconfig: does not work with ruby-gnome2 3.0.9-1
Package: xnetcardconfig Version: 0.3.0-1 Severity: serious Tags: experimental Dear Maintainer, I plan to upload ruby-gnome2 3.0.9 into unstable. Before I do so, I test rdep packages in experimental uploading. xnetcardconfig does not work with ruby-gnome2 3.0.9-1. % xnetcardconfig /usr/bin/xnetcardconfig.real:845:in `': undefined method `init' for Gtk:Module (NoMethodError) % Can you fix it to work with ruby-gnome2 3.0.9-1 ? I want to make ruby-gnome2 3.0.9-1 in time for stretch freeze (2016-Nov-05). -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xnetcardconfig depends on: ii gksu 2.0.2-9 ii pump 0.8.24-7 ii ruby 1:2.3.0+4 ii ruby-gdk3 3.0.9-1 ii ruby-gtk3 3.0.9-1 ii sudo 1.8.17p1-2 xnetcardconfig recommends no packages. xnetcardconfig suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#840374: Backtrace and patch
gdb) bt
#0 elf32_arm_count_additional_relocs (sec=0x6aa410)
at ../../bfd/elf32-arm.c:18175
#1 0x77b71b8a in bfd_elf_final_link (abfd=abfd@entry=0x68a9e0,
info=info@entry=0x685260 ) at ../../bfd/elflink.c:11224
#2 0x77b48f2b in elf32_arm_final_link (abfd=0x68a9e0,
info=0x685260 ) at ../../bfd/elf32-arm.c:12096
#3 0x0041adf7 in ldwrite () at ../../ld/ldwrite.c:577
#4 0x00405a97 in main (argc=, argv=)
at ../../ld/ldmain.c:431
And here's the patch to fix it:
---
bfd/elf32-arm.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: binutils-2.27/bfd/elf32-arm.c
===
--- binutils-2.27.orig/bfd/elf32-arm.c 2016-10-14 11:12:25.223492731 +1100
+++ binutils-2.27/bfd/elf32-arm.c 2016-10-14 11:19:42.470752509 +1100
@@ -18172,7 +18172,7 @@ elf32_arm_count_additional_relocs (asect
{
struct _arm_elf_section_data *arm_data;
arm_data = get_arm_elf_section_data (sec);
- return arm_data->additional_reloc_count;
+ return arm_data ? arm_data->additional_reloc_count : 0;
}
/* Called to set the sh_flags, sh_link and sh_info fields of OSECTION which
--
Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
Trustworthy Systems Group Data61 (formerly NICTA)
Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt
control: tag -1 + confirmed - moreinfo control: noowner -1 Hello, I'm going away for the weekend, so I'm marking this as confirmed as the only remaining issue is extremely minor (see below). I think that commit 240db346c4abfd3d6ccb1c9db36c7880db289f6a is ready for upload to Debian, though it would be nice if the below is fixed. On Thu, Oct 13, 2016 at 10:25:24PM +0800, Boyuan Yang wrote: > 2016-10-12 21:49 GMT+08:00 Sean Whitton : > > I suggest: > > > > 1) override the jquery warning, with a comment pointing to README.jquery > > (there is a special format for lintian override comments) > > I am not quite sure about what the special format for lintian override comment > is. I only found that comments in different place would have different effect > of showing / not showing in the verbose log. Could you please check the > grammar of my newly added `debian/qevercloud-doc.lintian-overrides' file? > At least lintian is accepting it. You should put the comments above the warning (currently below). That way, they are associated together. -- Sean Whitton signature.asc Description: PGP signature
Bug#840592: vim: Setting in /etc/vim/vimrc no effect / not working
On 10/14/2016 09:11 AM, James McCoy wrote: > On Thu, Oct 13, 2016 at 10:12:32AM +0800, john wrote: >>Setting in /etc/vim/vimrc or /etc/vim/vimrc.local no >>effect. >> >>Only setting in $HOME/.vimrc work. > As already discussed in other bug reports and in the NEWS file, Vim now > ships with a defaults.vim that is loaded when the user has no vimrc. > > See ":help defaults.vim" for more information. > > You can either disable it in your system vimrc or load it then and > override the options you don't like. > > Cheers, Yes, you are right, thank your help and close the bug, thanks. -- Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC signature.asc Description: OpenPGP digital signature
Bug#840697: modemmanager: interferes NeuG TRNG
Package: modemmanager
Version: 1.6.2-1
Severity: normal
Dear Maintainer,
I develop/use/sell USB TRNG (True Random Number Generator) device
which works as an USB CDC/ACM device.
The intention is that users can get the random bytes from /dev/ttyACM0
with no drivers installed. Unfortunately modemmanager interferes.
For its users, I recommend to have a following udev rule:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="234b", ATTRS{idProduct}=="0001",
ENV{ID_MM_DEVICE_IGNORE}="1"
And then, the device works fine.
Given the situation I distributed more than 200 devices, I think that
it makes sense to have the udev rule above in the modemmanager
package.
The hardware is by free hardware design and the firmware is free
software.
It is also possible to run the firmware on another board which is
cheap enough. Please have a look at:
http://www.fsij.org/gnuk/neug-on-stm32-nucleo-f103.html
So, I think there are more users of this device.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 4.7.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages modemmanager depends on:
ii init-system-helpers1.45
ii libc6 2.24-1
ii libglib2.0-0 2.48.1-3
ii libgudev-1.0-0 230-3
ii libmbim-glib4 1.14.0-1
ii libmbim-proxy 1.14.0-1
ii libmm-glib01.6.0-1
ii libpolkit-gobject-1-0 0.105-16
ii libqmi-glib5 1.16.0-1
ii libqmi-proxy 1.16.0-1
Versions of packages modemmanager recommends:
ii usb-modeswitch 2.4.0+repack0-1
modemmanager suggests no packages.
-- no debconf information
Bug#837591:
On Wed, Sep 14, 2016 at 10:27:06PM +0200, Tobias Frost wrote: > Actually, whether deleting a user on purge or not is disputed. > https://wiki.debian.org/AccountHandlingInMaintainerScripts > > (I wouldn't say this is RC, but I let the maintainer decide if it > should be downgraded) Understood. On Wed, Sep 14, 2016 at 11:21:07PM +0200, Neil Muller wrote: > Removing support for user deletion was specifically asked for when the > package was adopted into PAPT. I also don't see any compelling reason > to re-add it from policy, so I'm downgrading this bug. Right. > If there are files being left after the package is purged, please > provide details. Well, that's the thing. I wasn't very clear in my original report, but I can't think of files that irker could leave behind that we don't also want to remove. Logfiles, maybe, but those are not created by default anyways, AFAIK. So removing the user is harmless, and would make the package cleaner. Thanks. A. signature.asc Description: Digital signature
Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed
On Thu, Oct 13, 2016 at 08:27:12PM -0400, James McCoy wrote: > On Thu, Oct 13, 2016 at 07:37:13PM -0400, James McCoy wrote: > > However, I was currently looking into a different test failure whose > > symptom is that ":set modified" doesn't actually do anything. > > Interesting. This has something to do with enabling the language > bindings. When compiling with the language bindings, ":set modified" > doesn't change the option. Similarly, the segfault only happens when the Perl bindings are enabled. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#840642: [pkg-gnupg-maint] Bug#840642: gpgme binding cleanup
Hi Andre-- On Thu 2016-10-13 11:41:56 -0400, Andre Heinecke wrote: > On Wednesday 12 October 2016 20:34:25 Daniel Kahn Gillmor wrote: > For libqgpgme rebuilding kdepimlibs depending packages wont't work because > kdepimlibs qgpgme was Qt4 and libqgpgme from the gpgme package is Qt5. You > can't link Qt4 and Qt5 together. > > For gpgmepp It would require changing how the library is found. And depending > on the used API this will not work as gpgmepp from the gpgme package slightly > broke API to use C++11 memory instead of Boost (so that it is now plain c++ > without external dependencies) and some deprecated API was removed. > > But that affected mainly esoteric API regarding Assuan interaction. > Additionally you now need C++11 which kdepimlibs did not. Interesting, thanks for the details. >> * src:gpgmepp, which builds several binary packages, including >>- libkf5gpgmepp5 >>- libkf5qgpgme5 >> >>We should be able to drop this entire source package from the >>archive. Any build dependencies should probably move to >>libgpgmepp-dev from libkf5gpgmepp-dev. > > Yes. But as the libraries are coinstallable keeping around the current > Version > probably won't hurt. As said above there was a slight API break. well, much of the pain comes in the maintenance -- less to maintain, less pain :) >> Turns up the following packages that might need to be rebuilt: >> >> kaddressbook >> kde-runtime >> kget >> kmymoney >> libkf5libkleo5 >> libkf5wallet-bin >> libkleo4 >> libkwalletbackend5-5 >> libmessagecomposer4 >> libmessageviewer4 > > This list looks incomplete to me (probably implicity dependencies?). At least > Kleopatra is missing or are you not shipping a kde4 based kleopatra anymore? > (In that case I wonder why kaddressbook is in there) hm, you're absolutely right. i failed to look for reverse dependencies for libkf5gpgmepp-pthread5, which turns up some additional packages, most importantly: kleopatra kmail it'd be great to try to get those building against the gpgme-upstream-supported versions if we can! > Complete tightness. :-) You can't link qt4 and 5 together. I guess this is a question for the debian kde/qt team about how long we want to keep qt4 around for… --dkg signature.asc Description: PGP signature
Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed
On Thu, Oct 13, 2016 at 07:37:13PM -0400, James McCoy wrote: > However, I was currently looking into a different test failure whose > symptom is that ":set modified" doesn't actually do anything. Interesting. This has something to do with enabling the language bindings. When compiling with the language bindings, ":set modified" doesn't change the option. > Being > able to step through the code would make that a bit easier, but I guess > I can add printfs. The inability to use gdb seems to correlate to whatever's causing ":set modified" not to work. When no language bindings are enabled (vim-basic, vim-tiny), I can use gdb to debug Vim just fine. When the bindings are enabled, those tests fail and gdb can't debug Vim. I just tried enabling each binding individually and it seems this only happens with --enable-perlinterp. I can enable all the other languages (ruby, tcl, lua, python3), and things work just fine, but add Perl and things start breaking. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#827335: evince: assertion failed: (wayland_display->cursor_theme_name)
Hi,
Michael Biebl:
+ owner /{,var/}run/user/*/weston-shared-* rw,
I've run into this bug myself last month and submitted a pull request
to AppArmor upstream that does basically that, except I do it by
introducing a new 'wayland' abstraction, that I include in the 'gnome'
one:
https://code.launchpad.net/~intrigeri/apparmor/wayland/+merge/305422
I've just poked upstream about it.
If you're in a hurry, patching /etc/apparmor.d/usr.bin.evince as
proposed on this bug (quoted above) should be a fine
temporary solution.
Cheers,
--
intrigeri
Bug#828701: /usr/lib/x86_64-linux-gnu/libfm.so: Re: libfm4: Crashes (SIGABRT) on invalid paths
Package: libfm-dev Version: 1.2.4-1 Followup-For: Bug #828701 Dear Maintainer, the reported bug still exists and I can confirm that the attached patch works with pcmanfm (1.2.4-1). Greetings, Stephan Gabert -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.7.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 libfm-dev:amd64 depends on: ii libfm-extra41.2.4-1 ii libfm4 1.2.4-1 ii libglib2.0-dev 2.50.0-2 libfm-dev:amd64 recommends no packages. Versions of packages libfm-dev:amd64 suggests: pn libfm-doc -- no debconf information
Bug#839905: Bug#840293: pkg-kde-tools: pkgkde-symbolshelper broken by perl 5.24
Control: clone -1 -2
Control: reassign -2 libdpkg-perl
Control: retitle -2 libdpkg-perl: Dpkg::IPC::spawn immediately closes FH after
dup
Hi!
[ Was pointed to this bug by Stuart Prescott. ]
On Thu, 2016-10-13 at 23:30:09 +0200, gregor herrmann wrote:
> On Thu, 13 Oct 2016 17:13:09 -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> > Steps to reproduce:
> >
> > apt-get source -t experimental qtdeclarative-opensource-src
> > cd qtdeclarative-opensource-src-5.7.0/
> > getbuildlog qtdeclarative-opensource-src last
> > pkgkde-symbolshelper batchpatch -v 5.7.0 *.log
>
> Thanks!
> That makes it indeed easier to reproduce :)
Indeed!
> So, my findings:
> - the error "reopen stdout: Bad file descriptor" happens in
> /usr/share/perl5/Debian/PkgKde/SymbolsHelper/Patching.pm line 246:
> wait_child($pid, nocheck => 1);
> - that's when the formerly assembled $pid gets executed
> - looking at $pid above, I notice that both to_handle and
> error_to_handle are set to $outfile (a temp file created before)
> - just out of curiosity, I commented out the error_to_handle line
> (241), and now `pkgkde-symbolshelper batchpatch -v 5.7.0 *.log'
> passes
> - running `pkgkde-symbolshelper batchpatch -v 5.7.0 *.log' again
> fails with failed hunk errors from patch, which also doesn't look
> so bad
>
> Not sure where this leaves us, especially since I neither know
> Dpkg::IPC nor understand the apply() sub in
> Debian::PkgKde::SymbolsHelper::Patching.
> (And I also don't know where exactly the problem / changed behaviour
> with perl 5.24 lies. Since the spawn/wait_pid functions are from
> Dpkg::IPC, I guess looking into Dpkg::IPC might be interesting.)
The problem is that spawn() is closing the passed filehandle just
after duping it to STDOUT and then STDERR instead of queueing it for
deferred closure. I'm also not sure why this didn't trigger before?
Perhaps perl was delaying the filehandle closure?
I'll include the attached patch fpr libdpkg-perl in the next dpkg
release, but in the interim you might want to workaround this in
pkg-kde-tools, by duping the $output filehandle before passing it
to spawn().
Thanks,
Guillem
diff --git i/scripts/Dpkg/IPC.pm w/scripts/Dpkg/IPC.pm
index 5172540..3dfbde9 100644
--- i/scripts/Dpkg/IPC.pm
+++ w/scripts/Dpkg/IPC.pm
@@ -282,7 +282,8 @@ sub spawn {
} elsif ($opts{from_handle}) {
open(STDIN, '<&', $opts{from_handle})
or syserr(g_('reopen stdin'));
- close($opts{from_handle}); # has been duped, can be closed
+ # has been duped, can be closed
+ push @{$opts{close_in_child}}, $opts{from_handle};
}
# Redirect STDOUT if needed
if ($opts{to_file}) {
@@ -291,7 +292,8 @@ sub spawn {
} elsif ($opts{to_handle}) {
open(STDOUT, '>&', $opts{to_handle})
or syserr(g_('reopen stdout'));
- close($opts{to_handle}); # has been duped, can be closed
+ # has been duped, can be closed
+ push @{$opts{close_in_child}}, $opts{to_handle};
}
# Redirect STDERR if needed
if ($opts{error_to_file}) {
@@ -300,7 +302,8 @@ sub spawn {
} elsif ($opts{error_to_handle}) {
open(STDERR, '>&', $opts{error_to_handle})
or syserr(g_('reopen stdout'));
- close($opts{error_to_handle}); # has been duped, can be closed
+ # has been duped, can be closed
+ push @{$opts{close_in_child}}, $opts{error_to_handle};
}
# Close some inherited filehandles
close($_) foreach (@{$opts{close_in_child}});
Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed
On Fri, Oct 14, 2016 at 12:08:46AM +0100, Steven Chamberlain wrote: > Hi, > > James McCoy wrote: > > I've solved the fifo test failure, and now am able to see the segfault > > on fischer. However, gdb has been pretty useless for me on kfreebsd. > > > > Is there something else that I should try using instead? > > I would usually enable core dumps and look at those in gdb first, but > most of the time ktrace explains better what led up to the crash. > > I usually use `ktrace -di -- executable` and `kdump -EHf ktrace.out`. > Please show me the output of that, if you can reproduce the crash that > way. Thanks for the ktrace pointer. That's what helped me fix the fifo problem. However, I was currently looking into a different test failure whose symptom is that ":set modified" doesn't actually do anything. Being able to step through the code would make that a bit easier, but I guess I can add printfs. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#840680: [pkg-gnupg-maint] Bug#840680: dirmngr: Dirmngr not always responding
Control: tags 840680 + unreproducible moreinfo Control: severity 840680 important hi Shengjing-- Thanks for this report. it sounds frustrating! I hope we can debug it: On Thu 2016-10-13 15:12:44 -0400, Shengjing Zhu wrote: > After upgrade to 2.1.15-4, I find dirmngr is not always responding > which makes command like `gpg --refresh-keys` stuck. is this "always not responding" or "sometimes not responding"? I haven't observed the same behavior with dirmngr myself, so i'm not sure how to best proceed... > I test dirmngr with the following steps: > > First run `gpg-connect-agent --dirmngr /bye` > It should immediately return but it's stuck. > > But I open another shell to run `gpg-connect-agent --dirmngr /bye` > again. The first gpg-connect-agent returns and the second still is > stuck. > > And I run again `gpg-connect-agent` and the previous one returns. this is definitely strange behavior! have you tried attaching strace to the dirmngr process to see what it's doing while it's not answering you? or have you tried increasing the logging of dirmngr to see what it's doing while it's not responding? if the process id of dirmngr is $DIRMNGR_PID, you can use: strace -o dirmngr.strace -f -tt -T -p $DIRMNGR_PID to get an strace dump. You can increase the logging by adding these lines to ~/.gnupg/dirmngr.conf and then restarting dirmngr: log-file /tmp/dirmngr.log debug-level advanced If you've got dirmgnr logs or strace output that you think might be worth sharing, but are maybe too sensitive to post to this public bug report, feel free to send them privately to me (you can encrypt to 0EE5BE979282D80B9F7540F1CCD2ED94D21739E9 if you like). > So I guess only another process access to the dirmngr socket, the > previous connect will be got processed. I'm not sure what you mean by this. can you explain? --dkg signature.asc Description: PGP signature
Bug#577737: [pinentry-qt4] Re: gpg command won't use agent if the agent is configured to use pinentry-qt4
On Thu 2016-10-13 14:09:16 -0400, OmegaPhil wrote: > Enigmail is v1.9.5 via Get Addons (rather than the Debian package). > > I started playing with dirmngr.conf but then I realised you meant > gpg-agent.conf ;). thanks, yes, you are correct :) > As soon as I did a killall to have gpg-agent load the new > configuration and try again, it worked - I know that gpg2 stuff has > updated recently, and my uptime is ~11d, so perhaps the update scripts > don't kill off gpg-agent when theres some incompatible change? That's right, the package upgrade scripts make no attempt to restart long-running user processes, for reasons i suspect you can imagine :) Can you review /var/log/dpkg.log to see what versions of gpg-agent you might have been running initially? I'm glad it's working for you now, anyway, though i'm still in the dark as to why it wasn't working for you before. --dkg signature.asc Description: PGP signature
Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed
Steven Chamberlain wrote: > I didn't see a segfault yet on fischer, only this: Never mind, I can reproduce it with ~/vim-8.0.0022/src/vim-gtk/po$ ktrace -di -- ../vim -u NONE -e -X -S check.vim -c "if error == 0 | q | endif" -c cq af.po I'm reading over the kdump output now. I'm not sure what's with gdb. Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
Bug#831591: ffmpeg: kodi crash
Control: reopen -1 Control: reassign -1 kodi 16.1+dfsg1-2 Control: severity -1 important Hi, The relevant backtrace from the kodi_crashlog is: Thread 1 (Thread 0x7f1b6bffe700 (LWP 16893)): #0 0x7f1ba92991c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1 0x7f1ba929a64a in __GI_abort () at abort.c:89 #2 0x7f1ba92d4f4a in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f1ba93cdb30 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x7f1ba92da6b6 in malloc_printerr (action=3, str=0x7f1ba93ca909 "free(): invalid pointer", ptr=, ar_ptr=) at malloc.c:5004 #4 0x7f1ba92dae9e in _int_free (av=0x7f1ba9601b20 , p=, have_lock=0) at malloc.c:3865 #5 0x7f1baa6d4a9d in av_buffer_unref () from /usr/lib/x86_64-linux-gnu/libavutil.so.55 #6 0x7f1baa6e15d2 in av_frame_unref () from /usr/lib/x86_64-linux-gnu/libavutil.so.55 #7 0x7f1bab93cf10 in avcodec_decode_video2 () from /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #8 0x0090b26c in CDVDDemuxFFmpeg::ParsePacket(AVPacket*) () #9 0x0090d0c2 in CDVDDemuxFFmpeg::Read() () #10 0x01079b53 in CDVDPlayer::ReadPacket(DemuxPacket*&, CDemuxStream*&) () #11 0x0107ecd7 in CDVDPlayer::Process() () #12 0x012103ff in CThread::Action() () #13 0x012106bf in CThread::staticThread(void*) () #14 0x7f1bb23e5464 in start_thread (arg=0x7f1b6bffe700) at pthread_create.c:333 #15 0x7f1ba934d30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Looking at the ParsePacket function reveals [1]: AVFrame picture; memset(&picture, 0, sizeof(AVFrame)); picture.pts = picture.pkt_dts = picture.pkt_pts = picture.best_effort_timestamp = AV_NOPTS_VALUE; picture.pkt_pos = -1; picture.key_frame = 1; picture.format = -1; This is using non-public ABI, e.g. the size of AVFrame, while the documentation explicitly says "sizeof(AVFrame) is not a part of the public ABI" [2]. What's worse is that it doesn't use av_frame_alloc as required [3]: "AVFrame must be allocated using av_frame_alloc()." The whole block quoted above should be replaced with: AVFrame *picture = av_frame_alloc(). Then the following code should use picture instead of &picture: avcodec_decode_video2(st->codec, picture, &got_picture, pkt); And at the end it can be freed (instead of using av_frame_unref) with: av_frame_free(&picture); In the experimental kodi branch there is another occurrence of this bug in xbmc/cores/VideoPlayer/VideoRenderers/HwDecRender/MMALRenderer.cpp. Best regards, Andreas 1: https://anonscm.debian.org/cgit/pkg-multimedia/kodi.git/tree/xbmc/cores/dvdplayer/DVDDemuxers/DVDDemuxFFmpeg.cpp?id=8d5cf423001aa4e7f850c20b158b2811e637e607#n1665 2: https://anonscm.debian.org/cgit/pkg-multimedia/ffmpeg.git/tree/libavutil/frame.h?id=87b93f4e3ee2b6253ab9f5a166860a1ff18877d5#n174 3: https://anonscm.debian.org/cgit/pkg-multimedia/ffmpeg.git/tree/libavutil/frame.h?id=87b93f4e3ee2b6253ab9f5a166860a1ff18877d5#n154
Bug#832594: libinput10: Thinkpad middle mouse not functioning properly, appears to be libinput10 issue
Does this help: $ xinput set-prop "TPPS/2 IBM TrackPoint" "libinput Button Scrolling Button" 0 libinput 1.5 appears to enable scroll wheel emulation for the middle button by default. I recently hit a similar issue after a jessie -> stretch upgrade. Ross
Bug#840696: [flashplugin-nonfree] Get specific version from upstream
Package: flashplugin-nonfree Version: 1:3.7 Severity: wishlist --- Please enter the report below this line. --- I think that can be very usefull get a specific version example: # update-flashplugin-nonfree --install --verbose --get-version=11.2.202.635 thanks! --- System information. --- Architecture: amd64 Kernel: Linux 4.7.0-1-amd64 Debian Release: stretch/sid 500 testing ftp.debian.org 500 stable-updates huayra.bbs.docksud.com.ar 500 stable-proposed huayra.bbs.docksud.com.ar 500 stable huayra.bbs.docksud.com.ar 500 stable dl.google.com --- Package information. --- Depends (Version) | Installed ==-+-=== debconf| 1.5.59 OR debconf-2.0| wget | 1.18-4 gnupg | 2.1.15-3 OR gnupg2 | 2.1.15-3 libatk1.0-0| 2.22.0-1 libcairo2 | 1.14.6-1+b1 libfontconfig1 | 2.11.0-6.7 libfreetype6 | 2.6.3-3+b1 libgcc1| 1:6.1.1-11 libglib2.0-0 | 2.50.0-2 libgtk2.0-0 (>= 2.14) | 2.24.31-1 libnspr4 | 2:4.12-2 libnss3| 2:3.26-2 libpango1.0-0 | 1.40.3-2 libstdc++6 | 6.1.1-11 libx11-6 | 2:1.6.3-1 libxext6 | 2:1.3.3-1 libxt6 | 1:1.1.5-1 libcurl3-gnutls| 7.50.1-1 binutils | 2.27-8 Package's Recommends field is empty. Suggests (Version) | Installed -+-=== iceweasel| firefox-esr | konqueror-nsplugins | ttf-mscorefonts-installer| 3.6 fonts-dejavu | 2.37-1 ttf-xfree86-nonfree | hal-flash| --- Output from package bug script --- Debian version: stretch/sid Architecture: amd64 Package version: 1:3.7 Adobe Flash Player version: LNX 11,2,202,635 MD5 checksums: 88aa056c9d4f919bfc9c301f099fe0d1 /var/cache/flashplugin-nonfree/adobewebpage.html 29c85bc8504422120cf89702986ff8e1 /var/cache/flashplugin-nonfree/get-upstream-version.pl 5bb834820d1563b2df2ed52fd9986b24 /var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz 0a6cc8d010a71847b02409165d5574d6 /usr/lib/flashplugin-nonfree/libflashplayer.so Alternatives: flash-mozilla.so - auto mode link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 lrwxrwxrwx 1 root root 34 oct 13 20:04 /usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so /usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to /etc/alternatives/flash-mozilla.so
Bug#840695: plasma-sdk: lookandfeelexplorer requires kirigami, but it is not marked even in Recommends
Package: plasma-sdk Version: 5.8.0-1 Severity: important Dear Maintainer, $ lookandfeelexplorer "file:///usr/share/kpackage/genericqml/org.kde.plasma.lookandfeelexplorer/contents/ui/main.qml" "Error loading QML file.\n26: module \"org.kde.kirigami\" is not installed\n" Error loading the ApplicationWindow -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (850, 'testing'), (800, 'unstable'), (750, 'experimental'), (750, 'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-sdk depends on: ii kpackagetool5 5.26.0-1 ii libc6 2.24-3 ii libkf5archive55.26.0-1 ii libkf5completion5 5.26.0-1 ii libkf5configcore5 5.26.0-1 ii libkf5configwidgets5 5.26.0-1 ii libkf5coreaddons5 5.26.0-1 ii libkf5dbusaddons5 5.26.0-1 ii libkf5declarative55.26.0-1 ii libkf5i18n5 5.26.0-1 ii libkf5iconthemes5 5.26.0-1 ii libkf5kiocore55.26.0-1 ii libkf5kiowidgets5 5.26.0-1 ii libkf5package55.26.0-1 ii libkf5plasma5 5.26.0-2 ii libkf5plasmaquick55.26.0-2 ii libkf5quickaddons55.26.0-1 ii libkf5service-bin 5.26.0-1 ii libkf5service55.26.0-1 ii libkf5texteditor5 5.26.0-1 ii libkf5widgetsaddons5 5.26.0-1 ii libqt5core5a 5.6.1+dfsg-3+b1 ii libqt5dbus5 5.6.1+dfsg-3+b1 ii libqt5gui55.6.1+dfsg-3+b1 ii libqt5qml55.6.1-11 ii libqt5quick5 5.6.1-11 ii libqt5widgets55.6.1+dfsg-3+b1 ii libqt5xml55.6.1+dfsg-3+b1 ii libstdc++66.1.1-11 ii plasma-framework 5.26.0-2 Versions of packages plasma-sdk recommends: ii bash 4.4-1 Versions of packages plasma-sdk suggests: ii git 1:2.9.3-1 -- no debconf information
Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed
I didn't see a segfault yet on fischer, only this: | From test_channel.vim: | Found errors in Test_communicate(): | function | RunTheTest[9]..Test_communicate[2]..5_run_server[1]..RunServer[21]..Ch_communicate | line 26: Expected 'ok' but got '' | function | RunTheTest[9]..Test_communicate[2]..5_run_server[1]..RunServer line | 23: 'Caught exception: Vim(call):E121: Undefined variable: g:split' | | Test results: | | | From test_channel.vim: | Found errors in Test_communicate(): | function | RunTheTest[9]..Test_communicate[2]..5_run_server[1]..RunServer[21]..Ch_communicate | line 26: Expected 'ok' but got '' | function | RunTheTest[9]..Test_communicate[2]..5_run_server[1]..RunServer line | 23: 'Caught exception: Vim(call):E121: Undefined variable: g:split' | TEST FAILURE Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed
Hi, James McCoy wrote: > I've solved the fifo test failure, and now am able to see the segfault > on fischer. However, gdb has been pretty useless for me on kfreebsd. > > Is there something else that I should try using instead? I would usually enable core dumps and look at those in gdb first, but most of the time ktrace explains better what led up to the crash. I usually use `ktrace -di -- executable` and `kdump -EHf ktrace.out`. Please show me the output of that, if you can reproduce the crash that way. Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
Bug#840687: [pkg-gnupg-maint] Bug#840687: gnupg: Fails to sign git commits
Control: tags 840687 + unreproducible moreinfo
Hi Josef--
thanks for your report! sorry to hear you're having this problem.
hopefully we can get it sorted out!
I tried to replicate this with a test directory:
workdir=$(mktemp -d)
export GNUPGHOME="$workdir/gpg"
mkdir -m 0700 $GNUPGHOME
gpg --batch --passphrase-fd 3 3<<'
fpr=$(gpg --with-colons --with-fingerprint --list-secret-keys | awk -F:
'/^fpr:/{print $10}' | head -n1)
git init "$workdir/test"
cd "$workdir/test"
echo test > test.txt
git add test.txt
git commit -S"$fpr" -m 'test commit'
and it worked for me, using a pinentry-gnome3 :/
I did *not* get the responses you got:
On Thu 2016-10-13 16:44:38 -0400, Josef Vitu wrote:
> after upgrading from 1.4.20-6 to 2.1.15-4, signing a git commit fails with
> the following errors:
>
> gpg: signing failed: No data callback in IPC
> gpg: signing failed: No data callback in IPC
> error: gpg failed to sign the data
> fatal: failed to write commit object
>
> The password input into the pinentry-gnome3 (or pinentry-gtk-2) dialog is
> 100% correct.
Then i tried using pinentry-tty manually, with:
echo pinentry-program pinentry-tty >> "$workdir/gpg/gpg-agent.conf"
gpg-connect-agent killagent /bye
And i got the same errors you did:
> Attempts to use pinentry-tty failed with:
>
> gpg: signing failed: Invalid IPC response
with pinentry-tty, i saw:
gpg: signing failed: Invalid IPC response
gpg: signing failed: Invalid IPC response
error: gpg failed to sign the data
fatal: failed to write commit object
However, if i set GPG_TTY before trying to sign, the signature worked
with pinentry-tty as well:
export GPG_TTY=$(tty)
git commit -S"$fpr" -m 'test commit'
that worked fine.
So something is different about your setup. Can you start by trying the
same sequence i tried (with 2.1.15-4) and letting me know whether it
works independent of your homedir?
With your own homedir where this stuff is failing, can you turn up the
logging in gpg-agent and see what's going on there? add the following
lines to ~/.gnupg/gpg-agent.conf :
debug-pinentry
log-file /home/YOURUSER/gpg-agent.log
and then kill off the agent so it can be restarted:
gpg-connect-agent killagent /bye
and try to sign again.
Let me know what you find!
--dkg
signature.asc
Description: PGP signature
Bug#840694: gcc: /usr/bin/gcc should use /etc/alternatives
Package: gcc Version: 4:6.1.1-1 Severity: wishlist Dear Maintainer, I currently have gcc versions 4.7, 5.0 and 6.0 installed. I'd like to be able to switch between them on a regular basis. The simplest way to do this would be to use update-alternatives to switch, but currently /usr/bin/gcc and its friends are direct symlinks to /usr/bin/gcc-6 By `friends' I mean cpp, c++, c89 c99 gcc-ar gcc-ranlib gcc-nm etc. The same goes for the various cross compilers (arm-linux-gnueabi-gcc etc) -- Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/ Trustworthy Systems Group Data61 (formerly NICTA)
Bug#802658: libesmtp: Should support TLS 1.1+
Upstream has been completely MIA for several years now. I've not really checked to determine if there's actually anything dependent on libesmtp and have contemplated archive removal as I am not taking over as upstream and the project itself has appeared to be lifeless and I've merely been keeping the packaging updated. On 10/10/2016 12:30 AM, Salvatore Bonaccorso wrote: > Hi Jememy, > > Since almost now a year I try to get that patch forwarded and I have > it locally running without problems. I do not get a reply from > upstream author. > > Are you in contact with upstream/have an alternative contact address? > > The freeze for Debian stretch is approaching in meanwhile really fast. > > Regards, > Salvatore
Bug#840693: qttools-opensource-src: Please disable WebKit support on m68k and sh4
Source: qttools-opensource-src Version: 5.6.1-2 Severity: normal Hi! Both on m68k and sh4, qtwebkit-opensource-src doesn't build [1] and fixing the issue would probably require quite some elbow grease. Thus, it would be great if WebKit support in qttools could be disabled on these architectures for the time being. >From what I can see [2], it should be enough to not build-depend on >libqt5webkit5-dev on m68k and sh4, thus, I suggest suffixing this B-D with [!m68k !sh4]. Allowing qttools-opensource-src to build on m68k and sh4 would eventually allow cmake-extra-modules to build which will make a large number of packages installable again. Thanks for considering, Adrian > [1] > https://buildd.debian.org/status/package.php?p=qtwebkit-opensource-src&suite=sid > [2] > https://anonscm.debian.org/cgit/pkg-kde/qt/qttools.git/commit/?id=e986a62459dea5f04683df8ce02ed75501fce1e8 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#840692: nemo-python: plugin is not recognized or loaded by Nemo
Package: nemo-python Version: 3.0.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, The nemo-python extension is not displayed in the "Extensions" list under Edit->Plugins. This is further confirmed by the fact that none of the Python extensions I have installed work. Running Nemo under KDE, Gnome, and Cinnamon doesn't appear to make any difference. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core) 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 nemo-python depends on: ii gir1.2-nemo-3.0 3.0.6-3 ii libatk1.0-0 2.22.0-1 ii libc62.24-3 ii libcairo-gobject21.14.6-1+b1 ii libcairo21.14.6-1+b1 ii libgdk-pixbuf2.0-0 2.36.0-1 ii libglib2.0-0 2.50.1-1 ii libgtk-3-0 3.22.1-1 ii libnemo-extension1 3.0.6-3 ii libpango-1.0-0 1.40.3-2 ii libpangocairo-1.0-0 1.40.3-2 ii libpython2.7 2.7.12-3+b1 nemo-python recommends no packages. nemo-python suggests no packages. -- no debconf information
Bug#838234: transition: readline/readline6
On 13/10/16 20:10, Pino Toscano wrote: > Hi, > > In data martedì 11 ottobre 2016 00:14:35 CEST, Emilio Pozuelo Monfort ha > scritto: >> Control: tags -1 confirmed >> >> On 03/10/16 00:10, Emilio Pozuelo Monfort wrote: >>> Control: forwarded -1 >>> https://release.debian.org/transitions/html/readline7.html >>> >>> Hi, >>> >>> On 18/09/16 20:43, Matthias Klose wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition readline 7.0 is now released, changing the soversion. The idea is to upload the readline package from experimental (plus providing the libreadline*6-dev packages), and stop building the -dev packages and common packages from readline6. Afaics, the API didn't change; for rebuild tests I only see build failures for unrelated reasons. readline and readline6 can stay in testing for some time, but readline6 should be removed from testing before the stretch release. I haven't done a test rebuild on unstable, but building on Ubuntu yakkety. The current state of the transition can be seen at http://people.canonical.com/~ubuntu-archive/transitions/html/readline.html >>> >>> Sounds good. I'd prefer to see a test rebuild on sid, but I think we could >>> go >>> ahead with this as it's a separate source and shouldn't block anything. >> >> readline 6 got decrufted. Rebuilds scheduled. > > Please adjust the tracker to consider also Pre-Depends on libreadline6: > gawk has Pre-Depends instead of Depends, and there's libreadline6 there. > As consequence, please also schedule the binNMU of gawk for this > transition. Done, and scheduled. Cheers, Emilio
Bug#839884: [Pkg-utopia-maintainers] Bug#839884: network-manager: Confirmed here
Hi, It just happened again, apparently a new version got in testing: Unpacking network-manager (1.4.2-1+b1) over (1.4.2-1) ... and it still hangs; Setting up network-manager (1.4.2-1+b1) ... The information you requested: $ systemctl status NetworkManager-dispatcher.service ● NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service Loaded: loaded (/lib/systemd/system/NetworkManager-dispatcher.service; enable Active: inactive (dead) ps output again: root 7664 4248 0 23:18 pts/100:00:00 /usr/bin/dpkg --status-fd 80 --no-triggers --configure --pending root 8266 7664 0 23:19 pts/100:00:00 /bin/sh /var/lib/dpkg/info/network-manager.postinst configure 1.4.2-1 root 8332 1 0 23:19 ?00:00:00 /usr/sbin/NetworkManager --no-daemon root 8419 8266 0 23:19 pts/100:00:00 /bin/systemctl try-restart NetworkManager-dispatcher.service root 8423 8419 0 23:19 pts/100:00:00 /bin/systemd-tty-ask-password-agent --watch HTH! On 06-10-16 23:37, Michael Biebl wrote: Am 06.10.2016 um 21:42 schrieb Manuel Bilderbeek: Package: network-manager Version: 1.4.2-1 Followup-For: Bug #839884 Dear Maintainer, I also see the hangup: Setting up libkf5widgetsaddons-data (5.26.0-1) ... Setting up network-manager (1.4.2-1) ... and then nothing. ps -Af says: root 4897 2663 0 21:35 pts/200:00:00 /usr/bin/dpkg --status-fd 80 --configure --pending root 4906 4897 0 21:35 pts/200:00:00 /bin/sh /var/lib/dpkg/info/network-manager.postinst configure 1.4.0-4 root 4972 1 0 21:35 ?00:00:00 /usr/sbin/NetworkManager --no-daemon root 5060 4906 0 21:35 pts/200:00:00 /bin/systemctl try-restart NetworkManager-dispatcher.service root 5061 5060 0 21:35 pts/200:00:00 /bin/systemd-tty-ask-password-agent --watch What's the output of systemctl status NetworkManager-dispatcher.service -- Grtjs, Manuel
Bug#840691: libgs9: security update DSA-3691-1 breaks zathura, evince, ... in jessie
Package: libgs9 Version: 9.06~dfsg-2+deb8u3 Severity: grave Tags: security Justification: renders package unusable Hello! I had a bad surprise today in jessie. After the security update: [UPGRADE] libgs9:amd64 9.06~dfsg-2+deb8u1 -> 9.06~dfsg-2+deb8u3 [UPGRADE] libgs9-common:amd64 9.06~dfsg-2+deb8u1 -> 9.06~dfsg-2+deb8u3 I was unable to use zathura or evince (maybe other PS viewers are affected): $ zathura foo.eps warning: Failed to loads bookmarks. invalidaccess -7 error: Rendering failed (page 1) $ evince foo.eps invalidaccess -7 invalidaccess -7 Segmentation fault After downgrading back to libgs9/9.06~dfsg-2+deb8u1 and libgs9-common/9.06~dfsg-2+deb8u1, everything is back to normal and the two PS viewers work again. What went wrong? If this is indeed a regression (as it seems to be), please fix it as soon as possible! Thanks for your time. -- System Information: Debian Release: 8.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/20 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libgs9 depends on: ii libc6 2.19-18+deb8u6 ii libcups21.7.5-11+deb8u1 ii libcupsimage2 1.7.5-11+deb8u1 ii libfontconfig1 2.11.0-6.3+deb8u1 ii libfreetype62.5.2-3+deb8u1 ii libgs9-common 9.06~dfsg-2+deb8u3 ii libidn111.29-1+deb8u2 ii libijs-0.35 0.35-10 ii libjasper1 1.900.1-debian1-2.4+deb8u1 ii libjbig2dec00.11+20120125-1 ii libjpeg62-turbo 1:1.3.1-12 ii liblcms2-2 2.6-3+b3 ii libpaper1 1.1.24+nmu4 ii libpng12-0 1.2.50-2+deb8u2 ii libtiff54.0.3-12.3+deb8u1 ii poppler-data [gs-cjk-resource] 0.4.7-1 ii zlib1g 1:1.2.8.dfsg-2+b1 libgs9 recommends no packages. libgs9 suggests no packages. -- no debconf information
Bug#840685: tomcat8: DSA-3670 incomplete
Dear Markus, >> [ I contacted t...@security.debian.org about this, but no response ... ] > ... Please send them to the security team > first and not to a public mailing list. I did. They did not reply within what seemed a reasonable timeframe. >> Recently DSA-3670 was released, and /etc/init.d/tomcat8 modified so... > No, we did not modify this part in /etc/init.d/tomcat8. ... Whoops, sorry, you are right. Now checking, I do not see how I got confused. This is a separate, maybe new issue. > ... more information and a working proof > of concept code are appreciated. ... Maybe the security team will understand (recognize, accept) the issue without a PoC. If they reply with such a need, then I will write one. You or they might accept the suggested patch/fix: mkdir without -p, chown with -h. Cheers, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia
Bug#833722: ffmpeg: can hear music but no sound/dialogs from movie
Control: tags -1 unreproducible Hi shirish, On 08.08.2016 11:39, shirish शिरीष wrote: > Last few days, I have been able to hear the audio/songs/singing > background but no dialogs. > > I see the following on the CLI - Next time please also copy the command line, or at least mention the program producing the output. I guess the below comes from mpv. > [ffmpeg/audio] ac3: Channel layout '5.1(side)' with 6 channels does > not match specified number of channels 2: ignoring specified channel > layout > AO: [pulse] 48000Hz stereo 2ch float > VO: [opengl] 720x304 yuv420p > AV: 00:00:00 / 01:30:22 (0%) A-V: 0.000 > [ffmpeg/audio] ac3: exponent 26 is out-of-range > [ffmpeg/audio] ac3: error decoding the audio block This looks like the sample is broken/corrupted. > AV: 00:01:48 / 01:30:22 (1%) A-V: 0.000 > > Does this mean the only fix for such movies is a 5.1 output or there > could be some other fix ? No. Both ffplay and mpv usually just downmix the audio automatically. This works fine here without any warnings. Can you share a sample reproducing the problem? Otherwise I'm afraid I won't be able to help you. Best regards, Andreas
Bug#840472: apt-listbugs: [INTL:de] Updated German debconf translation
On Thu, 13 Oct 2016 20:53:55 +0200 Chris Leick wrote: > Francesco Poli: > > Chris Leick wrote: > > > Francesco Poli wrote; > > > > Perfect, then please suggest how I can modify: > > > >#: ../lib/aptlistbugs/logic.rb:54 > >msgid " -T : Filter bugs by tags you want to see.\n" > >msgstr " -T : filtert nach Kennzeichnungen, die Sie sehen > > wollen.\n" > > Hi Francesco, > > " -T : filtert nach Markierungen, die Sie sehen wollen.\n I basically know almost nothing about the German language, so I apologize in advance, in case I am completely wrong. But... why do you still translate "" as ""? Please let me know. Thanks for your time and patience! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgp3xGktr30VF.pgp Description: PGP signature
Bug#713004: Sponsoring
Yes, please take the package. I wanted to learn how to do debian packaging, but I never did. Thanks, Spencer On Thu, Oct 13, 2016, at 07:58 AM, Jelmer Vernooij wrote: > On Thu, Oct 13, 2016 at 03:17:23PM +0200, Bernhard Schmidt wrote: > > Control: retitle -1 ITA: ndisc6 -- IPv6 diagnostic tools > > > > On Fri, Apr 25, 2014 at 12:38:19AM +0200, Jelmer Vernooij wrote: > > > > Hi Jelmer, hi Spencer, > > > > > On Wed, Apr 23, 2014 at 07:38:48PM -0700, n...@cat.pdx.edu wrote: > > > > Yes. My account name is nibalizer-guest on alioth. I think I am still > > > > waiting on approval. How do I get a git repository? > > > I've uploaded a git repository here, which updates the package to > > > 1.0.2 and adds us as maintainers: > > > git+ssh://git.debian.org/git/collab-maint/ndisc6.git > > > > > > You should be able to join the collab-maint team on the alioth page, > > > see the "Request to join" link on > > > https://alioth.debian.org/projects/collab-maint/ > > > > The package is still up for adoption, any news here? > > > > If I don't hear from you I'll take over the package next week, > > incorporate the uploads that have accumulated in the meantime and do a > > force-push of the repo to show the actual content. Then I'll upgrade to > > 1.0.3 and current dh9. > > > > Of course anyone is invited to help. Feel free to push changes to the > > repo and do uploads yourself at any time. > I don't have enough time to take this package over by myself, and > jhaven't > heard back anything from Spencer. Thanks for taking over. > > Jelmer -- Spencer Krum n...@spencerkrum.com
Bug#839542: typo: Send/Que command to all matching filters
Control: forwarded -1 https://ffmpeg.org/pipermail/ffmpeg-devel/2016-October/201062.html Hi Mathieu, On 01.10.2016 21:14, Mathieu Malaterre wrote: > I do not believe this is proper english. Patch attached. Thanks for reporting this. I've forwarded the fix upstream together with a couple of other spelling fixes. I hope you don't mind that. Best regards, Andreas
Bug#839905: Bug#840293: pkg-kde-tools: pkgkde-symbolshelper broken by perl 5.24
On Thu, 13 Oct 2016 17:13:09 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Steps to reproduce: > > apt-get source -t experimental qtdeclarative-opensource-src > cd qtdeclarative-opensource-src-5.7.0/ > getbuildlog qtdeclarative-opensource-src last > pkgkde-symbolshelper batchpatch -v 5.7.0 *.log Thanks! That makes it indeed easier to reproduce :) So, my findings: - the error "reopen stdout: Bad file descriptor" happens in /usr/share/perl5/Debian/PkgKde/SymbolsHelper/Patching.pm line 246: wait_child($pid, nocheck => 1); - that's when the formerly assembled $pid gets executed - looking at $pid above, I notice that both to_handle and error_to_handle are set to $outfile (a temp file created before) - just out of curiosity, I commented out the error_to_handle line (241), and now `pkgkde-symbolshelper batchpatch -v 5.7.0 *.log' passes - running `pkgkde-symbolshelper batchpatch -v 5.7.0 *.log' again fails with failed hunk errors from patch, which also doesn't look so bad Not sure where this leaves us, especially since I neither know Dpkg::IPC nor understand the apply() sub in Debian::PkgKde::SymbolsHelper::Patching. Maybe guillem and/or modax as the respective authors can help here. (And I also don't know where exactly the problem / changed behaviour with perl 5.24 lies. Since the spawn/wait_pid functions are from Dpkg::IPC, I guess looking into Dpkg::IPC might be interesting.) Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Bob Dylan: Tweedle Dee & Tweedle Dum signature.asc Description: Digital Signature
Bug#840690: ruby-foreman: FTBFS: Failed examples: rspec ./spec/foreman/export/inittab_spec.rb:17 # Foreman::Export::Inittab exports to the filesystem
Source: ruby-foreman
Version: 0.82.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
ruby-foreman fails to build from source in unstable/amd64:
[..]
NoMethodError:
undefined method `stub' for
#
# /usr/lib/ruby/vendor_ruby/rspec/matchers.rb:967:in `method_missing'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:747:in
`method_missing'
# ./spec/foreman/export/upstart_spec.rb:14:in `block (2 levels) in '
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:443:in `instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:443:in `instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:350:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:507:in `block in
run_owned_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:506:in `each'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:506:in
`run_owned_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:593:in `block in
run_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:592:in `reverse_each'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:592:in
`run_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:462:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:490:in
`run_before_example'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:253:in `block in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in `block in
with_around_and_singleton_context_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in `block in
with_around_example_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `block in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:602:in
`run_around_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in
`with_around_example_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in
`with_around_and_singleton_context_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:627:in `block
in run_examples'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in
`run_examples'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:589:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `block
in run'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (3
levels) in run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `map'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (2
levels) in run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1835:in
`with_suite_hooks'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:112:in `block in
run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:77:in `report'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:111:in `run_specs'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
# /usr/bin/rspec:4:in `'
37) Foreman::Export::Upstart with a formation exports to the filesystem
with concurrency
Failure/Error: before(:each) { stub(upstart).say }
NoMethodError:
undefined method `stub' for
#
# /usr/lib/ruby/vendor_ruby/rspec/matchers.rb:967:in `method_missing'
# /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:747:in
`method_missing'
# ./spec/foreman/export/upstart_spec.rb:14:in `block (2 levels) in '
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:443:in `instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:443:in `instance_exec'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:350:in `run'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:507:in `block in
run_owned_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:506:in `each'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:506:in
`run_owned_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:593:in `block in
run_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:592:in `reverse_each'
# /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:592:in
`run_example_hooks_for'
# /usr/lib/ruby/vendor_ruby/rspe
Bug#840650: Firmware
I think firmware is ok. root@debian:/lib/firmware/rtlwifi# stat rtl8723befw.bin File: 'rtl8723befw.bin' Size: 30746 Blocks: 64 IO Block: 4096 regular file Device: 809h/2057d Inode: 267698 Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) Access: 2016-10-13 23:43:14.282229846 +0300 Modify: 2016-09-18 06:15:29.0 +0300 Change: 2016-09-22 00:24:27.314880254 +0300 Birth: - Moreover, there is only one rtl8723 firmware file in my system . I suppose if it was a FW bug i wouldn't be capable to use wifi even with 3.16 or with 4.7.5.1 (before the upgrade). George V
Bug#840685: tomcat8: DSA-3670 incomplete
On 13.10.2016 22:22, Paul Szabo wrote:
> Package: tomcat8
> Version: 8.0.14-1+deb8u3
> Severity: critical
> Tags: security
> Justification: root security hole
>
>
> [ I contacted t...@security.debian.org about this, but no response ... ]
I am CCing the security team in case they want to chime in here.
>
> Recently DSA-3670 was released, and /etc/init.d/tomcat8 modified so:
>
> ...
> NAME=tomcat8
> ...
> JVM_TMP=/tmp/tomcat8-$NAME-tmp
> ...
> # Remove / recreate JVM_TMP directory
> rm -rf "$JVM_TMP"
> mkdir -p "$JVM_TMP" || {
> log_failure_msg "could not create JVM temporary
> directory"
> exit 1
> }
> chown $TOMCAT8_USER "$JVM_TMP"
> ...
No, we did not modify this part in /etc/init.d/tomcat8. We fixed
CVE-2016-1240 by applying this patch
https://anonscm.debian.org/cgit/pkg-java/tomcat8.git/commit/?h=jessie&id=9a9fd4f1cae13304beed6d4e445d1be8a3917fe0
> That suffers from a TOCTOU race condition.
>
> An attacker can, after the "rm -rf", create a symlink to /etc. Then
> "mkdir -p" returns success (though does nothing); and chown follows
> the symlink. That is "game over": ability to replace /etc/passwd.
>
> The attacker can use inotify and act quickly, and have a good chance
> of winning the race to create the symlink before the init.d script
> starts a new mkdir process.
>
> Do you need some working PoC code?
I don't understand how this affects our solution for CVE-2016-1240. If
you claim this is a new issue, then more information and a working proof
of concept code are appreciated. Please send them to the security team
first and not to a public mailing list.
signature.asc
Description: OpenPGP digital signature
Bug#840689: libterm-readline-gnu-perl: FTBFS on 64-bit big endian architectures
Package: libterm-readline-gnu-perl Version: 1.34-1 Severity: serious Hi, On a rebuild against libreadline7, your package failed to build on big-endian, 64-bit architectures: # 2.4 History Variables ok 86 - history_inhibit_expansion_function ok 87 ok 88 ok Use of uninitialized value in string eq at t/readline.t line 119. Use of uninitialized value in string eq at t/readline.t line 119. # Failed test 'readline_state' # at t/readline.t line 152. Full logs at: https://buildd.debian.org/status/package.php?p=libterm-readline-gnu-perl Emilio
Bug#840688: ITP: r-cran-nleqslv -- GNU R package for solving systems of nonlinear equations
Package: wnpp Severity: wishlist Owner: "Sébastien Villemot" * Package name: r-cran-nleqslv Version : 3.0.3 Upstream Author : Berend Hasselman * URL : https://cran.r-project.org/web/packages/nleqslv/index.html * License : GPL-2+ Programming Lang: R Description : GNU R package for solving systems of nonlinear equations This R package solves a system of nonlinear equations using a Broyden or a Newton method with a choice of global strategies such as line search and trust region. There are options for using a numerical or user supplied Jacobian, for specifying a banded numerical Jacobian and for allowing a singular or ill-conditioned Jacobian. The package will be maintained within the Debian Science Team. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://sebastien.villemot.name `- GPG Key: 4096R/381A7594 signature.asc Description: PGP signature
Bug#840676: [pkg-go] Bug#840676: RFP: golang-github-kardianos-osext -- Extensions to the standard "os" package
On 14 Oct 2016, at 5:44 AM, Guillem Jover wrote: > > Package: wnpp > Severity: wishlist > Tags: patch > > * Package name: golang-github-kardianos-osext > Version : 0.0~git20160811.0.c2c54e5-1 > Upstream Author : Daniel Theophanes > * URL : https://github.com/kardianos/osext > * License : BSD-3-clause > Programming Lang: Go > Description : Extensions to the standard "os" package Hi Guillem. This package is already in Debian under the source package name "golang-osext". It's not the latest version though, so there is still some work that can be done here. Tim. signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#820474: cups-filters: texttopdf seg faults if comment in prettyprinted source file ends with keyword
Hi Brian, Thanks very much for the follow up. I have tested cups-filters version 1.11.4-1 on an installation of Debian unstable and it does, indeed, fix the problem. Please close this bug. Jim Uhl
Bug#840646: [debian-mysql] Bug#840646: mariadb-10.0: please move mysql_installdb to core package
Hi Otto, Note that I have a note (https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1612647) about trying to keep binaries between MariaDB and MySQL synced, to try and avoid the kind of error in that bug. I don't think that is in conflict with this request at all, but it would probably be worth adding to a list of rearrangements and Breaks/Replaces to add, then doing everything at once. Robie signature.asc Description: PGP signature
Bug#835177: [PKG-Openstack-devel] Bug#835177: aodh: FTBFS with eatmydata (build hangs)
On 10/13/2016 01:37 PM, Santiago Vila wrote: > + set -e > ++ mktemp -d /tmp/AODH-MONGODB-X > + MONGO_DATA=/tmp/AODH-MONGODB-lZXDc > + MONGO_PORT=29000 > + mkfifo /tmp/AODH-MONGODB-lZXDc/out > + MONGO_PID=16886 > + wait_for_line 'waiting for connections on port 29000' > /tmp/AODH-MONGODB-lZXDc/out > + mongod --maxConns 32 --nojournal --noprealloc --smallfiles --quiet --noauth > --port 29000 --dbpath /tmp/AODH-MONGODB-lZXDc --bind_ip localhost --config > /dev/null > + read line > > > I don't know what you did to try to fix this, but apparently it didn't > work, so I'm reopening this (wishlist) bug, and I hope you are still > willing to make this package compatible with eatmydata. > > Thanks a lot. I thought the issue was killing the processes *after* the unit tests are run. But then I tried to use command-prefix=eatmydata in the chroot.d file, and began to understood what happened. If you prefix the start of mongod with eatmydata, then the daemon produces no output at all, and the above script is in fact waiting for such text output. So I tried to write a script that would use netcat to see if the port 29000 is opened or not. And then I've seen that in fact, mongodb really seem to be stuck, doing nothing, if invoked with eatmydata. A quick use of strace shows that, with eatmydata, mongodb-server is looping on some nanosleep() calls. So I'm really not sure how to fix the issue. Any idea? Is there a way to disable eatmydata explicitly in my package, maybe only when starting mongodb? Is there a better way to setup schroot than adding command-prefix=eatmydata in your chroot.d schroot config file? Cheers, Thomas Goirand (zigo)
Bug#840496: More data
Same here More info: root@nas:/srv/Descargas# service amule-daemon start Job for amule-daemon.service failed because the control process exited with error code. See "systemctl status amule-daemon.service" and "journalctl -xe" for details. root@nas:/srv/Descargas# systemctl status amule-daemon.service ● amule-daemon.service - LSB: Daemonized version of aMule. Loaded: loaded (/etc/init.d/amule-daemon; generated; vendor preset: enabled) Active: failed (Result: exit-code) since jue 2016-10-13 22:31:15 CEST; 1min 12s ago Docs: man:systemd-sysv-generator(8) Process: 18125 ExecStart=/etc/init.d/amule-daemon start (code=exited, status=1/FAILURE) oct 13 22:31:15 nas amule-daemon[18125]: [8] ?? in /usr/bin/amuled[0x427e49] oct 13 22:31:15 nas amule-daemon[18125]: [9] wxEntry(int&, wchar_t**) in /usr/ lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f368e3bb332] oct 13 22:31:15 nas amule-daemon[18125]: [10] ?? in /usr/bin/amuled[0x420c42] oct 13 22:31:15 nas amule-daemon[18125]: [11] __libc_start_main in /lib/ x86_64-linux-gnu/libc.so.6[0x7f368d6a22b1] oct 13 22:31:15 nas amule-daemon[18125]: [12] ?? in /usr/bin/amuled[0x42675a] oct 13 22:31:15 nas amule-daemon[18125]: Aborted oct 13 22:31:15 nas systemd[1]: amule-daemon.service: Control process exited, code=exited status=1 oct 13 22:31:15 nas systemd[1]: Failed to start LSB: Daemonized version of aMule.. oct 13 22:31:15 nas systemd[1]: amule-daemon.service: Unit entered failed state. oct 13 22:31:15 nas systemd[1]: amule-daemon.service: Failed with result 'exit-code'. journalctl -xe relevant output: -- Subject: Unit amule-daemon.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit amule-daemon.service has begun starting up. oct 13 22:33:33 nas amule-daemon[18211]: 22:33:33: Warning: Mismatch between the program and library build versions detected. oct 13 22:33:33 nas amule-daemon[18211]: The library used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8), oct 13 22:33:33 nas amule-daemon[18211]: and your program used 3.0 (wchar_t,compiler with C++ ABI 1010,wx containers,compatible with 2.8). oct 13 22:33:33 nas amule-daemon[18211]: Assertion failed: ../../../../src/ libs/common/Path.cpp:CPath:258: Assertion 'm_printable.Length()' failed. oct 13 22:33:33 nas amule-daemon[18211]: Backtrace follows: oct 13 22:33:33 nas amule-daemon[18211]: [3] wxOnAssert(char const*, int, char const*, char const*, char const*) in /usr/lib/x86_64-linux-gnu/ libwx_baseu-3.0.so.0[0x7fc79298cc oct 13 22:33:33 nas amule-daemon[18211]: [4] ?? in /usr/bin/amuled[0x57f3cc] oct 13 22:33:33 nas amule-daemon[18211]: [5] ?? in /usr/bin/amuled[0x52a618] oct 13 22:33:33 nas amule-daemon[18211]: [6] ?? in /usr/bin/amuled[0x53524e] oct 13 22:33:33 nas amule-daemon[18211]: [7] ?? in /usr/bin/amuled[0x433935] oct 13 22:33:33 nas amule-daemon[18211]: [8] ?? in /usr/bin/amuled[0x427e49] oct 13 22:33:33 nas amule-daemon[18211]: [9] wxEntry(int&, wchar_t**) in /usr/ lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7fc792a1f332] oct 13 22:33:33 nas amule-daemon[18211]: [10] ?? in /usr/bin/amuled[0x420c42] oct 13 22:33:33 nas amule-daemon[18211]: [11] __libc_start_main in /lib/ x86_64-linux-gnu/libc.so.6[0x7fc791d062b1] oct 13 22:33:33 nas amule-daemon[18211]: [12] ?? in /usr/bin/amuled[0x42675a] oct 13 22:33:33 nas amule-daemon[18211]: Aborted oct 13 22:33:33 nas systemd[1]: amule-daemon.service: Control process exited, code=exited status=1 oct 13 22:33:33 nas systemd[1]: Failed to start LSB: Daemonized version of aMule.. -- Subject: Unit amule-daemon.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit amule-daemon.service has failed. -- -- The result is failed. oct 13 22:33:33 nas systemd[1]: amule-daemon.service: Unit entered failed state. oct 13 22:33:33 nas systemd[1]: amule-daemon.service: Failed with result 'exit-code'. -- David Garabana Barro jabber & google talk ID:da...@garabana.com Clave pública PGP/GPG: http://davide.garabana.com/pgp.html
Bug#840687: gnupg: Fails to sign git commits
Package: gnupg Version: 2.1.15-4 Severity: normal Dear Maintainer, after upgrading from 1.4.20-6 to 2.1.15-4, signing a git commit fails with the following errors: gpg: signing failed: No data callback in IPC gpg: signing failed: No data callback in IPC error: gpg failed to sign the data fatal: failed to write commit object The password input into the pinentry-gnome3 (or pinentry-gtk-2) dialog is 100% correct. Attempts to use pinentry-tty failed with: gpg: signing failed: Invalid IPC response I can view/edit/etc. all of the stored keys (using gpg; tried to install seahorse as well), only the communication wit git seems to be failing. Downgrading to 1.4.18-7+deb8u2 fixes the problem. Regards Josef Vitu -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.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 gnupg depends on: ii gnupg-agent2.1.15-4 ii libassuan0 2.4.3-1 ii libbz2-1.0 1.0.6-8 ii libc6 2.24-3 ii libgcrypt201.7.3-1 ii libgpg-error0 1.24-1 ii libksba8 1.3.5-2 ii libreadline7 7.0-1 ii libsqlite3-0 3.14.2-1+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages gnupg recommends: ii dirmngr 2.1.15-4 pn gnupg-l10n Versions of packages gnupg suggests: pn parcimonie pn xloadimage -- no debconf information
Bug#840665: firefox: I can't get rid of firefox
On Thu, Oct 13, 2016 at 12:15:59PM -0400, Ric Moore wrote: > Package: firefox > Version: 45.4.0esr-2 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > firefox keeps getting installed >* What exactly did you do (or not do) that was effective (or > ineffective)? > I tried to delete the pakcage only to have it re-installed. What was the command you typed and what was its output when you deleted the package and the output when it was re-installed? Mike
Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed
On Sat, Oct 01, 2016 at 08:33:54PM -0400, James McCoy wrote: > On Sat, Oct 01, 2016 at 10:48:47PM +0100, Steven Chamberlain wrote: > > But now, a new error is being seen on kfreebsd and interestingly, also > > on linux-alpha: > > > > | Found errors in Test_tagcase(): > > | Caught exception in Test_tagcase(): Vim(edit):E37: No write since last > > change (add ! to override) @ function RunTheTest[9]..Test_tagcase, line 3 > > | TEST FAILURE > > There's also a segfault on kfreebsd-i386 and a failure in > test_startup_utf8 (Test_read_fifo_utf8) on kfreebsd-*. I've solved the fifo test failure, and now am able to see the segfault on fischer. However, gdb has been pretty useless for me on kfreebsd. Is there something else that I should try using instead? Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#80123: Proposing new package - netbsd-pkgsrc
I'd propose a new package in Debian apt repository called netbsd-pkgsrc. `netbsd-pkgsrc` is the NetBSD packages collection for building third-party software on NetBSD and other UNIX-like systems. pkgsrc maybe very useful tool for maintaining packages and a good alternative for apt. Please consider my proposition.
Bug#840686: ITP: gudhi -- C++ template library for topological data analysis
Package: wnpp Severity: wishlist Owner: Gard Spreemann * Package name: gudhi Version : 1.3.1 Upstream Author : Gudhi project / INRIA * URL : http://gudhi.gforge.inria.fr/ * License : GPL-3+ Programming Lang: C++ Description : C++ template library for topological data analysis The GUDHI library is a generic open source C++ library for Topological Data Analysis (TDA) and Higher Dimensional Geometry Understanding. The library offers state-of-the-art data structures and algorithms to construct simplicial complexes and compute persistent homology. The GUDHI library is developed as part of the GUDHI project supported by the European Research Council. I have initial packaging of the libgudhi-dev (the headers for this template-based library) done, and will add the comprehensive set of examples later. I would need a sponsor. Best regards, Gard Spreemann
Bug#840685: tomcat8: DSA-3670 incomplete
Package: tomcat8
Version: 8.0.14-1+deb8u3
Severity: critical
Tags: security
Justification: root security hole
[ I contacted t...@security.debian.org about this, but no response ... ]
Recently DSA-3670 was released, and /etc/init.d/tomcat8 modified so:
...
NAME=tomcat8
...
JVM_TMP=/tmp/tomcat8-$NAME-tmp
...
# Remove / recreate JVM_TMP directory
rm -rf "$JVM_TMP"
mkdir -p "$JVM_TMP" || {
log_failure_msg "could not create JVM temporary
directory"
exit 1
}
chown $TOMCAT8_USER "$JVM_TMP"
...
That suffers from a TOCTOU race condition.
An attacker can, after the "rm -rf", create a symlink to /etc. Then
"mkdir -p" returns success (though does nothing); and chown follows
the symlink. That is "game over": ability to replace /etc/passwd.
The attacker can use inotify and act quickly, and have a good chance
of winning the race to create the symlink before the init.d script
starts a new mkdir process.
Do you need some working PoC code?
---
The script should be made more robust by using "chown -h". (This would
protect against the above attack.)
The script should use plain mkdir without "-p": not needed as we create
a single directory, and should not be used to let mkdir return failure.
(This may make it safe.)
Cheers, Paul
Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of SydneyAustralia
-- System Information:
Debian Release: 8.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (x86_64)
Kernel: Linux 3.16.36-pk07.24-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages tomcat8 depends on:
ii adduser3.113+nmu3
ii debconf [debconf-2.0] 1.5.56
ii tomcat8-common 8.0.14-1+deb8u3
ii ucf3.0030
Versions of packages tomcat8 recommends:
pn authbind
Versions of packages tomcat8 suggests:
pn libtcnative-1
pn tomcat8-admin
pn tomcat8-docs
pn tomcat8-examples
pn tomcat8-user
-- Configuration Files:
/etc/init.d/tomcat8 changed [not included]
/etc/tomcat8/catalina.properties [Errno 13] Permission denied:
u'/etc/tomcat8/catalina.properties'
/etc/tomcat8/context.xml [Errno 13] Permission denied:
u'/etc/tomcat8/context.xml'
/etc/tomcat8/logging.properties [Errno 13] Permission denied:
u'/etc/tomcat8/logging.properties'
/etc/tomcat8/policy.d/01system.policy [Errno 13] Permission denied:
u'/etc/tomcat8/policy.d/01system.policy'
/etc/tomcat8/policy.d/02debian.policy [Errno 13] Permission denied:
u'/etc/tomcat8/policy.d/02debian.policy'
/etc/tomcat8/policy.d/03catalina.policy [Errno 13] Permission denied:
u'/etc/tomcat8/policy.d/03catalina.policy'
/etc/tomcat8/policy.d/04webapps.policy [Errno 13] Permission denied:
u'/etc/tomcat8/policy.d/04webapps.policy'
/etc/tomcat8/policy.d/50local.policy [Errno 13] Permission denied:
u'/etc/tomcat8/policy.d/50local.policy'
/etc/tomcat8/server.xml [Errno 13] Permission denied: u'/etc/tomcat8/server.xml'
/etc/tomcat8/tomcat-users.xml [Errno 13] Permission denied:
u'/etc/tomcat8/tomcat-users.xml'
/etc/tomcat8/web.xml [Errno 13] Permission denied: u'/etc/tomcat8/web.xml'
-- debconf information excluded
Bug#840250: closed by Joerg Jaspert (done (Allow to query for files in archive, closes: #840250))
On 14459 March 1977, Joerg Jaspert wrote: >> https://api.ftp-master.debian.org/file_in_archive/%25%2fdgit_1.4.tar.gz> >> => 404 The requested URL /file_in_archive/%/dgit_1.4.tar.gz was not found on >> this server >> OTOH this >> https://api.ftp-master.debian.org/file_in_archive/%25dgit%5C_1.4.tar.gzdoes >> work, at least. > Honestly, I have no Idea what the web framework is making of it. And as I had none, I just read some documentation and a FAQ (uh gosh), and as such marked the "filepattern" part of the URL as "path", which is magic for bottle making it accept requests like https://api.ftp-master.debian.org/file_in_archive/t/tmux/%25ar.gz https://api.ftp-master.debian.org/file_in_archive/d/dgit/dgit_1.4.tar.gz https://api.ftp-master.debian.org/file_in_archive/9/%25.tar.gz which is way nicer than URL encoding / is, so we go with that. That is, you can specify as much of the path as you want/know, or use the %25 to get a % for the SQL LIKE, or combine them. Ought to be flexible (and halfway readable) enough. -- bye, Joerg If God didn’t want us to eat in church, he would’ve made gluttony a sin.
Bug#836154: sbuild --no-arch-any --no-arch-all --source fails on all only dsc
Hi, Quoting Sam Hartman (2016-10-13 19:36:21) > > "Johannes" == Johannes Schauer writes: > > Johannes> Do you know a situation when it would be beneficial to let > Johannes> sbuild create the source package *again* after it has > Johannes> already been produced for sbuild? > > Sbuild can take a directory as input. yes, and the first thing it does, is to run "dpkg-source -b ." to create a source package which is *then* passed to the actual sbuild machinery. So this is just a convenience feature which allows one to run sbuild from within a unpacked source package without manually executing dpkg-source. But the actual input to sbuild is still the source package. The question remains: in which situation would it be beneficial to let sbuild produce the source package *again*? > I tend to use it in that way for CI-driven builds from git repositories. > Sometimes I want source uploads, Use "dpkg-buildpackage -S" and add a "-nc" if you just extracted the source package (so no clean up is required). > sometimes I want a binary upload. Then just run sbuild but then you don't need --source. > (In this case I ended up wanting a source upload because of another bug in > mini-buildd, although in other cases I'd just want a source upload). As an > example, I might want to run gbp buildpackage --git-export-dir=somewhere > --git-builder=sbuild --source --no-arch-any --no-arch-all to prepare an > upload to debian (after testing my tree some other way). Does sbuild add > that much in that situation? No, but it sure doesn't hurt, and consistency > is nice. I still don't understand why you want to throw in the --source argument above. You will see that even if you do not provide the --source argument, there will be a .dsc in the parent directory, the one created by "dpkg-source -b ." as it is run by sbuild if you execute it from within an unpacked source package. Why do you want it to rebuild the source package *again*? Thanks! cheers, josch signature.asc Description: signature
Bug#840683: RM: sra-sdk [i386 kfreebsd-amd64 kfreebsd-i386] -- ROM; Does not build on some architectures any more
Package: ftp.debian.org Severity: normal Hi, upstream does not support i386 any more. So please remove the mentioned architectures to enable testing migration of sra-sdk. Thanks for your work as ftpmaster Andreas.
Bug#840684: firebird3.0: Please add patch to add m68k platform support
Source: firebird3.0
Version: 3.0.1.32609.ds4-6
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: m68k
Hi Damyan!
The patch attached to this bug report adds platform support for m68k
which is one of the ports architectures we have in Debian.
This patch contains two patches which have been squashed into one patch
for convenience. Both patches have also been sent upstream and are
awaiting review [1]. The patches sent upstream also contain some
more explanation.
Since firebird-dev is a reverse dependency to Qt and therefore transitively
a large number of packages, it's very important for the m68k port to have
a working firebird3.0 package.
Thus, it would be very much appreciated if you could include the attached
patch in your next upload.
Thanks a lot,
Adrian
> [1] https://github.com/FirebirdSQL/firebird/pull/52
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Description: Add platform support for Linux/m68k
Author: John Paul Adrian Glaubitz
--- firebird3.0-3.0.1.32609.ds4.orig/configure.ac
+++ firebird3.0-3.0.1.32609.ds4/configure.ac
@@ -361,6 +361,17 @@ dnl CPU_TYPE=ppc64
SHRLIB_EXT=so
;;
+ m68k*-*-linux*)
+ MAKEFILE_PREFIX=linux_generic
+ INSTALL_PREFIX=linux
+ PLATFORM=LINUX
+ AC_DEFINE(LINUX, 1, [Define this if OS is Linux])
+ AC_DEFINE(M68K, 1, [Define this if CPU is M68k])
+ LOCK_MANAGER_FLG=Y
+ EDITLINE_FLG=Y
+ SHRLIB_EXT=so
+ ;;
+
*-*-linux* | *-*-gnu*)
MAKEFILE_PREFIX=linux_generic
INSTALL_PREFIX=linux
@@ -997,10 +1008,11 @@ AC_CHECK_MEMBER([struct dirent.d_type],
dnl EKU: try to determine the alignment of long and double
dnl replaces FB_ALIGNMENT and FB_DOUBLE_ALIGN in src/jrd/common.h
AC_MSG_CHECKING(alignment of long)
-AC_RUN_IFELSE([AC_LANG_SOURCE([[main () {
+AC_RUN_IFELSE([AC_LANG_SOURCE([[#include
+main () {
struct s {
char a;
-long long b;
+union { long long x; sem_t y; } b;
};
exit((int)&((struct s*)0)->b);
}]])],[ac_cv_c_alignment=$ac_status],[ac_cv_c_alignment=$ac_status],[])
--- firebird3.0-3.0.1.32609.ds4.orig/src/common/classes/DbImplementation.cpp
+++ firebird3.0-3.0.1.32609.ds4/src/common/classes/DbImplementation.cpp
@@ -48,6 +48,7 @@ static const UCHAR CpuHppa = 13;
static const UCHAR CpuAlpha = 14;
static const UCHAR CpuArm64 = 15;
static const UCHAR CpuPowerPc64el = 16;
+static const UCHAR CpuM68k = 17;
static const UCHAR OsWindows = 0;
static const UCHAR OsLinux = 1;
@@ -87,7 +88,8 @@ const char* hardware[] = {
"HPPA",
"Alpha",
"ARM64",
- "PowerPC64el"
+ "PowerPC64el",
+ "M68k"
};
const char* operatingSystem[] = {
@@ -128,8 +130,8 @@ const UCHAR backwardTable[FB_NELEM(hardw
const UCHAR backEndianess[FB_NELEM(hardware)] =
{
-// Intel AMD Sparc PPC PPC64 MIPSEL MIPS ARM IA64 s390 s390x SH SHEB HPPA Alpha ARM64 PowerPC64el
- 0, 0, 1, 1, 1, 0, 1, 0, 0, 1, 1, 0, 1, 1, 0, 0, 0
+// Intel AMD Sparc PPC PPC64 MIPSEL MIPS ARM IA64 s390 s390x SH SHEB HPPA Alpha ARM64 PowerPC64el M68k
+ 0, 0, 1, 1, 1, 0, 1, 0, 0, 1, 1, 0, 1, 1, 0, 0, 0, 1
};
} // anonymous namespace
--- firebird3.0-3.0.1.32609.ds4.orig/src/common/common.h
+++ firebird3.0-3.0.1.32609.ds4/src/common/common.h
@@ -195,6 +195,10 @@
#define FB_CPU CpuPowerPc64
#endif /* PPC64 */
+#ifdef M68K
+#define FB_CPU CpuM68k
+#endif /* M68K */
+
#endif /* LINUX */
--- firebird3.0-3.0.1.32609.ds4.orig/src/jrd/inf_pub.h
+++ firebird3.0-3.0.1.32609.ds4/src/jrd/inf_pub.h
@@ -241,6 +241,7 @@ enum info_db_implementations
isc_info_db_impl_linux_arm64 = 84,
isc_info_db_impl_linux_ppc64el = 85,
isc_info_db_impl_linux_ppc64 = 86,
+ isc_info_db_impl_linux_m68k = 87,
isc_info_db_impl_last_value // Leave this LAST!
Bug#839905: Bug#840293: pkg-kde-tools: pkgkde-symbolshelper broken by perl 5.24
Steps to reproduce: apt-get source -t experimental qtdeclarative-opensource-src cd qtdeclarative-opensource-src-5.7.0/ getbuildlog qtdeclarative-opensource-src last pkgkde-symbolshelper batchpatch -v 5.7.0 *.log I'm using experimental's qtdeclarative because I know there are symbols that need fixing in there. -- SlackDeb: velo como un entrenamiento shaolin para geeks, en vez de meditación y tortura física, abstinencia de internet y sexo Horacio Francisco Sebastián "Perrito" Durán Barrionuevo, sobre un viaje que Federico "SlackDeb" Peretti estaba planeando con su novia. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#761980: program not importing ‘platform’ from standard library
> If you do find that âplatformâ was imported from the > wrong place, that indicates a bug in the âslimitâ > program for not importing from the standard library. ... or a platform.py earlier in my custom PYTHONPATH - which, now that I know what to look for, is exactly the problem. PEBKAC - sorry to waste your time - please close this bug, Eddy.
Bug#840679: [pkg-lxqt-devel] Bug#840679: {qterminal, libfm-qt, liblxqt}-l10n: fails to upgrade from 'sid' - trying to overwrite /usr/share/*/translations/*.qm
Good catch, thank you very much - the breaks and replaces was in place, but some package names and versions was messed up. Cheers Alf
Bug#840250: closed by Joerg Jaspert (done (Allow to query for files in archive, closes: #840250))
On 14459 March 1977, Ian Jackson wrote: > Should the docs eventually appear here > https://ftp-master.debian.org/epydoc/dakweb-module.html? They are there. > https://api.ftp-master.debian.org/file_in_archive/%25%2fdgit_1.4.tar.gz > => 404 The requested URL /file_in_archive/%/dgit_1.4.tar.gz was not found on > this server > OTOH this > https://api.ftp-master.debian.org/file_in_archive/%25dgit%5C_1.4.tar.gzdoes > work, at least. Honestly, I have no Idea what the web framework is making of it. -- bye, Joerg Dafür hat Ubuntu nen kleinen.
