Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#53436 closed defect (fixed)

port reclaim reports .turd_MacPorts file as unnused distfile

Reported by: neverpanic (Clemens Lang) Owned by: neverpanic (Clemens Lang)
Priority: Low Milestone: MacPorts 2.4.1
Component: base Version: 2.4.0
Keywords: Cc: jmroot (Joshua Root)
Port:

Description

MacPorts .pkg installers are created using port pkg MacPorts from the MacPorts port. MacPorts strips empty directories before packaging after destroot. We specify destroot.keepdirs in the MacPorts port to avoid this, but this directive creates .turd_MacPorts files to make these directories non-empty.

This also happens for $prefix/var/macports/distfiles, which is now scanned by port reclaim when run. port reclaim does not know about the .turd_MacPorts file, considers it to be an unused distfile and suggests deleting it. While not a problem per-se, this is unexpected for users.

Change History (5)

comment:1 Changed 8 years ago by neverpanic (Clemens Lang)

Owner: set to neverpanic
Resolution: fixed
Status: newclosed

In b0c0957/macports-base:

reclaim: Ignore .turd_MacPorts files

Ignore .turd_MacPorts files in reclaim to avoid confusing users when
reclaim claims the file is an unused distfile even though it was put
there by the MacPorts installer.

Closes: #53436

comment:2 Changed 8 years ago by neverpanic (Clemens Lang)

In 8ee43f7/macports-base:

reclaim tests: Remove constraints, add turd test

Remove interactivity and root constraints from reclaim test by mocking
everything that would require these constraints.

Add a test to verify that .turd_MacPorts files are kept by reclaim.

See: #53436

comment:3 Changed 8 years ago by neverpanic (Clemens Lang)

Second commit is the backport to release-2.4.

comment:4 Changed 8 years ago by jmroot (Joshua Root)

Milestone: MacPorts FutureMacPorts 2.4.1

comment:5 Changed 8 years ago by Clemens Lang <neverpanic@…>

In 8f8bead/macports-base:

Changelog: Add b0c0957

Add a changelog entry for a bug fixed in reclaim.

See: #53436

Note: See TracTickets for help on using tickets.