[arch-general] Xulrunner as makedepend while eclipse is installed
Because of [ 0 ] now eclipse and xulrunner packages conflict. I maintain two AUR packages [ 1 ] that need xulrunner at build time and I also have installed eclipse. I know building that packages in a clean chroot can be a solution but I'm afraid that is not what I can assume they will do about all users of the mentioned packages. Any idea of what could be done? [ 0 ] https://bugs.archlinux.org/task/28724 [ 1 ] https://aur.archlinux.org/packages.php?O=0&K=firetray-svn&do_Search=Go
On Fri, Mar 2, 2012 at 11:01 AM, Alexandre Ferrando
Because of [ 0 ] now eclipse and xulrunner packages conflict. I maintain two AUR packages [ 1 ] that need xulrunner at build time and I also have installed eclipse.
I know building that packages in a clean chroot can be a solution but I'm afraid that is not what I can assume they will do about all users of the mentioned packages.
Any idea of what could be done?
[ 0 ] https://bugs.archlinux.org/task/28724 [ 1 ] https://aur.archlinux.org/packages.php?O=0&K=firetray-svn&do_Search=Go
Not sure if it helps, but wonder (one of Arch devs) wrote: https://bbs.archlinux.org/viewtopic.php?pid=1066130#p1066130 "you can ignore the update until monodevelop and his dependecies are fixed"
On 03/02/2012 12:01 PM, Alexandre Ferrando wrote:
Because of [ 0 ] now eclipse and xulrunner packages conflict. I maintain two AUR packages [ 1 ] that need xulrunner at build time and I also have installed eclipse.
I know building that packages in a clean chroot can be a solution but I'm afraid that is not what I can assume they will do about all users of the mentioned packages.
Any idea of what could be done?
[ 0 ] https://bugs.archlinux.org/task/28724 [ 1 ] https://aur.archlinux.org/packages.php?O=0&K=firetray-svn&do_Search=Go
I don't see how can i solve this problem other than having conflicts. -- Ionuț
Ionut Biru said the following at 03/02/2012 04:23 AM :
On 03/02/2012 12:01 PM, Alexandre Ferrando wrote:
Because of [ 0 ] now eclipse and xulrunner packages conflict. I maintain two AUR packages [ 1 ] that need xulrunner at build time and I also have installed eclipse.
What should an ordinary user do when updating eclipse and he receives the message about conflicts and whether xulrunner should be removed? (I've just been escaping out of the attempted update with ctrl-C, on the assumption that this is a temporary situation and will soon be fixed. Is that a sensible thing to do, or is there some better way to proceed? It does mean that all the other updates are not performed, and that list is getting quite long now.) Doc Evans -- Web: http://www.sff.net/people/N7DR
On Wed, Mar 7, 2012 at 9:06 PM, D. R. Evans
What should an ordinary user do when updating eclipse and he receives the message about conflicts and whether xulrunner should be removed?
If you don't need xulrunner for any other app, I guess it's OK to remove it ...
Go ahead and tell it that xulrunner to be removed. If it is a dependency of something else, pacman will automatically stop and tell you that. -----Original Message----- From: arch-general-bounces@archlinux.org [mailto:arch-general-bounces@archlinux.org] On Behalf Of D. R. Evans Sent: Wednesday, March 07, 2012 3:06 PM To: arch-general@archlinux.org Subject: Re: [arch-general] Xulrunner as makedepend while eclipse is installed What should an ordinary user do when updating eclipse and he receives the message about conflicts and whether xulrunner should be removed? (I've just been escaping out of the attempted update with ctrl-C, on the assumption that this is a temporary situation and will soon be fixed. Is that a sensible thing to do, or is there some better way to proceed? It does mean that all the other updates are not performed, and that list is getting quite long now.) Doc Evans -- Web: http://www.sff.net/people/N7DR
What should an ordinary user do when updating eclipse and he receives the message about conflicts and whether xulrunner should be removed?
(I've just been escaping out of the attempted update with ctrl-C, on the assumption that this is a temporary situation and will soon be fixed. Is that a sensible thing to do, or is there some better way to proceed? It does mean that all the other updates are not performed, and that list is getting quite long now.)
Wait for a new version of eclipse, or use pactree to figure out which package to remove: $ pactree -r xulrunner $ pactree -r eclipse Or you can ignore (-syu --ignore ...) the eclipse upgrade, but I believe that will leave it broken, which suggests you might as well remove it anyway. Or you can compile eclipse yourself, against the current xulrunner - this is probably difficult, and might be a waste of time anyway.
participants (6)
-
Alexandre Ferrando
-
D. R. Evans
-
Eric Ryan Jones
-
Ionut Biru
-
Karol Blazewicz
-
Yclept Nemo