Errors building mysql55-client

[bw.mail.lists]

I get these in poudriere:

====>> [01] Starting build of databases/mysql56-client
====>> [01] Finished build of databases/mysql56-client: Failed: checksum
====>> [01] Skipping build of databases/mysql56-server: Dependent port 
databases/mysql56-client failed
====>> Stopping 2 builders
====>> No package built, no need to update the repository
====>> Cleaning up
====>> Umounting file systems
====>> Failed ports: databases/mysql56-client:checksum

====>> Skipped ports: databases/mysql56-server

====>> [] 0 packages built, 1 failures, 0 ignored, 1 skipped


This is mysql56, but I think it's related. As far as I know upstream 
changed the package because of man pages license issues. Didn't look 
into it any further, using mariadb mainly.

On 7/8/2013 10:57 PM, Dave Hayes wrote:
> On 06/27/13 03:13, C. L. Martinez wrote:
>> On Thu, Jun 27, 2013 at 9:21 AM, Trond Endrestøl
>> <Trond.Endrestol at fagskolen.gjovik.no> wrote:
>>> On Thu, 27 Jun 2013 07:55-0000, C. L. Martinez wrote:
>>> Either the file named distinfo is messed up, or the maintainer has
>>> access to a different file than the rest of us. Maybe you should wait
>>> until the MySQL mirrors catches up.
>
> I'm going to confirm that this was a recent patch to the ports tree:
>
> http://svnweb.freebsd.org/ports/head/databases/mysql55-server/distinfo?r1=320671&r2=321789
>
>
> It's pretty clear the versions the port is trying to download -used- to
> match the distinfo file, but they no longer do. This cryptic comment:
>
>    Distfile rerolled to make it clearer the license of this
>    community edition (GPLv2).
>
> seems to be the source of these errors which are biting me too.
>
> It would be nice for some clearer documentation on why distinfo was
> changed, what the real issue is, and what we can do to build this
> "correctly". Naively speaking, the version available for download off
> the mysql site matches the old distinfo SHA checksum so I'm not sure why
> this was changed at all.
>
> I've CC'd the ports list and the responsible committer on this. I'll
> file a PR too if I get no response to this message. :)