You are not logged in.
If you do not want learn yourself, you can only hope that others may learn how to rebuild packages. Otherwise, it might be nothing to install.
$ apt changelog android-sdk-platform-23 | cat
Get:1 store: android-framework-23 6.0.1+r72-6 Changelog
android-framework-23 (6.0.1+r72-6) unstable; urgency=medium
* source-only upload
-- Hans-Christoph Steiner <hans@eds.org> Thu, 31 Dec 2020 12:49:26 +0100
android-framework-23 (6.0.1+r72-5) unstable; urgency=medium
* Fix FTBFS with Java 9+ (Closes: #894285)
* add basic autopkgtest to check that class files are in the JAR
-- Hans-Christoph Steiner <hans@eds.org> Wed, 06 Mar 2019 12:10:58 +0000
android-framework-23 (6.0.1+r72-4) unstable; urgency=medium
* Team upload.
* Fix FTBFS (Closes: #891548)
* Add Apache NOTICE file
* Use debhelper 11
* Bump Standards-Version to 4.1.3
-- tony mancill <tmancill@debian.org> Sat, 10 Mar 2018 12:32:30 -0800
android-framework-23 (6.0.1+r72-3) unstable; urgency=medium
* Build-Depends on gradle-debian-helper (>= 1.4~) for backport friendly
* Build shrinkedAndroid.jar
* Build-Depends on proguard
-- Kai-Chung Yan <seamlikok@gmail.com> Fri, 09 Dec 2016 21:14:29 +0800
android-framework-23 (6.0.1+r72-2) unstable; urgency=medium
* d/build.gradle:
* Declare :uiautomator:stubs dependsOn :android:jar, fixing FTBFS
* Add -api & -removedApi options to Doclava
* Update the usage of gradle-debian-helper
* d/rules: Update the usage of maven-debian-helper
-- Kai-Chung Yan <seamlikok@gmail.com> Fri, 25 Nov 2016 13:55:33 +0800
android-framework-23 (6.0.1+r72-1) unstable; urgency=medium
* Initial release. (Closes: #833458)
-- Kai-Chung Yan <seamlikok@gmail.com> Fri, 07 Oct 2016 19:11:58 +0800
There is an official Ubuntu repository with native Debian sources and native Debian packages which work with Devuan. If some of them are needed to build Devuan packages, why not import them to the Devuan repository?
This means that you have to learn how to rebuild packages.
But you cannot learn this, if it is impossible to compile.
On the other hand, if the users do not want to learn anything, the "under-staffed and over-worked Devuan crew" may have more work to do.
Have you already installed android-sdk-platform-23 and rebuilt scrcpy for Devuan?
The name of a Debian package is determined by its changelog.
If you want to change the name, you can add certain lines to the changelog, or edit it.
$ apt changelog scrcpy | cat
Get:1 store: scrcpy 1.25-1 Changelog
scrcpy (1.25-1) unstable; urgency=medium
* New upstream release
* Bump Standards-Version to 4.6.2
-- Yangfl <mmyangfl@gmail.com> Fri, 20 Jan 2023 18:28:52 +0800
scrcpy (1.24-1) unstable; urgency=medium
* New upstream release
* FTBFS if BUILD_DIR is set (Closes: #1013304)
* Bump Standards-Version to 4.6.1
-- Yangfl <mmyangfl@gmail.com> Sat, 16 Jul 2022 17:47:57 +0800
scrcpy (1.23-1) unstable; urgency=medium
* New upstream release
* scrcpy now require scrcpy-server of the same version (Closes: #1004201)
* Fix FTBFS with ffmpeg 5.0 (Closes: #1004812)
-- Yangfl <mmyangfl@gmail.com> Wed, 09 Mar 2022 16:37:46 +0800
scrcpy (1.21-1) unstable; urgency=medium
* New upstream release
-- Yangfl <mmyangfl@gmail.com> Wed, 01 Dec 2021 04:36:41 +0800
scrcpy (1.19-1) unstable; urgency=medium
* New upstream release (Closes: #995295)
* Bump Standards-Version to 4.6.0
-- Yangfl <mmyangfl@gmail.com> Thu, 30 Sep 2021 11:25:13 +0800
scrcpy (1.17-1) unstable; urgency=medium
* New upstream release
-- Yangfl <mmyangfl@gmail.com> Mon, 18 Jan 2021 16:40:22 +0800
scrcpy (1.14-1) unstable; urgency=medium
* New upstream release
* Bump Standards-Version to 4.5.0
* Bump debhelper compat to 13
-- Yangfl <mmyangfl@gmail.com> Wed, 01 Jul 2020 14:59:53 +0800
scrcpy (1.12.1+ds-1) unstable; urgency=medium
* New upstream release (Closes: #947465)
* Recommend but not depend on adb
* Add upstream metadata
-- Yangfl <mmyangfl@gmail.com> Tue, 14 Jan 2020 13:14:59 +0800
scrcpy (1.11+ds-1) unstable; urgency=medium
* Initial release (Closes: #893279)
-- Yangfl <mmyangfl@gmail.com> Wed, 20 Nov 2019 23:40:21 +0800
Fetched 1,678 B in 0s (0 B/s)
What is interesting, android-sdk-platform-23 is also available in the same Ubuntu repository. It was also installed on Devuan 5 Daedalus without any problems:
$ sudo dpkg -i libandroid-23-java_6.0.1+r72-6_all.deb libandroid-uiautomator-23-java_6.0.1+r72-6_all.deb android-sdk-platform-23_6.0.1+r72-6_all.deb
(Reading database ... 399860 files and directories currently installed.)
Preparing to unpack libandroid-23-java_6.0.1+r72-6_all.deb ...
Unpacking libandroid-23-java (6.0.1+r72-6) over (6.0.1+r72-6) ...
Selecting previously unselected package libandroid-uiautomator-23-java.
Preparing to unpack libandroid-uiautomator-23-java_6.0.1+r72-6_all.deb ...
Unpacking libandroid-uiautomator-23-java (6.0.1+r72-6) ...
Preparing to unpack android-sdk-platform-23_6.0.1+r72-6_all.deb ...
Unpacking android-sdk-platform-23 (6.0.1+r72-6) over (6.0.1+r72-6) ...
Setting up libandroid-23-java (6.0.1+r72-6) ...
Setting up libandroid-uiautomator-23-java (6.0.1+r72-6) ...
Setting up android-sdk-platform-23 (6.0.1+r72-6) ...
android-sdk-platform-23
_http://us.archive.ubuntu.com/ubuntu/pool/universe/a/android-framework-23/android-sdk-platform-23_6.0.1+r72-6_all.deb
libandroid-23-java
_http://us.archive.ubuntu.com/ubuntu/pool/universe/a/android-framework-23/libandroid-23-java_6.0.1+r72-6_all.deb
libandroid-uiautomator-23-java
_http://us.archive.ubuntu.com/ubuntu/pool/universe/a/android-framework-23/libandroid-uiautomator-23-java_6.0.1+r72-6_all.deb
As the names suggest, all these debs are native Debian packages, which were somehow appropriated by Ubuntu.
The native Ubuntu packages look like this:
android-sdk-platform-23_6.0.1+r72-6ubuntu1_all.deb
android-sdk-platform-23 is needed to compile scrcpy on Devuan 5 Daedalus (see above).
The source is android-framework-23
android-framework-23_6.0.1+r72.orig.tar.xz 2016-11-11
android-framework-23_6.0.1+r72-6.debian.tar.xz 2021-01-02
android-framework-23_6.0.1+r72-6.dsc 2021-01-02
It is 100% Debian source without Ubuntu patches.
It is available in the same Ubuntu repository:
_http://us.archive.ubuntu.com/ubuntu/pool/universe/a/android-framework-23/android-framework-23_6.0.1+r72.orig.tar.xz
_http://us.archive.ubuntu.com/ubuntu/pool/universe/a/android-framework-23/android-framework-23_6.0.1+r72-6.debian.tar.xz
_http://us.archive.ubuntu.com/ubuntu/pool/universe/a/android-framework-23/android-framework-23_6.0.1+r72-6.dsc
$ cat /var/lib/dpkg/status | grep android-sdk-platform-23 -B11
Package: android-sdk
Suggests: android-sdk-platform-23, maven, proguard-gui
Why isn't android-sdk-platform-23 available in the Devuan 5 Daedalus repository?
I installed them both (see may previous post) with command
sudo dpkg -i scrcpy_1.25-1_amd64.deb scrcpy-server_1.25-1_all.deb
scrcpy-server_1.25-1_all.deb
_http://us.archive.ubuntu.com/ubuntu/pool/universe/s/scrcpy/scrcpy-server_1.25-1_all.deb
How to Install Scrcpy [Screen Copy] on Ubuntu 22.04 Jammy Jellyfish | ADB Scrcpy [Debugging Bridge]
_https://www.youtube.com/watch?v=is-ASr4n45g
Scrcpy 2.0 is out! How to Install & Use this Android Remote Control App
_https://ubuntuhandbook.org/index.php/2023/03/scrcpy-2-0-install-android-remote-control/
EVERYTHING WAS INSTALLED, but I do not have an Android device to test it.
Ubuntu package scrcpy_1.25-1_amd64.deb libavformat59 (>= 7:5.0)
Devuan:
$ apt show libavformat59
Package: libavformat59
Version: 7:5.1.5-0+deb12u1
_http://us.archive.ubuntu.com/ubuntu/pool/universe/s/scrcpy/
_http://us.archive.ubuntu.com/ubuntu/pool/universe/s/scrcpy/scrcpy_1.25-1_amd64.deb
$ dpkg-deb --info scrcpy_1.25-1_amd64.deb
new Debian package, version 2.0.
size 75486 bytes: control archive=949 bytes.
740 bytes, 16 lines control
707 bytes, 10 lines md5sums
Package: scrcpy
Version: 1.25-1
Architecture: amd64
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Yangfl <mmyangfl@gmail.com>
Installed-Size: 198
Depends: libavcodec59 (>= 7:5.0), libavdevice59 (>= 7:5.0), libavformat59 (>= 7:5.0), libavutil57 (>= 7:5.0), libc6 (>= 2.34), libsdl2-2.0-0 (>= 2.0.12), libusb-1.0-0 (>= 2:1.0.16), scrcpy-server (= 1.25-1)
Recommends: adb
Section: net
Priority: optional
Homepage: https://github.com/Genymobile/scrcpy
Description: Display and control your Android device
This application provides display and control of Android devices connected on
USB (or over TCP/IP). It does not require any root access.
.
This package contains the client (desktop) binary.
scrcpy-server_1.25-1_all.deb
_http://us.archive.ubuntu.com/ubuntu/pool/universe/s/scrcpy/scrcpy-server_1.25-1_all.deb
It was installed without problems:
$ sudo dpkg -i scrcpy_1.25-1_amd64.deb scrcpy-server_1.25-1_all.deb
(Reading database ... 391780 files and directories currently installed.)
Preparing to unpack scrcpy_1.25-1_amd64.deb ...
Unpacking scrcpy (1.25-1) over (1.25-1) ...
Selecting previously unselected package scrcpy-server.
Preparing to unpack scrcpy-server_1.25-1_all.deb ...
Unpacking scrcpy-server (1.25-1) ...
Setting up scrcpy-server (1.25-1) ...
Setting up scrcpy (1.25-1) ...
Processing triggers for bamfdaemon (0.5.6+repack-1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mate-menus (1.26.0-3) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.11.2-2) ...
$ whereis scrcpy
scrcpy: /usr/bin/scrcpy /usr/share/scrcpy /usr/share/man/man1/scrcpy.1.gz
$ scrcpy
scrcpy 1.25 <https://github.com/Genymobile/scrcpy>
* daemon not running; starting now at tcp:5037
* daemon started successfully
ERROR: Could not find any ADB device
ERROR: Server connection failed
I do not have any Android.
The "unstable" source failed
dpkg-checkbuilddeps: error: Unmet build dependencies: android-sdk-platform-23
$ dpkg-buildpackage -us -uc -b
dpkg-buildpackage: info: source package scrcpy
dpkg-buildpackage: info: source version 1.25-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Yangfl <mmyangfl@gmail.com>
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build .
dpkg-checkbuilddeps: error: Unmet build dependencies: android-sdk-platform-23
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
EDIT:
Debian sources need "android-sdk-platform-23" to be compiled.
But it seems that it is not available for Debian 12 Bookworm and Devuan 5 Daedalus.
This is the problem.
Thank you for the link!
It has links to old and new sources.
I will try to compile this:
_https://packages.debian.org/source/unstable/scrcpy
Download scrcpy
scrcpy_1.25-1.dsc
scrcpy_1.25.orig.tar.gz
scrcpy_1.25-1.debian.tar.xz
But I do have any sort of Android.
In the Chimaera repo, there might be the same source as in Debian
Debian:
_https://packages.debian.org/bullseye/scrcpyDownload Source Package scrcpy:
[scrcpy_1.17-1.dsc]
[scrcpy_1.17.orig.tar.gz]
[scrcpy_1.17-1.debian.tar.xz]
These three packages are needed. They provide the original source code, Debian patches, etc.
The Chimaera repo is likely to have these 3 packages and, perhaps, a package with Devuan patches.
Patches will automatically be applied, when you run "dpkg-source -x *.dsc"
How to get source code of package using the apt command on Debian or Ubuntu
_https://www.cyberciti.biz/faq/how-to-get-source-code-of-package-using-the-apt-command-on-debian-or-ubuntu/
1. enable the source repo
2. download the source with apt-get
apt-get source scrcpy
apt-get will download the source packages, unpack the source, and apply the patches.
3. disable the source repo
4. install build dependencies with mk-build-deps
5. build the package
Debian wiki: Get the build dependencies
_https://wiki.debian.org/BuildingAPackage#Get_the_build_dependencies
equivs
_https://wiki.debian.org/Packaging/HackingDependencies
@ralph.ronnquist
Perhaps, the simplest way is to download the source code (tars + dsc) manually from the Chimaera repository. This will not cause any "conflics".
Could you provide the link?
There is also a simple trick. Sometimes, it helps, but not always.
You can unpack a deb package with a special command.
Remove the unwanted dependencies from the list of dependencies.
Then pack it again, and install the deb.
This does not mean that the app will work, but this does not break dependencies.
If it does not work, you can simply remove the package
sudo apt remove <name of the package>
But this trick may cause troubles, if it about some important system libs (it may overwrite symlinks, etc.).
Debian wiki: Get the build dependencies
_https://wiki.debian.org/BuildingAPackage#Get_the_build_dependencies
_https://wiki.gbe0.com/linux/Debian/rebuild-package-from-source
Perhaps, you may better try to rebuild. This sort of practical knowledge may liberate from frustration.
If deb packages from the net break dependencies, you may try to fix them with "sudo apt install -f"
You may try to rebuild the package for your Devuan.
sudo apt-get install build-essential debhelper devscripts
apt show devscripts
1. Download the Debian source code (tars, dsc) manually.
You may also try sources from Ubuntu, or Ubuntu PPA.
For example, to rebuild wxMaxima for Devuan5, I used this source:
_https://launchpad.net/ubuntu/+source/wxmaxima/24.02.1-1build2
2. Extract the source code
dpkg-source -x *.dsc
3. cd to the source code directory
4. Install build dependencies
sudo mk-build-deps -i
5. Build the package
dpkg-buildpackage -us -uc -b
EDIT:
To avoid troubles, you may check build dependencies before installing them
$ mk-build-deps --help | grep "Build-Depends dependencies" -B2
-B, --build-dep
Generate a package which only depends on the source package's
Build-Depends dependencies.
dpkg-deb --info *.deb
You may also check dependencies before installing the package.
I asked you to post information that I had repeatedly posted myself for my system.
I hope that I am mistaken, but it looks like you are simulating "problems with ALSA", in order to convince people to use pulseaudio.
Actually, I am very happy that Debian devs managed to compile maxima which works.
It seems that it was a real problem. Without maxima, wxMaxima is useless.
$ maxima
Maxima 5.46.0 https://maxima.sourceforge.io
using Lisp GNU Common Lisp (GCL) GCL 2.6.14 git tag Version_2_6_15pre3
Debian devs used a certain version Common Lisp from git. It works.
Fedora devs used another Lisp, not Common Lisp. The result is "segmentation fault".
On Fedora, you open wxMaxima, type a command, execute it, and wxMaxima does not react.
The Fedora users cannot understand what is going on.
You can compile the same version of wxMaxima on Devuan. It works, because maxima works.
It seems that flatpak is a sort of simple solution to all problems, a sort of cargo cult ritual, perhaps.
Firefox is playing video in youtube:
$ firefox 2>&1
[Child 3342, MediaDecoderStateMachine #1] WARNING: 7fa31a74d4c0 Could not set cubeb stream name.: file ./dom/media/AudioStream.cpp:321
Input: 44100 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 1764
Output: 48000 Hz, 2 ch, 's16_le' (0x2): dummy = 0, period = 1920
Rates: 44100 --> 48000 (J: 0.00%, T: FFT, W: Vorbis)
Ok.
FFT is the fftrate resampler. It is GPL3, the source code is here:
_https://github.com/PetrovSE/fftrate
$ fuser -av $(find /dev/snd -type c 2>/dev/null)
USER PID ACCESS COMMAND
/dev/snd/controlC0: igor 2229 F.... mate-settings-d
igor 2324 F.... mate-volume-con
/dev/snd/pcmC0D0c:
/dev/snd/pcmC0D0p: igor 3175 F...m firefox-esr
/dev/snd/seq:
/dev/snd/timer: igor 3175 f.... firefox-esr
It works without apulse, and it works with apulse as well
$ apulse firefox 2>&1
Input: 48000 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 1920
Output: 48000 Hz, 2 ch, 's16_le' (0x2): dummy = 0, period = 1920
Rates: 48000 --> 48000 (J: 0.00%, T: None, W: Planar)
Ok.
Notice that the resampler is not active (T: None).
It seems that it makes sense to run browsers with apulse.
It helps to improve sound quality with Min, Brave, Chromium and Chrome.
It might be a bug in ALSA backend.
The same video with Chromium:
$ apulse chromium 2>&1
Input: 44100 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 1764
Output: 48000 Hz, 2 ch, 's16_le' (0x2): dummy = 0, period = 1920
Rates: 44100 --> 48000 (J: 0.00%, T: FFT, W: Vorbis)
Ok.
$ fuser -av $(find /dev/snd -type c 2>/dev/null)
USER PID ACCESS COMMAND
/dev/snd/controlC0: igor 2229 F.... mate-settings-d
igor 2324 F.... mate-volume-con
/dev/snd/pcmC0D0c:
/dev/snd/pcmC0D0p: igor 7968 F...m firefox-esr
igor 8428 F...m chromium
/dev/snd/seq:
/dev/snd/timer: igor 7968 f.... firefox-esr
igor 8428 f.... chromium
If you do not believe my words, why should I believe yours?
It might be very difficult to believe that you really want to configure ALSA.
With pure alsa, the sound was everywhere, except for the browser, which “did not see” the sound system. Either pipewire or jack was required.
If it works with pulseaudio, it does not mean that it cannot work with "pure alsa".
But I can agree that it might be difficult to create a correct ~/.asoundrc
That is why, I am using arateconf.
There is no sound device defined in the FF Daedalus settings.
I also do not have sound devices defined in the Firefox settings (about:support).
And, nevertheless, sound works with "pure alsa".
and nothing runs on Linux except Linux programs
The problem is that Linux programs, which were always working on Linux without any problems, may not work anymore.
For example, on Fedora, both maxima and wxMaxima do not work, and all sorts of maxima's flatpaks also fail.
On Devuan, maxima works, and wxMaxima is so buggy that is impossible to use. But you can compile it yourself.
However, you can install pulseaudio on Mac (if you want) with Homebrew
pulseaudio
Install command:brew install pulseaudio
Sound system for POSIX OSes
_https://formulae.brew.sh/formula/pulseaudio
systemd is not yet available for macOS.
On Devuan Daedalus 5.0, sound works in Firefox out of the box, after the removal of pulseaudio
_https://dev1galaxy.org/viewtopic.php?pid=49837#p49837
The problem might be that you want to use your Audigy2, and it is not the default device.
The simplest solution to such problems is to run
arateconf
and select Audigy2 as "default device".
The manual is here:
ALSA without PulseAudio and PipeWire
_https://dev1galaxy.org/viewtopic.php?id=6644
If you start a new topic, and I will try to help.
NOTE: It is not necessary to remove PulseAudio. You can remove it later, when ALSA is configured and sound works with
apulse firefox
Some useful commands for testing ALSA, you may find here:
_https://dev1galaxy.org/viewtopic.php?pid=50114#p50114
_https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture
Of course, it is very bad manners to remove pulseaudio or pipewire.
The good manners is to use pulseaudio, pipewire, or any other crap, because of loyalty to authorities.
Yes, I am using my method, and it works.
If the goal is to improve sound quality on your computer, you can simply remove pulseaudio and/or pipewire, install Petrov's fftrate plugin, and configure it for 32bit 192kHz (Intel HDA), or other HiRes format, if it is supported by your sound card. For USB headsets, you may try 16bit 48kHz.
If the goal is to improve sound quality on your notebook, my method may work.
What is important is to prevent resampling and format conversion.
Otherwise, you may not know, what you are actually testing.
OK, if you want to make an audio test, you may try something like this.
Take a free sample of 32bit Float DXD
_https://positive-feedback.com/reviews/music-reviews/what-we-hear-with-dxd-32-bit-files/
and downsample it with the fftrate resampler to different audio formats.
For example:
1. DXD to 192kHz 32bit (or 24bit)
2. DXD to 48kHz 16bit
Install Audacious and the fftrate ALSA plugin.
To prevent resampling, configure fftrate to 192kHz.
In Audacious, select ALSA output and set "Bit depth".
Then, you can play 192kHz wave.
Then, you can reconfigure fftrate for 48kHz 16bit format, and play 48kHz 16bit wave.
audacious 2>&1 *.wav
This is closely related topic. But it is still another topic, and we may better discuss it separately (in a new "topic").
The topic is about quality of resampling. It is about quality of digital sound, or, perhaps, more exactly, "digital sound file".
What you want to discuss is the quality of "digital to audio" conversion (DAC).
The final result depends on both, and on the sound system (quality of drivers etc.).
Yes, it is something like this, or even worse.
It has never been like this and now it is exactly the same again.
I am waiting for Steve Gibson to tell the story in details.
EDIT:
Security Now: CrowdStruck
_https://youtu.be/eLkfKizz6NU