[Bug 592101] pls upgrade
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=592101 Peter Lemenkov lemen...@gmail.com changed: What|Removed |Added Status|NEW |ASSIGNED -- 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. ___ ocaml-devel mailing list ocaml-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ocaml-devel
Re: orphaning Calibre
ok. Thats 3 of us... Ionuț: Could you mail us any info about the current state of the package or any gotchas? Thanks for picking this up, guys! The latest issue was figuring out a way to unbundle the modified pychm that calibre was shipping. That was in calibre 0.6.46. There's a 0.6.47 in -devel with other improvements. Other than that (and if they haven't added any more bundled libs since), the other problems should be documented in their respective tickets. Also the relationship that we (and other distributors) have with upstream could be improved. Right now, they're not really interested in making things standards-compliant or license-abiding or library-unbundling ;) [1][2] There's also the somewhat delicate problem of calibre requiring the unfree libunrar for a little part of its functionality, namely CBR file support. [1] http://bugs.calibre-ebook.com/ticket/4715#comment:9 [2] http://bugs.calibre-ebook.com/ticket/3832 - Ionuț -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: PackageKit need to be more intelligent!
On Wednesday 12 May 2010 23:24:13 Seth Vidal wrote: On Wed, 12 May 2010, Guido Grazioli wrote: 2010/5/12 Rahul Sundaram methe...@gmail.com: The search box has a icon on the left side which defaults to searching the name rather than description. It is probably too subtle to notice. I bet that is the problem here. Rahul Having an additional option in that context menu, which makes the search mimic the applications search implemented in latest pkgdb, would be a very nice feature indeed. yum can search an additional keywords database if it is in the metadata. This thread is more about UI frontend - it makes sense to list relevant results for end users. Devel packages for example are not. But I don't use any package management software so maybe it's already there. Yum and CLI rulez :D Jaroslav We added support for that in f13. -sv -- Jaroslav Řezník jrez...@redhat.com Software Engineer - Base Operating Systems Brno Office: +420 532 294 275 Mobile: +420 602 797 774 Red Hat, Inc. http://cz.redhat.com/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: PackageKit need to be more intelligent!
On Wednesday 12 May 2010 23:29:30 Chris Lumens wrote: users do not need to find devel packages from the PackageKit GUI, we need to search useful packages from here, that is my opinion... This line of thinking needs to stop. Developers are users, too, and development packages ending up in the search results is not such a bad thing. Those packages *are* useful to people, just not the people you have in mind. Developers are usually smart enough to filter results to fit their needs, end users are usually not able to do it. I'm not against smart defaults even these defaults does not fit my needs as for me it's really easy to setup my system to match my heart (do I have heart? ;-). Jaroslav - Chris -- Jaroslav Řezník jrez...@redhat.com Software Engineer - Base Operating Systems Brno Office: +420 532 294 275 Mobile: +420 602 797 774 Red Hat, Inc. http://cz.redhat.com/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Sending a sensible email. (was: PackageKit need to be more intelligent!)
On 12 May 2010 21:58, João Neto joao.gsn...@gmail.com wrote: The system package manager for Fedora to be smarter ... This is a general point I'm making, not just about your email in particular. There appears to be a trend on this list where a random user just posts an inflammatory email with ACME SOFTWARE IS RUBBISH. Now, if the maintainer of that software is scanning the email list, bear in mind he (or she) has likely spent a significant amount of time and energy getting the software into the state you see it now. They probably spend evenings and weekend closing duplicate bugs and fixing trivial typos that people notice. If you title an email with such rubbish then the maintainer is simply going to ignore it or spam it. I'll explain why: The way open source software works is you get the software for free. If you don't like it, you get your money back. If you want an additional feature, or a bug fixing really fast you either pay a Linux company like Red Hat or Suse some money and they assign a developer to work on it. If it's a big feature it's going to cost lots of money. The other way is to join the software mailing list, and suggest the new feature, and sell it to the maintainer. This means explaining what you think the benefits are, and what you think needs to be done. Bear in mind, that if most maintainers are like me, then they work on lots of different projects, only with a finite amount of time to work on each one. If you supply a patch, even if wrong, it shows you're willing to help and the maintainer has to worry less about the development overhead. If you state you're willing to test the feature with the development version, then the maintainer is even more likely to choose your feature over someone elses. Every line of code added is a development maintenance overhead, and the software maintainer will be aware of that. Now, what you're asking for in your email we are working on. It's called app-install, but needs lots of help from the Fedora infrastructure people to actually make it happen. I'm hoping we can get the infrastructure in place for F14. The way Fedora is fundamentally different from Ubuntu (in my experience) is that Ubuntu is perfectly willing to bodge some code on top of an Ubuntu only project which is stuck together with sticky-tape and string. The way I, as part of Fedora, work is that I design projects and code that can be shared with other distributions so we can all work together. But it takes longer, much longer. But in the long run, it's the correct thing to do. I know that Fedora will be a nicer place to be in five years time, because we're sharing code with the other distros and working upstream. So you can appreciate a developer getting annoyed when what he wrote is called rubbish when compared with the Ubuntu $bodge_of_the_day. Now, please don't take this email as a rebuke, just please be aware that to make changes you have to follow the processes, not just rubbish software on public mailing lists. Thanks, Richard. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Preupgrade F12-F13 error
- Clovis Tristao clo...@agr.unicamp.br wrote: How do I increase size the boot partition, with LVM? My partition: FilesystemSize Used Avail Use% Mounted on /dev/sda1 190M 39M 142M 22% /boot Can anyone help? Thanks a lot, Clóvis I think the easiest way is to simply download F13 DVD and do standard upgrade. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20100513 changes
Compose started at Thu May 13 08:15:05 UTC 2010 Broken deps for i386 -- almanah-0.7.2-1.fc13.i686 requires libedataserver-1.2.so.11 almanah-0.7.2-1.fc13.i686 requires libedataserverui-1.2.so.8 anjal-0.3.2-2.fc14.i686 requires libedataserver-1.2.so.11 anjal-0.3.2-2.fc14.i686 requires libcamel-1.2.so.14 anjal-0.3.2-2.fc14.i686 requires libcamel-provider-1.2.so.14 anjal-0.3.2-2.fc14.i686 requires libedataserverui-1.2.so.8 clutter-gtkmm-0.9.4-3.fc12.i686 requires libcluttermm-0.9.so.3 clutter-gtkmm-devel-0.9.4-3.fc12.i686 requires pkgconfig(cluttermm-0.9) dates-0.4.11-3.fc14.i686 requires libedataserver-1.2.so.11 evolution-couchdb-0.3.2-2.fc13.i686 requires libcamel-provider-1.2.so.14 evolution-couchdb-0.3.2-2.fc13.i686 requires libcamel-1.2.so.14 evolution-couchdb-0.3.2-2.fc13.i686 requires libedataserver-1.2.so.11 evolution-couchdb-0.3.2-2.fc13.i686 requires libcouchdb-glib-1.0.so.1 glabels-2.2.7-1.fc14.i686 requires libedataserver-1.2.so.11 gnome-launch-box-0.4-17.fc13.i686 requires libedataserver-1.2.so.11 gnome-phone-manager-0.65-5.fc12.i686 requires libedataserver-1.2.so.11 gnome-phone-manager-telepathy-0.65-5.fc12.i686 requires libedataserver-1.2.so.11 qtgpsc-0.2.3-6.fc12.i686 requires libgps.so.18 rubygem-right_aws-1.10.0-3.fc14.noarch requires rubygem(right-http_connection) = 0:1.2.4 vfrnav-0.4-1.fc13.i686 requires libgps.so.18 vifir-0.4-2.fc14.i686 requires libgps.so.18 viking-0.9.91-3.fc13.i686 requires libgps.so.18 Broken deps for x86_64 -- almanah-0.7.2-1.fc13.x86_64 requires libedataserverui-1.2.so.8()(64bit) almanah-0.7.2-1.fc13.x86_64 requires libedataserver-1.2.so.11()(64bit) anjal-0.3.2-2.fc14.x86_64 requires libcamel-provider-1.2.so.14()(64bit) anjal-0.3.2-2.fc14.x86_64 requires libedataserverui-1.2.so.8()(64bit) anjal-0.3.2-2.fc14.x86_64 requires libcamel-1.2.so.14()(64bit) anjal-0.3.2-2.fc14.x86_64 requires libedataserver-1.2.so.11()(64bit) clutter-gtkmm-0.9.4-3.fc12.i686 requires libcluttermm-0.9.so.3 clutter-gtkmm-0.9.4-3.fc12.x86_64 requires libcluttermm-0.9.so.3()(64bit) clutter-gtkmm-devel-0.9.4-3.fc12.i686 requires pkgconfig(cluttermm-0.9) clutter-gtkmm-devel-0.9.4-3.fc12.x86_64 requires pkgconfig(cluttermm-0.9) dates-0.4.11-3.fc14.x86_64 requires libedataserver-1.2.so.11()(64bit) evolution-couchdb-0.3.2-2.fc13.x86_64 requires libcamel-provider-1.2.so.14()(64bit) evolution-couchdb-0.3.2-2.fc13.x86_64 requires libcouchdb-glib-1.0.so.1()(64bit) evolution-couchdb-0.3.2-2.fc13.x86_64 requires libcamel-1.2.so.14()(64bit) evolution-couchdb-0.3.2-2.fc13.x86_64 requires libedataserver-1.2.so.11()(64bit) glabels-2.2.7-1.fc14.x86_64 requires libedataserver-1.2.so.11()(64bit) gnome-launch-box-0.4-17.fc13.x86_64 requires libedataserver-1.2.so.11()(64bit) gnome-phone-manager-0.65-5.fc12.x86_64 requires libedataserver-1.2.so.11()(64bit) gnome-phone-manager-telepathy-0.65-5.fc12.x86_64 requires libedataserver-1.2.so.11()(64bit) qtgpsc-0.2.3-6.fc12.x86_64 requires libgps.so.18()(64bit) rubygem-right_aws-1.10.0-3.fc14.noarch requires rubygem(right-http_connection) = 0:1.2.4 vfrnav-0.4-1.fc13.x86_64 requires libgps.so.18()(64bit) vifir-0.4-2.fc14.x86_64 requires libgps.so.18()(64bit) viking-0.9.91-3.fc13.x86_64 requires libgps.so.18()(64bit) New package R-statmod Statistical modeling New package R-xtable Export tables to LaTeX or HTML New package bsp The most popular node builder for Doom New package emacs-color-theme Color themes for Emacs New package perl-HTTP-Lite Lightweight HTTP implementation New package php-pear-HTML-Template-IT Integrated Templates New package php-swift-Swift Free Feature-rich PHP Mailer New package python-bunch Python dictionary with attribute-style access Updated Packages: dialog-1.1-11.20100428.fc14 --- * Wed May 12 2010 Miroslav Lichvar mlich...@redhat.com - 1.1-11.20100428 - update to 1.1-20100428 gnutls-2.8.6-1.fc14 --- * Wed May 12 2010 Tomas Mraz tm...@redhat.com 2.8.6-1 - upgrade to a new upstream version gutenprint-5.2.5-7.fc14 --- * Wed May 12 2010 Jiri Popelka jpope...@redhat.com 5.2.5-7 - Added IEEE 1284 Device ID for: Epson Stylus Photo 1400 (bug #577299). Epson Stylus Photo 830U (bug #577307). HP DeskJet 959C (bug #577291). * Thu Mar 25 2010 Tim Waugh twa...@redhat.com 5.2.5-6 - Added IEEE 1284 Device ID for Epson Stylus Photo R230 (from Ubuntu #520466). hplip-3.10.2-16.fc14 * Wed May 12 2010 Jiri Popelka
[Test-Announce] Fedora 13 Final RC3 Available Now!
Fedora 13 Final RC3 is now available [1], with changes from RC2 in NetworkManager, anaconda, pino, and shotwell [2]. Please refer to the following pages for download links and testing instructions. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha, Beta, and Final priority test cases for installation [3] and desktop [4] should pass in order to meet the Final Release Criteria [5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the test list [7]. [1] http://poelstra.fedorapeople.org/schedules/f-13/f-13-quality-tasks.html [2] https://fedorahosted.org/rel-eng/ticket/3652#comment:5 [3] https://fedoraproject.org/wiki/QA:Installation_validation_testing [4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [5] https://fedoraproject.org/wiki/Fedora_13_Final_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
rpms/perl-Test-WWW-Mechanize/devel .cvsignore, 1.8, 1.9 perl-Test-WWW-Mechanize.spec, 1.14, 1.15 sources, 1.8, 1.9
Author: mmaslano Update of /cvs/pkgs/rpms/perl-Test-WWW-Mechanize/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv27706 Modified Files: .cvsignore perl-Test-WWW-Mechanize.spec sources Log Message: * Thu May 13 2010 Petr Pisar ppi...@redhat.com - 1.28-1 - Version bump - Sort dependencies Index: .cvsignore === RCS file: /cvs/pkgs/rpms/perl-Test-WWW-Mechanize/devel/.cvsignore,v retrieving revision 1.8 retrieving revision 1.9 diff -u -p -r1.8 -r1.9 --- .cvsignore 20 Feb 2009 04:17:50 - 1.8 +++ .cvsignore 13 May 2010 12:11:56 - 1.9 @@ -1 +1 @@ -Test-WWW-Mechanize-1.24.tar.gz +Test-WWW-Mechanize-1.28.tar.gz Index: perl-Test-WWW-Mechanize.spec === RCS file: /cvs/pkgs/rpms/perl-Test-WWW-Mechanize/devel/perl-Test-WWW-Mechanize.spec,v retrieving revision 1.14 retrieving revision 1.15 diff -u -p -r1.14 -r1.15 --- perl-Test-WWW-Mechanize.spec7 May 2010 00:01:31 - 1.14 +++ perl-Test-WWW-Mechanize.spec13 May 2010 12:11:56 - 1.15 @@ -1,6 +1,6 @@ Name: perl-Test-WWW-Mechanize -Version:1.24 -Release:6%{?dist} +Version:1.28 +Release:1%{?dist} Summary:Testing-specific WWW::Mechanize subclass Group: Development/Libraries @@ -12,18 +12,17 @@ BuildRoot: %{_tmppath}/%{name}-%{ve BuildArch: noarch Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo $version)) -BuildRequires: perl(Test::More) +BuildRequires: perl(Carp::Assert::More) BuildRequires: perl(ExtUtils::MakeMaker) -BuildRequires: perl(WWW::Mechanize) = 1.24 +BuildRequires: perl(HTML::Lint) +BuildRequires: perl(HTTP::Server::Simple) = 0.07 BuildRequires: perl(Test::Builder::Tester) = 1.09 -BuildRequires: perl(Test::LongString) = 0.07 -BuildRequires: perl(Test::Pod), perl(Test::Pod::Coverage) +BuildRequires: perl(Test::LongString) = 0.12 +BuildRequires: perl(Test::More) +BuildRequires: perl(Test::Pod) = 0.08 +BuildRequires: perl(Test::Pod::Coverage) = 1.00 BuildRequires: perl(URI::file) -BuildRequires: perl(Carp::Assert::More) -BuildRequires: perl(HTTP::Server::Simple) = 0.07 - -# For improved testing -BuildRequires: perl(HTML::Lint) +BuildRequires: perl(WWW::Mechanize) = 1.24 %description Test::WWW::Mechanize is a subclass of WWW::Mechanize that incorporates @@ -48,6 +47,8 @@ find $RPM_BUILD_ROOT -depth -type d -exe %check +# network test died +rm -rf t/put_ok.t make test @@ -63,6 +64,10 @@ rm -rf $RPM_BUILD_ROOT %changelog +* Thu May 13 2010 Petr Pisar ppi...@redhat.com - 1.28-1 +- Version bump +- Sort dependencies + * Fri May 07 2010 Marcela Maslanova mmasl...@redhat.com - 1.24-6 - Mass rebuild with perl-5.12.0 Index: sources === RCS file: /cvs/pkgs/rpms/perl-Test-WWW-Mechanize/devel/sources,v retrieving revision 1.8 retrieving revision 1.9 diff -u -p -r1.8 -r1.9 --- sources 20 Feb 2009 04:17:50 - 1.8 +++ sources 13 May 2010 12:11:56 - 1.9 @@ -1 +1 @@ -40a7f3c1937fbcccaa07ef5473201514 Test-WWW-Mechanize-1.24.tar.gz +6f4b87f8502cf5096be8b03ae5b76d86 Test-WWW-Mechanize-1.28.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
ABRT duplicate detection - is it for real?
I'm getting the same bug reports over and over again, for example https://bugzilla.redhat.com/show_bug.cgi?id=542393 Shouldn't ABRT catch the duplicates? AFAIK abrt recognizes dupes based on hashes of the backtrace, but the format of the backtraces has changed with nearly every new ABRT version, so the backtraces will not be the same even from exactly the same crash. How to deal with that problem? And what about more complicated cases, for example a backtrace where the commandline is different as in /usr/bin/program /home/user/some.file. As user and filename change, the hash cannot be the same. Regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File Tk-804.028_503.tar.gz uploaded to lookaside cache by mmaslano
A file has been added to the lookaside cache for perl-Tk: 8ec3e456ca0eadd685a574e943d3d9ce Tk-804.028_503.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
rpms/perl-Tk/devel .cvsignore, 1.3, 1.4 perl-Tk.spec, 1.22, 1.23 sources, 1.3, 1.4 perl-Tk-XIM.patch, 1.1, NONE perl-Tk-events.patch, 1.1, NONE perl-Tk-getOpenFile.patch, 1.1, NONE perl-Tk-gif.patch,
Author: mmaslano Update of /cvs/pkgs/rpms/perl-Tk/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv24164 Modified Files: .cvsignore perl-Tk.spec sources Removed Files: perl-Tk-XIM.patch perl-Tk-events.patch perl-Tk-getOpenFile.patch perl-Tk-gif.patch Log Message: * Fri May 07 2010 Marcela Maslanova mmasl...@redhat.com - 804.028-12 - Mass rebuild with perl-5.12.0 update to development release Index: .cvsignore === RCS file: /cvs/pkgs/rpms/perl-Tk/devel/.cvsignore,v retrieving revision 1.3 retrieving revision 1.4 diff -u -p -r1.3 -r1.4 --- .cvsignore 2 Jan 2008 13:04:53 - 1.3 +++ .cvsignore 13 May 2010 12:56:23 - 1.4 @@ -1 +1 @@ -Tk-804.028.tar.gz +Tk-804.028_503.tar.gz Index: perl-Tk.spec === RCS file: /cvs/pkgs/rpms/perl-Tk/devel/perl-Tk.spec,v retrieving revision 1.22 retrieving revision 1.23 diff -u -p -r1.22 -r1.23 --- perl-Tk.spec7 May 2010 06:16:12 - 1.22 +++ perl-Tk.spec13 May 2010 12:56:23 - 1.23 @@ -2,6 +2,8 @@ %define perlver %(eval `%{__perl} -V:version`; echo $version) Name: perl-Tk +# devel version fix for perl 5.12: +%define real_version 804.028_503 Version:804.028 Release:12%{?dist} Summary:Perl Graphical User Interface ToolKit @@ -9,24 +11,12 @@ Summary:Perl Graphical User Inte Group: Development/Libraries License:GPL+ or Artistic URL:http://search.cpan.org/dist/Tk/ -Source0:http://cpan.org/modules/by-module/Tk/Tk-804.028.tar.gz +Source0:http://cpan.org/modules/by-module/Tk/Tk-%{real_version}.tar.gz Patch0: perl-Tk-widget.patch # modified version of http://ftp.de.debian.org/debian/pool/main/p/perl-tk/perl-tk_804.027-8.diff.gz Patch1: perl-Tk-debian.patch.gz # fix segfaults as in #235666 because of broken cashing code Patch2: perl-Tk-seg.patch -# fix interaction with XIM, bug #489228, upstream change r12589 -Patch3:perl-Tk-XIM.patch -# fix for bugs #491536 #489228 #506496 (see comment #8) -# see http://rt.cpan.org/Public/Bug/Display.html?id=38746 -Patch4:perl-Tk-events.patch -# fix for bug #487122 -# see http://rt.cpan.org/Public/Bug/Display.html?id=31989 -Patch5: perl-Tk-getOpenFile.patch - -# fix gif overflow in tk see CVE-2006-4484 and CVE-2007-6697 or #431518 and -# #431529 -Patch100: perl-Tk-gif.patch BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) @@ -52,7 +42,7 @@ Perl API is essentially the same as Tk80 been verified as compliant. There ARE differences see pod/804delta.pod. %prep -%setup -q -n Tk-%{version} +%setup -q -n Tk-%{real_version} find . -type f -exec %{__perl} -pi -e \ 's,^(#!)(/usr/local)?/bin/perl\b,$1%{__perl}, if ($. == 1)' {} \; chmod -x pod/Popup.pod Tixish/lib/Tk/balArrow.xbm @@ -65,10 +55,6 @@ chmod -x pod/Popup.pod Tixish/lib/Tk/bal %patch1 -p1 # patch to fix #235666 ... seems like caching code is broken %patch2 -p1 -b .seg -%patch3 -p1 -b .xim -%patch4 -b .events -%patch5 -b .getOpenFile -%patch100 %build %{__perl} Makefile.PL INSTALLDIRS=vendor X11LIB=%{_libdir} XFT=1 @@ -108,13 +94,11 @@ rm -rf $RPM_BUILD_ROOT %exclude %{_mandir}/man1/widget.1* %exclude %{_bindir}/gedi %exclude %{_bindir}/widget -%exclude %{perl_vendorarch}/fix_4_os2.pl %exclude %{perl_vendorarch}/Tk/demos -%exclude %{perl_vendorarch}/Tk/reindex.pl %changelog * Fri May 07 2010 Marcela Maslanova mmasl...@redhat.com - 804.028-12 -- Mass rebuild with perl-5.12.0 +- Mass rebuild with perl-5.12.0 update to development release * Fri Dec 4 2009 Stepan Kasal ska...@redhat.com - 804.028-11 - rebuild against perl 5.10.1 Index: sources === RCS file: /cvs/pkgs/rpms/perl-Tk/devel/sources,v retrieving revision 1.3 retrieving revision 1.4 diff -u -p -r1.3 -r1.4 --- sources 2 Jan 2008 13:04:53 - 1.3 +++ sources 13 May 2010 12:56:23 - 1.4 @@ -1 +1 @@ -7153c1c411b0dd005a0660179e5c5900 Tk-804.028.tar.gz +8ec3e456ca0eadd685a574e943d3d9ce Tk-804.028_503.tar.gz --- perl-Tk-XIM.patch DELETED --- --- perl-Tk-events.patch DELETED --- --- perl-Tk-getOpenFile.patch DELETED --- --- perl-Tk-gif.patch DELETED --- -- 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: ABRT duplicate detection - is it for real?
Hi Christoph, there was a flaw in the duplicate detection (undiscovered for a long time) that allowed to file that duplicates you received. It has been fixed. abrt.spec: * Mon May 03 2010 Karel Klic kk...@redhat.com 1.0.9-2 - fixed crash function detection (a part of duplication detection) Karel Dne 13.5.2010 14:55, Christoph Wickert napsal(a): I'm getting the same bug reports over and over again, for example https://bugzilla.redhat.com/show_bug.cgi?id=542393 Shouldn't ABRT catch the duplicates? AFAIK abrt recognizes dupes based on hashes of the backtrace, but the format of the backtraces has changed with nearly every new ABRT version, so the backtraces will not be the same even from exactly the same crash. How to deal with that problem? And what about more complicated cases, for example a backtrace where the commandline is different as in /usr/bin/program /home/user/some.file. As user and filename change, the hash cannot be the same. Regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rpms/perl-SOAP-Lite/devel perl-SOAP-Lite.spec,1.19,1.20
Author: corsepiu Update of /cvs/pkgs/rpms/perl-SOAP-Lite/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv18934 Modified Files: perl-SOAP-Lite.spec Log Message: * Thu May 13 2010 Ralf Corsépius corse...@fedoraproject.org - 0.710.10-4 - BR: perl(version) (Fix perl-5.12.0 build breakdown). Index: perl-SOAP-Lite.spec === RCS file: /cvs/pkgs/rpms/perl-SOAP-Lite/devel/perl-SOAP-Lite.spec,v retrieving revision 1.19 retrieving revision 1.20 diff -u -p -r1.19 -r1.20 --- perl-SOAP-Lite.spec 6 May 2010 12:28:07 - 1.19 +++ perl-SOAP-Lite.spec 13 May 2010 13:18:38 - 1.20 @@ -1,6 +1,6 @@ Name: perl-SOAP-Lite Version: 0.710.10 -Release: 3%{?dist} +Release: 4%{?dist} Summary: Client and server side SOAP implementation License: GPL+ or Artistic Group: Development/Libraries @@ -20,6 +20,7 @@ BuildRequires: perl(Crypt::SSLeay) BuildRequires: perl(IO::Socket::SSL) BuildRequires: perl(MIME::Lite) BuildRequires: perl(Apache) +BuildRequires: perl(version) %if 0%{?fedora} BuildRequires: perl(FCGI) %endif @@ -73,6 +74,9 @@ make test %{_mandir}/man1/* %changelog +* Thu May 13 2010 Ralf Corsépius corse...@fedoraproject.org - 0.710.10-4 +- BR: perl(version) (Fix perl-5.12.0 build breakdown). + * Thu May 06 2010 Marcela Maslanova mmasl...@redhat.com - 0.710.10-3 - Mass rebuild with perl-5.12.0 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Fedora 13 Release Candidate Phase
Jesse Keating said the following on 05/12/2010 03:11 PM Pacific Time: On Thu, 2010-05-13 at 02:42 +0530, Rahul Sundaram wrote: On 05/13/2010 02:37 AM, Bill Nottingham wrote: There was an open ticket requesting Pino. There was not anything from the maintainers requesting the games. I did mention this on IRC but what is the criteria for pulling in the updates? If I knew what would be reasonable to request, it would help for future releases. I am also looking for guidelines on, what updates are considered a good thing.Is the game update a problem? Rahul I was trying to do away with the tickets for freeze exceptions, as I was trying to do away with freeze exceptions outside of blocker bugs. However there are a few bugs which we would classify as not blockers but things which we would take a fix for. These generally start out by being proposed blockers. I'd like to see these would take a fix for bugs added or kept on the blocker list with a short comment explaining why they are being taken in since they don't meet the regular definition of blocker bug. This provides a very clear list of bugs that should get extra verification attention when the RC comes out. It also provides a clear trail of the decisions made so others can understand our process and reasoning. The process isn't perfect, nor all that documented, as we're exploring as we go. This is the first time we've done a RC phase with the no frozen rawhide style of development. I suspect we'll be better about process and documentation next time around. I'm looking forward to continuing to help expand the documentation about our release processes. This is important because then everyone is working with the same information and can approach the process in the same way. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ABRT duplicate detection - is it for real?
Dne 13.5.2010 14:55, Christoph Wickert napsal(a): AFAIK abrt recognizes dupes based on hashes of the backtrace, but the format of the backtraces has changed with nearly every new ABRT version, so the backtraces will not be the same even from exactly the same crash. The hash is not calculated from the whole backtrace, but from simplified version of it. In the case of gwget (https://bugzilla.redhat.com/attachment.cgi?id=374581), the input for hash calculation looks this way: $ abrt-backtrace ./backtrace -n -d 4 -r -m Thread node_get_last get_sequence IA__g_sequence_iter_get_sequence IA__gtk_list_store_set_valist Only names from the top few frames are used. How to deal with that problem? And what about more complicated cases, for example a backtrace where the commandline is different as in /usr/bin/program /home/user/some.file. As user and filename change, the hash cannot be the same. The command line is not a part of the hash calculation. AFAIK only the backtrace, package name, and a part of package version is. Karel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 13 Release Candidate Phase
El Wed, 12-05-2010 a las 15:59 -0500, Bruno Wolff III escribió: On Thu, May 13, 2010 at 02:23:38 +0530, Rahul Sundaram methe...@gmail.com wrote: On 05/13/2010 02:22 AM, Bruno Wolff III wrote: I don't see that pulling in the games is a good idea. The release process is that only blockers should be pulled in right now, though that is being bent a little. There should be some clarification done in that regard for the next release, but there is no way these game updates are in that category. While the risk that they would break other things seems very low, I don't think starting out with a smaller updates repository at this point is worth taking the risk. I might be convinced otherwise for a large package that was on the default install as that could result in significant bandwidth savings. But I don't think that applies to wesnoth or openarena. Well then, why do I hear people complain about it? I think because they see the size of updates as important and the risk of something breaking as being very low. Also the rules for including new packages are being bent for some packages, which makes one think they can be bent for other packages. Ironically, the OpenArena update *does* indeed break something: ber...@giskard:~$ openarena [...] Sound initialization successful. Loading vm file vm/ui.qvm... ...which has vmMagic VM_MAGIC_VER2 Loading 1550 jump table targets total 0, hsize 1021, zero 1021, min 0, max 0 Segmentation fault (core dumped) I gave a -1 to this update a few days ago, but it's been ignored: https://admin.fedoraproject.org/updates/openarena-0.8.5-1.fc13 Whether a broken update comes before, after or during a freeze does not significantly change the overall distro quality perceived by users. What we really need, imho, is a better QC process between packagers and stable updates. Bodhi was supposed to implement such process, but in fact it's mostly useless because there's no incentive for testers to go there and report about their experience with a package installed from updates-testing. One reason why I myself neglect to give karma points to updates is that it's hard to remember which packages were installed from updates-testing. Perhaps yum and gpk-application could remind you to do it. Even better, the abrt applet could popup after one day from installing an update to let you file a comment in Bodhi easily without going through the web interface. I don't think the complaints are unreasonable. I think the answer should still be no. The process should be explained as well as at least a general rational for other exceptions granted this go around. And for the future the process should be more closely followed and the process documentation updated if there are reasons we will take updates for packages other than to fix blockers after the RC process has started. I think we could take any package at any time, after a sufficient amount of testing has been done on it. If we want to raise the quality bar between RC and release, we may simply require more karma points to push an update to stable. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 13 Release Candidate Phase
On Thu, 13 May 2010, Bernie Innocenti wrote: What we really need, imho, is a better QC process between packagers and stable updates. Bodhi was supposed to implement such process, but in fact it's mostly useless because there's no incentive for testers to go there and report about their experience with a package installed from updates-testing. One reason why I myself neglect to give karma points to updates is that it's hard to remember which packages were installed from updates-testing. Perhaps yum and gpk-application could remind you to do it. Even better, the abrt applet could popup after one day from installing an update to let you file a comment in Bodhi easily without going through the web interface. good idea! sudo yum install fedora-easy-karma fedora-easy-karma follow the prompts (if any) -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ABRT duplicate detection - is it for real?
Am Donnerstag, den 13.05.2010, 15:17 +0200 schrieb Karel Klic: Hi Christoph, there was a flaw in the duplicate detection (undiscovered for a long time) that allowed to file that duplicates you received. It has been fixed. abrt.spec: * Mon May 03 2010 Karel Klic kk...@redhat.com 1.0.9-2 - fixed crash function detection (a part of duplication detection) This was pushed to stable the next day and the last duplicate I received was https://bugzilla.redhat.com/show_bug.cgi?id=591099 on May 11th. At this time the reporter should already have had 1.0.9-2 I guess. BTW: I already suggested that there should be timestamps in the bug report and in the backtraces. This might help us to avoid at least some confusion. Regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 13 Release Candidate Phase
On 05/12/2010 11:11 PM, Bruno Wolff III wrote: On Wed, May 12, 2010 at 16:22:13 -0500, Jon Cieslal...@jcomserv.net wrote: My understanding was that we would still open a rel-eng ticket for a freeze exception. Which I didn't do for Wesnoth. Because the outcry for it was underwhelming. And likely another rebuild will be needed shortly. I still need to do a test, but it looks like wesnoth will need to get built against the new boost-devel (after a boost update gets pushed), because the bug causing the problem for x86_64 is in a header using during the wesnoth build. I can prep for the test tonight, but it's a pain to do the final test remotely. So that will wait until tomorrow. Email me as soon as you want this done, and I'll do it ASAP. -J -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 13 Release Candidate Phase
On Thu, 2010-05-13 at 10:03 -0400, Bernie Innocenti wrote: El Thu, 13-05-2010 a las 09:53 -0400, Bernie Innocenti escribió: I gave a -1 to this update a few days ago, but it's been ignored: https://admin.fedoraproject.org/updates/openarena-0.8.5-1.fc13 Analyzing the event log in Bodhi exposes where our quality process ultimately fails: the update got my -1, then it was pushed to stable regardless of its negative karma. sundaram - 2010-04-27 15:36:35 This update has been submitted for testing. bodhi - 2010-04-28 03:08:08 This update has been pushed to testing sundaram - 2010-05-07 22:21:43 This update has been submitted for stable. bernie - 2010-05-08 15:28:43 Core dumps after initializing sound. (-1) bodhi - 2010-05-10 23:44:08 This update has been pushed to stable Is the last action automated or are humans overseeing it? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ hey, It works normally here. No breakage at all Available Devices: PulseAudio Software ALSA Software Sound initialization successful. Loading vm file vm/ui.qvm... ...which has vmMagic VM_MAGIC_VER2 Loading 1550 jump table targets total 0, hsize 1021, zero 1021, min 0, max 0 total 10042, hsize 1021, zero 2, min 0, max 30 VM file ui compiled to 3203472 bytes of code (0x7f97e563e000 - 0x7f97e594c190) compilation took 2.008561 seconds ui loaded in 1450816 bytes on the hunk 51 arenas parsed 1 arenas ignored to make count divisible by 4 24 bots parsed ^3WARNING: unknown blend mode 'gl_one_minus_dst_color' in shader 'menuback_blueish', substituting GL_ONE --- Common Initialization Complete --- I hadn't realized it was in testing so hadn't given it karma. Did now ;) Ankur -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Marc Wiriadisastra orphaning some packages
I'm taking drpython 2010/5/11 Rich Mattes richmat...@gmail.com: On Tue, May 11, 2010 at 9:32 AM, Paul W. Frields sticks...@gmail.com wrote: ... [6]mediatomb -- MediaTomb - UPnP AV Mediaserver for Linux I'll take this one. Co-maintainers welcome. Rich - End forwarded message - -- 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 -- Henrique LonelySpooky Junior -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 13 Release Candidate Phase
El Thu, 13-05-2010 a las 09:57 -0400, Seth Vidal escribió: sudo yum install fedora-easy-karma fedora-easy-karma follow the prompts (if any) Works fantastically, thanks! -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: perl 5.12 status
On 05/11/2010 03:42 PM, Marcela Maslanova wrote: Hello, I'm attaching list of failure. Some of them will be still fixable by simple rebuild. It's 133 build failures. perl-Apache2-SOAP FWIW: this package fails due to a dependency on mod_perl. When having rebuilt mod_perl, perl-Apache2-SOAP also builds. Ralf -- 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
rpms/perl-Net-SSH-Perl/devel perl-Net-SSH-Perl.spec,1.16,1.17
Author: pghmcfc Update of /cvs/pkgs/rpms/perl-Net-SSH-Perl/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv18870/devel Modified Files: perl-Net-SSH-Perl.spec Log Message: Don't clobber ~/.gnupg during build Index: perl-Net-SSH-Perl.spec === RCS file: /cvs/pkgs/rpms/perl-Net-SSH-Perl/devel/perl-Net-SSH-Perl.spec,v retrieving revision 1.16 retrieving revision 1.17 diff -u -p -r1.16 -r1.17 --- perl-Net-SSH-Perl.spec 4 May 2010 12:07:46 - 1.16 +++ perl-Net-SSH-Perl.spec 13 May 2010 14:16:59 - 1.17 @@ -1,14 +1,10 @@ # IDEA is a patent-encumbered alogorithm so default to not supporting it # To include support for the IDEA algorithm, use: rpmbuild --with IDEA -# Noarch package doesn't provide debuginfo but the default script -# interferes with signature checking so disable it completely -%define debug_package %{nil} - Summary: SSH (Secure Shell) client Name: perl-Net-SSH-Perl Version: 1.34 -Release: 6%{?dist} +Release: 7%{?dist} License: GPL+ or Artistic Group: Development/Libraries Url: http://search.cpan.org/dist/Net-SSH-Perl/ @@ -52,17 +48,26 @@ Net::SSH::Perl is an all-Perl module imp client. It is compatible with both the SSH-1 and SSH-2 protocols. %prep -%setup -q -n Net-SSH-Perl-%{version} +%setup -q -c -n Net-SSH-Perl + +# Copy up documentation for convenience with %%doc +%{__cp} -a Net-SSH-Perl-%{version}/{Changes,README,LICENSE,eg,ToDo} . # Avoid extra deps from examples %{__chmod} -x eg/* +# Create a GPG directory for testing, to avoid using ~/.gnupg +%{__mkdir} --mode=0700 gnupghome +export GNUPGHOME=$(pwd)/gnupghome +%{__gpg} --import %{SOURCE1} + # Remove Crypt::IDEA dep if we're not supporting the IDEA algorithm %define bogusreq 'perl(Crypt::IDEA)' %global reqfilt /bin/sh -c %{__perl_requires} | %{__grep} -Fvx %{bogusreq} %{!?_with_IDEA:%define __perl_requires %{reqfilt}} %build +cd Net-SSH-Perl-%{version} ( # Protocol support (select one) # 1=SSH1 2=SSH2 3=Both @@ -74,18 +79,20 @@ client. It is compatible with both the S ) | %{__perl} Makefile.PL INSTALLDIRS=vendor %{__make} %{?_smp_mflags} - -%check -# Critic and POD tests currently fail -%{__gpg} --import %{SOURCE1} -LC_ALL=en_US %{__make} test TEST_AUTHOR=1 TEST_CRITIC=0 TEST_SIGNATURE=1 TEST_SPELL=1 +cd - %install %{__rm} -rf %{buildroot} -%{__make} pure_install PERL_INSTALL_ROOT=%{buildroot} +%{__make} -C Net-SSH-Perl-%{version} pure_install PERL_INSTALL_ROOT=%{buildroot} /usr/bin/find %{buildroot} -type f -name .packlist -exec %{__rm} -f {} ';' -/usr/bin/find %{buildroot} -depth -type d -exec /bin/rmdir {} 2/dev/null ';' -%{__chmod} -R u+w %{buildroot}/* +/usr/bin/find %{buildroot} -depth -type d -exec /bin/rmdir {} ';' 2/dev/null +%{__chmod} -R u+w %{buildroot} + +%check +# Critic and POD tests currently fail +export GNUPGHOME=$(pwd)/gnupghome +LC_ALL=en_US %{__make} -C Net-SSH-Perl-%{version} test \ + TEST_AUTHOR=1 TEST_CRITIC=0 TEST_SIGNATURE=1 TEST_SPELL=1 %clean %{__rm} -rf %{buildroot} @@ -97,11 +104,14 @@ LC_ALL=en_US %{__make} test TEST_AUTHOR= %{_mandir}/man3/Net::SSH::Perl*.3pm* %changelog +* Thu May 13 2010 Paul Howarth p...@city-fan.org 1.34-7 +- Don't clobber ~/.gnupg during build + * Tue May 04 2010 Marcela Maslanova mmasl...@redhat.com - 1.34-6 - Mass rebuild with perl-5.12.0 * Mon Dec 7 2009 Stepan Kasal ska...@redhat.com - 1.34-5 -- rebuild against perl 5.10.1 +- Rebuild against perl 5.10.1 * Sun Jul 26 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org - 1.34-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
rpms/perl-Net-SSH-Perl/EL-6 perl-Net-SSH-Perl.spec,1.14,1.15
Author: pghmcfc Update of /cvs/pkgs/rpms/perl-Net-SSH-Perl/EL-6 In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv18870/EL-6 Modified Files: perl-Net-SSH-Perl.spec Log Message: Don't clobber ~/.gnupg during build Index: perl-Net-SSH-Perl.spec === RCS file: /cvs/pkgs/rpms/perl-Net-SSH-Perl/EL-6/perl-Net-SSH-Perl.spec,v retrieving revision 1.14 retrieving revision 1.15 diff -u -p -r1.14 -r1.15 --- perl-Net-SSH-Perl.spec 26 Jul 2009 13:46:37 - 1.14 +++ perl-Net-SSH-Perl.spec 13 May 2010 14:16:59 - 1.15 @@ -1,14 +1,10 @@ # IDEA is a patent-encumbered alogorithm so default to not supporting it # To include support for the IDEA algorithm, use: rpmbuild --with IDEA -# Noarch package doesn't provide debuginfo but the default script -# interferes with signature checking so disable it completely -%define debug_package %{nil} - Summary: SSH (Secure Shell) client Name: perl-Net-SSH-Perl Version: 1.34 -Release: 4%{?dist} +Release: 7%{?dist} License: GPL+ or Artistic Group: Development/Libraries Url: http://search.cpan.org/dist/Net-SSH-Perl/ @@ -52,17 +48,26 @@ Net::SSH::Perl is an all-Perl module imp client. It is compatible with both the SSH-1 and SSH-2 protocols. %prep -%setup -q -n Net-SSH-Perl-%{version} +%setup -q -c -n Net-SSH-Perl + +# Copy up documentation for convenience with %%doc +%{__cp} -a Net-SSH-Perl-%{version}/{Changes,README,LICENSE,eg,ToDo} . # Avoid extra deps from examples %{__chmod} -x eg/* +# Create a GPG directory for testing, to avoid using ~/.gnupg +%{__mkdir} --mode=0700 gnupghome +export GNUPGHOME=$(pwd)/gnupghome +%{__gpg} --import %{SOURCE1} + # Remove Crypt::IDEA dep if we're not supporting the IDEA algorithm %define bogusreq 'perl(Crypt::IDEA)' %global reqfilt /bin/sh -c %{__perl_requires} | %{__grep} -Fvx %{bogusreq} %{!?_with_IDEA:%define __perl_requires %{reqfilt}} %build +cd Net-SSH-Perl-%{version} ( # Protocol support (select one) # 1=SSH1 2=SSH2 3=Both @@ -74,18 +79,20 @@ client. It is compatible with both the S ) | %{__perl} Makefile.PL INSTALLDIRS=vendor %{__make} %{?_smp_mflags} - -%check -# Critic and POD tests currently fail -%{__gpg} --import %{SOURCE1} -LC_ALL=en_US %{__make} test TEST_AUTHOR=1 TEST_CRITIC=0 TEST_SIGNATURE=1 TEST_SPELL=1 +cd - %install %{__rm} -rf %{buildroot} -%{__make} pure_install PERL_INSTALL_ROOT=%{buildroot} +%{__make} -C Net-SSH-Perl-%{version} pure_install PERL_INSTALL_ROOT=%{buildroot} /usr/bin/find %{buildroot} -type f -name .packlist -exec %{__rm} -f {} ';' -/usr/bin/find %{buildroot} -depth -type d -exec /bin/rmdir {} 2/dev/null ';' -%{__chmod} -R u+w %{buildroot}/* +/usr/bin/find %{buildroot} -depth -type d -exec /bin/rmdir {} ';' 2/dev/null +%{__chmod} -R u+w %{buildroot} + +%check +# Critic and POD tests currently fail +export GNUPGHOME=$(pwd)/gnupghome +LC_ALL=en_US %{__make} -C Net-SSH-Perl-%{version} test \ + TEST_AUTHOR=1 TEST_CRITIC=0 TEST_SIGNATURE=1 TEST_SPELL=1 %clean %{__rm} -rf %{buildroot} @@ -97,6 +104,15 @@ LC_ALL=en_US %{__make} test TEST_AUTHOR= %{_mandir}/man3/Net::SSH::Perl*.3pm* %changelog +* Thu May 13 2010 Paul Howarth p...@city-fan.org 1.34-7 +- Don't clobber ~/.gnupg during build + +* Tue May 04 2010 Marcela Maslanova mmasl...@redhat.com - 1.34-6 +- Mass rebuild with perl-5.12.0 + +* Mon Dec 7 2009 Stepan Kasal ska...@redhat.com - 1.34-5 +- Rebuild against perl 5.10.1 + * Sun Jul 26 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org - 1.34-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Preupgrade F12-F13 error
Em 13-05-2010 05:35, Kamil Paral escreveu: How do I increase size the boot partition, with LVM? My partition: FilesystemSize Used Avail Use% Mounted on /dev/sda1 190M 39M 142M 22% /boot Can anyone help? Thanks a lot, Clóvis I think the easiest way is to simply download F13 DVD and do standard upgrade. Hi Folks, I decided to download http://fedora.c3sl.ufpr.br/linux//releases/test/13-Beta/Fedora/i386/iso/Fedora-13-Beta-i386-netinst.iso, and not to venture in an attempt to increase the /boot. :-) I hope the new version of Fedora by default able to determine the correct size of /boot. My version comes from successive installations and upgrades since the first version of Fedora. :-) Thank for all the replies and tips, Clovis -- Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clo...@feagri.unicamp.br http://www.feagri.unicamp.br Fone(0xx19) 35211031-35211038-91173116 ou FAX(55xx19) 35211005/35211010 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Marc Wiriadisastra orphaning some packages
Oops! Last minute changes. My time just got shorter again, so I can not take care of drpython now, however, I would not like to see it being removed from Fedora. 2010/5/13 Chen Lei supercyp...@gmail.com: On Tue, May 11, 2010 at 9:32 AM, Paul W. Frields sticks...@gmail.com wrote: [3]gnome-themes-extras -- Collection of metathemes for the Gnome desktop environment [4]gnomecatalog -- Catalog Software for Gnome Desktop Take those two, comaintainers are welcome for all of my packages https://admin.fedoraproject.org/pkgdb/users/packages Chen Lei -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Henrique LonelySpooky Junior -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 13 Release Candidate Phase
On Thu, May 13, 2010 at 09:06:39 -0500, Jon Ciesla l...@jcomserv.net wrote: I can prep for the test tonight, but it's a pain to do the final test remotely. So that will wait until tomorrow. Email me as soon as you want this done, and I'll do it ASAP. Two people have confirmed that a combination of installing the scratch build and rebuilding and then installing wesnoth solves the x86_64 connect to server issue. To do this quickly, it will require chainbuilding both packages so that both can get tested at the same time. Otherwise the boost update needs to go through testing and get to stable before a wesnoth rebuild would do any good. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Renaming packages, trimming changelog and re-starting revisions?
Hi, we recently started a relatively big rename of several packages (jakarta-commons). There seems to be inconsistency as far as changelog trimming and revision numbering goes. I could not find anything on that point on wiki. So: 1. Is is required to trim the changelog when renaming package? 2. Is it required to start counting revisions from 1 again? If there are no MUSTs, what is recommended or considered good practice? Thanks, -- Stanislav Ochotnicky sochotni...@redhat.com Associate Software Engineer - Base Operating Systems Brno PGP: 71A1677C Red Hat Inc. http://cz.redhat.com signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Renaming packages, trimming changelog and re-starting revisions?
On 05/13/2010 10:05 AM, Stanislav Ochotnicky wrote: Hi, we recently started a relatively big rename of several packages (jakarta-commons). There seems to be inconsistency as far as changelog trimming and revision numbering goes. I could not find anything on that point on wiki. So: Personally, I'd say. . . 1. Is is required to trim the changelog when renaming package? Please don't, but do comment on the old name at the relevant changelog entry. 2. Is it required to start counting revisions from 1 again? May as well, as long as the Obsoletes/Provides are good. If there are no MUSTs, what is recommended or considered good practice? Also, if you like, you could submit a draft for the FPC. Thanks, -J -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Renaming packages, trimming changelog and re-starting revisions?
On Thu, May 13, 2010 at 10:12:39 -0500, Jon Ciesla l...@jcomserv.net wrote: May as well, as long as the Obsoletes/Provides are good. The obsoletes don't appear to be good. I noticed that yesterday and filed a bug this morning. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Renaming packages, trimming changelog and re-starting revisions?
On Thu, May 13, 2010 at 10:12:39AM -0500, Jon Ciesla wrote: On 05/13/2010 10:05 AM, Stanislav Ochotnicky wrote: Hi, we recently started a relatively big rename of several packages (jakarta-commons). There seems to be inconsistency as far as changelog trimming and revision numbering goes. I could not find anything on that point on wiki. So: Personally, I'd say. . .think really old is around three- 1. Is is required to trim the changelog when renaming package? Please don't, but do comment on the old name at the( relevant changelog entry. Agreed -- I do trim changelogs of really old entries from my specs (4+ years) once a year or so. That's separate from renaming. -Toshoi pgpNHKT6r1Re4.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Renaming packages, trimming changelog and re-starting revisions?
On 05/13/2010 05:54 PM, Bruno Wolff III wrote: On Thu, May 13, 2010 at 10:12:39 -0500, Jon Ciesla l...@jcomserv.net wrote: May as well, as long as the Obsoletes/Provides are good. The obsoletes don't appear to be good. I noticed that yesterday and filed a bug this morning. Obsoletes where? Could you point to the bugzilla? -- Stanislav Ochotnicky sochotni...@redhat.com Associate Software Engineer - Base Operating Systems Brno PGP: 71A1677C Red Hat Inc. http://cz.redhat.com signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 13 Release Candidate Phase
On Thu, 2010-05-13 at 10:03 -0400, Bernie Innocenti wrote: El Thu, 13-05-2010 a las 09:53 -0400, Bernie Innocenti escribió: I gave a -1 to this update a few days ago, but it's been ignored: https://admin.fedoraproject.org/updates/openarena-0.8.5-1.fc13 Analyzing the event log in Bodhi exposes where our quality process ultimately fails: the update got my -1, then it was pushed to stable regardless of its negative karma. sundaram - 2010-04-27 15:36:35 This update has been submitted for testing. bodhi - 2010-04-28 03:08:08 This update has been pushed to testing sundaram - 2010-05-07 22:21:43 This update has been submitted for stable. bernie - 2010-05-08 15:28:43 Core dumps after initializing sound. (-1) bodhi - 2010-05-10 23:44:08 This update has been pushed to stable Is the last action automated or are humans overseeing it? It's a little of both. once the update has been requested for stable, the maintainer could rescind that request before releng does the push. However there are generally hundreds of updates across the releases that get pushed at one time, and releng does not have the time or man power to click through each one looking for negative karma. We rely on the maintainer to do the right thing. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Renaming packages, trimming changelog and re-starting revisions?
On Thu, May 13, 2010 at 18:17:51 +0200, Stanislav Ochotnicky sochotni...@redhat.com wrote: On 05/13/2010 05:54 PM, Bruno Wolff III wrote: On Thu, May 13, 2010 at 10:12:39 -0500, Jon Ciesla l...@jcomserv.net wrote: May as well, as long as the Obsoletes/Provides are good. The obsoletes don't appear to be good. I noticed that yesterday and filed a bug this morning. Obsoletes where? Could you point to the bugzilla? Filed against apache-commons-compress: https://bugzilla.redhat.com/show_bug.cgi?id=591779 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Renaming packages, trimming changelog and re-starting revisions?
On 05/13/2010 11:13 AM, Toshio Kuratomi wrote: On Thu, May 13, 2010 at 10:12:39AM -0500, Jon Ciesla wrote: On 05/13/2010 10:05 AM, Stanislav Ochotnicky wrote: Hi, we recently started a relatively big rename of several packages (jakarta-commons). There seems to be inconsistency as far as changelog trimming and revision numbering goes. I could not find anything on that point on wiki. So: Personally, I'd say. . .think really old is around three- 1. Is is required to trim the changelog when renaming package? Please don't, but do comment on the old name at the( relevant changelog entry. Agreed -- I do trim changelogs of really old entries from my specs (4+ years) once a year or so. That's separate from renaming. -Toshoi Agreed? I came out against trimming, not for. I don't feel terribly strongly about it, though. -J -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Marc Wiriadisastra orphaning some packages
[1]diveintopython -- Dive into Python - a python book If nobody else wants to take this, I'll take ownership of it. Julian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Renaming packages, trimming changelog and re-starting revisions?
On 05/13/2010 06:24 PM, Bruno Wolff III wrote: On Thu, May 13, 2010 at 18:17:51 +0200, Stanislav Ochotnicky sochotni...@redhat.com wrote: On 05/13/2010 05:54 PM, Bruno Wolff III wrote: On Thu, May 13, 2010 at 10:12:39 -0500, Jon Ciesla l...@jcomserv.net wrote: May as well, as long as the Obsoletes/Provides are good. The obsoletes don't appear to be good. I noticed that yesterday and filed a bug this morning. Obsoletes where? Could you point to the bugzilla? Filed against apache-commons-compress: https://bugzilla.redhat.com/show_bug.cgi?id=591779 Heh, funny thing...I actually sent an email today to Sandro Mathys wondering about this push of commons-compress to F-12/F-13 stable. I guess really no change is small enough. Maybe it would be good if there was a policy for package renames only happening in rawhide if no rebase is done (such as it was for compress). This was actually suggested by Sandro, after my inquiry. -- Stanislav Ochotnicky sochotni...@redhat.com Associate Software Engineer - Base Operating Systems Brno PGP: 71A1677C Red Hat Inc. http://cz.redhat.com signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Sending a sensible email. (was: PackageKit need to be more intelligent!)
On Thu, May 13, 2010 at 9:30 AM, Richard Hughes hughsi...@gmail.com wrote: On 12 May 2010 21:58, João Neto joao.gsn...@gmail.com wrote: The system package manager for Fedora to be smarter ... This is a general point I'm making, not just about your email in particular. There appears to be a trend on this list where a random user just posts an inflammatory email with ACME SOFTWARE IS RUBBISH. Now, if the maintainer of that software is scanning the email list, bear in mind he (or she) has likely spent a significant amount of time and energy getting the software into the state you see it now. They probably spend evenings and weekend closing duplicate bugs and fixing trivial typos that people notice. If you title an email with such rubbish then the maintainer is simply going to ignore it or spam it. I'll explain why: Well said! -- mike c -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Renaming packages, trimming changelog and re-starting revisions?
On Thu, May 13, 2010 at 11:30:30AM -0500, Jon Ciesla wrote: On 05/13/2010 11:13 AM, Toshio Kuratomi wrote: On Thu, May 13, 2010 at 10:12:39AM -0500, Jon Ciesla wrote: On 05/13/2010 10:05 AM, Stanislav Ochotnicky wrote: Hi, we recently started a relatively big rename of several packages (jakarta-commons). There seems to be inconsistency as far as changelog trimming and revision numbering goes. I could not find anything on that point on wiki. So: Personally, I'd say. . .think really old is around three- 1. Is is required to trim the changelog when renaming package? Please don't, but do comment on the old name at the( relevant changelog entry. Agreed -- I do trim changelogs of really old entries from my specs (4+ years) once a year or so. That's separate from renaming. -Toshoi Agreed? I came out against trimming, not for. I don't feel terribly strongly about it, though. Agreed as in: don't trim changelogs *because* you're renaming the package. But also pointing out that trimming changelogs is reasonable as long as you aren't treadingtoo closely to modern history. -Toshio pgpMeoNw7RR4x.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Renaming packages, trimming changelog and re-starting revisions?
On 05/13/2010 12:04 PM, Toshio Kuratomi wrote: On Thu, May 13, 2010 at 11:30:30AM -0500, Jon Ciesla wrote: On 05/13/2010 11:13 AM, Toshio Kuratomi wrote: On Thu, May 13, 2010 at 10:12:39AM -0500, Jon Ciesla wrote: On 05/13/2010 10:05 AM, Stanislav Ochotnicky wrote: Hi, we recently started a relatively big rename of several packages (jakarta-commons). There seems to be inconsistency as far as changelog trimming and revision numbering goes. I could not find anything on that point on wiki. So: Personally, I'd say. . .think really old is around three- 1. Is is required to trim the changelog when renaming package? Please don't, but do comment on the old name at the( relevant changelog entry. Agreed -- I do trim changelogs of really old entries from my specs (4+ years) once a year or so. That's separate from renaming. -Toshoi Agreed? I came out against trimming, not for. I don't feel terribly strongly about it, though. Agreed as in: don't trim changelogs *because* you're renaming the package. But also pointing out that trimming changelogs is reasonable as long as you aren't treadingtoo closely to modern history. -Toshio Gotcha. Yes, that's sane. -J -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 13 Release Candidate Phase
El Thu, 13-05-2010 a las 09:22 -0700, Jesse Keating escribió: It's a little of both. once the update has been requested for stable, the maintainer could rescind that request before releng does the push. However there are generally hundreds of updates across the releases that get pushed at one time, and releng does not have the time or man power to click through each one looking for negative karma. We rely on the maintainer to do the right thing. In this case, the maintainer did the right^W usual thing we do in Fedora: 1) push the update for testing 2) after two weeks with no feedback in bodhi, request pushing to stable 3) my -1 karma came at this point 4) releng approves and pushes to stable There were just 2 days between (3) and (4). If the maintainer was supposed to notice and cancel the push, we're prone to race-conditions like this one :-) Perhaps the (web?) UI used by releng could be enhanced to display the current karma next to each push request? Or maybe Bodhi could be configured to automatically cancel stable requests when the karma drops below 0? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 13 Release Candidate Phase
El Thu, 13-05-2010 a las 19:39 +0530, Ankur Sinha escribió: It works normally here. No breakage at all I figured out that something in my config file was making it crash: http://people.sugarlabs.org/bernie/q3config.cfg I had no time to bisect it against a pristine configuration file, so I'm not sure if it happens due to some strange setting of mine or with any configuration saved by OpenArena 0.8.1. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 yum in kvm or vmware guests
Am Donnerstag, den 06.05.2010, 15:18 -0400 schrieb Seth Vidal: On Thu, 6 May 2010, Thomas Spura wrote: My workaround for this was to kill the connection and yum will search then a new server and restart the connection. Maybe if the rate is 0.5 B/s - restart the connection would be a solution for this? (Didn't saw this issue quite a while now, but I could try to reproduce this and test your patches.) Take the python-urlgrabber from rawhide and give it a whirl, please. Done and commented at: https://admin.fedoraproject.org/updates/python-urlgrabber-3.9.1-7.fc13 Works as expected with a LOWSPEEDLIMIT rate at about 2 B/s. Thanks Thomas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 13 Release Candidate Phase
On Thu, May 13, 2010 at 01:19:49PM -0400, Bernie Innocenti wrote: El Thu, 13-05-2010 a las 09:22 -0700, Jesse Keating escribió: It's a little of both. once the update has been requested for stable, the maintainer could rescind that request before releng does the push. However there are generally hundreds of updates across the releases that get pushed at one time, and releng does not have the time or man power to click through each one looking for negative karma. We rely on the maintainer to do the right thing. In this case, the maintainer did the right^W usual thing we do in Fedora: 1) push the update for testing 2) after two weeks with no feedback in bodhi, request pushing to stable 3) my -1 karma came at this point 4) releng approves and pushes to stable There were just 2 days between (3) and (4). If the maintainer was supposed to notice and cancel the push, we're prone to race-conditions like this one :-) Perhaps the (web?) UI used by releng could be enhanced to display the The web UI does display it. However, using the web UI to submit the pushes really sucks for other unrelated reasons, so we don't use it. current karma next to each push request? Or maybe Bodhi could be configured to automatically cancel stable requests when the karma drops below 0? I can look at doing this on the client side for pushes. That's a pretty good idea. Could you file a ticket against bodhi and assign it to me so I don't forget? josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F-13 yum in kvm or vmware guests
On Thu, 13 May 2010, Thomas Spura wrote: Am Donnerstag, den 06.05.2010, 15:18 -0400 schrieb Seth Vidal: On Thu, 6 May 2010, Thomas Spura wrote: My workaround for this was to kill the connection and yum will search then a new server and restart the connection. Maybe if the rate is 0.5 B/s - restart the connection would be a solution for this? (Didn't saw this issue quite a while now, but I could try to reproduce this and test your patches.) Take the python-urlgrabber from rawhide and give it a whirl, please. Done and commented at: https://admin.fedoraproject.org/updates/python-urlgrabber-3.9.1-7.fc13 Works as expected with a LOWSPEEDLIMIT rate at about 2 B/s. I believe LOWSPEEDLIMIT is actually 1B/s but... at that point it is almost negligible. Probably need to make lowspeedlimit configurable from yum at some point. -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Clarification about taking orphaned packages asked
I have just taken ownership of the recently orphaned package 'diveintopython' in pkgdb as announced on this thread [1]. Now, while going through [2] I have a question about the instructions given there. If a package was last updated more than three months ago (running cvs log -r HEAD *.spec can show you this information), you will need to submit a review request and have the package approved by a reviewer as if it were new to Fedora. See the package review process for more information. There are a couple of small changes though, be sure to submit a 'update' request to 'cvs', and before you will be able to run the final 'make build' commands you will need to file a ticket w/ release engineering to unblock your package https://fedorahosted.org/rel-eng/newticket The package has not received updates for over three months now (but has been rebuilt and included in Fedora 13 etc.) and therefore I'll have to submit a new review request as far as I understood. What I don't get now is the part about the 'update' request to 'cvs'. What exactly does that mean? Should I check the package out from CVS and do a 'cvs update', or should I file an Update request (as opposed to Review request) in bugzilla against cvs, or something completely different? Sorry if it sounds obvious, but I don't know what that's trying to tell me. Regards, Julian [1] http://www.mail-archive.com/devel@lists.fedoraproject.org/msg07879.html [2] https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Clarification about taking orphaned packages asked
On 05/13/2010 01:23 PM, Julian Aloofi wrote: I have just taken ownership of the recently orphaned package 'diveintopython' in pkgdb as announced on this thread [1]. Now, while going through [2] I have a question about the instructions given there. If a package was last updated more than three months ago (running cvs log -r HEAD *.spec can show you this information), you will need to submit a review request and have the package approved by a reviewer as if it were new to Fedora. See the package review process for more information. There are a couple of small changes though, be sure to submit a 'update' request to 'cvs', and before you will be able to run the final 'make build' commands you will need to file a ticket w/ release engineering to unblock your package https://fedorahosted.org/rel-eng/newticket The package has not received updates for over three months now (but has been rebuilt and included in Fedora 13 etc.) and therefore I'll have to submit a new review request as far as I understood. What I don't get now is the part about the 'update' request to 'cvs'. What exactly does that mean? Should I check the package out from CVS and do a 'cvs update', or should I file an Update request (as opposed to Review request) in bugzilla against cvs, or something completely different? Sorry if it sounds obvious, but I don't know what that's trying to tell me. Regards, Julian [1] http://www.mail-archive.com/devel@lists.fedoraproject.org/msg07879.html [2] https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers I wouldn't think it would need a review, as it was *just* orphaned, and is a primarily informational package. -J -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Clarification about taking orphaned packages asked
Am Donnerstag, den 13.05.2010, 13:25 -0500 schrieb Jon Ciesla: On 05/13/2010 01:23 PM, Julian Aloofi wrote: Now, while going through [2] I have a question about the instructions given there. [...] I wouldn't think it would need a review, as it was *just* orphaned, and is a primarily informational package. -J I assumed so as well, but just thought I'd be sure and ask before breaking some policies. Julian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Clarification about taking orphaned packages asked
I think your safe with not redoing the review. -AdamM (from Android ) On May 13, 2010 1:52 PM, Julian Aloofi julian.fedorali...@googlemail.com wrote: Am Donnerstag, den 13.05.2010, 13:25 -0500 schrieb Jon Ciesla: On 05/13/2010 01:23 PM, Julian Aloofi wrote: Now, while going through [2] I have a question about the instructions given there. [...] I wouldn't think it would need a review, as it was *just* orphaned, and is a primarily informat... I assumed so as well, but just thought I'd be sure and ask before breaking some policies. Julian -- 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
Re: Fedora 13 Release Candidate Phase
On Thu, May 13, 2010 at 07:31:32PM +0100, Adam Williamson wrote: On Thu, 2010-05-13 at 13:45 -0400, Josh Boyer wrote: current karma next to each push request? Or maybe Bodhi could be configured to automatically cancel stable requests when the karma drops below 0? I can look at doing this on the client side for pushes. That's a pretty good idea. Could you file a ticket against bodhi and assign it to me so I don't forget? we've pretty much established already that numerical karma is a bad concept; I think it'd be better for to automatically rescind the request (or warn) if any negative feedback is posted after the push request but before the push, never mind what the overall numerical value is. If we combine that with requiring valid bug numbers before negative karma can be applied, then I'd be ok with that. Until we require that, there are way to many corner cases where something like that isn't going to work well. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Clarification about taking orphaned packages asked
Am Donnerstag, den 13.05.2010, 14:45 -0500 schrieb Adam Miller: I think your safe with not redoing the review. -AdamM (from Android ) That's what I wanted to hear :D I'll notice whether something is wrong when bodhi doesn't accept any new updates at the latest. Thanks for the help, Julian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rpms/perl-namespace-autoclean/devel .cvsignore, 1.3, 1.4 perl-namespace-autoclean.spec, 1.7, 1.8 sources, 1.3, 1.4
Author: mmaslano Update of /cvs/pkgs/rpms/perl-namespace-autoclean/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv12676 Modified Files: .cvsignore perl-namespace-autoclean.spec sources Log Message: * Tue May 04 2010 Marcela Maslanova mmasl...@redhat.com - 0.09-4 - Mass rebuild with perl-5.12.0 Index: .cvsignore === RCS file: /cvs/pkgs/rpms/perl-namespace-autoclean/devel/.cvsignore,v retrieving revision 1.3 retrieving revision 1.4 diff -u -p -r1.3 -r1.4 --- .cvsignore 16 Sep 2009 15:40:00 - 1.3 +++ .cvsignore 13 May 2010 06:23:12 - 1.4 @@ -1 +1 @@ -namespace-autoclean-0.09.tar.gz +namespace-autoclean-0.11.tar.gz Index: perl-namespace-autoclean.spec === RCS file: /cvs/pkgs/rpms/perl-namespace-autoclean/devel/perl-namespace-autoclean.spec,v retrieving revision 1.7 retrieving revision 1.8 diff -u -p -r1.7 -r1.8 --- perl-namespace-autoclean.spec 4 May 2010 08:32:54 - 1.7 +++ perl-namespace-autoclean.spec 13 May 2010 06:23:12 - 1.8 @@ -1,6 +1,6 @@ Name: perl-namespace-autoclean -Version:0.09 -Release:4%{?dist} +Version:0.11 +Release:1%{?dist} License:GPL+ or Artistic Group: Development/Libraries Summary:Keep imports out of your namespace Index: sources === RCS file: /cvs/pkgs/rpms/perl-namespace-autoclean/devel/sources,v retrieving revision 1.3 retrieving revision 1.4 diff -u -p -r1.3 -r1.4 --- sources 16 Sep 2009 15:40:01 - 1.3 +++ sources 13 May 2010 06:23:12 - 1.4 @@ -1 +1 @@ -79241eb4929cdf6eecd6e5cc4c1ef2f8 namespace-autoclean-0.09.tar.gz +25a1339256c844332637331c80a2f62a namespace-autoclean-0.11.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: perl 5.12 status
2010/5/12 Marcela Mašláňová mmasl...@redhat.com: perl-Catalyst-Action-RenderView perl-Catalyst-Authentication-Store-DBIx-Class perl-Catalyst-Controller-FormBuilder perl-Catalyst-Devel perl-Catalyst-Helper-FastCGI-ExternalServer perl-Catalyst-Model-DBIC-Schema perl-Catalyst-Model-LDAP perl-Catalyst-Model-XMLRPC perl-Catalyst-Plugin-Authentication perl-Catalyst-Plugin-Authorization-ACL perl-Catalyst-Plugin-ConfigLoader perl-Catalyst-Plugin-Session perl-Catalyst-Plugin-Session-State-Cookie perl-Catalyst-Plugin-StackTrace perl-Catalyst-Plugin-Static-Simple perl-Catalyst-Plugin-SubRequest perl-Catalyst-Runtime perl-Catalyst-View-PDF-Reuse perl-Catalyst-View-TT perl-namespace-autoclean perl-namespace-clean All of the above successfully rebuilt now. Only three perl-Catalyst-* are still failing: perl-Catalyst-Controller-BindLex perl-Catalyst-Controller-HTML-FormFu perl-Catalyst-View-JSON -- Iain. -- 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
rpms/perl-HTTP-Lite/devel perl-HTTP-Lite.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
Author: iarnell Update of /cvs/pkgs/rpms/perl-HTTP-Lite/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv29846/devel Modified Files: .cvsignore sources Added Files: perl-HTTP-Lite.spec Log Message: initial import --- NEW FILE perl-HTTP-Lite.spec --- Name: perl-HTTP-Lite Version:2.2 Release:1%{?dist} Summary:Lightweight HTTP implementation License:GPL+ or Artistic Group: Development/Libraries URL:http://search.cpan.org/dist/HTTP-Lite/ Source0: http://www.cpan.org/authors/id/A/AD/ADAMK/HTTP-Lite-%{version}.tar.gz BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) BuildArch: noarch BuildRequires: perl(ExtUtils::MakeMaker) BuildRequires: perl(Test::CPAN::Meta) BuildRequires: perl(Test::MinimumVersion) BuildRequires: perl(Test::Pod) Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo $version)) %{?perl_default_filter} %description HTTP::Lite is a stand-alone lightweight HTTP/1.1 implementation for perl. It is not intended as a replacement for the fully-features LWP module. Instead, it is intended for use in situations where it is desirable to install the minimal number of modules to achieve HTTP support, or where LWP is not a good candidate due to CPU overhead, such as slower processors. HTTP::Lite is also significantly faster than LWP. %prep %setup -q -n HTTP-Lite-%{version} %build %{__perl} Makefile.PL INSTALLDIRS=vendor make %{?_smp_mflags} %install rm -rf $RPM_BUILD_ROOT make pure_install DESTDIR=$RPM_BUILD_ROOT find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \; find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \; %{_fixperms} $RPM_BUILD_ROOT/* %check # most real tests require network access - ignore skipping test on this # platform messages RELEASE_TESTING=1 make test %clean rm -rf $RPM_BUILD_ROOT %files %defattr(-,root,root,-) %doc Changes LICENSE README %{perl_vendorlib}/* %{_mandir}/man3/* %changelog * Thu May 06 2010 Iain Arnell 2.2-1 - Specfile autogenerated by cpanspec 1.78. Index: .cvsignore === RCS file: /cvs/pkgs/rpms/perl-HTTP-Lite/devel/.cvsignore,v retrieving revision 1.1 retrieving revision 1.2 diff -u -p -r1.1 -r1.2 --- .cvsignore 11 May 2010 04:54:14 - 1.1 +++ .cvsignore 13 May 2010 07:20:45 - 1.2 @@ -0,0 +1 @@ +HTTP-Lite-2.2.tar.gz Index: sources === RCS file: /cvs/pkgs/rpms/perl-HTTP-Lite/devel/sources,v retrieving revision 1.1 retrieving revision 1.2 diff -u -p -r1.1 -r1.2 --- sources 11 May 2010 04:54:14 - 1.1 +++ sources 13 May 2010 07:20:45 - 1.2 @@ -0,0 +1 @@ +149651593132db8f3b06349a67cab77f HTTP-Lite-2.2.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
rpms/perl-HTTP-Lite/F-13 perl-HTTP-Lite.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
Author: iarnell Update of /cvs/pkgs/rpms/perl-HTTP-Lite/F-13 In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv29846/F-13 Modified Files: .cvsignore sources Added Files: perl-HTTP-Lite.spec Log Message: initial import --- NEW FILE perl-HTTP-Lite.spec --- Name: perl-HTTP-Lite Version:2.2 Release:1%{?dist} Summary:Lightweight HTTP implementation License:GPL+ or Artistic Group: Development/Libraries URL:http://search.cpan.org/dist/HTTP-Lite/ Source0: http://www.cpan.org/authors/id/A/AD/ADAMK/HTTP-Lite-%{version}.tar.gz BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) BuildArch: noarch BuildRequires: perl(ExtUtils::MakeMaker) BuildRequires: perl(Test::CPAN::Meta) BuildRequires: perl(Test::MinimumVersion) BuildRequires: perl(Test::Pod) Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo $version)) %{?perl_default_filter} %description HTTP::Lite is a stand-alone lightweight HTTP/1.1 implementation for perl. It is not intended as a replacement for the fully-features LWP module. Instead, it is intended for use in situations where it is desirable to install the minimal number of modules to achieve HTTP support, or where LWP is not a good candidate due to CPU overhead, such as slower processors. HTTP::Lite is also significantly faster than LWP. %prep %setup -q -n HTTP-Lite-%{version} %build %{__perl} Makefile.PL INSTALLDIRS=vendor make %{?_smp_mflags} %install rm -rf $RPM_BUILD_ROOT make pure_install DESTDIR=$RPM_BUILD_ROOT find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \; find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \; %{_fixperms} $RPM_BUILD_ROOT/* %check # most real tests require network access - ignore skipping test on this # platform messages RELEASE_TESTING=1 make test %clean rm -rf $RPM_BUILD_ROOT %files %defattr(-,root,root,-) %doc Changes LICENSE README %{perl_vendorlib}/* %{_mandir}/man3/* %changelog * Thu May 06 2010 Iain Arnell 2.2-1 - Specfile autogenerated by cpanspec 1.78. Index: .cvsignore === RCS file: /cvs/pkgs/rpms/perl-HTTP-Lite/F-13/.cvsignore,v retrieving revision 1.1 retrieving revision 1.2 diff -u -p -r1.1 -r1.2 --- .cvsignore 11 May 2010 04:54:14 - 1.1 +++ .cvsignore 13 May 2010 07:20:45 - 1.2 @@ -0,0 +1 @@ +HTTP-Lite-2.2.tar.gz Index: sources === RCS file: /cvs/pkgs/rpms/perl-HTTP-Lite/F-13/sources,v retrieving revision 1.1 retrieving revision 1.2 diff -u -p -r1.1 -r1.2 --- sources 11 May 2010 04:54:14 - 1.1 +++ sources 13 May 2010 07:20:45 - 1.2 @@ -0,0 +1 @@ +149651593132db8f3b06349a67cab77f HTTP-Lite-2.2.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
rpms/perl-HTTP-Lite/F-11 perl-HTTP-Lite.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
Author: iarnell Update of /cvs/pkgs/rpms/perl-HTTP-Lite/F-11 In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv29846/F-11 Modified Files: .cvsignore sources Added Files: perl-HTTP-Lite.spec Log Message: initial import --- NEW FILE perl-HTTP-Lite.spec --- Name: perl-HTTP-Lite Version:2.2 Release:1%{?dist} Summary:Lightweight HTTP implementation License:GPL+ or Artistic Group: Development/Libraries URL:http://search.cpan.org/dist/HTTP-Lite/ Source0: http://www.cpan.org/authors/id/A/AD/ADAMK/HTTP-Lite-%{version}.tar.gz BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) BuildArch: noarch BuildRequires: perl(ExtUtils::MakeMaker) BuildRequires: perl(Test::CPAN::Meta) BuildRequires: perl(Test::MinimumVersion) BuildRequires: perl(Test::Pod) Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo $version)) %{?perl_default_filter} %description HTTP::Lite is a stand-alone lightweight HTTP/1.1 implementation for perl. It is not intended as a replacement for the fully-features LWP module. Instead, it is intended for use in situations where it is desirable to install the minimal number of modules to achieve HTTP support, or where LWP is not a good candidate due to CPU overhead, such as slower processors. HTTP::Lite is also significantly faster than LWP. %prep %setup -q -n HTTP-Lite-%{version} %build %{__perl} Makefile.PL INSTALLDIRS=vendor make %{?_smp_mflags} %install rm -rf $RPM_BUILD_ROOT make pure_install DESTDIR=$RPM_BUILD_ROOT find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \; find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \; %{_fixperms} $RPM_BUILD_ROOT/* %check # most real tests require network access - ignore skipping test on this # platform messages RELEASE_TESTING=1 make test %clean rm -rf $RPM_BUILD_ROOT %files %defattr(-,root,root,-) %doc Changes LICENSE README %{perl_vendorlib}/* %{_mandir}/man3/* %changelog * Thu May 06 2010 Iain Arnell 2.2-1 - Specfile autogenerated by cpanspec 1.78. Index: .cvsignore === RCS file: /cvs/pkgs/rpms/perl-HTTP-Lite/F-11/.cvsignore,v retrieving revision 1.1 retrieving revision 1.2 diff -u -p -r1.1 -r1.2 --- .cvsignore 11 May 2010 04:54:14 - 1.1 +++ .cvsignore 13 May 2010 07:20:44 - 1.2 @@ -0,0 +1 @@ +HTTP-Lite-2.2.tar.gz Index: sources === RCS file: /cvs/pkgs/rpms/perl-HTTP-Lite/F-11/sources,v retrieving revision 1.1 retrieving revision 1.2 diff -u -p -r1.1 -r1.2 --- sources 11 May 2010 04:54:14 - 1.1 +++ sources 13 May 2010 07:20:44 - 1.2 @@ -0,0 +1 @@ +149651593132db8f3b06349a67cab77f HTTP-Lite-2.2.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
rpms/perl-HTTP-Lite/devel perl-HTTP-Lite.spec,1.1,1.2
Author: iarnell Update of /cvs/pkgs/rpms/perl-HTTP-Lite/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv32033 Modified Files: perl-HTTP-Lite.spec Log Message: * Thu May 13 2010 Iain Arnell iarn...@gmail.com 2.2-2 - bump for rebuild against perl 5.12.0 Index: perl-HTTP-Lite.spec === RCS file: /cvs/pkgs/rpms/perl-HTTP-Lite/devel/perl-HTTP-Lite.spec,v retrieving revision 1.1 retrieving revision 1.2 diff -u -p -r1.1 -r1.2 --- perl-HTTP-Lite.spec 13 May 2010 07:20:45 - 1.1 +++ perl-HTTP-Lite.spec 13 May 2010 07:23:24 - 1.2 @@ -1,6 +1,6 @@ Name: perl-HTTP-Lite Version:2.2 -Release:1%{?dist} +Release:2%{?dist} Summary:Lightweight HTTP implementation License:GPL+ or Artistic Group: Development/Libraries @@ -56,5 +56,8 @@ rm -rf $RPM_BUILD_ROOT %{_mandir}/man3/* %changelog +* Thu May 13 2010 Iain Arnell iarn...@gmail.com 2.2-2 +- bump for rebuild against perl 5.12.0 + * Thu May 06 2010 Iain Arnell 2.2-1 - Specfile autogenerated by cpanspec 1.78. -- 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-WWW-Mechanize-1.28.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Test-WWW-Mechanize: 6f4b87f8502cf5096be8b03ae5b76d86 Test-WWW-Mechanize-1.28.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: perl 5.12 status
On Thu, May 13, 2010 at 08:43:27AM +0200, Iain Arnell wrote: 2010/5/12 Marcela Mašláňová mmasl...@redhat.com: perl-Catalyst-Action-RenderView perl-Catalyst-Authentication-Store-DBIx-Class perl-Catalyst-Controller-FormBuilder perl-Catalyst-Devel perl-Catalyst-Helper-FastCGI-ExternalServer perl-Catalyst-Model-DBIC-Schema perl-Catalyst-Model-LDAP perl-Catalyst-Model-XMLRPC perl-Catalyst-Plugin-Authentication perl-Catalyst-Plugin-Authorization-ACL perl-Catalyst-Plugin-ConfigLoader perl-Catalyst-Plugin-Session perl-Catalyst-Plugin-Session-State-Cookie perl-Catalyst-Plugin-StackTrace perl-Catalyst-Plugin-Static-Simple perl-Catalyst-Plugin-SubRequest perl-Catalyst-Runtime perl-Catalyst-View-PDF-Reuse perl-Catalyst-View-TT perl-namespace-autoclean perl-namespace-clean All of the above successfully rebuilt now. Great. Attached is graph with build-time dependencies against F-12 update-testing. Good news: The depth is not so horrible as on previous graph. -- Petr attachment: graph-20100513-testing.svgz pgpO8cntT7WCe.pgp Description: PGP signature -- 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
rpms/perl-Data-FormValidator-Constraints-DateTime/devel 03-03-2010.patch, NONE, 1.1 perl-Data-FormValidator-Constraints-DateTime.spec, 1.4, 1.5
Author: iarnell Update of /cvs/pkgs/rpms/perl-Data-FormValidator-Constraints-DateTime/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv5433 Modified Files: perl-Data-FormValidator-Constraints-DateTime.spec Added Files: 03-03-2010.patch Log Message: * Thu May 13 2010 Iain Arnell iarn...@gmail.com 1.09-5 - fix FTBFS - tests fail after 03/03/2010 03-03-2010.patch: 3x_dates.t |2 +- dates.t|2 +- 2 files changed, 2 insertions(+), 2 deletions(-) --- NEW FILE 03-03-2010.patch --- diff -up Data-FormValidator-Constraints-DateTime-1.09/t/3x_dates.t.orig Data-FormValidator-Constraints-DateTime-1.09/t/3x_dates.t --- Data-FormValidator-Constraints-DateTime-1.09/t/3x_dates.t.orig 2005-12-19 23:08:18.0 +0100 +++ Data-FormValidator-Constraints-DateTime-1.09/t/3x_dates.t 2010-05-13 12:14:45.0 +0200 @@ -15,7 +15,7 @@ my $real_bad_date = '2'; my $today = DateTime-today-mdy('-'); # these are relative to the above $good_date; my $distant_future_date = '03-03-2110'; -my $future_date = '03-03-2010'; +my $future_date = '03-03-2020'; my $past_date = '03-03-1979'; my $distant_past_date = '03-03-1879'; diff -up Data-FormValidator-Constraints-DateTime-1.09/t/dates.t.orig Data-FormValidator-Constraints-DateTime-1.09/t/dates.t --- Data-FormValidator-Constraints-DateTime-1.09/t/dates.t.orig 2005-12-19 23:08:18.0 +0100 +++ Data-FormValidator-Constraints-DateTime-1.09/t/dates.t 2010-05-13 12:14:52.0 +0200 @@ -21,7 +21,7 @@ my $real_bad_date = '2'; my $today = DateTime-today-mdy('-'); # these are relative to the above $good_date; my $distant_future_date = '03-03-2110'; -my $future_date = '03-03-2010'; +my $future_date = '03-03-2020'; my $past_date = '03-03-1979'; my $distant_past_date = '03-03-1879'; Index: perl-Data-FormValidator-Constraints-DateTime.spec === RCS file: /cvs/pkgs/rpms/perl-Data-FormValidator-Constraints-DateTime/devel/perl-Data-FormValidator-Constraints-DateTime.spec,v retrieving revision 1.4 retrieving revision 1.5 diff -u -p -r1.4 -r1.5 --- perl-Data-FormValidator-Constraints-DateTime.spec 30 Apr 2010 13:32:26 - 1.4 +++ perl-Data-FormValidator-Constraints-DateTime.spec 13 May 2010 10:23:57 - 1.5 @@ -1,11 +1,15 @@ Name: perl-Data-FormValidator-Constraints-DateTime Version:1.09 -Release:4%{?dist} +Release:5%{?dist} Summary:D::FV constraints for dates and times License:GPL+ or Artistic Group: Development/Libraries URL: http://search.cpan.org/dist/Data-FormValidator-Constraints-DateTime/ Source0: http://www.cpan.org/authors/id/W/WO/WONKO/Data-FormValidator-Constraints-DateTime-%{version}.tar.gz +# http://rt.cpan.org/Ticket/Display.html?id=57456 +# tests fail after 03/03/2010 +Patch0: 03-03-2010.patch + BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) BuildArch: noarch BuildRequires: perl(Data::FormValidator) @@ -30,6 +34,7 @@ strings that would be properly formatted %prep %setup -q -n Data-FormValidator-Constraints-DateTime-%{version} +%patch0 -p1 %build %{__perl} Build.PL installdirs=vendor @@ -56,6 +61,9 @@ rm -rf $RPM_BUILD_ROOT %{_mandir}/man3/* %changelog +* Thu May 13 2010 Iain Arnell iarn...@gmail.com 1.09-5 +- fix FTBFS - tests fail after 03/03/2010 + * Fri Apr 30 2010 Marcela Maslanova mmasl...@redhat.com - 1.09-4 - Mass rebuild with perl-5.12.0 -- 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
rpms/perl-CatalystX-LeakChecker/devel .cvsignore, 1.2, 1.3 perl-CatalystX-LeakChecker.spec, 1.2, 1.3 sources, 1.2, 1.3
Author: mmaslano Update of /cvs/pkgs/rpms/perl-CatalystX-LeakChecker/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv31129 Modified Files: .cvsignore perl-CatalystX-LeakChecker.spec sources Log Message: * Fri Apr 30 2010 Marcela Maslanova mmasl...@redhat.com - 0.05-2 - Mass rebuild with perl-5.12.0 Index: .cvsignore === RCS file: /cvs/pkgs/rpms/perl-CatalystX-LeakChecker/devel/.cvsignore,v retrieving revision 1.2 retrieving revision 1.3 diff -u -p -r1.2 -r1.3 --- .cvsignore 16 Mar 2010 03:42:55 - 1.2 +++ .cvsignore 13 May 2010 10:55:10 - 1.3 @@ -1 +1 @@ -CatalystX-LeakChecker-0.05.tar.gz +CatalystX-LeakChecker-0.06.tar.gz Index: perl-CatalystX-LeakChecker.spec === RCS file: /cvs/pkgs/rpms/perl-CatalystX-LeakChecker/devel/perl-CatalystX-LeakChecker.spec,v retrieving revision 1.2 retrieving revision 1.3 diff -u -p -r1.2 -r1.3 --- perl-CatalystX-LeakChecker.spec 30 Apr 2010 01:53:25 - 1.2 +++ perl-CatalystX-LeakChecker.spec 13 May 2010 10:55:10 - 1.3 @@ -1,7 +1,7 @@ Name: perl-CatalystX-LeakChecker Summary:Debug memory leaks in Catalyst applications -Version:0.05 -Release:2%{?dist} +Version:0.06 +Release:1%{?dist} License:GPL+ or Artistic Group: Development/Libraries Source0: http://search.cpan.org/CPAN/authors/id/F/FL/FLORA/CatalystX-LeakChecker-%{version}.tar.gz Index: sources === RCS file: /cvs/pkgs/rpms/perl-CatalystX-LeakChecker/devel/sources,v retrieving revision 1.2 retrieving revision 1.3 diff -u -p -r1.2 -r1.3 --- sources 16 Mar 2010 03:42:55 - 1.2 +++ sources 13 May 2010 10:55:10 - 1.3 @@ -1 +1 @@ -c6227507da51072f2ef34ea164346bf3 CatalystX-LeakChecker-0.05.tar.gz +5cba5ffbbdedb754fe4d260fb1727acd CatalystX-LeakChecker-0.06.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
File MooseX-Params-Validate-0.14.tar.gz uploaded to lookaside cache by mmaslano
A file has been added to the lookaside cache for perl-MooseX-Params-Validate: 550ff3a83365ab48065f52562cf1ba23 MooseX-Params-Validate-0.14.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
rpms/perl-Data-FormValidator-Constraints-DateTime/devel .cvsignore, 1.2, 1.3 perl-Data-FormValidator-Constraints-DateTime.spec, 1.5, 1.6 sources, 1.2, 1.3 03-03-2010.patch, 1.1, NONE
Author: iarnell Update of /cvs/pkgs/rpms/perl-Data-FormValidator-Constraints-DateTime/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv16233 Modified Files: .cvsignore perl-Data-FormValidator-Constraints-DateTime.spec sources Removed Files: 03-03-2010.patch Log Message: * Fri May 14 2010 Iain Arnell iarn...@gmail.com 1.10-1 - update to latest upstream - drop 03-03-2010.patch Index: .cvsignore === RCS file: /cvs/pkgs/rpms/perl-Data-FormValidator-Constraints-DateTime/devel/.cvsignore,v retrieving revision 1.2 retrieving revision 1.3 diff -u -p -r1.2 -r1.3 --- .cvsignore 4 May 2009 23:13:00 - 1.2 +++ .cvsignore 14 May 2010 05:35:49 - 1.3 @@ -1 +1 @@ -Data-FormValidator-Constraints-DateTime-1.09.tar.gz +Data-FormValidator-Constraints-DateTime-1.10.tar.gz Index: perl-Data-FormValidator-Constraints-DateTime.spec === RCS file: /cvs/pkgs/rpms/perl-Data-FormValidator-Constraints-DateTime/devel/perl-Data-FormValidator-Constraints-DateTime.spec,v retrieving revision 1.5 retrieving revision 1.6 diff -u -p -r1.5 -r1.6 --- perl-Data-FormValidator-Constraints-DateTime.spec 13 May 2010 10:23:57 - 1.5 +++ perl-Data-FormValidator-Constraints-DateTime.spec 14 May 2010 05:35:49 - 1.6 @@ -1,14 +1,11 @@ Name: perl-Data-FormValidator-Constraints-DateTime -Version:1.09 -Release:5%{?dist} +Version:1.10 +Release:1%{?dist} Summary:D::FV constraints for dates and times License:GPL+ or Artistic Group: Development/Libraries URL: http://search.cpan.org/dist/Data-FormValidator-Constraints-DateTime/ Source0: http://www.cpan.org/authors/id/W/WO/WONKO/Data-FormValidator-Constraints-DateTime-%{version}.tar.gz -# http://rt.cpan.org/Ticket/Display.html?id=57456 -# tests fail after 03/03/2010 -Patch0: 03-03-2010.patch BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) BuildArch: noarch @@ -34,7 +31,6 @@ strings that would be properly formatted %prep %setup -q -n Data-FormValidator-Constraints-DateTime-%{version} -%patch0 -p1 %build %{__perl} Build.PL installdirs=vendor @@ -61,6 +57,10 @@ rm -rf $RPM_BUILD_ROOT %{_mandir}/man3/* %changelog +* Fri May 14 2010 Iain Arnell iarn...@gmail.com 1.10-1 +- update to latest upstream +- drop 03-03-2010.patch + * Thu May 13 2010 Iain Arnell iarn...@gmail.com 1.09-5 - fix FTBFS - tests fail after 03/03/2010 Index: sources === RCS file: /cvs/pkgs/rpms/perl-Data-FormValidator-Constraints-DateTime/devel/sources,v retrieving revision 1.2 retrieving revision 1.3 diff -u -p -r1.2 -r1.3 --- sources 4 May 2009 23:13:00 - 1.2 +++ sources 14 May 2010 05:35:50 - 1.3 @@ -1 +1 @@ -adec700adf05d817e09e890d99d9a339 Data-FormValidator-Constraints-DateTime-1.09.tar.gz +2c233c7234eac0c7705db9195075b5d1 Data-FormValidator-Constraints-DateTime-1.10.tar.gz --- 03-03-2010.patch DELETED --- -- 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
rpms/perl-Dist-Zilla/devel perl-Dist-Zilla.spec,1.2,1.3
Author: iarnell Update of /cvs/pkgs/rpms/perl-Dist-Zilla/devel In directory cvs01.phx2.fedoraproject.org:/tmp/cvs-serv16785 Modified Files: perl-Dist-Zilla.spec Log Message: * Fri May 14 2010 Iain Arnell - 2.101310-2 - bump for rebuild in dist-f14 Index: perl-Dist-Zilla.spec === RCS file: /cvs/pkgs/rpms/perl-Dist-Zilla/devel/perl-Dist-Zilla.spec,v retrieving revision 1.2 retrieving revision 1.3 diff -u -p -r1.2 -r1.3 --- perl-Dist-Zilla.spec13 May 2010 05:32:01 - 1.2 +++ perl-Dist-Zilla.spec14 May 2010 05:39:00 - 1.3 @@ -1,6 +1,6 @@ Name: perl-Dist-Zilla Version:2.101310 -Release:1%{?dist} +Release:2%{?dist} Summary:Distribution builder; installer not included! License:GPL+ or Artistic Group: Development/Libraries @@ -118,6 +118,9 @@ rm -rf $RPM_BUILD_ROOT %{_mandir}/man3/* %changelog +* Fri May 14 2010 Iain Arnell - 2.101310-2 +- bump for rebuild in dist-f14 + * Thu May 13 2010 Iain Arnell iarn...@gmail.com 2.101310-1 - update to latest upstream version -- 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