Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove and ignore previously packaged versions of qips-wfmgr that make the gem 130MB #1

Merged
merged 1 commit into from Jan 19, 2012

Conversation

drbrain
Copy link
Contributor

@drbrain drbrain commented Jan 17, 2012

qips-wfmgr releases use over 2GB of space on rubygems.org with 14 releases of 140MB each: https://gist.github.com/1629309

This pull request removes the gems from the pkg/ directory which contain multiple copies of the gem, each containing multiple copies of previous versions of the gem in their respective pkg/ directories.

Additionally I have filed technicalpickles/jeweler#216 to help with this problem as the source of the problem is in your packaging tool. In my brief look through the jeweler codebase it appears that removing and ignoring these files will solve the problem, reducing the size of qips-wfmgr below 1MB.

PS: We may ask you to re-release prior versions of qips-wfmgr without the multiple extra gems to save money for rubygems.org.

@delagoya
Copy link
Contributor

Wow, I did not realize the gem was packing these in. The project was bus factor 1 of someone that left the organization a while ago. Will make the updates and push a new gem. Thanks!
-angel

On Tuesday, January 17, 2012 at 6:19 PM, Eric Hodel wrote:

qips-wfmgr releases use over 2GB of space on rubygems.org with 14 releases of 140MB each: https://gist.github.com/1629309

This pull request removes the gems from the pkg/ directory which contain multiple copies of the gem, each containing multiple copies of previous versions of the gem in their respective pkg/ directories.

Additionally I have filed technicalpickles/jeweler#216 to help with this problem as the source of the problem is in your packaging tool. In my brief look through the jeweler codebase it appears that removing and ignoring these files will solve the problem, reducing the size of qips-wfmgr below 1MB.

PS: We may ask you to re-release prior versions of qips-wfmgr without the multiple extra gems to save money for rubygems.org (http://rubygems.org).

You can merge this Pull Request by running:

git pull https://github.com/drbrain/qips-wfmgr master

Or you can view, comment on it, or merge it online at:

#1

-- Commit Summary --

  • Remove previously packaged versions and ignore the pkg directory

-- File Changes --

M .gitignore (1)
D pkg/qips-wfmgr-0.1.0.gem (0)
D pkg/qips-wfmgr-0.1.1.gem (0)
D pkg/qips-wfmgr-0.1.2.gem (0)
D pkg/qips-wfmgr-0.1.3.gem (0)
D pkg/qips-wfmgr-0.2.0.gem (0)
D pkg/qips-wfmgr-0.2.1.gem (0)
D pkg/qips-wfmgr-0.2.2.gem (0)
D pkg/qips-wfmgr-0.2.3.gem (0)
D pkg/qips-wfmgr-0.3.0.gem (0)
D pkg/qips-wfmgr-0.3.1.gem (0)
D pkg/qips-wfmgr-0.4.0.gem (0)
D pkg/qips-wfmgr-0.4.1.gem (0)
D pkg/qips-wfmgr-0.4.2.gem (0)
D pkg/qips-wfmgr-0.4.3.gem (0)
D pkg/qips-wfmgr-0.4.4.gem (0)

-- Patch Links --

https://github.com/daustin/qips-wfmgr/pull/1.patch
https://github.com/daustin/qips-wfmgr/pull/1.diff


Reply to this email directly or view it on GitHub:
#1

delagoya pushed a commit that referenced this pull request Jan 19, 2012
Remove and ignore previously packaged versions of qips-wfmgr that make the gem 130MB
@delagoya delagoya merged commit 8cb34c9 into daustin:master Jan 19, 2012
@zenspider
Copy link

The latest gem is still huge... fyi...

@delagoya
Copy link
Contributor

Yeah, I have been trying to contact the gem owner that left our group to no
avail. Anyway to pull the whole gem from ruby gems ?

Sent from my iPad

On Aug 28, 2012, at 10:32 PM, Ryan Davis notifications@github.com wrote:

The latest gem is still huge... fyi...


Reply to this email directly or view it on
GitHubhttps://github.com//pull/1#issuecomment-8113688.

@zenspider
Copy link

You can file a support ticket on rubygems.org to fix ownership

On Aug 29, 2012, at 5:19, Angel Pizarro notifications@github.com wrote:

Yeah, I have been trying to contact the gem owner that left our group to no
avail. Anyway to pull the whole gem from ruby gems ?

Sent from my iPad

On Aug 28, 2012, at 10:32 PM, Ryan Davis notifications@github.com wrote:

The latest gem is still huge... fyi...


Reply to this email directly or view it on
GitHubhttps://github.com//pull/1#issuecomment-8113688.

Reply to this email directly or view it on GitHub.

@delagoya
Copy link
Contributor

I submitted a support request. -angel

On Friday, August 31, 2012 at 2:26 PM, Ryan Davis wrote:

You can file a support ticket on rubygems.org (http://rubygems.org) to fix ownership

On Aug 29, 2012, at 5:19, Angel Pizarro <notifications@github.com (mailto:notifications@github.com)> wrote:

Yeah, I have been trying to contact the gem owner that left our group to no
avail. Anyway to pull the whole gem from ruby gems ?

Sent from my iPad

On Aug 28, 2012, at 10:32 PM, Ryan Davis <notifications@github.com (mailto:notifications@github.com)> wrote:

The latest gem is still huge... fyi...


Reply to this email directly or view it on
GitHubhttps://github.com//pull/1#issuecomment-8113688.

Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub (#1 (comment)).

@zenspider
Copy link

I see that ownership was transferred. Please re-release this gem w/ the proper contents and then file a support ticket to get all of the previous versions yanked and purged. Lemme know if you need any help with packaging and releasing.

@delagoya
Copy link
Contributor

All versions of the gem removed. Apologies for the extreme delays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants