[00:00] <Daskreech> Anyone tested last nights daily live?
[00:09] <apachelogger> yay
[00:09] <apachelogger> Riddell: I can do audio with vlc backend
[00:10] <Riddell> mm hmm
[00:11] <Riddell> dantti_work: "Remover" -> "Remove" or "Uninstall"
[00:12] <Riddell> maybe that's already translated
[00:12] <Riddell> "Export Installed Package List..."
[00:12] <Riddell> "Install Package from List..."
[01:55] <dantti> Riddell: k, thanks, and yes that was translated... btw after upgrade to qt4.7 kvirc get's dam slow after some time
[04:04] <ScottK> Someone should merge kdelibs from Debian.
[04:04]  * ScottK is far to tired.
[08:46] <debfx> apachelogger: indeed, it needs to pass the -- ... as the last parameter
[08:47] <apachelogger> debfx: I am not sure how we can ensure that
[08:47] <apachelogger> possibly something closer to dh_builddeb
[08:49] <apachelogger> dantti: so, I have a tray item saying there are updates, then I click it and the updater starts, since I just booted I click the check for new updates button, it does stuff and kaboom ... my update list is empty :(
[08:51]  * Nightrose fluffles apachelogger
[08:57]  * apachelogger fluffs Nightrose
[08:57] <apachelogger> so
[08:57] <apachelogger> phonon-gst does srsly nasty shit
[08:57] <apachelogger> and that is responsible for it being the only backend to work with qtwebkit videos
[08:57] <apachelogger> because
[08:58] <apachelogger> in a qtwebkit context the videowidget will not have a parent and without a parent any widget will feel unwilling to paint stuff
[08:59] <apachelogger> phonon-gst is of gst, xine and vlc the only backend to implement logic that allows painting even if no direct parent is available
[09:00] <apachelogger> Nightrose: I fixed phonon-vlc bugs btw :P
[09:01] <Nightrose> \o/
[09:03] <apachelogger> dantti: and the deatils button is broken (it does not do no nothing)
[09:04] <valorie> apachelogger: ALL the bugs?
[09:05] <apachelogger> there are more? :O
[09:05] <valorie> I can recompile and Amarok won't crash anymore?
[09:05] <apachelogger> there is a crash?
[09:05] <valorie> hahaha
[09:05] <valorie> my hopes are dashed
[09:05] <apachelogger> well, I observed a crash indeed when playing a video and quitting rekonq
[09:05] <valorie> crashes on quit
[09:05] <valorie> which is so odd
[09:05]  * apachelogger supposes something does not get cleaned up properly inside the backend
[09:05] <valorie> sometimes, a minute later!
[09:06] <valorie> indeed
[09:06] <apachelogger> valorie: well, amarok takes its time to quit ... which is really the odd thing :P
[09:06] <valorie> saves layout and playlists and such
[09:06] <valorie> right, it's rather pokey
[09:08] <apachelogger> since the layout is only a qbytearray dump and the playlist is probably not 1 million entries long I do not see what takes so long  :P
[09:08] <apachelogger> I mean, clearly it ought to be saving and cleanup and whatnot, but it just seems a bit odd that shutdown would take so long
[09:09] <valorie> some people do have half a million in their playlists
[09:09] <valorie> oddly enough
[09:09] <valorie> and you just can't talk them out of it
[09:09]  * apachelogger is going to buy a dell studio 7 with core i5
[09:09] <apachelogger> valorie: that will never change ^^
[09:09] <valorie> well, mostly they are 16
[09:10] <valorie> and have been "doing that forever"
[09:10] <valorie> so there is hope
[09:10] <apachelogger> no no
[09:10] <valorie> if they grow up
[09:10] <apachelogger> in 5 years time there will be new users who are 16 :P
[09:10] <apachelogger> seee that is the vicious circle of making babies :P
[09:10] <valorie> lol
[09:10] <valorie> by then, maybe they will have discovered dynamic playlists
[09:11] <apachelogger> 5 years ago we told people not to load their entire collection into the playlist
[09:11] <apachelogger> and apparently little changed since then ^^
[09:11] <valorie> or the music will be beamed directly into our brains
[09:11] <apachelogger> valorie: imagine the quality!
[09:11] <valorie> with lasers!
[09:11] <apachelogger> oh
[09:11] <apachelogger> that is certainly unhealthy
[09:11] <valorie> lol
[09:11] <valorie> only if you LOOK
[09:11] <apachelogger> like those radio waves
[09:11] <apachelogger> ~~~~~~ <- radio waves
[09:12]  * valorie shudders in fear
[09:12] <valorie> the fillings in my teeth are picking something up!
[09:12] <apachelogger> oh my
[09:12] <apachelogger> OH MY
[09:12] <apachelogger> phonon is a silly rabbit
[09:13] <apachelogger> also phonon-vlc is a silly rabbit too since I need to jump through a couple of hoops to get thins working
[09:13] <apachelogger> -.-
[09:14] <apachelogger> ah
[09:14] <apachelogger> uh
[09:14] <apachelogger> eh
[09:14] <apachelogger> idea
[09:14] <apachelogger> nastyidea(tm)
[09:14] <valorie> ooo, fun!
[09:17] <apachelogger> oh my lord
[09:17] <apachelogger> badnastyidea(tm)
[09:17] <apachelogger> you know, it is quite mind warping that gst, xine and vlc use commpletely different architectural ways to paint a video
[09:18] <valorie> doesn't diversity make for a strong code base?
[09:19] <valorie> like in nature, you know
[09:19] <apachelogger> not if they need todo the same crap :P
[09:20] <Riddell> apachelogger: spooky enough, in Konqueror the HTML5 video works fine but the audio doesn't appear
[09:20] <apachelogger> uff?
[09:20] <apachelogger> Riddell: with gst?
[09:20] <Riddell> with xine
[09:20] <apachelogger> oh
[09:22] <apachelogger> oh
[09:22] <apachelogger> Riddell: with khtml?
[09:23] <apachelogger> khtml uses Phonon::VideoPlayer I think
[09:23] <apachelogger> whereas qtwebkit use the GUI of webkit and backs it up with a custom combo of Phonon foo for playback
[09:24] <apachelogger> which is the reason the videowidget doesnt have a parent widget ;)
[09:31] <agateau> Riddell: ping
[09:31] <agateau> Riddell: I attached a link to the proposed patch for bug #618727
[09:32] <agateau> Riddell: do you think it can go in?
[09:38] <Riddell> agateau: yes I think it should
[09:38] <Riddell> I can do that later
[09:38] <agateau> Riddell: great
[09:39] <debfx> agateau: does the gnome implementation of statusnotifieritem just ignore setOverlayIconBy*()?
[09:39] <agateau> debfx: yes it does, among other things :/
[09:39] <debfx> so as long as amarok calls setIconByName() once it's fine?
[09:39] <agateau> debfx: yes
[09:40] <agateau> debfx: gnome impl does not support overlay, passing icons by data or tooltips :/
[09:43] <debfx> oh well, at least we can drop the amarok patch with the new beta
[12:05] <apachelogger> dell's website is rather crappy I must say
[12:31] <shadeslayer> apachelogger++
[12:31] <shadeslayer> dell--
[12:36] <shadeslayer> Riddell: did you see new post in rekonq ML ?
[12:37] <shadeslayer> 3 days to FF :P
[12:37] <shadeslayer> 3 weeks to final release of 1.0
[12:37] <Riddell> shadeslayer: not read it yet, but I should yes
[12:43]  * shadeslayer hunts for rekonq bugs
[12:45]  * apachelogger hunts for qtwebkit bugs
[12:46] <apachelogger> Riddell: what do we do about rekonq btw?
[12:46] <apachelogger> people I have talked to all said it was too unstable
[12:46] <apachelogger> and I must agree
[12:47] <Riddell> apachelogger: what problems do you have?
[12:47] <apachelogger> crashingness in general
[12:47] <Riddell> I find it suitably stable now
[12:47] <apachelogger> random crashes, some in flash, some elsewhere
[12:48] <apachelogger> also I find the addressbar very hard to use ... though that might be because I am used too much to chrome
[12:48] <Riddell> the issues I have with it are comments on launchpad bugs giving an error, crash on tags on kubuntu.org, flash creating an empty window
[12:48] <Riddell> the addressbar doesn't update the urlbar if you press the down key, that's been fixed.  I believe the favicons for search engines are being fixed
[12:50] <debfx> Riddell: does rekonq crash when opening http://maps.google.com/ ?
[12:51] <Riddell> nope
[12:54] <Riddell> dpm: translations day on friday?
[12:55] <shadeslayer> apachelogger: works for me too.. ( maps.google )
[12:55] <shadeslayer> and i definitely need to code in ctrl+enter support :/
[12:55] <debfx> for me rekonq crashes on several websites, backtrace is always similar to the one in https://bugs.kde.org/show_bug.cgi?id=247825
[12:56] <shadeslayer> debfx: ill looksie at it
[12:56] <shadeslayer> although i have no video @ youtube... just sound.. i haz the flash
[12:58] <shadeslayer> debfx: try with rekonq 0.5.55
[12:58] <Riddell> he did
[12:59] <shadeslayer> ->fool()
[12:59] <debfx> I even built a new qtwebkit weekly snapshot
[13:12] <dpm> Riddell, I hope yes. I hadn't said anything because I've been trying to start the process to generate a full language pack. Last week there was a problem with the exports and this week there was a bug in LP that has just been cherrypicked today. The full export is running, and should be finished by the end of today or early tomorrow. After that, langpack-o-matic should package the translations and upload the new language packs. Let me re-check with pit
[13:12] <dpm> ti if Friday is still ok or it might be too tight.
[13:13] <shadeslayer> debfx: seems to work for all of us @ #rekonq :(
[13:13] <shadeslayer> any specific steps to reproduce? or just opening maps.google crashes it
[13:16] <Riddell> dpm: ok
[13:20] <debfx> shadeslayer: just opening maps.google.com crashes rekonq
[13:37] <Riddell> debfx: how's the amarok packages doing?
[13:39] <debfx> Riddell: it's ready, I pushed it to bzr and ninjas
[13:40] <Riddell> so what PPA to put it in I wonder
[13:40] <Riddell> Nightrose: when is release due?
[13:41] <Nightrose> Riddell: in a few hours
[13:41] <Nightrose> let's say in around 4 to 5
[13:42] <Riddell> Nightrose: can I upload to our archives now to make sure it's ready in time?
[13:42] <Nightrose> yea
[13:43] <sheytan> Nightrose are you talking about amarok in 4-5h? :D
[13:43] <Nightrose> yes
[13:43]  * sheytan likes new stuff :D
[13:43] <Nightrose> :D
[14:03] <dantti_work> apachelogger: about the systray problem, when the updater opens does it have updates?
[14:03] <apachelogger> dantti_work: aye
[14:04] <dantti_work> is that a yes ?
[14:04] <apachelogger> yes
[14:04] <dantti_work> so, what do you think the problem is?
[14:05] <dantti_work> if when it opened it had updates that's why the systray showed up
[14:05] <dantti_work> after you refreshed the list got empty?
[14:06] <apachelogger> yes
[14:06] <apachelogger> so supposedly the actual list refreshing goes wrong ... because if i close the window and open it again the list is populated properly again
[14:11] <dantti_work> apachelogger: hmm well I've done several changes in kpk that might have fixed that since here it works fine..
[14:12] <dantti_work> apachelogger: can you try building last svn?
[14:13]  * dantti_work refreshed the list several times and still got the updates list..
[14:21] <debfx> shadeslayer: after deleting all rekonq config files, it doesn't crash anymore :o
[14:21] <shadeslayer> :O
[14:32] <fregl> in the ppa with kde 4.5 the qt is missing assistant. that blocks the update in the gui.
[14:37] <amichair> shadeslayer: is the s-p-k fix ok? should I  nudge someone to merge it?
[14:37] <shadeslayer> im yet to check.. i dont know where the frickin deb went
[14:38] <shadeslayer> fregl: free for a folderview patch review?
[14:38] <fregl> folderview? I never touched that stuff
[14:39] <debfx> fregl: what packages depend on it? it has been removed from the qt 4.7
[14:40] <shadeslayer> erm
[14:40] <fregl> debfx: no packages, I had it installed before, so now the upgrade was blocked because it was not available any more I guess
[14:40] <shadeslayer> wrong Frederik i think
[14:40] <Riddell> fregl: libqtassistant has been removed by upstream
[14:41] <fregl> Riddell: upstream... uhh... ok
[14:41] <fregl> well, I just wanted to let you know that for me the upgrade was blocked. doing it the preferred way with aptitude works of course
[14:43] <fregl> for me personally it's no issue, just seems weird
[14:44] <Riddell> fregl: yes, Qt not really keeping to their binary compatibility promises
[14:47] <fregl> Riddell: so the lib is gone, but assistant is still there? ok. I have never even used that thing... still interesting
[14:47] <Riddell> right, it uses the new QtHelp library I think
[14:48] <fregl> ok
[14:49] <debfx> Riddell: do you know if the assistant compat library is abi compatible?
[14:50] <Riddell> debfx: different SONAME I think
[14:50] <Riddell> so we'd need to recompile all the rdepends to support it in lucid, I don't think it's worth it
[14:51] <fregl> Riddell: debfx: is there stuff depending on this lib? is this a real issue?
[14:52] <Riddell> a few scientific apps, presumably you have one installed if your upgrade got blocked
[14:52] <apachelogger> dantti_work: same thing with trunk
[14:53] <dantti_work> hmm weird let me check the code
[14:54] <debfx> Riddell: it has the same soname
[14:55] <JontheEchidna> So, now that install-package is gone it looks like there is nothing keeping gdebi-kde on the CD. However I don't think that aptcc can do .deb installation yet...
[14:55] <debfx> if it is just the code from qt 4.6.3 it should be compatible
[14:56] <Riddell> debfx: mm, I guess you could make symbols files and compare
[14:56] <JontheEchidna> We should probably add it back to the seed, even if gdebi-kde is lacking in maintenance :(
[14:56] <Riddell> dantti_work: aptcc can't do .deb installation?
[14:57] <JontheEchidna> http://simplest-image-hosting.net/jpg-0-plasma-desktopxd1575
[14:57] <dantti_work> Riddell: not yet, as you said you use deb something (fogot the name) I didn't work on adding this
[14:58] <dantti_work> yes gdebi-kde
[14:58] <dantti_work> it's quite complicate to resolve .deb dependencies libapt does not handle that
[14:59] <JontheEchidna> we'll have to add it back to the CD seeds for 10.10. It used to be pulled in as a dependency of install-package, but that's gone now
[14:59] <JontheEchidna> I can get on that
[14:59] <Riddell> thanks JontheEchidna
[15:00] <JontheEchidna> Oh, I'm also giving libdebconf-kde0 a symbols file so that we can build KPK against it
[15:00] <JontheEchidna> well, so that we can MIR it
[15:00] <JontheEchidna> and then get KPK to build against it
[15:01] <Riddell> lovely
[15:08] <ScottK> Testers needed for http://cdimage.ubuntu.com/kubuntu-netbook/lucid/daily-live/current/ - I'll work on it too, but not until tomorrow.
[15:08] <debfx> Riddell: two symbols are missing: _ZGVZ13qvariant_castI8QVariantET_RKS0_E3vid@Base and _ZN5QListI7QStringE13detach_helperEv@Base
[15:09] <dantti_work> apachelogger: can you try applying this patch on KcmKpkUpdate.cpp to see if it fixes your issue?
[15:09] <debfx> they don't appear to be relevant, but i'm not a c++ expert
[15:09] <apachelogger> dantti_work: what patch?
[15:09] <apachelogger> though generally, yes ^^
[15:09] <dantti_work> apachelogger: http://pastebin.com/K913eRwR  oops :P
[15:12] <apachelogger> ...
[15:13] <apachelogger> dantti_work: worky worky
[15:13] <apachelogger> dantti_work: btw, sometimes the "stuff is going on" icon does not go away
[15:14] <dantti_work> apachelogger: hmm well that might be a problem that I have no idea of how to fix that in packagekit-qt
[15:14] <dantti_work> apachelogger: what happens is that QtDBus proxies loose it comunication and don't reconnect again...
[15:15] <apachelogger> that is odd, usually they should just reconnect I think :S
[15:15] <dantti_work> yup, gtk-proxy works :P so they should too
[15:16] <dantti_work> but I need to make sure it's not a missusing
[15:16] <CIA-61> [libqapt] jmthomas * 1164714 * trunk/kdereview/libqapt/utils/qapt-batch/qaptbatch.cpp Mirror InitError handling improvements from Muon in qapt-batch
[15:24] <fregl> hm, 4.5 upgrade went well. except that I ended up not having kdebase-workspace-bin installed, bit unfortunate but probably my bad
[15:26] <debfx> Sput: quassel 0.7 beta has some word-wrap issues, sometimes it puts the last char of a word in the next line
[15:28] <yofel> debfx: known, our qt version is too old
[15:33] <debfx> hopefully they release 4.7 RC soon, this is really annoying
[15:40] <Riddell> fregl: can you install it now?
[15:41] <fregl> Riddell: yeah, it works all fine, it's just that I had kubuntu-desktop not installed, so nothing depended on it. that meant I didn't have plasma...
[15:46] <debfx> Riddell: I tested a package from lucid that uses qt assistant
[15:47] <debfx> it works fine on maverick, do you mind if I add a transitional package?
[15:48] <AnAnt> could someone comment on LP #619073 ?
[15:49] <fregl> debfx: thanks for taking care of that stuff
[15:51] <Riddell> hi AnAnt
[15:51] <AnAnt> Hello
[15:53] <Riddell> AnAnt: I think the patch should be kept, Office is the wrong place for that programme
[15:53] <Riddell> I'll comment
[15:53] <AnAnt> thanks
[15:54] <Riddell> debfx: go ahead
[15:55] <Riddell> debfx: hang on, on maverick?
[15:55] <Riddell> fregl's problem is in lucid
[15:56] <fregl> Riddell: well, I don't have a problem really... you can say people activating the ppa are on their own
[15:59] <alvin> Shouldn't there be a warning about bug 615902 then? (The blocked upgrade) After all, KDE 4.5 is news on kubuntu.org
[16:04] <Riddell> alvin: that bug seems to be a confusion of several issues, many of which should be fixed
[16:06] <alvin> I thought as much. Will these issues be fixed for Lucid as well?
[16:09] <Riddell> alvin: many are fixed I should say
[16:09] <Riddell> qtassistant is the main one left and that's upstream's fault and doesn't affect many people
[16:14] <alvin> Aptitude why (etc...) tells me that libqt4-assistant is installed because of kubuntu-desktop (who recommends printer-applet -> python-kde4 -> python-qt4 -> libqt4-assistant)
[16:19] <Riddell> alvin: python-qt4_4.7.3-1ubuntu2~lucid1~ppa2 from the PPA removes the dependency on libqt4-assistant
[16:21] <dantti_work> Riddell: is that related to qtassistand having a weird style? (seems like a broken CSS)
[16:21] <dantti_work> *assistant
[16:23] <Riddell> dantti_work: I would guess that's related to changes during the porting of qtassistant yes
[16:24] <alvin> Riddell: I was using aptitude... Now I see that apt-get doesn't complain about blocked upgrades anymore. (now trying)
[16:26] <Riddell> Nightrose: is there a release schedule for amarok?
[16:27] <Nightrose> Riddell: final of 2.3.2 at the end of the month - beyond that no
[16:27] <Riddell> that's the version I care about
[16:28] <Riddell> so my thinking is we should clear the beta PPA of the 4.5 betas, put amarok 2.3.2 betas in there for maverick and lucid, when 2.3.2 final comes out we can consider it for feature freeze exception in maverick
[16:28] <Riddell> debfx: how does that sound? ^^
[16:31] <shadeslayer> http://imgur.com/fg1hM : rekonq fix when kget is not installed ;)
[16:31] <debfx> Riddell: sounds good
[16:32] <shadeslayer> now all i have to do is display a Warning there to install KGet
[16:33] <Riddell> "warning, kget can mess with your download experience"
[16:34]  * Riddell has never seen the point of kget
[16:34] <shadeslayer> hehe :P
[16:34] <shadeslayer> Riddell: in the current behaviour you can check those boxes and the user  will think that KGet is already installed
[16:40] <debfx> Riddell: in lucid and maverick so we have a clean upgrade path on both
[16:41] <Riddell> debfx: what what?
[16:41] <debfx> adding a libqt4-assistant transitional package
[16:43] <Riddell> in theory maverick shouldn't need it, the packages will depend on the new package
[16:44] <Riddell> I may be being overly optimistic about apt's abilities though, so yes you may as well
[16:44] <Riddell> debfx: where did debian/patches/kubuntu/08_fix_handbook_install_location.diff comes from?  should it go upstream?
[16:49] <debfx> Riddell: from me, already reported it to Nightrose
[17:09] <eMyller> heua
[17:09] <eMyller> did you see ofirk lately?
[17:13] <Riddell> only briefly late at night
[17:18] <shadeslayer> eMyller: hes not on gtalk as well...
[17:19] <eMyller> i talked to him last night
[17:19] <eMyller> thanks :)
[17:36] <Quintasan> Did someone ping me
[17:36] <Riddell> no but it's nice to have you anyway :)
[17:37] <Quintasan> :O
[17:37] <Quintasan> Riddell: Hi there
[17:38] <neversfelde> oh, feature freeze, why did I missed that :)
[17:39] <neversfelde> any complaints about kdevelop in the backports ppa?
[17:42] <shadeslayer> neversfelde: for mav?
[17:42] <neversfelde> shadeslayer: for lucid
[17:42] <shadeslayer> oh.. who cares about lucid anymore :P
[17:42]  * shadeslayer is all for mav
[17:44] <Riddell> Nightrose: anything I should be doing to put this amarok beta through testing?
[17:47] <sheytan> eMyller he will be here in the next 2 days :)
[17:48] <shadeslayer> apachelogger: lol.. ubuntuone-kde icon fixed its self
[17:50] <Riddell> neversfelde: no complaints so I guess it's all good
[17:51] <neversfelde> great, I uploaded it very early in the morning and went on a vacation after it :)
[17:54] <debfx> is there a schedule for kde 4.5.*?
[17:56] <Riddell> debfx: nope
[17:57] <Nightrose> Riddell: sorry was on the phone
[17:57] <Nightrose> put it trough testing in what sense?
[17:58] <debfx> Riddell: you're right, apt handles the qt assistant transition fine (lucid->maverick)
[18:03] <Riddell> Nightrose: well it's playing music nicely, anything else I should be testing?
[18:03] <Nightrose> Riddell: ah hehe
[18:03] <Nightrose> hmmmm
[18:03] <Nightrose> you have a collection?
[18:03] <Nightrose> and see if last.fm is there
[18:03] <Riddell> I do
[18:04] <Nightrose> ok then you should be ok i think
[18:04] <Riddell> last.fm is there, it successfully tells me I need to pay when I try to play a stream
[18:04] <Riddell> even though I can listen through the lastfm application for free
[18:06] <Nightrose> jep that's supposed to be that way
[18:06] <Nightrose> yay for music industry
[18:07] <Riddell> ooh Amarok Theme is nice
[18:07] <Nightrose> :)
[18:09] <Nightrose> away for a bit
[18:10] <Riddell> Amarok building now in beta PPA for lucid and maverick
[18:10]  * Riddell out for a bit too
[18:12] <shadeslayer> whut theme?
[18:13] <ScottK> shadeslayer: How's kmymoney going?
[18:14] <shadeslayer> ScottK: i contacted debian and they said that i can package it for debian as well, since we have no ubuntu specific changes we can then sync it
[18:14] <ScottK> Great.
[18:14] <ScottK> Speaking of Debian....
[18:14] <ScottK> shadeslayer: kdelibs needs a merge from Debian.  Up for it?
[18:15] <shadeslayer> ill start on it in about 30 mins.. need to finish this report first
[18:15] <shadeslayer> erm.. cant :(
[18:17] <shadeslayer> and now i haz full blown power outage ^_^
[18:21] <shadeslayer> ScottK: can it wait till sunday? :P
[18:21] <ScottK> shadeslayer: Yes
[18:21] <shadeslayer> if its not taken up till then, then ill merge it
[18:22] <nigelb> ScottK: didn't you have intel 855?
[18:22] <ScottK> nigelb: No.  865.
[18:22] <nigelb> ScottK: did you get the normal live cd working?
[18:22] <ScottK> It's also ~100 miles from where I am right now.
[18:23] <ScottK> I didn't try Maverick with it yet.
[18:23] <nigelb> Lucid...
[18:23] <ScottK> It works ~fine on Luicd.
[18:24] <ScottK> It's not as stable as I'd like, but not horrible and kwin compositing even works.
[18:33] <Quintasan> shadeslayer: I can take the merge
[18:33] <Quintasan> ScottK: ^
[18:34] <shadeslayer> sure feel free to
[18:34] <ScottK> Quintasan: Great.
[18:34] <shadeslayer> im overloaded with $WORK :P
[18:42] <nigelb> ScottK: um, I put in lucid, I can't get in.
[18:43] <ScottK> nigelb: 845/855 support is somewhat spotty.  It varies a lot depending on exactly what versions you have.
[18:43] <ScottK> I'd ask in #ubuntu-x.
[18:44] <nigelb> ScottK: I'm running karmic for now.  But its xubuntu and i want to move to kubuntu lucid.
[18:44] <ScottK> Generally Lucid is better for Intel than Karmic (my 865 machine needed some PPA package to work at all on Karmic)
[18:46] <nigelb> What's happening is compiz being enabled by default thingy.
[18:46]  * nigelb needs to sit with this lappy for a day.
[18:46] <nigelb> I'm too busy doing stuff with it to fix it.
[18:46] <nigelb> There is a ppa with a fix.  But I can't get to some place where I can access a terminal to get it.
[18:46] <ScottK> Odd.  kwin is pretty good about shutting itself off if it's causing problem.
[18:47] <ScottK> Boot to rescue mode with networking?
[18:47] <nigelb> I see the plymouth screen and then nada.
[18:47] <nigelb> I thought hat was a windows thing?
[18:49] <ScottK> That's probably X crashing.
[19:26] <apachelogger> Nightrose: Quintasan is treating me badly and threatens me!!!!!!!!!
[19:26] <Quintasan> apachelogger: :<
[19:26] <Quintasan> Trolololololol
[19:27]  * Nightrose looks at Quintasan
[19:27] <Nightrose> you don't do that!
[19:27]  * Nightrose whistles
[19:27] <Quintasan> Who is threatening who apachelogger?
[19:27]  * Nightrose goes back to amarok releasage
[19:27] <Quintasan> Nightrose: but he spams my channel :<
[19:28] <Nightrose> Quintasan: he's apachelogger - he's allowed to do that
[19:28] <Nightrose> (i think)
[19:28] <apachelogger> 90% of the stuff i say is either flood or spam or both
[19:28] <Quintasan> No, they do not make sense
[19:29] <Quintasan> But triggerring a endless loop which resulted in endless repetition of "Hello" is :P
[19:29] <Quintasan> is spam :P
[19:29] <apachelogger> It was not repetition!!!!
[19:29] <apachelogger> it was variation thereof
[19:30] <Quintasan> But the sense was the same
[19:30] <Quintasan> :P
[19:30] <Quintasan> apachelogger: doesn't matter now, get back in there or no cookies and fame for you
[19:30] <Quintasan> ;)
[19:31] <apachelogger> I do not need no cokies nor fame no more
[19:31] <apachelogger> soon I will get my own documentary film
[19:31] <Quintasan> Oooh? :>
[19:32] <apachelogger> hmmmmmhmmmmmmhmmmmmm
[19:32] <Quintasan> No cookies, are you really sure?
[19:32] <apachelogger> now I wonder how rekonq worked before todays upgrade
[19:32] <apachelogger> odd enough
[19:32]  * Quintasan takes the tray with cookies from kubotu as soon as he arrives
[19:32] <apachelogger> kubotu has a sekrit warehouse
[19:32] <apachelogger> no dice getting there
[19:32] <apachelogger> we tried
[19:32] <apachelogger> he apparently has endless supplies of beer there
[19:32] <apachelogger> which is a very good reason to try getting there
[19:33] <Quintasan> No wonder you are sometimes not making any sense :P
[19:33] <apachelogger> it is just because I am so old and wise
[19:33] <Quintasan> >wise
[19:33] <apachelogger> I have seen you cannot even imagine
[19:34] <Quintasan> I will keep diplomatic silence here
[19:34] <apachelogger> Nightrose: phonon is made out of madness, I demand insanity to go to war with phonon!
[19:35] <Nightrose> aiai
[19:35] <Quintasan> Therefore I herby delegate apachelogger to declare war on Phonon
[19:35] <Quintasan> apachelogger, I bestow upon you the title of Warrior of Insanity!
[19:36] <apachelogger> hm
[19:36] <debfx> make love, not war!
[19:36] <apachelogger> one can say about gst a lot of things
[19:36] <apachelogger> but it certainly supports a shitload of codecs
[19:36] <Quintasan> +1 on that
[19:36] <Quintasan> debfx: It's not possible with Phonon
[19:37] <Quintasan> Phonon has crossed the line of madness long ago
[19:37] <apachelogger> what the firefly
[19:38] <apachelogger> why do I have a billion ~/.cache/virtuoso_*.ini files?
[19:38] <apachelogger> and what are they
[19:38] <apachelogger> and why do they not get cleaned up
[19:38] <apachelogger> and why and when and where
[19:38] <Quintasan> Trollmachine
[19:38] <Quintasan> apachelogger: ^
[19:39] <apachelogger> QStateMachine ftw!
[19:39] <debfx> do you seriously expect virtuoso to just work?
[19:39] <Quintasan> debfx: +1
[19:40] <apachelogger> I expect it to not take a dump in my .cache dir and then not clean up
[19:41] <Quintasan> What you expect and what takes place are usually two different things
[19:41] <apachelogger> clearly
[19:41] <apachelogger> because
[19:42] <apachelogger> #fail
[19:43] <Quintasan> Well, do not blame me for that. I did not invent Virtuoso
[19:44] <Quintasan> Nor did I invent that stupid indexing in KDE
[19:44]  * shadeslayer has met one of the co-contributors of Nepomuk
[19:45] <shadeslayer> he said its going to improve lots
[19:45] <shadeslayer> lets see :P
[19:45] <Quintasan> I'm eagerly awaiting it to do so
[19:58] <yofel> txwikinger: still have bug 449252 ? I haven't seen that in quite a while
[19:58] <neversfelde> so Natty Narwhal ?
[19:59] <yofel> wtf?
[19:59] <yofel> https://bugs.edge.launchpad.net/ubuntu/+source/apport/+bug/449252
[19:59] <maco> google define:natty tells me it means dapper or jaunty
[19:59] <maco> i wonder if sabdfl is having fun with a thesaurus
[19:59] <maco> yofel: i havent seen it in a while either. it used to spawn 70-200 processes for me
[20:00] <sabdfl> heh. it's wild over here in the isle of man :p
[20:01] <yofel> maco: right, for me too, but it behaves good since  a while ago, so if possible txwikinger should close the bug
[20:02] <nigelb> sabdfl: haha.
[20:03] <txwikinger> yofel: I don't remember. Have to look in the details. I have a couple of bugs spawning lots of processes
[20:06] <txwikinger> Ah that one... Haven't seen it for a while.. and it was a karmic beta
[20:23]  * txwikinger subconscience is still trying to find the association between the Isle of Man and a thesaurus
[21:10] <dantti_work> kdeinit4 is the one that calls kded isn't it?
[21:40] <apachelogger> dantti_work: calls?
[21:40] <apachelogger> dantti_work: you mean starts?
[21:40] <fdo> hello
[21:40] <apachelogger> yo fdo
[21:40] <dantti_work> apachelogger: yup
[21:40] <apachelogger> dantti_work: yeah, that is kdeinit4
[21:41] <fdo> hi i have questions about the kde pythin bindings
[21:41] <dantti_work> it seems so, it's just that a kpackagekit bug report was on kdeint4 but looking at the top of the report I saw kded...
[21:41] <dantti_work> thanks btw
[21:42] <fdo> is anybody here who is familiar with this?
[21:42] <Riddell> ** testers needed for Amarok beta, maverick and lucid https://edge.launchpad.net/~kubuntu-ppa/+archive/beta
[21:42] <fdo> pythin -> python
[21:42] <Riddell> fdo: go ahead and ask
[21:43] <fdo> i want to write a kio but i cant find any tutorial for kde4
[21:43] <fdo> hi Riddell
[21:44] <fdo> Riddell: the tutorials on the kde sides (and python) are for kde3
[21:44] <Quintasan> Riddell: is lichts still available?
[21:44] <Riddell> Quintasan: it got reinstalled for lucid.1 testing, I can turn it back on if you need it
[21:44] <Quintasan> Riddell: would be nice, I want to copy some recipes over
[21:44] <Riddell> fdo: I don't know I'm afraid, quite possibly that never got ported to KDE 4
[21:45] <Riddell> fdo: pykde maintainer sime isn't on the channel, so I think you need to ask on the kdebindings mailing list
[21:45] <Riddell> Quintasan: what was your user name?
[21:45] <Riddell> or what user name would you like?
[21:45] <fdo> ok thanks on the kde sides this irc is on top :o)
[21:46] <fdo> Riddell the maintainers name is sime?!
[21:46] <Quintasan> Riddell: my username was michal
[21:46] <Riddell> fdo: that's his irc nick
[21:46] <Quintasan> it could be quintasan now :P
[21:46] <fdo> Riddell: thanks ... Have a nice day!
[21:47] <maco> fdo: my experience with pykde & pyqt is that docs are few and far between, and the thing to do is read the normal C++ docs then mentally translate them to python syntax since the APIs are the same
[21:47] <fdo> hi maco
[21:48] <fdo> maco: i have read (the last 2 weeks) all i could find, but i dont know how i compile my script
[21:48] <fdo> marc: the tutorial was for kde3
[21:48] <Riddell> Quintasan: she's up
[21:48] <Quintasan> thx
[21:49] <maco> fdo: better off using a c++ kde4 one as itll at least have the right function names and such
[21:49] <maco> s/one/tutorial/
[21:49] <Quintasan> Riddell: username is michal, right?
[21:50] <Riddell> Quintasan: yes, with quintasan@nightwalker ssh key
[21:50] <fdo> maco: i found a blog entry from the rubby side ... and he is used exec=krubypluginfactory
[21:50] <Quintasan> huh
[21:50] <Quintasan> it asks me for password
[21:50] <maco> fdo: to run a python script you just type "python" before its name
[21:50] <fdo> maco: im not good at cpp
[21:51] <fdo> :o)
[21:51] <maco> fdo: im not saying /write/ c++, i'm saying /read/ it and use it to write python
[21:51] <fdo> maco i want to use it as a kio
[21:51] <maco> i dont know any C++ but thats how ive done all the pykde ive had to do
[21:52] <maco> tutorials for pykde4 are not common. you need to just look at normal, c++ kde4 examples and docs, then mentally turn it into python
[21:52] <fdo> i had written my class and all needed functions and now i know how to place the files but how do i compile this ...
[21:52] <maco> you dont compile python
[21:52] <maco> its interpretted
[21:52] <fdo> i have seen on kde3 ... they use make
[21:52] <maco> (ok so it has a JIT compiler, but since its JIT you can ignore it)
[21:53] <maco> makefiles can do ANYTHING
[21:53] <maco> they're /just/ scripts
[21:53] <fdo> yes i know but how does kde use it
[21:53] <maco> in kde4 land, CMake is used instead of autotools
[21:54] <maco> and im really not sure what the point is in a python app. the only use ive had for distutils (python's setup.py stuff) is in cases where i had a .ui file to compile to a .py file for a gui, but you wont have that for a kio
[21:54] <fdo> maco: this is my first step -> http://www.arnorehn.de/blog/2010/07/and-the-bindings-keep-rocking-writing-ruby-kio-slaves/
[21:55]  * maco didn't think anyone really used ruby on the desktop
[21:55] <fdo> i reimplemented it in python but: exec=krubypluginfactory didnt work
[21:55] <maco> of course not, thats for ruby...
[21:55] <maco> alexandria (book organiser for gnome) is the only thing ive seen done in ruby, and it crashes *constantly*
[21:55] <fdo> sorry yes
[21:56] <fdo> is used exec=kpythonpluginfactory ;0)
[21:56] <fdo> /usr/lib/kde4/kpythonpluginfactory.so
[21:57] <Quintasan> Riddell: bingley bingley beep, check priv :)
[21:58] <Riddell> yo
[22:00] <fdo> Riddell: the kde bindings channel ist #pyqt?
[22:00] <fdo> Riddell: on freenode
[22:02] <fdo> Riddell: i found it myself
[22:02] <fdo> thanks


[01:06] <epk> I'm trying to copy packages in my ppa from xenial to trusty and getting this error: commons-daemon 1.1.0-0ppa2 in xenial (same version already has published binaries in the destination archive)
[01:06] <epk> Do I need to make a second ppa?
[01:06] <epk> https://launchpad.net/~epkugelmass/+archive/ubuntu/jsvc/+packages
[01:19] <epk> my google foo was weak: https://bugs.launchpad.net/launchpad/+bug/330711
[18:36] <kyrofa> My snap builds have been revoking the proxy token for a half hour now, is something wrong?
[18:51] <kyrofa> There, finally done. Huh


[08:29] <acheron_uk> KCI fell off it's perch? I notice even it's channel bot has timed out.
[10:39] <BluesKaj> Hiyas all
[10:54] <clivejo> acheron_uk: looks like its totally dead
[10:55] <clivejo> starbuck1: is http://kci.pangea.pub offline?
[11:00] <starbuck1> clivejo: i see, it is reported running normal, but maybe something on the server got stuck
[11:00] <starbuck1> will reboot
[11:00] <clivejo> is the www interface responding for you?
[11:01]  * clivejo cant be sure its not his rubbish internet
[11:07] <starbuck1> comes up now after boot: http://kci.pangea.pub/
[11:08] <clivejo> nice one, thanks starbuck1
[11:11] <clivejo> thats one way to have it quiet for a day!
[11:13] <lordievader> Good afternoon
[11:14] <clivejo> hi lordievader
[11:14] <clivejo> acheron_uk: can you fix this one - https://launchpadlibrarian.net/262024669/buildlog_ubuntu-xenial-amd64.artikulate_4%3A16.04.1+p16.04+git20160528.0025-0_BUILDING.txt.gz
[11:15] <lordievader> Hey clivejo, how are you?
[11:16] <clivejo> lordievader: Im good thankyou
[11:16] <clivejo> and you?
[11:16] <lordievader> Doing good here too :D
[11:18]  * clivejo wonders why he gets a spam email every day from West Elm in brooklyn, ny
[11:22] <acheron_uk> clivejo: I'll have a look later :)
[11:23] <clivejo> Ill go ahead and fix it
[11:23] <clivejo> might as well use this chance to fix stuff when KCI is quite
[11:24] <clivejo> quiet
[11:24] <acheron_uk> no probs. I'll look at the log later, decide what I would do, then have a look to see what you actually did
[11:39] <clivejo> looks like I wont be able to use it
[12:10] <acheron_uk> clivejo: ok. adding that dep is what I concluded
[12:12] <acheron_uk> the kicker patch in kubuntu_stable (and merged since into unstable) now causes both to fail on KCI as is already applied upstream
[12:13] <acheron_uk> does that get reverted/removed? or does it have to stay somewhere as is still in theory valid for 5.6.4 (e.g backports ppa)?
[12:27] <acheron_uk> on artikulate, still fails as looks like they switched backends so qtgstreamerbackend.so is no longer being built
[12:27] <acheron_uk> https://quickgit.kde.org/?p=artikulate.git&a=commitdiff&h=88df2ed701d5cbf6106adf509c5a26132c51f267&hp=c759fb95a6f6c119872cd84b29a8511531d6db7f
[13:24] <sitter> maxyz: https://todo.kde.org/?controller=board&action=show&project_id=97
 Acheron_uk that's why we need branches
 They track the different archives and ppas
[18:43] <acheron_uk> yes, I get that
[18:49] <Niklas__> hey
[18:51] <acheron_uk> clivejo: but rather defeats the point if it is put into the stable branch to fix 5.6.4 in the ppa, and then that stable branch is merged with stable/unstable, and KCI pulls from both of those resulting in broken builds since it has been patched upstream
[18:52] <clivejo> stable should be 5.6.4
[18:52] <clivejo> unstable is git master
[18:59] <acheron_uk> clivejo: KCI stable is the upstream stable + and changes in their git that will be the next stable point release, yes?
[19:02]  * jimarvan waves
[19:04] <clivejo> acheron_uk: sounds right
[19:04] <clivejo> what was the package needs the patches removed?
[19:04] <clivejo> hi jimarvan
[19:06] <acheron_uk> clivejo: ah. I think I was getting the 2 patches you applied for me mixed up. they have such similar messages when just looking at the log, I thought the 1st had been applied in both when it really wasn't
[19:08] <clivejo> if and when the patch is applied upstream, it needs to be removed from unstable for it to build properly
[19:08] <acheron_uk> yep
[19:09] <acheron_uk> that fact was never unclear
[19:09] <clivejo> KCI is to try and give us a head start with upcoming changes
[19:09] <clivejo> so we can package them as the changed happen
[19:10] <clivejo> but its like a stack of cards
[19:11] <clivejo> if something breaks low down, the whole lot comes tumbling down!
[19:11] <acheron_uk> yes, I realised that from the start. all filters down in the end meaning if you keep on top of that, your eventual job packaging for the real distro/paas will be much easier
[19:12] <acheron_uk> ha. I like the pack of cards comparison
[19:13] <clivejo> and then LP issues dont help either
[19:14] <acheron_uk> not sure, but looked from the logs the LP went AWOL for a short time in the wee hours last night
[19:15] <clivejo> ah
[19:16] <clivejo> kio seems to be looking for the packaging on debian - git.debian.org:/git/pkg-kde/frameworks/kio
[19:20] <acheron_uk> xenial_stable_plasma-desktop was failing on 'upstream_include_cmath_c++_fix.diff' http://kci.pangea.pub/job/xenial_stable_plasma-desktop/65/console
[19:21] <acheron_uk> 'Reversed (or previously applied) patch detected!  Skipping patch.'
[19:27] <acheron_uk> and similarly xenial_stable_plasma-desktop if failing on 'upstream_fix_kicker_recent_documents.diff' as that is upstream
[19:29] <acheron_uk> it was those 2 I was getting mixed up earlier, switching between multiple browser tabs
[19:32] <acheron_uk> ^^^ I mean UNsnable on the 2nd of those FFS. lol
[19:33] <acheron_uk> or even *UNstable
[19:33] <acheron_uk> http://kci.pangea.pub/job/xenial_unstable_plasma-desktop/141/console
[19:57] <acheron_uk> also I don't get the logic of this merge https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/plasma-desktop/commit/?h=kubuntu_unstable&id=59ebd3a35fc8d2f56dea7758325bfcc79d6989de
[19:58] <acheron_uk> as it took that patch into unstable where it wasn't needed and would conflict
[20:01] <sitter> it doesn't know that
[20:02] <acheron_uk> I gathered now
[20:14]  * acheron_uk should pay more attention to origin of the merge messages
[20:28] <acheron_uk> at least I can see what has happened and why now
[20:29]  * acheron_uk hits git with a quantum physics textbook
[20:30] <acheron_uk> both confusing
[20:37] <clivejo> I need to learn how to work CI
[20:41] <acheron_uk> you have access now?
[20:51] <clivejo> not sure
[20:51] <clivejo> yofel added me to something
[20:52]  * clivejo doesnt feel well
[20:52] <clivejo> there weather feels so heavy and humid
[20:53] <jimarvan> where? :)
[20:53] <clivejo> here
[20:53] <jimarvan> ah
[20:53] <clivejo> my head feels like its gonna explode
[20:54] <jimarvan> same here, cant see after 5 meters, too dense fog
[20:54] <jimarvan> thank god for champions league :P
[20:55] <clivejo> a good storm would clear the air, but I doubt that as my neighbour is cutting sillage
[20:56] <acheron_uk> I saw you got added to the kubuntu-kci-gods team whatever that is
[20:57] <clivejo> yeah, I got an email about that
[20:57] <acheron_uk> warm/humid here as well, but so far so good
[21:00] <clivejo> cant seem to hold a train of though
[22:45] <clivejo> valorie: did you install apps 16.04.1?
[22:53] <DarinMiller> clivejo: I have apps staging enabled on YY, running updates now.  What would you like me to check?
[22:53] <clivejo> just check it installs and the apps work as expected
[22:54] <clivejo> Im having issues with korganizer
[22:54] <clivejo> and not having any luck finding someone to answer my bug report
[23:01] <valorie> oh, lemme start up my old laptop
[23:01] <valorie> got caught up in genealogy.....
[23:03] <valorie> the mysteries of the past are easier than those of the present, sometimes
[23:06] <clivejo> I cant settle my head to the past or present
[23:09] <DarinMiller> korganizer not installed, unmet depends libkf5calendarsupport5  + 6 other pacs.
[23:10] <clivejo> can you pastebin the output#
[23:14] <darin> clivejo: https://paste.kde.org/ph3utetaw
[23:15] <clivejo> do you know which of those it is having the problems with
[23:16] <DarinMiller> how do I check?
[23:18] <clivejo> see what it says when you try to install each of the ones its complaining about
[23:19] <clivejo> see if you can whittle it down to one problem package
[23:19] <darin> trying now...
[23:26] <valorie> hmmm, this old lappy doesn't want to boot into plasma
[23:26] <valorie> I haz tty....
[23:28] <valorie> at least tty6
[23:29] <valorie> trying again
[23:32] <valorie> nope, only tty6
[23:32] <valorie> it doesn't seem to be online
[23:33] <valorie> not sure how to proceed, actually
[23:35] <valorie> wire works, at least
[23:36] <valorie> so I'll finish upgrading, then add back staging-plasma, then try staging-apps or whatever it's actually called
[23:45] <valorie> yay I have plasma back
[23:45] <valorie> I think
[23:46] <valorie> nope, starts but never lets me login
[23:46] <valorie> just gray
[23:46] <acheron_uk> I 'll try in a YY VM tomorrow if it'll help
[23:47] <valorie> now I get tty 1-6
[23:47] <valorie> no clue what to do next....
[23:48] <valorie> startx still gray
[23:49] <DarinMiller> valorie, had same issue the other day.  Packages moved around and I had to install all 3 staging PPA's followed by updates to make everything work.
[23:49] <DarinMiller> is your network up in your tty?
[23:50] <valorie> wire is
[23:50] <valorie> no wifi
[23:51] <DarinMiller> ensure apps, FW and plasma ppa are enabled, run updates and plasma should start after that.
[23:52] <valorie> thanks, DarinMiller, trying that
[23:52] <valorie> now dist-upgrading
[23:54] <valorie> and rebooting
[23:56] <valorie> nope, no plasma
[23:57] <darin> Ok I have tried installing everything that pops up and summarize the trail here: https://paste.kde.org/p2l3dcmmy
[23:58] <clivejo> ah!
[23:58] <acheron_uk> DarinMiller: you may need to enable proposed to get libical2
[23:58] <clivejo> darin: libical2 is in proposed
[23:58] <acheron_uk> had that the other day
[23:58] <clivejo> me too, and totally forgot about it


[00:52]  * TheMuso is finding it difficult to work out why someone who wrote a packaging patch for a debian package decided to remove a .install file and use dh_install calls in debian/rules instead...
[00:52] <TheMuso> Baffling.
[00:58] <RAOF> Even well-understood magic can be, well, magic, I guess.
[01:01] <TheMuso> Yeah, but I would have thought creating a new install file for the newly created binary package would be easier.
[05:43] <pitti> Good morning
[05:48] <TheMuso> Hey pitti.
[07:17] <astropirate> Anyone know if the gnome3-team PPA is working?
[07:17] <astropirate> i mean stable
[07:17] <astropirate> *enough to use
[07:20] <TheMuso> From what I've heard, yes it is, but I haven't used it myself.
[07:20] <vish> !gnome3 | astropirate
[07:20] <ubot2> astropirate: Gnome 3 is not currently supported on Ubuntu. A PPA for natty is available at https://launchpad.net/~gnome3-team/+archive/gnome3 but these packages are EXPERIMENTAL and UNSTABLE, will break Unity and possibly other parts of your system, and safe downgrading is not possible.
[07:22] <astropirate> i don't care about unit. it is buggy
[07:22] <astropirate> *unity
[07:22] <vish> astropirate: also mentions "… and possibly other parts of your system," so use it at your own risk ;)
[07:23] <astropirate> hehe i plan to
[07:23] <astropirate> but just wanted to know if others had allready risked and if it had worked
[07:24] <vish> astropirate: you'd have better luck about that question on #ubuntu …
[07:25] <astropirate> vish ok, thanks
[07:25] <vish> yw..
[07:28] <jbicha> I use the gnome3 PPA but I don't recommend others do
[07:38] <astropirate> i tink this is the perfect opertunity to try other distros :D
[07:38] <astropirate> expanding horizons and all that junk
[07:39] <chrisccoulson> good morning everyone
[07:39] <vish> the world is your oyster!
[07:39] <TheMuso> Hey chrisccoulson.
[07:39] <chrisccoulson> hi TheMuso, how are you?
[07:39] <vish> morn chrisccoulson …
[07:39] <TheMuso> chrisccoulson: Not too bad thanks, just starting to get final bits and pieces together for my trip to UDS.
[07:43] <pitti> hey chrisccoulson
[07:43] <pitti> TheMuso: good luck!
[07:43] <chrisccoulson> hi pitti, how are you?
[07:43] <chrisccoulson> TheMuso, when do you travel?
[07:43] <pitti> chrisccoulson: splendid, thanks! slowly getting used to getting up at 6
[07:43] <chrisccoulson> i'm going to be a fairly late arriver, i don't travel until sunday :)
[07:44] <TheMuso> pitti: Thanks, there is a little bit of luck involved I guess.
[07:44] <TheMuso> chrisccoulson: I fly out tomorrow afternoon my time.
[07:44] <TheMuso> In less than 24 hours to be exact.
[08:55] <rodrigo_> morning
[08:59] <pitti> hey rodrigo_
[08:59] <rodrigo_> hi pitti
[09:28] <cdbs> Umm, is the Software Center 'reviews' server down?
[09:28] <cdbs> mpt: ^^
[09:45] <mpt> cdbs, works for me
[09:45] <mpt> http://www.downforeveryoneorjustme.com/reviews.ubuntu.com
[09:48] <pitti> o_O is there _anything_ the internet doesn't provide?
[09:48] <pitti> hah, http://iamboredandhavenothingtodo.com/ doesn't exist; quickly, point it to https://wiki.ubuntu.com/ContributeToUbuntu!
[09:58] <abhinav-> pitti: is there a gir for xlib as well ?
[09:59] <pitti> abhinav-: not an usable one, I think; /usr/share/gir-1.0/xlib-2.0.gir merely provides some struct names and open_display
[09:59] <pitti> abhinav-: use python-xlib for this
[09:59] <pitti> (static binding)
[09:59] <abhinav-> ah thanks
[10:01] <abhinav-> pitti: in gtk2 this feature could have been added without any unnecessary extra dependencies but with gtk3 the list is mounting up and still no success :-/
[10:02] <pitti> abhinav-: at this point you should perhaps file an upstream bug with the requirements and point out the lost API?
[10:02] <abhinav-> pitti: yeah. good suggestion. I cannot find any work around now :(
[10:03] <pitti> or gnome-screenshot should just be taught to give you the XID/pid
[10:03] <pitti> abhinav-: sorry for all the trouble..
[10:04] <abhinav-> pitti: yeah, it could be added to gnome-screenshot but it will add dependency on cairo and that will have to be done in C :-|
[10:05] <abhinav-> pitti: no problem, its just that every morning I feel like I could do it today :P
[10:05] <pitti> heh
[10:35] <cdbs> chrisccoulson: The globalmenu extension in oneiric Thunderbird doesn't hide up the old-style menubar from the window
[10:48] <cdbs> didrocks: hello there! Could you take a look at https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-default-apps-unity-integration ?
[10:49] <didrocks> cdbs: hey Bilal! sure having a look :)
[10:49] <didrocks> cdbs: is that something you want to work on?
[10:50] <cdbs> didrocks: yep, but others could pick up just as well.
[10:50] <cdbs> didrocks: We need to decide which app needs what
[10:50] <cdbs> didrocks: and there are a ton of non-default-but-immensely-popular apps which could do with integration as well.
[10:50] <cdbs> all that has to be decided
[10:51] <cdbs> didrocks: So if you say so, I'll set assignee to myself
[10:51] <didrocks> cdbs: ok, I'll ensure we have a designer coming and that it's scheduled then :)
[10:51] <didrocks> cdbs: sure ;)
[10:51]  * cdbs sets
[10:51] <cdbs> done
[10:51] <didrocks> pitti: hey, can you approve this one, please? ^^
[10:52] <cdbs> didrocks: its approved already
[10:52] <cdbs> pitti: ^
[10:52] <cdbs> pitti: oh no wait, it isn't
[10:52] <didrocks> no, it's still "proposed"
[10:53] <didrocks> I'm subscribing Jorge as well as we will need some community advocacy as well
[10:53] <cdbs> exactly
[10:54] <cdbs> Weird that the assignee would be attending remotely :(
[10:54] <pitti> not "proposed" any more :)
[10:54] <pitti> bonjour didrocks
[10:54] <cdbs> didrocks: Enjoying Budapest? How's the whether there?
[10:54] <didrocks> pitti: Guten Tag! ;)
[10:54] <cdbs> pitti: Good morning , and thanks :)
[10:55]  * cdbs should *seriously* learn french
[10:55] <didrocks> cdbs: well, depends, one day, it's a london weather, the other day it's really sunny ;)
[10:55] <didrocks> some kind of flip/flap :)
[10:55] <didrocks> cdbs: yeah, this is mandatory! :p
[10:55] <pitti> for now I should seriously learn some Hungarian phrases
[10:56] <didrocks> pitti: the "Sorry, I don't speak Hungarian" one? :-)
[10:56] <didrocks> pitti: thanks for acking!
[10:56] <cdbs> pitti: Fire up google translate and translate that :)
[10:57] <pitti> "Elnézést, én nem beszélek magyarul!", ugh
[10:57] <pitti> at least the pronounciation seems to be pretty straightforward
[10:58] <seb128> does it? ;-)
[10:58] <cdbs> it is, just read it like one reads English
[10:58] <cdbs> :)
[10:58] <pitti> cdbs: exactly not -- English pronounciation is horribly inconsistent
[10:59] <pitti> German, Russian, Hungarian etc. have strict rules, you pronounce as you write
[10:59]  * pitti tries to remember "Szeretnék két sört" (two beer please)
[11:00] <Laney> I like your style — no need to ever order just one ;-)
[11:02] <cdbs> sudo dd if=/dev/beer of=/home/pitti/glass{1,2} count=2048  # That's the unified way of saying that, no language barriers :)
[11:03] <pitti> why sudo?
[11:03] <pitti> access to beer should be fairly public!
[11:03] <cdbs> oops
[11:03] <Laney> requires administrator access to your body
[11:03] <Laney> aka adulthood
[11:04] <pitti> heh
[11:07] <jbicha> use sudo when you really want to make sure something gets done
[11:07] <jbicha> -f helps too :-)
[11:08] <pitti> one day I want a T-Shirt with http://xkcd.com/149/
[11:08] <davmor2> is there a way to make unity show up in the share my desktop feature on empathy?
[11:09] <jbicha> pitti: oh you mean like this one? http://store.xkcd.com/xkcd/#Sudo
[11:09] <pitti> right
[11:10] <jbicha> but you want someone else to buy it for you? lol
[12:03] <hyperair> does anybody know if we're moving to gtk3 in oneiric?
[12:22] <pitti> hyperair: yes, we will
[12:22] <hyperair> pitti: okay, awesome.
[12:23] <pitti> gets high time to do so :)
[12:23] <hyperair> yeah
[13:27] <ricotz> jbicha, ping
[13:29] <ricotz> jbicha, regarding the gnome-session 3.0.1 merge, what is the reason for dropping debian/po-up/de.po?
[13:44] <cyphermox> good morning!
[13:53] <pitti> hey cyphermox
[13:53] <cyphermox> hey pitti
[14:08] <cyphermox> hey piiti, I seem to have a bug 776662 here that mentions an possible issue with gnome-panel ...ubuntu6.5; would make that system crash. any ideas how/why this would be?
[14:08] <ubot2> Launchpad bug 776662 in network-manager-applet "network-manager-gnome crashes on logon after the last update" [Medium,Incomplete] https://launchpad.net/bugs/776662
[14:12] <pitti> cyphermox: oh, that was for me
[14:12] <pitti> cyphermox: ah, so presumably a regression from the SRU in bug 774427?
[14:12] <ubot2> Launchpad bug 774427 in gnome-panel "Cannot add applets to second X server display in 11.04" [Low,In progress] https://launchpad.net/bugs/774427
[14:13] <cyphermox> maybe
[14:13] <pitti> cyphermox: is it reproducible? I didn't try classic session recently
[14:13] <cyphermox> I was about to try, but I doubt I'll be able to reproduce it
[14:13] <pitti> I'd like to defer to rodrigo_ here, I need to leave now
[14:13] <cyphermox> sure
[14:13] <pitti> see you all in Budapest!
[14:13] <cyphermox> see you there!
[14:59] <jbicha> ricotz: oops, that wasn't intentional
[15:00] <jbicha> I'm not really sure why that file would have been cleared on my computer; I had no reason to be touching the pos
[15:01] <ricotz> jbicha, i see ;), do you want to propose a fix or shall i just add it back?
[15:02] <jbicha> I can propose a merge for you
[15:02] <ricotz> alright
[15:14] <rodrigo_> I have to do some stuff for my trip to budapest, so if I'm not back later, see you all in budapest!
[15:17] <jbicha> ricotz: thanks for letting me know
[15:17] <cyphermox> rodrigo_: alright ;)
[22:24] <bigon> what are the plan for gnome-shell and oneiric?
[22:51] <kenvandine> bigon, we will be talking about that at UDS
[22:51] <kenvandine> but we are expecting to have gtk3 and gnome3 in some fashion for oneirc
[22:52] <bigon> alright
[22:52] <kenvandine> but that isn't finalized or anything, just what we know we want to do
[22:54] <bigon> ok ok
[23:11] <bcurtiswx> bigon, do you know if cassidy is going to UDS?
[23:15] <bigon> bcurtiswx: good question, I know he's going to the guadec, but I'm not sure about UDS
[23:16] <bcurtiswx> bigon, OK thanks :)
[23:19] <bigon> this make me think that I should take vacations to go to the guadec


[05:29] -queuebot:#lubuntu-devel- Unapproved: lubuntu-installer-prompt (noble-proposed/universe) [24.04.5 => <IP_ADDRESS>] (lubuntu)
[12:22] <mkukri> hello, i am investigating LP: #2060624 , and i do wonder, in the calamares based installer, what is/should be responsible for configuring grub-pc/efi's debconf entries during/after installation
[12:22] -ubottu:#lubuntu-devel- Launchpad bug 2060624 in grub2 (Ubuntu) "lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice" [Undecided, New] https://launchpad.net/bugs/2060624
[12:23] <mkukri> subiquity has logic to this itself, and there is also a cloud-init module that suppossed to do this (although it's less complete and more buggy)
[12:24] <mkukri> s/subiquity/curtin in this case just be clear, it applies to both desktop isntaller and server one
[12:34]  * guiverc can't help there sorry.. you need a developer.    I did get same response on ubuntu-desktop-installer (xubuntu) BEFORE the format was forced.
[12:59] <mkukri> than this issue might strictly be unrelated but it seems like calamares based ubuntu installs do not fill the grub-pc/efi debconf fields correctly
[13:12] <mkukri> interestingly grub2/enable_os_prober is still false in debconf, even in installations were the alternative OS shows up in the menu
[13:14] <mkukri> hmm in fact regenerating grub debconf with update-grub after the os booted reproduces the bad behavior
[13:41] <mkukri> guiverc, i seem to have reproduced this on the desktop installer too, and i have a hunch what's going on but i am gonna do a few more tests before proclaiming it for sure
[14:03] <guiverc> :|  at creating it with ubuntu-desktop-installer (I like confirmation of what i experiened, but :( at it still being possible as the forced-format b/c of another issue I thought prevented it appearing with ubuntu-desktop-installer...
[14:04] <tsimonq2> mkukri: There's debconf prompts for that?
[14:05] <mkukri> grub-{efi,pc}/install-devices needs to be filled in, otherwise grub is not reinstalled on package update
[14:06] <mkukri> this is what curtin does https://github.com/canonical/curtin/blob/204562c277b096229ca20ba546149deef1d85e38/curtin/commands/curthooks.py#L632
[14:06] <mkukri> tsimonq2 ^
[14:06] <mkukri> the os-prober one i think im wrong about
[14:07] <mkukri> it exists, but there is an ubuntu patch that should force it enabled if the existing grub.cfg was generated with os-prober enabled
[14:08] <mkukri> and btw definitely not release critical, there were similar bugs (grub not reinstalling) in cloud images for years. but it should eventually be fixed
[14:11] <tsimonq2> mkukri: Ah okay, I see, thanks :)
[14:12] <tsimonq2> If I had to guess off the top of my head, this is where the modification should be made: https://git.lubuntu.me/Lubuntu/calamares-settings-ubuntu/src/branch/ubuntu/noble/common/modules/before_bootloader_context.conf
[14:13] <tsimonq2> Either that, or a dedicated contextualprocess to set the debconf prompts
[14:13]  * tsimonq2 would be interested in seeing what entries this results in *exactly* for the main Desktop Installer
[14:58] <mkukri> tsimonq2 i can give you an example from a simple install, the more annyoing case is raid where you have to put multiple things into the multiselect
[15:02] <mkukri> so for example, a simple *BIOS* qemu VM results in *grub-pc/install_devices: /dev/disk/by-id/ata-QEMU_HARDDISK_QM00001
[15:05] <mkukri> also i am not sure if lubuntu uses cloud-init at all, but the following recent bug might be relevant too https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2060695
[15:05] -ubottu:#lubuntu-devel- Launchpad bug 2060695 in cloud-init (Ubuntu) "24.04 grub-pc cannot upgrade on mirrored software RAID root disk" [Medium, Triaged]
[15:06] <mkukri> tl;dr cloud-init's cc_grub_dpkg module can mess things up on first boot if enabled
[15:51] <tsimonq2> mkukri: ack looking thanks :)
[15:52] <tsimonq2> mkukri: I don't believe Lubuntu uses cloud-init, no
[15:55] <mkukri> seems to be my observation as well because, ive done some lubuntu installs to (try to) track down the above bug and grub-pc/install-devices was always empty
[15:55] <mkukri> so yeah i assume it should be set by your installer
[16:05] <tsimonq2> mkukri: Calamares doesn't support RAID yet, interesting
[16:06] <arraybolt3> I just recently did a side-by-side install of Kubuntu (which also uses Calamares) and Windows 10 and os-prober did the right thing...
[16:07] <arraybolt3> does having the debconf fields not filled in result in an intermittent issue in this area?
[16:07] <tsimonq2> arraybolt3: To my understanding, when the grub package is updated it looks for those debconf config values to install GRUB to the right place
[16:07] <tsimonq2> postinst or similar
[16:07] <arraybolt3> right
[16:08] <mkukri> arraybolt3, yeah the os-prober issue is seperate from this
[16:08] <arraybolt3> I've seen very strange GRUB prompts during bootloader updates (or possibly even just kernel updates) that looked like something was awry with debconf
[16:08] <arraybolt3> and that is NOT a good UX
[16:08] <mkukri> i just noticed that this _whle_ looking at tthat
[16:08] <arraybolt3> so I'd say this is worth calling a release blocker in the event we can get a fix for it
[16:08] <mkukri> those should go away if debconf is set
[16:08] <mkukri> or there is grub-pc/cloud_style_installation but i recommend not setting that outside cloud images, that uses grub-probe instead
[16:08] <arraybolt3> right
[16:09] <tsimonq2> arraybolt3: What kind of errors did you see? just for the sake of justifying the fix
[16:09] <mkukri> i dont think this should give you errors, just debconf questions
[16:09] <tsimonq2> ah okay that follows
[16:10] <mkukri> and in non-ineractive mode it should just silently leave the old grub installed on disk
[16:10] <arraybolt3> yep, debconf questions
[16:10] <arraybolt3> so you'd upgrade and then see "Where eddo you want to install GRUB?"
[16:10] <arraybolt3> (or something like that)
[16:10] <arraybolt3> s/eddo/do/
[16:10] <arraybolt3> (lag is horrible right now because I'm zsync'ing an ISO)
[16:10] <mkukri> the reason this didnt come up in 23.10 btw is because grub-pc was *never* updated due to a multi year workaround....
[16:10] <mkukri> that  i finally removed in 24.04
[16:11] <arraybolt3> aha
[16:11] <arraybolt3> that makes a lot of sense
[16:12] <mkukri> and that's why cloud_style_installation was added, and why the cloud-init issue with subiquity was discovered too...
[16:12] <mkukri> things seem okay in noble, but i still have many discussions to have with various folks over the issues that were papered over for years
[16:12] <tsimonq2> mkukri: Can I ask why you think this may not be a 24.04 release blocker?
[16:13] <tsimonq2> (If I'm reading your earlier messages correctly, that is.)
[16:13] <mkukri> i guess i didnt have the debconf questions popping up in mind earlier
[16:13] <mkukri> i was only thinking of noninteractive upgrades
[16:14] <tsimonq2> arraybolt3: oh... wait... does Kubuntu's update notifier even support debconf prompts?
[16:14] <arraybolt3> Kubuntu's does not, Lubuntu's does.
[16:14] <arraybolt3> (because I made very sure that it did :P)
[16:14] <tsimonq2> I'd definitely call it a release blocker for Kubuntu then, what do you think?
[16:14] <arraybolt3> Even on Kubuntu though this issue should trigger if the user upgrades via apt, which I did for a while and still do sometimes.
[16:15] <mkukri> is kubuntu and lubuntu the only flavours not using the new desktop installer?
[16:15] <arraybolt3> Ubuntu Unity also.
[16:15] <tsimonq2> mkukri: and Ubuntu Unity
[16:15] <tsimonq2> arraybolt3: jinx :)_
[16:15] <arraybolt3> The main difficulty I'm seeing is, how do we get Calamares to tell us what device the bootloader was installed to?
[16:15]  * arraybolt3 digs in scripts
[16:15] <tsimonq2> arraybolt3: already there
[16:15] <tsimonq2> globalstorage
[16:16] <arraybolt3> right but I mean in a contextual process
[16:16] <arraybolt3> Calamares doesn't expose everything to the shell script thingies
[16:16] <arraybolt3> we could write a module in Python...
[16:16] <tsimonq2> Calamares exposes all globalStorage values to contextualprocesses :)
[16:16] <arraybolt3> but let's exhaust the other options first for sanity's sake
[16:16] <arraybolt3> oh it does? Perfect.
[16:17] <mkukri> should i file a bug about this. and what package is appopriate?
[16:18] <tsimonq2> mkukri: calamares-settings-ubuntu and yes please
[16:20] <arraybolt3> tsimonq2: I see a contextualprocess can decide what code to run based on the value of a global storage key, but does it let you use the value of a global storage key as a variable?
[16:20] <tsimonq2> ...oh?
[16:21] <arraybolt3> The thing is we need to be able to say "take the global storage key, find the corresponding by-id device, stuff it in this debconf entry".
[16:22] <mkukri> https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063354
[16:22] -ubottu:#lubuntu-devel- Launchpad bug 2063354 in calamares-settings-ubuntu (Ubuntu) "Calamares based flavours do not set grub-{efi,pc}/install_devices debconf" [Undecided, New]
[16:22] <tsimonq2> arraybolt3: hey guess what, the bootloader module itself is written in Python :P
[16:22] <tsimonq2> mkukri: Thank you!
[16:22] <arraybolt3> tsimonq2: heh, well there you go
[16:23] <tsimonq2> arraybolt3: do we want to move to Matrix?
[16:23] <arraybolt3> tsimonq2: mkukri is here so I think this is OK here for now
[16:24] <tsimonq2> arraybolt3: ok cool :)
[16:24] <mkukri> im end of day currently, but if you need help please tag my nick, ill check on IRC periodically
[16:25] <arraybolt3> will do, thank you for your help!
[16:26] <arraybolt3> tsimonq2: want me to tackle the patch or are you already doing it?
[16:26] <tsimonq2> arraybolt3: I'm on it, will check in
[16:26] <tsimonq2> arraybolt3: In the meantime any chance you could update RT and the bug report on what's happening?
[16:27] <tsimonq2> (probs release blocker for all three flavors, eh?)
[16:27] <arraybolt3> sure thing
[16:27] <tsimonq2> thank you :)
[16:27] <arraybolt3> and yes, probably a release blocker
[16:27] <mkukri> i assume the desktop installer based ones are fine?
[16:27] <mkukri> and maybe talk to the release team please
[16:29] <arraybolt3> I do not know if the desktop installer based ones are fine or not. If they don't set the debconf prompt, they're probably not fine.
[16:29] <arraybolt3> er, the debconf variable - you know what I mean
[16:29] <mkukri> curtin sets it
[16:30] <arraybolt3> Either the user will get unsightly debconf prompts, OR GRUB won't end up updating most likely, which would leave a gaping security hole and opportunity for Secure Boot bypasses and potential failure to boot if the SBAT key is rotated out.
[16:30] <mkukri> ubuntu desktop itself is definitely fine
[16:30] <mkukri> (ubuntu server too) i do test test thoseregularly
[16:30] <arraybolt3> kk
[16:31] <mkukri> and i think i tested xubuntu too yesteday, but dont hold me to that
[16:31]  * mkukri is going afk for a bit but will be back later
[16:48] <tsimonq2> arraybolt3: At this point, just wondering if setting it to /dev/disk/by-id/SOMETHING is the right thing compared to just /dev/sda1?
[16:48] <tsimonq2> thoughts?
[16:48] <arraybolt3> tsimonq2: /dev/sdXY are unstable and *will* change if the user changes drives (by, e.g., booting with a USB drive inserted).
[16:48] <arraybolt3> Learned this the hard way some time ago, and it's pretty common advice on the Interwebs.
[16:49] <arraybolt3> Figuring out the link between /dev/whatever and /dev/disk/by-id/SOMETHING should be easy enough in theory since the /dev/disk/by-id thingamajigs are just symlinks.
[16:49] <tsimonq2> That follows, now just wondering how it works with the main desktop installer, if there are multiple /dev/disk/by-id entries that match to one disk
[16:49] <tsimonq2> (can happen, from what I'm reading)
[16:49] <arraybolt3> https://www.tutorialspoint.com/python/os_readlink.htm
[16:50] <arraybolt3> oh really? That's not good...
[16:50] <arraybolt3> mmm, I see that I have that situation on *this* system I'm typing on.
[16:50] <tsimonq2> Bright side, the debconf config value is of type "multiselect"
[16:50] <arraybolt3> for me nvme-eui.00253857214071d7 and nvme-Samsung_SSD_970_EVO_Plus_1TB_S6S1NJ0T713093F point to the same partition
[16:50] <arraybolt3> er, the same NVME namespace I mean
[16:50] <arraybolt3> gosh I wish that there weren't NVME namespaces *and* partitions :P
[16:51] <arraybolt3> tsimonq2: maybe by-uuid would work too/instead? Just a thought.
[16:52] <tsimonq2> arraybolt3: the other thing is that in this virtual machine I can only see one by-id mapping to /dev/sda1
[16:53] <tsimonq2> Do you have test hardware? Would be great to see what those entries are actually set to in such a case with the Ubuntu Desktop installer
[16:53] <arraybolt3> tsimonq2: https://termbin.com/8n2f
[16:53] <arraybolt3> hrm... I can make the hardware I have test hardware.
[16:54] <tsimonq2> If you're okay with that, go for it
[16:55] <arraybolt3> I lost my two best testing laptops, one to video card failure, and one to whatever power mess it suffers from, so I'm stuck using one desktop for everything test-wise :P
[16:55] <arraybolt3> but anyway, I was going to test Xubuntu Minimal anyway so I'll give it a shot there
[16:55] <tsimonq2> awesome, thanks
[16:55] <arraybolt3> and maybe also try it in BIOS mode so we get a good picture
[16:57] <tsimonq2> BIOS and UEFI would be great for full testing coverage, probably looking for `sudo debconf-show grub2` on first boot
[16:57] <arraybolt3> nifty
[17:07] <tsimonq2> Testing some code now which just sets an example value for that debconf setting - to test syntax before we have actual values to work with :)
[17:11] <tsimonq2> arraybolt3: `sudo debconf-show grub-pc` not `sudo debconf-show grub2` my bad :)
[17:17] <tsimonq2> I just did a `sudo dpkg-reconfigure grub-pc` on an installed system which gave me some ideas, would still like to see the output of that for both GRUB and EFI to double check though
[17:21] <arraybolt3> tsimonq2: Might take me a bit, I'm just now starting to install Xubuntu for testing.
[17:21] <arraybolt3> Also I'm multitasking between work duties and also Matrix Council activity
[17:23] <arraybolt3> Got the installation going now.
[17:26] <tsimonq2> arraybolt3: sweet thanks
[17:28] <arraybolt3> tsimonq2: alright, so, from an EFI installation:
[17:28] <arraybolt3> uh, `sudo debconf-show grub2` on Xubuntu Minimal outputs nothing.
[17:28] <arraybolt3> Not even a newline.
[17:28] <tsimonq2> arraybolt3: 17:11 < tsimonq2> arraybolt3: `sudo debconf-show grub-pc` not `sudo debconf-show grub2` my bad :)
[17:29] <tsimonq2> :)
[17:29] <arraybolt3> oh lol, alrighty
[17:29] <arraybolt3> ok, grub-pc shows this:
[17:29] <arraybolt3> uh, lemme pastebin
[17:30] <arraybolt3> https://termbin.com/bn4o
[17:30] <tsimonq2> can I get the whole thing?
[17:30] <arraybolt3> I have the ls -l from /dev/disk/by-id coming
[17:30] <arraybolt3> and that is the whole thing
[17:30] <tsimonq2> wait, the whole output?
[17:30] <arraybolt3> That's literally the result of `sudo debconf-show grub-pc | nc termbin.com 9999`
[17:30] <arraybolt3> so yes, that's the whole output
[17:31] <tsimonq2> oh wow this is interesting, ok, yes please what is the /dev/disk/by-id output?
[17:31] <arraybolt3> frustratingly it looks like this particular physical machine with a SATA drive does NOT have multiple /dev/disk/by-id entries that point to the same device!
[17:31] <arraybolt3> https://termbin.com/y01a
[17:31] <arraybolt3> I didn't expect that
[17:31] <arraybolt3> And I cannot safely do this test on my primary laptop.
[17:33] <tsimonq2> arraybolt3: On your primary laptop, any chance you could just run `sudo dpkg-reconfigure grub-pc`, make sure all the entries are correct, then get the debconf-show output from that?
[17:33] <tsimonq2> also looking on my end
[17:35] <arraybolt3> grr, well... https://termbin.com/xiuu now you don't get any device at all... because this is a 22.04 installation on my main laptop.
[17:35] <tsimonq2> aaaaaaaHA
[17:35] <tsimonq2> ok it's only one device
[17:35] <tsimonq2> but it picks the first from the list
[17:36] <arraybolt3> ok good whatever works :P
[17:36] <tsimonq2> arraybolt3: I appreciate ya :)
[17:36] <arraybolt3> sorry I wasn't much help
[17:36] <arraybolt3> I tried *really hard* though
[17:36] <tsimonq2> you helped more than you think - only one debconf setting for that package is a good one
[17:40] <arraybolt3> ah ok
[17:50] <mkukri> make sure to test cryptsetup, LVM and those types of things if you support it too. ive seen weird bugs elsewhere with that before
[17:54] <arraybolt3> mkukri: we have a pretty immense checklist for the Cala-based flavors that covers almost all those weird edge cases (except for LVM which Doesn't Work(TM) with Calamres yet).
[17:54] <arraybolt3> tsimonq2: you still need the BIOS install output? I'm about to reinstall in BIOS mode for that.
[17:55] <arraybolt3> oh fun, Dell's BIOS has arbitrarily decided to gray out my legacy boot option for who-knows-why
[17:55] <arraybolt3> oh there we go, had to enable legacy option ROMs first
[17:58] <tsimonq2> arraybolt3: That would help :)
[17:58] <arraybolt3> kk, in progress...
[17:59] <arraybolt3> (man this installer takes like time and eternity to load)
[17:59] <tsimonq2> Prototype fix:
[17:59] <tsimonq2> +def get_disk_id(device_name):
[17:59] <tsimonq2> +    by_id_path = "/dev/disk/by-id"
[17:59] <tsimonq2> +    device_path = os.path.realpath(device_name)
[17:59] <tsimonq2> +
[17:59] <tsimonq2> +    for entry in os.listdir(by_id_path):
[17:59] <tsimonq2> +        full_entry_path = os.path.join(by_id_path, entry)
[17:59] <tsimonq2> +        if os.path.realpath(full_entry_path) == device_path:
[17:59] <tsimonq2> +            return full_entry_path
[17:59] <tsimonq2> [...]
[17:59] <tsimonq2> +        dev_id_path = get_disk_id(boot_loader["installPath"])
[17:59] <tsimonq2> +        check_target_env_call(["echo 'grub-pc grub-pc/install_devices multiselect " + dev_id_path + "' | debconf-set-selections"])
[18:00] <arraybolt3> Install in progress
[18:01] <arraybolt3> I don't get the details of what that function does but it looks vaguely right to me :)
[18:02] <tsimonq2> the one thing that's verylikely to cause issues is check_target_env_call
[18:02] <tsimonq2> and yep just ran into it not DTRT - coooooooooool
[18:03] <arraybolt3> needs sudo rights perhaps?
[18:03] <arraybolt3> or are you not chroot'd in?
[18:04] <arraybolt3> mmm, you probably need to run that command from within a chroot environment
[18:05] <arraybolt3> tsimonq2: alright a BIOS system has some significantly more interesting keys: https://termbin.com/qixa
[18:06] <arraybolt3> not sure which ones you care about (probably things like grub2/kfreebsd_cmdline_default are ignorable :P), but there you go
[18:06] <arraybolt3> and also ls -l from /dev/disk/by-id: https://termbin.com/15h8
[18:07] <tsimonq2> check_target_env_call means "call this in the target environment and check the result" :)
[18:07] <tsimonq2> arraybolt3: looking thanks!
[18:07] <arraybolt3> ah shoot then you *are* chroot'd in it sounds like
[18:08] <arraybolt3> well, I'm sure you'll figure it out, good luck and I'll be around to try and help
[18:08] <tsimonq2> thanks - also that BIOS output helps thank you :)
[18:44] <tsimonq2> arraybolt3: I have working code for BIOS, testing for EFI
[18:52] <arraybolt3> awesome
[18:59] <tsimonq2> arraybolt3: can I rubber ducky off you real quick?
[19:00] <tsimonq2> BIOS is good, EFI is the last hurdle here
[19:00] <tsimonq2> It seems like in the bootloader module it's being passed as /boot/efi, not the actual partition name
[19:00] <arraybolt3> oooh, ok
[19:01] <tsimonq2> So when grabbing the device ID for EFI, it should grab the ID corresponding to the partition mounted at /boot/efi yes?
[19:01] <arraybolt3> In that instance figure out what partition is mounted at /boot/efi and then use that?
[19:01] <arraybolt3> jinx
[19:01] <arraybolt3> so yeah, that sounds right
[19:01] <tsimonq2> sounds good :) finding some coffee
[19:01]  * genii twitches
[19:36] <mkukri> into install_device you need to put the actual disks
[19:36] <mkukri> tsimonq2, arraybolt3. grub-multi-install internally finds all the ESPs from that and mounts them
[19:37] <mkukri> /boot/efi is just a fallback and that mountpoint is ignored when you set install devices
[19:37] <mkukri> and grub-pc also expects the bare disks, but that part i think is obvious
[19:39] <tsimonq2> mkukri: Oh, just the actual disks?
[19:40] <tsimonq2> mkukri: Nothing under like /dev/disk/by-id or /dev/disk/by-uuid, just e.g. /dev/sda1 ?
[19:40] <mkukri> seems like i am wrong sorry, i checked a desktop installer install and it seems to have the ESP device node https://imgur.com/a/nVSnPGj
[19:40] <mkukri> the by-id and by-uuid part is still there yeah. i was just trying to say that it wasnt expecting the partition but it looks like it is
[19:41] <tsimonq2> No problem! Quick question though...
[19:41] <tsimonq2> Does by-uuid work just as well as by-id in this case?
[19:41] <mkukri> well, i do want to switch to by-uuid *eventually* but it's not tested yet
[19:42] <mkukri> and just to be clear this is the debconf options i get https://imgur.com/a/MvCEVlQ and the above image is the result in debconf db
[19:42] <tsimonq2> mkukri: The current roadblock I have is, for some reason I can only query by-uuid on EFI and by-id on BIOS
[19:43] <tsimonq2> Otherwise I have working code now
[19:44] <mkukri> by-id should work on EFI
[19:44] <mkukri> how are you trying to query it?
[19:44] <tsimonq2> $ ls -l /dev/disk/by-id/
[19:44] <tsimonq2> total 0
[19:44] <tsimonq2> lrwxrwxrwx 1 root root 9 Apr 24 13:45 ata-QEMU_DVD-ROM_QM00001 -> ../../sr0
[19:45] <mkukri> also if you are using a if=virtio disk in qemu you have to give it a serial number on the command line or it wont show up
[19:45] <tsimonq2> mkukri: Simple ls of /dev/disk/by-id
[19:45] <tsimonq2> oooh
[19:45] <tsimonq2> mkukri: I am using QEMU, how does that part work?
[19:45] <mkukri> what command line flag are you using to specify your hard disk?
[19:45] <mkukri> or is it virt manager? or LXD?
[19:45] <tsimonq2> virt-managere
[19:45] <tsimonq2> s/managere/manager/
[19:46] <mkukri> ah i am not sure what that does, but i am guessing it doesnt give the disk a serial number
[19:46] <mkukri> this is a problem with regular ubuntu as well in that case the debconf wont be filled either
[19:46] <mkukri> but the fallback install via /boot/efi still works
[19:46] <mkukri> if you want to test it similar to real hardware, try to specify a disk serial number for your VM in the options somewhere
[19:46] <mkukri> g
[19:47] <mkukri> apparently you can put <serial>some-arbitrary-serial</serial> in the vm's xml inside the <disk> tag
[19:47] <tsimonq2> ok looking then thanks
[19:48] <tsimonq2> mkukri: So to be clear, as for right now you'd recommend against going with by-uuid?
[19:49] <mkukri> if you want to have the same bugs as us then yes :)
[19:49] <mkukri> by uuid is the future plan but maybe it's better if we all switch at once in the 24.10 or 25.04 cycle
[19:50] <tsimonq2> cool, when we do get to that point it'll be a one-liner :)
[19:50] <mkukri> there are problems like UUID's not actually always being unique :/
[19:51]  * mkukri looks at our cloud images in disappointment.....
[19:51] <tsimonq2> oh wowww, okay, didn't know that
[19:52] <mkukri> the issue is, the images are obviously pre generated, so you'd need to replace the uuid with a random one on first boot, but no one has bothered yet
[19:53] <tsimonq2> ahh okay
[19:53] <tsimonq2> mkukri: yes that <serial>ABCDGEF</serial> fix worked \o/
[19:54] <tsimonq2> ok doing a final round of testing before uploading, should be in the clear in the next hour here
[19:54] <mkukri> im glad to hear, that took me many many hours of headbanging to figure out once
[19:54] <mkukri> so you said you dont have LVM or RAID. but do you have cryptsetup?
[19:54] <mkukri> and maybe ZFS?
[19:55] <mkukri> did you test those?
[19:57] <tsimonq2> I can do a round of testing with those, yeah. For now I have just been concerned with making sure regular non-encrypted BIOS and EFI work
[19:57] <tsimonq2> We don't do ZFS, RAID, or LVM at this current point in time, but encrypted installs definitely
[19:58] <mkukri> okay cool im just trying to be exhaustive
[19:58] <tsimonq2> no you're okay :) thanks for that
[19:58] <mkukri> and amd64 bios and uefi are your only GRUB based platforms?
[19:58] <tsimonq2> yes
[19:59] <mkukri> okay i think, i guess that's all the cases than
[19:59] <tsimonq2> cool cool :)
[20:30] -queuebot:#lubuntu-devel- Unapproved: calamares (noble-proposed/universe) [3.3.5-0ubuntu3 => 3.3.5-0ubuntu4] (lubuntu, ubuntustudio)
[20:42] -queuebot:#lubuntu-devel- Unapproved: rejected lubuntu-installer-prompt [source] (noble-proposed) [<IP_ADDRESS>]
[20:45] -queuebot:#lubuntu-devel- Unapproved: lubuntu-installer-prompt (noble-proposed/universe) [24.04.5 => 24.04.6] (lubuntu)
[20:50] -queuebot:#lubuntu-devel- Unapproved: accepted lubuntu-installer-prompt [source] (noble-proposed) [24.04.6]


