[08:54] <mib_04cywaog> i want compile gcc 2.95.3 but i cant compile on ubuntu 6.10
[09:44]  * e-jat brb .. zzZZzz sleepy ..
[09:45]  * e-jat back ..
[09:46] <stdin> bad e-jat, bad
[09:46] <e-jat> sorry
[09:46] <e-jat> typo
[09:47]  * jussi01 gigles and wonders how many times e-jat got told off for that...
[09:47] <e-jat> hmm ..
[09:47] <Myrtti> tsk tsk
[09:47] <Myrtti> naughty
[09:49] <e-jat> no la .. im not naughty ..
[09:49] <e-jat> :]
[18:02] <nemphis> hi all
[18:04] <nemphis> may i ask someone of the ubuntu irc team to give me the irc cloak? (https://launchpad.net/~nemphis)
[18:10] <Pici> nemphis: Have you followed all of the steps here: http://freenode.net/faq.shtml#nicksetup ?
[18:10] <nemphis> Pici: yes
[18:10] <Pici> nemphis: okay
[18:11] <Pici> nalioth, PriceChild, ping for nemphis cloak
[18:11] <Pici> nemphis: also, congrats on membership
[18:11] <nemphis> Pici: thank you :)
[19:08] <blizzz> hi, i became kubuntu member last wednesday and thus want to ask for the irc cloak. my launchpad profile is here: https://launchpad.net/~blizzz
[19:09] <Ekushey> congrats blizzz :)
[19:10] <blizzz> Ekushey: thank you :)
[19:10] <Myrtti> blizzz: have you followed this http://freenode.net/faq.shtml#nicksetup guide?
[19:10] <Ekushey> PriceChild can set the cloak for you... talk to him when he's online
[19:10] <blizzz> not yet
[19:10] <Myrtti> you need to complete all the steps, including setting up an email address, alternate nick etc.
[19:11] <Ekushey> hi Myrtti :)
[19:11] <Myrtti> hi Ekushey :-)
[19:12] <blizzz> Myrtti: i match the requirements
[19:12] <blizzz> Ekushey: i will, ty
[19:12] <Ekushey> my pleasure, and congrats again :)
[19:12] <Myrtti> PriceChild, nalioth ^
[19:13] <Ekushey> Myrtti, too bad you stepped down
[19:13] <blizzz> :)
[19:13] <Myrtti> Ekushey: took three days to consider, I think I did the correct choice under the circumstances
[19:14] <Ekushey> Myrtti, ok :(
[19:17] <nalioth> blizzz: you need to set an email, please
[19:17] <Ekushey> i've a question, what is the difference between ubuntu membership and kubuntu membership?
[19:18] <Ekushey> nalioth, you can set the cloak too?
[19:18] <nalioth> Ekushey: what cloak?
[19:18] <blizzz> nalioth: for my freenode account? musn't there be one already?
[19:19] <nalioth> blizzz: /msg nickserv info blizzz
[19:19]  * nalioth does not waste time asking for things that are already done
[19:19] <Ekushey> nalioth, ubuntu cloak?
[19:19] <nalioth> Ekushey: for you?
[19:19] <blizzz> indeed
[19:19] <Ekushey> nalioth, no no i already have it
[19:19] <nalioth> Ekushey: i'm lost then.
[19:21] <blizzz> nalioth: you don't have the command to set the adress, have you?
[19:21] <Ekushey> nalioth, i just want to know how many people can set the cloak so that i can tell others who might want to know
[19:21] <Myrtti> blizzz: you need to setup the email-address
[19:22] <nalioth> blizzz: /msg nickserv help set email
[19:22] <nalioth> Ekushey: they've been calling me all morning
[19:22] <nalioth> Ekushey: the folks here know
[19:23] <Pici> Ekushey: Any members of the IRCC can have a staffer set a Ubuntu cloak, its just easier to ask pric-ey and nal because they are staffers as well.
[19:23] <Ekushey> Pici, that answers my question :)
[19:36] <blizzz> nalioth: had some trouble with the greylist... anyway, email is set now
[19:50] <blizzz> thank you all
[19:50] <Myrtti> no probs
[19:50] <Myrtti> and congratulat...
[19:50]  * Myrtti shrugs and continues to compile bitlbee


[09:25] <Blu2> Ever took in consideration to make the top bar transparent and only fill it only when in fullscreen mode in Unity 8?
[09:46] <Saviq> Blu2, by "top bar" you mean the panel with menus and indicators? depending on the wallpaper, it could be really difficult to make out the details of the icons
[09:47] <Saviq> and when you expand a menu, would you fill the panel, too? or leave the menu "hanging" in void?
[10:03] <Blu2> Yeah it obvious has some problems, but if app windows had different colors and the top bar adapting it would be nice, like on andorid and ios
[10:04] <Blu2> I'm suggesting this for the visual appearance, it's "in" that the DE is as much in the background as possible
[10:05] <Blu2> like in chromeOS
[10:09] <Saviq> Blu2, we have a plan for that in the new unity8 interface, but that requires cooperation from the app, so that it doesn't draw when we're drawing indicators next
[10:09] <Saviq> so it will be opt-in
[10:14] <Blu2> another idea I had was putting everything (clock, networking, langeugae select notification center etc) as an icon in the launcher
[13:00] <Saviq> Mirv, hey, did we get the fix for https://bugreports.qt.io/browse/QTBUG-54822 into xenial/overlay's Qt?
[13:19] <Saviq> mzanetti, is what's written in https://code.launchpad.net/~mzanetti/unity8/appdrawer-improvements/+merge/313139 as commit message all that this branch changes? seems bigger :)
[13:58] <Mirv> Saviq: no, it's not even in 5.6.2 but in 5.6.3 to be released in a few months. and when I tried backporting the fix to 5.6.1, stuff started exploding in colorful ways. so we are stuck with the slightly config modified arm64 kernels that are installed on builders. however 5.7.1 seems fine so hopefully that means 5.6.3 will be too.
[13:59] <Saviq> Mirv, right, that just makes us unable to run arm64 CI on xenial :/
[13:59] <Saviq> ohwell
[16:28] <Blu2> Will icons be interactive eventually? like calendar showing the actual date


[00:00] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_baloo build #24: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/disco_unstable_baloo/24/
[00:34] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_kdevelop build #20: STILL UNSTABLE in 46 min: https://kci.pangea.pub/job/disco_unstable_kdevelop/20/
[00:36] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_plasma-desktop build #35: UNSTABLE in 35 min: https://kci.pangea.pub/job/disco_unstable_plasma-desktop/35/
[00:59] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_kphotoalbum build #18: STILL UNSTABLE in 44 min: https://kci.pangea.pub/job/disco_unstable_kphotoalbum/18/
[01:00] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kwin build #307: UNSTABLE in 48 min: https://kci.pangea.pub/job/bionic_stable_kwin/307/
[01:47] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_plasma-desktop build #353: UNSTABLE in 46 min: https://kci.pangea.pub/job/bionic_stable_plasma-desktop/353/
[02:08] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_syntax-highlighting build #23: STILL UNSTABLE in 43 min: https://kci.pangea.pub/job/disco_unstable_syntax-highlighting/23/
[03:57] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_phonon build #18: STILL UNSTABLE in 53 min: https://kci.pangea.pub/job/disco_unstable_phonon/18/
[04:57] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_kwindowsystem build #19: STILL UNSTABLE in 1 hr 0 min: https://kci.pangea.pub/job/disco_unstable_kwindowsystem/19/
[11:30] <BluesKaj> Hey folks
[11:48] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_plasma-workspace build #30: UNSTABLE in 24 min: https://kci.pangea.pub/job/disco_unstable_plasma-workspace/30/
[11:50] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2726: SUCCESS in 1 min 6 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2726/
[11:50] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2726: SUCCESS in 1 min 35 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2726/
[11:53] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2726: SUCCESS in 4 min 31 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2726/
 All of plasma 5.15 beta (5.14.90) is now in disco release pocket
[13:27] <mparillo> Release pocket means no PPAs needed?
[13:40] <IrcsomeBot4> <Lazy B> Yes
[13:48] <mparillo> Thanks. I removed my staging PPAs, and discover still re-installed 5.14.90. Is there something subtly different between the 5.14.90 from staging-plasma and the 5.14.90 from the release pocket?
[13:53] <BluesKaj> mparillo, acheronuk, release pocket?
[13:56] <mparillo> BluesKaj: It appears to me that if you are running an updated daily image (DD, to become 19.04) you now get Plasma 5.14.90, which is the beta for 5.15. Previously, I had to add the PPAs for staging-plasma and staging-frameworks. Then (yesterday or the day before) there was an announcement that you could add the beta PPA instead. Now it is simply available without a PPA.
[13:59] <BluesKaj> mparillo, i just ran a full-upgrade , but my pasma version is still 5.14.5
[14:00] <BluesKaj> do I need to uncomment the partners deb source
[14:00] <BluesKaj> ?
[14:03] <BluesKaj> backports are active
[14:04] <mparillo> I do not have Partners and I do not have backports for DD.
[14:08] <BluesKaj> so i guess i have to download the beta image
[14:11] <mparillo> You mean the daily ISO? I am not certain. I believe you generally just sed your sources changing cosmic to disco ?
[14:12] <BluesKaj> I'm on disco
[14:15] <acheronuk> mparillo: yesterday the test queues were very long, so I didn't know how long it would take to get to release pocket in the archive. hence putting it in a ppa as well, where proposed would not be needed
[14:15] <acheronuk> but it went quicker than I thought :)
[14:16] <BluesKaj> guess ill check the ppa
[14:16] <acheronuk> BluesKaj: may need a little while to sync to mirrors
[14:17] <acheronuk> PPA build for disco have gone now
[14:17] <mparillo> Thanks. Do you know why discover wanted to re-install 5.14.90?
[14:17] <acheronuk> re-install?
[14:18] <mparillo> I already had 5.14.90 from staging-plasma. I removed staging-plasma from my sources, but discover wanted to install 5.14.90 anyway.
[14:18] <acheronuk> replacing a ppa build with the archive one?
[14:18] <mparillo> Exactly. Is that working as designed?
[14:19] <acheronuk> if the archive version is higher, it will always want to install that
[14:20] <mparillo> They were both 5.14.90, but was there something else (maybe in the package name?) that made the archive version higher?
[14:21] <acheronuk> mparillo: the ppa version has ~ubuntu19.04~ppa after it
[14:21] <acheronuk> the ~ is treated specially to make that lower version than the same version without
[14:22] <mparillo> Thanks, so that is how discover 'knew' to upgrade me to the archive version. Thanks.
[14:26] <BluesKaj> acheronuk, yeah, the ppa says newer versions of the listed packages are available individually, so i'll wait
[14:27] <BluesKaj> on staging
[14:36] <BluesKaj> ok , changed my sources in discover to main server and plasma upgraded to 5.14.9
[14:48] <BluesKaj> ok, successful reboot, all seems weel with 5.l4.9
[14:48] <BluesKaj> well even
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2727: SUCCESS in 54 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2727/
[15:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2727: SUCCESS in 1 min 39 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2727/
[15:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2727: SUCCESS in 4 min 22 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2727/
[18:07] <ysteins> Will translations for Kubuntu-specific packages eventually be merged into Disco? Wondering because I translated the installer slideshow in the summer, but they were never merged into Cosmic. I thought the deadline for translations was close to release?


[12:28] <onilmaurya> i m new to ubuntu plz help me to install JMF api to java
[12:29] <onilmaurya> plz reply
[23:22] <micahg> doko: are you still around?
[23:26] <doko> micahg: what's up?
[23:27] <micahg> doko: hi, what's the trick to regenerate the control file for each series?
[23:27] <doko> touch debian/control.in; debian/rules debian/control
[23:27] <micahg> doko: k, in a chroot for each series?
[23:27] <doko> yes
[23:28] <micahg> doko: k, thanks, I'll try it this weekend


[06:25] <JackFrost> https://github.com/net-ssh/net-ssh/issues/843 sounds like bad news for net-ssh and OpenSSL 3.0. :3
[06:56] <cpaelzer> mwhudson: there is no way to do that yet
[06:57] <cpaelzer> mwhudson: we might add such a feature, but how should it be handled - a list of known special cases maybe
[06:58] <cpaelzer> mwhudson: where is that size a pain, just for the time to clone or for the space on your disk after cloning or are there more problems with that?
[06:59] <cpaelzer> in general - especially given that we close in on EOY - I'd suggest to file a bug here https://bugs.launchpad.net/usd-importer/+bugs to not forget about it
[12:19] <ddstreet> mapreri i approved the u-d-t uploads for h/i
[12:20] <ddstreet> however for debhelper in f (and b), it looks like doko uploaded it to j with a -nc so the .pot file wasn't correctly updated, so the backport has a sizable debdiff (though the backport is *correct* since the debhelper in jammy shouldn't have been uploaded after a -nc source build)
[12:21] <ddstreet> i think doko might be gone for the rest of the year, i don't see him here, so i may just upload a new debhelper to jammy that's correct
[12:24] <ddstreet> techinically i don't think it's really important, so maybe it's something that can just be ignored in the backports
[12:26] <ddstreet> mapreri also, the u-d-t upload in f has the wrong ~bpo suffix, so i rejected that, looks fine otherwise
[13:47] <mapreri> ddstreet: oh, thanks for catching the u-d-t wrong suffix!
[13:47] <mapreri> ddstreet: tbh I didn't notice the .pot not regenerated, I'd probably ignore it tbh
[14:12] <ddstreet> mapreri agreed, the backported one is actually the correct one, so i'll accept that and let foundations fix the one in jammy themselves
[14:13] <mapreri> ddstreet: FYI: my workflow there has been to start from the debian git repo, import the jammy .dsc, --bpo that, build.
[14:19]  * mapreri also finds funny how I can upload debhelper/focal-backports but not debhelper/jammy - luckily this will soon be "fixed" :3
[14:57] <ddstreet> mapreri in the debhelper upload for b, what's the reference "See ##1001403." ?
[15:08] <mapreri_mobile> ddstreet: I guess I copy-pasted an extra #... But regardless, that's a bug number?
[15:08] <mapreri_mobile> (sorry if I'm misunderstanding your question)
[15:08] <ddstreet> mapreri_mobile that was my first assumption, but the bug is from 2012 and doesn't seem related? assuming it's a lp bug...
[15:08] <ddstreet> i didn't think the debian bug numbers were that high yet?
[15:09] <mapreri_mobile> Ah
[15:09] <mapreri_mobile> Yes, it's bugs.d.o
[15:09] <mapreri_mobile> We got to 1M a couple of weeks ago :)
[15:09] <ddstreet> oh wow!
[15:09] <mapreri_mobile> Heh
[15:09] <ddstreet> lol well i see it now, sorry :)
[15:10] <mapreri_mobile> I also didn't see it coming tbh, considering I remember filing bugs on the 7xxk range not so long ago 😵😸
[15:11] <ddstreet> yeah i feel like it jumped very quickly there!
[15:11] <ddstreet> but that's probably just me :)
[15:11] <mapreri_mobile> I blame some pseudo-automated bugs, we didn't have so many bugs few years ago
[15:11] <mapreri_mobile> Go blame autopkgtests, mass rebuilds, etc
[15:12] <mapreri_mobile> Where are the times when we discovered a ftbfs years after it started happening!
[15:36] <ed__> hello, i believe that debian bug #994103 is fixed now. please can someone sync rust-pleaser to confirm?
[16:02] <mapreri> ed__: do you have a lp account I can mark the sync as sponsored for?
[16:02] <mapreri> or i can just do it in my name
[16:15] <ed__> mapreri: yeah, edneville
[16:26] <mapreri> % syncpackage -f -s edneville rust-pleaser
[16:26] <mapreri> Source rust-pleaser -> jammy/Proposed: current version 0.4.1-2ubuntu1, new version 0.5.1-1
[16:26] <mapreri> ed__: .
[16:33] <ed__> thanks mapreri!
[16:38] <mapreri> ed__: btw, you didn't close the debian bug with your upload.  please send the relevant control@ command (or mail -done@, etc)
[17:28] <ed__> mapreri: done, thanks again!
[18:19] <juliank> grub 2.06 has landed in release pocket :party-tux:
[18:19] <juliank> may your system refuse to boot
[19:35] <rbasak> mwhudson, cpaelzer: I'd really prefer not to special case it. If we ship pristine-tar branches in general, I don't want to break that expectation on random packages. That breaks workflows, and part of the point is to unify them from the various different ways Debian maintains VCSs across different packages.
[19:36] <rbasak> If it's not wanted then maybe we could find a way to configure the client to avoid fetching those refs in the cases where you don't want them. Would that work for you?


[17:13] <jaimani_almjz> hi
[17:14] <jaimani_almjz> Im a beginner at java and would like to know if you could point me to some open source java projects with which i can learn real world java development ?
[17:15] <jaimani_almjz> Thank you


[20:28] <zequence> we're getting lmms 1.0 in, all though it hasn't landed in Debian yet.
[20:28] <zequence> bug 1291675
[20:43] <Noskcaj> zequence, Are you going to use 1.0 or 0.9.92?
[20:59] <zequence> Noskcaj: It's practically 1.0 :). I can only vouch for what I've tested, and that version was ok for me.
[21:00] <zequence> (0.9.92)
[21:02] <Noskcaj> ok


[14:29] <realtime-neil> What's the `autoinstall` way of embedding a `seedfrom=...` into the `*.iso`? I'm used to putting my `preseed.cfg` at the top of the iso9660 archive and pointing the kernel at `file=/cdrom/preseed.cfg`.
[15:11] <realtime-neil> looks like what I want is `ds=nocloud;seedfrom=file:///cdrom/`, according to https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
[15:11] <realtime-neil> Anyone here doing something like that?
[15:11] <xnox> well the image itself does that by default anyway.
[15:12] <realtime-neil> xnox: Where does that default live, exactly?
[15:12] <xnox> if you are modying installer.squashfs you will find that it already has empty files you can modify the
[15:12] <xnox> 0	./var/lib/cloud/seed/nocloud/meta-data
[15:12] <xnox> 0	./var/lib/cloud/seed/nocloud/user-data
[15:12] <xnox> inside casper/installer.squashfs
[15:13] <xnox> maybe we should have put them straight on the iso with a comment "change me if you want to modify the baked in nodata cloud datasource"
[15:20] <realtime-neil> xnox: okay, understood ... fwiw, I understood the baked-in `/boot/grub/grub.cfg` params better, but I can work with this, too.
[15:22] <xnox> realtime-neil:  it should work to drop your own seed onto toplevel cdrom, and make your own custom grub.cfg with ds=nocloud;....
[15:22] <xnox> realtime-neil:  unless bugs =)
[15:23] <xnox> realtime-neil:  depends if you are already modifying installer.squashfs or not, and if calling mksquashfs to append two files to it is easy or not.
[15:24] <realtime-neil> xnox: good to know, thanks. Is there a facility to tell `user-data` to wrap a "legacy" preseed.cfg, or does the new `autoinstall` schema (https://ubuntu.com/server/docs/install/autoinstall-reference) only allow The New Way?
[15:29] <realtime-neil> I'm looking for a way to slide into this brave new autoinstall world with my old preseeds intact and then iteratively migrate them into modernity
[15:44] <xnox> realtime-neil:  impossible.....
[15:44] <realtime-neil> shucks.
[15:44] <xnox> realtime-neil:  1) is turning complete programming language 2) is declarative yaml syntax => the two are incompatible.
[15:45] <xnox> realtime-neil:  for example, it is impossible to know which questions preseed will ask, in which order, how many times, and which answers it expects.
[15:45] <xnox> realtime-neil:  a lot of preseeds fail on unclean disks and questions like "do you want to disable swap?" "i wound LVM with the same group name, what do you want me to do?" etc.
[15:46] <xnox> realtime-neil: preseeds are extremely fragile, especially if one reinstalls the same build over the top of the old one =/
[15:46] <xnox> realtime-neil:  and partman way to specify disk layouts is really akward, hence we ditched that.
[15:46] <xnox> autoinstall yaml is a hope to get things right.
[15:47] <realtime-neil> I don't doubt that's true, but certainly the case is easier for those installations that nuke whatever is on disk every time?
[15:55] <xnox> realtime-neil:  the old d-i, doesn't know how to nuke things. And there ware ghost things that reappear that it doesn't know how to deal with. I.e. partial volume groups, partial left-over raids, etc.
[15:56] <xnox> realtime-neil:  and it asks more questions when things like that appear. Or like demands one specifies UUID of the lvm group to purge, which one cannot preseed. Thus resulting in hanging the preseed installation at an interactive prompt.
[15:56] <xnox> it really freaks out if it creates a partition table, and somehow lvm group reappears in the place where the fresh partition is created.
[15:57] <xnox> (because well, it was still there, at the same offset)
[16:05] <realtime-neil> xnox: is it by design or just dumb luck that I've been able to avoid the problems you've mentioned with the `d-i partman*` preseed directives shown here: https://paste.ubuntu.com/p/G4wFNDr4nr/
[16:07] <realtime-neil> Note that the referenced `d-i partman/early_command` is effectively a no-op I use to `chvt 4` sometimes.