Bug#1000029: PCRE to PCRE2 migration

[Abhijith PA]

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. Thank you.


--abhijith

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Andreas Beckmann]

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 add-shell/remove-shell in its postinst/postrm.
9base/bookworm no longer does that, but it also does not clean up the
leftover entries from bullseye in its postinst.

>From the attached log (scroll to the bottom...):

0m45.2s ERROR: FAIL: After purging files have been modified:
  /etc/shellsnot owned


The following (untested) snippet for the postinst should perform the
neccessary cleanup:

if [ "$1" = "install" ] || [ "$1" = "upgrade" ]; then
if dpkg --compare-versions "$2" lt-nl "1:6-14~" ; then
remove-shell /bin/rc
remove-shell /usr/lib/plan9/bin/rc
fi
fi


cheers,

Andreas


9base_1:6-13.log.gz
Description: application/gzip

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Helmut Grohne]

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/bullseye called add-shell/remove-shell in its postinst/postrm.
> 9base/bookworm no longer does that, but it also does not clean up the
> leftover entries from bullseye in its postinst.

9base/bookworm no longer does, because it now uses dpkg-triggers to
perform the cleanup. It actually does clean up its entries.

> >From the attached log (scroll to the bottom...):
> 
> 0m45.2s ERROR: FAIL: After purging files have been modified:
>   /etc/shells  not owned

You should look closer:

0m45.2s DEBUG: Modified(user, group, mode, size, target): /etc/shells 
expected(root, root, - 100644, 128, None) != found(root, root, - 100644, 140, 
None)

It's a 12 byte difference. That's not 9base's entries. What you see here
is "/usr/bin/sh\n". So this is a /usr-merge bug. We already know it.
Thus force-merging.

> The following (untested) snippet for the postinst should perform the
> neccessary cleanup:
> 
> if [ "$1" = "install" ] || [ "$1" = "upgrade" ]; then
> if dpkg --compare-versions "$2" lt-nl "1:6-14~" ; then
> remove-shell /bin/rc
> remove-shell /usr/lib/plan9/bin/rc
> fi
> fi

No. Please continue to use the declarative approach.

Helmut

Processed (with 2 errors): Re: Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Debian Bug Tracking System]

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 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/1033167 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/1033167 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1033167 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.


-- 
1033167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033167
1035820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#967274: marked as done (bitstormlite: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bitstormlite
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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

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#955936: marked as done (pidgin-mpris: Depends on deprecated dbus-glib)

[Debian Bug Tracking System]

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 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.)


-- 
955936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pidgin-mpris
Severity: normal
Tags: sid bullseye
Control: block 895291 by -1
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: dbus-glib-deprecation

dbus-glib is a deprecated D-Bus library with some significant design
flaws, and is essentially unmaintained. I would like to minimize its
use, and eventually remove it from Debian. There will not be a
version that fixes its design flaws, because that would be a major
compatibility break, and any user of dbus-glib who is willing to port
their application to a newer, incompatible version should instead be
porting their application to a better D-Bus implementation such as
GDBus.

For most purposes, the recommended replacement for dbus-glib is the
GDBus family of APIs in GLib, found in . This does not add
an additional dependency, because dbus-glib already depends on a
sufficiently new version of GLib. A porting guide is available in the
GLib documentation:
. Practical
examples of porting from dbus-glib to GDBus can be found in the git
history of most older GNOME applications.

Alternatives to GDBus, with different design emphasis and trade-offs,
include sd-bus (systemd's D-Bus implementation), QtDBus (Qt's D-Bus
API), and libdbus (the low-level reference D-Bus implementation).
Please contact the D-Bus mailing list 
if you are unsure which D-Bus implementation is most suitable for a
particular package.

Some libraries expose dbus-glib as part of their API/ABI, in which
case removing the deprecated dependency requires breaking API/ABI
(telepathy-glib is a good example). For these libraries, maintainers
should talk to the dependent library's upstream developers about
whether the dependent library should break API/ABI and switch to
GDBus, or whether the dependent library should itself be deprecated.

In a few cases, the package uses the reference D-Bus library libdbus
for all D-Bus-related APIs, and only uses dbus-glib as a way to
connect libdbus to the GLib main loop: if the only functions
referenced from dbus-glib are dbus_connection_setup_with_g_main() and
dbus_server_setup_with_g_main(), then you are in this situation. The
recommended replacement in this case is to bundle the dbus-gmain
branch from the dbus-glib git repository, for example as a `git
subtree` or `git submodule`. For example, dbus-python's GLib
integration now works like this. See
 for more details. 
--- End Message ---
--- Begin Message ---
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

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#967700: marked as done (pidgin-mpris: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pidgin-mpris
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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

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#1023957: marked as done (gerstensaft: reproducible-builds: buildid differences in /usr/bin/beer)

[Debian Bug Tracking System]

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 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.)


-- 
1023957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gerstensaft
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The buildid for /usr/bin/beer varies when built from a different path:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/gerstensaft.html

The attached patch to src/Makefile fixes this by adding
-ffile-prefix-map to CFLAGS.

According to my local tests, with this patch applied, gerstensaft should
build reproducibly on tests.reproducible-builds.org!

Thanks for maintaining gerstensaft!

live well,
  vagrant
 From 9d2ed6cb070220ced710c6453dfae9563082e9ef Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 13 Nov 2022 07:46:46 +
Subject: [PATCH] src/Makefile: Add -ffile-prefix-map to CFLAGS to avoid
 embedding the build path.

https://reproducible-builds.org/docs/build-path/
---
 src/Makefile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/Makefile b/src/Makefile
index d81003e..ce6cc41 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -23,6 +23,7 @@ CC = gcc
 
 CFLAGS=-g -Wall \
 	-DG_DISABLE_DEPRECATED \
+	-ffile-prefix-map=$(CURDIR)=.
 
 
 GTK_CFLAGS=$(shell pkg-config gtk+-2.0 --cflags)
-- 
2.38.1



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
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

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#299351: marked as done (dbmix: Icon please)

[Debian Bug Tracking System]

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 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.)


-- 
299351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dbmix
Version: 0.9.8-4
Severity: wishlist


I notice that your application lacks an icon. For the Debian package please 
could you create a 32x32 pixel XPM in /usr/share/pixmaps/dbmix.xpm and 
reference it from /usr/lib/menu/dbmix by adding this:

icon="/usr/share/pixmaps/dbmix.xpm"

For more information, please refer to the updated Debian Policy:
http://www.debian.org/doc/packaging-manuals/menu.html/ch3.html#s3.7
This will ensure that your nice icon shows up in most menus.

If you're not graphically inclined, I'm prepared to create a suitable icon and 
submit a menufile patch into the bargain. Please email me with your 
requirements if this is the case.

Thanks for taking the time to deal with this, and thanks for all the effort you 
have put in to maintaining great free software.

tim hall
AGNULA/DeMuDi menu monitor


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (101, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-multimedia-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to 
en_GB)

Versions of packages dbmix depends on:
ii  libc6   2.3.2.ds1-20.demudi1 GNU C Library: Shared libraries an
ii  libdbaudiolib0  0.9.8-4  Communicate to the DBMix audio sys
ii  libglib1.2  1.2.10-9 The GLib library of C routines
ii  libgtk1.2   1.2.10-17The GIMP Toolkit set of widgets fo
ii  xlibs   4.3.0.dfsg.1-10  X Keyboard Extension (XKB) configu

-- no debconf information

--- End Message ---
--- Begin Message ---
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 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#535574: marked as done (beer is not properly non-utf-8-clean)

[Debian Bug Tracking System]

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 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.)


-- 
535574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: gerstensaft
Version: 0.3-4
Severity: important
Tags: l10n

I do not know if the tagging is correct, so feel free to change it.

Short error description:
   ~> beer

   (beer:23763): Gtk-WARNING **: Invalid input string

   (beer:23763): Gtk-WARNING **: Invalid input string

   (beer:23763): Gtk-WARNING **: Invalid input string

   (beer:23763): Gtk-WARNING **: Invalid input string

   (beer:23763): Pango-WARNING **: Invalid UTF-8 string passed to 
pango_layout_set_text()
   Speicherzugriffsfehler

Long description and possible workaround:

I have the locales set to de_DE (without utf-8!). That is fine for the
console but if it is used to localize GTK+ graphical output that is
wrong behaviour as gtk+ strings have to be always encoded in utf-8!
(There exists proper handling in glib and gtk.)

The segmentation fault (Speicherzugriffsfehler in German) can be worked
around by starting with "env LC_ALL=de_DE.utf8 beer". However, I still
get errors for invalid UTF-8 strings from pango as the file system is
latin1. But the application will start at least.

Please convert the strings properly before passing them to pango or
gtk+.

- -- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (800, 'stable'), (700, 'oldstable'), (600, 'unstable'), (60, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.28.7
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to 
de_DE)
Shell: /bin/sh linked to /bin/dash

Versions of packages gerstensaft depends on:
ii  libatk1.0-0 1.22.0-1 The ATK accessibility toolkit
ii  libc6   2.7-18   GNU C Library: Shared libraries
ii  libcairo2   1.6.4-7  The Cairo 2D vector graphics libra
ii  libglib2.0-02.16.6-2 The GLib library of C routines
ii  libgtk2.0-0 2.12.12-1~lenny1 The GTK+ graphical user interface 
ii  libpango1.0-0   1.20.5-5 Layout and rendering of internatio
ii  sendfile2.1b.20080616-2  Simple Asynchronous File Transfer

gerstensaft recommends no packages.

gerstensaft suggests no packages.

- -- no debconf information

- -- 
Klaus Ethgenhttp://www.ethgen.de/
pub  2048R/D1A4EDE5 2000-02-26 Klaus Ethgen 
Fingerprint: D7 67 71 C4 99 A6 D4 FE  EA 40 30 57 3C 88 26 2B
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iQEVAwUBSk3kep+OKpjRpO3lAQo89QgAkqnk004W0mlIjcmi2UjMXHKXJ8M51Fa3
dmL3YDsL1JEQFhXLupf4UYOhEk9/nQIpLAvDT0CkSwXPNZXlx+xAkzFOVpdWeQBS
hjzlpAKYvuzWKKVzgXLOUhEHrDVly6STKHusFHUqNItyW2hZ2R82HYiajEOF+QUc
AIk3vImXv4SeryQknc2VbX37Hp10AMnJL7SbcK0863IACKUrTVh8dwRk3a2me8hr
YTpamBQ8v08csZ8hXnllnbR2XnYL6+O6LbV2hcB/ko2Z4Kh2aEUxFuRa9AbVmPPN
HJxbFYCQM9waVNZrMJUkg4IDt4a0sU2I8VU0sAQjrJ8nUGBIBziveg==
=vVT2
-END PGP SIGNATURE-


--- End Message ---
--- Begin Message ---
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

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#965490: marked as done (dbmix: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

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 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.)


-- 
965490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dbmix
Version: 0.9.8-6.3
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package dbmix uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
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 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#967302: marked as done (dbmix: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dbmix
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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 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#436972: marked as done (gerstensaft: not handling nostrip build option (policy 10.1))

[Debian Bug Tracking System]

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 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.)


-- 
436972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gerstensaft
Version: 0.3-2
Severity: wishlist
User: bui...@naquadah.org
Usertags: nostrip

Hello,

There was a problem while autobuilding your package with 
DEB_BUILD_OPTIONS=nostrip.
Final binaries are still stripped.

If you call dh_strip correctly in debian/rules, this may mean that upstream
is stripping anyway.
You should look for call to strip, ld -s or install -s which may strip binaries.


> Automatic build of gerstensaft_0.3-2 on octave for sid/i386 by rebuildd 0.2.1
> Build started at 2007-08-09 19:08:02.041588
> **
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Need to get 51.9kB of source archives.
> Get:1 http://ftp.fr.debian.org sid/main gerstensaft 0.3-2 (dsc) [571B]
> Get:2 http://ftp.fr.debian.org sid/main gerstensaft 0.3-2 (tar) [46.9kB]
> Get:3 http://ftp.fr.debian.org sid/main gerstensaft 0.3-2 (diff) [4420B]
> Fetched 51.9kB in 0s (232kB/s)
> Download complete and in download only mode
> W: /home/staff/jd/.pbuilderrc does not exist
> I: using fakeroot in build.
> Current time: Thu Aug  9 19:08:09 UTC 2007
> pbuilder-time-stamp: 1186686489
> Building the build Environment
>  -> extracting base tarball [/var/cache/pbuilder/sid.tgz]
>  -> creating local configuration
>  -> copying local configuration
>  -> mounting /proc filesystem
>  -> mounting /dev/pts filesystem
>  -> policy-rc.d already exists
> Obtaining the cached apt archive contents
> Installing the build-deps
>  -> Attempting to parse the build-deps 
>  -> Considering build-dep libgtk2.0-dev
>-> Trying libgtk2.0-dev
>  -> Considering build-dep gettext
>-> Trying gettext
>  -> Installing  libgtk2.0-dev gettext
> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following extra packages will be installed:
>   defoma file fontconfig fontconfig-config gettext-base libatk1.0-0
>   libatk1.0-dev libcairo2 libcairo2-dev libcupsys2 libdatrie0 libexpat1
>   libexpat1-dev libfontconfig1 libfontconfig1-dev libfreetype6
>   libfreetype6-dev libglib2.0-0 libglib2.0-dev libgtk2.0-0 libgtk2.0-common
>   libice-dev libice6 libjpeg62 libmagic1 libnewt0.52 libpango1.0-0
>   libpango1.0-common libpango1.0-dev libpng12-0 libpng12-dev libpopt0
>   libslang2 libsm-dev libsm6 libthai-data libthai0 libtiff4 libx11-6
>   libx11-data libx11-dev libxau-dev libxau6 libxcursor-dev libxcursor1
>   libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3
>   libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1
>   libxrandr-dev libxrandr2 libxrender-dev libxrender1 pkg-config ttf-dejavu
>   ucf whiptail x11-common x11proto-core-dev x11proto-fixes-dev
>   x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev
>   x11proto-xext-dev x11proto-xinerama-dev xtrans-dev zlib1g-dev
> Suggested packages:
>   defoma-doc psfontmgr x-ttcidfont-conf dfontmgr cvs gettext-doc libcairo2-doc
>   cupsys-common libglib2.0-doc libgtk2.0-doc ttf-kochi-gothic ttf-kochi-mincho
>   ttf-thryomanes ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp
>   ttf-arphic-gkai00mp ttf-arphic-bkai00mp libpango1.0-doc imagemagick
> Recommended packages:
>   libft-perl curl wget lynx libatk1.0-data libglib2.0-data hicolor-icon-theme
>   libgtk2.0-bin libfribidi0 libpng12 debconf-utils
> The following NEW packages will be installed:
>   defoma file fontconfig fontconfig-config gettext gettext-base libatk1.0-0
>   libatk1.0-dev libcairo2 libcairo2-dev libcupsys2 libdatrie0 libexpat1
>   libexpat1-dev libfontconfig1 libfontconfig1-dev libfreetype6
>   libfreetype6-dev libglib2.0-0 libglib2.0-dev libgtk2.0-0 libgtk2.0-common
>   libgtk2.0-dev libice-dev libice6 libjpeg62 libmagic1 libnewt0.52
>   libpango1.0-0 libpango1.0-common libpango1.0-dev libpng12-0 libpng12-dev
>   libpopt0 libslang2 libsm-dev libsm6 libthai-data libthai0 libtiff4 libx11-6
>   libx11-data libx11-dev libxau-dev libxau6 libxcursor-dev libxcursor1
>   libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3
>   libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1
>   libxr

