Possible wrong versions tagged into f12-final
by Quentin Armitage
I've noticed what might be a couple of anomalies regarding which
versions of packages have been tagged into f12-final.
freenx-client: 0.9-9.fc12 was built as part of the dist-f12-rebuild, but
0.9-10.fc11 tagged has been tagged into f12-final.
gauche: 0.8.14.3.fc12 was built during the mass F12 rebuild, but
0.8.14.3.fc11 has been tagged into f12-final. It appears that
0.8.14-2.fc12 was built after 0.8.14-3.fc12 (during the mass F12
rebuild).
Quentin Armitage
11 years, 4 months
Packages looking for new owners
by Trond Danielsen
Hi everyone,
it is becoming clear to me that I can no longer provide the collection
of packages I maintain the love and care that they deserve. If only
there were more hours in a day, but the current situation does no
leave much room for volunteer work on free software :-(. Hopefully I
will find time in the future to return to Fedora related work
The list if packages I maintain is available here:
https://admin.fedoraproject.org/pkgdb/users/packages/trondd?acls=owner
I don't mind keeping libopenraw, avrdude and uisp unless anyone
_really_ want to maintain these packages.
Best regards,
--
Trond Danielsen
11 years, 4 months
Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
by Terry Barnaby
Ok, controversial title.
I have just tried to test install F12 on some of my systems, (5 different ones).
All of these bar 1 has problems with the graphics (X11 lockups, system lockups
and other problems) mainly in 3D but also in 2D.
I still am using F8 on most of my systems as the Graphics systems have not
been stable enough for 3D in Fedora since around those times.
I know there is a lot of work going on in the graphics front, I myself
have worked on and fed back issues as time and ability allow. During F11
I helped with some issues, but unfortunately none of these made it back into
updates for F11 and now F12 is out with yet more issues.
The Linux kernel is generally relatively stable, as is the main system
libraries etc in Fedora. The core issues most people seem to be facing is
Graphics and Sound issues. Obviously a major issue with Graphics is the sheer
number of different graphics chip sets in use and the lack of documentation
for quite a few of them. Due to this it requires a lot of user testing and
feedback to get these issues sorted out. Unfortunately the very fast
Fedora new release schedule gets in the way of getting this testing done
and things do not get fixed prior to a new release which introduces yet
another set of problems. The new release speed also uses a lot of
developer and user time in just managing to create a new release and
updating systems to use it.
I know the quick release cycle is one of Fedora's features in its aim to
be close to the leading edge, but this has to be balanced with usability
otherwise there will be few people actually using it in anger and thus
actually testing the software. This could lead to the demise of Fedora.
As an idea, at this stage, how about canceling the F13 release and just fixing
and updating the F12 release ? This will concentrate developers and users into
one system release. Similar to the pre-release test days we could have
post-release test days. For example a Graphics test day for F12 where
a certain set of tests with a test suite and a set of well known applications
could be run. As F12 would be out longer, more people could participate in this.
If a commitment, all round, to producing updates fixing the issues in F12 were
made, I think more people would be willing to participate as users could
expect to see a stable system for their efforts.
11 years, 4 months
Help with packaging
by Conrad Meyer
Hi list,
I'm experiencing trouble trying to get one of my packages (sdcc) to build for
Fedora 12. It builds on Fedora 11 and older (just double-checked in mock). It
seems to be some sort of change in how RPM uses __os_install_post or how brp-
strip-static-archive works between F11 and F12. Anyone familiar with any such
changes?
http://linux.dell.com/files/fedora/FixBuildRequires/mock-
results/x86_64/sdcc-2.9.0-4.fc12.src.rpm/result/build.log
Some background info for those unfamiliar with sdcc: sdcc is a compiler
targeting embedded devices. It bundles some archives that contain object code
for these other architectures -- chmodded 644, in %{_datadir} -- I don't even
know why brp-strip* dives into %{_datadir} anyway.
Thanks,
--
Conrad Meyer <cemeyer(a)u.washington.edu>
11 years, 4 months
Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
by Liang Suilong
After updating the package, compiz crashed and glxgears can not run.
However, KMS and plymouth can still run well.
Here is dmesg message that I grabbed:
[drm:r600_cs_packet_next_reloc_mm] *ERROR* No packet3 for relocation for
packet at 47.
[drm:r600_packet3_check] *ERROR* bad SET_CONTEXT_REG 0x28014
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
But I reboot with kernel-2.6.31.5-127. All the thing return to normal. My
desktop is running on Fedora 12 x86_64. My graphic card is HD3650.
ATi display drivers: xorg-x11-drv-ati-6.13.0-0.11.20091119git437113124.fc12
Kernel: 2.6.31.6-134.fc12.x86_64
Mesa: 7.6-0.15.fc12
Does any guy meet the same situation?
--
<url>http://www.liangsuilong.info</url>
Fight for freedom!!!!(3F)
Ask not what your Linux distro can do for you!
Ask what you can do for your Linux distro!
11 years, 4 months