Re: Maybe it is time to move tools to Python 3.x?

[Marcin Juszkiewicz]

W dniu 03.12.2014 o 20:30, Matthew Miller pisze:
> On Wed, Dec 03, 2014 at 08:13:42PM +0100, Marcin Juszkiewicz wrote:
>> When I worked at Canonical there was a goal to move both internal and
>> public tools to Python 3.x version. IIRC started somewhere around 12.04
>> and today when you look at Ubuntu Touch you will not find Python 2.7
>> there. Similar with other tools.
>> Can it be done? Maybe not in a month but who knows - f22 cycle?
> 
> Take a look at
>  for some
> work in progress.

Thanks.


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

Schedule for Thursday's FPC Meeting (2014-12-04 17:00 UTC)

[James Antill]

 Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2014-12-04 17:00 UTC in #fedora-meeting-1 on
irc.freenode.net.

 Local time information (via. rktime):

2014-12-04 09:00 Thu US/Pacific PST
2014-12-04 12:00 Thu US/Eastern EST
2014-12-04 17:00 Thu UTC <-
2014-12-04 17:00 Thu Europe/London <-
2014-12-04 18:00 Thu Europe/Paris   CET
2014-12-04 18:00 Thu Europe/Berlin  CET
2014-12-04 22:30 Thu Asia/Calcutta  IST
--new day--
2014-12-05 01:00 Fri Asia/Singapore SGT
2014-12-05 01:00 Fri Asia/Hong_Kong HKT
2014-12-05 02:00 Fri Asia/Tokyo JST
2014-12-05 03:00 Fri Australia/Brisbane EST

 Links to all tickets below can be found at: 

https://fedorahosted.org/fpc/report/12

= Followups =

(needed policy, feature not accepted yet)
#topic #466 recommend Privatedevices and PrivateNetwork in systemd
guidelines
.fpc 466
https://fedorahosted.org/fpc/ticket/466

(needinfo, just package dep?)
#topic #468 Temporary modernizr packing exception for kimchi
.fpc 468
https://fedorahosted.org/fpc/ticket/468

= New business =

#topic #472 Minor modification bootstrap-related guidelines
.fpc 472
https://fedorahosted.org/fpc/ticket/472

#topic #473 explicit conflicts exception for fedora-productimg-*
packages (or other solution?)
.fpc 473
https://fedorahosted.org/fpc/ticket/473

= Open Floor = 

 For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at:

https://fedorahosted.org/fpc/report/12


 If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

karma and Bodhi elections

[Sérgio Basto]

Hi, 
https://admin.fedoraproject.org/updates/firefox-34.0-1.fc20,thunderbird-31.3.0-1.fc20
are already to be push to stable without passing to test repo .

But for what I see: "stable karma: 0" it shouldn't be pulled to stable
even with karma 4 .
I had an idea 
why not ? be possible, set in Bodhi request, the minimum time to be in
testing ?
for firefox minimum time could be 1 or 2 days, but not 0 :) 
and setting 0 .

Best regards,
-- 
Sérgio M. B.

-- 
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 21 Final Release Candidate 5 (RC5) Available Now!

[Adam Williamson]

NOTE: Signing of the RC5 checksums is not yet complete. To be sure we're
testing the right bits we should remember to check that the images we
test match the signed checksum files once they're available, and of
course you can carefully check the TLS certificate of the server when
downloading the images. fedup tests may require the --nogpgcheck
parameter until the signed .treeinfo file is available. releng will
update and close the trac ticket when signing is complete.

As per the Fedora 21 schedule [1], Fedora 21 Final Release Candidate 5
(RC5) is now available for testing.

The difference between RC5 and RC4 is that the changes to python-blivet
and pyparted that were introduced in RC1 to fix bug #1166598 have been
reverted, as they were found to cause more serious problems than they
fixed. As this change affects the installer, all installation validation
tests should be run again. Existing RC4 test results for
post-installation tests will be considered valid and transferred into
the RC5 result pages; from now on, please do all testing with RC5
images.

Please see the following pages for download links (including delta ISOs)
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

