Anyone else seeing a massive roll back on packages form kde4 factory desktop 11.2 today?
Yep, I am unsure what to think about that…
→ pastebinned output of ‘zypper dup’
78 packages to upgrade, 183 to downgrade, 2 to change vendor.
the renumbering on qt packages (libqt, etc) i picked up a day ago… with the rest remaining unchanged… now everything has been renumbered to a “downgraded” package number… not a clue as to why, maybe some kind soul will enlighten us…
no doubt some will not notice and just stay with old packages for a long time.
Packman had some similar version#-issues recently and they also had a good reason for it. Only I forgot which reason it was… I think it’s pretty safe to assume it’s not an actual rollback.
I’m going to run it, what the heck!
I asked in #opensuse-kde
There was deathly hush
Things to keep in mind:
Factory will push development here, so remember it will change big time - just when I don’t know.
I ran it. No harm done as far as I can tell. Just changed the version from “release 224” to “release 2.”
That’ll be it - Makes sense
Probably it’s because of this: [opensuse-packaging] Converting factory devel packages to branch](http://lists.opensuse.org/opensuse-packaging/2010-01/msg00091.html)
Release numbers in the openSUSE Build Service aren’t manually specified by packagers, it’s semi-automatic. Once you start to create links between projects this kind of things can happen.
Since I never studied how release numbers are assigned I don’t know how to fix this, or if it can be fixed at all. But I opened a bug 18 months ago: https://bugzilla.novell.com/420488. If someone thinks it’s a big problem… vote for it.
Me too, no problems until now, packman did the same, but my curiosity is still there to know the why:):shame:
The versioning numbers 224 were from the development stage
To bring it to release they all had to be altered.
and now to release 152 again???
the eldest one kdebase4-4.4.0-150.6.x86_64
the old one kdebase4-4.4.0-2.1.x86_64
the new one kdebase4-4.4.0-152.1.x86_64
why the jump start from 150.6 jump to 2.2 end then to 152.1???
my curiosity grows more and more :):sarcastic:
An openSUSE Build Service developer explains it in the bug report I linked. It was a bug, it has been fixed… bugzilla works, people should use it.
and the link?? ooookkkk I will look for it in bugzilla;) I didn’t know it could be seen as a bug 
I thought a rethinking, a lottery, try to guess the new number