On 11/21/2014 08:52 PM, Eric Broch wrote:
On 11/21/2014 7:18 PM, Eric Shubert wrote:
You guys really know how to do things the hard way. I thought you were
up to date with the new way of doing things:
1) Notify EricS that there's a new version if he doesn't already know
2) EricS builds the new rpms
3) Eager users install from /testing/ repo
4) EricS promotes them test /current/
5) All users update safely
I've done step 2 now, so in an hour (giving mirrors time to sync)
you'll be able to:
# yum --enablerepo=qmailtoaster-testing update clamav
to pick up the latest version.
Isn't that easier? ;)
When a few people have reported running it for a few days with no
problems, I'll promote it to current.
Thanks.
EricS,
Sorry, I didn't mean to slight you in any way. I made the binary and
source rpms available to help with the work-load for you and the QMT
community. My intention was that you'd simply download the files from my
site and make sure I had the release numbering schemes correct, which I
did request.
EricB.
---------------------------------------------------------------------
Don't fret, EricB. Any fault is mine for not communicating the process.
Having you build rpms would actually be more difficult, as the whole
build process is scripted now and quite simple to run. Plugging in rpms
built otherwise would be harder than simply rebuilding them using the
scripts. Plus, the rpms wouldn't be properly signed. In addition when
there's a problem, it's difficult to track down where the problem might
be. In general, this adds to any confusion that already exists (largely
due to lack of documentation, which I'll take part of the blame for).
I do appreciate everyone's involvement. I hope we can focus our efforts
though so that our work is as efficient as possible. People should be
working either in github on the front end, or testing on the back end.
Everything else is pretty well automated at this point.
Thanks. :)
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
