[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#966117: marked as done (libcppunit-dev: Can libcppunit-dev become Multi-Arch:same?)

Your message dated Wed, 29 Jul 2020 21:40:59 +0200
with message-id <d2595fb2-fabd-b97d-52d7-790f84b73ef7@debian.org>
and subject line Re: Bug#966117: libcppunit-dev: Can libcppunit-dev become Multi-Arch:same?
has caused the Debian Bug report #966117,
regarding libcppunit-dev: Can libcppunit-dev become Multi-Arch:same?
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 owner@bugs.debian.org
immediately.)


-- 
966117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966117
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libcppunit-dev
Version: 1.14.0-3
Severity: normal

Dear maintainers,

libcppunit-dev's control file does not currently specify "Multi-Arch: same."

I may be missing an important detail, but it seems that it could specify it
because the included libraries are installed in the right architecture-dependent
folder.

The current situation severely hinders the cross-compileability of libcppunit.
For example, when trying to cross-compile for arm64, an

  apt-get install libcppunit-dev:arm64

will uninstall libcppunit-dev:amd64 (and libcppunit-1.x:amd64).

(Not using a separate sysroot for the cross-compilation and instead
installing other-architectural build dependencies on the host is
a bit yucky-ish, of course, but besides the point.)

I have verified that the libcppunit packages in Buster, Bullseye, Sid
lack a "Multi-Arch: same". Is this an omission, or am I simply missing
a crucial piece on why it cannot apply?

Thanks a lot for your attention.

Best regards,

Tobias

-- System Information:
Debian Release: 10.3
  APT prefers buster
  APT policy: (500, 'buster')
Architecture: i386 (i686)
Foreign Architectures: arm64

Kernel: Linux 4.15.0-106-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libcppunit-dev depends on:
ii  libcppunit-1.14-0  1.14.0-3

libcppunit-dev recommends no packages.

Versions of packages libcppunit-dev suggests:
pn  libcppunit-doc  <none>

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi,

Am 27.07.20 um 17:17 schrieb Rittweiler, Tobias:
>
>     I may be missing an important detail, but it seems that it could
>     specify it
>     because the included libraries are installed in the right
>     architecture-dependent
>     folder.
>
You at least might have missed that I don't care about Multi-Arch at
all. :-)

So anything which is Multi-Arch: is (if I didn't inherit) is result of a
bug report like this or someone else doing it where it still is
unnecessary ;-)


>
> I just noticed that the list of header files is *not* the same. The
> arm64 package also includes a
> /usr/bin/cppunit-config binary. So there is definitively more worked
> needed to make the package
> be "Multi-Arch: same".
>
> This makes this bug entry mood. Please close.
>
OK. Right.


Thanks, Closing. :)


Regards,


Rene

--- End Message ---
Reply to: