On 10.09.25 Emilio Pozuelo Monfort (pochu@debian.org) wrote:
> On 09/09/2025 23:17, Hilmar Preusse wrote:
Hello Emilio,
Thanks for caring about the issue.
> > Package: release.debian.org
> > Severity: normal
> > X-Debbugs-Cc: proftpd-mod-case@packages.debian.org
> > Control: affects -1 + src:proftpd-mod-case
> > User: release.debian.org@packages.debian.org
> > Usertags: binnmu
> >
> > nmu proftpd-mod-kafka_0.1-1 . hurd-i386 . unstable . -m "Rebuild with proftp-dev"
> > nmu proftpd-mod-vroot_0.9.12-1 . hurd-i386 . unstable . -m "Rebuild with proftp-dev"
>
Of course these do not need rebuilds, here failed the build on
hurd-amd64.
> Only on hurd-i386? Can you explain why? The two first packages failed to
> build the last time, it's not clear to me if this is because the last
> proftpd-dfsg update should address those failures.
>
The error message was always:
In file included from /usr/include/proftpd/conf.h:105,
from mod_case.c:23:
/usr/include/proftpd/fsio.h:41:13: fatal error: attr/xattr.h: No such file or directory
41 | # include <attr/xattr.h>
| ^~~~~~~~~~~~~~
Current situation is:
/usr/include/proftpd/fsio.h:
#ifdef PR_USE_XATTR
# if defined(HAVE_SYS_EXTATTR_H)
# include <sys/extattr.h>
# elif defined(HAVE_SYS_XATTR_H)
# include <sys/xattr.h>
# if defined(HAVE_ATTR_XATTR_H)
# include <attr/xattr.h>
# endif /* HAVE_ATTR_XATTR_H */
# endif /* HAVE_SYS_XATTR_H */
#endif /* PR_USE_XATTR */
and /usr/include/proftpd/config.h
/* Define if you have the <attr/xattr.h> header file. */
/* #undef HAVE_ATTR_XATTR_H */
/* Define if you have the <sys/xattr.h> header file. */
#define HAVE_SYS_XATTR_H 1
Hence I would expect that the builder now tries to read
"sys/xattr.h", which is included in libc0.3-dev. So at least the
issue on top should be solved. If that does not work I probably have
to declare an B-D on libattr1-dev.
Unfortunately I don't know if the situation changed between now and
proftp 1.3.8b as I can't find the proftp-dev package of version
1.3.8b any more. I suggest to trigger the binNMU for one package and
check if the build is OK or at least the error message changes.
Thanks,
Hilmar
Attachment:
signature.asc
Description: PGP signature