P. Kaluza wrote:
> Hi Thomas,
>
> Thomas Goirand wrote:
>> Hi,
>>
>> When I try to apply your patch that was made for 3.2.12 in the current
>> 3.2.21, it just fails:
>>
> [...]
>
>> Would you be able to provide a patch against version 3.2.21?
> yup, patch in dpatch format attached.
>
>
>> Is there one that exists already somewhere?
>>
> The last one in the debian's version of util-vserver is against yum
> 3.2.4. I didn't check upstream trunk, but it was trivial to forward-port
> anyway.
>
>> Also, why this has not been applied
>> in the upstream version, if this is a so old issue?
> I can only guess here:
> The issue the patch addresses, is that the yum caller can specify
> 'cachedir', 'persistdir' and 'logfile', but not where the 'lockfile'
> should go. yum alway prepends installroot to all of these, which, in the
> case of an externalized yum database, is certainly incorrect for at
> least some.
> However, the patch solves this by introducing a new interface for all
> these config parameters: the ability to prepend 'hostfs://' and
> 'chrootfs://' to all these config parameters.
> Yum upstream might have problems accepting this new interface, or they
> do not agree with the use case of externalized package databases at all.
>
> Maybe you can confirm this analysis with yum upstream.
>
> Ciao,
> Philipp
Hi,
I have added the patch in my local yum version on my laptop, and it
applies fine. Thanks for it. FYI: it's called
0005-vserver-interface.dpatch here (as I have already a
0004-logrotate-monthly.dpatch to fix the logrotate issue introduced by
the last upload):
--- yum-3.2.21.orig/etc/yum.logrotate 2009-04-01 10:47:14.000000000 +0800
+++ yum-3.2.21/etc/yum.logrotate 2009-04-01 10:48:05.000000000 +0800
@@ -2,6 +2,6 @@
missingok
notifempty
size 30k
- yearly
+ monthly
create 0600 root root
}
Now, I got another issue here, and not sure how to address it, maybe you
can help. During the build process, po/yum.pot is updated, when it is
not needed. Do you have any idea how I could make it so it's preserved
so my .diff.gz is not uselessly huge?
Once the above is fixed, I can upload again.
Thomas
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
