[bts-link] source package src:python-svg.path

2023-11-30 Thread debian-bts-link 
#
# bts-link upstream status pull for source package src:python-svg.path
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #1055159 (http://bugs.debian.org/1055159)
# Bug title: python-svg.path's autopkg tests fail with pillow 10.1.0
#  * https://github.com/regebro/svg.path/issues/103
#  * remote status changed: (?) -> open
usertags 1055159 + status-open

thanks

Bug#1054303: marked as done (RM: gscanbus -- RoQA; orphaned; dead upstream; depends on gtk2)

2023-11-30 Thread Debian Bug Tracking System 
Your message dated Thu, 30 Nov 2023 18:48:34 +
with message-id 
and subject line Bug#1056370: Removed package(s) from unstable
has caused the Debian Bug report #1054303,
regarding RM: gscanbus -- RoQA; orphaned; dead upstream; depends on gtk2
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.)


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

Source: gscanbus
Severity: serious

gscanbus is orphaned for 7 years and dead upstream. It also depends on the 
obsolete GTK 2.
I am going to file a RM bug when this is autoremoved from testing and nobody 
objects.
--- End Message ---
--- Begin Message ---
Version: 0.8-3+rm

Dear submitter,

as the package gscanbus 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/1056370

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1054301: marked as done (RM: glfer -- RoQA; orphaned; dead upstream; depends on gtk2)

2023-11-30 Thread Debian Bug Tracking System 
Your message dated Thu, 30 Nov 2023 18:50:24 +
with message-id 
and subject line Bug#1056369: Removed package(s) from unstable
has caused the Debian Bug report #1054301,
regarding RM: glfer -- RoQA; orphaned; dead upstream; depends on gtk2
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.)


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

Source: glfer
Severity: serious

glfer is orphaned for 14 years and dead upstream. It also depends on the 
obsolete GTK 2.
I am going to file a RM bug when this is autoremoved from testing and nobody 
objects.
--- End Message ---
--- Begin Message ---
Version: 0.4.2-4+rm

Dear submitter,

as the package glfer 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/1056369

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#658373: marked as done (glfer: Impossible to open any PCM WAV files)

2023-11-30 Thread Debian Bug Tracking System 
Your message dated Thu, 30 Nov 2023 18:50:24 +
with message-id 
and subject line Bug#1056369: Removed package(s) from unstable
has caused the Debian Bug report #658373,
regarding glfer: Impossible to open any PCM WAV files
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.)


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

glfer says "input is not a PCM WAV file"

WAV file for testing:

http://www-mmsp.ece.mcgill.ca/documents/audioformats/wave/Samples/Perverse/Utopia%20Critical%20Stop.WAV

(I'm guessing that this may be due to 64 bits arch)



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

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

Versions of packages glfer depends on:
ii  fftw2 2.1.3-22   library for computing Fast Fourier
ii  libatk1.0-0   2.2.0-2ATK accessibility toolkit
ii  libc6 2.13-24Embedded GNU C Library: Shared lib
ii  libcairo2 1.10.2-6.2 The Cairo 2D vector graphics libra
ii  libfontconfig12.8.0-3.1  generic font configuration library
ii  libfreetype6  2.4.8-1FreeType 2 font engine, shared lib
ii  libgdk-pixbuf2.0-02.24.0-2   GDK Pixbuf library
ii  libglib2.0-0  2.30.2-5   GLib library of C routines
ii  libgtk2.0-0   2.24.8-3   GTK+ graphical user interface libr
ii  libpango1.0-0 1.29.4-2   Layout and rendering of internatio

glfer recommends no packages.

Versions of packages glfer suggests:
ii  extra-xdg-menus   1.0-4  Extra menu categories for applicat

-- no debconf information




--- End Message ---
--- Begin Message ---
Version: 0.4.2-4+rm

Dear submitter,

as the package glfer 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/1056369

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#967425: marked as done (glfer: depends on deprecated GTK 2)

2023-11-30 Thread Debian Bug Tracking System 
Your message dated Thu, 30 Nov 2023 18:50:24 +
with message-id 
and subject line Bug#1056369: Removed package(s) from unstable
has caused the Debian Bug report #967425,
regarding glfer: 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.)


-- 
967425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glfer
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.4.2-4+rm

Dear submitter,

as the package glfer 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/1056369

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#967466: marked as done (gscanbus: depends on deprecated GTK 2)

