Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
On Thu, Nov 15, 2012 at 3:23 AM, Kevin Kofler kevin.kof...@chello.at wrote: And what about the many system administrators using handwritten rules (see Harald Reindl's reply)? There is a --direct option that is supposed to provide a compatibility/escape mechanism with full iptables functionality (and mostly same syntax). Last release cycle it appeared to work; testing it with some demanding real-world scripts would be interesting. Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Heads up: rpm 4.11 alpha coming soon to rawhide near you
Now that FESCo accepted http://fedoraproject.org/wiki/Features/RPM4.11 for F19... (in what might well be a record time - less than a minute in the meeting from proposal to acceptance :) Rpm 4.11 alpha (or actually post-alpha snapshot to pull in a few accumulated fixes + enhancements) will be hitting rawhide shortly. There's no soname bump involved this time, so no rebuilds required. There's one thing that does affect nearly every package: new warnings about bogus spec changelog dates. The most common cause is the day name not matching the given date, such as: warning: bogus date in %changelog: Tue Jun 03 2009 Panu Matilainen pmati...@redhat.com - 4.7.0-5 Jun 03 2009 was Wednesday, not Tuesday, hence the warning. As rpm hasn't hasn't previously validated changelog dates make sense as a whole, nearly every spec has one or more of these mistakes. It's just a warning though and doesn't cause build failures. Other than that, chances are you wont notice much anything at all. Assuming all goes well that is. So its the usual drill: keep your eyes open on rawhide builds and report any new oddities found ASAP. I'm not expecting any major issues with this but you never really know. For further details see the draft release notes at http://rpm.org/wiki/Releases/4.11.0 - Panu - -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: remove polkit from core?
On Wed, Nov 14, 2012 at 07:34:22PM +, Jóhann B. Guðmundsson wrote: On 11/14/2012 07:33 PM, Richard W.M. Jones wrote: On Wed, Nov 14, 2012 at 09:44:55AM -0500, Gregory Maxwell wrote: On Wed, Nov 14, 2012 at 9:26 AM, Chris Adams cmad...@hiwaay.net wrote: Great - let's take something that people are using, remove that functionality, and not announce it! This is not cool; it represents one of my biggest frustrations with a bunch of the new and improved ways of doing things. You track down how to do something, it works for a few releases, and then it doesn't anymore with no notice. I don't mind this much in isolation— and to some extent its unavoidable if there is to be progress. I also have the experience and impression that Fedora often dismisses use cases in the 'long tail' as things that power users can get by twiddling some opaque config file or registry entry or hacking some bit of code— this happens more often the closer you get to the desktop, but believe its a culture which permeates the project more generally than that. In isolation this too would be occasionally frustrating but finite in baddness. The combination of the two— that anything non-stock is subject to constant and often undocumented breakage _and_ that many non nearly-universal use cases are too non-mainstream to consider supportable stock features really diminishes the value I receive from using a distribution at all. I was trying yesterday to formulate a question for the people running for FESCo along these lines; also what they thought about: https://news.ycombinator.com/item?id=4772133 However I wasn't able to formulate a snappy and non-carping question in time for the deadline. Still, I do believe it's something that FESCo (those elected and those standing for election) ought to address. Why are other OS and upstream decision/discussion int their regard fesco problem? Should not their focus be first and foremost on our own distribution and our own OS? No. I think it's important to behave well with the larger free software community, and that includes other Linux distros and *BSD. From a purely selfish point of view, it leads to larger numbers of users testing our software in more configurations [different platforms, with and without different combinations of software installed], which is more likely to reveal bugs. Anyway, I'd like to hear what FESCo members have to say about this, because it would strongly influence who I would vote for. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: rpm 4.11 alpha coming soon to rawhide near you
On Thu, Nov 15, 2012 at 10:28:49AM +0200, Panu Matilainen wrote: For further details see the draft release notes at http://rpm.org/wiki/Releases/4.11.0 Should we start changing %doc README COPYING to %doc README %license COPYING ? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: rpm 4.11 alpha coming soon to rawhide near you
On 11/15/2012 11:59 AM, Richard W.M. Jones wrote: On Thu, Nov 15, 2012 at 10:28:49AM +0200, Panu Matilainen wrote: For further details see the draft release notes at http://rpm.org/wiki/Releases/4.11.0 Should we start changing %doc README COPYING to %doc README %license COPYING ? Eventually yes, although that'd be up to FPC I guess. Not yet however: while the produced packages are compatible with all older rpm versions, the spec is not. As long as there's a chance we might (temporarily) have to revert back to 4.10, you dont want to introduce spec-level changes that would cause build-failures on the older version. - Panu - -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: rpm 4.11 alpha coming soon to rawhide near you
On Thursday, November 15, 2012 06:20 PM, Panu Matilainen wrote: On 11/15/2012 11:59 AM, Richard W.M. Jones wrote: On Thu, Nov 15, 2012 at 10:28:49AM +0200, Panu Matilainen wrote: For further details see the draft release notes at http://rpm.org/wiki/Releases/4.11.0 Should we start changing %doc README COPYING to %doc README %license COPYING ? Eventually yes, although that'd be up to FPC I guess. Not yet however: while the produced packages are compatible with all older rpm versions, the spec is not. As long as there's a chance we might (temporarily) have to revert back to 4.10, you dont want to introduce spec-level changes that would cause build-failures on the older version. Maybe redhat-rpm-config could define the %license macro to the same as %doc on Fedora19 ? -- Mathieu -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: rpm 4.11 alpha coming soon to rawhide near you
On 11/15/2012 12:21 PM, Mathieu Bridon wrote: On Thursday, November 15, 2012 06:20 PM, Panu Matilainen wrote: On 11/15/2012 11:59 AM, Richard W.M. Jones wrote: On Thu, Nov 15, 2012 at 10:28:49AM +0200, Panu Matilainen wrote: For further details see the draft release notes at http://rpm.org/wiki/Releases/4.11.0 Should we start changing %doc README COPYING to %doc README %license COPYING ? Eventually yes, although that'd be up to FPC I guess. Not yet however: while the produced packages are compatible with all older rpm versions, the spec is not. As long as there's a chance we might (temporarily) have to revert back to 4.10, you dont want to introduce spec-level changes that would cause build-failures on the older version. Maybe redhat-rpm-config could define the %license macro to the same as %doc on Fedora19 ? Unfortunately that wont work: %license is clobbered by License: tag in specs. It could be aliased to %doc with a tiny patch to librpmbuild, but patching is needed. - Panu - -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The GNOME 3.6.2 Megaupdate
On 11/13/2012 01:07 PM, Kalev Lember wrote: It's time for the last big GNOME update for F18 to bring bug fixes and translation updates to users! The update is now in Bodhi, thanks to everyone who pitched in with builds. https://admin.fedoraproject.org/updates/FEDORA-2012-18258 It missed the Beta freeze by two days, however. And I would think it's something worth including in the Beta release: it's the final planned 3.6.x release and as such, very close to the final package set. I think it would make sense to include this in the Beta release, so that we can shake out more issues during the Beta, and so that the changes between Beta-Final wouldn't be so large. There won't be any more GNOME megaupdates for F18. This is the ticket I've filed to ask QA to consider including this in the Beta release: https://bugzilla.redhat.com/show_bug.cgi?id=808378 Any help testing this and finding regressions is most welcome (and feedback/karma in Bodhi is always welcome as well)! -- Best regards, Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The GNOME 3.6.2 Megaupdate
On 11/15/2012 11:43 AM, Kalev Lember wrote: This is the ticket I've filed to ask QA to consider including this in the Beta release: https://bugzilla.redhat.com/show_bug.cgi?id=876922 (Sorry, messed up the bugzilla link in the original message.) -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-Inline-Files] Modernize the spec a bit
commit 7e3320b2fc52fcd430356adda5f50f319d3ea188
Author: Petr Šabata con...@redhat.com
Date: Thu Nov 15 11:54:58 2012 +0100
Modernize the spec a bit
perl-Inline-Files.spec | 19 ---
1 files changed, 12 insertions(+), 7 deletions(-)
---
diff --git a/perl-Inline-Files.spec b/perl-Inline-Files.spec
index b3c3910..a53982f 100644
--- a/perl-Inline-Files.spec
+++ b/perl-Inline-Files.spec
@@ -1,6 +1,6 @@
Name: perl-Inline-Files
Version:0.68
-Release:4%{?dist}
+Release:5%{?dist}
Summary:Allows for multiple inline files in a single perl file
Group: Development/Libraries
License:GPL+ or Artistic
@@ -13,10 +13,11 @@ BuildRequires: perl(Cwd)
BuildRequires: perl(Data::Dumper)
BuildRequires: perl(File::Copy)
BuildRequires: perl(Filter::Util::Call)
+BuildRequires: perl(lib)
BuildRequires: perl(Test)
BuildRequires: perl(Test::More)
Requires: perl(Data::Dumper)
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
%description
Inline::Files generalizes the notion of the `__DATA__' marker and the
@@ -29,14 +30,13 @@ chmod -R a-x demo/* README Changes lib/Inline/Files.pm \
lib/Inline/Files/Virtual.pm
%build
-%{__perl} Makefile.PL INSTALLDIRS=vendor
+perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
-make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
-find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} ';'
-find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null ';'
-chmod -R u+w $RPM_BUILD_ROOT/*
+make pure_install DESTDIR=%{buildroot}
+find %{buildroot} -type f -name .packlist -exec rm -f {} ';'
+chmod -R u+w %{buildroot}/*
%check
make test
@@ -47,6 +47,11 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Thu Nov 15 2012 Petr Šabata con...@redhat.com - 0.68-5
+- Modernize the spec a bit
+- Update the dep list
+- Drop command macros
+
* Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.68-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: LuaJIT - an alternative for current Python C bindings
On 11/15/2012 01:49 AM, Alek Paunov wrote: So, to me it seems natural joining all above together to start thinking for replacing the classic python C bindings with thin textual or bytecode(*) LuaJIT/FFI shims in benefit of things with great set of dependencies like Anaconda (thanks to lupa, Lua objects behaves like Python ones in Python). The result will be order of magnitude easier for maintenance (towards the APIs evolution) and faster code. LuaJIT is currently not available for our secondary architectures, so this would need fixing first. (not available meaning exactly that, there is no fallback to a slow C interpreter mode or something like that.) It's also not clear how significant the actual memory savings will be because some of the Lua OO frameworks have quite a bit of overhead. And the eventually arriving abrt plugin will bring some weight with it, too. This is nothing against Lua or LuaJIT. I just don't think that switching programming languages will magically reduce resource consumption. This has to be an explicit design goal, or else it is not likely to happen. I'm sure it's possible to write resource-conserving Python code, too. It's just the baseline overhead from the run-time system which is unavoidable, but that's fairly small for Python (apparently less than 2 MB of unshared RSS per process). -- Florian Weimer / Red Hat Product Security Team -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Heads up: rpm 4.11 alpha coming soon to rawhide near you
On 11/15/2012 12:20 PM, Panu Matilainen wrote: On 11/15/2012 11:59 AM, Richard W.M. Jones wrote: On Thu, Nov 15, 2012 at 10:28:49AM +0200, Panu Matilainen wrote: For further details see the draft release notes at http://rpm.org/wiki/Releases/4.11.0 Should we start changing %doc README COPYING to %doc README %license COPYING ? Eventually yes, although that'd be up to FPC I guess. Not yet however: while the produced packages are compatible with all older rpm versions, the spec is not. As long as there's a chance we might (temporarily) have to revert back to 4.10, you dont want to introduce spec-level changes that would cause build-failures on the older version. Oh and btw, the same goes for using %autosetup: please do test it locally [*] and report any issues you may find, but avoid using in Fedora specs just yet. The whole %autosetup thing is implemented with macros and should be easy to pull into older Fedora releases once any early bugs have been shaken out. [*] Her's a quickstart guide to using %autosetup: 1) Make sure all the patches are using same prefix level (eg -p1) 2) Replace %setup with %autosetup (all the same switches apply), add patch prefix level if needed with -pN 3) Eliminate all %patch directives from the spec %autosetup defaults to using plain old 'patch' for the automated patch application, add -S git|quilt|hg|bzr to experiment with the DVCS intergration. - Panu - -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
Le jeudi 15 novembre 2012 à 03:23 +0100, Kevin Kofler a écrit : iptables rules are a long-established cross- distribution interface Not really. For example, ubuntu use ufw, mandriva used shorewall. Debian offered several frontend, but IIRC, didn't use one by default. And I have worked as firewall admin and developper, and while netfilter is a impressive piece of work, this is more used as a framework than anything. For example, one of the client wrote a script with automated roolback in case of issue, and we ( my company ) wrote a tool to edit rules without having to reload the whole firewall ( cause waiting 1 minutes to see if you crashed the whole network is not fun the 10 first time ). -- Michael Scherer -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-DateTime-TimeZone] Add BR, filter duplicated requires.
commit 473337bb37698841ad212e69bb895004a7be69bd
Author: Marcela Mašláňová mmasl...@redhat.com
Date: Thu Nov 15 13:36:09 2012 +0100
Add BR, filter duplicated requires.
perl-DateTime-TimeZone.spec | 11 +--
1 files changed, 9 insertions(+), 2 deletions(-)
---
diff --git a/perl-DateTime-TimeZone.spec b/perl-DateTime-TimeZone.spec
index 1d54790..cd8e2fa 100644
--- a/perl-DateTime-TimeZone.spec
+++ b/perl-DateTime-TimeZone.spec
@@ -1,12 +1,14 @@
Name: perl-DateTime-TimeZone
Version:1.54
-Release:1%{?dist}
+Release:2%{?dist}
Summary:Time zone object base class and factory
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/DateTime-TimeZone/
Source0:
http://www.cpan.org/authors/id/D/DR/DROLSKY/DateTime-TimeZone-%{version}.tar.gz
BuildArch: noarch
+BuildRequires: perl(base)
+BuildRequires: perl(lib)
BuildRequires: perl(Class::Load)
BuildRequires: perl(Class::Singleton) = 1.03
BuildRequires: perl(constant)
@@ -17,9 +19,9 @@ BuildRequires: perl(File::Spec)
BuildRequires: perl(List::Util)
BuildRequires: perl(Params::Validate) = 0.72
BuildRequires: perl(parent)
-BuildRequires: perl(Pod::Man) = 1.14
BuildRequires: perl(Test::More) = 0.88
BuildRequires: perl(Test::Output)
+BuildRequires: perl(Storable)
# not automatically detected
Requires: perl(File::Compare)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
@@ -31,6 +33,8 @@ Requires: perl(:MODULE_COMPAT_%(eval `%{__perl}
-V:version`; echo $versi
%endif
%?perl_default_filter}
+%global __requires_exclude
%{__requires_exclude}|perl\\(Params::Validate\\)$|perl\\(Class::Singleton\\)$
+
%if 0%{?perl_bootstrap}
# avoid circular dependencies - DateTime strictly requires DateTime::TimeZone
%global __requires_exclude
%{?__requires_exclude:%__requires_exclude|}perl\\(DateTime\\)
@@ -75,6 +79,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Thu Nov 15 2012 Marcela Mašláňová mmasl...@redhat.com - 1.54-2
+- add BR, filter duplicated requires
+
* Tue Nov 13 2012 Petr Pisar ppi...@redhat.com - 1.54-1
- update to latest upstream version - Olson 2012j
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: [@core] working definition for the minimal package set
From: Lennart Poettering mzerq...@0pointer.de I think a good way to approach this is by looking for the interesting usecases for a minimal installation: A) Containers B) VMs C) Bare-Metal Servers D) Paranoid people (not relevant) E) Embedded (out of focus for Fedora) I don't believe embedded is out of focus for Fedora, I already have several hundred such systems, soon likely to scale into the thousands. It works quite well for this and I don't see any reason @core can't work to their benefit as well. -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: LuaJIT - an alternative for current Python C bindings
On Thu, Nov 15, 2012 at 12:18 PM, Florian Weimer fwei...@redhat.com wrote: On 11/15/2012 01:49 AM, Alek Paunov wrote: So, to me it seems natural joining all above together to start thinking for replacing the classic python C bindings with thin textual or bytecode(*) LuaJIT/FFI shims in benefit of things with great set of dependencies like Anaconda (thanks to lupa, Lua objects behaves like Python ones in Python). The result will be order of magnitude easier for maintenance (towards the APIs evolution) and faster code. LuaJIT is currently not available for our secondary architectures, so this would need fixing first. (not available meaning exactly that, there is no fallback to a slow C interpreter mode or something like that.) It's also not clear how significant the actual memory savings will be because some of the Lua OO frameworks have quite a bit of overhead. And the eventually arriving abrt plugin will bring some weight with it, too. This is nothing against Lua or LuaJIT. I just don't think that switching programming languages will magically reduce resource consumption. This has to be an explicit design goal, or else it is not likely to happen. I'm sure it's possible to write resource-conserving Python code, too. It's just the baseline overhead from the run-time system which is unavoidable, but that's fairly small for Python (apparently less than 2 MB of unshared RSS per process). Porting yum to python3 might be an easier task ... from the python 3.3 changelog [1]: The storage of Unicode strings now depends on the highest codepoint in the string: pure ASCII and Latin1 strings (U+-U+00FF) use 1 byte per codepoint; BMP strings (U+-U+) use 2 bytes per codepoint; non-BMP strings (U+1-U+10) use 4 bytes per codepoint. The net effect is that for most applications, memory usage of string storage should decrease significantly - especially compared to former wide unicode builds - as, in many cases, strings will be pure ASCII even in international contexts (because many strings store non-human language data, such as XML fragments, HTTP headers, JSON-encoded data, etc.). We also hope that it will, for the same reasons, increase CPU cache efficiency on non-trivial applications. The memory usage of Python 3.3 is two to three times smaller than Python 3.2, and a little bit better than Python 2.7, on a Django benchmark (see the PEP for details). [1] http://docs.python.org/3/whatsnew/3.3.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: LuaJIT - an alternative for current Python C bindings
On Thu, Nov 15, 2012 at 2:18 PM, drago01 drag...@gmail.com wrote: On Thu, Nov 15, 2012 at 12:18 PM, Florian Weimer fwei...@redhat.com wrote: On 11/15/2012 01:49 AM, Alek Paunov wrote: So, to me it seems natural joining all above together to start thinking for replacing the classic python C bindings with thin textual or bytecode(*) LuaJIT/FFI shims in benefit of things with great set of dependencies like Anaconda (thanks to lupa, Lua objects behaves like Python ones in Python). The result will be order of magnitude easier for maintenance (towards the APIs evolution) and faster code. LuaJIT is currently not available for our secondary architectures, so this would need fixing first. (not available meaning exactly that, there is no fallback to a slow C interpreter mode or something like that.) It's also not clear how significant the actual memory savings will be because some of the Lua OO frameworks have quite a bit of overhead. And the eventually arriving abrt plugin will bring some weight with it, too. This is nothing against Lua or LuaJIT. I just don't think that switching programming languages will magically reduce resource consumption. This has to be an explicit design goal, or else it is not likely to happen. I'm sure it's possible to write resource-conserving Python code, too. It's just the baseline overhead from the run-time system which is unavoidable, but that's fairly small for Python (apparently less than 2 MB of unshared RSS per process). Porting yum to python3 might be an easier task ... from the python 3.3 changelog [1]: The storage of Unicode strings now depends on the highest codepoint in the string: pure ASCII and Latin1 strings (U+-U+00FF) use 1 byte per codepoint; BMP strings (U+-U+) use 2 bytes per codepoint; non-BMP strings (U+1-U+10) use 4 bytes per codepoint. The net effect is that for most applications, memory usage of string storage should decrease significantly - especially compared to former wide unicode builds - as, in many cases, strings will be pure ASCII even in international contexts (because many strings store non-human language data, such as XML fragments, HTTP headers, JSON-encoded data, etc.). We also hope that it will, for the same reasons, increase CPU cache efficiency on non-trivial applications. The memory usage of Python 3.3 is two to three times smaller than Python 3.2, and a little bit better than Python 2.7, on a Django benchmark (see the PEP for details). [1] http://docs.python.org/3/whatsnew/3.3.html Oh seems like the large savings are just compared to python 3.2 ... so would not really help. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
From: Stephen John Smoogen smo...@gmail.com On 14 November 2012 17:19, Lennart Poettering mzerq...@0pointer.de wrote: Oh, I wasn't aware that this is solely about anaconda-based installs, sorry. Well actually I think the correct question here is.. is this about anaconda based installs which was my guess when reading through this. However it is an assumption.. which means I am probably as much an ass as an umption in it. How about images created with things such as livecd-tools? I don't know to what extent, if any, that anaconda is involved in those builds. Last time I checked, it did not appear to be so maybe this whole @core thing really is irrelevant to me. -- John Florian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: bodhi 0.9.3 deployed to production
Adam Williamson wrote: There seems to be a mania for CURRENTRELEASE lately. I don't know where it's coming from. Well, it used to be what we used in the beginnings of Fedora. It got changed to ERRATA because that makes a lot more sense. The policy clearly states ERRATA: https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#CLOSED Thanks for confirming this. I filed: https://fedorahosted.org/bodhi/ticket/704 Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[389-devel] Revised: please review ticket 394 - error deleting a specific userpassword
I thought unhashed userpassword was removed from the entry, but it still might be there, so I added back the code to remove it. Original Message Subject: [389-devel] please review ticket 394 - error deleting a specific userpassword Date: Wed, 14 Nov 2012 15:52:47 -0500 From: Mark Reynolds marey...@redhat.com Reply-To: 389 Directory server developer discussion. 389-de...@lists.fedoraproject.org To: 389 Directory server developer discussion. 389-de...@lists.fedoraproject.org https://fedorahosted.org/389/ticket/394 https://fedorahosted.org/389/attachment/ticket/394/0001-Ticket-394-modify-delete-userpassword.patch -- Mark Reynolds Red Hat, Inc mreyno...@redhat.com -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
[Bug 877015] perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers
Product: Security Response https://bugzilla.redhat.com/show_bug.cgi?id=877015 Jan Lieskovsky jlies...@redhat.com changed: What|Removed |Added CC||mmasl...@redhat.com, ||perl-devel@lists.fedoraproj ||ect.org -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 877015] perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers
Product: Security Response https://bugzilla.redhat.com/show_bug.cgi?id=877015 --- Comment #1 from Jan Lieskovsky jlies...@redhat.com --- This issue affects the versions of the perl-CGI package, as shipped with Fedora release of 16 and 17. Please schedule an update. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: raising warning flag on firewalld-default feature
On Thu, Nov 15, 2012 at 01:53:32AM +0100, Lennart Poettering wrote: In fact, all system bus services should be configured to defer activation to systemd, so that all services regardless how they are triggered are executed in the same clean execution environment, and can be manipulated with the same commands (systemctl stop/kill/restart/mask/...) as any other services. [...] It's really not that hard. I think it's a really good rule to make all low-level system daemons work that way, to keep things robust and resource usage minimal. I was looking for resources on systemd and dbus activation. I realized that the documentation here is very scarce -- there's this tutorial on just dbus activation http://raphael.slinckx.net/blog/documents/dbus-tutorial and our wiki page http://fedoraproject.org/wiki/Packaging:Systemd#DBus_activation, but it seems like it might make a nice systemd for Developers, if you feel inspired at any point. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 877015] perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers
Product: Security Response https://bugzilla.redhat.com/show_bug.cgi?id=877015 Jan Lieskovsky jlies...@redhat.com changed: What|Removed |Added Whiteboard|impact=moderate,public=2012 |impact=moderate,public=2012 |1112,reported=20121115,sour |1112,reported=20121115,sour |ce=internet,cvss2=2.6/AV:N/ |ce=internet,cvss2=2.6/AV:N/ |AC:H/Au:N/C:N/I:P/A:N,fedor |AC:H/Au:N/C:N/I:P/A:N,rhel- |a-all/perl-CGI=affected |5/perl=affected,rhel-6/perl ||=affected,fedora-all/perl-C ||GI=affected -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 877015] perl-CGI: Newline injection due to improper CRLF escaping in Set-Cookie and P3P headers
Product: Security Response https://bugzilla.redhat.com/show_bug.cgi?id=877015 --- Comment #3 from Jan Lieskovsky jlies...@redhat.com --- This issue affects the versions of the perl package, as shipped with Red Hat Enterprise Linux 5 and 6. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Added some missing build dependencies
commit afe37c043b4f2380e4d5679890cfa20e69b65907
Author: Petr Šabata con...@redhat.com
Date: Thu Nov 15 16:10:08 2012 +0100
Added some missing build dependencies
perl-IO-Socket-SSL.spec |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
---
diff --git a/perl-IO-Socket-SSL.spec b/perl-IO-Socket-SSL.spec
index 6e90503..cf0a371 100644
--- a/perl-IO-Socket-SSL.spec
+++ b/perl-IO-Socket-SSL.spec
@@ -1,6 +1,6 @@
Name: perl-IO-Socket-SSL
Version: 1.77
-Release: 1%{?dist}
+Release: 2%{?dist}
Summary: Perl library for transparent SSL
Group: Development/Libraries
License: GPL+ or Artistic
@@ -12,9 +12,13 @@ BuildRequires: perl(Carp)
BuildRequires: perl(constant)
BuildRequires: perl(Exporter)
BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(IO::Select)
BuildRequires: perl(IO::Socket)
+BuildRequires: perl(IO::Socket::INET)
BuildRequires: perl(Net::LibIDN)
BuildRequires: perl(Net::SSLeay) = 1.21
+BuildRequires: perl(Scalar::Util)
+BuildRequires: perl(Socket)
BuildRequires: procps
# Use IO::Socket::IP for IPv6 support where available, else IO::Socket::INET6
%if 0%{?fedora} 15 || 0%{?rhel} 6
@@ -61,6 +65,9 @@ rm -rf %{buildroot}
%{_mandir}/man3/IO::Socket::SSL.3pm*
%changelog
+* Thu Nov 15 2012 Petr Šabata con...@redhat.com - 1.77-2
+- Added some missing build dependencies
+
* Fri Oct 5 2012 Paul Howarth p...@city-fan.org - 1.77-1
- Update to 1.77
- support _update_peer for IPv6 too (CPAN RT#79916)
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: remove polkit from core?
On Wed, Nov 14, 2012 at 08:34:00PM -0500, Simo Sorce wrote: Also, creating individual groups for all the various privileged operations we have simply doesn't scale. This is a better argument. So, PK's usecase is a valid and an important one. You cannot replace that by Unix groups. Which is why it would be nice for it to at least have the option for a small, simple key-pair authority configuration format. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
fedora elections questions [Re: remove polkit from core?]
On Thu, Nov 15, 2012 at 09:43:41AM +, Richard W.M. Jones wrote: Anyway, I'd like to hear what FESCo members have to say about this, because it would strongly influence who I would vote for. Yeah, I too came up with a couple of questions I'd like to add to https://fedoraproject.org/wiki/F19_elections_questionnaire, but the question collection period is over. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
On Wed, Nov 14, 2012 at 10:03:36PM -0800, Adam Williamson wrote: Is there any reason those two can't be split up? Maybe @really-hard-core for the first, and @core for the second. ;-) That's basically what Kevin proposed several mails back, and I agree it seems like we have two broadly definable cases here rather than one. I think Bill Nottingham mentioned something similar too, although I don't want to put words into his mouth. I'm open to the possibility, but I think using default instead of mandatory for many packages in @core covers this distinction relatively well. Then we have @standard for the next level. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
On Thu, Nov 15, 2012 at 01:19:59AM +0100, Lennart Poettering wrote: For containers a yum group for usage with --installroot= is the only thing that matters. For this, is a group even necessary or useful? -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
On Thu, Nov 15, 2012 at 01:13:09AM +0100, Lennart Poettering wrote: Well, it would be weird that the minimal installation is actually not minimal at all, but the container installation is. That would be weird. But fortunately, it's @core, not @minimal. So we could easily have @minimal, @core, and @standard, each with different targets. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
On 11/12/2012 11:28 AM, Matthew Miller wrote: I see three basic options for the target: A) kernel + init system and we're done B) boot to yum (with network): a text-mode bootstrap environment on which other things can be added by hand (or by kickstart) C) a traditional Unix command line environment with the expected basic tools available To me, 'C' is too wide for two reasons. First, it's too open for continual debate, because different people might expect different tools. Second, it's I was just working on a VMWare ESXI hypervisor which basically is a minimal Linux install, including a kernel running their virtualization hosting environment, and a busybox session. I found that there is a shockingly large amount of functionality in that busybox: we needed some network diagnostic tools, and discovered that it includes nc/netcat and ssh, as well as the usual ping/traceroute/nslookup/etc. I don't know if that is what you're after, because busybox duplicates the functionality of individual packages (and may have some limitations in how well it duplicates, I'm sure). All the same, I would definitely consider including it---it's of course available as a Fedora package. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: raising warning flag on firewalld-default feature
On 2012-11-15, 15:06 GMT, Matthew Miller wrote: I was looking for resources on systemd and dbus activation. I realized that the documentation here is very scarce -- there's this tutorial on just dbus activation http://raphael.slinckx.net/blog/documents/dbus-tutorial and our wiki page http://fedoraproject.org/wiki/Packaging:Systemd#DBus_activation, but it seems like it might make a nice systemd for Developers, if you feel inspired at any point. There is a lot of stuff on Lennart’s blog http://0pointer.de/blog/ Matěj -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-IO-stringy] BuildRequire perl(lib)
commit cfb2b6537a3fa9c24b395230b4d6e73888492aaa
Author: Petr Šabata con...@redhat.com
Date: Thu Nov 15 17:05:00 2012 +0100
BuildRequire perl(lib)
perl-IO-stringy.spec |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
---
diff --git a/perl-IO-stringy.spec b/perl-IO-stringy.spec
index d88ee05..74e1fcd 100644
--- a/perl-IO-stringy.spec
+++ b/perl-IO-stringy.spec
@@ -1,7 +1,7 @@
Summary: I/O on in-core objects like strings and arrays for Perl
Name: perl-IO-stringy
Version: 2.110
-Release: 20%{?dist}
+Release: 21%{?dist}
License: GPL+ or Artistic
Group: Development/Libraries
URL: http://search.cpan.org/dist/IO-stringy/
@@ -14,6 +14,7 @@ BuildRequires:perl(ExtUtils::MakeMaker)
BuildRequires: perl(FileHandle)
BuildRequires: perl(IO::File)
BuildRequires: perl(IO::Handle)
+BuildRequires: perl(lib)
BuildRequires: perl(Symbol)
Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
@@ -63,6 +64,9 @@ rm -rf %{buildroot}
%{_mandir}/man3/IO::WrapTie.3pm*
%changelog
+* Thu Nov 15 2012 Petr Šabata con...@redhat.com - 2.110-21
+- BuildRequire perl(lib)
+
* Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 2.110-20
- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: fedora elections questions [Re: remove polkit from core?]
On Thu, Nov 15, 2012 at 9:19 AM, Matthew Miller mat...@fedoraproject.org wrote: On Thu, Nov 15, 2012 at 09:43:41AM +, Richard W.M. Jones wrote: Anyway, I'd like to hear what FESCo members have to say about this, because it would strongly influence who I would vote for. Yeah, I too came up with a couple of questions I'd like to add to https://fedoraproject.org/wiki/F19_elections_questionnaire, but the question collection period is over. There will be a townhall where you or a proxy can ask them as well. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: raising warning flag on firewalld-default feature
On Thu, Nov 15, 2012 at 04:15:25PM +0100, Matej Cepl wrote: I was looking for resources on systemd and dbus activation. I realized that the documentation here is very scarce -- there's this tutorial on just dbus activation http://raphael.slinckx.net/blog/documents/dbus-tutorial and our wiki page http://fedoraproject.org/wiki/Packaging:Systemd#DBus_activation, but it seems like it might make a nice systemd for Developers, if you feel inspired at any point. There is a lot of stuff on Lennart’s blog http://0pointer.de/blog/ There *is* a lot of stuff on Lennart's blog. But unless I missed something, none of the articles are about D-Bus activation. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
On Thu, Nov 15, 2012 at 10:59:26AM -0500, Przemek Klosowski wrote: I don't know if that is what you're after, because busybox duplicates the functionality of individual packages (and may have some limitations in how well it duplicates, I'm sure). All the same, I would definitely consider including it---it's of course available as a Fedora package. Well, this is part of what I mean by Fedora is not a tiny-linux distribution. It might be interesting to have a busybox-based spin, but I think that's a different thing. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
Am 15.11.2012 13:33, schrieb Michael Scherer: Le jeudi 15 novembre 2012 à 03:23 +0100, Kevin Kofler a écrit : iptables rules are a long-established cross- distribution interface Not really. For example, ubuntu use ufw, mandriva used shorewall. Debian offered several frontend, but IIRC, didn't use one by default and they ALL using iptables/netfilter so if you write a iptables.sh you get it run on ANY distribution and that was the point signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
On 11/15/2012 11:18 AM, Matthew Miller wrote: On Thu, Nov 15, 2012 at 10:59:26AM -0500, Przemek Klosowski wrote: I don't know if that is what you're after, because busybox duplicates the functionality of individual packages (and may have some limitations in how well it duplicates, I'm sure). All the same, I would definitely consider including it---it's of course available as a Fedora package. Well, this is part of what I mean by Fedora is not a tiny-linux distribution. It might be interesting to have a busybox-based spin, but I think that's a different thing. Since busybox package already exists, I think it makes sense to use it--not because we're doing some tiny-linux, but because why not, it's just 651 kB. Most packages we discussed here (openssh-clients, sendmail) are individually much larger than that. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
PKLA -- JavaScript
On 11/14/2012 01:07 AM, tim.laurid...@gmail.com wrote: http://davidz25.blogspot.dk/2012/06/authorization-rules-in-polkit.html http://www.freedesktop.org/software/polkit/docs/master/polkit.8.html I've just reviewed those pages, and it's certainly not obvious to me how I would go about porting a PKLA file. [libvirt Management Access] Identity=unix-group:wheel Action=org.libvirt.unix.manage ResultAny=no ResultInactive=no ResultActive=yes The latter page, in particular, reads like something written for an audience of developers, rather than system administrators. I'm sure that I can figure it out in time, but this seems like a terrible burden to put on system administrators, particularly those who are (sometimes proudly) averse to anything that smacks of programming. -- Ian Pilcher arequip...@gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
Once upon a time, Przemek Klosowski przemek.klosow...@nist.gov said: Since busybox package already exists, I think it makes sense to use it--not because we're doing some tiny-linux, but because why not, it's just 651 kB. Most packages we discussed here (openssh-clients, sendmail) are individually much larger than that. That's not a good reason to use busybox in a general install. It doesn't exactly duplicate the commands it offers, only a subset. -- Chris Adams cmad...@hiwaay.net Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
On Thu, Nov 15, 2012 at 11:31:52AM -0500, Przemek Klosowski wrote: Well, this is part of what I mean by Fedora is not a tiny-linux distribution. It might be interesting to have a busybox-based spin, but I think that's a different thing. Since busybox package already exists, I think it makes sense to use it--not because we're doing some tiny-linux, but because why not, it's just 651 kB. Most packages we discussed here (openssh-clients, sendmail) are individually much larger than that. We could just add the busybox binary, but doing that alone doesn't really get much. In order to be useful, you want links to the commands you want busybox to implement. And then, I suppose we'd want some way for those commands to automatically get out of the way when full-featured versions are installed (I guess install in an alternate dir with less priority in $PATH than /usr/bin/). But since not every command is a literal drop-in replacement for the full-featured Fedora versions, that could be confusing (and for scripts, buggy). -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: PKLA -- JavaScript
On Thu, Nov 15, 2012 at 5:37 PM, Ian Pilcher arequip...@gmail.com wrote:
I've just reviewed those pages, and it's certainly not obvious to me
how I would go about porting a PKLA file.
[libvirt Management Access]
Identity=unix-group:wheel
Action=org.libvirt.unix.manage
ResultAny=no
ResultInactive=no
ResultActive=yes
The latter page, in particular, reads like something written for an
audience of developers, rather than system administrators. I'm sure
that I can figure it out in time, but this seems like a terrible burden
to put on system administrators, particularly those who are (sometimes
proudly) averse to anything that smacks of programming.
the .rules file should look like this: and go into *
/usr/share/polkit-1/rules.d/ *
polkit.addRule(function(action, subject) {
if (action.id == org.libvirt.unix.manage
subject.isInGroup(wheel)) {
return polkit.Result.YES;;
}
});
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The GNOME 3.6.2 Megaupdate
On Thu, 2012-11-15 at 11:43 +0100, Kalev Lember wrote: On 11/13/2012 01:07 PM, Kalev Lember wrote: It's time for the last big GNOME update for F18 to bring bug fixes and translation updates to users! The update is now in Bodhi, thanks to everyone who pitched in with builds. https://admin.fedoraproject.org/updates/FEDORA-2012-18258 It missed the Beta freeze by two days, however. And I would think it's something worth including in the Beta release: it's the final planned 3.6.x release and as such, very close to the final package set. I think it would make sense to include this in the Beta release, so that we can shake out more issues during the Beta, and so that the changes between Beta-Final wouldn't be so large. There won't be any more GNOME megaupdates for F18. This is the ticket I've filed to ask QA to consider including this in the Beta release: https://bugzilla.redhat.com/show_bug.cgi?id=808378 Any help testing this and finding regressions is most welcome (and feedback/karma in Bodhi is always welcome as well)! It would really help our confidence in taking a big dump like this as NTH if people could test it out and file karma, indeed - so please do, if you have some time. Thanks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
On Thu, 2012-11-15 at 14:48 +0100, Reindl Harald wrote: Am 15.11.2012 13:33, schrieb Michael Scherer: Le jeudi 15 novembre 2012 à 03:23 +0100, Kevin Kofler a écrit : iptables rules are a long-established cross- distribution interface Not really. For example, ubuntu use ufw, mandriva used shorewall. Debian offered several frontend, but IIRC, didn't use one by default and they ALL using iptables/netfilter so if you write a iptables.sh you get it run on ANY distribution and that was the point Right. I hate to say it, but Harald is correct here: AFAIK, all those and other firewall configuration mechanisms were ultimately just UI/abstraction layers wrapped around iptables. They wrote iptables rules. firewalld is very different. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: PKLA -- JavaScript
On Thu, Nov 15, 2012 at 5:37 PM, Ian Pilcher arequip...@gmail.com wrote: [...] but this seems like a terrible burden to put on system administrators, particularly those who are (sometimes proudly) averse to anything that smacks of programming. Thus are by definition not system administrators. There are not supposed to be software developers but being able to deal with simple code (shell scripts?!) is part of a sysadmins jobs. So the solution would be fire him and hire a new one. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: PKLA -- JavaScript
Once upon a time, tim.laurid...@gmail.com tim.laurid...@gmail.com said: the .rules file should look like this: and go into * /usr/share/polkit-1/rules.d/ * System-local config belongs in /etc, not /usr. Is there a corresponding /etc path for rules? -- Chris Adams cmad...@hiwaay.net Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: bodhi 0.9.3 deployed to production
On Thu, Nov 15, 2012 at 05:52:23AM +0100, Kevin Kofler wrote: Luke Macken wrote: A new bugfix release of Bodhi has just been deployed to production. https://admin.fedoraproject.org/updates Bugs and enhancement requests can be filed here: http://bodhi.fedorahosted.org This seems to be closing bugs as CURRENTRELEASE rather than ERRATA now, is that intentional? If yes, why? This change slipped through the cracks when fixing a problem with closing bugs with python-bugzilla. https://fedorahosted.org/bodhi/changeset/0f2651f2095bc5952468d2eb0af39ecc077521e3/ I just changed it back to CLOSED-ERRATA in git. Thanks for the heads up, luke -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: PKLA -- JavaScript
On Thu, Nov 15, 2012 at 06:06:44PM +0100, drago01 wrote: Thus are by definition not system administrators. There are not supposed to be software developers but being able to deal with simple code (shell scripts?!) is part of a sysadmins jobs. So the solution would be fire him and hire a new one. Or better yet! Fire all the Linux people and hire much cheaper admins for an OS where you can configure everything by clicking on stuff. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: PKLA -- JavaScript
On Thu, Nov 15, 2012 at 11:09:07AM -0600, Chris Adams wrote: Once upon a time, tim.laurid...@gmail.com tim.laurid...@gmail.com said: the .rules file should look like this: and go into * /usr/share/polkit-1/rules.d/ * System-local config belongs in /etc, not /usr. Is there a corresponding /etc path for rules? We went through this with the old version too: http://lists.freedesktop.org/archives/polkit-devel/2009-November/000258.html -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: PKLA -- JavaScript
On Thu, 15 Nov 2012 12:09:53 -0500 Matthew Miller mat...@fedoraproject.org wrote: On Thu, Nov 15, 2012 at 06:06:44PM +0100, drago01 wrote: Thus are by definition not system administrators. There are not supposed to be software developers but being able to deal with simple code (shell scripts?!) is part of a sysadmins jobs. So the solution would be fire him and hire a new one. Or better yet! Fire all the Linux people and hire much cheaper admins for an OS where you can configure everything by clicking on stuff. but you need 10 times as many clickies. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
Am 15.11.2012 18:06, schrieb Adam Williamson: On Thu, 2012-11-15 at 14:48 +0100, Reindl Harald wrote: Am 15.11.2012 13:33, schrieb Michael Scherer: Not really. For example, ubuntu use ufw, mandriva used shorewall. Debian offered several frontend, but IIRC, didn't use one by default and they ALL using iptables/netfilter so if you write a iptables.sh you get it run on ANY distribution and that was the point Right. I hate to say it, but Harald is correct here: AFAIK, all those and other firewall configuration mechanisms were ultimately just UI/abstraction layers wrapped around iptables. They wrote iptables rules. firewalld is very different. and that is why i hardly hope iptables.service will be available parallel to firewalld because both satisfy different needs * firewalld: desktops, standard-setups * iptables: users maintaining since forever their rules per shellscripts i am one of the second groups and doing DISTRIBUTED iptables-configurations for whole infrastructures since many years and using here any capability of iptables which can be hardly covered with abstraction layers firewalld is helpful for most average users and a fine idea iptables.service is for the pople needing 100% control of each netfilter-rule and it would be a great fault to try include any capability in firewalld because it would be too complex to use and finally not satifsy both user groups if it supports any comination you can do with a script containing some hundret iptables-commands it would became overloaded for the average user while most likely my usage could still only be covered partly the only things i need are: * /usr/sbin/iptables * /sbin/iptables-save /etc/sysconfig/iptables * a service loading /etc/sysconfig/iptables at startup * not collide with firewalld or forced to use it if this is possible and firewalld is the default i am happy, my workload stays fine and firewalld satisfies other user-types - a perfect combination and a real improvement at all signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The GNOME 3.6.2 Megaupdate
Dne 15.11.2012 18:04, Adam Williamson napsal(a): On Thu, 2012-11-15 at 11:43 +0100, Kalev Lember wrote: On 11/13/2012 01:07 PM, Kalev Lember wrote: It's time for the last big GNOME update for F18 to bring bug fixes and translation updates to users! The update is now in Bodhi, thanks to everyone who pitched in with builds. https://admin.fedoraproject.org/updates/FEDORA-2012-18258 It missed the Beta freeze by two days, however. And I would think it's something worth including in the Beta release: it's the final planned 3.6.x release and as such, very close to the final package set. I think it would make sense to include this in the Beta release, so that we can shake out more issues during the Beta, and so that the changes between Beta-Final wouldn't be so large. There won't be any more GNOME megaupdates for F18. This is the ticket I've filed to ask QA to consider including this in the Beta release: https://bugzilla.redhat.com/show_bug.cgi?id=808378 Any help testing this and finding regressions is most welcome (and feedback/karma in Bodhi is always welcome as well)! It would really help our confidence in taking a big dump like this as NTH if people could test it out and file karma, indeed - so please do, if you have some time. Thanks. I wish it would be installable as a single update. If bodhi could compose the yum install command for copy paste at least, it might be helpful as well. Vit -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The GNOME 3.6.2 Megaupdate
Dne 15.11.2012 18:45, Vít Ondruch napsal(a): Dne 15.11.2012 18:04, Adam Williamson napsal(a): On Thu, 2012-11-15 at 11:43 +0100, Kalev Lember wrote: On 11/13/2012 01:07 PM, Kalev Lember wrote: It's time for the last big GNOME update for F18 to bring bug fixes and translation updates to users! The update is now in Bodhi, thanks to everyone who pitched in with builds. https://admin.fedoraproject.org/updates/FEDORA-2012-18258 It missed the Beta freeze by two days, however. And I would think it's something worth including in the Beta release: it's the final planned 3.6.x release and as such, very close to the final package set. I think it would make sense to include this in the Beta release, so that we can shake out more issues during the Beta, and so that the changes between Beta-Final wouldn't be so large. There won't be any more GNOME megaupdates for F18. This is the ticket I've filed to ask QA to consider including this in the Beta release: https://bugzilla.redhat.com/show_bug.cgi?id=808378 Any help testing this and finding regressions is most welcome (and feedback/karma in Bodhi is always welcome as well)! It would really help our confidence in taking a big dump like this as NTH if people could test it out and file karma, indeed - so please do, if you have some time. Thanks. I wish it would be installable as a single update. If bodhi could compose the yum install command for copy paste at least, it might be helpful as well. Vit 'yum update' actually, but you get the point ;) Vit -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The GNOME 3.6.2 Megaupdate
On Thu, 15 Nov 2012 18:49:50 +0100 Vít Ondruch vondr...@redhat.com wrote: Dne 15.11.2012 18:45, Vít Ondruch napsal(a): ...snip... I wish it would be installable as a single update. If bodhi could compose the yum install command for copy paste at least, it might be helpful as well. 'yum update' actually, but you get the point ;) bodhi -D FEDORA-2012-18258 will download all packages in that update for you. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: PKLA -- JavaScript
On Thu, Nov 15, 2012 at 6:10 PM, Matthew Miller mat...@fedoraproject.org wrote: On Thu, Nov 15, 2012 at 11:09:07AM -0600, Chris Adams wrote: Once upon a time, tim.laurid...@gmail.com tim.laurid...@gmail.com said: the .rules file should look like this: and go into * /usr/share/polkit-1/rules.d/ * System-local config belongs in /etc, not /usr. Is there a corresponding /etc path for rules? We went through this with the old version too: http://lists.freedesktop.org/archives/polkit-devel/2009-November/000258.html Yeah, except this time there is also /etc/polkit-1/rules.d, so call of the alarm :) Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
On Thu, Nov 15, 2012 at 6:16 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 15.11.2012 18:06, schrieb Adam Williamson: Right. I hate to say it, but Harald is correct here: AFAIK, all those and other firewall configuration mechanisms were ultimately just UI/abstraction layers wrapped around iptables. They wrote iptables rules. firewalld is very different. (Side-reply to Adam:) I can't see the difference; /sbin/iptables still works if you have firewalld running. i am one of the second groups and doing DISTRIBUTED iptables-configurations for whole infrastructures since many years and using here any capability of iptables which can be hardly covered with abstraction layers It would be very helpful for judging the maturity/suitability of firewalld if you could try converting your iptables script to firewall-cmd --direct (which, at least I hope, should be possible to do with a few sed commands), and report back whether the pass-through capability is good enough. Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The GNOME 3.6.2 Megaupdate
On Thu, 2012-11-15 at 10:57 -0700, Kevin Fenzi wrote: On Thu, 15 Nov 2012 18:49:50 +0100 Vít Ondruch vondr...@redhat.com wrote: Dne 15.11.2012 18:45, Vít Ondruch napsal(a): ...snip... I wish it would be installable as a single update. If bodhi could compose the yum install command for copy paste at least, it might be helpful as well. 'yum update' actually, but you get the point ;) bodhi -D FEDORA-2012-18258 will download all packages in that update for you. Right. What I do is have a little side repo: [root@adam live]# cat /etc/yum.repos.d/side.repo [side] name=Private side repo baseurl=file:///home/adamw/local/repo/$basearch enabled=1 metadata_expire=30 gpgcheck=0 So I can go to ~/local/repo/x86_64, do 'bodhi -D FEDORA-2012-18258', 'createrepo .', 'sudo yum update'. Pretty straightforward once you get used to it, and it's handy to have stuff you're forcing in in an actual repository. Note the metadata_expire line, which sets the repo's metadata to expire in 30 seconds, so it's pretty much always fresh (there's about zero time penalty for getting the metadata from a small local disk side repo like this, so you may as well). Note that if you want to pull something from koji that isn't yet in bodhi, you can do 'koji download-build --arch=noarch --arch=x86_64 buildid' to get all the binary packages from the build at once. (change to i686 if you're 32-bit, obviously). Oh, and while we're on the 'neat bodhi tricks' subject, if you're running x86_64 but you need to pull down the 32-bit builds of a Bodhi update (for building a live image or something), 'linux32 bodhi -D' will DTRT. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[389-devel] please review ticket 507 - use mutex for FrontendConfig lock instead of rwlock
https://fedorahosted.org/389/ticket/507 https://fedorahosted.org/389/attachment/ticket/507/0001-Ticket-507-use-mutex-for-FrontendConfig-lock-instead.patch -- Mark Reynolds Red Hat, Inc mreyno...@redhat.com -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
On Thu, 2012-11-15 at 19:02 +0100, Miloslav Trmač wrote: On Thu, Nov 15, 2012 at 6:16 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 15.11.2012 18:06, schrieb Adam Williamson: Right. I hate to say it, but Harald is correct here: AFAIK, all those and other firewall configuration mechanisms were ultimately just UI/abstraction layers wrapped around iptables. They wrote iptables rules. firewalld is very different. (Side-reply to Adam:) I can't see the difference; /sbin/iptables still works if you have firewalld running. Sure, but the background here was the 'replace vs. augment' question - is firewalld actually planned to replace iptables in the long run, or are we committed to maintaining iptables as an alternative mechanism? It sounds like harald would be happy if the latter is the case. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
On Thu, Nov 15, 2012 at 7:10 PM, Adam Williamson awill...@redhat.com wrote: On Thu, 2012-11-15 at 19:02 +0100, Miloslav Trmač wrote: On Thu, Nov 15, 2012 at 6:16 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 15.11.2012 18:06, schrieb Adam Williamson: Right. I hate to say it, but Harald is correct here: AFAIK, all those and other firewall configuration mechanisms were ultimately just UI/abstraction layers wrapped around iptables. They wrote iptables rules. firewalld is very different. (Side-reply to Adam:) I can't see the difference; /sbin/iptables still works if you have firewalld running. Sure, but the background here was the 'replace vs. augment' question - is firewalld actually planned to replace iptables in the long run, or are we committed to maintaining iptables as an alternative mechanism? It sounds like harald would be happy if the latter is the case. (as far as I understand the situation:) iptables as a kernel interface and a low-level command will exist, but applications will expect the existence of the firewalld D-Bus service (as opposed to the system-config-firewall D-Bus service, at least; I'm not sure what this implies about systems where the firewalld D-Bus service is not available), and firewall-cmd, not iptables, will be the recommended user tool. In fact, not applications will expect..., but applications already expect - this is already the case with anaconda, control-center and perhaps other applications. Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
On Thu, Nov 15, 2012 at 10:10:43AM -0800, Adam Williamson wrote: Sure, but the background here was the 'replace vs. augment' question - is firewalld actually planned to replace iptables in the long run, or are we committed to maintaining iptables as an alternative mechanism? It sounds like harald would be happy if the latter is the case. One approach: firewalld could have a direct-only mode. If that mode were enabled, it'd load a static script from from /etc/sysconfig/iptables on launch, and respond to any commands other than the direct api with an in direct-only mode error. Then, firewalld-aware applications could choose to raise a user error or to go to whatever fallback they have. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
Am 15.11.2012 19:02, schrieb Miloslav Trmač: On Thu, Nov 15, 2012 at 6:16 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 15.11.2012 18:06, schrieb Adam Williamson: Right. I hate to say it, but Harald is correct here: AFAIK, all those and other firewall configuration mechanisms were ultimately just UI/abstraction layers wrapped around iptables. They wrote iptables rules. firewalld is very different. (Side-reply to Adam:) I can't see the difference; /sbin/iptables still works if you have firewalld running. i am one of the second groups and doing DISTRIBUTED iptables-configurations for whole infrastructures since many years and using here any capability of iptables which can be hardly covered with abstraction layers It would be very helpful for judging the maturity/suitability of firewalld if you could try converting your iptables script to firewall-cmd --direct (which, at least I hope, should be possible to do with a few sed commands), and report back whether the pass-through capability is good enough. you CAN NOT easily convert iptables.sh scripts containing hundrets of commands in a specific order which are well tested over years and your replacment for any hardware firewall/router this things are not written at once this things are growed, optimized and maintained over years this things are tested in zones where security is hardly needed it is a bad idea to touch them and re-test it all in production as you can IMPOSSIBLE build a infrastructure with tons of severs and clients with very specific block/reject/allow in a test environment without wasting hundrests of hours of your work and the main problem: this thinhs are working fine since forever you will have no benefit to convert them to something else it is one thing to develop new tools and abstraction layers a whole different story is throw away perfect workloads for nothing in the time we discuss this here someone could maintain iptables.service the next 20 years at all! signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: raising warning flag on firewalld-default feature
On Thu, 15.11.12 10:06, Matthew Miller (mat...@fedoraproject.org) wrote: On Thu, Nov 15, 2012 at 01:53:32AM +0100, Lennart Poettering wrote: In fact, all system bus services should be configured to defer activation to systemd, so that all services regardless how they are triggered are executed in the same clean execution environment, and can be manipulated with the same commands (systemctl stop/kill/restart/mask/...) as any other services. [...] It's really not that hard. I think it's a really good rule to make all low-level system daemons work that way, to keep things robust and resource usage minimal. I was looking for resources on systemd and dbus activation. I realized that the documentation here is very scarce -- there's this tutorial on just dbus activation http://raphael.slinckx.net/blog/documents/dbus-tutorial and our wiki page http://fedoraproject.org/wiki/Packaging:Systemd#DBus_activation, but it seems like it might make a nice systemd for Developers, if you feel inspired at any point. There's indeed not much documentation around. This is primarily because we were kinda waiting for kernel dbus to materialize which would probably shuffle a few things around in this area. Here's the gist of it: 1) In /usr/share/dbus-1/system-services/*.service use the SystemdService= setting to declare that activation of a specific D-Bus service should be done with systemd. 2) Basically, that's already it. However, here's a twist: instead of directly specifiying the systemd service file name I recommend specifying the name of a symlink which point to the actual service, and is available only if the service is actually enabled. Then, add Alias= for this symlink name to [Install] in the unit file. This way you can now enable/disable the service and this affects bus activation as administrators would expect. Here's an example for Avahi: In /usr/share/dbus-1/system-services/org.freedesktop.Avahi.service: [D-BUS Service] Name=org.freedesktop.Avahi SystemdService=dbus-org.freedesktop.Avahi.service And in /usr/lib/systemd/system/avahi-daemon.service: [Unit] Description=Avahi mDNS/DNS-SD Stack Requires=avahi-daemon.socket [Service] Type=dbus BusName=org.freedesktop.Avahi ExecStart=/usr/sbin/avahi-daemon -s ExecReload=/usr/sbin/avahi-daemon -r NotifyAccess=main [Install] WantedBy=multi-user.target Also=avahi-daemon.socket Alias=dbus-org.freedesktop.Avahi.service The important line here is the last, which has the effect that the symlink /etc/systemd/system/dbus-org.freedesktop.Avahi.service is managed by systemctl enable and systemctl disable so that the bus activation only works when avahi is actually enabled. Naming the symlinks dbus-xyz.service (with xyz being the actual bus name) is a just a recommendation, nothing is requiring that... Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
Am 15.11.2012 19:16, schrieb Miloslav Trmač: (as far as I understand the situation:) iptables as a kernel interface and a low-level command will exist, but applications will expect the existence of the firewalld D-Bus service (as opposed to the system-config-firewall D-Bus service, at least; I'm not sure what this implies about systems where the firewalld D-Bus service is not available), and firewall-cmd, not iptables, will be the recommended user tool and this is the reason why i say CAUTIOn i do not want nor can i accept anything on MY machines expect anything to deal with iptables-rules. i am the only on e instance to define what is open and closed and with which REJECT or DROP answer what is closed nobody and nothing has to touch this dynamically if a application needs a port open i am the one to open it and if not you can be sure there is a good reason why it stays closed - the reason is security and professional it-managment i am responsible for my data, comanies data and data of many customers so i have to be the instance to control every piece of software - on servers and static setups there is no need for dynmaic connifurations - the opposite is true: you need to disable and close ANYTHING and allow NOTHING where you are not 100% sure that you aware what is done these things will not change tomorrow nor in 20 years and the palces where they are changed you read regulary in the newspaper because intrusions and security leaks! signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
On Thu, Nov 15, 2012 at 7:08 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 15.11.2012 19:02, schrieb Miloslav Trmač: It would be very helpful for judging the maturity/suitability of firewalld if you could try converting your iptables script to firewall-cmd --direct (which, at least I hope, should be possible to do with a few sed commands), and report back whether the pass-through capability is good enough. you CAN NOT easily convert iptables.sh scripts containing hundrets of commands in a specific order which are well tested over years and your replacment for any hardware firewall/router Have you actually _tried_? It's supposed to be as easy as s/iptables/firewall-cmd --direct --passthrough ipv4/ I don't know for a fact whether it is good enough. You seem to have a script that could tell us. Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
Am 15.11.2012 19:27, schrieb Miloslav Trmač: On Thu, Nov 15, 2012 at 7:08 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 15.11.2012 19:02, schrieb Miloslav Trmač: It would be very helpful for judging the maturity/suitability of firewalld if you could try converting your iptables script to firewall-cmd --direct (which, at least I hope, should be possible to do with a few sed commands), and report back whether the pass-through capability is good enough. you CAN NOT easily convert iptables.sh scripts containing hundrets of commands in a specific order which are well tested over years and your replacment for any hardware firewall/router Have you actually _tried_? It's supposed to be as easy as s/iptables/firewall-cmd --direct --passthrough ipv4/ I don't know for a fact whether it is good enough. You seem to have a script that could tell us. i posted a script realier this day as .txt file with masked network details, but it did not go trough list moderation AFAIK until now signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
On Thu, 15 Nov 2012 19:30:27 +0100 Reindl Harald h.rei...@thelounge.net wrote: Am 15.11.2012 19:27, schrieb Miloslav Trmač: On Thu, Nov 15, 2012 at 7:08 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 15.11.2012 19:02, schrieb Miloslav Trmač: It would be very helpful for judging the maturity/suitability of firewalld if you could try converting your iptables script to firewall-cmd --direct (which, at least I hope, should be possible to do with a few sed commands), and report back whether the pass-through capability is good enough. you CAN NOT easily convert iptables.sh scripts containing hundrets of commands in a specific order which are well tested over years and your replacment for any hardware firewall/router Have you actually _tried_? It's supposed to be as easy as s/iptables/firewall-cmd --direct --passthrough ipv4/ I don't know for a fact whether it is good enough. You seem to have a script that could tell us. i posted a script realier this day as .txt file with masked network details, but it did not go trough list moderation AFAIK until now Everyone on this list doesn't need a copy of your (lengthy) iptables script, IMHO. Perhaps the two of you could continue this off line and test and report back to the list? kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The GNOME 3.6.2 Megaupdate
Vít Ondruch wrote: I wish it would be installable as a single update. If bodhi could compose the yum install command for copy paste at least, it might be helpful as well. Assuming you already have GNOME installed, these commands: yum install yum-security yum --enablerepo=updates-testing --advisory=FEDORA-2012-18258 update will update it to 3.6.2. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: LuaJIT - an alternative for current Python C bindings
Hi Florian, On 15.11.2012 13:18, Florian Weimer wrote: On 11/15/2012 01:49 AM, Alek Paunov wrote: So, to me it seems natural joining all above together to start thinking for replacing the classic python C bindings with thin textual or bytecode(*) LuaJIT/FFI shims in benefit of things with great set of dependencies like Anaconda (thanks to lupa, Lua objects behaves like Python ones in Python). The result will be order of magnitude easier for maintenance (towards the APIs evolution) and faster code. LuaJIT is currently not available for our secondary architectures, so this would need fixing first. (not available meaning exactly that, there is no fallback to a slow C interpreter mode or something like that.) Oh, I completely forgot the secondary architectures (besides ARM). Florian, you follow LuaJIT - what other architectures (except the clearly missing s390) should be covered ?. It's also not clear how significant the actual memory savings will be because some of the Lua OO frameworks have quite a bit of overhead. And the eventually arriving abrt plugin will bring some weight with it, too. This is nothing against Lua or LuaJIT. I just don't think that switching programming languages will magically reduce resource consumption. This has to be an explicit design goal, or else it is not likely to happen. I'm sure it's possible to write resource-conserving Python code, too. It's just the baseline overhead from the run-time system which is unavoidable, but that's fairly small for Python (apparently less than 2 MB of unshared RSS per process). Apparently, my pseudo-English is not enough for a normal communication :-(. I am commenting on the possibility for deploying LuaJIT FFI as a partial replacement (problematic + future) of the hand written or SWIG Python bindings in the first place, not switching the system language from Python to Lua. In a system tool/daemon written in Python: * Python loads libluajit.so (import lupa; from lupa import LuaRuntime; ...) * The C libraries (the targets of the binding) are described as LuaJIT FFI style bindings in simplified C [my primary point for that is correctness (avoiding the memory leaks and reference counting problems) and lowering the burden of the APIs evolution maintenance, not lowering the general memory footprint] * The current OO style Python wrappers (the higher level part of the classical C bindings) are implemented with the Lua metamethods over plain C objects (without any Lua OO frameworks) * Python calls the LuaJIT C lib object wrappers (as close as possible to the Python APIs exposed by the current bindings on top of the Python C API). Kind Regards, Alek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
Am 15.11.2012 19:37, schrieb Kevin Fenzi: Have you actually _tried_? It's supposed to be as easy as s/iptables/firewall-cmd --direct --passthrough ipv4/ I don't know for a fact whether it is good enough. You seem to have a script that could tell us. i posted a script realier this day as .txt file with masked network details, but it did not go trough list moderation AFAIK until now Everyone on this list doesn't need a copy of your (lengthy) iptables script, IMHO. Perhaps the two of you could continue this off line and test and report back to the list? your argumentation is NOT helpful i can NOT test a iptables.sh replace for a whole INFRASTRUCTURE i can NOT post a unmasked version with ip-addresses and hostnames i can NOT simulate a whole network with around 100 machines even i could do this all, it wozld be VERY difficult to RE-AUDIT the whole configuration and security-layers which are hardly to explain because usually infrastructure and network-segments you want to isolate in both directions is grwoing over years and not there at once and this is why REMOEV iptables.service would cause A LOT of work and auditing while you risk security troubles while you are at working on this for a more or less non existing benfit this is why it would be NOT a good idea to remove iptables.service some of this setups are hunderts of kilometers away the iptables.sh there is the ROUTER you can not test this remote because if you make a small mistake you have lost the game and the remote network is down and having everywhere lights-out-managment is a nice wish but in reality you do NOT want LOM exposed to the internet, so it is BEHIND this iptables-etups you play around REALLY: there is nothing more i can say to this topic it is not my decision if people drop iptables.service and make a big wasting of ressources and security while doing this all over the world - but people should keep in mind what damage they are doing if acting this way signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
On Thu, 2012-11-15 at 19:46 +0100, Reindl Harald wrote: Am 15.11.2012 19:37, schrieb Kevin Fenzi: Have you actually _tried_? It's supposed to be as easy as s/iptables/firewall-cmd --direct --passthrough ipv4/ I don't know for a fact whether it is good enough. You seem to have a script that could tell us. i posted a script realier this day as .txt file with masked network details, but it did not go trough list moderation AFAIK until now Everyone on this list doesn't need a copy of your (lengthy) iptables script, IMHO. Perhaps the two of you could continue this off line and test and report back to the list? your argumentation is NOT helpful i can NOT test a iptables.sh replace for a whole INFRASTRUCTURE i can NOT post a unmasked version with ip-addresses and hostnames i can NOT simulate a whole network with around 100 machines I don't think anyone asked you to do any of those things. Fedora obviously does not have the power to replace iptables with firewalld on your router, so the question is not 'can you replace iptables with firewalld on everything in your network and see if it works'. The question is more 'can you see if firewalld does a good job of imitating iptables on a single Fedora machine on your network, or a small amount of them'. The whole point is it should be able to imitate an iptables-type setup fairly transparently, so it should 'play nice' with the rest of your setup. Can't you just test that? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-Wx/f16] 0.9914 + more complete list of Provides
commit 37361aeae7d7d4eca39de9ec35ed6394ad00357b
Author: Tom Callaway s...@fedoraproject.org
Date: Thu Nov 15 14:04:14 2012 -0500
0.9914 + more complete list of Provides
perl-Wx.spec | 374 +-
sources |2 +-
2 files changed, 371 insertions(+), 5 deletions(-)
---
diff --git a/perl-Wx.spec b/perl-Wx.spec
index 9f4ef8a..a54b745 100644
--- a/perl-Wx.spec
+++ b/perl-Wx.spec
@@ -6,16 +6,18 @@
# NOTE: On every new version, we need to manually regenerate the list of XS
Provides
# cd Wx-*
-# for i in `grep -r PACKAGE= * | cut -d -f 2 | sed 's|PACKAGE=|perl(|g'
| grep Wx:: | sort -n |uniq`; do printf Provides: $i)\\n; done
+# for i in `grep -r PACKAGE= * | cut -d -f 2 | sed 's|PACKAGE=|perl(|g'
| grep Wx:: | sort -n |uniq`; do printf Provides: $i)\\n; done
provides.txt
+# grep -orP '%name{Wx::[^}]*}\s+class' |grep -v 3pm | cut -d : -f 2- | sed
's|%name{|Provides: perl(|g' | sed 's|} class|)|g' |uniq provides.txt
+# cat provides.txt | uniq | sort -n
Name: perl-Wx
-Version:0.9901
+Version:0.9914
Release:2%{?dist}
Summary:Interface to the wxWidgets cross-platform GUI toolkit
Group: Development/Libraries
License:GPL+ or Artistic
URL:http://search.cpan.org/dist/Wx/
-Source0:
http://search.cpan.org/CPAN/authors/id/M/MB/MBARBON/Wx-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/M/MD/MDOOTSON/Wx-%{version}.tar.gz
BuildRequires: wxGTK-devel
BuildRequires: perl(Alien::wxWidgets) = 0.25
BuildRequires: perl(Data::Dumper)
@@ -31,23 +33,46 @@ BuildRequires: perl(YAML) = 0.35
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# Manual provides from XS
+Provides: perl(Wx::AboutDialogInfo)
Provides: perl(Wx::AcceleratorEntry)
Provides: perl(Wx::AcceleratorTable)
Provides: perl(Wx::ActivateEvent)
Provides: perl(Wx::ANIHandler)
-Provides: perl(Wx::App)
+Provides: perl(Wx::Animation)
+Provides: perl(Wx::AnimationCtrl)
Provides: perl(Wx::_App)
+Provides: perl(Wx::App)
Provides: perl(Wx::ArchiveFSHandler)
+Provides: perl(Wx::ArrayStringProperty)
Provides: perl(Wx::ArtProvider)
Provides: perl(Wx::AUI)
+Provides: perl(Wx::AuiManager)
+Provides: perl(Wx::AuiManagerEvent)
+Provides: perl(Wx::AuiNotebook)
+Provides: perl(Wx::AuiNotebookEvent)
+Provides: perl(Wx::AuiPaneInfo)
+Provides: perl(Wx::AutoBufferedPaintDC)
+Provides: perl(Wx::BannerWindow)
Provides: perl(Wx::BestHelpController)
Provides: perl(Wx::Bitmap)
+Provides: perl(Wx::BitmapButton)
+Provides: perl(Wx::BitmapComboBox)
Provides: perl(Wx::BitmapDataObject)
Provides: perl(Wx::BitmapToggleButton)
Provides: perl(Wx::BMPHandler)
+Provides: perl(Wx::BookCtrl)
+Provides: perl(Wx::BookCtrlEvent)
+Provides: perl(Wx::BoolProperty)
Provides: perl(Wx::BoxSizer)
+Provides: perl(Wx::Brush)
+Provides: perl(Wx::BufferedDC)
+Provides: perl(Wx::BufferedPaintDC)
Provides: perl(Wx::BusyCursor)
Provides: perl(Wx::BusyInfo)
+Provides: perl(Wx::Button)
+Provides: perl(Wx::CalendarCtrl)
+Provides: perl(Wx::CalendarDateAttr)
+Provides: perl(Wx::CalendarEvent)
Provides: perl(Wx::Caret)
Provides: perl(Wx::CaretSuspend)
Provides: perl(Wx::CheckBox)
@@ -55,32 +80,80 @@ Provides: perl(Wx::CheckListBox)
Provides: perl(Wx::ChildFocusEvent)
Provides: perl(Wx::CHMHelpController)
Provides: perl(Wx::Choice)
+Provides: perl(Wx::Choicebook)
+Provides: perl(Wx::ClassInfo)
Provides: perl(Wx::ClassInfo)
Provides: perl(Wx::ClientDC)
Provides: perl(Wx::Clipboard)
Provides: perl(Wx::ClipboardTextEvent)
Provides: perl(Wx::CloseEvent)
+Provides: perl(Wx::CollapsiblePane)
+Provides: perl(Wx::CollapsiblePaneEvent)
Provides: perl(Wx::Colour)
Provides: perl(Wx::ColourData)
Provides: perl(Wx::ColourDatabase)
Provides: perl(Wx::ColourDialog)
+Provides: perl(Wx::ColourPickerCtrl)
+Provides: perl(Wx::ColourPickerEvent)
+Provides: perl(Wx::ColourProperty)
+Provides: perl(Wx::ColourPropertyValue)
Provides: perl(Wx::ComboBox)
+Provides: perl(Wx::ComboCtrl)
+Provides: perl(Wx::ComboPopup)
+Provides: perl(Wx::Command)
Provides: perl(Wx::CommandEvent)
+Provides: perl(Wx::CommandProcessor)
Provides: perl(Wx::ConfigBase)
Provides: perl(Wx::ContextHelp)
Provides: perl(Wx::ContextHelpButton)
Provides: perl(Wx::ContextMenuEvent)
Provides: perl(Wx::Control)
+Provides: perl(Wx::ControlWithItems)
Provides: perl(Wx::CURHandler)
Provides: perl(Wx::Cursor)
+Provides: perl(Wx::CursorProperty)
Provides: perl(Wx::DataFormat)
+Provides: perl(Wx::DatagramSocket)
Provides: perl(Wx::DataObject)
Provides: perl(Wx::DataObjectComposite)
Provides: perl(Wx::DataObjectSimple)
Provides: perl(Wx::DataView)
+Provides: perl(Wx::DataViewBitmapRenderer)
+Provides: perl(Wx::DataViewColumn)
+Provides: perl(Wx::DataViewCtrl)
+Provides: perl(Wx::DataViewDateRenderer)
+Provides: perl(Wx::DataViewEvent)
+Provides: perl(Wx::DataViewIconText)
+Provides: perl(Wx::DataViewIconTextRenderer)
[perl-Wx/f17] 0.9914 + more complete list of Provides
commit 9df52c8f768409c128c62c6eb15b425ca8dd3f86
Author: Tom Callaway s...@fedoraproject.org
Date: Thu Nov 15 14:06:15 2012 -0500
0.9914 + more complete list of Provides
perl-Wx.spec | 363 +-
sources |2 +-
2 files changed, 361 insertions(+), 4 deletions(-)
---
diff --git a/perl-Wx.spec b/perl-Wx.spec
index b260755..a54b745 100644
--- a/perl-Wx.spec
+++ b/perl-Wx.spec
@@ -6,10 +6,12 @@
# NOTE: On every new version, we need to manually regenerate the list of XS
Provides
# cd Wx-*
-# for i in `grep -r PACKAGE= * | cut -d -f 2 | sed 's|PACKAGE=|perl(|g'
| grep Wx:: | sort -n |uniq`; do printf Provides: $i)\\n; done
+# for i in `grep -r PACKAGE= * | cut -d -f 2 | sed 's|PACKAGE=|perl(|g'
| grep Wx:: | sort -n |uniq`; do printf Provides: $i)\\n; done
provides.txt
+# grep -orP '%name{Wx::[^}]*}\s+class' |grep -v 3pm | cut -d : -f 2- | sed
's|%name{|Provides: perl(|g' | sed 's|} class|)|g' |uniq provides.txt
+# cat provides.txt | uniq | sort -n
Name: perl-Wx
-Version:0.9903
+Version:0.9914
Release:2%{?dist}
Summary:Interface to the wxWidgets cross-platform GUI toolkit
Group: Development/Libraries
@@ -31,23 +33,46 @@ BuildRequires: perl(YAML) = 0.35
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# Manual provides from XS
+Provides: perl(Wx::AboutDialogInfo)
Provides: perl(Wx::AcceleratorEntry)
Provides: perl(Wx::AcceleratorTable)
Provides: perl(Wx::ActivateEvent)
Provides: perl(Wx::ANIHandler)
-Provides: perl(Wx::App)
+Provides: perl(Wx::Animation)
+Provides: perl(Wx::AnimationCtrl)
Provides: perl(Wx::_App)
+Provides: perl(Wx::App)
Provides: perl(Wx::ArchiveFSHandler)
+Provides: perl(Wx::ArrayStringProperty)
Provides: perl(Wx::ArtProvider)
Provides: perl(Wx::AUI)
+Provides: perl(Wx::AuiManager)
+Provides: perl(Wx::AuiManagerEvent)
+Provides: perl(Wx::AuiNotebook)
+Provides: perl(Wx::AuiNotebookEvent)
+Provides: perl(Wx::AuiPaneInfo)
+Provides: perl(Wx::AutoBufferedPaintDC)
+Provides: perl(Wx::BannerWindow)
Provides: perl(Wx::BestHelpController)
Provides: perl(Wx::Bitmap)
+Provides: perl(Wx::BitmapButton)
+Provides: perl(Wx::BitmapComboBox)
Provides: perl(Wx::BitmapDataObject)
Provides: perl(Wx::BitmapToggleButton)
Provides: perl(Wx::BMPHandler)
+Provides: perl(Wx::BookCtrl)
+Provides: perl(Wx::BookCtrlEvent)
+Provides: perl(Wx::BoolProperty)
Provides: perl(Wx::BoxSizer)
+Provides: perl(Wx::Brush)
+Provides: perl(Wx::BufferedDC)
+Provides: perl(Wx::BufferedPaintDC)
Provides: perl(Wx::BusyCursor)
Provides: perl(Wx::BusyInfo)
+Provides: perl(Wx::Button)
+Provides: perl(Wx::CalendarCtrl)
+Provides: perl(Wx::CalendarDateAttr)
+Provides: perl(Wx::CalendarEvent)
Provides: perl(Wx::Caret)
Provides: perl(Wx::CaretSuspend)
Provides: perl(Wx::CheckBox)
@@ -55,32 +80,80 @@ Provides: perl(Wx::CheckListBox)
Provides: perl(Wx::ChildFocusEvent)
Provides: perl(Wx::CHMHelpController)
Provides: perl(Wx::Choice)
+Provides: perl(Wx::Choicebook)
+Provides: perl(Wx::ClassInfo)
Provides: perl(Wx::ClassInfo)
Provides: perl(Wx::ClientDC)
Provides: perl(Wx::Clipboard)
Provides: perl(Wx::ClipboardTextEvent)
Provides: perl(Wx::CloseEvent)
+Provides: perl(Wx::CollapsiblePane)
+Provides: perl(Wx::CollapsiblePaneEvent)
Provides: perl(Wx::Colour)
Provides: perl(Wx::ColourData)
Provides: perl(Wx::ColourDatabase)
Provides: perl(Wx::ColourDialog)
+Provides: perl(Wx::ColourPickerCtrl)
+Provides: perl(Wx::ColourPickerEvent)
+Provides: perl(Wx::ColourProperty)
+Provides: perl(Wx::ColourPropertyValue)
Provides: perl(Wx::ComboBox)
+Provides: perl(Wx::ComboCtrl)
+Provides: perl(Wx::ComboPopup)
+Provides: perl(Wx::Command)
Provides: perl(Wx::CommandEvent)
+Provides: perl(Wx::CommandProcessor)
Provides: perl(Wx::ConfigBase)
Provides: perl(Wx::ContextHelp)
Provides: perl(Wx::ContextHelpButton)
Provides: perl(Wx::ContextMenuEvent)
Provides: perl(Wx::Control)
+Provides: perl(Wx::ControlWithItems)
Provides: perl(Wx::CURHandler)
Provides: perl(Wx::Cursor)
+Provides: perl(Wx::CursorProperty)
Provides: perl(Wx::DataFormat)
+Provides: perl(Wx::DatagramSocket)
Provides: perl(Wx::DataObject)
Provides: perl(Wx::DataObjectComposite)
Provides: perl(Wx::DataObjectSimple)
Provides: perl(Wx::DataView)
+Provides: perl(Wx::DataViewBitmapRenderer)
+Provides: perl(Wx::DataViewColumn)
+Provides: perl(Wx::DataViewCtrl)
+Provides: perl(Wx::DataViewDateRenderer)
+Provides: perl(Wx::DataViewEvent)
+Provides: perl(Wx::DataViewIconText)
+Provides: perl(Wx::DataViewIconTextRenderer)
+Provides: perl(Wx::DataViewIndexListModel)
+Provides: perl(Wx::DataViewItem)
+Provides: perl(Wx::DataViewItemAttr)
+Provides: perl(Wx::DataViewListCtrl)
+Provides: perl(Wx::DataViewListStore)
+Provides: perl(Wx::DataViewModel)
+Provides: perl(Wx::DataViewModelNotifier)
+Provides: perl(Wx::DataViewProgressRenderer)
+Provides: perl(Wx::DataViewRenderer)
+Provides:
[perl-Wx/f18] 0.9914 + more complete list of Provides
commit b84078132c3f0c213da6687ea716c8ac2f6aafa5
Author: Tom Callaway s...@fedoraproject.org
Date: Thu Nov 15 14:06:49 2012 -0500
0.9914 + more complete list of Provides
perl-Wx.spec | 329 +-
1 files changed, 326 insertions(+), 3 deletions(-)
---
diff --git a/perl-Wx.spec b/perl-Wx.spec
index f6845ab..a54b745 100644
--- a/perl-Wx.spec
+++ b/perl-Wx.spec
@@ -6,11 +6,13 @@
# NOTE: On every new version, we need to manually regenerate the list of XS
Provides
# cd Wx-*
-# for i in `grep -r PACKAGE= * | cut -d -f 2 | sed 's|PACKAGE=|perl(|g'
| grep Wx:: | sort -n |uniq`; do printf Provides: $i)\\n; done
+# for i in `grep -r PACKAGE= * | cut -d -f 2 | sed 's|PACKAGE=|perl(|g'
| grep Wx:: | sort -n |uniq`; do printf Provides: $i)\\n; done
provides.txt
+# grep -orP '%name{Wx::[^}]*}\s+class' |grep -v 3pm | cut -d : -f 2- | sed
's|%name{|Provides: perl(|g' | sed 's|} class|)|g' |uniq provides.txt
+# cat provides.txt | uniq | sort -n
Name: perl-Wx
Version:0.9914
-Release:1%{?dist}
+Release:2%{?dist}
Summary:Interface to the wxWidgets cross-platform GUI toolkit
Group: Development/Libraries
License:GPL+ or Artistic
@@ -31,23 +33,46 @@ BuildRequires: perl(YAML) = 0.35
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# Manual provides from XS
+Provides: perl(Wx::AboutDialogInfo)
Provides: perl(Wx::AcceleratorEntry)
Provides: perl(Wx::AcceleratorTable)
Provides: perl(Wx::ActivateEvent)
Provides: perl(Wx::ANIHandler)
-Provides: perl(Wx::App)
+Provides: perl(Wx::Animation)
+Provides: perl(Wx::AnimationCtrl)
Provides: perl(Wx::_App)
+Provides: perl(Wx::App)
Provides: perl(Wx::ArchiveFSHandler)
+Provides: perl(Wx::ArrayStringProperty)
Provides: perl(Wx::ArtProvider)
Provides: perl(Wx::AUI)
+Provides: perl(Wx::AuiManager)
+Provides: perl(Wx::AuiManagerEvent)
+Provides: perl(Wx::AuiNotebook)
+Provides: perl(Wx::AuiNotebookEvent)
+Provides: perl(Wx::AuiPaneInfo)
+Provides: perl(Wx::AutoBufferedPaintDC)
+Provides: perl(Wx::BannerWindow)
Provides: perl(Wx::BestHelpController)
Provides: perl(Wx::Bitmap)
+Provides: perl(Wx::BitmapButton)
+Provides: perl(Wx::BitmapComboBox)
Provides: perl(Wx::BitmapDataObject)
Provides: perl(Wx::BitmapToggleButton)
Provides: perl(Wx::BMPHandler)
+Provides: perl(Wx::BookCtrl)
+Provides: perl(Wx::BookCtrlEvent)
+Provides: perl(Wx::BoolProperty)
Provides: perl(Wx::BoxSizer)
+Provides: perl(Wx::Brush)
+Provides: perl(Wx::BufferedDC)
+Provides: perl(Wx::BufferedPaintDC)
Provides: perl(Wx::BusyCursor)
Provides: perl(Wx::BusyInfo)
+Provides: perl(Wx::Button)
+Provides: perl(Wx::CalendarCtrl)
+Provides: perl(Wx::CalendarDateAttr)
+Provides: perl(Wx::CalendarEvent)
Provides: perl(Wx::Caret)
Provides: perl(Wx::CaretSuspend)
Provides: perl(Wx::CheckBox)
@@ -55,32 +80,80 @@ Provides: perl(Wx::CheckListBox)
Provides: perl(Wx::ChildFocusEvent)
Provides: perl(Wx::CHMHelpController)
Provides: perl(Wx::Choice)
+Provides: perl(Wx::Choicebook)
+Provides: perl(Wx::ClassInfo)
Provides: perl(Wx::ClassInfo)
Provides: perl(Wx::ClientDC)
Provides: perl(Wx::Clipboard)
Provides: perl(Wx::ClipboardTextEvent)
Provides: perl(Wx::CloseEvent)
+Provides: perl(Wx::CollapsiblePane)
+Provides: perl(Wx::CollapsiblePaneEvent)
Provides: perl(Wx::Colour)
Provides: perl(Wx::ColourData)
Provides: perl(Wx::ColourDatabase)
Provides: perl(Wx::ColourDialog)
+Provides: perl(Wx::ColourPickerCtrl)
+Provides: perl(Wx::ColourPickerEvent)
+Provides: perl(Wx::ColourProperty)
+Provides: perl(Wx::ColourPropertyValue)
Provides: perl(Wx::ComboBox)
+Provides: perl(Wx::ComboCtrl)
+Provides: perl(Wx::ComboPopup)
+Provides: perl(Wx::Command)
Provides: perl(Wx::CommandEvent)
+Provides: perl(Wx::CommandProcessor)
Provides: perl(Wx::ConfigBase)
Provides: perl(Wx::ContextHelp)
Provides: perl(Wx::ContextHelpButton)
Provides: perl(Wx::ContextMenuEvent)
Provides: perl(Wx::Control)
+Provides: perl(Wx::ControlWithItems)
Provides: perl(Wx::CURHandler)
Provides: perl(Wx::Cursor)
+Provides: perl(Wx::CursorProperty)
Provides: perl(Wx::DataFormat)
+Provides: perl(Wx::DatagramSocket)
Provides: perl(Wx::DataObject)
Provides: perl(Wx::DataObjectComposite)
Provides: perl(Wx::DataObjectSimple)
Provides: perl(Wx::DataView)
+Provides: perl(Wx::DataViewBitmapRenderer)
+Provides: perl(Wx::DataViewColumn)
+Provides: perl(Wx::DataViewCtrl)
+Provides: perl(Wx::DataViewDateRenderer)
+Provides: perl(Wx::DataViewEvent)
+Provides: perl(Wx::DataViewIconText)
+Provides: perl(Wx::DataViewIconTextRenderer)
+Provides: perl(Wx::DataViewIndexListModel)
+Provides: perl(Wx::DataViewItem)
+Provides: perl(Wx::DataViewItemAttr)
+Provides: perl(Wx::DataViewListCtrl)
+Provides: perl(Wx::DataViewListStore)
+Provides: perl(Wx::DataViewModel)
+Provides: perl(Wx::DataViewModelNotifier)
+Provides: perl(Wx::DataViewProgressRenderer)
+Provides: perl(Wx::DataViewRenderer)
+Provides:
[perl-Wx] 0.9914 + more complete list of Provides
commit f78b62cbacba8fb8868d5788a5fe4640998aa08a
Author: Tom Callaway s...@fedoraproject.org
Date: Thu Nov 15 14:07:24 2012 -0500
0.9914 + more complete list of Provides
perl-Wx.spec | 329 +-
1 files changed, 326 insertions(+), 3 deletions(-)
---
diff --git a/perl-Wx.spec b/perl-Wx.spec
index f6845ab..a54b745 100644
--- a/perl-Wx.spec
+++ b/perl-Wx.spec
@@ -6,11 +6,13 @@
# NOTE: On every new version, we need to manually regenerate the list of XS
Provides
# cd Wx-*
-# for i in `grep -r PACKAGE= * | cut -d -f 2 | sed 's|PACKAGE=|perl(|g'
| grep Wx:: | sort -n |uniq`; do printf Provides: $i)\\n; done
+# for i in `grep -r PACKAGE= * | cut -d -f 2 | sed 's|PACKAGE=|perl(|g'
| grep Wx:: | sort -n |uniq`; do printf Provides: $i)\\n; done
provides.txt
+# grep -orP '%name{Wx::[^}]*}\s+class' |grep -v 3pm | cut -d : -f 2- | sed
's|%name{|Provides: perl(|g' | sed 's|} class|)|g' |uniq provides.txt
+# cat provides.txt | uniq | sort -n
Name: perl-Wx
Version:0.9914
-Release:1%{?dist}
+Release:2%{?dist}
Summary:Interface to the wxWidgets cross-platform GUI toolkit
Group: Development/Libraries
License:GPL+ or Artistic
@@ -31,23 +33,46 @@ BuildRequires: perl(YAML) = 0.35
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# Manual provides from XS
+Provides: perl(Wx::AboutDialogInfo)
Provides: perl(Wx::AcceleratorEntry)
Provides: perl(Wx::AcceleratorTable)
Provides: perl(Wx::ActivateEvent)
Provides: perl(Wx::ANIHandler)
-Provides: perl(Wx::App)
+Provides: perl(Wx::Animation)
+Provides: perl(Wx::AnimationCtrl)
Provides: perl(Wx::_App)
+Provides: perl(Wx::App)
Provides: perl(Wx::ArchiveFSHandler)
+Provides: perl(Wx::ArrayStringProperty)
Provides: perl(Wx::ArtProvider)
Provides: perl(Wx::AUI)
+Provides: perl(Wx::AuiManager)
+Provides: perl(Wx::AuiManagerEvent)
+Provides: perl(Wx::AuiNotebook)
+Provides: perl(Wx::AuiNotebookEvent)
+Provides: perl(Wx::AuiPaneInfo)
+Provides: perl(Wx::AutoBufferedPaintDC)
+Provides: perl(Wx::BannerWindow)
Provides: perl(Wx::BestHelpController)
Provides: perl(Wx::Bitmap)
+Provides: perl(Wx::BitmapButton)
+Provides: perl(Wx::BitmapComboBox)
Provides: perl(Wx::BitmapDataObject)
Provides: perl(Wx::BitmapToggleButton)
Provides: perl(Wx::BMPHandler)
+Provides: perl(Wx::BookCtrl)
+Provides: perl(Wx::BookCtrlEvent)
+Provides: perl(Wx::BoolProperty)
Provides: perl(Wx::BoxSizer)
+Provides: perl(Wx::Brush)
+Provides: perl(Wx::BufferedDC)
+Provides: perl(Wx::BufferedPaintDC)
Provides: perl(Wx::BusyCursor)
Provides: perl(Wx::BusyInfo)
+Provides: perl(Wx::Button)
+Provides: perl(Wx::CalendarCtrl)
+Provides: perl(Wx::CalendarDateAttr)
+Provides: perl(Wx::CalendarEvent)
Provides: perl(Wx::Caret)
Provides: perl(Wx::CaretSuspend)
Provides: perl(Wx::CheckBox)
@@ -55,32 +80,80 @@ Provides: perl(Wx::CheckListBox)
Provides: perl(Wx::ChildFocusEvent)
Provides: perl(Wx::CHMHelpController)
Provides: perl(Wx::Choice)
+Provides: perl(Wx::Choicebook)
+Provides: perl(Wx::ClassInfo)
Provides: perl(Wx::ClassInfo)
Provides: perl(Wx::ClientDC)
Provides: perl(Wx::Clipboard)
Provides: perl(Wx::ClipboardTextEvent)
Provides: perl(Wx::CloseEvent)
+Provides: perl(Wx::CollapsiblePane)
+Provides: perl(Wx::CollapsiblePaneEvent)
Provides: perl(Wx::Colour)
Provides: perl(Wx::ColourData)
Provides: perl(Wx::ColourDatabase)
Provides: perl(Wx::ColourDialog)
+Provides: perl(Wx::ColourPickerCtrl)
+Provides: perl(Wx::ColourPickerEvent)
+Provides: perl(Wx::ColourProperty)
+Provides: perl(Wx::ColourPropertyValue)
Provides: perl(Wx::ComboBox)
+Provides: perl(Wx::ComboCtrl)
+Provides: perl(Wx::ComboPopup)
+Provides: perl(Wx::Command)
Provides: perl(Wx::CommandEvent)
+Provides: perl(Wx::CommandProcessor)
Provides: perl(Wx::ConfigBase)
Provides: perl(Wx::ContextHelp)
Provides: perl(Wx::ContextHelpButton)
Provides: perl(Wx::ContextMenuEvent)
Provides: perl(Wx::Control)
+Provides: perl(Wx::ControlWithItems)
Provides: perl(Wx::CURHandler)
Provides: perl(Wx::Cursor)
+Provides: perl(Wx::CursorProperty)
Provides: perl(Wx::DataFormat)
+Provides: perl(Wx::DatagramSocket)
Provides: perl(Wx::DataObject)
Provides: perl(Wx::DataObjectComposite)
Provides: perl(Wx::DataObjectSimple)
Provides: perl(Wx::DataView)
+Provides: perl(Wx::DataViewBitmapRenderer)
+Provides: perl(Wx::DataViewColumn)
+Provides: perl(Wx::DataViewCtrl)
+Provides: perl(Wx::DataViewDateRenderer)
+Provides: perl(Wx::DataViewEvent)
+Provides: perl(Wx::DataViewIconText)
+Provides: perl(Wx::DataViewIconTextRenderer)
+Provides: perl(Wx::DataViewIndexListModel)
+Provides: perl(Wx::DataViewItem)
+Provides: perl(Wx::DataViewItemAttr)
+Provides: perl(Wx::DataViewListCtrl)
+Provides: perl(Wx::DataViewListStore)
+Provides: perl(Wx::DataViewModel)
+Provides: perl(Wx::DataViewModelNotifier)
+Provides: perl(Wx::DataViewProgressRenderer)
+Provides: perl(Wx::DataViewRenderer)
+Provides:
Re: The GNOME 3.6.2 Megaupdate
bodhi -D FEDORA-2012-18258 will download all packages in that update for you. Usability is so poor that you might give up [all on up-to-date Fedora 18 Beta-TC8+]: # type bodhi bash: type: bodhi: not found No hints? # yum install bodhi Loaded plugins: langpacks, presto, refresh-packagekit fedora/18/x86_64/metalink | 12 kB 00:00:00 updates/18/x86_64/metalink | 18 kB 00:00:00 No package bodhi available. Now search koji for package bodhi, see bodhi-0.9.3-1.fc18, try again yum install bodhi, fail again. Search harder, the package name actually is bodhi-client. So searching for packages doesn't return a package name. # yum install bodhi-client Then a typo (a *syntax error*) causes a crash. # bodhi -D FEDORA_2012-18258 Traceback (most recent call last): File /usr/bin/bodhi, line 523, in module main() File /usr/bin/bodhi, line 494, in main update = data['updates'][0] IndexError: list index out of range # https://bugzilla.redhat.com/show_bug.cgi?id=877134 -- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: raising warning flag on firewalld-default feature
On 11/12/2012 02:15 PM, Miloslav Trmač wrote: On Mon, Nov 12, 2012 at 7:54 PM, Kevin Kofler kevin.kof...@chello.at wrote: Right. We need to stop writing core system components in scripting languages! Well, there _are_ significant advantages to using a higer-level language than C.[1] Using one of the higher-level languages as a primary development language on par with C often increases the quality of the software and the time to develop it, in return for an acceptable loss of speed.\ ... [1] At least two to mention: - Automatic memory management, with all associated lack of bugs and simplified code - Much easier access to higher-level (and more efficient!) data structures. C programs frequently use linked lists instead of e.g. hash tables simply because maintaining hash tables and the associated memory allocation is just too complex. +1! I imagine that Kevin objects to the interpreter-induced slowness of scripting, but quite often it's not even relevant because the code doesn't run that much. To Miloslav's list of advantages, I would add access to better libraries (e.g. network programming in Python or Tcl is much easier than socket()-based code). There's the force multiplier effect of higher level libraries allowing better algorithms, which often trumps any advantages from compiled code. If there's a _measurable_ speed issue, all modern interpreters have an easy 'native method' interface, i.e. way of linking compiled code functions that implement time-critical parts, if they are too slow for interpreting. Let's avoid premature optimization--otherwise, taking this idea to the extreme, one could argue for rewriting system services in optimized assembly. Remember also that data is code: any config files could be seen as tiny specialized interpreted languages, so it's not like you can avoid interpretation anyway. Perhaps embracing scripting in system components would have a desirable side effect of more uniform config file syntax because it's just easier to use some standard form like JSON or XML.. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 876221] perl-Wx does not provide perl(Wx::Dialog) and others.
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876221 --- Comment #1 from Fedora Update System upda...@fedoraproject.org --- perl-Wx-0.9914-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/perl-Wx-0.9914-2.fc17 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 876221] perl-Wx does not provide perl(Wx::Dialog) and others.
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876221 --- Comment #2 from Fedora Update System upda...@fedoraproject.org --- perl-Wx-0.9914-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/perl-Wx-0.9914-2.fc16 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 876221] perl-Wx does not provide perl(Wx::Dialog) and others.
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876221 --- Comment #3 from Fedora Update System upda...@fedoraproject.org --- perl-Wx-0.9914-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/perl-Wx-0.9914-2.fc18 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: The GNOME 3.6.2 Megaupdate
On 11/15/12 2:11 PM, John Reiser wrote: # yum install bodhi Loaded plugins: langpacks, presto, refresh-packagekit fedora/18/x86_64/metalink | 12 kB 00:00:00 updates/18/x86_64/metalink | 18 kB 00:00:00 No package bodhi available. % sudo yum install /usr/bin/bodhi HTH. - ajax -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Setting the default firewall configuration (was Re: Attention, dependency fighters)
Am 15.11.2012 19:58, schrieb Adam Williamson: I don't think anyone asked you to do any of those things. Fedora obviously does not have the power to replace iptables with firewalld on your router, so the question is not 'can you replace iptables with firewalld on everything in your network and see if it works'. The question is more 'can you see if firewalld does a good job of imitating iptables on a single Fedora machine on your network, or a small amount of them'. The whole point is it should be able to imitate an iptables-type setup fairly transparently, so it should 'play nice' with the rest of your setup. Can't you just test that? and that is why i posted earlier this day a masked copy of the script ONE script distributed from a admin-server is deplayoed to ANY machine and exuted with ssh root@machine /scripts/iptables.sh this thing was written, optimized and maintained for many years it containes rules to block specific outgoing AND incoming connections in a more or less dynmic infrastructure there is no this is the iptables of machine X i am not only responsible for ONE network, there are finally MANY networks, they are more or less based on this one script the reason is simply that if you have, can and do maintain larger environemnts more or less a a one-man-show you need to find workloads and solutions to surivive this which is achievd since years - starting tis from scratch means wasting weeks of lifetime don't get me wrong: force this would be no improvement finally: i am pretty sure that my environments are even SMALL compared with many others out there, iptables-service is a one-shot thing at startup, low-level this all is netfilter of the kernel so i refuse to understand any sense removing the iptables command and iptables.service to replace it for the sake of replacment if your argumentation would be this direction i would say so why do we not remove XFCE, GNOME whatever because KDE exists signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: raising warning flag on firewalld-default feature
On Tue, Nov 13, 2012 at 2:48 AM, Jan Zelený jzel...@redhat.com wrote: On 12. 11. 2012 at 17:59:00, Chris Adams wrote: Once upon a time, Richard Vickery richard.vicker...@gmail.com said: Change still frightens people to varying degree s., and many busy end-users may not have time to read pages in order to learn a new command It is in _development_ and is just in F18 as a preview. If/when it is ready to replace yum, it may get a symlink from /usr/bin/yum. That's the plan. Can you guys post all of the plan in this list? (as a sep announcement) I am not sure the broader Fedora community has any real idea what dnf or the seemingly newly created packaging team plans are Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
Matthew Miller (mat...@fedoraproject.org) said: On Wed, Nov 14, 2012 at 10:03:36PM -0800, Adam Williamson wrote: Is there any reason those two can't be split up? Maybe @really-hard-core for the first, and @core for the second. ;-) That's basically what Kevin proposed several mails back, and I agree it seems like we have two broadly definable cases here rather than one. I think Bill Nottingham mentioned something similar too, although I don't want to put words into his mouth. What I had suggested at one point was we have an 'image-base' group that is *really* tiny, that is intended to be used as a basis for creating images, chroot, and other things where you're not necessarily doing package management *on the running system*. So it would be: kernel systemd initscripts util-linux bash and their dependencies. Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
Matthew Miller (mat...@fedoraproject.org) said: Well, it would be weird that the minimal installation is actually not minimal at all, but the container installation is. That would be weird. But fortunately, it's @core, not @minimal. So we could easily have @minimal, @core, and @standard, each with different targets. @core is what's shown as the minimal install in anacona. We could do some renaming, but having @minimal, and having it *not* be the minimal install in anaconda, sounds like a really bad idea. Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [@core] working definition for the minimal package set
On Thu, Nov 15, 2012 at 10:12 PM, Bill Nottingham nott...@redhat.com wrote: Matthew Miller (mat...@fedoraproject.org) said: Well, it would be weird that the minimal installation is actually not minimal at all, but the container installation is. That would be weird. But fortunately, it's @core, not @minimal. So we could easily have @minimal, @core, and @standard, each with different targets. @core is what's shown as the minimal install in anacona. We could do some renaming, but having @minimal, and having it *not* be the minimal install in anaconda, sounds like a really bad idea. We could have @core, @container and @cloud ... trying to fit multiple cases in one group just wont work. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Problem with jack update
On 15 November 2012 04:40, Orcan Ogetbil oget.fed...@gmail.com wrote: Hi all, A few months ago earlier in the F-17 release cycle, we had a problem with jackd turning verbose, flooding the stdout, even when its verbosity was turned off. This was a bug [1] in the compiler, specifically in the optimized builds, for which we filed a bug against upstream gcc [2]. As a workaround we rebuilt jack unoptimized, and we have been using the unoptimized build since. Late in September the issue got resolved in upstream gcc (see [2]). The fixed compiler version arrived at Fedora shortly. Therefore, I decided to rebuild jack optimized about 2 weeks ago. I rebuilt jack on my local box in a clean mock environment, and I tested it locally. There were no issues with verbosity. I submitted a build on koji and made a remark on [1] at comment #29. I checked the koji root.log [3] for the buildroot and I verified that it has the same gcc version 4.7.2-2.fc17 that my local mock build had (Not just the gcc, but all the core packages in root.log had the same versions with my local mock build). At this point, I made a mistake. Since no one complained in the bug report, I assumed that the issue was resolved and I pushed the update to stable after two weeks. Unfortunately, I just noticed that the verbosity issue persists in this koji build. I uploaded my local mock build results at [4]. The RPMs there do not have the verbosity issue. But I am out of ideas for what might be going wrong. The question is: what am I missing? Thanks, Orcan [1] https://bugzilla.redhat.com/show_bug.cgi?id=827748 [2] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53663 [3] http://koji.fedoraproject.org/koji/buildinfo?buildID=362840 [4] http://oget.fedorapeople.org/jack/ This isn't much help, but on a f18 install building the -12 spec I get the verbosity bug and not with the -11 version (the one with -O0). rpm -q gcc glibc gcc-4.7.2-3.fc18.x86_64 glibc-2.16-20.fc18.x86_64 (vs gcc-4.7.2-2.fc17.x86_64, it was built a few days after) And the same with recent updates: gcc-4.7.2-8.fc18.x86_64 glibc-2.16-20.fc18.x86_64 (gcc built 2012-11-09) -- imalone http://ibmalone.blogspot.co.uk -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The GNOME 3.6.2 Megaupdate
On 11/15/2012 11:11 AM, John Reiser wrote: bodhi -D FEDORA-2012-18258 will download all packages in that update for you. Usability is so poor that you might give up [all on up-to-date Fedora 18 Beta-TC8+]: yum search bodhi? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 876951] New: perl-CGI-3.63 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876951 Bug ID: 876951 Summary: perl-CGI-3.63 is available Product: Fedora Version: rawhide Component: perl-CGI Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Reporter: upstream-release-monitor...@fedoraproject.org Type: --- Latest upstream release: 3.63 Current version in Fedora Rawhide: 3.61 URL: http://search.cpan.org/dist/CGI/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 876952] New: perl-Net-GitHub-0.48 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876952 Bug ID: 876952 Summary: perl-Net-GitHub-0.48 is available Product: Fedora Version: rawhide Component: perl-Net-GitHub Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Reporter: upstream-release-monitor...@fedoraproject.org Type: --- Latest upstream release: 0.48 Current version in Fedora Rawhide: 0.47 URL: http://search.cpan.org/dist/Net-GitHub/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Tty] Fix the dependencies, license, and re-enable the tests
commit 10244d5461435a0c7e18561af1f3fe39792b8f24
Author: Petr Šabata con...@redhat.com
Date: Thu Nov 15 12:47:46 2012 +0100
Fix the dependencies, license, and re-enable the tests
perl-IO-Tty.spec | 44 +++-
1 files changed, 19 insertions(+), 25 deletions(-)
---
diff --git a/perl-IO-Tty.spec b/perl-IO-Tty.spec
index 91e2a6c..41d378c 100644
--- a/perl-IO-Tty.spec
+++ b/perl-IO-Tty.spec
@@ -1,17 +1,18 @@
Name: perl-IO-Tty
Version:1.10
-Release:7%{?dist}
+Release:8%{?dist}
Summary:Perl interface to pseudo tty's
-
-License:GPL+ or Artistic
+License:(GPL+ or Artistic) and BSD
Group: Development/Libraries
URL:http://search.cpan.org/dist/IO-Tty/
Source0:
http://www.cpan.org/authors/id/T/TO/TODDR/IO-Tty-%{version}.tar.gz
-BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
-
+BuildRequires: perl(Carp)
+BuildRequires: perl(Exporter)
BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(IO::File)
+BuildRequires: perl(IO::Handle)
BuildRequires: perl(Test::More)
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
# don't provide private Perl libs
%global _use_internal_dependency_generator 0
@@ -22,42 +23,35 @@ Requires: perl(:MODULE_COMPAT_%(eval `%{__perl}
-V:version`; echo $versi
%description
IO::Tty and IO::Pty provide an interface to pseudo tty's.
-
%prep
%setup -q -n IO-Tty-%{version}
-
%build
-%{__perl} Makefile.PL INSTALLDIRS=vendor OPTIMIZE=$RPM_OPT_FLAGS
+perl Makefile.PL INSTALLDIRS=vendor OPTIMIZE=%{optflags}
make %{?_smp_mflags}
-
%install
-rm -rf $RPM_BUILD_ROOT
-make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
-find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} ';'
-find $RPM_BUILD_ROOT -type f -name '*.bs' -a -size 0 -exec rm -f {} ';'
-find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null ';'
-%{_fixperms} $RPM_BUILD_ROOT/*
-
+make pure_install DESTDIR=%{buildroot}
+find %{buildroot} -type f -name .packlist -exec rm -f {} ';'
+find %{buildroot} -type f -name '*.bs' -a -size 0 -exec rm -f {} ';'
+%{_fixperms} %{buildroot}/*
%check
-##make test
-
-
-%clean
-rm -rf $RPM_BUILD_ROOT
-
+make test
%files
-%defattr(-,root,root,-)
%doc ChangeLog README
%{perl_vendorarch}/auto/IO/
%{perl_vendorarch}/IO/
%{_mandir}/man3/*.3pm*
-
%changelog
+* Thu Nov 15 2012 Petr Šabata con...@redhat.com - 1.10-8
+- Fix the dependencies
+- Re-enable the test suite
+- Modernize the spec
+- Correct the license tag
+
* Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.10-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 876165] mojomojo-1.07 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876165 Iain Arnell iarn...@gmail.com changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |RAWHIDE Last Closed||2012-11-15 06:58:40 --- Comment #1 from Iain Arnell iarn...@gmail.com --- This release just incorporates the patches to tests in our 1.06 version. No need to push it to stable branch(es). -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 876951] perl-CGI-3.63 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876951 Petr Pisar ppi...@redhat.com changed: What|Removed |Added CC|mmasl...@redhat.com |ppi...@redhat.com Assignee|mmasl...@redhat.com |ppi...@redhat.com Status|NEW |ASSIGNED -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Tty/f18] Fix the dependencies, license, and re-enable the tests
Summary of changes: 10244d5... Fix the dependencies, license, and re-enable the tests (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Tty/f17] (3 commits) ...Fix the dependencies, license, and re-enable the tests
Summary of changes: 5fe5d55... Perl 5.16 rebuild (*) d45c90e... - Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass (*) 10244d5... Fix the dependencies, license, and re-enable the tests (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 876951] perl-CGI-3.63 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=876951 --- Comment #1 from Petr Pisar ppi...@redhat.com --- Bug-fixing release. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File CGI.pm-3.63.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-CGI: 78eb3acb736205ca12ec2c79bc737e6c CGI.pm-3.63.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-CGI] 3.63 bump
commit 586f47573df5ddfd1b38c25f90920e3efd242500
Author: Petr Písař ppi...@redhat.com
Date: Thu Nov 15 13:08:56 2012 +0100
3.63 bump
.gitignore|1 +
perl-CGI.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 8755315..93e9c84 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@
/CGI.pm-3.60.tar.gz
/CGI.pm-3.61.tar.gz
/CGI.pm-3.62.tar.gz
+/CGI.pm-3.63.tar.gz
diff --git a/perl-CGI.spec b/perl-CGI.spec
index 86e651e..2a045a8 100644
--- a/perl-CGI.spec
+++ b/perl-CGI.spec
@@ -1,6 +1,6 @@
Name: perl-CGI
Summary:Handle Common Gateway Interface requests and responses
-Version:3.62
+Version:3.63
Release:1%{?dist}
License:GPL+ or Artistic
Group: Development/Libraries
@@ -67,6 +67,9 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Thu Nov 15 2012 Petr Pisar ppi...@redhat.com - 3.63-1
+- 3.63 bump
+
* Wed Nov 14 2012 Petr Pisar ppi...@redhat.com - 3.62-1
- 3.62 bump
diff --git a/sources b/sources
index 852c7a4..894f124 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-3600b5fb106c256d53393e86ba62c65e CGI.pm-3.62.tar.gz
+78eb3acb736205ca12ec2c79bc737e6c CGI.pm-3.63.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Tty/f16] (4 commits) ...Fix the dependencies, license, and re-enable the tests
Summary of changes: e326e55... - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass (*) 5fe5d55... Perl 5.16 rebuild (*) d45c90e... - Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass (*) 10244d5... Fix the dependencies, license, and re-enable the tests (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
