[07:02] <dholbach> good morning
[13:00] <dionjp_> Has anyone found a workaround for the issue where the nodes are in commissioning state ?
[21:30] <epikvision> though this may seem unrelated, I want to fix my first bug.
[21:30] <epikvision> https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1022935
[21:32] <epikvision> it's just a typo. I'm currently reading the "fixing a bug" page on the packaging guide.
[21:37] <epikvision> is it more reliable to pull the code from the launchpad site rather than use bazaar?
[23:18] <ScottK> Yes.


[07:43] <guiverc> kgiii, I gather you won't be around (now), but do you test sound in your *live* testing?  (watch something in firefox test or other?)
 FYi- all or most installs I do - sound is tested + video - no probs with kinetic so far (re @lubuntu_bot: (irc) <guiverc> kgiii, I gather you won't be around (now), but do you test sound in your *live* testing?  (watch something in firefox test or other?))
[08:03] <guiverc> thanks @Leokolb, I've not noted any issues either (inc. this box) .. reason for question was https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1979113
[08:04] <guiverc> (there is a thread on UF too about it)
 The bug report was on Budgie as far as I can see
[08:08] <guiverc> yeah, but I suspected it would impact more.. reporter was using GNOME..
[08:09] <guiverc> I'll just watch it; I've had no issues with my sound (excluding some songs I maybe didn't like)
 Eyes peeled @guiverc (re @lubuntu_bot: (irc) <guiverc> I'll just watch it; I've had no issues with my sound (excluding some songs I maybe didn't like))
[08:22] <guiverc> :)
[13:31] <kgiii> @guiverc I don't consider that part of my normal testing - but it's a part of my more advanced testing, when I test longer than normal. If that's the case, sounds will get tested.
[13:34] <kgiii> @guiverc & @leokolb Can one of you confirm https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1977465 so that hopefully it'll get noticed and fixed. I believe the fix should be simple, simply restorinjg the proper config files from previous releases. I have no idea how nobody else has confirmed it yet. It's a pretty glaring bug.
[15:02] <tsimonq2> kgiii: If you literally throw me a patch I'll handle the packaging :)
 "thanks @Leokolb, I've not..." <- Can repro when I manually switched to pipewire...
[15:04] <tsimonq2> A few questions related to pipewire:
[15:04] <tsimonq2>  - Does all of our existing code work with pipewire-pulse or even straight pipeline?
[15:04] <tsimonq2>  - What is involved in switching?
[15:04] <tsimonq2> * Can repro when I manually switched to pipewire...
[15:04] <tsimonq2> A few questions related to pipewire:
[15:04] <tsimonq2>  - Does all of our existing code work with pipewire-pulse or even straight pipewire?
[15:04] <tsimonq2>  - What is involved in switching?
[15:24] <tsimonq2> Dan Simmons: ask on the mailing list for a good time?
 Confirmed the bug (re @lubuntu_bot: (irc) <kgiii> @guiverc & @leokolb Can one of you confirm https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1977465 so that hopefully it'll get noticed and fixed. I believe the fix should be simple, simply restorinjg the proper config files from previous releases. I have no idea how nobody else has confirmed it yet. It's a pretty glaring bug.)
[15:24] <tsimonq2> I'd like to be able to focus on making money for a few days, block out a day or two for stack updates, and just bang it out
[15:25] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Are you subscribed to the lubuntu-devel mailing list and would you be interested in participating in a mini virtual sprint?
 "Dan Simmons: ask on the mailing..." <- Sure, maybe on Discourse too?
[16:59] <arraybolt3[m]> Simon Quigley (Developer): Virtual sprint sounds good, and yes, I am subscribed to the lubuntu-devel list. IIRC, we were planning next Monday?
[17:01] <arraybolt3[m]> kgiii: I actually tested for and found the bug, and reported it on the QA tracker, but never added a confirmation on Launchpad. I just confirmed it.
[17:03] <arraybolt3[m]> Oh, and good morning to everyone!
[17:03] <kgiii> arraybolt3[m]: Thanks! It should be a fairly trivial fix, as the work has been done before.  It's after noon here. 13:05ish
[17:39] <arraybolt3[m]> kgiii: It's after 12 here, I just said "Good morning" since I had just woken up a bit ago. So I guess it's actually good afternoon.
[17:40] <LeoK[m]> arraybolt3[m]: Early evening ...
[17:41] <arraybolt3[m]> Leo K: Just when the sun hit a 115 degree angle from the horizon. </oddlyspecific>
[18:04] <arraybolt3[m]> (Just realized I totally misunderstood what you said, nevermind, badly placed joke...)
[19:07] <arraybolt3[m]> Simon Quigley (Developer) Dan Simmons Finished packaging Featherpad 1.3.0 for Qt5, repo is at https://github.com/ArrayBolt3/featherpad-packaging. I did get some Lintian output that I'm not quite sure what to do with, and I need someone to double-check the debian/copyright file for me, but I think it's done! I'll pastebin the Lintian output.
[19:08] <arraybolt3[m]> Lintian output: https://termbin.com/70s0
[19:09] <arraybolt3[m]> Also, I still have my old debian/copyright file, if it is helpful.
[19:13] <tsimonq2> W: featherpad: no-manual-page usr/bin/featherpad
[19:13] <tsimonq2> W: featherpad: no-manual-page usr/bin/fpad
[19:13] <tsimonq2> If featherpad has zero CLI interface, override these. If they do have a CLI interface, file an upstream bug (and optionally submit a PR with a manpage)
[19:14] <tsimonq2> I: featherpad source: older-debian-watch-file-standard 3
[19:14] <tsimonq2> Fix this
[19:14] <arraybolt3[m]> There is a bit of a CLI interface.
[19:14] <tsimonq2> X: featherpad source: debian-rules-uses-as-needed-linker-flag (line 5)
[19:14] <tsimonq2> Investigate but pedantic
[19:14] <tsimonq2> arraybolt3[m]: There you are then :)
[19:15] <tsimonq2> P: featherpad source: update-debian-copyright 2021 vs 2022 [debian/copyright:15]
[19:15] <tsimonq2> See if an issue
[19:15] <tsimonq2> Besides what I mentioned LGTM
[19:16] <arraybolt3[m]> OK, nice! The copyright thingy is on "Files: debian/*", so maybe I should add myself into the list? So it had an entry "2022, Aaron Rainbolt<EMAIL_ADDRESS>I don't know if I should do that or not.
[19:16] <arraybolt3[m]> I do know that I just added a bunch of stuff into debian/* though.
[19:17] <tsimonq2> arraybolt3[m]: Yes or you can update the Lubuntu entry if there is one
[19:17] <arraybolt3[m]> There isn't one, should I make one?
[19:17] <tsimonq2> arraybolt3[m]: Just track the folder unless you care that deeply about having your name on specific files :)
[19:17] <tsimonq2> arraybolt3[m]: Yeah please
[19:17] <arraybolt3[m]> Nope, don't care. Sounds good. What email do I use for all of "Lubuntu Developers"<EMAIL_ADDRESS>[19:17] <tsimonq2> Lubuntu Developers<EMAIL_ADDRESS>[19:25] <arraybolt3[m]> Simon Quigley (Developer): As for the bit about the as-needed linker flag, libfm-qt uses the same thing in the same spot, so I don't *think* it's a problem. Also, Featherpad installs and launches just fine, so I don't think anything is breaking there.
[19:27] <tsimonq2> However, libfm-qt may present the same flag :) something to dig into and evaluate later
[20:38] <arraybolt3[m]> Simon Quigley (Developer): As far as the man page, I can probably dig into the docs and find out, but if you're there, where in the source code tree of Featherpad would I put a man page?
[20:44] <arraybolt3[m]> Simon Quigley (Developer): I'm realizing it's probably better if I ask tsujan, so nevermind about that last bit.
[20:51] <arraybolt3[m]> https://github.com/tsujan/FeatherPad/issues/660
 featherpad does have featherpad —help
[21:21] <arraybolt3[m]> lynorian: True. The only reason in all the world that a man page would be needed is to comply with Debian policy.
 also someone uploaded a snap version of featherpad that is a bit old of 0.15
[21:39] <arraybolt3[m]> Simon Quigley (Developer): So, I brought up the missing man page to tsujan on GitHub, mentioning that the reason for including a man page was for the sake of Debian policy. He said "If Debian has such a policy, it has two choices: either it doesn't package apps without man pages (bad for Debian), or it makes fake man pages for them (bad for apps). Either way, it doesn't seem rational." He also showed me that both Dolphin and
[21:39] <arraybolt3[m]> Konsole are missing man pages in Arch Linux, and further investigation on my side revealed that they are also missing man pages in Ubuntu Studio 22.04, making me think not all Ubuntu packages need a man page. Should we just override the man page warning, or should I proceed with writing a man page just for our distro?
[21:40] <Eickmeyer> arraybolt3[m]: It's allowed if the application provides its own documentation through another means. In this case, Konsole has documentation via its help pages.
[21:42] <arraybolt3[m]> Eickmeyer: Looking at the Debian policy, it doesn't look like they're happy with just that: https://www.debian.org/doc/debian-policy/ch-docs.html
[21:44] <arraybolt3[m]> But since Featherpad already has documentation in a Help page and via the --help flag on the command line, I'm not sure if it's worth conforming to the policy this time.
[21:45] <arraybolt3[m]> I mean, is it really that big of a deal to be like ' "man featherpad" Oh, there's no man page, ok, "featherpad --help" '?
[21:46] <Eickmeyer> arraybolt3[m]: Others who have been packaging longer than myself have let me know that as long as other documentation exists. Also, you'll notice it's only a "warning", not an error. The warning can be overridden if it's a false positive and other documentation exists elsewhere. https://lintian.debian.org/tags/no-manual-page
[21:47] <Eickmeyer> Check that link, it'll show hundreds of packages without manpages.
[21:47] <arraybolt3[m]> Also, we've been breaking the policy for this long and no one's cared one ounce right up until me because of one Lintian warning, so I don't think throwing a fit about it right now is a good use of resources and time.
[21:48] <Eickmeyer> That particular warning, IME, is not a blocker for a new package.
[21:48] <arraybolt3[m]> Especially not when the package has been in there for years without a man page.
[21:48] <arraybolt3[m]> OK, I'mma override it.
[21:59] <tsimonq2> +1 on rationale, good job working your way through it arraybolt3 @arraybolt3:matrix.org:
[22:04] <arraybolt3[m]> Simon Quigley (Developer): Uhh... how exactly do I add lintian overrides?
[22:04] <Eickmeyer> Also, +1 on using resources.
[22:06] <arraybolt3[m]> Ah, now I'm finding the documentation on it. Never mind.
[22:11] <arraybolt3[m]> (Why do docs sometimes hide until after you've asked a question?)
 arraybolt: not all lintian overrides make sense and overriding some of the lintian warnings is a no-no so you may want simon or i or both to review what lintian tags you are suppressing
 because some should never be suppressed because they legit are problems that need fixed
 (per package policy and such)
[22:31] <arraybolt3[m]> teward001: I'm overriding a missing man page in Featherpad. Me, tsujan, Eickmeyer, and Simon all think it should be overridden.
[22:32] <arraybolt3[m]> teward001: Good point though, I will always keep that in mind.
[22:36] <kc2bez[m]> You could use something like help2man but ultimately if upstream isn't receptive to the idea of a man page I don't know there is much you can do about it. https://www.gnu.org/software/help2man/
[22:39] <arraybolt3[m]> Dan Simmons: That's a good idea if a man page is important, but Featherpad has a Help button built in, there's a --help switch in Featherpad's CLI, and upstream isn't receptive to the idea of adding a man page when there's already documentation. If it's the consensus that we need a man page, I'll write it and we'll maintain it, but I don't think that's really necessary here.
[22:40] <kc2bez[m]> I don't think it is necessary I was only letting you know that it existed.
[22:41] <arraybolt3[m]> Dan Simmons: Good tool to know about! That should save me a lot of time for in the event I do make a man page.
[22:41] <kc2bez[m]> Yeah, exactly.
[23:05] <arraybolt3[m]> How bad is it if I killed an sbuild with Ctrl+C? Will it just reset the chroot, or is this going to produce botched builds now?
[23:05] <arraybolt3[m]> ('Cause I just did that...)
[23:32] <arraybolt3[m]> Simon Quigley (Developer) Dan Simmons Whew! Featherpad packaging complete, it's in the same spot. One last thing I wanted to mention, piuparts fails on every single build, complaining that package purging left some files in the system in /usr/local/share/fonts and /usr/share/fonts. Is this anything to worry about?
[23:40] <arraybolt3[m]> I did forget to do any further looking into the --as-needed linker flag, I just removed it and am attempting a build.
[23:43] <arraybolt3[m]> Ugh, and I made a boffo and ended up not changing the Copyright file (thanks for reminding me Lintian)... so it's not quite done after all. (I was in the middle of fixing stuff and accidentally deleted my whole working directory, had to sync from GitHub again and lost that change on accident.)
[23:48] <arraybolt3[m]> OK, now it's done.
[23:48] <arraybolt3[m]> (I just removed the "-Wl,--as-needed" flag from the rules file, and FeatherPad still built and ran just fine, so I left it that way.)
[23:49] <arraybolt3[m]> * just fine AFAICT, so


[10:59] <user_> hello
[10:59] <user_> i wana ask about something can i ??
[11:01] <user_> is anyone here ??
[11:02] <user_> any way is the ubuntu mobile gona work on the nokia n80 ? or se990i ?


[03:37] <twb> After lines like "You are not the bug assignee nor the maintainer of kvm (Ubuntu), and therefore cannot edit this bug's status."
[03:38] <twb> ...there is a form that appears to allow editing the status
[03:38] <twb> For example on https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936 there are about five of those
[03:38] <twb> Make that 7
[03:39] <twb> Usually when I encounter this kind of thing, it's because the app assumes I'm running a GUI browser with CSS support; this is not the case.
[03:42] <wgrant> That message has been obsolete for, ooh, at least 5 years now. It should only appear when you're not logged in, and it should be hidden under the expanders by default.
[03:42] <wgrant> Is it not?
[03:42] <twb> I'm not logged in, I'm using w3m.
[03:43] <twb> i.e. no CSS
[03:44] <twb> I don't know what an "expander" is; I'm just mentioning that there's like 10 screens of stuff to scroll past before I get to the actual ticket comments, in case 1) you didn't know w3m acts that way; and 2) you care about w3m users
[03:44] <wgrant> Those forms are hidden by default, and largely supplanted by the inline AJAX controls.
[03:44] <wgrant> I don't think we support w3m to any significant extent.
[03:44] <twb> Usually (2) doesn't apply so such reports get WONTFIXed and I don't worry too much because I don't use web apps
[03:45] <twb> If those forms aren't used by anyone anymore because AJAX has replaced them, and they're hidden from normal users anyway, might be worth going through and ripping them all out.
[10:29] <danhg> mrevell
[10:29] <mrevell> Hey danhg
[12:39] <unreg_toto> THanks lifeless , i did it
[16:00] <danhg> Hey, this thing had crashed without me noticing it.
[16:00] <danhg> Are we good to talk now?
[18:50] <micahg> hi, I'm having trouble adding an uploader to a packageset, I get a 401 error
[19:46] <achiang> hello, i experienced a crash in Precise; apport caught it and filed a bug report automatically; i'm noticing that it's private though -- is that correct? (also started here in #launchpad, can ask somewhere else if it's more relevant)
[19:50] <dobey> achiang: yes that's correct; crashes are private by default (in case the core contains private info)
[19:51]  * dobey wonders if there's any way to see all branches for sub-projects of a project group, that are on a specific series
[19:51] <dobey> i suspect not though :(
[19:51] <achiang> dobey: ok, but can an ubuntu developer see it and triage it then?
[19:52] <dobey> achiang: yes; well, anyone in the bug control team i think
[19:52] <dobey> or one of the ubuntu bug related teams, anyway
[19:52] <achiang> dobey: got it, thanks