Path: csiph.com!eternal-september.org!reader02.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: Emmanuel Arias Newsgroups: linux.debian.maint.python Subject: Re: Asking for help Poetry Date: Thu, 27 May 2021 03:40:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu May 27 01:33:26 2021 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.88 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FOURLA=0.1, HTML_MESSAGE=2, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .yaerobi. - helo: .mail-wm1-x336.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Gm-Message-State: AOAM533pBOAiVAuyLsR109ignB8PzWSpwHxH10QJacN4qLjFLcnvQJ85 sEboyk/0fM21K4F1styDxiUV8IZq1sR7QXi+5Hhxcg== X-Google-SMTP-Source: ABdhPJy7t1UYBMIj1hbh8kwTJF0D+N18x/JgeUpf5amZxMc6ns0jwYY531ojYOAJ4IeH66GVFrX2q5aM43EPdRLm9n4= X-Received: by 2002:a1c:e205:: with SMTP id z5mr4594887wmg.70.1622079187063; Wed, 26 May 2021 18:33:07 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000be2b0205c345bda0" X-Mailing-List: archive/latest/19196 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAFNO5ofG1+u19XXqDa--gQ2KwyKUzakm1wU0pVEk=ZryvjuOqw@mail.gmail.com Approved: robomod@news.nic.it Lines: 227 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python X-Original-Date: Wed, 26 May 2021 22:32:56 -0300 X-Original-Message-ID: X-Original-References: <955fe2f6-d5c0-bc76-803c-3a3e047ab1e7@yaerobi.com> Xref: csiph.com linux.debian.maint.python:13408 --000000000000be2b0205c345bda0 Content-Type: text/plain; charset="UTF-8" Hello Everybody, I left some advances on poetry. Happily (from my point of view) we are near to having poetry packaged. I've just push some new commits to salsa [0]. After spend several times with the tests (see patches), we just have two test that still fail (I didn't looking it yet): tests/installation/test_pip_installer.py - fail one unit test tests/utils/test_env.py - fail several unit tests. To build poetry, you will also need to build locally python3-cleo still in NEW [1], python-httpretty 1.0.5: I prepare a new upstream release and a member of OpenStack sponsored its to experimental (thanks Michal Arbet) [2] and pkginfo 1.7.0, I ping @jandd on #debian-python for a new upstream release packaging, but if I haven't got news about it these days, I will push my work and I'll ask for sponsorship. [0] https://salsa.debian.org/python-team/packages/poetry [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958366 [2] https://tracker.debian.org/news/1241115/accepted-python-httpretty-105-01-source-into-experimental/ Cheers, Emmanuel On Tue, May 11, 2021 at 8:55 AM Emmanuel Arias wrote: > Hello! > > On 5/11/21 1:25 AM, Sandro Tosi wrote: > > On Sat, May 8, 2021 at 9:56 PM Emmanuel Arias > wrote: > >> On 5/8/21 10:37 PM, Sandro Tosi wrote: > >>> On Mon, Mar 15, 2021 at 10:29 AM Emmanuel Arias > wrote: > >>>> On Mon, Mar 15, 2021 at 4:22 AM Sandro Tosi wrote: > >>>>>> * poetry-core failing https://ci.debian.net/packages/p/poetry-core/ > >>>>> are you handling this failure? > >>> looks like this is fixed in git: do you need a sponsor? > >> Yes, please. Thanks! > > sounds good, i'll have a look at this package soon and let you know > Thanks! > > > >>>>>> * python-cleo in review > https://salsa.debian.org/python-team/packages/cleo I hope finished this > week > >>> stefanor uploaded it a few days ago > >> Yes. > >>>>>> * poetry still in progress > https://salsa.debian.org/python-team/packages/poetry -> need help and > reviews > >>> for this one it looks like you imported a new upstream release a week > >>> ago: is there something we can help/check about poetry? > >> I've just push some advances. Currently, I'm working on tests, if you > >> want to take a look. > > maybe just ask here (or directly to me) if you have questions and > > what's failing/needs work, so we dont duplicate work > ok! > > > >> We need new upstream release for python-httpretty (for tests), that I > >> upload to mentors [0]. @zigo ask me about test that this new upstream > >> release doesn't break > >> cloud-init and python3-scciclient (I would like to take a look to ratt > >> for that). > > ratt is pretty great, and rather simple to use: > > > > - setup a sbuild schroot for unstable > > - build a binary package from the source you're working on > > - `ratt _amd64.changes` > > > > and then you'll get on screen the results for each package + a > > directory with the build results and logs > > > > https://github.com/Debian/ratt > > > > keep in mind it rebuilds packages sequentially, so it can take some > > time if the number of reverse deps is high. > > Thanks for the advice! > > > > >> Perhaps a good help from a more experienced person would be check if all > >> is ok with DFSG,that's my biggest concern. > > for which package specifically? while it's boring and long work, it's > > also rather trivial: look at every single file (yep, all of them) from > > the upstream source, and document their copyright and license in > > d/copyright -- happy to answer questions if you have something > > specific in mind about this > > Thanks, I hope have more news at the finish of the week > > Cheers! > > > > > > Regards, > --000000000000be2b0205c345bda0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Everybody,
<= br>
I left some advances on poetry. Happily (from my point of vie= w) we are near to
having poetry packaged. I've just push some= new commits to salsa [0].

