Re: [Tails-dev] Tails Clock 0.5

Delete this message

Reply to this message
Autor: Kevin C. Krinke
Data:  
A: tails-dev
Assumpte: Re: [Tails-dev] Tails Clock 0.5


On 2013-11-12 12:39 PM, intrigeri wrote:
>
> The URL in Vcs-Git should be usable by everyone.
>
> https://git.tails.boum.org has no valid certificate, better use
> https://git-tails.immerda.ch instead.


Just committed (locally):

Vcs-Git: git://git.tails.boum.org/kevin/clock
Vcs-Browser: https://git-tails.immerda.ch/kevin/clock


>> * Remove NEWS (needed to build though?)
>
> What's the actual issue with NEWS? I see a hackish "solution" in Git,
> but I don't know what problem it is supposed to workaround.


I initially gave up trying to debug this problem. Finally dug up the
correct configure.ac magik to make that end of things work however
git-buildpackage still dies on me during dh_installdocs.

My challenge now I suppose is to figure out what dh_installdocs is
requiring NEWS.

<relevant-parts-of-stderr>

make[1]: Leaving directory `/quo/git/hub/kckrinke/tailsclock/tailsclock-0.5'
dh_install
dh_installdocs
cp: cannot stat `NEWS': No such file or directory
dh_installdocs: cp -a NEWS debian/tailsclock/usr/share/doc/tailsclock
returned exit code 1
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
debuild: fatal error at line 1357:
dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed
gbp:error: Couldn't run 'debuild -i -I': debuild -i -I returned 29

</relevant-parts-of-stderr>

Any pointers?

> "debhelper (>= 9.0.0)" surely works, but it seems weird, given the
> current debhelper versionning scheme. "debhelper (>= 9)" should be
> just enough to express what you mean.


Done.

> Please bump Standards-Version to the latest one (`apt-get install
> debian-policy/unstable', see the checklist shipped in there).


/usr/share/doc/debian-policy/policy.html/upgrading-checklist.html

Not sure if that was the checklist you're referring to. Went through it
and didn't see anything that needed fixing. Was there anything in
particular?

> It would be nice if debian/control ended with a newline.


Done.

> Is the canonical upstream source of the package a signed Git tag (I
> would prefer this) or the .orig tarball?


0.6 will be released with a signed Git tag.


--
Kevin C. Krinke <kevin@???>
GnuPG - 851662D2 - 0x18C67F61851662D2
http://kevin.c.krinke.ca/851662D2.asc