[gentoo-user] libxml2 conflicts

[gentoo-user] libxml2 conflicts

[James]

Hello,


>>

I really like using 'autounmask' with portage issues.
So my package.use file has (2) sections. The first is where I list
a package and then the use flag settings for that specific package,
traditional usage of package.use, imo. The second section, below these
entries is where autounmask writes it's entries; and they seems to never be
pruned, just new entries at the bottom..... libxm2l has many entries in  the
second section and now I have a conflict. It is nice the way comments are
added to entries which lists the packages needing the flag. But after a
while the file grows too long, imho.


Every thing just upgraded except libxml2. Here is what I now get::

 emerge -uDNvp world

These are the packages that would be merged, in order:
Calculating dependencies... done!
WARNING: One or more updates/rebuilds have been skipped due to a dependency
conflict:
dev-libs/libxml2:2
  (dev-libs/libxml2-2.9.2-r4:2/2::gentoo, ebuild scheduled for merge)
conflicts with
    dev-libs/libxml2:2[-icu,abi_x86_32(-),abi_x86_64(-)] required by
(dev-qt/qtwebkit-4.8.6-r1:4/4::gentoo, installed)

 egrep libxml package.use
=dev-libs/libxml2-2.9.1-r1 python
>=dev-libs/libxml2-2.9.1-r4 python
>=dev-libs/libxml2-2.9.1-r4 icu
>=dev-libs/libxml2-2.9.2 -icu
>=dev-libs/libxml2-2.9.2 abi_x86_32
>=dev-libs/libxml2-2.9.2-r4 icu
=dev-libs/libxml2-2.9.2-r1 icu


So I guess a  manual clean up package.use is in order. Maybe parse all the
libml2 entries and consolidate them into a single entry in the section One
of the /etc/portage/package.use file? Maybe I should curtail my use of
'autounmask' as it seems to not have a mechanism to autoclean itself with
multiple conflicting entries. Note:: I have 'autounmask-write y' in the
make.conf file.


Beside a specific resolution, I guess I'm curious as to other gentoo-admin
philosophies related to autounmask usage and keeping the package.use file
reasonable and as concise as possible. Suggestions?


James

Re: [gentoo-user] libxml2 conflicts

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

On Wed, 13 Jan 2016 16:52:15 +0000 (UTC), James wrote:

> Beside a specific resolution, I guess I'm curious as to other
> gentoo-admin philosophies related to autounmask usage and keeping the
> package.use file reasonable and as concise as possible. Suggestions?
> 
I use a directory for package.use, then autounmask puts its entries in
the last file in there, so I have a file called zzz-autounmask. It's
pretty easy to clean up, just delete/move it and run emerge -u @world
again and it will be repopulated with any settings that are still needed.


-- 
Neil Bothwick

[unwieldy legal disclaimer would go here - feel free to type your own]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[gentoo-user] Re: libxml2 conflicts

[James]

Neil Bothwick <neil <at> digimed.co.uk> writes:


> I use a directory for package.use, then autounmask puts its entries in
> the last file in there, so I have a file called zzz-autounmask. It's
> pretty easy to clean up, just delete/move it and run emerge -u  <at> world
> again and it will be repopulated with any settings that are still needed.


OK, I'll give this a spin. One questions, where to move/name the traditional
flag settings I have in the top of the old file, here are a few for clarity::

media-sound/hydrogen    portaudio
dev-util/valgrind       mpi
net-irc/quassel         webkit
app-portage/layman      sync-plugin-portage  subversion  
net-wireless/kismet     -bluetooth
net-libs/libpcap        -bluetooth
sci-libs/hdf5           -cxx examples -fortran threads zlib mpi


Two file, zzz-autounmaks for it's entris and just place those above in this
file::/etc/portage/package.use/package.use?

And both  get properly parsed by emerge updates? 


James

Re: [gentoo-user] Re: libxml2 conflicts

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

On Wed, 13 Jan 2016 17:24:21 +0000 (UTC), James wrote:

> > I use a directory for package.use, then autounmask puts its entries in
> > the last file in there, so I have a file called zzz-autounmask. It's
> > pretty easy to clean up, just delete/move it and run emerge -u  <at>
> > world again and it will be repopulated with any settings that are
> > still needed.  
> 
> 
> OK, I'll give this a spin. One questions, where to move/name the
> traditional flag settings I have in the top of the old file, here are a
> few for clarity::
> 
> media-sound/hydrogen    portaudio
> dev-util/valgrind       mpi
> net-irc/quassel         webkit
> app-portage/layman      sync-plugin-portage  subversion  
> net-wireless/kismet     -bluetooth
> net-libs/libpcap        -bluetooth
> sci-libs/hdf5           -cxx examples -fortran threads zlib mpi
> 
> 
> Two file, zzz-autounmaks for it's entris and just place those above in
> this file::/etc/portage/package.use/package.use?
> 
> And both  get properly parsed by emerge updates? 
> 
Exactly. When package.* is a directory, portage treats all of its
contents as a single file, in lexical order. Look at the description
for /etc/portage/ in the portage man page.


-- 
Neil Bothwick

Accordion: a bagpipe with pleats.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[gentoo-user] Re: libxml2 conflicts

[»Q«]

On Wed, 13 Jan 2016 17:01:47 +0000
Neil Bothwick <neil@digimed.co.uk> wrote:

> I use a directory for package.use, then autounmask puts its entries in
> the last file in there, so I have a file called zzz-autounmask. It's
> pretty easy to clean up, just delete/move it and run emerge -u @world
> again and it will be repopulated with any settings that are still
> needed.

Thanks for that.  I haven't been using autounmask, partly because I
didn't think it could handle package.* a directories.  (Maybe I was
wrong all along or maybe when autounmask debuted I was right;  doesn't
matter now.)



  

Re: [gentoo-user] Re: libxml2 conflicts

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

On Wed, 13 Jan 2016 12:51:07 -0600, »Q« wrote:

> > I use a directory for package.use, then autounmask puts its entries in
> > the last file in there, so I have a file called zzz-autounmask. It's
> > pretty easy to clean up, just delete/move it and run emerge -u @world
> > again and it will be repopulated with any settings that are still
> > needed.  
> 
> Thanks for that.  I haven't been using autounmask, partly because I
> didn't think it could handle package.* a directories.  (Maybe I was
> wrong all along or maybe when autounmask debuted I was right;  doesn't
> matter now.)

Directories have always worked with automask because portage translates
the contents to a single file anyway. The only thng you have to be
careful of is file naming, because automask always adds ot the end of
package.use, which means it modifies the last file.


-- 
Neil Bothwick

If you can't be kind, be vague.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]