-----BEGIN PGP SIGNED MESSAGE-----
I've just updated liboauth to the latest 1.0.1 release in Rawhide. The
soname is now liboauth.so.0.8.5 (previously liboauth.so.0.8.4), and
dependent apps should not need a rebuild, but maintainers of the
affected components should probably double-check to be sure.
(Especially for Evolution and GNOME Documents, as ever since I enabled
two-factor authentication, synchronization with Google servers have been
a bit problematic anyway).
There's a scratch build for Fedora 18 here:
Note that upstream now considers all use of oauth_http functions to be
Michel Alexandre Salim
Fedora Project Contributor: http://fedoraproject.org/
Email: salimma(a)fedoraproject.org | GPG key ID: A36A937A
Jabber: hircus(a)jabber.ccc.de | IRC: hircus(a)irc.freenode.net
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
In case you were not bitten by Schrödinger's Cat in Grub or got around her, you
might run in dracut/systemd problems in the initramfs.
You will have to update to at least
systemd-198-6.fc19 and dracut-026-48.git20130315.fc19
for a working initramfs.
# koji download-build --arch=$(arch) systemd-198-6.fc19
# koji download-build --arch=$(arch) dracut-026-48.git20130315.fc19
# rpm -Fvh systemd*.rpm dracut*.rpm
# dracut -f --kver=<not_booting_kernel_version>
Sorry for the inconvenience!
I'm a software developer from Fort Wayne, Indiana. I work for a company
called ScreenCheck North America and have been building RPMs for our
in-house software as well as various open source projects not foung in EPEL
or other trusted repos. I created our internal Yum repos about a year ago
and have become quite fond of RedHat based distros, even so much as to move
my personal machines from Arch Linux to Fedora.
My goal is to maintain our open source RPMs as a Fedora Package Maintainer
so that we can share our work with the community.
I figured I would start with a tough one first, this is actually a package
that I don't use at work but have installed on most of my personal machines
and servers. I figured this would help me get a feel for the package review
If anyone from the Erlang SIG could give me feedback that would be extra
helpful as I'm fairly new to Erlang. All feedback is appreciated.