Launchpad itself

Disk space limit, build logs, and publishing

Asked by Simon Chopin

Hello,

TL;DR: Would it be possible to expand the disk quota on schopin/openssl3.0.0 a bit? (other questions are less urgent)

I've been working on rebuilding big swathes of the archive against OpenSSL3 to prepare for the upcoming transition. I did the first rebuild in the PPA schopin/openssl3, but as it was against a beta version and the final version has come out since then, I figured I'd reuse the PPA for a new build... To save disk space I had disabled publishing, and thought re-enabling it would not publish the pending binaries from the last rebuild, just the new ones (i.e. the new openssl version). It seems I was wrong, as the repo size ballooned over 300 GB overnight.

SInce the package deletion process isn't immediate, I figured I'd start fresh in a new PPA, creatively named schopin/openssl-3.0.0, but before I delete the previous one I'd like to know if its build logs will survive the deletion? If not, it'll have to wait until the new rebuild is over. In any case, can I get a disk space bump on the new PPA?

Last question: assuming I'd have to do a 3rd rebuild, can you confirm that the best course of action would have been to put the OpenSSL package in its own PPA, and do the rebuild in a separate one which declares a dependency on the first one?
 I figure it would prevent the whole publishing apocalypse...

Question information

Language:
English Edit question
Status:
Expired
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said : 		#1

Build logs won't survive deleting the entire PPA. What's the benefit of starting fresh here? Might we not as well just get it over with in the existing PPA at this point?

I've bumped quotas on both openssl3 and openssl-3.0.0, anyway.

Revision history for this message
Simon Chopin (schopin) said : 		#2

Hi Colin!

Quoting Colin Watson (2021-09-21 11:55:48)
> Colin Watson proposed the following answer:
> Build logs won't survive deleting the entire PPA. What's the benefit of
> starting fresh here? Might we not as well just get it over with in the
> existing PPA at this point?
 Well, the existing PPA was at 500% size capacity this morning, so I
figured starting fresh would be easier than trying to clean it up :/

> I've bumped quotas on both openssl3 and openssl-3.0.0, anyway.
Thanks!

Revision history for this message
Launchpad Janitor (janitor) said : 		#3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.