#1110733 fails on packages without priority

Package:
reprepro
Source:
reprepro
Description:
Debian package repository producer
Submitter:
Date:
2026-06-25 15:17:02 UTC
Severity:
normal
Tags:
#1110733#5
Date:
2025-08-10 15:14:39 UTC
From:
To:
Hi,

as of trixie, the the priority field isn't required anymore. reprepro
fails to import such packages (e.g. pci.ids 0.0~2025.07.11-1):
---snip---
No priority for 'pci.ids', skipping.
There have been errors!
---snap---

Regards,
Daniel
#1110733#8
Date:
2025-09-09 11:00:20 UTC
From:
To:
Re: Daniel Baumann

I also hit that on apt.postgresql.org.

A workaround is to update the .changes files, replacing "-" with
"optional". (No change in the .deb or .dsc required.)

sed -i -e 's/^\( [0-9a-f]\{32\} [0-9]\+ [a-z]\+\) - /\1 optional /' /srv/apt/$QUEUE/*.changes

Unfortunately the `-P, --priority priority` switch advertised in the
manpage doesn't work for processincoming.

IMHO reprepro should just fill in "optional" on its own there.

I haven't checked if it's a problem, but "Section" is also optional
and might have the same issue.

Christoph
#1110733#13
Date:
2026-01-03 19:46:07 UTC
From:
To:
Hi!

Hmm, but this is supposed to be handled transparently, where dpkg-dev
tools will fill in the Priority so that any generated artifact still
contains one.

Are these source packages from Debian forky/sid, being built with a dpkg
from Debian bookworm? (dpkg >= 1.22.13 in trixie/forky/sid should already
have the support to handle this transparently.)

Thanks,
Guillem
#1110733#16
Date:
2026-01-04 21:51:55 UTC
From:
To:
Re: Guillem Jover

Yes, the host doing the source package build is on bookworm. Thanks
for the hint, I'll see to get it upgraded to trixie.

Christoph
#1110733#21
Date:
2026-06-25 14:39:37 UTC
From:
To:
There is no reason to allow changes files without Priority.
Please build your packages with an appropriate dpkg version.