[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#842160: RFS: python-memory-profiler/0.40-1 [RC]



Control: tag -1 - moreinfo
Control: retitle -1 RFS: python-memory-profiler/0.41+git20161018-1 [RC]

2016-10-29 2:35 GMT+09:00 Mattia Rizzolo <mattia@debian.org>:
> Control: tag -1 moreinfo
> Control: owner -1 !
>
> On Wed, Oct 26, 2016 at 10:41:36PM +0900, Changwoo Ryu wrote:
>> I am looking for a sponsor for my package "python-memory-profiler":
>
> sure thing!
>
>> Or you can use the alioth git:
>>
>> https://anonscm.debian.org/git/users/cwryu/python-memory-profiler.git
>
> let's use git indeed.
>
>>
>>   * New upstream release
>>   * debian/*: Clean up the pybuild build (Closes: #804442)
>>   * debian/*: lintian fixes
>>     - Standard-Version: 3.9.8
>>     - Add missing source format
>>     - Use new https addresses for Vcs-* fields
>
> This is broken:
>
> mattia@chase /tmp % git clone https://anonscm.debian.org/users/cwryu/python-memory-profiler.git
> Cloning into 'python-memory-profiler'...
> fatal: repository 'https://anonscm.debian.org/users/cwryu/python-memory-profiler.git/' not found
> 128 mattia@chase /tmp %                                                                                                                                              :(
>
> Furthermore be aware that you can use
> https://anonscm.debian.org/git/users/cwryu/python-memory-profiler.git/
> for both of Vcs-Git and Vcs-Browser.

Got it. Thanks.

> Also, upstream has released 0.41, why not packaging that?  (annoying the
> fact that seems there are no recent tags in github).

0.41 have some issues; missing files, failed testsuite, etc. I'd
rather fetch newer source from upstream git.

Here is the fixed/updated version:

dget -x https://people.debian.org/~cwryu/debian/python-memory-profiler_0.41+git20161018-1.dsc

Or

debian/0.41+git20161018-1 tag in the alioth git
https://anonscm.debian.org/git/users/cwryu/python-memory-profiler.git/


This upstream git version still has some failed testsuites; it is time
consuming to fix those upstream maintenance issues myself so I just
commented out some tests.


Reply to: