Bug#946270: xpdf: can't search for various Unicode characters

2019-12-06 Thread Vincent Lefevre 
Package: xpdf
Version: 3.04-13
Severity: normal

It is not possible to search for various Unicode characters.
The concerned characters seem to be the ones that are not in
ISO-8859-1 (even though I use UTF-8 locales), such as €, δ, →.
The "Find" dialogue box does not accept such characters, either
via the keyboard or via copy-paste.

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

Kernel: Linux 5.3.0-2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xpdf depends on:
ii  libc6 2.29-3
ii  libgcc1   1:9.2.1-21
ii  libpaper1 1.1.28+b1
ii  libpoppler82  0.71.0-6
ii  libstdc++69.2.1-21
ii  libx11-6  2:1.6.8-1
ii  libxm42.3.8-2
ii  libxt61:1.1.5-1+b3

Versions of packages xpdf recommends:
ii  cups-bsd2.3.0-7
ii  gsfonts-x11 0.27
ii  poppler-data0.4.9-2
ii  poppler-utils   0.71.0-6
ii  sensible-utils  0.0.12+nmu1

xpdf suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#946276: mark docbook-website Multi-Arch: foreign

2019-12-06 Thread Helmut Grohne 
Package: docbook-website
Version: 2.5.0.0-8
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:libzeep

libzeep fails to satisfy its cross Build-Depends, because its dependency
on docbook-website is not satisfiable. In general, Architecture: all
packages can never satisfy cross Build-Depends unless marked Multi-Arch:
foreign or annotated :native. In this case, the multiarch hinter does
not suggest the Multi-Arch: foreign marking, because docbook-website has
maintainer scripts. I checked the maintainer scripts to be architecture
agnostic. Many other docbook stylesheet packages are already thus
marked. Please consider applying the attached patch.

Helmut
diff -u docbook-website-2.5.0.0/debian/changelog 
docbook-website-2.5.0.0/debian/changelog
--- docbook-website-2.5.0.0/debian/changelog
+++ docbook-website-2.5.0.0/debian/changelog
@@ -1,3 +1,9 @@
+docbook-website (2.5.0.0-9) UNRELEASED; urgency=medium
+
+  * Mark docbook-website Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 06 Dec 2019 06:11:52 +0100
+
 docbook-website (2.5.0.0-8) unstable; urgency=low
 
   * QA upload.
diff -u docbook-website-2.5.0.0/debian/control 
docbook-website-2.5.0.0/debian/control
--- docbook-website-2.5.0.0/debian/control
+++ docbook-website-2.5.0.0/debian/control
@@ -9,6 +9,7 @@
 
 Package: docbook-website
 Architecture: all
+Multi-Arch: foreign
 Replaces: docbook-xml-website
 Depends: ${misc:Depends}, docbook-xml (>= 4.2-7), docbook-xsl
 Conflicts: docbook-xml-website

Processed: mark docbook-website Multi-Arch: foreign

2019-12-06 Thread Debian Bug Tracking System 
Processing control commands:

> affects -1 + src:libzeep
Bug #946276 [docbook-website] mark docbook-website Multi-Arch: foreign
Added indication that 946276 affects src:libzeep

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

Processed: Re: Bug#840782 closed by Hideki Yamane (Bug#840782: fixed in fontforge 1:20190801~dfsg-1)

2019-12-06 Thread Debian Bug Tracking System 
Processing control commands:

> reopen -1
Bug #840782 {Done: Hideki Yamane } [gnulib] gnulib: please 
demote unnecessary dependencies to recommends
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions fontforge/1:20190801~dfsg-1.
> affects -1 - src:fontforge
Bug #840782 [gnulib] gnulib: please demote unnecessary dependencies to 
recommends
Removed indication that 840782 affects src:fontforge

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

Bug#840782: closed by Hideki Yamane (Bug#840782: fixed in fontforge 1:20190801~dfsg-1)

2019-12-06 Thread Helmut Grohne 
Control: reopen -1
Control: affects -1 - src:fontforge

On Sat, Nov 09, 2019 at 07:03:03PM +, Debian Bug Tracking System wrote:
> Changes:
>  fontforge (1:20190801~dfsg-1) experimental; urgency=medium
>  .
>* New upstream version 20190801~dfsg (Closes: #866690, #912062)
>* debian/control{,.in}
>  - remove Christian Perrier  from Uploaders
>(Closes: #894873, #927590)
>  - add Rules-Requires-Root: no
>  - bump up libfontforge3 from 2
>  - migrate to python3 (Closes: #936538)
>  - set Multi-Arch: foreign for -common,doc
>  - drop gnulib (Closes: #840782)

While your change to fontforge is gnulib-related. The bug you closed is
with gnulib, not fontforge. It no longer affects fontforge, but it's
still there.

Helmut

Bug#782592: marked as done (volti: support for XF86_AudioMicMute key)

2019-12-06 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Dec 2019 07:35:44 +
with message-id 
and subject line Bug#945946: Removed package(s) from unstable
has caused the Debian Bug report #782592,
regarding volti: support for XF86_AudioMicMute key
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.)


-- 
782592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: volti
Version: 0.2.3-5
Severity: wishlist

Hi,

my laptop has a “mute” key but also a “mic mute” key. The Mute key is
correctly supported by volti (when using the Xlib backend), but MicMute
isn't. It'd be nice to support the XF86AudioMicMute key as well.

Regards,
-- 
Yves-Alexis

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (450, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages volti depends on:
ii  python2.7.9-1
ii  python-alsaaudio  0.7-1
ii  python-dbus   1.2.0-2+b3
ii  python-gobject3.14.0-1
ii  python-gtk2   2.24.0-4
ii  python-xlib   0.14+20091101-1

volti recommends no packages.

volti suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.2.3-7+rm

Dear submitter,

as the package volti 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/945946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#786728: marked as done (volti: unmute does not work in pulseaudio)

2019-12-06 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Dec 2019 07:35:44 +
with message-id 
and subject line Bug#945946: Removed package(s) from unstable
has caused the Debian Bug report #786728,
regarding volti: unmute does not work in pulseaudio
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.)


-- 
786728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: volti
Version: 0.2.3-5
Severity: normal

Dear Maintainer,

I find that when I mute volti, it mutes both the volume in the Playback
menu of pavucontrol, as well as the stream in the "Output" menu of
pavucontrol. But when I click ummute, only the stream in the Playback
menu is being unmuted, while I have to unmute the stream in the Output
menu manually.


Kind regards,
--Toni++


-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages volti depends on:
ii  python2.7.9-1
ii  python-alsaaudio  0.7-1
ii  python-dbus   1.2.0-2+b3
ii  python-gobject3.14.0-1
ii  python-gtk2   2.24.0-4
ii  python-xlib   0.14+20091101-1

volti recommends no packages.

volti suggests no packages.

-- no debconf information
-- 
Mit freundlichen Gruessen / Kind regards / 祝好,
 
Toni Mueller.

Dipl.-Inf.

Oeko.neT Mueller & Brandt GbR   fon +49 2241 1488440
http://www.oeko.net TM28-RIPEAS29394

Software Development in Python (Plone, Pyramid, Django), IT Security,
Linux, OpenBSD, Hosting, Unix Systems Administration, Consulting
GPG: 4096R/96563E79 B213:F65C:0C8D:B6F9:9434::E92B:9428:82D6:9656:3E79
--- End Message ---
--- Begin Message ---
Version: 0.2.3-7+rm

Dear submitter,

as the package volti 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/945946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#684928: marked as done (volti: volume level numerical values differ from the ones shown by alsamixer)

2019-12-06 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Dec 2019 07:35:44 +
with message-id 
and subject line Bug#945946: Removed package(s) from unstable
has caused the Debian Bug report #684928,
regarding volti: volume level numerical values differ from the ones shown by 
alsamixer
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.)


-- 
684928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: volti
Version: 0.2.3-4
Severity: normal

Hello and thanks for maintaining Volti in Debian!

I've just installed this package and I'm giving it a try.

I noticed that the internal mixer shows volume level numerical values
that differ from the ones shown by alsamixer.
I think that this is very confusing, especially if one plans to use
alsamixer in some circumstances and volti in other ones.

I found out that there's a configuration option to disable the internal
mixer and use an external one: I chose to use alsamixer as external
mixer and thought I could be happy with this setting.

Unfortunately the channel that is controlled by the slider that is
obtained by left-clicking on the volti icon in the systray is affected
by the same issue!  :-(
Hence, if this slider controls the master channel, I may see that volti
claims its volume level is 95, while alsamixer says that the Master
level is 88. Changing this level from either volti or alsamixer modifies
both numbers, but they are never equal to each other!
Again, I think this is very confusing.

Please fix this bug and/or forward my bug report upstream, as
appropriate.

Thanks for your time.


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

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

Versions of packages volti depends on:
ii  python2.7.3~rc2-1
ii  python-alsaaudio  0.5+svn36-1+b2
ii  python-dbus   1.1.1-1
ii  python-gobject3.2.2-1
ii  python-gtk2   2.24.0-3
ii  python-xlib   0.14+20091101-1

volti recommends no packages.

volti suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.2.3-7+rm

Dear submitter,

as the package volti 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/945946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#890177: marked as done (volti: Please switch to python-gobject-2/python-gi)

2019-12-06 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Dec 2019 07:35:44 +
with message-id 
and subject line Bug#945946: Removed package(s) from unstable
has caused the Debian Bug report #890177,
regarding volti: Please switch to python-gobject-2/python-gi
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.)


-- 
890177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: volti
Version: 0.2.3-7
Severity: important
Tags: buster sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: pygobject-trans-rm

Dear Maintainer,

Your package volti depends against the python-gobject transitional
package.

We would like to drop this transitional package for buster.

Could you please switch to either python-gobject-2 (if your package
is using the old python binding for GObject) or to python-gi (if your
package is using the new gobject-introspection one).

Please don't hesitate to contact me if you have any questions.

Kind Regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Version: 0.2.3-7+rm

Dear submitter,

as the package volti 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/945946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#838430: marked as done (volti: traceback on startup)

2019-12-06 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Dec 2019 07:35:44 +
with message-id 
and subject line Bug#945946: Removed package(s) from unstable
has caused the Debian Bug report #838430,
regarding volti: traceback on startup
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
838430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: volti
Version: 0.2.3-7
Severity: important

Dear Maintainer,

I can't use volti because everytime I try to start it, it crashes:

$ volti
[alsactrl.py:__init__:41] can't open Master control for card HDMI,
trying to select first available mixer channel

[alsactrl.py:__init__:49] can't open first available control for card
HDMI
error: list index out of range
Traceback (most recent call last):
  File "/usr/bin/volti", line 52, in 
volti = main.VolumeTray()
  File "/usr/lib/volti/volti/main.py", line 124, in __init__
self.watchid = gobject.io_add_watch(fd, eventmask, self.update)
TypeError: an integer is required
$ 

This happens on a Dell Latitude E7440, which I have installed with
Jessie and then immediately upgraded to Stretch.


Cheers,
Toni



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

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

Versions of packages volti depends on:
ii  python-alsaaudio  0.7-1
ii  python-dbus   1.2.4-1
ii  python-gobject3.21.92-1
ii  python-gtk2   2.24.0-5
ii  python-xlib   0.14+20091101-5
pn  python:any

volti recommends no packages.

volti suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.2.3-7+rm

Dear submitter,

as the package volti 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/945946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#782748: marked as done (volti crashes and dosnt start again if soundcard removed)

2019-12-06 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Dec 2019 07:35:44 +
with message-id 
and subject line Bug#945946: Removed package(s) from unstable
has caused the Debian Bug report #782748,
regarding volti crashes and dosnt start again if soundcard removed
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.)


-- 
782748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: volti
Version: 0.2.3-5
Severity: important

Dear Maintainer,

i am using volti togehter with the lxde desktop to be able to control my volume 
through my mediakeys on my thinkpad (maybe there is also a better solution but 
i found out this for me because the lxde desktop env dosnt provide a volume 
mixing gsystem (like gnome2/mate dose) by defalut...

   * What led up to the situation?
i have changed the soundcard to another external to control this by the media 
keys on my thinkpad
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
some time later, i was on the go and volti wasnt working anymore. i tryed to do 
it in terminal to find out what was happening
   * What was the outcome of this action?
treaki@hostname:~$ volti
[alsactrl.py:__init__:41] can't open Master control for card ThinkPadEC, trying 
to select first available mixer channel

[alsactrl.py:__init__:49] can't open first available control for card ThinkPadEC
error: list index out of range
Xlib.protocol.request.QueryExtension
Traceback (most recent call last):
  File "/usr/bin/volti", line 53, in 
volti = main.VolumeTray()
  File "/usr/lib/volti/volti/main.py", line 124, in __init__
self.watchid = gobject.io_add_watch(fd, eventmask, self.update)
TypeError: an integer is required 
treaki@hostname:~$ cd .config/volti/
treaki@hostname:~/.config/volti$ ls
config
treaki@hostname:~/.config/volti$ mv config config1
treaki@hostname:~/.config/volti$ volti
   * What outcome did you expect instead?
that volti had an workaround about removed sondcards so that i dont need to 
trash and redo my whole configuration. Also i would apprichiate 
pulseaudiosupport and a more reliable codebase (sometimes volti dosnt survices 
a suspend to ram and is using up 99% of my cpu)


i hope this problems can be fixed

thanks in advance and keep up the good work with tebian

greetingds treaki


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages volti depends on:
ii  libdmtx-python [python]  20140917-1
ii  python   2.7.8-2
ii  python-alsaaudio 0.7-1
ii  python-dbus  1.2.0-2+b3
ii  python-gobject   3.14.0-1
ii  python-gtk2  2.24.0-4
ii  python-xlib  0.14+20091101-1

volti recommends no packages.

volti suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.2.3-7+rm

Dear submitter,

as the package volti 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/945946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#938799: marked as done (volti: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Dec 2019 07:35:44 +
with message-id 
and subject line Bug#945946: Removed package(s) from unstable
has caused the Debian Bug report #938799,
regarding volti: Python2 removal in sid/bullseye
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.)


-- 
938799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:volti
Version: 0.2.3-7
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:volti

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.2.3-7+rm

Dear submitter,

as the package volti 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/945946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#941877: marked as done (volti: Depends on unmaintained pygtk)

2019-12-06 Thread Debian Bug Tracking System 
Your message dated Sat, 07 Dec 2019 07:35:44 +
with message-id 
and subject line Bug#945946: Removed package(s) from unstable
has caused the Debian Bug report #941877,
regarding volti: Depends on unmaintained pygtk
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.)


-- 
941877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: volti
Version:  0.2.3-7
Severity: serious
Control: block 885135 by -1
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid bullseye

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011. Also, it uses Python2 and Python2 is being removed
from Debian.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Debian 11 "Bullseye" release as
we're going to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.2.3-7+rm

Dear submitter,

as the package volti 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/945946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#945946: Removed package(s) from unstable

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

 volti |0.2.3-7 | source, all

--- Reason ---
RoQA; unmaintained Python2 package
--

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)