[pkg-discuss] Can't install my development bits

Robert Thurlow

unread,

Dec 20, 2011, 12:09:50 PM12/20/11

to pkg-d...@opensolaris.org

Hi folks,

I have a repo, in sync with the final changeset of onnv-clone.
I have done a full build.

I have a machine auto-installed from the Austin lab to build 174
(because it is older than 175). I would like to get my bits on it.
I set the publisher immediately:

# pkg set-publisher -G http://aus-ai.us.oracle.com/solaris -g
http://ipkg.us.oracle.com/solaris11/release solaris
# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online
http://ipkg.us.oracle.com/solaris11/release/

I've tried an onu:

# /ws/onnv-tools/onbld/bin/onu -d
/net/rockyroad/export/builds/thurlow/fedfs/packages/i386/nightly -t fedfs
Preparing zone: global (1/1)
Updating
Packages to remove: 3
Packages to install: 3
Packages to update: 89
Create boot environment: No
Create backup boot environment: No
Services to change: 4

DOWNLOAD PKGS FILES XFER (MB)
Completed 95/95 3545/3545 265.2/265.2$<3>

PHASE ACTIONS
Removal Phase 1562/1562
Install Phase 1845/1845
Update Phase 3728/3728

PHASE ITEMS
Package State Update Phase 184/184
Package Cache Update Phase 92/92
Image State Update Phase 2/2

Only three packages? It didn't get my changes, that's certain.

# reboot
...
# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
fedfs NR / 5.66G static 2011-12-20 08:27
s11_174 - - 39.45M static 2011-12-20 00:43
# which nsdb-list
no nsdb-list in /usr/bin /usr/gnu/bin /usr/sbin /usr/X11/bin /sbin

Back to s11_174. I have pointed to my repo:

# /ws/onnv-tools/onbld/bin/onu -rd \
/net/rockyroad/export/builds/thurlow/fedfs/packages/i386/nightly
# pkg publisher
PUBLISHER TYPE STATUS URI
on-nightly origin online
file:///net/rockyroad/export/builds/thurlow/fedfs/packages/i386/nightly/repo.redist/
on-extra origin online
file:///net/rockyroad/export/builds/thurlow/fedfs/packages/i386/nightly/repo.extra/
solaris (non-sticky) origin online
http://ipkg.us.oracle.com/solaris11/release/
opensolaris.org (non-sticky)
# pkg unset-publisher opensolaris.org

The latest version in sight appears to be what I've built:

# pkg list -a -f pkg:/service/file-system/nfs
NAME (PUBLISHER) VERSION IFO
service/file-system/nfs 0.5.11-0.175.0.0.0.2.18011 ---
service/file-system/nfs (solaris) 0.5.11-0.175.0.0.0.2.1 ---
service/file-system/nfs (solaris) 0.5.11-0.174.0.0.0.0.17765 i--
service/file-system/nfs (solaris) 0.5.11-0.151.0.1 ---

All I really need is to get two packages installed, one changed
and one new:

# pkg update pkg:/service/file-system/nfs
No updates available for this image.

# pkg install pkg:/service/file-system/nfs/fedfs-test
Creating Plan -
pkg install: No matching version of service/file-system/nfs/fedfs-test can be
installed:
Reject:
pkg://on-extra/service/file-system/nfs/fedfs...@0.5.11,5.11-0.175.0.0.0.2.18011:20111220T002343Z
Reason: All versions matching 'require' dependency
pkg:/service/file-system/n...@0.5.11,5.11-0.175.0.0.0.2.18011 are rejected
Reject:
pkg://on-nightly/service/file-system/n...@0.5.11,5.11-0.175.0.0.0.2.18011:20111220T002343Z
Reason: This version is excluded by installed incorporation
pkg://solaris/consolidation/osnet/osnet-inc...@0.5.11,5.11-0.174.0.0.0.0.17765:20110919T155151Z

This seems like it should be simple. What's in my way, and how do I
figure it out? How do I install my stuff?

Thanks,
Rob T
_______________________________________________
pkg-discuss mailing list
pkg-d...@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Bart Smaalders

unread,

Dec 20, 2011, 12:24:41 PM12/20/11

to pkg-d...@opensolaris.org

You're trying to install your packages at version 175
on a OS running build 174. Why do you think this would work?

Did you try pkg update?

- Bart

--
Bart Smaalders Solaris Kernel Performance
bart.sm...@oracle.com http://blogs.sun.com/barts
"You will contribute more with Mercurial than with Thunderbird."
"Civilization advances by extending the number of important
operations which we can perform without thinking about them."

Robert Thurlow

unread,

Dec 20, 2011, 12:58:39 PM12/20/11

to Bart Smaalders, pkg-d...@opensolaris.org

Bart Smaalders wrote:

