Re: what is initramfs-0-rescue in F19?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.04.2013 17:03, schrieb Reindl Harald: ok, with dracut-nohostonly installed you become /usr/lib/dracut/dracut.conf.d/02-nohostonly.conf which is overriden by the since a long time existing /etc/dracut.conf.d/91-host-only.conf to have the same behavior as before and nobody thinks that tjis is a little pervert? [root@rawhide boot]# cat /usr/lib/dracut/dracut.conf.d/02-nohostonly.conf hostonly=no [root@rawhide boot]# cat /etc/dracut.conf.d/91-host-only.conf hostonly=yes works as intended, with the exception that I meant you to install dracut-norescue... My fault. Am 07.04.2013 15:06, schrieb Harald Hoyer: install dracut-nohostonly if you don't want that... see the Release Notes of http://fedoraproject.org/wiki/Features/DracutHostOnly On Sun, Apr 7, 2013 at 12:37 AM, Reindl Harald h.rei...@thelounge.net wrote: -rw--- 1 root root 18M 22. Mär 17:06 initramfs-0-rescue-74e76163c28448fba68b8667eb7b5d92.img -rw--- 1 root root 5,2M 7. Apr 00:34 initramfs-3.9.0-0.rc5.git1.301.fc19.x86_64.img is this the result of http://fedoraproject.org/wiki/Features/DracutHostOnly wasting space on virtual machines using hostonly since forever? [root@rawhide dracut.conf.d]# cat 91-host-only.conf hostonly=yes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRYmWFAAoJEANOs3ABTfJwpx8P/0+41QSRsXRqyWoQWXAHMC6J ldVtrDqPvyNrdSJgRD4kWxwmGT9h4ASFDed5NfcZa1DOudBFr6idvfJWnLb2T4+I 2RkU5jlXJt7kpNxjwh1ruRv8Z751Rneu+z9z62S0DYxZxBPIWAhO6EP9Ppu647Ck MwDphpq9RD3oDOcS6xIDi+yGbBPn0ajP9cTOp7tJloEruWNb9pGhttdyuFHmOakA 0rIyPcVdb5ikbSibduoQ0ttoSeXlx4Vd+SEZC5ciEhPejJVZW5dyXgptfxWIwwWS uecool1Y0pHKXOTJxumWK6rbgzBNDreNhH80q8ae3QvCjCSuezNap0gk9OVD5mUx ou9M3BqW3MlmRwib1uMFPMVyo3IB+mXtsYIrJw8WWbE3/leax5c3rAhyoMLQtKRa HwWmKVw3HLuBtwUoIP0af2x9/t8BnfTZOJ8uDbt+FSX0QR7QdYSQ+s21xypyz+fP Xf9MR3F4Kdzw4sylUlv0z+OWAL4boKAymO9E9VjusDMDhgm8tQHpXbjCeHzURE79 nDiUuyP1EUBlipO7mVWyDX8vhA+J/oW6Jg1JU/Nv+otetQd+ABadAEYM8wHQeE+y 7xsRNGfRQ6SdAPOlBisFR6FbR0bW1i+ikgjY9ZXa6UYVGhPSeQdI0SPxxWcgahtm q5zS0Plygzr5rdUGwbSB =BqHz -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 949145] perl-App-cpanminus-1.6105 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=949145 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC|mmasl...@redhat.com |ppi...@redhat.com Assignee|mmasl...@redhat.com |ppi...@redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=HsNRzA5341a=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File App-cpanminus-1.6105.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-App-cpanminus: 8c17979d4e8c9ac2ad3b26e823369d55 App-cpanminus-1.6105.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
yum progress/speed indicator for deltarpm rebuilding?
Now that deltarpm support is included in yum, and yum-presto is obsoleted, are there any plans to include a progress/speed indicator for deltarpm rebuilding, similar to what yum-presto had? Currently, there's no easy way to compare the speed of updates using drpms to that without. Even timing manually, each update is different, so short of doing the same update both ways by using a yum downgrade in between, it's not possible. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Undeprecating libsidplay and fbg
Hi, On 04/08/2013 12:01 AM, Michael Schwendt wrote: On Sun, 07 Apr 2013 22:42:11 +0200, Hans de Goede wrote: This is not only about free-ness this is also about some multimedia players (notably the gstreamer framework) not having libsidplay v2 support. That's all? Will it ever support libsidplay v2 or libsidplayfp, if distributions continue to include libsidplay v1? Some distributions even build with libsidplay v1 but [cluelessly] link to the sidplay2 home page. Building GStreamer only for libsidplay v1 means that it cannot play .sid files in PSID v2NG and RSID format. That's not very useful. http://www.hvsc.c64.org/#question9 There's not even any guarantee that it could play all .sid files with a PSID header, because if that file had been tested in a more capable SID player only, it could be that it doesn't work with libsidplay v1. Even the officially registered MIME type for .sid files (audio/prs.sid) covers RSID files, which would not be supported by GStreamer. The original message about retiring libsidplay v1 before F18: http://lists.fedoraproject.org/pipermail/devel/2012-May/167573.html If you worry just about GStreamer, I think it does a disservice to the community if it doesn't support any of the later and more capable SID music playing libs. Ok, you've got me convinced, I'll closing the review request and look into porting the gstreamer plugin ti sidplay v2. Regards, Hans -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On 04/05/2013 08:06 PM, Norvald Ryeng wrote: - hho...@redhat.com wrote: On 03/21/2013 08:36 PM, Norvald Ryeng wrote: What is the deadline for fixing the remaining issues with MySQL and MariaDB in Fedora? We would like to find a solution and get 5.6 in soon. Hi Norvald, I've just asked for creating component community-mysql, as discussed on fedora-devel above, the review is done already. As soon as it is built in koji I'm going to EOL MySQL component. So I'm expecting to be done in the beginning of the next week. I see you've bumped the epoch of the MariaDB packages to force MariaDB as default when both MySQL and MariaDB provide mysql-server. We've tested it, and it seems to do the trick. Could you rename the MySQL packages to mysql-community-* instead of community-mysql-*? That way the prefix aligns with the product name and OpenSuSE's prefix. I wanted to use that, but then found out that it wouldn't work. The problem is that it has the same prefix as virtual name mysql, that is used as requirement in other packages. As a result, when somebody asked for mysql -- mysql-community would be preferred before mariadb, because according [1] rule #9 (check the prefix of the pkg to the requiring pkg prefix (perl-foo and perl-lib) for each common character in the prefix add 2 points to the provider's score) would be applied. When we use the name community-mysql we don't have any same prefix, so the rule #10 is applied (if, at this point, we have pkgs with an equal score - look at the version of the provide), which means mariadb with higher epoch will be chosen. Generally, I don't like either, that packages in openSUSE an Fedora won't have the same name, but openSUSE has a bit more powerful RPM spec to handle such things. [1] http://yum.baseurl.org/wiki/CompareProviders How do we get push access to the git repo? It would be great to get 5.6 in before the test day on April 30. To get involved, just follow standard process as described on Fedora wiki: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers However, I'd rather wait with 5.6 until F20 because of the following reasons: * we are almost a month after feature freeze * I believe users will have enough concerns with switching to MariaDB and MySQL-5.6 would bring others * better wait a bit longer to stabilize the new release than bring a quite important package too soon Regards, Honza -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Explicit versioning of library names [was Re: package, package2, package3 naming-with-version exploit]
Dne 5.4.2013 22:03, Toshio Kuratomi napsal(a): On Fri, Apr 05, 2013 at 10:53:53AM +0200, Vít Ondruch wrote: Dne 4.4.2013 20:07, Toshio Kuratomi napsal(a): There is also an unwritten (I think it's unwritten. A quick search didn't find it in the guidelines) rule that in Fedora, the current version of the library carries the base name. Older libraries carry the version in the name. Interesting ... it seems time is changing. I made several attempts to make this unwritten rule to be written, the last wrap up and my latest proposal can be found here: http://lists.fedoraproject.org/pipermail/packaging/2012-October/008740.html Your proposals keep failing because they run contrary to the unwritten rules rather than canonifying them. May be I missing something, but what is different in Always consider to let a nonversioned package to follow an upstream release versions. The other versions of package kept in Fedora for compatibility reasons should be either prefixed by compat- prefix or their name should be suffixed by version string. contrary to the current version of the library carries the base name. Older libraries carry the version in the name. Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: package, package2, package3 naming-with-version exploit
On Sun, Apr 07, 2013 at 07:11:44AM -0400, Nico Kadel-Garcia wrote: Why was Java 1.4 succeeded by Java 5? Why was ICU 4.8.1 succeeded by ICU 49.1? Why does systemd have version 197 instead of 1.9.7 or somesuch? If you look at the source code and the package names, Java wasn't really renumbered that badly, Java 1.4 was succeeded by Java 1.5, and Java 1.5 by Java 1.6. They're just marketed misleadingly. Sun's desicsion to screw up numbering this way is a reflection of when they tried to SunOS 4 as Solaris 2.5. You are totally missing the point. What I tried to convey is that expectation that every upstream adheres to your favourite versioning scheme is not based on reality. You cannot base an argument on it, because the premise is already invalid. (Did I already say that in the part that you removed?) And yes, there actually _are_ projects that use the usual X.Y.Z versioning scheme, but _did not_ start with version 1.0.0. What comes immediately to my mind is libreoffice (the first release was 3.3.0) or libexttextcat (the first release was 3.2.0). And don't *get* me going on mod_perl numbering or CPAN version numbering. (Whose bright idea was it to use floating point? Version 2.237 is older than version 2.3 ?) Another point for my case. D. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20130408 changes
Compose started at Mon Apr 8 08:15:20 UTC 2013 Broken deps for x86_64 -- [TurboGears2] TurboGears2-2.1.4-5.fc19.noarch requires python-webob = 0:1.1.1 [aeolus-conductor] aeolus-conductor-0.10.6-2.fc19.noarch requires ruby(abi) = 0:1.9.1 [alexandria] alexandria-0.6.9-4.fc19.noarch requires ruby(abi) = 0:1.9.1 [amide] amide-1.0.0-4.fc19.x86_64 requires libvolpack.so.1()(64bit) [clementine] clementine-1.1.1-1.fc19.x86_64 requires libprotobuf.so.7()(64bit) clementine-1.1.1-1.fc19.x86_64 requires libimobiledevice.so.3()(64bit) [connman] connman-1.5-4.fc19.i686 requires libxtables.so.7 connman-1.5-4.fc19.i686 requires libgnutls.so.26(GNUTLS_1_4) connman-1.5-4.fc19.i686 requires libgnutls.so.26 connman-1.5-4.fc19.x86_64 requires libxtables.so.7()(64bit) connman-1.5-4.fc19.x86_64 requires libgnutls.so.26(GNUTLS_1_4)(64bit) connman-1.5-4.fc19.x86_64 requires libgnutls.so.26()(64bit) [deltacloud-core] deltacloud-core-1.0.5-2.fc19.noarch requires ruby(abi) = 0:1.9.1 [dragonegg] dragonegg-3.1-19.fc19.x86_64 requires gcc = 0:4.7.2-9.fc19 [eclipse] 1:eclipse-tests-4.3.0-0.30.fc20.x86_64 requires osgi(org.eclipse.releng.tools) [eruby] eruby-1.0.5-19.fc18.x86_64 requires libruby.so.1.9()(64bit) eruby-libs-1.0.5-19.fc18.i686 requires ruby(abi) = 0:1.9.0 eruby-libs-1.0.5-19.fc18.i686 requires libruby.so.1.9 eruby-libs-1.0.5-19.fc18.x86_64 requires ruby(abi) = 0:1.9.0 eruby-libs-1.0.5-19.fc18.x86_64 requires libruby.so.1.9()(64bit) [flowcanvas] flowcanvas-0.7.1-8.fc18.i686 requires libgraph.so.5 flowcanvas-0.7.1-8.fc18.x86_64 requires libgraph.so.5()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python2-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python3-debug-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python3-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 [gnome-applets] 1:gnome-applets-3.5.92-3.fc18.x86_64 requires libgweather-3.so.1()(64bit) [gnome-panel] gnome-panel-3.6.2-6.fc19.x86_64 requires libgnome-desktop-3.so.5()(64bit) gnome-panel-devel-3.6.2-6.fc19.i686 requires libgnome-desktop-3.so.5 gnome-panel-devel-3.6.2-6.fc19.x86_64 requires libgnome-desktop-3.so.5()(64bit) [gnome-pie] gnome-pie-0.5.3-3.20120826git1b93e1.fc19.x86_64 requires libbamf3.so.0()(64bit) [gnomint] gnomint-1.2.1-5.fc18.x86_64 requires libgnutls.so.26(GNUTLS_2_8)(64bit) gnomint-1.2.1-5.fc18.x86_64 requires libgnutls.so.26(GNUTLS_1_4)(64bit) gnomint-1.2.1-5.fc18.x86_64 requires libgnutls.so.26()(64bit) [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [kawa] 1:kawa-1.11-5.fc19.x86_64 requires servlet25 [kazehakase] kazehakase-webkit-0.5.8-15.svn3873_trunk.fc20.1.x86_64 requires webKitgtk = 0:1.1.1 [libkolab] php-kolab-0.4.1-3.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64 php-kolab-0.4.1-3.fc19.x86_64 requires php(api) = 0:20100412-x86-64 [mapserver] php-mapserver-6.0.3-9.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64 php-mapserver-6.0.3-9.fc19.x86_64 requires php(api) = 0:20100412-x86-64 [matreshka] matreshka-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-amf-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-amf-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-amf-mofext-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-amf-mofext-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-amf-ocl-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-amf-ocl-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-amf-uml-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-amf-uml-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-amf-utp-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-amf-utp-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-fastcgi-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-fastcgi-0.3.0-3.fc19.i686 requires libgnarl-4.7.so matreshka-fastcgi-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-fastcgi-0.3.0-3.fc19.x86_64 requires libgnarl-4.7.so()(64bit) matreshka-sql-core-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-sql-core-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-sql-postgresql-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-sql-postgresql-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-sql-sqlite-0.3.0-3.fc19.i686 requires libgnat-4.7.so
Re: Undeprecating libsidplay and fbg
On Mon, 08 Apr 2013 09:39:50 +0200, Hans de Goede wrote: If you worry just about GStreamer, I think it does a disservice to the community if it doesn't support any of the later and more capable SID music playing libs. Ok, you've got me convinced, I'll closing the review request and look into porting the gstreamer plugin ti sidplay v2. Or libsidplayfp which is active and has released 1.0 just recently: http://sourceforge.net/projects/sidplay-residfp/ -- Fedora release 19 (Schrödinger’s Cat) - Linux 3.9.0-0.rc5.git1.301.fc19.x86_64 loadavg: 0.39 0.37 0.36 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F-19 Branched report: 20130408 changes
Compose started at Mon Apr 8 09:15:19 UTC 2013 Broken deps for x86_64 -- [aeolus-conductor] aeolus-conductor-0.10.6-2.fc19.noarch requires ruby(abi) = 0:1.9.1 [alexandria] alexandria-0.6.9-4.fc19.noarch requires ruby(abi) = 0:1.9.1 [amide] amide-1.0.0-4.fc19.x86_64 requires libvolpack.so.1()(64bit) [clementine] clementine-1.1.1-1.fc19.x86_64 requires libprotobuf.so.7()(64bit) clementine-1.1.1-1.fc19.x86_64 requires libimobiledevice.so.3()(64bit) [connman] connman-1.5-4.fc19.i686 requires libxtables.so.7 connman-1.5-4.fc19.i686 requires libgnutls.so.26(GNUTLS_1_4) connman-1.5-4.fc19.i686 requires libgnutls.so.26 connman-1.5-4.fc19.x86_64 requires libxtables.so.7()(64bit) connman-1.5-4.fc19.x86_64 requires libgnutls.so.26(GNUTLS_1_4)(64bit) connman-1.5-4.fc19.x86_64 requires libgnutls.so.26()(64bit) [deltacloud-core] deltacloud-core-1.0.5-2.fc19.noarch requires ruby(abi) = 0:1.9.1 [denemo] denemo-0.9.4-0.fc18.x86_64 requires libgtksourceview-3.0.so.0()(64bit) [dragonegg] dragonegg-3.1-19.fc19.x86_64 requires gcc = 0:4.7.2-9.fc19 [eruby] eruby-1.0.5-19.fc18.x86_64 requires libruby.so.1.9()(64bit) eruby-libs-1.0.5-19.fc18.i686 requires ruby(abi) = 0:1.9.0 eruby-libs-1.0.5-19.fc18.i686 requires libruby.so.1.9 eruby-libs-1.0.5-19.fc18.x86_64 requires ruby(abi) = 0:1.9.0 eruby-libs-1.0.5-19.fc18.x86_64 requires libruby.so.1.9()(64bit) [fawkes] fawkes-firevision-0.5.0-5.fc19.i686 requires libjpeg.so.8(LIBJPEG_8.0) fawkes-firevision-0.5.0-5.fc19.i686 requires libjpeg.so.8 fawkes-firevision-0.5.0-5.fc19.x86_64 requires libjpeg.so.8(LIBJPEG_8.0)(64bit) fawkes-firevision-0.5.0-5.fc19.x86_64 requires libjpeg.so.8()(64bit) fawkes-guis-0.5.0-5.fc19.i686 requires libgraph.so.5 fawkes-guis-0.5.0-5.fc19.x86_64 requires libgraph.so.5()(64bit) fawkes-plugin-clips-0.5.0-5.fc19.i686 requires libclipsmm.so.2 fawkes-plugin-clips-0.5.0-5.fc19.x86_64 requires libclipsmm.so.2()(64bit) fawkes-plugin-player-0.5.0-5.fc19.x86_64 requires libgeos-3.3.6.so()(64bit) fawkes-plugin-player-0.5.0-5.fc19.x86_64 requires libboost_thread-mt.so.1.50.0()(64bit) fawkes-plugin-player-0.5.0-5.fc19.x86_64 requires libboost_system-mt.so.1.50.0()(64bit) fawkes-plugin-player-0.5.0-5.fc19.x86_64 requires libboost_signals-mt.so.1.50.0()(64bit) fawkes-plugin-tabletop-objects-0.5.0-5.fc19.x86_64 requires libboost_thread-mt.so.1.50.0()(64bit) fawkes-plugin-tabletop-objects-0.5.0-5.fc19.x86_64 requires libboost_system-mt.so.1.50.0()(64bit) [flowcanvas] flowcanvas-0.7.1-8.fc18.i686 requires libgraph.so.5 flowcanvas-0.7.1-8.fc18.x86_64 requires libgraph.so.5()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python2-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python3-debug-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 gcc-python3-plugin-0.11-1.fc19.x86_64 requires gcc = 0:4.7.2-8.fc19 [gdcm] gdcm-2.0.18-6.fc18.i686 requires libpoppler.so.26 gdcm-2.0.18-6.fc18.x86_64 requires libpoppler.so.26()(64bit) [gearbox] gearbox-10.11-3.fc19.i686 requires libIceUtil.so.35b gearbox-10.11-3.fc19.x86_64 requires libIceUtil.so.35b()(64bit) [gnome-applets] 1:gnome-applets-3.5.92-3.fc18.x86_64 requires libgweather-3.so.1()(64bit) [gnome-panel] gnome-panel-3.6.2-6.fc19.x86_64 requires libgnome-desktop-3.so.5()(64bit) gnome-panel-devel-3.6.2-6.fc19.i686 requires libgnome-desktop-3.so.5 gnome-panel-devel-3.6.2-6.fc19.x86_64 requires libgnome-desktop-3.so.5()(64bit) [gnome-pie] gnome-pie-0.5.3-3.20120826git1b93e1.fc19.x86_64 requires libbamf3.so.0()(64bit) [gnomint] gnomint-1.2.1-5.fc18.x86_64 requires libgnutls.so.26(GNUTLS_2_8)(64bit) gnomint-1.2.1-5.fc18.x86_64 requires libgnutls.so.26(GNUTLS_1_4)(64bit) gnomint-1.2.1-5.fc18.x86_64 requires libgnutls.so.26()(64bit) [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [gorm] gorm-1.2.18-1.fc19.i686 requires libgnustep-gui.so.0.22 gorm-1.2.18-1.fc19.x86_64 requires libgnustep-gui.so.0.22()(64bit) [kawa] 1:kawa-1.11-5.fc19.x86_64 requires servlet25 [libkolab] php-kolab-0.4.1-3.fc19.x86_64 requires php(zend-abi) = 0:20100525-x86-64 php-kolab-0.4.1-3.fc19.x86_64 requires php(api) = 0:20100412-x86-64 [matreshka] matreshka-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-amf-0.3.0-3.fc19.i686 requires libgnat-4.7.so matreshka-amf-0.3.0-3.fc19.x86_64 requires libgnat-4.7.so()(64bit) matreshka-amf-mofext-0.3.0-3.fc19.i686
dracut hostonly and cloud images
We're going to produce official Fedora Cloud images which should run on Amazon EC2, and various open source cloud infrastructure -- OpenStack, Eucalyptus, CloudStack, OpenNebula; with both KVM and Xen -- and probably also under VMware and VirtualBox. These images will be generated in Koji, not in the target systems. What's the best way to get the right stuff (and ideally only the right stuff) in the initramfs? -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: dracut hostonly and cloud images
Am 08.04.2013 15:05, schrieb Matthew Miller: We're going to produce official Fedora Cloud images which should run on Amazon EC2, and various open source cloud infrastructure -- OpenStack, Eucalyptus, CloudStack, OpenNebula; with both KVM and Xen -- and probably also under VMware and VirtualBox. These images will be generated in Koji, not in the target systems. What's the best way to get the right stuff (and ideally only the right stuff) in the initramfs? Depends on what the dracut image should be able to boot. LVM, crypto, MD raids? Which filesystems? # dracut test.img \ --drivers 'ext4' \ --filesystems 'ext4' \ --fscks 'ext4' \ --add qemu \ --omit network \ --omit mdraid \ --omit dmraid \ --omit plymouth \ --omit drm \ --omit btrfs \ --omit biosdevname \ --omit caps \ --omit resume \ --omit crypt \ --omit i18n \ --omit terminfo \ --omit multipath \ --no-hostonly This will build the initramfs test.img without network, MD-raid, DM-raid, plymouth, gfx drivers, without general purpose HW block drivers, without resume, biosdevname, btrfs, caps, crypt, i18n, terminfo but with the ext4 filesystem support, LVM, multipath and qemu block kernel drivers. $ ls -lh test.img -rw--- 1 harald harald 6,9M 8. Apr 16:05 test.img to see, which dracut modules have been used: $ lsinitrd test.img usr/lib/dracut/modules.txt dm kernel-modules lvm multipath qemu rootfs-block udev-rules systemd usrmount base fs-lib shutdown So, instead, you could also call dracut with: # dracut test.img \ --drivers 'ext4' \ --filesystems 'ext4' \ --fscks 'ext4' \ --modules dm kernel-modules lvm multipath qemu rootfs-block udev-rules systemd usrmount base fs-lib shutdown To see, which kernel drivers are in the initramfs: # lsinitrd test.img | grep /lib/modules To add a kernel driver, add it to the --drivers list. Let me know, if you need more info. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: MySQL and MariaDB in Fedora
On 04/08/2013 07:38 AM, Honza Horak wrote: However, I'd rather wait with 5.6 until F20 because of the following reasons: * we are almost a month after feature freeze Yes thanks to how you have handled this * I believe users will have enough concerns with switching to MariaDB and MySQL-5.6 would bring others Users should not be switched automatically to Mariadb on upgrades * better wait a bit longer to stabilize the new release than bring a quite important package too soon like we do with the rest of the components in the distribution. shrug JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Explicit versioning of library names [was Re: package, package2, package3 naming-with-version exploit]
On Mon, Apr 08, 2013 at 12:28:01PM +0200, Vít Ondruch wrote: Dne 5.4.2013 22:03, Toshio Kuratomi napsal(a): On Fri, Apr 05, 2013 at 10:53:53AM +0200, Vít Ondruch wrote: Dne 4.4.2013 20:07, Toshio Kuratomi napsal(a): There is also an unwritten (I think it's unwritten. A quick search didn't find it in the guidelines) rule that in Fedora, the current version of the library carries the base name. Older libraries carry the version in the name. Interesting ... it seems time is changing. I made several attempts to make this unwritten rule to be written, the last wrap up and my latest proposal can be found here: http://lists.fedoraproject.org/pipermail/packaging/2012-October/008740.html Your proposals keep failing because they run contrary to the unwritten rules rather than canonifying them. May be I missing something, but what is different in Always consider to let a nonversioned package to follow an upstream release versions. The other versions of package kept in Fedora for compatibility reasons should be either prefixed by compat- prefix or their name should be suffixed by version string. contrary to the current version of the library carries the base name. Older libraries carry the version in the name. Your usage of compat- is contrary to the unwritten rule. -Toshio pgpc9W1IQ8qh9.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: dracut hostonly and cloud images
On Mon, Apr 8, 2013 at 9:05 AM, Matthew Miller mat...@fedoraproject.org wrote: We're going to produce official Fedora Cloud images which should run on Amazon EC2, and various open source cloud infrastructure -- OpenStack, Eucalyptus, CloudStack, OpenNebula; with both KVM and Xen -- and probably also under VMware and VirtualBox. Can you elaborate on those last two? Are you intending to generate images explicitly for VMWare and VirtualBox, or do you expect the cloud images to just run there? If the former... please explain further. In both cases, is there a reason you're excluding Hyper-V? josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] Fedora 19 Alpha Go/No-Go Meeting, Thursday, April 11 @ 17:00 UTC
Join us on irc.freenode.net in #fedora-meeting-1 for this important meeting, wherein we shall determine the readiness of the Fedora 19 Alpha. Thursday, April 11, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST) Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting. Verifying that the Release criteria are met is the responsibility of the QA Team. For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 19 Alpha Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/19/alpha/buglist Reminder: the Readiness meeting follows the Go/No-Go meeting two hours later. Jaroslav ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Explicit versioning of library names [was Re: package, package2, package3 naming-with-version exploit]
Dne 8.4.2013 17:05, Toshio Kuratomi napsal(a): On Mon, Apr 08, 2013 at 12:28:01PM +0200, Vít Ondruch wrote: Dne 5.4.2013 22:03, Toshio Kuratomi napsal(a): On Fri, Apr 05, 2013 at 10:53:53AM +0200, Vít Ondruch wrote: Dne 4.4.2013 20:07, Toshio Kuratomi napsal(a): There is also an unwritten (I think it's unwritten. A quick search didn't find it in the guidelines) rule that in Fedora, the current version of the library carries the base name. Older libraries carry the version in the name. Interesting ... it seems time is changing. I made several attempts to make this unwritten rule to be written, the last wrap up and my latest proposal can be found here: http://lists.fedoraproject.org/pipermail/packaging/2012-October/008740.html Your proposals keep failing because they run contrary to the unwritten rules rather than canonifying them. May be I missing something, but what is different in Always consider to let a nonversioned package to follow an upstream release versions. The other versions of package kept in Fedora for compatibility reasons should be either prefixed by compat- prefix or their name should be suffixed by version string. contrary to the current version of the library carries the base name. Older libraries carry the version in the name. Your usage of compat- is contrary to the unwritten rule. Would you mind to explain yourself a bit more please? Ah, ok, so let me quote you [1]: compat-foo is not for packages in Fedora. It is the shared libraries that are necessary for thirdparty packages to run with the old versions of the libraries. However, there are probably exception in the same sense as my proposal. That is perfectly fine for me. So compat- is probably not a good idea. If you say that, we could have already updated revision of the draft. Vít [1] http://lists.fedoraproject.org/pipermail/packaging/2009-August/006431.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: dracut hostonly and cloud images
On Mon, Apr 08, 2013 at 04:08:19PM +0200, Harald Hoyer wrote: Depends on what the dracut image should be able to boot. LVM, crypto, MD raids? I'm fine with none of those by default, assuming it's relatively easy to put it back if someone has different needs. Which filesystems? ext4. [...snip...] This will build the initramfs test.img without network, MD-raid, DM-raid, plymouth, gfx drivers, without general purpose HW block drivers, without resume, biosdevname, btrfs, caps, crypt, i18n, terminfo but with the ext4 filesystem support, LVM, multipath and qemu block kernel drivers. Cool, thanks. Is the best approach to generate a dracut.conf in the kickstart file? Or should it be packaged up in some way? -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: dracut hostonly and cloud images
Am 08.04.2013 17:59, schrieb Matthew Miller: On Mon, Apr 08, 2013 at 04:08:19PM +0200, Harald Hoyer wrote: Depends on what the dracut image should be able to boot. LVM, crypto, MD raids? I'm fine with none of those by default, assuming it's relatively easy to put it back if someone has different needs. Which filesystems? ext4. [...snip...] This will build the initramfs test.img without network, MD-raid, DM-raid, plymouth, gfx drivers, without general purpose HW block drivers, without resume, biosdevname, btrfs, caps, crypt, i18n, terminfo but with the ext4 filesystem support, LVM, multipath and qemu block kernel drivers. Cool, thanks. Is the best approach to generate a dracut.conf in the kickstart file? Or should it be packaged up in some way? Don't know and don't know how the images are generated in detail anyway. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: dracut hostonly and cloud images
On Mon, Apr 08, 2013 at 11:08:03AM -0400, Josh Boyer wrote: We're going to produce official Fedora Cloud images which should run on Amazon EC2, and various open source cloud infrastructure -- OpenStack, Eucalyptus, CloudStack, OpenNebula; with both KVM and Xen -- and probably also under VMware and VirtualBox. Can you elaborate on those last two? Are you intending to generate images explicitly for VMWare and VirtualBox, or do you expect the cloud images to just run there? If the former... please explain further. The latter, definitely. And of those two, with priority to VirtualBox because it's a) open source (extensions notwithstanding) and b) heavily used on Mac laptops where Fedora is a common guest. (The cloud images isn't intended to be a generic guest image, but it's handy if it happens to work.) In both cases, is there a reason you're excluding Hyper-V? No, no particular reason; I just left it out of the list. I can't really test it myself, and the same lower-priority-since-it's-not-open applies. And in all cases we're certainly (and obviosuly I hope) not packaging up guest driver / toolkit software that isn't free software. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: dracut hostonly and cloud images
On Mon, Apr 08, 2013 at 06:04:52PM +0200, Harald Hoyer wrote: Cool, thanks. Is the best approach to generate a dracut.conf in the kickstart file? Or should it be packaged up in some way? Don't know and don't know how the images are generated in detail anyway. They're currently generated by running appliance-creator, which installs packages to a chroot and mimicks anaconda; in the future, they'll be created by running anaconda inside a VM (with oz, although it's fundamentally similar to doing it with livemedia-creator). This will be KVM in Fedora infrastructure, but the target environments are a little wider than that. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Weird broken deps.
Hello all, Can anyone help me make sense of the following broken-dep message? springlobby has broken dependencies in the rawhide tree: On i386: springlobby-0.169-2.fc20.i686 requires bdb835272157f37cbb0067c02ab4fc437596ed.debug springlobby-0.169-2.fc20.i686 requires 508df0cdc1c9e84cded295738bec13842f070d.debug Please resolve this as soon as possible. ?!?! - Gilboa -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Weird broken deps.
On Mon, 8 Apr 2013 19:51:15 +0300, Gilboa Davara wrote:
Hello all,
Can anyone help me make sense of the following broken-dep message?
springlobby has broken dependencies in the rawhide tree:
On i386:
springlobby-0.169-2.fc20.i686 requires
bdb835272157f37cbb0067c02ab4fc437596ed.debug
springlobby-0.169-2.fc20.i686 requires
508df0cdc1c9e84cded295738bec13842f070d.debug
Please resolve this as soon as possible.
?!?!
- Gilboa
On platforms where %_libdir is /usr/lib, don't include
%{_libdir}/*
in the %files section, because it will include the -debuginfo package
files. Be more specific about which files you want to include in your
package.
--
Fedora release 19 (Schrödinger’s Cat) - Linux 3.9.0-0.rc5.git1.301.fc19.x86_64
loadavg: 0.25 0.40 0.43
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: dracut hostonly and cloud images
On Mon, Apr 8, 2013 at 12:06 PM, Matthew Miller mat...@fedoraproject.org wrote: On Mon, Apr 08, 2013 at 11:08:03AM -0400, Josh Boyer wrote: We're going to produce official Fedora Cloud images which should run on Amazon EC2, and various open source cloud infrastructure -- OpenStack, Eucalyptus, CloudStack, OpenNebula; with both KVM and Xen -- and probably also under VMware and VirtualBox. Can you elaborate on those last two? Are you intending to generate images explicitly for VMWare and VirtualBox, or do you expect the cloud images to just run there? If the former... please explain further. The latter, definitely. And of those two, with priority to VirtualBox because it's a) open source (extensions notwithstanding) and b) heavily used on Mac laptops where Fedora is a common guest. (The cloud images isn't intended to be a generic guest image, but it's handy if it happens to work.) VirtualBox might be open source, but it is consistently broken. The VMWare hypervisor is closed source, but they actually got most of their kernel drivers upstream now (with the major exception of the hostfs one). We build and ship those drivers in the Fedora kernel. I'm not pretending that vbox isn't the more popular of the two, but from a kernel support standpoint it is certainly worse. We simply don't look at anything reported in VirtualBox unless it can be recreated in KVM or on real hardware. Mostly just an FYI. In both cases, is there a reason you're excluding Hyper-V? No, no particular reason; I just left it out of the list. I can't really test it myself, and the same lower-priority-since-it's-not-open applies. And in all cases we're certainly (and obviosuly I hope) not packaging up guest driver / toolkit software that isn't free software. Like VMWare, most of the hyperv kernel drivers are in the upstream kernel now. We also ship those in the Fedora kernel. Though of the three, I'd certainly agree it's the lowest on the list and none of the kernel team has an environment to actually test anything. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-ExtUtils-Config] Created tag perl-ExtUtils-Config-0.007-2.el5
The lightweight tag 'perl-ExtUtils-Config-0.007-2.el5' was created pointing to: 6eec1d0... Initial import (perl-ExtUtils-Config-0.007-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Config] Created tag perl-ExtUtils-Config-0.007-2.el6
The lightweight tag 'perl-ExtUtils-Config-0.007-2.el6' was created pointing to: 6eec1d0... Initial import (perl-ExtUtils-Config-0.007-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: dracut hostonly and cloud images
Am 08.04.2013 18:08, schrieb Matthew Miller: On Mon, Apr 08, 2013 at 06:04:52PM +0200, Harald Hoyer wrote: Cool, thanks. Is the best approach to generate a dracut.conf in the kickstart file? Or should it be packaged up in some way? Don't know and don't know how the images are generated in detail anyway. They're currently generated by running appliance-creator, which installs packages to a chroot and mimicks anaconda; in the future, they'll be created by running anaconda inside a VM (with oz, although it's fundamentally similar to doing it with livemedia-creator). This will be KVM in Fedora infrastructure, but the target environments are a little wider than that. Might be worth a /usr/lib/dracut/dracut.conf.d/90-name.conf in an rpm package with requirements and such. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
python-fedora minimum python version
Greetings all, Fedora Infrastructure develops a python module called python-fedora which can be used to connect to the web services that we run (Bodhi, packagedb, etc). This is used by fedpkg, pkgdb-cli, and a variety of ad hoc scripts that people are running on their systems. As the developers of this software, we would like to move to supporting python-2.6 and higher. Among other things, this will let us start considering a move to python3. python-2.6 is available in RHEL6 and python-2.7 is available in all current Fedora releases. However, RHEL5 has python-2.4. If we move to python-2.6 the version of python-fedora in EPEL5 will slowly lose functionality as its code is not updated while the web applications that the library talks to gain and remove features and change their API. The question that we have as the developers of python-fedora is whether this will be a problem for anyone. If the users of this library have moved on to RHEL6 and current Fedora, then we're fine with allowing the version in EPEL to slowly bit-rot; backporting only security fixes. However, if people are actively running code that depends on python-fedora working on RHEL5 then it's probably better for us to maintain python-2.4 compatibility, at least for the time being. So if you use this directly or run fedpkg or other scripts which require it on RHEL5 please speak up and let me know that we need to continue targeting python-2.4. If you send replies to this list, I'll see that the information is passed back to the infrastructure list and team. (And note, eventually we will have to move to a newer python version. If we choose to stay with python-2.4 now we'll reevaluate periodically to figure out when the time has come to move forward.) Thanks, Toshio pgpVHb_QWRYn9.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: python-fedora minimum python version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/08/2013 02:58 PM, Toshio Kuratomi wrote: Greetings all, Fedora Infrastructure develops a python module called python-fedora which can be used to connect to the web services that we run (Bodhi, packagedb, etc). This is used by fedpkg, pkgdb-cli, and a variety of ad hoc scripts that people are running on their systems. As the developers of this software, we would like to move to supporting python-2.6 and higher. Among other things, this will let us start considering a move to python3. python-2.6 is available in RHEL6 and python-2.7 is available in all current Fedora releases. However, RHEL5 has python-2.4. If we move to python-2.6 the version of python-fedora in EPEL5 will slowly lose functionality as its code is not updated while the web applications that the library talks to gain and remove features and change their API. The question that we have as the developers of python-fedora is whether this will be a problem for anyone. If the users of this library have moved on to RHEL6 and current Fedora, then we're fine with allowing the version in EPEL to slowly bit-rot; backporting only security fixes. However, if people are actively running code that depends on python-fedora working on RHEL5 then it's probably better for us to maintain python-2.4 compatibility, at least for the time being. So if you use this directly or run fedpkg or other scripts which require it on RHEL5 please speak up and let me know that we need to continue targeting python-2.4. If you send replies to this list, I'll see that the information is passed back to the infrastructure list and team. (And note, eventually we will have to move to a newer python version. If we choose to stay with python-2.4 now we'll reevaluate periodically to figure out when the time has come to move forward.) Thanks, Toshio This may seem like an obvious question, but why not simply have python-fedora Requires: python26 from EPEL? Wouldn't this avoid the issue entirely? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFjFC0ACgkQeiVVYja6o6NhoQCfSiyDqYjtXs9RN1YJfSXq4OAy j5oAnivOaRb5dXmtOvxy2V9rmpnOoYEv =rrsp -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File Image-ExifTool-9.25.tar.gz uploaded to lookaside cache by spot
A file has been added to the lookaside cache for perl-Image-ExifTool: c6071d197e5b5ccb7abc027fde0eb647 Image-ExifTool-9.25.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Image-ExifTool/f17] 9.25
commit 868e19e9e0a722d751caddbb592033a5cc885a86
Author: Tom Callaway s...@fedoraproject.org
Date: Mon Apr 8 15:07:54 2013 -0400
9.25
perl-Image-ExifTool.spec |8 +++-
sources |2 +-
2 files changed, 8 insertions(+), 2 deletions(-)
---
diff --git a/perl-Image-ExifTool.spec b/perl-Image-ExifTool.spec
index 3e7c82c..ec7f6d5 100644
--- a/perl-Image-ExifTool.spec
+++ b/perl-Image-ExifTool.spec
@@ -1,5 +1,5 @@
Name: perl-Image-ExifTool
-Version: 9.13
+Version: 9.25
Release: 1%{?dist}
License: GPL+ or Artistic
Group: Applications/Multimedia
@@ -51,6 +51,12 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Mon Apr 8 2013 Tom Callaway s...@fedoraproject.org - 9.25-1
+- update to 9.25 (stable)
+
+* Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 9.13-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
+
* Fri Jan 18 2013 Tom Callaway s...@fedoraproject.org - 9.13-1
- update to 9.13 (stable)
diff --git a/sources b/sources
index 5a08c8f..fc49aeb 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-35fc77415a0ef0d5f6477db3cc3b4f7d Image-ExifTool-9.13.tar.gz
+c6071d197e5b5ccb7abc027fde0eb647 Image-ExifTool-9.25.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Image-ExifTool/f18] 9.25
commit 6291ab461c61a5003e7ae1efa5ee17ddb4569143
Author: Tom Callaway s...@fedoraproject.org
Date: Mon Apr 8 15:08:07 2013 -0400
9.25
perl-Image-ExifTool.spec |8 +++-
sources |2 +-
2 files changed, 8 insertions(+), 2 deletions(-)
---
diff --git a/perl-Image-ExifTool.spec b/perl-Image-ExifTool.spec
index 3e7c82c..ec7f6d5 100644
--- a/perl-Image-ExifTool.spec
+++ b/perl-Image-ExifTool.spec
@@ -1,5 +1,5 @@
Name: perl-Image-ExifTool
-Version: 9.13
+Version: 9.25
Release: 1%{?dist}
License: GPL+ or Artistic
Group: Applications/Multimedia
@@ -51,6 +51,12 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Mon Apr 8 2013 Tom Callaway s...@fedoraproject.org - 9.25-1
+- update to 9.25 (stable)
+
+* Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 9.13-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
+
* Fri Jan 18 2013 Tom Callaway s...@fedoraproject.org - 9.13-1
- update to 9.13 (stable)
diff --git a/sources b/sources
index 5a08c8f..fc49aeb 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-35fc77415a0ef0d5f6477db3cc3b4f7d Image-ExifTool-9.13.tar.gz
+c6071d197e5b5ccb7abc027fde0eb647 Image-ExifTool-9.25.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Image-ExifTool/f19] 9.25
commit 4542b3db0987409a0be0d90f3f35bad7b9f7140b
Author: Tom Callaway s...@fedoraproject.org
Date: Mon Apr 8 15:08:19 2013 -0400
9.25
perl-Image-ExifTool.spec |7 +--
sources |2 +-
2 files changed, 6 insertions(+), 3 deletions(-)
---
diff --git a/perl-Image-ExifTool.spec b/perl-Image-ExifTool.spec
index ba3a99d..ec7f6d5 100644
--- a/perl-Image-ExifTool.spec
+++ b/perl-Image-ExifTool.spec
@@ -1,6 +1,6 @@
Name: perl-Image-ExifTool
-Version: 9.13
-Release: 2%{?dist}
+Version: 9.25
+Release: 1%{?dist}
License: GPL+ or Artistic
Group: Applications/Multimedia
Summary: Utility for reading and writing image meta info
@@ -51,6 +51,9 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Mon Apr 8 2013 Tom Callaway s...@fedoraproject.org - 9.25-1
+- update to 9.25 (stable)
+
* Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 9.13-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
diff --git a/sources b/sources
index 5a08c8f..fc49aeb 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-35fc77415a0ef0d5f6477db3cc3b4f7d Image-ExifTool-9.13.tar.gz
+c6071d197e5b5ccb7abc027fde0eb647 Image-ExifTool-9.25.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Image-ExifTool] 9.25
commit 4783a6ac81b8e81e07801d4b08eb063e96ab76a2
Author: Tom Callaway s...@fedoraproject.org
Date: Mon Apr 8 15:08:31 2013 -0400
9.25
.gitignore |1 +
perl-Image-ExifTool.spec |7 +--
sources |2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 9cb2829..8c95a44 100644
--- a/.gitignore
+++ b/.gitignore
@@ -11,3 +11,4 @@ Image-ExifTool-8.25.tar.gz
/Image-ExifTool-9.04.tar.gz
/Image-ExifTool-9.12.tar.gz
/Image-ExifTool-9.13.tar.gz
+/Image-ExifTool-9.25.tar.gz
diff --git a/perl-Image-ExifTool.spec b/perl-Image-ExifTool.spec
index ba3a99d..ec7f6d5 100644
--- a/perl-Image-ExifTool.spec
+++ b/perl-Image-ExifTool.spec
@@ -1,6 +1,6 @@
Name: perl-Image-ExifTool
-Version: 9.13
-Release: 2%{?dist}
+Version: 9.25
+Release: 1%{?dist}
License: GPL+ or Artistic
Group: Applications/Multimedia
Summary: Utility for reading and writing image meta info
@@ -51,6 +51,9 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Mon Apr 8 2013 Tom Callaway s...@fedoraproject.org - 9.25-1
+- update to 9.25 (stable)
+
* Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 9.13-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
diff --git a/sources b/sources
index 5a08c8f..fc49aeb 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-35fc77415a0ef0d5f6477db3cc3b4f7d Image-ExifTool-9.13.tar.gz
+c6071d197e5b5ccb7abc027fde0eb647 Image-ExifTool-9.25.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Undeprecating libsidplay and fbg
On 04/06/2013 10:54 AM, Hans de Goede wrote: fbg, review request: 949167 - Review Request: fbg - Falling Block Game https://bugzilla.redhat.com/show_bug.cgi?id=949167 Rationale for undeprecating: I'm the original packager of fbg and handed it over to lower my package load, only to later found out it got orphaned (and I missed this), so now I want to get it back into Fedora, as this is still a nice and simple game. I'm assuming you saw later why I deprecated it, there are legal issues with the use of a sound trademark in that game, and the format for the music file in question was... archaic. There is a sequel to fbg called fbg2, and I was able to resolve the music issue in that version. ~tom == Fedora Project -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: what is initramfs-0-rescue in F19?
On Sun, Apr 07, 2013 at 03:06:51PM +0200, Harald Hoyer wrote: install dracut-nohostonly if you don't want that... see the Release Notes of http://fedoraproject.org/wiki/Features/DracutHostOnly I removed my initramfs-0-rescue-* file because I didn't know what it was and no rpm claimed to own it. How do I get it back? I've tried running dracut with various options and it doesn't regenerate the image. Jeff -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: python-fedora minimum python version
On Mon, Apr 08, 2013 at 03:02:05PM -0400, Stephen Gallagher wrote: This may seem like an obvious question, but why not simply have python-fedora Requires: python26 from EPEL? Wouldn't this avoid the issue entirely? I considered that but someone would have to be responsible for the stack of python26 packages that python-fedora depended upon. Quite a ballooning of effort. It also may not help people who are depending on python-fedora if their scripts have not been ported to python-2.6 and python-fedora is python-2.6 only. For instance, this would push the fedpkg maintainers in EPEL5 to make a similar choice to rebase their application against pyhton2.6 and maintain the stack of packages they require on the python2.6 base. -Toshio pgpyOdodWoLV0.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Undeprecating libsidplay and fbg
Hi, On 04/08/2013 11:04 PM, Tom Callaway wrote: On 04/06/2013 10:54 AM, Hans de Goede wrote: fbg, review request: 949167 - Review Request: fbg - Falling Block Game https://bugzilla.redhat.com/show_bug.cgi?id=949167 Rationale for undeprecating: I'm the original packager of fbg and handed it over to lower my package load, only to later found out it got orphaned (and I missed this), so now I want to get it back into Fedora, as this is still a nice and simple game. I'm assuming you saw later why I deprecated it, there are legal issues with the use of a sound trademark in that game, and the format for the music file in question was... archaic. There is a sequel to fbg called fbg2, and I was able to resolve the music issue in that version. Yes, I've already closed the review ticket and I've made fbg2 obsolete fbg for F-19+ Regards, Hans -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: what is initramfs-0-rescue in F19?
On Mon, Apr 08, 2013 at 04:03:47PM -0500, Jeffrey Bastian wrote:
I removed my initramfs-0-rescue-* file because I didn't know what it was
and no rpm claimed to own it. How do I get it back? I've tried running
dracut with various options and it doesn't regenerate the image.
Attempting to answer my own question... I'm not sure if this is the
correct way, but I tried running this:
/etc/kernel/postinst.d/51-dracut-rescue-postinst.sh $(uname -r) \
/boot/initramfs-$(uname -r)*
And now I have rescue files again:
# ls -latr /boot/*0-rescue*
-rw---. 1 root root 27496022 Apr 8 16:46 /boot/initramfs-0-rescue-...img
-rw---. 1 root root 7860871 Apr 8 16:46 /boot/vmlinuz-0-rescue-...
Is dracut supposed to run the /etc/kernel/postinst.d/* scripts
automatically? I ran dracut through 'bash -x' and strace and it didn't
appear to even look in /etc/kernel/postinst.d
The reason I removed the file in the first place is because grub2-mkconfig
generates a not-very-descriptive entry in the menu. My grub.cfg now has this:
menuentry 'Fedora, with Linux 0-rescue-344...c20' ... {
Furthermore, my system is set up to dual boot between Fedora 17 and 19
Alpha, and now grub2-mkconfig has set this rescue image as the default
kernel for F17.
menuentry 'Fedora release 17 (Beefy Miracle)' ... {
...
linux /vmlinuz-0-rescue-344...
}
That seems a little strange to me.
Jeff
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] Fedora 19 Alpha Release Candidate 1 (RC1) Available Now!
*IMPORTANT*: Same images as with 19 Alpha TC3, TC4, and TC5 are over their size targets (all DVDs and Lives with the exception of Live KDE and Live SoaS). As per the Fedora 19 schedule [1], Fedora 19 Alpha Release Candidate 1 (RC1) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5545#comment:15 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace dl with download-ib01 in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha priority test cases for Installation [2], Base [3], and Desktop [4] should pass in order to meet the Alpha Release Criteria [5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the test list [7]. Create Fedora 19 Alpha test composes (TC) and release candidates (RC) https://fedorahosted.org/rel-eng/ticket/5545 Current Blocker and NTH bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-19/f-19-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Base_validation_testing [4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [5] https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria [6] irc://irc.freenode.net/fedora-qa [7] https://admin.fedoraproject.org/mailman/listinfo/test signature.asc Description: OpenPGP digital signature ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: package, package2, package3 naming-with-version exploit
On Mon, Apr 8, 2013 at 6:45 AM, David Tardon dtar...@redhat.com wrote: On Sun, Apr 07, 2013 at 07:11:44AM -0400, Nico Kadel-Garcia wrote: Why was Java 1.4 succeeded by Java 5? Why was ICU 4.8.1 succeeded by ICU 49.1? Why does systemd have version 197 instead of 1.9.7 or somesuch? If you look at the source code and the package names, Java wasn't really renumbered that badly, Java 1.4 was succeeded by Java 1.5, and Java 1.5 by Java 1.6. They're just marketed misleadingly. Sun's desicsion to screw up numbering this way is a reflection of when they tried to SunOS 4 as Solaris 2.5. You are totally missing the point. What I tried to convey is that expectation that every upstream adheres to your favourite versioning scheme is not based on reality. You cannot base an argument on it, because the premise is already invalid. (Did I already say that in the part that you removed?) No, I'm trying to point out that if you actually look at the source code, the numbering is not that awful. It's when you try to number things based on marketing that confusion arises,and Sun was a major contributor to this problem. And yes, there actually _are_ projects that use the usual X.Y.Z versioning scheme, but _did not_ start with version 1.0.0. What comes immediately to my mind is libreoffice (the first release was 3.3.0) or libexttextcat (the first release was 3.2.0). That's because it was a fork from another software package that was already at major version 3.x. And you don't have to backfill release numbers for completeness. Just stick with the GNU spec of x.y.z, x for major new releases, x.y for releases that add new features but will still run the older x release features, and x.y.z for minor releases that are compatible among all x.y numbers. And don't *get* me going on mod_perl numbering or CPAN version numbering. (Whose bright idea was it to use floating point? Version 2.237 is older than version 2.3 ?) Another point for my case. If your point were that some people deliberately ignored sensible and published standards and left the rest of the world to suck it up and deal, then yes. But it's the exception, rather than the rule, if you actually check the source code bundles. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 19 Alpha status: blockers, karma requests etc
Hi folks! Time for the first blocker status mail of the Fedora 19 cycle. The tl;dr summary: Karma needed for: * https://admin.fedoraproject.org/updates/FEDORA-2013-5141/systemd-201-1.fc19,initial-setup-0.3.4-3.fc19 * https://admin.fedoraproject.org/updates/FEDORA-2013-5027/libreport-2.1.3-2.fc19 Input needed from blocker voters and developers on: * https://bugzilla.redhat.com/show_bug.cgi?id=947142 QA folks, we need to complete the validation tests for RC1: https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Install https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Base Longer version follows. I'm touching every wooden object in sight right now, but things are actually looking quite good for the Alpha. There are only two open accepted blocker bugs: https://bugzilla.redhat.com/show_bug.cgi?id=929403 https://bugzilla.redhat.com/show_bug.cgi?id=926916 and both are in VERIFIED state, indicating that they have been confirmed fixed in Alpha RC1, but the updates need karma to be pushed stable to close the bugs. So if folks could provide karma on these updates: https://admin.fedoraproject.org/updates/FEDORA-2013-5141/systemd-201-1.fc19,initial-setup-0.3.4-3.fc19 https://admin.fedoraproject.org/updates/FEDORA-2013-5027/libreport-2.1.3-2.fc19 it would be very helpful. Both are relatively easy to test. For the systemd/initial-setup update, simply install Alpha RC1 and confirm that the initial-setup tool runs at first boot. It looks a lot like anaconda and lets you create a user account and set the root password if you did not already do so. The facts that it offers user account creation even if you already did it in anaconda, and that both it and gnome-initial-setup run on GNOME installs, are both known; they are bugs, but do not block the Alpha release. For the libreport update, check that, if anaconda crashes, you can file a bug on the crash by following the steps. In previous Alpha composes, this didn't work. If you can't make anaconda crash, there are instructions for faking a crash in the test case: https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla . We currently have only one proposed blocker bug: https://bugzilla.redhat.com/show_bug.cgi?id=947142 input on that from blocker voters and relevant developers would be very helpful. It is quite hard to decide on the blocker status of the bug without some kind of information on how many UEFI systems it is likely to affect. Of course, the sooner a fix or workaround can be devised, the better. Aside from the above, we need to complete the Alpha level validation tests: https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Install https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_19_Alpha_RC1_Base We already covered quite a lot of the ground with previous builds, but we need to make sure to check everything and catch any other lurking blockers. Thanks everyone, and let's hope we can get the Alpha out on time for once! Go/no-go is on Thursday, so we need to have a build fully tested without blockers by then. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Self Introduction
Hi all, I work for VMware. My Fedora account name is ravindrakumar. I would like to contribute open-vm-tools package to ongoing development of Fedora 19. For more details about open-vm-tools project, please refer http://open-vm-tools.sourceforge.net/. My review request for this contribution can be tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=905255#c6 This is going to be my first contribution to Fedora, so I need a sponsor for my contribution. I would really appreciate if someone could review my work and sponsor me. Thanks, Ravindra -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-App-cpanminus] 1.6105 bump
commit 52507cddd5951f6fbe112d313391822d3725acab
Author: Petr Písař ppi...@redhat.com
Date: Mon Apr 8 08:53:48 2013 +0200
1.6105 bump
.gitignore |1 +
perl-App-cpanminus.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 08e796c..8a6d014 100644
--- a/.gitignore
+++ b/.gitignore
@@ -42,3 +42,4 @@ App-cpanminus-0.9935.tar.gz
/App-cpanminus-1.6101.tar.gz
/App-cpanminus-1.6102.tar.gz
/App-cpanminus-1.6104.tar.gz
+/App-cpanminus-1.6105.tar.gz
diff --git a/perl-App-cpanminus.spec b/perl-App-cpanminus.spec
index 460e89f..b8cf5f8 100644
--- a/perl-App-cpanminus.spec
+++ b/perl-App-cpanminus.spec
@@ -1,5 +1,5 @@
Name: perl-App-cpanminus
-Version:1.6104
+Version:1.6105
Release:1%{?dist}
Summary:Get, unpack, build and install CPAN modules
License:GPL+ or Artistic
@@ -94,6 +94,9 @@ make test
%{_bindir}/cpanm
%changelog
+* Mon Apr 08 2013 Petr Pisar ppi...@redhat.com - 1.6105-1
+- 1.6105 bump
+
* Wed Apr 03 2013 Petr Pisar ppi...@redhat.com - 1.6104-1
- 1.6104 bump
diff --git a/sources b/sources
index 5e68d6d..5c337bd 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-608f08cc790e3f64daa7ded6577a5ad2 App-cpanminus-1.6104.tar.gz
+8c17979d4e8c9ac2ad3b26e823369d55 App-cpanminus-1.6105.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 949145] perl-App-cpanminus-1.6105 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=949145 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-App-cpanminus-1.6105-1 ||.fc20 Resolution|--- |RAWHIDE Last Closed||2013-04-08 03:04:29 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=S1HepZ46Lca=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 949147] perl-Compress-Bzip2-2.15 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=949147 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC|mmasl...@redhat.com,| |ppi...@redhat.com | Assignee|mmasl...@redhat.com |ppi...@redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=YJJCziWqAba=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File Compress-Bzip2-2.15.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Compress-Bzip2: f1cc338445e60dfd22f5a3a302fc22ca Compress-Bzip2-2.15.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Compress-Bzip2] 2.15 bump
commit 57f4a7b49eb8b76498379fdceebce4bce02dc96b
Author: Petr Písař ppi...@redhat.com
Date: Mon Apr 8 09:14:53 2013 +0200
2.15 bump
.gitignore |1 +
perl-Compress-Bzip2.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index f883b44..c9c9f56 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
Compress-Bzip2-2.09.tar.gz
/Compress-Bzip2-2.10.tar.gz
/Compress-Bzip2-2.13.tar.gz
+/Compress-Bzip2-2.15.tar.gz
diff --git a/perl-Compress-Bzip2.spec b/perl-Compress-Bzip2.spec
index 7e64743..dde1949 100644
--- a/perl-Compress-Bzip2.spec
+++ b/perl-Compress-Bzip2.spec
@@ -1,5 +1,5 @@
Name: perl-Compress-Bzip2
-Version:2.13
+Version:2.15
Release:1%{?dist}
Summary:Interface to Bzip2 compression library
Group: Development/Libraries
@@ -63,6 +63,9 @@ make test
%{_mandir}/man3/*.3pm*
%changelog
+* Mon Apr 08 2013 Petr Pisar ppi...@redhat.com - 2.15-1
+- 2.15 bump
+
* Thu Apr 04 2013 Petr Pisar ppi...@redhat.com - 2.13-1
- 2.13 bump
diff --git a/sources b/sources
index 8708e3a..09d5681 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-525bddd0edcfa3ba016016b189e919a6 Compress-Bzip2-2.13.tar.gz
+f1cc338445e60dfd22f5a3a302fc22ca Compress-Bzip2-2.15.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 949458] New: perl-App-cpanminus-1.6107 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=949458 Bug ID: 949458 Summary: perl-App-cpanminus-1.6107 is available Product: Fedora Version: rawhide Component: perl-App-cpanminus Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Assignee: mmasl...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org Category: --- Latest upstream release: 1.6107 Current version in Fedora Rawhide: 1.6104 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 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=40FL0TcdtAa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 910272] perl-Growl-GNTP-0.20 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=910272 Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org changed: What|Removed |Added Summary|perl-Growl-GNTP-0.18 is |perl-Growl-GNTP-0.20 is |available |available --- Comment #3 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Latest upstream release: 0.20 Current version in Fedora Rawhide: 0.16 URL: http://search.cpan.org/dist/Growl-GNTP/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=NDjrrq94zca=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 949460] New: perl-Test-YAML-Meta-0.20 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=949460 Bug ID: 949460 Summary: perl-Test-YAML-Meta-0.20 is available Product: Fedora Version: rawhide Component: perl-Test-YAML-Meta Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Assignee: berra...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: berra...@redhat.com, perl-devel@lists.fedoraproject.org, trem...@tremble.org.uk Category: --- Latest upstream release: 0.20 Current version in Fedora Rawhide: 0.19 URL: http://search.cpan.org/dist/Test-YAML-Meta/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=GGlPWcgdtVa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 861732] perlbrew-0.62 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=861732 Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org changed: What|Removed |Added Summary|perlbrew-0.61 is available |perlbrew-0.62 is available --- Comment #12 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Latest upstream release: 0.62 Current version in Fedora Rawhide: 0.50 URL: http://search.cpan.org/dist/App-perlbrew/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=cIIh60OwyRa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 949458] perl-App-cpanminus-1.6107 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=949458 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC|mmasl...@redhat.com | Assignee|mmasl...@redhat.com |ppi...@redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=dYbl85HW1Xa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File App-cpanminus-1.6107.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-App-cpanminus: be611dce0f19a38b522660370eb763f9 App-cpanminus-1.6107.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-App-cpanminus] 1.6107 bump
commit 11b465b71e8aae028cf1ec4f4f0be6e2373bf5a3
Author: Petr Písař ppi...@redhat.com
Date: Mon Apr 8 11:27:20 2013 +0200
1.6107 bump
.gitignore |1 +
perl-App-cpanminus.spec |6 --
sources |2 +-
3 files changed, 6 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 8a6d014..c872e34 100644
--- a/.gitignore
+++ b/.gitignore
@@ -43,3 +43,4 @@ App-cpanminus-0.9935.tar.gz
/App-cpanminus-1.6102.tar.gz
/App-cpanminus-1.6104.tar.gz
/App-cpanminus-1.6105.tar.gz
+/App-cpanminus-1.6107.tar.gz
diff --git a/perl-App-cpanminus.spec b/perl-App-cpanminus.spec
index b8cf5f8..6791039 100644
--- a/perl-App-cpanminus.spec
+++ b/perl-App-cpanminus.spec
@@ -1,5 +1,5 @@
Name: perl-App-cpanminus
-Version:1.6105
+Version:1.6107
Release:1%{?dist}
Summary:Get, unpack, build and install CPAN modules
License:GPL+ or Artistic
@@ -40,7 +40,6 @@ Requires: perl(Getopt::Long)
# HTTP::Tiny bundled
Requires: perl(IO::File)
Requires: perl(IO::Socket)
-Requires: perl(JSON)
# JSON::PP bundled
# lib::core::only not used
# local::lib bundled
@@ -94,6 +93,9 @@ make test
%{_bindir}/cpanm
%changelog
+* Mon Apr 08 2013 Petr Pisar ppi...@redhat.com - 1.6107-1
+- 1.6107 bump
+
* Mon Apr 08 2013 Petr Pisar ppi...@redhat.com - 1.6105-1
- 1.6105 bump
diff --git a/sources b/sources
index 5c337bd..104c38a 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-8c17979d4e8c9ac2ad3b26e823369d55 App-cpanminus-1.6105.tar.gz
+be611dce0f19a38b522660370eb763f9 App-cpanminus-1.6107.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 949458] perl-App-cpanminus-1.6107 is available
Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=949458 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-App-cpanminus-1.6107-1 ||.fc20 Resolution|--- |RAWHIDE Last Closed||2013-04-08 05:35:35 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=LVuLg4Qyyaa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File Test-CPAN-Meta-0.23.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-Test-CPAN-Meta: ec0129151f4631fc725a2d7ec24e4801 Test-CPAN-Meta-0.23.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
Broken dependencies: perl-Bio-SamTools
perl-Bio-SamTools has broken dependencies in the rawhide tree: On x86_64: perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq) On i386: perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::PrimarySeq) 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
Broken dependencies: perl-Math-Clipper
perl-Math-Clipper has broken dependencies in the rawhide tree: On x86_64: perl-Math-Clipper-1.17-3.fc19.x86_64 requires libpolyclipping.so.5()(64bit) On i386: perl-Math-Clipper-1.17-3.fc19.i686 requires libpolyclipping.so.5 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
Broken dependencies: perl-Bio-ASN1-EntrezGene
perl-Bio-ASN1-EntrezGene has broken dependencies in the rawhide tree: On x86_64: perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) On i386: perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) 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
[perl-Test-CPAN-Meta] Update to 0.23
commit 295f5199f83cb2cf01d101be9ef2b15ec03fd29e
Author: Paul Howarth p...@city-fan.org
Date: Mon Apr 8 12:00:03 2013 +0100
Update to 0.23
- New upstream release 0.23
- Updated INSTALL instructions
- Added minimum perl version (5.006)
- Reworked Makefile.PL for clarity
- Implemented Perl::Critic suggestions
- Added meta_yaml_ok test and example
- Several Version.pm updates, including new() parameter name change:
'yaml' is now 'data'
- Changes file dates changed to meet W3CDTF standards
- Don't use macros for commands
- Don't need to remove empty directories from the buildroot
- Make %files list more explicit
- Drop %defattr, redundant since rpm 4.4
.gitignore |3 +--
perl-Test-CPAN-Meta.spec | 39 +--
sources |2 +-
3 files changed, 27 insertions(+), 17 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 140934d..b9ac7bb 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1 @@
-Test-CPAN-Meta-0.17.tar.gz
-/Test-CPAN-Meta-0.21.tar.gz
+/Test-CPAN-Meta-[0-9.]*.tar.gz
diff --git a/perl-Test-CPAN-Meta.spec b/perl-Test-CPAN-Meta.spec
index 41a2b3d..940f046 100644
--- a/perl-Test-CPAN-Meta.spec
+++ b/perl-Test-CPAN-Meta.spec
@@ -1,12 +1,12 @@
Name: perl-Test-CPAN-Meta
-Version:0.21
-Release:4%{?dist}
+Version:0.23
+Release:1%{?dist}
Summary:Validation of the META.yml file in a CPAN distribution
License:Artistic 2.0
Group: Development/Libraries
URL:http://search.cpan.org/dist/Test-CPAN-Meta/
Source0:
http://www.cpan.org/authors/id/B/BA/BARBIE/Test-CPAN-Meta-%{version}.tar.gz
-BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(id -nu)
BuildArch: noarch
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(IO::File)
@@ -16,7 +16,7 @@ BuildRequires: perl(Test::Builder::Tester)
BuildRequires: perl(Test::More) = 0.70
BuildRequires: perl(Test::Pod) = 1.00
BuildRequires: perl(Test::Pod::Coverage) = 0.08
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
%description
This module was written to ensure that a META.yml file, provided with a
@@ -32,18 +32,14 @@ iconv -f iso-8859-1 -t utf-8 LICENSE LICENSE.tmp
mv -f LICENSE.tmp LICENSE
%build
-%{__perl} Makefile.PL INSTALLDIRS=vendor
+perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
-
make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
-
find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
-find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \;
-
-%{_fixperms} $RPM_BUILD_ROOT/*
+%{_fixperms} $RPM_BUILD_ROOT
%check
make test AUTOMATED_TESTING=1
@@ -52,12 +48,27 @@ make test AUTOMATED_TESTING=1
rm -rf $RPM_BUILD_ROOT
%files
-%defattr(-,root,root,-)
%doc Changes LICENSE README examples/
-%{perl_vendorlib}/*
-%{_mandir}/man3/*
+%{perl_vendorlib}/Test/
+%{_mandir}/man3/Test::CPAN::Meta.3pm*
+%{_mandir}/man3/Test::CPAN::Meta::Version.3pm*
%changelog
+* Mon Apr 8 2013 Paul Howarth p...@city-fan.org - 0.23-1
+- Update to 0.23
+ - Updated INSTALL instructions
+ - Added minimum perl version (5.006)
+ - Reworked Makefile.PL for clarity
+ - Implemented Perl::Critic suggestions
+ - Added meta_yaml_ok test and example
+ - Several Version.pm updates, including new() parameter name change:
+'yaml' is now 'data'
+ - Changes file dates changed to meet W3CDTF standards
+- Don't use macros for commands
+- Don't need to remove empty directories from the buildroot
+- Make %%files list more explicit
+- Drop %%defattr, redundant since rpm 4.4
+
* Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.21-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
@@ -80,7 +91,7 @@ rm -rf $RPM_BUILD_ROOT
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild
* Wed Dec 22 2010 Marcela Maslanova mmasl...@redhat.com - 0.17-2
-- 661697 rebuild for fixing problems with vendorach/lib
+- Rebuild to fix problems with vendorarch/lib (#661697)
* Sat Jul 31 2010 Paul Howarth p...@city-fan.org - 0.17-1
- Update to 0.17
diff --git a/sources b/sources
index 59e9832..0718e20 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-949b5867708c1fe5a3ac51cdcb25eaea Test-CPAN-Meta-0.21.tar.gz
+ec0129151f4631fc725a2d7ec24e4801 Test-CPAN-Meta-0.23.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Test-CPAN-Meta] Created tag perl-Test-CPAN-Meta-0.23-1.fc19
The lightweight tag 'perl-Test-CPAN-Meta-0.23-1.fc19' was created pointing to: 295f519... Update to 0.23 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Test-CPAN-Meta] Created tag perl-Test-CPAN-Meta-0.23-1.fc20
The lightweight tag 'perl-Test-CPAN-Meta-0.23-1.fc20' was created pointing to: 295f519... Update to 0.23 -- 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-Bio-SamTools
perl-Bio-SamTools has broken dependencies in the F-19 tree: On x86_64: perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq) On i386: perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::PrimarySeq) 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
Broken dependencies: perl-Bio-ASN1-EntrezGene
perl-Bio-ASN1-EntrezGene has broken dependencies in the F-19 tree: On x86_64: perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) On i386: perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) 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
Broken dependencies: perl-Math-Clipper
perl-Math-Clipper has broken dependencies in the F-19 tree: On x86_64: perl-Math-Clipper-1.17-3.fc19.x86_64 requires libpolyclipping.so.5()(64bit) On i386: perl-Math-Clipper-1.17-3.fc19.i686 requires libpolyclipping.so.5 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
[perl-ExtUtils-Config/el6] Initial import (perl-ExtUtils-Config-0.007-2)
Summary of changes: 6eec1d0... Initial import (perl-ExtUtils-Config-0.007-2) (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers/f19] Initial import (perl-ExtUtils-Helpers-0.014-2)
Summary of changes: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers/f18] Initial import (perl-ExtUtils-Helpers-0.014-2)
Summary of changes: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Config/el5] Initial import (perl-ExtUtils-Config-0.007-2)
Summary of changes: 6eec1d0... Initial import (perl-ExtUtils-Config-0.007-2) (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Config] Created tag perl-ExtUtils-Config-0.007-2.fc17
The lightweight tag 'perl-ExtUtils-Config-0.007-2.fc17' was created pointing to: 6eec1d0... Initial import (perl-ExtUtils-Config-0.007-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers/f17] Initial import (perl-ExtUtils-Helpers-0.014-2)
Summary of changes: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Config] Created tag perl-ExtUtils-Config-0.007-2.fc18
The lightweight tag 'perl-ExtUtils-Config-0.007-2.fc18' was created pointing to: 6eec1d0... Initial import (perl-ExtUtils-Config-0.007-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Config] Created tag perl-ExtUtils-Config-0.007-2.fc19
The lightweight tag 'perl-ExtUtils-Config-0.007-2.fc19' was created pointing to: 6eec1d0... Initial import (perl-ExtUtils-Config-0.007-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Config] Created tag perl-ExtUtils-Config-0.007-2.fc20
The lightweight tag 'perl-ExtUtils-Config-0.007-2.fc20' was created pointing to: 6eec1d0... Initial import (perl-ExtUtils-Config-0.007-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers/el6] Initial import (perl-ExtUtils-Helpers-0.014-2)
Summary of changes: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers/el5] Initial import (perl-ExtUtils-Helpers-0.014-2)
Summary of changes: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers] Created tag perl-ExtUtils-Helpers-0.014-2.el5
The lightweight tag 'perl-ExtUtils-Helpers-0.014-2.el5' was created pointing to: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers] Created tag perl-ExtUtils-Helpers-0.014-2.el6
The lightweight tag 'perl-ExtUtils-Helpers-0.014-2.el6' was created pointing to: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers] Created tag perl-ExtUtils-Helpers-0.014-2.fc17
The lightweight tag 'perl-ExtUtils-Helpers-0.014-2.fc17' was created pointing to: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers] Created tag perl-ExtUtils-Helpers-0.014-2.fc18
The lightweight tag 'perl-ExtUtils-Helpers-0.014-2.fc18' was created pointing to: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers] Created tag perl-ExtUtils-Helpers-0.014-2.fc19
The lightweight tag 'perl-ExtUtils-Helpers-0.014-2.fc19' was created pointing to: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ExtUtils-Helpers] Created tag perl-ExtUtils-Helpers-0.014-2.fc20
The lightweight tag 'perl-ExtUtils-Helpers-0.014-2.fc20' was created pointing to: efc3342... Initial import (perl-ExtUtils-Helpers-0.014-2) -- 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] #529: dn normalization must handle multiple space characters in attributes
https://fedorahosted.org/389/ticket/529 https://fedorahosted.org/389/attachment/ticket/529/0001-Ticket-529-dn-normalization-must-handle-multiple-spa.2.patch Bug description: This is the second half of the fix for #529. The first half fixed the DN normalization which used to allow DNs where only the number of spaces are different. Now it is rejucted as expected. But it breaks the backward compatibility. Fix description: The upgrade script 80upgradednformat.pl called from setup-ds.pl -u checks the duplicated DNs and rename them if necessary. For instance, if there are 2 DNs: cn=test user0,dc=example,dc=com (entryid: N) cn=testuser0,dc=example,dc=com (entryid: M) then the upgrade script/tool modifies the second one as follows: cn=test user0 M,dc=example,dc=com (entryid: M) and the original cn: testuser0 is kept in the attribute. The modified result is reported in setup-ds.pl -u as follows: Duplicated DN(s) were found and renamed. Renamed entry IDs are listed in /var/lib/dirsrv/slapd- ID/ldif/userRoot_conflict.txt. Contents of the conflict.txt: prinary entry ID: duplicated entry IDs 13:16 18 14:17 -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Fedora 19 Alpha Go/No-Go Meeting, Thursday, April 11 @ 17:00 UTC
Join us on irc.freenode.net in #fedora-meeting-1 for this important meeting, wherein we shall determine the readiness of the Fedora 19 Alpha. Thursday, April 11, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST) Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting. Verifying that the Release criteria are met is the responsibility of the QA Team. For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 19 Alpha Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/19/alpha/buglist Reminder: the Readiness meeting follows the Go/No-Go meeting two hours later. Jaroslav ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
