Thanks for the responses and attempts to build! Yes, it takes quite a bit of memory unfortunately, due to some very large auto-generated swig wrappers combined with some complicated boost usage.
In any case, I was not so much asking for help building/reproducing, as I was asking what I can do other than to reply to the bug, which seems not to be eliciting a response, to either avoid or delay the auto-removal process. Is auto-removal policy documented somewhere? Unfortunately all my searches turn up "apt-get autoremove" help instead. I am really worried the package will get removed from the upcoming Debian release because of this. regards, Steve On Thu, Apr 29, 2021 at 11:47 PM Eriberto Mota <eribe...@debian.org> wrote: > > I used a trivial jail with chroot. I can't reproduce the issue. > > Regards, > > Eriberto > > > Em qui., 29 de abr. de 2021 às 18:30, Tobias Frost <t...@debian.org> escreveu: > > > > On Thu, Apr 29, 2021 at 05:25:28PM +0200, Stephen Sinclair wrote: > > > Hi Mentors, > > > > > > My package siconos currently has a bug filed [1] and has been marked > > > for autoremoval from testing. > > > > > The problem is that I cannot reproduce it. The failure is on a test > > > that depends on another package, so I am wondering if there was just a > > > glitch here? I have replied to the bug report with working build > > > logs, but there has been no further activity, so I am not sure what > > > further action I can take to avoid that the package gets removed. > > > > > > Thanks for any help. > > > Steve > > > > > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986515 > > > > I could also not reproduce it in a pbuilder chroot. Might indeed be a glitch > > or some other dependency causing this… > > I'd either downgrade it to non RC and tag it unreproducible or close it with > > the request to reopen if it pops up again. > > > > -- > > tobi > > >