Re: Investigation of the F23 mass rebuild

2015-07-06 Thread Moez Roy 
On Thu, Jul 2, 2015 at 7:49 AM, Adam Jackson  wrote:
>
> Since the change was
> done by changing the rpm build macros, I think we can conclude that the
> build macros aren't being applied. Granted, packages can disable the
> hardened build macros, but the packages I've called out above aren't
> trying to disable them, or at least not doing so with %undefine.
>
>...
> - ajax

The problem is that some packages just look at the CFLAGS & CXXFLAGS.
They ignore the LDFLAGS.

The rpm build macros says to link with -pie and to add -z now in the LDFLAGS.

If you were to move those to the CFLAGS section the remaining packages
should get hardened.

As an example, this was the situation for Firefox:
http://pkgs.fedoraproject.org/cgit/firefox.git/commit/?id=ded1820a4f7f445b440a40a0e584bf3038307066

---

Then we come to the part where it says if it is not shared only then
add -pie. Is that really required? You can link shared libraries with
-pie http://sourceware.org/ml/binutils/2009-10/msg00088.html

So in another scenario, for example the LDFLAGS of the tracker.spec
had -fPIC so it did not get linked with -pie even though it is an
executable that runs at startup.

The point I am trying to get at is that if you do decide to move -pie
to the CFLAGS section please consider removing the !shared
requirement.

And if you do decide to move -Wl,-z,now to the CFLAGS please consider
adding a rule if it is not -Wl,-z,lazy. Probably something like this:
%{!-Wl,-z,lazy:-Wl,-z,now}

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

rawhide report: 20150706 changes

2015-07-06 Thread Fedora Rawhide Report 
Compose started at Mon Jul  6 05:15:04 UTC 2015
Broken deps for i386
--
[airsched]
airsched-1.00.0-12.fc23.i686 requires libzmq.so.4
[apache-scout]
apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws)
apache-scout-1.2.6-11.fc21.noarch requires 
mvn(org.apache.juddi:juddi-client)
[aws]
aws-tools-2015-2.fc23.i686 requires libaws_ssl.so
[bluetile]
bluetile-0.6-28.fc23.i686 requires 
ghc(gio-0.13.0.4-589ef11228222f8fdb72e24c64ce9d0a)
[bustle]
bustle-0.4.8-3.fc23.i686 requires libHSsetlocale-1.0.0.1-ghc7.8.4.so
bustle-0.4.8-3.fc23.i686 requires 
ghc(setlocale-1.0.0.1-5b5a3b6eb589586826a90a4c287ca0e0)
bustle-0.4.8-3.fc23.i686 requires 
ghc(hgettext-0.1.30-1fb42473ca2585938d9fc2bded6890b2)
bustle-0.4.8-3.fc23.i686 requires 
ghc(gio-0.13.0.4-589ef11228222f8fdb72e24c64ce9d0a)
[clearsilver]
perl-clearsilver-0.10.5-29.fc22.i686 requires 
perl(:MODULE_COMPAT_5.20.1)
perl-clearsilver-0.10.5-29.fc22.i686 requires libperl.so.5.20
[gammaray]
gammaray-qt5-2.2.1-10.fc23.i686 requires qt5-qtbase(x86-32) = 0:5.4.2
[ghc-gtk]
ghc-gtk-0.13.4-1.fc22.i686 requires 
ghc(gio-0.13.0.4-589ef11228222f8fdb72e24c64ce9d0a)
ghc-gtk-devel-0.13.4-1.fc22.i686 requires 
ghc-devel(gio-0.13.0.4-589ef11228222f8fdb72e24c64ce9d0a)
[ghc-hjsmin]
ghc-hjsmin-0.1.4.7-7.fc23.i686 requires 
ghc(language-javascript-0.5.13-0b8335d6a2507ee73f3b41c61a1ea2bf)
ghc-hjsmin-devel-0.1.4.7-7.fc23.i686 requires 
ghc-devel(language-javascript-0.5.13-0b8335d6a2507ee73f3b41c61a1ea2bf)
[golang-github-samalba-dockerclient]
golang-github-samalba-dockerclient-devel-0-0.1.gitc37a52f.fc23.noarch 
requires golang(github.com/docker/docker/utils)
golang-github-samalba-dockerclient-devel-0-0.1.gitc37a52f.fc23.noarch 
requires golang(github.com/docker/docker/pkg/timeutils)
golang-github-samalba-dockerclient-devel-0-0.1.gitc37a52f.fc23.noarch 
requires golang(github.com/docker/docker/pkg/stdcopy)
golang-github-samalba-dockerclient-devel-0-0.1.gitc37a52f.fc23.noarch 
requires golang(github.com/docker/docker/pkg/jsonlog)
[hadoop]
hadoop-common-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-servlet)
hadoop-common-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hadoop-common-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-json)
hadoop-common-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-core)
hadoop-hdfs-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hadoop-hdfs-2.4.1-8.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hadoop-mapreduce-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hadoop-mapreduce-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey.contribs:jersey-guice)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-servlet)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-json)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-core)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-client)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey.contribs:jersey-guice)
hadoop-yarn-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hadoop-yarn-2.4.1-8.fc22.noarch requires mvn(com.sun.jersey:jersey-json)
hadoop-yarn-2.4.1-8.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hadoop-yarn-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-client)
hadoop-yarn-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey.contribs:jersey-guice)
[hbase]
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server)
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json)
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-json)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-core)
[julia]
julia-0.3.7-2.fc23.i686 requires libspqr.so.1
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
[klavaro]
klavaro-3.01-0.pre1.1.fc23.1.i686 requires libgtkdataboks.so.0
[ldns]
perl-ldns-1.6.17-14.fc23.i686 requires perl(:MODULE_COMPAT_5.20.2)
perl-ldns-1.6.17-14.fc23.i686 requires libperl.so.5.20
[leksah-server]
leksah-server-0.14.3.1-2.fc23.i686 requires 
ghc(gio-0.13.0.4-589ef11228222f8fdb72e24c64ce9d0a)
[matreshka]
matreshka-servlet-devel-0.7.0-2.fc23.i686 requires 
matreshka-servlet-lib{?_isa} = 0:0.7.0-2.fc23
matres

Re: DisabledRepos and Software Center

2015-07-06 Thread Rex Dieter 
Miroslav Suchý wrote:

> I have question about
>   https://fedoraproject.org/wiki/Changes/DisabledRepoSupport
> 
> We (as Copr developers) are thinking about one RFE. We would like to
> create package which would contains .repo files and gpg keys for every
> Copr project. All of them with
>   enabled=0
>   enabled_metadata=1
> 
> But I wonder what would be user experience?

Be careful, enabling metadata for all copr's could yield a bad experience, 
since there is no QA (e.g. some coprs

For example, Workstation WG has tentative plans to use enabled_metadata=1 
only for a select reviewed list of coprs, that also comply with:

Any .repo files for Coprs that are installed by default in Fedora 
Workstation with enabled_metadata=1 should not point to Coprs that contain 
packages provided by Fedora, unless that repository contains only leaf 
packages.

(The mention of leaf packages was added to minimize risk of broken 
dependancies)

-- 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: DisabledRepos and Software Center

2015-07-06 Thread Rex Dieter 
Rex Dieter wrote:

> since there is no QA (e.g. some copr

Sorry for the half-thought here, meant to explicitly mention that some coprs 
or good (high-quality, well-maintained, etc...), while others are... less 
so.

-- 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: Investigation of the F23 mass rebuild

2015-07-06 Thread Adam Jackson 
On Thu, 2015-07-02 at 21:12 +0200, Till Maas wrote:
> Thank you for this great analysis. Do you still have the executable
> files and can run checksec on them and publish the output somewhere?

You got it:

https://ajax.fedorapeople.org/f23-checksec-scan

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

[POC-change] Fedora packages point of contact updates

2015-07-06 Thread nobody 
Change in package status over the last 168 hours


1 packages were orphaned

perl-qpid [f21, f20] was orphaned by irina
 Perl bindings for the Qpid messaging framework
 https://admin.fedoraproject.org/pkgdb/package/perl-qpid

1 packages were retired

hamcrest12 [master] was retired by msimacek
 Library of matchers for building test expressions
 https://admin.fedoraproject.org/pkgdb/package/hamcrest12

14 packages unorphaned
--
amqp [el6] was unorphaned by irina
 The AMQP specification
 https://admin.fedoraproject.org/pkgdb/package/amqp
compat-qpid-cpp [f22, f21, f20, master, el6, epel7] was unorphaned by irina
 Libraries for Qpid C++ client applications
 https://admin.fedoraproject.org/pkgdb/package/compat-qpid-cpp
garmintools [master] was unorphaned by limb
 Communication tools for Garmin devices
 https://admin.fedoraproject.org/pkgdb/package/garmintools
libdnet [f22, f21, f20, master] was unorphaned by robert
 Simple portable interface to lowlevel networking routines
 https://admin.fedoraproject.org/pkgdb/package/libdnet
netty31 [f22, master] was unorphaned by mbooth
 An asynchronous event-driven network application framework and tools for 
Java
 https://admin.fedoraproject.org/pkgdb/package/netty31
pymongo [el6] was unorphaned by orion
 Python driver for MongoDB
 https://admin.fedoraproject.org/pkgdb/package/pymongo
python-pyngus [f20] was unorphaned by irina
 Callback API implemented over Proton
 https://admin.fedoraproject.org/pkgdb/package/python-pyngus
qpid-cpp [f22, f21, f20, master, epel7] was unorphaned by irina
 Libraries for Qpid C++ client applications
 https://admin.fedoraproject.org/pkgdb/package/qpid-cpp
qpid-dispatch [f22, f21, f20, master, el6, epel7, el5] was unorphaned by irina
 Dispatch router for Qpid
 https://admin.fedoraproject.org/pkgdb/package/qpid-dispatch
qpid-proton [f22, f21, f20, master, el6, epel7, el5] was unorphaned by irina
 A high performance, lightweight messaging library
 https://admin.fedoraproject.org/pkgdb/package/qpid-proton
qpid-proton-java [el6, epel7] was unorphaned by irina
 Java libraries for Qpid Proton
 https://admin.fedoraproject.org/pkgdb/package/qpid-proton-java
qpid-qmf [f22, f21, f20, master, epel7] was unorphaned by irina
 The QPID Management Framework
 https://admin.fedoraproject.org/pkgdb/package/qpid-qmf
rubygem-qpid_messaging [f22, f21, f20, master, epel7] was unorphaned by irina
 Ruby bindings for the Qpid messaging framework
 https://admin.fedoraproject.org/pkgdb/package/rubygem-qpid_messaging
rubygem-qpid_proton [f22, f21, f20, master, el6, epel7] was unorphaned by irina
 Ruby language bindings for the Qpid Proton messaging framework
 https://admin.fedoraproject.org/pkgdb/package/rubygem-qpid_proton

0 packages were unretired


37 packages were given
-
php-horde-Horde-Alarm [f22, f21, f20, master, el6, epel7] was given by nb to 
remi
 Horde Alarm Libraries
 https://admin.fedoraproject.org/pkgdb/package/php-horde-Horde-Alarm
php-horde-Horde-Argv [f22, f21, f20, master, el6, epel7] was given by nb to remi
 Horde command-line argument parsing package
 https://admin.fedoraproject.org/pkgdb/package/php-horde-Horde-Argv
php-horde-Horde-Auth [f22, f21, f20, master, el6, epel7] was given by nb to remi
 Horde Authentication API
 https://admin.fedoraproject.org/pkgdb/package/php-horde-Horde-Auth
php-horde-Horde-Autoloader [f22, f21, f20, master, el6, epel7] was given by nb 
to remi
 Horde Autoloader
 https://admin.fedoraproject.org/pkgdb/package/php-horde-Horde-Autoloader
php-horde-Horde-Browser [f22, f21, f20, master, el6, epel7] was given by nb to 
remi
 Horde Browser API
 https://admin.fedoraproject.org/pkgdb/package/php-horde-Horde-Browser
php-horde-Horde-Cache [f22, f21, f20, master, el6, epel7] was given by nb to 
remi
 Horde Caching API
 https://admin.fedoraproject.org/pkgdb/package/php-horde-Horde-Cache
php-horde-Horde-Cli [f22, f21, f20, master, el6, epel7] was given by nb to remi
 Horde Command Line Interface API
 https://admin.fedoraproject.org/pkgdb/package/php-horde-Horde-Cli
php-horde-Horde-Compress [f22, f21, f20, master, el6, epel7] was given by nb to 
remi
 Horde Compression API
 https://admin.fedoraproject.org/pkgdb/package/php-horde-Horde-Compress
php-horde-Horde-Constraint [f22, f21, f20, master, el6, epel7] was given by nb 
to remi
 Horde Constraint library
 https://admin.fedoraproject.org/pkgdb/package/php-horde-Horde-Constraint
php-horde-Horde-Controller [f22, f21, f20, master, el6, epel7] was given by nb 
to remi
 Horde Controller libraries
 https://admin.fedoraproject.org/pkgdb/package/php-horde-Horde-Controller
php-horde-Horde-Data [f22, f21, f20, master, el6, epel

Re: Docker base image naming for non-x86_64

2015-07-06 Thread Pradipta Kumar Banerjee 
On 06/02/2015 08:32 PM, Adam Miller wrote:
> Hello all,
> There was recently a thread on the Fedora ARM mailing list[0]
> about getting a Fedora ARM image into the official Docker Hub. That
> discussion lead down the trail of how to best handle the naming for
> all of this.
> 
> The current questions are either using Fedora's namespace and just
> making a new image (using Fedora ARM as an example), this would be the
> "FROM" line for a Dockerfile
> 
> FROM fedora/armhfp
> 
> Which would then contain all the standard tags for latest, rawhide, f22, etc.
> 
> Or alternatively, have each architecture maintain their own namespace
> within the Hub which would look a little more like:
> 
> FROM fedora-arm
> 
> I'm personally a fan of the first option because it keeps things under
> the Fedora umbrella and also allows for flexibility of aarch64, POWER,
> etc as Docker supports more architectures. However the one thing I see
> there that could be problematic is the possibility for users to be
> confused if they don't search on the Docker Hub webUI and see the
> associated documentation highlighting that the base image is for a
> different architecture but instead just search from the docker command
> line and end up with an image that won't run.
> 
> Looking forward to feedback on the topic.

Is there any agreement on the naming scheme ?

> 
> Thanks,
> -AdamM
> 
> [0] - https://lists.fedoraproject.org/pipermail/arm/2015-June/009526.html
> 


-- 
Regards,
Pradipta

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

Planned Outage: fedorapeople.org - 2015-07-08 21:00 UTC

2015-07-06 Thread Kevin Fenzi 
Planned Outage: fedorapeople.org - 2015-07-08 21:00 UTC

 There will be an outage starting at 2015-07-08 21:00 UTC, which will
 last approximately 3 hours.

 To convert UTC to your local time, take a look at
 http://fedoraproject.org/wiki/Infrastructure/UTCHowto
 or run:

 date -d '2015-07-08 21:00 UTC'

 Reason for outage:

 We are migrating fedorapeople to a new instance. This new instance
 will be RHEL7 and managed in our ansible infrastructure. All users and
 data will be retained.

 Affected Services:

 Fedora People - http://fedorapeople.org/

 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/

 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/

 QA Services

 Secondary Architectures

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

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

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

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

 Contact Information:

 Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/4810

 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
 comments to the ticket for this outage above.


pgpw0kp0Rkpsh.pgp
Description: OpenPGP digital signature
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-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

Firefox 39 and "restore session"

2015-07-06 Thread Reindl Harald 

* Mo Jul 06 2015 Martin Stransky  - 39.0-7
- Added a fix for rhbz#1240259 - Firefox 39 does not open
  home page but "restore session"

well, does anobdy test things or are builds just fired out?
no change in that context. don't get me wrong but i would except 
local tests before a build hits koji at all




signature.asc
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

Re: Firefox 39 and "restore session"

2015-07-06 Thread Kevin Fenzi 
On Mon, 6 Jul 2015 22:00:41 +0200
Reindl Harald  wrote:

> * Mo Jul 06 2015 Martin Stransky  - 39.0-7
> - Added a fix for rhbz#1240259 - Firefox 39 does not open
>home page but "restore session"
> 
> well, does anobdy test things or are builds just fired out?
> no change in that context. don't get me wrong but i would except 
> local tests before a build hits koji at all

There may be any number of reasons a proposed fix for a bug doesn't
work for you. I'd indicate that in the bug report (as Remi already has
done) and work with them to find out what happened. 

kevin


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

Re: Firefox 39 and "restore session"

2015-07-06 Thread Reindl Harald 



Am 06.07.2015 um 22:13 schrieb Kevin Fenzi:

On Mon, 6 Jul 2015 22:00:41 +0200
Reindl Harald  wrote:


* Mo Jul 06 2015 Martin Stransky  - 39.0-7
- Added a fix for rhbz#1240259 - Firefox 39 does not open
home page but "restore session"

well, does anobdy test things or are builds just fired out?
no change in that context. don't get me wrong but i would except
local tests before a build hits koji at all


There may be any number of reasons a proposed fix for a bug doesn't
work for you. I'd indicate that in the bug report (as Remi already has
done) and work with them to find out what happened


well, if upstream FF39 with the sam eprofile as well as windows would 
not suffer from the same problem




signature.asc
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

octave 4.0.0

2015-07-06 Thread Orion Poplawski 
I'm going to be building octave 4.0.0 to Rawhide soon.  Everything that
requires it will need to be rebuilt.  I think this is:

csdp-6.1.1-9.fc23.src.rpm
lhapdf-5.9.1-9.fc23.src.rpm
NLopt-2.4.2-3.fc22.src.rpm
octave-audio-1.1.4-12.fc22.src.rpm
octave-communications-1.2.0-2.fc22.src.rpm
octave-control-2.6.6-1.fc22.src.rpm
octave-dicom-0.1.1-9.fc22.src.rpm
octave-general-1.3.4-1.fc22.src.rpm
octave-gsl-1.0.8-9.fc22.src.rpm
octave-image-2.2.2-1.fc22.src.rpm
octave-io-2.2.7-1.fc23.src.rpm
octave-miscellaneous-1.2.1-2.fc22.src.rpm
octave-ncarray-1.0.3-2.fc21.src.rpm
octave-netcdf-1.0.6-1.fc23.src.rpm
octave-nnet-0.1.13-7.fc21.src.rpm
octave-octcdf-1.1.7-3.fc22.src.rpm
octave-odepkg-0.8.4-3.fc22.src.rpm
octave-optim-1.4.0-2.fc22.src.rpm
octave-parallel-2.2.0-3.fc22.src.rpm
octave-quaternion-2.2.2-2.fc22.src.rpm
octave-signal-1.3.0-3.fc22.src.rpm
octave-specfun-1.1.0-9.fc22.src.rpm
octave-statistics-1.2.3-2.fc21.src.rpm
octave-struct-1.0.10-7.fc22.src.rpm
octave-symbolic-2.0.0-1.fc23.src.rpm
pfstools-1.8.5-20.fc23.src.rpm
plplot-5.10.0-17.fc22.src.rpm
qtoctave-0.10.1-17.fc22.src.rpm
shogun-3.2.0.1-0.33.git20141224.d71e19a.fc22.src.rpm
syntastic-3.5.0-1.fc22.src.rpm
toped-0.9.81-8.svn2211.fc22.src.rpm

I'll try to get this taken care of.

-- 
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: Firefox 39 and "restore session"

2015-07-06 Thread Kevin Fenzi 
On Mon, 6 Jul 2015 22:18:13 +0200
Reindl Harald  wrote:

> well, if upstream FF39 with the sam eprofile as well as windows would 
> not suffer from the same problem

Then it's something specific to the Fedora build. 

Upstream bundles things that the Fedora build unbundles, as well as
likely using different compile env and flags. 

Anyhow, not sure why this needs to be discussed here, the maintainer
is working on it in the indicated bug. 

kevin
 



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

Re: Docker base image naming for non-x86_64

2015-07-06 Thread Jon 
On Mon, Jul 6, 2015 at 12:27 PM, Pradipta Kumar Banerjee  wrote:

> On 06/02/2015 08:32 PM, Adam Miller wrote:
> > Hello all,
> > There was recently a thread on the Fedora ARM mailing list[0]
> > about getting a Fedora ARM image into the official Docker Hub. That
> > discussion lead down the trail of how to best handle the naming for
> > all of this.
> >
> > The current questions are either using Fedora's namespace and just
> > making a new image (using Fedora ARM as an example), this would be the
> > "FROM" line for a Dockerfile
> >
> > FROM fedora/armhfp
> >
> > Which would then contain all the standard tags for latest, rawhide, f22,
> etc.
> >
> > Or alternatively, have each architecture maintain their own namespace
> > within the Hub which would look a little more like:
> >
> > FROM fedora-arm
> >
> > I'm personally a fan of the first option because it keeps things under
> > the Fedora umbrella and also allows for flexibility of aarch64, POWER,
> > etc as Docker supports more architectures. However the one thing I see
> > there that could be problematic is the possibility for users to be
> > confused if they don't search on the Docker Hub webUI and see the
> > associated documentation highlighting that the base image is for a
> > different architecture but instead just search from the docker command
> > line and end up with an image that won't run.
> >
> > Looking forward to feedback on the topic.
>
> Is there any agreement on the naming scheme ?
>
>
The first form seems to have the most support.


> >
> > Thanks,
> > -AdamM
> >
> > [0] -
> https://lists.fedoraproject.org/pipermail/arm/2015-June/009526.html
> >
>
>
> --
> Regards,
> Pradipta
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>



-- 

-Jon Disnard
-- 
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: Docker base image naming for non-x86_64

2015-07-06 Thread Pradipta Kumar Banerjee 
On 07/07/2015 06:09 AM, Jon wrote:
> 
> 
> On Mon, Jul 6, 2015 at 12:27 PM, Pradipta Kumar Banerjee  > wrote:
> 
> On 06/02/2015 08:32 PM, Adam Miller wrote:
> > Hello all,
> > There was recently a thread on the Fedora ARM mailing list[0]
> > about getting a Fedora ARM image into the official Docker Hub. That
> > discussion lead down the trail of how to best handle the naming for
> > all of this.
> >
> > The current questions are either using Fedora's namespace and just
> > making a new image (using Fedora ARM as an example), this would be the
> > "FROM" line for a Dockerfile
> >
> > FROM fedora/armhfp
> >
> > Which would then contain all the standard tags for latest, rawhide, 
> f22, etc.
> >
> > Or alternatively, have each architecture maintain their own namespace
> > within the Hub which would look a little more like:
> >
> > FROM fedora-arm
> >
> > I'm personally a fan of the first option because it keeps things under
> > the Fedora umbrella and also allows for flexibility of aarch64, POWER,
> > etc as Docker supports more architectures. However the one thing I see
> > there that could be problematic is the possibility for users to be
> > confused if they don't search on the Docker Hub webUI and see the
> > associated documentation highlighting that the base image is for a
> > different architecture but instead just search from the docker command
> > line and end up with an image that won't run.
> >
> > Looking forward to feedback on the topic.
> 
> Is there any agreement on the naming scheme ?
> 
> 
> The first form seems to have the most support.
>  
Makes sense.. Should we also discuss this in the docker-dev mailing list as well
since this affects every official image in the docker hub ?

> 
> >
> > Thanks,
> > -AdamM
> >
> > [0] - 
> https://lists.fedoraproject.org/pipermail/arm/2015-June/009526.html
> >
> 
> 
> --
> Regards,
> Pradipta
> 
> --
> devel mailing list
> devel@lists.fedoraproject.org 
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> 
> 
> 
> 
> -- 
> 
> -Jon Disnard


-- 
Regards,
Pradipta

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