November 2012 - devel - Fedora Mailing-Lists

raising warning flag on firewalld-default feature

by Matthew Miller

https://fedoraproject.org/wiki/Features/firewalld-default We have an accepted feature for Firewalld to be the default in Fedora 18. The old scripts are primitive and can't handle dynamic environments very well, so having something new and modern is admirable. The lokkit family of GUI config tools is primative enough to be considered dangerous. And a lot of integration work has been done in NetworkManager, libvirt, and a bunch of other places. But, I think we should strongly consider pushing this to F19, because: - this turns out to be a big change! - there's little to no documentation - the UI is very confusing, with a large number of "zones" and no apparent way to configure those zones - toolset is not yet robust -- has funny things like `firewall-cmd --enable` enables *panic mode*. - no way to run once and exit for cloud guests with *non-dynamic* firewall needs, and it's a non-trivial user of system resources The alternative is to enable it by default in some cases but not in others, but I think that's just confusing. We should wait until it's ready and then turn it on everywhere. I think this bug is illustrative of the problems we're going to see if we ship as-is: <https://bugzilla.redhat.com/show_bug.cgi?id=869625>. Stef isn't trying to anything crazy, but is both foiled by the lack of options and confused by the choices that are there. We're going to get a lot more bugs like this, and worse, unhappy users. The lack of documentation is really the showstopper here. If we had really good 1) hand-holding documentation and 2) technical documentation for admins, I'd be more willing to take the risk. (In an even more ideal world, the UI would be so well designed that the hand-holding documentation wouldn't be necessary.) -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>

11 years, 5 months

30
84
0 / 0

[Test-Announce] 2012-11-29 @ 17:00 UTC - F18 Final Blocker Bug Review #1.1

by Tim Flink

# F18 Final Blocker Review meeting #1.1 # Date: 2012-11-29 # Time: 17:00 UTC (12:00 EST, 09:00 PST) # Location: #fedora-qa on irc.freenode.net We ended up not having enough people to go ahead with the blocker review meeting earlier today, so we adjourned and will start again tomorrow (2012-11-29). We'll be running through the beta blockers and nice-to-haves. The current list of blocker bugs is available at: http://qa.fedoraproject.org/blockerbugs/current We'll be reviewing the bugs to determine ... 1. Whether they meet the final release criteria [1] and should stay on the list 2. Whether they are getting the attention they need [1] http://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria For guidance on Blocker and Nice-to-have (NTH) bugs, please refer to - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_nth_bug_process For the blocker review meeting protocol, see - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting _______________________________________________ test-announce mailing list test-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce

11 years, 5 months

1
0
0 / 0

F-18 Branched report: 20121128 changes

by Fedora compose checker

Compose started at Wed Nov 28 09:15:37 UTC 2012 Broken deps for x86_64 ---------------------------------------------------------- [dhcp-forwarder] dhcp-forwarder-upstart-0.10-1801.fc18.noarch requires /sbin/initctl [fedora-jam-kde-theme] fedora-jam-kde-theme-1.0.1-1.fc18.noarch requires kfaenza-icon-theme [gcc-python-plugin] gcc-python2-debug-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python2-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python3-debug-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 gcc-python3-plugin-0.9-6.fc18.x86_64 requires gcc = 0:4.7.2-3.fc18 [znc-infobot] znc-infobot-0.206-2.fc18.x86_64 requires znc = 0:0.206 Broken deps for i386 ---------------------------------------------------------- [dhcp-forwarder] dhcp-forwarder-upstart-0.10-1801.fc18.noarch requires /sbin/initctl [fedora-jam-kde-theme] fedora-jam-kde-theme-1.0.1-1.fc18.noarch requires kfaenza-icon-theme [gcc-python-plugin] gcc-python2-debug-plugin-0.9-6.fc18.i686 requires gcc = 0:4.7.2-3.fc18 gcc-python2-plugin-0.9-6.fc18.i686 requires gcc = 0:4.7.2-3.fc18 gcc-python3-debug-plugin-0.9-6.fc18.i686 requires gcc = 0:4.7.2-3.fc18 gcc-python3-plugin-0.9-6.fc18.i686 requires gcc = 0:4.7.2-3.fc18 [znc-infobot] znc-infobot-0.206-2.fc18.i686 requires znc = 0:0.206 Removed package: mod_pubcookie-3.3.4a-7.fc18 Summary: Added Packages: 0 Removed Packages: 1 Upgraded Packages: 0 Compose finished at Wed Nov 28 13:33:52 UTC 2012

11 years, 5 months

