Package: python3-socketio-client
Version: 0.6.5-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package emits a SyntaxWarning
during installation:
Setting up python3-socketio-client (0.6.5-1) ...
/usr/lib/python3/dist-p
pidgin-hotkeys 0.2.4-3 is marked for autoremoval from testing on 2023-07-28
It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
https://bugs.debian.org/1036113
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/bl
pidgin-blinklight 0.11.1-5 is marked for autoremoval from testing on 2023-07-28
It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
https://bugs.debian.org/1036113
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/
pidgin-skype 20140930+svn665+dfsg-2 is marked for autoremoval from testing on
2023-07-28
It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
https://bugs.debian.org/1036113
This mail is generated by:
https://salsa.debian.org/release-team/rele
bitlbee-facebook 1.2.2-2 is marked for autoremoval from testing on 2023-07-28
It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
https://bugs.debian.org/1036113
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/
pidgin-extprefs 0.7-3 is marked for autoremoval from testing on 2023-07-28
It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
https://bugs.debian.org/1036113
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blo
pidgin-audacious 2.0.0-8 is marked for autoremoval from testing on 2023-07-28
It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
https://bugs.debian.org/1036113
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/
pidgin-librvp 0.9.7cvs-4 is marked for autoremoval from testing on 2023-07-28
It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
https://bugs.debian.org/1036113
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/
pidgin-privacy-please 0.7.1-4 is marked for autoremoval from testing on
2023-07-28
It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
https://bugs.debian.org/1036113
This mail is generated by:
https://salsa.debian.org/release-team/release-to
pidgin-nateon 0.0.0.svn147-2 is marked for autoremoval from testing on
2023-07-28
It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
https://bugs.debian.org/1036113
This mail is generated by:
https://salsa.debian.org/release-team/release-too
purple-discord 0.9.2023.02.15.git.4a09188-2 is marked for autoremoval from
testing on 2023-07-28
It (build-)depends on packages with these RC bugs:
1036113: libpurple0: license conflict with libsasl2
https://bugs.debian.org/1036113
This mail is generated by:
https://salsa.debian.org/release-t
Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #1039127,
regarding apf-firewall: ships sysv-init script without systemd unit
to be marked as done.
This means that you claim that the
This problem is resolved in Debian 12 Bookworm, with the arrival of ghostscript
10.0.
The bug should probably be closed. Thank you all for all of your work,
Jim McCloskey
* Jim McCloskey (mccl...@ucsc.edu) wrote:
|> Package: ghostscript
|> Version: 9.53~dfsg-2+deb10u4
|> X-Debbugs-Cc:
Version: 9.7+rev1-7+rm
Dear submitter,
as the package apf-firewall 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/10402
Your message dated Mon, 03 Jul 2023 23:42:22 +
with message-id
and subject line Bug#1040238: Removed package(s) from unstable
has caused the Debian Bug report #1039216,
regarding gsm0710muxd: 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:
apf-firewall | 9.7+rev1-7 | source, all
--- Reason ---
RoQA; obsolete, unmaintained
--
Note that the package(s)
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #1039263,
regarding masqmail: ships sysv-init script without systemd unit
to be marked as done.
This means that you claim that the pro
Version: 1.13-3+rm
Dear submitter,
as the package gsm0710muxd 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/1040238
T
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gsm0710muxd | 1.13-3 | source
gsm0710muxd | 1.13-3+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel,
ppc64el, s390x
--- Reason ---
RoQA; obsole
Your message dated Mon, 03 Jul 2023 23:41:23 +
with message-id
and subject line Bug#1040236: Removed package(s) from unstable
has caused the Debian Bug report #1039262,
regarding mason: ships sysv-init script without systemd unit
to be marked as done.
This means that you claim that the proble
Version: 0.3.4-2+rm
Dear submitter,
as the package masqmail 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/1040237
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
masqmail |0.3.4-2 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
--- Reason ---
RoQA; dead upstream, RC-buggy
-
Version: 1.0.0-13+rm
Dear submitter,
as the package mason 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/1040236
The v
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
mason | 1.0.0-13 | source, all
--- Reason ---
RoQA; dead upstream, alternatives exist
--
Note that the p
Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #851349,
regarding leftover crontab entry
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #841895,
regarding apf-firewall: Apf blocks mysql connection on 127.0.0.1
to be marked as done.
This means that you claim that the pro
Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #908655,
regarding apf-firewall: The rules activated by PKT_SANITY_STUFFED are
overzealous and block DSL customers
to be marked as don
Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #841895,
regarding apf-firewall: Apf blocks mysql connection on 127.0.0.1
to be marked as done.
This means that you claim that the pro
Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #633648,
regarding apf-firewall: The SET_REFRESH option is useless because of cron
ignores refresh.apf link
to be marked as done.
Thi
Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #703220,
regarding apf-firewall: RAB doesn't work because ipt_recent is now xt_recent.
to be marked as done.
This means that you claim
Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #703220,
regarding apf-firewall: RAB broken due to ipt_recent changing name to xt_recent
to be marked as done.
This means that you cla
Your message dated Mon, 03 Jul 2023 23:42:22 +
with message-id
and subject line Bug#1040238: Removed package(s) from unstable
has caused the Debian Bug report #955900,
regarding gsm0710muxd: Depends on deprecated dbus-glib
to be marked as done.
This means that you claim that the problem has b
Your message dated Mon, 03 Jul 2023 23:42:51 +
with message-id
and subject line Bug#1040239: Removed package(s) from unstable
has caused the Debian Bug report #519961,
regarding apf-firewall: package name is ... strange
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 03 Jul 2023 23:42:22 +
with message-id
and subject line Bug#1040238: Removed package(s) from unstable
has caused the Debian Bug report #558113,
regarding unix domain socket support
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #882316,
regarding masqmail fails to install on amd64 architecture
to be marked as done.
This means that you claim that the problem ha
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #986648,
regarding masqmail: new upstream version 0.3.5 available
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #678493,
regarding masqmail: prompting due to modified conffiles which were not modified
by the user
to be marked as done.
This means
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #691947,
regarding [masqmail] Error using rmail: Exit status 127
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #654643,
regarding masqmail: Silently discards mails when mbox exceeds 2 GiB
to be marked as done.
This means that you claim that the
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #673551,
regarding ifupdown: error during boot: grep: unrecognized option '--all'
to be marked as done.
This means that you claim that
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #427900,
regarding masqmail: SMTP server hangs when used to send when offline
to be marked as done.
This means that you claim that the
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #678361,
regarding stopped expanding aliases
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #245882,
regarding masqmail: spool files not completely removed upon delivery
to be marked as done.
This means that you claim that the
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #241796,
regarding mail with large amount of receipient addresses causes excessive
memory consumption
to be marked as done.
This
Your message dated Mon, 03 Jul 2023 23:41:23 +
with message-id
and subject line Bug#1040236: Removed package(s) from unstable
has caused the Debian Bug report #517837,
regarding Stopping mason does not flush nat table
to be marked as done.
This means that you claim that the problem has been d
Your message dated Mon, 03 Jul 2023 23:41:23 +
with message-id
and subject line Bug#1040236: Removed package(s) from unstable
has caused the Debian Bug report #178791,
regarding mason: Masquerading with iptables fails
to be marked as done.
This means that you claim that the problem has been d
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #216226,
regarding masqmail: big mails over slow links get sent multiple times
to be marked as done.
This means that you claim that th
Your message dated Mon, 03 Jul 2023 23:41:23 +
with message-id
and subject line Bug#1040236: Removed package(s) from unstable
has caused the Debian Bug report #169220,
regarding mason: Broken signal handling
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 03 Jul 2023 23:41:23 +
with message-id
and subject line Bug#1040236: Removed package(s) from unstable
has caused the Debian Bug report #1037225,
regarding mason: [INTL:tr] turkish translation of debconf messages
to be marked as done.
This means that you claim that the
control: tag -1 wontfix
As of version 4.10 (which I uploadeed to experimental today) the whole
extras/ subdirectory which contains gemplug is gone.
Cheers,
-Hilko
Processing control commands:
> tag -1 wontfix
Bug #829104 [sispmctl] sispmctl: Please package gemplug
Added tag(s) wontfix.
--
829104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: gthumb
Version: 3:3.12.2-3
Severity: serious
Tags: ftbfs trixie sid
https://buildd.debian.org/status/logs.php?pkg=gthumb&ver=3%3A3.12.2-3%2Bb2
...
FAILED: extensions/raw_files/libraw_files.so.p/main.c.o
cc -Iextensions/raw_files/libraw_files.so.p -Iextensions/raw_files
-I../extensions/r
Thank you for your contribution to Debian.
Mapping stable-security to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 02 Jul 2023 10:50:27 +0200
Source: ghostscript
Architecture: source
Version: 10.0.0~dfsg-11+deb12u1
Distribution: bookworm-sec
Processing control commands:
> fixed -1 4.10-1~exp1
Bug #804265 [sispmctl] sispmctl: Allow sispmctl to be run as non-priviledged
user
Marked as fixed in versions sispmctl/4.10-1~exp1.
--
804265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804265
Debian Bug Tracking System
Contact ow...@bu
control: fixed -1 4.10-1~exp1
Processing control commands:
> fixed -1 4.10-1~exp1
Bug #825330 [sispmctl] sispmctl: New upstream version is available
Marked as fixed in versions sispmctl/4.10-1~exp1.
--
825330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825330
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Processing control commands:
> fixed -1 4.1.0-1~exp1
Bug #825330 [sispmctl] sispmctl: New upstream version is available
There is no source info for the package 'sispmctl' at version '4.1.0-1~exp1'
with architecture ''
Unable to make a source version for version '4.1.0-1~exp1'
Marked as fixed in v
control: fixed -1 4.10-1~exp1
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 21 Jun 2023 18:48:23 -0300
Source: srecord
Architecture: source
Version: 1.64-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Aquila Mac
control: fixed -1 4.1.0-1~exp1
srecord_1.64-4_source.changes uploaded successfully to localhost
along with the files:
srecord_1.64-4.dsc
srecord_1.64-4.debian.tar.xz
srecord_1.64-4_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: gsm0710m...@packages.debian.org
Control: affects -1 + src:gsm0710muxd
Please remove gsm0710muxd. It's been orphaned since nine years and removal was
already suggested in the original O:
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: apf-firew...@packages.debian.org
Control: affects -1 + src:apf-firewall
Please remove apf-firewall. Removal was already hinted at in the original
orphan bug from 2016 and at this point
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: ma...@packages.debian.org
Control: affects -1 + src:mason
Please remove mason, it's orphaned without an adopter since 2018, upstream
is dead upstream (vanished off the internet) and it
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: masqm...@packages.debian.org
Control: affects -1 + src:masqmail
Please remove masqmail. It's dead upstream, orphaned without an adopter
since 2015 and RC-buggy (dropped from testing sin
Your message dated Mon, 3 Jul 2023 20:03:48 +0200
with message-id <20230703180348.gj7...@inutil.org>
and subject line Already fixed
has caused the Debian Bug report #1039326,
regarding powerman: ships sysv-init script without systemd unit
to be marked as done.
This means that you claim that the pr
Your message dated Mon, 3 Jul 2023 19:56:41 +0200
with message-id <20230703175641.gg7...@inutil.org>
and subject line Already fixed
has caused the Debian Bug report #1039330,
regarding proxsmtp: ships sysv-init script without systemd unit
to be marked as done.
This means that you claim that the pr
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 03 Jul 2023 12:38:02 +0200
Source: sispmctl
Architecture: source
Version: 4.10-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group
Changed-By:
sispmctl_4.10-1~exp1_source.changes uploaded successfully to localhost
along with the files:
sispmctl_4.10-1~exp1.dsc
sispmctl_4.10.orig.tar.gz
sispmctl_4.10-1~exp1.debian.tar.xz
sispmctl_4.10-1~exp1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debia
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 03 Jul 2023 08:56:32 +0200
Source: raptor2
Architecture: source
Version: 2.0.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: HÃ¥vard F
raptor2_2.0.16-2_source.changes uploaded successfully to localhost
along with the files:
raptor2_2.0.16-2.dsc
raptor2_2.0.16-2.debian.tar.xz
raptor2_2.0.16-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
71 matches
Mail list logo