[15:00] <barry> o/
[15:00] <tdaitx> \o
[15:01] <cyphermox> o/
[15:01] <robru> o-
[15:01] <sil2100> \o
[15:01]  * slangasek waves
[15:02] <slangasek> #startmeeting
[15:02] <meetingology> Meeting started Thu Aug  4 15:02:34 2016 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:02] <meetingology> Available commands: action commands idea info link nick
[15:02] <slangasek> [TOPIC] Lightning round
[15:02] <slangasek> $ echo $(shuf -e barry doko bdmurray slangasek caribou infinity sil2100 robru cyphermox pitti tdaitx xnox chiluk mwhudson)
[15:03] <slangasek> bdmurray pitti mwhudson robru chiluk barry cyphermox infinity xnox slangasek doko caribou tdaitx sil2100
[15:03] <slangasek> and... go
[15:03] <sil2100> Phew, will have time to prep my notes at least
[15:03] <bdmurray> irc discussion regarding the haproxy charm, switched one being used
[15:03] <bdmurray> worked on utilizing swift for ET code storage in mojo spec
[15:03] <bdmurray> worked on RT re Lift and shift error-tracker staging environment
[15:03] <bdmurray> updated meta-release files for X point release and W EOL
[15:04] <bdmurray> ubuntu-release-upgrader bug triage
[15:04] <bdmurray> reported, fixed update-manager bug regarding hwe-support-status (LP: #1607983)
[15:04] <bdmurray> built, tested, uploaded update-manager w/ HWE support for Trusty
[15:04] <bdmurray> ✔ done
[15:04] <bdmurray> research into adding update-notifier hwe support for Trusty
[15:05] <slangasek> pitti is off
[15:05] <slangasek> mwhudson is in the shadow of the sun
[15:05] <slangasek> robru:
[15:05] <robru> ah
[15:05] <robru> lp:bileto
[15:05] <robru> * big cache expiry cleanup. better logging, more aggressive purging, purging some caches that were previously overlooked and growing without bound
[15:05] <robru> * pretty display for merge targets when there are too many
[15:05] <robru> * fix race condition when deciding when to branch and when to pull local bzr caches
[15:05] <robru> * fix discovery of arches to consider for regressions when overlay PPA supports fewer arches than distro
[15:05] <robru> * serialize some overly-parallelized 'bzr missing' invocations that were hammering LP too hard
[15:05] <robru> * decrease status updater from 15 minutes to 20 minutes also due to too-high load
[15:05] <robru> * new page that only shows failure logs now that status job is spamming the "all logs" page
[15:05] <robru> * make britney skip QA-approved tickets in addition to the already skipped britney-approved tickets, halving britney run time from 1hr to 30 minutes.
[15:05] <robru> * fix race condition where status job reports stale status too soon after build job triggered, so people stop getting confused and building twice in a row for no reason
[15:05] <robru> * change instance_id from uuid to md5sum of html/js/css assets so forced page reloads stop happening when assets haven't changed
[15:05] <robru> * several iterations on CSS based on user feedback; now status/signoffs have independant coloring, and icons, rather than trying to choose one color based on the whole ticket status
[15:06]  * xnox shakes fist at the sun shadow
[15:07] <slangasek> robru: cache expiry cleanup> so things that were being cached that should have been cleaned up when a ticket was closed out (landed/dropped) but weren't?
[15:07] <chiluk> lp 1607920 : zfs failure on first boot due to missing /etc/mtab.  Will be fixing upstream to use /proc/self/mounts, and then SRU back into Ubuntu.
[15:07] <chiluk> Vacation Monday, Tuesday, off again Friday (lasik)
[15:07] <chiluk> -done-
[15:07] <barry> ubuntu-image: gadget.yaml branch; snap weld branch; test fixing branches; more-parsing branch; LP: #1605434
[15:07] <slangasek> "missing /etc/mtab" pff ancient software
[15:07] <barry> debuntu: voluptuous 0.9.2-1, 9.3-1, syncpackage; xonsh 0.4.4+dfsg-1 sponsorship; zope.interface 4.2.0-2
[15:07] <barry> --done--
[15:08] <chiluk> yeah.. it should've been fixed long ago.
[15:08] <robru> slangasek: yeah some lplib cache files were being kept forever, that got up to 200MBs until I started pruning it, also it was keeping britney indexes forever eg so we had trusty index files despite the fact that no trusty tickets were using britney for a while, so I started cleaning those up
[15:08] <chiluk> but there's a lot of logic around it and processing it.
[15:08] <slangasek> robru: oh interesting, I thought lplib did its own cache management properly
[15:08] <slangasek> well, I mean, I wouldn't be surprised if I have a 200MB cache here :)
[15:09] <robru> slangasek: yeah that was my assumption too but I've been watching the lplib cache expand for a long time, it started at 2MBs and just got bigger and bigger
[15:09] <robru> slangasek: it was growing by about 2MBs/day, now I delete all files older than 24 hours and the size hovers at 120MB
[15:10] <slangasek> cyphermox:
[15:10] <cyphermox> yup
[15:10] <cyphermox> MIR:
[15:10] <cyphermox> - review barbican (bug LP: #1543754)
[15:10] <cyphermox> - review content-hub (bug LP: #1597453)
[15:10] <sil2100> Didn't know lplib was such a beast
[15:10] <cyphermox> - review libpod-constants-perl
[15:10] <cyphermox> - review network-manager-openvpn (bug LP: #1574576)
[15:10] <cyphermox> trusty:
[15:10] <cyphermox> - NVMe SRU for ubiquity installer (bug LP: #1600308)
[15:10] <cyphermox> xenial:
[15:10]  * bdmurray thought everybody knew
[15:10] <robru> sil2100: bileto uses it rather aggressively
[15:10] <cyphermox> - grub2 efi ipv6 patch backports (bug LP: #1229458)
[15:10] <cyphermox> yakkety:
[15:10] <cyphermox> - merge / review choose-mirror
[15:10] <slangasek> yay phone MIRs \o/
[15:10] <cyphermox> - packagekit 1.1.1 no-change rebuilds
[15:10] <cyphermox> - discussion/planning shim work with pjones
[15:10] <cyphermox> - review ubiquity gtk3.20 changes from Laney
[15:10] <cyphermox> - fixup ubiquity ftbfs and error in nvme regex
[15:11] <cyphermox> - investigated porting click to packagekit 1.1.1
[15:11] <cyphermox>   - looks like maybe just a no-change rebuild will do, have yet to test from a PPA package
[15:11] <robru> my local lplib cache is only 18MBs, heh
[15:11] <cyphermox> other stuff:
[15:11] <cyphermox> - setting up snap build for canonical-foundations
[15:11] <cyphermox> - shim Secure Boot prompting improvements (bug LP: #1595611, bug LP: #1604936)
[15:11] <cyphermox> - some NetworkManager DNS issue with VPNs not in split-tunnelling.
[15:11] <cyphermox> - helped out slashd with packaging issues (mostly answering questions)
[15:11] <cyphermox> - waiting for a shim signature
[15:11] <cyphermox> yeah, phone MIRs, I'm a bit behind in reviewing MIRs so I took a bite from my list :)
[15:11] <cyphermox> (done)
[15:12]  * sil2100 gently pokes infinity
[15:12] <slangasek> cyphermox: don't know if it's been mentioned anywhere to you, but the goal from the client side is to have the unity8 stack on the desktop image as a non-default session by 16.10, so there'll be a few more MIRs coming :)
[15:13] <cyphermox> slangasek: I know! no problem, I don't mind reviewing them
[15:13] <slangasek> right :)
[15:13] <sil2100> We moving unity8 stuff to main now?
[15:13] <slangasek> sil2100: yes
[15:13] <cyphermox> it takes a bit of time, maybe I'm a little more thorough than I should by doing some code review, but hey
[15:13] <sil2100> Wow, didn't hear there was a final decision to do that now finally
[15:13] <sil2100> I might want to help with that
[15:13] <slangasek> long overdue, and the security team has been looped in to triage things globally wrt what is going to need deep security review and when
[15:14]  * slangasek pokes infinity less gently than sil2100
[15:14] <cyphermox> he wasn't responding earlier, but he pinged me at some insane hour
[15:14] <xnox> ..
[15:14] <xnox> boost1.61 update prepared for gcc+icu transition
[15:14] <xnox> openssl enable asm and apply fixes lp #1601836 also requested the same to be done in debian (maintainers are agreeable to the idea)
[15:14] <xnox> generate cloud images appx for Ubuntu on Windows
[15:14] <xnox> 14.04 point release testing (nvme)
[15:14] <xnox> sru validation
[15:14] <xnox> upcoming helping with boost/gcc/icu transition
[15:14] <xnox> ..
[15:15] <xnox> .... clearly enabling asm optimisations never causes regressions =) *caugh* but testing so far is solid and everyone else has it enabled
[15:16] <slangasek> xnox: was the '..' a 'done'?
[15:16] <cyphermox> isn't it an escape in some weird terminal thing?
[15:16] <slangasek> xnox, doko: I noticed the thread discussing ABI incompatibilities between gcc5 and gcc6... I think we're going to need to dig into this wrt phone stack ABIs
[15:17] <slangasek> (not here and now, but imminently)
[15:17] <slangasek> cyphermox: 8270?
[15:17] <slangasek>  * last week: CDO midcycle sprint
[15:17] <slangasek>   * lightning talk demo of snappy first boot experience, it was pretty snappy!
[15:17] <slangasek>   * discussions around snappy support on 14.04
[15:17] <slangasek>  * Monday: travel swap
[15:17] <slangasek>  * Tuesday: email catch-up
[15:17] <slangasek>  * Wednesday: sick day
[15:17] <slangasek>  * next:
[15:17] <slangasek>   * continued mid-cycle braindump
[15:17] <cyphermox> slangasek: sorry, I 404.
[15:17] <slangasek>   * continued email catch-up
[15:17] <slangasek>   * ubuntu-image
[15:17] <slangasek> (done)
[15:17] <xnox> slangasek, we know boost-regexp is bust, and autopkgtest shows that possibly some kdelibs are bust too. Apperantly they have fixed the bugs in abi-tagging in nested templates or something.
[15:18] <doko> - GCC 6 now the default
[15:18] <doko> - gcc 4.9.4 release, package update, gcc 5.4.1 package update
[15:18] <doko> - boost 1.61 transition
[15:18] <doko> - fixing build failures related to GCC 6 and boost 1.61
[15:18] <doko> - pinging people about fixing build failures ...
[15:18] <doko> - openjdk-8 update
[15:18] <doko> (done)
[15:18] <slangasek> xnox: sure; but where "fixed bug" == "break compatibility", we need to have a plan :)
[15:18] <doko> slangasek, but it will be ugly in any case
[15:18] <slangasek> it sounds like the gcc6 + boost 1.61 build failures should now be fixed en masse? yes?
[15:19] <doko> yes, there are "some".
[15:19] <doko> but let's first finish the transition rebuilds, see http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.61.html
[15:19]  * slangasek nods
[15:20] <slangasek> doko: so I suppose once boost has cleared we want to revisit what's still broken that the phone team needs to look at?
[15:20] <slangasek> meanwhile
[15:20] <slangasek> no caribou
[15:20] <slangasek> tdaitx:
[15:20] <tdaitx> = OpenJDK security update
[15:20] <tdaitx> - Packaged IcedTea 2.6.7 into openjdk-7-7u111-2.6.7 for Trusty and Precise; tested and provided packages to the security team
[15:20] <tdaitx> * Had to retry ARM64 build on Trusty 6 times until gcc/g++ didn't segfault (happens on every update as the PPA must use only the -security pocket, version on -updates works fine); tips on how to fix that?
[15:20] <tdaitx> - Working on 2 regressions from the security updates:
[15:20] <tdaitx> * JAMVM regression on OpenJDK 7u111
[15:20] <tdaitx> * OpenJDK 8u101 Zero VM on armhf (LP: #1609190)
[15:20] <tdaitx> = AOB
[15:20] <tdaitx> - Trying to figure out why Network Manager can't restart openvpn when ping-restart is set (seems to be missing the up script or dependencies in the chroot, still debugging that, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667611#20); cyphermox, help? =)
[15:20] <doko> slangasek, yes, they have a list, and are apparently starting to fix things
[15:20] <tdaitx> - Provider will install landline/adsl tomorrow morning (Friday)
[15:20] <tdaitx> (done)
[15:21] <slangasek> doko: ok good :)
[15:21] <cyphermox> oh, hai
[15:22] <sil2100> oh
[15:22] <sil2100> Me
[15:22] <sil2100> - Landing team work, silo coordination, preparing landing e-mails
[15:22] <sil2100> - RTM status meetings
[15:22] <sil2100> - Touch xenial:
[15:22] <sil2100>   * Coordinating rebuilds of all core clicks for arm64
[15:22] <sil2100>   * Modifying the livecd-rootfs build hooks to fetch arm64 from a different location
[15:22] <slangasek> tdaitx: tips on how to fix the -security gcc being broken> get the security team to pull that gcc into the security pocket for you? :)
[15:22] <sil2100>   * Switching system-image to import the new arm64 rootfs - first frieza arm64 image!
[15:22] <sil2100>   * Discussing fat-click-package future (consensus: wait for snaps?)
[15:22] <sil2100> - DMB meeting
[15:22] <sil2100> - Trying to refresh packagesets with the packageset script, output strange
[15:22] <sil2100> - Added mate-hub to the ubuntu-mate packageset
[15:22] <sil2100> - Releasing the modified goget-ubuntu-touch for new device support
[15:22] <sil2100> - Looking into backporting libboost1.58 to the overlay as per phone needs
[15:22] <sil2100> - Staging updated touch seeds to include new packages (indicator-keyboard, account-plugin-owncloud)
[15:22] <sil2100> - Started backporting golang-1.6 to the overlay as it seems to fix various issues
[15:22] <sil2100> - Finished work on switching generate-commitlog to the new bileto published_versions
[15:22] <sil2100> - Validating SRUs for xorg-server and mesa
[15:22] <sil2100> (got distracted, done)
[15:22] <tdaitx> slangasek, heh, I will poke them then
[15:22] <tdaitx> thanks
[15:23] <slangasek> tdaitx: they may say 'no', of course, but it's the right conversation to have :)
[15:23] <slangasek> sil2100: an arm64 image? woot!
[15:24] <sil2100> \o/
[15:24] <slangasek> sounds like you all had a very productive week without me
[15:24] <sil2100> Yeah, it doesn't boot quite yet, but it's because we didn't have a working device tarball
[15:24] <slangasek> should I go away more often? ;)
[15:24] <slangasek> any questions re: status?
[15:24] <sil2100> ondra assumed the armhf one should work ;p
[15:24] <sil2100> Not from me
[15:25] <slangasek> sil2100: backporting golang-1.6 to the overlay> that seems like it shouldn't be necessary to "backport" given that we have golang-1.6 as an SRU all the way back to trusty.  Do we just need to forward-copy to vivid/wily?
[15:26] <sil2100> Oh, might be a good idea then, yeah
[15:26] <sil2100> Didn't know we had that in trusty
[15:26]  * sil2100 could have checked
[15:26] <sil2100> I mean, I rarely look 'backwards' for stuff ;)
[15:26] <sil2100> That would make things rather easy
[15:27] <slangasek> if we want to do it "properly" then we may have to re-bootstrap in each release; mwhudson would be the one to talk to about that
[15:28] <slangasek> otherwise, I would be ok in this case with just binary-copying forward from trusty to vivid+wily, provided that infinity won't stab me for this
[15:28] <sil2100> He's not here so I guess we can just do it, he won't notice ;p
[15:29] <slangasek> heh
[15:29] <slangasek> sil2100: anyway, fast path to avoid blocking on SRU process would be for you to just do binary copy from trusty to the overlay ppa; it's a completely new package so I *think* it should be safe to copy in without going through a silo
[15:30] <slangasek> but, of course, you should double-check that it's not going to clobber any other binary packages
[15:30] <sil2100> I wanted to do that through a silo so that I can do rebuilds of all the packages we need and see if those work ok on vivid
[15:30] <slangasek> ok
[15:30] <slangasek> then you can binary-copy to a silo instead of to the overlay :-)
[15:30] <sil2100> SInce we know that golang-1.6 fixed some issues for xenial, and possibly it will fix those on vivid too
[15:30] <sil2100> Will do, thanks :)
[15:31] <slangasek> are you intending to change the golang defaults, or just provide golang-1.6 as an alternative?
[15:31] <slangasek> the latter matches what's been done in trusty, and is probably easier to QA in pieces because only things you know are broken and need rebuilt have to opt-in
[15:31] <sil2100> Not sure yet, both ways would work fine as we want to use the new golang for all our touch go packages anyway
[15:32] <sil2100> But yeah, maybe it would be less troublesome to not do a change of defaults
[15:32]  * slangasek nods
[15:32] <sil2100> THen we can have more control if anything is broken
[15:32] <sil2100> +1 on that idea then ;)
[15:32] <slangasek> cool
[15:32] <slangasek> [TOPIC] AOB
[15:33] <slangasek> anything else?
[15:34] <slangasek> #endmeeting
[15:34] <meetingology> Meeting ended Thu Aug  4 15:34:56 2016 UTC.
[15:34] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-08-04-15.02.moin.txt
[15:34] <slangasek> thanks, all!
[15:35] <barry> thanks!
[15:35] <sil2100> Thanks!
[20:06] <mwhudson> slangasek, sil2100: bootstrapping golang-1.6 in vivid and wily should be easy enough, gccgo is new enough there
[20:06] <mwhudson> slangasek, sil2100: copy-package -b is even easier though ...
[20:43] <sil2100> mwhudson: I did a copy-package to a silo already from trusty
[20:44] <sil2100> mwhudson: it's now about building go packages
[20:44] <sil2100> Like, those using golang
[20:44] <mwhudson> ah ok


