Version: 0.71b-4+rm
Dear submitter,
as the package alltray 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/1035819
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
alltray |0.71b-4 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
--- Reason ---
RoQA; orphaned; depends on gtk2; low
Version: 2.3.2-3+rm
Dear submitter,
as the package bygfoot 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/1035818
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
bygfoot |2.3.2-3 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
bygfoot-data |2.3.2-3 | all
--- Reason ---
RoQA;
Version: 0.5-4+rm
Dear submitter,
as the package aylet 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/1035817
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
aylet | 0.5-4 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
aylet-gtk | 0.5-4 | amd64, arm64, armel, armhf, i386, mips64el, mipsel,
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gsetroot | 1.1-3 | source
gsetroot | 1.1-3+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel,
ppc64el, s390x
--- Reason ---
RoQA;
Version: 1.1-3+rm
Dear submitter,
as the package gsetroot 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/1035816
The
Version: 1.6-9+rm
Dear submitter,
as the package bbrun 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/1035815
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
bbrun | 1.6-9 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
--- Reason ---
RoQA; orphaned; depends on gtk2; low
Version: 0.7.1-3+rm
Dear submitter,
as the package darksnow 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/1035814
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
darksnow |0.7.1-3 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
--- Reason ---
RoQA; orphaned; depends on gtk2; low
Version: 0.1~beta10-6+rm
Dear submitter,
as the package gkrellm-gkrellmpc 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
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gkrellm-gkrellmpc | 0.1~beta10-6 | source
gkrellm-gkrellmpc | 0.1~beta10-6+b1 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
--- Reason
Version: 0.7-8+rm
Dear submitter,
as the package wininfo 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/1035811
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
wininfo | 0.7-8 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
--- Reason ---
RoQA; orphaned; depends on gtk2; low
Version: 0.45-3+rm
Dear submitter,
as the package tabble 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/1035809
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
tabble | 0.45-3 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
--- Reason ---
RoQA; orphaned; depends on gtk2; low
Version: 1:0.6.1-5+rm
Dear submitter,
as the package transfermii 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
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
transfermii | 1:0.6.1-5 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
transfermii-gui | 1:0.6.1-5 | amd64, arm64, armel, armhf, i386, mips64el,
mipsel,
On 09/05/2023 16.55, Helmut Grohne wrote:
9base/bookworm no longer does, because it now uses dpkg-triggers to
Good to know that there is a better way nowadays ...
>From the attached log (scroll to the bottom...):
0m45.2s ERROR: FAIL: After purging files have been modified:
/etc/shells
Version: 2.1-2+rm
Dear submitter,
as the package screentest 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/1035806
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
screentest | 2.1-2 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
--- Reason ---
RoQA; orphaned; depends on gtk2; low
Version: 1.0.1-6+rm
Dear submitter,
as the package gkrellmitime 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/1035777
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gkrellmitime |1.0.1-6 | source
gkrellmitime | 1.0.1-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel,
ppc64el, s390x
--- Reason ---
RoQA;
Version: 0.3.6.2-3+rm
Dear submitter,
as the package ebview 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/1035776
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
ebview | 0.3.6.2-3 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
--- Reason ---
RoQA; orphaned; depends on gtk2; low
Version: 0.9.8-8+rm
Dear submitter,
as the package dbmix 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/1035774
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
dbmix |0.9.8-8 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
libdbaudiolib0 |0.9.8-8 | amd64, arm64, armel, armhf, i386, mips64el,
mipsel,
Version: 0.3-5+rm
Dear submitter,
as the package gerstensaft 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/1035770
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gerstensaft | 0.3-5 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
--- Reason ---
RoQA; orphaned; depends on gtk2; low
Version: 0.2q-6+rm
Dear submitter,
as the package bitstormlite 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/1035750
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
bitstormlite | 0.2q-6 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
--- Reason ---
RoQA; orphaned; depends on gtk2; low
Version: 0.2.3-3+rm
Dear submitter,
as the package pidgin-mpris 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/1035737
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
pidgin-mpris |0.2.3-3 | source
pidgin-mpris | 0.2.3-3+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel,
ppc64el, s390x
--- Reason ---
RoQA;
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #999840,
regarding alltray: Fails to start, opens and closes the window immediately
to be marked as done.
This means that you claim
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #967249,
regarding alltray: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #915500,
regarding alltray: Alltray not working correctly in fluxbox. show/hide command
don't work
to be marked as done.
This means
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #930477,
regarding alltray disrupts GUI for application program it docks
to be marked as done.
This means that you claim that the
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #829825,
regarding alltray: Uses deprecated gnome-common macros/variables
to be marked as done.
This means that you claim that the
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #677188,
regarding alltray: doesn't work : parse_theme: assertion failed
to be marked as done.
This means that you claim that the
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #663267,
regarding alltray: Introduce latest release (0.7.5.1dev) into unstable
to be marked as done.
This means that you claim that
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #613218,
regarding Alltray doesn't work with iceweasel in testing
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #571982,
regarding alltray: no tray icon; no way to get program in question back out of
tray
to be marked as done.
This means that
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #411459,
regarding alltray: Add multiple modifier support
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 15:06:48 +
with message-id
and subject line Bug#1035816: Removed package(s) from unstable
has caused the Debian Bug report #967467,
regarding gsetroot: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 15:08:56 +
with message-id
and subject line Bug#1035819: Removed package(s) from unstable
has caused the Debian Bug report #553314,
regarding alltray: "Show/Hide" function and close button don't work
to be marked as done.
This means that you claim that the
Your message dated Tue, 09 May 2023 15:06:16 +
with message-id
and subject line Bug#1035815: Removed package(s) from unstable
has caused the Debian Bug report #967268,
regarding bbrun: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 09 May 2023 15:07:53 +
with message-id
and subject line Bug#1035817: Removed package(s) from unstable
has caused the Debian Bug report #967265,
regarding aylet: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 09 May 2023 15:08:22 +
with message-id
and subject line Bug#1035818: Removed package(s) from unstable
has caused the Debian Bug report #964571,
regarding Languages are installed in a directory which is not expected by
"bygfoot"
to be marked as done.
This means that
Your message dated Tue, 09 May 2023 15:08:22 +
with message-id
and subject line Bug#1035818: Removed package(s) from unstable
has caused the Debian Bug report #967276,
regarding bygfoot: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 15:07:53 +
with message-id
and subject line Bug#1035817: Removed package(s) from unstable
has caused the Debian Bug report #930903,
regarding aylet FTCBFS: hard codes the build architecture pkg-config
to be marked as done.
This means that you claim that
Your message dated Tue, 09 May 2023 15:07:53 +
with message-id
and subject line Bug#1035817: Removed package(s) from unstable
has caused the Debian Bug report #672808,
regarding aylet: couldn't open sound device.
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 09 May 2023 15:07:53 +
with message-id
and subject line Bug#1035817: Removed package(s) from unstable
has caused the Debian Bug report #510051,
regarding Control keys do not work when aylet is started via xargs
to be marked as done.
This means that you claim that the
Your message dated Tue, 09 May 2023 15:07:53 +
with message-id
and subject line Bug#1035817: Removed package(s) from unstable
has caused the Debian Bug report #477359,
regarding aylet performs Thanatos.ay quite strangely
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 09 May 2023 15:04:47 +
with message-id
and subject line Bug#1035814: Removed package(s) from unstable
has caused the Debian Bug report #967300,
regarding darksnow: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 15:04:10 +
with message-id
and subject line Bug#1035812: Removed package(s) from unstable
has caused the Debian Bug report #967407,
regarding gkrellm-gkrellmpc: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 09 May 2023 15:03:39 +
with message-id
and subject line Bug#1035811: Removed package(s) from unstable
has caused the Debian Bug report #967803,
regarding wininfo: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 15:02:49 +
with message-id
and subject line Bug#1035809: Removed package(s) from unstable
has caused the Debian Bug report #967766,
regarding tabble: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 15:02:21 +
with message-id
and subject line Bug#1035807: Removed package(s) from unstable
has caused the Debian Bug report #967781,
regarding transfermii: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 15:02:49 +
with message-id
and subject line Bug#1035809: Removed package(s) from unstable
has caused the Debian Bug report #969740,
regarding tabble FTCBFS: broken embedded copy of AM_PATH_GTK_2_0
to be marked as done.
This means that you claim that the
Your message dated Tue, 09 May 2023 15:00:09 +
with message-id
and subject line Bug#1035776: Removed package(s) from unstable
has caused the Debian Bug report #967325,
regarding ebview: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 15:01:54 +
with message-id
and subject line Bug#1035806: Removed package(s) from unstable
has caused the Debian Bug report #967738,
regarding screentest: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 15:00:50 +
with message-id
and subject line Bug#1035777: Removed package(s) from unstable
has caused the Debian Bug report #967418,
regarding gkrellmitime: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 09 May 2023 15:01:54 +
with message-id
and subject line Bug#1035806: Removed package(s) from unstable
has caused the Debian Bug report #711217,
regarding doesn't render properly on startup
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 09 May 2023 15:01:54 +
with message-id
and subject line Bug#1035806: Removed package(s) from unstable
has caused the Debian Bug report #711218,
regarding add a IT8 target test
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 09 May 2023 15:00:09 +
with message-id
and subject line Bug#1035776: Removed package(s) from unstable
has caused the Debian Bug report #941192,
regarding ebview FTCBFS: debian/rules uses the build architecture compiler
to be marked as done.
This means that you claim
Your message dated Tue, 09 May 2023 15:00:09 +
with message-id
and subject line Bug#1035776: Removed package(s) from unstable
has caused the Debian Bug report #552169,
regarding ebview: Doesn't recognize QT4/KDE4 selection
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 09 May 2023 15:00:09 +
with message-id
and subject line Bug#1035776: Removed package(s) from unstable
has caused the Debian Bug report #542485,
regarding Remove deprecated "Application" in desktop file
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 09 May 2023 15:00:50 +
with message-id
and subject line Bug#1035777: Removed package(s) from unstable
has caused the Debian Bug report #1031777,
regarding gkrellmitime FTCBFS: uses the build architecture pkg-config
to be marked as done.
This means that you claim that
Your message dated Tue, 09 May 2023 14:58:36 +
with message-id
and subject line Bug#1035770: Removed package(s) from unstable
has caused the Debian Bug report #990273,
regarding gerstensaft FTCBFS: builds for the build architecture
to be marked as done.
This means that you claim that the
Your message dated Tue, 09 May 2023 14:59:09 +
with message-id
and subject line Bug#1035774: Removed package(s) from unstable
has caused the Debian Bug report #998988,
regarding dbmix: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that
Your message dated Tue, 09 May 2023 14:59:09 +
with message-id
and subject line Bug#1035774: Removed package(s) from unstable
has caused the Debian Bug report #973979,
regarding dbmix FTCBFS: confuses build and host architecture
to be marked as done.
This means that you claim that the
Your message dated Tue, 09 May 2023 14:58:36 +
with message-id
and subject line Bug#1035770: Removed package(s) from unstable
has caused the Debian Bug report #967385,
regarding gerstensaft: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 14:59:09 +
with message-id
and subject line Bug#1035774: Removed package(s) from unstable
has caused the Debian Bug report #967302,
regarding dbmix: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 09 May 2023 14:58:36 +
with message-id
and subject line Bug#1035770: Removed package(s) from unstable
has caused the Debian Bug report #436972,
regarding gerstensaft: not handling nostrip build option (policy 10.1)
to be marked as done.
This means that you claim that
Your message dated Tue, 09 May 2023 14:59:09 +
with message-id
and subject line Bug#1035774: Removed package(s) from unstable
has caused the Debian Bug report #965490,
regarding dbmix: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim
Your message dated Tue, 09 May 2023 14:58:36 +
with message-id
and subject line Bug#1035770: Removed package(s) from unstable
has caused the Debian Bug report #535574,
regarding beer is not properly non-utf-8-clean
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 May 2023 14:59:09 +
with message-id
and subject line Bug#1035774: Removed package(s) from unstable
has caused the Debian Bug report #299351,
regarding dbmix: Icon please
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 09 May 2023 14:58:36 +
with message-id
and subject line Bug#1035770: Removed package(s) from unstable
has caused the Debian Bug report #1023957,
regarding gerstensaft: reproducible-builds: buildid differences in /usr/bin/beer
to be marked as done.
This means that you
Your message dated Tue, 09 May 2023 14:55:55 +
with message-id
and subject line Bug#1035737: Removed package(s) from unstable
has caused the Debian Bug report #967700,
regarding pidgin-mpris: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 09 May 2023 14:55:55 +
with message-id
and subject line Bug#1035737: Removed package(s) from unstable
has caused the Debian Bug report #955936,
regarding pidgin-mpris: Depends on deprecated dbus-glib
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 09 May 2023 14:56:22 +
with message-id
and subject line Bug#1035750: Removed package(s) from unstable
has caused the Debian Bug report #967274,
regarding bitstormlite: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> forcemerge 1033167 -1
Bug #1033167 [usrmerge] usrmerge: messes with /etc/shells
Unable to merge bugs because:
package of #1035820 is '9base' not 'usrmerge'
Failed to forcibly merge 1033167: Did not alter merged bugs.
> affects 1033167 + 9base
Failed to mark 1033167
Control: forcemerge 1033167 -1
Control: affects 1033167 + 9base
Hi Andreas,
On Tue, May 09, 2023 at 04:39:21PM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package leaves modifications
> in /etc/shells after upgrading from bullseye to bookworm and purging the
>
Package: 9base
Version: 1:6-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package leaves modifications
in /etc/shells after upgrading from bullseye to bookworm and purging the
package.
9base/bullseye called
Hello.
On 08/05/23 11:07 PM, Daniel Spiljar wrote:
[..]
> Hello Abhijith,
>
> I knew pcre was obsolete, but wasn't aware of that not even bugfixes
> are made.
>
> Thank you for the heads-up! I added this to the TODO list, and will
> inform you as soon as I'm done with porting.
Wonderful.
87 matches
Mail list logo
