Bug 262764 - After DVD1 13.0-R install with ports tree, portsnap auto doesn't remove old directories for renamed ports
Summary: After DVD1 13.0-R install with ports tree, portsnap auto doesn't remove old d...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 13.0-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-24 19:59 UTC by Pau Amma
Modified: 2022-03-28 16:27 UTC (History)
1 user (show)

See Also:
pauamma: maintainer-feedback?
pauamma: mfc-stable13?
pauamma: mfc-stable12?

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 Pau Amma 2022-03-24 19:59:41 UTC 
Suspected in an IRC troubleshooting session, verified experimentally.
On a fresh install from amd64 13.0-R DVD1 with ports tree:
ls -ld /usr/ports/x11/gnome* # shows gnome3 with Apr 9, 2021 timestamp
portsnap auto
ls -ld /usr/ports/x11/gnome* # shows gnome3 with Apr 9, 2021 timestamp and gnome with Mar 24, 2022 timestamp.
Comment 1 Pau Amma 2022-03-24 20:16:01 UTC 
Forgot to say:

IMO, portsnap should balk (maybe with suggestion to rm -rf /usr/ports) if it finds a not-empty /usr/ports on first run, for POLAness. If someone rules "working as designed", then it needs to be documented, because trap for the unwary.