Re: Dash as default shell

[Pete Zaitcev]

On Thu, 2 Oct 2014 14:12:12 +0100
"Daniel P. Berrange"  wrote:

> I'd be curious of the results if someone wants to take a stock Fedora 21
> install and switch /bin/sh to point to dash and report if they can still
> boot & login to GNOME.

I did a smaller run on a server without GNOME. Had to chage the parts
of initscripts that you have foreseen and nothing else. The unpleasant
part was that iptables won't start.

-- Pete
-- 
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: No Mesa 10.3-1 in F21 (instead of rc3)?

[Rahul Sundaram]

Hi

On Fri, Oct 10, 2014 at 7:51 PM, Patrick Laimbock  wrote:

> That's good to hear. I didn't know that a (core) component during the
> dev cycle needed to go through the karma process so thanks for pointing
> that out.
>

https://fedoraproject.org/wiki/Releases/Branched  explains the process

Rahul
-- 
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: No Mesa 10.3-1 in F21 (instead of rc3)?

[Patrick Laimbock]

Hi Stephen,

On 10/10/2014 07:29 PM, Stephen Gallagher wrote:
[snip]
> According to
> https://admin.fedoraproject.org/updates/FEDORA-2014-11757/mesa-10.3-1.20140927.fc21
>  it only reached the stable karma threshold yesterday, so it will hit the 
> mirrors sometime tomorrow, most likely.

That's good to hear. I didn't know that a (core) component during the
dev cycle needed to go through the karma process so thanks for pointing
that out.

Cheers,
Patrick

-- 
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 Beta Test Compose 3 (TC3) Available Now!

[Adam Williamson]

As per the Fedora 21 schedule [1], Fedora 21 Beta Test Compose 3 (TC3)
is now available for testing. Content information, including changes,
can be found at https://fedorahosted.org/rel-eng/ticket/6010#comment:4 .
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

The Summary page:

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

combines the result tables from all the pages, without the instructions.

Ideally, all Alpha and Beta priority test cases for each of these test
pages [2] should pass in order to meet the Beta Release Criteria [3].
Help is available on #fedora-qa on irc.freenode.net [4], or on the test
list [5].

Create Fedora 21 Beta test compose (TC) and release candidate (RC)
https://fedorahosted.org/rel-eng/ticket/6010

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_Beta_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: Anyone else seen systemd-208-22.fc20.x86_64 setting /dev perms to 0600?

[David Woodhouse]

On Fri, 2014-10-10 at 15:57 +0100, Richard W.M. Jones wrote:
> Both /dev/fuse and /dev/net/tun were set to 0600 (they both should be
> 0666) at the exact moment that I updated to systemd-208-22.fc20.x86_64
> this morning.
> 
> Possible other files have been affected too, but those were the two
> that broke stuff.

I've seen /dev/net/tun get mode 0600 but hadn't actually correlated it
with anything, and it wasn't consistently doing it.

-- 
dwmw2


smime.p7s
Description: S/MIME cryptographic 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: Anyone else seen systemd-208-22.fc20.x86_64 setting /dev perms to 0600?

[Bruno Wolff III]

On Fri, Oct 10, 2014 at 15:57:12 +0100,
 "Richard W.M. Jones"  wrote:


Both /dev/fuse and /dev/net/tun were set to 0600 (they both should be
0666) at the exact moment that I updated to systemd-208-22.fc20.x86_64
this morning.

Possible other files have been affected too, but those were the two
that broke stuff.

Anyone seen this?


I have reported https://bugzilla.redhat.com/show_bug.cgi?id=1139034 because 
this broken sound for me.

--
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: No Mesa 10.3-1 in F21 (instead of rc3)?

[Stephen Gallagher]

On Fri, 2014-10-10 at 18:03 +0200, Patrick Laimbock wrote:
> Hi,
> 
> I'm wondering why Mesa 10.3-1 (so not the rc3 but the official 10.3 
> release) has not made it to F21. It fixes a bunch of crashes with Radeon 
> r300 (and hence gnome-shell) for me.
> 
> Thanks,
> Patrick


According to
https://admin.fedoraproject.org/updates/FEDORA-2014-11757/mesa-10.3-1.20140927.fc21
 it only reached the stable karma threshold yesterday, so it will hit the 
mirrors sometime tomorrow, most likely.


signature.asc
Description: This is a digitally signed message part
-- 
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 Carlos Morel-Riquelme

[Carlos Morel-Riquelme]

Hi folks, mi name is carlos morel-riquelme, i start using linux since 2008
with ubuntu but i change to fedora since fedora 15, now in fedora always
try to collaborate in testing and translate to spanish some wiki  pages.
Now i made a little Ruby app it's my first package for fedora so, i need to
somebody check this. Please :)

bugzilla review
https://bugzilla.redhat.com/show_bug.cgi?id=1151462

wiki
https://fedoraproject.org/wiki/User:N0oir


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

No Mesa 10.3-1 in F21 (instead of rc3)?

[Patrick Laimbock]

Hi,

I'm wondering why Mesa 10.3-1 (so not the rc3 but the official 10.3 
release) has not made it to F21. It fixes a bunch of crashes with Radeon 
r300 (and hence gnome-shell) for me.


Thanks,
Patrick
--
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: bugzilla usage trends

[Przemek Klosowski]

On 10/10/2014 06:12 AM, Richard W.M. Jones wrote:

On Thu, Oct 09, 2014 at 05:39:34PM -0400, Przemek Klosowski wrote:

I was curious about the rate of bug reporting in Fedora, and did
this quick experiment. I thought it might be interesting to folks
here who either work on the infrastructure or are curious about
long-term collaboration trends in Fedora.

