On Sat, 06 Oct 2018 20:39:42 -0400,
Paul Colquhoun wrote:
>
> On Sunday, 7 October 2018 8:34:39 AM AEDT Jack wrote:
> > On 2018.10.06 16:29, John Covici wrote:
> > > On Sat, 06 Oct 2018 14:55:53 -0400, Rich Freeman wrote:
> > > > On Sat, Oct 6, 2018 at 2:04 PM John Covici <cov...@ccs.covici.com>
> > >
> > > wrote:
> > >>> So, I have not been able to figure this out, it did not abort and
> > >>> wants to install the masked package, so hear is the whole output
> > >>> --- thanks for all your help.
> > >>
> > >> What is the actual package.mask set to? Does the same mask cover
> > >> both the installed and upgraded version of gtk+? It seems odd to me
> > >> that emerge would even offer the option to continue if a package was
> > >> masked. You might want to check with the portage team.
> > >
> > > The line in my /etc/portage/package.mask says
> > > x11-libs/gtk+-3.22.30
> >
> > For a specific version, you probably want that to be
> > =x11-libs/gtk+-3.22.30
> > or
> >
> > >=x11-libs/gtk+-3.22.30
> >
> > although the # in
> > [ebuild U #] x11-libs/gtk+-3.24.1:3::mv [3.22.30:3::gentoo]
> > seems to show it knows it is listed in package.mask.
>
>
> Apart from the package.mask syntax error, there is also an emerge flag you
> might want to try:
>
> --autounmask-keep-masks y
>
> I added this when emerge kept asking me to unmask stuff I had manually masked.
Thanks for the tip, I never heard of that one.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
cov...@ccs.covici.com
