Please remove the following email address: e.little...@gmail.com
On Sun, Sep 10, 2023 at 12:21 AM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Your message dated Sat, 09 Sep 2023 21:18:37 -0700 > with message-id <87sf7mzmn6....@hope.eyrie.org> > and subject line Re: Bug#830913: debian-policy: Allow amd64 systems > without /lib64 > has caused the Debian Bug report #830913, > regarding debian-policy: Allow amd64 systems without /lib64 > to be marked as done. > > This means that you claim that the problem has been dealt with. > If this is not the case it is now your responsibility to reopen the > Bug report if necessary, and/or fix the problem forthwith. > > (NB: If you are a system administrator and have no idea what this > message is talking about, this may indicate a serious mail system > misconfiguration somewhere. Please contact ow...@bugs.debian.org > immediately.) > > > -- > 830913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830913 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > ---------- Forwarded message ---------- > From: Javier Serrano Polo <jav...@jasp.net> > To: sub...@bugs.debian.org > Cc: > Bcc: > Date: Wed, 13 Jul 2016 00:09:59 +0200 > Subject: debian-policy: Allow amd64 systems without /lib64 > Package: debian-policy > Version: 3.9.8.0 > Severity: wishlist > > Some amd64 systems do not have /lib64, although they can run programs > with the interpreter set to /lib64/ld-linux-x86-64.so.2 . It would be > nice if Debian could allow such systems. In section 9.1.1, where it > says: > > The execution time linker/loader, ld*, must still be made > available in the existing location under /lib or /lib64 > > "must" should be "should". > > > > ---------- Forwarded message ---------- > From: Russ Allbery <r...@debian.org> > To: javier--7c8frosbhwv6hrgym4mlhjbycgp...@jasp.net > Cc: 830913-d...@bugs.debian.org > Bcc: > Date: Sat, 09 Sep 2023 21:18:37 -0700 > Subject: Re: Bug#830913: debian-policy: Allow amd64 systems without /lib64 > Russ Allbery <r...@debian.org> writes: > > Javier Serrano Polo <jav...@jasp.net> writes: > > >> Some amd64 systems do not have /lib64, although they can run programs > >> with the interpreter set to /lib64/ld-linux-x86-64.so.2 . It would be > >> nice if Debian could allow such systems. In section 9.1.1, where it > >> says: > > >> The execution time linker/loader, ld*, must still be made > >> available in the existing location under /lib or /lib64 > > >> "must" should be "should". > > > You reported the above bug six years ago, and it looks like it never > > received a reply. I'm sorry about that! > > > I'm confused by this bug report, though. What does "some amd64 systems" > > mean in this context? It looks to me like the amd64 libc6 package > > provides /lib64/ld-linux-x86-64.so.2, so a Debian amd64 system would > > satisfy this. Is there some alternate libc6 package available in Debian > > that does things differently? Or are you thinking of some sort of > > container or other type of restricted system? > > > Also, in this case, how does this work? Is the path somehow remapped at > > the kernel level? (If so, I'm wondering if that would qualify as "made > > available" for the purposes of Policy anyway.) > > It's now been about a year and it looks like this message didn't get a > reply, so I'm going to go ahead and close this bug because I don't think > we have enough information to act on it. If there are more details about > my questions above, feel free to open it. > > -- > Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
