=== EvilMTeck is now known as MTecknology | ||
kaustavdm | Hi, a package I uploaded to my ppa has been successfully built, but it is pending publishing for the last one hour. Can anyone tell me why? Please check https://launchpad.net/~kaustav-dasmodak/+archive/kido/+packages | 08:14 |
---|---|---|
wgrant | kaustavdm: Publication stops once a week for 1.5-2 hours, starting an hour ago. | 08:16 |
wgrant | OK then. | 08:16 |
StevenK | Hah | 08:17 |
=== Naresh` is now known as Naresh | ||
evaluate | Hello. | 09:32 |
maxb | hello | 09:32 |
evaluate | Is there a way I can get more permissions on launchpad for a specific package? I for example can't mark a bug as 'Won't fix'... | 09:33 |
wgrant | evaluate: You'll need to apply to join https://launchpad.net/~ubuntu-bugcontrol | 09:33 |
wgrant | There are no package-specific bug permissions at this time. | 09:33 |
evaluate | Ohh. | 09:33 |
evaluate | Is there some kind of process that I need to go through (I mean beside sending that application mail that is mentioned there), or are my chances pretty good if I mention that I am the upstream of a specific package and am only interested in handling the bugs for that package? | 09:35 |
wgrant | I haven't been through the application process for around 5 years, so I'm not too sure what it's like these days. | 09:36 |
evaluate | wgrant, I see. | 09:37 |
jfi | wgrant, Hello! getDailyDownloadTotals always returns the full list or a splitting might occurs at some limit? | 09:39 |
wgrant | jfi: It does not do batching. | 09:40 |
wgrant | It will always return the whole range that you request. | 09:40 |
wgrant | Or time out :) | 09:40 |
jfi | wgrant, ok:) | 09:40 |
jfi | wgrant, I never see a timeout, what is the consequence? http timeout or a reply with some 5xx code? | 09:42 |
wgrant | An HTTP 503 if you request too much data. | 09:43 |
wgrant | But these queries should generally be pretty fast. | 09:43 |
jfi | wgrant, yes, it is very fast, I have very impressed by the LP performance | 09:43 |
jfi | *I am | 09:43 |
Ampelbein | evaluate: regarding bug control as upstream: "If you are an upstream developer or bug triager for an upstream project contact Jorge Castro" (From https://wiki.ubuntu.com/UbuntuBugControl) | 09:44 |
evaluate | Ampelbein, I'm going through that wiki right now. Thank you! | 09:44 |
wgrant | jfi: We're getting faster, but we still have a long way to go :( | 09:45 |
=== yofel_ is now known as yofel | ||
gour | morning | 11:16 |
gour | no-wiki is one of the things which makes me tied to fossil...is support for wiki on the radar of LP devs? | 11:18 |
* gour is reading https://bugs.launchpad.net/launchpad/+bug/240067 thread...maybe the answer is there | 11:27 | |
ubot5 | Ubuntu bug 240067 in Launchpad itself "Launchpad projects need wikis" [Low,In progress] | 11:27 |
gour | some baby steps are there... | 11:37 |
exarkun | https://code.launchpad.net/~divmod-dev/divmod.org/trunk has been "Updating branch ..." for like 16 hours | 14:13 |
maxb | Sounds like you need someone who can actually look at the branch scanner logs on the server. It's probably best to file a question | 14:15 |
exarkun | okay | 14:15 |
exarkun | a question on launchpad? | 14:15 |
maxb | yes | 14:15 |
exarkun | thanks, asked (<https://answers.launchpad.net/launchpad/+question/158547>). | 14:17 |
=== tubadaz_ is now known as tubadaz | ||
=== tubadaz_ is now known as tubadaz | ||
respond | https://launchpad.net/viewmail-disabled used to be called https://launchpad.net/viewmail so how do I find out how it got renamed? | 17:54 |
nigelb | respond: you could ask on Monday when the launchpad staff are around | 17:59 |
respond | nigelb: thank you. Actually, probably what happened is specific to the viewmail package so I'll post a question to the current owner. | 18:00 |
nigelb | respond: ah, I assumed you were the owner! Yes, that works too :) | 18:00 |
respond | nigelb: I created a branch off of viewmail back in 2008. when I tried to view my branch, it showed up as viewmail-disabled instead of just viewmail. scouring the FAQ's on launchpad gave no indication of how that happened, so I'm stuck until the owner can get back to my inquiry I posted to him/her a few minutes ago. | 18:15 |
nigelb | respond: hrm, true. I don't find anything on quick googling | 18:16 |
respond | nigelb: yup. tried that too. :) | 18:16 |
respond | nigelb: thanks for your help though! | 18:16 |
nigelb | respond: :) | 18:16 |
maxb | respond: I'm not Launchpad staff, but I'd guess it was superseded by https://launchpad.net/vm | 18:32 |
maxb | respond: https://answers.launchpad.net/launchpad/+question/104604 | 18:38 |
tgm4883 | How is the amount of space calculated on a PPA? Apparently the Mythbuntu team is currently at 3.3GB of 3.0 GB on one of our PPA's, despite only having a handful of pacackages up there and me deleting some old ones that should not be available anymore | 21:56 |
tgm4883 | Is the repository size per PPA or per Team/User? | 22:04 |
micahg | tgm4883: per PPA, the actual deletion can take a little bit to happen | 22:16 |
tgm4883 | micahg, hmm ok. I've computed the size of each binary that the PPA says it has, which is about 1.5GB worth. Far less than the 3.3GB that it says it's at | 22:18 |
tgm4883 | I only deleted a few packages yesterday, no nearly 1.8GB worth | 22:18 |
micahg | tgm4883: which PPA is it? | 22:18 |
tgm4883 | https://launchpad.net/~mythbuntu/+archive/0.24/+packages | 22:18 |
tgm4883 | I'm checking our other PPA's now | 22:18 |
micahg | tgm4883: it would be 1GB of binary packages from before... | 22:19 |
tgm4883 | from before? | 22:20 |
tgm4883 | also, https://launchpad.net/~mythbuntu/+archive/0.25/+packages seems to be on it's way to the same issue. 2.5GB right now | 22:21 |
micahg | tgm4883: http://ppa.launchpad.net/mythbuntu/0.24/ubuntu/pool/main/m/mythtv/, looks fine, just takes a bit to delete | 22:22 |
micahg | you have several old versions | 22:22 |
tgm4883 | micahg, ok, how often do the old builds get purged? | 22:23 |
tgm4883 | Because the ones I had deleted yesterday were REALLY old | 22:23 |
micahg | tgm4883: I thought it was once a day, bit you'll have to wait for someone else for an official answer | 22:23 |
micahg | s/bit/but/ | 22:23 |
tgm4883 | micahg, that sounds about right. I'm looking though these packages and I think I may see why some of them were left over | 22:24 |
tgm4883 | not sure if it's a bug or not, but if the source package no longer builds a certain binary the binary seems to stay forever | 22:25 |
tgm4883 | which is why we have some builds from Nov apparently on this PPA that builds daily | 22:25 |
micahg | tgm4883: no, you should be able to delete it in the delete-packages page | 22:26 |
micahg | tgm4883: there is no NBS cleanup in PPAs | 22:26 |
tgm4883 | micahg, yea I did it manually yesterday. But it's apparently not automatic | 22:26 |
tgm4883 | well since the PPA has let us push and has built yesterdays changes, I'll just watch it and see if it returns to normal usage | 22:27 |
tgm4883 | thanks micahg | 22:27 |
micahg | tgm4883: just because it's not being built, doesn't mean that it wasn't built against | 22:27 |
tgm4883 | true | 22:28 |
tgm4883 | is there something we can do in debian/control to signal the package no longer exists? | 22:28 |
tgm4883 | iirc we already have conflicts/replaces set up | 22:28 |
tgm4883 | or doe soyuz not care about that in regards to removing old packages? | 22:29 |
micahg | tgm4883: there is no automatic package removal AFAIK | 22:30 |
micahg | tgm4883: in the primary archive, the archive admin manually remove stuff w/a helper script | 22:31 |
tgm4883 | But there is some form of replacing old packages with the new ones right? | 22:31 |
tgm4883 | otherwise we would overshoot our allotted space in 2 days | 22:31 |
micahg | tgm4883: you could use a transitional package | 22:32 |
tgm4883 | micahg, hmm, yea I think transitional packages make sense | 22:32 |
lifeless | tgm4883: are you talking about ppa disk utilisation? | 22:32 |
* micahg lets lifeless take over :) | 22:33 | |
tgm4883 | lifeless, yea | 22:33 |
lifeless | ok | 22:33 |
lifeless | so - stuff with the same source package name gets freed automatically | 22:33 |
tgm4883 | lifeless, I was just doing some PPA stuff and noticed we were at 98% yesterday | 22:33 |
lifeless | its not synchronised with the upload that replaces it | 22:33 |
lifeless | and its *per series* (so natty/karmic etc) | 22:33 |
tgm4883 | all of our stuff has the same source package name | 22:34 |
lifeless | so if you do the following you need to manually cleanup: | 22:34 |
lifeless | - switch from e.g. hardy to e.g. lucid you need to delete whats in hardy by hand | 22:34 |
lifeless | - change source package name you need to delete the old source and binary packages | 22:34 |
tgm4883 | I don't think either of those would effect us | 22:35 |
lifeless | ok, let me have a peek then | 22:36 |
lifeless | https://launchpad.net/~mythbuntu/+archive/0.25/+packages | 22:36 |
lifeless | 3 source packages (528.5 MiB) | 22:36 |
lifeless | 145 binary packages (2.0 GiB) | 22:37 |
tgm4883 | lifeless, what may cause an issue is we have a source package (mythtv) that builds multiple binary packages (main program plus plugin packages) | 22:37 |
lifeless | You also have dbg packages there | 22:37 |
lifeless | these tend to be quite big | 22:37 |
tgm4883 | if upstream removes one of the plugins, that obviously no longer gets built. But what does that mean for old source/binary packages? | 22:37 |
lifeless | should be automatic | 22:38 |
tgm4883 | lifeless, the 0.25 ppa is quite newish, take a look at https://launchpad.net/~mythbuntu/+archive/0.24/+packages | 22:38 |
lifeless | you can ask for more space too | 22:38 |
lifeless | 180MB per source package is quite large though ! | 22:38 |
tgm4883 | lifeless, which we have :) | 22:39 |
tgm4883 | yea it's a large source | 22:39 |
tgm4883 | all of mythtv, mythplugins, myththemes | 22:39 |
lifeless | mythtv-dbg_0.24.1+fixes.20110522.347cd24-0ubuntu0mythbuntu4_amd64.deb (53.6 MiB) | 22:40 |
tgm4883 | I think in the next 24 hours it should clean some of itself up and return to normal size (2 - 2.5GB) | 22:40 |
lifeless | so 100MB per build (i386 + amd64) on debug packages | 22:40 |
tgm4883 | lifeless, right, I pulled all of the packages into a spreadsheet and it only computed to 1.4GB, add source packages and I'm still under 2GB | 22:41 |
tgm4883 | I think it might just be cleanup. I think we had to do an extra build yesterday to fix an issue | 22:41 |
lifeless | hmm | 22:41 |
lifeless | there is a separate pass that happens | 22:41 |
lifeless | I forget the details | 22:41 |
lifeless | so yeah, give it 24 | 22:42 |
tgm4883 | lifeless, will do. I'll check back tomorrow if it doesn't change | 22:42 |
tgm4883 | I think it will though | 22:42 |
tgm4883 | thanks lifeless and micahg | 22:42 |
=== _thumper_ is now known as thumper | ||
ScottK | https://launchpad.net/~ubuntu.2012 seems like an unreasonably deceptive team name. | 23:08 |
ScottK | Is there a policy about such things? | 23:08 |
ScottK | https://launchpad.net/~india.launchpad.team too. | 23:11 |
lifeless | https://launchpad.net/~ubuntu-linugz | 23:12 |
persia | I don't believe there is such a policy. | 23:12 |
lifeless | there isn't a firm policy | 23:13 |
lifeless | however we do sort this sort of thing out | 23:13 |
lifeless | please make a question on answers.launchpad.net/launchpad and the CHR can do it | 23:13 |
persia | CHR? | 23:13 |
lifeless | community help rotation | 23:13 |
ScottK | OK. | 23:15 |
ScottK | Done | 23:16 |
lifeless | thanks | 23:19 |
lifeless | heh https://launchpad.net/~deadubuntuteam | 23:21 |
ajmitch | ubuntu for zombies? | 23:21 |
persia | It's important to respect diversity. | 23:22 |
ajmitch | sorry, ubuntu for the vitally-challenged | 23:22 |
lifeless | *snort* | 23:22 |
lifeless | persia: hey, when is the next asiapac mb meeting? | 23:23 |
lifeless | I am persistently confused | 23:23 |
persia | lifeless, Given that I failed to send an announcement last week, the 31st. | 23:23 |
lifeless | k | 23:23 |
cjohnston | lifeless: are you able to make a project a project group? | 23:53 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!