Subversion

[rupert THURNER]

I m sorry for this. What would be the best strategy to avoid a change in
the recipe when doing a patch level upgrade?  I d be glad if this could be
done by just changing the version number and maybe the names of referenced
dependencies.

Rupert
On Jan 15, 2015 3:26 PM, "Dagobert Michelsen" <dam at opencsw.org> wrote:

> Hi Rupert,
>
> in your subversion update several things are broken. I noticed you bumped
> the
> version and silenced checkpkg:
>
> https://buildfarm.opencsw.org/source/diff/opencsw/csw/mgar/pkg/subversion/trunk/Makefile?r2=%2Fopencsw%2Fcsw%2Fmgar%2Fpkg%2Fsubversion%2Ftrunk%2FMakefile%4024518&r1=%2Fopencsw%2Fcsw%2Fmgar%2Fpkg%2Fsubversion%2Ftrunk%2FMakefile%4023460
>
> This is unfortunate as the checkpkg errors would have lead you to the
> issue.
> Properly updating subversion is difficult, after investigating for the
> last two
> days these are the prerequisites I have identified:
>
> - location of the subversion config changed back from
> /opt/csw/etc/subversion to
>   /etc/subversion leading to the buildfarm config to be not pulled in.
> - libtool needs to be updated to honour gcc 4.9.x tags
> - this will probably help in allowing cc/gcc mixture of subversion and the
>   foreign function apis
> - python module needs to be modulated for 2.6/2.7/3.x
>
> So, please, do not just override the checkpkg errors without investigation
> or
> we will have broken packages.
>
>
> Thanks
>
>   — Dago
>
> --
> "You don't become great by trying to be great, you become great by wanting
> to do something,
> and then doing it so hard that you become great in the process." - xkcd
> #896
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20150115/ca923eb8/attachment-0001.html>