I've just created
https://fedoraproject.org/wiki/Features/libjpeg-turbo-jpeg8-ABI page which
contains plan how to successfully move from current jpeg6 API/ABI to more recent
jpeg8 API/ABI for Fedora 19.
All packages which depends on libjpeg.so will have to be rebuilt. Since I have
provenpackager privileges, I will cook some script which will rebuild all
pkgs automatically so no action will be required from maintainers.
If there are no objections against this approach, I will start with this task
Adam Tkac, Red Hat, Inc.
Unfortunately, I'm no longer in a position to maintain the projectM
packages (libprojectM, libprojectM-qt, projectM-jack,
projectM-libvisual, and projectM-pulseaudio), so I will need to orphan
these. If anyone would like to pick these up, feel free to come to me
with questions, or help.
2011-06-23 : FTBFS not responded to
2010-06-30 : -static packaging bug not responded to
Plus, release 0.89 from 20-May-2011 is available whereas Fedora contains
0.84 from 2010 ( http://sourceforge.net/projects/courier/files/cone/ ).
This looks like somebody with interest in Cone should sign up as
co-maintainer and find out what's up with the current maintainer.
Fedora release 16 (Verne) - Linux 3.1.1-2.fc16.x86_64
loadavg: 0.82 1.09 0.87
Hi, I have download the last Fedora-18-Beta-TC4 to do some tests
How to install it on a empty disk and use LVM (or create a software
>From the new disk manager anaconda panel I did not understand how to
create a new LVM partition and root and swap volume.
Is this features not yet supported or I have lost some HOWTO?
Dario Lesca - sip:firstname.lastname@example.org
(Inviato dal mio Linux Fedora 17 Gnome3)
Hey folks - just in case you haven't all figured this out yet, if
you're using the neat little trick of putting a few lines in your
~/.bashrc so that when you're in a directory containing a git repo, the
prompt will display what branch you're in, it'll stop working when you
update to the latest git - 1.7.12 - in F18 or Rawhide. To fix it, you
need to change:
because upstream split the prompt stuff out from the bash_completion
script. Perhaps the git packagers could consider providing git-prompt.sh
in a more permanent location, so we don't have to poke .bashrc every
time the git version changes? Thanks!
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
-----BEGIN PGP SIGNED MESSAGE-----
Testing some packages in Fedora 18, I noticed that lot of
configuration for httpd have not be fixed for new version 2.4.
So I open a tracker bug for this issues
Currently I have filed ~40 bugs, and continue to check all
applications providing a httpd configuration file.
I you need more explanation on the required changes, feel free to ask.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
-----END PGP SIGNATURE-----
// Deploying fedora infrastructure (koji) across clouds
// As promised, steps to deploy kojihub to an openstack instance
communicating with builders on ec2
// Any provider supported by deltacloud will work
// (lots of em: http://deltacloud.apache.org/drivers.html)
// A short video of these steps in action can be seen here:
// install deltacloud & drivers
$ sudo yum install wget deltacloud-core deltacloud-core-openstack
// start it
$ deltacloudd -i mock
// small wrapper script around deltacloud:
$ wget https://raw.github.com/movitto/mycloud/master/mycloud.rb
$ chmod +x mycloud.rb
// template describing kojihub cloud deployment
// template describing kojibuild cloud deployment
// edit kojihub deployment to contain openstack credentials
$ vim koji_f17.xml
// startup an instance on openstack w/ kojihub setup togo
$ ./mycloud.rb koji_f17.xml
// grab public address from output, grab kojibuild ssl credentials from
$ scp -i ~/os.key ec2-user@kojihub:/etc/pki/koji/kojiadmin.pem .
$ scp -i ~/os.key ec2-user@kojihub:/etc/pki/koji/koji_ca_cert.crt .
// edit kojibuild deployment to deploy to ec2 w/ correct koji
credentials & hub address
$ vim koji_builder_f17.xml
// startup an instance on ec2 w/ kojibuild communicating w/ the hub
$ ./mycloud.rb koji_builder_f17.xml
// open up a webbrowser, navigating to http://kojihub/koji to use your