[09:23] <lhtd> hey, do you known how can I check that the kernel is compatible with GPT guid support for partitions larger than 2To ?
[09:24] <alkisg> All linux kernels support gpt
[09:32] <lhtd> alkisg, this page says I might need to recompile the kernel https://www.cyberciti.biz/tips/fdisk-unable-to-create-partition-greater-2tb.html
[09:33] <alkisg> lhtd: fdisk doesn't support gpt; use gparted instead
[09:33] <lhtd> I have been having problems with the GPT partition table which gets corrupted everytime I reboot
[09:33] <lhtd> alkisg, on it right now
[09:35] <lhtd> I need to reboot to update the kernel after formating my disk. brb
[09:38] <lhtd> b
[09:40] <lhtd> I cannot remove the MBR protective partition table
[09:41]  * lhtd rebooting to see if gparted did the thing
[09:44] <lhtd> Well.. GPT partition table is not corrupted anymore, but It will re-corrupt itself, it has been doing that for about 4 months. MBR protective partition table is still present.
[09:45] <alkisg> lhtd: is that an ssd?
[09:45] <lhtd> Is there a recurrent problem trying to have a HDD with a bigger partition than 2To in ubuntu mate ?
[09:45] <lhtd> nope it's an HDD of 3 To
[09:45] <lhtd> only to store/treat big chuncks of data
[09:45] <alkisg> Do you see any read/write issues in the output of the `dmesg` command?
[09:47] <alkisg> There's no problem with HDDs larger than 3 TB in Ubuntu that I know of, no.
[09:47] <alkisg> The MBR protective partition is a good, normal thing to have
[09:47] <alkisg> Where is that disk connected, e.g. in normal pc, or some weird pc that could have "recovery settings" etc messing up the gpt on purpose?
[09:48] <lhtd> Most help sites like ubuntu forums and stackoverflow they say that to get partitions bigger than 2To you need to remove the MBR partition table and recompile the kernel with an extra option
[09:48] <alkisg> I've seen laptops write to gpt/mbr when the user selected the recovery mode...
[09:48] <lhtd> I have a normal desktop, a bit beefed up because is the one for my work
[09:49] <lhtd> `dmesg` says"Alternate GPT is invalid, using primary GPT
[09:49] <alkisg> The only site you showed us that says that, is a 2007 page talking about fdisk, which doesn't support gpt anyway
[09:49] <alkisg> Where have you seen that you need to compile kernels etc?
[09:50] <lhtd> the page is 2017, not 2007
[09:51] <alkisg>  https://www.cyberciti.biz/tips/fdisk-unable-to-create-partition-greater-2tb.html => November 6, 2007
[09:51] <lhtd> this one from 2009 talks about the limitations of MBR https://www.ibm.com/developerworks/library/l-gpt/
[09:52] <alkisg> I'm sure it says that MBR is limited
[09:52] <alkisg> Is this somehow related to you?
[09:52] <lhtd> alkisg, true, I got another page form cyberciti. this one to delete mbr https://www.cyberciti.biz/faq/linux-clearing-out-master-boot-record-dd-command/
[09:53] <alkisg> OK so far you showed 3 pages that do not say that gpt has a partition limit of 2 tb
[09:53] <alkisg> Did you actually see what you said anywhere?
[09:53] <lhtd> alkisg, I started working on this computer since February and every 2 weeks the GPT partition grid gets damaged. So i have to back up the data to use that HDD
[09:53] <alkisg> That part, I can understand and believe you
[09:54] <alkisg> But the assumption that gpt doesn't support 2 tb partitions, or that you need a custom compiled kernel, no, I can't believe you there
[09:54] <lhtd> I did, last time I formatted the HDD last month - i'm browsing my history
[09:54] <alkisg> So, I'm saying that you're looking in the wrong direction
[09:54] <lhtd> It's quite probable alkisg.
[09:55] <lhtd> Maybe I should try to find why the GPT gets damaged so often
[09:55] <alkisg> Right
[09:56] <alkisg> First, think of what you have (software etc) that might be writing to gpt
[09:57] <lhtd> Well, last time I formated I left the HDD empty and unused with an MBR protective and a GPT partition tables. Today I needed it to put some data in it and I cannot write in it because the GPT is damaged
[09:58] <alkisg> Did you format with fdisk last time?
[09:58] <lhtd> So.. I cannot think of any software writing to GPT since it hasn't been used at all
[09:58] <lhtd> nope gparted
[09:59] <alkisg> And can you reproduce that, by e.g. leaving the disk for 1 minute, then using it at next boot?
[09:59] <alkisg> Or does it need to be left for months?
[10:00] <alkisg> Btw, you should be worrying about this: (12:49:10 μμ) lhtd: `dmesg` says"Alternate GPT is invalid, using primary GPT
[10:00] <alkisg> Do a proper formatting that would result in dmesg not complaining about your gpt
[10:00] <alkisg> My `dmesg | grep -i gpt` show nothing at all
[10:01] <lhtd> I don't know how to reproduce it. I've been trying to figure that out.
[10:02] <lhtd> Ok, the partition table just got damaged again. I think it's gets poorly enabled when rebooting the computer.
[10:03] <lhtd> `dmesg | grep -i gpt` =   Alternate GPT is invalid, using primary GPT.
[10:03] <alkisg> That would mean it was not properly formatted
[10:03] <lhtd> Ok, I'll re-format my hdd
[10:03] <lhtd> dam... I thought that part was ok
[10:04]  * lhtd back to it.
[10:04] <lhtd> thanks alkisg I'll let you know how it goes
[10:04] <alkisg> lhtd: keep in mind that your disk might be corrupted
[10:04] <alkisg> I.e. hardware disk failure
[10:05] <alkisg> Check dmesg for read/write ATA errors etc
[10:05] <lhtd> I usually format it with gparted before doing anything with it
[10:05] <lhtd> Alright !
[10:05] <alkisg> lhtd: did you ever use raid in it?
[10:05] <alkisg> Like mdraid or something?
[10:05] <lhtd> not that I'm aware of, maybe the employee who used it before me, but i cannot be sure
[10:06] <lhtd> I got this computer, formatted all drives and got on ubuntu-mate to start working
[10:07] <lhtd> (there are 3 drives, 1 ssd for boot, 1 ssd for complex data and 1 hdd for big files)
[10:07] <alkisg> OK, try a good clean formatting. testdisk also does a good work for cleaning up gpt
[10:07]  * alkisg waves, later...
[10:09]  * lhtd formats and goes to a meeting. Thanks alkisg.
[13:26] <kuntal> want know about ibus
[13:40] <popo> hi,How do i install conkyForecast, in ubuntu17.04?
[13:44] <popo> anybody in??
[15:09] <Ntemis> hello
[15:09] <Ntemis> i am facing flickering issues in terminal after upgrade to 1.18
[15:10] <Ntemis> also desktop some times is unclickable with left mouse
[15:10] <Ntemis> selecting a folder or a document is no-op
[17:50] <nomic> .z
[18:06] <nomic> z.z.


[08:40] <slaine_> Hey Guys
[08:40] <slaine_> Upgraded my 8.10 (with 8.04 kernel) EPIA to 9.04 last night
[08:40] <slaine_> all went pretty smooth, congrats
[10:12] <Technophil> Hi, I have a Sony CRT HD TV which does 1080i.  The Screen underscans, that is the menu is off the screen etc.  Using an NVIDIA 8500GT.  Is there a way to get the whole screen onto the TV?  Would modelines be what I need here?
[10:13] <Technophil> When setting the 1080i option it seems nothing in xorg.conf will change the screen
[10:13] <Technophil> xvidtune also has no effect.
[10:19] <Technophil> Should Sony be asked to add a switch to "normoscan" the TV as I understand some recent digital TV's may be able to do.
[11:03] <Technophil> Maybe the answer is to run a LCD as the desktop and run images just on the TV, if only I could get the combination to work!
[11:30] <Technophil> Man it helps when the VGA cable is plugged in....!
[11:34] <slaine_> lol
[11:40] <Technophil> Yeh I hate that....
[11:50] <slaine_> I was doing something equally silly earlier with an RTSP server
[11:50] <slaine_> wondered why it wouldn't stream
[11:50] <slaine_> Was pointing to the wrong server IP, gah
[11:51] <slaine_> Anyone know if XvMC-vld shoule be working ok with the 9.04 installs on EPIA systems ?
[11:52] <slaine_> I can get xine -V xxmc playing at 30% CPU, but mythfrontend is playing back around 75%-80%
[14:03] <Essobi> morning..
[16:09] <spoky99> hi all
[16:09] <spoky99> someone can help me?
[16:10] <spoky99> I had a hauppauge hvr 1100
[16:13] <spoky99> it work fine with xine, I see the dvb-t channel one time then I selected a channel and... every time that I start the tv I have one error message and the frontend return to the menu
[17:56] <Essobi> Umm.. how do a specify a different server IP for mythfrontend/mythtv?  I assumed all I had to do was config the mysql server, which I did and that appears to work.. but I get an error connecting to the myth protocol port on <IP_ADDRESS> which obviously isn't the right IP.
[17:58] <superm1> Essobi, run mythtv-setup, and you set the master backend ip there
[18:00] <Essobi> roger that
[18:01] <Essobi> superm1: Really? that's wierd.. I assumed all the configs would be in the frontend packages..
[18:01] <Essobi> superm1: ubuntu is telling me that mythtv-setup is in the backend package
[18:01] <superm1> Essobi, on your backend pc you have to do this
[18:04] <Essobi> superm1: Aaaaah, that makes more sense now. :)
[18:07] <Essobi> anyone seen a pen based live frontend boot disk?
[18:07] <Essobi> s/disk/install
[18:09] <superm1> you can just install onto a usb key using ubiquity
[18:20] <Essobi> Yea?  nice..
[18:21] <Essobi> I can't find any docs on libmyth-perl...
[18:27] <spoky99> hi superm
[18:27] <superm1> hi spoky99
[18:27] <superm1> how's it going
[18:28] <spoky99> O_o
[18:28] <spoky99> superm1: I open a bug.. but I'm going to modifi it :)
[18:29] <superm1> spoky99, what's the bug?  my bug mail is overflowing :P
[18:29] <spoky99> superm1: here we ave a bad dvb-t signal, two trasmitter in opposit place in the same frequenze, one digital and the other analogic, the signal digital often is null
[18:29] <heyheyhey> is mythbuntu gona ever update to .22
[18:30] <superm1> heyheyhey, .22 has to be released first :P
[18:30] <heyheyhey> i see
[18:30] <spoky99> superm1: I select a broken channel and... every time the tv start go into this channel
[18:30] <heyheyhey> well i using the trunk right now it is wicked
[18:30] <superm1> spoky99, there is a setting in the mythtv-setup app for which channel to start on
[18:31] <superm1> heyheyhey, yeah it will be nice once we can switch
[18:31] <heyheyhey> yeah
[18:31] <heyheyhey> they are doing a nice job on .22
[18:32] <heyheyhey> love that channel grouping feature
[18:32] <spoky99> superm1: I know, but it work only the first time, the other time remember the last channel selected (I dont' know how deselect this freature)
[18:32] <superm1> heyheyhey, but at least for now there's weekly ubuntu builds, so you dont need to go from source and what not
[18:32] <superm1> spoky99, i'd go in the channel editor and just remove the channel then so you dont hit this in the future
[18:33] <spoky99> superm1: is not easy... the channel work sometime and sometime don't work
[18:33] <superm1> spoky99, can you maybe add an amplifier to your line?
[18:33] <spoky99> superm1: and the strange ting is that some channel tath I see with xine on the same card and computer... in mythtv tv are locked :)
[18:34] <superm1> spoky99, that's too bad.  you can consider switching to 0.22 to see if it handles the situations more gracefully
[18:34] <superm1> !weekly | spoky99
[18:34] <Zinn> spoky99: Weekly builds are available for MythTV 0.21 (Stable) and MythTV Trunk 0.22 (Unstable, use at your own RISK) for Hardy and Intrepid.  See http://www.mythbuntu.org/auto-builds for more info.
[18:35] <spoky99> superm1: the mythtv-setup option channel.conf a manual setting... don't work :)
[18:35] <spoky99> superm1: I try the weekli :)
[18:35] <spoky99> ops
[18:35] <spoky99> superm1: weekly :D
[18:37] <spoky99> superm1: using dvb-utils i create a good channel.conf but mythtv don't see one channel using it, also putting the right channel and option manualli don't see anu channel :(
[18:37] <spoky99> superm1: also this bug is solved with the 0.22?
[18:38] <superm1> spoky99, it's possible.  i don't follow 0.22 development closely enough to confidently say yes or no though
[18:39] <spoky99> I could learn how to save all the setting of mythtv :)
[18:39] <spoky99> superm1: you ar't a computer?
[18:39] <spoky99> :P
[18:48] <Essobi> anyone gotten snd_bt87x to work?
[18:53] <spoky99> superm1: & Zinn: i don't found the "Mythbuntu Repos" program, or I'm not undersanding the text into the link page?
[18:53] <superm1> spoky99, at the bottom of that page there is a link
[18:53] <superm1> click it and you will get a deb to install and enable weekly builds
[18:54] <spoky99> opsss... :) excuse me :)
[19:01] <spoky99> hi all!
[19:42] <stepz_> do people have any success running the mythtv weekly builds?
[19:42] <stepz_> mythfrontend segfaults consistently for me
[19:43] <stepz_> across several weeks, I wonder if it's to be expected or is it worth debugging
[19:46] <stepz_> here's the last page of output from running it with gdb: http://pastebin.com/m5f382f87
[19:56] <superm1> stepz_, is that trunk?
[19:57] <superm1> er is looks like -fixes
[19:57] <superm1> is that an AMD graphics card?
[20:00] <superm1> if so, look at the release notes
[20:04] <stepz_> that's trunk and on an nvidia card
[20:06] <stepz_> integrated chip, GeForce 7050 PV if that is of any consequence
[21:34] <superm1> stepz_, so if that's trunk, you need to reset the theme to GANT
[21:34] <superm1> unfortunately Mythbuntu's theme isn't ready for trunk yet
[21:39] <stepz_> switching to G.A.N.T didn't change anything except the background that flashes before the segfault
[21:43] <superm1> can you show the new log?
[21:52] <stepz_> http://pastebin.com/dc40b3fc
[21:54] <superm1> wow that's totally unuseful
[21:55] <stepz_> the stack trace is also the same
[21:55] <stepz_> and I can't figure out if there are any dbg packages to install to make it more useful
[21:56] <superm1> for the weekly builds we don't have them i dont think
[21:56] <superm1> they would be .ddebs
[21:56] <superm1> so maybe for weekly builds we should reinstitute -dbg packages for these types of situations
[21:58] <stepz_> is it relevant that I have installed the packages on top of kubuntu 9.04?
[22:04] <stepz_> ok, found out what the issue was
[22:04] <stepz_> somehow I had mythstream installed


[14:43] <holstein> BugeyeD: i could probably find an asterisk guy on IRC for you to talk to
[14:44] <holstein> if you need
[14:44] <holstein> i know a guy that used to have one setup and liked it
[16:08] <jack__> ping anyone who is alive
[16:36] <holstein> o/
[16:42] <jack__> holstein: ping
[16:42] <jack__> you there?
[16:43] <holstein> jack__: yup
[16:43] <holstein> whats up?
[16:43] <jack__> redhat has an opening for frontline techsupport. think I should send the job description out to the ubuntu-nc mailing list?
[16:45] <holstein> jack__: sure
[16:45] <holstein> you can preface it like that
[16:45] <holstein> *potentially OT community service announcement :)
[16:54] <BugeyeD> holstein: if you can find him, just ask what soft phone he uses on linux. and thanks.
[17:11] <holstein> BugeyeD:
[17:11] <holstein> 13:09 < workGuitarman> holstein: ekiga or twinkle for sip on ubuntu
[17:12] <holstein> says he likes twingle the best
[17:17] <BugeyeD> holstein: thanks! i've heard of ekiga, but didn't notice either in the ubuntu repository yesterday when i was playing. i'll try both. does he ever use iax2 protocol instead of sip, and does he use any kind of port nat/redirection? of course you can try to connect the two of us if you don't wanna do the copy/paste thing. :)
[17:18] <BugeyeD> they're both right there in the apt-cache output. and darned if there aren't even more that i didn't see somehow ... sheesh. yesterday was monday, wasn't it?
[17:18] <holstein> BugeyeD: you can try and catch him if you want
[17:18] <holstein> he's at work
[17:18] <holstein> but, he was playing trogdor a minute ago
[17:19] <holstein> over in #opensourcemusicians
[17:19] <holstein> workguitarman
[17:19] <holstein> IF you cant catch him
[17:19] <holstein> i'll copy and paste :)
[17:20] <BugeyeD> i just queried him, we'll see if he responds. thanks!
[22:28] <_marx_> BugeyeD: just saw this off of /. http://planet.gnu.org/gnutelephony/?p=14
[22:30] <BugeyeD> hey, cool!
[22:30] <BugeyeD> bookmarked, thanks!


