CentOS - May 2015 - Systemd

On May 24, 2015 4:46:18 PM PDT, Jonathan Billings <billings at negate.org>
wrote:
>> On May 24, 2015, at 18:24, Kirk Bocek <t004 at kbocek.com> wrote:
>> 
>> So:
>> 
>> $rpm -e --nodeps chrony
>
>No. Bad.
>
Okay, okay! I'll go on the paper.

I'll reinstall chrony. But there *are* places I've needed to use nodeps.
Mostly to manage inter-repo package incompatibilities.

Fortunately this isn't yet a production host but more a chance to learn all
the changes like this, systemd, grub2, xfs, whatever the new firewall is called.
The list keeps growing.

On 25/05/15 15:10, Kirk Bocek wrote:
> The list keeps growing.
oh boy, wait until people hear about ssmtp...

> On May 25, 2015, at 01:10, Kirk Bocek <t004 at kbocek.com> wrote:
> 
> I'll reinstall chrony. But there *are* places I've needed to use
nodeps. Mostly to manage inter-repo package incompatibilities.
You should look into the yum priorities option to ensure packages from different
repos don't step on each other, however I'd consider any yum repository
that requires you break your rpm database to be one to avoid.

--
Jonathan Billings

On 5/25/2015 4:40 AM, Jonathan Billings wrote:
>> On May 25, 2015, at 01:10, Kirk Bocek <t004 at kbocek.com> wrote:
>>
>> I'll reinstall chrony. But there *are* places I've needed to
use nodeps. Mostly to manage inter-repo package incompatibilities.
> You should look into the yum priorities option to ensure packages from
different repos don't step on each other, however I'd consider any yum
repository that requires you break your rpm database to be one to avoid.
>
>
It usually happens when I've wanted to change versions of the same 
software between repos and that software has been compiled differently. 
Usually audio-visual software. Yum install triggers a conflict and yum 
uninstall on the older package cascades a bunch of undesirable 
uninstalls. The only solution is rpm -e -nodeps followed by installing 
the newer package.

If you have a better solution, let me know.

On Mon, May 25, 2015 12:10 am, Kirk Bocek wrote:
>
>
> On May 24, 2015 4:46:18 PM PDT, Jonathan Billings <billings at
negate.org>
> wrote:
>>> On May 24, 2015, at 18:24, Kirk Bocek <t004 at kbocek.com>
wrote:
>>>
>>> So:
>>>
>>> $rpm -e --nodeps chrony
>>
>>No. Bad.
>>
>
> Okay, okay! I'll go on the paper.
>
> I'll reinstall chrony. But there *are* places I've needed to use
nodeps.
> Mostly to manage inter-repo package incompatibilities.
>
> Fortunately this isn't yet a production host but more a chance to learn
> all the changes like this, systemd, grub2, xfs, whatever the new firewall
> is called. The list keeps growing.
>
The need to use --nodeps undermines the idea of rpm based (or more
generally package based) system maintained in harmony by system vendor
(and extra repository vendors). Basically, you become individual system
vendor for yourself, which is a lot of work. If it comes to that, then you
will be in much better shape (from the point of view of how much time you
spend on keeping your box in harmony with all components working) if you
switch from package management based system to source build based system.
Examples of the last just off the top of my head would be: gentoo linux,
FreeBSD, NetBSD... The last two  are sort of "port based systems" as
far
as extra software is concerned. (Of course, BSD boxes in addition to ports
have package management, so in their case you can maintain system either
way: as prebuilt packages, or as building ports yourself, the last gives
you ability to change configuration options of what you build to your
specific needs).

Not intending to criticize what you are doing, just giving you an idea
what it looks like for external observer.

Just my $0.02

Valeri

++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
++++++++++++++++++++++++++++++++++++++++