Re: Proposal for revitalizing the sponsorship process for packaging
On Mon, 30 Apr 2012 10:53:45 +0100, NM (Nelson) wrote: Potential sponsors either nominate themselves or get nominated by somebody else: https://fedoraproject.org/wiki/How_to_sponsor_a_new_contributor My apologies for deviating the thread earlier. I would address this issue in a different way: 1) Assigning a sponsor to a new potential contributor takes a lot of time from an active 'sponsor' and there's no ensurance the contributor will go through it and succeed; in case it fails, it's 'wasted' time that could be used into something more productive from the sponsor. 2) Motivational issues: this are important, either from the sponsor and from the potential contributor; While for the potential contributor slow response times can break his motivation, for the 'sponsor' motivation can be affected by non-responsive contributors or people who just 'disappear' A sponsor who has made a bad experience could sound like that. ;) It's not necessarily a wasted effort, because for the reviewer it's useful practice. And often, multiple reviewers visit a review request ticket and read through the comments. Sometimes only as a self-test to find out whether they would notice the same issues with a package. But one can learn from reading [some] reviews. Which is also one reason why newbie packagers and needsponsor-packagers are encouraged to try reviewing somebody else's package. That this could speed on the sponsor-finding process should be enough motivation. I'm more concerned about the apparent increase of package-orphans due to packagers who drop off silently. No statistics known, but it seems to be a steady percentage of the total number of packages. One one side of the package collection there are attempts at adding new packages faster, while on the other side packages must be orphaned because maintainer is AWOL. This are probably the most relevant factors, sponsor's workflow and motivational issues. There's no easy fix for it, so my suggestion would be to face the current issues from a whole different perspective: a) Packages should be owned by a group of people and not necessarily from a single person; face this as the real 'owner' of the package is X, where X stands for the group of all co-maintainers of the package, which can be coordinated by a SIG; But this is possible already since the introduction of pkgdb! Even if the interface lists one of the maintainers as owner (aka the initial assignee in bugzilla), additional maintainers can be added to the four ACLs, getting full access to the package, including even the ability to approve further maintainers within pkgdb. Additionally, the SRCRPMNAME-owner Fedora Project mail alias can be used to reach all maintainer of the package. For some packages, the mail is forwarded to a special mailing-list even. Nothing (except for lack of motivation) really stops an interested volunteer from signing up as the bug triager for a package, for instance. The watchbugzilla ACL in pkgdb makes that easy. The person only needs to be sponsored, which shouldn't be a big hurdle, provided the person does the preparatory work, such as signing the deal with the existing package maintainer(s). Another person could handle releasing the updates in bodhi, and so on. As I mentioned elsewhere in this thread, a problem IMO is that once there is a single package owner already, hardly anybody else wants to take care of this package, too. Unless the owner becomes non-responsive or doesn't update the package frequently enough. Potential orphans have a higher chance of attracting a co-maintainer, which likely becomes the new owner if the previous owner drops off actually. Actual orphans are picked by existing packagers like low-hanging fruit, sometimes apparently without real interest in the packages. b) Introduce a more collaborative way; Imagine I want to get package 'foobar' updated; The step would be to encourage the current person to file a bug report requesting the update and provide already a git pull with the changes; When it comes to review one of the persons which maintains the package can review the git pull request and merge it/rebuild it or request further changes. This is the fase where there's know-how transiction and everyone would be allowed to submit changes to Fedora without being a packager. The review still happens and isn't bound to a single person, but instead to a group of persons, which should reduce the heat. Same as above. Or? Btw, we're facing the problem that update requests in bugzilla (similar to bug reports in bugzilla) are not handled for some packages. Non-responsive maintainers, different/conflicting workflows, too many tickets per component, etc. And still, bugzilla isn't a place where bug reporters would volunteer as co-maintainers. c) Such a method would also mean that packages are harder to get orphaned out, since theres more people looking after them; Well, there are small and larger teams of
Does anyone know what is up with nushio?
Hello, nushio, the rabbitvcs maintainer has not been answering one of his bug reports [1]. I have prepared an updated package that works with the new nautilus, but is still has not been committed. Does anyone know what the deal is? Has nushio left the project and should his packages thus be orphaned? Or is he just busy with real life and then I would kindly ask one of the provenpackagers to commit my changes. Regards, Julian [1] https://bugzilla.redhat.com/show_bug.cgi?id=760682 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F-17 Branched report: 20120501 changes
Compose started at Tue May 1 08:15:05 UTC 2012 Broken deps for x86_64 -- [LuxRender] LuxRender-blender-0.8.0-13.fc17.x86_64 requires blender(ABI) = 0:2.61 [aeolus-conductor] aeolus-conductor-0.4.0-2.fc17.noarch requires ruby(abi) = 0:1.8 [aeolus-configserver] aeolus-configserver-0.4.5-1.fc17.noarch requires ruby-nokogiri [dh-make] dh-make-0.55-4.fc17.noarch requires debhelper [dustmite] dustmite-1-4.20120304gitcde46e0.fc17.x86_64 requires libphobos2-ldc.so()(64bit) [egoboo] egoboo-2.7.5-11.fc17.x86_64 requires libenet-1.2.1.so()(64bit) [gcc-python-plugin] gcc-python2-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python2-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python3-debug-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 gcc-python3-plugin-0.9-1.fc17.x86_64 requires gcc = 0:4.7.0-0.10.fc17 [gorm] gorm-1.2.13-0.2.20110331.fc17.i686 requires libobjc.so.3 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-gui.so.0.20 gorm-1.2.13-0.2.20110331.fc17.i686 requires libgnustep-base.so.1.23 gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libobjc.so.3()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-gui.so.0.20()(64bit) gorm-1.2.13-0.2.20110331.fc17.x86_64 requires libgnustep-base.so.1.23()(64bit) [ibus-panel-extensions] ibus-panel-extensions-1.4.99.20111207-2.fc17.i686 requires libibus-1.0.so.0 ibus-panel-extensions-1.4.99.20111207-2.fc17.x86_64 requires libibus-1.0.so.0()(64bit) [matreshka] matreshka-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-fastcgi-0.1.1-9.fc17.i686 requires libgnarl-4.6.so matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-fastcgi-0.1.1-9.fc17.x86_64 requires libgnarl-4.6.so()(64bit) matreshka-sql-core-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-core-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-postgresql-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-postgresql-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) matreshka-sql-sqlite-0.1.1-9.fc17.i686 requires libgnat-4.6.so matreshka-sql-sqlite-0.1.1-9.fc17.x86_64 requires libgnat-4.6.so()(64bit) [mcollective] mcollective-common-1.3.1-7.fc17.noarch requires ruby(abi) = 0:1.8 [meshlab] meshlab-1.3.1-2.fc17.x86_64 requires libmuparser.so.0()(64bit) [moksha] moksha-0.5.0-5.fc15.noarch requires pyevent [natus] libnatus-V8-0.1.5-2.fc15.x86_64 requires libv8-3.0.0.1.so()(64bit) [ocaml-augeas] ocaml-augeas-0.4-9.fc15.x86_64 requires ocaml(runtime) = 0:3.12.0 [openvrml] libopenvrml-0.18.8-2.fc16.i686 requires libboost_thread-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.i686 requires libboost_system-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.i686 requires libboost_filesystem-mt.so.1.47.0 libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) libopenvrml-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_thread-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_system-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.i686 requires libboost_filesystem-mt.so.1.47.0 libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) libopenvrml-gl-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-java-0.18.8-2.fc16.x86_64 requires java-1.6.0-openjdk(x86-64) openvrml-javascript-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-javascript-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) openvrml-javascript-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-nodes-0.18.8-2.fc16.x86_64 requires libboost_thread-mt.so.1.47.0()(64bit) openvrml-nodes-0.18.8-2.fc16.x86_64 requires libboost_system-mt.so.1.47.0()(64bit) openvrml-nodes-0.18.8-2.fc16.x86_64 requires libboost_filesystem-mt.so.1.47.0()(64bit) openvrml-xembed-0.18.8-2.fc16.x86_64
Re: Does anyone know what is up with nushio?
On Tue, May 1, 2012 at 6:21 AM, Julian Sikorski beleg...@gmail.com wrote: Hello, nushio, the rabbitvcs maintainer has not been answering one of his bug reports [1]. I have prepared an updated package that works with the new nautilus, but is still has not been committed. Does anyone know what the deal is? Has nushio left the project and should his packages thus be orphaned? Or is he just busy with real life and then I would kindly ask one of the provenpackagers to commit my changes. Well, per: http://fedoraproject.org/wiki/PackageMaintainers/Policy/NonResponsiveMaintainers 1. Nothing on the vacation page. fedora-active-user gives: Last login in FAS: nushio 2012-04-20 Last action on koji: Mon, 15 Nov 2010 package list entry created: gnome-do-docklets in dist-f11 by pkgdb [still active] Last package update on bodhi: 2011-09-21 16:28:42 on package rabbitvcs-0.14.2.1-3.fc16 118 bugs assigned or cc to nus...@fedoraproject.org Still waiting on the BZ/email bits, it's slow. :) 2. You have that below. 3 and 4 are here. 5. Do you want to take over the package, or would provenpackager assistance be more to your liking? Regards, Julian [1] https://bugzilla.redhat.com/show_bug.cgi?id=760682 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- http://cecinestpasunefromage.wordpress.com/ in your fear, seek only peace in your fear, seek only love -d. bowie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Install Fedora Button for LiveCD
On 04/28/2012 12:33 AM, Jared K. Smith wrote: On Fri, Apr 27, 2012 at 3:02 PM, Bill Nottingham nott...@redhat.com wrote: I don't know how proposing and implementing a notification method of doing the same isn't providing a solution, but you're welcome to your own cross. Sorry Bill -- I'm confused here. Was a notification method actually implemented? Was it enabled in F17.TC1? If so, I didn't see it. Or was it implemented only for rawhide? I finished up the work on the notification and landed it in spin-kickstarts, so it should be available with the next media compose for both F17 and rawhide: http://git.fedorahosted.org/git/?p=spin-kickstarts.git;a=commit;h=ef24d01 This is how it currently looks after booting up the Desktop Live CD: http://kalev.fedorapeople.org/anaconda-notification.png Install starts the installer; clicking anywhere else within the black notification box dismisses the notification. -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Review swaps
I'm interested in swapping reviews. Here are the ones I need reviewed: vinci: https://bugzilla.redhat.com/show_bug.cgi?id=790560 permlib: https://bugzilla.redhat.com/show_bug.cgi?id=797312 Let me know what I can review for you. Thanks, -- Jerry James http://www.jamezone.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Install Fedora Button for LiveCD
On 05/01/2012 02:55 PM, Kalev Lember wrote: On 04/28/2012 12:33 AM, Jared K. Smith wrote: On Fri, Apr 27, 2012 at 3:02 PM, Bill Nottingham nott...@redhat.com wrote: I don't know how proposing and implementing a notification method of doing the same isn't providing a solution, but you're welcome to your own cross. Sorry Bill -- I'm confused here. Was a notification method actually implemented? Was it enabled in F17.TC1? If so, I didn't see it. Or was it implemented only for rawhide? I finished up the work on the notification and landed it in spin-kickstarts, so it should be available with the next media compose for both F17 and rawhide: http://git.fedorahosted.org/git/?p=spin-kickstarts.git;a=commit;h=ef24d01 This is how it currently looks after booting up the Desktop Live CD: http://kalev.fedorapeople.org/anaconda-notification.png Install starts the installer; clicking anywhere else within the black notification box dismisses the notification. Excellent thanks! A slight rewording suggestion, especially since hard disks are being rapidly replaced. You are currently using an uninstalled live image. You can try it out directly or install to your system. cheers, Pádraig. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Install Fedora Button for LiveCD
On Tue, May 1, 2012 at 7:55 AM, Kalev Lember kalevlem...@gmail.com wrote: I finished up the work on the notification and landed it in spin-kickstarts, so it should be available with the next media compose for both F17 and rawhide: Cool, thanks. This is how it currently looks after booting up the Desktop Live CD: http://kalev.fedorapeople.org/anaconda-notification.png Install starts the installer; clicking anywhere else within the black notification box dismisses the notification. I've got to be honest here -- I don't like the wording of the notification. In particular, the section that says If you want to keep using Fedora is ambiguous, as you could keep using Fedora from the live media without installing it. Might I suggest the following text instead: You are currently running Fedora from live media. To install Fedora to your hard drive, click the button below or the Install to Hard Drive option in the activities menu. -- Jared Smith -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Install Fedora Button for LiveCD
On May 1, 2012, at 10:25 AM, Jared K. Smith wrote: You are currently running Fedora from live media. To install Fedora to your hard drive, click the button below or the Install to Hard Drive option in the activities menu. You are currently running Fedora from live media. To install Fedora, click Install, or choose Install to Hard Drive in the Activities menu. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 17 Change Freeze
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, the fedora 17 schedule http://fedoraproject.org/wiki/Releases/17/Schedule lists the final change freeze as 2012-05-07 this means that you need to make sure that any changes you want in Fedora 17 final must be submited for stable in Bodhi before 2012-05-07 there will be a small window on monday where you can get your build in still but it is not assured. after this time only blocker bugs will be accepted to be pushed for stable. please work on testing and ensuring anything you want in final has the appropriate karma. If you have questions please drop by #fedora-releng on freenode Thanks Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk+gK7EACgkQkSxm47BaWffyRgCcCi8BEXJjgkPYrxS1A3kY0pmu WMUAnjSB7fhuYAu7Vb3cokhV6olltp+j =mQZP -END PGP SIGNATURE- ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does anyone know what is up with nushio?
W dniu 2012-05-01 15:23, Jon Ciesla pisze: On Tue, May 1, 2012 at 6:21 AM, Julian Sikorskibeleg...@gmail.com wrote: Hello, nushio, the rabbitvcs maintainer has not been answering one of his bug reports [1]. I have prepared an updated package that works with the new nautilus, but is still has not been committed. Does anyone know what the deal is? Has nushio left the project and should his packages thus be orphaned? Or is he just busy with real life and then I would kindly ask one of the provenpackagers to commit my changes. Well, per: http://fedoraproject.org/wiki/PackageMaintainers/Policy/NonResponsiveMaintainers 1. Nothing on the vacation page. fedora-active-user gives: Last login in FAS: nushio 2012-04-20 Last action on koji: Mon, 15 Nov 2010 package list entry created: gnome-do-docklets in dist-f11 by pkgdb [still active] Last package update on bodhi: 2011-09-21 16:28:42 on package rabbitvcs-0.14.2.1-3.fc16 118 bugs assigned or cc to nus...@fedoraproject.org Still waiting on the BZ/email bits, it's slow. :) 2. You have that below. 3 and 4 are here. I am not sure what you mean here... 5. Do you want to take over the package, or would provenpackager assistance be more to your liking? Last time I looked on the upstream git activity it was not clear if it is going to stay alive or not, so I'd say let's do a drive-by update now, and if the upstream situation clears out I can consider a proper takeover. Julian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 17 Change Freeze
On 1 May 2012 19:30, Dennis Gilmore den...@ausil.us wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, the fedora 17 schedule http://fedoraproject.org/wiki/Releases/17/Schedule lists the final change freeze as 2012-05-07 this means that you need to make sure that any changes you want in Fedora 17 final must be submited for stable in Bodhi before 2012-05-07 there will be a small window on monday where you can get your build in still but it is not assured. after this time only blocker bugs will be accepted to be pushed for stable. please work on testing and ensuring anything you want in final has the appropriate karma. If you have questions please drop by #fedora-releng on freenode There are a number of preupgrade bugs not marked as blockers, what happens to these? https://bugzilla.redhat.com/show_bug.cgi?id=813973 https://bugzilla.redhat.com/show_bug.cgi?id=817383 https://bugzilla.redhat.com/show_bug.cgi?id=817384 This one might not prevent upgrade: https://bugzilla.redhat.com/show_bug.cgi?id=817388 -- imalone http://ibmalone.blogspot.co.uk -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Anaconda 17.24-1 reverts to msdos disklabels for new installs
Back in Fedora 16 we tried to advance the state of the art. We switched to using GPT disklabels by default, and in many cases this worked just fine. But it has become increasingly obvious that the hardware isn't ready for us. We continue to get reports of boot problems related to BIOS that attempt to examine the disk before booting and GPT confuses them -- even when we set the PMBR's boot flag. So, for Fedora 17 we are going backwards and will wait for the world to catch up. What's changed: * msdos disklabels will be the default for disks under 2TB * GPT can be forced by passing gpt on the kernel cmdline * nogpt cmdline argument has been removed This only effects BIOS installs. EFI will continue to use GPT, as will disks larger than 2T -- Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT) pgph1Df6Xvsqj.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 17 Change Freeze
On Wed, 2 May 2012 00:01:23 +0100 Ian Malone ibmal...@gmail.com wrote: On 1 May 2012 19:30, Dennis Gilmore den...@ausil.us wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, the fedora 17 schedule http://fedoraproject.org/wiki/Releases/17/Schedule lists the final change freeze as 2012-05-07 this means that you need to make sure that any changes you want in Fedora 17 final must be submited for stable in Bodhi before 2012-05-07 there will be a small window on monday where you can get your build in still but it is not assured. after this time only blocker bugs will be accepted to be pushed for stable. please work on testing and ensuring anything you want in final has the appropriate karma. If you have questions please drop by #fedora-releng on freenode There are a number of preupgrade bugs not marked as blockers, what happens to these? That depends on where the actual bug is, to be honest. If it's in the actual preupgrade package itself - that's in F15 and F16 and would not be affected by the F17 code freeze https://bugzilla.redhat.com/show_bug.cgi?id=813973 This is a known limitation - workarounds are documented in the wiki http://fedoraproject.org/wiki/How_to_use_PreUpgrade#Not_enough_space_in_.2Fboot https://bugzilla.redhat.com/show_bug.cgi?id=817383 https://bugzilla.redhat.com/show_bug.cgi?id=817384 This is the first that I've heard of either of these - if you think they're worthy of being release blockers, feel free to mark them as such. The process for marking bugs as release blockers or NTH is documented at: - http://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - http://fedoraproject.org/wiki/QA:SOP_nth_bug_process You can find the tracker bugs to block on this page: - http://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers Tim signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Weekly ARM status meeting - Wed 2012/05/02
Hi everyone, A reminder that this week's ARM status meeting will take place tomorrow (Wednesday), on #fedora-meeting. There will be no phone call. Times in various timezones: PDT: 1pm MDT: 2pm CDT: 3pm EDT: 4pm UTC: 8pm BST: 9pm CST: 10pm Also join #fedora-arm on Freenode for general ARM discussion before/after the weekly syncup. Agenda: 0). Current build status - Gnarly bugs and build failures - Sending out regular problem package mails? - Atomics on older processors (v5)/LLVM/etc. 1). Fedora 17 Beta - What are the constraints on getting this out next week? - David will update us on media creation, etc. too 2). Secondary Architecture Promotion - Status of ARM toward promotion criteria (Brendan and Dennis have the ball, quick sync) 3). Your topic here Jon. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Review swaps
2012/5/1 Jerry James loganje...@gmail.com: I'm interested in swapping reviews. Here are the ones I need reviewed: vinci: https://bugzilla.redhat.com/show_bug.cgi?id=790560 permlib: https://bugzilla.redhat.com/show_bug.cgi?id=797312 Let me know what I can review for you. Thanks, Ok. I replied in the above with what I could help, and just made a newer package required by sagemath https://bugzilla.redhat.com/show_bug.cgi?id=817981 Later I will try to make a proper singular package, and work a bit more in the initial cliquer package I made just to get further in sagemath build. With the ratpoints package, now it fails in singular build. -- Jerry James http://www.jamezone.org/ Paulo -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Review swaps
2012/5/1 Paulo César Pereira de Andrade paulo.cesar.pereira.de.andr...@gmail.com: 2012/5/1 Jerry James loganje...@gmail.com: I'm interested in swapping reviews. Here are the ones I need reviewed: vinci: https://bugzilla.redhat.com/show_bug.cgi?id=790560 permlib: https://bugzilla.redhat.com/show_bug.cgi?id=797312 Let me know what I can review for you. Thanks, Ok. I replied in the above with what I could help, and just made a newer package required by sagemath https://bugzilla.redhat.com/show_bug.cgi?id=817981 Later I will try to make a proper singular package, and work a bit more in the initial cliquer package I made just to get further in sagemath build. With the ratpoints package, now it fails in singular build. Oops, I remembered I did look very quickly in cliquer, and it was because I just made a few quick patches to your package :-) You may want to check http://kenobi.mandriva.com/~pcpa/cliquer-1.21-1.fc16.src.rpm for the changes I made. The only extra file should be cl.h, that I took from the mandriva repository, and afaik I got it originally from sagemath srpm, but in mandriva I also used the upstream tarball. -- Jerry James http://www.jamezone.org/ Paulo -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does anyone know what is up with nushio?
On Tue, May 1, 2012 at 2:39 PM, Julian Sikorski beleg...@gmail.com wrote: W dniu 2012-05-01 15:23, Jon Ciesla pisze: On Tue, May 1, 2012 at 6:21 AM, Julian Sikorskibeleg...@gmail.com wrote: Hello, nushio, the rabbitvcs maintainer has not been answering one of his bug reports [1]. I have prepared an updated package that works with the new nautilus, but is still has not been committed. Does anyone know what the deal is? Has nushio left the project and should his packages thus be orphaned? Or is he just busy with real life and then I would kindly ask one of the provenpackagers to commit my changes. Well, per: http://fedoraproject.org/wiki/PackageMaintainers/Policy/NonResponsiveMaintainers 1. Nothing on the vacation page. fedora-active-user gives: Last login in FAS: nushio 2012-04-20 Last action on koji: Mon, 15 Nov 2010 package list entry created: gnome-do-docklets in dist-f11 by pkgdb [still active] Last package update on bodhi: 2011-09-21 16:28:42 on package rabbitvcs-0.14.2.1-3.fc16 118 bugs assigned or cc to nus...@fedoraproject.org Still waiting on the BZ/email bits, it's slow. :) 2. You have that below. 3 and 4 are here. I am not sure what you mean here... Just that you've done those steps as of your email. 5. Do you want to take over the package, or would provenpackager assistance be more to your liking? Last time I looked on the upstream git activity it was not clear if it is going to stay alive or not, so I'd say let's do a drive-by update now, and if the upstream situation clears out I can consider a proper takeover. I'll update this for rawhide, f17 and f16. -J Julian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- http://cecinestpasunefromage.wordpress.com/ in your fear, seek only peace in your fear, seek only love -d. bowie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Review swaps
On Tue, May 1, 2012 at 6:35 PM, Paulo César Pereira de Andrade paulo.cesar.pereira.de.andr...@gmail.com wrote: Oops, I remembered I did look very quickly in cliquer, and it was because I just made a few quick patches to your package :-) You may want to check http://kenobi.mandriva.com/~pcpa/cliquer-1.21-1.fc16.src.rpm for the changes I made. The only extra file should be cl.h, that I took from the mandriva repository, and afaik I got it originally from sagemath srpm, but in mandriva I also used the upstream tarball. Okay, I will try to look at that tomorrow. Thanks, Paulo. And, for the record, I still need someone to swap those 2 reviews with me. Thanks! -- Jerry James http://www.jamezone.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Does anyone know what is up with nushio?
W dniu 2012-05-02 03:12, Jon Ciesla pisze: On Tue, May 1, 2012 at 2:39 PM, Julian Sikorskibeleg...@gmail.com wrote: W dniu 2012-05-01 15:23, Jon Ciesla pisze: On Tue, May 1, 2012 at 6:21 AM, Julian Sikorskibeleg...@gmail.com wrote: Hello, nushio, the rabbitvcs maintainer has not been answering one of his bug reports [1]. I have prepared an updated package that works with the new nautilus, but is still has not been committed. Does anyone know what the deal is? Has nushio left the project and should his packages thus be orphaned? Or is he just busy with real life and then I would kindly ask one of the provenpackagers to commit my changes. Well, per: http://fedoraproject.org/wiki/PackageMaintainers/Policy/NonResponsiveMaintainers 1. Nothing on the vacation page. fedora-active-user gives: Last login in FAS: nushio 2012-04-20 Last action on koji: Mon, 15 Nov 2010 package list entry created: gnome-do-docklets in dist-f11 by pkgdb [still active] Last package update on bodhi: 2011-09-21 16:28:42 on package rabbitvcs-0.14.2.1-3.fc16 118 bugs assigned or cc to nus...@fedoraproject.org Still waiting on the BZ/email bits, it's slow. :) 2. You have that below. 3 and 4 are here. I am not sure what you mean here... Just that you've done those steps as of your email. 5. Do you want to take over the package, or would provenpackager assistance be more to your liking? Last time I looked on the upstream git activity it was not clear if it is going to stay alive or not, so I'd say let's do a drive-by update now, and if the upstream situation clears out I can consider a proper takeover. I'll update this for rawhide, f17 and f16. -J Julian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Thank you for your assistance. Julian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File CPAN-Changes-0.19.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-CPAN-Changes: 0091529b269037e959291dd64af8b178 CPAN-Changes-0.19.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-CPAN-Changes] Update to 0.19
commit de6564e6c90ea58f68a5d920d04d91dcb4471bd4
Author: Paul Howarth p...@city-fan.org
Date: Tue May 1 10:22:01 2012 +0100
Update to 0.19
- New upstream release 0.19:
- Test::CPAN::Changes now accepts version entries ending in '-TRIAL'
(CPAN RT#76882)
- releases() in CPAN::Changes also accepts entries ending in '-TRIAL'
- Don't need to remove empty directories from buildroot
- Drop %defattr, redundant since rpm 4.4
perl-CPAN-Changes.spec | 14 ++
sources|2 +-
2 files changed, 11 insertions(+), 5 deletions(-)
---
diff --git a/perl-CPAN-Changes.spec b/perl-CPAN-Changes.spec
index b552be4..65fc9b4 100644
--- a/perl-CPAN-Changes.spec
+++ b/perl-CPAN-Changes.spec
@@ -1,7 +1,7 @@
Name: perl-CPAN-Changes
Summary: Read and write Changes files
-Version: 0.18
-Release: 2%{?dist}
+Version: 0.19
+Release: 1%{?dist}
License: GPL+ or Artistic
Group: Development/Libraries
URL: http://search.cpan.org/dist/CPAN-Changes/
@@ -38,7 +38,6 @@ make %{?_smp_mflags}
%install
make pure_install DESTDIR=%{buildroot}
find %{buildroot} -type f -name .packlist -exec rm -f {} \;
-find %{buildroot} -depth -type d -exec rmdir {} \; 2/dev/null
%{_fixperms} %{buildroot}
%check
@@ -46,7 +45,6 @@ make test
make test TEST_FILES=$(echo $(find xt/ -name '*.t'))
%files
-%defattr(-,root,root,-)
%doc Changes README
%{perl_vendorlib}/CPAN/
%{perl_vendorlib}/Test/
@@ -56,6 +54,14 @@ make test TEST_FILES=$(echo $(find xt/ -name '*.t'))
%{_mandir}/man3/Test::CPAN::Changes.3pm*
%changelog
+* Tue May 1 2012 Paul Howarth p...@city-fan.org - 0.19-1
+- Update to 0.19:
+ - Test::CPAN::Changes now accepts version entries ending in '-TRIAL'
+(CPAN RT#76882)
+ - releases() in CPAN::Changes also accepts entries ending in '-TRIAL'
+- Don't need to remove empty directories from buildroot
+- Drop %%defattr, redundant since rpm 4.4
+
* Tue Jan 10 2012 Paul Howarth p...@city-fan.org - 0.18-2
- Fedora 17 mass rebuild
diff --git a/sources b/sources
index 34c84bc..3f3819d 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-e30fbdaa1d94f99d25b1342ba604e239 CPAN-Changes-0.18.tar.gz
+0091529b269037e959291dd64af8b178 CPAN-Changes-0.19.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-CPAN-Changes] Created tag perl-CPAN-Changes-0.19-1.fc18
The lightweight tag 'perl-CPAN-Changes-0.19-1.fc18' was created pointing to: de6564e... Update to 0.19 -- 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 Image-ExifTool-8.90.tar.gz uploaded to lookaside cache by spot
A file has been added to the lookaside cache for perl-Image-ExifTool: c34f2138af14e7ab75bddb12d9e8e726 Image-ExifTool-8.90.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Image-ExifTool] 8.90
commit 1fee4500ae8af2ab6e74750d5bb04522bf666dec
Author: Tom Callaway s...@fedoraproject.org
Date: Tue May 1 16:15:42 2012 -0400
8.90
.gitignore |1 +
perl-Image-ExifTool.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index deb7774..f9efc29 100644
--- a/.gitignore
+++ b/.gitignore
@@ -6,3 +6,4 @@ Image-ExifTool-8.25.tar.gz
/Image-ExifTool-8.75.tar.gz
/Image-ExifTool-8.77.tar.gz
/Image-ExifTool-8.85.tar.gz
+/Image-ExifTool-8.90.tar.gz
diff --git a/perl-Image-ExifTool.spec b/perl-Image-ExifTool.spec
index 5f28b46..a1ca938 100644
--- a/perl-Image-ExifTool.spec
+++ b/perl-Image-ExifTool.spec
@@ -1,5 +1,5 @@
Name: perl-Image-ExifTool
-Version: 8.85
+Version: 8.90
Release: 1%{?dist}
License: GPL+ or Artistic
Group: Applications/Multimedia
@@ -51,6 +51,9 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Tue May 1 2012 Tom Callaway s...@fedoraproject.org - 8.90-1
+- update to 8.90
+
* Tue Apr 3 2012 Tom Callaway s...@fedoraproject.org - 8.85-1
- update to 8.85
diff --git a/sources b/sources
index 239aef0..27e193a 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-3bb1b595473a91da5757ca8d5f5703af Image-ExifTool-8.85.tar.gz
+c34f2138af14e7ab75bddb12d9e8e726 Image-ExifTool-8.90.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Image-ExifTool/f17] 8.90
commit 1e4e5ae2dc431a230109ca462949a8e2d594fe5c
Author: Tom Callaway s...@fedoraproject.org
Date: Tue May 1 16:15:57 2012 -0400
8.90
perl-Image-ExifTool.spec |5 -
sources |2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
---
diff --git a/perl-Image-ExifTool.spec b/perl-Image-ExifTool.spec
index 5f28b46..a1ca938 100644
--- a/perl-Image-ExifTool.spec
+++ b/perl-Image-ExifTool.spec
@@ -1,5 +1,5 @@
Name: perl-Image-ExifTool
-Version: 8.85
+Version: 8.90
Release: 1%{?dist}
License: GPL+ or Artistic
Group: Applications/Multimedia
@@ -51,6 +51,9 @@ make test
%{_mandir}/man3/*.3*
%changelog
+* Tue May 1 2012 Tom Callaway s...@fedoraproject.org - 8.90-1
+- update to 8.90
+
* Tue Apr 3 2012 Tom Callaway s...@fedoraproject.org - 8.85-1
- update to 8.85
diff --git a/sources b/sources
index 239aef0..27e193a 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-3bb1b595473a91da5757ca8d5f5703af Image-ExifTool-8.85.tar.gz
+c34f2138af14e7ab75bddb12d9e8e726 Image-ExifTool-8.90.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 Gtk2-1.243.tar.gz uploaded to lookaside cache by spot
A file has been added to the lookaside cache for perl-Gtk2: 77d2abaca66ac631269f8eb57f84bcf2 Gtk2-1.243.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Gtk2] 1.243
commit e7fd3169fab3104fc49a0801c2642f6afdaa0ee6
Author: Tom Callaway s...@fedoraproject.org
Date: Tue May 1 16:30:09 2012 -0400
1.243
.gitignore |1 +
perl-Gtk2.spec |7 +--
sources|2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 834a122..f962ee9 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@ Gtk2-1.203.tar.gz
/Gtk2-1.224.tar.gz
/Gtk2-1.240.tar.gz
/Gtk2-1.241.tar.gz
+/Gtk2-1.243.tar.gz
diff --git a/perl-Gtk2.spec b/perl-Gtk2.spec
index 48b6c5c..4095929 100644
--- a/perl-Gtk2.spec
+++ b/perl-Gtk2.spec
@@ -5,8 +5,8 @@
#
Name: perl-Gtk2
-Version:1.241
-Release:2%{?dist}
+Version:1.243
+Release:1%{?dist}
Summary:Perl interface to the 2.x series of the Gimp Toolkit library
Group: Development/Libraries
License:LGPLv2+
@@ -70,6 +70,9 @@ chmod -R u+w $RPM_BUILD_ROOT/*
%{_mandir}/man3/*.3pm*
%changelog
+* Tue May 1 2012 Tom Callaway s...@fedoraproject.org - 1.243-1
+- update to 1.243
+
* Fri Jan 13 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.241-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild
diff --git a/sources b/sources
index 6cb253b..53f08fc 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-82ee2af46ef9ab7b560601e3ae6f8f7a Gtk2-1.241.tar.gz
+77d2abaca66ac631269f8eb57f84bcf2 Gtk2-1.243.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: libpython2.7.so, /usr/lib or /usr/lib64, Liquid error parsing markdown
On Tue, May 01, 2012 at 12:25:30PM +0700, Nick Fenwick wrote: On 05/01/2012 11:47 AM, Nick Fenwick wrote: python-2.7.2-5.2.fc16.x86_64 It seems that because I had only the 64 bit python rpms installed, I didn't have the 32 bit libraries. ln -s /usr/lib64/libpython2.7.so /usr/lib/libpython2.7.so This was a hack. Installing i686 architecture fixed my problem more gracefully. yum install libpython.i686 Do you feel this is a dependency problem in one of the other systems I've installed (ruby, octopress), and their dependency on python? Perhaps I should move this query onto some other forum, such as rvm (the ruby installer, some part of which installed rubypython). There's a thread at https://github.com/ imathis/octopress/issues/251 where the Octopress guy seems to be distancing himself from dependency management, which doesn't look promising if the ball's actually in his court. Yeah -- on 64bit multilib, the system should find the 64 bit libraries in /usr/lib64/ and on 32bit multilib systems, in /usr/lib/. It's a little strange to me that your program works with either the 64bit compiled library or the 32bit compiled library. (It used the 64bit lib when you symlinked and the 32bit lib when you installed the 32bit package). Normally the program you've installed is linked at buildtime to one or the other (and built to work with a library that expects certain types to be of a certain size associated with that architecture). This also seems to imply that the library is not being loaded by the system dynamic linker but by something else -- perhaps it's being brought in as part of a dlopen'd object. My best guess is that this is a problem with one of the things that's making use of libpython. Perhaps the program was built on a 32bit system and it therefore assumes that libraries are in /usr/lib/. Perhaps the path is hardcoded to be /usr/lib/ in the build scripts. -Toshio pgpxOeBMCY556.pgp Description: PGP signature ___ python-devel mailing list python-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/python-devel
