[18:43] <jcjordyn120> Hello
[18:44] <flocculant> hi
[19:12] <jcjordyn120> is yakkety yak going to be a lts or a standard release?
[19:16] <flocculant> jcjordyn120: it'll be a standard one
[23:20] <LazyUser69> Will sending an error report genuinely help fix a problem?


[10:45] <zniavre>  #931630
[10:55] <eagles0513875> zniavre: bug 931630
[11:11] <ikonia> eagles0513875: did you progress your issue ok ?
[11:12] <eagles0513875> ikonia: seems like i kinda made a mess of things reinstalling the netbook package and then switching to the netbook layout
[11:12] <eagles0513875> i have the normal desktop menu bar on the bottom with the k menu and all as well as the netbook menubar which crashes on login
[11:12] <ikonia> eagles0513875: ok, so despite that it seems like you have made progress to narrow it down
[11:13] <eagles0513875> correct that the issue is the the netbook transition package i haven't tried anything else today sadly
[11:13] <ikonia> I don't think the issue is the transistion package
[11:13] <ikonia> that's not going to cause an applet to crash
[11:13] <ikonia> (applet - bad wording)
[11:14] <ikonia> the netbook package is just a meta package, that won't cause applications to crash
[11:17] <eagles0513875> ok thing is on instant crash there is no back trace or anything
[11:22] <ikonia> you don't have to get a back trace
[11:22] <ikonia> eagles0513875: lets get a plan together here,
[11:22] <eagles0513875> ok
[11:22] <ikonia> eagles0513875: 1.) do you know if anyone else has confirmed the issue with the netbook layout
[11:23] <eagles0513875> sadly not i can't find anyone else with a netbook :(
[11:23] <ikonia> ok, that would be really helpful, to get another netbook user to confirm the issue and anything similar/different
[11:23] <ikonia> have you hit a few people up on the mailing list/irc
[11:24] <ikonia> does the issue occur if you use a laptop/desktop and install the netbook layout ?
[11:25] <eagles0513875> actually forgot about the mailing list
[11:25] <ikonia> not a crime
[11:25] <ikonia> what about the other stuff, does it work on a laptop if you use the netbook layout ?
[11:26] <eagles0513875> but I'm having issues with that no mode set which i have to figure out how I'm going to tackle but thats not related to the current discussion
[11:26] <ikonia> I told you how to fix the nomodeset issue
[11:26] <ikonia> you must have another machine to try a kubuntu netbook layout install on ?
[11:27] <ikonia> hell, would you like me to try it on a vm I have running on my laptop now ?
[11:28] <eagles0513875> ikonia: the problem with vms at least from what i have seen bugs that surface on physical hardware don't surface at all on virtual machines and vice versa
[11:28] <eagles0513875> but ill go ahead and setup a vm :)
[11:28] <ikonia> eagles0513875: do you think this is a hardware problem ? as 2 minutes ago you thought it was a problem with a meta package?
[11:29] <eagles0513875> i don't think so
[11:29] <ikonia> hand on heart, where do you think the issue lies from what you have seen far
[11:29] <eagles0513875> this netbook is fairly new and in great condition
[11:29] <eagles0513875> its a package just not sure what exactly the package is :(
[11:29] <ikonia> hardware problem does mean "broken hardware" it could be an incompatability
[11:30] <ikonia> ok - let me get a vm image running and you can walk me through it,
[11:30] <ikonia> give me a few minutes
[11:30] <ikonia> are you running 32 or 64bit ?
[11:30] <eagles0513875> ikonia: 11.10 worked fine on the netbook desktop
[11:30] <eagles0513875> 32bit
[11:30] <ikonia> right and you're using 12.10 ?
[11:31] <eagles0513875> correct
[11:31] <eagles0513875> i noticed the menubar issue in 12.04
[11:31] <ikonia> ok, lets stick with what you're currently running
[11:32] <eagles0513875> ok
[11:32] <ikonia> exactly which install image are you using so I grab the same one
[11:33] <eagles0513875> i did the net install
[11:33] <ikonia> ughhh
[11:33] <ikonia> despite me telling you multiple times not to
[11:33] <ikonia> I'll just use the standard 12.10 current image
[11:35] <ikonia> there is no 12.10 kubuntu-netbook image I can find, give me a minute or two
[11:36] <ikonia> fine, I'll use the net installer
[11:36] <ikonia> eagles0513875: which/where did you get the netinstaller image you are using
[11:37] <eagles0513875> oops meant the alternate cd
[11:37] <eagles0513875> which is technically the net install
[11:37] <ikonia> the altnernave cd is NOT the net instrall
[11:37] <ikonia> there is nothing "net install" abou it
[11:37] <eagles0513875> ok
[11:37] <ikonia> please be %100 clear - what are you using
[11:37] <eagles0513875> i forgot that they took the net install down
[11:38] <ikonia> so which cd image are you using, link me to it
[11:39] <eagles0513875> http://www.kubuntu.org/getkubuntu/download
[11:39] <eagles0513875> then the 32bit alternate cd option
[11:39] <ikonia> ok
[11:40] <ikonia> eagles0513875: that is NOT 12.10 !!!!!P
[11:40] <eagles0513875> then i did a manual upgrade from 12.04 to 12.10 by changing the sources list
[11:40] <ikonia> I am getting REALLY annoyed with this now
[11:40] <ikonia> eagles0513875: why did you upgrade to 12.10 ?
[11:41] <eagles0513875> was hoping to contribute this cycle to the project
[11:41] <ikonia> contribute to the cycle ???
[11:41] <ikonia> sorry, I'm backing out of this you need to grow up
[11:41] <eagles0513875> ok. ill do further testing on a vm myself
[11:41] <ikonia> I'll test the 12.04 issue with you
[11:42] <ikonia> you're just making an invalid test case
[11:42] <eagles0513875> ?
[11:42] <ikonia> is the issue on 12.04 currently ?
[11:42] <eagles0513875> initially my netbook was on 12.04 and it was there
[11:42] <eagles0513875> yes
[11:42] <ikonia> right, so focus on that
[11:42] <eagles0513875> ok well i don't want to waste your time ill setup a vm after lunch and test it out on there
[11:42] <ikonia> that is the active distro, that is LTS
[11:42] <ikonia> if there is a fix it will get fed into the other releases, focus on what's real
[11:43] <eagles0513875> ok
[11:43] <ikonia> eagles0513875: it's not so much my time I'm bothered about (although I don't enjoy having it wasted) it's others like the development time you're wasting
[11:43] <ikonia> eagles0513875: you need to get solid and valid test results
[11:43] <ikonia> eagles0513875: the more you just amble on giving random bits of info the more invalid/lucid it becomes
[11:43] <eagles0513875> ok
[11:43] <ikonia> work with me here on the 12.04 issue, we can move to 12.10 if needed to confirm the issue
[11:44] <ikonia> can you get a clean 12.04 image on your netbook, is that possible ?
[11:44] <eagles0513875> i can reinstall just have to backup a few things
[11:44] <ikonia> is that possible now (while I'm downloading the CD ?)
[11:45] <eagles0513875> i need to download the cd and was going to leave that downloading while i go have lunch
[11:45] <ikonia> ok, I'm downloading the CD now
[11:45] <ikonia> can you please ping me when you return so you can walk me through the issue please.
[11:46] <eagles0513875> sure thing
[11:46] <ikonia> thank you
[12:14] <edgy> Hi, I have precise dual boot with windows and now wants to install quantal alongside. I will create an lv_root, lv_home and then boot from the liveCD and choose the / and /home to point to the previouse volumes, is that OK?
[12:37] <tbf> is there a reason for making libboost-1.46-dev and libboost-1.48-dev conflict with each other? how about making them parallel installable?
[13:07] <BluesKaj> hey all
[13:47] <eagles0513875> ikonia: ping
[13:47] <eagles0513875> ikonia: about to make my bootable usb
[13:55] <ikonia> eagles0513875: ahhh great, I'm installing at the moment
[13:56] <eagles0513875> turns out the download didn't complete, only partially :( redownloading the iso now. :(
[13:58] <eagles0513875> ikonia: do you mind if i ask you what might sound like a stupid question
[14:02] <ikonia> always
[14:02] <ikonia> (as in never a problem)
[14:04] <eagles0513875> whats the point of having a netbook desktop when the standard kde layout work just fine and i feel at times out performs the netbook one
[14:05] <ikonia> it works fine for you
[14:05] <ikonia> others like different things
[14:05] <ikonia> your view/experience does not represent everyones elses, others may find it performs worse, or like a different layout better
[14:05] <ikonia> personally I don't like netbook layouts, but then again, that's just me
[14:06] <eagles0513875> ikonia: i actually agree with you
[14:07] <eagles0513875> one thing i have noticed which is odd as of 12.04 in system settings there is no way to disable the track pad
[14:07] <eagles0513875> on ones laptop/netbook
[14:08] <ikonia> I'm not really a kde user, so I don't know about things like that
[14:08] <eagles0513875> not a problem
[14:08] <eagles0513875> another question. i had tried unity
[14:08] <eagles0513875> nm scratch that question
[14:08] <ikonia> ok
[14:11] <eagles0513875> 5 min to go for the redownload of the iso to complete
[14:12] <ikonia> I'm still installing as I was tight with the ammount of ram and cpu I have the machine
[14:14] <eagles0513875> all my netbook is is a hyper threaded atom with 2gb of ram
[14:15] <ikonia> eagles0513875: lets move this to #kubuntu as we are not discussing 12.10 at this time
[14:15] <eagles0513875> ikonia: read my mind :D
[16:22] <iceroot> hi
[16:22] <iceroot> is it a bug or a feature that the auto-mounter is using /run/media/username instead of /media/ for removable devices?
[20:00] <DrHalan> hey guys. i was wondering if there is already a version of UbuntuTV to try out
[21:12] <edgy> Hi, I tried to import a file to muon that contaim package names and now I got "'The package system could not be initialized, your configuration may be broken.". I guess the file is not in the proper format but how can I get muon back? I closed and restart but getting the same error.
[23:05] <alex_mayorga> How broken is Quetzal?
[23:07] <FernandoMiguel> not much
[23:08] <FernandoMiguel> one of my machines is having probs with cups
[23:08] <FernandoMiguel> other then that, it's fine
[23:08] <FernandoMiguel> sound is very low.....
[23:21] <alex_mayorga> FernandoMiguel: Is it alpha 1 yet?
[23:21] <alex_mayorga> I usually jump in right after the 1st alpha
[23:22] <FernandoMiguel> long ago
[23:37] <alex_mayorga> Not that long ago according to http://www.ubuntu.com/testing


[04:20] <lifehappy> where's dash panel
[05:06] <letstrythis> o.0
[09:32] <dan-roger> hej
[12:08] <studio-user271> Thanks and Hello everyon
[16:12] <holstein> letstrythis: im sure you have already searched and found out about nice levels.. but in case you havent http://en.wikipedia.org/wiki/Nice_(Unix)
[16:12] <holstein> letstrythis: you really shouldnt need to mess with those anymore for audio production, or otherwise.. unless you are trying to do something very particular, in which you would likely either already know, or want to learn about setting priorities
[16:59] <letstrythis> ty looking over a guide i know what nice is but not what moitorix is representing on a grapgh with nice value of 97%
[16:59] <letstrythis> ubunturt is not for audio only xD
[17:00] <holstein> letstrythis: i never implied it was
[17:00] <holstein> letstrythis: but, in relation to this channel, thats what i know about.. and we used to have to tweak those
[17:06] <letstrythis> lots of tweaking with rt...trying to get em balanced a bit better and understand how things use the current system
[17:06] <holstein> you shouldnt need to anymore
[17:06] <holstein> not many do, and if you start with a server distro, things should be setup as you need out of the box.. or at least close
[17:06] <holstein> there are compromises to any of these tweaks
[17:07] <holstein> the ones we discuss here will be irrelevant to your needs
[17:07] <holstein> the compromises are taking power management and laptops and audio/video production into account
[17:32] <letstrythis> xD well i went back to rt because it was obvious i needed to, i am unfamiliar with low latency, aesired i don't know it supports, it installed some rt compnents anyway, so i did a comparison over 3 days with just te day 1 install...and rt performed better for what i need to do so far...the gui doesn't pause, i can still work...and if it does, terminal works....internet stays on under high loads...many things
[17:33] <holstein> "better" is always a matter of opinion, and will typically invovle compromise
[17:33] <letstrythis> some adjustment dont need restarts...
[17:34] <holstein> if you were looking at power comsumption, and system resource load, and wear and tear.. etc..
[17:34] <letstrythis> yes
[17:34] <letstrythis> often those compromises can be worked out with upgrades, tweaks or working with devs too
[17:35] <holstein> letstrythis: i never impled they couldnt.. but, i dont think it "often"
[17:35] <letstrythis> yes, this is what i'm trying to look at now and understand
[17:35] <holstein> and, in itself there is an investement
[17:39] <letstrythis> yup, i'm already investing in this endevor so..plan to continue
[17:40] <letstrythis> the reason i come here, is because this is whee i got support for rt when it was basically just starting
[17:40] <holstein> sure.. its just that most folks typically find that the sane defaults are just that.. sane
[17:40] <holstein> letstrythis: actually this is where i started communicating with you in the first place about it in regards to audio production.. when you were unclear with me about what your intentions were
[17:41] <holstein> otherwise, i still say, you are in the wrong place
[17:41] <letstrythis> XD well audio will be part of it
[17:42] <holstein> letstrythis: *not* audio production friend.. not in the way that i am discussing, and this channel is focused
[17:43] <letstrythis> and so will video and cad work
[17:43] <holstein> which dont require what you are talking about
[17:44] <letstrythis> okay so live broacasting, voip isn't what your talking about?
[17:44] <holstein> letstrythis: correct. that is *not* what im talking about
[17:44] <holstein> letstrythis: this is only for 2 things.. as i said
[17:45] <letstrythis> regardless of how you define this, your being here, has helped me and so have others...thank you
[17:45] <holstein> live effects processing.. meaning, you pluck a guitar string, and you want an effect such as distortion to occur with the sound you are creating in as close to realtime as possible
[17:46] <holstein> software synths... you press a key on a midi keyboard, and a sound or sample is triggered in as close to realtime as possible.. so that when you press the key, it seems like you are playing the actual instrument
[17:46] <holstein> all other applications are not the scope of realtime for audio production, and are not really what we talk about with "realtime"
[17:46] <holstein> rt kernels are just allowing and facilitating priorities with compromises
[17:47] <letstrythis> cool, your exeieces with that custom setup will likely behelpful to o me and many others
[17:47] <holstein> other things facilitate other compromises
[17:47] <holstein> letstrythis: i dont do "custom" setups, though
[17:47] <holstein> letstrythis: this is just with the stock ubuntustudio setup
[17:47] <holstein> letstrythis: its tailored to, within reason, facilitate audio production
[17:48] <letstrythis> well that woud als be xubuntstudio basically?
[17:48] <holstein> letstrythis: there is no "xubuntustudio"
[17:48] <holstein> letstrythis: we use XFCE just as xubuntu does
[17:48] <holstein> letstrythis: they are *all* ubuntu
[17:53] <letstrythis> what kinda pc did you do this from, did you watch how hard things wrked at some point? I'm thinking along the lines of these comprprimises...i need to know how to ajust these things on the fly...much as i think you had to, but first i have to understand what the software is telling me, andso need something more then the standard system monitor, possible,
[17:53] <holstein> letstrythis: *many* different hardware cased.. i watched for audio production specific issues only
[17:54] <holstein> letstrythis: adjusting kernel paramaters like that on the fly should not be needed, or done
[17:54] <letstrythis> XD man i could imagine, many audio hadware is proprietary...
[17:55] <holstein> letstrythis: im not talking about with audio hardware
[17:55] <holstein> letstrythis: im talking about adjusting the kernel paramaters on the fly *specifically* as you suggest. that should be both avoided, and not necessary
[17:56] <letstrythis> yea well...what do you do when your sound breaks up and you know a slight prioirty increase would hel...knowing what it will comprimise, it would be a wise thing to do...no?
[17:57] <holstein> letstrythis: it doesnt
[17:57] <holstein> letstrythis: i use JACK, and it doesnt
[17:57] <holstein> letstrythis: for all my audio production needs, that are reasonable, audio doesnt break up
[17:57] <holstein> letstrythis: if it does, i relax my jack settings
[17:57] <letstrythis> i see
[17:58] <holstein> letstrythis: i do not intend to tweak kernel paramaters for this purpose
[17:59] <letstrythis> i do think i recall a few threads asking about jack and resource useage...
[17:59] <holstein> letstrythis: sure.. which are completely irrelevant to you
[17:59] <holstein> letstrythis: jack and resource usage is just for that.. using jack
[17:59] <holstein> and, if you dont need jack, you should use it. the overhead is not needed
[18:04] <letstrythis> okay, so what do you think is relevent?
[18:06] <holstein> letstrythis: really, just that you shouldnt be applying kernel settings like that on the fly
[18:06] <holstein> not in ubuntu, at least
[22:30] <studio-user712> italiani..?
[22:30] <holstein> !it
[23:21] <t001> Hi I switched from windows and I installed 14.04 with an ATI graphics card. What do I need to do before switchig to a GeForce 7200GS?
[23:23] <t001> I want to make sure NVidia 304-updates drivers are there to support my graphics card
[23:25] <t001> Also I am going to buy graphics cards for another computer. Should I avoid NVidia cards since I am not able to install 14.04 with those cards?
[23:31] <t001> any document or media you could point me to so I can switch my graphics card succesfully?
[23:32] <t001> Alguien sabe que hacer para cambiar una targeta grafica?
[23:33] <Unit193> t001: I don't know of a doc for that, but I can tell you I'm using 304 on this computer now tih 14.04.


[04:28] <InHisName> pin-drop
[17:28] <MutantTu1key> join ##debian
[17:29] <MutantTu1key> all i gotta say is linux has the most f***ed up file association launching system ever
[17:30] <MutantTu1key> half of the programs don't use XDG, xdg isn't a great solution for every window manager, anytime i install a new package my defaults get overwridden
[17:30] <MutantTu1key> my latest gripe: installing an wine update has caulsed all programs to laucnh with wine's IE
[17:30] <MutantTu1key> WHY loard!


[09:53] <teddy-dbear> Morning peoples, critters and everything else
[12:19] <teddy-dbear> off to PACS
[12:19] <teddy-dbear> seeya


[14:33] <lindol> hi all
[21:06] <kozukumi> I have an issue with gdm not respawning in Ubuntu Gnome 15.10 (Gnome Shell 3.16) when auto login is enabled. All works fine if I do not have autologin enabled. Anyone seen this? I can't find any errors in the log files. It just doesn't respawn with some text on the screen, last line saying "A start job is running for Wait for Plymouth Boot Screen to Quit (47s / no limit)"
[21:47] <muelli> kozukumi: sounds strange.  Mind you that logs are done via journalctl nowadays.
[21:50] <kozukumi> yeah journalctl says nothing
[21:51] <kozukumi> All I get is this http://i.imgur.com/BuUOpH3.jpg
[22:01] <muelli> kozukumi: that's not journalctl though ;-)
[22:01] <kozukumi> yeah indeed, that is a picture of the screen when it errors ;)
[22:03] <darkxst> that should timeout and continue after 2mins though
[22:38] <kozukumi> darkxst why is it happening though?
[22:45] <darkxst> kozukumi, idk, did gdm crash?
[22:46] <darkxst> get the logs from journalctl
[22:46] <kozukumi> what is the best way to get the logs related to the crash?
[22:46] <kozukumi> jorunalctl list thousands of lines
[22:47] <darkxst> pastebin
[22:47] <kozukumi> ok i will do it next time i logout and crash it ;)


[06:34]  * Squirm looks at cocooncrash
[06:35] <Squirm> so I was looking for a post on the ins and outs of xbmc
[06:36] <Squirm> and wanting to browse the web as well as use xbmc. Realised Raspbmc isn't quite the way do go. Came across cocooncrash's blog post that had been linked on a forum. Found it Sunday, opened up the page now, realised it had a .za.net and was like, oh, cool. Header: cocooncrash
[06:36] <Squirm> :D
[06:54] <Squirm> but yeah, go go South Africans
[08:30] <Vince-0> surpdurp
[08:44] <psyatw> hi Vince-0
[08:49] <Vince-0> work work
[08:55] <tinuva> Squirm, you be surprised how many south africans contribute to opensource/linux in general :P
[09:07] <Vince-0> non from Durban that I know of
[09:13] <Squirm> http://michael.gorven.za.net/raspberrypi/xbmc
[09:13] <Squirm> it's a god post - haven't tried it yet though
[09:13] <Squirm> s/god/goog
[09:13] <Squirm> s/goog/good
[09:40] <cocooncrash> Squirm: :-)
[19:32] <nuvolari> .
[19:32] <nuvolari> bloep
[19:32] <nuvolari> hello's
[19:34] <rotsee> hello nuvolari!
[19:34] <nuvolari> hi rotsee :)
[19:34] <nuvolari> are you new here? :P
[19:36] <rotsee> Yep, just browsing new channels for fun!
[19:36] <rotsee> and in SA for half a year, so looking around in SA-channels too, obviously! :)
[19:37] <nuvolari> welcome! It's been quiet today, and I've not been around too much lately :P
[19:37] <nuvolari> From where are you rotsee? If I may ask?
[19:38] <rotsee> From Sweden!
[19:39] <nuvolari> Great! I hope you will have a good stay here and in ZA too!
[19:39] <nuvolari> Maaz: coffee on
[19:39]  * Maaz washes some mugs
[19:40] <rotsee> Thanks! How is Linux adaptation here, btw? Ubuntu as popular as one would expect?
[19:43] <Maaz> Coffee's ready for nuvolari!
[21:12] <nlsthzn> the fly's be in da house
[21:15] <superfly> upgrading my VPS
[21:15] <nlsthzn> ah...
[21:15] <who_da_fly> I'm upgrading my VPS... currently upgrading PostgreSQL 8.4 to 9.1
[21:15] <nlsthzn> other than that, how are you superfly / who_da_fly ?
[21:16] <who_da_fly> sunburnt thanks
[21:16] <who_da_fly> we had a company outing yesterday... "I'm on a BOAT"
[21:16] <who_da_fly> and a new guy started today
[21:17] <nlsthzn> yes, spring/summer getting under way now back there... nice
[21:17] <who_da_fly> cool, but not so cool. flipping PC hassles. no HDMI cables, and the brand new hard drive was faulty
[21:17] <who_da_fly> *grumble*
[21:18] <nlsthzn> that sucks...
[21:18] <who_da_fly> well, we managed to get most things up and running by the end of the day, apart from his PC
[21:19] <nlsthzn> so far I have been very lucky... made two desktop purchases here in the last year and both where a ok from the beginning
[21:19] <who_da_fly> these days I trust Takealot.com more than the PC distributors themselves
[21:19] <nlsthzn> my last PC in SA I bought from an online store...
[21:20] <nlsthzn> can't remember the name now :p
[21:26] <who_da_fly> prophecy? sybaritic?
[21:27] <nlsthzn> sybar
[21:27] <nlsthzn> very good prices
[21:27] <nlsthzn> there was an issue with propechy that time
[21:27] <nlsthzn> both decent if I recall
[21:27] <who_da_fly> yeah, they still have that reputation
[21:28] <nlsthzn> cool


[14:43] <Michalxo_> hello
[14:43] <Keybuk> hello
[14:43] <Michalxo_> is it normal to stop keyb working when in gdm logging screen -> ctrl+alt+f1 -> back to f7
[14:43] <Michalxo_> and keyb is working no more
[14:44] <Keybuk> no
[14:44] <Michalxo_> well.. it happens to me.. did 3 times in a row.. to be sure :D
[14:44] <Michalxo_> and got some images of mountall problem I have with ntfs-3g
[14:45] <Michalxo_> will uppload in a moment
[14:45] <Michalxo_> cjwatson, I am here, I caught your last message
[14:46] <Keybuk> the keyboard issue is likely an X problem, unrelated to boot changes
[14:46] <Keybuk> (your keyboard would either work, or not at all, switching to/fro console shouldn't make a difference)
[14:46] <Michalxo_> ok I'll past it then there :)
[14:46] <Michalxo_> well.. it works here, it works there.. then it works no more :)
[14:47] <Keybuk> iz gtk bug
[14:49] <Michalxo_> http://pastebin.org/18318
[14:51] <Keybuk> *reading8
[14:51] <Michalxo_> dunno how to make it in 1 link :(
[14:51] <Keybuk> so your two ntfs filesystems didn't mount
[14:51] <Keybuk> but otherwise your boot worked?
[14:52] <Michalxo_> yes
[14:52] <Michalxo_> and on shutdown, I have that error message of mountall
[14:52] <Keybuk> fuse: failed to create temporary directory
[14:52] <Keybuk> seems to be the key message here
[14:52] <Keybuk> the STOP/CONT thing?  don't worry about that - that's just a random artefact of the shutdown sequence
[14:52] <Michalxo_> well.. I know nothing about that :(
[14:52] <Michalxo_> haha ok :)
[14:53] <Keybuk> could you try something for me
[14:53] <Keybuk> boot it up
[14:53] <Keybuk> and open a terminal
[14:53] <Keybuk> then run
[14:53] <Keybuk> sudo -s
[14:53] <Keybuk> that'll give you a root terminal
[14:53] <Keybuk> then run
[14:53] <Keybuk> echo -n add > /sys/block/sda/sda1/uevent
[14:53] <Keybuk> echo -n add > /sys/block/sda/sda6/uevent
[14:54] <Keybuk> then see if your two windows partitions are mounted
[14:55] <Michalxo_> well.. can't I do it here?
[14:55] <Keybuk> Michalxo_: "here" ?
[14:55] <Michalxo_> or you mean recovery?
[14:55] <Michalxo_> why reboot :-/
[14:55] <Keybuk> oh, you're on the system now?  yes you can do it now
[14:55] <Michalxo_> I am there :)
[14:55] <doko> Keybuk: udev isn't running as well
[14:55] <Keybuk> I didn't say "reboot", just "boot" :)
[14:55] <Michalxo_> heh
[14:55] <Keybuk> doko: please take a ticket - I'll be with you shortly :p
[14:57] <Michalxo_> Keybuk, should taht echo change something in file?
[14:57] <Michalxo_> they are not mounted
[14:57] <Keybuk> ok
[14:58] <Keybuk> Michalxo_: what does "status mountall" say ?
[14:58] <Michalxo_> start/running, process 1159
[14:59] <Keybuk> ah, no, I see
[14:59] <Keybuk> it already tried to mount them and failed, and doesn't try again
[15:00] <Keybuk> Michalxo_: thanks for your help, I can see what's wrong
[15:00] <Michalxo_> so? :) update will be soon out?
[15:00] <Keybuk> yes
[15:00] <Michalxo_> thank you... btw ntfs / ntfs-3g in fstab = that big difference?
[15:00] <Keybuk> no, it understands both
[15:01] <Keybuk> the problem you have is that it tries to mount the ntfs partitions while the root filesystem is still read-only
[15:01] <Michalxo_> cause with ntfs it works good
[15:01] <Michalxo_> aha
[15:01] <Keybuk> and since ntfs-3g is handled by fuse, this can't work, because it needs at least /tmp to be writable
[15:01] <Michalxo_> ah, I see
[15:01] <Keybuk> ntfs is handled in-kernel, so might not
[15:01] <Michalxo_> ok then
[15:01] <Keybuk> the mounting while / is read-only is a bit of an optimisation
[15:02] <Keybuk> it seems to be a bit over-ambitious
[15:02] <Michalxo_> :)
[15:02] <Michalxo_> ok then :) anything you need more from me?
[15:02] <Keybuk> no, thank you very much for your help
[15:02] <Michalxo_> welcome, thanks for upcoming patch and work :)
[15:03] <Michalxo_> bye! :)
[15:03] <Keybuk> doko: right
[15:03] <Keybuk> you said that udev was not running?
[15:04] <cjwatson> Keybuk: where does revision control for mountall live?
[15:04] <Keybuk> cjwatson: /home/scott/work/native-upstart/mountall
[15:04] <cjwatson> ah :)
[15:04] <cjwatson> bzr init it is, then
[15:04] <Keybuk> I can't push to lp:~ubuntu-core-dev/ubuntu/karmic/mountall :-(
[15:05] <Keybuk> oh, but I can if I put /ubuntu on the end
[15:05] <Keybuk> cjwatson: lp:~ubuntu-core-dev/ubuntu/karmic/mountall/ubuntu
[15:05] <cjwatson> cool, thanks
[15:07] <Keybuk> pull again, hadn't pushed the pending changes
[15:09] <doko> Keybuk: yes
[15:10] <Keybuk> doko: that's odd
[15:10] <Keybuk> do you see any udev output on the console?
[15:11] <doko> Keybuk: no
[15:12] <doko> only running process beisdes kernel processes is mountall
[15:15] <doko> hmm, /var is on it's own partition, mount says it's mounted ro, but it's not the partition (just see a lock and a run dir)
[15:15] <Keybuk> doko: mount lies until the root filesystem is mounted, remember
[15:15] <Keybuk> hmm
[15:15] <Keybuk> doko: what does "status udev" say?
[15:16] <doko> Keybuk: udev stop/waiting
[15:17] <Keybuk> try "start udev"
[15:17] <cjwatson> Keybuk: did you notice Steve uploaded mountall 0.1.5?
[15:18] <Keybuk> cjwatson: no
[15:18] <cjwatson> conversion to dh, probably supersedes your pending change if you're OK with it
[15:18] <Keybuk> argh, why the fuck did he do that?
[15:18] <cjwatson> so that we don't have to remember to use dh_installchangelogs?
[15:18] <Keybuk> you don't change people's packaging to another system without at least talking to them
[15:19] <cjwatson> 10:04 <slangasek> Keybuk: any good reason for me to not switch mountall to dh 7, so we don't have to worry about missing things like dh_installchangelogs in the future? :)
[15:19] <cjwatson> I guess he was in a rush or something
[15:19] <Keybuk> well, he can maintain it then
[15:20] <Keybuk> I'll reassign all the mountall bugs to him
[15:20] <doko> Keybuk: does start, then I get hundreds of messages "UNEXPECTED INCONSISTENCY, Superblock last mount time is in the future". after that I can't enter anything
[15:20] <cjwatson> gah


[00:00] -queuebot:#ubuntu-release- New binary: soplex [armhf] (noble-proposed/universe) [6.0.3+dfsg-1] (no packageset)
[00:03] -queuebot:#ubuntu-release- New binary: rust-deluxe [riscv64] (noble-proposed/universe) [0.5.0-1] (no packageset)
[00:04] -queuebot:#ubuntu-release- New binary: nanovg [riscv64] (noble-proposed/universe) [0.0~git20230826.f93799c+dfsg-1] (no packageset)
[00:07] -queuebot:#ubuntu-release- New binary: rust-libusb1-sys [riscv64] (noble-proposed/universe) [0.6.4-1] (no packageset)
[00:08] -queuebot:#ubuntu-release- New binary: soplex [arm64] (noble-proposed/universe) [6.0.3+dfsg-1] (no packageset)
[00:12] -queuebot:#ubuntu-release- New binary: rust-libpulse-glib-binding [riscv64] (noble-proposed/universe) [2.28.1-1] (no packageset)
[00:12] -queuebot:#ubuntu-release- New binary: rust-pyo3-filelike [riscv64] (noble-proposed/universe) [0.2.0-1] (no packageset)
[00:13] <vorlon> doko: why have you added boost1.81 on i386?
[00:20] <vorlon> arraybolt3: "maybe sometime today" - definitely no guarantee on that, we're past EOY for all the Canonical folks (and none of the non-Canonical folks are particularly active).  And I have a number of other things I'm working on that are more urgent (like, launching a transition in Debian for 600 libraries for 64-bit time_t)
[00:21] -queuebot:#ubuntu-release- Packageset: Removed boost1.81 from i386-whitelist in noble
[00:23] <vorlon> doko: ^^ removed again pending a rationale; boost1.83 is there by LocutusOfBorg's request because 1.83 is now boost-defaults in unstable, but I'm unaware of anything i386 that's blocked on boost1.81
[00:36] -queuebot:#ubuntu-release- Packageset: Added boost1.81 to i386-whitelist in noble
[01:31] -queuebot:#ubuntu-release- New binary: soplex [riscv64] (noble-proposed/universe) [6.0.3+dfsg-1] (no packageset)
[01:43] -queuebot:#ubuntu-release- New binary: rust-deluxe [s390x] (noble-proposed/universe) [0.5.0-1] (no packageset)
[01:43] -queuebot:#ubuntu-release- New binary: rust-libusb1-sys [s390x] (noble-proposed/universe) [0.6.4-1] (no packageset)
[01:48] -queuebot:#ubuntu-release- New binary: nanovg [s390x] (noble-proposed/universe) [0.0~git20230826.f93799c+dfsg-1] (no packageset)
[01:48] -queuebot:#ubuntu-release- New binary: rust-libpulse-glib-binding [s390x] (noble-proposed/universe) [2.28.1-1] (no packageset)
[01:50] -queuebot:#ubuntu-release- New: accepted nanovg [riscv64] (noble-proposed) [0.0~git20230826.f93799c+dfsg-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-deluxe [armhf] (noble-proposed) [0.5.0-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-deluxe [s390x] (noble-proposed) [0.5.0-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-libpulse-glib-binding [riscv64] (noble-proposed) [2.28.1-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-libusb1-sys [ppc64el] (noble-proposed) [0.6.4-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-libusb1-sys [s390x] (noble-proposed) [0.6.4-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-pyo3-filelike [riscv64] (noble-proposed) [0.2.0-1]
[01:50] -queuebot:#ubuntu-release- New: accepted soplex [arm64] (noble-proposed) [6.0.3+dfsg-1]
[01:50] -queuebot:#ubuntu-release- New: accepted soplex [ppc64el] (noble-proposed) [6.0.3+dfsg-1]
[01:50] -queuebot:#ubuntu-release- New: accepted nanovg [s390x] (noble-proposed) [0.0~git20230826.f93799c+dfsg-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-libpulse-glib-binding [ppc64el] (noble-proposed) [2.28.1-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-libusb1-sys [riscv64] (noble-proposed) [0.6.4-1]
[01:50] -queuebot:#ubuntu-release- New: accepted soplex [amd64] (noble-proposed) [6.0.3+dfsg-1]
[01:50] -queuebot:#ubuntu-release- New: accepted soplex [riscv64] (noble-proposed) [6.0.3+dfsg-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-deluxe [riscv64] (noble-proposed) [0.5.0-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-pyo3-filelike [ppc64el] (noble-proposed) [0.2.0-1]
[01:50] -queuebot:#ubuntu-release- New: accepted rust-libpulse-glib-binding [s390x] (noble-proposed) [2.28.1-1]
[01:50] -queuebot:#ubuntu-release- New: accepted soplex [armhf] (noble-proposed) [6.0.3+dfsg-1]
[01:50] -queuebot:#ubuntu-release- New: accepted bankstown-lv2 [amd64] (noble-proposed) [1.0.0-1]
[01:50] -queuebot:#ubuntu-release- New: accepted bankstown-lv2 [armhf] (noble-proposed) [1.0.0-1]
[01:50] -queuebot:#ubuntu-release- New: accepted elenv [amd64] (noble-proposed) [0.1.0+git20231106.e7619ff-1]
[01:50] -queuebot:#ubuntu-release- New: accepted licenserecon [amd64] (noble-proposed) [1.0]
[01:50] -queuebot:#ubuntu-release- New: accepted licenserecon [armhf] (noble-proposed) [1.0]
[01:50] -queuebot:#ubuntu-release- New: accepted minetest-mod-ltool [amd64] (noble-proposed) [1.6.1-1]
[01:50] -queuebot:#ubuntu-release- New: accepted nanovg [arm64] (noble-proposed) [0.0~git20230826.f93799c+dfsg-1]
[01:50] -queuebot:#ubuntu-release- New: accepted nanovg [ppc64el] (noble-proposed) [0.0~git20230826.f93799c+dfsg-1]
[01:51] -queuebot:#ubuntu-release- New: accepted r-cran-patrick [amd64] (noble-proposed) [0.2.0-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-deluxe [arm64] (noble-proposed) [0.5.0-1]
[01:51] -queuebot:#ubuntu-release- New: accepted bankstown-lv2 [arm64] (noble-proposed) [1.0.0-1]
[01:51] -queuebot:#ubuntu-release- New: accepted endesive [amd64] (noble-proposed) [2.16+dfsg-1]
[01:51] -queuebot:#ubuntu-release- New: accepted licenserecon [ppc64el] (noble-proposed) [1.0]
[01:51] -queuebot:#ubuntu-release- New: accepted nanovg [armhf] (noble-proposed) [0.0~git20230826.f93799c+dfsg-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-deluxe [amd64] (noble-proposed) [0.5.0-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-libpulse-glib-binding [amd64] (noble-proposed) [2.28.1-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-libpulse-glib-binding [armhf] (noble-proposed) [2.28.1-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-libusb1-sys [arm64] (noble-proposed) [0.6.4-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-pyo3-filelike [amd64] (noble-proposed) [0.2.0-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-pyo3-filelike [armhf] (noble-proposed) [0.2.0-1]
[01:51] -queuebot:#ubuntu-release- New: accepted deepdish [amd64] (noble-proposed) [0.3.7-1]
[01:51] -queuebot:#ubuntu-release- New: accepted nanovg [amd64] (noble-proposed) [0.0~git20230826.f93799c+dfsg-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-deluxe [ppc64el] (noble-proposed) [0.5.0-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-libusb1-sys [amd64] (noble-proposed) [0.6.4-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-pyo3-filelike [arm64] (noble-proposed) [0.2.0-1]
[01:51] -queuebot:#ubuntu-release- New: accepted licenserecon [arm64] (noble-proposed) [1.0]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-libpulse-glib-binding [arm64] (noble-proposed) [2.28.1-1]
[01:51] -queuebot:#ubuntu-release- New binary: rust-pyo3-filelike [s390x] (noble-proposed/universe) [0.2.0-1] (no packageset)
[01:51] -queuebot:#ubuntu-release- New: accepted r-cran-labelled [amd64] (noble-proposed) [2.12.0-1]
[01:51] -queuebot:#ubuntu-release- New: accepted rust-libusb1-sys [armhf] (noble-proposed) [0.6.4-1]
[01:58] -queuebot:#ubuntu-release- New binary: soplex [s390x] (noble-proposed/universe) [6.0.3+dfsg-1] (no packageset)
[04:40] -queuebot:#ubuntu-release- New: accepted rust-pyo3-filelike [s390x] (noble-proposed) [0.2.0-1]
[04:40] -queuebot:#ubuntu-release- New: accepted soplex [s390x] (noble-proposed) [6.0.3+dfsg-1]
[05:55] <vorlon> tsimonq2, Eickmeyer: uh /usr/share/applications/kde4/ubiquity-kdeui.desktop is the *actual filename* shipped in ubiquity-frontend-kde
[05:56] <Eickmeyer> vorlon: https://launchpadlibrarian.net/703887511/ubiquity_24.04.1_24.04.2.diff.gz
[05:58] <vorlon> Eickmeyer: ok - I only saw the casper diff not the ubiquity diff.  In any event, such a change doesn't belong being added onto an unrelated MP without being documented in the changelog
[06:01] <Eickmeyer> I mean, we're not stupid; we wouldn't have done one without the other.
[06:04] <vorlon> how should I know it wasn't an oversight, when the ubiquity changes are being made without following existing code review processes?
[06:17] -queuebot:#ubuntu-release- New: accepted icu [amd64] (noble-proposed) [74.2-1ubuntu1]
[06:17] -queuebot:#ubuntu-release- New: accepted icu [armhf] (noble-proposed) [74.2-1ubuntu1]
[06:17] -queuebot:#ubuntu-release- New: accepted icu [ppc64el] (noble-proposed) [74.2-1ubuntu1]
[06:17] -queuebot:#ubuntu-release- New: accepted icu [s390x] (noble-proposed) [74.2-1ubuntu1]
[06:17] -queuebot:#ubuntu-release- New: accepted icu [arm64] (noble-proposed) [74.2-1ubuntu1]
[06:17] -queuebot:#ubuntu-release- New: accepted icu [riscv64] (noble-proposed) [74.2-1ubuntu1]
[06:17] -queuebot:#ubuntu-release- New: accepted icu [i386] (noble-proposed) [74.2-1ubuntu1]
[06:20] -queuebot:#ubuntu-release- New binary: boost-defaults [amd64] (noble-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[06:20] -queuebot:#ubuntu-release- New binary: boost-defaults [ppc64el] (noble-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[06:20] -queuebot:#ubuntu-release- New binary: boost-defaults [i386] (noble-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[06:20] -queuebot:#ubuntu-release- New binary: boost-defaults [s390x] (noble-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[06:21] -queuebot:#ubuntu-release- New binary: boost-defaults [armhf] (noble-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[06:22] -queuebot:#ubuntu-release- New binary: boost-defaults [arm64] (noble-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[06:34] -queuebot:#ubuntu-release- New: accepted boost-defaults [amd64] (noble-proposed) [<IP_ADDRESS>ubuntu1]
[06:34] -queuebot:#ubuntu-release- New: accepted boost-defaults [armhf] (noble-proposed) [<IP_ADDRESS>ubuntu1]
[06:34] -queuebot:#ubuntu-release- New: accepted boost-defaults [ppc64el] (noble-proposed) [<IP_ADDRESS>ubuntu1]
[06:34] -queuebot:#ubuntu-release- New: accepted boost-defaults [arm64] (noble-proposed) [<IP_ADDRESS>ubuntu1]
[06:34] -queuebot:#ubuntu-release- New: accepted boost-defaults [s390x] (noble-proposed) [<IP_ADDRESS>ubuntu1]
[06:34] -queuebot:#ubuntu-release- New: accepted boost-defaults [i386] (noble-proposed) [<IP_ADDRESS>ubuntu1]
[06:40] -queuebot:#ubuntu-release- New binary: boost-defaults [riscv64] (noble-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[06:43] -queuebot:#ubuntu-release- New: accepted boost-defaults [riscv64] (noble-proposed) [<IP_ADDRESS>ubuntu1]
[07:54] <LocutusOfBorg> vorlon, now that we have boost-defaults defaulting on i386 we need it?
[07:55] <LocutusOfBorg> vorlon, can we please have some ghc removals so we can finally end this transition?
[07:55] <LocutusOfBorg> Debian migrated yesterday
[08:22] <vorlon> LocutusOfBorg: what do you mean, "boost-defaults defaulting on i386"?
[08:23] <vorlon> LocutusOfBorg: ghc removals> I've just yanked out ppc64el libghc*lua* that were missing according to update_excuses; this was slightly faster than working out binary package names from the list of source packages you gave.  you had some packages in the list you posted earlier that I can't see have removals required wrt ppc64el
[08:24] <vorlon> specifically, haskell-hedis?
[08:24] <vorlon> and I see lpeg is out of date, checking that now
[08:25] <vorlon> also I apparently forgot the '-a ppc64el' part, lovely
[08:25] <vorlon> but ^C is your friend
[08:25] <LocutusOfBorg> vorlon, I'm speaking about this
[08:25] <LocutusOfBorg> boost-defaults (<IP_ADDRESS>ubuntu7 to <IP_ADDRESS>ubuntu1)
[08:25] <LocutusOfBorg> now I presume d_oko will start issuing rebuilds after boost-defaults publishes and then stuff will need i386
[08:26] <vorlon> boost1.83 is already built on i386 https://launchpad.net/ubuntu/+source/boost1.83/1.83.0-1ubuntu2
[08:26] <LocutusOfBorg> maybe it would have been better to first merge boost-defaults and then add it to i386 list
[08:26] <LocutusOfBorg> I'm just trying to understand your sentence above
 doko: ^^ removed again pending a rationale; boost1.83 is there by LocutusOfBorg's request because 1.83 is now boost-defaults in unstable, but I'm unaware of anything i386 that's blocked on boost1.81
[08:27] <LocutusOfBorg> I don't know if I made any mistake in my request
[08:27] <vorlon> I'm talking about the fact that doko added boost1.8*1* to i386 whitelist, not boost1.8*3*
[08:27] <LocutusOfBorg> ohhhhhhhhhhhhhhhhhhhhh
[08:27] <LocutusOfBorg> I already had my coffee, probably I should get another one
[08:27] <LocutusOfBorg> anyhow, last blockers are:
[08:28] <LocutusOfBorg> nbconvert kick out or ignore autopkgtests (Debian bugs: #1042699 #1050667 #1057949)
[08:28] -ubottu:#ubuntu-release- Debian bug 1050667 in src:nbconvert "DSA for jupyter-core in oldstable triggers nbconvert autopkgtest" [Serious, Open] https://bugs.debian.org/1050667
[08:28] -ubottu:#ubuntu-release- Debian bug 1057949 in src:nbconvert "nbconvert: needs update for new version of pandoc: PDF creating failed" [Serious, Open] https://bugs.debian.org/1057949
[08:28] -ubottu:#ubuntu-release- Debian bug 1042699 in src:nbconvert "nbconvert: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting" [Serious, Open] https://bugs.debian.org/1042699
[08:28] <LocutusOfBorg> pypandoc, r--cran-flextable r-cran-rmarkdown ignore on ppc64el, they are related to lua support missing.
[08:29] <LocutusOfBorg> we can upload a fix to ignore testsuite, but we are confident that haskell lua will start building again on ppc64el in the future, so together with Debian release team we assumed that hinting the testsuite on ppc64el was better than hacking it, and forget about the hack later
[08:30] <LocutusOfBorg> so, with the 3 badtesting above we should be finally good to migrate, or at least britney will tell us something more
[08:32] <LocutusOfBorg> (btw haskell-hedis was fixed in the new ghc upload, fixing a ppc64el specific failure, the Debian bug should have the good list)
[08:33] <LocutusOfBorg> last thing, do you think we can stop building ocaml on i386?
[08:37] <vorlon> what still depends on it?
[08:38] <vorlon> it's late here, I don't have time to look at the autopkgtest ignores; I'll try to pick it up in the morning
[08:38] <vorlon> I don't see ocaml in the i386 list
[08:39] <vorlon> so yes, we have stopped building it; just needs cleanup of older binaries
[08:47] -queuebot:#ubuntu-release- Unapproved: cockpit (jammy-backports/universe) [306-1~bpo22.04.1 => 307-1~bpo22.04.1] (no packageset)
[08:47] -queuebot:#ubuntu-release- Unapproved: cockpit (lunar-backports/universe) [303-1~bpo23.04.1 => 307-1~bpo23.04.1] (no packageset)
[08:48] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (mantic-backports/universe) [300-1~bpo23.10.1 => 304-1~bpo23.10.1] (no packageset)
[08:48] -queuebot:#ubuntu-release- Unapproved: cockpit (mantic-backports/universe) [303-1~bpo23.10.1 => 307-1~bpo23.10.1] (no packageset)
[08:48] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (jammy-backports/universe) [303-1~bpo22.04.1 => 304-1~bpo22.04.1] (no packageset)
[08:48] -queuebot:#ubuntu-release- Unapproved: cockpit-podman (lunar-backports/universe) [79-1~bpo23.04.1 => 82-1~bpo23.04.1] (no packageset)
[08:48] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (lunar-backports/universe) [300-1~bpo23.04.1 => 304-1~bpo23.04.1] (no packageset)
[08:49] -queuebot:#ubuntu-release- Unapproved: cockpit-podman (mantic-backports/universe) [79-1~bpo23.10.1 => 82-1~bpo23.10.1] (no packageset)
[08:53] <vorlon> LocutusOfBorg: did a run of removals of unneeded i386 binaries, ocaml is gone now
[09:12] <doko> 1.81 was just to have something in the release pocket on i386 before the icu upload. it could have been removed later
[09:37] <LocutusOfBorg> yay!
[09:54] -queuebot:#ubuntu-release- New binary: r-cran-broom.helpers [amd64] (noble-proposed/universe) [1.14.0-1] (no packageset)
[10:02] -queuebot:#ubuntu-release- New: accepted r-cran-broom.helpers [amd64] (noble-proposed) [1.14.0-1]
[11:27] <LocutusOfBorg> missing build on ppc64el: libghc-hslua-marshalling-dev, libghc-hslua-marshalling-prof (from 2.1.0-2build1)
[11:27] <LocutusOfBorg> vorlon, ^^
[11:28] <LocutusOfBorg> also if possible the hints...
[11:28] <LocutusOfBorg> oops g night!
[11:29] <LocutusOfBorg> I didn't read
[11:59] <tsimonq2> vorlon: Ubiquity> In this case, following the existing code process would have been quite ineffective. MPs have been rejected recently for the desire to not put further effort into Ubiquity, and generally speaking, Foundations does *not* support Qt frontends for core applications. I know, because we've had critical bugs for Ubiquity, software-properties-qt, and more in the past, but were told to
[11:59] <tsimonq2> fix it ourselves if we wanted it done. All three Qt-based flavors feel this way, acutely with the new Flutter installer, which hardcodes GNOME items in, with us as an afterthought. We're used to it. It's not how it should be, but as the only Core Developer out of the three aforementioned flavors, I tend to take on reviews and queries specific to this. I was actively iterating on these changes
[11:59] <tsimonq2> with Erich, therefore we didn't file an MP. If you'd like us to file the paperwork regardless next time, fine, that's a valid point. As for, "well, this should have followed an MP process," no, we refuse to wait three months just to get a NACK.
[12:02] <tsimonq2> (Sorry, te_ward is also a Core Developer and he's on the Lubuntu Team, he's just not heavily involved with these sorts of things.)
[13:55] -queuebot:#ubuntu-release- New binary: node-jupyterlab [amd64] (noble-proposed/universe) [4.0.9+ds1+~cs3.4.4-1] (no packageset)
[14:09] <LocutusOfBorg> vorlon, please if you do the hints, rollback haskell-text-icu <IP_ADDRESS>-1build1 to the previous version and restore once the haskell is migrated
[14:10] <LocutusOfBorg> I don't think we want to entangle haskell with everything else
[14:13] <LocutusOfBorg> jbicha, gst-plugins ping :)
[16:02] <vorlon> tsimonq2: "MPs have been rejected recently for the desire to not put further effort into Ubiquity" [citation needed] https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquity/+ref/main/+merges?field.status=REJECTED&field.status-empty-marker=1
[16:03] <vorlon> there was one MP recently that I disapproved of because it was adding code in ubiquity for an UBUNTU image, which is not supposed to be using ubiquity by 24.04 release
[16:03] <vorlon> and "I don't want to use the review process because I don't like the review feedback from the (current) maintainers" is a poor excuse
[16:05] <vorlon> doko: I have no idea why "something in the release pocket on i386 before the icu upload" is supposed to be useful, for a package we don't need on i386 at all
[16:21] <vorlon> LocutusOfBorg: fwiw with the haskell lua ppc64el removals, I would expect those autopkgtests to also fail on baseline now, not requiring a hint
[16:21] <vorlon> (and this is what I'm trying now)
[16:26] <vorlon> LocutusOfBorg: marshalling> oops, I overlooked that marshal and marshalling are different :P
[16:28] <vorlon> temporarily rolling haskell-text-icu back to <IP_ADDRESS>-1 to unentangle icu vs ghc
[16:37] <doko> vorlon: there's also haskell-stringprep
[16:38] <vorlon> doko: thanks, rolling that back too
[16:44] <Eickmeyer> vorlon: ubiquity/casper> It would probably be in your best interest to not carry on that line of conversation any further as it's just showing to be anti-collaborative and disrespectful toward fellow developers, and placing unnecessary barriers for the sake of placing barriers. As I see it, it seems that you don't trust either one of us to do the
[16:44] <Eickmeyer> right thing, and for that we're both quite offended. Simon is a very competent developer which you seem to disregard and stifle regularily. So, perhaps before berating a Core Developer accepting a seemingly unrelated MP, check to see if the right thing was done first? And then, maybe instead of berating a Core Developer for maintaining
[16:44] <Eickmeyer> long-unmaintained code (the Qt frontend) that Foundations refuses to maintain, maybe you should thank him? If this is the system you support, then as I see it, it's very broken. There are a lot of eyes on you right now, so I'd be very careful about how you respond.
[16:53] <vorlon> Eickmeyer: the "right thing" for these packages is to use the established code review practices.  What's anti-collaborative is ignoring the established processes.  Once ubiquity is disentangled from main and no longer has ~ubuntu-installer as the maintainer, flavors can maintain it using whatever practices they want.  Or if someone wants to move the ubiquity KDE frontend to a separate source
[16:53] <vorlon> package and decouple it from ubiquity, that's fine too.  But casper remains in main and should be held to a high standard regarding not just the content of code changes but also the documentation (in changelog and commit messages) because of the sensitivity of the code in interacting with other packages.
[16:57] <LocutusOfBorg> vorlon, they need hint
[16:57] <LocutusOfBorg> they are not "BD-uninstallable"
[16:57] <LocutusOfBorg> on stderr there is a print
[16:57] <LocutusOfBorg> "247s RuntimeError: Pandoc died with exitcode "89" during conversion: This version of pandoc has been compiled without Lua support.
[16:57] <LocutusOfBorg> "
[16:57] <LocutusOfBorg> this is not something that will auto heal I would say with a ppc64el removal
[16:57] <LocutusOfBorg> right?
[16:57] <LocutusOfBorg> test_conversion_with_lua_filter is something that will fail in any case
[16:58] <vorlon> LocutusOfBorg: what changes is that the *baseline* regresses, so it's no longer a regression that blocks migration
[16:58] <vorlon> https://autopkgtest.ubuntu.com/packages/r/r-cran-rmarkdown/noble/ppc64el
[16:58] <LocutusOfBorg> but pandoc in release is probably built with lua support embedded
[16:59] <LocutusOfBorg> so, not sure if it will fail... in proposed it was split into a ton of pandoc-foo libraries
[17:00] <vorlon> well, at least one of them has also failed in release pocket on retry
[17:00] <vorlon> as this is preferred over hints, we'll see what happens with the other two
[17:00] <vorlon> and I'll add hints if necessary
[17:04] <LocutusOfBorg> thanks!
[17:06] <vorlon> LocutusOfBorg: and yeah, pypandoc passed in release pocket, feh - adding a hint
[17:07] <LocutusOfBorg> yeah that was my fear
[17:07] <vorlon> and oops the retry above that failed wasn't my no-proposed one at all, it was the spurious regular test against -proposed that I had to trigger to get fresh cookies out of autopkgtest.u.c :P
[17:08] <LocutusOfBorg> ok so now I understand, that was also my guess :)
[17:13] <LocutusOfBorg> r-cran-rmarkdown needs an hint
[17:13] <LocutusOfBorg> it didn't fail with migration-reference
[17:13] <vorlon> ack (boo)
[17:16] <LocutusOfBorg> and also r-cran-flextable succeeded with migration-reference/0
[17:16] <LocutusOfBorg> :/
[17:16] <vorlon> yeah, all hints added now
[17:16] <LocutusOfBorg> thanks, crossing fingers
[17:16] <LocutusOfBorg> I'll copy back the two packages if I see the migration
[17:17] <vorlon> ack
[17:18] <LocutusOfBorg> (the copy you did one hour ago didn't publish yet, strange)
[17:20] -queuebot:#ubuntu-release- New binary: appstream [amd64] (noble-proposed/main) [1.0.1-2] (core)
[17:22] -queuebot:#ubuntu-release- New binary: appstream [arm64] (noble-proposed/main) [1.0.1-2] (core)
[17:23] -queuebot:#ubuntu-release- New: accepted appstream [amd64] (noble-proposed) [1.0.1-2]
[17:23] -queuebot:#ubuntu-release- New: accepted node-jupyterlab [amd64] (noble-proposed) [4.0.9+ds1+~cs3.4.4-1]
[17:23] -queuebot:#ubuntu-release- New: accepted appstream [arm64] (noble-proposed) [1.0.1-2]
[17:23] -queuebot:#ubuntu-release- New binary: appstream [ppc64el] (noble-proposed/main) [1.0.1-2] (core)
[17:30] <LocutusOfBorg> whoever accepted appstream binaries please make sure you are not accepting into main pocket
[17:34] <vorlon> I used new-binary-debian-universe to accept them; if that put them in the wrong pocket, will be fixed up via https://ubuntu-archive-team.ubuntu.com/component-mismatches-proposed.html
[17:39] -queuebot:#ubuntu-release- New binary: r-cran-ggstats [amd64] (noble-proposed/universe) [0.5.1-1] (no packageset)
[17:41] -queuebot:#ubuntu-release- New: accepted appstream [ppc64el] (noble-proposed) [1.0.1-2]
[17:41] -queuebot:#ubuntu-release- New: accepted r-cran-ggstats [amd64] (noble-proposed) [0.5.1-1]
[17:41] <vorlon> N | libappstreamqt3 Component: main Section: libs Priority: OPTIONAL
[17:41] <vorlon> so yes it'll get cleaned up via component-mismatches
[17:46] <vorlon> LocutusOfBorg: so appstream-generator is in unstable now, but it's ftbfs on armhf/riscv64/s390x
[17:47] <vorlon> I mean, I guess I don't care too much, we're not going to be running the generator for Ubuntu itself on any of those archs
[17:47] <LocutusOfBorg> correct
[17:47] <LocutusOfBorg> no reverse deps
[17:48] <LocutusOfBorg> I'm waiting for Debian but if you want to remove in the meanwhile even better
[17:48] <vorlon> yeah, I'll just remove those
[17:48] <LocutusOfBorg> this should make ldc and appstream transition become NBS cleanable
[17:49] <vorlon> yep
[17:49] <LocutusOfBorg> (and haskell to migrate next round hopefully)
[17:49] <vorlon> have just uploaded libappindicator to drop gtk2 support (NBS) but that itself appears to have revdeps, me
[17:49] <vorlon> h
[17:49] <vorlon> afk for a couple hours (at least)
[17:50] <LocutusOfBorg> yay thanks for the help, I'm keeping fingers crossed
[18:02] <LocutusOfBorg> migrating ghc/9.4.7-2/amd64 to testing makes libghc-stringprep-dev/1.0.0-12build2/amd64 uninstallable
[18:02] <LocutusOfBorg> sigh
[18:02] <LocutusOfBorg> needing a new run
[18:55] <LocutusOfBorg> vorlon, if I can use your time... netcdf/i386 hint please?
[18:57] <LocutusOfBorg> real test was added, and fails now, from neutral to fail
[19:41] <LocutusOfBorg> Moving: haskell-ghc-typelits-knownnat/0.7.9-1build2
[19:41] <LocutusOfBorg> BRACE FOR IMPACT
[19:47] <vorlon> LocutusOfBorg: netcdf/i386> done
[19:47] <LocutusOfBorg> thanks!
[19:53] <LocutusOfBorg> libappstreamqt3/amd64 in main cannot depend on libqt6core6 in universe
[19:54] <LocutusOfBorg> vorlon, ^^ it should really go in universe indeed
[20:01] <vorlon> yeah. libappstreamqt-dev needs re-added to the Extra-Excludes.  Done now (after having just dropped it :P)
[20:21] <LocutusOfBorg> (haskell-stringprep and haskell-text-icu copied back!)
[20:22] <LocutusOfBorg> oh btw, src:signon can go away, all the binaries have been replaced and provided by src:signond from Debian
[20:23] <vorlon> LocutusOfBorg: do you mind a quick removal bug report for that one?
[20:24] <LocutusOfBorg> https://bugs.launchpad.net/ubuntu/+source/signon/+bug/2046971
[20:24] -ubottu:#ubuntu-release- Launchpad bug 2046971 in signon (Ubuntu) "RM signon from noble" [Undecided, New]
[20:24] <LocutusOfBorg> done :)
[20:24] <vorlon> Eickmeyer: fyi, related to your earlier casper mp https://code.launchpad.net/~vorlon/livecd-rootfs/+git/livecd-rootfs/+merge/457665
[20:26] <Eickmeyer> vorlon: Funny you should mention that. I managed to do the exact same thing using edubuntu-live-settings, all in a package, completely with actual installed files. I think the desktop team could do the same.
[20:36] <vorlon> ah, that's certainly an option; and you already had an edubuntu-live-settings package to add it to, so it makes a certain amount of sense there.  I was going to outline how the above hook would then be refactored to work for both edubuntu and ubuntu, and avoid code getting out of sync
[20:36] <vorlon> does ubuntustudio need anything in this regard still?
[20:37] <Eickmeyer> I'm still mulling over how to do the same thing using Plasma Desktop. It can certainly be scripted to do something like that using javascript, but I just need to remember what needs to be done. Since there's an ubuntustudio-live-settings package, I can just do it there.
[20:48] <Eickmeyer> vorlon: I am also considering adding an oft-requested minimal install option for Ubuntu Studio. Since it already has the core seed/metapackage, that would be the basis, so no new package necessary. It would, of course, require another MP for livecd-rootfs. Along with that, considering adding minimal+audio, minimal+video, and
[20:48] <Eickmeyer> minimal+graphics+photography options since the layering is quite easy.
[21:28] <vorlon> Eickmeyer: layers however form a tree; you can't have an 'everything' layer that inherits from all of audio+video+graphics+photography, so if you intend to offer 'everything' as an install option, you'll be doubling the size of the image
[21:34] <Eickmeyer> vorlon: True, and there's a lot to consider, and perhaps a refactoring of the tasks so that "everything" would be what is now the "desktop" tasks so that it doesn't layer, similar to how the "desktop-gnome" task for edubuntu is now.
[21:35] <Eickmeyer> I'm perhaps not being specific enough, but there's an idea in my head that doesn't add task upon task upon task.
[23:17] -queuebot:#ubuntu-release- New binary: libcotp [amd64] (noble-proposed/universe) [3.0.0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: rust-heed [amd64] (noble-proposed/universe) [0.20.0~alpha.9-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: rust-libgweather [amd64] (noble-proposed/universe) [4.3.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: libcotp [arm64] (noble-proposed/universe) [3.0.0-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: libcotp [ppc64el] (noble-proposed/universe) [3.0.0-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: libcotp [armhf] (noble-proposed/universe) [3.0.0-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: rust-heed [ppc64el] (noble-proposed/universe) [0.20.0~alpha.9-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: rust-libgweather [ppc64el] (noble-proposed/universe) [4.3.1-1] (no packageset)
[23:35] -queuebot:#ubuntu-release- New: accepted libcotp [amd64] (noble-proposed) [3.0.0-1]
[23:35] -queuebot:#ubuntu-release- New: accepted libcotp [armhf] (noble-proposed) [3.0.0-1]
[23:35] -queuebot:#ubuntu-release- New: accepted rust-heed [amd64] (noble-proposed) [0.20.0~alpha.9-1]
[23:35] -queuebot:#ubuntu-release- New: accepted rust-libgweather [amd64] (noble-proposed) [4.3.1-1]
[23:35] -queuebot:#ubuntu-release- New: accepted libcotp [arm64] (noble-proposed) [3.0.0-1]
[23:35] -queuebot:#ubuntu-release- New: accepted rust-heed [ppc64el] (noble-proposed) [0.20.0~alpha.9-1]
[23:35] -queuebot:#ubuntu-release- New: accepted libcotp [ppc64el] (noble-proposed) [3.0.0-1]
[23:35] -queuebot:#ubuntu-release- New: accepted rust-libgweather [ppc64el] (noble-proposed) [4.3.1-1]
[23:37] -queuebot:#ubuntu-release- New binary: rust-libgweather [arm64] (noble-proposed/universe) [4.3.1-1] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: rust-libgweather [armhf] (noble-proposed/universe) [4.3.1-1] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: rust-heed [arm64] (noble-proposed/universe) [0.20.0~alpha.9-1] (no packageset)
[23:39] -queuebot:#ubuntu-release- New binary: rust-heed [armhf] (noble-proposed/universe) [0.20.0~alpha.9-1] (no packageset)
[23:44] -queuebot:#ubuntu-release- New: accepted rust-heed [arm64] (noble-proposed) [0.20.0~alpha.9-1]
[23:44] -queuebot:#ubuntu-release- New: accepted rust-libgweather [arm64] (noble-proposed) [4.3.1-1]
[23:44] -queuebot:#ubuntu-release- New: accepted rust-heed [armhf] (noble-proposed) [0.20.0~alpha.9-1]
[23:44] -queuebot:#ubuntu-release- New: accepted rust-libgweather [armhf] (noble-proposed) [4.3.1-1]
[23:48] <vorlon> xnox: Debian bug #737634 was wontfix'ed 9 years ago, and the TC issued advice a year ago that was not taken by the Debian maintainer.  Is it still useful to carry this delta?
[23:48] -ubottu:#ubuntu-release- Debian bug 737634 in dpkg "dpkg: Allow overriding is_native version checks in dpkg 3.0 Native." [Wishlist, Open] https://bugs.debian.org/737634


[12:25] <BluesKaj> Hi all
[14:06] <ahoneybun[m]> heyo BluesKaj
[14:09] <BluesKaj> hey ahoneybun[m]
 So no fixes for this as of now? (re @IrcsomeBot: <mmikowski> myfenris: 10th and 11th gen i915 is generally solid. It gets tricky in 12th- and 13th-gen. So that's likely not it.)
[16:55] <mmikowski> myfenris: If you are not seeing i915 errors in the syslog, then that's not likely to be causing a desktop hang, especially if you are using a 10th gen processor. We would need to know more about the problem to be able to advise on how to fix it. The best thing to do would be to file a bug on how to reproduce  and detailing your configuration.
[17:21] <mmikowski> myfernris: You could post the bug here too! :)
[22:19] <arraybolt3> mmikowski: Have you noticed that Discover no longer gives update notifications on Plasma 5.27? I've had to switch to manually updating the system.
[22:38] <mmikowski> arraybolt3: No, I hadn't.
[22:38] <mmikowski> Lemme check