Re: .debs for courier products

Mike:

The process of building .deb's from Sam's courier source is outlined in the
INSTALL within each source package (and is best done on a clean system or
after purging the Ubuntu packages).

However, those .deb's are laid out according to Sam's recipe for installing
courier; whereas the Ubuntu packages go by Ubuntu's recipe. Mostly, the
differences are in the directory layout and ownership of the
executables/permissions.

There are enough differences that it's a pain to try to mix the two. At the
bug link in my message you quoted I provide the quick recipe for installing
Sam's debs. Just follow that if you are building from Sam's source.

Another approach would be to use the list of package names for courier that
you know from 22.04 to find the *deleted* packages from 24.04, and
individually download those, so you can install them anyway.

E.g. https://launchpad.net/ubuntu/noble/amd64/courier-imap

Look there, and download the most recent deleted package. Do that for all
the remaining packages. Then install them (possibly with --force) in the
right order. In this way, you'll have installed courier using packages
Ubuntu built (but for some unknown reason deleted from 24.04), in Ubuntu's
recipe for directory and ownership structure.

There are pros and cons to both methods. I can report that installing Sam's
packes works just fine and I only had to change a couple of executable
references in my config files (grep for /usr in the configs) and also
change MAILUSER and MAILGROUP from courier to daemon. This is basically
what's spelled out in the bug link above.

A.


On Mon, Dec 2, 2024 at 5:43 PM Mike Wright <[email protected]>
wrote:

> On 12/1/24 16:39, Andrew Athan wrote:
>  > If this is on ubuntu and you are running into problems replacing the
> 24.04
>  > packages with an install from deb's build from upstream courier: see my
>  > notes here,
> https://bugs.launchpad.net/ubuntu/+source/courier/+bug/2071662
>
>
> Hi Andrew, I'm very interested in this.
>
> All told, I'd be much happier using debs than compiling courier
> packages.  For starters, it's a lot less work and I know where
> everything is and already have my tools customized to work with that.
>
> How is this deb creation handled?  Some build option? Some after the
> fact created by package maintainers?  Is it available for mere mortals?
> Inquiring minds, etc.
>
> I am familiar with debs and have created some simple ones for my own
> purposes.  One is for use on hosting providers such as Digital Ocean.  I
> spin up a vm, install openssh-server and rsync, upload my deb and dpkg
> -i it.  Instant firewall with access from my IP and a user account with
> my certificate already in place.
>
> Thanks,
> Mike Wright
>

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