Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #12329 > unrolled thread

About itsdangerous

Back to article view | Back to linux.debian.maint.python

Contents

  About itsdangerous Julien Puydt <julien.puydt@laposte.net> - 2020-02-27 11:50 +0100
    Re: About itsdangerous Andrey Rahmatullin <wrar@debian.org> - 2020-02-27 11:50 +0100
      Re: About itsdangerous Julien Puydt <julien.puydt@laposte.net> - 2020-02-27 15:10 +0100
        Re: About itsdangerous Andrey Rahmatullin <wrar@debian.org> - 2020-02-27 15:20 +0100
          Re: About itsdangerous Julien Puydt <julien.puydt@laposte.net> - 2020-02-27 17:10 +0100
            Re: About itsdangerous Andrey Rahmatullin <wrar@debian.org> - 2020-02-27 17:20 +0100
            Re: About itsdangerous Dmitry Shachnev <mitya57@debian.org> - 2020-02-27 17:30 +0100

#12329 — About itsdangerous

Hi,

I saw python3-itsdangerous was far behind upstream, and decided to if
it was easy to update : but it's not on salsa.

Should I import the last known package version (recent upload to remove
the Python 2 package) to a new salsa repository and start from here?

Cheers,

JP

[toc] | [next] | [standalone]

#12330

[Multipart message — attachments visible in raw view] — view raw

On Thu, Feb 27, 2020 at 11:33:00AM +0100, Julien Puydt wrote:
> Hi,
> 
> I saw python3-itsdangerous was far behind upstream, and decided to if
> it was easy to update : but it's not on salsa.
> 
> Should I import the last known package version (recent upload to remove
> the Python 2 package) to a new salsa repository and start from here?
I think you should import the alioth backup and import the last upload on
top of it.

-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#12331

Le jeudi 27 février 2020 à 15:49 +0500, Andrey Rahmatullin a écrit :
> On Thu, Feb 27, 2020 at 11:33:00AM +0100, Julien Puydt wrote:
> > Hi,
> > 
> > I saw python3-itsdangerous was far behind upstream, and decided to
> > if
> > it was easy to update : but it's not on salsa.
> > 
> > Should I import the last known package version (recent upload to
> > remove
> > the Python 2 package) to a new salsa repository and start from
> > here?
> I think you should import the alioth backup and import the last
> upload on
> top of it.

Hmmm... I searched for "itsdangerous":
- on salsa ( 
https://salsa.debian.org/search?utf8=%E2%9C%93&search=itsdangerous&group_id=&project_id=&repository_ref=&nav_source=navbar
) : nothing
- on https://alioth-archive.debian.org/git/ : nothing

Is there some other place where I could have a look?

JP

[toc] | [prev] | [next] | [standalone]

#12332

[Multipart message — attachments visible in raw view] — view raw

On Thu, Feb 27, 2020 at 12:57:49PM +0100, Julien Puydt wrote:
> Le jeudi 27 février 2020 à 15:49 +0500, Andrey Rahmatullin a écrit :
> > On Thu, Feb 27, 2020 at 11:33:00AM +0100, Julien Puydt wrote:
> > > Hi,
> > > 
> > > I saw python3-itsdangerous was far behind upstream, and decided to
> > > if
> > > it was easy to update : but it's not on salsa.
> > > 
> > > Should I import the last known package version (recent upload to
> > > remove
> > > the Python 2 package) to a new salsa repository and start from
> > > here?
> > I think you should import the alioth backup and import the last
> > upload on
> > top of it.
> 
> Hmmm... I searched for "itsdangerous":
> - on salsa ( 
> https://salsa.debian.org/search?utf8=%E2%9C%93&search=itsdangerous&group_id=&project_id=&repository_ref=&nav_source=navbar
> ) : nothing
> - on https://alioth-archive.debian.org/git/ : nothing
https://alioth-archive.debian.org/git/collab-maint/python-itsdangerous.git.tar.xz

-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#12333

Le jeudi 27 février 2020 à 19:14 +0500, Andrey Rahmatullin a écrit :

> https://alioth-archive.debian.org/git/collab-maint/python-itsdangerous.git.tar.xz
> 

I must be going through a very bad day, but trying to follow 
https://wiki.debian.org/Salsa/AliothMigration#By_hand doesn't work ;
the two git checkout commands (both pristine-tar and upstream) give:
error: pathspec 'pristine-tar' did not match any file(s) known to git

Are we sure the original git repository had the correct structure
anyway?

JP

[toc] | [prev] | [next] | [standalone]

#12334

[Multipart message — attachments visible in raw view] — view raw

On Thu, Feb 27, 2020 at 05:02:32PM +0100, Julien Puydt wrote:
> > https://alioth-archive.debian.org/git/collab-maint/python-itsdangerous.git.tar.xz
> > 
> 
> I must be going through a very bad day, but trying to follow 
> https://wiki.debian.org/Salsa/AliothMigration#By_hand doesn't work ;
> the two git checkout commands (both pristine-tar and upstream) give:
> error: pathspec 'pristine-tar' did not match any file(s) known to git
> 
> Are we sure the original git repository had the correct structure
> anyway?
It indeed doesn't use pristine-tar. Its upstream branch is named master
(as you can check in debian/gbp.conf) and looks like a clone of the
upstream repo master branch. OTOH the last release there repacks the
tarball and so uses the master-dfsg branch instead.

-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#12335

[Multipart message — attachments visible in raw view] — view raw

Hi Julien!

On Thu, Feb 27, 2020 at 05:02:32PM +0100, Julien Puydt wrote:
> Le jeudi 27 février 2020 à 19:14 +0500, Andrey Rahmatullin a écrit :
>
> > https://alioth-archive.debian.org/git/collab-maint/python-itsdangerous.git.tar.xz
> > 
>
> I must be going through a very bad day, but trying to follow 
> https://wiki.debian.org/Salsa/AliothMigration#By_hand doesn't work ;
> the two git checkout commands (both pristine-tar and upstream) give:
> error: pathspec 'pristine-tar' did not match any file(s) known to git
>
> Are we sure the original git repository had the correct structure
> anyway?

Looking at that repo, it did not have the correct structure, but I think
it makes sense to preserve its history anyway. I would do the following
with branches:

debian/unstable — rename to debian/master
master-dfsg — rename to upstream

Also update branch names in debian/gbp.conf accordingly. And gbp should create
a pristine-tar branch when you update to a newer release.

--
Dmitry Shachnev

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web