Portability in dpkg is very important, to be able to support downstreams and people who use it on other systems, or even package it in other (non-GNU/Linux) distributions. But currently porting to many of those is done purely through documentation, so catching build or run-time issues is clearly a reactive process, although it would be nice to switch to a more proactive model.

So it would be very much appreciated if either interested parties could provide access to such systems, or setup some kind of continuous integration system from git. Barring anything else, sending build and test suite success or failure reports from time to time would be also appreciated.

Please get in contact with the mailing list if you can offer resources (or privately to GuillemJover if you'd rather remain anonymous).

The following systems are of particular interest:

System

Supported

Access

CI

Remote Sponsor

build

tests

local VM

remote

GNU/Linux

(./)

(./)

(./)

(./)

https://salsa.debian.org/dpkg-team/dpkg/-/pipelines

Debian project

GNU/Hurd

(./)

(./)

(./)

(./)

Debian project

musl/Linux

(./)

(./)

(./)

(./)

GCC Compile Farm

FreeBSD

(./) 13.x

(./)

(./)

(./)

https://github.com/guillemj/dpkg/actions/workflows/freebsd.yml

GCC Compile Farm

NetBSD

(./) 9.x

(./)

(./)

(./)

https://github.com/guillemj/dpkg/actions/workflows/netbsd.yml

GCC Compile Farm

OpenBSD

(./) 7.x

(./)

(./)

(./)

https://github.com/guillemj/dpkg/actions/workflows/openbsd.yml

GCC Compile Farm

OmniOS (illumos)

(./)

(./)

(./)

<!>

https://github.com/guillemj/dpkg/actions/workflows/omnios.yml

DilOS (illumos)

(./)

/!\ 1

<!>

(./)

Igor Kozhukhov (on behalf of the DilOS project)

macOS

(./) 12.x

(./) 2

<!>

(./)

https://github.com/guillemj/dpkg/actions/workflows/macos.yml

GCC Compile Farm

Solaris

(./) 11.4 3

(./)

<!>

(./)

GCC Compile Farm; (no need for access via OpenCSW as cfarm uses that already)

AIX

(./) 7.2, 7.3

(./)

<!>

(./)

GCC Compile Farm

HP-UX

?

?

<!>

<!>

Redox

?

?

(./)

<!>

Haiku

{X} 4

{X}

(./)

<!>

Minix

{X} 5

{X}

(./)

<!>

Supported means that at least that OS release is known to build from git HEAD, previous versions might build too.

  1. userland is too old (1)

  2. needs Mach-O executable support (2)

  3. Solaris 11.3 and earlier have a too old userland (3)

  4. BeFS does not support hardlinks (4)

  5. Minix upstream is not active (5)