> $ git switch master
> $ git tag v0.21
> $ git switch debian
> $ git merge master
> $ gbp dch --release
>
> ...but gbp chooses a release of 0.20-2 as opposed to 0.21-1.
>
> What am I missing?
>
> Thanks for helping me to get back on the gbp horse!
>
> -m
>
&g
Hi,
On Wed, Mar 13, 2024 at 6:35 AM دانیال بهزادی
wrote:
>
> Can you try importing new upstream version with gbp too:
>
> gbp import-orig ../package.orig.tar.gz
>
> Or if you use watch file:
>
>gbp import-orig --uscan
Thanks for the reply.
I'm upstream and the upstream code is in t
Can you try importing new upstream version with gbp too:
gbp import-orig ../package.orig.tar.gz
Or if you use watch file:
gbp import-orig --uscan
for release.
Debian branch: debian
Upstream branch: master
$ git switch master
$ git tag v0.21
$ git switch debian
$ git merge master
$ gbp dch --release
...but gbp chooses a release of 0.20-2 as opposed to 0.21-1.
What am I missing?
Thanks for helping me to get back on the gbp horse!
-m
PS. I
ong.)
> …
>> Note how the last entry is unfinished, because of ongoing
>> development. When I now call "dch" to add another entry, the editor
>> looks like this:
> …
>> dch of course complains loudly:
> Bug: https://bugs.debian.org/784397
I found that bug a
s unfinished, because of ongoing development.
> When I now call "dch" to add another entry, the editor looks like this:
…
> dch of course complains loudly:
Bug: https://bugs.debian.org/784397
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA
--8<
Note how the last entry is unfinished, because of ongoing development.
When I now call "dch" to add another entry, the editor looks like this:
---8<
foobar (1.0-3) UNRELEASED; urgency=medium
* Third
*
a 'debian'
directory with required files
What I'm struggling with:
- creating a proper changelog
Obviously I can create it manually but the automagic creation sounded
like a much better plan. But the problem I have is that I can't get it
to work.
When I didn't have a ch
a 'debian'
directory with required files
What I'm struggling with:
- creating a proper changelog
Obviously I can create it manually but the automagic creation sounded
like a much better plan. But the problem I have is that I can't get it
to work.
When I didn't have a ch
On 2014-01-05 10:06, Thomas Goirand wrote:
> On 01/05/2014 04:55 PM, Andreas Tille wrote:
>> Hi,
>>
>> since some days I noticed that a `dch -i` creates an entry with
>> "urgency=medium" instead of "urgency=low". Anybody with the same
>&
On 01/05/2014 04:55 PM, Andreas Tille wrote:
> Hi,
>
> since some days I noticed that a `dch -i` creates an entry with
> "urgency=medium" instead of "urgency=low". Anybody with the same
> observation and what might be the reason for this?
>
> Kind rega
On Sun, Jan 5, 2014 at 12:55 AM, Andreas Tille wrote:
> Hi,
>
> since some days I noticed that a `dch -i` creates an entry with
> "urgency=medium" instead of "urgency=low". Anybody with the same
> observation and what might be the reason for this?
#730343
Hi,
since some days I noticed that a `dch -i` creates an entry with
"urgency=medium" instead of "urgency=low". Anybody with the same
observation and what might be the reason for this?
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to
Thanks a lot everyone =D
--
With best regards
Dmitrijs Ledkovs (for short Dima),
Ледков Дмитрий Юрьевич
On Tue, Apr 21, 2009 at 09:22:49PM +0200, Stéphane Glondu wrote:
> Neil Williams a écrit :
> >> Is it still allowed as per 3.8.1 policy to use multi maintainer style
> >> changelogs?
> >
> > Yes.
>
> And what was the prevous style of changelog allowed, by the way?
Originally, the debian changelo
Dmitrijs Ledkovs writes:
> Is it still allowed as per 3.8.1 policy to use multi maintainer style
> changelogs?
> (Asking because of the explicit statement of one type of changlelog
> and new upgrade to must)
That type of changelog allows anything at all following the two space
indent for entries
Neil Williams a écrit :
>> Is it still allowed as per 3.8.1 policy to use multi maintainer style
>> changelogs?
>
> Yes.
And what was the prevous style of changelog allowed, by the way?
--
Stéphane
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscr
On Tue, 21 Apr 2009 20:06:23 +0100
Dmitrijs Ledkovs wrote:
> Dear all
>
> Is it still allowed as per 3.8.1 policy to use multi maintainer style
> changelogs?
Yes.
> (Asking because of the explicit statement of one type of changlelog
> and new upgrade to must)
The important lines are:
> fooba
Dear all
Is it still allowed as per 3.8.1 policy to use multi maintainer style
changelogs?
(Asking because of the explicit statement of one type of changlelog
and new upgrade to must)
Eg.
foobar (1.5.11-1) unstable; urgency=low
[ Joe Plow Mber ]
* New upstream release
[ Vasja Pupkin ]
On Thu, Mar 28, 2002 at 05:06:13PM +0100, pp wrote:
> Is there any way to use dch , to increase only version number?
If you specify a changelog entry on the command line dch won't drop you
into an editor.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever.
On Thu, Mar 28, 2002 at 05:06:13PM +0100, pp wrote:
> Is there any way to use dch , to increase only version number?
If you specify a changelog entry on the command line dch won't drop you
into an editor.
--
"You grabbed my hand and we fell into it, like a daydream
Hello!
Is there any way to use dch , to increase only version number?
Or any other tool?
I need it for daily builded debs , and I do not need exactly change
anything else in changelog.
Piotras
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
Hello!
Is there any way to use dch , to increase only version number?
Or any other tool?
I need it for daily builded debs , and I do not need exactly change
anything else in changelog.
Piotras
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
23 matches
Mail list logo
