[bug#61620,v2] gnu: tlpui: Update to 1.5.0-6.

* gnu/packages/linux.scm (tlpui): Update to 1.5.0-6.
[arguments]<#:phases>: Rename USE-TLP-INPUT into SET-ABSOLUTE-LOCATIONS to
be more accurate.  Also add a new phase to skip failing tests.
[inputs]: Add LSBUTILS and PCIUTILS.
---
 gnu/packages/linux.scm | 42 ++++++++++++++++++++++++++++++++----------
 1 file changed, 32 insertions(+), 10 deletions(-)


base-commit: e36ac715518387686bd8165e1724ce54984ee0ee

Hi,

Nicolas Goaziou <mail@nicolasgoaziou.fr> skribis:

> * gnu/packages/linux.scm (tlpui): Update to 1.5.0-6.
> [arguments]<#:phases>: Rename USE-TLP-INPUT into SET-ABSOLUTE-LOCATIONS to
> be more accurate.  Also add a new phase to skip failing tests.
> [inputs]: Add LSBUTILS and PCIUTILS.

This triggers 3 build failures according to
<https://qa.guix.gnu.org/issue/61620>.  Could you take a look?

Thanks,
Ludo’.

Hello,

Ludovic Courtès <ludo@gnu.org> writes:

> This triggers 3 build failures according to
> <https://qa.guix.gnu.org/issue/61620>.  Could you take a look?

I don't understand where those failures are coming from. The tlpui
package has no dependents packages. Besides, following the "3" link
leads to a page that I cannot parse either.

Could someone explain where to look at?

Regards,

Hi Chris,

On Sat, 04 Mar 2023 at 19:33, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> This triggers 3 build failures according to
>> <https://qa.guix.gnu.org/issue/61620>.  Could you take a look?
>
> I don't understand where those failures are coming from. The tlpui
> package has no dependents packages. Besides, following the "3" link
> leads to a page that I cannot parse either.
>
> Could someone explain where to look at?

Clicking on the “3” from <https://qa.guix.gnu.org/issue/61620> leads to
<https://data.qa.guix.gnu.org/compare/package-derivations?base_commit=3809aa01a1287dbe5be90e7aa4407bf27a6467ed&target_commit=e2112b0d1e90a5a1f4f82bce8f8a29ab5fd86408&system=x86_64-linux&target=none&build_change=broken>
which displays nothing:

    Showing 0 new derivations across 0 packages

Moreover, clicking on
<https://data.qa.guix.gnu.org/compare/package-derivations?base_commit=3809aa01a1287dbe5be90e7aa4407bf27a6467ed&target_commit=e2112b0d1e90a5a1f4f82bce8f8a29ab5fd86408&system=x86_64-linux&target=none>
lists many that does not seem related to ’tlpui’.

This story looks like #61616.

<http://issues.guix.gnu.org/msgid/782ad1100907d6b1487103ab37faedf52abc9019.camel@gmail.com>

Since in both cases it seems an issue with Open MPI and it had been
fixed by 9ae4846c502b75867b83180bb65d422ff838e4e6, are these 3 failures
relevant?

Cheers,
simon

Simon Tournier <zimon.toutoune@gmail.com> writes:

> Clicking on the “3” from <https://qa.guix.gnu.org/issue/61620> leads to
> <https://data.qa.guix.gnu.org/compare/package-derivations?base_commit=3809aa01a1287dbe5be90e7aa4407bf27a6467ed&target_commit=e2112b0d1e90a5a1f4f82bce8f8a29ab5fd86408&system=x86_64-linux&target=none&build_change=broken>
> which displays nothing:
>
>     Showing 0 new derivations across 0 packages
>
> Moreover, clicking on
> <https://data.qa.guix.gnu.org/compare/package-derivations?base_commit=3809aa01a1287dbe5be90e7aa4407bf27a6467ed&target_commit=e2112b0d1e90a5a1f4f82bce8f8a29ab5fd86408&system=x86_64-linux&target=none>
> lists many that does not seem related to ’tlpui’.
>
> This story looks like #61616.
>
> <http://issues.guix.gnu.org/msgid/782ad1100907d6b1487103ab37faedf52abc9019.camel@gmail.com>
>
> Since in both cases it seems an issue with Open MPI and it had been
> fixed by 9ae4846c502b75867b83180bb65d422ff838e4e6, are these 3 failures
> relevant?

They are indeed not relevant to the changes here. They are detected as
changing because the derivations do change, but that's because they
change every time you try and compute them, rather than changing as a
result from the patches here.

I think a way to avoid this would be to have the error happen earlier,
so rather than waiting until you try and build the derivation, try to
detect that the builder script can't be read when it's being created. I
can't see an easy way to do that, but I've filed an issue about it:
https://issues.guix.gnu.org/62051

Hello,

Christopher Baines <mail@cbaines.net> writes:

> They are indeed not relevant to the changes here. They are detected as
> changing because the derivations do change, but that's because they
> change every time you try and compute them, rather than changing as a
> result from the patches here.
>
> I think a way to avoid this would be to have the error happen earlier,
> so rather than waiting until you try and build the derivation, try to
> detect that the builder script can't be read when it's being created. I
> can't see an easy way to do that, but I've filed an issue about it:
> https://issues.guix.gnu.org/62051

Meanwhile, this looks like a green flag for the current package, so
I applied the patch.

Thanks for the feedback.

Regards,

Hi Chris,,

On mer., 08 mars 2023 at 15:06, Christopher Baines <mail@cbaines.net> wrote:

> I think a way to avoid this would be to have the error happen earlier,
> so rather than waiting until you try and build the derivation, try to
> detect that the builder script can't be read when it's being created. I
> can't see an easy way to do that, but I've filed an issue about it:
> https://issues.guix.gnu.org/62051

Thanks for explaining.  Hum, indeed #62051 does not seem easy. :-)

Cheers,
simon