Hello, I've submitted a while ago a review-request on a package [0] that is taken from bitbucket.org. Unfortunately there was no reviewer yet, and I suspect that is because unlike github [1] we have no rules on how to handle bitbucket. Have other packagers experienced something similar in other software? Is there a "good" way to handle repository-distributed software? As it is now in [0] I've tried to simulate the github rules on bitbucket.
regards, Nikos
[0]. https://bugzilla.redhat.com/show_bug.cgi?id=1062282 [1]. https://fedoraproject.org/wiki/Packaging:SourceURL#Github
Seems like bitbucket uses unversioned tar ball, not the best approch
https://bitbucket.org/yarosla/httpress/get/tip.tar.gz
I would make my own tarball from the git checkout and document in the spec how to make it
https://fedoraproject.org/wiki/Packaging:SourceURL#Using_Revision_Control
Tim
On Wed, Feb 26, 2014 at 10:16 AM, Nikos Mavrogiannopoulos nmav@redhat.comwrote:
Hello, I've submitted a while ago a review-request on a package [0] that is taken from bitbucket.org. Unfortunately there was no reviewer yet, and I suspect that is because unlike github [1] we have no rules on how to handle bitbucket. Have other packagers experienced something similar in other software? Is there a "good" way to handle repository-distributed software? As it is now in [0] I've tried to simulate the github rules on bitbucket.
regards, Nikos
[0]. https://bugzilla.redhat.com/show_bug.cgi?id=1062282 [1]. https://fedoraproject.org/wiki/Packaging:SourceURL#Github
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
На 26.02.2014 12:11, Tim Lauridsen написа:
Seems like bitbucket uses unversioned tar ball, not the best approch
https://bitbucket.org/yarosla/httpress/get/tip.tar.gz
I would make my own tarball from the git checkout and document in the spec how to make it
For example:
https://bitbucket.org/david/django-storages/get/8f043afb500b4e9bfc6ed27d5225...
-- Alex
On 26.02.2014 10:16, Nikos Mavrogiannopoulos wrote:
Hello, I've submitted a while ago a review-request on a package [0] that is taken from bitbucket.org. Unfortunately there was no reviewer yet, and I suspect that is because unlike github [1] we have no rules on how to handle bitbucket. Have other packagers experienced something similar in other software? Is there a "good" way to handle repository-distributed software? As it is now in [0] I've tried to simulate the github rules on bitbucket.
regards, Nikos
[0]. https://bugzilla.redhat.com/show_bug.cgi?id=1062282 [1]. https://fedoraproject.org/wiki/Packaging:SourceURL#Github
FWIW, this is how eigen does it:
# Source file is at: http://bitbucket.org/eigen/eigen/get/3.1.3.tar.bz2 # Renamed source file so it's not just a version number Source0: eigen-%{version}.tar.bz2
Sandro
Hi,
Maybe we should add guidelines for bitbucket. That could be very similar to github's template:
=== %global owner $OWNER %global tag $TAG %global commit $COMMIT %global shortcommit %(c=%{commit}; echo ${c:0:12})
...
Source0: https://bitbucket.org/%%7Bowner%7D/%%7Bname%7D/get/%%7Btag%7D.tar.gz
...
%prep %setup -qn %{owner}-%{name}-%{shortcommit} ===
I have tested this sucessfully with one (mercurial) package where $TAG is %{version}.
What do you think ?
Dridi
On Wed, Feb 26, 2014 at 11:19 AM, Sandro Mani manisandro@gmail.com wrote:
On 26.02.2014 10:16, Nikos Mavrogiannopoulos wrote:
Hello, I've submitted a while ago a review-request on a package [0] that is taken from bitbucket.org. Unfortunately there was no reviewer yet, and I suspect that is because unlike github [1] we have no rules on how to handle bitbucket. Have other packagers experienced something similar in other software? Is there a "good" way to handle repository-distributed software? As it is now in [0] I've tried to simulate the github rules on bitbucket.
regards, Nikos
[0]. https://bugzilla.redhat.com/show_bug.cgi?id=1062282 [1]. https://fedoraproject.org/wiki/Packaging:SourceURL#Github
FWIW, this is how eigen does it:
# Source file is at: http://bitbucket.org/eigen/eigen/get/3.1.3.tar.bz2 # Renamed source file so it's not just a version number Source0: eigen-%{version}.tar.bz2
Sandro
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Sun, Mar 2, 2014 at 9:04 PM, Dridi Boukelmoune dridi.boukelmoune@gmail.com wrote:
Hi,
Maybe we should add guidelines for bitbucket. That could be very similar to github's template:
=== %global owner $OWNER %global tag $TAG %global commit $COMMIT %global shortcommit %(c=%{commit}; echo ${c:0:12})
...
Source0: https://bitbucket.org/%%7Bowner%7D/%%7Bname%7D/get/%%7Btag%7D.tar.gz
...
%prep %setup -qn %{owner}-%{name}-%{shortcommit} ===
I have tested this sucessfully with one (mercurial) package where $TAG is %{version}.
What do you think ?
It's acceptable, only.
We should teach SCM to work with VCS instead of writing lines of things which need to be updated everytime.
Bitbucket has downloads support.
Also you can get the tarball from the tags.
What's the problem?
On Wed, Feb 26, 2014 at 11:21 AM, Christopher Meng cickumqt@gmail.comwrote:
Bitbucket has downloads support.
Also you can get the tarball from the tags.
What's the problem?
The problem with this project is that there is no release tags, so you cant get a specific version, just download the current master this is not very usefull for a fedora package.
Tim
На 26.02.2014 13:00, Tim Lauridsen написа:
On Wed, Feb 26, 2014 at 11:21 AM, Christopher Meng cickumqt@gmail.comwrote:
Bitbucket has downloads support.
Also you can get the tarball from the tags.
What's the problem?
The problem with this project is that there is no release tags, so you cant get a specific version, just download the current master this is not very usefull for a fedora package.
Tim
Tim, tip at the moment is commit d8c968c so to download this place the commit number instead of the tag name "tip" in the download url. For example:
https://bitbucket.org/yarosla/httpress/get/d8c968c.tar.gz
-- Alex
On Feb 26, 2014 7:00 PM, "Tim Lauridsen" tim.lauridsen@gmail.com wrote:
The problem with this project is that there is no release tags, so you
cant get a specific version, just download the current master
this is not very usefull for a fedora package.
You can ask them to tag it from now on. I always do that.