Ideally, all Alpha, Beta, and Final priority test cases for each of
these test pages [2] should 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 21 Final test compose (TC) and release candidate (RC)
https://fedorahosted.org/rel-eng/ticket/6031

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

[1] http://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
[3] https://fedoraproject.org/wiki/Fedora_21_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

Nonresponsive maintainer (invalid email address): Chris Lockfort (clock...@redhat.com)

[David Shea]

Through some series of accidents, the python-pyudev package in Fedora is 
assigned to clock...@redhat.com. This account has been closed since at 
least early 2013. The email address isn't "invalid" exactly in that 
emails won't bounce, but it is a black hole from which no responses will 
return, and as such I am skipping to the later parts of the 
nonresponsive maintainer process.


So: does anyone know how to contact Chris Lockfort, or if he is still 
interested in maintaining python-pyudev? If he is not, I would like to 
take over the package.


For the documentation of unresponsiveness, here's all the bugs, ain't 
none responded to: 
https://bugzilla.redhat.com/buglist.cgi?component=python-pyudev&list_id=3060872&product=Fedora 



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

Heads up RabbitMQ users!

[Peter Lemenkov]

Hello All!

I've removed SSLv3 from the list of supported crypto protocols in
Erlang. This should apply only for cases where application doesn't
define explicitly a list of supported protocols. E.g. if your package
explicitly enables SSLv3 then it will be available, otherwise - won't
be. The packages are available in testing repositories:

- erlang-17.3.4-3.fc21
- erlang-R16B-03.10.fc20
- erlang-R16B-03.10.el7

I'm pretty sure this won't break things which weren't broken already.
However I've heard a bizarre report about RabbitMQ failure when using
Erlang with SSlv3 disabled against some 3rd party crypto tool:

* https://groups.google.com/forum/#!topic/rabbitmq-users/Hs5J9UauJz8

I would be thankful for the testing of RabitMQ against these new Erlang builds.

My next goal is to audit CouchDB, Ejabberd, RabbitMQ packages and
remove any SSLv3 traces from them (or even disable explicitly if
possible/necessary). Just fyi.
-- 
With best regards, Peter Lemenkov.
-- 
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: PVM: Retire or not to retire?

[M. Edward (Ed) Borasky]

PVM in particular and high-performance computing in general are
severely broken in most Linux distros and applications. First of all,
there's licensing - the GPU folk, especially NVidia, aren't willing to
back down as long as their intellectual property strategies are making
them rich. For example, I took a stab at enabling OpenCL on Fedora 21
after seeing it in the release notes and ran into a bunch of bugs and
piss-poor / non-existent documentation.

Second, most of this stuff is "clever hacks" by scientists who aren't
software engineers. I'm somewhat unique - I've spent a big chunk of my
life in scientific applications programming / software engineering,
but most scientists have to be taught the basics - the shell, version
control, etc. - by the likes of the Software Carpentry project.

Personally, I say "go ahead and kick PVM out of Fedora." IMHO a distro
should provide the kernel, compilers and interpreters, installers,
desktops, filesystems, virtualization, etc. and end-user applications
/ language communities should distribute stuff that works on any
distro. Nobody's going to be "the best distro for" bioinformatics,
audio engineering, robotics, web design, etc. - that's not the way
open source works.

On Wed, Dec 3, 2014 at 10:39 AM, Richard Shaw  wrote:
> Is anyone going to scream if PVM get's retired?
>
> Upstream was last updated in 2009 as far as I can tell...
> It's packaging is atrocious...
> The source is copied to the buildroot and compiled in place...
> It violates the packaging guidelines in multiple bad ways...
> Also see: https://bugzilla.redhat.com/show_bug.cgi?id=1029469
>
> If someone wants/needs it then they need to step up and fix the open bugs
> and at least make an attempt at getting ti closer aligned to the packaging
> guidelines.
>
> Thanks,
> Richard
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct



-- 
Twitter: http://twitter.com/znmeb; OSJourno: Robust Power Tools for
Digital Journalists https://osjourno.com

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

Re: Maybe it is time to move tools to Python 3.x?

[Matthew Miller]

On Wed, Dec 03, 2014 at 08:13:42PM +0100, Marcin Juszkiewicz wrote:
> When I worked at Canonical there was a goal to move both internal and
> public tools to Python 3.x version. IIRC started somewhere around 12.04
> and today when you look at Ubuntu Touch you will not find Python 2.7
> there. Similar with other tools.
> Can it be done? Maybe not in a month but who knows - f22 cycle?

Take a look at
 for some
work in progress.

-- 
Matthew Miller

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

Maybe it is time to move tools to Python 3.x?

[Marcin Juszkiewicz]

Hi

Today I tried to use few Fedora tools and was greet with nice tracebacks
when gave wrong arguments or something other happened. But that's not
why I am writing.

What surprised me more is that Fedora tools are still Python 2.x based.
Someone may write "so what?" but I think that using legacy version
should have some end date. 6 years passed since Python 3.0 release...

When I worked at Canonical there was a goal to move both internal and
public tools to Python 3.x version. IIRC started somewhere around 12.04
and today when you look at Ubuntu Touch you will not find Python 2.7
there. Similar with other tools.

Can it be done? Maybe not in a month but who knows - f22 cycle?
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Summary/Minutes from today's FESCo meeting (2014-12-03 at 18UTC)

[Kevin Fenzi]

===
#fedora-meeting: FESCO (2014-12-03)
===


Meeting started by nirik at 18:00:13 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-12-03/fesco.2014-12-03-18.00.log.html
.



Meeting summary
---
* init process  (nirik, 18:00:13)

* ticket #1349  Fedora 22 scheduling strategy (and beyond)  (nirik,
  18:03:09)
  * LINK: https://fedoraproject.org/wiki/Fedora_21_Retrospective
(nirik, 18:13:42)
  * will decide final schedule based on feedback from f21 release cycle
(nirik, 18:15:49)
  * LINK: https://fedoraproject.org/wiki/Fedora_21_Retrospective
(nirik, 18:16:01)
  * LINK: https://fedorahosted.org/fesco/ticket/1349#comment:24 makes
sense to me  (kalev, 18:16:02)
  * AGREED: jreznik_2nd will send to devel-announce: retrospective wiki
page, changes must be testable by early feb 2015, and we are
targeting a may release. Specific dates to come. (+6,0,0)  (nirik,
18:54:22)

* ticket #1369 packages should disable internal crash handlers and
  depend on ABRT  (nirik, 18:54:49)
  * AGREED: Let projects continue to do as they see fit (+6,0,0)
(nirik, 19:05:42)

* next weeks chair  (nirik, 19:05:51)
  * thozza to chair next week.  (nirik, 19:06:49)
  * we will not meet on the 24th or the 31st.  (nirik, 19:08:25)

* Open Floor  (nirik, 19:08:29)

Meeting ended at 19:11:37 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* nirik (88)
* mattdm (59)
* jwb (57)
* sgallagh (44)
* jreznik_2nd (36)
* kalev (27)
* thozza (13)
* mitr (9)
* t8m (9)
* adamw (8)
* zodbot (6)
* otaylor (5)
* tflink (4)
* mclasen (3)
* stickster (2)
* mmaslano (0)
* dgilmore (0)

--
18:00:13  #startmeeting FESCO (2014-12-03)
18:00:13  Meeting started Wed Dec  3 18:00:13 2014 UTC.  The chair is 
nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:13  Useful Commands: #action #agreed #halp #info #idea #link 
#topic.
18:00:13  #meetingname fesco
18:00:13  #chair dgilmore jwb kalev mattdm mitr mmaslano nirik sgallagh 
stickster t8m thozza
18:00:13  #topic init process
18:00:13  The meeting name has been set to 'fesco'
18:00:13  Current chairs: dgilmore jwb kalev mattdm mitr mmaslano nirik 
sgallagh stickster t8m thozza
18:00:52  present
18:00:52 * mattdm is here
18:01:00  hi
18:01:04  Hello
18:01:55  so, I guess we have quorum today at least. ;)
18:02:04  :)
18:02:12  I'm here
18:02:20  jreznik_2nd: you around?
18:02:36  hi all
18:03:06  lets go ahead and get started...
18:03:09  #topic ticket #1349Fedora 22 scheduling strategy (and 
beyond)
18:03:09  .fesco 1349
18:03:10  nirik: #1349 (Fedora 22 scheduling strategy (and beyond)) – 
FESCo - https://fedorahosted.org/fesco/ticket/1349
18:03:16 * jreznik_2nd is here but give me two minutes
18:03:19  any further thoughts or discussion on this?
18:03:22  sure...
18:03:30  hi all
18:04:19  So, we're definitely running into some schedule and process 
related conflicts with anaconda team and qa
18:04:33  I don't think we can or should solve that right now
18:04:47  mattdm: yeah, my thoughts
18:04:55  right, but perhaps we could/should wait on this ticket until 
after we do a retrospective for f21?
18:04:59  but we need to take some time to understand what's going on 
there and make some (possibly big) adjustments to fix.
18:05:07  nirik: yes.
18:05:10  but if we want may release, we have a real pressure now 
on having changes done asap
18:05:42  As I've been mentioning all over the place, I'd like to 
host a FAD on revamping some of the process
18:05:54  sgallagh: face to face fad or vfad?
18:06:08  (Things like running blocker testing earlier, tightening up 
the Final Freeze, etc.)
18:06:17  mattdm: Probably a vFAD
18:06:44  sgallagh: good because I don't think we have much money left 
for real ones, which would put it to march or later, which is too late for f22
18:06:58  we could start collecting things now? ie, stick up a wiki page 
with "problems you saw" and "good things you saw" ?
18:06:59  well, I didn't see any big issues this release if you 
take a look on all what was done
18:07:08  nirik: sounds good.
18:07:19  and 'possible solutions/ideas' ?
18:07:25  jreznik_2nd: Except for the last two weeks, when things got 
a bit hairy.
18:07:32  nirik: Probably an excellent idea
18:08:00  would anyone like to make such a thing? I could, but might not 
get to it for a bit as I am traveling later today and will be away/busy at a 
FAD. ;)
18:08:03  I think the final release has been exceptionally smooth 
actually, mostly thanks to the additional freeze week I guess
18:08:18  I also thing we should position f22 as a ".1" release (even 
if we're not changing the numbering)
18:08:29  well, until the last week, then it's back to hero testing 
again. ;(
18:09:01  kalev: we had a few issues with anaconda but it was more 
abo

PVM: Retire or not to retire?

[Richard Shaw]

Is anyone going to scream if PVM get's retired?

Upstream was last updated in 2009 as far as I can tell...
It's packaging is atrocious...
The source is copied to the buildroot and compiled in place...
It violates the packaging guidelines in multiple bad ways...
Also see: https://bugzilla.redhat.com/show_bug.cgi?id=1029469

If someone wants/needs it then they need to step up and fix the open bugs
and at least make an attempt at getting ti closer aligned to the packaging
guidelines.

Thanks,
Richard
-- 
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: Meeting minutes from Env-and-Stacks WG meeting (2014-12-03)

[Bohuslav Kabrda]

> Action Items
> 
> * bkabrda will ask java guys to create a wiki page summarizing the
>approaches we thought of and why we think it's not worth the effort +
>post the link to WG ML once it's ready

Here it is: https://fedoraproject.org/wiki/User:Mizdebsk/FedoraMavenRepository

Slavek
-- 
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: How many users does Fedora have?

[Pádraig Brady]

On 02/12/14 18:12, Stephen John Smoogen wrote:
> 
> 
> On 2 December 2014 at 09:22, Matthew Miller  > wrote:
> 
> On Tue, Dec 02, 2014 at 05:15:38PM +0100, jfm...@free.fr 
>  wrote:
> > Now it seems Fedora's downloads have been steadily going downwards
> > and it is highly improbable that is due to a spectacular increase of
> > number of people setting local mirrors.
> 
> Smooge is working on some updated statistics, and from what I've seen,
> it's mostly flat, but not actually steadily downwards. More on the
> other things later. :)
> 
> 
> 
> Temporary URL for picture of things from 2007 til last month:
> 
> https://smooge.fedorapeople.org/stats-2014/
> 
> I am hoping to have a permanent url and updated set by next month.

Good info thanks.
I think it would be worth splitting the Fedora and EPEL graphs.
(I presume that's why the second graph goes to 800K while the first
only goes to 200K).

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

Meeting minutes from Env-and-Stacks WG meeting (2014-12-03)

[Honza Horak]

#fedora-meeting: Env and Stacks (2014-12-03)



Meeting started by hhorak at 12:02:01 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2014-12-03/env-and-stacks.2014-12-03-12.02.log.html
.



Meeting summary
---
* init process  (hhorak, 12:02:39)

* Follow-ups  (hhorak, 12:04:26)
  * LINK:

https://fedoraproject.org/wiki/Env_and_Stacks/Projects/LanguageSpecificRepositories
(ncoghlan, 12:06:03)
  * LINK: https://github.com/pulp/pulp_python   (ncoghlan, 12:10:50)
  * the Java guys has reached a conclusion that downstream maven
repository wouldn't have significant benefit, so I'd say that Python
is alone as a pilot right now  (hhorak, 12:14:20)
  * Python wheel's currently have a problem where all prebuild Linux
binaries get tagged "linux_https://mail.python.org/pipermail/distutils-sig/2014-November/025297.html
(hhorak, 12:24:08)
  * LINK:

https://mail.python.org/pipermail/distutils-sig/2014-December/025337.html
(hhorak, 12:24:15)
  * we should make some marketing for the 'upstream repository' ideas,
so we get feedback from broader community, but not sooner than the
devpi instance is out and we have an example of using that in a
Dockerfile to install a Python app  (hhorak, 12:31:13)
  * LINK:

https://fedoraproject.org/wiki/Env_and_Stacks/Projects/UserLevelPackageManagement
(ncoghlan, 12:33:38)
  * ACTION: ncoghlan: add the "trusted curator" rationale to
LanguageSpecificRepositories page  (ncoghlan, 12:51:52)
  * ACTION: bkabrda will ask java guys to create a wiki page summarizing
the approaches we thought of and why we think it's not worth the
effort + post the link to WG ML once it's ready  (hhorak, 12:56:37)

* SCLs and CentOS  (hhorak, 12:59:43)
  * Software collections development is now slowly moving to CentOS,
since that is nice open platform where software collections make
much more sense.  (hhorak, 13:01:22)
  * So, what is happening is that CentOS SIG was established that would
help to develop some better ecosystem around SCLs where more people
can actively participate.  (hhorak, 13:01:49)
  * LINK: http://wiki.centos.org/SpecialInterestGroup/SCLo   (hhorak,
13:01:53)
  * better said centos seems to like scls more than fedora  (hhorak,
13:07:29)
  * there are still valid use cases for SCLs in Fedora  (hhorak,
13:23:08)
  * SCLs as a technology should be implemented in Fedora first,
irrelevant of its consumption of the content  (hhorak, 13:27:41)

* Chairman for next meeting  (hhorak, 13:39:01)

Meeting ended at 13:44:03 UTC.




Action Items

* ncoghlan: add the "trusted curator" rationale to
  LanguageSpecificRepositories page
* bkabrda will ask java guys to create a wiki page summarizing the
  approaches we thought of and why we think it's not worth the effort +
  post the link to WG ML once it's ready




Action Items, by person
---
* bkabrda
  * bkabrda will ask java guys to create a wiki page summarizing the
approaches we thought of and why we think it's not worth the effort
+ post the link to WG ML once it's ready
* ncoghlan
  * ncoghlan: add the "trusted curator" rationale to
LanguageSpecificRepositories page
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* bkabrda (62)
* hhorak (62)
* ncoghlan (61)
* langdon (43)
* juhp (15)
* bochecha (14)
* Southern_Gentlem (5)
* zodbot (4)
* RemiFedora (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
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: 20141203 changes

[Fedora Rawhide Report]

Compose started at Wed Dec  3 05:15:02 UTC 2014
Broken deps for i386
--
[3Depict]
3Depict-0.0.16-3.fc22.i686 requires libmgl.so.7.2.0
[Sprog]
Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
[cab]
cab-0.1.9-12.fc22.i686 requires cabal-dev
[cinepaint]
cinepaint-libs-1.4-7.fc22.i686 requires libImath-2_1.so.11
cinepaint-libs-1.4-7.fc22.i686 requires libIlmThread-2_1.so.11
cinepaint-libs-1.4-7.fc22.i686 requires libIlmImf-Imf_2_1.so.21
cinepaint-libs-1.4-7.fc22.i686 requires libIexMath-2_1.so.11
cinepaint-libs-1.4-7.fc22.i686 requires libIex-2_1.so.11
cinepaint-libs-1.4-7.fc22.i686 requires libHalf.so.11
[dnssec-check]
dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14
dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14
[gegl]
gegl-0.2.0-20.fc22.i686 requires libImath-2_1.so.11
gegl-0.2.0-20.fc22.i686 requires libIlmThread-2_1.so.11
gegl-0.2.0-20.fc22.i686 requires libIlmImf-Imf_2_1.so.21
gegl-0.2.0-20.fc22.i686 requires libIexMath-2_1.so.11
gegl-0.2.0-20.fc22.i686 requires libIex-2_1.so.11
gegl-0.2.0-20.fc22.i686 requires libHalf.so.11
[glances]
glances-2.1.2-2.fc22.noarch requires python-psutil >= 0:2.0.0
[kde-plasma-nm]
kde-plasma-nm-openconnect-0.9.3.5-1.fc22.i686 requires 
libopenconnect.so.3(OPENCONNECT_3.0)
kde-plasma-nm-openconnect-0.9.3.5-1.fc22.i686 requires 
libopenconnect.so.3
[nwchem]
nwchem-openmpi-6.3.2-11.fc21.i686 requires libmpi_usempi.so.1
[python-selenium]
python3-selenium-2.43.0-1.fc22.noarch requires python3-rdflib
[rubygem-wirb]
rubygem-wirb-1.0.3-2.fc21.noarch requires rubygem(paint) < 0:0.9
[shogun]
shogun-doc-3.2.0.1-0.27.git20140804.96f3cf3.fc22.noarch requires 
shogun-data = 0:0.8.1-0.18.git20140804.48a1abb.fc22
[uwsgi]
uwsgi-plugin-gridfs-2.0.7-2.fc22.i686 requires libmongoclient.so
uwsgi-stats-pusher-mongodb-2.0.7-2.fc22.i686 requires libmongoclient.so
[vfrnav]
vfrnav-20140510-2.fc22.i686 requires libpolyclipping.so.16
vfrnav-utils-20140510-2.fc22.i686 requires libpolyclipping.so.16
[wine]
wine-1.7.32-1.fc22.i686 requires mingw32-wine-gecko = 0:2.34



Broken deps for x86_64
--
[3Depict]
3Depict-0.0.16-3.fc22.x86_64 requires libmgl.so.7.2.0()(64bit)
[Sprog]
Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
[cab]
cab-0.1.9-12.fc22.x86_64 requires cabal-dev
[cinepaint]
cinepaint-libs-1.4-7.fc22.i686 requires libImath-2_1.so.11
cinepaint-libs-1.4-7.fc22.i686 requires libIlmThread-2_1.so.11
cinepaint-libs-1.4-7.fc22.i686 requires libIlmImf-Imf_2_1.so.21
cinepaint-libs-1.4-7.fc22.i686 requires libIexMath-2_1.so.11
cinepaint-libs-1.4-7.fc22.i686 requires libIex-2_1.so.11
cinepaint-libs-1.4-7.fc22.i686 requires libHalf.so.11
cinepaint-libs-1.4-7.fc22.x86_64 requires libImath-2_1.so.11()(64bit)
cinepaint-libs-1.4-7.fc22.x86_64 requires 
libIlmThread-2_1.so.11()(64bit)
cinepaint-libs-1.4-7.fc22.x86_64 requires 
libIlmImf-Imf_2_1.so.21()(64bit)
cinepaint-libs-1.4-7.fc22.x86_64 requires libIexMath-2_1.so.11()(64bit)
cinepaint-libs-1.4-7.fc22.x86_64 requires libIex-2_1.so.11()(64bit)
cinepaint-libs-1.4-7.fc22.x86_64 requires libHalf.so.11()(64bit)
[dnssec-check]
dnssec-check-1.14.0.1-4.fc20.x86_64 requires 
libval-threads.so.14()(64bit)
dnssec-check-1.14.0.1-4.fc20.x86_64 requires libsres.so.14()(64bit)
[gegl]
gegl-0.2.0-20.fc22.i686 requires libImath-2_1.so.11
gegl-0.2.0-20.fc22.i686 requires libIlmThread-2_1.so.11
gegl-0.2.0-20.fc22.i686 requires libIlmImf-Imf_2_1.so.21
gegl-0.2.0-20.fc22.i686 requires libIexMath-2_1.so.11
gegl-0.2.0-20.fc22.i686 requires libIex-2_1.so.11
gegl-0.2.0-20.fc22.i686 requires libHalf.so.11
gegl-0.2.0-20.fc22.x86_64 requires libImath-2_1.so.11()(64bit)
gegl-0.2.0-20.fc22.x86_64 requires libIlmThread-2_1.so.11()(64bit)
gegl-0.2.0-20.fc22.x86_64 requires libIlmImf-Imf_2_1.so.21()(64bit)
gegl-0.2.0-20.fc22.x86_64 requires libIexMath-2_1.so.11()(64bit)
gegl-0.2.0-20.fc22.x86_64 requires libIex-2_1.so.11()(64bit)
gegl-0.2.0-20.fc22.x86_64 requires libHalf.so.11()(64bit)
[glances]
glances-2.1.2-2.fc22.noarch requires python-psutil >= 0:2.0.0
[kde-plasma-nm]
kde-plasma-nm-openconnect-0.9.3.5-1.fc22.x86_64 requires 
libopenconnect.so.3(OPENCONNECT_3.0)(64bit)
kde-plasma-nm-openconnect-0.9.3.5-1.fc22.x86_64 requires 
libopenconnect.so.3()(64bit)
[nwchem]
nwchem-openmpi-6.3.2-11.fc21.x86_64 requires libmpi_usempi.so.1()(64bit)
[python-selenium]
python3-selenium-2.43.0-1.fc22.noarch requires python3-rdflib
[rubygem-wirb]
   

Re: How many users does Fedora have?

[Vít Ondruch]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dne 3.12.2014 v 08:47 Michel Alexandre Salim napsal(a):
> At the risk of jumping in, here's my own 2 cents on the subject...
>
> On 12/03/2014 12:30 AM, Stephen John Smoogen wrote:
>>
>>
>> On 2 December 2014 at 09:15, mailto:jfm...@free.fr>>
wrote:
>>
>> 2)  It has an uninspiring installer.
>>
>>
>> Ok I need more information on what this means in comparison to what? I
>> have installed pretty much every major Linux distribution and I have
>> never found any one of them 'inspiring'. Even the Ubuntu one is more of
>> "well at least its not the base Debian installer" versus "OMG I am alive
>> and free because of this installer." So I need more information to
>> understand what you are saying.
>> 
> While the next-gen Anaconda in Fedora 21 is much improved since its
> first iteration in Fedora 18, having just installed Ubuntu 14.04 on a
> test VM in the same week, I must say the Ubuntu installer has an edge
> mostly in aesthetics -- during the installation process, instead of a
> small banner at the bottom for introducing the operating system, you get
> an interactive grid of screenshots in the middle of the installation
> window, with nice looking left and right toggles.

