I have a Pi Zero that I was using for making a non-network printer available on the network. I had to reinstall the software, and I selected Trixie (32-bit, Lite) as it was the latest.

However, the printer-driver-gutenprint package doesn't seem to be present, so I can't get it working again.

This is part of Debian Trixie. https://packages.debian.org/stable/prin ... gutenprint

Anyone have any insight.

can confirm: missing from 32-bit trixie repo, present in 64-bit

‘Remember the Golden Rule of Selling: "Do not resort to violence."’ — McGlashan.
Pronouns: he/him

Thanks for the confirmation. I believe there was an option to install a 32-bit bookworm image instead. Is there a way to check to see if the printer-driver-gutenprint is in that release's repo?

PiZeroPrint wrote: ↑

Thu Nov 06, 2025 8:48 pm

I believe there was an option to install a 32-bit bookworm image instead. Is there a way to check to see if the printer-driver-gutenprint is in that release's repo?

printer-driver-gutenprint is available for 32-bit Bookworm.

but it should be in 32-bit Trixie, as it's in Debian Trixie. Perhaps an oversight

‘Remember the Golden Rule of Selling: "Do not resort to violence."’ — McGlashan.
Pronouns: he/him

PiZeroPrint wrote: ↑

Thu Nov 06, 2025 8:48 pm

Is there a way to check to see if the printer-driver-gutenprint is in that release's repo?

The link in your original post allows that1. If you scroll to the bottom you can see that the trixie package is only downloadable for 64bit architectures. But if you click the bookworm link at the top right, that package exists for 32bit architectures as well.

Also, if you click "Debian Changelog" at the right on the original trixie page, you can find the reason: The bugs referenced are at 1064088 and 1064089. I do not understand the connection between the 64bit time_t policy and the build errors.

There was a thread recently about cyrus-imapd not being available in 32bit trixie. In that case I could not find the reason, now I suspect it is the same. Perhaps the much vaunted solution to the Y2038 problem in trixie was partially achieved by just dropping any difficult packages 13 years ahead of time.

1 Technically, the Debian package lists only confirm if the package is in Debian armhf, and in rare cases a package could be missing from Raspbian armhf, which is still used as the basis of 32bit RPOS. But unless you need compatibility with first-generation Pi1 or Zero1, you could install the Debian armhf package anyway, if it still existed.

Thanks all. That explains things. I will reflash the SD card with bookworm.

And hopefully someone looking to set up a wireless print server and runs into this problem will see this thread in a google search. Nothing showed up for me.