Librsvg 2.40.20 is released and is the last release in the 2.40.x series

[Federico Mena Quintero]

Hello,

I have just released librsvg-2.40.20.  This is the last release that I
will make in the 2.40.x series - the C-only version.

This release is to avoid having unreleased commits in the 2.40 branch. 
It also has a security fix.

People are *STRONGLY* encouraged to switch to 2.41.x as soon as
possible.  Librsvg 2.41.x is ABI and API compatible with 2.40.x, so it
is a drop-in replacement.  You only need a Rust toolchain to compile
it.  If you or your distro can compile Firefox 57, you can probably
compile librsvg 2.41 without problems.

Librsvg 2.40.20 is available here:

  https://download.gnome.org/sources/librsvg/2.40/

SHA256 checksums:
44d5b49a607daf0809bcf589dbf5772ac588e5a1c877be9681e12419f5ab22a4  
librsvg-2.40.20.news
dae9d34aefd447129e9da0e344dfc9ca96f067f455ff576ef493550aebf8b284  
librsvg-2.40.20.changes
cff4dd3c3b78bfe99d8fcfad3b8ba1eee3289a0823c0e118d78106be6b84c92b  
librsvg-2.40.20.tar.xz

What's new in this release:

- Except for emergencies, this will be the LAST RELEASE of the
  librsvg-2.40.x series.  We are moving to 2.41, which is vastly
  improved over the 2.40 series.  The API/ABI there remain unchaged,
  so we strongly encourage you to upgrade your sources and binaries to
  librsvg-2.41.x.
- bgo#761175 - Allow masks and clips to reuse a node being drawn.
- Don't access the file system when deciding whether to load a remote
  file with a UNC path for a paint server (i.e. don't try to load it at all).
- Vistual Studio: fixed and integrated introspection builds, so
  introspection data is built directly from the Visual Studio project
  (Chun-wei Fan).
- Visual Studio: We now use HIGHENTROPYVA linker option on x64 builds,
  to enhance the security of built binaries (Chun-wei Fan).
- Fix generation of Vala bindings when compiling in read-only source
  directories (Emmanuele Bassi).

Enjoy,

  Federico

signature.asc
Description: This is a digitally signed message part
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Need a little help with libgweather yak shaving

[Bastien Nocera]

Hello all,

If you're feeling a little generous in this holiday season, do I have
the project for you!

I've spent the past week and a bit triaging libgweather's bugzilla,
adding automated tests, and hooking up continuous integration so it's
easier than ever to contribute to libgweather.

But we still have a fair number of bugs opened against libgweather
which I'd like us to close before migrating to GitLab for issue
tracking.

I've rewritten the libgweather contribution wiki page to include what
we're looking for:
https://wiki.gnome.org/Projects/LibGWeather/ImprovingLocations

This is the list of bugs we'd like to fix before the migration:
https://bugzilla.gnome.org/buglist.cgi?bug_status=UNCONFIRMED_status=NEW_status=ASSIGNED_status=REOPENED=locations_id=271984=libgweather

A few of them are easier than others, and bug 556843 is a huge task
which you can contribute to for your country.

Feel free to comment in the bugs with references, and ask here about
more generic concerns.

Cheers
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list