[aur-general] Keeping community64 up to date
belanger at ASTRO.UMontreal.CA
Thu Mar 27 14:36:21 EDT 2008
On Thu, 27 Mar 2008, JJDaNiMoTh wrote:
> On Fri, 21 Mar 2008 21:37:20 +1000
> Allan McRae <allan.mcrae at qimr.edu.au> wrote:
>> I have come to realize that the current way of keeping community64 in
>> sync could use some improving. I realized this when looking at the
>> pkg_diff web page  thinking I would build some packages. After being
>> distracted by the internet for a few minutes... I reloaded the page and
>> noticed that some of the packages had been uploaded. Now had I actually
>> built those packages, it would have been a waste of time. Also, I'm
>> never sure how much time to wait and see whether the TU who uploaded the
>> i686 package is going to upload the x86_64 package.
> Uhm... maybe the man that has uploaded these packages was I :)
> Simply, at this point, with Aaron's building machine and some of us
> which have 32/64 bit hardware, I don't understand why there are ~ 150
> different packages from 32 to 64 bit community.
You also need to consider that the 32 and 64 community repo will never be
completely in sync because of lib32 stuff and of packages that don't work
> Last thing: we some packages maintained by devs in community or
> community64 out-of-date, and recompile it seems do not work because the
> older release. What we need to do?
Inform the maintainer. Offer to do the update for both arch if they are
too busy to do it.
> Last last: What about dtw? We have a lot of his packages in community
> out-of-dated , in this page  seems he isn't a TU, but has 3 bug
> opened . IMHO, the best is moving all his packages back to
> unsupported and close bug assigned to him.
>  http://aur.archlinux.org/packages.php?K=dtw&SeB=m
>  http://wiki.archlinux.org/index.php/Trusted_Users
I think dtw is unofficially inactive. Email him to ask about his status.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the aur-general