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
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
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
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
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
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
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
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
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
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~
Il giorno lun, 24/10/2016 alle 09.31 +0200, IOhannes m zmölnig ha
scritto:
> [...]
> is it possible to try the ardour5 binary provided by upstream [1] and
> see whether the problem persists?
>
I just did (with the "Free/Demo" version), and it works perfectly (with
the same session/jack
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
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
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
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
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
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
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
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
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
--
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-rc-requ...@lists.debian.org
with a subject of unsubscribe.
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:
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
Il giorno sab, 31/05/2014 alle 12.07 +0200, Domenico Iezzi ha scritto:
Hi,
FTBFS can be fixed by changing doc/build/sphinx/html to
build/sphinx/html in
debian/python-sqlkit-doc.docs
Regards,
Domenico Iezzi
Hi Domenico, thanks a lot for your patch. Unfortunately I am very busy
at the
Package: gxtuner
Version: 2.1-1
Severity: critical
The window regularly opens, but the program never shows any activity. Nothing
is written to the terminal. The two buttons allow me to change the level of
threshold and reference pitch, but nothing changes.
(on the same system, at the same time
Hi Thomas,
I had already switched to python-babel in my packaging git repo, I will
upload a new version as soon as possible.
Pietro
Il giorno sab, 05/10/2013 alle 02.55 +0800, Thomas Goirand ha scritto:
Package: python-sqlkit
Version: 0.9.5-1
Severity: serious
Hi,
I would like to
Hi Martin,
I did have fixing those bugs in my TODO list, but those are a couple of
critical months for me on the non-Debian side, so thank you very much
for the NMU.
Pietro
Il giorno gio, 29/08/2013 alle 08.29 +0200, Martin Pitt ha scritto:
tag 717680 pending
tag 718078 pending
thanks
Il giorno mar, 10/04/2012 alle 22.52 +0200, Laurent Bigonville ha
scritto:
So this cannot be reproduced anymore, upstream think it could be a GTK+ issue.
Sorry for disappearing: the requests for additional tests got lost in my
flood of mail, but I confirm the problem is solved.
Pietro
--
severity 55 minor
thanks
==
FAIL: /«PKGBUILDDIR»/shapely/tests/cascaded_union.txt
Doctest: cascaded_union.txt
--
Traceback (most recent call
Il giorno gio, 08/12/2011 alle 12.43 +0100, Jose Carlos Garcia Sogo ha
scritto:
On Sun, Dec 4, 2011 at 1:06 AM, Pietro Battiston m...@pietrobattiston.it
wrote:
[...]
At the end of this email is the output when ran in gdb, including a
backtrace.
Could you install deja-dup-dbg package
Package: deja-dup
Version: 20.2-1
Severity: grave
Deja-dup just crashes when started with the --restore argument. Backup
instead works fine.
At the end of this email is the output when ran in gdb, including a backtrace.
As far as I can tell, that could also just be a bug in libgtk...
I don't
A working package with the fix suggested by Paul is here:
http://mentors.debian.net/package/deja-dup
with that I don't mean it's time/I'm entitled for a NMU (though some ETA
on producing the ETA would be appreciated - that's maybe the most
popular desktop backup software, and it's
Sorry, in the above description I linked to the wrong bug: the right one
is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614192
Pietro
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: xournal
Version: 0.4.5-2
Severity: serious
Justification: fails to build from source
Xournal currently FTBFS. Here is the relevant part of the build log:
[...]
gcc -Wall -g -O2 -Wl,--as-needed -o xournal main.o xo-misc.o xo-file.o xo-
paint.o xo-print.o xo-support.o xo-interface.o
Il giorno ven, 12/11/2010 alle 13.46 +0100, Moritz Muehlenhoff ha
scritto:
On Mon, Nov 08, 2010 at 11:08:38AM +0100, Pietro Battiston wrote:
I didn't forget this, it's just harder than I thought, in particular
considering I have no cloud computing experience and account.
I'm still
I didn't forget this, it's just harder than I thought, in particular
considering I have no cloud computing experience and account.
I'm still committed to fix it (and also asked for help upstream), but
have no precise idea of the time it will take. In particular, any help
is appreciated.
Pietro
Il giorno dom, 31/10/2010 alle 21.01 +0100, Moritz Muehlenhoff ha
scritto:
On Thu, Oct 21, 2010 at 09:57:50AM +0200, Pietro Battiston wrote:
I wrote Soren 8 days ago informing him that I could take of that.
I'll soon submit a patch.
What's the status?
That I'll soon submit a patch.
OK
I wrote Soren 8 days ago informing him that I could take of that.
I'll soon submit a patch.
Pietro
signature.asc
Description: This is a digitally signed message part
As far as I can tell,
1) this is fixed upstream
http://trac.sagemath.org/sage_trac/attachment/ticket/6927/6927-disk_cache-ref.patch
(and in the last upstream release)
2) the (upstream) patched file is the only one currently importing
processing ( sage/parallel/decorate.py already imports
Package: jokosher
Version: 0.11.3-1
Severity: serious
Justification: Policy 12.5
I think I checked the Jokosher tarball throughly, and found absolutely no
reference to the fact that Jokosher would be GPL v. 2+.
debian/copyright instead states so.
Now: it's true that the GPL itself states that
Package: drgeo
Version: 1.1.0-1
Severity: grave
Tags: patch
Justification: renders package unusable
drgeo 1.1.0-1 actually seems to work, in Lenny, just by luck, but if
recompiled with a more modern gcc, i.e. the one found in Sid (or in Ubuntu
Intrepid), it sistematically segfaults.
The bug
41 matches
Mail list logo