[Yum-devel] Is "yum clean all" problem or repository issue? Newpackages could not show after "yum clean all"

[jigang.djg]

Two more suggestions for your problem:

(1):atrribute and name filter.

Is that only new packages can not be seen or installed from the client machine, but old ones are still available, and they are in the same reposity ?
    If is that, firstly, check the MODE, OWNER and GROUP of newly-added rpms, make sure that the MODE,OWNER and GROUP of new packages are the
same with old pks which are OK.
They, when attributes of rpm files are the same , but new packages are still unavailable, try to add new version of available packages to the reposity,
and check whether they can be updated, if it works and can be updated, It can be sure that the NAME of newly-added pkgs are filtered by some middle devices
(for exampel, a firewall) or they are ignored by some proxy programs such as haproxy, squid or nginx.

(2): http download directly, proxy ?

Is the downloading of new packages on reposity machine(not client machine) successful (when apache is running ok), such as "wget http://127.0.0.1/xxx/foo.rpm" ?
     if it fails, it proves that there may be some filters in the web server programs which  filters the downloading.

or it success, try to download the rpms from client machine with command like:
wget http://public_domain_name/xxx/foo.rpm

if the donwloading fails, then it is the fault of the network, check you network.

otherwise,  new rpms can be got from client machines, and the primary.xml.gz can not be found, it is probably that the "primary.xml.gz" was
filtered by some network devices or proxy programs.



________________________________
发件人： jupiter
发送时间： 2012-07-17  19:48:35
收件人： yum development
抄送：
主题： Re: [Yum-devel] Is "yum clean all" problem or repository issue? Newpackages could not show after "yum clean all"
I've just found that the repomd.xml in my client machine which cannot
see the new packages is actually the same repomd.xml in the private
repository machine which can see the new packages. In the private
repository machine I can see new packages in primary.xml.gz, but there
is no primary.xml.gz in the the client machine I can check with. Is
there anyway to check the primary.xml.gz in the client machine?
Thank you.
On 7/17/12, jupiter <jupiter.hce at gmail.com> wrote:
> Thanks James.
>
> I did "yum clean expire-cache", it did not work either. Yes, I had run
> createrepo to generate a fresh repomd.xml. In fact, I can see new
> packages when I did "yum list" in the private repository machine, that
> convinced me the repomd.xml is ok, but some cache out there to prevent
> other machines getting the new repomd.xml.
>
> Some one suggested me there could be some cache proxy to cause the
> problem, did you also suggest to check if there is cache proxy out
> there? How can I check cache proxy? My client machines have never set
> to use proxy. I did not expect that  cleaning yum cache could be this
> harder :-(.
>
> Thank you.
>
> Jupiter
>
> On 7/17/12, James Antill <james at fedoraproject.org> wrote:
>> On Sat, 2012-07-14 at 21:52 +1000, jupiter wrote:
>>> Hi,
>>>
>>> I built a private yum repository, it works and all packages can be
>>> shown from another machine yum list. but when I added more packages to
>>> the private yum repository, the yum list could not show the new one
>>> just added. I did "yum clean all", it did not help either.
>>>
>>> Since I can never test with public yum repositories if the "yum clean
>>> all" works to show packages which have just been added to the
>>> repository. Is it the problem for the "yum clean all", or it is the
>>> problem for my private yum repository? My question is how can I test
>>> the "yum clean all" to show packages just added from public yum
>>> repository? Or how can I fix the yum repository to show new packages?
>>
>>  You just need "yum clean expire-cache" to get a new version of
>> repomd.xml ... and everything will follow from that. You probably need
>> to generate a repomd.xml via. createrepo ... or maybe play with a
>> caching proxy in the middle?
>>
>>> BTW, the client machine yum.conf has already set keepcache=0.
>>
>>  This configuration is to do with packages, not repodata.
>>
>> _______________________________________________
>> Yum-devel mailing list
>> Yum-devel at lists.baseurl.org
>> http://lists.baseurl.org/mailman/listinfo/yum-devel
>>
>
_______________________________________________
Yum-devel mailing list
Yum-devel at lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel

________________________________

This email (including any attachments) is confidential and may be legally privileged. If you received this email in error, please delete it immediately and do not copy it or use it for any purpose or disclose its contents to any other person. Thank you.

本电邮(包括任何附件)可能含有机密资料并受法律保护。如您不是正确的收件人，请您立即删除本邮件。请不要将本电邮进行复制并用作任何其他用途、或透露本邮件之内容。谢谢。
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.baseurl.org/pipermail/yum-devel/attachments/20120717/9d3af147/attachment.html>