I have not seen Ubuntu installer in a while, but may be we could
leverage AppData, which are prepared for Gnome Software, and present
some nice applications you can right after Fedora installation is done ...


Vít
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUfvNTAAoJEAzgnueZF7h8bkcP/2ZGrRr9HWtCQxMhyLjnVaku
6N6FBdEpiZCwK/y6qYkuIceGfpsRzCWgG2IKPCGThNxDAvre0SLkDOrj8ZTdVD3g
lQyAaoIVCCvIg5sI1RVloCJY83anDyg5HQwNKzzawXkZcj0e81gnkXeU1UG+CWia
52IvQKQfran7vEI2PTxYfIgcnLP+fBS5QTyFBY4+WaLhqTWsYerx0GlhBOyIb+ET
rwOdqwhviReblww2zdLPYe+CwUDN7YWMRAToAE908fjgl7NhyisgsCyCEG9M/WQg
Gu8+gHQnY+swKoumdb7upmOSWDN3ddwySZt7hSgcXIrRq5kgIj1sIxGLDLHjM/aQ
xBa70blWxv7H1OfM8uwuzz8SrEk0IJjyxw8ufw1GPkBwbma9SudOaBdW5MHHceHk
2f/lCPyhx7WXUd1owdnxcmtVjHG97LpcORw7tqpOk4hV3vfqWv9ul4XAR13+/FpN
7mq9QbAlqDDUEdSqP8MHlRx7EzxUiJ9VnXxtYVgsRjYKY9auZ5YkBWdx7cRaHUSV
arLp5DA+oWcXHtr36hJw2pzZXhfr5LMc65X67lP9McOl4xAMmwkzq0Mfsa5rbuXM
HJqimp0vdUzxtbFInTpRaWaYVfGrq8PUmg8i0n2sppi4pLOolYGdWVWCfbBfBNpY
hiO7bqH38QN0UKAYYocb
=JBqD
-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

