Re: GCC 5 compatibility problems: GCC 4.10?

It's not in Fedora - RStudio Server. It's not in any distro; they package it themselves for Debian/Ubuntu, openSUSE and RHEL/CentOS. If you want it on Fedora you have to build it from source. On Fri, May 8, 2015 at 8:33 PM, Rex Dieter wrote: > M. Edward (Ed) Borasky wrote: > >> Yes, I'm currently

Re: GCC 5 compatibility problems: GCC 4.10?

Paolo Bonzini wrote: > Hi all, > > I'm encountering a few problems with GCC 5 due to code that fails to > work with GCC major releases above 4. In particular, there are at least > problems with the kernel fedora's kernel builds, can you be more specific about the problems you're experiencing?

Re: GCC 5 compatibility problems: GCC 4.10?

M. Edward (Ed) Borasky wrote: > Yes, I'm currently blocked with a major package that compiles on GCC > 4.9.1 but collapses in the link step on GCC 5.1.1. I've notified the > upstream and they're either fix it or tell me to abandon hope of > running on Fedora. ;-) What package? -- Rex -- devel

Introduction

Hi everyone, New member here! My name is Aditya Prakash. I am second year computer science student at NIT Durgapur , India. This summer, I will be working on Glittergallery under GSoC. In case you have never heard of it,

Re: Review or swap for burp - network backup

On Fri, 2015-05-08 at 00:42 +0200, gil wrote: > Il 08/05/2015 00:37, Jerry James ha scritto: > > On Thu, May 7, 2015 at 3:33 PM, gil wrote: > > > Hi > > > I'm not sure if AGPLV3 is a valid license for Fedora > > See https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#Soft > > wareLicenses >

[Test-Announce] Planned Outage: Taskotron - 2015-05-11 19:00 UTC

Planned Outage: Taskotron - 2015-05-11 19:00:00 UTC There will be an outage starting at 2015-05-11 19:00:00 UTC, which will last about 15 minutes To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2015-05-11 19:00:00 UTC' ---

Re: Help understanding failing Koji build

On Fri, May 8, 2015 at 4:26 PM, Orion Poplawski wrote: > suitesparse was not properly retired in EPEL. It's being fixed now. > Should > be working once the next EL6 repo gen is complete, hopefully 30 minutes or > so. > Thanks! I'll try it when I get back on network that is not behind an HTTP pr

Re: Help understanding failing Koji build

On 05/08/2015 12:27 PM, Taylor Braun-Jones wrote: > Hi, > > I'm having trouble understanding why the following el6-candidate Koji build is > failing: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=9687724 > > Local mock build works fine on my machine (i.e. with `fedpkg mockbuild`). The

Re: Help understanding failing Koji build

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/08/2015 10:04 PM, Taylor Braun-Jones wrote: > On Fri, May 8, 2015 at 3:56 PM, Antonio Trande > mailto:anto.tra...@gmail.com>> wrote: > > suitesparse has been retired on EPEL6 > (https://admin.fedoraproject.org/pkgdb/package/suitesparse/). You

Re: Help understanding failing Koji build

On Fri, May 8, 2015 at 3:56 PM, Antonio Trande wrote: > suitesparse has been retired on EPEL6 > (https://admin.fedoraproject.org/pkgdb/package/suitesparse/). You > should require a rebuild on EPEL6 if possible, otherwise you cannot > build your package in https://koji.fedoraproject.org. > I don'

Re: Help understanding failing Koji build

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/08/2015 09:28 PM, Taylor Braun-Jones wrote: > On Fri, May 8, 2015 at 3:07 PM, Antonio Trande > mailto:anto.tra...@gmail.com>> wrote: > > Your koji build requires suitesparse-devel >= 3.4.0-9 > > DEBUG util.py:388: Error: No Package found for

[Test-Announce] Fedora 22 Final Test Compose 3 (TC3) Available Now!

As per the Fedora 22 schedule [1], Fedora 22 Final Test Compose 3 (TC3) is now available for testing. Please help us complete as much of the validation testing as we can! This build includes the anaconda hack which should finally resolve (well, more sort of hide) all the UnicodeDecodeError bugs. I

Re: firewall-offline-cmd needs a --quiet option

- Original Message - > From: "K Richard Pixley" > To: "Development discussions related to Fedora" > > Sent: Friday, May 8, 2015 3:14:13 PM > Subject: firewall-offline-cmd needs a --quiet option > > That's all I really have to say on this. > > I don't know where else to raise the issue

Re: Help understanding failing Koji build

On Fri, May 8, 2015 at 3:07 PM, Antonio Trande wrote: > Your koji build requires suitesparse-devel >= 3.4.0-9 > > DEBUG util.py:388: Error: No Package found for suitesparse-devel >= > 3.4.0-9 > > a release unavailable on EPEL6: > http://koji.fedoraproject.org/koji/packageinfo?packageID=4724 > >

firewall-offline-cmd needs a --quiet option

That's all I really have to say on this. I don't know where else to raise the issue, though. There doesn't seem to be a project page or contact info for firewalld developers that I can find. I wouldn't even know what to do with the patches if I wrote it. --rich -- devel mailing list devel@list

Re: Help understanding failing Koji build

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/08/2015 08:58 PM, Taylor Braun-Jones wrote: > On Fri, May 8, 2015 at 2:30 PM, Antonio Trande > mailto:anto.tra...@gmail.com>> wrote: > > root.log --> tail: > > https://koji.fedoraproject.org/koji/getfile?taskID=9687732&name=root.log&offset=-4

Re: Help understanding failing Koji build

On Fri, May 8, 2015 at 2:30 PM, Antonio Trande wrote: > root.log --> tail: > > > https://koji.fedoraproject.org/koji/getfile?taskID=9687732&name=root.log&offset=-4000 > Shoot, I totally missed that somehow... But now the question is why my local mock build works, but the Koji build does not. Fo

Re: Help understanding failing Koji build

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/08/2015 08:27 PM, Taylor Braun-Jones wrote: > Hi, > > I'm having trouble understanding why the following el6-candidate > Koji build is failing: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=9687724 > > Local mock build works fine o

Help understanding failing Koji build

Hi, I'm having trouble understanding why the following el6-candidate Koji build is failing: https://koji.fedoraproject.org/koji/taskinfo?taskID=9687724 Local mock build works fine on my machine (i.e. with `fedpkg mockbuild`). The Koji x86_64 and i686 build.log files both simply end with "LEAVE d

Re: GCC 5 compatibility problems: GCC 4.10?

Yes, I'm currently blocked with a major package that compiles on GCC 4.9.1 but collapses in the link step on GCC 5.1.1. I've notified the upstream and they're either fix it or tell me to abandon hope of running on Fedora. ;-) On Fri, May 8, 2015 at 9:10 AM, Paolo Bonzini wrote: > Hi all, > > I'm

Self Introduction: Stefan Cornelius

Hi, I'm Stefan Cornelius from Germany and will turn 31 within the next couples of days. I've decided very early to focus on security, which is why I now have a decade of hobby and professional Linux experience, with nothing to show for in terms of code or packages provided. Time to change that a

Re: GNOME 3 bug?

On Fri, 2015-05-08 at 09:42 -0600, Nathanael D. Noblet wrote: > > So is this a bug? Is there a way to 'reset' gnome settings to > defaults? Or detect differences between defaults and a user's > settings > that may have caused this? I ask because previously I had window > focus > set to follow

GCC 5 compatibility problems: GCC 4.10?

Hi all, I'm encountering a few problems with GCC 5 due to code that fails to work with GCC major releases above 4. In particular, there are at least problems with the kernel and with Coverity. Unfortunately, downgrading to Fedora 21's GCC 4.9 is very hard in Fedora 22, unless you only care about

GNOME 3 bug?

Hello, I updated my F21 workstation to F22 beta. Everything has gone well except for some bug in GNOME. Window focus is messed up. When I click on a window in the background it gets focus, but doesn't come to the foreground. Only clicking a window title brings it forward. A side effect of thi

Re: Taskotron check failed, but I think it's not my fault

On Fri, 8 May 2015 16:59:22 +0300 Igor Gnatenko wrote: > Hi, > > I pushed mesa update into F22, but actually testing failed at some > packages. > > I think its not related to my update. > > https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/67288/steps/runtask/logs/stdio >

Taskotron check failed, but I think it's not my fault

Hi, I pushed mesa update into F22, but actually testing failed at some packages. I think its not related to my update. https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/67288/steps/runtask/logs/stdio Can you check what happened? -- devel mailing list devel@lists.fedoraproj

rawhide report: 20150508 changes

Compose started at Fri May 8 05:15:03 UTC 2015 Broken deps for i386 -- [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [aeskulap] aeskulap-0.2.2-0.19beta1.fc22.i686 requires libofstd.so.3.6 aesku

F-22 Branched report: 20150508 changes

Compose started at Fri May 8 07:15:02 UTC 2015 Broken deps for armhfp -- [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [aeskulap] aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libofstd.so.3.6