Re: Bug#840094: blends-dev: Does not recognize multiline dependencies
Hi,
On Thu, Nov 10, 2016 at 10:38:32PM +0100, Ole Streicher wrote:
> On 10.11.2016 21:07, Andreas Tille wrote:
> > So I confirm that the first problem we detected is solved but there is
> > another one breaking Debian Edu. I have again no suspicion why the '\'
> > sign is not elimiunated from the list only in those few cases.
>
> I can also just "poke in the fog" here. I thought that the multilines
> were already eaten up by lines 537-544, and should not appear again
> here. However, they do, as my "print" debugger shows. Perlists, please
> help!!!
>
> The pragmatic solution here is to just remove the backslashes from the
> end of line. I can commit a patch that does this.
>
> However, debian-edu keeps to be broken. Reason is that the tasks contain
> lines like (development)
>
> Depends: fp-compiler, [...multiline... ], fp-units-fv
> Depends: lazarus
>
> so, with two "Depends" in one section. Or (electronics):
That's definitely broken and not supported by other tools than
blends-dev and should be fixed. Every Depends, Recommends and
Suggests should be in a separate paragraph.
> Depends: qucs, gpsim, oregano
> Recommends: education-menus, xoscope
> Suggests: kicad, kicad-doc-en, kicad-doc-de, kicad-doc-es, kicad-doc-fr
> Suggests: electric, pcb, xcircuit, freehdl, gtkwave
> Responsible: ?
> NeedConfig: no
>
> two "Suggests". This does not work anymore (no idea why), but is also
> IMO forbidden by RFC834.
The web sentinel code does not even allow one Depends and Suggests in a
common paragraph.
> I have no idea why this works without RFC834 continuation, but not with
> them.
>
> On the other hand, we *win* one more dependency: in "common", the
> "firmware-ralink" dependency line was *not* preceded one with a
> backslash. This shows that the backslash is just a bad idea for
> continuation lines.
Meanwhile I'm fully convinced that you are right here and we should fix
this soon since also in Debian Science some missing backslashes caused
loss of Dependencies in the resulting metapackages.
> --> debian-edu tasks are just broken. They don't follow any rule, and
> depending from the parser one will get always different results. Maybe
> we should fix that? remove all backslash continuation lines and
> duplicated keywords from the tasks files?
I think it should be sufficient to add line breaks where needed.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: