Update: PackageMaintainers wiki cleanup update
by Susan Lauber
On Sat, Jan 31, 2009 at 5:01 PM, Susan Lauber
<laubersm(a)fedoraproject.org> wrote:
>
> Greetings to the authors/maintainers of Package Maintainer wiki pages,
>
> I introduced myself last week [1] and since then I have dug into the pages and set up a task table [2]
>
> I have already added a category to most pages so they can all be found together [3].
> If there are others or if you create a new page just add the string [[Category:Package Maintainers]] to the bottom of the page.
>
> The next step is renaming so that pages are easier to find in a search. It will also make the category page easier to use. I have started making suggested in the packagemaintainers.psv [4] file in the wikirename.git repo and
Update: Pages were moved this past weekend (20090222)
I also did a lot of work merging the old PackageMaintainers page into
the Category page itself. I think it is still too long but will
continue to clean it up this week. If I missed any redirects, please
let me know (or just fix them).
See https://fedoraproject.org/wiki/Category:Package_Maintainers
The layout has
*old PackageMaintainers info at the top (maintained manually)
*Sub Categories (dynamically created list)
*Pages in the Category (synamically created list)
*Please do NOT include subdirs / in names going forward.
*All links to the old page names should redirect but going forward,
please try to use the new names.
*To add a page to the category add [[Category:Package_Maintainers]] to
the bottom of the page.
*To link to the category page from within another page use the syntax
[[:Category:Package_Maintainers]] (not the extra colon at the
beginning)
>
> ***I encourage others to check the proposed names and offer additional suggestions.***
>
> I would like to have this file ready for the wikibot by the end of the week (Feb 7).
> Lack of response will be seen as a vote of confidence :)
>
> Thanks,
> Susan
>
> [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01545.html
> [2] https://fedoraproject.org/wiki/Docs_tasks_for_Packaging_Guide_and_related...
> [3] https://fedoraproject.org/wiki/Category:Package_Maintainers
> [4] http://git.fedorahosted.org/git/?p=wikirename.git;a=blob_plain;f=packagem...
> with naming instructions at https://fedoraproject.org/wiki/Help:Wiki_structure
>
--
Susan Lauber, (RHCX, RHCA, RHCSS)
Lauber System Solutions, Inc.
http://www.laubersolutions.com
gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974
15 years, 3 months
Need help with gxine's SEGFAULT
by Martin Sourada
Hi all,
I've recently received a bug report for gxine [1] on Rawhide (SEGFAULT
when playing a song). The problem is that I cannot reproduce the issue
(neither on F10 nor on Rawhide) and the reporter is unable to produce
back-trace (I am unable to reproduce this error as well):
$ gdb gxine
GNU gdb (GDB) Fedora (6.8.50.20090210-1.fc11)
...
(gdb) run
Starting program: /usr/bin/gxine
[Thread debugging using libthread_db enabled]
Error while reading shared library symbols:
find_new_threads_callback: cannot get thread info: generic error
find_new_threads_callback: cannot get thread info: generic error
I hope to either bisect the issue myself or at least forward it with
useful info upstream, so I though I'd ask -devel and -test lists for
help.
For -devel: Does anyone know what might be wrong with gdb in this case?
Should I expect gxine or gdb to be at fault? Any other ideas what can
the reporter do to give me useful information about the SEGFAULT? On a
related note, I'd welcome a co-maintainer for gxine because I use it
very rarely lately (practically only for DVD-Video) and it would be
good to have someone who uses it more co-maintaining it...
For -test: Is anyone able to reproduce the SEGFAULT *and* produce a
useful back-trace? If so, please attach your back-trace to the bug.
Thanks,
Martin
References:
[1] https://bugzilla.redhat.com/show_bug.cgi?id=486494
15 years, 3 months
Latest kernels and sound still not working in F10
by Simo Sorce
I am wondering if something is being done for the alsa problem and lack
of sound with newer F10 kernels.
I keep upgrading kernels as soon as they come out but I still have to
revert to 2.6.27.7-134 each time or I get no sound from the sound card
on my desktop (Creative Labs SB Audigy).
At some point in one of the kernels (170.2.5 ?) I saw some changelog
about fixing this problem but it seem like it doesn't work at least for
me.
Is there any work being done to fix it ?
Simo.
--
Simo Sorce * Red Hat, Inc * New York
15 years, 3 months
F11-Alpha: no yum update; gtk-update-icon-cache
by sean darcy
Just did a clean install of alpha 11. On first yum update ( over night )
machine locks ups. Restart. run yum-complete-transaction. It seems yum
had installed the 1100+ updated packages, but got stuck erasing.
Every 5 -10 packages, yum fails with a gtk-update-icon-cache: No theme
index file
............
ValueError: too many values to unpack
So I'm waiting for each fail, running rpm -q on the failing package, and
then rpm -e --noscripts on the older version of the package.
And now, after doing that on bluez-gnome, yum-complete-transaction dies,
with:
ImportError: No module named iniparse
Any way to fix any this? Or just give it up?
sean
15 years, 3 months
Package review request: OpenBSD calendar(1) command
by David Cantrell
I've packaged up the calendar(1) command from OpenBSD and created a
review request:
https://bugzilla.redhat.com/show_bug.cgi?id=485853
Warren Togami reviewed it but raised an issue about the name of the
actual command. The concern is that the name might be too generic and
could possibly collide with something else.
The executable is /usr/bin/calendar, as taken from OpenBSD.
If you have any reservations about the executable being named
/usr/bin/calendar, reply here or post in the review request.
Thanks,
--
David Cantrell <dcantrell(a)redhat.com>
Red Hat / Honolulu, HI
15 years, 3 months
Fedora 10/KDE: how to make vfat mount with shortname=mixed as default?
by Serguei Miridonov
Hello,
I had posted this question to fedora-list with a hope that some
advanced used could find a solution but till now that post is
unanswered. So, now I hope that somebody from a developers community
can help...
In konqueror from KDE 3.x there was an option in folder properties -
"Mounting options" which could be used to specify some mounting
options for certain drives (the volume was specified by the device ID,
not sure now...). I could not find similar options in modern Dolphin
file manager.
In fact, for myself, and probably for many other users, it would be
more practical to make the option 'shortname=mixed' system-wide and
add the possibility to adjust it for particular drives, if necessary.
Is it possible in Fedora 10 without any program recompilation?
There are some forum posts about using gconf-editor, but it does not
seem to work in KDE...
There are also related problems: for example, how one can add 'eject
<device>' or 'sdparm --command=stop <device>' into hal or mount/umount
helpers? This is necessary for proper handling external drives and
flash memory.
Any idea?
Thanks.
15 years, 3 months
Fedora needs your help
by Nicolas Mailhot
Dear all,
As some of you know Fedora 11 will feature automatic font installation¹.
This is a genuinely new feature that does not try to ape what other
operating systems do and play on Linux's traditional attention to
localization and internationalization. It's a free/libre alternative to
the DRM-ed distribution channels proprietary foundries are pushing right
now².
However, awesome new installation code is not sufficient. To work well
this feature requires a large and sane font package pool to draw on. To
provide this pool the Fonts SIG has worked hard to define clear and sane
packaging guidelines last year³.
The maintainers of affected packages were notified two months ago of
needed changes⁴. However, while many reacted fast, others have still not
started looking at it⁵.
With only one month left before Fedora 11 beta it's time for others to
step up and help adapt the remaining packages. Please take a look at the
bugzilla tracker⁴, adopt an open bug, and propose spec file changes
there. Extensive documentation was written⁶ for this operation and you
do not need to be a font expert to participate.
Also, changing such a large pool of packages is never mistake-free, and
we also need testers to QA⁷ the changes. Please take a look at the
bugzilla tracker⁴, adopt a closed bug, and check the corresponding
package was converted properly.
I'm afraid we are massively short-handed right now. Please help.
_________
¹ http://fedoraproject.org/wiki/Features/AutomaticFontInstallation
² http://en.wikipedia.org/wiki/Embedded_OpenType
³ Finally ratified in January 2009, but their expected content was
public a long time before)
https://www.redhat.com/archives/fedora-devel-announce/2009-January/msg000...
⁴ https://bugzilla.redhat.com/show_bug.cgi?id=477044
⁵ http://blog.stevecoinc.com/2009/02/help.html
⁶ http://fedoraproject.org/wiki/Shipping_fonts_in_Fedora_%28FAQ%29
http://fedoraproject.org/wiki/Packaging:FontsPolicy
⁷
http://fedoraproject.org/wiki/Features/Repackaging_of_Fedora_fonts#How_To...
http://fedoraproject.org/wiki/Improving_existing_font_packages
--
Nicolas Mailhot
_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce
15 years, 3 months
Package review SIG work
by Jason L Tibbitts III
I would like see if it's possible to get the package review SIG moving
again. I personally have been very low on time since Fudcon but
things are starting to let up.
I have two questions:
Who is interested in working with a package review SIG? I'll include
some possible SIG agenda items at the end of this message.
How should the SIG conduct business?
Within Fedora this generally happens via IRC meetings, but I'm not
sure how that would work out because we really do have reviewers from
all over the planet and picking a single time for an IRC meeting will
inevitably leave some folks out. Plus there's been some recent
backlash relating to conducting business on IRC which I'm sensitive
to.
So, I see a couple of options:
1) Have more than one meeting time and rotate through them.
2) Figure out how to conduct reasonable business (with an agenda,
time-limited discussion and votes) on a mailing list.
I am willing to handle the various duties while the SIG gets
organized. I will follow this thread for a couple of days and
summarize the responses.
Here's a random list of potential SIG agenda items:
Getting https://fedoraproject.org/wiki/SIGs/Package_Review into shape.
Dealing with significantly time-consuming reviews and possible
multiple-reviewer scenarios. Should the SIG identify these reviews
and attempt to parcel them out to groups of reviewers?
Addressing the growing number of NEEDSPONSOR tickets.
Forming a merge review priority list: finishing up the
F9MergeReviewTarget ticket and identifying the next set of reviews to
tackle.
Metrics.
Proposing to manage the ReviewGuidelines document.
- J<
15 years, 3 months
