11:22 p.m.
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).
I have some experience with creating build systems which use specific
package versions based on Cygwin. Since there is a working MSys build,
it shouldn't be difficult to build with specific package versions - one
just has to create a local cygwin or MSys package repository, which
keeps these specific versions and tell the Cygwin/MSys installer to use
that one. The Cygwin installer creates a suitable repository as a cache
automatically. Not sure how this works with MSys, but I guess it has
similar features. The main issue here might be to get the versions
mentioned in the Wiki. One might have to build them from scratch.
If someone has a years old cache folder of Cygwin or MSys with all the
old package versions, please put is somewhere.
It would make sense to run two builds, one with the latest packages and
one with an archived set of packages.
Best regards,
Michael
.
12:21 a.m.
Am 23.07.2017 um 23:22 schrieb Michael Soegtrop via Inkscape-devel:
I have some experience with creating build systems which use
specific
package versions based on Cygwin. Since there is a working MSys build,
it shouldn't be difficult to build with specific package versions - one
just has to create a local cygwin or MSys package repository, which
keeps these specific versions and tell the Cygwin/MSys installer to use
that one. The Cygwin installer creates a suitable repository as a cache
automatically. Not sure how this works with MSys, but I guess it has
similar features. The main issue here might be to get the versions
mentioned in the Wiki. One might have to build them from scratch.
If someone has a years old cache folder of Cygwin or MSys with all the
old package versions, please put is somewhere.
It would make sense to run two builds, one with the latest packages and
one with an archived set of packages.
Best regards,
Michael
(just for clarification: we're using MSYS2, not MSYS! Also we're
creating native builds based on mingw-w64, not Cygwin builds)
While I agree on the idea of having CI with packages using the minimal
version numbers it does not make that much sense to uses MSYS2 as a base
as it's designed to be rolling release and constantly develops. Creating
our own package repository sounds like a lot of unncessary work,
especially as I doubt a "years old cache" of MSYS2 would be able to
build Inkscape at this stage (as a matter of fact I added some packages
myself and fixed some bugs in others along the way).
I assume it'd be much easier to decide on some old but widespread Linux
distro an base CI on that.
Regards,
Eduard
9:09 a.m.
Dear Eduard,
I assume it'd be much easier to decide on some old but widespread
Linux distro an base CI on that.
I think it will be difficult to keep such a CI system sane and safe. It
is much less of a fuzz to to builds on a years old Cygwin on a modern
Windows than to maintain a CI server with a years old Linux. The idea of
using repo caches is to archive the state in which things did work once.
The point is to maintain compatibility with such a build environment.
With Cygwin this is very low effort - just backup the local repo cache
and tell the installer to not update the cached version. That's all. You
can setup any number of cygwins from different repo caches with a script
on one Windows machine. I don't know much about MSys2, but I guess it
would be similar.
Best regards,
Michael
11:01 a.m.
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-Information.html#GLI...
[1]
https://developer.gnome.org/gdk3/stable/gdk3-General.html#GDK-VERSION-MAX...
12:59 p.m.
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-
Information.html#GLIB-VERSION-MAX-ALLOWED:CAPS
[1] https://developer.gnome.org/gdk3/stable/gdk3-General.html#
GDK-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
1:05 p.m.
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
>
>
4:02 p.m.
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-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!
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
>>
>>
>
4:16 p.m.
Am 24.07.2017 um 16:02 schrieb Alex Valavanis:
I've brought the trunk PPA back online... it's currently
failing on
the "make test" step:
That's because the build is configured to do "make test" which only runs
tests but does not build them.
If you replace it with "make check" we should be all set!
Thanks for bringing this back online!
Regards,
Eduard
4:22 p.m.
OK great... I'll wait for the current build to finish first and check there
aren't any further issues, then I'll try to re-enable the tests.
AV
On 24 July 2017 at 15:16, Eduard Braun <eduard.braun2@...173...> wrote:
Am 24.07.2017 um 16:02 schrieb Alex Valavanis:
> I've brought the trunk PPA back online... it's currently failing on the
> "make test" step:
>
That's because the build is configured to do "make test" which only runs
tests but does not build them.
If you replace it with "make check" we should be all set!
Thanks for bringing this back online!
Regards,
Eduard
11:38 p.m.
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-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
6:06 p.m.
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-
xenial-amd64.inkscape-trunk_1%3A0.92.0+devel+15937+86~
ubuntu16.04.1_BUILDING.txt.gz
>
> 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
6:28 p.m.
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...
<mailto: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-xenial-amd64.ink...
<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... <mailto: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... <mailto: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...
<mailto: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
<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
<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
<mailto:Inkscape-devel@lists.sourceforge.net>
> >>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
<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
<mailto:Inkscape-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
<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
6:30 p.m.
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
6:35 p.m.
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...
<mailto: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... <mailto: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-xenial-amd64.ink...
>
<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... <mailto: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... <mailto: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...
> <mailto: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
> <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
> <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
> <mailto:Inkscape-devel@lists.sourceforge.net>
> > >>>
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> <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
> <mailto:Inkscape-devel@lists.sourceforge.net>
> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> <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
> <mailto:Inkscape-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> <https://lists.sourceforge.net/lists/listinfo/inkscape-devel>
6:40 p.m.
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
>
>
>
7:03 p.m.
Just looking for any opportunity to tell the community we're fixing
their (substantial) problems. Maybe it's not a huge deal at this point.
On 08/10/2017 10:40 AM, Alex Valavanis wrote:
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...
<mailto: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...
> <mailto: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...
>> <mailto: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-xenial-amd64.ink...
>>
<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...
>> <mailto: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...
>> <mailto: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... <mailto: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
>> <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
>> <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
>> <mailto:Inkscape-devel@lists.sourceforge.net>
>> > >>>
>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>> <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
>> <mailto:Inkscape-devel@lists.sourceforge.net>
>> >
>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>> <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
>> <mailto:Inkscape-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>> <https://lists.sourceforge.net/lists/listinfo/inkscape-devel>
>
>
4:49 a.m.
On Thu, Aug 10, 2017 at 11:03:24AM -0600, Ryan Gorley wrote:
Just looking for any opportunity to tell the community we're
fixing their
(substantial) problems. Maybe it's not a huge deal at this point.
Not sure the trunk PPAs are in great shape for end users.
Probably better to point them to the 0.93 release notes:
http://wiki.inkscape.org/wiki/index.php/Release_notes/0.93
Unfortunately a lot's missing, but we'll need to get that filled in one
way or another.
Bryce
On 08/10/2017 10:40 AM, Alex Valavanis wrote:
>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...
><mailto: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...
>> <mailto: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...
>>> <mailto: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-xenial-amd64.ink...
>>>
<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...
>>> <mailto: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...
>>> <mailto: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... <mailto: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
>>>
<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
>>>
<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
>>> <mailto:Inkscape-devel@lists.sourceforge.net>
>>> > >>>
>>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>>
<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
>>> <mailto:Inkscape-devel@lists.sourceforge.net>
>>> >
>>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>>
<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
>>> <mailto:Inkscape-devel@lists.sourceforge.net>
>>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>> <https://lists.sourceforge.net/lists/listinfo/inkscape-devel>
>>
>>
>
>
1995
days inactive
2014
days old
inkscape-devel@lists.inkscape.org
16 comments
6 participants
participants (6)
-
Alex Valavanis -
Bryce Harrington -
Eduard Braun -
Michael Soegtrop -
Ryan Gorley -
Tobias Ellinghaus