F-21 Branched report: 20141203 changes

[Fedora Branched Report]

Compose started at Wed Dec  3 07:15:03 UTC 2014
Broken deps for armhfp
--
[avro]
avro-mapred-1.7.5-9.fc21.noarch requires hadoop-mapreduce
avro-mapred-1.7.5-9.fc21.noarch requires hadoop-client
[openstack-nova]
openstack-nova-compute-2014.1.2-1.fc21.noarch requires 
libvirt-daemon-xen
[ostree]
ostree-grub2-2014.11-1.fc21.armv7hl requires grub2
[spring-maps-default]
spring-maps-default-0.1-12.fc21.noarch requires spring
[syntastic]
syntastic-d-3.5.0-1.fc21.noarch requires ldc










Summary:
Added Packages: 0
Removed Packages: 0
Modified Packages: 0
Size of added packages: 0 (0 )
Size change of modified packages: 0 (0 )
Size of removed packages: 0 (0 )
Size change: 0 (0 )
Compose finished at Wed Dec  3 11:17:47 UTC 2014

-- 
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 21 Final Release Candidate 4 (RC4) Available Now!

[Adam Williamson]

NOTE: Signing of the RC4 tree is not yet complete, there are technical
issues in releng preventing it working. To strictly be sure we're
testing the right bits we should remember to check that the images we
test match the signed checksum files once they're available, and of
course you can carefully check the TLS certificate of the server when
downloading the images. fedup tests may require the --nogpgcheck
parameter until the signed .treeinfo file is available. releng will
update and close the trac ticket when signing is complete.

As per the Fedora 21 schedule [1], Fedora 21 Final Release Candidate 4
(RC4) is now available for testing. Note that RC3 never made it out of
the compose process - releng made a small mistake so they started over,
and it was easier to call the retry 'RC4' than clean up the failed
attempt and call the retry 'RC3'.

The only difference between RC4 and RC2 should be that the live images
have correct fontconfig caches. Otherwise RC4 and RC2 should be
effectively identical. There is no difference in their package sets, the
fontconfig fix was done in the kickstarts. Existing RC2 test results
will be considered valid for RC4 and transferred to the RC4 result
pages, but from now on, please switch to testing the RC4 images.

At present we're hopeful RC4 will be good enough for Final release, so
please help us get through all the testing!

Please see the following pages for download links (including delta ISOs)
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

Ideally, all Alpha, Beta, and Final priority test cases for each of
these test pages [2] should 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 21 Final test compose (TC) and release candidate (RC)
https://fedorahosted.org/rel-eng/ticket/6031

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

[1] http://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
[3] https://fedoraproject.org/wiki/Fedora_21_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