After spend several tim= es with the tests (see patches), we just have two
test that still= fail (I didn't looking it yet):

tests/install= ation/test_pip_installer.py - fail one unit test
tests/utils/test_env.py -=C2=A0 fail several unit tests.

To build poetry, you will also need to build locally python3-cleo still i= n NEW [1], python-httpretty 1.0.5:
I prepare a new upstream relea= se and a member of OpenStack sponsored its=C2=A0 to
experimental = (thanks=C2=A0Michal Arbet) [2] and pkginfo 1.7.0, I ping @jandd on #debian-= python
for a new upstream=C2=A0release packaging, but if I haven&= #39;t got news about it these days, I will push=C2=A0
my work and= I'll ask for sponsorship.=C2=A0

Cheers,=C2=A0
Emmanuel

On Tue, May 11, 2021 at 8:55 A= M Emmanuel Arias <eamanu@yaerobi.c= om> wrote:
eamanu@yaerobi.com> wrote:
>> On 5/8/21 10:37 PM, Sandro Tosi wrote:
>>> On Mon, Mar 15, 2021 at 10:29 AM Emmanuel Arias <eamanu@yaerobi.com> wr= ote:
>>>> On Mon, Mar 15, 2021 at 4:22 AM Sandro Tosi <morph@debian.org> wrote:=
>>>>>> * poetry-core failing https://= ci.debian.net/packages/p/poetry-core/
>>>>> are you handling this failure?
>>> looks like this is fixed in git: do you need a sponsor?
>> Yes, please. Thanks!
> sounds good, i'll have a look at this package soon and let you kno= w
Thanks!
>
>>>>>> * python-cleo in review h= ttps://salsa.debian.org/python-team/packages/cleo I hope finished this = week
>>> stefanor uploaded it a few days ago
>> Yes.
>>>>>> * poetry still in progress https://salsa.debian.org/python-team/packages/poetry -> need hel= p and reviews
>>> for this one it looks like you imported a new upstream release= a week
>>> ago: is there something we can help/check about poetry?
>> I've just push some advances. Currently, I'm working on te= sts, if you
>> want to take a look.
> maybe just ask here (or directly to me) if you have questions and
> what's failing/needs work, so we dont duplicate work
ok!
>
>> We need new upstream release for python-httpretty (for tests), tha= t I
>> upload to mentors [0]. @zigo ask me about test that this new upstr= eam
>> release doesn't break
>> cloud-init and python3-scciclient (I would like to take a look to = ratt
>> for that).
> ratt is pretty great, and rather simple to use:
>
> - setup a sbuild schroot for unstable
> - build a binary package from the source you're working on
> - `ratt <file>_amd64.changes`
>
> and then you'll get on screen the results for each package + a
> directory with the build results and logs
>
> https://github.com/Debian/ratt
>
> keep in mind it rebuilds packages sequentially, so it can take some > time if the number of reverse deps is high.

Thanks for the advice!

>
>> Perhaps a good help from a more experienced person would be check = if all
>> is ok with DFSG,that's my biggest concern.
> for which package specifically? while it's boring and long work, i= t's
> also rather trivial: look at every single file (yep, all of them) from=
> the upstream source, and document their copyright and license in
> d/copyright -- happy to answer questions if you have something
> specific in mind about this

Thanks, I hope have more news at the finish of the week

Cheers!


>
> Regards,
--000000000000be2b0205c345bda0--