[06:14] good mornnig [06:22] Good morning. [07:09] omg fixed the test laptop [07:09] * valorie writes to the list [07:20] KCI-E :: E: extra-cmake-modules source: build-depends-on-metapackage build-depends: qt5-default [07:20] Oo [07:21] our isos are huge! [07:21] too big for my 1gb sticks [07:21] valorie: How huge? [07:22] I'd like to mention again that ubuntu still fits on like a CD and the rest is filled up with language packs... [07:22] to be fair, almost everyone else is going over 1 gb as well [07:22] not ubuntu though [07:22] for giggles I sorted all the ISOs by size [07:22] what else is there? [07:23] we're not the biggest [07:23] I seed all the ISOs [07:23] Hehe, who is? [07:23] everything that isn't EOL [07:24] the plasma5 beta2 ISOs are being shared at a good clip [08:05] valorie: yay :) [08:06] Riddell: did you do git branches already? === vinay is now known as Guest82909 [08:06] apachelogger: nope, what should be done? [08:06] dunno yet :P [08:06] let's dance instead https://www.youtube.com/watch?v=qXavZYeXEc0 [08:06] I wish I had yet another machine to try out installing that ISO directly [08:06] hi SourBlue, did you add that sddm.conf to kubuntu-default-settings? [08:08] Riddell: so, slashes in branch names are rejected by alioth? [08:09] Riddell: I haven't had the time to do that, if you tell me how I can do it in my break [08:14] apachelogger: yep [08:14] http://paste.ubuntu.com/8453676/ [08:14] thoughts? [08:15] could also use - actually [08:15] dashes are easier to read IMO [08:16] OTOH underscore allows us to do random nonesenese kubuntu_utopic_archive-sru1231 [08:16] apachelogger: I seem to remember reading dashes don't work great in git [08:16] apachelogger: do we really need branches for backports and updates? we don't have them at the moment [08:16] Riddell: no, but we need something that works in the future [08:16] it's just an example [08:16] gotcha [08:18] the only problem I see with this btw is that during development one branch such as kubuntu_utopic_next might get multiple merges from kubuntu_unstable which might be a hassle to implement [08:19] while with the other scheme I suggested in the mail last week that'd be no problem as we'd have a branch per upstream version, so instead of doing multiple merges we'd do multiple branches of unstable (which from a workflow perspective would probably be nicer) [08:19] we can of course always change to the version scheme at a later point if needed [08:48] my oh my [08:48] so much work [08:53] too right, what are all these failing tests on kde sc? :( [09:00] Riddell: http://paste.ubuntu.com/8453902/ [09:00] what happened to that patch? [09:01] why would that require a patch at all Oo [09:02] ah ah [09:02] I get it [09:05] Riddell: piiiiiiiiiiiiiiiing [09:05] hi apachelogger [09:05] Riddell: where did the patch go [09:05] my script says it's not in master [09:06] the kdesu one? it's at https://git.reviewboard.kde.org/r/120380/ [09:06] also... why are you landing patches without upstream review :'( [09:06] Riddell: in debian git master [09:06] it has been getting upstream review [09:06] somehow it ended up in kubuntu-unstable on launchpad [09:06] but it is not in debian git [09:07] so unless you pushed the branch to unstable directly the patch might have been lost int he git move [09:07] ah, maybe I have been not adjusting my workflow to git [09:09] kubuntu-packaging-next should have all memberse removed and be reowned to some pseudo account/group no one is in to prevent people from using it [09:10] kdesu synced [09:11] mh, now my branch will get screwed over I think [09:11] oh my ^^ [09:11] uh oh [09:14] nevermind [09:14] git will figure it out or something [09:15] assuming you imported exactly the same change anyway [09:16] anyone know why ubuntu jenkins thinks okular is failing it's autopkgtests? https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-okular/lastBuild/? [09:18] Riddell: tooling fail I'd say [09:19] * apachelogger hopes that unstable import wasn't utter rubbish [09:19] frameworks has suprisingly little delta [09:22] Riddell: had you done that patch import in bzr I'd had have a conflict now, git doesn't even care :P [09:22] that's why git one [09:22] s/one/won [09:23] go go git [09:26] btw, I think we'll want to drop .gitattributes into all repos setting dpkg-mergechangelogs as merger or something [09:26] depends a lot on how we want to do the changelog thing though I guess [09:42] oh wait [09:42] ah this is rubbish [09:42] all the branches are owned by kubuntu-packagers, so we can't put them under unaccessible ownership [09:42] meh [09:43] we could create new branches with a readme pointing out the stuff is in git now [09:43] being new branches that'd break ancenstry and prevent pushes (as long as one doesn't -f) [09:47] valorie: forwarded an e-mail to you [09:48] "LinuxFest Spokane 2015 invite from SFCC" [10:19] apachelogger: any ETA on new images? (asks the plasma meeting) [10:20] ooh you have one? [10:22] Riddell: http://kci.pangea.pub/images/kubuntu5-201409261420-x86_64.iso [10:22] haven't been able to test yet though [10:22] usb stick was a bit of an annoyance on friday [10:27] apachelogger: I don't suppose you've added a magic feature to tarme to extract FEATURE and DIGEST commits? [10:27] no [10:28] that'd be logme.rb anyway [10:28] plus that needs more details [10:28] like... how to know which tag is the one we want to considered the origin [10:36] apachelogger: command line argument? [10:36] kubuntu-ci image seems to boot up and run [10:36] no wallpaper but panel et al is fine [10:36] and I can't type anything [10:40] Riddell: typing works for me [10:44] why again a missed hangout [10:44] you know, I should like get a webcam or something xD [10:48] can you tell me how i can add something to the kubuntu-default-settings package? [10:51] apachelogger: possibly a virtualbox issue [10:51] stop testing in vbox :P [10:51] ooh hi SourBlue [10:52] SourBlue: did you work out what we want in the sddm.conf file? [10:54] HIya folks [10:58] Riddell: I think it could work to add the "MinimumVT=7" line to the sddm.conf but I'm not 100% sure I'm trying to edit the iso right now but it takes time and I'm at work right now so I only have time in my breaks [11:00] ehm [11:00] I really think sddm should be patched [11:00] on ubuntu it has no business defaulting to any VT but 7 [11:02] maybe, I'll talk to d_ed about which is best when he appears [11:03] SourBlue: do you have a launchpad account with an ssh key? if so I can take you through adding it to a package [11:04] I have a launchpad account but i need to add my ssh key [11:04] SourBlue: make it so and we can do this [11:06] hmm, interesting, sddm only defaults to vt 1 if it finds systemd http://paste.kde.org/podftr5g3 [11:07] okay done [11:07] SourBlue: URL? [11:08] of? [11:08] SourBlue: of your launchpad account! [11:08] I've no idea what your name is :) [11:09] https://launchpad.net/~denis-meiswinkel [11:10] hi Denis :) [11:10] SourBlue: ok ssh ubuntu@ec2-54-167-111-137.compute-1.amazonaws.com [11:10] then run byobu [11:16] SourBlue: ? [11:16] give me a second i made a little mistake [11:18] could you update the key i put a old one in my launchpad [11:18] ok [11:18] SourBlue: try now [11:20] Hmm i always get "Permission denied (publickey)." [11:21] SourBlue: try once more [11:21] I didn't add your newest one correctly [11:26] Nope he won't accept it [11:29] SourBlue: try ssh ubuntu@ec2-54-167-111-137.compute-1.amazonaws.com and see if it'll let you use password "foobar" [11:29] okay there we go [11:29] SourBlue: run byobu [11:29] and type something [11:30] yay [11:30] SourBlue: ok this is a shared amazon ec2 server running byobu/screen which we can both use [11:30] cloud computing for the win [11:30] oh thats strange ^^ [11:30] SourBlue: having chatted with d_ed seems our best fix would be to patch sddm [11:30] Oehh, multiplayer screen? [11:31] SourBlue: so let's do that [11:31] Allways fun to mess with ;) [11:31] SourBlue: do you already know stuff about packaging or am I best to tell you all the steps? [11:31] I know the basics [11:32] If you have the time you can tell me whats important [11:32] SourBlue: start by downloading the existing package [11:32] which is in kubuntu-ppa/next [11:32] https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/next/+packages?field.name_filter=sddm&field.status_filter=published&field.series_filter= [11:33] find the .dsc file and run dget to download it and the associated .orig and debian tars [11:35] * Riddell nudges SourBlue [11:35] done [11:35] SourBlue: noo, on the ec2 server [11:36] ah okay [11:36] sorry [11:37] SourBlue: dget the .dsc (you did that debian tar) [11:37] SourBlue: lovely [11:37] so you did that "exopr Lang=C" right? [11:38] the .dsc is a descirption of the other files in the package, and the other files are the .orig.tar. which is the upstream source and the debian.tar.gz which is the packaging bits [11:38] yes that was me [11:38] SourBlue: dpkg-source -x *dsc to extract the source package [11:39] SourBlue: cd into the sources and look around [11:39] it will have a debian/ directory with the packaging [11:39] and the upstream source code [11:39] we want to patch CMakeLists.txt [11:39] patches in our packages use a tool called quilt [11:40] SourBlue: run quilt new kubuntu_minimumvt.diff [11:40] to start off the new patch [11:41] SourBlue: now run quilt add CMakeLists.txt [11:41] to tell it we want to include that file in the patch [11:41] SourBlue: lovely, now open CMakeLists.txt in your favourite text editor [11:41] and find the line set(MINIMUM_VT 1) [11:42] change that 1 to a 7 [11:42] save and close [11:42] run quilt refresh to update the patch [11:42] and open up debian/patches/kubuntu_minimumvt.diff in a text editor [11:43] great, that patch looks like it does what we want [11:43] now we need to add headers to the patch [11:43] to document what it does [11:43] http://dep.debian.net/deps/dep3/ [11:44] I think we want "A vendor specific patch not meant for upstream submitted on the BTS by a Debian developer:" [11:44] so copy and paste the lines below that section in the dep3 document [11:44] mh [11:44] Riddell: quilt -e header --dep3 [11:45] where? [11:45] SourBlue: at the top of the patch file [11:45] above the first line [11:45] apachelogger: interesting [11:45] SourBlue: set the author to yourself [11:45] set the bug to https://bugs.launchpad.net/kubuntu-ppa/+bug/1362599 [11:45] Launchpad bug 1362599 in Kubuntu PPA "ubiquity-dm does not run on kubuntu plasma5 images" [Undecided,Fix committed] [11:45] and maybe change it to Bug-Ubuntu [11:46] Origin can be the same bug report [11:46] and give it a useful description [11:47] "ubuntu expects X to start on vt7 stop it detecting the half broken systemd which makes it start on vt1" something like that [11:47] add " Launchpad bug 1362599 in Kubuntu PPA "ubiquity-dm does not run on kubuntu plasma5 images" [Undecided,Fix committed]" to or just the ulr? [11:47] Launchpad bug 1362599 in Kubuntu PPA "ubiquity-dm does not run on kubuntu plasma5 images" [Undecided,Fix committed] https://launchpad.net/bugs/1362599 [11:47] url* [11:48] just the url is good on those lines [11:49] Is that okay? [11:49] lovely [11:49] SourBlue: save and quit [11:50] now we need to add an entry to the package changelog [11:50] run EDITOR=vi dch [11:50] (else it'll start emacs) [11:50] brrr [11:51] if you have something to say harald please let the whole class hear it [11:51] SourBlue: change the name and e-mail to you [11:51] emacs sucks! [11:52] in the comment put the name of the patch and the description again [11:52] also put LP: #1362599 to link it to the bug on launchpad [11:52] Launchpad bug 1362599 in Kubuntu PPA "ubiquity-dm does not run on kubuntu plasma5 images" [Undecided,Fix committed] https://launchpad.net/bugs/1362599 [11:53] Name? [11:53] SourBlue: filename of the patch [11:53] kubuntu_minimumvt.diff [11:53] new lintian still hates our kdeev license lines, I am beginning to think we should sed them all [11:54] like that? [11:54] SourBlue: put "Add " before the patch filename so you know what the change is [11:55] SourBlue: only 1 space needed after the * [11:55] SourBlue: lovely [11:55] save that [11:56] and now we compile it to check it's still sane [11:56] run debuild to compile [11:56] we don't change the urgency? [11:56] SourBlue: the default is fine for urgency unless it's a security update [11:57] apt install those build dependencies and run debuild again [11:58] Riddell: /usr/lib/pbuilder/pbuilder-satisfydepends-classic [11:58] or you can run that script ↑ [11:58] although it has the weird side effect of running apt autoremove for some reason [11:58] which can mess you up if you're building two things at once [11:58] Whats wrong with that? [11:59] Riddell: that's because it explicitly wants sequential builds [11:59] sometimes I'm compiling two packages at once and I've had that script remove packages the first build needs [11:59] reason being that it installs a fake package with the relevant deps [12:00] a subsequent run will then remove the fake package and call autoremove to revert to what the system was like before [12:02] Riddell: why don't you pbuilder the packages btw? [12:03] apachelogger: quicker not to, and this is a shiny new ec2 so it's a fresh environment anyway [12:03] SourBlue: woo, it compiles! [12:03] with apt-caching there's not much slowness about pbuilder other than unpacking [12:03] Riddell: the thing is, if you build two things at once it's not a fresh env anymore ;) [12:04] Is it bad if we do it unsigned? [12:04] SourBlue: ok lets build the source package with debuild -S [12:05] lovely [12:05] cd .. [12:05] oh wait [12:05] we didn't set the release, sorry [12:05] edit debian/changelog again [12:05] set UNRELEASED to utopic [12:06] debuild -S again [12:06] Riddell: dch -r [12:06] or you could have used that ↑ [12:06] so now you'll find a .changes file [12:07] looks fine, now I need to sign it [12:08] ok I've run debsign -r ec2-54-167-111-137.compute-1.amazonaws.com:sddm/sddm_0.9.0-0ubuntu1~ubuntu14.10~ppa8_source.changes [12:08] which has downloaded, signed and uploaded the files [12:08] so if you look in the .changes now it'll have PGP bits [12:08] lovely [12:08] wow thats awesome [12:09] one other check we can do to make sure we're uploading the right thing and not made any mistakes [12:09] debdiff sddm_0.9.0-0ubuntu1%7Eubuntu14.10%7Eppa7.dsc sddm_0.9.0-0ubuntu1~ubuntu14.10~ppa8.dsc [12:09] yep looks good [12:10] so now upload it to the PPA [12:10] dput ppa:kubuntu-ppa/next-staging sddm_0.9.0-0ubuntu1~ubuntu14.10~ppa8_source.changes [12:10] add a --unchecked to that [12:11] I guess add the --unchecked directly after the dput [12:11] woo, you uploaded your first package to kubuntu! [12:11] Jay! :) [12:12] SourBlue: it's compiling away now at https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/next-staging/+packages?field.name_filter=sddm&field.status_filter=published&field.series_filter= [12:12] SourBlue: and once that's done we'll copy it over from next-staging to next [12:13] and then it'll appear on the ISO when it gets amde [12:13] which is at about 22:00 in the evening in some european timezone or other [12:13] so by midnight we can check if it fixes the problem :) [12:13] That would be awesome :D [12:15] Thank you so much! [12:17] SourBlue: I'll kill the ec2 shortly, anything you want to copy off there for notes? [12:17] Nope [12:22] SourBlue: we're coming to the end of our release cycle with a release in october so less scope for randomly updating or making new packages [12:22] lots of scope for testing and bugfixes :) [12:24] Hehehe ^^ sounds great [12:24] I can't wait to see Plasma 5 when it's ready [12:26] ah but now you're an elite kubuntu ninja you get to try it before it's ready [12:27] and then work out which bugs still apply http://goo.gl/B527rj [12:31] https://i.imgur.com/PIWiVb6.gif [12:33] So if i want to help with bugs etc. where should i look? [12:39] okie, where is the ssh page for alioth [12:39] okie, where is the ssh page for alioth [12:43] shadeslayer: user profile [12:44] don't see it [12:45] alioth is annoying [12:45] shadeslayer: https://alioth.debian.org/account/editsshkeys.php [12:45] I think u need nu glasses [12:46] no seriously, searched for ssh [12:46] nothing [12:46] https://alioth.debian.org/account/ [12:47] bottom of the page [12:47] Shell Account Information [12:47] search for shell -> nothing [12:47] stop using firefox [12:48] :O [12:48] nothing in chromium as well [12:48] works in chrome [12:49] or maybe you just dont know how to search [12:49] maybe you type into address bar [12:49] apachelogger: http://i.imgur.com/7EMiuxM.png [12:50] shadeslayer: you been accepted into pkg-kde group? [12:50] not yet [12:50] ... === rdieter_ is now known as rdieter [12:51] apachelogger: but I can access https://alioth.debian.org/account/editsshkeys.php [12:51] I suppose it is hidden from the mainpage because it made no sense [12:52] unless you are in a group you won't have access to anything anyway, so the key makes no sense one would argue [12:52] * apachelogger finds that a bit silly [12:55] Riddell: now the question is, who is going to port the kubuntu-automation stuff to git [12:55] aaaalso, how do we want to handle branchery for the time being? have automation branch unstable into kubuntu_utopic_next or do it in a separate script? [12:55] not that it made much difference [13:02] apachelogger: what needs ported to git? all the bzr branches? [13:02] SourBlue: check out the links on http://qa.kubuntu.co.uk/ [13:02] Utopic milestoned bugs and kubuntu-ppa/next Plasma 5 bugs have lots of bugs [13:03] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=kubuntu-packaging has packages needing done [13:03] SourBlue: you could for example look at packaging grantlee which has new versions in both kdelibs4 and kf5 land [13:04] Riddell: assuming it does bzr co and bzr builddep etc. all that needs property [13:05] also I think someone needs to figure out gbp, every time I used it I ended up defining 500 arguments to make it do what the right thing ^^ [13:06] apachelogger: I was expecting to port the scripts as I need them, starting with kubuntu-initial-upload when plasma 5.1 beta is buildable [13:06] which is when these kf5 packages get through launchpad [13:09] Riddell: fine by me as long as I don't have to do it :P [13:09] you'll want to write additional logic though [13:10] apachelogger: what additional logic? [13:10] you'll want to branch kubuntu_unstable [13:10] so git clone; git pull; git checkout kubuntu_unstable; git checkout -b kubuntu_utopic_next; [13:11] and for the next release that'll need more adjustment as it needs to merge unstable into next [13:11] shouldn't be too much of a bother though as next by then will be continously merged back into unstable (or such was the plan anwyay) [13:12] so there wouldn't be merge conflicts or anything [13:12] actually that raises a question ... should unstable track git master or Plasma/5.1 [13:12] :S [13:14] or we could setup kubuntu_5.1 which tracks that branch and setup secondary CI builds for that, seems like a bit of a resource waste though [13:14] * apachelogger gets a headache [13:20] Riddell: So if I wanted to package this one https://bugs.launchpad.net/ubuntu/+bug/1372471 what do I have to do? [13:20] Launchpad bug 1372471 in Ubuntu "[needs-packaging] kdev-python-py3" [Wishlist,New] [13:21] SourBlue: take a look at the current kdev-python package [13:21] it'll need ported to python3 for the kdev-python-py3 one [13:22] python packaging is a bit of an art in itself, fortunately ScottK is an expert there :) [13:22] ah okay ^^ [13:22] So i would download the source to my own machine (apt source *name*) [13:23] apachelogger: so unstable is the kubuntu-ci packaging? how does this fit in with us only having a master branch so far? [13:24] Riddell: we don't we now have kubuntu_unstable :P [13:24] Riddell: hi, now after one week I looked at my ppa and launchpad compiled new kde4 packages for precise... but some needs fixing (reupload) but repo size is 100% [13:24] is there way to increase size of ppa? [13:24] launchpad refused to upload new packages [13:24] Pali: you need to file a question on it I think [13:25] https://help.launchpad.net/Packaging/PPA "Size and transfer limits" [13:25] kubuntu_unstable derives from master, our releases (kubuntu_utopic_*) ultimately derive from master, master probably will want to merge whatever stuff we have in some release (kubuntu_utopic_*) at some point and rewrite the changelog [13:26] but that's debian's problem :) [13:27] so following the assumption that master <= kubuntu_*_* && kubuntu_*_* <= kubuntu_unstable, unstable can always merge from everything and fixes as such should be done in master (if applicable) then foward merged to all kubuntu_*_* (as applicable) and then this gets forward merged into kubuntu_unstable (possibly automatic) [13:28] ok, I send question to that launchpad tracker [13:28] all of this kinda depends on debian figuring out how they want to use master [13:28] how long it will take? [13:29] on our side it doesn't really matter where we put unstable in terms of merge order as ideally I'd like all branches to somehow merge up with unstable automatically [13:29] Pali: I'm not sure, sending chocolate to wgrant may make it faster [13:29] :-) [13:29] so in the long run you could make a SRU for 14.04 and our automation would propagate the fix to all our branches >=14.04 and then possibly even spins test builds off of that [13:30] that's a long way to go though, also possibly a tad too much automation ^^ [13:47] Chocolate or pings, either way. [13:51] ^^ [13:53] thanks! :-) [13:54] aww volkan gezer left kubuntu-devel mailing list [13:54] SourBlue: have you joined the kubuntu-devel mailing list? also needed to be an elite kubuntu ninja [13:56] I think i did [13:57] great [13:58] You see if someone left the list? [13:58] yes list admins gets a notification [13:59] worse than the NSA [14:00] Maybe he is from the NSA who knows.. [14:00] Maybe i am.. [14:00] checking out us communist freedom fighters [14:02] ah ah ah [14:02] https://www.youtube.com/watch?v=VEy5vIWCJLQ [14:04] lol what [14:06] monty python reference, that's what ;) [14:06] * SourBlue loves 100% Protection! [14:13] sourblue to testers, roger roger [14:30] apachelogger: git-buildpackage wasn't used so far debian's kde sc packages. one thing is having something on git, but that doesn't mean it's compatible with git-buildpackage. when I was starting I was tricked by that [14:31] the workflow was explained in qt4-x11 README.source if I recall correctly [14:38] http://ubottu.com/factoids.cgi?search=sourblue [14:39] what to name the sddm-kcm package? currently it's kde-config-sddm but I wonder if it should be sddm-kcm [14:43] Riddell: policy is kde-config-foo [14:45] there is a policy for that? [14:46] Ubottu what does that mean? [14:46] I am only a bot, please don't think I'm intelligent :) [14:46] Riddell: debian [14:46] there was a mail thread about it some years back [14:47] which is where the kde-config- thing comes from [14:47] well remembered [14:49] Do you know a way to see if a package is installed or not that gives a response like 0 or 1 so my script can use it? [14:49] like if package is installed do this if not do something else [14:50] dpkg -s [14:55] Hmm looks like it could work but it won't do what i want i need something like this: http://pastebin.com/7KmsX8YF [15:00] have to go see you soon [15:04] SourBlue: if dpkg -s vlc &> /dev/null; then echo "installed"; else "not installed"; fi [15:19] sddm-kcm in next-staging [15:36] http://pastebin.com/7KmsX8YF does someone have a clue how I can make this work? [15:41]