[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#759403: lintian: Please publish machine-readable report for all packages



Hi,

Niels Thykier wrote (27 Aug 2014 05:06:11 GMT) :
> I am personally considering whether we should have it in one file.
> Maybe something like:

>   "$SOURCE/$VERSION":
>     maintainer: ...
>     ...
>     binaries:
>     - "$BINARY1/$VERSION1/$ARCH"
>       tags:
>       - $TAG_NAME:
>         ...
>       - $TAG_NAME:
>         ...
>       ...
>    - tags:
>      - $TAG_NAME:
>        ...
>    - udebs:
>      - "$UDEB1/$VERSION1/$ARCH":
>         tags:
>         - $TAG_NAME:
>           ...
>         - $TAG_NAME:
>           ...
>         ...

Works for me.

> Note that $SOURCE/$VERSION should be enough to uniquely identify a
> source.  For binaries/udeb we also need the architecture.

I have a working PoC locally for listing $SOURCE/$VERSION and the
corresponding source package tags.

But regarding binaries & udebs, I have a problem. It looks like
parse_lintian_log loses the architecture information along the way:
e.g. in $by_maint{$maintainer}{$source}{$source_version}, pkg_info
hashes that have type => binary lacks the architecture information.

And indeed, the web reports don't include architecture information.
(and I don't need it personally). So, to start with I'll simplify the
problem and will try to come up with something that works but without
the architecture information. Fair enough?

Cheers,
--
intrigeri


Reply to: