So I have this package that I made, but it has no 'assigned' reviewer:
if someone wouldn't mind doing this, once I am a packager myself, I wouldn't
mind reviewing other's packages.
On Mon, Jun 6, 2011 at 9:19 PM, Ryan Lewis <me(a)ryanlewis.net> wrote:
> Hola Fedora developers,
> My name is Ryan! Currently i'm a PhD student in computer science theory at
> dartmouth college. I'm a campus ambassador at dartmouth college. My research
> interests are in computational & applied topology for a brief introduction
> to field: http://en.wikipedia.org/wiki/Topological_data_analysis.
> I try to contribute to the community as a campus ambassador. I regularly
> give away install/live media buttons and stickers to just about everyone,
> and I use them as prizes when I TA computer science classes (which works
> really well for getting us dartmouth undergrads to contribute).
> I've just joined this list, and I'm learning now about how to write RPM
> spec files, with my ultimate goal of maintaining a few packages.
> I recently got my koji browser certs, and I've been reading the guidelines.
> I move pretty slowly on my own, if anyone nearby me is interested in helping
> me advance my packaging 'foo' as they say, i'd be open to the assistance!
I'm a Linux/Unix sysadmin who has been using all sorts of linux/unix
variants since about 1998 now. I have previously made or tried to make
some small contributions to the Banshee, Jokosher and KNode projects.
These did not go very far, but I was glad to be able to help.
I have been using Fedora for the past few years on the desktop (mainly
CentOS on server side). A few months ago I re-packaged BIND for our
company which was not easy so I decided I need to learn more about
packaging stuff properly. I asked Máirín Duffy on twitter what I could
do to contribute for packages and she suggested fonts as an easy place
to start so here I am :-)
She has suggested some fonts I could package so I'm working through the
first one, League Gothic. I'm having some trouble understanding what
foundries are and how font packaging works in Fedora in general so any
help along those lines is much appreciated.
I have been having problems with my Lenovo T61 and Rawhide. Currently
the system will do all kinds of watchdog resets when I am booting the
3.0 kernels but not with the 2.6.38 kernel. I am trying to figure out
how to best capture and debug them as they tend to scroll off the
screen faster than I can catch anything. For the rc4 kernels I think
it is dieing when trying to remount the root disk but on the rc5
kernel it gets past that and crashes during nfs or smartd. The funny
thing is.. when I installed kdump and put in 256MB for a kernel save..
the problem goes away on reboot.
Does turning on kdump and installing debuginfo kernel stuff change
things in a way that a watchdog oops won't happen?
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Let us be kind, one to another, for most of us are fighting a hard
battle." -- Ian MacLaren
I'm going to replace the report library with the new libreport. Today I
plan to replace it in rawhide and if it goes smoothly I'd like to
replace it in F15 as well.
- libreport is written in C (report is in python), so it's easier to
write bindings for other languages
- it's API compatible with report (it has python bindings)
- it shares configuration with ABRT, so users just need to write their
credentials and defaults only once
- shares the UI with ABRT (the reporting wizard), so users are presented
with the same UI despite of from where they are reporting a problem
- it has a bit different UI
- account information (e.g: bz loging+password) is forgotten and needs
to be entered again
- some minor breakage expected (hopefully not...)
affected packages (according to repoquery):
- report + subpackages (being obsoleted)
As I said, libreport should be API compatible with report, so no changes
should needed, but of course can't be 100% sure if it's bugfree ;)
glibc now includes libnss_db again, so the nss_db package is no longer
needed from f16 onward.
Andreas Schwab, schwab(a)redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."