it's a good
thing to have in the repo, though.
Signed-off-by: Russell Currey
---
docker-compose-eatmydata.yml | 32 +++
tools/docker/Dockerfile.eatmydata | 9 +
2 files changed, 41 insertions(+)
create mode 100644 docker-compose-eatmydata.yml
create
On Wed, 2019-05-01 at 17:27 +1000, Andrew Donnellan wrote:
> On 1/5/19 2:35 pm, Russell Currey wrote:
> > psycopg2-binary fails if pg_config isn't installed, which is
> > provided by
> > libpq-dev.
> >
> > This seems strange to me since psycopg2-binary suggests
re elegant way to do it. Unfortunately it doesn't seem like
there's any way to do conditional COPY, and anything in RUN is plain
/bin/sh, so that's why it looks like it does.
Tested on ppc64le and on x86_64.
Signed-off-by: Russell Currey
---
tools/docker/Dockerfile| 14 --
to
Might as well since it's there, and it gives some clue to anyone trying
to use Docker on non-x86. I figured it was best to leave this out of
the README since it's incredibly niche.
Signed-off-by: Russell Currey
---
docs/development/installation.rst | 4
1 file changed, 4 insertions
that psycopg2-binary only needs to compile itself on
non-x86 platforms, since I hit this on ppc64le.
Anyway, it works when this is added.
Signed-off-by: Russell Currey
---
tools/docker/Dockerfile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/docker/Dockerfile b/tools
Creating the .env file is mentioned in the installation documentation
but not in the README, so following only the steps mentioned there will
fail. Add this and add a `cd patchwork` in there for good measure so
you could straight up copy paste the steps.
Signed-off-by: Russell Currey
On Thu, 2018-11-08 at 14:28 +, Stephen Finucane wrote:
> On Fri, 2018-11-09 at 00:42 +1100, Daniel Axtens wrote:
> > Hi Christopher,
> >
> > > What I'm really trying to is get to the point where the series
> > > can be
> > > tested. I know you've written and talked about using Patchwork
> > >
On Fri, 2017-10-13 at 13:01 +1100, Daniel Axtens wrote:
> Hi David,
>
> You might also want to look at Snowpatch - it's a shim between patchwork
> and Jenkins, so it might have some helpful concepts.
>
> https://developer.ibm.com/open/openprojects/snowpatch/
> https://github.com/ruscur/snowpatch
On Thu, 2017-05-25 at 22:26 +0100, Stephen Finucane wrote:
> On Thu, 2017-05-25 at 18:47 +1000, Andrew Donnellan wrote:
> > Token authentication is generally viewed as a more secure option for
> > API
> > authentication than storing a username and password.
> >
> > Django REST Framework gives us
On Mon, 2017-05-01 at 08:47 +1000, Daniel Axtens wrote:
> Hi Stephen,
>
> Apologies on my patchwork-silence; I've recently moved from IBM to
> Canonical so I've been a bit flat-out.
>
> I haven't tested the patches for support for distro-package Xenial, so
> I'd like to do that, and also do some
port subject prefixes in the REST API.
>
> Signed-off-by: Daniel Axtens <d...@axtens.net>
>
Tested-by: Russell Currey <rus...@russell.cc>
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork
On Tue, 2017-02-14 at 08:47 +1100, Daniel Axtens wrote:
> Hi Stephen,
>
> > On Sat, 2017-02-11 at 21:55 +1100, Daniel Axtens wrote:
> > > Some mailing lists accept patches for multiple projects, and use
> > > a subject prefix to differentiate the projects.
> >
> > A couple of comments on this
On Sat, 2017-02-11 at 21:55 +1100, Daniel Axtens wrote:
> Some mailing lists accept patches for multiple projects, and use
> a subject prefix to differentiate the projects.
>
> Therefore, for snowpatch, it's useful to be able to fetch the
> subject prefixes. Snowpatch calls these 'categories', so
On Sat, 2016-11-19 at 16:51 +, Stephen Finucane wrote:
> Adopt a hybrid approach, by adding an additional series endpoint to the
> existing patch endpoint:
>
> /series/${series_id}/
> /patches/${patch_id}/
>
> This is based on the approach described here:
>
>
On Thu, 2016-11-17 at 01:47 +, Stephen Finucane wrote:
> This requires the series REST API series.
This breaks stuff, I'm not sure why.
Environment:
Request Method: GET
Request URL: http:///project//list/
Django Version: 1.8
Python Version: 2.7.12
Installed Applications:
On Mon, 2016-09-05 at 14:25 +1000, Andrew Donnellan wrote:
> On 05/09/16 14:19, Russell Currey wrote:
> >
> > In testing v2 I found a weird issue I didn't find before.
> >
> > If you send a new series in reply to the cover letter of a previous series,
>
ed-off-by: Stephen Finucane <stephen.finuc...@intel.com>
> Tested-by: Russell Currey <rus...@russell.cc>
> ---
In testing v2 I found a weird issue I didn't find before.
If you send a new series in reply to the cover letter of a previous series, it
appends the patches to the prev
On Tue, 2016-08-02 at 13:44 +1000, Daniel Axtens wrote:
> >
> > Would it be possible to use chromium instead? It's probably included in
> > distributions and wouldn't require adding a third-party repo, and worse,
> > proprietary software.
> >
> That's a fair point; I'll have a look.
>
> Would
On Tue, 2016-08-02 at 10:24 +1000, Daniel Axtens wrote:
> This makes it possible to use Docker and docker-compose for development
> as an alternative to Vagrant.
>
> I quite liked vagrant a couple of years ago, but currently:
>
> * Trying to install VirtualBox on Ubuntu wants me to disable
>
t; ---
There might have been some edge cases this fails to parse, but for everything I
saw series were parsed correctly.
Tested-by: Russell Currey <rus...@russell.cc>
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork
On Mon, 2016-06-13 at 11:41 +0100, Stephen Finucane wrote:
> Add a series model. This model is intentionally very minimal to allow
> as much dynaminism as possible. It is expected that patches will be
> migrated between series as new data is provided.
>
> Signed-off-by: Stephen Finucane
If multiple cover letters are found, parsemail dies with a
MultipleObjectsReturned exception. This is particularly problematic in
the middle of a parsearchive run, so just ignore multiple cover letters.
Signed-off-by: Russell Currey <rus...@russell.cc>
---
patchwork/bin/parsemail.py | 3
Given the documentation suggests using Ubuntu, and any Debian derivative
requires manually specifying plugins in uwsgi, add the python27 plugin to
the example uwsgi settings file.
Signed-off-by: Russell Currey <rus...@russell.cc>
---
lib/uwsgi/patchwork.ini | 2 ++
1 file changed, 2 inse
systemctl takes the name of the operation before the name of the service
so that you can do multiple things at once, i.e. "systemctl status nginx
postgresql". Fix the ordering of the arguments.
Signed-off-by: Russell Currey <rus...@russell.cc>
---
docs/deployment.md | 8
The uwsgi service command didn't work without root, fix it by running the
entire expression under a shell with root privileges.
Signed-off-by: Russell Currey <rus...@russell.cc>
---
docs/deployment.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/deployment.md
On Thu, 2016-06-16 at 09:21 +1000, Andrew Donnellan wrote:
> On 15/06/16 19:07, Finucane, Stephen wrote:
> > The best option we might have, if per-series reporting is really
> > necessary, is to allow Check uploading against a Series endpoint. This
> > would actually cause N Checks to be
26 matches
Mail list logo
