From nobody Fri Mar 29 08:36:30 2024 X-Original-To: alpine-aports@lists.alpinelinux.org Received: from mail-yb1-f176.google.com (mail-yb1-f176.google.com [209.85.219.176]) by lists.alpinelinux.org (Postfix) with ESMTP id F3313F81636 for ; Thu, 14 Feb 2019 14:59:54 +0000 (UTC) Received: by mail-yb1-f176.google.com with SMTP id 18so864244ybf.8 for ; Thu, 14 Feb 2019 06:59:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=DfDpxg6arPuCjuz5dCx2rJCvwEJpwT1RdbXbUPSEkMc=; b=dwoFjmXyqWNGXDssMJLz33SW2pyZwIHgJqK5lucdPmBf4a4uswb5xZUXY0jtGDT1Kd bSyDgilN6I3DfVowu957zTR+/oa2y78n6oUStPW7h/xfCVq4B9WPcv/V8DjwdXWjvsyZ gU2jlc7UO4ih8c8UiNAhNDfjBA1Er8kLkDd4D074FaC99lwIw83MylkVXVw2EUk9s9qr u2I9AhoCxvNAcWnapK49D3Hz4VTjO40zyevKzvZ3Kw5GO0DYX33HI/biY6le6wTGu6gM Zdh4YGwTm6gb/kWPM6QFTN+nQBTv6ow19zSAqSsdBCKfkFIDN/rPOA3NOaJxP3WxoT2D AYXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=DfDpxg6arPuCjuz5dCx2rJCvwEJpwT1RdbXbUPSEkMc=; b=gX2uNYmadiPHNeFkQCF5TR59RMJDleeZVcnT5soj+se5u+u22ZPNuvnEz89lK+dllw LnijCiYBY366feHv9Td+xYlqSeDJoMsDS7dZNow4eU1qgNo4l8Pi7mSkd4ewgD5aNjpG TShiZ7pbm7QNUdyyfQiwxYFFUehQM46HJcINSqvnZAYzU6gd+iTfH6ufYF/96a1ZQP+l AeEag1Boldv/Y+8alhMlQONu5tFK+mligMpoG9WA+fIiX4zi3v/Ujded8kMTk/kAyiYH Y2sc7R8G7Agm9qEGdg83wzERsB8lvrC4yGyOgLkl/ODSM0RQp5zO1lNh3sYp0p5RelxI UE8A== X-Gm-Message-State: AHQUAubbBtApzr6JI6hvWoZTmMJ0jZoyi9kLLjjjLE1949vJZxgOrQ/w U/Pa0TVlvO7Nkse3kqGv38SAL4v5o3K40bPakuMpmbqw X-Google-Smtp-Source: AHgI3IbCKd1FJwBq/L25uv/6VtPAxHtor3VcX6C3CXh2yMEh9xl5wwnrDkbaip/VlbEAinVpsGh7LD04ubmS8swgFRg= X-Received: by 2002:a25:3043:: with SMTP id w64mr3666217ybw.428.1550156394175; Thu, 14 Feb 2019 06:59:54 -0800 (PST) X-Mailinglist: alpine-aports Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 From: Andrew Bell Date: Thu, 14 Feb 2019 09:59:43 -0500 Message-ID: Subject: [alpine-aports] PR Merge? To: alpine-aports@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="00000000000038a25d0581dbe986" --00000000000038a25d0581dbe986 Content-Type: text/plain; charset="UTF-8" Hi, I made a PR from to the github aports repo a while ago and haven't heard anything. There seem to be a lot of PRs there just waiting with no feedback. Is there a part of the process that I'm not understanding to get a PR merged? Do you need help to manage these changes? Thanks, -- Andrew Bell andrew.bell.ia@gmail.com --00000000000038a25d0581dbe986 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I made a PR from to the github apor= ts=C2=A0repo a while ago and haven't heard anything.=C2=A0 There seem t= o be a lot of PRs there just waiting with no feedback.=C2=A0 Is there a par= t of the process that I'm not understanding to get a PR merged?=C2=A0 D= o you need help to manage these changes?

Thanks,

--
--00000000000038a25d0581dbe986-- --- Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org Help: alpine-aports+help@lists.alpinelinux.org --- From nobody Fri Mar 29 08:36:30 2024 X-Original-To: alpine-aports@lists.alpinelinux.org Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) by lists.alpinelinux.org (Postfix) with ESMTP id 2CA3EF815D3 for ; Sat, 16 Feb 2019 22:31:36 +0000 (UTC) Received: from bell.riseup.net (unknown [10.0.1.178]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 7A0411A04F4 for ; Sat, 16 Feb 2019 14:31:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1550356295; bh=20xvqVapKEbdvFoKBKWDQxdMHSO0TeMjTiheAL7Kdqo=; h=Date:From:To:Subject:In-Reply-To:References:From; b=hSVwNbeuhwYbU1vSuxgx/XFVLFG6yNJ8brGsN8s0fxd1LFxznP9S90Ygl7kqEuMl5 Ciet42o3Nm/S11McdChtteT879/6eknOyDfAeRsvuB/jH50sC8GnLIJQyb1EyHnIb+ 6sQGnOUiivzlK09P+Q5pi1d16LAXOYCQGICqZptk= X-Riseup-User-ID: 09A77AA144E2603D0558C7F0787FAE770CAF9E76703C80DC89896B30C695CF2C Received: from [127.0.0.1] (localhost [127.0.0.1]) by bell.riseup.net (Postfix) with ESMTPSA id 64634221EE6 for ; Sat, 16 Feb 2019 14:31:35 -0800 (PST) X-Mailinglist: alpine-aports Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Date: Sat, 16 Feb 2019 14:31:35 -0800 From: ghostbar@riseup.net To: alpine-aports@lists.alpinelinux.org Subject: Re: [alpine-aports] PR Merge? In-Reply-To: References: Message-ID: Hi Andrew, You need to send a patch to the aports mailing lists. The PR method is not used for contributions in alpine. You can read more on how to it here: https://wiki.alpinelinux.org/wiki/Creating_patches On 2019-02-14 09:59, Andrew Bell wrote: > Hi, > > I made a PR from to the github aports repo a while ago and haven't > heard anything. There seem to be a lot of PRs there just waiting with > no feedback. Is there a part of the process that I'm not > understanding to get a PR merged? Do you need help to manage these > changes? > > Thanks, > > -- > Andrew Bell > andrew.bell.ia@gmail.com --- Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org Help: alpine-aports+help@lists.alpinelinux.org --- From nobody Fri Mar 29 08:36:30 2024 X-Original-To: alpine-aports@lists.alpinelinux.org Received: from mail-yw1-f50.google.com (mail-yw1-f50.google.com [209.85.161.50]) by lists.alpinelinux.org (Postfix) with ESMTP id 66D37F816B2 for ; Sun, 17 Feb 2019 01:02:39 +0000 (UTC) Received: by mail-yw1-f50.google.com with SMTP id d190so5125223ywd.12 for ; Sat, 16 Feb 2019 17:02:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ba6DAu25wAl9R4dz3Fdwdu61/875HVDjAUTdmDc6VOU=; b=kxyX2R40jjIUhh/9s3rRej67PitsjEaAvO1RjopmSflyW0LZ9t7jpHOJjdNpQMTJKL sJFtUGWErOPZ0WIhYY1vHgbNnubO/i1TIL6ICTTLlElEKLr2DkMcy42kPOGWHNq1oNoC xgwHa+/ywAVLR+3vuKZGs4ufKRNwi3kh0wj7s9CQOTzDHBUmruX84/3iNuBB+hyhoCLG FgtDZGFbo2pNgyFh00uxDBXx9sM05HD/Bm7QtZPg5KKzGqVLO8xuerAbehROcVqkaPqx 8ucCRzZYE07MXQBPmmAZNoj811PrxQilBvFpMcgABcW1nPjx5gluRvTVIWpoCGSgD4JJ N0Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ba6DAu25wAl9R4dz3Fdwdu61/875HVDjAUTdmDc6VOU=; b=OTVhEQs3O2csWra0YwGToTiTUCWR3EG52rj8zrn5yvf/TFRQCYMl+ofjO2G4t3avPB guRM/jZy3BvqHw7miIeQ9fDhj4SCW2vMfcP2wagKJ/55jMWJ5X4T9QYP3WhGwjjh8KoW K2bQ9T6+zWpIOHkri6s3xg7LG7qGKD3Bs97JTvDDsK/rLM+BH8C9NVvKy6eQCgGnHZZd 5b7zbwYETjzXSzywBnO9GF1TpezNjn0JvdwCZnzECIRu21L+ETzagxv/Pv2tZsjv8kWs yZgugEt5wXKDHOOT5ozkuyn/63lKXduME5dEXOEgLxAfCYC/cyvrNzlfHt7PFqjQqTXB QlFQ== X-Gm-Message-State: AHQUAubZkjimznGyWd/bG1wppUspOacaiK8OOFtjnlXKoPKG4g8XoSDg kilaJL4eN1nSKLXN3IlQ5FU5UiSYSkU+eDI4CHI= X-Google-Smtp-Source: AHgI3IYrxDOx9Gc67a3uMaqk3S/+Yit41cjupQgZFS/mrVIK+Pl0sjsOEnPuvpIDoLyD4QwnKz/VhQ4QW+50uDYe7W0= X-Received: by 2002:a81:7c0a:: with SMTP id x10mr13708352ywc.259.1550365358907; Sat, 16 Feb 2019 17:02:38 -0800 (PST) X-Mailinglist: alpine-aports Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 References: In-Reply-To: From: Andrew Bell Date: Sat, 16 Feb 2019 20:02:33 -0500 Message-ID: Subject: Re: [alpine-aports] PR Merge? To: ghostbar@riseup.net Cc: alpine-aports@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="0000000000007d681605820c90eb" --0000000000007d681605820c90eb Content-Type: text/plain; charset="UTF-8" It would be nice if this was clear on this page: https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package The implication is that you can make a PR from the github repo. Thanks, On Sat, Feb 16, 2019 at 5:31 PM wrote: > Hi Andrew, > > You need to send a patch to the aports mailing lists. The PR method is > not used for contributions in alpine. You can read more on how to it > here: https://wiki.alpinelinux.org/wiki/Creating_patches > > On 2019-02-14 09:59, Andrew Bell wrote: > > Hi, > > > > I made a PR from to the github aports repo a while ago and haven't > > heard anything. There seem to be a lot of PRs there just waiting with > > no feedback. Is there a part of the process that I'm not > > understanding to get a PR merged? Do you need help to manage these > > changes? > > > > Thanks, > > > > -- > > Andrew Bell > > andrew.bell.ia@gmail.com > > > --- > Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org > Help: alpine-aports+help@lists.alpinelinux.org > --- > > -- Andrew Bell andrew.bell.ia@gmail.com --0000000000007d681605820c90eb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

It would be ni= ce if this was clear on this page:=C2=A0https://wiki.alpinelinux.org/wiki/Cre= ating_an_Alpine_package

The implication is that you can make a P= R from the github=C2=A0repo.

Thanks,

On Sat, Feb 16, 2019 at 5:31 PM <ghostbar@riseup.net> wrote:
Hi Andrew,

You need to send a patch to the aports mailing lists. The PR method is
not used for contributions in alpine. You can read more on how to it
here: https://wiki.alpinelinux.org/wiki/Creating_p= atches

On 2019-02-14 09:59, Andrew Bell wrote:
> Hi,
>
> I made a PR from to the github aports repo a while ago and haven't=
> heard anything.=C2=A0 There seem to be a lot of PRs there just waiting= with
> no feedback.=C2=A0 Is there a part of the process that I'm not
> understanding to get a PR merged?=C2=A0 Do you need help to manage the= se
> changes?
>
> Thanks,
>
> --
> Andrew Bell
> andrew.b= ell.ia@gmail.com


---
Unsubscribe:=C2=A0 alpine-aports+unsubscribe@lists.alpinelinux.= org
Help:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0alpine-aports+help@lists.alpine= linux.org
---



--
--0000000000007d681605820c90eb-- --- Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org Help: alpine-aports+help@lists.alpinelinux.org --- From nobody Fri Mar 29 08:36:30 2024 X-Original-To: alpine-aports@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id EA7F2F815B9 for ; Wed, 20 Feb 2019 12:11:44 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 614299E1EBE; Wed, 20 Feb 2019 12:11:44 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 1F8C79E0400; Wed, 20 Feb 2019 12:11:42 +0000 (UTC) Date: Wed, 20 Feb 2019 13:11:38 +0100 From: Natanael Copa To: Andrew Bell Cc: ghostbar@riseup.net, alpine-aports@lists.alpinelinux.org Subject: Re: [alpine-aports] PR Merge? Message-ID: <20190220131138.618fd73c@ncopa-desktop.copa.dup.pw> In-Reply-To: References: X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-alpine-linux-musl) X-Mailinglist: alpine-aports Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, You can send patch via github PR or via git send-email to alpine-aports mailing list. If you have a trivial patch you can also do: `git format-patch -1 --stdout | tpaste` and post the URL on IRC Freenode #alpine-devel channel if you have the attention of a developer with git push access. I have been on vacation for a month and we have been pretty busy with the 3.9 release so we have falling behind with the PR queue. Sorry for that. Do you have the URL to the github PR? -nc On Sat, 16 Feb 2019 20:02:33 -0500 Andrew Bell wrote: > It would be nice if this was clear on this page: > https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package > > The implication is that you can make a PR from the github repo. > > Thanks, > > On Sat, Feb 16, 2019 at 5:31 PM wrote: > > > Hi Andrew, > > > > You need to send a patch to the aports mailing lists. The PR method is > > not used for contributions in alpine. You can read more on how to it > > here: https://wiki.alpinelinux.org/wiki/Creating_patches > > > > On 2019-02-14 09:59, Andrew Bell wrote: > > > Hi, > > > > > > I made a PR from to the github aports repo a while ago and haven't > > > heard anything. There seem to be a lot of PRs there just waiting with > > > no feedback. Is there a part of the process that I'm not > > > understanding to get a PR merged? Do you need help to manage these > > > changes? > > > > > > Thanks, > > > > > > -- > > > Andrew Bell > > > andrew.bell.ia@gmail.com > > > > > > --- > > Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org > > Help: alpine-aports+help@lists.alpinelinux.org > > --- > > > > > --- Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org Help: alpine-aports+help@lists.alpinelinux.org --- From nobody Fri Mar 29 08:36:30 2024 X-Original-To: alpine-aports@lists.alpinelinux.org Received: from mail-yb1-f179.google.com (mail-yb1-f179.google.com [209.85.219.179]) by lists.alpinelinux.org (Postfix) with ESMTP id 925D5F8147F for ; Wed, 20 Feb 2019 17:23:45 +0000 (UTC) Received: by mail-yb1-f179.google.com with SMTP id j85so6559291ybg.11 for ; Wed, 20 Feb 2019 09:23:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j0g1zQaSOkTWYF9O4iPFrhLSfeThSyaeuGWS7qQYsjg=; b=kImKFYTe7EVim5Aohax8rFDB2srfLJqx6+Y8prRDbvsejjxnGIhcfz++77CI932JhL efqoGJGNlX+mKZJKqrs5pa6DL2ja0XH8rpH5wZL1Khp1WJzi8p/C5c7hK8BimXh/mAnA SMSheGNtPg8hiNG8m2Xgv/ybXCqe9wjS6zrdiluNTwl+DzYpj3IsGY5Gl1Tna81gJYY+ 6zOk1FCl2hnhMdIIXHuHO4gyfzSWZJWmm0S1dBpm7UC7w4VHr30i9FyElFADvwSkLyEJ wknwcFQgfNbLPNY1VOPQmqGLNWQX+o//Ywn8npVt1QSX0sawfzslkEdDM326InOjtpzl ev9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j0g1zQaSOkTWYF9O4iPFrhLSfeThSyaeuGWS7qQYsjg=; b=aXBJGppnXHIOJheUYqvlDuMqs/51OZaReRDnrQ5Zi6nSc4GwJ5hGPpOOEhkgCczXjt 7iOFzhktEzrF/YncGp41039v33KGYhj+RSQOeiNlQNsfm8ea4CCrascEX2j9nzeB6LXV nKVoyiNouCa17wRj42kalzy1h/Rd9w6Dih1o7Jfp0msbeydBDw5Pa0YEKtu0HQifvMHV 1DYaLABA6iLr0zoGBJp7E9ugN7kzj6nTqR2TliGkhJPwpseucaO2TISQgX36P/pwZUcp j701xQoo/LJ00xNwtwiRbZqJ3nXHCEyQ7XXFvgsJdAhDWeo/t97gc75uYGuItmduZ3vc +Cdw== X-Gm-Message-State: AHQUAubdY1BHQ2OWsYhFTn65ApTahooTsPtnxW/WE2KN2QUkS8CgOJL4 rfB4CjfBrg6Y6D2fOtCk9s97oRnc7s+VGEiUxKI= X-Google-Smtp-Source: AHgI3IY3y+tCm5muIq3NKu71SdswMJaW48YTkME/O3Gju4t0rtfRA3Ho20HWxn9lqeg/e5oHUoKabddsVmoYfjD5mGo= X-Received: by 2002:a25:4654:: with SMTP id t81mr28189314yba.59.1550683424938; Wed, 20 Feb 2019 09:23:44 -0800 (PST) X-Mailinglist: alpine-aports Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 References: <20190220131138.618fd73c@ncopa-desktop.copa.dup.pw> In-Reply-To: <20190220131138.618fd73c@ncopa-desktop.copa.dup.pw> From: Andrew Bell Date: Wed, 20 Feb 2019 12:23:33 -0500 Message-ID: Subject: Re: [alpine-aports] PR Merge? To: Natanael Copa Cc: ghostbar@riseup.net, alpine-aports@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="000000000000b3df790582569ee8" --000000000000b3df790582569ee8 Content-Type: text/plain; charset="UTF-8" On Wed, Feb 20, 2019 at 7:11 AM Natanael Copa wrote: > Hi, > > You can send patch via github PR or via git send-email to alpine-aports > mailing list. If you have a trivial patch you can also do: > > `git format-patch -1 --stdout | tpaste` > > and post the URL on IRC Freenode #alpine-devel channel if you have the > attention of a developer with git push access. > Thanks. I just wasn't sure of the process and the PR had been sitting a while. > I have been on vacation for a month and we have been pretty busy with > the 3.9 release so we have falling behind with the PR queue. Sorry for > that. > > Do you have the URL to the github PR? > https://github.com/alpinelinux/aports/pull/6252 I think this has been taken care of and can be closed. I believe GDAL will build with GEOS support automatically if it's found without the explicit --with-geos configuration option. The geos-dev dependency should do that. Thanks, -- Andrew Bell andrew.bell.ia@gmail.com --000000000000b3df790582569ee8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Feb 20, 2019= at 7:11 AM Natanael Copa <ncop= a@alpinelinux.org> wrote:
Hi,

You can send patch via github PR or via git send-email to alpine-aports=
mailing list. If you have a trivial patch you can also do:

=C2=A0 `git format-patch -1 --stdout | tpaste`

and post the URL on IRC Freenode #alpine-devel channel if you have the<= br>attention of a developer with git push access.

=
Thanks.=C2=A0 I just wasn't sure of the process and the PR h= ad been sitting a while.
=C2=A0
I have been on vacation for a month and we have been = pretty busy with
the 3.9 release so we have falling behind with the PR q= ueue. Sorry for
that.

Do you have the URL to the github PR?

https://gith= ub.com/alpinelinux/aports/pull/6252

I think th= is has been taken care of and can be closed.=C2=A0 I believe GDAL will=C2= =A0build with GEOS support automatically if it's found without the expl= icit --with-geos=C2=A0configuration option.=C2=A0 The geos-dev dependency s= hould do that.

Thanks,

-= -
--000000000000b3df790582569ee8-- --- Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org Help: alpine-aports+help@lists.alpinelinux.org ---