Device ownership/permissions
by Orion Poplawski
What system is responsible for changing device ownership/permissions in
fedora when a user logs in on Fedora 8? We're trying to figure out a
problem that is causing pulseaudio not to run with latest testing
updates (https://bugzilla.redhat.com/show_bug.cgi?id=411071). I'm think
it may be a problem with hal-acl-tool, but I really have no clue.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
16 years, 4 months
summer coding for 2008
by Karsten Wade
The page for ideas for Fedora projects that interns and summer coding
students can tackle is now open:
http://fedoraproject.org/wiki/SummerOfCode/2008/Ideas
"Good ye gods, Karsten, it's December, why are you worried about that
now?"
Glad you asked.
Fedora got a much smaller number of student slots last year compared to
projects of a similar or much smaller size. The GSoC team responds when
you have lots of good proposals from students by giving you more slots.
We didn't have good ideas out early, we didn't do much publicity early,
and students didn't get many proposals in.
So, the more ideas on that page, the better. Work can actually happen
on an upstream project, through Fedora, if it brings benefits to Fedora.
(We did this with Moin Moin the last two years, as well as GNOME's
Damned Lies this last year.)
Is there anyone interested in helping to coordinate idea creation for
the various intern programs we can be part of?
Remember that although some programs require students to work on solo
coding projects, they can be modular parts of a greater whole. Students
can also come from within the existing communities.
Depending on interest, we'll probably hold a BarCamp and/or a hackfest
session on this topic at FUDCon. The goal is to be prepared and loud
about it, so when Google opens the proposal doors in the Spring(?),
Fedora is more than ready.
- Karsten
--
Karsten Wade, Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41
16 years, 4 months
Sun releases APOC
by Razvan Corneliu C.R. "d3vi1" VILT
While stuff released by Sun Microsystems is not really what fedora-devel
is usually about, this little piece of technology, with a design simple
enough for every admin to understand, does change a lot in enterprise
deployment, and seems to be a natural complement to the FreeIPA project.
What it is all about is rather simple: Having a "centralized storage for
application and desktop configuration". In APOC's case it's a LDAP
server. I can only dream of the day in which my GAIM and Evolution
settings can be loaded on a PDA (say N800) or another new workstation
from the LDAP server, as well as imposing settings for my users.
While the first one can be solved by a NFS or CIFS mount, the second one
is not really that elegantly solved.
>From my point of view it's the most elegant approach to this problem and
I hope that the Fedora Project plans to include it's wonderful
functionality into future versions of the distribution.
I am aware of the fact that everything that APOC does can be replicated
using some other mechanisms, but none is as elegant as storing
everything in a LDAP server, and it obviously makes more sense to do so
considering that FreeIPA and Samba4 and many other projects base their
data storage on LDAP.
With stuff like this, easily manageable UNIX desktops seem to be closer
every day.
I am rather curious on what you guys think.
Cheers,
Razvan
P.S.: Before you ask, YES it's GPL 2.0 (dual-licensed with CDDL) and
it's hosted at freedesktop.org ( http://apoc.freedesktop.org/wiki/ to be
more exact)
16 years, 4 months
Re: Orphaning packages
by Jon Ciesla
>
>>
>>> Hi,
>>>
>>> Just to let you know that other than the mono packages I currently
>>> maintain,
>>> I'm going to have to drop the other packages I have down for me.
>>>
>>> For ease, if it's a mono or mono-related package (such as mono-develop,
>>> libgdiplus, db4o etc), I'll maintain it. Anything else is dropped. I'll
>>> update
>>> the wiki and the owners lists as soon as I can.
>>>
>>> Basically, it's the old problem of time....
>>
>> I'll take genchemlab and gonvert.
>
> Which you'll need to orphan in pkgdb, BTW. In case you forgot. I know I
> would. :)
Is there someone In rel-eng or cvsadmin or thereabouts that should assist
with this, if Paul hasn't the time? I feel bad making more demands on his
time in order to help him lessen the demands on his time. :)
>>> TTFN
>>>
>>> Paul
>>>
>>> --
>>> Get your free @ukpost.com account now
>>> http://www.ukpost.com/
>>>
>>> --
>>> fedora-devel-list mailing list
>>> fedora-devel-list(a)redhat.com
>>> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>>>
>>
>>
>> --
>> novus ordo absurdum
>>
>> --
>> fedora-devel-list mailing list
>> fedora-devel-list(a)redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>>
>
>
> --
> novus ordo absurdum
>
--
novus ordo absurdum
16 years, 4 months
pykde4 planned?
by Neal Becker
Is it planned to have a pykde4 to go with kde4?
16 years, 4 months
Undoing ACLs (was Re: Dealing with PPC in Fedora 9(+))
by Jesse Keating
On Wed, 05 Dec 2007 12:00:49 +0000
David Woodhouse <dwmw2(a)infradead.org> wrote:
> (Although I don't feel wonderfully happy about accepting such rights
> for myself alone when I feel strongly that _all_ Fedora contributors
> should be able to commit to all packages. It's not as if we can't
> revert stuff, and can't promote an attitude of violence towards
> people who abuse the privilege, like we already have.)
This is actually a topic that has come up a few times. A good number
of previously core packages still have default locked down ACLs. This
was somewhat mandated by the general populace of core maintainers.
However I think that the trial period is over and I hope that the
Fedora maintainers at large have proved to be responsible about what
they do, so that all maintainers should feel confident in opened
packages.
I still want there to be an ACL system for when a maintainer strongly
feels that his/her package should be kept to a small commit list.
However the vast majority would be just fine open, and would promote
more of a help you neighbor attitude if ACLs weren't in the way.
So I'd like to discuss the idea of having an automated "opening" of all
ACLs that a maintainer can opt /out/ of should they choose. Some
methodology of tagging each package that should be opened and allowing
some time for a maintainer to "untag" the package as it were to opt out
of opening it.
I'm bouncing this back over to fedora-devel-list as that's where
something like this should be brought up.
Thoughts?
--
Jesse Keating
Fedora -- All my bits are free, are yours?
16 years, 4 months
Smolt database is broken
by Michael Wiktowy
I just submitted my profile a few days ago and immediately tried to
retrieve it and got some other machine that didn't match my config. So
I submitted it again and things looked a bit more reasonable. Today I
checked it again and the vast majority of it has changed.
So there is some massive database corruption going on AFAICT. Did I
miss a message somewhere indicating this?
ref my machine:
http://smolt.fedoraproject.org/show?UUID=c8dbb9d3-a9bd-4ba6-b92e-4a294ba5...
/Mike
16 years, 4 months
Rebuilds for openssl/openldap
by Matthias Clasen
Here is a list of packages which still need to be rebuilt against the
new openssl or openldap. (The list is just what is blocking the update
on my machine, there may be more in the repository).
I would be happy to help out with this, but most of these have ACLs that
prevent me from doing so...
Matthias
apr-util
autofs
bind-libs
bind-utils
cups
cyrus-sasl
cyrus-sasl-md5
fetchmail
hpijs
hplip
htdig
httpd
httpd-tools
inkscape
libflashsupport
libsane-hpaio
mysql-libs
nss_ldap
ntp
opal
pam_ccreds
postgresql-libs
pwlib
pyOpenSSL
python-ldap
qca-tls
sendmail
subversion
sudo
tcpdump
transmission
xchat
xorg-x11-server-Xephyr
xorg-x11-server-Xnest
xorg-x11-server-Xorg
16 years, 4 months