[aur-general] Keeping community64 up to date

[Ronald van Haren]

On Thu, Mar 27, 2008 at 4:54 PM, JJDaNiMoTh <jjdanimoth at gmail.com> wrote:
>
>  pressh: Your e17 packages are effectively hard to maintain ( for
>  circular dep, and others that you explain here ). Do you have a 64
>  hardware or you need an hand? In this case, tell us ( a solution could
>  be found ).
>
I don't have much time at the moment to answer all your questions, so
at this point I only answer the question directed to me. I may find
time later tonight (or someone else may have jumped in by then) to
discuss more about syncing i686 and x86_64.

No I have no x86_64 hardware :( so I only build i686 myself. Eric
(Snowman) is building the x86_64 e17 packages. He usually updates the
x86_64 within a few days after I update the i686 packages (which I do
on a two weekly basis), that is if he has the time to do so. I noticed
he missed the last update (10 days ago), but I assume this is because
he is busy doing more important things.
I expect him to update the x86_64 packages on the next update. I keep
an eye on it so if major lagging occurs I will contact him, or scream
for help here so someone else can jump in.

All other packages I maintain I build on the x86_64 build machine. At
the moment two of these packages are behind the i686 ones
(kaa-metadata & freevo) as they depend on kaa-base and I had to wait
for the build machine to synchronize. I will build those
today/tomorrow.