uploaded file does not start to build

Which package did you upload, and to where? You don't have a PPA, and you're not in any teams, so you can't successfully upload anything to Launchpad.

See https://help.launchpad.net/Packaging/PPA for help on using PPAs.

Well, I seem to be able to :-).
$ dput ppa:libreplan/ppa ../libreplan_1.4.1-8.vivid_source.changes
Package has already been uploaded to ppa on ppa.launchpad.net
Nothing more to do for ../libreplan_1.4.1-8.vivid_source.changes

https://launchpad.net/~libreplan/+archive/ubuntu/ppa/+builds?build_state=all&build_text=&batch=75

I am the projectleader of the LibrePlan project. Just don't know how to add that project to my account, but that is currently not my main concern.

Ah, so it's rather that one of your bot accounts is uploading it. It was rather difficult to debug without having any idea which user, PPA or package you were talking about.

That bot's email account was sent two rejection emails. The error is this:

   PPA exceeded its size limit (6232.00 of 6144.00 MiB).

Deleting the obsolete lucid, quantal and saucy packages from the PPA and waiting a few hours should let you upload successfully.

Got it.

Last question:
How can I delete those packages? I read the help text but can't seem to find the delete page

Regards, Jeroen

https://launchpad.net/~libreplan/+archive/ubuntu/ppa, "View package details", "Delete packages".

got it. Thanks!

So. the files are removed, the disck space is freed and I have 3 G available. I have now waited 8 hours patiently for all this. Now how long will it take before the builds I submitted will start?

regards, Jeroen

No builds are currently pending (the "Needs building" state) in your PPA. From what you said earlier, you probably need to upload your source packages again; nothing's going to happen automatically until *you* do that.

The message remains: "Package has already been uploaded to ppa on ppa.launchpad.net
Nothing more to do for ../libreplan_1.4.1-8.vivid_source.changes"

So I just incremented the releasecounter and uploaded a new file.

That seems to solve my current build problem.

For future reference, you could also have used "dput -f" to override that; the record of whether it's been uploaded is entirely local to your system.