Skip Menu |
 

This queue is for tickets about the Moose CPAN distribution.

Report information
The Basics
Id: 85157
Status: rejected
Priority: 0/
Queue: Moose

People
Owner: Nobody in particular
Requestors: pablo [...] pablo.com.mx
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



From pablo [...] pablo.com.mx Thu May 9 12: 32:38 2013
MIME-Version: 1.0
X-Spam-Status: No, score=-6.899 tagged_above=-99.9 required=10 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
X-Spam-Flag: NO
Content-Type: multipart/alternative; boundary="089e013cb81a6da8a604dc4b986c"
Message-ID: <CAJRPuoynjW1YENw27Far0WcMcrT=akrobj=ayqqe+CGZPjcoPw [...] mail.gmail.com>
X-Received: by 10.60.131.6 with SMTP id oi6mr4560172oeb.19.1368117144818; Thu, 09 May 2013 09:32:24 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
X-Spam-Score: -6.899
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id CA7E62409A4 for <cpan-bug+Class-MOP [...] hipster.bestpractical.com>; Thu, 9 May 2013 12:32:38 -0400 (EDT)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-sqtuyC5PzT for <cpan-bug+Class-MOP [...] hipster.bestpractical.com>; Thu, 9 May 2013 12:32:37 -0400 (EDT)
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id 03A5C2409A3 for <bug-Class-MOP [...] rt.cpan.org>; Thu, 9 May 2013 12:32:36 -0400 (EDT)
Received: (qmail 1288 invoked by alias); 9 May 2013 16:32:36 -0000
Received: from mail-oa0-f54.google.com (HELO mail-oa0-f54.google.com) (209.85.219.54) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Thu, 09 May 2013 09:32:29 -0700
Received: by mail-oa0-f54.google.com with SMTP id j1so3670458oag.27 for <bug-Class-MOP [...] rt.cpan.org>; Thu, 09 May 2013 09:32:25 -0700 (PDT)
Received: by 10.182.106.5 with HTTP; Thu, 9 May 2013 09:32:24 -0700 (PDT)
Delivered-To: cpan-bug+Class-MOP [...] hipster.bestpractical.com
Subject: Warnings when using with latest version of Package::Stash
Return-Path: <pablo [...] pablo.com.mx>
X-RT-Mail-Extension: class-mop
X-Original-To: cpan-bug+Class-MOP [...] hipster.bestpractical.com
X-Spam-Check-BY: la.mx.develooper.com
X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=03lcgkkXNtEwuONJD3UOYdExp/vjeLsSMLWYoywHQ+g=; b=dSAGbKj3B35nFbdf7Ql+qgX1Wo1exG/9OqtSu0jWIe/8WDkjdjl6DpSSgN4jbRSUHk 5EfyTYEYQ6uAszGIlPb4bcwi8gdQZ0duRPXtaTtiLOR3/A1XGlvRYs2oMgl/vlG0vdV5 LOSkp0usxAa76nj9mDTY06PMV/DUsuf3i9tJiHPxfjtD0MmE7WifvTlJFSzVK4yqWIZS WUbETvE/AxzYUOooqV3TAeJYQY68wWEfnhNjbjrwaKiCkFEIQqPXS8FAsx6sSvMFx3q1 1Q8dPsxW71P/4V5xCsWaGMMsXyxgItOXdAAbts7qIMdoM8LPJLFeadGyE4O6CIAMhiQF BB3g==
Date: Thu, 9 May 2013 09:32:24 -0700
X-Spam-Level:
To: bug-Class-MOP [...] rt.cpan.org
X-GM-Message-State: ALoCoQlWgIh/LaNIjnKhColjOAjLdSHONkG3s3QATEyOfqSG0JQNdohvdTWqdre8nGmpUQbgfmUN
From: Pablo Fischer <pablo [...] pablo.com.mx>
X-RT-Interface: Email
Content-Length: 0
content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: iso-8859-1
Content-Length: 1099
Hello, One of the applications I've has a dependency in Moose, moose has a dependency on Class::MOP.. Class::MOP depends on Package::Stash 0.13 or higher. The latest version of Package::Stash (pushed to cpan on 04/Jan/2013 has a list of deprecated calls that are still in Class::MOP. Can Class::MOP::Package be fixed so it can work with newest version of Package::Stash (deprecated calls) and with the old one? Package::Stash::get_or_add_package_symbol('Package::Stash=HASH(0xa01aee0)', 'HASH(0xa01acc4)') called at perl/5.10/i686-linux-thread-multi-64int-ld/Class/MOP/Package.pm line 128 Class::MOP::Package::get_or_add_package_symbol('Class::MOP::Class=HASH(0xa01ad64)', 'HASH(0xa01acc4)') called at perl/5.10/i686-linux-thread-multi-64int-ld/Class/MOP/Class.pm line 836 From code of Package::Stash: http://cpansearch.perl.org/src/DOY/Package-Stash-0.34/lib/Package/Stash.pm sub get_or_add_package_symbol { deprecated('get_or_add_package_symbol is deprecated, please use get_or_add_symbol'); shift->get_or_add_symbol(@_); } Thanks! -- Pablo Fischer (pablo [arroba/at] pablo.com.mx)
content-type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: iso-8859-1
Content-Length: 1593
MIME-Version: 1.0
In-Reply-To: <CAJRPuoynjW1YENw27Far0WcMcrT=akrobj=ayqqe+CGZPjcoPw [...] mail.gmail.com>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <CAJRPuoynjW1YENw27Far0WcMcrT=akrobj=ayqqe+CGZPjcoPw [...] mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.12-14311-1368121757-1986.85157-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 825
Download (untitled) / with headers
text/plain 825b
On 2013-05-09 09:32:39, pablo@pablo.com.mx wrote: Show quoted text
> Hello, > > One of the applications I've has a dependency in Moose, moose has a > dependency on Class::MOP.. Class::MOP depends on Package::Stash 0.13 > or > higher. The latest version of Package::Stash (pushed to cpan on > 04/Jan/2013 > has a list of deprecated calls that are still in Class::MOP. > > Can Class::MOP::Package be fixed so it can work with newest version of > Package::Stash (deprecated calls) and with the old one?
Can you clarify the problem? Is it problematic for you to upgrade to the latest Package::Stash? Class::MOP is not calling any deprecated methods in Package::Stash. However, a quick grep of the codebase can appear as if it is, because some of the method names in Class::MOP::Package are the same as some of these deprecated methods in PS.
MIME-Version: 1.0
In-Reply-To: <rt-4.0.12-14311-1368121757-1986.85157-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <CAJRPuoynjW1YENw27Far0WcMcrT=akrobj=ayqqe+CGZPjcoPw [...] mail.gmail.com> <rt-4.0.12-14311-1368121757-1986.85157-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.12-21375-1368122039-1408.85157-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 1120
On Thu May 09 13:49:17 2013, ETHER wrote: Show quoted text
> On 2013-05-09 09:32:39, pablo@pablo.com.mx wrote:
> > Hello, > > > > One of the applications I've has a dependency in Moose, moose has a > > dependency on Class::MOP.. Class::MOP depends on Package::Stash 0.13 > > or > > higher. The latest version of Package::Stash (pushed to cpan on > > 04/Jan/2013 > > has a list of deprecated calls that are still in Class::MOP. > > > > Can Class::MOP::Package be fixed so it can work with newest version
> of
> > Package::Stash (deprecated calls) and with the old one?
> > Can you clarify the problem? Is it problematic for you to upgrade to > the latest Package::Stash?
Problem is with a _LOT_ of warnings and not sure if there would be a (bigger) potential problem with a future version of Package::Stash that totally removes these methods. Show quoted text
> > Class::MOP is not calling any deprecated methods in Package::Stash. > However, a quick grep of the codebase can appear as if it is, > because some of the method names in Class::MOP::Package are the > same as some of these deprecated methods in PS.
Yep, that's correct.
MIME-Version: 1.0
In-Reply-To: <CAJRPuoynjW1YENw27Far0WcMcrT=akrobj=ayqqe+CGZPjcoPw [...] mail.gmail.com>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <CAJRPuoynjW1YENw27Far0WcMcrT=akrobj=ayqqe+CGZPjcoPw [...] mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.12-14311-1368122244-1202.85157-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 395
Download (untitled) / with headers
text/plain 395b
Moose does not have a dependency on Class::MOP - Class::MOP was moved into the Moose distribution several years ago. The separate Class::MOP distribution on CPAN is historical and should not be used. The latest version of Moose depends on Package::Stash 0.32, and the Class::MOP that is shipped with the latest version of Moose does not contain any calls to deprecated methods in Package::Stash.
MIME-Version: 1.0
In-Reply-To: <rt-4.0.12-14311-1368122244-1202.85157-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <CAJRPuoynjW1YENw27Far0WcMcrT=akrobj=ayqqe+CGZPjcoPw [...] mail.gmail.com> <rt-4.0.12-14311-1368122244-1202.85157-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.12-13306-1368123117-1809.85157-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 621
Download (untitled) / with headers
text/plain 621b
On Thu May 09 13:57:24 2013, DOY wrote: Show quoted text
> Moose does not have a dependency on Class::MOP - Class::MOP was moved > into the Moose distribution several years ago. The separate > Class::MOP distribution on CPAN is historical and should not be > used. The latest version of Moose depends on Package::Stash 0.32, > and the Class::MOP that is shipped with the latest version of Moose > does not contain any calls to deprecated methods in Package::Stash.
I think that explains it =/ Just found out I had that old version that depends on Class-MOP =/. I'll need to upgrade (this is a veryyyyy old app, that's why)


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.