[01:21] New bug: #215448 in malone "Should strip gpg signatures for attachments" [Undecided,New] https://launchpad.net/bugs/215448 [01:21] Ooo, yeah. [01:57] kiko: hey... how do I keep a package in a PPA from building for lpia? [01:57] kiko: I've got one with mono depends which don't seem to be in gutsy for lpia, and I'd love to mark it as "don't bother" [01:58] mtaylor: restrict the control file Architecture field [01:58] cprov-out: isn't that just for the binary packages? [01:59] or the binary sections, rather? [02:00] mtaylor: well, it controls in which architecture you want to build a given binary package, if instead of 'any' you specify 'i386 amd64' it won't build in lpia [02:00] cprov-out: right... but I'm erroring out in missing build depends... [02:01] so I'm trying to prevent it from even loading up a vm and starting... [02:02] mtaylor: sorry, I don't understand what you mean. loading where ? [02:02] a PPA [02:02] in a PPA [02:02] cprov-out: so, I upload the source package for gutsy [02:03] and it tries to build it against i386 amd64 and lpia, but I konw that the lpia build is going to fail for gutsy - and that it's going to fail in the build-dep step [02:03] and I don't really care about that - so I'd like to just skip it [02:03] mtaylor, what cprov-out said -- update the control file to not build it on that arch. [02:04] do I need to do the architecture field of all of the binary sections? [02:04] mtaylor: okay, so far ... upload a new source that won't build in lpia, change the Architecture in the control file as I've suggested. [02:04] yes -- one for each binary, mt [02:04] mtaylor, [02:04] ok === kiko is now known as kiko-zzz [02:05] cprov-out, now -- to to bed. :) [02:05] * kiko-zzz goes too [02:05] mtaylor: s/any/i386 amd64 (leave the 'all' alone) [02:05] kiko-zzz: not yet, I have a review to reply, but g'night :) [02:06] sweet. thanks guys [02:58] My emails to ubuntu-devel are still getting put in the moderation queue despite me being in the Ubuntu Developer group. Do I have to use a specific address, or can I use any of my confirmed launchpad emails? [02:58] Or is it because I have to sign my emails? [03:00] YokoZar: ubuntu-devel is not managed by launchpad [03:01] so you need to subscribe any emails you want to post as at https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel [03:01] jamesh: I was hoping someone would know how the scripts interact, because it somehow uses the ubuntu devel group as a validation [03:02] which scripts are you referring to? [03:02] Or maybe I'm mistaken and new Ubuntu devs have to be manually added to the mailing list by the admin [03:03] I just assumed there was some sort of "ask launchpad if this email is an ubuntu dev, if not put in moderation queue" type script going on [03:03] you need to subscribe to the mailing list yourself [03:03] see the URL I posted above [03:03] I'm already subscribed though, since before I was a dev [03:03] I'll try removing/redoing it, maybe that'll refresh it [03:04] YokoZar: we do have mailing list support in Launchpad now, but the existing Ubuntu mailing lists haven't been migrated to that infrastructure [03:04] that will likely happen in the future [03:04] Thanks [03:04] once that's done, you'll be able to post with any email registered to your LP account, and you'll only get first post moderation once for all lists [03:04] rather than once for each list [03:05] (in cases where you aren't a list member, that is) [03:14] I think I figured out the problem - I registered a long time ago with an address that now forwards to my current one; since I was sending from my new address, it thought me not a subscriber [03:14] Thanks for your help :) [03:19] YokoZar: you can subscribe multiple addresses to the list, and set them as no email if you want [03:19] that way you can post from multiple addresses but receive email on only one [04:08] good night people === asac_ is now known as asac [07:19] mdke: ping [07:19] jtv: (In case I'm not around at the moment, please provide a bit of information about what you want and I will respond when I get back) [07:30] morning [08:00] Gooooooooooooooooooood morning Launchpadders! [08:04] morning. pshaw. [08:04] mpt: changing hemispheres has you all topsy turvy! [08:05] next thing you know, you'll be saying that the sun rises in the west and eggs should be cracked with a fork! [08:05] Eggs should be cracked with a frying pan. [08:08] morning all [08:09] * mdke winces at mention of eggs [08:09] jtv: pong; saw your email, and am pretty excited :) [08:09] sounds awesome [08:12] Hello [08:12] a question about SVN imports [08:13] does that mean that I should continue using the SVN or the BZR ? [08:13] because I see a status called "last sync" [08:13] AnAnt: it depends [08:13] thumper: depends on what ? [08:14] AnAnt: if you are switching to bzr then just start using bzr [08:14] AnAnt: if you want to keep committing to svn then don't [08:16] sorry, I was lagging [08:17] thumper: depends on what ? [08:17] [19:14] AnAnt: if you are switching to bzr then just start using bzr [08:17] [19:14] AnAnt: if you want to keep committing to svn then don't [08:18] thumper: ok, I see that the bzr is in ~vcs.imports/ how do I change that to be in my team dir ? [08:18] AnAnt: branch from it and push to LP [08:18] mdke: cool, just let me know what you need. [08:19] thumper: you mean: bzr branch http://<~vcs.imports URL> , then bzr push svn+ssh:// ? [08:20] jtv: basically I have been importing po files into the ubuntu-doc branch, and correcting some of them by amending a string and the po-revision-date. I've got a list of them in a file called broken_translations in the branch and need to upload those po files to LP at ubuntu/hardy/+source/ubuntu-docs/templates [08:20] AnAnt: if you are using a recent bzr (1.2 or later) then use 'bzr launchpad-login' to identify yourself [08:21] AnAnt: then you can go 'bzr branch lp:~vcs-imports/project/name [08:21] AnAnt: and 'bzr push lp:~team/project/name' [08:21] AnAnt: somewhat smaller [08:21] ok [08:21] I'm looking to change the ui shortly (RSN) [08:23] how do I tell bzr about my account ? [08:23] I get: No Launchpad user ID configured. [08:25] thumper: how do I tell bzr about my account ? [08:26] AnAnt: did you see the bit about "bzr launchpad-login" [08:26] mdke: argh, the scripts don't support sourcepackage uploads yet. Never mind. Have a URL to that broken_translations file for me? [08:26] ah, bzr launchpad-login [08:27] * mpt gets enraged by "There is 1 error" [08:27] I fixed the error, but Launchpad keeps unfixing it [08:28] jtv: hang on a tic. (to be honest, I don't really know why we use LP source package translations rather than project translations, it's all a bit confused) [08:29] mdke: saves an import step, I guess. Shortens your feedback cycle. [08:30] jtv: can LP import translations automatically from a bzr branch yet? [08:30] or is that not feasible? [08:33] mdke: that's still a long way off. [08:33] thanks fellows ! [08:34] jtv: ah. anyway, we don't really use the automatic import stuff; since all our translations come from LP anyway [08:35] it's no big deal to upload pot files [08:35] mdke: the file you're digging up links to the updated PO files, right? [08:35] jtv: not really, it just lists them. what do you mean by links? [08:36] mdke: just so I can unambiguously find the right ones. [08:36] jtv: yes, that will be ok. I'm just waiting for a commit to go through [08:36] ok [08:37] jtv: but at the moment I haven't finished correcting all the translations, it would just be to show you how things are set up, for now. I expect that all the translations will be fixed by the weekend [08:38] mdke: okay, if you send them to me now I can start scripting. [08:41] mdke: the problem was that you don't have upload privileges, right? [08:41] mdke: going for a post-lunch walk first though. :-) [08:43] jtv: yes; I had upload privileges for some languages but not others [08:43] damn this commit is taking a long time [08:47] jtv: ok, my commit hasn't finished and I need to go to work, so i'll just tell you. In the https://code.edge.launchpad.net/~ubuntu-core-doc/ubuntu-doc/ubuntu-hardy branch, it is at ubuntu/broken_translations, and the templates referred to are all at ubuntu/$templatename [08:47] jtv: (except for one, serverguide, which is at generic/serverguide) [08:48] jtv: for the next release I've simplified the branch structure a lot so it is more straightforward [08:48] mdke: ok, thanks. [08:48] jtv: the broken translations file has some asterisks in it, which are just for my benefit so can see which translations I fixed already; I'll take them out when everything is fixed [08:49] jtv: thanks to you :) [08:50] mdke: as I like to say, thank me when it's done. :-) [08:50] i will :D [08:50] bye [08:50] bye [08:51] New bug: #215537 in malone "Correcting unknown package by choosing "I don't know" gives further mysterious error" [Undecided,New] https://launchpad.net/bugs/215537 [08:52] Hm, I think that's a dupe. [08:54] Indeed, bug #189522. [08:54] Launchpad bug 189522 in malone ""I don't know" refused when reporting a bug" [Undecided,Incomplete] https://launchpad.net/bugs/189522 [08:54] mpt: You even replied to that bug yourself. [08:55] Fujitsu, I saw that report when reporting the new one [08:55] Is the new one different in some way? [08:55] 189522 doesn't have enough information for me to tell whether it's the same bug [08:56] but it seems unlikely that it is [08:57] 189522's reporter complains that he can't choose "I don't know". You do too in 215537. Is it particularly likely that it's broken in two ways? [08:57] In David's case he (apparently) chose "I don't know" to start with, whereas I chose a package name to start with. [08:57] Ah. So it could well be. [08:58] * Fujitsu returns to his cave. [09:00] Bug 102216 is in a similar predicament -- I can't reproduce it, it might be the same bug as the one I just reported, but it seems unlikely. [09:00] Launchpad bug 102216 in ubuntu "[malone] Still finds an error when chosen dont know for package name" [Undecided,Invalid] https://launchpad.net/bugs/102216 === mwhudson_ is now known as mwhudson === mwhudson_ is now known as mwhudson [10:06] New bug: #215557 in launchpad-buildd "open-iscsi fails to install" [Undecided,Invalid] https://launchpad.net/bugs/215557 [10:16] https://edge.launchpad.net/ubuntu/+mirror/ftp.dei.uc.pt-archive2 -> could some LP admin remove my entry that is duplicate? [10:17] <\sh> guys, when is the publisher for ppa running? every XX mins? === mtaylor is now known as mtaylor|away [10:19] \sh: */20 [10:20] <\sh> Fujitsu, thx :) [10:35] New bug: #215575 in launchpad "xorg-driver-fglrx cannot be selected as package to report bug about" [Undecided,New] https://launchpad.net/bugs/215575 [11:58] Quick question. Does launchpad have any kind of web service or API? === thekorn_ is now known as thekorn [12:21] Hi. Is there a way to send bug e-mails to an arbitrary e-mail address? [12:21] I want to send bug mails to a list. (And I found out too late that launchpad itself has lists now.) === mrevell is now known as mrevell-luncheon [12:51] New bug: #215628 in soyuz "Require a script to unembargo private packages" [High,In progress] https://launchpad.net/bugs/215628 [13:13] hi === mrevell-luncheon is now known as mrevell [13:47] New bug: #215661 in launchpad "PPA should allow multiple versions of a package to be present" [Undecided,New] https://launchpad.net/bugs/215661 [13:47] New bug: #215665 in malone "impossible to install hardy in LVM" [Undecided,New] https://launchpad.net/bugs/215665 === vednis is now known as mars === matsubara_ is now known as matsubara [14:32] New bug: #137440 in launchpad-documentation "Launchpad application tours don't close the deal" [Low,Confirmed] https://launchpad.net/bugs/137440 === fdd_0 is now known as fdd === jdahlin_ is now known as jdahlin [15:21] * Hobbsee stabs packages that dont' built. [15:21] er, build [15:23] i am having a small problem with PPA [15:23] i made the mistake of deleting a package from there [15:23] shoot [15:23] now i have files in there that do not allow me to reupload the package [15:23] and i can't find a way to make it rebuild the package [15:24] the package was broken, but at least it was apt-get installable for some value of apt-get installable [15:24] upload a higher version? [15:25] automatically generated stuff so making it create something a version higher is a bit problematic [15:25] because the stuff all autogenerates again, each time? [15:26] no, because the code that would detect what "debian" versions are available is not there ;) [15:26] so if the package i am generating a deb from is the same - i will get the same debian package version [15:27] sounds like the package is broken. [15:27] which package? [15:28] your package [15:28] the idea is this - i take a python egg, run it through a script, and get all the parts needed to upload it to PPA [15:28] like .changes .dsc the diff and the tarball [15:28] automatically [15:29] as that is the only way i can generate the deb at the moment [15:29] i can't really create zope.i18n_3.4.0-2 [15:29] and as 3.4.0-1 was uploaded to launchpad [15:29] and then deleted [15:29] i can't upload 3.4.0-1 again [15:29] why? [15:30] because ppa does not allow me that [15:30] it deleted the deb [15:30] if you wait for the cron job, you can actually upload it again. [15:30] oh, so this is not true delete. [15:30] cprov-out: might be able to help you do a true delete [15:31] i don't know what a true delete is ... [15:31] stuff that deletes both binary and source [15:31] i see [15:31] only admins can do it? [15:31] apparnetly so [15:32] * Hobbsee does not work on launchpad [15:34] ignas: is it really helpful to have created a build system where you cannot do a rebuild, for any reason? [15:34] Launchpad is a very cool tool. [15:34] i can do a rebuild, problem is that if I fix a package, i can't upload the fixed package if it's already there [15:35] unless i do a "new release" [15:35] as in - debian release [15:35] ignas: the disk-remover is running each 30 minutes are you sure that the files still on disk. Point me to your PPA. [15:36] cprov-out: https://edge.launchpad.net/~schooltool-owners/+archive?field.name_filter=zope.i18n&field.status_filter=any [15:36] zope.i18n 3.4.0 is the problematic package [15:46] fricking launchpad. [15:46] cprov-out: please investigate OOPS-832EA102 [15:47] and OOPS-832EA103 [15:48] come on, this was working for gutsy... [15:49] it shouldn't die around hardy freeze time. [15:49] ignas: the files you've mentioned are not in pool since 2,5 hours ago, you should be able to re-upload the same version. [15:50] i see, i saw them listed when i expanded package description so i assumed they still are in there [15:50] got "Already uploaded to ppa.launchpad.net" [15:50] "Doing nothing for python-zope.i18n_3.4.0-1_source.changes" [15:51] ignas: use dput -f [15:51] ignas: :) dput is silly [15:51] * Hobbsee tries the workaround [15:51] cprov-out: thanks, that fixed it [15:51] * Hobbsee stabs. [15:52] workaround doesn't work. [15:52] ignas: too early ... wait some minutes to thank us. [15:52] :) [15:52] no way to do release management work on launchpad any more. Not happy. Please fix. Thanks in advance. [15:54] Hobbsee: let's check your oops. You, impatient child :P [15:54] cprov-out: it's 1am. I'm not so patient when i want the stuff to build before i go to bed. === mtaylor is now known as mtaylor|to-home [15:55] cprov-out: and i don't think slangasek suddenly wants to do all the universe stuff, too. [15:55] Hobbsee: it was a timeout, did you try again ? [15:55] cprov-out: 3 times on edge, 2 on normal LP. [15:56] no dice. [15:59] hiya mthaddon [15:59] hey Hobbsee [16:03] cprov-out: can you ping me when you get it fixed please? [16:03] * Hobbsee heads to bed [16:04] Hobbsee: okay, good night. [16:04] thanks [16:06] Rejected: [16:06] The source bip - 0.7.2-0ubuntu1 is already accepted in ubuntu/hardy and you cannot upload the same version within the same distribution. You have to modify the source version and re-upload. [16:06] ? [16:06] i deleted it. [16:07] * Hobbsee shrugs, will test it in other ways [16:15] New bug: #215738 in soyuz "The message on emails for upload rejections is misleading" [Medium,In progress] https://launchpad.net/bugs/215738 [16:18] cprov-out: hmm, indeed - apparently no thanks ;) even though i have reuploaded the package with -f, launchpad is not trying to rebuilt it, because it is "deleted" [16:47] cprov-out: launchpad rejected my changes because - "the version is the same" [16:51] ignas, increment the version and try again. [16:51] kiko: i can't [16:51] kiko: which is why i tried to remove the old package [16:51] "delete" it [16:51] and upload it again [16:52] it deleted the deb [16:52] ignas, you can't? fingers cramped? :) [16:52] kiko: i can't - it would take long, and i want a working deb back [16:52] ignas: does't really matter if you've deleted the source, soyuz check if it was ever uploaded to that PPA. [16:52] ignas: so, you will never be able to reupload the same version. [16:52] kiko: so i was thinking maybe there is a way to at least "rebuild" the deb again [16:53] if i can't reupload the same version [16:53] hmmm [16:53] until i get the version part resolved [16:53] because at the moment i am stuck [16:53] old version deleted, new version - not there yet [16:53] ignas: why did you remove it ? [16:53] cprov-out: because i assumed that if i will remove it i will be able to upload it back [16:53] again [16:53] because well - it won't be in there [16:55] I have to go not, but I'm sure someone else will explain to you why it's we can't allow you to upload the same version of a package with a different content. [16:55] * cprov-out goes [16:55] emm, so unless i will manage to come up with a new version I will not have anything installable in PPA? [16:56] ignas, you can just append -rev1 to the existing version number. [16:57] kiko: packages are generated automatically [16:57] kiko: i have written only parts of that system, so i would have to find out how it works and fix it [16:57] kiko: which i will do, but it will take time [16:57] ignas, you can change them after generated, this once. [16:57] kiko: i have no idea how debian packages are generated at the moment [16:58] ignas, I'll let you read about that -- but it's not very complicated, just pick up the source package you generated and update the version [16:58] maybe LaserJock or Fujitsu might have a hint :) [16:59] kiko: so - why is the delete button in there at all? [16:59] kiko: if it only "hides" actually [17:00] and if it only "hides", why isn't there "unhide" button [17:01] it does delete the package. [17:01] it just doesn't allow you to reuse the version. [17:02] i see [17:03] ok, it makes sense, though having an undelete or "rebuild" button would be kind of nice, because - the version is locked to the particular state of the package anyway [17:03] if it is to "not allow 2 different packages under the same name + version in the world" [17:03] that I could agree with; however, if you delete and upload a new version, all bets are off. [17:03] thing, then it would kind of make sense to allow people to reupload the same package under the same version number [17:04] if you want to file a bug about undeleting deleted packages that haven't been superseded yet, we can do that [17:04] i mean - you can just keep md5/sha or something like that [17:04] kiko: if such a thing would make sense for anyone else except for me at this specific moment... === salgado is now known as salgado-lunch [17:22] hmm, i have dsc file, changes file, orig.tar.gz and diff.gz, how do i get the same sandbox i would get by using "apt-get source some-package" from these? [17:40] Can someone point me to the link where I can request an svn project be converted to bzr? [17:40] ...and added to launchpad... === matsubara is now known as matsubara-lunch [17:44] <_MMA_> I don't know if this is a Launchpad or Bazaar question. Is there a way to keep specific files automatically synced between branches? === salgado-lunch is now known as salgado [18:07] New bug: #215798 in launchpad-bazaar "Register branch page should make it clear registration is not pre-requisite for working on a project" [Medium,New] https://launchpad.net/bugs/215798 === matsubara-lunch is now known as matsubara [18:29] Hi! I need some help with branch merging... I am unexperienced user of bazaar. Ok I have this branch https://code.launchpad.net/~sque/liboonet/spec2-dev and I want to merge it at this https://code.launchpad.net/~sque/liboonet/trunk. I clicked on propose for merge, it changed on "work in progress" statues, I then added to the merge queue [18:30] and now? what? [18:30] how the REAL merging happens? I have given all the needed info [18:32] sque: someone with the appropriate permission need to merge your branch into the other branch [18:33] I am the owner of both branches [18:33] and push the changes to launchpad [18:34] matsubara the "propose for merging" and "add in merge queue" are just informational actions? [18:34] I have to pull both branches localy, merge one to the other and push it back? [18:34] sque: AFAIK, yes [18:36] you just need to pull the target branch locally. [18:36] brz pull target-branch [18:36] cd target-branch [18:36] I have done that... [18:36] and then? [18:36] bzr merge url-of-proposed-merge-branch [18:36] bzr commit -m "description of merged changes" [18:36] bzr push [18:37] I think that would do it [18:37] so this... does nothing! https://code.launchpad.net/~sque/liboonet/trunk/+merge-queue [18:39] well, nothing is unfair. Imagine for instance how that merge-queue helps projects which get lots of contributions. It's a single place where you can see all the proposed patches to include in mainline. [18:39] I think that at some point this might be automated though. [18:39] sque: you might want to ask thumper about it when he's around. [18:40] or maybe abentley [18:40] The way it is presented seems more like a real action not just an organizational place [18:41] and that got confused me. If I knew from the 1st place that it was just informational I wouldn't use it on a project of 1 developer :P [18:41] I would just merge the code localy and just commit it [18:42] anyway ty :) [18:42] sque: https://blueprints.edge.launchpad.net/launchpad-bazaar [18:43] sque: that's the list of specs the launchpad-bazaar team will be working on. check the branch-merge-bot one. it seems to be what you're asking for. [18:43] it was the first in the list that I clicked ;) [18:43] sque: so the merge-queue page is the first step on that direction [18:43] yes [18:44] and probably you will press something like "do it" and all the queue will be processed [18:44] nice :D [19:21] I just uploaded a package to my PPA which was denied. I believe I have fixed it but the same dput command tells me 'you already uploaded that one dummy' [19:21] Zelut: yeah, either remove the .upload file or use dput -f [19:24] hi! [19:24] LaserJock: ok, that works.. now I realize I don't think I fixed the problem after all :) [19:25] LaserJock: I build my package with bzr-buildpackage --native. That created .changes, .deb, .orig & .dsc. [19:25] some news on the LP mailing lists since #208431 got fixed? [19:25] my application is still stuck :/ [19:25] LaserJock: I dput the .changes (after signing) and its rejected for 'containing a binary package' [19:26] yeah [19:26] you need a source-only upload [19:26] LaserJock: ..but if I remove the .deb from the folder it complains that it can't find the .deb. [19:26] so look for a _source.changes file [19:26] rather than a _.changes [19:27] ...which I don't have. [19:27] could be you need to create one [19:28] can you tell I'm new at this :) [19:32] ok, I think I got it.. dput the _source.changes file.. lets see how this gets accepted. [19:33] it's got a much better chance :-) [19:33] I'll wrap my head around this one of these days. [19:36] ok, this is probably another simple one but this time I got: Signer has no upload rights at all to this distribution. [19:37] oops [19:37] you uploaded to Ubuntu [19:38] you were ------||----- close to being a MOTU there ;-) [19:38] i thought I'd try to squeeze it in there [19:38] so you just rand dput *_source.changes? [19:38] *ran [19:39] I did, and I'm using the .dput.conf as suggested here: https://help.launchpad.net/PPAQuickStart [19:39] yeah, the problem is the default is ubuntu [19:40] we've discussed a little about changing the global dput config to not default to ubuntu to avoid that kind of thing [19:40] so I should simple remove the /ubuntu/ on my incoming or..? [19:40] no [19:41] your .dput.cf file is fine [19:41] you just need to do dput my-ppa *_source.changes [19:41] where "my-ppa" is the name of the PPA in the .dput.cf you want to upload to [19:42] dput has a global config file in /etc/ that has an ubuntu section for developers to upload with [19:42] but it's set as the default [19:43] that makes sense [19:43] i wonder if its assumed people using PPAs already know this so it isn't mentioned on the LP link. [19:44] ie; if you're building your own PPA archive you *probably* already know the steps so the docs are lacking. [19:45] ok, tat one was accepted [19:45] thank you [19:47] well, it is in there [19:47] but probably not clear enough [19:47] Step 3: Upload signed sources only (no binaries), using [19:47] dput phototeam-ppa P_V_source.changes [19:48] so technically that has both the "You need to upload _source.changes" part and "dput *_source.changes" part [19:48] but it's not really as clear as it probably should be [21:20] New bug: #215913 in malone "filing bug report requires account" [Undecided,New] https://launchpad.net/bugs/215913 [21:56] New bug: #195013 in rosetta "Firefox 3 and xulrunner 1.9 needs translations" [Undecided,Confirmed] https://launchpad.net/bugs/195013 [21:58] hi [22:01] I have some problems with a PPA [22:01] The repository itself seems to be corrupted [22:02] https://launchpad.net/~awn-testing/+archive [22:03] If somenone have a good idea, I'm interesting :) [22:22] gilir, what do you mean by "corrupted"? I see you had some amd64 failures there [22:22] but other than that it looks ok to me [22:23] gilir, ah, I see. "Chroot problem" [22:24] kiko, do you know what causes the ppa builders to set the status as "Chroot problem"? [22:24] that's a new one for me [22:24] Rinchen people using the PPA have the same error when they do apt-get update [22:25] gilir, well your log states "E: Encountered a section with no Package: header" [22:26] do you have a depends in there by chance? [22:26] * Rinchen is not the PPA expert. :-) [22:27] Rinchen yes I build package with depends on packages on the PPA [22:27] but I can't see which package have this Section probelm [22:29] yeah the logs don't seem to indicate which dependency it might be...they just issue the error [22:31] unfortunately gilir I don't know enough to help you beyond this point. someone else here might though. If you don't get an answer, you can file a Question on LP or email the users list [22:31] Rinchen Ok thanks :) === Martinp24 is now known as Martinp23