You are not logged in.
I had a read through some example debbuild files from you and find them a big step forward compared to the native deb packaging files. So from that point of view easydeb looks like a great improvement to me, thanks for making this tool available.
But I still have the following question:
It takes recipes and builds deb packages.
Does easydeb build the packages in a clean chroot environment (like 'mock' does for RPM based distros) or simply with the environment of the user launching it?
Last edited by tux_99 (2025-11-15 19:56:59)
Online
When installing the deb package from your git repo I get the following error:
Unpacking easydeb-git (0.5.1.r0.g053bbf3) ...
Setting up libarchive-tools (3.7.4-4) ...
Setting up gawk (1:5.2.1-2+b1) ...
Setting up easydeb-git (0.5.1.r0.g053bbf3) ...
Compiling '/usr/share/easydeb/dependencies/missing_apt_dependencies.py'...
ln: failed to create symbolic link '/etc/firejail/easydeb.profile': No such file or directory
dpkg: error processing package easydeb-git (--configure):
installed easydeb-git package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for libc-bin (2.41-12) ...
Errors were encountered while processing:
easydeb-git
Notice: Download is performed unsandboxed as root as file '/home/user/Downloads/easydeb-git_0.5.1.r0.g053bbf3_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
What "Download" does the Notice in the end refer to?
I had downloaded the package manually and then run apt install /home/user/Downloads/easydeb-git_0.5.1.r0.g053bbf3_all.deb as root (su - ) to install it.
Last edited by tux_99 (2025-11-15 21:04:12)
Online
This addition is a bit off-topic but possibly historically relevant/interesting, especially to the younger generation who might be unaware of its existence over 25 years ago. I have used this method several times over the years and it never failed me:
HowTo Build a Package from Source the Smart Way (from Soul Singin')
https://forums.debian.net/viewtopic.php?f=16&t=38976
My package building days are long over but I am wondering if reinventing the wheel is just a face-lift or something completely different.
Online
@golinux thanks for that link, it's a well written guide and there is certainly some interesting info but all those methods described are geared towards someone who just wants to install some not already packaged software on his on PC, not to produce redistributable packages.
If easydeb does a clean chroot build as I hope it does then for me that's far more useful than the methods described in your link.
Last edited by tux_99 (2025-11-15 21:20:38)
Online
Many thanks for the clarification tux_99. ![]()
Online
Hi there!
I am regularily building audio packages for Devuan/Debian.
At least when using the "cmake" routine this command works fine in creating deb-packages for Devuan/Debian:
sudo checkinstall -D cmake --build '/home/user/path/build' --target installGreetings, Michael
Ad aspera ad astra
Offline
@tux_99
No automatic chroot. You'll need to launch that your self, it should work just fine. The design strategy is unix/kiss (specialized and simple). For personal use it's fine like that. Even debian building tools don't automatically use a chroot. You can use it for sloppy personal packages and for high quality packages. You could also use distrobox or anything else of the sort.
ln: failed to create symbolic link '/etc/firejail/easydeb.profile': No such file or directory
buuuug, you don't have firejail installed. Speak of the devil, yes, i'm not using a chroot. tmp fix, install firejail (it's a sandboxing tool). The error, is that it's trying to symlink the firejail profile in the firejail folder that doesn't exist, so that you can use it if you want. You don't have to use firejail, this is why it's not in the dependencies, it's totally optional. I flagged it as prerelease for a reason.
the other is apt specific. I'm guessing because you used full path, it thinks it's doing a download as root. With sudo/doas and ./package i never get this.
@golinux @Babarosa
The strategy of the project is a AUR for debs. It's not "just" a new packaging format for dummies. There's all the arcane stuff you need to do to package stuff. Where you download from, dependencies, commands, patches..... Some stuff are especially badly behaved and you need to straiten them up. Now, every user must redo everything from scratch and hunt down the solution like a windows user. With a deb AUR this stuff can be greatly reduced. You are supposed to share your DEBBUILDs.
Offline
fixed the bug, new release: https://gitea.com/easydeb/easydeb/relea … 4d_all.deb
Offline
fixed the bug, new release:
Thanks, I can confirm the error is gone.
BTW, do I understand this right that I could simply take a pkgbuild file from Arch AUR, rename it to debbuild and adapt the dependencies if necessary and then build it on devuan?
In other words, is the file format specification of the debbuild files 100% compatible with the pkgbuild file format?
Online