Description of problem: Version-Release number of selected component (if applicable): k3b 2.0.2 2.mga1 There is no transcode available for k3b in mageia 1, but it is developped in cauldron ---> http://88.191.121.20/madb/mageia/index.php/package/list/distrelease/1/application/0/arch/2/source/0?t_search=transcode
It adds functionalities to k3b but the bug report concerns directly the transcode package, so I adapted the title.
CC: (none) => stormiSummary: k3b transcode => package request (Mageia 1) : transcodeSource RPM: (none) => transcode
*** Bug 2242 has been marked as a duplicate of this bug. ***
CC: (none) => goy_ben_regesh
(In reply to comment #2) > *** Bug 2242 has been marked as a duplicate of this bug. *** Sorry I should have searched before adding. Best regards
Keywords: (none) => BackportComponent: New RPM package request => RPM PackagesSummary: package request (Mageia 1) : transcode => backport request (Mageia 1) : transcode
it's more an "update request" than a backport request because it exists in Mandriva 2010.2 (from plf) nevertheless there a little problem with it : it was built with faac in plf... and may not built this way in Mageia1 => loosing some features when upgrading (little regression) see bug 2833
CC: (none) => philippedidier
PLF != mdv2010.1/2
CC: (none) => sander.lepik
Blocks: (none) => 2929
(In reply to comment #4) > it's more an "update request" than a backport request because it exists in > Mandriva 2010.2 (from plf) > > nevertheless there a little problem with it : it was built with faac in plf... > and may not built this way in Mageia1 => loosing some features when upgrading > (little regression) > see bug 2833 removing the backport keyword and cc'ing the committers that weren't in the cc of this report, yet
Keywords: Backport => (none)CC: (none) => fundawang, marja11, oliver.bgrComponent: RPM Packages => New RPM package requestSummary: backport request (Mageia 1) : transcode => transcode, A linux video stream processing utilityWhiteboard: (none) => Mdv, cauldron
plf2010.1 != mdv2010.1 but plf ~ mga.tainted So what to do? And telling the users to wait for backports is not a solution because as it is, they won't be available in the next several million years :/
(In reply to comment #7) > plf2010.1 != mdv2010.1 > but > plf ~ mga.tainted > > So what to do? > > And telling the users to wait for backports is not a solution because as it is, > they won't be available in the next several million years :/ Are you saying that the rule that it is valid to package mdv 2010.x packages for Mageia, doesn't apply to plf packages, so you can't just package it for 1 tainted and push it to 1/tainted/updates? Are you sure the following doesn't apply to plf? https://wiki.mageia.org/en/Mgarepo#The_package_doesn.27t_exist_yet_in_Mageia_1 I think many Mdv plf packages got packaged for Mga tainted before, and it'll probably happen again: there are a lot of package request where I put Mdv on the whiteboard to indicate the package is in Mdv 2010.x, regardless of which repositories they are in.
I would oush it, but see comment #5. And the wiki page you cite doesn't say a word about plf, sop it's not clear.
I would push it, but see comment #5. And the wiki page you cite doesn't say a word about plf, so it's not clear.
Yes : the wiki is not clear about it but indeed lots of packages from plf repo and lots of packages specially built for plf repo have been already imported in mga.tainted repo... Transcode causes a particular problem : it was built with faac in plf !!! And faac is a ugly thing for mageia people : see comment #4 and the closed bug report : bug 2833
Blocks: (none) => 2833
you may look at bug 2960 too ! transcode was in svn since june but never provided to mageia 1 ... it's in cauldron-tainted , built without BuildRequire faac-devel the spec of transcode for mageia respects the strict policy of tainted repo (only free licence but with patent problems in some countries... )
Blocks: 2833 => (none)Depends on: (none) => 2833
I know about faac quite well and I don't see the missing faac as a problem for transcode. And I do know, many plf packages are in tainted (that's why we do have tainted), the question remains, if a package being in plf2010.1 qualifies for pushing to updates.
That was done for autopano-sift : existing in plf, not provided in the initial release of Mageia1/tainted, and added in Mageia/tainted/updates ! That was done too for the tainted version of avidemux, freetype : provided first only in Mageia1/core and added later to Mageia/tainted/updates with a special build that may cause some patent problems (same as for plf versions)...
CC: (none) => nelg
*** Bug 4335 has been marked as a duplicate of this bug. ***
CC: (none) => mark9117
CC: (none) => kbulgrien
Version: 1 => Cauldron
As far as I can tell, transcode is available in both cauldron and mga2. Closing as fixed.
Status: NEW => RESOLVEDCC: (none) => johnnyResolution: (none) => FIXED