/srv/irclogs.ubuntu.com/2010/08/18/#ubuntu-devel.txt

ebroderYeah, I saw that, too00:00
ionLoading all the stuff needed for a graphical plymouth before ureadahead does its thing would defeat the purpose of ureadahead, but printing a line of text wouldn’t.00:01
jdong"Loading loading screen...."00:01
jdong:)00:01
jdongis that like Windows 7's "calculating time remaining"?00:01
ebroderIf I'm basically trying to create a livecd rootfs with the nvidia drivers baked in, what do I need to do? Install nvidia-current, drop in an xorg.conf, anything else?00:01
ionPlymouth’s purpose is not a loading screen. It’s multiplexing interaction between the user and startup programs.00:02
cjwatsonwell, plymouth yes, plymouth-splash not necessarily00:03
cjwatsonI suspect we are in agreement from different directions, though00:03
jdongion: sure, but given that it also functions as a loading screen, it looks a little bit confusing00:09
=== bjf is now known as bjf[afk]
jdongion: especially on machines with poor IO performance00:09
ionYes, a dozen seconds of black screen isn’t optimal.00:10
lilmonstahello all , apolagies for asking but is the 10.04.1 release still due today?   would it be the daily iso listed as 16.1?00:11
ionWe should do what Windows™ does: drop the readahead stuff, generate (and keep updating) a model of disk usage patterns and use idle time to reorder disk blocks for optimal startup times. :-P00:12
jdongion: theirs also includes a readaheader00:13
ionok00:14
jdongit does some interesting throttling stuff though to minimize the devastation if the readahead info is really wrong (tm)00:14
jdonglike for us, if you put 5000 random files in the readahead pack, your boot performance will really tank :)00:14
jdong(on HDD)00:14
penguin42(I was thinking Maverick is currently feeling slower at boot than lucid - but I haven't timed it)00:15
jdongmy two Maverick machines at work here are reiser4 and btrfs00:15
jdongone doesn't support readahead, the other is slower than NFS to asia.00:15
ebroderOww. You must not like your data00:15
jdongthanks to 2.6.3500:15
jdonghaha experimental setup :)00:16
* ajmitch thought all your setups were experimental00:16
jdongit is kind of a shame that it takes 7 hours 30 minutes to install from the alternate CD on btrfs in Maverick00:16
jdongwonder if we want to roll back that commit for ubuntu-maverick.git00:16
RAOFIt's more of a shame that installing 80 updates takes 2 hours on btrfs.00:17
=== kentb is now known as kentb_out
jdong(or cross our fingers and hope Oracle has a patch)00:17
jdongRAOF: I got pissed enough to locally revert that00:17
ajmitchRAOF: that sounds worse than my laptop :)00:17
jdonghttp://git.kernel.org/?p=linux/kernel/git/mason/btrfs-unstable.git;a=commit;h=5da9d01b66458b180a6bee0e637a1d0a3effc62200:17
jdongthat thing00:17
RAOFjdong: I got pissed enough to take an image (as it seems by btrfs partition is interestingly broken) and reformat to ext400:17
jdongHAHAHA00:18
jdongok that works too!00:18
ionMeh. I’m counting days until Oracle drops the btrfs project and instantly starts suing everyone using/developing/distributing it for infringing on their Imaginary Property. :-P00:18
jdongion: well brtfs probably does violate the crap out of the ZFS patent portfolio00:18
RAOFchrisccoulson: Isn't it a bit late for you to be joining #ubuntu-devel? :)00:20
=== Narwhal is now known as IdleOne
chrisccoulsonRAOF, oh, i must have got disconnected for a bit ;)00:29
RAOFAaah, ext4.  < 10 minutes to download and install 300 packages.00:33
slangasekwait, are you extolling ext4 because of how fast dpkg runs on it?00:34
jdonghaha.00:35
RAOFslangasek: In comparison to how dpkg runs on *btrfs*, that's practically negative time :)00:36
slangasekinteresting00:37
RAOF(at least in maverick)00:37
lifelessRAOF: good or bad on btrsfs?00:37
RAOFlifeless: Terrible on btrfs.00:37
lifelesslet me guess00:37
lifelessfsync?00:37
RAOFOn the order of 2 hours to install 80 already downloaded updates00:37
RAOFI'm not sure that it is fsync, actually, although my libeatmydata testing wasn't particularly rigourous.00:38
lifelessok00:38
lifelessany ideas?00:38
lifelessand does eatmydata take care of the fsync variants ?00:38
RAOFjdong's already posted a link to the patch (series?) which causes a ~10x regression in write-heavy loads that's in Maverick00:38
lifeless(sync, fsyncdir)00:39
RAOFI think libeatmydata does, yes.00:39
RAOFThere's an LP bug about this, too.00:39
jdonglifeless: and no, eatmydata doesn't take care of the btrfs thing. It has to do with delayed allocation not truly delaying allocation, forcing way more tree operations than needed00:42
lifelessjdong: thanks00:42
jdongChris Mason had triaged the bug though and says he's working on a patch00:43
RAOFbug #601299 , if you're interested.00:43
jdong(two weeks ago)00:43
ubottuLaunchpad bug 601299 in linux (Ubuntu) "maverick btrfs slow install" [Undecided,Confirmed] https://launchpad.net/bugs/60129900:43
jdongwow, 12 hours to set up on a SSD00:43
jdongimpressive!00:43
jdongoh nvm it's an Asus SDHC-on-a-card "SSD"00:44
chrisccoulsoneatmydata is such a cool name. it almost makes me feel compelled to use it all the time00:45
jdongoh just patch eglibc if you're gonna do that ;-)00:46
djznfolks, 10.04.1 --- any hopes for tonight still ? or probably another 7 days...?01:20
skat_djzn, looking likely.   #ubuntu-release is fairly active ;)01:36
djznso we don't get 10.04.1 tonight.....02:22
ScottKdjzn: I wouldn't assume that.02:23
ScottKI guess it depends on when tonight ends for you.02:23
djznScottK: it ends in 1:30 hour.... -3.00 GMT02:23
djznlol02:23
ScottKYou might yet then.02:24
djznScottK: how can you be so sure... this has been postponed for a few days... yet, no sign of isos....02:25
ScottKI'm somewhat involved in the effort.02:27
djznScottK: I could notice that...02:29
djznScottK: I feel a hint.... that everything is already done... ISOs are ready... the thing is... there are several types of ISOs and each of them had to be produced.. the netbook one, the alternate one, even the DVD had to be made....02:31
djznScottK: But I am not sure... still a Fix Commited bug laying....02:32
=== dendrobates is now known as dendro-afk
* ScottK was going to tell him it's out.03:21
ajmitchoh well, just a little late :)03:21
* ajmitch wonders when the NZ mirrors will have it03:22
ScottKAt least natty will be less typing than maverick.03:23
ajmitchbut getting people to spell narwhal properly will be fun03:24
ajmitchAt least it's not drapper :)03:24
ajmitchgreat, looks like one of the nz mirrors just has a recursive symlink03:32
=== almaisan-away is now known as al-maisan
* huntz0r is away: I'm busy03:58
ionThanks for the information!03:58
huntz0rbloody xchat...04:02
=== al-maisan is now known as almaisan-away
=== oubiwann-away is now known as oubiwann
pittiGood morning05:43
pittikirkland: pong05:44
pittismoser: yup, will do ASAP05:44
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
dholbachgood morning07:32
* mneptok looks left07:38
* mneptok looks right07:38
* mneptok junps up and down on dholbach 07:38
mneptokMOIN!07:38
dholbachhi mneptok07:38
mneptok*tacklehug*07:38
ajmitchthat's a nice enthusiastic greeting07:40
TheMusoBrutally so.07:42
TheMuso:)07:42
dholbach:-)07:43
=== almaisan-away is now known as al-maisan
Sarvattwere the non-LTS ports archives before jaunty moved to another server or were they wiped out completely?08:46
tjaaltonSarvatt: try http://old-releases.ubuntu.com08:52
Sarvattphew, thanks tjaalton!08:54
tjaaltonthis is weird, mounting Maple14 cdrom doesn't work otherwise but manually08:57
tjaaltonboth on lucid & maverick08:57
sorentjaalton: The maple cdroms are rather special, irrc.09:11
soreniirc, even.09:11
sorentjaalton: I believe it will look different depending on whether you mount it from linux, windows or mac.09:11
sorentjaalton: ...and it'll look different depending on whether you mount the iso like you normally would or if you look at it through one of the userspace tools to inspect iso's.09:12
sorentjaalton: In short, I'm not surprised some things act up. They shouldn't, but I'm not surprised :)09:13
tjaaltonsoren: ah, could be like that yes09:15
tjaaltonwell, whatever tries to automount them should be fixed to support those I suppose :)09:16
tjaaltonsoren: worked on jaunty though, so sounds like a regression to me ;)09:24
tjaalton(just tested it)09:24
sorentjaalton: I remember having problems in... err...09:27
* soren rewinds his brain a couple of years09:27
sorenerr.. edgy, it must have been.09:27
tjaaltonsoren: ok.. now it seems to be udev handling the mounts?09:29
sorentjaalton: No idea.09:31
cjwatsonudev won't be mounting things itself.  perhaps udisks.09:33
tjaaltonright09:34
sivanghi all09:34
sivangWhat are the tools commonly used to allow participants not in physical presence to be part of a developer's summit? http://gobby.0x539.de/trac/ comes to mind, but what other tools have past summits used?09:36
bilalakhtarbdrung: there?09:51
bdrungbilalakhtar: yes09:51
bilalakhtarbdrung: a main patch, ready?09:52
bilalakhtarbdrung: patch has been accepted in MeeGo09:52
bilalakhtarpackage: gnome-disj-utility09:52
bilalakhtarK09:52
bdrungbilalakhtar: i will put it on my list. i will have time for it in the evening09:52
bdrungbilalakhtar: can you give me the lp?09:53
bilalakhtarbdrung: Thanks a lot! https://code.edge.launchpad.net/~bilalakhtar/ubuntu/maverick/gnome-disk-utility/fix-414107/+merge/3296609:53
bilalakhtarbug #414107 bdrung09:53
ubottuLaunchpad bug 414107 in gnome-disk-utility (Ubuntu) "Palimpsest GUI impossible to use on small screen" [Medium,In progress] https://launchpad.net/bugs/41410709:53
bilalakhtarits a branch merge, hence bug is in-progress09:54
bdrungbilalakhtar: if your branch is ready, unassign yourself09:54
bilalakhtarbdrung: and, status of bug?09:54
bdrungbilalakhtar: sponsor don't care about the status09:55
bdrungbilalakhtar: i saw statuses of (new, confirmed, triaged, in progress, fix committed)09:56
bilalakhtarhuh?09:56
bilalakhtarbdrung: what does that mean?09:56
bilalakhtarbdrung: I don;t need to subscribe sponsors to the bug, right?09:57
bdrungbilalakhtar: the merge request will appear on the sponsors list. so no need to subsrcribe the team.09:58
bilalakhtarbdrung: what do you mean by 'I saw statuses of .....'09:58
bilalakhtarah well leave it. I know bdrung is busy. Bye!10:00
=== doko_ is now known as doko
bdrungbilalakhtar: the bugs that i sponsored had a status of one of the mentioned above. we have no rule which status the bug should have.10:01
bilalakhtaraha bdrung thanks10:02
bdrungbilalakhtar: it could be everything except a 'fixed' status or Incomplete10:03
bilalakhtarthanks bdrung10:03
bilalakhtarbdrung: I just ran update-maintainer over it, so if you have already downloaded the branch, please pul10:06
bilalakhtar*pull10:06
bdrungbilalakhtar: i haven't pulled it yet. sponsor-patch will run update-maintainer (and therefore catch those mistakes) ;)10:07
bilalakhtarthanks bdrung :)10:07
=== yofel_ is now known as yofel
ricotzseb128, hello10:42
seb128hi ricotz10:42
ricotzseb128, looks like i have a working gtk+3 package :)10:42
seb128ricotz, can you talk about it on #debian-gnome?10:43
ricotzok10:43
seb128ricotz, ideally we would get it in debian, they started work there10:43
=== chrisccoulson_ is now known as chrisccoulson
theclawhi11:17
theclawhow do I have to mark config files so that when installing the package, I will get asked whether I want to overwrite the config?11:18
theclawI already tried putting the configs in 'conffiles'11:19
cjwatsonjust install them somewhere under /etc, and use debhelper compat level 3 or above (usually 7 these days)11:21
cjwatsonwith even remotely modern debhelper you don't need to fiddle with conffiles by hand11:21
cjwatsonit will only prompt you if there are some local changes versus the distributed copy11:21
theclawyes, I have local changes. Maybe I'm using an outdated debhelper11:22
cjwatsonastonishingly unlikely11:22
cjwatsonwell, you might be using an outdated debhelper compat level11:23
theclawcjwatson: I have '5' in debian/compat, so this shouldn't be the problem?11:23
cjwatsonbut debhelper 3 dates back to 200111:23
cjwatsonthen there is something else wrong and we would need detailed information (e.g. an example) to debug it11:23
seb128hum, "vesamenu.c32: not a COM32R image"11:23
seb128I wonder what went wrong with that lucid usb stick I just did11:24
cjwatsonthe installed version of syslinux tends to need to match11:24
theclawcjwatson: I can't distribute anything of the package, sorry11:24
seb128cjwatson, you mean I can't do a lucid usb key with maverick usb creator?11:24
theclawcjwatson: but thanks for the hints11:25
seb128or on maverick rather11:25
cjwatsonseb128: only if you downgrade to lucid's syslinux11:25
cjwatson(at the moment)11:25
seb128cjwatson, ok thanks11:25
cjwatsontheclaw: can't help if you can't share11:25
seb128I did the keys 3 times and rsync the iso again to be sure11:25
seb128it's a non obvious issue ;-)11:25
cjwatsonthere's an open bug for it11:25
cjwatsonev and I have talked about it, but it's mostly been conference/holiday season since then11:26
seb128ok, thanks11:26
seb128at least I know what's going on now ;-)11:26
cjwatsonI'm not sure what the right answer is given that syslinux isn't actually on the CD, only isolinux11:27
bilalakhtarbdrung: I actually need to get it SRUed into Lucid at the same time. How to do this with a branch? since lp:ubuntu/lucid-proposed/gnome-disk-utility does not exist.11:42
tumbleweedbilalakhtar: propose merging into lucid instead of lucid-proposed?11:46
bilalakhtartumbleweed: is that acceptable?11:47
bilalakhtartumbleweed: ok, I will follow the good-old debdiff method11:47
tumbleweedother people seem to do that, the problem is that the merge request will never be marked Merged automatically...11:47
tumbleweed(and the reviewer can't mark it merged / WIP)11:48
bilalakhtartumbleweed: well, since it is my first SRU, I don;t want to experiment with it11:48
bilalakhtarso I am debdiffing11:48
tumbleweedbilalakhtar: :)11:48
=== MacSlow is now known as MacSlow|lunch
bilalakhtartumbleweed: if you are free, bug #61973811:55
ubottuLaunchpad bug 619738 in amara (Ubuntu) "Sync amara 1.2a2-1.1 (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/61973811:55
bilalakhtartumbleweed: you were the one who got the ubuntu patches there11:56
tumbleweedbilalakhtar: hah, sure11:56
geserbilalakhtar: what's the benefit of syncing it now?11:57
bilalakhtargeser: why?11:57
tumbleweedbilalakhtar: that wasn't an ubuntu patch11:57
bilalakhtargeser: so that in N release they get synced automatically11:57
bilalakhtartumbleweed: I know, but the reason is the same11:57
bilalakhtargeser: people say: Drop the ubuntu changes whenever possible11:58
bilalakhtartumbleweed: the current ubuntu changes and the debian accepted changes are somewhat different, but they have the same goal: move away from python2.511:58
geserbilalakhtar: yes, but we are currently past FF and should start focusing towards release. That also excludes syncs which no benefit right now.11:59
bilalakhtargeser: ok, I will take care about it next time onwards.12:00
geserbeing able to autosync for N isn't IMHO a valid reason for syncing (at least if it's the only reason)12:01
bilalakhtargeser: ah, ok, please allow this one, I will take care from the next time onwards12:02
geserbilalakhtar: sure (it's up to your sponsors to ACK it or not) but please consider if syncing a package gains us anything for the release for next syncs/merges12:07
geserwe shouldn't sync/merge because we can12:07
bilalakhtarok, I will take care from the next time onwards, geser12:07
cjwatsongeser++12:08
sabdflseb128: did you get a chance to look into gnome-terminal tabs?12:48
=== al-maisan is now known as almaisan-away
seb128sabdfl, not yet, still busy with feature freeze exception from dx and other teams12:50
sabdflokdokey12:52
sabdfli saw the version bump this morning and got all hopeful ;-)12:52
seb128sabdfl, no, that was just standard GNOME 2.31 update ;-)12:54
=== echidnaman is now known as JontheEchidna
=== MacSlow|lunch is now known as MacSlow
=== jtechidna is now known as JontheEchidna
=== thekorn_ is now known as thekorn
=== almaisan-away is now known as al-maisan
=== jtechidna is now known as JontheEchidna
pittislangasek, robbiew: \o/ 10.04.113:53
ricotzjcastro, hello13:54
pittirobbiew: hm, https://wiki.ubuntu.com/LucidLynx/ReleaseNotes/ChangeSummary/10.04.1 looks a bit thin?13:55
pittiis there a non-boilerplate version of this?13:56
=== e-jat is now known as ejat
cjwatsonpitti: we were stuck on a silly UTF-8 decoding error in the script that generates it - I gave a fixed version to robbiew a couple of hours ago, so he should be able to fill that out once he's up14:16
cjwatsonthe error was ultimately down to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593442, if you care ...14:16
ubottuDebian bug 593442 in dpkg "dpkg-genchanges can produce broken UTF-8 in Description" [Normal,Open]14:16
pitticjwatson: oh nice, it's autogenerated now?14:17
cjwatsonpitti: more or less always was partially; it requires manual editing to do categorisation and get it into a consistent editorial voice14:18
=== maco2 is now known as maco
\shcjwatson: I just stumbled upon a bug discussion for openssh + the ldap patch...do you still support your argument, or would it be a good idea to re-check the quality of the openssh LPK  patch (bts: #319244)14:34
cjwatsonI still support my argument - get it upstream first, I'm not going to carry it in a distro14:34
cjwatsonsorry14:34
cjwatsonI haven't made any argument either way about the quality of the patch, so that is a red herring14:35
=== e-jat is now known as ejat
\shcjwatson: I just trying to find now any reference from upstream about this issue...but looks like I'm too tired to read all google hits14:36
\shah there14:38
pittihm, we recently started to pull in openjdk into the images, leading to massive oversizedness14:41
ahasenackpitti: hi, is 10.04.1 out yet?14:44
pittiahasenack: yes14:44
ahasenackpitti: cool, so -proposed is unfrozen?14:44
pittiahasenack: right; I'll get to SRUs ASAP14:45
ahasenackpitti: thanks14:45
\shcjwatson: when you are interested in this topic: http://marc.info/?l=openssh-unix-dev&m=127607159208207&w=2 -> the whole thread :)14:46
jcastroricotz: hi14:51
ricotzjcastro, hi, how is the progress with the gome3 (gnome-shell) ppa?14:52
=== bjf[afk] is now known as bjf
jcastroricotz: I am not sure, I've been gone for a bit, seb128 might know15:01
ricotzjcastro, there are still plans to provide a ppa with a gnome3 preview?15:01
ricotzjcastro, ah, ok, then i am up2date15:02
seb128ricotz, not really15:02
seb128ricotz, we need to get gtk3 in with all those libraries changes first but everybody is busy15:02
ricotzseb128, ok15:03
seb128with GNOME3 delayed from one cycle and gtk3 delayed until end of year we almost have extra time15:03
ricotzseb128, ok, but the goal is still to get gtk3 into maverick?15:04
seb128would be nice to get it in universe yes15:04
ricotzmy package still has some file collisions with gtk2, i am not sure about the right way to solve them15:05
=== sconklin-gone is now known as sconklin
ricotzbut gnome-shell can be built again with it15:06
cjwatson\sh: thanks.  they seem to be going about things the right way, at last; there is probably some hope15:06
robbiewpitti: fyi, starting on the change summary now...assuming python holds up :)15:09
pitti_ahasenack: I followed up to bug 610744, there's still some bug cleanup to do15:12
ubottuLaunchpad bug 610744 in landscape-client (Ubuntu Karmic) "Update jaunty, karmic, lucid and maverick to landscape-client 1.5.4" [Undecided,New] https://launchpad.net/bugs/61074415:12
seb128ricotz, I would appreciate if you didn't have your own gtk3 version in a ppa15:13
seb128ricotz, it has potential to create trouble for users who want to try it and don't know it might conflict with the official builds when we will have those15:13
ricotzseb128, yes, that is why i want someone of you to review it15:14
ricotzi still have it in my staging ppa which shouldnt be used15:15
freepitti_: hey, didn't we agree on opening SRU tasks only for the main SRU bug (which references the other ones)? for sake of convenience15:21
pittifree: we did? I can't remember15:22
freepitti: also I think that internally we were marking bugs as "Fix released" only when the packages actually hit -updates15:22
pittifree: but anyway, if the 1.5.4 changelog claims to fix a bug which is still open upstream and targetted at 1.5.5, there's something wrong?15:22
pittifree: that's what the Ubuntu task should be for then15:22
pittifree: but ok, I can accept the "fix committed" upstream state, even if it's slightly weird15:22
freepitti: right, I'm fine whatever, I just didn't open tasks because of the above15:23
pittiok, I can't remember the discussion where we agreed to not add SRU tasks15:23
freepitti: about the wrong milestone, sorry about that, the bug should have been marked "Fix committed" quite a bit ago, but we forgot, so it was automatically shifted to 1.5.5 by a script we use at the end of the milestone15:25
freepitti: so do you prefer to have tasks for all bugs or only for the main one?15:25
ScottKIs http://people.canonical.com/~ubuntu-archive/NBS/ updating correctly?  I uploaded most of the rebuild targets for http://people.canonical.com/~ubuntu-archive/NBS/libkrb5-25-heimdal last night and even the ones that built ~12 hours ago still show there.15:25
pittiScottK: hm, usually it does15:25
pitticronjob is working, anyway, but only every 8 hours15:26
* ScottK checks another one.15:26
ScottKpitti: Probably just got caught in the window where we don't get a publisher run for a few hours + the 8 hour cron job cycle.15:27
ScottKI'll check it again tonight then.15:27
ScottKThanks for looking.15:27
pittinp; I have used it a few days ago, and it was working fine15:27
pittibut please let me know if the next update (at 1900 UTC) is still bad15:28
ScottKWill do.15:28
cjwatsonslangasek: could you review https://code.launchpad.net/~csurbhi/ubuntu/maverick/samba/samba-fix.276472/+merge/32753 ?15:40
slangasekcjwatson: my review is not worth much there; it looks syntactically correct, but should be reviewed by somebody who understands the protocol better15:50
slangasek(i.e., upstream)15:50
slangasekcjwatson: (do you want me to follow up with an actual merge review saying this?)15:51
cjwatsonslangasek: sure, just looking for somebody to claim it really16:04
=== fta_ is now known as fta
=== dendro-afk is now known as dendrobates
cndHi all, are MIR reports processed on a set schedule?16:53
cndseb128, pitti ^^?16:53
pitticnd: not sure, asac is driving it these days16:53
=== asac_ is now known as asac
pittibut I expect not16:53
cndasac, in case you missed my question due to your ping timeout :), are MIR reports processed on a set schedule?16:54
=== deryck is now known as deryck[lunch]
bilalakhtarCan anyone accept the nominations at bug #414107 ?17:19
ubottuLaunchpad bug 414107 in gnome-disk-utility (Ubuntu) "Palimpsest GUI impossible to use on small screen" [Medium,In progress] https://launchpad.net/bugs/41410717:19
achiangslangasek: this bug has a patch and looks like Keybuk even reviewed it; any chance of taking a look? https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/53713317:23
ubottuLaunchpad bug 537133 in mountall (Ubuntu Lucid) "mountall issues with NFS root filesystem" [Medium,Confirmed]17:23
=== emma is now known as emc44
=== emc44 is now known as em
=== al-maisan is now known as almaisan-away
bilalakhtarbdrung: about the bug I told you, there is an SRU also needed for it, so when you look at the maverick branch, could you please look at the debdiff attached to the bug report also (sponsors subscribed there)? That debdiff is for getting the package into lucid-proposed17:57
jibelcjwatson, hello, bug 619135, do you think that's really a packaging issue or dpkg becoming suddenly overly verbose due to the changes in 1.15.8.4 ?18:11
ubottuLaunchpad bug 619135 in banshee (Ubuntu) "Warnings in '/var/lib/dpkg/updates/***' while installing banshee" [Undecided,New] https://launchpad.net/bugs/61913518:11
jibelcjwatson, the relevant changelog entry "* Always print a massage on warning when parsing control files."18:11
=== deryck[lunch] is now known as deryck
akheronI did do-release-upgrade on a karmic server today, everything was fine until libc-i686 was upgraded18:39
akheronright after that everything started to fail, failing about missing version GLIBC_2.1118:40
akheron*complaining18:41
akheronwhat could be wrong?18:41
penguin42akheron: Can you get an ldd /bin/ls out of it?18:42
akheronI can reproduce this easily, as I have a backup disk image of the server18:42
akheronpenguin42: after the upgrade has failed?18:42
=== almaisan-away is now known as al-maisan
penguin42akheron: Yeh depending just how failed it is18:43
akheronI don't think so, as at least ls just segfaults18:43
sebnerJontheEchidna: hola :) , if you are bored you could update k3b and make another backport maybe? :)18:43
akheronI cannot access the machine right now, and before trying again I would have to restore the backups18:43
djznScottK: Just dropped by to say THANK YOU for the point release18:55
ScottKdjzn: It was very little to do with me, but you're welcome.  You left just slightly too soon last night.18:56
djznyeah, i had to sleep, but doesn't matter now, it's there...18:56
=== nxvl_ is now known as nxvl
=== fta_ is now known as fta
JontheEchidnasebner: ooh, turns out I can merge from debian. :)19:18
highvoltageJontheEchidna: nice :)19:21
=== al-maisan is now known as almaisan-away
SpamapSpitti: Don't know if you noticed, but I proposed merging a change to the WI tracker that will allow you to stop regenerating all the html/burndown/json for closed out milestones.19:45
SpamapSpitti: and currently looking at speeding up the select statements a lot19:45
=== fta_ is now known as fta
mycaeHello. I think I was asked in a bug to request an FFE for a  package sync (minor package that was new to debian), but I cannot seem to find any documentation on how one does this. In fact, i thought this was what I was doing. Does anyone know what I am supposed to do? (bug #617787)20:18
ubottuLaunchpad bug 617787 in Ubuntu "Sync request: 3depict" [Wishlist,Confirmed] https://launchpad.net/bugs/61778720:18
micahgmycae: looks like you're fine on this20:21
micahgarchive admins are subscribed and FFe was approved20:21
mycaeok. good. was not clear if I had to "get" an FFE from someone/where20:21
mycaethankyou.20:22
=== fta_ is now known as fta
=== fta_ is now known as fta
=== fta_ is now known as fta
macoi just got an email from lp saying a package i uploaded failed to build on itanic but the FAILEDTOBUILD.txt.gz says "Built  successfully" partway down...21:05
macolike, right at that end bit before the chroot cleans up and uninstalls all the stuff it installed as build deps21:05
macoi am confused by this definition of fail21:06
SpamapSmaco: it detected that ia64 was a failure and noted it for you.21:06
SpamapSthey've added fuzzy logic now.. if processor_architecture.value == 0: send fail email21:07
SpamapSia: can you paste a link to the build?21:08
macohttp://launchpadlibrarian.net/53949323/buildlog_ubuntu-lucid-ia64.skyeye_1.2.5-2ubuntu1.10.04.1_FAILEDTOBUILD.txt.gz21:09
gesermaco: the failure is "Function `get_sym' implicitly converted to pointer at utils/main/skyeye.c:20021:18
geser"21:18
geserthe source file is missing the prototype for the function21:18
macowhy is that so far after the "build successful" message?21:19
geserthe buildd scans the output for this and fails if it's found21:19
macoand that's a bit odd21:19
geseramd64 should fail the same way21:19
macosince its a no-change rebuild21:19
macoand the package it didnt change from /did/ build on ia6421:20
geserbut a lib might have changed between the time it got build last and now21:20
macowell i dont know about ia64, but amd64 does not fail in pbuilder21:21
maco...and actually on lp it did complete on amd6421:22
macohmm ...21:22
* maco goes back to calling it itanic21:22
geseryeah, hmm21:22
geserperhaps a header which doesn't get included on ia64 for some reason21:23
macoim glad amd64 won the 64bit market21:23
ScottKmaco: You can ignore ia64 anyway, it's about to be killed.21:25
ajmitchthe TB have spoken21:25
ScottKYep.21:25
* ScottK isn't sure why ia64 went along with sparc since it was still functional, but oh well.21:26
macowhich was still functional?21:26
ajmitchI think it wa sfunctional but noone was caring for it21:26
ScottKia6421:26
ajmitchbut it at least booted afaik21:26
* ScottK saw ia64 specific bugs reported by users as recently as Karmic.21:26
ScottKSo I think it even has a non-zero number of users.21:27
macoim surprised by that21:27
ScottKBut it's decided now anyway.21:27
macodo they even sell itanium hardware anymore?21:27
macoi saw it for like 6 months then people realised they couldnt use 32bit windows on it, then it went away21:27
achianghp sells quite a bit of ia6421:27
macois that servers?21:28
achiangit only makes $10B / year for them21:28
ScottKYes21:28
macoah21:28
achiangactually, that number seems wrong, please ignore it21:28
* ScottK has a server running Hardy that has a motherboard/CPU that dates from 1999.21:28
mdkeslangasek: around?21:28
ajmitchperhaps the port can be revived if someone steps up to look after it21:29
* ScottK has another running Lucid from 2000.21:29
ScottKPerhaps, but restarting a port is hard.  Ask lamont about restarting hppa.21:29
* maco would use debian if the year starts with a 121:29
penguin42there are probably quite a few Ia64 workstations/small servers that geeks have managed to hang on to when the places they work were about to throw them out21:29
ScottKSince it's in Lucid, they'll be able to do it for another 3 - 5 years.21:30
penguin42or actually after they through them out :-)21:30
ScottKThe last Sparc installer that worked was Gutsy.  The last working system was, I think, Jaunty.  So it's in a very different situation.21:31
ajmitchmaco: what's wrong with using debian? :)21:32
ajmitchpenguin42: especially if they have shares in power companies21:32
macoajmitch: it's more about what's wrong with using ubuntu21:32
penguin42ajmitch: They make great heaters21:32
ajmitchmaco: if you have an ia64, the answer would be obvious :)21:33
macoajmitch: i was referring to ScottK's old machines21:33
macoi tried feisty on a c1998 machine. that was...on the edge of bearable21:33
ajmitchI had breezy on an old laptop with 128MB of RAM21:34
macoi doubt it could boot lucid..if i could find it21:34
ajmitchit was interesting21:34
macoetch + e17 was the fanciest thing i could run on it and still have enough ram available to run 1 app at a time21:35
ScottKUp through Hardy I have a laptop with 256MB of RAM I ran Kubuntu on (and even built packages)21:35
ScottKhave/had21:35
* ajmitch would just like little things like suspend/resume to work on hardware from last year, let alone having an ancient laptop boot21:35
maco(er, ram+swap)21:35
macoajmitch: ancient things are more likely to work i think21:35
maconice old stable drivers21:36
ajmitchrather than using things like fglrx21:36
macoif it predates this wifi and bluetooth dohickeys, itll probably be happy :P21:36
macoScottK: did you have to install your own ethernet cards on those machines, or did they come with them?21:36
ScottKOne came with the other is home built, so I had to add it.21:37
ScottKThe laptop needed a PCMCIA ethernet card.21:38
ScottKErr wifi card.21:38
ScottKEthernet was built in.21:38
macoi think the WinME machine was the first we had that could do ethernet21:38
cjwatsonjibel: I think it might be dpkg breakage - I noticed it myself on different packages, but at the time put it down to the fact that I only restored this system from backup recently21:52
=== bjf is now known as bjf[afk]
=== blueyed_ is now known as blueyed
=== sconklin is now known as sconklin-gone
=== dendrobates is now known as dendro-afk
jdonghmmmmm23:57
jdongany way to debug when APT tells me "Hash Sum Mismatch" but I don't believe it?23:57
jdongthe Release file's md5sum and sha1sum listed for a Packages.bz2 matches what I get when I manually fetch the URL23:57
penguin42jdong: I've seen that type of thing happen with dodgy ram or other faults23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!