F-22 Branched report: 20150508 changes

2015-05-08 Thread Fedora Branched Report
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
aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires liboflog.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libijg8.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libijg16.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libijg12.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmnet.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmjpeg.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmimgle.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmimage.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmdata.so.3.6
[crystal]
crystal-2.2.1-2.fc22.armv7hl requires libkdecorations.so.4
[dnssec-check]
dnssec-check-1.14.0.1-4.fc20.armv7hl requires libval-threads.so.14
dnssec-check-1.14.0.1-4.fc20.armv7hl requires libsres.so.14
[gcc-python-plugin]
gcc-python2-debug-plugin-0.13-2.fc22.armv7hl requires gcc = 
0:4.9.2-1.fc22
gcc-python2-plugin-0.13-2.fc22.armv7hl requires gcc = 0:4.9.2-1.fc22
gcc-python3-debug-plugin-0.13-2.fc22.armv7hl requires gcc = 
0:4.9.2-1.fc22
gcc-python3-plugin-0.13-2.fc22.armv7hl requires gcc = 0:4.9.2-1.fc22
[kde-style-skulpture]
kde-style-skulpture-0.2.4-9.fc22.armv7hl requires libkdecorations.so.4
[leksah]
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(utf8-string-0.3.7-013ef9ad8ac70ebb11df31f487b74f26)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(unix-2.6.0.1-7550b9ae9dbc74e4d6570cc239a29030)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(transformers-0.3.0.0-23508e0b4a1c1bc1cf2c2de3bb13e90c)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(time-1.4.0.1-970760bdd865d8b6cafac382276795a2)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(text-0.11.3.1-17cae9ba49c3f3d533bf78a6e387f543)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(strict-0.3.2-04f0cc1e99eff2196c0a7cd16d748b37)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(regex-tdfa-1.1.8-0b03687c4e38c00ef92e9445170081e2)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(regex-base-0.93.2-6a541a53412d1d7d310fa69bca50c85f)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(pretty-1.1.1.0-2de27f83b2c1c65d629a564e9e01b27d)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(parsec-3.1.3-a8bebef411959de671abb0f1f7da556f)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(old-time-1.1.0.1-29c02e2b3bbdfd9a5756f0c46f4d6071)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(network-2.4.1.2-82f6bcf79fe0252b3ab387e8dcb82e71)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(mtl-2.1.2-2f2cd438035824ec2bed4811930bc232)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(ltk-0.12.1.0-2fbb10498719be9dbdbb3d9f8adedbec)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(leksah-server-0.12.1.2-7dbd70c9f5e4dd8b3b5efcb6597b3bfd)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(hslogger-1.2.1-43834164508859009a3cc8aef7fd1e84)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(gtksourceview2-0.12.5.0-588b179d0562576f9afa46559cebf79f)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(gtk-0.12.5.0-2342a114ec8897cecfdda15ac92aed08)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(glib-0.12.5.0-1b94df160e141377711a221615168695)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(gio-0.12.5.0-b012293268f349d8f05c73d053798c7b)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(ghc-7.6.3-18fc786f8ad3478b9bb568d865b0e48d)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(filepath-1.3.0.1-62570c67b40fb99e7078c0d179220531)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(enumerator-0.4.19-a164f71ed1088e349dd8bc4cdee8e449)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(directory-1.2.0.1-504c99535d64699e20e001d81b577d06)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(deepseq-1.3.0.1-aa1be128186a233c7290faf88620ffe5)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(containers-0.5.0.0-3b8b869ec10d44736414ab5bea776319)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(bytestring-0.10.0.2-ea1d6622fb7aad447c7746744ecded40)
ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires 
ghc-devel(binary-shared-0.8.3-e7b0a0ea6f1cabbb7494156068d1e65c)
g

rawhide report: 20150508 changes

2015-05-08 Thread Fedora Rawhide Report
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
aeskulap-0.2.2-0.19beta1.fc22.i686 requires liboflog.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg8.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg16.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg12.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmnet.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmjpeg.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmimgle.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmimage.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmdata.so.3.6
[crystal]
crystal-2.2.1-2.fc22.i686 requires libkdecorations.so.4
[dleyna-connector-dbus]
dleyna-connector-dbus-0.2.0-4.fc22.i686 requires libdleyna-core-1.0.so.3
[dleyna-server]
dleyna-server-0.4.0-7.fc23.i686 requires libdleyna-core-1.0.so.3
[dmlite-plugins-memcache]
dmlite-plugins-memcache-0.5.0-7.fc20.i686 requires libprotobuf.so.8
[dmlite-plugins-s3]
dmlite-plugins-s3-0.5.1-5.fc22.i686 requires libprotobuf.so.8
[dsqlite]
dsqlite-1.1.1-5.fc22.i686 requires libphobos-ldc.so.64
[gazebo]
gazebo-4.0.2-2.fc22.i686 requires libprotobuf.so.8
gazebo-libs-4.0.2-2.fc22.i686 requires libprotobuf.so.8
player-gazebo-4.0.2-2.fc22.i686 requires libprotobuf.so.8
[gl3n]
gl3n-0.20140505-13.fc22.i686 requires libphobos-ldc.so.64
[julia]
julia-0.3.7-2.fc23.i686 requires libLLVM-3.5.so
julia-devel-0.3.7-2.fc23.i686 requires libLLVM-3.5.so
[kde-style-skulpture]
kde-style-skulpture-0.2.4-9.fc22.i686 requires libkdecorations.so.4
[latte-integrale]
4ti2-1.6.2-9.fc23.1.i686 requires 4ti2-libs(x86-32) = 0:1.6.2-9.fc23
4ti2-devel-1.6.2-9.fc23.1.i686 requires 4ti2-libs(x86-32) = 
0:1.6.2-9.fc23
[leksah]
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSxhtml-3000.2.1-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSutf8-string-0.3.7-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSunix-2.6.0.1-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHStransformers-0.3.0.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHStime-1.4.0.1-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHStext-0.11.3.1-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHStemplate-haskell-2.8.0.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSstrict-0.3.2-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSregex-tdfa-1.1.8-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSregex-base-0.93.2-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSrandom-1.0.1.1-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSprocess-1.1.0.2-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSpretty-1.1.1.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSparsec-3.1.3-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSpango-0.12.5.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSold-time-1.1.0.1-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSold-locale-1.0.0.5-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSnetwork-2.4.1.2-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSmtl-2.1.2-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSltk-0.12.1.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSleksah-server-0.12.1.2-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSinteger-gmp-0.5.0.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHShslogger-1.2.1-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHShpc-0.6.0.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHShoopl-3.9.0.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHShaddock-2.13.2-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSgtksourceview2-0.12.5.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSgtk-0.12.5.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSglib-0.12.5.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSgio-0.12.5.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSghc-prim-0.3.0.0-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSghc-paths-0.1.0.9-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSghc-7.6.3-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22.i686 requires 
libHSfilepath-1.3.0.1-ghc7.6.3.so
ghc-leksah-0.12.1.3-16.fc22

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

2015-05-08 Thread Igor Gnatenko
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.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

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

2015-05-08 Thread Tim Flink
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
> 
> Can you check what happened?

Yeah, that's a bug in depcheck that we've been working on for a while
now:
  https://phab.qadevel.cloud.fedoraproject.org/T366

We just deployed a workaround for this issue yesterday and the invalid
failures from this bug won't show up in bodhi anymore.

Apologies for the inconvenience,

Tim


pgp5B9P8gLmOv.pgp
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

GNOME 3 bug?

2015-05-08 Thread Nathanael D. Noblet
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 this
behaviour if I click and drag a window that wasn't already the 'top'
most window, it drags it behind all other windows. Makes it difficult
to manage window placement if you can't see it.

  A new user created doesn't have the same issues.

  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 the mouse at one point so perhaps a series of non
-standard settings is causing this.

  Finally is this something that I should file a bug on?

-- 
Nathanael
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

GCC 5 compatibility problems: GCC 4.10?

2015-05-08 Thread Paolo Bonzini
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 the C compiler.  This is because the C++
compiler wants a matching libstdc++, and most C++ packages need the GCC
5 libstdc++ (maybe because of the ABI changes, I don't know).

Is it outrageous to ask for a "compatibility" GCC package that declares
itself as 4.10?  This is similar to how kernel 3.0 was initially
packaged as 2.6.40.  Or perhaps there is another possibility that I
haven't thought of?

Thanks,

Paolo

-- 
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: GNOME 3 bug?

2015-05-08 Thread Nathanael D. Noblet
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 the mouse at one point so perhaps a series of non
> -standard settings is causing this.
> 
>   Finally is this something that I should file a bug on?

Deleting a host of .gnome directories and re-logging in seems to have
fixed the window focus issue at the expense of having lost some other
minor settings.

> 
> -- 
> Nathanael
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Self Introduction: Stefan Cornelius

2015-05-08 Thread 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
bit, isn't it? ;)

To be honest, my contributions in terms of packaging will be very
limited - and horribly egoistic. I want to get Capstone
into Fedora, both out of personal and professional reasons (as
part of Red Hat Product Security). For that, I need help reviewing
the package so that it can go into Fedora. I'll also need a
sponsor in order to become a packager, so that I can act as
capstone maintainer. Any help or pointers will be greatly appreciated!

capstone. http://www.capstone-engine.org/
"Capstone is a lightweight multi-platform, multi-architecture
disassembly framework.

Our target is to make Capstone the ultimate disassembly engine for
binary analysis and reversing in the security community."

Review request:
https://bugzilla.redhat.com/show_bug.cgi?id=1098965

Upstream is aware of the packaging process and supports it 100%.

Thanks and kind regards,
-- 
Stefan Cornelius / Red Hat Product Security

Come talk to Red Hat Product Security at the Summit!
Red Hat Summit 2015 - https://www.redhat.com/summit/
-- 
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: GCC 5 compatibility problems: GCC 4.10?

2015-05-08 Thread M. Edward (Ed) Borasky
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 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 the C compiler.  This is because the C++
> compiler wants a matching libstdc++, and most C++ packages need the GCC
> 5 libstdc++ (maybe because of the ABI changes, I don't know).
>
> Is it outrageous to ask for a "compatibility" GCC package that declares
> itself as 4.10?  This is similar to how kernel 3.0 was initially
> packaged as 2.6.40.  Or perhaps there is another possibility that I
> haven't thought of?
>
> Thanks,
>
> Paolo
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct



-- 
OSJourno: Robust Power Tools for Digital Journalists
http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists

Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Help understanding failing Koji build

2015-05-08 Thread Taylor Braun-Jones
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 do -->
" right after the .src.rpm is created. Any ideas?

Thanks,
Taylor
-- 
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: Help understanding failing Koji build

2015-05-08 Thread Antonio Trande
-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 on my machine (i.e. with `fedpkg 
> mockbuild`). The Koji x86_64 and i686 build.log files both simply
> end with "LEAVE do --> " right after the .src.rpm is created. Any
> ideas?
> 
> Thanks, Taylor
> 

root.log --> tail:

https://koji.fedoraproject.org/koji/getfile?taskID=9687732&name=root.log&offset=-4000

- -- 
Antonio Trande

mailto: sagitter 'at' fedoraproject 'dot' org
http://fedoraos.wordpress.com/
https://fedoraproject.org/wiki/User:Sagitter
GPG Key: 0x565E653C
Check on https://keys.fedoraproject.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJVTQDeAAoJEF5tK7VWXmU8IjEH/332HVJkHr/0RqOQM/TPxhSK
KIer27qoW5p2acfgwsVYHeqhjyAPLiChOAIC7fbfjJs/9XbJoecCNiynHWPZdRyK
0sWzwjIX4uavbpuopAoMFnKhSjhBntSI6K14s6SeqpR4qGOLfJP9+nOyr1X/AALY
NfafuGQxwL5G9utBx36EVWqATb7h7uKqd9jOzDWeg1S3f09j3oLYRPVhIFV+ARIL
D5Fboj90hXraGrXVxmI2DrrC44C3QhYaOJ4LwdcQVZZjfwgOxp2uqWHJ852Y0cvl
q4Jq3YBPk+2pLyt2J5QgB9DrOAjlaOaYF5bdjdVLZFQ+LrV8Gf1xKqnkHQ0w0q0=
=/YLy
-END PGP SIGNATURE-
-- 
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: Help understanding failing Koji build

2015-05-08 Thread Taylor Braun-Jones
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. For my local builds, I'm just using the most
up-to-date /etc/mock/epel-6-x86_64.cfg that ships with mock. Looks to me
like the unsatisfied package dependency should be available:

http://mirror.centos.org/centos/6/os/x86_64/Packages/suitesparse-3.4.0-9.el6.x86_64.rpm

Taylor
-- 
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: Help understanding failing Koji build

2015-05-08 Thread Antonio Trande
-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=-4000
>
> 
> 
> Shoot, I totally missed that somehow...
> 
> But now the question is why my local mock build works, but the
> Koji build does not. For my local builds, I'm just using the most 
> up-to-date /etc/mock/epel-6-x86_64.cfg that ships with mock. Looks
> to me like the unsatisfied package dependency should be available:
> 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/suitesparse-3.4.0-9.el6.x86_64.rpm
>
>  Taylor
> 
> 

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

What release of suitesparse is installed on your system?

- -- 
Antonio Trande

mailto: sagitter 'at' fedoraproject 'dot' org
http://fedoraos.wordpress.com/
https://fedoraproject.org/wiki/User:Sagitter
GPG Key: 0x565E653C
Check on https://keys.fedoraproject.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJVTQldAAoJEF5tK7VWXmU81owH/RNTcZryJPrUbLu8ZAXg4JZ3
ZSgTUMPjB50UZ1yFzGwlyCf5g7w8GDNvYv6DNySyt/mXy3YtEzHuQNlfhADWh7SU
iPt/K1hLeXk9ITc0B2+Cg/hHq4uYs7mwFbPOZa+3UHfq3hz8vLDyjdK59b1LU7rJ
9xk2oDJ8l9vsf3iy+GMMHHXkXVO0ejDlmIUo5OCZTWLKGdzcj+3YVXnMX2oPzA8I
E5o2vXz1jH11kbc+7yAiPdjvMngysSzL7OPrXQw5irqqPR8ITtJOrAcs1cET9Bxj
4BVlRJHzkGCIcXqueeAsbJ/jQKC/MkYjGrXfLmAwPRjBhUJdznAi4sdZu7dGsfc=
=j0Rm
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

firewall-offline-cmd needs a --quiet option

2015-05-08 Thread K Richard Pixley
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@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Help understanding failing Koji build

2015-05-08 Thread Taylor Braun-Jones
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
>
> What release of suitesparse is installed on your system?
>

suitesparse-3.4.0-9 comes from CentOS 6.6 base. Here's the relevant section
of my mock build:

...
--> Finished Dependency Resolution

Dependencies Resolved


 Package Arch Version  Repository
 Size

Installing:
 atlas-devel i686 3.8.4-2.el6  base
3.8 M
 cmake28 i686 2.8.11.2-1.el6   epel
7.1 M
 eigen3-develnoarch   3.2.3-1.el6  epel
 16 M
 gflags-develi686 1.3-7.el6epel
 24 k
 suitesparse-devel   i686 3.4.0-9.el6  base
145 k
 tbb-devel   i686 2.2-3.20090809.el6   base
102 k
Installing for dependencies:
 atlas   i686 3.8.4-2.el6  base
2.4 M
 gflags  i686 1.3-7.el6epel
 68 k
 libarchive  i686 2.8.3-4.el6_2base
137 k
 libgfortran i686 4.4.7-11.el6 base
245 k
 suitesparse i686 3.4.0-9.el6  base
502 k
 tbb i686 2.2-3.20090809.el6   base
 74 k

Transaction Summary

Install  12 Package(s)
-- 
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: firewall-offline-cmd needs a --quiet option

2015-05-08 Thread Stephen Gallagher

- 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, 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.
> 

The project page is at https://github.com/t-woerner/firewalld

You can file bugs there as well.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

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

2015-05-08 Thread Adam Williamson
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. It would be
great if folks can test non-English live installs pretty hard with
this and subsequent builds to make sure nothing unexpected has
resulted (and also to make sure the known bugs really are fixed).

Content information, including changes, can be found at 
https://fedorahosted.org/rel-eng/ticket/6166#comment:4 . Please see the
following pages for
download links and testing instructions. Normally dl.fedoraproject.org 
should provide the fastest download, but download-
ib01.fedoraproject.org is available as a mirror (with an approximately 
1 hour lag) in case of trouble. To use it, just replace "dl" with 
"download-ib01" in the download URL.

Installation:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test

Base:

https://fedoraproject.org/wiki/Test_Results:Current_Base_Test

Workstation and Desktop:

https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test

Server:

https://fedoraproject.org/wiki/Test_Results:Current_Server_Test

Cloud:

https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

Summary:

https://fedoraproject.org/wiki/Test_Results:Current_Summary

All non-Optional test cases for each of these test pages [2] must 
pass in order to meet the Final Release Criteria [3].

Help is available on #fedora-qa on irc.freenode.net [4], or on the 
test list [5].

Create Fedora 22 Final test compose (TC) and release candidate (RC) 
https://fedorahosted.org/rel-eng/ticket/6166

Current Blocker and Freeze Exception bugs:
http://qa.fedoraproject.org/blockerbugs/current

[1] 
http://fedorapeople.org/groups/schedule/f-22/f-22-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
[3] https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria
[4] irc://irc.freenode.net/fedora-qa
[5] https://admin.fedoraproject.org/mailman/listinfo/test
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
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: Help understanding failing Koji build

2015-05-08 Thread Antonio Trande
-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 suitesparse-devel
> >= 3.4.0-9
> 
> a release unavailable on EPEL6: 
> http://koji.fedoraproject.org/koji/packageinfo?packageID=4724
> 
> What release of suitesparse is installed on your system?
> 
> 
> suitesparse-3.4.0-9 comes from CentOS 6.6 base. Here's the
> relevant section of my mock build:
> 
> ...

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.


- -- 
Antonio Trande

mailto: sagitter 'at' fedoraproject 'dot' org
http://fedoraos.wordpress.com/
https://fedoraproject.org/wiki/User:Sagitter
GPG Key: 0x565E653C
Check on https://keys.fedoraproject.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJVTRTZAAoJEF5tK7VWXmU8bq8H/0Fh1DIySP/mdvu9kXZufaLh
AKWoPwQjySFibvNdzcRj7xNMzXJXyX/Y3oJU/VNVww/qLscMrnK2NtGZiP6iGuZO
UScnm8VwLGSyQip/Bu/FYzvmtiLB2MgjkBOf9kSQ2UToC6iBNL/6E2Fh962MSl+e
8SwUuhcfsIPZyEQwHsyWM/q9tjMRK2BvQmysCk+YeQkZhpeRlMWbue4HwvovAONq
F5rLXG5OaFtPw8ZGV9Jyhaco9QQ/D8aSzrYCJP7q2GjExoAuhYdAqasJmHCBih5J
pfK7/7iAbnQNn7qRq+QKD5ChNtRlof/rWffrsqgeEdnLiK0fHG9kONBSshol8QY=
=YZ1+
-END PGP SIGNATURE-
-- 
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: Help understanding failing Koji build

2015-05-08 Thread Taylor Braun-Jones
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't need EPEL6 to provide suitesparse - it's provided by CentOS base:

http://mirror.centos.org/centos/6/os/x86_64/Packages/suitesparse-3.4.0-9.el6.x86_64.rpm
-- 
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: Help understanding failing Koji build

2015-05-08 Thread Antonio Trande
-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 
> should require a rebuild on EPEL6 if possible, otherwise you
> cannot build your package in https://koji.fedoraproject.org.
> 
> 
> I don't need EPEL6 to provide suitesparse - it's provided by CentOS
> base:
> 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/suitesparse-3.4.0-9.el6.x86_64.rpm
>
> 
> 

You need suitesparse to build on koji.
Was not that the problem?

- -- 
Antonio Trande

mailto: sagitter 'at' fedoraproject 'dot' org
http://fedoraos.wordpress.com/
https://fedoraproject.org/wiki/User:Sagitter
GPG Key: 0x565E653C
Check on https://keys.fedoraproject.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJVTRjDAAoJEF5tK7VWXmU8y2cH/17pLbd/4BZTMnIFONlt7TYi
hYOTKT3XanboX55JYmv6HjPEh1rytYDCLiXQkOezWSFtMw0hyoEQPyUYbf98uA0N
mr2CBEjCYaFTrJPsY8j8cb9Wx/McbtQ+N3Q78wu6+iPh2zr8Mn/3vel2ySWp5x4C
QfPb73uqbTNvNWumG+kdaQgEBxN6D8uMAq9/W2ekJMZCAFCwmeXfPQv9vtzzvPUU
A+i1XmUf0BKUhhD3v/jV9tLPOcon0uU3gdnDrxBGbKUcWg2Cu5w2cycs5RbhpQi7
EOJQ3ScoRzpnbY/zsVbjiOQhxz3rjazax2G3CWgp164CHc6E/xUJ1u3RXi9nTHM=
=XEA0
-END PGP SIGNATURE-
-- 
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: Help understanding failing Koji build

2015-05-08 Thread Orion Poplawski
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
> Koji x86_64 and i686 build.log files both simply end with "LEAVE do --> "
> right after the .src.rpm is created. Any ideas?
> 
> Thanks,
> Taylor
> 
> 

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.

Also, this probably belongs on epel-devel

-- 
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301   http://www.nwra.com
-- 
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: Help understanding failing Koji build

2015-05-08 Thread Taylor Braun-Jones
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
proxy (the HTTP proxy support in fedpkg is broken[1])


> Also, this probably belongs on epel-devel
>

You're right - I'll use that list next time.

Taylor

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1164561
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

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

2015-05-08 Thread Tim Flink
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'

-
Reason for outage
-

There's a pending security update for the database used by Taskotron
and everything using that database host needs to be stopped while it is
being updated.

The outage will be very short and any jobs which would have been
scheduled during the outage will be run once the outage is complete.

-
Affected Services
-

Taskotron

---
Unaffected Services
---

Ask Fedora - ​​http://ask.fedoraproject.org/

Badges - ​​https://badges.fedoraproject.org/

BFO - ​​http://boot.fedoraproject.org/

Blockerbugs - ​​https://qa.fedoraproject.org/blockerbugs/

Bodhi - ​​https://admin.fedoraproject.org/updates/

Buildsystem - ​​http://koji.fedoraproject.org/

GIT / Source Control - pkgs.fedoraproject.org

Darkserver - ​​https://darkserver.fedoraproject.org/

DNS - ns-sb01.fedoraproject.org, ns02.fedoraproject.org,
ns04.fedoraproject.org, ns05.fedoraproject.org

Docs - ​​http://docs.fedoraproject.org/

Elections - ​​https://admin.fedoraproject.org/voting

Email system

Fedmsg busmon - ​​http://apps.fedoraproject.org/busmon

Fedora Account System - ​​https://admin.fedoraproject.org/accounts/

Fedora Community - ​​https://admin.fedoraproject.org/community/

Fedora Calendar - ​​https://apps.fedoraproject.org/calendar/

Fedora Hosted - ​​https://fedorahosted.org/

Fedora OpenID - ​​https://id.fedoraproject.org/

Fedora People - ​​http://fedorapeople.org/

Main Website - ​​http://fedoraproject.org/

Mirror List - ​​https://mirrors.fedoraproject.org/

Mirror Manager - ​​https://admin.fedoraproject.org/mirrormanager/

Package Database - ​​https://admin.fedoraproject.org/pkgdb/

Secondary Architectures

Spins - ​​http://spins.fedoraproject.org/

Start - ​​http://start.fedoraproject.org/

Torrent - ​​http://torrent.fedoraproject.org/

Wiki - ​​http://fedoraproject.org/wiki/


pgpHPBEd9izFD.pgp
Description: OpenPGP digital signature
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce-- 
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: Review or swap for burp - network backup

2015-05-08 Thread Adam Williamson
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
> > for lists of good and bad licenses.  AGPLv3 is on the list of good
> > licenses.
> > 
> > HTH.  Regards,
> yes i know but that page seem not updated ...

It is actively maintained. It just doesn't need to change much. It's
very unlikely an existing license which had previously been checked
would suddenly be found to be incompatible with Fedora's policies,
anyway - the page would only likely need a wholesale update if
Fedora's rules changed.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Introduction

2015-05-08 Thread Aditya Prakash
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, Glittergallery will be the web app which will help
designers to collaborate. I will be working on its commenting system,
integration of sparkleshare  and design-with-git
, improvements on its
project's page etc.
My summer vacation is long and I was hoping I could be involved with more
fedora projects. I was really interested in ongoing redesign of fedora-spins
 website, however I can't find its
repository, all I found was its ticket
.
I know C, C++, Python, Ruby and may be a bit of JAVA too. I would be really
grateful if someone can point me to fedora projects which can be a good
place to start for me and whose maintainers would be willing to deal with
noobs.

Thank You!
-- 
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: GCC 5 compatibility problems: GCC 4.10?

2015-05-08 Thread Rex Dieter
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 mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: GCC 5 compatibility problems: GCC 4.10?

2015-05-08 Thread Rex Dieter
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?

-- Rex

-- 
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: GCC 5 compatibility problems: GCC 4.10?

2015-05-08 Thread M. Edward (Ed) Borasky
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 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 mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct



-- 
OSJourno: Robust Power Tools for Digital Journalists
http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists

Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct