Discussion:
Bug#934322: Split reporting code from Lintian proper
Add Reply
Felix Lechner
2019-08-09 18:30:02 UTC
Reply
Permalink
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.

Name suggestions are welcome. How about 'lintian-reporting' or
'lintian-webservice'?

Kind regards,
Felix Lechner
Chris Lamb
2019-08-10 17:30:02 UTC
Reply
Permalink
Hi Felix,
Post by Felix Lechner
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. Perhaps I'm missing something...


Regards,
--
,''`.
: :' : Chris Lamb
`. `'` ***@debian.org 🍥 chris-lamb.co.uk
`-
Felix Lechner
2019-08-10 17:40:01 UTC
Reply
Permalink
Hi Chris,
Post by Chris Lamb
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?

Kind regards,
Felix
Chris Lamb
2019-08-11 12:40:02 UTC
Reply
Permalink
Hi Felix,
Post by Felix Lechner
Post by Chris Lamb
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 not know the historical reason. Perhaps it makes sense I cannot
install packages but also it might make sense that we can deploy misc/
random changes from Git.


Regards,
--
,''`.
: :' : Chris Lamb
`. `'` ***@debian.org 🍥 chris-lamb.co.uk
`-
Mattia Rizzolo
2019-08-11 13:20:03 UTC
Reply
Permalink
Post by Chris Lamb
Post by Felix Lechner
Post by Chris Lamb
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 not know the historical reason. Perhaps it makes sense I cannot
install packages but also it might make sense that we can deploy misc/
random changes from Git.
It definitely happened more than once in history that lindsay was
running on a commit that was slighly different than the released one.
--
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Chris Lamb
2019-08-11 13:30:01 UTC
Reply
Permalink
Post by Mattia Rizzolo
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 after I let the sid version mature and migrate to testing).


Regards,
--
,''`.
: :' : Chris Lamb
`. `'` ***@debian.org 🍥 chris-lamb.co.uk
`-
Felix Lechner
2019-08-11 15:00:01 UTC
Reply
Permalink
Post by Chris Lamb
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-backports
cycle on lindsay if I can solve the out of memory problems there and
provide a way to preview new reporting features before they are
released into master?

Loading...