Hi,
Dominic Hargreaves wrote:
> On Tue, Aug 21, 2018 at 08:42:11PM -0700, Russ Allbery wrote:
>> I do feel like allowing either based on the whim of the packager is just
>> kind of bad. It produces inconsistent behavior to no real benefit for
>> anyone. If you install a Perl earlier in your
Hi,
> Addressing your inconsistency argument above: I can certainly see an
> argument that some types of perl scripts shipped in Debian might want
> to opt into being run by a different interpreter for special reasons,
> but I think they should be the exception rather than the rule. Having
I am
On Tue, Aug 21, 2018 at 08:42:11PM -0700, Russ Allbery wrote:
> Russ Allbery writes:
>
> > Did Lintian have some special case that was allowing /usr/bin/env perl
> > previously and then Lintian changed based on Policy? That would be
> > unfortunate, since we thought we were changing to match
On Thu, 23 Aug 2018 at 01:20:44 +1000, Stuart Prescott wrote:
> d) revert to /usr/share/doc/python-foo-doc: do we ignore policy's
> recommendation, overriding (or changing) dh_installdocs? While
> /usr/share/doc/main-package is only a recommendation in policy, 700
> python-foo-doc packages
Package: debian-policy
X-Debbugs-CC: debhelper-de...@lists.alioth.debian.org,
debian-pyt...@lists.debian.org
Hi!
[ Promised follow up to the Python BoF at DebConf ]
For historical reasons, Python 2 modules are packaged as python-foo while
Python 3 modules are python3-foo. Documentation was
On Wednesday, 22 August 2018 13:26:30 AEST Ian Jackson wrote:
> In practice, replacing perl with a homebrewed actual perl is rare and
> in that case you want to put it in /usr/bin, because that's where all
> distributed perl scripts expect it to be.
(If you'd make it /usr/bin/perl anyway, isn't
Russ Allbery writes ("Bug#906901: debian-policy: Perl script shebang
requirement is disturbing and inconsistent with rest of policy"):
> Yeah, this is one of the points that I'm struggling with: I feel like our
> stance with Perl (and Python) and our stance with maintainer scripts is
>
Norbert Preining wrote:
> Hmm, really? Looking throught the python scripts in TeX Live I find a
> lot of different things:
> /usr/share/texlive/texmf-dist/scripts] find . -name \*.py -exec head -n1
> '{}' \;
[...]
> I don't see that this is acutally working in debhelper.
debhelper does this just
Hi,
On Tue, 21 Aug 2018, Russ Allbery wrote:
> Perl folks, the short version is that Lintian wasn't actually checking for
> scripts that used /usr/bin/env perl, so our check when we closed #683495
> was bogus. Lintian has now changed based on Policy, and it looks like
> there were around 2,000
Package: debian-policy
Version: 4.2.0.1
Severity: normal
Dear Maintainer,
In policy/policy/ch-scope.rst
> udebs (stripped-down binary packages used by the Debian Installer) do
> not comply with all of the requirements discussed here. See the `Debian
> Installer internals
> manual
10 matches
Mail list logo
