Gitlab migration should be checked

Dear @mguenther I migrated this package according to our guide but it was a special package and it needs further modification to work here. Could you please look into it when you have the time?

• builds are not passing.
• pillow 3.2 is installed while this code requires pillow < 3.

ping @bob

I am not sure if I can help you with this. Just some details about this package, which need to be considered when changing the build infrastructure:

1. This package is just a wrapper for the PythonFaceEvaluation package, which needs to be patched, and where a local (non-public) version of it can be found here: https://gitlab.idiap.ch/biometric/PythonFaceEvaluation
2. As this package relies on an external package, the .travis.yml required special steps in order to build. These steps need to be replicated in the gitlab.ci
3. As the external package is not python 3 compatible, neither is this package. Python 3 builds will definitely fail.

@sebastien.marcel : Maybe we should move the PythonFaceEvaluation package from the biometric group to the bob group. But, please assure that this package is not made public -- I am not sure about the license of the original code that can be found here: http://www.cs.colostate.edu/facerec/algorithms/baselines2011.php)

Let me know if I can help you by providing more information on this. I am not sure if I can help you with the Gitlab migration, as I am not familiar with the whole process.

Can I generate the wheel for whatever Pillow < 3.x

I want to drop myself as a maintainer of this package since I don't use it. If I get back to using it, I might look back into it.

Come on, don't be so harsh.

Hey,

It is really difficult to fit this package on our ci. I bend the ci a lot and it is still screwed.

I think the easiest and, most important, the cleanest way to do it is to migrate the original CSU code to support Pillow >= 3. This code is too old (2012 the last release). Can we release bob.bio.base without it?

We don't have this package on conda, so does not make sense to hold this package

reference: bob.bio.base#39 (closed)

mentioned in issue bob.bio.base#39 (closed)

bob.bio.base does not depend on bob.bio.csu. We can easily publish that without bob.bio.csu.

On the other hand, bob.bio.csu depends on bob.bio.base, so when releasing a new version of bob.bio.base, we should also update bob.bio.csu. However, I don't think that we need to migrate this package to work in the GitLab CI. As you mentioned, the wrapped CSU code is from 2012, and I am not sure, how many people are using it. I think it might be OK to have this package, release a new version of it, but do not enforce it to run in the GitLab CI.

Any contrary thoughts?

Awesome @mguenther Tomorrow I will release bob.io.base, bob.bio.face, bob.bio.video, bob.bio.vein, bob.bio.spear and bob.db.bio_filelist

bob.bio.vein is private - please don't release it.

ok @andre.anjos

hey @mguenther , I squashed the commits. Now it is easy to see what I've done.

This package is working with the new bob.bio.base. Two tests are failling.

• bob.bio.csu.test.test_preprocessors.test_ldair_detect
• bob.bio.csu.test.test_preprocessors.test_lrpca_detect

The crops are slightly different

Yes, tests are passing because they need to be adapted as well. I will push a new version soon.

Mentioned in merge request !1 (merged)

Mentioned in commit 62bcdc10

marked the checklist item builds are not passing. as completed

I think we can consider this fixed. Re-open if wrong.

closed

mentioned in issue #3 (closed)