Bug#796635: nvi: Has init script in runlevel S but no matching service file

Package: nvi Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package nvi has an initscript that is enabled in runlevel S, but it does not provide a corresponding systemd service unit. Systemd generates units for all sysv init scripts

Bug#796630: rdnssd: Has init script in runlevel S but no matching service file

Package: rdnssd Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package rdnssd has an initscript that is enabled in runlevel S, but it does not provide a corresponding systemd service unit. Systemd generates units for all sysv init sc

Bug#796588: adjtimex: Has init script in runlevel S but no matching service file

Package: adjtimex Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package adjtimex has an initscript that is enabled in runlevel S, but it does not provide a corresponding systemd service unit. Systemd generates units for all sysv ini

Bug#796472: zshdb: update to latest upstream 0.09

Package: zshdb Followup-For: Bug #796472 Control: notforwarded -1 Hi, The problems with the tests that have been seen are a bug in zsh, not a bug in the upstream zshdb project. From #pkg-zsh: ft ╡ I bet this is caused by what is fixed in 35412 ∟ ╡ zsh-workers reference number that is. ∟

Processed: Re: zshdb: update to latest upstream 0.09

Processing control commands: > notforwarded -1 Bug #796472 [zshdb] zshdb: update to latest upstream 0.09 Unset Bug forwarded-to-address -- 796472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#796483: Removed package(s) from unstable

Version: 0.99.3-4+rm Dear submitter, as the package colrconv has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/796483 The

Bug#796483: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: colrconv | 0.99.3-4 | source, amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x colrconv | 0.99.3-4+b1 | hurd-i386 -

libytnef_1.5-9_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 22 Aug 2015 11:10:24 +0200 Source: libytnef Binary: libytnef0 libytnef0-dev Architecture: source amd64 Version: 1.5-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Ricardo Mones D

Bug#742146: marked as done (libytnef: fails to build with clang instead of gcc)

Your message dated Sat, 22 Aug 2015 09:41:32 + with message-id and subject line Bug#742146: fixed in libytnef 1.5-9 has caused the Debian Bug report #742146, regarding libytnef: fails to build with clang instead of gcc to be marked as done. This means that you claim that the problem has been

Processing of libytnef_1.5-9_amd64.changes

libytnef_1.5-9_amd64.changes uploaded successfully to localhost along with the files: libytnef_1.5-9.dsc libytnef_1.5-9.debian.tar.xz libytnef0-dev_1.5-9_amd64.deb libytnef0_1.5-9_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)