Control: tags -1 - moreinfo
On Sat, Apr 23, 2016 at 02:38:54PM +, Niels Thykier wrote:
> The issue then being that Lintian can say very little about the
> dependencies of a given packages (except if it has none).
I agree. For this reason I implemented the check outside lintian on top
of
On Mon, 31 Aug 2015 12:16:59 +0200 Fabian Greffrath
wrote:
> Hi again, Jakub,
>
> Am Montag, den 31.08.2015, 12:09 +0200 schrieb Jakub Wilk:
> > Python used to be the classic example:
> > "python" was an arch:all meta-package that depended on "python2.X".
> > But if a Python
Hi again, Jakub,
Am Montag, den 31.08.2015, 12:09 +0200 schrieb Jakub Wilk:
> Python used to be the classic example:
> "python" was an arch:all meta-package that depended on "python2.X".
> But if a Python module depended on "python", it was because it needed a
> Python interpreter of the same
Hi Fabian!
* Fabian Greffrath , 2015-08-28, 13:46:
Not every "Architecture: all" package can be marked as "Multi-Arch:
foreign". Otherwise, we could just teach dpkg and APT to treat all
arch:all packages as if they were ma:foreign and be done with it. :)
could you please
Package: lintian
Version: 2.5.36.1
Severity: wishlist
Hi there,
I am not sure if there is a situation possible in which an Arch:all
package should not carry the Multi-Arch:foreign tag. However, it is
part of the Multiarch specification that packages which may satisfy
dependencies on all
* Fabian Greffrath fab...@debian.org, 2015-08-28, 09:40:
I am not sure if there is a situation possible in which an Arch:all
package should not carry the Multi-Arch:foreign tag.
Not every Architecture: all package can be marked as Multi-Arch:
foreign. Otherwise, we could just teach dpkg and
Hi Jakub,
Am Freitag, den 28.08.2015, 11:25 +0200 schrieb Jakub Wilk:
Not every Architecture: all package can be marked as Multi-Arch:
foreign. Otherwise, we could just teach dpkg and APT to treat all
arch:all packages as if they were ma:foreign and be done with it. :)
could you please point
7 matches
Mail list logo