On Sat, 4 Dec 2004, Andreas Jochens wrote:
> However, I had severe problems with 'glibc' upgrades when the '/lib64'
> symlink was created by 'glibc' instead of 'base-files'.
> Basically, everything stopped working during the upgrade because
> the '/lib64' temporarily disappeared and the binarie
On Sun, Dec 05, 2004 at 04:39:06PM +0100, Santiago Vila wrote:
>
> Could you please provide details about the problem of having the
> symlinks in glibc?
>
> Is it that glibc has a versioned Replaces: base-files and dpkg removes
> the symlink in base-files before installing the one from glibc,
> c
On Sun, 5 Dec 2004, Kurt Roeckx wrote:
> On Sun, Dec 05, 2004 at 04:39:06PM +0100, Santiago Vila wrote:
> >
> > Could you please provide details about the problem of having the
> > symlinks in glibc?
> >
> > Is it that glibc has a versioned Replaces: base-files and dpkg removes
> > the symlink in
Santiago Vila <[EMAIL PROTECTED]> writes:
> On Sat, 4 Dec 2004, Andreas Jochens wrote:
>
>> However, I had severe problems with 'glibc' upgrades when the '/lib64'
>> symlink was created by 'glibc' instead of 'base-files'.
>> Basically, everything stopped working during the upgrade because
>> th
On Sun, 5 Dec 2004, Goswin von Brederlow wrote:
> The problem is we already have it in base-files on every installed
> amd64 system.
Yes, I'm fully aware of that. See the message I wrote after that.
> > In such case I think it would be completely acceptable that the preinst
> > simply manipulate
On Sat, Nov 06, 2004 at 12:43:36PM -0500, Daniel Jacobowitz wrote:
> "Invalid read" is not a memory leak - this says something has been
> freed and then used. It looks like the destructors are running in the
> wrong order, maybe.
>
> We'd still need a testcase.
A somewhat crappy testcase:
$ apt-
On Sun, Dec 05, 2004 at 06:14:24PM +0100, Santiago Vila wrote:
> On Sun, 5 Dec 2004, Kurt Roeckx wrote:
>
> > On Sun, Dec 05, 2004 at 04:39:06PM +0100, Santiago Vila wrote:
> > >
> > > Could you please provide details about the problem of having the
> > > symlinks in glibc?
> > >
> > > Is it that
At Sat, 4 Dec 2004 18:13:24 +0100,
Guillermo S. Romero <[EMAIL PROTECTED]> wrote:
> Denis said I have to use UTF-8 so Xlib works, ignoring what locale -a
> report, and you say utf8 is the right value, but that will make Xlib
> not work. Denis reasoning:
>
> The name listed in /usr/share/i18n/SUP
On Sun, Dec 05, 2004 at 05:28:19PM -0500, Jurij Smakov wrote:
> 0001-00012000 r-xp 08:11 458670 a.out
> 0002-00024000 rwxp 08:11 458670 a.out
> 00024000-08002000 rwxp 00024000 00:00 0
> mmap(0x1, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) =
> 0x1
>
Hello,
[Please CC the replies to me, as I am not subscribed to this list]
While investigating recent FTBFS bug reports [0,1] I have come to a
conclusion, that something is wrong with either the dynamic linker
ld-linux.so.2, or the way kernel handles certain mmap() calls (at
least on sparc64, possib
10 matches
Mail list logo
