Bug#1028589: ITP: telephony-service -- Telephony service components for Lomiri
Am 13. Jänner 2023 11:44:56 MEZ schrieb Mike Gabriel : >Package: wnpp >Severity: wishlist >Owner: Mike Gabriel >X-Debbugs-Cc: debian-de...@lists.debian.org > >* Package name: telephony-service > Version : 0.5 > Upstream Author : UBports developers >* URL : >https://gitlab.com/ubnports/development/core/telephony-service/ >* License : GPL-3, CC-BY-SA-3.0 > Programming Lang: C++ > Description : Telephony service components for Lomiri > > This package will provide the telephony dispatcher daemon for Lomiri's > Dialer App and Messaging App and its client API. Just a suggestion: would it make sense, to prefix the ubports packages with a common prefix like ubports- ? "telephony-service" is a rather generic name, and I don't think it ought to be "owned" by any specific provider. So yeah: I guess I'm suggesting to even prefix the source packages mfh.her.fsr IOhannes
Bug#1016011: ITP: pd-mapper -- Qualcomm PD mapper service
Am 25. Juli 2022 11:01:03 MESZ schrieb Arnaud Ferraris : >Package: wnpp >Severity: wishlist >Owner: Arnaud Ferraris >X-Debbugs-Cc: debian-de...@lists.debian.org, aferra...@debian.org > >* Package name: pd-mapper > Version : 0.0+git20220208 > Upstream Author : Bjorn Andersson >* URL : https://github.com/andersson/pd-mapper >* License : BSD > Programming Lang: C > Description : Qualcomm PD mapper service > >'pd-mapper' is the reference implementation for Qualcomm's Protection >Domain mapper service. It is required for userspace applications to >access the various remote processors (Wi-Fi, modem, sensors...) on >recent Qualcomm SoCs using the QRTR protocol. Just to note: AFAIK all Debian packages that currently use the "pd-" prefix belong to the "pure-data" universe, just like Python packages have a "python-" prefix. There is no formal "reservation" of that namespace, but I would expect quite some confusion if there are a few totally unrelated packages using the same naming scheme. There's even an exusting pd-mapping package So I humbly suggest to pick a name that reduces confusion, if possible. mfh.her.fsr IOhannes mfh.her.fsr IOhannes
Bug#1007814: ITP: spek -- acoustic spectrum analyser
I'm on my mobile phone, and autocorrection has struck again. Instead of "'Spain" I meant of course "spek". mfg.gss.owh IOhannes
Bug#1007814: ITP: spek -- acoustic spectrum analyser
You might want to consider maintaining 'Spain under the umbrella of the multimedia team (and I might be interested in sponsoring) mfh.her.fsr IOhannes
Bug#795901: ITP: pd-iem -- collection of general purpose objects for Pure Data
Control: retitle -1 ITP: pd-iemutils -- collection of general purpose
objects for Pure Data
thanks.
On Mon, 17 Aug 2015 21:14:20 +0200 IOhannes m zmoelnig
wrote:
> Package: wnpp
> Severity: wishlist
> Owner: IOhannes m zmoelnig
>
> * Package name: pd-iem
> Version : 1.20
> Upstream Author : Institute of Electronic Music and Acoustics (iem)
> * URL : http://iem.at/
> * License : GPL
> Programming Lang: C, Pd
> Description : collection of general purpose objects for Pure Data
>
> pd-iem consists of a number of independent submodules
> - iem_adaptfilt (adaptive filters)
> - iem_delay (optimized delay lines)
> - iem_roomsim (room simluation)
> - iem_spec2 (optimized frequency domain processing)
there are various "iem"-prefixed libraries (some of them not included in
this package), so we convinced upstream to use a better name ("iem_utils").
gmasdr
IOhannes
signature.asc
Description: OpenPGP digital signature
Bug#729203: [FFmpeg-devel] Reintroducing FFmpeg to Debian
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 (resending, to keep debian-devel and the bug-report in the loop) personally i would welcome if both libav and ffmpeg could co-exist within Debian¹. as i see it, libav and ffmpeg have diverged, and as such i would like to have the choice which one to use. On 2014-07-28 11:55, Marco d'Itri wrote: > On Jul 28, Alessio Treglia wrote: > >> Personally I don't feel like dropping libav in favor of ffmpeg >> now at this stage. + 1 i don't think that dropping libav is appropriate at all. > Except that, for a lot of the depending packages, there would be > an immediate benefit in the number of bugs fixed. at least in theory. > Personally I feel that we have inflicted libav on our users for > way more time than it was sensible to do. i would appreciate it, if you (and anybody else) used a less flammable &| touchy language. fgmadr IOhannes ¹ but then i'm not a member of the security team :-) -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJT1jRXAAoJELZQGcR/ejb45GYP/2a06m3B6PRGyjV6oGS1xwDg 0if/Lssn500F8yjrYFKnexKGZg6xncKVKJ+NJncX3pIWMKu/fOXKJusC5Z5eMdvg Ecruo7sXBojUnUxtaibGExkjdCWHv4wC/xwx/gQVUg3ijQGr5CQgZKXRPzf6dAG5 Sc4KS7w1SBtgLWaKvsOVhljSB39lye1cUk8vgkPkvSytJPiFMo1QSCDlbNz5JGbf 4c8viga5W9KCH5zMLzZTRQOkiPQpZMPsd/l220YX6ADwlBhnG/yRFBx7SBOnVDYb BIWb4MFrsCikzC5gJrJZdVAkB96AWOWR6J8N0s8LI2Y1ZwOIM4nJB1FNeQvFRaJI xe5p3dTI5DS7Kvc6i4LjKcO5m1EdZXeS1vV/OMDrLtgpfDC7pfhn3lImaYMPGCpA 60GNGo/PnbUMWGT3Z5JCeX/Q59X53d8DrW7gTcrQoSr6y0DN8AFEpcuDCYbd2ubt /A+0MeocRPNKGiNB7lEfvpSD3x3e4pGlSFB1AMgnwCGmpXzHeA51LzbDJGtfdWon x8L7OD5QD/LwRqQtAncRpf9jB56oJvktmznluSuCcJeY9ADSYH2YDPC1g3CCnuKG SOJpSClZrPjlc2511emDcnOaMJhkyjeQ8R+I67+I05r0jBdk2FDnFASsNVVcRV5o lzO+UTdVUs0nWsiDa+CX =PGZV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53d6345a.6050...@debian.org
Bug#748293: O: frei0r
Control: retitle -1 ITA: frei0r thanks pkg-multimedia has promised to adopt frei0r a long time ago. let's do it! (and move the package from experimental to unstable) fgmards IOhannes signature.asc Description: OpenPGP digital signature
Bug#615055: ITP: assimp -- Open Asset Import Library
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/26/2011 09:26 AM, Ralf Treinen wrote: > It is customary not to mention in the description of the package that it > is open source, since eveything in debian is. true enough, i will keep that in mind for future ITPs and the package description once the packaging is done. fgmadr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1pF1QACgkQkX2Xpv6ydvSuYwCg1qjsC7xHd3983P8YtIUE7f2O W1sAnRPkkqRxWLozTVY/1E20EXcnjmRf =dyfs -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d691754.3060...@iem.at
Bug#610164: ITP: gmerlin-encoders -- encoder plugins for Gmerlin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/16/2011 11:35 AM, Christian Marillat wrote: > IOhannes m zmoelnig writes: > >> Package: wnpp >> Severity: wishlist >> Owner: IOhannes m zmoelnig >> >> . >> This package includes a number of encoders to be used by Gmerlin > > Do you intent to package encoders who are not allowed in Debian (lame, > faac, etc...) ? > no. the packages are intended for proper Debian inclusion. the question is, whether we could find a solution to include the non-free parts via debian-multimedia, e.g. by producing a number of binary packages, e.g. gmerlin-encoders-speex (debian) and gmerlin-encoders-faac (d-m) how does this sound to you? fgmasdr IOhannes PS: i'm part of pkg-multimedia-maintainers, and we are currently trying to get gmerlin/gmerlin-avdecoders/gmerlin-encoders into debian. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0zUKoACgkQkX2Xpv6ydvQhNwCbBANFulwQhQGXRWxJ0iiN07uW S6IAn3GqtcgHSovlflrLYf70cdS4X/58 =P/C8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d3350aa.5040...@iem.at
Bug#598354: ITP: gstreamer0.10-v4l2loopback -- GStreamer sink to write into v4l2 loopback devices
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/29/2010 03:16 PM, Sebastian Dröge wrote: >> on the long run, i would prefer if v4l2sink could write to the loopback >> device as well. > > Well, instead of writing something new wouldn't it be better to fix > v4lsink instead? :) I'd be happy to review patches and commit them > upstream :P it turned out that i could fix the v4l2loopback kernel module so that it is now supported by v4l2sink. since this obsoletes the v4l2loopback gst-element, i guess one could close this ITP. should i do that? > But IIRC v4l2sink only expects the v4l2 device to list all supported > formats and then can use any of these formats. Also IIRC it was written > by someone who wanted to use it for a loopback device so it actually > worked at some point ;) this doesn't really mean anything. the v4l2sink assumes certain capabilities of the sink device which were obviously present on the device the upstream author was using, though there could be (and are) other perfectly legal devices that don't have this capabilities. famsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkywY3oACgkQkX2Xpv6ydvRargCcDOKKCNoIMe9IcOPAXoj008ys xKgAn0ck2LmzB3NVLt2epz+rWA8bSMFE =cyxR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cb0637a.2030...@iem.at
