Pete Zaitcev zait...@redhat.com writes:
On Mon, 23 Apr 2012 14:08:05 -0600
Orion Poplawski or...@cora.nwra.com wrote:
%global commit bd245c9
Source0:
https://github.com/jukka/pcfi/tarball/%{commit}/jukka-pcfi-%{commit}.tar.gz
%setup -q -n jukka-pcfi-%{commit}
I do not understand how
On Mon, 23 Apr 2012 14:08:05 -0600
Orion Poplawski or...@cora.nwra.com wrote:
%global commit bd245c9
Source0:
https://github.com/jukka/pcfi/tarball/%{commit}/jukka-pcfi-%{commit}.tar.gz
%setup -q -n jukka-pcfi-%{commit}
I do not understand how this is supposed to work in the face of
yum
On Wed, 2012-06-13 at 11:45 -0600, Pete Zaitcev wrote:
Suppose I cut a package last year:
swift3-1.0.0-878c23.tag.xz
Then I build an RPM:
openstack-swift-plugin-swift3-1.0.0-878c23-1.fc17.noarch.rpm
Today I run the same git-archve and get:
swift3-1.0.0-5c74ba.tag.xz
Le mercredi 13 juin 2012 à 19:49 +0200, Pierre-Yves Chibon a écrit :
On Wed, 2012-06-13 at 11:45 -0600, Pete Zaitcev wrote:
Suppose I cut a package last year:
swift3-1.0.0-878c23.tag.xz
Then I build an RPM:
openstack-swift-plugin-swift3-1.0.0-878c23-1.fc17.noarch.rpm
Today I run
On Wed, 2012-06-13 at 11:45 -0600, Pete Zaitcev wrote:
On Mon, 23 Apr 2012 14:08:05 -0600
Orion Poplawski or...@cora.nwra.com wrote:
%global commit bd245c9
Source0:
https://github.com/jukka/pcfi/tarball/%{commit}/jukka-pcfi-%{commit}.tar.gz
%setup -q -n jukka-pcfi-%{commit}
On Wed, Jun 13, 2012 at 08:10:14PM +0200, Pierre-Yves Chibon wrote:
On Wed, 2012-06-13 at 11:45 -0600, Pete Zaitcev wrote:
On Mon, 23 Apr 2012 14:08:05 -0600
Orion Poplawski or...@cora.nwra.com wrote:
%global commit bd245c9
Source0:
On Wed, 2012-06-13 at 20:10 +0200, Pierre-Yves Chibon wrote:
On Wed, 2012-06-13 at 11:45 -0600, Pete Zaitcev wrote:
On Mon, 23 Apr 2012 14:08:05 -0600
Orion Poplawski or...@cora.nwra.com wrote:
%global commit bd245c9
Source0:
On Wed, 2012-06-13 at 13:22 -0700, Adam Williamson wrote:
On Wed, 2012-06-13 at 20:10 +0200, Pierre-Yves Chibon wrote:
On Wed, 2012-06-13 at 11:45 -0600, Pete Zaitcev wrote:
On Mon, 23 Apr 2012 14:08:05 -0600
Orion Poplawski or...@cora.nwra.com wrote:
%global commit bd245c9
On 04/23/2012 11:21 AM, Patrick Monnerat wrote:
On Mon, 2012-04-23 at 14:27 +0100, Adam Williamson wrote:
On Fri, 2012-04-20 at 20:51 -0700, Eric Smith wrote:
Corey Richardson wrote:
Getting source tarballs from github is a nightmare. See
So I watch the jabberd2 ml. They just released 2.2.15. Someone asked for
them to provide a tarball in the downloads section [1]. So the upstream
has uploaded one there. Originally the upstream asked what purpose
uploading a tarball would provide, the main reason they gave was the
inclusion of
On Fri, Apr 20, 2012 at 08:51:29PM -0700, Eric Smith wrote:
Corey Richardson wrote:
Getting source tarballs from github is a nightmare. See
http://lists.fedoraproject.org/pipermail/devel/2011-February/148676.html
The debian tool doesn't help very much because one still needs revision
On Fri, 2012-04-20 at 20:51 -0700, Eric Smith wrote:
Corey Richardson wrote:
Getting source tarballs from github is a nightmare. See
http://lists.fedoraproject.org/pipermail/devel/2011-February/148676.html
The debian tool doesn't help very much because one still needs revision
garbage
On Mon, 2012-04-23 at 14:27 +0100, Adam Williamson wrote:
On Fri, 2012-04-20 at 20:51 -0700, Eric Smith wrote:
Corey Richardson wrote:
Getting source tarballs from github is a nightmare. See
http://lists.fedoraproject.org/pipermail/devel/2011-February/148676.html
I noticed putting what
On 04/23/2012 06:27 AM, Adam Williamson wrote:
On Fri, 2012-04-20 at 20:51 -0700, Eric Smith wrote:
#!/bin/sh
# usage: tcplay-get-snapshot.sh hash
git clone git://github.com/bwalex/tc-play
( cd tc-play \
git archive --format=tar --prefix=tcplay-$1/ $1 \
) | xz - tcplay-$1.tar.xz
We
On Mon, 2012-04-23 at 10:37 -0700, Andy Grover wrote:
wget --content-disposition https://github.com/$user/$project/tarball/$tag;
lets you download a tarball named $user-$project-$tag-0-$gitsha1.tar.gz.
That saves the maintainer from having to document how to generate the
tarball, in
On 04/23/2012 11:37 AM, Andy Grover wrote:
wget --content-disposition https://github.com/$user/$project/tarball/$tag;
lets you download a tarball named $user-$project-$tag-0-$gitsha1.tar.gz.
That saves the maintainer from having to document how to generate the
tarball, in exchange for dealing
On 04/23/2012 10:48 AM, Adam Williamson wrote:
On Mon, 2012-04-23 at 10:37 -0700, Andy Grover wrote:
wget --content-disposition https://github.com/$user/$project/tarball/$tag;
lets you download a tarball named $user-$project-$tag-0-$gitsha1.tar.gz.
That saves the maintainer from having to
On 2012-04-23 20:56, Orion Poplawski wrote:
My problem is I'm wedded to spectool -g and it doesn't use
--content-disposition. Would it be safe to have spectool always use
that option?
No, because the Content-Disposition header from the server may result in
changing the downloaded file's name
On 04/23/2012 11:21 AM, Patrick Monnerat wrote:
On Mon, 2012-04-23 at 14:27 +0100, Adam Williamson wrote:
On Fri, 2012-04-20 at 20:51 -0700, Eric Smith wrote:
Corey Richardson wrote:
Getting source tarballs from github is a nightmare. See
On 04/23/2012 01:08 PM, Orion Poplawski wrote:
Nice! I'll note explicitly that this also works with short git tags, so:
%global commit bd245c9
Source0:
https://github.com/jukka/pcfi/tarball/%{commit}/jukka-pcfi-%{commit}.tar.gz
%setup -q -n jukka-pcfi-%{commit}
works.
Even if
Getting source tarballs from github is a nightmare. See
http://lists.fedoraproject.org/pipermail/devel/2011-February/148676.html
The debian tool doesn't help very much because one still needs revision
--
devel mailing list
devel@lists.fedoraproject.org
(Let's try this again, but with less fail!)
Getting source tarballs from github is a nightmare. See
http://lists.fedoraproject.org/pipermail/devel/2011-February/148676.html
The debian tool doesn't help very much because one still needs revision
garbage in the specfile. Is there any more recent
On 04/20/2012 08:24 PM, Corey Richardson wrote:
(Let's try this again, but with less fail!)
Getting source tarballs from github is a nightmare. See
http://lists.fedoraproject.org/pipermail/devel/2011-February/148676.html
The debian tool doesn't help very much because one still needs revision
Corey Richardson wrote:
Getting source tarballs from github is a nightmare. See
http://lists.fedoraproject.org/pipermail/devel/2011-February/148676.html
The debian tool doesn't help very much because one still needs revision
garbage in the specfile. Is there any more recent ways to mitigate
24 matches
Mail list logo
