From: Enrico Joerns <ejo@pengutronix.de>
To: gurpartap singh <gurpartap.terron@yahoo.in>
Cc: "rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: Re: [RAUC] Errors in Using Rauc
Date: Wed, 5 Apr 2017 12:21:54 +0200 [thread overview]
Message-ID: <e459981b-7dd0-e842-e3f4-19d16ffbc244@pengutronix.de> (raw)
In-Reply-To: <1043369542.264396.1491368896805@mail.yahoo.com>
Hi,
On 04/05/2017 07:08 AM, gurpartap singh wrote:
> Hi Enrico,
> I am facing problems with D-Bus service.
> 1. Error creating proxy: Error calling StartServiceByName for
> de.pengutronix.rauc: Timeout was reached
>> D-Bus error while installing `/home/rauc/update.raucb
yes, we discussed this issue on the list already. For reference, see
https://www.mail-archive.com/rauc@pengutronix.de/msg00005.html
The issue here was that the non-systemd D-Bus activation of RAUC did not
work due to an error in the D-Bus service file.
The fix for this is already upstream, so you can either build the latest
version from the master branch or fix the service file manually.
https://github.com/rauc/rauc/commit/bd7afda21226318bd5ca21cd7009f0aa3a73d9f0
> 2.How to start D-Bus service and run rauc in Daemon mode.
Well this question mainly answers itself by the fix provided above. You
have to install the generated service files on your target. Then you
will be able to start the RAUC daemon with D-Bus activation.
If you prefer an explicit start of RAUC, use a service file of your
preferred init process (we only support systemd out of the box).
> 3.Please start some IRC chat so we can get live help from your team.
Well, this is an Open Source project, right. Thus you are free to use it
(and to contribute!) and people are willing to help you. But I would
give you the helpful advice not to expect community channels to provide
free full-time commercial support for you!
For now, I read your request as "Do you have an official IRC channel?"
and have to answer "No, we don't have." That is simply because we cannot
guarantee that there will be someone available for discussion in a
period of time that would not frustrate the questioner.
For now I assume asynchronous mail communication or GitHub Issues/Pull
Requests are the appropriate format for this project.
If you really need commercial support for you project, feel free to
contact my company, Pengutronix.
Best 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
next prev parent reply other threads:[~2017-04-05 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1195414473.2379963.1489058037687.ref@mail.yahoo.com>
2017-03-09 11:13 ` gurpartap singh
2017-03-13 16:08 ` Enrico Joerns
2017-04-05 5:08 ` gurpartap singh
2017-04-05 10:21 ` Enrico Joerns [this message]
2017-05-23 9:03 ` Enrico Joerns
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=e459981b-7dd0-e842-e3f4-19d16ffbc244@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=gurpartap.terron@yahoo.in \
--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