9:46 a.m.
Hello,
We are supposed to be frozen in order to prepare the RPM Fusion release.
Still I would like the nvidia driver to be updated to the latest
There is also rpmfusion-*-release to update and the related mock* and spin
changes...
Anyone still see any blocker bug beyound this one related to the multilib
issue ?
https://bugzilla.rpmfusion.org/show_bug.cgi?id=3020
Anyway, I cannot froze the release before fedora because the kernel might
change there.
(I don't know if any blocker is related to the kernel actually).
Nicolas (kwizart)
6:51 p.m.
On Dom, 2013-12-08 at 10:46 +0100, Nicolas Chauvet wrote:
Hello,
We are supposed to be frozen in order to prepare the RPM Fusion
release.
Still I would like the nvidia driver to be updated to the latest
There is also rpmfusion-*-release to update and the related mock* and
spin changes...
Anyone still see any blocker bug beyound this one related to the
multilib issue ?
https://bugzilla.rpmfusion.org/show_bug.cgi?id=3020
Anyway, I cannot froze the release before fedora because the kernel
might change there.
(I don't know if any blocker is related to the kernel actually).
Hi,
when you planning branch F20 ? after or before frozen ?
I'm asking this because I'd like plan some time to help out.
Cheers,
--
Sérgio M. B.
6:53 p.m.
What is the plan for F20 at all? This is my first Fedora release when I
have package in rpmfusion, so I have no idea. Still see only F-18, F-19
and devel in cvs.
Thanks
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
9:23 p.m.
2013/12/15 Miro Hrončok <mhroncok(a)redhat.com>
What is the plan for F20 at all? This is my first Fedora release when
I
have package in rpmfusion, so I have no idea. Still see only F-18, F-19 and
devel in cvs.
We should have been branched along with fedora, but in the f20 case, we are
rather late if we ever branch at all in cvs. In others words, I would
prefer to amputate some time for the f21 development and work more on a
koji migration than to still continue with cvs.
For the mpv case, and given that I will still need to build few packages
for the release, I can either delete the build for f20 or put it directly
in the release Everything repo, replacing the previous package.
That been said, I would prefer that only urgent jobs to be provided for f20
until the release freeze is over. We a still in a blocking release
management in RPM Fusion.
Nicolas (kwizart)
9:32 p.m.
For the mpv case, and given that I will still need to build few
packages for the release, I can either delete the build for f20 or put
it directly in the release Everything repo, replacing the previous
package.
Do whatever you prefer, I've resolved two bug reports, so I thing it's
a good idea to have it in F20, but if it is too complicated, I don't
really care to much, as long as it works.
Thanks
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
1:05 a.m.
Nicolas Chauvet wrote:
We should have been branched along with fedora, but in the f20 case,
we
are rather late if we ever branch at all in cvs. In others words, I would
prefer to amputate some time for the f21 development and work more on a
koji migration than to still continue with cvs.
Is branching really that much effort? I'd rather have F20 branched now, and
then the migration to git+Koji can go on without being a blocker for working
on packages for F21. The current CVS+Plague infrastructure is working, so
migrating to something different should not block actual packaging work.
Kevin Kofler
4:03 p.m.
On Dom, 2013-12-15 at 22:23 +0100, Nicolas Chauvet wrote:
2013/12/15 Miro Hrončok <mhroncok(a)redhat.com>
What is the plan for F20 at all? This is my first Fedora
release when I have package in rpmfusion, so I have no idea.
Still see only F-18, F-19 and devel in cvs.
We should have been branched along with fedora, but in the f20 case,
we are rather late if we ever branch at all in cvs. In others words, I
would prefer to amputate some time for the f21 development and work
more on a koji migration than to still continue with cvs.
but have we this infra structure ? , could I help on it ?
For the mpv case, and given that I will still need to build few
packages for the release, I can either delete the build for f20 or put
it directly in the release Everything repo, replacing the previous
package.
That been said, I would prefer that only urgent jobs to be provided
for f20 until the release freeze is over. We a still in a blocking
release management in RPM Fusion.
Nicolas (kwizart)
--
Sérgio M. B.
3802
days inactive
3810
days old
rpmfusion-developers@lists.rpmfusion.org
6 comments
4 participants
participants (4)
-
Kevin Kofler -
Miro Hrončok -
Nicolas Chauvet -
Sérgio Basto