hovercraft 2.7-5 is marked for autoremoval from testing on 2023-12-24
It (build-)depends on packages with these RC bugs:
1055159: python-svg.path: python-svg.path's autopkg tests fail with pillow
10.1.0
https://bugs.debian.org/1055159
This mail is generated by:
https://salsa.debian.org/releas
python-svg.path 6.3-1 is marked for autoremoval from testing on 2023-12-24
It is affected by these RC bugs:
1055159: python-svg.path: python-svg.path's autopkg tests fail with pillow
10.1.0
https://bugs.debian.org/1055159
This mail is generated by:
https://salsa.debian.org/release-team/releas
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 30 Nov 2023 01:28:16 +0100
Source: python-jenkinsapi
Architecture: source
Version: 0.3.13-1
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group
Changed-By: A
python-jenkinsapi_0.3.13-1_source.changes uploaded successfully to localhost
along with the files:
python-jenkinsapi_0.3.13-1.dsc
python-jenkinsapi_0.3.13.orig.tar.gz
python-jenkinsapi_0.3.13-1.debian.tar.xz
python-jenkinsapi_0.3.13-1_source.buildinfo
Greetings,
Your Debian queue
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 24 Nov 2023 18:20:14 +0100
Source: unadf
Architecture: source
Version: 0.7.11a-5+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian QA Group
Changed-By: M
Your message dated Wed, 29 Nov 2023 22:47:14 +
with message-id
and subject line Bug#838248: fixed in unadf 0.7.11a-5+deb12u1
has caused the Debian Bug report #838248,
regarding unadf: CVE-2016-1243 and CVE-2016-1244
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Wed, 29 Nov 2023 22:47:14 +
with message-id
and subject line Bug#838248: fixed in unadf 0.7.11a-5+deb12u1
has caused the Debian Bug report #838248,
regarding unadf 0.7.11a-5 calls system() with unsanitized input
to be marked as done.
This means that you claim that the probl
Source-only uploads to NEW are not allowed.
binary:smuxi-engine is NEW.
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
smuxi_1.1-3_source.changes uploaded successfully to localhost
along with the files:
smuxi_1.1-3.dsc
smuxi_1.1-3.debian.tar.xz
smuxi_1.1-3_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Wed, 29 Nov 2023 19:46:36 +
with message-id
and subject line Bug#1052496: fixed in zope.i18nmessageid 6.1.0-1
has caused the Debian Bug report #1052496,
regarding zope.i18nmessageid: please package v6.0.1 and drop dependency on six
to be marked as done.
This means that you
Your message dated Wed, 29 Nov 2023 19:46:36 +
with message-id
and subject line Bug#1046707: fixed in zope.i18nmessageid 6.1.0-1
has caused the Debian Bug report #1046707,
regarding zope.i18nmessageid: Fails to build source after successful build
to be marked as done.
This means that you clai
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
smuxi |1.1-1.2 | all
smuxi-engine | 1.1-2 | all
--- Reason ---
RoQA; NBS; useless metapackage
--
Version: 0.0~git20161222.0.85786f5-7+rm
Dear submitter,
as the package golang-github-go-macaron-bindata 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, pl
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
golang-github-go-macaron-bindata | 0.0~git20161222.0.85786f5-7 | source
golang-github-go-macaron-bindata-dev | 0.0~git20161222.0.85786f5-7 | all
--- Reason
Your message dated Wed, 29 Nov 2023 18:34:05 +
with message-id
and subject line Bug#1055840: Removed package(s) from unstable
has caused the Debian Bug report #1039169,
regarding dhis-client: ships sysv-init script without systemd unit
to be marked as done.
This means that you claim that the
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
dhis-client | 5.5-6 | source, amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, riscv64, s390x
--- Reason ---
RoQA; dead upstream, orphaned
---
Version: 5.5-6+rm
Dear submitter,
as the package dhis-client 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/1055840
Th
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #1039156,
regarding cpufreqd: ships sysv-init script without systemd unit
to be marked as done.
This means that you claim that the pro
Version: 2.4.2-5+rm
Dear submitter,
as the package cpufreqd 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/1056251
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
cpufreqd |2.4.2-5 | source, amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, riscv64, s390x
--- Reason ---
RoQA; orphaned, uses obsolete cpufrequ
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #966620,
regarding cpufreqd: No turbo mode for Ryzen 4750U
to be marked as done.
This means that you claim that the problem has been d
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #883009,
regarding cpufreqd: flood syslog with reporting missing /sys files
to be marked as done.
This means that you claim that the p
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #733545,
regarding cpufreqd should honour bios_limit when setting max/min freq
to be marked as done.
This means that you claim that th
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #647713,
regarding fails to build from source twice
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #627265,
regarding cpufreqd: should not use numeric signals in init script
to be marked as done.
This means that you claim that the pr
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #684446,
regarding cpufreqd: 'man cpufreqd' typos: "configration", "mimimum",
"paramters" and "writeable"
to be marked as done.
This
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #626852,
regarding cpufreqd: shows failure to start at boot, yet it works
to be marked as done.
This means that you claim that the pro
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #602032,
regarding cpufreqd: WTF is my machine burning up? AMD 64 bit Turion.
to be marked as done.
This means that you claim that th
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #627649,
regarding Please don't use obsolete libsysfs-dev any more
to be marked as done.
This means that you claim that the problem ha
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #583663,
regarding cpufreqd: fails to start when parallellized boot is enabled
to be marked as done.
This means that you claim that th
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #605643,
regarding make cpufreqd-get show also active rule
to be marked as done.
This means that you claim that the problem has been d
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #566528,
regarding [cpufreqd] cpufreq-info no longer returns correct frequency range
to be marked as done.
This means that you claim t
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #428249,
regarding makes bad choices on desktop
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #458012,
regarding cpufreqd: Automatic loading of modules stops on the first error
to be marked as done.
This means that you claim tha
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #583663,
regarding cpufreqd: CPU Frequency daemon start failed!
to be marked as done.
This means that you claim that the problem h
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #403428,
regarding cpufreqd: modprobe call at init script with no arguments
to be marked as done.
This means that you claim that the p
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #537219,
regarding cpufreqd still complaints about missing files in
/sys/class/power_supply
to be marked as done.
This means that you
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #416618,
regarding cpufreqd: I'd like to see acpi lid support
to be marked as done.
This means that you claim that the problem has bee
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #330409,
regarding cpufreqd: restore full scaling range upon removal
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #1044574,
regarding cpufreqd: Fails to build source after successful build
to be marked as done.
This means that you claim that the pr
Your message dated Wed, 29 Nov 2023 18:30:32 +
with message-id
and subject line Bug#1056251: Removed package(s) from unstable
has caused the Debian Bug report #1012736,
regarding cpufreqd: failed to parse profile= per CPU node at Rules section.
to be marked as done.
This means that you claim
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 Nov 2023 18:01:47 +0100
Source: apt-xapian-index
Architecture: source
Version: 0.54
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group
Changed-By: Alexan
apt-xapian-index_0.54_source.changes uploaded successfully to localhost
along with the files:
apt-xapian-index_0.54.dsc
apt-xapian-index_0.54.tar.xz
apt-xapian-index_0.54_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Wed, 29 Nov 2023 17:19:04 +
with message-id
and subject line Bug#968060: fixed in apt-xapian-index 0.54
has caused the Debian Bug report #968060,
regarding axi-cache: string/bytes confusion in display
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Nov 2023 17:19:04 +
with message-id
and subject line Bug#1039456: fixed in apt-xapian-index 0.54
has caused the Debian Bug report #1039456,
regarding apt-xapian-index: missing depedency on python3-six
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 29 Nov 2023 17:19:04 +
with message-id
and subject line Bug#1018310: fixed in apt-xapian-index 0.54
has caused the Debian Bug report #1018310,
regarding apt-xapian-index: build-depends on python3-nose or uses it for
autopkgtest
to be marked as done.
This means that yo
Your message dated Wed, 29 Nov 2023 17:19:04 +
with message-id
and subject line Bug#940987: fixed in apt-xapian-index 0.54
has caused the Debian Bug report #940987,
regarding rdetails fails: TypeError: sequence item 0: expected str instance,
bytes found
to be marked as done.
This means that
Your message dated Wed, 29 Nov 2023 17:19:04 +
with message-id
and subject line Bug#1032332: fixed in apt-xapian-index 0.54
has caused the Debian Bug report #1032332,
regarding apt-xapian-index: Fails to install due to missing dependency on
python3-six
to be marked as done.
This means that y
48 matches
Mail list logo
