Re: [Catalyst] Can't locate object method "storage" via package "MyApp::Model::DB"
On Thu, Jan 7, 2010 at 9:26 AM, Matthias Dietrich wrote: > Hi, > > after upgrading every perl module on my dev system weeks ago I get many > errors like > > Can't locate object method "storage" via package "MyApp::Model::DB" This sounds like what I ran into yesterday, after upgrading Catalyst::Model::DBIC::Schema to 0.35. I suspect you need to add the SchemaProxy[1] trait to your model. -Chris [1] http://search.cpan.org/perldoc?Catalyst::TraitFor::Model::DBIC::Schema::SchemaProxy -- Chris Weyl Ex astris, scientia ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Easiest Way To Update Fedora 10 to Catalyst-Runtime-5.71000
On Fri, Feb 6, 2009 at 10:45 AM, Richard Siddall < richard.sidd...@elirion.net> wrote: > Robert L Cochran wrote: > >> My installation of Fedora 10 x86_64 is using Fedora-packaged Perl >> (perl-5.10.0-53.fc10.x86_64) and the perl-Catalyst-Runtime >> (perl-Catalyst-Runtime-5.7015-1.fc10.noarch) and it doesn't seem to be >> maintained; there is no 5.71000 release as an RPM package. I have read >> the thread from last summer about Red Hat and CentOS releases not having >> real good Perl installations. >> >> I'd like to upgrade to 5.71000, using an RPM package if possible. >> (perhaps I can get the source RPM for 5.7015 and rebuild it for 5.71000 >> with any new dependencies added in. I have an RPM build tree on this >> machine that I've been using to build stuff like avr-gcc.) >> >> Any suggestions? >> > > Looks like the maintainer of that RPM is > https://fedoraproject.org/wiki/User:Cweyl according to > http://koji.fedoraproject.org/koji/packageinfo?packageID=4381 > > You might try contacting him/her and asking for an updated package. (Note > the Amazon wishlist!) > Heh. I'd forgotten I link that there. perl-Catalyst-Runtime is maintained; 5.71000 was just released on 19 Jan and it takes time to look at it, make any spec updates, build test and push. Even if I'd updated the package on the same day it was released it likely wouldn't have made it into F-10 at this point in the stable updates channel (especially given how focused people are on the F-11 alpha at the moment). I do tend to issue updates in the "stable" releases as well (e.g. F-9, F-10 at this point), but other packagers may choose to limit their updates to rawhide (aka what will be the next release) unless specifically requested. We also try to be pretty careful with upgrading complex packages like perl-Catalyst-Runtime, as breaking things in a stable release is, well, pretty embarassing :) One of the best ways to ask that a package be updated is to file a bug against it in bugzilla[1], asking that it be updated in a given release to a newer version... This both ensures that it doesn't get lost in someone's inbox, and allows other Perl packagers some visibility to it. Most packagers respond well to RFE bugs like this, and on the whole, the people who own Perl packages in Fedora tend to be pretty proactive. If you want to take a shot at updating them on your own, cpanspec or CPANPLUS::Dist::RPM/::Fedora are good places to look. Fedora's CVS[2] also contains everything needed to build an updated package, and, like everyone else, we love patches too. Especially as part of a bugzilla entry :) Right now, updating perl-Catalyst-Runtime is dependent on perl-HTTP-Body 1.05 making its way through the updates system. Once that's in stable, I can update F-10 to the latest. -Chris [1] https://bugzilla.redhat.com; directly at https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora, pick the package under the "component" listing. [2] http://fedoraproject.org/wiki/Using_Fedora_CVS -- Chris Weyl Ex astris, scientia ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Accessing request environment variables under fastcgi?
On Fri, Oct 17, 2008 at 10:19 AM, Mark Trostler <[EMAIL PROTECTED]> wrote:
>
> They're all in a hashref here: $c->engine->env
I knew I was making way too much out of it.
Thanks :-)
-Chris
--
Chris Weyl
Ex astris, scientia
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
[Catalyst] Accessing request environment variables under fastcgi?
Hey all -- So, I might be a bit crazy here, and there might be a perfectly good way to do this that I'm not aware of, and my searches aren't returning anything useful. Hitting me with a clue-stick is quite welcome. :-) I'm working on a site where all of the users already have SSL certs identifying themselves installed in their browser (for a different site, same project). I'd like to have Apache handle the messy SSL bits, and Apache already provides me with the directives needed to do this, including authenticating the cert by checking the its signature against the signer's CA. Apache also provides a whole slew of environment variables, on a per-request basis, for exactly this. [1] I'm then planning on examining what of the authentication modules I can steal^H^H^H^H^Hliberate to do client authentication based on what apache is saying. I'm using mod_fcgid as that's what is packaged with Fedora. These variables don't seem to be passed on through to the app. My questions: 1) Is there a way I can get at these SSL_* environment varialbes, on a per-request basis, from my app? 2) It looks to me like the only sane way to do this is to patch mod_fcgid to pass the SSL_* vars through as headers. (e.g. SSL_CLIENT_VERIFY becomes x-ssl_client_verify -- and does the whole "prepend x-" seem sane?) (This works, and I have such a patch.) 3) ...or, maybe, use some mod_rewrite incantation that's eluded me so far, though I'm unsure mod_fcgid passes env variables through at all. 4) Is there something I'm missing/overlooking here? Does Catalyst::Engine::FastCGI stash the passed %env somewhere? Or is there some other way I can get at it? Thanks- -Chris [1] http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#envvars -- Chris Weyl Ex astris, scientia ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst and Taint?
On Tue, Jul 22, 2008 at 8:30 PM, Matt S Trout <[EMAIL PROTECTED]> wrote: > On Mon, Jul 21, 2008 at 10:08:11PM -0700, Chris Weyl wrote: >> Hey all -- >> >> A google of "catalyst taint" turns up this message: >> >> http://lists.scsys.co.uk/pipermail/catalyst/2005-December/004007.html >> >> It doesn't look like there has been a release of >> Module::Pluggable::Fast since then. Does anyone know where this patch >> lurks? :-) (Assuming, of course, that this is still the right path to >> work down.) > > We don't even use Module::Pluggable::Fast anymore. Catalyst went back to > a refactored plain Module::Pluggable instead for 5.70+. Hopefully the > patch claco sent back then got applied somewhere in the meantime. > > Before caring about a three year old message, first check the module > it refers to is even involved anymore :) I'll keep that in mind :) According to CPAN, Module::Pluggable::Fast hasn't been updated since 16 Dec 2005, about 2 weeks before that email was sent If it was applied, I rather suspect it wasn't there. > (and since you're the only person since to mention taint mode, I don't > think most people care about it - I certainly don't see it being very > useful for Catalyst code, maybe you could enlighten us as to why you > do?) Taint mode would seem to be a good way to help protect against accidental exposures, especially in internet-facing apps. I was curious to see what would happen if I tried running an instance with -T... Admittedly, I'm more of a newbie Catalyst user than internals person by any measure, but is there something about Catalyst that renders taint unnecessary, or moot? ...or obsolete? ...or more of a pain than it's worth? -Chris -- Chris Weyl Ex astris, scientia ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] Catalyst and Taint?
Hey all --
A google of "catalyst taint" turns up this message:
http://lists.scsys.co.uk/pipermail/catalyst/2005-December/004007.html
It doesn't look like there has been a release of
Module::Pluggable::Fast since then. Does anyone know where this patch
lurks? :-) (Assuming, of course, that this is still the right path to
work down.)
Thanks-
-Chris
--
Chris Weyl
Ex astris, scientia
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
On Tue, Apr 29, 2008 at 10:02 AM, Peter Corlett <[EMAIL PROTECTED]> wrote: > On Tue, Apr 29, 2008 at 11:34:57AM -0500, Jonathan Rockway wrote: > > * On Tue, Apr 29 2008, Peter Corlett wrote: > [...] > > >> Right, and I need to read the entire Linux and libc source code to be > >> able to write a Unix application. > > It will help, yes. > > It may well help, but it is not necessarily the best approach. The source > code to a library is too low-level for a user of the library to really get a > grip on how all the pieces fit together and are intended to be used. Perhaps oddly, with Perl I've often found reading the _tests_ to be more helpful than wading through the source of a library, particularly if it builds on top of other code. (Of course, this presupposes a good test suite, but...) -Chris -- Chris Weyl Ex astris, scientia ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
