From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] buildchroot: Allow downgrades when installing packages
Date: Mon, 25 Feb 2019 12:08:23 +0100 [thread overview]
Message-ID: <ad489b83-d3f6-0e6f-834d-d8a7e3152dc7@siemens.com> (raw)
In-Reply-To: <20190225111530.36c1b655@md1za8fc.ad001.siemens.net>
On 25.02.19 11:15, Henning Schild wrote:
> Am Mon, 25 Feb 2019 10:57:33 +0100
> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
>
>> On 25.02.19 10:39, [ext] Henning Schild wrote:
>>> Am Sat, 23 Feb 2019 11:44:21 +0100
>>> schrieb Jan Kiszka <jan.kiszka@web.de>:
>>>
>>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>>
>>>> This can happen when changing the recipe of a self-built package,
>>>> and that already when going from v1.0-rc3 to v1.0.
>>>
>>> Seems pretty risky. If the only motivation is a local package, i
>>> would argue your layer has a bug because it is going "up and down".
>>> If it
>>
>> Look at the example I cited: It was an upgrade.
>
> In that case your version was wrong.
>
> ... The format is: [epoch:]upstream_version[-debian_revision].
>
> ... The upstream_version may contain only alphanumerics [6] and the
> characters . + - ~ (full stop, plus, hyphen, tilde) and should start
> with a digit. If there is no debian_revision then hyphens are not
> allowed.
>
> https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-version
>
> So it should have been v1.0-rc3-deb0, or v1.0+rc3 ...
> It is a bug in your layer not in Isar.
Removing -rcX from a version string is lexically a downgrade, logically not. I'm
not that sure if you can compensate this.
Anyway, a real downgrade is a valid development scenario as well for our isar-apt.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-02-25 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 10:44 Jan Kiszka
2019-02-25 9:39 ` Henning Schild
2019-02-25 9:57 ` Jan Kiszka
2019-02-25 10:15 ` Henning Schild
2019-02-25 11:08 ` Jan Kiszka [this message]
2019-03-19 10:10 ` Baurzhan Ismagulov
2019-03-19 10:31 ` Jan Kiszka
2019-03-19 17:33 ` Maxim Yu. Osipov
2019-03-19 18:46 ` Jan Kiszka
2019-03-04 9:04 ` Claudius Heine
2019-03-04 9:08 ` Jan Kiszka
2019-03-28 12:42 ` Maxim Yu. Osipov
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=ad489b83-d3f6-0e6f-834d-d8a7e3152dc7@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/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