[00:01] np, thanks! === slashd- is now known as slashd === mnepton is now known as mneptok [04:59] Any chance to get a ppa removed if it's unmaintained? Is there a procedure for that? [04:59] delisting or the like? [05:00] reason why: this is confusing a lot of people. It's been broke almost as long as it has worked and every package in the repo has failed. [05:00] https://launchpad.net/~videolan/+archive/ubuntu/master-daily [05:00] https://launchpad.net/~videolan/+archive/ubuntu/master-daily/+packages === Serge is now known as hallyn [07:12] hey there [07:14] could somebody remind me how to trigger autopkgtests to use proposed package versions [07:17] seb128: IIRC adding &all-proposed=1 to the request was the trick, if that's what you're looking for [07:18] sil2100, thanks [07:18] I don't need full proposed though [07:18] I just want to use abi-compliance-checker from there [07:18] but I guess all-proposed would work as well [07:20] seb128: I guess you can use multiple 'trigger' entries too [07:20] that's what https://wiki.ubuntu.com/ProposedMigration#How_to_re-run_autopkgtests_with_dependencies_on_other_packages_in_the_proposed_pocket suggests [07:20] I wonder if I need to encode version [07:20] or just use &trigger=abi-compliance-checker [07:20] seb128: e.g. add something like trigger=abi-compliance-checker/version-from-proposed [07:23] sil2100, I tried, let's see if I got it right [07:23] sil2100, thanks [07:23] sil2100, oh, and hey, how are you? ;-) [08:26] tsimonq2, "kf5-messagelib" has symbols sadness... do you have an hint/patch? [08:29] I see acheronuk told me most of them are fixed in git, but I don't know where to look/fix [08:29] e.g. is this ok to upload? https://launchpad.net/ubuntu/+source/kf5-messagelib/4:16.12.3-0ubuntu1 [08:30] I mean the fixes on git [08:30] https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/messagelib I don't even know the right branch [08:35] LocutusOfBorg: They are fixed in git on the artful_archive branch, but for apps 17.04.3 which we have been getting ready to upload once transitions have calmed. So really have to look at symbols fixes and pick out what applies, or do a rebuild in a ppa of the 16.12.3 version and use pkgkde-symbolshelper to patch symbols and do some manual corrections [08:49] I will have time to do these later, but maybe not until this evening === gsilvapt_ is now known as gsilvapt [11:50] @pilot in === udevbot changed the topic of #ubuntu-devel to: Zesty Released | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-zesty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots: mdeslaur [13:01] mdeslaur: good day [13:02] I've seen that you updated LP: #1709193, thanks. I just noticed that I had not use "-proposed" for any of the debdiffs, please let me know if that is a problem [13:02] Launchpad bug 1709193 in gnutls28 (Ubuntu Artful) "Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer" [Undecided,Confirmed] https://launchpad.net/bugs/1709193 [13:09] sdeziel: nope, we don't do that anymore [13:09] sdeziel: would you mind if I added Bug-Debian and Bug-Ubuntu links to the patch and remove the debian bug number form the changelog? [13:10] minor OCD nitpicks [13:10] not at all, go ahead [13:10] thanks [13:10] I wasn't sure if I should leave the debian bug number in there [13:10] I usually stick it in the patch itself, others may do differently [13:13] makes sense [15:46] sdeziel: could you please update the gnutls bug description with the SRU template: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template [15:46] sdeziel: I'm about to upload the packages for processing [15:46] mdeslaur: yes, on it [15:47] awesome, thanks [16:01] Yayyyyyyy patch pilot \o/ [16:02] I will clap my hands when those patches land safely in -updates ;) [16:05] LocutusOfBorg: I see acheronuk took care of it :) [16:33] mdeslaur: let me know if the SRU justification is good enough [16:35] EvanCarroll: did this get sorted, yet? [16:36] i notice LocutusOfBorg is amongst the "newset members" of this PPA and s/he was active here not too long after you posted. [16:42] in case it did not: the generic answer is probably 'no' (however, this is just a guess of someone not formally involved in ubuntu or launchpad). PPAs are generally unsupported and extra care needs to be taken before one decides to trust them (and one should re-check occasionally). did you contact the owners, yet? [16:53] sdeziel: I think it's ok, let's see what the sru team says [16:55] tomreyn: no [16:56] tomreyn: I have contacted the owners [16:56] tomreyn: they're unresponsive. [16:56] every single one of them? [16:57] tomreyn: Also, in it's infinite Wisdom you can file an bug on a PPA. So essentially the only visual indicator is the failure to build, but because it's unsupported it's just fails all the time, it's wasting resources building (knowing it will fail), and it's confusing users as old questions point to it from when it worked. [16:57] tomreyn: yes, iirc, and multiple times. [16:58] There should be a method of delisting, especially in this case. The situaion with VLC and Ubuntu is really poor right now [16:59] EvanCarroll: PPAs are not part of ubuntu [16:59] are you referring to other issues? [17:00] may i ask about your motivation, just out of interest? [17:00] (as a reminder, i'm just anothe rubuntu user, no one special) [17:03] EvanCarroll: also did you try this? https://help.launchpad.net/Feedback [17:04] tomreyn: s/ubuntu/launchpad/ whereever it makes a difference. [17:04] motivation: eliminating confusion with official but unmaintained ppas. [17:05] I suppose I could join the right channel [17:05] EvanCarroll: i'm just wondering what makes you care, i bet there are a LOT of other PPAs which create failing builds on a regular schedule. [17:05] I didn't realize there was a launchpad channel [17:05] EvanCarroll: to be clear, not s/ubuntu/launchpad/. tomreyn's point is that PPAs are not part of ubuntu [17:06] tomreyn: that's not the right description of the domain, there are a lot of other ppas which are offiical with an upstream project or where at one point in time but are entirely unmaintained now? [17:06] this isn't a failure to build this is problem for the past year that's confusing 83,000+ people. [17:07] just going by askubuntu view counts. [17:08] EvanCarroll: declared official by an upstream does not make it part of supported ubuntu [17:08] no one said it was officially support by anything [17:08] it's clearly not /supported/ at all. [17:08] it's not against launchpad policy for someone to have a ppa that produces broken / out of date contents; it's also not something that the Ubuntu community can fix by fiat if someone is giving directions to a bad ppa. This is a social problem [17:08] sure, upstream might decide to support some PPA, but that's nothing ubuntu folks could be held responsible for [17:08] the problem is the launchpad confuses people and makes them /think/ it is. [17:09] if there is documentation on any official Ubuntu sites directing users to the ppa, that's something we could fix [17:09] ok, so that's the problem then the launchpad policy supports confusing users. [17:09] that's not a good policy. [17:09] "You can update your system with unsupported packages from this untrusted PPA by adding ppa:videolan/master-daily to your system's Software Sources. (Read about installing) " === slangase` is now known as slangasek [17:09] it's not the packages. [17:09] it's the page. [17:09] this sentence i just quoted is pronted on every PPA page [17:09] *printed [17:10] EvanCarroll: sorry, what other policy would you expect? Launchpad is a platform; do you want the Launchpad team to be deciding whose ppas are supported "well enough"? [17:10] EvanCarroll: what page are you referring to? [17:10] if people cannot read or decide not to read they will probbalky make a lot fo bad choices in life [17:12] fwiw, I don't expect most users to ever browse to the ppa in a web browser before enabling it, but here is the banner you get for this particular ppa in add-apt-repository: http://paste.ubuntu.com/25291536/ [17:13] slangasek: I would expect the policy of "repositories that are unmaintained and cease to function with all supported version of Ubuntu will be delisted." [17:13] slangasek: good question though. [17:13] what is 'maintained'? 'cease to function'? delisted by whom? [17:13] The issue here is not "there is a ppa". The issue is "someone thought it was a good idea to tell other people to use a ppa that says right on its cover that it's only for testing purposes" [17:13] cease to function = cease to build. [17:14] unmatained = no intention to maintan, not working for any use case. [17:14] Delisted by whom = delisted by launchpad.net [17:14] why not ask upstream to delete the ppa? [17:15] last successful build in that ppa was 17 hours ago for xenial (https://launchpad.net/~videolan/+archive/ubuntu/master-daily/+builds?build_text=&build_state=all) [17:15] slangasek: I have. Multiple. Multiple times. [17:15] https://launchpad.net/~videolan/+contactuser [17:16] no one responds slangasek where do you see that? [17:16] EvanCarroll: ok. then you certainly can ask the Launchpad Team to intervene; I'm just not sure why they would [17:16] slangasek: that's the xenial build start that succeeded, the build fails. [17:18] actually wait, I'm looking into this. I didn't think it was still building on Xenial [17:19] EvanCarroll: ah, heh; I've never noticed before that the "build start" shows as a different record, ahwell [17:20] Yea, I think this is just build start record. [17:20] ok, last successful build was precisely a year ago :) https://launchpad.net/~videolan/+archive/ubuntu/master-daily/+builds?build_text=vlc&build_state=built [17:20] slangasek: there ya go [17:20] that's about when the confusion started. [17:21] that's certainly an argument that it should be sunset. Maybe the launchpad team would care because it wastes build resources? :) [17:21] I would hope the confusion it's causing is more of an issue. But, at this point whatever. [17:22] It's a very common question people want vlc 3.x, and they the ppa just isn't there and the snap is broken and doesn't do h.265, and building vlc isn't exactly a walk in the park [17:22] EvanCarroll: so are you following up with the Launchpad team about this? again, Ubuntu has no authority here [17:23] "and the snap is broken"> oh? that's a different matter entirely; I certainly had the impression the snap was working well [17:24] slangasek: yes, I'm in the wrong channel I'll admit [17:24] slangasek: the snap is pretty borked too. I don't know where to view the change logs on that or the build options, but the meta data is wrong on the snap [17:27] `snap info vlc` should tell me the git/version not just "daily" https://askubuntu.com/a/915164/29097 I don't think the snap is being updated either though [17:27] it's certainly not updated daily [17:27] win 3 [17:29] EvanCarroll: that's a choice made by the snap's owner === JanC_ is now known as JanC [18:57] @pilot out === udevbot changed the topic of #ubuntu-devel to: Zesty Released | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-zesty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots: [21:54] Bah, creating build chroots still failing for me.