2023-11-30 Thread Debian Bug Tracking System 
Your message dated Thu, 30 Nov 2023 18:48:34 +
with message-id 
and subject line Bug#1056370: Removed package(s) from unstable
has caused the Debian Bug report #967466,
regarding gscanbus: 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.)


-- 
967466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gscanbus
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.8-3+rm

Dear submitter,

as the package gscanbus 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/1056370

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#967471: marked as done (gtick: depends on deprecated GTK 2)

2023-11-30 Thread Debian Bug Tracking System 
Your message dated Thu, 30 Nov 2023 18:57:45 +
with message-id 
and subject line Bug#1054406: Removed package(s) from unstable
has caused the Debian Bug report #967471,
regarding gtick: 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.)


-- 
967471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtick
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.5-3+rm

Dear submitter,

as the package gtick 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/1054406

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1049720: marked as done (gtick: Fails to build binary packages again after successful build)

2023-11-30 Thread Debian Bug Tracking System 
Your message dated Thu, 30 Nov 2023 18:57:45 +
with message-id 
and subject line Bug#1054406: Removed package(s) from unstable
has caused the Debian Bug report #1049720,
regarding gtick: Fails to build binary packages again after successful build
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.)


-- 
1049720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtick
Version: 0.5.5-3
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -b
> -
> 
> dpkg-buildpackage: info: source package gtick
> dpkg-buildpackage: info: source version 0.5.5-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Pino Toscano 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  fakeroot debian/rules clean
> dh clean
>dh_auto_clean
>   make -j8 distclean
> make[1]: Entering directory '/<>'
> Making distclean in doc
> make[2]: Entering directory '/<>/doc'
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f Makefile
> make[2]: Leaving directory '/<>/doc'
> Making distclean in po
> make[2]: Entering directory '/<>/po'
> rm -f *.insert-header
> rm -f remove-potcdate.sed
> rm -f stamp-poT
> rm -f core core.* gtick.po gtick.1po gtick.2po *.new.po
> rm -fr *.o
> rm -f Makefile Makefile.in POTFILES *.mo
> make[2]: Leaving directory '/<>/po'
> Making distclean in src
> make[2]: Entering directory '/<>/src'
> test -z "gtick" || rm -f gtick
> test -z "optionlexer.c optionparser.h optionparser.c" || rm -f optionlexer.c 
> optionparser.h optionparser.c
> rm -f *.o
> rm -f *.tab.c
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f ./.deps/dsp.Po
> rm -f ./.deps/g711.Po
> rm -f ./.deps/gtick.Po
> rm -f ./.deps/gtkoptions.Po
> rm -f ./.deps/gtkutil.Po
> rm -f ./.deps/help.Po
> rm -f ./.deps/metro.Po
> rm -f ./.deps/option.Po
> rm -f ./.deps/optionlexer.Po
> rm -f ./.deps/optionparser.Po
> rm -f ./.deps/options.Po
> rm -f ./.deps/profiles.Po
> rm -f ./.deps/threadtalk.Po
> rm -f ./.deps/util.Po
> rm -f ./.deps/visualtick.Po
> rm -f Makefile
> make[2]: Leaving directory '/<>/src'
> Making distclean in testsuite
> make[2]: Entering directory '/<>/testsuite'
> test -z "testdsp testg711 testmetro testmetro-static" || rm -f testdsp 
> testg711 testmetro testmetro-static
> rm -f *.o
> test -z "testdsp.log testg711.log testmetro.log testmetro-static.log" || rm 
> -f testdsp.log testg711.log testmetro.log testmetro-static.log
> rm -f *.tab.c
> test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> test . = "." || test -z "" || rm -f 
> rm -f ../src/*.o
> test -z "testdsp.trs testg711.trs testmetro.trs testmetro-static.trs" || rm 
> -f testdsp.trs testg711.trs testmetro.trs testmetro-static.trs
> rm -f ../src/.deps/.dirstamp
> test -z "test-suite.log" || rm -f test-suite.log
> rm -f ../src/.dirstamp
> rm -f ../src/.deps/dsp.Po
> rm -f ../src/.deps/g711.Po
> rm -f ../src/.deps/gtkoptions.Po
> rm -f ../src/.deps/gtkutil.Po
> rm -f ../src/.deps/help.Po
> rm -f ../src/.deps/metro.Po
> rm -f ../src/.deps/option.Po
> rm -f ../src/.deps/optionlexer.Po
> rm -f ../src/.deps/optionparser.Po
> rm -f ../src/.deps/options.Po
> rm -f ../src/.deps/profiles.Po
> rm -f ../src/.deps/threadtalk.Po
> rm -f ../src/.deps/util.Po
> rm -f ../src/.deps/visualtick.Po
> rm -f ./.deps/common.Po
> rm -f ./.deps/testdsp.Po
> rm -f ./.deps/testg711.Po
> rm -f ./.deps/testmetro-static.Po
> rm -f ./.deps/testmetro.Po
> rm -f Makefile
> make[2]: Leaving directory '/<>/testsuite'
> make[2]: Entering directory '/<>'
> test -z "intl/Makefile" ||

Bug#1056370: Removed package(s) from unstable

2023-11-30 Thread Debian FTP Masters 
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  gscanbus |  0.8-3 | source, amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, riscv64, s390x

--- Reason ---
RoQA; orphaned; dead upstream; depends on gtk2
--

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

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

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.
Thorsten Alteholz (the ftpmaster behind the curtain)

Bug#1056370: Removed package(s) from unstable

2023-11-30 Thread Debian FTP Masters 
Version: 0.8-3+rm

Dear submitter,

as the package gscanbus 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/1056370

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.
Thorsten Alteholz (the ftpmaster behind the curtain)

Bug#1056369: Removed package(s) from unstable

2023-11-30 Thread Debian FTP Masters 
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 glfer |0.4.2-4 | source, amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, riscv64, s390x

--- Reason ---
RoQA; orphaned; dead upstream; depends on gtk2
--

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

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

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.
Thorsten Alteholz (the ftpmaster behind the curtain)

Bug#1056369: Removed package(s) from unstable

2023-11-30 Thread Debian FTP Masters 
Version: 0.4.2-4+rm

Dear submitter,

as the package glfer 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/1056369

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.
Thorsten Alteholz (the ftpmaster behind the curtain)

Bug#1054406: Removed package(s) from unstable

2023-11-30 Thread Debian FTP Masters 
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 gtick |0.5.5-3 | source, amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, riscv64, s390x

--- Reason ---
RoQA; orphaned; alternative exists; depends on gtk2
--

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

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

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.
Thorsten Alteholz (the ftpmaster behind the curtain)

Bug#1054406: Removed package(s) from unstable

2023-11-30 Thread Debian FTP Masters 
Version: 0.5.5-3+rm

Dear submitter,

as the package gtick 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/1054406

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.
Thorsten Alteholz (the ftpmaster behind the curtain)

Processed: bug 1038364 is forwarded to https://github.com/Globulation2/glob2/issues/76

2023-11-30 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forwarded 1038364 https://github.com/Globulation2/glob2/issues/76
Bug #1038364 [src:glob2] glob2: Depends on SDL 1.2
Set Bug forwarded-to-address to 
'https://github.com/Globulation2/glob2/issues/76'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1038364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013738: marked as done (gxmessage: Please remove dependency on install-info)

2023-11-30 Thread Debian Bug Tracking System 
Your message dated Fri, 01 Dec 2023 01:19:08 +
with message-id 
and subject line Bug#1013738: fixed in gxmessage 3.4.3-2
has caused the Debian Bug report #1013738,
regarding gxmessage: Please remove dependency on install-info
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.)


-- 
1013738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gxmessage
Severity: minor

Dear Maintainer,

your package declares a dependency on "install-info". However this
dependency should only be needed for info viewers, as they have to
care about updating the info index. Your package do not seem to be an
info viewer hence the dependency on "install-info" is not needed.
Consider to remove it.

https://wiki.debian.org/Transitions/DpkgToGnuInstallInfo

Many thanks,

Hilmar Preuße
--- End Message ---
--- Begin Message ---
Source: gxmessage
Source-Version: 3.4.3-2
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
gxmessage, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1013...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated gxmessage package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 30 Nov 2023 19:41:55 -0500
Source: gxmessage
Architecture: source
Version: 3.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 981873 1013738 1049736
Changes:
 gxmessage (3.4.3-2) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Jelmer Vernooij ]
   * Migrate repository from alioth to salsa.
 .
   [ Boyuan Yang ]
   * debian/: Apply wrap-and-sort -abst.
   * Bump debhelper v13, Standards-Version 4.6.2.
   * debian/control: Update homepage. (Closes: #981873)
   * debian/control: Do not depend on install-info. (Closes: #1013738)
   * debian/control: Build-dep on texinfo to avoid double FTBFS.
 (Closes: #1049736)
Checksums-Sha1:
 f158e382782805ce6dc92fd2ca71792ee72836c9 1928 gxmessage_3.4.3-2.dsc
 7d9d7a72e90b3421fd615387bba8e44b931c35ed 275354 gxmessage_3.4.3.orig.tar.gz
 0684e59e425612e43b962f840036231d4a1d5751 4476 gxmessage_3.4.3-2.debian.tar.xz
 9962872c1df1eeb98c494e2c8d09b94d59f7b797 15448 
gxmessage_3.4.3-2_amd64.buildinfo
Checksums-Sha256:
 4515f6dc1d3d2816bc387517b19ec616225eefb1e62060877ef1e5d5f85f7199 1928 
gxmessage_3.4.3-2.dsc
 db4e1655fc58f31e5770a17dfca4e6c89028ad8b2c8e043febc87a0beedeef05 275354 
gxmessage_3.4.3.orig.tar.gz
 82d7bd3d397fcbea80d126cb6ed8fd82ca96831669d4682d8a25ef6512348752 4476 
gxmessage_3.4.3-2.debian.tar.xz
 4f5e1fbf246ceb2698be68cb1fe5be673f7c988b78060040a623a0527ff97c50 15448 
gxmessage_3.4.3-2_amd64.buildinfo
Files:
 91d18e933710d9c2f98568610f950b4d 1928 gnome optional gxmessage_3.4.3-2.dsc
 0e6b5b23ffccc785ff8627485f6b7ce4 275354 gnome optional 
gxmessage_3.4.3.orig.tar.gz
 9da976381059b567fdd220dac1a76f70 4476 gnome optional 
gxmessage_3.4.3-2.debian.tar.xz
 8dc6c32a5fe2382836b3dfbe3f8b6cce 15448 gnome optional 
gxmessage_3.4.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmVpL6AACgkQwpPntGGC
Ws7fKQ//YhAoXiPKs50QARrDCuuMVO0ja3fkmQtgUH4DxjEF9oh2/tDsrwaVyUtk
i3iNn8iFd79iPhpNw7HYoEhsdaNUohMwT5fQKLPV48gw/0O2QrxD06yFn1O2APXi
PpBZwkJxdTrj1m7j0n2FE/w7yvRcCBaZhc9Gs9CSSTonyeWkiHeoDrhZsc6ojqxi
LUrvi/aTs29AtOWq6p+sVMvPPzk+RmqSqeZkKt4fQYAoAV4lfOSY2fMXGMDVxAut
Q53PK4GhxIF6iMsl3jyYIqMIsyELXAEEhE3fVhA1eZyx4eCm9UTn866n3GQEGHN+
sxHAiqbiVJR/yxXcsZc7/j0debpe7ZHMJoui/ZEcvlip5LnY+7I1tymBBrCnmTxS
xysDVwbLiHvc0o6LXNv5zFFN0WtaFFFZgU2t0BN6TptQSqkzRI4uFs8y5dxV48th
tbvNSO/WoN/9j9sULM9OipIHMvtxaQZGCX3cBBYdSGdaR5j45LKqvJaFUmtKXhS4
G1I+aMimHNiFKWgImw6HpQYV1nYhC1cQaWQRuXpZmGu7jmvm8iqwsguKhE+AhGSf
BRk9+7w3xmOBENz04gP63/iwk3BfgJiQY0HmB4OMWW/r/vNc9NRgron9A6YgVKVP
zWFuONFyRF2KSzSyo2Pzvu6FYY0Z9iP+dvwKQ8cKdh8KYamiV/E=
=vW2r
-END PGP SIGNATURE End Message ---

Bug#1049736: marked as done (gxmessage: Fails to build binary packages again after successful build)

2023-11-30 Thread Debian Bug Tracking System 
Your message dated Fri, 01 Dec 2023 01:19:08 +
with message-id 
and subject line Bug#1049736: fixed in gxmessage 3.4.3-2
has caused the Debian Bug report #1049736,
regarding gxmessage: Fails to build binary packages again after successful build
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.)


-- 
1049736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gxmessage
Version: 3.4.3-1
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -b
> -
> 
> dpkg-buildpackage: info: source package gxmessage
> dpkg-buildpackage: info: source version 3.4.3-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Daniel Echeverry 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  fakeroot debian/rules clean
> dh clean  --with autotools-dev
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
> dh: warning: The autotools-dev sequence is deprecated and replaced by dh in 
> debhelper (>= 9.20160115)
> dh: warning: This feature will be removed in compat 12.
>dh_auto_clean
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   make -j1 distclean
> make[1]: Entering directory '/<>'
> Making distclean in doc
> make[2]: Entering directory '/<>/doc'
> make[3]: Entering directory '/<>/doc'
> test -z "gxmessage.dvi gxmessage.pdf gxmessage.ps gxmessage.html" \
> || rm -rf gxmessage.dvi gxmessage.pdf gxmessage.ps gxmessage.html
> rm -rf gxmessage.t2d gxmessage.t2p
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> test -z "gxmessage.info" || rm -f gxmessage.info
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> make[3]: Leaving directory '/<>/doc'
> rm -f Makefile
> make[2]: Leaving directory '/<>/doc'
> Making distclean in po
> make[2]: Entering directory '/<>/po'
> rm -f *.pox gxmessage.pot *.old.po cat-id-tbl.tmp
> rm -f .intltool-merge-cache
> rm -f Makefile Makefile.in POTFILES stamp-it
> rm -f *.mo *.msg *.cat *.cat.m *.gmo
> make[2]: Leaving directory '/<>/po'
> make[2]: Entering directory '/<>'
> test -z "gxmessage" || rm -f gxmessage
> rm -f *.o
> rm -f *.tab.c
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f config.h stamp-h1
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f cscope.out cscope.in.out cscope.po.out cscope.files
> make[2]: Leaving directory '/<>'
> rm -f config.status config.cache config.log configure.lineno 
> config.status.lineno
> rm -rf ./.deps
> rm -f Makefile
> make[1]: Leaving directory '/<>'
>dh_autotools-dev_restoreconfig
> dh_autotools-dev_restoreconfig: warning: Compatibility levels before 10 are 
> deprecated (level 9 in use)
> dh_autotools-dev_restoreconfig: warning: dh_autotools-dev_restoreconfig is 
> deprecated; please see dh_autotools-dev_restoreconfig(1) for a replacement
> dh_autotools-dev_restoreconfig: warning: This feature will be removed in 
> compat 12.
>dh_clean
> dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in 
> use)
>  debian/rules build
> dh build  --with autotools-dev
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
> dh: warning: The autotools-dev sequence is deprecated and replaced by dh in 
> debhelper (>= 9.20160115)
> dh: warning: This feature will be removed in compat 12.
>dh_update_autotools_config
>dh_autotools-dev_updateconfig
> dh_autotools-dev_updateconfig: warning: Compatibility levels before 10 are 
> deprecated (level 9 in use)
> dh_autotools-dev_updateconfig: warning: dh_autotools-dev_updateconfig is 
> deprecated; please see dh_aut

Bug#981873: marked as done (gxmessage: Wrong homepage)

2023-11-30 Thread Debian Bug Tracking System 
Your message dated Fri, 01 Dec 2023 01:19:08 +
with message-id 
and subject line Bug#981873: fixed in gxmessage 3.4.3-2
has caused the Debian Bug report #981873,
regarding gxmessage: Wrong homepage
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.)


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

Package: gxmessage
Version: 3.4.3-1
Severity: normal

I have see that the project homepage do not respond anymore:
http://homepages.ihug.co.nz/~trmusson/programs.html#gxmessage

I think that the homepage is now:
https://trmusson.dreamhosters.com/programs.html#gxmessage

see here:
https://savannah.gnu.org/forum/forum.php?forum_id=9292

Ciao
Davide

Note: this is a simplified bug report that I use to report homepage 
problems found at https://repology.org/repository/debian_testing/problems
--- End Message ---
--- Begin Message ---
Source: gxmessage
Source-Version: 3.4.3-2
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
gxmessage, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 981...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated gxmessage package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 30 Nov 2023 19:41:55 -0500
Source: gxmessage
Architecture: source
Version: 3.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 981873 1013738 1049736
Changes:
 gxmessage (3.4.3-2) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Jelmer Vernooij ]
   * Migrate repository from alioth to salsa.
 .
   [ Boyuan Yang ]
   * debian/: Apply wrap-and-sort -abst.
   * Bump debhelper v13, Standards-Version 4.6.2.
   * debian/control: Update homepage. (Closes: #981873)
   * debian/control: Do not depend on install-info. (Closes: #1013738)
   * debian/control: Build-dep on texinfo to avoid double FTBFS.
 (Closes: #1049736)
Checksums-Sha1:
 f158e382782805ce6dc92fd2ca71792ee72836c9 1928 gxmessage_3.4.3-2.dsc
 7d9d7a72e90b3421fd615387bba8e44b931c35ed 275354 gxmessage_3.4.3.orig.tar.gz
 0684e59e425612e43b962f840036231d4a1d5751 4476 gxmessage_3.4.3-2.debian.tar.xz
 9962872c1df1eeb98c494e2c8d09b94d59f7b797 15448 
gxmessage_3.4.3-2_amd64.buildinfo
Checksums-Sha256:
 4515f6dc1d3d2816bc387517b19ec616225eefb1e62060877ef1e5d5f85f7199 1928 
gxmessage_3.4.3-2.dsc
 db4e1655fc58f31e5770a17dfca4e6c89028ad8b2c8e043febc87a0beedeef05 275354 
gxmessage_3.4.3.orig.tar.gz
 82d7bd3d397fcbea80d126cb6ed8fd82ca96831669d4682d8a25ef6512348752 4476 
gxmessage_3.4.3-2.debian.tar.xz
 4f5e1fbf246ceb2698be68cb1fe5be673f7c988b78060040a623a0527ff97c50 15448 
gxmessage_3.4.3-2_amd64.buildinfo
Files:
 91d18e933710d9c2f98568610f950b4d 1928 gnome optional gxmessage_3.4.3-2.dsc
 0e6b5b23ffccc785ff8627485f6b7ce4 275354 gnome optional 
gxmessage_3.4.3.orig.tar.gz
 9da976381059b567fdd220dac1a76f70 4476 gnome optional 
gxmessage_3.4.3-2.debian.tar.xz
 8dc6c32a5fe2382836b3dfbe3f8b6cce 15448 gnome optional 
gxmessage_3.4.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmVpL6AACgkQwpPntGGC
Ws7fKQ//YhAoXiPKs50QARrDCuuMVO0ja3fkmQtgUH4DxjEF9oh2/tDsrwaVyUtk
i3iNn8iFd79iPhpNw7HYoEhsdaNUohMwT5fQKLPV48gw/0O2QrxD06yFn1O2APXi
PpBZwkJxdTrj1m7j0n2FE/w7yvRcCBaZhc9Gs9CSSTonyeWkiHeoDrhZsc6ojqxi
LUrvi/aTs29AtOWq6p+sVMvPPzk+RmqSqeZkKt4fQYAoAV4lfOSY2fMXGMDVxAut
Q53PK4GhxIF6iMsl3jyYIqMIsyELXAEEhE3fVhA1eZyx4eCm9UTn866n3GQEGHN+
sxHAiqbiVJR/yxXcsZc7/j0debpe7ZHMJoui/ZEcvlip5LnY+7I1tymBBrCnmTxS
xysDVwbLiHvc0o6LXNv5zFFN0WtaFFFZgU2t0BN6TptQSqkzRI4uFs8y5dxV48th
tbvNSO/WoN/9j9sULM9OipIHMvtxaQZGCX3cBBYdSGdaR5j45LKqvJaFUmtKXhS4
G1I+aMimHNiFKWgImw6HpQYV1nYhC1cQaWQRuXpZmGu7jmvm8iqwsguKhE+AhGSf
BRk9+7w3xmOBENz04gP63/iwk3BfgJiQY0HmB4OMWW/r/vNc9NRgron9A6YgVKVP
zWFuONFyRF2KSzSyo2Pzvu6FYY0Z9iP+dvwKQ8cKdh8KYamiV/E=
=vW2r
-END PGP SIGNATURE End Message ---

Processing of gxmessage_3.4.3-2_source.changes

2023-11-30 Thread Debian FTP Masters 
gxmessage_3.4.3-2_source.changes uploaded successfully to localhost
along with the files:
  gxmessage_3.4.3-2.dsc
  gxmessage_3.4.3.orig.tar.gz
  gxmessage_3.4.3-2.debian.tar.xz
  gxmessage_3.4.3-2_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

gxmessage_3.4.3-2_source.changes ACCEPTED into unstable

2023-11-30 Thread Debian FTP Masters 
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 30 Nov 2023 19:41:55 -0500
Source: gxmessage
Architecture: source
Version: 3.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 981873 1013738 1049736
Changes:
 gxmessage (3.4.3-2) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Jelmer Vernooij ]
   * Migrate repository from alioth to salsa.
 .
   [ Boyuan Yang ]
   * debian/: Apply wrap-and-sort -abst.
   * Bump debhelper v13, Standards-Version 4.6.2.
   * debian/control: Update homepage. (Closes: #981873)
   * debian/control: Do not depend on install-info. (Closes: #1013738)
   * debian/control: Build-dep on texinfo to avoid double FTBFS.
 (Closes: #1049736)
Checksums-Sha1:
 f158e382782805ce6dc92fd2ca71792ee72836c9 1928 gxmessage_3.4.3-2.dsc
 7d9d7a72e90b3421fd615387bba8e44b931c35ed 275354 gxmessage_3.4.3.orig.tar.gz
 0684e59e425612e43b962f840036231d4a1d5751 4476 gxmessage_3.4.3-2.debian.tar.xz
 9962872c1df1eeb98c494e2c8d09b94d59f7b797 15448 
gxmessage_3.4.3-2_amd64.buildinfo
Checksums-Sha256:
 4515f6dc1d3d2816bc387517b19ec616225eefb1e62060877ef1e5d5f85f7199 1928 
gxmessage_3.4.3-2.dsc
 db4e1655fc58f31e5770a17dfca4e6c89028ad8b2c8e043febc87a0beedeef05 275354 
gxmessage_3.4.3.orig.tar.gz
 82d7bd3d397fcbea80d126cb6ed8fd82ca96831669d4682d8a25ef6512348752 4476 
gxmessage_3.4.3-2.debian.tar.xz
 4f5e1fbf246ceb2698be68cb1fe5be673f7c988b78060040a623a0527ff97c50 15448 
gxmessage_3.4.3-2_amd64.buildinfo
Files:
 91d18e933710d9c2f98568610f950b4d 1928 gnome optional gxmessage_3.4.3-2.dsc
 0e6b5b23ffccc785ff8627485f6b7ce4 275354 gnome optional 
gxmessage_3.4.3.orig.tar.gz
 9da976381059b567fdd220dac1a76f70 4476 gnome optional 
gxmessage_3.4.3-2.debian.tar.xz
 8dc6c32a5fe2382836b3dfbe3f8b6cce 15448 gnome optional 
gxmessage_3.4.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmVpL6AACgkQwpPntGGC
Ws7fKQ//YhAoXiPKs50QARrDCuuMVO0ja3fkmQtgUH4DxjEF9oh2/tDsrwaVyUtk
i3iNn8iFd79iPhpNw7HYoEhsdaNUohMwT5fQKLPV48gw/0O2QrxD06yFn1O2APXi
PpBZwkJxdTrj1m7j0n2FE/w7yvRcCBaZhc9Gs9CSSTonyeWkiHeoDrhZsc6ojqxi
LUrvi/aTs29AtOWq6p+sVMvPPzk+RmqSqeZkKt4fQYAoAV4lfOSY2fMXGMDVxAut
Q53PK4GhxIF6iMsl3jyYIqMIsyELXAEEhE3fVhA1eZyx4eCm9UTn866n3GQEGHN+
sxHAiqbiVJR/yxXcsZc7/j0debpe7ZHMJoui/ZEcvlip5LnY+7I1tymBBrCnmTxS
xysDVwbLiHvc0o6LXNv5zFFN0WtaFFFZgU2t0BN6TptQSqkzRI4uFs8y5dxV48th
tbvNSO/WoN/9j9sULM9OipIHMvtxaQZGCX3cBBYdSGdaR5j45LKqvJaFUmtKXhS4
G1I+aMimHNiFKWgImw6HpQYV1nYhC1cQaWQRuXpZmGu7jmvm8iqwsguKhE+AhGSf
BRk9+7w3xmOBENz04gP63/iwk3BfgJiQY0HmB4OMWW/r/vNc9NRgron9A6YgVKVP
zWFuONFyRF2KSzSyo2Pzvu6FYY0Z9iP+dvwKQ8cKdh8KYamiV/E=
=vW2r
-END PGP SIGNATURE-