Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Jun 2015 16:24:05 +0000
From:      bugzilla-noreply@freebsd.org
To:        pkg@FreeBSD.org
Subject:   [Bug 198900] ports-mgmt/pkg: pkg version show status '?' when using multiple repos
Message-ID:  <bug-198900-32340-fhce5BfyBh@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198900-32340@https.bugs.freebsd.org/bugzilla/>
References:  <bug-198900-32340@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198900

--- Comment #1 from elofu17@hotmail.com ---
Doh. I found the problem.
INDEXDIR is not set, therefore PORTSDIR is searched instead, and PORTSDIR
defaults to /usr/ports if unset, which it is.
However, on this machine, someone has installed /usr/ports, so the local index
was actually there, messing with the results when I assumed both INDEXDIR and
PORTSDIR would fail, defaulting to Remote repository mode like on all other
boxes.



Hwever, I still have a bug to report:

On another machine I get a '?' even though the port is available.
It is configured to only use my repo. Not ports.

# ls -l /usr/ports/
total 0

# pkg version | grep '?'
rubygem-ruby-augeas-0.5.0_2        ?

# pkg version -R | grep '?'
rubygem-ruby-augeas-0.5.0_2        ?

# pkg version -Rr sentor | grep '?'
rubygem-ruby-augeas-0.5.0_2        ?

So in all tests I get a '?' indicating that the port is missing in the repo.

But if I explicitly search for it, it exists in my repo:
# pkg search -r sentor rubygem-ruby-augeas-0.5.0_2
rubygem-ruby-augeas-0.5.0_2


Can the problem be the unusual port name?
It contains two dashes within the port name before the third and last dash that
separates the name from the version number. Also, the version has an odd "0_2"
value.
Could it be a faulty regexp that make the comparison fail, and the port is
tagged as nonexistent in the repo?

/Elof

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198900-32340-fhce5BfyBh>