I works all days on D Programming Feature.
* ldc package is done
* but not tango, link:
This package need a review i need help for finish this.
Thanks for any help
Jonathan MERCIER <bioinfornatics(a)gmail.com>
I am trying to checkout the package I put into the repository via CVS a
couple of weeks ago, frama-c, and i am getting a couple of errors.
[rader@tpath3 upload]$ fedpkg -v clone frama-c
Traceback (most recent call last):
File "/usr/bin/fedpkg", line 812, in <module>
File "/usr/bin/fedpkg", line 408, in clone
pyfedpkg.clone(args.module, args.user, args.path, args.branch)
File "/usr/lib/python2.6/site-packages/pyfedpkg/__init__.py", line 170, in
raise FedpkgError('Could not clone %s: %s' % (giturl, e))
pyfedpkg.FedpkgError: Could not clone ssh://
mrader(a)pkgs.stg.fedoraproject.org/frama-c: 'git clone ssh://
mrader(a)pkgs.stg.fedoraproject.org/frama-c' returned exit status 128: Use of
uninitialized value in string eq at /usr/local/bin/gl-auth-command line 65.
R access for frama-c DENIED to mrader
fatal: The remote end hung up unexpectedly
Does anyone have an idea what is causing this?
Hi, everyone. Just a heads-up to proven testers: now Fedora 14 has been
branched, the proven tester process is in effect for Fedora 14 packages.
Just like Fedora 13, critical path updates for Fedora 14 (even while
it's in development) will require +1 from a proven tester and +1 from
someone different. So, we really need proven testers to start testing
those F14 packages!
If you have a spare system you can run Fedora 14 on, or you can set up a
VM, or you're feeling particularly adventurous and you have a fallback
system in case F14 breaks your main system, please do go ahead and put
F14 on there. Installing F14 direct is currently a bit tricky, but what
you can do is install F13 live and then update to F14; you may have to
remove a couple of packages to make this work right now, soon it should
work without problems.
Then you can follow the proven tester procedure exactly as you would
with a released version - all the same repositories exist,
fedora-easy-karma will (should!) work, and the updates go through Bodhi.
Thanks a lot!
Right now we have one critpath update we want to get approved ASAP -
https://admin.fedoraproject.org/updates/pygtk2-2.17.0-7.fc14 . I've
already filed a +1 on it, but it needs confirmation. There may be others
of which I'm not yet aware.
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
test-announce mailing list
I found a fix on bugzilla:
rpm -e --nodeps systemd-units
yum install systemd-units
Which created the symlinks and default.service which seemed to be missing, and allowed the boot to finish, but I may have been to quick to use it. One CPU core is at maximum and Chrome won't open, so I'm temporarily back to upstart till I get time to look at it further.
From: darrell pfeifer <darrellpf(a)gmail.com>
To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>
Sent: Wed, Jul 28, 2010 6:46 pm
Subject: Re: [HEADS-UP] systemd is now the default init system in rawhide
On Wed, Jul 28, 2010 at 19:33, <goineasy9(a)aol.com> wrote:
Add init=/sbin/upstart to the end of the kernel line and it will boot up using upstart. Last lines in my boot read failing to load default.service and then failing to start default.service.
Check one of the recent previous messages.
ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
Will solve that problem and get you a bit further along the way.
devel mailing list
Em Sexta-feira 30 Julho 2010, às 09:02:34, você escreveu:
04:09 AM, Helio Chissini de Castro wrote:
> > Hello Guys
post here is to present a small utility that maybe will
> > be
people building rpms on your machine locally and want to
avoid all the
usual flags and directories needed to use rpmbuild
> > Hope this tool be useful for more people as it is
> Well, if
you really want it to be useful for us, and maybe for
> take a look at
it, a relevant link to some kind of site and/or
> would probably be
Ahh, sorry :-)
I just submitted
to koji, and here's the links
of built packages
Helio Chissini de Castro
and Brazil Primary Contact
KDE Developer since 2002
Tried to do a commit and seem to be in a bad state:
[orion@orca paraview]$ fedpkg commit -p
[master 6f6d9c7] Add patch to support python 2.7
2 files changed, 18 insertions(+), 1 deletions(-)
create mode 100644 paraview-3.8.0-py27.patch
Warning: No xauth data; using fake authentication data for X11 forwarding.
parse /etc/gitolite/conf/gitolite.conf-compiled.pm failed: Can't find
string terminator "'" anywhere before EOF at
/etc/gitolite/conf/gitolite.conf-compiled.pm line 1296608.
fatal: The remote end hung up unexpectedly
Could not push: Command '['git', 'push']' returned non-zero exit status 128
[orion@orca paraview]$ fedpkg commit -m 'Add patch to support python 2.7' -p
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
nothing added to commit but untracked files present (use "git add" to track)
Could not commit: Command '['git', 'commit', '-m', 'Add patch to support
python 2.7', '-a']' returned non-zero exit status 1
not sure what to do now.