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

Bug#990737: Audacity's new privacy policy may need to be addressed



Title: -

Package: audacity
Severity: important
Tags: upstream

Not yet in the archive I don't think, but flagging this here:

https://www.audacityteam.org/about/desktop-privacy-notice/

This may need addressing in the Debian packaging, i.e. in addition to ensuring that the data collection is off by default, maybe the whole tracking code needs to be removed?

-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages audacity depends on:
ii audacity-data 2.4.2~dfsg0-4
ii libavcodec58 7:4.3.2-0+deb11u1
ii libavformat58 7:4.3.2-0+deb11u1
ii libavutil56 7:4.3.2-0+deb11u1
ii libc6 2.31-12
ii libexpat1 2.2.10-2
ii libflac++6v5 1.3.3-2
ii libflac8 1.3.3-2
ii libgcc-s1 10.2.1-6
ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii libglib2.0-0 2.66.8-1
ii libgtk-3-0 3.24.24-4
ii libid3tag0 0.15.1b-14
ii liblilv-0-0 0.24.12-2
ii libmad0 0.15.1b-10
ii libogg0 1.3.4-0.1
ii libportaudio2 19.6.0-1.1
ii libportsmf0 0.1~svn20101010-5
ii libsndfile1 1.0.31-1
ii libsoundtouch1 2.2+ds1-2
ii libsoxr0 0.1.3-4
ii libstdc++6 10.2.1-6
ii libsuil-0-0 0.10.10-1
ii libtwolame0 0.4.0-2
ii libvamp-hostsdk3v5 2.10.0-1
ii libvorbis0a 1.3.7-1
ii libvorbisenc2 1.3.7-1
ii libvorbisfile3 1.3.7-1
ii libwxbase3.0-0v5 3.0.5.1+dfsg-2
ii libwxgtk3.0-gtk3-0v5 3.0.5.1+dfsg-2

audacity recommends no packages.

Versions of packages audacity suggests:
pn ladspa-plugin <none>

-- no debconf information

--

.''`. martin f. krafft <> @martinkrafft

:' : proud Debian developer

.'http://people.debian.org/~madduck- Debian - when you have better things to do than fixing systems


Reply to: