The officially official Devuan Forum!

You are not logged in.

#26 Re: Other Issues » [SOLVED] LXCFS 4.0.12 build ? » 2022-11-14 21:37:04

Sorry, Golinux, I overlooked your post above HoaS's.  I appreciate the warning <thumbs-up>

--K

#27 Re: Other Issues » [SOLVED] LXCFS 4.0.12 build ? » 2022-11-14 18:26:08

Thanks again, HoaS

I'll tag this thread solved and continue with the homework due-diligence.

Your time is much appreciated

--K

#28 Re: Other Issues » [SOLVED] LXCFS 4.0.12 build ? » 2022-11-14 17:58:26

Thank you, HoaS

I started looking into backports following RR's suggestion, which lead me to :

https://backports.debian.org/Instructions/

As a matter of Backports policy, packages in the stable-backports suite are taken from Debian testing ...

And following the tracker link RR provided, no releases in the vendor 4.x.x branch following 4.0.7 have been added to testing :
https://tracker.debian.org/pkg/lxcfs

It looks like immediately following the 4.0.7 release, the target was moved to 5.0.0 and then to 5.0.2.

If I understand policy correctly, I would be asking for a backport of 5.0.2 from testing to be made available for Bullseye in Backports.  If I were the package maintainer receiving that request, my response would likely be something along the lines of "Why are you making more work for me?  Eyes on Bookworm.", because experience suggests backporting a major 5.x.x version to a system built at the time 4.x.x was stable frequently gets hairy.  If that kind of work were the norm, I would expect Backports to be a bit of an unstable mess.

My perception was that Debian Updates followed software vendor stable releases :
https://linuxcontainers.org/lxcfs/downloads/

  • lxcfs-4.0.7 => lxcfs-4.0.8 => lxcfs-4.0.9 => lxcfs-4.0.10 => lxcfs-4.0.11 => lxcfs-4.0.12

But, that seems not to be the case.

When you say "The stable release is so named because the version numbers do not change.", does that mean Updates are more like :

  • lxcfs-4.0.7-1 + patches => lxcfs-4.0.7-2 + patches => lxcfs-4.0.7-3 +patches => lxcfs-4.0.7-4

In which case patches are generally limited to bug squashing and mitigating security concerns?

If I were to produce a patch against lxcfs-4.0.7-1 that exclusively corrected the lxcfs presentation of /proc/meminfo ... would that be welcomed within the Debian ecosystem and worthy of an lxcfs-4.0.7-2 package being released?

Perhaps what I am looking for is a grey area between Backports and Updates where the software vendor has addressed minor issues within a major release and deemed a minor release is warranted.  Do these minor releases get picked up in the Debian update cycle?  Or do folks just wait for the next Debian stable release?

Thank you for your time as I build an understanding of the way things work,
--K

#29 Re: Other Issues » [SOLVED] LXCFS 4.0.12 build ? » 2022-11-13 23:00:22

Thanks, RR

For my immediate needs I did this :

apt-get install devscripts
apt-get install quilt
mkdir /tmp/lxcfs
chown _apt:root /tmp/lxcfs
cd /tmp/lxcfs/
apt-get source lxcfs
apt-get build-dep lxcfs
wget https://linuxcontainers.org/downloads/lxcfs/lxcfs-4.0.12.tar.gz
cd lxcfs-4.0.7
uupdate -v 4.0.12-1 ../lxcfs-4.0.12.tar.gz 
cd ../lxcfs-4.0.12-1
vi debian/rules

override_dh_installinit:
#    mv debian/lxcfs/etc/rc.d/init.d/lxcfs debian/lxcfs.init
#    rm -rf debian/lxcfs/etc/rc.d
    dh_installinit -p lxcfs --no-stop-on-upgrade

override_dh_installsystemd:
#    dh_installsystemd -p lxcfs --no-stop-on-upgrade lxcfs.service

dpkg-buildpackage -us -uc -b

And this produced an "lxcfs_4.0.12-1-0devuan1_amd64.deb" package that I installed and confirmed the /proc/meminfo fix works.  Nice.

So that is great ... for me.  But I'm still at a loss, regarding Debian/Devuan culture (I earned my grey beard in the RPM world), as to how one effectively approaches/advocates/assists toward greater symmetry between stable vendor releases and distribution updates without stepping on toes within the Debian ecosystem.

