On Thu, Jun 09, 2022 at 06:34:20PM +0300, Andrius Merkys wrote:
> Interesting. I maintain a package with ~80 MBs in debian/. But again,
> maybe I will get a REJECT next time it has to clear NEW. It would be
> nice to have a rule of thumb to implement in lintian, but from [5] I
> gather this is not
On 2022-06-08 21:54, Andreas Tille wrote:
>> Or try finding some other dataset that is free and can be used for testing.
> Yes, this would be another option. Hoping for input from busco users
> here.
I have used busco in my research, but not enough to understand the
datasets, alas.
Best,
Hi Andreas,
On 2022-06-07 12:34, Andreas Tille wrote:
> [1] - https://salsa.debian.org/med-team/busco
> [2] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010653
> [3] - https://gitlab.com/ezlab/busco/-/issues/566
Thanks a lot for pushing forward with this. Can you tell me
Am Wed, Jun 08, 2022 at 07:39:08PM +0530 schrieb Nilesh Patra:
> On Wed, Jun 08, 2022 at 05:26:18PM +0530, Mohd Bilal wrote:
> > The upstream responded[1] to my query regarding the license of busco
> > datasets. Looks like it uses a non-free license (CC-BY-ND-4.0).
>
> Aw, crap!
That's a pity.
On Wed, Jun 08, 2022 at 05:26:18PM +0530, Mohd Bilal wrote:
> The upstream responded[1] to my query regarding the license of busco
> datasets. Looks like it uses a non-free license (CC-BY-ND-4.0).
Aw, crap!
> So I think adding this test data would make the package non-free. Seeking
> everyone's
Good Day Team,
The upstream responded[1] to my query regarding the license of busco
datasets. Looks like it uses a non-free license (CC-BY-ND-4.0).
So I think adding this test data would make the package non-free.
Seeking everyone's opinion on what should be done next :)
[1] -
Hi again,
Am Tue, Jun 07, 2022 at 11:34:44AM +0200 schrieb Andreas Tille:
> >
> > Erm. Was not the original intent to wait for the upstream clarification
> > of the license of this data? And what about mention in debian/copyright?
>
> Aaaargh, I was to much concentratet on the second part of
On Tue, Jun 07, 2022 at 10:31:23AM +0300, Andrius Merkys wrote:
> > This is perfectly in line with the request of ftpmaster to keep the
> > debian/ dir "sensibly" small and I'm pretty sure ftpmaster would have
> > been rejected the package if the data[...]
> To me this looks like an intricate
Hi Andrius,
Am Tue, Jun 07, 2022 at 10:31:23AM +0300 schrieb Andrius Merkys:
> >> On 2022-06-06 22:37, Mohd Bilal wrote:
> >>> I have added an autopkgtest for busco[1] as mentioned in bug report[2].
> >>> The license for the test data needs to be added. I have opened an
> >>> issue[3] upstream
Hi Andreas,
On 2022-06-07 09:57, Andreas Tille wrote:
>> On 2022-06-06 22:37, Mohd Bilal wrote:
>>> I have added an autopkgtest for busco[1] as mentioned in bug report[2].
>>> The license for the test data needs to be added. I have opened an
>>> issue[3] upstream asking for clarification.
I compared the size of installed package (apt show busco) with the size of
test data. So thought of adding the test data outside the debian directory as
suggested in the debian med policy[4]
[4] - https://med-team.pages.debian.net/policy/#embedding-large-test-data
Hi Andrius,
Am Tue, Jun 07, 2022 at 09:23:20AM +0300 schrieb Andrius Merkys:
>
> On 2022-06-06 22:37, Mohd Bilal wrote:
> > I have added an autopkgtest for busco[1] as mentioned in bug report[2].
> > The license for the test data needs to be added. I have opened an
> > issue[3] upstream asking
Hi Mohd,
On 2022-06-06 22:37, Mohd Bilal wrote:
> I have added an autopkgtest for busco[1] as mentioned in bug report[2].
> The license for the test data needs to be added. I have opened an
> issue[3] upstream asking for clarification. Requesting someone to review
> my changes .
>
> Thanks,
>
13 matches
Mail list logo