Debian Bug report logs - #13283
dpkg-buildpackage produces an i386 change file for an all (arch) package

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Darren/Torin/Who Ever..." <torin@daft.com>

To: submit@bugs.debian.org

Subject: dpkg-buildpackage produces an i386 change file for an all (arch) package

Date: 23 Sep 1997 00:42:29 -0700

Package: dpkg-dev
Version: 1.4.0.19
-----BEGIN PGP SIGNED MESSAGE-----

Notice, nothing up my sleeve:
>{2}[0]~SRC/debian/weblint/weblint-1.020/debian kitchen:-) ls
>changelog  control    copyright  rules*
>{2}[0]~SRC/debian/weblint/weblint-1.020/debian kitchen:-) grep i386 *
>{2}[1]~SRC/debian/weblint/weblint-1.020/debian kitchen:-) 

But after I run dpkg-buildpackage -tc, I get a weblint_1.20_i386.changes
file:
>{2}[0]~SRC/debian/weblint/weblint-1.020 kitchen:-) dpkg-buildpackage -tc
>[Much output later]
>{2}[0]~SRC/debian/weblint/weblint-1.020 kitchen:-) ls ..
>weblint-1.020/                weblint_1.020-1.dsc	weblint_1.020-1_i386.changes
>weblint_1.020-1.diff.gz       weblint_1.020-1_all.deb	weblint_1.020.orig.tar.gz
>{2}[0]~SRC/debian/weblint/weblint-1.020 kitchen:-) 

It's not that big of a deal since it's not named anywhere and I can
rename it.  Still it should generate the correctly named file.

Darren
- -- System Information
Debian Release: 1.3
Kernel Version: Linux kitchen 2.0.30 #3 Wed Aug 27 08:21:50 -0700 1997 i586 unknown

- -- 
<torin@daft.com> <http://www.daft.com/~torin> <torin@debian.org> <torin@io.com>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Sysadmin, webweaver, postmaster for hire.  C/Perl/CGI programmer and tutor. @
@		     Make a little hot-tub in your soul.		      @

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBNCdy044wrq++1Ls5AQFjpAQAisWfdrUzGQVN3ukylD0JszlaE9LFFvOH
NJpA/m1Y6e/1BWAQKFi84w+ANwULTJ3d+ggS639tW/6xrE3wfrGAl6F+by0vLw6N
SOmgzuxRfsisQN2oTou1ytXjVCLpx4tO5JMQmCWvVOoEIdxcEoVhSr6n8RfTVm7R
3lLOO5VRlKs=
=4Ehn
-----END PGP SIGNATURE-----

Message #10 received at 13283@bugs.debian.org (full text, mbox, reply):

From: Guy Maor <maor@ece.utexas.edu>

To: "Darren/Torin/Who Ever..." <torin@daft.com>, 13283@bugs.debian.org

Subject: Re: Bug#13283: dpkg-buildpackage produces an i386 change file for an all (arch) package

Date: 23 Sep 1997 09:16:18 -0500

"Darren/Torin/Who Ever..." <torin@daft.com> writes:

> >{2}[0]~SRC/debian/weblint/weblint-1.020/debian kitchen:-) ls
> >changelog  control    copyright  rules*
> >{2}[0]~SRC/debian/weblint/weblint-1.020/debian kitchen:-) grep i386 *
> >{2}[1]~SRC/debian/weblint/weblint-1.020/debian kitchen:-) 
> 
> But after I run dpkg-buildpackage -tc, I get a weblint_1.20_i386.changes
> file:

Is the arch `all' and not `any'?


Guy

Message #15 received at 13283@bugs.debian.org (full text, mbox, reply):

From: "Darren/Torin/Who Ever..." <torin@daft.com>

To: Guy Maor <maor@ece.utexas.edu>

Cc: 13283@bugs.debian.org

Subject: Re: Bug#13283: dpkg-buildpackage produces an i386 change file for an all (arch) package

Date: 23 Sep 1997 10:33:22 -0700

-----BEGIN PGP SIGNED MESSAGE-----

Guy Maor, in an immanent manifestation of deity, wrote:
>> But after I run dpkg-buildpackage -tc, I get a weblint_1.20_i386.changes
>> file:
>
>Is the arch `all' and not `any'?

Yes, definitely.  The .deb (weblint_1.20-1_all.deb) comes out named and
setup fine, it's just the changes file that is named wrong.

Darren
- -- 
<torin@daft.com> <http://www.daft.com/~torin> <torin@debian.org> <torin@io.com>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Sysadmin, webweaver, postmaster for hire.  C/Perl/CGI programmer and tutor. @
@		     Make a little hot-tub in your soul.		      @

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBNCf9Po4wrq++1Ls5AQGjdQP/XZxE98KWcyorjLGjivAzZwlh3GgTLZ0n
qgwIyZANnPcHUDCScwAevIlvB7UiHOeXOOZqu8hP7GJf4BL+3Y8kcB4Qz2J/LbsV
ffZJPUkZTgZakLGlDwmz6Fu67VCThBdYHSqP1yl+ILQomZcxwP5UFTltKjU26/Rl
Lf8akNc+X1U=
=5XfE
-----END PGP SIGNATURE-----

Message #20 received at 13283@bugs.debian.org (full text, mbox, reply):

From: Guy Maor <maor@ece.utexas.edu>

To: "Darren/Torin/Who Ever..." <torin@daft.com>

Cc: 13283@bugs.debian.org

Subject: Re: Bug#13283: dpkg-buildpackage produces an i386 change file for an all (arch) package

Date: 23 Sep 1997 14:49:58 -0500

"Darren/Torin/Who Ever..." <torin@daft.com> writes:

> Yes, definitely.  The .deb (weblint_1.20-1_all.deb) comes out named and
> setup fine, it's just the changes file that is named wrong.

oh, sorry, I misread that the .deb file was named incorrectly.  The
.changes file is fine with that name.  The purpose of embedding the
architecture in the .changes filename is merely to avoid collisions;
the filename is not parsed in any way.

In general the .changes should always have the compiled-on arch in its
filename; there may be 'any' archs and 'all' archs produced by the
package.  Making the .changes file use the 'any' arch for packages
which produce solely any binaries is just an unnecessary complication.

So I think there is no bug here.


Guy

Message #25 received at 13283@bugs.debian.org (full text, mbox, reply):

From: "Darren/Torin/Who Ever..." <torin@daft.com>

To: Guy Maor <maor@ece.utexas.edu>

Cc: 13283@bugs.debian.org

Subject: Re: Bug#13283: dpkg-buildpackage produces an i386 change file for an all (arch) package

Date: 24 Sep 1997 10:17:36 -0700

-----BEGIN PGP SIGNED MESSAGE-----

There were a couple places that somewhat confused me in the message
below.  I will rephrase them and you can tell me if it still sounds
correct.

Guy Maor, in an immanent manifestation of deity, wrote:
>oh, sorry, I misread that the .deb file was named incorrectly.  The

Oh.  On fourth read, I got that you -originally- read that the .deb file
was named wrong.

>In general the .changes should always have the compiled-on arch in its
>filename; there may be 'any' archs and 'all' archs produced by the
>package.  Making the .changes file use the 'any' arch for packages
>which produce solely any binaries is just an unnecessary complication.

But it still seems wrong that if a package produces *no* architecture
dependent binaries, that the changes file looks architecture dependent.
Also messes up scripts and such that expect to be able to use the
architecture of the deb to find the changes file.

How about if I change this to a wishlist item?

Darren
- -- 
<torin@daft.com> <http://www.daft.com/~torin> <torin@debian.org> <torin@io.com>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Sysadmin, webweaver, postmaster for hire.  C/Perl/CGI programmer and tutor. @
@		     Make a little hot-tub in your soul.		      @

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBNClLJ44wrq++1Ls5AQFu+wQAjvDtiXM+2tuQG+f6xUyWr4ZELycJRMwq
7CtP34nPmZZYwd6G6QwJP4MaN4N8Phv/8ie/ybGsmP8GtPDa3Lh3kfAty20kZdUr
CEKiALIBALQ4ihC+EcFHuFaSsTogrW36YOXUlwp02xTjb4z5Iy0isM2LxwKDckc9
ESAbQR8VU+Q=
=R2sm
-----END PGP SIGNATURE-----

Message #30 received at 13283@bugs.debian.org (full text, mbox, reply):

From: Guy Maor <maor@ece.utexas.edu>

To: "Darren/Torin/Who Ever..." <torin@daft.com>

Cc: 13283@bugs.debian.org

Subject: Re: Bug#13283: dpkg-buildpackage produces an i386 change file for an all (arch) package

Date: 24 Sep 1997 12:31:16 -0500

"Darren/Torin/Who Ever..." <torin@daft.com> writes:

> Oh.  On fourth read, I got that you -originally- read that the .deb file
> was named wrong.

Right.

> But it still seems wrong that if a package produces *no* architecture
> dependent binaries, that the changes file looks architecture dependent.

Like I said, it doesn't really matter.

> Also messes up scripts and such that expect to be able to use the
> architecture of the deb to find the changes file.

There's nothing preventing a single source package from producing
binaries for more than one arch.  You can't predict the name of the
changes file from only a deb.  A script looking for the .changes file
would be better to find the Source field in the deb, and look for
pack_version_*.changes.

> How about if I change this to a wishlist item?

sure.


Guy

Send a report that this bug log contains spam.