Re: build and ports mismatching ?

On Fri, May 25, 2018 at 07:51:15AM +, Stuart Henderson wrote: > That is at least detected by package tools and more easily fixed :) The package tools err on the side of caution because we've been burnt too many times. There is often whining about it from other developers because sometimes

Re: build and ports mismatching ?

On 2018-05-24, Sebastian Benoit wrote: > Base system snapshots (including xenocara) and packages are not build > at the same time. Package builds use the latest snapshot, but since > building packages takes a day or so (depending on the arcitecture and > build machines

Re: build and ports mismatching ?

Great explanation, Thanks. Elias. 2018-05-24 15:59 GMT-03:00 Sebastian Benoit : > Elias M. Mariani(marianiel...@gmail.com) on 2018.05.24 15:45:15 -0300: >> Thanks Sebastian for the reply, >> I do follow source-changes, just that I don't understand if it's >> common for a

Re: build and ports mismatching ?

Elias M. Mariani(marianiel...@gmail.com) on 2018.05.24 15:45:15 -0300: > Thanks Sebastian for the reply, > I do follow source-changes, just that I don't understand if it's > common for a library to have 2 version numbers. There is the old version number(s) and the newest one. If you check your

Re: build and ports mismatching ?

Thanks Sebastian for the reply, I do follow source-changes, just that I don't understand if it's common for a library to have 2 version numbers. Or if the ports/snapshots system is made with some inner logic to avoid this kind of conflict. I mean, the ports did not install the library, that means

Re: build and ports mismatching ?

Elias M. Mariani(marianiel...@gmail.com) on 2018.05.24 14:22:35 -0300: > Hi, > I noticed just now a couple of errors after updating from > snapshots/amd64 (22/05) and updating the packages with pkg_add -u > (24/05) indicating a mismatch in some library, I think it was > libfreetype.so.28.2 vs 29.0