Arch Linux

brando56894

Member

From: NYC

Registered: 2008-08-03

Posts: 681

Archiso and Custom Pacman Repository

TL;DR after reviewing this before posting it I noticed that the pacman.conf that is sourced is locate in work/pacman.conf and not ./pacman.conf so what's the point of ./pacman.conf? I added my custom repo there and it didn't pick it up, I had to add it to work/pacman.conf for archiso to sync my custom repo.

I'm in the process of learning how to use Archiso and everything seems to go well during the building process until it gets to local packages that I have built from the AUR and have in a local repository. From the output of the archiso script it looks like my repository isn't included in the pacman.conf even though I added it.

My custom repository is located at /etc/pacman.d/custom-repo and I created it by executing repo-add /etc/pacman.d/custom-repo/custom.db.tar.gz /etc/pacman.d/custom-repo/* which gave the following output:

[root@arch /etc/pacman.d/custom-repo]# repo-add /etc/pacman.d/custom-repo/custom.db.tar.gz /etc/pacman.d/custom-repo/*
==> Adding package '/etc/pacman.d/custom-repo/android-tools-4.2.2_r1.2-1-x86_64.pkg.tar.xz'
  -> Computing checksums...
  -> Creating 'desc' db entry...
  -> Creating 'depends' db entry...
==> Adding package '/etc/pacman.d/custom-repo/android-udev-52.3b7ebf2-1-any.pkg.tar.xz'
  -> Computing checksums...
  -> Creating 'desc' db entry...
  -> Creating 'depends' db entry...
==> Adding package '/etc/pacman.d/custom-repo/heimdall-git-f956190-1-x86_64.pkg.tar.xz'
  -> Computing checksums...
  -> Creating 'desc' db entry...
  -> Creating 'depends' db entry...
==> Adding package '/etc/pacman.d/custom-repo/package-query-1.2-2-x86_64.pkg.tar.xz'
  -> Computing checksums...
  -> Creating 'desc' db entry...
  -> Creating 'depends' db entry...
==> Adding package '/etc/pacman.d/custom-repo/yaourt-1.3-1-any.pkg.tar.xz'
  -> Computing checksums...
  -> Creating 'desc' db entry...
  -> Creating 'depends' db entry...
==> Creating updated database file '/etc/pacman.d/custom-repo/custom.db.tar.gz'

In my /etc/pacman.conf I have the repo added as follows and it syncs just fine when I issue pacman -Syy so I know that it works

[custom]
Server = file:///etc/pacman.d/custom-repo

Now to get Archiso to pull from it I should add the repo location to /root/livecd/pacman.conf, correct?

During building pacman syncs but my repo isn't listed, what am I missing here?

[root@arch ~/livecd]# cls;./build.sh -v

[mkarchiso] INFO: Configuration settings
[mkarchiso] INFO:                   Command:   install
[mkarchiso] INFO:              Architecture:   i686
[mkarchiso] INFO:         Working directory:   work/i686
[mkarchiso] INFO:    Installation directory:   arch
[mkarchiso] INFO:        Pacman config file:   work/pacman.conf
[mkarchiso] INFO:                  Packages:   arch-install-scripts b43-fwcutter btrfs-progs crda darkhttpd ddrescue dhclient dialog dmraid dnsmasq dnsutils dosfstools elinks ethtool f2fs-tools fsarchiver gnu-netcat gpm gptfdisk grml-zsh-config grub haveged hdparm ipw2100-fw ipw2200-fw irssi lftp linux-atm mc mtools nfs-utils nilfs-utils nmap ntfs-3g ntp openconnect openssh openvpn partclone parted partimage pptpclient ppp rfkill rp-pppoe rsync smartmontools speedtouch sudo tcpdump testdisk usb_modeswitch vpnc wget wireless_tools wpa_actiond wvdial xl2tpd zd1211-firmware zsh xorg-server xorg-xinit xorg-server-utils xorg-drivers xorg-xkill yakuake kdebase alsa-utils wicd android-tools android-udev yaourt base-devel bash-completion dvd+rw-tools filezilla firefox gparted heimdall htop k3b mlocate samba tigervnc unrar unzip ttf-dejavu networkmanager cdrdao lsof strace gpart exfat-utils kwebkitpart icoutils kdegraphics-svgpart kdegraphics-thumbnailers kdemultimediaffmpegthumbs kdemultimedia-mplayerthumbs gdb rarian libva-vdpau-driver

[mkarchiso] INFO: Installing packages to 'work/i686/root-image/'...
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: There are 34 members in group xorg-drivers:
:: Repository extra
   1) xf86-input-evdev  2) xf86-input-joystick  3) xf86-input-keyboard  4) xf86-input-mouse  5) xf86-input-synaptics  6) xf86-input-vmmouse
   7) xf86-input-void  8) xf86-video-ark  9) xf86-video-ast  10) xf86-video-ati  11) xf86-video-cirrus  12) xf86-video-dummy  13) xf86-video-fbdev
   14) xf86-video-geode  15) xf86-video-glint  16) xf86-video-i128  17) xf86-video-intel  18) xf86-video-mach64  19) xf86-video-mga
   20) xf86-video-modesetting  21) xf86-video-neomagic  22) xf86-video-nouveau  23) xf86-video-nv  24) xf86-video-openchrome  25) xf86-video-r128
   26) xf86-video-savage  27) xf86-video-siliconmotion  28) xf86-video-sis  29) xf86-video-tdfx  30) xf86-video-trident  31) xf86-video-v4l
   32) xf86-video-vesa  33) xf86-video-vmware  34) xf86-video-voodoo

Enter a selection (default=all): 
:: There are 11 members in group kdebase:
:: Repository extra
   1) kde-wallpapers  2) kdebase-dolphin  3) kdebase-kdepasswd  4) kdebase-kdialog  5) kdebase-keditbookmarks  6) kdebase-kfind  7) kdebase-konq-plugins
   8) kdebase-konqueror  9) kdebase-konsole  10) kdebase-kwrite  11) kdebase-plasma

Enter a selection (default=all): 
error: target not found: android-tools
error: target not found: android-udev
error: target not found: yaourt
error: target not found: heimdall

hachir86

Member

Registered: 2013-09-12

Posts: 3

Re: Archiso and Custom Pacman Repository

Not sure if you have figured this out yet or not but I ran into your post because I am also having an issue with archiso and a custom repo.

In your case, you're on the right track... the "work" folder gets created when you start a build. Go to the folder that contains your "build.sh" file, in my case it's "~/archlive/releng/" - in this folder you should have a copy of pacman.conf.  The very first time you start a build, the work folder gets created and the ~/archlive/releng/pacman.conf file gets copied into the work folder.

Unfortunately, if you've already started a build and it fails for whatever reason, then your "work" folder already exists and it doesn't get updated the next time you try running your build. So, if you edit "~/archlive/releng/pacman.conf" then the same file in the "work" folder won't be updated with your changes when you start the build again.

For this reason, I personally have just gotten into the habit of deleting the work folder. That way everything starts fresh. So, either delete the work folder, or make sure that the two pacman.conf files in the above mentioned locations are the same then retry your build.

hachir86

Member

Registered: 2013-09-12

Posts: 3

Re: Archiso and Custom Pacman Repository

The problem I am having is that my build keeps failing because it can't locate the right architecture for a package I want to install from the AUR.

I've added the package name to packages.both, verified the package is available for both x86 and x64 and I've also checked the PKGBUILD file and everything looks fine.

However, when I run my build I keeps getting errors about an incorrect package architecture. At first, my build would almost immediately fail with this error, so I tried creating a custom repo with both x86 and x64 versions of the pkg and now it goes through the entire x86 build but as soon as the build.sh switches over to the x64 build then again I get the package architecture error.

From what I can tell the build.sh script goes through the build of the x86 iso and downloads all the i686 packages. Then, it switches over to x64 and downloads all the x86_64 packages. This works fine except for this one pkg from the AUR. So, can anyone tell me how can I get it to see that there are two distinct packages for each architecture??

Thank you for any suggestions.

brando56894

Member

From: NYC

Registered: 2008-08-03

Posts: 681

Re: Archiso and Custom Pacman Repository

I delete the work folder usually after something breaks or when I start a new build. I couldn't figure out what the issue was so I just edited the one under work and deleted all the files except for pacman.conf. I ran out of space in my VM so I tried to grow the disk image but that ended up corrupting it and I had to start over, luckily I had zipped up all my custom files before this happened so I don't have to add all my custom stuff back in manually.

After doing a fresh Arch Install the problem that I'm having now is that after creating my custom repo pacman says that it can't find the database file when I run build.sh, yet I know it works just fine because when I run pacman -Sy in the normal arch install it updates and installs the packages just fine. So confused.

I was/am having the same problem that you're encountering, is the package android-tools by any chance?

hachir86

Member

Registered: 2013-09-12

Posts: 3

Re: Archiso and Custom Pacman Repository

No it wasn't with android-tools but I got mine to work finally. Try this:

I assume you already have the pkg built and everything. If not then you'll need to look into makepkg first.
If you have the pkg ready though then make a folder, for example /home/user/AURpkgs and copy all the *.pkg.tar.xz files into it.

Then, when you create your custom repo using 'repo-add' make sure it's something like this:

repo-add /home/user/AURpkgs/myrepo.db.tar.gz /home/usr/AURpkgs/*.pkg.tar.xz

This way your repo db file is in the same folder as your AUR package(s).

Lastly of course, you will also need to make sure that you add this repo to pacman.conf. Notice that the name of the db.tar.gz file in the command above needs to be the same as the repo name you add to pacman.conf (in brackets) below:

[myrepo]
SigLevel = Optional TrustAll
Server = File:///home/user/AURpkgs

Good luck.

halimbo

Member

From: Krefeld, Germany

Registered: 2013-10-23

Posts: 74

Re: Archiso and Custom Pacman Repository

I ran into the same problems.
I now have different repos and all of them are added right, but i still get the package architecture error in the second run for the x86_64 packages.

halimbo

Member

From: Krefeld, Germany

Registered: 2013-10-23

Posts: 74

Re: Archiso and Custom Pacman Repository

Yaaay, I figured it out! *___*

You have to trick with the "arch" variable in the pacman.conf file.

I did it with the following directory structure:

# for i686
~/repository/i686/customrepo.db.tar.gz and your packages

# for x86_64
~/repository/x86_64/customrepo.db.tar.gz and your other packages

And in pacman.conf:

[customrepo]
SigLevel = Optional TrustAll
Server = file:///media/halim_storage/Repositories/customrepo/$arch

hope that makes it clear, i don't wish anyone this kind of struggle

i somebody should care about the wiki page, i'll try to do this in the next few days, if no native-english user wants to do it.
there are some other things to mention. too:
https://bbs.archlinux.org/viewtopic.php?id=177650