Conda package resolution seems broken

Not sure when it started, but we are currently facing package resolution problems in several places.

Examples:

• https://gitlab.idiap.ch/bob/bob.learn.tensorflow/pipelines/35806
• https://gitlab.idiap.ch/bob/bob.learn.em/pipelines/35872

The only thing we noticed was a change in the patch version of conda-build.

Could this be problem?

@amohammadi: any clues?

mentioned in merge request !132 (merged)

After rebuilding bob.conda to allow all packages produce .conda versions, bob.learn.em is building OK (https://gitlab.idiap.ch/bob/bob.learn.em/pipelines/35977)

assigned to @andre.anjos

After bob.learn.em was successful, bob.learn.tensorflow pipelines are also back to normal: https://gitlab.idiap.ch/bob/bob.learn.tensorflow/pipelines/35978

Closing this ticket.

closed

Situation has deteriorated again to its previous state:

• Nightlies are green: https://gitlab.idiap.ch/bob/bob.nightlies/pipelines/35993, but
• bob.learn.em: https://gitlab.idiap.ch/bob/bob.learn.em/pipelines/36000
• bob.learn.tensorflow: https://gitlab.idiap.ch/bob/bob.learn.tensorflow/pipelines/35999

Somehow, the key to solve this is passing through bob.learn.em. There is some unbalancing of the force on that package.

reopened

@andre.anjos have you tried deleting all the betas and try from scratch?

Hey pipelines seem to be working again and they are much faster as well: https://gitlab.idiap.ch/bob/bob.pad.base/-/jobs/184251

Thanks for the feedback. I relaunched bob.learn.em (https://gitlab.idiap.ch/bob/bob.learn.em/pipelines/36124) let's see if that works as well before closing.

I did not try removing all betas before running the nightlies.

bob.learn.em continues to fail: https://gitlab.idiap.ch/bob/bob.learn.em/-/jobs/184403

With respect to bob.learn.em, one thing that I don't understand in the conflicts is the reference with bob.db.iris. Where is this come from?

https://gitlab.idiap.ch/bob/bob.learn.em/-/jobs/184404

Package bob.extension conflicts for:
bob.core[version='>=2.2.4b.0,<3.0a0'] -> bob.extension[version='>=4.0.0b.0,<5.0a0']
bob.blitz[version='>=2.0.20b.0,<3.0a0'] -> bob.extension[version='>=4.0.0b.0,<5.0a0']
bob.learn.activation[version='>=2.0.15b.0,<3.0a0'] -> bob.extension[version='>=4.0.0b.0,<5.0a0']
bob.sp[version='>=2.0.15b.0,<3.0a0'] -> bob.extension[version='>=4.0.0b.0,<5.0a0']
bob.learn.linear[version='>=2.1.7b.0,<3.0a0'] -> bob.extension[version='>=4.0.0b.0,<5.0a0']
bob.extension[version='>=4.0.0b.0,<5.0a0']
bob.math[version='>=3.1.5b.0,<4.0a0'] -> bob.core[version='>=2.2.4b.0,<3.0a0'] -> bob.extension[version='>=4.0.0b.0,<5.0a0']
bob.db.iris -> bob.db.base[version='>=3.0.1,<4.0a0'] -> bob.extension[version='>=2.5.0,<3.0a0|>=3.1.0,<4.0a0|>=3.1.1,<4.0a0|>=3.1.2,<4.0a0|>=3.1.2b.0,<4.0a0|>=3.2.0,<4.0a0']**
bob.io.base[version='>=3.0.7b.0,<4.0a0'] -> bob.extension[version='>=4.0.0b.0,<5.0a0']

mmm, bob.db.iris is coming from our docs and it's a test dependency

I don't understand why iris is requested at runtime

Hey @andre.anjos,

It seems that the issue is with bob.db.iris, check https://gitlab.idiap.ch/bob/bob.learn.em/-/jobs/184523

I don't understand why bob.db.iris is being requested at runtime

I cannot get conda to automatically update itself in a conda install command. Maybe we should run a conda update conda command before anything else to get the latest version. Anyways, everything seems to work now so I reverted most of my commits excepts for adding --update-specs.

Please reopen this issue if this comes back.

closed

There, broken again:

https://gitlab.idiap.ch/bob/bob.learn.em/-/jobs/184669

This problem is not understood, or solved!

reopened