In order to on-board packit into anaconda, there are several actions to do it. Workflow anaconda process is: * Release and push a tag into Github * tag translations into Github from Zanata. Based on the discussion, it would be good to split translations. How does it look like .packit.yaml? https://github.com/packit-service/packit/blob/master/docs/configuration.md How to test packit in anaconda? https://github.com/packit-service/packit/blob/master/docs/propose_update.md Basically, in your upstream repository create .packit.yml and install packit package. I guess you will need to install also ogr `pip3 install ogr`
Did you have a chance to try packit? Do you have any progress?
(In reply to Petr Hracek from comment #1) > Did you have a chance to try packit? > Do you have any progress? There were some bigger items to land & some F30 related work, but I plan to finally start on this during next week. Will let you know if I hit any issues. :)
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
The changes will likely happen first on Rawhide, so switching back.
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
PR: https://github.com/rhinstaller/anaconda/pull/2359 I've created PR with Packit configuration. However, we are missing dependencies on a Packit service side. See https://github.com/rhinstaller/anaconda/pull/2359#issuecomment-595207860. We are blocked by this right now. Should I create an upstream issue or do we want to solve it here?
I'm so sorry, this has completely fallen off my radar. What dependencies do you need to be installed? From the logs, I can see glib-devel only. I'll hand this to my peer Franta, who is Community master for our current sprint :)
Honestly, I don't know which dependencies. It depends on the environment. I can give you the list if I would know what is the base image. The list have to be created error-by-error :(.
This is minimal set of dependencies based on an empty mock for fedora-rawhide. libtool glib2-devel gettext-devel git python3-polib python3-pocketlint However, it could change in the future. Maybe the best way would be to have something like requirements.txt, so the project can give you a list of dependencies or to specify those in the packit.yml file would be best solution.
Thanks for the list. > libtool > python3-pocketlint These are already there. > glib2-devel > gettext-devel > python3-polib I will add those. (https://github.com/packit-service/sandcastle/pull/60) > git There is already a git-core, is it enough? > However, it could change in the future. Maybe the best way would be to have > something like requirements.txt, so the project can give you a list of > dependencies or to specify those in the packit.yml file would be best > solution. Yes, this is definitely not a final solution. We need to figure out, how can we achieve this to not break the sandboxing.
Seems that the git-core should be enough for us.
Packit is now on-boarded on Anaconda. Thanks a lot for all your help packit team!