Bug 185763 - ports-mgmt/pkg should fail if no category is specified for the package
Summary: ports-mgmt/pkg should fail if no category is specified for the 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-01-14 03:40 UTC by Wojciech A. Koszek
Modified: 2014-12-29 23:33 UTC (History)
1 user (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 Wojciech A. Koszek freebsd_committer freebsd_triage 2014-01-14 03:40:00 UTC 
I'm trying our FreeBSD 10-RC5.

Upon system installation my 1st step was to install Subversion, since I want to fetch the most up-to-date src/ and recompile the system.

I did:

pkg_bootstrap
pkg2ng
pkg install subversion

pkg warned me there are many conflicts. I think it's because many packages of the same type but different version were matched:

	Installing subversion: 1.7.14
	Installing subversion: 1.6.23_2

I think this is confusing for new FreeBSD. We could either offer a help, or just fail (exit unless / is present in the package name) and have users Google the answer.

How-To-Repeat: pkg install subversion
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2014-01-14 20:28:34 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-ports-bugs

ports PR.
Comment 2 Edwin Groothuis freebsd_committer freebsd_triage 2014-01-14 20:28:56 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->portmgr

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 3 Baptiste Daroussin freebsd_committer freebsd_triage 2014-12-29 23:33:22 UTC 
This has been fixed by fixing the unicity of package names