NEW: devel/github-backup

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

NEW: devel/github-backup

Laurence Tratt
github-backup allows one to incrementally backup a github user and
repositories, including issues, pull requests and so on e.g.:

  github-backup ltratt -i -o <backup_dir> -t <oauth_token> --all

Note that although there is a PyPi package, the source download doesn't work
(don't ask me why), so the port uses GH_* instead.


Laurie
--
Personal                                             http://tratt.net/laurie/
Software Development Team                                http://soft-dev.org/
   https://github.com/ltratt              http://twitter.com/laurencetratt


github-backup.tgz (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: NEW: devel/github-backup

Stuart Henderson
On 2017/09/21 10:22, Laurence Tratt wrote:
> github-backup allows one to incrementally backup a github user and
> repositories, including issues, pull requests and so on e.g.:
>
>   github-backup ltratt -i -o <backup_dir> -t <oauth_token> --all

Likely too late for 6.2, but:


: # $OpenBSD: Makefile.template,v 1.76 2017/02/25 16:04:20 danj Exp $
:
: COMMENT = Backup a github user or organization

lowercase start of COMMENT

:
: MODPY_EGG_VERSION = 0.13.2
: DISTNAME = python-githup-backup-${MODPY_EGG_VERSION}
: PKGNAME = githup-backup-${MODPY_EGG_VERSION}
:
: GH_ACCOUNT = josegonzalez
: GH_PROJECT = python-github-backup
: GH_TAGNAME = ${MODPY_EGG_VERSION}

please zap the DISTNAME, it's the default

: CATEGORIES = devel
:
: HOMEPAGE = https://github.com/josegonzalez/python-github-backup

same, HOMEPAGE is the default

:
: MAINTAINER = Laurence Tratt <[hidden email]>
:
: PERMIT_PACKAGE_CDROM = Yes

needs a license marker

:
: MODULES = lang/python
: MODPY_SETUPTOOLS = Yes
: MODPY_VERSION = ${MODPY_DEFAULT_VERSION_2}
:
: .include <bsd.port.mk>

> Note that although there is a PyPi package, the source download doesn't work
> (don't ask me why), so the port uses GH_* instead.

I've seen that recently too, there's something on pypi that was redirecting
the old-style human-readable /packages/source/s/someproject/ URLs to the
hash-based ones instead (/packages/6b/03/84nnnnn/) which seems to no longer
be picking up new uploads.

Reply | Threaded
Open this post in threaded view
|

Re: NEW: devel/github-backup

Laurence Tratt
On Thu, Sep 21, 2017 at 10:53:03AM +0000, Stuart Henderson wrote:

Hello Stuart,

Thanks -- I've fixed and pushed to openbsd-wip based on your comments.

>> Note that although there is a PyPi package, the source download doesn't
>> work (don't ask me why), so the port uses GH_* instead.
> I've seen that recently too, there's something on pypi that was redirecting
> the old-style human-readable /packages/source/s/someproject/ URLs to the
> hash-based ones instead (/packages/6b/03/84nnnnn/) which seems to no longer
> be picking up new uploads.

Hmm, I guess the question is whether that's intentional or accidental on
their part...


Laurie
--
Personal                                             http://tratt.net/laurie/
Software Development Team                                http://soft-dev.org/
   https://github.com/ltratt              http://twitter.com/laurencetratt

Reply | Threaded
Open this post in threaded view
|

Re: NEW: devel/github-backup

Laurence Tratt
On Thu, Sep 21, 2017 at 11:02:28AM +0000, Laurence Tratt wrote:

Here's an updated version of devel/github-backup based on Stuart's pre-lock
comments. I think this is ready for importing, so am looking for OKs.

For those who've forgotten:

> github-backup allows one to incrementally backup a github user and
> repositories, including issues, pull requests and so on e.g.:
>
>   github-backup ltratt -i -o <backup_dir> -t <oauth_token> --all


Laurie
--
Personal                                             http://tratt.net/laurie/
Software Development Team                                http://soft-dev.org/
   https://github.com/ltratt              http://twitter.com/laurencetratt

github-backup.tgz (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: NEW: devel/github-backup

Edd Barrett-3
On Thu, Oct 12, 2017 at 10:55:53AM +0100, Laurence Tratt wrote:
> On Thu, Sep 21, 2017 at 11:02:28AM +0000, Laurence Tratt wrote:
>
> Here's an updated version of devel/github-backup based on Stuart's pre-lock
> comments. I think this is ready for importing, so am looking for OKs.

Has anyone had a chance to look at this?

--
Best Regards
Edd Barrett

http://www.theunixzoo.co.uk

Reply | Threaded
Open this post in threaded view
|

Re: NEW: devel/github-backup

Stuart Henderson
In reply to this post by Laurence Tratt
On 2017/10/12 10:55, Laurence Tratt wrote:

> On Thu, Sep 21, 2017 at 11:02:28AM +0000, Laurence Tratt wrote:
>
> Here's an updated version of devel/github-backup based on Stuart's pre-lock
> comments. I think this is ready for importing, so am looking for OKs.
>
> For those who've forgotten:
>
> > github-backup allows one to incrementally backup a github user and
> > repositories, including issues, pull requests and so on e.g.:
> >
> >   github-backup ltratt -i -o <backup_dir> -t <oauth_token> --all
>
>
> Laurie
> --
> Personal                                             http://tratt.net/laurie/
> Software Development Team                                http://soft-dev.org/
>    https://github.com/ltratt              http://twitter.com/laurencetratt



From README:

: Fortunately, basic use cases are fairly simple. First, you need to generate a
: GitHub OAuth token (Settings -> Personal Access Tokens -> Generate New Token).
: Then choose your use case.

It's currently in Settings -> Developer Settings -> Personal Access Tokens -> ..
It would be nice to suggest which permissions are actually needed as there are
many possibilities. (But then it would be nice if upstream mentioned this too :)

: To backup a single repository:
:
:   $ github-backup <organization> -N <repo regex> --all -o <output dir> \
:     -t <oauth token>

This would be <user> not <organization> wouldn't it?

Reply | Threaded
Open this post in threaded view
|

Re: NEW: devel/github-backup

Stuart Henderson
On 2017/11/11 13:43, Stuart Henderson wrote:

> On 2017/10/12 10:55, Laurence Tratt wrote:
> > On Thu, Sep 21, 2017 at 11:02:28AM +0000, Laurence Tratt wrote:
> >
> > Here's an updated version of devel/github-backup based on Stuart's pre-lock
> > comments. I think this is ready for importing, so am looking for OKs.
> >
> > For those who've forgotten:
> >
> > > github-backup allows one to incrementally backup a github user and
> > > repositories, including issues, pull requests and so on e.g.:
> > >
> > >   github-backup ltratt -i -o <backup_dir> -t <oauth_token> --all
> >
> >
> > Laurie
> > --
> > Personal                                             http://tratt.net/laurie/
> > Software Development Team                                http://soft-dev.org/
> >    https://github.com/ltratt              http://twitter.com/laurencetratt
>
>
>
> From README:
>
> : Fortunately, basic use cases are fairly simple. First, you need to generate a
> : GitHub OAuth token (Settings -> Personal Access Tokens -> Generate New Token).
> : Then choose your use case.
>
> It's currently in Settings -> Developer Settings -> Personal Access Tokens -> ..
> It would be nice to suggest which permissions are actually needed as there are
> many possibilities. (But then it would be nice if upstream mentioned this too :)
>
> : To backup a single repository:
> :
> :   $ github-backup <organization> -N <repo regex> --all -o <output dir> \
> :     -t <oauth token>
>
> This would be <user> not <organization> wouldn't it?

[...]  I'd be OK importing without the README (and associated PLIST entry)
for now and working on that later ...

Reply | Threaded
Open this post in threaded view
|

Re: NEW: devel/github-backup

Laurence Tratt
In reply to this post by Stuart Henderson
On Sat, Nov 11, 2017 at 01:43:07PM +0000, Stuart Henderson wrote:

Hello Stuart,

> From README:
> : Fortunately, basic use cases are fairly simple. First, you need to generate a
> : GitHub OAuth token (Settings -> Personal Access Tokens -> Generate New Token).
> : Then choose your use case.
> It's currently in Settings -> Developer Settings -> Personal Access Tokens -> ..

Erf. Updated. I wonder what it'll be called next week!

> It would be nice to suggest which permissions are actually needed as there
> are many possibilities. (But then it would be nice if upstream mentioned
> this too :)

I'm a bit nervous about this, as GitHub could change the number, or
semantics, of the permissions, and then we'd be inadvertently misleading
people until we noticed and updated the port (which, on stable, could be many
months). [I suspect, but can't be sure, that upstream might have the same
reasons for not documenting these things.] Fortunately, although there's
quite a few permissions, I found them to be fairly understandable.

> : To backup a single repository:
> :
> :   $ github-backup <organization> -N <repo regex> --all -o <output dir> \
> :     -t <oauth token>
> This would be <user> not <organization> wouldn't it?

Good spot!

I've pushed fixes to openbsd-wip.


Laurie
--
Personal                                             http://tratt.net/laurie/
Software Development Team                                http://soft-dev.org/
   https://github.com/ltratt              http://twitter.com/laurencetratt

Reply | Threaded
Open this post in threaded view
|

Re: NEW: devel/github-backup

Laurence Tratt
In reply to this post by Stuart Henderson
On Sat, Nov 11, 2017 at 01:44:32PM +0000, Stuart Henderson wrote:

Hello Stuart,

> [...]  I'd be OK importing without the README (and associated PLIST entry)
> for now and working on that later ...

Please find attached a tarball which does just that. Looking for other OKs
for import!


Laurie

github-backup.tgz (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: NEW: devel/github-backup

Laurence Tratt
On Thu, Nov 30, 2017 at 12:08:10PM +0000, Laurence Tratt wrote:

>> [...]  I'd be OK importing without the README (and associated PLIST entry)
>> for now and working on that later ...
> Please find attached a tarball which does just that. Looking for other OKs
> for import!

Still looking for a final OK or two... Or maybe I'm the only person who
worries about all the state of my github repositories disappearing ;)


Laurie
--
Personal                                             http://tratt.net/laurie/
Software Development Team                                http://soft-dev.org/
   https://github.com/ltratt              http://twitter.com/laurencetratt


github-backup.tgz (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: NEW: devel/github-backup

Stuart Henderson
It's already OK'd, just needs somebody who agrees with that to import it.
Free commit!


On 8 December 2017 13:22:06 Laurence Tratt <[hidden email]> wrote:

> On Thu, Nov 30, 2017 at 12:08:10PM +0000, Laurence Tratt wrote:
>
>>> [...]  I'd be OK importing without the README (and associated PLIST entry)
>>> for now and working on that later ...
>> Please find attached a tarball which does just that. Looking for other OKs
>> for import!
>
> Still looking for a final OK or two... Or maybe I'm the only person who
> worries about all the state of my github repositories disappearing ;)
>
>
> Laurie
> --
> Personal                                             http://tratt.net/laurie/
> Software Development Team                                http://soft-dev.org/
>    https://github.com/ltratt              http://twitter.com/laurencetratt
>