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

Git migration schedule

Started by	Barry Warsaw <barry@debian.org>
First post	2015-10-02 16:30 +0200
Last post	2015-10-22 10:30 +0200
Articles	20 on this page of 79 — 20 participants

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

  Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-02 16:30 +0200
    Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-02 22:50 +0200
      Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-02 23:10 +0200
      Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-03 11:50 +0200
        Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-03 12:50 +0200
          Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-03 16:30 +0200
            Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-03 17:00 +0200
              Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-03 20:10 +0200
          Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-03 21:00 +0200
            Re: Git migration schedule Daniele Tricoli <eriol@mornie.org> - 2015-10-03 21:50 +0200
              Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-03 22:30 +0200
            Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-04 21:10 +0200
              Re: Git migration schedule Julien Puydt <julien.puydt@laposte.net> - 2015-10-04 21:30 +0200
              Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-04 21:40 +0200
                Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-04 23:10 +0200
                  Re: Git migration schedule IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-05 12:10 +0200
                    Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-05 22:40 +0200
                      Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 23:30 +0200
                        Re: Git migration schedule IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-06 09:40 +0200
                Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 18:00 +0200
              Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-04 23:10 +0200
              Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 17:50 +0200
                Re: Git migration schedule Scott Kitterman <debian@kitterman.com> - 2015-10-05 18:30 +0200
                Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-06 02:40 +0200
                  Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-08 17:10 +0200
              Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 18:00 +0200
                Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 22:40 +0200
                Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-05 22:40 +0200
            Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 17:40 +0200
              Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-09 10:30 +0200
                Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 01:10 +0200
                  Re: Git migration schedule Ben Finney <ben+debian@benfinney.id.au> - 2015-10-10 03:20 +0200
                    Re: Git migration schedule Mattia Rizzolo <mattia@mapreri.org> - 2015-10-10 03:50 +0200
                    Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 04:40 +0200
                    Re: Git migration schedule Barry Warsaw <barry@python.org> - 2015-10-10 21:10 +0200
                      Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-11 10:30 +0200
                        Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-18 03:00 +0200
            Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 17:50 +0200
            Re: Git migration schedule Daniel Stender <debian@danielstender.com> - 2015-10-05 21:00 +0200
            Re: Git migration schedule Barry Warsaw <barry@python.org> - 2015-10-06 01:20 +0200
              Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-06 01:30 +0200
    Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-08 17:10 +0200
      Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-09 02:00 +0200
        Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-09 10:00 +0200
          Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 00:40 +0200
            Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-10 01:00 +0200
              Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-11 02:30 +0200
                Re: Git migration schedule Raphael Hertzog <hertzog@debian.org> - 2015-10-12 09:10 +0200
                Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-12 21:40 +0200
      Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-09 10:10 +0200
        Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-09 16:50 +0200
          Re: Git migration schedule Arthur de Jong <adejong@debian.org> - 2015-10-09 18:50 +0200
            Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-09 19:40 +0200
              Re: Git migration schedule Arthur de Jong <adejong@debian.org> - 2015-10-09 21:30 +0200
        Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 00:30 +0200
          Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-11 10:30 +0200
      Re: Git migration schedule pushback permissions/DEP-3 workflow Daniel Stender <debian@danielstender.com> - 2015-10-12 20:20 +0200
        Re: Git migration schedule pushback permissions/DEP-3 workflow Daniele Tricoli <eriol@mornie.org> - 2015-10-12 20:30 +0200
    Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 00:20 +0200
      Re: Git migration schedule IOhannes m zmölnig <zmoelnig@umlaeute.mur.at> - 2015-10-10 21:40 +0200
    Re: Git migration schedule Jean-Michel Vourgère <nirgal@debian.org> - 2015-10-18 22:10 +0200
      Re: Git migration schedule Piotr Ożarowski <piotr@debian.org> - 2015-10-18 23:10 +0200
      Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-19 19:20 +0200
        Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-19 23:40 +0200
          Re: Git migration schedule Raphael Hertzog <hertzog@debian.org> - 2015-10-21 10:00 +0200
        Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-19 23:40 +0200
          Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-20 16:10 +0200
            Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-21 09:40 +0200
              Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-21 16:50 +0200
                Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-21 23:40 +0200
                  Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-22 00:10 +0200
                    Re: Git migration schedule Sandro Tosi <sandro.tosi@gmail.com> - 2015-10-22 00:30 +0200
                      Re: Git migration schedule Raphael Hertzog <hertzog@debian.org> - 2015-10-22 09:20 +0200
                        Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-23 01:50 +0200
                      Re: Git migration schedule Julien Puydt <julien.puydt@laposte.net> - 2015-10-22 10:00 +0200
                        Re: Git migration schedule Piotr Ożarowski <piotr@debian.org> - 2015-10-22 10:10 +0200
                        pristine-tar (was: Git migration schedule) "W. Martin Borgert" <debacle@debian.org> - 2015-10-22 13:10 +0200
                          Re: pristine-tar (was: Git migration schedule) Barry Warsaw <barry@debian.org> - 2015-10-23 01:50 +0200
                      Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-22 10:30 +0200

Page 3 of 4 — ← Prev page 1 2 [3] 4 Next page →

#7486

From	Barry Warsaw <barry@debian.org>
Date	2015-10-06 01:30 +0200
Message-ID	<qgnmG-5iM-9@gated-at.bofh.it>
In reply to	#7485

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

On Oct 05, 2015, at 07:12 PM, Barry Warsaw wrote:

>I did an update (not uploaded) of webob from this migration and it worked
>perfectly.  But it's a simple package without patches.  I'll try a few more.

Similarly for ply 3.8.  The nice thing here is that there were several quilt
patches that got applied upstream and were no longer necessary.  git-dpm
recognized this and automatically deleted those patches.

For both packages `git-dpm tag` DTRT.

Cheers,
-Barry

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

#7561

From	Stefano Rivera <stefanor@debian.org>
Date	2015-10-08 17:10 +0200
Message-ID	<qhkZs-76Q-11@gated-at.bofh.it>
In reply to	#7421

Hi Barry (2015.10.02_16:24:28_+0200)
> 8-Oct - Assuming no objections or showstoppers, turn off write access to all
> of DPMT svn.

Done. And kicking off the migration now...

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

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

#7574

From	Brian May <brian@microcomaustralia.com.au>
Date	2015-10-09 02:00 +0200
Message-ID	<qhtgl-1Ro-5@gated-at.bofh.it>
In reply to	#7561

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

On Fri, 9 Oct 2015 at 02:06 Stefano Rivera <stefanor@debian.org> wrote:

> Done. And kicking off the migration now...
>

Great!

Will the migration do packages like python-django?

Just thinking that python-django in subversion is old, and the version in
git doesn't (yet) use git-dpm; you don't want the migration changing the
existing python-django git by mistake.

I am not sure what the plan is for the location for the final migration run.

I suspect there are other packages that will be in a similar situation.

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

#7578

From	Stefano Rivera <stefanor@debian.org>
Date	2015-10-09 10:00 +0200
Message-ID	<qhAKS-4hU-15@gated-at.bofh.it>
In reply to	#7574

Hi Brian (2015.10.09_01:52:20_+0200)
> Will the migration do packages like python-django?

It migrated everything that's in SVN. What happens to the result is up
to us. We can replace migrated results with existing git packages.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

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

#7587

From	Brian May <brian@microcomaustralia.com.au>
Date	2015-10-10 00:40 +0200
Message-ID	<qhOuu-7eA-27@gated-at.bofh.it>
In reply to	#7578

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

On Fri, 9 Oct 2015 at 18:58 Stefano Rivera <stefanor@debian.org> wrote:

> It migrated everything that's in SVN. What happens to the result is up
> to us. We can replace migrated results with existing git packages.
>

Ok, I probably should create another thread to discuss this for Django then.

Also, contrary to the rules we just agreed on, this sounds like one rare
time when all uploaders should be contacted before moving any repositories
around.

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

#7588

From	Barry Warsaw <barry@debian.org>
Date	2015-10-10 01:00 +0200
Message-ID	<qhONQ-7Be-1@gated-at.bofh.it>
In reply to	#7587

On Oct 09, 2015, at 10:30 PM, Brian May wrote:

>Ok, I probably should create another thread to discuss this for Django then.
>
>Also, contrary to the rules we just agreed on, this sounds like one rare
>time when all uploaders should be contacted before moving any repositories
>around.

Probably so.  I have a checkout of python-django here and it seems to already
be in git.  I haven't looked at the converted svn->git repo yet, but I'm
wondering if what was converted was just old and out of date?  I'm pretty sure
it was in git to manage the 1.8 transition.  The debian/sid branch has 1.7.9-1
at its top while debian/experimental has UNRELEASED 1.8.3-2.

That's probably necessary given the complexity of python-django, but since it
deviates from GitPackaging, there should be a debian/README.source to explain
to other team members how the repo is supposed to be used.

