same for chromium

CC: (none) => dmorganec, thierry.vignaud
Summary: remove firefox-aurora, firefox-beta, firefox-beta-l10n for mga 3 => remove firefox-aurora, firefox-beta, firefox-beta-l10n, chromium-browser-unstable, chromium-browser-beta for mga 3
Source RPM: firefox-aurora, firefox-beta, firefox-beta-l10n => firefox-aurora, firefox-beta, firefox-beta-l10n, chromium-browser-unstable, chromium-browser-beta

Just them to an exclude list when syncing cauldron to mga3
As for chromium*, they're already obsoleted by chromium-browser-stable.

(In reply to Thierry Vignaud from comment #2)
> Just them to an exclude list when syncing cauldron to mga3

oh ok didn't know it was possible

> As for chromium*, they're already obsoleted by chromium-browser-stable.

Sophie is not agree :p

:q chromium-browser
19:29 <Sophie> rpm name matching `chromium-browser' in (Mageia, cauldron, *) :
19:29 <Sophie> chromium-browser, chromium-browser-beta, 
               chromium-browser-stable, chromium-browser-unstable

CC: (none) => sysadmin-bugs
Component: RPM Packages => Release (media or process)
Assignee: bugsquad => sysadmin-bugs

I could have swear I had seen it in chromium-browser-stable changelog but rpm doesn't agree with me :-(

for tainted. For core/release i asked a push.

As I said on the -dev ml, as we already got rid of bumblebee, we still have a library that was imported for bumblebee, libbsd, which we should also get rid of.  It's only used by one other package, which wasn't in Mageia 2, was imported during this cycle, and has already been dropped and has no maintainer, and it seems nobody's interested in it, so we should remove xombrero too.

https://ml.mageia.org/l/arc/dev/2013-05/msg00305.html

CC: (none) => luigiwalser

plop, seems it was missed, can it still be done ?

firefox-aurora, firefox-beta, firefox-beta-l10n packages have been removed from Mageia 3 repository.

Status: NEW => RESOLVED
CC: (none) => boklm
Resolution: (none) => FIXED

Are we going to do anything about libbsd and xombrero?