From: Enrico Joerns <ejo@pengutronix.de>
To: caglar.kilimci@accenture.com
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] RAUC service
Date: Tue, 11 Apr 2017 10:06:06 +0200 [thread overview]
Message-ID: <716f6ba5-e56b-c7f4-6c24-7c3e80aff92a@pengutronix.de> (raw)
In-Reply-To: <64a091483ef24b17b72ca00e0220bfda@BY2PR42MB136.048d.mgd.msft.net>
On 04/10/2017 12:51 PM, caglar.kilimci@accenture.com wrote:
> Hi,
>
>> -----Original Message-----
>> From: RAUC [mailto:rauc-bounces@pengutronix.de] On Behalf Of Enrico Joerns
>> Sent: Monday, April 10, 2017 1:14 PM
>> To: Kilimci, Caglar <caglar.kilimci@accenture.com>
>> Cc: rauc@pengutronix.de
>> Subject: Re: [RAUC] RUAC service
>>
>> Hi,
>>>> (rauc:537): GLib-GObject-CRITICAL **: g_object_set: assertion
>>>> 'G_IS_OBJECT (object)' failed
>>>> (rauc:537): rauc-DEBUG: name 'de.pengutronix.rauc' acquired
>>>>
>>>> What does it mean?
>>>
>>> to ease understanding what could have went wrong: Which exact version
>>> of RAUC are you using? (Because there were some changes surrounding
>>> the Code that might have caused this issue.)
>>>
>>> I am using Yocto and last commit information is:
>>> commit 3867722b8d64c43765e2d04f346dd612c02ad137
>>> Author: Jan Lübbe <jluebbe@lasnet.de>
>>> Date: Mon Feb 13 10:34:53 2017 +0100
>>>
>>> README.md: update github URL
>>> And console output is:
>>> # rauc --version
>>> rauc 0.572-3867-dirty
>>
>> Ok, if you say Yocto, I assume you are using meta-rauc, right?
>
> Yes.
>
>> And yes... definitely have to update meta-rauc to use the latest version of RAUC.
>>
>> I assume you see an error that was fixed by https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_rauc_rauc_commit_98f8484fb3357fc8b2bba7ddc7f31f6e9a04f518&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=upIHLD0Klq6JestBglGOFqnMsu-XuSQmo8ZR72YSuzk&m=WDiwOwwH7GKgnr7AJRSwUEvzGyudqO3xVljYy-FZdKc&s=kFt8J6YqEh8zSIEo2QaJnDj8RySTDNxPBWPN2x4hh-E&e=
>> (as always, the first commit after the revision that is in ;) )
>
> This patch solves the problem for now :)
>
>> For now you can update RAUC manually by adding (if not yet existing) a rauc_git.bbappend file to your projects meta layer and set
>>
>> SRCREV = "33fe5ab4bc8c364b666b7332c2f3ec6fc095b7a2"
>>
>> to use the latest version of RAUC.
>
> I could not try it for now, because of missing local infrastructure of mine but I will try this as soon as possible.
FTR: We have updated the RAUC revision in meta-rauc master to the latest
upstream revision (the one mentioned above) now.
Regards, Enrico
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
prev parent reply other threads:[~2017-04-11 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 8:40 [RAUC] RUAC service caglar.kilimci
2017-04-10 9:18 ` Enrico Joerns
2017-04-10 9:29 ` caglar.kilimci
2017-04-10 10:14 ` Enrico Joerns
2017-04-10 10:51 ` caglar.kilimci
2017-04-11 8:06 ` Enrico Joerns [this message]
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=716f6ba5-e56b-c7f4-6c24-7c3e80aff92a@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=caglar.kilimci@accenture.com \
--cc=rauc@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox