On Sun, 13 Jan 2013 06:00:58 +
"Richard W.M. Jones" wrote:
> On Fri, Jan 11, 2013 at 09:17:03PM -0700, Kevin Fenzi wrote:
> > On Sat, 12 Jan 2013 02:53:06 +
> > "Richard W.M. Jones" wrote:
> >
> > > When I did the big OCaml codegen fix/update in F18 recently, I
> > > just bumped these p
Compose started at Sun Jan 13 08:15:06 UTC 2013
Broken deps for x86_64
--
[bootconf]
bootconf-1.4-6.fc18.noarch requires grub
[ember]
ember-0.6.3-3.fc19.x86_64 requires libOgreMain.so.1.7.4()(64bit)
[epiphany-extensions]
On 12 January 2013 19:07, Kevin Fenzi wrote:
> On Fri, 11 Jan 2013 13:01:03 +
> Ian Malone wrote:
>
>> KDE favourites:
>> For a spin (or formula) it makes sense that the favourites should
>> reflect the spin (or formula) focus. The kickstart updates this
>> through /etc/skel/.kde/share/confi
On 12 January 2013 17:02, Kevin Kofler wrote:
> Ian Malone wrote:
>> KDE favourites:
>> For a spin (or formula) it makes sense that the favourites should
>> reflect the spin (or formula) focus. The kickstart updates this
>> through /etc/skel/.kde/share/config/kickoffrc and
>> /etc/rc.d/init.d/live
hedgewars-0.9.18-1 is still in updates-testing despite it also being in
the release and 0.9.18-3 being in updates. Is there a way I can get rid of
the version in updates-testing?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Tue, Jan 8, 2013 at 2:15 PM, Kevin Fenzi wrote:
> Greetings.
>
> I've whipped up the early ideas of a way to replace (most) spins with
> something that is more generic and useful. I have signed up for a
> fudcon session to brainstorm on this idea and see if it can be beaten
> into a plan/schedu
On Sun, 13 Jan 2013 09:27:00 -0600
Bruno Wolff III wrote:
> hedgewars-0.9.18-1 is still in updates-testing despite it also being
> in the release and 0.9.18-3 being in updates. Is there a way I can
> get rid of the version in updates-testing?
I can untag it from there...
Some delay here I thin
On Sun, Jan 13, 2013 at 12:30:19 -0700,
Kevin Fenzi wrote:
I'll untag it manually.
If I had manually untagged it, would that have done the trick? I wasn't
sure if that was all that was needed or if there was more too it?
(I seemed to remember that testing tags could be changed by packager
Richard W.M. Jones wrote:
>> Note that in the future to avoid this:
>>
>> https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Minor_release_bumps_for_old_branches
>
> I was using git merge to keep the F18 and Rawhide histories exactly
> the same.
That doesn't preclude following the above g
