| ibanja | I have mirrored two drives on zfs pool backup. How do I get it to automount on boot? | 03:07 |
|---|---|---|
| ibanja | zfs pool is called 'backup' and it mounts on '/zfs' | 03:08 |
| gnarface | i haven't messed much with zfs but normally you'd handle auto-mount from your /etc/fstab | 03:09 |
| ibanja | zfs is different. The systemd command is: systemctl enable zfs.target zfs-import.service zfs-mount.service | 03:12 |
| ibanja | all answers these days seem to be systemd answers. | 03:12 |
| ibanja | OK, that was easy. It just worked and mounted on reboot. | 03:26 |
| cousin_luigi | eyalroz: Yeah, unfortunately I don't use debian/devuan in a graphical environment. Not sure how the package build flow works here. | 06:04 |
| cousin_luigi | rwp: The package I've inherited has an internal time save feature for devices without RTC: do you think fake-hwclock would be a good replacement? https://gitlab.com/lbaldoni/voyage-util/-/blob/main/debian/voyage-util.voyage-sync.init?ref_type=heads#L88 | 06:08 |
| rwp | cousin_luigi, The advantage to fake-hwclock is that it is used by every Raspberry Pi, of which there are many, and a lot of other systems. So it is a pretty well used package. And it will happen at the right time in the system boot. Better is to have an actual hwclock and avoid the problem. But if your internal method works then it works. | 07:34 |
| cousin_luigi | rwp: Makes sense. In fact I dropped that thing, which I had never used since 2007 or so. | 07:35 |
| rwp | What is "that thing"? voyage-util/? | 07:36 |
| cousin_luigi | rwp: The clock save feature of voyage-util. Perhaps you clicked on the link after I deleted everything. | 07:54 |
| cousin_luigi | rwp: https://gitlab.com/lbaldoni/voyage-util/-/commit/b270a056c87fa2586d4f6ce01d2a497d6ae14808 | 07:55 |
| rwp | I clicked on the link and the save restore of time to a timestamp file was there. | 07:55 |
| cousin_luigi | fake-hwclock seems more polished | 07:55 |
| rwp | The problem is that "that thing" didn't really identify anything, and you said you hadn't used it since 2007, but it was still there so you were using it now, you can see the confusion. | 07:56 |
| cousin_luigi | rwp: Sorry, done too many things and interacted with too many people in the last few days. | 08:03 |
| rwp | I understand. People were not meant to talk to other people in December. We were meant to hide from predator beasts, drink, and pray our autumn harvest will last us through the winter. The Internet and food advanced preservation techniques has ruined us forever now. | 08:06 |
| onefang | lol | 08:13 |
| xrogaan | The Release file in daedalus-security hasn't changed since the 21th of December: http://deb.devuan.org/merged/dists/daedalus-security/main/binary-amd64/ | 11:46 |
| xrogaan | Received multiple security bulletins since then. | 11:47 |
| cousin_luigi | How come devuan is a point ahead of debian with the kernel? | 13:30 |
| cousin_luigi | I thought that was shared. | 13:30 |
| xrogaan | are you on testing? | 13:36 |
| cousin_luigi | xrogaan: no | 13:37 |
| xrogaan | cousin_luigi: the kernel are the same, so you might not be on stable. Or you have the backport kernel | 15:31 |
| cousin_luigi | xrogaan: http://paste.debian.net/hidden/cdb111b2/ Can you explain this? | 15:52 |
| xrogaan | cousin_luigi: yeah, I believe a mirror isn't updating. | 15:54 |
| cousin_luigi | xrogaan: But a mirror is AHEAD | 15:54 |
| cousin_luigi | Unless...oh you mean on bookworm? | 15:55 |
| xrogaan | bookworm is 6.1.67 | 15:55 |
| cousin_luigi | xrogaan: https://packages.debian.org/bookworm/linux-image-amd64 | 15:56 |
| cousin_luigi | Where do you see 67? | 15:56 |
| xrogaan | it's in stable-proposed-update and stable-update | 15:56 |
| cousin_luigi | How come the website doesn't reflect that yet? | 15:57 |
| xrogaan | it does: https://tracker.debian.org/pkg/linux-signed-amd64 | 15:58 |
| xrogaan | https://qa.debian.org/madison.php?package=linux-signed-amd64 | 15:59 |
| cousin_luigi | oh | 16:00 |
| xrogaan | devuan: do you not handle some mirror? | 16:33 |
| xrogaan | https://qa.debian.org/madison.php?package=chromium << security should be .129 | 16:33 |
| xrogaan | https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=chromium&x=submit | 16:33 |
| xrogaan | but the listing for daedalus-security is still .109 | 16:34 |
| xrogaan | wait, which one is the stable channel again? | 16:34 |
| xrogaan | it's chimera. nevermind then | 16:34 |
| xrogaan | Yeah, the mirror I am hitting is borked | 16:35 |
| xrogaan | i 120.0.6099.109-1~deb12u1 stable-security 500 | 16:35 |
| * blockhead scrolls up. there is an irc channel just for stable? | 17:22 | |
| golinux | blockhead: no | 17:24 |
| salago | Hi, i have lost all my saved money to FTX jews around 20000 dollars. | 19:18 |
| salago | Please help me live. Please help me. | 19:18 |
| salago | BTC : bc1q9vfmfwj6av9pxj50r6xyl652mwhqvw5ds86nw2 | 19:18 |
| rwp | Difficult to block that type of scammer. Just a hit and run. | 19:29 |
| n4dir | is is the second time i run in this error on old-stable: dpkg-deb: error: archive 'jjazzlab_4.0.1-1_amd64.deb' uses unknown compression for member 'control.tar.zst', giving up | 19:59 |
| n4dir | dpkg-deb: error: archive 'jjazzlab_4.0.1-1_amd64.deb' uses unknown compression for member 'control.tar.zst', giving up | 19:59 |
| n4dir | sorry for double quote. | 19:59 |
| n4dir | Besides unpacking and repacking the whole shebang is there a more easy approach to solve the problem (besides the obvious: upgrading to stable) | 20:00 |
| fsmithred | should be zstd? | 20:08 |
| fsmithred | or maybe install zstd | 20:08 |
| n4dir | zstd is installed | 20:09 |
| n4dir | for the other app (surge XT) i followed a guide, and it meant to unpack the deb, then untar a file, the put the whole thing back together. Which was not much fun | 20:10 |
| n4dir | only to find out 3 days later surge XT crashed due to other errors, and removed it again. | 20:10 |
| fsmithred | what does file say about control.tar.zst? | 20:11 |
| n4dir | whew, how did you unpack a deb file again? | 20:12 |
| n4dir | just "ar x" my history says | 20:13 |
| n4dir | control.tar.zst: Zstandard compressed data (v0.8+), Dictionary ID: None | 20:14 |
| n4dir | output of "file" | 20:14 |
| fsmithred | 1.21.18 <- dpkg with zstd support | 20:35 |
| n4dir | is it in backports? | 20:35 |
| n4dir | oh, i got them enabled. Doesn't look like it | 20:35 |
| fsmithred | good question. chimaera has newer. | 20:35 |
| fsmithred | sorry, daedalus has newer | 20:36 |
| n4dir | you sure? I am non chimaera ... ah, you got it wrong | 20:36 |
| n4dir | well, no biggie. Not sure how long i will run this old stable version. | 20:36 |
| n4dir | surge XT would be nice, the app i just ran into (jjazzlab) is not for my needs | 20:37 |
| n4dir | back some years i was proud running sid. Now i am always proud if on old-stable :-) | 20:37 |
| rwp | The nice thing about (Old)+Stable is that I am not continuously thrashed churning through endless updates. | 20:41 |
| rwp | One can unpack .deb files using dpkg-source but manually is easy as they are old stile old .ar files and "ar x foo.deb" will unpack them into control.tar and data.tar files. | 20:41 |
| rwp | Then you can uncompress each of those files. Which is apparently what tripped up dpkg for you as it was using an unknown compression. | 20:42 |
| n4dir | yeah, as said, i did that for surge. It isn't really comfortable. | 20:42 |
| rwp | It's possible to pack those back up into a valid .deb file but one must remember to tell ar that it must use the ancient original ar format to do so. Or one can rebuild it with dpkg-buildpackage with some effort. | 20:43 |
| n4dir | nope, just packed it back together and that worked. | 20:43 |
| rwp | Best is if you get the source and rebuild it from source. That would be a backport. And it would be the most reliable since it was compiled on your system with the version of the shared libraries that are installed. | 20:43 |
| n4dir | for jjazzlab i could just download another zip file, no deb, unzip it and run the bin/jjazzlab. I was more asking in general | 20:45 |
| rwp | The general purpose solution is to upgrade. (shrug) | 20:48 |
| spine-o-saurus | hay so i loaded up install media and went thru install steps but it is at partition disks part, but it only has ext2 file system option. isn't there an ext4 option? | 23:19 |
| debdog | spine-o-saurus: what install media? no, there should be much more options than just ext2. expert install? mayhap you missed loading some module | 23:36 |
| spine-o-saurus | oh ya i missed the install step to load modules | 23:39 |
| spine-o-saurus | now it is showing | 23:39 |
| debdog | phew, easy fix | 23:39 |
| debdog | have success! (do not mix with sucks-ess) | 23:41 |
| spine-o-saurus | grub wants to configure NVRAM variables to boot into Devuan automatically. this is the standard? | 23:56 |
| rwp | spine-o-saurus, UEFI boot requires NVRAM variables known as EFI vars in order to boot internal storage like disk drives and SSDs. | 23:59 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!