Re: Rebuilding gcc on Fedora 18 - Howto build i686 packages on a x86_64 machine

On Wed, 28 Aug 2013 06:48:24 +0200, Jon Miller wrote: > How do the experts build the i686 & x86_64 packages? (I did notice the "Build > Host" varies between the two, so I'm wondering if I need to build a 32bit > Fedora 18 instance to repeat this build process?) With some packages it is possible to

Re: Rebuilding gcc on Fedora 18 - Howto build i686 packages on a x86_64 machine

On Tue, 2013-08-27 at 21:48 -0700, Jon Miller wrote: > How do the experts build the i686 & x86_64 packages? (I did notice the "Build > Host" varies between the two, so I'm wondering if I need to build a 32bit > Fedora 18 instance to repeat this build process?) Use mock: mock -r fedora-18-i386

Rebuilding gcc on Fedora 18 - Howto build i686 packages on a x86_64 machine

Hello, Hoping this is the correct place to ask this type of question & also hope it's an easy / quick one. I'll gladly ask elsewhere if not. We have ran into a compiler issue with gcc and I was looking to apply a small patch[1] and I've done so via pulling down the gcc src.rpm on my updated Fedor

Re: Graphics driver support in F21+

On Tue, Aug 27, 2013 at 04:30:25PM -0400, john.flor...@dart.biz wrote: > > From: mj...@srcf.ucam.org > > On Tue, Aug 27, 2013 at 02:54:46PM +, "Jóhann B. Guðmundsson" wrote: > > > > > "From this point forward only graphics driver that have kms support > > > will be allow to be packaged and shi

Re: Why is AHCI built-in?

On 19.08.2013 20:46, Kyle McMartin wrote: > On Mon, Aug 19, 2013 at 01:35:16PM -0500, Ian Pilcher wrote: >> On 08/19/2013 01:19 PM, Kyle McMartin wrote: >>> because it's commonly used and found on basically every machine now. >>> there are many advantages to having it built in that outweigh the con

Re: [libntlm/f19: 2/3] New version with cleanup.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Its not okay to use "Author: Koji " as your git config. please fix it immediately to use your real name and email Dennis On Mon, 26 Aug 2013 03:07:35 + (UTC) Christopher Meng wrote: > commit dee12b4f18564a2bfd99d5f93457b7f84a49aea7 > Author: Ko

Re: [ACTION REQUIRED] Retiring long-term FTBFS packages for Fedora 20 v2

I retired the following packages that were reported earlier recently: curry eclipse-phpeclipse fedora-package-config-smart mod_mono nautilus-sendto-trac open-cobol petitboot simulavr smart tiobench The following packages are did not build for two releases and will be retired before the Alpha Chang

Orphaning ne7ssh

Hi. I'll orphan ne7ssh library. It is FBFS after last botan update. Upstream did not answer on my report (only via web-form). As I also do not use it in my development now I do not want spent time to even try porting it. -- With best wishes

Re: Graphics driver support in F21+

> From: mj...@srcf.ucam.org > On Tue, Aug 27, 2013 at 02:54:46PM +, "Jóhann B. Guðmundsson" wrote: > > > "From this point forward only graphics driver that have kms support > > will be allow to be packaged and shipped in the distribution" > > Only if you want to drop VESA support. Please don

Re: Graphics driver support in F21+

On Tue, 2013-08-27 at 12:58 -0600, Daniel Drake wrote: > On Tue, Aug 27, 2013 at 9:30 AM, Peter Robinson wrote: > > > >> xorg-x11-drv-geode > > > > > > geode is used on the OLPC XO-1 and is maintained by Daniel Drake (dsd) and > > he's basically done all recent commits for upstream releases and fi

Re: Graphics driver support in F21+

On Tue, Aug 27, 2013 at 9:30 AM, Peter Robinson wrote: > >> xorg-x11-drv-geode > > > geode is used on the OLPC XO-1 and is maintained by Daniel Drake (dsd) and > he's basically done all recent commits for upstream releases and fixes > unless it's been something like an ABI rebuild or similar. I'm

Re: Why is AHCI built-in?

On Mon, 19 Aug 2013 13:16:03 -0500 Ian Pilcher wrote: > (I want to rebuild it with LED triggers for the disk LEDs on my NAS.) Frankly this sounds like madness. You need to build a kernel, it's trivial -- just edit one of configs and rpmbuild -ba, and then you have very clear delineation of what

Re: Comps Cleanup

Kalev Lember (kalevlem...@gmail.com) said: > I'd like to be able to commit to master, check out the f20 branch, and > 'git cherry-pick master'. Is that really that much difference than git diff | sed | patch? In any case, this would (as stated) require fixing the buildrawhide, buildbranced, and

Re: Graphics driver support in F21+

On 08/27/2013 03:14 PM, drago01 wrote: On Tue, Aug 27, 2013 at 4:54 PM, "Jóhann B. Guðmundsson" wrote: Is it not better to drop entirely graphics drivers that do not have kms support and at the *same time* adopt the policy "From this point forward only graphics driver that have kms support wi

ino - Desperately looking for a new maintainer (with an actual Arduino)

Hi, I've somehow managed to build and maintain a bit package ino. The reason is simple - I need it as a BuildRequires for some other package. However I don't have an Arduino and is very hard for me to test the package in action and respond / solve the bugs related to it. I don't want to orpha

Re: Graphics driver support in F21+

On Tue, Aug 27, 2013 at 02:54:46PM +, "Jóhann B. Guðmundsson" wrote: > "From this point forward only graphics driver that have kms support > will be allow to be packaged and shipped in the distribution" Only if you want to drop VESA support. -- Matthew Garrett | mj...@srcf.ucam.org -- deve

Re: Graphics driver support in F21+

On Tue, Aug 27, 2013 at 10:46:19AM -0400, Adam Jackson wrote: > For F21, I plan to orphan the following X video drivers: > > xorg-x11-drv-apm > xorg-x11-drv-cirrus > xorg-x11-drv-geode > xorg-x11-drv-glint > xorg-x11-drv-i128 > xorg-x11-drv-i740 > xorg-x11-drv-mach64 > xorg-x11-drv-mga > xorg-x11-

Re: Graphics driver support in F21+

> xorg-x11-drv-geode > geode is used on the OLPC XO-1 and is maintained by Daniel Drake (dsd) and he's basically done all recent commits for upstream releases and fixes unless it's been something like an ABI rebuild or similar. I'm sure he'll take over the maintainership if needed. Peter -- deve

Re: Graphics driver support in F21+

On Tue, 2013-08-27 at 14:54 +, "Jóhann B. Guðmundsson" wrote: > Is it not better to drop entirely graphics drivers that do not have kms > support and at the *same time* adopt the policy > > "From this point forward only graphics driver that have kms support will > be allow to be packaged an

Re: Graphics driver support in F21+

On Tue, Aug 27, 2013 at 4:54 PM, "Jóhann B. Guðmundsson" wrote: > On 08/27/2013 02:46 PM, Adam Jackson wrote: >> >> For F21, I plan to orphan the following X video drivers: >> >> xorg-x11-drv-apm >> xorg-x11-drv-cirrus >> xorg-x11-drv-geode >> xorg-x11-drv-glint >> xorg-x11-drv-i128 >> xorg-x11-dr

Re: Graphics driver support in F21+

On Tue, 2013-08-27 at 10:58 -0400, Brian Wheeler wrote: > Out of curiosity, is the cirrus driver used in qemu/kvm or does it use > something else? There's a KMS driver for qemu's cirrus emulation now; X loads xorg-x11-drv-modesetting in that scenario. (Likewise for the Matrox G200SE series of se

Re: Graphics driver support in F21+

Out of curiosity, is the cirrus driver used in qemu/kvm or does it use something else? On 08/27/2013 10:46 AM, Adam Jackson wrote: For F21, I plan to orphan the following X video drivers: xorg-x11-drv-apm xorg-x11-drv-cirrus xorg-x11-drv-geode xorg-x11-drv-glint xorg-x11-drv-i128 xorg-x11-drv

Re: Graphics driver support in F21+

On 08/27/2013 02:46 PM, Adam Jackson wrote: For F21, I plan to orphan the following X video drivers: xorg-x11-drv-apm xorg-x11-drv-cirrus xorg-x11-drv-geode xorg-x11-drv-glint xorg-x11-drv-i128 xorg-x11-drv-i740 xorg-x11-drv-mach64 xorg-x11-drv-mga xorg-x11-drv-neomagic xorg-x11-drv-r128 xorg-x1

Graphics driver support in F21+

For F21, I plan to orphan the following X video drivers: xorg-x11-drv-apm xorg-x11-drv-cirrus xorg-x11-drv-geode xorg-x11-drv-glint xorg-x11-drv-i128 xorg-x11-drv-i740 xorg-x11-drv-mach64 xorg-x11-drv-mga xorg-x11-drv-neomagic xorg-x11-drv-r128 xorg-x11-drv-rendition xorg-x11-drv-s3virge xorg-x11-

Re: Overall rawhide package testing.

There are many false positive issues with RubyGems in the report. Namely about: 279 GemCheckRequiresRubygems https://fedorahosted.org/FedoraReview/ticket/224 333 RubyCheckTestsRun https://fedorahosted.org/FedoraReview/ticket/225 I already submitted patch to address the first issue. Regards Jose

Re: Unresponsive maintainer of plasma-widget-menubar

- Original Message - > Oh? The Changes wrangler? Yeah, me and sorry about that :( Problem solved. Jaroslav > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Unresponsive maintainer of plasma-widget-menubar

Am Sonntag, 25. August 2013, 14:39:50 schrieben Sie: > Hi, > > the package maintainer of plasma-widget-menubar doesn't response for some > months. The package needs to be updated to v0.2.0. See > https://bugzilla.redhat.com/show_bug.cgi?id=952360. > > I like to take the maintainership. > Problem

Reminder: Fedora 20 Alpha Change Deadline in one week

Greeting! This is a reminder, that the Alpha Change Deadline is coming in one week, on Sep 03, according to the schedule approved by FESCo [1]. After the freeze, you will have to use Bodhi for any updates to branched Fedora 20. Updates will land in updates-testing after being pushed. Updates that

Re: Fonts with default Fedora installation

On 27 August 2013 14:04, Nicolas Mailhot wrote: > > Le Mar 27 août 2013 06:34, pravin@gmail.com a écrit : > > > Yeah. > > If someone does specific request for SMP we should go ahead with it. At > > the > > end of days it is going to take only some kb's space in ISO's. > > I know it's probably

Re: Fonts with default Fedora installation

Le Mar 27 août 2013 06:34, pravin@gmail.com a écrit : > Yeah. > If someone does specific request for SMP we should go ahead with it. At > the > end of days it is going to take only some kb's space in ISO's. I know it's probably wishful thinking on my part, but it would be great if all the lo