Hi,
Le 19/04/2017 à 13:10, Tim Retout a écrit :
> Hi Vincent,
>
> Just to clarify: when I run with -font 6x10, it launches, but shows
> the white GUI reported originally. So I think this should still be
> "serious"?
Ah, ok. I did not know (I did not understand correctly your remark).
I won't play anymore with the severity. Do as you wish (or wait for
the maintainer to take position).
My position is just that whatever the severity is, the bug will not
be solved more quickly. But stretch cannot be release with a package
with a RC bug, so it will be 'solved' (for stretch) by removing
the package. And it will be a global removal (the whole spim source
package) with the GUI *and* CLI programs.
As you are a user of the software (and not me), it is up to you
to judge if this bug is severe enough so that it is better to
remove the whole package from stretch (ie make this bug RC) or not
(leave this bug not RC). Modifying the severity only have this effect
(giving or not a RC bug to the package, so excluding or not the
package from stretch). Increasing the severity of a bug very rarely
makes this bug to be fixed quicker (especially for such a package
that, according to this bug, already lacks behind upstream versions)
Regards,
Vincent
> Kind regards,
>
> On 19 April 2017 at 08:29, Vincent Danjean <vincent.danj...@ens-lyon.org>
> wrote:
>> severity 860011 important
>> thanks
>>
>> Hi,
>>
>> Given that:
>> - this program has the same version has jessie (just a binary rebuild)
>> - the non-gui part seems working fine
>> - the gui part seems to have an easy workaround (xspim -font 6x10)
>> I do not think the reported bug must be release critical.
>>
>> Letting the bug RC would just mean that no spim at all would be
>> present in stretch (it is really late wrt the release and there is
>> no patch proposed), and not that a new patched package would magically
>> appear.
>> Just looking at the bug (I do not use spim myself), the GUI has
>> clearly a bug. But the core of the software works with a CLI
>> program and the GUI bug seems to have an easy workaround. So I was
>> hesitating between a normal or important severity for this bug.
>> Do not hesitate to propose a patch to the maintainer (or to help
>> him to package the new version for after stretch) if you want some
>> progress on this bug.
>>
>> Regards,
>> Vincent
>>
>> Le 18/04/2017 à 19:58, Tim Retout a écrit :
>>> severity 860011 serious
>>> thanks
>>>
>>> I can confirm the broken GUI.
>>>
>>> I had to run "xspim -font 6x10" to get it to launch, as per a comment
>>> at the end of this Ubuntu issue, a different issue to #670949:
>>> https://bugs.launchpad.net/ubuntu/+source/spim/+bug/824084
>>>
>>> Marking as 'serious' because at least the CLI program still works...
>>>
>>
>>
>> --
>> Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org
>> GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA
>> Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
>> APT repo: deb http://people.debian.org/~vdanjean/debian unstable main
>>
>
>
>
