https://bugzilla.novell.com/show_bug.cgi?id=470570 Summary: Krusader packet name conflict Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dendy_ua@bk.ru QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-2.5 Firefox/3.0.5 Starting with developing Krusader 2, package for it appeared in openSUSE repositories under name krusader-1.99*. The previous KDE3 based version has name krusader-1.90* and accessible from openSUSE repositories too. The problem is that short packet name for these applications is the same: krusader So newer KDE4 based version completely hides previous KDE3 based. This is not a good practice, because these two applications are not the same technically, just in mind. This would be acceptable if Krusader 2 had full set of futures of Krusader 1.90 and was stable. But it not. It still contains so many bugs, it is very slow. It is now even release yet. So I don't when it will be ready to use for Krusader users. I think I will stay with Krusader 1.90 for a couple years. openSUSE repositories should not hide previous versions of Krusader, and should move Krusader 2 into, for example: kde4-krusader to avoid conflicting with Krusader 1.90. Using package protecting in Zypper is not a case because: 1. Bugfixes could still appears for the Krusader 1.90 2. Protecting not works in Yast (at least in Qt4 version of Yast) Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.