Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#24604 closed update (fixed)

syck 0.70 changes to point to current canonical syck library

Reported by: apinstein@… Owned by: lharple@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: adamdoupe@…, anddam (Andrea D'Amore)
Port: syck

Description

Since why bailed on syck it looks like it's been taken over by this guy:

http://github.com/indeyets/syck

See: http://lists.freebsd.org/pipermail/freebsd-ports/2009-September/057243.html

The 0.55 port won't build on 10.6/64-bit. We were able to easily update the portfile to use the 0.70 release from indeyets' site.

Just update master_sites to http://github.com/indeyets/syck/downloads and update the checksum desired for this file: http://github.com/downloads/indeyets/syck/syck-0.70.tar.gz

Update the port's version to 0.70 and everything compiled great and worked for us.

I don't know of any better way to "confirm" that this is the official new home for syck.

Attachments (2)

syck_version_70.patch (1.0 KB) - added by adamdoupe@… 10 years ago.
Patch to upgrade portfile to version .70
v0.70 failed build.log (4.0 KB) - added by anddam (Andrea D'Amore) 10 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 11 years ago by jmroot (Joshua Root)

Owner: changed from macports-tickets@… to lharple@…
Port: syck added
Version: 1.8.2

Please remember to fill in the Port field and cc the maintainer.

comment:2 Changed 10 years ago by drew@…

I'll second the request for the syck port to be updated to 0.70.

The new home for syck does appear to be on GitHub: http://github.com/indeyets/syck

Changed 10 years ago by adamdoupe@…

Attachment: syck_version_70.patch added

Patch to upgrade portfile to version .70

comment:3 Changed 10 years ago by adamdoupe@…

Cc: adamdoupe@… added

Cc Me!

comment:4 Changed 10 years ago by apinstein@…

gah... I just upgraded another box to 10.6 and had this issue (which I reported 10 months ago) and it still isn't fixed in Macports! And subsequently just wasted another 2 hours of my life re-finding this bug.

What is the process for taking over ownership of the syck portfile so that I can commit the patch?

comment:5 Changed 10 years ago by jmroot (Joshua Root)

The procedure to follow for abandoned ports is laid out in the Guide. But in this case it's only been 35 minutes since a patch was provided…

comment:6 in reply to:  3 Changed 10 years ago by anddam (Andrea D'Amore)

Replying to adamdoupe@…:

Don't diff the $Id$ line too when creating patch file.

The patch isn't building on my system, I'm attaching output and will check into it later.

Changed 10 years ago by anddam (Andrea D'Amore)

Attachment: v0.70 failed build.log added

comment:7 Changed 10 years ago by anddam (Andrea D'Amore)

Cc: and.damore@… added

Cc Me!

comment:8 Changed 10 years ago by anddam (Andrea D'Amore)

Resolution: fixed
Status: newclosed

Seems the build error was due to parallel build, I disabled it and committed the patch in r76528.

comment:9 Changed 10 years ago by apinstein@…

Excellent, thanks!

Note: See TracTickets for help on using tickets.