[00:54] <darkblueb> on LUbuntu jammy installer disk, how can that be set as a source of packages
[01:02] <darkblueb> a quick find says that there are only grub and efi related dot-debs on the ordinary filesystem, on that jammy install DVD
[02:21] <teward> the installer is based off a config file and seeded by the packages in the iso.  why do you want to source a debian repo or package in (L)Ubuntu?  It can introduce unpredictable behavior.
[02:21] <teward> darkblueb: ^
[02:21] <teward> also not all of us are around on the weekend - this is a support chat done by volunteers so
[02:22] <darkblueb> hi from Berkeley teward
[02:22] <teward> hi from the pits of despair.  :P
[02:22] <darkblueb> our reputable dot-org has built club linux for close to ten years
[02:22] <teward> so fyi before you go further
[02:23] <teward> i'm an it security guy
[02:23] <darkblueb> previously the phd in athens that does it, had used a certain tool chain, but in jammy times, things may change
[02:23] <teward> prefacing with "our reputable site" immediately is a red flag
[02:23] <darkblueb> please confirm any public records you wish
[02:23] <teward> just saying ;)
[02:24] <teward> how about you start with what your goal is
[02:24] <teward> so i dont have to read 8+ hours of backlog
[02:24] <teward> i.e. what are you trying to do
[02:25] <darkblueb> hm well, it is a bit like an onion perhaps
[02:26] <darkblueb> I had installed jammy with XUbuntu installer two or three times in VMs with virtualbox, on a large'ish machine I own
[02:26] <darkblueb> using that iso image file
[02:26] <darkblueb> next, booting a real machine with an LUbuntu installer, to install to a 5TB drive, and that is now done
[02:27] <darkblueb> that machine has enough horsepower to meaningfully runs VMs, and a builder
[02:27] <darkblueb> with a base jammy installed and stock universe repos, I can do small checks on what versions of major things there are .. on jammy
[02:28] <darkblueb> for the purposes at hand here, the packaging is really current.. too current perhaps!  multiple people have already expressed surprise at python 3.10
[02:29] <darkblueb> so I am looking around at the installed jammy world, with the installed setup, and discovering now the debian live system, including  live-build
[02:29] <darkblueb> live-build is a package available in stock repos, and I am reading the source and layout now
[02:30] <darkblueb> I'll write some condensed version of what I find, to the tech lead in athens
[02:32] <darkblueb> you are Ubuntu Studio team you say
[02:33] <darkblueb> the setup I will burn has qt5 based desktop apps, it has some server things on apache, and also tomcat java, and it has postgresql with some very stable parts 
[02:34] <darkblueb> I am generally quick to show others the site and the docs in ten+ human languages, however if you mean it to be a security check, you will have to put that in writing to someone that is not me
[02:36] <darkblueb> I install and look over, corrspond with the teams, fix small things, for more than fifty team projects in all the major language groups, on that "dstro" 
[02:37] <darkblueb> we used to use xfce long ago, but since we have core qt5 apps, LUbuntu seemed natural.. it has not been a perfect ride
[03:14] <teward> darkblueb: i think you're confusing Ubuntu Studio with Lubuntu
[03:14] <teward> they're different teams
[03:15] <darkblueb> indeed
[03:15] <teward> you might want to consider installing Lubuntu plain, and then running a script to install your projects, etc.  Unfortunately, i think customization of the installer is slightly beyond the standard support scope of this channel
[03:15] <teward> but what it sounds like is you want to make a custom iso/spin of Lubuntu that installs certain packages, code, etc. preset
[03:16] <teward> you might want to just script it, install Lubuntu, load script, run script post-install.  Rather than trying to customize the ISOs.
[03:16] <darkblueb> you can try it anytime - it works great
[03:16] <teward> I don't know how/what/if live-build is even something that the UBuntu ISOs use
[03:16] <teward> because Lubuntu's ISOs use i believe Calamares as their installer driver
[03:16] <darkblueb> we have distribution in the mid-ten thousands or so I think
[03:16] <teward> and when I say Ubuntu i mean ubuntu and flavors.
[03:22] <darkblueb> the european union satellite imagery distribution clouds feature our distro, for example.. that counts
[03:27] <darkblueb> but, I hear you about Calamares and otherwise .. the previous edition and back have been built with tools that are maybe not in jammy now.. I am finding out
[03:34] <guiverc> calamares has been used on releases of Lubuntu since Lubuntu 18.10; 18.04 was the last using `ubiquity` & debian-installer (as alternate ISO)
[09:49] <Towser> I have a question, i have an MSI U180 and I'm thinking of switching it to lubuntu, will it run much worse or will it run as ok as puppy did?
[11:56] <guiverc> Towser, you can't make comparisons & expect them to fit all situations.. Puppy Wary was extremely light with specifics apps; but not modern apps; but you probably don't mean wary (5.3).  Lubuntu is LXQt thus very light with Qt5 apps... I don't know which Puppy you mean, nor what tk/libs they use, but if it's not Qt5 you won't be comparing apples with apples.. so contrast what you'll run with what the OS/DE choice uses by default; more so than 
[11:56] <guiverc> distro vs. distro
[11:57]  * guiverc ignores release details that matter too..  ie.  all of hte software stack matters inc. user apps you'll be using
 https://askubuntu.com/questions/1135874/how-to-scale-display-in-lubuntu-up-150-or-200
 "Scaling is a known issue with LXQt"
 Going through https://github.com/lxqt/lxqt-config/issues/401, and it seems still to be so.
 I want to tweak DPI to me HiDPI screen, while keep scaling the same to my 2nd monitor. 
 Would that be possible?
 My xterm looks really tiny on my HiDPI laptop screen. However, I only want to change its DPI, not xterm's font, as bringing xterm up on my remote display looks just as normal as always.
 My advice is to avoid using xterm
 xterm is what I use most. 
 It happens to everything else too, like my featherpad, or gnome.
 Featherpad should not have this problem as a Qt app
 Weird
 hmm... not as obvious, just a bit smaller than I'd prefer