Hi,
On 2025. Jul 26., Sat at 23:21, Laurent Pinchart <
[email protected]> wrote:
On Fri, Aug 02, 2019 at 07:03:17PM +0200, Bálint Réczey wrote:
Control: tags -1 confirmed
Severity: -1 wishlist
F. Poirotte <[email protected]> ezt írta (időpont: 2018. ápr. 7., Szo, 18:33):
Package: libevent-dev
Version: 2.0.21-stable-3
Severity: normal
Dear Maintainer,
While bug #675320 added support for multi-arch for the main packages,
it seems
the development package was overlooked. As such, it is not currently
possible to
install the dev package for multiple architectures (eg. amd64 and
i386) at the
same time.
Trying to co-install multiple variants results in apt-get/aptitude
trying to first
remove previously installed packages. Here's the trace when trying to
install
the i386 variant on a system where the amd64 variant is already
installed:
$ sudo aptitude install libevent-dev:i386
The following NEW packages will be installed:
libevent-core-2.0-5:i386{a} libevent-dev:i386{b}
libevent-extra-2.0-5:i386{a} libevent-openssl-2.0-5:i386{a} libevent-pthreads-2.0-5:i386{a}
0 packages upgraded, 5 newly installed, 0 to remove and 2 not upgraded. Need to get 569 kB of archives. After unpacking 1,971 kB will be used. The following packages have unmet dependencies:
libevent-dev : Conflicts: libevent-dev:i386 but 2.0.21-stable-3 is to
be installed
libevent-dev:i386 : Conflicts: libevent-dev but 2.0.21-stable-3 is
installed
The following actions will resolve these dependencies:
Remove the following packages:
1) libevent-dev [2.0.21-stable-3 (now, stable)]
Accept this solution? [Y/n/q/?] q
I checked the control file in testing/sid (libevent-2.1-6
(2.1.8-stable-4))
and the problem is also visible there.
Yes, this is correct.
Header files differ between architectures:
$ diffoscope libevent-dev_2.1.8-stable-4_*
...
│ │ ├── ./usr/include/event2/event-config.h
│ │ │ @@ -439,33 +439,33 @@
│ │ │ your system. */
│ │ │ /* #undef EVENT__PTHREAD_CREATE_JOINABLE */
│ │ │
│ │ │ /* The size of `int', as computed by sizeof. */
│ │ │ #define EVENT__SIZEOF_INT 4
│ │ │
│ │ │ /* The size of `long', as computed by sizeof. */
│ │ │ -#define EVENT__SIZEOF_LONG 8
│ │ │ +#define EVENT__SIZEOF_LONG 4
...
This can be fixed, but the -dev packages are not co-installable
currently.
This is a bit annoying, when using libevent-dev in a CI container aimed
at building for multiple architectures, we have to install the
arch-specific package version manually before each arch build job.
You mentioned it can be fixed. How would you envision that ? Ideally
upstream should geenrate a header file with SIZEOF macros, but that may
be hard to change as it could break some users.
Yes, this change could be offered upstream.
Cheers,
Balint
<div dir="auto">Hi,</div><div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On 2025. Jul 26., Sat at 23:21, Laurent Pinchart <<a href="mailto:
[email protected]">
[email protected]</
> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)" dir="auto">On Fri, Aug 02, 2019 at 07:03:17PM +0200, Bálint Réczey
wrote:<br>
> Control: tags -1 confirmed<br>
> Severity: -1 wishlist<br>
> <br>
> F. Poirotte <<a href="mailto:fpoirotte%
[email protected]" target="_blank">
[email protected]</a>> ezt írta (időpont: 2018.<br>
> ápr. 7., Szo, 18:33):<br>
> ><br>
> > Package: libevent-dev<br>
> > Version: 2.0.21-stable-3<br>
> > Severity: normal<br>
> ><br>
> > Dear Maintainer,<br>
> ><br>
> > While bug #675320 added support for multi-arch for the main packages, it seems<br>
> > the development package was overlooked. As such, it is not currently possible to<br>
> > install the dev package for multiple architectures (eg. amd64 and i386) at the<br>
> > same time.<br>
> ><br>
> > Trying to co-install multiple variants results in apt-get/aptitude trying to first<br>
> > remove previously installed packages. Here's the trace when trying to install<br>
> > the i386 variant on a system where the amd64 variant is already installed:<br>
> ><br>
> > $ sudo aptitude install libevent-dev:i386<br>
> > The following NEW packages will be installed:<br>
> > libevent-core-2.0-5:i386{a} libevent-dev:i386{b} libevent-extra-2.0-5:i386{a} libevent-openssl-2.0-5:i386{a} libevent-pthreads-2.0-5:i386{a}<br>
> > 0 packages upgraded, 5 newly installed, 0 to remove and 2 not upgraded.<br>
> > Need to get 569 kB of archives. After unpacking 1,971 kB will be used.<br>
> > The following packages have unmet dependencies:<br>
> > libevent-dev : Conflicts: libevent-dev:i386 but 2.0.21-stable-3 is to be installed<br>
> > libevent-dev:i386 : Conflicts: libevent-dev but 2.0.21-stable-3 is installed<br>
> > The following actions will resolve these dependencies:<br>
> ><br>
> > Remove the following packages:<br>
> > 1) libevent-dev [2.0.21-stable-3 (now, stable)]<br>
> ><br>
> ><br>
> > Accept this solution? [Y/n/q/?] q<br>
> ><br>
> ><br>
> > I checked the control file in testing/sid (libevent-2.1-6 (2.1.8-stable-4))<br>
> > and the problem is also visible there.<br>
> <br>
> Yes, this is correct.<br>
> <br>
> Header files differ between architectures:<br>
> <br>
> $ diffoscope libevent-dev_2.1.8-stable-4_*<br>
> ...<br>
> │ │ ├── ./usr/include/event2/event-config.h<br>
> │ │ │ @@ -439,33 +439,33 @@<br>
> │ │ │ your system. */<br>
> │ │ │ /* #undef EVENT__PTHREAD_CREATE_JOINABLE */<br>
> │ │ │<br>
> │ │ │ /* The size of `int', as computed by sizeof. */<br>
> │ │ │ #define EVENT__SIZEOF_INT 4<br>
> │ │ │<br>
> │ │ │ /* The size of `long', as computed by sizeof. */<br> > │ │ │ -#define EVENT__SIZEOF_LONG 8<br>
> │ │ │ +#define EVENT__SIZEOF_LONG 4<br>
> ...<br>
> <br>
> This can be fixed, but the -dev packages are not co-installable currently.<br>
This is a bit annoying, when using libevent-dev in a CI container aimed<br>
at building for multiple architectures, we have to install the<br> arch-specific package version manually before each arch build job.<br>
You mentioned it can be fixed. How would you envision that ? Ideally<br> upstream should geenrate a header file with SIZEOF macros, but that may<br>
be hard to change as it could break some users.</blockquote><div dir="auto"><br></div><div dir="auto">Yes, this change could be offered upstream.</div><div dir="auto"><br></div><div dir="auto">Cheers,</div><div dir="auto">Balint</div><div dir="auto"><br><
/div></div></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)