Control: severity -1 serious
Control: tags -1 + ftbfs
Hi Maintainer and i386, arm, mips porters
> As far as I can tell, the reason is that coreutils now uses a 64-bit
> time_t and functions with a "64" suffix. Datefudge however does not
> expose nor implement such functions.
As can be seen on re
On Thu, 25 Aug 2022 at 21:18, Wookey wrote:
> Yeah I should be on the list, but it looks like I wrote a reply to the
> 'call for porters' back in Decemeber, but stopped to look something
> up, got distracted and never actually sent it.
I'd be happy to add you to the list, if you sent that mail no
Hi Adrian
On Wed, 16 Feb 2022 at 13:36, John Paul Adrian Glaubitz
wrote:
> On 2/16/22 12:33, Christian Kastner wrote:
> >> Bus errors are normally easy to spot. Just run the code in question through
> >> GDB and see where it crashes. Then look at the backtrace with the debug
> >> symbols installe
Dear Arm Porters
Is anyone able to help with the bus error on armhf please?
On Wed, 16 Feb 2022 at 09:33, Andreas Tille wrote:
>
> Control: tags -1 upstream
> Control: forwarded -1
> https://github.com/scikit-learn/scikit-learn/issues/22503
> also sent another bug report
> https://gi
Hi YunQiang Su
On Sun, 26 Dec 2021 at 11:17, YunQiang Su wrote:
>
> For mipsel and mips64el, I
> - test most packages on this architecture
> - run a Debian testing or unstable system on port that I use regularly
> - fix toolchain issues
> - triage arch-specific bugs
> - fix arch-relat
Hi
A friendly reminder about the porter roll call for bookworm.
On Sat, 2 Oct 2021 at 11:57, Graham Inggs wrote:
> We are doing a roll call for porters of all prospective release
> architectures. If you are an active porter behind one of these
> architectures [1] and intend to continu
Hi
We are doing a roll call for porters of all prospective release
architectures. If you are an active porter behind one of these
architectures [1] and intend to continue for the development cycle of
Debian Bookworm (est. release mid-2023), please respond with a signed
email containing the follow
Hi
A friendly reminder about the porter roll call for bullseye.
On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote:
> We are doing a roll call for porters of all release architectures. If
> you are an active porter behind one of the release architectures [1]
> for the entire lifetime
Hi
We are doing a roll call for porters of all release architectures. If
you are an active porter behind one of the release architectures [1]
for the entire lifetime of Debian Bullseye (est. end of 2024), please
respond with a signed email containing the following before Friday,
November 27:
*
Hi!
Dpkg in Ubuntu carries a patch introduced in dpkg 1.16.1.2ubuntu2 from
December 2011.
The changelog entry reads:
* Apply patch from Steve McIntyre to special-case armhf/armel ELF
objects in Shlibs/Objdump.pm, so we don't get incorrect deps.
Wine-development since 1.9.9-1 has a script (sona
Hi Peter
On 19 April 2016 at 21:17, Peter Colberg wrote:
> julia 0.4.5-3 FTBFS on armel due to an outdated llvm-3.8 package:
Yes, suihkulokki pointed this out previously.
I requested removal of the armel binaries in bug #820713, and that
already has been processed.
Since the 0.4.5-3 upload, the
On 09/04/2016 13:41, Riku Voipio wrote:
And yes, vorr is an NEON instruction.
OK, so that is confirmed then.
Any ideas on where to disable NEON? I couldn't find anything explicitly
enabling it in the Julia source. The problem seems to have appeared
when we switched from LLVM 3.7 to LLVM 3.
On 9 April 2016 at 00:53, peter green wrote:
> It would be useful if someone can reproduce the issue and get a dissasembly
> of the failure location.
I hope this is useful. I'll leave my screen session on abel.d.o. open
in case I need to fetch more information.
[Thread debugging using libthread
On 8 April 2016 at 21:16, Emilio Pozuelo Monfort wrote:
> Why did you switch to 3.8? The default in unstable is 3.6 and in experimental
> is
> 3.7.
I understood there were severe performance regressions with Julia on
LLVM > 3.3 that were only fixed in 3.8.
> I'm Cc'ing the arm and llvm lists, m
Hi
During the ARM ports Bof at DebConf15, we (Paul Gevers and I)
mentioned an issue we were experiencing with fpc/lazarus builds on
ARM.
We have now found that the problem is related to the '-z relro' hardening flag.
If we build Lazarus with the Debian default hardening flags, which
include '-z
15 matches
Mail list logo
