Re: Fedora 18 : broken configuration for httpd 2.4

Le 31/10/2012 22:25, Gianluca Sforna a écrit : > So, befoer I dig into manuals, can you name the most common causes for > breakage? Some explanation on the tracker bug https://bugzilla.redhat.com/show_bug.cgi?id=871373 Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fed

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On Thu, Nov 1, 2012 at 6:37 AM, Ralf Corsepius wrote: > On 10/31/2012 11:00 PM, Toshio Kuratomi wrote: > >> On Wed, Oct 31, 2012 at 10:59:54AM -0700, Jesse Keating wrote: >> >>> >>> I think we need to give developers more time for feature integration >>> after the feature freeze. >>> >>> +1 >> >

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On 11/01/2012 08:37 AM, Ralf Corsepius wrote: On 10/31/2012 11:00 PM, Toshio Kuratomi wrote: On Wed, Oct 31, 2012 at 10:59:54AM -0700, Jesse Keating wrote: I think we need to give developers more time for feature integration after the feature freeze. +1 No matter whether we increase the len

F18 yum update problem

http://fpaste.org/5mbi/ 2 days ago It was just a "libvirt" package but now gnome and empathy packages also broken too. -- -- Onuralp SEZER Fedora Ambassadors EMEAMember / Turkey

Re: F18 yum update problem

On Thu, 1 Nov 2012 10:03:20 +0200 Onuralp SEZER wrote: > http://fpaste.org/5mbi/ > > 2 days ago It was just a "libvirt" package but now gnome and empathy > packages also broken too. > Not broken as such, just that not all pkgs arrive in the repo, at the same time. Did you try the suggestion

Re: F18 yum update problem

On Thursday, November 01, 2012 04:03 PM, Onuralp SEZER wrote: http://fpaste.org/5mbi/ 2 days ago It was just a "libvirt" package but now gnome and empathy packages also broken too. You're using the -testing repositories. Packages get pushed there, unpushed, downgraded,... If, for example, l

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On 11/01/2012 02:09 AM, Kevin Kofler wrote: Anaconda is the least tested component in Fedora (most people test it at most once every 6 months) and arguably the most critical (because it is required to get Fedora up and running at all). The less it changes, the better! This is not right in fact

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

Tom Lane píše v St 31. 10. 2012 v 11:08 -0400: > Adam Williamson writes: > > ... Practically speaking, for F18, > > though, I think we just need to soldier on with newUI and get it done as > > best we can. Obviously slipping the schedule by a week again and again > > in response to the latest fire

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

Le mercredi 31 octobre 2012 à 10:59 -0700, Jesse Keating a écrit : > On 10/31/2012 09:56 AM, Toshio Kuratomi wrote: > > * Jesse Keating, Jeremy Katz, and others who helped shape the current policy > >and theory of our release schedule felt that the 6 month release cycle > > was > >fine but

Re: Re: Deploying fedora infrastructure (koji) across clouds

On 10/31/2012 01:07 PM, Seth Vidal wrote: > >> // small wrapper script around deltacloud: >> $ wget https://raw.github.com/movitto/mycloud/master/mycloud.rb >> $ chmod +x mycloud.rb >> >> // template describing kojihub cloud deployment >> $ wget >> https://raw.github.com/aeolus-incubator/templates/

Re: Re: Re: Deploying fedora infrastructure (koji) across clouds

On 10/31/2012 01:10 PM, Seth Vidal wrote: > > > > On Wed, 31 Oct 2012, Mo Morsi wrote: > >>> #2: Could there be a way to take a (working) nightly build, build >>> one's package against that nightly in a personal build of some sort, >>> and somehow have a verification process that it built in that >

Re: Deploying fedora infrastructure (koji) across clouds

On 11/01/2012 08:33 AM, Mo Morsi wrote: > On 10/31/2012 01:10 PM, Seth Vidal wrote: >> >> >> On Wed, 31 Oct 2012, Mo Morsi wrote: >> #2: Could there be a way to take a (working) nightly build, build one's package against that nightly in a personal build of some sort, and somehow have

Re: Orphaning Unity bits: bamf, compiz-plugins-main, dee, libindicator

And whoever want to install unity or these packages, can just use GNOME:Ayatana from the open build service :) regards, Damian 2012/11/1 Adam Williamson : > I currently own a few packages related to my old abortive attempt to > build Unity for Fedora. I don't have time to maintain these or any >

Re: rubygem-{bunny,moneta,ohai} package ownership

The packages look like they were retired after being orphaned for a few fedora cycles. You'll need to resubmit them proper, but should be able to base the new packages on the existing ones pre-retirement. And in the case of moneta, the package version is the same so that can just be resubmitted as

F-18 Branched report: 20121101 changes

Compose started at Thu Nov 1 09:15:25 UTC 2012 Broken deps for x86_64 -- [dhcp-forwarder] dhcp-forwarder-upstart-0.10-1801.fc18.noarch requires /sbin/initctl [dnf] dnf-0.2.14-2.git4831982.fc18.noarch requires python-hawkey >=

Re: Orphaning Unity bits: bamf, compiz-plugins-main, dee, libindicator

On 11/01/2012 06:06 PM, Damian Ivanov wrote: > And whoever want to install unity or these packages, can just use > GNOME:Ayatana from the open build service :) Unfortunately that replaces many important components with forked versions. If it was a pure add-on repository, that would be ok. Rahul

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On 11/01/2012 12:22 PM, Michael Scherer wrote: Maybe having some kind of dependencies between feature could also be a idea. Anaconda requires dracut to not change, so we need a way to express this, and a way to avoid changes at the same time. The same goes for a python upgrade or lots of things.

rawhide report: 20121101 changes

Compose started at Thu Nov 1 08:15:06 UTC 2012 Broken deps for x86_64 -- [LabPlot] LabPlot-1.6.0.2-12.fc18.i686 requires libaudiofile.so.0 LabPlot-1.6.0.2-12.fc18.x86_64 requires libaudiofile.so.0()(64bit) [PyKDE] PyK

Re: Orphaning Unity bits: bamf, compiz-plugins-main, dee, libindicator

On 10/31/2012 08:24 PM, Adam Williamson wrote: > Only one package depends on any of these: gwibber depends on dee. So > someone interested in gwibber might want to pick up dee. I'll take dee, although, gwibber will never progress past 3.6, because the upstream (Canonical) plan is to convert gwibbe

Re: Orphaning Unity bits: bamf, compiz-plugins-main, dee, libindicator

On Thu, Nov 1, 2012 at 1:18 PM, Tom Callaway wrote: > On 10/31/2012 08:24 PM, Adam Williamson wrote: > > Only one package depends on any of these: gwibber depends on dee. So > > someone interested in gwibber might want to pick up dee. > > I'll take dee, although, gwibber will never progress past

Re: Orphaning Unity bits: bamf, compiz-plugins-main, dee, libindicator

- Original Message - > I currently own a few packages related to my old abortive attempt to > build Unity for Fedora. I don't have time to maintain these or any > direct interest in them - they were just Unity building blocks to me. > I'm orphaning these packages: > > bamf > compiz-plugins

Re: Re: Deploying fedora infrastructure (koji) across clouds

Le jeudi 01 novembre 2012 à 08:32 -0400, Mo Morsi a écrit : > On 10/31/2012 01:07 PM, Seth Vidal wrote: > > You can orchestrate all of these steps across/between multiple systems > > using ansible: http://ansible.cc - I've been documenting spinning up and > > provisioning instances on my blog in t

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On Wed, Oct 31, 2012 at 07:17:30PM -0700, Adam Williamson wrote: > On Thu, 2012-11-01 at 03:09 +0100, Kevin Kofler wrote: > > Adam Williamson wrote: > > > I'd recommend asking dcantrell, as he has some good points on this > > > topic. I broadly agree with him that it might well be more or less > >

Re: Re: Deploying fedora infrastructure (koji) across clouds

On Thu, 1 Nov 2012, Mo Morsi wrote: Cool thanks for the info Seth. Ansible looks interesting, its a configuration orchestration component akin to Puppet / Chef is it not? Does it do any provisioning in itself? Ansible is more like this: Combining puppet and chef in one item. Then making

Re: Orphaning Unity bits: bamf, compiz-plugins-main, dee, libindicator

On 11/01/2012 09:22 AM, Peter Robinson wrote: > > > > On Thu, Nov 1, 2012 at 1:18 PM, Tom Callaway > wrote: > > On 10/31/2012 08:24 PM, Adam Williamson wrote: > > Only one package depends on any of these: gwibber depends on dee. So > > someone interested

Re: Maybe highlight release-slipping features? (was: Re: Anaconda is totally trashing the F18 schedule)

On Wed, Oct 31, 2012 at 07:38:27AM -0400, Scott Schmit wrote: > > Given the current state of F18 I agree let's lengthen this release > > cycle up to 9 months and arguably we should lengthen the whole >^ > > development cycle to 9 month

Re: Orphaning Unity bits: bamf, compiz-plugins-main, dee, libindicator

On Thu, Nov 1, 2012 at 1:37 PM, Tom Callaway wrote: > On 11/01/2012 09:22 AM, Peter Robinson wrote: > > > > > > > > On Thu, Nov 1, 2012 at 1:18 PM, Tom Callaway > > wrote: > > > > On 10/31/2012 08:24 PM, Adam Williamson wrote: > > > Only one package depends on

Re: Re: Re: Deploying fedora infrastructure (koji) across clouds

On Thu, 1 Nov 2012, Mo Morsi wrote: Hrm I was refering more to the repos necessary to bootstrap the cloud instance for the koji builder. I see - I thought you were referring to package repos. Which component imposes this limitation on koji, the hub or the builder? the hub. Would b

Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, Nov 01, 2012 at 09:24:52AM +0200, Panu Matilainen wrote: > There are features and features... some of them are new versions of > leafnode packages or a just bunch of new packages which nothing else > depends on, and some of them affect *everything* in the distro. > Perhaps the invasive chan

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

Hi all, It's important to recognise the negative effects of delays to the release. Upstream projects are reliant on the Fedora release process to get updates out to their users. GNOME released version 3.6 on 26 September. It was a big release and contained major improvements to our user experience

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On Thu, 2012-11-01 at 13:01 +, "Jóhann B. Guðmundsson" wrote: > On 11/01/2012 12:22 PM, Michael Scherer wrote: > > Maybe having some kind of dependencies between feature could also be a > > idea. Anaconda requires dracut to not change, so we need a way to > > express this, and a way to avoid ch

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On 10/31/2012 05:59 PM, Jesse Keating wrote: On 10/31/2012 09:56 AM, Toshio Kuratomi wrote: * Jesse Keating, Jeremy Katz, and others who helped shape the current policy and theory of our release schedule felt that the 6 month release cycle was fine but that certain features were going to

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On Thu, Nov 01, 2012 at 02:25:39PM +, Allan Day wrote: > It's important to recognise the negative effects of delays to the > release. Upstream projects are reliant on the Fedora release process to get > updates out to their users. GNOME released version 3.6 on 26 September. It > was a big rele

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

Am 01.11.2012 15:41, schrieb "Jóhann B. Guðmundsson": > > We ( QA community ) would benefit from a longer release cycle since we > need more time to properly test "features" and other vital components > and arguably the QA part of an feature should FESCO delegate to QA > community to oversee and h

MPI updates

Some MPI updates: - I built openmpi 1.6.3 in rawhide yesterday. This had an unexpected bump in the libmpi_f90.so soname. I know this affects hdf5 and netcdf-fortran, both my packages and I'll be rebuilding them later today (hopefully). - MPI packaging guidelines have changed (https://fedor

