Many packages are renamed to non-existing versions
Hundreds of packages are incorrectly renamed. For example, the manifest SUNWaac.mf contains these lines:
set name=pkg.fmri value=pkg:/SUNWaac@0.5.11,5.11-0.133 set name=pkg.renamed value=true set name=variant.arch value=$(ARCH) depend fmri=pkg:/email@example.com,5.11-0.133 type=require
but the manifest driver-storage-aac.mf has its version determined by a variable:
set name=pkg.fmri value=pkg:/driver/storage/aac@$(PKGVERS) set name=pkg.description \ value="Adaptec AdvanceRaid Controller SCSI HBA Driver" set name=pkg.summary value="Adaptec AdvanceRaid Controller SCSI HBA Driver" set name=info.classification value=org.opensolaris.category.2008:Drivers/Ports set name=variant.arch value=$(ARCH)
Note that these packages are both part of illumos, describing code that's exported from illumos. The renamed parent should refer directly to its child. The solution to make the versions specified in the parent and child always match is this change:
< depend fmri=pkg:/firstname.lastname@example.org,5.11-0.133 type=require --- > depend fmri=pkg:/driver/storage/aac@$(PKGVERS) type=require
I'm attaching the file /tmp/mf.names, which lists all the manifests that need this change.
Updated by Gary Mills almost 5 years ago
Here's the sort of error I was getting from running `pkg update -n -vvv osnet-incorporation@...':
Reject: pkg://openindiana.org/SUNW0on@0.5.11,5.11-0.133:20131206T170741Z pkg://openindiana.org/SUNW1394@0.5.11,5.11-0.133:20131206T170744Z pkg://openindiana.org/SUNW1394h@0.5.11,5.11-0.133:20131206T170748Z pkg://openindiana.org/SUNWaac@0.5.11,5.11-0.133:20131206T170751Z pkg://openindiana.org/SUNWacc@0.5.11,5.11-0.133:20131206T170755Z pkg://openindiana.org/SUNWafe@0.5.11,5.11-0.133:20131206T170758Z pkg://openindiana.org/SUNWapch22memail@example.com,5.11-0.133:20131206T055729Z pkg://openindiana.org/SUNWapct@0.5.11,5.11-0.133:20131206T170802Z Reason: Higher ranked publisher on-nightly was selected
Putting a variable as the version number eliminated that sort of error. Surely the renamed child package should be in the same repository as its parent. That seems reasonable to me.