instance the
changelog now has an entry 4.0.4-3~1.gbpaa26a9 and did not take the
tag "4.1.0" into account.
Did any one tried to move from using the upstream tarball to using an
upstream tag instead?
Thanks in advance for any help or comment about what I did so far
(which might be complet
Dear Andreas,
On 13/07/18 22:00, Andreas Tille wrote:
Hi Emmanuel,
On Fri, Jul 13, 2018 at 06:33:13PM +0200, Emmanuel Promayon wrote:
In upstream we are also using a local gitlab instance to host our project
(hosted on gricad-gitlab.univ-grenoble-alpes.fr).
As far as I know gitlab provides a
d
> git add debian
> git commit -m "add debian packaging dir"
> git push --set-upstream origin debian/sid
> gbp dch --debian-branch=debian/sid --snapshot --auto debian/
>
> But I am not sure it is the right thing to do as for instance the
> changelog now has an entr
an/sid --snapshot --auto debian/
>
> But I am not sure it is the right thing to do as for instance the changelog
> now has an entry 4.0.4-3~1.gbpaa26a9 and did not take the tag "4.1.0" into
> account.
>
> Did any one tried to move from using the upstream tarball to using a
for instance the
changelog now has an entry 4.0.4-3~1.gbpaa26a9 and did not take the tag
"4.1.0" into account.
Did any one tried to move from using the upstream tarball to using an
upstream tag instead?
Thanks in advance for any help or comment about what I did so far (which
mig
5 matches
Mail list logo