From: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Launchpad linux-rdma group and rdma-core daily builds
Date: Tue, 07 Nov 2017 17:20:58 +0100 [thread overview]
Message-ID: <1510071658.32330.18.camel@profitbricks.com> (raw)
In-Reply-To: <20171107155838.GE21466-uk2M96/98Pc@public.gmane.org>
Am Dienstag, den 07.11.2017, 08:58 -0700 schrieb Jason Gunthorpe:
> On Tue, Nov 07, 2017 at 02:50:06PM +0100, Benjamin Drung wrote:
>
> > The package was built successfully for Ubuntu 16.04 (xenial) and
> > newer.
> > The build fails for Ubuntu 14.04 (trusty) due to the missing
> > libsystemd-dev package.
>
> Yes, to build on trusty a patch to the control file would be needed..
>
> IIRC libsystemd-dev is called something else on trusty.
>
> I am fine not building on trusty.
>
> What can be done if developers join the launchpad group?
You can change the description of the team, adjust subscriptions (e.g.
once rdma-core is in Ubuntu, linux-rdma could subscribe to the bug
reports), create new PPAs, adjust the daily build recipe (e.g. trigger
builds, add/remove series), configure the rdma-core project (e.g.
description, create series and milestones). I am not sure which of the
listed things need administrator permission.
--
Benjamin Drung
System Developer
Debian & Ubuntu Developer
ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin
Email: benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org
URL: https://www.profitbricks.de
Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-11-07 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 13:50 Launchpad linux-rdma group and rdma-core daily builds Benjamin Drung
[not found] ` <1510062606.32330.13.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-07 15:58 ` Jason Gunthorpe
[not found] ` <20171107155838.GE21466-uk2M96/98Pc@public.gmane.org>
2017-11-07 16:20 ` Benjamin Drung [this message]
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=1510071658.32330.18.camel@profitbricks.com \
--to=benjamin.drung-eikl63zcoxah+58jc4qpia@public.gmane.org \
--cc=jgg-uk2M96/98Pc@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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