Bug#322926: merging changes files breaks wrappers (like debuild)

2005-12-07 Thread Julian Gilbey
On Sun, Dec 04, 2005 at 12:42:40AM +0300, Nikita V. Youshchenko wrote: Devscripts may handle this situation by just picking not $package_$version_$arch.changes, but instead find the file that matches $package_$version_*.changes pattern. In one of the the previous mails, I wrote that there

Bug#322926: merging changes files breaks wrappers (like debuild)

2005-12-07 Thread Nikita V. Youshchenko
On Sun, Dec 04, 2005 at 12:42:40AM +0300, Nikita V. Youshchenko wrote: Devscripts may handle this situation by just picking not $package_$version_$arch.changes, but instead find the file that matches $package_$version_*.changes pattern. In one of the the previous mails, I wrote that

Bug#322926: merging changes files breaks wrappers (like debuild)

2005-12-03 Thread Nikita V. Youshchenko
Hi, If dpkg-cross is installed, it provides it's own dpkg-buildpackage, which potentially replaces the *_${arch}.changes file with *_source+${arch}.changes. When debuild calls helpers like lintian or debsign, these will fail because debuild assumes the *_${arch}.changes filename.

Bug#322926: merging changes files breaks wrappers (like debuild)

2005-12-03 Thread Nikita V. Youshchenko
I tried to reproduce the situation where 'source+arch' appears, but failed. And, as far as I can read the code, dpkg-cross version of dpkg-buildpackage should not do this. First, before doing any .changes processing, it checks if there are exactly two files that match pattern

Bug#322926: merging changes files breaks wrappers (like debuild)

2005-12-03 Thread Julian Gilbey
On Sat, Dec 03, 2005 at 11:41:14PM +0300, Nikita V. Youshchenko wrote: I probably understood how 'sources' come in. If one first runs 'dpkg-buildpackage -S', a .changes file will be created with 'sources' in the arch part of the name. Later, if 'dpkg-buildpackage' is run to create binary

Bug#322926: merging changes files breaks wrappers (like debuild)

2005-12-02 Thread Nikita V. Youshchenko
On Sat, Aug 20, 2005 at 11:32:07PM +0400, Nikita V. Youshchenko wrote: Package: dpkg-cross, devscripts, dpkg-dev Severity: normal If dpkg-cross is installed, it provides it's own dpkg-buildpackage, which potentially replaces the *_${arch}.changes file with

Bug#322926: merging changes files breaks wrappers (like debuild)

2005-12-01 Thread Julian Gilbey
On Sat, Aug 20, 2005 at 11:32:07PM +0400, Nikita V. Youshchenko wrote: Package: dpkg-cross, devscripts, dpkg-dev Severity: normal If dpkg-cross is installed, it provides it's own dpkg-buildpackage, which potentially replaces the *_${arch}.changes file with *_source+${arch}.changes.

Bug#322926: merging changes files breaks wrappers (like debuild)

2005-08-20 Thread Nikita V. Youshchenko
Package: dpkg-cross, devscripts, dpkg-dev Severity: normal If dpkg-cross is installed, it provides it's own dpkg-buildpackage, which potentially replaces the *_${arch}.changes file with *_source+${arch}.changes. When debuild calls helpers like lintian or debsign, these will fail because

Bug#322926: merging changes files breaks wrappers (like debuild)

2005-08-13 Thread martin f krafft
Package: dpkg-cross, devscripts, dpkg-dev Severity: normal If dpkg-cross is installed, it provides it's own dpkg-buildpackage, which potentially replaces the *_${arch}.changes file with *_source+${arch}.changes. When debuild calls helpers like lintian or debsign, these will fail because debuild