Cheers,
-Barry

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

#7605

From	Brian May <brian@microcomaustralia.com.au>
Date	2015-10-11 02:30 +0200
Message-ID	<qicGt-db-7@gated-at.bofh.it>
In reply to	#7588

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

On Sat, 10 Oct 2015 at 09:55 Barry Warsaw <barry@debian.org> wrote:

> Probably so.  I have a checkout of python-django here and it seems to
> already
> be in git.  I haven't looked at the converted svn->git repo yet, but I'm
> wondering if what was converted was just old and out of date?  I'm pretty
> sure
> it was in git to manage the 1.8 transition.  The debian/sid branch has
> 1.7.9-1
> at its top while debian/experimental has UNRELEASED 1.8.3-2.
>
> That's probably necessary given the complexity of python-django, but since
> it
> deviates from GitPackaging, there should be a debian/README.source to
> explain
> to other team members how the repo is supposed to be used.
>

What branches do I need to put the debian/README.source file in? There are
six debian/* branches, don't think it is a good idea to try and maintain a
consistent debian/README.source in all branches.

Maybe debian/experimental would be sufficient? Or perhaps
debian/experimental + debian/sid?

In fact, putting in a branch seems wrong, it isn't specific to any one
branch, not sure where a better place would be though.

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

#7623

From	Raphael Hertzog <hertzog@debian.org>
Date	2015-10-12 09:10 +0200
Message-ID	<qiFp7-8uI-1@gated-at.bofh.it>
In reply to	#7605

On Sun, 11 Oct 2015, Brian May wrote:
> What branches do I need to put the debian/README.source file in? There are
> six debian/* branches, don't think it is a good idea to try and maintain a
> consistent debian/README.source in all branches.
> 
> Maybe debian/experimental would be sufficient? Or perhaps
> debian/experimental + debian/sid?
> 
> In fact, putting in a branch seems wrong, it isn't specific to any one
> branch, not sure where a better place would be though.

IMO, you should just indicate that the repository follows DEP-14 and not be
specific about the branch names. That way you don't have any problem.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

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

#7638

From	Barry Warsaw <barry@debian.org>
Date	2015-10-12 21:40 +0200
Message-ID	<qiR6W-cl-13@gated-at.bofh.it>
In reply to	#7605

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

On Oct 11, 2015, at 12:28 AM, Brian May wrote:

>What branches do I need to put the debian/README.source file in? There are
>six debian/* branches, don't think it is a good idea to try and maintain a
>consistent debian/README.source in all branches.
>
>Maybe debian/experimental would be sufficient? Or perhaps
>debian/experimental + debian/sid?
>
>In fact, putting in a branch seems wrong, it isn't specific to any one
>branch, not sure where a better place would be though.

I agree that it's a bit weird, but there really isn't any better place,
AFAICT.  debian/experimental and debian/sid are the most likely places people
will look, so probably at least there.

Cheers,
-Barry

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

#7579

From	Stefano Rivera <stefanor@debian.org>
Date	2015-10-09 10:10 +0200
Message-ID	<qhAUy-4Iv-13@gated-at.bofh.it>
In reply to	#7561

Hi debian-python (2015.10.08_17:06:29_+0200)
> Done. And kicking off the migration now...

And it's done.

Things that need to be looked at:
http://whiteboard.debian.net/dpmt-git-migration.wb

Please mark them off if you've looked at them.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

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

#7581

From	Barry Warsaw <barry@debian.org>
Date	2015-10-09 16:50 +0200
Message-ID	<qhH9E-54I-23@gated-at.bofh.it>
In reply to	#7579

On Oct 09, 2015, at 10:01 AM, Stefano Rivera wrote:

>And it's done.

\o/

Thank you for all your amazing work on this Stefano!

>Things that need to be looked at:
>http://whiteboard.debian.net/dpmt-git-migration.wb
>
>Please mark them off if you've looked at them.

I've done an updating pass through the wiki page:

https://wiki.debian.org/Python/GitPackaging

and marked it "official".  Please pay special attention to the section on
post-migration clean ups that folks can help with:

https://wiki.debian.org/Python/GitPackaging#Post-migration_clean_up

I'd also like to send an email to debian-devel@ inviting people who may have
abandoned the DPMT because of our use of subversion, to come back to the team.

Cheers,
-Barry

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

#7582

From	Arthur de Jong <adejong@debian.org>
Date	2015-10-09 18:50 +0200
Message-ID	<qhJ1L-7NG-9@gated-at.bofh.it>
In reply to	#7581

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

On Fri, 2015-10-09 at 10:47 -0400, Barry Warsaw wrote:
> I'd also like to send an email to debian-devel@ inviting people who
> may have abandoned the DPMT because of our use of subversion, to come
> back to the team.

Perhaps an email to d-d-announce would be in order. I for one don't
regularly read debian-python (pyton-*-team even less for that matter).

A short email of what changed with a few pointers to how we are working
now. I think the wiki page may also be very useful for other teams.

-- 
-- arthur - adejong@debian.org - http://people.debian.org/~adejong --

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

#7583

From	Barry Warsaw <barry@debian.org>
Date	2015-10-09 19:40 +0200
Message-ID	<qhJO9-wh-7@gated-at.bofh.it>
In reply to	#7582

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

On Oct 09, 2015, at 06:46 PM, Arthur de Jong wrote:

>Perhaps an email to d-d-announce would be in order.

Good idea, thanks.

-Barry

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

#7584

From	Arthur de Jong <adejong@debian.org>
Date	2015-10-09 21:30 +0200
Message-ID	<qhLwB-31r-11@gated-at.bofh.it>
In reply to	#7583

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

On Fri, 2015-10-09 at 13:34 -0400, Barry Warsaw wrote:
> On Oct 09, 2015, at 06:46 PM, Arthur de Jong wrote:
> > Perhaps an email to d-d-announce would be in order.
> 
> Good idea, thanks.

Thanks everyone for the hard work. Time for me to learn a new tool ;)

-- 
-- arthur - adejong@debian.org - http://people.debian.org/~adejong --

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

#7586

From	Brian May <brian@microcomaustralia.com.au>
Date	2015-10-10 00:30 +0200
Message-ID	<qhOkP-73l-43@gated-at.bofh.it>
In reply to	#7579

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

On Fri, 9 Oct 2015 at 19:01 Stefano Rivera <stefanor@debian.org> wrote:

> Things that need to be looked at:
> http://whiteboard.debian.net/dpmt-git-migration.wb
>

Not sure what the headings mean. "Git packages moved out the way" seems
obvious - and probably exactly what I mentioned before with Django, but
what about "Merge SVN"? Is this the same thing or different? What is
"Orphaned tags"?

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

#7611

From	Stefano Rivera <stefanor@debian.org>
Date	2015-10-11 10:30 +0200
Message-ID	<qikaZ-2Me-9@gated-at.bofh.it>
In reply to	#7586

Hi Brian (2015.10.10_00:22:09_+0200)
> what about "Merge SVN"? Is this the same thing or different?

The svn history goes beyond the most recent upload to the archive, but
couldn't be automatically merged into the upload history.

> What is "Orphaned tags"?

There were tags that aren't linked into the rest of the history.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

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

#7629 — Re: Git migration schedule pushback permissions/DEP-3 workflow

From	Daniel Stender <debian@danielstender.com>
Date	2015-10-12 20:20 +0200
Subject	Re: Git migration schedule pushback permissions/DEP-3 workflow
Message-ID	<qiPRw-6RC-13@gated-at.bofh.it>
In reply to	#7561

On 08.10.2015 17:06, Stefano Rivera wrote:
> Hi Barry (2015.10.02_16:24:28_+0200)
>> 8-Oct - Assuming no objections or showstoppers, turn off write access to all
>> of DPMT svn.
> 
> Done. And kicking off the migration now...
> 
> SR

Thanks for the work, things likes automatically updated Vcs fields are much appreciated.

Git-dpm patching appears to be great with features like auto-dropping of patches
applied by upstream, that's much better than Quilt. Exploring ...

I've got a push back error here:
<cut>
$ git push
Counting objects: 22, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (21/21), done.
Writing objects: 100% (22/22), 2.72 KiB | 0 bytes/s, done.
Total 22 (delta 12), reused 0 (delta 0)
remote: error: insufficient permission for adding an object to repository database ./objects
remote: fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
To ssh://danstender-guest@git.debian.org/git/python-modules/packages/citeproc-py.git
 ! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'ssh://danstender-guest@git.debian.org/git/python-modules/packages/citeproc-py.git'
</cut>

Question:
When new patch has been installed after <git-dpm update patches> it misses a DEP-3 compliant header.
I've now edited debian/patches/0001-foo.patch for that and made another commit on master. Is there a
better/another workflow for this?

Thanks
DS

-- 
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/

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

#7630 — Re: Git migration schedule pushback permissions/DEP-3 workflow

From	Daniele Tricoli <eriol@mornie.org>
Date	2015-10-12 20:30 +0200
Subject	Re: Git migration schedule pushback permissions/DEP-3 workflow
Message-ID	<qiQ1b-74n-1@gated-at.bofh.it>
In reply to	#7629

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

On Monday, October 12, 2015 08:13:41 PM Daniel Stender wrote:
> I've got a push back error here:
> <cut>
> $ git push
> Counting objects: 22, done.
> Delta compression using up to 4 threads.
> Compressing objects: 100% (21/21), done.
> Writing objects: 100% (22/22), 2.72 KiB | 0 bytes/s, done.
> Total 22 (delta 12), reused 0 (delta 0)
> remote: error: insufficient permission for adding an object to repository
> database ./objects remote: fatal: failed to write object
> error: unpack failed: unpack-objects abnormal exit
> To
> ssh://danstender-guest@git.debian.org/git/python-modules/packages/citeproc-
> py.git ! [remote rejected] master -> master (unpacker error)
> error: failed to push some refs to
> 'ssh://danstender-guest@git.debian.org/git/python-modules/packages/citeproc
> -py.git' </cut>

I have experienced same problems, but only related to pushing tags (I mean, 
pushing works except for tags).
For example pywavelets:
❯ git push --tags            
Counting objects: 1, done.
Writing objects: 100% (1/1), 176 bytes | 0 bytes/s, done.
Total 1 (delta 0), reused 0 (delta 0)
remote: error: insufficient permission for adding an object to repository 
database ./objects
remote: fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
To git+ssh://git.debian.org/git/python-modules/packages/pywavelets
 ! [remote rejected] upstream/0.3.0 -> upstream/0.3.0 (unpacker error)
error: failed to push some refs to 'git+ssh://git.debian.org/git/python-
modules/packages/pywavelets'

The same is happening with python-urllib3.

Cheers!

-- 
 Daniele Tricoli 'eriol'
 https://mornie.org

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

#7585

From	Brian May <brian@microcomaustralia.com.au>
Date	2015-10-10 00:20 +0200
Message-ID	<qhOb8-6RX-7@gated-at.bofh.it>
In reply to	#7421

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

On Sat, 3 Oct 2015 at 00:24 Barry Warsaw <barry@debian.org> wrote:

> 5-Oct - Do one last test run with an updated svn dump.  Put the results in
> a
> public place for folks to play with and comment on.
>
> 8-Oct - Assuming no objections or showstoppers, turn off write access to
> all
> of DPMT svn.
>
> 9-Oct - One more svn dump and conversion run.  Move the git repos into
> their
> final resting place.
>
> Announce, celebrate, ???, profit!
>

We haven't finished yet. We still need to do the celebrate step :-)

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

#7602

From	IOhannes m zmölnig <zmoelnig@umlaeute.mur.at>
Date	2015-10-10 21:40 +0200
Message-ID	<qi89Q-24k-15@gated-at.bofh.it>
In reply to	#7585

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

On 10/10/2015 12:16 AM, Brian May wrote:
> On Sat, 3 Oct 2015 at 00:24 Barry Warsaw <barry@debian.org> wrote:
> 
>> 5-Oct - Do one last test run with an updated svn dump.  Put the results in
>> a
>> public place for folks to play with and comment on.
>>
>> 8-Oct - Assuming no objections or showstoppers, turn off write access to
>> all
>> of DPMT svn.
>>
>> 9-Oct - One more svn dump and conversion run.  Move the git repos into
>> their
>> final resting place.
>>
>> Announce, celebrate, ???, profit!
>>
> 
> We haven't finished yet. We still need to do the celebrate step :-)
> 

congratulations to all the people that have done this fantastic piece of
work.
hurray!

fgmards
IOhannes

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

Page 3 of 4 — ← Prev page 1 2 [3] 4 Next page →

csiph-web

Git migration schedule

Contents

#7486

#7561

#7574

#7578

#7587

#7588

#7605

#7623

#7638

#7579

#7581

#7582

#7583

#7584

#7586

#7611

#7629 — Re: Git migration schedule pushback permissions/DEP-3 workflow

#7630 — Re: Git migration schedule pushback permissions/DEP-3 workflow

#7585

#7602