rubyforge <-> gemcutter issues

[ara.t.howard]

this is an issue gem publishers need to be aware off:

http://help.rubygems.org/discussions/problems/318-original-sync-to-rubyforge-never-worked-what-now

until it's fixed it's possible that your releases are not making it to
other people's machines during 'gem install'

fyi.

 

[botp]

=A0http://help.rubygems.org/discussions/problems/318-original-sync-to-rub=

yforge-never-worked-what-now

but rubyforge also reflects older version....

$ gem env | egrep sources
- :update_sources =3D> true
- :sources =3D> ["http://gems.rubyforge.org/"]

$ gem list --remote | egrep "^options "
options (2.1.1)

 

[Luis Lavena]

this is an issue gem publishers need to be aware off:

 http://help.rubygems.org/discussions/problems/318-original-sync-to-ru....

until it's fixed it's possible that your releases are not making it to
other people's machines during 'gem install'

fyi.

I never expected gems published on gemcutter (now rubygems.org) been
reflected at RubyForge automatically. Also, after the migration, never
expected gems (beyond .zip and tar packages) published at RubyForge be
feed into gemcutter.

The overhead of keep those things under sync is huge.

I disconnected gem publishing to RubyForge and now gems are pushed to
gemcutter only while .zip and tar to RubyForge for OS packagers.

That is what I understood and assumed.

FYI.

 

[ara.t.howard]

I disconnected gem publishing to RubyForge and now gems are pushed to

gemcutter only while .zip and tar to RubyForge for OS packagers.

That is what I understood and assumed.

agreed - but i cannot push to any of the gems i used to own, otherwise
that would be an option. i honestly don't completely understand the
whole set of problems, but i think they fall into 4 categories

1) ownership after transfer
2) syncing rubyforge -> gemcutter
3) gems never synced
4) lack of a simple README re: how it supposed to work.

cheers.
-a

 

[Luis Lavena]

agreed - but i cannot push to any of the gems i used to own, otherwise
that would be an option.  i honestly don't completely understand the
whole set of problems, but i think they fall into 4 categories

1) ownership after transfer

This could be related to the email/account records at RubyForge versus
the ones at rubygems.org. I had problems with this too and requested
the merge of these two accounts (both using the same email address) to
solve it.

2) syncing rubyforge -> gemcutter

Perhaps a failure on #1 could have rendered your old gems never to
appear in rubygems.org

3) gems never synced

4) lack of a simple README re: how it supposed to work.

Indeed.

Seems to me that the most grief about changes in the Ruby community
are associated with the lack of visibility and communication of those
changes.

I share my thoughts on that before gemcutter/rubygems conversion and
how things supposed to work afterwards.

 

[Ryan Davis]

this is an issue gem publishers need to be aware off:
=20
= http://help.rubygems.org/discussions/problems/318-original-sync-to-rubyfor=
ge-never-worked-what-now
=20
until it's fixed it's possible that your releases are not making it to
other people's machines during 'gem install'

=46rom the ticket:

for example, i own the options gem. it's been updated on rubyforge =

(via api) several times. over here we see (grep page for options) =
options 2.2.0 has been released:

=20
http://rubyforge.org/frs/?group_id=3D1024&amp;release_id=3D43932
=20
yet a search on gemcutter results in:
=20
http://rubygems.org/search?utf8=3D✓&amp;query=3Doptions
=20
in my case gemcutter has effectively stolen about 100 of my gems - the =

system owns them and i cannot release fixes.

Wasn't this latter issue addressable via `gem owner`?

owner Manage gem owners on RubyGems.org.

I seem to recall having to fire off a whole mess of those after the =
transition and haven't had many of the issues you're having. Tho I did =
adapt hoe to publish to gemcutter as well as to rubyforge, so I'm prolly =
masking it somewhat.=

 

[Quintus]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 10.09.2010 21:37, schrieb ara.t.howard:

agreed - but i cannot push to any of the gems i used to own, otherwise
that would be an option. i honestly don't completely understand the
whole set of problems, but i think they fall into 4 categories

1) ownership after transfer
2) syncing rubyforge -> gemcutter
3) gems never synced
4) lack of a simple README re: how it supposed to work.

cheers.
-a

You say you can't publish newer version of gems you own? That's really
interesting, since when rubygems.org just had started out (with the name
"gemcutter"), I had the same problem. On rubyforge.org I owned the au3
and xdo gems, but as I tried to push a new version, I was told I did not
have the rights to do so. Since Nick Quaranto stated on gemcutter.org
that one should email him if issues with gems arise, I did likewise and
within two days I was able to publish gems again.
I'n not sure if that's related to your special issue, I just wanted to
throw my own experience in, in case it helps you.

Vale,
Marvin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyKlOcACgkQDYShvwAbcNlbKwCdGBWvcfk1bPmxFDplX8oy+84P
TysAoIDi3dzS9XHRYpaAGkgSDjtEog3J
=EmkX
-----END PGP SIGNATURE-----