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

Bug#237698: marked as done (dpkg-dev: dpkg-buildpackage -v seems not working)



Your message dated Tue, 01 Jun 2004 15:57:41 -0300
with message-id <1086116260.17455.3.camel@syndicate>
and subject line Bug#237698: dpkg-dev: dpkg-buildpackage -v seems not working
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 12 Mar 2004 21:48:51 +0000
>From ultrotter@quaqua.net Fri Mar 12 13:48:51 2004
Return-path: <ultrotter@quaqua.net>
Received: from adsl-110-27.37-151.net24.it (deathstar) [151.37.27.110] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1B1uWQ-0007A5-00; Fri, 12 Mar 2004 13:48:51 -0800
Received: from executor.studio.tixteam.net (executor [192.168.5.3])
	by deathstar (Postfix) with ESMTP
	id 9308A7E4C4; Fri, 12 Mar 2004 22:48:40 +0100 (CET)
Received: by executor.studio.tixteam.net (Postfix, from userid 1000)
	id 5E6791FD2E; Fri, 12 Mar 2004 22:48:20 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Guido Trotter <ultrotter@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: dpkg-dev: dpkg-buildpackage -v seems not working
X-Mailer: reportbug 2.50
Date: Fri, 12 Mar 2004 22:48:20 +0100
Message-Id: <20040312214820.5E6791FD2E@executor.studio.tixteam.net>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level: 

Package: dpkg-dev
Version: 1.10.20
Severity: normal

Hi,

I've tried to build a package with

dpkg-buildpackage -v0.7.0+1.0beta1-1 -rfakeroot

in order to have, included in the changes file, the changelog entry from
0.7.0+1.0beta1-2 and after.

Instead the whole changelog was included, from its beginning... :/

Thanks,

Guido

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.3
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Versions of packages dpkg-dev depends on:
ii  binutils                   2.14.90.0.7-5 The GNU assembler, linker and bina
ii  cpio                       2.5-1.1       GNU cpio -- a program to manage ar
ii  make                       3.80-6        The GNU version of the "make" util
ii  patch                      2.5.9-1       Apply a diff file to an original
ii  perl [perl5]               5.8.3-2       Larry Wall's Practical Extraction 
ii  perl-modules               5.8.3-2       Core Perl modules.

-- no debconf information

---------------------------------------
Received: (at 237698-done) by bugs.debian.org; 1 Jun 2004 18:57:53 +0000
>From scott@netsplit.com Tue Jun 01 11:57:53 2004
Return-path: <scott@netsplit.com>
Received: from populous.netsplit.com (mailgate.netsplit.com) [62.49.129.34] (qmailr)
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BVESO-0001G8-00; Tue, 01 Jun 2004 11:57:52 -0700
Received: (qmail 24380 invoked from network); 1 Jun 2004 18:57:49 -0000
Received: from unknown (HELO est254-251.brazil.debconf.org) (scott@201.2.133.6)
  by populous.netsplit.com with RC4-MD5 encrypted SMTP; 1 Jun 2004 18:57:49 -0000
Subject: Re: Bug#237698: dpkg-dev: dpkg-buildpackage -v seems not working
From: Scott James Remnant <scott@netsplit.com>
To: Guido Trotter <ultrotter@debian.org>, 237698-done@bugs.debian.org
In-Reply-To: <20040313061109.GA1239@quaqua.net>
References: <20040312214820.5E6791FD2E@executor.studio.tixteam.net>
	 <Pine.LNX.4.58.0403121801030.13832@gradall.private.brainfood.com>
	 <20040313061109.GA1239@quaqua.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-cm6n5HTecIibtNGXjXeh"
Message-Id: <1086116260.17455.3.camel@syndicate>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.5.7 
Date: Tue, 01 Jun 2004 15:57:41 -0300
Delivered-To: 237698-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--=-cm6n5HTecIibtNGXjXeh
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2004-03-13 at 07:11 +0100, Guido Trotter wrote:

> Sorry for reopening the bug, but I'm not convinced... Feel free to close =
it
> again if it's not applicable, but please explain me where I am wrong with
> my interpretation (given below).
>=20
> On Fri, Mar 12, 2004 at 06:01:28PM -0600, Adam Heath wrote:=20
>=20
> > > I've tried to build a package with
> > >
> > > dpkg-buildpackage -v0.7.0+1.0beta1-1 -rfakeroot
> > >
> > > in order to have, included in the changes file, the changelog entry f=
rom
> > > 0.7.0+1.0beta1-2 and after.
> >=20
> > -v takes an *exact* match; it does not find the version that is after(o=
r
> > before).
>=20
doogie is correct here, the match you're looking for must exist in your
changelog file -- and every entry up to, but not including that will get
included.  This matches the manpage description:

>        -vversion
>               In   dpkg-buildpackage,   dpkg-genchanges  and dpkg-parsech=
angelog =20
>               this  causes changelog information from all versions strict=
ly=20
>               later than version to be used.
>=20
> Doesn't this mean that if I have in the changelog:
>=20
> 0.7.0+1.0beta1-1
> 0.7.0+1.0beta1-2
> 0.7.0+1.0beta1-3
> 0.6.0-4
>=20
So, you have a changelog that looks something like:

----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8=
<----
test (0.7.0+1.0beta1-3) unstable; urgency=3Dlow
                                                                           =
    =20
  * this is beta1-3 of 0.7.0
=20
 -- Scott James Remnant <scott@netsplit.com>  Tue,  1 Jun 2004 15:40:12 -03=
00
=20
test (0.7.0+1.0beta1-2) unstable; urgency=3Dlow
=20
  * this is beta1-2 of 0.7.0
=20
 -- Scott James Remnant <scott@netsplit.com>  Tue,  1 Jun 2004 15:40:12 -03=
00
=20
test (0.7.0+1.0beta1-1) unstable; urgency=3Dlow
=20
  * this is beta1-1 of 0.7.0
=20
 -- Scott James Remnant <scott@netsplit.com>  Tue,  1 Jun 2004 15:40:12 -03=
00
=20
test (0.6.0-4) unstable; urgency=3Dlow
=20
  * this is 0.6.0-4
=20
 -- Scott James Remnant <scott@netsplit.com>  Tue,  1 Jun 2004 15:40:12 -03=
00
---->8-------->8-------->8-------->8-------->8-------->8-------->8-------->=
8----

> and I give -v0.7.0+1.0beta1-1 the changelog for -2 and -3 is included?
>=20
Yes:

----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8=
<----
syndicate tmp% dpkg-parsechangelog -ltest.cl -v0.7.0+1.0beta1-1
Source: test
Version: 0.7.0+1.0beta1-3
Distribution: unstable
Urgency: low
Maintainer: Scott James Remnant <scott@netsplit.com>
Date: Tue,  1 Jun 2004 15:40:12 -0300
Changes:
 test (0.7.0+1.0beta1-3) unstable; urgency=3Dlow
 .
   * this is beta1-3 of 0.7.0
 .
 test (0.7.0+1.0beta1-2) unstable; urgency=3Dlow
 .
   * this is beta1-2 of 0.7.0
---->8-------->8-------->8-------->8-------->8-------->8-------->8-------->=
8----

> Moreover doesn't this mean that if I give 0.7.0 (which I have not done)
> the changelog for -1 -2 and -3 is included? From the documentation it see=
ms
> so...
>=20
No, the version you give must exist in the changelog.

Scott
--=20
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

--=-cm6n5HTecIibtNGXjXeh
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAvNGkIexP3IStZ2wRAhjBAJ9kaxTpv0DeumuJR4Q9HD/6QJUlUgCdEBvZ
LXimCo9+vcFVwiBMXTgoreQ=
=z9Le
-----END PGP SIGNATURE-----

--=-cm6n5HTecIibtNGXjXeh--



Reply to: