zaptel: ztmonitor etc. not deleted

[Kilian Krause]

--=-bdQcziuhhzsb4I3Ls+02
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi Tzafrir,

Am Sonntag, den 13.03.2005, 21:55 +0200 schrieb Tzafrir Cohen:
> Hi
>=20
> I got the following errors when trying to build zaptel:
>=20
> dpkg-source: cannot represent change to ztmonitor: binary file contents c=
hanged
> dpkg-source: cannot represent change to ztspeed: binary file contents cha=
nged
> dpkg-source: cannot represent change to zttest: binary file contents chan=
ged
>=20
> Indeed the makefile had not instructions to delete it in the 'clean'
> target. I then tried to edit the Makefile patch, only to figure out the
> patch is being unapplied before calling $(MAKE) clean.
>=20
> A quick fix:
> add to the 'clean' in debian/rules:
>=20
> 	rm -f fxstest ztmonitor ztspeed zttest

yes, broken clean targets from upstreams are quite common nowadays.
Thanks for the fix. It was just sneaked into SVN and will accompany next
uploads.

> However this is not the first time I stumble upon this type of bug. Any
> simple way to modify the build scripts so they'll try to:
>=20
> * build
> * clean
> * build
>=20
> ? Any point in that?

running debuild twice does exactelly that. You can also unpack, copy to
a safe place, run "debuild -us -uc -rfakeroot&&fakeroot debian/rules
clean" and compare to the backup copy.

--=20
Best regards,
 Kilian

--=-bdQcziuhhzsb4I3Ls+02
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil

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

iD8DBQBCNJzxvdkzt4X+wX8RAo0lAJwIAznmXHisht6salmOm+HnPghkogCfW3wv
lid3OCIaFG5sY1PyA4Foaxo=
=XrGs
-----END PGP SIGNATURE-----

--=-bdQcziuhhzsb4I3Ls+02--