Your message dated Wed, 11 Dec 2024 22:52:51 +
with message-id
and subject line Bug#1087580: fixed in xmms2 0.8+dfsg-28
has caused the Debian Bug report #1087580,
regarding Build-Depends on the obsolete cython3-legacy
to be marked as done.
This means that you claim that the problem has been d
xmms2_0.8+dfsg-28_source.changes uploaded successfully to localhost
along with the files:
xmms2_0.8+dfsg-28.dsc
xmms2_0.8+dfsg-28.debian.tar.xz
xmms2_0.8+dfsg-28_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Dec 2024 22:25:55 +
Source: xmms2
Architecture: source
Version: 0.8+dfsg-28
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Bastian
Version: 1.20180812.1-7+rm
Dear submitter,
as the package python-cliapp 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/
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
python-cliapp | 1.20180812.1-7 | source
python3-cliapp | 1.20180812.1-7 | all
--- Reason ---
RoQA; obsolete, unmaintained upstream
-
Version: 2.6.0+dfsg-9+rm
Dear submitter,
as the package gimp-gap 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/1088055
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gimp-gap | 2.6.0+dfsg-9 | source, amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, riscv64, s390x
--- Reason ---
RoQA; not compatible with gimp 3
---
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #676935,
regarding please implement a debug=True setting
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #950700,
regarding RFS: python-cliapp/1.20180812.1-4 [ITA] -- Python framework for Unix
command line programs
to be marked as done.
T
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #756405,
regarding obnam: '$obnam help ls' shows a traceback
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #681866,
regarding manpage error regarding -r option
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #655091,
regarding --dump-memory-profile should log at info level
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #677115,
regarding per-subcommand config file sections
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #1080900,
regarding Missing Build-Depends on python3-setuptools
to be marked as done.
This means that you claim that the problem has b
Your message dated Wed, 11 Dec 2024 18:25:53 +
with message-id
and subject line Bug#1088055: Removed package(s) from unstable
has caused the Debian Bug report #866224,
regarding Fwd: gimp-gap 2.6.0 is wrong for gimp 2.8.x
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 11 Dec 2024 18:25:53 +
with message-id
and subject line Bug#1088055: Removed package(s) from unstable
has caused the Debian Bug report #967397,
regarding gimp-gap: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Wed, 11 Dec 2024 18:25:53 +
with message-id
and subject line Bug#1088055: Removed package(s) from unstable
has caused the Debian Bug report #846323,
regarding mplayer extraction is broken
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Wed, 11 Dec 2024 18:25:53 +
with message-id
and subject line Bug#1088055: Removed package(s) from unstable
has caused the Debian Bug report #1088054,
regarding gimp-gap: Not compatible with gimp 3
to be marked as done.
This means that you claim that the problem has been dea
Do me a favor and think about this for one minute. What you are
doing right now is producing a result. That result is your reality.
Not something you picture in your imagination.
Question? Have you been experiencing the same results day after day
year after year? Have you settled and feel trapped i
19 matches
Mail list logo
