[perl-Geo-IP/f20] Update to 1.45
commit d5b1765b82f9aea44deaddca5c7a31e27dce342b
Author: Emmanuel Seyman emman...@seyman.fr
Date: Fri Feb 20 11:32:46 2015 +0100
Update to 1.45
.gitignore | 1 +
perl-Geo-IP.spec | 11 +++
sources | 2 +-
3 files changed, 9 insertions(+), 5 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index a05d815..fe04bd6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
Geo-IP-1.38.tar.gz
/Geo-IP-1.40.tar.gz
/Geo-IP-1.42.tar.gz
+/Geo-IP-1.45.tar.gz
diff --git a/perl-Geo-IP.spec b/perl-Geo-IP.spec
index a85efae..9dd2095 100644
--- a/perl-Geo-IP.spec
+++ b/perl-Geo-IP.spec
@@ -1,17 +1,18 @@
Name: perl-Geo-IP
Summary: Efficient Perl bindings for the GeoIP location database
-Version: 1.42
-Release: 2%{?dist}
+Version: 1.45
+Release: 1%{?dist}
URL: http://search.cpan.org/dist/Geo-IP/
License: GPL+ or Artistic
-Source0:
http://search.cpan.org/CPAN/authors/id/B/BO/BORISZ/Geo-IP-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/M/MA/MAXMIND/Geo-IP-%{version}.tar.gz
Patch0: Geo-IP-1.40-Drop-failing-namelookup-unit-test.patch
Patch1: Geo-IP-1.40-Fix-shebangs-in-example-files.patch
BuildRequires:GeoIP-devel
BuildRequires:perl(ExtUtils::MakeMaker)
+BuildRequires:perl(Test::More)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
@@ -28,7 +29,6 @@ similar modules.
%prep
%setup -q -n Geo-IP-%{version}
-%patch0 -p1
%patch1 -p1
@@ -60,6 +60,9 @@ make test
%changelog
+* Fri Feb 20 2015 Emmanuel Seyman emman...@seyman.fr - 1.45-1
+- Update to 1.45 (#1186988)
+
* Sat Aug 03 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.42-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
diff --git a/sources b/sources
index 2525237..5d98035 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-6516415a1aa6b5fd5d3444ef418c52f5 Geo-IP-1.42.tar.gz
+781fbf2a6b6505e86e3e5ebe05254928 Geo-IP-1.45.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
[Bug 1186988] GEOIP_SILENCE support needs to be added to perl-Geo-IP
https://bugzilla.redhat.com/show_bug.cgi?id=1186988 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- perl-Geo-IP-1.45-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/perl-Geo-IP-1.45-1.fc21 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=2OMdzzW4t5a=cc_unsubscribe -- 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 1186988] GEOIP_SILENCE support needs to be added to perl-Geo-IP
https://bugzilla.redhat.com/show_bug.cgi?id=1186988 Emmanuel Seyman emman...@seyman.fr changed: What|Removed |Added Version|rawhide |21 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6VQVDw5Ggja=cc_unsubscribe -- 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
Broken dependencies: polymake
polymake has broken dependencies in the F-22 tree: On x86_64: polymake-2.13-18.git20141013.fc22.x86_64 requires perl = 4:5.20.1 On i386: polymake-2.13-18.git20141013.fc22.i686 requires perl = 4:5.20.1 On armhfp: polymake-2.13-18.git20141013.fc22.armv7hl requires perl = 4:5.20.1 Please resolve this as soon as possible. -- 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 1186988] GEOIP_SILENCE support needs to be added to perl-Geo-IP
https://bugzilla.redhat.com/show_bug.cgi?id=1186988 --- Comment #8 from Fedora Update System upda...@fedoraproject.org --- perl-Geo-IP-1.45-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-Geo-IP-1.45-1.fc20 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=tVobrnckfaa=cc_unsubscribe -- 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 1194255] perl-Compress-Bzip2-2.22 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194255 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- Package perl-Compress-Bzip2-2.22-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing perl-Compress-Bzip2-2.22-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2320/perl-Compress-Bzip2-2.22-1.fc21 then log in and leave karma (feedback). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=tiEs6ogmESa=cc_unsubscribe -- 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
Broken dependencies: polymake
polymake has broken dependencies in the rawhide tree: On x86_64: polymake-2.13-18.git20141013.fc22.x86_64 requires perl = 4:5.20.1 On i386: polymake-2.13-18.git20141013.fc22.i686 requires perl = 4:5.20.1 On armhfp: polymake-2.13-18.git20141013.fc22.armv7hl requires perl = 4:5.20.1 Please resolve this as soon as possible. -- 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
Re: Minutes from Env-and-Stacks WG meeting (2015-02-19)
Quoting Honza Horak (2015-02-19 19:48:59) * Dockerfiles recommended tips (hhorak, 18:15:21) * LINK: https://fedoraproject.org/wiki/Env_and_Stacks/Tasklist (hhorak, 18:15:45) * LINK: https://fedoraproject.org/wiki/User:Hhorak/Draft/task-dockerfile-rules (hhorak, 18:15:55) * ACTION: phracek to get in touch with marek, author of JBoss Docker images best practices (hhorak, 18:24:10) I liked openshift's tips: http://docs.openshift.org/latest/image_writers_guide/guidelines.html Tomas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1186988] GEOIP_SILENCE support needs to be added to perl-Geo-IP
https://bugzilla.redhat.com/show_bug.cgi?id=1186988 Emmanuel Seyman emman...@seyman.fr changed: What|Removed |Added Summary|Version bump to libraries |GEOIP_SILENCE support needs |from GeoIP 1.6.4|to be added to perl-Geo-IP -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Dtjfzqp1QSa=cc_unsubscribe -- 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 1186988] GEOIP_SILENCE support needs to be added to perl-Geo-IP
https://bugzilla.redhat.com/show_bug.cgi?id=1186988 --- Comment #6 from Emmanuel Seyman emman...@seyman.fr --- perl-Geo-IP is already at 1.45 in F22. I'll release updates for F20 and F21. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=kOVmX7Xy0ra=cc_unsubscribe -- 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 1194256] perl-Getopt-Long-2.44 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194256 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #9 from Fedora Update System upda...@fedoraproject.org --- Package perl-Getopt-Long-2.44-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing perl-Getopt-Long-2.44-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2309/perl-Getopt-Long-2.44-1.fc21 then log in and leave karma (feedback). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=WEYI4dNJLPa=cc_unsubscribe -- 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-Geo-IP/f21] Update to 1.45
commit d1cc66c1fea6e26aaa10dd1d25ade275ba8889c2
Author: Emmanuel Seyman emman...@seyman.fr
Date: Fri Feb 20 11:07:27 2015 +0100
Update to 1.45
.gitignore | 1 +
perl-Geo-IP.spec | 11 +++
sources | 2 +-
3 files changed, 9 insertions(+), 5 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index a05d815..fe04bd6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
Geo-IP-1.38.tar.gz
/Geo-IP-1.40.tar.gz
/Geo-IP-1.42.tar.gz
+/Geo-IP-1.45.tar.gz
diff --git a/perl-Geo-IP.spec b/perl-Geo-IP.spec
index 206d1a9..61cd3aa 100644
--- a/perl-Geo-IP.spec
+++ b/perl-Geo-IP.spec
@@ -1,17 +1,18 @@
Name: perl-Geo-IP
Summary: Efficient Perl bindings for the GeoIP location database
-Version: 1.42
-Release: 4%{?dist}
+Version: 1.45
+Release: 1%{?dist}
URL: http://search.cpan.org/dist/Geo-IP/
License: GPL+ or Artistic
-Source0:
http://search.cpan.org/CPAN/authors/id/B/BO/BORISZ/Geo-IP-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/M/MA/MAXMIND/Geo-IP-%{version}.tar.gz
Patch0: Geo-IP-1.40-Drop-failing-namelookup-unit-test.patch
Patch1: Geo-IP-1.40-Fix-shebangs-in-example-files.patch
BuildRequires:GeoIP-devel
BuildRequires:perl(ExtUtils::MakeMaker)
+BuildRequires:perl(Test::More)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
@@ -28,7 +29,6 @@ similar modules.
%prep
%setup -q -n Geo-IP-%{version}
-%patch0 -p1
%patch1 -p1
@@ -60,6 +60,9 @@ make test
%changelog
+* Fri Feb 20 2015 Emmanuel Seyman emman...@seyman.fr - 1.45-1
+- Update to 1.45 (#1186988)
+
* Sun Aug 17 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.42-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild
diff --git a/sources b/sources
index 2525237..5d98035 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-6516415a1aa6b5fd5d3444ef418c52f5 Geo-IP-1.42.tar.gz
+781fbf2a6b6505e86e3e5ebe05254928 Geo-IP-1.45.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
Re: Proposal to (formally/easily) allowing multiple versions of the same library installable
/*Ralf Corsepius rc040...@freenet.de*/ wrote on Mon, 16 Feb 2015 17:17:32 +0100: On 02/16/2015 05:10 PM, Martyn Foster wrote: On 16 February 2015 at 15:12, Kevin Kofler kevin.kof...@chello.at mailto:kevin.kof...@chello.at wrote: Christopher Meng wrote: Maintaining several version of the same library is not easy as you think, basically once a developer wants to install version X while then another people want to deploy things based on version Y, how to crack this nut? You can't just care about runtime. Then you need to patch one or the other package to work with the same version. Only if that is not possible, a compatibility library can be considered. But we should always first try to make everything work with the same version (if possible, the newer one). The requirement to work with multiple versions of a package come up in the scientific/HPC community very frequently. Its not always about API compatibility, sometimes exact numerical reproduction is required which isn't preserved even between minor versions (i.e. an OS update). I don't buy this argument wrt. Fedora. Fedora is a rapid moving, forward looking distro, in which such regressions should be fixed and not be worked around by compat-libs. Ralf I guess the main point is missed completely. The main proposal is not mainly about compatibility. It's about providing latest development libraries in stable releases for *user* consumption (not for distro one). Also, the compatibility package is solely provided for user consumption; *no* Fedora package should be built against it (unless it happens already). There are some arguments against providing such thing in Fedora, but if someone wants to install two versions of the same library (e.g. installing the latest version for development while having default version for Fedora packages); he'll do it anyway. So, if such packages are not provided by Fedora, he will install from source. So, the user will install multiple versions anyway. Do you want to support him, or not? Regards, Hedayat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Broken already (was: Re: How to install Rawhide?)
Also the -02-18 one for Rawhide x86_64 Live Workstation, which started fine and managed to install, too. Haven't rebooted yet, though. It has been broken already by the first bunch of updates (62 or 63 pkgs). Oh no! Something has gone wrong [Logout] prior to GDM greeting screen coming up. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Proposal to (formally/easily) allowing multiple versions of the same library installable
On 02/16/2015 08:17 AM, Ralf Corsepius wrote: On 02/16/2015 05:10 PM, Martyn Foster wrote: On 16 February 2015 at 15:12, Kevin Kofler kevin.kof...@chello.at mailto:kevin.kof...@chello.at wrote: Christopher Meng wrote: Maintaining several version of the same library is not easy as you think, basically once a developer wants to install version X while then another people want to deploy things based on version Y, how to crack this nut? You can't just care about runtime. Then you need to patch one or the other package to work with the same version. Only if that is not possible, a compatibility library can be considered. But we should always first try to make everything work with the same version (if possible, the newer one). The requirement to work with multiple versions of a package come up in the scientific/HPC community very frequently. Its not always about API compatibility, sometimes exact numerical reproduction is required which isn't preserved even between minor versions (i.e. an OS update). I don't buy this argument wrt. Fedora. Fedora is a rapid moving, forward looking distro, in which such regressions should be fixed and not be worked around by compat-libs. Ralf Since Fedora serves as a blueprint for RHEL, CentOS, and Scientific Linux, which do get used in the scientific community and encounter the issues Martyn mentioned, any technical framework that Fedora develops to handle those issues would do the larger community quite a service, even if it does not get used that often by Fedora users. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1194637] New: perl-constant-defer-6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194637 Bug ID: 1194637 Summary: perl-constant-defer-6 is available Product: Fedora Version: rawhide Component: perl-constant-defer Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Latest upstream release: 6 Current version/release in rawhide: 5-8.fc22 URL: http://search.cpan.org/dist/constant-defer/ 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. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=wAYJ2m6wGPa=cc_unsubscribe -- 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 1194637] perl-constant-defer-6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194637 --- Comment #1 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Scratch build succeeded http://koji.fedoraproject.org/koji/taskinfo?taskID=9004870 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=u4NlUSv9F5a=cc_unsubscribe -- 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
[Base] Base Design WG agenda meeting 20 February 2015 15:00 UTC on #fedora-meeting
Agenda: - Vote for new chairman of the Base Design WG to replace Phil Knirsch - Open Floor -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[fusioninventory-agent/f21] (4 commits) ...commenting unused source
Summary of changes: 8a4a710... initial import (#1090933) (*) 0d0bf02... updating description and using upstream unit file (*) b2d4eb0... changing tab into spaces (*) e6b3bee... commenting unused source (*) (*) 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
[fusioninventory-agent/f20] (4 commits) ...commenting unused source
Summary of changes: 8a4a710... initial import (#1090933) (*) 0d0bf02... updating description and using upstream unit file (*) b2d4eb0... changing tab into spaces (*) e6b3bee... commenting unused source (*) (*) 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
[fusioninventory-agent/epel7] (4 commits) ...commenting unused source
Summary of changes: 8a4a710... initial import (#1090933) (*) 0d0bf02... updating description and using upstream unit file (*) b2d4eb0... changing tab into spaces (*) e6b3bee... commenting unused source (*) (*) 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
Gnome in F22 not automouting sdcards / usb-sticks
Hi All, I've upgraded both my main workstation as well as my laptop to F22, and I've noticed that my stock Gnome desktop no longer automounts sdcards / usbsticks. If I start files it sees the device show up just fine, and double clicking mounts it, but it no longer gets mounted automatically, even if I plug it in after I login. Is this change deliberate ? If so is there an option to change back to the old behavior. If this is not deliberate, are other people seeing this ? And if no one else is seeing this how do I debug this ? Regards, Hans -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1188538] perl-Fsdb-2.55-1.fc22 FTBFS: t/test_command.t tests fail
https://bugzilla.redhat.com/show_bug.cgi?id=1188538 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Fixed In Version|perl-Fsdb-2.56-1.fc21 |perl-Fsdb-2.56-1.el7 --- Comment #8 from Fedora Update System upda...@fedoraproject.org --- perl-Fsdb-2.56-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ngegVGS5IHa=cc_unsubscribe -- 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 1188820] perl-MCE-1.600 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1188820 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- perl-MCE-1.600-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=RwNCY8z4O2a=cc_unsubscribe -- 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 1188820] perl-MCE-1.600 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1188820 --- Comment #8 from Fedora Update System upda...@fedoraproject.org --- perl-MCE-1.600-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=eBwBzQVjxia=cc_unsubscribe -- 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
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 99 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3989/cross-binutils-2.23.88.0.1-2.el7.1 17 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0610/qpid-cpp-0.30-9.el7 15 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0626/perl-Gtk2-1.2495-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing cl-asdf-20101028-8.el7 cmocka-1.0.0-1.el7 common-lisp-controller-7.4-8.el7 dl_poly-1.9.20140324-7.el7 dspam-3.10.2-10.el7 knot-1.6.2-1.el7 mate-screensaver-1.8.1-2.el7 mdbtools-0.7.1-3.el7 meld-3.13.0-2.el7 mock-1.2.7-1.el7 notify-python-0.1.1-28.el7 php-pear-phing-2.10.1-1.el7 pyhoca-gui-0.5.0.3-1.el7 python-XStatic-termjs-0.0.4.2-1.el7 python-x2go-0.5.0.2-1.el7 qelectrotech-0.40-1.el7 roundcubemail-1.1.0-1.el7 sbcl-1.2.8-1.el7 shinken-2.2-1.el7 Details about builds: cl-asdf-20101028-8.el7 (FEDORA-EPEL-2015-0883) Another System Definition Facility Update Information: Bringing sbcl to epel7 References: [ 1 ] Bug #1188126 - SBCL for EPEL7 https://bugzilla.redhat.com/show_bug.cgi?id=1188126 cmocka-1.0.0-1.el7 (FEDORA-EPEL-2015-0871) Lightweight library to simplify and generalize unit tests for C Update Information: Update to version 1.0.0 ChangeLog: * Mon Feb 16 2015 Andreas Schneider a...@redhat.com - 1.0.0-1 - Update to version 1.0.0: * Added new test runner with group fixtures. The old runner is deprecated * Added an extensible message output formatter * Added jUnit XML message output * Added subunit message output * Added Test Anything Protocol message output * Added skip() command * Added test_realloc() * Added a cmockery compat header * Fixed a lot of bugs on Windows common-lisp-controller-7.4-8.el7 (FEDORA-EPEL-2015-0883) Common Lisp source and compiler manager Update Information: Bringing sbcl to epel7 References: [ 1 ] Bug #1188126 - SBCL for EPEL7 https://bugzilla.redhat.com/show_bug.cgi?id=1188126 dl_poly-1.9.20140324-7.el7 (FEDORA-EPEL-2015-0876) General purpose classical molecular dynamics (MD) simulation Update Information: New package References: [ 1 ] Bug #1107800 - Review Request: dl_poly - General purpose classical molecular dynamics (MD) simulation https://bugzilla.redhat.com/show_bug.cgi?id=1107800 dspam-3.10.2-10.el7 (FEDORA-EPEL-2015-0884) A library and Mail Delivery Agent for Bayesian SPAM filtering Update Information: Fixes an improper call to free() in sqlite3 driver Changes sqlite3 driver to not use auto_commit mode Updates the dspamc permissions to match the dspam binary Updated dspamc permissions ChangeLog: * Thu Feb 19 2015 Nathanael Noblet nathan...@gnat.ca - 3.10.2-10 - Fix for bug #1193177 References: [ 1 ] Bug #1193177 - sqlite3_drv bad memory free and severe performance bug - with patch https://bugzilla.redhat.com/show_bug.cgi?id=1193177 [ 2 ] Bug #1185489 - permissions of dspamc different than dspam https://bugzilla.redhat.com/show_bug.cgi?id=1185489 knot-1.6.2-1.el7 (FEDORA-EPEL-2015-0881) An authoritative DNS daemon
[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 1034 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6 124 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3434/pylint-1.3.1-1.el6,python-astroid-1.2.1-2.el6,python-logilab-common-0.62.1-2.el6 99 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4008/cross-binutils-2.23.51.0.3-1.el6.1 87 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4242/facter-1.6.18-8.el6 76 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4485/python-tornado-2.2.1-7.el6 58 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4884/mapserver-6.0.4-1.el6 56 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4918/dokuwiki-0-0.23.20140929b.el6 37 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0232/chicken-4.9.0.1-2.el6 15 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0644/perl-Gtk2-1.2495-1.el6 12 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0696/drupal7-path_breadcrumbs-3.2-1.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0701/unbound-1.5.1-1.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0738/drupal6-views-2.18-1.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0740/python-crypto2.6-2.6.1-2.el6 5 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0779/drupal7-views-3.10-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing cmocka-1.0.0-1.el6 dl_poly-1.9.20140324-9.el6 drupal7-webform-4.3-1.el6 dspam-3.10.2-6.el6 golang-github-codegangsta-cli-1.2.0-2.el6 knot-1.6.2-1.el6 mingw-binutils-2.25-2.el6 mock-1.2.7-1.el6 python-bottle-0.12.6-1.el6 python-docopt-0.6.1-3.el6 shinken-2.2-1.el6 Details about builds: cmocka-1.0.0-1.el6 (FEDORA-EPEL-2015-0887) Lightweight library to simplify and generalize unit tests for C Update Information: Update to version 1.0.0 ChangeLog: * Mon Feb 16 2015 Andreas Schneider a...@redhat.com - 1.0.0-1 - Update to version 1.0.0: * Added new test runner with group fixtures. The old runner is deprecated * Added an extensible message output formatter * Added jUnit XML message output * Added subunit message output * Added Test Anything Protocol message output * Added skip() command * Added test_realloc() * Added a cmockery compat header * Fixed a lot of bugs on Windows dl_poly-1.9.20140324-9.el6 (FEDORA-EPEL-2015-0869) General purpose classical molecular dynamics (MD) simulation Update Information: Specify permissions for installed .jar References: [ 1 ] Bug #1107800 - Review Request: dl_poly - General purpose classical molecular dynamics (MD) simulation https://bugzilla.redhat.com/show_bug.cgi?id=1107800 drupal7-webform-4.3-1.el6 (FEDORA-EPEL-2015-0891) Webform is the module for making surveys in Drupal Update Information: - Update to 4.3 - Release notes can be found at https://www.drupal.org/node/2427257 - Update to 4.2 - Release notes can be found at https://www.drupal.org/node/2381793 ChangeLog: * Fri Feb 20 2015 Peter Borsa peter.bo...@gmail.com 4.3-1 - Update to 4.3 - Release notes can be found at https://www.drupal.org/node/2427257 * Tue Dec 23 2014 Peter Borsa peter.bo...@gmail.com 4.2-1 - Update to 4.2 - Release notes can be found at https://www.drupal.org/node/2381793 * Tue Nov 25 2014 Peter Borsa peter.bo...@gmail.com 4.1-2 - Fix el6 spec file * Tue Nov 25 2014 Peter Borsa peter.bo...@gmail.com 4.1-1 - Update to 4.1 - Release notes can be found at https://www.drupal.org/node/2351973 * Sat Jun 7 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org - 4.0-0.3.beta3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild References: [ 1 ] Bug #1193356 - drupal7-webform-4.3 is available https://bugzilla.redhat.com/show_bug.cgi?id=1193356 [ 2 ] Bug #1150458 - drupal7-webform-4.2 is available
[Bug 1193177] sqlite3_drv bad memory free and severe performance bug - with patch
https://bugzilla.redhat.com/show_bug.cgi?id=1193177 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #5 from Fedora Update System upda...@fedoraproject.org --- Package dspam-3.10.2-10.el7: * should fix your issue, * was pushed to the Fedora EPEL 7 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing dspam-3.10.2-10.el7' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0884/dspam-3.10.2-10.el7 then log in and leave karma (feedback). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=yWWfttJg7Qa=cc_unsubscribe -- 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
Re: openqa_fedora_tools patch: add 'all' mode
On Wed, 2015-02-18 at 10:59 -0800, Adam Williamson wrote: On Wed, 2015-02-18 at 05:33 -0500, Josef Skladanka wrote: I'd really love to see some more comments in you code, which is using the wikitcms/relval internal attributes and so on (it gets somewhat wild in places). One further note on this, in case it isn't obvious. Now fedfind, relval, and wikitcms have a unified approach to versioning in all cases - we always use the 'release, milestone, compose' concept - I intend for it always to be OK to take a 'release, milestone, compose' from fedfind and throw it at wikitcms or relval, and vice versa. To add another design note here (sorry if I'm boring people to tears): The overall flow of the openqa_fedora_tools/Wikitcms integration is that openqa runs on *images*, then can tell Wikitcms 'hey, I have some results for an image with this release, milestone and compose, can you do something with them?' and it's Wikitcms' job to figure out if it can do anything useful with those results. At present it can only do anything useful if it can find a release validation event whose version matches the image version, but that's not *inevitable*. As I suggested at the meeting this week we could, for instance, invent a new type of result page and hence python-wikitcms 'event', for storing automated test results for non-nominated nightly composes. This means there's a rather funny workflow for the 'current validation event' case: 1. OpenQA asks python-wikitcms to find the 'current validation event' 2. OpenQA asks python-wikitcms for the fedfind Release object that matches the event 2. OpenQA asks fedfind for the images from that 'Release' and tests them 3. OpenQA asks relval to report results for 'the validation event that matches the version of these images I just ran some tests on' 4. python-wikitcms does more or less the reverse of what fedfind did back at step 3, and finds (surprise surprise!) that there is a 'matching' validation event, and reports results for that In most cases the release, milestone, compose attributes for both the python-wikitcms and fedfind objects are actually identical, so they just get thrown around a few times and nothing remarkable happens. But for the special case of Rawhide nightlies, at steps 2 and 3/4, fedfind and python-wikitcms have to twiddle with the version attributes a bit: At step 2, python-wikitcms asks fedfind for a Release object for the ValidationEvent whose version attributes are release: 22, milestone: Rawhide, compose: 20150207 (for instance). fedfind.release.get_release() translates this to a Release with the version attributes release: Rawhide, milestone: '', compose: 20150207, which is appropriate for fedfind. The fedfind Image objects inherit those attributes. At step 3, OpenQA uses the fedfind Image version attributes, so it runs : relval report-auto --release Rawhide --milestone --compose 20150207 ... and python-wikitcms wiki.Wiki.get_validation_page() has to do the opposite of the conversion fedfind did: it converts 'release: Rawhide, milestone: '', compose: 20150207' back to 'release: 22, milestone: Rawhide, compose: 20150207' and finds the correct ValidationEvent. All of this is a bit baroque, but still I think actually the best way to do it given the constraints of the system and the information available: * We don't want circular deps between wikitcms and fedfind so fedfind can find the 'current validation event' itself (and then what? the Image objects for Rawhide nightly composes 'nominated for testing' would have different version attributes from the Image objects for Rawhide nightly composes *not* 'nominated for testing'?) * I don't want to remove openqa's ability to run against non-event images (which would allow us to tie it strongly to *event* versioning rather than *image* versioning). The concept of a 'validation event' is really one that's kind of bound up with manual testing, it's not an appropriate concept to tie an automatic testing system to. * We *could* special case openqa so that when it knows it's running for a specific validation event it uses the event's 'version' as the BUILD, not the image's 'version'. That would avoid the double conversion for Rawhide nightlies. But every time I write it that way, it just seems wrong. And it would mean that if the current validation event was '22 Rawhide 20150207' and you ran: openqa_trigger.py current openqa_trigger.py --release 22 --milestone Rawhide --compose 20150207 then the two sets of jobs would have *different* BUILD identifiers, which seems wrong. * I don't see a way to get openqa to run against TC/RC images using only fedfind, *without* openqa or fedfind asking python-wikitcms to find 'events' for it. It would be pretty ugly to teach fedfind to scrape stage/ so you could ask it for TCs/RCs that currently 'exist'. Unless releng is providing the information in a sanely-consumable format somewhere, Wikitcms is
[Bug 1188538] perl-Fsdb-2.55-1.fc22 FTBFS: t/test_command.t tests fail
https://bugzilla.redhat.com/show_bug.cgi?id=1188538 --- Comment #9 from John Heidemann jo...@isi.edu --- Btw, the change in perl-Getopt-Long that triggered this bug in perl-Fsdb apparently propagated across f20 and f21, not just rawhide. So this upgrade is needed across the board. The F20 change is in testing... is there an easy way to shortcut the week of quiet time to get it in stable? -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6yF6QkPEmra=cc_unsubscribe -- 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
New Upstream Release Monitoring Systems
I'm proud to announce that the Infrastructure team has finished deploying the first iteration of our replacement for the older, wiki-based Upstream Release Monitoring tools this week. You can read about the details of the trio of systems[1] now used to coordinate upstream release monitoring on the same old wiki page. Names of systems: - pkgdb is the familiar Fedora Package DB https://admin.fedoraproject.org/pkgdb It provides some flags used by the other systems. - anitya is the web app running at https://release-monitoring.org It is responsible for scraping upstream release sites looking for new releases. - the-new-hotness is a backend daemon that responds to fedmsg messages about upstream releases. The bugs filed in bugzilla look much the same as they did before, but for packagers there is one thing to note: the process of getting your package(s) registered for upstream release monitoring has changed. Please see the instructions[2] on the wiki page. Old packages that were listed on the wiki page have been imported to release-monitoring.org and have had their monitoring flag set in pkgdb. New packages added to Fedora now have their monitoring flag set to True by default and a script attempts to map them to an upstream project in release-monitoring.org automatically. If you want new upstream releases monitored for your package(s), you must: - Add the upstream project to anitya[3]. - Map the upstream project to a Fedora package in anitya[3]. - Enable the monitoring flag for that Fedora package in pkgdb2[4]. Note also that it is now possible to get notifications about upstream releases without bugs being filed in bugzilla. To do this, add your projects to release-monitoring.org and configure your Fedora Notifications (FMN)[5] account while leaving the monitor flag set to False in pkgdb[4]. If you encounter bugs or have requests for enhancement, as always please do file them[6][7][8].. and if you're having problems with a particular package there is a place to list those[8] also on the wiki page. [1] https://fedoraproject.org/wiki/Upstream_release_monitoring#Details [2] https://fedoraproject.org/wiki/Upstream_release_monitoring#TLDR.3B_Get_Packages_Monitored [3] https://release-monitoring.org [4] https://admin.fedoraproject.org/pkgdb [5] https://apps.fedoraproject.org/notifications [6] https://github.com/fedora-infra/anitya [7] https://github.com/fedora-infra/pkgdb2 [8] https://github.com/fedora-infra/the-new-hotness [9] https://fedoraproject.org/wiki/Upstream_release_monitoring#Requesting_Help signature.asc Description: PGP signature ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
New Upstream Release Monitoring Systems
I'm proud to announce that the Infrastructure team has finished deploying the first iteration of our replacement for the older, wiki-based Upstream Release Monitoring tools this week. You can read about the details of the trio of systems[1] now used to coordinate upstream release monitoring on the same old wiki page. Names of systems: - pkgdb is the familiar Fedora Package DB https://admin.fedoraproject.org/pkgdb It provides some flags used by the other systems. - anitya is the web app running at https://release-monitoring.org It is responsible for scraping upstream release sites looking for new releases. - the-new-hotness is a backend daemon that responds to fedmsg messages about upstream releases. The bugs filed in bugzilla look much the same as they did before, but for packagers there is one thing to note: the process of getting your package(s) registered for upstream release monitoring has changed. Please see the instructions[2] on the wiki page. Old packages that were listed on the wiki page have been imported to release-monitoring.org and have had their monitoring flag set in pkgdb. New packages added to Fedora now have their monitoring flag set to True by default and a script attempts to map them to an upstream project in release-monitoring.org automatically. If you want new upstream releases monitored for your package(s), you must: - Add the upstream project to anitya[3]. - Map the upstream project to a Fedora package in anitya[3]. - Enable the monitoring flag for that Fedora package in pkgdb2[4]. Note also that it is now possible to get notifications about upstream releases without bugs being filed in bugzilla. To do this, add your projects to release-monitoring.org and configure your Fedora Notifications (FMN)[5] account while leaving the monitor flag set to False in pkgdb[4]. If you encounter bugs or have requests for enhancement, as always please do file them[6][7][8].. and if you're having problems with a particular package there is a place to list those[8] also on the wiki page. [1] https://fedoraproject.org/wiki/Upstream_release_monitoring#Details [2] https://fedoraproject.org/wiki/Upstream_release_monitoring#TLDR.3B_Get_Packages_Monitored [3] https://release-monitoring.org [4] https://admin.fedoraproject.org/pkgdb [5] https://apps.fedoraproject.org/notifications [6] https://github.com/fedora-infra/anitya [7] https://github.com/fedora-infra/pkgdb2 [8] https://github.com/fedora-infra/the-new-hotness [9] https://fedoraproject.org/wiki/Upstream_release_monitoring#Requesting_Help signature.asc Description: PGP signature ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Changes in the f22 workstation
I wanted to give a heads-up to the wider audience about a number of workstation changes that are landing in the f22 branch (and rawhide) this week, in time for the alpha freeze next week: - The message tray at the bottom is gone, notifications are now shown at the top, and can be reviewed in the calendar popup ( https://fedoraproject.org/wiki/Changes/GnomeShell_NewNotifications) - The gnome-shell theme has been refreshed - The login screen is using Wayland ( https://fedoraproject.org/wiki/Changes/Login_Screen_Over_Wayland) - Codec installation has been integrated in gnome-software (currently this is hooked up in totem) - Nautilus has received a number of improvements ( https://fedoraproject.org/wiki/Changes/Nautilus_Improvements) Please let us know if you see any fallout from these changes. Thanks! Matthias -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [Test-Announce] Fedora 22 Branched 20150218 nightly compose nominated for testing
On Sat, Feb 21, 2015 at 3:13 AM, Adam Williamson adamw...@fedoraproject.org wrote: Because https://bugzilla.redhat.com/show_bug.cgi?id=1194494 . Oh, thanks. This is the second bug I've managed to miss in BZ this week, I think I need to catch up on my sleep. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [Test-Announce] Fedora 22 Branched 20150218 nightly compose nominated for testing
I downloaded the generic x86_64 boot iso from https://kojipkgs.fedoraproject.org/mash/branched-20150218/22/x86_64/os/images/boot.iso which was linked to from https://fedoraproject.org/wiki/Test_Results:Fedora_22_Branched_20150218_Installation and went on to install it in a vm on a fedora 21 host. After 3-4 unsuccessful installation attempts and a lot of tweaking in virt-manager, I managed to get it going. After it was done and rebooted, I got to a gdm screen without any users listed, I was unable to switch to another vt and when the lock screen appeared, I couldn't make it go away whether I typed on the keyboard or rolled the scroll wheel on my mouse. I could ssh to the vm, which I did and found that probably wayland is to blame for not being able to log in. However, what struck me as odd was this: # uname -a Linux localhost.localdomain 3.20.0-0.rc0.git9.1.fc23.x86_64 #1 SMP Wed Feb 18 22:01:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Why would I end up with an f23 kernel? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1185328] perl-Encode-2.68 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1185328 --- Comment #4 from Fedora Update System upda...@fedoraproject.org --- perl-Encode-2.70-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=KDdni7ay3Oa=cc_unsubscribe -- 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 1186988] GEOIP_SILENCE support needs to be added to perl-Geo-IP
https://bugzilla.redhat.com/show_bug.cgi?id=1186988 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #9 from Fedora Update System upda...@fedoraproject.org --- Package perl-Geo-IP-1.45-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing perl-Geo-IP-1.45-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2387/perl-Geo-IP-1.45-1.fc21 then log in and leave karma (feedback). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=VgF3YmNmcPa=cc_unsubscribe -- 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
Re: [Test-Announce] Fedora 22 Branched 20150218 nightly compose nominated for testing
On Sat, 2015-02-21 at 02:35 +0200, Alexander Ploumistos wrote: I downloaded the generic x86_64 boot iso from https://kojipkgs.fedoraproject.org/mash/branched-20150218/22/x86_64/os/images/boot.iso which was linked to from https://fedoraproject.org/wiki/Test_Results:Fedora_22_Branched_20150218_Installation and went on to install it in a vm on a fedora 21 host. After 3-4 unsuccessful installation attempts and a lot of tweaking in virt- manager, I managed to get it going. After it was done and rebooted, I got to a gdm screen without any users listed, I was unable to switch to another vt and when the lock screen appeared, I couldn't make it go away whether I typed on the keyboard or rolled the scroll wheel on my mouse. I could ssh to the vm, which I did and found that probably wayland is to blame for not being able to log in. However, what struck me as odd was this: # uname -a Linux localhost.localdomain 3.20.0-0.rc0.git9.1.fc23.x86_64 #1 SMP Wed Feb 18 22:01:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Why would I end up with an f23 kernel? Because https://bugzilla.redhat.com/show_bug.cgi?id=1194494 . -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Test-Announce] Proposal to CANCEL: 2015-02-23 Fedora QA Meeting
Hi folks! I'm tentatively suggesting we cancel the QA meeting on Monday, but that's assuming we do a blocker review meeting. I think it'd be good to check in on the status of 22 Alpha in general, but we can do that within the blocker review meeting assuming we have one. I don't think we have any other big topics to discuss, but I'm making sure to get this email out several days ahead so we can change our minds and have a meeting if necessary. So did I miss anything? Anyone have anything we should talk about? Just reply to this mail and we can set up the meeting. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Changes in the f22 workstation
Hi, On Fri, Feb 20, 2015 at 7:00 PM, Pete Travis li...@petetravis.com wrote: I'm nervous about GDM on Wayland; Wayland has never worked well on my systems. Can you talk about fallback strategies a bit? Can GDM detect when Wayland isn't working well enough to be usable, and cleanly fall back? It tries to. We do start X in a different way now when falling back (as part of the user session, instead of as root outside of the user session), so there may be bugs that need to get ironed out. It worked okay in my limited testing though (putting nomodeset on the kernel commandline on my intel based laptop) That's probably a big ask, though; presumably this can be set one way or another by the user? Right you can put WaylandEnable=false in the [daemon] section of /etc/gdm/custom.conf to skip wayland altogether. --Ray -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [Proposal] Ring-based Packaging Policies
On Thu, Feb 12, 2015 at 01:32:04PM -0500, Stephen Gallagher wrote: === Core Packages === Any package that is provided on a release-blocking medium (which at present includes Fedora Atomic, Fedora Cloud, Fedora Server, Fedora Workstation, the KDE Spin and several ARM images) must comply exactly with the packaging guidelines as they are written today. [...] === Ring Packages === Any new package that is *not* going to be part of the install media set is required to pass a lighter review and is permitted to carry bundled libraries, with caveats to be listed below. What would be the place for higher-quality packages that aren't on any install media (and are also not required to create those)? I think a broad collection of reviewed and guideline-conforming packages is a useful thing to have. Just mixing them together in a single repo with the lower-quality stuff would diminish their value in significant ways. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1188538] perl-Fsdb-2.55-1.fc22 FTBFS: t/test_command.t tests fail
https://bugzilla.redhat.com/show_bug.cgi?id=1188538 --- Comment #10 from Jason Tibbitts ti...@math.uh.edu --- It should push much sooner if the update can get three positive karma. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=WDtdsyWthua=cc_unsubscribe -- 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
Re: Self introduction: Taylor Braun-Jones
On 02/20/2015 08:17 PM, Taylor Braun-Jones wrote: Hi everyone, I am going through the process of becoming a Fedora Package Collection maintainer and wanted to say hi and introduce myself. I've been a Linux user since 2000, extensively since about 2002. I currently work in software RD for a medical device company and am a big proponent of using open source software to accomplish what we do. Qt, ITK, VTK, MITK, cmake are some of the packages work with the most. I've maintained a private YUM repos for RHEL6 and RHEL7 packages that we use but a lot of these packages make more sense in the public Fedora repos so I'd like to start contributing and maintaining them there. I look forward to working/playing with you all. Welcome! I'm the current maintainer for VTK and cmake and would welcome any and all help maintaining any of my packages. I'm current in the process of working on the VTK 6.2.0 update and staging builds here: https://copr.fedoraproject.org/coprs/orion/VTK/ - Orion -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1194637] perl-constant-defer-6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194637 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #9 from Fedora Update System upda...@fedoraproject.org --- Package perl-constant-defer-6-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing perl-constant-defer-6-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2364/perl-constant-defer-6-1.fc21 then log in and leave karma (feedback). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=jQpLbLWSBFa=cc_unsubscribe -- 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
RE: nonresponsive maintainer - Axel Thimm
Also I can help in some packages. Access Asked fakechroot,fakeroot,freenx-server,greylistd,synaptic,fedora-package-config-apt,apt Mosaab From: fdc-li...@fcami.net Date: Wed, 18 Feb 2015 10:24:04 +0100 Subject: Re: nonresponsive maintainer - Axel Thimm To: devel@lists.fedoraproject.org CC: axel.th...@atrpms.net On Wed, Feb 18, 2015 at 5:20 AM, Orion Poplawski or...@cora.nwra.com wrote: I'm continuing the nonresponsive maintainer process for Axel Thimm https://bugzilla.redhat.com/show_bug.cgi?id=1186467 +1 I've been effectively maintaining a number of Axel's packages for years now. Time to get them properly owned. Does anyone know how to contact Axel? I can help maintain vtk/vtkdata/fail2ban and possibly others if needed. François -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Strange issues with octave+swig+UTF8 in rawhide
The check in the plplot package for the octave bindings are failing in rawhide. I point my finger at gcc :), but I have no idea what is going on so just putting this out there. plplot uses a swig generated interface for the octave wrapper. By the time the swig wrapper is calling the plplot C function I'm seeing UTF8 string pointers pointing to garbage (or perhaps just off by a byte, who knows). I've rebuilt swig, then octave, but no avail. So, if anyone sees anything strange in this regard and fixes it, let me know. - Orion -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Changes in the f22 workstation
On Feb 20, 2015 2:09 PM, Matthias Clasen mcla...@redhat.com wrote: I wanted to give a heads-up to the wider audience about a number of workstation changes that are landing in the f22 branch (and rawhide) this week, in time for the alpha freeze next week: - The message tray at the bottom is gone, notifications are now shown at the top, and can be reviewed in the calendar popup ( https://fedoraproject.org/wiki/Changes/GnomeShell_NewNotifications) - The gnome-shell theme has been refreshed - The login screen is using Wayland ( https://fedoraproject.org/wiki/Changes/Login_Screen_Over_Wayland) - Codec installation has been integrated in gnome-software (currently this is hooked up in totem) - Nautilus has received a number of improvements ( https://fedoraproject.org/wiki/Changes/Nautilus_Improvements) Please let us know if you see any fallout from these changes. Thanks! Matthias -- I'm nervous about GDM on Wayland; Wayland has never worked well on my systems. Can you talk about fallback strategies a bit? Can GDM detect when Wayland isn't working well enough to be usable, and cleanly fall back? That's probably a big ask, though; presumably this can be set one way or another by the user? --Pete -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Test-Announce] 2015-02-23 @ 1700 UTC ** Blocker Review Meeting
# F22 Blocker Review meeting # Date: 2015-02-23 # Time: 1700 UTC # Location: #fedora-blocker-review on irc.freenode.net It's that time of the week again! After another week of testing we have 4 proposed Alpha blockers and 2 proposed for final. If you want to take a look at the proposed or accepted blockers, the full list can be found here: https://qa.fedoraproject.org/blockerbugs/ Make sure to click through the milestones to see how many we have before the meeting! We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F22 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Changes in the f22 workstation
On 20/02/15 21:09, Matthias Clasen wrote: I wanted to give a heads-up to the wider audience about a number of workstation changes that are landing in the f22 branch (and rawhide) this week, in time for the alpha freeze next week: - The message tray at the bottom is gone, notifications are now shown at the top, and can be reviewed in the calendar popup ( https://fedoraproject.org/wiki/Changes/GnomeShell_NewNotifications) This does seem like an improvement, following the general improvement in notifications with each release. However I'm surprised that there is still no mention of a permanent indicator in the top bar, that notifications are present. This can be achieved with an extension, but with large changes to notifications happening now, it would seem like an ideal time to also introduce that change. If you drill down through the comments at the above URL, you get to this: https://bugzilla.gnome.org/show_bug.cgi?id=641723 thanks, Pádraig. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Self introduction: Taylor Braun-Jones
Hi everyone, I am going through the process of becoming a Fedora Package Collection maintainer and wanted to say hi and introduce myself. I've been a Linux user since 2000, extensively since about 2002. I currently work in software RD for a medical device company and am a big proponent of using open source software to accomplish what we do. Qt, ITK, VTK, MITK, cmake are some of the packages work with the most. I've maintained a private YUM repos for RHEL6 and RHEL7 packages that we use but a lot of these packages make more sense in the public Fedora repos so I'd like to start contributing and maintaining them there. I look forward to working/playing with you all. Cheers, Taylor http://taylor.braun-jones.org/meet-me/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Gnome in F22 not automouting sdcards / usb-sticks
On Fri, Feb 20, 2015 at 2:54 PM, Hans de Goede hdego...@redhat.com wrote: Hi All, I've upgraded both my main workstation as well as my laptop to F22, and I've noticed that my stock Gnome desktop no longer automounts sdcards / usbsticks. If I start files it sees the device show up just fine, and double clicking mounts it, but it no longer gets mounted automatically, even if I plug it in after I login. Is this change deliberate ? If so is there an option to change back to the old behavior. If this is not deliberate, are other people seeing this ? And if no one else is seeing this how do I debug this ? I'm seeing this too, on some devices I'm evening seeing the device show up in dmesg etc but device nodes not being created for the device even though it sees partitions etc so I'm wondering if it's actually lower down the stack from gnome. Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: systemd-219 issues with 22 and Rawhide composes
On Fri, 20.02.15 16:03, Peter Robinson (pbrobin...@gmail.com) wrote: On Fri, Feb 20, 2015 at 3:47 PM, Harald Hoyer har...@redhat.com wrote: To prevent surprises on the next systemd updates like in https://bugzilla.redhat.com/show_bug.cgi?id=1116651, we will not apply workarounds anymore in rawhide and track the issues on https://bugzilla.redhat.com/show_bug.cgi?id=systemd-other-tracker so, that they are not forgotten. We removed the change for /etc/resolv.conf in F22 again (like in F21), but this time we keep the change for rawhide. Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. Are you going to start notifying deve@ of upcoming changes that may impact other areas of the distro too rather than just land them without notification or discussion? Oh god, stop this, will you? The folks in question knew I would drop the patch. In the original bug I even said I would remove the work-around from systemd.rpm after TC1 of the last cycle. I was nice, left it in for the whole cycle, only dropped it now. There is no news in all of this, I just removed the work-around now, as indicated back then. How many months would you like me to notify people in advance of a simple change like this? Isn't 6 month *ample* time? How much time do you think is appropriate for fixing a file copy routine in anaconda? 12 months? 18 months? 2 years? Also, NM fixed a similar issue with /etc/resolve.conf in their code a long time ago, to my knowledge. Am I so misguided to assume that Anaconda can fix a fricking file copy too, in all those months? Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[perl-Perl4-CoreLibs/f22] (3 commits) ...Sort provides by English rules
Summary of changes: 090172c... Import (*) c6bffdb... Do not build-require File::Find, Socket, and warnings::regi (*) 2e2d575... Sort provides by English rules (*) (*) 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-Perl4-CoreLibs/f21] (3 commits) ...Sort provides by English rules
Summary of changes: 090172c... Import (*) c6bffdb... Do not build-require File::Find, Socket, and warnings::regi (*) 2e2d575... Sort provides by English rules (*) (*) 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
[PkgDB] ppisar:perl-Perl4-CoreLibs watchbugzilla set to Obsolete
user: ppisar set for ppisar acl: watchbugzilla of package: perl-Perl4-CoreLibs from: Approved to: Obsolete on branch: f22 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Perl4-CoreLibs -- 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
[PkgDB] ppisar:perl-Perl4-CoreLibs watchcommits set to Obsolete
user: ppisar set for ppisar acl: watchcommits of package: perl-Perl4-CoreLibs from: Approved to: Obsolete on branch: f20 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Perl4-CoreLibs -- 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
[fusioninventory-agent/f22] building as noarch
Summary of changes: 15aae5f... building as noarch (*) (*) 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
Re: Proposal to (formally/easily) allowing multiple versions of the same library installable
Hi On Mon, Feb 16, 2015 at 11:17 AM, Ralf Corsepius wrote: I don't buy this argument wrt. Fedora. Fedora is a rapid moving, forward looking distro, in which such regressions should be fixed and not be worked around by compat-libs. In ideal conditions, this is fine but in the real world, people do have to use older versions of libraries because debugging issues in newer versions isn't a priority and won't be for a lot of users. Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
File Perl4-CoreLibs-0.003.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Perl4-CoreLibs: f74747c234470a087871f564a5f5db15 Perl4-CoreLibs-0.003.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-Perl4-CoreLibs] Import
commit 090172c8f2659ec057bfa86c43a82197da3d58f6
Author: Petr Písař ppi...@redhat.com
Date: Fri Feb 20 17:04:03 2015 +0100
Import
.gitignore | 1 +
perl-Perl4-CoreLibs.spec | 101 +++
sources | 1 +
3 files changed, 103 insertions(+)
---
diff --git a/.gitignore b/.gitignore
index e69de29..b75a9ec 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/Perl4-CoreLibs-0.003.tar.gz
diff --git a/perl-Perl4-CoreLibs.spec b/perl-Perl4-CoreLibs.spec
new file mode 100644
index 000..5efac38
--- /dev/null
+++ b/perl-Perl4-CoreLibs.spec
@@ -0,0 +1,101 @@
+Name: perl-Perl4-CoreLibs
+Version:0.003
+Release:1%{?dist}
+Summary:Libraries historically supplied with Perl 4
+License:GPL+ or Artistic
+Group: Development/Libraries
+URL:http://search.cpan.org/dist/Perl4-CoreLibs/
+Source0:
http://www.cpan.org/authors/id/Z/ZE/ZEFRAM/Perl4-CoreLibs-%{version}.tar.gz
+BuildArch: noarch
+BuildRequires: perl
+BuildRequires: perl(Module::Build) = 0.26
+BuildRequires: perl(strict)
+BuildRequires: perl(warnings)
+# Run-time:
+BuildRequires: perl(File::Find)
+BuildRequires: perl(IPC::Open2)
+BuildRequires: perl(IPC::Open3)
+# Prefer Socket over socket.ph
+BuildRequires: perl(Socket)
+BuildRequires: perl(Text::ParseWords) = 3.25
+BuildRequires: perl(Time::Local)
+BuildRequires: perl(warnings::register)
+# Tests:
+BuildRequires: perl(Config)
+BuildRequires: perl(IO::Handle)
+BuildRequires: perl(Test::More)
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
+Requires: perl(File::Find)
+Requires: perl(IPC::Open2)
+Requires: perl(IPC::Open3)
+Requires: perl(Socket)
+Requires: perl(Text::ParseWords) = 3.25
+Requires: perl(Time::Local)
+Requires: perl(warnings::register)
+# Dependencies on these Perl 4 files are generated as perl(foo.pl):
+Provides: perl(abbrev.pl) = %{version}
+Provides: perl(assert.pl) = %{version}
+Provides: perl(bigfloat.pl) = %{version}
+Provides: perl(bigint.pl) = %{version}
+Provides: perl(bigrat.pl) = %{version}
+Provides: perl(cacheout.pl) = %{version}
+Provides: perl(complete.pl) = %{version}
+Provides: perl(ctime.pl) = %{version}
+Provides: perl(dotsh.pl) = %{version}
+Provides: perl(exceptions.pl) = %{version}
+Provides: perl(fastcwd.pl) = %{version}
+Provides: perl(finddepth.pl) = %{version}
+Provides: perl(find.pl) = %{version}
+Provides: perl(flush.pl) = %{version}
+Provides: perl(ftp.pl) = %{version}
+Provides: perl(getcwd.pl) = %{version}
+Provides: perl(getopt.pl) = %{version}
+Provides: perl(getopts.pl) = %{version}
+Provides: perl(hostname.pl) = %{version}
+Provides: perl(chat2.pl) = %{version}
+Provides: perl(importenv.pl) = %{version}
+Provides: perl(look.pl) = %{version}
+# newgetopt.pl is distributed by Getopt-Long, CPAN RT#102212
+Provides: perl(open2.pl) = %{version}
+Provides: perl(open3.pl) = %{version}
+Provides: perl(pwd.pl) = %{version}
+Provides: perl(shellwords.pl) = %{version}
+Provides: perl(stat.pl) = %{version}
+Provides: perl(syslog.pl) = %{version}
+Provides: perl(tainted.pl) = %{version}
+Provides: perl(termcap.pl) = %{version}
+Provides: perl(timelocal.pl) = %{version}
+Provides: perl(validate.pl) = %{version}
+
+%description
+This is a collection of .pl files that have historically been bundled with the
+Perl core and were removed from perl 5.16. These files should not be used by
+new code. Functionally, most have been directly superseded by modules in the
+Perl 5 style. This collection exists to support old Perl programs that
+predates satisfactory replacements.
+
+%prep
+%setup -q -n Perl4-CoreLibs-%{version}
+# newgetopt.pl is distributed by Getopt-Long, CPAN RT#102212
+rm lib/newgetopt.pl
+sed -i -e '/^lib\/newgetopt\.pl/d' MANIFEST
+
+%build
+perl Build.PL installdirs=vendor
+./Build
+
+%install
+./Build install destdir=$RPM_BUILD_ROOT create_packlist=0
+%{_fixperms} $RPM_BUILD_ROOT/*
+
+%check
+./Build test
+
+%files
+%doc Changes README
+%{perl_vendorlib}/*
+%{_mandir}/man3/*
+
+%changelog
+* Thu Feb 19 2015 Petr Pisar ppi...@redhat.com 0.003-1
+- Specfile autogenerated by cpanspec 1.78.
diff --git a/sources b/sources
index e69de29..81d5924 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+f74747c234470a087871f564a5f5db15 Perl4-CoreLibs-0.003.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-Perl4-CoreLibs] Do not build-require File::Find, Socket, and warnings::register
commit c6bffdb8cd2f780e87eec6f090624d531e07dafc Author: Petr Písař ppi...@redhat.com Date: Fri Feb 20 17:10:00 2015 +0100 Do not build-require File::Find, Socket, and warnings::register perl-Perl4-CoreLibs.spec | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) --- diff --git a/perl-Perl4-CoreLibs.spec b/perl-Perl4-CoreLibs.spec index 5efac38..dc8b2c9 100644 --- a/perl-Perl4-CoreLibs.spec +++ b/perl-Perl4-CoreLibs.spec @@ -12,14 +12,14 @@ BuildRequires: perl(Module::Build) = 0.26 BuildRequires: perl(strict) BuildRequires: perl(warnings) # Run-time: -BuildRequires: perl(File::Find) +# File::Find not used at tests BuildRequires: perl(IPC::Open2) BuildRequires: perl(IPC::Open3) # Prefer Socket over socket.ph -BuildRequires: perl(Socket) +# Socket not used at tests BuildRequires: perl(Text::ParseWords) = 3.25 BuildRequires: perl(Time::Local) -BuildRequires: perl(warnings::register) +# warnings::register not used at tests # Tests: BuildRequires: perl(Config) BuildRequires: perl(IO::Handle) @@ -99,3 +99,5 @@ perl Build.PL installdirs=vendor %changelog * Thu Feb 19 2015 Petr Pisar ppi...@redhat.com 0.003-1 - Specfile autogenerated by cpanspec 1.78. +- Do not build-require File::Find, Socket, and warnings::register which are + not exercised by tests -- 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-Perl4-CoreLibs] Sort provides by English rules
commit 2e2d575969b0bac4a746fe267c4c4e9b2feebc45
Author: Petr Písař ppi...@redhat.com
Date: Fri Feb 20 17:12:12 2015 +0100
Sort provides by English rules
perl-Perl4-CoreLibs.spec | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
---
diff --git a/perl-Perl4-CoreLibs.spec b/perl-Perl4-CoreLibs.spec
index dc8b2c9..36cdcde 100644
--- a/perl-Perl4-CoreLibs.spec
+++ b/perl-Perl4-CoreLibs.spec
@@ -39,6 +39,7 @@ Provides: perl(bigfloat.pl) = %{version}
Provides: perl(bigint.pl) = %{version}
Provides: perl(bigrat.pl) = %{version}
Provides: perl(cacheout.pl) = %{version}
+Provides: perl(chat2.pl) = %{version}
Provides: perl(complete.pl) = %{version}
Provides: perl(ctime.pl) = %{version}
Provides: perl(dotsh.pl) = %{version}
@@ -52,7 +53,6 @@ Provides: perl(getcwd.pl) = %{version}
Provides: perl(getopt.pl) = %{version}
Provides: perl(getopts.pl) = %{version}
Provides: perl(hostname.pl) = %{version}
-Provides: perl(chat2.pl) = %{version}
Provides: perl(importenv.pl) = %{version}
Provides: perl(look.pl) = %{version}
# newgetopt.pl is distributed by Getopt-Long, CPAN RT#102212
@@ -101,3 +101,4 @@ perl Build.PL installdirs=vendor
- Specfile autogenerated by cpanspec 1.78.
- Do not build-require File::Find, Socket, and warnings::register which are
not exercised by tests
+- Sort provides by English rules
--
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
[PkgDB] ppisar:perl-Perl4-CoreLibs watchcommits set to Obsolete
user: ppisar set for ppisar acl: watchcommits of package: perl-Perl4-CoreLibs from: Approved to: Obsolete on branch: master To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Perl4-CoreLibs -- 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-Perl4-CoreLibs/f20] (3 commits) ...Sort provides by English rules
Summary of changes: 090172c... Import (*) c6bffdb... Do not build-require File::Find, Socket, and warnings::regi (*) 2e2d575... Sort provides by English rules (*) (*) 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
Re: [Base] Base Design WG agenda meeting 20 February 2015 15:00 UTC on #fedora-meeting
On 20.02.2015 14:35, Harald Hoyer wrote: Agenda: - Vote for new chairman of the Base Design WG to replace Phil Knirsch - Open Floor Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2015-02-20/fedora_base_design_working_group.2015-02-20-15.01.html Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2015-02-20/fedora_base_design_working_group.2015-02-20-15.01.txt Log: http://meetbot.fedoraproject.org/fedora-meeting/2015-02-20/fedora_base_design_working_group.2015-02-20-15.01.log.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[fusioninventory-agent] building as noarch
commit 15aae5f34513b476d24f58c4e8caa45d5477a1e6
Author: jehane maria...@tuxette.fr
Date: Fri Feb 20 16:10:07 2015 +0100
building as noarch
fusioninventory-agent.spec | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
---
diff --git a/fusioninventory-agent.spec b/fusioninventory-agent.spec
index 65d9499..8f68510 100644
--- a/fusioninventory-agent.spec
+++ b/fusioninventory-agent.spec
@@ -5,9 +5,9 @@ License: GPLv2+
URL: http://fusioninventory.org/
Version: 2.3.15
-Release: 2%{?dist}
+Release: 3%{?dist}
+BuildArch: noarch
Source0:
http://search.cpan.org/CPAN/authors/id/G/GR/GROUSSE/FusionInventory-Agent-%{version}%{?prever}.tar.gz
-
Source1: %{name}.cron
#Source2: %{name}.init
#Source3: %{name}.service
@@ -278,6 +278,9 @@ install -m 644 -D contrib/yum-plugin/%{name}.conf
%{buildroot}%{_sysconfdir}/yum
%changelog
+* Fri Feb 20 2015 Marianne Lombard - 2.3.15-3
+- building as noarch
+
* Wed Feb 11 2015 Marianne Lombard maria...@tuxette.fr - 2.3.15-2
- fix description of subpackage
- using upstream systemd unit file
--
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
systemd-219 issues with 22 and Rawhide composes
To prevent surprises on the next systemd updates like in https://bugzilla.redhat.com/show_bug.cgi?id=1116651, we will not apply workarounds anymore in rawhide and track the issues on https://bugzilla.redhat.com/show_bug.cgi?id=systemd-other-tracker so, that they are not forgotten. We removed the change for /etc/resolv.conf in F22 again (like in F21), but this time we keep the change for rawhide. Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: systemd-219 issues with 22 and Rawhide composes
On Fri, Feb 20, 2015 at 3:47 PM, Harald Hoyer har...@redhat.com wrote: To prevent surprises on the next systemd updates like in https://bugzilla.redhat.com/show_bug.cgi?id=1116651, we will not apply workarounds anymore in rawhide and track the issues on https://bugzilla.redhat.com/show_bug.cgi?id=systemd-other-tracker so, that they are not forgotten. We removed the change for /etc/resolv.conf in F22 again (like in F21), but this time we keep the change for rawhide. Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. Are you going to start notifying deve@ of upcoming changes that may impact other areas of the distro too rather than just land them without notification or discussion? Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[PkgDB] ppisar:perl-Perl4-CoreLibs watchcommits set to Obsolete
user: ppisar set for ppisar acl: watchcommits of package: perl-Perl4-CoreLibs from: Approved to: Obsolete on branch: f22 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Perl4-CoreLibs -- 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
[PkgDB] ppisar:perl-Perl4-CoreLibs watchcommits set to Obsolete
user: ppisar set for ppisar acl: watchcommits of package: perl-Perl4-CoreLibs from: Approved to: Obsolete on branch: f21 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Perl4-CoreLibs -- 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
[PkgDB] ppisar:perl-Perl4-CoreLibs watchbugzilla set to Obsolete
user: ppisar set for ppisar acl: watchbugzilla of package: perl-Perl4-CoreLibs from: Approved to: Obsolete on branch: f20 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Perl4-CoreLibs -- 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
[PkgDB] ppisar:perl-Perl4-CoreLibs watchbugzilla set to Obsolete
user: ppisar set for ppisar acl: watchbugzilla of package: perl-Perl4-CoreLibs from: Approved to: Obsolete on branch: master To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Perl4-CoreLibs -- 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
[PkgDB] ppisar:perl-Perl4-CoreLibs watchbugzilla set to Obsolete
user: ppisar set for ppisar acl: watchbugzilla of package: perl-Perl4-CoreLibs from: Approved to: Obsolete on branch: f21 To make changes to this package see: https://admin.fedoraproject.org/pkgdb/package/perl-Perl4-CoreLibs -- 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
Re: systemd-219 issues with 22 and Rawhide composes
On Fri, Feb 20, 2015 at 4:11 PM, Lennart Poettering mzerq...@0pointer.de wrote: On Fri, 20.02.15 16:03, Peter Robinson (pbrobin...@gmail.com) wrote: On Fri, Feb 20, 2015 at 3:47 PM, Harald Hoyer har...@redhat.com wrote: To prevent surprises on the next systemd updates like in https://bugzilla.redhat.com/show_bug.cgi?id=1116651, we will not apply workarounds anymore in rawhide and track the issues on https://bugzilla.redhat.com/show_bug.cgi?id=systemd-other-tracker so, that they are not forgotten. We removed the change for /etc/resolv.conf in F22 again (like in F21), but this time we keep the change for rawhide. Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. Are you going to start notifying deve@ of upcoming changes that may impact other areas of the distro too rather than just land them without notification or discussion? Oh god, stop this, will you? No, I mean the above in general for general changes you make that affect the distro as a whole. You generally land them without notification. The folks in question knew I would drop the patch. In the original bug I even said I would remove the work-around from systemd.rpm after TC1 of the last cycle. I was nice, left it in for the whole cycle, only dropped it now. Yes, and it looks like it affects dhcpd too... just because you notified one dev team on a single bug it's not the same as a wider announcement to the wider community. There's all sorts of things that this can affect, and while yes it may be a bug in their software, it should be as widely notified as possible. People have priorities that may not be the same as yours. There is no news in all of this, I just removed the work-around now, as indicated back then. Again, I'm not just referring to this single incident, it would be nice if you notified people widely of changes. It's a community, people don't all follow closely the upstream development of all upstream components. How many months would you like me to notify people in advance of a simple change like this? Isn't 6 month *ample* time? Likely not, not everyone has the same schedule as upstream systemd, in a lot of cases they don't know it's broken until things land and teams have other priorities. How much time do you think is appropriate for fixing a file copy routine in anaconda? 12 months? 18 months? 2 years? I'm not just referring to *just* anaconda. This is *one* thing, there's other things that might be broken by this. How long has /etc/resolv.conf been a file in that location? How many things across the distro expect it to be like it is? It's legacy and while I'm not against changing it there may be impact that isn't take into account. Bullying people/process/team just because you've waited 6 months already isn't an appropriate response just because you're impatient and want to move on. We're a community that doesn't revolved around systemd... sorry! Also, NM fixed a similar issue with /etc/resolve.conf in their code a long time ago, to my knowledge. Am I so misguided to assume that Anaconda can fix a fricking file copy too, in all those months? To my knowledge there also looks to be issues with dhcp due to this change as of yesterday so maybe you don't have all the knowledge. What else might be affected in the distro according to your knowledge? Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
RE: Orphaning and seeking comaintainers of some packages
Alot taked ... Mosaab Date: Tue, 17 Feb 2015 17:19:38 +0800 Subject: Orphaning and seeking comaintainers of some packages From: cicku...@gmail.com To: devel@lists.fedoraproject.org Hi, There are some packages I don't use anymore, feel free to take them: libntlm python-durus barry spambayes rblcheck tokyocabinet jaxodraw flterm libquvi libquvi-scripts quvi python-django-socialregistration dayplanner gengetopt code2html elementary-icon-theme drehatlas-widelands-fonts pycryptopp drehatlas-xaporho-fonts qdevelop kawa perl-BDB txt2rss scanssh mimetex perl-Date-HolidayParser perl-Email-Find python-pymtp(epel7) These below are packages I seldom use, feel free to comaintain them: NetPIPE PyMca roxterm autoconf-archive freetalk unhide firehol npth exaile flickcurl jwm elektra dmenu profile-sync-daemon python-eyed3 oyranos Thanks. -- Yours sincerely, Christopher Meng http://cicku.me -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: systemd-219 issues with 22 and Rawhide composes
Hi On Fri, Feb 20, 2015 at 11:11 AM, Lennart Poettering wrote: How many months would you like me to notify people in advance of a simple change like this? Isn't 6 month *ample* time? The problem isn't necessarily the speed of change but the amount of caution and attention paid to inform folks affected by such changes. It is a fairly simple change in this case but it affects more than just one component and not everyone is aware of the details in the first place. A simple announcement here or fedora devel announce list would go a long way. Rahul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: systemd-219 issues with 22 and Rawhide composes
Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. Are you going to start notifying deve@ of upcoming changes that may impact other areas of the distro too rather than just land them without notification or discussion? Oh god, stop this, will you? No, I mean the above in general for general changes you make that affect the distro as a whole. You generally land them without notification. I generally do that? Can you be more precise? The folks in question knew I would drop the patch. In the original bug I even said I would remove the work-around from systemd.rpm after TC1 of the last cycle. I was nice, left it in for the whole cycle, only dropped it now. Yes, and it looks like it affects dhcpd too... just because you notified one dev team on a single bug it's not the same as a wider announcement to the wider community. There's all sorts of things that this can affect, and while yes it may be a bug in their software, it should be as widely notified as possible. People have priorities that may not be the same as yours. Hey! Come on. Everything that systemd does is create a symlink for /etc/resolv.conf if nothing else has created on for that. If something else created and owned that file, it leaves the thing alone. That's all. It's very defensively written. Anaconda's file copy routine tripped up on it though, since it follows symlinks on the destination (which is a really bad idea, and needs to be fixed). There is no news in all of this, I just removed the work-around now, as indicated back then. Again, I'm not just referring to this single incident, it would be nice if you notified people widely of changes. It's a community, people don't all follow closely the upstream development of all upstream components. Ok, then please list all those numerous incidents please. How many months would you like me to notify people in advance of a simple change like this? Isn't 6 month *ample* time? Likely not, not everyone has the same schedule as upstream systemd, in a lot of cases they don't know it's broken until things land and teams have other priorities. OK, got it, will let everybody know now of changes 5 years in advance. Would that suit your needs? Not what I'm saying at all. There's no need to throw toys to the extreme just because someone is asking for a certain level of reason and engagement. Anyway, I have the suspicion you just want to make a fuss, and this is where it ends for me hence. Nope, I don't, I just want engagement, generally and overall I'm actively positive for systemd and a big advocate for it. You just need to engage in the community and if something isn't done in six months because another team has other priorities and other deadlines and people push back because it's actually breaking other areas of the distribution there's no need to throw toys from the pram and storm off. It's a large distro of moving parts and we need flexibility as a result, things get pushed due to delays. It's not the end of the world! Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
File constant-defer-6.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-constant-defer: 6af9912fa420340e9e171ac81f450492 constant-defer-6.tar.gz -- 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-constant-defer/f22] Version 6 bump
Summary of changes: 4a9d20c... Version 6 bump (*) (*) 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 1194637] perl-constant-defer-6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194637 --- Comment #3 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- ppisar's perl-constant-defer-6-1.fc23 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=613441 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=TD7GSPz3eda=cc_unsubscribe -- 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
setup needed for building from src rpms ?
I'm not sure if this is the right list for the question, but... I now have the time and opportunity to migrate my main dev machine from Fedora 8 to something current, namely F21. But in the intervening years, there have been lots of changes to KDE, and most of the visual aspects don't suit my way of thinking, especially about usability. Personally I found the older everything to be easer and faster to use. ie. less mouse movements and fewer clicks, etc. But I won't turn this into a rant. Rather I want to patch some of my major pain points to re-introduce some of the options and flexibility that seems to have been removed since then. I thought I'd start with enhancing some of the items in kdetoys, so I fetched the source RPM and tried installing it with yum and dnf. Yum complains about 'Not a compatible architecture: src' DNF complains about 'Will not install a source rpm package RPM tries to work but warns about: missing user and group mockbuild. Can someone point me to a guide for installing/configing the prerequisites for building from source? (It doesn't seem as easy as it used to be.) Thanks Fulko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1194637] perl-constant-defer-6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194637 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-constant-defer-6-1.fc2 ||3 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=RloK8h6HFya=cc_unsubscribe -- 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
Re: setup needed for building from src rpms ?
Am 20.02.2015 um 17:59 schrieb Fulko Hew: I'm not sure if this is the right list for the question, but... not really, at least the subject is on-topic I now have the time and opportunity to migrate my main dev machine from Fedora 8 to something current, namely F21. But in the intervening years, there have been lots of changes to KDE, and most of the visual aspects don't suit my way of thinking, especially about usability. Personally I found the older everything to be easer and faster to use. ie. less mouse movements and fewer clicks, etc. But I won't turn this into a rant. Rather I want to patch some of my major pain points to re-introduce some of the options and flexibility that seems to have been removed since then. I thought I'd start with enhancing some of the items in kdetoys, so I fetched the source RPM and tried installing it with yum and dnf. Yum complains about 'Not a compatible architecture: src' DNF complains about 'Will not install a source rpm package RPM tries to work but warns about: missing user and group mockbuild. a src.rpm is a SOURCE package to install it in a *build environment* or rpmbuild ---rebuild package.src.rpm and rpm -ivh just unpacks it in the build environment (SPECS, SOURCES..) to use rpmbuild https://fedoraproject.org/wiki/How_to_create_an_RPM_package signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1194637] perl-constant-defer-6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194637 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- perl-constant-defer-6-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/perl-constant-defer-6-1.fc21 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=DhFMiaKghha=cc_unsubscribe -- 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
Re: systemd-219 issues with 22 and Rawhide composes
On Fri, 20.02.15 11:07, Dennis Gilmore (den...@ausil.us) wrote: On Fri, 20 Feb 2015 11:04:13 -0600 Dennis Gilmore den...@ausil.us wrote: On Fri, 20 Feb 2015 17:36:17 +0100 Lennart Poettering mzerq...@0pointer.de wrote: On Fri, 20.02.15 16:24, Peter Robinson (pbrobin...@gmail.com) wrote: Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. Are you going to start notifying deve@ of upcoming changes that may impact other areas of the distro too rather than just land them without notification or discussion? Oh god, stop this, will you? No, I mean the above in general for general changes you make that affect the distro as a whole. You generally land them without notification. I generally do that? Can you be more precise? A recent example, systemd decided that os-release needed to be moved to /usr/lib/ I did not see any notification on devel@ nor was i contacted directly. the first I heard of it was a third party person filing a bug against fedora-release I should add that changing it broke the compose process and was quickly fixed. wider communication means that other effected components have some visibility into things that may effect them. You cannot really blame me for breakages for things I neither asked for nor was involved with at all in Fedora. Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: systemd-219 issues with 22 and Rawhide composes
On 02/20/2015 05:11 PM, Lennart Poettering wrote: Also, NM fixed a similar issue with /etc/resolve.conf in their code a long time ago, to my knowledge. Am I so misguided to assume that Anaconda can fix a fricking file copy too, in all those months? Maybe it is time to step back and consider if replacing /etc/resolv.conf with a symbolic link is something that can be reasonably implemented from a backwards compatibility perspective? Usually, if we face this much trouble within Fedora itself, it's a good indicator of the pain that we'll have to deal with downstream. -- Florian Weimer / Red Hat Product Security -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[perl-constant-defer/f21] Version 6 bump
commit 63339afe9ed50b0e4b786523888774b88c4340bf
Author: Petr Písař ppi...@redhat.com
Date: Fri Feb 20 17:50:33 2015 +0100
Version 6 bump
.gitignore | 1 +
perl-constant-defer.spec | 28 +---
sources | 2 +-
3 files changed, 19 insertions(+), 12 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 24fb515..9a2618c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
/constant-defer-5.tar.gz
+/constant-defer-6.tar.gz
diff --git a/perl-constant-defer.spec b/perl-constant-defer.spec
index 838e92f..dd7f57c 100644
--- a/perl-constant-defer.spec
+++ b/perl-constant-defer.spec
@@ -1,27 +1,30 @@
Name: perl-constant-defer
-Version:5
-Release:7%{?dist}
+Version:6
+Release:1%{?dist}
Summary:Constant subs with deferred value calculation
License:GPLv3+
Group: Development/Libraries
URL:http://search.cpan.org/dist/constant-defer/
Source0:
http://www.cpan.org/authors/id/K/KR/KRYDE/constant-defer-%{version}.tar.gz
BuildArch: noarch
+BuildRequires: perl
# The inc/my_pod2html is not called
BuildRequires: perl(ExtUtils::MakeMaker)
-BuildRequires: perl(lib)
+BuildRequires: perl(strict)
# Run-Time:
BuildRequires: perl(Carp)
+BuildRequires: perl(vars)
# Tests:
-BuildRequires: perl(Devel::FindRef)
+# Devel::FindRef not used
BuildRequires: perl(Exporter)
+BuildRequires: perl(lib)
BuildRequires: perl(Scalar::Util)
BuildRequires: perl(Test)
-BuildRequires: perl(Test::More)
# Optionals tests:
BuildRequires: perl(Data::Dumper)
-BuildRequires: perl(Devel::StackTrace)
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+# Devel::StackTrace not used
+# Test::More not used
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
Requires: perl(Carp)
%description
@@ -35,24 +38,27 @@ allowing it to be garbage collected.
chmod -x examples/*
%build
-%{__perl} Makefile.PL INSTALLDIRS=vendor
+perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
-make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
+make pure_install DESTDIR=$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 \;
%{_fixperms} $RPM_BUILD_ROOT/*
%check
make test
%files
-%doc Changes COPYING examples README
+%license COPYING
+%doc Changes examples README
%{perl_vendorlib}/*
%{_mandir}/man3/*
%changelog
+* Fri Feb 20 2015 Petr Pisar ppi...@redhat.com - 6-1
+- Version 6 bump
+
* Sat Jun 07 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 5-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
diff --git a/sources b/sources
index 89e633c..f51ec56 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-519232b64896395b84b41f5300d1cab3 constant-defer-5.tar.gz
+6af9912fa420340e9e171ac81f450492 constant-defer-6.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
[Bug 1194637] perl-constant-defer-6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194637 --- Comment #2 from Petr Pisar ppi...@redhat.com --- This release improves documentations and tests. It's suitable for all Fedoras. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=18VxZLyt2ja=cc_unsubscribe -- 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-constant-defer/f20] Version 6 bump
commit 1402021d7069a8cec47bb525fa52df02b6ed0411
Author: Petr Písař ppi...@redhat.com
Date: Fri Feb 20 17:50:33 2015 +0100
Version 6 bump
.gitignore | 1 +
perl-constant-defer.spec | 28 +---
sources | 2 +-
3 files changed, 19 insertions(+), 12 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 24fb515..9a2618c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
/constant-defer-5.tar.gz
+/constant-defer-6.tar.gz
diff --git a/perl-constant-defer.spec b/perl-constant-defer.spec
index 9d6f96d..a6be7e5 100644
--- a/perl-constant-defer.spec
+++ b/perl-constant-defer.spec
@@ -1,27 +1,30 @@
Name: perl-constant-defer
-Version:5
-Release:6%{?dist}
+Version:6
+Release:1%{?dist}
Summary:Constant subs with deferred value calculation
License:GPLv3+
Group: Development/Libraries
URL:http://search.cpan.org/dist/constant-defer/
Source0:
http://www.cpan.org/authors/id/K/KR/KRYDE/constant-defer-%{version}.tar.gz
BuildArch: noarch
+BuildRequires: perl
# The inc/my_pod2html is not called
BuildRequires: perl(ExtUtils::MakeMaker)
-BuildRequires: perl(lib)
+BuildRequires: perl(strict)
# Run-Time:
BuildRequires: perl(Carp)
+BuildRequires: perl(vars)
# Tests:
-BuildRequires: perl(Devel::FindRef)
+# Devel::FindRef not used
BuildRequires: perl(Exporter)
+BuildRequires: perl(lib)
BuildRequires: perl(Scalar::Util)
BuildRequires: perl(Test)
-BuildRequires: perl(Test::More)
# Optionals tests:
BuildRequires: perl(Data::Dumper)
-BuildRequires: perl(Devel::StackTrace)
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+# Devel::StackTrace not used
+# Test::More not used
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
Requires: perl(Carp)
%description
@@ -35,24 +38,27 @@ allowing it to be garbage collected.
chmod -x examples/*
%build
-%{__perl} Makefile.PL INSTALLDIRS=vendor
+perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
-make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
+make pure_install DESTDIR=$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 \;
%{_fixperms} $RPM_BUILD_ROOT/*
%check
make test
%files
-%doc Changes COPYING examples README
+%license COPYING
+%doc Changes examples README
%{perl_vendorlib}/*
%{_mandir}/man3/*
%changelog
+* Fri Feb 20 2015 Petr Pisar ppi...@redhat.com - 6-1
+- Version 6 bump
+
* Sun Aug 04 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 5-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
diff --git a/sources b/sources
index 89e633c..f51ec56 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-519232b64896395b84b41f5300d1cab3 constant-defer-5.tar.gz
+6af9912fa420340e9e171ac81f450492 constant-defer-6.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
Re: systemd-219 issues with 22 and Rawhide composes
On Fri, Feb 20, 2015 at 04:52:20PM +, Peter Robinson wrote: Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. Are you going to start notifying deve@ of upcoming changes that may impact other areas of the distro too rather than just land them without notification or discussion? Oh god, stop this, will you? No, I mean the above in general for general changes you make that affect the distro as a whole. You generally land them without notification. I generally do that? Can you be more precise? The folks in question knew I would drop the patch. In the original bug I even said I would remove the work-around from systemd.rpm after TC1 of the last cycle. I was nice, left it in for the whole cycle, only dropped it now. Yes, and it looks like it affects dhcpd too... just because you notified one dev team on a single bug it's not the same as a wider announcement to the wider community. There's all sorts of things that this can affect, and while yes it may be a bug in their software, it should be as widely notified as possible. People have priorities that may not be the same as yours. Hey! Come on. Everything that systemd does is create a symlink for /etc/resolv.conf if nothing else has created on for that. If something else created and owned that file, it leaves the thing alone. That's all. It's very defensively written. Anaconda's file copy routine tripped up on it though, since it follows symlinks on the destination (which is a really bad idea, and needs to be fixed). There is no news in all of this, I just removed the work-around now, as indicated back then. Again, I'm not just referring to this single incident, it would be nice if you notified people widely of changes. It's a community, people don't all follow closely the upstream development of all upstream components. Ok, then please list all those numerous incidents please. How many months would you like me to notify people in advance of a simple change like this? Isn't 6 month *ample* time? Likely not, not everyone has the same schedule as upstream systemd, in a lot of cases they don't know it's broken until things land and teams have other priorities. OK, got it, will let everybody know now of changes 5 years in advance. Would that suit your needs? Not what I'm saying at all. There's no need to throw toys to the extreme just because someone is asking for a certain level of reason and engagement. Anyway, I have the suspicion you just want to make a fuss, and this is where it ends for me hence. Nope, I don't, I just want engagement, generally and overall I'm actively positive for systemd and a big advocate for it. You just need to engage in the community and if something isn't done in six months because another team has other priorities and other deadlines and people push back because it's actually breaking other areas of the distribution there's no need to throw toys from the pram and storm off. It's a large distro of moving parts and we need flexibility as a result, things get pushed due to delays. It's not the end of the world! I think we can do better than this level of communication. Yes, it would have been good to avoid a surprise here. There are issues on both sides. Blaming the situation on either impatience or sloth doesn't do any justice to the good efforts everyone makes. On one side, it may not be reasonable to expect that all teams track or follow up on every bug. It's right to expect some explicit notice and, more importantly, collaboration across teams -- talking to each other, not just filing a bug without clear expectations. On the other hand, Fedora is supposed to be innovative and we need to take a positive approach to change. When teams see a change coming up they know will cause them work or breakage, they can proactively reach out to engage. In fact, anyone can facilitate such a conversation. Also, a side note: A book I read on communication in relationships once (I think it was That's Not What I Meant by Deborah Tannen) said that when one universalizes statements, e.g. you usually do X or you always do Y, it's unlikely to yield any positive results in a discussion. I've seen nothing in open source communication that gives evidence to the contrary. :-) The important thing is that we try to deal constructively with this specific situation, and in learning from it, we can mitigate similar situations in the future. -- Paul W. Frields pfrie...@redhat.com Manager, Fedora Engineering - Emerging Platform http://redhat.com -- http://opensource.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1194637] perl-constant-defer-6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194637 --- Comment #8 from Fedora Update System upda...@fedoraproject.org --- perl-constant-defer-6-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-constant-defer-6-1.fc20 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=9lGcRbikSEa=cc_unsubscribe -- 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-constant-defer] Version 6 bump
commit 4a9d20c1b6b45322323e6b2668a6bff79d9c3e25
Author: Petr Písař ppi...@redhat.com
Date: Fri Feb 20 17:50:33 2015 +0100
Version 6 bump
.gitignore | 1 +
perl-constant-defer.spec | 28 +---
sources | 2 +-
3 files changed, 19 insertions(+), 12 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 24fb515..9a2618c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
/constant-defer-5.tar.gz
+/constant-defer-6.tar.gz
diff --git a/perl-constant-defer.spec b/perl-constant-defer.spec
index e533106..f687cf2 100644
--- a/perl-constant-defer.spec
+++ b/perl-constant-defer.spec
@@ -1,27 +1,30 @@
Name: perl-constant-defer
-Version:5
-Release:8%{?dist}
+Version:6
+Release:1%{?dist}
Summary:Constant subs with deferred value calculation
License:GPLv3+
Group: Development/Libraries
URL:http://search.cpan.org/dist/constant-defer/
Source0:
http://www.cpan.org/authors/id/K/KR/KRYDE/constant-defer-%{version}.tar.gz
BuildArch: noarch
+BuildRequires: perl
# The inc/my_pod2html is not called
BuildRequires: perl(ExtUtils::MakeMaker)
-BuildRequires: perl(lib)
+BuildRequires: perl(strict)
# Run-Time:
BuildRequires: perl(Carp)
+BuildRequires: perl(vars)
# Tests:
-BuildRequires: perl(Devel::FindRef)
+# Devel::FindRef not used
BuildRequires: perl(Exporter)
+BuildRequires: perl(lib)
BuildRequires: perl(Scalar::Util)
BuildRequires: perl(Test)
-BuildRequires: perl(Test::More)
# Optionals tests:
BuildRequires: perl(Data::Dumper)
-BuildRequires: perl(Devel::StackTrace)
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+# Devel::StackTrace not used
+# Test::More not used
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
Requires: perl(Carp)
%description
@@ -35,24 +38,27 @@ allowing it to be garbage collected.
chmod -x examples/*
%build
-%{__perl} Makefile.PL INSTALLDIRS=vendor
+perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
-make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
+make pure_install DESTDIR=$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 \;
%{_fixperms} $RPM_BUILD_ROOT/*
%check
make test
%files
-%doc Changes COPYING examples README
+%license COPYING
+%doc Changes examples README
%{perl_vendorlib}/*
%{_mandir}/man3/*
%changelog
+* Fri Feb 20 2015 Petr Pisar ppi...@redhat.com - 6-1
+- Version 6 bump
+
* Wed Aug 27 2014 Jitka Plesnikova jples...@redhat.com - 5-8
- Perl 5.20 rebuild
diff --git a/sources b/sources
index 89e633c..f51ec56 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-519232b64896395b84b41f5300d1cab3 constant-defer-5.tar.gz
+6af9912fa420340e9e171ac81f450492 constant-defer-6.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
Re: systemd-219 issues with 22 and Rawhide composes
On Fri, 2015-02-20 at 17:43 +0100, Florian Weimer wrote: On 02/20/2015 05:11 PM, Lennart Poettering wrote: Also, NM fixed a similar issue with /etc/resolve.conf in their code a long time ago, to my knowledge. Am I so misguided to assume that Anaconda can fix a fricking file copy too, in all those months? Maybe it is time to step back and consider if replacing /etc/resolv.conf with a symbolic link is something that can be reasonably implemented from a backwards compatibility perspective? Usually, if we face this much trouble within Fedora itself, it's a good indicator of the pain that we'll have to deal with downstream. I would love to know the outcome of this discussion, since we just made a change to NetworkManager git master (will be version 1.2, target Fedora 23) to make /etc/resolv.conf a symlink when it's under NM's control. If there are problems here, we want to know too. * NM won't replace a symlinked /etc/resolv.conf that doesn't point to NM's copy in /var * You can disable this behavior with dns=none in /etc/NetworkManager/NetworkManager.conf and manage resolv.conf on your own too Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: systemd-219 issues with 22 and Rawhide composes
On Fri, 20 Feb 2015 17:36:17 +0100 Lennart Poettering mzerq...@0pointer.de wrote: On Fri, 20.02.15 16:24, Peter Robinson (pbrobin...@gmail.com) wrote: Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. Are you going to start notifying deve@ of upcoming changes that may impact other areas of the distro too rather than just land them without notification or discussion? Oh god, stop this, will you? No, I mean the above in general for general changes you make that affect the distro as a whole. You generally land them without notification. I generally do that? Can you be more precise? A recent example, systemd decided that os-release needed to be moved to /usr/lib/ I did not see any notification on devel@ nor was i contacted directly. the first I heard of it was a third party person filing a bug against fedora-release Dennis -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1194637] perl-constant-defer-6 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1194637 --- Comment #6 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- ppisar's perl-constant-defer-6-1.fc21 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=613444 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=lwR1c3o2qQa=cc_unsubscribe -- 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
Re: systemd-219 issues with 22 and Rawhide composes
On Fri, 20 Feb 2015 11:04:13 -0600 Dennis Gilmore den...@ausil.us wrote: On Fri, 20 Feb 2015 17:36:17 +0100 Lennart Poettering mzerq...@0pointer.de wrote: On Fri, 20.02.15 16:24, Peter Robinson (pbrobin...@gmail.com) wrote: Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. Are you going to start notifying deve@ of upcoming changes that may impact other areas of the distro too rather than just land them without notification or discussion? Oh god, stop this, will you? No, I mean the above in general for general changes you make that affect the distro as a whole. You generally land them without notification. I generally do that? Can you be more precise? A recent example, systemd decided that os-release needed to be moved to /usr/lib/ I did not see any notification on devel@ nor was i contacted directly. the first I heard of it was a third party person filing a bug against fedora-release I should add that changing it broke the compose process and was quickly fixed. wider communication means that other effected components have some visibility into things that may effect them. Dennis -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: systemd-219 issues with 22 and Rawhide composes
On Fri, 20.02.15 11:04, Dennis Gilmore (den...@ausil.us) wrote: On Fri, 20 Feb 2015 17:36:17 +0100 Lennart Poettering mzerq...@0pointer.de wrote: On Fri, 20.02.15 16:24, Peter Robinson (pbrobin...@gmail.com) wrote: Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. Are you going to start notifying deve@ of upcoming changes that may impact other areas of the distro too rather than just land them without notification or discussion? Oh god, stop this, will you? No, I mean the above in general for general changes you make that affect the distro as a whole. You generally land them without notification. I generally do that? Can you be more precise? A recent example, systemd decided that os-release needed to be moved to /usr/lib/ I did not see any notification on devel@ nor was i contacted directly. the first I heard of it was a third party person filing a bug against fedora-release While moving it is great, it's not really that important to move it. I mean, moving it is useful in the context of stateless systems that can boot up with empty /etc. However, Fedora is so far away from that, that we have tons of other things to fix first, before the os-release move would start to matter. We haven't posted a feature to make Fedora stateless in this sense, and hence also didn't ask for /etc/os-release to be moved. There are some upstream things to work on before we can propose such a Fedora change. So, thank you very much for moving it! But this is neither a change that would really need coordination, nor something we pushed for from our side. Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: So everything in Rawhide must be compiled with -fPIC?
I've never argumented against the goal that web browser or all network aware services should be PIEs, after all, why would we (Ulrich Drepper and myself) add the PIE support into the toolchain otherwise? I'm just not convinced most of the unpriviledged programs should be PIEs. Thanks to e.g. e-mail about any program can be made to run untrusted data, e.g. PDF readers, office suites, image viewers, if you open an attachment of the respective type. Therefore it makes a sane default IMHO. It is also something to attract users that care about security very much to Fedora. So your saying here that this is miraculously going to stop people from running random binaries that are being emailed to them? Or is just going stop people from running random non PIC/PIE binaries? I don't buy that this is a miracle fix to that problem. How then does it affect other third party binaries not compiled with PIC/PIE that people might wish to run? More over in the Change request [1] I don't see any evidence with examples, links to research papers etc on how this makes things more secure all I see is basically because SECURITY man!!! . The feature says our users less likely become victims of attacks but which sort of attacks, how does it improve security. I understand why we'd want it on remotely accessible daemons and long running back ground processes, even things like mail clients that connect to the internet. There is absolutely no technical detail in the change, other than the technical change to implement it, there's no mention that it will have an impact on performance, with numbers to back it up, across the three primary architectures. Given that the person who actually wrote the code to implement the actual functionality has grave concerns about it's usefulness and impact to end users and packagers. I'm also concerned that he will be the person that will need to fix problems are likely going to be seen by packagers and not you as the person proposing the change? Do you have the time and ability to deal with these problems? Having dealt with these issues across a number of architectures and having had to ask Jakob nicely for his time and assistance when there's been issues from his response I'm not sure you've got his buy in to deal with this. Also I've seen no performance analysis across all three architectures to see the impact. I'll happily send you an XO-1 to test on (our lowest supported device on i686 and also one of our most widely deployed Fedora device) and ARM hardware if you've not got access to test. Fedora users tend to keep hardware around for longer time than a lot of enterprises, it's also a distro used a lot in the developing world on low end cheap hardware because the rest of the world isn't necessarily so privileged as to be able afford the latest and greatest and I think we need to consider that along side possible security improvements! Peter [1] https://fedoraproject.org/wiki/Changes/Harden_all_packages_with_position-independent_code -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: systemd-219 issues with 22 and Rawhide composes
On Fri, 20.02.15 16:24, Peter Robinson (pbrobin...@gmail.com) wrote: Sorry for the inconvenience and feel free to add bugs to the tracker, which are caused by systemd changes and have to be fixed in other components. Are you going to start notifying deve@ of upcoming changes that may impact other areas of the distro too rather than just land them without notification or discussion? Oh god, stop this, will you? No, I mean the above in general for general changes you make that affect the distro as a whole. You generally land them without notification. I generally do that? Can you be more precise? The folks in question knew I would drop the patch. In the original bug I even said I would remove the work-around from systemd.rpm after TC1 of the last cycle. I was nice, left it in for the whole cycle, only dropped it now. Yes, and it looks like it affects dhcpd too... just because you notified one dev team on a single bug it's not the same as a wider announcement to the wider community. There's all sorts of things that this can affect, and while yes it may be a bug in their software, it should be as widely notified as possible. People have priorities that may not be the same as yours. Hey! Come on. Everything that systemd does is create a symlink for /etc/resolv.conf if nothing else has created on for that. If something else created and owned that file, it leaves the thing alone. That's all. It's very defensively written. Anaconda's file copy routine tripped up on it though, since it follows symlinks on the destination (which is a really bad idea, and needs to be fixed). There is no news in all of this, I just removed the work-around now, as indicated back then. Again, I'm not just referring to this single incident, it would be nice if you notified people widely of changes. It's a community, people don't all follow closely the upstream development of all upstream components. Ok, then please list all those numerous incidents please. How many months would you like me to notify people in advance of a simple change like this? Isn't 6 month *ample* time? Likely not, not everyone has the same schedule as upstream systemd, in a lot of cases they don't know it's broken until things land and teams have other priorities. OK, got it, will let everybody know now of changes 5 years in advance. Would that suit your needs? Anyway, I have the suspicion you just want to make a fuss, and this is where it ends for me hence. Good night, Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Proposal to (formally/easily) allowing multiple versions of the same library installable
On 02/16/2015 04:17 PM, Ralf Corsepius wrote: I don't buy this argument wrt. Fedora. Fedora is a rapid moving, forward looking distro, in which such regressions should be fixed and not be worked around by compat-libs. That rather assumes that the only use for Fedora libraries is running programs that are part of Fedora rather than programs that a user installs from elsewhere. While this may be true, it's not necessarily a good thing. Andrew. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
