Bug#819773: RFS: python-path-and-address/1.0.0-1 [ITP]
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]. 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
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?
> 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.
> * 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.
> 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.
> 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.
Regards,
Tiago.
[1]: https://lists.debian.org/debian-mentors/2016/04/msg00008.html
[2]: https://anonscm.debian.org/git/collab-maint/python-path-and-address.git/commit/?h=debian/unstable&id=f75e55228e6a94ee9c87ef7cae91e07c5b4997c5
[3]: https://opensource.org/licenses/MIT
[4]: http://choosealicense.com/licenses/mit/
--
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil
Reply to: