Bug#4561: dpkg-genchanges puts bad Maintainer: in changes file

1996-09-24 Thread Yves Arrouye
I think the solution is in dpkg-genchanges(1): -Dfield=value Override or add an output control file field. This option is understood by dpkg-source, dpkg- gencontrol and dpkg-genchanges. Or -mMy Name [EMAIL PROTECTED]. Yes.

Bug#4561: dpkg-genchanges puts bad Maintainer: in changes file

1996-09-24 Thread Heiko Schlittermann
Yves Arrouye wrote: : :I think the solution is in dpkg-genchanges(1): : -Dfield=value :Override or add an output control file field. This :option is understood by dpkg-source, dpkg- :gencontrol and dpkg-genchanges. : : Or -mMy

Bug#4561: dpkg-genchanges puts bad Maintainer: in changes file

1996-09-23 Thread Yves Arrouye
Package: dpkg-dev Version: 1.4.0 It appears that the Maintainer: field in control is ignored, so the Maintainer: field in the changes file is made with the name of the user calling dpkg-genchanges and the name of the host the file is built on. This is a problem, and in any case, the generated

Bug#4561: dpkg-genchanges puts bad Maintainer: in changes file

1996-09-23 Thread Chris Fearnley
'Yves Arrouye wrote:' Package: dpkg-dev Version: 1.4.0 It appears that the Maintainer: field in control is ignored, so the Maintainer: field in the changes file is made with the name of the user calling dpkg-genchanges and the name of the host the file is built on. This is a problem, and in any