Bug 282791 - sysutils/kubo-go: gid already allocated
Summary: sysutils/kubo-go: gid already allocated
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: John Hixson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-15 23:58 UTC by Calvin Buckley
Modified: 2024-11-19 17:12 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (jhixson)

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 Calvin Buckley 2024-11-15 23:58:14 UTC 
I'm upgrading from FreeBSD/amd64 14.0 to 14.1, and upgrading the binary packages on my system as a result. However, it seems kubo-go gets installed as a new dependency to something installed on my system. When pkg gets to installing this, I get to:

```
[441/506] Installing kubo-go-0.29.0_4...
===> Creating groups
Creating group 'kubo-go' with gid '883'
pw: gid `883' has already been allocated
```

The GID 883 seems allocated to ipfs-go already however. It looks like kubo-go replaces ipfs-go, looking at: https://github.com/freebsd/freebsd-ports/commit/fc2f8f7ed067de1d4b2682cb5cf8a65807d81978

Is there something I'm missing for the upgrade? It looks like bug #280346 might match my current situation, but it claims it's fixed.
Comment 1 Calvin Buckley 2024-11-19 17:12:17 UTC 
I worked around this by removing ipfs-go (it seems beets wanted it), removing the user/group with rmuser, then resuming the upgrade.