devel November 2009

devel@lists.fedoraproject.org

330 participants
292 discussions

F12-Beta-i686-Live has some bugs
by Ikem Krueger 17 Nov '09

17 Nov '09

I booted from cd and I was left with a black screen. When I switched to a console, I got: render error detected, EIR: 0x00000010 [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking I guess the kernel is guessing my graphiccard wrong. Usually I use "i810" or "intel" in Xorg. Workaround is to boot with "nomodeset". (That isn't even working with the LXDE Spin. :S) --- When I boot without "rhgb", I got several times: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. And at the end: plymouthd: ply-event-loop.c:729: ply_event_loop_stop_watching_fd: Assertion 'watch != ((void *)0)' failed. -- Btw, Where went the options for "testing ram", "testing cd/dvd", "failsafe"? o.O

3 2

How to update F12 packages?
by Jeff Garzik 17 Nov '09

17 Nov '09

Project Hail[1] has three packages in F12, cld, chunkd and tabled, which need updating. I successfully built cld: "make build" placed it into dist-f12-updates-candidate apparently. But "koji wait-repo" is timing out after a two-hour wait, preventing me from building chunkd and tabled. What do I need to do, to build updated chunkd and tabled packages on top of the new cld? Does each dependency need its own bodhi update, or something? I am hoping to avoid - build cld - submit bodhi update - wait for update to be processed into repo - build chunkd - submit bodhi update - wait for update to be processed into repo - build tabled - submit bodhi update - wait for update to be processed into repo Surely there is a faster way, for _clusters_ of dependent packages, such as Project Hail's? Thanks, Jeff [1] http://hail.wiki.kernel.org/

2 2

The tag mercurial-1_4-1_fc12 is already applied on a different branch
by Neal Becker 16 Nov '09

16 Nov '09

Seems I do this every time we have a new release. In F12: cvs tag -F -c mercurial-1_4-1_fc12 ERROR: The tag mercurial-1_4-1_fc12 is already applied on a different branch ERROR: You can not forcibly move tags between branches cvs tag: Pre-tag check failed cvs [tag aborted]: correct the above errors first! What are my choices to proceed? I already have built/are building 1.4.1 on F13 and F11. I don't want to have a different package number on F12.

3 4

rpmlint warnings...
by Nathanael D. Noblet 16 Nov '09

16 Nov '09

Hello, So I recently posted my first package and the review. While I waited I started cleaning up more issues I found after I realized you could run rpmlint on the actual rpm and not just the spec file. I'd like the review to go as quickly as possible so I'm just trying to get all those warnings cleaned up. My package has a number of sub packages for various backend drivers. These subpackages basically contain a .so file for the most part however I'm getting rpmlint messages as follows libdspam.x86_64: W: devel-file-in-non-devel-package /usr/lib64/libdspam.so how is libdspam.so determined to be a devel file? libdspam.so.7.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped Is what I get back from file. What is it that I'm missing? Thanks,

4 7

[Fwd: Broken dependencies: offlineimap]
by Christoph Höger 16 Nov '09

16 Nov '09

Hi, does anyone know what this means? Did we switch from Python 2.6 to 3.x or is python broken itself on rawhide?

2 2

Fedora Release Engineering meeting summary for 2009-11-16
by Jesse Keating 16 Nov '09

16 Nov '09

Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2009-11-16/fedora-releng.20… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2009-11-16/fedora-releng.20… Log: http://meetbot.fedoraproject.org/fedora-meeting/2009-11-16/fedora-releng.20… Meeting summary --------------- * roll call (Oxf13, 18:06:03) * Fedora 13 (Oxf13, 18:18:51) * AGREED: No Frozen Rawhide meeting to be held Thursday the 19th at 2000UTC on Fedora Talk (Oxf13, 18:31:54) * mash configs were still trying to compose ppc, and failing badly (Oxf13, 18:35:55) * install image creation was not actually shut off (Oxf13, 18:37:28) * ACTION: notting to fix mash today to stop trying to mash ppc (Oxf13, 18:38:04) * Oxf13 already fixed image creation not being turned off (Oxf13, 18:38:25) * ACTION: wwoods will stop israwhidebroken from caring about ppc(64) (Oxf13, 18:42:46) * ACTION: oxf13 to review proposed schedule and comment on list (Oxf13, 18:47:26) * Open Floor (Oxf13, 18:49:37) Meeting ended at 18:55:35 UTC. Action Items ------------ * notting to fix mash today to stop trying to mash ppc * wwoods will stop israwhidebroken from caring about ppc(64) * oxf13 to review proposed schedule and comment on list -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating

1 0

"make tag" failure doesn't fail right?
by Braden McDaniel 16 Nov '09

16 Nov '09

I did: $ make tag and got: cvs tag -c openvrml-0_18_3-11_fc13 cvs tag: openvrml.spec is locally modified cvs [tag aborted]: correct the above errors first! Whoops. And so I proceeded to commit the outstanding changes that I'd forgotten to commit. Once I'd done that, I went to tag again: $ make tag cvs tag -c openvrml-0_18_3-11_fc13 ERROR: Tag openvrml-0_18_3-11_fc13 has been already created. The following tags have been created so far . . . openvrml-0_18_3-11_fc13:devel:braden:1258273475 cvs tag: Pre-tag check failed cvs [tag aborted]: correct the above errors first! Uh oh. Did my previous "make tag" actually succeed? -- Braden McDaniel <braden(a)endoframe.com>

4 4

Re: What questions would you like to ask the Candidates for the Fedora Board, FESCo, and FAMSCO?
by Thorsten Leemhuis 16 Nov '09

16 Nov '09

Hi! Sorry, I haven't got around to work on the final version of the questions yet. I plan to do that early tomorrow, which leaves everybody still something like 13 hours to add questions to the wiki. CU knurd Thorsten Leemhuis wrote on 12.11.2009 07:28: > > As you may have heard already, several seats of the Fedora Board, FESCo, > and FAMSCO are up for election soon(¹). Right now we are in the > nomination period, which will be followed by a "Candidate > Questionnaire." That means we'll give candidates a list of questions to > answer by private mail within one week after the nomination period > closed; the results will be publish soon after that to make sure they > are available to the public before the Town Hall meetings on IRC happen. > > Candidates may choose to answer (or not) those questions as they see > fit. Voters can use the answers to get an impression of what the > candidate think or plan to do while serving for the committees they are > nominated for. That should help to get a interesting discussion running > during the IRC Town Hall meetings; furthermore, those people that can't > or don't want to participate in the IRC meetings can use the answers to > make a more informed vote. > > Hence we need to prepare a few good questions that we can send to the > candidates once the nomination period ends. And that's where I need > *your help* now: > > If you have one or more questions you'd like to send to the candidates > simply go and add them to: > > https://fedoraproject.org/wiki/Elections/F13_Questionnaire > > It just takes a minute or two, so best to do it right now -- otherwise > you might get distracted and forget about it. ;-) > > I'll take care of the remaining work to review, sort, and clean up the > questions(²); after that I'll send them to the candidates soon after the > nomination period ended. Hence, I need your question suggestions by > around the 15th November 17:00 UTC latest to get a chance to prepare > everything in time. > > So please go to the wiki now and add at least one hard question! The > answers will help Fedora contributors to chose whom to vote for! Thanks > in advance for your help . > > CU > knurd > > (¹) If you haven't read about it yet see > https://fedoraproject.org/wiki/Elections for details. > > (²) If you want to get involved or review the questions before I send > them please drop me a line and I'll try to get that arranged; maybe we > can arrange a quick, informal IRC meeting on Sunday evening if there is > interest

1 0

Broken dependencies script at it again
by Paul Howarth 16 Nov '09

16 Nov '09

Please make it stop. milter-regex-1.7-6.fc12.ppc requires /bin/sh I guess this is happening because of dropping ppc/ppc64 as primary arches? ISTR the last time the dep checker went off on a mailbombing session it was suggested that it checks for broken deps against obvious things like /bin/sh and declared itself insane, sparing us all the pointless mails? Paul.

13 19

Re: FESCO ticket#270 - preupgrade and F-12
by Jerry Vonau 16 Nov '09

16 Nov '09

> On Fri, 2009-11-13 at 09:35 -0500, Andy Gospodarek wrote: > > On Thu, Nov 12, 2009 at 11:27:28PM -0500, Bill Nottingham wrote: > > > Toshio Kuratomi (a badger gmail com) said: > > > > > There are definitely workarounds available, but none that meet the > > > > > criteria for preupgrade as an effortless upgrade option. > > > > > > > > So I'm a bit confused by what is so hard here. preupgrade starts up, > > > > finds it can't store stage2, and then tells you that you'll need to have a > > > > wired connection to the internet if you want to use it. So you have to > > > > download stage2 when you reboot and you have to cart your laptop over to the > > > > router to plug it in while it does so... it's not like I'm going to be using > > > > it for work while anaconda is running.... > > > > > > Basically, the case where it fails is when there's enough space to download > > > stage2, but not enough space left after downloading stage2 to do the > > > upgrade. > > > > > > > Could we add some support to use a USB key as scratch space for any part > > of this process? > > Not a bad idea. Not sure who would add this support and test it before > Tuesday. Definitely something to consider as a future enhancement to > preupgrade. You could hand edit the stage2= line and point is to any non-lvm partition including a temporary usbkey. You would need to have a filesystem label on the usbkey, and change "Fedora" to be the name of your usbkey in the grub.conf file entry for preupgrade. Just make sure that the install.img resides in /images on the usbkey. You could boot off the boot.iso and pass the needed options to anaconda, appending to the boot line does work with: append initrd=initrd.img stage2=hd:LABEL="Fedora" preupgrade \ repo=hd::/var/cache/yum/preupgrade ks=hd:sda1:/upgrade/ks.cfg Yea, I know ks=hd:sda1 is less that ideal, but if that is the /boot partition unless your playing bios games with the boot order, where else can it be but sda1? This could be added to the boot.iso in a stanza as an option much like rescue. Just some thoughts, Jerry

2 1

← Newer
1
...
13
14
15
16
17
18
19
...
30
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel November 2009