Re: [PATCH v2] dpkg-base: Remove newly deployed debs from buildchroots

[Jan Kiszka <jan.kiszka@siemens.com>]

On 23.08.20 18:30, Baurzhan Ismagulov wrote:
> On Tue, Aug 18, 2020 at 07:57:26AM +0200, Jan Kiszka wrote:
>>> Yes, Debian Policy section 3.2 requires that different packages have different
>>> version numbers. Maybe we should introduce a script that would do that for the
>>> developer.
>>
>> This won't help in the cases you play with a recipe, change small
>> details, rebuild, test. It's reasonable to update the version when
>> publishing. However, it's a needless burden to do that for a local
>> development cycle. Here, Isar shall support that the just built instance
>> of a package is also used locally, without an explicit "clean".
> 
> If this is how the upstream tooling works (which is a requirement for them
> since there is no other way), things will get complicated and keep breaking. An

Can you name concrete other issues?

> alternative could be to automate version bumping by requiring a local commit.
> In the long term, I don't see a way around that.

Commits for rebuilds are user-unfriendly. We will need to solve that in
a better way versioning should actually require a bump.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux