11:17 p.m.
A year ago we kicked off a rapid 0.92 release, but turns out it wasn't
so rapid! But I'd like to re-kickoff 0.92, with renewed hopes of
getting through the remainder of the release process swiftly.
The main thing the release got hung up on was the cmake transition, but
at this point it's actually close to done and I think we can proceed.
We've accumulated a lot of nice features for this release. Please
review (and make sure your own items are listed!)
http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92
I'd like to propose the following expedited plan for getting the release
out, with Chill being today, Frost in about a week, and Freeze a week or
so.
Bryce
# Period Tasks Notes
--------------------------------------------------------------------------------
√1. Open development.
√Implement new build system
√Begin switching packaging to use new build system
2. Chill. Development focuses on wrapping up
Post inkscape-0.92-pre0.tar.gz
Today Disable features that aren't finished
Identify 'make distcheck' issues
Identify remaining writing needed for Release Notes.
Identify any release blocker bugs [scislac]
Start an About Screen contest
√ Recruit Release Wardens for Hard Freeze
3. Frost. Only production-ready code committed to Mainline
Finalize any major changes to platform packaging
May 15 Inkscape must pass 'make distcheck'
(1 wk) Finalize about screen
Finalize Release Notes except Known Issues
Post additional inkscape-0.92-pre*.tar.gz releases
Packagers test creating pkgs of the -pre* releases
4. Freeze. Stable Branch is forked from Mainline
Regular development resumes on Mainline.
May 22nd-ish Only Release Wardens can commit to Stable Branch
Cherrypick bug fixes from Mainline to Stable
Complete any late work under advisement of Wardens
Focus on release-critical bug fixing.
String Freeze No further string changes allowed on Stable Branch.
Translators work on translations.
Finalize all extensions
Finalize codebase translations
Finalize Known Issues section of Release Notes
Finalize packaging scripts
Post additional inkscape-0.92-pre*.tar.gz releases
5. Release. Post inkscape-0.92.tar.gz
Post packages
Post official announcements
Plan 0.92.1+ release(s), if needed
6. Open development.
== Postponed ==
Decide new unit testing system
Ensure Windows uninstall works
Integrate new swatch dialog
Migrate mailing lists off sourceforge
(Other bits off roadmap...)
Triage and prioritize bugs report this year
Finalize tutorials to be shipped with release
Finalize other docs included in the release
4:35 p.m.
Hi all,
The release process is so fast I just noticed we have already reached string freeze...
There are 214 reports linked to 0.92 and half of them are regressions.
I *feel* we should at least try to fix some of the 25 high importance regressions before
releasing.
What about a bug hunt?
Regards,
--
Nicolas
8:12 p.m.
Hi Nicolas,
I totally agree! One of Inkscapes biggest weaknesses are regressions.
While a new release often brings many exciting new features that people
would like to play around with, there are often severe regressions that
not only cancel those achievements but even leave users with mixed to
negative feelings about the new release. If we could sort out the worst
regressions the profit would therefore be disproportional.
Best example is bug 1571192 [1] (severe performance regression in GTK2
builds caused by some - in principle very welcome - GTK3 fixes during
the hackfest). I had used trunk builds for my productive work for quite
some time now. Since this regression I stopped using them and even
returned to stable 0.91 builds on some machines. For me a 0.92 release
without a fix for that issue would be worthless, despite the many great
features and improvements it would offer. Therefore also the slightly
off-topic question: Are you making any progress on this issue Krzysztof?
I hope I can have a look at some bugs, but I don't have too much time
right now... Also German translation needs some more work which is
probably as important as fixing bugs now that we're in string freeze...
Best Regards,
Eduard
[1] https://bugs.launchpad.net/inkscape/+bug/1571192
Am 30.05.2016 um 16:35 schrieb Nicolas Dufour:
Hi all,
The release process is so fast I just noticed we have already reached string freeze...
There are 214 reports linked to 0.92 and half of them are regressions.
I *feel* we should at least try to fix some of the 25 high importance regressions before
releasing.
What about a bug hunt?
Regards,
--
Nicolas
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
8:40 p.m.
Thanks Eduard,
Regressions that are critical to the release are noted as blockers. You
can help inkscape manage it's bugs overall by making sure key bugs are
marked as blocking or critical as needed. I think we should talk more
about which bugs should be more important to the next release as we go
into freeze.
Our community will always be on the back-foot for regressions because
it is open to contributions, only middling at code review and has no
(yet) funding for bug fixing. Taken together you can see how we
encourage features and discourage bug fixing structurally.
Although we encourage bug fixing socially ;-) so if you've written some
code this year, please please fix some bugs for the next release. My
own personal plea which will hopefully encourage me to also fix some
bugs for the release.
Martin,
On Tue, 2016-05-31 at 20:12 +0200, Eduard Braun wrote:
Hi Nicolas,
I totally agree! One of Inkscapes biggest weaknesses are
regressions.
While a new release often brings many exciting new features that
people
would like to play around with, there are often severe regressions
that
not only cancel those achievements but even leave users with mixed
to
negative feelings about the new release. If we could sort out the
worst
regressions the profit would therefore be disproportional.
Best example is bug 1571192 [1] (severe performance regression in
GTK2
builds caused by some - in principle very welcome - GTK3 fixes
during
the hackfest). I had used trunk builds for my productive work for
quite
some time now. Since this regression I stopped using them and even
returned to stable 0.91 builds on some machines. For me a 0.92
release
without a fix for that issue would be worthless, despite the many
great
features and improvements it would offer. Therefore also the
slightly
off-topic question: Are you making any progress on this issue
Krzysztof?
I hope I can have a look at some bugs, but I don't have too much
time
right now... Also German translation needs some more work which is
probably as important as fixing bugs now that we're in string
freeze...
Best Regards,
Eduard
[1] https://bugs.launchpad.net/inkscape/+bug/1571192
Am 30.05.2016 um 16:35 schrieb Nicolas Dufour:
>
> Hi all,
>
> The release process is so fast I just noticed we have already
> reached string freeze...
>
> There are 214 reports linked to 0.92 and half of them are
> regressions.
> I *feel* we should at least try to fix some of the 25 high
> importance regressions before releasing.
>
> What about a bug hunt?
>
> Regards,
> --
> Nicolas
>
> -----------------------------------------------------------------
> -------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth
> and traffic
> patterns at an interface-level. Reveals which users, apps, and
> protocols are
> consuming the most bandwidth. Provides multi-vendor support for
> NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using
> capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;1326
> 59582;e
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
-------------------------------------------------------------------
-----------
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and
protocols are
consuming the most bandwidth. Provides multi-vendor support for
NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using
capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659
582;e
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
6:58 a.m.
On Tue, May 31, 2016 at 02:40:01PM -0400, Martin Owens wrote:
Thanks Eduard,
Regressions that are critical to the release are noted as blockers. You
can help inkscape manage it's bugs overall by making sure key bugs are
marked as blocking or critical as needed. I think we should talk more
about which bugs should be more important to the next release as we go
into freeze.
Our community will always be on the back-foot for regressions because
it is open to contributions, only middling at code review and has no
(yet) funding for bug fixing. Taken together you can see how we
encourage features and discourage bug fixing structurally.
Keeping things open for contributions has always been an important
principle in Inkscape since we founded the project. But you're entirely
correct it comes with the corresponding downside that it's also rather
open to incoming bugs too. Over time the increasing number of features
has increased the overall complexity of the software too, making bugs
both more likely and more tricky to fix.
Although we encourage bug fixing socially ;-) so if you've
written some
code this year, please please fix some bugs for the next release. My
own personal plea which will hopefully encourage me to also fix some
bugs for the release.
I'd love to hear ideas on how we could stimulate better focus onto bug
fixing (and general code cleanup / refactoring), particularly as we
advance towards 1.0.
Bryce
Martin,
On Tue, 2016-05-31 at 20:12 +0200, Eduard Braun wrote:
> Hi Nicolas,
>
> I totally agree! One of Inkscapes biggest weaknesses are
> regressions.
> While a new release often brings many exciting new features that
> people
> would like to play around with, there are often severe regressions
> that
> not only cancel those achievements but even leave users with mixed
> to
> negative feelings about the new release. If we could sort out the
> worst
> regressions the profit would therefore be disproportional.
>
> Best example is bug 1571192 [1] (severe performance regression in
> GTK2
> builds caused by some - in principle very welcome - GTK3 fixes
> during
> the hackfest). I had used trunk builds for my productive work for
> quite
> some time now. Since this regression I stopped using them and even
> returned to stable 0.91 builds on some machines. For me a 0.92
> release
> without a fix for that issue would be worthless, despite the many
> great
> features and improvements it would offer. Therefore also the
> slightly
> off-topic question: Are you making any progress on this issue
> Krzysztof?
>
> I hope I can have a look at some bugs, but I don't have too much
> time
> right now... Also German translation needs some more work which is
> probably as important as fixing bugs now that we're in string
> freeze...
>
> Best Regards,
> Eduard
>
> [1] https://bugs.launchpad.net/inkscape/+bug/1571192
>
>
> Am 30.05.2016 um 16:35 schrieb Nicolas Dufour:
> >
> > Hi all,
> >
> > The release process is so fast I just noticed we have already
> > reached string freeze...
> >
> > There are 214 reports linked to 0.92 and half of them are
> > regressions.
> > I *feel* we should at least try to fix some of the 25 high
> > importance regressions before releasing.
> >
> > What about a bug hunt?
> >
> > Regards,
> > --
> > Nicolas
> >
> > -----------------------------------------------------------------
> > -------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth
> > and traffic
> > patterns at an interface-level. Reveals which users, apps, and
> > protocols are
> > consuming the most bandwidth. Provides multi-vendor support for
> > NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using
> > capacity
> > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;1326
> > 59582;e
> > _______________________________________________
> > Inkscape-devel mailing list
> > Inkscape-devel(a)lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>
> -------------------------------------------------------------------
> -----------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and
> protocols are
> consuming the most bandwidth. Provides multi-vendor support for
> NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using
> capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659
> 582;e
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAABCAAGBQJXTdqBAAoJEOVbsiwf4qcgTiMP/2Ox3690q4PnuKUBib6W7+hc
x5xdQ8Z4+oLJWgqwC1kEzKvq6jlPYdlXzOLg6lS3QZ+hRyaCZLeL9udwDOOx3d3i
DCmPqrR/n8SvaQ1l0srHILZN3PO9QkzftMhommFfojdmu2BeHvZ3RzF2pFew93Q3
0GjpGMdOgzmyT6wwaNf4RnoxdXcZxivacJyccNfgFuAKFI0BfZmbQkhYz0AFqYVM
PPKolka/39ZrNb09gLzU4KRJwvhzf4EcdlII/Ke7WrUkkD5yEd2Zt9/L/DwaxzN5
5kEiC8zE9UW1/B/YzY3EU2TT223EbQ6T2LKmW5U5Xwd/ITxf0gNYsEB65yTvMm79
ZXXZa2gU0t7L7p8s/q8SgUsvvPeE5/WHmQI1wqihjC6/8KvZe0aivtA2sP3eB4SS
ScFNgBRjaN9WXH0bPHtG6XJfl219HK88Xdd6aVUIsplN8Fgkeysvu1kJC5N7z3eK
RJUWbppOTEyfGypO1S7BJ3CWaIgODrbzP/a+/00m5///C0HMaKzehocg7ZYiWJ5Q
jnk3e+bZ6IlwCPlqxzTjTjMTtsF5EGnSA73Yb/EuzGS/1M5bL6fPb4GsJgMgDmuP
jI7GClX0o15kzAX71ic4KD0yFU5ZHxKYkDS/CnApG+v8V8ykwy6Fq6Ntt/CrZF8/
DNY503xjBBWLv6e4y+rh
=9C6W
-----END PGP SIGNATURE-----
9:45 a.m.
On 5 June 2016 at 06:58, Bryce Harrington wrote:
On Tue, May 31, 2016 at 02:40:01PM -0400, Martin Owens wrote:
> Although we encourage bug fixing socially ;-) so if you've written some
> code this year, please please fix some bugs for the next release. My
> own personal plea which will hopefully encourage me to also fix some
> bugs for the release.
I'd love to hear ideas on how we could stimulate better focus onto bug
fixing (and general code cleanup / refactoring), particularly as we
advance towards 1.0.
How about something like Bugs Ahoy[1], which is used by Mozilla to
track the bugs and features related to the interests of the users and
degree of complexity?
That doesn't have to be a separated website but could just be a page
in the wiki categorizing bugs a bit.
Sebastian
[1] http://www.joshmatthews.net/bugsahoy/
1:50 p.m.
Bryce,
One of the biggest issues I see right now is that Inkscape will not compile
on Windows (at least 64bit). The cmake files have to be modified so that
system files are picked up correctly during linking. :(
Thanks,
Partha
On Sun, Jun 5, 2016 at 3:45 AM, Sebastian Zartner <
sebastianzartner@...400...> wrote:
On 5 June 2016 at 06:58, Bryce Harrington wrote:
> On Tue, May 31, 2016 at 02:40:01PM -0400, Martin Owens wrote:
>> Although we encourage bug fixing socially ;-) so if you've written some
>> code this year, please please fix some bugs for the next release. My
>> own personal plea which will hopefully encourage me to also fix some
>> bugs for the release.
>
> I'd love to hear ideas on how we could stimulate better focus onto bug
> fixing (and general code cleanup / refactoring), particularly as we
> advance towards 1.0.
How about something like Bugs Ahoy[1], which is used by Mozilla to
track the bugs and features related to the interests of the users and
degree of complexity?
That doesn't have to be a separated website but could just be a page
in the wiki categorizing bugs a bit.
Sebastian
[1] http://www.joshmatthews.net/bugsahoy/
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and protocols
are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
7:49 p.m.
On Sun, Jun 05, 2016 at 07:50:22AM -0400, Partha Bagchi wrote:
Bryce,
One of the biggest issues I see right now is that Inkscape will not compile
on Windows (at least 64bit). The cmake files have to be modified so that
system files are picked up correctly during linking. :(
Send me the list of changes that need to be made to support that.
Bryce
Thanks,
Partha
On Sun, Jun 5, 2016 at 3:45 AM, Sebastian Zartner <
sebastianzartner@...400...> wrote:
> On 5 June 2016 at 06:58, Bryce Harrington wrote:
> > On Tue, May 31, 2016 at 02:40:01PM -0400, Martin Owens wrote:
> >> Although we encourage bug fixing socially ;-) so if you've written
some
> >> code this year, please please fix some bugs for the next release. My
> >> own personal plea which will hopefully encourage me to also fix some
> >> bugs for the release.
> >
> > I'd love to hear ideas on how we could stimulate better focus onto bug
> > fixing (and general code cleanup / refactoring), particularly as we
> > advance towards 1.0.
>
> How about something like Bugs Ahoy[1], which is used by Mozilla to
> track the bugs and features related to the interests of the users and
> degree of complexity?
> That doesn't have to be a separated website but could just be a page
> in the wiki categorizing bugs a bit.
>
> Sebastian
>
> [1] http://www.joshmatthews.net/bugsahoy/
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>
8:23 a.m.
FYI: I have invested quite some time into getting Inkscape to compile on
Windows using CMake. My changes are available in this branch:
http://launchpad.net/~faubulous/inkscape/cmake-win32
Five weeks ago I proposed a merge of the branch into trunk. However, that
never happend. The version in this repository should compile just fine
using 64-bit and 32-bit. There's two remaining issues which I did not
manage to solve:
1. Inkscape crashes when trying to load locales (serious issue. Did not
find a solution in weeks. May be some gettext expert does know whats going
on.).
2. The app icon does not get compiled in (Minor issue. RC file needs to be
compiled into executable instead of libinkscape_base).
In order to compile it, just edit configure.bat to set your environment
variables and build type. Run 'configure.bat' and then 'mingw32-make
install -j X'.
*Semiodesk GmbH | *Werner-von-Siemens-Str. 6 Geb. 15k, 86159 Augsburg,
Germany | Phone: +49 821 8854401 | Fax: +49 821 8854410 | www.semiodesk.com
This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended recipient(s).
Any unauthorized disclosure, dissemination, distribution, copying or the
taking of any action in reliance on the information herein is prohibited.
E-mails are not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, or contain viruses. Anyone who communicates
with us by e-mail is deemed to have accepted these risks. Semiodesk GmbH is
not responsible for errors or omissions in this message and denies any
responsibility for any damage arising from the use of e-mail. Any opinion
and other statement contained in this message and any attachment are solely
those of the author and do not necessarily represent those of the company.
2016-06-05 19:49 GMT+02:00 Bryce Harrington <bryce@...961...>:
On Sun, Jun 05, 2016 at 07:50:22AM -0400, Partha Bagchi wrote:
> Bryce,
>
> One of the biggest issues I see right now is that Inkscape will not
compile
> on Windows (at least 64bit). The cmake files have to be modified so that
> system files are picked up correctly during linking. :(
Send me the list of changes that need to be made to support that.
Bryce
> Thanks,
> Partha
>
>
> On Sun, Jun 5, 2016 at 3:45 AM, Sebastian Zartner <
> sebastianzartner@...400...> wrote:
>
> > On 5 June 2016 at 06:58, Bryce Harrington wrote:
> > > On Tue, May 31, 2016 at 02:40:01PM -0400, Martin Owens wrote:
> > >> Although we encourage bug fixing socially ;-) so if you've
written
some
> > >> code this year, please please fix some bugs for the next release. My
> > >> own personal plea which will hopefully encourage me to also fix some
> > >> bugs for the release.
> > >
> > > I'd love to hear ideas on how we could stimulate better focus onto
bug
> > > fixing (and general code cleanup / refactoring), particularly as we
> > > advance towards 1.0.
> >
> > How about something like Bugs Ahoy[1], which is used by Mozilla to
> > track the bugs and features related to the interests of the users and
> > degree of complexity?
> > That doesn't have to be a separated website but could just be a page
> > in the wiki categorizing bugs a bit.
> >
> > Sebastian
> >
> > [1] http://www.joshmatthews.net/bugsahoy/
> >
> >
> >
------------------------------------------------------------------------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> > traffic
> > patterns at an interface-level. Reveals which users, apps, and
protocols
> > are
> > consuming the most bandwidth. Provides multi-vendor support for
NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> > planning reports.
https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> > _______________________________________________
> > Inkscape-devel mailing list
> > Inkscape-devel(a)lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> >
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and protocols
are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
11:24 a.m.
On Mon, 2016-06-06 at 08:23 +0200, Sebastian Faubel wrote:
FYI: I have invested quite some time into getting Inkscape to
compile
on Windows using CMake. My changes are available in this branch: http
://launchpad.net/~faubulous/inkscape/cmake-win32
Five weeks ago I proposed a merge of the branch into trunk. However,
that never happend. The version in this repository should compile
just fine using 64-bit and 32-bit. There's two remaining issues which
I did not manage to solve:
1. Inkscape crashes when trying to load locales (serious issue. Did
not find a solution in weeks. May be some gettext expert does know
whats going on.).
2. The app icon does not get compiled in (Minor issue. RC file needs
to be compiled into executable instead of libinkscape_base).
In order to compile it, just edit configure.bat to set your
environment variables and build type. Run 'configure.bat' and then
'mingw32-make install -j X'.
Has this been merged?
Tav
3:36 p.m.
Hi Bryce,
Eduard already posted the output from his attempt to compile Inkscape using
the current cmake build system and so will not regurgitate that.
From that post, the affected functions are strdup, close, read,
unlink,
fileno, dup2 and nextafter. All of these functions have an equivalent
"_"
(underscore) version within Windows and so, I was able to substitute those
in the source files and get the compiler to remove all those undefined
references.
I am still stumped with the following:
Z:/foss/gcc/64bit/gcc-posix-5.3.0/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vfprintf.o):mingw_vfprintf.c:(.text+0x11):
undefined reference to `_lock_file'
Z:/foss/gcc/64bit/gcc-posix-5.3.0/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vfprintf.o):mingw_vfprintf.c:(.text+0x33):
undefined reference to `_unlock_file'
Z:/foss/gcc/64bit/gcc-posix-5.3.0/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vprintf.o):mingw_vprintf.c:(.text+0x16):
undefined reference to `_lock_file'
Z:/foss/gcc/64bit/gcc-posix-5.3.0/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vprintf.o):mingw_vprintf.c:(.text+0x44):
undefined reference to `_unlock_file'
collect2.exe: error: ld returned 1 exit status
src/CMakeFiles/inkscape_base.dir/build.make:18500: recipe for target
`lib/libinkscape_base.dll' failed
make[2]: *** [lib/libinkscape_base.dll] Error 1
CMakeFiles/Makefile2:666: recipe for target
`src/CMakeFiles/inkscape_base.dir/all' failed
make[1]: *** [src/CMakeFiles/inkscape_base.dir/all] Error 2
Makefile:127: recipe for target `all' failed
make: *** [all] Error 2
I don't yet know how to fix this.
Please let me know if you have any suggestions or questions.
Thanks,
Partha
On Sun, Jun 5, 2016 at 1:49 PM, Bryce Harrington <bryce@...961...>
wrote:
On Sun, Jun 05, 2016 at 07:50:22AM -0400, Partha Bagchi wrote:
> Bryce,
>
> One of the biggest issues I see right now is that Inkscape will not
compile
> on Windows (at least 64bit). The cmake files have to be modified so that
> system files are picked up correctly during linking. :(
Send me the list of changes that need to be made to support that.
Bryce
> Thanks,
> Partha
>
>
> On Sun, Jun 5, 2016 at 3:45 AM, Sebastian Zartner <
> sebastianzartner@...400...> wrote:
>
> > On 5 June 2016 at 06:58, Bryce Harrington wrote:
> > > On Tue, May 31, 2016 at 02:40:01PM -0400, Martin Owens wrote:
> > >> Although we encourage bug fixing socially ;-) so if you've
written
some
> > >> code this year, please please fix some bugs for the next release. My
> > >> own personal plea which will hopefully encourage me to also fix some
> > >> bugs for the release.
> > >
> > > I'd love to hear ideas on how we could stimulate better focus onto
bug
> > > fixing (and general code cleanup / refactoring), particularly as we
> > > advance towards 1.0.
> >
> > How about something like Bugs Ahoy[1], which is used by Mozilla to
> > track the bugs and features related to the interests of the users and
> > degree of complexity?
> > That doesn't have to be a separated website but could just be a page
> > in the wiki categorizing bugs a bit.
> >
> > Sebastian
> >
> > [1] http://www.joshmatthews.net/bugsahoy/
> >
> >
> >
------------------------------------------------------------------------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> > traffic
> > patterns at an interface-level. Reveals which users, apps, and
protocols
> > are
> > consuming the most bandwidth. Provides multi-vendor support for
NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> > planning reports.
https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> > _______________________________________________
> > Inkscape-devel mailing list
> > Inkscape-devel(a)lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> >
6:12 a.m.
On Tue, May 31, 2016 at 08:12:12PM +0200, Eduard Braun wrote:
Hi Nicolas,
I totally agree! One of Inkscapes biggest weaknesses are
regressions. While a new release often brings many exciting new
features that people would like to play around with, there are often
severe regressions that not only cancel those achievements but even
leave users with mixed to negative feelings about the new release.
If we could sort out the worst regressions the profit would
therefore be disproportional.
Best example is bug 1571192 [1] (severe performance regression in
GTK2 builds caused by some - in principle very welcome - GTK3 fixes
during the hackfest). I had used trunk builds for my productive work
for quite some time now. Since this regression I stopped using them
and even returned to stable 0.91 builds on some machines. For me a
0.92 release without a fix for that issue would be worthless,
despite the many great features and improvements it would offer.
Therefore also the slightly off-topic question: Are you making any
progress on this issue Krzysztof?
Yes, this is one of the release critical bugs we're already tracking.
This was discussed at the release meeting yesterday. This may have been
due to a Gtk3 fix landed during the hackfest.
I hope I can have a look at some bugs, but I don't have too much
time right now...
Am 30.05.2016 um 16:35 schrieb Nicolas Dufour:
>Hi all,
>
>The release process is so fast I just noticed we have already reached string
freeze...
>
>There are 214 reports linked to 0.92 and half of them are regressions.
>I *feel* we should at least try to fix some of the 25 high importance regressions
before releasing.
>
>What about a bug hunt?
We're skipping doing a bug hunt this time around in order to get the
release out more quickly. It would be great to get more regressions
resolved, but time is a limited commodity, as Eduard points out. We
still have a lot left to do for the release, so there's ample time for
anyone that would like to focus on fixing more bugs before we release.
Bryce
2549
days inactive
2588
days old
inkscape-devel@lists.inkscape.org
11 comments
8 participants
participants (8)
-
Bryce Harrington -
Eduard Braun -
Martin Owens -
Nicolas Dufour -
Partha Bagchi -
Sebastian Faubel -
Sebastian Zartner -
Tavmjong Bah