January 2009 - devel - Fedora Mailing-Lists

by Denis Leroy

I've been investigating the move to libgda 3.99.8 (4.0 API) for Fedora 11. The 4.0 API is apparently stable now, and based on the F-11 release timeframe, upstream does recommend it. There's also a growing number of projects working with the 4.0 API already and I've received a request for this for an Anjuta plugin (https://bugzilla.redhat.com/show_bug.cgi?id=479298). There are currently 4 packages that depend on the 3.0 API: glom, gnome-python2-extras, qof and gnumeric-plugins-extras. The port to 4.0 appears to be non-trivial (http://library.gnome.org/devel/libgda-4.0/3.99/migration-2.html). We can probably work out a patch for something like the gnumeric plugin, but I don't know how much work would be required to port gnome-python2-extras for example. Glom still uses the 3.0 API, but the 4.0 port is almost finished in SVN. 2 options here: 1. Wait for glom to release its 4.0 API port, ping upstream for other dependencies or work on patches. Not yet clear how much work is required for this. 2. Revive the compat-libgda package (currently a dead.package, we used to have it for the 2.0 API when 2.99 was packaged) for the 3.0 API and move libgda to 3.99. Would this require a new package review ? I'm strongly leaning toward 2, mostly because of the uncertainty of option 1 plus the fact it will hold up other updates waiting for the 4.0 API and delay 4.0 API testing.

15 years, 3 months

3
4
0 / 0

Kernel message

by casimiro barreto

Hello, I'm receiving this message: [casimiro@terra ~]$ terra kernel: P0 eprtr bv hehl,cucoktrtld(oa vns=1819 Someone knows what's going on? Error in CPU0 ??? Thanks Casimiro

15 years, 3 months

3
2
0 / 0

No F11 Alpha for PowerPC

by Josh Boyer

Hi All, Due to some unforeseen circumstances, there will not be an F11 Alpha release for PowerPC. Aside from the normal issues that effect all the architectures, there were two things that contributed to this being the case: 1) The ppc64 kernels have not booted in quite some time. This is due to yaboot not being able to handle a kernel with CONFIG_RELOCATABLE=y being set because of the differences that creates in the elf file type. I fixed yaboot today and the ppc64 kernel will again at least try to boot. However... 2) While everyone was rejoicing over the upstream merge of squashfs into the kernel (myself included), we didn't quite realize that squashfs-tools does not work on big-endian architectures. This prevents ananconda from building the images needed for daily rawhide boot.isos and the actual composed install media. This is an upstream problem, and I have emailed them to see if there is anything I can do to help. However given the timeframe in question, it is quite unlikely that this will be fixed before the Alpha date. Even if it was, the lack of testing since Jan 12 would lead me to hesitate doing an Alpha release. I'll work on this as best I can. Hopefully by the time Beta rolls around we'll be back on track. josh

15 years, 3 months

1
0
0 / 0

FESCo Meeting Summary for 2009-01-16

by Josh Boyer

=== Members Present === * Brian Pepple (bpepple) * Jarod Wilson (j-rod) * Kevin Fenzi (nirik) * Josh Boyer (jwb) * Bill Nottingham (notting) * David Woodhouse (dwmw2) (partly) * Dennis Gilmore (dgilmore) * Jon Stanley (jds2001) == Summary == === Features === * FESCo did not feel the ReviewOMatic feature fit the criteria of a feature but encouraged it otherwise: https://fedoraproject.org/wiki/Features/ReviewOMatic * FESCo approved CUPS PolicyKit Integration as a feature: https://fedoraproject.org/wiki/Features/CupsPolicyKitIntegration * FESCo defered the decision on the Debuginfo Revamp feature and requested more information: https://fedoraproject.org/wiki/Features/DebugInfoRevamp * FESCo approved the EXT4 Default Filesystem feature after much debate, with the caveat that it will be reverted if Alpha/Beta find too many issues. I, for one, welcome our new ext4 overlords: https://fedoraproject.org/wiki/Features/Ext4DefaultFs * FESCo approved the Gnome 2.26 Feature: https://fedoraproject.org/wiki/Features/Gnome2_26 * FESCo declined the Live System on DVD feature on the grounds that it was not technically possible due to space constraints on everything except i386, had no proposed patches to enable the feature, and generally seemed like a wishlist item rather than an actual feature request: https://fedoraproject.org/wiki/Features/Live_System_for_the_DVD_Image * FESCo approved the XFCE 4.6 feature: https://fedoraproject.org/wiki/Features/Xfce46 === FPC Font Package Naming Guidelines === * FESCo had no objections to the FPC proposal: https://fedorahosted.org/fesco/ticket/18 === ovm === * FESCo ruled that ovm was acceptable as long as iverilog (or other similar toolsets) get in at the same time. They realize that those tools might not be immediately usable. === New Sponsor Requests === * Lubomir Rintel (lkundrak) was approved as a sponsor. * Itamar Reis Peixoto was declined as a sponsor on the grounds that he has done no reviews. FESCo encourages him to do some package reviews and reapply. * Ian Weller was declined as a new sponsor. FESCo encourages him to do some more package reviews and reapply. * Kevin Kofler was approved as a sponsor. IRC log can be found at: http://jwboyer.fedorapeople.org/fesco/fesco-meeting-2009-01-16.txt.html

