Built, signed & uploaded.
The package will now stay some days in the NEW queue, depending on how
the ftmasters are busy, if nothing goes wrong.
Cheers,
Hugo
--
Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E
signature.asc
> Well, I'm not really sure about how the HEAD problem happened, i thought it
> was how we were supposed to work (although i would find it better to have
> the HEAD properly set). I created the git following our team's
> instructions[1] and it looks like we have at least one more package with
>
Hi Hugo,
git
> ---
>
> * HEAD is set on a non-existent ref. This is weird, I don't
>know how you did that. The repository appears to be empty when you
>clone it for the first time... :-)
>
> * You can already push the 'upstream' tags. In fact, you should delete
>the 'debian' tags if
Hi Samuel,
> I've just created the git repo. and pushed hashid, i didn't push any tags
> because i believe we will only tag hashid when we update the manpage, if i
> did something wrong please feel free to point out.
Here are some things that can still be improved:
git
---
* HEAD is set on a
Hi Hugo,
I've just created the git repo. and pushed hashid, i didn't push any tags
because i believe we will only tag hashid when we update the manpage, if i
did something wrong please feel free to point out.
Thanks.
Samuel Henrique O. P. [samueloph]
2016-08-20 17:19 GMT-03:00 Hugo Lefeuvre
Hi Samuel,
> I believe the manpage update should be made in form of a PR on the
> project's github page, and because it's not practical to wait for another
> release, we can patch the new manpage with quilt until we get a new release.
I agree. Let's patch the manpage in our Debian release and
6 matches
Mail list logo
