On Wed, May 12, 2021 at 01:58PM +0000, Greg KH wrote:
> On Tue, May 11, 2021 at 08:58:16PM +0200, Nicolas Schier wrote:
> > From: Finn Behrens <me@xxxxxxxxx>
> >
> > commit c25ce589dca10d64dde139ae093abc258a32869c upstream.
> >
> > Change every shebang which does not need an argument to use /usr/bin/env.
> > This is needed as not every distro has everything under /usr/bin,
> > sometimes not even bash.
> >
> > Signed-off-by: Finn Behrens <me@xxxxxxxxx>
> > Signed-off-by: Masahiro Yamada <masahiroy@xxxxxxxxxx>
> > [nicolas@xxxxxxxxx: ported to v4.9, updated contexts, adapt for old
> > scripts]
>
> What about 4.14, 4.19, 5.4, and 5.10? We can't add patches only to one
> stable tree and not all of the newer ones as well.
Hi Greg,
yes, that makes sense obviously, I did not have that in mind. If there
is a chance for acceptance, I will gladly provide the patches for the
newer stable tree as well.
> And what problem is this solving? What distro has problems with this
> for this old kernel tree?
>
> thanks,
>
> greg k-h
my concrete problem is that I work with several 4.9 kernel trees and
that our build system uses diffconfig (for consistency checking) which
does not run anymore on a current Debian testing (/usr/bin/python is
not more available). As the corresponding upstream "fix" commit
51839e29cb59544 (cp. patch 2/2) technically bases on commit
c25ce589dca10d64dde, I thought backporting both should be the cleaner
way.
I would not mind to drop this patch, but I would like to see commit
51839e29cb59544 in the stable trees. Does it make sense to prepare
backports of it for all current stable trees?
Thanks and kind regards,
Nicolas
--
epost: nicolas@xxxxxxxxx irc://oftc.net/nsc
↳ gpg: 18ed 52db e34f 860e e9fb c82b 7d97 0932 55a0 ce7f
-- frykten for herren er opphav til kunnskap --
