W nawiązaniu do strony

Dzień dobry, reprezentuję firmę zajmującą się budową nowoczesnych Stron i Sklepów Online. Z przyjemnością podeślę naszą aktualną propozycję w tym zakresie. Jeśli mogę, proszę o e-mail zwrotny o treści TAK. ... Z wyrazami szacunku Strony i Sklepy Internetowe

Re: ML-Policy and tesseract-ocr

[Debian list policy is to reply to list without CC to individuals, except where the individual has asked for a CC.] For the rest of your reply, I agree with Sam's response (i.e. no Suggests is necessary). ...Marvin * Mo Zhou [190812 20:29]: > > The source package would need to Build-Depend on t

Re: ML-Policy and tesseract-ocr

On Tue, Aug 13, 2019 at 8:45 AM Sam Hartman wrote: > In cases where the model is not recreated, but where software in Debian > could create the model, I think a README file is better than a package > relationship. Personally, I'd like to see Policy specify a standard mechanism that people could u

Re: ML-Policy and tesseract-ocr

> "Mo" == Mo Zhou writes: >> (result of running the training program with specific input data, >> if I understand correctly?) Mo> Yes, correct. >> The source package would need to Build-Depend on the training >> program and its inputs, but in general there would not nee

Re: ML-Policy and tesseract-ocr

Hi Marvin, On 2019-08-12 18:35, Marvin Renich wrote: > * Mo Zhou [190812 10:31]: >> To this end, I wrote the policy #5 [3]: >> >>A package that includes a machine learning model, must also include >>the corresponding training program, or depend on the package that >> provides >>the co

Re: Why keep upstream sources in Git at salsa.d.o?

Am Montag, den 12.08.2019, 19:53 +0200 schrieb Marc Haber: > On Sun, 11 Aug 2019 15:03:51 +0200, Daniel Leidert > wrote: > > Am Sonntag, den 11.08.2019, 01:55 +0800 schrieb Drew Parsons: > > > Upstreams are starting to use git lfs in their git repos. In some cases > > > the git-lfs references fi

Bug#934641: ITP: python-timeline -- Timeline module for modelling a series of actions

Package: wnpp Severity: wishlist Owner: Colin Watson * Package name: python-timeline Version : 0.0.6 Upstream Author : Canonical Ltd. * URL : https://launchpad.net/python-timeline * License : LGPL-3 Programming Lang: Python Description : Timeline module

Re: how to handle upstream orig tarball with git-lfs reference files?

On Mon, 12 Aug 2019, Andrej Shadura wrote: > Hi, > > On Sun, 11 Aug 2019 at 14:57, Daniel Leidert wrote: > > > > Am Sonntag, den 11.08.2019, 07:26 +0200 schrieb Andrej Shadura: > > > On Sun, 11 Aug 2019, 04:18 Drew Parsons, wrote: > > > > We have the policy of not pulling files from the interne

Re: ML-Policy and tesseract-ocr

* Mo Zhou [190812 10:31]: > To this end, I wrote the policy #5 [3]: > >A package that includes a machine learning model, must also include >the corresponding training program, or depend on the package that > provides >the corresponding training program. > > Does that make sense? If i

Re: Why keep upstream sources in Git at salsa.d.o? (was: how to handle upstream orig tarball with git-lfs reference files?)

On Sun, 11 Aug 2019 15:03:51 +0200, Daniel Leidert wrote: >Am Sonntag, den 11.08.2019, 01:55 +0800 schrieb Drew Parsons: >> Upstreams are starting to use git lfs in their git repos. In some cases >> the git-lfs references files are retained in the source tarball, not >> replacing the reference

ML-Policy and tesseract-ocr

Hi -devel, src:tesseract-ocr has two concrete bugs that are associated to ML-Policy[1]. Let's discuss about the possible solution. BTW, today I drew a diagram[2] for the ML-Policy. Those who don't bother to read the full text could have a look at the diagram. -- #933878: training files are split

Bug#934596: ITP: postgresfixture -- Python fixture for creating PostgreSQL clusters and databases

Package: wnpp Severity: wishlist Owner: Colin Watson * Package name: postgresfixture Version : 0.4.1 Upstream Author : Gavin Panella * URL : https://launchpad.net/postgresfixture * License : AGPL-3.0 Programming Lang: Python Description : Fixture for cr