[ATrpms-devel] are your repositories deltarpm compatible?
Valent Turkovic
valent.turkovic at gmail.com
Tue May 8 20:17:52 CEST 2007
Here is a little explanation of presto from Jonathan, I copy/pasted email
that is sent to fedora-developer mailing list:
> Fresh installation of Fedora Core 6
>
> Yum install deltarpm version 3.4-1 from Fedora Extras
> Install yum-presto version 0.2.9-1 from the wiki page
> wget the repo file into /etc/yum.repos.d. Verified that it is enabled
> Disable updates and extras repository. Core repo is left enabled.
>
> Here is the output:
>
> yum -d10 update
> Loading "presto" plugin
> Loading "installonlyn" plugin
> Running "config" handler for "presto" plugin
> Running "config" handler for "installonlyn" plugin
> Yum Version: 3.0
> COMMAND: yum -d10
> Installroot: /
> Setting up Update Process
> Setting up repositories
> Running "postreposetup" handler for "presto" plugin
> Setting up Presto
> Reading Presto metadata in from local files
> No drpms available for presto
> No drpms available for core
> Reading repository metadata in from local files
> Setting up Package Sacks
> Reading Local RPMDB
> Building updates object
> No Packages marked for Update/Obsoletion
>
> If I enable updates and extras yum does starts downloading header files.
>
> Rahul
Yeah, that's how it's supposed to work. The presto repository *only*
contains yum-presto, so you'll get automatic presto updates.
Do a normal yum update with updates and extras. If you want to
understand why (and aren't sick of extremely long explanations), read
on.
Presto works on top of whatever repositories it's been made for (at the
moment, only updates and extras). The idea is that livna could set up
their own presto repository and so could freshrpms. For people without
presto, it would work as a normal repository, while for people with
presto, it would be a presto-enhanced respository.
There are two ways to tell presto when there's a presto repository:
1. In the repository file (i.e. fedora-updates.repo), add a deltaurl
with the presto repository location (should work with deltamirrorlist as
well)
2. In the presto.conf file in /etc/yum/pluginconf.d. You make a section
with the name of the repository (much like yum does if you use a
centralized yum.conf) and add the deltaurl under it.
At the moment, we are using the second way because we don't want to mess
around with fedora-updates.repo and fedora-extras.repo on people's
systems. If a repository was using presto themselves, they would
release their .repo file using the first method.
Sorry I've been so long-winded.
Jonathan
On 5/8/07, Axel Thimm <Axel.Thimm at atrpms.net> wrote:
>
> On Thu, May 03, 2007 at 12:01:41PM +0200, Valent Turkovic wrote:
> > On 4/12/07, Axel Thimm <Axel.Thimm at atrpms.net> wrote:
> > > On Tue, Apr 10, 2007 at 09:56:33AM +0200, Valent Turkovic wrote:
> > > > I'm not aware if freshrpms and atrpms fedora repositories are
> deltarpm
> > > > compatible, so please tell me :)
> > >
> > > I don't really know what it takes to be compatible. Do you mean
> > > whether deltarpms are produced? Then no, there are none.
> > >
> > > If you mean whether there is a base package set to have as a starting
> > > diff for creating deltarpms, then there isn't one either. But since it
> > > works with Fedora Extras (which also has no release/updates structure
> > > like Core) it should work in theory with ATrpms, too.
> > >
> > > > Please help support this project so it goes through beta testing and
> > > > gets full support in Fedora 7. This project needs you!
> > >
> > > Currently ATrpms undergoes a lot of infrastructure changes, so it is
> > > not something I can put very high on the TODO list (I have currently
> > > no idea how involved that might be on both administration and run time
> > > resources). Since it's coming with F7 the earliest maybe it's better
> > > to wait until then and ping again?
> > >
> > >
> >
> > I'm pinging at your request :)
>
> You mean F7 started to ship deltarpms? I didn't mean the tools
> becoming available, but some big repo going through the maturing
> phase. :=)
>
> > I hope you got a lot of stuff done for Fedora 7 or you are near the
> > end of it. I'm just installing Fedora 7 test 4 on my other machine
> > while writing this mail.
> >
> > I can't tell you all you need to do to make ATrpms compatible with
> > deltarpm and yum-presto plugin but I asked Jonathan Dieter
> > <jdieter at gmail.com>, the mainainer of yum-presto plugin to join this
> > lists so he can provide some much needed input.
>
> OK. I still don't know the mechanics behind it, but it surely needs at
> least two rpms of the same package to create diffs (BTW does it
> create N*(N-1)/2 deltas if there are N old packages around?). The
> problem is that ATrpms' update scripts create the new repo in a
> speparate stage w/o looking at the old one and then swap it in
> place. Anyway, we'll see.
>
> > I can only say that deltarpm is a great idea, and works great in
> practice.
> >
> > It is maybe little less needed for repos like yours because people
> > mainly download from you, and update is secondary. But also when new
> > packages arrive then old packages will be updated.
> >
> > You should think how to enable more and more people to use linux, and
> > great repos like yours is a really big benefit to fedora users.
> >
> > There are millions of people with dialup and other slow connections on
> > our planet and updates for them are almost impossible. Or students
> > with laptops who can do some big installs when they are at ther
> > university but at home have also slow connection.
> >
> > For all of them bandwidth is scarce and deltarpms is a great solution
> > to that problem so please do all you can with implementing it.
> >
> > Thank you in advance.
> >
> > Valent from Croatia.
> >
>
> --
> Axel.Thimm at ATrpms.net
>
>
--
http://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241
Skype: valent.turkovic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070508/aa58b956/attachment.html
More information about the atrpms-devel
mailing list