On Tue, Jul 07, 2020 at 03:52:08PM +0200, Guillem Jover wrote:
> Holger, as I mentioned some days ago, I consider this case a
> regression which I was planning on fixing. This fix was already
> included earlier today in the dpkg 1.20.4 upload. :)
yup, I've seen this today. Thank you!
--
On Tue, 2020-07-07 at 09:29:44 +, Holger Levsen wrote:
> On Mon, Jul 06, 2020 at 09:08:43PM -0700, Felix Lechner wrote:
> > > not sure if this is the same bug or just a similar one:
> > > lrwxrwxrwx 1 user user 9 Jul 3 16:07 debian/munin.service -> /dev/null
> > As for Holger's package,
Hi Holger,
On Tue, Jul 7, 2020 at 2:29 AM Holger Levsen wrote:
>
> sigh. so IMNSHO now lintian *and* dpkg are buggy. Or point me to policy
> which prohibits files pointing to /dev/null. This worked for years.
The restriction applies only to source packages and not to
installation packages. Is
On Mon, Jul 06, 2020 at 09:08:43PM -0700, Felix Lechner wrote:
> > not sure if this is the same bug or just a similar one:
> > lrwxrwxrwx 1 user user 9 Jul 3 16:07 debian/munin.service -> /dev/null
> As for Holger's package, Lintian also flags that condition. Source
> packages can be unpacked
Hi Guillem,
On Fri, Jul 3, 2020 at 9:54 PM Guillem Jover wrote:
>
> As long as the autopkgtests show regressions for the involved packages
>From Lintian's perspective, this bug is now resolved. After some
changes on our side, Lintian builds in unstable (without a new upload
of dpkg). I would
On Fri, 2020-07-03 at 05:27:46 -0700, Felix Lechner wrote:
> Why did you lower the severity instead of releasing a fix?
As explained, because the severity seemed off. Also because there
are still other regressions being dealt with…
> If version 1.20.3 progresses to testing, Lintian loses its
Hi!
On Fri, 2020-07-03 at 14:12:10 +, Holger Levsen wrote:
> not sure if this is the same bug or just a similar one:
Yeah, related, but not entirely the same.
> [...]
> dpkg-source: info: extracting munin in munin-2.0.63
> dpkg-source: info: unpacking munin_2.0.63.orig.tar.gz
> dpkg-source:
Hi,
not sure if this is the same bug or just a similar one:
[...]
dpkg-source: info: extracting munin in munin-2.0.63
dpkg-source: info: unpacking munin_2.0.63.orig.tar.gz
dpkg-source: info: unpacking munin_2.0.63-1.debian.tar.xz
dpkg-source: error: pathname 'munin-2.0.63/debian/munin.service'
Hi,
On Thu, Jul 2, 2020 at 10:11 PM Guillem Jover wrote:
>
> The affected pathnames contain symlink loops, which I'd consider to be
> erroneous constructs, and I don't see why we'd want to allow these. In
> this case this seem just like an incorrect error message. I've updated
> this locally now
Control: severity -1 minor
On Fri, 2020-07-03 at 01:54:11 +0300, Andrei POPESCU wrote:
> Control: reassign -1 dpkg-dev
> On Mi, 01 iul 20, 15:47:53, Felix Lechner wrote:
> > Control: retitle -1 dpkg-source: False positive 'points outside source root'
> > Control: severity -1 serious
> > The
Control: reassign -1 dpkg-dev
On Mi, 01 iul 20, 15:47:53, Felix Lechner wrote:
> Control: retitle -1 dpkg-source: False positive 'points outside source root'
> Control: severity -1 serious
>
> Hi,
>
> The initial filing said the three packages contained link targets
> outside of the package
Control: retitle -1 dpkg-source: False positive 'points outside source root'
Control: severity -1 serious
Hi,
The initial filing said the three packages contained link targets
outside of the package root, but that is not so. This is not right:
dpkg-source: error: pathname
12 matches
Mail list logo
