Bug 194666 - ports-mgmt/pkg: pkg version lists ports needing an update but update has been applied via pkg
Summary: ports-mgmt/pkg: pkg version lists ports needing an update but update has been...
Status: Closed Not Enough Information
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-pkg (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-28 17:17 UTC by crum.zach
Modified: 2015-04-15 19:23 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description crum.zach 2014-10-28 17:17:49 UTC
The following have been updated to the latest but pkg indicates they are older versions than the current version

pkg check does not remedy the situation.

dri-9.1.7_6,2                      <
libEGL-9.1.7_4                     <
libGL-9.1.7_3                      <
libglapi-9.1.7_2                   <
libglesv2-9.1.7_3                  <

I have also deleted the packages using pkg delete and re-installed them. 

I am building all packages from ports.
Comment 1 John Marino freebsd_committer freebsd_triage 2014-10-31 09:23:30 UTC
This is a new xorg / old xorg issue.

Depending on the value/definition of WITH_NEW_XORG, a different version is produced.  For official repos, that's going to be a specific version and your setup may require the other.

IMO, this PR is invalid --- it's just a misunderstanding of what you are seeing.

CC'ing pkg@
Comment 2 crum.zach 2014-11-02 01:06:48 UTC
WITH_NEW_XORG has been defined since I installed 10.0. 

I understand that pkg is supposed to tell me when ports are out-of-date/stale. In this case, they are the same version.

For example
 pkg version indicates libEGL "libEGL-9.1.7_4   <"

However, when looking at freshports.org, the current version is 9.1.7_4

If I understand it correctly, pkg version should output "libEGL-9.1.7_4    ="

I will happily go away, but I'll continue to scratch my head as to why the version is being marked as stale, when it's the current version.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2014-11-02 01:10:10 UTC
Over to maintainers.
Comment 4 crum.zach 2014-11-09 03:06:31 UTC
chromium-38.0.2125.111 now exhibits the same behavior. It is listed as needing updated, but it is up to date.
Comment 5 Baptiste Daroussin freebsd_committer freebsd_triage 2014-12-29 23:26:56 UTC
Sorry I do not understand the issue

Can you give more details about your setup?
Comment 6 crum.zach 2015-04-15 19:23:16 UTC
Way back when, after a PKG update, ports were being updated but the database was displaying the wrong version info.

I never heard back from anyone as to how to investigate further, and have since wiped my workstation and started fresh. :) That fixed it, The Microsoft way.