Re: Synchronizing local debian repository
jarek <jarek@poczta.srv.pl> writes:
> Hello!
>
> I don't know it this list i suitable from my question, so if there is a
> better list, let me know.
Wrong list. Not sure where it should go best (debian-user?) so i will
just answere here.
> For a long time, I'm looking for solution to synchronize local debian
> repository which is not connected to internet.
> At the moment I'm doing this the following way:
> 1. With apt-mirror synchronize local repository on computer connected
> to internet.
> 2. From apt-mirror log get list of changed packages.
> 3. Transfer changed packages to DVD-R.
> 4. Merge changed files with second repository not connect to internet.
> It works, but is complicated and prone to various errors, i.e. if
> apt-mirror will fail in middle of work.
> Now I have idea, to create a script, which will fetch packages with
> MTIME greater then last fetch (with lets say 1 day gap).
> Is this a good idea ? I've compared dates from few mirrors and it looks
> promising, but I didn't found any official info about this.
> If there is other, known way to do this, I'll be happy to hear about
> this.
> From my point of view it would be great if there will be some number
> telling in which order packages were added to repository, i.e:
> Package: libc-bin
> Priority: required
> Section: libs
> Installed-Size: 1636
> Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
> Architecture: amd64
> Source: eglibc
> Version: 2.11.2-10
> Repository-revision: 23423
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> It should work similar to revision number in svn. The other solution is
> to have build date in each package, i.e.:
>
> Package: libc-bin
> Priority: required
> Section: libs
> Installed-Size: 1636
> Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
> Architecture: amd64
> Source: eglibc
> Version: 2.11.2-10
> Created: 23.01.2011 21:17:00
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> best regards
> Jarek
Each package has a version and name+version(+arch) is unique. The
version is also monotone rising but that is irelevant. The packages
filename is also unqiue. So you really don't need a revision or
timestamp.
I think what you are looking for is apt-zip. Or at least apt-zip should
be a good start. You should not rely on the MTIME of files. Use the
Packages file to compare what you non-networks system has with what it
should have and fetch the difference.
MfG
Goswin
Reply to: