[Users] Repos/mirrors & 7.0.12

[Alexey Zilber]

My bad Jonathan, it looks like it was the same [Users] list.  I got
confused because I also get emails from bugs.openvz.org.   But yeah, looks
like it was all the same list.

-Alex

On Tue, Dec 17, 2019 at 10:54 AM Alexey Zilber <alexeyzilber at gmail.com>
wrote:

> Yeah, the dev list is a more active.  It's unfortunate, as I think ovz7 is
> a much stronger product than ovz6.  I hate cross-posting as well....
>
> -Alex
>
> On Tue, Dec 17, 2019 at 9:53 AM Jonathan Wright <jonathan at knownhost.com>
> wrote:
>
>> Thanks for this info!  This type of things seems like something worth of
>> updating the mailing list, but alas, communication has always been poor
>> when it comes to vz7.
>> On 12/16/2019 6:11 PM, Alexey Zilber wrote:
>>
>> Hi Jonathan,
>>
>>   I asked the same question on the dev list and this was the response
>> below.  Btw, if you're having issues, do a yum clean all.
>>
>> On 12/13/2019 06:07 AM, Alexey Zilber wrote:
>>
>> Hi All,
>>
>>    I notice that there is some funkiness going on with the repo
>> metadata.  A lot of times when I do a 'yum update' I get a message saying
>> my local cache is newer than the repo.   If I try to install a specific
>> package, I'll get errors like:
>>
>> debian-10.0-x86_64-ez-7.0.0-9. FAILED
>>
>>
>> http://mirror.zetup.net/openvz/virtuozzo/releases/7.0/x86_64/os/Packages/d/debian-10.0-x86_64-ez-7.0.0-9.vz7.noarch.rpm:
>> [Errno 14] HTTP Error 404 - Not Found           ]  0.0 B/s |    0
>> B  --:--:-- ETA
>>
>> Trying other mirror.
>>
>>
>> The package will never be found on any mirror.
>>
>>
>> The only way forward is to do a 'yum clean all', then everything is
>> fine... until a few weeks later, when the same thing happens again.  Are
>> the repos going through some major changes?
>>
>>
>> Hi Alexey,
>>
>> well, i can explain the current situation:
>> we've uploaded vz7 update 12 bits recently
>> https://download.openvz.org/virtuozzo/releases/openvz-7.0.12-283/
>> <https://download.openvz.org/virtuozzo/releases/openvz-7.0.12-283/x86_64/os/Packages/d/>
>>
>> but found a memory leak on vz7.116.6 kernel if running VMs and as OpenVZ
>> users cannot fix kernel issues via ReadyKernel patches,
>> we decided to roll back update 12 bits in repo until we have it fixed.
>>
>> This explains the situation with particular debian-10.0-x86_64-ez-7.0.0-9
>> rpm:
>> it presents in update 12 repo
>>
>> https://download.openvz.org/virtuozzo/releases/openvz-7.0.12-283/x86_64/os/Packages/d/
>>
>> but absents in update 11 repo
>>
>> https://download.openvz.org/virtuozzo/releases/openvz-7.0.11-235/x86_64/os/Packages/d/
>>
>>
>> But this is quite exceptional case, this does not explain why (if) it
>> happens to you often, the reason should be something else.
>>
>> Hope that helps.
>>
>> --
>> Best regards,
>>
>> Konstantin Khorenko,
>> Virtuozzo Linux Kernel Team
>>
>>
>>
>>
>> On Sun, Dec 15, 2019, 11:24 PM Jonathan Wright <jonathan at knownhost.com>
>> wrote:
>>
>>> Has this been pulled or what?  7.0.12 seems to be flip flopping and is
>>> in repos one day, and gone the next.
>>>
>>> Why is there constant uncertainty surrounding vz7 repos, random cases of
>>> repos dying for a week at a time, etc.  Who is running this show?
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at openvz.org
>>> https://lists.openvz.org/mailman/listinfo/users
>>>
>>
>> _______________________________________________
>> Users mailing listUsers at openvz.orghttps://lists.openvz.org/mailman/listinfo/users
>>
>> _______________________________________________
>> Users mailing list
>> Users at openvz.org
>> https://lists.openvz.org/mailman/listinfo/users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20191217/5dae4f3f/attachment-0001.html>