Bug#967385: marked as done (gerstensaft: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gerstensaft
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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

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#973979: marked as done (dbmix FTCBFS: confuses build and host architecture)

[Debian Bug Tracking System]

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 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.)


-- 
973979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dbmix
Version: 0.9.8-7
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

dbmix fails to cross build from source, because it confuses the terms
build architecture and host architecture in a quite obvious way. Please
consider applying the attached patch.

Helmut
diff -u dbmix-0.9.8/debian/changelog dbmix-0.9.8/debian/changelog
--- dbmix-0.9.8/debian/changelog
+++ dbmix-0.9.8/debian/changelog
@@ -1,3 +1,9 @@
+dbmix (0.9.8-8) UNRELEASED; urgency=medium
+
+  * Fix FTCBFS: Fix build vs host confusion. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 07 Nov 2020 20:26:52 +0100
+
 dbmix (0.9.8-7) unstable; urgency=medium
 
   * QA upload.
diff -u dbmix-0.9.8/debian/rules dbmix-0.9.8/debian/rules
--- dbmix-0.9.8/debian/rules
+++ dbmix-0.9.8/debian/rules
@@ -13,7 +13,7 @@
 ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE))
   confflags += $(DEB_HOST_GNU_TYPE)
 else
-  confflags += --host $(DEB_BUILD_GNU_TYPE) --build $(DEB_HOST_GNU_TYPE)
+  confflags += --host $(DEB_HOST_GNU_TYPE) --build $(DEB_BUILD_GNU_TYPE)
 endif
   
 CFLAGS=-Wall -g
--- End Message ---
--- Begin Message ---
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 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#998988: marked as done (dbmix: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

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 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.)


-- 
998988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dbmix
Version: 0.9.8-8
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
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 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#990273: marked as done (gerstensaft FTCBFS: builds for the build architecture)

[Debian Bug Tracking System]

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 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.)


-- 
990273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gerstensaft
Version: 0.3-4.2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

gerstensaft fails to cross build from source, because it does not pass
cross tools to make. Pretty please, can you use debhelper? That would be
a lot less annoying to fix. Anyway, I've attached a patch that manually
passes the relevant cross tools. Beyond this, it also strips at make
install time with the build architecture strip, which happens to break
DEB_BUILD_OPTIONS=nostrip (#436972) as well as generation of -dbgsym
packages. The attached patch fixes all mentioned issues. Please consider
applying it.

Helmut
diff -u gerstensaft-0.3/debian/changelog gerstensaft-0.3/debian/changelog
--- gerstensaft-0.3/debian/changelog
+++ gerstensaft-0.3/debian/changelog
@@ -1,3 +1,12 @@
+gerstensaft (0.3-4.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Pass cross tools CC and PKG_CONFIG.
++ Pass a non-stripping install. (Closes: #436972)
+
+ -- Helmut Grohne   Thu, 24 Jun 2021 12:31:48 +0200
+
 gerstensaft (0.3-4.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u gerstensaft-0.3/debian/rules gerstensaft-0.3/debian/rules
--- gerstensaft-0.3/debian/rules
+++ gerstensaft-0.3/debian/rules
@@ -27,19 +27,22 @@
 installbin = install -g root -o root -m 755
 installdoc = install -g root -o root -m 644
 
+-include /usr/share/dpkg/buildtools.mk
+PKG_CONFIG ?= pkg-config
+
 ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
 CFLAGS = -g -O2 -Wall
 else
 CFLAGS = -O2 -Wall
 endif
 ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
-STRIP = strip
+STRIP ?= strip
 else
 STRIP = echo
 endif
 
 build:
-   $(MAKE) PIXMAP_WM_DIR=/usr/share/pixmaps prefix=/usr
+   $(MAKE) PIXMAP_WM_DIR=/usr/share/pixmaps prefix=/usr CC='$(CC)' 
PKG_CONFIG="$(PKG_CONFIG)"
touch stamp-build
 
 clean: debclean
@@ -69,7 +72,7 @@
$(installdoc) readme debian/tmp/usr/share/doc/$(package)/
gzip -9nf debian/tmp/usr/share/doc/$(package)/changelog.Debian
#
-   $(MAKE) PIXMAP_WM_DIR=`pwd`/debian/tmp/usr/share/pixmaps 
prefix=`pwd`/debian/tmp/usr install
+   $(MAKE) PIXMAP_WM_DIR=`pwd`/debian/tmp/usr/share/pixmaps 
prefix=`pwd`/debian/tmp/usr install='install --strip-program=true' install
gzip -9n debian/tmp/usr/share/man/man?/*
$(STRIP) debian/tmp/usr/bin/beer
#
diff -u gerstensaft-0.3/src/Makefile gerstensaft-0.3/src/Makefile
--- gerstensaft-0.3/src/Makefile
+++ gerstensaft-0.3/src/Makefile
@@ -25,8 +25,9 @@
-DG_DISABLE_DEPRECATED \
 
 
-GTK_CFLAGS=$(shell pkg-config gtk+-2.0 --cflags)
-GTK_LIBS=$(shell pkg-config gtk+-2.0 --libs)
+PKG_CONFIG ?= pkg-config
+GTK_CFLAGS=$(shell $(PKG_CONFIG) gtk+-2.0 --cflags)
+GTK_LIBS=$(shell $(PKG_CONFIG) gtk+-2.0 --libs)
 
 CFLAGS+=$(GTK_CFLAGS)
 LIBS+=$(GTK_LIBS)
--- End Message ---
--- Begin Message ---
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

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#1031777: marked as done (gkrellmitime FTCBFS: uses the build architecture pkg-config)

[Debian Bug Tracking System]

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 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.)


-- 
1031777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gkrellmitime
Version: 1.0.1-7
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

gkrellmitime fails to cross build from source, because the upstream
Makefile hard codes the build architecture pkg-config. I'm attaching a
patch for your convenience.

Helmut
--- gkrellmitime-1.0.1.orig/Makefile
+++ gkrellmitime-1.0.1/Makefile
@@ -6,7 +6,8 @@
 INCLUDEDIR ?= $(PREFIX)/include
 
 # Support for Debian policy
-CFLAGS += -I$(INCLUDEDIR) `pkg-config gtk+-2.0 --cflags`
+PKG_CONFIG ?= pkg-config
+CFLAGS += -I$(INCLUDEDIR) `$(PKG_CONFIG) gtk+-2.0 --cflags`
 INSTALL = install
 INSTALL_FILE= $(INSTALL) -p-o root -g root -m 644
 INSTALL_DIR = $(INSTALL) -p -d -o root -g root -m 755
@@ -17,7 +18,7 @@
 
 
 $(TARGET).so: $(TARGET).o
-	$(CC) $(LDFLAGS) -shared `pkg-config gtk+-2.0 --libs` $< -o $@
+	$(CC) $(LDFLAGS) -shared `$(PKG_CONFIG) gtk+-2.0 --libs` $< -o $@
 
 $(TARGET).o: $(TARGET).c
 	$(CC) $(CPPFLAGS) $(CFLAGS) -c $<
--- End Message ---
--- Begin Message ---
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

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#552169: marked as done (ebview: Doesn't recognize QT4/KDE4 selection)

[Debian Bug Tracking System]

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 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.)


-- 
552169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ebview
Version: 0.3.6.2-1
Severity: normal

Hello,

The search by selection doesn't work with QT4/KDE4 apps like konversation,
not even copying the selection with ctrl-c does anything.

Btw, is there an upstream repository or mailing list or something, or are the
0.3.6.x versions only in Debian? The listed homepage ebview.sf.net and the sf
project page look untouched since 0.3.6.

Best regards,
Christian Ohm


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-2-amd64 (SMP w/2 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 ebview depends on:
ii  libatk1.0-01.28.0-1  The ATK accessibility toolkit
ii  libc6  2.10.1-1  GNU C Library: Shared libraries
ii  libcairo2  1.8.8-2   The Cairo 2D vector graphics libra
ii  libeb134.4.1-1   C library for accessing electronic
ii  libfontconfig1 2.6.0-4   generic font configuration library
ii  libfreetype6   2.3.11-1  FreeType 2 font engine, shared lib
ii  libglib2.0-0   2.22.2-2  The GLib library of C routines
ii  libgtk2.0-02.18.3-1  The GTK+ graphical user interface 
ii  libpango1.0-0  1.26.0-1  Layout and rendering of internatio
ii  libx11-6   2:1.2.2-1 X11 client-side library
ii  zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime

ebview recommends no packages.

Versions of packages ebview suggests:
pn  edict-fpw  (no description available)

-- no debconf information

-- 
All progress is based upon a universal innate desire of every organism
to live beyond its income.
-- Samuel Butler, "Notebooks"


--- End Message ---
--- Begin Message ---
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

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#542485: marked as done (Remove deprecated "Application" in desktop file)

[Debian Bug Tracking System]

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 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.)


-- 
542485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ebview
Version: 0.3.6.2-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu karmic ubuntu-patch

Hello Maintainer,

*** /tmp/tmp_AoAZx
In Ubuntu, we've applied the attached patch to achieve the following:

  *debian/ebview.desktop
  - Removed value "Application" for key "Categories" in group
"Desktop Entry"(deprecated)

We thought you might be interested in doing the same. 


-- System Information:
Debian Release: squeeze/sid
  APT prefers karmic
  APT policy: (500, 'karmic'), (500, 'jaunty')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-5-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u ebview-0.3.6.2/debian/ebview.desktop ebview-0.3.6.2/debian/ebview.desktop
--- ebview-0.3.6.2/debian/ebview.desktop
+++ ebview-0.3.6.2/debian/ebview.desktop
@@ -10,3 +10,3 @@
 Type=Application
-Categories=Application;GTK;Utility;Dictionary;
+Categories=GTK;Utility;Dictionary;
 MimeType=application/ebview;
--- End Message ---
--- Begin Message ---
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

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#941192: marked as done (ebview FTCBFS: debian/rules uses the build architecture compiler)

[Debian Bug Tracking System]

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 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.)


-- 
941192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ebview
Version: 0.3.6.2-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

ebview fails to cross build from source, because debian/rules uses the
build architecture compiler as a make default. The easiest way of fixing
that is seeding CC from dpkg's buildtools.mk. Please consider applying
the attached patch.

Helmut
diff --minimal -Nru ebview-0.3.6.2/debian/changelog 
ebview-0.3.6.2/debian/changelog
--- ebview-0.3.6.2/debian/changelog 2018-11-04 16:12:52.0 +0100
+++ ebview-0.3.6.2/debian/changelog 2019-09-26 06:46:07.0 +0200
@@ -1,3 +1,9 @@
+ebview (0.3.6.2-3) UNRELEASED; urgency=medium
+
+  * Fix FTCBFS: Seed CC from dpkg's buildtools.mk. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 26 Sep 2019 06:46:07 +0200
+
 ebview (0.3.6.2-2) unstable; urgency=medium
 
   * QA upload
diff --minimal -Nru ebview-0.3.6.2/debian/rules ebview-0.3.6.2/debian/rules
--- ebview-0.3.6.2/debian/rules 2018-11-04 16:12:52.0 +0100
+++ ebview-0.3.6.2/debian/rules 2019-09-26 06:46:06.0 +0200
@@ -1,5 +1,6 @@
 #!/usr/bin/make -f
 
+-include /usr/share/dpkg/buildtools.mk
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 %:
--- End Message ---
--- Begin Message ---
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

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#711218: marked as done (add a IT8 target test)

[Debian Bug Tracking System]

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 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.)


-- 
711218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: screentest
Version: 2.0-2.1
Severity: wishlist

It would be nice to generate an IT8 target test:

https://en.wikipedia.org/wiki/IT8

they look like this:

https://en.wikipedia.org/wiki/File:IT8target.jpg

To quote wikipedia, we would need to generate:

These targets consists of 24 grey fields and 264 color fields in 22 columns:

Column 01 to 12: HCL color model, which differ in Hue, Chroma, and Lightness
Column 13 to 16: CMYK-Colors Cyan, Magenta, Yellow, and Key (black) in 
different steps of brightness
Column 17 to 19: RGB-Colors Red, Green, and Blue in different steps of 
brightness
Column 20 to 22: undefined, producers' choice

Anyone working on something like this?

-- System Information:
Debian Release: 7.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages screentest depends on:
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-38
ii  libcairo2   1.12.2-3
ii  libfontconfig1  2.9.0-7.1
ii  libfreetype62.4.9-1.1
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglade2-0 1:2.6.4-1
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libgtk2.0-0 2.24.10-2
ii  libpango1.0-0   1.30.0-1
ii  libxml2 2.8.0+dfsg1-7+nmu1

screentest recommends no packages.

screentest suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
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

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#967418: marked as done (gkrellmitime: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gkrellmitime
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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

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#711217: marked as done (doesn't render properly on startup)

[Debian Bug Tracking System]

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 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.)


-- 
711217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: screentest
Version: 2.0-2.1
Severity: important

When the window is brought up, some of the grids are missing. If the
window is refreshed, they come back.

This manifests in different ways: sometimes I get a blank square on
top left, sometimes only the help text is missing...

-- System Information:
Debian Release: 7.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages screentest depends on:
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-38
ii  libcairo2   1.12.2-3
ii  libfontconfig1  2.9.0-7.1
ii  libfreetype62.4.9-1.1
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglade2-0 1:2.6.4-1
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libgtk2.0-0 2.24.10-2
ii  libpango1.0-0   1.30.0-1
ii  libxml2 2.8.0+dfsg1-7+nmu1

screentest recommends no packages.

screentest suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
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

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#967738: marked as done (screentest: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: screentest
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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

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#967325: marked as done (ebview: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ebview
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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

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#969740: marked as done (tabble FTCBFS: broken embedded copy of AM_PATH_GTK_2_0)

[Debian Bug Tracking System]

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 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.)


-- 
969740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tabble
Version: 0.43-3
Severity: important
Tags: upstream fixed-upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

tabble fails to cross build from source, because it ships a broken,
outdated, embedded copy of AM_PATH_GTK_2_0 in aclocal.m4. Please remove
this embedded copy and use the packaged one instead. Failing that,
please update the copy and register it with the security tracker. Please
refer to https://wiki.debian.org/EmbeddedCopies for more details on the
process. This bug report comes without a patch, because the actual
problem has long been fixed. tabble just happens to ship a copy of the
bug.

Helmut
--- End Message ---
--- Begin Message ---
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 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#967781: marked as done (transfermii: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: transfermii
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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 https://bugs.debian.org/1035807

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#967766: marked as done (tabble: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tabble
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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 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#967803: marked as done (wininfo: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wininfo
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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 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#967407: marked as done (gkrellm-gkrellmpc: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gkrellm-gkrellmpc
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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 https://bugs.debian.org/1035812

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#967300: marked as done (darksnow: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: darksnow
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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

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#477359: marked as done (aylet performs Thanatos.ay quite strangely)

[Debian Bug Tracking System]

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 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.)


-- 
477359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aylet
Version: 0.5-1

When playing Thanatos.ay [1], it doesn't sound quite ``right'',
for the lack of a better word.

IIRC, I've heard this file performed much better by AYEmul (W32
binary available from [2].)

[1] ftp://ftp.worldofspectrum.org/pub/sinclair/music/ay/games/t/Thanatos.ay.zip
[2] ftp://ftp.worldofspectrum.org/pub/sinclair/music/players-pc/



--- End Message ---
--- Begin Message ---
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 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#510051: marked as done (Control keys do not work when aylet is started via xargs)

[Debian Bug Tracking System]

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 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.)


-- 
510051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aylet
Version: 0.5-2
Severity: normal


Use command similar to the following to reproduce:

echo "AgentX.ay AgentX2.ay" |xargs aylet


-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages aylet depends on:
ii  libc6 2.7-16 GNU C Library: Shared libraries
ii  libncurses5   5.7+20081213-1 shared libraries for terminal hand

aylet recommends no packages.

Versions of packages aylet suggests:
pn  aylet-gtk  (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
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 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#672808: marked as done (aylet: couldn't open sound device.)

[Debian Bug Tracking System]

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 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.)


-- 
672808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aylet
Version: 0.5-3
Severity: important

Dear Maintainers,

aylet is compiled to use OSS driver, and it seems OSS compatibility
layer is not installed by default in Debian Wheezy. As a workaround, one
can install alsa-oss package and start aylet as follows:

$ aoss aylet *.ay

Probably, there are other ways to solve the problem, but if going the
suggested way it would be good to add alsa-oss into the list of aylet
dependencies, and specifically mention the workaround in README.Debian.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages aylet depends on:
ii  libc62.13-32
ii  libncurses5  5.9-7
ii  libtinfo55.9-7

aylet recommends no packages.

Versions of packages aylet suggests:
pn  aylet-gtk  

-- no debconf information

-- 
...Bye..Dmitry.


--- End Message ---
--- Begin Message ---
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 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#930903: marked as done (aylet FTCBFS: hard codes the build architecture pkg-config)

[Debian Bug Tracking System]

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 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.)


-- 
930903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aylet
Version: 0.5-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

aylet fails to cross build from source, because a debian patch hard
codes the build architecture pkg-config. After making it substitutable,
aylet cross builds successfully. Please consider applying the attached
patch.

Helmut
diff -u aylet-0.5/debian/changelog aylet-0.5/debian/changelog
--- aylet-0.5/debian/changelog
+++ aylet-0.5/debian/changelog
@@ -1,3 +1,9 @@
+aylet (0.5-4) UNRELEASED; urgency=medium
+
+  * Fix FTCBFS: Make pkg-config substitutable. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 22 Jun 2019 08:49:53 +0200
+
 aylet (0.5-3) unstable; urgency=low
 
   * QA upload (Closes: #636740).
diff -u aylet-0.5/debian/patches/3_gtk2_Makefile.diff 
aylet-0.5/debian/patches/3_gtk2_Makefile.diff
--- aylet-0.5/debian/patches/3_gtk2_Makefile.diff
+++ aylet-0.5/debian/patches/3_gtk2_Makefile.diff
@@ -1,6 +1,6 @@
 --- aylet-0.5/Makefile 2005-12-18 04:05:08.0 +0100
 +++ aylet-0.5-changes/Makefile 2006-03-20 10:37:26.0 +0100
-@@ -39,14 +39,29 @@
+@@ -39,14 +39,30 @@
  
  all: aylet xaylet
  
@@ -11,7 +11,8 @@
 +gtk1: all
 +
 +# GTK+2 stuff: "make gtk2"
-+gtk2: GTKCONFIG:=pkg-config gtk+-2.0
++PKG_CONFIG?=pkg-config
++gtk2: GTKCONFIG:=$(PKG_CONFIG) gtk+-2.0
 +gtk2: GTKFLAGS:=-DGTK2 $(shell \
 +   $(GTKCONFIG) --modversion | \
 +   awk 'BEGIN { FS="." } \
--- End Message ---
--- Begin Message ---
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 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#967276: marked as done (bygfoot: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bygfoot
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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 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#964571: marked as done (Languages are installed in a directory which is not expected by "bygfoot")

[Debian Bug Tracking System]

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 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.)


-- 
964571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bygfoot
Version: 2.3.2-2+b1

Hi,

   - Bygfoot Football Manager game is only in English and does not offer the 
possibility to change the language.
   - I saw with "strace" that bygfoot searches for languages in 
"/usr/local/share/locale"
   - While dpkg indicates that they are installed in "/usr/share/games/locale"
   - So i tested a : "cp -R /usr/share/games/locale /usr/local/share/"
   - Manual copying of languages to the directory expected by bygfoot 
successfully bypasses the anomaly but I guess there must be a better solution.
 
I using Debian GNU/Linux 10, kernel 4.19.0-9-amd64, locale fr_FR.UTF-8, MATE 
desktop
 
Best regards,
Guillaume GÉANT
--- End Message ---
--- Begin Message ---
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 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#967265: marked as done (aylet: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aylet
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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 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#967268: marked as done (bbrun: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bbrun
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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 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#553314: marked as done (alltray: "Show/Hide" function and close button don't work)

[Debian Bug Tracking System]

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 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.)


-- 
553314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: alltray: "Show/Hide" function and close button don't work
Package: alltray
Version: 0.69-1
Justification: renders package unusable
Severity: grave

*** Please type your report below this line ***
when I use the alltray in any program, the menu option "show / hide" doesn't
work. For maximizing the program again, I had use the option "undock" and
for minimizing again, the close button doesn't work, I have to open another
alltray and use it.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages alltray depends on:
ii  libatk1.0-01.28.0-1  The ATK accessibility toolkit
ii  libc6  2.9-25GNU C Library: Shared libraries
ii  libcairo2  1.8.8-2   The Cairo 2D vector graphics
libra
ii  libfontconfig1 2.6.0-4   generic font configuration
library
ii  libfreetype6   2.3.11-1  FreeType 2 font engine, shared
lib
ii  libgconf2-42.28.0-1  GNOME configuration database
syste
ii  libglib2.0-0   2.22.2-2  The GLib library of C routines
ii  libgtk2.0-02.18.2-1  The GTK+ graphical user
interface
ii  liborbit2  1:2.14.17-1   libraries for ORBit2 - a CORBA
ORB
ii  libpango1.0-0  1.26.0-1  Layout and rendering of
internatio
ii  libpng12-0 1.2.40-1  PNG library - runtime
ii  libx11-6   2:1.2.2-1 X11 client-side library
ii  libxcursor11:1.1.9-1 X cursor management library
ii  libxext6   2:1.0.4-1 X11 miscellaneous extension
librar
ii  libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes'
extensio
ii  libxi6 2:1.2.1-2 X11 Input extension library
ii  libxinerama1   2:1.0.3-2 X11 Xinerama extension library
ii  libxrandr2 2:1.3.0-2 X11 RandR extension library
ii  libxrender11:0.9.4-2 X Rendering Extension client
libra
ii  zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime

alltray recommends no packages.

alltray suggests no packages.

-- no debconf information


reportbug-alltray-20091030-5856-kupWyF
Description: Binary data
--- End Message ---
--- Begin Message ---
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 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#967467: marked as done (gsetroot: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gsetroot
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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 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#411459: marked as done (alltray: Add multiple modifier support)

[Debian Bug Tracking System]

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 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.)


-- 
411459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alltray
Version: 0.69-2
Severity: wishlist
Tags: patch


Please apply this patch allowing several modifiers.
New syntax:  -k Modifier:Modifier:...:keycode .

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages alltray depends on:
ii  libatk1.0-0   1.12.4-2   The ATK accessibility toolkit
ii  libc6 2.3.6.ds1-12   GNU C Library: Shared libraries
ii  libcairo2 1.2.4-4The Cairo 2D vector graphics libra
ii  libfontconfig12.4.2-1generic font configuration library
ii  libfreetype6  2.2.1-5FreeType 2 font engine, shared lib
ii  libgconf2-4   2.16.0-3   GNOME configuration database syste
ii  libglib2.0-0  2.12.6-2   The GLib library of C routines
ii  libgtk2.0-0   2.8.20-5   The GTK+ graphical user interface 
ii  liborbit2 1:2.14.4-1 libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0 1.14.8-5   Layout and rendering of internatio
ii  libpng12-01.2.15~beta5-1 PNG library - runtime
ii  libx11-6  2:1.0.3-5  X11 client-side library
ii  libxcursor1   1.1.7-4X cursor management library
ii  libxext6  1:1.0.1-2  X11 miscellaneous extension librar
ii  libxfixes31:4.0.1-5  X11 miscellaneous 'fixes' extensio
ii  libxi61:1.0.1-4  X11 Input extension library
ii  libxinerama1  1:1.0.1-4.1X11 Xinerama extension library
ii  libxrandr22:1.1.0.2-5X11 RandR extension library
ii  libxrender1   1:0.9.1-3  X Rendering Extension client libra
ii  zlib1g1:1.2.3-13 compression library - runtime

alltray recommends no packages.

-- no debconf information
diff -u -Nru alltray-0.69/src/shortcut.c alltray-0.69.new/src/shortcut.c
--- alltray-0.69/src/shortcut.c	2006-07-06 17:42:23.0 +0200
+++ alltray-0.69.new/src/shortcut.c	2007-02-19 09:41:58.0 +0100
@@ -44,13 +44,27 @@
 #include "common.h"
 #include "utils.h"
 
+struct {
+  gchar* name;
+  unsigned int mask;
+} modifiers[] = {
+  { "Shift", ShiftMask },
+  { "Control", ControlMask },
+  { "Alt", Mod1Mask },
+  { "Winkey_right", Mod4Mask },
+  { "AltGr", Mod5Mask },
+  { NULL, 0}
+};
+
+
 gboolean parse_shortcut (gchar *string, 
 unsigned int *key_return, unsigned int *modifier_return)
 {
 
   gchar *tmp=NULL;
   gchar *colon=NULL;
-  gchar *modifier=NULL;
+  gchar *current=NULL;
+  int i;
 
 
   if (debug) printf ("parse_shortcut\n");
@@ -59,74 +73,34 @@
 return FALSE;
 
   tmp=g_strdup (string);
-  
-  colon=strstr (tmp,":");
 
-  if (colon) {
-if (debug) printf ("colon: %s\n", colon);
+  *modifier_return=0;
+  for (current=tmp; (colon=strchr (current,':')) != NULL; current=colon+1) {
 
-*key_return =atoi (++colon);
-
-if (*key_return == 0)
-  *key_return=XKeysymToKeycode(GDK_DISPLAY(), XStringToKeysym(colon));
-
-   *(--colon)=0;
-   modifier=tmp;
-  
-   if (debug) printf ("modifier: %s\n", modifier);
-
-   do {
-
-if (!strcmp (modifier, "Shift")) {
-  if (debug) printf ("found Shift\n");
-  *modifier_return=ShiftMask;
-  break;
-}
-
-if (!strcmp (modifier, "Control")) {
-  if (debug) printf ("found Control\n");
-  *modifier_return=ControlMask;
-  break;
-}
-  
-if (!strcmp (modifier, "Alt")) {
-  if (debug) printf ("found Alt\n");
-  *modifier_return=Mod1Mask;
-  break;
-}
-
-if (!strcmp (modifier, "Winkey_right")) {
-  if (debug) printf ("found Winkey_right\n");
-  *modifier_return=Mod4Mask;
-  break;
-}   
+   *colon=0;
 
-if (!strcmp (modifier, "AltGr")) {
-  if (debug) printf ("found AltGr\n");
-  *modifier_return=Mod5Mask;
-  break;
-}   
+   if (debug) printf ("modifier: %s\n", current);
 
+   for (i = 0; modifiers[i].name; ++i) {
+

Bug#571982: marked as done (alltray: no tray icon; no way to get program in question back out of tray)

[Debian Bug Tracking System]

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 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.)


-- 
571982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alltray
Version: 0.70-1
Severity: grave
Justification: renders package unusable

"alltray iceowl --st --na &" causes Iceowl to start, but no icon actually 
appears in the system tray and there's no way to get the program back up again 
without re-running it.  Doesn't that kind of defeat the purpose of alltray?


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32pio (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages alltray depends on:
ii  libatk1.0-0   1.28.0-1   The ATK accessibility toolkit
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib
ii  libcairo2 1.8.8-2The Cairo 2D vector graphics libra
ii  libfontconfig12.8.0-2generic font configuration library
ii  libfreetype6  2.3.11-1   FreeType 2 font engine, shared lib
ii  libgconf2-4   2.28.0-1   GNOME configuration database syste
ii  libglib2.0-0  2.22.4-1   The GLib library of C routines
ii  libgtk2.0-0   2.18.6-1   The GTK+ graphical user interface 
ii  libpango1.0-0 1.26.2-1   Layout and rendering of internatio
ii  libx11-6  2:1.3.3-1  X11 client-side library

alltray recommends no packages.

alltray suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
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 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#663267: marked as done (alltray: Introduce latest release (0.7.5.1dev) into unstable)

[Debian Bug Tracking System]

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 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.)


-- 
663267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alltray
Version: 0.71b-1
Severity: normal
Tags: upstream

The latest release of alltray has been out for over 6 months now and includes
support for closing an application to tray (rather than terminating it).

I have not actually tried to compile it myself and test it out, but I can do
that if needed.
Download to compile: https://launchpad.net/alltray/+download



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages alltray depends on:
ii  libatk1.0-0 2.2.0-2
ii  libc6   2.13-27
ii  libcairo2   1.10.2-7
ii  libfontconfig1  2.8.0-3.1
ii  libfreetype62.4.8-1
ii  libgconf2-4 3.2.3-3
ii  libglib2.0-02.30.2-6
ii  libgtk2.0-0 2.24.10-1
ii  libpango1.0-0   1.29.4-3
ii  libx11-62:1.4.4-4

alltray recommends no packages.

alltray suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
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 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#613218: marked as done (Alltray doesn't work with iceweasel in testing)

[Debian Bug Tracking System]

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 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.)


-- 
613218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alltray
Versione: 0.71b-1  [i386]

On Debian testing alias "wheezy" alltray doesn't work with iceweasel.
If I exec: alltray iceweasel
iceweasel isn't docked, but is showed.
In I use alltray without argoments, and I try to dock iceweasel, it is docked 
but the "show" event on icon tray 
dosn't work.

All on xfce4 with xfwm4 4.6.2-1


Valenti Walter


  --- End Message ---
--- Begin Message ---
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 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#677188: marked as done (alltray: doesn't work : parse_theme: assertion failed)

[Debian Bug Tracking System]

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 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.)


-- 
677188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alltray
Version: 0.71b-1
Severity: normal

Hi.

My Gnome session looks different after an upgrade to 3.4 in recent testing 
transition, so there may be a problem with the theme.

Alltray doesn't seem to like that :
$ LANG=C alltray sshmenu
(eval):3: warning: discarding old message_type
(eval):1: warning: method redefined; discarding old message_type=
**
ERROR:gnome_theme.c:207:parse_theme: assertion failed: (content)
Abandon

The (eval) messages seem to be those of sshmenu.

Hope this helps.

Best regards,

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages alltray depends on:
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-33
ii  libcairo2   1.12.2-1
ii  libfontconfig1  2.9.0-6
ii  libfreetype62.4.9-1
ii  libgconf2-4 3.2.5-1
ii  libglib2.0-02.32.3-1
ii  libgtk2.0-0 2.24.10-1
ii  libpango1.0-0   1.30.0-1
ii  libx11-62:1.4.99.901-2

alltray recommends no packages.

alltray suggests no packages.

-- debconf-show failed


--- End Message ---
--- Begin Message ---
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 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#829825: marked as done (alltray: Uses deprecated gnome-common macros/variables)

[Debian Bug Tracking System]

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 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.)


-- 
829825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alltray
Version: 0.71b-1
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-common

Hi,

gnome-common did a cleanup upstream and deprecated quite a few macros
and variables.

gnome-doc-utils removal
===
The gnome-doc-utils build infrastructure was removed completely along
with the following macros:

 GNOME_DOC_INIT [1]
 GNOME_COMMON_INIT [2]


deprecated variables

The following variables used in gnome-autogen.sh have been declared
deprecated [3]:

 REQUIRED_GNOME_DOC_UTILS_VERSION
 REQUIRED_DOC_COMMON_VERSION
 USE_COMMON_DOC_BUILD
 FORBIDDEN_M4MACROS
 GNOME2_DIR
 GNOME2_PATH
 USE_GNOME2_MACROS

deprecated macros
=
The following macros have also been declared deprecated:

 GNOME_COMPILE_WARNINGS [4]
 GNOME_CXX_WARNINGS [5]

Upstream has documentation at [6] with how you can fix your package and
why those particular changes were made.

According to codesearch.d.n your package alltray uses one of the macros or
variables so might be affected, especially once you run autoreconf. Please
update your package accordingly and forward it to upstream if possible.

If you have further question, please don't hesitate to ask.

Regards,
Michael

[1] https://git.gnome.org/browse/gnome-common/commit/?id=6684e2fa5
[2] https://git.gnome.org/browse/gnome-common/commit/?id=1f60e9536
[3] https://git.gnome.org/browse/gnome-common/commit/?id=4c8d8ad93
[4] https://git.gnome.org/browse/gnome-common/commit/?id=b57bae0be
[5] https://git.gnome.org/browse/gnome-common/commit/?id=2bffd7e1u
[6] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
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 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#930477: marked as done (alltray disrupts GUI for application program it docks)

[Debian Bug Tracking System]

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 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.)


-- 
930477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alltray
Version: 0.71b-1+b2
Severity: important

Dear Maintainer,

When running the command:

   alltray zotero

the zotero program is opened, successfully docks and appears normal, however,
when you go to the system tray and display the zotero application window,
dragging and dropping items between collections (folders) is broken.  If 
zotero is launched outside of alltray, or launched instead using kdocker 
(the KDE equivalent of alltray), zotero has no problems.

NOTES:
  - When attempting to drag and drop in zotero, the folder name you are
dragging to becomes highlighted once you are aligned sufficiently
to allow dropping. When run under alltray, this highlighting never
occurs no matter where you position the item to be dropped, and
dropping the item doesn't work.

  - In zotero, this drag/drop mechanism is the only method which can be
used to copy or move items between the collection folders, so this
completely breaks copy/move functionality. I have not noticed any other
GUI issues when running zotero under alltray

  - Zotero version 5.0.66

  - For people seeking a workaround, when using kdocker (at least in debian
stretch), you need to use the "-n" option (which is not listed on the
kdocker man page):  kdocker -n Zotero zotero


-- System Information:
Debian Release: 9.9
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages alltray depends on:
ii  gconf-service3.2.6-4+b1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u4
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgconf-2-4 3.2.6-4+b1
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libx11-6 2:1.6.4-3+deb9u1

alltray recommends no packages.

alltray suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
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 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#915500: marked as done (alltray: Alltray not working correctly in fluxbox. show/hide command don't work)

[Debian Bug Tracking System]

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 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.)


-- 
915500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alltray
Version: 0.71b-1+b2
Severity: normal

Dear Maintainer,
Run alltray in click mode. App icon (for example kcalc, terminator) appear in 
tray, but nothing happen when i clicked on show/hide command from tray context 
menu.
When i'm running alltray from console result is: no tray icon.


-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages alltray depends on:
ii  gconf-service3.2.6-4+b1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u3
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgconf-2-4 3.2.6-4+b1
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libx11-6 2:1.6.4-3+deb9u1

alltray recommends no packages.

alltray suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
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 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#967249: marked as done (alltray: depends on deprecated GTK 2)

[Debian Bug Tracking System]

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 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.)


-- 
967249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alltray
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
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 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#999840: marked as done (alltray: Fails to start, opens and closes the window immediately)

[Debian Bug Tracking System]

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 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.)


-- 
999840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alltray
Version: 0.71b-2
Severity: important

Dear Maintainer,

when started, the app launches its "configuration" window and closes it
immediately. I've been able to read the text in the window only having it
recorded with kazam, needless to say I didn't click anywhere "else" to close
it. If started from a terminal, gives "ERROR get class hints" message in 
stdout. Useless.

I'm using KDE Plasma from stable ("bullseye") as the desktop environment, if 
it's important.


-- System Information:
Debian Release: 11.1
  APT prefers stable-security
  APT policy: (991, 'stable-security'), (991, 'stable'), (99, 'testing'), (90,
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.14.9-bootes0-p-1000 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en_US
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages alltray depends on:
ii  gconf-service 3.2.6-7
ii  libc6 2.31-13+deb11u2
ii  libgconf-2-4  3.2.6-7
ii  libgdk-pixbuf-2.0-0   2.42.2+dfsg-1
ii  libgdk-pixbuf-xlib-2.0-0  2.40.2-2
ii  libglib2.0-0  2.66.8-1
ii  libgtk2.0-0   2.24.33-2
ii  libx11-6  2:1.7.2-1

alltray recommends no packages.

alltray suggests no packages.
--- End Message ---
--- Begin Message ---
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 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#1035737: Removed package(s) from unstable

[Debian FTP Masters]

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; orphaned; depends on gtk2; low popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035737

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#1035737: Removed package(s) from unstable

[Debian FTP Masters]

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

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#1035750: Removed package(s) from unstable

[Debian FTP Masters]

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 popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035750

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#1035750: Removed package(s) from unstable

[Debian FTP Masters]

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

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#1035770: Removed package(s) from unstable

[Debian FTP Masters]

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 popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035770

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#1035770: Removed package(s) from unstable

[Debian FTP Masters]

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

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#1035774: Removed package(s) from unstable

[Debian FTP Masters]

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, ppc64el, s390x
libdbaudiolib0-dev |0.9.8-8 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; orphaned; RC-buggy; depends on gtk2; low popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035774

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#1035774: Removed package(s) from unstable

[Debian FTP Masters]

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 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#1035776: Removed package(s) from unstable

[Debian FTP Masters]

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 popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035776

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#1035776: Removed package(s) from unstable

[Debian FTP Masters]

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

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#1035777: Removed package(s) from unstable

[Debian FTP Masters]

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; orphaned; depends on gtk2; low popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035777

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#1035777: Removed package(s) from unstable

[Debian FTP Masters]

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

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#1035806: Removed package(s) from unstable

[Debian FTP Masters]

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 popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035806

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#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Andreas Beckmann]

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   not owned


You should look closer:

0m45.2s DEBUG: Modified(user, group, mode, size, target): /etc/shells 
expected(root, root, - 100644, 128, None) != found(root, root, - 100644, 140, 
None)

It's a 12 byte difference. That's not 9base's entries. What you see here
is "/usr/bin/sh\n". So this is a /usr-merge bug. We already know it.
Thus force-merging.


Given that this seems to be the only package showing this behavior in my 
bullseye2bookworm tests so far, I didn' expect some "systematic" error 
outside of this package.



Andreas

Bug#1035806: Removed package(s) from unstable

[Debian FTP Masters]

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

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#1035807: Removed package(s) from unstable

[Debian FTP Masters]

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, ppc64el, s390x

--- Reason ---
RoQA; orphaned; depends on gtk2; low popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035807

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#1035807: Removed package(s) from unstable

[Debian FTP Masters]

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 https://bugs.debian.org/1035807

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#1035809: Removed package(s) from unstable

[Debian FTP Masters]

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 popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035809

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#1035809: Removed package(s) from unstable

[Debian FTP Masters]

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 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#1035811: Removed package(s) from unstable

[Debian FTP Masters]

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 popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035811

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#1035811: Removed package(s) from unstable

[Debian FTP Masters]

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 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#1035812: Removed package(s) from unstable

[Debian FTP Masters]

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 ---
RoQA; orphaned; depends on gtk2; low popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035812

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#1035812: Removed package(s) from unstable

[Debian FTP Masters]

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 https://bugs.debian.org/1035812

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#1035814: Removed package(s) from unstable

[Debian FTP Masters]

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 popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035814

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#1035814: Removed package(s) from unstable

[Debian FTP Masters]

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

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#1035815: Removed package(s) from unstable

[Debian FTP Masters]

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 popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035815

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#1035815: Removed package(s) from unstable

[Debian FTP Masters]

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 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#1035816: Removed package(s) from unstable

[Debian FTP Masters]

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 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#1035816: Removed package(s) from unstable

[Debian FTP Masters]

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; orphaned; depends on gtk2; low popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035816

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#1035817: Removed package(s) from unstable

[Debian FTP Masters]

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, 
ppc64el, s390x

--- Reason ---
RoQA; orphaned; depends on gtk2; low popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035817

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#1035817: Removed package(s) from unstable

[Debian FTP Masters]

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 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#1035818: Removed package(s) from unstable

[Debian FTP Masters]

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; orphaned; depends on gtk2; low popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035818

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#1035818: Removed package(s) from unstable

[Debian FTP Masters]

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 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#1035819: Removed package(s) from unstable

[Debian FTP Masters]

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 popcon
--

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 1035...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1035819

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#1035819: Removed package(s) from unstable

[Debian FTP Masters]

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 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)