AppImageLauncher
AppImageLauncher copied to clipboard
TheAssassin
Add PPAs for 23.04
Pre-submit checks
- [X] I checked for similar issues beforehand, but could not find any. I could not add my proposal to any existing issue.
- [X] I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise.
Additional context
Err:11 https://ppa.launchpadcontent.net/appimagelauncher-team/stable/ubuntu lunar Release
404 Not Found
I'm in the process of fleshing out the toolchain on Launchpad to restore the PPAs to functionality. It's no small task given all the vendoring that goes on in the AppImage ecosystem, but time permitting I don't anticipate encountering anything that can't be overcome. If you look at the Daily PPA you can see that I've already got the Lunar and Mantic series enabled and the first vendored library (cpr) successfully building.
To that end, though, ideally I'd like to be placing these build dependencies in their own PPA to minimize the potential breakage that could occur for end users who could accidentally install them. If either @TheAssassin or @shoogle could grant me the privileges on the team to be able to create more PPAs, I'd be much obliged and feel at greater liberty to "move fast and break things" once I'd organized everything a bit more. It would also be delightful if @TheAssassin were able to create a new branch in this repo where all the submodules had been deinited, on account of Launchpad still not being fully compatible with Git submodules. I end up having to make repositories for each of the submodules and then nest them in the build directory via the recipe, and it's far less fraught to do so when I can target a branch that doesn't have them already checked out into those filepaths (provided it's kept reasonably in sync with master). I believe there's no longer a need to remove the .gitmodules file in such a branch, at least; it seems to be ignored so long as there aren't any checkouts.
That's all I've got for an update on this at the moment, I'm afraid. Thanks for everyone's patience. 🙇🏻♂️
Pinging @TheAssassin and @shoogle again as packaging work continues apace, but as seen above, I'm unable to continue without the ability to create other PPAs to house the dependent packages. As we're over the storage limit already at some point in the next few days new builds will start to fail over the inability to upload. The Launchpad team permissions are here, and it's a couple quick clicks to toggle my membership status (same username as here) to Administrator. Thanks again.
@RogueScholar, I think you have access now at:
- https://launchpad.net/~appimage-maintainers
- https://launchpad.net/~appimagelauncher-team
Is that what you need?
Had a look, too, should be good now. Thanks @shoogle. @RogueScholar let us know if this is sufficient.
Sorry guys, I don't see any change to my permissions on Launchpad still, and specifically the Create New PPA link is still absent. I've logged out and back in, cleared cache and cookies, all the usual procedures. When I look at the team membership I see my status listed as Approved and not Administrator, is that not what you see?
@RogueScholar I made you an admin on the AppImageLauncher team. I do not have sufficient access to the AppImage team, unfortunately.
Ping @shoogle.
For the record, I highly welcome your initiative to package this software, and I can relate to why you want to use a separate PPA. I ran into some issues lately with all the dependency packages and it took me half an hour to downgrade all the libraries again to unbreak my system.
Ping @shoogle.
Sorry guys, I must have missed this notification. I've made @TheAssassin and @RogueScholar admins at https://launchpad.net/~appimage-maintainers.