3
2
0 / 0

Re: [fedora-java] broken compatibility from jna-3.4.0 to 3.5.0

by Stanislav Ochotnicky

Quoting Ismael Olea (2012-11-27 16:24:26) > > We have seen such problems many times in many packages. Usually adding a > > dummy method just to satisfy the signature is enough though in this case it > > might not be. > > > > I see. > > > > Please report it to svnkit developers too. > > > > Done: http://issues.tmatesoft.com/issue/SVNKIT-329 Ccing devel so that audience is bigger (I believe this deserves it) Just for future reference. What you have written in upstream bugreport is basically: "I have tried to build your software in unsupported way (ant vs gradle) and used different versions of your dependencies and it failed. I've done it because other project has some silly rules. Can you fix it?". Upstream might or might not realize what you are asking for is a simple dependency bump with API fix (most likely). And they can get annoyed by your request (some upstreams definitely would). To be precise, this situation is not a bug in upstream at all, but it is caused by us (Fedora as a distribution). Therefore it's more of a RFE as far as upstream is concerned. RFEs written as bugreports can be hard to sell. This is not just for your benefit. I've seen several such bugreports from Fedora contributors. They can sometimes make dealing with upstreams difficult, so please be careful with the wording. -- Stanislav Ochotnicky <sochotnicky(a)redhat.com> Software Engineer - Base Operating Systems Brno PGP: 7B087241 Red Hat Inc. http://cz.redhat.com

11 years, 5 months

1
0
0 / 0

Schedule for Wednesday's FESCo Meeting (2012-11-28)

by Miloslav Trmač

Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 17:00UTC (1:00pm EDT, 19:00 CEST) in #fedora-meeting on irc.freenode.net. Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #966 Fedora 19 Schedule proposal (DRAFT!) .fesco 966 https://fedorahosted.org/fesco/ticket/966 = New business = #topic #974 Allow releases on Wed and Thu as well .fesco 974 https://fedorahosted.org/fesco/ticket/974 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 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/fesco, 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.

11 years, 5 months

1
1
0 / 0

[Test-Announce] 2012-11-28 @ 17:00 UTC - F18 Final Blocker Bug Review #1

by Tim Flink

# F18 Final Blocker Review meeting #1 # Date: 2012-11-28 # Time: 17:00 UTC (12:00 EST, 09:00 PST) # Location: #fedora-qa on irc.freenode.net I know everyone's excited for the next round of blocker review but there are already quite a few proposed blocker and nth bugs on the list and we have to get started sometime. Keeping with the beta blocker review meetings, we'll cap the meeting length at 3 hours and probably continue on 2012-11-29 if the meeting lasts that long. We'll be running through the beta blockers and nice-to-haves. The current list of blocker bugs is available at: http://qa.fedoraproject.org/blockerbugs/current We'll be reviewing the bugs to determine ... 1. Whether they meet the final release criteria [1] and should stay on the list 2. Whether they are getting the attention they need [1] http://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria For guidance on Blocker and Nice-to-have (NTH) bugs, please refer to - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_nth_bug_process For the blocker review meeting protocol, see - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting _______________________________________________ test-announce mailing list test-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce

11 years, 5 months

1
0
0 / 0

Re: need help with a package

by Jon VanAlten

----- Original Message ----- > From: "Alexander Aristotle Davis" <aadavis1(a)myseneca.ca> > To: "Development discussions related to Fedora" <devel(a)lists.fedoraproject.org> > Cc: "jon vanalten" <jon.vanalten(a)redhat.com> > Sent: Tuesday, November 27, 2012 5:58:27 AM > Subject: RE: need help with a package > > hello Jon, > > thanks for responding to my email, > > I will like to keep the package alive. > > > I am already a member of FAS2, I am having trouble taking over the > package can you guide me on the steps necessary to take ownership of > the package > I have made changes to the release when I first download the package. > The package original version and release is 2.3.3-2 and the new > version and release is 2.3.3-3. > Hi Alex, As I tried to communicate in prior email, a first step to taking ownership of a package in Fedora is to become part of the packagers group. I included a link to how that process works. RE: keeping the package alive, again from the sounds of things the security bug will need to be fixed. Note that in the security bug it is already said that if nobody is able to do that, the package should be removed from fedora/epel. Bumping the release in the package without making meaningful change to the package is not incredibly helpful. Besides, from what I can see in git there already exists a -3 release in all active branches, it's actually up to -4 in f18 and rawhide. I wonder what sources you started from, since it seems like you have most of the same spec as in git, but missing most of the changelog. Please spend some time on the wiki[1], I think most of the questions you have are answered. Giving you a short cut easy step by step answer on the mailing list will only keep you from actually learning the tools and policies that are necessary for fedora contributors. The wiki is there to (hopefully) answer any questions a new contributor might have. If you've gone through the stuff there, and the picture is still not clear, please do come back to list with questions :) cheers, jon [1] https://fedoraproject.org/wiki/Category:Package_Maintainers