[12:47] <mitya57> Noskcaj, not yet, it breaks LXDE if I recall correctly
[22:01] <ubunted> Installing ubuntu-14.04.1-desktop-amd64 fails with "'grub-install /dev/sda' failed" , no specific error given
[22:56] <ubunted> Installing ubuntu-14.04.1-desktop-amd64 fails with "'grub-install /dev/sda' failed" , no specific error given
[23:52] <xperia> hi all. i am having problems with compileing tkgate from sources. when i do this here => sudo apt-get build-dep tkgate & apt-get source tkgate & cd tkgate-2.0~b10 & ./configure & make i get build error messages like "block.c:1103:20: error: ‘Tcl_Interp’ has no member named ‘result’"


[14:21] <adom> re: Ubuntu Jam: if its far enough ahead to schedule around my schedule, and its within decent distance, i could be convinced to attend.
[14:21] <adom> that is, of course, if others are planning on going as well
[14:26] <bcurtiswx> I know that Kevin, Myself, and Dan at least will probably attend. It seems the MLK Library is right off the metro (1 block IIRC), so usually easy WMATA access brings more participants
[23:45] <adom> ive never been to one, is there usefulness for someone like me, that loves Ubuntu but hates Unity? currently using gnome+cairo-dock with ubuntu 13.04.
[23:45] <adom> like, if i come, will the devoted just thrash me?


[03:29] <hallyn> pitti: mind you i think it's a shame :)
[06:52] <pitti> Good morning
[06:52] <didrocks> good morning pitti
[06:52] <pitti> bonjour didrocks !
[08:22] <brainwash> pitti: hi. does pkexec work for you? running "pkexec whoami" gives me:
[08:23] <brainwash>  polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
[08:30] <brainwash> bug 1288786
[08:30] <brainwash> same error message in comment #7
[08:57] <mwhudson> doko: ping, did you see https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1586872
[09:20] <mapreri> cjwatson: really not totally sure how this could be possible, but indeed using -O2 instead of -O3 (at least, that's the only relevant change I see) made cowdancer build on pcc64el.
[09:20] <mapreri> https://volatile.mapreri.org/2016-06-02/d177d0ca47a32d7e2a8a05675de28948/0.80_0.80u1.html — if you are fancy looking the diff of the 2 logs and figure it out :|
[09:29] <mapreri> Thank you very much for the precious hint!
[09:38] <cjwatson> np
[10:18] <Odd_Bloke> What package creates/manages /etc/nsswitch.conf?  (And how can I work this out for myself in future?)
[10:22] <brainwash> Odd_Bloke: try  dpkg -S /etc/nsswitch.conf
[10:22] <rbasak> Odd_Bloke: failing that (which it will as it isn't a conffile), "grep nsswitch.conf /var/lib/dpkg/info/*" is a quick hack to find maintainer scripts on your system that reference it.
[10:22] <rbasak> Odd_Bloke: looks like the answer is base-files.
[10:23] <Odd_Bloke> brainwash: rbasak: Thanks! :)
[10:24] <Unit193> rbasak: Don't forget apt-file 'nsswitch.conf'
[10:40] <ubuntu577> Hello all,  need help  .. how to rebuild the ppa to another architecture.
[10:42] <ubuntu577> sorry .. I mean  how to build  Archives  to another architecture  through ppa
[10:42] <cjwatson> ubuntu577: PPAs automatically build packages for all architectures they're configured to build for, but you can enable some additional architectures that aren't enabled by default using the "Change details" page on the PPA
[11:18] <xnox> ogra_, do you have time at all to look into initrafs-ubuntu-touch thing? it has not been rebuild for a while. I've tried dropping adbd (apperantely doesn't work and not available on arm64) and enable arm64 build and no dice.
[11:18] <xnox> it build locally, but fails in a launchpad ppa.
[11:19] <xnox> ogra_, https://launchpad.net/~xnox/+archive/ubuntu/nonvirt/+build/9844912
[11:25] <ogra_> xnox, hmm
[11:25] <ogra_> + fakechroot chroot ./build apt update
[11:25] <ogra_> /usr/sbin/chroot: failed to run command ‘apt’: No such file or directory
[11:26] <ogra_> why would it not run apt-get
[11:26] <zander> I'm trying to upload a packaged version of my software to launchpad. It gives me "rejected" with no useful error message. Is there anyone that can help out?
[11:27] <xnox> ogra_, it did run apt-get before, and resulted in similar error messages "apt-get not found" changed to apt, no dice.
[11:27] <xnox> ogra_, somehow debootstrap log shows loads of errors too.
[11:27] <xnox> locally it builds fine.
[11:27] <cjwatson> zander: Can you provide your dput command line?
[11:27] <ogra_> weird
[11:28] <zander> cjwatson: dput ppa:bitcoinclassic/bitcoinclassic  bitcoinclassic_0.12.1-trusty1_sources.changes
[11:29] <cjwatson> zander: Are you sure you didn't get a useful error message?  Our logs show that we sent you one indicating that dpkg-source failed to extract the source package
[11:30] <cjwatson> starting with "dpkg-source failed for bitcoinclassic_0.12.1-trusty1.dsc [return: 2]"
[11:30] <cjwatson> it's slightly cryptic I'll grant ...
[11:31] <zander> The full text is http://paste.ubuntu.com/16918003/
[11:31] <zander> I can't find the actual error.
[11:31] <zander> Nothing I can use to fix it, anyway.
[11:32] <cjwatson> zander: So one thing that this can sometimes be is that our production systems (unfortunately) still run on precise, and it's occasionally possible to construct a source package that precise's dpkg-source obscurely fails to unpack like this.
[11:32] <cjwatson> zander: Can you put the source package somewhere I can see?  I recognise most of the usual causes of this by now
[11:32] <zander> sure
[11:34] <ogra_> xnox, i think the deboostrap.log looks fine though (the pre-dep moaning is notmal IIRC)
[11:34] <ogra_> *normal
[11:36] <zander> cjwatson: http://thomaszander.se/foo/
[11:38] <cjwatson> zander: Right, the problem is that debian/patches/series lists a patch that doesn't exist.  In fact dpkg-source in xenial fails to unpack the package in a similar way.
[11:39] <zander> isn't series supposed to list the release? Trusty in this case?
[11:40] <cjwatson> No.
[11:40] <cjwatson> Not even a little bit :)
[11:40] <cjwatson> It's a quilt patch series.
[11:40] <zander> ok, I guess I misread a tutorial somewhere :)
[11:41] <zander> My intention was to host several 'versions'. For the different ubunutu releases.
[11:41] <cjwatson> You could probably just delete debian/patches/ entirely, as it is.  But if you need patches in future, then each line in debian/patches/series should be a file in debian/patches/ which is a patch file applied to the upstream source code.  You'd normally manage those with quilt or with some more sophisticated tooling around it.
[11:44] <zander> Since I develop on debian, I would just change the actual sourcetree. I'll delete the dir.
[11:49] <zander> cjwatson: its building now \o/
[11:49] <zander> So, how can I get it build for more than one version of ubuntu?
[11:52] <cjwatson> zander: Often it's entirely unnecessary to have multiple builds, and you can just upload to the oldest series you want to support and then copy it forward to all the other ones using "Copy packages" in your PPA and telling it to copy existing binaries.
[11:52] <zander> ah
[11:53] <cjwatson> zander: But if you really need to build separately for different Ubuntu series, then you can just build source packages with different versions (usually just changing the bit after the last "-") and a different target in the top entry in debian/changelog.
[11:54] <zander> That makes sense. thanks
[12:27] <zander> Another question. Is there a simple way to append the filelist to the .dsc file?    What are you finding that you need to add to it?
[13:30] <zander> cjwatson: 'add to it'... I need to *create* it.  Since I have not found any tool to do so for me.
[13:30] <cjwatson> zander: debuild -S
[13:31] <cjwatson> zander: really really do not write the .dsc by hand :-)
[13:32] <cjwatson> debuild is a wrapper around dpkg-buildpackage, and you can use that too, but debuild is a little more convenient
[13:33] <zander> I tried to run that a couple of times. Never got any useful output from it.  For instance; http://paste.ubuntu.com/16919442/
[13:33] <cjwatson> zander: Was that before or after you removed the nonsense debian/patches ?
[13:34] <zander> thats just now. I removed the patches dir.
[13:34] <cjwatson> zander: can you post 'find -ls' from there so that we can orient ourselves?
[13:35] <cjwatson> debuild -S is what basically everyone else uses so you have some weird corner case here
[13:36] <cjwatson> zander: It sounds like perhaps you have "debian" as a symlink, which isn't allowed
[13:37] <zander> http://paste.ubuntu.com/16919488/
[13:37] <zander> Hmm, I'll move the debian dir...
[13:38] <cjwatson> Right, the debian directory must always be at the top level of the package's ordinary source tree, and not a symlink
[13:39] <zander> but its Ok to not have it inside the .orig.tgz ?
[13:39] <cjwatson> Indeed, it's normal not to have it in the orig.
[13:39] <zander> Well, i guess I got bitten by lots of little rules :)
[13:40] <zander> But it seems to work now. Which makes me quite happy.
[13:40] <cjwatson> Excellent
[13:42] <mgedmin> would be nice to improve the error message about 'debian' not being a directory
[13:43] <mgedmin> e.g. "add_directory() only handles directories at /usr/share/perl5/Dpkg/Source/Package/V2.pm line 556." doesn't even mention what the not-directory was
[13:51] <pitti> xnox, infinity, tinoco: aupkg02 (<IP_ADDRESS>) is still down (since yesterday), could one of you please torture it with the right stick?
[13:59] <xnox> pitti, it has a stalled task on the CPUs
[14:00] <xnox> with kthreads starved for 17227361 jiffies
[14:00] <xnox> force poweroff, rebooting
[14:00] <xnox> pitti, booted
[14:01] <tuxinator> hi all, since some time (only have time to investigate now, my mirror does not sync from cdimage.ubuntu.com::cdimage/
[14:01] <pitti> xnox: cheers!
[14:01] <tuxinator> the error message is only  change_dir "/daily/current" (in cdimage) failed: No such file or directory (2)
[14:01] <tuxinator> at my site the directorys exist
[15:31] <arges> bdmurray: can you sru-review kpatch/xenial today? Thanks
[15:34] <bdmurray> arges: sure
[16:19] <nacc> rbasak: so i had to remove one of our optimizations from the algorithm -- the one that looks for launchpad versions 'greater than' the tip's version when doing an import to an existing repository. Because of the case of versions going backwards potentially ... so i'm now using the publishing date and asking for published history after a committed date (this also minimizes our lp traffic). Does that
[16:20] <nacc> seem sane? I'm thinking I may fudge it a little bit to make sure we don't 'miss' any publishes (still considering corner cases)
[16:21] <rbasak> nacc: I think going by publishing date is fine. That's what I thought we were doing already!
[16:23] <nacc> rbasak: launchpad_revs_greater_than(debian, last_debian_version) (and similar for ubuntu)
[16:23] <nacc> rbasak: so we were (in my old undrstanding) using the versions, not the dates
[16:24] <rbasak> nacc: fair enough. We've changed plans so many times I lost track, sorry. I think publishing dates is fine as long as it doesn't interfere with import ordering in some unexpected way.
[16:24] <rbasak> (I don't see why it would).
[16:24] <rbasak> And in fact, going by publishing date is probably more accurate for the pocket parent in this new world order.
[16:25] <nacc> rbasak: ack, that's what i'm thinking too -- i just need to make sure we're capturing and passing the date properly as far as the JSON goes (so we don't miss stuff published, e.g., the same day let's say)
[16:36] <nacc> rbasak: a new interesting case, python-pip (https://launchpad.net/ubuntu/+source/python-pip/+publishinghistory?batch=75) -- 8.1.2-1 was in debian/sid (first seen there) then yakkety-proposed then yakkety-release. Our history indicates the version from debian/sid was copied to yakkety-proposed and yakkety, as opposed from debian/sid to yakkety-proposed and then from yakkety-proposed to yakkety-release.
[16:36] <nacc> This turns out to be true based upon the publishing logs (both indicate copies from debian/sid). But is that always the case?
[16:43] <nacc> ogasawara_: is there a reason there aren't xenial directories in http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Apologies in advance if you're not the right person to ask :)
[16:46] <rbasak> nacc: I'm not sure why that happened. Something to do with archive opening perhaps? It'll create some slightly different history in our import but is otherwise OK, right?
[16:47] <nacc> rbasak: yeah, i'm not 100% either -- to clarify, the algorithm as written now, for a version that has already been imported previously, will mark as the 'changelog parent' the commit corresponding to the first import of that version. I'm just trying to think if that is correct or not :)
[16:48] <rbasak> nacc: if it does affect us then I'd have to ask someone like Colin to explain.
[16:49] <rbasak> nacc: would a parent minimisation function help us here? If the commit has two parents A and B, and A is an ancestor of B, then eliminate A.
[16:50] <rbasak> I'm not sure if that makes sense or not for us. Not thought it through.
[16:55] <nacc> rbasak: we probably should add something liek that, but i don't think it applies to this particular case. The two parents are distinct (the pocket parent is the old yakkety release version, correctly)
[16:57] <nacc> rbasak: from a code content perspective our algorithm is correct; i'm just not sure we have enough information from any source to know where something gets copied from, let me see if launchpadlib says
[17:00] <ogasawara_> nacc: I see we have xenial for 4.4.9, .10, .11, and .12...is there a specific version you were hoping to find?  I don't believe we have anything earlier than that because xenial hadn't been officially released until end of april, so build after that would use xenial's config.
[17:04] <nacc> ogasawara_: i might just be misunderstanding hte layout of the directories, but there is a 4.6-rc6-wily, but not a 4.6-rc6-xenial ?
[17:04] <nacc> ogasawara_: in fact those 4 you found are the only xenial, but there are many more for wily and (now) yakkety
[17:05] <nacc> ogasawara_: someone in #ubuntu was asking how to test mainline on xenial for a bug report, and i wasn't sure if we'd normally advise them to just use latest-yakkety (and if that would work properly, i'd worry about deps)
[17:05] <rbasak> nacc: do we need to know where the code was copied from? Since the trees are identical and a previous uploader (or archive admin) could have copied from a different pocket (but the same version), then from a source package perspective, is it fundementally part of the data we're trying to capture at all?
[17:07] <nacc> rbasak: no, we probably don't. But I want to make sure we don't accidentally lose some publishing information. So let's say that in this case, the yakkety version had gone debian -> y-proposed -> y-release. There would be no link in our git tree from the y-release commit to y-proposed, because the first import was in debian and that's where we'd point the 'publish parent' commit to.
[17:11] <rbasak> nacc: I understand how that loses some information about publication ordering, but my initial feeling is that it's OK. We're interested in the history of the code, and the code hasn't changed. One might consider all of the commits sharing a version to be bundled together, and as a whole the graph edges to and from the bundle would be correct.
[17:11] <nacc> rbasak: yep, absolutely
[17:11] <nacc> and in theory, the one in any other pocket *did* come from the first one, by definition, aiui
[17:12] <nacc> so we're bsaically doing a bit of optimized parent following :)
[17:12] <rbasak> Yeah. Sort of like git and renames again :)
[17:13] <ogasawara_> nacc: I'm reaching out to apw for clarification as I actually was only expecting to see 4.6-rc# builds against yakkety
[17:17] <nacc> ogasawara_: ack, thanks! yeah, i think that's what is confusing the user (and me) :)
[17:18] <cjwatson> nacc: the copy-from information in fact tells you where it was originally uploaded to, not the previous hop in the chain; so what you're seeing is expected.
[17:21] <nacc> cjwatson: ah ok, thanks for clarifying -- that makes me happy that our algorithm will match that :)
[17:21] <nacc> cjwatson: even if accidentally...
[17:35] <RobertDupont> hello guys
[17:36] <RobertDupont> I found a bug in an iptables module and I was wondering if I have to report it to iptables or kernel
[17:36] <RobertDupont> rule is inserting just fine
[17:36] <RobertDupont> it is just not matching when it should be on 16.04 (works fine on 14.04)
[17:52] <RobertDupont> does anybody know
[17:52] <RobertDupont> or you're just not interested in bug reports?
[17:53] <cjwatson> People aren't very likely to respond to bug reports on IRC, especially if they're a bit ambiguous or difficult to diagnose immediately.  Just report it to wherever you think most sensible, that's better than nothing
[17:54] <RobertDupont> I'm just asking which package I should file it to
[17:54] <cjwatson> (I don't know the answer to exactly where it belongs, though I'd suspect the kernel.  But I reject your false dichotomy that either somebody here knows or nobody is interested in bug reports)
[17:55] <RobertDupont> well, I've filed a couple of reproductible bug reports and nobody has fixed them
[17:55] <RobertDupont> some bugs have been present since 2008 and haven't been fixed
[17:56] <cjwatson> Sure, but also lots of bugs are fixed all the time.  Human effort is sadly finite
[17:56] <cjwatson> Speaking of which, end of day and dinnertime
[17:57] <RobertDupont> apparmor, snort and a few other big ones
[18:08] <Logan> nacc: hey, have you been working on the phpunit-mock-object merge? phpunit is still uninstallable because it depends on phpunit-mock-object >= 3.1, and we have 3.0.6-1+ubuntu1
[18:11] <nacc> Logan: let me do that right now
[18:12] <Logan> thanks!
[18:15] <nacc> barry: https://code.launchpad.net/~usd-import-team/ubuntu/+source/python-pip/+git/python-pip
[18:23] <barry> nacc: cool!
[18:24] <nacc> barry: i took a quick look, it seems correct, and didn't provide any warnings, errors, etc., but do please take a look when you can and let me know if anything looks odd
[18:31] <barry> nacc: will do
[18:31] <nacc> barry: thanks! also just uploaded the helper script for merges at https://code.launchpad.net/~usd-import-team/usd-importer/+git/usd-importer
[18:32] <nacc> and that's the current importer's code too (same repository)
[18:32]  * barry nods
[18:34] <rbasak> nacc: looking at usd-import-reconstruct-merge, it looks good, just a couple of comments.
[18:35] <rbasak> Only from a quick read of the code, so maybe I've got it wrong.
[18:35] <nacc> rbasak: ack, it might need some love, i just cobbled it together last night
[18:35] <rbasak> 1) dsc_commit_tag looks like it might match too much, for example ubuntu1.1 when ubuntu1 is being looked for.
[18:36] <nacc> rbasak: ah you're right, i'll anchor it
[18:36] <rbasak> 2) Never mind, I missed something. Looks good :)
[18:36] <nacc> rbasak: or i could just use -F right?
[18:36] <nacc> oh but that would still need anchoring
[18:37] <nacc> i guess `grep -F -w` ?
[18:37] <nacc> or -x, not sure, i'll read :)
[18:38] <rbasak> I'd use a regexp. Because you're looking for /^(import|upload)\/<version>$/, right?
[18:40] <rbasak> nacc: BTW, we should probably pull together my ubuntu-git-tools repo with the usd-importer repo at some point. No point having them separate.
[18:40] <nacc> rbasak: ack, you're right, becauseall i have is the version, sorry
[18:41] <nacc> rbasak: yep, they are starting to be more related
[18:50] <hallyn> smb: hrmph.  you're telling me my libvirt upgrade/transition stuff was wrong?
[18:52] <smb> hallyn, no, in the end the problem is that we upgraded before it was done completely, so was not executed. I just finishing up some upload that is more persistent
[18:52] <bdmurray> happyaron: How is bug 1297849 related to the network-manager-openconnect upload in xenial-proposed?
[18:55] <smb> hallyn, That systemd suddenly got more picky about a still lingering /etc/systemd/system/libvirtd.service alias to libvirt-bin might be another problem. I decided that I just check and if found remove various files which may still be present when doing 1.3.4 to 1.3.4 upgrades (or fresh install but then its unlikely to find anything)
[18:59] <hallyn> smb: my ego thanks you :)
[18:59] <smb> hallyn, :D
[18:59] <hallyn> makes sense too
[19:00] <hallyn> \o
[19:01] <nacc> rbasak: smoser: pushed updates, thanks to you both!
[19:02] <nacc> caribou: corosync imported, and the helper script dtrt, i think, as far as building you a reconstruct/<version> commit
[19:02] <nacc> rbasak: so the bash script *could* tag the commit too, would that be useful? as I can get the version out of dpkg-parsechangelog given the commit, apply the renaming rules to it, etc.
[19:10] <rbasak> nacc: yeah, that'd probably be useful. Maybe tag it reconstruct/<version> unless that tag already exists, in which case warn?
[19:32] <nacc> rbasak: yep, will work on that now
[19:33] <nacc> rbasak: i probably could dig and find it, but i didn't see a good way of doing cherry-pick without checking out first
[19:35] <rbasak> nacc: you need a working tree I think. The only way to not clobber the user's tree would be to do it like git-dsc-commit and use a temporary directory for the tree I think.
[19:35] <nacc> rbasak: yeah, i was hoping to avoid that route
[19:36] <nacc> rbasak: i think it's "ok" as-is? if someone hates it, we can modify it
[19:39] <nacc> rbasak: and git-tag already does that detection and will emit an appropriate warning, i think
[19:40] <rbasak> nacc: yeah I think it's fine as-is and we can change it later if it's an issue. Generally the user will want to check it out anyway I think, or at least have a clean tree before doing so.
[19:41] <nacc> rbasak: yep
[19:41] <nacc> rbasak: that's a good point, i should probably handle the error case on checkout
[19:42] <rbasak> nacc: perhaps just insist on a clean tree first. I think git-dsc-commit does that.
[19:42] <nacc> rbasak: yep
[19:45] <nacc> rbasak: pushed
[19:45] <nacc> caribou: --^ so the helper script for corosync should generate the reconstruct tag for you now
[19:54] <nacc> rbasak: I really appreciate all the feedback so far! Thanks!
[20:03] <elbrus> rbasak: would you recommend me to try for MOTU (or even ubuntu developer as I'd like to help with my own package dbconfig-common which is in main)
[20:03] <elbrus> and would you endorse my application
[20:03] <elbrus> ?
[20:07] <pitti> infinity: I'm confused about https://launchpadlibrarian.net/262897168/buildlog_ubuntu-yakkety-amd64.autopkgtest_3.20.8_BUILDING.txt.gz -- don't buildd chroots have "deb-src" apt sources?
[20:08] <pitti> (builds fine in my sid and yakkety schroots)
[20:14] <pitti> I can reproduce it if I drop deb-src, but that seems strange for a buildd chroot
[20:19]  * pitti will add a @skipUnless() if there are no deb-src, not much that I can do then
[20:22] <cjwatson> pitti: The default setup for buildd chroots doesn't much matter, since Launchpad blats out its own preferred sources.list anyway
[20:23] <cjwatson> (doesn't matter for builds, that is)
[20:25] <cjwatson> pitti: So in this case it's the one that Launchpad blats out that matters, not what's in the chroot; and Launchpad doesn't write out deb-src lines, because buildds fetch the source straight from the librarian
[20:25] <cjwatson> (except in the private PPA case which currently does a somewhat weird thing, but even that doesn't rely on deb-src)


[23:49] <charles_> Transmission 1.06 is out:
[23:49] <charles_> http://download.m0k.org/transmission/files/transmission-1.06.tar.bz2


[00:06] <Omega> BUGabundo: version numbers don't really mean anything
[00:06] <BUGabundo> I know
[00:54] <xjjk> mm is the latest firefox-next build crashing a lot or is it just me
[00:54] <xjjk> i.e. 3 crashes in the last 20 min
[00:55] <micahg> xjjk: wfm on natty
[00:55] <xjjk> I'm still on maverick
[00:55] <xjjk> eh, time to disable all my extensions…
[00:56] <micahg> xjjk: can you report the crash to mozilla?
[00:56] <xjjk> yes, reported the last 3 with the built-in crash reporter
[00:57] <xjjk> fortunately I've -dbg and -mozsymbols installed
[00:57] <micahg> xjjk: you actually don't need either to report crashes to mozilla
[00:57] <xjjk> right
[00:57] <xjjk> sorry, was just asking if it was known
[00:57] <xjjk> if it isn't, should start investigating it now…
[01:00] <micahg> chrisccoulson: any problem with pasting crashids here? ^^
[01:01] <xjjk> ehh the crash reporter doesn't really tell you anything interesting…
[01:01] <chrisccoulson> it doesn't because i've not submitted the symbols from firefox-next
[01:01] <chrisccoulson> please run it in gdb
[01:03] <micahg> chrisccoulson: when beta 3 comes, can you submit those?
[01:04] <xjjk> just to confirm: there isn't a PPA/etc following the Firefox Aurora channel, right?
[01:07] <xjjk> mm crashing in wordcopy.c
[01:07] <xjjk> something to do with cache
[01:07] <xjjk> time to clear my cache, I suppose
[01:21] <xjjk> and problems appear to be gone after clearing cache…
[11:36] <chrisccoulson> bhearsum, you haven't started aurora builds yet have you?
[11:36] <chrisccoulson> **restarted
[12:49] <fta> woww, linking with ld-gold is fast
[12:49] <fta> now the next bottleneck is lzma
[14:08] <bhearsum> chrisccoulson: we haven't started publishing nightlies yet, nope
[14:08] <bhearsum> we're still deciding what to back out / pref off
[14:08] <chrisccoulson> bhearsum, ok, thanks
[14:34] <m_conley> chrisccoulson: hey - do you know if there's a channel for EDS development?
[14:34] <m_conley> chrisccoulson: IRC channel
[14:34] <m_conley> ?
[14:35] <m_conley> chrisccoulson: nm - think I found it. :)
[14:52] <m_conley> chrisccoulson: ping
[14:53] <chrisccoulson> hi m_conley
[14:53] <m_conley> chrisccoulson: hey - so this just popped up on my radar:  https://bugzilla.mozilla.org/show_bug.cgi?id=659918
[14:53] <ubot2> Mozilla bug 659918 in OS Integration "Thunderbird's internal pref for setting default mail program is still using the old url-handler stuff in gconf." [Normal,New: ]
[14:53] <chrisccoulson> fixed already :)
[14:54] <m_conley> chrisccoulson: am I correct in assuming that this is related to that GIO service patch you landed not too long ago?
[14:54] <chrisccoulson> yeah, that's https://bugzilla.mozilla.org/show_bug.cgi?id=624341
[14:54] <ubot2> Mozilla bug 624341 in OS Integration "Update check for default mailer to work the new way (glib >= 2.27.1)" [Normal,Resolved: fixed]
[14:54] <m_conley> ah, lovely
[14:54] <m_conley> :)
[14:54] <m_conley> chrisccoulson: thanks!
[14:55] <micahg> chrisccoulson: we still have fallback on older glib implementations, right?
[14:56] <chrisccoulson> micahg, yes
[14:56] <micahg> chrisccoulson: k
[22:06] <fta> chrisccoulson, do you maintain the translations of your desktop files in lp now?
[22:55] <BUGabundo> evening
[23:06] <fta> gasp, the new adblock is broken
[23:06] <BUGabundo> hehe
[23:08] <fta> weird to see ads
[23:09] <BUGabundo> ahaahahahaahahahahah
[23:09] <BUGabundo> fta: Order has been handed over to the carrier and is in transit
[23:10] <BUGabundo> https://www.amazon.co.uk/Asus-EeePad-Transformer-Tablet-Android/dp/B004TB0EMK/ref=pd_rhf_p_t_1
[23:10] <fta> what for?
[23:10] <fta> i'm quite happy with my galaxy tab
[23:11] <BUGabundo> this is better :D
[23:11] <BUGabundo> yours the 7"?
[23:13] <fta> yes
[23:14] <fta> i bring it with me almost everywhere, something you can't do with a 10"
[23:15] <BUGabundo> right
[23:15] <BUGabundo> I plan to use it at home
[23:15] <BUGabundo> already have a 4.3" Desire HD
[23:16] <fta> yep, i think i'll get a 10" or more next time, to keep at home, but i'll still use my 7"
[23:17] <fta> i'm waiting for the new coupled smartphone+tablet contract from my isp, see if it's worth it
[23:19] <fta> hm, it seems the last chromium daily is broken..
[23:19] <fta> my canvas are gone in http://people.ubuntu.com/~fta/chromium/stats/stats.html
[23:20] <BUGabundo> 7" feels to big to carry
[23:20] <BUGabundo> maybe up to 5"
[23:21] <fta> depends on your usage
[23:21] <fta> i read books & magazines, it's just the size
[23:22] <BUGabundo> yeah
[23:22] <fta> the web is nicer in 7" too, less need to scroll


[04:43] <MeloMan> Sup
[04:44] <MeloMan> russians?
[04:47] <JoeyJoeJo> Is it possible to install ubuntu touch in a VM?
[06:46] <dholbach> good morning
[06:47] <SpacedOut> JoeyJoeJo: I haven't tried, but as Android sdk comes with qemu to run Android there, I don't see why it wouldn't work.  It might be the same as porting to a new hardware device but I don't know, I never tried.
[09:26] <dinomight> anyone know if the installer will wipe the media partition (where all of my personal stuff is located)?
[09:26] <dinomight> (galaxy nexus)
[09:29] <greyback> dinomight: yes, it wipes everything
[09:31] <dinomight> that sucks you'd suppose it wouldn't wipe the sdcard (or media mnt in the case of a phone without sd card)
[09:33] <dinomight> well now to figure out how to do transfer the media to my computer
[09:33] <dinomight> mtp sucks
[10:58] <diwic> rsalveti, seb128, do you think we should have a UDS session about audio on the Touch images? (A followup to previous vUDS audioflinger session)
[11:44] <SybyAbraham> HELLO
[12:15] <sergiusens> Mirv: ping
[12:19] <Mirv> sergiusens: pong
[12:22] <sergiusens> Mirv: hey, there's another problem with the new Qt
[12:22] <Mirv> sergiusens: ok, what's up, is there a bug filed?
[12:23] <sergiusens> Mirv: ppa:ubuntu-unity/daily-build-next seems to be not using ppa:c-e/qt5-proper so the qt-sensor fix (and any other qt dependant project) is not using it
[12:23] <Mirv> sergiusens: oh, it's building against raring archives, is that is? then it's also missing any previous updates
[12:23] <sergiusens> Mirv: the new qtubuntu-sensors is linked to 5.0.1
[12:24] <sergiusens> Mirv: yeah, can you take care of that with didrocks?
[12:24] <Mirv> mmrazik: it seems like that ^ would need PPA added as well, are you involved with that jenkins?
[12:24] <sergiusens> Mirv: I would of just added the build dep in the PPA
[12:24] <sergiusens> Mirv: jenkins has the right deps ;-)
[12:25] <sergiusens> Mirv: it's the ppa that would need access to those packages
[12:25] <mmrazik> Mirv: what sergiusens says... this needs to be added in lp
[12:25] <mmrazik> shall I add it? I most likely can
[12:25] <Mirv> sergiusens: ok so jenkins builds alright already, just the PPA?
[12:25] <mmrazik> mhm
[12:25] <mmrazik> not sure if adding the ppa is right
[12:25] <mmrazik> would prefer to check with didrocks first
[12:28] <sergiusens> Mirv: mmrazik yeah, adding the PPA or copying the packages in there... whichever... but I asked you since you (Mirv) since you are in the same team now and also working on Qt
[12:28] <Mirv> let's get more people on the board :)
[12:28] <mmrazik> sergiusens: the thing is that didrocks is using that PPA as a "archive-like" build IMO
[12:29] <Mirv> sil2100: what do you think, is there any sensible reason for daily-build-next not to have qt5-proper PPA as build-dep?
[12:29] <mmrazik> so when we start adding PPAs I would be concerned of some unintended asserts being broken
[12:29] <Mirv> mmrazik: for saucy there is nothing in those PPAs
[12:29] <sergiusens> mmrazik: well, there's a conflict there...
[12:29] <sergiusens> mmrazik: as Qt5 isn't being built there at all, so to the least it should be copied in
[12:29] <mmrazik> anyway. I'm not "owner" of that ppa and I'm unsure so I would rather not change anything
[12:30] <mmrazik> if there is somebody else brave enough...
[12:30] <sergiusens> mmrazik: yeah, that's why I asked Mirv :-)
[12:30] <mmrazik> sergiusens: I see ;)
[12:30] <Mirv> I've had my share of brave changes lately :)
[12:31] <sergiusens> Mirv: oh, didn't choose you because you were brave, but because it's Qt5 and the _release team_ PPA ;-)
[12:31] <Mirv> anyhow, in my mind qt5-proper PPA has so far acted as a "archive substitute" until we actually have latest Qt in a development Ubuntu, which we had for a little while with raring but of course it then got released and we have had further updates
[12:31] <sergiusens> you intersect perfectly :-P
[12:31] <sil2100> Mirv: not sure, I think there is no particular reason for that - I think before we didn't have that since we were pushing our own patched Qt5 versions, maybe that was the reason?
[12:31] <sil2100> Mirv: now I think we could add the dep, but maybe let's wait for Didier to say his word
[12:32] <sergiusens> anyways, anything I use to build the phablet images I consider 'archive' like
[12:32] <Mirv> sil2100: ah, right. there has been this delta that desktop team (before we joined) pushed their own Qt builds every now and then, while the qt5-proper PPA, even though recommended everywhere as official, was more like handled by SDK Team
[12:32] <Mirv> now there shouldn't be that delta anymore
[12:32] <sergiusens> sil2100: is didrocks on today?
[12:33] <Mirv> he's not here until tomorrow
[12:33] <sergiusens> sil2100: Mirv once the dep is added we might need to manually trigger a daily build for all the qt based projects
[12:34] <sergiusens> Mirv: that sucks
[12:34]  * ogra_ grumbles about mountall
[12:36] <ogra_> grmbl ...
[12:37] <ogra_> so i have the container flip working with a two line patch that bind mounts /data/ubuntu to /root in the initrd ... it boots fine until i mount the partition readonly :( since mountall freaks out then
[12:39] <Mirv> sergiusens: yes, that triggering should probably be done then, since some of the packages define a strict version dependency (>= 5.0.x)
[12:42] <Mirv> interesting that we now kind of get builds against both 5.0.2 and 5.0.1 - jenkins builds against the former and then the PPA rebuilds it against 5.0.1
[12:42] <jodh> ogra_: define "freak out". stgraber was using ro-root with mountall recently. If you are manually mounting stuff in the initramfs, I think you need to ensure that options in /etc/fstab / /lib/init/fstab match those you used in the initrd.
[12:43] <sergiusens> Mirv: well, we always kept qt5-proper as a dep
[12:44] <sergiusens> Mirv: since idk, november last year
[12:44] <ogra_> jodh, well, we try to use the caintainer rootfs in /data/ubuntu ... run-init didnt like that i pointed to a subdir there so the other alternative i saw was mounting /data to /mnt and then bindmounting /mnt/ubuntu to /root (which becomes / after run-init) ... mountall wants to fsck /root which it cant for a bind mounted readonly mount
[12:45] <ogra_> *container
[12:45] <Mirv> sergiusens: yes, regarding daily-build-next the trend to do that just has stopped at around Apr 20, when we did the final uploads to raring (identical to qt5-proper), so further updates to qt5-proper (also 5.0.1 ones) have not been picked up in the build-deps
[12:46] <Mirv> it only appeared more clearly now with the 5.0.2 in qt5-proper
[12:46] <ogra_> jodh, it works fine if i dont mount readonly, but then also mountall just skips the fsck
[12:46] <sergiusens> Mirv: yeah... which leaves us in a catch 22, since you mentioned devs wanted this new version, but we can't use it until it's in that PPA
[12:48] <ogra_> jodh, my issue is that mountall tries to fsck the bind mount, not the underlying filesystem (i think)
[12:51] <mmrazik> they turned off the internet in germany?
[12:51] <Mirv> sergiusens: yes. although the 5.0.2 improvements are mostly in the Qt modules themselves, and no API changes, so as long as they're installed on the device the fixes are in use. it's the sensors which is now lacking because of this disperancy.
[12:52] <Mirv> sergiusens: some app developers might also want to use something special from 5.0.2, but mostly it's the Qt internal fixes developers have been waiting for
[12:54] <Mirv> sergiusens: do you know if tmoenicke looking at the webkit DPR patch rebasing by the way, or someone else? ken and others would like to have the file_access patch which is in the 5.0.2 package.
[12:55] <sergiusens> Mirv: I would say we should leave that for saucy (topic for migrating in vUDS)
[13:00] <Mirv> sergiusens: ok, that's fine as 5.0.1 works with the rest being 5.0.2 (I double-checked that it also holds true for using qmlwebkit)
[13:00] <Mirv> I need to do a saucy webkit build, though, as well
[13:00] <jodh> ogra_: can you point me to your diff?
[13:09] <sergiusens> Mirv: there is one problem I found though with the osk... it doesn't raise for the _webapps_
[13:13] <Mirv> sil2100: thanks for approving the AP 1.3 merge request :)
[13:15] <Mirv> sergiusens: the phablet ppa 5.0.1 qtwebkit does have the fixTriggerOSKonWebPages.patch, but there haven't been any new related patches flying around as far as I know
[13:39] <sil2100> kenvandine: ping!
[13:47] <kenvandine> sil2100, pong
[13:57] <kenvandine> sil2100, pong
[14:05] <sil2100> kenvandine: hi! I wanted to know how's the status with the phone-app autopilot tests, as I see those are still failing
[14:05] <sil2100> kenvandine: what's the problem? Can I help in any way?
[14:06] <kenvandine> sil2100, i'm really not sure, they passed for me locally a couple days ago
[14:08] <kenvandine> but there was still problems with jenkins not running with the right autopilot
[14:08] <kenvandine> today's failures look like real failures though
[14:14] <kenvandine> sil2100, sigh... looks like it's the swipeToSwitchTabs change
[14:15] <kenvandine> it was deprecated, so i re-enabled that as a temporary fix
[14:15] <sil2100> kenvandine: argh, again someone updated the source but not the tests?
[14:15] <kenvandine> it is no longer deprecated, it has been removed
[14:15] <kenvandine> toolkit changed
[14:18] <nik90> kenvandine: I had this issue as well. I have written a python function which I use to switch tabs. You can find it http://paste.ubuntu.com/5661357/
[14:19] <nik90> kenvandine: It is very similar to reveal_toolbar() function used in the phone-app at the moment.
[14:19] <kenvandine> nik90, cool, maybe we can use that to fix the tests :)
[14:20] <nik90> kenvandine: I think the sdk developers are considering to provide some common autopilot functions we can use like reveal_toolbar(), swipetabs() etc.
[14:22] <kenvandine> it would be useful
[14:23]  * nik90 hates when things cannot be found when you actually search them
[14:25] <nik90> kenvandine: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1177341
[14:30] <mterry> Is the tst_ListViewWithPageHeader.qml test in unity/phablet really unreliable for anyone else?
[14:38] <greyback> mterry: as the author: no :) But I did struggle for quite a while to make it as reliable as possible.
[14:45] <user82> popey, do you update daily?
[14:51] <popey> user82: if there is a build worth flashing to, yes
[14:54] <user82> ok thanks popey. where do you see if it is worth it?
[14:56] <boiko> rsalveti: would you mind taking this one a look: https://code.launchpad.net/~boiko/platform-api/new_apps/+merge/163548
[14:57] <rsalveti> boiko: sure :-)
[14:57]  * rsalveti back from vac, time to get some stuff done ;-)
[15:05] <popey> user82: based on conversations here mostly
[15:07] <ogra_> jodh, sorry it took so long (was buys with other stuff) http://paste.ubuntu.com/5661490/
[15:12] <ogra_> jodh, i'm essentially moving the rootfs mount from a device to a filesystem subdir
[15:13] <ogra_> (and bind mount that)
[15:14] <user82> still waiting for 3g data popey ... but no idea where to look
[15:15] <popey> user82: that hasn't changed since you last asked ☻
[15:17] <popey> user82: I expect we'll make an announcement when 3g works. also https://wiki.ubuntu.com/Touch/Devices/Nexus is a good place to monitor, maybe subscribe to that page
[15:20] <user82> popey, that page i have been looking for a lot
[15:20] <user82> thanks for the link!!!
[15:27] <ThiagoSiqueira> Hi guys, I'm from Brazil and I'm doing a homework for university about Ubuntu Touch. I would like know whether the kernel's version of Ubuntu desk is the same of Ubuntu Touch.
[15:27] <ogra_> no, its an android kernel
[15:28] <ogra_> see the porting wikipage from the channel topic
[15:29] <ThiagoSiqueira> hmm, ok. Thank you very much ogra_
[15:29] <popey> user82: np
[15:31] <sergiuse1s> Mirv: talked to bfiller just now and he's also pushing for adding the dep to the PPA
[15:31] <tvoss> tedg, ping
[15:32] <bfiller> sergiuse1s, Mirv : yes, was writing an email up about this now
[15:32] <bfiller> seems like it's a must have unless there is another option I'm missing
[15:32] <tedg> tvoss, Howdy!
[15:40] <ThiagoSiqueira> Ubuntu Touch uses Android Kernel, right?
[15:46] <Cimi> ThiagoSiqueira, ogra already answered you, yes
[15:48] <rsalveti> sergiuse1s: don't we need to disable mtp for other devices as well?
[15:49] <ogra_> we should disable it for all devices
[15:49] <rsalveti> yeah
[15:49] <rsalveti> oh, the qt migration is for 5.0.2
[15:49] <ThiagoSiqueira> I know, but Android uses many kernel's versions. I would like to know whether the kernel's version is 3.0 or 2.6
[15:49] <ogra_> i thought sergio did that for at least all nexus ones
[15:49] <ThiagoSiqueira> I knew, but Android uses many kernel's versions. I would like to know whether the kernel's version is 3.0 or 2.6
[15:49] <sergiuse1s> rsalveti: ?
[15:49] <ogra_> ThiagoSiqueira, it is the version that cyanogenmod uses for each device
[15:50] <sergiuse1s> rsalveti: want to mumble, I'll tell you what I did
[15:50] <ogra_> (they differ pre device)
[15:50] <rsalveti> sergiuse1s: sure :-)
[15:50] <ogra_> *per
[15:59] <sergiusens> bfiller: Mirv another option would be to backout the _raring_ qt 5.0.2 and just leave it for saucy
[16:40] <sergiusens> rsalveti: you around?
[16:43] <sergiusens> rsalveti: for when you get back https://code.launchpad.net/~sergiusens/touch-preview-images/phablet-build-scripts/+merge/163572
[16:48] <ogra_> sergiusens, you should add a size check
[17:56] <rsalveti> sergiuse1s: I'm now
[17:56] <rsalveti> sergiuse1s: checking the mr
[17:56] <sergiusens> rsalveti: great
[18:05] <rsalveti> ricmm: mind giving a bless at https://code.launchpad.net/~boiko/platform-api/new_apps/+merge/163548 ?
[18:05] <rsalveti> I approved it but would be nice if you could happrove it ;-)
[18:06] <rsalveti> sergiusens: I know it might be a different jenkins now, but any idea why there's no auto-ci happening for ^?
[18:24] <njin> https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1179617
[18:29] <sergiusens> rsalveti: looking at the platform-api issue now
[18:51] <rsalveti> sergiusens: seems I'm back again
[18:51] <rsalveti> weird
[18:54] <sergiusens> rsalveti: i c u now, but icq not :-P
[18:54] <rsalveti> sergiusens: :P
[19:10]  * popey pokes mhall119
[19:11] <sergiusens> kenvandine: hey, how would I use friends on the phone? As in, how doI enable an account?
[19:11] <kenvandine> sergiusens, run uoa-create
[19:12] <sergiusens> kenvandine: thanks, will try
[19:12] <kenvandine> uoa-create twitter $username
[19:15] <mhall119> popey: I'm here, finishing a late lunch
[19:15] <sergiusens> kenvandine: is there a way to get the supported service names?
[19:15] <popey> sergiusens: when are we moving to saucy for daily images?
[19:15] <ricmm> rsalveti: looking
[19:15] <kenvandine> sergiusens, there is an API for libaccounts for that
[19:16] <kenvandine> sergiusens, in the default install just twitter and facebook
[19:16] <kenvandine> but you can install friends-flickr
[19:16] <ricmm> rsalveti: https://jenkins.qa.ubuntu.com/job/platform-api-raring-armhf-ci/10/console
[19:16] <sergiusens> popey: after vUDS most likely
[19:16] <sergiusens> popey: but the hard estimate is something like EOW
[19:16] <kenvandine> friends-foursquare
[19:16] <kenvandine> etc
[19:16] <ricmm> something gone wrong there, can you take a look?
[19:16] <popey> thanks sergiusens
[19:16] <plars> sergiusens: so there's no daily build until then?
[19:16] <rsalveti> ricmm: sergiusens is already taking care of that
[19:16] <ricmm> thanks
[19:16] <popey> mhall119: so we should push saucy builds to the collections ppa
[19:16] <rsalveti> ricmm: just review the code and I can happrove later
[19:16] <sergiusens> plars: there's a broken Qt5 thing going on
[19:16] <mhall119> popey: and core apps too, if we're not already
[19:16] <Fyodorovna> t
[19:16] <sergiusens> plars: that's the reason for no daily build
[19:17] <popey> they're done already mhall119
[19:17] <plars> ah, ok
[19:17] <mhall119> cool
[19:17] <mhall119> popey: I'll do the ones I've uploaded so far
[19:17] <mhall119> going forward, what releases do you want to support?
[19:18] <popey> ditto
[19:18] <popey> well we need raring for desktop
[19:18] <popey> and saucy for tablet/phone
[19:19] <mhall119> any point in providing quantal builds?
[19:19] <popey> no
[19:19] <mhall119> when are device images going to go saucy?
[19:21] <popey> see above, end of week in all likelyhood
[19:31] <user82> popey, also not bad http://cdimages.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/raring-preinstalled.changelog
[19:33] <popey> user82: we should probably link to that on the page..
[19:44] <user82> popey, at least you can see when thee last build was and what happened
[19:47] <achiang> sergiusens: is today a good day to update to the latest (whatever phablet-flash gives me) ? this is for a gnex, just for dev purposes, not for any demo purposes
[19:51] <mhall119> bah, popey how do you upload the same version of a package for a different release?
[19:51] <mhall119> seb128: ^^
[19:51] <mhall119> seb128: uploading to a PPA, to be precise
[19:53] <seb128> mhall119, the ppa web ui let you copy the source or source/binaries
[19:55] <mhall119> seb128: oh nice, I can do them all at once
[19:55] <mhall119> seb128: should I have it re-build them, or just copy the binaries?
[19:56] <seb128> depends of what you copy
[19:56] <mhall119> they're mostly all pure-QML, but there is also a libhud package
[19:56] <seb128> usually you don't need a rebuilt
[19:56] <seb128> you don't need to rebuild then
[19:56] <mhall119> ok
[19:58] <mhall119> sweet, thanks seb128
[19:58] <mhall119> popey: I've got all the collections packages copying to Saucy
[19:59] <user82> what exactly is the feature "Accelerated_Display "?
[19:59] <user82> in the table: https://wiki.ubuntu.com/Touch/Devices/Nexus
[20:00] <seb128> mhall119, yw ;-)
[20:03] <mhall119> user82: probably hardware OpenGL support
[20:04] <mhall119> instead of software compositing
[20:04] <user82> ah might be true mhall119
[20:04] <popey> oh sweet! I thought we'd have to re-push them all
[20:04] <popey> that's awesome thanks seb128
[20:04]  * popey ticks the "learned something new today" box on his to-do list
[20:15] <rsalveti> ls -l
[20:15] <rsalveti> argh
[20:15] <rsalveti> compiz
[20:27] <sergiusens> achiang: latest for dev is ok
[20:30] <achiang> sergiusens: thanks
[22:46] <rickspencer3> does anyone else get this effect in QtCreator where the QML scene doesn't quite load?
[23:23] <mhall119> rickspencer3: sometimes I have it load but the window doesn't get focus, so it's hidden behind QtCreator
[23:37] <rickspencer3> mhall119, that's not what I see
[23:42] <mhall119> then I haven't experienced what you are
[23:43] <mhall119> qmlscene loads for me every time, unless there's an error in my code in which case I get an error message
[23:43] <rickspencer3> mhall119, right
[23:43] <rickspencer3> mhall119, https://bugs.launchpad.net/touch-preview-images/+bug/1179716
[23:43] <rickspencer3> maybe there is something in my settings or something


[01:07] <mx6523> !usb
[01:08] <mx6523> i got a persistent live install, is there a way to make it faster?
[01:08] <guiverc> installing on a real hdd/ssd comes to mind, thumb-drives are very slow at writing...
[01:10] <mx6523> i used mkusb to create a persistent live USB install, but maybe it would be faster if i installed with the ubuntu installer?
[01:26] <oerheks> any live iso is slow.
[04:27] <jimmyorrea> Hey guys, im pretty new at this so i would appreciate very specific help as if I was a child,hehehe . Tried installing lubuntu on an old computer using a bootable usb flashdrive, everything was ok until the very end where it says it cannot install the grub boot , ive tried several ways but im really really lost, id appreciate the help
[04:36] <jimmyorrea> i decided to go on installing it without the grub booter and it warned me “/vmlinuz kernel on partition /dev/sda2 and root= /dev/sda2” but i dont know what that is or how to type it
[04:51] <jimmyorrea> hey guys, im installing lubuntu with a usb flashdrive and everything ok untill the very end where it says “GRUB installation failed” “The ‘grub-efi-amd64-signed’ package failed to install into /target/ . Withoit the GRUB boot loader, the installed system will not boot”..... i dont know what to do, help please
[05:05] <guiverc> hi jimmyorrea, sorry I'm not good at grub (I'd refresh myself by looking up details if I had to do it, but UEFI can complicate things that I'm not very familiar with), lubuntu is an official flavor, so you could try #ubuntu too
[05:07]  * guiverc adds, don't ask in both channels at the same time, give people a chance to answer like you've done here first :)
[06:05] <GChan0226> henlo
[06:08] <guiverc> GChan0226, Hi, if you have a Lubuntu support question, please ask it (try and keep to a single line, and be patient as people will respond when they can)
[06:09] <GChan0226> how to install lubuntu on a hp laptop with SSD storage
[06:09] <guiverc> Have you looked at the Lubuntu manaul, ie. https://manual.lubuntu.me/stable/1/Installing_lubuntu.html
[06:10] <guiverc> (hdd or ssd, method is the same)
[06:12] <GChan0226> I am unable to continue at the 'setting up partitions' step, where the option 'erase disk' is nowhere to be seen.
[06:13] <guiverc> what release of Lubuntu?  If it has windows already installed, it needs to be cleanly shutdown (ie. no hibernate, no fastboot otherwise the unclean file-system will cause it to be ignored to prevent dataloss)
[06:18] <GChan0226> I am on 20.04.1 LTS. The laptop came with windows 10 preinstalled. I booted up Lubuntu with a USB. I pressed 'shut down' on windows before proceeding to power the laptop up again to the boot menu.
[06:19] <guiverc> actually on unclean fs I'd expect erase disk to show anyway, how old is the laptop (sorry I may not answer for awhile, called away)
[06:19] <GChan0226> 3 months old
[06:22] <GChan0226> btw, the only option available is 'manual partitioning'
[06:34] <guiverc> GChan0226, I would try using the manual partition option to remove ('-') all existing partitions... I recall having trouble with one device but it was awhile ago & no longer provides trouble.. when in manual partitioning do you see the current entries/partitioning?
[06:40] <guiverc> the other thing you could check (which should apply) is no partition is mounted; if any partition is mouned erase disk won't be clickable... (exit calamares/installer & use kde partition manager to unmount, then exit kde partition manager & re-start calamares)
[06:40] <guiverc> GChan0226, ^
[06:41] <guiverc> that's usually an issue for me if 'swap' is detected on 'live' boot, it's used to speed performane, it may impact you if you explored your ssd before starting installer/calamares
[06:49] <sanc40m> hi guys good day
[06:50] <sanc40m> downloaded twice yesterday
[06:50] <sanc40m> all two downloads have errors
[06:51] <sanc40m> was not able to make them boot from usb
[06:52] <guiverc> sanc40m, what release did you download?  (I'm assuming Lubuntu)
[06:54] <guiverc> the manual link for installation is https://manual.lubuntu.me/stable/1/Installing_lubuntu.html (contains details on downloading.. & writing media etc)
[06:54] <GChan0226> I can see that there are 4 partitions
[06:54] <GChan0226> I don't understand what is the mounting of partitions
[06:56] <guiverc> You `mount` a partition to explore what files/directories are on it, so exploration of a ssd before install (looking at what's there) could cause a `mount` to occur.  It's a command, but is an operation by file manager (pcmanfm-qt) in exploration (pcmanfm-qt does command for you)
[06:59] <GChan0226> I opened up kde partition manager and I checked that only the bigger partition is mounted
[07:00] <GChan0226> clicking 'unmount' result in fails
[07:00] <GChan0226> 'The file system on partition /dev/nvme0n1p3 could not be unmounted.'
[07:01] <GChan0226> Details:
[07:02] <GChan0226> Command: umount --verbose --all-targets /dev/nvme0n1p3
[07:02] <GChan0226> unmount: /cdrom: target is busy
[07:03] <guiverc> ensure you are looking at your ssd, /cdrom will refer to your install media (thumb-drive most probably)
[08:09] <doc499> i'm trying to install 20.04.1 from a usb key on a toshiba laptop. first time during bootup when it runs a file check it found one error but still booted into lxqt (cont.)
[08:09] <doc499> since there was no message about which file was in error i decided to re-write the iso on the key to hopefully correct the error (cont.)
[08:10] <doc499> then when i booted from the usb key i got a kernel panic about not syncing, no init found
[08:11] <doc499> is there a way to check the file system integrity on the key without booting from it? i can access it from a file manager
[08:11] <doc499> also, does this suggest that the iso was not written correctly to the usb key? maybe the key itself is defective
[08:11] <doc499> just trying to troubleshoot here
[08:11] <guiverc> did you verify the ISO (unlikely but still worth checking on issues), but most importantly the write to install media needs validation (the squashfs contians ALL files so pointing out the file is pointless when they're squashed together; all are good or all are wrong)
[08:12] <doc499> guiverc, yeah i ran 256shasum and it was correct
[08:12] <guiverc> the write to thumb-drive is the most likely issue I have..
[08:13] <doc499> i suppose i can just try re-writing it again and checking. it did boot the last time even after the error message about the one file error, so it might be the key that's defective
[08:13] <guiverc> there are many types of ISO files, not all writing tools cope with all, so I'd suggest trying another tool. the manual suggests what has been tested (for windows, mac & of course GNU/Linux)
[08:14] <doc499> guiverc, i was using dd
[08:14] <doc499> dd bs=4M if=/path/to/iso of=/dev/sdb conv=fdatasync
[08:14] <guiverc> :)  `dd` is good...  try another thumb-drive maybe..  did you `sync` post completion to ensure all data written
[08:15] <doc499> guiverc, see my previous post of the command used
[08:17] <guiverc> I don't use that conv=, my last iso write was `sudo dd bs=4M oflag=sync status=progress of=/dev/sdb if=/de2900/lubuntu_64/focal-desktop-amd64.iso`  but by sync I meant `sudo sync` to ensure any buffers in memory get written to devices (ie. flush buffers from ram)
[08:21] <doc499> guiverc, before i used to use && sync at the end of the command, then somewhere i read about dd's built-in conv=fdatasync option, so maybe i'll just go back to && sync and see if that makes a difference
[08:22] <doc499> it is a cheap "walgreens" usb drive, so that could be an issue as well
[08:22] <doc499> it's not very old thought
[08:22] <guiverc> I'm not aware of fdatasync... you maybe right & it's not needed... it was a thought I had so offered it.
[08:22] <doc499> well, i'll just use the && sync command and see how it goes
[08:23] <guiverc> Yeah I've had 3/5 "new" verbatim (pack of 5) that won't hold a valid ISO, annoying with current lockdown as I can't return & swap..
[08:23] <guiverc> I won't buy verbatim again though!
[08:27]  * guiverc is away
[08:32] <doc499> ok gonna reboot and see, thanks for your help
[09:03] <lubuntu_> i just installed lubuntu 20.04.1 on a toshiba laptop, but when i boot it just drops to a grub command line and not a menu
[09:03] <lubuntu_> i'm on the livecd right now trying to troubleshoot
[09:03] <lubuntu_> i had 18.04 lts previously installed and reformatted the / partition
[09:04] <lubuntu_> however, there was a /dev/sda1 partition of about 34mb that i left alone, so maybe i did something wrong during installation
[09:05] <lubuntu_> is on /dev/sda3 as it was before
[09:05] <lubuntu_> root / is on /dev/sda3 as it was before
[09:05] <lubuntu_> did i need to make a bios/grub boot flag on /dev/sda1 during installation?
[09:07] <lubuntu_> i'm trying to salvage this without having to do the entire installation again
 Guys pls help,  … Iam having an old desktop, running on win 7. It is very slow now in browsing. I ve only 2 gb ram, core 2duo 2.5 ghz, 500 gb hardisk . I tried ubuntu but it is slower than 7. I am going to install lubuntu now, but there are two versions 18.4 and 20.4 , which one is better?
 Do you have any suggestions for me? I just wanna browse faster
[09:11] <lubuntu_> this is the current layout: https://dpaste.com/BESYTCBKH
[09:12] <guiverc> @Aj, O
 What
[09:12] <guiverc> I'd suggest 20.04 as it has more supported life (3 years from 2020-April), 18.04 reaches EOL in 2021-April (3 years from 2018-April)
 Ok thanka
 Thanks
[09:12] <guiverc> I tested both using a c2d 2GB thinkpad sl510... so both are okay
 Okay
 I will try the 20.4 version
[09:13] <guiverc> with that limited RAM though, software choice is very important, and wrong software/app choices can waste your limited ram
 How much swap should i use
[09:14] <guiverc> 18.04 is GTK2 (very few GTK2 apps as most are GTK3), 20.04 is Qt5..
[09:14] <guiverc> Swap files can be used in both, so can be adjusted as needs require.   I'd say 4 or 5GB
 I only need to browse and stream live classes.
[09:15] <guiverc> 20.04 by default won't create SWAP, it's done manually (some don't like it, esp. those with SSDs). 18.04 defaults to having swap from memory
[09:16] <lubuntu_> guiverc: i was the other guy chatting with you about 15 mins about regarding the usb key issue
[09:16] <lubuntu_> i fixed that problem and installed, but now grub won't boot correctly from the hard disk, i must have done something wrong during setup
 What are u talking about
[09:19] <lubuntu_> the /dev/sda1 partition is 34mb in size and is an EFI system, but i didn't assign it to anything during setup, i just reformatted /dev/sda3 as / as it was previously with 18.04 and assigned /dev/sda4 as /home without reformatting. The install went fine, then when i boot into the new installation, it just drops to a grub command line prompt with no menu options
[09:21] <lubuntu_> here's the partition table layout: https://dpaste.com/BESYTCBKH
[09:21] <lubuntu_> i guess grub installed incorrectly during setup?
[09:22] <lubuntu_> it can't find my root partition or even show a menu?
[09:29] <lubuntu_> this was the advice i found in an askubuntu thread: https://dpaste.com/GPHG6E4X7
[09:29] <lubuntu_> haven't tried it yet
[09:33] <lubuntu_> there is no /boot/efi on the system partition
[09:34] <lubuntu_> i was create that directory and continue with the commands in the paste link
[09:38] <lubuntu_> if all else fails and i re-install, how would i assign /dev/sda1 during setup?
[09:43] <lubuntu_> i chroot to the system partition, created /boot/efi and tried to reinstall grub to /dev/sda and got the following error message: https://dpaste.com/9666EKM2P
[09:49] <lubuntu_> doing some more research, apparently, i was supposed to boot the install medium in efi mode
[09:51] <lubuntu_> i'm already booted into the install medium\
[09:52] <lubuntu_> [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
[09:52] <lubuntu_> gives: EFI boot on HDD
[09:53] <lubuntu_> right now, i'm following these instructions: https://wiki.debian.org/GrubEFIReinstall#Reinstalling_grub-efi_on_your_hard_drive
 Why the fuck people are using this bridge bot when they are seeking support.  Its …], because they write from the irc
 @nihal697 [To the kittens probably], to anyone
 @lubuntu_ [<lubuntu_> right now, i'm following these instructions: https://wiki.debian.org/ …], Does BIOS/firmware menu shows lubuntu/ubuntu entry to you?
 @N0um3n0 [because they write from the irc], Irc?
[12:32] <guiverc> fyi: user lubuntu_ left some time ago
 @N0um3n0 [to anyone], Only kittens, i dun understand why people turned to be softies all of a sudden
 @guiverc [<guiverc> fyi: user lubuntu_ left some time ago], Lmao
 Thanks for information
[12:34] <guiverc> @nihal697, https://wiki.ubuntu.com/IRC/ChannelList
 @guiverc [<guiverc> @nihal697, https://wiki.ubuntu.com/IRC/ChannelList], O.o … Thanks !
[12:58] <tomreyn> nihal697: i'd say the irc end of the bridge was around a good while before the ones you're on. ;-)
[12:58] <tomreyn> * the one
 I'm going to switch to lubuntu from windows, is it ok to keep d and e drives as ntfs without formatting them?
 @Aj [I'm going to switch to lubuntu from windows, is it ok to keep d and e drives as …], Yeah completely fine. … Just read the guides and do not install lubuntu in the whole hard drive, otherwise it will be lost automatically
 @nihal697 [Yeah completely fine. … Just read the guides and do not install lubuntu in the who …], I am only formatting c
 @nihal697 [Yeah completely fine. … Just read the guides and do not install lubuntu in the who …], Bro, is lubuntu 20.4 fast  with 2 gb ram , core2 duo 2.5 ghz
 @Aj [I am only formatting c], Whatever u do, just read twice when u r in the installation process.
 @Aj [Bro, is lubuntu 20.4 fast  with 2 gb ram , core2 duo 2.5 ghz], Well, in comparison to other distros, yes definitely. … You can try bodhi linux or antiX also if you dont get satisfied with the performance of Lubuntu. But they are very minimal.
 @nihal697 [Well, in comparison to other distros, yes definitely. … You can try bodhi linux or …], Lubuntu 18.04 is working fine though
 @Aj [Lubuntu 18.04 is working fine though], ¯\_(ツ)_/¯
 @Aj [Bro, is lubuntu 20.4 fast  with 2 gb ram , core2 duo 2.5 ghz], Very fast ;)
 @chikatambun [i have k43sj  board i want to upgrade the memory... will it support 1600MHz...? …], I don't know if it's still useful, but I have the same laptop here. I have upgraded ram. It doesn't run 1600mhz
 @Aj [Bro, is lubuntu 20.4 fast  with 2 gb ram , core2 duo 2.5 ghz], It's faster if you run the bare os. However, many modern tasks such as running office apps or web browser with Gmail/YouTube will be painful on any os. I strongly recommend you to consider upgrading your ram (even 4gb would be much much better)


[15:36] <zillah> hi all
[15:37] <kwadroke> hello
[15:38] <zillah> how's it going this morning?
[15:39] <kwadroke> it's going ok, I suppose
[15:39] <kwadroke> for a monday anyway
[15:39] <zillah> lol i know the feeling
[15:39] <kwadroke> how's it going with you?
[15:42] <zillah> not too bad, i need to be getting some work done, but having a hard time waking up this morning.  feel more like playing than working
[15:42] <kwadroke> same here
[15:44] <zillah> i'm trying to make shairplay work on ubuntu server  :)
[15:44] <zillah> doubleb and i got it running on macOS the other night, but having problems with ubuntu
[15:45] <kwadroke> haven't heard of that till now
[15:45] <kwadroke> but I'm trying to move away from apple products
[15:47] <zillah> i've always been a freebsd guy until recently...i can't help myself, i like macos and don't even know why
[15:48] <zillah> i guess it's like freebsd with a much better gui and a lot better software support
[15:49] <Ahmuck> give me a link, and i can prolly get it working in under an hour
[15:49] <zillah> i keep getting RSA.xs:178: OpenSSL error: no start line at ./shairport.pl line 89.
[15:50] <zillah> i tried upgrading Crypt::OpenSSL::RSA but that didn't help
[15:54] <Ahmuck>  a link to the software
[15:56] <zillah> to shairport?
[15:56] <Ahmuck> yes
[15:56] <zillah> http://mafipulation.org/static/shairport-0.05.tar.gz
[15:58] <Ahmuck> is Apple seriously locking down speakers now?
[15:58] <zillah> yep, isn't that awesome
[15:59] <zillah> really makes me want to get everything back on linux
[16:04] <Ahmuck> p   libcrypt-openssl-rsa-perl                                                - Perl module providing basic RSA functionality
[16:04] <Ahmuck> sudo aptitude search install libcrypt-openssl-rsa-perl
[16:05] <zillah> libcrypt-openssl-rsa-perl is already the newest version.
[16:05] <zillah> 0 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.
[16:05] <zillah> :)
[16:14] <zillah> ah, i had an old version
[16:15] <zillah> now all i get is Can't exec "avahi-publish-service": No such file or directory at shairport.pl line 87.
[16:19] <zillah> so maybe my avahi-daemon.config needs to be fixed, i dunno
[16:27] <Ahmuck> what avahi stuff do you have installed?
[16:29] <Ahmuck> i   avahi-autoipd                                                            - Avahi IPv4LL network address configuration daemon
[16:30] <Ahmuck> i   avahi-daemon                                                             - Avahi mDNS/DNS-SD daemon
[16:30] <Ahmuck> i   avahi-utils                                                              - Avahi browsing, publishing and discovery utilities
[16:30] <Ahmuck> i   libavahi-client3                                                         - Avahi client library
[16:30] <Ahmuck> i   libavahi-common-data                                                     - Avahi common data files
[16:30] <Ahmuck> i   libavahi-common3                                                         - Avahi common library
[16:30] <Ahmuck> i   libavahi-core7                                                           - Avahi's embeddable mDNS/DNS-SD library
[16:30] <Ahmuck> i   libavahi-glib1                                                           - Avahi glib integration library
[16:30] <Ahmuck> i   libavahi-gobject0                                                        - Avahi GObject library
[16:31] <zillah> root@ubuntu:/home/mitchell/shairport-0.05# dpkg -l |grep avahi
[16:31] <zillah> ii  avahi-daemon                              0.6.23-4ubuntu4.1                 Avahi mDNS/DNS-SD daemon
[16:31] <zillah> ii  libavahi-client3                          0.6.23-4ubuntu4.1                 Avahi client library
[16:31] <zillah> ii  libavahi-common-data                      0.6.23-4ubuntu4.1                 Avahi common data files
[16:31] <zillah> ii  libavahi-common3                          0.6.23-4ubuntu4.1                 Avahi common library
[16:31] <zillah> ii  libavahi-core5                            0.6.23-4ubuntu4.1                 Avahi's embeddable mDNS/DNS-SD library
[16:31] <zillah> ii  libavahi-glib1                            0.6.23-4ubuntu4.1                 Avahi glib integration library
[16:31] <Ahmuck> i   libavahi-ui0                                                             - Avahi GTK+ User interface library
[16:31] <Ahmuck> i   python-avahi                                                             - Python utility package for Avahi
[16:32] <Ahmuck> suu need libavahi-core7
[16:33] <Ahmuck> what ubuntu version r u using?
[16:34] <zillah> 9.04
[16:37] <Ahmuck> ah, nm
[16:37] <Ahmuck> i'm using 11.04
[16:37] <Ahmuck> why so far back?
[16:39] <Ahmuck> 9.04 is not listed in repos because it had security issues
[16:39] <Ahmuck> 9.10 is about to fall out of support iirc
[16:39] <Ahmuck> and 10.04 is the latest Long Term Support release
[16:39] <zillah> lol i haven't upgraded much because it always breaks vmware
[16:40] <Ahmuck> ah.
[16:40] <Ahmuck> ur using VMWare for server VM machines?
[16:40] <zillah> and i haven't wanted to recomplie vmware because it seems i have a perpetual free license for vmware infrastructure :)
[16:41] <zillah> i have a server 2008 virtual machine i use as a backup domain controller
[16:41] <zillah> i installed avahi-utils and now i get Avahi publishing failed! Do you have avahi-publish-service on your PATH? at shairport.pl line 65, <DATA> line 23.
[16:42] <Ahmuck> u upgrade to libavahi-core7?
[16:43] <Ahmuck> that service is directly releated to mDNS.  u know how to check to see what services are running?
[16:43] <zillah> i tried apt-get install libavahi-core7 and get "not found"
[16:44] <zillah> other than ps | grep "service"...no
[16:45] <Ahmuck> sudo apt-get install sysv-rc-conf
[16:45] <zillah> ah...service --status-all i guess
[16:46] <zillah> what's the sysv rc.conf for?
[16:46] <zillah> i don't see anything about mdns
[16:47] <Ahmuck> [05/23/11 10:30] <Ahmuck> i   avahi-daemon                                                             - Avahi mDNS/DNS-SD daemon
[16:47] <Ahmuck> mDNS/DNS-SD
[16:47] <zillah> ah, duh lol
[16:47] <Ahmuck> sysv.rc.conf is for those command line challanged people
[16:48] <Ahmuck> but i see u can grep, so u prolly don't need it
[16:48] <zillah> i only have command line  :)
[16:48] <Ahmuck> well, sysv-rc.conf is a term app
[16:48] <Ahmuck> anywho
[16:49] <Ahmuck> so, ur service isn't started.  u know how to start/stop a service, to see if it's started, etc.
[16:50] <zillah> root@ubuntu:/home/mitchell/shairport-0.05# ps aux|grep avahi
[16:50] <zillah> avahi     9747  0.0  0.0  31896  1672 pts/1    S    10:42   0:00 avahi-daemon: running [ubuntu.local]
[16:50] <zillah> avahi     9748  0.0  0.0  31764   532 ?


[07:25] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: VMware alternatives: discover open source @ https://ubuntu.com//blog/vmware-alternatives
[07:57] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: Charmed Kubernetes and Huawei OceanStor Dorado All-Flash storage integration verificati... @ https://ubuntu.com//blog/charmed-kubernetes-and-huawei-oceanstor-dorado-all-flash-storage-integration-verification-reports
[08:10] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: Kubeflow just applied to join CNCF – what does it mean for you? @ https://ubuntu.com//blog/kubeflow-applied-join-cncf
[17:56] -SwissBot:#ubuntu-news- ::Planet:: Full Circle Magazine: Full Circle Weekly News #285 @ https://fullcirclemagazine.org/podcast/full-circle-weekly-news-285/
[20:59] -SwissBot:#ubuntu-news- ::Planet:: Scarlett Gately Moore: KDE Gear snaps round 3! @ https://www.scarlettgatelymoore.dev/kde-gear-snaps-round-3/
[22:58] -SwissBot:#ubuntu-news- ::Planet:: The Fridge: Call for nomination for the Ubuntu Membership board @ https://fridge.ubuntu.com/2022/10/26/call-for-nomination-for-the-ubuntu-membership-board/


[03:56] <ScottK> broder: This just means you should be doing more uploading to Debian.
[05:42] <vibhav> https://bugs.launchpad.net/ubuntu/+source/libgssapi-perl/+bug/935236 is fixed in Debian
[05:43] <vibhav> Should I sync or prepare a debdiff?
[05:44] <micahg> vibhav: does it need an FFe for the sync?
[05:44] <vibhav> micahg: i dont know
[05:45] <micahg> well, it's unseeded with 2 reverse-dependencies, so sync would be preferable
[05:45] <micahg> but check if it needs an FFe
[05:45] <vibhav> I did not understand what you just said :(
[05:46] <micahg> it also depends on if the new version needs other things pulled in
[05:46] <micahg> !ffe | vibhav
[05:46] <vibhav> micahg: I know what is a FFe
[05:46] <vibhav> The "unseeded with 2 reverse-dependencies"
[05:46] <vibhav> part
[05:46] <micahg> vibhav: not on any images and only 2 other packages use it
[05:47] <vibhav> micahg: from where did you know that?
[05:47] <micahg> vibhav: seeded-in-ubuntu and reverse-depends (2 tools in ubuntu-dev-tools)
[05:47] <vibhav> ah
[05:49] <vibhav> So I shall request a sync
[05:51] <micahg> well, it's not fixed, it's disabled, but that's fine
[05:55] <micahg> was it decided if hardening enablement needs an FFe or not?
[06:02] <RAOF> Sounds like a feature (but a pretty safe one) to me.
[06:02] <micahg> vibhav: I forgot to ask if it builds :)
[06:02] <vibhav> micahg: Doing it right now
[06:03] <micahg> vibhav: already replied to your bug
[06:03] <vibhav> ah
[06:04] <vibhav> The Ill prepare a debdiif, right?
[06:04] <micahg> vibhav: yeah, that'll work, just make sure it builds first :)
[06:09] <vibhav> micahg: I just need to add the patch to debian/patches/ right? (And not modify the source instead)
[06:10] <micahg> vibhav: and update the debian/patches/series file
[06:10] <vibhav> ok
[06:14] <vibhav> uploaded packages, hopes that it builds :)
[06:14] <micahg> it's a quick package
[06:17] <vibhav> "start is 24 minutes"
[06:17] <vibhav> drat, Ill use pbuilder
[06:17] <micahg> vibhav: right, a local build should be quick
[06:19] <vibhav> Till now, its fine
[06:19] <vibhav> dependencies have been installed
[06:19] <vibhav> done!
[06:19]  * vibhav attaches debdiff
[06:22] <vibhav> micahg: Done :)
[06:23] <vibhav> Could it be backported to oneiric?
[06:23] <vibhav> micahg: And please review the debdiff
[06:24] <micahg> vibhav: does an oneiric build fail the same way?
[06:27] <vibhav> micahg: Not sure, let me ask somebody
[06:28] <micahg> vibhav: why were you asking me about oneiric?
[06:29] <vibhav> micahg: Never MInd
[06:55] <vibhav> I thought/window 7
[06:55] <vibhav> oops :)
[07:03] <dholbach> good morning
[07:04] <ajmitch> morning dholbach
[07:04] <dholbach> hey ajmitch
[07:07] <geser> Hi dholbach and ajmitch
[07:08] <dholbach> hey geser
[07:13] <vibhav> micahg: ping
[07:14] <micahg> vibhav: pong
[07:15] <vibhav> micahg: Did you check my debdiff
[07:15] <micahg> vibhav: no, I'm working on other things
[07:17] <vibhav> ah fine
[07:20] <vibhav> dholbach: Do you have some free time?
[08:11] <vibhav> kdebase is not present in oneiric and precise
[08:11] <vibhav> How can it be brought into the distros
[08:13] <geser> why? what's the problem?
[08:13] <vibhav> https://launchpad.net/ubuntu/+source/kdebase
[08:13] <vibhav> Its only present in Natty, maverick, lucid and harfy
[08:13] <vibhav> hardy*
[08:15] <geser> "In oneiric kdebase source was renamed kde-baseapps" (lp: #814411)
[08:16] <vibhav> ah
[08:16] <vibhav> thanks
[08:18] <vibhav> LP: #814411
[14:05] <mfisch> tumbleweed: Whet did you mean in your comment for 959347, "It also doesn't close this bug"
[14:05] <tumbleweed> the changelog entry doesn't include LP: #959347
[14:06] <mfisch> tumbleweed: oh, ok
[14:06] <mfisch> tumbleweed: why is the version 0.3.8-0ubuntu1 when we no longer have any patches in there?
[14:06] <mfisch> is it always 0ubuntu1 for us?
[14:07] <tumbleweed> mfisch: firstly, it's not a native package so it neends to be dash something
[14:08] <tumbleweed> http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
[14:08] <tumbleweed> the first upload in debian will be -1. We want to get that when its available, so we want something that sorts before it
[14:08] <tumbleweed> we also want it to be clear that its an ubuntu modification
[14:08] <tumbleweed> so we use -0ubuntu1 whenever grabbing new upstream versions and leapfrogging debian
[14:22] <mfisch> tumbleweed: got it, thx
[14:49] <astraljava> Hi gang, I'm building ubuntustudio-meta on my precise pbuilder, and stumbled upon a few warnings:
[14:49] <astraljava> dpkg-gencontrol: warning: Recommends field of package ubuntustudio-graphics: unknown substitution variable ${germinate:Recommends}
[14:50] <astraljava> I couldn't find much info regarding that variable on dpkg-gencontrol documentation, but I admit I may not know where to look. Any pointers, anyone?
[15:21] <mfisch> tumbleweed: new debdiff incoming
[15:23] <Laney> astraljava: that usually means that nothing has put any information into that substvar
[15:23] <Laney> if that's intentional then you don't need to worry
[15:25] <astraljava> Laney: Ok, I'll ignore it for now. Thanks!
[16:22] <jtaylor> yey got a reply from upstream wanting the modified files instead of patches :/
[16:22] <jtaylor> thats a good sign
[16:25] <nigelb> jtaylor: Looks like they have a great way to track changes :D


 @Alon Ganon, Hey, welcome! Glad to have you here :)
 @Alon Ganon, o/
 So what's the plan for lxqt on Lubuntu?
[01:04] <wxl> we're ditching it
[01:04] <wxl> it's no fun any more
 hahahahahaha
[01:04] <wxl> we're going to use gtk2 foreverrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr
 Very funny
 Is it there yet, if not, will it be on stable?
 @wxl, Oh *obviously* /s
 @AceHW, Yep
 As a separate edition
 @tsimonq2, Oh.
 @Alon Ganon, Hey, and I was the guy responding to you :)
 Any chance Ubuntu won't have problems in LTS release?
[01:06] <wxl> yes because everything's always perfect all the time??
 @AceHW, A very large chance that it will go smoothly tbh
 @wxl, Yes absolutely /s
 Both Ubuntu and Debian had problems last time, right?
 ...
[01:06] <wxl> i agree with @tsimonq2 on that but "won't have problems?" NOTHING is without problems
 ???
[01:06] <wxl> including all the commercial options out there
[01:07] <wxl> there's ALWAYS going to be problems
 ^
 Right'
[01:07] <wxl> which is good because that's room for improvement
 Exactly
[01:07] <wxl> where's agaida to give us that quote that what's stable is dead, at least according to biology
[01:07] <wxl> ?
 XD
[01:08] <wxl> anyways i've run "last time's" release for a long while without problems
[01:08] <wxl> well
[01:08] <agaida> one should use quassel and have this in the backlog
[01:08] <wxl> without anything unusual
[01:08] <wxl> problems happen. but it's ok.
[01:08] <wxl> BIG problems are bad problems. but there won't be those.
[01:08] <agaida> but here it is
[01:09] <agaida> There's this special biologist word we use for "stable". It's "dead". ~ Jack Cohen
[01:09] <wxl> hey wait does quassel run in a terminal?
[01:09]  * wxl ducks and is out
[01:09] <agaida> with the irssi plugin - for sure
 hahahahahahahahaha
 Ooh ok
[01:14] <agaida> wxl: for you only - https://github.com/phhusson/quassel-irssi
[05:34] <wxl> !info linux xenial
[05:34] <wxl> !info linux-generic xenial
[05:35] <wxl> !info linux-generic zesty
[05:35] <wxl> !info linux-generic artful
[05:35] <wxl> !info linux-generic artful-proposed
[05:35] <wxl> !info linux-generic zesty-proposed
[05:35] <wxl> !info linux-generic bionic
[05:36] <tsimonq2> wxl: boooooo use !upkg linux-generic bruv
[05:36] <tsimonq2> In DDG
[05:36] <tsimonq2> !upkg linux-generic in DDG
[05:36] <wxl> yeah that's no fun
[05:36] <tsimonq2> Bah :P
[05:45] <wxl> um
[05:45] <wxl> @tsimonq2: why does that info disagree with https://launchpad.net/ubuntu/+source/linux ?
[05:45] <wxl> i.e. for artful:
[05:45] <wxl>  4.13.0-16.19 	release (main) 	2017-10-14
[05:45] <wxl> 4.13.0-21.24 	security, updates (main) 	2017-12-20
[05:45] <wxl> 4.13.0-22.25 	proposed (main) 	2017-12-20
[05:45] <wxl> but above is <IP_ADDRESS>.22 main, <IP_ADDRESS>.23 proposed
 @wxl, *shrug* but I'd trust Launchpad more
