GSOC PROJECT REQUEST FOR A MENTOR
by Sarath Kumar Somana
I'm Sarath, a student from India. I have been working with Ruby on Rails
Web Framework for more than a year now. I have done most of my
contributions to www.acenetcampus.com. I am very interested in taking up
Design Hub project mentioned in Fedora Project's Wiki Page for Summer Of
Code Ideas. I am interested in integrating the tools into a full fledged
platform for designers. Please help me through starting off my
contribution. Please do tell me the prerequisites to be satisfied to be
able to do this project under fedora.
I've talked with Mairin Duffy who is the mentor for the project but she
won't be mentoring the project. Can any one help me out with this ??
11 years, 2 months
PackageKit ordering patch
by Andrew Wyatt
Properly order packages returned by PackageKit so automations executed
on 64bit systems won't sometimes pull 32bit packages due to a lack of
ordering (Jockey).
--
diff -rupN PackageKit-0.6.22.orig/backends/yum/yumFilter.py PackageKit-0.6.22/backends/yum/yumFilter.py
--- PackageKit-0.6.22.orig/backends/yum/yumFilter.py 2012-12-19 14:39:41.148069422 -0500
+++ PackageKit-0.6.22/backends/yum/yumFilter.py 2012-12-19 14:56:49.163672753 -0500
@@ -88,6 +88,8 @@ class YumFilter(PackagekitFilter):
if (base, version) not in base_list_already_got:
output_list.append((pkg, status))
base_list_already_got.append ((base, version))
+ output_list.sort()
+ output_list.reverse()
return output_list
def _do_newest_filtering(self, pkglist):
@@ -116,6 +118,8 @@ class YumFilter(PackagekitFilter):
del newest[key]
newest[key] = (pkg, state)
+ newest.values().sort()
+ newest.values().reverse()
return newest.values()
def post_process(self):
@@ -127,6 +131,8 @@ class YumFilter(PackagekitFilter):
if FILTER_NEWEST in self.fltlist:
self.package_list = self._do_newest_filtering(self.package_list)
+ self.package_list.sort()
+ self.package_list.reverse()
return self.package_list
def _pkg_compare(self, pkg1, pkg2):
11 years, 2 months
Fedora 19 Feature/Branch Freeze coming in one week
by Jaroslav Reznik
Hi!
As time flows really fast, we are getting closer to another important
milestones for Fedora 19 [1] on 2013-03-12 (as agreed by FESCo):
* Feature Freeze -- Planning & Development Ends
* Branch Freeze -- Branch Fedora 19 from Rawhide
Feature Freeze is in one week from now, please keep in mind that
it's the time when your features has to be in *substantially
complete and in a testable state!*. See the Feature Freeze policy [2].
Please update your feature pages - with the best percentage done
"estimate" - 80%+ and last updated field (do not update Features List,
it's automatically generated now). If you're *at risk* of not making
the Feature Freeze, please update your feature page accordingly
and let me know. The community can help a lot, communication is the
key.
For Branch Freeze Policy, take a look on [3] and also on the list
of orphaned packages and packages that have failed to build since
Fedora 17, as these are going to be blocked on Branch date [4].
The full Fedora 19 schedule moved to a new, program manager neutral
place, see [5]. Please, let me know if you need any change in the
schedule.
Thanks
Jaroslav
[1] http://fedoraproject.org/wiki/Releases/19/Schedule
[2] https://fedoraproject.org/wiki/Feature_Freeze_Policy
[3] http://fedoraproject.org/wiki/Branch_Freeze_Policy
[4] http://lists.fedoraproject.org/pipermail/devel/2013-March/179338.html
[5] http://fedorapeople.org/groups/schedule/f-19/
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11 years, 2 months
Amide, looking for a co-maintainer
by Mario Ceresa
Hi all,
I noticed that Amide is orphaned, even if it is still possible to
install in f18. Is anyone interested in helping to maintain it?
Thanks,
Mario
BTW: I tried to take ownership, but I can only do that for 17. Is
there something wrong with my FAS account?
11 years, 2 months
F16 and F18: bugzilla, bugs and EOL
by Dmitrij S. Kryzhevich
Hi!
There an interesting thing happened in gugzilla recently. Some bug
(https://bugzilla.redhat.com/show_bug.cgi?id=809773) is applied for F16. There
are some (five, ten, twenty,...) simmilar bugs which are, ofcouse, are marked
as dublicate. But. Last one is for F18
(https://bugzilla.redhat.com/show_bug.cgi?id=895465), and it is marked as
dublicate of F16 bug when, you know, F16 is automatcaly EOF. So the first bug
is automaticaly closed as well a new one.
Nothing strange here? We have new bug reports that are closed automaticaly
wiht no solution. Something should be changed here, how do you think?
Dmitrij S. Kryzhevich.
11 years, 2 months
