lp:~juliank/launchpad

Get this repository:
git clone https://git.qastaging.paddev.net/~juliank/launchpad
Only Julian Andres Klode can upload to this repository. If you are Julian Andres Klode please log in for upload directions.

Branches

Name Last Modified Last Commit
wip-ppa-architectures 2025-10-17 20:36:53 UTC
WIP: archivepublisher: Do not publish disabled architectures for PPAs

Author: Julian Andres Klode
Author Date: 2025-10-17 20:36:53 UTC

WIP: archivepublisher: Do not publish disabled architectures for PPAs

PPA publishing only checked whether the DAS was enabled, but not
whether the processor for it was enabled in the PPA; causing PPAs
to end up with two issues:

A. Architecture: all packages appear for disabled architectures.
B. The disabled architectures appear enabled

This change compromises three parts:

1. Not writing indices for disabled architectures
2. Updating the list of indices to exclude disabled architectures

These address the actual publishing, hence point A.

3. Updating the Release file generator to only put the enabled
   architectures in the Architectures field.

This causes APT, for empty or missing Packages files not to warn
about the PPA not supporting that architecture.

YMMV here, in particular, it's likely wrong for i386: We don't want
PPAs to warn when added to multi-arch amd64+i386 system; so we should
likely special case this there.

On the flip side, we may not want to advertise "primary" architectures
as supported that aren't.

apt-ftparchive-per-distro-cache-cache 2025-02-17 14:00:18 UTC
Use per-distro-pocket apt-ftparchive caches

Author: Julian Andres Klode
Author Date: 2025-02-17 13:57:30 UTC

Use per-distro-pocket apt-ftparchive caches

The cache databases get corrupted quite regularly, and
this means we need to rescan the debs for all series
in the archive, which is a lot of work.

So switch to per-distro caches instead, actually including
the full pocket. The huge advantage is we never need to
rescan stable release pockets anymore - once scanned we
don't modify their databases anymore as there's nothing
to write.

valid-until 2024-08-20 17:32:31 UTC
Implement Valid-Until for security pocket

Author: Julian Andres Klode
Author Date: 2024-08-20 17:10:47 UTC

Implement Valid-Until for security pocket

Implement the Valid-Until field for all security pockets;
including existing ones.

Set the Valid-Until field two weeks after the publication
Date field, and republish the Release file if it will expire
in less than a week.

A similar change probably needs to be made for ESM publishing,
I haven't checked that. This works for the main archive at the
very least.

LP: #716535

13 of 3 results
This repository contains Public information 
Everyone can see this information.