# On the server, publishing a new version
root@sw-install:/opt/shutl/install/pkg/bash-config# pkgsend publish -s http://localhost:80 -d proto bash-config.p5m
PUBLISHED
pkg://shutl/config/bash-config@1.0.1,0.1:20120123T170659Z
# On teh client
root@shutl-app1:~# pkg refresh
root@shutl-app1:~# pkg list -av bash-config
FMRI IFO
pkg://shutl/config/bash-config@1.0.0,0.1:20120123T161829Z i--
pkg://shutl/shutl/config/bash-config@1.0.0,0.1:20120123T155011Z ---
# ^^ the shutl/shutl version came back
# On the server, ran a rebuild (again)
root@sw-install:~# pkgrepo -s /export/ips rebuild
Initiating repository rebuild.
# Now on the client, it's OK again
root@shutl-app1:~# pkg list -nv bash-config
FMRI IFO
pkg://shutl/config/bash-config@1.0.1,0.1:20120123T170659Z ---
# On the server, no shutl/shutl version is there:
root@sw-install:~# pkgrepo -s /export/ips list | grep bash-config
shutl config/bash-config 1.0.1,0.1:20120123T170659Z
shutl config/bash-config 1.0.0,0.1:20120123T161829Z
# Trying again
# On the server: Publishing again, a version 1.0.2 now
root@sw-install:/opt/shutl/install/pkg/bash-config# pkgsend publish -s http://localhost:80 -d proto bash-config.p5m
PUBLISHED
pkg://shutl/config/bash-config@1.0.2,0.1:20120123T172157Z
# On teh client, shutl/shutl comes back again
root@shutl-app1:~# pkg refresh
root@shutl-app1:~# pkg list -av bash-config
FMRI IFO
pkg://shutl/config/bash-config@1.0.0,0.1:20120123T161829Z i--
pkg://shutl/shutl/config/bash-config@1.0.0,0.1:20120123T155011Z ---
# -nv shows the updated 1.0.2, but still the spurious shutl/shutl
root@shutl-app1:~# pkg list -nv bash-config
FMRI IFO
pkg://shutl/config/bash-config@1.0.2,0.1:20120123T172157Z ---
pkg://shutl/shutl/config/bash-config@1.0.0,0.1:20120123T155011Z ---
# Now I'll need to rebuild again to get rid of it