On Sunday, Jun 15, 2003, at 15:50 US/Eastern, Matt Zimmerman wrote:
Er, no. Those binaries would work perfectly fine if you had built apt
with
the same C++ ABI. But I can't specify in a build-dependency "oh, and
your
apt must be built with the same C++ ABI". I _certainly_ can't do so
retroa
On Saturday, Jun 14, 2003, at 19:17 US/Eastern, Matt Zimmerman wrote:
This was before woody released, before there was
any kind of C++ ABI transition plan, before there was even a g++-3.2
in the
archive. Surely you aren't suggesting that last year's
build-dependencies
should have anticipated
On Saturday, Jun 14, 2003, at 18:45 US/Eastern, Matt Zimmerman wrote:
My two questions were:
1) Why did dpkg-buildpackage wind up compiling with the wrong
compiler? Isn't there a C++ transition plan that should
prevent that.
python-apt will, by default, use the de
On Saturday, Jun 14, 2003, at 01:40 US/Eastern, Matt Zimmerman wrote:
If you had wanted to find out the answer before sending this to
debian-devel, you would not have had to look very far.
bugs.debian.org/python-apt has the answer three times over.
http://bugs.debian.org/cgi-bin/bugreport.cgi?
I've managed to get python-apt (and thus apt-listchanges) working again
on my testing system. What a PITA...
Anyway, I first just tried to recompile python-apt-0.5.4.3. Compile went
fine, but the first attempt to execute apt-listchanges failed with a
dynamic linking error. C++ API change.
First,
5 matches
Mail list logo
