From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
Steffen Sledz <sledz@dresearch-fe.de>
Cc: Lianhao Lu <lianhao.lu@intel.com>
Subject: Re: hash generation for PR Service?
Date: Wed, 17 Sep 2014 17:11:10 +0100 [thread overview]
Message-ID: <1410970270.14624.106.camel@ted> (raw)
In-Reply-To: <54197EDC.3070406@dresearch-fe.de>
On Wed, 2014-09-17 at 14:30 +0200, Steffen Sledz wrote:
> Hi Guys,
>
> On 15.09.2014 08:19, Steffen Sledz wrote:
> > On 10.09.2014 13:24, Steffen Sledz wrote:
> >> I'm not sure if this is the right mailing list for our problem. Please forgive me if not (and tell me the right one).
> >>
> >>
> >> We're investigating some problems related with package versions going backwards using a PR Service[1].
> >>
> >> Can someone give some hints where we can get information about
> generation of the hashes which are used to request values from the PR
> service? Especially which data/files/directories are involved..
> >>
> >>
> >> [1] <https://wiki.yoctoproject.org/wiki/PR_Service>
> >
> > Ping! Who can provide related information?
>
> there was no feedback in the ml. :(
>
> Can you help us on this issue?
The hashes are the same hashes bitbake itself uses to decide whether to
reexecute tasks or not and are the same hashes encoded into the sstate
objects.
The manual gives information about this:
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#checksums
Please read and understand that, then if you have specific questions,
please ask them and you may get a more targeted answer. At the moment
the question is not specific enough to be easy to answer.
Cheers,
Richard
prev parent reply other threads:[~2014-09-17 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 11:24 hash generation for PR Service? Steffen Sledz
2014-09-15 6:19 ` Steffen Sledz
[not found] ` <54197EDC.3070406@dresearch-fe.de>
2014-09-17 16:11 ` Richard Purdie [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=1410970270.14624.106.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=lianhao.lu@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sledz@dresearch-fe.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 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.