Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Fabian Groffen <grobian@g.o>
Subject: Re: RFC: virtual/shadow
Date: Mon, 12 Mar 2012 11:38:51 +0100
On 12-03-2012 11:35:43 +0100, "Paweł Hajdan, Jr." wrote:
> On 3/12/12 11:27 AM, Fabian Groffen wrote:
> > My rsync0 now spits out this message:
> > 
> >   Virtual package in package.provided: virtual/shadow-0
> >   See portage(5) for correct package.provided usage.
> > 
> > I did not forsee this happening, but each and every Prefix user now gets
> > this complaint on each and every emerge invocation.  It does not seem to
> > block any operation, but could we perhaps hold back further changes
> > until I can sort this out with Zac?
> 
> Ah, I read portage(5) now and adding a virtual to package.provided is
> indeed explicitly prohibited.
> 
> I removed it, but some further changes might be required for prefix
> (i.e. version number >= 4.1 in package.provided to satisfy the virtual),
> and I'll indeed hold back further changes in that area,
> and preferably just let you do any necessary fixes for prefix.

Thanks a lot for your swift actions!


-- 
Fabian Groffen
Gentoo on a different level
Attachment:
signature.asc (Digital signature)
References:
RFC: virtual/shadow
-- Paweł Hajdan, Jr.
Re: RFC: virtual/shadow
-- Paweł Hajdan, Jr.
Re: RFC: virtual/shadow
-- Fabian Groffen
Re: RFC: virtual/shadow
-- Paweł Hajdan, Jr.
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: RFC: virtual/shadow
Next by thread:
eselect repository moved to git
Previous by date:
Re: RFC: virtual/shadow
Next by date:
Lastrite: dev-ada/qtada


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.