Bug#816858: Logical volumes on external USB disk cause boot to enter emergency shell
On Sat, Mar 05, 2016 at 09:09:09PM +0100, Christoph Pleger wrote: > I have Debian jessie running on a Wandboard armhf device. Some of the > filesystems are located in LVM logical volumes on an external USB disk. This > causes boot to enter emergeny shell, because the logical volumes cannot be > found. The only way I found so far to prevent that is to use sysvinit instead > of systemd and insert a sleep in /etc/init.d/lvm2 before vgchange. I have no idea what you mean with "logical volumes cannot be found". If devices may be missing, please make sure that the fstab entry includes "nofail". Please show full logs and please test with a current version, something like 2.02.142. Bastian -- Women are more easily and more deeply terrified ... generating more sheer horror than the male of the species. -- Spock, "Wolf in the Fold", stardate 3615.4
Bug#791463: Quick review
On 6 March 2016 at 01:20, Pali Rohár wrote: > First dpkg-buildpackage call works, but calling it secondary fails with: > > dpkg-source: info: local changes detected, the modified files are: > udfclient-0.8.1/Makefile > > It is because "debian/rules clean" calls only "bmake clean" which does > not delete autogenerated file Makefile. That is deleted by another > target "bmake cleandir". > > So version 20150606-2 still does not work for udfclient. > > Now I think that I should stay with my implementation which is working > instead experimenting with --buildsystem=bmake.. For that, there's debian/clean, where you delete the autogenerated file, just as you'd do if you had autoconf+gmake. -- Cheers, Andrew
Bug#812213: RFP: golang-github-satori-go.uuid -- UUID package for Go
On Sat, 5 Mar 2016 23:00:25 -0500 Peter Colberg wrote: > retitle 812213 ITP: golang-github-satori-go.uuid -- UUID package for Go > owner 812213 ! > thanks > > Hi Daniel, > > On Thu, Jan 21, 2016 at 05:21:21PM +0100, Daniel Stender wrote: > > * Package name: golang-github-satori-go.uuid > > Version : 0.0+git20151029.d41af8b > > Upstream Author : Maxim Bublis > > * URL : https://github.com/satori/go.uuid > > * License : Expat > > Programming Lang: Go > > Description : UUID package for Go > > I intend to upload this package, which is a dependency of acmetool [1]. > > [1] > https://lists.alioth.debian.org/pipermail/pkg-go-maintainers/Week-of-Mon-20160229/003379.html > > Regards, > Peter Great! Best, DS -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Bug#816881: dpkg: fails to install kernel with boot partition with vfat filesystem
Package: dpkg Version: 1.17.26 Severity: important Dear Maintainer, I have installed my Debian system with a /boot partition on FAT16 because I have a common partition for /boot and UEFI firmware. However, installing the linux-kernel tryes to do a symbolic link as a backup measure before upgrade. Since FAT filesystems do not support symlinks the process fails and the pacakge remains unconfigured. I expect the package to install and issue a warning instead of an error, ask me what to do or I don't know. See output bellow (Romanian, sorry) Unpacking linux-image-3.16.0-4-amd64 (3.16.7-ckt20-1+deb8u4) over (3.16.7-ckt20-1+deb8u3) ... dpkg: error processing archive /var/cache/apt/archives/linux- image-3.16.0-4-amd64_3.16.7-ckt20-1+deb8u4_amd64.deb (--unpack): nu se poate face legătură copie de siguranță lui „./boot/System.map-3.16.0-4-amd64” înainte de instalarea noii versiuni: Operation not permitted dpkg-deb: error: subprocess lipește was killed by signal (Broken pipe) umber Start (sector)End (sector) Size Code Name 12048 1050623 512.0 MiB EF00 EFI System 2 105062417827839 8.0 GiB 8200 Linux swap 317827840 1250263694 587.7 GiB 8300 Linux filesystem -- System Information: Debian Release: 8.3 APT prefers stable APT policy: (900, 'stable'), (400, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=ro_RO.UTF8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-7+b3 ii libc62.19-18+deb8u3 ii liblzma5 5.1.1alpha+20120614-2+b3 ii libselinux1 2.3-2 ii tar 1.27.1-2+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 1.0.9.8.2 -- no debconf information
Bug#816882: ruby-websocket-driver: must depend on ruby-websocket-extensions
Package: ruby-websocket-driver Version: 0.6.3-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, ruby-websocket-driver has missing dependency on ruby-websocket-extensions, so it's impossible to use it. -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=be_BY.utf8, LC_CTYPE=be_BY.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#816883: ITP: ruby-websocket-extensions -- Generic extension manager for WebSocket connections
Package: wnpp Severity: wishlist Owner: Hleb Valoshka <375...@gmail.com> * Package name: ruby-websocket-extensions Version : 0.1.2 Upstream Author : James Coglan * URL : https://github.com/faye/websocket-extensions-ruby * License : Expat Programming Lang: Ruby Description : Generic extension manager for WebSocket connections A minimal framework that supports the implementation of WebSocket extensions in a way that's decoupled from the main protocol. This library aims to allow a WebSocket extension to be written and used with any protocol library, by defining abstract representations of frames and messages that allow modules to co-operate. websocket-extensions provides a container for registering extension plugins, and provides all the functions required to negotiate which extensions to use during a session via the Sec-WebSocket-Extensions header. By implementing the APIs defined in this document, an extension may be used by any WebSocket library based on this framework. We need it to fix #816882.
Bug#803171: this only affects one profile in complaint mode
retitle 803171 torbrowser-launcher: apparmor/usr.bin.torbrowser-launcher should be set to enforce or the profile removed tags 803171 + help user pkg-apparmor-t...@lists.alioth.debian.org usertags 803171 + modify-profile thanks Hi, this bugs also affects a single profile, usr.bin.torbrowser-launcher, so I'm updating the meta data accordingly. Could someone using apparmor (or having access to test setup) please comment whether just setting it to enforce now works or else include the logs here? That would be nice :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#816884: ITP: golang-github-docker-libnetwork -- Docker Networking
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Package name: golang-github-docker-libnetwork Version: 0.5.6 Upstream Author: Docker, Inc. License: Apache-2.0 URL: https://github.com/docker/libnetwork Vcs-Browser: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-docker-libnetwork.git Description: Docker Networking Libnetwork provides a native Go implementation for connecting containers . The goal of libnetwork is to deliver a robust Container Network Model that provides a consistent programming interface and the required network abstractions for applications. signature.asc Description: This is a digitally signed message part.
Bug#675867: debsnap: provide option to specify first and last version to download
Hi, On Fri, Mar 04, 2016 at 07:18:37PM +0100, Samuel Thibault wrote: > Hello, > > Ivo De Decker, on Sun 03 Jun 2012 21:02:24 +0200, wrote: > > Please provide an option to debsnap to specify the first and last version to > > be downloaded. > > I'm not sure how useful it is to get the first version, but I often want > the last version, yes. True but I may want the second from the last version to avoid recent regression :-) As a feature addition strategy for debsnap, I think adding "--list" to list all available versions without download and use it to specify specific version download under existing UI is more generic solution. Regards, Osamu
Bug#808393: severity
severity 808393 normal thanks sslv3 is a deprecated technology https://blog.mozilla.org/security/2014/10/14/the-poodle-attack-and-the-end-of-ssl-3-0/ and the package still works for most of the imap provider. In parallel, I am going to upload a new upstream release, maybe it will fix your problem. Sylvestre
Bug#791463: Quick review
On Sunday 06 March 2016 08:59:53 Andrew Shadura wrote: > On 6 March 2016 at 01:20, Pali Rohár wrote: > > First dpkg-buildpackage call works, but calling it secondary fails > > with: > > > > dpkg-source: info: local changes detected, the modified files are: > > udfclient-0.8.1/Makefile > > > > It is because "debian/rules clean" calls only "bmake clean" which > > does not delete autogenerated file Makefile. That is deleted by > > another target "bmake cleandir". > > > > So version 20150606-2 still does not work for udfclient. > > > > Now I think that I should stay with my implementation which is > > working instead experimenting with --buildsystem=bmake.. > > For that, there's debian/clean, where you delete the autogenerated > file, just as you'd do if you had autoconf+gmake. But should not be cleandir part of that --buildsystem=bmake? Or why not? -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part.
Bug#812459: python3-stem: fails to upgrade from 'testing' - trying to overwrite /usr/bin/tor-prompt
Hi Donncha, Donncha O'Cearbhaill: > This package is marked for autoremoval on the 8th March and the bug has > not received a response from the package maintainer. > > I've attached an NMU patch which I think will resolve this issue. Thanks for the patch! > diff -Nru python-stem-1.4.1b/debian/changelog > python-stem-1.4.1b/debian/changelog > --- python-stem-1.4.1b/debian/changelog 2016-01-18 14:58:04.0 > +0100 > +++ python-stem-1.4.1b/debian/changelog 2016-03-06 00:16:13.0 > +0100 > @@ -1,3 +1,12 @@ > +python-stem (1.4.1b-2.1) unstable; urgency=medium > + > + * Non-maintainer upload. > + * debian/rules: Use update-alternatives to select between > +/usr/bin/tor-prompt for the Python 2 and Python 3 packages > +(Closes: #812459). I don't think alternatives are the solution to this. tor-prompt as provided by python-stem or by python3-stem should be strictly equilavent in terms of features. I can't imagine why would someone prefer to use the Python 2 version when someone else would prefer the Python 3 one. I think either tor-prompt should be moved to its own package, or only kept in python3-stem (because Python 2 will have to go away one day). We can make python-stem Depends on python3-stem to make sure that tor-prompty will continue to be there on upgrade. -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#816192: RFS: python-proselint/0.3.5-1 [ITP] -- A prose linter
On Sun, Feb 28, 2016 at 11:53 PM, Víctor Cuadrado Juan wrote:
> I am looking for a sponsor for my package "python-proselint"
...
> Proselint aggregates knowledge about best practices in writing from world's
> greatest writers and editors, and makes it accessible by giving suggestions in
> the form of a linter for prose.
This sounds useful, thanks for packaging it.
Here is a review:
I can't find a copy of the BSD license grant in the upstream tarball
at all, only in PKG-INFO and setup.py. I'm not sure this is good
enough for ftp-master approval. Please talk to upstream about
including a license grant in a README or in setup.py or something.
They have a LICENSE.md file in their github repository so they
probably just forgot to include it and README.md and other files in
the source distribution.
The upstream test system assumes proselint is installed instead of
testing the code in the source tree.
The proselint command when installed prints a lot of exceptions.
It would be great if upstream would sign their releases using OpenPGP.
https://wiki.debian.org/debian/watch#Cryptographic_signature_verification
https://help.riseup.net/en/security/message-security/openpgp/best-practices
I'm not sure you need separate Python 2 and Python 3 packages. Are
there any users of the proselint Python module apart from the
proselint command-line tool? If not I would just create a proselint
binary package that uses Python 3.
Either way you definitely do not need proselint and proselint3
command-line tools, since they offer identical functionality.
If you decide on a proselint package, it should be Section: text, not
Section: python.
I would suggest to forward the manual page upstream. If they want to
have the manual page automatically generated, the options I know of
include sphinx and sphinxcontrib-autoprogram or
python3-sphinx-argparse.
Upstream may want to add shell completion, which can be done
automatically using python3-argcomplete.
You may want to wrap and sort the debian/ packaging to make diffs
easier to read. I use this:
wrap-and-sort --short-indent --wrap-always --sort-binary-packages
--trailing-comma --verbose
I'm seeing a disturbing amount of calls to subprocess functions with
shell=True or where equivalent Python functions could be used, please
send upstream a patch to avoid using subprocess or call functions from
it without using shell=True. Forking subprocesses is more expensive
than handling it in Python and using shell=True can be potentially
dangerous so it is a bad habit to get into even if it is safe where
used in proselint (if it is not, they need to issue some security
advisories). The Process Identifier Preservation Society will thank
you!
http://bonedaddy.net/pabs3/log/2014/02/17/pid-preservation-society/
http://oss-security.openwall.org/wiki/disclosure/cve
No need for shell=True:
out = subprocess.check_output("proselint --version", shell=True)
subprocess.call("proselint --debug >/dev/null", shell=True)
Potentially dangerous depending on the arguments:
out = subprocess.check_output("proselint {}".format(fullpath), shell=True)
subprocess.call("{} {}".format("open", fullpath), shell=True)
subprocess.call("proselint {} >/dev/null".format(filepath), shell=True)
Use the python equivalents instead:
subprocess.call("find . -name '*.pyc' -delete", shell=True)
subprocess.call("rm -rfv proselint/cache > /dev/null && mkdir -p
{}".format(os.path.join(os.path.expanduser("~"), ".proselint")),
shell=True)
Please add some upstream metadata: https://wiki.debian.org/UpstreamMetadata
Automatic checks:
build:
I: pybuild base:184: cd
/build/python-proselint-0.3.5/.pybuild/pythonX.Y_2.7/build; python2.7
-m unittest discover -v
/bin/sh: 1: proselint: not found
[(1, 15, 'garner.dates', u"When specifying a date range, write 'from X to Y'.")]
Exception TypeError: "'NoneType' object is not callable" in ignored
Exception TypeError: "'NoneType' object is not callable" in ignored
Exception TypeError: "'NoneType' object is not callable" in ignored
Exception TypeError: "'NoneType' object is not callable" in ignored
Exception TypeError: "'NoneType' object is not callable" in ignored
Exception TypeError: "'NoneType' object is not callable" in ignored
Exception TypeError: "'NoneType' object is not callable" in ignored
Exception TypeError: "'NoneType' object is not callable" in ignored
I: pybuild base:184: cd
/build/python-proselint-0.3.5/.pybuild/pythonX.Y_3.5/build; python3.5
-m unittest discover -v
/bin/sh: 1: proselint: not found
lintian:
P: python-proselint source: debian-watch-may-check-gpg-signature
X: python3-proselint: library-package-name-for-application usr/bin/proselint3
X: python3-proselint: application-in-library-section python usr/bin/proselint3
P: python3-proselint: no-upstream-changelog
X: python-proselint: library-package-name-for-application usr/bin/proselint
X: python-proselint: application-in-library-section python usr/bin/proselint
P: python-proselint: no-upstream-changelog
check
Bug#692803: git-pbuilder: does not allow arguments with spaces or special chars to pbuilder
Hi Philipp,
On Fri, Mar 04, 2016 at 03:59:10PM +0100, Philipp Hahn wrote:
> Package: git-buildpackage
> Version: 0.6.22
> Followup-For: Bug #692803
>
> Dear Maintainer,
>
> /usr/bin/git-pbuilder contains:
> > 266 # Add all of the additional arguments we got on the command line, but
> > quote
> > 267 # them from the shell since they'll undergo another round of shell
> > expansion
> > 268 # when the pbuilder runs debbuild.
> ...
> > 270 for arg in "$@" ; do
> ...
> > 274 DEBBUILDOPTS+=" $(shell_quote "$arg")"
> > 275 done
>
> This seems to be right only when *not* using --use-pdebuild-internal, as
>
> /usr/lib/pbuilder/pdebuild-checkparams:
> > 44 »···--debbuildopts)
> > 45 »···DEBBUILDOPTS="${2:+$DEBBUILDOPTS $2}"
> passes the argument unmodified, but then
>
> /usr/bin/pdebuild:
> > 46 if [ "${USE_PDEBUILD_INTERNAL}" = 'yes' ]; then
> > 57 »···--debbuildopts "${DEBBUILDOPTS}" \
> passes on the argument unmodified when using the internal pdebuild, but
>
> > 74 else
> > 78 echo "dpkg-buildpackage -S -us -uc -r${BUILDSOURCEROOTCMD}
> > $DEBBUILDOPTS" | \
> > 80 »···/bin/bash
> does splitting on IFS when not using it.
> > 90 fi
>
>
> For completeness:
>
> /usr/lib/pbuilder/pdebuild-internal:
> > 48 »···--debbuildopts)
> > 50 »···DEBBUILDOPTS="${2:+${DEBBUILDOPTS:+$DEBBUILDOPTS }$2}";
> un-splitted
> > 123 export DEBBUILDOPTS
> > 124 CMD="/usr/bin/dpkg-buildpackage -rfakeroot -us -uc "'${DEBBUILDOPTS}'
> > 128 if echo "$CMD" | \
> > 129 su -p pbuser;·
>
> does *not* spit on IFS, so DEBBUILDOPTS still contains the 's from
> shell_quote() leading to the error
>
> > I: Running /usr/bin/dpkg-buildpackage -rfakeroot -us -uc ${DEBBUILDOPTS}
> > dpkg-buildpackage: unknown option or argument '-sa'
> >
> > Use --help for program usage information.
Could you add examples how you invoke gbp to see the error. Is it just
passing --use-pdebuild-internal as --git-pbuilder-options ?
I do think we need to skip the quoting in this case.
cc'ing Russ since I'm not sure if he's following gbp bugs.
> PS: I still wonder why --use-pdebuild-internal is not the default, as I
> don't want to pollute my development environment with all those build
> dependencies. That makes running "debian/rules clean" sometimes more
> complicate as I'm missing some required dependencies for that, but
> still..."
I just use "-nc" when invoking gbp.
Cheers,
-- Guido
Bug#791463: Quick review
On 6 March 2016 at 09:50, Pali Rohár wrote: >> > It is because "debian/rules clean" calls only "bmake clean" which >> > does not delete autogenerated file Makefile. That is deleted by >> > another target "bmake cleandir". >> > >> > So version 20150606-2 still does not work for udfclient. >> > >> > Now I think that I should stay with my implementation which is >> > working instead experimenting with --buildsystem=bmake.. >> >> For that, there's debian/clean, where you delete the autogenerated >> file, just as you'd do if you had autoconf+gmake. > > But should not be cleandir part of that --buildsystem=bmake? Or why not? You're actually very right in this, I'm going to implement that right now. -- Cheers, Andrew
Bug#791463: Quick review
On Sunday 06 March 2016 10:24:05 Andrew Shadura wrote: > On 6 March 2016 at 09:50, Pali Rohár wrote: > >> > It is because "debian/rules clean" calls only "bmake clean" > >> > which does not delete autogenerated file Makefile. That is > >> > deleted by another target "bmake cleandir". > >> > > >> > So version 20150606-2 still does not work for udfclient. > >> > > >> > Now I think that I should stay with my implementation which is > >> > working instead experimenting with --buildsystem=bmake.. > >> > >> For that, there's debian/clean, where you delete the autogenerated > >> file, just as you'd do if you had autoconf+gmake. > > > > But should not be cleandir part of that --buildsystem=bmake? Or why > > not? > > You're actually very right in this, I'm going to implement that right > now. Ok, but first please check which target should be really tried to be called and in which order... I think on some freebsd system (when using bmake?) is cleandir called two times. But I'm not sure. -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part.
Bug#816885: ITP: golang-github-mattn-go-shellwords -- parse line as shell words in Golang
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Package name: golang-github-mattn-go-shellwords Version: 1.0.0 Upstream Author: Yasuhiro Matsumoto License: Expat URL: https://github.com/mattn/go-shellwords Vcs-Browser: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-mattn-go-shellwords.git Description: parse line as shell words in Golang Parse line as shell words. Based on cpan module Parse::CommandLine (https://metacpan.org/pod/Parse::CommandLine). signature.asc Description: This is a digitally signed message part.
Bug#816886: Duplicate text in description
Package: cups-browsed Version: 1.8.2-3 Severity: minor The APT description contains a duplicate paragraph: cups-browsed is also useful with a CUPS >= 1.6 client to allow the latter to browse the printer list of CUPS < 1.6 servers (by using the old 'cups' protocol in BrowseRemoteProtocols). . cups-browsed is also useful with a CUPS >= 1.6 server to allow CUPS < 1.6 clients to browse its printer list (by using the old 'cups' protocol in BrowseLocalProtocols). -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cups-browsed depends on: ii init-system-helpers 1.29 ii libavahi-client3 0.6.32~rc+dfsg-1 ii libavahi-common3 0.6.32~rc+dfsg-1 ii libavahi-glib1 0.6.32~rc+dfsg-1 ii libc62.21-9 ii libcups2 2.1.3-3 ii libglib2.0-0 2.47.1-1 ii libldap-2.4-22.4.42+dfsg-2+b2 Versions of packages cups-browsed recommends: pn avahi-daemon cups-browsed suggests no packages. -- no debconf information -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#816887: libncursesw5: background color of mutt's message is black
Package: libncursesw5 Version: 6.0+20151017-1 Severity: normal Since ncurses 6.0+20151017-1, background color of mutt's message is black. Downgrading libncursesw5 to 6.0+20150810-1 fixes the issue. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.3 (SMP w/4 CPU cores) Locale: LANG=ja_JP.eucJP, LC_CTYPE=ja_JP.eucJP (charmap=EUC-JP) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libncursesw5 depends on: ii libc6 2.21-9 ii libtinfo5 6.0+20160213-1 Versions of packages libncursesw5 recommends: pn libgpm2 libncursesw5 suggests no packages. -- no debconf information
Bug#816888: libncursesw5: mutt's thread display is broken
Package: libncursesw5 Version: 6.0+20160213-1 Severity: important Since ncurses 6.0+20160213-1, mutt's thread display is broken. Downgrading libncursesw5 to 6.0+20151024-2 fixes the issue. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.3 (SMP w/4 CPU cores) Locale: LANG=ja_JP.eucJP, LC_CTYPE=ja_JP.eucJP (charmap=EUC-JP) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libncursesw5 depends on: ii libc6 2.21-9 ii libtinfo5 6.0+20160213-1 Versions of packages libncursesw5 recommends: pn libgpm2 libncursesw5 suggests no packages. -- no debconf information
Bug#816890: mirrors: Lack of information in the sponsor field gives error on mirror submission.
Package: mirrors Severity: normal This is a bug in the mirror submission form. -- <1457218034.550...@smtp.gmail.com> Hello, I think there is a bug in the mirror submission script. The documentation and the submission form itself states that the Sponsor URL field is an optional field, however, I was unable to submit my mirror until I filled this field. The error message was "Sponsor URL format is http://example.com/";. Greetings, fnkr
Bug#816889: ITP: golang-github-racksec-srslog -- replacement for the standard Golang library "log/syslog"
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Package name: golang-github-racksec-srslog Version: 0.0~git20160120 Upstream Author: Rackspace License: BSD-3-clause URL: https://github.com/RackSec/srslog Vcs-Browser: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-racksec-srslog.git Description: replacement for the standard Golang library "log/syslog" Drop-in replacement for the standard library "log/syslog", but with extra features. signature.asc Description: This is a digitally signed message part.
Bug#816891: jessie-pu: package espeakup/1:0.71-19
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Hello,
I'd like to upload to Jessie the attached changes to the espeakup
package.
The current Jessie debian installer got a bug which made it only support
german, english, french, and portuguese. That is because the file
hierarchy of voices has changed in the updated upstream version, and
they had provided compatibility links, but only for those languages.
The attached change uses a mere recursive grep to find language
identifiers instead of hardcoding the path. That actually allows to drop
the special-casing of the nb language. The change also special cases
gallician, for which we have no native support, but the portuguese voice
should be fine enough, better than english anyway. It also makes the
espeakup daemon select the voice not only by name, but also by property,
just like the espeak program does, which is needed when the voice is
chosen by the language it supports and not by the identifier of the
voice.
Samuel
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'oldoldstable'),
(500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.4.0 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
Samuel
bon comment on fait de l'investigation pour savoir qui est le vilain ?
on débranche le routeur et on regarde qui s'affole
-+- #ens-mim administre -+-
diff --exclude .svn --exclude .git --exclude CVS --exclude .hg -ur
espeakup-0.71-orig/debian/changelog espeakup-0.71/debian/changelog
--- espeakup-0.71-orig/debian/changelog 2016-03-06 10:48:36.0 +0100
+++ espeakup-0.71/debian/changelog 2016-03-06 10:54:47.723787694 +0100
@@ -1,3 +1,15 @@
+espeakup (1:0.71-19+deb8u1) jessie; urgency=medium
+
+ * espeakup-udeb.restart:
+- Make looking up available languages independent from file hierarchy, thus
+fixing all language (but de, en, fr, pt which were still working)... This
+also allows dropping special-casing nb into no.
+- Use portuguese for galician, since they are so close, and portuguese
+will always be better than english anyway.
+ * synth.c: Fix looking up voices by language name.
+
+ -- Samuel Thibault Thu, 31 Dec 2015 15:22:01 +0100
+
espeakup (1:0.71-19) unstable; urgency=medium
* Enable STARTTIME to work around racy daemon start test.
diff --exclude .svn --exclude .git --exclude CVS --exclude .hg -ur
espeakup-0.71-orig/debian/espeakup-udeb.restart
espeakup-0.71/debian/espeakup-udeb.restart
--- espeakup-0.71-orig/debian/espeakup-udeb.restart 2016-03-06
10:48:36.0 +0100
+++ espeakup-0.71/debian/espeakup-udeb.restart 2016-03-06 10:52:14.304762663
+0100
@@ -12,17 +12,17 @@
lang=`echo $locale | sed 's/_.*//'`
country=`echo $locale | sed 's/.*_//;s/\..*//;s/@.*//' | tr A-Z a-z`
-if [ "$lang" = nb ]
+if [ "$lang" = gl ]
then
- lang=no
+# Not supported by espeak yet, but pt should be fine enough, better
than
+# english anyway
+ lang=pt
fi
-if [ -f /usr/lib/*/espeak-data/voices/$lang-$country ] || \
- [ -f /usr/lib/*/espeak-data/voices/$lang/$lang-$country ]
+if grep -r "^language $lang-$country$" /usr/lib/*/espeak-data/voices
then
VOICE="$lang-$country"
-elif [ -f /usr/lib/*/espeak-data/voices/$lang ] || \
- [ -f /usr/lib/*/espeak-data/voices/$lang/$lang ]
+elif grep -r "^language $lang$" /usr/lib/*/espeak-data/voices
then
VOICE="$lang"
else
diff --exclude .svn --exclude .git --exclude CVS --exclude .hg -ur
espeakup-0.71-orig/synth.c espeakup-0.71/synth.c
--- espeakup-0.71-orig/synth.c 2016-03-06 10:48:36.0 +0100
+++ espeakup-0.71/synth.c 2016-03-06 10:51:48.814924736 +0100
@@ -91,6 +91,13 @@
espeak_ERROR rc;
rc = espeak_SetVoiceByName(voice);
+ if (rc != EE_OK)
+ {
+ espeak_VOICE voice_select;
+ memset(&voice_select, 0, sizeof(voice_select));
+ voice_select.languages = voice;
+ rc = espeak_SetVoiceByProperties(&voice_select);
+ }
if (rc == EE_OK)
strcpy(s->voice, voice);
return rc;
Bug#791463: Quick review
On Sunday 06 March 2016 10:28:31 Pali Rohár wrote: > On Sunday 06 March 2016 10:24:05 Andrew Shadura wrote: > > On 6 March 2016 at 09:50, Pali Rohár wrote: > > >> > It is because "debian/rules clean" calls only "bmake clean" > > >> > which does not delete autogenerated file Makefile. That is > > >> > deleted by another target "bmake cleandir". > > >> > > > >> > So version 20150606-2 still does not work for udfclient. > > >> > > > >> > Now I think that I should stay with my implementation which is > > >> > working instead experimenting with --buildsystem=bmake.. > > >> > > >> For that, there's debian/clean, where you delete the > > >> autogenerated file, just as you'd do if you had autoconf+gmake. > > > > > > But should not be cleandir part of that --buildsystem=bmake? Or > > > why not? > > > > You're actually very right in this, I'm going to implement that > > right now. > > Ok, but first please check which target should be really tried to be > called and in which order... I think on some freebsd system (when > using bmake?) is cleandir called two times. But I'm not sure. See: http://www.freebsd.org/cgi/man.cgi?build(7) -- Pali Rohár pali.ro...@gmail.com signature.asc Description: This is a digitally signed message part.
Bug#811377: [Pkg-sysvinit-devel] Adopting Sysvinit
[Simon Richter] > Hi, Hi. I would be happy for skilled people with more time to take over the maintenance. I would be happy to help with the knowledge I got, but lack the time required to do a good job maintaining the sysvinit, insserv and startpar package. Note that all three belong together and should be maintained by the same group. I can approve members to the alioth project. > It seems Ben's mail didn't make it to the maintainers' mailing list. I'm > going to poke a few people individually now. I just approved them. -- Happy hacking Petter Reinholdtsen
Bug#816891: jessie-pu: package espeakup/1:0.71-19
Samuel Thibault, on Sun 06 Mar 2016 11:21:24 +0100, wrote: > I'd like to upload to Jessie the attached changes to the espeakup > package. I forgot to mention that these changes have been well tested in debian sid, and checked again with the jessie installer. Samuel
Bug#816879: transition: libtommath
Control: tags -1 confirmed On 06/03/16 08:25, Dominique Dumont wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hello > > libtommath 1.0 has been released upstream. The new library went > from so version 0 to 1. Some macros like MIN and MAX were removed > from the public header files. This may break compilation. > > libtommath 1 was uploaded in experimental and builds fine on all > supported arch: > https://buildd.debian.org/status/package.php?p=libtommath&suite=experimental&comaint=yes > > Affected reversed dependencies are: > > * convlit, libtomcrypt: > rebuild ok, needs binNMU > > * moarvm, rakudo: > I maintain theses packages and a new version is ready > > * firebird3: > only in experimental. I've warned the maintainer of > the incoming change Go ahead. Emilio
Bug#816892: debootstrap synchronize the whole filesystem
Package: debootstrap Version: 1.0.79 Severity: normal Tags: patch Sync at the end of debootstrap sometimes takes for a while. It seems enough to synchronize only a target filesystem. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.3 (SMP w/4 CPU cores) Locale: LANG=ja_JP.eucJP, LC_CTYPE=ja_JP.eucJP (charmap=EUC-JP) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages debootstrap depends on: ii wget 1.17.1-1+b1 Versions of packages debootstrap recommends: ii debian-archive-keyring 2014.3 ii gnupg 1.4.20-4 debootstrap suggests no packages. -- no debconf information diff -uNrp debootstrap-1.0.79.orig/debootstrap debootstrap-1.0.79/debootstrap --- debootstrap-1.0.79.orig/debootstrap 2015-11-09 13:01:25.0 +0900 +++ debootstrap-1.0.79/debootstrap 2016-03-06 19:22:04.970728229 +0900 @@ -686,7 +686,7 @@ if am_doing_phase second_stage; then mv "$TARGET/debootstrap/debootstrap.log" "$TARGET/var/log/bootstrap.log" fi fi - sync + sync -f "$TARGET" if [ "$KEEP_DEBOOTSTRAP_DIR" = true ]; then if [ -x "$TARGET/debootstrap/debootstrap" ]; then
Bug#811377: [Pkg-sysvinit-devel] Adopting Sysvinit
Hi, On 06.03.2016 11:30, Petter Reinholdtsen wrote: > I can approve members to the alioth project. Okay, I think it makes the most sense to use the Alioth project then, I've just applied to become a member of the project. Should we schedule a "bug fixing weekend" at some point to get the number of open bugs down? I also plan to add a few tests on Jenkins -- specifically - check that transitioning from and to systemd works - check that debootstrap with sysvinit works, without having to boot into systemd - check that debootstrap default installation doesn't break Simon signature.asc Description: OpenPGP digital signature
Bug#816497: closed by m...@debian.org (Manuel A. Fernandez Montecelo) (Bug#816497: fixed in aptitude 0.7.8-1)
Thanks Manuel, "aptitude (un)markauto" works now with version 0.7.8-1. I've made another observation: all systems I administer are amd64, mainly multi-core, only one unicore machine with almost the same package list on these systems. Every multi-core machine has several ten "Auto-New-Install" entries in /var/lib/aptitude/pkgstates, the unicore machine has none. Best regards, Jörg-Volker.
Bug#816466: Processed: reopening 816466 ...
Hi
Dne 5.3.2016 v 00:54 Debian Bug Tracking System napsal(a):
> Processing commands for cont...@bugs.debian.org:
>
>> reopen 816466
> Bug #816466 {Done: Michal Čihař } [phpmyadmin] I had to
> additionally install libapache2-mod-php7 to get it working.
> Bug reopened
> Ignoring request to alter fixed versions of bug #816466 to the same values
> previously set
>> retitle 816466 I had to additionally install libapache2-mod-php7.0 to get it
>> working
> Bug #816466 [phpmyadmin] I had to additionally install libapache2-mod-php7 to
> get it working.
> Changed Bug title to 'I had to additionally install libapache2-mod-php7.0 to
> get it working' from 'I had to additionally install libapache2-mod-php7 to
> get it working.'
>> thanks
> Stopping processing here.
Can you please explain what do you expect? The libapache2-mod-php7.0 is
in the dependencies, actually after fixing #816462 it's the first one.
There is nothing more we can do.
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
signature.asc
Description: OpenPGP digital signature
Bug#816893: new upstream (3.1.2)
Package: rsync Severity: wishlist Hi, it would be nice if you could upgrade to the current upstream version (3.1.2). Regards, Daniel
Bug#812078: Aw: Re: Bug#812078: eric: got a lot of errors: DictWithPWL unusable
Hi Stefan > I use Debian Jessie not wheezy ;) Sorry, one of my silly mistakes. > I'ce no installed the latest version from eric6 website and it works now.. > I think there is a problem with the Editor -> Autocompletion/Calltips -> > QScintilla Now I have installed jessie but I still cannot reproduce your bugs with Editor->Autocompletion/Calltips enabled. Do you have time to give me some more information? Regards Gudjon
Bug#498383: Add tag support for debhelper files
Control: reassign -1 dh-exec Control: tags -1 -patch Hi, I am reassigning this feature request to dh-exec, because it is the primary interface for fancy filtering the debhelper config files at the moment. I am not aware if dh-exec already supports particular filter. The original request is quoted in full beyond for the convenience of the dh-exec maintainer (excl. the original patch, which will not apply to dh-exec). Thanks, ~Niels On Tue, 09 Sep 2008 17:22:21 +0200 Goswin von Brederlow wrote: > Package: debhelper > Version: 8.0.0~mrvn.1 > Severity: wishlist > Tags: patch > > Hi, > > during the recent emDebian work session in Extremadura we talked about > how to reduce the amount of patching emDebian has to do on debhelper > files due to using special DEB_BUILD_OPTIONS (specifically nodoc). The > problem is that depending on DEB_BUILD_OPTIONS the amount of files > debhelper should act upon varies. > > The solution we came up with is to tag lines and let debhelper match > those tags against DEB_BUILD_OPTIONS and some DEB_HOST_*. That way > lines can be made conditional. > > The syntax is fairly simple. Tags are single words that can be > prefixed by ! to negate the match. A list of tags is tags seperated by > space. A line can be tagged by prefixing it with a list of tags > enclosed in []: > > [tag1 !tag2 tag3] source [] > > A list of tags matches if all tags are present in DEB_BUILD_OPTIONS > (or not for !) and then the source [] pair is used. Otherwise > the line is ignored. Lines without tag are always used. > > > Using the tags the same debhelper files can be used for normal builds > and builds with DEB_BUILD_OPTIONS=nodoc once the respective doc files > have been tagged [!nodoc]. > > MfG > Goswin > > [...] signature.asc Description: OpenPGP digital signature
Bug#816183: iceowl-extension: cannot create new calendar
Hi Carsten, Thanks for the help. It seems to be an add-on. With this add-on disabled it works again On 03/05/2016 10:07 AM, Carsten Schoenert wrote: Hi, On Sun, Feb 28, 2016 at 02:11:02PM +0100, wforumw wrote: When I try to create a new calendar, the 'Create New Calendar' window appears but is totally empty. (see attachment) You can fill in nothing. The only buttons on the bottem are Cancel, Back and Finish. Back and Finish doesn't do anything, Cancel let the windows disappear. I can't reproduce your issue. For me all works as expected netherless I use my various clients or I create new profiles. Did you check the behaviour with disabled plugins and/or a new profile? Is there something visible in the JS console (Ctrl+Shif+J) related to that issue? Have you tried to start icedove from a terminal and look there for some output? Note also the hints within the Debian wiki. https://wiki.debian.org/Icedove#Debugging_Icedove_Activity Regards Carsten
Bug#816272: [Pkg-clamav-devel] Bug#816272: clamav-freshclam: logrotate errors out with "gzip: stdin: file size changed while zipping"
2016-03-05 23:07 GMT+01:00 Sebastian Andrzej Siewior :
> every other? I assumed twice a day.
That's correct, of course, my mistake.
> Btw: is this the cron/ anacron package or systemd's cron stuff?
just plain cron (3.0pl1-127+deb8u1)
> When you select `cron' in debconf then it will roll the big dice
Tried that yesterday, result:
18 */12 * * *clamav [ -x /usr/bin/freshclam ] &&
/usr/bin/freshclam --quiet >/dev/null
It now runs at 18 past noon and midnight, but I still got a
(different) error e-mail this morning:
/etc/cron.daily/logrotate:
error: error running non-shared postrotate script for
/var/log/clamav/freshclam.log of '/var/log/clamav/freshclam.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1
Maybe that's just an artefact of the recent debconf run, we'll see in a week.
> So *I* really think just adding the extra option to lograte is the simplest
> thing to do.
I'd love to but it is already in there as standard:
/var/log/clamav/freshclam.log {
rotate 12
weekly
compress
delaycompress
missingok
create 640 clamav adm
postrotate
if [ -d /run/systemd/system ]; then
systemctl -q is-active clamav-freshclam && systemctl kill
--signal=SIGHUP clamav-freshclam
else
/etc/init.d/clamav-freshclam reload-log > /dev/null
fi
endscript
}
Christian
Bug#816894: RFP: foreman-ansible-inventory -- Foreman dynamic inventory script for ansible
Package: wnpp Severity: wishlist * Package name: foreman-ansible-inventory Version : 0.0.1 * URL : https://github.com/theforeman/foreman_ansible_inventory * License : GPL Programming Lang: Python Description : Foreman dynamic inventory script for ansible This script retrieves hosts and their configuration out of a Foreman instance in a foremat suitable as a ansible dynamic inventory. We don't have Foreman in Debian (yet) but ansible is there and therefore it's useful with remote foreman remote instances.
Bug#815408: gscan2pdf: fails to record some settings when saving profile
On 6 March 2016 at 03:14, Gerry Butler wrote: > I have only recently started using gscan2pdf, and I may have a > misunderstanding > about how profiles should be used. Following is the way I assumed I could > use them: > > (1) Suppose I always want to scan business cards with 24bit colour, > 200 dpi, flat-bed, 90mm x 60mm. > > (2) I have just been scanning A4 pages with gray scale, 150 dpi, adf central > align, > 210 x 297 mm > > (3) I assume I can re-load a previously saved profile, called "business > card", which will > set everything to my desired values. > > (4) But it can't, because when I saved "business card" profile, it did not > record mode or > resolution, as they were already 24bit colour and 200 dpi when I saved it. > > (5) I can make it save mode and resolution in the "business card" profile by > making > sure I change every setting before saving the "business card" profile, but > that > seems more awkward than it should be. I take your point, and I don't think you have misunderstood things. > I have submitted a related bug report about failure to set geometry to 90mm > x 60mm, > although these values are recorded in the profile. This may also be a > misunderstanding on my part. No. I think I have fixed that with the v1.3.9 release. Please test and let me know. > My scanner is brother MFC-8890DW. It shows only a few settings: mode, > resolution, > source (flatbed, adf, etc), geometry. > Perhaps a partial solution might be to save only the common options, or > those > not requiring a restart. I am willing to devote some time to experimenting > with settings and options, if that will assist you. Thanks for the offer. The SANE library doesn't really have common option names. Perhaps mode, resolution, the geometry options and source are, but most backends require a reload on setting mode or source. Perhaps when saving a profile, an additional dialog would be useful: "You have changed options a,b,c. These will be stored in the profile. Please select any additional options you would like stored in this profile". Either that, or perhaps a setting in Edit/Preferences to either store profiles with the current behaviour, or with all available options.
Bug#816895: RFP: telify - Firefox / Iceweasel plugin, makes all phone numbers on a page clickable
Package: wnpp Severity: wishlist https://addons.mozilla.org/en-us/firefox/addon/telify/ http://www.codepad.de/en/software/firefox-add-ons/telify.html Copied from web site: Version:1.3.1 Updated:October 23, 2012 Works with: Mozilla Firefox 3.0 - 18.0 Mozilla Thunderbird 3.0 - 18.0 Platforms: Windows, Mac OS X and Linux Languages: English, French, German License:Creative Commons BY-ND Note: BY-ND is a non-free license so this package should go in non-free, not main: https://lists.debian.org/debian-legal/2013/08/msg00015.html unless somebody is willing to rewrite the code and release it under a free license.
Bug#814083: RFS: kwstyle/1.0.1+git3224cf2-1 [ITA]
Hi Mattia, On Wednesday 02 March 2016 13:16:14 Mattia Rizzolo wrote: > control: owner -1 ! > control: tag -1 moreinfo > > Hi Benjamin! > > On Sat, Feb 06, 2016 at 07:15:04PM +0100, Benjamin Eikel wrote: > > I am looking for a sponsor for my package "kwstyle" > > Cool, I'm available to review and sponsor this :) thank you for the interest in sponsoring the package! > > > You can find the current state of my packaging work at > > https://github.com/eikel/KWStyle-Debian > yay, git! I'll work with that, everything is easier with git. > Since you don't seem to have access to collab-maint, I'm happy to repush > there everything once this upload is done :) > I'm sadly not willing to advocate for collab-maint access in this case. > > > Let's start the fun! > > * This is a nice update, cool work! > * please revert b6963ab31cd4dddb922471da7ae190790c7ed2b2, cme did the > right thing, the current version of policy is 3.9.7. > * in d/rules those lines are useless, please remove them: > DPKG_EXPORT_BUILDFLAGS = 1 > include /usr/share/dpkg/default.mk > You should read debhelper(7), in particular the changes done with > compat level 9. > * unused-file-paragraph-in-dep5-copyright paragraph at line 192 > + that's because those files are also reported on the next paragraph, > with different copyright; please meld the paragraphs > * can you consider enabling hardening buildflags? > * at the end of the iteration please bump the changelog entry I worked on all the points on your list and pushed my changes to the aforementioned GitHub repository. Please review them and give feedback. Kind regards Benjamin signature.asc Description: This is a digitally signed message part.
Bug#816896: xul-ext-ublock-origin: Doesn't install anything on conkeror
Package: xul-ext-ublock-origin Version: 1.6.0+dfsg-1 Severity: normal Dear Maintainer, Installing this package adds ublock-origin to firefox but not conkeror - the package info at least implies that it does. Reinstalling conkeror make no difference. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-rc8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xul-ext-ublock-origin depends on: ii conkeror1.0~~pre-1+git160130-1 ii fonts-font-awesome 4.5.0~dfsg-1 ii iceweasel 44.0.2-1 xul-ext-ublock-origin recommends no packages. xul-ext-ublock-origin suggests no packages. -- no debconf information
Bug#816897: sbuild --build-dep-resolver=aptitude will install packages from untrusted sources
Package: sbuild Version: 0.68.0-1 Severity: serious Tags: security sbuild --build-dep-resolver=aptitude will install packages from untrusted sources. I'm building a backports of dune-geometry in a freshly created jessie-backports chroot. For this I added a local apt repository deb file:///srv/apt/ansgar/pub jessie-backports main to the chroot's sources.list (there is a bind mount setup too). The signing key was *not* installed yet (as I forgot to do so). Building the package with $ /usr/bin/sbuild -j8 -d jessie-backports -A \ --build-dep-resolver=aptitude dune-geometry_2.4.1-1~bpo8+1.dsc made apt in the chroot complain as expected: +--- | W: GPG error: file: jessie-backports InRelease: The following signatures | couldn't be verified because the public key is not available: | NO_PUBKEY 4618504DFB3AD1E0 +--- But to my surprise, the aptitude solver went on to install packages from there: +--- | aptitude -y --without-recommends -o Dpkg::Options::=--force-confold | -o Aptitude::CmdLine::Ignore-Trust-Violations=false [...] | install sbuild-build-depends-dune-geometry-dummy:amd64 | [...] | The following actions will resolve these dependencies: | | Install the following packages: | 1) libdune-common-dev [2.4.1-1~bpo8+1 ()] | [...] | Selecting previously unselected package libdune-common-dev:amd64. | Preparing to unpack .../libdune-common-dev_2.4.1-1~bpo8+1_amd64.deb ... | Unpacking libdune-common-dev:amd64 (2.4.1-1~bpo8+1) ... | [...] | Setting up libdune-common-dev:amd64 (2.4.1-1~bpo8+1) ... | [...] | Package versions: [...] libdune-common-dev_2.4.1-1~bpo8+1 [...] +--- I'm not sure if this is an issue with sbuild calling aptitude or with aptitude. Feel free to reassign to aptitude (aptitude 0.6.11-1+b1 was installed in the chroot). (This was before the dune-common backport reached the archive.) Ansgar -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (100, 'buildd-unstable'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sbuild depends on: ii adduser 3.113+nmu3 ii apt-utils 1.2.4 ii libsbuild-perl 0.68.0-1 ii perl5.22.1-7 Versions of packages sbuild recommends: ii debootstrap 1.0.79 ii fakeroot 1.20.2-1 Versions of packages sbuild suggests: pn deborphan ii wget 1.17.1-1+b1 -- no debconf information
Bug#816858: Logical volumes on external USB disk cause boot to enter emergency shell
Hello, > I have no idea what you mean with "logical volumes cannot be found". It means that the logical volume device nodes are listed in /etc/fstab, but the filesystems cannot be mounted because the device nodes are not present. > If > devices may be missing, please make sure that the fstab entry includes > "nofail". That is no option, because mounting the filesystems is necessary for the computer to work as required. > > Please show full logs and please test with a current version, something > like 2.02.142. Upgrading to a newer version did not help. I have attached the output of dmesg directly after entering the emergency shell. Regards Christoph Pleger[0.00] Booting Linux on physical CPU 0x0 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.16.0-4-armmp (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) [0.00] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine model: Wandboard i.MX6 Quad Board [0.00] Memory policy: Data cache writealloc [0.00] On node 0 totalpages: 524288 [0.00] free_area_init_node: node 0, pgdat c09de940, node_mem_map ee7f8000 [0.00] DMA zone: 1520 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 194560 pages, LIFO batch:31 [0.00] HighMem zone: 2576 pages used for memmap [0.00] HighMem zone: 329728 pages, LIFO batch:31 [0.00] PERCPU: Embedded 9 pages/cpu @ee7b3000 s12608 r8192 d16064 u36864 [0.00] pcpu-alloc: s12608 r8192 d16064 u36864 alloc=9*4096 [0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 522768 [0.00] Kernel command line: console=ttymxc0,115200 apparmor=1 security=apparmor quiet init=/lib/sysvinit/init [0.00] PID hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Memory: 2054716K/2097152K available (6413K kernel code, 829K rwdata, 2204K rodata, 688K init, 393K bss, 42436K reserved, 1318912K highmem) [0.00] Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xffc0 - 0xffe0 (2048 kB) vmalloc : 0xf000 - 0xff00 ( 240 MB) lowmem : 0xc000 - 0xef80 ( 760 MB) pkmap : 0xbfe0 - 0xc000 ( 2 MB) modules : 0xbf00 - 0xbfe0 ( 14 MB) .text : 0xc0008000 - 0xc0872938 (8619 kB) .init : 0xc0873000 - 0xc091f140 ( 689 kB) .data : 0xc092 - 0xc09ef610 ( 830 kB) .bss : 0xc09ef610 - 0xc0a51b34 ( 394 kB) [0.00] Hierarchical RCU implementation. [0.00] RCU dyntick-idle grace-period acceleration is enabled. [0.00] NR_IRQS:16 nr_irqs:16 16 [0.00] L2C-310 erratum 769419 enabled [0.00] L2C-310 enabling early BRESP for Cortex-A9 [0.00] L2C-310 full line of zeros enabled for Cortex-A9 [0.00] L2C-310 ID prefetch enabled, offset 1 lines [0.00] L2C-310 dynamic clock gating enabled, standby mode enabled [0.00] L2C-310 cache controller enabled, 16 ways, 1024 kB [0.00] L2C-310: CACHE_ID 0x41c7, AUX_CTRL 0x76070001 [0.00] Switching to timer-based delay loop [0.06] sched_clock: 32 bits at 66MHz, resolution 15ns, wraps every 65075262448ns [0.002098] Console: colour dummy device 80x30 [0.002127] Calibrating delay loop (skipped), value calculated using timer frequency.. 132.00 BogoMIPS (lpj=264000) [0.002142] pid_max: default: 32768 minimum: 301 [0.002271] Security Framework initialized [0.002316] AppArmor: AppArmor initialized [0.002326] Yama: disabled by default; enable with sysctl kernel.yama.* [0.002401] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [0.002416] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [0.003322] Initializing cgroup subsys memory [0.003349] Initializing cgroup subsys devices [0.003389] Initializing cgroup subsys freezer [0.003409] Initializing cgroup subsys net_cls [0.003441] Initializing cgroup subsys blkio [0.003469] Initializing cgroup subsys perf_event [0.003484] Initializing cgroup subsys net_prio [0.003559] CPU: Testing write buffer coherency: ok [0.003589] ftrace: allocating 23120 entries in 68 pages [0.041431] CPU0: thread -1, cpu 0, socket 0, mpidr 8000 [0.041723] Setting up static identity map for 0x105c2418 - 0x105c2470 [0.051939] CPU1: Booted secondary processor [0.051974] CPU
Bug#816096: initramfs-tools: Error reporting false missing dependancy on busybox
On Sat, Mar 5, 2016 at 9:53 PM, Christophe wrote: > > Hi, > Sorry for the delay. I re-checked, and both packages were *not* installed! I > gave a try with busybox-static and it does fix the problem. I also gave a try > setting BUSYBOX=n in the initramfs.conf file, which also works. > > So this makes me wonder: > - if it is a (new) design choice to use Busybox, shouldn't it be added as a > dependency? > - if not, shouldn't the variable be automatically set, with something like: > > if [ -x /bin/busybox ]; then > BUSYBOX=y > else > BUSYBOX=n > fi As Ben always says, please read the NEWS. If you didn't while upgrading initramfs-tools, it's placed under /usr/share/doc/initramfs-tools/ Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
Bug#800752: RFA: newsbeuter -- text mode rss feed reader with podcast support
retitle 800752 ITA: newsbeuter -- text mode rss feed reader with podcast support owner 800752 ! thanks I have been using newsbeuter on and off for about a year and I'm interested in adopting it. Regards, Nikos Tsipinakis
Bug#816898: qsapecng: Segfaults on exit and missing Qt-signals
Package: qsapecng Version: 2.0.0-8 Severity: normal The program segfaults on exit and the following signals are missing: Object::connect: No such signal QwtPlotPicker::selected(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::appended(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::moved(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::selected(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::appended(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::moved(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::selected(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::appended(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::moved(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::selected(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::appended(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::moved(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::selected(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::appended(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::moved(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::selected(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::appended(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::moved(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::selected(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::appended(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::moved(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::selected(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::appended(const QwtDoublePoint&) Object::connect: No such signal QwtPlotPicker::moved(const QwtDoublePoint&) This package depends on libqwt which will be upgraded to version 6.1.2 soon. I have compiled qsapecng agains the new libqwt and got exactly the same behaviour. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init
Bug#816886: Duplicate text in description
On Sun 06 Mar 2016 at 10:37:26 +0100, martin f krafft wrote: > The APT description contains a duplicate paragraph: One paragraph is not a duplicate of the other. Please note the distinction made between a client and a server (and the versions) and the different directives used in cups-browsed.conf. Perhaps the cups README.Debian will make things clearer. > cups-browsed is also useful with a CUPS >= 1.6 client to allow the > latter to browse the printer list of CUPS < 1.6 servers (by using > the old 'cups' protocol in BrowseRemoteProtocols). A CUPS < 1.6 server does not have native Bonjour broadcasting using Avahi; broadcasting with the CUPS protocol is the only choice. A CUPS >= 1.6 client would need BrowseRemoteProtocols cups for the remote queues to be visible on the client. > cups-browsed is also useful with a CUPS >= 1.6 server to allow CUPS > < 1.6 clients to browse its printer list (by using the old 'cups' > protocol in BrowseLocalProtocols). A CUPS >= 1.6 server does have native Bonjour broadcasting using Avahi and its queues will automatically be advertised that way. However, a CUPS < 1.6 client can only browse queues advertised with the CUPS protocol. cups-browsed can cause the server to do CUPS broadcasing with BrowseLocalProtocols cups Regards, Brian.
Bug#816899: net backend no longer works since upgrade to jessie
Package: sane-utils Version: 1.0.25+git20150927-1 Severity: important Since I upgraded our "scan server" to jessie (sane-utils 1.0.22.7-4 to 1.0.24-8), clients cannot use it via the network anymore. Suffice it to say that scanimage -L locally still works, but that's accessing the device directly and not going via saned. When a client makes a request (scanimage -L), they are told that no scanners were identified, but this happens after a successful conversation with the server: % SANE_DEBUG_NET=255 scanimage -L [sanei_debug] Setting debug level of net to 255. [net] sane_init: authorize != null, version_code != null [net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6) from sane-backends 1.0.25git [net] sane_init: Client has little endian byte order [net] sane_init: searching for config file [net] sane_init: trying to add scanner [net] add_device: adding backend scanner [net] add_device: backend scanner added [net] sane_init: done reading config [net] sane_init: evaluating environment variable SANE_NET_HOSTS [net] sane_init: evaluating environment variable SANE_NET_TIMEOUT [net] sane_init: done [net] sane_get_devices: local_only = 0 [net] connect_dev: trying to connect to scanner [net] connect_dev: [0] connection succeeded (IPv6) [net] connect_dev: sanei_w_init [net] connect_dev: net_init (user=madduck, local version=1.0.3) [net] connect_dev: freeing init reply (status=Success, remote version=1.0.3) [net] connect_dev: done [net] sane_get_devices: finished (0 devices) No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [net] sane_exit: exiting [net] net_avahi_cleanup: stopping thread [net] net_avahi_cleanup: done [net] sane_exit: closing dev 0x562a410df020, ctl=126 [net] sane_exit: finished. The server sees the request and authorizes it based on the subnet: # saned -d [saned] main: starting debug mode (level 2) [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up [saned] check_host: access by remote host: 2001:a60:f0fb:0:2ad2:44ff:fe8c:5bd [saned] init: access granted to madduck@2001:a60:f0fb:0:2ad2:44ff:fe8c:5bd [saned] bailing out, waiting for children... [saned] bail_out: all children exited Even if I crank up debug level on the server to 255 (-d255), I don't get any additional information, other than the following four lines before it says "bailing out": [saned] process_request: waiting for request [saned] process_request: got request 1 [saned] process_request: waiting for request [saned] process_request: got request 10 I cannot access the scanner via the net backened from localhost either, so firewalling is also not in the way. Apart, I've verified that the daemon listens on the right sockets, and the port is open all the way between clients and process. To me, it looks like saned is either not seeing any scanners, or not passing them on. However, the saned user can access the device just fine (su -c 'scanimage -L' saned) and running saned as root also doesn't improve things. In short, either something drastically changed without a corresponding NEWS.Debian entry, or something broke. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sane-utils depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.58 ii init-system-helpers1.29 ii libavahi-client3 0.6.32~rc+dfsg-1 ii libavahi-common3 0.6.32~rc+dfsg-1 ii libc6 2.21-9 ii libieee1284-3 0.2.11-12 ii libjpeg62-turbo1:1.4.2-2 ii libsane1.0.25+git20150927-1 ii libsystemd0229-2 ii libusb-1.0-0 2:1.0.20-1 ii update-inetd 4.43 sane-utils recommends no packages. Versions of packages sane-utils suggests: pn avahi-daemon ii unpaper 6.1-1 -- no debconf information -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#787297: needrestart: allow users to disable/control notifications
tags 787297 upstream fixed-upstream thanks Hi, On Sun, May 31, 2015 at 07:38:33AM +0200, Christoph Anton Mitterer wrote: > This would mean that root and other users get notifications > about stuff needed to be restarted, either when run manually, > via apt, or e.g. via cron (should something like be implemented). > > > This also means that each user should get a way to disable > these notifications for him and perhaps to control how > he want's to get such notifications. > This could be done via a ~/.needrestart.conf . in needrestart 2.7 it is possible to disable the default notify scripts by editing /etc/needrestart/notify.conf. The notification configuration is used for all users - it is currently not possible to let the user select a method. It is intentional to not read a config file from the users home directory due to security concerns. HTH, Thomas -- :: WWW:https://fiasko-nw.net/~thomas/ :: ::: Jabber: xmpp:tho...@jabber.fiasko-nw.net ::: :: flickr: https://www.flickr.com/photos/laugufe/ ::
Bug#816858: Logical volumes on external USB disk cause boot to enter emergency shell
On Sun, Mar 06, 2016 at 01:16:21PM +0100, Christoph Pleger wrote: > I have attached the output of dmesg directly after entering the emergency > shell. dmesg does not help, as it does not show the errors by lvm and systemd. The complete content of the journal since boot (via journalctl) should be enough. > [5.382082] scsi 1:0:0:0: Direct-Access WD Ext HDD 1021 2002 > PQ: 0 ANSI: 4 > [5.425786] sd 1:0:0:0: [sda] 1953519616 512-byte logical blocks: (1.00 > TB/931 GiB) > [5.426974] sd 1:0:0:0: [sda] Test WP failed, assume Write Enabled > [5.428095] sd 1:0:0:0: [sda] Asking for cache data failed > [5.433628] sd 1:0:0:0: [sda] Assuming drive cache: write through > [5.910813] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl > 0x50 > [ 17.501163] sda: sda1 sda2 sda3 sda4 > [ 17.531490] sd 1:0:0:0: [sda] Attached SCSI disk > [ 17.548154] sd 1:0:0:0: Attached scsi generic sg0 type 0 This just shows that this device take aweful long time to respond. But nothing that is above the timeout. Bastian -- Change is the essential process of all existence. -- Spock, "Let That Be Your Last Battlefield", stardate 5730.2
Bug#816228: Don't include in stretch
To record it in #816228: A tracker page for the removal was set up as https://release.debian.org/transitions/html/jasper-rm.html Regards, Salvatore
Bug#816900: RFP: libdigest-elf-perl -- Perl extension for ELF hash function
Package: wnpp Severity: wishlist * Package name: libdigest-elf-perl Version : 1.42 Upstream Author : Steve McKay * URL : https://metacpan.org/release/Digest-Elf * License : MIT Programming Lang: Perl Description : Perl extension for ELF hash function This Perl module provides a fast implementation of the ELF hash function. It is a stable module and seems to be an ideal candidate for packaging. I plan to maintain this package under the umbrella of the Debian Perl Group (nickm-guest). Cheers, Nick
Bug#816901: RM: owncloud-news -- ROM; Not Debian material
Package: ftp.debian.org Severity: normal Control: clone -1 -2 Retitle: -2 RM: owncloud-documents -- ROM; Not Debian material Hi, Thank you for removing every owncloud-* packages from experimental via #816769. Two more packages depending on owncloud (>= 8) already made it in unstable, can you please take care of them too? As per #816376, owncloud will not be part of Stretch, so there is no point keeping the current WIP. Regards David signature.asc Description: PGP signature
Bug#816903: reportbug: package dependencies listed as but they are installed
Package: reportbug Version: 6.6.6 Severity: normal i notice that many packages used with reportbug show dependencies listed as but they are installed i.e. all 3 below report not installed Package: debsums State: installed Automatically installed: no Version: 2.1.2 Package: python-gtk2 State: installed Automatically installed: no Version: 2.24.0-4 but $ aptitude show dlocate No current or candidate version found for dlocate Package: dlocate State: not a real package not consistent ... ? -- Package-specific info: ** Environment settings: INTERFACE="gtk2" ** /home/fulano/.reportbugrc: reportbug_version "6.6.6" mode standard ui gtk2 offline realname "Fulano Diego Perez" email "fulanope...@cryptolab.net" smtphost "mail.autistici.org" smtpuser "fulanope...@cryptolab.net" smtptls http_proxy "http://127.0.0.1:8118"; -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt 1.2.3 ii python-reportbug 6.6.6 pn python:any reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums pn dlocate pn emacs23-bin-common | emacs24-bin-common ii exim4 4.86-7 ii exim4-daemon-light [mail-transport-agent] 4.86-7+b2 ii file 1:5.25-2 ii gnupg 1.4.20-4 pn python-gtk2 pn python-gtkspellcheck ii python-urwid 1.3.1-2 ii python-vte 1:0.28.2-5+b1 pn xdg-utils Versions of packages python-reportbug depends on: ii apt 1.2.3 ii file 1:5.25-2 ii python-debian 0.1.27 ii python-debianbts 2.6.0 pn python:any python-reportbug suggests no packages. -- no debconf information
Bug#816904: future of make-ssl-cert now that we have letsencrypt
Package: ssl-cert Version: 1.0.35 Severity: wishlist Should the make-ssl-cert script continue doing the same thing, creating Snakeoil certs only? Or should it be extended to give the user the option of using letsencrypt? If this is added, any packages already relying on make-ssl-cert will automatically be configured with letsencrypt Some discussion of Let's Encrypt and related issues occurred here: https://lists.debian.org/debian-devel/2015/08/msg7.html
Bug#802306: packagekitd eating up RAM
Hi Matthias, On Sat, 13 Feb 2016 16:33:05 +0100, Matthias Klumpp wrote: > Can you check if this issue still appears with the latest PackageKit > in unstable (v1.1.0)? > I fixed a few minor memory leaks that I found, and there are also a > few other changes which might have an impact on this - although I am > still a bit in the dark on why this issue happens at all (still can't > reproduce it :-/). Sorry for the lack of response, I haven't had the time to look into this in detail. But it looks like the memory leak is fixed, I have a two-week-old packagekitd process only using 33MB of RAM. Regards, Stephen pgpAJIkclTj3R.pgp Description: OpenPGP digital signature
Bug#816906: ITP: ruby-mathgl -- Ruby wrapper of MathGL
Package: wnpp Owner: Youhei SASAKI Severity: wishlist * Package name: ruby-mathgl Version : 0.1.0 Upstream Author : Masahiro TANAKA * URL or Web page : http://masa16.github.io/ruby-mathgl/ * License : LGPL-3.0+ Description : Ruby wrapper of MathGL MathGL is a library for scientific data visualization developed by Alexey Balakin. In Debian, MathGL is provided named "mathgl". . This package provides Ruby wrapper of MathGL, made using SWIG. --- Youhei SASAKI GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07
Bug#815006: Icedove -> Thunderbird
Hi, in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815006#5, you state that similar discussions are going on for the renaming of Icedove. Are those publicly trackable somewhere? Cheers! u.
Bug#816905: RM: php-defaults -- RoQA; Name taken over by php-defaults
Package: ftp.debian.org Severity: normal As expected, using the existing php-* naming scheme for the recent PHP transition leads to some conflicts. php-soap_0.13.0-1 vanished under php-defaults (providing php-soap 1:7.0+35), so there is little point keeping it. php-services-weather is probably be a bit broken because of that, but we might get rid of it at some point anyway, see #792195. signature.asc Description: PGP signature
Bug#815006: Icedove -> Thunderbird
Hello, On Sun, Mar 06, 2016 at 02:12:30PM +, u wrote: > Hi, > > in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815006#5, you state > that similar discussions are going on for the renaming of Icedove. Are > those publicly trackable somewhere? yes. Sylvestre opened up #816679 for tracking via the BTS for the Icedove part. http://bugs.debian.org/816679 Regards Carsten
Bug#816907: kodi: Crashes on shutdown
Package: kodi Version: 15.2+dfsg1-3 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I cliked on the shutdown button. * What exactly did you do (or not do) that was effective (or ineffective)? The shutdown was effective but created a kodi_crashlog file in my home folder. * What was the outcome of this action? The creation of that crash log file. * What outcome did you expect instead? I expected the app to close without creating that file. *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.3.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 kodi depends on: ii kodi-bin 15.2+dfsg1-3 ii kodi-data 15.2+dfsg1-3 kodi recommends no packages. kodi suggests no packages. -- no debconf information
Bug#816905: RM: php-soap -- RoQA; Name taken over by php-defaults
Control: retitle -1 RM: php-soap -- RoQA; Name taken over by php-defaults Hi, I meant to remove php-soap, not php-defaults, sorry (even reportbug got confused by the hijacked name…) On Sun, Mar 06, 2016 at 10:17:21AM -0400, David Prévot wrote: > Package: ftp.debian.org > Severity: normal > > As expected, using the existing php-* naming scheme for the recent PHP > transition leads to some conflicts. php-soap_0.13.0-1 vanished under > php-defaults (providing php-soap 1:7.0+35), so there is little point > keeping it. > > php-services-weather is probably be a bit broken because of that, but we > might get rid of it at some point anyway, see #792195. signature.asc Description: PGP signature
Bug#816909: xfce4-notifyd: should not throw an error in a GNOME session
Package: xfce4-notifyd Version: 0.2.4-3+b1 Severity: minor Dear Maintainer, I am using GNOME in Debian testing, while having XFCE installed. Since some time I am informed on each login that xfce4-notifyd can't start because GNOME is already providing a notification daemon. I think it should be possible to have two desktop environments installed at the same time. It should be possible to switch between full installations of GNOME and XFCE simply via the login screen. notifyd shouldn't throw an error each time GNOME does its job. This may be related to #640082, since a start via session manager would probably make it easier to start notifyd only in XFCE. But I don't care about the mechanism used to start notifyd, I just want it to be quiet until it is needed. Thanks for your work! Michael -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (10, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages xfce4-notifyd depends on: ii libc6 2.21-9 ii libcairo2 1.14.6-1 ii libdbus-1-3 1.10.6-1 ii libdbus-glib-1-20.106-1 ii libgdk-pixbuf2.0-0 2.32.3-1.2 ii libglib2.0-02.46.2-3 ii libgtk2.0-0 2.24.29-1 ii libnotify4 0.7.6-2 ii libx11-62:1.6.3-1 ii libxfce4ui-1-0 4.12.1-2 ii libxfce4util7 4.12.1-2 ii libxfconf-0-2 4.12.0-2+b1 Versions of packages xfce4-notifyd recommends: ii libnotify-bin 0.7.6-2 xfce4-notifyd suggests no packages. -- no debconf information
Bug#816908: arduino 1.6.7 available
Package: arduino Version: 2:1.5.6.2+sdfsg2-3 Severity: wishlist https://github.com/arduino/Arduino/tree/1.6.7 Please upload a newer version of the arduino IDE, as from 1.6.5 onwards it also supports non-ATmega chips (like the ESP8266). Thanks, Martin -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages arduino depends on: ii arduino-core 2:1.5.6.2+sdfsg2-3 ii default-jre [java7-runtime] 2:1.7-52.1 ii libastylej-jni2.04-1.1 ii libcommons-exec-java 1.3-1 ii libcommons-httpclient-java3.1-12 ii libcommons-logging-java 1.2-1 ii libjmdns-java 3.4.1-2 ii libjna-java 4.2.1-1 ii libjsch-java 0.1.53-1 ii libjssc-java 2.6.0-5+b1 ii openjdk-7-jre [java7-runtime] 7u95-2.6.4-1 ii oracle-java7-jdk [java7-runtime] 7u72 Versions of packages arduino recommends: ii astyle 2.04-1.1 ii extra-xdg-menus 1.0-4 ii policykit-1 0.105-14.1 arduino suggests no packages. -- no debconf information -- Martin Zobel-Helas Debian System Administrator Debian & GNU/Linux Developer Debian Listmaster http://about.me/zobel Debian Webmaster GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B
Bug#816910: debsnap: Add --list option
Package: devscripts
Version: 2.16.1
Severity: wishlist
User: devscri...@packages.debian.org
Usertags: debsnap
Tags: patch
It will be nice to just list versions (for source and binary).
What do you think about patch like one here.
Osamu
>From a84839692d75877de10ff1b620dbb85dd32d47fd Mon Sep 17 00:00:00 2001
From: Osamu Aoki
Date: Sun, 6 Mar 2016 23:36:31 +0900
Subject: [PATCH] debsnap: Add --list option
---
scripts/debsnap.1 | 4
scripts/debsnap.pl | 15 +--
2 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/scripts/debsnap.1 b/scripts/debsnap.1
index 217c1ac..306b4e8 100644
--- a/scripts/debsnap.1
+++ b/scripts/debsnap.1
@@ -45,6 +45,10 @@ Report on the \fBdebsnap\fP configuration being used and progress during the
download operation. Please always use this option when reporting bugs.
.TP
+.BR \-\-list
+Don't dwnload but just list versions.
+
+.TP
.BR \-\-binary
Download binary packages instead of source packages.
diff --git a/scripts/debsnap.pl b/scripts/debsnap.pl
index 50749fb..b40a9f7 100755
--- a/scripts/debsnap.pl
+++ b/scripts/debsnap.pl
@@ -84,6 +84,7 @@ The following options are supported:
Default is ./source-
-f, --force Force overwriting an existing
destdir
+--list Don't download but just list versions
--binaryDownload binary packages instead of
source packages
-a ,
@@ -216,7 +217,7 @@ sub keep_version($)
read_conf(@ARGV);
Getopt::Long::Configure('gnu_compat');
Getopt::Long::Configure('no_ignore_case');
-GetOptions(\%opt, 'verbose|v', 'destdir|d=s', 'force|f', 'help|h', 'version', 'first=s', 'last=s', 'binary', 'architecture|a=s@') || usage(1);
+GetOptions(\%opt, 'verbose|v', 'destdir|d=s', 'force|f', 'help|h', 'version', 'first=s', 'last=s', 'list', 'binary', 'architecture|a=s@') || usage(1);
usage(0) if $opt{help};
usage(1) unless @ARGV;
@@ -277,7 +278,17 @@ unless (@versions) {
warn "$progname: No matching versions found for $package\n";
$warnings++;
}
-if ($opt{binary}) {
+if ($opt{list}) {
+foreach my $version (@versions) {
+ if ($opt{binary}) {
+ print "$version->{binary_version}\n";
+ }
+ else {
+ print "$version->{version}\n";
+ }
+}
+}
+elsif ($opt{binary}) {
foreach my $version (@versions) {
my $src_json = fetch_json_page("$opt{baseurl}/mr/package/$version->{source}/$version->{version}/binfiles/$version->{name}/$version->{binary_version}?fileinfo=1");
--
2.7.0
Bug#816911: Should probably ship a transitional package fonts-droid to migrate to fonts-droid-fallback
Source: fonts-android Version: 1:4.4.4r2-7 Severity: minor Hi, I noticed that I have a non-downloadable binary-package named fonts-droid installed. Looking why it has been removed I saw that it bascially just has been renamed to fonts-droid-fallback. So I think, the fonts-android source package should provide a transitional binary-package from fonts-droid to fonts-droid-fallback. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-rc4-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#610048: FYI: debsnap --list
Hi, I filed a wishlist bug with a patch for --list option. http://bugs.debian.org/816910 Do you agree this type of code ? Osamu
Bug#816698: subversion: FTBFS on mips, mipsel
On Fri, Mar 04, 2016 at 06:41:00PM +0100, Christian Hofstaedtler wrote: > Your package FTBFS on the mips and mipsel buildds: > > https://buildd.debian.org/status/fetch.php?pkg=subversion&arch=mips&ver=1.9.3-2%2Bb1&stamp=1457047589 > https://buildd.debian.org/status/fetch.php?pkg=subversion&arch=mipsel&ver=1.9.3-2%2Bb1&stamp=1457043167 Odd. Both built fine in the last sourceful upload. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy
Bug#811377: [Pkg-sysvinit-devel] Adopting Sysvinit
On Sun, 06 Mar 2016, Petter Reinholdtsen wrote: > Hi. I would be happy for skilled people with more time to take over the > maintenance. I would be happy to help with the knowledge I got, but > lack the time required to do a good job maintaining the sysvinit, > insserv and startpar package. Same here. In fact, I've not had the time to properly setup the environment required for pre-upload QA on sysvinit for a *long* time, so I was always in an "advisory" mode anyway. > > It seems Ben's mail didn't make it to the maintainers' mailing list. I'm > > going to poke a few people individually now. > > I just approved them. Thanks. Simon Richter's request for project access arrived after you did your approval run, apparently. I have just approved him. While approving Simon, I noticed we use "junior" developer as the non-admin role level (I initially thought we used "senior" developer). Just to make it clear, there are no differences at all between the junior and senior developer roles in the pkg-sysvinit alioth project. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Bug#816913: sphinxsearch: Daily sphinxsearch cron fails when there are only RT indexes in config
Package: sphinxsearch Version: 2.2.9-1 Severity: minor Dear Maintainer, Default crontab installed with sphinxsearch assumes there's at least one non-rt index in the config file. When it's not true, it produces mail noise (without really affecting anything): FATAL: no indexes found in config file '/etc/sphinxsearch/sphinx.conf' Please provide separate option in /etc/default/sphinxsearch to enable/disable this daily crontab (something like RUN_INDEXER_DAILY) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.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 sphinxsearch depends on: ii adduser 3.113+nmu3 ii libc6 2.21-9 ii libexpat1 2.1.0-7 ii libgcc1 1:5.3.1-10 ii libmysqlclient18 5.6.28-1 ii libpq59.5.1-1 ii libstdc++65.3.1-10 ii libstemmer0d 0+svn585-1 ii zlib1g1:1.2.8.dfsg-2+b1 sphinxsearch recommends no packages. sphinxsearch suggests no packages. -- Configuration Files: /etc/default/sphinxsearch changed: START=yes -- no debconf information
Bug#816912: systemd: Can't make non-shared bind mounts in fstab
Package: systemd Version: 215-18 Severity: normal Dear Maintainer, For some time, I have been using a distinct set of bind mounts of the system directory tree (i.e. /, /usr, /var) for backup purposes. Unfortunately, it seems that systemd now makes bind mounts shared by default, so that /tmp, /home etc. etc. end up being mounted as well, which makes it impossible to make a backup of just a subset of my filesystem tree. The only 'solution' I have found, is that applications that need non-shared bind mounts should be adapted. However, the application in question here is systemd itself... Please add an fstab flag (or so) that directs systemd to create a non-shared bind mount. Kind regards, Rogier. /etc/fstab: --- # /dev/data/root / ext4 errors=remount-ro,relatime 0 1 /dev/data/boot /boot ext4relatime0 2 /dev/data/home /home ext4relatime0 2 /dev/data/tmp /tmpext4 relatime0 2 /dev/data/usr /usrext4 relatime0 2 /dev/data/local /usr/local ext4relatime0 2 /dev/data/var /varext4 relatime0 2 /dev/data/swap noneswapsw 0 0 /dev/data/scratch /mnt/scratchext4relatime 0 2 /dev/data/media /home/rogier/media ext4relatime0 2 /dev/data/wheezy32 /mnt/wheezy32 ext4 ro,relatime,noauto 0 2 /dev/data/wheezy64 /mnt/wheezy64 ext4 ro,relatime,noauto 0 2 /dev/data/jessie32 /mnt/jessie32 ext4 ro,relatime,noauto 0 2 /dev/data/jessie64 /mnt/jessie64 ext4 ro,relatime,noauto 0 2 /dev/data/stretch32 /mnt/stretch32 ext4ro,relatime,noauto 0 2 /dev/data/stretch64 /mnt/stretch64 ext4ro,relatime,noauto 0 2 /dev/backup/backup /var/lib/backuppc ext4relatime,noauto 0 2 /dev/data/postgresql/var/lib/postgresql ext4relatime0 2 /dev/data/deb-cache /var/cache/apt/archives ext4relatime0 2 # Loopback mounts of system filesystems for backup - allows using rsync without need to # exclude all unwanted mounts on the command-line (which is unmaintainable) / /export/sys nonerw,bind 0 0 /usr/export/sys/usr nonero,bind 0 0 /var/export/sys/var nonerw,bind 0 0 /boot /export/sys/bootnonero,bind 0 0 /usr/local /export/sys/usr/local nonero,bind 0 0 --- -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US, 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 systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59.2 ii libacl1 2.2.52-2 ii libaudit1 1:2.4.2-1 ii libblkid1 2.26.2-6 ii libc6 2.19-18 ii libcap2 1:2.24-9 ii libcap2-bin 1:2.24-9 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod220-1 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2+b1 ii libsystemd0 215-18 ii mount 2.26.2-6 ii sysv-rc 2.88dsf-59.2 ii udev215-18 ii util-linux 2.26.2-6 Versions of packages systemd recommends: ii dbus1.8.18-1 ii libpam-systemd 215-18 Versions of packages systemd suggests: pn systemd-ui -- no debconf information
Bug#800845: autopkgtest: Add support for nested VMs
Hey Christian, Christian Seiler [2016-03-04 23:36 +0100]: > There's a small bug in the changes you made to my patch: logging.warning > should be adtlog.warning. Also, technically you missed a return path in > get_cpuflag(), since /proc/cpuinfo could contain no line that starts with > 'flags'. Indeed, thanks! I made that more robust by always returning [] in the end: http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=748453b095 > While test-building I also noticed quite a few lintian informational > notices about the manpages (mainly hyphen-used-as-minus-sign) Weird, I don't see them here, I just get the ones below and the too old Standards-Version. > (Also note that lintian gives me: > W: autopkgtest: executable-not-elf-or-script > usr/share/autopkgtest/setup-commands/ubuntu-touch-session > W: autopkgtest: executable-not-elf-or-script > usr/share/autopkgtest/setup-commands/ro-apt > W: autopkgtest: executable-not-elf-or-script > usr/share/autopkgtest/setup-commands/ro-apt-update > There are no shebangs in there: is that intentional?) They aren't needed, but to quiesce lintian I added them now. There's however one issue which I'd like to address before release. Adding "update-initramfs -u" to adt-virt-qemu increased the test time quite dramatically. The tests/testpkg-simple/ no-op test now takes 28s instead of 20s here. I wonder, do we really need this? A reboot without an update initrd should not be affected by this: the /dev/baseimage node does not exist at all, thus there can't be any UUID clash. It only gets added after booting (and rebooting too), so having the initrd know about this is not required at all. I pushed http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=f5b9cabe6 now to fix this. I want to give you a chance to review this before I push the red release button, though. :-) Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: PGP signature
Bug#800845: autopkgtest: Add support for nested VMs
Hi Martin, On 03/06/2016 04:19 PM, Martin Pitt wrote: > Christian Seiler [2016-03-04 23:36 +0100]: >> There's a small bug in the changes you made to my patch: logging.warning >> should be adtlog.warning. Also, technically you missed a return path in >> get_cpuflag(), since /proc/cpuinfo could contain no line that starts with >> 'flags'. > > Indeed, thanks! I made that more robust by always returning [] in the > end: > > > http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=748453b095 Looks good, haven't tested it though. >> While test-building I also noticed quite a few lintian informational >> notices about the manpages (mainly hyphen-used-as-minus-sign) > > Weird, I don't see them here, I just get the ones below and the too > old Standards-Version. Ok, I'll send a patch soon, if you can wait with the release for another hour or so. ;-) (Btw. I run lintian -L '>=pedantic/wild-guess', so maybe that's why you don't see them.) > There's however one issue which I'd like to address before release. > Adding "update-initramfs -u" to adt-virt-qemu increased the test time > quite dramatically. The tests/testpkg-simple/ no-op test now takes 28s > instead of 20s here. I wonder, do we really need this? A reboot > without an update initrd should not be affected by this: the > /dev/baseimage node does not exist at all, thus there can't be any > UUID clash. It only gets added after booting (and rebooting too), so > having the initrd know about this is not required at all. > > I pushed > > > http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=f5b9cabe6 > > now to fix this. I want to give you a chance to review this before I > push the red release button, though. :-) This is wrong. The udev rules do two things: - link_priority - /dev/baseimage symlink If you don't update the initramfs, /dev/baseimage won't exist, true. But that does NOT mean that the UUID clashes don't happen. From my experience testing this, the UUID clashes would result in ~50% the time having /dev/disk/by-uuid/XXX being a symlink to /dev/vdb1 while the other 50% it would be /dev/vda1. Now funnily enough for mounting the root file system in the initramfs, this doesn't appear to have any impact whatsoever (not sure why, though, haven' investigated that), but it definitely _will_ have an impact for any other file systems. Which means that if you have a test image that has multiple partitions (which vmdebootstrap doesn't generate, but the docs of adt-virt-qemu do mention that _any_ VM image should do), this _will_ break those cases. What you _could_ do is create a flag file in /run and update the reboot script to update the initramfs before rebooting if that flag file is set - that way only if a reboot is needed will the initramfs be updated and hence you optimize for the common case where that's not needed. Regards, Christian signature.asc Description: OpenPGP digital signature
Bug#814083: RFS: kwstyle/1.0.1+git3224cf2-1 [ITA]
control: tag -1 pending On Sun, Mar 06, 2016 at 01:07:10PM +0100, Benjamin Eikel wrote: > I worked on all the points on your list and pushed my changes to the > aforementioned GitHub repository. Please review them and give feedback. everything's cool for me now. I can't upload right now because I'm on a shitty network, etc, etc. I'll do later today or tomorrow at most. Anyway, I'd like to ask you for a thing: we have this nifty package in debian, check-all-the-things [0], which runs a huge number of linters and checkers and whatnot over a directory, proving a huge report. The maintainer asked if I'm able to provide a patch adding a check based on KWStyle; I tried it (clearly, I never heard of this thing before your RFS) but didn't succed in producing a readable output. Given that I hope you are able to use this tool, would like to spend some minutes working on a patch for it? It's really easy, see doc/README [1] for kind of short instruction; basically, it's just adding a paragraph in data/c [2], just glancing over this file is enough to have an idea of what is needed :) [0] links: https://tracker.debian.org/pkg/check-all-the-things https://packages.debian.org/experimental/check-all-the-things https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git [1] https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git [2] https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git/tree/data/c -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#807040: general: System hangs and then restarts (kernel panic)
I have not heard back from you, so I would assume that this issue will never be fixed. Just for others that might run into the same problem, here a summary: Debian Jessie, as of March 6, 2016 does not work on a Lenovo T61 due to a bug in nouveau and/or X11. Nouveau makes this machine kernel panic, while the proprietary driver just crashes and restarts X11. This bug has not been fixed in Testing (Stretch) as this date. This is no hardware issue, as Debian Wheezy works flawlessly, no kernel panics, no crashes, with both Nvidia proprietary driver and nouveau, although nouveau creates really ugly display distortions and font errors that make it unusable at times. I migrated this machine to Stretch, in hopes that this will get fixed, as this is a perfectly fine laptop and I cannot just buy another one because of this bug and staying with Wheezy forever is not an option. I use Debian on every other machine and for over 10 years it has never deserted me. On Tue, Dec 29, 2015 at 5:59 PM, Nigra Truo wrote: > So I was forced to downgrade to Debian Wheezy and I had some people that > were constantly telling me that this must be a hardware issue, and it is > not. Wheezy works perfectly on this laptop, no crashes, no nothing, stable > as a rock. > Now I still have an image on a seperate harddisk to troubleshoot this, as > I obviously don't like to just have to skip Jessie and wait for a few > years, while running the old obsolete Debian. > Is there any way this bug will be attempted to fix or will Debian Jessie > just not run on a Lenovo T61 Laptop ever? > > Thanks, > > Markus > > On Wed, Dec 23, 2015 at 3:28 PM, Nigra Truo wrote: > >> Hi, >> >> Sorry, I was getting a little negative, this is really hard. I appreciate >> any help you can give. >> If I had the kernel logs, could you do something with them and help >> determine what crashed. >> I set up kexec, kdump to collect the logs. >> >> Thanks, >> >> Markus >> >> On Tue, Dec 22, 2015 at 3:57 AM, Nigra Truo wrote: >> >>> Hi Sven, >>> >>> >>> >>> On Mon, Dec 21, 2015 at 1:55 PM, Sven Joachim wrote: >>> On 2015-12-11 08:20 +0100, Adam Borowski wrote: > On Thu, Dec 10, 2015 at 07:17:43PM -0800, Nigra Truo wrote: >> That does not work neither unfortunately. I installed the proprietary >> driver and now X crashes. At least the whole machine does not crash, but I >> can open a Desktop, KDE or Gnome, then open an app, maximize the window and >> I get a prompt crash. > > Oif. I'm afraid I can't help you further here -- I'm a mere user when it > comes to X drivers. I could help with installing a newer version or an > alternate driver, but for more, we need actual driver guys :( Problem is, there is no such person in Debian for the nouveau driver. >>> >>> Who will fix this then when nobody is in charge then? >>> This problem is a huge disaster, I had about 25 restarts today already >>> and can't work like this and will need to downgrade to have a stable system >>> to work and troubleshoot this on the side on a test harddisk, as a test >>> system as a system of this instable magnitude needs to be treated. >>> >>> >>> >> The unability to get logs in the Kernel Panic is a huge problem, I can't >> believe that this his still not solved, that there is no automatic >> mechanism, to at least see what caused the panic or, for the matter, >> logging that ANY panic has occurred. Right now, the most serious of errors >> does not have any accounting whatsoever. >>> >>> > > When the kernel panics, most of its facilities are considered dead. Doing > something as complex as a filesystem write would require temporarily > ignoring the panic, with a huge risk of data corruption. A generally pretty > bad idea. >>> >>> I don't know how Windows does it, but it does remember that there was a >>> bluescreen. If Windows can, so can Linux. >>> Right now, I can't stop my system from restarting, I don't know what the >>> hell is restarting it, if it is the watchdog service, which I deactivated >>> in the kernel (and it still restarts), when I push some keys, it shows the >>> kernel panic and shows the message "rebooting in 30 seconds" and when I do >>> a google search, there is absolutely no reference or documentation about >>> what that is, what is causing it and WHO is doing it, why the reboot? >>> As of Debian Wheezy, there as absolutely no restarting when the kernel >>> paniced and that is the way it needs to be. >>> Now with the new kernel, it just restarts, and could easily go into a >>> reboot loop, endlessly restarting. Also, it does not show anything in the >>> logs, there is absolutely nothing on the system that shows the system had a >>> panic or that it even crashed, which is totally horrendous, considering >>> that you could have data loss and never know about it. I don't understand >>> why this is solved so pathetica
Bug#815734: regression: ESS cannot be compiled
On 6 March 2016 at 13:23, Norbert Preining wrote: | Dear all | | > BINGO -- once I add that things pass with the new texinfo.tex | | Good. | | I have uploaded texinfo -5 just now, should be in the repos in | no time. | | After this, please remove the old texinfo.tex copies - we had to | fight with outdated texinfo.tex for too often around the 4.8 | times, I try to make sure that this doesn't happen again. Easy enough for us as doc/texinfo.tex sticks out in git. | For -6 I have added a recommends on texlive-fonts-recommended, but | this is for users and not targetting package builds. So please | add the build-dep if necessary. Done in the ess git repo which contains debian/. I'll upload a new ess_15.09.2-3 with these changes too. All good then -- so thanks all. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#815775: zeroc-ice: diff for NMU version 3.5.1-6.4
Control: tags 815775 + patch Control: tags 815775 + pending Dear maintainer, Chris Knadle has prepared an NMU for zeroc-ice (versioned as 3.5.1-6.4) and I've uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- .''`. 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: Treibhaus: Joe Zawinul & Syndicate diff -Nru zeroc-ice-3.5.1/debian/changelog zeroc-ice-3.5.1/debian/changelog --- zeroc-ice-3.5.1/debian/changelog 2015-11-21 08:41:17.0 +0100 +++ zeroc-ice-3.5.1/debian/changelog 2016-03-06 16:22:22.0 +0100 @@ -1,3 +1,16 @@ +zeroc-ice (3.5.1-6.4) unstable; urgency=medium + + * Non-maintainer upload. + * debian/control: +- Remove dependencies to fix FTBFS bug: + libmono2.0-cil, + mono-gmcs + (Closes: #815775) + [Note: the Ubuntu source packages zeroc-ice upstream ships have + far fewer Build-Depends.] + + -- Christopher Knadle Fri, 04 Mar 2016 21:54:19 -0500 + zeroc-ice (3.5.1-6.3) unstable; urgency=medium * Non-maintainer upload. diff -Nru zeroc-ice-3.5.1/debian/control zeroc-ice-3.5.1/debian/control --- zeroc-ice-3.5.1/debian/control 2015-11-20 05:39:06.0 +0100 +++ zeroc-ice-3.5.1/debian/control 2016-03-06 16:22:22.0 +0100 @@ -18,7 +18,6 @@ ruby, libqt4-dev, Build-Depends-Indep: mono-devel | c-sharp-2.0-compiler, - libmono2.0-cil, pkg-config, default-jdk | java-gcj-compat, libjgoodies-looks-java (>= 2.5.2), @@ -27,7 +26,6 @@ libdb5.3-java (>= 5.1.4~) | libdb-java (>= 5.1.4~), ant, ant-optional, - mono-gmcs, cli-common-dev (>= 0.8~) Standards-Version: 3.9.6 Homepage: http://www.zeroc.com/ signature.asc Description: Digital Signature
Bug#816910: debsnap: Add --list option
On Sun, Mar 06, 2016 at 11:44:06PM +0900, Osamu Aoki wrote: > It will be nice to just list versions (for source and binary). > > What do you think about patch like one here. Looks good to me. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy
Bug#800845: autopkgtest: Add support for nested VMs
On 03/06/2016 04:29 PM, Christian Seiler wrote: >>> While test-building I also noticed quite a few lintian informational >>> notices about the manpages (mainly hyphen-used-as-minus-sign) >> >> Weird, I don't see them here, I just get the ones below and the too >> old Standards-Version. > > Ok, I'll send a patch soon, if you can wait with the release for > another hour or so. ;-) Ok, so I test-built autopkgtest in both Jessie and sid chroots, and the Jessie chroots gave my hyphen-used-as-minus-sign, whereas the sid ones don't, I just noticed. I did a bit of digging and found: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785353 So basically the tag is completely useless and one shouldn't care about it anymore. I've attached a patch that fixes the following spelling mistakes, however: I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-build-lxc.1.gz SYNOPSYS SYNOPSIS I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-build-lxd.1.gz SYNOPSYS SYNOPSIS I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-buildvm-ubuntu-cloud.1.gz SYNOPSYS SYNOPSIS I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-run.1.gz SYNOPSYS SYNOPSIS I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-run.1.gz preceeding preceding I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-virt-chroot.1.gz SYNOPSYS SYNOPSIS I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-virt-lxc.1.gz SYNOPSYS SYNOPSIS I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-virt-lxd.1.gz SYNOPSYS SYNOPSIS I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-virt-null.1.gz SYNOPSYS SYNOPSIS I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-virt-qemu.1.gz SYNOPSYS SYNOPSIS I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-virt-schroot.1.gz SYNOPSYS SYNOPSIS I: autopkgtest: spelling-error-in-manpage usr/share/man/man1/adt-virt-ssh.1.gz SYNOPSYS SYNOPSIS Also note that I get: P: autopkgtest source: package-uses-old-debhelper-compat-version 8 I: autopkgtest source: missing-debian-source-format I: autopkgtest source: vcs-field-uses-insecure-uri vcs-browser http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git I: autopkgtest source: vcs-field-uses-insecure-uri vcs-git git://anonscm.debian.org/autopkgtest/autopkgtest.git I'm not going to send a patch for these, but to make your life easier for the Vcs URIs, here are the debian/control fields for those: Vcs-Git: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git Vcs-Browser: https://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git (Other than that, the package is lintian clean.) Regards, Christian From 4eb56702a757e0654775785f1794d7c4fa5ef420 Mon Sep 17 00:00:00 2001 From: Christian Seiler Date: Sun, 6 Mar 2016 16:47:16 +0100 Subject: [PATCH] Fix spelling errors in manpages. --- runner/adt-run.1 | 4 ++-- tools/adt-build-lxc.1| 2 +- tools/adt-build-lxd.1| 2 +- tools/adt-buildvm-ubuntu-cloud.1 | 2 +- virt-subproc/adt-virt-chroot.1 | 2 +- virt-subproc/adt-virt-lxc.1 | 2 +- virt-subproc/adt-virt-lxd.1 | 2 +- virt-subproc/adt-virt-null.1 | 2 +- virt-subproc/adt-virt-qemu.1 | 2 +- virt-subproc/adt-virt-schroot.1 | 2 +- virt-subproc/adt-virt-ssh.1 | 2 +- 11 files changed, 12 insertions(+), 12 deletions(-) diff --git a/runner/adt-run.1 b/runner/adt-run.1 index 57a1fc6..1274ec9 100644 --- a/runner/adt-run.1 +++ b/runner/adt-run.1 @@ -1,7 +1,7 @@ .TH adt\-run 1 2014 autopkgtest .SH NAME adt\-run \- test an installed binary package using the source package's tests -.SH SYNOPSYS +.SH SYNOPSIS .B adt\-run .IR options ... .B \-\-\- @@ -114,7 +114,7 @@ is a file (*.click), install given click package into testbed. If it is a click name (like "com.example.myapp"), assume it is already installed in the testbed and read the manifest from it. -Run click package tests from the preceeding +Run click package tests from the preceding .BR --click-source . If a click source directory is not specified explicitly, it will be downloaded according to the manifest's diff --git a/tools/adt-build-lxc.1 b/tools/adt-build-lxc.1 index 24bf448..6deef8d 100644 --- a/tools/adt-build-lxc.1 +++ b/tools/adt-build-lxc.1 @@ -2,7 +2,7 @@ .SH NAME adt-build-lxc \- Create or update autopkgtest container for adt\-virt-lxc -.SH SYNOPSYS +.SH SYNOPSIS .B adt-build-lxc .I distribution release .RI [ architecture ] diff --git a/tools/adt-build-lxd.1 b/tools/adt-build-lxd.1 index ba20a27..5fb2d70 100644 --- a/tools/adt-build-lxd.1 +++ b/tools/adt-build-lxd.1 @@ -2,7 +2,7 @@ .SH NAME adt-build-lxd \- Create or update autopkgtest container for adt\-virt-lxd -.SH SYNOPSYS +.SH SYNOPSIS .B adt-build-lxd .I image diff --git a/tools/adt-buildvm-ubuntu-cloud.1 b/tools/adt-buildvm-ubuntu-cloud.1 index b992f32..fdce40c 100644 --- a/tools/adt-buildvm-ubuntu-cloud.1 +++ b/tool
Bug#816390: Pending fixes for bugs in the libnet-domain-tld-perl package
tag 816390 + pending thanks Some bugs in the libnet-domain-tld-perl package are closed in revision 9357e0fd91b1c4535ca41a6d1f3a494af9f03826 in branch 'master' by gregor herrmann The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-domain-tld-perl.git/commit/?id=9357e0f Commit message: New upstream release. Fixes "Please package new upstream release 1.74" (Closes: #816390)
Bug#751505: Buggy "Switch user" on the "Action Buttons" plugin
Package: xfce4-panel Version: 4.12.0-3 Followup-For: Bug #751505 Note that dm-tool is lightdm specific, so it's probably not appropriate to execute that unconditionally. One way could be to read /etc/X11/default-display-manager and run the appropriate command based on that. In the meantime, users can work around this with --- /usr/bin/gdmflexiserver #!/bin/sh exec dm-tool switch-to-greeter --- X -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-panel depends on: ii exo-utils0.10.7-1 ii libatk1.0-0 2.18.0-1 ii libc62.21-9 ii libcairo21.14.6-1 ii libdbus-1-3 1.10.6-1 ii libdbus-glib-1-2 0.106-1 ii libexo-1-0 0.10.7-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.6.1-0.1 ii libgarcon-1-00.4.0-2 ii libgdk-pixbuf2.0-0 2.32.3-1.2 ii libglib2.0-0 2.46.2-3 ii libgtk2.0-0 2.24.29-1 ii libice6 2:1.0.9-1+b1 ii libpango-1.0-0 1.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libpangoft2-1.0-01.38.1-1 ii libsm6 2:1.2.2-1+b1 ii libwnck222.30.7-5 ii libx11-6 2:1.6.3-1 ii libxext6 2:1.3.3-1 ii libxfce4ui-1-0 4.12.1-2 ii libxfce4util74.12.1-2 ii libxfconf-0-24.12.0-2+b1 xfce4-panel recommends no packages. xfce4-panel suggests no packages. -- no debconf information
Bug#816900: RFP: libdigest-elf-perl -- Perl extension for ELF hash function
Control: retitle -1 ITP: libdigest-elf-perl -- Perl extension for ELF hash function On Sun, 06 Mar 2016 14:04:18 +, Nick Morrott wrote: > Package: wnpp > Severity: wishlist > > * Package name: libdigest-elf-perl [..] > I plan to maintain this package under the umbrella of the Debian Perl > Group (nickm-guest). Retitling the bug accordingly (s/RFP/ITP/) :) Please use X-Debbugs-Cc instead of plain Cc next time, then the mail will be sent by the BTS with the bug number inserted. You can also just use "dpt gen-itp" from a preliminary source package tree. 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: David Bowie: Changes signature.asc Description: Digital Signature
Bug#816911: [Pkg-fonts-devel] Bug#816911: Should probably ship a transitional package fonts-droid to migrate to fonts-droid-fallback
Quoting Axel Beckert (2016-03-06 15:47:37) > I noticed that I have a non-downloadable binary-package named > fonts-droid installed. Looking why it has been removed I saw that it > bascially just has been renamed to fonts-droid-fallback. > > So I think, the fonts-android source package should provide a > transitional binary-package from fonts-droid to fonts-droid-fallback. It is not a simple transition: The project is dead upstream. Main part has a sort-of replacement (but not exactly!) in fonts-noto, but another part is preserved in Debian as fonts-droid-fallback because the exact form is needed (for Ghostscript - not sure if other places too). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#816914: Eom auto reload file is broken
Package: eom Version: 1.12.2-1 1) Open some jpg file in Eye of MATE. 2) Don't close Eom window. Open same file in Gimp. 3) Change file in Gimp and save it. Of course, via file->overwrite test.jpg, not via ctrl+s. What I'm expected: Eom at least ask "File changed. do you want reload it?" (it's work in Jessie). What I'm got: in one file Eom window turn black. In other file - Eom simply ignore file changing.
Bug#816858: Logical volumes on external USB disk cause boot to enter emergency shell
Hello, > dmesg does not help, as it does not show the errors by lvm and systemd. > The complete content of the journal since boot (via journalctl) should > be enough. I have systemd purged currently. Like I wrote, the problem also occurs with sysvinit, if /etc/init.d/lvm2 does not contain an additional sleep command before the vgchange call. With systemd, the sleep command does not help. So, journalctl is not available. What log is best in this situation? Regards Christoph Pleger
Bug#816076: wicd-daemon: upgrade reconfigures static ethernet interface, and kills ssh sessions.
Hi Gianfranco, On Sat, Mar 05, 2016 at 03:51:23PM +, Gianfranco Costamagna wrote: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816076 Thanks for the heads up. I seem to have missed that bug report initially. I noticed that interruption, too, at least once. But IIRC in my case, network came back with the same IP IIRC since the IP was assigned staticallt by the DHCP server. I'll forward it to upstream for now. Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News| a...@deuxchevaux.org (Mail) X See http://www.nonhtmlmail.org/campaign.html | a...@noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web)
Bug#816896: [Pkg-mozext-maintainers] Bug#816896: xul-ext-ublock-origin: Doesn't install anything on conkeror
Control: reassign -1 conkeror
Hello,
On Sun, Mar 06, 2016 at 11:42:05AM +, John Kozak wrote:
> Installing this package adds ublock-origin to firefox but not conkeror -
> the package info at least implies that it does. Reinstalling conkeror
> make no difference.
As with #680709, I believe that this is a bug in conkeror rather than
xul-ext-ublock-origin. There is an entry for Conkeror in install.rdf
and xul-ext-ublock-origin provides
/usr/share/mozilla/extensions/{a79fe89b-6662-4ff4-8e88-09950ad4dfde}/ublo...@raymondhill.net
so Conkeror should find the extension.
It turns out, btw, that Conkeror doesn't work with uBlock Origin at all
atm: see . If this
upstream bug is not fixed, I will remove the package info implying that
uBlock origin works with Conkeror.
--
Sean Whitton
signature.asc
Description: PGP signature
Bug#816857: gimagereader: fails to launch with "symbol lookup error"
Hi Jeff and Jeffrey, I think tessaract broke it's ABI again without taking care of renaiming the package name and bumping SONAME :( That's really annoying as gimagereader broke again. (See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794489 for reference) Building with tessaract from unstable results in a broken binary in testing - same undefined symbol as last time. > This is the complete error messager: > > gimagereader-gtk: symbol lookup error: gimagereader-gtk: > undefined symbol: _ZN9tesseract11TessBaseAPI13AnalyseLayoutEv Could you please fix this? And could you take care of this properly next time - it really wasts my time. Best, Philip signature.asc Description: OpenPGP digital signature
Bug#816915: sudo: fails to honour NOPASSWD directive
Package: sudo Version: 1.8.15-1.1 Severity: normal Current versions of sudo fail to honour the NOPASSWD directive set for a user/host/command set in /etc/sudoers: sudo -n apt-get update sudo: a password is required /etc/sudoers says: xxx =NOPASSWD:/usr/bin/apt-get (of course, in the sudoers I have the real user and host names) I haven't changed the sudoers, so it must be a recent undocumented change in programme behaviour. The same configuration works just fine in Arch Linux. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sudo depends on: ii libaudit1 1:2.4.5-1 ii libc6 2.21-9 ii libpam-modules 1.1.8-3.2 ii libpam0g1.1.8-3.2 ii libselinux1 2.4-3 sudo recommends no packages. sudo suggests no packages. -- Configuration Files: /etc/sudoers [Errno 13] Keine Berechtigung: u'/etc/sudoers' /etc/sudoers.d/README [Errno 13] Keine Berechtigung: u'/etc/sudoers.d/README' -- no debconf information
Bug#800845: autopkgtest: Add support for nested VMs
Hi Martin,
On 03/06/2016 04:29 PM, Christian Seiler wrote:
> What you _could_ do is create a flag file in /run and update the reboot
> script to update the initramfs before rebooting if that flag file is
> set - that way only if a reboot is needed will the initramfs be updated
> and hence you optimize for the common case where that's not needed.
So this took me longer than I hoped, because a kernel update on my host
screwed up QEMU's support for rebooting VMs in general - and it was a
real pain to figure that out.
Now that that works again:
I've implemented this in the following way:
- touch /run/autopkgtest-update-initramfs-at-reboot in setup_baseimage()
- /sbin/autopkgtest-reboot{,-prepare}:
- if /run/autopkgtest-update-initramfs-at-reboot exists AND
update-initramfs is present, update the initramfs
- /usr/share/initramfs-tools/hooks/autopkgtest (created in
setup_baseimage()):
- unconditionally remove /run/autopkgtest-update-initramfs-at-reboot
Because a initramfs-tools hook will only be called if an initramfs
is generated - but if it's generated anyway, we might as well
remove the flag file, because then we can save ourselves a lot of
work.
So basically, IF a reboot is requested AND no initramfs was generated
since, THEN and ONLY THEN will update-initramfs be called. So we minimize
how often it's required to actually generate it.
Tested it against my update open-iscsi package tests (see my RFC mail),
and it works without a hitch.
Patch is attached.
Hopefully that satisfies your performance requirements?
Regards,
Christian
From f4652b649883e2d11aeb7354e3dcf4e52135e5e1 Mon Sep 17 00:00:00 2001
From: Christian Seiler
Date: Sun, 6 Mar 2016 17:04:24 +0100
Subject: [PATCH] adt-virt-qemu: regenerate initramfs only on reboots
The initramfs needs to be regenerated due to UUID collisions with the
baseimage drive, but we only need to do that if the testbed is
rebooted. So in turn just set a flag file and only regenerate the
initramfs when a reboot is requested.
---
lib/adt_testbed.py | 6 ++
virt-subproc/adt-virt-qemu | 14 ++
2 files changed, 20 insertions(+)
diff --git a/lib/adt_testbed.py b/lib/adt_testbed.py
index 2e6dffd..30ee075 100644
--- a/lib/adt_testbed.py
+++ b/lib/adt_testbed.py
@@ -142,6 +142,9 @@ class Testbed:
self.execute(['sh', '-ecC', '''[ ! -e /tmp/autopkgtest-reboot ] || exit 0; '''
'''/bin/echo -e '#!/bin/sh -e\\n'''
'''[ -n "$1" ] || { echo "Usage: $0 " >&2; exit 1; }\\n'''
+ '''[ ! -e "/run/autopkgtest-update-initramfs-at-reboot" ] || {'''
+ ''' if type update-initramfs >/dev/null 2>&1; then '''
+ '''update-initramfs -k all -u; fi; }\\n'''
'''echo "$1" > /run/autopkgtest-reboot-mark\\n'''
'''test_script_pid=$(cat /tmp/adt_test_script_pid)\\n'''
'''p=$PPID; while true; do read _ c _ pp _ < /proc/$p/stat;'''
@@ -154,6 +157,9 @@ class Testbed:
self.execute(['sh', '-ecC', '''[ ! -e /tmp/autopkgtest-reboot-prepare ] || exit 0; '''
'''/bin/echo -e '#!/bin/sh -e\\n'''
'''[ -n "$1" ] || { echo "Usage: $0 " >&2; exit 1; }\\n'''
+ '''[ ! -e "/run/autopkgtest-update-initramfs-at-reboot" ] || {'''
+ ''' if type update-initramfs >/dev/null 2>&1; then '''
+ '''update-initramfs -k all -u; fi; }\\n'''
'''echo "$1" > /run/autopkgtest-reboot-prepare-mark\\n'''
'''test_script_pid=$(cat /tmp/adt_test_script_pid)\\n'''
'''kill -KILL $test_script_pid\\n'''
diff --git a/virt-subproc/adt-virt-qemu b/virt-subproc/adt-virt-qemu
index 2116be1..a0f1339 100755
--- a/virt-subproc/adt-virt-qemu
+++ b/virt-subproc/adt-virt-qemu
@@ -208,6 +208,20 @@ def setup_baseimage():
term.send(b'udevadm settle --exit-if-exists=/dev/baseimage\n')
VirtSubproc.expect(term, b'#', 10)
+# The initramfs needs to be regenerated to include the new udev
+# rules, but this is only necesssary if the testbed is rebooted, so
+# just touch a flag file.
+term.send(b'touch /run/autopkgtest-update-initramfs-at-reboot\n')
+VirtSubproc.expect(term, b'#', 10)
+
+# Add an update-initramfs hook that removes the flag file, because
+# if the test case calls update-initramfs anyway, we don't need to
+# do so ourselves.
+term.send(b'''if [ -d /usr/share/initramfs-tools/hooks ] ; then '''
+ b'''printf '#!/bin/sh\\nrm -f %s\\nexit 0\\n' "/run/autopkgtest-update-initramfs-at-reboot" '''
+ b'''> /usr/share/initramfs-tools/hooks/autopkgtest; '''
+ b'''chmod +x /usr/share/initramfs-tools/hooks/autopkgtest; fi\n''')
+VirtSubproc.expe
Bug#800845: autopkgtest: Add support for nested VMs
Hello Christian, Christian Seiler [2016-03-06 16:54 +0100]: > I've attached a patch that fixes the following spelling mistakes, Thanks, applied. > P: autopkgtest source: package-uses-old-debhelper-compat-version 8 > I: autopkgtest source: missing-debian-source-format > I: autopkgtest source: vcs-field-uses-insecure-uri vcs-browser > http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git > I: autopkgtest source: vcs-field-uses-insecure-uri vcs-git > git://anonscm.debian.org/autopkgtest/autopkgtest.git Fixed in git too. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: PGP signature
Bug#816076: wicd-daemon: upgrade reconfigures static ethernet interface, and kills ssh sessions.
Hi Andrew, Andrew Vaughan wrote: > My home server is a headless box, administered from a vnc session tunnelled > over ssh. It has no wifi adaptor, just a single ethernet port that is > statically configured via /etc/network/interfaces. So why are you using wicd at all? I don't see why you need wicd in such a setup. > This behaviour is wrong on so many levels. > > 1. A package upgrade should never bring down an existing in-use interface > without asking the user/admin first. I agree here mostly. It's though only a real issue if the interface doesn't come up again with the same IP afterwards. > 2. I don't think I have ever actually used wicd. See my question above. You don't need it. > Wicd-daemon should not assume that just because it is installed it > owns all the network interfaces. I disagree here. In Debian, it's common that NetworkManager and similar tools manage those interfaces from /etc/network/interfaces which are not listed (or maybe also those which are on "auto"). The issue here seems that wicd seems to no more blacklists them. Will have to check. > I have been through basically the same problems with network-manager in the > past. Issues like this are why so many people are hostile to that package. Indeed. That's why I'm using wicd, too. It was though worse with NetworkManager back then since usually, the network interface stayed down afterwards. That got fixed in the meanwhile, though, IIRC. For now I've forwarded this issue to upstream at https://bugs.launchpad.net/wicd/+bug/1553761 Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#800845: autopkgtest: Add support for nested VMs
On 03/06/2016 06:17 PM, Martin Pitt wrote: > Christian Seiler [2016-03-06 16:54 +0100]: >> I've attached a patch that fixes the following spelling mistakes, > > Thanks, applied. > >> P: autopkgtest source: package-uses-old-debhelper-compat-version 8 >> I: autopkgtest source: missing-debian-source-format >> I: autopkgtest source: vcs-field-uses-insecure-uri vcs-browser >> http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git >> I: autopkgtest source: vcs-field-uses-insecure-uri vcs-git >> git://anonscm.debian.org/autopkgtest/autopkgtest.git > > Fixed in git too. Thanks. However, this causes: W: autopkgtest source: package-needs-versioned-debhelper-build-depends 9 You're going to need a Build-Depends: debhelper (>= 9) in there. ;-) Regards, Christian signature.asc Description: OpenPGP digital signature
Bug#800845: autopkgtest: Add support for nested VMs
Hello Christian, Christian Seiler [2016-03-06 16:29 +0100]: > But that does NOT mean that the UUID clashes don't happen. From my > experience testing this, the UUID clashes would result in ~50% > the time having /dev/disk/by-uuid/XXX being a symlink to /dev/vdb1 > while the other 50% it would be /dev/vda1. Ah, this would be because on a reboot the drive is already added to QEMU, so indeed we don't have the same situation. > Now funnily enough for mounting the root file system in the > initramfs, this doesn't appear to have any impact whatsoever (not > sure why, though, haven' investigated that) The initramfs only mounts the root fs read-only, so it doesn't really matter which one it picks. But this might indeed clash as soon as the real userspace takes over and tries to mount it r/w, and that's not possible with /dev/baseimage. So in order to exploit that we'd need to run the udev rule before systemd-remount-fs.service. Also, is it actually safe to add the base image *again* after a reboot if it already is added? Won't you have two drives then, and /dev/baseimage randomly points to one of it? > What you _could_ do is create a flag file in /run and update the reboot > script to update the initramfs before rebooting if that flag file is > set - that way only if a reboot is needed will the initramfs be updated > and hence you optimize for the common case where that's not needed. That's one way to mitigate this, although it still sucks as it would run on *every* reboot, and for some tests like systemd that adds up quickly! -- so, we need a more persistent flag file. We also need that flag file on the host side to avoid re-adding the drive to the QEMU monitor again on each reboot. Maybe a better way to avoid this would be to introduce the concept of a pre-boot hook in adt-virt-*, which could then simply remove the drive via the QEMU monitor. Then the next hook_open() would re-add it, and everyone is happy. :-) Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: PGP signature
Bug#800845: autopkgtest: Add support for nested VMs
Hi Martin, On 03/06/2016 06:26 PM, Martin Pitt wrote: > Also, is it actually safe to add the base image *again* after a reboot > if it already is added? Won't you have two drives then, and > /dev/baseimage randomly points to one of it? But setup_baseimage() doesn't do that. It's only run the first time after QEMU is started - it's NOT run every boot. Just look at where it's hooked in. :-) (That was the point: I only wanted to add it once so I don't have to deal with reboots - otherwise we need to intercept reboots and remove the drive and all these nasty things that I didn't want to deal with.) >> What you _could_ do is create a flag file in /run and update the reboot >> script to update the initramfs before rebooting if that flag file is >> set - that way only if a reboot is needed will the initramfs be updated >> and hence you optimize for the common case where that's not needed. > > That's one way to mitigate this, although it still sucks as it would > run on *every* reboot, No, only on the first reboot, because then the initramfs is generated and doesn't need to be regenerated. > We also need that > flag file on the host side to avoid re-adding the drive to the QEMU > monitor again on each reboot. No, we don't, see the other patch I sent. I did use --shell on various trivial tests to verify the presence / absence of that flag file at various points in time. > Maybe a better way to avoid this would be to introduce the concept of > a pre-boot hook in adt-virt-*, which could then simply remove the > drive via the QEMU monitor. Why? It's not necessary. So current git master + my flag file patch + debhelper (>= 9) works just fine for me (and I did test it quite a bit) AND is (except for the override) completely lintian clean, even with my lintian setting. Regards, Christian signature.asc Description: OpenPGP digital signature
Bug#782616: nm.debian.org: Please add a mechanism to test mail dispatch
Hi, I'm sorry but couldn't really reproduce this bug in my dev environment focusing it on an econding problem. Instead i found a way to properly render the diacritics in the email headers and gonna submit a patch in relation with bug 744077. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744077 The patch could fix this problem but as long as i cannot reproduce it i can't be sure about it. So i prefer to send the patch to the other ticket also because it is directly related to its title. If you have any ideas about how to reproduce it, they're more than welcome. Bests, efkin.
Bug#744077: nm.debian.org: encoding problems in e-mail headers
Hi,
i think this patch should solve this bug.
Bests,
efkin.
---
>From c4fef717fbdff1bb4a9abc31c4b5f323fae58ca1 Mon Sep 17 00:00:00 2001
From: efkin
Date: Sun, 6 Mar 2016 18:19:03 +0100
Subject: [PATCH] Email headers render properly utf-8 chars
This should fix email headers that were not
properly rendered.
---
backend/templatetags/nm.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/backend/templatetags/nm.py b/backend/templatetags/nm.py
index 54b0d4a..166a0f3 100644
--- a/backend/templatetags/nm.py
+++ b/backend/templatetags/nm.py
@@ -64,7 +64,8 @@ def formataddr(person, nametag=None):
Return a formatted address like "Foo " for a Person
"""
import email.utils
-name = person.fullname.encode('unicode_escape')
+from email.header import Header
+name = str(Header(unicode(person.fullname)))
if nametag is not None:
name += " " + nametag
addr = person.preferred_email
--
2.1.4
Bug#816916: nagios3-common depends on dummy package nagios-plugins-basic
Package: nagios3-common Version: 3.5.1.dfsg-2 Severity: normal Hi, Package nagios3-common depends on dummy package nagios-plugins-basic, thus preventing its removal. The fix would be to replace the dependency on nagios-plugins-basic by monitoring-plugins-basic. In theory, this can be fixed in jessie without introducing new dependencies, because nagios-plugins-basic already depends on monitoring-plugins-basic, so changing this dependency in nagios3-common shouldn't install any new package. Regards, -- Raphaël Halimi signature.asc Description: OpenPGP digital signature
Bug#816917: nagios3-common recommends dummy package nagios-plugins
Package: nagios3-common Version: 3.5.1.dfsg-2 Severity: normal Hi, Package nagios3-common recommends dummy package nagios-plugins. The fix would be to replace the recommends on nagios-plugins by monitoring-plugins. In theory, this can be fixed in jessie without introducing new dependencies, because nagios-plugins already depends on monitoring-plugins, so changing this dependency in nagios3-common shouldn't install any new package. Regards, -- Raphaël Halimi signature.asc Description: OpenPGP digital signature
Bug#796603: closed by Anton Zinoviev (Bug#796603: fixed in console-setup 1.138)
On 5 Mar 2016 17:01, "Anton Zinoviev" wrote: > > On Fri, Mar 04, 2016 at 03:08:39PM -0300, Felipe Sateler wrote: > > > > > Unfortunately, I will not be able to maintain this file or to update it > > > in accordance with future changes in systemd. So I suppose that unless > > > you or somebody else volunteers to maintain it, it will be better to > > > continue without it. > > > > As long as the initscript does simple things, it should require very > > little maintainance. While I can't commit to maintain it (I am no > > expert in console matters), feel free to CC pkg-systemd-maintainers or > > myself if you ever receive a bug about this. > > The reason I hesitate is that I am not a "normal" maintainer of > console-setup. While I have enough time for development related to > console-setup, my limitations force me to allocate this time in batches > with relatively large periods between them. In fact, it won't be > incorrect to say that most of the time other people take care of this > package (one can easily observe this in the changelog). As long as the systemd service keeps relatively close to what the init script is doing, keeping the service file up to date is easy. The only problematic parts would be if the dependencies are changing; but then there are people that can answer questions. It would be a bit harder if the systemd units and init scripts start diverging. > > > >> Before=local-fs-pre.target > > >> Wants=local-fs-pre.target > > > > > > What is the meaning of these two? > > > > This ensures it is run before systemd attempts to fsck and mount any > > local filesystems. It is therefore a relatively appropriate > > replacement for the checkroot dependency. > > What does 'Wants' do? Is this some kind of optimization? Wants means that whenever the service is started, the listed dependencies should be started as well. In systemd, ordering and functional dependencies are orthogonal, so there are separate keywords to specify both. Ordering dependencies do not mean that all the listed services will be activated, it only means: if these units are part of the same transaction, then start them before (or after) the declaring unit. The functional dependency means that if the service is to be started, the listed units will be added to the transaction. In this case, there is a small optimization: mounts and fsck services are ordered after local-fs-pre, but do not depend on it. Thus on simple scenarios the target is never incorporated into the boot transaction. Services that should run before need to cause the target to be pulled in explicitly, which is why keyboard-setup.sh would need to Want it. There are more details about the target in the systemd.special manpage, and about dependencies in systemd.unit. > > > There does not appear to be a keymap init script: > > > > These are created by the kernel when devtmpfs is mounted, and systemd > > mounts /dev before starting any units, so they should be available, > > yes. > > This is good. It seems we don't need 'After'. Right, it can be started as early as possible (and keymap removed from the init script). > > > > One novelty in version 1.138 is that it is unnecessary to run setupcon > > > in order to configure the console. It is OK to configure the keyboard > > > in this way, but this usually will be slower than what the script > > > keyboard-setup.sh does -- instead of setupcon it runs > > > /etc/console-setup/cached_setup_keyboard.sh and reverts to using > > > setupcon only when this script doesn't exist of fails. > > > > IMO, the init script should be as dumb as possible, as it is a > > conffile. Therefore all program logic should move outside the script > > and into a helper script that lives in /lib. This way, improvements > > are guaranteed to be shipped to users. > > The script /etc/console-setup/cached_setup_keyboard.sh is not a > configuration file and the user is not supposed to edit it. Since it is > autogenerated, there is no problem to ship improvements to the users. > (Under FHS this script would have to go in /var rather than in /etc, > however, we need it while /var is not yet mounted. Years ago, nobody at > debian-devel could find a solution to this problem, so now console-setup > violates this aspect of FHS.) I meant the logic to determine if setupcon or the cached scripts should be run. If in the future that part is changed (eg, the names are changed, or more scripts are generated), there is no guarantee the change will reach users, since they may have modified the init script. > > > The resulting unit would be: > > > > ConditionPathExists=/bin/setupcon > > Is there a possibility to use something like 'ConditionPathDoesntExist? > If yes, then we can use two units like these: > > Unit 1: > > ConditionPathExists=/etc/console-setup/cached_setup_keyboard.sh > ExecStart=/etc/console-setup/cached_setup_keyboard.sh > > Unit 2: > > ConditionPathDoesntExist=/etc/console-setup/cached_setup_keyboard.sh > ConditionPathExists=/bin/setupc
