Re: Scala package owner unresponsive
On 08/22/2013 01:03 PM, Jochen Schmitt wrote: Yes, the reason fot this is very simple. On F18 we had a jdk-1.6.0 environment in addition to the jdk-1.7.0. Scala was built explicitly agains jdk-1.6.0 because jdk-1.7.0 is not supported on this release. Really? How did *that* happen? -- Florian Weimer / Red Hat Product Security Team -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Changes to make MySQL vs. MariaDB less confusing
On 22 August 2013 08:27, Bjorn Munch bjorn.mu...@oracle.com wrote: Yes we are! Sorry for the long silence. The window for F19 closed so it became less urgent, then I had vacation, was sick, then others here were on vacation but we're all here now and I shall be uploading new packages with MySQL 5.6.13 very soon. They are already ready internally, but I need to do some final checks and a scratch build. I was indeed planning to do that today anyway. I will get back with more details later. It's this sort of behaviour that leads many of us to want to wash our hands of Oracle in the first place... As for the 'window for F19' well you've missed the window for F20 now as well ... However that is somewhat of a moot point given that (and the AOO issues are similar but let's stay focused on mysql/mariadb) things like spec files, package reviews and so on don't need a release to target anyway - they just need bugzilla tickets and builds in koji following the standard packaging guidelines that everyone - big company or little individuals - need to follow. Once things are building cleanly there and package review is passed (and any outstanding conflict questions are dealt with) then fine look at adding it as a feature for a future Fedora - but that is a long way off at this point still it seems. Frankly I'm still of the opinion the Oracle distribution of the MySQL based server should be dropped entirely... If Oracle want 'community-mysql' to exist for Fedora and want to maintain it themselves then they can set up their own repositories on their own infrastructure and these compatibilities issues with Fedora can be removed entirely as a result. As for an upgrade of community-mysql from 5.5 to 5.6 that should probably be discussed or be considered as a feature in case of knock on issues with respect to F18 users upgrading (didn't the obsolete for mariadb only cover 5.5?) plus the loss of file level compatibility for someone to make a switch between community-mysql and mariadb at their choosing... plus there's a lot of non-backwards compatible changes that people need to be aware of from 5.5 to 5.6: http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Self introduction
Hi all, I'd like to introduce myself as a new packager. I've created a review request here for nitrogen: https://bugzilla.redhat.com/show_bug.cgi?id=1000275 Nitrogen is a lightweight desktop background setter that was orphaned before the F19 release, I decided to package it after I got annoyed that I had to get the RPM from pbone.net :P And yes, I'm looking for a sponser :) A little about me, I'm a student living in New Zealand. I've been using Fedora since I was 12, and regularly compile builds of various Blender development branches for others to use. I love 3D modeling + compositing and have worked as a volunteer modeler in a short film. Thanks, James Wrigley -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Changes to make MySQL vs. MariaDB less confusing
On Fri, Aug 23, 2013 at 9:40 AM, James Hogarth james.hoga...@gmail.comwrote: On 22 August 2013 08:27, Bjorn Munch bjorn.mu...@oracle.com wrote: Yes we are! Sorry for the long silence. The window for F19 closed so it became less urgent, then I had vacation, was sick, then others here were on vacation but we're all here now and I shall be uploading new packages with MySQL 5.6.13 very soon. They are already ready internally, but I need to do some final checks and a scratch build. I was indeed planning to do that today anyway. I will get back with more details later. It's this sort of behaviour that leads many of us to want to wash our hands of Oracle in the first place... Sorry to say, but to me it rather sounds just plain human. As for the 'window for F19' well you've missed the window for F20 now as well ... However that is somewhat of a moot point given that (and the AOO issues are similar but let's stay focused on mysql/mariadb) things like spec files, package reviews and so on don't need a release to target anyway - they just need bugzilla tickets and builds in koji following the standard packaging guidelines that everyone - big company or little individuals - need to follow. Once things are building cleanly there and package review is passed (and any outstanding conflict questions are dealt with) then fine look at adding it as a feature for a future Fedora - but that is a long way off at this point still it seems. Frankly I'm still of the opinion the Oracle distribution of the MySQL based server should be dropped entirely... If Oracle want 'community-mysql' to exist for Fedora and want to maintain it themselves then they can set up their own repositories on their own infrastructure and these compatibilities issues with Fedora can be removed entirely as a result. As for an upgrade of community-mysql from 5.5 to 5.6 that should probably be discussed or be considered as a feature in case of knock on issues with respect to F18 users upgrading (didn't the obsolete for mariadb only cover 5.5?) plus the loss of file level compatibility for someone to make a switch between community-mysql and mariadb at their choosing... plus there's a lot of non-backwards compatible changes that people need to be aware of from 5.5 to 5.6: http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 schedule: what would you do with more time?
On Thu, Aug 22, 2013 at 4:12 PM, Matthew Miller mat...@fedoraproject.orgwrote: On Thu, Aug 22, 2013 at 11:08:18PM +0800, Christopher Meng wrote: What things we do _now_ could be improved with the investment of some effort? Perl rebuild always take a lot of time, and as a result it will affect the mass rebuild. Apparently less so with all the new ARM builders, right? Is this something you're saying could be improved, or is it just something we always need to budget time for? The perl upgrade process is some what manual and there's a whole bunch of circular dependencies that cause/require a bunch of manual bootstrapping of certain packages so the perl mass rebuild is some what different to a standard all in mass rebuild. Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 schedule: what would you do with more time?
On Thu, Aug 22, 2013 at 4:56 PM, Mat Booth fed...@matbooth.co.uk wrote: On 22 August 2013 16:03, Matthew Miller mat...@fedoraproject.org wrote: Based on discussion at Flock, on the devel mailing list, and in the FESCo meeting, we are looking for feedback on the idea of a longer release cycle for Fedora 21 -- not (right now at least) the bigger question of the 6-month cycle overall, but just, right now, slowing down for a release to get some things in order. Specifically, both Release Engineering and QA have clear needs (and even plans for) greater automatiion, but are also incredibly busy simply doing the things they need to do _now_ to get the release out the door. So, FESCo would like to see some specifics, like If we had one week with nothing else to worry about, we could have automated generation and upload of cloud images (to pick an example I personally care about). Or with six months of overall delay, we could have continuous integration testing of a key subset of rawhide. Or we could spend a couple of weeks and automate the new package and review workflow. What Infrastructure projects would be helped by this? Web and design team, would slowing down the release focus allow time to work on, oh, say, getting the Wiki beautiful (or does it not matter)? What else? As we look at Fedora.next ideas and possibly decide to start implementation in the F21 timeframe, we will likely find _new_ things that take specific work. Let's not worry about that right now. What things we do _now_ could be improved with the investment of some effort? Here's my favourite bugbear: https://fedorahosted.org/packagedb/ticket/243 I have no idea why the package retirement process needs intervention from rel-eng.-- Mat Booth http://fedoraproject.org/get-fedora There's been discussion of adding fedpkg retire-package to fedpkg which would basically just open a dead.package file to allow you to add an entry and then remove the contents from git, block the package in koji, and retire it in the package DB. I don't think anyone has had the time to do this yet both in fedpkg and the backend although I suspect this gets a whole lot easier now with fedmsg. Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Problem with sed in spec file
On Wed, Aug 21, 2013 at 6:58 PM, Juan Orti Alcaine juan.o...@miceliux.com wrote: El Miércoles, 21 de agosto de 2013 16:03:23 Richard W.M. Jones escribió: Just open a bug against selinux-policy and ask the maintainer to drop a file somewhere which contains the version number, eg: %install echo '%{version}' $RPM_BUILD_ROOT%{_datadir}/selinux/version We do something similar in the OCaml compiler base package. Rich. Done. https://bugzilla.redhat.com/show_bug.cgi?id=999584 Or possibly even better, drop it into /usr/lib/rpm/macros.d so it can be used even easier in specfiles, something like echo '%%_selinux_policy_version %{version}' \ $RPM_BUILD_ROOT%{_rpmconfigdir}/macros.d/selinux-policy.macros -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 schedule: what would you do with more time?
E.g. going after these: http://ausil.fedorapeople.org/**f20-failed.htmlhttp://ausil.fedorapeople.org/f20-failed.html Right now we have ~350+ broken packages, a lengthy series of broken deps, an unknown amount of defacto unmaintained packages and an unknown amout of maintainers having gone MIA. Agreed. What Infrastructure projects would be helped by this? A web infrastructure to * ease package orphanage. * launch AWOL/MIA requests * a unified koji/bodhi/bugzilla Web-GUI You think BZ is slow now? * much longer build.log holding time for FTBFS. I think this comes down to the amount of storage it takes and the amount we have available. Also, - faster builders: Introduction of the arm has significantly increased the turn around times of package building. - better mirroring: I am having the impression mirrormanager doesn't work well at all. E.g. this morning, yum sent me around the globe for rawhide and failed in the end, seemingly because all fast mirrors seem to be busy loading f20. TBF I don't believe this is anything to do with mirror manager at all, the fact is a lot of mirrors just don't hold rawhide or don't update it daily so they're at times out of date. Secondary arches have similar issues regarding those sorts of problems because there's a lot less mirrors of those. Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [ACTION REQUIRED] Retiring long-term FTBFS packages for Fedora 20
On Tue, Aug 20, 2013 at 12:05 AM, Till Maas opensou...@till.name wrote: smart athimm, scop Where does this information about maintainers come from? Once upon a time I (scop) was a co-maintainer for this package, but I believe I've resigned a long time ago, and packagedb doesn't show me associated with it. https://admin.fedoraproject.org/pkgdb/acls/name/smart -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Thu, 2013-08-22 at 22:05 -0700, Adam Williamson wrote: On Thu, 2013-08-22 at 21:47 -0700, Adam Williamson wrote: As plupload is a .sh not a .as3 I *think* we may be able to build it with swfc. I'll see whether that's possible. plupload looks like, well, a giant pain in the ass. It depends on a bit called moxie which is just kinda smooshed into the .swf shipped with wordpress. If someone else wants to work on building that mess, go for it, but for now, I'm going to work on ripping out the Flash and Silverlight parts from plupload, and ripping out swfupload entirely. I've done a super-dumb test scratch build of wordpress at http://koji.fedoraproject.org/koji/taskinfo?taskID=5844538 which more or less just rips swfupload out entirely, and rips out the other binary blobs with no adjustments, hoping the plugins that use them will fall back or error out intelligently. Help testing this is welcome. Trying to rip the bits out any more delicately looks to be a royal PITA. Bloody minified javascript. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Thu, 2013-08-15 at 13:45 -0700, T.C. Hollingsworth wrote: It's come to my attention that a number of packages contain Flash (.swf) files, but absolutely none of them have BuildRequires on a free software Flash toolchain, nor do any of them seem to be shipping the source for these files. :-( It has never been permissible to included prebuilt files of this nature in Fedora [1], and FPC unequivocally stated during today's meeting that they have no interest in making an exception for this. Please remove this prohibited content from your packages, or ensure that any included .swf files are built from source using a free software toolchain like `swfc` during the %build phase. A list of affected packages sorted by owner is included below, and I'll be filing bugs for these soon. -T.C. [1] https://fedoraproject.org/wiki/Packaging:Guidelines#No_inclusion_of_pre-built_binaries_or_libraries brummbq owncloud I've quickly tested and built a 'fix' for owncloud (just dropping the plugins, really) for F18, F19, F20 and Rawhide. See https://bugzilla.redhat.com/show_bug.cgi?id=1000257 . -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 schedule: what would you do with more time?
On 08/23/2013 10:39 AM, Peter Robinson wrote: * a unified koji/bodhi/bugzilla Web-GUI You think BZ is slow now? What do you mean by now ... now as in comparison to yesterday, or in general. In general, my issues with bugzilla basically are two: - It's UI is clumsy to use for Fedora - filing or searching bugs requires a lot of user interaction, some of which are not easy to accomplish. I meanwhile have begun to favor searching BZ for some classes of BZs through the pkgdb (https://admin.fedoraproject.org/pkgdb/packages), because its UI seems easier to use. - The turnaround times, esp, during searches leaves much to be desired on my side. I have no idea about the cause, whether my gradually aging machine has become too slow for bugzilla, whether I am having a bad network connection to BZ@RH, whether my firefox/F19 is having problems or if bugzilla is having performance problems. All I can say, my subjective experience with bugzilla often is jerky responses to UI interactions. In most cases in the order of several seconds, but sometimes also in the order of several tenths of seconds, in rare cases in the order of several minutes. I meanwhile am leaning to enter and search BZ throuhg https://admin.fedoraproject.org/pkgdb/packages * much longer build.log holding time for FTBFS. I think this comes down to the amount of storage it takes and the amount we have available. Is that really that much? I am not asking for keeping all of a failed built forever. I am only asking to keep the last failed builts, or at least the log files of them. When it comes to estimating whether somebody might be able to help out, they are a valuable resoure. At least I stop looking into FTBFSes, when noticing the class of failure probably appears not to be in my domain of knowledge. - better mirroring: I am having the impression mirrormanager doesn't work well at all. E.g. this morning, yum sent me around the globe for rawhide and failed in the end, seemingly because all fast mirrors seem to be busy loading f20. TBF I don't believe this is anything to do with mirror manager at all, the fact is a lot of mirrors just don't hold rawhide or don't update it daily so they're at times out of date. Well, I am pretty sure the metalink files as being provided by dl.fedoraproject.org occasionally point me to mirrors which were out-of-sync. These incidents sometimes seem to be temporary, but I've also observed cases where mirror manager pointed me to mirrors which seem to have been busy syncing. This not only happens for rawhide and not only during branching, but occasionally also happens with fedora-updates. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Thu, 2013-08-15 at 13:45 -0700, T.C. Hollingsworth wrote: It's come to my attention that a number of packages contain Flash (.swf) files, but absolutely none of them have BuildRequires on a free software Flash toolchain, nor do any of them seem to be shipping the source for these files. :-( It has never been permissible to included prebuilt files of this nature in Fedora [1], and FPC unequivocally stated during today's meeting that they have no interest in making an exception for this. Please remove this prohibited content from your packages, or ensure that any included .swf files are built from source using a free software toolchain like `swfc` during the %build phase. A list of affected packages sorted by owner is included below, and I'll be filing bugs for these soon. -T.C. [1] https://fedoraproject.org/wiki/Packaging:Guidelines#No_inclusion_of_pre-built_binaries_or_libraries limb roundcubemail ngompa tinymce So, tinymce has a 'media' plugin which lets you embed media in HTML you're editing with it. If it thinks the media might need playing with Flash, it'll generate HTML that tries to use a Flash player - moxieplayer.swf - to play it (sometimes as a fallback from HTML5). Just nuking moxieplayer.swf doesn't stop tinymce generating HTML that looks for it, so that's not really the way to go. But I think I found a way to patch the plugin not to try and use moxieplayer.swf and just to spit out nice clean HTML instead. I also bumped tinymce to the latest upstream release, since it hadn't been bumped since 2011 and was *ancient*. Testing of this is very welcome. I've sent the build to Rawhide and F20 for now. roundcubemail is on this list because it bundles tinymce, basically. I think it should be trivial to replace its bundled tinymce with the system-wide one. I'm going to test installing the updated and de-Flashed tinymce along with a roundcubemail build patched to use a system-wide tinymce on my own server and check that it works okay that way. If it does, I'll submit that combination to all Fedora releases. I suspect many other packages on the list may be there because they're bundling tinymce. In most cases, unbundling it ought to be trivial; it seems like the 3.x series of tinymce maintained compatibility well, so I think it shouldn't be a problem to use system-wide tinymce. But I'll look into it some more tomorrow. askbot is the only package right now using the systemwide tinymce. I'm assuming ask.fp.o runs on EL, but I'm not sure. Any infra folks reading this, would you be interested in checking ask.fp.o behaves sensibly with de-Flashed tinymce 3.5.8? I don't think the Flash issue should matter at all because it looks like askbot customizes the tinymce editor widget somewhat and doesn't actually expose the media plugin _at all_. I don't see why it wouldn't work with tinymce 3.5.8 - in fact it ought to work better - but we should probably check. Random note: patching minifed javascript is a giant fucking PITA, and we can't edit the 'source' javascript for tinymce and re-minify it because Fedora doesn't have yuicompressor - https://bugzilla.redhat.com/show_bug.cgi?id=745515 . Sigh. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 schedule: what would you do with more time?
Dne 23.8.2013 10:24, Peter Robinson napsal(a): On Thu, Aug 22, 2013 at 4:12 PM, Matthew Miller mat...@fedoraproject.org mailto:mat...@fedoraproject.org wrote: On Thu, Aug 22, 2013 at 11:08:18PM +0800, Christopher Meng wrote: What things we do _now_ could be improved with the investment of some effort? Perl rebuild always take a lot of time, and as a result it will affect the mass rebuild. Apparently less so with all the new ARM builders, right? Is this something you're saying could be improved, or is it just something we always need to budget time for? The perl upgrade process is some what manual and there's a whole bunch of circular dependencies that cause/require a bunch of manual bootstrapping of certain packages so the perl mass rebuild is some what different to a standard all in mass rebuild. Peter The same applies for Ruby. It is definitely not just fire the rebuild and forget. During the process, there is typically need to update some packages to be compatible with latest release, some were FTBFS already before, some others need bootstrap due to circular dependencies. Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, 2013-08-23 at 04:03 -0700, Adam Williamson wrote: Just nuking moxieplayer.swf doesn't stop tinymce generating HTML that looks for it, so that's not really the way to go. But I think I found a way to patch the plugin not to try and use moxieplayer.swf and just to spit out nice clean HTML instead. I also bumped tinymce to the latest upstream release, since it hadn't been bumped since 2011 and was *ancient*. Testing of this is very welcome. I've sent the build to Rawhide and F20 for now. Random note: patching minifed javascript is a giant fucking PITA, and we can't edit the 'source' javascript for tinymce and re-minify it because Fedora doesn't have yuicompressor - https://bugzilla.redhat.com/show_bug.cgi?id=745515 . Sigh. Oh - since the patch is to the minified .js it's probably borderline unreadable. This is what the patch basically is, against editor_plugin_src.js in tinymce/jscripts/tiny_mce/plugins/media/editor_plugin_src.js , line 341: -flashPlayer = editor.getParam('flash_video_player_url', self.convertUrl(self.url + '/moxieplayer.swf')); +flashPlayer = false; just that seems to do the trick. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
Hi, On Thu, 22 Aug 2013 18:23:39 -0600 Chris Murphy li...@colorremedies.com wrote: snip I'd back no release name for 20 with 8 points and 0 for everything else, if it's an option, and in particular if the marketing includes to the effect of: Fedora 20 is nameless in honor of Seth Vidal who hated release names with the white hot passion of 10,000 supernovas. +1000 Cheers, Tomas -- Tomas Radej tra...@redhat.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
Thanks for tackling this! On Fri, Aug 23, 2013 at 4:03 AM, Adam Williamson awill...@redhat.com wrote: So, tinymce has a 'media' plugin which lets you embed media in HTML you're editing with it. If it thinks the media might need playing with Flash, it'll generate HTML that tries to use a Flash player - moxieplayer.swf - to play it (sometimes as a fallback from HTML5). Just nuking moxieplayer.swf doesn't stop tinymce generating HTML that looks for it, so that's not really the way to go. But I think I found a way to patch the plugin not to try and use moxieplayer.swf and just to spit out nice clean HTML instead. I also bumped tinymce to the latest upstream release, since it hadn't been bumped since 2011 and was *ancient*. Testing of this is very welcome. I've sent the build to Rawhide and F20 for now. roundcubemail is on this list because it bundles tinymce, basically. I think it should be trivial to replace its bundled tinymce with the system-wide one. I'm going to test installing the updated and de-Flashed tinymce along with a roundcubemail build patched to use a system-wide tinymce on my own server and check that it works okay that way. If it does, I'll submit that combination to all Fedora releases. I suspect many other packages on the list may be there because they're bundling tinymce. In most cases, unbundling it ought to be trivial; it seems like the 3.x series of tinymce maintained compatibility well, so I think it shouldn't be a problem to use system-wide tinymce. But I'll look into it some more tomorrow. askbot is the only package right now using t. he systemwide tinymce. I'm assuming ask.fp.o runs on EL, but I'm not sure. Any infra folks reading this, would you be interested in checking ask.fp.o behaves sensibly with de-Flashed tinymce 3.5.8? I don't think the Flash issue should matter at all because it looks like askbot customizes the tinymce editor widget somewhat and doesn't actually expose the media plugin _at all_. I don't see why it wouldn't work with tinymce 3.5.8 - in fact it ought to work better - but we should probably check. Random note: patching minifed javascript is a giant fucking PITA, and we can't edit the 'source' javascript for tinymce and re-minify it because Fedora doesn't have yuicompressor - https://bugzilla.redhat.com/show_bug.cgi?id=745515 . Sigh. Ideally, we would port dependent applications to TinyMCE 4. It looks like 3.x is ancient; it hasn't had a commit in over a year. Version 4 uses a nodejs- based build system so we can do minification properly according to the shiny new guidelines. The differences don't look too crazy: http://www.tinymce.com/wiki.php/Tutorial:Migration_guide_from_3.x I can package up what's needed (including a new-world compliant tinymce package) if someone can verify that porting is possible. (Or I'll try and find time to look myself sometime soon.) BTW, this is why we want to start requiring minification in %build, so we'll be able to patch JS sanely once again. ;-) -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
On Thu, Aug 22, 2013 at 8:39 PM, Dan Mashal dan.mas...@gmail.com wrote: It will be dedicated in the release announcement. Perhaps someone might add something to the download page on the website as well. Hi Josh, Thanks for replying. I personally LOVE release names. However, I feel that we should forego it this one release. What is the point of the board of the community decides everything? To ensure that the community gets to decided anything for starters. That's a much broader topic though, and I'll stick to the release name stuff in my reply. We all know that there needs to be a tough decision made by the board, and it's not release names vs no release names. For me it's about doing what Seth would have wanted, whether he was close to us or not, whether he he touched us or knew us or cared about personally. Please seriously consider the following and have a BOARD vote on it: We consider it. It was decided against. The names in the vote are the possibilities going forward. I personally would love to have no release names (ever), but we're beyond that point now. I do not foresee further emails changing that, so while feedback is welcome for future releases I don't want people to get the expectation that it will change for F20. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
On Thu, Aug 22, 2013 at 10:29 PM, Paul Wouters pwout...@redhat.com wrote: On Thu, 22 Aug 2013, Chris Murphy wrote: On Aug 22, 2013, at 6:12 PM, Josh Boyer jwbo...@fedoraproject.org wrote: I'm not necessarily disagreeing, but there are essentially two camps right now. Those that don't care about release names one bit (like me), and those that do. If those that do care want better names, they'll need to work harder at creating meaningful suggestions. OK I'm third camp: peanut gallery. I don't really care about release names, I'm happier to see them go away, but insofar as we have them, I'm playing along by a.) voting, b.) complaining. [1] It would be good if the next vote would allow none as an option. I could not vote 'none' on the last election. And I think it is important to track the percentage of people who want to kill the meaningless names. That's a good suggestion for future votes. At the moment, the best you can do is cast 0 votes for all choices. That won't really change the outcome, but at least votes will be recorded. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, 2013-08-23 at 04:43 -0700, T.C. Hollingsworth wrote: Thanks for tackling this! On Fri, Aug 23, 2013 at 4:03 AM, Adam Williamson awill...@redhat.com wrote: So, tinymce has a 'media' plugin which lets you embed media in HTML you're editing with it. If it thinks the media might need playing with Flash, it'll generate HTML that tries to use a Flash player - moxieplayer.swf - to play it (sometimes as a fallback from HTML5). Just nuking moxieplayer.swf doesn't stop tinymce generating HTML that looks for it, so that's not really the way to go. But I think I found a way to patch the plugin not to try and use moxieplayer.swf and just to spit out nice clean HTML instead. I also bumped tinymce to the latest upstream release, since it hadn't been bumped since 2011 and was *ancient*. Testing of this is very welcome. I've sent the build to Rawhide and F20 for now. roundcubemail is on this list because it bundles tinymce, basically. I think it should be trivial to replace its bundled tinymce with the system-wide one. I'm going to test installing the updated and de-Flashed tinymce along with a roundcubemail build patched to use a system-wide tinymce on my own server and check that it works okay that way. If it does, I'll submit that combination to all Fedora releases. I suspect many other packages on the list may be there because they're bundling tinymce. In most cases, unbundling it ought to be trivial; it seems like the 3.x series of tinymce maintained compatibility well, so I think it shouldn't be a problem to use system-wide tinymce. But I'll look into it some more tomorrow. askbot is the only package right now using t. he systemwide tinymce. I'm assuming ask.fp.o runs on EL, but I'm not sure. Any infra folks reading this, would you be interested in checking ask.fp.o behaves sensibly with de-Flashed tinymce 3.5.8? I don't think the Flash issue should matter at all because it looks like askbot customizes the tinymce editor widget somewhat and doesn't actually expose the media plugin _at all_. I don't see why it wouldn't work with tinymce 3.5.8 - in fact it ought to work better - but we should probably check. Random note: patching minifed javascript is a giant fucking PITA, and we can't edit the 'source' javascript for tinymce and re-minify it because Fedora doesn't have yuicompressor - https://bugzilla.redhat.com/show_bug.cgi?id=745515 . Sigh. Ideally, we would port dependent applications to TinyMCE 4. It looks like 3.x is ancient; it hasn't had a commit in over a year. Version 4 uses a nodejs- based build system so we can do minification properly according to the shiny new guidelines. The differences don't look too crazy: http://www.tinymce.com/wiki.php/Tutorial:Migration_guide_from_3.x I can package up what's needed (including a new-world compliant tinymce package) if someone can verify that porting is possible. (Or I'll try and find time to look myself sometime soon.) All the upstream projects I found seemed to consider jumping to tinymce 4 a rather large move. Debian packages 3 and 4 as separate packages. I rather think we should do the same rather than just pretend they're the same thing and we'll be easily able to migrate things from one to the other. Or, at least let's get a tinymce 3.5.8 built and all things that bundle 3 un-bundled before we start worrying about 4. :) So, after some teeth gnashing, I've confirmed roundcube can indeed be relatively easily unbundled to use a system 3.5.8 package. It needs the spellchecker plugin which is a separate package in Fedora, which tripped me up for a while. However, to do this, I run into the fucking convert-a-directory-to-a-symlink old chestnut, and RPM/yum just isn't having it. Following the breadcrumbs all over this list and Bugzilla I came up with this %pretrans: %pretrans -p lua -- changed dir to symlink in 0.9.3-1, workaround RPM issues path = %{roundcubedir}/program/js/tiny_mce if posix.readlink(path) then os.remove(path) end But yum/rpm just won't wear it. 'yum update mynewroundcubepackage.rpm' fails with a file conflict just like it does if there's no %pretrans at all. I was able to test my unbundling simply by manually removing and reinstalling the roundcube package, but I can't push it out anywhere unless I can get a %pretrans which yum/rpm will be happy with. Anyone? https://bugzilla.redhat.com/show_bug.cgi?id=975909 may be involved, I guess. roundcubemail ships tinymce as /usr/share/roundcubemail/program/js/tiny_mce and hooks into it rather untidily; it seems rather cleaner to just do 'ln -s /usr/share/tinymce/jscripts/tiny_mce %{buildroot}%{roundcubedir}/program/js/tiny_mce' in the spec rather than write a messy patch for roundcube to change where it looks for tinymce, which would probably need constant updating. BTW, this is why we want to start requiring minification in %build, so we'll be able to patch JS sanely once again. ;-) I am
Re: Bundled Flash
On Fri, 2013-08-23 at 05:40 -0700, Adam Williamson wrote: However, to do this, I run into the fucking convert-a-directory-to-a-symlink old chestnut, and RPM/yum just isn't having it. Following the breadcrumbs all over this list and Bugzilla I came up with this %pretrans: %pretrans -p lua -- changed dir to symlink in 0.9.3-1, workaround RPM issues path = %{roundcubedir}/program/js/tiny_mce if posix.readlink(path) then os.remove(path) end But yum/rpm just won't wear it. 'yum update mynewroundcubepackage.rpm' fails with a file conflict just like it does if there's no %pretrans at all. I was able to test my unbundling simply by manually removing and reinstalling the roundcube package, but I can't push it out anywhere unless I can get a %pretrans which yum/rpm will be happy with. Anyone? https://bugzilla.redhat.com/show_bug.cgi?id=975909 may be involved, I guess. roundcubemail ships tinymce as /usr/share/roundcubemail/program/js/tiny_mce and hooks into it rather untidily; it seems rather cleaner to just do 'ln -s /usr/share/tinymce/jscripts/tiny_mce %{buildroot}%{roundcubedir}/program/js/tiny_mce' in the spec rather than write a messy patch for roundcube to change where it looks for tinymce, which would probably need constant updating. Just to cover my ass, this kind of symlinking is explicitly allowed by the draft new JavaScript policy: Regardless, web applications may want to make subdirectories of %{_jsdir} available under their own directory via aliases or symlinks for compatibility purposes or to eliminate needless deviation from upstream. https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/JavaScript so I reckon it's fine to do it, so damnit yum, let me. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F-20 Branched report: 20130823 changes
What about this? perl(Digest::SHA) I've seen many broken ones because of it now. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Heads up: GNOME 3.9.90 in F20 / rawhide
Hi, Just a quick heads up that GNOME 3.9.90 builds have landed in today's Branched (F20) and Rawhide. This is the first Beta release towards GNOME 3.10 and marks the beginning of the UI and API freezes. Next up is GNOME 3.9.91 on September 4th. I am personally running F20 here with the latest GNOME and would encourage anyone interested to try it out; seems to be working fairly well. -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
On Fri, 23 Aug 2013 13:39:40 +0200, Tomas Radej wrote: Hi, On Thu, 22 Aug 2013 18:23:39 -0600 Chris Murphy wrote: snip I'd back no release name for 20 with 8 points and 0 for everything else, if it's an option, and in particular if the marketing includes to the effect of: Fedora 20 is nameless in honor of Seth Vidal who hated release names with the white hot passion of 10,000 supernovas. +1000 I don't think it's been hatred (or passionate fighting, or else he would have tried to reach a decision at the FPB level), but indeed, he has been one of those who think the release name process is a waste of time and of no use. https://lists.fedoraproject.org/pipermail/advisory-board/2012-March/011419.html How many people are involved in suggesting release names, reviewing them, checking them (Red Hat Legal)? How many people enjoy doing all that? There aren't many voters. It has come up many years ago already, too, that hardly anybody refers to a Fedora distribution release using its codename instead of the release numbers and/or shortnames: Fedora 19, F19, F-19, f19. It doesn't get more accurate. No point releases as with Red Hat Linux. -- Well, a few still call it Fedora Core. ;-) Fedora release 20 (Null) - Linux 3.11.0-0.rc6.git1.2.fc20.x86_64 loadavg: 0.29 0.14 0.13 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Changes to make MySQL vs. MariaDB less confusing
On Fri, Aug 23, 2013 at 3:40 AM, James Hogarth james.hoga...@gmail.comwrote: Frankly I'm still of the opinion the Oracle distribution of the MySQL based server should be dropped entirely... If Oracle want 'community-mysql' to exist for Fedora and want to maintain it themselves then they can set up their own repositories on their own infrastructure and these compatibilities issues with Fedora can be removed entirely as a result. If someone (Oracle-employee or not) is willing to go through the trouble of learning the packaging guidelines, submitting and working through a review, getting sponsored, and getting a package into the distribution, what basis does anyone have to block that effort? We have packaging guidelines for inter-package conflicts, and those issues must be resolved as part of the package review anyway. The idea that we can single out an organization or a software package and say You can't put this in Fedora, in spite of the fact that the package in question can made to abide by all of Fedora's guidelines and policies (albeit with a little bit of work and collaboration,) seems contradict the Friends and Features foundations. If what they're doing becomes actively harmful to the distribution, then we can take it up with FESCo. Otherwise, I think we have to treat them like any other community member regardless of our feelings about their employer. Rich -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
solib change: libmng 2.0.2 coming to rawhide Monday!
Per https://bugzilla.redhat.com/show_bug.cgi?id=997816 I will be updating libmng in rawhide Monday. My repoquery indicated the following consumers: Rebuilt fine with libmng 2.0.2: avahi DevIL ETL freeimage gcin gimp PyQt qt qt3 scim-bridge synfig FTBFS with either libmng 1.0.10 or libmng 2.0.2: directfb Relies on directfb being rebuilt successfully first: xine-lib Retired: qcad If anyone has any issues, please comment in the BZ. I've posted an fc20 SRPM if you want to start looking at this prior to it hitting rawhide: http://fedorapeople.org/~limb/libmng-2.0.2-1.fc20.src.rpm Thanks! -J -- 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 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: solib change: libmng 2.0.2 coming to rawhide Monday!
On Fri, Aug 23, 2013 at 8:10 AM, Jon Ciesla limburg...@gmail.com wrote: Per https://bugzilla.redhat.com/show_bug.cgi?id=997816 I will be updating libmng in rawhide Monday. My repoquery indicated the following consumers: Rebuilt fine with libmng 2.0.2: avahi DevIL ETL freeimage gcin gimp PyQt qt qt3 scim-bridge synfig Additionally, I'll handle the rebuilds for these unless I hear otherwise from owners first. -J FTBFS with either libmng 1.0.10 or libmng 2.0.2: directfb Relies on directfb being rebuilt successfully first: xine-lib Retired: qcad If anyone has any issues, please comment in the BZ. I've posted an fc20 SRPM if you want to start looking at this prior to it hitting rawhide: http://fedorapeople.org/~limb/libmng-2.0.2-1.fc20.src.rpm Thanks! -J -- http://cecinestpasunefromage.wordpress.com/ in your fear, seek only peace in your fear, seek only love -d. bowie -- 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 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, Aug 23, 2013 at 5:40 AM, Adam Williamson awill...@redhat.com wrote: All the upstream projects I found seemed to consider jumping to tinymce 4 a rather large move. Debian packages 3 and 4 as separate packages. I rather think we should do the same rather than just pretend they're the same thing and we'll be easily able to migrate things from one to the other. I should have known it couldn't be that easy. :-/ Or, at least let's get a tinymce 3.5.8 built and all things that bundle 3 un-bundled before we start worrying about 4. :) So, after some teeth gnashing, I've confirmed roundcube can indeed be relatively easily unbundled to use a system 3.5.8 package. It needs the spellchecker plugin which is a separate package in Fedora, which tripped me up for a while. However, to do this, I run into the fucking convert-a-directory-to-a-symlink old chestnut, and RPM/yum just isn't having it. Following the breadcrumbs all over this list and Bugzilla I came up with this %pretrans: %pretrans -p lua -- changed dir to symlink in 0.9.3-1, workaround RPM issues path = %{roundcubedir}/program/js/tiny_mce if posix.readlink(path) then os.remove(path) end But yum/rpm just won't wear it. 'yum update mynewroundcubepackage.rpm' fails with a file conflict just like it does if there's no %pretrans at all. I was able to test my unbundling simply by manually removing and reinstalling the roundcube package, but I can't push it out anywhere unless I can get a %pretrans which yum/rpm will be happy with. Anyone? https://bugzilla.redhat.com/show_bug.cgi?id=975909 may be involved, I guess. I believe that's the code for the symlink-directory direction. The state of the art for directory-symlink seems to be: https://bugs.launchpad.net/rpm/+bug/633636/comments/3 as linked to in bug: https://bugzilla.redhat.com/show_bug.cgi?id=447156 And it's god awful. How much beer do I have to buy Panu to make this work properly? You could just say screw anaconda installs and just use `rm -rf`. Though I tried that once, in *EPEL* even, and it only took a week for someone to complain. :-( roundcubemail ships tinymce as /usr/share/roundcubemail/program/js/tiny_mce and hooks into it rather untidily; it seems rather cleaner to just do 'ln -s /usr/share/tinymce/jscripts/tiny_mce %{buildroot}%{roundcubedir}/program/js/tiny_mce' in the spec rather than write a messy patch for roundcube to change where it looks for tinymce, which would probably need constant updating. Any chance you could just use an Alias in the apache config? Then you can just delete the directory and not muck around with making yum happy. -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F-20 Branched report: 20130823 changes
On Fri, Aug 23, 2013 at 8:46 AM, Christopher Meng cicku...@gmail.com wrote: What about this? perl(Digest::SHA) I've seen many broken ones because of it now. I'd like to know, too. The perl-Digest-SHA package is still in the fedpkg sources, and doesn't say it's .dead. Is it just a bogus transient error? Regards, -- Konstantin Ryabitsev LinuxFoundation.org Montréal, Québec -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, Aug 23, 2013 at 5:44 AM, Adam Williamson awill...@redhat.com wrote: Just to cover my ass, this kind of symlinking is explicitly allowed by the draft new JavaScript policy: Regardless, web applications may want to make subdirectories of %{_jsdir} available under their own directory via aliases or symlinks for compatibility purposes or to eliminate needless deviation from upstream. https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/JavaScript so I reckon it's fine to do it, so damnit yum, let me. Ugh, this bug never crossed my mind when I wrote that. I'll definitely make sure that section grows a big red box warning about this. -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
File POE-1.356.tar.gz uploaded to lookaside cache by psabata
A file has been added to the lookaside cache for perl-POE: 287f75fb2ae59fb9de16abfdca01baae POE-1.356.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-POE] 1.356 bump
commit 13e0611fec5e66f884a719bdbc4dc5b2474cd834 Author: Petr Šabata con...@redhat.com Date: Fri Aug 23 15:53:02 2013 +0200 1.356 bump .gitignore|1 + perl-POE.spec | 37 - sources |2 +- 3 files changed, 30 insertions(+), 10 deletions(-) --- diff --git a/.gitignore b/.gitignore index 88f2294..997ad5a 100644 --- a/.gitignore +++ b/.gitignore @@ -5,3 +5,4 @@ POE-1.289.tar.gz /POE-1.352.tar.gz /POE-1.353.tar.gz /POE-1.354.tar.gz +/POE-1.356.tar.gz diff --git a/perl-POE.spec b/perl-POE.spec index d0b0ab0..43f3987 100644 --- a/perl-POE.spec +++ b/perl-POE.spec @@ -1,6 +1,6 @@ Name: perl-POE -Version: 1.354 -Release: 9%{?dist} +Version: 1.356 +Release: 1%{?dist} Summary: POE - portable multitasking and networking framework for Perl Group: Development/Libraries @@ -8,37 +8,53 @@ License: GPL+ or Artistic URL: http://search.cpan.org/dist/POE/ Source0: http://search.cpan.org/CPAN/authors/id/R/RC/RCAPUTO/POE-%{version}.tar.gz BuildArch: noarch -Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version)) +Requires: perl(:MODULE_COMPAT_%(eval $(perl -V:version); echo $version)) -BuildRequires: perl(ExtUtils::MakeMaker) +BuildRequires: perl +BuildRequires: perl(base) +BuildRequires: perl(bytes) +BuildRequires: perl(Carp) BuildRequires: perl(Compress::Zlib) = 1.33 +BuildRequires: perl(Config) +BuildRequires: perl(constant) BuildRequires: perl(Curses) = 1.08 BuildRequires: perl(Data::Dumper) BuildRequires: perl(Errno) = 1.09 BuildRequires: perl(Exporter) +BuildRequires: perl(ExtUtils::MakeMaker) +BuildRequires: perl(Fcntl) BuildRequires: perl(File::Spec) = 0.87 +BuildRequires: perl(FileHandle) +BuildRequires: perl(HTTP::Date) +BuildRequires: perl(HTTP::Request) +BuildRequires: perl(HTTP::Response) +BuildRequires: perl(HTTP::Status) BuildRequires: perl(IO) = 1.24 BuildRequires: perl(IO::Handle) = 1.27 +BuildRequires: perl(IO::Pipely) BuildRequires: perl(IO::Poll) = 0.01 BuildRequires: perl(IO::Pty) = 1.02 BuildRequires: perl(IO::Socket) BuildRequires: perl(IO::Tty) = 1.08 -BuildRequires: perl(HTTP::Date) -BuildRequires: perl(HTTP::Request) -BuildRequires: perl(HTTP::Response) -BuildRequires: perl(HTTP::Status) # POE::Test::Loops unsurprisingly requires POE # ...and it's not in EPEL at the moment %if 0%{!?perl_bootstrap:1} ! ( 0%{?rhel} ) -BuildRequires: perl(POE::Test::Loops) = 1.351 +BuildRequires: perl(POE::Test::Loops) = 1.352 %endif +BuildRequires: perl(POSIX) = 1.02 +BuildRequires: perl(Scalar::Util) BuildRequires: perl(Socket) = 1.7 BuildRequires: perl(Socket6) = 0.14 BuildRequires: perl(Storable) = 2.16 +BuildRequires: perl(strict) +BuildRequires: perl(Symbol) +BuildRequires: perl(Sys::Hostname) BuildRequires: perl(Term::Cap) = 1.09 BuildRequires: perl(Term::ReadKey) = 2.21 BuildRequires: perl(Time::HiRes) = 1.59 BuildRequires: perl(URI) = 1.30 +BuildRequires: perl(vars) +BuildRequires: perl(warnings) # test BuildRequires: perl(Test::Harness) = 2.26 BuildRequires: perl(Test::More) @@ -120,6 +136,9 @@ make test %{_mandir}/man3/*.3* %changelog +* Wed Aug 21 2013 Petr Šabata con...@redhat.com - 1.356-1 +- 1.356 bump + * Wed Aug 14 2013 Jitka Plesnikova jples...@redhat.com - 1.354-9 - Perl 5.18 re-rebuild of bootstrapped packages diff --git a/sources b/sources index 4358a8f..5bfd68e 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -928482218e29aa4c27f281db9bdc1ac4 POE-1.354.tar.gz +287f75fb2ae59fb9de16abfdca01baae POE-1.356.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: F20 release name election?
On Fri, Aug 23, 2013 at 8:04 AM, Michael Schwendt mschwe...@gmail.com wrote: I don't think it's been hatred (or passionate fighting, or else he would have tried to reach a decision at the FPB level), but indeed, he has been one of those who think the release name process is a waste of time and of no use. https://lists.fedoraproject.org/pipermail/advisory-board/2012-March/011419.html That was a very practical solution to what appeared to be another layer of hassle around release names. In reality so far at least that hassle hasn't materialized. How many people are involved in suggesting release names, reviewing them, checking them (Red Hat Legal)? How many people enjoy doing all that? There aren't many voters. Part of the deal with participating in a community is that sometimes you do things you would not choose to do to enable others to do what they do choose to do. Red Hat legal can kill release names at any time by simply saying they no longer are willing to vet the names. The Fedora Board can do the same. Neither has so why do we have to keep going over this? The Board spends maybe 3-4 hours on this twice a year. If that is too much to enable part of the community to enjoy participating in the tradition of release naming then propose the Board simply stop doing it. It has come up many years ago already, too, that hardly anybody refers to a Fedora distribution release using its codename instead of the release numbers and/or shortnames: Fedora 19, F19, F-19, f19. It doesn't get more accurate. No point releases as with Red Hat Linux. And there really isn't anything accomplished by bringing up the same old arguments again now except to spoil the fun those who enjoy this might have. At least I can't see any reason. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
How to check EPEL dependencies from Fedora?
I would like to get fltk in EPEL updated to 1.3.X as fldigi is dropping backward compatibility with fltk 1.1.X. In order to do that I was trying to figure out the magnatude of the change, but I don't seem to have a good way of checking which other EPEL packages will need to be rebuilt. I tried using repoquery from a mock chroot of EPEL 6, but as I understand it, running yum/rpm tools really are not designed to work from inside mock. At least if gives a lot of errors about the rpm database, but it did produce output... # repoquery --whatrequires libfltk.so.1.1 rpmdb: /var/lib/rpm/Name: unexpected file type or format error: cannot open Name index using db3 - Invalid argument (22) rpmdb: /var/lib/rpm/Providename: unexpected file type or format error: cannot open Providename index using db3 - Invalid argument (22) Pixie-0:2.2.6-3.el6.i686 aqsis-libs-0:1.6.0-3.el6.i686 fltk-devel-0:1.1.10-1.el6.i686 octave-6:3.4.3-1.el6.i686 Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F-20 Branched report: 20130823 changes
On 08/23/2013 03:42 PM, Konstantin Ryabitsev wrote: On Fri, Aug 23, 2013 at 8:46 AM, Christopher Meng cicku...@gmail.com wrote: What about this? perl(Digest::SHA) I've seen many broken ones because of it now. I'd like to know, too. The perl-Digest-SHA package is still in the fedpkg sources, and doesn't say it's .dead. Is it just a bogus transient error? Looks like it got blocked in koji yesterday, perhaps by a mistake? $ koji list-pkgs --show-blocked --tag f20 --package perl-Digest-SHA Package Tag Extra Arches Owner --- --- --- perl-Digest-SHA f18 ppisar [BLOCKED] $ koji list-history --tag=f18 --package perl-Digest-SHA snip, lots of builds happening Thu Aug 22 17:12:19 2013 package list entry for perl-Digest-SHA in f18 updated by ausil blocked: False - True -- Hope this helps, Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Changes to make MySQL vs. MariaDB less confusing
On 23 August 2013 14:06, Rich Mattes richmat...@gmail.com wrote: On Fri, Aug 23, 2013 at 3:40 AM, James Hogarth james.hoga...@gmail.comwrote: Frankly I'm still of the opinion the Oracle distribution of the MySQL based server should be dropped entirely... If Oracle want 'community-mysql' to exist for Fedora and want to maintain it themselves then they can set up their own repositories on their own infrastructure and these compatibilities issues with Fedora can be removed entirely as a result. If someone (Oracle-employee or not) is willing to go through the trouble of learning the packaging guidelines, submitting and working through a review, getting sponsored, and getting a package into the distribution, what basis does anyone have to block that effort? We have packaging guidelines for inter-package conflicts, and those issues must be resolved as part of the package review anyway. The idea that we can single out an organization or a software package and say You can't put this in Fedora, in spite of the fact that the package in question can made to abide by all of Fedora's guidelines and policies (albeit with a little bit of work and collaboration,) seems contradict the Friends and Features foundations. If what they're doing becomes actively harmful to the distribution, then we can take it up with FESCo. Otherwise, I think we have to treat them like any other community member regardless of our feelings about their employer. I agree overall which is why I suggest the official orphaning of community-mysql ... it only seems like it will be a pain to keep both that and MariaDB for the existing maintainers. If another party (whether it be corporate sponsorship via Oracle or a random individual) wants to pick up the pain of community-mysql packaging adhering to the Fedora Packaging Guidelines then good for them but the reasons for switching to MariaDB in the beginning during the F19 release was down to lack of transparency (eg test cases and security notices) from upstream... From the first date Honza announced the intended feature we heard a lot of promises from Oracle about how they would act with stewardship but words are cheap - so far in all this time there's been little of any actual substance. After many weeks (two or three months maybe?) of waiting Bjorn announced himself as the maintainer of MySQL without apparently any communication with the existing maintainers first - at least Honza stated I'm really glad to see some real action from your part finally http://mm3test.fedoraproject.org/hyperkitty/list/de...@mm3test.fedoraproject.org/thread/LWB37ALUAM5PLXGTQLVQBRAHPQPXLWKE/ If they do manage to comply with FPG and have a proper RPM and act the part of Friends (as the reminder had to go last time) then fantastic... but there really has been little if any evidence of that so far - all the way since the Sun purchase in fact. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F-20 Branched report: 20130823 changes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 23 Aug 2013 16:11:14 +0200 Kalev Lember kalevlem...@gmail.com wrote: On 08/23/2013 03:42 PM, Konstantin Ryabitsev wrote: On Fri, Aug 23, 2013 at 8:46 AM, Christopher Meng cicku...@gmail.com wrote: What about this? perl(Digest::SHA) I've seen many broken ones because of it now. I'd like to know, too. The perl-Digest-SHA package is still in the fedpkg sources, and doesn't say it's .dead. Is it just a bogus transient error? Looks like it got blocked in koji yesterday, perhaps by a mistake? $ koji list-pkgs --show-blocked --tag f20 --package perl-Digest-SHA Package Tag Extra Arches Owner --- --- --- perl-Digest-SHA f18 ppisar [BLOCKED] $ koji list-history --tag=f18 --package perl-Digest-SHA snip, lots of builds happening Thu Aug 22 17:12:19 2013 package list entry for perl-Digest-SHA in f18 updated by ausil blocked: False - True Seems there was a bug in my script that synced the blocked packages via inheritance from f17 to f18. a fall out from cutting off inheritance completely. Its been unblocked now Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlIXdAoACgkQkSxm47BaWfeUBgCfb3CkVnFe2rvgrfxhF/4+8Ccd rRcAmwZ2ZFN7fzVKbgjjRJf/PC9TMhjC =VIZD -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: How to check EPEL dependencies from Fedora?
I'm thinking this produce a bit more of a complete list... # repoquery --resolve --whatrequires fltk rpmdb: /var/lib/rpm/Name: unexpected file type or format error: cannot open Name index using db3 - Invalid argument (22) rpmdb: /var/lib/rpm/Providename: unexpected file type or format error: cannot open Providename index using db3 - Invalid argument (22) fltk-0:1.1.10-1.el6.x86_64 fltk-0:1.1.10-1.el6.i686 Pixie-0:2.2.6-3.el6.i686 Pixie-0:2.2.6-3.el6.x86_64 alsamixergui-0:0.9.0-0.9.rc2.el6.x86_64 aqsis-0:1.6.0-3.el6.x86_64 aqsis-libs-0:1.6.0-3.el6.i686 aqsis-libs-0:1.6.0-3.el6.x86_64 fltk-devel-0:1.1.10-1.el6.i686 fltk-devel-0:1.1.10-1.el6.x86_64 fltk-fluid-0:1.1.10-1.el6.x86_64 htmldoc-0:1.8.27-13.el6.x86_64 mup-0:6.1-4.el6.x86_64 octave-6:3.4.3-1.el6.i686 octave-6:3.4.3-1.el6.x86_64 rakarrack-0:0.5.8-2.el6.x86_64 Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: How to check EPEL dependencies from Fedora?
On Fri, Aug 23, 2013 at 09:10:44AM -0500, Richard Shaw wrote: I tried using repoquery from a mock chroot of EPEL 6, but as I understand it, running yum/rpm tools really are not designed to work from inside mock. At least if gives a lot of errors about the rpm database, but it did produce output... If you're maintaining EPEL packages, might I suggest having a VM with RHEL or CentOS handy? -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 989982] perl-SOAP-Lite-1.06 is available
https://bugzilla.redhat.com/show_bug.cgi?id=989982 Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org changed: What|Removed |Added Summary|perl-SOAP-Lite-1.05 is |perl-SOAP-Lite-1.06 is |available |available --- Comment #4 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Latest upstream release: 1.06 Current version/release in Fedora Rawhide: 0.716-3.fc20 URL: http://search.cpan.org/dist/SOAP-Lite/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=F2oyWt6RX2a=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1000525] New: perl-UUID-Tiny-1.04 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1000525 Bug ID: 1000525 Summary: perl-UUID-Tiny-1.04 is available Product: Fedora Version: rawhide Component: perl-UUID-Tiny Keywords: FutureFeature, Triaged Assignee: mhron...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mhron...@redhat.com, perl-de...@lists.fedoraproject.org Latest upstream release: 1.04 Current version/release in Fedora Rawhide: 1.03-5.fc20 URL: http://search.cpan.org/dist/UUID-Tiny/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Wkv2yjmIwwa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Changes to make MySQL vs. MariaDB less confusing
On 22/08 09.27, Bjorn Munch wrote: I will get back with more details later. I have now made new packages available and updated #958131. - Bjorn -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
EPEL need help in installing dom4j on rhel 6.4
Hi, I am trying to install dom4j rpm in rhel 6.4. As it is not available in rhel,i have added epel repo and tried to install dom4j ,but no luck. Here is my epel.repo [epel] name=Extra Packages for Enterprise Linux 6 - $basearch #baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch mirrorlist= https://mirrors.fedoraproject.org/metalink?repo=epel-6arch=$basearch failovermethod=priority enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 [epel-debuginfo] name=Extra Packages for Enterprise Linux 6 - $basearch - Debug #baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch/debug mirrorlist= https://mirrors.fedoraproject.org/metalink?repo=epel-debug-6arch=$basearch failovermethod=priority enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 gpgcheck=1 [epel-source] name=Extra Packages for Enterprise Linux 6 - $basearch - Source #baseurl=http://download.fedoraproject.org/pub/epel/6/SRPMS mirrorlist= https://mirrors.fedoraproject.org/metalink?repo=epel-source-6arch=$basearch failovermethod=priority enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 gpgcheck=1 Please help me in installing this package. Thanks Upendra ___ epel-devel mailing list epel-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: F21 schedule: what would you do with more time?
On Fri, Aug 23, 2013 at 12:32 PM, Ralf Corsepius rc040...@freenet.de wrote: On 08/23/2013 10:39 AM, Peter Robinson wrote: * much longer build.log holding time for FTBFS. I think this comes down to the amount of storage it takes and the amount we have available. Is that really that much? And if it is, just compress them. 50-60 MB build logs compress to 1-2 MB with gzip (checked with webkitgtk and libreoffice). gzipped logs can be served so that they're directly viewable in browsers so there shouldn't be any inconvenience, on the contrary actually due to smaller download size, for example like this with Apache: Files *.log.gz ForceType text/plain AddEncoding x-gzip .gz /Files -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Changes to make MySQL vs. MariaDB less confusing
- james.hoga...@gmail.com wrote: From the first date Honza announced the intended feature we heard a lot of promises from Oracle about how they would act with stewardship but words are cheap - so far in all this time there's been little of any actual substance. I get the feeling the discussion is about maintainership, but taking over maintainership has not been an issue. Honza is the maintainer. He's doing a good job, and last I heard he intends to continue doing so for a while. What we/I did for F19 was to help solve the problem at hand: Find a way to have both MySQL and MariaDB in Fedora. And it worked. Together we found a solution. While Honza is still the maintainer, Bjørn has stepped up to help with packaging. He has made the 5.6 package that is currently in review, and Honza is reviewing it. As part of this effort, we've also had engineers in the background fixing bugs to reduce the number of patches applied during packaging. If you want us to do more, please say so. We're happy to help out. Regards, Norvald H. Ryeng -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: How to check EPEL dependencies from Fedora?
On Fri, Aug 23, 2013 at 5:10 PM, Richard Shaw hobbes1...@gmail.com wrote: I tried using repoquery from a mock chroot of EPEL 6, but as I understand it, running yum/rpm tools really are not designed to work from inside mock. repoquery from yum-utils = 1.1.31-17.fc19 has --installroot which can be used from outside the mock chroot like $ repoquery --installroot /var/lib/mock/epel-6-x86_64/root --whatrequires fltk -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
USB-based Gnome 3 lockups
Hi all, When I got this laptop (Thinkpad W530), I ran F17. It was always perfectly stable. When I installed F18, it started to (seemingly) randomly lock up Gnome 3. I could never see much in syslog of use. I knew it was just gnome because I could still ctrl+alt+fX to other terminals. If I restarted dbus, gnome restarted and most of the time I could log back in. I thought it might have been my bluetooth mouse, but it still crashed when bt/wan were disabled (airport mode mechanical switch flipped). The random lock ups continued when I upgraded to Fedora 19 and I never was able to sort out why. Finally I started noticing a pattern; When I used the USB3 ports, it would crash within a few hours. I recently stopped using the USB3 ports and it's not crashed since. The USB2 ports are just fine. So how can I debug this further? Cheers digimer PS - Machine details; = lemass:/home/digimer# cat /etc/redhat-release Fedora release 19 (Schrödinger’s Cat) = = lemass:/home/digimer# uname -a Linux lemass.alteeve.ca 3.10.7-200.fc19.x86_64 #1 SMP Thu Aug 15 23:19:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux = = lemass:/home/digimer# lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 02:00.0 System peripheral: Ricoh Co Ltd MMC/SD Host Controller (rev 08) 03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 3e) = = lemass:/home/digimer# lsusb Bus 002 Device 005: ID 18d1:4ee1 Google Inc. Nexus 4 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 04f2:b2ea Chicony Electronics Co., Ltd Integrated Camera [ThinkPad] Bus 001 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 006: ID 05ac:1402 Apple, Inc. Ethernet Adapter [A1277] Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub = = lemass:/home/digimer# dmidecode # dmidecode 2.12 SMBIOS 2.7 present. 73 structures occupying 2985 bytes. Table at 0xDAE9D000. Handle 0x, DMI type 134, 16 bytes OEM-specific Type Header and Data: 86 10 00 00 00 53 54 4D 20 01 01 00 00 02 01 02 Strings: TPM INFO System Reserved Handle 0x0001, DMI type 4, 42 bytes Processor Information Socket Designation: CPU Socket - U3E1 Type: Central Processor Family: Core i7 Manufacturer: Intel(R) Corporation ID: A9 06 03 00 FF FB EB BF Signature: Type 0, Family 6, Model 58, Stepping 9 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension)
Re: F21 schedule: what would you do with more time?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 23 Aug 2013 09:33:59 +0100 Peter Robinson pbrobin...@gmail.com wrote: On Thu, Aug 22, 2013 at 4:56 PM, Mat Booth fed...@matbooth.co.uk wrote: On 22 August 2013 16:03, Matthew Miller mat...@fedoraproject.org wrote: Based on discussion at Flock, on the devel mailing list, and in the FESCo meeting, we are looking for feedback on the idea of a longer release cycle for Fedora 21 -- not (right now at least) the bigger question of the 6-month cycle overall, but just, right now, slowing down for a release to get some things in order. Specifically, both Release Engineering and QA have clear needs (and even plans for) greater automatiion, but are also incredibly busy simply doing the things they need to do _now_ to get the release out the door. So, FESCo would like to see some specifics, like If we had one week with nothing else to worry about, we could have automated generation and upload of cloud images (to pick an example I personally care about). Or with six months of overall delay, we could have continuous integration testing of a key subset of rawhide. Or we could spend a couple of weeks and automate the new package and review workflow. What Infrastructure projects would be helped by this? Web and design team, would slowing down the release focus allow time to work on, oh, say, getting the Wiki beautiful (or does it not matter)? What else? As we look at Fedora.next ideas and possibly decide to start implementation in the F21 timeframe, we will likely find _new_ things that take specific work. Let's not worry about that right now. What things we do _now_ could be improved with the investment of some effort? Here's my favourite bugbear: https://fedorahosted.org/packagedb/ticket/243 I have no idea why the package retirement process needs intervention from rel-eng.-- Mat Booth http://fedoraproject.org/get-fedora There's been discussion of adding fedpkg retire-package to fedpkg which would basically just open a dead.package file to allow you to add an entry and then remove the contents from git, block the package in koji, and retire it in the package DB. I don't think anyone has had the time to do this yet both in fedpkg and the backend although I suspect this gets a whole lot easier now with fedmsg. to block packages in koji you need to be an admin. the plan is to teach pkgdb to block packages and get it access to a cert with admin privileges, then have fedpkg handle git and talking to pkgdb, then pkgdb can handle the blocking in koji. but no one has had the time to implement it. pkgdb needs to also make sure that packages can't be retired in stable Fedora's. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlIXlEkACgkQkSxm47BaWfewMgCfZf0ZGxqxTODi4tAMH87VQ+Iu 66oAn1722phEFrtdXr9HKlyUIQjLqRxW =yHHc -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: How to check EPEL dependencies from Fedora?
On Fri, Aug 23, 2013 at 9:52 AM, Matthew Miller mat...@fedoraproject.orgwrote: On Fri, Aug 23, 2013 at 09:10:44AM -0500, Richard Shaw wrote: I tried using repoquery from a mock chroot of EPEL 6, but as I understand it, running yum/rpm tools really are not designed to work from inside mock. At least if gives a lot of errors about the rpm database, but it did produce output... If you're maintaining EPEL packages, might I suggest having a VM with RHEL or CentOS handy?'' Yup, that's the full blown way to do it :) But I'm looking for a way to do it remoted in over SSH instead of at my desk. I think the chroot method (via mock or otherwise). Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: A new depedency of existing BuildRequires causes build failure - who to blame?
On 08/21/2013 03:09 AM, Ville Skyttä wrote: On Tue, Aug 20, 2013 at 4:19 PM, Tadej Janež tadej.ja...@tadej.hicsalta.si wrote: I'll fill a bug against plplot. By the way, plplotd.pc lists quite a few things in its Libs: line -- without having a deeper look I think chances are that at least some of them should be moved to Libs.private to avoid unnecessary linkage bloat when dependent packages aren't built with ld --as-needed. If that's correct, this is something to report upstream (plplot maintainer Cc'd). Yeah, they shouldn't be there. I've removed them in plplot-5.9.9-20.svn12479.fc21, building now. Please give that a try. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: How to check EPEL dependencies from Fedora?
On Fri, Aug 23, 2013 at 10:52:47AM -0400, Matthew Miller wrote: If you're maintaining EPEL packages, might I suggest having a VM with RHEL or CentOS handy? Kevin does this already for everybody: https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
fcitx-unikey-0.2.2 license tag corrected from GPLv2+ to GPLv3+
The previous version 0.1.1 is already under GPLv3+. -robin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: How to check EPEL dependencies from Fedora?
On Fri, Aug 23, 2013 at 12:41 PM, Till Maas opensou...@till.name wrote: On Fri, Aug 23, 2013 at 10:52:47AM -0400, Matthew Miller wrote: If you're maintaining EPEL packages, might I suggest having a VM with RHEL or CentOS handy? Kevin does this already for everybody: https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers That works. Thanks! Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
grib_api license change and shared library support
grib_api 1.11.0 will be built shortly for Rawhide. Two main changes: - License changes from LGPLv3 to ASL 2.0 - grib_api now builds shared libraries. Please move to use BR grib_api-devel. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, 2013-08-23 at 06:36 -0700, T.C. Hollingsworth wrote: On Fri, Aug 23, 2013 at 5:40 AM, Adam Williamson awill...@redhat.com wrote: All the upstream projects I found seemed to consider jumping to tinymce 4 a rather large move. Debian packages 3 and 4 as separate packages. I rather think we should do the same rather than just pretend they're the same thing and we'll be easily able to migrate things from one to the other. I should have known it couldn't be that easy. :-/ Or, at least let's get a tinymce 3.5.8 built and all things that bundle 3 un-bundled before we start worrying about 4. :) So, after some teeth gnashing, I've confirmed roundcube can indeed be relatively easily unbundled to use a system 3.5.8 package. It needs the spellchecker plugin which is a separate package in Fedora, which tripped me up for a while. However, to do this, I run into the fucking convert-a-directory-to-a-symlink old chestnut, and RPM/yum just isn't having it. Following the breadcrumbs all over this list and Bugzilla I came up with this %pretrans: %pretrans -p lua -- changed dir to symlink in 0.9.3-1, workaround RPM issues path = %{roundcubedir}/program/js/tiny_mce if posix.readlink(path) then os.remove(path) end But yum/rpm just won't wear it. 'yum update mynewroundcubepackage.rpm' fails with a file conflict just like it does if there's no %pretrans at all. I was able to test my unbundling simply by manually removing and reinstalling the roundcube package, but I can't push it out anywhere unless I can get a %pretrans which yum/rpm will be happy with. Anyone? https://bugzilla.redhat.com/show_bug.cgi?id=975909 may be involved, I guess. I believe that's the code for the symlink-directory direction. The state of the art for directory-symlink seems to be: https://bugs.launchpad.net/rpm/+bug/633636/comments/3 as linked to in bug: https://bugzilla.redhat.com/show_bug.cgi?id=447156 And it's god awful. How much beer do I have to buy Panu to make this work properly? Oh, god, yes, I saw that, and assumed it was an earlier cut. You could just say screw anaconda installs and just use `rm -rf`. Though I tried that once, in *EPEL* even, and it only took a week for someone to complain. :-( I suppose we could do it that way wrapped in an 'if' statement so it only runs on updates; seems reasonable to assume bash is available for an update transaction? roundcubemail ships tinymce as /usr/share/roundcubemail/program/js/tiny_mce and hooks into it rather untidily; it seems rather cleaner to just do 'ln -s /usr/share/tinymce/jscripts/tiny_mce %{buildroot}%{roundcubedir}/program/js/tiny_mce' in the spec rather than write a messy patch for roundcube to change where it looks for tinymce, which would probably need constant updating. Any chance you could just use an Alias in the apache config? Then you can just delete the directory and not muck around with making yum happy. Doesn't seem to work. Seems like it's just ignored: if I set it and move tiny_mce/ away, no tinymce. If I leave it set but also put the tiny_mce directory in place on the filesystem (by symlink or not), tinymce works. I don't actually have any idea whether PHP is supposed to respect the Apache aliases or whether it's looking at the 'real' filesystem, but it seems to be b). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, 2013-08-23 at 11:26 -0700, Adam Williamson wrote: Any chance you could just use an Alias in the apache config? Then you can just delete the directory and not muck around with making yum happy. Doesn't seem to work. Seems like it's just ignored: if I set it and move tiny_mce/ away, no tinymce. If I leave it set but also put the tiny_mce directory in place on the filesystem (by symlink or not), tinymce works. I don't actually have any idea whether PHP is supposed to respect the Apache aliases or whether it's looking at the 'real' filesystem, but it seems to be b). Yup, SO thinks it's b): Could it be because include and require use filesystem references, and the leading / refers to the filesystem root directory. PHP doesn't refer back to the Apache alias, or treat the web server htdocs directory as root http://stackoverflow.com/questions/3683754/apache-alias-or-scriptalias-in-use-with-php-doesnt-work so using an Apache alias to 'relocate' PHP is never going to work, AIUI. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [ACTION REQUIRED] Retiring long-term FTBFS packages for Fedora 20
Hi, On Fri, Aug 23, 2013 at 11:51:15AM +0300, Ville Skyttä wrote: On Tue, Aug 20, 2013 at 12:05 AM, Till Maas opensou...@till.name wrote: smart athimm, scop Where does this information about maintainers come from? Once upon a time I (scop) was a co-maintainer for this package, but I believe I've resigned a long time ago, and packagedb doesn't show me associated with it. https://admin.fedoraproject.org/pkgdb/acls/name/smart this happened because of a bug in the script. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, 2013-08-23 at 11:26 -0700, Adam Williamson wrote: You could just say screw anaconda installs and just use `rm -rf`. Though I tried that once, in *EPEL* even, and it only took a week for someone to complain. :-( I suppose we could do it that way wrapped in an 'if' statement so it only runs on updates; seems reasonable to assume bash is available for an update transaction? Well, no, I guess not: http://lists.opensuse.org/opensuse-factory/2012-09/msg01063.html We can't have nice things. It's looking like I either need an ugly patch to RC or an ugly pile of lua in the spec. Sigh. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
EPEL Fedora 5 updates-testing report
The following Fedora EPEL 5 Security updates need testing: Age URL 488 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5630/bugzilla-3.2.10-5.el5 383 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6608/Django-1.1.4-2.el5 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11174/libzrtpcpp-3.2.1-3.el5 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11165/cacti-0.8.8b-1.el5 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11144/chrony-1.25-3.el5 3 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11276/ssmtp-2.61-21.el5 1 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11300/drupal7-theme-zen-5.4-1.el5 The following builds have been pushed to Fedora EPEL 5 updates-testing perl-Carp-Fix-1_25-1.01-2.el5 perl-Perl6-Caller-0.100-2.el5 remctl-3.6-1.el5 Details about builds: perl-Carp-Fix-1_25-1.01-2.el5 (FEDORA-EPEL-2013-11314) Smooth over incompatible changes in Carp 1.25 Update Information: This is the first Fedora/EPEL release of perl-Carp-Fix-1_25. References: [ 1 ] Bug #998410 - Review Request: perl-Carp-Fix-1_25 - Smooth over incompatible changes in Carp 1.25 https://bugzilla.redhat.com/show_bug.cgi?id=998410 perl-Perl6-Caller-0.100-2.el5 (FEDORA-EPEL-2013-11310) OO caller() interface Update Information: This is the first EPEL release of perl-Perl6-Caller. References: [ 1 ] Bug #998434 - Review Request: perl-Perl6-Caller - OO caller() interface https://bugzilla.redhat.com/show_bug.cgi?id=998434 remctl-3.6-1.el5 (FEDORA-EPEL-2013-11319) Client/server for Kerberos-authenticated command execution Update Information: Update to the latest upstream release. This update slightly modifies the way a client handles timeouts and signal interruptions. For a full list of changes, see the [upstream changelog](http://www.eyrie.org/~eagle/software/remctl/news.html). ChangeLog: * Wed Aug 21 2013 Ken Dreyer ktdre...@ktdreyer.com - 3.6-1 - Upgrade to 3.6 - Drop upstreamed EL5 gcc patch * Sun Aug 4 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org - 3.5-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild * Wed Jul 17 2013 Petr Pisar ppi...@redhat.com - 3.5-2 - Perl 5.18 rebuild ___ epel-devel mailing list epel-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL Fedora 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 488 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11175/php-symfony2-HttpFoundation-2.2.5-1.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11198/filezilla-3.7.3-1.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11194/cacti-0.8.8b-1.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11183/php-symfony2-Validator-2.2.5-1.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11187/libzrtpcpp-3.2.1-2.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11222/seamonkey-2.20-1.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11195/chrony-1.25-3.el6 7 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11179/libtommath-0.42.0-2.el6,libtomcrypt-1.17-20.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11250/Django14-1.4.6-1.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11245/python-virtualenv-1.10.1-1.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11257/drupal7-entity-1.2-1.el6 3 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11274/ssmtp-2.61-21.el6 1 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11301/drupal7-theme-zen-5.4-1.el6 1 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11291/ansible-1.2.3-2.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11311/roundcubemail-0.9.3-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing asterisk-sounds-core-1.4.24-1.el6 diskimage-builder-0.0.1-4.el6 inxi-1.9.14-2.el6 perl-Carp-Fix-1_25-1.01-3.el6 perl-Perl6-Caller-0.100-2.el6 php-PHP-CSS-Parser-5.0.8-1.el6 python-sparklines-0.9-1.el6 remctl-3.6-1.el6 roundcubemail-0.9.3-1.el6 source-highlight-3.1.7-1.el6 trac-vatar-plugin-1.9-1.el6 Details about builds: asterisk-sounds-core-1.4.24-1.el6 (FEDORA-EPEL-2013-11317) Core sounds for Asterisk Update Information: Update to 1.4.24 Fix incorrect summary on Russian subpackage Add Italian sounds ChangeLog: * Wed Aug 21 2013 Jeffrey Ollie j...@ocjtech.us - 1.4.24-1 - Add Italian (it) sounds - Fix BZ999376 fix summary for asterisk-sounds-core-ru * Sat Aug 3 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org - 1.4.23-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild References: [ 1 ] Bug #999376 - Bad name of field Summary for package asterisk-sounds-core-ru https://bugzilla.redhat.com/show_bug.cgi?id=999376 diskimage-builder-0.0.1-4.el6 (FEDORA-EPEL-2013-11312) Image building tools for OpenStack Update Information: New diskimage-builder package References: [ 1 ] Bug #990279 - Review Request: diskimage-builder - Image building tools for OpenStack https://bugzilla.redhat.com/show_bug.cgi?id=990279 inxi-1.9.14-2.el6 (FEDORA-EPEL-2013-11309) A full featured system information script Update Information: Update to new version with correct sources. Update to new version, Disable builtin update. Update to new version. First release of a newer, better system information script for irc, administration, and system troubleshooters. perl-Carp-Fix-1_25-1.01-3.el6 (FEDORA-EPEL-2013-11315) Smooth over incompatible changes in Carp 1.25 Update Information: This is the first Fedora/EPEL release of perl-Carp-Fix-1_25. References: [ 1 ] Bug #998410 - Review Request: perl-Carp-Fix-1_25 - Smooth over incompatible changes in Carp 1.25 https://bugzilla.redhat.com/show_bug.cgi?id=998410
Re: Bundled Flash
On Fri, Aug 23, 2013 at 1:47 PM, Adam Williamson awill...@redhat.comwrote: On Fri, 2013-08-23 at 11:26 -0700, Adam Williamson wrote: You could just say screw anaconda installs and just use `rm -rf`. Though I tried that once, in *EPEL* even, and it only took a week for someone to complain. :-( I suppose we could do it that way wrapped in an 'if' statement so it only runs on updates; seems reasonable to assume bash is available for an update transaction? Well, no, I guess not: http://lists.opensuse.org/opensuse-factory/2012-09/msg01063.html We can't have nice things. It's looking like I either need an ugly patch to RC or an ugly pile of lua in the spec. Sigh. Sorry, just noticed the gist of this thread. Are you trying to replace a directory with a symlink? Take a look at gallery2: Example. In %install: #remove bundled Smarty. rm -rf lib/smarty ln -s ../../php/Smarty2 ${RPM_BUILD_ROOT}%{installprefix}/gallery2/lib/smarty Then in %post: if [ -L %{installprefix}/gallery2/lib/smarty ]; then rm -f %{installprefix}/gallery2/lib/smarty fi if [ -d %{installprefix}/gallery2/lib/smarty -a ! -L %{installprefix}/gallery2/lib/smarty ]; then mv %{installprefix}/gallery2/lib/smarty %{installprefix}/gallery2/lib/smarty.rpmbak \ ln -s ../../php/Smarty2 %{installprefix}/gallery2/lib/smarty \ rm -rf %{installprefix}/gallery2/lib/smarty.rpmbak fi if [ ! -L %{installprefix}/gallery2/lib/smarty ]; then ln -s ../../php/Smarty2 %{installprefix}/gallery2/lib/smarty fi Then in %files %ghost %{installprefix}/gallery2/lib/smarty Pretty? Nope. Overkill? Maybe? Reliable? So far. This was the product of work by myself, Rex Dieter, and some serious pain. shudder moodle has similar examples, including one we had to reverse. -J -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- 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 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: USB-based Gnome 3 lockups
Digimer wrote: When I got this laptop (Thinkpad W530), I ran F17. It was always perfectly stable. When I installed F18, it started to (seemingly) randomly lock up Gnome 3. I could never see much in syslog of use. I knew it was just gnome because I could still ctrl+alt+fX to other terminals. If I restarted dbus, gnome restarted and most of the time I could log back in. I thought it might have been my bluetooth mouse, but it still crashed when bt/wan were disabled (airport mode mechanical switch flipped). The random lock ups continued when I upgraded to Fedora 19 and I never was able to sort out why. Finally I started noticing a pattern; When I used the USB3 ports, it would crash within a few hours. I recently stopped using the USB3 ports and it's not crashed since. The USB2 ports are just fine. So how can I debug this further? This query should go to the users list: http://admin.fedoraproject.org/mailman/listinfo/users As always, first step is update the BIOS and firmware: http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/g5uj15us.txt ---cortamorena--- 2.52 UEFI: 2.52 / ECP: 1.09 - (Fix) Fixed an issue where the computer might hang when attaching/detaching the USB device to/from the computer or Docking Station. ---fin-- BTW, this model has a lot of firmware updates(disk, amt, dvd, battery, ...) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, 2013-08-23 at 13:57 -0500, Jon Ciesla wrote: Sorry, just noticed the gist of this thread. Are you trying to replace a directory with a symlink? Take a look at gallery2: Example. In %install: #remove bundled Smarty. rm -rf lib/smarty ln -s ../../php/Smarty2 ${RPM_BUILD_ROOT}%{installprefix}/gallery2/lib/smarty Then in %post: if [ -L %{installprefix}/gallery2/lib/smarty ]; then rm -f %{installprefix}/gallery2/lib/smarty fi if [ -d %{installprefix}/gallery2/lib/smarty -a ! -L %{installprefix}/gallery2/lib/smarty ]; then mv %{installprefix}/gallery2/lib/smarty %{installprefix}/gallery2/lib/smarty.rpmbak \ ln -s ../../php/Smarty2 %{installprefix}/gallery2/lib/smarty \ rm -rf %{installprefix}/gallery2/lib/smarty.rpmbak fi if [ ! -L %{installprefix}/gallery2/lib/smarty ]; then ln -s ../../php/Smarty2 %{installprefix}/gallery2/lib/smarty fi Then in %files %ghost %{installprefix}/gallery2/lib/smarty Pretty? Nope. Overkill? Maybe? Reliable? So far. Are you sure? Does it work since rpm started throwing file conflict errors when you're trying to do this? That seems to be a fairly recent innovation, and the changelog indicates this was written in 2008. Has it actually been tested recently? https://bugzilla.redhat.com/show_bug.cgi?id=447156#c22 The discussions I could find about this seem to be down on doing it in % pre, so I can't see why %post would be any better. Ref http://mm3test.fedoraproject.org/hyperkitty/list/de...@mm3test.fedoraproject.org/message/XRQUA2DOHNCFWWP2F7WLFW6L5GHPCERZ/ . -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, Aug 23, 2013 at 2:11 PM, Adam Williamson awill...@redhat.comwrote: On Fri, 2013-08-23 at 13:57 -0500, Jon Ciesla wrote: Sorry, just noticed the gist of this thread. Are you trying to replace a directory with a symlink? Take a look at gallery2: Example. In %install: #remove bundled Smarty. rm -rf lib/smarty ln -s ../../php/Smarty2 ${RPM_BUILD_ROOT}%{installprefix}/gallery2/lib/smarty Then in %post: if [ -L %{installprefix}/gallery2/lib/smarty ]; then rm -f %{installprefix}/gallery2/lib/smarty fi if [ -d %{installprefix}/gallery2/lib/smarty -a ! -L %{installprefix}/gallery2/lib/smarty ]; then mv %{installprefix}/gallery2/lib/smarty %{installprefix}/gallery2/lib/smarty.rpmbak \ ln -s ../../php/Smarty2 %{installprefix}/gallery2/lib/smarty \ rm -rf %{installprefix}/gallery2/lib/smarty.rpmbak fi if [ ! -L %{installprefix}/gallery2/lib/smarty ]; then ln -s ../../php/Smarty2 %{installprefix}/gallery2/lib/smarty fi Then in %files %ghost %{installprefix}/gallery2/lib/smarty Pretty? Nope. Overkill? Maybe? Reliable? So far. Are you sure? Does it work since rpm started throwing file conflict errors when you're trying to do this? That seems to be a fairly recent innovation, and the changelog indicates this was written in 2008. Has it actually been tested recently? https://bugzilla.redhat.com/show_bug.cgi?id=447156#c22 The discussions I could find about this seem to be down on doing it in % pre, so I can't see why %post would be any better. Ref http://mm3test.fedoraproject.org/hyperkitty/list/de...@mm3test.fedoraproject.org/message/XRQUA2DOHNCFWWP2F7WLFW6L5GHPCERZ/. No, I've mostly left it as is since written, and adapted to additional bundled PHP libs as needed. Testing was heavy at the time but has been mimimal since. Conversely, it's been a long time since I've had a BZ on any of this, which is not necessarily good evidence that it works. If you find a better way I'm more than happy to rip it off^H^H^H^H^H^H^H^H^H^Hlearn. -J -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- 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 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
On Fri, 23 Aug 2013 09:04:54 -0500, inode0 wrote: [...] so why do we have to keep going over this? Dunno whether we _have_ to. The original purpose of this thread has been a different one. -- Fedora release 20 (Null) - Linux 3.11.0-0.rc6.git1.2.fc20.x86_64 loadavg: 0.08 0.09 0.07 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Release packages ownership
Hi, due to a lack of time, I released the ownership of most of my packages : cclive https://admin.fedoraproject.org/pkgdb/acls/name/cclive?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Command line video extraction utility clive https://admin.fedoraproject.org/pkgdb/acls/name/clive?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Video extraction tool for user-uploaded video hosts grilo-plugins https://admin.fedoraproject.org/pkgdb/acls/name/grilo-plugins?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Plugins for the Grilo framework libquvi https://admin.fedoraproject.org/pkgdb/acls/name/libquvi?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- A cross-platform library for parsing flash media stream libquvi-scripts https://admin.fedoraproject.org/pkgdb/acls/name/libquvi-scripts?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Embedded lua scripts that libquvi uses for parsing the media details qdevelop https://admin.fedoraproject.org/pkgdb/acls/name/qdevelop?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Development environment dedicated to Qt4 quvi https://admin.fedoraproject.org/pkgdb/acls/name/quvi?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Command line tool for parsing video download links trickle https://admin.fedoraproject.org/pkgdb/acls/name/trickle?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Portable lightweight userspace bandwidth shaper umph https://admin.fedoraproject.org/pkgdb/acls/name/umph?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Command line tool for parsing video links from Youtube feeds vbindiff https://admin.fedoraproject.org/pkgdb/acls/name/vbindiff?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Visual binary diff nomnom https://admin.fedoraproject.org/pkgdb/acls/name/nomnom?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- The graphical video download tool Feel free to take it :) Eponyme -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
Le vendredi 23 août 2013 à 14:19 -0500, Jon Ciesla a écrit : On Fri, Aug 23, 2013 at 2:11 PM, Adam Williamson awill...@redhat.com wrote: On Fri, 2013-08-23 at 13:57 -0500, Jon Ciesla wrote: Pretty? Nope. Overkill? Maybe? Reliable? So far. Are you sure? Does it work since rpm started throwing file conflict errors when you're trying to do this? That seems to be a fairly recent innovation, and the changelog indicates this was written in 2008. Has it actually been tested recently? https://bugzilla.redhat.com/show_bug.cgi?id=447156#c22 The discussions I could find about this seem to be down on doing it in % pre, so I can't see why %post would be any better. Ref http://mm3test.fedoraproject.org/hyperkitty/list/de...@mm3test.fedoraproject.org/message/XRQUA2DOHNCFWWP2F7WLFW6L5GHPCERZ/ . No, I've mostly left it as is since written, and adapted to additional bundled PHP libs as needed. Testing was heavy at the time but has been mimimal since. Conversely, it's been a long time since I've had a BZ on any of this, which is not necessarily good evidence that it works. If you find a better way I'm more than happy to rip it off^H^H^H^H^H^H^H^H^H^Hlearn. So what we found on irc : Since rpm first create the files for the new rpm that is installed, then remove the files that should be removed still present from old rpm and not in the new one, we fix the issue by waiting until the directory is removed to create the symlink. Looking at https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering , we need something after step 10. So in %install : +# remove bundled tinymce +rm -rf %{buildroot}%{roundcubedir}/program/js/tiny_mce + ( + others additions ) Since the only solution we have ( in new rpm ) is step 14, we need to add a %posttrans : +%posttrans +if [ ! -h %{roundcubedir}/program/js/tiny_mce ]; +ln -s /usr/share/tinymce/jscripts/tiny_mce %{roundcubedir}/program/js/tiny_mce +fi %posttrans is kinda garanted to have bash and ln, due to it being run after everything. However, we need to make sure that the symlink is managed by rpm in %files, so we add a %ghost : %config(noreplace) %{_sysconfdir}/httpd/conf.d/roundcubemail.conf %attr(0775,root,apache) %dir /var/log/roundcubemail %config(noreplace) %{_sysconfdir}/logrotate.d/roundcubemail +%ghost %{roundcubedir}/program/js/tiny_mce And if we remove the rpm, we need to remove the symlink : +%preun +if [ $1 -eq 0 ]; then +# remove the symlink we have added in %postrans for migration +rm -f %{roundcubedir}/program/js/tiny_mce +fi Now, this method has a huge problem, we cannot downgrade the package to the bundled version. There is no script that would remove the symlink in time, ie before step 3 of https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering Everything that is run is from the new package to install, ie the old rpm that we want to downgrade to. So since we would need to fix the old rpm to have it downgradable, that's a bit hard. Another issue is the %ghost, we cannot really check the symlink is still the same. Maybe there is some better syntax for that. -- Michael Scherer -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Blocking unblocked retired packages
Hi, I blocked the following packages that were retired in pkgdb but not blocked in koji (there might be some packages included that have been retired recently where rel-eng tickets were filed): acheck acheck-rules animorph bsd-mailx c-ares19 cdi-api11 clearlooks-phenix-theme climm detex emerillon gnome-shell-extension-noripple gnome-shell-extension-workspacesmenu gpp4 guiloader-c++ hardinfo ibus-panel-extensions icc_examin makehuman metapost-metauml mhgui nemo-open-terminal nodejs-tobi-cookie perl-Bio-SamTools php-pecl-zendopcache PythonCAD python-nova-adminclient python-testosterone repsurgeon rhevsh tetex-IEEEtran xmltex I also temporarily blocked the following packages but then run a dependency check and noticed that a lot of packages depend on these retired packages. The dependency check is not complete, because too many packages are affected. I did not yet Bcc all maintainers, since this affects too many maintainers as well. Package(co)maintainers === directfb orphan, kwizart libgssglue orphan maven2-common-poms orphan, mizdebsk, akurtakov, fnasser, yyang, huwang, dbhole, sochotni python-quantumclient orphan, jruzicka, vaneldik, pbrady, apevec, gkotton, markmc, rkukura spacewalk-web orphan tslib orphan The following packages require above mentioned packages: Depending on: directfb xine-lib (maintained by: kkofler, kkofler, rdieter) xine-lib-extras requires libdirect-1.6.so.0, libdirectfb-1.6.so.0, libfusion-1.6.so.0 Depending on: libgssglue conserver (maintained by: jkastner) conserver requires libgssglue.so.1, libgssglue.so.1(libgssapi_CITI_2) conserver requires libgssapi-devel = 0.4-2.fc19, libgssglue-devel = 0.4-2.fc19 conserver-client requires libgssglue.so.1, libgssglue.so.1(libgssapi_CITI_2) libserf (maintained by: cicku, jorton) libserf requires libgssapi-devel = 0.4-2.fc19 rdesktop (maintained by: ssp, fab, alexl, caillon, caolanm, hadess, johnp, mbarnes, mclasen, rhughes, rstrode, ssp, xiphmont, rathann) rdesktop requires libgssglue.so.1, libgssglue.so.1(libgssapi_CITI_2) rdesktop requires libgssglue-devel = 0.4-2.fc19 gnome-rdp (maintained by: lbazan, vicodan, echevemaster, lbazan) gnome-rdp requires rdesktop = 1.8.0-1.fc20 gnome-rdp requires rdesktop = 1.8.0-1.fc20 vinagre (maintained by: hadess, rishi, berrange, teuf) vinagre requires rdesktop = 1.8.0-1.fc20 gnome-do-plugins (maintained by: nushio, mcrha, antiaircraft) gnome-do-plugins-vinagre requires vinagre = 3.9.90-1.fc21 subversion (maintained by: jorton, lkundrak, kanarip) subversion requires libserf-1.so.0 subversion-javahl requires libserf-1.so.0 subversion-libs requires libserf-1.so.0 subversion-python requires libserf-1.so.0 subversion-ruby requires libserf-1.so.0 subversion-tools requires libserf-1.so.0 Depending on: maven2-common-poms antlr-maven-plugin (maintained by: spot, tradej) antlr-maven-plugin requires maven2-common-poms = 1.0-50.fc20 buildnumber-maven-plugin (maintained by: weli, mizdebsk, tradej, dbhole) buildnumber-maven-plugin requires maven2-common-poms = 1.0-50.fc20 maven-scm (maintained by: guidograzioli, mizdebsk, jcapik, akurtakov, sochotni, java-sig) maven-scm requires maven2-common-poms = 1.0-50.fc20 mercury (maintained by: gil) mercury requires maven2-common-poms = 1.0-50.fc20 plexus-ant-factory (maintained by: sochotni, tradej, msrb, mizdebsk, java-sig) plexus-ant-factory requires maven2-common-poms = 1.0-50.fc20 maven-plugin-tools (maintained by: jcapik, mizdebsk, yyang, sochotni, java-sig, jcapik) maven-plugin-tools requires plexus-ant-factory = 1.0-0.12.a2.1.fc20 maven-script-ant requires plexus-ant-factory = 1.0-0.12.a2.1.fc20 access-modifier-annotation (maintained by: msrb, tradej, mizdebsk, sochotni, java-sig) access-modifier-annotation requires mvn(org.apache.maven.plugins:maven-scm-plugin) = 1.7 fasterxml-oss-parent (maintained by: gil, java-sig) fasterxml-oss-parent requires mvn(org.apache.maven.plugins:maven-scm-plugin) = 1.7
Re: F20 release name election?
On Fri, Aug 23, 2013 at 8:34 AM, Josh Boyer wrote: On Thu, Aug 22, 2013 at 10:29 PM, Paul Wouters wrote: It would be good if the next vote would allow none as an option. I could not vote 'none' on the last election. And I think it is important to track the percentage of people who want to kill the meaningless names. That's a good suggestion for future votes. At the moment, the best you can do is cast 0 votes for all choices. That won't really change the outcome, but at least votes will be recorded. Can we request an exception from the board to add (empty string) as an option for _just_ the F20 naming poll? Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, 2013-08-23 at 23:15 +0200, Michael Scherer wrote: No, I've mostly left it as is since written, and adapted to additional bundled PHP libs as needed. Testing was heavy at the time but has been mimimal since. Conversely, it's been a long time since I've had a BZ on any of this, which is not necessarily good evidence that it works. If you find a better way I'm more than happy to rip it off^H^H^H^H^H^H^H^H^H^Hlearn. So what we found on irc : Since rpm first create the files for the new rpm that is installed, then remove the files that should be removed still present from old rpm and not in the new one, we fix the issue by waiting until the directory is removed to create the symlink. Looking at https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering , we need something after step 10. So in %install : +# remove bundled tinymce +rm -rf %{buildroot}%{roundcubedir}/program/js/tiny_mce + ( + others additions ) Since the only solution we have ( in new rpm ) is step 14, we need to add a %posttrans : +%posttrans +if [ ! -h %{roundcubedir}/program/js/tiny_mce ]; +ln -s /usr/share/tinymce/jscripts/tiny_mce %{roundcubedir}/program/js/tiny_mce +fi %posttrans is kinda garanted to have bash and ln, due to it being run after everything. However, we need to make sure that the symlink is managed by rpm in %files, so we add a %ghost : %config(noreplace) %{_sysconfdir}/httpd/conf.d/roundcubemail.conf %attr(0775,root,apache) %dir /var/log/roundcubemail %config(noreplace) %{_sysconfdir}/logrotate.d/roundcubemail +%ghost %{roundcubedir}/program/js/tiny_mce And if we remove the rpm, we need to remove the symlink : +%preun +if [ $1 -eq 0 ]; then +# remove the symlink we have added in %postrans for migration +rm -f %{roundcubedir}/program/js/tiny_mce +fi Now, this method has a huge problem, we cannot downgrade the package to the bundled version. There is no script that would remove the symlink in time, ie before step 3 of https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering Everything that is run is from the new package to install, ie the old rpm that we want to downgrade to. So since we would need to fix the old rpm to have it downgradable, that's a bit hard. Another issue is the %ghost, we cannot really check the symlink is still the same. Maybe there is some better syntax for that. Thanks, misc. So to put this in context: it seems ridiculous we don't have single canonical recommended method for doing this kind of directory-something_else change when it really needs to be done. I suspect we're going to need to do it a whole lot for the js-unbundling effort - from what I've seen so far, it's often so ugly as to be impractical to try and patch a webapp to find a js library it expects to be inside its tree, outside its tree. There's often PHP which looks for it as a filesystem path but also code which generates *direct URLs* to the stuff in the shared js library, for instance, which would be ugly to try and fix up for the shared library being elsewhere (you'd have to have an Alias for each webapp just for that case). So anyway - I think we need some best practice on this. We definitely need a 'if you absolutely must change a directory into a symlink (or a file, or the same operations in the other direction), here's how you do it' snippet set. If folks could chip in with thoughts on misc's approach to doing this, that'd be great: Panu, do you see any problems? Know a better way? I tried the giant-lump-of-lua from https://bugs.launchpad.net/rpm/+bug/633636/comments/3 , but it throws a bunch of warnings when cleanup of the *old* package tries to remove all the files that are now no longer there, which is bad, and misc thinks it's bad in other ways, I believe. There are various other attempts to do this kind of operation spread through various packages in Fedora and out - moodle has some, for instance, xmvn has one, there are others I think that I don't have to hand right now. And, T.C., we probably need the Web Assets policy to set some rules/guidelines on how best to achieve unbundling: should we always try to patch the upstream to find the 'official' location of the shared resource on Fedora? Should we always do it with symlinks or aliases where possible? Should we allow either approach depending on circumstances? I'd like to unbundle tinymce from roundcubemail and moodle, but it's probably best to decide 'best practice' first then do it in line with that. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
On 08/23/2013 04:27 PM, Orcan Ogetbil wrote: Can we request an exception from the board to add (empty string) as an option for _just_ the F20 naming poll? You'd have to reset voting, too. I've already voted, but I'd re-vote to vote for no name. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
On Fri, Aug 23, 2013 at 5:27 PM, Orcan Ogetbil oget.fed...@gmail.com wrote: Can we request an exception from the board to add (empty string) as an option for _just_ the F20 naming poll? Or how about None. It even fits with the lineage -- just like the Schrodinger's cat, it's neither False nor True. It's None. That would be a worthy tribute to the pythonista and the release-name hater. Best, -- Konstantin Ryabitsev LinuxFoundation.org Montréal, Québec -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 schedule: what would you do with more time?
On 08/22/2013 09:03 AM, Matthew Miller wrote: As we look at Fedora.next ideas and possibly decide to start implementation in the F21 timeframe, we will likely find _new_ things that take specific work. Let's not worry about that right now. What things we do _now_ could be improved with the investment of some effort? Some kind of continuous integration testing would be lovely - automatically build some dependent packages when one is updated and note any failures. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, Aug 23, 2013 at 11:26 AM, Adam Williamson awill...@redhat.com wrote: On Fri, 2013-08-23 at 06:36 -0700, T.C. Hollingsworth wrote: Any chance you could just use an Alias in the apache config? Then you can just delete the directory and not muck around with making yum happy. Doesn't seem to work. Seems like it's just ignored: if I set it and move tiny_mce/ away, no tinymce. If I leave it set but also put the tiny_mce directory in place on the filesystem (by symlink or not), tinymce works. I don't actually have any idea whether PHP is supposed to respect the Apache aliases or whether it's looking at the 'real' filesystem, but it seems to be b). Ugh sorry, I didn't realize PHP had its tentacles in there. The Alias trick only works when it's just a script tag. -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Release packages ownership
Hi, - Original Message - Hi, due to a lack of time, I released the ownership of most of my packages : snip The following packages are used by Totem (directly or indirectly), so it would be good to have them find new owners: grilo-plugins https://admin.fedoraproject.org/pkgdb/acls/name/grilo-plugins?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Plugins for the Grilo framework libquvi https://admin.fedoraproject.org/pkgdb/acls/name/libquvi?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- A cross-platform library for parsing flash media stream libquvi-scripts https://admin.fedoraproject.org/pkgdb/acls/name/libquvi-scripts?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Embedded lua scripts that libquvi uses for parsing the media details Cheers -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Blocking unblocked retired packages
Hi, On Fri, Aug 23, 2013 at 11:25:47PM +0200, Till Maas wrote: Depending on: maven2-common-poms antlr-maven-plugin (maintained by: spot, tradej) antlr-maven-plugin requires maven2-common-poms = 1.0-50.fc20 This is a BR, I reported it here: https://bugzilla.redhat.com/show_bug.cgi?id=887166 and blocked maven2-common-poms again. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Blocking unblocked retired packages
I don't know what happened with libgssglue. This was retired for what reason? It affects too many... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
On 23/08/13 17:49 -0400, Konstantin Ryabitsev wrote: Or how about None. It even fits with the lineage -- just like the Schrodinger's cat, it's neither False nor True. It's None. That would be a worthy tribute to the pythonista and the release-name hater. +1 -- Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, 2013-08-23 at 01:53 -0700, Adam Williamson wrote: On Thu, 2013-08-22 at 22:05 -0700, Adam Williamson wrote: On Thu, 2013-08-22 at 21:47 -0700, Adam Williamson wrote: As plupload is a .sh not a .as3 I *think* we may be able to build it with swfc. I'll see whether that's possible. plupload looks like, well, a giant pain in the ass. It depends on a bit called moxie which is just kinda smooshed into the .swf shipped with wordpress. If someone else wants to work on building that mess, go for it, but for now, I'm going to work on ripping out the Flash and Silverlight parts from plupload, and ripping out swfupload entirely. I've done a super-dumb test scratch build of wordpress at http://koji.fedoraproject.org/koji/taskinfo?taskID=5844538 which more or less just rips swfupload out entirely, and rips out the other binary blobs with no adjustments, hoping the plugins that use them will fall back or error out intelligently. Help testing this is welcome. Trying to rip the bits out any more delicately looks to be a royal PITA. Bloody minified javascript. OK, I've now tested and improved the Wordpress changes. swfupload is still completely gone. tinymce is patched to smoothly remove the use of moxieplayer, using the same patch I've used and tested in other packages. plupload is patched to never try and use the Flash or Silverlight uploaders, only the HTML5 and HTML4 ones (really, it's not a 'patch' so much as the removal of the .js files for the Flash and Silverlight uploaders). mediaelement is patched to never try and use the Flash or Silverlight players; it will embed an HTML5 player if possible, and offer a download link for the media if not. I've tested all these changes against Firefox 23, IE 10, and IE 10 in its IE 7 emulation mode, and they seem to work correctly. I'm sending a Wordpress 3.6 build with all the changes out for testing. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, Aug 23, 2013 at 2:15 PM, Michael Scherer m...@zarb.org wrote: So what we found on irc : Since rpm first create the files for the new rpm that is installed, then remove the files that should be removed still present from old rpm and not in the new one, we fix the issue by waiting until the directory is removed to create the symlink. Looking at https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering , we need something after step 10. snip code While we're sharing hacks...did you know that rpm doesn't move symlink targets when they change in some instances, too? I can't make a simple minimal test case reproduce this to save my life, but it sure does blow up in the real world: https://bugzilla.redhat.com/show_bug.cgi?id=997978 Thank $DEITY with nodejs I can divine the correct symlink targets from a json file on the filesystem, so I can fix up ~20 packages in one scriptlet: http://pkgs.fedoraproject.org/cgit/nodejs-inherits.git/tree/nodejs-inherits.spec#n43 If I weren't so lucky I would have had to add scriptlet gunk to ~20 packages instead of just that one. :-( Now, this method has a huge problem, we cannot downgrade the package to the bundled version. There is no script that would remove the symlink in time, ie before step 3 of https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering Everything that is run is from the new package to install, ie the old rpm that we want to downgrade to. So since we would need to fix the old rpm to have it downgradable, that's a bit hard. The %pretrans hackery previously recommended also suffers from the same flaw. I'm not sure there's anything we can do about it. :-( Another issue is the %ghost, we cannot really check the symlink is still the same. Maybe there is some better syntax for that. -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, Aug 23, 2013 at 2:28 PM, Adam Williamson awill...@redhat.com wrote: And, T.C., we probably need the Web Assets policy to set some rules/guidelines on how best to achieve unbundling: should we always try to patch the upstream to find the 'official' location of the shared resource on Fedora? Should we always do it with symlinks or aliases where possible? Should we allow either approach depending on circumstances? I'd like to unbundle tinymce from roundcubemail and moodle, but it's probably best to decide 'best practice' first then do it in line with that. Definitely either approach depending on circumstances. I specifically didn't define a best practice because I didn't think there was going to be one. In some cases there might be a global config file that lets you point the path to the Fedora-y location, so it's easier to patch that one file than to mess around with the directory-symlink madness. In other cases it's hardcoded in nine million places all over the codebase, so the symlink approach starts to look much nicer. :-) That's also the reason why a global httpd path is coming (unfortunately not till Fedora 21 now), because in some instances a server path is easier to config than a filesystem path. Basically, do whatever makes you least likely to pull all your hair out in the process. :-) Sooner or later there's going to be a best practices (emphasis on the plural) document that describes all these techniques nicely, but I wasn't expecting people to jump into unbundling with both feet quite so quickly. ;-) -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Release packages ownership
On Sat, Aug 24, 2013 at 7:11 AM, Bastien Nocera bnoc...@redhat.com wrote: libquvi https://admin.fedoraproject.org/pkgdb/acls/name/libquvi?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- A cross-platform library for parsing flash media stream libquvi-scripts https://admin.fedoraproject.org/pkgdb/acls/name/libquvi-scripts?_csrf_token=a20dac710fd0964437afa7c441bfb9b72e57b277-- Embedded lua scripts that libquvi uses for parsing the media details Easy, taken. If there is no objection, I'll push an update of its latest version. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
Josh Boyer jwboyer at fedoraproject.org writes: The Board has an open ticket on the naming process. We're working through it now, but no release names isn't an immediate option because the last time we proposed that the community vote showed names were still desired. Hopefully we'll resolve the ticket shortly and explain how naming needs to work in the future. What is the ticket URL? I don't see it under active Fesco tickets. BTW, I was wondering if it's possible to simply remove any reference to the release name from the Fedora OS, so it's not a burden on developers (like Schrödinger’s Cat was). I noticed that there is a closed ticket https://fedorahosted.org/fesco/ticket/1103 (Release names should not include shell metacharacters), which appears to just assume that the release name has to be included in the OS itself (otherwise, there would be no need for the ticket). Is that actually true? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Review swap request: web-assets
Hi! Would someone be willing to trade me a review for: https://bugzilla.redhat.com/show_bug.cgi?id=997678 It's dead simple at the moment: it just provides a couple directories and RPM macros. Later on it will grow some httpd magic but that's on hold until Fedora 21 since we're still sorting that out with Debian and it's past Change Freeze. Thanks! -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, Aug 23, 2013 at 02:28:23PM -0700, Adam Williamson wrote: On Fri, 2013-08-23 at 23:15 +0200, Michael Scherer wrote: So anyway - I think we need some best practice on this. We definitely need a 'if you absolutely must change a directory into a symlink (or a file, or the same operations in the other direction), here's how you do it' snippet set. If folks could chip in with thoughts on misc's approach to doing this, that'd be great: Panu, do you see any problems? Know a better way? I tried the giant-lump-of-lua from https://bugs.launchpad.net/rpm/+bug/633636/comments/3 , but it throws a bunch of warnings when cleanup of the *old* package tries to remove all the files that are now no longer there, which is bad, and misc thinks it's bad in other ways, I believe. There are various other attempts to do this kind of operation spread through various packages in Fedora and out - moodle has some, for instance, xmvn has one, there are others I think that I don't have to hand right now. +1 I was going to see if limburgher would push his recipe into an FPC guideline but it seems that that method no longer works reliably. it'll be interesting to hear what Panu says here but I think the FPC could live with the caveats if it had to. And, T.C., we probably need the Web Assets policy to set some rules/guidelines on how best to achieve unbundling: should we always try to patch the upstream to find the 'official' location of the shared resource on Fedora? Should we always do it with symlinks or aliases where possible? Should we allow either approach depending on circumstances? One further thought here: https://fedoraproject.org/w/index.php?title=Packaging:JavaScript#Static_Inclusion_of_Libraries Taking a static library approach is also allowed. This can save packagers from some of the headaches you mentioned (like some things detecting the absolute path to libraries) but introduces the static libraries headaches (having to rebuild when the library package updates in order to get the changes that occurred there.) Not sure if we want to recommend that just to get around the directory-symlink issue but it is an option. -Toshio pgphbf6jy0g35.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
On Fri, Aug 23, 2013 at 11:55:44PM +, Andre Robatino wrote: Josh Boyer jwboyer at fedoraproject.org writes: The Board has an open ticket on the naming process. We're working through it now, but no release names isn't an immediate option because the last time we proposed that the community vote showed names were still desired. Hopefully we'll resolve the ticket shortly and explain how naming needs to work in the future. What is the ticket URL? I don't see it under active Fesco tickets. It's a board ticket. And unfortunately as a project we've never managed to resolve the board's need for private tickets sometimes and the need for public tickets in most cases. BTW, I was wondering if it's possible to simply remove any reference to the release name from the Fedora OS, so it's not a burden on developers (like Schrödinger’s Cat was). I noticed that there is a closed ticket https://fedorahosted.org/fesco/ticket/1103 (Release names should not include shell metacharacters), which appears to just assume that the release name has to be included in the OS itself (otherwise, there would be no need for the ticket). Is that actually true? There are various things that want to get at the release name. I suspect that if we put it into a different file in the OS, those things would just move around to try to find it. We could just put the release number into those files and keep the release name in our heads, I suppose. There wouldn't be a technical downside to that but I don't know whether people would like that socially or not. -Toshio pgpdH_L0NzERa.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
Toshio Kuratomi a.badger at gmail.com writes: We could just put the release number into those files and keep the release name in our heads, I suppose. There wouldn't be a technical downside to that but I don't know whether people would like that socially or not. When I said release name I meant just the non-numerical reference. So for example the F19 version of /etc/fedora-release could have just been Fedora release 19, not Fedora release 19 (Schrödinger’s Cat). If this was acceptable, the release name could use any characters whatsoever, even the Batman symbol (a Family Guy reference). -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On Fri, 2013-08-23 at 17:12 -0700, Toshio Kuratomi wrote: On Fri, Aug 23, 2013 at 02:28:23PM -0700, Adam Williamson wrote: On Fri, 2013-08-23 at 23:15 +0200, Michael Scherer wrote: So anyway - I think we need some best practice on this. We definitely need a 'if you absolutely must change a directory into a symlink (or a file, or the same operations in the other direction), here's how you do it' snippet set. If folks could chip in with thoughts on misc's approach to doing this, that'd be great: Panu, do you see any problems? Know a better way? I tried the giant-lump-of-lua from https://bugs.launchpad.net/rpm/+bug/633636/comments/3 , but it throws a bunch of warnings when cleanup of the *old* package tries to remove all the files that are now no longer there, which is bad, and misc thinks it's bad in other ways, I believe. There are various other attempts to do this kind of operation spread through various packages in Fedora and out - moodle has some, for instance, xmvn has one, there are others I think that I don't have to hand right now. +1 I was going to see if limburgher would push his recipe into an FPC guideline but it seems that that method no longer works reliably. it'll be interesting to hear what Panu says here but I think the FPC could live with the caveats if it had to. And, T.C., we probably need the Web Assets policy to set some rules/guidelines on how best to achieve unbundling: should we always try to patch the upstream to find the 'official' location of the shared resource on Fedora? Should we always do it with symlinks or aliases where possible? Should we allow either approach depending on circumstances? One further thought here: https://fedoraproject.org/w/index.php?title=Packaging:JavaScript#Static_Inclusion_of_Libraries Taking a static library approach is also allowed. This can save packagers from some of the headaches you mentioned (like some things detecting the absolute path to libraries) but introduces the static libraries headaches (having to rebuild when the library package updates in order to get the changes that occurred there.) Not sure if we want to recommend that just to get around the directory-symlink issue but it is an option. Using the system copy really would be a lot cleaner, in some cases - I'd really hope we can do it and not have to resort to static inclusion :/ -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Review swap request: web-assets
On Aug 23, 2013 6:00 PM, T.C. Hollingsworth tchollingswo...@gmail.com wrote: Hi! Would someone be willing to trade me a review for: https://bugzilla.redhat.com/show_bug.cgi?id=997678 It's dead simple at the moment: it just provides a couple directories and RPM macros. Later on it will grow some httpd magic but that's on hold until Fedora 21 since we're still sorting that out with Debian and it's past Change Freeze. Thanks! -T.C. -- I'll take this. I have one that I'd like your insight on regarding the web assets dir, conveniently; details to follow. --Pete -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On 8/23/13, Adam Williamson awill...@redhat.com wrote: On Fri, 2013-08-23 at 17:12 -0700, Toshio Kuratomi wrote: One further thought here: https://fedoraproject.org/w/index.php?title=Packaging:JavaScript#Static_Inclusion_of_Libraries Taking a static library approach is also allowed. This can save packagers from some of the headaches you mentioned (like some things detecting the absolute path to libraries) but introduces the static libraries headaches (having to rebuild when the library package updates in order to get the changes that occurred there.) Not sure if we want to recommend that just to get around the directory-symlink issue but it is an option. Using the system copy really would be a lot cleaner, in some cases - I'd really hope we can do it and not have to resort to static inclusion :/ +1 That exception is intended mainly for two specific classes of issues: 1. Minified JS libraries that have always bundled other libraries. For instance, jQuery has bundled sizzle.js since time immemorial, and unbundling it and requiring every webapp to add an extra script tag for sizzle.js would be a complete nightmare. 2. Webapps that use only parts of ginormous frameworks like dojo and build and minify their own JS file that only has the stuff they need. At least one of the maintainers of such a package would prefer to have to keep up with updates in a static copy rather than force clients to load gobs of JS that isn't used, and that makes a lot of sense. It's for case #2 that the exception got expanded to be allowed for webapp packages, but it's really not intended to just permit bundling to continue when you can just as easily unbundle. I'll look at tightening I don't consider the rpm symlink bug to be a good enough reason to invoke this exception, however annoying it is. It'll be a lot easier in the long run to just figure out the necessary spec goop to get it converted, and then the maintainers of packages dependent on tinymce will never have to worry about it again. ;-) -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
On 8/23/13, T.C. Hollingsworth tchollingswo...@gmail.com wrote: It's for case #2 that the exception got expanded to be allowed for webapp packages, but it's really not intended to just permit bundling to continue when you can just as easily unbundle. I'll look at tightening Bah, that was supposed to say: I'll look at tightening the language there in a future update so this doesn't get used as a blanket excuse to bundle when we really shouldn't be bundling. -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Bundled Flash
fre 2013-08-23 klockan 16:46 -0700 skrev Adam Williamson: But if I'm going to do it, I'd rather get the replace-dir-with-symlink stuff 'right' (for whatever value we decide is 'right') first time. The shortest scriptlet I saw to remove a directory in pretrans is: (see e.g. http://pkgs.fedoraproject.org/cgit/mozilla-firetray.git/tree/mozilla-firetray.spec) %pretrans -p lua st = posix.stat(path to dir) if st and st.type == directory then os.execute(rm -rf path to dir) end But, this sort of cheats a bit since is calls out to system rm, which is not present on the initial install transaction. On the other hand on the initial install transaction the directory does not exist and the os.execute will not be executed. So it is possibly acceptable. Doing recursive directory removal completely in lua is as already mentioned a quite long script. The corresponding scriptlets to remove a symlink or a file do not have to cheat: %pretrans -p lua st = posix.stat(path to link) if st and st.type == link then os.remove(path to link) end %pretrans -p lua st = posix.stat(path to file) if st and st.type == regular then os.remove(path to file) end Mattias smime.p7s Description: S/MIME cryptographic signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Proposal for new package group: Development:Formal Methods Tools
On Thu, Aug 22, 2013 at 03:26:48PM -0600, Jerry James wrote: On Sat, Aug 17, 2013 at 1:31 PM, John C. Peterson j...@eskimo.com wrote: I would like to edit comps.xml to add a new package group for the tools that have already been packaged by the Formal Methods SIG. I propose that the group be located under the Development category. Id: formal-methods-tools Name: Formal Methods Tools Description: These tools for the development of hardware and software are based on Formal proof methods. The default for the group itself will be false (will not be installed by default). Find below a list of package names to be included in the group with the proposed level (D for default, O for optional). Given that the scope of application of these tools is very diverse, it made sense to me to make most of the packages optional; O alt-ergo O alt-ergo-gui O coq O coq-coqide O coq-doc O coq-emacs O coq-emacs-el O cryptominisat O cryptominisat-devel O csisat O cudd O cvc3 O cvc3-devel O cvc3-doc O cvc3-emacs O cvc3-emacs-el O cvc3-java O cvc3-xemacs O cvc3-xemacs-el O E O emacs-common-proofgeneral O emacs-proofgeneral O emacs-proofgeneral-el O flocq O flocq-source D frama-c O gappa O gappalib-coq O glueminisat D minisat2 O picosat D prover9 O prover9-apps O prover9-devel O prover9-doc O pvs-sbcl O sat4j O stp O stp-devel O tex-zfuzz O why O why-all O why-coq O why-gwhy O why-jessie O why-pvs-support O why3 O why3-emacs O zenon I maintain or comaintain a fair number of these packages. I originally added them to comps under Engineering and Scientific, just because there was no other category that was even remotely close to what these packages do. However, they are not really a great fit for that category. I like John's proposal. We should probably move all of them over to this new category once it is created. We can consider whether some of them should be listed in both places, but I think most would be in the new formal-methods-tools category only. I think most users who are familiar with development tools based on Formal proof methods would look for them under the Development category. (So I agree, most all of the above packages should be moved into the new group). The polybori, polybori-gui, polybori-ipbori packages certainly seem like they could be meaningfully listed in both groups. (The provers based on first order logic like the prover9, prover9-devel packages seem like candidates as well, since they could be of interest to pure mathematicians). -- John C. Peterson, KD6EKQ mailto:j...@eskimo.com San Diego, CA U.S.A -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 release name election?
On Thu, 2013-08-22 at 17:39 -0700, Dan Mashal wrote: I personally LOVE release names. However, I feel that we should forego it this one release. What is the point of the board of the community decides everything? We all know that there needs to be a tough decision made by the board, and it's not release names vs no release names. For me it's about doing what Seth would have wanted, whether he was close to us or not, whether he he touched us or knew us or cared about personally. I really hate trying to put words in others people mouths, especially when they cannot reply themselves, but my experience of Seth tells me he wouldn't want the Board to go against the wishes of the Fedora community in his honor, he wouldn't find that very honorable. I would like to see a more prominent dedication than just the release announcement, but I do not know what that could be. Simo. -- Simo Sorce * Red Hat, Inc * New York -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1000315] New: Please build perl-MooseX-Aliases for EPEL
https://bugzilla.redhat.com/show_bug.cgi?id=1000315 Bug ID: 1000315 Summary: Please build perl-MooseX-Aliases for EPEL Product: Fedora Version: rawhide Component: perl-MooseX-Aliases Assignee: iarn...@gmail.com Reporter: n.beern...@oxilion.nl QA Contact: extras...@fedoraproject.org CC: iarn...@gmail.com, perl-devel@lists.fedoraproject.org Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=b9FtImhX2Xa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1000315] Please build perl-MooseX-Aliases for EPEL
https://bugzilla.redhat.com/show_bug.cgi?id=1000315 --- Comment #1 from Niek Beernink n.beern...@oxilion.nl --- Sorry, I hit submit a little too quick and forgot to add the polite question: Would you mind building perl-MooseX-Aliases for EPEL so we can use it in CentOS? -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=myh9vFznVPa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1000315] Please build perl-MooseX-Aliases for EPEL
https://bugzilla.redhat.com/show_bug.cgi?id=1000315 Niek Beernink n.beern...@oxilion.nl changed: What|Removed |Added Blocks||138 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=VRjNWgy5i2a=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1000038] Please build perl-Net-Twitter for EPEL
https://bugzilla.redhat.com/show_bug.cgi?id=138 Niek Beernink n.beern...@oxilion.nl changed: What|Removed |Added Depends On||1000318 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=40l73CeydYa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1000318] New: Please build perl-MooseX-Role-Parameterized for EPEL
https://bugzilla.redhat.com/show_bug.cgi?id=1000318 Bug ID: 1000318 Summary: Please build perl-MooseX-Role-Parameterized for EPEL Product: Fedora Version: rawhide Component: perl-MooseX-Role-Parameterized Assignee: iarn...@gmail.com Reporter: n.beern...@oxilion.nl QA Contact: extras...@fedoraproject.org CC: iarn...@gmail.com, mmasl...@redhat.com, perl-devel@lists.fedoraproject.org Would you mind building perl-MooseX-Role-Parameterized for EPEL so we can use it in CentOS? -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=DrjNxUZRU0a=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1000318] Please build perl-MooseX-Role-Parameterized for EPEL
https://bugzilla.redhat.com/show_bug.cgi?id=1000318 Niek Beernink n.beern...@oxilion.nl changed: What|Removed |Added Blocks||138 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=c8Ecz8NTS4a=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel