This mail was intended for Haskell SIG list. Sorry for the devel wide mail.
On Sun, Sep 25, 2011 at 11:25 AM, lakshminaras2...@gmail.com <
lakshminaras2...@gmail.com> wrote:
> 1) gtk2hs updates available on rawhide (0.12.1)
> https://bugzilla.redhat.com/show_bug.cgi?id=739876
>
> 2) ghc-rp
1) gtk2hs updates available on rawhide (0.12.1)
https://bugzilla.redhat.com/show_bug.cgi?id=739876
2) ghc-rpm-macros related bug on f14,f15 fixed. New builds of haskell
packages should have the correct rpm hash information from now on
3) Pending reviews requiring owners
ghc-wai - https://b
On Sep 23, 2011, at 1:41 PM, Richard W.M. Jones wrote:
> On Fri, Sep 23, 2011 at 12:54:35PM -0700, Jesse Keating wrote:
>> I'm upgrading GitPython from 0.2x to 0.3 in rawhide. There are some changes
>> that require consumers to do some minor porting, briefly outlined at
>> http://packages.python
On Fri, Sep 23, 2011 at 20:51, Matthew Garrett wrote:
> On Fri, Sep 23, 2011 at 07:42:55PM -0400, Doug Ledford wrote:
> It may work. It may not. It may leave the system unbootable. You can't
> guarantee it, and you've been told that this is behaviour that you can't
> depend on. If you choose to d
Greetings.
I've untagged GitPython-0.3.2-0.1.RC1.fc17 in rawhide. It was breaking
the buildroot. ;( Things should start working soon.
(Yes, I know that we don't want rawhide to go back after something has
entered a compose, but here we have no choice, since we need a
buildroot to build the fixed
I just took over the akmods package at RPM Fusion and one of the many
BZ requests is to convert it to systemd.
The current suggestion is:
[Unit]
Description=Builds and install new kmods from akmod packages
After=syslog.target
Before=prefdm.service
[Service]
Type=oneshot
ExecStart=-/usr/sbin/akmod
Compose started at Sat Sep 24 08:15:20 UTC 2011
Broken deps for x86_64
--
389-admin-1.1.23-1.fc17.i686 requires libicuuc.so.46
389-admin-1.1.23-1.fc17.i686 requires libicui18n.so.46
389-admin-1.1.23-1.fc17.i686 require
On 09/06/2011 11:14 PM, Roberto Ragusa wrote:
> Anyway, the problem happened again one hour ago, so I just decided
> to upgrade only the kernel to the one from F15 and hope for the best.
> If it happens again, I will then upgrade Xorg and Mesa.
Replying to myself in this old thread just to let go
