=== guiverc2 is now known as guiverc | ||
sudip | a newbie question - If a package is added to the "lto-disabled-list", then will the package be automatically rebuilt after the "lto-disabled-list" has been updated? | 11:38 |
---|---|---|
sudip | also, is it preferable to disable from "lto-disabled-list" or from d/rules ? | 11:43 |
ginggs | sudip: someone will need to retry the builds after the new lto-disabled-list is published | 18:43 |
ginggs | packages in main should ideally be fixed, or LTO disabled in the package | 18:45 |
sudip | ginggs: ok, so packages in Universe then go via lto-disabled-list. and how is it handled if I have to disable LTO in a package in Mantic? | 18:45 |
ginggs | packages in universe should also ideally be fixed, or failing that, added to lto-disabled-list (to avoid adding delta) | 18:46 |
ginggs | sudip: at a guess, i'd say we'd want to "fix" it the same way we fixed it in noble | 18:50 |
ginggs | that being said, it doesn't look like we've SRU'd lto-diabled-list in the past | 18:51 |
sudip | ginggs: I dont know the fix for Noble yet. There is a segfault when python tries to import, and from the coredump I get bad call flags of _PyExc_SystemError.lto_priv.0. So I disabled LTO in d/rules to test and that worked. | 18:52 |
ginggs | sudip: i think we'd want a fix in noble before we SRU. what is the package in question? | 18:56 |
sudip | LP: #1994145 | 18:56 |
-ubottu:#ubuntu-devel- Launchpad bug 1994145 in mirage (Ubuntu) "Mirage segfaults immediately when run" [Undecided, In Progress] https://launchpad.net/bugs/1994145 | 18:56 | |
* sudip has added the stacktrace in the upstream issue | 18:57 | |
* sudip will check back later what ginggs suggests | 19:15 | |
=== guiverc2 is now known as guiverc |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!