Skip Menu |
 

This queue is for tickets about the Coat-Persistent CPAN distribution.

Report information
The Basics
Id: 94947
Status: open
Priority: 0/
Queue: Coat-Persistent

People
Owner: Nobody in particular
Requestors:
Cc:
AdminCc:

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



MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
From: dam [...] cpan.org
Subject: [PATCH] missing whatis entries
X-RT-Interface: REST
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
Content-Length: 432
Download (untitled) / with headers
text/plain 432b
In Debian we are currently applying the attached patch to Coat-Persistent. We thought you might be interested in it too. Subject: Add missing whatis entries From: Ansgar Burchardt <ansgar@43-1.org> Date: Sat, 20 Jun 2009 10:49:15 +0200 This patch adds a missing whatis entry for lib/Coat/Persistent/Types.pm and fixes the whatis entry in lib/Coat/Persistent/Types/MySQL.pm. Thanks in advance, Damyan Ivanov, Debian Perl Group
X-RT-Interface: REST
MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Type: multipart/mixed; boundary="----------=_1398227392-5030-0"
Content-Transfer-Encoding: binary
RT-Message-ID: <rt-4.0.18-5030-1398227392-541.94947-0-0 [...] rt.cpan.org>
Content-Length: 0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 17
Here's the patch.
Content-Type: text/plain; charset="utf-8"; name="whatis-entries.patch"
Content-Disposition: attachment; filename="whatis-entries.patch"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
Content-Length: 829

Message body is not shown because sender requested not to inline it.

MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-5030-1398227392-541.94947-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-5030-1398227392-541.94947-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-19127-1398258550-1555.94947-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: 381
Download (untitled) / with headers
text/plain 381b
On Wed Apr 23 00:29:52 2014, DAM wrote: Show quoted text
> Here's the patch.
This module is completely deprecated. We don't know of anyone who actually uses it, nor would we recommend ever touching it. One should use either Moo or Moose and get off this package as soon as possible. We have no intention of supporting it at all. Would it be possible to deprecate this package in Debian as well?
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-19127-1398258550-1555.94947-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-5030-1398227392-541.94947-0-0 [...] rt.cpan.org> <rt-4.0.18-19127-1398258550-1555.94947-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-21374-1398259654-1129.94947-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: 974
Download (untitled) / with headers
text/plain 974b
On Wed Apr 23 09:09:10 2014, xsawyerx wrote: Show quoted text
> On Wed Apr 23 00:29:52 2014, DAM wrote:
> > Here's the patch.
> > This module is completely deprecated. We don't know of anyone who > actually uses it, nor would we recommend ever touching it.
Don't use "We" when you mean "I" ... I know of some code that use it. Show quoted text
> > One should use either Moo or Moose and get off this package as soon as > possible.
That is true but the documentation already states that, and that's not the point of this ticket Show quoted text
> > We have no intention of supporting it at all.
Again, "you" may have no intention of supporting it. I'm happy to provide minimal maintenance to it. Show quoted text
> > Would it be possible to deprecate this package in Debian as well?
That's a good idea. @Dam: I'll merge your patch and release soon. As sawyer suggests, do you have anything depending on Coat ? I suspect so, if you still have it, but it's worth double-checking. If not, can it be deprecated at some point ? dams.
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-21374-1398259654-1129.94947-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-5030-1398227392-541.94947-0-0 [...] rt.cpan.org> <rt-4.0.18-19127-1398258550-1555.94947-0-0 [...] rt.cpan.org> <rt-4.0.18-21374-1398259654-1129.94947-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-30681-1398260120-284.94947-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: 1421
Download (untitled) / with headers
text/plain 1.3k
On Wed Apr 23 09:27:34 2014, DAMS wrote: Show quoted text
> > On Wed Apr 23 09:09:10 2014, xsawyerx wrote:
> > On Wed Apr 23 00:29:52 2014, DAM wrote:
> > > Here's the patch.
> > > > This module is completely deprecated. We don't know of anyone who > > actually uses it, nor would we recommend ever touching it.
> > Don't use "We" when you mean "I" ... I know of some code that use it.
Okay. *I for the first case, at least 70% of "we" in second case. Better? Show quoted text
> > One should use either Moo or Moose and get off this package as soon > > as > > possible.
> > That is true but the documentation already states that, and that's not > the point of this ticket
I never said it was the point of this ticket, nor did I think that. Show quoted text
> > We have no intention of supporting it at all.
> > Again, "you" may have no intention of supporting it. I'm happy to > provide minimal maintenance to it.
Considering this was Alexis' project, and I talked to him about it a long time ago, he said he has no intention of supporting it. He added me so I could add the deprecation notice. I am also unaware of you agreeing to provide minimal maintenance as a policy of the project, so there's little point in flogging me for stating what the policy of the author is, since what it is contradicting is only your personal offer for assistance. Show quoted text
> > Would it be possible to deprecate this package in Debian as well?
> > That's a good idea.
Thank you.
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-30681-1398260120-284.94947-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-5030-1398227392-541.94947-0-0 [...] rt.cpan.org> <rt-4.0.18-19127-1398258550-1555.94947-0-0 [...] rt.cpan.org> <rt-4.0.18-21374-1398259654-1129.94947-0-0 [...] rt.cpan.org> <rt-4.0.18-30681-1398260120-284.94947-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-15365-1398260809-130.94947-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: 1575
Download (untitled) / with headers
text/plain 1.5k
On Wed Apr 23 09:35:20 2014, xsawyerx wrote: Show quoted text
> On Wed Apr 23 09:27:34 2014, DAMS wrote:
> > > > On Wed Apr 23 09:09:10 2014, xsawyerx wrote:
> > > On Wed Apr 23 00:29:52 2014, DAM wrote:
> > > > Here's the patch.
> > > > > > This module is completely deprecated. We don't know of anyone who > > > actually uses it, nor would we recommend ever touching it.
> > > > Don't use "We" when you mean "I" ... I know of some code that use it.
> > > Okay. *I for the first case, at least 70% of "we" in second case. > Better?
yes :) Show quoted text
>
> > > We have no intention of supporting it at all.
> > > > Again, "you" may have no intention of supporting it. I'm happy to > > provide minimal maintenance to it.
> > > Considering this was Alexis' project, and I talked to him about it a > long time ago, he said he has no intention of supporting it. He added > me so I could add the deprecation notice.
Later on, he gave me COMAINT so I could fix a critical bug in it, and provide minimal maintenance. Hence my last release. Show quoted text
> > I am also unaware of you agreeing to provide minimal maintenance as a > policy of the project,
Wel, me doing the last release should be a good hint :) Show quoted text
> so there's little point in flogging me for > stating what the policy of the author is, since what it is > contradicting is only your personal offer for assistance.
Sorry, I didn't mean to "flog" you, just to point out that as comaint, I had a different opinion and position than what you were stating as The Truth. Including me into it (by using "we") was what triggered my will to speak for myself.
MIME-Version: 1.0
In-Reply-To: <rt-4.0.18-15365-1398260809-130.94947-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-4.0.18-5030-1398227392-541.94947-0-0 [...] rt.cpan.org> <rt-4.0.18-19127-1398258550-1555.94947-0-0 [...] rt.cpan.org> <rt-4.0.18-21374-1398259654-1129.94947-0-0 [...] rt.cpan.org> <rt-4.0.18-30681-1398260120-284.94947-0-0 [...] rt.cpan.org> <rt-4.0.18-15365-1398260809-130.94947-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-21374-1398261306-1887.94947-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: 73
And actually the code from github and CPAN have diverged. Will merge them


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.