The officially official Devuan Forum!

You are not logged in.

#1 Re: Packaging for Devuan » [SOLVED] kicad 7 vs kicad 8. » 2024-03-27 17:41:25

Check the maintainer field when you look at "apt info PACKAGENAME".

Does it mention Devuan? (No, it doesn't.)

If the v8 packages are not backwards compatible, then it's a Debian bug, which you should raise via Debian's bug tracking system.

#2 Devuan » Dependency trees on pkginfo.devuan.org are unstable » 2024-03-21 19:36:03

boughtonp
Replies: 0

I noticed the debtree link for Chimaera and Daedalus packages go to the same page, even when there are differing dependencies.

Looking at the debtree man page, I'm guessing this is a limitation of that software:

man debtree wrote:

If multiple versions of a package are available, the dependency information for the highest available version will be used

Which, given the way pkginfo.devuan.org is setup, suggests that the debtree is always going to represent the newest packages - i.e. whatever is in Ceres/unstable - and checking (e.g.) xserver-xorg-core confirms this to be the case.

I'm assuming that resolving this would be non-trivial, but it should be easy enough to add a suitable clarification to the output generated by the debtree-query.html script?

#3 Re: Off-topic » question regarding hyperbola os » 2024-03-12 20:25:37

Forums truncating URLs is a common annoying anti-feature.

With the (poorly written) FluxBB software this forum uses, it is hard-coded to occur above 55 characters. (The internal forum links are 53 characters, so do not trigger it.)

The auto-linking functionality can be bypassed by deleting the entire protocol, which means also avoiding the truncating functionality, is less ugly than deleting just one letter, and can be either screenshotted or copy-pasted without issue, and without need to manually add h to the start.

It can be done by holding ctrl whilst tapping del twice - compared to deleting a single letter it's a tiny amount of extra work for the author, and removes the need for readers to add a letter.

(Also, if an unlinked URL is the only thing on a line, it can be quickly selected by triple-clicking.)

#4 Re: Installation » [SOLVED] Can't use my Directories » 2024-03-12 19:37:15

> I don't have sha256sum and apt ( or synaptic) can't find it.

/usr/bin/sha256sum is part of coreutils, which is an Essential package in Debian-based distros.

#5 Re: Installation » radicale not starting with init-script » 2024-03-10 00:28:14

There is no radicale package maintainer in Devuan because there is no radicale package in Devuan - Devuan uses the Debian package unmodified.

Devuan only modifies a relatively small number of Debian packages (to remove systemd entanglement - usually when a package has "Depends: systemd"), the majority of packages are unmodified from Debian repositories.

(In addition to searching as you did, you can tell when you have a Devuan-modified package by looking for "devuan" in the Version, and checking for "pool/DEVUAN/" at the start of the filename. The radicale package does not have these, because it comes from Debian.)

So, if Debian's radicale package supplies a sysvinit script (which it appears to here), and you've identified a problem with that script, then the report should go via Debian's bug tracker  (i.e. not direct to Radicale's bug tracker).

#6 Re: Devuan Derivatives » antiX 23.1 "init-diversity" edition » 2024-03-03 12:25:58

bimon wrote:

What do you think about creating a systemd like CLI and service definitions for Devuan with S6 init ?

My idea is to create a wrapper which would automatically translate somehow config files looking like systemd into S6 syntax when any such config file has been changed and its syntax has been linted without an error.

For something similar (unrelated to s6), see sr.ht/~craftyguy/superd

https://sr.ht/~craftyguy/superd/ wrote:

superd is a user service supervisor that is only intended to be used for supervising user services. It makes absolutely no attempt to replace init/pid 1, and should never be used do to that.
...
Service configuration uses systemd's .service files, so that it's low(er) effort to configure services. Many things intended to run as user services already have systemd config written.

#7 Re: Desktop and Multimedia » Using seatd in Chimaera » 2024-02-29 16:21:53

*bump*

https://tracker.debian.org/pkg/seatd wrote:

old-bpo: 0.7.0-6~bpo11+1
stable: 0.7.0-6
testing: 0.8.0-1
unstable: 0.8.0-1

https://pkginfo.devuan.org/seatd wrote:

0.8.0-1+b1 ceres excalibur
0.7.0-6 daedalus
0.5.0-1 chimaera

The Debian seatd source at //sources.debian.org/src/seatd/0.7.0-6~bpo11+1/ indicates the upstream sourcecode repository is //git.devuan.org/devuan/seatd

The list of tags has "debian/0.7.0-6" but no "devuan/anything" since 0.5.0-1 (despite daedalus,ceres,excalibur having newer versions), and also no tag matching the bullseye backport 0.7.0-6~bpo11+1.

So I'm assuming that from 0.5.0-2 onwards both Debian and Devuan have been using the same version, and the only actual difference between seatd_0.7.0-6_amd64.deb and seatd_0.7.0-6~bpo11+1_amd64.deb are different libc versions used when compiling the binaries.

Is there any reason installing seatd_0.7.0-6~bpo11+1_amd64.deb from bullseye-backports repo on a chimaera system will cause issues?

#8 Re: Other Issues » Installing latest xfce4-terminal » 2024-02-29 15:42:33

mobius wrote:

I am unclear as to your suggestion:

Add Devuan Testing repos to existing Devaun installation, or

Install Devuan Testing in VM?

I was suggesting running Devuan Testing in a VM to confirm that the v1.1.1 provides what you want.

I have also yet to properly checkout how backports are created - though the link fsmithred provided probably provides that information (and there looks to be a simpler guide at //wiki.debian.org/SimpleBackportCreation for personal use) - but the first step is confirming there's a suitable version in Debian/Devuan repos, hence why the suggestion to try the version Devuan Testing provides.

#9 Re: Other Issues » Installing latest xfce4-terminal » 2024-02-28 23:39:14

I don't see shortcut preference changes in the v1.1.2 changelog (at //gitlab.xfce.org/apps/xfce4-terminal/-/tags), but v1.1.0 appears to have a bunch of potentially-relevant changes.

Since Devuan Testing has v1.1.1, a sensible first step would be to test that in a VM and see if it does have the desired functionality. If so, looking into what it might take to get that version backported would be worth checking.

#10 Re: Off-topic » Undergarment Brouhaha » 2024-02-28 23:19:15

Why is this nonsense bickering still going on? (That's a question to answer in your own head, not an invitation to prolong it.)

Alex's joke is clearly just that: a joke. It is not an attempt to humiliate anyone. (And if it was such an attempt, there are better ways to deal with that.)

Yes, it's off-topic noise, but they are neither alone in making such posts, nor the worst offender.

If there was a problem, Oui is capable of standing up for themselves and/or reporting it themselves.

(I wouldn't be surprised if the only problem Oui had was annoyance at two thirds of the posts in this thread being completely off-topic.)

#11 Re: Other Issues » Installing latest xfce4-terminal » 2024-02-27 22:24:42

Devuan is an OS for people that want stable well-tested software NOT the latest versions - it is not a rolling source distro (like Artix/Gentoo/Slackware/etc).

Further, trying to install packages from GitHub is liable to cause problems - if one has a good reason to install from source (for a newer version than "apt-get source" will give), the correct location to obtain the source code is either git.devuan.org/devuan or sources.debian.org (depending on whether Devuan has modified that package or not), but again there's no guarantee that compiling newer source will work.

Finally, if gcc is actually installed then the binary will be at /usr/bin/gcc - which is in the path - and if you're not aware of things like that, it's a good sign you need to do more learning before trying to install from source (or that you shouldn't bother because you probably don't need the latest version, or if you really do need it then go with an OS that provides it out of the box, like those mentioned above).

#12 Re: Hardware & System Configuration » merged /usr » 2024-02-27 16:18:39

See //sources.debian.org/src/dpkg/1.22.5/debian/dpkg.postinst/

Presumably the Devuan vendor value is not "debian", and someone needs to do what Kali have done and submit a patch.

#13 Re: Other Issues » tomcat10 on daedalus » 2024-02-25 15:15:10

> the tomcat start script is very complex

No, it's not. It's about 260 lines long, and most of that is boilerplate.

//sources.debian.org/src/orphan-sysvinit-scripts/0.16/scripts/tomcat9/

The difference between running Tomcat 9 and Tomcat 10 is that some previously optional stuff might no longer be optional:

//tomcat.apache.org/tomcat-9.0-doc/setup.html
//tomcat.apache.org/tomcat-10.1-doc/setup.html

That aside, adapting the script may be as simple as search-replace "tomcat9" with "tomcat10".

#14 Documentation » [SOLVED] How to assign apt priority to cdrom repository. » 2024-02-23 15:49:40

boughtonp
Replies: 0

There's plenty of results online on how to change priority of a local repository, but my searches turned up nothing for how to do it regarding packages on a "cdrom" (actually a DVD ISO).

In the end it was relatively simple: identify the origin by checking the policy output, e.g: apt-cache policy | egrep -C1 'origin|cdrom'

# apt-cache policy | egrep -C1 'origin|cdrom'
...
 500 cdrom://[Devuan GNU/Linux 4.0 chimaera amd64 - desktop 20211012] chimaera/main amd64 Packages
     release c=main,b=amd64
     origin Devuan GNU/Linux 4.0 chimaera amd64 - desktop 20211012
...

Then create a file in /etc/apt/preferences.d directory (or edit /etc/apt/preferences file), such as:

Explanation: cdrom
Package: *
Pin: origin "Devuan GNU/Linux 4.0 chimaera amd64 - desktop 20211012"
Pin-Priority: 600

The double quotes are optional, but it must be double or nothing (single quotes do not work).
The Explanation line is a comment, so can contain a brief description of what/why.

See man apt_preferences for filename rules, then jump to "How APT Interprets Priorities" for an explanation of priority numbers.

Note that there's a difference between the origin of a repository, and a package's "Origin" value; (the latter would use Pin: release o=Debian or Pin: release o=Devuan).

#15 Re: Hardware & System Configuration » merged /usr » 2024-02-21 15:33:00

alume wrote:
> Another success in trying to break the logical perfection of the Unix file system?

It was "broken" back in the 1970s, by Ken and Dennis themselves; long before Linus or Ian even touched a computer, or Richard got annoyed with Xerox.

Even though I agree that moving bin, lib and sbin into /usr is not the right solution, it is a minor issue compared to so many other problems.

-
In any case it's good that the Devuan team have made a clear announcement to follow Debian's lead on this and focus efforts on the Devuan project's stated aims.

#16 Re: Installation » [SOLVED» Nvidia and kernel 6.1.0.18 - not good! » 2024-02-14 17:24:45

For anyone wondering about version numbers.
6.1.0-18 = Linux v6.1.76
6.1.0-17 = Linux v6.1.69

There's no new proposed-update listed in the news section of the Package Tracker for Linux

Message #19 on the linked thread suggests it is the driver that has been patched rather than the kernel - and that is supported by the News section on the Package Tracker for nvidia-graphics-drivers-tesla-470 (though I've no idea if that's the correct/only nvidia package in question).

#17 Re: Freedom Hacks » [SOLVED] Want to compile something, but need to revert some stuff, » 2024-02-11 17:00:07

Running git reset revision will change where HEAD is pointed, and - depending on various factors - may or not result in losing history, and may affect the ability to interact with remotes.

Alternatively, git checkout -b branch revision will create a new local branch at that point, allowing one to make changes but not lose history, and retaining the ability to push/pull as normal.

There are a bunch of other potential options depending on precisely what the situation is and what the desired outcome is.

#18 Re: Installation » Installing from src and apt » 2024-02-10 17:21:12

So create a deb package containing the files resulting from compilation, which you install with dpkg --install dummy-package.deb so dpkg knows what files your package owns. (If there are dependencies to resolve, apt install dummy-package.deb would be the appropriate command, but Apt doesn't do actual installation, not do the other frontends, dpkg does.)

There's official tools for creating deb packages that involve hundreds of MB of dependencies, but you basically only need ar (binutils), tar, and a few lines of script to create a deb file.

#19 Re: DIY » Announcement of the OpenMATE desktop environment » 2024-02-06 15:19:49

Microsoft does not respect its users - it treats them as a resource to be spied upon and exploited.

This is true for Microsoft Windows, and it is true for Microsoft GitHub - there have been numerous demonstrations of this for anyone paying attention.

Frankly, I struggle to comprehend how people who otherwise care enough to use Devuan can be ok with GitHub.

-

Codeberg is one of several alternatives, and to see what's good about them one can simply start with looking at the homepage:

codeberg.org wrote:

Codeberg is a collaboration platform providing Git hosting and services for free and open source software, content and projects.

NON-PROFIT
Codeberg is maintained by the non-profit organization Codeberg e.V., based in Berlin, Germany. For us, supporting the commons comes first.
Its future is in the hands of its users. You can help too!

COMMUNITY
We are more than just Git hosting: Our community is comprised of like-minded developers, artists, academics, hobbyists and professionals.
We celebrate free culture, openness and creativity.

RESPECT
No tracking. No third-party cookies. No profiteering. Everything runs on servers that we control. Your data is not for sale.
Hosted in Europe, we welcome the world.

In addition, they have a migration feature to make it easier to migrate existing projects away from GitHub (or GitLab/others), though obviously for a new project one doesn't need to use that.

#20 Re: Desktop and Multimedia » Help needed with StumpWM » 2024-02-03 16:45:37

Debian version numbers are explained in section 5.6.12 of the Debian Policy Manual:

Debian Policy Manual, section 5.6.12 wrote:

The version number of a package. The format is: [epoch:]upstream_version[-debian_revision].

The three components here are:

epoch
    This is a single (generally small) unsigned integer. It may be omitted, in which case zero is assumed.

    Epochs can help when the upstream version numbering scheme changes, but they must be used with care. You should not change the epoch, even in experimental, without getting consensus on debian-devel first.

upstream_version
    This is the main part of the version number. It is usually the version number of the original (“upstream”) package from which the .deb file has been made, if this is applicable. Usually this will be in the same format as that specified by the upstream author(s); however, it may need to be reformatted to fit into the package management system’s format and comparison scheme.

    The comparison behavior of the package management system with respect to the upstream_version is described below. The upstream_version portion of the version number is mandatory.

    The upstream_version must contain only alphanumerics 6 and the characters . + - ~ (full stop, plus, hyphen, tilde) and should start with a digit. If there is no debian_revision then hyphens are not allowed.

debian_revision
    This part of the version number specifies the version of the Debian package based on the upstream version. It must contain only alphanumerics and the characters + . ~ (plus, full stop, tilde) and is compared in the same way as the upstream_version is.

    It is conventional to restart the debian_revision at 1 each time the upstream_version is increased.

    The package management system will break the version number apart at the last hyphen in the string (if there is one) to determine the upstream_version and debian_revision. The absence of a debian_revision is equivalent to a debian_revision of 0.

    Presence of the debian_revision part indicates this package is a non-native package (see Source packages). Absence indicates the package is a native package.

So the version is 22.11, with an epoch of 2 is because the StumpWM developers appear to have a habit of changing versioning convention.

Checking //tracker.debian.org/stumpwm suggests there was no version 1.0.1 in Debian, though following the homepage link shows documentation links for a "v1.0.1-rc" (but also links for both "1.0.0" and "v1.0.0" so not sure what's up there), as well as for "22.11" and others.

If compiling from source, the correct source code to use is the Debian source code, linked from the Debian Package Tracker link above, (and making sure to switch to the branch corresponding to the Debian/Devuan version being used, otherwise there may be dependency issues).

#21 Re: Devuan » Devuan vs Arcolinux » 2024-02-02 18:23:53

Arcolinux is just Arch with stuff pre-installed, including systemd.

Artix is Arch without systemd, and thus is the complement to Devuan (for those who want a rolling Pacman-based distro).

#22 Re: Devuan » Interesting article and post at The Register » 2024-01-29 16:11:10

I kept waiting for the interesting part which that badly written blog article seemed to be building up to, then I found myself at the end. :/

The full comment is interesting - the idea of the US DoD potentially protecting against SystemD over-reach is not something I'd heard before, though my cynical side responds to that with a huge /LOL/ because clearly nothing of the sort will happen.

#23 Re: Other Issues » Incomplete translation into Russian of devuan installation ! » 2024-01-28 16:33:20

The instructions in post #2 appear to refer to the Dev1Galaxy forum.

It's unclear whether the statement in post #1 is referring to the installer or the installed system, and how much this is a Devuan issue or a Debian one, but seems to be it's definitely not referring to this forum.

This Debian page says the Russian translation is 90% complete, and there is a page written in Russian at //wiki.debian.org/ru/L10n/Russian which might be relevant to increasing that percentage.

If the issue is actually Devuan-specific, more details would be required.

#24 Re: Devuan » Praise for the security updates » 2024-01-28 16:12:54

That's a convoluted and inefficient way to write apt-cache show xserver-\* | grep Filename - and the grep must be ^Filename: to prevent false positives.

It also completely misses what I was saying. I was referring to making the status of forks visible directly in the generated debtree dependency diagram.

#25 Re: Devuan » Praise for the security updates » 2024-01-27 16:18:07

Fair enough - I missed that post.

Searching for xorg in the Devuan repos only returns xorg-server - which is the source package for "xserver-xorg-core", aka "Xorg X server - core server".

That's different to the "X.Org X Window System" from the "xorg" package I was referring to, but it is a dependency of it.

Searching the debtree of xorg for "devuan" highlights that xserver-common is also a fork, (unsurprising since it comes from the same xorg-server source package), but the debtree doesn't directly highlight that xserver-xorg-core is itself forked - would be nice if there was some way to have an indication of that.

It also seems the issue in your linked thread has yet to be resolved - based on the versions listed at //pkginfo.devuan.org/xserver-xorg-core and //tracker.debian.org/pkg/xorg-server, there should be a 2:21.1.7-3+deb12u4devuan1 in daedalus-proposed-updates and a 2:21.1.7-3+deb12u5devuan1 in daedalus-security channel.

Board footer

Forum Software