Bug#934322: Split reporting code from Lintian proper

2019-08-12 Thread Chris Lamb
Felix Lechner wrote: > > Indeed and even within this lindsay is running the unstable version > > and is updated at the time of the release (instead of at time-of- > > backport after I let the sid version mature and migrate to testing). > > Would you both be comfortable if we returned to a stable-

Bug#934322: Split reporting code from Lintian proper

2019-08-11 Thread Felix Lechner
On Sun, Aug 11, 2019 at 6:18 AM Chris Lamb wrote: > > Indeed and even within this lindsay is running the unstable version > and is updated at the time of the release (instead of at time-of- > backport after I let the sid version mature and migrate to testing). Would you both be comfortable if we

Bug#934322: Split reporting code from Lintian proper

2019-08-11 Thread Chris Lamb
Mattia wrote: > It definitely happened more than once in history that lindsay was > running on a commit that was slighly different than the released one. Indeed and even within this lindsay is running the unstable version and is updated at the time of the release (instead of at time-of- backport

Bug#934322: Split reporting code from Lintian proper

2019-08-11 Thread Mattia Rizzolo
On Sun, Aug 11, 2019 at 01:30:51PM +0100, Chris Lamb wrote: > > > How would this work? We don't install the lintian binary package on > > > lindsay.debian.org so this wouldn't bring in extra dependencies > > > automatically. > > > > I slowly figured that out with help from olasd and adsb. Why are

Bug#934322: Split reporting code from Lintian proper

2019-08-11 Thread Chris Lamb
Hi Felix, > > How would this work? We don't install the lintian binary package on > > lindsay.debian.org so this wouldn't bring in extra dependencies > > automatically. > > I slowly figured that out with help from olasd and adsb. Why are we > not limiting ourselves to backports on lindsay? I do

Bug#934322: Split reporting code from Lintian proper

2019-08-10 Thread Felix Lechner
Hi Chris, On Sat, Aug 10, 2019 at 10:17 AM Chris Lamb wrote: > > How would this work? We don't install the lintian binary package on > lindsay.debian.org so this wouldn't bring in extra dependencies > automatically. I slowly figured that out with help from olasd and adsb. Why are we not limiting

Bug#934322: Split reporting code from Lintian proper

2019-08-10 Thread Chris Lamb
Hi Felix, > Going forward, lintian.d.o would simply depend on 'lintian', in > addition to any installation prerequisites for the reporting package. How would this work? We don't install the lintian binary package on lindsay.debian.org so this wouldn't bring in extra dependencies automatically. Pe

Bug#934322: Split reporting code from Lintian proper

2019-08-09 Thread Felix Lechner
Package: src:lintian Hi, I have had trouble keeping DSA in the loop on new dependencies. May I please split Lintian's reporting code into a separate package? Going forward, lintian.d.o would simply depend on 'lintian', in addition to any installation prerequisites for the reporting package. Nam