Bug#1061511: gedit-source-code-browser-plugin: Upstream unmaintained for over a decade

2024-01-27 Thread Pietro Battiston 
Il giorno sab, 27/01/2024 alle 13.55 +0600, Ildar Mulyukov ha scritto:
> This shows the python exceptions:
> > G_MESSAGES_DEBUG=all gedit
> I did a couple of steps with it and found it's no more one line fix,
> unfortunately.
> 

I'm still using Gedit 44, I will try to investigate as soon as I have a
46 to test.

Pietro

Bug#1061511: gedit-source-code-browser-plugin: Upstream unmaintained for over a decade

2024-01-25 Thread Pietro Battiston 
Dear Kip,

thanks for your mail and references. I have asked ildar, in the bug you
referred to, additional details on what broke in the last Gedit
versions. If anybody is able to fix his fork, or produce another one
and make some minimal commitment to update it (or accept contributions
for it) over time, I will be happy to switch the Debian package to it.

The best thing would clearly be having an up to date fork owned by a
project, rather than an individual who (legitimately) writes "I
personally don't plan to maintain this regularly". I would be happy to
be in such a project and occasionally contribute - while I would not
want to simply package my personal fork.

Pietro

Bug#1000731: Program fails to start

2021-11-27 Thread Pietro Battiston 
Hi Osamu,

thanks for your analysis.

nautilus-scripts-manager was never meant to be more than a GUI to
handle these links in a comfortable way (with the possible benefit of
proposing localized names if the script provides them).
This is stated quite clearly in the project web page:
http://www.pietrobattiston.it/nautilus-scripts-manager
I myself used this package when I was a nautilus user, but I changed my
default file manager some time ago.

So is it an essential package? Definitely not. Is it well maintained?
Probably not. But the program works regularly in bullseye; apparently
something changed in bookworm and I have to understand what. The fact
that it didn't get new commits since 2014 is unrelated to the issue you
are experiencing.

In short: if we decide to keep this package, making it work in bookworm
should be a one liner, as the problematic line's aim is just to test if
there is an active graphic user session. By the way: I guess you are
running the program inside a graphic session?

If we decide to drop this package, I don't expect too much user
desperation either ;-) (mainly because of the low popcon)

Cheers,

Pietro

Il giorno dom, 28/11/2021 alle 14.03 +0900, Osamu Aoki ha scritto:
> Package: nautilus-scripts-manager
> Version: 2.0-1.1
> Severity: important
> X-Debbugs-Cc: Pietro Battiston , Piotr
> Ożarowski , Ondřej Nový 
> 
> Hi,
> 
> As I try to start nautilus-scripts-manager, it doesn't start
> 
> $ nautilus-scripts-manager
> /usr/bin/nautilus-scripts-manager:21: PyGIWarning: Pango was imported
> without specifying a version first. Use gi.require_version('Pango',
> '1.0') before import to ensure that the right version gets loaded.
>   from gi.repository import Pango, Gtk, GLib
> /usr/bin/nautilus-scripts-manager:21: PyGIWarning: Gtk was imported
> without specifying a version first. Use gi.require_version('Gtk',
> '4.0') before import to ensure that the right version gets loaded.
>   from gi.repository import Pango, Gtk, GLib
> Traceback (most recent call last):
>   File "/usr/bin/nautilus-scripts-manager", line 97, in 
>     s = Gdk.Screen.get_default()
>   File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py",
> line 32, in __getattr__
>     return getattr(self._introspection_module, name)
>   File "/usr/lib/python3/dist-packages/gi/module.py", line 123, in
> __getattr__
>     raise AttributeError("%r object has no attribute %r" % (
> AttributeError: 'gi.repository.Gdk' object has no attribute 'Screen'
> 
> 
> This package is not usable for the main purpose via GUI. (If we were
> to use command-line, we can do it via "ln -s" anyway.  I suppose
> those
> CLI are there for test purpose.)
> 
> I found a salsa repository which seems to be most current and updated
> some there.
>   https://salsa.debian.org/debian/nautilus-scripts-manager
> 
> After making some housekeeping and a few commits, I realized the
> nautilus script itself can be created and used independent of this
> package and there is no Debian package using this program to manage
> their nautilus scripts any more for user.
> 
> There is a nice tutorial NautilusScriptsHowto which let us use
> nautilus
> script itself without this package.
>   https://help.ubuntu.com/community/NautilusScriptsHowto
> 
> So I decided to stop. What is the point of keeping this package?
> 
> I am CCing git committers of this package.
> 
> If anyone is interested to keep this package, please update salsa
> repo
> and make upload.  The last commit by the upstream seems to be 2014.
> 
> If no one respond in few months, we should remove this from the next
> release.
> 
> Regards,
> 
> Osamu
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.15.0-1-amd64 (SMP w/12 CPU threads)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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
> 
> Versions of packages nautilus-scripts-manager depends on:
> ii  nautilus    41.1-1
> ii  python3 3.9.7-1
> ii  python3-gi  3.42.0-2+b1
> 
> nautilus-scripts-manager recommends no packages.
> 
> nautilus-scripts-manager suggests no packages.
> 
> -- no debconf information

Bug#998462: Plugin fails to load

2021-11-04 Thread Pietro Battiston 
Hi Crysn,

thanks for your report. The bug is not new, but there must have been
some confusion around it.

The error was already signaled as #955812 , I produced a simple
upstream fix at

https://gitlab.gnome.org/GNOME/gedit-latex/-/commit/2b4cbb4421b0f4e831550b7bc6a02931314e4133

and Adrian Bunk produced a NMU:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955812#82

... but I just found out the NMU diff was fixing a separate problem,
not the one included in the above patch. And indeed, I just tested the
plugin in bullseye and it produces the same error.

A new upstream version is badly needed and I will try to get it out as
soon as possible, but I will also try to get a backport of this diff to
bullseye (except I never did a backport so not sure how easy it will
be).

Pietro


Il giorno gio, 04/11/2021 alle 16.50 +0100, chrysn ha scritto:
> Package: gedit-latex-plugin
> Version: 3.20.0-2
> Severity: important
> 
> When using this in sid or bookworm, when the plugin is enabled and a
> .tex file opened, nothing happens and this shows up on stderr: 
> 
> Traceback (most recent call last):
>   File "/usr/lib/gedit/plugins/latex/tabdecorator.py", line 87, in
> _on_load
>     self._adjust_editor()
>   File "/usr/lib/gedit/plugins/latex/tabdecorator.py", line 107, in
> _adjust_editor
>     location = self._text_buffer.get_location()
> AttributeError: 'Document' object has no attribute 'get_location'
> Traceback (most recent call last):
>   File "/usr/lib/gedit/plugins/latex/tabdecorator.py", line 95, in
> _on_save
>     if not self._adjust_editor():
>   File "/usr/lib/gedit/plugins/latex/tabdecorator.py", line 107, in
> _adjust_editor
>     location = self._text_buffer.get_location()
> AttributeError: 'Document' object has no attribute 'get_location'
> 
> Could there be an undeclared mismatch between the LaTeX plugin
> version
> and gedit? (Gedit underwent something that looked like a major
> version
> change since the plugin was last updated, maybe an API changed).
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
> Kernel taint flags: TAINT_CRAP
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_GB:en
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages gedit-latex-plugin depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-2
> ii  gedit    40.1-2
> ii  libglib2.0-bin   2.70.0-3
> ii  python3  3.9.7-1
> ii  python3-dbus 1.2.18-3
> ii  python3-gi   3.42.0-1+b1
> ii  rubber   1.6.0-2
> 
> Versions of packages gedit-latex-plugin recommends:
> ii  texlive  2021.20210921-1
> 
> gedit-latex-plugin suggests no packages.
> 
> -- no debconf information
>

Bug#877740: gedit-latex-plugin: diff for NMU version 3.20.0-1.2

2021-02-13 Thread Pietro Battiston 
Thank you again!

Meanwhile, I merged your changes back in salsa, where there is a new
version in principle ready to be uploaded:
https://salsa.debian.org/debian/gedit-latex-plugin
It fixes a number of small other issues which are not urgent, but
neither invasive.

I'll let you judge if you want to proceed with this NMU or rather
upload the new version (notice I'm not a DD, so I need a sponsor
anyway). If you choose the second option, let me know beforehand and I
will quickly squeeze 3.20.0-1.2 out of debian/changelog.

CC-ing Olivier Tilloy, who had prepared few months ago a 3.20.0-2
fixing this issue which however, to the best of my understanding, never
got uploaded to any repo, so I've removed the related lines from
debian/changelog.

Pietro

Il giorno sab, 13/02/2021 alle 10.57 +0200, Adrian Bunk ha scritto:
> Dear maintainer,
> 
> I've prepared an NMU for gedit-latex-plugin (versioned as 3.20.0-
> 1.2). 
> The diff is attached to this message.
> 
> This upload was a correction for a mistake I did in my previous NMU.
> 
> cu
> Adrian

Bug#877740: Bug#955812: gedit-latex-plugin: diff for NMU version 3.20.0-1.1

2021-02-07 Thread Pietro Battiston 
Il giorno dom, 07/02/2021 alle 11.30 +0200, Adrian Bunk ha scritto:
> I've prepared an NMU for gedit-latex-plugin (versioned as 3.20.0-
> 1.1).

Thank you very much Adrian, and sorry everybody for the extremely slow
reaction.

Pietro

Bug#939028: Does it run?

2021-01-19 Thread Pietro Battiston 
Itaï, João,

still interested? Were you able to build and run the last version under
under testing or unstable?

So far, I wasn't, but if you were, that would be already the first
important step towards re-uploading to Debian.

What I tried was changing the dh_auto_configure by removing 

--enable-kwallet --enable-akonadi

and adding

--disable-ecal

so that the configuration succeeded; but then, it failed after a while
with

src/syncevo/Cmdline.cpp:1589:54: error: ‘_1’ was not declared in this
scope
 1589 |  _1));
  |  ^~


... which to my (ignorant) eyes reminds of the following warning, which
appeared multiple times before the error:

/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice
of declaring the Bind placeholders (_1, _2, ...) in the global
namespace is deprecated. Please use  + using
namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS
to retain the current behavior.’

Let me know,

Pietro

Bug#958108: Please build and install bindings for gi introspection

2020-04-26 Thread Pietro Battiston 
Il giorno dom, 26/04/2020 alle 15.46 +0200, Philipp Kern ha scritto:
> [...]
> Did you actually manage to build it successfully? There's currently a
> FTBFS bug due to glib (#935614) that I was able to bisect on the
> upstream Github report but where I am at a loss on how to fix.

Sorry, I should have mentioned that I did my experiment under buster.

Pietro

Bug#958108: Please build and install bindings for gi introspection

2020-04-18 Thread Pietro Battiston 
Package: libinfinity-0.7-0
Version: 0.7.1-1
Severity: wishlist
Tags: patch

The libinfinity software includes the gi introspection code, but it is
currently disabled in the debian package.

According to my tests, enabling it would only require replacing

--enable-gtk-doc


with

--enable-gtk-doc \
--enable-introspection

within debian/rules, and adding

usr/lib/@DEB_HOST_MULTIARCH@/girepository-1.0/*

after

usr/lib/@DEB_HOST_MULTIARCH@/libinfinoted-plugin-manager-*.so.*

within debian/libinfinity-0.7.0.install.



Thanks in advance,

Pietro



-- System Information:
Debian Release: 10.3
  APT prefers stable
  APT policy: (600, 'stable'), (500, 'stable-updates'), (500, 'stable-debug'), 
(500, 'proposed-updates-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libinfinity-0.7-0 depends on:
ii  dpkg  1.19.7
ii  libavahi-client3  0.7-4+b1
ii  libavahi-common3  0.7-4+b1
ii  libc6 2.29-9
ii  libdaemon00.14-7
ii  libglib2.0-0  2.58.3-2+deb10u2
ii  libgnutls30   3.6.7-4+deb10u3
ii  libgsasl7 1.8.0-8+b2
ii  libpam0g  1.3.1-5
ii  libxml2   2.9.4+dfsg1-7+b3

libinfinity-0.7-0 recommends no packages.

libinfinity-0.7-0 suggests no packages.

-- no debconf information

Bug#955812: gedit-latex-plugin does not work anymore

2020-04-16 Thread Pietro Battiston 
Il giorno dom, 12/04/2020 alle 18.12 +0200, Maurizio Quadrio ha
scritto:
> > [...]
> if BENCHMARK: t = time.clock()
> AttributeError: module 'time' has no attribute 'clock'

This (and the other AttributeError that followed) should be fixed by

https://gitlab.gnome.org/GNOME/gedit-latex/-/commit/0cf04556eeb3f35084051d5ec98c345432a838fe

... but you might need to also apply

https://gitlab.gnome.org/GNOME/gedit-latex/-/commit/959755c21d9909dafdd639455a1e621063b9c633

Then the plugin should work again.

I plan to create a release and the new Debian package in the next days.

Pietro

Bug#955812: gedit-latex-plugin does not work anymore

2020-04-12 Thread Pietro Battiston 
Thanks Maurizio!

Il giorno dom, 12/04/2020 alle 18.12 +0200, Maurizio Quadrio ha
scritto:
> > Mmmhhh... that's strange. Are you sure you only edited the line
> > starting with "location = self.text_buffer"?!
> [...]
> AttributeError: 'LaTeXEditor' object has no attribute
> '_document_is_master'

OK, seems to be

https://gitlab.gnome.org/GNOME/gedit-latex/-/issues/2

Will try to fix this too.

Pietro

Bug#955812: gedit-latex-plugin does not work anymore

2020-04-12 Thread Pietro Battiston 
Il giorno dom, 12/04/2020 alle 16.24 +0200, Maurizio Quadrio ha
scritto:
> @return: the extension of the currently opened file
>  ^
> SyntaxError: invalid syntax


Mmmhhh... that's strange. Are you sure you only edited the line
starting with "location = self.text_buffer"?!

Bug#955812: gedit-latex-plugin does not work anymore

2020-04-12 Thread Pietro Battiston 
Sorry, forget my last comment, only now I read the entire
gitlab.gnome.org bug, and produced a simple patch:
https://gitlab.gnome.org/GNOME/gedit-latex/-/commit/2b4cbb4421b0f4e831550b7bc6a02931314e4133

It works with gedit 3.30.2, so if any of you could test it with gedit
3.36.1-1 (even just editing that single file by hand), then I'd be
happy to merge the fix upstream and then update the Debian package.
Otherwise, I'll try to get a sid install running and test myself as
soon as possible.

Pietro

Il giorno sab, 11/04/2020 alle 19.28 +0200, Maurizio Quadrio ha
scritto:
> Dear Pietro,
> 
> thanks for your efforts. I fear the issue is related to both gedit-
> latex
> (upstream) *and* gedit. I also have a feeling that the trace I sent
> before was there since quite some time, whereas gedit-latex (which I
> use
> daily) broke a couple weeks ago.
> 
> Anyway, I'll stay tuned and see what happens...
> 
> 
> > Thanks Maurizio.
> > 
> > I still couldn't try to reproduce, but this reminds of
> > https://gitlab.gnome.org/GNOME/gedit/issues/225
> > 
> > ... which would suggest it is a problem of gedit, not gedit-latex.
> > 
> > Indeed, a gedit "Document.get_location()" should return a valid
> > Gio.File except if the file is not saved:
> > https://wiki.gnome.org/Apps/Gedit/PythonPluginHowTo#Gedit.Document
> >  - which does not seem to be your case.
> > 
> > Pietro
> >

Bug#955812: gedit-latex-plugin does not work anymore

2020-04-11 Thread Pietro Battiston 
Il giorno sab, 11/04/2020 alle 13.08 +0200, Maurizio Quadrio ha
scritto:
> [489][mq.asus: /home/mq]$ gedit -s
> Traceback (most recent call last):
>   File "/usr/lib/gedit/plugins/latex/tabdecorator.py", line 87, in
> _on_load
> self._adjust_editor()
>   File "/usr/lib/gedit/plugins/latex/tabdecorator.py", line 107, in
> _adjust_editor
> location = self._text_buffer.get_location()
> AttributeError: 'Document' object has no attribute 'get_location' 

Thanks Maurizio.

I still couldn't try to reproduce, but this reminds of
https://gitlab.gnome.org/GNOME/gedit/issues/225

... which would suggest it is a problem of gedit, not gedit-latex.

Indeed, a gedit "Document.get_location()" should return a valid
Gio.File except if the file is not saved:
https://wiki.gnome.org/Apps/Gedit/PythonPluginHowTo#Gedit.Document
 - which does not seem to be your case.

Pietro

Bug#955812: gedit-latex-plugin does not work anymore

2020-04-05 Thread Pietro Battiston 
Matthias, thank you for your report.

Indeed, I still didn't test the plugin with gedit version later 3.30.2.

Could you please try running gedit from the terminal (with "-s" if you
have other windows open already) and report any warning/error message?

Thanks,

Pietro



Il giorno dom, 05/04/2020 alle 10.06 +0200, Matthias Brennwald ha
scritto:
> Package: gedit-latex-plugin
> Version: 3.20.0-1
> Severity: important
> 
> I am running on Debian Testing. Since pulling in an upgrade
> yesterday, the
> gedit-latex-plugin does not work anymore. The gedit bottom panel used
> to show
> the LaTeX stuff, now it's just empty. Running the LaTeX compiler from
> within
> gedit (CTRL-ALT-1) does nothing. This happened to me on two different
> machines.
> I confirmed the plugin is activated in the gedit preferences.
> 
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (950, 'testing'), (800, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages gedit-latex-plugin depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
> ii  gedit3.36.1-1
> ii  gvfs-bin 1.44.1-1
> ii  python3  3.8.2-2
> ii  python3-dbus 1.2.16-1
> ii  python3-gi   3.36.0-1
> ii  rubber   1.5.1-2
> 
> Versions of packages gedit-latex-plugin recommends:
> ii  texlive  2019.20200302-1
> 
> gedit-latex-plugin suggests no packages.
> 
> -- no debconf information

Bug#945681: gvb: diff for NMU version 1.4-1.1

2019-12-26 Thread Pietro Battiston 
Dear Adrian,

thank you, I really appreciate. I was planning to fix that packaging
mistake, but as you might have noticed, I have really slow reactions
lately - and then, I still need to go through a sponsor. So if you
prefer, feel free to re-upload the package without delay.

Pietro

Il giorno gio, 26/12/2019 alle 15.04 +0200, Adrian Bunk ha scritto:
> Control: tags 945681 + patch
> Control: tags 945681 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for gvb (versioned as 1.4-1.1) and uploaded it
> to DELAYED/14. Please feel free to tell me if I should cancel it.
> 
> cu
> Adrian

Bug#944082: Removed package(s) from unstable

2019-11-11 Thread Pietro Battiston 
Il giorno mar, 12/11/2019 alle 00.02 +0100, Moritz Mühlenhoff ha
scritto:
> Your package is not a standalone, it's part of a complex system of
> components which interact with each other, we can't just ping people
> over and over when doing bigger-scale changes.

Managing complex systems requires rules, and indeed Debian has some,
including for migrations. This is why I was surprised by you declaring
the package "unmaintained" or "dead upstream" and removing it all of a
sudden: I was not asking for any special treatment for this package -
well on the contrary, I hadn't expected the special treatment it
received.

I have other packages with open bugs (sorry). I know you are busy, but
should you find the time to think about removing any of them, please
find the time before to ask me or at least warn me.

Thanks,

Pietro

Bug#944082: Removed package(s) from unstable

2019-11-04 Thread Pietro Battiston 
Moritz,

I didn't upload new releases simply because there were none, and there
were none simply because the required upgrade - to gtk 3 and gobject
introspection - has so far not been completed. There was already a bug¹
tracking that problem.

This was not an abandoned package, I was fully aware it had this
problematic dependency on pygtk, that it would eventually be removed
from unstable if the problem was not solved, and I was in contact with
upstream to understand if an upgrade plan was feasible. I would have
expected someone to try to contact me/the upstream developer -
respectively - before declaring it "dead upstream" and "unmaintained"
and removing it in 1 day.

(Then, what I don't understand is why I didn't receive any email
yesterday when this bug was opened. Had the package already been
reassigned?!)

Thanks for any clarification. I certainly won't claim I'm a model
maintainer, but I would like to better understand in what conditions
packages with open problems can disappear all of a sudden without the
maintainer being informed.

Pietro Battiston

¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885470


Il giorno lun, 04/11/2019 alle 07.45 +, Debian FTP Masters ha
scritto:
> We believe that the bug you reported is now fixed; the following
> package(s) have been removed from unstable:
> 
> python-sqlkit |  0.9.6.1-2 | all
> python-sqlkit-doc |  0.9.6.1-2 | all
> sqlkit |  0.9.6.1-2 | source
> 
> --- Reason ---
> RoQA; Dead upstream, unmaintained, depends on legacy libs
> --
> 
> 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 944...@bugs.debian.org.
> 
> The full log for this bug can be viewed at 
> https://bugs.debian.org/944082
> 
> This message was generated automatically; if you believe that there
> is
> a problem with it please contact the archive administrators by
> mailing
> ftpmas...@ftp-master.debian.org.
> 
> Debian distribution maintenance software
> pp.
> Scott Kitterman (the ftpmaster behind the curtain)

Bug#885212: Somebody plans to work on this?

2019-10-12 Thread Pietro Battiston 
Dear Debian Science Maintainers,

are there plans to fix this, or should we worry?

(I ask because I am the maintainer of gbutils which is set for
autoremoval in 9 days due to this)

Thanks,

Pietro

Bug#896726: gedit-source-code-browser-plugin: diff for NMU version 3.0.3-5.1

2018-06-12 Thread Pietro Battiston 
Dear Adrian,

Il giorno dom, 10/06/2018 alle 16.44 +0300, Adrian Bunk ha scritto:
> I've prepared an NMU for gedit-source-code-browser-plugin (versioned
> as 
> 3.0.3-5.1) and uploaded it to DELAYED/15. 

Thanks, this is much appreciated.

Pietro

Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring

2018-01-28 Thread Pietro Battiston 
Il giorno dom, 31/12/2017 alle 17.13 -0500, Jeremy Bicha ha scritto:
> On Sun, Dec 31, 2017 at 4:50 PM, Pietro Battiston <me@pietrobattiston
> .it> wrote:
> > given that gallery is dead upstream since 2014
> > ( http://galleryproject.org/time-to-hibernate ), I'm tempted to
> > orphan
> > this package (which I'm using no more).
> > 
> > In fact, gallery-uploader (and its dependency python-galleryremote)
> > never supported Gallery 3, and hence were officially obsolete since
> > since way before.
> 
> In that case, could you consider requesting those two packages be
> removed instead of orphaning them?

Done: #888645, #888646

Pietro

Bug#888646: RM: galleryremote -- ROM; obsolete, abandoned upstream

2018-01-28 Thread Pietro Battiston 
Package: ftp.debian.org
Severity: normal

This is a library which is (was) only used by "gallery-uploader",
of which I am also the maintainer, and of which I just requested
the removal (#888645). The reason is that this library (and hence
gallery-uploader) only supports very old versions of the gallery
web service.

Pietro

Bug#888645: RM: gallery-uploader -- ROM; obsolete, abandoned upstream, serious bug

2018-01-28 Thread Pietro Battiston 
Package: ftp.debian.org
Severity: normal

Also see #867959.

In short, the library ("python-galleryremote", source "galleryremote") 
underlying
the program only supports version of the Gallery (PHP) web service which have 
been
discontinued since many years.

Cheers,

Pietro

Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring

2018-01-04 Thread Pietro Battiston 
Il giorno dom, 31/12/2017 alle 17.13 -0500, Jeremy Bicha ha scritto:
> On Sun, Dec 31, 2017 at 4:50 PM, Pietro Battiston <me@pietrobattiston
> .it> wrote:
> > given that gallery is dead upstream since 2014
> > ( http://galleryproject.org/time-to-hibernate ), I'm tempted to
> > orphan
> > this package (which I'm using no more).
> > [...]
> 
> In that case, could you consider requesting those two packages be
> removed instead of orphaning them?

Sure. For reference:
https://groups.yahoo.com/neo/groups/gallery3/conversations/messages/555

Pietro

Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring

2017-12-31 Thread Pietro Battiston 
Il giorno dom, 31/12/2017 alle 14.28 -0500, Jeremy Bicha ha scritto:
> It is my understanding that it is Release
> Critical for a package to recommend a removed library because it
> keeps
> the package from being a candidate for auto-removal when users
> upgrade.


Thanks Jeremy for opening this issue,

given that gallery is dead upstream since 2014
( http://galleryproject.org/time-to-hibernate ), I'm tempted to orphan
this package (which I'm using no more).

In fact, gallery-uploader (and its dependency python-galleryremote)
never supported Gallery 3, and hence were officially obsolete since
since way before.

I'm going to send a message to the unofficial support group just to
check if anybody complains.

Pietro

Bug#880679: src:bottleneck: Relicense debianization to compatible terms with upstream

2017-11-03 Thread Pietro Battiston 
Il giorno ven, 03/11/2017 alle 17.28 +, Ghislain Antony Vaillant ha
scritto:
> Could you acknowledge your agreement to this request, which we
> discussed
> offline some time ago. 


Just nitpicking, but there is no "compatibility problem" in having a
GPL-3 package on a BSD project: in particular, anybody providing a
patch is perfectly free to release it - or not - under BSD (assuming
that the fix is not trivial, obviously).

That said, given that I am basically transferring responsability of the
package to you, I accept your preference for having the package
licensed as BSD, and hence acknowledge the relicensing.

Pietro

Bug#880678: src:bottleneck: Transfer package maintenance to the DPMT

2017-11-03 Thread Pietro Battiston 
Il giorno ven, 03/11/2017 alle 17.26 +, Ghislain Antony Vaillant ha
scritto:
> Package: src:bottleneck
> Severity: wishlist
> 
> Hi Pietro,
> 
> Could you acknowledge your agreement to this request, which we
> discussed
> offline some time ago.

Sure! Go ahead, and thank you for the care you are devoting to this
package.

Pietro

Bug#864509: Mistake in Italian translation (of "however:")

2017-06-09 Thread Pietro Battiston 
Package: dpkg
Version: 1.18.24
Severity: minor
Tags: l10n

In Italian, dpkg outputs (since as long as I can remember - I mentioned the
problem to a translator back in 2008) messages like

 skypeforlinux dipende da apt-transport-https; comunque:
  Il pacchetto apt-transport-https non è installato.

which should instead be

 skypeforlinux dipende da apt-transport-https; tuttavia:
  Il pacchetto apt-transport-https non è installato.

or (clearer, but more informal):

 skypeforlinux dipende da apt-transport-https, solo che:
  Il pacchetto apt-transport-https non è installato.

The problem is at line 4000 of po/it.po.

(the capital letter in "Il pacchetto" also seems wrong to me, but the original
English string is capitalized too)



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (400, 'experimental')
Architecture: amd64
 (x86_64)

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

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.24-10
ii  liblzma5 5.2.2-1.2+b1
ii  libselinux1  2.6-3+b1
ii  tar  1.29b-1.1
ii  zlib1g   1:1.2.8.dfsg-5

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt1.4.1
pn  debsig-verify  

-- no debconf information

Bug#737651: Killer does not respect niceness

2017-03-15 Thread Pietro Battiston 
Il giorno gio, 14/08/2014 alle 19.31 +0200, Petter Reinholdtsen ha
scritto:
> Sorry for the late reply.

Sorry for the _really_ late reply.


> I believe you lack one key information.  The nice level must be
> greater than 9.

Indeed I had missed this.

>   The information is hidden in the manual page,
> killer(1):
> 
>    removeNiceJobs
>    This function removes all jobs that have a nice value greater
> than 9.
>    That is, they have a lower sceduling priority than the default
> (0).
> 

While I'm at it, let me point out that the two sentences are not really
in agreement, and "sceduling" misses an "h". I would suggest replacing
with

"This function removes all jobs that have a nice value greater than 9
(default is 0, and 10 when running with the "nice" command)."


Anyway, thanks for your clarification.

Pietro

Bug#857290: Patch available

2017-03-09 Thread Pietro Battiston 
I have tested the patch at
https://git.gnome.org/browse/mutter/patch/?id=542ed1d024042cadae1c92c73
eb1e7f1acafd7e8
and after rebuilding mutter 3.22.3-1 with such patch applied, the
problem disappears.

It is a small patch, I hope it can be accepted by the release team.
Let me know if I can help.

Pietro

Bug#857290: Alternatetab makes gnome-shell segfault when window closes while switching

2017-03-09 Thread Pietro Battiston 
Package: gnome-shell-extensions
Version: 3.22.2-1
Severity: important

I use Alternatetab, and gnome-shell segfaults every time I switch away from a
window and the window closes before I finish switching (or in other terms:
every time I send an email with Evolution and forget to wait before switching
away from the composer window).

This didn't happen until some versions of gnome-shell ago (but I am unable to
provide more precise estimates of the regression version).

To reproduce:
- start gnome-shell
- enable Alternatetab
- open two terminals
- in one run "sleep 3; exit"
- before 3 seconds, press Alt+Tab to switch to the other, but leave Alt
pressed, and wait

I am attaching the backtrace.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gnome-shell-extensions depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gir1.2-atk-1.0   2.22.0-1
ii  gir1.2-clutter-1.0   1.26.0+dfsg-2
ii  gir1.2-gdkpixbuf-2.0 2.36.5-2
ii  gir1.2-glib-2.0  1.50.0-1+b1
ii  gir1.2-gmenu-3.0 3.13.3-8
ii  gir1.2-gtk-3.0   3.22.8-1
ii  gir1.2-mutter-3.03.22.3-1
ii  gir1.2-pango-1.0 1.40.3-3
ii  gnome-session3.22.2-2
ii  gnome-shell  3.22.3-1
ii  gvfs 1.30.3-1

Versions of packages gnome-shell-extensions recommends:
ii  gnome-tweak-tool  3.22.0-1

gnome-shell-extensions suggests no packages.

-- no debconf information
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gnome-shell...Reading symbols from 
/usr/lib/debug/.build-id/04/e476cc74b34d75e59e702faf509444be7c1f80.debug...done.
done.
(gdb) r
Starting program: /usr/bin/gnome-shell --replace
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdfba7700 (LWP 3614)]
[New Thread 0x7fffdd33a700 (LWP 3647)]
[New Thread 0x7fffdcb39700 (LWP 3650)]
[New Thread 0x7fffc700 (LWP 3651)]
[New Thread 0x7fffcf5f8700 (LWP 3653)]
[New Thread 0x7fffcedf7700 (LWP 3654)]
[New Thread 0x7fffb700 (LWP 3656)]
Gjs-Message: JS LOG: Failed to launch ibus-daemon: Esecuzione del processo 
figlio "ibus-daemon" non riuscita (File o directory non esistente)
Gjs-Message: JS LOG: Failed to add search provider 
/usr/share/gnome-shell/search-providers/org.gnome.bijiben-search-provider.ini: 
TypeError: appInfo is null
[New Thread 0x7fffb39ff700 (LWP 3666)]
[New Thread 0x7fffb2999700 (LWP 3671)]
[Thread 0x7fffdcb39700 (LWP 3650) exited]
[Thread 0x7fffb39ff700 (LWP 3666) exited]
[Thread 0x7fffb700 (LWP 3656) exited]
[New Thread 0x7fffb700 (LWP 3705)]
[Thread 0x7fffb2999700 (LWP 3671) exited]

Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
meta_window_appears_focused (window=0x0) at core/window.c:6745
6745core/window.c: File o directory non esistente.
#0  0x767694d0 in meta_window_appears_focused (window=0x0) at 
core/window.c:6745
#1  0x76747171 in meta_window_actor_get_paint_volume 
(actor=0x575e7760 [MetaWindowActor], volume=0x575e7630) at 
compositor/meta-window-actor.c:758
#2  0x75aac922 in _clutter_actor_get_paint_volume_real 
(pv=0x575e7630, self=0x575e7760 [MetaWindowActor]) at 
clutter-actor.c:17427
#3  0x75aac922 in _clutter_actor_get_paint_volume_mutable 
(self=0x575e7760 [MetaWindowActor]) at clutter-actor.c:17503
#4  0x75ab6159 in clutter_actor_get_paint_volume (self=) 
at clutter-actor.c:17548
#5  0x75ad6042 in clutter_clone_get_paint_volume (actor=0x56ec8a20 
[ClutterClone], volume=0x56ec88f0) at clutter-clone.c:218
#6  0x75aac922 in _clutter_actor_get_paint_volume_real 
(pv=0x56ec88f0, self=0x56ec8a20

Bug#777069: Switching from RFP to ITP

2017-02-24 Thread Pietro Battiston 
Il giorno ven, 24/02/2017 alle 10.36 +, Ghislain Vaillant ha
scritto:
> I would like to take over the following RFP.

Great, thanks!

Pietro

Bug#818226: Slightly different behaviour

2017-02-15 Thread Pietro Battiston 
Hi Dan,

with 1.2.5-2, I  (reliably) see a (stilly buggy) different behaviour
from the one you report.

Create a folder containing the following subfolders:
ab
oa
pa
po
pq

and then quickly type "p", "o" and Enter.

If I interpret correctly your report, then
- either the first letter is missed, and then "oa" will be opened
- or it is not missed, and then "po" will be opened

Instead, if I type quickly enough, I reliably open "pa" (that is,
_only_ the first letter is considered - although interestingly, I
briefly see that "po" was rightly selected). If I type more slowly,
"po" is correctly opened.

I'm trying to understand if this bug has "replaced" yours or if they
are independent.

(Ironically, I left Nautilus for pcmanfm precisely for the typeahead
functionality!)

Pietro

Bug#851613: src:bottleneck: Tests fail if enabled

2017-01-19 Thread Pietro Battiston 
Il giorno gio, 19/01/2017 alle 15.19 +, Ghislain Vaillant ha
scritto:
> On Thu, 2017-01-19 at 15:55 +0100, Pietro Battiston wrote:
> > Il giorno mar, 17/01/2017 alle 23.26 +, Ghislain Vaillant ha
> > scritto:
> > [...]
> > > Assuming, numpy stays in this version for the release, i.e.
> > > without
> > > the
> > > fix for the regression, then we'd be effectively releasing a
> > > buggy
> > > bottleneck package for Stretch.
> > 
> > I don't consider a software "buggy" just because its tests expose a
> > regression of some other software :-)
> 
> This is true if you consider the software *alone*. Debian is a
> *distribution*, so we should consider the software and its
> environment
> as a whole, which includes its runtime dependencies.

We are in the Debian bug tracker, I gave it as granted that the choice
depends on what's best for Debian.

On the other hand, your reasoning is nice because if it held, it would
mean that we'd be better off if upstream had never released the tests
in the first place, since we wouldn't even be discussing this and
Stretch users wouldn't be at risk of not having bottleneck (which works
fine) included.

Instead it is in the best interest of Stretch if bottleneck is included
_and_ it is in the best interest of Stretch if the regression in numpy
is fixed, and the two aspects are pretty orthogonal. Oh, and it is even
in the best interest of Stretch if by failing (even just in the logs),
its tests help exposing (possible future) regressions in other Debian
packages.

Then, the optimum is clearly that numpy is fixed and tests are enabled,
so let's wait and see.

Pietro

Bug#851613: src:bottleneck: Tests fail if enabled

2017-01-19 Thread Pietro Battiston 
Il giorno mar, 17/01/2017 alle 23.26 +, Ghislain Vaillant ha
scritto:
> On Tue, 2017-01-17 at 22:35 +0100, Pietro Battiston wrote:
> > [...]
> > I am a bit confused. It seems to me that bottleneck itself is not
> > in
> > worse shape than before the numpy regression was introduced.
> 
> It is still not worth releasing as it is. Sure the binary packages do
> build, but they fail to test with the current version of Numpy.

Yes, but it's because of numpy :-)

> Assuming, numpy stays in this version for the release, i.e. without
> the
> fix for the regression, then we'd be effectively releasing a buggy
> bottleneck package for Stretch.

I don't consider a software "buggy" just because its tests expose a
regression of some other software :-)
And I would hardly consider this as a valid reason for not releasing in
Stretch.
But anyway: I like the last approach you just proposed, I just pushed
your changes to alioth and asked my sponsor to upload.

Pietro

Bug#851613: src:bottleneck: Tests fail if enabled

2017-01-16 Thread Pietro Battiston 
Thanks for your report. Tests run fine in my install, which is a bit
out of date (e.g. python3-numpy version 1:1.11.2-1).
I will try to understand what update broke them. In the meanwhile, I
filed the bug upstream.

Pietro

Bug#851613: src:bottleneck: Tests fail if enabled

2017-01-16 Thread Pietro Battiston 
Il giorno lun, 16/01/2017 alle 20.50 +, Ghislain Antony Vaillant ha
scritto:
> [...]
> Input array:
> [[ inf   7. -inf  -9.]
>  [-10.  nan  nan   5.]
>  [  4.  nan  nan  inf]]
> 
> x and y +inf location mismatch:
>  x: array([-1. , -2.5,  inf], dtype=float32)
>  y: array([-1. , -2.5,  2. ], dtype=float32)

See kwgoodman's comment...
https://github.com/kwgoodman/bottleneck/issues/160#issuecomment-2729794
74

Pietro

Bug#851613: src:bottleneck: Tests fail if enabled

2017-01-16 Thread Pietro Battiston 
Il giorno lun, 16/01/2017 alle 22.32 +, Ghislain Vaillant ha
scritto:
> [...]
> Just out of curiosity, may I ask why the package is not team-
> maintained 
> by the Python modules team or the Debian Science team?

No specific reason, except that I don't know how it works and don't
have much time to learn (and last time I had time, the DPMT was still
using svn so I gave up!).

I would be happy to have the migration to a team happening if it means
less work for me, and I would not be happy if it means more work for me
:-)

Pietro

Bug#823770: Fixed?

2016-12-03 Thread Pietro Battiston 
Forget my previous message. This bug can just be closed, as stated by
Marc himself:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822828#15

Bug#823770: Fixed?

2016-12-03 Thread Pietro Battiston 
Marc, I suggest you test with 3.20.0-2, I expect the issue to be
solved.

Pietro

Bug#822828: Fixed?

2016-12-03 Thread Pietro Battiston 
Marc, I suggest you test with 3.20.0-2, I expect the issue to be
solved.

(and _this_ is the bug I meant to write to)

Pietro

Bug#770153: Patch introducing patch

2016-11-30 Thread Pietro Battiston 
As suggested in IRC, attached is a patch against the svn repo that
fixes the issue.

Pietrodiff --git a/debian/patches/09_fix_plugin_load_segfault.patch b/debian/patches/09_fix_plugin_load_segfault.patch
new file mode 100644
index 000..9e527f7
--- /dev/null
+++ b/debian/patches/09_fix_plugin_load_segfault.patch
@@ -0,0 +1,29 @@
+Description: fix segfault when loading plugins which extend menus
+ This patch integrates upstream commits
+ f4ecdcb8807fec2594f62bf7a7f179063f31e41b
+ and
+ 3bdfa5764deb9909dae9ef041a7e9b6d6297341a
+ The latter is only a style fix, but will make merging new upstream release
+ straightforward.
+Author: Pietro Battiston <m...@pietrobattiston.it>
+Bug-Debian: https://bugs.debian.org/770153
+Origin: upstream, https://bugzilla.gnome.org/show_bug.cgi?id=737781
+Bug: https://bugzilla.gnome.org/show_bug.cgi?id=737781
+Forwarded: not-needed
+Last-Update: 2016-11-30
+
+---
+--- gedit-3.22.0.orig/gedit/gedit-app.c
 gedit-3.22.0/gedit/gedit-app.c
+@@ -1712,6 +1712,11 @@ find_extension_point_section (GMenuModel
+ 
+ 			subsection = g_menu_model_get_item_link (model, i, G_MENU_LINK_SECTION);
+ 
++			if (subsection == NULL)
++			{
++subsection = model;
++			}
++
+ 			j_items = g_menu_model_get_n_items (subsection);
+ 
+ 			for (j = 0; j < j_items && !section; j++)
diff --git a/debian/patches/series b/debian/patches/series
index 766e40c..f703d0b 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 01_gedit-bugreport-location.patch
 03_no_gnu_gettext.patch
 08_multiarch_fallback.patch
+09_fix_plugin_load_segfault.patch

Bug#822828: Another duplicate?

2016-11-30 Thread Pietro Battiston 
Notice that
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823770
is probably itself a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770153

Pietro

Bug#823770: Duplicate?

2016-11-30 Thread Pietro Battiston 
Might be a(nother) dup of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770153

(which would be good news, since there is a fix)

Pietro

Bug#770153: Please add patch with upstream fix

2016-11-30 Thread Pietro Battiston 
Given the simplicity of the fix, I strongly suggest to add it as a
patch in Debian. It resorts to the following commit:
https://git.gnome.org/browse/gedit/commit/?id=f4ecdcb8807fec2594f62bf7a
7f179063f31e41b

... although I would add the following just for clarity:

https://git.gnome.org/browse/gedit/commit/?id=3bdfa5764deb9909dae9ef041
a7e9b6d6297341a

I would be happy to help (i.e. to prepare a unified patch).

Pietro

Bug#839548: Reports "No certificate was found" on working server

2016-11-02 Thread Pietro Battiston 
I recently upgraded several other packages, and while I ignore which
one made the difference, I can't reproduce the bug anymore (still with
the same version of gobby): gobby connects fine.

So I think this can be closed.

Pietro

Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*

2016-10-24 Thread Pietro Battiston 
Il giorno lun, 24/10/2016 alle 16.28 +0200, IOhannes m zmölnig
(Debian/GNU) ha scritto:
> 
> On 2016-10-24 13:48, Pietro Battiston wrote:
> > 
> > Il giorno lun, 24/10/2016 alle 12.06 +0200, Fabian Greffrath ha
> > scritto:
> > > 
> > > It's just a wild guess, but this
> > > 
> > > Pietro Battiston wrote:
> > > > 
> > > > 
> > > > Package: ardour
> > > > Version: 1:5.4.0~dfsg-1
> > > [...]
> > > > 
> > > > 
> > > > ii  ardour-data   1:4.2~dfsg-5
> > > 
> > > just doesn't seem corect to me!
> > > 
> > 
> > Oooohhh...
> > right.
> > This explains everything.
> > 
> > Package "ardour" should probably depend on the same exact version
> > of
> > package "ardour-data".
> 
> this is the fix i uploaded today with 1:5.4.0~dfsg-2

Yep, I replied before seeing it!

Thank you very much,

Pietro

Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*

2016-10-24 Thread Pietro Battiston 
Il giorno lun, 24/10/2016 alle 12.06 +0200, Fabian Greffrath ha
scritto:
> It's just a wild guess, but this
> 
> Pietro Battiston wrote:
> > 
> > Package: ardour
> > Version: 1:5.4.0~dfsg-1
> [...]
> > 
> > ii  ardour-data   1:4.2~dfsg-5
> 
> just doesn't seem corect to me!
> 

Oooohhh...
right.
This explains everything.

Package "ardour" should probably depend on the same exact version of
package "ardour-data".

Pietro

Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*

2016-10-23 Thread Pietro Battiston 
Package: ardour
Version: 1:5.4.0~dfsg-1
Severity: grave

Ardour 1:4.7~dfsg-2 works great. If instead I upgrade to 1:5.3~dfsg-1 (current
unstable) or 1:5.4.0~dfsg-1 (current testing), I get a segfault when I try to
load any project.

I am attaching a gdb run (from 1:5.4.0~dfsg-1).



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

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

Versions of packages ardour depends on:
ii  ardour-data   1:4.2~dfsg-5
ii  jackd 5
ii  libarchive13  3.2.1-4
ii  libasound21.0.29-1
ii  libatk1.0-0   2.18.0-1
ii  libatkmm-1.6-1v5  2.24.2-1
ii  libaubio4 0.4.1-2+b3
ii  libbluetooth3 5.33-1
ii  libc6 2.24-3
ii  libcairo2 1.14.2-2
ii  libcairomm-1.0-1v51.12.0-1
ii  libcurl3-gnutls   7.45.0-1
ii  libcwiid1 0.6.00+svn201-3.2
ii  libfftw3-single3  3.3.5-1
ii  libflac8  1.3.1-4
ii  libfluidsynth11.1.6-3
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6-2
ii  libgcc1   1:5.2.1-22
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libglib2.0-0  2.50.0-1
ii  libglibmm-2.4-1v5 2.50.0-1
ii  libgtk2.0-0   2.24.28-1
ii  libgtkmm-2.4-1v5  1:2.24.5-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  liblilv-0-0   0.24.0~dfsg0-1
ii  liblo70.28-5
ii  liblrdf0  0.4.0-5
ii  libltc11  1.1.4-1
ii  libogg0   1.3.2-1
ii  libpango-1.0-01.38.0-3
ii  libpangocairo-1.0-0   1.38.0-3
ii  libpangoft2-1.0-0 1.38.0-3
ii  libpangomm-1.4-1v52.40.1-3
ii  librubberband21.8.1-6+b1
ii  libsamplerate00.1.8-8
ii  libserd-0-0   0.24.0~dfsg0-1
ii  libsigc++-2.0-0v5 2.10.0-1
ii  libsndfile1   1.0.25-9.1
ii  libsord-0-0   0.16.0~dfsg0-1
ii  libsratom-0-0 0.4.6~dfsg0-1
ii  libstdc++66.2.0-6
ii  libsuil-0-0   0.8.2~dfsg0-1
ii  libtag1v5 1.9.1-2.4
ii  libvamp-hostsdk3v52.6~repack0-2
ii  libvamp-sdk2v52.6~repack0-2
ii  libx11-6  2:1.6.3-1
ii  libxml2   2.9.2+zdfsg1-4

Versions of packages ardour recommends:
ii  ardour-video-timeline   1:5.4.0~dfsg-1
ii  chromium [www-browser]  50.0.2661.94-1
ii  epiphany-browser [www-browser]  3.18.0-1+b1
ii  firefox-esr [www-browser]   45.0.1esr-1
ii  iceweasel   45.3.0esr-1
ii  links [www-browser] 2.12-1
ii  w3m [www-browser]   0.5.3-25

Versions of packages ardour suggests:
pn  jamin 
ii  qjackctl  0.4.0-1

-- no debconf information
(gdb) r
Starting program: /usr/lib/ardour5/ardour-5.4.0 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Cannot find ArdourMono TrueType font
bind txt domain [gtk2_ardour5] to /usr/share/ardour5/locale
Ardour5.4.0 (built using 1:5.4.0~dfsg-1 and GCC version 6.2.0 20161010)
ardour: [INFO]: Your system is configured to limit Ardour to only 65.536 open files
ardour: [INFO]: Loading system configuration file /etc/ardour5/system_config
ardour: [INFO]: Loading user configuration file /home/pietro/.config/ardour5/config
[New Thread 0x7fffd942d700 (LWP 27425)]
ardour: [INFO]: CPU vendor: GenuineIntel
ardour: [INFO]: AVX-capable processor
ardour: [INFO]: CPU brand: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
ardour: [INFO]: Using SSE optimized routines
[New Thread 0x7fffd8c2c700 (LWP 27426)]
[New Thread 0x7fffd3fff700 (LWP 27427)]
[New Thread 0x7fffd37fe700 (LWP 27428)]
[New Thread 0x7fffd196e700 (LWP 27429)]
[New Thread 0x7fffd116d700 (LWP 27430)]
Cannot xinstall SIGPIPE error handler
ardour: [INFO]: Loading default ui configuration file /etc/ardour5/default_ui_config
ardour: [INFO]: Loading user ui configuration file /home/pietro/.config/ardour5/ui_config
ardour: [WARNING]: Color file for dark-ardour not found along /home/pietro/.config/ardour5/themes:/usr/share/ardour5/themes
ardour: [INFO]: Loading ui configuration file /etc/ardour5/clearlooks.rc
/etc/ardour5/clearlooks.rc:9: Invalid symbolic

Bug#839548: Reports "No certificate was found" on working server

2016-10-02 Thread Pietro Battiston 
Il giorno dom, 02/10/2016 alle 16.24 +0200, Philipp Kern ha scritto:
> [...]
> > The server works perfectly with gobby 0.5.0 from a Windows machine,
> > and 
> > used to
> > work perfectly with the previous version of the Debian package.
> 
> How did you start the infinote server? You might have turned off 
> security there? Did you actually install a cert? [...]
> 

The server was started with the following config file:

[infinoted]
security-policy=require-tls  # commenting this doesn't help
certificate-file=/home/pietro/.config/infinoted.cert
password=EDITED
key-file=/home/pietro/.config/infinoted.key


The cert was generated by the server itself (I tried to generate a new
one, no difference).

Then again, everything works smoothly with the same server from the
same (upstream) version of gobby ran in Windows.

Pietro

Bug#839548: Reports "No certificate was found" on working server

2016-10-01 Thread Pietro Battiston 
Package: gobby
Version: 0.5.0-8
Severity: important

Since I upgraded gobby to 0.5.0-8 (and some libraries with it), when I try to
connect to my server, it fails with the following error message: "The server
certificate is not trusted: No certificate was found.".

At the same time, in the terminal I see the following popping up:

** (gobby:31425): WARNING **: Failure during SRV record lookup: No address
associated with name
Will go on with normal A/ lookup

The server works perfectly with gobby 0.5.0 from a Windows machine, and used to
work perfectly with the previous version of the Debian package.



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

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

Versions of packages gobby depends on:
ii  dpkg1.18.3
ii  libatk1.0-0 2.18.0-1
ii  libatkmm-1.6-1v52.24.2-1
ii  libc6   2.24-3
ii  libcairo-gobject2   1.14.2-2
ii  libcairo2   1.14.2-2
ii  libcairomm-1.0-1v5  1.12.0-1
ii  libgcc1 1:5.2.1-22
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.0-1
ii  libglibmm-2.4-1v5   2.50.0-1
ii  libgnutls30 3.5.4-2
ii  libgsasl7   1.8.0-8+b1
ii  libgtk-3-0  3.22.0-1
ii  libgtkmm-3.0-1v53.22.0-1
ii  libgtksourceview-3.0-1  3.22.0-1
ii  libinfgtk3-0.6-00.6.6-1
ii  libinfinity-0.6-0   0.6.7-1+b1
ii  libpango-1.0-0  1.38.0-3
ii  libpangocairo-1.0-0 1.38.0-3
ii  libpangomm-1.4-1v5  2.40.1-3
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libstdc++6  5.2.1-22
ii  libxml++2.6-2v5 2.40.1-1
ii  libxml2 2.9.2+zdfsg1-4

gobby recommends no packages.

Versions of packages gobby suggests:
ii  avahi-daemon  0.6.31-5

-- no debconf information

Bug#833124: Please update versione Depends on libecal

2016-08-01 Thread Pietro Battiston 
Package: evolution
Version: 3.20.4-1
Severity: important

Evolution 3.20.4-2 depends on

"libecal-1.2-19 (>= 3.17)"

Hence when I manually upgraded to Evolution 3.20.4-2 (version in "testing") my
system was left with libecal-1.2-19 version 3.18.0-3, and in this configuration
Evolution would segfault every time I tried to open the preferences window. I
noticed that the gdb backtrace referred to libecal, and indeed upgrading
libecal-1.2-19 to version 3.20.4-2 immediately fixed the problem. The versioned
Depends should hence probably be changed to

"libecal-1.2-19 (>= 3.20.4)"



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

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

Versions of packages evolution depends on:
ii  dbus   1.10.0-3
ii  evolution-common   3.20.4-1
ii  evolution-data-server  3.20.4-2
ii  libc6  2.19-22
ii  libcamel-1.2-573.20.4-2
ii  libclutter-gtk-1.0-0   1.6.6-1
ii  libecal-1.2-19 3.20.4-2
ii  libedataserver-1.2-21  3.20.4-2
ii  libevolution   3.20.4-1
ii  libglib2.0-0   2.48.0-1
ii  libgtk-3-0 3.20.3-2
ii  libical2   2.0.0-0.4
ii  libicu55   55.1-5
ii  libnotify4 0.7.6-2
ii  libsoup2.4-1   2.52.1-1
ii  libwebkitgtk-3.0-0 2.4.9-2+b1
ii  libxml22.9.2+zdfsg1-4
ii  psmisc 22.21-2.1

Versions of packages evolution recommends:
ii  bogofilter 1.2.4+dfsg1-3
ii  evolution-plugins  3.20.4-1
ii  yelp   3.16.1-1

Versions of packages evolution suggests:
pn  evolution-ews   
ii  evolution-plugins-experimental  3.20.4-1
ii  gnupg   1.4.19-5
ii  network-manager 1.2.0-1

-- debconf information excluded

Bug#820957: fontypython: Fonts not rendered in the font preview. A fallback font is used instead.

2016-04-14 Thread Pietro Battiston 
Il giorno gio, 14/04/2016 alle 09.49 +0200, Pietro Battiston ha
scritto:
> It is more than probable that this reflects the same problem as
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806976
> since fontypython uses "tostring()" at lines 413 and 414 of
> fontypythonmodules/gui_Fitmap.py

Quick update: this is indeed the problem, and it is indeed fixed by
just replacing the two "tostring()" with "tobytes()": fontypython
starts working again.

Kartik, shall I proceed with an NM upload (like the last time)?

Pietro

Bug#820957: fontypython: Fonts not rendered in the font preview. A fallback font is used instead.

2016-04-14 Thread Pietro Battiston 
Indeed, I can reproduce, and have verified the bug is triggered by the
update of python-pil (in my case, from 2.9.0-1+b1 to 3.1.1-1+b1).

It is more than probable that this reflects the same problem as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806976
since fontypython uses "tostring()" at lines 413 and 414 of
fontypythonmodules/gui_Fitmap.py

My guess is also that this should not be hard to fix... will try to
give a look in the next couple of weeks.

Kartik, do you think we should also ask a "Breaks" on python-pil (as
currently happens for rapid-photo-downloader and tilestache)?

Pietro

Bug#743877: ITP: numba -- NumPy-aware optimizing compiler for Python

2016-03-03 Thread Pietro Battiston 
Il giorno mar, 15/12/2015 alle 17.53 +0100, Daniel Stender ha scritto:
> Hi Pietro,
> 
> I've got llvmlite in NEW now. I would be interested in maintaining
> Numba, too. Is that
> allright with you?
> 

Sorry Daniel, I had missed your email.

I think the fact that you adopt Numba is just great.

Pietro

Bug#706027: I use it

2015-10-21 Thread Pietro Battiston 
Unetbootin is very useful to me. I used it to prepare a lot of
Ubuntu/Debian installations, and also to prepare some USB sticks to be
used as live distributions.

I think this bug can be closed.

Bug#712902: Workaround

2015-10-21 Thread Pietro Battiston 
I have the same problem. While

gksu unetbootin

does not work for me,

QT_X11_NO_MITSHM=1 unetbootin

does. The fix comes from
https://bugs.archlinux.org/task/42030#comment131387

I see in the author's PPA version 608, but I have no idea if it
addresses this bug.

Pietro

Bug#787896: Update...

2015-10-19 Thread Pietro Battiston 
I don't know if it was an update or what (I'm running testing), but
evince doesn't honour any more the "button-layout" setting. Other
programs (e.g. evolution, iceweasel...) do (Gedit doesn't).
My workaround hence doesn't work any more.

Bug#787896: Upstream said WONTFIX

2015-10-13 Thread Pietro Battiston 
I also was hit by this problem. Two remarks:

- I am afraid this is WONTFIX (or at least RedHat thinks so:
  https://bugzilla.redhat.com/show_bug.cgi?id=1180709), because it was
  an intentional change... but you can maybe try to open a bug upstream
  raising the issue (though I doubt that they will listen).

- I was able to solve the problem for me by just changing the buttons
  layout:

gsettings set org.gnome.desktop.wm.preferences button-layout \ ":close"

  Now evince is able to go half-screen on my 1366x768 monitor (but not
  on my 1280x1024 one). You can certainly shrink a bit more by also
  removing the "close" button and/or by switching theme (see
  https://bbs.archlinux.org/viewtopic.php?id=189333 ) but it will be
  very hard to get down half of a 1024 screen.

(BTW: Peter, as far as I know Okular or Zathura could work for you.)

Pietro

Bug#784986: Ubuntu package

2015-10-09 Thread Pietro Battiston 
Just for the records, there is an Ubuntu package:
https://launchpad.net/~alessandro-strada/+archive/ubuntu/ppa
which I am using succesfully under Debian testing, and which might be a
starting point for a Debian package.

Pietro

Bug#714973: google-drive-ocamlfuse

2015-10-09 Thread Pietro Battiston 
Notice the RFP for the better maintained google-drive-ocamlfuse:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784986

Pietro

Bug#783169: google-drive-ocamlfuse

2015-10-06 Thread Pietro Battiston 
I just want to signal that google-drive-ocamlfuse seems to work
reliably, has a Ubuntu package (which I'm using under Debian) and is
quite comfortable to use - just mounts the drive in the desired
position:
http://gdfuse.forge.ocamlcore.org/

Pietro

Bug#798829: "OSError: [Errno 2] No such file or directory: ''" when running bibtex

2015-09-25 Thread Pietro Battiston 
Il giorno mer, 23/09/2015 alle 23.21 +0200, Pietro Battiston ha
scritto:
> [...]
> I also seem to be able to provide an explanation: patch
> rubber-1.2/src/latex_modules/bibtex.py
> 

Sorry, I meant patch
debian/patches/02_rubber_bibtext_20120807.diff
... witch affects file
src/latex_modules/bibtex.py

Pietro

Bug#798829: "OSError: [Errno 2] No such file or directory: ''" when running bibtex

2015-09-23 Thread Pietro Battiston 
Il giorno mer, 23/09/2015 alle 22.36 +0200, Preuße, Hilmar ha scritto:
> On 13.09.2015 13:02, Pietro Battiston wrote:
> 
> Hi,
> 
> > Since one of the last two updates, rubber is unable to compile a
> > document of
> > mine which previously it was perfectly able to:
> > 
> We're failing to reproduce the problem. Could you provide a minimal
> example to
> reproduce it? Are we looking at a duplicate of #798991?
> 

I also seem to be able to provide an explanation: patch
rubber-1.2/src/latex_modules/bibtex.py

it replaces

biblio = Bibliography(doc, doc.target)

with

biblio = Bibliography(doc, basename(doc.target))

at line 410 or so. Now, the second argument becomes attribute
"self.base" of the newly created Bibliography object (line 44). And
here comes line 256 or so:

workdir = os.path.dirname(self.base)

which asks the workdir... of a filename, rather than a path!

The patch doesn't give any detail on which bug it was fixing, so I
don't know what should be done about it.

Pietro

Bug#798829: "OSError: [Errno 2] No such file or directory: ''" when running bibtex

2015-09-23 Thread Pietro Battiston 
Il giorno mer, 23/09/2015 alle 22.36 +0200, Preuße, Hilmar ha scritto:
> On 13.09.2015 13:02, Pietro Battiston wrote:
> 
> Hi,
> 
> > Since one of the last two updates, rubber is unable to compile a
> > document of
> > mine which previously it was perfectly able to:
> > 
> We're failing to reproduce the problem. Could you provide a minimal
> example to
> reproduce it? 

Here's a minimal example... but anything using bibtex fails for me, so
I'm afraid the bug is context-related...

1) put the following in a file ~/radiation.tex:

\documentclass{article}
\begin{document}
test \cite{pietro}
\bibliographystyle{plain}
\bibliography{radiation.bib}
\end{document}

2) put the following in a file ~/radiation.bib:
@article{pietro,
  title={Shameless self-cite},
  author={Pietro Battiston},
  year={2014}
}

3) open a terminal and type in one line:
rubber --inplace --maxerr -1 --short --force --warn all --pdf
radiation.tex

You get the error above. Notice running pdflatex and bibtex manually wo
rks fine.

> Are we looking at a duplicate of #798991?

Assuming the symptoms of #798991 are correctly reported, no: I don't
have any symlink in my setup.

Pietro

Bug#798738: Unable to reproduce

2015-09-16 Thread Pietro Battiston 
I'm unfortunately unable to reproduce both on my normal user and on a
brand new user: fontypython seems to behave fine.

The only difference I spot in the dependencies is that my version of
 python-wxgtk3.0 is 3.0.2.0+dfsg-1+b1 : could this explain the
different behavior?

Pietro

Bug#798829: "OSError: [Errno 2] No such file or directory: ''" when running bibtex

2015-09-13 Thread Pietro Battiston 
Package: rubber
Version: 1.2-1
Severity: important
Tags: patch

Since one of the last two updates, rubber is unable to compile a document of
mine which previously it was perfectly able to:

pietro@debiousci:~/radiation$ rubber --inplace --maxerr -1 --short --force
--warn all --pdf radiation_04.tex
compiling radiation_04.tex...
running BibTeX on radiation_04...
Traceback (most recent call last):
  File "/usr/bin/rubber", line 4, in 
sys.exit(Main()(sys.argv[1:]))
  File "/usr/lib/python2.7/dist-packages/rubber/cmdline.py", line 331, in
__call__
return self.main(cmdline)
  File "/usr/lib/python2.7/dist-packages/rubber/cmdline.py", line 287, in main
ret = env.main.make(True)
  File "/usr/lib/python2.7/dist-packages/rubber/depend.py", line 164, in make
ok = self.force_run()
  File "/usr/lib/python2.7/dist-packages/rubber/converters/latex.py", line
1288, in force_run
return self.run(True)
  File "/usr/lib/python2.7/dist-packages/rubber/converters/latex.py", line
1310, in run
if not self.post_compile():
  File "/usr/lib/python2.7/dist-packages/rubber/converters/latex.py", line
1261, in post_compile
if not mod.post_compile():
  File "/usr/lib/python2.7/dist-packages/rubber/converters/latex.py", line
1526, in post_compile
return self.pymodule.post_compile()
  File "/usr/lib/python2.7/dist-packages/rubber/latex_modules/bibtex.py", line
421, in post_compile
return biblio.post_compile()
  File "/usr/lib/python2.7/dist-packages/rubber/latex_modules/bibtex.py", line
235, in post_compile
return self.run()
  File "/usr/lib/python2.7/dist-packages/rubber/latex_modules/bibtex.py", line
258, in run
if self.doc.env.execute(['bibtex', basename], doc, pwd=workdir):
  File "/usr/lib/python2.7/dist-packages/rubber/environment.py", line 228, in
execute
stderr = stderr)
  File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory: ''

The problem is that "execute()" in "environment.py" is receiving the empty
string as "pwd" argument, and this in turn is due to "run()", in
latex_modules/bibtex.py, calling "os.path.dirname" on a string which contains
(at least in some cases) a filename rather than a full path.

The problem is solved by replacing

workdir = os.path.dirname (self.base)

with

workdir = os.path.dirname(os.path.realpath(self.base))

at line 256 of latex_modules/bibtex.py. I am farly confident this fix should
not have undesired effects, what I ignore is whether it would better be
implemented at some other level (i.e. if other modules than bibtex are affected
by this bug).



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

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

Versions of packages rubber depends on:
ii  python  2.7.9-1
pn  python:any  
ii  texlive-latex-base  2015.20150823-1

rubber recommends no packages.

Versions of packages rubber suggests:
ii  imagemagick  8:6.8.9.9-5
pn  sam2p
pn  transfig 

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/lib/python2.7/dist-packages/rubber/environment.py 
(from rubber package)
debsums: changed file 
/usr/lib/python2.7/dist-packages/rubber/latex_modules/bibtex.py (from rubber 
package)

Bug#773525: Randomly excludes available connections [when there are too many?]

2015-07-17 Thread Pietro Battiston 
Sorry if this is trivial to all the participants in the discussion - it
was not stated clearly so I thought it may be useful information.

nmcli c (1.0.2-2) currently appears to be fixed, in the sense that it
consistently outputs the same list of my 456 connections (see also the
duplicate bug).

nm-connection-editor (from network-manager-gnome 1.0.2-1) and gnome
-control-center (from gnome-system-tools 3.0.0-4) are still broken:
they both show only part of the connections, and not always the same
ones.

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#789618: Suspend

2015-06-22 Thread Pietro Battiston 
Interestingly (or not?), the shortcut for suspension doesn't work, but
the button for suspending in the top-right menu works regularly.

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#789618: Shorcuts associated to launchers stopped working

2015-06-22 Thread Pietro Battiston 
Package: gnome-shell
Version: 3.14.4-1
Severity: normal

Today I upgraded my system, and most shortcuts stopped working. Upon
investigation, it turns out that shortcuts are broken if they launch external
applications, regardless of what combination of keystrokes is chosen.

For instance, my shortcuts for Home, Terminal stopped working.
The shortcut for launching the prompt (with Alt+F2) still works regularly.

But if I reassign Alt+F2 to launching Home, it doesn't work. Conversely, if I
assign Ctrl+Alt+H to the prompt, it works.

There are other bugs open about shortcuts not working, but they don't seem to
be related, since they seem to depend on the chosen combination/used keyboard
layout, while here both seem to be irrelevant.

To be honest, it is not clear to me which package is to blame, since gnome-
shell was _not_ upgraded today! Some packages that were instead upgraded are
libgtk-3-common, gir1.2-gtk-3.0, gnome-menus, desktop-file-utils, libglib2.0-0,
gnome-control-center, gnome-settings-daemon, gnome-shell-extension-weather.
Please feel free to reassign.

I tested this on two different computers, including an environment with no
extensions activated.



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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  evolution-data-server3.16.3-1
ii  gir1.2-accountsservice-1.0   0.6.40-2
ii  gir1.2-atspi-2.0 2.16.0-1
ii  gir1.2-caribou-1.0   0.4.18.1-1
ii  gir1.2-clutter-1.0   1.22.2-3
ii  gir1.2-freedesktop   1.44.0-1+b1
ii  gir1.2-gcr-3 3.16.0-1
ii  gir1.2-gdesktopenums-3.0 3.16.1-1
ii  gir1.2-gdm3  3.14.1-8
ii  gir1.2-gkbd-3.0  3.6.0-1
ii  gir1.2-glib-2.0  1.44.0-1+b1
ii  gir1.2-gnomebluetooth-1.03.16.1-1
ii  gir1.2-gnomedesktop-3.0  3.16.2-2
ii  gir1.2-gtk-3.0   3.16.4-2
ii  gir1.2-ibus-1.0  1.5.10-1
ii  gir1.2-mutter-3.03.14.4-2+b1
ii  gir1.2-networkmanager-1.01.0.2-2
ii  gir1.2-nmgtk-1.0 1.0.2-1
ii  gir1.2-pango-1.0 1.36.8-3
ii  gir1.2-polkit-1.00.105-8
ii  gir1.2-soup-2.4  2.50.0-2
ii  gir1.2-telepathyglib-0.120.24.1-1
ii  gir1.2-telepathylogger-0.2   0.8.1-1
ii  gir1.2-upowerglib-1.00.99.3-1+b1
ii  gjs  1.42.0-1
ii  gnome-backgrounds3.16.0-1
ii  gnome-icon-theme-symbolic3.12.0-1
ii  gnome-settings-daemon3.16.2-3
ii  gnome-shell-common   3.14.4-1
ii  gnome-themes-standard3.14.2.2-1
ii  gsettings-desktop-schemas3.16.1-1
ii  libatk-bridge2.0-0   2.16.0-1
ii  libatk1.0-0  2.16.0-2
ii  libc62.19-18
ii  libcairo21.14.2-2
ii  libcanberra-gtk3-0   0.30-2.1
ii  libcanberra0 0.30-2.1
ii  libclutter-1.0-0 1.22.2-3
ii  libcogl-pango20  1.20.0-2
ii  libcogl201.20.0-2
ii  libcroco30.6.8-3+b1
ii  libdbus-glib-1-2 0.102-1
ii  libecal-1.2-16   3.12.11-1
ii  libedataserver-1.2-183.12.11-1
ii  libgcr-base-3-1  3.16.0-1
ii  libgdk-pixbuf2.0-0   2.31.4-2
ii  libgirepository-1.0-11.44.0-1+b1
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.42.0-1
ii  libglib2.0-0 2.44.1-1
ii  libgstreamer1.0-01.4.5-2
ii  libgtk-3-0   3.16.4-2
ii  libical1a1.0-1.3
ii  libjson-glib-1.0-0   1.0.4-1
ii  libmozjs-24-024.2.0-3
ii  libmutter0e  3.14.4-2+b1
ii  libnm-glib4  1.0.2-2
ii  libnm-util2  1.0.2-2
ii

Bug#788844: RFS: gbutils/5.6.6-1 [ITP]

2015-06-15 Thread Pietro Battiston 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package gbutils

 * Package name: gbutils
   Version : 5.6.6-1
   Upstream Author : Giulio Bottazzi
 * URL : http://cafed.sssup.it/software/gbutils/gbutils.html
 * License : GPL-2+
   Section : science

It builds those binary packages:

  gbutils- utilities for command line econometrics

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

http://mentors.debian.net/package/gbutils


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

dget -x \
http://mentors.debian.net/debian/pool/main/g/gbutils/gbutils_5.6.6-1.dsc

or the packaging git repository with

git clone git://anonscm.debian.org/collab-maint/gbutils.git


Regards,

Pietro Battiston


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#787082: [ITP] gbutils - utilities for command line econometrics

2015-05-28 Thread Pietro Battiston 
Package: wnpp
Severity: wishlist

Description: utilities for command line econometrics
 A set of command line utilities for the manipulation and statistical analysis
 of data. These utilities read data from standard input in an ASCII format and
 print the result in ASCII format to standard output.


signature.asc
Description: This is a digitally signed message part

Bug#777069: RFP: line-profiler -- Line-by-line profiling for Python

2015-02-04 Thread Pietro Battiston 
Package: wnpp
Severity: wishlist

* Package name: line-profiler
  Version : 1.0
  Upstream Author : Robert Kern
* URL : https://pypi.python.org/pypi/line_profiler/
* License : Python
  Programming Lang: Python
  Description : Line-by-line profiling for Python

line_profiler is a simple module for doing line-by-line profiling of desired
Python functions.

It also provides a magic command for ipython, %lprun, which is really handy to
profile code on the fly.

I quickly packaged line_profiler and I am using it succesfully. I don't think I
will (try to) adopt it, but here is my git repo anybody can use/start from:
http://anonscm.debian.org/gitweb/?p=collab-maint/line-profiler.git
git clone git://anonscm.debian.org/collab-maint/line-profiler.git

The package for Python 3 also provides the executable kernprof, which should
simplify the operation of profiling a Python script. I haven't tested it yet.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#742134: Packaged new version

2015-01-30 Thread Pietro Battiston 
I quickly put together a package of 0.7.0 also supporting python3, and
after suppressing two problematic tests (PageRank tests segfault - I
didn't investigate why), I am using it without any problem so far.

Attached are the modified files (I have no familiarity with svn),
including the two meant to reside in debian/patches. At the following
address:
http://pietrobattiston.it/t/igraph
are the resulting binary packages for amd64.

Notice that my package could not be simply uploaded as it is, since it
(should) build-depends on the same version of igraph, i.e. 0.7.0, which
is not in Debian (and never was). The build process only works on my pc
because it automatically fetches and builds igraph 0.7.0. The produced
packages seem to play well with libigraph 0.7.1 (except maybe for the
failed tests?), but forcing the build against libigraph 0.7.1 fails.

Anyway, it is possible that when jessie is out python-igraph 0.7.1 will
be out too. It will then maybe be a good time to transform the
build-depends into a versioned one.

Cheers,

Pietro
python-igraph (0.7-1) unstable; urgency=medium

  * Imported Upstream version 0.7 (Closes: #758211)
  * Support for Python3 (Closes: #742134)
  * Updated watch file
  * Bump Standards-Version to 3.9.6

 -- Pietro Battiston m...@pietrobattiston.it  Fri, 30 Jan 2015 11:26:02 +0100

python-igraph (0.6.5-1) unstable; urgency=low

  [ Jakub Wilk ]
  * Use canonical URIs for Vcs-* fields.

  [ TANIGUCHI Takaki ]
  * New upstream release
  * Bump Standards-Version to 3.9.4. 

 -- TANIGUCHI Takaki tak...@debian.org  Thu, 06 Jun 2013 10:57:53 +0900

python-igraph (0.5.4-2) unstable; urgency=low

  * Stop installing /usr/bin/igrpah. (Closes: #664443)
  * debian/control: Change Maintainer to DPMT.

 -- TANIGUCHI Takaki tak...@debian.org  Sun, 18 Mar 2012 11:38:57 +0900

python-igraph (0.5.4-1) unstable; urgency=low

  * Initial release (Closes: #574825)

 -- TANIGUCHI Takaki tak...@debian.org  Sat, 17 Mar 2012 17:23:55 +0900
Source: python-igraph
Section: python
Priority: extra
Maintainer: Debian Python Modules Team 
python-modules-t...@lists.alioth.debian.org 
Uploaders: TANIGUCHI Takaki tak...@debian.org
Build-Depends: debhelper (= 8.0.0),
python-all-dev,
python3-all-dev,
python-setuptools,
python3-setuptools,
libigraph-dev,
dh-python
Standards-Version: 3.9.6
Homepage: http://igraph.sourceforge.net/
Vcs-Svn: svn://anonscm.debian.org/python-modules/packages/python-igraph/trunk/
Vcs-Browser: 
http://anonscm.debian.org/viewvc/python-modules/packages/python-igraph/trunk/

Package: python-igraph
Architecture: any
Depends: ${python:Depends}, ${shlibs:Depends}, ${misc:Depends}
Provides: ${python:Provides}
Description: High performance graph data structures and algorithms
 Python interface to the igraph high performance graph library, primarily
 aimed at complex network research and analysis.
 .
 Graph plotting functionality is provided by the Cairo library, so make
 sure you install the Python bindings of Cairo if you want to generate
 publication-quality graph plots.

Package: python3-igraph
Architecture: any
Depends: ${python3:Depends}, ${shlibs:Depends}, ${misc:Depends}
Provides: ${python3:Provides}
Description: High performance graph data structures and algorithms
 Python interface to the igraph high performance graph library, primarily
 aimed at complex network research and analysis.
 .
 Graph plotting functionality is provided by the Cairo library, so make
 sure you install the Python bindings of Cairo if you want to generate
 publication-quality graph plots.
 .
 This is the version of the package for Python 3.
#!/usr/bin/make -f

export PYBUILD_NAME=igraph

%:
	dh $@  --with python2,python3 --buildsystem=pybuild

override_dh_auto_install:
	dh_auto_install
	rm -f $(CURDIR)/debian/python-igraph/usr/bin/igraph
version=3
opts=filenamemangle=s/.*\/([^#]*)#.*/$1/ \
https://pypi.python.org/simple/python-igraph/ 
\.\./\.\./packages/source/p/python-igraph/python-igraph-(.*)\.tar\.gz.md5=.*

From: Pietro Battiston m...@pietrobattiston.it
Date: Fri, 30 Jan 2015 11:32:40 +0100
Subject: Skip tests which segfault

---
 igraph/test/atlas.py  | 1 +
 igraph/test/structural.py | 1 +
 2 files changed, 2 insertions(+)

diff --git a/igraph/test/atlas.py b/igraph/test/atlas.py
index 28410b0..062dd19 100644
--- a/igraph/test/atlas.py
+++ b/igraph/test/atlas.py
@@ -6,6 +6,7 @@ from igraph import *
 
 class TestBase(unittest.TestCase):
 def testPageRank(self):
+return
 for idx, g in enumerate(self.__class__.graphs):
 try:
 pr = g.pagerank()
diff --git a/igraph/test/structural.py b/igraph/test/structural.py
index 5e5e717..84ef31c 100644
--- a/igraph/test/structural.py
+++ b/igraph/test/structural.py
@@ -280,6 +280,7 @@ class CentralityTests(unittest.TestCase):
 self.assertAlmostEqual(cl[idx], cl2[idx], places=3)
 
 def testPageRank(self):
+return
 g = Graph.Star(11)
 cent

Bug#770153: Oops

2015-01-07 Thread Pietro Battiston 
Mike, sorry for seeing your reply now only.

You say this has a workaround, which is used by all known gedit
plugins shipped in Debian, but this sentence is false for
gedit-latex-plugin (see my last comment). Have you checked others?
Notice the bug is only triggered by a _combination_ of two plugins, so
testing each plugin separately doesn't help.

If the mere fact that nobody is working on a fix could make any given
bug non-critical, it would be s easy to release early...

Best,

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773883: unblock: fontypython/0.4.4-1.3

2014-12-24 Thread Pietro Battiston 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package fontypython

0.4.4-1.3 solves the grave bug #773579 (formally, but in fact bugs #757886 and
#757886, which had never really been fixed).

Moreover, the one-liner 0001-Do-not-crash-on-empty-pogs-list.patch solves
another grave bug (fontypython would crash if it had never been ran
successfully in the past - and yes, this is unfortunately a recursive
definition).

Attached is the debdiff since 0.4.4-1.1 (notice that 0.4.4-1.2 only introduced
a patch, which was deleted in 0.4.4-1.3).

Thanks,

Pietro

unblock fontypython/0.4.4-1.3

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
diff -Nru fontypython-0.4.4/debian/changelog fontypython-0.4.4/debian/changelog
--- fontypython-0.4.4/debian/changelog	2014-09-04 02:18:51.0 +0200
+++ fontypython-0.4.4/debian/changelog	2014-12-24 17:27:13.0 +0100
@@ -1,3 +1,19 @@
+fontypython (0.4.4-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Removed flawed patch (wx 2.8 is not in jessie)
+  * Patch: do not crash on empty pogs list
+  * Patches for compatibility with wxpython 3.0 (Closes: #773579)
+
+ -- Pietro Battiston m...@pietrobattiston.it  Sun, 21 Dec 2014 22:54:02 +0100
+
+fontypython (0.4.4-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: select wx 2.8 (rather than 3.0) (Closes: #765487)
+
+ -- Pietro Battiston m...@pietrobattiston.it  Sun, 14 Dec 2014 09:39:51 +0100
+
 fontypython (0.4.4-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch
--- fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch	1970-01-01 01:00:00.0 +0100
+++ fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch	2014-12-24 17:29:21.0 +0100
@@ -0,0 +1,21 @@
+From: Pietro Battiston m...@pietrobattiston.it
+Date: Sun, 21 Dec 2014 11:50:28 +0100
+Subject: Do not crash on empty pogs list
+
+---
+ fontypythonmodules/gui_PogChooser.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/fontypythonmodules/gui_PogChooser.py b/fontypythonmodules/gui_PogChooser.py
+index 94b7f2e..f233529 100644
+--- a/fontypythonmodules/gui_PogChooser.py
 b/fontypythonmodules/gui_PogChooser.py
+@@ -80,7 +80,7 @@ class PogChooser(wx.ListCtrl) :
+ 			i = self.FindItem(-1, select)
+ 			self.indexselected = i # Set this to help initial icon settings.
+ 			self.Select(i, True)
+-		else:
++		elif self.__poglistCopy:
+ 			self.Select(0, False)
+ 			self.indexselected = -1
+ 
diff -Nru fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch
--- fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch	1970-01-01 01:00:00.0 +0100
+++ fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch	2014-12-24 17:29:21.0 +0100
@@ -0,0 +1,134 @@
+From: Pietro Battiston m...@pietrobattiston.it
+Date: Sun, 21 Dec 2014 09:14:19 +0100
+Subject: Removed unused code which causes crash with wx 3.0
+
+---
+ fontypython| 2 --
+ fontypythonmodules/dialogues.py| 4 
+ fontypythonmodules/gui_Left.py | 4 
+ fontypythonmodules/gui_Middle.py   | 5 -
+ fontypythonmodules/gui_PogChooser.py   | 4 
+ fontypythonmodules/gui_Right.py| 4 
+ fontypythonmodules/gui_ScrolledFontView.py | 4 
+ fontypythonmodules/wxgui.py| 4 
+ 8 files changed, 31 deletions(-)
+
+diff --git a/fontypython b/fontypython
+index a05290f..e46e34e 100755
+--- a/fontypython
 b/fontypython
+@@ -72,8 +72,6 @@ else: # err code -11
+ 
+ 	## Setup wxPython to access translations : enables the stock buttons.
+ 	localedir = fontypythonmodules/locales
+-	langid = wx.LANGUAGE_DEFAULT
+-	mylocale = wx.Locale( langid )
+ 
+ 	iPC = PC.PathControl() 
+ 
+diff --git a/fontypythonmodules/dialogues.py b/fontypythonmodules/dialogues.py
+index 1fbff5f..eba7ab3 100644
+--- a/fontypythonmodules/dialogues.py
 b/fontypythonmodules/dialogues.py
+@@ -23,10 +23,6 @@ import wx
+ import wx.html as html
+ 
+ 
+-## Setup wxPython to access translations : enables the stock buttons.
+-langid = wx.LANGUAGE_DEFAULT # Picks this up from $LANG
+-mylocale = wx.Locale( langid )
+-
+ ## langcode = locale.getlocale()[0] # I must not use getlocale...
+ ## This is suggested by Martin:
+ loc = locale.setlocale(locale.LC_CTYPE) # use *one* of the categories (not LC_ALL)
+diff --git

Bug#773579: fontypython should be ported to wx 3.0 (yes, again)

2014-12-21 Thread Pietro Battiston 
Il giorno dom, 21/12/2014 alle 20.07 +, Olly Betts ha scritto:
 On Sun, Dec 21, 2014 at 12:41:19AM +0100, Pietro Battiston wrote:
  Il giorno sab, 20/12/2014 alle 10.37 +, Olly Betts ha scritto:
   On Sat, Dec 20, 2014 at 10:10:53AM +0100, Pietro Battiston wrote:
  
  [...]
  1) I and other people (a niche, but a stable niche, and if I don't
  misinterpret popcon, its 0.03% of active users locate it in the top 10%
  of debian packages) use it
 
 I think you must be misinterpreting - popcon doesn't report data about
 how much people use the packages they have installed (only if they've
 used each package recently).
 

Sorry... I'm missing the difference!

 [...]
 I tried to test the latest fontypython version (your NMU) but the
 package seems to be missing any actual python code:
 [...]

Yes, that's exactly what I meant when I said my package was useless.

 
 It looks like the assertions are due to trying to create wx.Locale
 objects before the wx.App object.  It doesn't need to create one in
 every file - just creating one should be enough.
 

No worry, the lines you deleted are apparently not needed at all.

 It then runs into the wx.ListCtrl issue you mention in the other bug.
 The simple fix is to just disable all such assertions (as happens by
 default with wx 2.8):
 
 http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README
 
 With that, fontypython runs for me - I'll send an nmudiff in a moment.
 
 It would be better to try to fix them, but I don't have time to dig
 in deeper.  If you want to, please do - or let me know if you'd like
 me to just upload my NMU.
 

I did fix the issue (patch 0003-... in the attached debdiff), but your
approach may be better suited for jessie. Most importantly, I introduced
another minimal patch to fix an annoying bug (patch 0001-...).

Feel free to upload my nmu or to only pick this last patch, as you think
is more appropriate.

Pietro
diff -Nru fontypython-0.4.4/debian/changelog fontypython-0.4.4/debian/changelog
--- fontypython-0.4.4/debian/changelog	2014-12-21 23:05:39.0 +0100
+++ fontypython-0.4.4/debian/changelog	2014-12-21 22:57:15.0 +0100
@@ -1,3 +1,12 @@
+fontypython (0.4.4-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Removed flawed patch (wx 2.8 is not in jessie)
+  * Patch: do not crash on empty pogs list
+  * Patches for compatibility with wxpython 3.0 (Closes: #773579)
+
+ -- Pietro Battiston m...@pietrobattiston.it  Sun, 21 Dec 2014 22:54:02 +0100
+
 fontypython (0.4.4-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch
--- fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch	1970-01-01 01:00:00.0 +0100
+++ fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch	2014-12-21 22:49:18.0 +0100
@@ -0,0 +1,21 @@
+From: Pietro Battiston m...@pietrobattiston.it
+Date: Sun, 21 Dec 2014 11:50:28 +0100
+Subject: Do not crash on empty pogs list
+
+---
+ fontypythonmodules/gui_PogChooser.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/fontypythonmodules/gui_PogChooser.py b/fontypythonmodules/gui_PogChooser.py
+index 94b7f2e..f233529 100644
+--- a/fontypythonmodules/gui_PogChooser.py
 b/fontypythonmodules/gui_PogChooser.py
+@@ -80,7 +80,7 @@ class PogChooser(wx.ListCtrl) :
+ 			i = self.FindItem(-1, select)
+ 			self.indexselected = i # Set this to help initial icon settings.
+ 			self.Select(i, True)
+-		else:
++		elif self.__poglistCopy:
+ 			self.Select(0, False)
+ 			self.indexselected = -1
+ 
diff -Nru fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch
--- fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch	2014-12-21 23:05:39.0 +0100
+++ fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch	1970-01-01 01:00:00.0 +0100
@@ -1,21 +0,0 @@
-From: Pietro Battiston m...@pietrobattiston.it
-Date: Sun, 14 Dec 2014 09:39:17 +0100
-Subject: Select wx 2.8 (rather than 3.0)
-

- fontypythonmodules/sanitycheck.py | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/fontypythonmodules/sanitycheck.py b/fontypythonmodules/sanitycheck.py
-index cf4fcc1..0448b6b 100644
 a/fontypythonmodules/sanitycheck.py
-+++ b/fontypythonmodules/sanitycheck.py
-@@ -31,7 +31,7 @@ except:
- 
- try:
- 	import wxversion ## Dec 2007: noticed that it may not be installed along with wxPython
--	wxversion.ensureMinimal(2.8) 
-+	wxversion.select(2.8)
- except:
- 	print strings.wxVersionError
- 	print
diff -Nru fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch

Bug#773579: fontypython should be ported to wx 3.0 (yes, again)

2014-12-21 Thread Pietro Battiston 
Il giorno dom, 21/12/2014 alle 22.58 +, Olly Betts ha scritto:
 On Sun, Dec 21, 2014 at 11:16:16PM +0100, Pietro Battiston wrote:
  Il giorno dom, 21/12/2014 alle 20.07 +, Olly Betts ha scritto:
   On Sun, Dec 21, 2014 at 12:41:19AM +0100, Pietro Battiston wrote:
Il giorno sab, 20/12/2014 alle 10.37 +, Olly Betts ha scritto:
 On Sat, Dec 20, 2014 at 10:10:53AM +0100, Pietro Battiston wrote:

[...]
1) I and other people (a niche, but a stable niche, and if I don't
misinterpret popcon, its 0.03% of active users locate it in the top 10%
of debian packages) use it
   
   I think you must be misinterpreting - popcon doesn't report data about
   how much people use the packages they have installed (only if they've
   used each package recently).
  
  Sorry... I'm missing the difference!
 
 Looking at:
 
 https://qa.debian.org/popcon.php?package=fontypython
 
 304 of the 172166 machines which report to popcon have fontypython
 installed.
 
 Of those 304:
 
 * 47 appear to have actually used the package in the past X days (I
   forget what X is)
 * 246 have it installed but haven't used it in the past X days
 * 10 have recently installed or upgraded it so information on when they
   last used it isn't available (since this is determined by looking at
   the last access times of files in the package).
 * 1 didn't report a useful atime or ctime - not sure what can cause
   that.
 
 And overall, there are 17708 packages with more reported installs and
 12444 with more reported recent uses.  That page doesn't show how many
 packages there are, but apparently jessie has about 2.
 

That's were I got it wrong... I saw ~ 400 000 lines in
http://popcon.debian.org/by_inst.gz
and thought that was the number of packages. Instead all but ~ 49 499
say Not in sid, and probably even less are in jessie.

Sorry for the OT.

   It looks like the assertions are due to trying to create wx.Locale
   objects before the wx.App object.  It doesn't need to create one in
   every file - just creating one should be enough.
  
  No worry, the lines you deleted are apparently not needed at all.
 
 If we don't create a wx.Locale at all, are the stock button labels
 localised?  I only have English locales set up so I can't trivially
 check (the call to setlocale() fails if I set LANG to a locale I don't
 have set up), but I guess you have an Italian locale set up.
 

Yes, stock buttons are indeed localized (i.e. the wx.ID_CANCEL in the
settings dialog).

The only localization initialization I see is in
fontypythonmodules/i18n.py ... maybe wx is getting the locale from
gettext?!

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773579: fontypython should be ported to wx 3.0 (yes, again)

2014-12-20 Thread Pietro Battiston 
Package: fontypython
Version: 0.4.4-1.2
Severity: grave

When I fixed #765487, I missed #757886, that is, the fact that the transition
from 2.8 to 3.0 (of fontypython) had not been spontaneous. As a consequence
of this, I assumed Depends were OK, which they are not, and the current
package is useless. As a consequence of this (probably), I also missed #755757.

(applause)

So using wx 2.8 is not an option in jessie, and the original bug must be
solved.

Olly, in #757886 you state that everything seems to be fine... can you confirm
with wxpython3.0 3.0.1.1+dfsg-2 ?



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fontypython depends on:
ii  python-imaging   2.6.1-1
ii  python-wxgtk3.0  3.0.1.1+dfsg-2

fontypython recommends no packages.

fontypython suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773579: fontypython should be ported to wx 3.0 (yes, again)

2014-12-20 Thread Pietro Battiston 
Il giorno sab, 20/12/2014 alle 10.37 +, Olly Betts ha scritto:
 On Sat, Dec 20, 2014 at 10:10:53AM +0100, Pietro Battiston wrote:
  When I fixed #765487, I missed #757886, that is, the fact that the 
  transition
  from 2.8 to 3.0 (of fontypython) had not been spontaneous. As a 
  consequence
  of this, I assumed Depends were OK, which they are not, and the current
  package is useless. As a consequence of this (probably), I also missed 
  #755757.
  
  (applause)
  
  So using wx 2.8 is not an option in jessie, and the original bug must be
  solved.
 
 Or we don't release jessie with fontypython - you say in #765487 that it
 seems pretty abandoned upstream.  It does seem like people are
 actually still using it though, judging from the comments in that
 ticket.
 

I'm reluctant for three reasons:
1) I and other people (a niche, but a stable niche, and if I don't
misinterpret popcon, its 0.03% of active users locate it in the top 10%
of debian packages) use it
2) to the best of my knowledge, there are no alternatives (i.e. programs
allowing to install a font without admin powers or messing with
shell/hidden files),
3) it works flawlessly with wx 2.8, and I expect the fix for 3.0 to be
easy.

  Olly, in #757886 you state that everything seems to be fine... can you 
  confirm
  with wxpython3.0 3.0.1.1+dfsg-2 ?
 
 Will retest it when I have a suitable machine in front of me.
 
 But the error messages in #765487 do seem to indicate how to solve the
 problem:
 
 .../src/common/stdpbase.cpp(62): assert traits failed in Get(): create 
 wxApp before calling this
 
 i.e. make sure that the wxApp object is created before this code gets
 called.
 

This is easily fixed.¹ I will try to also fix the rest,¹ but since you
reported fontypython working with wx 3.0, and since I am not a wx
expert, I was wondering whether only some systems were affected, and
why.

Pietro

¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765487#25


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773525: Randomly excludes available connections [when there are too many?]

2014-12-19 Thread Pietro Battiston 
Package: network-manager
Version: 0.9.10.0-4
Severity: grave

Copypasted from a shell:

pietro@debiousci:~$ for i in `seq 1 10`; do nmcli c | wc; done
127 637   12827
127 637   12827
127 627   12827
126 628   12726
127 629   12573
127 634   12828
127 629   12827
127 630   12319
127 631   12827
127 627   12827


I am clearly not changing my list of available connections (so quick!). So what
is happening is that network-manager is dropping some of my registered
connections, in a random way. Initially I though it is unable to handle more
than 127, but then I saw that sometimes it only lists 126. The output of
nmcli c is otherwise almost sane (see below).

Some connections show up more frequently, some less. Consider for instance:

pietro@debiousci:~$ for i in `seq 1 10`; do nmcli c | grep -i condividi; done |
sort
Condividi 8a006f93-95ac-4683-a683-56413cbb95bb
802-3-ethernet   --
Condividi 8a006f93-95ac-4683-a683-56413cbb95bb
802-3-ethernet   --
Condividi 8a006f93-95ac-4683-a683-56413cbb95bb
802-3-ethernet   --
Condividi cab18fac-376f-42cf-9349-d9b4170dacce
802-3-ethernet   --
condividi con dnsmasq d54c2a91-f654-4d52-bdbd-cf9d8efdd9e5
802-3-ethernet   --
condividi  daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi   daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --

So
- one connection, Condividi, is shown 3 times out of 10
- one connection, condividi con dnsmasq, is shown 1 time only
- one connection, condividi, is shown most of the times... with different
space paddings

Different runs of the above command will clearly give different results, but
some connections are indeed more rare - i.e. condividi con dnsmasq usually
shows in none of the 10 tries - and some exhibit (even more than 2) different
space paddings. The wireless connection I need to use at work shows up more or
less once every 100 tries. Which, by the way, is very annoying: it usually
disables autoconnect, makes it virtually impossible to use gnome-control-center
(or the GNOME 3 drop-down menu) to connect, and makes it very hard and time
consuming also with nmcli c up (nm-connection-editor is also affected).

This is why the bug is grave: in particular, if a remote server relies on
network-manager in order to connect at startup... you'd better hope it is not
too remote.

The bug was present also with 0.9.10.0-3. My rough guess is that the
problematic upgrade was located between July and September.

P.S: just for info: _most_ of the connections are dropped:
pietro@debiousci:~$ ls /etc/NetworkManager/system-connections | wc
431 8918594



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.8.12-1
ii  init-system-helpers1.22
ii  isc-dhcp-client4.3.1-5
ii  libc6  2.19-13
ii  libdbus-1-31.8.12-1
ii  libdbus-glib-1-2   0.102-1
ii  libgcrypt201.6.2-4+b1
ii  libglib2.0-0   2.42.1-1
ii  libgnutls-deb0-28  3.3.8-5
ii  libgudev-1.0-0 215-7
ii  libmm-glib01.4.0-1
ii  libndp01.4-2
ii  libnewt0.520.52.17-1+b1
ii  libnl-3-2003.2.24-2
ii  libnl-genl-3-200   3.2.24-2
ii  libnl-route-3-200  3.2.24-2
ii  libnm-glib40.9.10.0-3
ii  libnm-util20.9.10.0-3
ii  libpam-systemd 215-7
ii  libpolkit-gobject-1-0  0.105-8
ii  libreadline6   6.3-8+b1
ii  libsoup2.4-1   2.48.0-1
ii  libsystemd0215-7
ii  libteamdctl0   1.12-1
ii  libuuid1   2.25.2-3
ii  lsb-base   4.1+Debian13+nmu1
ii  policykit-10.105-8
ii  udev   215-7
ii  wpasupplicant  2.3-1

Versions of packages network-manager recommends:

Bug#773525: [Pkg-utopia-maintainers] Bug#773525: Randomly excludes available connections [when there are too many?]

2014-12-19 Thread Pietro Battiston 
Il giorno ven, 19/12/2014 alle 15.45 +0100, Michael Biebl ha scritto:
 [...]
 Am 19.12.2014 um 15:32 schrieb Pietro Battiston:
 [...]
  This is why the bug is grave: in particular, if a remote server relies on
  network-manager in order to connect at startup... you'd better hope it is 
  not
  too remote.
 
 Not really, grave means, the package is unusable, which it clearly i'snt.
 

It is hardly usable for me - it would be totally unusable for me if at
work I did not (usually) have also a cable connection, which usually
works (or maybe I just created enough copies of it? don't know...).

Except that your question below seems to imply nobody except me has many
( 127, presumably?) connections. So, OK, if it's just me I understand.
My best guess is that computers on which many connections got remembered
along the years are statistically not the same ones which are updated to
testing, but I have no data to test this hypothesis.


  The bug was present also with 0.9.10.0-3. My rough guess is that the
  problematic upgrade was located between July and September.
  
 
 Can you pinpoint the exact version please.
 

(I'm not forgetting your request, but I don't think I will manage to do
it today)


  pietro@debiousci:~$ ls /etc/NetworkManager/system-connections | wc
  431 8918594
 
 How did you generate 431 connections? Did you copy files around?
 

Yeah, I enjoy copying files around!

No.

Looking at them, I certainly have some doubles, i.e. because one
connection did not show up so I recreated it thinking it had completely
disappeared. But mostly (300) they are real connections. The oldest
ones are from 2011, which means ~ 1.5 per week... given that I travel
quite a bit, I hack quite a bit, and when I am without Internet and see
some open wireless I often try to connect, this is not a particularly
strange number.

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773264: [patch] Errors in Italian translation

2014-12-15 Thread Pietro Battiston 
Package: denemo
Version: 1.1.8-2
Severity: normal

See
http://savannah.gnu.org/bugs/index.php?43830
the patch at
http://savannah.gnu.org/bugs/download.php?file_id=32678
fixes this. I guess it will be merged upstream quickly, but if there happened
to be a new upload of denemo for Jessie, it would be nice to include it
(currently, the same label is show for two pretty different menu items).



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages denemo depends on:
ii  denemo-data 1.1.8-2
ii  guile-2.0-libs  2.0.11+1-9
ii  libasound2  1.0.28-1
ii  libatk1.0-0 2.14.0-1
ii  libaubio4   0.4.1-2+b2
ii  libc6   2.19-13
ii  libcairo-gobject2   1.14.0-2.1
ii  libcairo2   1.14.0-2.1
ii  libevdocument3-43.14.1-1
ii  libevview3-33.14.1-1
ii  libfftw3-double33.3.4-2
ii  libfluidsynth1  1.1.6-2
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-2
ii  libgc1c21:7.2d-6.4
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.1-1
ii  libgtk-3-0  3.14.5-1
ii  libgtksourceview-3.0-1  3.14.1-1
ii  libpango-1.0-0  1.36.8-2
ii  libpangocairo-1.0-0 1.36.8-2
ii  libportaudio2   19+svn20140130-1
ii  libportmidi01:184-2.2
ii  librsvg2-2  2.40.5-1
ii  librubberband2  1.8.1-6
ii  libsmf0 1.3-2
ii  libsndfile1 1.0.25-9+b1
ii  libxml2 2.9.1+dfsg1-4
ii  ttf-denemo  1.1.8-2

Versions of packages denemo recommends:
pn  alsanone
pn  denemo-doc  none
ii  lilypond2.18.2-4

denemo suggests no packages.

-- Configuration Files:
/etc/denemo/denemo.conf 1c0c9596b806fdb4c50427a03deaa6e6 [Errno 2] File o 
directory non esistente: u'/etc/denemo/denemo.conf 
1c0c9596b806fdb4c50427a03deaa6e6'

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765487: Enforcing wx 2.8

2014-12-14 Thread Pietro Battiston 
Attached is a very minimal debdiff fixing the bug by selecting 2.8 as
wx version. Since last version was an NMU I though a further one could
be appreciated, but I will wait at least a week before (asking my
sponsor to) upload, so feel free to edit and upload before.

For the records, I did spend some minutes trying to make fontypython
(which seems pretty abandoned upstream) work with wx 3.0, and those are
the results:
- to make it start, it was sufficient to remove the lines
langid = wx.LANGUAGE_DEFAULT # Picks this up from $LANG
mylocale = wx.Locale( langid )
  from each of the 7 files in which they appear (they don't seem to be
  needed)
- however, afterwards it still raised annoying errors having to do with
  selecting items in a wx.ListCtrl. I am not able to reproduce reliably,
  and it is possible they were due to different versions of wx mixing up
  in my analysis, but some error message was identical to [1], and so
  [2] convinced me that at least for now relying on 2.8 is the right
  thing to do.

Pietro

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736368
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736368#10

diff -Nru fontypython-0.4.4/debian/changelog fontypython-0.4.4/debian/changelog
--- fontypython-0.4.4/debian/changelog	2014-12-14 09:36:08.0 +0100
+++ fontypython-0.4.4/debian/changelog	2014-12-14 09:41:50.0 +0100
@@ -1,3 +1,10 @@
+fontypython (0.4.4-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: select wx 2.8 (rather than 3.0) (Closes: #765487)
+
+ -- Pietro Battiston m...@pietrobattiston.it  Sun, 14 Dec 2014 09:39:51 +0100
+
 fontypython (0.4.4-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch
--- fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch	1970-01-01 01:00:00.0 +0100
+++ fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch	2014-12-14 09:39:20.0 +0100
@@ -0,0 +1,21 @@
+From: Pietro Battiston m...@pietrobattiston.it
+Date: Sun, 14 Dec 2014 09:39:17 +0100
+Subject: Select wx 2.8 (rather than 3.0)
+
+---
+ fontypythonmodules/sanitycheck.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/fontypythonmodules/sanitycheck.py b/fontypythonmodules/sanitycheck.py
+index cf4fcc1..0448b6b 100644
+--- a/fontypythonmodules/sanitycheck.py
 b/fontypythonmodules/sanitycheck.py
+@@ -31,7 +31,7 @@ except:
+ 
+ try:
+ 	import wxversion ## Dec 2007: noticed that it may not be installed along with wxPython
+-	wxversion.ensureMinimal(2.8) 
++	wxversion.select(2.8)
+ except:
+ 	print strings.wxVersionError
+ 	print
diff -Nru fontypython-0.4.4/debian/patches/series fontypython-0.4.4/debian/patches/series
--- fontypython-0.4.4/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ fontypython-0.4.4/debian/patches/series	2014-12-14 09:39:20.0 +0100
@@ -0,0 +1 @@
+0001-Select-wx-2.8-rather-than-3.0.patch

Bug#772852: Bad PDF rendering: invalid font scale

2014-12-11 Thread Pietro Battiston 
Source: poppler
Severity: normal
Tags: upstream

See https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042
Basically, some text will appear as garbage in EasyJet boarding passes, and
possibly other documents.

This is fixed upstream, I am targeting attention to it because the fix is
pretty simple:
https://www.libreoffice.org/bugzilla/attachment.cgi?id=107478
 and so maybe a fixed version can be accepted for the January 5 deadline.



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765848: Additional info

2014-12-01 Thread Pietro Battiston 
I'm hit by the same bug, although until reading this page I had been
unable to diagnose it: in my case (Compaq 6910p, Intel Corporation
82801H (ICH8 Family) HD Audio Controller (rev 03)), when the wrong sink
(Analog out) is selected, I do hear audio from the speakers, but at a
very low volume.

I just want to add two informations:
- I'm unable to reproduce reliably, but I am quite confident that this
bug only occurred to me in coincidence with a suspend+wakeup,
- until now (since I didn't know pavucontrol would help), I worked
around this bug by plugging in and out the headphones: this always
termporarily fixes the problem.

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#768134: Plugin does not work with gedit 3.8

2014-11-23 Thread Pietro Battiston 
Il giorno dom, 23/11/2014 alle 14.07 +0100, Tobias Frost ha scritto:
 Package: gedit-latex-plugin
 Followup-For: Bug #768134
 Control: tags -1 pending
 
 Hi Pietro,
 
 I read your last message as a pending is warranted...
 (Please remove it again when I'm wrong...)
 

Right, thanks!

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#770153: Raising severity

2014-11-23 Thread Pietro Battiston 
Package: gedit
Followup-For: Bug #770153
Control: severity 770153 grave

I decided to upload gedit-latex-plugin (hence closing #768134) without
the workaround for this which is applied upstream: whichever menu is
used, as long as this bug is not solved there will be many combinations
of plugins which make gedit segfault.

So I'm raising the severity of this to grave - notice that data loss
is well possible in the case in which gedit crashes at the moment of
activating a plugin.

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#740222: Fixed in git

2014-11-22 Thread Pietro Battiston 
Thanks Jakub, I just prepared and pushed to the git repo 3.8.0-2, which
fixes this bug.¹

(I'm just waiting a couple of days for any reaction to #770153 before
uploading)

Pietro

¹
http://anonscm.debian.org/cgit/collab-maint/gedit-latex.git/log/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#768134: Ready...

2014-11-22 Thread Pietro Battiston 
3.8.0-2 is ready...
http://anonscm.debian.org/cgit/collab-maint/gedit-latex.git/log/
I'm just waiting a couple of days to see if #768134 gets fixed, then I
will upload in any case.

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#770153: gedit segfaults when one tries to extend tools-section after extending preferences-section

2014-11-19 Thread Pietro Battiston 
Package: gedit
Version: 3.14.0-2
Severity: important
Tags: upstream

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

Although the Debian latex plugin can workaround this (i.e. in the current
upstream master it uses preferences-section instead than tools-section),
the bug makes it impossible to use i.e. crypto ( http://pietrobattiston.it
/gedit-crypto - I know this particularly well since I wrote it, but I am sure
there are other cases) and Snippets together.

What is worse, if I run gedit and enable the problematic plugin, it will not
crash. But next time it will give no signs of life, and (unless I know how to
use dconf to disable the plugins, or unless I completely uninstall them) I will
not be able to start it again.

I am attaching a backtrace. Unfortunately I don't have much time now and I'm
having trouble understanding which package contains the symbols for libgedit (I
do have gedit-dev installed).



-- Package-specific info:
Active plugins:
  - 'latex'
  -  'spell'
  -  'charmap'

Plugins in $HOME:
  - file-search

Module versions:
  - glib  2.42.0
  - gtk+  3.14.4
  - gtksourceview 3.14.1
  - pygobject 2.28.6
  - enchant   1.6.0
  - iso-codes 3.57


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

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

Versions of packages gedit depends on:
ii  gedit-common   3.14.0-2
ii  gir1.2-peas-1.01.12.1-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  iso-codes  3.57-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-12
ii  libcairo-gobject2  1.14.0-2.1
ii  libcairo2  1.14.0-2.1
ii  libenchant1c2a 1.6.0-10.1
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libgirepository-1.0-1  1.42.0-2.2
ii  libglib2.0-0   2.42.0-2
ii  libgtk-3-0 3.14.4-1
ii  libgtksourceview-3.0-1 3.14.1-1
ii  libpango-1.0-0 1.36.8-2
ii  libpangocairo-1.0-01.36.8-2
ii  libpeas-1.0-0  1.12.1-1
ii  libx11-6   2:1.6.2-3
ii  libxml22.9.1+dfsg1-4
ii  python3-gi 3.14.0-1
ii  python3-gi-cairo   3.14.0-1
pn  python3:anynone

Versions of packages gedit recommends:
ii  yelp3.14.1-1
ii  zenity  3.14.0-1

Versions of packages gedit suggests:
ii  gedit-plugins  3.14.0-1

-- no debconf information
Program received signal SIGSEGV, Segmentation fault.
g_menu_model_get_n_items (model=0x0) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./gio/gmenumodel.c:492
492 /build/glib2.0-dt6trg/glib2.0-2.42.0/./gio/gmenumodel.c: File o 
directory non esistente.
(gdb) thread apply all bt 

Thread 3 (Thread 0x7fffe7fff700 (LWP 16195)):
#0  0x7707e17d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x74216ee4 in g_main_context_poll (priority=2147483647, n_fds=1, 
fds=0x7fffe00010c0, timeout=25000, context=0x8656b0)
at /build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:4076
#2  g_main_context_iterate (context=context@entry=0x8656b0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out)
at /build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3776
#3  0x74216ffc in g_main_context_iteration (context=0x8656b0, 
may_block=1) at /build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3842
#4  0x7fffec57527d in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
#5  0x7423d925 in g_thread_proxy (data=0x86d8a0) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gthread.c:764
#6  0x773520a4 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#7  0x77086cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7fffeeb75700 (LWP 16194)):
#0  0x7707e17d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x74216ee4 in g_main_context_poll (priority=2147483647, n_fds=2, 
fds=0x7fffe80010c0, timeout=-1, context=0x668e60)
at /build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:4076
#2  g_main_context_iterate (context=0x668e60, block=block@entry=1, 
dispatch=dispatch@entry=1, self=optimized out) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3776
#3  0x74217272 in g_main_loop_run (loop=0x668df0) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3975
#4  0x77894f06 in gdbus_shared_thread_func (user_data=0x668e30) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./gio/gdbusprivate.c:273
#5  0x7423d925 in g_thread_proxy (data=0x64b720) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gthread.c:764
#6  0x773520a4 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#7

Bug#768134: Plugin does not work with gedit 3.8

2014-11-05 Thread Pietro Battiston 
Package: gedit-latex-plugin
Version: 3.8.0-1
Severity: grave

The last upstream release of the plugin, 3.8, is totally useless with gedit 
(3.12 and) 3.14,
which jessie ships.

I did fix this however in upstream git, making the plugin work again:
https://git.gnome.org/browse/gedit-latex/commit/?id=9cb413d78d363d47a03bd30984cfadea79220df2
 but was not able to have a new version released and into sid in time.

I will soon upload 3.8.0-2, including the patch which updates the interface 
(together with a patch
only introducing language updates, and updated dependences solving bug 
#740222), and ask for a
freeze exception.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gedit-latex-plugin depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gedit3.14.0-2
ii  gvfs-bin 1.22.0-1+b1
ii  python-poppler   0.12.1-8.1
ii  python3  3.4.1-1
ii  python3-dbus 1.2.0-2+b3
ii  rubber   1.1+20100306-6

Versions of packages gedit-latex-plugin recommends:
pn  python-enchant  none
pn  texlive none

gedit-latex-plugin suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#767198: unblock: sqlkit/0.9.6.1-1

2014-10-29 Thread Pietro Battiston 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package sqlkit

It was removed from testing because of #725372, which is fixed in this version. 
Apart from that, it updates the sqlalchemy version supported, fixes some 
(unreported) bugs and adds documentation.

unblock sqlkit/0.9.6.1-1

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#767199: unblock: gvb/1.4-1

2014-10-29 Thread Pietro Battiston 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package gvb

This release does not add any features, it simply adapts to new gtk and python, 
fixes documentation, cleans some code, closes #722271. And it is excluded from 
the natural migration to testing by just 1 day!

unblock gvb/1.4-1

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765371: Import fails - error parsing version (fixed upstream)

2014-10-14 Thread Pietro Battiston 
Package: python-ow
Version: 2.9p5-1
Severity: grave

Trying to import ow results in

pietro@debiousci:~$ python -c import ow
Traceback (most recent call last):
  File string, line 1, in module
  File /usr/lib/python2.7/dist-packages/ow/__init__.py, line 37, in module
__version__ = _OW.version( ) + '-%s' % '$Id$'.split( )[ 2 ]
IndexError: list index out of range


The line which gives an error... couldn't really do otherwise. The problem
comes from the fact that while in previous upstream versions that line looked
like

__version__ = _OW.version( ) + '-%s' % '$Id: __init__.py,v 1.19 2013/03/24 
01:23:30 alfille Exp $'.split( )[ 2 ]

,  this was changed probably through an automatic replacement which broke
owpython in version 2.9p5.

The same applies to ownet. Attached is a patch which fixes both.

Notice that both are also fixed upstream in version 2.9p7 (exactly in the same
way as my patch). So the optimal fix would be to simply package it. But if
this can't be done in reasonable time, I could (push  2.9p5-1.1 to
collab-maint, and) try to get a new NMU sponsored with my simple patch applied.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python-ow depends on:
ii  libc62.19-11
ii  libow-2.9-5  2.9p5-1.1
ii  python   2.7.8-1

python-ow recommends no packages.

python-ow suggests no packages.

-- no debconf information
commit 64222f5788c664c15bb0f980ed170be1405c308c
Author: Pietro Battiston m...@pietrobattiston.it
Date:   Tue Oct 14 14:32:29 2014 +0200

Only return the OW version

diff --git a/debian/patches/only-return-the-OW-version.patch b/debian/patches/only-return-the-OW-version.patch
new file mode 100644
index 000..3c040be
--- /dev/null
+++ b/debian/patches/only-return-the-OW-version.patch
@@ -0,0 +1,25 @@
+From: Pietro Battiston m...@pietrobattiston.it
+Date: Tue, 14 Oct 2014 14:29:13 +0200
+Subject: Only return the OW version.
+
+The python files are currently installed without replacing some
+placeholders such as $Id$. As a consequence, the parsing (split())
+of the version number fails. This horrible hack simply disables it,
+until the real fix is implemented.
+---
+ module/swig/python/ow/__init__.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/module/swig/python/ow/__init__.py b/module/swig/python/ow/__init__.py
+index 0ed9dfd..84bc115 100644
+--- a/module/swig/python/ow/__init__.py
 b/module/swig/python/ow/__init__.py
+@@ -34,7 +34,7 @@ from ow import _OW
+ 
+ __author__ = 'Peter Kropf'
+ __email__ = 'pkr...@gmail.com'
+-__version__ = _OW.version( ) + '-%s' % '$Id$'.split( )[ 2 ]
++__version__ = _OW.version( )
+ 
+ 
+ #
diff --git a/debian/patches/series b/debian/patches/series
index 494f101..f0fe969 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -7,3 +7,4 @@ deb-specific_python-install.patch
 deb_specific__owfs-use-config.patch
 for-upstream_fix-ABI.patch
 for-upstream_owexist-manpage.patch
+only-return-the-OW-version.patch

Bug#761254: Argue your case upstream...

2014-09-16 Thread Pietro Battiston 
Il giorno sab, 13/09/2014 alle 13.26 +0200, Andreas Henriksson ha
scritto:
 [...]
 2. Convince upstream to make a new stable release.

Thanks for the clarification Andreas.

Unfortunately this has already been asked in the upstream bug¹, and
there was no reply, so there is probably not much I can do apart from
waiting.

Pietro

¹ https://bugzilla.gnome.org/show_bug.cgi?id=735953#c8 - but I only
understood after reading your message


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#726784: Works for me

2014-09-12 Thread Pietro Battiston 
I am using libgtk-3-0 3.12.2-3 and I am perfectly able to scroll
Iceweasel or the mails list in Evolution while the window in which I'm
writing this message is focused.

Either the bug was solved, or it is an IceWM bug.

Could you test with other desktop managers?

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#761254: Broken (bookmarked) gvfsd-sftp connection render several apps unusable

2014-09-12 Thread Pietro Battiston 
Package: libgtk-3-0
Version: 3.12.2-3+b1
Severity: normal
Tags: upstream

To reproduce, simply create a bookmark in nautilus for a remote sftp position,
mount it by browsing to it, and then somehow break the connection (i.e. unplug
the ethernet cable).

Result:
- evince, gedit and others no longer save
- nautilus no longer starts
- evolution no longer opens the composer

The bug was reported upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=735953
and a patch was provided:
https://bug735953.bugzilla-attachments.gnome.org/attachment.cgi?id=285251

I really think it should be applied.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable'), (500, 
'oldstable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libgtk-3-0 depends on:
ii  libatk-bridge2.0-0   2.12.1-1+b1
ii  libatk1.0-0  2.12.0-1
ii  libc62.19-10
ii  libcairo-gobject21.12.16-3
ii  libcairo21.12.16-3
ii  libcolord2   1.2.1-1
ii  libcups2 1.7.5-1
ii  libfontconfig1   2.11.0-6
ii  libfreetype6 2.5.2-1.1
ii  libgdk-pixbuf2.0-0   2.30.8-1
ii  libglib2.0-0 2.40.0-5
ii  libgtk-3-common  3.12.2-3
ii  libjson-glib-1.0-0   1.0.2-1
ii  libpango-1.0-0   1.36.6-1
ii  libpangocairo-1.0-0  1.36.6-1
ii  libpangoft2-1.0-01.36.6-1
ii  librest-0.7-00.7.12-3
ii  libsoup2.4-1 2.46.0-2
ii  libwayland-client0   1.5.0-1
ii  libwayland-cursor0   1.5.0-1
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1
ii  libxdamage1  1:1.1.4-2
ii  libxext6 2:1.3.2-1
ii  libxfixes3   1:5.0.1-2
ii  libxi6   2:1.7.4-1
ii  libxinerama1 2:1.1.3-1
ii  libxkbcommon00.4.1-2
ii  libxml2  2.9.1+dfsg1-4
ii  libxrandr2   2:1.4.2-1
ii  multiarch-support2.19-10
ii  shared-mime-info 1.3-1

Versions of packages libgtk-3-0 recommends:
ii  hicolor-icon-theme  0.13-1
ii  libgtk-3-bin3.12.2-3+b1

Versions of packages libgtk-3-0 suggests:
ii  gvfs 1.20.3-1
ii  librsvg2-common  2.40.3-2

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754296: RFP: python-jsonpointer -- python library to resolve JSON Pointers

2014-07-09 Thread Pietro Battiston 
Package: wnpp
Severity: wishlist

* Package name: python-jsonpointer
*  Version : 1.4
* Upstream Author : Stefan Kögl ste...@skoegl.net
* URL : https://pypi.python.org/pypi/jsonpointer
* License : BSD
* Programming Lang: Python
* Description : library to resolve JSON Pointers

jsonpointer is a python library to resolve JSON Pointers according to RFC 6901.

It is required by (future versions of) ipython, hence I packaged it in order to
run ipython from upstream git (success). However, I have no idea of what a JSON
pointer is, so I'm not proposing myself as maintainer. Whoever is willing to
can start from my work:
git clone git://anonscm.debian.org/collab-maint/python-jsonpointer.git


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#752674: Upstream bug

2014-07-04 Thread Pietro Battiston 
Il giorno ven, 04/07/2014 alle 07.20 +0900, Mike Hommey ha scritto:
 On Thu, Jul 03, 2014 at 03:03:40PM +0200, Pietro Battiston wrote:
  This seems quite similar to
  https://bugzilla.mozilla.org/show_bug.cgi?id=1015175
  ... but my browser does not crash with mapy.cz .
  [...]
  
  (all but the first do crash mine)
 
 Your crash is bug 751569.
 

Oops... thanks.

Pietro


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

  1   2   3   >