Bug#1088867: Removed package(s) from unstable

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

python-cliapp | 1.20180812.1-7 | source
python3-cliapp | 1.20180812.1-7 | all

--- Reason ---
RoQA; obsolete, unmaintained upstream
--

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

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

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

2024-12-11 Thread Debian FTP Masters 
Version: 1.20180812.1-7+rm

Dear submitter,

as the package python-cliapp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088867

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

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:25:53 +
with message-id 
and subject line Bug#1088055: Removed package(s) from unstable
has caused the Debian Bug report #967397,
regarding gimp-gap: depends on deprecated GTK 2
to be marked as done.

This means that you claim that the problem has been 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.)


-- 
967397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gimp-gap
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.6.0+dfsg-9+rm

Dear submitter,

as the package gimp-gap has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088055

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#1088054: marked as done (gimp-gap: Not compatible with gimp 3)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:25:53 +
with message-id 
and subject line Bug#1088055: Removed package(s) from unstable
has caused the Debian Bug report #1088054,
regarding gimp-gap: Not compatible with gimp 3
to be marked as done.

This means that you claim that the problem has been 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.)


-- 
1088054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gimp-gap
Version: 2.6.0+dfsg-9
Severity: serious
Tags: ftbs trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gimp3

The Debian GNOME team intends to upload gimp 3 RC1 to Unstable soon,
for inclusion in the next major stable release of Debian, Debian 13
Trixie.

gimp-gap is only compatible with gimp 2.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Version: 2.6.0+dfsg-9+rm

Dear submitter,

as the package gimp-gap has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088055

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#846323: marked as done (mplayer extraction is broken)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:25:53 +
with message-id 
and subject line Bug#1088055: Removed package(s) from unstable
has caused the Debian Bug report #846323,
regarding mplayer extraction is broken
to be marked as done.

This means that you claim that the problem has been dealt with.
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.)


-- 
846323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimp-gap
Version: 2.6.0+dfsg-5+b1
Severity: important

Dear maintainers,

MPlayer command-line parameters have changed to that mplayer-based extraction
fails with:

-aofile has been removed. Use -ao pcm:file= instead.
-jpeg has been removed. Use -vo jpeg: instead.

It should be fairly easy to patch gimp-gap to use the new interface.

Regards, Thibaut.



-- System Information:
Debian Release: stretch/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages gimp-gap depends on:
ii  gimp 2.8.18-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-7
ii  libcairo21.14.6-1.1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libgimp2.0   2.8.18-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpangoft2-1.0-01.40.3-3
ii  libpng16-16  1.6.26-2
ii  zlib1g   1:1.2.8.dfsg-2+b3

Versions of packages gimp-gap recommends:
ii  mplayer  2:1.3.0-5

gimp-gap suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.6.0+dfsg-9+rm

Dear submitter,

as the package gimp-gap has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088055

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#866224: marked as done (Fwd: gimp-gap 2.6.0 is wrong for gimp 2.8.x)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:25:53 +
with message-id 
and subject line Bug#1088055: Removed package(s) from unstable
has caused the Debian Bug report #866224,
regarding Fwd: gimp-gap 2.6.0 is wrong for gimp 2.8.x
to be marked as done.

This means that you claim that the problem has 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.)


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

Package: gimp-gap

Version: 2.6.0+dfsg-5+b2

from

https://bugzilla.gnome.org/show_bug.cgi?id=749290

Note that the GIT master was still compatible with the older GIMP-2.6.x 
releases

until 2015.05.14, but since this date it has been updated to the level of
the gap-2-8 branch.
Note that GIT master is now intended for further updates
to follow GIMP-2.9.x and later API changes.




Now Now master and 2.8 gimp-gap branches are the same.

gimp-gap 2.6.0 is broken in many functions with gimp 2.8.xx




Regards


--- End Message ---
--- Begin Message ---
Version: 2.6.0+dfsg-9+rm

Dear submitter,

as the package gimp-gap has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088055

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#677115: marked as done (per-subcommand config file sections)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id 
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #677115,
regarding per-subcommand config file sections
to be marked as done.

This means that you claim that the problem has been dealt 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.)


-- 
677115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cliapp
Version: 0.29-1
Severity: wishlist

Hello,

I'm hitting a limit in the default "command line options in config file"
behaviour: I have a "--output" option that sends the command output to a
file instead of stdout.

I'd like to set a config file option to avoid typing this command:

  egt backup --output="/var/backups/egt-%Y-%m-%d-%H:%M:%S.tar"

but I still want this command to send output to stdout:

  egt weekly-report


A possible implementation would be allowing a per-subcommand section in
the config file, like this:

  [cmd backup]
  output = "/var/backups/egt-%Y-%m-%d-%H:%M:%S.tar"

the section being ignored unless the given subcommand is being run.

I didn't suggest to just use [backup] for the section name, because
that would be ambiguous if one implemented a 'config' subcommand.
However, 'cmd ' looks rather ugly, and just the subcommand name would
feel much more natural. An alternative, backwards-compatible strategy
could be to also accept something like "[DEFAULTS]" for the main
section, and if the main section is named that way then 'config' is not
treated specially and can be used for subcommands.

Unfortunately ConfigParser won't parse a config file with data outside
of any section header: that would have been a perfect solution to the
ambiguity.

However, it does accept "[ ]" (must have a space) as a section header.
It's another option, but still not so natural.


Ciao,

Enrico

-- 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/4 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 python-cliapp depends on:
ii  python 2.7.2-10
ii  python2.6  2.6.7-4
ii  python2.7  2.7.3~rc2-2.1

python-cliapp recommends no packages.

Versions of packages python-cliapp suggests:
ii  libjs-query   
ii  libjs-underscore  1.1.6-1

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.20180812.1-7+rm

Dear submitter,

as the package python-cliapp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088867

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#655091: marked as done (--dump-memory-profile should log at info level)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id 
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #655091,
regarding --dump-memory-profile should log at info level
to be marked as done.

This means that you claim that the problem has 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.)


-- 
655091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obnam
Version: 0.24.1-1
Severity: wishlist

Since the default is to log memory profiles at debug level. Specifying
the option explicitly should log it even if the log-level is below debug.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-486
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 obnam depends on:
ii  libc6 2.13-24
ii  python2.7.2-9
ii  python-cliapp 0.23-1
ii  python-larch  0.26-1
ii  python-paramiko   1.7.7.1-2
ii  python-tracing0.6-2
ii  python-ttystatus  0.15-1
ii  python2.6 2.6.7-4
ii  python2.7 2.7.2-8

obnam recommends no packages.

obnam suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.20180812.1-7+rm

Dear submitter,

as the package python-cliapp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088867

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#756405: marked as done (obnam: '$obnam help ls' shows a traceback)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id 
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #756405,
regarding obnam: '$obnam help ls' shows a traceback
to be marked as done.

This means that you claim that the problem has been 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.)


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

# obnam help ls
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 190, in _run
self.process_args(args)
  File "/usr/lib/python2.7/dist-packages/obnamlib/app.py", line 201, in
process_args
cliapp.Application.process_args(self, args)
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 568, in
process_args
method(args[1:])
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 316, in help
self._help_helper(args, False)
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 302, in
_help_helper
fmt = self.get_help_text_formatter(width=width)
AttributeError: 'App' object has no attribute 'get_help_text_formatter'



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 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 obnam depends on:
ii  libc6 2.19-7
ii  python2.7.8-1
ii  python-cliapp 1.20140315-1
ii  python-fuse   2:0.2.1-9
ii  python-larch  1.20131130-1
ii  python-paramiko   1.14.0-2
ii  python-tracing0.8-1
ii  python-ttystatus  0.23-1

obnam recommends no packages.

obnam suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 1.20180812.1-7+rm

Dear submitter,

as the package python-cliapp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088867

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#950700: marked as done (RFS: python-cliapp/1.20180812.1-4 [ITA] -- Python framework for Unix command line programs)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id 
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #950700,
regarding RFS: python-cliapp/1.20180812.1-4 [ITA] -- Python framework for Unix 
command line programs
to be marked as done.

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


-- 
950700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cliapp
Version: 1.20180812.1-4
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-cliapp"

 * Package name: python-cliapp
   Version : 1.20180812.1-4
   Upstream Author : Lars Wirzenius 
 * URL : http://liw.fi/cliapp/
 * License : GPL-2+
 * Vcs : None
   Section : python

It builds those binary packages:

  python3-cliapp - Python framework for Unix command line programs

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/python-cliapp

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-cliapp/python-cliapp_1.20180812.1-4.dsc

Changes since the last upload:

   * New maintainer. (Closes: #914028)
   * debian/control:
 - Bumped Standard-Version to 4.5.1.
 - Setting new manteiner
   * debian/rules:
 - Fixed override dh_auto_test.

Regards,

--
  jair reis
--- End Message ---
--- Begin Message ---
Version: 1.20180812.1-7+rm

Dear submitter,

as the package python-cliapp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088867

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#1080900: marked as done (Missing Build-Depends on python3-setuptools)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id 
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #1080900,
regarding Missing Build-Depends on python3-setuptools
to be marked as done.

This means that you claim that the problem has 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.)