> You're trying to install your packages at version 175
> on a OS running build 174. Why do you think this would work?

Because it used to work in recent memory?
Because my packages are chronologically newer?
Because my packages have a higher version number?

> Did you try pkg update?

I got two unnamed packages the first time, and now:

# pkg update -nv

No updates available for this image.

Rob T

Bart Smaalders

unread,

Dec 20, 2011, 1:15:26 PM12/20/11

to Robert Thurlow, pkg-d...@opensolaris.org

On 12/20/11 09:58, Robert Thurlow wrote:
> Bart Smaalders wrote:
>
>> You're trying to install your packages at version 175
>> on a OS running build 174. Why do you think this would work?
>
> Because it used to work in recent memory?
> Because my packages are chronologically newer?
> Because my packages have a higher version number?
>
>> Did you try pkg update?
>
> I got two unnamed packages the first time, and now:
>
> # pkg update -nv
> No updates available for this image.
>
> Rob T

The more you tell pkg, the better the errors you'll get.

Since you're connected to the release repo, pkg update *@latest
should do something useful.

- Bart

--
Bart Smaalders Solaris Kernel Performance
bart.sm...@oracle.com http://blogs.sun.com/barts
"You will contribute more with Mercurial than with Thunderbird."
"Civilization advances by extending the number of important
operations which we can perform without thinking about them."

Robert Thurlow

unread,

Dec 20, 2011, 1:52:19 PM12/20/11

to Bart Smaalders, pkg-d...@opensolaris.org

Bart Smaalders wrote:

> The more you tell pkg, the better the errors you'll get.

So what would be the syntax for asking pkg to install my own
bits, that show up marked with "0.5.11-0.175.0.0.0.2.18011"?

> Since you're connected to the release repo, pkg update *@latest
> should do something useful.

I'll give that a try; I've just installed S11 FCS on the box.

More generally, are there any best practices? I am trying
to do something pretty vanilla - have a project gate that
I and others can install from.

Thanks,
Rob T

Robert Thurlow

unread,

Dec 20, 2011, 1:56:56 PM12/20/11

to Bart Smaalders, pkg-d...@opensolaris.org

Robert Thurlow wrote:

> I'll give that a try; I've just installed S11 FCS on the box.

With S11 FCS:

# pkg set-publisher -G http://aus-ai.us.oracle.com/solaris -g http://ipkg.us.ora
cle.com/solaris11/release solaris

# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online http://ipkg.us.oracle.co
m/solaris11/release/

# /ws/onnv-tools/onbld/bin/onu -rd \
/net/rockyroad/export/builds/thurlow/fedfs/packages/i386/nightly

# pkg publisher
PUBLISHER TYPE STATUS URI
on-nightly origin online file:///net/rockyroad/ex
port/builds/thurlow/fedfs/packages/i386/nightly/repo.redist/
on-extra origin online file:///net/rockyroad/ex
port/builds/thurlow/fedfs/packages/i386/nightly/repo.extra/
solaris (non-sticky) origin online http://ipkg.us.oracle.co
m/solaris11/release/
opensolaris.org (non-sticky)

# pkg unset-publisher opensolaris.org

# pkg update -nv \*@latest

Many lines of:

No matching version of system/storage/removable-media can be installed:
Reject: pkg://on-nightly/system/storage/removab...@0.5.11,5.11-0.175.0.0
.0.2.18011:20111220T181640Z
Reason: Excluded by proposed incorporation 'consolidation/osnet/osnet-incorpo
ration'

And one of these:

No matching version of consolidation/osnet/osnet-incorporation can be installed:
Reject: pkg://on-nightly/consolidation/osnet/osnet-inc...@0.5.11,5.11-
0.175.0.0.0.2.18011:20111220T181524Z
Reason: Excluded by proposed incorporation 'entire'

Bart Smaalders

unread,

Dec 20, 2011, 1:58:36 PM12/20/11

to Robert Thurlow, pkg-d...@opensolaris.org

On 12/20/11 10:52, Robert Thurlow wrote:
>
>
> More generally, are there any best practices? I am trying
> to do something pretty vanilla - have a project gate that
> I and others can install from.
>
> Thanks,

In general, updating to newer bits just works. The packaging
system will following the constraints encoded in the packages;
one of those constraints is that packages that comprise a single
consolidation cannot be from mixed builds.

>
> So what would be the syntax for asking pkg to install my own
> bits, that show up marked with "0.5.11-0.175.0.0.0.2.18011"?

pkg update osnet-inc...@0.5.11-0.175.0.0.0.2.18011

will update the your OS to the specified version.

The various consolidations have incorporation packages that
specify the various version of packages that were built &
tested together; the "entire" package by default locks all
the consolidation incorporations together so that one is
running components that are all from a particular build.

