PPA storage limit increase request

Asked by kisak

Good day,

A couple years ago, I created a general purpose Mesa / LLVM PPA at https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa with the intention of providing the latest point release of mesa and llvm for Ubuntu 18.04 LTS and newer. At the time, I needed the storage limit to be bumped larger than 2GB, which was requested at https://answers.launchpad.net/launchpad/+question/686000. Thanks for letting me use Launchpad to make a current mesa point release available to any interested Ubuntu users.

After a while of routine updates, it became clear that a secondary, more stable option was also needed if there was unexpected complications and I created https://launchpad.net/~kisak/+archive/ubuntu/turtle as an alternative to cover that situation.

With the preparation to update kisak-mesa fresh to mesa 21.3.0, I'm in the process of updating kisak-mesa stable (the turtle link above) to mesa 21.2.5 and llvm 13. Unfortunately, with the six llvm 12 builds (i386 and amd64 variants for 3 distro releases), and the eight llvm 13 builds, it looks like I'm going to temporarily exceed the 2GB limit on that PPA unless I break it by purging llvm 12 before mesa is rebuilt against llvm 13.

Unlike kisak-mesa fresh, debug symbols will not be enabled on kisak-mesa stable at any point in the future, so only a small storage limit bump would be needed to ease this update cycle. Please let me know if this is a reasonable request.

~non-sequitur secondary request~

I had a single user request over the couple years of maintaining the kisak-mesa PPA to also expand arch coverage to include ARM systems, but this is blocked by a lack of suitable hardware to locally test, troubleshoot, and resolve any issues that might come up. This made me reluctant to dive head first into ARM builds. That said, since I'm already asking about storage limits, would there be interest in trying to make builds for that available anyway, if I added a PPA description note that there is no local testing outside of X86 systems, would there be interest in making that happen?

Adding armhf and arm64 builds would at least need the 8GB limit doubled to 16GB on kisak-mesa fresh, or more if there's interest in also covering the less commonly used architectures. The kisak-mesa stable PPA would need substantially less space with the lack of debug symbols.

From the launchpad hosting side, is it worth the disk space to experiment with expanding arch coverage? If it is, which arches should I look at including?

Thank you for considering this request,
kisak

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
William Grant
Solved:
Last query:
Last reply:

This question was originally filed as bug #1951320.

Revision history for this message
kisak (kisak) said :
#1

Good day,

A couple years ago, I created a general purpose Mesa / LLVM PPA at https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa with the intention of providing the latest point release of mesa and llvm for Ubuntu 18.04 LTS and newer. At the time, I needed the storage limit to be bumped larger than 2GB, which was requested at https://answers.launchpad.net/launchpad/+question/686000. Thanks for letting me use Launchpad to make a current mesa point release available to any interested Ubuntu users.

After a while of routine updates, it became clear that a secondary, more stable option was also needed if there was unexpected complications and I created https://launchpad.net/~kisak/+archive/ubuntu/turtle as an alternative to cover that situation.

With the preparation to update kisak-mesa fresh to mesa 21.3.0, I'm in the process of updating kisak-mesa stable (the turtle link above) to mesa 21.2.5 and llvm 13. Unfortunately, with the six llvm 12 builds (i386 and amd64 variants for 3 distro releases), and the eight llvm 13 builds, it looks like I'm going to temporarily exceed the 2GB limit on that PPA unless I break it by purging llvm 12 before mesa is rebuilt against llvm 13.

Unlike kisak-mesa fresh, debug symbols will not be enabled on kisak-mesa stable at any point in the future, so only a small storage limit bump would be needed to ease this update cycle. Please let me know if this is a reasonable request.

~non-sequitur secondary request~

I had a single user request over the couple years of maintaining the kisak-mesa PPA to also expand arch coverage to include ARM systems, but this is blocked by a lack of suitable hardware to locally test, troubleshoot, and resolve any issues that might come up. This made me reluctant to dive head first into ARM builds. That said, since I'm already asking about storage limits, would there be interest in trying to make builds for that available anyway, with a PPA description note that there is no local testing outside of X86 systems? Adding armhf and arm64 builds would at least need the 8GB limit doubled to 16GB on kisak-mesa fresh, or more if there's interest in also covering the less commonly used architectures.

From the launchpad hosting side, is it worth the disk space to experiment with expanding arch coverage? If it is, which arches should I look at including?

Thank you for considering this request,
kisak

Revision history for this message
Best William Grant (wgrant) said :
#2

I've increased the limits on both PPAs to 16GiB.

For desktop use I think amd64, armhf and amd64 are the most reasonable targets at the moment; ppc64el and s390x are pretty much pure server platforms, and riscv64 isn't ready for general availability yet.

Revision history for this message
kisak (kisak) said :
#3

Thanks William Grant, that solved my question.