mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <post@lespocky.de>, Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [PATCH v2 5/5] modemmanager: version bump 1.14.8 -> 1.16.2
Date: Tue, 30 Mar 2021 19:34:01 +0200	[thread overview]
Message-ID: <20210330173401.GH12201@pengutronix.de> (raw)
In-Reply-To: <4053874.OBDmMSYSSk@ada>

On Tue, Mar 30, 2021 at 03:54:19PM +0200, Alexander Dahl wrote:
> Am Dienstag, 30. März 2021, 11:17:26 CEST schrieb Roland Hieber:
> > On Tue, Mar 30, 2021 at 08:42:35AM +0200, Michael Olbrich wrote:
> > > Why not update libgudev instead of adding this patch?
> > 
> > In <20210329054904.24342-1-post@lespocky.de>, Alexander Dahl wrote:
> > > Hei hei,
> > > 
> > > in this v2 series I removed the libgudev version bump, until that
> > > license issue is clarified. (I suggested to set 'LGPL-2.0-or-later AND
> > > LGPL-2.1-or-later' in IRC, but don't know if that's possible?)
> > 
> > I think that variant is the best way we can currently express this
> > situation (and it will effectively result in LGPL-2.1-or-later).
> 
> Meanwhile upstream clarified to LGPL-2.1-or-later only and included SPDX tags 
> to file headers:
> 
> https://gitlab.gnome.org/GNOME/libgudev/-/merge_requests/14
> 
> So we could just wait for the next release to have that sorted out cleanly. 
> Will have to switch to meson for building the libgudev package though.

I've applied the modemmanager update as is for now. Please keep the patch
in mind, when the update happens.

Regards,
Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  reply	other threads:[~2021-03-30 17:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  5:48 [ptxdist] [PATCH v2 0/5] ModemManager: version bump Alexander Dahl
2021-03-29  5:49 ` [ptxdist] [PATCH v2 1/5] libqmi: Add license file hashes Alexander Dahl
2021-03-30 18:08   ` [ptxdist] [APPLIED] " Michael Olbrich
2021-03-29  5:49 ` [ptxdist] [PATCH v2 2/5] libqmi: version bump 1.26.2 -> 1.28.2 Alexander Dahl
2021-03-30 18:08   ` [ptxdist] [APPLIED] " Michael Olbrich
2021-03-29  5:49 ` [ptxdist] [PATCH v2 3/5] modemmanager: Revise applicable licenses Alexander Dahl
2021-03-30 18:08   ` [ptxdist] [APPLIED] " Michael Olbrich
2021-03-29  5:49 ` [ptxdist] [PATCH v2 4/5] modemmanager: Add license file hashes Alexander Dahl
2021-03-30 18:08   ` [ptxdist] [APPLIED] " Michael Olbrich
2021-03-29  5:49 ` [ptxdist] [PATCH v2 5/5] modemmanager: version bump 1.14.8 -> 1.16.2 Alexander Dahl
2021-03-30  6:42   ` Michael Olbrich
2021-03-30  9:17     ` Roland Hieber
2021-03-30 13:54       ` Alexander Dahl
2021-03-30 17:34         ` Michael Olbrich [this message]
2021-03-30 18:08   ` [ptxdist] [APPLIED] " Michael Olbrich

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=20210330173401.GH12201@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=post@lespocky.de \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@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