Bug#1069310: FTBFS: tests failed

2024-05-06 Thread Reinhard Tartler
I spent about half an hour looking at this, and wanted to share my thoughts:

- the build / tests succeed on all architectures but mips64el
- the panic in question appears to come from here:
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print_linux.go/#L13
--
a map[int64]string is being set with the key "syscall.O_DIRECT" to the
value "DIRECT".
- that map is pre-initialized here:
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print.go/#L64-L80
- on most architectures, such as amd64, the constant `syscall.O_DIRECT` is
set to the value 0x4000, cf.
https://cs.opensource.google/go/go/+/master:src/syscall/zerrors_linux_amd64.go;l=627;bpv=0;bpt=1
- on mipsel64, the value is set to 0x8000, cf.
https://cs.opensource.google/go/go/+/master:src/syscall/zerrors_linux_mips64.go;l=774?q=O_DIRECT=go%2Fgo=11
- this value conflicts with
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print.go/#L77
so
we now get conflicting values for the same key. This explains the message
"panic: DIRECT (8000) overlaps with LARGEFILE (8000).

-- 
regards,
Reinhard


Processed: Re: Bug#1069310: FTBFS: tests failed

2024-04-19 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 golang-github-hanwen-go-fuse-dev
Bug #1069310 [src:gocryptfs] FTBFS: tests failed
Bug reassigned from package 'src:gocryptfs' to 
'golang-github-hanwen-go-fuse-dev'.
No longer marked as found in versions gocryptfs/2.4.0-1.
Ignoring request to alter fixed versions of bug #1069310 to the same values 
previously set
> affects -1 src:gocryptfs
Bug #1069310 [golang-github-hanwen-go-fuse-dev] FTBFS: tests failed
Added indication that 1069310 affects src:gocryptfs

-- 
1069310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1069310: FTBFS: tests failed

2024-04-19 Thread Shengjing Zhu
Control: reassign -1 golang-github-hanwen-go-fuse-dev
Control: affects -1 src:gocryptfs

On Sat, Apr 20, 2024 at 2:54 AM Andrey Rakhmatullin  wrote:
>
> Source: gocryptfs
> Version: 2.4.0-1
> Severity: serious
> Tags: ftbfs
>
> https://buildd.debian.org/status/fetch.php?pkg=gocryptfs=mips64el=2.4.0-1%2Bb6=1713405841=0
>
> panic: DIRECT (8000) overlaps with LARGEFILE (8000)
>
> goroutine 1 [running]:
> github.com/hanwen/go-fuse/fuse.(*flagNames).set(0xc000126708, 0x8000,
> {0x1201d640e, 0x6})
> 
> /<>/_build/src/github.com/hanwen/go-fuse/fuse/print.go:126
> +0x234
> github.com/hanwen/go-fuse/fuse.init.1()
> /<>/_build/src/github.com/hanwen/go-
> fuse/fuse/print_linux.go:13 +0x68
> FAILgithub.com/rfjakob/gocryptfs/internal/syscallcompat 0.007s
>

This is similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061659 and
https://github.com/hanwen/go-fuse/issues/502 which is only fixed on
i386.

-- 
Shengjing Zhu



Bug#1069310: FTBFS: tests failed

2024-04-19 Thread Andrey Rakhmatullin
Source: gocryptfs
Version: 2.4.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=gocryptfs=mips64el=2.4.0-1%2Bb6=1713405841=0

panic: DIRECT (8000) overlaps with LARGEFILE (8000)

goroutine 1 [running]:
github.com/hanwen/go-fuse/fuse.(*flagNames).set(0xc000126708, 0x8000,
{0x1201d640e, 0x6})
/<>/_build/src/github.com/hanwen/go-fuse/fuse/print.go:126
+0x234
github.com/hanwen/go-fuse/fuse.init.1()
/<>/_build/src/github.com/hanwen/go-
fuse/fuse/print_linux.go:13 +0x68
FAILgithub.com/rfjakob/gocryptfs/internal/syscallcompat 0.007s


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled