[03:03] <lotuspsychje> good morning
[06:10] <ducasse> good morning
=== jelly-home is now known as jelly
=== kostkon_ is now known as kostkon
[17:06] <AWFunTV> hi , can someone help me about potentially un maintained packages in focal
[17:06] <daftykins> that'd be a support query for #ubuntu main
[17:07] <coconut> daftykins, my fault then, since i advised this channel.. oops
[17:07] <AWFunTV> i was just at #ubuntu main and they told me to come here
[17:07] <daftykins> ah well write it out and we'll see!
[17:08] <AWFunTV> @dafykine, was that a response to my request, as I got directed here from #ubuntu
[17:08] <AWFunTV> got is sorry slow updates
[17:09] <AWFunTV> The package ISC-DHCP-Server, has an ever growing number of un assigned bugs, and no activity since april
[17:09] <AWFunTV> #In my case due a a bug I cant run in a cluster
[17:10] <daftykins> a DHCP server in a cluster... interesting scenario
[17:11] <AWFunTV> you need a cluster of servers (clustered by dhcp), as if one fails and there is no backup, devices start dropping off the network when they try to renew the lease
[17:12] <AWFunTV> raised a bug had it confimed by multple other people, and a work around i.e use the dhcp from ubuntu 18.04. but no response from the maintainers
[17:13] <AWFunTV> and lots more potential bugs recieving the same (no) response
[17:14] <daftykins> 'buntus support period probably makes it unsuitable for your intended setup anyway, since i'd be willing to bet a cluster on a network is something you don't want to be reinstalling in 5 years
[17:15] <AWFunTV> testing only takes a few weeks
[17:15] <AWFunTV> already migrated from 14.04 - 16 - 18 - 20
[17:15] <AWFunTV> the config is really simple and used to work really well
[17:16] <AWFunTV> remember this is a cluster at the app level
[17:16] <daftykins> i don't think i'm following the use of the term right, normally clustering is for high availability of a more serious main service... just having DHCP not behave seems a little basic
[17:17] <daftykins> which release did it last behave correctly on?
[17:17] <AWFunTV> 18.04
[17:18] <AWFunTV> this is cluster at the app level not at the server level, I haven seen server level cluster for years, it all seems to be at the app level these data
[17:19] <AWFunTV> effectively isc-dhcp-server installed on two diffeernt system and they exchange state information, to allow either server to serve any request and each to be aware of each other state, so if one fails the remaining server can continue
[17:19] <AWFunTV> dont forget if DHCP fails, devices start to drop off the network as their IP  lease is not renewed, its kind of critical
[17:20] <AWFunTV> I currently have the 18.04 release installed and pinned on 20.04 and it workd perfectly
[17:20] <daftykins> so why did you upgrade?
[17:20] <AWFunTV> multiple people have confirmed the bug exists
[17:21] <daftykins> yes you've already repeated that and i'm quite familiar with DHCP :)
[17:21] <AWFunTV> to keep all the packages up to the latest level. Gone are the days of running  out of date s/w
[17:21] <daftykins> but apparently it wasn't important enough to test and identify ahead of time?
[17:21] <AWFunTV> I have a lot of AI running on the network
[17:22] <daftykins> lol, ok i'm out - this is a total crock
[17:22] <daftykins> hf
[17:22] <Ussat> define out of date software, just because its not latest dosnt mean its out of date
[17:23] <AWFunTV> I've worked in environments where people do not upgrade until the end of extended support. I've always tried to keep up with the latest s/w especailly as i run a lot of AI and want a consistent build,
[17:23] <AWFunTV> which is the right hannel to report un supported packages
[17:24] <daftykins> if you've already contacted the maintainer and they haven't responded, you'll have to change your distro choice or compile yourself
[17:25] <Ussat> again, the "latest" is not always the best . If you TRUELY wanted the LATEST you would not even be useing Ubuntu
[17:25] <AWFunTV> i though ubuntu had a policy that all s/w n teir packages much be maintained. I've reported by launchpad, bt they dont appear to be responsing to any issues
[17:25] <AWFunTV> USSat the latest with some stability
[17:25] <daftykins> !info isc-dhcp-server
[17:26] <Ussat> define "some stability"
[17:26] <Ussat> MOst corp envs are n-1
[17:26] <AWFunTV> daftykins is that an irc command ?
[17:26] <Ussat> https://www.cnn.com/2020/07/06/politics/robocalls-supreme-court-ruling/index.html
[17:27] <Ussat> ooppsss
[17:27] <AWFunTV> ussat agreed but it depends on the definition of n
[17:27] <AWFunTV> major , minor or lower
[17:27] <Ussat> ....
[17:27] <daftykins> it would have triggered the bot if it were working or present, yeah
[17:27] <daftykins> Original-Maintainer: Debian ISC DHCP maintainers <pkg-dhcp-devel@lists.alioth.debian.org>
[17:27] <Ussat> wahtever, you arre clueless
[17:28] <daftykins> well that's not quite the most polite way of phrasing it, but yes it sounds like this issue has been encountered due to a combination of unwise decisions and what i term 'version chasing' so i'm done
[17:29] <AWFunTV> friendly lot aren't you all
[17:29] <AWFunTV> bye
[17:35] <daftykins> best not to enable crazy
[17:35] <Ussat> but it CAN be entertaining...
[17:37] <daftykins> :)
[18:33] <ducasse> AWFunTV: are you using the package rom 18.04?
[18:33] <ducasse> *from
[20:21] <Bashing-om> UWN638 is on the streets - https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue638 :D
[20:25] <leftyfb> oerheks: why are you saying 18.04 isn't suitable for the pi 4? It should work fine. If not, then there's a bug that should be fixed
[20:25] <leftyfb> oerheks: https://ubuntu.com/blog/roadmap-for-official-support-for-the-raspberry-pi-4
[20:26] <oerheks> he claimed it did not, and returned i have actualle seen no issues
[20:26] <oerheks> long time we had to wait for the 19.10.1
[20:26] <waveform> the pi 4 support got backported to 18.04 but the current images have outdated firmware that won't boot it "out of the box"; upgrade the image on an older 3 and it will then boot on a 4
[20:27] <leftyfb> waveform: that's broken and should be fixed
[20:27] <leftyfb> no OS should require you to upgrade the OS on different hardware to work on a piece of hardware
[20:29] <waveform> the 18.04 support was largely for people that wanted to stay on 18.04, i.e. for upgraders; officially we supported the 4B *from* 19.10 - i.e. the LTS that supported the 4B "out of the box" was (and is) 20.04. Still, it is a confusing situation - I'll try and SRU the firmware for 18.04 for the next point release
[20:29] <oerheks>  Please note that even though these images are labelled "+raspi3" they are compatible with the Raspberry Pi 2 and 3 (and 4 in the case of 19.10.1).
[20:29] <oerheks> https://wiki.ubuntu.com/ARM/RaspberryPi
[20:29] <oerheks> ?
[20:29] <oerheks> i only have a rasppi 2 to test..
[20:31] <leftyfb> waveform: thank you
[20:32] <leftyfb> though to be clear, I'm only running 20.04 and Raspbian on my pi's. Moving to Ubuntu as sd cards die out
[20:32] <leftyfb> it's nice having my pi's running the same OS as my laptop