https://github.com/mietzen/template-debian-pkg-repo
Template for a Debian Package Repository hosted on GH-Pages
https://github.com/mietzen/template-debian-pkg-repo
debian dev pkg-repo template
Last synced: 10 months ago
JSON representation
Template for a Debian Package Repository hosted on GH-Pages
- Host: GitHub
- URL: https://github.com/mietzen/template-debian-pkg-repo
- Owner: mietzen
- License: mit
- Created: 2025-08-04T08:23:16.000Z (11 months ago)
- Default Branch: main
- Last Pushed: 2025-08-06T05:18:54.000Z (11 months ago)
- Last Synced: 2025-09-06T05:58:18.807Z (10 months ago)
- Topics: debian, dev, pkg-repo, template
- Homepage:
- Size: 29.3 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: ReadMe.md
- License: LICENSE
Awesome Lists containing this project
README
# Debian Repository on GitHub Pages
This template repository automatically creates and maintains a Debian package repository hosted on GitHub Pages by pulling `.deb` packages from GitHub releases.
## Setup
### Configure Packages
Edit `packages.yml` to list the GitHub repositories you want to include:
```yaml
packages:
example-package-1:
url: https://github.com/user/repo1
version: "1.2.3"
# Optional regex to select which .deb assets to include from the release
asset_regex: '.*amd64.*'
example-package-2:
url: https://github.com/user/repo2
version: "2.0.1"
asset_regex: '.*all.*'
```
#### asset_regex usage
- asset_regex is an optional regular expression used to filter release assets by filename before downloading. Only files ending with .deb are ever considered. If asset_regex is omitted, all .deb assets from the release are eligible.
- Invalid regular expressions are safely ignored and treated as if no filter was provided.
- Examples:
- Match architecture-specific packages:
- '.*amd64.*' selects .deb assets that contain amd64 in their filename.
- Match no-arch packages:
- '.*all.*' selects Architecture: all packages that are commonly built once for all architectures.
- Match multiple patterns:
- '.*(amd64|arm64).*' selects both amd64 and arm64 assets from the same release.
- Capture groups are allowed but unused; matching is boolean only.
Note: Filtering by asset_regex affects which assets are downloaded, but the actual Architecture used in repository metadata is always derived from the package’s control file inside the .deb.
### Enable GitHub Pages
1. Go to your repository settings
2. Navigate to "Pages" in the sidebar
3. Select "GitHub Actions" as the source
4. The workflows will automatically deploy your repository
## How architectures are determined (dynamic discovery)
Architectures are discovered dynamically based on the Packages files that are generated:
- The build step downloads selected .deb assets and reads their control metadata.
- Packages are grouped by their control Architecture field:
- If Architecture is all, entries are added to a dedicated all bucket.
- Otherwise, entries are associated with their specific architecture (e.g., amd64, arm64, i386, etc.).
- Packages files are generated per-architecture and for all. Each per-arch Packages file includes the union of:
- All packages whose Architecture equals that arch
- All packages whose Architecture is all
- The Release file Architectures field is derived at deploy time by scanning which binary- directories exist under dists/stable/main.
Result:
- If only Architecture: all packages exist, the repository will publish binary-all and the Release file will list Architectures: all.
- If you also include, for example, amd64 packages, both binary-all and binary-amd64 are present and Release will list Architectures: all amd64.
## Special handling: Architecture: all
- A single canonical Packages file for all is generated at dists/stable/main/binary-all/Packages.
- Each per-architecture Packages file additionally includes the all entries. This ensures clients on any specific architecture can install no-arch packages without mixing components.
Practical implications:
- You can publish only no-arch packages and still have a valid repository (Architectures: all).
- Mixing all with arch-specific packages is supported; clients will see all packages regardless of the chosen architecture.
## Usage
### Adding your Repository to your System
```bash
echo "deb [trusted=yes] https://.github.io// stable main" | sudo tee /etc/apt/sources.list.d/my-deb-pkgs.list
sudo apt-get update
```
### Adding New Packages
1. Add the package to `packages.yml`:
```yaml
packages:
new-package:
url: https://github.com/owner/new-package-repo
version: "1.0.0"
# Optional: filter assets by filename to specific architectures
asset_regex: '.*(amd64|arm64|all).*'
```
2. The update workflow will automatically detect new releases daily, or you can trigger it manually:
- Go to Actions → Update Package List → Run workflow
## License
This repository structure and scripts are provided under MIT License. Individual packages retain their original licenses.