Bug 292012

Summary:	dev-util/kdevelop-3.9.96 version bump
Product:	Gentoo Linux	Reporter:	Erik <esigra>
Component:	[OLD] Development	Assignee:	Gentoo KDE team <kde>
Status:	RESOLVED FIXED
Severity:	enhancement	Keywords:	InVCS
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	http://archives.gentoo.org/gentoo-user/msg_50a74de98ce3244e913a7d4b21becee9.xml
Whiteboard:	[kde-testing]
Package list:		Runtime testing required:	---

Description Erik 2009-11-05 20:12:48 UTC

dev-util/kdevelop-3.9.96 has been released but portage only has dev-util/kdevelop-3.9.95 as the newest version.

Reproducible: Always

Steps to Reproduce:

Comment 1 Dror Levin (RETIRED) gentoo-dev

2009-11-08 21:23:51 UTC

kdevelop is bumped in the kde-testing overlay, you are welcome to test it.

Comment 2 Erik 2009-11-12 11:22:40 UTC

(In reply to comment #1)
> kdevelop is bumped in the kde-testing overlay, you are welcome to test it.

What is the point of masking the stable version for removal, keeping an old crashy beta version available and hiding the new beta version with important bugfixes in an overlay?

Comment 3 Samuli Suominen (RETIRED) gentoo-dev

2009-11-12 11:25:18 UTC

(In reply to comment #2)
> crashy beta version available and hiding the new beta version with important
> bugfixes in an overlay?

I agree, it should have been bumped to Portage right away.

Comment 4 Nikita Melnichenko 2009-11-12 14:51:22 UTC

(In reply to comment #3)
> 
> I agree, it should have been bumped to Portage right away.
> 

Me too. There are arch keywords for masking "unstable" versions in the main tree. I think overlay is good for brand new packages (not versions!) that portage doesn't officially support. This is not the case.

Comment 5 Romain Perier (RETIRED) gentoo-dev

2009-11-12 16:05:01 UTC

moved in the main tree, closing

Comment 6 Erik 2009-11-16 12:33:36 UTC

Unfortunately the upgrade from beta5 to beta6 does not work well. There seems to be file collisions between kdeveplatform of beta6 and kdevelop beta5. This has been confirmed by 2 other users so far. See the URL. The reported workaround is to emerge -C kdevelop and then emerge kdevelop. I do not know that to do about it. The best that I can think of is to let kdevelop-3.9.95 block kdevplatform-3.9.96. Then the user will be informed immediately, instead of after building the whole package.