I did two installs yesterday, and both of them have ended up with
SELINUX=disabled in /etc/selinux/config
I changed them back to 'enabled', rebooted, which caused a relabel,
and all seems fine.
What's happening here ?
Dave
I've just built a new F12 DeviceKit-power package[1] in koji which
should be in tomorrows rawhide. This should fix some of the issues
people were having with adding and removing devices. Please can you
give this build a test, and please then reply if it either fixes a
problem you were having with the old build, or if it causes a
regression and breaks something that worked before. Thanks.
Richard.
[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=131863
Hi,
I wanted to be a good packager and include the upstream CHANGELOG lines
in the update notes of bsf-2.4.0, but bodhi does not accept empty lines
(error) nor linebreaks (ignored). How is that text supposed to be
formatted?
regards
Christoph
You (spot) said:
"undo arch-specific deps on gecko-libs and java (%%{?isa} doesn't work
like you think it works)"
Unless I was told the wrong things in this thread:
https://www.redhat.com/archives/fedora-devel-list/2009-July/msg01366.html
... it *does* work like I think it works. xulrunner and openjdk are
broken.
AFAICT, no one who's actually looks at this disputes that the
aforementioned packages are broken. There is some resistance to fixing
them (for reasons I do not entirely agree with).
As it stands, though your changes fix a dependency problem, they make
the specfile less correct and openvrml is susceptible to the problem
documented in the aforementioned fedora-devel thread. It would be
better if xulrunner and openjdk were fixed instead (bugs 517665 and
517666, respectively).
--
Braden McDaniel <braden(a)endoframe.com>
I went over to https://translate.fedoraproject.org/ earlier with the
idea of adding my project. Firstly, there's no hint of how to do this
from the front page. After some Leisure Suit Larry style clicking on
stuff at random until something favourable happens, I found a link
carefully hidden at the bottom of the browse all projects page. The link
says:
Couldn't find your project? Go ahead and <a>add it</a>!
So, I clicked in 'add it', which gives me:
===
Forbidden access
Looks like you do not have the necessary permissions to the required action.
Here's a link to the homepage. You know, just in case.
===
That's everything, btw. No link to an admin contact, process, mailing
list, documentation, or anything. Just a promise of being able to add my
project, then a bucket of cold water.
Despite that, I'd still like to add my project to Transifex! Can anybody
point me to the process?
Thanks,
Matt
Yes, it is now that legendary time, well loved by the hearts of men for
millennia(*): Graphics Test Week!
Tomorrow - 2009-09-09 - is ATI/AMD Radeon graphics card Test Day (1).
Thursday - 2009-09-10 - is NVIDIA graphics card Test Day (2). And Friday
- 2009-09-11 - is Intel graphics card Test Day (3). I am currently
rolling up a pair of live CD images that will likely be used for all
three days; they should be uploaded soon. Please, please grab the live
CDs, do the testing, and come out to the Test Day(s) for the graphics
hardware you own! As always, graphics are a critical piece of Fedora and
we want to make sure Fedora 12 works on as wide a range of graphics
hardware as possible.
The testing's very easy to do and it shouldn't take more than an hour of
your time to boot the live CD and run the tests. There's no need to
install anything to hard disk. You don't even need to be a Fedora user
to take part, and what's in Fedora's drivers today will be in everyone
else's tomorrow, so helping us test this benefits all distributions down
the road.
The Test Day gatherings themselves are held in IRC, in channel
#fedora-test-day on the Freenode network. Please do join in if you can -
we can help advise you with any questions you have, and if you run into
bugs, the developers can investigate them with you right away. If you
can't make it out for the actual day, though, you can still do the
testing, and your results are still useful! Just download the live
image, do the tests, and fill in the results table as the page
instructs. Many thanks to everyone who's able to make it out and do the
testing. Remember - tomorrow ATI; Thursday NVIDIA; Friday Intel.
* - well, okay. Not really millennia. More like...months.
(1) - https://fedoraproject.org/wiki/Test_Day:2009-09-09_Radeon
(2) - https://fedoraproject.org/wiki/Test_Day:2009-09-10_Nouveau
(3) - https://fedoraproject.org/wiki/Test_Day:2009-09-11_Intel
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
Hi,
The Beta release notes is a important source of information for our
users, testers, ambassadors, even fellow developers and press for that
release. So I am asking you all to help you a bit. Here is how:
I have "open sourced" my process of finding information and my notes and
copied over all that information to
https://fedoraproject.org/wiki/Fedora_12_Beta_release_notes
If you don't have much time, take one item in this list and add more
information. I will also help you avoid even clicking on a link and copy
the same information below:
Quick notes:
* Hybrid ISO - earlier revision in Alpha release notes history. Confirm
that it works well before adding it here
* Status of http://www.ing.unibs.it/openfwwf/ in Fedora? How well does
it work?
* Moblin - Explain in detail with potentially a screencast
* GNOME Shell - Ogg Screencast possibly with voice over
* Yum Presto - In GNOME and KDE groups. What about delta rpm generation?
* http://live.gnome.org/GTK%2B/ClientSideWindows - Eclipse and Adobe
Reader needs a workaround
* Abrt - whats the status?
* Anaconda MDRaid - Explain in detail
* Lower Process Capabilities
* Contact KDE SIG and gather important changes. Phonon has changed to
gstreamer backend in Alpha release and was not mentioned. So call it out
in the Beta release.
Additional sources:
* Look at F11 Preview release notes and use it as a template. It matches
the beta this release because of rel eng decision to tweak the release
process a bit
* Read rawhide reports in between alpha and beta release for new
packages as well as import changes worth noting here
* Quickly skimp through all threads in fedora-devel and fedora-test list
for note worthy changes
* Read Planet Fedora and reference developer blogs when important
changes are mentioned
* Consult with QA team and make sure note worth issues are mentioned. If
anything needs explicit testing, highlight it
* More details at
https://fedoraproject.org/wiki/Releases/12/FeatureList. Read the release
notes section of each of the approved feature
Thanks.
Rahul