[zypp-devel] Re: [zypp-commit] r8851 - /trunk/libzypp/zypp/sat/Solvable.cc
Hi Duncan (and others), On Thu, 21 Feb 2008, matz@svn.opensuse.org wrote:
Author: matz Date: Thu Feb 21 16:39:05 2008 New Revision: 8851
URL: http://svn.opensuse.org/viewcvs/zypp?rev=8851&view=rev Log: We need to add mediadir also in the non-trivial case.
This and the last commit to satsolver/tools/repo_rpmmd.c fix a bug in parsing of susetags repos which look like our full trees (i.e. no revisions in the rpm filename), unfortunately it necessarily breaks handling of the media file with already generated SOLV files from yum repos. You need to update those, once this libsatsolv and libzypp is submitted, or already now if you use SVN. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Michael Matz wrote:
This and the last commit to satsolver/tools/repo_rpmmd.c fix a bug in parsing of susetags repos which look like our full trees (i.e. no revisions in the rpm filename), unfortunately it necessarily breaks handling of the media file with already generated SOLV files from yum repos. You need to update those, once this libsatsolv and libzypp is submitted, or already now if you use SVN.
Ciao, Michael.
How can we tackle the problem of incompatible solv files? In the past the CacheStore removed the db if the version of the schema changed. Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Hi, On Thu, 21 Feb 2008, Duncan Mac-Vicar Prett wrote:
How can we tackle the problem of incompatible solv files?
Yes, this is a problem. We have a version in the SOLV file, but that's for the format itself, not for the content. We could introduce another field, which is incremented whenever the generators are changed in a meaningful way. Another possibility would be to (e.g.) store the SVN revision of libsatsolver with which libzypp was built in the .cookie file. Then when it reads the cookie and is itself built with a newer SVN revision of satsolver it could declare those SOLV files to be outdated. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Am Donnerstag, 21. Februar 2008 schrieb Michael Matz:
Hi,
On Thu, 21 Feb 2008, Duncan Mac-Vicar Prett wrote:
How can we tackle the problem of incompatible solv files?
Yes, this is a problem. We have a version in the SOLV file, but that's for the format itself, not for the content. We could introduce another field, which is incremented whenever the generators are changed in a meaningful way.
Another possibility would be to (e.g.) store the SVN revision of libsatsolver with which libzypp was built in the .cookie file. Then when it reads the cookie and is itself built with a newer SVN revision of satsolver it could declare those SOLV files to be outdated.
That's surely an engineer's solution :) This wouldn't work if we really wanted to have solv files on the media, because it would be almost impossible to guarantee that we always have the latest SVN checkout compiled on the hosts creating them. We need some manually increased number and have to hope that we do not have to increase them too often - and if we do that all hosts are updated. But CD makers will truely love satsolver quickly if you come and say "yeah, we fixed a typo in the man page, please reinstall". Greetings, Stephan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Hi, On Thu, 21 Feb 2008, Stephan Kulow wrote:
This wouldn't work if we really wanted to have solv files on the media, because it would be almost impossible to guarantee that we always have the latest SVN checkout compiled on the hosts creating them.
Good reasons.
We need some manually increased number and have to hope that we do not have to increase them too often
I agree. Question is, if that number would be in libzypp or in libsatsolver, or in the SOLV files. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (3)
-
Duncan Mac-Vicar Prett -
Michael Matz -
Stephan Kulow