Installation failed: Package Manager Error - help please

Hello, I’m new here, in fact, I haven’t even started using EndeavourOS xD

I’ve encountered an error while installing the OS. I’m installing on an old laptop.
I downloaded the ISO from a mirror from Germany, today. Did the sha512sum test, and came back OK.
I did use ventoy to write the iso file, for the first time - not sure maybe if I did some mistake there?
In the installation options, I chose to delete disk and set swap to ‘with hibernate’ (8GB; my computer has 4GB, but planning on adding 4GB soon) and I chose the Xfce4 DE.

I did try to find an answer by searching similar posts, but couldn’t find an answer…

This is the log file.
And a section from it that I’ve noticed keeps repeating:

2024-10-16 - 22:58:55 [6]: [PYTHON JOB]: "error: blueman: signature from \"Robin Candau <antiz@archlinux.org>\" is invalid" 
2024-10-16 - 22:58:55 [6]: [PYTHON JOB]: ":: File /var/cache/pacman/pkg/blueman-2.4.3-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature))." 
2024-10-16 - 22:58:55 [6]: [PYTHON JOB]: "Do you want to delete it? [Y/n] error: failed to commit transaction (invalid or corrupted package)" 
2024-10-16 - 22:58:55 [6]: [PYTHON JOB]: "" 
2024-10-16 - 22:58:55 [6]: [PYTHON JOB]: "Errors occurred, no packages were upgraded." 

I also noticed when I tried to install again, I think there were 3 partitions being created before, but now, if I choose Replace partition (Delete is gone, since it’s already deleted the partitions?), only 2 are being created - the main one in ext4? And 8GB for swap… Is this ok?

I would reaally appreciate your help here!
How should I proceed with the installation? And what went wrong? o.O

Hello @meoow ,
As for partitions create a GPT type Partition table an EFI (size 1GB) fat32 partition is also needed.
The program for it: gparted.
The second signature problem can be fixed by
eos-update --yay
if I am not mistaken.
(miau in my language)

Hello @eso ,and thank you for your reply.

Do I still need the partition if my BIOS doesn’t support UEFI mode? (cca. 12 yo ThinkPad)

Should I do the eos-update --yay while I’m booted from the USB?
Sorry, I’m really new to all of this…

(ha, same as my language - miau/mjav, however you like to write it x))

It should not be crucial
these signature errors occur at the end or when you do not update for months

It seems you are a little unlucky. It happened that a specific package (blueman) is not properly signed by the packager. This sometimes happens and is soon corrected, but during this automatic process, it blocks the whole installation, I am afraid.

If you can’t wait for one or a few days to be fixed, it needs some hacky staff to do. I suggest you just wait and try again later.

Darn :/… How will I know when a new release (or fix?) is out and available for download?
I will have to download a new ISO file, right?..

How did you know this was the issue, and not a bad USB maybe? (I have no idea if this is even a possible explanation for the error that I got, just asking myself what could have happened) Has this happened before?
Os there a link or something you can share that explains this behaviour?

(I’ve been reading the wiki and so far hadn’t come across something that would explain thiss error - the be fair I didn’t come far yet at all xD)
But I always ike to inform myself on what/how and why if I can and it would be nice to know what’s going on.

Hope I’m not asking too much, and someone can share a light for me a bit (:

I did find an artical on eDiscorery regarding signatures and keyrings issues, as well as a thread discussing a similar issue (I think?).

But do these apply also for the very first installation of EndeavourOS?

I thought those are meant if you encounter them during updates - after you’ve already successfully installed EndeavourOS?

There are two methods of installation. In simple words:
Off-line and on-line.
With off-line, you don’t use internet, so you install the CD/ISO system packages (whenever this was produced), onto the installation target.
With on-line, you use internet, and install remote packages (like when you update your system).

You have selected the on-line installation, so package signing matters, since you install remote (and the most current) packages.

If you do an off-line installation, it should not have this problem. You will need to update packages after installation, of course, where you will face the same issue. Until then, it may have been fixed, or you just wait.

untagging blueman will help.
log only shows this single package with an error for the signature… could be an issue with the sig file ot the key from the dev…

Just done a xfce4 install with blueman tagged (defaults) and i do not got the issue, so seems to be resolved already.

If not simple untag and go install the bluemean gui later…

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.