On Mon, Apr 04, 2016 at 08:09:31PM -0300, Tiago Ilieve wrote:
> Hi Mattia,
>
> On 4 April 2016 at 18:25, Mattia Rizzolo <mattia@debian.org> wrote:
> > I usually prefer using git to do my stuff, though here a simple clone is
> > not enough:
> >
> > mattia@chase ~/devel/RFS/python-path-and-address % git clone https://anonscm.debian.org/git/collab-maint/python-path-and-address.git
> > Cloning into 'python-path-and-address'...
> > remote: Counting objects: 119, done.
> > remote: Compressing objects: 100% (110/110), done.
> > remote: Total 119 (delta 44), reused 0 (delta 0)
> > Receiving objects: 100% (119/119), 27.69 KiB | 0 bytes/s, done.
> > Resolving deltas: 100% (44/44), done.
> > Checking connectivity... done.
> > warning: remote HEAD refers to nonexistent ref, unable to checkout.
> >
> > you seems to use debian/unstable as main packaging branch, so please set
> > HEAD in a way a simple 'git clone' just works.
>
> This is related to some issues with collab-maint I've reported last
> weekend[1].
yep, saw the mail that day, but didn't pay much attention back then.
> In the other repositories that I've created in there, "git
> symbolic-ref HEAD refs/heads/debian/unstable" can be used update the
> default branch. The problem is that, as I'm not the owner (because I
> didn't created the the repository, adopted ITP) nor member of the
> group ("Debian" instead of "scm_collab-maint") of the folder
> "/git/collab-maint/python-path-and-address.git", it raises the
> following error:
>
> error: Unable to open HEAD.lock for writing
This is basically a security feature, I think, not a bug.
Though you should be able to fix it more manually by directly editing
the HEAD file.
but this time I just run the command for you :)
This turned the HEAD file to be group Debian again and I can't have it
back to scm_collab-maint as I'm not in the collab-maint anymore.
Yeah, permissions on collab-maint (and alioth in general) are just a
mess....
If you have troubles with file permissions on collab-maint feel free to
mail me if you don't have any nearby DD..
> If you know someone with sudo privileges on git.debian.org
> (moszumanska) to fix the folder permissions, please let me know so I
> can forward this issue to them. Maybe I should ask the DSA team
> directly?
DSA has nothing to do with alioth (sadly?), there is only one active
person with root on moszumanska (which is the guy that replied to you
last time, iirc), but he won't chgrp the directory (as afaik he made
them gid:Debian exactly because he wants to avoid external messing with
repositories (if the root directory was writable by you you would be
able to do anything with the config and the hooks, and that's a security
trouble on collab-maint where everybody has access).
> > Also, your git repository seems to lack a pristine-tar branch, which is
> > basically needed to get the same tarball that is in the archive.
>
> There's the "upstream" branch in there, which serves this purpose. It
> is defined as "upstream-branch" in "debian/gbp.conf". Running "gbp
> buildpackage" will recreate
> "python-path-and-address_1.1.0.orig.tar.xz" from it:
>
> gbp:info: python-path-and-address_1.1.0.orig.tar.xz does not exist,
> creating from 'upstream/1.1.0'
>
> It uses the tag to do this, so there's even no need to checkout
> "origin/upstream" in a local branch.
Yep, even if I'm always wary of this.
I'm a guy who prefers using the tarballs as provided upstream.
I wrote this item before noticing that you used .xz, so a different
tarball than upstream.
Fine by me, I see how this is enough for this case.
> > * debian/patches:
> > + empty, please remove the directory
>
> Done[2].
>
> > * debian/changelog:
> > + be more precise: that's the Expat license
>
> I do understand that some may say that the Expat License is the right
> name for MIT license, but the text in there is identical to the ones
> published by OSI[3] and GitHub's Choose a License[4] of the MIT
> License. In order to avoid any further confusion, I'd like to ask you
> to leave this as is. The name "MIT" is much more popular for the text.
ok, yes I know it's more popular. To me it seems "Expat" is known only
within Debian, heh :)
>
> > I'll look also at the rdep of this once through with this.
>
> Thank you. Feel free to take the ownership of the other RFS too.
going to set myself as owner, will look at it somewhen tomorrow though.
> > Note: fixing on git is enough, I'm very much fine doing everything
> > with git.
>
> I prefer to do that too. I've uploaded the package to mentors because
> it would be easier for anyone to take a look (using the web interface)
> at its state without even having to download it.
>
> I'll ping you every time I make a change.
Well, I uploaded it :D
I also tagged the repository.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature