such that my o/s patching
is always working against something stable. Woe unto you that assumes their yum
update on 2 different machines is the same if you don't have a mirror you
control, or you don't check your /etc/yum.log.
Tim Kanuka
Canadian Light Source Inc.
-Original Mess
we see this behaviour. (It did trip me up when during the
6.6->6.7 upgrade because I update my machines against a local mirror that is
configured somewhat differently than the scientificlinux.org repos.)
Tim Kanuka
Canadian Light Source Inc.
To all:
Thank you for the links to grunt and the gurulabs presentation - I have not
come across those before. Here's another toolset that I have just started
exploring:
https://github.com/marquiz/git-buildpackage-rpm/
http://marquiz.github.io/git-buildpackage-rpm/gbp-rpm.html
The idea is to bui
To all:
I notice that the version of the various MariaDB packages in the
7x/x86_64/os/Packages/ repo are all currently 5.5.41. Would we expect any
coming updated packages to MariaDB to appear in the security or fastbugs
directories as appropriate, just like the former SL6x MySQL 5.1 packages did
test your
applications on an updated *test* environment. The only way to guarantee that
your *production* environment is updated in the same way as the *test*
environment is to have a mirror repo that is not changing unexpectedly.
Tim Kanuka
Canadian Light Source
-Original Message-
