Hey folks,
Just looking at some of the Fedora package submissions, I'm seeing a fairly consistent problem.
Each time an individual aeolus project tags a release, we should be uploading the equivalent tarball (and/or gem) for that tag to a HTTP server somewhere.
I can find release artifacts for imagefactory and oz:
http://repos.fedorapeople.org/repos/aeolus/oz/0.5.0/tarball/oz-0.5.0.tar.gz http://repos.fedorapeople.org/repos/aeolus/image-factory/0.4.0/tarball/image...
But there's none for rubygem-imagefactory, rubygem-aeolus-image, aeolus-conductor or aeolus-configure.
I've taken the liberty of uploading them:
http://repos.fedorapeople.org/repos/aeolus/imagefactory-console/0.4.0/gem/im... http://repos.fedorapeople.org/repos/aeolus/aeolus-image/0.0.1/gem/aeolus-ima... http://repos.fedorapeople.org/repos/aeolus/conductor/0.3.0/tarball/aeolus-co... http://repos.fedorapeople.org/repos/aeolus/aeolus-configure/2.0.1/tarball/ae...
And, for reference, exactly what I did is logged below.
Cheers, Mark.
$> cd imagefactory-console $> git reset --hard v0.4.0 $> rake gem $> gpg --detach-sign --armor -o pkg/imagefactory-console-0.4.0.gem.sign pkg/imagefactory-console-0.4.0.gem $> ssh fedorapeople.org 'cd /srv/repos/aeolus && mkdir -p imagefactory-console/0.4.0/gem' $> scp pkg/imagefactory-console-0.4.0.gem* fedorapeople.org:/srv/repos/aeolus/imagefactory-console/0.4.0/ $> ssh fedorapeople.org 'cd /srv/repos/aeolus && chgrp -R gitaeolus imagefactory-console'
$> cd aeolus-image $> git reset --hard v0.0.1 $> rake gem $> gpg --detach-sign --armor -o pkg/aeolus-image-0.0.1.gem.sign pkg/aeolus-image-0.0.1.gem $> ssh fedorapeople.org 'cd /srv/repos/aeolus && mkdir -p aeolus-image/0.0.1/gem' $> scp pkg/aeolus-image-0.0.1.gem* fedorapeople.org:/srv/repos/aeolus/aeolus-image/0.0.1/gem $> ssh fedorapeople.org 'cd /srv/repos/aeolus && chgrp -R gitaeolus aeolus-image'
$> cd conductor $> git reset --hard v0.3.0_RC_1 $> git tag v0.3.0 $> git push origin tag v0.3.0 $> make dist $> gpg --detach-sign --armor -o aeolus-conductor-0.3.0.tar.gz.sign aeolus-conductor-0.3.0.tar.gz $> ssh fedorapeople.org 'cd /srv/repos/aeolus && mkdir -p conductor/0.3.0/tarball' $> scp aeolus-conductor-0.3.0.tar.gz* fedorapeople.org:/srv/repos/aeolus/conductor/0.3.0/tarball $> ssh fedorapeople.org 'cd /srv/repos/aeolus && chgrp -R gitaeolus conductor/0.3.0/tarball'
$> cd configure $> git reset --hard v2.0.1_RC_1 $> git tag v2.0.1 $> rake package $> gpg --detach-sign --armor -o pkg/aeolus-configure-2.0.1.tgz.sign pkg/aeolus-configure-2.0.1.tgz $> ssh fedorapeople.org 'cd /srv/repos/aeolus && mkdir -p aeolus-configure/2.0.1/tarball' $> scp pkg/aeolus-configure-2.0.1.tgz* fedorapeople.org:/srv/repos/aeolus/aeolus-configure/2.0.1/tarball $> ssh fedorapeople.org 'cd /srv/repos/aeolus && chgrp -R gitaeolus aeolus-configure'
On 07/22/11 - 12:04:42PM, Mark McLoughlin wrote:
Hey folks,
Just looking at some of the Fedora package submissions, I'm seeing a fairly consistent problem.
Each time an individual aeolus project tags a release, we should be uploading the equivalent tarball (and/or gem) for that tag to a HTTP server somewhere.
I can find release artifacts for imagefactory and oz:
http://repos.fedorapeople.org/repos/aeolus/oz/0.5.0/tarball/oz-0.5.0.tar.gz http://repos.fedorapeople.org/repos/aeolus/image-factory/0.4.0/tarball/image...
But there's none for rubygem-imagefactory, rubygem-aeolus-image, aeolus-conductor or aeolus-configure.
I've taken the liberty of uploading them:
Thanks for doing this Mark. It has indeed been overlooked up until this point, but we need to add this task to the list of release tasks.
On 07/22/2011 07:04 AM, Mark McLoughlin wrote:
Hey folks,
Just looking at some of the Fedora package submissions, I'm seeing a fairly consistent problem.
Each time an individual aeolus project tags a release, we should be uploading the equivalent tarball (and/or gem) for that tag to a HTTP server somewhere.
We should be pushing the gems to http://rubygems.org as well. We can pull the gems for the rpms directly from there.
-Mo
On Fri, 2011-07-22 at 08:35 -0400, Mo Morsi wrote:
On 07/22/2011 07:04 AM, Mark McLoughlin wrote:
Hey folks,
Just looking at some of the Fedora package submissions, I'm seeing a fairly consistent problem.
Each time an individual aeolus project tags a release, we should be uploading the equivalent tarball (and/or gem) for that tag to a HTTP server somewhere.
We should be pushing the gems to http://rubygems.org as well. We can pull the gems for the rpms directly from there.
Good point Mo, I've done that now - updated instructions below
https://rubygems.org/gems/aeolus-image https://rubygems.org/gems/imagefactory-console
Jay and Martyn - could you set up accounts there so I can add you as owners?
Cheers, Mark.
$> cd imagefactory-console $> git reset --hard v0.4.0 $> rake gem $> gem push pkg/imagefactory-console-0.4.0.gem $> gpg --detach-sign --armor -o pkg/imagefactory-console-0.4.0.gem.sign pkg/imagefactory-console-0.4.0.gem $> ssh fedorapeople.org 'cd /srv/repos/aeolus && mkdir -p imagefactory-console/0.4.0/gem' $> scp pkg/imagefactory-console-0.4.0.gem* fedorapeople.org:/srv/repos/aeolus/imagefactory-console/0.4.0/ $> ssh fedorapeople.org 'cd /srv/repos/aeolus && chgrp -R gitaeolus imagefactory-console'
$> cd aeolus-image $> git reset --hard v0.0.1 $> rake gem $> gem push pkg/aeolus-image-0.0.1.gem $> gpg --detach-sign --armor -o pkg/aeolus-image-0.0.1.gem.sign pkg/aeolus-image-0.0.1.gem $> ssh fedorapeople.org 'cd /srv/repos/aeolus && mkdir -p aeolus-image/0.0.1/gem' $> scp pkg/aeolus-image-0.0.1.gem* fedorapeople.org:/srv/repos/aeolus/aeolus-image/0.0.1/gem $> ssh fedorapeople.org 'cd /srv/repos/aeolus && chgrp -R gitaeolus aeolus-image'
aeolus-devel@lists.fedorahosted.org
-
Chris Lalancette -
Mark McLoughlin -
Mo Morsi