michael schuster schreef op 24-02-10 10:12:
>> $ pkg set-publisher -g http://solaris.bionicmutton.org:10001 bionicmutton
>> pkg set-publisher:
>> One or more of the repository origin(s) listed below contains package
>> data for mypkgs; not bionicmutton:
>>
>> http://solaris.bionicmutton.org:10001/
>>
>> This is either because one of the repository origins is not valid for
>> this publisher, or because the list of known publishers retrieved from
>> the repository origin does not match the client.
>
>
> this isn't a severe limitation, but looks a little strange.
It's a documented change. I think it's all about the relation between
publishers ("mypkgs") and repositories.
("http://solaris.bionicmutton.org:10001/";)
A publisher can have many (possibly mirrored) repositories, which can be
correctly recognized as all being the same now. It only requires to
configure your repository with a sensible name, I don't think that's too
much to ask.
By not allowing users to configure their own name for publishers, FRMI's
will also be the same for everywhere: a package like x11/library/mesa
will now always have the FRMI pkg://opensolaris.org/x11/library/mesa at ...
instead of sometimes being called
pkg://opensolaris-dev/x11/library/mesa at ..., etc.
You don't have to specify a name anymore while adding a publisher btw,
so this is enough now, and will never fail because of a mismatch:
pkg set-publisher -g http://solaris.bionicmutton.org:10001
Onno
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
URL:
<http://mail.opensolaris.org/pipermail/kde-discuss/attachments/20100224/094f2f7a/attachment.bin>
