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

Bug#860084: marked as done (RFP: libxdf -- static C++ library for loading XDF (multi-channel stream format) files)



Your message dated Sat, 19 Jan 2019 06:48:27 +0000
with message-id <20190119064827.g4jopq5diwuriet2@master.debian.org>
and subject line RFP: libxdf
has caused the Debian Bug report #860084,
regarding RFP: libxdf -- static C++ library for loading XDF (multi-channel stream format) files
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.)


-- 
860084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860084
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Michael Hanke <mih@debian.org>

* Package name    : libxdf
  Version         : 0.93
  Upstream Author : Yida Lin (?)
* URL             : https://github.com/Yida-Lin/libxdf
* License         : GPL3
  Programming Lang: C++
  Description     : static C++ library for loading XDF (multi-channel stream format) files


Libxdf is a cross-platform C++ library for loading multimodal,
multi-rate signals stored in XDF files. Libxdf is a core component of
bio-signal viewing application SigViewer. It can also be integrated into
other C++ applications.

The last release is just a few days old.

This is a new dependency of the sigviewer package that needs an update
to version 0.6 (#860083)

This package will be maintained by the NeuroDebian team.

At the moment upstream does not support building a shared library.

--- End Message ---
--- Begin Message ---
already in debian
https://packages.qa.debian.org/libx/libxdf.html

--- End Message ---

Reply to: