[00:04] -kubuntu-ci:#kubuntu-devel- Project merger_print-manager build #760: FAILURE in 1 min 26 sec: http://kci.pangea.pub/job/merger_print-manager/760/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #738: UNSTABLE in 7 min 8 sec: http://kci.pangea.pub/job/mgmt_merger/738/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #723: UNSTABLE in 7 min 11 sec: http://kci.pangea.pub/job/mgmt_progenitor/723/
[00:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_breeze-plymouth build #35: FAILURE in 9 min 14 sec: http://kci.pangea.pub/job/zesty_unstable_breeze-plymouth/35/
[00:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kigo build #34: FAILURE in 10 min: http://kci.pangea.pub/job/zesty_unstable_kigo/34/
[00:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #16: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/16/
[00:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kspaceduel build #35: FAILURE in 9 min 14 sec: http://kci.pangea.pub/job/zesty_unstable_kspaceduel/35/
[00:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmag build #36: FAILURE in 9 min 14 sec: http://kci.pangea.pub/job/zesty_unstable_kmag/36/
[00:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_analitza build #33: FAILURE in 10 min: http://kci.pangea.pub/job/zesty_unstable_analitza/33/
[00:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kfind build #6: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kfind/6/
[00:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #11: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_peruse/11/
[00:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kfind build #12: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/zesty_unstable_kfind/12/
[00:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkipi build #99: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_libkipi/99/
[00:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #66: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/66/
[00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #19: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/19/
[00:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kigo build #35: FIXED in 18 min: http://kci.pangea.pub/job/zesty_unstable_kigo/35/
[00:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmag build #37: FIXED in 18 min: http://kci.pangea.pub/job/zesty_unstable_kmag/37/
[00:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdesdk-kioslaves build #36: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_kdesdk-kioslaves/36/
[00:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-runtime build #73: STILL FAILING in 42 min: http://kci.pangea.pub/job/zesty_unstable_kde-runtime/73/
[00:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #296: STILL FAILING in 40 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/296/
[00:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kspaceduel build #36: FIXED in 25 min: http://kci.pangea.pub/job/zesty_unstable_kspaceduel/36/
[00:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #121: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/xenial_unstable_kopete/121/
[00:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #289: STILL FAILING in 38 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/289/
[00:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #22: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/zesty_unstable_kopete/22/
[00:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #97: STILL UNSTABLE in 47 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/97/
[01:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemmodels build #332: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kitemmodels/332/
[01:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-runtime build #74: STILL FAILING in 23 min: http://kci.pangea.pub/job/zesty_unstable_kde-runtime/74/
[01:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #297: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/297/
[01:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #290: STILL FAILING in 23 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/290/
[01:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #17: STILL FAILING in 29 min: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/17/
[01:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #133: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/133/
[01:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #21: STILL UNSTABLE in 1 hr 38 min: http://kci.pangea.pub/job/zesty_unstable_krita/21/
[02:25] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_breeze-plymouth build #36: FIXED in 12 min: http://kci.pangea.pub/job/zesty_unstable_breeze-plymouth/36/
[02:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_analitza build #34: FIXED in 19 min: http://kci.pangea.pub/job/zesty_unstable_analitza/34/
[02:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #36: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/36/
[03:13] <wxl> tsimonq2: ever got ot the seccomp -17 error with a lxc?
 O__o
[03:16] <wxl> http://paste.ubuntu.com/23546801/
 After running what command?!?
[03:17] <wxl> lxc-start -n somecontainername -F
 o
 m
 g
 NO
 wrong
 man lxc
[03:17] <wxl> originally -d but it gives you some generic message and says to use F
[03:18] <wxl> https://help.ubuntu.com/lts/serverguide/lxc.html
[03:18] <wxl> so sorry, you're wrong
 Nuh uh
[03:19] <wxl> then you tell me how to start the container
 rtfm: https://www.stgraber.org/2016/03/11/lxd-2-0-introduction-to-lxd-112/
[03:19] <wxl> that's not the manual
 We'll you are doing 1.0 commands
 I'm doing 2.0 commands
[03:20] <wxl> lxd is an extension of lxc
[03:20] <wxl> i doubt it will make a bit of difference
 But he uses commands with just LXC on them
 Some of them
[03:22] <DarinMiller_> wxl: are you running an LXD container in lieu of sbuild?
[03:22] <wxl> DarinMiller_: well, lxc, as a diagnosing method. but tsimonq2 is whining that it doesn't count and i have to use lxd.
[03:27] <DarinMiller_> Isn't lxc essentially a vm on steroids with small footprints for mulitple instances?  How does one use it for packaging?  :P
[03:34] <wxl> DarinMiller_: you done a merge fix yet?
[03:34] <DarinMiller_> only assisted.
[03:35] <wxl> there's a new one up on print manager
 Now do it on your own and call for help when needed. XD
 Wait
 :/
[03:36] <DarinMiller_> I was trying to play with audiocd-kio and wanted to compile it in an sbuild enviro so I could play with it.  But I never suceeded with sbuild.
[03:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:36] -kubuntu-ci:#kubuntu-devel- Project merger_print-manager build #761: FIXED in 18 sec: http://kci.pangea.pub/job/merger_print-manager/761/
[03:36] <wxl> where did you get hung up at?
[03:36] <DarinMiller_> There fixed.
 Nevermind wxl
 Internal error solved by a rebuild
[03:36] <wxl> bah
[03:37] <wxl> no fun at all
[03:37] <DarinMiller_> :)
[03:37] <wxl> where do we have the order of merges documented?
 Nowhere
 NOTHING KCI related is documented
 Well not true, a few tiny things
[03:38] <wxl> not true
 But still, very very little docs
[03:38] <wxl> the packaging documentation has a fair amount
[03:39] <wxl> ok so what's the order again?
[03:39] <DarinMiller_> when I run: sbuild -d zesty-amd64-shm
[03:40] <wxl> i know it's stable -> unstable
[03:40] <wxl> but there was another step
[03:40] <DarinMiller_> i get: dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream tarball found at
[03:40] <wxl> DarinMiller_: oh! change your nick to the right one and you'll see my note about that
[03:41] <wxl> btw i can see your ip :)
[03:41] <DarinMiller_> ohhhh
[03:42] <DarinMiller_> you can see my ip?
 YES WE CAN
 Sorry, being Obama. :P
[03:43] <DarinMiller_> How do I fix that?
[03:44] <wxl> DarinMiller_: identify yourself to nickserv
 (Document) https://irc-attachments.kde.org/cSyqyOzI/file_1251.mp4
[03:46] <wxl> tsimonq2: see "Language and Subject" here https://wiki.ubuntu.com/IRC/Guidelines
[03:46] <wxl> tsimonq2: what's the merge order?
 r t f m :)
[03:48] <wxl> god dude you got a real problem
 You do this to me. :)
[03:49] <wxl> i'm asking you for help because, as you said, it's not documented
[03:49] <DarinMiller> is my ip still showing? The freenode message says I am identified as DarinMiller...
[03:49] <wxl> DarinMiller: still is. you need a cloak
[03:49] <wxl> DarinMiller: are you a kubuntu member and/or an ubuntu member?
[03:50] <DarinMiller> wxl: yes
[03:50] <wxl> oops sorry for the message
[03:50] <wxl> which?
 archive | backports -> stable | unstable (zesty)
[03:51] <wxl> | meaning or?
 merge into
 pipe into
[03:51] <wxl> then what's the arrows?
[03:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #137: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/137/
 So archive is merged into backports which is merged into stable which is merged into unstable
[03:52] <wxl> DarinMiller: head over to #freenode and ask them for help getting an unaffiliated cloak
[03:53] <DarinMiller> ok
[03:54] <wxl> tsimonq2: i remember taking three steps when i was doing merges. but you're showing four
[03:55] <DarinMiller> how are you able to see my ip?
[03:56] <wxl> DarinMiller: do a whois on yourself. you'll see that this shows a format username@hostname
[03:56] <wxl> DarinMiller: if you look at most of us here, you'll see something very different-- with slashes in it
[04:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_frameworkintegration build #177: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_frameworkintegration/177/
[04:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #304: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_kstars/304/
[04:06] <wxl> tsimonq2: i remember taking three steps when i was doing merges. but you're showing four
[04:07] <tsimonq2> wxl: Oh sorry. Yeah, I must have initially taught you wrong then. Sorries.
[04:07] <wxl> tsimonq2: and what does the arrow signify?
[04:11] <wxl> tsimonq2: is the arrow the same as a pipe?
[04:11] <tsimonq2> wxl: Yes
[04:12] <wxl> tsimonq2: so
[04:12] <wxl> 1. git clone
[04:12] <wxl> 2. git checkout kubuntu_archive
[04:12] <wxl> 3. git checkout kubuntu_backports
[04:12] <wxl> 4. git merge
[04:12] <wxl> etc.?
[04:12] <tsimonq2> Yes :)
[04:13] <wxl> great
[04:16] <wxl> https://notes.kde.org/p/kubuntu-packaging
[04:16] <wxl> check out the merge fix thing at the bottom
[04:16] <wxl> tweak as needed
[04:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #230: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/230/
[04:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #242: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kio-extras/242/
[04:27] <DarinMiller> lots of chatter on #freenode, but nobody wants grant me an unaffiliated cloak.  I will request again tomorrow...
[04:27] <tsimonq2> DarinMiller: wait
[04:27] <DarinMiller> OK
[04:28] <tsimonq2> DarinMiller: Aha! No staff online!
[04:28] <wxl> there's staff online
[04:28] <tsimonq2> wxl: ...no?
[04:28] <wxl>  /who freenode/staff/*
[04:28] <tsimonq2>  /stats p
[04:28] <wxl> the "H" means "here"
[04:28] <DarinMiller>  /stats p
[04:28] <tsimonq2> DarinMiller: PM one. :)
[04:29] <wxl> hold on
[04:29] <wxl> i'm working on one right now
[04:29] <tsimonq2> wxl: No? Try it with the Ubuntu members list.
[04:30] <DarinMiller> wxl: you working with a freenode staffer or obtaining an unaffiliated cloak?
[04:30] <wxl> DarinMiller: message nhandler and he'll get you one
[04:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #216: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/216/
[04:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #218: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/218/
[04:35] <wxl> welcome to the club DarinMiller :)
[04:37] <DarinMiller> I can still see my IP as /whois broadcasts my connection location. Is that only broadcast to me, or can you see it also.
[04:37] <DarinMiller> ?
[04:37] <wxl> only you
[04:38] <wxl> DarinMiller: you know how to automatically identify with nickserv when you connect to irc?
[04:38] <DarinMiller> Yes?
[04:38] <wxl> are you sure? :)
[04:38] <DarinMiller> No :)
[04:39] <wxl> https://docs.kde.org/trunk5/en/extragear-network/konversation/serverlist.html
[04:39] <wxl> 2nd pic there
[04:39] <wxl> #3
[04:39] <wxl> well #2 and #3
[04:39] <wxl> add DarinMiller to your identity on #2
[04:39] <wxl> then add /msg nickserv identify YOUR-PASSWORD to #3
[04:40] <wxl> also you can get encrypted connections on port 7000
[04:40] <wxl> see the 4th pic for info on that
[04:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #171: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/171/
[04:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #122: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/122/
[04:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #230: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_cantor/230/
[04:43] <DarinMiller> I assume a secure connection is to protect private message content as all of the channels I visit are public.
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #62: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/62/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #265: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/265/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_print-manager build #205: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_print-manager/205/
[04:49] <wxl> DarinMiller: well, it secures everything.
[04:49] <wxl> s/secures/encrypts/
[04:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #172: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/172/
[04:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #45: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/45/
[05:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #54: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/xenial_unstable_marble/54/
[05:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #195: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/195/
[05:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #65: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kwin/65/
[05:21] <DarinMiller> wxl: OK, security setup as instructed.  Thanks for the tips.
[05:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khelpcenter build #95: FAILURE in 2 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_khelpcenter/95/
[05:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_bomber build #132: FAILURE in 2 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_bomber/132/
[05:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kholidays build #101: FAILURE in 2 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kholidays/101/
[05:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_knavalbattle build #82: FAILURE in 2 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_knavalbattle/82/
[05:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kidentitymanagement build #87: FAILURE in 2 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kidentitymanagement/87/
[05:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #216: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/216/
[05:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #196: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/196/
[05:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kholidays build #102: FIXED in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kholidays/102/
[05:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_bomber build #133: FIXED in 11 min: http://kci.pangea.pub/job/yakkety_unstable_bomber/133/
[05:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_knavalbattle build #83: FIXED in 12 min: http://kci.pangea.pub/job/yakkety_unstable_knavalbattle/83/
[05:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kidentitymanagement build #88: FIXED in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kidentitymanagement/88/
[05:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khelpcenter build #96: FIXED in 12 min: http://kci.pangea.pub/job/yakkety_unstable_khelpcenter/96/
[05:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio-extras build #105: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kio-extras/105/
[05:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #69: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/69/
[05:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #125: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/125/
[05:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #33: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_kstars/33/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #155: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/155/
[05:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #33: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/33/
[06:04] <aniketh_> Ping
[06:05] <aniketh_> Kunbuntu packager who does not package log.h in the dev package inside /usr/include/KF5/KScreen/kscreen
[06:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #57: STILL FAILING in 32 min: http://kci.pangea.pub/job/yakkety_unstable_marble/57/
[06:06] <aniketh_> I have the fix need to patch
[06:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcompactdisc build #27: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/zesty_unstable_libkcompactdisc/27/
[06:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-extras build #25: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kio-extras/25/
[06:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #24: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/24/
[06:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #29: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_cantor/29/
[06:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #21: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/21/
[06:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #43: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/43/
[06:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #120: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/120/
[06:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #30: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/30/
[06:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_print-manager build #20: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_print-manager/20/
[06:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #25: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/25/
[06:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-nm build #31: UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_plasma-nm/31/
[06:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #22: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/22/
[06:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #58: STILL FAILING in 29 min: http://kci.pangea.pub/job/yakkety_unstable_marble/58/
[06:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-integration build #31: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_plasma-integration/31/
[06:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #40: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_marble/40/
[06:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwin build #40: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/zesty_unstable_kwin/40/
[07:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #67: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/67/
[07:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #33: UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/33/
[07:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #68: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/68/
[07:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #22: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/22/
[08:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #36: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/36/
[08:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #48: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/48/
[13:01] <acheronuk> aniketh_: the new log class was not introduced until plasma 5.8, so in 5.7 there is nothing to package
[13:04] <acheronuk> in plasma 5.8's libkf5screen-dev it is present
[13:27] <BluesKaj> Hiyas all
[14:39] <santa_> good afternoon
[14:41] <santa_> acheronuk, tsimonq2: if we don't have a sponsor yet, I would like to stage frameworks and plasma new versions tonight
[14:41] <santa_> also wxl ↑
[14:43] <acheronuk> santa_: oddly enough, I was just considering doing a test staging of plasma 5.8.4 in my ppas
[14:43] <acheronuk> so doing it for real is even better
[14:45] <santa_> ok, so whoever is available @ ~ 22:00 UTC please show up s we can split the work
[14:45] <santa_> * so we can split the work
[15:28] <aniketh_> acheronuk: Oh ! So doesn't older version need log class ?
[15:32] <acheronuk> aniketh_: well, the KDE developers either didn't think so or that it wasn't worth backporting the addition of it to the plasma 5.7 branch.
[15:32] <acheronuk> if you want to ask them, try in #plasma
[18:14] <wxl> hey kids
 Hai wxl
[18:14] <wxl> tsimonq2: you still at skewl?
 Yes siree
 But lunch now
 So I have the next hour free
[18:15] <acheronuk> evening :)
[18:23] <wxl> tsimonq2: so whatcha working on?
[18:23] <wxl> acheronuk: we're meeting at 2200?
[18:23] <acheronuk> looks like it
[18:23] <wxl> what's the work needs like?
[18:24] <acheronuk> ?
[18:25] <wxl> um
[18:25] <wxl> what do we intend to do?
[18:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #73: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/73/
[18:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #74: NOW UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/74/
[18:27] <acheronuk> santa_ wants to stage frameworks 5.28 and plasma 5.8.4
[18:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #21: NOW UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/21/
 wxl: Food omnomnom
[18:31] <wxl> i've never helped with staging before
[18:31]  * wxl reads docs
[18:31] <IrcsomeBot1> * tsimonq2 giggles
 We have docs?
[18:35] <acheronuk> the readme.ng?
[18:35] <wxl> doesn't https://notes.kde.org/p/kubuntu-packaging
 I think we should start discussing having an alternate Wayland Kubuntu session ship with 17.04.
[18:37] <acheronuk> wxl: those are now a bit out of date for staging
[18:38] <blaze> alternate session will come with plasma 5.9
[18:38] <blaze> no need to bother
[18:39] <wxl> well some docs would be nice
[18:39] <wxl> is the readme.ng sufficient?
[18:43] <acheronuk> well, the notes.kde.org doc is good background as well
[18:43] <wxl> background is probably sufficient preparation
[18:43] <wxl> as long as you and santa_ can help us fill in the gaps
[18:43] <acheronuk> just that from "Execute the script...." to "git-push-all" parts are redundant should you be using the new tooling
[18:44] <wxl> then we can try modify the docs as we go
[18:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #74: FIXED in 12 min: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/74/
[18:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #75: FIXED in 13 min: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/75/
[18:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #22: FIXED in 13 min: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/22/
[18:51] <wxl> acheronuk: in README.ng, it's section 3 that's relevant?
[18:52] <acheronuk> I hope so!
[19:02] <santa_> wxl: we are going to follow what's in README.ng, the wiki pages are outdated, but we will update them later
[19:03] <wxl> santa_: in section 3?
[19:03] <santa_> and everything else
[19:04] <santa_> wxl: are you available @ 22:00 utc ?
[19:06] <santa_> acheronuk: btw I pushed to master a mockup of the new KA config handling, have you seen it?
[19:07] <santa_> (we are not going to use that today but I hope to get it ready for the next round of stagings)
[19:12] <acheronuk> santa_: so a unified config, rather than having it all spread out in hard to remember places?
[19:13] <santa_> acheronuk: yes, and the fact that you may have a user config now
[19:14] <santa_> because right now both you and Simon are changing the upload-area dir and there's no other way but changing the thing in the KA clone
[19:15] <santa_> I'm also setting my stuff sometimes and it's really inconvenient because it might trigger accidents with 'git commit -a'
[19:24] <wxl> santa_: should be yes
[19:25] <acheronuk> santa_: just doing a dry run, and get this oddity +kpackage
[19:25] <acheronuk> http://paste.ubuntu.com/23549885/
[19:26] <acheronuk> that gets added even though it's already there
[19:28] <santa_> acheronuk: because there is both 5.28.0 and 5.28.1
[19:29] <santa_> acheronuk: thank you for pointing it out, I guess I can rush the rewrite of the script involved in that because its current code is bad
[19:29] <santa_> i.e. hardcoded package names in the script
[19:39] <acheronuk> santa_: also getting some weirdness with do-all http://paste.ubuntu.com/23549944/
[19:44] <santa_> acheronuk: "do-all do-all gbp-newrelease" ?
[19:45] <acheronuk> doh!
[19:45]  * acheronuk walks off ashamed
[19:51] <ahoneybun> o/
[19:51] <wxl> morn ahoneybun
[19:51] <ahoneybun> afternoon wxl
[19:53] <santa_> hi
[19:53] <ahoneybun> hey santa_
[20:14] <acheronuk> santa_: looks like 5 packages will fail with patch issues http://paste.ubuntu.com/23550093/
[20:30] <santa_> acheronuk: ok we will have a look later, I need a break
[20:30] <santa_> I will be back
[20:43] <ahoneybun> https://www.reddit.com/r/kde/duplicates/5eyj7l/which_kde_distros_do_you_use/
[20:46] <acheronuk> santa_: the changelogs are also a bit messed up e.g. http://paste.ubuntu.com/23550212/
[20:47] <acheronuk> not getting a new entry as the previous is still unreleased. probably not a big deal
[20:48] <acheronuk> and a "New upstream release (5.28.0)" is not getting added
[20:52] <acheronuk> solid: patch needs updating
[20:52] <acheronuk> breeze-icons: patch needs removing as applied upstream
[20:53] <acheronuk> kcoreaddons: patches needs removing as applied upstream
[20:54] <acheronuk> knotifications: 3 patches needs removing as applied upstream
[21:00] <blaze> why patching something which is not pushed into archives yet?
[21:00] <acheronuk> kio: kubuntu_failing-tests.diff needs a refresh
[21:32] <acheronuk> santa_: same for plasma. no "New upstream release (5.8.4)" entry created
[21:42] <acheronuk> gbp-nr fails on discover with
[21:42] <acheronuk> do-all current directory: discover/git/ (16 of 39)
[21:42] <acheronuk> ----------------------------------------------------------------------
[21:42] <acheronuk> calling: /home/neo/kubuntu/kubuntu-automation/gbp-plugins/scripts/new-release -d zesty
[21:42] <acheronuk> new-release doesn't support non frameworks/Plasma/Apps packages
[21:42] <acheronuk> ----------------------------------------------------------------------
[21:43] <acheronuk> ahoneybun: yes, I saw that :/
 The poll?
[21:43] <acheronuk> yep
 What's wrong with it?
[21:45] <acheronuk> nothing is wrong. I just don't think reddit is a very representative demographic
 Well yea
[22:27] <santa_> acheronuk: fixed in master the 3 issues you pointed out, do you mind to retry your dry run to confirm they are actully fixed?
[22:28] <santa_> * actually
[22:32] <acheronuk> just grabbing a fresh clone of plasma
[22:33] <wxl> ya'll need help or what?
[22:34] <valorie> !alis
[22:34] <valorie> :-)
[22:34] <acheronuk> wxl let me just chack this then we can probably go through this all together from scratch
[22:34] <acheronuk> *check
[22:34] <wxl> acheronuk: k ping me when you're ready
[22:38] <acheronuk> santa_: still not adding the "New upstream release (5.8.4)" in the changelog
[22:39] <acheronuk> oh wait. forget that
[22:44] <acheronuk> looks bettr I think
[22:49] <acheronuk> still fails on discover
[22:51] <acheronuk> can do that manually I think
[22:54] <acheronuk> Darin about?
[22:55] <santa_> acheronuk: ok, I'm doing my dry-runs here too
[23:03] <acheronuk>  ok. where to do this?
[23:05] <santa_> acheronuk: this what? the staging of frameworks and plasma?
[23:05] <acheronuk> yep. well that will have to be done on linode, but I meant the chat
[23:07] <santa_> aha
[23:08] <santa_> well, you can pick either frameworks or plasma
[23:08] <santa_> and I will do the other
[23:08] <santa_> if you need help with the one you pick I could get into your container and see what's wrong
[23:09] <wxl> well i'm here to help but don't have a bloody clue what to do or what you need
[23:11] <santa_> you will
[23:12] <acheronuk> santa_: ah. I must have misunderstood. thought we were going to go through both with wxl
[23:12] <santa_> hmm, not yet
[23:12] <santa_> but I want him to watch what you do on the linode
[23:13] <wxl> yeah that's good
[23:13] <santa_> acheronuk: so can you add his keys to your container?
[23:14] <acheronuk> shall I do plasma then? as that should be a bit simpler?
[23:15] <santa_> ok, I will pick frameworks then
[23:15] <acheronuk> santa_: if you do frameworks, solid patch will need these 2 changes
[23:15] <acheronuk> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/solid/log/?h=kubuntu_unstable
[23:15] <acheronuk> I think anyway.....
[23:16] <acheronuk> wxl: they key on your LP page?
[23:16] <acheronuk> *the
[23:16] <wxl> acheronuk: yeah, the rocky one
[23:16] <santa_> well, we must get that merging th kubuntu_unstable branch
[23:17] <acheronuk> yep
[23:19] <acheronuk> wxl: ssh dev.kubuntu.co.uk on port 2203
[23:19] <acheronuk> wxl: chat here or on BBB?
[23:21] <wxl> acheronuk: ugh 2203 is blocked here at work
[23:21] <acheronuk> oh
[23:22] <acheronuk> ummm
[23:22] <wxl> yeah
[23:22] <wxl> well
[23:23] <acheronuk> wxl: well, I did a dry run here with the tooling. basically did everything apart from push to git and upload. when you get off work, maybe Simon could take you through that on his container
[23:24] <wxl> acheronuk: yeah c'est la vie.
[23:25] <acheronuk> annoying. sorry
[23:28] <acheronuk> santa_: pushing changes to KA. want to do yours first, then I pull those and do mine?
[23:29] <santa_> acheronuk: well I should do mine first since I'm doing frameworks
[23:30] <acheronuk> ok. tell me when you are all done
[23:30] <santa_> I'm doing a dry-run of fw after merging kubbuntu_unstable, if everything goes fine I will do it for real
[23:31] <santa_> 33/73
[23:37] -kubuntu-ci:#kubuntu-devel- Starting build #7 for job mgmt_pause_integration (previous build: ABORTED)


[15:17] <coconut> someone can kick archivist out of #ubuntu?
[15:20] <coconut> ?
[15:23] <coconut> oh... he left


[03:05] <jbicha> hi! on https://launchpad.net/ubuntu/quantal/+queue?queue_state=1 why is the diff stored at http://lplibrarian-private-download.internal:8000/110291526/haskell-aeson_<IP_ADDRESS>-1_<IP_ADDRESS>-1build1.diff.gz
[03:38] <micahg> jbicha: looks like a bug
[03:39] <micahg> lifeless: ^^^
[03:41] <lifeless> indeed thats a bug
[03:41] <lifeless> please file it
[03:41] <lifeless> cjwatson will need to know about it
[03:44] <jbicha> it's affecting other stuff too, https://launchpad.net/ubuntu/+source/mutter/3.5.4-0ubuntu1
[03:52] <stgraber> it's not affecting all the diff links and the relation between these that are affected isn't obvious (not time based and nothing obvious in the .changes that I could see)
[03:52] <jbicha> are there recent uploads that have normal diffs?
[03:53] <stgraber> fairly recent yeah
[03:53] <stgraber> I spotted a couple to quantal 4 hours ago that were fine
[03:54] <stgraber> https://launchpad.net/ubuntu/quantal/+queue?queue_state=3&queue_text=&memo=120&start=120
[03:54] <stgraber> lists gnome-orca with an invalid link, but gjs and libsoup2.4 are fine
[03:54] <jbicha> anyway, bug 1025515
[03:54] <stgraber> kde-runtime too, but if you go to the next page, you have some more that are pointing to the internal server
[04:21] <wgrant> jbicha, lifeless, micahg: cjwatson's already fixed that, but existing uploads haven't been repaired.
[04:21] <wgrant> It affects sources that were originally uploaded to a private PPA.
[04:21] <micahg> wgrant: would've pinged you, but I thought you were on vacation :)
[04:22] <micahg> wgrant: the quantal queue doesn't include stuff uploaded to private PPAs :)
[04:23] <wgrant> Ahhh
[04:23] <wgrant>     @property
[04:23] <wgrant>     def private(self):
[04:23] <wgrant>         """See `IPackageDiff`."""
[04:23] <wgrant>         return all(
[04:23] <wgrant>             archive.private for archive in self.to_source.published_archives)
[04:23] <wgrant> So if it's not published in any archives at all, it'll end up private :/
[04:23] <micahg> heh, I had a sneaky suspicion about that part
[04:25] <lifeless> wgrant: what what, we store a static url? what about TLT ?
[04:26] <wgrant> lifeless: We store an LFA reference.
[04:26] <wgrant> lifeless: Private archives know how to do the TLT redirection dance
[04:27] <wgrant> Public archives and +queue do not, deliberately.
[04:27] <lifeless> wgrant: lplibrarian-private-download.internal isn't a TLT base url *either*
[04:27] <wgrant> lifeless: No, it's the http_url
[04:27] <lifeless> ahhhhg
[04:27] <wgrant> Which things will use unless they're getting TLTs
[04:27] <wgrant> using getURL
[04:27] <lifeless> we should just nuke that for private entirely.
[04:28] <wgrant> Er
[04:28] <wgrant> No
[04:28] <lifeless> yeah :)
[04:28] <wgrant> It's how internal downloads work :)
[04:28] <lifeless> doesn't have to be.
[04:28] <wgrant> You want to issue a bazillion TLTs for every file just so we can access them internally?
[04:28] <wgrant> Seems unwise.
[04:28] <wgrant> At least until we know it scales
[04:28] <wgrant> Which we don't...
[04:28] <lifeless> its about as much IO as needed to write a log entry
[04:28] <lifeless> we know that we can do that already.
[04:29] <lifeless> Internal downloads of public things should use the public url
[04:29] <wgrant> Well, recall that we already have some unidentified load issue with TLTs in the librarian server.
[04:29] <lifeless> internal downloads of private things should use a private url, TLTs provide one.
[04:29] <lifeless> yes, should fix that first.
[04:29] <lifeless> Wasn't aware that it was load correlated.
[13:24] <iwata0303> Hallo, folks.
[13:25] <iwata0303> Now, I get "Not a branch" error when trying to access to some branches on Launchpad.
[13:26] <mgz> iwata0303: has the branch been deleted or moved?
[13:26] <Lasall> how do you branch?
[13:26] <iwata0303> e.g. lp:tortoisebzr, lp:qbzr. They cirtainly exist.
[13:26] <mgz> ah, okay, they do exist :)
[13:26] <iwata0303> Has something changed ?
[13:26] <mgz> $ bzr branch lp:qbzr
[13:26] <mgz> bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/+branch/qbzr/".
[13:26] <mgz> ...and that is a bit worrying
[13:28] <mgz> $ bzr branch lp:~qbzr-dev/qbzr/trunk2a
[13:28] <mgz> Branched 1494 revisions.
[13:28] <mgz> so, the mapping is borked.
[13:31] <iwata0303> Can I do something to fix it ?
[13:32] <mgz> iwata0303: problem seems to be launchpad's end
[13:32] <mgz> there are a few recent changes to branch stacking for the privacy work, but nothing jumps out at me as being to blame
[13:34] <mgz> iwata0303: for a workaround if you need to update your copies locally, you can find out the real location from the web page and pull from that
[13:38] <iwata0303> The workaround is okay for my personal work, but this problem may block next bzr windows installer release.
[13:39] <mgz> iwata0303: don't make me cry more ;_;
[13:39] <mgz> (I think that should be fine, as I can always manually change the locations to pull from when building the installer)
[13:40] <mgz> but this is clearly a regression in launchpad that needs fixing
[13:45] <iwata0303> mgz: I see. Thank you for your advice :)
[13:45] <mgz> thanks for reporting the problem :)
[13:58] <dobey> how does one remove a team from subscription to bugs for a specific package in ubuntu these days?
[14:01] <mgz> dobey: not sure as I can't find a team I'm subscribed to stuff seperately under, but maybe under ubuntu/+source/PROJECT/+subscriptions ?
[14:04] <dobey> apparently that doesn't work either. but i'm middle-man at the moment, as no teams i'm admin of are subscribed to package bugs in ubuntu, i don't think
[14:05] <mgz> okay, so we're both in the dark :)
[14:06] <dobey> but i do see an Unsubscribe for myself on another package where i am subscribed, on the +subscriptions page
[14:06] <dobey> i wonder if that's broken for teams that are also members of ubuntu-bug-control
[14:10] <bdrung> hi, i try to run lp:ubuntu-sponsoring, but it always crashes due to a LP timeout error (OOPS-cdbdeb62c9dc06f0a82055212f63fb1e)
[14:11] <dobey> mgz: http://ubuntuone.com/5zoA5NukA3PV1bjhPiJlgj <- chipaca sees this on that page. trying to remove ubuntuone-hackers from couchdb bug subscription. he's the team owner and an admin. for me, it shows my subscription via that team. wonder why it's blank for him
[14:13] <mgz> dobey: right, that's what I see on projects I have no direct subscriptions for
[14:13] <mgz> implies if he's subscribed to that project, it's through some other more twisty path
[14:13] <dobey> no, ubuntuone-hackers is subscribed to that package
[14:14] <dobey> mgz: you can see it listed on https://launchpad.net/ubuntu/+source/couchdb
[14:18] <mgz> dobey: can he edit stuff on ~ubuntuone-hackers/+structural-subscriptions ?
[14:22] <dobey> mgz: i could delete it from there even
[14:23] <mgz> dobey: ace.
[14:23] <sfeu> Hey there, I require armhf builds for my project. But  if i define armhf for architecture in debian/control, launchpad rejects my build. So i am required to use my own pbuilder on arm, right?
[14:24] <mgz> sfeu: or get a special permission bit to use the launchpad arm builders
[14:25] <mgz> I'm not sure who you need to beg for that though.
[14:27] <sfeu> mgz: thanks for the info. I will try to asks the admins in launchpad/answers then.
[14:27] <mgz> that'll still be me today, I'll poke someone in the know.
[14:31] <sfeu> thanks mgz. I am doing my first steps porting libcassowary, a constrain solver to recent 10.04 and 12.04 ubuntu versions. would be great if one can enable this special bit for my repository. https://launchpad.net/~sfeu/+archive/ppa/+packages
[14:37] <mgz> sfeu: will get back to you shortly
[14:48] <sfeu> mgz: thx
[15:00] <czajkowski> sfeu: are you canonica/linaro
[15:30] <mgz> sfeu: so, the short answer is yes, you need your own builder (or to piggyback on debian or some other group that providers builders to members)
[17:59] <dobey> how do i copy binary packages from the Ubuntu archive, to a PPA, into a different series?
[18:01] <elmo> dobey: from the PPA's page, 'View Package Details'
[18:01] <elmo> dobey: then there should be a copy link near the top right
[18:01] <elmo> oh, blah
[18:01] <elmo> dobey: sorry
[18:02] <dobey> :)
[18:03] <dobey> yeah, from ubuntu main into a ppa, not from one ppa to another
[18:03] <dobey> stupid circular deps in python modules not making this easy for me :-/
[18:35] <sfeu_> mgz: ok. thanks - then i will set up my own one.
[19:44] <evillyEvil> How long is a "Rejected" branch kept on launchpad?
[19:44] <evillyEvil> How do I view the list of all rejected branches of mine?
[19:50] <lifeless> evillyEvil: code.l.n/~ and use the filter to choose rejected branches.
[19:51] <lifeless> erm, abandoned.
[19:51] <lifeless> I'm not sure there is a view for my-reject-ed-proposals
[19:51] <evillyEvil> lifeless: will those rejected branches got deleted after sometime?
[20:19] <lifeless> evillyEvil: nope


[00:01]  * Obsidian1723 work is over yeah!! Time to go home. cya all
[21:05] <tonyyarusso> exigraff, h00k, jenkinbr: Has there been any movement on a Duluth/Superior or Grand Rapids release event?  Or just Madison and Twin Cities?
[21:05] <tonyyarusso> Alpha_Cluster: Do you have something put together for Northwest yet?
[22:31] <Alpha_Cluster> tonyyarusso: no i havent really be doing much sorry :(
[22:31] <Alpha_Cluster> i actually havent even been using ubuntu much
[22:34] <Obsidian1723> Alpha, what do you use?
[22:36] <Alpha_Cluster> OSX >.< and WHS mostly
[22:37] <Alpha_Cluster> i have a copy of ubuntu and kubuntu that run in parallels its just ati's drivers cause tearing on my media center computer
[22:37] <Alpha_Cluster> otherwise i might have a linux box
[22:39] <Obsidian1723> ahhh
[22:39] <Obsidian1723> Why OIS X?
[22:39] <Obsidian1723> OS X
[22:39] <Alpha_Cluster> cause its Unix and they make really nice laptops
[22:40] <Obsidian1723> Its not UNIX..
[22:40] <Alpha_Cluster> um actaully it is
[22:40] <Alpha_Cluster> its got the unix certs
[22:40] <tonyyarusso> Alpha_Cluster: Well, if you can still coax someone else into organizing something, that'd be nice.  :)
[22:40] <Alpha_Cluster> rofl
[22:41] <Obsidian1723> Its a hybrid mix of NeXtstep misxed with FreeBSD. FreeBSD is a deriviative of UNIX, where as Mac OS X is a hybrid / derivative of a derivaitve.
[22:41] <Alpha_Cluster> i dont know anyone really up here to much...
[22:42] <tonyyarusso> Obsidian1723: http://www.macworld.co.uk/mac/news/index.cfm?newsid=19719&pagtype=allchandate
[22:43] <Alpha_Cluster> yeah unix is a cert nothing more
[22:43] <tonyyarusso> right
[22:43] <Obsidian1723> yah?
[22:43] <Obsidian1723> Well Mac OS isn't SCo, System V
[22:44] <Alpha_Cluster> why does that have anything to do wtih Unix?
[22:45] <Alpha_Cluster> all unix means is The Open Group certified it and its posix complient
[22:48]  * Alpha_Cluster stabs 5400rpm hdd
[22:48] <Alpha_Cluster> stupid laptop harddrives
[22:51] <tonyyarusso> Alpha_Cluster: Seriously, if you could even get four or five people to hang out and talk about Lucid for an hour at a coffee shop it would make me happy.
[22:51] <tonyyarusso> And with that, I should head out.
[22:51] <Alpha_Cluster> tonyyarusso: we shall see what i can do
[22:51] <tonyyarusso> Takyoji: Same goes for you down in the South :)
[22:52] <Alpha_Cluster> yay im not hte only bad one >.<
[22:53] <Takyoji> :P
[22:53] <Takyoji> Otherwise it may have to be a week late.
[22:53] <Takyoji> As in, next week.
[22:53] <Alpha_Cluster> lol
[22:53] <Alpha_Cluster> yeah i haave the same problm
[22:53] <Alpha_Cluster> maybe the X server will work by then too
[22:53] <Alpha_Cluster> or have they fixed that
[22:55]  * Obsidian1723 is back
[22:56] <Alpha_Cluster> UNIX smash
[22:56] <Takyoji> otherwise I'll actually have a laptop to bring with me for once. :D
[22:56] <Takyoji> for the installfest
[22:56] <Alpha_Cluster> lol i actually dont have a mobile linux comp >.<
[22:56] <Alpha_Cluster> i just got a vm
[22:57] <Obsidian1723> Good to have a mobile Linux box.
[22:57] <Takyoji> oh that's right, aren't you that Windows elitist that doesn't even use Ubuntu? :P
[22:57] <Takyoji> (kidding of course)
[22:57] <Alpha_Cluster> Takyoji: actually i a windows server and a MacBook Pro :p
[22:58] <Alpha_Cluster> i keep trying to use Ubuntu for my media center but ATI doesnt want it to happen
[22:58] <Obsidian1723> Try Mythbuntu?
[22:58] <Alpha_Cluster> ist the graphics driver tears
[22:59] <Alpha_Cluster> i know more then enough about linux to configure the rest but i cannot get fglrx to not tear
[22:59] <Obsidian1723> Swap it out for an Nvidia or a PTCV5500
[22:59] <Obsidian1723> PCTV5500
[22:59] <Obsidian1723> yeah ATI can be a biatchie.
[22:59] <Obsidian1723> You can never go wrong with Intel/Nvidia
[22:59] <Alpha_Cluster> oh iknow
[23:00] <Alpha_Cluster> yeah you can go very wrong
[23:00] <Obsidian1723> AMD/ATI, lotsa issues
[23:00] <Alpha_Cluster> i hate nvidia's elitism
[23:00] <Obsidian1723> 'yeah, but it works.
[23:00] <Alpha_Cluster> i dont care
[23:00] <Alpha_Cluster> i want it to work correctly
[23:00] <Alpha_Cluster> and in linux that means FOSS drivers
[23:00] <Obsidian1723> It's certainly less restrcitive than Apple is.
[23:01] <Obsidian1723> Well, FOSS is nice if you can get it... I'm not like rms where it must be free or nothing at all.
[23:01] <Alpha_Cluster> eh with apple i have no expectation that anything above cocoa is open on linux i shouldnt have to run a nvidia binary blog to get my grpahics
[23:01] <Alpha_Cluster> ati at least is making it possible to write the drivers
[23:01] <Alpha_Cluster> and actualy those drivers will probably work here in a few months for me
[23:02] <Alpha_Cluster> Obsidian1723: btw problem with the HD5500 no cable card
[23:04] <Alpha_Cluster> besides nvidida doesnt make hdmi ports on their graphics cards
[23:04] <Obsidian1723> True...
[23:04] <Alpha_Cluster> which is the only way i will plug a computer into my tv besides displayport
[23:05] <Takyoji> Isn't HDMI patent-encumbered? :P
[23:05] <Alpha_Cluster> ?
[23:05] <Obsidian1723> heh
[23:06] <Alpha_Cluster> you need to license it like 90% of port technologies
[23:06] <Alpha_Cluster> i dont believe there is anything encumbering about video going through it
[23:13] <h00k> tonyyarusso: I've been busy,the only thing that I see in the state is down in Madison where I'll be headed


[23:58] <on3pk> after I delete the file, it will then try to download it again at the next upgrade command
[23:59] <on3pk> I can hold back manpages, but then nothign upgrades


[04:15] <maxwellian> From w3m code: "is_hangul = wtf_is_hangul((wc_uchar *) str);"
[04:15]  * maxwellian loves self-documenting code
[05:36] <SunilThaha> Hi all, is there a way I can specify in debian packaging install-file to ignore files?
[10:28] <Laney> SunilThaha: -Xitem
[10:28] <Laney> see the manpage
[11:07] <LucidFox> Gah, this is going to be a pain
[11:07] <LucidFox> libdc0 doesn't build in Debian on armel because it doesn't pass a test there...
[11:07] <LucidFox> but it passes it on Ubuntu...
[11:07] <LucidFox> I have no idea how to approach this
[11:08] <NCommander> LucidFox: abandoned all hope?
[11:09] <NCommander> LucidFox: where's the Debian build log?
[11:09] <LucidFox> Well, it's one obscure architecture, specific to Debian and not reproducible on Ubuntu, I don't have the hardware to check, and it prevents it from entering testing
[11:09] <LucidFox> Debian build log: https://buildd.debian.org/fetch.cgi?&pkg=libdc0&ver=0.3.23-1&arch=armel&stamp=1273321478&file=log
[11:09] <LucidFox> Ubuntu build log: http://launchpadlibrarian.net/44543051/buildlog_ubuntu-lucid-armel.libdc0_0.3.23-1_FULLYBUILT.txt.gz
[11:09] <NCommander> LucidFox: lots of people would complain that armel is obsecure :-)
[11:10] <LucidFox> Well... what *is* armel?
[11:10] <bilalakhtar> !armel
[11:10] <bilalakhtar> oops, the bot doesn't kno
[11:10] <azeem_> little endian arm, with a modern ABI
[11:10] <bilalakhtar> !architecture
[11:10] <NCommander> LucidFox: ARM architecture, basically embedded devices, mobile phones, and other handy stuff
[11:10] <LucidFox> ah
[11:11] <NCommander> LucidFox: hrm, interesting
[11:11] <LucidFox> Well, I don't have the needed hardware to test-build the package on sid :/
[11:11] <azeem_> LucidFox: you can't install qemu? :P
[11:11] <azeem_> but to be fair, it's probably a local issue with the Debian build
[11:11] <azeem_> d
[11:11] <LucidFox> qemu supports armel?
[11:12] <RAOF> Yeah.
[11:12] <NCommander> LucidFox: yup, though its a bit slow.
[11:12] <LucidFox> on an AMD64 host CPU?
[11:12] <tumbleweed> LucidFox: yes, although it works best if you use qemu-static rather than CPU emulation
[11:12] <RAOF> NCommander: Slower than the native hardware? :)
[11:12] <NCommander> LucidFox: are you a DD? You can get access to the armel porter box
[11:12] <NCommander> RAOF: yes :-/
[11:12] <LucidFox> No, not a DD
[11:12] <tumbleweed> RAOF: pretty fast, though
[11:12] <tumbleweed> (because you can throw many cores at it)
[11:12] <RAOF> There's actually a script to build an armel chroot with qemu-static.  It's pretty simple.
[11:13] <RAOF> I think it's a part of pbuilder-dist?
[11:13] <NCommander> RAOF: there's also rootstock. ogra ^
[11:13] <ogra> rootstock is way t complex
[11:13] <ogra> if you only want a chroot use qemu-debootstrap
[11:14] <LucidFox> neat
[11:14] <LucidFox> And well, I wouldn't be able to become a DD even if I wanted to, since apparently you need your key personally signed, and there are like 2 DDs in all of Russia
[11:15] <tumbleweed> LucidFox: next time you go on holiday...
[11:16] <LucidFox> eh...
[11:16] <tumbleweed> (look for DDs when you are in other countries)
[11:17] <LucidFox> Let's just forget it, okay?
[11:17]  * LucidFox grumbles
[11:19] <LucidFox> Okay, found the needed option in man pbuilder-dist, thanks
[11:24] <LucidFox> Why is it called "armel" anyway?
[11:24] <LucidFox> What does the "el" part stand for?
[11:24] <Rhonda> Endian Little
[11:24] <LucidFox> ah
[11:26] <Rhonda> LucidFox: http://wiki.debian.org/ArchitectureSpecificsMemo might be a helpful overview. :)
[11:45] <pmjdebruijn> hi
[11:45] <pmjdebruijn> I'm building package on my PPA, which works just fine
[11:45] <pmjdebruijn> however I want to add a -dbg variant
[11:45] <pmjdebruijn> that all seems simple enough, but the only change would be the not-stripping of the symols
[11:46] <pmjdebruijn> however, I'd like to debug version to be compile with different options
[11:46] <pmjdebruijn> since the application in question (darktable) can have extra internal checks that slow it down, but are useful for debugging
[11:47] <pmjdebruijn> so Ideally I want to to build two binary packages out of a single source package
[11:47] <pmjdebruijn> with a different ./configure
[11:47] <pmjdebruijn> can anybody give me some hints as how to do this (elegantly :)
[11:49] <RAOF> pmjdebruijn: There are a couple of packages which build multiple times with differnet options.
[11:49] <RAOF> The one I've touched most recently was mesa - that builds about 6 times with different configure options ;)
[11:53] <pmjdebruijn> RAOF: aha!
[11:54] <pmjdebruijn> RAOF: I'll look into it, thanks
[11:54] <RAOF> Mesa is more complex than the simplest case, but it'll be something to start with.
[11:55] <pmjdebruijn> yeah thanks
[11:57] <bigon> could someone new beid package?
[11:58] <pmjdebruijn> eh?
[13:18] <\sh> siretart: ping -> please join #fai@oftc thx :)
[14:12] <coolbhavi> hello I ve a doubt, I m maintaining mobile-broadband-provider-info in debian and ubuntu .. How to request SRU in case of an exception? https://wiki.ubuntu.com/StableReleaseUpdates#mobile-broadband-provider-info
[14:21] <pmjdebruijn> anybody have a simpler example of building multiple binary packages from a single source packages with different configures
[14:21] <pmjdebruijn> maybe cdbs/debhelper7 based, since I'm trying to move anyway from normal packages
[14:25] <pmjdebruijn> btw
[14:25] <pmjdebruijn> out of curiousity
[14:25] <pmjdebruijn> how do the -dbg packages actually work
[14:26] <pmjdebruijn> I mean you have the /usr/lib/debug/usr/bin/foo binary
[14:26] <pmjdebruijn> would I need to start that directly?
[14:26] <Rhonda> You don't start it.
[14:26] <pmjdebruijn> gdb just "knows"?
[14:26] <Rhonda> Yes.
[14:26] <pmjdebruijn> huh?
[14:26] <pmjdebruijn> ok?
[14:26] <pmjdebruijn> funky
[14:27] <pmjdebruijn> so if I gdb /usr/bin/foo, it actually start /usr/lib/debug/usr/bin/foo ?
[14:27] <pmjdebruijn> that's actually quite cool
[14:27]  * Rhonda . o O ( and why do connected topics always appear within a short timeframe for me? )
[14:27] <Rhonda> No, it doesn't start that.
[14:27] <Rhonda> …
[14:27] <pmjdebruijn> but what if a binary has it's own libraries (for plugins or whatnot)?
[14:28] <pmjdebruijn> do those get redirected automatically as well to /usr/lib/debug?
[14:28]  * pmjdebruijn guesses they will
[14:28] <Rhonda> There is no redirection happening at all.
[14:28] <pmjdebruijn> huh?
[14:28] <Rhonda> Those are just the stripped out debugging informations.
[14:28] <pmjdebruijn> are there any docs on that?
[14:28] <Rhonda> Nothing gets started from there.
[14:28] <Rhonda> The debuggers look in there for context, nothing more nothing less.
[14:28] <pmjdebruijn> Rhonda: those aren't full binaries?
[14:29] <Rhonda> No, definitely not. :)
[14:29] <pmjdebruijn> oh
[14:29] <pmjdebruijn> hmm
[14:29] <pmjdebruijn> ok
[14:29] <pmjdebruijn> though I've talked to some developer who note that compiling with -O2 for example does destroy some info handy on debugging?
[14:29] <pmjdebruijn> /on/when/
[14:33] <LucidFox> Okay. The worst thing someone can do is provoke me into being honest.
[14:34] <LucidFox> And I'll be honest. I think the Debian New Maintainer is such ridiculous, overcomplicated bull that it's a wonder they ever get new DDs to begin with.
[14:37] <Rhonda> LucidFox: *blinks*  :)   Well, yes and no. :)
[14:38] <LucidFox> The "web of trust" requirement reeeeeally annoys me
[14:38] <carstenh> LucidFox: you need to 1. maintain some packages in debian 2. enter your mail on some internet site 3. wait 4. answer questions (the templates that are normally used are available via public svn) you get per mail from someone 5.  maintain your packagesand wait
[14:38] <carstenh> getting two or three signatures can't be that hard
[14:38] <LucidFox> No sane open source project should include meeting an existing developer in person as a requirement to become a developer
[14:38] <LucidFox> carstenh> ...
[14:38] <LucidFox> Not when the nearest DDs are like half the continent away
[14:39] <pmjdebruijn> :(
[14:39] <azeem_> LucidFox: go to a UDS and get your key signed there
[14:39]  * LucidFox sighs
[14:39] <LucidFox> You don't understand, do you?
[14:39] <azeem_> I think I don't care
[14:39] <LucidFox> I was able to become a MOTU without *ever* meeting *any* other Ubuntu developer in person.
[14:40] <azeem_> that's great; it doesn't mean other policies are insane
[14:40] <carstenh> LucidFox: you can't upload binary packages to ubuntu
[14:40] <LucidFox> And I'm not exactly made of money to go to developer meetings
[14:53] <RainCT> coolbhavi: Have you seen https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ?
[14:55] <RainCT> LucidFox: have you got in touch with them to ask for an alternative? the docs say there are other ways if you live too far away from other DDs
[14:56] <carstenh> | If there is no Debian Developer close to you, alternative ways to pass the ID check may be permitted as an absolute exception on a case-by-case-basis. See the identification page for more information.
[14:57] <LucidFox> "as an absolute exception on a case-by-case-basis" generally means "no"
[14:57] <LucidFox> And it'I'm sure that
[14:57] <LucidFox> And it's Debian, I'm sure that "half of Russia away" is close enough by their standards
[14:58] <Rhonda> No, it doesn't generally mean "no".
[14:58] <maco> LucidFox: it has happened
[14:58] <Rhonda> Pleading that it generally means "no" without giving it a try is spreading FUD, sorry to speak so frankly. :/
[14:59] <Rhonda> And I guess you know that I am the least person who is against you or anything along that lines.
[15:01] <LucidFox> I know
[15:01] <LucidFox> But reading the procedure makes me want to cry
[15:02] <azeem_> pfft
[15:03] <LucidFox> I know, I know, "But we all had to go through this!!!11"
[15:03]  * Rhonda hugs LucidFox comfortingly.
[15:03] <LucidFox> That doesn't change my opinion about the procedure
[15:03] <Rhonda> LucidFox: You can depend on my full support on this if it becomes of a real issue with the frontdesk, to speak with them.
[15:04] <LucidFox> Well, I'm not thinking of becoming a DD actually
[15:04] <LucidFox> my contributions to Debian aren't nearly enough
[15:04] <RainCT> LucidFox: It's not that bad, the questions aren't anything special (if just my AM hadn't dissapeared after saying he'd check some package and give the final ack :/)
[15:05] <maco> RainCT: the questions arent the problem. the keysigning is
[15:05] <RainCT> Yeah
[15:06] <Rhonda> LucidFox is in somewhat the same boat with respect to keysigning like Vagrant.
[15:06] <LucidFox> Vagrant?
[15:06] <Rhonda> … though from a completely different angle.
[15:06] <LucidFox> Who's Vagrant?
[15:07] <Rhonda> LucidFox: Vagrant is a linux terminal server project developer who abandoned his "legal" name long ago and refuses to hand out a paper that he doesn't believe in.
[15:07] <LucidFox> Ah
[15:07] <LucidFox> Well, that's a factor too
[15:08] <LucidFox> As you can imagine, I have objections to the idea of contributing under the name written in my passport
[15:08] <LucidFox> so even if I showed it to a DD, it wouldn't be of much use
[15:08] <Rhonda> I've met him at at least three debconfs so far and dared to state once that I might be thinking about signing his key because I have way more trust in him than in some others that hand out regular passports on keysigning parties.
[15:09] <Rhonda> LucidFox: Vagrant isn't contributing under his legal name neither.
[15:10] <Rhonda> LucidFox: echo vagrant | nc db.debian.org finger
[15:10] <maco> i've signed for an alias before
[15:11] <LucidFox> Actually
[15:11] <LucidFox> Disregard this...
[15:11] <LucidFox> it turns out that there's a DD in my city
[15:11] <LucidFox> but the point still stands!
[15:11] <Rhonda> Yes, it might not be easy, but I am quite confident that your case is special enough to warrant some discussion/effort in that area, and I am willing to help.
[15:11] <maco> for someone i'd known for like a year
[15:12] <LucidFox> turns out he's quite newly admitted, I was surprised to see a DD in Novosibirsk
[15:12] <LucidFox> But this changes nothing.
[15:13] <LucidFox> Honestly I don't think my contributions to Debian are enough even for DMship, I just happen to maintain a few packages ported from Ubuntu - it's more like I felt bitter about the whole air of elitism around the procedure.
[15:13] <LucidFox> compared to Ubuntu, again
[15:17] <LucidFox> Sorry if I sounded offensive...
[15:18] <Rhonda> See it from a different angle - if it weren't for those itches, ubuntu might not even exist and mark would still be a happy DD. ;)
[15:18] <LucidFox> Rhonda> I don't think it was his main motivating factor for creating Ubuntu
[15:19] <Rhonda> I wouldn't rule out that it was part of the reason.
[15:31] <carstenh> LucidFox: this should be enough for DM and nowaday people are required to become DM before the become DD.
[15:31] <carstenh> RainCT: you could ask frontdesk about getting a new AM
[15:31] <LucidFox> AM?
[15:32] <carstenh> account manager, the person who puts the question templates from svn.debian.org into a mail
[15:32] <LucidFox> ah
[15:32] <carstenh> ... checks the answers and checks the packages and then recommends applicants to the frontdesk
[15:35] <carstenh> s/account manager/application manager/
[15:38] <Rhonda> carstenh: Well, the case is on a completely different area, like mentioned. I'd like to have further discussion on this topic in here, how helpful and "convincing" they are meant with "go to UDS" or similar to have dropped. Thanks for understanding.
[15:39] <shadeslayer> Rhonda: around? :)
[15:40] <Rhonda> No, that's just a clone and bot of myself.
[15:40] <shadeslayer> heh :P
[15:41] <shadeslayer> Rhonda: i just uploaded a package on mentors,any ideas how to move forward? nobody on debian-qt-kde is around :(
[15:41] <shadeslayer> well.. not just,i uploaded my package yesterday
[15:41] <shadeslayer> Rhonda: http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=fastuserswitch
[15:42] <Rhonda> shadeslayer: did you try #debian-mentors or #debian-ubuntu or the mentors mailinglist?
[15:42] <shadeslayer> i trued debian-mentors,left a message yesterday,someone is yet to reply
[15:42] <shadeslayer> *tired
[15:42] <shadeslayer> oh gwad
[15:42] <shadeslayer> *tried :P
[15:44] <shadeslayer> Rhonda: btw just a question,my package is called plasma-widget-fastuserswitch but the source is called fastuserswitch,will i be questioned for that?
[15:45] <azeem_> no
[15:46] <shadeslayer> ok... good to know
[15:49] <Rhonda> shadeslayer: It is generally adviced to have as source package name one of the binary package names …
[15:49] <Rhonda> azeem_: erm, your no isn't completely right
[15:49] <Rhonda> azeem_, shadeslayer: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581337#29
[15:50] <Rhonda> For a context of why it is a bad idea to not have the source package name match one of its binaries.
[15:50] <azeem_> Rhonda: it's adviced to have the source package name as the upstream tarball name
[15:50] <shadeslayer> Rhonda: ok,but upstream provides the tarball named as fastuserswitch , but , the tarball has a plasmoid, thus i named the package plasma-widget-fastuserswitch
[15:50] <Rhonda> azeem_: No, it isn't.
[15:50] <azeem_> *shrug*
[15:50] <Rhonda> azeem_: See the perl packages, for instances.
[15:51] <Rhonda> And please read the linked bugreport and the woes it brings.
[15:51] <shadeslayer> right i see what this can cause
[15:51] <shadeslayer> so what do you suggest?
[15:51] <shadeslayer> rename upstream tarball?
[15:52] <Rhonda> It's a simple mv. :)
[15:52] <azeem_> Rhonda: isn't that bug report about a binary package from another source package which is also called sm?
[15:52] <shadeslayer> Rhonda: no i meant to ask if its advised :P
[15:53] <Rhonda> shadeslayer: I would suggest that, yes. It avoids some confusion.
[15:54] <shadeslayer> Rhonda: great,thanks for the advice,now one last thing,since that package has already been uploaded,is it possible to delete it? or rather what do i do with that pacakge
[15:55] <Rhonda> I have no clue about how the mentors site works in that area. Given that it requires one to always do a full source upload including orig.tar.gz I think it is training wrong behavior anyway and usually advice to use a random webserver as dropbox. :)
[15:55] <Rhonda> Have to leave now, sorry.
[15:56] <RainCT> shadeslayer: You can delete it from the "My packages" (or whatever it's called) section
[15:56] <shadeslayer> RainCT: ah thanks
[15:56] <shadeslayer> Rhonda: thanks again
[15:57] <tumbleweed> shadeslayer: yes you need to delete from mentors
[15:57] <coolbhavi> hi tumbleweed
[15:58] <tumbleweed> coolbhavi: hi
[15:58] <tumbleweed> shadeslayer: actually, I can't remember if you need to delete after it's been uploaded, but it's wise to delete after you've got an interested spnsor (who will presumably upload)
[15:59] <shadeslayer> :D
[15:59] <shadeslayer> done
[15:59] <shadeslayer> will upload with proper fix :P
[16:00] <RainCT> well you could also set it as "not looking for a sponsor", but there isn't really a point in having it there for no reason
[16:00] <coolbhavi> tumbleweed, if you have time can you please take a look at https://bugs.edge.launchpad.net/ubuntu/+source/ugene/+bug/606642
[16:01] <tumbleweed> coolbhavi: I can't look right now, but it's in the sponsor queue (and an open tab in my browser)
[16:02] <coolbhavi> tumbleweed, okay!
[17:59] <Kasuko> Hello, I am having a package that is failing to build on the PPA, it's just a simple command line program in python using distutils. I followed https://wiki.ubuntu.com/PackagingGuide/Python exactly and it builds on my own computer. But when I submit it to the launchpad PPA it fails with the error being "/bin/sh: python2.5: not found" Any idea why?
[18:00] <danohuiginn> Kasuko: probably because maverick is using python2.6
[18:00] <danohuiginn> you'll need to adjust the python version somewhere
[18:00] <danohuiginn> or, ideally, configure things to automatically use the appropriate version
[18:02] <Kasuko> danohuiginn: I never set it to use python 2.5, I only ever said it depends on python >= 2.5
[18:02] <Kasuko> its using the cdbs though
[18:02] <Kasuko> so should there be a build-depends on python2.5?
[18:04] <carstenh> run "grep -r python2.5 ." in the source directory to find the error
[18:05] <carstenh> or rather "in the source packages top directory"
[18:05] <Kasuko> nothing
[18:05] <carstenh> weird
[18:07] <Kasuko> I have no doubt it's probably me but I don't know where to find information on why something isn't building on the PPA. It builds fine on my computer
[18:08] <Kasuko> the error is while running "running build_py
[18:08] <carstenh> posting the link to the build log could help
[18:09] <Kasuko> http://launchpadlibrarian.net/52217318/buildlog_ubuntu-karmic-i386.pyxis_0.1-0ubuntu1_FAILEDTOBUILD.txt.gz
[18:11] <carstenh> for buildver in 2.6 2.5; do cd /build/buildd/pyxis-0.1 && cd . && python$buildver setup.py build --build-base="/build/buildd/pyxis-0.1/./build"; done
[18:11] <carstenh> this doesn't look correct but i have no idea how python is packaged this season
[18:13] <carstenh> /usr/share/cdbs/1/class/python-distutils.mk:67: WARNING:  Use of XS-Python-Version and XB-Python-Version fields in debian/control is deprecated with pysupport method; use\ debian/pyversions if you need to specify specific versions.
[18:13] <Kasuko> so what do I do?
[18:13] <carstenh> this warning is about versions, you got problems with version, thus fixing it can't hurt ;)
[18:14] <danohuiginn> yeah that error seems to come from within cdbs: for buildver in $(cdbs_python_build_versions)
[18:14] <Kasuko> carstenh: I don't know how to fix it though
[18:16] <pmjdebruijn> hmm I'm trying to add a -dbg (with the same configure), to my darktable package
[18:16] <pmjdebruijn> however I end up with two empty directories in debian/darktable and debian/darktable-dbg and two empty packages
[18:16] <pmjdebruijn> while debian/tmp is filled with lots of good stuff
[18:17] <pmjdebruijn> http://wiki.debian.org/DebugPackage
[18:17] <pmjdebruijn> I have this both with cdbs and debhelper
[18:17] <azeem_> pmjdebruijn: do you have a debian/darktable.install
[18:17] <azeem_> ?
[18:18] <shadeslayer> pmjdebruijn: you need install files ;)
[18:18] <carstenh> Kasuko: is this an arch all or an arch any package?
[18:19] <pmjdebruijn> shadeslayer: I was afraid of that
[18:19] <pmjdebruijn> I'd expected some automagics here as well
[18:19] <pmjdebruijn> ok
[18:19] <carstenh> Kasuko: could be http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577580
[18:19] <pmjdebruijn> well in theory I could just install straight into debian/darktable too, right?
[18:20] <pmjdebruijn> having .install files for darktable and darktable-dbg package is a bit pointless since everything except /usr/lib/debug has to go in darktable
[18:22] <shadeslayer> hmm
[18:22] <shadeslayer> pmjdebruijn: can you paste your rules files?
[18:22] <pmjdebruijn> I could
[18:22] <shadeslayer> please do :)
[18:22] <pmjdebruijn> just a minute different machine, I need to reattach my screen :)
[18:22] <shadeslayer> ok :)
[18:23] <Kasuko> carstenh: so essentially I am SOL till the builders use cdbs?
[18:24] <pmjdebruijn> shadeslayer: http://pastebin.com/11KNLfrd (debian/rules)
[18:24] <carstenh> Kasuko: they use cdbs, but possibly a buggy version or something completly different is broken in your package.  at least you begin to understand why many people don't use cdbs ;)
[18:25] <shadeslayer> hmmm.. that seems about right.. why isnt it installing files then :/
[18:25] <pmjdebruijn> I didn't have .install files yet
[18:25] <pmjdebruijn> I tried that just a minute ago
[18:25] <pmjdebruijn> failed because of a typo
[18:25] <shadeslayer> :P
[18:25] <pmjdebruijn> I just wanted to check if that's the proper way
[18:25] <carstenh> Kasuko: (because black magic is fine if it works but if it does not it is hard to debug)
[18:25] <pmjdebruijn> also in there a .install struction to take everything _Except_ something
[18:25] <shadeslayer> having install files is the proper way
[18:26] <shadeslayer> yeah
[18:26] <pmjdebruijn> is*
[18:26] <shadeslayer> uh wait... no
[18:26] <shadeslayer> afaik .install files install everything inside them
[18:26] <pmjdebruijn> right :(
[18:26] <shadeslayer> pmjdebruijn: you need to document which files you didnt install
[18:26] <Kasuko> carstenh: ya its installing version 0.4.59 on the chroot but that bug is fixed in 0.4.81 :(
[18:27] <shadeslayer> pmjdebruijn: put them in debian/not-installed
[18:27] <Kasuko> carstenh: so essentially you are saying learn debhelper :P
[18:27] <pmjdebruijn> shadeslayer: huh?
[18:27] <shadeslayer> pmjdebruijn: if you dont install something,you have to put it in debian/not-installed
[18:27] <pmjdebruijn> shadeslayer: that's not what I ment
[18:28] <pmjdebruijn> shadeslayer: I just wanted to install everything into darktable.install but /usr/lib/debug which goes into darktable-dbg
[18:28] <shadeslayer> pmjdebruijn: yes i know,but just giving you more info :)
[18:28] <pmjdebruijn> the point is I wouldn't have to update darktable.install every time the content changes
[18:28] <shadeslayer> yep
[18:29] <carstenh> Kasuko: does it work for newer versions?
[18:29] <Kasuko> carstenh: does what work for newer versions?
[18:30] <geser> Kasuko: looking at your build problem: it looks like it doesn't need any compilation for a specific python version. What's the XS-Python-Version value for that package?
[18:30] <carstenh> Kasuko: building on karmic fails, karmic is more than a year old. did the autobuilder try to build it on lucid or on maverick?
[18:31] <Kasuko> no, I was going to build it on karmic then copy to lucid and maverick
[18:31] <carstenh> Kasuko: but listen to geser, he is more experienced with python
[18:31] <Kasuko> geser: 2.5
[18:31] <Kasuko> carstenh: I listen to everyone :P
[18:35] <Kasuko> geser: yes, it's pretty much a simple python program. All it needs is some features from 2.5 (and they are only to remove deprication warnings)
[18:37] <geser> try XS-Python-Version: all or build-depend on python-all (as this would pull in python2.5 and python2.6)
[18:39] <Kasuko> geser: should I be using XS-Python-Version still or debian/pyversions?
[18:42] <Kasuko> geser: giving it a try, uploaded ... waiting for build
[18:46] <Kasuko> Aw crap, I have screwed the PPA up
[18:54] <shadeslayer> Kasuko: which one?
[18:55] <Kasuko> my pyxis one, I deleted the ubuntu1 version and was trying to reupload it. I should have just made an ubuntu2 version right?
[18:55] <Kasuko> ppa:pyxis/pyxis
[18:56] <shadeslayer> noo
[18:56] <shadeslayer> Kasuko: give me the link
[18:57] <shadeslayer> Kasuko: do you know how to version packages in ppa's?
[18:57] <Kasuko> https://launchpad.net/~pyxis/+archive/pyxis
[18:57] <shadeslayer> Kasuko: look at https://edge.launchpad.net/~rohangarg/+archive/experimental for hints
[18:58] <shadeslayer> awww....
[18:58] <shadeslayer> pyxis 0.1-0ubuntu1 <<
[18:58] <Kasuko> ... what?
[18:58] <Kasuko> ok I will add the ~ppa1 in
[18:58] <Kasuko> one question
[18:59] <shadeslayer> Kasuko: ok,when you upload to PPA's add something like ~lucid1~ppa1 or ~ppa1
[18:59] <Kasuko> would it be 0ubuntu0~ppa1?
[18:59] <shadeslayer> well.. since this package is currently not in debian but in ubuntu,it should be 0ubuntu1
[18:59] <shadeslayer> thats my take...
[19:01] <Kasuko> But its not in Ubuntu
[19:01] <Kasuko> This is the first it is being packaged. Actually the first it's being distributed
[19:01] <shadeslayer> Kasuko:  i meant that since your uploading the first ubuntu package :P
[19:01] <Kasuko> ok
[19:02] <Kasuko> also since it isn't distribution specific I was told I didn't need a ~lucid1
[19:03] <maxb> Typically I'd call something -0ppa1 in this scenario
[19:03] <shadeslayer> maxb: 0ubuntu1-0ppa1 ?
[19:03] <maxb> No, just upstreamwhatever-0ppa1
[19:04] <shadeslayer> seems reasonable ..
[19:04] <Kasuko> maxb: pyxis_0.1-0ubuntu1~ppa1
[19:05] <shadeslayer> Kasuko: no pyxis_0.1-0ppa1
[19:05] <Kasuko> alright
[19:06] <maxb> The reason not to do 0.1-0ubuntu1~ppa1 here, is that version sounds like 1) Ubuntu packaged 0.1-0ubuntu1, and then 2) I backported it in my ppa
[19:06] <Kasuko> maxb: I agree, but I was thinking it would have been more like 0ubuntu0~ppa1 but just ppa1 makes more sense
[19:07] <Kasuko> will there be any issues if I do want to get it into the ubuntu repos?
[19:07] <maxb> You are right, there used to be some poor advice on a launchpad wiki which had people doing the ubuntu0~ppa thing far too often
[19:08] <Kasuko> so if I version it ppa1 and then version ubuntu1 comes out which superscedes what?
[19:08] <maxb> Issues of what kind? The only thing related to versioning is that all of your PPA versions should be "less than" the version number which would be assigned to a first ubuntu upload
[19:08] <maxb> In this case, 0ppa1 is less than 0ubuntu1 so it all works out nicely
[19:09] <maxb> This is because "u" is later in the alphabet than "p"
[19:09] <Kasuko> oh ok, I wasn't sure how alphanumerical characters worked
[19:09] <Kasuko> maxb: thank you for your help, I guess I should stop assume wiki's words are laws :P
[19:10] <maxb> Wikis are helpful, but ultimately they *are* editable by pretty much anyone, so well-meaning misinformation may be present
[19:25] <Kasuko> and its GOOD! Thank You all!
[20:27] <lfaraone> If I'm just doing a package rename, is there an easy way to streamline the process for the Archive Admins? (the content is the same)
[21:02] <fabrice_sp> who just uploaded aceitoneiso?
[21:02] <fabrice_sp> it still FTBFS for me in amd64
[21:02] <fabrice_sp> bdrung, ?
[21:15] <ari-tczew> shadeslayer: please take a look on MoM/universe, package yakuake, maybe you'll be interested in merge
[21:25] <bdrung> fabrice_sp: yes?
[21:25] <shadeslayer> ari-tczew: im overloaded with merges ^_^
[21:25] <bdrung> fabrice_sp: i uploaded aceitoneiso - it builds on amd64
[21:26] <shadeslayer> ari-tczew: i can do it after this week only
[21:26] <ari-tczew> shadeslayer: no problem for me
[21:26] <fabrice_sp> bdrung, strange, as I updated my chroot before building it :-/
[21:26] <fabrice_sp> you're using sbuild or pbuilder?
[21:27] <bdrung> fabrice_sp: pbuilder
[21:27] <fabrice_sp> hmm, I'm using sbuild
[21:27] <bdrung> fabrice_sp: are you behind a mirror?
[21:27] <fabrice_sp> not really: only caching packages
[21:27] <geser> bdrung: argh
[21:28] <bdrung> geser: ?
[21:28] <fabrice_sp> but I can see the libqtwebkit-dev package in my chroot
[21:28] <geser> bdrung: how did you convince soyuz to accept "Architecture: linux-any
[21:28] <geser> "?
[21:28] <geser> bug #605002
[21:29] <geser> bdrung: https://edge.launchpad.net/ubuntu/+source/acetoneiso/2.2.2-2 has no build records
[21:29] <fabrice_sp> I saw that: i thought it tookt time
[21:30] <bdrung> geser: i wasn't aware of that bug. i didn't argued with soyuz - it just accepted the package.
[21:32] <geser> bdrung: I looks like you need to upload it again with Architecure: any to get build records
[21:33] <geser> bdrung: you uploaded it with syncpackage from u-d-t, right?
[21:33] <shadeslayer> ari-tczew: handed over merge to yofel :D
[21:34] <shadeslayer> but he will need a bit of help :D
[21:34] <bdrung> geser: yes
[21:40] <Laney> wgrant: what's wrong with the Haskell mdt page? It says tons of packages are outdated in sid when they aren't
[22:01] <tyarusso> Anyone alive to tell me what I'm doing wrong with debconf?  The questions are asked during a dpkg-reconfigure, but not during installation.  https://edge.launchpad.net/~tonyyarusso/+archive/ppa/+sourcepub/1241047/+listing-archive-extra for source.
[22:07] <kees> tyarusso: debconf defaults to using the system-set priority level (high by default) when installing, and dpkg-reconfigure implies -plow
[22:09] <kees> tyarusso: and I think you only need the final "db_go"
[22:09] <kees> but I'm rather guessing at this point :0
[22:10] <toabctl> hi
[22:11] <toabctl> i downloaded a package with "bzr branch lp:ubuntu/xf86-input-wacom" , changed the package to a new upstream version and want to push th package now back to launchpad and send a merge request. how can i push the package to launchpad?
[22:11] <toabctl> i tried "brz push lp:~toabctl/ubuntu/xf86-input-wacom/new_upstream_0.10.7" but this does not work. any ideas?
[22:11] <tyarusso> kees: Okay, so I have one question set as "low" and one as "high", so from that I would expect the latter to be asked at least, wouldn't it?  As for the db_go point, I have no idea, although I thought the samples I found had it after each.
[22:12]  * tyarusso is rather amazed at how hard it seems to be to find someone well-versed in debconf - I thought everyone used this!
[22:13] <geser> toabctl: try "lp:~toabctl/ubuntu/maverick/xf86-input-wacom/new_upstream_0.10.7", don't if this is really the issue
[22:15] <geser> tyarusso: debconf is required for user interaction but not every package needs user interaction and depend on the work someone does or the package he touches, he might never need to touch debconf
[22:16] <ari-tczew> bdrung: very, very quick response. thanks!
[22:16] <tyarusso> geser: Fine, s/everyone/lots of people/ :P
[22:18] <geser> tyarusso: if you don't find here an answer, try asking #debian-devel@OFTC; DDs should have some knowledge of debconf too :)
[22:18] <tyarusso> geser: #debian-devel eh?  (I've been trying #debian-mentors; wasn't sure if the other was appropriate)
[22:20] <geser> hmm
[22:20] <geser> I don't know which one is better, I'm not very familiar with the #debian-* channels
[22:20] <tyarusso> mmk
[22:21]  * tyarusso will just try things until he either gets an answer or gets yelled at


[18:35] <macman_> meh
[18:35] <macman_> anyone alive ?
[19:37] <abx> Does anyone know of any issues on running Ubuntu 9.10 on a Toshiba Satellite A-Series laptop?