Bug#1050462: gtg: crashes on startup often

2023-09-03 Thread François Mazen
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 both methods in
GTG/gtk/general_preferences.py

For now, I've followed the upstream advice to revert the behavior to get a
default font when font_name is not available, hence by-passing the two
problematic methods. I've just committed the patch [1], and I'll likely upload a
new package shortly to prevent package removal.

Let me know if this sounds acceptable to you.

Best,
François

[1]
https://salsa.debian.org/python-team/packages/gtg/-/commit/e9ac644f40629704a4e85b56ff887a59d6748d58


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


Bug#1050462: gtg: crashes on startup often

2023-08-25 Thread François Mazen
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 [browser] section of the
~/.config/gtg/gtg.conf config file.

I've checked the fix and no more crash occurs, so it could be integrated as a
quilt patch for the Debian package.

Best Regards,
François


[1]
https://github.com/getting-things-gnome/gtg/issues/961#issuecomment-1475321154


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


Bug#1037579: Patch for FTBFS

2023-07-28 Thread François Mazen
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 Mazen 
Description: Fix fail to build from source due to missing header with GCC13.
Forwarded: not-needed

--- a/src/armnnUtils/VerificationHelpers.hpp
+++ b/src/armnnUtils/VerificationHelpers.hpp
@@ -4,6 +4,7 @@
 //
 
 #include 
+#include 
 #include 
 
 #include 
--- a/include/armnn/profiling/ISendTimelinePacket.hpp
+++ b/include/armnn/profiling/ISendTimelinePacket.hpp
@@ -6,6 +6,7 @@
 #pragma once
 
 #include 
+#include 
 #include 
 #include 
 


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


Bug#1023229: f3d: autopkgtest regression on s390x: Compare with ref failed

2022-10-31 Thread François Mazen
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






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


Bug#1021566: fixed in opencascade 7.6.3+dfsg1-4

2022-10-22 Thread François Mazen
Thanks Tobias for the quick fix!
François



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


Bug#1016598: binoculars: vtk[6,7] removal

2022-10-15 Thread François Mazen
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,
François

[1] https://salsa.debian.org/science-team/binoculars
[2] https://mentors.debian.net/package/binoculars/


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


Bug#992924: freefem++: autopkgtest failure on arm64/ppc64el

2021-08-25 Thread François Mazen
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]: https://nm.debian.org/process/920/approval/



Bug#992381: freefem++: missing comma in Uploaders field

2021-08-18 Thread François Mazen
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
> X-Debbugs-CC: Francois Mazen 
> 
> freefem++ 4.9+dfsg1-1 introduced an invalid uploaders field, that is
> missing a comma between Ricardo Mones & Joseph Nahmias.
> 
>    $ apt-cache showsrc freefem++ | grep -E '^$|^Version|^Uploaders'
>    Version: 3.61.1+dfsg1-6
>    Uploaders: Christophe Trophime
> , Dimitrios Eftaxiopoulos
> 
>    
>    Version: 4.9+dfsg1-1
>    Uploaders: Christophe Trophime
> , Dimitrios Eftaxiopoulos
>  Francois Mazen 
> 
> According to Debian policy 5.6.3 the Uploaders field must separate
> individual uploaders using commas:
> 
>    List of the names and email addresses of co-maintainers of the
>    package, if any. ... The format of each entry is the same as that
> of
>    the Maintainer field, and multiple entries must be comma
> separated.
>   
> https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders
> 



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


Bug#967212: solfege: Unversioned Python removal in sid/bullseye

2020-08-04 Thread François Mazen
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




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


Bug#941537: Solfege removal

2019-11-11 Thread François Mazen
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
Description: This is a digitally signed message part


Bug#901148: timidity: Timidity needed by solfege

2019-07-31 Thread François Mazen
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 Solfege and check that timidity-daemon 
is not installed (timidity "suggests" timidity-daemon so it should not
be installed automatically).

Best,
François



Bug#920639: solfege: Does not start

2019-01-28 Thread François Mazen
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, the browser does will freeze solfege until
 # I close the browser window.
 try:
+webbrowser.get()
 i = webbrowser._tryorder.index("x-www-browser")
 webbrowser._tryorder.append(webbrowser._tryorder[i])
 del webbrowser._tryorder[i]

A patch is attached, and I'll generate a new package as soon as
possible.

Best Regards,
François


--- a/solfege/mainwin.py
+++ b/solfege/mainwin.py
@@ -25,6 +25,7 @@
 # debian etch system, the browser does will freeze solfege until
 # I close the browser window.
 try:
+webbrowser.get()
 i = webbrowser._tryorder.index("x-www-browser")
 webbrowser._tryorder.append(webbrowser._tryorder[i])
 del webbrowser._tryorder[i]


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


Bug#898075: jack: segfaults at start

2018-08-27 Thread François Mazen
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 fixes the issue, and a patch is attached to this message.

I think it's a viable solution because according to the documentation
in the cursesmodule folder [1], the jack_cursesmodule is an old binding
of ncurses: version 1.5b1 from before the release of python 2.0 [2]
(see the version number at the beginning of jack_cursesmodule.c [3]).
So, using the official binding from python is a much more reliable
solution.

In addition, I can provide a non-maintainer upload for this package and
eventually maintain the package.

Best Regards,
François

[1] 
https://sources.debian.org/src/jack/3.1.1+cvs20050801-29.2/cursesmodule/README.cursesmodule/
[2] https://invisible-island.net/ncurses/ncurses-python.html
[3] 
https://sources.debian.org/src/jack/3.1.1+cvs20050801-29.2/cursesmodule/jack_cursesmodule.c/


Author: Francois Mazen 
Description: remove jack_cursesmodule, an obsolete curses binding
Bug-Debian: https://bugs.debian.org/898075

--- a/setup.py
+++ b/setup.py
@@ -13,11 +13,6 @@
 url = "http://www.home.unix-ag.org/arne/jack/;,
 
 # Description of the modules and packages in the distribution
-ext_modules = [ Extension('jack_cursesmodule',
-['cursesmodule/jack_cursesmodule.c'], libraries=["ncursesw"],
-include_dirs=["/usr/include/ncursesw"],
-extra_compile_args=["-Wno-strict-prototypes"]) ],
-
 py_modules = [ 'jack_CDTime', 'jack_TOC', 'jack_TOCentry', 'jack_argv',
 'jack_checkopts', 'jack_children', 'jack_config', 'jack_constants',
 'jack_display', 'jack_encstuff', 'jack_freedb', 'jack_functions',