updating alpine port to new version (as a maintainer)

Kurt Jaeger lists at opsec.eu
Sat Jan 17 18:25:24 UTC 2015


> > # then I check the build and stuff on my test system (10.1-amd64)
> > rm -rf work && make check-plist
> > [ some iterations later ]
> When I do the make check-plist I get an error:
> ===>  License APACHE20 accepted by the user
> ===>  Found saved configuration for alpine-2.11_2
> ===>   alpine-2.20 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by alpine-2.20 for building
> ===>  Extracting for alpine-2.20
> => SHA256 Checksum OK for alpine-2.20/alpine-2.20.tar.xz.
> => SHA256 Checksum OK for alpine-2.20/maildir.patch.gz.
> ===>  Patching for alpine-2.20
> ===>  Applying distribution patches for alpine-2.20
> ===>  Applying FreeBSD patches for alpine-2.20
> Ignoring previously applied (or reversed) patch.
> 2 out of 2 hunks ignored--saving rejects to ./alpine/alpine.c.rej
> => Patch patch-alpine__alpine.c failed to apply cleanly.

The patch files/patch-alpine__alpine.c no longer applies to the new
version of the code.

> Any ideas how to go from here?

I normally proceed by moving all non-applying patches into a seperate
directory and try if the build works:

cd ~/myp/mail/alpine
mkdir OLD
mv files/patch-alpine__alpine.c OLD/

# and retry
rm -rf work && make check-plist

If the patch is required (but different), one has to dig into the
code and find out what needs to change for the code to build.

pi at opsec.eu            +49 171 3101372                         5 years to go !

More information about the freebsd-ports mailing list