Re: Help with autopkgtest for Seqsero and python-loompy

2021-03-07 Thread Andreas Tille
On Mon, Mar 08, 2021 at 12:30:52AM +0530, Nilesh Patra wrote: > > Thank you so much! I haven't had a chance to work on loompy yet, but I > > have added tests to Seqsero. Please review and sponsor. > > Please remove the "ubuntu1" from changelog header. +1 > @Andreas, I'm not sure if it should be

Re: Help with autopkgtest for Seqsero and python-loompy

2021-03-07 Thread Nilesh Patra
On Sun, 7 Mar, 2021, 11:58 pm Shruti Sridhar, wrote: > Hi, > > Thank you so much! I haven't had a chance to work on loompy yet, but I > have added tests to Seqsero. Please review and sponsor. > Please remove the "ubuntu1" from changelog header. @Andreas, I'm not sure if it should be uploaded at

Re: Help with autopkgtest for Seqsero and python-loompy

2021-03-07 Thread Shruti Sridhar
Hi, Thank you so much! I haven't had a chance to work on loompy yet, but I have added tests to Seqsero. Please review and sponsor. Best, Shruti On Wed, Feb 24, 2021 at 2:33 PM Andreas Tille wrote: > On Wed, Feb 24, 2021 at 02:00:19PM +0530, Nilesh Patra wrote: > > Protecting the master branc

Re: Help with autopkgtest for Seqsero and python-loompy

2021-02-24 Thread Andreas Tille
On Wed, Feb 24, 2021 at 02:00:19PM +0530, Nilesh Patra wrote: > Protecting the master branch is an ideal thing to do since this doesn't > allow force pushing -- if it wasn't protected, it'd be easy for a new comer > who's not very well versed > with git to mistakenly mess things up. > ... > That ca

Re: Differences in salsa access (was: Help with autopkgtest for Seqsero and python-loompy)

2021-02-24 Thread Andreas Tille
Hi, On Wed, Feb 24, 2021 at 02:08:36PM +0530, Nilesh Patra wrote: > > There are some Debian Med repositories where the access control > > set up differently. Users that are logged in and have permissions will > > see that under "Protected branches", in the column "Allowed to push" > > for the mast

Re: Differences in salsa access (was: Help with autopkgtest for Seqsero and python-loompy)

2021-02-24 Thread Nilesh Patra
On Wed, 24 Feb 2021 at 14:05, Juhani Numminen wrote: > Hi, > > Nilesh Patra kirjoitti 23.2.2021 klo 19.39: > > Hi, > > > > On Tue, 23 Feb 2021 at 22:25, Shruti Sridhar > wrote: > > > [...] I couldn't push my changes because it is on a protected branch > so

Differences in salsa access (was: Help with autopkgtest for Seqsero and python-loompy)

2021-02-24 Thread Juhani Numminen
Hi, Nilesh Patra kirjoitti 23.2.2021 klo 19.39: > Hi, > > On Tue, 23 Feb 2021 at 22:25, Shruti Sridhar > wrote: > [...] I couldn't push my changes because it is on a protected branch so I > have made a fork

Re: Help with autopkgtest for Seqsero and python-loompy

2021-02-24 Thread Nilesh Patra
Hi Andreas On Wed, 24 Feb 2021 at 13:40, Andreas Tille wrote: > > In any case, you can enable salsa CI on your personal fork to track this. > > Hmmm, I think we should not propagate personal forks. I'm afraid that > some fork might feature interesting commits but will be lost somewhere. > So I'

Re: Help with autopkgtest for Seqsero and python-loompy

2021-02-24 Thread Andreas Tille
Hi, On Tue, Feb 23, 2021 at 11:09:39PM +0530, Nilesh Patra wrote: > ... Thanks Nilesh for helping out. No comment so far. > In any case, you can enable salsa CI on your personal fork to track this. Hmmm, I think we should not propagate personal forks. I'm afraid that some fork might feature i

Re: Help with autopkgtest for Seqsero and python-loompy

2021-02-23 Thread Nilesh Patra
Hi, On Tue, 23 Feb 2021 at 22:25, Shruti Sridhar wrote: > Hi, > > I was trying to write autopkgtests for Seqsero and python-loompy. I have > been facing some errors. Could someone please have a look and let me know > what I can do : > > 1. Seqsero : I

Help with autopkgtest for Seqsero and python-loompy

2021-02-23 Thread Shruti Sridhar
Hi, I was trying to write autopkgtests for Seqsero and python-loompy. I have been facing some errors. Could someone please have a look and let me know what I can do : 1. Seqsero : I added the test data and the path to that in the example file but on run