Re: MPI updates (soname bumps)

On 11/01/2012 09:08 AM, Orion Poplawski wrote: - I'm planning on building mpich2 1.5 shortly in rawhide with the above module changes. Updating to 1.5 also for hwloc 1.5 support. This is a soname bump from .3 to .8 as well. -- Orion Poplawski Technical Manager 303-415-970

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On Thu, Nov 1, 2012 at 10:56 AM, Heiko Adams wrote: > Maybe we should think again about switching to a roling release models > for Fedora stable. This would IMHO have some benefits to the whole > community. I'm afraid a rolling release model would make it *harder* to make major changes to Fedora,

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On Thu, Nov 1, 2012 at 10:25 AM, Allan Day wrote: > It's important to recognise the negative effects of delays to the release. OLPC is downstream of F18, and planning to ship an "OLPC OS" version 13.1.0 first week of December 2012 (approx); which will be based on F18. We are not affected by Anac

[perl-podlators] Do not export under-specified dependencies

commit c680f3ad42b87972392ae01751448a370400a137 Author: Petr Písař Date: Thu Nov 1 16:57:03 2012 +0100 Do not export under-specified dependencies perl-podlators.spec | 10 -- 1 files changed, 8 insertions(+), 2 deletions(-) --- diff --git a/perl-podlators.spec b/perl-podlators.s

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On 11/01/2012 07:32 AM, David Lehman wrote: On Thu, 2012-11-01 at 13:01 +, "Jóhann B. Guðmundsson" wrote: On 11/01/2012 12:22 PM, Michael Scherer wrote: Maybe having some kind of dependencies between feature could also be a idea. Anaconda requires dracut to not change, so we need a way to e

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, 2012-11-01 at 09:56 -0400, Matthew Miller wrote: > On Thu, Nov 01, 2012 at 09:24:52AM +0200, Panu Matilainen wrote: > > There are features and features... some of them are new versions of > > leafnode packages or a just bunch of new packages which nothing else > > depends on, and some of th

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On Thu, 2012-11-01 at 09:32 -0500, David Lehman wrote: > On Thu, 2012-11-01 at 13:01 +, "Jóhann B. Guðmundsson" wrote: > > On 11/01/2012 12:22 PM, Michael Scherer wrote: > > > Maybe having some kind of dependencies between feature could also be a > > > idea. Anaconda requires dracut to not chan

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On Thu, 2012-11-01 at 15:56 +0100, Heiko Adams wrote: > Am 01.11.2012 15:41, schrieb "Jóhann B. Guðmundsson": > > > > We ( QA community ) would benefit from a longer release cycle since we > > need more time to properly test "features" and other vital components > > and arguably the QA part of an

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

On Thu, Nov 1, 2012 at 5:12 PM, Adam Williamson wrote: > On Thu, 2012-11-01 at 09:32 -0500, David Lehman wrote: > > On Thu, 2012-11-01 at 13:01 +, "Jóhann B. Guðmundsson" wrote: > > > On 11/01/2012 12:22 PM, Michael Scherer wrote: > > > > Maybe having some kind of dependencies between feature

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On 11/01/2012 07:08 PM, Adam Williamson wrote: On Thu, 2012-11-01 at 09:56 -0400, Matthew Miller wrote: On Thu, Nov 01, 2012 at 09:24:52AM +0200, Panu Matilainen wrote: There are features and features... some of them are new versions of leafnode packages or a just bunch of new packages which no

Re: Fedora 18 : broken configuration for httpd 2.4

It would have been super nice to actually include a link in all of those bugs, or some reference. I mean, they must have been filed by program, so it's not as if you would have had to do a bunch of extra typing. We really need a "mass bug filing howto" or something. Preferably starting with "Don

Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

Adam Williamson wrote: > I didn't want to throw this grenade into the debate, but now someone > else has, I'll just note that I was in favour of this before and I'm > still in favour of it now. :) Rolling release is a model that makes > clear sense for a distribution with the goals that Fedora has.

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, Nov 01, 2012 at 10:08:39AM -0700, Adam Williamson wrote: > I was rather thinking we can simply take advantage of the critical path > definition here. After all, when we came up with the critpath, the idea > was it was a general concept which could be useful beyond the idea of a > 'critpath

Re: still UsrMove problems and wrong PATH in openssh

Björn Persson (bjorn@rombobjörn.se) said: > Emmanuel Seyman wrote: > > From bug #871503 (and I apologize if I'm reading this wrong), it > > appears that the dependency on /bin/perl is being caused by the > > hardcoded $PATH in openssh. > > > > To fix the problem, I think we would not only need to

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

- Original Message - > On Thu, Nov 01, 2012 at 10:08:39AM -0700, Adam Williamson wrote: > > I was rather thinking we can simply take advantage of the critical > > path > > definition here. After all, when we came up with the critpath, the > > idea > > was it was a general concept which coul

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On 11/01/2012 06:09 PM, Jaroslav Reznik wrote: We were thinking with a few folks more about "Self contained feature" but yeah, there's a lack of real definition. Other thing is - these "Self contained features" could be approved implicitly once are announced on devel list (in cooperation with Fe

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

- Original Message - > On 11/01/2012 06:09 PM, Jaroslav Reznik wrote: > > We were thinking with a few folks more about "Self contained > > feature" > > but yeah, there's a lack of real definition. > > > > Other thing is - these "Self contained features" could be approved > > implicitly once

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, Nov 01, 2012 at 02:09:21PM -0400, Jaroslav Reznik wrote: > > That sounds good. Maybe recast those ideas as three levels? > > - Critical Path Feature > > - Other Enhancement Feature > > - New Leaf Feature > We were thinking with a few folks more about "Self contained feature" > but yeah,

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, Nov 1, 2012 at 7:34 PM, Matthew Miller wrote: > On Thu, Nov 01, 2012 at 02:09:21PM -0400, Jaroslav Reznik wrote: >> > That sounds good. Maybe recast those ideas as three levels? >> > - Critical Path Feature >> > - Other Enhancement Feature >> > - New Leaf Feature >> We were thinking wit

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

- Original Message - > On Thu, Nov 1, 2012 at 7:34 PM, Matthew Miller > wrote: > > On Thu, Nov 01, 2012 at 02:09:21PM -0400, Jaroslav Reznik wrote: > >> > That sounds good. Maybe recast those ideas as three levels? > >> > - Critical Path Feature > >> > - Other Enhancement Feature > >> >

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, Nov 1, 2012 at 7:45 PM, Jaroslav Reznik wrote: > - Original Message - >> On Thu, Nov 1, 2012 at 7:34 PM, Matthew Miller >> wrote: >> > On Thu, Nov 01, 2012 at 02:09:21PM -0400, Jaroslav Reznik wrote: >> >> > That sounds good. Maybe recast those ideas as three levels? >> >> > - Cr

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, Nov 1, 2012 at 2:45 PM, Jaroslav Reznik wrote: > - Original Message - >> On Thu, Nov 1, 2012 at 7:34 PM, Matthew Miller >> wrote: >> > On Thu, Nov 01, 2012 at 02:09:21PM -0400, Jaroslav Reznik wrote: >> >> > That sounds good. Maybe recast those ideas as three levels? >> >> > - Cr

Fedora 18 ARM Alpha Release

The Fedora ARM team is pleased to announce that the Fedora 18 Alpha release for ARM is now available for download from: http://dl.fedoraproject.org/pub/fedora-secondary/releases/test/18-Alpha/Images/armhfp/ The Alpha release includes prebuilt images for the Trimslice, Pandaboard and Highbank har

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, Nov 01, 2012 at 07:41:21PM +0100, drago01 wrote: > > I think "Leaf" is better than "Self contained", since it's unlikely for the > > feature to have zero outside dependencies. I think it'd be fine for such a > > feature to rely on small changes to existing packages (version updates, > > say

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, 2012-11-01 at 19:50 +0100, drago01 wrote: > On Thu, Nov 1, 2012 at 7:45 PM, Jaroslav Reznik wrote: > > - Original Message - > >> On Thu, Nov 1, 2012 at 7:34 PM, Matthew Miller > >> wrote: > >> > On Thu, Nov 01, 2012 at 02:09:21PM -0400, Jaroslav Reznik wrote: > >> >> > That sounds

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

The other thing that we mustn't forget are major changes that aren't put through the feature process, but slip in "via the back door". Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, Nov 01, 2012 at 08:13:57PM +, Richard W.M. Jones wrote: > The other thing that we mustn't forget are major changes that aren't > put through the feature process, but slip in "via the back door". That's where the critpath vs. other enhancement distinction comes in -- for critpath we can

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On 11/01/2012 08:13 PM, Richard W.M. Jones wrote: The other thing that we mustn't forget are major changes that aren't put through the feature process, but slip in "via the back door". As far as I know you are not obligated to participate in the feature process and what do you exactly define a

[perl-MIME-Types/f18] Update to 1.36

Summary of changes: 3863b4d... Update to 1.36 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mail

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, 2012-11-01 at 21:28 +, "Jóhann B. Guðmundsson" wrote: > On 11/01/2012 08:13 PM, Richard W.M. Jones wrote: > > The other thing that we mustn't forget are major changes that aren't > > put through the feature process, but slip in "via the back door". > > As far as I know you are not obli

Re: MPI updates

On Thu, 01 Nov 2012 09:08:36 -0600 Orion Poplawski wrote: > Some MPI updates: > > - I built openmpi 1.6.3 in rawhide yesterday. This had an unexpected > bump in the libmpi_f90.so soname. I know this affects hdf5 and > netcdf-fortran, both my packages and I'll be rebuilding them later > today (h

Re: Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

On Thu, Nov 01, 2012 at 02:43:00PM -0700, Adam Williamson wrote: > I think I once proposed that FESCo should formally have the ability to > declare that a given change ought to be a feature and force it through > the feature process, but that proposal was rejected. I think that requiring the featu

f18tc6 + texlive 2012: usable docbook, doxygen pdf toolchains

Using F18 TC6 in a KVM install, I was able to install texlive-2012 as per the updates-testing packages, and look at the state of generating documenation with DocBook toolchains using dblatex and Doxygen toolchains using pdflatex. This is related to RH488651, the tracker bug to update TeX in Fedo

Re: f18tc6 + texlive 2012: usable docbook, doxygen pdf toolchains

On Qui, 2012-11-01 at 19:14 -0700, Benjamin De Kosnik wrote: > Using F18 TC6 in a KVM install, I was able to install texlive-2012 as > per the updates-testing packages, and look at the state of generating > documenation with DocBook toolchains using dblatex and Doxygen > toolchains using pdflatex.

new setting for SYSFONT attribute

Hi, I am working on bug (https://bugzilla.redhat.com/show_bug.cgi?id=871119)/etc/sysconfig/i18n is no longer used. On fedora 17, system-config-language sets attributes LANG,SYSFONT in /etc/sysconfig/i18n file. Fedora 18, i checked the locale.conf file which has only one attribute i.e LANG. I wo

Re: Re: Deploying fedora infrastructure (koji) across clouds

On Thu, 1 Nov 2012, Michael Scherer wrote: Le jeudi 01 novembre 2012 à 08:32 -0400, Mo Morsi a écrit : On 10/31/2012 01:07 PM, Seth Vidal wrote: You can orchestrate all of these steps across/between multiple systems using ansible: http://ansible.cc - I've been documenting spinning up and