/srv/irclogs.ubuntu.com/2007/12/22/#ubuntu-devel.txt

slangasektjaalton: ah, ok; thanks for following up then :)00:16
=== Katze is now known as Shely
=== Shely is now known as Katze
lamontif I import a pdf in the gimp as layers, how can I save that such that I get a multi-page doc?01:38
nny_1why are 2.6.22-14 has no headers listed in hardy repos???02:06
nny_1er reformat02:06
nny_1why doesn't 2.6.22-14 have no headers in repos*02:07
nny_1lol close enough02:07
nny_1but yeah i can't build against the 2.6.22-14 kernel without source02:07
Hobbseewhy do you want to?02:09
nny_1Hobbsee: compile zaptel02:09
Hobbseeit's not the latest kernel...02:10
nny_1Hobbsee correct!02:10
nny_1Hobbsee but apt-get upgrade doesn't provide the 2.6.24-2, and i am having issues building zaptel with that kernel/source combo02:10
keescookHobbsee, can you look at the build failures of celestia 1.4.1+cvs20070626-3ubuntu3?  That's a transient problem, right?02:11
Hobbseenny_1: linux-headers-2.6.24-2 - Header files related to Linux kernel version 2.6.2402:11
Hobbseeappaers to be there02:11
nny_1yes, but not linux-2.6.22-202:12
nny_1er 2.6.22-14*02:12
nny_1and if i do an apt-get upgrade, which I assume means, latest suggested packages, it doesn't try to move the kernel up to the latest version02:12
nny_1so* I tried using it anyways, and it screamed02:13
nny_1make[2]: Entering directory `/usr/src/linux-headers-2.6.24-2-server'02:13
nny_1scripts/Makefile.build:46: *** CFLAGS was changed in "/usr/src/zaptel-1.4.7.1/Makefile". Fix it to use EXTRA_CFLAGS.  Stop.02:13
nny_1make[2]: *** [_module_/usr/src/zaptel-1.4.7.1] Error 202:13
nny_1make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-2-server'02:13
nny_1make[1]: *** [modules] Error 202:13
nny_1make[1]: Leaving directory `/usr/src/zaptel-1.4.7.1'02:13
nny_1make: *** [all] Error 202:13
nny_1gah02:13
nny_1dangit02:13
Hobbseeyeesh.  pastebin, perhaps?02:13
nny_1pidgin as an IRC client FTL02:13
nny_1Hobbsee: ya think? i wasn't intending for it to line break02:13
Hobbseeinstall it manually.  or install linux-headers-generic to automatically pick them up02:14
nny_1muwhaahaha02:15
nny_1nope02:15
nny_1  linux-headers-2.6.24-2 linux-headers-2.6.24-2-generic linux-headers-generic02:15
nny_1sigh.. so wait, hardy doesn't suggest I use the latest kernel, but gives me no method for compiling against the current one... this is a bug methinks02:15
Hobbseehardy does now.02:15
StevenKSo you edit that Makefile to use EXTRA_CFLAGS, not CFLAGS02:15
Hobbseeyou presumably don't have the latest package "linux" installed02:16
Hobbseeit's not a bug that you havent' gotten the correct metapackages installed (and yes, the dist-upgrader checks for this)02:16
slangaseknny_1: you're not going to get linux-headers-2.6.22-14 anymore, that's an old kernel.02:16
StevenKIt should still be linux-generic / linux-server, surely?02:17
nny_1StevenK: yeah was gonna do that.. but i have numerous other things to compile, and that error got me thinking otherwise.. trust me, i wouldn't use alpha for this if i didn't need something that was only in sid/hardy's repos AFAIK02:17
persiaHobbsee: Only upgrade-manager checks that.  Apt-get allows broken systems.02:17
StevenKnny_1: Then why not backport what you want to Gutsy? I would.02:17
nny_1ok well, i did an install, apt-get update, apt-get upgrade and this is what i have02:17
nny_1StevenK: i spent 9 hours trying to do that with the original dapper install, and it got angry...02:17
Hobbseepersia: this is true02:17
StevenKNote I didn't say Dapper02:18
nny_1persia: upgrade manager doesn't run on a server02:18
nny_1StevenK: indeed02:18
nny_1StevenK: mind you i am battling libsnmp9 badness02:18
nny_1heh who am I kidding, it's all a science project02:18
persianny_1: Good point.  Likely a bug.  I'll file that.02:19
StevenKUpgrade manager will be put into Dapper before Hardy releases02:20
nny_1persia: no problem, was only curious as to which version *I* should be using on server02:20
nny_1since there is no GUI on this box02:20
persianny_1: I tend to use aptitude for servers, but there ought be a CLI update-manager to make it easier.02:21
Fujitsuupdate-manager-core has the CLI one, doesn't it?02:21
nny_1StevenK: yeah i agree with the gutsy thing. this is more of, I had stable asterisk running on dapper, want to get snmp working for many many more servers later, figured since we only use LTS for these that Hardy alpha would be a good time to try it02:21
nny_1persia: noted.. i switch between aptitude and apt02:23
nny_1I assume the cflags issue means EXTRA_CFLAGS+=-DSTANDALONE_ZAPATA -DBUILDING_TONEZONE (added the EXTRA_)02:24
StevenKRight02:24
nny_1hrmm02:25
nny_1seems to be happier.. wait for it.. nope shoot02:25
nny_1same error02:25
nny_1let me see if their are other areas in the Makefile02:25
nny_1ahh foudn it my bad02:26
nny_1lol i don't even want hotplug support :\02:26
nny_1lol well heck02:37
nny_1i installed th enew image, but still running the old one02:37
nny_1lol reboot02:40
nny_1again02:40
nny_1:)02:40
DoubleDavegood evening everyone03:53
=== DoubleDave is now known as ubergoober
ubergooberl03:54
=== ubergoober is now known as DoubleDave
DoubleDaveanyways hows things in here tonight?03:54
=== stu1 is now known as stub
=== elkbuntu_ is now known as elkbuntu
=== bigon is now known as bigon`
=== rob1 is now known as rob
=== ubiq__ is now known as lucid
=== rob1 is now known as rob
warp10Hi all!06:31
=== \sh_away is now known as \sh
=== cassidy_ is now known as cassidy
=== \sh is now known as \sh_away
=== azeem_ is now known as azeem
=== bluekuja_ is now known as bluekuja
=== Lure_ is now known as Lure
=== \sh_away is now known as \sh
=== \sh is now known as \sh_away
=== bigon` is now known as bigon
=== \sh_away is now known as \sh
=== \sh is now known as \sh_away
=== Hobbsee_ is now known as Hobbsee
=== \sh_away is now known as \sh
=== \sh is now known as \sh_away
=== \sh_away is now known as \sh
* Hobbsee looks at celestia for keescook12:16
Hobbseekeescook: i'm hoping that's transient.  if not, i'll look at it again.12:17
ion_celestia has failed to upgrade for a while, but i haven’t got around to reporting a bug yet.12:21
ion_dpkg: error processing /var/cache/apt/archives/celestia-gnome_1.4.1+cvs20070626-3ubuntu2_i386.deb (--unpack):12:22
ion_ trying to overwrite `/usr/share/celestia/data/asteroids.ssc', which is also in package celestia-common12:22
persiaion_: The bug exists.  I'll dig it up for you.12:22
Hobbseedarn, it's not transient12:22
Hobbseehum, damh12:23
Hobbseeer, damn12:23
Hobbseewould probably be nice to do another upload for that12:23
persiabug #17657612:23
ubotuLaunchpad bug 176576 in celestia "package celestia-kde None [modified: /var/lib/dpkg/info/celestia-kde.list] failed to install/upgrade: trying to overwrite `/usr/share/celestia/data/asteroids.ssc', which is also in package celestia-common" [High,Fix released] https://launchpad.net/bugs/17657612:23
persiaHobbsee: Yes.  It needs versioned conflicts/replaces set properly.12:24
Hobbseeuhhhhhhhhhhh12:24
Hobbseecprov......12:24
Hobbseelamont: fairly urgent ping12:25
Hobbseethe buildds shouldn't be that empty, i'm sure12:27
Hobbseeunless everything is takign 40 seconds to fail12:27
ion_persia: Thanks12:27
Hobbseekeescook: okay, that looks like fairly big "Soyuz has FUBAR'd"-type problems.12:29
Hobbseebut damn, lamont had better like seeing the hppa's down to 0 builds.12:30
Hobbseekeescook: s/Soyuz/GNOME/12:33
geserHobbsee: looks like esound-common got lost in hardy12:42
* persia thought that was intentional, as part of pulseaudio-by-default12:42
Hobbseeso, uh, where is it?12:43
geserpersia: but then it makes libesd-alsa0 and libesd0 uninstallable12:43
FujitsuThat binary is still built.12:43
FujitsuI think Soyuz got confused.12:43
HobbseeFujitsu: well, exactly12:44
FujitsuIt doesn't seem to exist in the archive, but the SPR page says it does.12:44
geserand many packages still depend on libesd12:44
FujitsuBut that source has had bad things done to it.12:44
persiageser: In the case of libesd0, that's a good thing (in my book).  In the case of libesd-alsa0, perhaps it needs to be done differently.  Anyway, I see 0.2.38-0ubuntu4 in the pool.12:44
Fujitsugeser: Like libgnome, so the world has exploded.12:44
Hobbseesource hasn't appeared to change since gutys12:44
geserHobbsee: pitti moved libesd yesterday from main to universe and back to main12:45
geserperhaps soyuz ate it12:45
FujitsuThat's what I discovered and suggested in #launchpad... I don't think Soyuz liked it much.12:46
Hobbseeohhh.....12:46
FujitsuThat binary has vanished.12:46
persiaHrm.  pulseaudio-esound-compat Provides; esound.  Perhaps that's insufficient.12:46
HobbseeFujitsu: what's the status of the build?12:46
Fujitsupersia: esound-common12:46
HobbseeFujitsu: failed to upload, by any chance?12:46
FujitsuHobbsee: What build?12:46
Hobbseeesound, i think12:46
HobbseeFujitsu: or anything that built that depended on it12:46
persiaFujitsu: That's just documentation, and doesn't have an rdepend from gnome from my cache.12:47
Fujitsu  libesd0: Depends: esound-common (>= 0.2.38-0ubuntu4) but it is not installable12:47
* Hobbsee wonders what happens if you rebuild libesd012:47
geserFujitsu: not only Gnome broke on the missing esound-common but also KDE12:48
Fujitsugeser: Yay.12:48
* persia suggests replacing libesd0 with something else. Purging the package doesn't break GNOME.12:48
* Hobbsee ponders uploading a no-change-rebuild, and seeing what happens12:49
FujitsuI suspect Soyuz didn't process-deathrow before it was repromoted.12:49
Hobbseeno idea.  you're hte soyuz expert.  but that sounds possible12:49
FujitsuSo it might have seen the existing binary record in main, and not overwritten it, so it then got removed.12:49
* Hobbsee thought deathrow was used for removed packages, not demoted ones12:50
FujitsuI bet everybody's off and uncontactable for Christmas too :P12:50
geserHobbsee: either it breaks further more (in which case you have a week to fix it) or it works again12:50
FujitsuHobbsee: The binaries were removed. From a component.12:50
HobbseeFujitsu: oh, point.12:50
* Hobbsee grabs source12:50
FujitsuA no-change rebuild should probably fix it - if only by getting the binary republished.12:51
Fujitsu(of esound)12:51
FujitsuPoking a Soyuz person is probably better, though.12:51
Hobbseethey won't be around for the next week, at least.12:51
* Hobbsee uploads12:52
geserdoes it need to go through binary NEW?12:52
HobbseeFujitsu: worthy of a soyuz bug, though12:52
FujitsuThat's no problem for Hobbsee.12:52
Hobbseegeser: shouldn't do.12:52
Hobbseegeser: but, i can accept from there anyway12:52
Hobbseeshouldn't, as it's my own upload.  but can.12:53
FujitsuHobbsee: Sure, but I'll poke more thoroughly first.12:53
Hobbseegeser: why would it?12:53
Hobbseeoh, yes, it might get chucked there, i guess12:53
Fujitsugeser: I think the binary still exists, just the publishings are deleted.12:55
* Hobbsee taps fingers, waits for queue builder13:05
geserHobbsee: could you also give-back kdmtheme rhythmbox gnomebaker mrwtoppm empathy once esound-common is back?13:13
Hobbseegeser: i'd be in favour of getting someone to call cprov or something, and getting him to do a mass giveback before christmas.13:14
Hobbseethen let the buildds sort it all out over the break13:14
Hobbseeright.  now we have esoudn common.13:42
=== \sh is now known as \sh_away
=== \sh_away is now known as \sh
seb128Hobbsee: what was this esound upload?13:56
Hobbseeseb128: a soyuz bug.13:56
Hobbseeseb128: it ate the binaries13:56
seb128Hobbsee: has that been confirmed as a soyuz issue?13:57
seb128Hobbsee: what binary has been eaten by soyuz there?13:57
* Hobbsee ponders what to answer to that13:57
Hobbseeseb128: esound-common13:57
Fujitsuesound-common vanished from the archive after a rather odd sequence of events on its source package.13:58
seb128Hobbsee: pitti demoted esound yesterday, are you sure that the binary is not just to universe?13:58
seb128did you speak about somebody from the soyuz team about the issue?13:58
Hobbseeseb128: based on how it just ended up in new, it's probably a reasonably safe assumption that it wasn't in universe.13:58
Hobbseeseb128: and it's not in apt-caches, etc, so not in the recently published universe lists13:59
FujitsuNor rmadison.13:59
seb128ok, did you raise the issue to the soyuz team before trying to workarouding it?13:59
Hobbseeseb128: no13:59
seb128grr13:59
Hobbseeseb128: although Fujitsu filed a bug.13:59
Hobbseeseb128: it's a sunday, and it's the 23rd of december.  last i checked, they'd all left for holidays, haven't they?14:00
\shHobbsee, 22nd of Dec14:00
seb128Hobbsee: it's saturday in most timezones and in holidays != vanished14:00
Hobbsee\sh: 23rd here, but granted.14:00
seb128I'm on holidays and I'm still reading mails ;-)14:00
Hobbseeyou and Riddell appear to be the exception14:01
StevenKSuch dedication14:01
StevenKOr insanity, either way14:01
seb128and StevenK ;-)14:01
FujitsuErgh, they're multiplying!14:01
HobbseeRiddell: had a meeting14:01
Hobbseeso he's excepted14:01
StevenKI'm not reading e-mail, I'm heckling14:01
seb128Hobbsee: I'm not that sure, I think several people read mails every now and then14:01
StevenKI'd do more fftw3-dev rebuilds, but slangasek might hate me14:02
StevenKWait, he won't. Alpha 2 is out the door.14:03
HobbseeStevenK: it's not a freeze now14:03
Hobbseebut, do check to see if esound and friends are all happy now, so thinks don't fail14:03
StevenKseb128: Did you see gimp in -proposed?14:03
seb128StevenK: I've read the -changes mails14:03
seb128StevenK: look like you didn't try building the update? ;-)14:03
StevenKShush. :-(14:04
seb128Hobbsee: there is no esound in NEW14:04
Hobbseeseb128: yes, i know.14:04
seb128nor glib2.0, weir14:05
seb128weird14:05
* Hobbsee wasn't aware that glib2.0 should be in NEW14:05
seb128Hobbsee: there is a new libgio-fam binary14:06
seb128it was built by an another source package before though14:06
seb128so it might not require NEWing14:06
Hobbseeseb128: looks like someone else approved it14:06
Hobbseeyeah, quite possibly.  it appears to be built from the right source nwo14:06
seb128Hobbsee: what about esound?14:06
Hobbseeunless i'm incompetent using my tools, of course.14:06
seb128and somebody retried the rhythmbox build14:06
Hobbseeseb128: it was in new.  it's now not14:06
seb128but that still didn't work due to esound14:07
Hobbseeahh, yes, so this is how you found out to come and yell at me.14:07
Hobbseethis is true.  wasn't sure if it was transient, as keescook asked me to check a similar failure14:07
seb128Hobbsee: no, I started IRC because I read the hardy-changes mails14:07
seb128I asked pitti to retry the rhythmbox build yesterday already14:07
Hobbseeyes, and it failed.14:08
seb128since it failed because libesd0 was in universe14:08
Hobbseei retried it today, adn it also failed, so some of us in here debugged the problem.14:08
seb128right14:08
* Hobbsee is not *that* incompetent, FYI.14:08
seb128Hobbsee: well, we were debugging the problem yesterday already14:08
seb128and that's something that should not require a new upload14:08
seb128but should rather be fixed at the archive level14:08
Hobbseenext week.14:08
seb128the week after that most likely14:09
* Fujitsu notes that all is good now, anyway.14:09
seb128everybody is on holidays next week ;-)14:09
Hobbseeso, 2 weeks.14:09
FujitsuSo we have half of main uninstallable for two weeks, yay.14:09
* Hobbsee notes that some people *might* actually care about building anything GUI-related in the next 2 weeks.14:09
seb128Fujitsu: I though all was good now?14:09
seb128Hobbsee: I'm pretty sure that people would reply to mails14:10
Fujitsuseb128: I meant in the scenario where no rebuild occurred, sorry.14:10
Hobbseeseb128: it is now, after my upload, which you're telling me that i shouldn't have done.14:10
seb128I for one joined IRC14:10
seb128and I think that if somebody mail pitti he's likely to show up today14:10
* Hobbsee notes that he, in all likelyhood, could not fix it, if it's a soyuz bug?14:11
seb128but right, the bug has been workarounded so there is no hurry now14:11
seb128Hobbsee: well, there is often way to workaround soyuz issue as archive admins14:12
Hobbseeseb128: archive admins can republish removed binaries?14:12
seb128nothing is trashed14:12
Hobbseesure, it's still in librarian.  but it wasn't in hardy at all.14:12
seb128you just have to move the binaries from where they are to the right place back usually14:12
FujitsuThe binaries had been deleted. They weren't moved to anywhere.14:13
seb128Fujitsu: how do you now? uploads rejected are moved somewhere and not deleted for example14:13
seb128Fujitsu: are you sure they are not somewhere in the librarian?14:14
Fujitsuseb128: This was a legitimately superseded and subsequently `deleted' (although still in librarian) binary.14:14
FujitsuRIght, but can one recover them from there without being a god?14:14
* Hobbsee ponders the point of fishing for them in librarian, vs just reuploading, and taking 3 mins on all arches to build.14:14
seb128Hobbsee: well, the point is that there is a soyuz bug there14:15
Hobbseeseb128: https://launchpad.net/bugs/17810214:15
seb128Hobbsee: and sometime it's easier to debug things when they are still in a weird state than after workarounding14:15
ubotuLaunchpad bug 178102 in soyuz "(Quick) promotion and demotion can lose binaries" [Undecided,New]14:15
Hobbseeseb128: this can happen to any binary.  obviously, ones which do *not* cause mass uninstability would be good ones to test with14:15
Hobbseebut, i see your point14:16
seb128ok, I didn't know that was happening to any binary and easy to trigger since I didn't try14:17
seb128Hobbsee: thanks anyway to workarounding the issue ;-)14:17
Hobbseeseb128: you're welcome.  do you still think i'm incompetent?14:17
seb128Hobbsee: I didn't say or though that you are incompetent14:18
seb128I would just have tried to contact somebody from the soyuz team before workarounding the issue14:18
* Hobbsee normally would have14:19
seb128though admittedly that's not the best timing due to holidays14:19
* Hobbsee is aware of the time of year, etc, though.14:19
* Hobbsee has no contact phone numbers, etc, cprov is not talking, etc.14:19
Hobbseein fact, none are on irc at all, not even logging14:20
seb128no14:20
=== asac_ is now known as asac
* seb128 hugs Hobbsee14:20
seb128Hobbsee: sorry for ranting14:21
* Hobbsee continues to hide behind her seb-shield.14:21
* Hobbsee does not wish to be blasted again14:21
=== bigon is now known as bigon`
=== bigon` is now known as bigon
seb128Hobbsee: could you give an another rhythmbox build retry? ;-)14:22
\shhow lucky i am..wine needs libesd0 lol14:22
Fujitsuseb128: I wouldn't advise it for at least another 10 minutes.14:22
seb128Fujitsu: publisher is still running?14:22
Fujitsuseb128: Doesn't it normally finish around */45?14:23
seb128Fujitsu: ok thanks, no hurry there14:23
FujitsuErm, 20 minutes, then.14:23
Hobbseeseb128: yeah, but still waiting for the rest to publish.14:23
* Fujitsu can't count.14:23
Hobbseeseb128: btw, i also checked the scrollback, to see exactly what you guys had done, too.14:23
lamontHobbsee: sup?14:24
seb128Hobbsee: well, when I pinged pitti yesterday the issue was that libesd moved to universe14:24
seb128Hobbsee: we didn't notice any lack of binary there14:24
Hobbseeseb128: and it moved back.  as you would have seen, had you checked your aptcache.14:24
seb128Hobbsee: ?14:24
* Hobbsee isn't sure why it only ate that binary, and not the others, though14:24
seb128Hobbsee: an arch any or all issue?14:25
Hobbseelamont: can you do a mass giveback?14:25
lamontnope14:25
Hobbseeseb128: i don't know.  perhaps it is14:25
Hobbseelamont: do you have contacts for those who can?14:25
FujitsuThere are strange things done with arch: all domination.14:25
Hobbseelamont: it would be nice to do it over christmas14:25
Hobbseelamont: seeing as we have empty, waiting buildds14:25
lamontwell, there's the RSI-inducing button-clicking method...14:26
Hobbseeand no kde4 uploads :P14:26
seb128Hobbsee: what about my aptcache? pitti said he promoted the binaries again yesterday and after that we were on holidays, I didn't look at anything out of my mails today14:26
lamontthen what can: cprov, infinity14:26
Hobbseesarah@LongPointyStick:~% madison libesd0                                 1:06AM14:26
Hobbsee   libesd0 | 0.2.38-0ubuntu4 | http://mirror.internode.on.net hardy/main Packages14:26
Hobbsee   libesd0 | 0.2.38-0ubuntu4 | http://archive.ubuntu.com hardy/main Packages14:26
Hobbsee    esound | 0.2.38-0ubuntu4 | http://mirror.internode.on.net hardy/main Sources14:26
Hobbsee    esound | 0.2.38-0ubuntu4 | http://archive.ubuntu.com hardy/main Sources14:26
Hobbseelamont: right.  got contact #'s for either of them, to start it off?  (but wait till we've got some bits checked, that the esound stuff really has worked)14:26
Hobbseeseb128: ^ should have told you that it was in main again (source and binaries)14:27
lamontno14:27
Hobbseelamont: guess seb128 had better be begged to do it, then14:27
seb128Hobbsee: well, since pitti promoted it yesterday I though it would be there ;-)14:27
Hobbseeseb128: well, most of it is...14:27
seb128Hobbsee: what do you need now? build retries for what?14:28
FujitsuErmmm.14:28
seb128note that I'm not a buildd admin and can't do those14:28
FujitsuThis is odd.14:28
Hobbseeseb128: you have the great canonical phone directory.14:28
FujitsuSoyuz left the binaries that still exist in universe.14:28
HobbseeFujitsu: but didn't publish them?14:28
HobbseeFujitsu: where are you finding that info?14:29
FujitsuHobbsee: rmadison from an hour ago says -0ubuntu4 has esound binaries in universe.14:29
StevenKrmadison might be lagged more, though14:29
* persia notes that old binaries that aren't superceded by new versions for the same component and architecture have always seemed to benefit from manual poking.14:29
HobbseeFujitsu: when was that last updated, though?14:29
FujitsuHobbsee, StevenK: Recently enough that the esound-common one is missing.14:29
HobbseeFujitsu: wlel, we don't know if that one got nuked between main and universe, or universe and main.14:30
Hobbseeif it happened to get nuked btwn main and universe, that would still fit the problem14:30
Fujitsuseb128: Did somebody not knock the binaries back to main?14:31
seb128what binaries?14:31
seb128esound should be in universe14:31
seb128libesd should be in main14:31
FujitsuOhh.14:32
FujitsuI see, it is split. How confusing.14:32
FujitsuSo it's just the arch: all that is broken.14:32
\sh.oO(there should be someone doing lvl2/lvl3 on-duty call support somehow in between these peaceful days, no?)14:33
HobbseeFujitsu: so something strange happens to arch: all binary demotions / promotions.  got it.14:35
Hobbseeie, they vanish14:35
Hobbsee\sh: presumably, unless they presumed that no one would do any ubuntu development over christmas14:35
FujitsuYep. It may only occur when both are performed within a short window, but I'm not entirely sure of how the binary removals work.14:36
Hobbseeguess you'll find out14:36
\shHobbsee, well, it's the time of the year...all things which could get a bit messy are happening now14:37
StevenKLike Christmas shopping.14:37
* StevenK shivers14:37
Hobbseeurgh.  don't mention that14:37
FujitsuHah.14:37
* Hobbsee stabs stupid customers.14:37
\shor "hey, we are happy script kiddies, let's fck up some things" or "we produced a not known bug in our software..."14:38
geserseb128: run "rmadison esound-common", there is no entry for hardy14:40
seb128geser: is that a follow up on the discussion we just had on the chan or a new one?14:41
seb128esound-common | 0.2.38-0ubuntu5 |         hardy | all14:41
gesera followup14:41
seb128on drescher14:41
FujitsuAha, it's back!14:41
geserfor -0ubuntu4 there was no entry for hardy14:41
seb128geser: that's the bug we were speaking about and that Hobbsee workaround with the upload14:42
Hobbseegood, i'm glad it's back14:42
seb128workarounded14:42
geserand rmadison for mere mortals still shows -0ubuntu414:42
Fujitsuseb128: It's probably actually `worked around'14:42
seb128Fujitsu: thanks ;-)14:42
seb128geser: did you run apt-get update?14:42
Fujitsuseb128: rmadison uses a script on rookery.14:43
geserrmadison needs "apt-get update"?14:43
seb128ok, I don't use rmadison so I don't know14:43
seb128maybe rookery didn't update yet14:43
FujitsuI don't think anything but drescher will have updated yet.14:43
geserbut it's good that the lost binary is back again14:44
seb128Get:1 http://archive.ubuntu.com gutsy/main esound-common 0.2.38-0ubuntu4 [42.2kB]14:44
FujitsuGutsy, -0ubuntu4.14:44
seb128right14:45
seb128that's the current14:45
seb128still need to wait for an archive update14:45
seb128but since drescher has the new one that should be alright14:45
seb128let's wait for the next update14:45
* Hobbsee gives some packages back, and sees what happens14:48
FujitsuThey won't try to build for ages anyway.14:48
Hobbseewhy?14:48
FujitsuOh, I guess the builds will immediately be recreated, rather than having to wait for queue-builder like new ones.14:49
Hobbseerhythmbox has started14:49
FujitsuThat was quick.14:49
* Fujitsu watches.14:49
FujitsuAha, it worked.14:50
Fujitsukdmtheme got build-deps properly on castilla, at least.14:50
FujitsuAnd that was libesd0-dev.14:50
Hobbseelooks like libgpod-dev is dead on hppa14:50
FujitsuGet:1 http://ftpmaster.internal hardy/main esound-common 0.2.38-0ubuntu5 [42.3kB]14:50
FujitsuHobbsee: It *is* hppa...14:51
\shbut it's not published on archive.ubuntu.com?14:51
Hobbseeoh, that's depwaited14:51
Fujitsu\sh: No, that won't sync for a while, probably.14:51
\shcrap :(14:51
* Hobbsee wonders why sg3-utils failed to upload on hppa14:52
FujitsuHobbsee: When?14:52
HobbseeFujitsu: sg3-utils14:52
Hobbsee2007-11-2714:52
Hobbseeer, that14:53
Hobbseehum, 5 min build tim14:53
Hobbseee14:53
* Hobbsee hits retry14:53
FujitsuHobbsee: It was promoted on the 27th.14:53
Hobbseeahhh14:53
Hobbseeoh, so it was promoted14:53
Hobbseegood.  then it's fine to retry14:53
FujitsuDo you still have a page open from before you retried it?14:53
\shso no wine building...time to deal somewhat more with django14:54
HobbseeFujitsu: no14:54
Hobbseewhy, what were you looking for?14:54
FujitsuJust wondering what time it failed, but it was probably the promotion.14:54
Fujitsu\sh: It has hit a.u.c14:59
\shFujitsu, cool thx :)14:59
seb128Hobbsee: the rhythmbox build worked, you rock ;-)15:05
seb128ok, enough computer for now15:05
seb128see you later15:05
ion_“enough computer”?15:05
* ion_ has problems understanding the concept15:06
Fujitsuion_: You're not meant to understand it. It's a new Canonical plot to make our minds explode.15:06
Amaranthion_: I heard there is this place called 'outside'15:07
=== asac_ is now known as asac
AmaranthPerhaps he went there15:07
FujitsuAmaranth: Ah, another Canonical invention.15:07
* Fujitsu heads off to bed.15:08
ion_amaranth: This so-called “outside” is compatible with laptop computers.15:08
AmaranthNot if they have a glossy screen :P15:08
=== jpatrick_ is now known as jpatrick
\shhmm...15:32
\shlibesd0-alsa is still not installable...strange15:32
Hobbsee\sh: should be fixed15:32
\sh libesd0-dev: Depends: libesd-alsa0 (= 0.2.38-0ubuntu4) but it is not going to be installed or15:34
\sh                        libesd0 (= 0.2.38-0ubuntu4)15:34
\sh               Depends: esound-common (>= 0.2.38-0ubuntu4) but it is not installable15:34
\shjust updated the pbuilder15:34
persia\sh: Works from here, with updated cache.  Which mirror are you viewing?15:36
\shpersia, well, pbuilder is using archive.ubuntu.com but doesn't give me the used ip address from the RR15:37
Hobbsee\sh: out of date15:37
persia\sh: True.  Keep updating until it works :)15:37
pochuYay, works here too!15:37
* pochu thanks Hobbsee 15:37
Hobbsee:)15:38
Hobbseeahh, there we go.15:38
HobbseeTotals by arch:15:38
Hobbsee    * sparc:2915:38
Hobbsee    * i386:3815:38
Hobbsee    * amd64:3415:38
Hobbseeuninstallable from main ^15:38
Hobbseemuch better15:39
=== ubiq__ is now known as ubiq_
hilea question related to bug #500397: is it nautilus or gnome-vfs, which is deciding which inotify events are actually received by nautilus? i.e. are the events filtered somehow?18:31
hilehmpf, should have been on gnome-devel, nevermind18:31
spectiehey all, i'm a debian package maintainer for apertium, the version in debian is 3.0.5 and the version in ubuntu is 1.0.318:34
spectiethere is a lot of stuff that has changed in between the versions and i was wondering if it might be possible to accelerate the process of getting the new versions in ubuntu?18:34
spectieis there anything i can do to help etc. ?18:34
\shspectie, not true18:36
spectieoh ?18:36
spectiewhat is not true ?18:36
\shspectie, in our dev version apertium is http://packages.ubuntu.com/hardy/source/apertium18:36
keescookpersia: celestia> nah, that bug will be fixed when the most recent build finishes -- I made a weird mistake with the rules file18:36
pochu  apertium |    3.0.5-1 | http://archive.ubuntu.com hardy/universe Sources18:36
spectieaha cool18:36
Ubulette!info apertium hardy18:36
Ubulette(too slow)18:37
* keescook wanders afk again18:37
ubotuapertium: Shallow-transfer machine translation engine. In component universe, is optional. Version 3.0.5-1 (hardy), package size 251 kB, installed size 1044 kB18:37
spectie\sh, and when will that be in gutsy ?18:37
\shspectie, if then only via backports18:37
mjj29spectie: I assume it will never be in gutsy18:37
spectieok18:37
mjj29in the same way it will never be in etch18:37
pochuYou can request a backport if you want it in Gutsy. You will probably need some testing before it's approved.18:37
spectiewhat is the timescale of hardy being released ?18:38
Mithrandirspectie: https://wiki.ubuntu.com/HardyReleaseSchedule18:39
spectiecool thanks18:39
spectiei guess it would be worth requesting a backport18:39
spectieas 1.0.3 is probably broken by default18:39
spectie!info lttoolbox hardy18:45
ubotulttoolbox: Apertium lexical processing modules and tools. In component universe, is optional. Version 3.0.1-1 (hardy), package size 16 kB, installed size 100 kB18:45
spectie!info apertium-es-ca hardy18:48
ubotuapertium-es-ca: Apertium linguistic data to translate between Spanish and Catalan. In component multiverse, is optional. Version 1.0.5-2 (hardy), package size 778 kB, installed size 1700 kB18:48
Mithrandirspectie: if you're just looking for versions, rmadison -u ubuntu $package in Debian will tell you the relevant versions18:52
spectieaha thanks18:52
spectiei just finished18:52
spectiebut i'll remember in future18:53
Mithrandir(rmadison $pkg will give you the versions for Debian, but you probably knew that already)18:53
spectiefiled the request18:57
spectiethanks for your help18:57
Ubulettehmm, xine-lib 1.1.8-3ubuntu2 diff contains sources changes outside of debian/patches19:56
tuxistpromblems packaging flitghgear20:28
tuxisthttp://paste.ubuntu-nl.org/49344/20:28
tuxistanny sollutions20:29
\shtuxist, looks like a missing lib/shared object or whatever...20:30
tuxisti think it is problem in the header of libsgmisc20:31
\shtuxist, is it using simgear-dev?20:34
tuxistyes i have version 1.0.020:34
\shtuxist, the version in hardy is still 0.3.10-2 for simgear0...so it could be that flightgear needs a newer version of simgear20:36
tuxisti have installed allready the new vrsion20:36
tuxistyes i have version 1.0.020:36
\shtuxist, so you are sure that your flightgear package is including the correct simgear package? :)20:37
tuxist./configure --prefix=/usr20:37
\shtuxist, so you just compile the source...but you didn't packaged it...20:37
tuxistwhen have compiled the package i start packaging20:38
tuxistsucsessful20:38
tuxist;-)20:38
\shtuxist, well, if you use pbuilder for building the package...you need to make sure that pbuilder is getting the 1.0.0 package of simgear and not the provided package from <insert your ubuntu release here>20:39
tuxisti have the problem broken script20:42
tuxistthanks20:42
tjaaltonwhich package is responsible for the debug output on vt8?21:21
tjaaltonnevermind21:26
ion_Probably PEBKAC, but it seems as if fglrx in hardy doesn’t support Xv.22:54
=== \sh is now known as \sh_away
ion_Huh. The tubes claim that i can only choose OpenGL acceleration *or* Xv acceleration. Way to go, ATI! :-P22:58
ion_After modifying xorg.conf, both seem to work after all.23:05

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