Re: /etc/sysconfig/modules/
Sérgio Basto (ser...@serjux.com) said: > Hi, > In my F17 system > rpm -qf /etc/sysconfig/modules/* > bluez-4.99-2.fc17.x86_64 > qemu-system-x86-1.0.1-1.fc17.x86_64 > > on this > http://fedora-os.org/2012/09/13/workaround-for-vbox-modules-loading/ > Antonio Trande says that modules of vbox ( don't matter what) doesn't > load at boot time . > But if this is true neither should boot bluez or qemu-system. > 1 - Which package is responsibility to load modules > from /etc/sysconfig/modules/ ? systemd *should* load it via the fedora-loadmodules.service. > 2 - Also in article mention that we should put this files > in /etc/modules-load.d/ as part of systemd , > but > yum provides /etc/modules-load.d/\* > No Matches found > shouldn't bluez, qemu-system-x86 etc etc move loading modules > to /etc/modules-load.d/ ? It should, but the old should still work for the time being. Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Qua, 2012-09-19 at 11:13 +1000, Ankur Sinha wrote: > On Tue, 2012-09-18 at 23:11 +0100, Camilo Mesias wrote: > > Thanks for all the suggestions, I took the X11 config option which *just > > works* > > > > I honestly think this should be the default. > > > > At least, if there is a setting it should be system wide rather than > > personal / effective only after login, because devices with touchpads > > are predominantly personal devices not shared workstations... > > > > -Cam > > > Hi folks, > > We set up a page about this (The link was sent to the list too iirc) > > https://fedoraproject.org/wiki/How_to_enable_touchpad_click#KDE > > It still misses the KDE method. Could someone please add it? Please add > info about gdm etc also if you think it should be present there. Hi, I don't read all thread , sorry I'm repeating someone , but I use synclient to configure my touchpad. I have a simple script that I run in my home user, when I lose my configuration, which is just after a systemctl restart udev-trigger.service, not often neither after reboots ~/syncl.sh synclient VertTwoFingerScroll=1 synclient HorizTwoFingerScroll=1 synclient -l | grep -i scroll synclient VertEdgeScroll=1 synclient HorizEdgeScroll=1 synclient -l | grep -i tap synclient TapButton1=1 synclient TapButton2=1 synclient TapButton3=1 -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Tue, 2012-09-18 at 23:11 +0100, Camilo Mesias wrote: > Thanks for all the suggestions, I took the X11 config option which *just > works* > > I honestly think this should be the default. > > At least, if there is a setting it should be system wide rather than > personal / effective only after login, because devices with touchpads > are predominantly personal devices not shared workstations... > > -Cam Hi folks, We set up a page about this (The link was sent to the list too iirc) https://fedoraproject.org/wiki/How_to_enable_touchpad_click#KDE It still misses the KDE method. Could someone please add it? Please add info about gdm etc also if you think it should be present there. -- Thanks, Warm regards, Ankur: "FranciscoD" Please only print if necessary. Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG http://fedoraproject.org/wiki/User:Ankursinha http://dodoincfedora.wordpress.com/ signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: New Anaconda and Mouse Buttons
On 09/19/2012 04:25 AM, Przemek Klosowski wrote: > Glad you like it. It seems to be a fairly 'early-on' Anaconda > functionality change, so I am not sure what's the next step: feature > request? bug report? Could someone from the Anaconda or Fedora > engineering suggest the right thing to do? File a RFE against Anaconda Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: New Anaconda and Mouse Buttons
On 09/18/2012 02:20 PM, john.flor...@dart.biz wrote: > > PROPROSED: > > on (button-1-press or button-2-press or button-3-press) of ok_button do: > > commit_changes() > > end; > > I see two problems with this approach: it blocks forever any possibility > of using multiple buttons in Anaconda, and makes it behave differently > from the system it is about to install. I would prefer this: > > on (button-1-press or button-2-press or button-3-press) of ok_button do: > if (button-1-press) do: > commit_changes() > else > ask_if_the_user_wants_to_change_the_mouse_handedness() > end; Very clever. That would float my boat. Glad you like it. It seems to be a fairly 'early-on' Anaconda functionality change, so I am not sure what's the next step: feature request? bug report? Could someone from the Anaconda or Fedora engineering suggest the right thing to do? BTW, if the user chooses to reconfigure the mouse in Anaconda, it probably could be a good default setting for the OS, too. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Non-responsive pytrainer maintainer; anyone interested in the package?
On 09/18/2012 01:59 AM, Kevin Fenzi wrote: On Mon, 17 Sep 2012 11:28:07 +0200 Brendan Jones wrote: On 09/17/2012 11:18 AM, Kalev Lember wrote: On 09/05/2012 07:02 PM, Kalev Lember wrote: The ticket for its non-responsive maintainer Douglas E. Warner is: https://bugzilla.redhat.com/show_bug.cgi?id=842894 All reasonable attempts to resolve this have failed. Douglas E. Warner confirmed in https://bugzilla.redhat.com/show_bug.cgi?id=842894#c2 that he currently doesn't have time for Fedora package maintenance. Can some FESCo member please look over this issue and orphan pytrainer, and possibly other Douglas E. Warner's packages as well? I've requested ACL's - if I can't fix it I'll orphan it I've approved your acls. kevin 1.9.1 pushed to rawhide,f18,f17 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: fedpkg / koji error
On 09/05/2012 08:07 PM, Tom Callaway wrote:
On 09/05/2012 12:48 PM, Simone Caronni wrote:
This means that even for the EPEL branch the first %if block is
evaluated; so the fedpkg on my system (Fedora 17) sets %rhel to 6 but
does not unset %fedora and they are both present.
Confirmed. fedpkg is inheriting the value of "%fedora" from the base OS
on EPEL targets.
The reason why is because fedpkg determines the dist tag values from the
branch name, and then passes them to rpm via the "--define" flag, which
overrides those specific macros if present, but leaves all the other RPM
macros intact. RPM has no "--undefine" flag to disable a macro, so the
best thing we can do is to --define the unused dist tag target to 0
(%fedora for EL branches, %rhel for Fedora branches). There is some
legacy code in fedmsg handling now-obsolete OLPC branches, so in my
patch, I just told it to treat "rhel" as the unused dist tag for the
OLPC branch case.
This change might cause a slight change in evaluated behavior, if anyone
was doing something depending on %rhel or %fedora being unset, but the
common case of checking value like you do (and like we document):
%if 0%{rhel}
should evaluate to:
00, or 0. I've tested and confirmed this fix resolves your specific
conditionals such that only one resolves on each branch.
(If you want to see this in action on a Fedora box, check out a package
that has an EPEL branch, go to the EPEL branch, and add the following
under %setup:
echo "fedora is %{?fedora}"
echo "rhel is %{?rhel}"
Then, run fedpkg prep and note the output.)
Jesse, I'm not sure if you're still the correct upstream here, please
correct me if you're not, and I'll send the patch somewhere else.
~tom
==
Fedora Project
This helps me a lot as well building el srpms from master with "fedpkg --dist
el6 srpm". +1 from me.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 http://www.nwra.com
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Subject: Schedule for Wednesday's FESCo Meeting (2012-09-19)
Do we no longer email the feature / bug tracker owners before discussions that affect their features or bugs? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
Thanks for all the suggestions, I took the X11 config option which *just works* I honestly think this should be the default. At least, if there is a setting it should be system wide rather than personal / effective only after login, because devices with touchpads are predominantly personal devices not shared workstations... -Cam -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
/etc/sysconfig/modules/
Hi, In my F17 system rpm -qf /etc/sysconfig/modules/* bluez-4.99-2.fc17.x86_64 qemu-system-x86-1.0.1-1.fc17.x86_64 on this http://fedora-os.org/2012/09/13/workaround-for-vbox-modules-loading/ Antonio Trande says that modules of vbox ( don't matter what) doesn't load at boot time . But if this is true neither should boot bluez or qemu-system. 1 - Which package is responsibility to load modules from /etc/sysconfig/modules/ ? 2 - Also in article mention that we should put this files in /etc/modules-load.d/ as part of systemd , but yum provides /etc/modules-load.d/\* No Matches found shouldn't bluez, qemu-system-x86 etc etc move loading modules to /etc/modules-load.d/ ? Thanks, -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: What happend with SystemConfigCleanup?
Mmm... Maybe devel list will be interested to develop this good tool. Somebody wants develop or start develop these tool or create software (control panel) to admin your system with s-c-*(tools)? On Sep 18, 2012 10:39 PM, "Nicola Soranzo" wrote: > Il giorno mar, 18/09/2012 alle 20.11 +0100, Álvaro Castillo ha scritto: > > What happend with SCC? > > https://fedoraproject.org/wiki/Features/SystemConfigCleanup > > > "Current status > > > > Targeted release: Fedora 18 > > Last updated: 2009-05-19 > > Percentage of completion: 25%" > > > > Is not updated from 2009, have worked only 25% but will be included on > > F18? How is possible? > > You missed > > "Category: FeaturePageIncomplete" > at the end of the page, i.e. it is a feature being investigated by the > Fedora community that have not been Proposed or Accepted for a > particular Fedora release. More info at > > https://fedoraproject.org/wiki/Features/Policy > > Nicola > > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: What happend with SystemConfigCleanup?
Il giorno mar, 18/09/2012 alle 20.11 +0100, Álvaro Castillo ha scritto: > What happend with SCC? > https://fedoraproject.org/wiki/Features/SystemConfigCleanup > "Current status > > Targeted release: Fedora 18 > Last updated: 2009-05-19 > Percentage of completion: 25%" > > Is not updated from 2009, have worked only 25% but will be included on > F18? How is possible? You missed "Category: FeaturePageIncomplete" at the end of the page, i.e. it is a feature being investigated by the Fedora community that have not been Proposed or Accepted for a particular Fedora release. More info at https://fedoraproject.org/wiki/Features/Policy Nicola -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
> From: Adam Williamson > To: Development discussions related to Fedora > Date: 09/18/2012 14:57 > Subject: Re: Why is not enabled TapButton of touchpad on Fedora by default? > Sent by: devel-boun...@lists.fedoraproject.org > > On Tue, 2012-09-18 at 08:35 -0400, john.flor...@dart.biz wrote: > > > From: Adam Williamson > > > > > > Oh, I should also note that, IIRC, the intent is that the driver > > should > > > detect if there are no physical buttons and enable tap-to-click in > > this > > > case. So touchpads which have no buttons and are only supposed to > > work > > > with tap-to-click should be OK. > > > > Where does my notebook's touchpad fall in this continuum? At the > > bottom corners of the touch-sensitive area are two "buttons" which > > click with tactile feedback, but yet are still part of the > > touch-sensitive surface. In other words, the bottom corners can > > actually be deformed/depressed. FWIW, I enabled tap-to-click -- did I > > just answer my own question? -- simply because my wife and I both > > found the mouse to be moving off target too often when tried using > > these "buttons". > > As far as evdev is concerned those are almost certainly just perfectly > normal buttons, i.e., they send a 'button press' event. The fact that > they also function as part of the touch-sensitive surface is probably > irrelevant. So evdev would see your touchpad as one with buttons, and > wouldn't enable tap-to-click. If memory serves (which, in my case, is always questionable), that matches my experience: I had to enable the feature; it wasn't on by default. > (I hereby include my permanent disclaimer that I'm just the idiot > monkey, and any time someone who's not an idiot monkey comes along and > contradicts me, you can confidently assume I'm wrong...so if ajax or > whot or someone shows up and says I'm wrong, then I damn well am.) Hey! That's mine too, except you can s/ajax|whot/nearly anyone/g. Offer void where not prohibited. -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] Fedora 18 QA Retrospective page is up
The Retrospective page for Fedora 18 QA is now up:
https://fedoraproject.org/wiki/Fedora_18_QA_Retrospective
We use the retrospective page to track things that went well and things
that didn't go so well during the Fedora 18 validation process, and for
tracking ideas we have but don't have time to act on during the rush of
doing validation (that's the wishlist).
Please, add any feedback you have of this type to the retrospective
page! There are instructions on the page for adding feedback.
All feedback is useful, and once 18 validation is done, we'll take a
look at all the items on the page and come up with specific
recommendations for addressing them which we'll file as trac tickets and
work on in the time before Fedora 19 validation starts up. We've been
doing this for a while now and it's turned out to be a great way to keep
constantly improving our processes.
You can look at the previous pages for inspiration:
https://fedoraproject.org/wiki/Category:QA_Retrospective
And I'll copy/paste James' old list of leading questions to prompt
feedback (thanks, James!):
1. Were you able to participate in any Fedora 18 Alpha, Beta or
Final test runs?
2. What worked well, what prevented you from participating, were
instructions clear?
3. What worked (or didn't work) well about Fedora Test Days this
release?
4. Are you a maintainer, why do you think your critpath updates
haven't been tested? What could you do to encourage more
testing of your proposed updates?
5. Did you escalate any bugs for consideration as
{Alpha,Beta,Final} release Blockers? Why not? Was the process
well documented and did it make sense?
6. Did you attend or contribute to any Fedora blocker meetings?
Why not? What did you like, dislike? What prevented you from
participating?
7. Did you find any of the release criteria changes or validation
test extensions particularly useful or problematic?
8. Can you think of any obviously important areas we are not
currently covering in the validation tests and criteria?
9. Unlimited time and resource ... what do you think the the QA
team should focus on for Fedora 19 and beyond
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 18 Alpha is hereby declared GOLD
On Sep 18, 2012, at 1:02 PM, Adam Williamson wrote: > So in the context of this mail, we're not talking about Alpha being > released, we're talking about it being declared release-able. Fedora 18 Alpha Release Criteria/Requirements Satisfied Fulfilled Met Achieved Fedora 18 Alpha is hereby declared releaseable a go I'd go with the first one. It's the least ambiguous, in particular for ESL speakers. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Subject: Schedule for Wednesday's FESCo Meeting (2012-09-19)
Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 17:00UTC (1:00pm EDT) in #fedora-meeting on irc.freenode.net. Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic 932 F18 Features - progress at Feature Freeze .fesco 932 https://fedorahosted.org/fesco/ticket/932 #topic 940 The tmp-on-tmpfs feature should be disabled by default .fesco 940 https://fedorahosted.org/fesco/ticket/940 = New business = #topic 951 Co-maintainership of Chitlesh's Fedora packages maintainer issue .fesco 951 https://fedorahosted.org/fesco/ticket/951 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 If you would like to add something to this agenda, you can reply to this e-mail, file a new ticket at https://fedorahosted.org/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
What happend with SystemConfigCleanup?
Hi! What happend with SCC? https://fedoraproject.org/wiki/Features/SystemConfigCleanup "Current status Targeted release: Fedora 18 Last updated: 2009-05-19 Percentage of completion: 25%" Is not updated from 2009, have worked only 25% but will be included on F18? How is possible? Álvaro Castillo http://fedoraproject.org/wiki/User:Netsys Linux user #547784 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 18 Alpha is hereby declared GOLD
On Tue, 2012-09-18 at 11:16 -0600, Chris Murphy wrote: > On Sep 17, 2012, at 3:34 PM, Jesse Keating wrote: > > > Also, the point of marking something as GOLD was that it's ready to > be staged for distribution. GOLD meant Gold Master, that is the master > copy was produced and sent off to the duplicators. > > Right. The GM refers to the digital version from which the physical > stamping plate for mass producing CD/DVD's are made, or the stamping > plate itself. Companies, even big ones who had to send out CD's to > alpha and beta testers by mail because the software was big enough and > the internet slow enough, never made mass produced CD's for software. > The were in-house made by burning, not stamping. i.e. there was no GM. > The term GM or GOLD is simply inapplicable to alphas and betas. > > > "Ready for testing" doesn't quite embody that same idea. > > Good. It shouldn't. > > > "Completed" seems to make some sense, the Alpha has been completed > and is now being staged for release. > > I would use the word "RELEASE" instead of TC1, TC2, RC1, RC2. So > "Fedora 18 Alpha RC3" became "Fedora 18 Alpha Release". It was after > all a "release candidate" and once no longer a candidate, it is a > release. > > "Completed" adds yet another term that seems unnecessary, albeit > vastly more appropriate than GOLD or GM. I think you're missing the subtle distinction Jesse was drawing. His point is that the mail we're discussing is not the *release* announcement. It's the *sign-off* announcement. It's sent out right after the go/no-go meeting happens, which is nearly a week before the actual release. We send out another mail to announce the actual release. So in the context of this mail, we're not talking about Alpha being released, we're talking about it being declared release-able. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Tue, 2012-09-18 at 08:35 -0400, john.flor...@dart.biz wrote: > > From: Adam Williamson > > > > Oh, I should also note that, IIRC, the intent is that the driver > should > > detect if there are no physical buttons and enable tap-to-click in > this > > case. So touchpads which have no buttons and are only supposed to > work > > with tap-to-click should be OK. > > Where does my notebook's touchpad fall in this continuum? At the > bottom corners of the touch-sensitive area are two "buttons" which > click with tactile feedback, but yet are still part of the > touch-sensitive surface. In other words, the bottom corners can > actually be deformed/depressed. FWIW, I enabled tap-to-click -- did I > just answer my own question? -- simply because my wife and I both > found the mouse to be moving off target too often when tried using > these "buttons". As far as evdev is concerned those are almost certainly just perfectly normal buttons, i.e., they send a 'button press' event. The fact that they also function as part of the touch-sensitive surface is probably irrelevant. So evdev would see your touchpad as one with buttons, and wouldn't enable tap-to-click. (I hereby include my permanent disclaimer that I'm just the idiot monkey, and any time someone who's not an idiot monkey comes along and contradicts me, you can confidently assume I'm wrong...so if ajax or whot or someone shows up and says I'm wrong, then I damn well am.) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 18 Alpha is hereby declared GOLD
On Tue, 2012-09-18 at 08:18 +0200, Stijn Hoop wrote: > On Mon, 17 Sep 2012 21:21:00 -0700 > Adam Williamson wrote: > > > On Mon, 2012-09-17 at 22:03 -0400, Matthew Miller wrote: > > > On Tue, Sep 18, 2012 at 12:51:00AM +0200, Björn Persson wrote: > > > > > It's cute, but I think might read a bit bizarre in isolation. > > > > > 'Ready for testing' is terminally boring, but seems safe... > > > > Aren't the terms "alpha" and "beta"? Fedora 18 has been declared > > > > alpha. Before that it was pre-alpha. After some more testing and > > > > fixing it will reach beta status. Right? > > > > > > But how do you say "finalized alpha release" and "finalized beta > > > release", given that these milestones go through a qa and release > > > engineering process themselves? > > > > The Alpha release itself is done now. Alpha is Alpha. Alpha is done. > > All work is towards Beta. We *test* Alpha, but all that testing is > > towards making Beta and Final better. We test Beta, to make Final > > better. But Fedora 18 Alpha is a particular thing that is now done > > and will never change. Fedora 18 Beta will be a particular thing that > > will be done and will never change. The state of F18 a week after the > > Alpha unfreeze is no longer Fedora 18 Alpha. It's something else. > > Yeah but why not rename the _Release_ Candidates as well ? > > As in: > > F18 Pre-Alpha 1 (current TC1) > F18 Pre-Alpha 2 (current TC2) > ... > F18 Pre-Alpha 5 (current RC2) > F18 Alpha > F18 Pre-Beta 1 (current TC1) > ... > F18 Beta > F18 Pre-Release 1 > ... > F18 Release == Gold > > ? > > My EUR 0.02, I don't really care that much about the color of the > bikeshed but this suggestion was the most interesting to me ;-) As I said, that's an active topic within QA as well, but it's probably best to keep the two discussions separate, having them both in one thread will only confuse things. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 18 Alpha is hereby declared GOLD
On Sep 18, 2012, at 12:03 PM, Jesse Keating wrote: > On 09/18/2012 10:16 AM, Chris Murphy wrote: >> I would use the word "RELEASE" instead of TC1, TC2, RC1, RC2. So >> "Fedora 18 Alpha RC3" became "Fedora 18 Alpha Release". It was after >> all a "release candidate" and once no longer a candidate, it is a >> release. >> >> "Completed" adds yet another term that seems unnecessary, albeit >> vastly more appropriate than GOLD or GM. > > I think you missed my point. The announcement is trying to state that we the > project have finished the Alpha, and have begun the staging process to get it > released to the public. It is not released yet, people cannot download it > from our mirror system, so calling it "released" does not make sense. I said release, not released. You're wanting a substitute for GOLD in the phrase "is hereby declared GOLD"? If you're stuck on making a declaration, then ended it with "completed" is fine. But I think "Fedora 18 Alpha Release Criteria have been met" is more clear about what has happened. Something declared completed will imply to some people that alpha as a process is completed, as another person has already mentioned, although it's perhaps a minor confusion. Chris Murphy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: New Anaconda and Mouse Buttons
> From: Przemek Klosowski > To: Development discussions related to Fedora > Date: 09/18/2012 14:09 > Subject: Re: New Anaconda and Mouse Buttons > Sent by: devel-boun...@lists.fedoraproject.org > > On 09/18/2012 01:26 PM, john.flor...@dart.biz wrote: > > > PROPROSED: > > on (button-1-press or button-2-press or button-3-press) of ok_button do: > > commit_changes() > > end; > > I see two problems with this approach: it blocks forever any possibility > of using multiple buttons in Anaconda, and makes it behave differently > from the system it is about to install. I would prefer this: > > on (button-1-press or button-2-press or button-3-press) of ok_button do: > if (button-1-press) do: > commit_changes() > else > ask_if_the_user_wants_to_change_the_mouse_handedness() > end; Very clever. That would float my boat. Anything to avoid using my mouse "backwards" would be highly appreciated. Oddly, I can make the switch into "backward" use quite quickly, but getting back to "normal" latter takes some stumbling. It's almost like having to respond to the name John with one group of people, but Michael to everyone else ... it might not be that bad if nobody else shared those names. -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: New Anaconda and Mouse Buttons
On 09/18/2012 01:26 PM, john.flor...@dart.biz wrote: PROPROSED: on (button-1-press or button-2-press or button-3-press) of ok_button do: commit_changes() end; I see two problems with this approach: it blocks forever any possibility of using multiple buttons in Anaconda, and makes it behave differently from the system it is about to install. I would prefer this: on (button-1-press or button-2-press or button-3-press) of ok_button do: if (button-1-press) do: commit_changes() else ask_if_the_user_wants_to_change_the_mouse_handedness() end; -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: New Anaconda and Mouse Buttons
> From: "Jason L Tibbitts III" > JF> Now, if the mouse pointer could also reverse upon detecting the > JF> apparent handedness of the user, well that would be one of the > JF> coolest UI tricks ever. > > I certainly hope not; I'm left handed and would never dream of switching > the mouse around, given that the standard arrangement is far more > advantageous to left-handed folks than it is to right-handed folks > (since your writing hand is free to actually write). I always assumed > the standard arrangement was simply created by some anonymous lefty in > an attempt to give them (another) advantage over right-handed folks, and > am always baffled when a lefty wants to change it. I see your point, but I only write via keyboard -- I cannot organize anything on a paper and / (search) works poorly there. :-) I do lots of CAD work and drawing with my left hand (via mouse) whilst entering numerics and formulas at the 10-key with my right hand. Like you, I also always assumed this was created by some covert lefty to our advantage. > On to the discussion, asking the user to press the button they usually > use for selecting things does work, but adds yet another step and I can > see the complaints about it now. No, no, no. Please no unnecessary configuration questions for anaconda ... maybe firstboot, but that's another story. I'm merely proposing that anaconda change like so, with this pseudo-code: CURRENTLY: on button-1-press of ok_button do: commit_changes() end; PROPROSED: on (button-1-press or button-2-press or button-3-press) of ok_button do: commit_changes() end; Thus clicking anything clickable in the anaconda UI can be done with any mouse button, regardless of position, orientation, etc.. Once the installation is complete, such preferences can be handled by the DE (GNOME, KDE, etc.) preferences. I'm only proposing that anaconda "feel" already configured as comfortably as the DE when in reality, it's not configured at all. The installer is the one and only place where emulating a Fruity computer's single-button mouse makes sense. Since we can't reduce the number of physical buttons, I propose we reduce the logical number to just one. -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 18 Alpha is hereby declared GOLD
On Sep 17, 2012, at 3:34 PM, Jesse Keating wrote: > Also, the point of marking something as GOLD was that it's ready to be staged > for distribution. GOLD meant Gold Master, that is the master copy was > produced and sent off to the duplicators. Right. The GM refers to the digital version from which the physical stamping plate for mass producing CD/DVD's are made, or the stamping plate itself. Companies, even big ones who had to send out CD's to alpha and beta testers by mail because the software was big enough and the internet slow enough, never made mass produced CD's for software. The were in-house made by burning, not stamping. i.e. there was no GM. The term GM or GOLD is simply inapplicable to alphas and betas. > "Ready for testing" doesn't quite embody that same idea. Good. It shouldn't. > "Completed" seems to make some sense, the Alpha has been completed and is now > being staged for release. I would use the word "RELEASE" instead of TC1, TC2, RC1, RC2. So "Fedora 18 Alpha RC3" became "Fedora 18 Alpha Release". It was after all a "release candidate" and once no longer a candidate, it is a release. "Completed" adds yet another term that seems unnecessary, albeit vastly more appropriate than GOLD or GM. Chris Murphy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning: mtpfs (FUSE filesystem for MTP devices like Android tablets)
On Seg, 2012-09-17 at 14:15 +0100, Richard W.M. Jones wrote: > (3) I don't use it any more. I just gave up trying to get files off > Android tablets. WTF don't they support USB mass storage like every > other thing out there? Android 2.1 and 2.3 have "USB mass storage" has option. But this holidays , I try transfer photos from a friend machine and others situation Canon , Nokia , JVC all by default use MTP, this fuse mtp should IMHO be a default in ours Fedora system. I had no idea of their existence ( mtpfs) I going to test it now. Thanks, Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: New Anaconda and Mouse Buttons
> "JF" == John Florian writes: JF> Now, if the mouse pointer could also reverse upon detecting the JF> apparent handedness of the user, well that would be one of the JF> coolest UI tricks ever. I certainly hope not; I'm left handed and would never dream of switching the mouse around, given that the standard arrangement is far more advantageous to left-handed folks than it is to right-handed folks (since your writing hand is free to actually write). I always assumed the standard arrangement was simply created by some anonymous lefty in an attempt to give them (another) advantage over right-handed folks, and am always baffled when a lefty wants to change it. On to the discussion, asking the user to press the button they usually use for selecting things does work, but adds yet another step and I can see the complaints about it now. - J< -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
New Anaconda and Mouse Buttons
I haven't had a chance yet to try the new F18 installer and barely have had a chance to play with my F17->F18 upgrade box. However, I'm most curious if the new installer has considered or already gained what I'd consider a subtle improvement in becoming mouse button agnostic. I'm a "lefty" (handedness, not politically which doesn't belong here) and always reverse my button order so that their arrangement is as natural to me as they are for a "righty" in that the button closest to the keyboard is the primary button. In the past, Anaconda had no need for more than one button, so why not treat all buttons as equals? In other words, any mouse button click should be handled identically. Now, if the mouse pointer could also reverse upon detecting the apparent handedness of the user, well that would be one of the coolest UI tricks ever. (Oh and while I'm dreaming, might as well magically change all UI labels and documentation for mouse buttons to be 1st, 2nd, 3rd, etc. instead of "left", "right", "middle".) I've been adapting all my life, so I won't be too disappointed if none of this materializes. -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
> From: mike cloaked > >> From: Florian Müllner > > Any ideas on the equivalent for KDM? > > > > Why not enable it in xorg itself - from memory you can look for a file > like /etc/X11/xorg.conf.d/10-synaptics.conf (or possibly in > /usr/share/X11/xorg.conf.d/50-synaptics.conf or similar) > > Then ensure that you have a section like: > > Section "InputClass" > Identifier "touchpad catchall" > Driver "synaptics" > MatchIsTouchpad "on" > MatchDevicePath "/dev/input/event*" > Option "TapButton1" "1" > Option "TapButton2" "2" > Option "TapButton3" "3" > Option "VertEdgeScroll" "on" > EndSection > > When you boot you should have touchpad buttons available even at the > KDM greeter stage for login - (I guess same for GDM though I am a KDE > user only) Perfect! I'll give that a try soon, but it looks just like what I wanted. I figured there was something like this, but hadn't snooped around yet -- this will save me much time. Thanks! > I have been doing this for several years with my laptops I'm relatively new to owning a laptop. Used them for years at work but those were bungled with Windoze. Win7 lived all of about 5m on my Samsung before something worthwhile (F17) was installed after which it immediately soared in value by a factor of nearly infinity. :-) -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] Announcing the release of Fedora 18 Alpha!!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Fedora 18 "Spherical Cow" Alpha release is plumping up! This release offers a preview of some of the best free and open source technology currently under development. Model a glimpse of the future: http://fedoraproject.org/get-prerelease Already mooo-tivated to give F18 Alpha a try? Great! We still hope that you'll read onwards; there are fabulous features in this release you may want to know about, as well as important information regarding specific, common F18 Alpha installation issues and bugs, all of which are detailed in this release announcement. *** What is the Alpha Release? *** Fedora 18 adds many new and improved features for a variety of audiences. A small sample is included below; the full list of features for this release can be seen on the Fedora 18 Feature List, here: http://fedoraproject.org/wiki/FeatureList = On the Desktop = * NetworkManager Hotspots improve the ability to use a computer's WiFi adapter to create a network hot spot. * The redesigned installation system adds flexibility to the installation process while simplifying the user interface. * Desktop updates galore: Gnome 3.6, KDE Plasma Workspace 4.9, Xfce 4.10, Sugar 0.98, and the introduction of the MATE Desktop in Fedora. = For sysadmins = * The Riak NoSQL database, a fault-tolerant and scalable database system, is included for the first time in Fedora 18. * Samba 4 adds SMB3 support and support for FreeIPA trusted domains. * Offline system updates adds support for installing OS packages at boot. This gives systems administrators the ability to upgrade important libraries in a controlled manner. * Fedora 18 will be able to easily join an Active Directory domain or FreeIPA realm. = For developers = * The Python 3 stack is upgraded to version 3.3. * Rails is upgraded from version 3.0 to version 3.2. * Perl 5.16 adds Unicode 6.1 support. * Power7 optimized ppc64p7 is added as a supported platform for Fedora 18 packages. = Cloud and Virtualization = * OpenShift Origin brings Platform as a Service (PaaS) infrastructure to Fedora. * Eucalyptus gives Fedora the ability to support private, AWS-compatible Infrastructure as a Service (IaaS) clouds. * Fedora 18 Alpha's OpenStack packages are synchronized with "Folsom," the OpenStack release due near the end of September. * Heat provides an API for orchestration of cloud applications using file- or web-based templates, enabling a standardized method for OpenStack users to launch applications in an OpenStack cloud. It is currently an OpenStack related project. * Virt Live Snapshots adds the ability to perform snapshots of QEMU and libvirt virtual machines without having to stop the guest. * The oVirt Engine is upgraded to version 3.1 and adds GUI tools. *** Known Issues and Bugs *** We know that many of you are moo-tivated to download and try the Alpha release of "Spherical Cow"; to help you avoid stepping into any sticky issues, we'd like to highlight a few specific issues, before you mve on to the downloads page. Information about these, and other common bugs, including bug reports and workarounds for known issues where available, are detailed on the Common F18 Bugs page, as well as in the Alpha release notes; links to both pages are provided below. * Utilizing automatic partitioning during installation will reformat all selected disks on which to install without any further warning; ALL EXISTING DATA ON THE DISKS WILL BE LOST. At this time, there is no option presented to use free space on the disks, or to resize existing partitions. A workaround solution exists. * Some NVIDIA graphics adapters will have problems with the start or display of the login manager or the desktop. This will prevent the user from reaching a usable desktop, when booting the live image or an installed system. In these cases, the login manager and/or desktop may fail to appear at all, or may appear but with the cursor missing, and/or visual corruption issues. * This release features a new user interface for the anaconda installer, which will significantly enhance the end-user installation experience. Known issues relating to the new installer user interface include: ** For non-graphical installations, a root password must be set to be able to login; for graphical installations, the first user should be set as an adminstrative user. This is currently the default setup during installation. ** There is no anaconda-based upgrade or preupgrade to F18 Alpha; if you must upgrade an installed system, you should use yum. ** The new installer user interface is still undergoing work; the Alpha release may not necessarily duplicate exactly the implementation seen in the Final release of Fedora 18 in November. For more information, including information about other common and known bugs, tips on how to report bugs, and the official release schedule,
Re: Why is not enabled TapButton of touchpad on Fedora by default?
If you do not like touchpad. Can disable on your laptop with Fn keys. However who can use it need edit somefiles...add code to uses it So. I never occurs that I pushed my finger accidentaly and moved cursor. Lol On Sep 18, 2012 2:16 PM, "Álvaro Castillo" wrote: > Yest... Need edit files to use something as touchpad :) > On Sep 18, 2012 2:11 PM, "mike cloaked" wrote: > >> On Tue, Sep 18, 2012 at 1:55 PM, wrote: >> > devel-boun...@lists.fedoraproject.org wrote on 09/18/2012 08:09:33: >> > >> >> From: Florian Müllner >> >> To: Development discussions related to Fedora >> >> >> >> Date: 09/18/2012 08:10 >> >> Subject: Re: Why is not enabled TapButton of touchpad on Fedora by >> >> default? >> >> Sent by: devel-boun...@lists.fedoraproject.org >> >> >> >> On Tue, Sep 18, 2012 at 11:41 AM, Camilo Mesias >> >> wrote: >> >> > I always enable the feature but it is an ongoing annoyance that it is >> >> > disabled at GDM, is there any way to force it to default to on for >> the >> >> > whole system? >> >> >> >> I have the following in /etc/dconf/db/gdm.d/10-local-settings: >> >> >> >> [org/gnome/settings-daemon/plugins/mouse] >> >> active=true >> >> >> >> [org/gnome/settings-daemon/peripherals/touchpad] >> >> tap-to-click=true >> >> >> >> You will need to run "dconf update" as root for the change to take >> effect. >> >> >> >> >> >> Regards, >> >> Florian >> >> -- >> >> devel mailing list >> >> devel@lists.fedoraproject.org >> >> https://admin.fedoraproject.org/mailman/listinfo/devel >> > >> > >> > Any ideas on the equivalent for KDM? >> > >> >> Why not enable it in xorg itself - from memory you can look for a file >> like /etc/X11/xorg.conf.d/10-synaptics.conf (or possibly in >> /usr/share/X11/xorg.conf.d/50-synaptics.conf or similar) >> >> Then ensure that you have a section like: >> >> Section "InputClass" >> Identifier "touchpad catchall" >> Driver "synaptics" >> MatchIsTouchpad "on" >> MatchDevicePath "/dev/input/event*" >> Option "TapButton1" "1" >> Option "TapButton2" "2" >> Option "TapButton3" "3" >> Option "VertEdgeScroll" "on" >> EndSection >> >> When you boot you should have touchpad buttons available even at the >> KDM greeter stage for login - (I guess same for GDM though I am a KDE >> user only) >> >> I have been doing this for several years with my laptops >> >> >> -- >> mike c >> -- >> devel mailing list >> devel@lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/devel > > -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
Yest... Need edit files to use something as touchpad :) On Sep 18, 2012 2:11 PM, "mike cloaked" wrote: > On Tue, Sep 18, 2012 at 1:55 PM, wrote: > > devel-boun...@lists.fedoraproject.org wrote on 09/18/2012 08:09:33: > > > >> From: Florian Müllner > >> To: Development discussions related to Fedora > >> > >> Date: 09/18/2012 08:10 > >> Subject: Re: Why is not enabled TapButton of touchpad on Fedora by > >> default? > >> Sent by: devel-boun...@lists.fedoraproject.org > >> > >> On Tue, Sep 18, 2012 at 11:41 AM, Camilo Mesias > >> wrote: > >> > I always enable the feature but it is an ongoing annoyance that it is > >> > disabled at GDM, is there any way to force it to default to on for the > >> > whole system? > >> > >> I have the following in /etc/dconf/db/gdm.d/10-local-settings: > >> > >> [org/gnome/settings-daemon/plugins/mouse] > >> active=true > >> > >> [org/gnome/settings-daemon/peripherals/touchpad] > >> tap-to-click=true > >> > >> You will need to run "dconf update" as root for the change to take > effect. > >> > >> > >> Regards, > >> Florian > >> -- > >> devel mailing list > >> devel@lists.fedoraproject.org > >> https://admin.fedoraproject.org/mailman/listinfo/devel > > > > > > Any ideas on the equivalent for KDM? > > > > Why not enable it in xorg itself - from memory you can look for a file > like /etc/X11/xorg.conf.d/10-synaptics.conf (or possibly in > /usr/share/X11/xorg.conf.d/50-synaptics.conf or similar) > > Then ensure that you have a section like: > > Section "InputClass" > Identifier "touchpad catchall" > Driver "synaptics" > MatchIsTouchpad "on" > MatchDevicePath "/dev/input/event*" > Option "TapButton1" "1" > Option "TapButton2" "2" > Option "TapButton3" "3" > Option "VertEdgeScroll" "on" > EndSection > > When you boot you should have touchpad buttons available even at the > KDM greeter stage for login - (I guess same for GDM though I am a KDE > user only) > > I have been doing this for several years with my laptops > > > -- > mike c > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Tue, Sep 18, 2012 at 1:55 PM, wrote: > devel-boun...@lists.fedoraproject.org wrote on 09/18/2012 08:09:33: > >> From: Florian Müllner >> To: Development discussions related to Fedora >> >> Date: 09/18/2012 08:10 >> Subject: Re: Why is not enabled TapButton of touchpad on Fedora by >> default? >> Sent by: devel-boun...@lists.fedoraproject.org >> >> On Tue, Sep 18, 2012 at 11:41 AM, Camilo Mesias >> wrote: >> > I always enable the feature but it is an ongoing annoyance that it is >> > disabled at GDM, is there any way to force it to default to on for the >> > whole system? >> >> I have the following in /etc/dconf/db/gdm.d/10-local-settings: >> >> [org/gnome/settings-daemon/plugins/mouse] >> active=true >> >> [org/gnome/settings-daemon/peripherals/touchpad] >> tap-to-click=true >> >> You will need to run "dconf update" as root for the change to take effect. >> >> >> Regards, >> Florian >> -- >> devel mailing list >> devel@lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/devel > > > Any ideas on the equivalent for KDM? > Why not enable it in xorg itself - from memory you can look for a file like /etc/X11/xorg.conf.d/10-synaptics.conf (or possibly in /usr/share/X11/xorg.conf.d/50-synaptics.conf or similar) Then ensure that you have a section like: Section "InputClass" Identifier "touchpad catchall" Driver "synaptics" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "TapButton1" "1" Option "TapButton2" "2" Option "TapButton3" "3" Option "VertEdgeScroll" "on" EndSection When you boot you should have touchpad buttons available even at the KDM greeter stage for login - (I guess same for GDM though I am a KDE user only) I have been doing this for several years with my laptops -- mike c -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
> From: Nicola Soranzo > Il giorno mar, 18/09/2012 alle 08.35 -0400, john.flor...@dart.biz ha > scritto: > > > From: Adam Williamson > > > > > > Oh, I should also note that, IIRC, the intent is that the driver > > should > > > detect if there are no physical buttons and enable tap-to-click in > > this > > > case. So touchpads which have no buttons and are only supposed to > > work > > > with tap-to-click should be OK. > > > > Where does my notebook's touchpad fall in this continuum? At the > > bottom corners of the touch-sensitive area are two "buttons" which > > click with tactile feedback, but yet are still part of the > > touch-sensitive surface. In other words, the bottom corners can > > actually be deformed/depressed. FWIW, I enabled tap-to-click -- did I > > just answer my own question? -- simply because my wife and I both > > found the mouse to be moving off target too often when tried using > > these "buttons". > > It's called a ClickPad, it's supported in X.org released with F17. > > Nicola Oh! Thanks for that info. Indeed we're running F17 on it (Samsung 5 series IIRC) without any issues at all. Fedora may work great on it, but this old dog isn't adapting so well to the new tricks of these touchy-clicky things. Oh well, praise be the new days where it all just works vs. the old days where you prayed the most critical bits worked. =) -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Sep 18, 2012 2:56 PM, wrote: > Any ideas on the equivalent for KDM? No, sorry. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
Il giorno mar, 18/09/2012 alle 08.35 -0400, john.flor...@dart.biz ha scritto: > > From: Adam Williamson > > > > Oh, I should also note that, IIRC, the intent is that the driver > should > > detect if there are no physical buttons and enable tap-to-click in > this > > case. So touchpads which have no buttons and are only supposed to > work > > with tap-to-click should be OK. > > Where does my notebook's touchpad fall in this continuum? At the > bottom corners of the touch-sensitive area are two "buttons" which > click with tactile feedback, but yet are still part of the > touch-sensitive surface. In other words, the bottom corners can > actually be deformed/depressed. FWIW, I enabled tap-to-click -- did I > just answer my own question? -- simply because my wife and I both > found the mouse to be moving off target too often when tried using > these "buttons". It's called a ClickPad, it's supported in X.org released with F17. Nicola -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
devel-boun...@lists.fedoraproject.org wrote on 09/18/2012 08:09:33: > From: Florian Müllner > To: Development discussions related to Fedora > Date: 09/18/2012 08:10 > Subject: Re: Why is not enabled TapButton of touchpad on Fedora by default? > Sent by: devel-boun...@lists.fedoraproject.org > > On Tue, Sep 18, 2012 at 11:41 AM, Camilo Mesias wrote: > > I always enable the feature but it is an ongoing annoyance that it is > > disabled at GDM, is there any way to force it to default to on for the > > whole system? > > I have the following in /etc/dconf/db/gdm.d/10-local-settings: > > [org/gnome/settings-daemon/plugins/mouse] > active=true > > [org/gnome/settings-daemon/peripherals/touchpad] > tap-to-click=true > > You will need to run "dconf update" as root for the change to take effect. > > > Regards, > Florian > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel Any ideas on the equivalent for KDM? -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Broken dependencies: perl-OpenOffice-UNO
perl-OpenOffice-UNO has broken dependencies in the rawhide tree: On x86_64: perl-OpenOffice-UNO-0.07-3.fc17.x86_64 requires perl(:MODULE_COMPAT_5.14.2) On i386: perl-OpenOffice-UNO-0.07-3.fc17.i686 requires perl(:MODULE_COMPAT_5.14.2) perl-OpenOffice-UNO-0.07-3.fc17.i686 requires libsal_textenc.so Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: [Test-Announce] Fedora 18 Alpha is hereby declared GOLD
devel-boun...@lists.fedoraproject.org wrote on 09/18/2012 02:18:31: > From: Stijn Hoop > To: Development discussions related to Fedora > Date: 09/18/2012 02:18 > Subject: Re: [Test-Announce] Fedora 18 Alpha is hereby declared GOLD > Sent by: devel-boun...@lists.fedoraproject.org > > On Mon, 17 Sep 2012 21:21:00 -0700 > Adam Williamson wrote: > > > On Mon, 2012-09-17 at 22:03 -0400, Matthew Miller wrote: > > > On Tue, Sep 18, 2012 at 12:51:00AM +0200, Björn Persson wrote: > > > > > It's cute, but I think might read a bit bizarre in isolation. > > > > > 'Ready for testing' is terminally boring, but seems safe... > > > > Aren't the terms "alpha" and "beta"? Fedora 18 has been declared > > > > alpha. Before that it was pre-alpha. After some more testing and > > > > fixing it will reach beta status. Right? > > > > > > But how do you say "finalized alpha release" and "finalized beta > > > release", given that these milestones go through a qa and release > > > engineering process themselves? > > > > The Alpha release itself is done now. Alpha is Alpha. Alpha is done. > > All work is towards Beta. We *test* Alpha, but all that testing is > > towards making Beta and Final better. We test Beta, to make Final > > better. But Fedora 18 Alpha is a particular thing that is now done > > and will never change. Fedora 18 Beta will be a particular thing that > > will be done and will never change. The state of F18 a week after the > > Alpha unfreeze is no longer Fedora 18 Alpha. It's something else. > > Yeah but why not rename the _Release_ Candidates as well ? > > As in: > > F18 Pre-Alpha 1 (current TC1) > F18 Pre-Alpha 2 (current TC2) > ... > F18 Pre-Alpha 5 (current RC2) > F18 Alpha > F18 Pre-Beta 1 (current TC1) > ... > F18 Beta > F18 Pre-Release 1 > ... > F18 Release == Gold > > ? > > My EUR 0.02, I don't really care that much about the color of the > bikeshed but this suggestion was the most interesting to me ;-) > > --Stijn > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel That's the simplest, easiest to understand (without referencing a wiki for definitions) option I've seen proposed yet. -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
> From: Adam Williamson > > Oh, I should also note that, IIRC, the intent is that the driver should > detect if there are no physical buttons and enable tap-to-click in this > case. So touchpads which have no buttons and are only supposed to work > with tap-to-click should be OK. Where does my notebook's touchpad fall in this continuum? At the bottom corners of the touch-sensitive area are two "buttons" which click with tactile feedback, but yet are still part of the touch-sensitive surface. In other words, the bottom corners can actually be deformed/depressed. FWIW, I enabled tap-to-click -- did I just answer my own question? -- simply because my wife and I both found the mouse to be moving off target too often when tried using these "buttons". -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
On Tue, Sep 18, 2012 at 11:41 AM, Camilo Mesias wrote: > I always enable the feature but it is an ongoing annoyance that it is > disabled at GDM, is there any way to force it to default to on for the > whole system? I have the following in /etc/dconf/db/gdm.d/10-local-settings: [org/gnome/settings-daemon/plugins/mouse] active=true [org/gnome/settings-daemon/peripherals/touchpad] tap-to-click=true You will need to run "dconf update" as root for the change to take effect. Regards, Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: XtreemFS on Fedora
Quoting Renich Bon Ciric (2012-09-17 15:29:46) > Hello guys! > > I'm interested in packaging XtreemFS for Fedora. They're BSD and the > project pretty good; even if it's java-based; it works fine with > openjdk. It's a EU project, it seems. > > I'm not proficient in java but I have been using this one and know it well. > > And, besides, the developers are very friendly and all. They, also, > have RPMs for F16: > http://download.opensuse.org/repositories/home:/xtreemfs/Fedora_16/ > > I'd love it if somebody proficient in java would join to help co-maintain. > > I sent an email just like this one to the java-devel list. Please, > forgive the repost. I can't really help with comaintaining, but in Fedora/Java land we quite often solve problems as a group. So if you'll hit specific problems with the package and send email to java-devel (or drop by #fedora-java at the right time), someone will help out. We have quite a few provenpackagers and unwritten agreement between most of us that we fix up each other's packages. Unless the package has big dependency changes between releases, the maintenance burden should be pretty small. It seems only the server part is Java and it has close to zero dependencies (except protobuf, which we have in fedora). You should be able to build it without problem. If you don't feel comfortable, don't build the Java/server part and someone can create server subpackage patches once the package is in Fedora. Good luck! -- Stanislav Ochotnicky Software Engineer - Base Operating Systems Brno PGP: 7B087241 Red Hat Inc. http://cz.redhat.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning: mtpfs (FUSE filesystem for MTP devices like Android tablets)
Richard W.M. Jones wrote: > > I've orphaned this package. There are various > reasons for this: > > (1) It's buggy: https://admin.fedoraproject.org/pkgdb/acls/bugs/mtpfs > > (2) Upstream is not responsive. The weight of developer effort seems > to have moved to several alternative projects, and it's probably > worthwhile adopting one of these and deprecating mtpfs. > https://bugzilla.redhat.com/show_bug.cgi?id=841260#c1 > > (3) I don't use it any more. I just gave up trying to get files off > Android tablets. WTF don't they support USB mass storage like every > other thing out there? > > Rich. > I gave up on usb transfer - just use airdroid instead. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why is not enabled TapButton of touchpad on Fedora by default?
Hi, On Tue, Sep 18, 2012 at 1:32 AM, Kevin Kofler wrote: > I don't >> understand why people want that annoying "feature" at all. It's a mistake to project your annoyance with a given feature onto the masses. I always enable the feature but it is an ongoing annoyance that it is disabled at GDM, is there any way to force it to default to on for the whole system? I find it's great for quiet clicking and is easier on the fingers than clicking a physical button. Also it's much better user experience to click somewhere you finger already is than to look down for a button or reposition by touch (given that there are often two physical buttons). Also I use several laptops and the button arrangement is always subtly different, if I can tap to click on all of them, it's a big usability win. -Cam -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 18 Alpha is hereby declared GOLD
- Original Message - > On Thu, 2012-09-13 at 17:07 -0400, Jaroslav Reznik wrote: > > At the F18 Alpha Go/No-Go Meeting that just occurred, the Fedora 18 > > Alpha release was declared GOLD. F18 Alpha will be released > > Tuesday, > > September 18, 2012. > > It's been suggested that we should stop using 'GOLD' when talking > about > Alpha and Beta, and I think this is right. Only final releases should > be > said to have gone 'gold' - this is how the term is generally > understood, > and using it for Alpha and Beta releases confuses people as to their > status. Jaroslav, what needs to happen for the term not to be used > for > F18 Beta and future Alpha / Beta releases? For Alpha, I used GOLD as used in the past but I'm open to a new wording. I like "Public Alpha"/"Public Beta" as suggested in the thread. I talked to a few people around and they use it. Public Alpha = latest RC compose used for redistribution/mirroring Public Alpha Availability = the date when Public Alpha is available (we currently call it "Alpha Public Availability" in schedules). I was checking schedules - the GOLD is not used there, so from this point, there's no problem. It has to be fixed in announcement, my job :) For TC/RC - I'm ok with it. Even for alpha/beta RC means release candidate - something that's going to be released to the wild. Instead of TC snapshot #x could be used but TC really means - use it for testing, there's no confusion. Funny story: one friend understood "is hereby declared GOLD" as "wow, Spherical Cow was renamed to GOLD?". R. > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora > http://www.happyassassin.net > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
