Opened 6 years ago

Closed 6 years ago

#55437 closed defect (fixed)

kdepimlibs4-kioslaves @4.14.3: reinplace didn't change anything

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: NicosPavlov
Priority: Normal Milestone:
Component: ports Version: 2.4.2
Keywords: Cc:
Port: kdepimlibs4-kioslaves

Description

A reinplace in kdepimlibs4-kioslaves doesn't do anything:

--->  Fetching archive for kdepimlibs4-kioslaves
--->  Attempting to fetch kdepimlibs4-kioslaves-4.14.3_12.darwin_16.x86_64.tbz2 from https://packages.macports.org/kdepimlibs4-kioslaves
--->  Fetching distfiles for kdepimlibs4-kioslaves
--->  Verifying checksums for kdepimlibs4-kioslaves
--->  Extracting kdepimlibs4-kioslaves
--->  Applying patches to kdepimlibs4-kioslaves
--->  Configuring kdepimlibs4-kioslaves
Warning: reinplace s|%PREFIX%|/opt/local|g didn't change anything in /opt/local/var/macports/build/_Users_rschmidt_macports_macports-ports-svn-trunk_kde_kdepimlibs4/kdepimlibs4-kioslaves/work/kdepimlibs-4.14.3/gpgme++/CMakeLists.txt
--->  Building kdepimlibs4-kioslaves
--->  Staging kdepimlibs4-kioslaves into destroot
--->  Installing kdepimlibs4-kioslaves @4.14.3_12
--->  Activating kdepimlibs4-kioslaves @4.14.3_12
--->  Cleaning kdepimlibs4-kioslaves

You'll need to decide whether the reinplace needs to be adjusted or removed.

I note kdepimlibs4-kioslaves is a subport of kdepimlibs4 and the reinplace is done for both. So you may need to look into whether the reinplace needs to be handled differently in each of those two (sub)ports.

Change History (2)

comment:1 Changed 6 years ago by NicosPavlov

You are right, the reinplace is a remnant from previous operations that can be suppressed.

comment:2 Changed 6 years ago by NicosPavlov

Resolution: fixed
Status: newclosed

In 7584cecbc5eca95395dd0cb6ff01e2e1e2c8c8c7/macports-ports (master):

kdepimlibs4: Remove useless reinplace from previous operations (fixes #55437)

Note: See TracTickets for help on using tickets.