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

Bug#969187: marked as done (librtmidi-dev: content differs vastly between architectures)



Your message dated Sat, 29 Aug 2020 00:38:46 +0200
with message-id <20200828223846.GB165715@ramacher.at>
and subject line Re: Bug#969187: librtmidi-dev: content differs vastly between architectures
has caused the Debian Bug report #969187,
regarding librtmidi-dev: content differs vastly between architectures
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.)


-- 
969187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969187
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: librtmidi-dev
Version: 3.0.0~ds1-2+b1
Severity: important
X-Debbugs-Cc: tg@mirbsd.de

The amd64 package…

https://packages.debian.org/sid/amd64/librtmidi-dev/filelist

/usr/include/rtmidi/RtMidi.h
/usr/include/rtmidi/rtmidi_c.h
/usr/lib/x86_64-linux-gnu/librtmidi.so
/usr/lib/x86_64-linux-gnu/pkgconfig/rtmidi.pc
/usr/share/doc/librtmidi-dev/README.md
/usr/share/doc/librtmidi-dev/changelog.Debian.amd64.gz
/usr/share/doc/librtmidi-dev/changelog.Debian.gz
/usr/share/doc/librtmidi-dev/changelog.gz
/usr/share/doc/librtmidi-dev/copyright

… and the arm64 package…

https://packages.debian.org/sid/arm64/librtmidi-dev/filelist

/usr/include/RtMidi.h
/usr/include/rtmidi/RtMidi.h
/usr/include/rtmidi/rtmidi_c.h
/usr/lib/aarch64-linux-gnu/librtmidi.so
/usr/lib/aarch64-linux-gnu/librtmidi.so
/usr/lib/aarch64-linux-gnu/pkgconfig/rtmidi.pc
/usr/lib/aarch64-linux-gnu/pkgconfig/rtmidi.pc
/usr/share/doc/librtmidi-dev/README.md
/usr/share/doc/librtmidi-dev/changelog.Debian.arm64.gz
/usr/share/doc/librtmidi-dev/changelog.Debian.gz
/usr/share/doc/librtmidi-dev/changelog.Debian.gz
/usr/share/doc/librtmidi-dev/changelog.gz
/usr/share/doc/librtmidi-dev/copyright
/usr/share/doc/librtmidi-dev/copyright
/usr/share/doc/librtmidi-dev/readme
/usr/share/doc/librtmidi-dev/release.txt.gz

… differ *vastly* in content. Something in the build system must
be wrong. This can lead to architecture-specific FTBFSes in pak‐
kages depending on librtmidi-dev.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.7.0-2-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages librtmidi-dev depends on:
pn  libasound2-dev  <none>
pn  libjack-dev     <none>
pn  librtaudio-dev  <none>
pn  librtmidi3      <none>
ii  librtmidi4      3.0.0~ds1-2+b1
pn  librtmidi5      <none>

librtmidi-dev recommends no packages.

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

--- End Message ---
--- Begin Message ---
On 2020-08-28 22:14:49 +0000, Thorsten Glaser wrote:
> Sebastian Ramacher dixit:
> 
> >That looks like the expected difference between the amd64 and arm64
> >packages. So what issues are you seeing?
> 
> Oh, interesting. I was using p.d.o to search for RtMidi.h
> and found this divergence in the file lists on p.d.o…
> 
> >> https://packages.debian.org/sid/amd64/librtmidi-dev/filelist
> >> https://packages.debian.org/sid/arm64/librtmidi-dev/filelist
> 
> I admit I didn’t download the packages and look for myself,
> trusting the p.d.o data to be, if possibly up to 36 hours out
> of date, at least accurate.

So nothing to fix here

Cheers
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply to: