#917 closed defect (worksforme)

Netatalk fails to build in trunk (build 8297)

Reported by: JoeSchmuck Owned by: delphij
Priority: major Milestone:
Component: Backend Version: 8.0.1-RELEASE
Keywords: Cc:

Description

While attempting another build of the trunk I ran into netatalk build failure. I will attach the log file. Might be related to the 8196 change where many directories were changed.

This of course stop the rest of the build process.

Attachments (1)

netatalk.zip (41.3 KB) - added by JoeSchmuck 19 months ago.
Error Log

Download all attachments as: .zip

Change History (12)

Changed 19 months ago by JoeSchmuck

Error Log

comment:1 Changed 19 months ago by gcooper

Nope.. the netatalk 2.2.1 patch update broke my WITHOUT_APPLETALK fixes because it's broken upstream.

r8196 has absolutely nothing to do with this breakage.

Last edited 19 months ago by gcooper (previous) (diff)

comment:2 Changed 19 months ago by JoeSchmuck

Not sure what you mean by upstream, when I assume things I get it all wrong. So long as it gets rectified eventually.

comment:3 Changed 19 months ago by gcooper

------------------------------------------------------------------------
r8176 | yaberauneya | 2011-10-07 01:22:34 -0700 (Fri, 07 Oct 2011) | 4 lines

Fix net/netatalk compilation from scratch with -DWITHOUT_APPLETALK specified.

Part of the fix is derived from PR 160181. The pkg-plist portion will need to be contributed back upstream after adjusting it for 2.2.1.

I'll get to this as soon as I can (probably in 1-2 days). For now just revert the last change like so and restart your build:

svn merge -c -8196 patches/ports-netatalk.patch

(and yes, I was being dyslexic.. r8196 did cause this breakage).

Last edited 19 months ago by gcooper (previous) (diff)

comment:4 Changed 19 months ago by delphij

  • Owner set to delphij
  • Status changed from new to accepted

I'm working on this.

comment:5 Changed 19 months ago by delphij

  • Resolution set to fixed
  • Status changed from accepted to closed

Fixed as r8263 and filed a ports PR to FreeBSD maintainer.

comment:7 Changed 19 months ago by JoeSchmuck

  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Summary changed from Netatalk fails to build in trunk (build 8247) to Netatalk fails to build in trunk (build 8297)

The same problem is back, well probably. I tried to build twice today, both failed at the same point.

comment:8 Changed 19 months ago by gcooper

Nuke the patch, svn up the patches/, and things will potentially be more sane.

comment:9 Changed 19 months ago by gcooper

Sorry. My previous directions were incomplete:

  1. You'll need to go back to the previous patch version (r8262):

svn merge -c -8263 patches/ports-netatalk.patch

  1. Revert the patch:

{{{ (cd FreeBSD/ports/ && sudo patch -p0) < patches/ports-netatalk.patch

  1. svn up the new patch:

svn revert patches/ports-netatalk.patch

  1. Remove the reference to the patch in the patches file:

sudo sed -i '' '/netatalk/d' FreeBSD/ports-patches

  1. Rerun the build.

sudo sh build/do_build.sh

You could arguably replace steps 1.-4. with "nuke your FreeBSD / obj.* directories and skip to step 5.", but that takes longer because it will need to repull and repatch everything. The above directions will work (I've had to employ them when testing out changes to patches before), minus the case where it adds new files via the patch.

That's why the devs at iX use ZFS snapshot / rollback of the FreeBSD directories extensively. I was trying to push unionfs style mounts for storing all modifications to the src and ports trees because it would work in all cases, instead of just with ZFS, but there are issues with that method (it causes ZFS / unionfs fs deadlocks).

Last edited 19 months ago by gcooper (previous) (diff)

comment:10 Changed 19 months ago by JoeSchmuck

I blew it all away (reset VM snapshot to virgin setting) and tried to build again, downloading everything again, this time it crashed at creating Install World. I've reset the VM again and will try one more time. That was r8299. Now it's going to be 8301 but I'm not holding my breath. I'll check the build in the morning, if it crashed again at the same spot I'll drop a new ticket and close this one.

comment:11 Changed 18 months ago by JoeSchmuck

  • Resolution set to worksforme
  • Status changed from reopened to closed

Not sure when or where it got fixed but I do not have the problem any longer.

Note: See TracTickets for help on using tickets.