I checked the date of reporting of every 10,000th bug (bugzilla #1,
#1, etc, all the way to the recent 115---see attached data).
Some bugs were private so I didn't have access to their info, but I
got enough data to  calculate bug velocity (increase in the bug
number divided by the time interval) over time. The data is a little
noisy, but you can clearly see the ever-increasing trend.

I'm afraid there are a couple of problems with this analysis:
- Automated bugs (eg from abrt) may or may not be considered to be
   real bug reports.
Just a  COUPLE? Thank you, kind Sir---I would have said it's rife with 
problems. For one thing
it totally ignores the distinction of Fedora vs. EPEL and RedHat bugs. 
Still, it gives an order of
magnitude estimate and the trend. No matter what the origin of the bugs, 
they still have to

be dealt with somehow.


- Bugzilla has both imported large bug sets from other databases at
   various times (when Red Hat acquired other companies), and also has
   had periods when it didn't allocate bug numbers sequentially.  At
   one point IIRC each new bug report incremented the bug ID by 10.

Ah so that's where the spikes come from. I was wondering.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Engineering Representiatve for the new Fedora Council

[Matthew Miller]

Hey all Fedora distribution developers, engineers, builders, and
infrastructure people! As I hope you've seen by now, we're creating a new
Fedora Council as a top-level project leadership and governance body.
(If you missed it, see inode0's general announcement to the community

and the new charter at .)

One seat of the new Council is selected by FESCo to represent all of the
groups that logically fall under that committee — not in the ruleship sense,
but in the sense that it makes a natural place for coordination and
representation of the technical concerns.

We have a FESCo ticket  for
selecting this representative, but the conversation is larger than just the
members of FESCo, so I'm bringing it here. Help FESCo decide who can best
represent you, your groups, and your work in the project.


-- 
Matthew Miller

Fedora Project Leader
___
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

Engineering Representiatve for the new Fedora Council

[Matthew Miller]

Hey all Fedora distribution developers, engineers, builders, and
infrastructure people! As I hope you've seen by now, we're creating a new
Fedora Council as a top-level project leadership and governance body.
(If you missed it, see inode0's general announcement to the community

and the new charter at .)

One seat of the new Council is selected by FESCo to represent all of the
groups that logically fall under that committee — not in the ruleship sense,
but in the sense that it makes a natural place for coordination and
representation of the technical concerns.

We have a FESCo ticket  for
selecting this representative, but the conversation is larger than just the
members of FESCo, so I'm bringing it here. Help FESCo decide who can best
represent you, your groups, and your work in the project.


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

Re: rpm 4.12 and weak dependencies

[Miloslav Trmač]

- Original Message -
> On Thu, Oct 9, 2014, at 11:09 AM, Miloslav Trmač wrote:
> 
> > especially as we are taking the RPM-level control away from the users
> > completely in cloud
> 
> How is that?

We ship filesystem images with many installed packages.  Removing the packages 
from an existing image is possible but fairly pointless because it will not 
decrease the maximum image size.  And the way to spin up a new VM quickly is to 
clone a disk image, not to install it from a set of RPMs.  RPMs still exist but 
are not something users interact with the way we keep updating one RPM at a 
time in workstations.

> > and Atomic images already.
> 
> See:
> 
> https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2014-October/msg5.html

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

Anyone else seen systemd-208-22.fc20.x86_64 setting /dev perms to 0600?

[Richard W.M. Jones]

Both /dev/fuse and /dev/net/tun were set to 0600 (they both should be
0666) at the exact moment that I updated to systemd-208-22.fc20.x86_64
this morning.

Possible other files have been affected too, but those were the two
that broke stuff.

Anyone seen this?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
-- 
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: Action Required: Shipping larger application icons in Fedora 22

[Jaroslav Reznik]

- Original Message -
> In Fedora 21 we show any valid application in the software center with
> an application icon of 32x32 or larger. Currently a 32x32 icon has to
> be padded with 16 pixels of whitespace on all 4 edges, and *also* has
> to be scaled x2 to match other UI elements on HiDPI screens. This
> looks fuzzy, out of alignment and lowers the quality of an otherwise
> beautiful installing experience.
> 
> For Fedora 22 we are planning to increase the minimum icon size to
> 48x48, with recommended installed sizes of 24x24, 48x48, 64x64,
> 256x256 (or SVG). Modern desktop applications typically ship multiple
> sizes of icons in known locations, and it's very much the minority of
> packages in Fedora that only ship such small icons.
>
> jreznik kmousetool (kmousetool.desktop)

Upstream bug https://bugs.kde.org/show_bug.cgi?id=339844

This icon really deserves more love by upstream.

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

Re: Action Required: Shipping larger application icons in Fedora 22

[Richard Hughes]

On 29 September 2014 12:36, Richard Hughes  wrote:
> Updated packages should be built for F22 (rawhide) before the end of
> October

So far very few packages have been built for F22 that contain larger
icons. I'm still all set to start mass-filing bugs at the end of
October.

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

[Base] Base Design WG agenda meeting 10 October 2014 15:00 UTC on #fedora-meeting

[Phil Knirsch]

Agenda:
 - Update buildrequires cleanup work (davids & nils!)
 - Update Alpha base image
 - Open Floor

Thanks & regards, Phil

--
Philipp Knirsch  | Tel.:  +49-711-96437-470
Manager Core Services| Fax.:  +49-711-96437-111
Red Hat GmbH | Email: Phil Knirsch 
Wankelstrasse 5  | Web:   http://www.redhat.com/
D-70563 Stuttgart, Germany
--
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: Giving away all of my packages

[Christof Damian]

Thanks Tuan. It is yours now.

On 10 October 2014 03:51, Truong Anh. Tuan  wrote:
>
> - Original Message -
>> From: "Christof Damian" 
>> To: "Development discussions related to Fedora" 
>> 
>> Cc: "Fedora PHP development team" 
>> Sent: Thursday, October 9, 2014 9:12:42 PM
>> Subject: Re: Giving away all of my packages
>>
>> Remaining packages up for grabs:
>>
>> - python-progressbar ( hasn't changed for ages, might be time to retire it)
>
> AFAICS, there is only one left so I can take this if you want.
> At a glance, I see it maybe useful so it is worth to keep it.
>
> FAS: tuanta.
>
> Kind regards,
> Tuan
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
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: 20141010 changes

[Fedora Rawhide Report]

Compose started at Fri Oct 10 05:15:05 UTC 2014
Broken deps for i386
--
[Agda]
ghc-Agda-2.3.2.2-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so
ghc-Agda-2.3.2.2-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so
ghc-Agda-2.3.2.2-5.fc22.i686 requires 
ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires 
libHSterminfo-0.3.2.5-ghc7.6.3.so
ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires 
libHShaskeline-0.7.0.3-ghc7.6.3.so
ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires 
ghc-devel(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires 
ghc(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3)
ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires 
ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
[PyQuante]
PyQuante-libint-1.6.4-11.fc22.1.i686 requires libint(x86-32) = 
0:1.1.6-2.fc21
[Sprog]
Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
[audtty]
audtty-0.1.12-9.fc20.i686 requires libaudclient.so.2
[authhub]
authhub-0.1.2-3.fc19.i686 requires libjson.so.0
[aws]
aws-devel-3.1.0-6.fc21.i686 requires libgrypt-devel
[cab]
cab-0.1.9-12.fc22.i686 requires cabal-dev
[collectd]
collectd-onewire-5.4.1-9.fc22.i686 requires libowcapi-2.9.so.5
[darcs]
darcs-2.8.4-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so
darcs-2.8.4-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so
darcs-2.8.4-5.fc22.i686 requires 
ghc(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3)
darcs-2.8.4-5.fc22.i686 requires 
ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
ghc-darcs-2.8.4-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so
ghc-darcs-2.8.4-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so
ghc-darcs-2.8.4-5.fc22.i686 requires 
ghc(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3)
ghc-darcs-2.8.4-5.fc22.i686 requires 
ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
ghc-darcs-devel-2.8.4-5.fc22.i686 requires 
ghc-devel(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3)
ghc-darcs-devel-2.8.4-5.fc22.i686 requires 
ghc-devel(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
[debconf]
debconf-1.5.53-1.fc22.noarch requires perl(:MODULE_COMPAT_5.18.2)
[deltacloud-core]
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudservers)
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudfiles)
[django-recaptcha]
django-recaptcha-0.1-7.20091212svn6.fc21.noarch requires python-django14
[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
[dragonegg]
dragonegg-3.4-0.3.rc0.fc21.i686 requires gcc = 0:4.8.2-14.fc21
[edelib]
edelib-2.1-5.fc22.i686 requires libedelib.so
edelib-devel-2.1-5.fc22.i686 requires libedelib.so
[eucalyptus]
eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.i686 requires 
hibernate3-jbosscache >= 0:3.6.10-7
[fatrat]
1:fatrat-1.2.0-0.21.beta2.fc22.i686 requires libtorrent-rasterbar.so.7
[flush]
flush-0.9.12-10.fc22.i686 requires libtorrent-rasterbar.so.7
[gedit-valencia]
gedit-valencia-0.4.0-1.20131223git94442bf.fc21.i686 requires 
libvala-0.24.so.0
[ghc-hjsmin]
ghc-hjsmin-0.1.4.7-3.fc22.i686 requires 
libHSoptparse-applicative-0.9.0-ghc7.6.3.so
[gnome-python2-desktop]
gnome-python2-metacity-2.32.0-18.fc21.i686 requires 
libmetacity-private.so.0
[gofer]
ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) >= 0:0.16.0
[golang-github-influxdb-influxdb]

golang-github-influxdb-influxdb-datastore-0.8.0-0.3.rc4.git67f9869.fc22.noarch 
requires golang(github.com/influxdb/gomdb)
[gorm]
gorm-1.2.18-5.fc20.i686 requires libgnustep-gui.so.0.23
[hledger]
ghc-hledger-0.19.3-5.fc22.i686 requires 
libHSterminfo-0.3.2.5-ghc7.6.3.so
ghc-hledger-0.19.3-5.fc22.i686 requires 
libHShaskeline-0.7.0.3-ghc7.6.3.so
ghc-hledger-0.19.3-5.fc22.i686 requires 
ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
ghc-hledger-devel-0.19.3-5.fc22.i686 requires 
ghc-devel(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
hledger-0.19.3-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so
hledger-0.19.3-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so
hledger-0.19.3-5.fc22.i686 requires 
ghc(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3)
hledger-0.19.3-5.fc22.i686 requires 
ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5)
[idris]
idris-0.9.9.1-3.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so
idris-0.9.9.1-3.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so
idris-0.9.9.1-3.fc22.i686 requires 
ghc(t

F-21 Branched report: 20141010 changes

[Fedora Branched Report]

Compose started at Fri Oct 10 07:15:02 UTC 2014
Broken deps for armhfp
--
[PyQuante]
PyQuante-libint-1.6.4-11.fc21.1.armv7hl requires libint(armv7hl-32) = 
0:1.1.6-2.fc21
[audtty]
audtty-0.1.12-9.fc20.armv7hl requires libaudclient.so.2
[authhub]
authhub-0.1.2-3.fc19.armv7hl requires libjson.so.0
[avro]
avro-mapred-1.7.5-9.fc21.noarch requires hadoop-mapreduce
avro-mapred-1.7.5-9.fc21.noarch requires hadoop-client
[cduce]
cduce-0.5.5-9.fc21.armv7hl requires ocaml(Camlp4) = 
0:ebd368022fd2bc7b305a42902efa4c90
[cp2k]
cp2k-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21
cp2k-mpich-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 
0:1.1.6-2.fc21
cp2k-openmpi-2.5.1-8.fc21.armv7hl requires libmpi_usempi.so.1
cp2k-openmpi-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 
0:1.1.6-2.fc21
[deltacloud-core]
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudservers)
deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires 
rubygem(cloudfiles)
[django-recaptcha]
django-recaptcha-0.1-7.20091212svn6.fc21.noarch requires python-django14
[dragonegg]
dragonegg-3.4-0.3.rc0.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21
[edelib]
edelib-2.1-5.fc21.armv7hl requires libedelib.so
edelib-devel-2.1-5.fc21.armv7hl requires libedelib.so
[eucalyptus]
eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.armv7hl 
requires hibernate3-jbosscache >= 0:3.6.10-7
[fatrat]
1:fatrat-1.2.0-0.21.beta2.fc21.armv7hl requires 
libtorrent-rasterbar.so.7
[flush]
flush-0.9.12-10.fc21.armv7hl requires libtorrent-rasterbar.so.7
[freesteam]
freesteam-ascend-2.1-6.20140724svn753.fc21.armv7hl requires 
libascend.so.1
[gcc-python-plugin]
gcc-python2-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 
0:4.8.2-14.fc21
gcc-python2-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21
gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires 
libpython3.3dm.so.1.0
gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 
0:4.8.2-14.fc21
gcc-python3-plugin-0.12-18.fc21.armv7hl requires libpython3.3m.so.1.0
gcc-python3-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21
[gedit-valencia]
gedit-valencia-0.4.0-1.20131223git94442bf.fc21.armv7hl requires 
libvala-0.24.so.0
[gnome-python2-desktop]
gnome-python2-metacity-2.32.0-18.fc21.armv7hl requires 
libmetacity-private.so.0
[gofer]
ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) >= 0:0.16.0
[leiningen]
leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks
leiningen-1.7.1-7.fc20.noarch requires classworlds
[libghemical]
libghemical-2.99.1-24.fc20.armv7hl requires libf77blas.so.3
libghemical-2.99.1-24.fc20.armv7hl requires libatlas.so.3
[libmygpo-qt]
libmygpo-qt5-devel-1.0.8-1.fc21.armv7hl requires libmygpo-qt5{?_isa} = 
0:1.0.8-1.fc21
[libopensync-plugin-irmc]
1:libopensync-plugin-irmc-0.22-7.fc20.armv7hl requires libopenobex.so.1
[ltsp]
ltsp-client-5.4.5-8.fc21.armv7hl requires fuse-unionfs
ltsp-server-5.4.5-8.fc21.armv7hl requires cdialog
[meshmagick]
meshmagick-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1
meshmagick-libs-0.6.0-20.svn2898.fc21.armv7hl requires 
libOgreMain.so.1.8.1
[monodevelop-vala]
monodevelop-vala-2.8.8.1-6.fc21.armv7hl requires vala < 0:0.25.0
[netdisco]
netdisco-1.1-7.fc21.noarch requires perl(SNMP::Info::Layer2::Bay)
[ocaml-pa-do]
ocaml-pa-do-0.8.16-3.fc21.armv7hl requires ocaml(Camlp4) = 
0:ebd368022fd2bc7b305a42902efa4c90
[openslides]
openslides-1.3.1-3.fc21.noarch requires python-django < 0:1.5
[openstack-nova]
openstack-nova-compute-2014.1.2-1.fc21.noarch requires 
libvirt-daemon-xen
[openvas-client]
openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_omp.so.6
openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_nasl.so.6
openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_misc.so.6
openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_hg.so.6
openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_base.so.6
[perl-RT-Authen-ExternalAuth]
perl-RT-Authen-ExternalAuth-0.11-5.fc21.noarch requires rt3
[perl-RT-Extension-CommandByMail]
perl-RT-Extension-CommandByMail-0.07-10.fc21.noarch requires 
perl(RT::Interface::Email)
[pipelight-selinux]
pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight-common
pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight-common
pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight
pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight
[pootle]
pootle-2.1.6-8.fc21.noarch requires python-django14
[python-askbot-fedmsg]
python-askbot-fedmsg-0.1.0-2.fc21.noarch requi

Re: bugzilla usage trends

[Richard W.M. Jones]

On Thu, Oct 09, 2014 at 05:39:34PM -0400, Przemek Klosowski wrote:
> I was curious about the rate of bug reporting in Fedora, and did
> this quick experiment. I thought it might be interesting to folks
> here who either work on the infrastructure or are curious about
> long-term collaboration trends in Fedora.
> 
> I checked the date of reporting of every 10,000th bug (bugzilla #1,
> #1, etc, all the way to the recent 115---see attached data).
> Some bugs were private so I didn't have access to their info, but I
> got enough data to  calculate bug velocity (increase in the bug
> number divided by the time interval) over time. The data is a little
> noisy, but you can clearly see the ever-increasing trend.

I'm afraid there are a couple of problems with this analysis:

- Automated bugs (eg from abrt) may or may not be considered to be
  real bug reports.

- Bugzilla has both imported large bug sets from other databases at
  various times (when Red Hat acquired other companies), and also has
  had periods when it didn't allocate bug numbers sequentially.  At
  one point IIRC each new bug report incremented the bug ID by 10.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
-- 
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: [Base] Base Design WG agenda meeting 03 October 2014 15:00 UTC on #fedora-meeting

[Dennis Gilmore]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, 06 Oct 2014 13:32:08 +0200
Václav Pavlín  wrote:

> Dennis, how can I help you to figure out image publishing process?
> Let me know if I can be any help, we should definitely move forward
> on this and it probably doesn't make sense vote until you say we have
> a workflow how to ship the image.
> 
> Vašek

A big hurdle we have right now is that docker does not support an api
at all to update the registry. so all updates will need people to
manually do things. The other big one is that they do not want us to
push updates daily like we really should for rawhide. 

Dennis


> On 3.10.2014 08:56, Václav Pavlín wrote:
> > Hi I will be traveling to Prague in the afternoon so I'd suggest to 
> > cancel this meeting as 2 members are not going to be there and I my 
> > bus might get delay.
> >
> > Vašek
> >
> > On 3.10.2014 02:57, Dennis Gilmore wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> >>
> >> On Thu, 02 Oct 2014 18:28:40 +0200
> >> Phil Knirsch  wrote:
> >>
> >>> Unfortunately tomorrow is a public holiday in Germany, but if
> >>> someone else from the WG would run the meeting i've put together
> >>> a proposed agenda for tomorrow to give a few updates:
> >>>
> >>> Agenda:
> >>>- Update buildrequires cleanup work (davids)
> >>>- Update Alpha base image
> >>>- Open Floor
> >>>
> >>> Thanks & regards, Phil
> >>>
> >> I will be missing the meeting due to being on PTO
> >>
> >> Dennis
> >> -BEGIN PGP SIGNATURE-
> >> Version: GnuPG v2
> >>
> >> iQIcBAEBAgAGBQJULfRzAAoJEH7ltONmPFDRB7kQAKkrlI37MubsAPVtpgHl8riB
> >> +kzk4owFeyxRMOwhEahRWDNAPOj9GA2gB53DjE9sWfTrlBfgIQxK+vjrOGCUfkaJ
> >> hvPRVOTp1yrpchea6FnR7H8ZWD1HEcFgTt8ffpCHegnWJCfGlRgE4Ac1FZ75DicC
> >> wPx3z9iSzYTMNei13QgDFjsUyVROI7BDT0eQAuCGAqoJ5waGhoNzIuGf7HiNYpi5
> >> VhYUuHXrOWRGBf8rRnxo94MLZWJKuLCd0mGNklMnZoA7eyJ1fxclfAEUf4NBFc7/
> >> mfpK1zpQRiHkfsQSfZFOghTNOepWCWxKlLJIC2aYEbWDSQFTyzyigX8cm6tflfzi
> >> pBGuukHq/SNhcBtrnnNCKLGfB4T2kzPr3ph52urqqcKlDOLXTJ16nD2GdDmMdG8F
> >> ija2QmhZBEHO5b99J/b74iTgGmbrA+5XPrCF2c0hD6YG+CIcxI0e+uie6Y2e2zsC
> >> AoJnOf94eavkEWCJhIzKOhieLBo/pZ0JfwAuvR//euf52tUlaAvE2/aEehY5Ezb+
> >> PaZ8fKgH71BST/r3exNKKv7BOWkQkcyBXeFhOkPuaToEOX17UoHisJdDrdxx/tAk
> >> AeZAAGvJSYeEt57HzObCbeS/OEZ+cCfnJu4s+zmuSiXImWkbyYV04xLTmLxzE+oP
> >> NvsU1+XAno8as7nylz5U
> >> =DLam
> >> -END PGP SIGNATURE-
> >
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBAgAGBQJUN5vuAAoJEH7ltONmPFDRqHUP/j9zqZVmq/xb8KpzoqJWBCxS
ogp4ZDwC1XmDgIADTMzU5ry9/1dL/gG1lfWrFm3NmWoqluLle5rykTWnLS+Dzt4e
9+bn6kMbd1YywGPcj1mPJzoa28k56H4zK4NeELTmIc1WpmFCD2+ZGsvzXlmSAQWH
DEwURBU565JDPWBJs+LLxlidF7AaTscx7TFVhfAdYCoaiwa5xxves8mytphpFnl0
h5IAObJVNqQLdGyz4hkTFAT7O7oauMp3NTnAtAbuaYlfwJBBJf1QGKdGkv6+tQH1
6g9kdvcfuA5yBjQDscYl0nGxLXfIeo0PevVelbvpwlwgal8nH/Ohd4pJ1miHeFsH
qYZVfCKYHuEl6+/8RTr8DuBk3jbVQ/88JTr+WtYWnrqcJYwDYaqdWLEZEgMd7BhU
37Hfj1jyIYOpysnTdB5au8e/bp6rbAR+5eEatnpgNxS8Gs3c6NMvYLwSZeL/8jgp
h6YyCZTpdAndpktDK/oTxdF7zTv1Hm0VbtlEMBSXv5eV4JUmWqv6xCUDQrTXzMea
+LEwejmTw3UMgK/4BQ4Afq7IufX0pGKK8iB9KrWfb1wvEBL1s6UP0yiQ1EEydiRg
lR+RlzkzdPrEVOs3YIbVBmAO7pe22TFy7TWJoQ20mJOOxdKGT7I72B1+JkFhWdad
rUilxS+UigB1YXPPQ/zn
=lLVF
-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: rpm 4.12 and weak dependencies

[Florian Festi]

On 10/09/2014 05:29 PM, Jerry James wrote:

Added most of your improvements to the page.

Thanks!

Florian


PS: The rpm.org wiki is locked down because of spam. But people
inerested in improving the contents and documentation can just create an
account and ask for edit privileges on the mailing lists or #rpm.org
@freenode.

-- 

Red Hat GmbH, http://www.de.redhat.com/ Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Charles Peters
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct