fixed
What should we do next? I assume all issues fixed on github.
hello, can anyone help to continue?
hello, do we have any updates on the status?
@tolyadouble please submit a PR for rpm and/or debian packages to https://github.com/theforeman/foreman-packaging/tree/rpm/develop or https://github.com/theforeman/foreman-packaging/tree/deb/develop respectively. Both branches contain instructions on how to proceed with adding new packages to repositories.
Thanks, PR merged. Does it mean all ready / or do we need to do additional?
Sorry all, Iāve been on some extended leave and lost track of this. Where are we at? I see packages in the nightly repo - is there anything more to handle?
@tolyadouble thanks so much for your contributions - and your patience. It shouldnāt take this long to get plugins moved over, so Iāll be taking some notes to figure out how we can improve the process
Thanks @Gwmngilfen . Yes, latest thing we moved the package to the nightly repo.
Will be great if we can see it in - List of Smart-Proxy Plugins - Foreman and foreman-installer tool
Is it possible to do?
Itās a wiki so feel free to add it, or if youāre uncomfortable I can do it tomorrow. Thanks!
Updated. I also noticed that here https://github.com/theforeman/foreman-packaging/tree/rpm/1.17 we have old version 1.4, will it be updated automatically?
1.0.4 I guess you mean
No, thereās no automatic update - the packagers have no easy way to know what Foreman/Proxy versions a new release supports, so itās up to the authors to ask for the build to happen on the right versions. In this PR I see you only ticked nightly, so thatās what happened. If itās suitable for 1.17 then Iām sure the @packaging team can queue a build for you.
correct. Yes, it will be great if we can merge it to 1.17, should I write to someone in @packaging ? I also prepared *.deb package and create PR ( ticked nightly and 1.17 for this ).
Thanks for your help