Project

General

Profile

Bug #6511

Many packages are renamed to non-existing versions

Added by Gary Mills almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
2015-12-14
Due date:
% Done:

0%

Estimated time:
Difficulty:
Bite-size
Tags:
needs-triage
Gerrit CR:

Description

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:/driver/storage/aac@0.5.11,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:/driver/storage/aac@0.5.11,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.


Files

mf.names (4.15 KB) mf.names Gary Mills, 2015-12-14 03:56 PM
#1

Updated by Alexander Pyhalov almost 5 years ago

I see it in the following way:
pkg:/driver/storage/aac@$(PKGVERS) satisfies the dependency when PKGVERS>=0.5.11,5.11-0.133. SUNWaac doesn't need to be updated on every PKGVERS update. So I don't think it's an issue.

#2

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/SUNWapch22m-php52@5.2.12,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.

#3

Updated by Igor Kozhukhov over 4 years ago

  • Status changed from New to Closed

closed by request from owner
"In that case, there's no problem. Somebody who has the authority
should close the bug report. I'll abandon the webrev."

Also available in: Atom PDF