Removing entire allows one to pick which version of the
consolidations are used together; note that one is still
subject to any additional dependencies specified in the
individual packages, so attempting to mix bits too far
out of sync will result in error messages.

- Bart

--
Bart Smaalders Solaris Kernel Performance
bart.sm...@oracle.com http://blogs.sun.com/barts
"You will contribute more with Mercurial than with Thunderbird."
"Civilization advances by extending the number of important
operations which we can perform without thinking about them."

Robert Thurlow

unread,

Dec 20, 2011, 3:03:45 PM12/20/11

to Bart Smaalders, pkg-d...@opensolaris.org

Bart Smaalders wrote:

>> So what would be the syntax for asking pkg to install my own
>> bits, that show up marked with "0.5.11-0.175.0.0.0.2.18011"?
>
> pkg update osnet-inc...@0.5.11-0.175.0.0.0.2.18011
>
> will update the your OS to the specified version.

OK, that bounces due to 'entire', which makes sense.

> The various consolidations have incorporation packages that
> specify the various version of packages that were built &
> tested together; the "entire" package by default locks all
> the consolidation incorporations together so that one is
> running components that are all from a particular build.
>
> Removing entire allows one to pick which version of the
> consolidations are used together; note that one is still
> subject to any additional dependencies specified in the
> individual packages, so attempting to mix bits too far
> out of sync will result in error messages.

OK:

# pkg update osnet-inc...@0.5.11-0.175.0.0.0.2.18011
Creating Plan -
pkg update: No matching version of consolidation/osnet/osnet-incorporation can b

e installed:
Reject: pkg://on-nightly/consolidation/osnet/osnet-inc...@0.5.11,5.11-
0.175.0.0.0.2.18011:20111220T181524Z

Reason: This version is excluded by installed incorporation pkg://solaris/ent
i...@0.5.11,5.11-0.175.0.0.0.2.0:20111020T143822Z

# pkg uninstall entire
Packages to remove: 1

Create boot environment: No
Create backup boot environment: No

PHASE ACTIONS
Removal Phase 64/64

PHASE ITEMS
Package State Update Phase 1/1
Package Cache Update Phase 1/1

Image State Update Phase 2/2

# pkg update osnet-inc...@0.5.11-0.175.0.0.0.2.18011

This got the attached. pkg:/system/library/boot-management looks
like the key log.

Rob T

pkg.out

Seth Goldberg

unread,

Dec 20, 2011, 3:45:02 PM12/20/11

to Robert Thurlow, pkg-d...@opensolaris.org

Hi there,

You'll need to add an install-nightly publisher, since that's where the boot-management package is (for now). Then you should be able to do your update. Note that this is because the machine you did your build on was running update 1 build 3. If you had built on an FCS system, your existing boot-management package would have satisfied that requirement.

--S

