Re: Building rpms in mock

I'm quoting extensively because context is is important here.

> As long as they rebuild and update directly, on the live 
> system, they'll be fine. courier-authlib's configure will 
> find the existing one, and use the same mail user and group 
> names that the existing installation does.

> But if someone's building the packages in mock, the mock 
> chroot will now have courier uid and gid in it, and the 
> updated courier-authlib package gets built with that. 
> Then it upgrades an existing package which was build with 
> mailuser/mailgroup. The binaries will be ok. All configuration 
> files and runtime directories and files are now completely 
> broken. That's going to seriously mess things up.

Yes, but. These legacy considerations create an obstacle
to courier going forward, getting included in distros and
gaining a wider user base, while also perpetuating all
the problems that arise from different user:group and
uid:gid. So I think it would be correct to say that the
issue here is not what should be done, but how it should
be done in order to minimise damage to existing installations.

(In a parenthesis, I have been using courier since 2001
with courier:courier from the very beginning. Yet I have
lost track of how many times I ended up with a broken
upgrade because I built courier on a system other than
the one that it will run on, and got user:group wrong.
In my case these messes are almost a necessity, because
I never install compilers and other such on production
systems, so courier always gets built on a system other
than the one that it will run on. Thus, I can attest that
damage to existing installations is also being done
regularly by the current user:group logic.)

> I should find a way to prevent that from happening.

You already have: --define 'notice_option --with-notice=unicode'.

A similar emergency break kan be applied to the legacy
random user:group risk. "If you are updating an existing
installation that uses anything other than user=courier
group=courier, please add --define 'mailuser <your_user>'
--define 'mailgroup <your_group>' to your build command,
or else use --define 'uidgidbreakage ihavebeenwarned' to
build as user=courier group=courier anyway.

Z


-- 
Слава Україні!
Путин хуйло!


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