Hello, security:apparmor and security:apparmor:factory contain lots of old packages. I'd like to do some cleanup there if nobody objects. (I don't want to break anything, but OTOH I see lots of *very* old packages in those repos that probably nobody needs nowadays.) Note that I started maintaining the apparmor only half a year ago, therefore I might not know everything that still needs one of the packages. @Jeff: Please reply even if you agree with the cleanup - you as the former maintainer of the apparmor package probably know better if one of the packages is still needed somewhere. Let me first give you a short overview what is in the repos right now. Note that build is disabled for most packages - I added a note to all packages with build active. * Packages in security:apparmor: (repos: SLE_10 and factory) apparmor-admin_en [2] apparmorapplet-gnome - 0.9 [1] apparmor-dbus - 1.1 [1] (SLE_10 build enabled) libapparmor1 - 2.2 (SLE_10 build enabled) apparmor-profile-editor (only a broken link to factory) apparmor - 2.5.1 (the package in openSUSE:11.4:Update is newer) (SLE 11 SP2 also uses this version AFAIK) apparmor_2_6 - 2.6.1 * Packages in security:apparmor:factory (repos: 11.4, 12.1, factory, tumbleweed) apparmor-admin_en [2] (build active, but has a broken link) apache2-mod_apparmor - 2.0.2 tomcat_apparmor - 2.0.2 apparmor-dbus 2.3 [3] apparmor-parser - 2.3.1 [3] apparmor-profiles - 2.3 [3] apparmor-utils - 2.3 [3] libapparmor1 - 2.3 [3] pam_apparmor - 2.3 [3] apparmorapplet-gnome - 0.9 apparmor-profile-editor - 0.9.1 apparmor - 2.7.2 - that's the latest available packaged version (and building is of course enabled) If nobody objects within a week, I will - delete all pre-2.5 packages without any active repo - delete apparmor-admin_en - rename security:apparmor apparmor (2.5.1) to apparmor-2_5 and include the changes from 11.4:Update - move the active development to security:apparmor instead of security:apparmor:factory (and send a changedevelrequest for factory) - add 11.4, 12.1 and tumbleweed repos in security:apparmor - drop security:apparmor:factory (it will be empty after applying the changes above) In other words: after the cleanup, there will only be security:apparmor with the following packages: - apparmor-dbus 1.1 and libapparmor1 2.2 because they have the SLE_10 build enabled - apparmor_2.5 (with build disabled and the changes from 11.4:Update included) - apparmor_2.6 (with build disabled) - and of course the apparmor package (currently 2.7.2) with the latest version If you still need one of the packages I'm planning to delete, please speak up now - or remain silent forever ;-) Regards, Christian Boltz [1] I'm not sure to which apparmor versions those packages belong, however I'm quite sure they belong to version 2.4 or older (the apparmor-* packages were merged to a single apparmor package in 2.5) [2] outdated, now part of the Security Guide, and Karl Eichwalder wrote on opensuse-doc that I "probably can delete it" [3] the 2.3 / 2.3.1 packages were included in openSUSE 11.1, 11.2 and 11.3. Those releases are out of maintenance (with the exception of evergreen) and the packages in 11:3:Update are newer. Therefore I don't think it makes sense to keep them in security:apparmor. (If evergreen needs a fix for the apparmor packages, I'll of course help.) -- [18:16] <psankar> suseROCKs, sorry. didnt follow the conversation [...] [18:16] <suseROCKs> psankar, content is irrelevnt. You are simply here to nod yes to everyting I say with total and fervent agreement. [from #opensuse-project] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org