transaction is marked for autoremoval from testing
transaction 3.0.0-1 is marked for autoremoval from testing on 2024-07-21 It is affected by these RC bugs: 1072780: transaction: fails to migrate to testing for too long: uploader built arch:all binary https://bugs.debian.org/1072780 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
python-restless is marked for autoremoval from testing
python-restless 2.2.0-2 is marked for autoremoval from testing on 2024-07-21 It (build-)depends on packages with these RC bugs: 1072780: transaction: fails to migrate to testing for too long: uploader built arch:all binary https://bugs.debian.org/1072780 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
zope.location is marked for autoremoval from testing
zope.location 5.0-1 is marked for autoremoval from testing on 2024-07-21 It (build-)depends on packages with these RC bugs: 1072780: transaction: fails to migrate to testing for too long: uploader built arch:all binary https://bugs.debian.org/1072780 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
libwibble is marked for autoremoval from testing
libwibble 1.1-3 is marked for autoremoval from testing on 2024-06-28
It is affected by these RC bugs:
1070014: libwibble: FTBFS on arm{64,el}: (7/36) Fs: ../wibble/sys/fs.test.h:
72: assertion `i.ischr()' failed;
https://bugs.debian.org/1070014
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
guessnet is marked for autoremoval from testing
guessnet 0.58 is marked for autoremoval from testing on 2024-06-28
It (build-)depends on packages with these RC bugs:
1070014: libwibble: FTBFS on arm{64,el}: (7/36) Fs: ../wibble/sys/fs.test.h:
72: assertion `i.ischr()' failed;
https://bugs.debian.org/1070014
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
Bug#1039340: marked as done (ramond: ships sysv-init script without systemd unit)
Your message dated Sun, 16 Jun 2024 01:46:33 + with message-id and subject line Bug#1073277: Removed package(s) from unstable has caused the Debian Bug report #1039340, regarding ramond: ships sysv-init script without systemd unit 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.) -- 1039340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ramond Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), ramond has been flagged by Lintian as shipping a sysv-init script without a corresponding systemd unit file. The default init system in Debian is systemd, and so far this worked because a transitional sysv-init-to-unit generator was shipped by systemd. This is in the process of being deprecated and will be removed by the time Trixie ships, so the remaining packages that ship init scripts without systemd units will stop working. There are various advantages to using native units, for example the legacy generator cannot tell the different between a oneshot service and a long running daemon. Also, sanboxing and security features become available for services. For more information, consult the systemd documentation: https://www.freedesktop.org/software/systemd/man/systemd.unit.html You can find the Lintian warning here: https://lintian.debian.org/sources/ramond In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks! --- End Message --- --- Begin Message --- Version: 0.5-6+rm Dear submitter, as the package ramond 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/1073277 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1073277: Removed package(s) from unstable
Version: 0.5-6+rm Dear submitter, as the package ramond 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/1073277 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1073277: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: ramond | 0.5-6 | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x --- Reason --- RoQA; unmaintained, dead upstream, unused -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1073...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1073277 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1073136: Removed package(s) from unstable
Version: 2.3.3-2+rm Dear submitter, as the package kmfl-keyboards-mywin 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/1073136 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1073136: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: kmfl-keyboards-mywin |2.3.3-2 | source, all --- Reason --- ROQA; libkmfl superseded by src:keyman -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1073...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1073136 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#875831: marked as done (ramond: Crashes on rule without prefix attribute)
Your message dated Sun, 16 Jun 2024 01:46:33 + with message-id and subject line Bug#1073277: Removed package(s) from unstable has caused the Debian Bug report #875831, regarding ramond: Crashes on rule without prefix attribute 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.) -- 875831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ramond Version: 0.5-4 Severity: normal Tags: ipv6 Dear Maintainer, when defining rules without a prefix attribute, then ramond crashes as soon as the rule is hit. Able to reproduce on amd64 and armhf (Raspbian). Here's an example config that will crash on the very first router advertisement. /etc/ramond.conf: /usr/local/sbin/ramond.sh route-cleared /usr/local/sbin/ramond.sh route-advertised -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core) 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: systemd (via /run/systemd/system) Versions of packages ramond depends on: ii libapr1 1.5.2-5 ii libc6 2.24-11+deb9u1 ii libpcap0.8 1.8.1-3 ii libxml2 2.9.4+dfsg1-2.2 ii zlib1g 1:1.2.8.dfsg-5 ramond recommends no packages. ramond suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.5-6+rm Dear submitter, as the package ramond 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/1073277 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#753298: marked as done (ramond: setenv("FOO", NULL) results in a mangled environment for the child process that ramond forks)
Your message dated Sun, 16 Jun 2024 01:46:33 +
with message-id
and subject line Bug#1073277: Removed package(s) from unstable
has caused the Debian Bug report #753298,
regarding ramond: setenv("FOO", NULL) results in a mangled environment for the
child process that ramond forks
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.)
--
753298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ramond
Version: 0.5-4
Severity: important
Tags: patch
Dear Maintainer,
ramond runs a process when it detects a problem. remond send the prefix
detected to the child via environment vairables. If the Rogue Router
Announcement does not contain a prefix the enviromnent vairables are
garbled. changing setenv("FOO", NULL) to setenv("FOO", "") fixes it.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-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
Versions of packages ramond depends on:
ii libapr1 1.5.1-2
ii libc6 2.19-4
ii libpcap0.8 1.5.3-4
ii libxml2 2.9.1+dfsg1-3
ii zlib1g 1:1.2.8.dfsg-1
ramond recommends no packages.
ramond suggests no packages.
-- no debconf information
--- ramond-0.5.orig/src/main.c
+++ ramond-0.5/src/main.c
@@ -567,8 +567,8 @@ void executeActions(struct rule *this_ru
}
else
{
- setenv("PREFIX", NULL, 1);
- setenv("PREFIX_LEN", NULL, 1);
+ setenv("PREFIX", "", 1);
+ setenv("PREFIX_LEN", "", 1);
}
setenv("SOURCE_ADDR", data->from_str, 1);
--- End Message ---
--- Begin Message ---
Version: 0.5-6+rm
Dear submitter,
as the package ramond 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/1073277
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1039397: marked as done (tircd: ships sysv-init script without systemd unit)
Your message dated Sun, 16 Jun 2024 00:59:30 + with message-id and subject line Bug#1073081: Removed package(s) from unstable has caused the Debian Bug report #1039397, regarding tircd: ships sysv-init script without systemd unit 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.) -- 1039397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tircd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), tircd has been flagged by Lintian as shipping a sysv-init script without a corresponding systemd unit file. The default init system in Debian is systemd, and so far this worked because a transitional sysv-init-to-unit generator was shipped by systemd. This is in the process of being deprecated and will be removed by the time Trixie ships, so the remaining packages that ship init scripts without systemd units will stop working. There are various advantages to using native units, for example the legacy generator cannot tell the different between a oneshot service and a long running daemon. Also, sanboxing and security features become available for services. For more information, consult the systemd documentation: https://www.freedesktop.org/software/systemd/man/systemd.unit.html You can find the Lintian warning here: https://lintian.debian.org/sources/tircd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks! --- End Message --- --- Begin Message --- Version: 0.30-4.1+rm Dear submitter, as the package tircd 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/1073081 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1039297: marked as done (omnievents: ships sysv-init script without systemd unit)
Your message dated Sun, 16 Jun 2024 01:00:01 + with message-id and subject line Bug#1073082: Removed package(s) from unstable has caused the Debian Bug report #1039297, regarding omnievents: ships sysv-init script without systemd unit 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.) -- 1039297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: omnievents Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), omnievents has been flagged by Lintian as shipping a sysv-init script without a corresponding systemd unit file. The default init system in Debian is systemd, and so far this worked because a transitional sysv-init-to-unit generator was shipped by systemd. This is in the process of being deprecated and will be removed by the time Trixie ships, so the remaining packages that ship init scripts without systemd units will stop working. There are various advantages to using native units, for example the legacy generator cannot tell the different between a oneshot service and a long running daemon. Also, sanboxing and security features become available for services. For more information, consult the systemd documentation: https://www.freedesktop.org/software/systemd/man/systemd.unit.html You can find the Lintian warning here: https://lintian.debian.org/sources/omnievents In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks! --- End Message --- --- Begin Message --- Version: 1:2.6.2-6.1+rm Dear submitter, as the package omnievents 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/1073082 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1073084: Removed package(s) from unstable
Version: 1.15-13+rm Dear submitter, as the package ploop 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/1073084 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1073084: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libploop-dev | 1.15-13+b1 | amd64, i386 libploop1 | 1.15-13+b1 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x ploop |1.15-13 | source ploop | 1.15-13+b1 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x --- Reason --- RoQA; depends on obsolete kernel module; orphaned; dead upstream -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1073...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1073084 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1073082: Removed package(s) from unstable
Version: 1:2.6.2-6.1+rm Dear submitter, as the package omnievents 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/1073082 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1073082: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libomnievents-dev | 1:2.6.2-6.1 | armel, armhf libomnievents-dev | 1:2.6.2-6.1+b1 | amd64, arm64, i386, mips64el, ppc64el, riscv64, s390x libomnievents2t64 | 1:2.6.2-6.1 | armel, armhf libomnievents2t64 | 1:2.6.2-6.1+b1 | amd64, arm64, i386, mips64el, ppc64el, riscv64, s390x omnievents | 1:2.6.2-6.1 | source, armel, armhf omnievents | 1:2.6.2-6.1+b1 | amd64, arm64, i386, mips64el, ppc64el, riscv64, s390x omnievents-doc | 1:2.6.2-6.1 | all --- Reason --- RoQA; orphaned; upstream orphaned -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1073...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1073082 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1073081: Removed package(s) from unstable
Version: 0.30-4.1+rm Dear submitter, as the package tircd 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/1073081 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1073081: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: tircd | 0.30-4.1 | source, all --- Reason --- RoQA; obsolete; orphaned -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1073...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1073081 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1072999: Removed package(s) from unstable
Version: 1:3.3.6ds1-34+rm Dear submitter, as the package gcc-3.3 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/1072999 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1072999: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: gcc-3.3 | 1:3.3.6ds1-34 | source libstdc++5 | 1:3.3.6-34 | amd64, i386 --- Reason --- RoQA; orphaned; leaf pkg; build-depends on autoconf2.13 -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1072...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1072999 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#677825: marked as done (Default configuration of auto_post=0 is confusing on upgrade)
Your message dated Sun, 16 Jun 2024 00:59:30 + with message-id and subject line Bug#1073081: Removed package(s) from unstable has caused the Debian Bug report #677825, regarding Default configuration of auto_post=0 is confusing on upgrade 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.) -- 677825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tircd Version: 0.21.2-2 Severity: grave For the last few days, my attempts to set status through tircd have quietly done nothing. I assume this is due to a Twitter API change and might need to be fixed in libnet-twitter-lite-perl rather than tircd. Ben. -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (100, 'proposed-updates'), (100, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tircd depends on: ii adduser 3.112+nmu2 add and remove users and groups ii libhtml-parser-perl 3.66-1 collection of modules that parse H ii libjson-any-perl 1.22-1 wrapper class for the various JSON ii libnet-twitter-lite-perl 0.10003-1 interface to the Twitter API ii libpoe-filter-ircd-perl 2.42-1 parser for the IRC protocol ii libpoe-perl 2:1.2890-1 event-driven component architectur ii liburi-perl 1.60-1 module to manipulate and access UR ii libwww-perl 5.836-1Perl HTTP/WWW client/server librar tircd recommends no packages. tircd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.30-4.1+rm Dear submitter, as the package tircd 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/1073081 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#527258: marked as done (tircd: please offer identica connect additionally)
Your message dated Sun, 16 Jun 2024 00:59:30 + with message-id and subject line Bug#1073081: Removed package(s) from unstable has caused the Debian Bug report #527258, regarding tircd: please offer identica connect additionally 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.) -- 527258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tircd Version: 0.7-1 Severity: minor Tags: upstream Hi! Given that being able to connect to identica instead of twitter with tircd is just a s/Twitter/Identica/g in the tircd script away it might be a good idea to either offer a second script named iircd or make it a configure option to rather use the Net::Identica modules instead of the Net::Twitter ones. Thanks. :) Rhonda --- End Message --- --- Begin Message --- Version: 0.30-4.1+rm Dear submitter, as the package tircd 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/1073081 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1020239: marked as done (gcc-3.3: build-depends on gsfonts-x11 should be replaced by fonts-urw-base35)
Your message dated Sun, 16 Jun 2024 00:56:13 + with message-id and subject line Bug#1072999: Removed package(s) from unstable has caused the Debian Bug report #1020239, regarding gcc-3.3: build-depends on gsfonts-x11 should be replaced by fonts-urw-base35 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.) -- 1020239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-3.3 Version: 1:3.3.6ds1-34 Severity: normal Dear Maintainer, we are currently removing the old gsfonts-x11 package and replace it by fonts-urw-base35, which contains the real fonts (replaces gsfonts) as well as the symlinks and fonts.scale/fonts.alias voodoo, which is needed for using the fonts in X11. Your source package gcc-3.3 currently Build-Depends on gsfonts-x11. It would be a good idea to change this dependency to fonts-urw-base35 (or for backward compatibility to fonts-urw-base35 | gsfonts-x11). For the release of bookworm this shouldn't be a problem, since we ship a dummy package gsfonts-x11 depending on fonts-urw-base35, but it would be a good idea to change the dependency anyway soon. Except this, I'm curious, what this Build-Depends is good for at all. The package gsfonts-x11 doesn't ship fonts itself but depends on the gsfonts package (shipping Type1 fonts) and makes them available to X11. From my point of view this is only useful for some desktop environment using X11 but should not be used in Build-Depends. Greetings Roland --- End Message --- --- Begin Message --- Version: 1:3.3.6ds1-34+rm Dear submitter, as the package gcc-3.3 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/1072999 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processing of cava-alsa_0.10.2-1_source.changes
cava-alsa_0.10.2-1_source.changes uploaded successfully to localhost along with the files: cava-alsa_0.10.2-1.dsc cava-alsa_0.10.2.orig.tar.gz cava-alsa_0.10.2-1.debian.tar.xz cava-alsa_0.10.2-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
cava-alsa_0.10.2-1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 09 Jun 2024 14:03:50 -0300 Source: cava-alsa Architecture: source Version: 0.10.2-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Matheus Polkorny Changes: cava-alsa (0.10.2-1) unstable; urgency=medium . * QA upload. * New upstream version 0.10.2 * d/cava.1: Update manual * d/control: - Bump Standards-Version to 4.7.0 - Remove Uploaders field - Update Build-Depends - Update description * d/copyright: Update to the new release * d/patches: - 0001-Remove-rpath.patch: Drop patch, unnecessary in the new release - 0001-typo.patch: New patch to fix typo - 0002-Typo.patch: Forwarded to Upstream and apply DEP-3 - missing-prototypes.patch: Drop patch, unnecessary in the new release * d/rules: Remove unnecessary command in the new release Checksums-Sha1: 22eb45d1a5a533424a713a4cd3f6aa8ffca3ccc9 2018 cava-alsa_0.10.2-1.dsc 395974082d5274f2037d4d5c47937a189d16fcc7 130036 cava-alsa_0.10.2.orig.tar.gz a4f743aac1e8c9faffbcbaffe7241dcd72ed5ceb 3728 cava-alsa_0.10.2-1.debian.tar.xz 6f1dfc7b5f65050fb691b28e2ef4aa1b939234d1 11524 cava-alsa_0.10.2-1_amd64.buildinfo Checksums-Sha256: 0ab2e499af25158a137fc75efd9185ecefd0456459684157f2cb30a728a2da03 2018 cava-alsa_0.10.2-1.dsc 853ee78729ed3501d0cdf9c1947967ad3bfe6526d66a029b4ddf9adaa6334d4f 130036 cava-alsa_0.10.2.orig.tar.gz 8ed437b585b8339bf750fd0ba9c0b04d1736f3a45d99aa63dd2b0e5dc1f0593d 3728 cava-alsa_0.10.2-1.debian.tar.xz 1a3c700d4be602d0255949889d6ab5fcb78543a375a22e113a38325c8a87ed77 11524 cava-alsa_0.10.2-1_amd64.buildinfo Files: a0b169c2358b60a689630542de8bf93a 2018 sound optional cava-alsa_0.10.2-1.dsc 5d2b051d7c9ad9bdb950e3e4dd5ebc9e 130036 sound optional cava-alsa_0.10.2.orig.tar.gz 3ae265c5ab9106d1606d3d333c457638 3728 sound optional cava-alsa_0.10.2-1.debian.tar.xz 90e78a1dbcd3871e70070b43e6771fd2 11524 sound optional cava-alsa_0.10.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEI3pUsQKHKL8A7zH00Ot2KGX8XjYFAmZuIAsUHHNlcmdpb2Rq QGRlYmlhbi5vcmcACgkQ0Ot2KGX8XjaEsw/9Fz49V7+X4BmmAA/3dqfrmJGImM6a ZqYm/FGdFBRIVu3meJXaL2/bXyMPYLF73AySEMavT2sBA7AkNk2WeevBxiP0DEOk Av7j4sjJfsVLzxTrBIE8XFe2dFT1NhdKRDWFjq4tPkdYSQZ950oMmCtAjNVce3mU 9iWR5DK2KYQ8Y1SV70d1LHDn0XAjnQ0iVCm+Td4JRjoHXu1Fr6HupZRmZewraHJo lYkA6ANty+nTOXQFnD+9GcDAkBsEFXSTP1bl3O7MDUQfwOYBxxN0nKP7LIISKszT DvIseRjGGXWLoXDaIyJ7i6ws10w72sjgzRUH61nTNDpmCQHGQ6LRwGespVE4LDn8 3YLDk3zOGZK/jtl0O/9hMIPPB8cSDD9HlyB7pfssyODPPZSMaxz/8gbuNuEbaIJS 2RhyUZ2eb2sz3Q2j6aH+ClxiR9Ntn1N/FJiYnyc2kC5jyLnhU5zaYJG53Ehwl5MM AnsZ6cxux3JM01GaBT7trJXmtwgOfNT/+1UAHN7kJw4sY4rR1QXsIpyazFkuyoso q6D098GgWXWc3IemlsqG8TyL2aLhjMGCbVWTpEYnWy9Jn+TMs6rQdQ6Magq4C2Bz KtypX2z3vurBZXHfUAE98S0qJ5uHVsHSkex8nkBdwO04ZUL0uNOpJCkmqJOls6k1 1B0HL9qO90uNyEE= =wlZD -END PGP SIGNATURE- pgpTN9JIHE2z8.pgp Description: PGP signature
pymongo_4.7.3-1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 15 Jun 2024 16:25:28 + Source: pymongo Architecture: source Version: 4.7.3-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastien Roucariès Closes: 748424 752525 1034525 1036815 Changes: pymongo (4.7.3-1) unstable; urgency=medium . * QA upload * Update d/watch * Import python team repo * Use any-arm instead of any-armel and any-armhf (Closes: #1034525) * Move homepage (Closes: #1036815) * New upstream releae: + Fix "helpers.py enforces strict checking for sort() values" (Closes: #748424) + Move pure python package to arch:all (Closes: #752525) + Fix CVE-2024-5629 Checksums-Sha1: cf379d7af8b31048ed99a26035fe1277094ed026 2553 pymongo_4.7.3-1.dsc 996643da2259c85210b1d0312c2ceba2b7bea912 1548275 pymongo_4.7.3.orig.tar.gz 689ab9e5bdbc96cf3ee479671c7f48c3d13a6003 9992 pymongo_4.7.3-1.debian.tar.xz b5d816cb54d1b9633370fd59c611736e06e6e7d1 10468 pymongo_4.7.3-1_amd64.buildinfo Checksums-Sha256: 457a136c0db08895020b587f4c567ab9eff93a9da6d5080f2f94f3723cd0f553 2553 pymongo_4.7.3-1.dsc 4fd2d390c2f9d8aa6291ce2bfbc9f6e8a360adb0e7b238e730874011e27a 1548275 pymongo_4.7.3.orig.tar.gz c1d2917d60d9bf3678cf3087298dad5781c5c03132df3e84b239707cefa973de 9992 pymongo_4.7.3-1.debian.tar.xz d97e8889af4d2fa5dcc379f104a716b1f50dd1d32eb1bca70430c8551aa5da45 10468 pymongo_4.7.3-1_amd64.buildinfo Files: b5c1dbf2f9bcbc4d375097af1897ffd2 2553 python optional pymongo_4.7.3-1.dsc 42076fe4ebbbceeadcf980a4aa41a90d 1548275 python optional pymongo_4.7.3.orig.tar.gz a30a5680c89a5a427aaed16ac2b1064c 9992 python optional pymongo_4.7.3-1.debian.tar.xz a6f23a44e9b931f5da80e504af6b20d5 10468 python optional pymongo_4.7.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmZuDDcRHHJvdWNhQGRl Ymlhbi5vcmcACgkQADoaLapBCF83xw//cg468Fs6QDsSjA7ZF3hF10owC/g/eIwj HEqBbwtQa9M9xdEH2/2eejkA8iHxPTj2W+WdOZTIfeZoNUECnOrxRjSuuXqrD8dj RO2hyPy7QImUwaoc0n7dSPm22xGWPCLNVf+BmwXRMvbwIBJzV4C2DK2QBS7LuVPF Br6VzAD8Mr7LeLvMFLeIZjmgbc/tlafvHgKLmzbE6oa1CVJWHSn2XXlm8oXJ/1ig LjDPip+cKOiSBu/8m0socHUhjzTK7DlGlRmrKTBKb8DanwK0TkR7itfk1NLAHliV /pb1AfYY9O5s77BkUwOtlgf8rOcpsRICGEvYZQwHih3rzEUXHBTMmgqQHz5p5yqs I9uWOShsXN+ZbluZS9WoMSqdn6CjaL0CFqZq9b8lSOwAtoN2EM/U7CsamLkYpOjp JIlrvRDWzQuj4AZqR53M7SBtkVlXFiJRY8mRygpz4Dy7Bi9TDQs13oCGST5lIDiO n1OTscyUeY9B7D4gfCmL1ujow1GKVJ53+556vOAury3H+31XYpkkTJho1PdVLaW4 BHxdqYSyXvTCSbtyBDm8myVP7eHslYwX7dDfS1P80J/BIMLn+pXDIR8TnSSl65oI z7yEUOIBFcM0LODZl2E6j9IEWHyQ4SQ/uMv1TjB/H0aPxEoyirq0QdAqY8S1Xmbc D1XY97KeK20= =cL5f -END PGP SIGNATURE- pgp8ROg4Tz1Rr.pgp Description: PGP signature
Processing of pymongo_4.7.3-1_source.changes
pymongo_4.7.3-1_source.changes uploaded successfully to localhost along with the files: pymongo_4.7.3-1.dsc pymongo_4.7.3.orig.tar.gz pymongo_4.7.3-1.debian.tar.xz pymongo_4.7.3-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed: Re: Bug#1072780: src:transaction: fails to migrate to testing for too long: uploader built arch:all binary
Processing control commands:
> fixed -1 transaction/4.0-2
Bug #1072780 {Done: Paul Gevers } [src:transaction]
src:transaction: fails to migrate to testing for too long: uploader built
arch:all binary
Marked as fixed in versions transaction/4.0-2.
--
1072780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1072780: src:transaction: fails to migrate to testing for too long: uploader built arch:all binary
Control: fixed -1 transaction/4.0-2 On Fri, Jun 07, 2024 at 09:39:20PM +0200, Paul Gevers wrote: > Your package is only blocked because the arch:all binary package(s) aren't > built on a buildd. Unfortunately the Debian infrastructure doesn't allow > arch:all packages to be properly binNMU'ed. Hence, I will shortly do a > no-changes source-only upload to DELAYED/15, closing this bug. Please let me > know if I should delay or cancel that upload. This was fixed by transaction 4.0-2, and it looks like either you cancelled your upload or it was automatically dropped from the DELAYED queue. transaction (4.0-2) unstable; urgency=medium * QA upload * Source-only reupload -- Bastian Germann Wed, 12 Jun 2024 20:49:57 + Thanks, -- Colin Watson (he/him) [cjwat...@debian.org]
Processing of sendmail_8.15.2-22+deb11u1_source.changes
sendmail_8.15.2-22+deb11u1_source.changes uploaded successfully to localhost along with the files: sendmail_8.15.2-22+deb11u1.dsc sendmail_8.15.2.orig.tar.gz sendmail_8.15.2-22+deb11u1.debian.tar.xz sendmail_8.15.2-22+deb11u1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
sendmail_8.15.2-22+deb11u1_source.changes ACCEPTED into oldstable-proposed-updates->oldstable-new
Thank you for your contribution to Debian. Mapping bullseye to oldstable. Mapping oldstable to oldstable-proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 13 May 2024 18:44:56 + Source: sendmail Architecture: source Version: 8.15.2-22+deb11u1 Distribution: bullseye Urgency: medium Maintainer: Debian QA Group Changed-By: Bastien Roucariès Closes: 1059386 1070190 Changes: sendmail (8.15.2-22+deb11u1) bullseye; urgency=medium . * QA-upload * Fix CVE-2023-51765 (Closes: #1059386): sendmail allowed SMTP smuggling in certain configurations. Remote attackers can use a published exploitation technique to inject e-mail messages with a spoofed MAIL FROM address, allowing bypass of an SPF protection mechanism. This occurs because sendmail supports . but some other popular e-mail servers do not. This is resolved with 'o' in srv_features. * Enable _FFR_REJECT_NUL_BYTE for rejecting mail that include NUL byte * By default enable rejecting mail that include NUL byte. set confREJECT_NUL to 'true' by default . User could disable by setting confREJECT_NUL to false. (Closes: #1070190). Close a variant of CVE-2023-51765 aka SMTP smuggling. Checksums-Sha1: e8387dc8f69767f775bf200bca982c84b0e3b35b 2583 sendmail_8.15.2-22+deb11u1.dsc 5801d4b06f4e38ef228a5954a44d17636eaa5a16 2207417 sendmail_8.15.2.orig.tar.gz c92f537870c0d7999fba9514d70dc72b1b15b5a4 237992 sendmail_8.15.2-22+deb11u1.debian.tar.xz 91544b74daf90cb88fd5be9e41d57dcfccb4e0be 10852 sendmail_8.15.2-22+deb11u1_amd64.buildinfo Checksums-Sha256: 01209292838448434150f88db19e6b99149cbedf152eb1730c586c01247eb689 2583 sendmail_8.15.2-22+deb11u1.dsc 24f94b5fd76705f15897a78932a5f2439a32b1a2fdc35769bb1a5f5d9b4db439 2207417 sendmail_8.15.2.orig.tar.gz 4a41780cc5257cd2544468b319ab8485f19db0a128516984b539df8b6191c168 237992 sendmail_8.15.2-22+deb11u1.debian.tar.xz fab45feef620621f9568c00a2704b73d8ef3618991c766151e9060f461bdb50e 10852 sendmail_8.15.2-22+deb11u1_amd64.buildinfo Files: bd1354eb43821c1ae25145cac1ad8576 2583 mail optional sendmail_8.15.2-22+deb11u1.dsc a824fa7dea4d3341efb6462ccd816f00 2207417 mail optional sendmail_8.15.2.orig.tar.gz 063725ac14b612541d3894f277cba34e 237992 mail optional sendmail_8.15.2-22+deb11u1.debian.tar.xz ece20853faa7b86f0068b921fc92b5cc 10852 mail optional sendmail_8.15.2-22+deb11u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmZuBQIRHHJvdWNhQGRl Ymlhbi5vcmcACgkQADoaLapBCF9LGg//RTfP04a0TRSgIgn8gcp5Q3hmqcVBMSBX SaqS0o9NHkJR0R5c/Hwldl/yXqrl/NgFneWXZSlflePU1oGS7oCUQi+jlsHRQIU6 ovNJEj3LZQvMxQtihJVnAN6sABv2jEWRquvmbk0Xb2UO1B3kdpP3pmsrgnlBhV1p odcDhbN0LVkUGoHiNhwwUxNkEREhAuVYHEaSzU6L0y2hHsfmzSZn+XP+p9zrPyot SiMuWwtACJEZwniSJ7zn+XKSUR8oQ4usIXTPxVD7YZV8sCRB6+V/QROHkRwTXFCk 6ecqhP2VXAK5hUU4Bu7w2Jcij4N2vRoVvoeP6w8UbSObziHKoDeuyyshQM3Vp3hL Y7+VAB0HGFs8fIAd6qyckoafJw1HBrBrBAUO6/xcfQcfh8rcaNcJyhOnOcZxBQEe ofpaprutBGnlbSijlH1VAkPEFlmSYEvRHsGgDaoCs4rWKALCoVrvQM+SeTaF+vii SpkAdNDnyWcVz5IMIuAfVMRFA2REOdcuxbdfR0vvpeH2spCpIlnzEOK/tca3BsGN F2nk8kPb4QhJLd/TH2AhAX5ot84zZFC5SXwD/54zF5IPrHarCKrgOqB1gcKriZQm aqNIC3iMwqp9t2/qyVyMbG+X0qkP1keNCwv4G6oHL3gxdfX2SueOUe96DRa+CK39 OfxYtVPc7uE= =yh31 -END PGP SIGNATURE- pgpFyWCn_xaHc.pgp Description: PGP signature
Processing of qpsmtpd_0.94-7_source.changes
qpsmtpd_0.94-7_source.changes uploaded successfully to localhost along with the files: qpsmtpd_0.94-7.dsc qpsmtpd_0.94-7.debian.tar.xz qpsmtpd_0.94-7_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
qpsmtpd_0.94-7_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Jun 2024 19:35:59 +0200 Source: qpsmtpd Architecture: source Version: 0.94-7 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Changes: qpsmtpd (0.94-7) unstable; urgency=medium . * QA upload. . * Added d/gbp.conf to describe branch layout. * Updated vcs in d/control to Salsa. * Updated d/gbp.conf to enforce the use of pristine-tar. * Updated Standards-Version from 3.9.6 to 4.7.0. * Use wrap-and-sort -at for debian control files. * Trim trailing whitespace. * Set Homepage field in Source rather than Binary package. * Bump debhelper from deprecated 9 to 13. * Set debhelper-compat version in Build-Depends. * Replace obsolete lsb-base build dependency with sysvinit-utils (>= 3.05-4~). * Updated d/watch to check github project for new versions. Checksums-Sha1: 1699886223532bd184d3a2ae58bf765d66d0b2d6 1813 qpsmtpd_0.94-7.dsc 59a8574144aa7bd38ab66ad538a2b156b908ceba 51384 qpsmtpd_0.94-7.debian.tar.xz 339edd3b2ee4fac078083c4c91bbb492a334c96f 6353 qpsmtpd_0.94-7_source.buildinfo Checksums-Sha256: dadf094e44bcc75c53094c6598d455acad8fcf727cdfcebb819932e06ad4ef75 1813 qpsmtpd_0.94-7.dsc 32c009120787ae73b6e00ac3bc7a40574aeb8d023400ff203a7f04925d90b271 51384 qpsmtpd_0.94-7.debian.tar.xz cde2f47590b0735a3923c6a22a9c876b53a9755180dbcc083eb5f7c21e1bfbc5 6353 qpsmtpd_0.94-7_source.buildinfo Files: 2bfe0641f8cd4c300db16e81d2879148 1813 mail optional qpsmtpd_0.94-7.dsc 4c6f8a8ebd13b2766eb54ad3a931a928 51384 mail optional qpsmtpd_0.94-7.debian.tar.xz 32dc13338c1338d23cd4895d722b2e72 6353 mail optional qpsmtpd_0.94-7_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmZt0W4ACgkQgSgKoIe6 +w6wqhAAvmb7eWEFgI6TVQJ1gmtbHrRI70AoWetz+9tiUobFMeH40T6vL9gP8tVb RnFrgvAdfnkwNR7HtbAZ6ECHMOFb1t96UBwzNA5nNnTQr4JME+tHdyfgXxBLdAWO aJuvDvzKwkxahKunwQI5S8EsVeDDLzWu02yOVC4PAalkC2v6lB5HwpqeKDJJVY2t T4iLG48+JMiUaYaZqZn45S5qa3lXzOTaFSz9ryZp12o2u7qcpit2CqYPFULFm/cz wnqpfLrbmTKjZp61HYgmRTjOunM6/L1MOaFZuUl78xxvWu4WNOAKn7uoloyygifw XbnREKRrWx3VB6Fu/3hXc2jqXc5mvvRrEPQ/mIEBBO3eORzML4EAwafyC7g2IRAr 8MRc4lTaXAmnRZ33PtW+HwoBso+Wyh9QEVmNtTYvqJyyHDtWBTT89tNrEI6I+R5F 7FMQipKfYkTwYzG4BuyVHghkLISZYxZJkqb2+EFYN5Yy9ExQp57reNin7BFAxAYd h7kFXxUALq1GeU9BQx79uHnN5G0Ky8Ao2EPkqqe/3OWQ2qaYIbJaYOZhg6kq9o+k QgsT7F74udv8L5OWINpdNYxidEWjr6+f4919KZPwMqkdtN2Bt3oLjAKkfWmc3Xiu zHRHLDasrG/0Kpb/Y/JeSIDs5jjpqGzokXo/2guMJJGWNiVx4Ds= =6lja -END PGP SIGNATURE- pgpccGnTMfyKe.pgp Description: PGP signature
Bug#1073277: RM: ramond -- RoQA; unmaintained, dead upstream, unused
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: ram...@packages.debian.org Control: affects -1 + src:ramond User: ftp.debian@packages.debian.org Usertags: remove Please remove ramond. It's dead upstream, the last maintainer upload was in 2012 without a new adopter and it's basically non-existent in popcon. Cheers, Moritz
Processing of liblip_2.0.0-3_source.changes
liblip_2.0.0-3_source.changes uploaded successfully to localhost along with the files: liblip_2.0.0-3.dsc liblip_2.0.0-3.debian.tar.xz liblip_2.0.0-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
liblip_2.0.0-3_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Jun 2024 12:57:07 +0200 Source: liblip Architecture: source Version: 2.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Changes: liblip (2.0.0-3) unstable; urgency=medium . * QA upload. . * Added d/gbp.conf to describe branch layout. * Updated vcs in d/control to Salsa. * Updated d/gbp.conf to enforce the use of pristine-tar. * Updated Standards-Version from 3.7.2 to 4.7.0. * Use wrap-and-sort -at for debian control files * debian/control: Remove empty control field Conflicts in package liblip2t64. * Remove field Priority on binary packages liblip-dev, liblip2t64 that duplicates source. Checksums-Sha1: c973bc287a3d4aa1011bc179d8b0ef9f6c4bf644 1911 liblip_2.0.0-3.dsc 0a52fef03b865206827a5e361b2e204f64340182 4760 liblip_2.0.0-3.debian.tar.xz f2a0310c7f3debc6b56d83a3829f7c57ed3907e2 4749 liblip_2.0.0-3_source.buildinfo Checksums-Sha256: 73bef81824edd0133a2456bda660911587ca4ceb9abff08835c41832f02309e1 1911 liblip_2.0.0-3.dsc a62338f975e2c0110942327e1533917374217be033c4d28c7e7daf0e1552637c 4760 liblip_2.0.0-3.debian.tar.xz 21c3d78489f03a6ba464da39b0b011bea935af0e15e02237660eeb0b0c014df8 4749 liblip_2.0.0-3_source.buildinfo Files: c879ec0effdce3c5f2b76c099f56075f 1911 math optional liblip_2.0.0-3.dsc dd641e698583500bac326127e7c2e300 4760 math optional liblip_2.0.0-3.debian.tar.xz 605e81c44bb5b4d04a76e3d6b650c37d 4749 math optional liblip_2.0.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmZtc+IACgkQgSgKoIe6 +w7xaQ//YXBuQVgvMSUlUmY88USffd/zfIxHbJkColc4kheUL1Qw1s70VFCvOsnw NSnuwrNghEmkMlMrSvrHSLbfVhNSpwy99+b28PWmzNnoveC2kQij3mR10FCl0Qh0 X1/sH2/gGZBWfKYSixTkU15+k/eEbtS8qFKtPE+jEgXCozNNrJcZPN5V8kUnZFpZ iQcugbWz5JG6I2c4whBzKOUCWg4eOd3eXUkXSGl8XGJf0z+Da49ecibzcemx8EzB LcWcG94vg8sHJoJAMNK/PKhiB9GFcq3pDW5GiYmhHXR1nXVxP9xFQaWJjvD+Zyjv PmIcA1PVD2Cxzj/UwQpXjxZlarvcSrxIZQHnXu6T+dU7C20kzwi5bROosy9eZEnu ySuXo7RuX3sYGDcs3YC9lSM8leDlMTPXqtFDZTQYTiUeSKMT4iwsSRcF+aE8cyQU +V8E7qwylHqxo5Ykrt8pG6s7pcV7v2ofyagjH0W2EqOKSFewSmFoLXHtMwgazwQs J7BJ/WZe/aOq0PZlaN3hFYYTiLQce9PejUCviwePIdOaDwMzUcF52IXxUhim85AV h75NsACIUn3K5NowvnJ3yNypuftj6IrZtfHsTJ3G4RB2YBTxwqdJaG8abDRXeoRB CE1FmQDokW+7j1ZEoVZCDdTpq4LCPJQG0Ql8f9pCWK3BcWWPy0g= =fF3K -END PGP SIGNATURE- pgp3UnBod3J0A.pgp Description: PGP signature
Processed: block 1071970 with 999956 999960 999964 999968 999975 999984 1000014 1000065 1000093 1000100 1050187 999924 999930 1000053 1000067 1000076 1000087 1000129 1050182 1071681 1071686 999919 999
Processing commands for cont...@bugs.debian.org: > block 1071970 with 56 60 64 68 75 84 114 165 > 193 1000100 1050187 24 30 153 167 176 187 1000129 > 1050182 1071681 1071686 19 38 65 104 147 158 161 > 168 1070288 1073114 Bug #1071970 [libpcre3] pcre3 should not be part of trixie 1071970 was not blocked by any bugs. 1071970 was blocking: 1063571 Added blocking bug(s) of 1071970: 158, 176, 65, 24, 154, 114, 187, 19, 1070288, 193, 38, 68, 1071681, 167, 1000100, 168, 56, 84, 64, 165, 1050187, 147, 153, 1000129, 30, 1073114, 161, 39, 1071686, 104, 75, 1050182, and 60 > thanks Stopping processing here. Please contact me if you need assistance. -- 1071970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#576520: cdbackup: CRC checks fail on DVD images
Control: tags -1 + patch
[Phil Reynolds 2010-04-05]
> When writing virtual images for later burning to DVDs, if the -C switch
> to cdbackup is not used, the tracks in the images cannot be restored
> using cdrestore as the CRC check fails. This applies whether the images
> are on DVD or have been kept on a hard disc.
I wonder, could this be caused by a memory overflow in the CRC
calculating code? If so, I propose this patch to fix it.
Description: Make sure setting and reading CRC do not work past buffer size.
The code used to store 8 bytes in a 4 byte space, and read 8 bytes from a 4
byte space on 64 bit platforms. Rewrite to use int32_t to ensure only 4
bytes are used.
Author: Petter Reinholdtsen
Bug-Debian: https://bugs.debian.org/576520
Forwarded: no
Last-Update: 2024-06-15
---
--- cdbackup-0.7.1.orig/cdbackup.c
+++ cdbackup-0.7.1/cdbackup.c
@@ -29,6 +29,7 @@ SUCH DAMAGE.
#include
#include
#include
+#include
#include
#include
#include
@@ -392,8 +393,8 @@ int backup(void)
}
}
if(crc) {
- int l=crc32(buffer,bytes+DBSIZE);
- *((unsigned long *)(&buffer[CD_FRAMESIZE-4]))=l;
+ int32_t l=crc32(buffer,bytes+DBSIZE);
+ *((int32_t *)(&buffer[CD_FRAMESIZE-sizeof(l)]))=l;
}
Vwrite(buffer); grandTotal+=CD_FRAMESIZE;
} while(db->status==0);
--- cdbackup-0.7.1.orig/cdrestore.c
+++ cdbackup-0.7.1/cdrestore.c
@@ -28,6 +28,7 @@ SUCH DAMAGE.
#include
#include
+#include
#include
#include
#include
@@ -203,8 +204,8 @@ int restore(int disktrack)
}
if(db->flags&F_CRC) {
- int l=crc32(buffer,size+DBSIZE);
- if(*((unsigned long *)(&buffer[CD_FRAMESIZE-4]))!=l) {
+ int32_t l=crc32(buffer,size+DBSIZE);
+ if(*((int32_t *)(&buffer[CD_FRAMESIZE-sizeof(l)]))!=l) {
if(verbose) fprintf(stderr,"%s: bad CRC checksum at
%lld\n",prg_name,totalRead);
serror("Bad checksum, block corrupted, restore failed");
}
The patch is commited to the git repo on
https://salsa.debian.org/debian/cdbackup >, but not uploaded as I could
like to know if it solve this bug first. Are you able to test it?
--
Happy hacking
Petter Reinholdtsen
Processed: Re: cdbackup: CRC checks fail on DVD images
Processing control commands: > tags -1 + patch Bug #576520 [cdbackup] cdbackup: CRC checks fail on DVD images Added tag(s) patch. -- 576520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of cdbackup_0.7.1-3_source.changes
cdbackup_0.7.1-3_source.changes uploaded successfully to localhost along with the files: cdbackup_0.7.1-3.dsc cdbackup_0.7.1-3.debian.tar.xz cdbackup_0.7.1-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
cdbackup_0.7.1-3_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Jun 2024 09:31:52 +0200 Source: cdbackup Architecture: source Version: 0.7.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Changes: cdbackup (0.7.1-3) unstable; urgency=medium . * QA upload. . * Added d/gbp.conf to describe branch layout. * Updated vcs in d/control to Salsa. * Updated d/gbp.conf to enforce the use of pristine-tar. * Updated Standards-Version from 3.9.8 to 4.7.0. * Use wrap-and-sort -at for debian control files * Trim trailing whitespace. * Use correct machine-readable copyright file URI. * Bump debhelper from deprecated 9 to 13. * Set debhelper-compat version in Build-Depends. * Change priority extra to priority optional. * Adjusted d/rules to build with CPPFLAGS and LDFLAGS for hardening. * Flagged in d/control that build do not need root to work. Checksums-Sha1: 48993dd768b797c2bab2b388874da57ac653a0bc 1813 cdbackup_0.7.1-3.dsc b7ad3d0724dd0ac43769df3cb45e74dd6d9b58a0 5672 cdbackup_0.7.1-3.debian.tar.xz 3a17f027109b500e304067129b90901e7fc89e92 6361 cdbackup_0.7.1-3_source.buildinfo Checksums-Sha256: f75fd1466bc8cc8fd1cd19fd51e74d3422d5b690c5dab32f3a0537471881e4f6 1813 cdbackup_0.7.1-3.dsc ad67fc6ef13f04cb25df3a2ba07cd4550ffd98e74104872bd1169ac06b3d2f45 5672 cdbackup_0.7.1-3.debian.tar.xz 692c969a3cc91bdfc868cfb34b4b1f8ab974e9b8bed9448a732ea510576cfc4d 6361 cdbackup_0.7.1-3_source.buildinfo Files: 215b04ae877f3730ec61a89c0a297869 1813 admin optional cdbackup_0.7.1-3.dsc 6612af578dbf1226ac4edefffa0f0bda 5672 admin optional cdbackup_0.7.1-3.debian.tar.xz 31b5048abc14698eac46eeabff7fd629 6361 admin optional cdbackup_0.7.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmZtQ6EACgkQgSgKoIe6 +w7z+Q//c17tib7TnSKA+XYf+WsoC+TKF7ZiJh4n3JpfPO1QktHcu5An48lHLyFd tulj+ouSInEa+lGKRgLQFaLE3JwdtzQfniakQhs20MTGSSmE6wXvM40DXb2nCI5+ FbuwoPo5rby1c11wb0S6cR7ppmfdMya8qohnX5zcZax0y1+KXySkd6TdqoWkG3+u 1uPpfIa3WBrYvP3yqhMVRM49OuYsSfe7JYgquGRGFR9Ri+TwjEds+0/SEluCLgax nmSz+KwlfXDZ8S09L21DzgRQFkHCWwhmZdIJ9IiZovgQRCtpHrrSuB7ZedBr2Q95 Q1Hz63JerDoeMP+zhGNwTxqCwWXNQCuuZGk6KcqzurrpQmpfznPlktjs01RRT5IT hQFX/kQbwZGrq+if5EQOspKbp8Y4wXCkyWaEHreSx2i9ViiZg0K7B7+9mrCsI7/o COWgcYOK6cpOxToJjkExqLYUmHnidIr1P7UU8P66YOakvd1QN3KbC1ih/qC6Vtm7 Hlgl55g2LLEbWuol7BywvKU457P9NHT258GTbNQJqYERpePKOAs1R8AeWzDHaOp+ swphnNjO5Z17gnZMM4ZO6zNV57mye6dc1DKOb8dWMnuaGMOG5wr9L4mFgujq/KXw LmKEQNqqdzqdvctKzmyIXVc5JcPndOQiJYfPnYyX9TL0+njtz18= =dMuo -END PGP SIGNATURE- pgpSyK4NHtXHj.pgp Description: PGP signature
