---------- Forwarded message ----------
Do what thou wilt
shall be the whole of the Law.
On 4/22/10, Rahul Sundaram <metherid(a)gmail.com> wrote:
thank you for your ack.
and you have at least tried to answer one question.
but i find McCann's proposals too nebulous to allow
serious approval (if i were in the position to approve
them) first, they are based on an oxymoron:
"pointless updates" a package cannot be pointless
and be an update.
limiting non-critical updates to once weekly.
he does not specify what is meant by 'critical', how
this would help, or even how this would differ from the
as has been pointed out, there is no "stable release"
Establish norms or rules that limit the types of changes in stable
releases to ensure the releases remain stable
maybe i can help here: bugfixes, new software, configuration, interface,
again, how "stable" can Fedora be made and not conflict with
'incubate(ing) innovative new technologies'?
Love is the law, love under will.
Peter Robinson (pbrobinson(a)gmail.com) said:
> > Honestly, I could see exploding it into a variety of smaller, more focused
> > groups. Perhaps I'll whip up a proposal based on some comps files I have
> > lying around here.
> I've spent a little time looking at the hardware side of things and
> done a basic patch for some of the hardware stuff based on the current
> rawhide comps file. I've broken it down into network/server/misc for
> the time being and pushed the print stuff over to its group. More can
> be done as it was a quick look through. The old hardware-support
> currently includes all the other groups so there's no real change for
> current builds overall.
Splitting it by functionality makes a bit more sense; for example,
you'd want a 'smart card support', not just merging it in with other
(Sorry I've let this lie... been way too busy.)
Also, I'm not sure the grouplist construct works as you're trying
to use it.
> I also noticed that alot of the filesystems group lists are replicated
> into base. I think base should have the core ext related tools to boot
> a default Fedora and the other stuff like ntfs should just remain in
> the filesystems group.
Actually, anaconda will pull in the ones you use for formatting if
On Tue, 2010-04-20 at 18:00 +0100, Mat Booth wrote:
> Is this what has caused this bug in the F13 Beta?
A package split I have built in rawhide this morning can not break an
F13 release that went to the mirrors a week ago...
I am working with the artists to clean up our gnome-icon-theme package.
As part of that effort, I have split off a -legacy subpackage that
contains all the legacy symlinks, leaving only standard icon names and
symlinks for GTK+ stock icons in the main package. This is in rawhide.
If you notice missing icons in applications, please
a) File a bug against the application
b) Install gnome-icon-theme-legacy if you want your icons backc
I know that you are working on other issues, but can somebody
'enlighten' me how this Bug Report should be interpreted. (The PC is
dual Intel E2200, i686 architecture, and the OS is Fedora 11)
- First is this a bug of a regular bug report & support system or is it a bug of a 'not well elaborated addware'
- Why are these 3 keys of the hash table generated?
- What does 'unable to query info' mean?
- How could thus bug be fixed manually?
- Who is the intended recipient of this Bug Report?
- Why it could not be sent automatically?
and so on.
It is issued every time when shutting down the OS (and within some variations the content is almost one and the same).
Can anyone of you spent a few minutes on this?
P.S.: BTW the HP printer is working normally with hplip-3.10.2-1.fc11 (i586).
Am Mittwoch, den 14.04.2010, 10:25 +0200 schrieb Jaroslav Reznik:
> Hi Matthias.
> We were discussing polkit agent reorganization @ our kde sig meeting -
> cwickert joined us too .
> Could you clarify autostart of the agent? I agree it should be task for
> desktop as it's now core component and I don't see need for users to change
> this configuration.
I do. Xfce for example has no agent ATM, so users should be free to
choose ether polkit-gnome or lxpolkit. This could be easily done it we
allowed installing them individually. The choice which one is started
could be easily done graphically in the session properties.
If I understood Matthias correctly he wants the desktop to autostart the
agent and have it hardcoded somewhere. IMHO this is a step in the wrong
direction as it takes the user the freedom to decide what he wants to
> But other question is - what about desktops without own
> polkit or even standalone wms? Another point is autostart desktop file - if the
> agent is going to be started by autostart desktop file, this autostart belongs
> to agent and should be distributed together in the agent package.
> Could be
> ShowOnlyIn option considered as the correct way to achieve no autostarting in
> other desktops?
IMO yes. And IMO we still need packages that use polkit require
PolicyKit-authentication-agent because otherwise a user of say openbox
or icewm wont get a working package.
in my view it should not run by default.
Installing the service by people who know what it is could not be a problem, and by people who don't know what it is maybe it is a good idea for them to learn something about it before installing.
Let the user decide by himself what kind of SSH and how will he use, if he decides to use the service at all.
P.S. Is there anywhere on the Net a SWOT analysis of the SSH service.
I have still been holding back on migrating from Pidgin to Empathy
because I have years and years of logs that I don't want to lose. Is
anyone working on that? Upstream doesn't seem to made much progress in
a long time. I would take any hackish solutions since it is going to
be a one time deal.
We started working on the fedora-tour sometime back. I realized that we
hadnt *officially* made an announcement here on the Desktop sig mailing
About the tour
It's targeted for the F 14 release. We're on a stage where we're
deciding what the best way to get sources for the tour would be.
Is there a criteria list that we need to keep in mind while working on
It's using pyclutter for the interface.
It's at a very early stage currently, and we'd like to have the desktop
sig in on this so everyone knows what to do.
- FAS : ankursinha ; franciscod @ Freenode
- gpg --keyserver pgp.mit.edu --recv-keys 5E9BF638