Well, it's been broken for up to 2 months (since we switched to git & the
PPAs consequently stopped warning us about build failures).
Perhaps Michael can advise on how long the problem has existed.
AV
On 10 August 2017 at 17:35, Ryan Gorley <ryan@...3592...> wrote:
Not exciting, unless someone tried to install on Trusty or Debian 8
and
failing in the past...? Your call because I don't know how widespread the
issue was.
On 08/10/2017 10:30 AM, Alex Valavanis wrote:
I'm not sure it's the most exciting news! I imagine the people who are
interested in trunk builds on LTS systems are already getting their
Inkscape news on this list.
AV
On 10 August 2017 at 17:28, Ryan Gorley <ryan@...3592...> wrote:
> Is this something we should proactively push out to social media?
>
> On 08/10/2017 10:06 AM, Alex Valavanis wrote:
>
> Hi All,
>
> Ubuntu Trusty builds are now fixed in the trunk PPA. I hope this will
> also have fixed Debian 8 builds... please let me know if not.
>
> We can now pay attention to the PPA build logs so we avoid build failures
> on older systems :)
>
>
> AV
>
> On 24 July 2017 at 22:38, Bryce Harrington <bryce@...961...>
> wrote:
>
>> On Mon, Jul 24, 2017 at 03:02:11PM +0100, Alex Valavanis wrote:
>> > Hi All,
>> >
>> > I've brought the trunk PPA back online... it's currently failing on
the
>> > "make test" step:
>> >
>> >
https://launchpadlibrarian.net/330394206/buildlog_ubuntu-xen
>> ial-amd64.inkscape-trunk_1%3A0.92.0+devel+15937+86~ubuntu16.
>> 04.1_BUILDING.txt.gz
>>
<
https://launchpadlibrarian.net/330394206/buildlog_ubuntu-xenial-amd64.ink...
>> >
>> > As an interim measure, I've disabled the test rule in the PPA builder
>> until
>> > someone figures out how to fix it!
>>
>> Thanks for converting the PPAs, Alex!
>>
>> Bryce
>>
>> > AV
>> >
>> > On 24 July 2017 at 12:05, Alex Valavanis <valavanisalex@...400...>
>> wrote:
>> >
>> > > Just another +1 for handling this all through CI. It will place an
>> > > impossible burden on developers if we need to manually rebuild
>> everything
>> > > on a list of "supported" build systems before committing to
trunk.
>> > >
>> > > The PPA builds are currently out of date because we don't yet have
an
>> > > "official" mirror of the git repo on Launchpad. It's not
too tricky
>> to set
>> > > up though, and we can switch to using git-builder when it's
>> available.
>> > >
>> > >
>> > > AV
>> > >
>> > > On 24 July 2017 at 11:59, Alex Valavanis
<valavanisalex@...400...>
>> wrote:
>> > >
>> > >> I've re-added the listing for Debian oldstable to our
"Tracking
>> > >> Dependencies" page...
http://wiki.inkscape.org/wiki/
>> > >> index.php/Tracking_Dependencies#Distros
>> > >>
>> > >> On 24 July 2017 at 10:01, Tobias Ellinghaus <houz@...173...>
wrote:
>> > >>
>> > >>> Am Sonntag, 23. Juli 2017, 23:22:46 CEST schrieb Michael
Soegtrop
>> via
>> > >>> Inkscape-devel:
>> > >>> > Dear Eduard, dear Inkscape Team
>> > >>> >
>> > >>> > > If this version matches the actual requirement
unexpected build
>> > >>> failures
>> > >>> > > like Michael was experiencing should be impossible as
cmake
>> would
>> > >>> > > already warn at the configure stage.
>> > >>> >
>> > >>> > I would think that CMake allows newer versions than the
>> specified one,
>> > >>> > unless explicitly told otherwise. The issue here is that
some
>> GTK 3.16
>> > >>> > are actually used although only GTK 3.8 features should be
used
>> (as far
>> > >>> > as I understood).
>> > >>>
>> > >>> While I tend to believe that users of ages old stale^Wstable
>> > >>> distributions
>> > >>> shouldn't expect bleeding edge development versions of
programs to
>> work
>> > >>> on
>> > >>> their systems I'd still like to help with at least the
glib/gtk
>> part:
>> > >>>
>> > >>> Read [0] and [1], then add the defines to CMakeLists.txt to
have
>> them
>> > >>> set for
>> > >>> all files. Also make sure that the compiler warns about
deprecated
>> > >>> functions.
>> > >>> That will bring you half way there. Once the code base
compiles
>> without
>> > >>> compiler warnings you can enable -Werror for development
builds
>> (i.e.,
>> > >>> when
>> > >>> there is a .git folder) and you will be sure to stay
compatible
>> with
>> > >>> those
>> > >>> libraries.
>> > >>>
>> > >>> The rest can be done with CI, or just crowd source it and wait
for
>> people
>> > >>> complaining when builds fail. :-)
>> > >>>
>> > >>> [...]
>> > >>>
>> > >>> > Best regards,
>> > >>> >
>> > >>> > Michael
>> > >>>
>> > >>> Tobias
>> > >>>
>> > >>>
>> > >>> [0]
https://developer.gnome.org/glib/stable/glib-Version-Informa
>> > >>> tion.html#GLIB-VERSION-MAX-ALLOWED:CAPS
>> > >>> [1]
https://developer.gnome.org/gdk3/stable/gdk3-General.html#GD
>> > >>> K-VERSION-MAX-ALLOWED:CAPS
>> > >>> ------------------------------------------------------------
>> > >>> ------------------
>> > >>> Check out the vibrant tech community on one of the world's
most
>> > >>> engaging tech sites,
Slashdot.org!
http://sdm.link/slashdot
>> > >>> _______________________________________________
>> > >>> Inkscape-devel mailing list
>> > >>> Inkscape-devel(a)lists.sourceforge.net
>> > >>>
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>> > >>>
>> > >>>
>> > >>
>> > >
>>
>> > ------------------------------------------------------------
>> ------------------
>> > Check out the vibrant tech community on one of the world's most
>> > engaging tech sites,
Slashdot.org!
http://sdm.link/slashdot
>>
>> > _______________________________________________
>> > Inkscape-devel mailing list
>> > Inkscape-devel(a)lists.sourceforge.net
>> >
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites,
Slashdot.org!
http://sdm.link/slashdot
>
>
>
> _______________________________________________
> Inkscape-devel mailing
listInkscape-devel@...1901...://lists.sourceforge.net/lists/listinfo/inkscape-devel
>
>
>