Is there a Welcome-to-Debian blog somewhere tailored for old transplants?
--K

#30 Other Issues » [SOLVED] LXCFS 4.0.12 build ? » 2022-11-12 21:13:31

kaiyel
Replies: 8

Version 4.0.12 of LXCFS has been out since 2022-Feb, but no update past the 4.0.7-1 release is available in Debian :

https://packages.debian.org/bullseye/allpackages
https://packages.debian.org/bullseye-up … llpackages

The latest stable release of LXCFS, from the detailed changelog, indicates meminfo and swaps are now cgroupv2 aware.  That has value to me as some software I use relies on meminfo to tune itself to available memory :

https://discuss.linuxcontainers.org/t/l … ased/13287

I found the Debian work-needing and prospective packages page, but no mention of updates for LXCFS appear forthcoming :

https://www.debian.org/devel/wnpp/

Is it accurate to say my options are "doing without" or "building my own"?

As a transplant from the RPM-world my question is a bit of an ecosystem/protocol question in the DEB-world.  Can someone educate me as to a proper series of events that should take place to advance a Debian package update?  I'm confident I can roll my own package (having done so in the RPM-world as needed), but that only helps me.

Thanks,
--K

#31 Documentation » HOWTO : Fix bind9 managed-keys-zone: Unable to fetch DNSKEY set '.' » 2022-11-10 17:45:18

kaiyel
Replies: 0

I had a need for a local caching-only name server and installed my goto resolver
bind9 on a fresh Chimaera instance.

apt-get install -y bind9 bind9-utils

Out of the box I discovered an error logged to syslog and all lookups failed :

managed-keys-zone: Unable to fetch DNSKEY set '.': timed out

The default location for the "bind.keys" file is "/etc/bind.keys", but the package
locates that file as "/etc/bind/bind.keys".  As such it was necessary to specify the
current file location by editing the "/etc/bind/named.conf.options" config :

vi /etc/bind/named.conf.options

such that :

dnssec-validation auto;
bindkeys-file "/etc/bind/bind.keys";

And, after saving, remove the (likely junked) cache file and journal :

rm /var/cache/bind/managed-keys.bind*

Restart bind and my caching server is now usable.

--K

#32 Re: Installation » From Debian (testing) to Devuan » 2022-09-29 17:21:49

For those who are interested in the greybeard history of why "bin" was split between "/bin" and "/usr/bin" :

http://lists.busybox.net/pipermail/busy … 74114.html

--K

#33 Re: Documentation » HOWTO : enable pasting linefeed-separated commands into bash terminal » 2022-09-20 15:51:02

Fair smile

As mentioned in the detailed Bash list of changes, bracketed paste mode was enabled by default starting in bash-5.1-alpha.

For folk like me, bash 5.x is a shiny new thing and losing the default ability to immediately execute pasted commands is a change to decades old behavior.  I doubt Devuan (or Debian) devs will stray from the new defaults established by bash devs -- so I think you are in good shape.  And to their monumental credit, the bash devs gave us an easy way to restore old behavior.  In the future, should the bash devs determine the old way was the more common usage and change the default back, this same bashrc tweak can be reversed to turn the new behavior back "on" for you as well.

#34 Re: Documentation » Help - list all services » 2022-09-19 22:37:19

If you've migrated from the Redhat world where you were comfortable with "chkconfig --list",

apt-get install -y sysv-rc-conf

and see if you like "sysv-rc-conf --list".

--K

#35 Documentation » HOWTO : enable pasting linefeed-separated commands into bash terminal » 2022-09-19 19:12:40

kaiyel
Replies: 4

Hat tip to Chris Siebenmann :

https://utcc.utoronto.ca/~cks/space/blo … asteChange

I regularly paste short lists of linefeed separated commands from a library of various instructions into bash terminal windows to accomplish small tasks.

The bash shell on my devuan system accepts the pasted content, but waits for a final interactive <enter> keypress before proceeding with command execution.  I've not experienced that interactive <enter> confirmation requirement before.  I understand it allows folks one last read of the commands before execution, so it's not necessarily a bad default.  But after giving myself some time to try and get used to it, I've decided it's just not for me.  If I copied the linefeed and pasted it, it is because I wanted the command executed ... every single time.

Thanks to Chris Siebenmann's blog I learned this interactive confirmation is a new feature of bash that can be turned off by appending this change to the "/etc/bash.bashrc" configuration :

bind 'set enable-bracketed-paste off'

Start a new shell and I'm back to middle-mouse clicking my pasted commands without having to touch the keyboard.  A "win" for me; maybe for you too.

--K

#37 Other Issues » [SOLVED] Missing RapidSVN » 2022-01-04 16:37:17

kaiyel
Replies: 2

Since upgrading to chimaera, RapidSVN is no longer available :

$ apt-get download rapidsvn
E: Can't find a source to download version '0.12.1dfsg-3.1+b1' of 'rapidsvn:amd64'

$ apt-get source rapidsvn
Reading package lists... Done
E: Can not find version '0.12.1dfsg-3.1' of package 'rapidsvn'
E: Unable to find a source package for rapidsvn

Did it not make the cut / does a better (one that does not involve Java or KDE libs) alternative exist?

Thanks,

--K

#38 Documentation » HOWTO : enable pure-ftpd to follow symbolic links » 2021-10-13 20:52:39

kaiyel
Replies: 0

One of pure-ftpd's key FTP server features is the ability to chroot individuals to their home folders, while still allowing the admin to use symbolic links to delegate disk space to these individuals.

From https://www.pureftpd.org/project/pure-ftpd/ :

Symbolic links can be followed when users are chrooted, even when they are pointing out of the chroot jail. This unique feature makes shared content easy to set up.

However, this feature requires that the binary has been compiled with the --with-virtualchroot switch set.  Failure to do so will result in ftp clients experiencing errors like "550 Can't change directory to thefoldername: No such file or directory" when attempting to navigate symbolic link folders.

Unfortunately for me, who uses this feature in-house (each dev group has their own "project" share), office (the scanner uploads to a samba accessible folder), and production (customers each have their own "site" share), the Devuan/Debian package has not set this flag.

What follows are the steps I used to restore that feature capability to the Devuan pure-ftpd package.  Rebuilding .deb packages is old-hat for the Debian folks, so read no further.  But if you (like me) are escaping the RedHat/systemd fork-that-was-not-a-fork, and are much more acquainted with RPM than APT, maybe this helps.

echo "start with an updated system"
apt-get update
apt-get upgrade

echo "you will need the devscripts tools"
apt-get install devscripts

echo "work within a folder apt can access"
cd /tmp/

echo "acquire the pure-ftp source and build dependencies"
apt-get source pure-ftpd
apt-get build-dep pure-ftpd

echo "set the virtualchroot flag"
cd pure-ftpd-1.0.47/
vi debian/rules
-- optflags=--with-everything --with-largefile --with-pam --with-privsep --with-tls --with-rfc2640
++ optflags=--with-everything --with-largefile --with-pam --with-privsep --with-tls --with-rfc2640 --with-virtualchroot

echo "supply a changelog comment and bump the revision number"
dch -n

echo "rebuild and install the package(s)"
debuild -us -uc
cd ..
apt-get install ./pure-ftpd_1.0.47-3.1_amd64.deb ./pure-ftpd-common_1.0.47-3.1_all.deb

echo "done"
cd

Hope I have that right ... feedback is welcome.  There was a bit of trial and error failure getting there as this was my first ever .deb package rebuild.

--K

#39 Documentation » HOWTO : LibreOffice open files on "Windows share" (samba) server » 2020-10-07 06:01:20

kaiyel
Replies: 1

I found I could not open spreadsheets from a "Windows share" connected samba server from this freshly installed Devuan Beowulf Mate desktop.  I've had this issue before using both openoffice and libreoffice on other distributions.  I was able to replicate the "fix" here and thought I would add this to the documentation for anyone having similar issues.

su - root
apt-get install gvfs-fuse
apt-get install libreoffice-gnome
sed -i 's/#X-GIO-NoFuse=true/X-GIO-NoFuse=true/' /usr/share/applications/libreoffice-*
reboot

Having experienced this with versions of Mint and PCLOS in the past, and now Devuan, I wonder "is it just me" or should a dependency be added to the libreoffice installer?

--K

Board footer

Forum Software