-- 
1080900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cliapp
Version: 1.20180812.1-6
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: dh-python-no-setuptools
Tags: sid, trixie

This package failed build from source when test-built against a version of
dh-python without a python3-setuptools dependency.

distutils is no longer part of the Python standard library, since 3.12. But a
minimal version of it becomes available when the python3-setuptools package is
installed.

Please add a Build-Depends on python3-setuptools to your package, or migrate
the package's build system away from setuptools/distutils.

If you run into any difficulties, please raise them on
debian-pyt...@lists.debian.org.

This bug has been filed at "important" severity, as the change hasn't been
made in dh-python yet, but this may be raised to RC before the trixie release.

Thanks,

Stefano
--- End Message ---
--- Begin Message ---
Version: 1.20180812.1-7+rm

Dear submitter,

as the package python-cliapp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088867

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#681866: marked as done (manpage error regarding -r option)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id 
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #681866,
regarding manpage error regarding -r option
to be marked as done.

This means that you claim that the problem has been dealt 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.)


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

Hi,

obnam manpage contains the following bit in synopsis:

   [-r=REPOSITORY]
 
The equal sign however works only with *long* commandline options
like [--repository=REPOSITORY], resulting in:

  % obnam -r=/var/tmp/obnam-test/ backup ponnies
  00h00m00s 1 files; 0 B (0 B/s) setting upERROR: =/var/tmp/obnam-test: No such 
file or directory

without the equal sign everything works as expected:

  % obnam -r /var/tmp/obnam-test/ backup ponnies
  Backed up 10 files, uploaded 14.6 MiB in 1s at 16.4 MiB/s average speed

Cheers
-- 
Miroslav Kure
--- End Message ---
--- Begin Message ---
Version: 1.20180812.1-7+rm

Dear submitter,

as the package python-cliapp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088867

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#676935: marked as done (please implement a debug=True setting)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 18:28:11 +
with message-id 
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #676935,
regarding please implement a debug=True setting
to be marked as done.

This means that you claim that the problem has been 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.)


-- 
676935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cliapp
Version: 0.29-1
Severity: wishlist

Hello,

I'm using cliapp for rapidly prototyping a new tool, and I find it
inconvenient that IOErrors are reported without a backtrace. Although I
understand that would be the right behaviour once the tool is ready for
prime time.

Django has a 'DEBUG=True' setting in its config, which you disable when
you put the code into production. It's used to switch default behaviour
from "what the developer would expect" to "what the user would expect".

Since cliapp is excellent to speed up development of new tools, a
debug=True switch, say, in Application's constructor, or tied to a
--debug commandline option that would also set the appropriate loglevel,
sounds like a very good idea.


Ciao,

Enrico


-- 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/4 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 python-cliapp depends on:
ii  python 2.7.2-10
ii  python2.6  2.6.7-4
ii  python2.7  2.7.3~rc2-2.1

python-cliapp recommends no packages.

Versions of packages python-cliapp suggests:
ii  libjs-query   
ii  libjs-underscore  1.1.6-1

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.20180812.1-7+rm

Dear submitter,

as the package python-cliapp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088867

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

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

  gimp-gap | 2.6.0+dfsg-9 | source, amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, riscv64, s390x

--- Reason ---
RoQA; not compatible with gimp 3
--

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

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

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

2024-12-11 Thread Debian FTP Masters 
Version: 2.6.0+dfsg-9+rm

Dear submitter,

as the package gimp-gap has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088055

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)

xmms2_0.8+dfsg-28_source.changes ACCEPTED into unstable

