Hi,
[Cc'ing the ITP FTR]
I have almost finished preparing emacs-snapshot and temporarily pushed
it there, so please have a look when you have some time as I may have
messed things around ;-):
https://salsa.debian.org/arnau/deb-emacs
I have a few questions though:
* bin_priority (for update-alternatives): I think it would make sense
to have an higher one for emacs-snapshot, what about a number big
enough so it doesn't clash with future stable release (such as 999)?
* Currently emacs-snapshot version is:
2:YYYYMMDD-<LATEST_AVAILABLE_TAG>-g<MASTER_COMMIT_ID>-1
Considering that this is not really the LATEST_AVAILABLE_TAG but
MASTER_COMMIT_ID at the time of packaging and in order to shorten
the version which is currently rather long, MASTER_COMMIT_ID only
should be enough, isn't it?
This would mean having something like this after bumping the epoch
and where the first '-1' is only in case of we upload two different
Git snapshots on the same day:
3:YYYYMMDD-1+git<MASTER_COMMIT_ID>-1
What do you think?
* I put myself as Maintainer, and Rob and Dima as Uploaders, but if
either Rob or Dima wish to be in the Maintainer field, please let me
know as either is fine to me.
* I was thinking about having deb-emacs repository for both emacs25
and emacs-snapshot in collab-maint Git (as emacs.git) instead of a
user repository. What do you think?
* Rob: I have made several changes to emacs25 branch, feel free to
merge them if they look fine to you:
https://salsa.debian.org/arnau/deb-emacs/commits/deb/emacs25/d/sid/master
And some packaging questions I will add to debian/README.source:
* Dima is using gbp-pq and Rob git-dpm. In order to keep it as close
as possible to emacs25 packaging, I have been using git-dpm. I
don't really well both of them as this is the first time I use them
so I have absolutely no opinion on this. Dima: is that ok?
Rob: I ran the following command after importing patches from
emacs25 and merging them with the ones from emacs-snapshot from
Dima:
$ git-dpm init --record-patch-name ../emacs-snapshot_20180414-1+git836dce6.orig.tar.xz deb/emacs-snapshot/d/sid/upstream
However, I'm not so familiar with git-dpm, so would you mind
explaining how you use it for emacs25?
* Rob: I followed your naming scheme for branches and tags, thus:
+ Branches:
deb/emacs-snapshot/d/sid/master
deb/emacs-snapshot/d/sid/upstream
+ Tags:
deb/emacs-snapshot/v/upstream/20180414-1+git836dce6
* Rob: Could you please explain how you remove non-DFSG documentation
(such as emacs.texi) from the Git repository?
* Here is what I have been using to create a new upstream release from
deb/emacs-snapshot/d/sid/master branch:
$ git tag -s -m "Upstream tagged for Debian version 20180414-1+git836dce6." deb/emacs-snapshot/v/upstream/20180414-1+git836dce6 deb/emacs-snapshot/d/sid/upstream
$ gbp buildpackage --git-builder=/bin/true --git-upstream-tree=deb/emacs-snapshot/v/upstream/20180414-1+git836dce6
=> Thanks to debian/gbp.conf I added, this will automatically
generate the tarball with pristine-tar. If that's ok, maybe
debian/gbp.conf should be added to emacs25 branch too?
Cheers,
--
Arnaud
Attachment:
signature.asc
Description: PGP signature