Patch tagging/classification

Ruslan Kuprieiev kupruser at
Tue Feb 9 08:25:27 AEDT 2016

On 02/08/2016 08:50 PM, Damien Lespiau wrote:
> On Mon, Feb 08, 2016 at 08:08:58PM +0200, Ruslan Kuprieiev wrote:
>>> As mentioned before, Freedesktop's patchwork has a somewhat strong
>>> opinion on distribution dependencies. It favours deploying patchwork in
>>> an isolated, sateless, WM/container (or at least in a virtualenv) with a
>>> tight control on the versions of those dependencies (as opposed to
>>> relying on the distribution packages). People have voiced concerns about
>>> this, but I find it rather freeing.
>> I totally support this opinion. From a user standpoint, that doesn't
>> want to get into deep fiddling with packages and configurations of DBs
>> and Django, I would prefer to just download, unpack, do 2-3 additional
>> trivial steps and have my own patchwork ready to serve my mailing list
>> =)
>> Do you have your patchwork version in a easy-to-deploy form? If you
>> do, would mind sharing it? I would love to try it out.
> Unfortunately, I don't have anything to share. Right now, each admin has
> to figure out how patchwork can fit in the existing infrastructure (and
> there are quite a few combinations). I myself use fabric
> ( to automate the deployment of patchwork, but
> that only works with a manual first installation.
> I can see how a better story for both the installation and updates of
> patchwork is needed, as well as a few supported ways to hook an existing
> mailing-list that isn't necessarily on the same host as patchwork.
> I think it should be fairly straightforward to make a docker image with
> PostgreSQL, django and patchwork. To feed emails to patchwork, I'd
> create a new REST entry point that would accept emails given the proper
> credentials. Basically the same code as today but decoupling patchwork
> from the host the mailing-list is hosted on. Then, mail delivery to
> patchwork could be hooked to anything: local delivery (/etc/aliases and
> local(8) as documented today) or a script feeding emails from any source
> (eg. fetchmail + procmail).
> I've added it to the TODO list but, time is scarce.

In my hand-made solution I used smtp and pop3 python modules to fetch
mail for a configured gmail account that is subscribed to a certain 
mailing list.
Fetching and sending was quite easy and worked well, even considering gmail
restriction on allowed frequency of checking email(once in 5-8 minutes 
was fine).
So yeah, ability to use both mailing list and arbitrary email subscribed 
to that
mailing list would be quite handy, especially for development, allowing 
to tryout patchwork somewhere safe and not pollute production server 
just yet.

Docker file with a list of needed packages and commands would be great.

I'll try to set up patchwork once again by the end of this week and will 
try to
provide some feedback or even some changes to docs to make things clear
for newbies like myself.


More information about the Patchwork mailing list