Hi Everybody, Happy new year.
I would leave some advances on poetry packaging. >From the missing dependencies we have: * poetry-core in NEW [0] * pastel in NEW need for clikit [1] * pylev in NEW need for clikit [2] * crashtest has RFS need for clikit [3] * clikit is ready on salsa but waiting for crashtest before RFS [4] * cleo ready but waiting for clikit [5] * shellingham not ready nor ITP yet. * poetry some advances on salsa [6] For experience in the other packages (pylev, paste, etc) and for recommendation of DDs, poetry package use upstream github repository where we have important things like tests. I was looking and exist lot of setup.py that makes me think that we will need repack the upstream package. I will continue working on it but after my reset week, I will be offline until 9 january Thanks Cheers, Emmanuel [0] https://ftp-master.debian.org/new/poetry-core_1.0.0-1.html [1] https://ftp-master.debian.org/new/pastel_0.2.1-1.html [2] https://ftp-master.debian.org/new/pylev_1.2.0-1.html [3] https://lists.debian.org/debian-python/2020/12/msg00061.html [4] https://salsa.debian.org/python-team/packages/crashtest [5] https://salsa.debian.org/python-team/packages/cleo [6] https://salsa.debian.org/python-team/packages/poetry On Fri, Dec 4, 2020 at 6:36 PM Emmanuel Arias <eam...@yaerobi.com> wrote: > Hi everyone, > > After read [0] and thinking about it, IMO the best solution is try to > package python-poetry, > and its dependencies. I make a very simple (and probably wrong) script [1] > to verify the > package that will be need package into Debian, before poetry package. > > [{'name': 'cleo'}, {'name': 'clikit'}, {'name': 'crashtest'}, {'name': > 'shellingham'}, {'name': 'pastel'}, {'name': 'pylev'}] > > Please feel free to ITP them :) > > [0] https://github.com/python-poetry/poetry/issues/2346 > [1] https://github.com/eamanu/pydebdep > > On Sun, Nov 22, 2020 at 11:03 AM Emmanuel Arias <eam...@yaerobi.com> > wrote: > >> Hi everyone, >> >> In the last week I re-take this work. >> >> But, we need to discuss the poetry situation. First of all, poetry >> upstream doesn't consider >> adding vendor libs to the source. They have their reasons about this >> situation. I recommend >> you read this [0] [1]. >> >> The problem here, is that poetry need some dependencies that are not in >> Debian yet, >> and that dependencies have more dependencies (not in Debian). >> >> Here there're some possibilities that from my point of view we can >> follow. >> If you read [0] @abn recommend use `sonnet` script to build poetry >> but is not maintained. In the other hand we can can try to package >> poetry-core >> that is a more pip similar case with the vendor libs. >> >> In this week I want to make some tests using `sonnet` and look poetry-core >> with the aim to package poetry before freezing Debian. >> >> I can send you (not today) the list of the dependencies that will be need >> package if we want poetry in Debian. >> >> This is my analysis about poetry (from a not so experienced DM) I will >> happy to listen to more experienced people about this, and if you consider >> correct that I mention, please. >> >> Thanks! >> >> [0] https://github.com/python-poetry/poetry/issues/2607 >> [1] https://github.com/python-poetry/poetry/issues/2346 >> >> >> Cheers, >> Arias Emmanuel >> @eamanu >> yaerobi.com >> >> >> On Thu, Nov 19, 2020 at 12:16 PM Bastian Venthur <vent...@debian.org> >> wrote: >> >>> Hi, >>> >>> I see some updates on the salsa repository, any chance we can get this >>> package ready before the next freeze so we'll have it in the next stable >>> release? >>> >>> >>> Cheers, >>> >>> Bastian >>> >>> On 29.06.20 06:04, Scott Kitterman wrote: >>> > >>> > >>> > On June 29, 2020 3:08:53 AM UTC, Emmanuel Arias <eam...@yaerobi.com> >>> wrote: >>> >> Hi, >>> >> >>> >> I'm working on poetry packaging, I created on salsa de repository [0]. >>> >> >>> >> Note that there are many packages that are not in Debian like cachy, >>> >> cleo, >>> >> etc. >>> >> >>> >> I RFS python-cachy [1] and now I'm working on cleo, which depends on >>> >> clikit >>> >> that is not on Debian (if I search correctly). >>> >> >>> >> Bastian Venthur note me that pienv, pip have vendors folder with the >>> >> dependencies >>> >> but looking on poetry that _vendor folder is empty. >>> >> >>> >> So, looking for I more experienced opinion, do you think that we would >>> >> try >>> >> convince >>> >> to upstream to make available vendors on the release (if that is >>> >> necessary) >>> >> or >>> >> we need to package all the missing dependencies? >>> > >>> > Definitely they should be packaged. >>> > >>> > At least for pip none of the vendored libs are used in Debian's >>> package. Fortunately upstream supports use of system libs with only minor >>> patching. >>> > >>> > Scott K >>> > >>> > >>> >>> >>> -- >>> Dr. Bastian Venthur http://venthur.de >>> Debian Developer venthur at debian org >>> >>>
