Russ Allbery schrieb:
Lintian intentionally doesn't check for dangling symlinks at all because
of this issue. See #217023.
Oh, I didn't know this.
In this case, I think you should keep the menu package in the binary
package and not move it to the data package. (Honestly, I would do the
Hello Russ,
Russ Allbery schrieb:
Right, the problem is that Lintian checks a package at a time, so while
it's checking foo, it has no access to foo-data. Lintian is designed to
check each package in isolation. It's difficult to do more than that and
still support things like lintian.d.o.
Fabian Greffrath greffr...@leat.rub.de writes:
Russ Allbery schrieb:
That being said, there is a possible hack that we can apply here that
may fix the common case of checking a *.changes file for a set of
related packages and on lintian.d.o. See the discussion in #456657 for
more details.
Package: lintian
Severity: minor
Version: 2.1.5
Dear lintian maintainers,
sorry for the subject line, but my concern is a little bit too
complicated to describe it in one line, I guess. ;)
Imagine I build a package foo, which consists of a binary in /usr/bin
and architecture-independent
severity 512645 wishlist
merge 512645 120323
retitle 512645 [checks/manpages] missing man pages reported for foo that are in
foo-data
thanks
Fabian Greffrath greffr...@leat.rub.de writes:
But now, if I run lintian on the newly created packages, I get warnings
like binary-without-manpage:
5 matches
Mail list logo
