On 09/04/2016 11:07 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
> On domingo, 4 de septiembre de 2016 10:53:46 P. M. ART Sebastiaan Couwenberg 
> wrote:
>> On 09/04/2016 10:45 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
>>> Passing -c0 is definitely not the way to go. Please remove the current
>>> upload from the delayed queue.
>>
>> I will cancel the upload if you confirm to upload a different fix to
>> prevent the testing autoremoval.
> 
> Please go ahead, i'll fix this.

Thanks! I've cancelled my upload.

>> I do not agree that "passing -c0 is definitely not the way to go". This
>> is the second RC bugreport because of changed symbols due to GCC
>> upgrades. A more permanent fix is needed, especially since this package
>> is not actively maintained as Gudjon recently confirmed.
> 
> I have actually started my notebook to add more info to the mail I have just 
> sent from my phone, but you where quicker ;-)
> 
> The problem is that passing -c0 actually might hide worst bugs like API/ABI 
> breakages. If you want a rock-solid stable you need to really deal with 
> symbols changes. Like it or not, that's the correct way to go.

I definitely don't like it, so I take my chances with the C++ packages I
use symbols files for.

I agree that verifying the symbols changes is better, but I'm not
willing to put in the effort required. Plus my C++ skills are not that
great, so it's hard for me to judge what's a ABI break and what's not.

> Now QWT also really needs better maintainership, but that's another story. 
> Maybe we should remove it from testing before the freeze?

Definitely not. Removing QWT and its rdeps from testing is out of the
question for me. I've spent a great amount of effort to keep QGIS in
stretch, having it removed due to its essential qwt dependency would
seriously ruin my mood not to speak of more serious actions I'd then
consider.

As we discussed in the previous RC bug (#830329), I'd rather not become
the sole maintainer of qwt in Debian, but it is in need of team
maintenance. Perhaps we should join forces in a pkg-qwt team on Alioth?

I've also considered moving qwt to the Debian GIS team where I do pretty
much all my work and where qgis is maintained as well. While qwt is not
really a GIS nor OSM related package, it saves the hassle of a separate
team. I've also considered the Qt/KDE as a reasonably appropriate team
for collaborative maintenance of qwt, but I expect the team to not
consider it very appropriate either.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to