From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/7] libglib2: bump to version 2.50.0
Date: Mon, 10 Oct 2016 19:49:00 +0200 [thread overview]
Message-ID: <20161010194900.069c347b@free-electrons.com> (raw)
In-Reply-To: <7dc3ea74-e874-4b9b-b6e3-2789bf126616@zacarias.com.ar>
Hello,
On Mon, 10 Oct 2016 10:04:59 -0300, Gustavo Zacarias wrote:
> 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
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-10 17:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 15:01 [Buildroot] [PATCH 1/7] libglib2: bump to version 2.50.0 Gustavo Zacarias
2016-09-20 15:01 ` [Buildroot] [PATCH 2/7] glib-networking: " Gustavo Zacarias
2016-09-20 15:01 ` [Buildroot] [PATCH 3/7] gvfs: bump to version 1.30.0 Gustavo Zacarias
2016-09-20 15:01 ` [Buildroot] [PATCH 4/7] libsoup: bump to version 2.56.0 Gustavo Zacarias
2016-09-20 15:01 ` [Buildroot] [PATCH 5/7] gdk-pixbuf: bump to version 2.36.0 Gustavo Zacarias
2016-09-20 15:01 ` [Buildroot] [PATCH 6/7] atk: bump to version 2.22.0 Gustavo Zacarias
2016-09-20 15:01 ` [Buildroot] [PATCH 7/7] vala: bump to version 0.34.0 Gustavo Zacarias
2016-09-20 18:20 ` [Buildroot] [PATCH 1/7] libglib2: bump to version 2.50.0 Thomas Petazzoni
2016-09-21 12:11 ` Thomas Petazzoni
2016-10-09 20:07 ` Thomas Petazzoni
2016-10-10 13:04 ` Gustavo Zacarias
2016-10-10 17:49 ` Thomas Petazzoni [this message]
2016-10-10 17:57 ` Gustavo Zacarias
2016-10-10 19:28 ` Thomas Petazzoni
2016-10-10 21:37 ` Gustavo Zacarias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161010194900.069c347b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.