git-octopus
git-octopus copied to clipboard
lesfurets
Provide RPM and DEB packaging
I work for Kelkoo. We would like to use this project, but we need to repackage with rpm and maybe submit to fedora. Did you already do it or plan to do it? Otherwise we can. Thanks for the great job.
Absolutely great. We never did it and always wanted to. If you need any precisions on how to build the sources or need some changes on the project, let us know :)
Hi,
I heard it may be possible to have RPMs built on top of the Homebrew port. I don't remember how, but have a look at Linux Homebrew project, they may already have what you want...
Mathieu (git-octopus Homebrew (macOs) maintainer)
Le 18 nov. 2016 à 11:36, Arnaud Pflieger [email protected] a écrit :
Absolutely great. We never did it and always wanted to. If you need any precisions on how to build the sources or need some changes on the project, let us know :)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lesfurets/git-octopus/issues/24#issuecomment-261500703, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYJEGL3vpFhmq8trQZ4znG5_KhP9x4Bks5q_X-UgaJpZM4K2TeP.
I think that if you do it using fpm you will get both rpm and deb packaging
I can contact Henri Gomez or Pierre Antoine Gregoire on this if needed. I’ll be piece of cake for them ☺
Dimitri BAELI IT Associate Director
[cid:[email protected]]https://www.lesfurets.com/ 12-14 rue Médéric 75017 Paris +33 1 56 02 36 50 LesFurets.comhttps://www.lesfurets.com/ Facebookhttps://www.facebook.com/hervelesfurets - Twitterhttps://twitter.com/lesfurets
From: Denis Rampnoux [email protected] Reply-To: lesfurets/git-octopus [email protected] Date: Friday, November 18, 2016 at 11:40 AM To: lesfurets/git-octopus [email protected] Subject: Re: [lesfurets/git-octopus] rpm packaging (#24)
I think that if you do it using fpm you will get both rpm and deb packaging
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/lesfurets/git-octopus/issues/24#issuecomment-261501564, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACyNWXuwhkjTxN2o9xTydbfFF46X--IEks5q_YCZgaJpZM4K2TeP.
Thanks for the support. If nobody already did we can work on this we have experience on rpm packaging and we have allocated some time for this. We don't use .deb but could have a look at fpm.
Are you ok if we submit to fedora? Do you prefer to be the maintainer of the package?
We should provide a .deb package too... I'll look into it when I have time.
Hi everybody we submitted a review request for fedora : https://bugzilla.redhat.com/show_bug.cgi?id=1401013#c1, cross the fingers! If someone wants to install the rpm (el7,f24,f25,f26) you can get it here : https://copr.fedorainfracloud.org/coprs/baitaand/git-octopus/build/484097/ The spec file is temporary here : https://github.com/danoliv/git-octopus-spec. If the package will be approved it will be hosted on a fedora git repository.
Can we add that to the documentation? Should we wait it is hosted the fedora git repo? And how does it work when we release a new version?
Yes you can add it in the documentation, I will improve the doc on github so you can use it as reference.
Usually it is the maintainer work to prepare the rpm when a new version of the software is available, a ticket will be opened automatically in the fedora bugtracker as soon as a new tar.gz is available on github.
All this will be available after the package will be approved.
In the mean time the copr repository can be used to install the rpm, you can create an "official one" if you want to or use mine https://copr.fedorainfracloud.org/coprs/baitaand/git-octopus/.
OK I'll link your copr repository in the README and close this issue when the package is approved. Thanks!
In this case you can add this to the README: dnf copr enable baitaand/git-octopus dnf install git-octopus
What do we do when there's a new git-octopus version? Can you give me steps to release the rpm?
That makes me think we'll need our own copr repository if we don't want to be dependant on you
Added a section in the README https://github.com/lesfurets/git-octopus#rpm-package-manager
I'm working on the .deb script I'll commit it in the repo (https://www.debian.org/doc/manuals/debmake-doc/ch04.en.html)
In order to submit to fedora you need to became an official fedora maintainers (https://fedoraproject.org/wiki/Join_the_package_collection_maintainers). It is a long process, the person needs to pass a sort of screening, review or produce other packages and find a sponsor that support its application.
After the person is approved it can be the official maintainer (or the co-maintainer) of the package. At Kelkoo we are integrating git-octopus in our workflow so we are motivated to maintain/co-maintain the rpm.
I started the process by submitting the spec file for git-octopus for a review https://bugzilla.redhat.com/show_bug.cgi?id=1401013, see https://fedoraproject.org/wiki/Package_Review_Process to understand the process.
Usually the good practice is to have a separated repository for the packaging (spec files, patch, etc) and fedora will provide a git repository as soon as the package and the maintainer are approved.
I will update the documentation as soon as possible.
Again, thank a lot for doing that. By the way, did you looked at https://github.com/lesfurets/git-octopus/issues/25? I'm rewriting git-octopus in go, so the packaging will change. I think it will just be simplier
Yes, pretty cool! As soon as you have a beta version I would like to test it and to look at the packaging.
I want to announce that git-octopus (version 1.4) is on the fedora official repository : https://admin.fedoraproject.org/pkgdb/package/rpms/git-octopus/
The package is in testing at the moment, you can install it by doing: dnf --enablerepo=updates-testing install git-octopus
Thank you !
Dimitri BAELI
Le 21 mars 2017 à 15:51, Arnaud Pflieger [email protected] a écrit :
Woohoo \o/
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I have a question about the packaging: at the moment the minimum git version is 1.8, is there any particular reason for excluding git 1.7? Thanks!
This change introduced in 1.4 that fixes #16 uses an option of git merge-base that is available only on git >= 1.8
For git-octopus 2.0 though, this is not required. The case is handled without this command. The unit test TestOctopusAlreadyUpToDate checks this behavior.
Great! so from git-octopus 2 it can be compatible with git 1.7 (therefore with centos 6). Thanks!
2.0 beta1 from our private rpm repository, soon the beta2 We are waiting for the final 2.0 release to put in the officials centos and fedora repos.
So you are using 2.0 already, that's good news! The problem for the release is that we still miss a bunch of features that was implemented in 1.x