| kreyren | W: GPG error: http://deb.devuan.org/devuan testing InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB | 07:49 |
|---|---|---|
| kreyren | 07:49 | |
| kreyren | help | 07:49 |
| kreyren | where do i get the cert | 07:49 |
| kreyren | nwm found it | 07:50 |
| xrogaan | testing might not be the keyword you want | 08:16 |
| xrogaan | not sure though. fsmithred jaromil ? | 08:16 |
| kreyren | need help with it tho.. i don't know how to fix that gpg err;-; | 08:26 |
| kreyren | testing should be fine assuming running debian testing | 08:26 |
| kreyren | expecting frankendebian | 08:26 |
| Evilham | kreyren: testing is an alias for beowulf, which follows buster, aka debian stable | 08:27 |
| gnarface | kreyren: apt-key add [filename] | 08:27 |
| gnarface | (as root) | 08:27 |
| gnarface | there is a package for it though too | 08:28 |
| Evilham | kreyren: it wouldn't make much sense for devuan to follow debian "testing", because releases don't happen simultaneously and things would utterly break with e.g. different libc versions | 08:29 |
| Evilham | So testing is just an alias, and you probably want to use release names knowing what they mean | 08:30 |
| kreyren | is there release compatible with testing debian ? | 08:49 |
| xrogaan | which "testing" do you want? | 08:53 |
| xrogaan | buster or bullseye? | 08:53 |
| r3boot | kreyren: gpg --recv-keys 94532124541922FB | sudo apt-key add - | 09:31 |
| kreyren | r3boot, http://ix.io/1Qei | 09:42 |
| kreyren | xrogaan, it's bullseye, buster is stable now | 09:42 |
| xrogaan | yes, but ascii is still devuan's stable. | 09:47 |
| xrogaan | you want devuan's testing, which is beowulf | 09:47 |
| kreyren | you dont have symlink from testing to current release name? | 09:49 |
| kreyren | so that i woudn't have to change it after new release | 09:50 |
| kreyren | seems to be the case based on size and modify date in https://deb.devuan.org/devuan/ | 09:53 |
| xrogaan | devuan testing is beowulf. | 09:59 |
| xrogaan | https://deb.devuan.org/devuan/devuan/dists/testing/InRelease << "Suite: beowulf" | 09:59 |
| kreyren | xrogaan, so this is sane? http://ix.io/1Qet | 10:23 |
| xrogaan | no | 10:24 |
| xrogaan | debian testing != devuan testing | 10:24 |
| kreyren | xrogaan, so what should i use? expecting franken-debian | 10:36 |
| kreyren | beowulf? | 10:36 |
| xrogaan | stable debian, buster, correspond to testing devuan, beowulf. That is until beowulf gets released. | 10:39 |
| xrogaan | franken-debian is a bad idea | 10:39 |
| kreyren | why is it bad idea | 10:39 |
| xrogaan | Because you add back removed packages? Creates conflicts right? | 10:40 |
| kreyren | conflicts are not a problem i can resolve these | 10:41 |
| xrogaan | the checksum of the devuan packages, even though they don't differ from debian's, will be different | 10:44 |
| xrogaan | because of the tarball metadata | 10:44 |
| kreyren | noted | 10:44 |
| kreyren | So how do i resolve this on devuan? `W: GPG error: http://deb.devuan.org/devuan testing-proposed-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB` assuming https://pastebin.com/raw/JUh5Q1QG | 10:44 |
| xrogaan | you have devuan-keyring? | 10:45 |
| kreyren | nope | 10:46 |
| kreyren | trying to fetch | 10:46 |
| kreyren | got it works, ty | 11:07 |
| kreyren | ,v consolekit2 | 11:07 |
| kreyren | ah.. you don't have consolekit2 on devuan? | 11:08 |
| kreyren | got it nwm | 11:08 |
| kreyren | nwm that is consolekit1 how do i get consolekit2 ? | 11:55 |
| kreyren | you seem to have it on https://git.devuan.org/devuan-packages/ConsoleKit2 | 11:56 |
| Akuli | how do i update the clock from ntp or whatever devuan uses? | 18:24 |
| Akuli | i googled instructions and found ntp and ntpd, but they don't seem to be installed by default, is some ntp alternative installed? | 18:25 |
| gnarface | this is not different from debian | 18:26 |
| gnarface | apt-get install ntp | 18:26 |
| Akuli | is there a reason why it isn't installed by default? because debian doesn't do it? | 18:27 |
| gnarface | yes | 18:27 |
| Akuli | thanks :) | 18:27 |
| gnarface | with in some installation choices, it may get installed by default, but that would also be the same ones as debian | 18:27 |
| gnarface | you can use ntpdate instead if you just want to update the clock once and not keep a daemon running | 18:28 |
| gnarface | (same as debian there too) | 18:28 |
| unixman | If you have a "bad" clock with a large drift, as I have seen in some systems, might need to run a cron job several times a day to keep the clock in sync. | 18:30 |
| gnarface | yea, in those cases it's usually better to just run ntpd | 18:30 |
| gnarface | ntpd has almost no resource requirements | 18:30 |
| gnarface | they sure don't make those clocks like they used to | 18:31 |
| gnarface | and with ARM hardware that doesn't even have a actual clock, ntpd is almost a necessity | 18:32 |
| * unixman nods | 18:42 | |
| kreyren | is there any repository in devuan that is equivalent to debian bullseye? | 18:50 |
| gnarface | which one is bullseye now? is that their new testing? | 18:51 |
| kreyren | yep | 18:51 |
| gnarface | hmm, that's a good question but i don't know if it is up yet | 18:51 |
| kreyren | using https://i.imgur.com/NRZk9lz.png and i would want to use more recent packages from devuan | 18:52 |
| kreyren | since i need them for openrc from debian to work without issues | 18:53 |
| gnarface | i think the current state of affairs is that beowulf, which is still devuan testing, corresponds to debian stable now | 18:54 |
| gnarface | if debian buster just went stable recently | 18:54 |
| kreyren | yep seems to be that way | 18:54 |
| gnarface | so that puts devuan out of sync until they catch up | 18:54 |
| gnarface | you can still get the package from ceres though, in a pinch | 18:54 |
| kreyren | like it works fine with beowulf + bullseye atm | 18:54 |
| kreyren | actually it works great no issues in comparison to only debian.. | 18:55 |
| kreyren | ceres? | 18:56 |
| gnarface | ceres is devuan unstable, corresponding to debian sid | 18:56 |
| gnarface | like debian sid, it's always designated unstable | 18:57 |
| kreyren | i see i was thinking about it, but i'm not sure about stability on sid | 18:57 |
| gnarface | well you could try backporting the package just to see | 18:57 |
| kreyren | since my kreybian is rescue OS to gentoo/exherbo/guix | 18:57 |
| gnarface | sounds quite daring | 18:58 |
| kreyren | eh? O.o | 18:58 |
| gnarface | mixing distros/major releases/repos | 18:59 |
| gnarface | it's just all risky business | 18:59 |
| gnarface | i recommend make a backup before you do anything | 18:59 |
| kreyren | not really | 18:59 |
| kreyren | meh backup is for the weak xD i have configurations on remote server to fetch on demand rest can be grabbed from iso/tarball | 19:00 |
| kreyren | or i have WIP LFS script that can export apt on itself | 19:00 |
| kreyren | probably testing packages one by one on current to pin packages from sid is more sane? | 19:05 |
| gnarface | well, backporting from sid (ceres) is more sane | 19:05 |
| gnarface | which basically just means rebuilding from the src package | 19:06 |
| gnarface | but you might have to rebuild dependency packages too | 19:06 |
| gnarface | and it can get out of hand | 19:06 |
| gnarface | depending on how broad the discrepancies are | 19:06 |
| kreyren | compiling is preffered | 19:07 |
| kreyren | will investigate ty for info | 19:07 |
| gnarface | the basic procedure as described by the debian backports instructions should apply generally to devuan too | 19:07 |
| gnarface | the only real difference being which repo you get the src packages from | 19:08 |
| kreyren | i see | 19:08 |
| kreyren | is there a way to make debian sid to not fetch latest git commit etc.. ? So that it woudn't break as often | 19:09 |
| kreyren | or are these cherrypicked? | 19:09 |
| gnarface | yea i think that's up to the individual package maintainers | 19:09 |
| kreyren | noted | 19:10 |
| gnarface | some of them will do it that way because that's just what "unstable" is for... breaking things | 19:10 |
| gnarface | if you follow the story line of the movies that debian names their releases after | 19:10 |
| drawkula | iirc there are incoming and experimental before a package reaches unstable... | 19:11 |
| gnarface | it is important to note that "sid" is the neighbor kid that breaks toys | 19:11 |
| gnarface | that wasn't chosen by accident | 19:11 |
| drawkula | so unstable is not the hottest magma | 19:11 |
| kreyren | ik, just not sure if it's the best approach | 19:11 |
| kreyren | like i'm using experimental for nvidia-drivers which is sane for example | 19:11 |
| gnarface | yes, there is also "experimental" which is more risky than sid/unstable but it is not a complete package set | 19:11 |
| gnarface | just be aware that some package maintainers are using sid to try to fix their shit while some of them are actively trying to break it | 19:12 |
| kreyren | and using openrc with it's deps from sid should also be sane | 19:12 |
| kreyren | assuming that it's adapted for gentoo's rolling | 19:12 |
| gnarface | i did use experimental for nvidia drivers once and i would not recommend it | 19:13 |
| gnarface | ymmv | 19:13 |
| kreyren | works for me so far.. GPU performance is slightly better and it's more stable | 19:13 |
| kreyren | or like it was dropping frames on testing, but it issueless on experimental | 19:14 |
| drawkula | I typically grab the deb-sources... mixing binaries from different branches is not good for my sleep... :-) | 19:14 |
| kreyren | using deb-sources from debian+devuan is going to make them compatible? | 19:14 |
| drawkula | not automagically | 19:15 |
| kreyren | the built itself will output conflicts to be resolved prior to merge or ? | 19:15 |
| drawkula | some will build without changes, some need minor tweaks, some are beasts... | 19:15 |
| kreyren | i see | 19:16 |
| kreyren | ty for info, i will investigate | 19:16 |
| * kreyren needs to go afk now | 19:16 | |
| drawkula | lokk into the dsc files for build dependencies | 19:16 |
| drawkula | look | 19:16 |
| golinux | kreyren: The is not yet a devuan repo that parallels bullseye | 19:44 |
| golinux | That will only happen once beowulf (stretch) is officially released. | 19:45 |
| drawkula | beowulf (buster)? | 19:45 |
| golinux | Urmmm yes, Senior moment | 19:47 |
| golinux | Thanks for catching that. | 19:47 |
| drawkula | I mostly use debian/devuan+number in my notes | 19:49 |
| weedloser | any idea of when beowulf will get released? | 19:53 |
| weedloser | i bet you get this question often, sorry | 19:54 |
| gnarface | if you ask the right people you might be able to find a inventory of packages known to still be broken | 19:55 |
| gnarface | or if you have a spare machine you can just try it | 19:55 |
| gnarface | (or put it in a vm or whatever) | 19:55 |
| weedloser | I did try beowulf in a vm a few months back, worked fine | 19:55 |
| gnarface | i think they're still working on some of the permissions backends related to graphical login prompts and such | 19:56 |
| gnarface | it's probably fine for headless machines | 19:56 |
| weedloser | where can i see the progress and maybe help out? | 19:56 |
| gnarface | that's a good question and other than the repo itself i'm not sure the right answer | 19:56 |
| gnarface | i think jaromil might have been keeping a broken packages list separately from bugs.devuan.org where they're supposed to be submitted | 19:59 |
| weedloser | i see they have a gitlab but it's a little difficult to work with | 19:59 |
| weedloser | thanks | 19:59 |
| gnarface | but that list itself may be still incomplete. i think the status currently is they're still waiting for feedback to consider a status report valid | 20:00 |
| gnarface | oh and i think fsmithred was saying a week or two ago that most the task-* metapackages related to desktop stuff are broken | 20:02 |
| gnarface | or, if not most of them, an unknown quantity of them, making it a bit of a minefield | 20:02 |
| weedloser | too bad there's so little manpower into this project! | 20:05 |
| gnarface | yes, but we can only blame ourselves | 20:05 |
| gnarface | for not helping | 20:05 |
| gnarface | they're definitely looking for volunteers | 20:06 |
| weedloser | i know it's wishful thinking but i really hope this effort integrates with debian | 20:06 |
| weedloser | fragmentation is no good | 20:06 |
| gnarface | i hope debian disbands frankly | 20:06 |
| gnarface | and then all the users and testers and maintainers with a soul left just come over here | 20:07 |
| gnarface | but that is more of a conversation for #debianfork | 20:07 |
| weedloser | seeing as the nature of debian is compatibility and modular it just makes perfect sense to also have init freedom, support for several inits | 20:10 |
| weedloser | altough it's hard work | 20:10 |
| weedloser | only gentoo competes i think... and it's source based | 20:10 |
| gnarface | this is a designated support channel | 20:10 |
| weedloser | yes, sorry | 20:11 |
| gnarface | they've created #debianfork for this type of discussion | 20:11 |
| gnarface | and i'll happily agree with you there | 20:11 |
| fsmithred | there is collaboration between debian and devuan | 20:13 |
| fsmithred | on sysvinit, elogind, not sure what else | 20:13 |
| drawkula | debottstrap? | 20:27 |
| drawkula | deboo* | 20:27 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
