Closed EoD closed 11 years ago
Everything in my overlay should have no collisions with my emul linux x86 packages On 18 Aug 2013 10:55, "EoD" notifications@github.com wrote:
Hey,
it might be some hassle, but could you please remove the amd64 stable keyword from the packages you create? I personally only install what is necessary for my needs and don't want to install all of them.
The reason why I'm filing that issue is that I can't do a normal "emerge -vuDN @world https://github.com/world @systemhttps://github.com/system" because some of your new packages collide with what I have installed and I have to go through a long list and mask them manually.
— Reply to this email directly or view it on GitHubhttps://github.com/FireBurn/Overlay/issues/35 .
No, there were no file collisions. I couldn't do a world emerge because your packages depend on packages which collided with what I had installed. It was somewhere deep in the tree (e.g. the gst stuff). If you need it, I can look it up later when I'm at home.
Are you still having issues with this?
No, I can't reproduce it with the current, but I changed my system config a lot over the last week(s).
It happened when I made a completely new install of the FireBurn overlay.
Hey,
it might be some hassle, but could you please remove the amd64 stable keyword from the packages you create? I personally only install what is necessary for my needs and don't want to install all of them.
The reason why I'm filing that issue is that I can't do a normal "emerge -vuDN @world @system" because some of your new packages collide with what I have installed and I have to go through a long list and mask them manually.