Difference between revisions of "Local repository"

From ArchWiki
Jump to: navigation, search
m (updated to pacman -Syu)
(18 intermediate revisions by 10 users not shown)
Line 1: Line 1:
[[Category:Management package (English)]]
+
[[Category:Package management]]
{{i18n|Local_repository_HOW-TO}}
+
[[es:Local repository]]
 +
[[ru:Local repository HOW-TO]]
 +
{{Expansion}}
 +
{{Merge|pacman Tips}}
 +
 
 
This document outlines one way to share Arch Linux packages across a LAN. A better way to do this would be to create a [[Custom local repository with ABS and gensync]] and make the repository available across the LAN using NFS or FTP. This document should be edited to describe this process in detail. For the time being, the original HOWTO is left intact below:
 
This document outlines one way to share Arch Linux packages across a LAN. A better way to do this would be to create a [[Custom local repository with ABS and gensync]] and make the repository available across the LAN using NFS or FTP. This document should be edited to describe this process in detail. For the time being, the original HOWTO is left intact below:
  
To share all your downloaded packages in your lan
+
== Introduction ==
Pros  save bandwidth, diskspace and time.
+
Sharing all of your downloaded packages to your LAN can save bandwidth, diskspace, and time.
"pacman -Sy"  will sync against our local repository
+
pacman -Syu
"pacman -S pkgname" try to download and install pkg from localserver if pkg not exist it download
+
Will sync against our local repository;
from the next server in the list /etc/pacman.conf and save pkg on localserver.
+
pacman -S pkgname  
"alsync" will update localserver db against ftp.archlinux.org
+
Will try to download and install a package from localserver. If the package does not exist it will download it from the next server in the list /etc/pacman.conf and save the package on localserver;
 
+
alsync
ex. for my network
+
Will update localserver database against ftp.archlinux.org.
serverip=192.168.14.3
+
network=192.168.14.0/255.255.255.0
+
adjust to yours
+
 
+
 
+
== on the server side ==
+
on your server create an nfs share readwrite for all pc on your lan
+
 
+
If you run Arch Linux on the server you can
+
  pacman -S rpcbind
+
  pacman -S nfs-utils
+
 
+
edit /etc/exports
+
add line
+
  /var/cache/pacman/pkg
+
  192.168.14.0/255.255.255.0 (rw,no_root_squash,sync)
+
add rpcbind, nfs-common and nfs-server to DAEMONS in /etc/rc.conf
+
 
+
run the followings:
+
  # /etc/rc.d/rpcbind start
+
  # /etc/rc.d/nfs-common start
+
  # /etc/rc.d/nfs-server start
+
check the nfsshare run "exportfs" on server.
+
 
+
=== Check hosts.allow and hosts.deny===
+
  
to work (very simple):
+
In example: for my network
 +
serverip=192.168.14.3
 +
network=192.168.14.0/255.255.255.0
 +
Adjust to your needs.
  
hosts.deny
+
== On the Server Side ==
ALL: ALL: DENY
+
Create an NFS share on the server hosting the packages.
  
hosts.allow
+
For detailed help on setting up an NFS server please see [[ NFS ]]
ALL: 192.168.14.
+
  
Explanation:  
+
* Add this line to /etc/exports:
 +
/var/cache/pacman/pkg 192.168.14.0/24(rw,no_subtree_check,nohide)
  
hosts.deny deny all connection that doesnt exist on hosts.allow.
+
* If you modify /etc/exports while the server is running, you must re-export them for changes to take effect:
hosts.allow allow connection from local network 192.168.14.0/255.255.255.0
+
# exportfs -ra
  
== on all clients==
+
== On all clients==
*rename /var/cache/pacman/pkg  to /var/cache/pacman/pkgorg
+
*Rename /var/cache/pacman/pkg  to /var/cache/pacman/pkgorg.
*create a new /var/cache/pacman/pkg and mount the nfs share there
+
*Create a new /var/cache/pacman/pkg and mount the nfs share there.
*run "mount -o rw,nolock 192.168.14.3:/var/cache/pacman/pkg /var/cache/pacman/pkg"
+
*Run:
*if the mount from command line does not work add this option "nfsvers=3"
+
mount -o rw,nolock 192.168.14.3:/var/cache/pacman/pkg /var/cache/pacman/pkg
or if you want it automount after the reboot,
+
*If the mount from command line does not work add this option:
add this line in /etc/fstab
+
nfsvers=3
 +
*Or, if you want it automount after the reboot, add this line in /etc/fstab:
 
   192.168.14.3:/var/cache/pacman/pkg /var/cache/pacman/pkg    nfs    rw,nolock
 
   192.168.14.3:/var/cache/pacman/pkg /var/cache/pacman/pkg    nfs    rw,nolock
*again if the mount does not work, try to add mount option nfsvers=3 to the fstab entry.
+
*Again, if the mount does not work, try to add mount option nfsvers=3 to the fstab entry.
*run "mount -a"
+
*Run:
*run "df" to check mount
+
mount -a
*move all your already fetched pkg from your clients
+
*Run:
 +
df
 +
To check mount.
 +
*Move all your already fetched pkg from your clients:
 
   /var/cache/pacman/pkgorg to /var/cache/pacman/pkg
 
   /var/cache/pacman/pkgorg to /var/cache/pacman/pkg
*edit /etc/pacman.conf and add this lines directly after the line
+
*Edit /etc/pacman.conf and add this lines directly after the line:
  
 
   {current}
 
   {current}
Line 74: Line 60:
 
I have skipped the step 3 because for me it works as i want already. I sync from each PC and all share the pacman cache.
 
I have skipped the step 3 because for me it works as i want already. I sync from each PC and all share the pacman cache.
  
== To sync your local repository v.s. archlinux.org==
+
== To sync your local repository against archlinux.org==
*"alsync" connects, login, and update your packages database on the local nfsserver
+
*"alsync" connects, logs in, and updates your packages database on the local nfs server
 
   pacman -S openssl
 
   pacman -S openssl
 
   pacman -S wget
 
   pacman -S wget
  
  
*create a file called /bin/alsync and put in this lines
+
*create a file called /bin/alsync and add these lines
 
   cd /var/cache/pacman/pkg
 
   cd /var/cache/pacman/pkg
 
   wget -N ftp://ftp.archlinux.org/current/'''.db.'''
 
   wget -N ftp://ftp.archlinux.org/current/'''.db.'''
Line 89: Line 75:
 
copy this file to your clients
 
copy this file to your clients
  
*to try run as root on first client
+
*Attempt to run as root on the first client
 
   alsync
 
   alsync
   pacman -Sy
+
   pacman -Syu
 
   pacman -S new-pkgname
 
   pacman -S new-pkgname
  
*move to next client and run
+
*Then move to the next client and run
   pacman -Sy
+
   pacman -Syu
 
   pacman -S new-pkgname
 
   pacman -S new-pkgname

Revision as of 06:09, 29 June 2013

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Local repository#)

Merge-arrows-2.pngThis article or section is a candidate for merging with pacman Tips.Merge-arrows-2.png

Notes: please use the second argument of the template to provide more detailed indications. (Discuss in Talk:Local repository#)

This document outlines one way to share Arch Linux packages across a LAN. A better way to do this would be to create a Custom local repository with ABS and gensync and make the repository available across the LAN using NFS or FTP. This document should be edited to describe this process in detail. For the time being, the original HOWTO is left intact below:

Introduction

Sharing all of your downloaded packages to your LAN can save bandwidth, diskspace, and time.

pacman -Syu

Will sync against our local repository;

pacman -S pkgname 

Will try to download and install a package from localserver. If the package does not exist it will download it from the next server in the list /etc/pacman.conf and save the package on localserver;

alsync

Will update localserver database against ftp.archlinux.org.

In example: for my network

serverip=192.168.14.3
network=192.168.14.0/255.255.255.0

Adjust to your needs.

On the Server Side

Create an NFS share on the server hosting the packages.

For detailed help on setting up an NFS server please see NFS

  • Add this line to /etc/exports:
/var/cache/pacman/pkg 192.168.14.0/24(rw,no_subtree_check,nohide)
  • If you modify /etc/exports while the server is running, you must re-export them for changes to take effect:
# exportfs -ra

On all clients

  • Rename /var/cache/pacman/pkg to /var/cache/pacman/pkgorg.
  • Create a new /var/cache/pacman/pkg and mount the nfs share there.
  • Run:
mount -o rw,nolock 192.168.14.3:/var/cache/pacman/pkg /var/cache/pacman/pkg
  • If the mount from command line does not work add this option:
nfsvers=3
  • Or, if you want it automount after the reboot, add this line in /etc/fstab:
 192.168.14.3:/var/cache/pacman/pkg /var/cache/pacman/pkg    nfs    rw,nolock
  • Again, if the mount does not work, try to add mount option nfsvers=3 to the fstab entry.
  • Run:
mount -a
  • Run:
df

To check mount.

  • Move all your already fetched pkg from your clients:
 /var/cache/pacman/pkgorg to /var/cache/pacman/pkg
  • Edit /etc/pacman.conf and add this lines directly after the line:
 {current}
 Server = file:///var/cache/pacman/pkg

and after

 {extra}
 Server = file:///var/cache/pacman/pkg

I have skipped the step 3 because for me it works as i want already. I sync from each PC and all share the pacman cache.

To sync your local repository against archlinux.org

  • "alsync" connects, logs in, and updates your packages database on the local nfs server
 pacman -S openssl
 pacman -S wget


  • create a file called /bin/alsync and add these lines
 cd /var/cache/pacman/pkg
 wget -N ftp://ftp.archlinux.org/current/.db.
 wget -N ftp://ftp.archlinux.org/extra/.db.
  • chmod 777 /bin/alsync

copy this file to your clients

  • Attempt to run as root on the first client
 alsync
 pacman -Syu
 pacman -S new-pkgname
  • Then move to the next client and run
 pacman -Syu
 pacman -S new-pkgname