libcourier-auth Debian packaging issue

Hi all,


I'm trying to build .deb's to be able to install the latest versions of 
courier (1.3.7), courier-authlib (0.72.1) & courier-unicode (2.3.0).

I'm building within a Docker container, so I don't pollute my desktop 
environment.

Early on in the process I create a `courier` user & group for Courier to 
run as, then instruct Docker to switch to that new user before I 
download, and un-tar the tarballs.

I verified this by adding `RUN whoami` to the Dockerfile, and I got 
`courier`.

I then run `courier-debuild -us -uc`, which Docker is still running as 
the `courier` user, but the resultant .deb's are dependant on 
`libcourier-auth-config-daemon-daemon_0.72.1-100_amd64.deb`.  This .deb 
file is created by `courier-debuild` - that's not the primary issue as 
far as I can tell.

I also recall there being some discussion in the mailing list about 
tweaking the authlib build process to "guard against updates to newer 
versions with different compilation options" (courier-authib 0.72.1 
release announcement on 31 Jan, 2024), and that this would result in RPM 
& DEB packages being built with a username & group included in the 
package name, as per the above - I can't seem to find that discussion now.

As the resultant .deb has `daemon-daemon` in the file name, am I correct 
in thinking that it has been configured to use the user & group of 
`daemon:daemon`?  IF that is the case, how do I change it to use 
`courier:courier`, given that I'm running `courier-debuild` from the 
`courier` user account?


Regards,

Krystal.



_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users