Similar to Bug 8833, we need to remove some packages from the repository before branching Mageia 4, packages that we don't intend to support or will not be able to support. Reproducible: Steps to Reproduce:
As was the case before, the firefox-aurora, firefox-beta, and firefox-beta-l10n packages are included in the list of ones needing to be deleted. As for chromium-browser-stable, somehow I've become the unofficial maintainer. I'd certainly like to see someone else adopt it if we're going to continue to support it. For iceape, spturtle has resumed maintaining the package, so we should be OK for now.
As mentioned in Bug 8833, libbsd and xombrero were candidates for removal. I'm sure there are other unmaintained packages that could be considered. As usual, any additional ones should be discussed on the -dev ml before removal.
In the category of packages we will not be able to support are the OpenStack related packages. This was discussed in the last QA meeting: http://meetbot.mageia.org/mageia-qa/2013/mageia-qa.2013-11-21-20.08.html As of right now, this list of packages includes: openstack-ceilometer openstack-cinder openstack-glance openstack-heat openstack-java-sdk openstack-keystone openstack-neutron openstack-nova openstack-packstack openstack-savanna openstack-swift openstack-swift-plugin-swift3 openstack-utils python-ceilometerclient python-cinderclient python-glanceclient python-heatclient python-keystoneclient python-neutronclient python-novaclient python-swiftclient perl-Net-OpenStack-Attack perl-Net-OpenStack-Compute
Blocks: (none) => 11704
livecd-tools needs to be dropped as asked in Bug 10259.
Depends on: (none) => 11973
transifex which is no more maintained and wasn't rebuilded since MGA2, cf bug 11973
What about MSN clients as aMSN, emesene, ... as MSN no longer exists?
CC: (none) => mageia
(In reply to Damien Lallement from comment #6) > What about MSN clients as aMSN, emesene, ... as MSN no longer exists? Indeed, we discussed getting rid of amsn for Mageia 3 because of that and that it has no hope of ever being ported to the newer farstream stuff, but decided to keep it for Mageia 3 since MSN wasn't dead yet, but now would be a good time to get rid of it.
We should also remove java-1.8.0-openjdk and ca-certificates: https://ml.mageia.org/l/arc/dev/2013-12/msg01048.html
(In reply to David Walser from comment #7) > (In reply to Damien Lallement from comment #6) > > What about MSN clients as aMSN, emesene, ... as MSN no longer exists? > > Indeed, we discussed getting rid of amsn for Mageia 3 because of that and > that it has no hope of ever being ported to the newer farstream stuff, but > decided to keep it for Mageia 3 since MSN wasn't dead yet, but now would be > a good time to get rid of it. About aMSN: If the decition point is regarding the msn service closure, I'd say keep it untill such point that Microsoft confirm that the service is permanently closed. if i remember correctly, it will remain operational untill mid march or so. I'm one of the users who still login to MSN (using pidgin but still) on a daily basis, and there are others doing the same. There is no need to remove a fully working client just because of a future service closure.
CC: (none) => cooker
(In reply to Johnny A. Solbu from comment #9) > (In reply to David Walser from comment #7) > > (In reply to Damien Lallement from comment #6) > > > What about MSN clients as aMSN, emesene, ... as MSN no longer exists? > > > > Indeed, we discussed getting rid of amsn for Mageia 3 because of that and > > that it has no hope of ever being ported to the newer farstream stuff, but > > decided to keep it for Mageia 3 since MSN wasn't dead yet, but now would be > > a good time to get rid of it. > > About aMSN: If the decition point is regarding the msn service closure, I'd > say keep it untill such point that Microsoft confirm that the service is > permanently closed. if i remember correctly, it will remain operational > untill mid march or so. I'm one of the users who still login to MSN (using > pidgin but still) on a daily basis, and there are others doing the same. > There is no need to remove a fully working client just because of a future > service closure. OK, thanks for the updated information. This can wait for Mageia 5 then.
freepops hasn't been updated upstream in 5 years, and is now refusing to compile due to problem with newer bison and lua versions, at least. It wasn't even successfully built in mga3 probably for the same reasons. Unless someone steps up to update it (in which case, he might as well take over upstream maintainership), there's not much choice but to drop it.
CC: (none) => dan
(In reply to David Walser from comment #3) > In the category of packages we will not be able to support are the OpenStack > related packages. This was discussed in the last QA meeting: > http://meetbot.mageia.org/mageia-qa/2013/mageia-qa.2013-11-21-20.08.html The meeting notes don't give any details, why shouldn't they be supported, especially the client libraries?
CC: (none) => pterjan
(In reply to Pascal Terjan from comment #12) > (In reply to David Walser from comment #3) > > In the category of packages we will not be able to support are the OpenStack > > related packages. This was discussed in the last QA meeting: > > http://meetbot.mageia.org/mageia-qa/2013/mageia-qa.2013-11-21-20.08.html > > The meeting notes don't give any details, why shouldn't they be supported, > especially the client libraries? A large, confusing set of packages, with no clear maintainer or history of consistent maintenance, and literally an average of one new security issue per week. I personally do not have the ability to support them, do not know of anyone who could and would willingly and successfully take full responsibility for them, nor have any idea how QA could handle such a high frequency of new issues. Why shouldn't they be supported IMO isn't the right question to ask here.
W.r.t. comment #11, Pascal has gotten freepops to compile again, so there's no pressing need to drop it any more. The question of whether we want to support a 5 year old appliction that parses data retrieved over untrusted network connections can be answered later :^)
Priority: Normal => release_blocker
openstack, livecd-tools, transifex, firefox-beta, java-1.8.0-openjdk and ca-certificates moved to ~schedbot/old lets see what breaks if anything... iirc the checks will run ~1 hour (http://check.mageia.org/cauldron/dependencies.html)
Status: NEW => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED