From: "Baeuerle, Florian" <Florian.Baeuerle@allegion.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH v3 1/3] polkit: add debian patches
Date: Thu, 17 Jan 2019 10:01:29 +0000 [thread overview]
Message-ID: <af98a6c4f90782f373384d92c374d75f1540b76b.camel@allegion.com> (raw)
In-Reply-To: <20190117085807.3uafhxx3w7fekrdq@pengutronix.de>
Hi,
Am Donnerstag, den 17.01.2019, 09:58 +0100 schrieb m.olbrich@pengutronix.de:
> Hi,
>
> On Wed, Jan 16, 2019 at 09:36:22AM +0000, Baeuerle, Florian wrote:
> > is there a chance to get these patches into ptxdist? I think this fixes
> > quite a
> > few bugs.
> >
> > Any rework required?
>
> I've been doing some rework myself. The situation is unlikely to change in
> the near future, so I expect we will need to import new patches again at
> some point. So I want to automate this a bit.
> I'm doing the same thing with openssl so I just copied and modified the
> script I use there (see attachment). I'm doing some build tests with this
> right now. This should hit master sometime this week.
>
> My patch selection is a bit different from yours, so I'd appreciate some
> feedback there. I'm currently importing from
> policykit-1_0.105-25.debian.tar.xz, that the latest version in Debian
> unstable.
Okay, I see you identified more debian-specific patches.
You blacklisted 06_systemd-service.patch, that presumably is, because the debian
build system is responsible for installing the polkit.service file.
I think it would be nice to install the polkit service on systemd-based systems,
so we could either resemble what the debian build system does (i.e. placing that
service in projectroot, and use mentioned patch) *or* use this upstream patch:
https://cgit.freedesktop.org/polkit/commit/data/?id=29950854f6b9e9b8ea2d96d67c79eeec1046a4f1
- Florian
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-01-17 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 14:18 [ptxdist] [PATCH 1/2] rules: polkit: Fix incorrect installation path Dold, Wolfram
2018-12-10 14:18 ` [ptxdist] [PATCH 2/2] rules: systemd: Change hardcoded polkit configure option Dold, Wolfram
2018-12-11 7:43 ` Michael Olbrich
2018-12-11 15:34 ` [ptxdist] [PATCH v2 1/2] " Dold, Wolfram
2018-12-11 7:41 ` [ptxdist] [PATCH 1/2] rules: polkit: Fix incorrect installation path Michael Olbrich
2018-12-11 15:34 ` [ptxdist] [PATCH v2 2/2] patches/polkit-0.105: Ubuntu polkit patches Dold, Wolfram
2018-12-17 8:26 ` [ptxdist] (no subject) Dold, Wolfram
2018-12-17 8:26 ` [ptxdist] [PATCH v2 2/2] patches/polkit-0.105: Ubuntu polkit patches Dold, Wolfram
2018-12-17 9:19 ` Dold, Wolfram
2018-12-17 10:53 ` Dold, Wolfram
2018-12-22 13:19 ` [ptxdist] [PATCH v3 0/3] polkit debian patches Baeuerle, Florian
2018-12-22 13:19 ` [ptxdist] [PATCH v3 1/3] polkit: add " Baeuerle, Florian
2019-01-16 9:36 ` Baeuerle, Florian
2019-01-17 8:58 ` m.olbrich
2019-01-17 10:01 ` Baeuerle, Florian [this message]
2019-01-17 13:48 ` Michael Olbrich
2018-12-22 13:19 ` [ptxdist] [PATCH v3 2/3] polkit: add patch from upstream Baeuerle, Florian
2018-12-22 13:19 ` [ptxdist] [PATCH v3 3/3] systemd: enable POLKIT support if polkit is selected Baeuerle, Florian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af98a6c4f90782f373384d92c374d75f1540b76b.camel@allegion.com \
--to=florian.baeuerle@allegion.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox