[00:27] DarinMiller, you around? [00:27] I need your help with sbuild again [00:31] I went through the tutorial and I'm getting the same error in all builds, including ones I know they're building in KCI: https://paste.ubuntu.com/24885745/ [00:31] I'm pretty positive this is related to the sbuild's setup... [00:40] gsilvapt: https://groups.google.com/d/msg/linux.debian.bugs.rc/3LHnM78aLZQ/5EkBoexwBQAJ [00:40] gsilvapt: Bookmark it ;) [00:40] I lost the logs of our conversations. I will bookmark it this time. Thank you!!!! [00:44] yeap, this is working now, I was getting a bit desperate about this, loll. [01:22] The cantor package is requiring a library I have no clue why's there for. Locally, the build fails (because the required version does not exist) but if I remove this package from the b-d, it builds with status attempted. [01:22] The library is libanalitza-dev [01:22] It was introduced in a upstream release: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/cantor/commit/?h=kubuntu_unstable&id=901b5b811d026d1ddbc7a2589e4bb18fbbf45c43 [01:23] Wait, not that one [01:23] I don't know where this comes from. It isn't part of the cmake list [01:28] Interesting, it does not fail in KCI builds because of this. [02:46] Hi gsilvapt [02:47] I f you have rebooted, you may need to run the last 2 commands in step 11 i n the sbuild guide: https://wiki.ubuntu.com/SimpleSbuild [02:48] 1) mkdir -p /dev/shm/schroot/overlay/ [02:49] 2) sudo mount -o remount,size=75% /dev/shm [02:54] gsilvapt: I responded before reading your build log. As you may have discovered, if you need a PPA for a build, then you can use something like: [02:54] sbuild -d artful-amd64 --extra-repository="deb [trusted=yes] http://us.archive.ubuntu.com/ubu ntu/ artful-proposed multiverse restricted universe main" -j4 [02:55] Or if you need multiple ppa, like this: [02:55] sbuild -d artful-amd64 --extra-repository="deb [trusted=yes] http://ppa.launchpad.net/kubuntu-ppa/staging-frameworks/ubuntu artful main deb [trusted=yes] http://ppa.launchpad.net/kubuntu-ppa/staging-plasma/ubuntu artful main" -j4 [02:55] also don't forget to clean up your failed sessions: schroot -e --all-sessions [08:00] Good morning [08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1585: SUCCESS in 59 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1585/ [08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1585: SUCCESS in 1 min 1 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1585/ [08:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1585: SUCCESS in 3 min 52 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1585/ [08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1585: SUCCESS in 4 min 12 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1585/ [09:23] Hey all [10:23] * acheronuk melts === nameless is now known as Guest63797 [12:54] DarinMiller, no the problem was with the gpg keys. I had to delete the folder in order to proceed. It's explained here: https://groups.google.com/forum/#!msg/linux.debian.bugs.rc/3LHnM78aLZQ/5EkBoexwBQAJ [12:55] And hello all o/ [13:09] Thanks @acheronuk [13:09] for what? [13:10] Twitter stuff [13:10] Ah, right. NP [13:14] tsimonq2: fyi I would need (at least) qtmultimedia built for i386 and updated in the landing ppa, otherwise there would be a few plasma packages which wouldn't be able to build [14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1586: SUCCESS in 59 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1586/ [14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1586: SUCCESS in 1 min 3 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1586/ [14:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1586: SUCCESS in 3 min 52 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1586/ [14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1586: SUCCESS in 4 min 7 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1586/ [16:28] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_ark build #59: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/xenial_stable_ark/59/ [16:28] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ark build #47: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/artful_stable_ark/47/ [16:29] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_ark build #45: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/zesty_stable_ark/45/ [16:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ark build #51: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/artful_unstable_ark/51/ [16:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ark build #201: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/zesty_unstable_ark/201/ [16:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ark build #518: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/xenial_unstable_ark/518/ [16:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ark build #519: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/xenial_unstable_ark/519/ [16:48] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ark build #202: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/zesty_unstable_ark/202/ [18:02] santa_: ack [21:19] hello all [21:19] hi gsilvapt [21:22] hi clivejo [21:22] You asked about bug reporting the other night. Need anything in that regard? [21:23] we have lots of stuff we would like into the archive [21:24] I see. Well, I never done anything in that regard but I can learn :) [21:28] https://wiki.ubuntu.com/SponsorshipProcess [21:29] I assume I should focus on this page? https://help.ubuntu.com/community/ReportingBugs [21:30] well you use a bug report [21:30] https://bugs.launchpad.net/ubuntu/+filebug [21:30] Subscribe ubuntu-sponsors [21:33] https://bugs.launchpad.net/ubuntu/+bug/1663675 [21:33] Launchpad bug 1663675 in Ubuntu "[needs-packaging] Please package Peruse" [Wishlist,Incomplete] [21:33] try getting that in, valorie will love you forever [21:34] Wow, wait, I'm getting confused. [21:35] I'm not following what you need help with. Triaging bugs? Request sponsorship, fix bugs ...? [21:36] paperwork :P [21:37] That can be many things... Could you elaborate? :) [21:38] https://bugs.launchpad.net/ubuntu/+bug/1663675/comments/4 [21:38] Launchpad bug 1663675 in Ubuntu "[needs-packaging] Please package Peruse" [Wishlist,Incomplete] [21:40] Okay. And is there a list of all files which need this kind of thing? [21:46] the maintainer here should be the email address of kubuntu-devel? [21:57] clivejo, made a push. I followed the recommendations there, except rule #4 as I have no clue what that is [21:57] Ah, and rule #6. I don't want to mess up the licenses and copyright thingy [21:58] https://code.launchpad.net/~gsilvapt/kubuntu-packaging/+git/peruse/+merge/325892 [21:58] how are you mixing repos? [21:59] got ksudoku stuff in there too :/ [22:01] Ah, right... Dammit. I always click "choose other" and forget to click the bullet. It's an annoying bug. For the obvious reason, if you're choosing a different target, it is because you want that target. [22:01] Let me re-do that MR [22:02] Yeap, now it is correct: https://code.launchpad.net/~gsilvapt/kubuntu-packaging/+git/peruse/+merge/325893 [22:02] In fact I was looking at the diff and it was odd. [22:09] can you add a comment on the bug now and ask for a review? [22:10] https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/peruse/+ref/kubuntu_unstable [22:11] gsilvapt: are you on telegram? [22:11] clivejo, I have an account but I don't use it often because I don't know anyone who does. [22:11] And yes, I can take care of that [22:13] clivejo, I have to assign ubuntu-sponsors to the bug again and in the comment ask for a review, isn't that so? [22:13] just add the comment for now [22:14] jbicha will review [22:15] Okay then. [22:15] I'm installing Telegram, btw [22:16] if he okays it, then add sponsors [22:17] Roger. Telegram -> gsilvapt [22:18] gsilvapt was added by: CliffordTheBigRedDoggie [22:18] Thanks, CliffordTheBigRedDoggie [22:18] that allows you to use the bridge [22:19] The bot over there? Or does this has more funcionalities? [22:20] clifford is my telegram [22:20] Yes, I recognized by name [22:20] Ah, duh!! [22:20] Never associated that huge name was you, even though I know you are called Clifford :) [22:23] So, what is the bridge after all? [22:23] (Regardless, thank you!) [22:23] it links Telegram to this channel [22:24] and the group on Telegram to here [22:24] Cool! [22:24] Do you guys use Telegram, besides for the bridge? [22:25] yup [22:25] Ok, thank you [22:25] most of the team are on here [22:26] hum, I'm seeing that. I thought some people stopped using telegram due to those security accusations they were involved a few months/years ago [22:27] oh? [22:27] clivejo, regarding some other packages that could require 'paper work', where can I find more? [22:28] maybe see how you go with peruse [22:28] but there are lots more [22:30] I asked because I figured this can take some time to be reviewed because people are generally busy [22:31] well telepathy-morse and telegram-qt need some work [22:33] need them to fix this bug https://bugs.launchpad.net/ubuntu/+source/ktp-contact-list/+bug/1512135 [22:33] Launchpad bug 1512135 in ktp-contact-list (Ubuntu) "Cannot add Telegram account to Telepathy" [Medium,Confirmed] [22:35] To fix that bug, I need to add that dependency in debian/control? package: telepathy-morse, homepage, .... [22:35] no, need those two new package in the archive [22:37] Hum, I'm not sure if I know how to do that [22:41] packaging is in LP git [22:42] This one already exists: https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/telegram-qt [22:42] I think [22:43] The other one does not. Do you mean I need to create the other one first? [22:43] Or I'm not following even? :D [22:43] yup [22:45] Ok, lets see if I can do that. [22:45] So, I have to take this list: https://github.com/TelepathyIM/telepathy-morse/blob/master/CMakeLists.txt [22:45] the packaging needs cleaned up [22:46] Create the usual debian folder and add all details that I can get from that GitHub repo? [22:46] the debian folder has been created already and it is building [22:46] Oh?, I couldn't find it [22:47] https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/telegram-qt/tree/?h=kubuntu_unstable [22:49] hum, then I'm not understanding what I'm dealing with. I have these two packages and they're related. Does telegram-qt needs the telepathy-morse addition and a general clean of the package? [22:49] telepathy-morse needs telegram-qt [22:49] they both provide access to telegram in Plasma [22:53] do you know how to check and update the copyright files? [22:55] No [22:59] I'm so lost right now xD [23:00] https://wiki.debian.org/CopyrightReviewTools [23:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [23:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #893: FIXED in 6 min 58 sec: https://kci.pangea.pub/job/mgmt_merger/893/ [23:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [23:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #873: FIXED in 7 min 2 sec: https://kci.pangea.pub/job/mgmt_progenitor/873/ [23:07] Lets see if I get this. kde-telepathy-contact-list has a bug which requires telepathy-morse to be installed. It is on your ppa. telepathy-morse requires telegram-qt, which is the link you sent. [23:07] Now, they both need work. I assume they need an copyright update for starters [23:07] in order for it to connect to and use telegram, you need to install the two extra packages [23:08] yes they both work and I'm using them at the moment [23:08] but we want them in the archive, so they have to have everything right [23:09] Okay, I'll try working on telegram-qt first because it is already in the archive [23:09] it is? [23:10] !info libtelegram-qt5-dev [23:10] Package libtelegram-qt5-dev does not exist in artful [23:12] s/archive/kubuntu-packaging [23:12] And I can't find the other one [23:12] its there too [23:12] https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/telepathy-morse [23:13] hum, thank you! [23:13] Regarding the previous bug you gave to me, Jeremy replied, I've subscribed the sponsors again. Do i need to do something else for the time being? [23:14] is he happy with the changes? [23:15] well, he asked me to re-subscribe the sponsor team so I guess he is [23:15] ok [23:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktouch build #213: FAILURE in 9 min 8 sec: https://kci.pangea.pub/job/zesty_unstable_ktouch/213/ [23:21] gsilvapt: do you have a PPA you could upload a build to? [23:23] I never did any of that so I don't think so [23:24] ok, so go to your page [23:24] https://launchpad.net/~gsilvapt [23:24] there [23:24] and create a new PPA, maybe artful or kde or something [23:24] whatever you want to call it [23:25] Ok, done [23:25] ok click on the link to it [23:26] Yes [23:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ksnakeduel build #189: FAILURE in 1 min 2 sec: https://kci.pangea.pub/job/xenial_unstable_ksnakeduel/189/ [23:28] Do you want the link or something in particular? [23:29] no [23:30] can you build the source and upload it to your PPA? [23:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdb build #42: FAILURE in 23 min: https://kci.pangea.pub/job/artful_unstable_kdb/42/ [23:32] Of kde-telepathy-contact-list? [23:32] no peruse [23:36] I have to go now, but we'll pick this up another time [23:36] I build the source by using sbuild and uploading some generated files after that or that's not it? [23:36] debuild -S [23:36] Bah, okay. We can resume tomorrow or so [23:37] grab the source with uscan --download-current-version --destdir=../ [23:37] then debuild -S [23:38] Ok, thank you. i'll try this and if I get stuck I'll report tomorrow [23:38] Ive uploaded to my PPA - https://launchpad.net/~clivejo/+archive/ubuntu/artful/+packages?field.name_filter=peruse&field.status_filter=published&field.series_filter= [23:38] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktouch build #47: FAILURE in 9 min 35 sec: https://kci.pangea.pub/job/artful_unstable_ktouch/47/ [23:39] you could investigate those failures ^ [23:41] My build failed for gpg errors [23:42] secret key not availble [23:42] probably cause I'm on the changelog [23:42] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-pa build #47: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/xenial_stable_plasma-pa/47/ [23:42] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_cantor build #38: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/xenial_stable_cantor/38/ [23:43] Yes, it has your name on it [23:44] should have got you to take it over [23:45] Don't know, but it failed the build [23:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #327: STILL UNSTABLE in 38 min: https://kci.pangea.pub/job/xenial_unstable_cantor/327/ [23:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kile build #54: STILL UNSTABLE in 39 min: https://kci.pangea.pub/job/zesty_unstable_kile/54/ [23:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_elisa build #51: STILL UNSTABLE in 39 min: https://kci.pangea.pub/job/xenial_unstable_elisa/51/