Your message dated Fri, 7 Jun 2019 06:26:59 +0200
with message-id <20190607042658.ga30...@alf.mars>
and subject line Re: Bug#930077: systemd: add :native to python3-evdev build
dependency
has caused the Debian Bug report #930077,
regarding systemd: add :native to python3-evdev build dependency
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
930077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd
Version: 241-5
Please change the build dependency
python3-evdev <!nocheck>,
to
python3-evdev:native <!nocheck>,
Only with that change I could cross-compile the package. TIA!
--- End Message ---
--- Begin Message ---
Hi Michael,
Thank you for pulling me in the loop. Can I slightly update your routing
table here? Please use debian-cr...@lists.debian.org. Most likely,
you'll still get an answer from me, but I'm trying to change that.
On Thu, Jun 06, 2019 at 10:37:02PM +0200, Michael Biebl wrote:
> Am 06.06.19 um 22:16 schrieb W. Martin Borgert:
> > On 2019-06-06 19:59, Michael Biebl wrote:
> >> Could you give a bit more details on why this is necessary and e.g. why
> >> python3-pyparsing does not need :native?
> >
> > I'm not even sure myself, but I try my best :-)
> >
> > Short: python3-evdev is any, python3-pyparsing is all.
> >
> > Longer: When cross-building, one needs the -dev packages for the
> > host arch, e.g. building on amd64 for armel needs
> > libfoo-dev:armel. Anything that is executed during build, e.g.
> > yacc, lex, Python stuff must be amd64, of course. The Python
> > interpreter must be amd64 ("native), and that counts for "any"
> > modules, too, e.g. python3-evdev. python3-pyparsing is "all", so
> > there is no need for :native.
>
> I guess the problem is that python3.7 is marked as Multi-Arch: allowed?
This looks like an X/Y problem to me. Let me go back to the initial bug
submission. There Martin wrote:
| Only with that change I could cross-compile the package. TIA!
The relevant dependency is already marked <!nocheck> and during cross
compilation we generally pass that profile. So the relevant dependency
is irrelevant to cross building. It seems to me that Martin simply
forgot passing the right profiles and options, which is strange, because
both sbuild and pbuilder pass them by default. Indeed crossqa confirms
that all is fine for systemd:
http://crossqa.debian.net/src/systemd
For this reason, I am simply closing the bug. Martin should contact
d-cross@l.d.o or #d-bootstrap to figure out of to fix his cross build
environment.
Helmut
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