[17:44] <fagan> Hey, I caused an issue with lp because of a weird bzr whoami that got pushed and merged
[17:44] <fagan> (I think)
[17:44] <jcsackett> fagan: what issue? is there an example you can point me to?
[17:44] <jcsackett> or just some more details?
[17:45] <fagan> jcsackett: I had a # at the end of my bzr whoami
[17:45] <fagan> now if you go to lp on a merge page it gives an oops
[17:45] <fagan> I dont know if its all of them but its definitely on the one I merged to
[17:46] <jcsackett> fagan: no worries, you're whoami change didn't cause the oops.
[17:46] <fagan> Ah ok
[17:46] <jcsackett> we're currently investigating that issue. you can follow along, if you like, on bug 759928
[17:46] <fagan> Oh I broke tarmac
[17:46] <fagan> I thought that I blew up lp too
[17:46] <fagan> :)
[17:46] <fagan> its cool
[17:48] <jcsackett> fagan: bzr whoami is used to identify a commiter. you may see a change in the "committed by <some-name>" data in the revision logs for your branch.
[17:48] <fagan> jcsackett: yeah I know but it just strangely started oopsing when I broke tarmc so I thought I should at least ask and/or say sorry :)
[17:49] <jcsackett> fagan: just a coincidence of timing. no worries. :-)
[17:49] <nigelb> fagan: omg, you blew up LP! :P
[17:49] <fagan> nigelb: wouldnt that be badass
[17:50] <nigelb> fagan: it only would if you got all the builders down
[17:50]  * nigelb touches wood 'just in case'
[17:50] <fagan> nigelb: good to know ill mark it down that I have to do that to kill lp
[17:51]  * fagan is an intern so breaking everything is a minor possability
[17:51]  * jcsackett makes note to have fagan "watched."
[17:51] <jcsackett> :-p
[17:52] <nigelb> fagan: this reminds of something :p
[17:52] <fagan> nigelb: what would that be? :)
[17:53] <nigelb> sec, finding
[17:54] <nigelb> fagan: http://quotes.burntelectrons.org/2804
[17:55] <fagan> nigelb: yeah thats the idea
[17:55] <nigelb> fagan: heh, glad to know :P
[17:56] <fagan> but at least I am exposing awesome bugs
[17:56] <nigelb> Yeah,I follow your blog posts, interesting to hear :)
[17:57] <fagan> nigelb: oh cool its good to see that people are enjoying them ill have a nice one today anyway
[17:57] <fagan> :)
[17:57] <nigelb> :)
[18:03] <fagan> tarmac is fixed now :)
[18:07] <fagan> (ill write in my post how the guys fixed it)
[18:12] <FloSoft> hi - i try to upload a new "orig" file for one of my packages to my ppa but it always gets rejected even i delete the package in the ppa
[18:15] <fagan> nigelb: http://shanefagan.com/internship-day-15
[18:15] <fagan> :D
[18:17] <nigelb> fagan: hahah
[18:17] <TheEvilPhoenix> FloSoft:  you never should upload a new orig file.
[18:18] <FloSoft> TheEvilPhoenix: shouldnt it remove it if the corresponding package is deleted in the ppa?
[18:18] <micahg> TheEvilPhoenix: FloSoft: to be more correct, you need an "upstream" version bump when uploading a new .orif file
[18:18] <micahg> *orig
[18:19] <fagan> later all
[18:21] <FloSoft> micahg: okay, i'll try that - but: shouldnt it remove the orig-source from the ppa too, if no package references it??
[18:23] <micahg> FloSoft: no, to prevent having to original files w/the same name and different contents
[18:23] <FloSoft> okay
[19:15] <ScottK> lifeless: Error ID: OOPS-1929F1046 is on the package accept page.
[19:18] <lifeless> ScottK: thanks; triggering a log sync
[19:18] <ScottK> Good luck.
[19:22] <bigjools> that page is a nightmare
[19:27] <ScottK> Same two packages worked on the second try.
[19:37] <lifeless> SQL time: 7798 ms
[19:37] <lifeless> potassium
[19:37] <lifeless> 1/2 a second looking up the same archive 70 times
[19:38] <lifeless> 0.3 looking up the distroseries arch tags the same 70 times
[19:38] <lifeless> 0.8 of a second pulling back 6 SourcePackageFilePublishing entries
[19:39] <lifeless> 1.4 seconds bring back *bug subscriptions* - wtf
[19:39] <lifeless> make that 2.5 seconds
[19:40] <lifeless> ScottK: lots of fat there, but spread all over in little bits
[19:40] <ScottK> Fin
[19:40] <lifeless> ScottK: it needs a big flattening
[19:40] <ScottK> Fun
[19:41] <lifeless> anyhow
[19:41] <lifeless> you were on a slow appserver we're replacing
[19:41] <lifeless> its litle that that was a dominating factor
[19:42] <lifeless> s/litle/likely/
[19:43]  * elmo twitches
[19:44] <marktraceur> Hi there, #launchpad, want to help a fellow upload a package?
[19:59] <saulus> HELP: I cant login any more and my pw reminder does not get towards me. I had a look in the spam section but there was nothing. I waited 12h. Whan can I do?
[20:01] <saulus> Im registered in freenode with this nick. This nick is also on my info page in launchpad. Also I should get all mails that you send me to my launchpad account (hopefully). So there are ways to veryfy me.
[20:02] <sinzui> saulus: https://help.launchpad.net/Feedback
[20:02] <sinzui> saulus: I think you want to use https://forms.canonical.com/lp-login-support/
[20:03] <saulus> thy sinzui , Ill try that
[20:03] <saulus> thanks
[20:09] <Darxus> In a source build recipe, how do I specify an official ubuntu source package as the source of the packaging information (debian directory)?
[20:13] <Darxus> I mean, what's the path?
[20:17] <Darxus> Ah, looks like I want lp:ubuntu/spamassassin ?
[20:21] <FloSoft> hi, any idea to https://answers.launchpad.net/launchpad/+question/152715
[20:32] <Darxus> I can't edit https://help.launchpad.net/Packaging/SourceBuilds/Recipes ?
[20:39] <Darxus> "Conflict adding file debian.  Moved existing file to debian.moved."
[20:39] <Darxus> "bzr: ERROR: Conflicts from merge"
[20:40] <Darxus> In a source build recipe I told it to merge the debian directory from the normal ubuntu package on top of the source from spamassassin's svn trunk.  Trunk contains an (old, useless) debian directory.  Moving the old one out of the way was the right thing.  What do I do to get it to ignore this and build?
[20:43] <Darxus> Build log was https://launchpadlibrarian.net/69302542/buildlog.txt.gz
[21:02] <sinzui> Darxus: I think you want to branch the upstream. You can delete debian/ from that one.
[21:03] <sinzui> Darxus: The alternative is to try nest instead of merge with a packaging branch with some hope that the nested branch overwrites the old debian dir
[21:12] <Darxus> sinzui: I did use nest-part.  https://code.launchpad.net/~darxus/+recipe/spamassassin-daily
[21:13] <Darxus> I don't want to branch it, because the whole rason I was trying to do this was automated daily builds.
[21:13] <Darxus> Should I open a (feature request) bug against launchpad?
[21:14] <lifeless> Darxus: please
[21:14] <lifeless> Darxus: what you can do in the interim is:
[21:14] <lifeless>  - branch it and delete debian
[21:14] <lifeless>  - have a three-rule recipe
[21:15] <Darxus> lifeless: Thanks.  Three rule recipe?
[21:15] <lifeless> that is - start with trunk, merge your branch (which deletes /debian only), merge the packaging (which adds a good /debian)
[21:17] <sinzui> Switching from bzr-builder to recipes was harder than I hoped for me. many things are easier with shell commands
[21:17] <Darxus> lifeless: Ohh, I didn't realize merging a branch could delete a directory, thanks.
[21:18] <lifeless> Darxus: definitely file a bug
[21:18] <Darxus> I am.
[21:18] <lifeless> Darxus: because it would be nice to do it more directly.
[21:18] <lifeless> Darxus: but this should get you going
[21:21] <Darxus> https://bugs.launchpad.net/launchpad/+bug/760201
[22:56] <lifeless> Darxus: see sinzui's comment on your bug
[22:56] <lifeless> Darxus: he has given you a few steps
[22:58] <Darxus> lifeless: Oh, thanks.
[23:13] <doko> https://launchpad.net/builders
[23:13] <doko> Not allowed here
[23:13] <doko> Sorry, you don't have permission to access this page.
[23:13] <doko> is this expected?
[23:14] <doko> lifeless: ^^^
[23:14] <lifeless> doko: iz bug
[23:14] <lifeless> there is an embargoed build shown on the page right now
[23:14] <lifeless> Unauthorized: (<lp.code.model.sourcepackagerecipebuild.SourcePackageRecipeBuild object at 0x1931a150>, 'title', 'launchpad.View')<br />
[23:14] <doko> ahh, ok
[23:15] <lifeless> I thought there was a bug but I can't see it - filing one
[23:16] <lifeless> bug 760303
[23:17] <mwhudson> that's a but that keeps reappearing
[23:17] <mwhudson> *bug
[23:18] <lifeless> we haven't fixed it by filtering on load :)
[23:20] <maxb> The same class of bug exists on the +code-imports list
[23:25] <sinzui> 403 bugs should be tagged as such. I think several of them could be fixed together if we knew them all
[23:28] <Darxus> So why does https://code.launchpad.net/~ubuntu-branches/ubuntu/natty/spamassassin/natty contain patches against spamassassin v3.3.0 when the spamassassin package has contained patches against v3.3.1 since lucid?
[23:30] <sinzui> Darxus: I think the package maintainers could answer that. Source package branches are copied/cloned for each release. So while the package might be updated by a human, I doubt he will update the branch unless something breaks
[23:31] <Darxus> Ah, thanks.
[23:31] <Darxus> That sucks :)
[23:44] <maxb> Darxus: That sounds like an automated package import branch.
[23:44] <maxb> Sometimes the importer has issues with some packages, leading to the branches being stale
[23:45] <maxb> And indeed in this case: http://package-import.ubuntu.com/status/spamassassin.html
[23:46] <Darxus> Ahh, thanks.
[23:47] <Darxus> I'm pretty sure that second tarball shouldn't be included.
[23:47] <Darxus> I think the whole point was to keep rules separate so people would set up a cron job to update them regularly via sa-update.
[23:59] <bryceh_> https://launchpadlibrarian.net/68484762/Lspci.txt (and other attachments) are giving out 503 errors