Skip to contentSkip to conversation

libglib2: bump to version 2.50.0

PATCH New Gustavo Zacarias 2 participants 15 messages Sep 20, 2016 – Oct 10, 2016

lore
Share & tools
lore
#0 lore raw

PATCH 1/7 libglib2: bump to version 2.50.0

It now requires util-linux libmount so add the dependency/select.

---
 package/libglib2/Config.in     | 2 ++
 package/libglib2/libglib2.hash | 4 ++--
 package/libglib2/libglib2.mk   | 6 +++---
 3 files changed, 7 insertions(+), 5 deletions(-)
package/libglib2/Config.in +2 -0
index 84ee816..80c7d67 100644
@@ -5,6 +5,8 @@ config BR2_PACKAGE_LIBGLIB2
 	select BR2_PACKAGE_LIBFFI
 	select BR2_PACKAGE_PCRE
 	select BR2_PACKAGE_PCRE_UCP
+	select BR2_PACKAGE_UTIL_LINUX
+	select BR2_PACKAGE_UTIL_LINUX_LIBMOUNT
 	select BR2_PACKAGE_ZLIB
 	depends on BR2_USE_WCHAR # gettext
 	depends on BR2_TOOLCHAIN_HAS_THREADS
package/libglib2/libglib2.hash +2 -2
index 35728e2..3bc4021 100644
@@ -1,2 +1,2 @@
-# https://download.gnome.org/sources/glib/2.48/glib-2.48.2.sha256sum
-sha256  f25e751589cb1a58826eac24fbd4186cda4518af772806b666a3f91f66e6d3f4  glib-2.48.2.tar.xz
+# https://download.gnome.org/sources/glib/2.50/glib-2.50.0.sha256sum
+sha256  830b551fa626bda06e12729205b3c5bb0d82b924a8cf64d948945878f01b7d70  glib-2.50.0.tar.xz
package/libglib2/libglib2.mk +3 -3
index 6b1a387..5bc6ed5 100644
@@ -4,8 +4,8 @@
 #
 ################################################################################
 
-LIBGLIB2_VERSION_MAJOR = 2.48
-LIBGLIB2_VERSION = $(LIBGLIB2_VERSION_MAJOR).2
+LIBGLIB2_VERSION_MAJOR = 2.50
+LIBGLIB2_VERSION = $(LIBGLIB2_VERSION_MAJOR).0
 LIBGLIB2_SOURCE = glib-$(LIBGLIB2_VERSION).tar.xz
 LIBGLIB2_SITE = http://ftp.gnome.org/pub/gnome/sources/glib/$(LIBGLIB2_VERSION_MAJOR)
 LIBGLIB2_LICENSE = LGPLv2+
@@ -102,7 +102,7 @@ HOST_LIBGLIB2_CONF_OPTS = \
 
 LIBGLIB2_DEPENDENCIES = \
 	host-pkgconf host-libglib2 host-gettext \
-	libffi pcre zlib $(if $(BR2_NEEDS_GETTEXT),gettext)
+	libffi pcre util-linux zlib $(if $(BR2_NEEDS_GETTEXT),gettext)
 
 HOST_LIBGLIB2_DEPENDENCIES = \
 	host-gettext host-libffi host-pcre host-pkgconf host-zlib
Signature · 1 line
2.7.3
#1 lore raw

PATCH 2/7 glib-networking: bump to version 2.50.0

---
 package/glib-networking/glib-networking.hash | 4 ++--
 package/glib-networking/glib-networking.mk   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)
package/glib-networking/glib-networking.hash +2 -2
index a495af1..bbcecb7 100644
@@ -1,2 +1,2 @@
-# From http://ftp.gnome.org/pub/gnome/sources/glib-networking/2.48/glib-networking-2.48.2.sha256sum
-sha256	925c0c49d6b2b8b5695f2e33cd952d1dbb7d18d3f2f796413577719315bb3a84	glib-networking-2.48.2.tar.xz
+# From http://ftp.gnome.org/pub/gnome/sources/glib-networking/2.50/glib-networking-2.50.0.sha256sum
+sha256	3f1a442f3c2a734946983532ce59ed49120319fdb10c938447c373d5e5286bee	glib-networking-2.50.0.tar.xz
package/glib-networking/glib-networking.mk +2 -2
index b6e40f8..d3077e9 100644
@@ -4,8 +4,8 @@
 #
 ################################################################################
 