[05:49] <wxl> well yeah it's weird because it's behind on main but ahead on proposed wtf
[05:54] <JackFrost> https://launchpad.net/ubuntu/+source/linux-meta
[05:54] <tsimonq2> wxl: ^^^
[05:54] <wxl> um ok
[05:55] <tsimonq2> wxl: Kernel metapackages sometimes don't have the same versions as the kernel packages themselves
[05:55] <tsimonq2> (they should, I think(
[05:55] <tsimonq2> )
[05:55] <wxl> confusing. so linux-generic is right?
[05:55] <wxl> (for kernel version)
[05:55] <JackFrost> To quote ubot93: < ubot93> linux-generic (source: linux-meta)
[05:56] <tsimonq2> Right, linux-generic is a metapackage
[05:56] <wxl> oh so linux is correct ok good
[05:58] <wxl> oh my bionic main still has the Bad Kernel™
[05:58] <tsimonq2> wxl: Are You Sure?
[05:58] <wxl> yep
[05:58] <wxl> fix was in 4.13.0-21.24 and bionic main is 4.13.0-17.20
[05:59] <tsimonq2> wxl: You've read changelogs too?
[05:59] <wxl> getting there
[05:59] <wxl> yep fix ain't in there
[06:00] <tsimonq2> Then go ping someone. :P
[06:00] <wxl> you go ping someone i'm trying to collect this mess of a bug together
[06:00] <tsimonq2> ¯\_(ツ)_/¯
[06:00] <wxl> wait hold on
[06:00]  * wxl grumbles still about launchpad
 (Photo, 720x1280) https://i.imgur.com/bTyNVtv.jpg
 Who needs Android Oreo when you can have better selfies? 😐
 @VikingRedwolf, Better? please... I need a miracle.
 😂
 lies! you're sexy!
 "please,  only a human face, no dogs or cats allowed for face detection"
 (Document) http://vps.tsimonq2.net:8080//file_3258.mp4
 (Document) http://vps.tsimonq2.net:8080//file_3259.mp4
 lol
 I just realised there's not a single gtk3 ftp client for linux
[13:00] <agaida> ftp is dead
 😢
 I use it with my phone because kdeconnect doesn't work, and I hate cables
[13:01] <agaida> buy a microsoft lumia :D
 (Document) http://vps.tsimonq2.net:8080//file_3260.mp4
[13:01] <agaida> hrhrhr
[18:11] <wxl> just FYI should it ever come up https://bugs.launchpad.net/ubuntu-qa-website/+bug/1740704
[21:18] <lynorian_next> ftp has beenn around too long
[21:18] <lynorian_next> and sucks in some ways
[21:18] <lynorian_next> also who is this kev bowring person marking all these ubuntu-manual tests needed as invalid?
[21:19] <wxl> flocculant. probably the biggest contributor to the testcases
[21:20] <lynorian_next> oh that is flocculant
[21:20] <lynorian_next> ok
[21:20] <lynorian_next> just did not recognize the name
 @lynorian_next, sftp?
 ssh?
 dav?
[21:27] <lynorian_next> yes that still works fine
[21:28] <lynorian_next> or rsync or zsync
 I need a dav server for me phone then
[21:31] <agaida> one could consider nextcloud
 that uses internet
 I need to share things without a cable. and pushbullet and airdroid are shitty
 kdeconnect is perfect, if it worked
 Happy 2018 to all
 Same to you :D
 (Document) http://vps.tsimonq2.net:8080//file_3267.mp4
 (Sticker, 512x512) http://vps.tsimonq2.net:8080//file_3268