Re: Open security issues affecting trixie which are not RC (2025-04-29)

2025-04-29 Thread Jeffrey Walton
On Tue, Apr 29, 2025 at 2:21 PM Moritz Mühlenhoff wrote: > > Hi, > giving this a try for the trixie release: > > If anyone wants to help getting trixie in good shape: Here's > a list of open security issues below the RC threshold which > would still be useful to fix before the release. Many of > t

Re: RFC: dropping armel from Debian for the upcoming release

2024-08-21 Thread Jeffrey Walton
On Wed, Aug 21, 2024 at 11:18 AM Hector Oron wrote: > > [...] > There was also a suggestion to mark non-for-us or stop building large > packages that may not be that useful in the armel architecture, such > LibreOffice, possibly some desktops, etc.. since armel is mostly meant > for embedded and

Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf

2024-03-26 Thread Jeffrey Walton
On Tue, Mar 26, 2024 at 7:44 PM Thorsten Glaser wrote: > > I’m answering back from the $dayjob address because Googlemail > cannot communicate with normal mailservers. > > >I can send you two dev boards, if you want them. The first is > >Wandboard Dual (Cortex-A9, ARMv7 with NEON), and the second

Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf

2024-03-26 Thread Jeffrey Walton
On Tue, Mar 26, 2024 at 6:30 PM Thorsten Glaser wrote: > > [...] > > The options for the armel/armhf porters are to either get the > .debs from me, install them in a chroot, and then the other B-D, > and rebuild the packages, or to use dpkg --force-depends to > install the dependencies (which make

Re: Ability to further support 32bit architectures

2024-01-11 Thread Jeffrey Walton
On Thu, Jan 11, 2024 at 5:45 AM Bastian Blank wrote: > > On Thu, Jan 11, 2024 at 09:48:34AM +, Dimitri John Ledkov wrote: > > Disabling debug symbols, enabling debug symbol zstd compression, using > > split debug symbols (disabled BTF usage) should help here. > > Okay, maybe more workarounds e

Re: Thinking about a "jessie and a half" release

2016-09-09 Thread Jeffrey Walton
>>> Is anybody else interested in helping? Thoughts/comments? >> >>Sorry to bump an old thread >> >>Please consider moving to Clang 3.8 or 4.0 as the LLVM front end for >>the platform. >> >>Clang 3.5 and 3.6 are no longer maintained. The bugs we are >>discovering and reporting are being closed

Re: Thinking about a "jessie and a half" release

2016-09-06 Thread Jeffrey Walton
> There's something I've been pondering for a while, along with some > other folks - it might be useful to do a "jessie and a half" release, > similarly to what we did in the etch days. That's *basically* just > like a normal jessie release, but with a few key updates: > > * backports kernel > *

Re: Thinking about a "jessie and a half" release

2016-07-12 Thread Jeffrey Walton
> There's something I've been pondering for a while, along with some > other folks - it might be useful to do a "jessie and a half" release, > similarly to what we did in the etch days. That's *basically* just > like a normal jessie release, but with a few key updates: > > * backports kernel > *