[Debian-astro-maintainers] Bug#786715: stellarium: Uses private copies of external headers

Thibaut Paumard thibaut at debian.org
Tue Jun 2 08:07:30 UTC 2015


Le 01/06/2015 21:20, Sune Vuorela a écrit :
> On Monday 01 June 2015 16:21:59 Thibaut Paumard wrote:
>> Le 24/05/2015 20:46, Sune Vuorela a écrit :
>>> Source: stellarium
>>> Version: 0.13.3-1
>>> Severity: serious
>>
>> Hi,
>>
>> I think the severity of this bug is overstated. There is no reason why
>> this should warrant removing stellarium from testing.
> 
> It is fragile and broken and just waiting to fall apart.
> 
>> Upstream is working on the issue, I suggest downgrading the severity to
>> "normal" or "important" at most.
> 
> 3) in my case would have been 'normal' or 'important', but the fact that it 
> uses *its own* copy of headers and the actual symbols from Qt is just broken.
> Had it at least used it's own copy of qzip.cpp,  we could have started a 
> discussion, but this isn't the case. (src/CMakeLists.txt in the archive 
> contains IF(!WIN32), and given it is more or less nonsense from a cmake pov, 
> it just evaluates to false. IF(NOT WIN32) would likely have given closer to 
> expected behaviour )
> 
> /Sune
> 

Hi,

Quoting: https://www.debian.org/Bugs/Developer.en.html#severities

serious
    is a severe violation of Debian policy (roughly, it violates a
    "must" or "required" directive), or, in the package maintainer's or
    release manager's opinion, makes the package unsuitable for release.

In this instance, I fail to see which section of the Policy is being
violated.

Anyway, the bug is going to be resolved soon. The only difference
between the important and serious severities at the moment is whether or
not stellarium will be removed from testing and loose exposure to beta
testers.

Kind regards, Thibaut.



More information about the Debian-astro-maintainers mailing list