Sent from my iPhone
> On May 4, 2025, at 11:50 AM, [email protected] wrote: > > Pocket <[email protected]> wrote: > >> >> Sent from my iPhone >> >>>> On May 4, 2025, at 9:21 AM, [email protected] wrote: >>> >>> Pocket <[email protected]> wrote: >>> >>>> >>>> I am building packages using makepkg for the raspberry pi 4 platform >>>> >>>> I changed the CFLAGS adding -march=armv8-a -mtune=cortex-a72 >>>> (makepkg.conf). >>>> >>>> I started to build all the packages that make up the "Building in a >>>> clean chroot" following the building in a claen chroot on the wiki. >>>> All when well. >>>> I will then build all the "base" package followed by all the packages I >>>> use on a "desktop" system. >>>> >>>> I would now like to make a custom repository for those packages and then >>>> have pacman install from there, eventually to remove the core extra etc >>>> repositories. >>>> >>>> I know how to create the custom repository (from the various wiki docs) >>>> using repo-add. I have a nginx web server on a remote raspberry pi and >>>> it will serve those packages >>>> >>>> from /etc/pacman.conf >>>> [custom] >>>> SigLevel = Optional TrustAll >>>> Server = http://www.home.arpa/Repository >>>> >>>> >>>> So my questions are as follows >>>> >>>> 1. How to get pacman to pull the packages from the custom >>>> repository first >>>> >>>> 2. I would like to sign the packages in the custom repository. >>>> >>>> I have looked at some of the information regarding signing >>>> packages(maybe missing some of them). It was totally confusing. >>>> I need guidance in the form of Step 1, step 2 etc. >>>> >>>> Is there such docs in existance? >>>> >>> >>> It could be >>> https://wiki.archlinux.org/title/Pacman/Package_signing#Adding_unofficial_keys >>> is what you are looking for. >>> >> >> I tried that and I either messed it up or I didn’t understand it as it >> failed to work. Pacman rejected it and when I try to sign the package using >> repo-add it failed as well. >> >> I am looking for a doc that shows the complete steps ie >> Create a key >> Add it to the Pacman keyring >> Then the rest of the steps >> >> Ie which key do I add to the keyring public or secret? >> >> I need a little hand holding on this one >> > > Other then asking > if you are able to install an unsiged package you built yourself with > pacman -U path/to/such/a/package > I can not help you in the details. > I do believe that using the script command to have a log for the shortest > session you can make to demostrate the 1st error message you got can help > both you and others find out the failure. > The prevoius message in this thread seeme to me rather detailed. But again, > having a log of the commands and their output can help if something fails. > You can also try asking in the forum. Again, I do believe logs are helpful. > Here is the steps gpg —full-gen-key gpg —export —armor —output public-key.asc pocket gpg —export-secret-keys —armor —output private-key.asc pocket The key id is pocket. For each key/attempt I imported each key into Pacman-key and signed with Pacman-key —lsign pocket Then I tried this. repo-add —sign —key pocket custom.db.tar.xz “file spec” It failed with the error invalid key/doesn’t know the key. I tried it with the public key, then I removed it from the key-chain and tried the private key. Both failed attempts failed I don’t have the exact error message as I am not at the raspberry pi at the moment