> pkg update: No solution was found to satisfy constraints
>
> maintained incorporations:
>
> pkg://solaris/consolidation/ldoms/ldoms-inc...@0.5.11,5.11-0.175.0.0.0.1.0:20111012T230609Z
> pkg://solaris/consolidation/gfx/gfx-inco...@0.5.11,5.11-0.175.0.0.0.2.0:20111019T144752Z
> pkg://solaris/consolidation/vpanels/vpanels-in...@0.5.11,5.11-0.175.0.0.0.1.778:20111012T230640Z
> pkg://solaris/consolidation/admin/admin-inc...@0.5.11,5.11-0.175.0.0.0.2.0:20111019T144751Z
> pkg://solaris/consolidation/SunVTS/SunVTS-inc...@0.5.11,5.11-0.172.0.0.0.0.0:20110816T071310Z
> pkg://solaris/consolidation/ub_javavm/ub_javavm-i...@0.5.11,5.11-0.175.0.0.0.2.0:20111019T144756Z
> pkg://solaris/consolidation/solaris_re/solaris_re-i...@0.5.11,5.11-0.175.0.0.0.2.0:20111019T122734Z
> pkg://solaris/consolidation/cacao/cacao-inc...@0.5.11,5.11-0.174.0.0.0.0.0:20110921T190516Z
> pkg://solaris/consolidation/userland/userland-in...@0.5.11,5.11-0.175.0.0.0.2.537:20111019T091357Z
> pkg://solaris/consolidation/jdmk/jdmk-inco...@0.5.11,5.11-0.173.0.0.0.0.0:20110828T210111Z
> pkg://solaris/consolidation/nvidia/nvidia-inc...@0.5.11,5.11-0.175.0.0.0.0.0:20110927T192422Z
> pkg://solaris/consolidation/dbtg/dbtg-inco...@0.5.11,5.11-0.175.0.0.0.2.0:20111019T144751Z
> pkg://solaris/consolidation/ips/ips-inco...@0.5.11,5.11-0.175.0.0.0.2.2576:20111020T063559Z
> pkg://solaris/consolidation/cde/cde-inco...@0.5.11,5.11-0.175.0.0.0.0.0:20110927T191905Z
> pkg://solaris/consolidation/man/man-inco...@0.5.11,5.11-0.175.0.0.0.0.0:20110927T192523Z
> pkg://solaris/consolidation/desktop/desktop-in...@0.5.11,5.11-0.175.0.0.0.2.0:20111019T132128Z
> pkg://solaris/consolidation/l10n/l10n-inco...@0.5.11,5.11-0.175.0.0.0.1.765:20111012T043917Z
> pkg://solaris/consolidation/X/X-incor...@0.5.11,5.11-0.175.0.0.0.0.1215:20110927T121319Z
> pkg://solaris/consolidation/sic_team/sic_team-in...@0.5.11,5.11-0.172.0.0.0.0.0:20110816T070737Z
> pkg://solaris/consolidation/java/java-inco...@0.5.11,5.11-0.173.0.0.0.0.0:20110828T210417Z
> pkg://solaris/consolidation/sunpro/sunpro-inc...@0.5.11,5.11-0.174.0.0.0.0.0:20110921T184135Z
> pkg://solaris/consolidation/cns/cns-inco...@0.5.11,5.11-0.175.0.0.0.1.0:20111012T230319Z
> pkg://solaris/consolidation/nspg/nspg-inco...@0.5.11,5.11-0.175.0.0.0.2.0:20111019T144753Z
> pkg://solaris/consolidation/install/install-in...@0.5.11,5.11-0.175.0.0.0.2.1482:20111019T122620Z
> pkg://solaris/consolidation/xvm/xvm-inco...@0.5.11,5.11-0.175.0.0.0.2.0:20111019T144757Z
> pkg://solaris/consolidation/desktop/gnome-inc...@0.5.11,5.11-0.175.0.0.0.2.0:20111019T132130Z
> pkg://solaris/consolidation/sfw/sfw-inco...@0.5.11,5.11-0.175.0.0.0.2.0:20111019T144754Z
>
> Plan Creation: dependency error(s) in proposed packages:
>
> No suitable version of required package pkg://on-nightly/consolidation/osnet/osnet-inc...@0.5.11,5.11-0.175.0.0.0.2.18011:20111220T181524Z found:
> Reject: pkg://on-nightly/consolidation/osnet/osnet-inc...@0.5.11,5.11-0.175.0.0.0.2.18011:20111220T181524Z
> Reason: All versions matching 'incorporate' dependency pkg:/service/security/kerbe...@0.5.11,5.11-0.175.0.0.0.2.18011 are rejected
> Reject: pkg://on-nightly/service/security/kerbe...@0.5.11,5.11-0.175.0.0.0.2.18011:20111220T181559Z
> Reason: All versions matching 'require' dependency pkg:/system/cor...@0.5.11,5.11-0.175.0.0.0.2.18011 are rejected
> Reject: pkg://on-nightly/system/cor...@0.5.11,5.11-0.175.0.0.0.2.18011:20111220T181603Z
> Reason: All versions matching 'require' dependency pkg:/system/boot-environm...@0.5.11,5.11-0.175.0.0.0.2.18011 are rejected
> Reject: pkg://on-nightly/system/boot-environm...@0.5.11,5.11-0.175.0.0.0.2.18011:20111220T181600Z
> Reason: A version for 'require' dependency on pkg:/system/library/boot-ma...@0.5.11,5.11-0.175.1.0.0.3.1504 cannot be found
>
> Plan Creation: Errors in installed packages due to proposed changes:
>
> No suitable version of installed package pkg://solaris/system/zones/brand/brand-...@0.5.11,5.11-0.175.0.0.0.2.1:20111019T085057Z found
> Reject: pkg://on-nightly/system/zones/brand/brand-...@0.5.11,5.11-0.175.0.0.0.2.18011:20111220T181644Z
> Reason: All versions matching 'require' dependency pkg:/system/cor...@0.5.11,5.11-0.175.0.0.0.2.18011 are rejected
> Reject: pkg://on-nightly/system/cor...@0.5.11,5.11-0.175.0.0.0.2.18011:20111220T181603Z
> Reason: All versions matching 'require' dependency pkg:/system/boot-environm...@0.5.11,5.11-0.175.0.0.0.2.18011 are rejected
> Reject: pkg://on-nightly/system/boot-environm...@0.5.11,5.11-0.175.0.0.0.2.18011:20111220T181600Z
> Reason: A version for 'require' dependency on pkg:/system/library/boot-ma...@0.5.11,5.11-0.175.1.0.0.3.1504 cannot be found
> Reject: pkg://solaris/system/zones/brand/brand-...@0.5.11,5.11-0.175.0.0.0.2.1:20111019T085057Z