Hello,
apparently the character string generated in jack_cursesmodule that is
passed to ncurses is invalid. I can't figure why this happen but I
suspect an issue in the python binding in jack_cursesmodule.
Hopefully you can bypass jack_cursesmodule to use the built-in ncurses
python binding.
It
Hello,
thanks a lot for reporting this issue.
It seems that the behavior of python3 webbrowser module changed with
python 3.7.2 release.
A simple fix is to call webbrowser.get() before using the module.
--- a/solfege/mainwin.py
+++ b/solfege/mainwin.py
@@ -25,6 +25,7 @@
# debian etch system,
Hi Alain,
> I upgraded from Stretch to Buster and sound completely disappeared.
> Removing Timidity fixed the problem but made me unable to use gnu
> solfege as it
> depends on timidity.
The sound is broken by timidity-daemon, not the timidity package
itself.
So you should try to install GNU
Hello,
Lilypond and Solfege packages will be removed in about 14 days.
As maintainer of Solfege, this will affect my work.
Do you plan tu upload a new Lilypond package to avoid the automatic
removal?
If not, I can prepare a NMU. Just let me know.
Thanks,
François
signature.asc
Hello Matthias,
the python2 dependency may be dh-python, but I doubt it actually
depends on python2 because there is no dh-python3 package.
As indirect dependency, lilypond package depends on python2.
Could you please confirm that this bug is only because of lilypond?
Thanks,
François
Hello Adrian,
thanks for making the failures visible with this bug.
I'm waiting for my access to porter boxes [1] in order to debug and fix
the issue(s).
In the meantime, do not hesitate to provide patch or any kind of help.
Best Regards,
François
[1]:
Hi Paul,
thanks for the notification about the error in the uploaders field!
Should be fixed with the 4.9+dfsg1-2 version.
Have a nice day,
François
Le mercredi 18 août 2021 à 10:14 +0800, Paul Wise a écrit :
> Source: freefem++
> Version: 4.9+dfsg1-1
> Severity: serious
> Usertags: uploaders
Hi Antonio,
> We probably want to fix the code to *not* segfault when the workaround
> is not in place.
Agreed!
> I'm not sure whether this is a bug in gtg itself, or
> in pango.
The issue is likely in the g_object_get_property or in
pango_font_description_to_string, or in the code calling
Dear Antonio,
thanks for the crash report! I can reproduce it easily with unstable
distribution and the call stack points to pango_font_description_to_string
method.
The issues seems to have been already reported upstream [1] and the suggested
worj around is to add "font_name = Sans 11" in the
Thanks Tobias for the quick fix!
François
signature.asc
Description: This is a digitally signed message part
Hello,
I've pushed the modification to the salsa repo [1] and I've uploaded a
NMU package to mentors [2].
VTK is used in the tests, so I had to keep the package python3-vtk9.
Could you please review the code and upload?
Additional request: could you enable CI on the salsa repo?
Thanks,
Hello Paul,
thanks for reporting the issue, I've investigated and this is an Assimp
problem that I've reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023212
The big endian architecture may be the root of the issue, thanks for
pointing that out.
Best Regards,
François
tags 1037579 + patch
thanks
Dear maintainers,
please find attached a patch to fix the FTBFS with gcc13. The main
issue was missing headers for the uint32_t and uint64_t definitions.
I can prepare an NMU in case you don't have time to upload new package.
Best Regards,
François
Author: Francois
13 matches
Mail list logo
