[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Another bug in latex-cjk-chinese-arphic



Op 05-08-08 10:10, schreef Norbert Preining:
> On Di, 05 Aug 2008, "Danai SAE-HAN (韓達耐)" wrote:
>>> - I have checked in the current code for the three packages, BUT:
>>>   . for cjk and latex-cjk-japanese-wadalab ONLY the changes to the
>>>     original source package. So only the trunk/debian directory is
>>>     there. You have to put the .orig.tar.gz into
>>> 	PACKAGE/tarballs/
>>>     (i.e., cjk/tarballs/cjk_4.8.0+git20080711.orig.tar.gz) but do
>>>     NOT (!) commit that, leave it there on your computer.
>> Hmmm, so I create
>> cjk-4.8.0+git20080711/cjk/tarballs/cjk_4.8.0+git20080711.orig.tar.gz locally?
> 
> Not "creating", copying it from where you have it. Remember it should be
> the very same one already uploaded to Debian, no md5sum changes.

Indeed, sorry, I meant copying.

>> The upstream CJK package uses GIT to handle updates; could I trigger SVN to
>> pull this GIT source as well, and automatically change the .orig.tar.gz name?
> 
> No idea, sorry. I guess best is you add to the debian/rules file
> something like
> 	make -f debian/rules orig-source
> which does that. But I have no idea. Anyway, normally you dont have to
> do that so often, so that I am not that concerned of.

It might be nice to have something like git-clone to create the tarball, no?
 I don't like GIT that much; it doesn't have an option to fetch a specific
revision based on a date (or at least an incremental revision number), but I
could work around this.

The Debian Policy (section 4.9) describes the use of the get-orig-source
target.  However, I've also read that there is some speculation about its
formulation.  Having fixed .tar.gz files with watch/uscan isn't a problem,
but it is slightly more complicated when you have a VCS.

Option A.
I could use a specific revision number, that is parsed from debian/changelog.
 debian/rules then has to build a pristine tarball.

This looks like the easiest way, but not entirely in accord with the Policy.
 Although you could argue that it fetches the original source tarball which
has the same md5sum as the package maintainer has uploaded to Debian.

I, and others as well, find this section of the Policy lacks some clarity.

Option B.
debian/rules fetches the latest GIT repository, scans the latest commit for
the date, updates the versioning in debian/changelog, and repackages the
orig.tar.gz file.

This is quite difficult to implement, and I fail to see the added value of it.


Do you agree that I should go for option A?


>>> If you want to check out only your stuff do
>>>   for i in  cjk latex-cjk-japanese-wadalab latex-cjk-chinese-arphic ; do
>>>     svn co svn+ssh://danai-guest@svn.debian.org/svn/debian-tex/$i .
>>>   done
>> Thanks for the scriplet; I've put it in my ~/bin.
> 
> No, that is only for initial co, after that you want to use
> 	svn update 
> in the three directories!

Oh yeah, indeed.


Best regards


-- 
Danai SAE-HAN (韓達耐)

題目:《牧童詩》
作者:黃庭堅(1045-1105)

騎牛遠遠過前村,短笛橫吹隔隴聞。
多少長安名利客,機關用盡不如君。

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: