Re: RPM Soft dependencies (Was: Re: Agenda for the 2009-05-26 Packaging Committee meeting)
Toshio Kuratomi wrote: What is the behaviour when a package with soft deps on another package is upgraded and the soft dependency is currently not installed? I do not know how Mandriva handle it, but in Debian it works like this: Old package A require nothing. New package A: Require B Suggest C $ apt-get upgrade Following package will be upgraded: A Suggested packages: C Following packages will be installed to satisfy dependecies: B Install [Y/n]: I.e. requires are automatically picked up. But suggested packages are not selected and you get only information about them. And if you install using some higher tool (aptitude, dselect), after you leave screen with package selection, then screen like this will appear: Installed/Selection NameVersion Available Version yy A 1.0 2.0 _y B 1.0 __ C 1.0 And you may or may not select the suggested package. -- Miroslav Suchy Red Hat Satellite Engineering -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01
There is much more information that can be pulled via a turbogrears app we are running. But I am looking to see what is useful in terms of a weekly report. I have the date tuesday to tuesday as it matches up with the Bugzappers meeting time. Hi, thanks for the stats. I'd like to see there additional stats for fedora 9, 10, rawhide: - overall number of opened bugs - number of new bugs in last x days - number of closed bugs in last x days Would it be possible? Michal -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Swapping reviews
On Fri, 2009-05-29 at 19:49 +0200, Xavier Bachelot wrote: I have a webcalendar package I never submitted. You may want to take a look and if you find anything you like, feel free to take. Thanks Xavier, I looked at your package, but it seems to suffer from the same weakness as mine: bundled modules :-( -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaned eclipse-pydev
- Christoph Höger choe...@cs.tu-berlin.de wrote: Isn't that this application with ads in it? Mmm, not aware of any... Not sure what you meant. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaned eclipse-pydev
Isn't that this application with ads in it? Mmm, not aware of any... Not sure what you meant. If you use the evaluation version of Pydev Extensions (a different plugin to Pydev), it reminds you every so often to buy the full version. See: http://fabioz.com/pydev/ The basic Pydev doesn't have these popups. Rich -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Unbootable machine
On 06/02/09 13:48, Bernie Innocenti wrote: On 06/02/09 07:10, H. Peter Anvin wrote: Bernie Innocenti wrote: Ok, I wiped mbr and made fdisk create a new one: Disk /dev/sdb: 2055 MB, 2055208960 bytes 64 heads, 62 sectors/track, 1011 cylinders ^^ Equally weird. The only standard ones are 64 heads, 32 sectors and 255 heads, 63 sectors. Shouldn't fdisk guess these values automagically? And, more importantly, who are we going to blame if it doesn't? ;-) For the record, GNU parted gets it right: ber...@giskard:~$ sudo dd if=/dev/zero of=/dev/sdb ^C5017+0 records in 5017+0 records out 2568704 bytes (2.6 MB) copied, 1.63415 s, 1.6 MB/s 130!ber...@giskard:~$ sudo parted /dev/sdb GNU Parted 1.8.8 Using /dev/sdb Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) mklabel New disk label type? msdos (parted) unit chs (parted) print Model: USB DISK 2.0 (scsi) Disk /dev/sdb: 249,220,34 Sector size (logical/physical): 512B/512B BIOS cylinder,head,sector geometry: 249,255,63. Each cylinder is 8225kB. Partition Table: msdos Number Start End Type File system Flags (parted) mkpart File system type? [ext2]? fat32 Start? 0 End? 100% Warning: You requested a partition from 0,0,0 to 249,220,34. The closest location we can manage is 0,1,0 to 248,254,62. Is this still acceptable to you? Yes/No? y (parted) p Model: USB DISK 2.0 (scsi) Disk /dev/sdb: 249,220,34 Sector size (logical/physical): 512B/512B BIOS cylinder,head,sector geometry: 249,255,63. Each cylinder is 8225kB. Partition Table: msdos Number Start End Type File system Flags 1 0,1,0 248,254,62 primary lba -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
awesfx package reinclusion
Hello i'm new to this list; i submitted a new review request: https://bugzilla.redhat.com/show_bug.cgi?id=490061 in order to re-include the awesfx package which was retired on apr 2008: http://fedoraproject.org/wiki/PackageMaintainers/RetiredPackages Could someone give me some hints on the procedure? Should i reverse actions described here: http://fedoraproject.org/wiki/PackageMaintainers/PackageEndOfLife or treat the package as a new one? thanks -- Guido Grazioli guido.grazi...@gmail.com Via Parri 11 48011 - Alfonsine (RA) Mobile: +39 347 1017202 (10-18) Key FP = 7040 F398 0DED A737 7337 DAE1 12DC A698 5E81 2278 Linked in: http://www.linkedin.com/in/guidograzioli -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Orphaned eclipse-pydev
- Richard Fearn richardfe...@gmail.com wrote: Isn't that this application with ads in it? Mmm, not aware of any... Not sure what you meant. If you use the evaluation version of Pydev Extensions (a different plugin to Pydev), it reminds you every so often to buy the full version. See: http://fabioz.com/pydev/ The basic Pydev doesn't have these popups. Rich I see. Well, we use Pydev from SF.net [1] and no Pydev Extensions [2], so, no ads in Fedora. Michal -- [1] http://pydev.sourceforge.net/ [2] http://fabioz.com/pydev/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: [Sugar-devel] Unbootable machine
Jonas Smedegaard wrote: Also look for how you have configured your BIOS... some Award BIOSes have USB-ZIP, USB-HDD, USB-FDD configurations; you generally want USB-HDD. In my (older non-Sugar) experience, USB-HDD is best, then USB-ZIP, and if none of those options are available then pick USB-FDD (which is then most likely names something else). This is absolutely the order of preference. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01
On Mon, Jun 1, 2009 at 11:32 PM, Brennan Ashton bash...@brennanashton.com wrote: There is much more information that can be pulled via a turbogrears app we are running. But I am looking to see what is useful in terms of a weekly report. I have the date tuesday to tuesday as it matches up with the Bugzappers meeting time. Are you geared up for component by component reporting or perhaps groups of components? How do triagers currently organize their time when picking components? Would component-by-component reporting help spread/grow triage manpower into hot spot areas of the repository? And the flipside, can you visualize how triage manpower is actually spread through the repository currently? Are our expert smoke jumpers landing near the hotspots without a lot of coordinated effort? or is triage being done mostly by maintainers, fighting the local fires in their back yards? And in the future I'd like to see weekly reporting feature by feature that gives a sense of progress on bugs loosely associated with a feature proposal. Can we visualize the effect that feature specific test days have on the bug lifecycle for that feature? Also reporting on tracking the aggregate progress on tracker/blocker bugs for the next release. Can you highlight work or drive interest in working on release target and blocker bugs in some way in the reporting? . -jefSaw my first smoke jumpers in action like a mile away from me last weekend...hence the imageryspaleta -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
access to a ppc64 machine for bigloo's upstream
Hi, is here anybody that could give access to a ppc64 machine to bigloo's upstream? The builds of bigloo on ppc64 (and s390x) gets stuck and they are willing to debug/fix it, but need a ppc64 machine. their homepage is http://www-sop.inria.fr/mimosa/fp/Bigloo/ failing builds https://koji.fedoraproject.org/koji/taskinfo?taskID=1389648 (internal copy of gc) https://koji.fedoraproject.org/koji/taskinfo?taskID=1389647 (using packaged gc) thread on upstream mailing list http://thread.gmane.org/gmane.lisp.scheme.bigloo/4289 Thanks Dan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
rawhide report: 20090602 changes
Compose started at Tue Jun 2 06:15:08 UTC 2009 Updated Packages: anaconda-11.5.0.58-1.fc11 - * Sun May 31 2009 David Lehman dleh...@redhat.com - 11.5.0.58-1 - Pass --force to lvresize so it doesn't ask for confirmation. (dlehman) - Fix a typo in action sorting for resize actions (fs vs. device). (#501000) (dlehman) - Sending translation for French (mrtom) mkinitrd-6.0.86-2.fc11 -- * Fri May 29 2009 Peter Jones pjo...@redhat.com - 6.0.86-2 - Require kbd package so keyboard settings will work right after initial installation. (#501584) Summary: Added Packages: 0 Removed Packages: 0 Modified Packages: 2 Broken deps for ppc64 -- cabal2spec-0.12-1.fc11.noarch requires ghc 0:6.10.1-7 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01
On Tue, Jun 2, 2009 at 8:53 AM, Adam Williamson awill...@redhat.com wrote: It could do, but on the other hand, we're mostly getting to the point where the components that lack coverage are ones which need a triager who's already knowledgeable about that component: we can't just parachute someone in. (see e.g. anaconda and kernel). How short is that list of components? Can you visualize that? Just identifying that finite list could help motivate exactly that sort of recruitment effort needed to fill the need. If we identify the short list accurately, can we then advertise the short list as a rewarding challenge to undertake? Our very own elite highly trained specialists..our 00's..our A-team. So highly prized they even get codenames and catch phrases. -jef -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: access to a ppc64 machine for bigloo's upstream
On Tue, Jun 02, 2009 at 06:41:49PM +0200, Dan Horák wrote: Hi, is here anybody that could give access to a ppc64 machine to bigloo's upstream? The builds of bigloo on ppc64 (and s390x) gets stuck and they are willing to debug/fix it, but need a ppc64 machine. Email me an ssh pubkey and your preferred login and I'll give you an account on my G5 running rawhide josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01
On Tue, 2009-06-02 at 09:08 -0800, Jeff Spaleta wrote: On Tue, Jun 2, 2009 at 8:53 AM, Adam Williamson awill...@redhat.com wrote: It could do, but on the other hand, we're mostly getting to the point where the components that lack coverage are ones which need a triager who's already knowledgeable about that component: we can't just parachute someone in. (see e.g. anaconda and kernel). How short is that list of components? Can you visualize that? Just identifying that finite list could help motivate exactly that sort of recruitment effort needed to fill the need. If we identify the short list accurately, can we then advertise the short list as a rewarding challenge to undertake? Our very own elite highly trained specialists..our 00's..our A-team. So highly prized they even get codenames and catch phrases. Anything on the Components and Triagers page where there's no-one under Active Triagers. :) (oh, and Need help? is not set to No). Currently that list is: PackageKit firstboot gdm glibc gtk2 mkinitrd upstart as I said, these are bits that you kinda need decent expertise on to be able to triage properly. PackageKit might be the lowest-hanging fruit on that list. you can add: pulseaudio anaconda kernel each of these currently isn't really being triaged by any triagers. Lennart is happy to have triage for PA, but only from someone who already knows what they're talking about when it comes to PA in quite some detail (which is quite a small pool). I'm currently working with the anaconda / kernel folks to see what we can do about setting down the requirements for triage for those components. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On 01.06.2009 20:14, Jesse Keating wrote: On Mon, 2009-06-01 at 19:49 +0200, Thorsten Leemhuis wrote: On 29.05.2009 22:57, Jesse Keating wrote: Thx for your reply and sorry, I didn't found time to answer earlier. Some more comments: [...] - how about reducing the number or zero day updates (which is ridiculous high for F11) by setting a different, later freeze date for all packages that are neither on the install DVD or on a Spin? That's a bit hard to determine easily and programaticaly. I've all but given up on my quest to reduce the number of updates. Just a general comment, not relevant for the Announcing Fedora Activity Day. I'm glad that you gave up that quest, as Fedora gets lot's of updates is afaics a reason why a lot people actually use or contribute to Fedora. But that doesn't matter much. What I really want to say: I totally agree with this: It's just doesn't seem to be in line with the desires of the package maintainers, whether or not it's in line with the desires of (some of) the project leaders. It IMHO shows a big and more and more pressing problem in Fedora: Packagers and leadership are not working towards the same direction. Anyway, back to topic: - other distributions seems to manage a whole lot more test releases (e.g. alphas, beta, RC, milestones, ...) per devel cycle; is that something we should aim for as well? If there was a way to do it without adding stress and work needed to teams like releng, installer, etc.. [...] One comment: *from a outside* it often looks a bit like - some (not all) people go crazy for weeks or months and ignore some of those bugs that are not pressing, but nevertheless pressing (e.g. kind of bugs that tend to land on target or blocker tracker bugs or already are there) - then you send a reminder there will be a a test release next week - people suddenly wake up and try to fix those bugs for the test release - they notice: arghh, serious things are broken, we need more time; can we please slip? - we slip Maybe more target dates where people should get things into shape might help to reduce the work for the real test/final releases. - how about doing something like a cp -l development devel-snapshot now and then (once a week) when we know rawhide is mostly working? The rawhide trees for at least the past month are kept in the Fedora infrastructure and are even available by a public url. We haven't tagged any of them as stable though. They are afaics way to far away/way to slow to reach to do a proper network install in an acceptable period of time (at least from Germany). Is rsync available -- I'm not aware of it, so I doubt it? - how can we reduce our time between finishing a (test) release and releasing it dramatically? It seems other distributions get new (test) release out to the users a lot quicker then the three to five days days we require, which seems a whole lot for a devel cycle that takes 180 days in total (and we all know how much rawhide can move on with a few days) If we didn't care to let the mirrors sync up we could release it earlier. However what good does that do when nobody can /get/ to the release because none of the mirrors have it, and the ones that do can't help sync to those that don't because users are tying up all the bandwidth? I didn't say to not care. But maybe shorten the time we wait for them and help to get the bits out more quickly; pushing users to use bittorrent more might help a lot as well. - I'd be glad if we could stick to our release targets a lot better. Delaying releases looks quite unprofessional. Delaying also creates trouble for those depending on our releases. Take computer magazines (which have hard deadlines for productions) that might want to ship with a new release on a CD or DVD together with the next issue -- due to our fame in missing deadlines it seems to me that we are a lot more unattractive than Ubuntu (which afaics is on the shelf's here in Germany with new computer magazines just a few days after it has been released) What looks more unprofessional? Delaying the release, or hitting our date and releasing with bugs that eat people's data? Or releasing with broken graphics for large swaths of users? I think you drifted a bit way to far away and into a opposition without need. I for example nowhere said that we should not slip if there is a strong reason to. But my comment was quite open, so it's partly my fault; so let me rephrase: What is rel-eng doing in the next devel cycle to make sure we slip less then we used to in the past? Or does rel-eng think everything was fine and missing three and a half target dates (alpha, beta, release and the first slipped release target date) out of four is acceptable? - why do we have to slip by a whole week most of the time? can't we find ways to slip just a day or two if there really is no way around a delay? The marketing machine has very strongly requested that we only do releases on Tuesdays.
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On 01.06.2009 21:50, Adam Williamson wrote: On Mon, 2009-06-01 at 19:49 +0200, Thorsten Leemhuis wrote: - should we set an way earlier freezes date for things like anaconda, kernel, isolinux, grub and other crucial pieces to make sure they are in better shape a bit earlier and thus are less likely a reason for release slips? If you're basing this off the F11 cycle, it's worth noting that kernel and anaconda have not been 'reasons for release slips' in this cycle in that late changes were made to them which turned out to be bad ideas. I know, but: It was simply that there were bugs in them all along which were critical enough to block the release. An earlier freeze date would not have helped at all. It might have helped to find the problem earlier -- I for example got the impression that a lot of people had problems with the storage rewrite and thus aborted their tests with Alpha or Beta. CU knurd -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
Jesse Keating wrote: On Mon, 2009-06-01 at 20:56 -0500, Bruno Wolff III wrote: Do you hard link the new release files to the ones identical in rawhide so that rsync doesn't have to transfer them to places mirroring rawhide? Yes and no. We do use hardlinks, however the mechanism that gets it from PHX to Raleigh is Netapp snapmirror, which works at the block level. I don't know enough about snapmirror to know if it is helped by hardlinks or not. The individual files aren't the real problem, it's the isos, particularly the live isos. A program similar to Jigdo could speed this up. Transfer only the RPM packages (taking advantage of hard links) and information on what packages are in each ISO image, and then recreate the ISO images at the destination. That way each package would only be transferred once, regardless of how many ISO images it occurs in. Björn Persson signature.asc Description: This is a digitally signed message part. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
Matt Domsch wrote: On Mon, Jun 01, 2009 at 04:03:04PM -0400, Paul W. Frields wrote: I'm getting out of my ken here, but could this be done in stages with I2 connected hosts getting the bits early/first and then moving on to others? We need to move ~130GB to each of ~230 mirrors, in about 4 days. We already have in place a limited amount of tiering. The Tier 0/1 mirrors get the bits first, then downstream mirrors pull from them. We have nearly all our Tier 1 mirrors on I2 (all but the us.kernel.org). Right now it's not mandatory, but no new mirrors (those signed up in the last 18 months or so) have been granted ACL permissions to download from the masters. http://fedoraproject.org/wiki/Infrastructure/Mirroring/Tiering One of my hopes for the F12 cycle is that we will have increased use of tiering and push mirroring. What about dropping hierarchical mirroring altogether? Why hasn't someone developed a distributed (i.e. bittorrent-like) system for mass mirroring? :-) -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- Congratulations! You've won a free trip to the future! All you have to do to claim your prize is wait five minutes... -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On Tue, Jun 2, 2009 at 3:02 PM, Matthew Woehlke mw_tr...@users.sourceforge.net wrote: Matt Domsch wrote: What about dropping hierarchical mirroring altogether? Why hasn't someone developed a distributed (i.e. bittorrent-like) system for mass mirroring? :-) -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- Congratulations! You've won a free trip to the future! All you have to do to claim your prize is wait five minutes... -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list Why not? Might be an interesting idea to pursue. -Adam -- http://maxamillion.googlepages.com - () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
Björn Persson wrote: A program similar to Jigdo could speed this up. Transfer only the RPM packages (taking advantage of hard links) and information on what packages are in each ISO image, and then recreate the ISO images at the destination. That way each package would only be transferred once, regardless of how many ISO images it occurs in. Jigdo doesn't work in Fedora unless you want to implement a self-compiling jigdo creator. Why? 'Cause old Fedora updates are not kept on mirrors. A Jigdo file you create today may not work next week. Bad, bad, bad. k? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
Matthew Woehlke wrote: What about dropping hierarchical mirroring altogether? Why hasn't someone developed a distributed (i.e. bittorrent-like) system for mass mirroring? :-) Already discussed[1][2] on the fedora-test-list. [1] https://www.redhat.com/archives/fedora-test-list/2009-June/msg00032.html [2] https://www.redhat.com/archives/fedora-test-list/2009-June/msg00062.html -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Maintainer Responsibilities
Hello, I don't want to start a long thread, but just to ask a couple questions for my own clarification. Does a maintainer's responsibilities end with packaging bugs? IOW, if there is a problem in the package that is _broken code_ do they need to do something about it or is it acceptable for them to close the bug and say talk to upstream? Do we want those bugs open to track when the bug is fixed in the distro? I'll accept whatever the answer is, I'm just curious. Thanks, -Steve -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On Tue, 2009-06-02 at 21:30 +0200, Thorsten Leemhuis wrote: but if we get RC with the final name transferred to the mirrors ahead of time then they can be updated relative quickly as well, as only a few bit change. We don't do this as it tends to lead to leaks, and confusion as to whether the release has been done or not. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On Tue, 2009-06-02 at 21:12 +0200, Thorsten Leemhuis wrote: It might have helped to find the problem earlier -- I for example got the impression that a lot of people had problems with the storage rewrite and thus aborted their tests with Alpha or Beta. An earlier freeze would have just frozen the work unfinished. The rewrite was a massive undertaking and we knew it was going to take longer than the release cycle to finish. Freezing earlier wouldn't have helped. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
Jesse Keating wrote: An earlier freeze would have just frozen the work unfinished. The rewrite was a massive undertaking and we knew it was going to take longer than the release cycle to finish. Freezing earlier wouldn't have helped. Then it should have been done in a work branch and targeted for a later release. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
Matthew Woehlke wrote: It's too bad fedora-test-list doesn't seem to be on gmane (or isn't named obviously; gmane.org is being too slow for me to ask about the mail address). gmane.linux.redhat.fedora.testers Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
Steve Grubb wrote: I don't want to start a long thread, but just to ask a couple questions for my own clarification. Does a maintainer's responsibilities end with packaging bugs? IOW, if there is a problem in the package that is _broken code_ do they need to do something about it or is it acceptable for them to close the bug and say talk to upstream? It's the reporter's job to report the bug upstream when asked to do so. Fixing bugs often requires two-way communication, so it's important for upstream to have a real reporter to talk to, I don't see why it should be the maintainer's job to play the relaying monkey. We're not carrier pigeons. We can't even CC the reporter on the upstream bug unless they register an account there, and at that point they can just as well file the bug themselves. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On Wed, Jun 03, 2009 at 01:08:15AM +0200, Kevin Kofler wrote: Thorsten Leemhuis wrote: It IMHO shows a big and more and more pressing problem in Fedora: Packagers and leadership are not working towards the same direction. The best solution for that is to change the leadership. :-) So don't vote for the same old hats for FESCo and FPB. Honestly, that is pretty short-sighted. And Thorsten's statement isn't entirely accurate either. Entirely new FESCo and FPB would still be faced with the same problems we have today. Let's look at in a bit more detail. 1) I don't recall ever seeing FESCo or FPB state as a committee that they want fewer packages and updates. If you have a mailing list post to meeting minutes that say that, I would be happy to look at it. 2) The people that _have_ advocated for fewer updates have actual limitations they are facing that would make it desirable. As Jesse said in his reply earlier, it takes 8+ hours to mash rawhide now. It _also_ takes at least 8 hours to do an updates push. We are facing some real limitations on our turn around time for things at the moment and they are only going to get worse as we have newer releases that will get the delta rpms. At the same time, the same people are getting raked over the coals for not getting bits out fast enough. We are working on this from a rel-eng standpoint, but advocating for a bit of discretion on what should be pushed as an update is not entirely a bad thing. Personally, I would love it if package maintainers slowed down a bit. But it's not an end solution. So certainly the leadership, defined as FESCo and FPB, is not in conflict with the contributor's apparent direction. As far as I can see, they haven't made a statement either way. If there is a group that was pushing for something that ran contrary, it was Rel-Eng. And given that Jesse and I both just said we're going to basically stop begging people to slow down on updates, I think even that group is trying to figure out a way to make things better. Hell, that's partly what this FAD is all about. So, please. The rhetoric isn't really needed, it's not productive, and it's just going to stir things up more than necessary. Maybe more target dates where people should get things into shape might help to reduce the work for the real test/final releases. Actually a better strategy is to just schedule the release a few weeks earlier than when you actually want to release, then the slips will make it hit the real target date very closely. :-) Except our schedule is public and open. So whatever we say the date is, pretend or not, is the date that people will expect and target. josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Announcing Fedora Activity Day - Fedora Development Cycle 2009
On Wed, Jun 03, 2009 at 01:10:14AM +0200, Kevin Kofler wrote: Jesse Keating wrote: An earlier freeze would have just frozen the work unfinished. The rewrite was a massive undertaking and we knew it was going to take longer than the release cycle to finish. Freezing earlier wouldn't have helped. Then it should have been done in a work branch and targeted for a later release. You have a point, but for something like anaconda you really need it to be installable and tested via installs. Simply branching the package isn't enough, since you need actual composes with the branched code in it. Not impossible to do, but when we have trouble getting people to test rawhide already I'm not sure diluting our test pool that way is a great answer. josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Fedora Elections: Town Hall schedule set, beginning in 12 hours
With each of the candidates noting they can attend at least one of the IRC Town Halls for their respective offices, the schedule I proposed is now set. Town Halls begin in about 12 hours. Each group participating in the election will host two Town Hall sessions on IRC. Each will last one hour, or less if there are no further questions. How to Join * Everyone should join #fedora-townhall on FreeNode (irc.freenode.net). Only candidates and a moderator may speak in this channel. * Non-candidates should also join #fedora-townhall-public on FreeNode (irc.freenode.net). Direct your questions for the candidates to the moderator. FESCo Candidate forum Wednesday, June 3, 1400 UTC (10am US Eastern Daylight Time, 7am US Pacific Daylight Time) Moderated by Max Spevack FESCo Candiate forum Thursday, June 4, 0200 UTC (Wed night, 10pm US Eastern Daylight Time, 7pm US Pacific Daylight Time) Moderated by Chris Tyler Board Candidate forum Thursday, June 4, 1400 UTC (10am US Eastern Daylight Time, 7am US Pacific Daylight Time) Moderated by Paul Frields Board Candidate forum Friday, June 5 0200 UTC (Thurs night, 10pm US Eastern Daylight Time, 7pm US Pacific Daylight Time) Moderated by John Rose (aka inode0) https://fedoraproject.org/wiki/Elections lists these now. I look forward to your participation, and hope these forums will more fully inform our electorate about the candidates. Thanks, Matt -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
Hello, I don't want to start a long thread, but just to ask a couple questions for my own clarification. Does a maintainer's responsibilities end with packaging bugs? IOW, if there is a problem in the package that is _broken code_ do they need to do something about it or is it acceptable for them to close the bug and say talk to upstream? Do we want those bugs open to track when the bug is fixed in the distro? I'll accept whatever the answer is, I'm just curious. Thanks, -Steve This is from the official Bugzappers page https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses#Upstreaming The bug is not a packaging bug, the package maintainer has no plans to work on this in the near future, and there is an upstream bug tracking system other than the Red Hat Bugzilla. Thank you for the bug report. At the moment, the Fedora developers are busy fixing other issues and may not have time to work on this one. The best way to make sure your problem will get looked on is to report it to the authors of the program. Most upstream authors use a bug tracking system like Bugzilla, and more people who know the code will be looking at the bug report there. The upstream bug tracking system to use is: You are requested to add the bugzilla link here for tracking purposes. Please make sure the bug isn't already in the upstream bug tracker before filing it. Maintainers should be free to either fix it locally (time permitting) and upstream the patch or request that the bug be filed at the upstream projects tracker for the upstream developers to resolve it. If it is sent upstream the bug is closed as UPSTREAM and our local report is cross-referenced to the upstream one. That way the maintainer and all interested parties can follow its progress. SMP -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
rpms/perl-JSON-XS/devel .cvsignore, 1.9, 1.10 perl-JSON-XS.spec, 1.15, 1.16 sources, 1.9, 1.10
Author: cweyl
Update of /cvs/extras/rpms/perl-JSON-XS/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv8578
Modified Files:
.cvsignore perl-JSON-XS.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 2.24-1
- auto-update to 2.24 (by cpan-spec-update 0.01)
Index: .cvsignore
===
RCS file: /cvs/extras/rpms/perl-JSON-XS/devel/.cvsignore,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- .cvsignore 23 Feb 2009 06:44:23 - 1.9
+++ .cvsignore 2 Jun 2009 07:02:01 - 1.10
@@ -1 +1 @@
-JSON-XS-2.2311.tar.gz
+JSON-XS-2.24.tar.gz
Index: perl-JSON-XS.spec
===
RCS file: /cvs/extras/rpms/perl-JSON-XS/devel/perl-JSON-XS.spec,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -p -r1.15 -r1.16
--- perl-JSON-XS.spec 27 Mar 2009 05:03:34 - 1.15
+++ perl-JSON-XS.spec 2 Jun 2009 07:02:01 - 1.16
@@ -1,11 +1,12 @@
Name: perl-JSON-XS
-Version:2.2311
-Release:4%{?dist}
+Epoch: 1
+Version:2.24
+Release:1%{?dist}
Summary:JSON serialising/deserialising, done correctly and fast
-License:GPL+ or Artistic
+License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/JSON-XS/
-Source0:
http://www.cpan.org/authors/id/M/ML/MLEHMANN/JSON-XS-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/M/ML/MLEHMANN/JSON-XS-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
@@ -13,12 +14,11 @@ Requires: perl(:MODULE_COMPAT_%(ev
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(Test::More)
-
# don't provide private Perl libs
%global _use_internal_dependency_generator 0
%global __deploop() while read FILE; do /usr/lib/rpm/rpmdeps -%{1} ${FILE};
done | /bin/sort -u
-%global __find_provides /bin/sh -c %{__grep} -v '%{perl_vendorarch}/.*\\.so$'
| %{__deploop P}
-%global __find_requires /bin/sh -c %{__deploop R}
+%global __find_provides /bin/sh -c %{__grep} -v '%_docdir' | %{__grep} -v
'%{perl_vendorarch}/.*\\.so$' | %{__deploop P}
+%global __find_requires /bin/sh -c %{__grep} -v '%_docdir' | %{__deploop R}
%description
This module converts Perl data structures to JSON and vice versa. Its
@@ -63,6 +63,9 @@ rm -rf %{buildroot}
%{_mandir}/man[13]/*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 2.24-1
+- auto-update to 2.24 (by cpan-spec-update 0.01)
+
* Thu Mar 26 2009 Chris Weyl cw...@alumni.drew.edu - 2.2311-4
- Stripping bad provides of private Perl extension libs
Index: sources
===
RCS file: /cvs/extras/rpms/perl-JSON-XS/devel/sources,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- sources 23 Feb 2009 06:44:24 - 1.9
+++ sources 2 Jun 2009 07:02:01 - 1.10
@@ -1 +1 @@
-e9b34ed8f85fdf18e69b4c32f5cd321b JSON-XS-2.2311.tar.gz
+8821744b35260f4712a28ed68afcd2b6 JSON-XS-2.24.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-Catalyst-Runtime/devel .cvsignore, 1.9, 1.10 perl-Catalyst-Runtime.spec, 1.13, 1.14 sources, 1.7, 1.8
Author: cweyl
Update of /cvs/extras/rpms/perl-Catalyst-Runtime/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv8913
Modified Files:
.cvsignore perl-Catalyst-Runtime.spec sources
Log Message:
* Fri May 29 2009 Chris Weyl cw...@alumni.drew.edu 5.80004-1
- drop Catalyst::Manual exclusions (no longer present)
- streamline req/prov filtering
- auto-update to 5.80004 (by cpan-spec-update 0.01)
- added a new br on perl(Scalar::Util) (version 0)
- added a new br on perl(Class::MOP) (version 0.83)
- added a new br on perl(Time::HiRes) (version 0)
- added a new br on perl(MRO::Compat) (version 0)
- added a new br on perl(Sub::Exporter) (version 0)
- added a new br on perl(B::Hooks::EndOfScope) (version 0.08)
- added a new br on perl(namespace::clean) (version 0)
- added a new br on perl(Moose) (version 0.78)
- added a new br on perl(MooseX::MethodAttributes::Inheritable) (version 0.10)
- added a new br on perl(Carp) (version 0)
- added a new br on perl(Text::Balanced) (version 0)
- added a new br on perl(Class::C3::Adopt::NEXT) (version 0.07)
- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
- added a new br on perl(Test::MockObject) (version 1.07)
- altered br on perl(HTTP::Request::AsCGI) (0.5 = 0.8)
- added a new br on perl(MooseX::Emulate::Class::Accessor::Fast) (version
0.00801)
Index: .cvsignore
===
RCS file: /cvs/extras/rpms/perl-Catalyst-Runtime/devel/.cvsignore,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- .cvsignore 12 Apr 2009 02:06:36 - 1.9
+++ .cvsignore 2 Jun 2009 07:04:02 - 1.10
@@ -1,7 +1 @@
-Catalyst-Runtime-5.71001.tar.gz
-Catalyst-Runtime-*
-*.rpm
-*.gz
-noarch
-clog
-.build*
+Catalyst-Runtime-5.80004.tar.gz
Index: perl-Catalyst-Runtime.spec
===
RCS file:
/cvs/extras/rpms/perl-Catalyst-Runtime/devel/perl-Catalyst-Runtime.spec,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -p -r1.13 -r1.14
--- perl-Catalyst-Runtime.spec 12 Apr 2009 02:06:36 - 1.13
+++ perl-Catalyst-Runtime.spec 2 Jun 2009 07:04:02 - 1.14
@@ -1,19 +1,19 @@
Name: perl-Catalyst-Runtime
-Version:5.71001
-Release:2%{?dist}
+Version:5.80004
+Release:1%{?dist}
Summary:Catalyst core modules
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Catalyst-Runtime/
# remember to rebuild perl-Catalyst-Devel on update of this package
-Source0:
http://www.cpan.org/authors/id/M/MR/MRAMBERG/Catalyst-Runtime-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/F/FL/FLORA/Catalyst-Runtime-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# core
BuildRequires: perl = 1:5.8.1
-BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(ExtUtils::MakeMaker) = 6.42
BuildRequires: perl(Test::More)
BuildRequires: perl(Test::Harness)
# cpan
@@ -24,10 +24,10 @@ BuildRequires: perl(Class::Inspector)
BuildRequires: perl(Data::Dump)
BuildRequires: perl(File::Modified)
BuildRequires: perl(HTML::Entities)
-BuildRequires: perl(HTTP::Body)= 1.04
+BuildRequires: perl(HTTP::Body)= 1.04
BuildRequires: perl(HTTP::Headers) = 1.64
BuildRequires: perl(HTTP::Request)
-BuildRequires: perl(HTTP::Request::AsCGI) = 0.5
+BuildRequires: perl(HTTP::Request::AsCGI) = 0.8
BuildRequires: perl(HTTP::Response)
BuildRequires: perl(LWP::UserAgent)
BuildRequires: perl(Module::Pluggable) = 3.01
@@ -44,6 +44,9 @@ BuildRequires: perl(Proc::ProcessTable)
BuildRequires: perl(Test::Pod)
BuildRequires: perl(Test::Pod::Coverage)
BuildRequires: perl(YAML)
+BuildRequires: perl(Test::Exception)
+# optional tests
+BuildRequires: perl(FCGI)
# use base ...
Requires: perl(Class::Accessor::Fast)
@@ -51,6 +54,30 @@ Requires: perl(Class::Data::Inheri
# 'requires'
Requires: perl(HTTP::Request::AsCGI) = 0.5
+# until bundles M::I is updated
+BuildRequires: perl(CPAN)
+
+### auto-added brs!
+BuildRequires: perl(Scalar::Util)
+BuildRequires: perl(Class::MOP) = 0.83
+BuildRequires: perl(Time::HiRes)
+BuildRequires: perl(MRO::Compat)
+BuildRequires: perl(Sub::Exporter)
+BuildRequires: perl(B::Hooks::EndOfScope) = 0.08
+BuildRequires: perl(namespace::clean)
+BuildRequires: perl(Moose) = 0.78
+BuildRequires: perl(MooseX::MethodAttributes::Inheritable) = 0.10
+BuildRequires: perl(Carp)
+BuildRequires: perl(Text::Balanced)
+BuildRequires: perl(Class::C3::Adopt::NEXT) = 0.07
+BuildRequires: perl(Test::MockObject) = 1.07
+BuildRequires: perl(MooseX::Emulate::Class::Accessor::Fast) = 0.00801
+
+# neither provide nor require things we shouldn't
+%global
rpms/perl-JSON-XS/F-11 perl-JSON-XS.spec, 1.15, 1.16 sources, 1.9, 1.10
Author: cweyl
Update of /cvs/extras/rpms/perl-JSON-XS/F-11
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv9404
Modified Files:
perl-JSON-XS.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 2.24-1
- auto-update to 2.24 (by cpan-spec-update 0.01)
Index: perl-JSON-XS.spec
===
RCS file: /cvs/extras/rpms/perl-JSON-XS/F-11/perl-JSON-XS.spec,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -p -r1.15 -r1.16
--- perl-JSON-XS.spec 27 Mar 2009 05:03:34 - 1.15
+++ perl-JSON-XS.spec 2 Jun 2009 07:07:23 - 1.16
@@ -1,11 +1,12 @@
Name: perl-JSON-XS
-Version:2.2311
-Release:4%{?dist}
+Epoch: 1
+Version:2.24
+Release:1%{?dist}
Summary:JSON serialising/deserialising, done correctly and fast
-License:GPL+ or Artistic
+License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/JSON-XS/
-Source0:
http://www.cpan.org/authors/id/M/ML/MLEHMANN/JSON-XS-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/M/ML/MLEHMANN/JSON-XS-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
@@ -13,12 +14,11 @@ Requires: perl(:MODULE_COMPAT_%(ev
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(Test::More)
-
# don't provide private Perl libs
%global _use_internal_dependency_generator 0
%global __deploop() while read FILE; do /usr/lib/rpm/rpmdeps -%{1} ${FILE};
done | /bin/sort -u
-%global __find_provides /bin/sh -c %{__grep} -v '%{perl_vendorarch}/.*\\.so$'
| %{__deploop P}
-%global __find_requires /bin/sh -c %{__deploop R}
+%global __find_provides /bin/sh -c %{__grep} -v '%_docdir' | %{__grep} -v
'%{perl_vendorarch}/.*\\.so$' | %{__deploop P}
+%global __find_requires /bin/sh -c %{__grep} -v '%_docdir' | %{__deploop R}
%description
This module converts Perl data structures to JSON and vice versa. Its
@@ -63,6 +63,9 @@ rm -rf %{buildroot}
%{_mandir}/man[13]/*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 2.24-1
+- auto-update to 2.24 (by cpan-spec-update 0.01)
+
* Thu Mar 26 2009 Chris Weyl cw...@alumni.drew.edu - 2.2311-4
- Stripping bad provides of private Perl extension libs
Index: sources
===
RCS file: /cvs/extras/rpms/perl-JSON-XS/F-11/sources,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- sources 23 Feb 2009 06:44:24 - 1.9
+++ sources 2 Jun 2009 07:07:23 - 1.10
@@ -1 +1 @@
-e9b34ed8f85fdf18e69b4c32f5cd321b JSON-XS-2.2311.tar.gz
+8821744b35260f4712a28ed68afcd2b6 JSON-XS-2.24.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-JSON-XS/F-10 perl-JSON-XS.spec, 1.12, 1.13 sources, 1.9, 1.10
Author: cweyl
Update of /cvs/extras/rpms/perl-JSON-XS/F-10
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv9462
Modified Files:
perl-JSON-XS.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 2.24-1
- auto-update to 2.24 (by cpan-spec-update 0.01)
Index: perl-JSON-XS.spec
===
RCS file: /cvs/extras/rpms/perl-JSON-XS/F-10/perl-JSON-XS.spec,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -p -r1.12 -r1.13
--- perl-JSON-XS.spec 24 Feb 2009 06:20:23 - 1.12
+++ perl-JSON-XS.spec 2 Jun 2009 07:07:40 - 1.13
@@ -1,11 +1,12 @@
Name: perl-JSON-XS
-Version:2.2311
+Epoch: 1
+Version:2.24
Release:1%{?dist}
Summary:JSON serialising/deserialising, done correctly and fast
-License:GPL+ or Artistic
+License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/JSON-XS/
-Source0:
http://www.cpan.org/authors/id/M/ML/MLEHMANN/JSON-XS-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/M/ML/MLEHMANN/JSON-XS-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
@@ -13,6 +14,11 @@ Requires: perl(:MODULE_COMPAT_%(ev
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(Test::More)
+# don't provide private Perl libs
+%global _use_internal_dependency_generator 0
+%global __deploop() while read FILE; do /usr/lib/rpm/rpmdeps -%{1} ${FILE};
done | /bin/sort -u
+%global __find_provides /bin/sh -c %{__grep} -v '%_docdir' | %{__grep} -v
'%{perl_vendorarch}/.*\\.so$' | %{__deploop P}
+%global __find_requires /bin/sh -c %{__grep} -v '%_docdir' | %{__deploop R}
%description
This module converts Perl data structures to JSON and vice versa. Its
@@ -57,6 +63,18 @@ rm -rf %{buildroot}
%{_mandir}/man[13]/*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 2.24-1
+- auto-update to 2.24 (by cpan-spec-update 0.01)
+
+* Thu Mar 26 2009 Chris Weyl cw...@alumni.drew.edu - 2.2311-4
+- Stripping bad provides of private Perl extension libs
+
+* Thu Feb 26 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 2.2311-3
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild
+
+* Thu Feb 26 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 2.2311-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild
+
* Sun Feb 22 2009 Chris Weyl cw...@alumni.drew.edu 2.2311-1
- update to 2.2311
Index: sources
===
RCS file: /cvs/extras/rpms/perl-JSON-XS/F-10/sources,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- sources 24 Feb 2009 06:20:23 - 1.9
+++ sources 2 Jun 2009 07:07:40 - 1.10
@@ -1 +1 @@
-e9b34ed8f85fdf18e69b4c32f5cd321b JSON-XS-2.2311.tar.gz
+8821744b35260f4712a28ed68afcd2b6 JSON-XS-2.24.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-MooseX-Types/devel perl-MooseX-Types.spec,1.9,1.10
Author: cweyl
Update of /cvs/extras/rpms/perl-MooseX-Types/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv10358
Modified Files:
perl-MooseX-Types.spec
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.11-2
- add br on CPAN for bundled version of M::I
Index: perl-MooseX-Types.spec
===
RCS file: /cvs/extras/rpms/perl-MooseX-Types/devel/perl-MooseX-Types.spec,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- perl-MooseX-Types.spec 25 May 2009 07:17:54 - 1.9
+++ perl-MooseX-Types.spec 2 Jun 2009 07:12:21 - 1.10
@@ -1,6 +1,6 @@
Name: perl-MooseX-Types
Version:0.11
-Release:1%{?dist}
+Release:2%{?dist}
# see Makefile.PL, lib/MooseX/Types.pm
License:GPL+ or Artistic
Group: Development/Libraries
@@ -22,6 +22,8 @@ BuildRequires: perl(Sub::Install) = 0.9
BuildRequires: perl(Test::More) = 0.80
BuildRequires: perl(Test::Exception)
BuildRequires: perl(Sub::Exporter)
+# for M::I
+BuildRequires: perl(CPAN)
### auto-added brs!
BuildRequires: perl(Scalar::Util) = 1.19
@@ -86,6 +88,9 @@ rm -rf %{buildroot}
%{_mandir}/man3/*.3*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.11-2
+- add br on CPAN for bundled version of M::I
+
* Mon May 25 2009 Chris Weyl cw...@alumni.drew.edu 0.11-1
- auto-update to 0.11 (by cpan-spec-update 0.01)
- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-Mouse/devel .cvsignore, 1.8, 1.9 perl-Mouse.spec, 1.9, 1.10 sources, 1.8, 1.9
Author: cweyl
Update of /cvs/extras/rpms/perl-Mouse/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv11087
Modified Files:
.cvsignore perl-Mouse.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.23-1
- auto-update to 0.23 (by cpan-spec-update 0.01)
- altered br on perl(Test::Exception) (0 = 0.21)
- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
- altered br on perl(Test::More) (0 = 0.8)
Index: .cvsignore
===
RCS file: /cvs/extras/rpms/perl-Mouse/devel/.cvsignore,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -p -r1.8 -r1.9
--- .cvsignore 3 May 2009 18:59:05 - 1.8
+++ .cvsignore 2 Jun 2009 07:16:59 - 1.9
@@ -1 +1 @@
-Mouse-0.22.tar.gz
+Mouse-0.23.tar.gz
Index: perl-Mouse.spec
===
RCS file: /cvs/extras/rpms/perl-Mouse/devel/perl-Mouse.spec,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- perl-Mouse.spec 3 May 2009 18:59:05 - 1.9
+++ perl-Mouse.spec 2 Jun 2009 07:16:59 - 1.10
@@ -1,24 +1,23 @@
-
-Name: perl-Mouse
-Version:0.22
-Release:1%{?dist}
-License:GPL+ or Artistic
+Name: perl-Mouse
+Version:0.23
+Release:1%{?dist}
+License:GPL+ or Artistic
Group: Development/Libraries
-Summary:Moose minus the antlers
-Source:
http://search.cpan.org/CPAN/authors/id/S/SA/SARTAK/Mouse-%{version}.tar.gz
+Summary:Moose minus the antlers
+Source:
http://search.cpan.org/CPAN/authors/id/S/SA/SARTAK/Mouse-%{version}.tar.gz
Url:http://search.cpan.org/dist/Mouse
-BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
BuildArch: noarch
BuildRequires: perl(Class::Method::Modifiers) = 1.01
-BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(ExtUtils::MakeMaker) = 6.42
BuildRequires: perl(MRO::Compat)
BuildRequires: perl(Scalar::Util) = 1.14
# tests
BuildRequires: perl(Moose)
-BuildRequires: perl(Test::Exception)
-BuildRequires: perl(Test::More)
+BuildRequires: perl(Test::Exception) = 0.21
+BuildRequires: perl(Test::More) = 0.8
# Strictly speaking, since 0.09 these are soft dependencies, that is, Mouse
# will take advantage of them (and run faster) if they're there; but can cope
@@ -31,14 +30,14 @@ Requires: perl(MRO::Compat)
%description
-Moose, a powerful metaobject-fuelled extension of the Perl 5 object system,
+Moose, a powerful metaobject-fuelled extension of the Perl 5 object system,
is wonderful. (For more information on Moose, please see 'perldoc Moose'
after installing the perl-Moose package.)
Unfortunately, it's a little slow. Though significant progress has been
made over the years, the compile time penalty is a non-starter for some
applications. Mouse aims to alleviate this by providing a subset of Moose's
-functionality, faster.
+functionality, faster.
%prep
%setup -q -n Mouse-%{version}
@@ -73,15 +72,21 @@ find %{buildroot} -depth -type d -exec r
make test
%clean
-rm -rf %{buildroot}
+rm -rf %{buildroot}
%files
%defattr(-,root,root,-)
-%doc Changes t/
+%doc Changes t/
%{perl_vendorlib}/*
%{_mandir}/man3/*.3*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.23-1
+- auto-update to 0.23 (by cpan-spec-update 0.01)
+- altered br on perl(Test::Exception) (0 = 0.21)
+- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
+- altered br on perl(Test::More) (0 = 0.8)
+
* Sun May 03 2009 Chris Weyl cw...@alumni.drew.edu 0.22-1
- update to 0.22
Index: sources
===
RCS file: /cvs/extras/rpms/perl-Mouse/devel/sources,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -p -r1.8 -r1.9
--- sources 3 May 2009 18:59:05 - 1.8
+++ sources 2 Jun 2009 07:16:59 - 1.9
@@ -1 +1 @@
-780ace6a75fd1837be6c5c4010e05cfd Mouse-0.22.tar.gz
+ee51652607053ee0be56aff304a5bc07 Mouse-0.23.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-MRO-Compat/devel .cvsignore, 1.5, 1.6 perl-MRO-Compat.spec, 1.7, 1.8 sources, 1.5, 1.6
Author: cweyl
Update of /cvs/extras/rpms/perl-MRO-Compat/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv11459
Modified Files:
.cvsignore perl-MRO-Compat.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.11-1
- auto-update to 0.11 (by cpan-spec-update 0.01)
- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
- altered br on perl(Class::C3) (0.19 = 0.20)
Index: .cvsignore
===
RCS file: /cvs/extras/rpms/perl-MRO-Compat/devel/.cvsignore,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- .cvsignore 2 Apr 2009 07:41:05 - 1.5
+++ .cvsignore 2 Jun 2009 07:18:24 - 1.6
@@ -1 +1 @@
-MRO-Compat-0.10.tar.gz
+MRO-Compat-0.11.tar.gz
Index: perl-MRO-Compat.spec
===
RCS file: /cvs/extras/rpms/perl-MRO-Compat/devel/perl-MRO-Compat.spec,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -p -r1.7 -r1.8
--- perl-MRO-Compat.spec2 Apr 2009 07:41:05 - 1.7
+++ perl-MRO-Compat.spec2 Jun 2009 07:18:24 - 1.8
@@ -1,20 +1,20 @@
Name: perl-MRO-Compat
-Version:0.10
+Version:0.11
Release:1%{?dist}
Summary:Mro::* interface compatibility for Perls 5.9.5
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/MRO-Compat/
-Source0:
http://www.cpan.org/authors/id/F/FL/FLORA/MRO-Compat-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/F/FL/FLORA/MRO-Compat-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# core
-BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(ExtUtils::MakeMaker) = 6.42
BuildRequires: perl(Test::More) = 0.47
# cpan
-BuildRequires: perl(Class::C3) = 0.19
+BuildRequires: perl(Class::C3) = 0.20
BuildRequires: perl(Class::C3::XS) = 0.08
# test
BuildRequires: perl(Test::Pod)
@@ -26,7 +26,7 @@ Requires: perl(Class::C3) = 0.19
%description
The mro namespace provides several utilities for dealing with method
resolution order and method caching in general in Perl 5.9.5 and higher.
-This module provides those interfaces for earlier versions of Perl (back
+This module provides those interfaces for earlier versions of Perl (back
to 5.6.0 anyways).
It is a harmless no-op to use this module on 5.9.5+. That is to say,
@@ -69,6 +69,11 @@ rm -rf %{buildroot}
%{_mandir}/man3/*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.11-1
+- auto-update to 0.11 (by cpan-spec-update 0.01)
+- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
+- altered br on perl(Class::C3) (0.19 = 0.20)
+
* Thu Apr 02 2009 Chris Weyl cw...@alumni.drew.edu 0.10-1
- update to 0.10
Index: sources
===
RCS file: /cvs/extras/rpms/perl-MRO-Compat/devel/sources,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- sources 2 Apr 2009 07:41:05 - 1.5
+++ sources 2 Jun 2009 07:18:24 - 1.6
@@ -1 +1 @@
-0187128ab46570c8955251bc78674cbc MRO-Compat-0.10.tar.gz
+462b68631d5bef8c807190f1c5c17306 MRO-Compat-0.11.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-POE/devel .cvsignore, 1.10, 1.11 perl-POE.spec, 1.15, 1.16 sources, 1.10, 1.11
Author: cweyl
Update of /cvs/extras/rpms/perl-POE/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv12376
Modified Files:
.cvsignore perl-POE.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 1.006-1
- auto-update to 1.006 (by cpan-spec-update 0.01)
Index: .cvsignore
===
RCS file: /cvs/extras/rpms/perl-POE/devel/.cvsignore,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -p -r1.10 -r1.11
--- .cvsignore 19 May 2009 06:08:54 - 1.10
+++ .cvsignore 2 Jun 2009 07:22:52 - 1.11
@@ -1 +1 @@
-POE-1.005.tar.gz
+POE-1.006.tar.gz
Index: perl-POE.spec
===
RCS file: /cvs/extras/rpms/perl-POE/devel/perl-POE.spec,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -p -r1.15 -r1.16
--- perl-POE.spec 19 May 2009 06:08:54 - 1.15
+++ perl-POE.spec 2 Jun 2009 07:22:53 - 1.16
@@ -1,5 +1,5 @@
Name: perl-POE
-Version: 1.005
+Version: 1.006
Release: 1%{?dist}
Summary: POE - portable multitasking and networking framework for Perl
@@ -142,6 +142,9 @@ rm -rf %{buildroot}
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 1.006-1
+- auto-update to 1.006 (by cpan-spec-update 0.01)
+
* Sun May 17 2009 Chris Weyl cw...@alumni.drew.edu 1.005-1
- auto-update to 1.005 (by cpan-spec-update 0.01)
- added a new br on perl(Storable) (version 2.16)
Index: sources
===
RCS file: /cvs/extras/rpms/perl-POE/devel/sources,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -p -r1.10 -r1.11
--- sources 19 May 2009 06:08:54 - 1.10
+++ sources 2 Jun 2009 07:22:53 - 1.11
@@ -1 +1 @@
-f1bfba242aad1ae0d7a124f289d13a9a POE-1.005.tar.gz
+13c4ee6ab28b5ca1d031e654a50a3859 POE-1.006.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-POE-Component-Server-SimpleHTTP/devel .cvsignore, 1.5, 1.6 perl-POE-Component-Server-SimpleHTTP.spec, 1.9, 1.10 sources, 1.5, 1.6
Author: cweyl
Update of /cvs/extras/rpms/perl-POE-Component-Server-SimpleHTTP/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv13175
Modified Files:
.cvsignore perl-POE-Component-Server-SimpleHTTP.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 1.58-1
- auto-update to 1.58 (by cpan-spec-update 0.01)
- added a new br on perl(Storable) (version 0)
- added a new br on perl(Sys::Hostname) (version 0)
- added a new br on perl(POE::Filter::HTTP::Parser) (version 0.02)
- added a new br on perl(Socket) (version 0)
- added a new br on perl(Test::POE::Client::TCP) (version 0.1)
- altered br on perl(POE) (0 = 1.)
- altered br on perl(Test::More) (0 = 0.47)
- added a new br on perl(Carp) (version 0)
Index: .cvsignore
===
RCS file:
/cvs/extras/rpms/perl-POE-Component-Server-SimpleHTTP/devel/.cvsignore,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- .cvsignore 26 Oct 2008 22:00:12 - 1.5
+++ .cvsignore 2 Jun 2009 07:25:42 - 1.6
@@ -1 +1 @@
-POE-Component-Server-SimpleHTTP-1.48.tar.gz
+POE-Component-Server-SimpleHTTP-1.58.tar.gz
Index: perl-POE-Component-Server-SimpleHTTP.spec
===
RCS file:
/cvs/extras/rpms/perl-POE-Component-Server-SimpleHTTP/devel/perl-POE-Component-Server-SimpleHTTP.spec,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- perl-POE-Component-Server-SimpleHTTP.spec 27 Feb 2009 00:01:54 -
1.9
+++ perl-POE-Component-Server-SimpleHTTP.spec 2 Jun 2009 07:25:42 -
1.10
@@ -1,12 +1,12 @@
Name: perl-POE-Component-Server-SimpleHTTP
-Version:1.48
-Release:2%{?dist}
+Version:1.58
+Release:1%{?dist}
Summary:Serve HTTP requests in POE
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/POE-Component-Server-SimpleHTTP/
#Source0:
http://www.cpan.org/authors/id/B/BI/BINGOS/POE-Component-Server-SimpleHTTP-1.23.tar.gz
-Source0:
http://www.cpan.org/modules/by-module/POE/POE-Component-Server-SimpleHTTP-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/B/BI/BINGOS/POE-Component-Server-SimpleHTTP-%{version}.tar.gz
BuildArch: noarch
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
@@ -17,7 +17,7 @@ BuildRequires: perl(HTTP::Date)
BuildRequires: perl(HTTP::Request)
BuildRequires: perl(HTTP::Response)
BuildRequires: perl(IPC::Shareable)
-BuildRequires: perl(POE)
+BuildRequires: perl(POE) = 1.
BuildRequires: perl(POE::Component::SSLify) = 0.04
BuildRequires: perl(POE::Driver::SysRW)
BuildRequires: perl(POE::Filter::HTTPD)
@@ -25,7 +25,7 @@ BuildRequires: perl(POE::Wheel::ReadWri
BuildRequires: perl(POE::Wheel::SocketFactory)
# tests
-BuildRequires: perl(Test::More)
+BuildRequires: perl(Test::More) = 0.47
BuildRequires: perl(POE::Component::Client::HTTP)
# optional tests
@@ -37,6 +37,14 @@ BuildRequires: perl(Test::Pod)
Requires: perl(HTTP::Response)
+### auto-added brs!
+BuildRequires: perl(Storable)
+BuildRequires: perl(Sys::Hostname)
+BuildRequires: perl(POE::Filter::HTTP::Parser) = 0.02
+BuildRequires: perl(Socket)
+BuildRequires: perl(Test::POE::Client::TCP) = 0.1
+BuildRequires: perl(Carp)
+
%description
This module makes serving up HTTP requests a breeze in POE.
@@ -76,6 +84,17 @@ rm -rf %{buildroot}
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 1.58-1
+- auto-update to 1.58 (by cpan-spec-update 0.01)
+- added a new br on perl(Storable) (version 0)
+- added a new br on perl(Sys::Hostname) (version 0)
+- added a new br on perl(POE::Filter::HTTP::Parser) (version 0.02)
+- added a new br on perl(Socket) (version 0)
+- added a new br on perl(Test::POE::Client::TCP) (version 0.1)
+- altered br on perl(POE) (0 = 1.)
+- altered br on perl(Test::More) (0 = 0.47)
+- added a new br on perl(Carp) (version 0)
+
* Thu Feb 26 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.48-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild
Index: sources
===
RCS file: /cvs/extras/rpms/perl-POE-Component-Server-SimpleHTTP/devel/sources,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- sources 26 Oct 2008 22:00:12 - 1.5
+++ sources 2 Jun 2009 07:25:43 - 1.6
@@ -1 +1 @@
-13bac016a801a9bdd34c6c074123d78f POE-Component-Server-SimpleHTTP-1.48.tar.gz
+9c252b837cf11fb1ae23bcc052deba9e POE-Component-Server-SimpleHTTP-1.58.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-MRO-Compat/F-11 perl-MRO-Compat.spec, 1.7, 1.8 sources, 1.5, 1.6
Author: cweyl
Update of /cvs/extras/rpms/perl-MRO-Compat/F-11
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv14046
Modified Files:
perl-MRO-Compat.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.11-1
- auto-update to 0.11 (by cpan-spec-update 0.01)
- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
- altered br on perl(Class::C3) (0.19 = 0.20)
Index: perl-MRO-Compat.spec
===
RCS file: /cvs/extras/rpms/perl-MRO-Compat/F-11/perl-MRO-Compat.spec,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -p -r1.7 -r1.8
--- perl-MRO-Compat.spec2 Apr 2009 07:41:05 - 1.7
+++ perl-MRO-Compat.spec2 Jun 2009 07:27:01 - 1.8
@@ -1,20 +1,20 @@
Name: perl-MRO-Compat
-Version:0.10
+Version:0.11
Release:1%{?dist}
Summary:Mro::* interface compatibility for Perls 5.9.5
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/MRO-Compat/
-Source0:
http://www.cpan.org/authors/id/F/FL/FLORA/MRO-Compat-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/F/FL/FLORA/MRO-Compat-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# core
-BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(ExtUtils::MakeMaker) = 6.42
BuildRequires: perl(Test::More) = 0.47
# cpan
-BuildRequires: perl(Class::C3) = 0.19
+BuildRequires: perl(Class::C3) = 0.20
BuildRequires: perl(Class::C3::XS) = 0.08
# test
BuildRequires: perl(Test::Pod)
@@ -26,7 +26,7 @@ Requires: perl(Class::C3) = 0.19
%description
The mro namespace provides several utilities for dealing with method
resolution order and method caching in general in Perl 5.9.5 and higher.
-This module provides those interfaces for earlier versions of Perl (back
+This module provides those interfaces for earlier versions of Perl (back
to 5.6.0 anyways).
It is a harmless no-op to use this module on 5.9.5+. That is to say,
@@ -69,6 +69,11 @@ rm -rf %{buildroot}
%{_mandir}/man3/*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.11-1
+- auto-update to 0.11 (by cpan-spec-update 0.01)
+- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
+- altered br on perl(Class::C3) (0.19 = 0.20)
+
* Thu Apr 02 2009 Chris Weyl cw...@alumni.drew.edu 0.10-1
- update to 0.10
Index: sources
===
RCS file: /cvs/extras/rpms/perl-MRO-Compat/F-11/sources,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- sources 2 Apr 2009 07:41:05 - 1.5
+++ sources 2 Jun 2009 07:27:01 - 1.6
@@ -1 +1 @@
-0187128ab46570c8955251bc78674cbc MRO-Compat-0.10.tar.gz
+462b68631d5bef8c807190f1c5c17306 MRO-Compat-0.11.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-MRO-Compat/F-10 perl-MRO-Compat.spec, 1.6, 1.7 sources, 1.5, 1.6
Author: cweyl
Update of /cvs/extras/rpms/perl-MRO-Compat/F-10
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv14073
Modified Files:
perl-MRO-Compat.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.11-1
- auto-update to 0.11 (by cpan-spec-update 0.01)
- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
- altered br on perl(Class::C3) (0.19 = 0.20)
Index: perl-MRO-Compat.spec
===
RCS file: /cvs/extras/rpms/perl-MRO-Compat/F-10/perl-MRO-Compat.spec,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -p -r1.6 -r1.7
--- perl-MRO-Compat.spec2 Apr 2009 07:47:38 - 1.6
+++ perl-MRO-Compat.spec2 Jun 2009 07:27:05 - 1.7
@@ -1,20 +1,20 @@
Name: perl-MRO-Compat
-Version:0.10
+Version:0.11
Release:1%{?dist}
Summary:Mro::* interface compatibility for Perls 5.9.5
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/MRO-Compat/
-Source0:
http://www.cpan.org/authors/id/F/FL/FLORA/MRO-Compat-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/F/FL/FLORA/MRO-Compat-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# core
-BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(ExtUtils::MakeMaker) = 6.42
BuildRequires: perl(Test::More) = 0.47
# cpan
-BuildRequires: perl(Class::C3) = 0.19
+BuildRequires: perl(Class::C3) = 0.20
BuildRequires: perl(Class::C3::XS) = 0.08
# test
BuildRequires: perl(Test::Pod)
@@ -26,7 +26,7 @@ Requires: perl(Class::C3) = 0.19
%description
The mro namespace provides several utilities for dealing with method
resolution order and method caching in general in Perl 5.9.5 and higher.
-This module provides those interfaces for earlier versions of Perl (back
+This module provides those interfaces for earlier versions of Perl (back
to 5.6.0 anyways).
It is a harmless no-op to use this module on 5.9.5+. That is to say,
@@ -69,6 +69,11 @@ rm -rf %{buildroot}
%{_mandir}/man3/*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.11-1
+- auto-update to 0.11 (by cpan-spec-update 0.01)
+- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
+- altered br on perl(Class::C3) (0.19 = 0.20)
+
* Thu Apr 02 2009 Chris Weyl cw...@alumni.drew.edu 0.10-1
- update to 0.10
Index: sources
===
RCS file: /cvs/extras/rpms/perl-MRO-Compat/F-10/sources,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- sources 2 Apr 2009 07:47:38 - 1.5
+++ sources 2 Jun 2009 07:27:05 - 1.6
@@ -1 +1 @@
-0187128ab46570c8955251bc78674cbc MRO-Compat-0.10.tar.gz
+462b68631d5bef8c807190f1c5c17306 MRO-Compat-0.11.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-Mouse/F-11 perl-Mouse.spec,1.9,1.10 sources,1.8,1.9
Author: cweyl
Update of /cvs/extras/rpms/perl-Mouse/F-11
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv14365
Modified Files:
perl-Mouse.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.23-1
- auto-update to 0.23 (by cpan-spec-update 0.01)
- altered br on perl(Test::Exception) (0 = 0.21)
- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
- altered br on perl(Test::More) (0 = 0.8)
Index: perl-Mouse.spec
===
RCS file: /cvs/extras/rpms/perl-Mouse/F-11/perl-Mouse.spec,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- perl-Mouse.spec 3 May 2009 19:00:44 - 1.9
+++ perl-Mouse.spec 2 Jun 2009 07:27:56 - 1.10
@@ -1,24 +1,23 @@
-
-Name: perl-Mouse
-Version:0.22
-Release:1%{?dist}
-License:GPL+ or Artistic
+Name: perl-Mouse
+Version:0.23
+Release:1%{?dist}
+License:GPL+ or Artistic
Group: Development/Libraries
-Summary:Moose minus the antlers
-Source:
http://search.cpan.org/CPAN/authors/id/S/SA/SARTAK/Mouse-%{version}.tar.gz
+Summary:Moose minus the antlers
+Source:
http://search.cpan.org/CPAN/authors/id/S/SA/SARTAK/Mouse-%{version}.tar.gz
Url:http://search.cpan.org/dist/Mouse
-BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
BuildArch: noarch
BuildRequires: perl(Class::Method::Modifiers) = 1.01
-BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(ExtUtils::MakeMaker) = 6.42
BuildRequires: perl(MRO::Compat)
BuildRequires: perl(Scalar::Util) = 1.14
# tests
BuildRequires: perl(Moose)
-BuildRequires: perl(Test::Exception)
-BuildRequires: perl(Test::More)
+BuildRequires: perl(Test::Exception) = 0.21
+BuildRequires: perl(Test::More) = 0.8
# Strictly speaking, since 0.09 these are soft dependencies, that is, Mouse
# will take advantage of them (and run faster) if they're there; but can cope
@@ -31,14 +30,14 @@ Requires: perl(MRO::Compat)
%description
-Moose, a powerful metaobject-fuelled extension of the Perl 5 object system,
+Moose, a powerful metaobject-fuelled extension of the Perl 5 object system,
is wonderful. (For more information on Moose, please see 'perldoc Moose'
after installing the perl-Moose package.)
Unfortunately, it's a little slow. Though significant progress has been
made over the years, the compile time penalty is a non-starter for some
applications. Mouse aims to alleviate this by providing a subset of Moose's
-functionality, faster.
+functionality, faster.
%prep
%setup -q -n Mouse-%{version}
@@ -73,15 +72,21 @@ find %{buildroot} -depth -type d -exec r
make test
%clean
-rm -rf %{buildroot}
+rm -rf %{buildroot}
%files
%defattr(-,root,root,-)
-%doc Changes t/
+%doc Changes t/
%{perl_vendorlib}/*
%{_mandir}/man3/*.3*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.23-1
+- auto-update to 0.23 (by cpan-spec-update 0.01)
+- altered br on perl(Test::Exception) (0 = 0.21)
+- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
+- altered br on perl(Test::More) (0 = 0.8)
+
* Sun May 03 2009 Chris Weyl cw...@alumni.drew.edu 0.22-1
- update to 0.22
Index: sources
===
RCS file: /cvs/extras/rpms/perl-Mouse/F-11/sources,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -p -r1.8 -r1.9
--- sources 3 May 2009 19:00:44 - 1.8
+++ sources 2 Jun 2009 07:27:56 - 1.9
@@ -1 +1 @@
-780ace6a75fd1837be6c5c4010e05cfd Mouse-0.22.tar.gz
+ee51652607053ee0be56aff304a5bc07 Mouse-0.23.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-Mouse/F-10 perl-Mouse.spec,1.8,1.9 sources,1.8,1.9
Author: cweyl
Update of /cvs/extras/rpms/perl-Mouse/F-10
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv14421
Modified Files:
perl-Mouse.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.23-1
- auto-update to 0.23 (by cpan-spec-update 0.01)
- altered br on perl(Test::Exception) (0 = 0.21)
- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
- altered br on perl(Test::More) (0 = 0.8)
Index: perl-Mouse.spec
===
RCS file: /cvs/extras/rpms/perl-Mouse/F-10/perl-Mouse.spec,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -p -r1.8 -r1.9
--- perl-Mouse.spec 3 May 2009 19:00:56 - 1.8
+++ perl-Mouse.spec 2 Jun 2009 07:28:01 - 1.9
@@ -1,24 +1,23 @@
-
-Name: perl-Mouse
-Version:0.22
-Release:1%{?dist}
-License:GPL+ or Artistic
+Name: perl-Mouse
+Version:0.23
+Release:1%{?dist}
+License:GPL+ or Artistic
Group: Development/Libraries
-Summary:Moose minus the antlers
-Source:
http://search.cpan.org/CPAN/authors/id/S/SA/SARTAK/Mouse-%{version}.tar.gz
+Summary:Moose minus the antlers
+Source:
http://search.cpan.org/CPAN/authors/id/S/SA/SARTAK/Mouse-%{version}.tar.gz
Url:http://search.cpan.org/dist/Mouse
-BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
BuildArch: noarch
BuildRequires: perl(Class::Method::Modifiers) = 1.01
-BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(ExtUtils::MakeMaker) = 6.42
BuildRequires: perl(MRO::Compat)
BuildRequires: perl(Scalar::Util) = 1.14
# tests
BuildRequires: perl(Moose)
-BuildRequires: perl(Test::Exception)
-BuildRequires: perl(Test::More)
+BuildRequires: perl(Test::Exception) = 0.21
+BuildRequires: perl(Test::More) = 0.8
# Strictly speaking, since 0.09 these are soft dependencies, that is, Mouse
# will take advantage of them (and run faster) if they're there; but can cope
@@ -31,14 +30,14 @@ Requires: perl(MRO::Compat)
%description
-Moose, a powerful metaobject-fuelled extension of the Perl 5 object system,
+Moose, a powerful metaobject-fuelled extension of the Perl 5 object system,
is wonderful. (For more information on Moose, please see 'perldoc Moose'
after installing the perl-Moose package.)
Unfortunately, it's a little slow. Though significant progress has been
made over the years, the compile time penalty is a non-starter for some
applications. Mouse aims to alleviate this by providing a subset of Moose's
-functionality, faster.
+functionality, faster.
%prep
%setup -q -n Mouse-%{version}
@@ -73,15 +72,21 @@ find %{buildroot} -depth -type d -exec r
make test
%clean
-rm -rf %{buildroot}
+rm -rf %{buildroot}
%files
%defattr(-,root,root,-)
-%doc Changes t/
+%doc Changes t/
%{perl_vendorlib}/*
%{_mandir}/man3/*.3*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.23-1
+- auto-update to 0.23 (by cpan-spec-update 0.01)
+- altered br on perl(Test::Exception) (0 = 0.21)
+- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
+- altered br on perl(Test::More) (0 = 0.8)
+
* Sun May 03 2009 Chris Weyl cw...@alumni.drew.edu 0.22-1
- update to 0.22
Index: sources
===
RCS file: /cvs/extras/rpms/perl-Mouse/F-10/sources,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -p -r1.8 -r1.9
--- sources 3 May 2009 19:00:57 - 1.8
+++ sources 2 Jun 2009 07:28:02 - 1.9
@@ -1 +1 @@
-780ace6a75fd1837be6c5c4010e05cfd Mouse-0.22.tar.gz
+ee51652607053ee0be56aff304a5bc07 Mouse-0.23.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 503763] perl-Text-Glob is not available in EPEL4
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=503763 Xavier Bachelot xav...@bachelot.org changed: What|Removed |Added Blocks||503765 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 503764] New: perl-Number-Compare is not available in EPEL4
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-Number-Compare is not available in EPEL4 https://bugzilla.redhat.com/show_bug.cgi?id=503764 Summary: perl-Number-Compare is not available in EPEL4 Product: Fedora EPEL Version: el4 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-Number-Compare AssignedTo: rob.my...@gtri.gatech.edu ReportedBy: xav...@bachelot.org QAContact: extras...@fedoraproject.org CC: rob.my...@gtri.gatech.edu, fedora-perl-devel-list@redhat.com, lxt...@gmail.com Classification: Fedora perl-Number-Compare is branched but not available in EPEL4. The version from EPEL5 rebuilds fine on EL4. Could you please built it ? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 503765] New: perl-File-Find-Rule is not available in EPEL4
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-File-Find-Rule is not available in EPEL4 https://bugzilla.redhat.com/show_bug.cgi?id=503765 Summary: perl-File-Find-Rule is not available in EPEL4 Product: Fedora EPEL Version: el4 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-File-Find-Rule AssignedTo: rob.my...@gtri.gatech.edu ReportedBy: xav...@bachelot.org QAContact: extras...@fedoraproject.org CC: rob.my...@gtri.gatech.edu, fedora-perl-devel-list@redhat.com, lxt...@gmail.com Depends on: 503763,503764 Classification: Fedora perl-File-Find-Rule is branched but not available in EPEL4. The version from EPEL5 rebuilds fine on EL4. Could you please built it ? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 503763] New: perl-Text-Glob is not available in EPEL4
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-Text-Glob is not available in EPEL4 https://bugzilla.redhat.com/show_bug.cgi?id=503763 Summary: perl-Text-Glob is not available in EPEL4 Product: Fedora EPEL Version: el4 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-Text-Glob AssignedTo: rob.my...@gtri.gatech.edu ReportedBy: xav...@bachelot.org QAContact: extras...@fedoraproject.org CC: rob.my...@gtri.gatech.edu, fedora-perl-devel-list@redhat.com, lxt...@gmail.com Classification: Fedora perl-Text-Glob is branched but not available in EPEL4. The version from EPEL5 rebuilds fine on EL4. Could you please built it ? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-MooseX-Singleton/devel .cvsignore, 1.2, 1.3 perl-MooseX-Singleton.spec, 1.1, 1.2 sources, 1.2, 1.3
Author: cweyl
Update of /cvs/extras/rpms/perl-MooseX-Singleton/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv2976
Modified Files:
.cvsignore perl-MooseX-Singleton.spec sources
Log Message:
* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.17-1
- auto-update to 0.17 (by cpan-spec-update 0.01)
- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
- altered br on perl(Moose) (0.65 = 0.74)
Index: .cvsignore
===
RCS file: /cvs/extras/rpms/perl-MooseX-Singleton/devel/.cvsignore,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- .cvsignore 5 Mar 2009 21:20:55 - 1.2
+++ .cvsignore 2 Jun 2009 15:45:32 - 1.3
@@ -1 +1 @@
-MooseX-Singleton-0.14.tar.gz
+MooseX-Singleton-0.17.tar.gz
Index: perl-MooseX-Singleton.spec
===
RCS file:
/cvs/extras/rpms/perl-MooseX-Singleton/devel/perl-MooseX-Singleton.spec,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- perl-MooseX-Singleton.spec 5 Mar 2009 21:20:55 - 1.1
+++ perl-MooseX-Singleton.spec 2 Jun 2009 15:45:32 - 1.2
@@ -1,15 +1,15 @@
Name: perl-MooseX-Singleton
-Version:0.14
+Version:0.17
Release:1%{?dist}
Summary:Turn your Moose class into a singleton
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/MooseX-Singleton/
-Source0:
http://www.cpan.org/authors/id/D/DR/DROLSKY/MooseX-Singleton-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/S/SA/SARTAK/MooseX-Singleton-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
-BuildRequires: perl(ExtUtils::MakeMaker)
-BuildRequires: perl(Moose) = 0.65
+BuildRequires: perl(ExtUtils::MakeMaker) = 6.42
+BuildRequires: perl(Moose) = 0.74
BuildRequires: perl(Test::Exception)
BuildRequires: perl(Test::More)
BuildRequires: perl(Test::Warn)
@@ -64,5 +64,10 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man3/*
%changelog
+* Tue Jun 02 2009 Chris Weyl cw...@alumni.drew.edu 0.17-1
+- auto-update to 0.17 (by cpan-spec-update 0.01)
+- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
+- altered br on perl(Moose) (0.65 = 0.74)
+
* Wed Mar 04 2009 Allisson Azevedo allis...@gmail.com 0.14-1
- Initial rpm release.
Index: sources
===
RCS file: /cvs/extras/rpms/perl-MooseX-Singleton/devel/sources,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- sources 5 Mar 2009 21:20:55 - 1.2
+++ sources 2 Jun 2009 15:45:32 - 1.3
@@ -1 +1 @@
-2e1aefa342d4d73bd8ff6fe2ab0ab34e MooseX-Singleton-0.14.tar.gz
+d4fa63586132b12a5fcfe06981926507 MooseX-Singleton-0.17.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
[Bug 503767] New: perl-Params-Validate is not available in EPEL4
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: perl-Params-Validate is not available in EPEL4 https://bugzilla.redhat.com/show_bug.cgi?id=503767 Summary: perl-Params-Validate is not available in EPEL4 Product: Fedora EPEL Version: el4 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: perl-Params-Validate AssignedTo: rob.my...@gtri.gatech.edu ReportedBy: xav...@bachelot.org QAContact: extras...@fedoraproject.org CC: rob.my...@gtri.gatech.edu, fedora-perl-devel-list@redhat.com, lxt...@gmail.com Depends on: 503766 Classification: Fedora perl-Params-Validate is branched but not available in EPEL4. The version from EPEL5 rebuilds fine on EL4. Could you please built it ? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl Fedora-perl-devel-list mailing list Fedora-perl-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
rpms/perl-DBIx-Class-Schema-Loader/devel .cvsignore, 1.2, 1.3 perl-DBIx-Class-Schema-Loader.spec, 1.3, 1.4 sources, 1.2, 1.3
Author: cweyl
Update of /cvs/extras/rpms/perl-DBIx-Class-Schema-Loader/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv17915
Modified Files:
.cvsignore perl-DBIx-Class-Schema-Loader.spec sources
Log Message:
* Wed Jun 03 2009 Chris Weyl cw...@alumni.drew.edu 0.04006-1
- auto-update to 0.04006 (by cpan-spec-update 0.01)
- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
- altered br on perl(Test::More) (0 = 0.47)
Index: .cvsignore
===
RCS file: /cvs/extras/rpms/perl-DBIx-Class-Schema-Loader/devel/.cvsignore,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- .cvsignore 23 Jul 2008 23:54:28 - 1.2
+++ .cvsignore 3 Jun 2009 05:16:41 - 1.3
@@ -1 +1 @@
-DBIx-Class-Schema-Loader-0.04005.tar.gz
+DBIx-Class-Schema-Loader-0.04006.tar.gz
Index: perl-DBIx-Class-Schema-Loader.spec
===
RCS file:
/cvs/extras/rpms/perl-DBIx-Class-Schema-Loader/devel/perl-DBIx-Class-Schema-Loader.spec,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -p -r1.3 -r1.4
--- perl-DBIx-Class-Schema-Loader.spec 26 Feb 2009 14:14:43 - 1.3
+++ perl-DBIx-Class-Schema-Loader.spec 3 Jun 2009 05:16:42 - 1.4
@@ -1,30 +1,30 @@
Name: perl-DBIx-Class-Schema-Loader
-Version:0.04005
-Release:3%{?dist}
+Version:0.04006
+Release:1%{?dist}
Summary:Dynamic definition of a DBIx::Class::Schema
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/DBIx-Class-Schema-Loader/
-Source0:
http://www.cpan.org/modules/by-module/DBIx/DBIx-Class-Schema-Loader-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/I/IL/ILMARI/DBIx-Class-Schema-Loader-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
# core
BuildRequires: perl(Digest::MD5) = 2.36
-BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(ExtUtils::MakeMaker) = 6.42
BuildRequires: perl(File::Path)
BuildRequires: perl(File::Spec)
-BuildRequires: perl(Scalar::Util)
-BuildRequires: perl(Test::More)
-BuildRequires: perl(Text::Balanced)
+BuildRequires: perl(Scalar::Util)
+BuildRequires: perl(Test::More) = 0.47
+BuildRequires: perl(Text::Balanced)
# cpan
-BuildRequires: perl(Carp::Clan)
+BuildRequires: perl(Carp::Clan)
BuildRequires: perl(Class::Accessor::Fast) = 0.30
BuildRequires: perl(Class::C3) = 0.18
BuildRequires: perl(Class::Data::Accessor) = 0.03
-BuildRequires: perl(Class::Inspector)
+BuildRequires: perl(Class::Inspector)
BuildRequires: perl(Data::Dump) = 1.06
BuildRequires: perl(DBD::SQLite) = 1.12
BuildRequires: perl(DBI) = 1.56
@@ -41,7 +41,7 @@ Requires: perl(Class::Data::Access
%description
DBIx::Class::Schema::Loader automates the definition of a
-DBIx::Class::Schema by scanning database table definitions
+DBIx::Class::Schema by scanning database table definitions
and setting up the columns, primary keys, and relationships.
%prep
@@ -66,7 +66,7 @@ EOF
chmod +x %{__perl_requires}
%build
-echo n | %{__perl} Makefile.PL INSTALLDIRS=vendor
+echo n | %{__perl} Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
@@ -74,7 +74,7 @@ rm -rf %{buildroot}
make pure_install PERL_INSTALL_ROOT=%{buildroot}
-find %{buildroot} -type f -name .packlist -exec rm -f {} +
+find %{buildroot} -type f -name .packlist -exec rm -f {} +
find %{buildroot} -depth -type d -exec rmdir {} 2/dev/null \;
%{_fixperms} %{buildroot}/*
@@ -87,11 +87,16 @@ rm -rf %{buildroot}
%files
%defattr(-,root,root,-)
-%doc Changes README t/
+%doc Changes README t/
%{perl_vendorlib}/*
%{_mandir}/man3/*
%changelog
+* Wed Jun 03 2009 Chris Weyl cw...@alumni.drew.edu 0.04006-1
+- auto-update to 0.04006 (by cpan-spec-update 0.01)
+- altered br on perl(ExtUtils::MakeMaker) (0 = 6.42)
+- altered br on perl(Test::More) (0 = 0.47)
+
* Thu Feb 26 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.04005-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild
Index: sources
===
RCS file: /cvs/extras/rpms/perl-DBIx-Class-Schema-Loader/devel/sources,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- sources 23 Jul 2008 23:54:28 - 1.2
+++ sources 3 Jun 2009 05:16:42 - 1.3
@@ -1 +1 @@
-d9e112493df06800862b93bf46760c4f DBIx-Class-Schema-Loader-0.04005.tar.gz
+819e92fd8c7088fdde730d1295556d3c DBIx-Class-Schema-Loader-0.04006.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
