Bug 186827 - ports-mgmt/pkg pkg-repo(8) includes only oldest version of package
Summary: ports-mgmt/pkg pkg-repo(8) includes only oldest version of package
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-pkg (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-17 02:50 UTC by John Marshall
Modified: 2018-01-11 18:14 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Marshall 2014-02-17 02:50:00 UTC 
pkg-repo(8) states:

     Symbolic links are ignored, and only the most recent package for
     each origin is included in the catalogue.

Every time I have created a repository, I have discovered that only the
oldest version of each package is included in the catalogue.

Fix: 

Workaround is to remove older versions of packages from the packages
directory, so that only the latest version of each package is present
prior to creating the repository.
How-To-Repeat: 
 - Start with empty packages directory
 - build ports and create packages
 - update ports tree
 - build ports and create packages for updated ports
 - Create repository catalogue with pkg-repo(8)
 - Query catalogue for one of the updated ports and note old version
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2014-02-17 02:50:08 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->portmgr

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Bryan Drewery freebsd_committer freebsd_triage 2014-02-17 17:31:45 UTC 
Issue is logged here https://github.com/freebsd/pkg/issues/723
Comment 3 Walter Schwarzenfeld freebsd_triage 2018-01-11 17:47:37 UTC 
Works now without problems. I  think this could be closed.
Comment 4 Baptiste Daroussin freebsd_committer freebsd_triage 2018-01-11 17:49:19 UTC 
the specific part of this ticket is fixed yet, the generic issue is not cf the github issue, but that is fine enough to close that one yes