Andreas Tille <andr...@an3as.eu> writes:
> On Tue, Apr 10, 2018 at 04:48:32PM +0200, Ole Streicher wrote:
>> Andreas Tille <ti...@debian.org> writes:
>> > I'm not sure about the UDD usage. I've manually used
>> > /usr/share/blends-dev/blend-gen-control --udd -r UNRELEASED -S -t
>> > but it seems its not doing anything.
>> There are no double-checks in the moment. The release is directly
>> queried from the "release" database, so "UNRELEASED" will return an
>> empty list (and therefore downgrade all packages). I however don't
>> understand what this is for? Is it a hardcoded equivalent to unstable?
> $ cat /etc/blends/sources.list.UNRELEASED
> # For testing purposes this sources.list might be useful. It is a
> # good practice to use UNRELEASED in the changelog as target distribution
> # for not yet finished packages and blends-dev should also work in this
> # case
> deb http://ftp.debian.org/debian unstable main
> I now tried
> /usr/share/blends-dev/blend-gen-control --udd -r unstable -S -c -m
> which results in a change of the debian/control file. I see some diffs
> compared to the non-udd version. I do not have time to investigate those
> single differences (all in all 40 diff paragraphs). Just to make sure
> I understood the test case correctly: Both results (with --udd and
> without) should have no difference, right?
In principle, yes. However the main difference is that the apt version
takes the packages according the distribution setting in
/etc/blends/sources.list.*, while the UDD version takes it from the
So, /etc/blends/sources.list.unstable maps to testing, while "--udd -r
unstable" will query for the unstable release and so take sid.
I have seen the discussion why unstable maps to testing; and in
principle one could map "UNRELEASED" --> "unstable" and "unstable" -->
"testing"; however I don't want to have this coded in two different
places: once in /etc/blends/sources.list.* and once in
blends-gen-control. So, if we have it in blends-gen-control (or in the
Makefile), /etc/sources.list.* should be reverted to standard.
> BTW, I think my previous test - as non-sense it probably was to use
> UNRELEASED - uncovered a problem: If there is an empty list returned
> the debian/control file should be changed to everything Suggests.
> However it did not change at all which is wrong.
I'll check this.