15 years, 3 months

1
0
0 / 0

How do I allow automatic non root access to my non standard USB device ?

by linux guy

I'm doing some embedded development and my flash programmer has a USB interface. Everything works fine if I program the device as root, but I'd like to be able to do it as a regular user. I get port permission errors if I try to run the programmer as a regular user. $ lsusb Bus 002 Device 003: ID 064e:a101 Suyin Corp. Laptop integrated WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 006: ID 15ba:0003 Olimex Ltd. OpenOCD JTAG Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 002: ID 046d:c512 Logitech, Inc. LX-700 Cordless Desktop Receiver Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 07ca:a321 AVerMedia Technologies, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 003: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module] Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub My programmer is the Olimex Ltd. OpenOCD JTAG device on bus 7. The documentation for the device says it needs access to /proc/bus/usb. I can allow regular user access by manually issuing a chown command for the port, but then I'd have to do it every time I reboot or unplug the programmer. How do I set it up to happen automatically in F10 ? Thanks !

15 years, 3 months

6
20
0 / 0

Is Yum broken in Rawhide?

by Richard W.M. Jones

I did a 'yum clean all', but I still get the stack trace below from commands such as 'yum install foo' or 'yum update'. Rich. # yum install yum Loaded plugins: dellsysidplugin2, refresh-packagekit (process:1645): GLib-CRITICAL **: g_timer_stop: assertion `timer != NULL' failed (process:1645): GLib-CRITICAL **: g_timer_destroy: assertion `timer != NULL' failed Traceback (most recent call last): File "/usr/bin/yum", line 29, in <module> yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 229, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 104, in main result, resultmsgs = base.doCommands() File "/usr/share/yum-cli/cli.py", line 339, in doCommands self._getTs(needTsRemove) File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 101, in _getTs self._getTsInfo(remove_only) File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 112, in _getTsInfo pkgSack = self.pkgSack File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 592, in <lambda> pkgSack = property(fget=lambda self: self._getSacks(), File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 435, in _getSacks self.repos.populateSack(which=repos) File "/usr/lib/python2.6/site-packages/yum/repos.py", line 251, in populateSack sack.populate(repo, mdtype, callback, cacheonly) File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 184, in populate dobj = repo_cache_function(xml, csum) File "/usr/lib64/python2.6/site-packages/sqlitecachec.py", line 45, in getPrimary self.repoid)) TypeError: Can not create packages table: near "release": syntax error -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v

15 years, 3 months

4
6
0 / 0

Plan for tomorrow's (20090123) FESCo meeting

by Jon Stanley

Here's a list of items that will come up during tomorrow's FESCo meeting. 26 Archer 27 IBus 28 Stronger Hashes 30 KVM PCI Device Assignment - https://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment 31 SSSD - https://fedoraproject.org/wiki/Features/SSSD 32 Instant on Fedora - https://fedoraproject.org/wiki/Features/instant-on-Fedora 29 Review FPC Report - https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01235.html 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. Thanks! -Jon

15 years, 3 months

3
5
0 / 0

Problem with login in root account in Fedora10

by navneet rastogi

Hello, I am a member of GLUG Meerut and we are distributing Fedora10.I want to tell u about a bug in fedora10. It's just a simple mistake of a '#' but you never ignore it because a small ant can kill a big ELEPHANT .

15 years, 3 months

2
3
0 / 0

smart package manager oddities

by Stefan Grosse

Hi, I was trying to clean up my system. When I was running kdirstat I discovered that the smart package manager consumed 30 percent of my disk space since it seems to create a huge file in /var/lib/channels at every channel update. (140 MB for fedora-development) I reported the bug in smart/launchpad: https://bugs.launchpad.net/smart/+bug/319965 Can someone confirm this problem? Unfortunately removing smart does not remove those files. So I have to manually remove them. Why is yum not cleaning completely? Cheers Stefan

15 years, 3 months

5
5
0 / 0

X Problem in Fedora 10

by casimiro barreto

Hello, Yesterday I recovered a box from a crash (HD toasted). As I had to reinstall OS, previous configurations were lost. This box has an old video monitor (capable of 1024x768 or even 1240x1024 if you "pull strings") but after reinstall I'm limited to 800x600. Since /etc/X11/xorg.conf doesn't work anymore I'll be gratefull if someone points out where I can reconfigure X in order to set proper parameters (like VideoChip and video mode)??? Best regards, Casimiro

15 years, 3 months

4
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel January 2009