-GLIB_NETWORKING_VERSION_MAJOR = 2.48
-GLIB_NETWORKING_VERSION = $(GLIB_NETWORKING_VERSION_MAJOR).2
+GLIB_NETWORKING_VERSION_MAJOR = 2.50
+GLIB_NETWORKING_VERSION = $(GLIB_NETWORKING_VERSION_MAJOR).0
 GLIB_NETWORKING_SITE = http://ftp.gnome.org/pub/gnome/sources/glib-networking/$(GLIB_NETWORKING_VERSION_MAJOR)
 GLIB_NETWORKING_SOURCE = glib-networking-$(GLIB_NETWORKING_VERSION).tar.xz
 GLIB_NETWORKING_INSTALL_STAGING = YES
Signature · 1 line
2.7.3
#2 lore raw

PATCH 3/7 gvfs: bump to version 1.30.0

In reply to Gustavo Zacarias

Disable admin since it requires polkit-gobject + libcap.

---
 package/gvfs/gvfs.hash | 4 ++--
 package/gvfs/gvfs.mk   | 5 +++--
 2 files changed, 5 insertions(+), 4 deletions(-)
package/gvfs/gvfs.hash +2 -2
index 440671f..9c53487 100644
@@ -1,2 +1,2 @@
-# From http://ftp.gnome.org/pub/GNOME/sources/gvfs/1.28/gvfs-1.28.3.sha256sum
-sha256	458c4cb68570f6ef4a9e152995c62d0057c3e0a07ed64d84c7200cdd22f0bd17	gvfs-1.28.3.tar.xz
+# From http://ftp.gnome.org/pub/GNOME/sources/gvfs/1.30/gvfs-1.30.0.sha256sum
+sha256	2285d387213eef528f09df4b113d9d2e54ce7108c50587355d07f2a885840da4	gvfs-1.30.0.tar.xz
package/gvfs/gvfs.mk +3 -2
index e2947fd..50a2fa2 100644
@@ -4,8 +4,8 @@
 #
 ################################################################################
 
-GVFS_VERSION_MAJOR = 1.28
-GVFS_VERSION = $(GVFS_VERSION_MAJOR).3
+GVFS_VERSION_MAJOR = 1.30
+GVFS_VERSION = $(GVFS_VERSION_MAJOR).0
 GVFS_SOURCE = gvfs-$(GVFS_VERSION).tar.xz
 GVFS_SITE = http://ftp.gnome.org/pub/GNOME/sources/gvfs/$(GVFS_VERSION_MAJOR)
 GVFS_INSTALL_STAGING = YES
@@ -20,6 +20,7 @@ GVFS_CONF_ENV = ac_cv_path_LIBGCRYPT_CONFIG=$(STAGING_DIR)/usr/bin/libgcrypt-con
 # Most of these are missing library support
 GVFS_CONF_OPTS = \
 	--disable-afc \
+	--disable-admin \
 	--disable-bash-completion \
 	--disable-cdda \
 	--disable-gconf \
Signature · 1 line
2.7.3
#3 lore raw

PATCH 4/7 libsoup: bump to version 2.56.0

In reply to Gustavo Zacarias
---
 package/libsoup/libsoup.hash | 4 ++--
 package/libsoup/libsoup.mk   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)
package/libsoup/libsoup.hash +2 -2
index 45cee42..b42cf2f 100644
@@ -1,2 +1,2 @@
-# From http://ftp.gnome.org/pub/gnome/sources/libsoup/2.54/libsoup-2.54.1.sha256sum
-sha256	47b42c232034734d66e5f093025843a5d8cc4b2357c011085a2fd04ef02dd633	libsoup-2.54.1.tar.xz
+# From http://ftp.gnome.org/pub/gnome/sources/libsoup/2.56/libsoup-2.56.0.sha256sum
+sha256	d8216b71de8247bc6f274ec054c08547b2e04369c1f8add713e9350c8ef81fe5	libsoup-2.56.0.tar.xz
package/libsoup/libsoup.mk +2 -2
index 5f5156b..f6e92f8 100644
@@ -4,8 +4,8 @@
 #
 ################################################################################
 
-LIBSOUP_VERSION_MAJOR = 2.54
-LIBSOUP_VERSION = $(LIBSOUP_VERSION_MAJOR).1
+LIBSOUP_VERSION_MAJOR = 2.56
+LIBSOUP_VERSION = $(LIBSOUP_VERSION_MAJOR).0
 LIBSOUP_SOURCE = libsoup-$(LIBSOUP_VERSION).tar.xz
 LIBSOUP_SITE = http://ftp.gnome.org/pub/gnome/sources/libsoup/$(LIBSOUP_VERSION_MAJOR)
 LIBSOUP_LICENSE = LGPLv2+
Signature · 1 line
2.7.3
#4 lore raw

PATCH 5/7 gdk-pixbuf: bump to version 2.36.0

In reply to Gustavo Zacarias
---
 package/gdk-pixbuf/gdk-pixbuf.hash | 4 ++--
 package/gdk-pixbuf/gdk-pixbuf.mk   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
package/gdk-pixbuf/gdk-pixbuf.hash +2 -2
index e73170c..e5a8958 100644
@@ -1,2 +1,2 @@
-# From http://ftp.gnome.org/pub/gnome/sources/gdk-pixbuf/2.34/gdk-pixbuf-2.34.0.sha256sum
-sha256	d55e5b383ee219bd0e23bf6ed4427d56a7db5379729a6e3e0a0e0eba9a8d8879	gdk-pixbuf-2.34.0.tar.xz
+# From http://ftp.gnome.org/pub/gnome/sources/gdk-pixbuf/2.36/gdk-pixbuf-2.36.0.sha256sum
+sha256	85ab52ce9f2c26327141b3dcf21cca3da6a3f8de84b95fa1e727d8871a23245c	gdk-pixbuf-2.36.0.tar.xz
package/gdk-pixbuf/gdk-pixbuf.mk +1 -1
index 36eed60..6d1a84d 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-GDK_PIXBUF_VERSION_MAJOR = 2.34
+GDK_PIXBUF_VERSION_MAJOR = 2.36
 GDK_PIXBUF_VERSION = $(GDK_PIXBUF_VERSION_MAJOR).0
 GDK_PIXBUF_SOURCE = gdk-pixbuf-$(GDK_PIXBUF_VERSION).tar.xz
 GDK_PIXBUF_SITE = http://ftp.gnome.org/pub/gnome/sources/gdk-pixbuf/$(GDK_PIXBUF_VERSION_MAJOR)
Signature · 1 line
2.7.3
#5 lore raw

PATCH 6/7 atk: bump to version 2.22.0

In reply to Gustavo Zacarias
---
 package/atk/atk.hash | 4 ++--
 package/atk/atk.mk   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
package/atk/atk.hash +2 -2
index 7178ccc..12c9870 100644
@@ -1,2 +1,2 @@
-# From http://ftp.gnome.org/pub/gnome/sources/atk/2.20/atk-2.20.0.sha256sum
-sha256 493a50f6c4a025f588d380a551ec277e070b28a82e63ef8e3c06b3ee7c1238f0 atk-2.20.0.tar.xz
+# From http://ftp.gnome.org/pub/gnome/sources/atk/2.22/atk-2.22.0.sha256sum
+sha256 d349f5ca4974c9c76a4963e5b254720523b0c78672cbc0e1a3475dbd9b3d44b6 atk-2.22.0.tar.xz
package/atk/atk.mk +1 -1
index 663d13a..90d329a 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-ATK_VERSION_MAJOR = 2.20
+ATK_VERSION_MAJOR = 2.22
 ATK_VERSION = $(ATK_VERSION_MAJOR).0
 ATK_SOURCE = atk-$(ATK_VERSION).tar.xz
 ATK_SITE = http://ftp.gnome.org/pub/gnome/sources/atk/$(ATK_VERSION_MAJOR)
Signature · 1 line
2.7.3
#6 lore raw

PATCH 7/7 vala: bump to version 0.34.0

In reply to Gustavo Zacarias
---
 package/vala/vala.hash | 4 ++--
 package/vala/vala.mk   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)
package/vala/vala.hash +2 -2
index 4a4a41c..b8d47a6 100644
@@ -1,2 +1,2 @@
-# From https://download.gnome.org/sources/vala/0.32/vala-0.32.1.sha256sum
-sha256	dd0d47e548a34cfb1e4b04149acd082a86414c49057ffb79902eb9a508a161a9	vala-0.32.1.tar.xz
+# From https://download.gnome.org/sources/vala/0.34/vala-0.34.0.sha256sum
+sha256	5d59e1ad4c59debc83687b593345a3cf9ef2e9020354145e59a188de4348f455	vala-0.34.0.tar.xz
package/vala/vala.mk +2 -2
index 4cdc0d7..2a4d257 100644
@@ -4,8 +4,8 @@
 #
 ################################################################################
 
-VALA_VERSION_MAJOR = 0.32
-VALA_VERSION = $(VALA_VERSION_MAJOR).1
+VALA_VERSION_MAJOR = 0.34
+VALA_VERSION = $(VALA_VERSION_MAJOR).0
 VALA_SITE = http://download.gnome.org/sources/vala/$(VALA_VERSION_MAJOR)
 VALA_SOURCE = vala-$(VALA_VERSION).tar.xz
 VALA_LICENSE = LGPLv2.1+
Signature · 1 line
2.7.3
#7 lore raw

PATCH 1/7 libglib2: bump to version 2.50.0

In reply to Gustavo Zacarias

Hello,

Quoted 8 lines · Gustavo Zacarias

It now requires util-linux libmount so add the dependency/select.

---
 package/libglib2/Config.in     | 2 ++
 package/libglib2/libglib2.hash | 4 ++--
 package/libglib2/libglib2.mk   | 6 +++---
 3 files changed, 7 insertions(+), 5 deletions(-)

All applied, thanks!

One more dependency for libglib2, this is really becoming an heavy package :/

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
#8 lore raw

PATCH 1/7 libglib2: bump to version 2.50.0

In reply to Gustavo Zacarias

Hello,

Quoted 3 lines · Gustavo Zacarias

It now requires util-linux libmount so add the dependency/select.

With this new version, the crc32 symbol gets defined twice in static linking scenarios. See
http://autobuild.buildroot.net/results/c26/c2602f2e9db665d5a1d7cea8f3256099ce34a527/build-end.log

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#9 lore raw

PATCH 1/7 libglib2: bump to version 2.50.0

Hello,

Quoted 8 lines · Thomas Petazzoni
Quoted 3 lines · Gustavo Zacarias

It now requires util-linux libmount so add the dependency/select.

With this new version, the crc32 symbol gets defined twice in static linking scenarios. See
http://autobuild.buildroot.net/results/c26/c2602f2e9db665d5a1d7cea8f3256099ce34a527/build-end.log

Since this issue has been there for a long time, and caused more than 500 autobuilder failures, I've for now reverted the bump of libglib2 to 2.50.0.

Could you look into this issue, and submit a new version of libglib2 patch that doesn't exhibit this problem?

Thanks a lot!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#10 lore raw

PATCH 1/7 libglib2: bump to version 2.50.0

Quoted 17 lines · Thomas Petazzoni

Hello,

Quoted 8 lines · Thomas Petazzoni
Quoted 3 lines · Gustavo Zacarias

It now requires util-linux libmount so add the dependency/select.

With this new version, the crc32 symbol gets defined twice in static linking scenarios. See
http://autobuild.buildroot.net/results/c26/c2602f2e9db665d5a1d7cea8f3256099ce34a527/build-end.log

Since this issue has been there for a long time, and caused more than 500 autobuilder failures, I've for now reverted the bump of libglib2 to 2.50.0.

Quoted 6 lines

Could you look into this issue, and submit a new version of libglib2 patch that doesn't exhibit this problem?

Thanks a lot!

Thomas

Hi.
Hmmm ok... this causes more problems than it solves IMO.
So now what, revert gvfs, glibmm, gtk, gtkmm, wayland, weston, legacy ? Regards.

#11 lore raw

PATCH 1/7 libglib2: bump to version 2.50.0

Hello,

Quoted 3 lines · Gustavo Zacarias

Hi.
Hmmm ok... this causes more problems than it solves IMO.
So now what, revert gvfs, glibmm, gtk, gtkmm, wayland, weston, legacy ?

Hm, sadly, it causes some other problems. And indeed, if nobody takes care of the crc32 issue, the only option will be to revert all those packages. I can't take care of fixing all autobuilder issues myself.

Best regards,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#12 lore raw

PATCH 1/7 libglib2: bump to version 2.50.0

Quoted 8 lines · Thomas Petazzoni

Hello,

Quoted 3 lines · Gustavo Zacarias

Hi.
Hmmm ok... this causes more problems than it solves IMO.
So now what, revert gvfs, glibmm, gtk, gtkmm, wayland, weston, legacy ?

Quoted 7 lines

Hm, sadly, it causes some other problems. And indeed, if nobody takes care of the crc32 issue, the only option will be to revert all those packages. I can't take care of fixing all autobuilder issues myself.

Best regards,

Thomas

Hi Thomas.
Ok let's clear something out for this case.
First, i didn't like the hyperbole in the commit message, it's not 500+ failures, it didn't even reach 200.
Second, it's only for static builds.
Third, as i told you on IRC i'd look into it time allowing, this is voluntary work on spare time, so this revert didn't rest in happily with me. Fourth, i never left any big breakage of my own making at RC/release time, we are breaking eggs at this time so to speak, so a little headsup/patience would have been appreciated.
Five, yes, i knew you'd break a ton of stuff with a revert, but again "fourth" no headsup on IRC or anything - there's a reason the whole gnome stuff bump was in a series.

As you probably know the latest uclibc bump broke powerpc entirely and i didn't see any revert there, so it kind of feels personal (i know it's been fixed recently).

Regards.

#13 lore raw

PATCH 1/7 libglib2: bump to version 2.50.0

Hello,

Quoted 2 lines · Gustavo Zacarias

First, i didn't like the hyperbole in the commit message, it's not 500+ failures, it didn't even reach 200.

There are really 500+ breakage of libglib2 2.25.0, though admittedly not all of them are necessarily related to the crc32 issue.

Quoted 1 line

Second, it's only for static builds.

Correct.

Quoted 2 lines

Third, as i told you on IRC i'd look into it time allowing, this is voluntary work on spare time, so this revert didn't rest in happily with me.

Sure, and I'm perfectly fine with that. But then, you should also understand that if the problem isn't fixed in a reasonable time frame and causes a large number of build failures, it's normal if we revert, to take the time to do it properly.

I'm routinely doing this. A very recent example are the changes from Thomas DS on binutils/gdb to avoid the texinfo dependency: I reverted them half an hour after applying them, because they were breaking stuff. There's nothing wrong with this: something was broken with the patches, they need to be fixed, and in the mean time, reverting is the most appropriate solution.

Quoted 3 lines

Fourth, i never left any big breakage of my own making at RC/release time, we are breaking eggs at this time so to speak, so a little headsup/patience would have been appreciated.

Well, the issues have been occurring since September 20th, when I applied your patches. So it's been about 20 days. As you have seen above, I reverted much more quickly the patches from Thomas DS (though they are admittedly introducing a much more serious breakage).

Quoted 3 lines

Five, yes, i knew you'd break a ton of stuff with a revert, but again "fourth" no headsup on IRC or anything - there's a reason the whole gnome stuff bump was in a series.

I pinged you several times on IRC about this. I could dig the logs if you want to, but I don't think it's the point. The failures have been around for a while, and therefore hiding potentially lots of other failures. After some time, if no fix comes up, it's just normal to revert.

Quoted 3 lines

As you probably know the latest uclibc bump broke powerpc entirely and i didn't see any revert there, so it kind of feels personal (i know it's been fixed recently).

I think you're taking things way too personally here. Yes the uclibc bump was broken (but it was kind of expected due to the massive change introduced in 1.0.18), and it was fixed relatively quickly. But again, look at Thomas DS patches: I reverted them. Look at the patches from Bernd bumping Perl: I reverted them because Fran?ois Perrad didn't like them. Ditto for other patches from Bernd bumping some Python packages:
I reverted them because Christophe Vu-Brugier gave some negative feedback about them.

Reverting is just a normal thing, you shouldn't take it personally.

Best regards,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#14 lore raw

PATCH 1/7 libglib2: bump to version 2.50.0

Quoted 9 lines · Thomas Petazzoni

Hello,

Quoted 2 lines · Gustavo Zacarias

First, i didn't like the hyperbole in the commit message, it's not 500+ failures, it didn't even reach 200.

There are really 500+ breakage of libglib2 2.25.0, though admittedly not all of them are necessarily related to the crc32 issue.

Hi.
How did you get to that number?
Let's see mine...
http://autobuild.buildroot.net/?reason=libglib2-2.50.0 (from 0-50)

http://autobuild.buildroot.net/?reason=libglib2-2.50.0&start=150 (150-200)

http://autobuild.buildroot.net/?reason=libglib2-2.50.0&start=200 (gives no results)

So it's up to 200 worst case for all failure sources. glibmm alone is beating that record down with fury in a far shorter timeframe.

Quoted 8 lines
Quoted 2 lines

Third, as i told you on IRC i'd look into it time allowing, this is voluntary work on spare time, so this revert didn't rest in happily with me.

Sure, and I'm perfectly fine with that. But then, you should also understand that if the problem isn't fixed in a reasonable time frame and causes a large number of build failures, it's normal if we revert, to take the time to do it properly.

Quoted 6 lines

I'm routinely doing this. A very recent example are the changes from Thomas DS on binutils/gdb to avoid the texinfo dependency: I reverted them half an hour after applying them, because they were breaking stuff. There's nothing wrong with this: something was broken with the patches, they need to be fixed, and in the mean time, reverting is the most appropriate solution.

In this case it just backfired horribly, by not giving a headsup/talking on IRC the autobuilder results went far down the drain.
Which could have been avoided by me telling you "hey, revert will make it far worse".
After all what's the point of me being in charge of this package in DEVELOPERS if you don't consult about the consequences of such an action?

Quoted 9 lines
Quoted 3 lines

Five, yes, i knew you'd break a ton of stuff with a revert, but again "fourth" no headsup on IRC or anything - there's a reason the whole gnome stuff bump was in a series.

I pinged you several times on IRC about this. I could dig the logs if you want to, but I don't think it's the point. The failures have been around for a while, and therefore hiding potentially lots of other failures. After some time, if no fix comes up, it's just normal to revert.

You can dig all of the logs you want, they will just say on my side "i'll look into it for a proper solution when i get some free time" - there's no mystery there.

Quoted 13 lines
Quoted 3 lines

As you probably know the latest uclibc bump broke powerpc entirely and i didn't see any revert there, so it kind of feels personal (i know it's been fixed recently).

I think you're taking things way too personally here. Yes the uclibc bump was broken (but it was kind of expected due to the massive change introduced in 1.0.18), and it was fixed relatively quickly. But again, look at Thomas DS patches: I reverted them. Look at the patches from Bernd bumping Perl: I reverted them because Fran?ois Perrad didn't like them. Ditto for other patches from Bernd bumping some Python packages:
I reverted them because Christophe Vu-Brugier gave some negative feedback about them.

Quoted 1 line

Reverting is just a normal thing, you shouldn't take it personally.

It's util-linux/zlib at fault here, the libglib2 failure is just one trigger, it would have failed the same for any other project that links to both of them statically anyway.
So basically reverting to me is just glossing it over. Regards.