All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tino Breddin <tbreddin@tpip.net>
To: yocto@yoctoproject.org
Subject: Problem with AUTOINC and ipk
Date: Wed, 17 Jul 2013 13:14:16 +0200 (CEST)	[thread overview]
Message-ID: <2109127027.634544.1374059656770.JavaMail.root@tpip.net> (raw)
In-Reply-To: <2018085420.634497.1374059058554.JavaMail.root@tpip.net>

Hi there,

We are having problems with using AUTOINC together with the ipk package format. I'm not sure whether this issue applies to rpm and deb as well.

Given the following configuration in a recipe:

SRCREV = "AUTOINC"
PV = "git${SRCPV}"
PR = "r0"

The generated package will have a version like this:

git0+e6d1870200802f32e17e334272191397e15aec53-r0

In case the latest Git revision changes, the new package would have the version:

git0+30249a36b39482a98772c881334ee703715a54cc-r0

My understanding is that the first integer before the + is meant to be incremented monotonically to allow the package manager to figure out that a upgrade is available. Where is the state for this integer kept? Obviously if 2 developers build the package independent from each other it would always be 0 initially. But it will stay 0 for a single developer too if the package is cleaned first. At least that is what we are seeing.

I'd appreciate any feedback on how to handle recipes which should follow the Git HEAD.

Cheers,
Tino


       reply	other threads:[~2013-07-17 11:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2018085420.634497.1374059058554.JavaMail.root@tpip.net>
2013-07-17 11:14 ` Tino Breddin [this message]
2013-07-17 15:28   ` Problem with AUTOINC and ipk Martin Jansa

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=2109127027.634544.1374059656770.JavaMail.root@tpip.net \
    --to=tbreddin@tpip.net \
    --cc=yocto@yoctoproject.org \
    /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.