Bug#904083: Regression run_lintian calls lintian with a non existing filename

2019-08-09 Thread Maximiliano Curia
¡Hola Johannes! El 2019-01-04 a las 19:35 +0100, Johannes Schauer escribió: Quoting Maximiliano Curia (2019-01-04 19:01:52) On Thu, 19 Jul 2018 13:08:02 +0200 Maximiliano Curia wrote: With the new release of sbuild 0.77 (which moves the run_lintian call outside of the build function),

Bug#904083: Regression run_lintian calls lintian with a non existing filename

2019-01-04 Thread Johannes Schauer
¡Hola! Quoting Maximiliano Curia (2019-01-04 19:01:52) > > On Thu, 19 Jul 2018 13:08:02 +0200 Maximiliano Curia > > wrote: > >> With the new release of sbuild 0.77 (which moves the run_lintian call > >> outside > >> of the build function), lintian receives the name of a no longer existing > >>

Bug#904083: Regression run_lintian calls lintian with a non existing filename

2019-01-04 Thread Maximiliano Curia
¡Hola Johannes! El 2019-01-04 a las 15:34 +0100, Johannes Schauer escribió: Control: tag -1 + moreinfo Control: severity -1 normal Hi, On Thu, 19 Jul 2018 13:08:02 +0200 Maximiliano Curia wrote: With the new release of sbuild 0.77 (which moves the run_lintian call outside of the build

Bug#904083: Regression run_lintian calls lintian with a non existing filename

2019-01-04 Thread Johannes Schauer
Control: tag -1 + moreinfo Control: severity -1 normal Hi, On Thu, 19 Jul 2018 13:08:02 +0200 Maximiliano Curia wrote: > With the new release of sbuild 0.77 (which moves the run_lintian call outside > of the build function), lintian receives the name of a no longer existing > changes file (as

Bug#904083: Regression run_lintian calls lintian with a non existing filename

2018-07-19 Thread Maximiliano Curia
Package: sbuild Version: 0.77.0-3 Severity: important Hi, With the new release of sbuild 0.77 (which moves the run_lintian call outside of the build function), lintian receives the name of a no longer existing changes file (as the unlink is part of the copy_changes) and as such it fails