Re: Intent to help with making packages cross-buildable
Hi Nilesh,
On Tue, Feb 16, 2021 at 04:12:20PM +0530, Nilesh Patra wrote:
> Well, yes. I was actually looking for _all_ the packages that aren't cross
> buildable and not just last ten - _also_ for packages which _do not_ have
> FTCBFS bugs filed.
Thus far I didn't find such a list useful for two reasons:
* It would contain more than half the archive. To put it another way:
If you randomly choose three packages, chances are very high that one
of them fails to cross build.
* Large sections of the archive cannot be cross built due to a small
number of issues affecting many packages.
* Sometimes packages ftcbfs temporarily or in architecture-specific
ways. Whether a package is broken is not as much a boolean as we
think.
So personally, I'v mainly sorted the archive by popcon and worked
downwards.
> This helps me in two ways:
>
> * Easier to find target packages to work on
> * I maintain several packages of which many are arch:any.
> Checking crossqa.d.n/sec/<packageneeded> is cumbersome to look up for each
> on of them and decide which of them don't cross build and then work on it.
> So getting a complete list could be nice.
>
> Let me know if it's already available and I missed it.
I see. Would your list be machine readable (json/yaml/...) or human
readable? Would it include satisfiability issues or only genuine ftcbfs?
Would it include bug numbers? Would it break down by maintainer? What
confidence (in terms of failures) is needed to be listed?
You can find the backing sql schema at
https://git.subdivi.de/?p=~helmut/crossqa.git;a=blob;f=schema.sql.
That'll tell you what is easily possible. We can attempt to acquire more
data from e.g. udd though.
Maybe you can sketch the desired output list here?
Helmut
Reply to: