X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by lists.alpinelinux.org (Postfix) with ESMTP id 6D23F1EB587 for ; Mon, 25 Oct 2010 14:36:18 +0000 (UTC) Received: by wwe15 with SMTP id 15so3579220wwe.25 for ; Mon, 25 Oct 2010 07:36:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:reply-to:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=Ti7K4E4sla2KzxojK8seTTCYz5R19I709P3gdINSGXg=; b=FQMnrJyyIqrBCTbbDj6AoH6BZCKwpjBhBmHlpfX0AqcBoiRWrnxWPcwXruSBcq43bi Opd9Wt55mH+H+bl/cguMKgvMW60/ByeDMMR98uWVkivmou2XZTiwLrvAuu3KNjstzCYR BZ3sAeKcH78cioQ1eM8+3GkGevpfKl0r6h8/s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=B4iR7D5nXiEjqwCnXkJPkIMhyDgngehI4O93O5yKwlXIOxSy9KAQGTpD6dmT4ZcyAR DNcjT8T3dgjnfaAt0CWDPa22ttRxITfv/Coyn2gLPsEHbb8kGgIzB4OJzG3lMoiLAVXg gMzHaXIJNYdNS8yBA1jVAwwJbVDi0pONuJAxk= Received: by 10.227.142.146 with SMTP id q18mr6498950wbu.163.1288017376364; Mon, 25 Oct 2010 07:36:16 -0700 (PDT) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Sender: jeremythomerson@gmail.com Reply-To: jeremy@thomersonfamily.com Received: by 10.216.230.69 with HTTP; Mon, 25 Oct 2010 07:35:56 -0700 (PDT) In-Reply-To: <1287995976.13130.17.camel@ncopa-desktop.nor.wtbts.net> References: <1287637719-9886-1-git-send-email-jeremy@thomersonfamily.com> <1287637719-9886-2-git-send-email-jeremy@thomersonfamily.com> <1287995976.13130.17.camel@ncopa-desktop.nor.wtbts.net> From: Jeremy Thomerson Date: Mon, 25 Oct 2010 09:35:56 -0500 X-Google-Sender-Auth: 7SEtOj982J67CvT3tbjwE0VdGDg Message-ID: Subject: Re: [alpine-devel] [PATCH 2/2] create new package for rdiff-backup To: Natanael Copa Cc: alpine-devel@lists.alpinelinux.org Content-Type: multipart/alternative; boundary=0016e64f44842ec71b049371ea17 --0016e64f44842ec71b049371ea17 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Oct 25, 2010 at 3:39 AM, Natanael Copa wrote: > On Thu, 2010-10-21 at 05:08 +0000, Jeremy Thomerson wrote: > > --- > > testing/rdiff-backup/APKBUILD | 26 ++++++++++++++++++++++++++ > > This looks like an interesting project. Talked the other day with Timo > (fabled) about simplifying updating CF installs with Alpine Linux. > Currently you need to download the iso image, mount it, copy the files > to CF and reboot. This can be done with the setup-bootable tool, but > still, its not efficient. So we talked about alternatives. > > rdiff-backup might be worth look at for that purpose. > I've used rdiff-backup for several years to backup my home fileserver to an offsite location. The save-a-diff functionality has saved me several times where rsync overwriting the previous file would have killed me. For instance, you accidentally echo "" > some-important-file, but don't realize it until a day or two later. rsync would have blown away my remote backup, too. With rdiff, I can restore from a previous point in time (like version control for backups). > > 1 files changed, 26 insertions(+), 0 deletions(-) > > create mode 100644 testing/rdiff-backup/APKBUILD > > It fails to build: > ... > copying rdiff_backup/rpath.py -> build/lib.linux-i686-2.6/rdiff_backup > copying rdiff_backup/log.py -> build/lib.linux-i686-2.6/rdiff_backup > running build_ext > error: invalid Python installation: unable to > open /usr/include/python2.6/pyconfig.h (No such file or directory) > ... > > > +makedepends="librsync-dev" > ^^^ > It needs python-dev in makedepends > > Care to resend? > > Thanks! > -nc > > Sure, I have some questions that I'm hoping you can help me with to get better at this. It built for me, which must mean that I installed python-dev at some point during my trial-and-error approach to creating these aports. Is there some way to know "hey, this thing is dependent on something that I already have installed on my system"? Do you just build on a box with absolutely nothing installed (only alpine-sdk for instance)? Jeremy --0016e64f44842ec71b049371ea17 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Mon, Oct 25, 2010 at 3:39 AM, Natanael Co= pa <ncopa@alp= inelinux.org> wrote:
On Thu, 2010-10-21 at 05:08 +0000, Jeremy Thomerson wrote= :
> ---
> =A0testing/rdiff-backup/APKBUILD | =A0 26 ++++++++++++++++++++++++++
This looks like an interesting project. Talked the other day with Tim= o
(fabled) about simplifying updating CF installs with Alpine Linux.
Currently you need to download the iso image, mount it, copy the files
to CF and reboot. This can be done with the setup-bootable tool, but
still, its not efficient. So we talked about alternatives.

rdiff-backup might be worth look at for that purpose.
=
I've used rdiff-backup for several years to backup my ho= me fileserver to an offsite location. =A0The save-a-diff functionality has = saved me several times where rsync overwriting the previous file would have= killed me. =A0For instance, you accidentally echo "" > some-i= mportant-file, but don't realize it until a day or two later. =A0rsync = would have blown away my remote backup, too. =A0With rdiff, I can restore f= rom a previous point in time (like version control for backups).
=A0
> =A01 files changed, 26 insertions(+), 0 deletions(-)=
> =A0create mode 100644 testing/rdiff-backup/APKBUILD

It fails to build:
...
copying rdiff_backup/rpath.py -> build/lib.linux-i686-2.6/rdiff_backup copying rdiff_backup/log.py -> build/lib.linux-i686-2.6/rdiff_backup
running build_ext
error: invalid Python installation: unable to
open /usr/include/python2.6/pyconfig.h (No such file or directory)
...
=A0
> +makedepends=3D"librsync-dev"
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0^^^
It needs python-dev in makedepends

Care to resend?

Thanks!
-nc


Sure, I have some questions that I'm= hoping you can help me with to get better at this.

It built for me, which must mean that I installed python-dev at some poin= t during my trial-and-error approach to creating these aports. =A0Is there = some way to know "hey, this thing is dependent on something that I alr= eady have installed on my system"? =A0Do you just build on a box with = absolutely nothing installed (only alpine-sdk for instance)?

Jeremy
--0016e64f44842ec71b049371ea17-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---