Increase PPA limit (for schools-wikipedia)

Asked by Pascal de Bruijn on 2009-12-13


I have locally (on my home system) packaged Schools Wikipedia. Schools Wikipedia is a subselection of all Wikipedia Articles, based on the UK National Curriculum, which has been audited by SOS Childrens Villages volunteers. So it's supposed to be child safe, and any big mistakes have been checked/removed.

The problem is, that the sources all together are 3GB, and the resulting package is also 3GB (it's architecture independent), so if I were to submit this package, I would need an extra 6GB of PPA space.

Thanks for your consideration,

Pascal de Bruijn

Question information

Tom Haddon (mthaddon) said : #2

I've set the limit for to 6GB. Let us know if that wasn't the PPA you had in mind, as I wasn't entirely clear on that from your request.

Thanks, Tom

Pascal de Bruijn (pmjdebruijn) said : #3

Sorry, yes that is the right PPA.

However, I asked for an increase of 6 GB, since the new packages will take 6GB of space, I still need an additional 1GB for all my other packages...

So I need 7GB to make this work.

Pascal de Bruijn (pmjdebruijn) said : #4

Since these aren't hard limits I tried to upload my package sources... But my 'schools-wikipedia' package still hasn't turned up on my PPA...

Maybe another unforeseen limit has been reached?

Pascal de Bruijn

Pascal de Bruijn (pmjdebruijn) said : #5

I still require some assistance...

Steve McInerney (spm) said : #6

Sorry 'bout that delay there - you managed to hit the w/e :-/
I've increased your limit to 8Gb - see how that goes? 7 sounded like it may be tight.

- Steve

Pascal de Bruijn (pmjdebruijn) said : #7

Is there a way to trace what went wrong with my initial upload?

I uploaded it to ppa:pmjdebruijn on 2009-12-19 17:20 (+0100):

Successfully uploaded schools-wikipedia_0.0.20081023-0pmjdebruijn1~karmic.dsc to for ppa.
Successfully uploaded schools-wikipedia_0.0.20081023.orig.tar.gz to for ppa.
Successfully uploaded schools-wikipedia_0.0.20081023-0pmjdebruijn1~karmic.diff.gz to for ppa.
Successfully uploaded schools-wikipedia_0.0.20081023-0pmjdebruijn1~karmic_source.changes to for ppa.

I never got an accepted _or_ rejected email.

I'm asking this because, re-uploading 3 GB is not trivial at 128KB/sec.


This happens when you sign your package with a key unknown to Launchpad, or you forgot to sign it at all. In the former case, this is because it prevents Launchpad being a spam vector. In the latter, it's because it doesn't know who to email.

In both cases, the upload is simply discarded.

Make sure that you are:

 * signing your package
 * the signature is associated with your Launchpad account

Julian Edwards suggests this article as an answer to your question:
FAQ #227: “Why has the package I dput-ed into my team's PPA not shown up yet?”.

This is not my issue...

$ gpg --verify schools-wikipedia_0.0.20081023-0pmjdebruijn1~karmic_source.changes
gpg: Signature made Sat 19 Dec 2009 04:46:45 PM CET using DSA key ID 601A0BFA
gpg: Good signature from "Pascal de Bruijn <email address hidden>"
gpg: aka "Pascal Maria Johannes de Bruijn <email address hidden>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: E82F 7CC0 A9DB 0A43 185D 0832 3328 B36B 601A 0BFA

I've signed a new package (shared-color-targets) just like this and gpg --verify on that package gives exactly the same message. However the new package did get accepted and built.

So I'm reasonably sure the key isn't the problem here.

Ok, I am looking into it, will get back to you.

Thank you for your time.

I probably have access to a highspeed uplink again on Thursday or next Monday. So if I still have to re-upload I can do it then, but I'd like to resolve any other issues before then.

Hi Pascal, I've just been through the logs of the upload processor, and it shows that an error occurred while processing your upload (detailed log here

Following through on that error, it comes down to the fact that

(1) Launchpad using an integer field to store the size of the file, which I would have thought would limit the possible size to 4294967296 bytes, but given the error, I'm guessing it's always stored as a signed integer, so the limit is 2147483648 bytes, and

(2) Launchpad is not checking the upper-bound of the file size before trying to create the record in the database - hence you not receiving a nice upload failure message.

So unfortunately this makes it impossible to upload such a file at the moment.

I'll turn this into a bug report so that (2) can be address appropriately.

Can you help with this problem?

Provide an answer of your own, or ask Pascal de Bruijn for more information if necessary.

To post a message you must log in.