Re: While we're talking about RPM dependencies ...
16.04.2012 09:33, Toshio Kuratomi написал: On Mon, Apr 16, 2012 at 02:02:31AM +0400, Pavel Alexeev wrote: 16.04.2012 00:51, Toshio Kuratomi wrote: On Sun, Apr 15, 2012 at 11:16:58PM +0400, Pavel Alexeev wrote: As I look it for me for first glance. Install or update one package scenario (yum install foo): 1) Client ask last foo package version. 2) Server calculate all dependencies by self algorithms and return in requested form (several may be used from JSON to XML) full list of dependencies for that package. No other overhead provided like dependencies of all packages, filelist etc. 3) Client got it, intercept with current installed packages list, exclude whats already satisfy needs, and then request each other what does not present starting from 1. Update scenario (yum update): 1) Client ask repo-server to get a list of actual versions available packages. 2) Server answer it. 3) Client found which updated and request its as in first scenario for update. I don't think this would be a speedup. Instead of the CPUs of tens of thousands of computers doing the depsolving, you'd be requiring the CPUs of a single site to do it. Yes. And as many clients do the same work, caching will give there good results. So, sequence requests will costs nothing. No. Most requests will be different because they have a different initial state. If you read my suggestion I do not suggest send from client big upload overhead of current installed state. Client ask from server full dependency which package have, and then intercept answer with current installed software. So, answer for each client for package will be the same. Additionally it still allow resolve dependencies with several enabled repositories when some dependencies can't be resolved on one server repo. The server that constructs the subsets of repodata would become single point of failures whereas currently the repodata can be hosted on any mirror. This setup would be much more sensitive to mirrors and repodata going out of sync. There'd likely be times when a new push has gone out where the primary mirror was the only server which could push packages out as every other mirror would be out of sync wrt the repodata server. Yes, as I wrote initially it introduce more requirements to the server, especially some sort of scripting allowed (php, perl, python, ruby or other). But at all it is not exclude mirroring as it is free software and any ma install it, and sync metadata information in traditional way. If you're requiring that mirrors run the script on their systems, then that makes this idea pretty much a non-starter. We've been told by mirrors that they do not want to do this. For that mirror traditional fallback scheme will be available. But if that will be implemented, I think appeared new mirrors also. And client may prefer one or another type depending by they needs. Additional it can be implemented as only solver mirror to serve requests and then point to download on other(s) mirrors. In that case requirements will be small and it may be hosted even on shared hosting. So, I too can provide that mirror. -Toshio -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: bug or feature? gdm logins not recorded in lastlog
On Mon, 2012-04-16 at 00:03 -0400, John Ellson wrote: Before I generate a bug report, could I get a second opinion on whether this is a bug or a feature? Console logins through gdm are not getting recorded in lastlog. (Fedora 16) I think it is a bug. It might be solvable by adding the line: sessionrequiredpam_lastlog.so silent nowtmp to the gdm PAM configuration files. -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building the GNOME 3.4.1 Release
On Sat, 2012-04-14 at 13:53 +0100, Richard Hughes wrote: If you're maintaining a GNOMEish package and you want it included in the 3.4.1 release, please build the package like normal and then add the build ID to: https://docs.google.com/spreadsheet/ccc?key=0AtzJKpbiGX1zdGJzeU9waFJFZmgyQzBuN2VxU0lxbHc Hi, it will be kind of you to not touch packages you do not own, especially those which are actively maintained. The way you did it breaks build the package like normal from your instructions. Most of the packages released on ftp.gnome.org with the exact version 3.4.1 can be handled by the mclazy script, but I'm sure there are other packages that we'll need to do manually for the 3.4.1 mega-update. I've no idea what it means in reality. Say I'll not add my build ids into your google page, am I still responsible for filling update of my packages? Bye, Milan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Looking for a sponsor
Hello, I have several package reviews pending to be approved, and I also need a sponsor. Is there any willing sponsor who can help me with this? I can swap reviews if there is someone interested in a non informal review. One of my packages is gogoc, a client for the IPv6 tunnel broker freenet6.net. It would be interesting if it can be available before the world IPv6 day on June 6th https://bugzilla.redhat.com/show_bug.cgi?id=738556 Other package is arm, a program for monitoring the Tor routers. I have split this one in three packages, because it included some third party libraries in the same tarball. https://bugzilla.redhat.com/show_bug.cgi?id=756445 https://bugzilla.redhat.com/show_bug.cgi?id=756443 https://bugzilla.redhat.com/show_bug.cgi?id=756435 Thank you. Juan Orti. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building the GNOME 3.4.1 Release
On 16 April 2012 10:13, Milan Crha mc...@redhat.com wrote: it will be kind of you to not touch packages you do not own, especially those which are actively maintained. The way you did it breaks build the package like normal from your instructions. In the same way I've emailed for your two other privately emails, apologies. If you had already updated F17 with the upstream 3.4.1 then the automatic script would have ignored your package completely. There's no way for me to know the difference between maintainer not doing update because he's busy and maintainer wants to handle this himself in his own time. Now you've told me in a not-so-polite way I'll just take off evolution from the auto-build list. I've no idea what it means in reality. Say I'll not add my build ids into your google page, am I still responsible for filling update of my packages? Yes, if you want to be, although I think we should aim to have one easy-to-qa update for micro-point updates of a single desktop environment, rather than the huge number of updates we had before that were *impossible* to QA [1]. Is there a reason evolution is so special that it shouldn't be considered a core GNOME package that gets released with everything else? Richard. [1] As often non-core packages need new versions of libgnome3 to build against or new DBus interfaces in gnome-settings-daemon at runtime. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building the GNOME 3.4.1 Release
On Mon, 2012-04-16 at 10:33 +0100, Richard Hughes wrote: ... If you had already updated F17 with the upstream 3.4.1 then the automatic script would have ignored your package completely. Hey, I didn't have much time to do so. You script stepped in only two hours after release on Gnome's ftp. It's not so bad, but still early and unexpected for me. There's no way for me to know the difference between maintainer not doing update because he's busy and maintainer wants to handle this himself in his own time. Maybe he's just _currently_ busy, sleeping (consider different timezones) and so on? Anyway, I never asked to have those packages part of the auto-build list, and never was asked for acceptance. This is easily distinguishable, isn't it? Now you've told me in a not-so-polite way I'll just take off evolution from the auto-build list. evolution*, please. I've no idea what it means in reality. Say I'll not add my build ids into your google page, am I still responsible for filling update of my packages? Yes, if you want to be, although I think we should aim to have one easy-to-qa update for micro-point updates of a single desktop environment, rather than the huge number of updates we had before that were *impossible* to QA [1]. Is there a reason evolution is so special that it shouldn't be considered a core GNOME package that gets released with everything else? I cannot answer this objectively now, I'm sorry. There is certainly nothing extra special about those packages, apart of your auto-build script not being able to build those packages correctly (which it cannot do in general anyway), but I currently have bad feelings about this process, so, well, let me think about it. Bye, Milan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File Sys-Virt-0.9.11.tar.gz uploaded to lookaside cache by berrange
A file has been added to the lookaside cache for perl-Sys-Virt: ef7cc31803667fbb894bff5a13692d68 Sys-Virt-0.9.11.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-Sys-Virt] Update to 0.9.11 release
commit 3b4ca404602122a806aee61ddb439674373ba925
Author: Daniel P. Berrange berra...@redhat.com
Date: Mon Apr 16 11:33:53 2012 +0100
Update to 0.9.11 release
perl-Sys-Virt.spec |7 +--
sources|2 +-
2 files changed, 6 insertions(+), 3 deletions(-)
---
diff --git a/perl-Sys-Virt.spec b/perl-Sys-Virt.spec
index 11cc769..d54b275 100644
--- a/perl-Sys-Virt.spec
+++ b/perl-Sys-Virt.spec
@@ -1,7 +1,7 @@
# Automatically generated by perl-Sys-Virt.spec.PL
Name: perl-Sys-Virt
-Version:0.9.10
+Version:0.9.11
Release:1%{?dist}%{?extra_release}
Summary:Represent and manage a libvirt hypervisor connection
License:GPLv2+ or Artistic
@@ -15,7 +15,7 @@ BuildRequires: perl(Test::Pod::Coverage)
BuildRequires: perl(Test::CPAN::Changes)
BuildRequires: perl(XML::XPath)
BuildRequires: perl(Time::HiRes)
-BuildRequires: libvirt-devel = 0.9.10
+BuildRequires: libvirt-devel = 0.9.11
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
%description
@@ -59,6 +59,9 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man3/*
%changelog
+* Mon Apr 16 2012 Daniel P. Berrange berra...@redhat.com - 0.9.11-1
+- Update to 0.9.11 release
+
* Mon Feb 13 2012 Daniel P. Berrange berra...@redhat.com - 0.9.10-1
- Update to 0.9.10 release
diff --git a/sources b/sources
index 4836677..bc2f618 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-363b206e39b24f69d642b337e324aba6 Sys-Virt-0.9.10.tar.gz
+ef7cc31803667fbb894bff5a13692d68 Sys-Virt-0.9.11.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: Building the GNOME 3.4.1 Release
On 16 April 2012 11:32, Milan Crha mc...@redhat.com wrote: Maybe he's just _currently_ busy, sleeping (consider different timezones) and so on? Anyway, I never asked to have those packages part of the auto-build list, and never was asked for acceptance. This is easily distinguishable, isn't it? I was asked to handle the GNOME mega-updates because so much of GNOME was released in a semi-random way with packages getting left behind. I'm sorry if I had not consulted everyone before I started, but the kind of maintainer who is too busy to build packages is also the kind of person who's too busy to send me an email to opt-in. So far only two maintainers have asked to be opted out of the new system and i guess a few dozen people have thanked me for automating an otherwise boring and repetitive task. evolution*, please. Yup, done. ...but I currently have bad feelings about this process... For the record, I think you've completely over-reacted. One polite email would have made you look much more helpful and professional than *4* angry emails. Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Where document service which is disabled after F16-F17 upgrade via yum
Hello all, named service is disabled after F16-F17 update via yum due to initscripts-systemd conversion. It wasn't possible to keep it enabled when was due to too many differences between initscripts and systemd unit files. As written in https://bugzilla.redhat.com/show_bug.cgi?id=808889, this backward incompatibility should be documented somewhere but I'm not sure where. Can you please point me where should I document it? Thank you in advance. Regards, Adam -- Adam Tkac, Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building the GNOME 3.4.1 Release
On Mon, 2012-04-16 at 11:13 +0200, Milan Crha wrote: On Sat, 2012-04-14 at 13:53 +0100, Richard Hughes wrote: If you're maintaining a GNOMEish package and you want it included in the 3.4.1 release, please build the package like normal and then add the build ID to: https://docs.google.com/spreadsheet/ccc?key=0AtzJKpbiGX1zdGJzeU9waFJFZmgyQzBuN2VxU0lxbHc Hi, it will be kind of you to not touch packages you do not own, especially those which are actively maintained. The way you did it breaks build the package like normal from your instructions. We've always built packages coming from the GNOME FTP and that follow the GNOME releases. Matthias did it, I did it, Tomas did it, and now Richard is doing it. What's so special about Evolution that we can't update it as a bug fix update when the package is released on the FTP site? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F-17 Branched report: 20120416 changes
Compose started at Mon Apr 16 08:15:03 UTC 2012 Broken deps for x86_64 -- [aeolus-conductor] aeolus-conductor-0.4.0-2.fc17.noarch requires ruby(abi) = 0:1.8 [aeolus-configserver] aeolus-configserver-0.4.5-1.fc17.noarch requires ruby-nokogiri [ale] ale-0.9.0.3-6.fc17.x86_64 requires libMagickCore.so.4()(64bit) [alexandria] alexandria-0.6.8-2.fc17.1.noarch requires ruby(abi) = 0:1.8 [cuneiform] cuneiform-1.1.0-6.fc17.i686 requires libMagick++.so.4 cuneiform-1.1.0-6.fc17.x86_64 requires libMagick++.so.4()(64bit) [dh-make] dh-make-0.55-4.fc17.noarch requires debhelper [dmapd] dmapd-0.0.47-2.fc17.i686 requires libMagickWand.so.4 dmapd-0.0.47-2.fc17.i686 requires libMagickCore.so.4 dmapd-0.0.47-2.fc17.x86_64 requires libMagickWand.so.4()(64bit) dmapd-0.0.47-2.fc17.x86_64 requires libMagickCore.so.4()(64bit) [dogtag-pki] dogtag-pki-9.0.0-10.fc17.noarch requires pki-util-javadoc = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-util = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-tks = 0:9.0.9 dogtag-pki-9.0.0-10.fc17.noarch requires pki-symkey = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-silent = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-setup = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-selinux = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-ocsp = 0:9.0.9 dogtag-pki-9.0.0-10.fc17.noarch requires pki-native-tools = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-kra = 0:9.0.10 dogtag-pki-9.0.0-10.fc17.noarch requires pki-java-tools-javadoc = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-java-tools = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-common-javadoc = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-common = 0:9.0.18 dogtag-pki-9.0.0-10.fc17.noarch requires pki-ca = 0:9.0.18 [drawtiming] drawtiming-0.7.1-5.fc17.x86_64 requires libMagickCore.so.4()(64bit) drawtiming-0.7.1-5.fc17.x86_64 requires libMagick++.so.4()(64bit) [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [dx] dx-4.4.4-21.fc17.x86_64 requires libMagickCore.so.4()(64bit) dx-libs-4.4.4-21.fc17.i686 requires libMagickCore.so.4 dx-libs-4.4.4-21.fc17.x86_64 requires libMagickCore.so.4()(64bit) [egoboo] egoboo-2.7.5-11.fc17.x86_64 requires libenet-1.2.1.so()(64bit) [entangle] entangle-0.3.2-1.fc17.x86_64 requires libgexiv2.so.0()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python2-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python3-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python3-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 [gorm] gorm-1.2.13-0.2.20110331.fc17.i686 requires libobjc.so.3 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-gui.so.0.20 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-base.so.1.23 gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libobjc.so.3()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-gui.so.0.20()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-base.so.1.23()(64bit) [i3] i3-4.0.1-2.fc17.x86_64 requires libxcb-property.so.1()(64bit) i3-4.0.1-2.fc17.x86_64 requires libxcb-icccm.so.1()(64bit) i3-4.0.1-2.fc17.x86_64 requires libxcb-event.so.1()(64bit) i3-4.0.1-2.fc17.x86_64 requires libxcb-aux.so.0()(64bit) i3-4.0.1-2.fc17.x86_64 requires libxcb-atom.so.1()(64bit) [ibus-gucharmap] ibus-gucharmap-1.4.0-4.fc17.x86_64 requires libibus-1.0.so.0()(64bit) [ibus-panel-extensions] ibus-panel-extensions-1.4.99.20111207-2.fc17.i686 requires libibus-1.0.so.0 ibus-panel-extensions-1.4.99.20111207-2.fc17.x86_64 requires libibus-1.0.so.0()(64bit) [imageinfo] imageinfo-0.05-14.fc17.x86_64 requires libMagickCore.so.4()(64bit) [inkscape] inkscape-0.48.2-4.fc17.x86_64 requires libMagickCore.so.4()(64bit) inkscape-0.48.2-4.fc17.x86_64 requires libMagick++.so.4()(64bit) inkscape-view-0.48.2-4.fc17.x86_64 requires libMagickCore.so.4()(64bit) inkscape-view-0.48.2-4.fc17.x86_64 requires libMagick++.so.4()(64bit) [jboss-as] jboss-as-7.1.0-2.fc17.noarch requires slf4j-jboss-logmanager [k3d] k3d-0.8.0.2-6.fc17.i686 requires libMagickCore.so.4 k3d-0.8.0.2-6.fc17.i686 requires libMagick++.so.4 k3d-0.8.0.2-6.fc17.x86_64 requires libMagickCore.so.4()(64bit) k3d-0.8.0.2-6.fc17.x86_64 requires libMagick++.so.4()(64bit) [kxstitch] kxstitch-0.8.4.1-8.fc17.x86_64 requires libMagickCore.so.4()(64bit)
Re: Where document service which is disabled after F16-F17 upgrade via yum
On 04/16/2012 10:44 AM, Adam Tkac wrote: Hello all, named service is disabled after F16-F17 update via yum due to initscripts-systemd conversion. It wasn't possible to keep it enabled when was due to too many differences between initscripts and systemd unit files. As written in https://bugzilla.redhat.com/show_bug.cgi?id=808889, this backward incompatibility should be documented somewhere but I'm not sure where. Can you please point me where should I document it? Thank you in advance. Hmm was this not generally documented in the release notes for F15/F16 since this affects *all* service that get migrated between releases. JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Building the GNOME 3.4.1 Release
On Mon, 2012-04-16 at 12:17 +0100, Bastien Nocera wrote: We've always built packages coming from the GNOME FTP and that follow the GNOME releases. Matthias did it, I did it, Tomas did it, and now Richard is doing it. Hi, hmm, I do not see any x.x.x-1 build being done by any of those you name for evo itself for the past year. What's so special about Evolution that we can't update it as a bug fix update when the package is released on the FTP site? I still differentiate between build and update. There is no problem with the update, there is a little problem with the build. It's mainly because dependencies between those packages, and in case of evo 3.4.0.1 also slightly more complicated change in the .spec file, which the smart script didn't know about. Bye, Milan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: bug or feature? gdm logins not recorded in lastlog
On 04/16/2012 03:16 AM, Tomas Mraz wrote: On Mon, 2012-04-16 at 00:03 -0400, John Ellson wrote: Before I generate a bug report, could I get a second opinion on whether this is a bug or a feature? Console logins through gdm are not getting recorded in lastlog. (Fedora 16) I think it is a bug. It might be solvable by adding the line: sessionrequiredpam_lastlog.so silent nowtmp to the gdm PAM configuration files. Thanks Tomas, that does seem to fix it. Bugzilla #812853 John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20120416 changes
Compose started at Mon Apr 16 08:15:05 UTC 2012 Broken deps for x86_64 -- [389-ds-base] 389-ds-base-1.2.11-0.1.a1.fc18.x86_64 requires libdb-5.2.so()(64bit) [aeolus-conductor] aeolus-conductor-0.4.0-2.fc17.noarch requires ruby(abi) = 0:1.8 [aeolus-configserver] aeolus-configserver-0.4.5-1.fc18.noarch requires ruby-nokogiri [anaconda] anaconda-18.1-1.fc18.x86_64 requires librpmio.so.2()(64bit) anaconda-18.1-1.fc18.x86_64 requires librpm.so.2()(64bit) [axis2c] axis2c-1.6.0-4.fc17.i686 requires httpd-mmn = 0:20051115-x86-32 axis2c-1.6.0-4.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python2-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python3-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python3-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 [gnome-applet-sensors] gnome-applet-sensors-2.2.7-4.fc15.i686 requires libpanel-applet-2.so.0 gnome-applet-sensors-2.2.7-4.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) [gorm] gorm-1.2.13-0.2.20110331.fc17.i686 requires libobjc.so.3 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-gui.so.0.20 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-base.so.1.23 gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libobjc.so.3()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-gui.so.0.20()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-base.so.1.23()(64bit) [gridsite] gridsite-1.7.19-1.fc18.x86_64 requires httpd-mmn = 0:20051115-x86-64 [inkscape] inkscape-0.48.2-4.fc17.x86_64 requires libMagickCore.so.4()(64bit) inkscape-0.48.2-4.fc17.x86_64 requires libMagick++.so.4()(64bit) inkscape-view-0.48.2-4.fc17.x86_64 requires libMagickCore.so.4()(64bit) inkscape-view-0.48.2-4.fc17.x86_64 requires libMagick++.so.4()(64bit) [lcgdm-dav] lcgdm-dav-server-0.7.0-1.fc18.x86_64 requires httpd-mmn = 0:20051115-x86-64 [libapreq2] libapreq2-2.13-6.fc17.i686 requires httpd-mmn = 0:20051115-x86-32 libapreq2-2.13-6.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [matreshka] matreshka-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnarl-4.6.so matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnarl-4.6.so()(64bit) matreshka-sql-core-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-core-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-postgresql-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-postgresql-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-sqlite-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-sqlite-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) [mcollective] mcollective-common-1.3.1-7.fc17.noarch requires ruby(abi) = 0:1.8 [meshlab] meshlab-1.3.1-2.fc17.x86_64 requires libmuparser.so.0()(64bit) [mod_auth_pam] mod_auth_pam-1.1.1-11.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_cband] mod_cband-0.9.7.5-7.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_cluster] mod_cluster-1.1.1-4.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_geoip] mod_geoip-1.2.5-6.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_limitipconn] mod_limitipconn-0.23-5.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_line_edit] mod_line_edit-1.0.0-8.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_log_post] mod_log_post-0.1.0-4.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_perl] mod_perl-2.0.5-8.fc18.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_pubcookie] mod_pubcookie-3.3.4a-7.fc18.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_python] mod_python-3.3.1-17.fc17.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_scgi] mod_scgi-1.13-5.fc15.x86_64 requires httpd-mmn = 0:20051115 [mod_security] mod_security-2.5.13-3.fc18.x86_64 requires httpd-mmn = 0:20051115-x86-64 [mod_suphp] mod_suphp-0.6.3-8.fc18.x86_64 requires httpd-mmn = 0:20051115-x86-64 [moksha] moksha-0.5.0-5.fc15.noarch requires pyevent [natus] libnatus-V8-0.1.5-2.fc15.x86_64 requires libv8-3.0.0.1.so()(64bit) [ocaml-augeas] ocaml-augeas-0.4-9.fc15.x86_64 requires ocaml(runtime) = 0:3.12.0
Re: rawhide report: 20120416 changes
On Mon, Apr 16, 2012 at 02:03:45PM +, Fedora Rawhide Report wrote: Compose started at Mon Apr 16 08:15:05 UTC 2012 Broken deps for x86_64 -- [vdsm] vdsm-4.9.3.2-0.fc17.x86_64 requires /usr/sbin/saslpasswd2 Jindrich Novy has updated cyrus-sasl to re-enable the saslpasswd2 binary, so this should be resolved in tomorrows dep-check. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] 2012-04-16 @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2012-04-16 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! Apologies for the late notice but we're still planning to hold a QA meeting in a couple hours. Please add any topic suggestions to the meeting wiki page: https://fedoraproject.org/wiki/QA/Meetings/20120409 The current proposed agenda is included below. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 17 Beta Retrospective 4. Test Day report 5. Upcoming QA events 6. AutoQA update 7. Open floor signature.asc Description: PGP 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
systemd: Can Type=simple be used with a wrapper script?
I'm working on a package that uses a wrapper script to start the daemon, so as the subject says: Can I use Type=simple if the daemon uses a wrapper script or am I stuck with Type=forking? Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd: Can Type=simple be used with a wrapper script?
On Mon, 2012-04-16 at 10:24 -0500, Richard Shaw wrote: I'm working on a package that uses a wrapper script to start the daemon, so as the subject says: Can I use Type=simple if the daemon uses a wrapper script or am I stuck with Type=forking? AIUI yes, but you have to exec the real binary, i.e. the PID of your daemon mustn't change lest systemd thinks your daemon died. Nils -- Nils Philippsen Those who would give up Essential Liberty to purchase Red Hat a little Temporary Safety, deserve neither Liberty n...@redhat.com nor Safety. -- Benjamin Franklin, 1759 PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd: Can Type=simple be used with a wrapper script?
On Mon, Apr 16, 2012 at 10:30 AM, Nils Philippsen n...@redhat.com wrote: On Mon, 2012-04-16 at 10:24 -0500, Richard Shaw wrote: I'm working on a package that uses a wrapper script to start the daemon, so as the subject says: Can I use Type=simple if the daemon uses a wrapper script or am I stuck with Type=forking? AIUI yes, but you have to exec the real binary, i.e. the PID of your daemon mustn't change lest systemd thinks your daemon died. So really no :) That's OK, I can use forking... Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Fedora-packaging] [Guidelines Change] Changes to the Packaging Guidelines
On 14/04/12 20:32 +0100, Jeroen van Meeuwen wrote: On Thursday, April 12, 2012 04:57:29 PM Tom Callaway wrote: A bundling exception for boost within Passenger was granted, due to the intrusive nature of the forked changes, the efforts of the maintainer to merge as many of them as possible into the upstream boost source tree, and the visible efforts of the upstream to keep the bundled copy of boost in sync with the current boost releases. The package must also include a Requires: bundled(boost) = $VERSION where $VERSION is the boost version being bundled. https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Packages_grant ed_exceptions While I appreciate the work Brett Lentz has been putting in upstream, why does this package have to be taken away from me? I'm already facing a thanks for your work but no thanks[1]. I apologize if that's how it sounded. That wasn't my intended meaning. The issue was that you just started dropping your updated specs into the bug report without any comment and seemingly prior to understanding the scope of the exception that was granted. In addition, your last update to the bug was on 2010-11-21. As far as I could tell, you had abandoned this review request. I respectfully request Uncle Shadowman *not* be forcefully made the owner of the package, and the reporter of the review request be granted ownership. As we've discussed elsewhere, I see no reason why we can't share ownership of the package. We've both contributed quite a bit to making the package acceptable for Fedora, and there's plenty of room for both of us to continue maintaining it. Kind regards, Jeroen van Meeuwen [1] https://bugzilla.redhat.com/show_bug.cgi?id=470696#c114 -- Systems Architect, Kolab Systems AG e: vanmeeuwen at kolabsys.com m: +44 74 2516 3817 w: http://www.kolabsys.com pgp: 9342 BF08 ---Brett. pgp2Y0NfUK2nO.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Guidelines Change] Changes to the Packaging Guidelines
On Thu, Apr 12, 2012 at 04:57:29PM -0400, Tom Callaway wrote: Packages which have SysV initscripts that contain 'non-standard service commands' (commands besides start, stop, reload, restart, or try-restart) must convert those commands into standalone helper scripts. Systemd does not support non-standard unit commands. https://fedoraproject.org/wiki/Packaging:Systemd#Unit_Files The guideline for SysV initscripts[0] also specifies the commands force-reload, status and usage. Why are these dropped? Also how should new helper scripts be named after the conversion? A best practice naming schema would make it a lot easier for a user to find the matching helper script for removed commands. Regards Till [0] http://fedoraproject.org/wiki/Packaging:SysVInitScript#Required_Actions -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Summary/Minutes from today's FESCo Meeting (2012-04-16)
=== #fedora-meeting: FESCO (2012-04-16) === Meeting started by nirik at 17:05:17 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2012-04-16/fesco.2012-04-16-17.05.log.html . Meeting summary --- * init process (nirik, 17:05:17) * #833 Clarify provenpackagers communication policy for making changes to packages (nirik, 17:06:38) * AGREED: Will add wording about contacting maintainers to provenpackager policy and announce. (+7) (nirik, 17:10:47) * ACTION: mmaslano to make change to wiki and announce. (nirik, 17:11:36) * #830 define requirements for secondary arch promotion (nirik, 17:11:40) * LINK: http://fedoraproject.org/wiki/Secondary_Architecture_Promotion_Requirements_(Draft) (nirik, 17:11:40) * AGREED: Defer this issue a week and wait for more feedback/changes to draft. (+7) (nirik, 17:28:42) * #829 New proven packagers request: Pavel Alexeev(hubbitus) (nirik, 17:29:16) * LINK: https://admin.fedoraproject.org/updates/FEDORA-2012-4828 needs to go stable. (nirik, 17:34:58) * AGREED: request is approved. (+7) (nirik, 17:36:03) * Open Floor (nirik, 17:36:09) * ACTION: mjg59 will chair next week. (nirik, 17:38:58) * ACTION: nirik to update meeting process page. (nirik, 17:45:10) Meeting ended at 17:49:01 UTC. Action Items * mmaslano to make change to wiki and announce. * mjg59 will chair next week. * nirik to update meeting process page. Action Items, by person --- * mjg59 * mjg59 will chair next week. * mmaslano * mmaslano to make change to wiki and announce. * nirik * nirik to update meeting process page. * **UNASSIGNED** * (none) People Present (lines said) --- * nirik (74) * pjones (22) * mjg59 (21) * jonmasters (18) * t8m (17) * notting (11) * bconoboy (11) * mitr (10) * limburgher (10) * mmaslano (9) * zodbot (7) * jsmith (2) * tflink (1) * sgallagh (0) -- 17:05:17 nirik #startmeeting FESCO (2012-04-16) 17:05:17 zodbot Meeting started Mon Apr 16 17:05:17 2012 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:05:17 zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:05:17 nirik #meetingname fesco 17:05:17 zodbot The meeting name has been set to 'fesco' 17:05:17 nirik #chair notting nirik mjg59 mmaslano t8m pjones sgallagh mitr limburgher 17:05:17 nirik #topic init process 17:05:18 zodbot Current chairs: limburgher mitr mjg59 mmaslano nirik notting pjones sgallagh t8m 17:05:23 * notting is here 17:05:27 * limburgher is here 17:05:27 t8m Hi 17:05:27 mitr Hello all 17:05:33 mmaslano hello 17:05:33 nirik sorry for the delay everyone. 17:06:16 pjones hi./ 17:06:30 nirik ok, shall we go ahead and dive in? 17:06:38 nirik #topic #833 Clarify provenpackagers communication policy for making changes to packages 17:06:39 nirik .fesco 833 17:06:41 zodbot nirik: #833 (Clarify provenpackagers communication policy for making changes to packags) – FESCo - https://fedorahosted.org/fesco/ticket/833 17:06:54 nirik mmaslano: you were going to propose/make some wording changes? 17:07:23 mmaslano nirik: I'm fine with berrange proposal :) 17:07:35 mmaslano I won't correct English speakers ;-) 17:07:38 mjg59 Hi 17:07:38 nirik yeah, seems fine to me too. 17:07:47 limburgher Agreed, sane. 17:07:55 mmaslano I'll add it to the wiki page 17:08:06 nirik +1 17:08:09 mjg59 Works for me 17:08:24 mitr I'm not sure we want it that strict, e.g. for handling urgent issues or mass changes in rawhide preannounced on fedora-devel 17:08:44 nirik well, it says should try 17:08:48 mitr right 17:08:55 pjones Well, I wish he'd use the series comma, but sure, that's fine. 17:09:29 t8m I think the should already includes the common sense when applicable. 17:09:31 t8m so +1 17:09:49 mmaslano +1 if voting needed 17:09:54 mitr +1 then, we can always weaken it later 17:09:54 limburgher +1 17:10:14 mjg59 +1 17:10:18 pjones +1 17:10:37 notting +1 17:10:47 nirik #agreed Will add wording about contacting maintainers to provenpackager policy and announce. (+7) 17:11:08 nirik mmaslano: can you announce the change too? or would you like someone else to? 17:11:24 mmaslano nirik: I can send an email to devel 17:11:29 nirik thanks. 17:11:36 nirik #action mmaslano to make change to wiki and announce. 17:11:40 nirik #topic #830 define requirements for secondary arch promotion 17:11:40 nirik .fesco 830 17:11:40 nirik http://fedoraproject.org/wiki/Secondary_Architecture_Promotion_Requirements_(Draft) 17:11:41 zodbot nirik: #830 (define requirements for secondary arch promotion) – FESCo - https://fedorahosted.org/fesco/ticket/830 17:12:05 nirik so, any further feedback here? does anyone have proposed changes? 17:12:26 nirik there's 2 things on the discussion tab 17:13:25 jonmasters so we will have further feedback, but not today 17:13:34
Re: [Guidelines Change] Changes to the Packaging Guidelines
Till Maas (opensou...@till.name) said: On Thu, Apr 12, 2012 at 04:57:29PM -0400, Tom Callaway wrote: Packages which have SysV initscripts that contain 'non-standard service commands' (commands besides start, stop, reload, restart, or try-restart) must convert those commands into standalone helper scripts. Systemd does not support non-standard unit commands. https://fedoraproject.org/wiki/Packaging:Systemd#Unit_Files The guideline for SysV initscripts[0] also specifies the commands force-reload, status and usage. Why are these dropped? status is a standard command, although scripts that do non-obvious status things would need to implement them in other ways. (See 'network status', as an example.) force-reload is a standard command. usage is not a standard command... since systemd enforces a standard set of verbs, it's sort of obsolete. Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd: Can Type=simple be used with a wrapper script?
On Mon, Apr 16, 2012 at 10:30 AM, Nils Philippsen n...@redhat.com wrote: On Mon, 2012-04-16 at 10:24 -0500, Richard Shaw wrote: I'm working on a package that uses a wrapper script to start the daemon, so as the subject says: Can I use Type=simple if the daemon uses a wrapper script or am I stuck with Type=forking? AIUI yes, but you have to exec the real binary, i.e. the PID of your daemon mustn't change lest systemd thinks your daemon died. Ok, after looking through the wrapper script in detail I FINALLY get what you meant :) I think type simple is going to work. Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Feedback on secondary architecute promotion requirements draft
On 04/03/2012 08:21 AM, Peter Jones wrote: [snip] We need to make the whole process one with continuous feedback, or it's never going to work. So I'd expect that we don't want to specify anything all that precisely - I'd rather you come up with an implementation plan to satisfy each point, and then we (SA Maintainer and FESCo) decide together if it's satisfactory, and later decide that it has or hasn't yet been met, and if not what remedial steps should be taken. Communication is really the piece which needs development in the proposed guidelines. SA's tend to work quite independently so the proposal needs to spell out a few things that get everybody communicating at the right times and the right ways. It's probably perfectly clear in many people's minds folks how these things should be handled, but if we could formalize them a tiny bit it would do wonders for filling in what's missing in the secondary promotion draft. 1. What does the SA2PA proposal need to cover? MJG's 10 criteria give a general scope of what needs to be covered, so this is more or less done. If I'm reading Peter's comments above correctly the guidelines should indicate that the SA2PA proposal must be generated by the SA team (as opposed to FESCo) and should address all 10 points. 2. How should an SA team propose to FESCo and the community that their SA is ready to be evaluated for PA track? Is submitting a feature page the right way to start, or a discussion on f-d-l? Whatever the right way is I'd like to see that information added to the proposed guidelines. 3. When should the SA team make their first proposal? There is great potential for wasted effort bringing the topic up too early or too late in the SA's development, not to mention when in the primary release cycle such topics should be brought up. 4. How to keep FESCo and the community informed during the process. Presumably after #2 there will be feedback along the lines of you need to do more on points x, y, and z. If the answer is FESCo will say how to keep everybody informed then let's have the proposal state that. Basically, I think the guidelines MJG has put together are good principles; they just need some procedural blanks filled in so SA teams know how to apply them and communicate with the greater Fedora community. -- Brendan Conoboy / Red Hat, Inc. / b...@redhat.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File IO-Socket-SSL-1.66.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-IO-Socket-SSL: 0f104165ff7da7f46aa8d9c10ac61bdf IO-Socket-SSL-1.66.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
Fedora 18 schedule and Python 3.3
Do we have a schedule for Fedora 18 yet? I've started creating a feature page for getting Python 3.3 into Fedora: https://fedoraproject.org/wiki/Features/Python_3.3 but it's not clear to me yet how well the Python 3.3 upstream schedule lines up with Fedora's schedule. So for now I've simply used the Fedora 16 schedule, and offset the dates by a year (2011 - 2012). Based on that, Python 3.3 will probably be a Fedora 18 feature - though I don't think we can do any packaging work until 3.3 hits feature freeze (stabilizing the .pyc format and the .so ABI). Having said that there's plenty of work to be done getting our patches into upstream before it hits feature freeze! Hope this sounds sane Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 schedule and Python 3.3
Hi, I found http://fedoraproject.org/wiki/Releases/Schedule and there seems to be a relatively easy way to determine the Fedora 18 Release date. Tuesday before October 31st. So most probably Tuesday, 30th October 2012, if I am not mistaken. HTH Johannes On 04/16/2012 10:11 PM, David Malcolm wrote: Do we have a schedule for Fedora 18 yet? I've started creating a feature page for getting Python 3.3 into Fedora: https://fedoraproject.org/wiki/Features/Python_3.3 but it's not clear to me yet how well the Python 3.3 upstream schedule lines up with Fedora's schedule. So for now I've simply used the Fedora 16 schedule, and offset the dates by a year (2011 - 2012). Based on that, Python 3.3 will probably be a Fedora 18 feature - though I don't think we can do any packaging work until 3.3 hits feature freeze (stabilizing the .pyc format and the .so ABI). Having said that there's plenty of work to be done getting our patches into upstream before it hits feature freeze! Hope this sounds sane Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Feedback on secondary architecute promotion requirements draft
On Mon, Apr 16, 2012 at 01:41:58PM -0700, Brendan Conoboy wrote: Basically, I think the guidelines MJG has put together are good principles; they just need some procedural blanks filled in so SA teams know how to apply them and communicate with the greater Fedora community. I think a better way to think about this might be lie the packaging guidelines - they provide a set of technical constraints, but they don't tell you how to be part of the packaging community. I see SAs in the same kind of way. Secondary architecture maintainers should be active members of the greater Fedora community. You should be talking about what you're doing, providing regular status updates on devel@, actively involving yourself in other technical discussions to make sure that decisions aren't made without consideration of your constraints. Basically, behave as if you're a primary architecture. If you manage that then I think most of the problems you're worried about go away. It'll be obvious to everyone whether or not you're ready to be a primary architecture at any given point. Don't worry about the details. Just be part of Fedora. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 schedule and Python 3.3
On Mon, Apr 16, 2012 at 5:11 PM, David Malcolm dmalc...@redhat.com wrote: Do we have a schedule for Fedora 18 yet? Robyn is great at keeping the scedules updated -- they're typically in her directory on fedorapeople.org. Here are the key dates for F18: http://rbergero.fedorapeople.org/schedules/f-18/f-18-key-tasks.html -- Jared Smith -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 18 schedule and Python 3.3
On Mon, 2012-04-16 at 17:39 -0400, Jared K. Smith wrote: On Mon, Apr 16, 2012 at 5:11 PM, David Malcolm dmalc...@redhat.com wrote: Do we have a schedule for Fedora 18 yet? Robyn is great at keeping the scedules updated -- they're typically in her directory on fedorapeople.org. Here are the key dates for F18: http://rbergero.fedorapeople.org/schedules/f-18/f-18-key-tasks.html Aha! I was looking at the wiki, which seems to have pages of the form Releases/N/Schedule for 7 = N = 17, but not for N=18 yet. Thanks! I've updated the feature page [1] accordingly. (There's currently about a 1 month period between the upstream Python 3.3 feature freeze and F18 feature freeze) Dave [1] https://fedoraproject.org/wiki/Features/Python_3.3#Current_status -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
3.3.1-5.fc17.x86_64.debug power management and overheating issue
Hi, Is anyone else seeing issues with 3.3.1-5.fc17? My thinkpad X201 both overheats and shuts down: Apr 16 20:30:19 thinkpad kernel: [ 5508.559650] intel ips :00:1f.6: MCP limit exceeded: Avg temp 9572, limit 9000 Apr 16 20:30:24 thinkpad kernel: [ 5513.556695] intel ips :00:1f.6: MCP limit exceeded: Avg temp 9799, limit 9000 Apr 16 20:30:29 thinkpad kernel: [ 5518.553871] intel ips :00:1f.6: MCP limit exceeded: Avg temp 10069, limit 9000 Apr 16 20:30:34 thinkpad kernel: [ 5523.878334] Critical temperature reached (100 C), shutting down. Apr 16 20:30:34 thinkpad kernel: [ 5523.888383] Critical temperature reached (100 C), shutting down. Also, when i close the lid, the suspension icon keeps blinking and the laptop does not actualy suspend. Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: 3.3.1-5.fc17.x86_64.debug power management and overheating issue
Could be https://bugzilla.redhat.com/show_bug.cgi?id=675433 On Apr 16, 2012, at 6:41 PM, Paul Wouters wrote: Hi, Is anyone else seeing issues with 3.3.1-5.fc17? My thinkpad X201 both overheats and shuts down: Apr 16 20:30:19 thinkpad kernel: [ 5508.559650] intel ips :00:1f.6: MCP limit exceeded: Avg temp 9572, limit 9000 Apr 16 20:30:24 thinkpad kernel: [ 5513.556695] intel ips :00:1f.6: MCP limit exceeded: Avg temp 9799, limit 9000 Apr 16 20:30:29 thinkpad kernel: [ 5518.553871] intel ips :00:1f.6: MCP limit exceeded: Avg temp 10069, limit 9000 Apr 16 20:30:34 thinkpad kernel: [ 5523.878334] Critical temperature reached (100 C), shutting down. Apr 16 20:30:34 thinkpad kernel: [ 5523.888383] Critical temperature reached (100 C), shutting down. Also, when i close the lid, the suspension icon keeps blinking and the laptop does not actualy suspend. Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 810223] Circular build dependency in perl-HTTP-Message-6.03-1.fc18
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=810223 --- Comment #9 from Petr Pisar ppi...@redhat.com 2012-04-16 03:01:36 EDT --- Change 5501683d6bad7205ef78c6c4b842a2952842d2bd reverted in perl-HTML-Parser-3.69-4.fc18. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File Coro-6.08.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Coro: 86bcfac8bf53c9fe979106692b82b8b1 Coro-6.08.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-Coro] 6.08 bump
commit 0eb504a4d1943e6dd6e0ec4a769290a97351d062
Author: Petr Písař ppi...@redhat.com
Date: Mon Apr 16 09:02:13 2012 +0200
6.08 bump
.gitignore |1 +
perl-Coro.spec |7 +--
sources|2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index d2052a2..eedd555 100644
--- a/.gitignore
+++ b/.gitignore
@@ -7,3 +7,4 @@
/Coro-6.05.tar.gz
/Coro-6.06.tar.gz
/Coro-6.07.tar.gz
+/Coro-6.08.tar.gz
diff --git a/perl-Coro.spec b/perl-Coro.spec
index 1ef3555..485dc55 100644
--- a/perl-Coro.spec
+++ b/perl-Coro.spec
@@ -1,6 +1,6 @@
Name: perl-Coro
-Version:6.07
-Release:3%{?dist}
+Version:6.08
+Release:1%{?dist}
Summary:The only real threads in perl
License:GPL+ or Artistic
Group: Development/Libraries
@@ -125,6 +125,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Mon Apr 16 2012 Petr Pisar ppi...@redhat.com - 6.08-1
+- 6.08 bump
+
* Tue Feb 21 2012 Peter Robinson pbrobin...@fedoraproject.org - 6.07-3
- Add patch to fix build on ARM. RHBZ 750805
diff --git a/sources b/sources
index f59f24f..daa3a65 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-354dd4f058a30f085716010b771e27e9 Coro-6.07.tar.gz
+86bcfac8bf53c9fe979106692b82b8b1 Coro-6.08.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 812520] perl-Coro-6.08 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=812520 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Coro-6.08-1.fc18 Resolution||RAWHIDE Last Closed||2012-04-16 03:10:48 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Class-ISA/f16] (3 commits) ...Post-merge cleanup
Summary of changes: 1bbce4d... - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass (*) 87d9df7... Change description to something more descriptive (#811144) (*) 99ae3db... Post-merge cleanup (*) 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-Class-ISA/f16: 3/3] Post-merge cleanup
commit 99ae3db4376ba13a5862239dee4b926274d87648
Author: Petr Šabata con...@redhat.com
Date: Mon Apr 16 10:52:22 2012 +0200
Post-merge cleanup
perl-Class-ISA.spec |7 ++-
1 files changed, 2 insertions(+), 5 deletions(-)
---
diff --git a/perl-Class-ISA.spec b/perl-Class-ISA.spec
index 60d38bc..05d9b19 100644
--- a/perl-Class-ISA.spec
+++ b/perl-Class-ISA.spec
@@ -1,6 +1,6 @@
Name: perl-Class-ISA
Version:0.36
-Release:1007%{?dist}
+Release:1006%{?dist}
Summary:Report the search path for a class's ISA tree
License:GPL+ or Artistic
Group: Development/Libraries
@@ -37,13 +37,10 @@ make test
%{perl_vendorlib}/*
%changelog
-* Fri Apr 13 2012 Petr Šabata con...@redhat.com - 0.36-1007
+* Fri Apr 13 2012 Petr Šabata con...@redhat.com - 0.36-1006
- Change description to something more descriptive (#811144)
- Modernize spec
-* Fri Jan 13 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.36-1006
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild
-
* Fri Jun 17 2011 Marcela Mašláňová mmasl...@redhat.com - 0.36-1005
- Perl mass rebuild
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 811144] RPM description is not descriptive
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=811144 Petr Šabata psab...@redhat.com changed: What|Removed |Added Version|17 |16 --- Comment #8 from Petr Šabata psab...@redhat.com 2012-04-16 04:53:53 EDT --- (In reply to comment #7) Thanks. Unfortunately I noticed just now that I filed the bug against F17 instead of F16. Could this patch of uttermost importance be backported there as well? :-) I guess it could. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 811144] RPM description is not descriptive
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=811144 --- Comment #9 from Fedora Update System upda...@fedoraproject.org 2012-04-16 04:59:16 EDT --- perl-Class-ISA-0.36-1006.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/perl-Class-ISA-0.36-1006.fc16 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 810223] Circular build dependency in perl-HTTP-Message-6.03-1.fc18
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=810223 --- Comment #10 from Paul Howarth p...@city-fan.org 2012-04-16 06:14:58 EDT --- I'm really sorry about this but the BuildRequires: perl(HTTP::Headers) needs to be excluded from perl-HTML-Parser when bootstrapping (the Requires: is OK). perl-HTTP-Message always has a runtime dependency on perl-HTML-Parser and this creates a build-dep cycle. Again, really sorry about messing you about here. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 746941] perl-Mojolicious-2.81 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=746941 Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org changed: What|Removed |Added Summary|perl-Mojolicious-2.80 is|perl-Mojolicious-2.81 is |available |available --- Comment #52 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org 2012-04-16 06:40:28 EDT --- Latest upstream release: 2.81 Current version in Fedora Rawhide: 2.70 URL: http://search.cpan.org/dist/Mojolicious/ 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 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 812822] New: perl-Test-Moose-More-0.008 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-Test-Moose-More-0.008 is available https://bugzilla.redhat.com/show_bug.cgi?id=812822 Summary: perl-Test-Moose-More-0.008 is available Product: Fedora Version: rawhide Platform: Unspecified OS/Version: Unspecified Status: NEW Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Component: perl-Test-Moose-More AssignedTo: ppi...@redhat.com ReportedBy: upstream-release-monitor...@fedoraproject.org QAContact: extras...@fedoraproject.org CC: fedora-perl-devel-l...@redhat.com, mmasl...@redhat.com, ppi...@redhat.com Classification: Fedora Story Points: --- Type: --- Regression: --- Mount Type: --- Documentation: --- Latest upstream release: 0.008 Current version in Fedora Rawhide: 0.007 URL: http://search.cpan.org/dist/Test-Moose-More/ 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 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Sys-Virt/f17] Update to 0.9.11 release
Summary of changes: 3b4ca40... Update to 0.9.11 release (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 810223] Circular build dependency in perl-HTTP-Message-6.03-1.fc18
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=810223 --- Comment #11 from Petr Pisar ppi...@redhat.com 2012-04-16 09:11:24 EDT --- I removed the build-dependency only in perl-HTML-Parser-3.69-5.fc18. Please make sure none of the two packages will be needed for building other packages (even transitively) during the bootstrap. Because now you can build both of them, but you cannot use any of them (the run-time dependencies will be unsatisfied). -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File Test-Moose-More-0.008.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Test-Moose-More: db5052fcdaa2238220dcd148b66ef68f Test-Moose-More-0.008.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-Moose-More] 0.008 bump
commit 2d3f3a37f630867eddfa188e4a130f3dd9188e95
Author: Petr Písař ppi...@redhat.com
Date: Mon Apr 16 15:23:27 2012 +0200
0.008 bump
.gitignore|1 +
perl-Test-Moose-More.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index fdfeb95..aceddd1 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
/Test-Moose-More-0.005.tar.gz
/Test-Moose-More-0.006.tar.gz
/Test-Moose-More-0.007.tar.gz
+/Test-Moose-More-0.008.tar.gz
diff --git a/perl-Test-Moose-More.spec b/perl-Test-Moose-More.spec
index 7d77d98..883f57c 100644
--- a/perl-Test-Moose-More.spec
+++ b/perl-Test-Moose-More.spec
@@ -1,5 +1,5 @@
Name: perl-Test-Moose-More
-Version:0.007
+Version:0.008
Release:1%{?dist}
Summary:More tools for testing Moose packages
License:LGPLv2+
@@ -58,6 +58,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Mon Apr 16 2012 Petr Pisar ppi...@redhat.com - 0.008-1
+- 0.008 bump
+
* Thu Apr 12 2012 Petr Pisar ppi...@redhat.com - 0.007-1
- 0.007 bump
diff --git a/sources b/sources
index b5a382b..80d467f 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-7730d76df37ea8c86d08707f453a3e73 Test-Moose-More-0.007.tar.gz
+db5052fcdaa2238220dcd148b66ef68f Test-Moose-More-0.008.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 812822] perl-Test-Moose-More-0.008 is available
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=812822 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Test-Moose-More-0.008- ||1.fc18 Resolution||RAWHIDE Last Closed||2012-04-16 09:46:07 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 810223] Circular build dependency in perl-HTTP-Message-6.03-1.fc18
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=810223 --- Comment #12 from Paul Howarth p...@city-fan.org 2012-04-16 09:44:31 EDT --- (In reply to comment #11) I removed the build-dependency only in perl-HTML-Parser-3.69-5.fc18. Thanks. Please make sure none of the two packages will be needed for building other packages (even transitively) during the bootstrap. Because now you can build both of them, but you cannot use any of them (the run-time dependencies will be unsatisfied). Why do you say that? Once they are both built, they are both installable, are they not? perl-HTML-Parser is very low down in the build dependency hierarchy, and if it was uninstallable then it would impact the build of 772 other packages, which either build-require it or some other package that build-requires/requires it. The build order as I see it at the moment is available here: http://www.city-fan.org/~paul/perl-boot/buildorder perl-HTML-Parser can be built in the 2nd pass and perl-HTTP-Message can be built in the 3rd pass, so they should both be usable for builds from the 4th pass onwards (where packages in pass N have at least one build dependency [or runtime dependency of one] built in the previous pass and all packages in a given pass can be built in parallel as they have no dependencies on each other). I described the boot process as I understand it in an email to the perl-devel list last week: http://lists.fedoraproject.org/pipermail/perl-devel/2012-April/050071.html -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 810223] Circular build dependency in perl-HTTP-Message-6.03-1.fc18
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=810223 --- Comment #13 from Petr Pisar ppi...@redhat.com 2012-04-16 09:55:42 EDT --- Provided you will maintain decomposition of rebuilds into passes to minimize incoherent states as much as possible, then you are right. I pointed just the fact. Obviously I forgot the state where both packages have been already rebuilt. My apology. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-RPM2
perl-RPM2 has broken dependencies in the rawhide tree: On x86_64: perl-RPM2-1.0-2.fc17.x86_64 requires librpmio.so.2()(64bit) perl-RPM2-1.0-2.fc17.x86_64 requires librpm.so.2()(64bit) On i386: perl-RPM2-1.0-2.fc17.i686 requires librpmio.so.2 perl-RPM2-1.0-2.fc17.i686 requires librpm.so.2 Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 810510] Circular build dependency in perl-DateTime-0.70-3.fc18
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=810510 Paul Howarth p...@city-fan.org changed: What|Removed |Added Status|NEW |CLOSED Resolution||NOTABUG Last Closed||2012-04-16 13:46:44 --- Comment #3 from Paul Howarth p...@city-fan.org 2012-04-16 13:46:44 EDT --- It turns out that the only package built during the bootstrap phase that pulls in DT::TZ but not DT is perl-DateTime itself, so there's no issue here. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File IO-Socket-SSL-1.65.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-IO-Socket-SSL: f8bc9c35f00aba116e32839db321fcce IO-Socket-SSL-1.65.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Update to 1.65
commit f7be3459a3c2815008ad86c7455d5f81f9515587
Author: Paul Howarth p...@city-fan.org
Date: Mon Apr 16 21:13:12 2012 +0100
Update to 1.65
- New upstream release 1.65
- Added NPN (Next Protocol Negotiation) support (CPAN RT#76223)
perl-IO-Socket-SSL.spec |6 +-
sources |2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/perl-IO-Socket-SSL.spec b/perl-IO-Socket-SSL.spec
index 06d7d93..29ce60e 100644
--- a/perl-IO-Socket-SSL.spec
+++ b/perl-IO-Socket-SSL.spec
@@ -1,5 +1,5 @@
Name: perl-IO-Socket-SSL
-Version: 1.64
+Version: 1.65
Release: 1%{?dist}
Summary: Perl library for transparent SSL
Group: Development/Libraries
@@ -54,6 +54,10 @@ rm -rf %{buildroot}
%{_mandir}/man3/IO::Socket::SSL.3pm*
%changelog
+* Mon Apr 16 2012 Paul Howarth p...@city-fan.org - 1.65-1
+- Update to 1.65
+ - added NPN (Next Protocol Negotiation) support (CPAN RT#76223)
+
* Sat Apr 7 2012 Paul Howarth p...@city-fan.org - 1.64-1
- Update to 1.64
- ignore die from within eval to make tests more stable on Win32
diff --git a/sources b/sources
index c134b78..4db7d42 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-1759c2195631fd59429761a3b512e931 IO-Socket-SSL-1.64.tar.gz
+f8bc9c35f00aba116e32839db321fcce IO-Socket-SSL-1.65.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL/f17] (2 commits) ...Update to 1.65
Summary of changes: 126ee08... Update to 1.64 (*) f7be345... Update to 1.65 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Created tag perl-IO-Socket-SSL-1.65-1.fc18
The lightweight tag 'perl-IO-Socket-SSL-1.65-1.fc18' was created pointing to: f7be345... Update to 1.65 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Created tag perl-IO-Socket-SSL-1.65-1.fc17
The lightweight tag 'perl-IO-Socket-SSL-1.65-1.fc17' was created pointing to: f7be345... Update to 1.65 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Update to 1.66
commit 04cfd057efd74aa5a629e442192935fbd5d67ab9
Author: Paul Howarth p...@city-fan.org
Date: Mon Apr 16 21:55:37 2012 +0100
Update to 1.66
- New upstream release 1.66
- Make it thread safer (CPAN RT#76538)
perl-IO-Socket-SSL.spec |6 +-
sources |2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/perl-IO-Socket-SSL.spec b/perl-IO-Socket-SSL.spec
index 29ce60e..94f5b08 100644
--- a/perl-IO-Socket-SSL.spec
+++ b/perl-IO-Socket-SSL.spec
@@ -1,5 +1,5 @@
Name: perl-IO-Socket-SSL
-Version: 1.65
+Version: 1.66
Release: 1%{?dist}
Summary: Perl library for transparent SSL
Group: Development/Libraries
@@ -54,6 +54,10 @@ rm -rf %{buildroot}
%{_mandir}/man3/IO::Socket::SSL.3pm*
%changelog
+* Mon Apr 16 2012 Paul Howarth p...@city-fan.org - 1.66-1
+- Update to 1.66
+ - make it thread safer (CPAN RT#76538)
+
* Mon Apr 16 2012 Paul Howarth p...@city-fan.org - 1.65-1
- Update to 1.65
- added NPN (Next Protocol Negotiation) support (CPAN RT#76223)
diff --git a/sources b/sources
index 4db7d42..c57e02c 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-f8bc9c35f00aba116e32839db321fcce IO-Socket-SSL-1.65.tar.gz
+0f104165ff7da7f46aa8d9c10ac61bdf IO-Socket-SSL-1.66.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL/f17] Update to 1.66
Summary of changes: 04cfd05... Update to 1.66 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Created tag perl-IO-Socket-SSL-1.66-1.fc17
The lightweight tag 'perl-IO-Socket-SSL-1.66-1.fc17' was created pointing to: 04cfd05... Update to 1.66 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-IO-Socket-SSL] Created tag perl-IO-Socket-SSL-1.66-1.fc18
The lightweight tag 'perl-IO-Socket-SSL-1.66-1.fc18' was created pointing to: 04cfd05... Update to 1.66 -- 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 Mail-IMAPClient-3.31.tar.gz uploaded to lookaside cache by nb
A file has been added to the lookaside cache for perl-Mail-IMAPClient: 48242ae8c0479611b5c84d4aa2b52d7c Mail-IMAPClient-3.31.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-Mail-IMAPClient] Upgrade to 3.31
commit b5acc38171e66b464e2bc73fb55e10b975fcb618
Author: Nick Bebout n...@fedoraproject.org
Date: Mon Apr 16 22:57:55 2012 -0500
Upgrade to 3.31
.gitignore|1 +
perl-Mail-IMAPClient.spec |7 +--
sources |2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index c4be2b4..f09cd8c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@ Mail-IMAPClient-3.25.tar.gz
/Mail-IMAPClient-3.27.tar.gz
/Mail-IMAPClient-3.28.tar.gz
/Mail-IMAPClient-3.30.tar.gz
+/Mail-IMAPClient-3.31.tar.gz
diff --git a/perl-Mail-IMAPClient.spec b/perl-Mail-IMAPClient.spec
index 08035bf..6542fdd 100644
--- a/perl-Mail-IMAPClient.spec
+++ b/perl-Mail-IMAPClient.spec
@@ -1,6 +1,6 @@
Name: perl-Mail-IMAPClient
-Version:3.30
-Release:2%{?dist}
+Version:3.31
+Release:1%{?dist}
Summary:An IMAP Client API
Group: Development/Libraries
License:GPL+ or Artistic
@@ -52,6 +52,9 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man3/*.3*
%changelog
+* Mon Apr 16 2012 Nick Bebout n...@fedoraproject.org - 3.31-1
+- Upgrade to 3.31
+
* Fri Jan 13 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 3.30-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild
diff --git a/sources b/sources
index ee6cb17..eac44e7 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-a1965d99f1e25bab580e19e6546f433d Mail-IMAPClient-3.30.tar.gz
+48242ae8c0479611b5c84d4aa2b52d7c Mail-IMAPClient-3.31.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-Mail-IMAPClient/f16] (2 commits) ...Upgrade to 3.31
Summary of changes: fe99ce2... - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass (*) b5acc38... Upgrade to 3.31 (*) (*) 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-Mail-IMAPClient/f15] (2 commits) ...Upgrade to 3.31
Summary of changes: fe99ce2... - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass (*) b5acc38... Upgrade to 3.31 (*) (*) 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-Mail-IMAPClient/el6] (3 commits) ...Merge branch 'master' into el6
Summary of changes: fe99ce2... - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass (*) b5acc38... Upgrade to 3.31 (*) 5e5a830... Merge branch 'master' into el6 (*) 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-Mail-IMAPClient/el6: 3/3] Merge branch 'master' into el6
commit 5e5a830d21d9ce6c1c2f3f49dfd1ecb3154834d1 Merge: c5a13ff b5acc38 Author: Nick Bebout n...@fedoraproject.org Date: Mon Apr 16 22:59:29 2012 -0500 Merge branch 'master' into el6 .gitignore|1 + perl-Mail-IMAPClient.spec |8 +++- sources |2 +- 3 files changed, 9 insertions(+), 2 deletions(-) --- -- 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-Mail-IMAPClient/el5] (3 commits) ...Merge branch 'master' into el5
Summary of changes: fe99ce2... - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass (*) b5acc38... Upgrade to 3.31 (*) 1afff74... Merge branch 'master' into el5 (*) 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-Mail-IMAPClient/el5: 3/3] Merge branch 'master' into el5
commit 1afff74dfb456c4b8b652e96ad2260956b4e5e30 Merge: 5d1e560 b5acc38 Author: Nick Bebout n...@fedoraproject.org Date: Mon Apr 16 22:59:42 2012 -0500 Merge branch 'master' into el5 .gitignore|1 + perl-Mail-IMAPClient.spec |8 +++- sources |2 +- 3 files changed, 9 insertions(+), 2 deletions(-) --- -- 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-Mail-IMAPClient/el4] (3 commits) ...Merge branch 'master' into el4
Summary of changes: fe99ce2... - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass (*) b5acc38... Upgrade to 3.31 (*) 5de1841... Merge branch 'master' into el4 (*) 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-Mail-IMAPClient/el4: 3/3] Merge branch 'master' into el4
commit 5de1841ea00c323e51f97b65ecd94ba7556a104e Merge: 4be9b98 b5acc38 Author: Nick Bebout n...@fedoraproject.org Date: Mon Apr 16 22:59:54 2012 -0500 Merge branch 'master' into el4 .gitignore|1 + perl-Mail-IMAPClient.spec |8 +++- sources |2 +- 3 files changed, 9 insertions(+), 2 deletions(-) --- diff --cc .gitignore index bb657ff,f09cd8c..bb3beea --- a/.gitignore +++ b/.gitignore @@@ -1,2 -1,5 +1,3 @@@ -Mail-IMAPClient-3.25.tar.gz -/Mail-IMAPClient-3.27.tar.gz /Mail-IMAPClient-3.28.tar.gz /Mail-IMAPClient-3.30.tar.gz + /Mail-IMAPClient-3.31.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