2024-12-11 Thread Debian FTP Masters 
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 11 Dec 2024 22:25:55 +
Source: xmms2
Architecture: source
Version: 0.8+dfsg-28
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1087580
Changes:
 xmms2 (0.8+dfsg-28) unstable; urgency=medium
 .
   * QA upload
   * d/copyright: Convert to machine-readable format
   * Fix lintian date warning
   * Drop python3-xmmsclient (Closes: #1087580)
Checksums-Sha1:
 e82309d91b6b386744c356c13f2a81f3e5d77711 6581 xmms2_0.8+dfsg-28.dsc
 5ec28cd7f23ac2d4e67e4ea08c9417bffd68f695 174792 xmms2_0.8+dfsg-28.debian.tar.xz
 b9fd907de38e07431dde7f96758e96f9f77506a8 19185 
xmms2_0.8+dfsg-28_source.buildinfo
Checksums-Sha256:
 c5e715fc0a037dd2b7c0e007cc118c5363d0b51b5f79b3112d59560c69d55e3a 6581 
xmms2_0.8+dfsg-28.dsc
 b6fe96a2dd10150da4c409c9f6f66bace885594e60c516ce923e684972f7 174792 
xmms2_0.8+dfsg-28.debian.tar.xz
 b18936a9376b20f99185f4f62fa485dd3df7f7f54a95f4a097ac09428306d90e 19185 
xmms2_0.8+dfsg-28_source.buildinfo
Files:
 3ac7cb5db9bbb2d533a2419fc79e4c9e 6581 sound optional xmms2_0.8+dfsg-28.dsc
 68f38e895aae7453854a6a3c4a970fc4 174792 sound optional 
xmms2_0.8+dfsg-28.debian.tar.xz
 6e19ff3c47509095377f4fe91d18c5b3 19185 sound optional 
xmms2_0.8+dfsg-28_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmdaEiMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFKUXDACbJRwW7vwCzeKbWFMP0p2TmRD1otwEG6ON
DQX2v8Gej9kDMqDx1f9yXJUJPgfDvD+A5hzVdLP+LkfHBeQeO+y5CS8i79ockEfr
gMaAz+FLNL4Ud3r/d6JSu+PejU8iPTW7GmcSHaU3CsXyDImyEp5vHZQusb1TPFHR
v2300Rbsk4VcPDz6FO0DVngcu2nqbalbXADB64cZkKbWYUW83sSWX3DGwWsV66Bu
CfHl6pvXpE3s2BRmnfK/HoAtdxGSxxm5uQNS9etH/ERAqU+/7Py9bGY+8x+S7pyA
4huGoMJAQqc2tKq27KhFW+XaEb0YD0IP/3owJI9yrHluGqUA1P5bEyOGLKYp5cAp
ke7KwtElhMvvlrSQaIMTtj8hJBioWyZU4mbWqlPtNiqr6PgOiphLVd2KSFTmdvtM
3iy+oeVSxOiXc1m7eZJGwd3ef6po3WWDN7qScnoktS+nbmPU7KQlELyPA/jZoasi
VUvVKgTFJx68NMz6+lZVYfcPeZAZk3M=
=PaoB
-END PGP SIGNATURE-



pgpaDytwwQzVs.pgp
Description: PGP signature

Processing of xmms2_0.8+dfsg-28_source.changes

2024-12-11 Thread Debian FTP Masters 
xmms2_0.8+dfsg-28_source.changes uploaded successfully to localhost
along with the files:
  xmms2_0.8+dfsg-28.dsc
  xmms2_0.8+dfsg-28.debian.tar.xz
  xmms2_0.8+dfsg-28_source.buildinfo

Greetings,

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

Bug#1087580: marked as done (Build-Depends on the obsolete cython3-legacy)

2024-12-11 Thread Debian Bug Tracking System 
Your message dated Wed, 11 Dec 2024 22:52:51 +
with message-id 
and subject line Bug#1087580: fixed in xmms2 0.8+dfsg-28
has caused the Debian Bug report #1087580,
regarding Build-Depends on the obsolete cython3-legacy
to be marked as done.

This means that you claim that the problem has been 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.)


-- 
1087580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmms2
Version: 0.8+dfsg-27
Severity: serious

The package FTBFS with modern cython so in #1056894 it was temporarily switched
to cython3-legacy a year ago. The time is now up and as cython3-legacy won't be
in trixie, xmms2 won't be in trixie either unless someone ports it or, if
that's possible, builds it without cython (e.g. if it's only needed for Python
bindings it makes sense to drop those).

https://github.com/xmms2/xmms2-devel/commit/80ac6585ad914ff6b2f63f7bf3e8e2eebbc697cc
probably fixes the problem but I have no idea if it can be applied to the
packaged long-dead stable version.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.10.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: xmms2
Source-Version: 0.8+dfsg-28
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
xmms2, 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 1087...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated xmms2 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: Wed, 11 Dec 2024 22:25:55 +
Source: xmms2
Architecture: source
Version: 0.8+dfsg-28
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1087580
Changes:
 xmms2 (0.8+dfsg-28) unstable; urgency=medium
 .
   * QA upload
   * d/copyright: Convert to machine-readable format
   * Fix lintian date warning
   * Drop python3-xmmsclient (Closes: #1087580)
Checksums-Sha1:
 e82309d91b6b386744c356c13f2a81f3e5d77711 6581 xmms2_0.8+dfsg-28.dsc
 5ec28cd7f23ac2d4e67e4ea08c9417bffd68f695 174792 xmms2_0.8+dfsg-28.debian.tar.xz
 b9fd907de38e07431dde7f96758e96f9f77506a8 19185 
xmms2_0.8+dfsg-28_source.buildinfo
Checksums-Sha256:
 c5e715fc0a037dd2b7c0e007cc118c5363d0b51b5f79b3112d59560c69d55e3a 6581 
xmms2_0.8+dfsg-28.dsc
 b6fe96a2dd10150da4c409c9f6f66bace885594e60c516ce923e684972f7 174792 
xmms2_0.8+dfsg-28.debian.tar.xz
 b18936a9376b20f99185f4f62fa485dd3df7f7f54a95f4a097ac09428306d90e 19185 
xmms2_0.8+dfsg-28_source.buildinfo
Files:
 3ac7cb5db9bbb2d533a2419fc79e4c9e 6581 sound optional xmms2_0.8+dfsg-28.dsc
 68f38e895aae7453854a6a3c4a970fc4 174792 sound optional 
xmms2_0.8+dfsg-28.debian.tar.xz
 6e19ff3c47509095377f4fe91d18c5b3 19185 sound optional 
xmms2_0.8+dfsg-28_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmdaEiMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFKUXDACbJRwW7vwCzeKbWFMP0p2TmRD1otwEG6ON
DQX2v8Gej9kDMqDx1f9yXJUJPgfDvD+A5hzVdLP+LkfHBeQeO+y5CS8i79ockEfr
gMaAz+FLNL4Ud3r/d6JSu+PejU8iPTW7GmcSHaU3CsXyDImyEp5vHZQusb1TPFHR
v2300Rbsk4VcPDz6FO0DVngcu2nqbalbXADB64cZkKbWYUW83sSWX3DGwWsV66Bu
CfHl6pvXpE3s2BRmnfK/HoAtdxGSxxm5uQNS9etH/ERAqU+/7Py9bGY+8x+S7pyA
4huGoMJAQqc2tKq27KhFW+XaEb0YD0IP/3owJI9yrHluGqUA1P5bEyOGLKYp5cAp
ke7KwtElhMvvlrSQaIMTtj8hJBioWyZU4mbWqlPtNiqr6PgOiphLVd2KSFTmdvtM
3iy+oeVSxOiXc1m7eZJGwd3ef6po3WWDN7qScnoktS+nbmPU7KQlELyPA/jZoasi
VUvVKgTFJx68NMz6+lZVYfcPeZAZk3M=
=PaoB
-END PGP SIGNATURE-



pgpUra_u95PQR.pgp
Description: PGP signature
--- End Message ---

The Impact of a Missing Key Ingredient in Our Lives

2024-12-11 Thread James 
Do me a favor and think about this for one minute. What you are
doing right now is producing a result. That result is your reality.
Not something you picture in your imagination.
Question? Have you been experiencing the same results day after day
year after year? Have you settled and feel trapped in this experience?
Did you know being trapped is only temporary?
Would you be open to a new experience an experience that would give
you your true purpose in life? The link below will take you to a
complimentary guide that will reveal a key ingredient that most people
never have experienced.

Your Life Your Choice

   

 You have what is called personal potential. This is something no one
can take from you and directly associated with your personal potential
are talents and capabilities.

Question? Are you experiencing your personal potential as a reality or
is it imaginary?

Did you know there is a common element that slows down and stops your
personal potential?

We have a complimentary guide coming out at the end of this year and
if you would like a copy please fill out and submit the following
form.

Personal Potential Form
[https://directmailrelay.com/index.php/campaigns/mb369r9tx4779/track-url/xk30299qon4c3/75d26a6e4f06da22f32d649baf3c6950a77a16ed]

Worldwide thinking men and women alike feel that a major event will
soon take place in the world we live in. What is surprising to most is
this event is not a secret. It just happens to be unknown to many.

Question? Would you like to be prepared for this event or have hit you
as an overwhelming surprise?

The below link will take you to a complimentary guide that will inform
you of this coming event. It does not surprise many that the United
States plays a role in this event, what does surprise everyone is the
other Nation.
One World in Turmoil
[https://directmailrelay.com/index.php/campaigns/mb369r9tx4779/track-url/xk30299qon4c3/2ca26753356af73a9aaed47285fe1c4f3485a023]

  


https://directmailrelay.com/index.php/lists/xq24799y821fc/unsubscribe/xk30299qon4c3/mb369r9tx4779