You are not logged in.
> 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".
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).
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.
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).
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.
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.
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 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.
Debian version numbers are explained in section 5.6.12 of the Debian Policy Manual:
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).
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.
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.
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.
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.
Thunderbird does not depend on systemd. The promptness of its security updates is due to Debian maintainers Carsten Schoenert, Christoph Göhre, and the Debian Security Team.
Firefox does not depend on systemd. The promptness of its security updates is due to Debian maintainer Mike Hommey, the Debian Mozilla Team, and the Debian Security Team.
Chromium does not depend on systemd. The promptness of its security updates is due to Debian maintainers Andres Salomon, Timothy Pearson, the Debian Chromium Team, and the Debian Security Team.
Xorg does not depend on systemd. The promptness of its security updates is due to the Debian X Strike Force, and the Debian Security Team.
None of these packages depend on systemd, none of these packages are forked by Devuan, security for them is not handled by the Devuan team.
This is not a slight on those who maintain Devuan but an attempt to communicate that Devuan is Debian (with systemd removed).
The Devuan Team do important work to maintain init freedom - and absolutely deserve credit for that - but they have nothing to do with how your web browser, mail client, or display server works.
I get no asterisk using the the quote button on this forum.
You appear to have missed the part of brocashelm's post stating the "asterisks are there because FluxBB apparently fails to parse things dynamically".
In other words, they added the asterisks because FluxBB is badly written, and complains if one tries to use "[c][quote][/c]", and the easiest workaround is to insert a dummy character.
-
The point they were trying to make is that clicking a button to add empty quote tags is near worthless - typing two tags is trivial. The lack of a per-post option makes it harder to keep track of things one might want to reply to.
Sort by modified date on both sides then only drag the files that are newer.
Or check out rclone which is in the repo, supports DropBox and can do equivalent to rsync.
However, asking a question isn't (shouldn't be) rocking a boat, especially if you're new to a process - being new to something is exactly when people are more likely to ask questions.
-
Apparently bird bath heaters are a thing. No idea how effective they might be, but might be worth checking out if you've got an outdoor power source.
Steve is not whining. (Your mention of feeding birds has a slight ring of that though.)
Have you tried asking the court if non-proprietary alternatives can be used - yeah, they may say no, but you'll never know if you don't ask. (And similarly, they might never learn why it matters if nobody ever raises the subject.)
In any case, DropBox almost certainly still has a browser-based interface, removing the need to install anything.
It means you don't have to re-install it every time you create a new profile, it's there from the start.
It might mean it doesn't get disabled next time Mozilla "forgets" to renew a certificate.
It hasn't been singled out - there's a bunch of other webext packages too. Most - but not all - are mainated by the "Debian Mozilla Extension Maintainers". I don't know what criteria they might have.
Greasemonkey used to be in the repo, but not with the webext- prefix; it got removed when it stopped working. If that's changed maybe you could ask for it to be re-added.
You're requesting the already stretched Devuan team of volunteers divert their time into investigating proprietary software for you? :|
Why don't you setup an isolated VM and check it out yourself?
Or even better, use something non-proprietary like Nextcloud that is already supported.
The way to install uBlock Origin is apt install webext-ublock-origin-firefox.
Since you can use uBlock Origin to disable and selectively enable scripts per domain, do you actually have a need for NoScript?
How does that script compare to the nftables init script which is already in the orphan-sysvinit-scripts package?
...
edit:
Looking at the nftables.init script the answer seems to be: the official-but-going-away script has better logging with a verbose option, and correctly sets name/desc variables, but not sure if there's any material difference...?
Searching with DuckDuckGo doesn't stop one from also submitting to Google - if a search doesn't return the results you want, add "!g" and it'll send the same terms to Google Search.
Before doing so, one might opt to use the "Share Feedback" option in the bottom right, to allow DuckDuckGo to improve.
And of course, if one wants Google Search results but without Google's personalized spying, consider if you trust Startpage's claims (or whether the acquisition by ad-company System1 is a problem).
Hibernation is different to the "Fast Startup" (i.e. fake shutdown) which arrived with Windows 8.
It does not exist in Windows 7.
That all three OSes mentioned boot slowly on an old computer containing 2008 spinning drives shouldn't be a surprise - even if WD3200AAKS usually has better performance than Samsung HD080HJ, there are plenty of factors which might account for the reported 5 seconds difference.
Anyhow, if people want to discuss boot times, might I suggest a distinct dedicated thread (with some degree of methodicalness applied).
I don't object to the suggestion in #18, but maybe it could be re-ordered to place the clarification next to where it applies:
Visitors are expected to exhibit adult behaviour, regardless of age, based on a foundation of mutual respect.
Or, if removing the adult/age terms, perhaps:
Visitors are expected to behave with maturity, and interact from a foundation of mutual respect.
The recommended sources.list for Daedalus is this:
deb http://deb.devuan.org/merged daedalus main
deb http://deb.devuan.org/merged daedalus-updates main
deb http://deb.devuan.org/merged daedalus-security main
Adding non-free-firmware repository is useful if used by the hardware in question.
Adding non-free and contrib are NOT needed.
Gimp is in the main repository.