How to handle breakages when the size of a class in a shared lib increases?

2023-07-11 Thread Pierre Gruet
Dear Mentors, I maintain a package that builds a shared library. I uploaded a new upstream version of it to Debian, with no removed symbols, no ABI change... Fine. Unfortunately, it turns out fields were added to some class (of which size thus increased) in the shared library, so that binari

Re: How to handle breakages when the size of a class in a shared lib increases?

2023-07-11 Thread Tobias Frost
Hi Pierre, On Tue, Jul 11, 2023 at 04:10:49PM +0200, Pierre Gruet wrote: > Dear Mentors, > > I maintain a package that builds a shared library. I uploaded a new upstream > version of it to Debian, with no removed symbols, no ABI change... Fine. > Unfortunately, it turns out fields were added to

Re: How to handle breakages when the size of a class in a shared lib increases?

2023-07-11 Thread Andrey Rakhmatullin
On Tue, Jul 11, 2023 at 04:10:49PM +0200, Pierre Gruet wrote: > I maintain a package that builds a shared library. I uploaded a new upstream > version of it to Debian, with no removed symbols, no ABI change... Fine. Tobias already explained that there was actually an ABI change, but... > How shoul

Re: How to handle breakages when the size of a class in a shared lib increases?

2023-07-11 Thread Pierre Gruet
Hi tobi, Le 11/07/2023 à 16:52, Tobias Frost a écrit : Hi Pierre, On Tue, Jul 11, 2023 at 04:10:49PM +0200, Pierre Gruet wrote: Dear Mentors, I maintain a package that builds a shared library. I uploaded a new upstream version of it to Debian, with no removed symbols, no ABI change... Fine.

Bug#1036751: RFS: mini-httpd/1.30-4 [ITA] -- Small HTTP server

2023-07-11 Thread Alexandru Mihail
Hello again, >In short, considering debian-legal's input, should I mention the NCSA >copyright notice in debian/copyright for Files: htpasswd.c, adding a >separate License: NCSA field to clarify the provenance of said source >? After a bit more research into how other projects treat NCSA bits I'd

Re: How to handle breakages when the size of a class in a shared lib increases?

2023-07-11 Thread Sune Vuorela
On 2023-07-11, Pierre Gruet wrote: > Unfortunately, it turns out fields were added to some class (of which > size thus increased) in the shared library, so that binaries built > against a previous version of it now segfault as they are not allocating > enough space. Either you need to do a pac