Difficulties testing the new nouveau driver
by Richard Hughes
As some of you may know I've been packaging and testing nouveau (the
free NVIDIA 3D driver) for some time. The current way the driver is
packaged is making things very difficult to properly test on fedora:
* The xf86-video-nv-2.1.5.tar.bz2 and nouveau-gitID.tar.gz are included
in the xorg-x11-drv-nv-2.1.5 srpm.
* This srpm spits out xorg-x11-drv-nv-2.1.5 and
xorg-x11-drv-nouveau-2.1.5 rpm files when built.
This poses me problems as:
* I can't easily keep the original nv rpm intact when building the new
nouveau
* The upstream version of nouveau ddx is 1.2.0, and the rpm version is
2.1.5
* I can't uninstall the xorg-x11-drv-nv driver to test nouveau from
source without nuking the nv driver too.
I understand that one day the nouveau ddx will replace the nv ddx, but
this can be accomplished with standard rpm obsoletes rather than
shipping the nouveau source in the nv srpm. For me, I think the proper
way of doing this would be to:
* Have a nouveau srpm *and* a nv srpm - they are different codebases and
have different version numbers
* Somehow fix the brokenness that has lead to the version number
xorg-x11-drv-nouveau-2.1.5 being installed when actually installed was
xorg-x11-drv-nouveau-1.2.0
Ideas welcome.
Richard.
16 years, 2 months
Orphaning packages
by Paul F. Johnson
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....
TTFN
Paul
--
Get your free @ukpost.com account now
http://www.ukpost.com/
16 years, 2 months
Fedora 8 installation crash
by Thomas Swan
I don't think this is just you. When trying to install F8 on an HP laptop
(in text mode)
loader received SIGSEGV! Backtrace:
[0x804a030]
[0x110420]
[0x81a3f42]
[0x805b750]
[0x805c153]
[0x804b207]
[0x8175004]
0x8048151]
Installing in graphical mode yields the following error messages:
*** glibc detected *** /sbin/loader: munmap_chunk(): invalid pointer:
0x0850c810
=== Backgrace: ===
[0x81a4083]
[0x805b750]
[0x805c153]
[0x804b207]
[0x8175004]
[0x8048151]
======= Memory map =======
00110000-00111000 r-xp 001110000 00:00 0 [vdso]
08048000-0828e000 r-xp 00000000 00:01 36 /sbin/loader
0828e000-08299000 rw-p 00245000 00:01 36 /sbin/loader
08299000-082d3000 rw-p 08299000 00:00 0
0849b000-08589000 rw-p 0849b000 00:00 0
b7f36000-b7f39000 rw-p b7f36000 00:00 0
bfedb000-bfef0000 rw-p bffea000 00:00 0
loader received a SIGABRT! Backtrace:
[0x804a030]
[0x110420]
[0x81e7f80]
[0x8182a30]
[0x819930b]
[0x81a4003]
[0x805b750]
[0x805c153]
[0x804b207]
[0x8175004]
[0x8048151]
install exited abnormally [1/1]
This exact same problem happens when installing from known good media on
both USB DVD drives and the local dvd drive.
I am using the Fedora-8-i386-DVD.iso. Memtest has been run on this system
and there are no memory errors.
This doesn't seem to be isolated. <
http://www.nabble.com/F8-Installation-Issue---Second-Try-tf4806216.html#a...
>
--
The early bird may get the worm, but the it's the second mouse that gets the
cheese.
16 years, 2 months
Firefox 3 Beta 2 in Rawhide
by Martin Stransky
Hello,
Firefox 3 has finally landed in Rawhide. It's a slightly unpolished
version and we appreciate if you test it and report all issues to
bugzilla (like missing locales, broken plugins and so on).
If you're interested and don't want to switch to rawhide, you can run
Firefox 3 on Fedora 8, too. Just download and compile the latest
xulrunner (xulrunner-1.9-0.beta2.1.fc9) and then compile and install
firefox from rawhide.
There's one side effect of this update. The former firefox-devel package
has been removed from rawhide and gecko-libs 1.8 is no more shipped. All
packages have to run with xulrunner (gecko-libs 1.9) now.
If you're a package maintainer and your package already uses xulrunner,
please rebuild it against the new rawhide version. Xulrunner directory
has been changed and many gecko packages (if not all) are linked with
--rpath linker directive. As long as rpath is used you have to rebuild
gecko-libs based packages after each xulrunner change so please consider
to remove it. Gecko libraries are registered system wide by
/etc/ld.so.conf.d and rpath should not be necessary in rawhide.
Happy testing&hacking! :)
ma.
16 years, 2 months
network manager command-line control?
by Matthew Miller
I want to make sure I'm not missing something before I file an RFE. I'd like
to be able to enable/disable wireless (or wired, for that matter) networking
from scripts. The nm-tool program seems like the logical place for this
functionality, but it doesn't appear to actually have it at this point.
Specifically, my laptop generates a custom Sony ACPI button event when the
wireless antenna is switched on or off -- I'd like to automatically enable
or disable wireless networking correspondingly. Is there an easy way to do
this that I'm just not seeing? Thanks.
(Also, is there a way to supress the pop-up messages about changes in
connections status? I find them more obtrusive and distracting than
helpful.)
--
Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>
16 years, 3 months
Python Eggs & distutils in Rawhide
by Toshio Kuratomi
Just a small heads up for those of you packaging python modules.
python-2.5.1-18, just built for rawhide, has reverted a small patch we
were carrying that disabled generation of egg-info for modules created
by distutils. That means that python modules built against rawhide will
now create an extra file of metadata in the python_sitelib and
python_sitearch directories. You'll need to include those in your
%files section if it's not already pulled in via a wildcard.
For more information on what these files give us, take a look at the
Python Egg Guidelines on:
http://fedoraproject.org/wiki/Packaging/Python/Eggs
-Toshio
_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce
16 years, 3 months
Renaming anjuta-gdl to libgdl
by Debarshi Ray
I propose to rename the anjuta-gdl package to lbgdl.
The prefix anjuta- seems to imply that the package is dependent on the
main anjuta (owned by me) package , which is not the case. In fact, it
is the other way round. Even then, it is not anjuta specific and being
the GNOME Devtools Library which can be used by other applications
also.
Currently the gnome-python2-gdl (owned by Matthew Barnes) package
provides Python bindings to this library, and would be affected by
this change. The gnome-build (previously held by Paul F. Johnson)
package also depends on anjuta-gdl.
$ repoquery --repoid development --alldeps --whatrequires anjuta-gdl
gnome-build-0:0.1.4-2.fc7.x86_64
anjuta-gdl-devel-0:0.7.3-2.fc9.x86_64
anjuta-gdl-0:0.7.3-2.fc9.i386
gnome-build-0:0.1.4-2.fc7.i386
anjuta-1:2.2.0-4.fc9.i386
anjuta-1:2.2.0-4.fc9.x86_64
gnome-python2-gdl-0:2.19.1-12.fc9.x86_64
anjuta-gdl-devel-0:0.7.3-2.fc9.i386
anjuta-gdl-0:0.7.3-2.fc9.x86_64
The %changelog tells us that the name anjuta-gdl was chosen instead of
gdl since there already exists a package called gdl. Debian and Ubuntu
call it libgdl.
Comments?
Cheers,
Debarshi
--
GPG key ID: 63D4A5A7
Key server: pgp.mit.edu
16 years, 3 months
Re: KDE logout options with F8
by Kevin Kofler
Christopher Aillon <caillon <at> redhat.com> writes:
> If your first reaction had been to ask for more information instead of
> add complaints, I might have mentioned that the plan is to have this for
> F9 (I think so at least, someone can correct me if I'm wrong?). Not
> sure if that counts as long term...
Even if somebody implements a KDE frontend for the GDM backend, that won't make
KDM go away. There's no way KDM is going away for KDE 4.0 which realistically
will be what F9 will be shipping. (And of course, it's even less likely that
said thing would happen in 3.5. Chances that KDE 4.1 will be anywhere near
ready at F9 release are essentially nil, 4.1 might quite possibly not even make
F10.)
> It is a reasonable request. Can you accept reasonable answers? Notting
> and jkeating have already replied with technical analysis explaining why
> it is not possible.
I have suggested at least 2 technical solutions, none of which needs any
changes to Anaconda:
1. revert the default login manager in Base X to XDM. As much as you
(plural "you") hate that, it's the most logical solution and some other people
in this thread are defending it too.
2. change the fallback logic to pick KDM over GDM. As I said, I think we can
easily put KDM in a subpackage so it doesn't accidentally get installed by a
dependency on kdebase, kde-redhat used to do that in FC6 times.
There's another one, which is even less invasive (and doesn't change the
behavior for the neither-GNOME-nor-KDE case as 1. nor for the
both-GNOME-and-KDE case as 2., but really only affects KDE-but-not-GNOME which
is what needs fixing), but has to be implemented as a specialized Anaconda
hack. Pseudocode:
if (! upgrade && KDE selected && ! GNOME selected)
echo 'DISPLAYMANAGER="KDE"' >/mnt/sysimage/etc/sysconfig/desktop
> Besides, we already know it's not going to happen for F8. And F9 we
> could in theory have a better all around solution....
"better" is subjective. If upstream KDE isn't going to drop KDM or recommend
against it, IMHO that fact shouldn't be ignored.
Kevin Kofler
16 years, 3 months
gripe/question: /etc/sysconfig/system-config-firewall???
by Douglas McClendon
Anybody care to explain to me the logic of the file
/etc/sysconfig/system-config-firewall
which makes my kickstart and/or lokkit invocations not be respected?
I.e. port 22 remains open even if I do
lokkit --enabled
(or just firewall --enabled in kickstart)
It seems like if anything lokkit should be writing this file, not
reading one installed by an rpm. But maybe I just need a clue. ???
-dmc
16 years, 3 months
Helping out with broken deps due to openssl changes
by Hans de Goede
Hi All,
I noticed in todays rawhide report that there are still quite a few packages
whcih are broken due to the openssl update.
I know these are the non trivial rebuild cases. I would hereby like to offer to
help. So anyone interested in receiving some help in getting their package(s)
fixed?
Regards,
Hans
16 years, 3 months
