adplug is marked for autoremoval from testing
adplug 2.2.1+dfsg3-1 is marked for autoremoval from testing on 2019-09-14 It is affected by these RC bugs: 925627: adplug: ftbfs with GCC-9
vzctl is marked for autoremoval from testing
vzctl 4.9.4-6 is marked for autoremoval from testing on 2019-09-14 It (build-)depends on packages with these RC bugs: 925803: ploop: ftbfs with GCC-9
adplay is marked for autoremoval from testing
adplay 1.7-4 is marked for autoremoval from testing on 2019-09-14 It (build-)depends on packages with these RC bugs: 925627: adplug: ftbfs with GCC-9
libcommoncpp2 is marked for autoremoval from testing
libcommoncpp2 1.8.1-7 is marked for autoremoval from testing on 2019-09-14 It is affected by these RC bugs: 925739: libcommoncpp2: ftbfs with GCC-9
mpdtoys is marked for autoremoval from testing
mpdtoys 0.25 is marked for autoremoval from testing on 2019-09-14 It (build-)depends on packages with these RC bugs: 925627: adplug: ftbfs with GCC-9
ploop is marked for autoremoval from testing
ploop 1.15-6 is marked for autoremoval from testing on 2019-09-14 It is affected by these RC bugs: 925803: ploop: ftbfs with GCC-9
vzdump is marked for autoremoval from testing
vzdump 1.2.6-5 is marked for autoremoval from testing on 2019-09-14 It (build-)depends on packages with these RC bugs: 925803: ploop: ftbfs with GCC-9
Your Debian package(s) will not migrate to testing
Dear Debian QA Group, This is a courtesy message about your package(s) which is/are stuck in sid, and will not migrate to testing, in case you are unaware; they are listed below. The release managers announced on 7th July 2019 in their email to debian-devel-announce and debian-release (Message-ID: <20190707014700.gf15...@powdarrmonkey.net>) that only source-only uploads would transition to testing. Here is the relevant part of what they wrote: ~ No binary maintainer uploads for bullseye = The release of buster also means the bullseye release cycle is about to begin. >From now on, we will no longer allow binaries uploaded by maintainers to migrate to testing. This means that you will need to do source-only uploads if you want them to reach bullseye. Q: I already did a binary upload, do I need to do a new (source-only) upload? A: Yes (preferably with other changes, not just a version bump). Q: I needed to do a binary upload because my upload went to the NEW queue, do I need to do a new (source-only) upload for it to reach bullseye? A: Yes. We also suggest going through NEW in experimental instead of unstable where possible, to avoid disruption in unstable. Q: Does this also apply to contrib and non-free? A: No. Not all packages in contrib and non-free can be built on the buildds, so maintainer uploads will still be allowed to migrate for packages outside main. ~ To perform a source-only build and upload, run dpkg-buildpackage -S and then upload the relevant files in the normal way (for example, using dupload or dput). Your package(s) involved is/are as follows: Source package: dosage Version: 2.15-3 One relevant line of the excuse file (including the uploader): Not built on buildd: arch all binaries uploaded by morph, a new source-only upload is needed to allow migration Transition verdict: REJECTED_PERMANENTLY Source package: ffe Version: 0.3.9-1 One relevant line of the excuse file (including the uploader): Not built on buildd: arch amd64 binaries uploaded by sergi...@sergiodj.net Transition verdict: REJECTED_PERMANENTLY Source package: link-grammar Version: 5.6.2-1 One relevant line of the excuse file (including the uploader): Not built on buildd: arch amd64 binaries uploaded by mhatta Transition verdict: REJECTED_PERMANENTLY Source package: qr-tools Version: 1.4~bzr32-1 One relevant line of the excuse file (including the uploader): Not built on buildd: arch all binaries uploaded by blade, a new source-only upload is needed to allow migration Transition verdict: REJECTED_PERMANENTLY Source package: dbus-cpp Version: 5.0.0+18.04.20171031-2 One relevant line of the excuse file (including the uploader): Not built on buildd: arch amd64 binaries uploaded by lamby Transition verdict: REJECTED_PERMANENTLY Source package: collada2gltf Version: 20140924-5 One relevant line of the excuse file (including the uploader): Not built on buildd: arch amd64 binaries uploaded by rene Transition verdict: REJECTED_PERMANENTLY Source package: dh-kpatches Version: 0.99.36+nmu4 One relevant line of the excuse file (including the uploader): Not built on buildd: arch all binaries uploaded by lamby, a new source-only upload is needed to allow migration Transition verdict: REJECTED_PERMANENTLY Source package: twitter-bootstrap Version: 2.0.2+dfsg-10 One relevant line of the excuse file (including the uploader): Not built on buildd: arch all binaries uploaded by lamby, a new source-only upload is needed to allow migration Transition verdict: REJECTED_PERMANENTLY Source package: syslinux-themes-debian Version: 12-4 One relevant line of the excuse file (including the uploader): Not built on buildd: arch all binaries uploaded by deb...@abeckmann.de, a new source-only upload is needed to allow migration Transition verdict: REJECTED_PERMANENTLY Source package: pidgin-openpgp Version: 0.1-2 One relevant line of the excuse file (including the uploader): Not built on buildd: arch all binaries uploaded by tg, a new source-only upload is needed to allow migration Transition verdict: REJECTED_PERMANENTLY I hope this is of help to you! Best wishes, Julian
Bug#934231: anacron: please provide a runscript for runit
Package: anacron
Version: 2.3-29
Followup-For: Bug #934231
Hi,
I have updated the patches and the MR:
First patch adds Gtilab CI test and include a test for the runscript
https://salsa.debian.org/Lorenzo.ru.g-guest/anacron/pipelines/69420
The second one, compared to the previuos version, adds the following:
* bump dh-runit version to 2.8.14 in Build-depends
* add presubj option for dh-runit
* slightly reword the echo messages in run and finish files
Thanks,
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.20.3-van (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages anacron depends on:
ii debianutils 4.8.6.3
ii libc62.28-10
ii lsb-base 11.1.0
Versions of packages anacron recommends:
ii cron [cron-daemon] 3.0pl1-134
Versions of packages anacron suggests:
ii postfix [mail-transport-agent] 3.4.5-1+b1
ii powermgmt-base 1.36
ii socklog [system-log-daemon] 2.1.0+repack-1
-- no debconf information
>From 7b21cdaa7e71ccb4ebe684a333a090f7e82369a1 Mon Sep 17 00:00:00 2001
From: Lorenzo Puliti
Date: Wed, 4 Sep 2019 18:30:06 +0200
Subject: [PATCH 1/2] Add gitlab CI
---
debian/.gitlab-ci.yml | 6 ++
1 file changed, 6 insertions(+)
create mode 100644 debian/.gitlab-ci.yml
diff --git a/debian/.gitlab-ci.yml b/debian/.gitlab-ci.yml
new file mode 100644
index 000..8ca3a45
--- /dev/null
+++ b/debian/.gitlab-ci.yml
@@ -0,0 +1,6 @@
+include:
+ - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+ -
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
+ - https://salsa.debian.org/kaction/daemons/raw/master/pipeline.yml
+variables:
+ RELEASE: unstable
--
2.23.0
>From 0969d723daa71cd8d2cb26e44edebe27c4306c9f Mon Sep 17 00:00:00 2001
From: Lorenzo Puliti
Date: Thu, 8 Aug 2019 13:36:43 +0200
Subject: [PATCH 2/2] Add a runscript for runit
Add a runscript for runit; rely on dh-runit for
maintscripts code.
---
debian/anacron.runit| 1 +
debian/anacron.runscript/finish | 11 +++
debian/anacron.runscript/run| 21 +
debian/control | 2 ++
debian/rules| 2 +-
5 files changed, 36 insertions(+), 1 deletion(-)
create mode 100644 debian/anacron.runit
create mode 100644 debian/anacron.runscript/finish
create mode 100644 debian/anacron.runscript/run
diff --git a/debian/anacron.runit b/debian/anacron.runit
new file mode 100644
index 000..b41198a
--- /dev/null
+++ b/debian/anacron.runit
@@ -0,0 +1 @@
+debian/anacron.runscript logscript,name=anacron,since=2.3-30,presubj
diff --git a/debian/anacron.runscript/finish b/debian/anacron.runscript/finish
new file mode 100644
index 000..45a5ef2
--- /dev/null
+++ b/debian/anacron.runscript/finish
@@ -0,0 +1,11 @@
+#!/bin/sh
+set -e
+
+NAME=Anacron
+
+[ $1 = -1 ] && echo "runsv: ERROR in $NAME: unexpected error or wrong sh
syntax"
+
+[ $1 = 161 ] && echo "runsv: ERROR $1 in $NAME: disabled by local settings" \
+ && sv d $(dirname $0) && exit 0
+
+echo "runsv: $NAME stopped "
diff --git a/debian/anacron.runscript/run b/debian/anacron.runscript/run
new file mode 100644
index 000..dcfb16d
--- /dev/null
+++ b/debian/anacron.runscript/run
@@ -0,0 +1,21 @@
+#!/usr/bin/env /lib/runit/invoke-run
+set -e
+
+NAME=Anacron
+
+exec 2>&1
+
+# exit status of on_ac_power:
+# 0= on-ac // 1= on-battery // 255=unknown, likely a desktop witout APM
+if [ x"$ANACRON_RUN_ON_BATTERY_POWER" != x"yes" -a -x /usr/bin/on_ac_power ];
then
+/usr/bin/on_ac_power || retval=$?
+if [ x"$retval" = x1 ]; then
+echo "deferred while on battery power" && exit 161
+fi
+fi
+
+# don't restart anacron when it's done
+sv once anacron
+
+echo "runsv: starting $NAME..."
+exec /usr/sbin/anacron -d $ANACRON_ARGS
diff --git a/debian/control b/debian/control
index 9a38b23..fc5e3ed 100644
--- a/debian/control
+++ b/debian/control
@@ -3,6 +3,7 @@ Section: admin
Priority: optional
Build-Depends:
debhelper-compat (= 12),
+ dh-runit(>=2.8.14),
Maintainer: Debian QA Group
Standards-Version: 4.2.1
Rules-Requires-Root: no
@@ -12,6 +13,7 @@ Vcs-Browser: https://salsa.debian.org/debian/anacron
Package: anacron
Architecture: any
+Breaks: ${runit:Breaks}
Depends:
debianutils (>= 1.7),
lsb-base (>= 3.0-10),
diff --git a/debian/rules b/debian/rules
index 93acac4..5b251e6 100755
--- a/debian/rules
+++ b/debian/rules
@@ -20,7 +20,7 @@ else
endif
%:
- dh $@
+ dh $@ --with runit
override_dh_auto_install:
$(MAKE) install PREFIX=debian/anacron
MANDIR=debian/anacron/usr/share/man
--
2.23.0
Bug#935034: marked as done (xmldiff: severe memory leak)
Your message dated Wed, 4 Sep 2019 10:10:47 -0400 with message-id and subject line Re: Bug#935034: xmldiff: severe memory leak has caused the Debian Bug report #935034, regarding xmldiff: severe memory leak to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 935034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xmldiff Version: 0.6.10-3 Severity: normal Dear Maintainer, * What led up to the situation? I ran xmldiff on two xml files. * What was the outcome of this action? The program immediately swallowed up all available memory, turning to continues swapping, and made the whole system unresponsive. -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8), LANGUAGE=nl_NL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xmldiff depends on: ii libc6 2.28-10 ii python 2.7.16-1 xmldiff recommends no packages. Versions of packages xmldiff suggests: pn python-psyco pn xmldiff-xmlrev -- no debconf information Nadat de onderhandelingen tussen Wouter Bos en Jan Peter Balkenende mislukt waren maakte D66 echter een coalitie met CDA en VVD mogelijk en voorkwam aldus dat de LPF opnieuw , of de ChristenUnie en de SGP voor het eerst in de regering zouden komen .
Bug#939377: citadel-server: After installation: Webcit cannot connect, server hangs
Package: citadel-server Version: 917-2+b1 Severity: grave Justification: renders package unusable Dear Maintainer, The installation could only be done after I manually removed Exim. I also removed Apache, which might not have been necessary. The Citadel server hangs directly after it is started, so that Webcit and the comman-line client cannot connect: # systemctl status citadel.service ● citadel.service - LSB: control citadel server start at boot time Loaded: loaded (/etc/init.d/citadel; generated) Active: active (exited) since Tue 2019-09-03 21:49:58 CEST; 4min 8s ago Docs: man:systemd-sysv-generator(8) Process: 469 ExecStart=/etc/init.d/citadel start (code=exited, status=0/SUCCESS) Sep 03 21:49:53 frodo systemd[1]: Starting LSB: control citadel server start at boot time... Sep 03 21:49:58 frodo systemd[1]: Started LSB: control citadel server start at boot time. Sep 03 21:50:00 frodo citserver[666]: db: cursor still in progress on cdb 00: attempt to write during r/o cursor So the server is lying as it reports success without actually working. The files /var/lib/citadel/data/cdb* are owned by root:root. If I remove them, they are recreated in the same way with the same error. The situation is the same if I manually set their ownership to citadel:citadel. The files can be verified: # db_verify cdb.0* BDB5105 Verification of cdb.00 succeeded. […] db-util/stable,now 5.3.1+nmu1 all [installed] db5.3-util/stable,now 5.3.28+dfsg1-0.5 i386 [installed,automatic] -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-5-686-pae (SMP w/1 CPU core) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages citadel-server depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10 ii libcitadel4917-2 ii libcurl4 7.64.0-4 ii libdb5.3 5.3.28+dfsg1-0.5 ii libexpat1 2.2.6-2 ii libical3 3.0.4-3 ii libldap-2.4-2 2.4.47+dfsg-3 ii libpam0g 1.3.1-5 ii libsieve2-12.2.6-2 ii libssl1.1 1.1.1c-1 ii lsb-base 10.2019051400 ii openssl1.1.1c-1 ii patch 2.7.6-3+deb10u1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages citadel-server recommends: pn db4.6-util ii shared-mime-info 1.10-1 citadel-server suggests no packages. -- Configuration Files: /etc/citadel/messages/changepw [Errno 13] Permission denied: '/etc/citadel/messages/changepw' /etc/citadel/messages/goodbye [Errno 13] Permission denied: '/etc/citadel/messages/goodbye' /etc/citadel/messages/hello [Errno 13] Permission denied: '/etc/citadel/messages/hello' /etc/citadel/messages/newuser [Errno 13] Permission denied: '/etc/citadel/messages/newuser' /etc/citadel/messages/register [Errno 13] Permission denied: '/etc/citadel/messages/register' /etc/citadel/messages/roomaccess [Errno 13] Permission denied: '/etc/citadel/messages/roomaccess' /etc/citadel/messages/unlisted [Errno 13] Permission denied: '/etc/citadel/messages/unlisted' -- debconf information: * citadel/ServerIPAddress: 0.0.0.0 citadel/BadUser: citadel/LDAPServer: 0.0.0.0 * citadel/LoginType: Internal citadel/LDAPServerPort: 389 * citadel/Administrator: admin citadel/LDAPBindDNPassword: OpenSesame citadel/LDAPBaseDN: dc=example,dc=com citadel/LDAPBindDN: *** I had to remove the Citadel server as I needed a working MTA. *** -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-5-686-pae (SMP w/1 CPU core) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages citadel-server depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10 ii libcitadel4917-2 ii libcurl4 7.64.0-4 ii libdb5.3 5.3.28+dfsg1-0.5 ii libexpat1 2.2.6-2 ii libical3 3.0.4-3 ii libldap-2.4-2 2.4.47+dfsg-3 ii libpam0g 1.3.1-5 ii libsieve2-12.2.6-2 ii libssl1.1 1.1.1c-1 ii lsb-base 10.2019051400 ii openssl1.1.1c-1 ii patch 2.7.6-3+deb10u1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages citadel-server recommends: pn db4.6-util ii shared-mime-info 1.10-1 citadel-server suggests no packages.
Découvrez les offres Back to school !
Se désinscrire de la liste: http://link.wibzen.com/u/443/76e431eb0623a25e1962a2e3e5b20015e1395b2e4a9387e7
Bug#935034: xmldiff: severe memory leak
Sandro Tosi schreef op de 2e dag van de herfstmaand van het jaar 2019: > On Sun, 18 Aug 2019 13:59:42 +0200 Peter Kleiweg wrote: > > Package: xmldiff > > Version: 0.6.10-3 > > Severity: normal > > > > Dear Maintainer, > > > >* What led up to the situation? > > > > I ran xmldiff on two xml files. > > > >* What was the outcome of this action? > > > > The program immediately swallowed up all available memory, turning to > > continues > > swapping, and made the whole system unresponsive. > > can you try again with the xmldiff 2.3, recently uploaded to Debian? version 2.3 seems to be working fine -- Peter
Découvrez les offres Back to school !
Afin de voir votre message, cliquez sur le lien: http://link.datanews.ovh/v/443/240a316e003c5a0bffca2afeaf93ee777565ddcdc72aaf5c
