On 2024-04-20 at 16:19, Christoph Anton Mitterer wrote:
> On Sat, 2024-04-20 at 07:54 -0400, P. J. McDermott wrote:
> > Then the salvage procedure can play out for the full 28+ days
> > specified
> > by developers-reference (21 days to allow the maintainer to object
> &
r
NMU, unless you do that).
You and I both apparently made the exact same changes to backport the
CVE-2024-32487 patch (except your patch still has the original upstream
diffstat instead of the backport, which is fine), so that's a good
confirmation that my patch was (and yours is) correc
d the procedure be sped up
somehow?
[1]: https://salsa.debian.org/pehjota/less
[2]:
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#how-to-salvage-a-package
--
Patrick "P. J." McDermott: http://www.pehjota.net/
Lead Developer, ProteanOS: http://www.pro
library before now.
But the previous bug report claims that this breaks something (so let's
break everything else instead).
[1]: https://wiki.debian.org/UsingSymbolsFiles#C.2B-.2B-_libraries
[2]: https://www.eyrie.org/~eagle/journal/2012-01/008.html
[3]: https://www.eyrie.org/~eagle
tags -1 + patch
thanks
https://salsa.debian.org/lua-team/lua5.4/-/merge_requests/5
--
Patrick "P. J." McDermott: http://www.pehjota.net/
Lead Developer, ProteanOS: http://www.proteanos.com/
Founder and CEO, Libiquity: http://www.libiquity.com/
Package: liblua5.4-0
Version: 5.4.6-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: p...@pehjota.net
Hi,
Since version 5.4.6-1, liblua5.4-c++.so.0.0.0 defines no "lua_*"
function symbols (only "lua_ident@@LUA_5.4"):
$ readelf -s /usr/lib/x86_64-linux-gnu/liblua5.4-c++
On 01/04/2011 07:46 AM, Colin Watson wrote:
> On Tue, Jan 04, 2011 at 12:06:54AM +, Colin Watson wrote:
>
>> On Mon, Jan 03, 2011 at 12:13:01AM +, Colin Watson wrote:
>>
>>> 2011-01-02 Colin Watson
>>>
>>> * grub-core/bus/pci.c (grub_pci_iterate): Skip remaining functions
>>>
On 01/01/2011 06:57 PM, Colin Watson wrote:
> On Sat, Jan 01, 2011 at 06:35:52PM -0500, P. J. McDermott wrote:
>
>> Considering the machines this is affecting (machines with the Poulsbo
>> chipset) and the configuration workaround, I'd bet the issue lies in the
>>
I'm Cc'ing everyone involved in this bug for information, since I don't
know who's subscribed (I am though).
I first noticed this issue a month or two ago on installing Squeeze onto
my Acer Aspire One AO751h, though I didn't have time to do anything more
than install the old working GRUB 2 version
9 matches
Mail list logo