[00:05] <RAOF> Will do
[00:06] <RAOF> Nope, I'm too late :)
[00:08] <RAOF> bdmurray: Or maybe I'm confused? It looks like lasagne was already removed from Ubuntu before hirsute release?
[00:11] <bdmurray> RAOF: Ah, I didn't look first! I'll just close bug 1888735 then.
[00:11] <sarnold> man you're good :) getting it removed 14 months earlier..
[01:39] -queuebot:#ubuntu-release- New: accepted jinja2-time [amd64] (jammy-proposed) [0.2.0-3]
[01:46] -queuebot:#ubuntu-release- Unapproved: accepted libdrm [source] (focal-proposed) [2.4.107-8ubuntu1~20.04.1]
[01:56] -queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (focal-proposed) [1:13.99.1-1ubuntu3.13]
[03:34] -queuebot:#ubuntu-release- Unapproved: php7.4 (focal-proposed/main) [7.4.3-4ubuntu2.7 => 7.4.3-4ubuntu2.8] (i386-whitelist)
[03:36] -queuebot:#ubuntu-release- Unapproved: php7.4 (hirsute-proposed/main) [7.4.16-1ubuntu2.2 => 7.4.16-1ubuntu2.3] (i386-whitelist, ubuntu-desktop, ubuntu-server)
[04:10] -queuebot:#ubuntu-release- New binary: cookiecutter [amd64] (jammy-proposed/universe) [1.7.3-1] (no packageset)
[08:04] -queuebot:#ubuntu-release- New binary: rtmidi [riscv64] (jammy-proposed/universe) [5.0.0-2] (i386-whitelist, ubuntustudio)
[12:06] <paride> Hi -release. IIRC there's a way to request a temporary removal of a package from -proposed to ease the other ongoing transitions, but I can't find any documentation on the procedure. Do you have a pointer?
[12:08] <paride> The package in question has been auto-synced. In particular I have no idea on how the blocking works: do we have something like block-proposed but for auto-syncs?
[12:08] <seb128> paride, hey, just open a bug on the package requesting the deletion and subscribe ubuntu-archive
[12:09] <seb128> paride, there is a sync blacklist but iirc it's not going to try to sync again the same version if it's deleted, it will get the next upload back though
[12:10] <paride> seb128, thanks! that clarifies. Or I guess I can manually syncpackage to bring it back in...
[12:10] <seb128> paride, yes, sync or upload will work
[12:43] <paride> done: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1952918
[12:44] <paride> I hope it all makes sense :)
[15:15] -queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (impish-proposed) [1:15.0+dfsg1-1ubuntu2.2]
[15:25] -queuebot:#ubuntu-release- Unapproved: accepted deja-dup [source] (bionic-proposed) [37.1-2fakesync1ubuntu0.2]
[17:23] -queuebot:#ubuntu-release- New binary: rust-elfx86exts [amd64] (jammy-proposed/universe) [0.3.0-5] (no packageset)
[17:24] <ricotz> juliank, hi :), could you please cancel the autopkgtest run for "libreoffice/1:7.3.0~beta1-0ubuntu<IP_ADDRESS>~lo3" ?
[17:24] <ricotz> something is really wrong there :(
[17:34] -queuebot:#ubuntu-release- New binary: rust-elfx86exts [arm64] (jammy-proposed/universe) [0.3.0-5] (no packageset)
[17:44] <ricotz> juliank, maybe better to let it finish (which it will hopefully do at some point), to have some log to investigate
[17:46] <juliank> ricotz: good good, busy anyway
[17:47] <ricotz> juliank, sorry for the noise
[17:53] <juliank> ricotz: no problem, it's just I might not notice :)
[19:30] <ginggs> would someone please add r-bioc-biocsingular to big_packages for arm64 and s390x? and qutip for amd64?
[19:40] <bdmurray> I can do that
[19:47] <ginggs> bdmurray: thanks!
[20:10] -queuebot:#ubuntu-release- New: accepted eta [amd64] (jammy-proposed) [1.0.1-1]
[20:10] -queuebot:#ubuntu-release- New: accepted eta [armhf] (jammy-proposed) [1.0.1-1]
[20:10] -queuebot:#ubuntu-release- New: accepted eta [s390x] (jammy-proposed) [1.0.1-1]
[20:10] -queuebot:#ubuntu-release- New: accepted eta [arm64] (jammy-proposed) [1.0.1-1]
[20:10] -queuebot:#ubuntu-release- New: accepted eta [ppc64el] (jammy-proposed) [1.0.1-1]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [amd64] (jammy-proposed) [5.0.0-1]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [armhf] (jammy-proposed) [5.0.0-1]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [ppc64el] (jammy-proposed) [5.0.0-1]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [s390x] (jammy-proposed) [5.0.0-1]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [arm64] (jammy-proposed) [5.0.0-2]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [ppc64el] (jammy-proposed) [5.0.0-2]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [arm64] (jammy-proposed) [5.0.0-1]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [riscv64] (jammy-proposed) [5.0.0-1]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [i386] (jammy-proposed) [5.0.0-2]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [i386] (jammy-proposed) [5.0.0-1]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [s390x] (jammy-proposed) [5.0.0-2]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [amd64] (jammy-proposed) [5.0.0-2]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [armhf] (jammy-proposed) [5.0.0-2]
[20:11] -queuebot:#ubuntu-release- New: accepted rtmidi [riscv64] (jammy-proposed) [5.0.0-2]
[20:12] -queuebot:#ubuntu-release- New: accepted finalcut [amd64] (jammy-proposed) [0.8.0-3]
[20:12] -queuebot:#ubuntu-release- New: accepted finalcut [armhf] (jammy-proposed) [0.8.0-3]
[20:12] -queuebot:#ubuntu-release- New: accepted finalcut [riscv64] (jammy-proposed) [0.8.0-3]
[20:12] -queuebot:#ubuntu-release- New: accepted finalcut [amd64] (jammy-proposed) [0.8.0-4]
[20:12] -queuebot:#ubuntu-release- New: accepted finalcut [armhf] (jammy-proposed) [0.8.0-4]
[20:12] -queuebot:#ubuntu-release- New: accepted finalcut [riscv64] (jammy-proposed) [0.8.0-4]
[20:12] -queuebot:#ubuntu-release- New: accepted ldc [amd64] (jammy-proposed) [1:1.28.0-1ubuntu1]
[20:12] -queuebot:#ubuntu-release- New: accepted ldc [armhf] (jammy-proposed) [1:1.28.0-1ubuntu1]
[20:12] -queuebot:#ubuntu-release- New: accepted simple-image-filter [arm64] (jammy-proposed) [1.1.0+git20211020.7d385d1-1]
[20:12] -queuebot:#ubuntu-release- New: accepted simple-image-filter [ppc64el] (jammy-proposed) [1.1.0+git20211020.7d385d1-1]
[20:13] -queuebot:#ubuntu-release- New: accepted finalcut [arm64] (jammy-proposed) [0.8.0-3]
[20:13] -queuebot:#ubuntu-release- New: accepted finalcut [s390x] (jammy-proposed) [0.8.0-3]
[20:13] -queuebot:#ubuntu-release- New: accepted finalcut [ppc64el] (jammy-proposed) [0.8.0-4]
[20:13] -queuebot:#ubuntu-release- New: accepted ldc [arm64] (jammy-proposed) [1:1.28.0-1ubuntu1]
[20:13] -queuebot:#ubuntu-release- New: accepted simple-image-filter [armhf] (jammy-proposed) [1.1.0+git20211020.7d385d1-1]
[20:13] -queuebot:#ubuntu-release- New: accepted finalcut [ppc64el] (jammy-proposed) [0.8.0-3]
[20:13] -queuebot:#ubuntu-release- New: accepted finalcut [s390x] (jammy-proposed) [0.8.0-4]
[20:13] -queuebot:#ubuntu-release- New: accepted simple-image-filter [s390x] (jammy-proposed) [1.1.0+git20211020.7d385d1-1]
[20:13] -queuebot:#ubuntu-release- New: accepted finalcut [arm64] (jammy-proposed) [0.8.0-4]
[20:13] -queuebot:#ubuntu-release- New: accepted simple-image-filter [amd64] (jammy-proposed) [1.1.0+git20211020.7d385d1-1]
[20:13] -queuebot:#ubuntu-release- New: accepted aiosignal [amd64] (jammy-proposed) [1.2.0-1]
[20:13] -queuebot:#ubuntu-release- New: accepted matrix-sydent [amd64] (jammy-proposed) [2.5.1-1]
[20:13] -queuebot:#ubuntu-release- New: accepted python-rdata [amd64] (jammy-proposed) [0.5-2]
[20:13] -queuebot:#ubuntu-release- New: accepted unifrac [amd64] (jammy-proposed) [0.10.0-3]
[20:13] -queuebot:#ubuntu-release- New: accepted unifrac [ppc64el] (jammy-proposed) [0.10.0-3]
[20:13] -queuebot:#ubuntu-release- New: accepted ansible-core [amd64] (jammy-proposed) [2.12.0-1]
[20:13] -queuebot:#ubuntu-release- New: accepted simple-image-filter [riscv64] (jammy-proposed) [1.1.0+git20211020.7d385d1-1]
[20:13] -queuebot:#ubuntu-release- New: accepted python-installer [amd64] (jammy-proposed) [0.4.0+dfsg1-1]
[20:13] -queuebot:#ubuntu-release- New: accepted unifrac [arm64] (jammy-proposed) [0.10.0-3]
[20:13] -queuebot:#ubuntu-release- New: accepted cookiecutter [amd64] (jammy-proposed) [1.7.3-1]
[20:13] -queuebot:#ubuntu-release- New: accepted flake8-comprehensions [amd64] (jammy-proposed) [3.6.1-1]
[20:13] -queuebot:#ubuntu-release- New: accepted flake8-quotes [amd64] (jammy-proposed) [3.3.1-1]
[20:13] -queuebot:#ubuntu-release- New: accepted rust-elfx86exts [amd64] (jammy-proposed) [0.3.0-5]
[20:13] -queuebot:#ubuntu-release- New: accepted flake8-class-newline [amd64] (jammy-proposed) [1.6.0-1]
[20:13] -queuebot:#ubuntu-release- New: accepted python-tomli-w [amd64] (jammy-proposed) [0.4.0-1]
[20:13] -queuebot:#ubuntu-release- New: accepted flake8-import-order [amd64] (jammy-proposed) [0.18.1-1]
[20:13] -queuebot:#ubuntu-release- New: accepted rust-elfx86exts [arm64] (jammy-proposed) [0.3.0-5]
[21:50] -queuebot:#ubuntu-release- New binary: q2-diversity-lib [amd64] (jammy-proposed/universe) [2021.8.0-1] (no packageset)
[23:07] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (focal-proposed/main) [2.664.35 => 2.664.36] (desktop-core, i386-whitelist)
[23:08] -queuebot:#ubuntu-release- New binary: cryptsetup [amd64] (jammy-proposed/main) [2:2.4.2-1ubuntu1] (core, i386-whitelist)
[23:08] -queuebot:#ubuntu-release- New binary: cryptsetup [s390x] (jammy-proposed/main) [2:2.4.2-1ubuntu1] (core, i386-whitelist)
[23:09] -queuebot:#ubuntu-release- New binary: cryptsetup [i386] (jammy-proposed/main) [2:2.4.2-1ubuntu1] (core, i386-whitelist)
[23:09] -queuebot:#ubuntu-release- New binary: cryptsetup [ppc64el] (jammy-proposed/main) [2:2.4.2-1ubuntu1] (core, i386-whitelist)
[23:12] -queuebot:#ubuntu-release- New binary: cryptsetup [armhf] (jammy-proposed/main) [2:2.4.2-1ubuntu1] (core, i386-whitelist)
[23:15] -queuebot:#ubuntu-release- New binary: cryptsetup [arm64] (jammy-proposed/main) [2:2.4.2-1ubuntu1] (core, i386-whitelist)
[23:28] -queuebot:#ubuntu-release- New: accepted q2-diversity-lib [amd64] (jammy-proposed) [2021.8.0-1]
[23:29] -queuebot:#ubuntu-release- New: accepted cryptsetup [amd64] (jammy-proposed) [2:2.4.2-1ubuntu1]
[23:29] -queuebot:#ubuntu-release- New: accepted cryptsetup [ppc64el] (jammy-proposed) [2:2.4.2-1ubuntu1]
[23:30] -queuebot:#ubuntu-release- New: accepted cryptsetup [i386] (jammy-proposed) [2:2.4.2-1ubuntu1]
[23:30] -queuebot:#ubuntu-release- New: accepted cryptsetup [s390x] (jammy-proposed) [2:2.4.2-1ubuntu1]
[23:30] -queuebot:#ubuntu-release- New: accepted cryptsetup [arm64] (jammy-proposed) [2:2.4.2-1ubuntu1]
[23:30] -queuebot:#ubuntu-release- New binary: cryptsetup [riscv64] (jammy-proposed/main) [2:2.4.2-1ubuntu1] (core, i386-whitelist)
[23:30] -queuebot:#ubuntu-release- New: accepted cryptsetup [armhf] (jammy-proposed) [2:2.4.2-1ubuntu1]