wizzomafizzo at gmail.com
Thu Jan 1 23:18:25 EST 2009
On Fri, Jan 2, 2009 at 10:15 AM, Jonathan Wiersma
<aurgeneralsub at jonw.org> wrote:
> I'm confused... I noticed my lib32-glibc was out of date, so I went to
> check where I should flag it as being out of date:
> I did a search on http://www.archlinux.org/packages/?q=lib32-glibc and
> and did not find any lib32-glibc packages (although a ton of AUR packages
> depend on it). So I created a new on in AUR. Now I just checked pacman -Ss
> lib32-glibc and it comes-up with:
> community/lib32-glibc 2.8-3 (lib32)
> GNU C Library (32 Bit)
> I'm guessing this is a bug, but I'm not sure if I should be requesting the
> lib32-glibc package I created be deleted because it's already in community
> or if I should leave it.
At the moment the community scripts don't add 64bit-only packages to
the AUR. These lib32 packages are only meant for 64bit so they do
exist in community but the AUR won't show them. The package you've
made on the AUR should be deleted.
This is a bug but it's already known and isn't really harmful or
anything, the AUR just doesn't have a proper concept of arches yet.
More information about the aur-general