Error executing build script #3

nkls commented 2023年12月20日 17:30:39 +01:00

I am encountering an error.

System:
Linux Mint 21.1

First I executed pEp-build/gnu-linux/GO_AS_ROOT as root.
Then I executed pEp-build/gnu-linux/pEp-build as non-root user

Error:
python3: can't open file '/home/nkls/usr-pep/bin/yml2proc': [Errno 2] No such file or directory
FATAL ERROR at step build: failed building libpEptransport

I also uploaded the complete stdout and stderr of the script.

Kind regards

nkls

:)

I am encountering an error. System: Linux Mint 21.1 First I executed pEp-build/gnu-linux/GO_AS_ROOT as root. Then I executed pEp-build/gnu-linux/pEp-build as non-root user Error: python3: can't open file '/home/nkls/usr-pep/bin/yml2proc': [Errno 2] No such file or directory FATAL ERROR at step build: failed building libpEptransport I also uploaded the complete stdout and stderr of the script. Kind regards nkls :)

nkls commented 2023年12月20日 17:46:33 +01:00

No description provided.

lucasaiu commented 2024年01月04日 12:00:01 +01:00

So, the problem is that yml2proc has not been installed to the right place. Which is surprising. I cannot reproduce your problem with Debian or with Mint 21.2.

So, the problem is that `yml2proc` has not been installed to the right place. Which is surprising. I cannot reproduce your problem with Debian or with Mint 21.2.

lucasaiu commented 2024年01月04日 12:00:51 +01:00

@nkls , if you still have your old directories from your bug report, could you please send me the output of this?

find ~ | grep yml2proc

(run as the user nkls)

Otherwise, please run the latest version of the build script and show me the output. I have made a few changes in the build script; they will not solve the problem, but the script will now be verbose in the part that failed for you.

@nkls , if you still have your old directories from your bug report, could you please send me the output of this? find ~ | grep yml2proc (run as the user `nkls`) Otherwise, please run the latest version of the build script and show me the output. I have made a few changes in the build script; they will not solve the problem, but the script will now be verbose in the part that failed for you.

lucasaiu commented 2024年01月05日 20:51:04 +01:00

This is a log from @nkls after the recent changes.

This is a log from @nkls after the recent changes.

lucasaiu commented 2024年01月05日 21:37:27 +01:00

<positron> This looks like a completely different failure
<positron> yml2proc now works, but I changed nothing
<positron> Now what fails to compile is pepenginesequoiabackend [20:54]
<positron> error: unused imports: `StringListIterMut`, `StringListIter`
<positron> --> src/pep.rs:24:5
<positron> I am puzzled
<positron> I will try to reproduce using your own exact distribution
<positron> Oh [20:55]
<positron> I think we should disable Werror or the equivalent of it
<positron> Because it is failing on something that looks completely harmless:
<positron> error: unused imports: `StringListIterMut`, `StringListIter`
<positron> --> src/pep.rs:24:5
<positron> Yes
<positron> = note: `-D unused-imports` implied by `-D warnings`
<positron> = help: to override `-D warnings` add `#[allow(unused_imports)]`
<positron> Okay, I will avoid that failure
<positron> I think I will fix everything on Monday [20:56]
<positron> Thanks a lot for now, nkls
<nkls> oh, the issue on codeberg! sure, sry :) [21:20]
<nkls> i hope that was helpful [21:23]
<positron> It certainly is [21:35]
ERC>

<positron> This looks like a completely different failure <positron> yml2proc now works, but I changed nothing <positron> Now what fails to compile is pepenginesequoiabackend [20:54] <positron> error: unused imports: `StringListIterMut`, `StringListIter` <positron> --> src/pep.rs:24:5 <positron> I am puzzled <positron> I will try to reproduce using your own exact distribution <positron> Oh [20:55] <positron> I think we should disable Werror or the equivalent of it <positron> Because it is failing on something that looks completely harmless: <positron> error: unused imports: `StringListIterMut`, `StringListIter` <positron> --> src/pep.rs:24:5 <positron> Yes <positron> = note: `-D unused-imports` implied by `-D warnings` <positron> = help: to override `-D warnings` add `#[allow(unused_imports)]` <positron> Okay, I will avoid that failure <positron> I think I will fix everything on Monday [20:56] <positron> Thanks a lot for now, nkls <nkls> oh, the issue on codeberg! sure, sry :) [21:20] <nkls> i hope that was helpful [21:23] <positron> It certainly is [21:35] ERC>

lucasaiu commented 2024年01月09日 12:08:03 +01:00

I made the build more forgiving. Please try again and tell me, @nkls .

What I have not done yet is building both versions of the Thunderbird addon, and installing the one matching the Thunderbird version which is detected. Doing that now.

I made the build more forgiving. Please try again and tell me, @nkls . What I have not done yet is building both versions of the Thunderbird addon, and installing the one matching the Thunderbird version which is detected. Doing that now.

lucasaiu commented 2024年01月09日 12:08:32 +01:00

@nkls, if you confirm that this work I will close this issue. The Thunderbird change belongs elsewhere.

@nkls, if you confirm that this work I will close this issue. The Thunderbird change belongs elsewhere.

lucasaiu commented 2024年01月09日 17:12:35 +01:00

And now I have also added support for "pEpForThunderbird legacy". I will not add a new codeberg issue for that unless you find problems, @nkls . Please tell me if it works well.

Regards.

And now I have also added support for "pEpForThunderbird legacy". I will not add a new codeberg issue for that unless you find problems, @nkls . Please tell me if it works well. Regards.

lucasaiu commented 2024年01月09日 22:58:31 +01:00

@nkls 's build failed.

@nkls 's build failed.

lucasaiu commented 2024年01月09日 23:01:05 +01:00

I should test on Mint 21.1.

I should test on Mint 21.1.

lucasaiu commented 2024年01月10日 12:44:43 +01:00

Another report from @nkls. This is some issue with the Python version (!)

Another report from @nkls. This is some issue with the Python version (!)

lucasaiu commented 2024年01月10日 19:03:47 +01:00

@nkls :
Hello nkls [19:01]
I think I am finished updating for today
It works well for me; the Python part should be more robust. I hope that it works on your side. Unfortunately I cannot reproduce the issue.

I fixed a few minor things; hoping it will be enough to solve the Python issue, that I cannot reproduce.

Tested on a few new systems as well, where everything works. The current list is:

• Luca Saiu's heavily customised distribution based on Debian unstable;
• Debian 11;
• Debian 12.4.0;
• Fedora 38, 'basic functionality' [not tested recently because of a VM issue, but it should still work];
• Fedora 39 workstation;
• Ubuntu 22.04.02-deskop, 'minimal installation';
• Mint 20.1 XFCE;
• Mint 21 XFCE;
• Mint 21.1 XFCE;
• Mint 21.2 XFCE.

@nkls : <positron> Hello nkls [19:01] <positron> I think I am finished updating for today <positron> It works well for me; the Python part should be more robust. I hope that it works on your side. Unfortunately I cannot reproduce the issue. I fixed a few minor things; hoping it will be enough to solve the Python issue, that I cannot reproduce. Tested on a few new systems as well, where everything works. The current list is: * Luca Saiu's heavily customised distribution based on Debian unstable; * Debian 11; * Debian 12.4.0; * Fedora 38, 'basic functionality' [not tested recently because of a VM issue, but it should still work]; * Fedora 39 workstation; * Ubuntu 22.04.02-deskop, 'minimal installation'; * Mint 20.1 XFCE; * Mint 21 XFCE; * Mint 21.1 XFCE; * Mint 21.2 XFCE.

lucasaiu commented 2024年01月15日 11:41:27 +01:00

@nkls : I have built with success on peppi. You can read what I did in ~positron/_GO. The configuration file ~positron/pEp-build-settings is particularly harmess, as it only defines core_no to 1 in order not to stress your computer, and nothing else.

So I would say that all the peppi problems are solved.

@nkls : I have built with success on `peppi`. You can read what I did in `~positron/_GO`. The configuration file `~positron/pEp-build-settings` is particularly harmess, as it only defines `core_no` to 1 in order not to stress your computer, and nothing else. So I would say that all the `peppi` problems are solved.

lucasaiu commented 2024年01月15日 13:05:51 +01:00

It works for me but fails for @nkls: see log_peppi-2024年05月15日--1.txt

It works for me but fails for @nkls: see `log_peppi-2024年05月15日--1.txt`

lucasaiu commented 2024年01月15日 14:54:59 +01:00

Fixed. This is a successful build log from peppi, for future reference.

Fixed. This is a successful build log from `peppi`, for future reference.