Arvados

Other distros (debian12, ubuntu2004, ubuntu2204, ubuntu2404, rocky8) are also failing with the same error message.

Tom Clegg wrote:

Building packages worked after the previous merge, but after the #20311 merge (plus one unrelated-looking merge 8028981fd that didn't need to build a rails package) we're failing on arvados-api-server

We're not failing on arvados-api-server. The package build script follows the pattern of some of our other build tools where it sets a global exit code based on failure, but still continues its work and only exits with that error code at the end. arvados-api-server just happens to be the last package it builds. This is the real error:

Package arvados-docker-cleaner_3.2.0~dev20250804004422-1_amd64.deb not found, building
Building deb (amd64) package for arvados-docker-cleaner from /arvados/services/dockercleaner

Error: /root/go/bin/pam_arvados.so=/usr/lib/pam_arvados.so: Unable to figure out package name from fpm results:

{:timestamp=>"2025-08-07T21:12:57.098769+0000", :message=>"Invalid package configuration: Cannot package the path '/usr/lib/arvados-docker-cleaner/share/doc/arvados-docker-cleaner/arvados-docker-cleaner.service', does it exist?", :level=>:error}

fpm returned an error executing the command:

env -C /tmp/pybuild.UH1YjCp8 fpm --chdir=/usr/lib/arvados-docker-cleaner --name=arvados-docker-cleaner --version=3.2.0~dev20250804004422 --input-type=dir --output-type=deb --depends=python3.11 --iteration=1 --replaces=python-arvados-docker-cleaner --url=https://arvados.org --license= --description=Arvados Docker image cleaner --maintainer Arvados Package Maintainers <packaging@arvados.org> --vendor The Arvados Project --after-install /arvados/build/go-python-package-scripts/postinst --before-remove /arvados/build/go-python-package-scripts/prerm --deb-no-default-config-files share/doc/arvados-docker-cleaner/arvados-docker-cleaner.service=/lib/systemd/system/arvados-docker-cleaner.service bin/arvados-docker-cleaner=/usr/bin/arvados-docker-cleaner .=/usr/lib/arvados-docker-cleaner

(My best guess is that the references to pam_arvados.so represent a bug in the script.)

I believe the fix is b6bba268483cf9ae7841ba5aa19f7de81359156c. This change let me build the package locally.

20311-python-license @ 1b7ea61dcae6d9df20da5bcd6b9ba8cb07499575 - build-packages-multijob: #4785

RPM builds are failing because they strictly require a license field, and the way we were passing through the Python license field doesn't work anymore. This is a slightly more involved fix to address that.

20311-python-license LGTM