[Debian-med-packaging] Bug#817163: [sanvila at debian.org: Bug#817163: camitk: FTBFS when built with dpkg-buildpackage -A (191 tests failed out of 191)]

[Gianfranco Costamagna]

Hi Emmanuel,


>Thank you for your email and your files.
>I did some work on it as well, and you are right the 4.0.0 should not be 
>too difficult to package. At the moment I am concentrating on removing a 
>bug that makes camitk not usable on laptop (see #798167).


wonderful
>I did not realize that camitk was blocking the update of insight-toolkit 
>and/or vtk packages, sorry.


no problem :)
>I commited the first changes (not dissimilar to the one you send) on the 
>git master branch, but did not finished to check everything.
>As I am new to packaging using git, I will probably need more time than 
>usual to complete the package.


http://anonscm.debian.org/git/debian-med/camitk.git/tree/debian/control

just note: you can extract my debian directory, and do a git diff to see my changes

and then git add -p to select the changes you want inside or outside.
(git commit at the end)

e.g. the control file needs to be updated :=

>Unfortunately, I will not be able to work on the packaging before the 
>beginning of May.


ok

>It this is too long to wait, and you want to move on with the decruft, >please proceed with the temporary removal of camitk.
>
>Hopefully it won't be long after that to have the camitk package back on 
>sid (and on testing!)
>
>Again, thank you for your work...


the problem is: removing from testing means a new trip on NEW queue.

How do you feel about putting something in experimental just to avoid that?
a version, a snapshot, even with some bugs, at least will make the package
available for some testing, and will help in moving to vtk6/itk4 faster.

if you can put something in experimental it will be great (and count on
me as sponsor).

Otherwise to avoid the new queue we might ask ftpmasters to break the package
and to make it uninstallable until it gets fixed (I mean, removing --force
the vtk, hence making it uninstallable by default)

Sorry for the unconvenience, but vtk7 is already out there, and we still have the 5 around
since years.

stretch won't have it, so we need to work on the dependencies to make the compatible
with vtk6+
(same faith for itk).

thanks a lot!

(if you want me to commit my changes on the repo, just ask)


Gianfranco

Emmanuel

On 17/04/16 10:17, Gianfranco Costamagna wrote:
> Hi, please note that this bug is blocking the decruft of the old itk.
>
> I did import the latest beta version, and tried to build it.
> (I'm attaching the packaging to this email)
>
> Except for some failures in dh_install everything was good so far.
>
> Can you please update to the beta at least and close all the RC bugs?
>
> otherwise since we want vtk to be removed I think we will be forced to ask a
> temporary removal of this package from unstable.
>
> thanks for understanding,
>
> Gianfranco
>
> On Wed, 23 Mar 2016 08:51:40 +0100 Andreas Tille <andreas at an3as.eu> wrote:
>> Thanks for your bug housekeeping - that's really appreciated. :-)
>>
>> Kind regards
>>
>>       Andreas.
>>
>> On Wed, Mar 23, 2016 at 07:36:56AM +0100, Emmanuel Promayon wrote:
>>> Thank you to Santiago for this bug report and thank you to Andreas for the
>>> fix!
>>>
>>> Here is the patch I applied to d/rules:
>>> 78c78
>>> < override_dh_auto_test:
>>> ---
>>>> override_dh_auto_test-arch:
>>>
>>> We are now waiting for the next upstream release (planned to be released
>>> soon) and will then apply this change to the next package version.
>>> I therefore will mark this bug pending for now.
>>>
>>> Kind regards,
>>> Emmanuel
>>>
>>
>>
>>
>>> _______________________________________________
>>> Debian-med-packaging mailing list
>>> Debian-med-packaging at lists.alioth.debian.org
>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>>
>>
>> --
>> http://fam-tille.de
>>
>>