pghmcfc pushed to perl-Test-Version (perl-Test-Version-2.00-1.fc22). Update to 2.00 (..more)
From 660290745bc5b997c3281f6971deb49784084437 Mon Sep 17 00:00:00 2001
From: Paul Howarth p...@city-fan.org
Date: Thu, 7 May 2015 09:58:28 +0100
Subject: Update to 2.00
- New upstream release 2.00
- Added filename_match setting
diff --git a/perl-Test-Version.spec b/perl-Test-Version.spec
index 22c6c65..3815f6a 100644
--- a/perl-Test-Version.spec
+++ b/perl-Test-Version.spec
@@ -1,17 +1,13 @@
# noarch, but to avoid debug* files interfering with manifest test:
%global debug_package %{nil}
-# Had a six-digit version in a previous life
-%global cpan_version 1.05
-%global rpm_version 1.05
-
Name: perl-Test-Version
-Version: %{rpm_version}
+Version: 2.00
Release: 1%{?dist}
Summary: Check to see that versions in modules are sane
License: Artistic 2.0
URL: http://search.cpan.org/dist/Test-Version/
-Source0:
http://search.cpan.org/CPAN/authors/id/P/PL/PLICEASE/Test-Version-%{cpan_version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/P/PL/PLICEASE/Test-Version-%{version}.tar.gz
BuildArch: noarch
# ===
# Module build requirements
@@ -28,7 +24,7 @@ BuildRequires:perl(Module::Metadata)
BuildRequires: perl(parent)
BuildRequires: perl(strict)
BuildRequires: perl(Test::Builder)
-BuildRequires: perl(Test::More) = 0.88
+BuildRequires: perl(Test::More) = 0.94
BuildRequires: perl(version) = 0.86
BuildRequires: perl(warnings)
# ===
@@ -71,7 +67,7 @@ This module's goal is to be a one stop shop for checking to
see that your
versions across your dist are sane.
%prep
-%setup -q -n Test-Version-%{cpan_version}
+%setup -q -n Test-Version-%{version}
%build
perl Makefile.PL INSTALLDIRS=vendor
@@ -95,6 +91,10 @@ make test TEST_FILES=$(echo $(find xt/ -name '*.t'))
%{_mandir}/man3/Test::Version.3*
%changelog
+* Thu May 7 2015 Paul Howarth p...@city-fan.org - 2.00-1
+- Update to 2.00
+ - Added filename_match setting
+
* Wed May 6 2015 Paul Howarth p...@city-fan.org - 1.05-1
- Update to 1.05
- New maintainer (PLICEASE) updated meta
diff --git a/sources b/sources
index 0c835f0..f805d07 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-5dbfd5ace4ef158e45f6754a2772fa8a Test-Version-1.05.tar.gz
+c29e8e41482b358722dcf8fd2abd7549 Test-Version-2.00.tar.gz
--
cgit v0.10.2
http://pkgs.fedoraproject.org/cgit/perl-Test-Version.git/commit/?h=perl-Test-Version-2.00-1.fc22id=660290745bc5b997c3281f6971deb49784084437
--
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
pghmcfc pushed to perl-Test-Version (perl-Test-Version-2.00-1.fc23). Update to 2.00 (..more)
This commit already existed in another branch. http://pkgs.fedoraproject.org/cgit/perl-Test-Version.git/commit/?h=perl-Test-Version-2.00-1.fc23id=660290745bc5b997c3281f6971deb49784084437 -- 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
pghmcfc uploaded Test-Version-2.00.tar.gz for perl-Test-Version
c29e8e41482b358722dcf8fd2abd7549 Test-Version-2.00.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Test-Version/Test-Version-2.00.tar.gz/c29e8e41482b358722dcf8fd2abd7549/Test-Version-2.00.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
pghmcfc pushed to perl-Test-Version (master). Update to 2.00 (..more)
From 660290745bc5b997c3281f6971deb49784084437 Mon Sep 17 00:00:00 2001
From: Paul Howarth p...@city-fan.org
Date: Thu, 7 May 2015 09:58:28 +0100
Subject: Update to 2.00
- New upstream release 2.00
- Added filename_match setting
diff --git a/perl-Test-Version.spec b/perl-Test-Version.spec
index 22c6c65..3815f6a 100644
--- a/perl-Test-Version.spec
+++ b/perl-Test-Version.spec
@@ -1,17 +1,13 @@
# noarch, but to avoid debug* files interfering with manifest test:
%global debug_package %{nil}
-# Had a six-digit version in a previous life
-%global cpan_version 1.05
-%global rpm_version 1.05
-
Name: perl-Test-Version
-Version: %{rpm_version}
+Version: 2.00
Release: 1%{?dist}
Summary: Check to see that versions in modules are sane
License: Artistic 2.0
URL: http://search.cpan.org/dist/Test-Version/
-Source0:
http://search.cpan.org/CPAN/authors/id/P/PL/PLICEASE/Test-Version-%{cpan_version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/P/PL/PLICEASE/Test-Version-%{version}.tar.gz
BuildArch: noarch
# ===
# Module build requirements
@@ -28,7 +24,7 @@ BuildRequires:perl(Module::Metadata)
BuildRequires: perl(parent)
BuildRequires: perl(strict)
BuildRequires: perl(Test::Builder)
-BuildRequires: perl(Test::More) = 0.88
+BuildRequires: perl(Test::More) = 0.94
BuildRequires: perl(version) = 0.86
BuildRequires: perl(warnings)
# ===
@@ -71,7 +67,7 @@ This module's goal is to be a one stop shop for checking to
see that your
versions across your dist are sane.
%prep
-%setup -q -n Test-Version-%{cpan_version}
+%setup -q -n Test-Version-%{version}
%build
perl Makefile.PL INSTALLDIRS=vendor
@@ -95,6 +91,10 @@ make test TEST_FILES=$(echo $(find xt/ -name '*.t'))
%{_mandir}/man3/Test::Version.3*
%changelog
+* Thu May 7 2015 Paul Howarth p...@city-fan.org - 2.00-1
+- Update to 2.00
+ - Added filename_match setting
+
* Wed May 6 2015 Paul Howarth p...@city-fan.org - 1.05-1
- Update to 1.05
- New maintainer (PLICEASE) updated meta
diff --git a/sources b/sources
index 0c835f0..f805d07 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-5dbfd5ace4ef158e45f6754a2772fa8a Test-Version-1.05.tar.gz
+c29e8e41482b358722dcf8fd2abd7549 Test-Version-2.00.tar.gz
--
cgit v0.10.2
http://pkgs.fedoraproject.org/cgit/perl-Test-Version.git/commit/?h=masterid=660290745bc5b997c3281f6971deb49784084437
--
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
pghmcfc pushed to perl-Test-Version (f22). Update to 2.00 (..more)
From 660290745bc5b997c3281f6971deb49784084437 Mon Sep 17 00:00:00 2001
From: Paul Howarth p...@city-fan.org
Date: Thu, 7 May 2015 09:58:28 +0100
Subject: Update to 2.00
- New upstream release 2.00
- Added filename_match setting
diff --git a/perl-Test-Version.spec b/perl-Test-Version.spec
index 22c6c65..3815f6a 100644
--- a/perl-Test-Version.spec
+++ b/perl-Test-Version.spec
@@ -1,17 +1,13 @@
# noarch, but to avoid debug* files interfering with manifest test:
%global debug_package %{nil}
-# Had a six-digit version in a previous life
-%global cpan_version 1.05
-%global rpm_version 1.05
-
Name: perl-Test-Version
-Version: %{rpm_version}
+Version: 2.00
Release: 1%{?dist}
Summary: Check to see that versions in modules are sane
License: Artistic 2.0
URL: http://search.cpan.org/dist/Test-Version/
-Source0:
http://search.cpan.org/CPAN/authors/id/P/PL/PLICEASE/Test-Version-%{cpan_version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/P/PL/PLICEASE/Test-Version-%{version}.tar.gz
BuildArch: noarch
# ===
# Module build requirements
@@ -28,7 +24,7 @@ BuildRequires:perl(Module::Metadata)
BuildRequires: perl(parent)
BuildRequires: perl(strict)
BuildRequires: perl(Test::Builder)
-BuildRequires: perl(Test::More) = 0.88
+BuildRequires: perl(Test::More) = 0.94
BuildRequires: perl(version) = 0.86
BuildRequires: perl(warnings)
# ===
@@ -71,7 +67,7 @@ This module's goal is to be a one stop shop for checking to
see that your
versions across your dist are sane.
%prep
-%setup -q -n Test-Version-%{cpan_version}
+%setup -q -n Test-Version-%{version}
%build
perl Makefile.PL INSTALLDIRS=vendor
@@ -95,6 +91,10 @@ make test TEST_FILES=$(echo $(find xt/ -name '*.t'))
%{_mandir}/man3/Test::Version.3*
%changelog
+* Thu May 7 2015 Paul Howarth p...@city-fan.org - 2.00-1
+- Update to 2.00
+ - Added filename_match setting
+
* Wed May 6 2015 Paul Howarth p...@city-fan.org - 1.05-1
- Update to 1.05
- New maintainer (PLICEASE) updated meta
diff --git a/sources b/sources
index 0c835f0..f805d07 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-5dbfd5ace4ef158e45f6754a2772fa8a Test-Version-1.05.tar.gz
+c29e8e41482b358722dcf8fd2abd7549 Test-Version-2.00.tar.gz
--
cgit v0.10.2
http://pkgs.fedoraproject.org/cgit/perl-Test-Version.git/commit/?h=f22id=660290745bc5b997c3281f6971deb49784084437
--
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: dnf woes
- Original Message - From: Radek Holy rh...@redhat.com To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Wednesday, May 6, 2015 5:24:52 PM Subject: Re: dnf woes - Original Message - From: Philip Rhoades p...@pricom.com.au To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Wednesday, May 6, 2015 4:31:46 PM Subject: dnf woes People, I have been watching the dnf arguments over the last year or so with a little interest but now I am exposed to an actual problem - I have been making VMs from the last few beta versions of Fedora-Live-Xfce-x86_64-22 and find that Beta-3 still does not let me update packages after installation - I still get the following error: Error: Failed to synchronize cache for repo 'fedora' from 'https://mirrors.fedoraproject.org/metalink?repo=fedora-22arch=x86_64': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried whenever I do anything with dnf (eg dnf [install xx | update] etc) - there doesn't to be too many reports about this so am I missing something? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: p...@pricom.com.au -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct There are some similar reports already but we have never been able to reproduce it. It would be nice if someone could provide us more debugging info, e.g. by running DNF with LIBREPO_DEBUG=1. -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct FYI, https://bugzilla.redhat.com/show_bug.cgi?id=1219283 Please continue the discussion there in case of a valuable input. -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Agenda for Env-and-Stacks WG meeting (2015-05-07)
WG meeting will be at 12:00 UTC (9:00 EST, 14:00 Brno, 8:00 Boston, 21:00 Tokyo, 22:00 Brisbane) in #fedora-meeting-2 on Freenode. = Topics = * Follow-ups, if any progress has been made * Docker images building within Fedora * Containers-Testing-Framework * 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
Unison in Fedora
[Previous discussion here: https://lists.fedoraproject.org/pipermail/devel/2011-September/thread.html#157495 ] Unison is a fairly widely used file synchronization package. Think of it as a more efficient, multi-directional 'rsync'. Unison has the unfortunate property that versions of Unison are not compatible with each other unless they have the exact same major.minor release. eg. Unison 2.40.128 is compatible with Unison 2.40.102, but incompatible with Unison 2.48.3 (the latest upstream). The reason that matters is you might be running Unison across multiple machines, running different Linux distros, which have different versions of Unison. For this reason, Fedora packages three different Unison branches in separate packages: - unison213 (currently Unison 2.13.16) - unison227 (currently Unison 2.27.57) - unison240 (currently Unison 2.40.128) - There was a unison package, but it is retired We don't package the latest upstream (Unison 2.48.3) at all[1]. For comparison, Debian packages: - unison2.27.57 - unison2.32.52 - unison (which contains 2.40.x) - unison-all, a meta-package, which pulls in all of the above AFAICT Debian also does not package the latest upstream version. So you can see that someone who needed to synchronize across Fedora and Debian machines would have two compatible choices: - Fedora unison227 - Debian unison2.27.57 - Fedora unison240 - Debian unison Anyway, I think this situation is crazy. One reason is that in order to add the latest upstream Unison (2.48) I'm going to have to submit a new unison248 package[1]. And then if there's another version, I'll have to submit a new package for that. I think Fedora should have a single unison source package, and it should contain the multiple upstream branch sources and build different binary subpackages. The binary subpackages would have the same names as now (unison227 etc), making this a compatible update for existing Fedora Unison users. This way I only need to submit a single new package review, we can delete the unison2xx source packages, and there'll be a single place for unison in Fedora for ever more. Discuss ... Rich. [1] BTW there is a COPR build of unison248 if you search for it. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: gcc5 C++11 ABI rebuilds and FTBFS packages
On Mon, May 04, 2015 at 01:09:23PM +0200, Kalev Lember wrote: So I went on and spent 30 minutes writing a script to rebuild C++ packages on rawhide that hadn't gotten rebuilt yet, and ran the script over the weekend. The script was not very smart and it basically just brute forced its way through, trying to greedily build as many packages as possible. It did 5 passes over the packages, building a bit more and unbreaking deeper dep chains each time. I believe it's now converged to a set packages that need manual attention. [This requires a degree in OCaml, but anyway ...] Here is the script I use to rebuild the OCaml packages, in order, to any depth of dependencies, automatically: http://git.annexia.org/?p=goals.git;a=blob;f=fedora_ocaml_rebuild.ml It is based on goaljobs, which is a generalized form of 'make': http://git.annexia.org/?p=goaljobs.git;a=summary Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
pghmcfc pushed to perl-Test-Version (f22). Update to 1.05 (..more)
From 92ad27ed31296b3644e2fb6ab7d96f3900edd60c Mon Sep 17 00:00:00 2001
From: Paul Howarth p...@city-fan.org
Date: Wed, 6 May 2015 10:40:36 +0100
Subject: Update to 1.05
- New upstream release 1.05
- New maintainer (PLICEASE) updated meta
- Retained six-digit version number for rpm to maintain upgrade path, until
upstream reaches version 2 anyway
diff --git a/perl-Test-Version.spec b/perl-Test-Version.spec
index c930ed1..22c6c65 100644
--- a/perl-Test-Version.spec
+++ b/perl-Test-Version.spec
@@ -1,14 +1,17 @@
# noarch, but to avoid debug* files interfering with manifest test:
%global debug_package %{nil}
+# Had a six-digit version in a previous life
+%global cpan_version 1.05
+%global rpm_version 1.05
+
Name: perl-Test-Version
-Version: 1.004001
+Version: %{rpm_version}
Release: 1%{?dist}
Summary: Check to see that versions in modules are sane
License: Artistic 2.0
-Group: Development/Libraries
URL: http://search.cpan.org/dist/Test-Version/
-Source0:
http://search.cpan.org/CPAN/authors/id/X/XE/XENO/Test-Version-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/P/PL/PLICEASE/Test-Version-%{cpan_version}.tar.gz
BuildArch: noarch
# ===
# Module build requirements
@@ -48,7 +51,6 @@ BuildRequires:perl(Test::Tester)
BuildRequires: perl(English)
BuildRequires: perl(Pod::Coverage::TrustPod)
BuildRequires: perl(Test::CPAN::Changes) = 0.19
-BuildRequires: perl(Test::CPAN::Meta::JSON)
BuildRequires: perl(Test::DistManifest)
BuildRequires: perl(Test::EOL)
BuildRequires: perl(Test::MinimumVersion)
@@ -69,7 +71,7 @@ This module's goal is to be a one stop shop for checking to
see that your
versions across your dist are sane.
%prep
-%setup -q -n Test-Version-%{version}
+%setup -q -n Test-Version-%{cpan_version}
%build
perl Makefile.PL INSTALLDIRS=vendor
@@ -90,9 +92,15 @@ make test TEST_FILES=$(echo $(find xt/ -name '*.t'))
%license LICENSE
%doc Changes CONTRIBUTING README
%{perl_vendorlib}/Test/
-%{_mandir}/man3/Test::Version.3pm*
+%{_mandir}/man3/Test::Version.3*
%changelog
+* Wed May 6 2015 Paul Howarth p...@city-fan.org - 1.05-1
+- Update to 1.05
+ - New maintainer (PLICEASE) updated meta
+- Retained six-digit version number for rpm to maintain upgrade path, until
+ upstream reaches version 2 anyway
+
* Tue Oct 21 2014 Paul Howarth p...@city-fan.org - 1.004001-1
- Update to 1.004001
- Improved consistent check diagnostics (GH#11)
diff --git a/sources b/sources
index 3d78ba4..0c835f0 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-539cf46f84d54f670bff8710ce072ed2 Test-Version-1.004001.tar.gz
+5dbfd5ace4ef158e45f6754a2772fa8a Test-Version-1.05.tar.gz
--
cgit v0.10.2
http://pkgs.fedoraproject.org/cgit/perl-Test-Version.git/commit/?h=f22id=92ad27ed31296b3644e2fb6ab7d96f3900edd60c
--
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: Unison in Fedora
On Thu, May 07, 2015 at 08:41:25AM -0600, Kevin Fenzi wrote: Well, just as mentioned in the previous thread, if you do things this way it means every user of any unison will have to get a useless update everytime any version of unison in your combined package updates for any reason. Thats pretty disruptive. Looking at the figures: Package Updates in last.. of which mass rebuilds 2½ years - unison213 5 3 unison227 4 4 unison24012 3 unison248[*] 10 3 - Total31 Total excluding mass rebuilds = 18 Since mass rebuilds would only happen once for the combined package, the total number of updates over the past 2½ years for a combined package would have been 21 or 22, well under one update per month. Rich. [*] Estimated by assuming that we built every new upstream stable release when it came out, but didn't have to rebuild between those releases, except for mass rebuilds. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [EPEL-devel] wine 32
Am 07.05.2015 um 21:58 schrieb ToddAndMargo: Any sign of Red Hat changing their ways? Or are they just sick and tired of 32 bit? i686 is dead - there is no RHEL7 for i686 at all the last non x86_64 i faced was 5 years ago and frankly the whole linux stack would be much more tiny without the old code and could be optimized for mordern and relevant CPU's signature.asc Description: OpenPGP digital signature ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: Unison in Fedora
On Thu, 7 May 2015 08:58:45 -0600 Stephen John Smoogen smo...@gmail.com wrote: Well, just as mentioned in the previous thread, if you do things this way it means every user of any unison will have to get a useless update everytime any version of unison in your combined package updates for any reason. Thats pretty disruptive. I think the issue is that none of those versions are getting updates anymore. They are dead code... any fix that is going to be in one is probably going to be in all of them so they would all need it. I mean that anytime you say add a new version to it, or fix some minor packaging issue in just one, _EVERYONE_ with _ANY_ version will then get the update (even though it actually changes nothing on their system). ie, you have: unison package that ships all of Unison 2.13.16, 2.27.57, 2.40.128 Users install the one they need/want to use. you add 2.48.3 and all those users of the other 3 will get an update with 0 changes. I don't think just adding new packages is that big a deal to save everyone from this. kevin pgp8eSDKoj3X1.pgp 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
Re: Unison in Fedora
On Thu, May 07, 2015 at 11:50:02AM -0600, Kevin Fenzi wrote: I think the issue is that none of those versions are getting updates anymore. They are dead code... any fix that is going to be in one is probably going to be in all of them so they would all need it. I mean that anytime you say add a new version to it, or fix some minor packaging issue in just one, _EVERYONE_ with _ANY_ version will then get the update (even though it actually changes nothing on their system). So, how about _two_ packages, unison and unison-compat (or unison-legacy)? The unison would contain the latest code — as a name-versioned subpackage. The unison-compat would contain all of the legacy ones — also as subpackages. The compat package would only need to be rebuilt when those have security updates, or when a version moves from current to legacy status. Hopefully security updates are infrequent (and I bet would tend to cross multiple old versions if they affect any), and the shift from current-legacy could be done only in rawhide (and therefore for end-users only at Fedora release update time). ie, you have: unison package that ships all of Unison 2.13.16, 2.27.57, 2.40.128 Users install the one they need/want to use. you add 2.48.3 and all those users of the other 3 will get an update with 0 changes. I don't think just adding new packages is that big a deal to save everyone from this. kevin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unison in Fedora
On Thu, May 07, 2015 at 07:01:44PM +0100, Richard W.M. Jones wrote: I think the problem is almost everyone would be using unison-legacy, since that would be the only version compatible with the broader ecosystem of Unison servers (by which I mean Debian). So it doesn't really solve the unnecessary updates problem, if that is really a problem. Well, presuambly, the frequently-changing package would be the non-legacy one which is under active development, right? So, unison-legacy wouldn't change often at all. Any non-critical fixes to it, including graduationof non-legacy to legacy, could be done in Rawhide, where mass rebuilds are likely to happen anyway, so all of the almost-everyone using the legacy package would only see a new package on system upgrade. (Or is my logic here flawed?) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unison in Fedora
On Thu, May 07, 2015 at 02:19:27PM -0400, Matthew Miller wrote: On Thu, May 07, 2015 at 07:01:44PM +0100, Richard W.M. Jones wrote: I think the problem is almost everyone would be using unison-legacy, since that would be the only version compatible with the broader ecosystem of Unison servers (by which I mean Debian). So it doesn't really solve the unnecessary updates problem, if that is really a problem. Well, presuambly, the frequently-changing package would be the non-legacy one which is under active development, right? So, unison-legacy wouldn't change often at all. Any non-critical fixes to it, including graduationof non-legacy to legacy, could be done in Rawhide, where mass rebuilds are likely to happen anyway, so all of the almost-everyone using the legacy package would only see a new package on system upgrade. (Or is my logic here flawed?) I don't think your logic is flawed, but there do appear to be more builds for the combined unison-legacy package -- see my figures here, assuming unison-legacy would cover the first three packages. https://lists.fedoraproject.org/pipermail/devel/2015-May/210455.html Anyway, I'd still prefer a single package, because I don't see the frequency of updates as being an actual problem. Another data item is the size of the Unison package: unison213 3875690 bytes unison227 4017698 bytes unison240-gtk 4491617 bytes (These figures are all for F21) So you're pushing out around 4MB per update to each user, assuming you cannot get any savings from delta RPMs. That's one second of download time for most people in the developed world. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- 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: Unison in Fedora
On Thu, May 07, 2015 at 07:49:34PM +0100, Richard W.M. Jones wrote: I don't think your logic is flawed, but there do appear to be more builds for the combined unison-legacy package -- see my figures here, assuming unison-legacy would cover the first three packages. Actually, your figures over-inflate things. Going back to February 2008, when 2.27 and 2.13 split, there are only _two_ changes which only affect one or the other of the packages, one a bugfix and the other a spec file cleanup (as part of a mass cleanup). So, together or separate, the number of updates is virtually the same. On the other hand, the number of unique changes to unison240 is somewhat higher (although I don't think we're in the top percentile of package churn in any case). -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
F22 updates stopped ?
Hi,
https://admin.fedoraproject.org/updates/FEDORA-2015-6974/dpkg-1.16.16-5.fc22
bodhi says (2015-05-05 12:30:03) that have been push to stable , but
not close the bug
and
dnf repoquery --qf %{repoid} %{name}-%{version}-%{release} dpkg
(...)
updates-testing dpkg-1.16.16-5.fc22
Also doesn't found any wxPython-3.0.2.0-5 in update-testing :
https://admin.fedoraproject.org/updates/wxPython-3.0.2.0-5.fc22
when it says that have been pushed .
All mirror, that I check, seems stopped 4 of May ...
http://mirrors.us.kernel.org/fedora/updates/testing/22/x86_64/
etc
Can someone check what happens ?
Thanks,
--
Sérgio M. B.
--
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: Unison in Fedora
On Thu, May 07, 2015 at 01:59:10PM -0400, Matthew Miller wrote: On Thu, May 07, 2015 at 11:50:02AM -0600, Kevin Fenzi wrote: I think the issue is that none of those versions are getting updates anymore. They are dead code... any fix that is going to be in one is probably going to be in all of them so they would all need it. I mean that anytime you say add a new version to it, or fix some minor packaging issue in just one, _EVERYONE_ with _ANY_ version will then get the update (even though it actually changes nothing on their system). So, how about _two_ packages, unison and unison-compat (or unison-legacy)? The unison would contain the latest code — as a name-versioned subpackage. The unison-compat would contain all of the legacy ones — also as subpackages. The compat package would only need to be rebuilt when those have security updates, or when a version moves from current to legacy status. Hopefully security updates are infrequent (and I bet would tend to cross multiple old versions if they affect any), and the shift from current-legacy could be done only in rawhide (and therefore for end-users only at Fedora release update time). I think the problem is almost everyone would be using unison-legacy, since that would be the only version compatible with the broader ecosystem of Unison servers (by which I mean Debian). So it doesn't really solve the unnecessary updates problem, if that is really a problem. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F22 updates stopped ?
On Thursday, May 07, 2015 09:03:05 PM Sérgio Basto wrote:
Hi,
https://admin.fedoraproject.org/updates/FEDORA-2015-6974/dpkg-1.16.16-5.fc22
bodhi says (2015-05-05 12:30:03) that have been push to stable , but
not close the bug
and
dnf repoquery --qf %{repoid} %{name}-%{version}-%{release} dpkg
(...)
updates-testing dpkg-1.16.16-5.fc22
the comment says it is being pushed to stable. not that it has been pushed.
Also doesn't found any wxPython-3.0.2.0-5 in update-testing :
https://admin.fedoraproject.org/updates/wxPython-3.0.2.0-5.fc22
when it says that have been pushed .
Same it says that is its being pushed
All mirror, that I check, seems stopped 4 of May ...
http://mirrors.us.kernel.org/fedora/updates/testing/22/x86_64/
etc
Can someone check what happens ?
We have had issues pushing updates this week due to someone pasting invalid
data into the update info that caused updateinfo.xml validation to go boom. it
is being worked on and fixed.
Dennis
signature.asc
Description: This is a digitally signed message part.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Unison in Fedora
On Thu, May 07, 2015 at 11:50:02AM -0600, Kevin Fenzi wrote: I don't think just adding new packages is that big a deal to save everyone from this. I think the main problem is that I'm not motivated to go through the new package process for unison245, unison247 or unison248, and evidently nor is anyone else. Whereas I would be a lot more motivated if new releases of Unison were more like new releases of other packages. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F22 updates stopped ?
On Thu, 07 May 2015 21:03:05 +0100
Sérgio Basto ser...@serjux.com wrote:
Hi,
https://admin.fedoraproject.org/updates/FEDORA-2015-6974/dpkg-1.16.16-5.fc22
bodhi says (2015-05-05 12:30:03) that have been push to stable , but
not close the bug
and
dnf repoquery --qf %{repoid} %{name}-%{version}-%{release} dpkg
(...)
updates-testing dpkg-1.16.16-5.fc22
Also doesn't found any wxPython-3.0.2.0-5 in update-testing :
https://admin.fedoraproject.org/updates/wxPython-3.0.2.0-5.fc22
when it says that have been pushed .
All mirror, that I check, seems stopped 4 of May ...
http://mirrors.us.kernel.org/fedora/updates/testing/22/x86_64/
etc
Can someone check what happens ?
Yes. You can be sure releng is aware and working on it. ;)
We have had another week of fun issues... first the typical composes
failing due to known issues, then lately we have had issues around an
update with some characters in it that caused the repodata to be
invalid (xmllint caught it and failed the compose) and then some
storage issues (slowness due to removing old composes so we could free
up space).
Anyhow, this is all being worked on. :)
kevin
pgpXjOsqSEP5y.pgp
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 1217452] perl-App-cpanminus-1.7034 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1217452 --- Comment #7 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Created attachment 1023309 -- https://bugzilla.redhat.com/attachment.cgi?id=1023309action=edit [patch] Update to 1.7034 (#1217452) -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1217452] perl-App-cpanminus-1.7034 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1217452 Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org changed: What|Removed |Added Summary|perl-App-cpanminus-1.7033 |perl-App-cpanminus-1.7034 |is available|is available --- Comment #6 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Latest upstream release: 1.7034 Current version/release in rawhide: 1.7031-1.fc23 URL: http://search.cpan.org/dist/App-cpanminus/ 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 Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Working Around Recent Depcheck inferior arch Failures
Recently, there have been some invalid failures in depcheck that take the form of: package foo-1.2-3.fc21.i686 requires foo-libs(x86-32) = 1.2-3.fc21, but none of the providers can be installed foo-libs-1.2-3.fc21.i686 has inferior architecture This issue has been particularly difficult for us to track down and while we were finally able to reproduce it on a developer's system, we don't have a fix for the root cause that we've found. To keep the issue from affecting any more packagers, we pushed changes to production Taskotron to mitigate the impact of these invalid failures. Future occurrences will not show up as Bodhi comments and unless you're following results in our systems closely, packagers shouldn't notice any more of these failures. When these failures happen, the job will be rerun and from what we've seen so far it's unlikely that repeated jobs will hit this same issue. If you do see any more of this type of invalid failure reported to Bodhi, please let us know so we can fix it. Tim The details of what we changed: https://phab.qadevel.cloud.fedoraproject.org/T467 The original issue that we're still working on: https://phab.qadevel.cloud.fedoraproject.org/T366 pgpZzxXYumTet.pgp 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 1217452] perl-App-cpanminus-1.7034 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1217452 --- Comment #8 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Scratch build succeeded http://koji.fedoraproject.org/koji/taskinfo?taskID=9682201 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
F-22 Branched report: 20150507 changes
Compose started at Thu May 7 15:15:02 UTC 2015 Broken deps for armhfp -- [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [aeskulap] aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libofstd.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires liboflog.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libijg8.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libijg16.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libijg12.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmnet.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmjpeg.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmimgle.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmimage.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmdata.so.3.6 [crystal] crystal-2.2.1-2.fc22.armv7hl requires libkdecorations.so.4 [dnssec-check] dnssec-check-1.14.0.1-4.fc20.armv7hl requires libval-threads.so.14 dnssec-check-1.14.0.1-4.fc20.armv7hl requires libsres.so.14 [gcc-python-plugin] gcc-python2-debug-plugin-0.13-2.fc22.armv7hl requires gcc = 0:4.9.2-1.fc22 gcc-python2-plugin-0.13-2.fc22.armv7hl requires gcc = 0:4.9.2-1.fc22 gcc-python3-debug-plugin-0.13-2.fc22.armv7hl requires gcc = 0:4.9.2-1.fc22 gcc-python3-plugin-0.13-2.fc22.armv7hl requires gcc = 0:4.9.2-1.fc22 [kde-style-skulpture] kde-style-skulpture-0.2.4-9.fc22.armv7hl requires libkdecorations.so.4 [leksah] ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(utf8-string-0.3.7-013ef9ad8ac70ebb11df31f487b74f26) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(unix-2.6.0.1-7550b9ae9dbc74e4d6570cc239a29030) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(transformers-0.3.0.0-23508e0b4a1c1bc1cf2c2de3bb13e90c) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(time-1.4.0.1-970760bdd865d8b6cafac382276795a2) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(text-0.11.3.1-17cae9ba49c3f3d533bf78a6e387f543) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(strict-0.3.2-04f0cc1e99eff2196c0a7cd16d748b37) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(regex-tdfa-1.1.8-0b03687c4e38c00ef92e9445170081e2) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(regex-base-0.93.2-6a541a53412d1d7d310fa69bca50c85f) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(pretty-1.1.1.0-2de27f83b2c1c65d629a564e9e01b27d) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(parsec-3.1.3-a8bebef411959de671abb0f1f7da556f) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(old-time-1.1.0.1-29c02e2b3bbdfd9a5756f0c46f4d6071) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(network-2.4.1.2-82f6bcf79fe0252b3ab387e8dcb82e71) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(mtl-2.1.2-2f2cd438035824ec2bed4811930bc232) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(ltk-0.12.1.0-2fbb10498719be9dbdbb3d9f8adedbec) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(leksah-server-0.12.1.2-7dbd70c9f5e4dd8b3b5efcb6597b3bfd) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(hslogger-1.2.1-43834164508859009a3cc8aef7fd1e84) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(gtksourceview2-0.12.5.0-588b179d0562576f9afa46559cebf79f) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(gtk-0.12.5.0-2342a114ec8897cecfdda15ac92aed08) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(glib-0.12.5.0-1b94df160e141377711a221615168695) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(gio-0.12.5.0-b012293268f349d8f05c73d053798c7b) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(ghc-7.6.3-18fc786f8ad3478b9bb568d865b0e48d) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(filepath-1.3.0.1-62570c67b40fb99e7078c0d179220531) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(enumerator-0.4.19-a164f71ed1088e349dd8bc4cdee8e449) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(directory-1.2.0.1-504c99535d64699e20e001d81b577d06) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(deepseq-1.3.0.1-aa1be128186a233c7290faf88620ffe5) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(containers-0.5.0.0-3b8b869ec10d44736414ab5bea776319) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(bytestring-0.10.0.2-ea1d6622fb7aad447c7746744ecded40) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(binary-shared-0.8.3-e7b0a0ea6f1cabbb7494156068d1e65c)
ppisar pushed to perl-Module-Starter-Plugin-CGIApp (f22). Adapt to changes in Module-Starter-1.71
From 08f6e5151b6e6bd01e60956e0e90725ebf1e41a9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com
Date: Thu, 7 May 2015 13:43:25 +0200
Subject: Adapt to changes in Module-Starter-1.71
diff --git
a/Module-Starter-Plugin-CGIApp-0.42-Adapt-to-Module-Starter-1.71.patch
b/Module-Starter-Plugin-CGIApp-0.42-Adapt-to-Module-Starter-1.71.patch
new file mode 100644
index 000..6bd3a1d
--- /dev/null
+++ b/Module-Starter-Plugin-CGIApp-0.42-Adapt-to-Module-Starter-1.71.patch
@@ -0,0 +1,57 @@
+From a1e8f3b6937be2c8c03de3dfb09ca53ca62be88a Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com
+Date: Thu, 7 May 2015 13:37:53 +0200
+Subject: [PATCH] Adapt to Module-Starter-1.71
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Module-Starter 1.70 and 1.71 changed how test files are created. This
+adjusts to the change.
+
+Filtering t/boilerplate.t from MANIFEST is a hack. I don't understand why
+it's not created into xt directory.
+
+https://bugzilla.redhat.com/show_bug.cgi?id=1189463
+https://rt.cpan.org/Public/Bug/Display.html?id=101894
+https://github.com/xsawyerx/module-starter/issues/47#issuecomment-73425236
+Signed-off-by: Petr Písař ppi...@redhat.com
+---
+ lib/Module/Starter/Plugin/CGIApp.pm | 7 ++-
+ 1 file changed, 2 insertions(+), 5 deletions(-)
+
+diff --git a/lib/Module/Starter/Plugin/CGIApp.pm
b/lib/Module/Starter/Plugin/CGIApp.pm
+index cb0f1b7..f3aa37b 100644
+--- a/lib/Module/Starter/Plugin/CGIApp.pm
b/lib/Module/Starter/Plugin/CGIApp.pm
+@@ -125,7 +125,6 @@ sub create_distro {
+ push @files, $self-create_modules( @{ $self-{modules} } );
+
+ push @files, $self-create_t( @{ $self-{modules} } );
+-push @files, $self-create_xt( @{ $self-{modules} } );
+ push @files, $self-create_tmpl();
+ my %build_results = $self-create_build();
+ push @files, @{ $build_results{files} };
+@@ -147,7 +146,7 @@ sub _create_manifest {
+
+ my $file = File::Spec-catfile( $self-{basedir}, 'MANIFEST' );
+ open my $fh, '', $file or croak Can't open file $file: $OS_ERROR\n;
+-foreach my $file ( sort @files ) {
++foreach my $file ( grep !m{^\Qt/boilerplate.t\E$}, sort @files ) {
+ print {$fh} $file\n or croak $OS_ERROR\n;
+ }
+ close $fh or croak Can't close file $file: $OS_ERROR\n;
+@@ -261,9 +260,7 @@ in the distribution.
+ sub create_t {
+ my ( $self, @modules ) = @_;
+
+-my %t_files = $self-t_guts(@modules);
+-
+-my @files = map { $self-_create_t( $_, $t_files{$_} ) } keys %t_files;
++my @files = $self-SUPER::create_t(@modules);
+
+ # This next part is for the static files dir t/www
+ my @dirparts = ( $self-{basedir}, 't', 'www' );
+--
+2.1.0
+
diff --git a/perl-Module-Starter-Plugin-CGIApp.spec
b/perl-Module-Starter-Plugin-CGIApp.spec
index 702a3af..a98ee22 100644
--- a/perl-Module-Starter-Plugin-CGIApp.spec
+++ b/perl-Module-Starter-Plugin-CGIApp.spec
@@ -1,11 +1,13 @@
Name: perl-Module-Starter-Plugin-CGIApp
Version:0.42
-Release:8%{?dist}
+Release:9%{?dist}
Summary:Template based module starter for CGI apps
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Module-Starter-Plugin-CGIApp/
Source0:
http://www.cpan.org/authors/id/J/JA/JALDHAR/Module-Starter-Plugin-CGIApp-%{version}.tar.gz
+# Adapt to changes in Module-Starter-1.71, bug #1189463, CPAN RT#101894
+Patch0:
Module-Starter-Plugin-CGIApp-0.42-Adapt-to-Module-Starter-1.71.patch
BuildArch: noarch
BuildRequires: perl(File::Copy::Recursive)
BuildRequires: perl(File::DirCompare)
@@ -13,7 +15,8 @@ BuildRequires: perl(File::ShareDir)
BuildRequires: perl(HTML::Template)
BuildRequires: perl(Module::Build)
BuildRequires: perl(Module::Signature)
-BuildRequires: perl(Module::Starter)
+# Constrain Module::Starter version due to bug #1189463
+BuildRequires: perl(Module::Starter) = 1.71
BuildRequires: perl(Pod::Coverage) = 0.18
BuildRequires: perl(Test::Builder)
BuildRequires: perl(Test::MockTime)
@@ -24,8 +27,11 @@ BuildRequires: perl(Test::WWW::Mechanize::CGIApp)
BuildRequires: perl(Time::Piece)
BuildRequires: perl(Titanium)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+Requires: perl(Module::Starter) = 1.71
%{?perl_default_filter}
+# Remove under-specified dependencies:
+%global __requires_exclude
%{?__requires_exclude:%__requires_exclude|}^perl\\(Module::Starter\\)$
%description
This is a plugin for Module::Starter that builds you a skeleton
@@ -34,6 +40,7 @@ CPAN. You can customize the output using HTML::Template.
%prep
%setup -q -n Module-Starter-Plugin-CGIApp-%{version}
+%patch0 -p1
%build
@@ -60,6 +67,9 @@ find $RPM_BUILD_ROOT -depth -type d -exec rmdir {}
2/dev/null \;
%{_mandir}/man3/*
%changelog
+* Thu May 07 2015 Petr Pisar ppi...@redhat.com -
[Bug 1219466] perl-Config-Properties-1.79 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1219466 --- Comment #1 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Created attachment 1023090 -- https://bugzilla.redhat.com/attachment.cgi?id=1023090action=edit [patch] Update to 1.79 (#1219466) -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1219469] perl-DBIx-DBSchema-0.45 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1219469 --- Comment #2 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Scratch build failed http://koji.fedoraproject.org/koji/taskinfo?taskID=9677828 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Unison in Fedora
On Thu, May 07, 2015 at 09:17:10AM +0100, Richard W.M. Jones wrote: I think Fedora should have a single unison source package, and it should contain the multiple upstream branch sources and build different binary subpackages. The binary subpackages would have the same names as now (unison227 etc), making this a compatible update for existing Fedora Unison users. This way I only need to submit a single new package review, we can delete the unison2xx source packages, and there'll be a single place for unison in Fedora for ever more. This seems like a sane plan to me, given the circumstances. (It's really too bad that newer versions don't _themselves_ have a compat mode, but oh well.) I suppose this would need a special exception from FPC. -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
ppisar pushed to perl-Module-Starter-Plugin-CGIApp (master). Adapt to changes in Module-Starter-1.71
From 08f6e5151b6e6bd01e60956e0e90725ebf1e41a9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com
Date: Thu, 7 May 2015 13:43:25 +0200
Subject: Adapt to changes in Module-Starter-1.71
diff --git
a/Module-Starter-Plugin-CGIApp-0.42-Adapt-to-Module-Starter-1.71.patch
b/Module-Starter-Plugin-CGIApp-0.42-Adapt-to-Module-Starter-1.71.patch
new file mode 100644
index 000..6bd3a1d
--- /dev/null
+++ b/Module-Starter-Plugin-CGIApp-0.42-Adapt-to-Module-Starter-1.71.patch
@@ -0,0 +1,57 @@
+From a1e8f3b6937be2c8c03de3dfb09ca53ca62be88a Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com
+Date: Thu, 7 May 2015 13:37:53 +0200
+Subject: [PATCH] Adapt to Module-Starter-1.71
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Module-Starter 1.70 and 1.71 changed how test files are created. This
+adjusts to the change.
+
+Filtering t/boilerplate.t from MANIFEST is a hack. I don't understand why
+it's not created into xt directory.
+
+https://bugzilla.redhat.com/show_bug.cgi?id=1189463
+https://rt.cpan.org/Public/Bug/Display.html?id=101894
+https://github.com/xsawyerx/module-starter/issues/47#issuecomment-73425236
+Signed-off-by: Petr Písař ppi...@redhat.com
+---
+ lib/Module/Starter/Plugin/CGIApp.pm | 7 ++-
+ 1 file changed, 2 insertions(+), 5 deletions(-)
+
+diff --git a/lib/Module/Starter/Plugin/CGIApp.pm
b/lib/Module/Starter/Plugin/CGIApp.pm
+index cb0f1b7..f3aa37b 100644
+--- a/lib/Module/Starter/Plugin/CGIApp.pm
b/lib/Module/Starter/Plugin/CGIApp.pm
+@@ -125,7 +125,6 @@ sub create_distro {
+ push @files, $self-create_modules( @{ $self-{modules} } );
+
+ push @files, $self-create_t( @{ $self-{modules} } );
+-push @files, $self-create_xt( @{ $self-{modules} } );
+ push @files, $self-create_tmpl();
+ my %build_results = $self-create_build();
+ push @files, @{ $build_results{files} };
+@@ -147,7 +146,7 @@ sub _create_manifest {
+
+ my $file = File::Spec-catfile( $self-{basedir}, 'MANIFEST' );
+ open my $fh, '', $file or croak Can't open file $file: $OS_ERROR\n;
+-foreach my $file ( sort @files ) {
++foreach my $file ( grep !m{^\Qt/boilerplate.t\E$}, sort @files ) {
+ print {$fh} $file\n or croak $OS_ERROR\n;
+ }
+ close $fh or croak Can't close file $file: $OS_ERROR\n;
+@@ -261,9 +260,7 @@ in the distribution.
+ sub create_t {
+ my ( $self, @modules ) = @_;
+
+-my %t_files = $self-t_guts(@modules);
+-
+-my @files = map { $self-_create_t( $_, $t_files{$_} ) } keys %t_files;
++my @files = $self-SUPER::create_t(@modules);
+
+ # This next part is for the static files dir t/www
+ my @dirparts = ( $self-{basedir}, 't', 'www' );
+--
+2.1.0
+
diff --git a/perl-Module-Starter-Plugin-CGIApp.spec
b/perl-Module-Starter-Plugin-CGIApp.spec
index 702a3af..a98ee22 100644
--- a/perl-Module-Starter-Plugin-CGIApp.spec
+++ b/perl-Module-Starter-Plugin-CGIApp.spec
@@ -1,11 +1,13 @@
Name: perl-Module-Starter-Plugin-CGIApp
Version:0.42
-Release:8%{?dist}
+Release:9%{?dist}
Summary:Template based module starter for CGI apps
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Module-Starter-Plugin-CGIApp/
Source0:
http://www.cpan.org/authors/id/J/JA/JALDHAR/Module-Starter-Plugin-CGIApp-%{version}.tar.gz
+# Adapt to changes in Module-Starter-1.71, bug #1189463, CPAN RT#101894
+Patch0:
Module-Starter-Plugin-CGIApp-0.42-Adapt-to-Module-Starter-1.71.patch
BuildArch: noarch
BuildRequires: perl(File::Copy::Recursive)
BuildRequires: perl(File::DirCompare)
@@ -13,7 +15,8 @@ BuildRequires: perl(File::ShareDir)
BuildRequires: perl(HTML::Template)
BuildRequires: perl(Module::Build)
BuildRequires: perl(Module::Signature)
-BuildRequires: perl(Module::Starter)
+# Constrain Module::Starter version due to bug #1189463
+BuildRequires: perl(Module::Starter) = 1.71
BuildRequires: perl(Pod::Coverage) = 0.18
BuildRequires: perl(Test::Builder)
BuildRequires: perl(Test::MockTime)
@@ -24,8 +27,11 @@ BuildRequires: perl(Test::WWW::Mechanize::CGIApp)
BuildRequires: perl(Time::Piece)
BuildRequires: perl(Titanium)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+Requires: perl(Module::Starter) = 1.71
%{?perl_default_filter}
+# Remove under-specified dependencies:
+%global __requires_exclude
%{?__requires_exclude:%__requires_exclude|}^perl\\(Module::Starter\\)$
%description
This is a plugin for Module::Starter that builds you a skeleton
@@ -34,6 +40,7 @@ CPAN. You can customize the output using HTML::Template.
%prep
%setup -q -n Module-Starter-Plugin-CGIApp-%{version}
+%patch0 -p1
%build
@@ -60,6 +67,9 @@ find $RPM_BUILD_ROOT -depth -type d -exec rmdir {}
2/dev/null \;
%{_mandir}/man3/*
%changelog
+* Thu May 07 2015 Petr Pisar ppi...@redhat.com -
corsepiu pushed to perl-DBIx-DBSchema (f22). Upstream update. (..more)
From 07946b6b8dc4757bfea6b5130aad9d01eb685338 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ralf=20Cors=C3=A9pius?= corse...@fedoraproject.org
Date: Thu, 7 May 2015 15:01:50 +0200
Subject: Upstream update.
- Update BRs.
diff --git a/.gitignore b/.gitignore
index 3bcf636..b834f12 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1 @@
-/DBIx-DBSchema-0.44.tar.gz
+/DBIx-DBSchema-0.45.tar.gz
diff --git a/perl-DBIx-DBSchema.spec b/perl-DBIx-DBSchema.spec
index 9867204..95a921d 100644
--- a/perl-DBIx-DBSchema.spec
+++ b/perl-DBIx-DBSchema.spec
@@ -1,6 +1,6 @@
Name: perl-DBIx-DBSchema
-Version:0.44
-Release:3%{?dist}
+Version:0.45
+Release:1%{?dist}
Summary:Database-independent schema objects
Group: Development/Libraries
@@ -11,11 +11,21 @@ Source0:
http://www.cpan.org/authors/id/I/IV/IVAN/DBIx-DBSchema-%{version}.tar.g
BuildArch: noarch
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo $version))
BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(base)
+BuildRequires: perl(Carp)
+BuildRequires: perl(Data::Dumper)
BuildRequires: perl(DBI)
+BuildRequires: perl(Exporter)
+BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(FreezeThaw)
+BuildRequires: perl(Storable)
+BuildRequires: perl(strict)
+BuildRequires: perl(vars)
+
# Required by the tests
-BuildRequires: perl(DBD::Pg) = 1.32
+BuildRequires: perl(Test::More)
+BuildRequires: perl(DBD::Pg) = 1.41
%description
DBIx::DBSchema objects are collections of DBIx::DBSchema::Table objects and
@@ -57,6 +67,10 @@ make test
%changelog
+* Thu May 07 2015 Ralf Corsépius corse...@fedoraproject.org - 0.45-1
+- Upstream update.
+- Update BRs.
+
* Thu Aug 28 2014 Jitka Plesnikova jples...@redhat.com - 0.44-3
- Perl 5.20 rebuild
diff --git a/sources b/sources
index 074ee05..fdb8d8e 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-303de52e8dc2ca2f33407592db6bd7b0 DBIx-DBSchema-0.44.tar.gz
+45f2d5c134fd3f74afa378c8e33bc65f DBIx-DBSchema-0.45.tar.gz
--
cgit v0.10.2
http://pkgs.fedoraproject.org/cgit/perl-DBIx-DBSchema.git/commit/?h=f22id=07946b6b8dc4757bfea6b5130aad9d01eb685338
--
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 1219466] New: perl-Config-Properties-1.79 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1219466 Bug ID: 1219466 Summary: perl-Config-Properties-1.79 is available Product: Fedora Version: rawhide Component: perl-Config-Properties Keywords: FutureFeature, Triaged Assignee: xav...@bachelot.org Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, xav...@bachelot.org Latest upstream release: 1.79 Current version/release in rawhide: 1.77-2.fc22 URL: http://search.cpan.org/dist/Config-Properties/ 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 Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
FYI: Firefox - No more binary components in extensions
Forwarded Message Subject: No more binary components in extensions Date: Mon, 4 May 2015 11:03:12 -0400 From: Benjamin Smedberg benja...@smedbergs.us Reply-To: dev-extensi...@lists.mozilla.org To: dev-platform dev-platf...@lists.mozilla.org, Firefox Dev firefox-...@mozilla.org, dev-extensi...@lists.mozilla.org (Followup questions or comments to mozilla.dev.extensions only, please.) With the landing of bug 1159737, I have removed support for binary XPCOM components in extensions. This is planned to ride the Firefox 40 train. This change is necessary because we no longer expose or intend to expose a binary-stable API to XPCOM. Most addons have already moved away from binary XPCOM components, but those that haven't are a source of instability around Firefox releases. Extension authors that need to use native binaries are encouraged to do so using the addon SDK system/child_process pipe mechanism: https://developer.mozilla.org/en-US/Add-ons/SDK/Low-Level_APIs/system_child_process If this is not sufficient, JS-ctypes may be an alternative mechanism to use shared libraries, but this API is much more fragile and it's easy to write unsafe code. I will be updating MDN documentation and removing or archiving old documentation about binary XPCOM components in the next few weeks. --BDS ___ dev-platform mailing list dev-platf...@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform -- 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 1219466] perl-Config-Properties-1.79 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1219466 --- Comment #2 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Scratch build succeeded http://koji.fedoraproject.org/koji/taskinfo?taskID=9677803 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
corsepiu pushed to perl-DBIx-DBSchema (master). Upstream update. (..more)
From 07946b6b8dc4757bfea6b5130aad9d01eb685338 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ralf=20Cors=C3=A9pius?= corse...@fedoraproject.org
Date: Thu, 7 May 2015 15:01:50 +0200
Subject: Upstream update.
- Update BRs.
diff --git a/.gitignore b/.gitignore
index 3bcf636..b834f12 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1 @@
-/DBIx-DBSchema-0.44.tar.gz
+/DBIx-DBSchema-0.45.tar.gz
diff --git a/perl-DBIx-DBSchema.spec b/perl-DBIx-DBSchema.spec
index 9867204..95a921d 100644
--- a/perl-DBIx-DBSchema.spec
+++ b/perl-DBIx-DBSchema.spec
@@ -1,6 +1,6 @@
Name: perl-DBIx-DBSchema
-Version:0.44
-Release:3%{?dist}
+Version:0.45
+Release:1%{?dist}
Summary:Database-independent schema objects
Group: Development/Libraries
@@ -11,11 +11,21 @@ Source0:
http://www.cpan.org/authors/id/I/IV/IVAN/DBIx-DBSchema-%{version}.tar.g
BuildArch: noarch
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo $version))
BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(base)
+BuildRequires: perl(Carp)
+BuildRequires: perl(Data::Dumper)
BuildRequires: perl(DBI)
+BuildRequires: perl(Exporter)
+BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(FreezeThaw)
+BuildRequires: perl(Storable)
+BuildRequires: perl(strict)
+BuildRequires: perl(vars)
+
# Required by the tests
-BuildRequires: perl(DBD::Pg) = 1.32
+BuildRequires: perl(Test::More)
+BuildRequires: perl(DBD::Pg) = 1.41
%description
DBIx::DBSchema objects are collections of DBIx::DBSchema::Table objects and
@@ -57,6 +67,10 @@ make test
%changelog
+* Thu May 07 2015 Ralf Corsépius corse...@fedoraproject.org - 0.45-1
+- Upstream update.
+- Update BRs.
+
* Thu Aug 28 2014 Jitka Plesnikova jples...@redhat.com - 0.44-3
- Perl 5.20 rebuild
diff --git a/sources b/sources
index 074ee05..fdb8d8e 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-303de52e8dc2ca2f33407592db6bd7b0 DBIx-DBSchema-0.44.tar.gz
+45f2d5c134fd3f74afa378c8e33bc65f DBIx-DBSchema-0.45.tar.gz
--
cgit v0.10.2
http://pkgs.fedoraproject.org/cgit/perl-DBIx-DBSchema.git/commit/?h=masterid=07946b6b8dc4757bfea6b5130aad9d01eb685338
--
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
corsepiu pushed to perl-DBIx-DBSchema (f21). Cleanup merger.
From 7153b11784ff900b2cb7d73fb744f605a3c88c00 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ralf=20Cors=C3=A9pius?= corse...@fedoraproject.org Date: Thu, 7 May 2015 15:11:52 +0200 Subject: Cleanup merger. diff --git a/perl-DBIx-DBSchema.spec b/perl-DBIx-DBSchema.spec index 95a921d..c2c014b 100644 --- a/perl-DBIx-DBSchema.spec +++ b/perl-DBIx-DBSchema.spec @@ -71,9 +71,6 @@ make test - Upstream update. - Update BRs. -* Thu Aug 28 2014 Jitka Plesnikova jples...@redhat.com - 0.44-3 -- Perl 5.20 rebuild - * Sat Jun 07 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org - 0.44-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild -- cgit v0.10.2 http://pkgs.fedoraproject.org/cgit/perl-DBIx-DBSchema.git/commit/?h=f21id=7153b11784ff900b2cb7d73fb744f605a3c88c00 -- 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
corsepiu pushed to perl-DBIx-DBSchema (f21). Perl 5.20 rebuild
From e48186a241eedf7e52db7e48ed4b101932dd0443 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova jples...@redhat.com
Date: Thu, 28 Aug 2014 03:17:15 +0200
Subject: Perl 5.20 rebuild
diff --git a/perl-DBIx-DBSchema.spec b/perl-DBIx-DBSchema.spec
index 57e31bc..9867204 100644
--- a/perl-DBIx-DBSchema.spec
+++ b/perl-DBIx-DBSchema.spec
@@ -1,6 +1,6 @@
Name: perl-DBIx-DBSchema
Version:0.44
-Release:2%{?dist}
+Release:3%{?dist}
Summary:Database-independent schema objects
Group: Development/Libraries
@@ -57,6 +57,9 @@ make test
%changelog
+* Thu Aug 28 2014 Jitka Plesnikova jples...@redhat.com - 0.44-3
+- Perl 5.20 rebuild
+
* Sat Jun 07 2014 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.44-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
--
cgit v0.10.2
http://pkgs.fedoraproject.org/cgit/perl-DBIx-DBSchema.git/commit/?h=f21id=e48186a241eedf7e52db7e48ed4b101932dd0443
--
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
corsepiu pushed to perl-DBIx-DBSchema (f21). Upstream update. (..more)
From 07946b6b8dc4757bfea6b5130aad9d01eb685338 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ralf=20Cors=C3=A9pius?= corse...@fedoraproject.org
Date: Thu, 7 May 2015 15:01:50 +0200
Subject: Upstream update.
- Update BRs.
diff --git a/.gitignore b/.gitignore
index 3bcf636..b834f12 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1 @@
-/DBIx-DBSchema-0.44.tar.gz
+/DBIx-DBSchema-0.45.tar.gz
diff --git a/perl-DBIx-DBSchema.spec b/perl-DBIx-DBSchema.spec
index 9867204..95a921d 100644
--- a/perl-DBIx-DBSchema.spec
+++ b/perl-DBIx-DBSchema.spec
@@ -1,6 +1,6 @@
Name: perl-DBIx-DBSchema
-Version:0.44
-Release:3%{?dist}
+Version:0.45
+Release:1%{?dist}
Summary:Database-independent schema objects
Group: Development/Libraries
@@ -11,11 +11,21 @@ Source0:
http://www.cpan.org/authors/id/I/IV/IVAN/DBIx-DBSchema-%{version}.tar.g
BuildArch: noarch
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo $version))
BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(base)
+BuildRequires: perl(Carp)
+BuildRequires: perl(Data::Dumper)
BuildRequires: perl(DBI)
+BuildRequires: perl(Exporter)
+BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(FreezeThaw)
+BuildRequires: perl(Storable)
+BuildRequires: perl(strict)
+BuildRequires: perl(vars)
+
# Required by the tests
-BuildRequires: perl(DBD::Pg) = 1.32
+BuildRequires: perl(Test::More)
+BuildRequires: perl(DBD::Pg) = 1.41
%description
DBIx::DBSchema objects are collections of DBIx::DBSchema::Table objects and
@@ -57,6 +67,10 @@ make test
%changelog
+* Thu May 07 2015 Ralf Corsépius corse...@fedoraproject.org - 0.45-1
+- Upstream update.
+- Update BRs.
+
* Thu Aug 28 2014 Jitka Plesnikova jples...@redhat.com - 0.44-3
- Perl 5.20 rebuild
diff --git a/sources b/sources
index 074ee05..fdb8d8e 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-303de52e8dc2ca2f33407592db6bd7b0 DBIx-DBSchema-0.44.tar.gz
+45f2d5c134fd3f74afa378c8e33bc65f DBIx-DBSchema-0.45.tar.gz
--
cgit v0.10.2
http://pkgs.fedoraproject.org/cgit/perl-DBIx-DBSchema.git/commit/?h=f21id=07946b6b8dc4757bfea6b5130aad9d01eb685338
--
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
delete changed cra's 'commit' permission on perl-File-KeePass (el5) to 'Approved'
delete changed cra's 'commit' permission on perl-File-KeePass (el5) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-KeePass/ -- 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
delete changed cra's 'commit' permission on perl-File-KeePass (f21) to 'Approved'
delete changed cra's 'commit' permission on perl-File-KeePass (f21) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-KeePass/ -- 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
delete changed cra's 'commit' permission on perl-File-KeePass (f22) to 'Approved'
delete changed cra's 'commit' permission on perl-File-KeePass (f22) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-KeePass/ -- 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: [EPEL-devel] wine 32
On Wednesday, May 06, 2015 06:53:54 PM Stephen John Smoogen wrote: On 6 May 2015 at 18:21, ToddAndMargo toddandma...@zoho.com wrote: On 05/06/2015 09:31 AM, Stephen John Smoogen wrote: On 6 May 2015 at 00:28, ToddAndMargo toddandma...@zoho.com wrote: Hi Kevin and EPEL, Is there any sign of EPEL 7 support for Wine 32 yet? The lack of Wine 32 is keeping me on SL 6.6 and it is starting to drive me nuts! EPEL: think of the guilt you would feel if I get stuck in an insane asylums over the lack of wine 32 support! Seriously, the guilt would haunt you to the end of your days. Okay, maybe not, but still ... Sadly it isn't possible in EPEL. There are not enough of the i686 libraries available to compile all the tools needed. It will require people actually doing the work to making an i686 CentOS or Scientific Linux but that only seems possible if the glibc/kernel/some other tools are not the same as in x86_64 and it would require people to actually do the work which no one has shown much effort in wanting to do. Hi Steven, Does this help? https://www.centos.org/forums/viewtopic.php?f=48t=49542 Seems like most of the thinking has already been done. Not really. That works well for building it yourself and you should follow those instructions for your own benefit. It doesn't work in our build system for various reasons I can give hand-wavey answers to but Dennis Gilmore or another Release Engineer could answer in depth if you need. [And from my last asking about this.. it isn't something that can be fixed simply.] a few issues, the biggest one is that koji enforces single arch in the buildroots. so we can only build i686 in a i686 chroot. since we do not have enough i686 content to enable building i686 its not possible that route. the other way to try and do it would be to cross build the world so that we have x86_64 rpms with 32 bit content in them. that would require exeptions to the packaging guidelines, and somoene to write new specs for every package needed and to get them through review. in the end you would have to use a non rhel evironment and you would have say glibc32 openssl32 etc x86_64 rpms that means a massive support burden. without Red Hat providing full 32 bit trees its just not a realistic option to support any 32 bit builds for epel7 Dennis signature.asc Description: This is a digitally signed message part. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: Review Swap
Thanks. Taken. Marek gil píše v St 06. 05. 2015 v 19:14 +0200: Take! can you review this https://bugzilla.redhat.com/show_bug.cgi?id=1214385 ? regards gil Il 06/05/2015 17:53, Marek Skalický ha scritto: Is anyone up for a review swap? I want to get mongo-tools into Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1218277 Let me know what I can review for you in return. Thanks, Marek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
rawhide report: 20150507 changes
Compose started at Thu May 7 05:15:03 UTC 2015 Broken deps for i386 -- [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [aeskulap] aeskulap-0.2.2-0.19beta1.fc22.i686 requires libofstd.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires liboflog.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg8.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg16.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg12.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmnet.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmjpeg.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmimgle.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmimage.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmdata.so.3.6 [concordance] libconcord-1.2-1.fc23.i686 requires libzip.so.2 [crystal] crystal-2.2.1-2.fc22.i686 requires libkdecorations.so.4 [dleyna-connector-dbus] dleyna-connector-dbus-0.2.0-4.fc22.i686 requires libdleyna-core-1.0.so.3 [dleyna-renderer] dleyna-renderer-0.4.0-4.fc22.i686 requires libdleyna-core-1.0.so.3 [dleyna-server] dleyna-server-0.4.0-7.fc23.i686 requires libdleyna-core-1.0.so.3 [dmlite-plugins-memcache] dmlite-plugins-memcache-0.5.0-7.fc20.i686 requires libprotobuf.so.8 [dmlite-plugins-s3] dmlite-plugins-s3-0.5.1-5.fc22.i686 requires libprotobuf.so.8 [dsqlite] dsqlite-1.1.1-5.fc22.i686 requires libphobos-ldc.so.64 [gazebo] gazebo-4.0.2-2.fc22.i686 requires libprotobuf.so.8 gazebo-libs-4.0.2-2.fc22.i686 requires libprotobuf.so.8 player-gazebo-4.0.2-2.fc22.i686 requires libprotobuf.so.8 [gl3n] gl3n-0.20140505-13.fc22.i686 requires libphobos-ldc.so.64 [julia] julia-0.3.7-2.fc23.i686 requires libLLVM-3.5.so julia-devel-0.3.7-2.fc23.i686 requires libLLVM-3.5.so [kde-style-skulpture] kde-style-skulpture-0.2.4-9.fc22.i686 requires libkdecorations.so.4 [latte-integrale] 4ti2-1.6.2-9.fc23.1.i686 requires 4ti2-libs(x86-32) = 0:1.6.2-9.fc23 4ti2-devel-1.6.2-9.fc23.1.i686 requires 4ti2-libs(x86-32) = 0:1.6.2-9.fc23 [leksah] ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSxhtml-3000.2.1-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSutf8-string-0.3.7-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSunix-2.6.0.1-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHStransformers-0.3.0.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHStime-1.4.0.1-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHStext-0.11.3.1-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHStemplate-haskell-2.8.0.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSstrict-0.3.2-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSregex-tdfa-1.1.8-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSregex-base-0.93.2-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSrandom-1.0.1.1-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSprocess-1.1.0.2-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSpretty-1.1.1.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSparsec-3.1.3-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSpango-0.12.5.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSold-time-1.1.0.1-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSold-locale-1.0.0.5-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSnetwork-2.4.1.2-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSmtl-2.1.2-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSltk-0.12.1.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSleksah-server-0.12.1.2-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSinteger-gmp-0.5.0.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHShslogger-1.2.1-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHShpc-0.6.0.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHShoopl-3.9.0.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHShaddock-2.13.2-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSgtksourceview2-0.12.5.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSgtk-0.12.5.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSglib-0.12.5.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSgio-0.12.5.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSghc-prim-0.3.0.0-ghc7.6.3.so ghc-leksah-0.12.1.3-16.fc22.i686 requires libHSghc-paths-0.1.0.9-ghc7.6.3.so
delete changed cra's 'commit' permission on perl-File-KeePass (f20) to 'Approved'
delete changed cra's 'commit' permission on perl-File-KeePass (f20) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-KeePass/ -- 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
delete changed cra's 'commit' permission on perl-File-KeePass (el6) to 'Approved'
delete changed cra's 'commit' permission on perl-File-KeePass (el6) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-KeePass/ -- 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
delete changed cra's 'commit' permission on perl-File-KeePass (epel7) to 'Approved'
delete changed cra's 'commit' permission on perl-File-KeePass (epel7) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-KeePass/ -- 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
[389-devel] Please review: [389 Project] #48148: start/stop/restart-dirsrv utilities should ignore admin-serv directory (1.2.11 only)
https://fedorahosted.org/389/ticket/48148 https://fedorahosted.org/389/attachment/ticket/48148/0001-Ticket-48148-start-stop-restart-dirsrv-utilities-sho.2.patch git patch file (1.2.11 branch) -- additional fix for restart-dirsrv and non-root user -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
[389-devel] Please review (take 2): [389 Project] #48148: start/stop/restart-dirsrv utilities should ignore admin-serv directory (1.2.11 only)
https://fedorahosted.org/389/ticket/48148 https://fedorahosted.org/389/attachment/ticket/48148/0001-Ticket-48148-start-stop-restart-dirsrv-utilities-sho.3.patch git patch file (1.2.11 branch) -- revised: additional fix for restart-dirsrv and non-root user Thanks to Rich for his suggestions! Updated the patch accordingly. --noriko -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: Review or swap for burp - network backup
Hi I'm not sure if AGPLV3 is a valid license for Fedora Requested the intervention of Fedora Legal Tracker guys, for a check Note: i asked not long ago if neo4j project, with the same Affero General Public License, can be imported in Fedora, but is not possible for my case. If the package can be imported can you review this https://bugzilla.redhat.com/show_bug.cgi?id=1214396 for me? thanks regards gil [1] https://github.com/neo4j/neo4j http://www.neo4j.org/ Il 07/05/2015 17:18, Andrew Niemantsverdriet ha scritto: Hello Everyone, I have a package that I would like reviewed: https://bugzilla.redhat.com/show_bug.cgi?id=1186819 * * Burp is a network backup program, it provides a way automate backups. I would appreciate a review and I'm willing to do a review swap with somebody. Thank you, -- _ /-\ ndrew Niemantsverdriet Linux System Administrator Academic Computing (406) 238-7360 Rocky Mountain College 1511 Poly Dr. Billings MT, 59102 -- 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: Review or swap for burp - network backup
On Thu, May 7, 2015 at 3:33 PM, gil punto...@libero.it wrote: Hi I'm not sure if AGPLV3 is a valid license for Fedora See https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#SoftwareLicenses for lists of good and bad licenses. AGPLv3 is on the list of good licenses. HTH. Regards, -- Jerry James http://www.jamezone.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Review or swap for burp - network backup
Il 08/05/2015 00:37, Jerry James ha scritto: On Thu, May 7, 2015 at 3:33 PM, gil punto...@libero.it wrote: Hi I'm not sure if AGPLV3 is a valid license for Fedora See https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#SoftwareLicenses for lists of good and bad licenses. AGPLv3 is on the list of good licenses. HTH. Regards, yes i know but that page seem not updated ... -- 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: Unison in Fedora
On Thu, 7 May 2015 09:17:10 +0100 Richard W.M. Jones rjo...@redhat.com wrote: [Previous discussion here: https://lists.fedoraproject.org/pipermail/devel/2011-September/thread.html#157495 ] (I guess I was cc'ed directly because I replied in that thread? There's no need, I am still on this list. ;) Unison is a fairly widely used file synchronization package. Think of it as a more efficient, multi-directional 'rsync'. Unison has the unfortunate property that versions of Unison are not compatible with each other unless they have the exact same major.minor release. eg. Unison 2.40.128 is compatible with Unison 2.40.102, but incompatible with Unison 2.48.3 (the latest upstream). ...snip... Anyway, I think this situation is crazy. One reason is that in order to add the latest upstream Unison (2.48) I'm going to have to submit a new unison248 package[1]. And then if there's another version, I'll have to submit a new package for that. I think Fedora should have a single unison source package, and it should contain the multiple upstream branch sources and build different binary subpackages. The binary subpackages would have the same names as now (unison227 etc), making this a compatible update for existing Fedora Unison users. This way I only need to submit a single new package review, we can delete the unison2xx source packages, and there'll be a single place for unison in Fedora for ever more. Discuss ... Well, just as mentioned in the previous thread, if you do things this way it means every user of any unison will have to get a useless update everytime any version of unison in your combined package updates for any reason. Thats pretty disruptive. kevin pgpQtiUBuL4rD.pgp 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
Review or swap for burp - network backup
Hello Everyone, I have a package that I would like reviewed: https://bugzilla.redhat.com/show_bug.cgi?id=1186819 Burp is a network backup program, it provides a way automate backups. I would appreciate a review and I'm willing to do a review swap with somebody. Thank you, -- _ /-\ ndrew Niemantsverdriet Linux System Administrator Academic Computing (406) 238-7360 Rocky Mountain College 1511 Poly Dr. Billings MT, 59102 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
delete changed cra's 'commit' permission on perl-File-KeePass (master) to 'Approved'
delete changed cra's 'commit' permission on perl-File-KeePass (master) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-File-KeePass/ -- 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: Unison in Fedora
On 7 May 2015 at 08:41, Kevin Fenzi ke...@scrye.com wrote: On Thu, 7 May 2015 09:17:10 +0100 Richard W.M. Jones rjo...@redhat.com wrote: [Previous discussion here: https://lists.fedoraproject.org/pipermail/devel/2011-September/thread.html#157495 ] (I guess I was cc'ed directly because I replied in that thread? There's no need, I am still on this list. ;) Unison is a fairly widely used file synchronization package. Think of it as a more efficient, multi-directional 'rsync'. Unison has the unfortunate property that versions of Unison are not compatible with each other unless they have the exact same major.minor release. eg. Unison 2.40.128 is compatible with Unison 2.40.102, but incompatible with Unison 2.48.3 (the latest upstream). ...snip... Anyway, I think this situation is crazy. One reason is that in order to add the latest upstream Unison (2.48) I'm going to have to submit a new unison248 package[1]. And then if there's another version, I'll have to submit a new package for that. I think Fedora should have a single unison source package, and it should contain the multiple upstream branch sources and build different binary subpackages. The binary subpackages would have the same names as now (unison227 etc), making this a compatible update for existing Fedora Unison users. This way I only need to submit a single new package review, we can delete the unison2xx source packages, and there'll be a single place for unison in Fedora for ever more. Discuss ... Well, just as mentioned in the previous thread, if you do things this way it means every user of any unison will have to get a useless update everytime any version of unison in your combined package updates for any reason. Thats pretty disruptive. I think the issue is that none of those versions are getting updates anymore. They are dead code... any fix that is going to be in one is probably going to be in all of them so they would all need it. -- Stephen J Smoogen. -- 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 1086545] Upgrade to new upstream version
https://bugzilla.redhat.com/show_bug.cgi?id=1086545 lionel.c...@cern.ch changed: What|Removed |Added Status|MODIFIED|CLOSED Resolution|--- |WORKSFORME Last Closed||2015-05-07 02:01:19 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
corsepiu uploaded DBIx-DBSchema-0.45.tar.gz for perl-DBIx-DBSchema
45f2d5c134fd3f74afa378c8e33bc65f DBIx-DBSchema-0.45.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-DBIx-DBSchema/DBIx-DBSchema-0.45.tar.gz/45f2d5c134fd3f74afa378c8e33bc65f/DBIx-DBSchema-0.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 1219469] New: perl-DBIx-DBSchema-0.45 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1219469 Bug ID: 1219469 Summary: perl-DBIx-DBSchema-0.45 is available Product: Fedora Version: rawhide Component: perl-DBIx-DBSchema Keywords: FutureFeature, Triaged Assignee: rc040...@freenet.de Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: lxt...@gmail.com, perl-devel@lists.fedoraproject.org, rc040...@freenet.de Latest upstream release: 0.45 Current version/release in rawhide: 0.44-3.fc22 URL: http://search.cpan.org/dist/DBIx-DBSchema/ 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 Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1219469] perl-DBIx-DBSchema-0.45 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1219469 --- Comment #1 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Created attachment 1023092 -- https://bugzilla.redhat.com/attachment.cgi?id=1023092action=edit [patch] Update to 0.45 (#1219469) -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-PDL-Graphics-PLplot
perl-PDL-Graphics-PLplot has broken dependencies in the rawhide tree: On x86_64: perl-PDL-Graphics-PLplot-0.67-5.fc22.x86_64 requires libplplotd.so.12()(64bit) On i386: perl-PDL-Graphics-PLplot-0.67-5.fc22.i686 requires libplplotd.so.12 On armhfp: perl-PDL-Graphics-PLplot-0.67-5.fc22.armv7hl requires libplplotd.so.12 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 1219469] perl-DBIx-DBSchema-0.45 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1219469 Ralf Corsepius rc040...@freenet.de changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed||2015-05-07 08:54:34 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Unison in Fedora
On 05/07/2015 04:58 PM, Stephen John Smoogen wrote: On 7 May 2015 at 08:41, Kevin Fenzi ke...@scrye.com wrote: On Thu, 7 May 2015 09:17:10 +0100 Richard W.M. Jones rjo...@redhat.com wrote: [Previous discussion here: https://lists.fedoraproject.org/pipermail/devel/2011-September/thread.html#157495 ] (I guess I was cc'ed directly because I replied in that thread? There's no need, I am still on this list. ;) Unison is a fairly widely used file synchronization package. Think of it as a more efficient, multi-directional 'rsync'. Unison has the unfortunate property that versions of Unison are not compatible with each other unless they have the exact same major.minor release. eg. Unison 2.40.128 is compatible with Unison 2.40.102, but incompatible with Unison 2.48.3 (the latest upstream). This is because of these compatibility problems and the absence of Unison 2.48.3 in the official repo that I packaged Unison 2.48 in copr. I didn't go any further because I hadn't the time. ...snip... Anyway, I think this situation is crazy. One reason is that in order to add the latest upstream Unison (2.48) I'm going to have to submit a new unison248 package[1]. And then if there's another version, I'll have to submit a new package for that. I think Fedora should have a single unison source package, and it should contain the multiple upstream branch sources and build different binary subpackages. The binary subpackages would have the same names as now (unison227 etc), making this a compatible update for existing Fedora Unison users. This way I only need to submit a single new package review, we can delete the unison2xx source packages, and there'll be a single place for unison in Fedora for ever more. Discuss ... Well, just as mentioned in the previous thread, if you do things this way it means every user of any unison will have to get a useless update everytime any version of unison in your combined package updates for any reason. Thats pretty disruptive. Maybe something like debian does : propose a unison (or unison-all) package that always pull all the supported version of unison but let the user install just a specific version. I think the issue is that none of those versions are getting updates anymore. They are dead code... any fix that is going to be in one is probably going to be in all of them so they would all need it. I think after a certain amount of time it is reasonable to think that the old version are not required any more. The question is how to decide that? -- Julien Enselme aka Jujens http://www.jujens.eu/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
