gmane.linux.redhat.fedora.devel

Re: Need some packages to be reviewed.

Volker Fröhlich — 2012-05-23T12:28:59

Am Mittwoch, 23. Mai 2012, 16:19:22 schrieb Aditya Patawari:

I'd trade whisper for:

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

Volker Fröhlich

[Test-Announce] Fedora 17 FINAL Go/No-Go Meeting (#2), Thursday,May 24, < at >13:00 Eastern

Robyn Bergeron — 2012-05-23T12:16:21

Please join us on irc.freenode.net in #fedora-meeting-1 for this 
important meeting, wherein we shall determine the shipment readiness of 
F17 Final.

Thursday, May 24, 2012 < at > 17:00 UTC (13:00 EDT/10:00 PDT)

"Before each public release Development, QA and Release Engineering meet 
to determine if the release criteria are met for a particular release. 
This meeting is called the Go/No-Go Meeting."

"Verifying that the Release criteria are met is the responsibility of 
the QA Team."

For more details about this meeting see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting

In the meantime: Keep an eye on the blocker list here:
http://fedoraproject.org/wiki/Current_Release_Blockers

Let's ship the beefy miracle, folks! :)

-Robyn
_______________________________________________
test-announce mailing list
test-announce< at >lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

Fedora 17 FINAL Go/No-Go Meeting (#2), Thursday, May 24,< at >13:00 Eastern

Robyn Bergeron — 2012-05-23T12:16:21

Please join us on irc.freenode.net in #fedora-meeting-1 for this 
important meeting, wherein we shall determine the shipment readiness of 
F17 Final.

Thursday, May 24, 2012 < at > 17:00 UTC (13:00 EDT/10:00 PDT)

"Before each public release Development, QA and Release Engineering meet 
to determine if the release criteria are met for a particular release. 
This meeting is called the Go/No-Go Meeting."

"Verifying that the Release criteria are met is the responsibility of 
the QA Team."

For more details about this meeting see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting

In the meantime: Keep an eye on the blocker list here:
http://fedoraproject.org/wiki/Current_Release_Blockers

Let's ship the beefy miracle, folks! :)

-Robyn
_______________________________________________
devel-announce mailing list
devel-announce< at >lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

[Test-Announce] Fedora Board, FESCo,and FAmSCo elections: Town hall meeting schedule

Robyn Bergeron — 2012-05-23T11:43:56

As you have (hopefully) heard by now, elections for the Fedora Board, 
FESCo, and FAmSCo are quickly approaching.

In each election cycle, a series of town hall meetings is held to give 
community members and opportunity to ask candidates questions - and hear 
their answers - via IRC.

The town hall schedule for the upcoming election is as follows:

Fedora Project Board:
* Tuesday, May 29, 2012 at 17:00 UTC
* Wednesday, May 30, 2012 at 20:00 UTC

FESCo (Fedora Engineering Steering Committee):
* Wednesday, May 30, 2012 at 17:00 UTC
* Thursday, May 31, 2012 at 20:00 UTC

FAmSCo (Fedora Ambassadors Steering Committee):
* Sunday, May 27, 2012 at 16:00 UTC
* Monday, May 28 at 17:00 UTC

Not sure what time that is? Use a handy-dandy time zone calculator to 
find out when to show up:
http://www.timeanddate.com/worldclock/converter.html

Important information about how you can participate in the town halls 
via IRC, as well as the details of each town hall meeting, can be seen 
on the wiki here:

http://fedoraprojec

Fedora Board, FESCo, and FAmSCo elections: Town hall meeting schedule

Robyn Bergeron — 2012-05-23T11:43:56

As you have (hopefully) heard by now, elections for the Fedora Board, 
FESCo, and FAmSCo are quickly approaching.

In each election cycle, a series of town hall meetings is held to give 
community members and opportunity to ask candidates questions - and hear 
their answers - via IRC.

The town hall schedule for the upcoming election is as follows:

Fedora Project Board:
* Tuesday, May 29, 2012 at 17:00 UTC
* Wednesday, May 30, 2012 at 20:00 UTC

FESCo (Fedora Engineering Steering Committee):
* Wednesday, May 30, 2012 at 17:00 UTC
* Thursday, May 31, 2012 at 20:00 UTC

FAmSCo (Fedora Ambassadors Steering Committee):
* Sunday, May 27, 2012 at 16:00 UTC
* Monday, May 28 at 17:00 UTC

Not sure what time that is? Use a handy-dandy time zone calculator to 
find out when to show up:
http://www.timeanddate.com/worldclock/converter.html

Important information about how you can participate in the town halls 
via IRC, as well as the details of each town hall meeting, can be seen 
on the wiki here:

http://fedoraprojec

F-17 Branched report: 20120523 changes

Fedora Branched Report — 2012-05-23T11:10:56

Compose started at Wed May 23 08:15:05 UTC 2012

Broken deps for x86_64
----------------------------------------------------------
[LuxRender]
LuxRender-blender-0.8.0-13.fc17.x86_64 requires blender(ABI) = 0:2.61
[aeolus-conductor]
aeolus-conductor-0.4.0-2.fc17.noarch requires rubygem(fastercsv)
aeolus-conductor-0.4.0-2.fc17.noarch requires ruby(abi) = 0:1.8
[aeolus-configserver]
aeolus-configserver-0.4.5-1.fc17.noarch requires ruby-nokogiri
[calf]
lv2-calf-plugins-0.0.18.6-6.fc17.x86_64 requires lv2core
[dh-make]
dh-make-0.55-4.fc17.noarch requires debhelper
[dustmite]
dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit)
[gnome-do-plugins]
gnome-do-plugins-banshee-0.8.4-8.fc17.x86_64 requires mono(Banshee.CollectionIndexer) = 0:2.2.0.0
[gorm]
gorm-1.2.13-0.2.20110331.fc17.i686 requires libobjc.so.3
gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-gui.so.0.20
gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-base.so.1.23
gorm-1.2.13-0.2.20110331.fc17.x86_64 r

Need some packages to be reviewed.

Aditya Patawari — 2012-05-23T10:49:22

Hey,

I am looking for some kind people to review the following packages:


Carbon: https://bugzilla.redhat.com/show_bug.cgi?id=824348
graphite-web: https://bugzilla.redhat.com/show_bug.cgi?id=824357
whisper: https://bugzilla.redhat.com/show_bug.cgi?id=824361

--
Aditya Patawari
http://blog.adityapatawari.com/
https://fedoraproject.org/wiki/User:Adimania
India

Re: Packaging Guidelines - creating tarball from VCS with script

Tomas Radej — 2012-05-23T08:12:54

On Wed, 16 May 2012 10:10:17 -0600
Kevin Fenzi <kevin< at >scrye.com> wrote:


Since the discussion is pretty much done here, I'll talk to RPM guys and see if they find this to be a good idea. Thanks for the input, guys.

Re: Stop the git abuse

Panu Matilainen — 2012-05-23T06:53:38

Just out of curiosity, which package is that? I'm seeing a much bigger 
difference between dropped caches and the following run (from ~6-7 
seconds of uncached down to ~0.5s on the next run)


Well, here's what I see after drop_caches=3 from 'strace -tt fedpkg 
verrel' on kernel.spec which is one of the most complicated specs in 
Fedora land:

09:09:06.928011         fedpkg exec
09:09:12.699345         python imports done
09:09:13.510192         rpm exec
09:09:15.345425         rpm exit
09:09:15.385441         fedpkg exit

So by the look of things, 2/3 of the execution time is spent importing 
python modules. The rpm execution time is heavily dependent on what the 
spec actually does, eg in case of kernel.spec this includes ~50 
fork+execs of shell, getconf and two python invocations from executing 
shell macros.

 From plain rpmspec parsing POV (shell macros aside), at top of 
callgrind charts sits the rpm bad performance hallmark pattern of 
repeated insert/delete, qsort and bsearch cycles (on macros). Ch

[Test-Announce] Fedora 17 Final Release Candidate 4 (RC4) AvailableNow!

Andre Robatino — 2012-05-23T02:41:27

As per the Fedora 17 schedule [1], Fedora 17 Final Release Candidate 4
(RC4) is now available for testing. Content information, including
changes, can be found at https://fedorahosted.org/rel-eng/ticket/5196 .
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

Desktop:

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

Security Lab:

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

Ideally, all Alpha, Beta, and Final priority test cases for Installation
[2], Base [3], Desktop [4], and Security Lab [5] should pass in orde

Kickstart packages --default parsing query

Amit Saha — 2012-05-23T01:26:09

Hello:

I posted this to the Kickstart list [1], but thought of checking it
here in the interest of a faster turnaround time.

I am trying to add a repository to an existing KS file. This is the script [2].

The script is doing its job for KS files which do not have a
'--default' switch added to the %packages section. However, for a KS
file which has a %packages --default section added, the parser does
not read beyond it and hence creates a KS file which do not have any
of the following packages specified in the KS file.

To quickly verify the problem, I have added two KS files (basically
the fedora-install-fedora.ks used to create Fedora installation DVDs)
with one having the --default option, and the other not having it. I
have commented out the actual repo addition code so that the problem
can be reproduced easily.

For example, with the default.ks file:

$python ks_addrepo.py

#version=DEVEL
repo --name="fedora"
--mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basear

Weekly ARM status meeting - Wed 2012/05/23

Paul Whalen — 2012-05-23T00:10:32

Good day all,

This weeks Fedora ARM status meeting will take place tomorrow (Wednesday May 23rd) in #fedora-meeting-1 on Freenode.

Times in various time zones (please let us know if these do not work):

PDT: 1pm
MDT: 2pm
CDT: 3pm
EDT: 4pm
UTC: 8pm
BST: 9pm
CST: 10pm


Current items on the agenda:

1) F17 build status 
        - branching, updates, updates-testing
        - remaining problem packages
2) Rawhide status update
        - how do we look for F18?
        - problem packages
3) ARM Koji status update
        - Update on latest downtime
4) Your topic here

If you have any other items you would like to discuss that are not mentioned, please feel free to send an email to the list or bring it up at the end of the meeting.

Paul

Re: Stop the git abuse

Jesse Keating — 2012-05-22T23:12:33

I bet if you traced it, the majority of time is waiting for rpm to 
return queries about the spec file.

--
jlk

Re: changelog in spec file, was Re: Stop the git abuse

Przemek Klosowski — 2012-05-22T20:56:56

+1

It's great that CVS vulnerability numbers patched by each release are 
mentioned in the changelog. Tracking it is a common requirement in many 
environments, and rpm -q --changelog provides a very nice way to find 
out about it.

In fact, is that a policy or just something nice that people do? if the 
latter, could we consider adopting it officially?

Re: Replacing libusb1 with libusbx

Hans de Goede — 2012-05-22T16:23:35

Hi,

On 05/22/2012 02:55 PM, Bastien Nocera wrote:

No, Daniel handed it over to Peter Stuge about 18 months ago (give or
take), and that didn't work out to well. I (and others) have tried pretty
much every everything to avoid having to fork, but to no result.

Regards,

Hans

Re: Stop the git abuse

Dennis Gilmore — 2012-05-22T16:14:37

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 21 May 2012 09:50:53 -0700
Jesse Keating <jkeating< at >redhat.com> wrote:


cvs.fedoraproject.org has been shut down for quite awhile now. we do
have the cvs trees archived but you need to file a ticket with
infrastructure to get access.


Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAk+7u3MACgkQkSxm47BaWfdqYgCgtifyFuky1+ALMh8B1bctyMgq
NDIAnAsUSJ2sqlMiKs5rXqRSjUTdzGEu
=82fG
-----END PGP SIGNATURE-----

Re: [announce] yum: parallel downloading

James Antill — 2012-05-22T15:27:57

 Do _any_ web browsers have a connection limit lower than 4? Given that
and that we obey the max connections limit of the user and that in the
metalink ... it seems pretty alarmist to say 3 is too many to a single
server.


 You can open an RFE in bugzilla, and we could look at it if it's really
useful information ... one problem though is that we combine all
bareurls+mirrors, and move between them at the urlgrabber layer. So we
couldn't easily just change something on the yum side.

Re: [announce] yum: parallel downloading

Zdenek Pavlas — 2012-05-22T14:18:49

It does, indeed. Parallel downloader tries to use keepalives, too.
(we cache and reuse the last idle process instead of closing it)


/me just checked with tcpflow that we really do.
Please, contact me off-list if you can reproduce it. Thanks!

Re: Stop the git abuse

David Cantrell — 2012-05-22T14:10:31

Yeah, that is a nice workflow for package management in
pkgs.fedoraproject.org for things that we [the Fedora project] are not also
the upstream for.  For the anaconda case, we're sort of unique in that we
don't make releases and post them anywhere.  The .tar.bz2 files end up in
SRPMs only.  So for us, we go to great lengths to avoid patches in
pkgs.fedoraproject.org.  If we have to make changes, that's a new release.
The anaconda SRPM should only ever contain a spec file and tarball from us.
Downstream consumers will probably put patches in there though.

Re: Stop the git abuse

Greg Swift — 2012-05-22T13:55:18

which fits within the definition I stated. okay.. np


So I recently helped bring python-augeas into EPEL.  Before that (for
the last 2+ years) the spec file supported RHEL conditionals and many
of the python-augeas users did local builds of the fedora package in
their RHEL environment.

Just because a package has not gotten an EPEL maintainer yet, doesn't
mean the package doesn't support RHEL.

The zabbix package is in EPEL.  On RHEL 5 that means it is in the 1.4
branch due to the update policies.  The Fedora package had gone
through 1.6 and 1.8 releases before RHEL6 came out, none of which are
in epel-testing. Myself and many others built our updated packages off
the fedora package. I know there are several other packages that fall
into this category.  So what would happen in those scenarios?

I realize that at some threshold maintaining too many conditionals can
make a spec very difficult to work with, but for very simple and
limited conditionals the same could be said of having multiple spec
files.  I'd

Re: [announce] yum: parallel downloading

Matt Domsch — 2012-05-22T13:36:17

That's MirrorManager's doing.  I don't have a box for mirror admins to
tell MM otherwise - that they'd be happy with >1 connection.  I
suppose that could be added, default to 1.


I'd be happy if yum/urlgrabber/libcurl finally used http keepalives.
Last time I looked (and it has been a while), it didn't, so you always
paid the TCP slow startup penalty for each package.