On 01/09/2011 05:52 PM, bradb...@seanet.com wrote:
> I am trying to update the cppad package using a new version of the
> upstream source following the instructions on
> http://fedoraproject.org/wiki/PackageMaintainers/UpdatingPackageHowTo
>
> I used the command
> fedpkg new-sources cppad-20110101.
On Sun, 9 Jan 2011 16:52:00 -0800 (PST)
bradb...@seanet.com wrote:
...snip...
> When I execute "md5sum cppad-20110101.0.gpl.tgz", I get
> ba57ee45b1a950004c33003e929c7ec1 cppad-20110101.0.gpl.tgz
If you look in your sources file you will see:
d25559c1adb7bbdbb254206b7464dc78 cppad-2011
Latest status of the OCaml upgrade is here:
http://fedoraproject.org/wiki/Talk:Features/OCaml3.12
I notice there are also a couple of OCaml packages not mentioned above
which I forgot to do.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'to
On Sun, Jan 09, 2011 at 06:06:56PM +, Paul F. Johnson wrote:
> Is there some form of magic that I need to use to get virt-manager to
> work as non-root on x86_64?
I don't know why the problem would be x86-64-specific, but in any case
you may need to modify the PolicyKit configuration to allow
> My understanding was that we never touch databases in RPMs, period. We
> don't create, modify, update, or remove. I can't recall at the moment
> where this stems from, but the rationale, as I recall, was that we can
> never be sure if the database is available at RPM install/upgrade time.
> Plu
Hi,
Is there some form of magic that I need to use to get virt-manager to
work as non-root on x86_64?
When I run it, I'm getting
Unable to open a connection to the libvirt management daemon.
Libvirt URI is: qemu:///system
Verify that:
- The 'libvirtd' daemon has been started
More details sh
Hey Fedorans!
Do you have a pet feature in Fedora or in our project's infrastructure that
you've wanted to implement for a while but lack the time or desire to
implement yourself? Do you want to see something awesome happen this summer?
Do you want to see students working on Fedora, and getting
susmit shannigrahi wrote:
> Correct, it exits the installation.
Then the software is broken and cannot reasonably be packaged at all.
Migrating data on upgrades ought to be automatic. Having the "options" of
"overwrite database" or "abort installation" is entirely useless.
Kevin Kofler