11 years, 5 months

1
0
0 / 0

Orphaning many packages

by Jesse Keating

Since I'll no longer need these for my day job I'm going to orphan them rather than neglect them. Free for the taking! GitPython (dgoodwin is a co-maintainer) pexpect (only EPEL 6) python-ctypes (only EPEL 5) python-nss (only EPEL 5) python-offtrac sigul (mitr is a co-maintainer) -- Help me fight child abuse: http://tinyurl.com/jlkcourage - jlk

11 years, 5 months

4
5
0 / 0

FESCo townhall: November 27

by Ankur Sinha

Hi folks, The logs from the FESCo townhall are below. Please do take time out to go through them if you missed the townhall: http://meetbot.fedoraproject.org/fedora-townhall/2012-11-27/fesco-townhal... http://meetbot.fedoraproject.org/fedora-townhall/2012-11-27/fesco-townhal... http://meetbot.fedoraproject.org/fedora-townhall/2012-11-27/fesco-townhal... -- Thanks, Warm regards, Ankur: "FranciscoD" Please only print if necessary. Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG http://fedoraproject.org/wiki/User:Ankursinha http://dodoincfedora.wordpress.com/

11 years, 5 months

1
0
0 / 0

Anything changed on rawhide builders recently? Can't build ladvd

by Tomasz Torcz

Hi, Today I tried to build ladvd 1.0.4 package for rawhide, but it failed with some strange message http://koji.fedoraproject.org/koji/getfile?taskID=4662562&name=build.log&... , which is pasted below. So I rolled back to 1.0.2 and it failed to build, too. It was building fine previously. Then I tried to build for F18, it was built succesfuly (although it packaging ultimately failed because of unrelated reason). So the question is: what's broken with rawhide builders? The message on rawhide builder is: #v+ libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -Wall -Werror -Wformat -Wformat-security -D_FORTIFY_SOURCE=2 -fno-delete-null-pointer-checks -fstack-protector -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 -mtune=atom -fasynchronous-unwind-tables -c child.c -fPIC -DPIC -o .libs/child.o In file included from cli.c:20:0: common.h:152:8: error: redefinition of 'struct sysinfo' In file included from /usr/include/linux/kernel.h:4:0, from /usr/include/linux/sysctl.h:25, from /usr/include/sys/sysctl.h:43, from common.h:50, from cli.c:20: /usr/include/linux/sysinfo.h:7:8: note: originally defined here make[2]: *** [cli.lo] Error 1 make[2]: *** Waiting for unfinished jobs.... In file included from child.c:20:0: common.h:152:8: error: redefinition of 'struct sysinfo' In file included from /usr/include/linux/kernel.h:4:0, from /usr/include/linux/sysctl.h:25, from /usr/include/sys/sysctl.h:43, from common.h:50, from child.c:20: /usr/include/linux/sysinfo.h:7:8: note: originally defined here make[2]: *** [child.lo] Error 1 In file included from util.c:20:0: common.h:152:8: error: redefinition of 'struct sysinfo' In file included from /usr/include/linux/kernel.h:4:0, from /usr/include/linux/sysctl.h:25, from /usr/include/sys/sysctl.h:43, from common.h:50, from util.c:20: /usr/include/linux/sysinfo.h:7:8: note: originally defined here In file included from master.c:20:0: common.h:152:8: error: redefinition of 'struct sysinfo' In file included from /usr/include/linux/kernel.h:4:0, from /usr/include/linux/sysctl.h:25, from /usr/include/sys/sysctl.h:43, from common.h:50, from master.c:20: /usr/include/linux/sysinfo.h:7:8: note: originally defined here make[2]: Leaving directory `/builddir/build/BUILD/ladvd-1.0.4/src' make[2]: *** [master.lo] Error 1 make[2]: *** [util.lo] Error 1 make[1]: *** [all] Error 2 make[1]: Leaving directory `/builddir/build/BUILD/ladvd-1.0.4/src' make: *** [all-recursive] Error 1 #v- -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. xmpp: zdzichubg(a)chrome.pl Your routes will be aggreggated. -- Alex Yuriev

11 years, 5 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel November 2012