I don't think I have access or permissions to rename/reassign the bug to ftpmaster so they can remove the armel binaries.
How can I move this forward so that the package doesn't get autoremoved next week? Thanks, Thomas On Fri, Jun 14, 2019 at 2:28 PM Thomas Calderon <calderon.tho...@gmail.com> wrote: > OK, let's have them removed, when I will push an updated version, I will > make sure to remove armel from the list of targets. > > Do I need to do anything else for now? > > Thanks, > > Thomas > > On Thu, Jun 13, 2019 at 8:02 PM Peter Green <plugwash-urg...@p10link.net> > wrote: > >> On 13/06/19 10:00, Thomas Calderon wrote: >> > Hi there, >> > >> > It's unfortunate that OCaml has removed the support for ocamlopt for >> armel, it sounds like CamlCrush will not be able to ship for armel. >> > Is it required that I create an updated Debian release excluding armel >> as a target or as you said, ftpmaster can just remove the binaries? >> Removing the binaries is enough in cases like this, they won't be rebuilt >> until/unless their build-dependencies become available again. >> >> I'm not sure if the binary removal will propagate automatically from >> unstable to testing during the freeze or if one needs to ask the release >> team for that. >> >>
