On Sun, Nov 09, 2008 at 02:29:58PM +0100, Elimar Riesebieter wrote:
> * Lionel Elie Mamane [081109 11:30 +0100]
>> Package: alsa-lib
>> Version: 1.0.18-1
>> Severity: serious
>> Justification: lenny release goal
> No, 1.0.18 isn't tagged to went into Lenny!
I never said it was supposed to go into lenny; however, I very highly
doubt we are going to drop that being a serious bug after lenny. Also,
if you prefer another justification, it breaks a "must" directive of
the policy, section 4.9:
clean
This must undo any effects that the build and binary targets may
have had, (...)
What happens here is that the clean fails to undo the effects and
errors out.
That behaviour has been a "Severity: serious" bug since before woody
(in other words, since the oldest policy I have read).
>> Second build:
>> [EMAIL PROTECTED]:~/j/alsa-lib-1.0.18 0 $ debuild -us -uc -b
> This runs fine here. So I don't know how to reproduce?
Does it run fine when run *twice*? That is, you "dpkg-source -x", then
"debuild -us -uc -b" (that runs fine and builds the .debs), then run
"debuild -us -uc -b" again, it fails. The difference might be
different versions of autoconf; I have 2.61-8.
The following sequence also fails:
dpkg-source -x alsa-lib_1.0.18-1.dsc
cd alsa-lib-1.0.18
debuild -us -uc -b
fakeroot make -f debian/rules clean
What I think happens:
configure_cross_compile.patch patches configure, but the configure is
regenarated from configure.in (after the patch is applied to
configure) in the first build run, thus overriding the changes done by
the patch. Then, obviously, the patch doesn't unapply anymore, and the
clean target fails.
>From the log of the first build:
make[1]: Entering directory `/home/master/j/alsa-lib-1.0.18/bibuild'
cd .. && /bin/sh /home/master/j/alsa-lib-1.0.18/missing --run aclocal-1.10
cd .. && /bin/sh /home/master/j/alsa-lib-1.0.18/missing --run automake-1.10
--foreign
cd .. && /bin/sh /home/master/j/alsa-lib-1.0.18/missing --run autoconf
This seems to rerun the whole aclocal / automake / autoconf suite.
--
Lionel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
