apt-move incompatible with non-debian repository structures
Luis M
lemsx1 at gmail.com
Thu Apr 20 04:35:11 UTC 2006
I thought apt-move was deprecated code. apt-move has many more flaws
than this. The easiest way to get a nice, pool-based repository that
supports multiple architectures on debian is using reprepro.
now, reprepro command line interface is meant to be use from a front
end (really) and not by mere mortals typing things. For this reason i
wrote a nice script called simply "repository" [1].
with my script you can setup your environment as follows:
/home/Shared/debian
/home/Shared/debian/incoming
/home/Shared/debian/conf/distributions
Where /home/Shared/debian will hold your repository and
/home/Shared/debian/pool will have all your packages.
The distributions files has entries like:
Origin: Kiskeyix
Label: Debian-All
Suite: debian-stable
Codename: stable
Version: 3.1
Architectures: i386 powerpc all source
Components: main non-free contrib
Description: Debian stable + non-free + contrib (some backported)
Update: debian security
#SignWith: yes
Origin: Kiskeyix
Label: Ubuntu-New
Suite: ubuntu-unstable
Codename: dapper
Version: 6.04
Architectures: i386 powerpc all source
Components: main multiverse restricted universe
UDebComponents: main multiverse restricted universe
Description: Ubuntu Dapper plus plus (and backported)
Update: ubuntu security
#SignWith: yes
Now, in order to add packages to the distribution you want, you simply
put the source files in /home/Shared/debian/incoming (.dsc,
.orig.tar..., .deb's for that package...) and run:
repository add
If you want to keep your own mirror of the official ubuntu/debian
packages, then you create $codename directories inside incoming:
/home/Shared/debian/incoming/dapper
/home/Shared/debian/incomng/unstable
and copy your .deb files into them, then add the files using the same command:
repository add
From time to time you might need to tidy things a bit, and you can simple do:
repository remove
Which will remove all unreference packages from your repo. (man reprepro).
If you need to remove only a few packages, then you can do:
repository remove package1 package2 ... packageN
and they will be removed from their respective $codename
repositories.... automagically ;-)
I hope that helps.
[1] http://lems.kiskeyix.org/toolbox/?f=repository
On 4/19/06, John Schofield <schoflist at dakim.com> wrote:
> Package: apt-move
> Version: 4.2.24-1.1ubuntu1
> Severity: important
>
>
> apt-move has the Debian main/restricted/non-us/etc. sections of the
> repository hard-coded into it.
>
> When using apt-move to duplicate an Ubuntu repository, only the main and
> restricted components are duplicated. Files from universe or multiverse
> are ignored.
>
> My expectation is that the components to be used/ignored would be a
> configurable option, rather than hard-coded in the program itself.
--
----)(-----
Luis Mondesi
*NIX Guru
Kiskeyix.org
"We think basically you watch television to turn your brain off, and
you work on your computer when you want to turn your brain on" --
Steve Jobs in an interview for MacWorld Magazine 2004-Feb
No .doc: http://www.gnu.org/philosophy/no-word-attachments.es.html
More information about the ubuntu-users
mailing list