Re: 2 commits - createrepo/__init__.py createrepo/utils.py genpkgmetadata.py mergerepo.py modifyrepo.py
Anders F Björklund <[email protected]> Sat, 17 Sep 2011 09:56:45 +0200
| Newsgroups | gmane.linux.rpm.metadata |
|---|---|
| Message-ID | <[email protected]> |
seth vidal wrote:
>> What is the confusion ?
>
>
> You're creating a different set of repodata in primary/repomd.xml if
> nothing else.
Not sure I follow. It will either use gz or xz just like the new one,
the only difference is when you want compatibility mode and "both" ?
But you would have some problems anyway, if trying to read the lzma
compressed metadata as uncompressed (for instance). So seemed better ?
> Now - someone using suse/mandriva will find a problem with how it makes
> those and, when googling for where to report it, file a bug at
> createrepo.baseurl.org.
BTW: that tracker looks spammed ?
http://createrepo.baseurl.org/report/1
> that's what I mean by confusion. It's the same problem I have whenever
> there are patches into red hat or fedora yum/createrepo that don't make
> it into upstream. This is why we try to never have those.
I'm sure that you have compatibility and bugfix patches in fedora,
without forking and renaming ? If you're talking about backporting
features, that is slightly different... It was only done because it
was simpler than trying to port all of yum and keep it updated there.
The official standpoint is still preferring the "master" createrepo,
which in practice means that it is broken at runtime because of yum.
Using the "maintenance" createrepo was more about getting it running.
Eventually I'm sure that yum could be updated, so that it works again.
As far as I know, it's working in openSUSE even if kept at yum 3.2.25
and I think that yum 3.2.29 should be more or less fixed for Mandriva
and for FreeBSD (once deployed) which should allow createrepo 0.9.9.
I don't think anyone tried Solaris recently, but it had some issues...
> Do you see what I mean?
Yes, but not how it applies here.
I know that the --lzma was rejected upstream and replaced by --xz,
and I know that yum doesn't want to support all versions of rpm / os.
But one could still add xz compression to createrepo and sqlitecachec,
preferably upstream too, without having to call it something else ?
I don't really care, the patches are there if anyone wants them...
http://afb.users.sourceforge.net/repodata/patches/ ("maintenance")
--anders