oS 12.1 Update Repository is not Up To Date

Hi,
This email from opensuse-update mailing list says there is an update available for sudo, which will install sudo-1.8.2-2.8.1. It is dated May-29 12:00 (probably CEST). I somehow recall that in the past when these emails appear, the update is indeed already available for download. But not this time:

# zypper lr -d suse-update
Alias          : suse-update
Name           : suse-update
URI            : http://download.opensuse.org/update/12.1
Enabled        : Yes
Priority       : 50
Auto-refresh   : On
Keep Packages  : Off
Type           : rpm-md
GPG Check      : On
GPG Key URI    :
Path Prefix    :
Parent Service :
MD Cache Path  : /var/cache/zypp/raw/suse-update
# zypper ref suse-update
Repository 'suse-update' is up to date.
Specified repositories have been refreshed.
# zypper lp
Loading repository data...
Reading installed packages...
No updates found.
# rpm -q sudo
sudo-1.8.2-2.5.1.x86_64

Also the modification dates on Index of /update/12.1 indicate that the last time it has been updated was 2h before this email has been sent (May-29 10:00). There have been some more updates since that and none of them have reached the update repo.

Does anyone know what is going on? Am I simply to impatient? Is the build service broken? Did the update URL change? I’m getting a bit nervous…
– Yarny

You must have a very, very security sensitive system that you are that greedy after security updates. Most of us simply wait until they are in the Update Repo. I personaly only look about once a week there.

But I looked now and see, on my 11.4 system there are update for sudo, php5, net-snmp and recommened ones for ntp and man-pages.
I guess your’a will now lso be there.

On 05/31/2012 11:16 AM, Yarny wrote:
> Does anyone know what is going on? Am I simply to impatient? Is the
> build service broken? Did the update URL change? I’m getting a bit
> nervous…

relax…

the output of these two commands will (i think) probably show you have
the update installed already…


sudo -V
cat /var/log/zypp/history | grep sudo | grep 2012

if not, then just do as the mailing list note says, this:


su -
zypper in -t patch openSUSE-2012-293

and it should flow…then if you do the first two commands i gave, you
should see that they have changed to the new version…


dd

On 2012-05-31 12:49, dd@home.dk wrote:
> On 05/31/2012 11:16 AM, Yarny wrote:
>> Does anyone know what is going on? Am I simply to impatient? Is the
>> build service broken? Did the update URL change? I’m getting a bit
>> nervous…
>
> relax…
>
> the output of these two commands will (i think) probably show you have the
> update installed already…
>
>


> sudo -V
> cat /var/log/zypp/history | grep sudo | grep 2012
> 

if not, then just do as the mailing list note says, this:


> su -
> zypper in -t patch openSUSE-2012-293
> 

which shows in my system:


> Telcontar:~ # cat /var/log/zypp/history | grep sudo | grep 2012
....
> 2012-05-30 12:06:21|install|sudo|1.7.6p2-0.13.1|x86_64||repo-update|8483fb687f66b426ad84a98fc6ec59346babbc4b2774c6b863f9f8048b670f67
> Telcontar:~

And the security post says:


- openSUSE 11.4 (i586 x86_64):

sudo-1.7.6p2-0.13.1
sudo-debuginfo-1.7.6p2-0.13.1
sudo-debugsource-1.7.6p2-0.13.1

So, I installed it yesterday.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Judging from your postings, I see that openSUSE 11.4’s update repo is up to date. Well, 12.1’s isn’t. Compare this timestamp

openSUSE:12.1:Update.repo 29-May-2012 10:36

with this timestamp

openSUSE:11.4:Update.repo 30-May-2012 16:32

. There was definitely no update of 12.1-update repo (since May-29 10:36).

No. “sudo -V” just gives me the upstream version number (1.8.2), and

# grep sudo /var/log/zypp/history
2012-05-23 06:40:50|install|sudo|1.8.2-2.5.1|x86_64||localrepo|027c49b3cafe4fbe6c97f9ddc00e5bdde4f8726
2012-05-23 06:42:27|install|yast2-sudo|2.21.1-2.1.1|noarch||localrepo|77279aef09fd3a1a8c9d0607ec0c3aa4
2012-05-23 07:27:26|install|gnome-sudoku|3.2.1-2.1.2|x86_64||suse|643cbe8d681fd7b6a1fdf6fef97185
2012-05-23 07:46:37|install|ksudoku|4.7.2-3.1.2|x86_64||suse|889ed2dac17df100ef653bf175460d6e5ee
# zypper in -t patch openSUSE-2012-293
Loading repository data...
Reading installed packages...
'openSUSE-2012-293' not found in package names. Trying capabilities.
No provider of 'patch:openSUSE-2012-293' found.
Resolving package dependencies...

Nothing to do.

This is apparently a problem in openSUSE’s build service. There are simply no updates which my machine might fetch.

Actually, I don’t read opensuse-update, but I find a compressed version of all security updates on LWN.net each day (e.g. this, where the sudo update was announced). When they appear at LWN.net, my machine already fetched them. But since May-29, this isn’t the case and the update repo is laging behind for at least 48h now. That’s why I concluded there is something wrong.
– Yarny

You have convinced me that there is something wrong with the 12.1 Update repo. Thing is now, where to report this.

BTW, my remark about you being very security concious is not to be take negative. I was only a bit amazed because such a security consiousness is something I see more often connected to a professional environment using SLES/SLED or the like.

On 05/31/2012 02:46 PM, Yarny wrote:
> there is something wrong

the folks who care for and feed the update repo are not here in these
forums…please catch their attention using the contact info provided
here <http://en.opensuse.org/openSUSE:Services_help>, which gives:

email admin@opensuse.org

or use Bugzilla with the Product openSUSE.org and the Component Download
Infrastructure
<https://bugzilla.novell.com/enter_bug.cgi?classification=7340&product=openSUSE.org&submit=Use+This+Product&component=Download%20Infrastructure>


dd

Done so.

Thanks for your remarks. In such cases, I prefer to consult the forum first, since there might be some announcement (“12.1 updates suspended for a week due to sudden server illness”) somewhere which I didn’t see and I want to be fairly sure about my bug reports. That’s how it is now.

Wasn’t really taken negative, it just wanted to justify my conclusion that something is wrong. In fact I feel flattered.
– Yarny

O yes, that is a save way to walk. I would have done the same.

And thanks to DD for providing he contacts I was to lazy to search for.

For the record: It’s got fixed (or fixed itself), and updates are now avaliable as usual. I closed my bug report. – Y

Thanks for reporting back.