Hi folks,
Does anyone know of a reason why the bin32- acroread packages can't be deleted? The standard acroread packages support both arches now.
(Just thought I'd check I wasn't missing anything before getting trigger happy...)
Cheers,
Pete.
On 30 November 2010 17:36, Peter Lewis plewis@aur.archlinux.org wrote:
Hi folks,
Does anyone know of a reason why the bin32- acroread packages can't be deleted? The standard acroread packages support both arches now.
(Just thought I'd check I wasn't missing anything before getting trigger happy...)
Which one have to be deleted?
On Tuesday 30 November 2010 16:38:42 Andrea Scarpino wrote:
On 30 November 2010 17:36, Peter Lewis plewis@aur.archlinux.org wrote:
Does anyone know of a reason why the bin32- acroread packages can't be deleted? The standard acroread packages support both arches now.
(Just thought I'd check I wasn't missing anything before getting trigger happy...)
Which one have to be deleted?
Sorry, should have included some specifics:
Well, bin32-acroread (http://aur.archlinux.org/packages.php?ID=7906) appears to be superceded by acroread (http://aur.archlinux.org/packages.php?ID=16980)
and likewise with:
bin32-acroread-ja / acroread-ja bin32-acroread-de / acroread-de
The other language ones haven't been converted though (yet), except acroread- fi, for which there's just the one package.
Pete.
On 30 November 2010 17:49, Peter Lewis plewis@aur.archlinux.org wrote:
Well, bin32-acroread (http://aur.archlinux.org/packages.php?ID=7906) appears to be superceded by acroread (http://aur.archlinux.org/packages.php?ID=16980)
and likewise with:
bin32-acroread-ja / acroread-ja bin32-acroread-de / acroread-de
deleted with no issues.
aur-general@lists.archlinux.org