[07:17] <didrocks> good morning
[07:45] <dholbach> good morning
[07:56] <G> dholbach: hey
[07:56] <G> dholbach: you are part of the Server Team right?
[07:56] <dholbach> g: no, I'm not
[07:57] <G> oh okay :)
[07:57] <G> dholbach: sorry, I'd just thought your name had come up in the meeting minutes
[07:58] <dholbach> I'd be a bit surprised - I hope they didn't assign me work while I wasn't there :)
[08:17] <Besogon> hi. Could you tell me how a package deletes menu files as my package don't delete them
[08:22] <Besogon> hey
[08:23] <Besogon> What rule does tell to the debuilt how exactly my packaged shoul be removed
[08:23] <Besogon> should
[08:26] <G> dholbach: haha sorry, obviously I've got names confused (or a more possible case, I am completely confused about everything :)
[08:28] <dholbach> G: no worries :)
[08:35] <pitti> Good morning
[08:35] <geser> Guten Morgen pitti
[08:36] <pitti> mr_pouit: great to hear, thanks
[08:36] <pitti> hey geser, good morning
[08:37] <Besogon> people, to delete menu files I should write postrm file, will I?
[09:39] <Besogon> рудз
[09:40] <Besogon> help
[09:40] <Besogon> need advise about build deb. postrm script
[09:44] <Besogon> No one alive
[09:48] <pitti> Besogon: you don't need to remove files from a package in maintainer scripts
[09:49] <pitti> uninstalling a package will remove all files that it ships
[09:50] <OdyX> pitti: Hi, just saw your comments on usb-modeswitch. Thanks for the investigation, I wrongly assumed udev versions in Debian and Ubuntu were close.
[09:52] <OdyX> pitti: is it possible to get a fix in udev by adopting Debian's patch or would you prefer to get an Ubuntu-specifically updated usb-modeswitch ?
[09:52] <Besogon> pitti, I'm trying to build a package and install some menu file
[09:53] <Besogon> also as deinstall them
[09:53] <Besogon> the deb package can install menu files using makefile but not uninstall them
[09:53] <Besogon> which script should I use to do that
[09:53] <azeem_> 10:47 < pitti> uninstalling a package will remove all files that it ships
[09:53] <Besogon> pitti,
[09:54] <Besogon> postrm or prerm
[09:54] <azeem_> 10:47 < pitti> Besogon: you don't need to remove files from a package in maintainer scripts
[09:56] <pitti> OdyX: both sid and Maverick have udev 161
[09:56] <Besogon> azeem_, so how can I do that in other way. *.menu and *.desktop files aren't deleted bu dpkg.
[09:56] <pitti> OdyX: how does Debian modify udev to make this work?
[09:57] <OdyX> pitti: there is a patch that adds that /lib/udev/hotplug.functions
[09:57] <azeem_> Besogon: then this would be a bug in dpkg
[09:57] <OdyX> (in Debian)
[09:57] <azeem_> Besogon: they are shipped in the .deb?
[09:57] <pitti> OdyX: ah, I see; that's what provides wait_for_file()
[09:57] <OdyX> exactly
[09:58] <tkamppeter> pitti, hi
[09:58] <Besogon> azeem_, no. But they are being installed indeed. I used a manual https://wiki.ubuntu.com/PackagingGuide/Complete
[09:58] <azeem_> how are they installed?
[09:58] <pitti> hey tkamppeter, how are you?
[09:58] <Besogon> azeem_, debuild utility
[09:59] <azeem_> debuild builds .debs
[09:59] <Besogon> azeem_, give me a secon
[09:59] <Besogon> d
[09:59] <azeem_> either they are shipped in the .deb, or they are somehow installed at install time
[09:59] <tkamppeter> pitti, fine.
[09:59] <OdyX> pitti: I am considering "conditional patching" based on dpkg-vendor, but a fix in udev is cleaner (for me) :-)
[09:59] <azeem_> Besogon: maybe they are not shipped, and the files you have on your harddisk are from a previous manual install
[10:00] <pitti> OdyX: how does upstream usb-modeswitch handle that? hotplug.functions isn't something that upstream could rely on?
[10:00] <OdyX> pitti: it does not, it uses the wait_for_file function "inline"
[10:01] <pitti> OdyX: and you don't want to just use that in usb-modeswitch?
[10:01] <OdyX> pitti: I am at fault on that bug, because I wanted to play smart and avoid code duplication by using Debian's functions.
[10:01] <OdyX> pitti: nah, on Debian it's a code duplication.
[10:01] <pitti> OdyX: well, it's not really "at fault"
[10:01] <Besogon> azeem_, no. I tryed to install and uninstall the files some times. This files are installed but they are not shown in dpkg -L and not deleted
[10:01] <pitti> OdyX: I don't mind much adding that file to our udev package
[10:01] <Besogon> azeem_, http://pastebin.com/1cPmJssS
[10:01] <Besogon> azeem_, this is my makefile
[10:02] <tkamppeter> pitti, I can reduce the default installation by another 18 MB, replacing the Foomatic data in /usr/share/foomatic by another compressed PPD package.
[10:02] <OdyX> pitti: AFAIK, alsa-utils uses it too (hence patched in Ubuntu)
[10:02] <pitti> tkamppeter: niice!
[10:02] <OdyX> pitti: or I can do conditional patching (almost done now ;-) )
[10:02] <azeem_> Besogon: then they are likely from a manual install and not a packaging issue
[10:02] <Besogon> azeem_, all after string 19 are not shown in deb
[10:02] <pitti> OdyX: nah, if this breaks several packages, I'll just add it to our udev
[10:02] <pitti> seems easier than playing catch-up
[10:03] <ion> Here’s an inotify-based wait-for-file, but in its current incarnation it requires the directory in which the file is supposed to appear to exist. http://github.com/ion1/wait-for-file
[10:03] <tkamppeter> pitti, main disadvantage is that the package foomatic-db will take 2 hours to build on my box (generate all PPDs and then compress them).
[10:03] <OdyX> ion: Debian's udev's wait_for_file is useful at boot time, to wait on /usr to be mounted e.g.
[10:03] <tkamppeter> pitti, but this will not be a problem for the end user.
[10:04] <Besogon> azeem_, what is a manual install?
[10:04] <OdyX> tkamppeter: why are you generating the PPDs again ? didn't we decided to get rid of the prebuilt ones ?
[10:04] <azeem_> Besogon: running "make install" as root
[10:04] <azeem_> outside of debuild
[10:04] <azeem_> with /usr as prefix
[10:05] <pitti> OdyX: hm, which bug # was that again?
[10:06] <tkamppeter> OdyX, I am looking into making Foomatic faster and less space-consuming. So I have tested building all PPDs and compressing them with pyppd, as the XMLs take space and the listing of all PPDs via "lpinfo -m" is slow.
[10:06] <pitti> OdyX: so we'll reassing that to udev and I'll ship the file in udev; sounds ok?
[10:07] <pitti> OdyX: bug 625110  is most likely a dupe?
[10:07] <Besogon> azeem_, ok. Now I've looked through the alacarte and found none of this files. Now I'm making sudo debuild
[10:08] <pitti> OdyX: nevermind, got the bug mail
[10:08] <OdyX> pitti: fixing that in udev seems very fine to me. Thanks in advance !
[10:08] <tkamppeter> OdyX, my plans are adding a binary package named foomatic-db-compressed-ppds to the foomatic-db source package keeping all other binary packages. The distro can then decide to use foomatic-db-engine plus foomatic-db OR foomatic-db-compressed-ppds.
[10:08] <pitti> OdyX: ok, great!
[10:09] <tkamppeter> OdyX, note also that foomatic-db-compressed-ppds will NOT contain foomatic-rip.
[10:09] <OdyX> tkamppeter: so that would be a re-introduction of foomatic-filters-ppds we had before, right ?
[10:11] <Besogon> azeem, in tmmfortran-1.0/debian I don't see menufiles.
[10:11] <azeem> Besogon: I don't have time to look into this, sorry
[10:11] <Besogon> azeem, pity
[10:11] <tkamppeter> OdyX, not really, as foomatic-rip will not be contained in the package.
[10:12] <Besogon> Who can help me with makefile and building deb file
[10:13] <tkamppeter> OdyX, my former abolishing of foomatic-filters-ppds was the huge waste of space of uncompressed or individually gzipped PPD files. I completely underestimated the great compression potential of pyppd, which was not ready that time.
[10:16] <Besogon> aha I undestand
[10:17] <tkamppeter> OdyX, using foomatic-db-compressed-ppds instead of foomatic-db and foomatic-db-engine saves 18 MB on an installed system (great for live CDs) and listing all Foomatic PPDs gets vastly faster, even faster than serving the Foomatic database from MySQL.
[10:18] <OdyX> tkamppeter: nice.
[11:29] <Besogon> hey. I return
[11:29] <Besogon> back
[11:29] <Besogon> Why a package I made don't copy a file in etc directory?
[11:30] <Besogon> I see it file in the list dpkg -L
[11:31] <Besogon> But actually the one wasn't copied
[11:31] <Besogon> What does it mean?
[11:33] <ion> It’s so bright and vivid. It’s almost starting to look like a triple rainbow.
[13:04] <AnAnt> Hello, could someone approve: LP #626711
[13:29] <pitti> AnAnt: done
[13:30] <AnAnt> pitti: thanks
[13:30] <AnAnt> pitti: & thanks for texlive-bin too
[13:52] <oubiwann> pitti: hey man, I'm trying to run apport-collect <bug number>
[13:53] <oubiwann> pitti: but I'm a beta tester, so I get edge
[13:53] <oubiwann> pitti: and as a result, an ncurses login screen
[13:53] <oubiwann> pitti: but I can't continue in the ncurses view, once I enter my email/pass
[13:53] <oubiwann> pitti: any clues, hints, etc.? or is this a known bug?
[13:54] <pitti> oubiwann: ncurses login? that's new
[13:54] <pitti> oubiwann: last time I had this, it just opened a page in my browser
[13:54] <pitti> oubiwann: oh, are you in a chroot or something without firefox?
[13:54] <pitti> oubiwann: ncurses login screen> that's w3m or so?
[13:54] <oubiwann> pitti: ssh connection, yeah
[13:55] <oubiwann> pitti: yeah, looks like it... maybe links/lynx
[13:55] <pitti> oubiwann: then it's better to open the URL that it prints out locally
[13:59] <ogra_cmpc> oubiwann, there is a bug about LP login not working with w3m iirc (dont ask me about the bug # though)
[13:59] <oubiwann> ogra_cmpc: sweet, thanks
[14:05] <barry> hi folks, i'm having an odd problem updating one of my early maverick machines and i'm wondering 1) if this is a bug worth reporting/investigating; 2) what's the safest way to fix the problem
[14:07] <barry> i have both libgirepository1.0-0 and -1 installed apparently.  the former has a [!] icon in synaptic (not sure exactly what that means).  apt-get, update-mgr, and landscape all fail to update the machine because of this.  if i explicitly mark the -0 for reinstallation, apt wants to remove a *ton* of packages, which i'd rather not let it do ;)
[14:08] <seb128> libgirepository1.0-0 is deprecated
[14:08] <seb128> nothing should depends on it
[14:08] <barry> seb128: yep, you see my problem :)  it appears as though a ton of things do depend on it
[14:09] <seb128> doubteful
[14:09] <seb128> sudo apt-get remove libgirepository1.0-0
[14:09] <seb128> what does that want to do?
[14:10] <barry> seb128: hmm, it looks like it just wants to remove that one package.
[14:10] <seb128> see ;-)
[14:10] <seb128> dunno why update-manager would fail on that
[14:10] <barry> seb128: u-m, landscape, *and* synaptic ;)
[14:10] <seb128> what does apt-get dist-upgrade say?
[14:11] <barry> nothing to do
[14:11] <barry> let's see what u-m says now
[14:12] <seb128> what version of libgirepository1.0-0 did you have?
[14:12] <barry> seb128: it was 0.6.something iirc.  seems like doing the manual removal has made at least u-m and synaptic happy again
[14:13] <barry> seb128: i need to reboot that machine and then we'll see if landscape is happy to
[14:14] <barry> very odd though; i was sure i tried an apt-get remove and saw tons of other removals.  maybe it was apt-get install --reinstall tho.  seb128 thanks
[14:14] <seb128> np
[14:22] <tkamppeter> OdyX, ping
[14:28] <OdyX> tkamppeter: pong
[14:29] <tkamppeter> OdyX, was there ever a foomatic-db package in Debian which provided the foomatic-filters-ppds package?
[14:30] <OdyX> tkamppeter: Lenny (current stable) has f-f-ppds, built from src:foomatic-filters-ppds. Squeeze had foomatic-filters-ppds built from foomatic-db-engine and now ships it as a "dummy" package
[14:32] <tkamppeter> OdyX, I am looking into pre-building the PPDs from the build of foomatic-db without duplicating upstream source code and without modifying foomatic-db-engine upstream.
[14:33] <OdyX> tkamppeter: then you need to B-D on foomatic-filters, right ?
[14:33] <tkamppeter> OdyX, looks like that I have to build foomatic-db-compressed-ppds out of the foomatic-db-engine build then.
[14:34] <tkamppeter> OdyX, foomatic-filters is never needed to pre-build the PPDs.
[14:34] <OdyX> tkamppeter: you may want to take a look at the git history of foomatic-db-engine
[14:35] <OdyX> http://git.debian.org/?p=collab-maint/foomatic-db-engine.git;a=commitdiff;h=2254476
[14:35] <tkamppeter> OdyX, problem is that a foomatic-db-engine installed into the system by BD can only build PPDs from the XML data installed into the system, not from the XML data in the current package's source tree.
[14:36] <OdyX> huh, sucks....
[14:44] <tkamppeter> OdyX, thanks for the link.
[15:05] <G> zul: do you happen to be around by any chance?
[15:05] <zul> G: yes
[15:05] <G> zul: hey, I noticed that the Server Team seems to have a slightly different SRU policy for accepting packages
[15:05] <zul> G: yeah
[15:06] <G> zul: regarding something like Bug 589063 (I believe libvirt/KVM etc falls under Server), whats the best way to get it 'accepted'?
[15:07] <zul> G: send a note to the ubuntu-sever mailing list
[15:07] <G> zul: so, as a reply to the e-mail you send out weekly?
[15:07] <zul> G: yep
[15:11] <G> zul: argh, server-list doesn't have reply mugging
[15:12] <G> zul: sorry for the fact you'll get it twice
[15:12] <zul> G: thats fine
[15:13] <G> zul: okay there we go, thanks
[15:13] <zul> G: no problem
[15:15] <G> zul: I'd been working off the main SRU policy, didn't realise (actually more like forgot) that there was a seperate Server policy :)
[15:19]  * G has a poke at other virt bugs
[16:00] <G> zul: btw, whats the process for getting fixes into maverick at this stage as well
[16:00] <zul> G: open up a bug
[16:00] <G> bug already exists
[16:01] <zul> G: then someone should be already looking at it
[16:01] <G> zul: okay, (just isolating a patch for the bug atm)
[16:02] <zul> G: bring it up on #ubuntu-server
[16:02] <G> zul: okay will do
[16:27] <theclaw> hi
[16:29] <theclaw> I have a package with executables, and want to create a package with debugging symbols of those executables; however, if I use dh_strip --dbg-package, it strips the executables, making them non-executable
[16:29] <theclaw> any idea how to fix this?
[16:35] <penguin42> theclaw: Has it also created separate -dbg debs ?
[16:36] <theclaw> penguin42: yes
[16:36] <penguin42> I *think* those should have the debug symbols
[16:36] <theclaw> penguin42: "file /path/to/debugbin" says "... not stripped", "file /path/to/normal_bin" says "... stripped"
[16:37] <theclaw> (I said "strips" above when I should have said "doesn't strip", sorry)
[16:38] <theclaw> do executable files have to be stripped so that they can be executed?
[16:38] <penguin42> no
[16:39] <penguin42> and stripping shouldn't change whether it can execute
[16:40] <theclaw> hmm.
[16:46] <ScottK> didrocks: Your ubuntu-netbook-default-settings upload will affect U/I, right?
[16:47] <didrocks> ScottK: one of the icon will slightely change and nautilus removal in the installation, right. the issue is that it will probably change again later as we don't have the list of things to display by default (and it's an issue, I agree)
[16:48] <ScottK> didrocks: My understanding is that post U/I freeze such changes need an FFe with an ack from the docs team.
[16:48] <ScottK> Mostly so they know not to do any screenshots of that yet.
[16:49] <didrocks> ScottK: I wasn't thinking it was such impacting. I was planning to send an email to them as we will likely have some changes in any case. Thanks for the reminder.
[16:50] <ScottK> didrocks: Please open an FFe bug (feel free to say all the planned changes) and subscribe them.
[16:50] <didrocks> ScottK: doing it now, ubuntu-docs is the team, right?
[16:50] <ScottK> didrocks: AFAIK, yes.
[16:50] <didrocks> ScottK: thanks, doing it
[16:50] <ScottK> didrocks: Do you mind reuploading with the FFe bug in debian/changelog?
[16:51] <didrocks> ScottK: sure, if it's not accepted already?
[16:51] <ScottK> It's not.
[16:51] <ScottK> I'll reject so you can reupload.
[16:51] <didrocks> ok, great :) thanks
[16:52] <didrocks> well, once launchpad won't timeout again ::
[16:52] <ari-tczew> https://code.launchpad.net/~ubuntu-branches/ubuntu/maverick/avogadro/maverick
[16:52] <ari-tczew> hmmm, why latest release has dated earlier than previously?
[16:53] <graphitemaster> hey why can't I request anymore CD's?
[16:54] <graphitemaster> i used to request everytime a new version came out, my internet is not the fastest ya know, it's bad enough it takes me two months to download an iso
[16:56] <tkamppeter> OdyX, I have solved my problem, one can redirect to an alternative XML database via the env variable FOOMATICDB with all tools of foomatic-db-engine.
[17:03] <didrocks> ScottK: reuploaded
[17:11] <penguin42> is it possible to build i386 packages on x86-64 using pbuilder or the like?
[17:19] <ScottK> cjwatson: Your blog post on grub2/windows made the news picks section on http://www.groklaw.net/
[17:22] <geser> penguin42: yes, if you have an i386 pbuilder
[17:23] <penguin42> geser: Ah so just pubilder --architecture i386 ?
[17:25] <geser> yes
[17:27] <penguin42> nice, I'm jsut building a modifed Maverick Mesa that fixes a radeon issue, and it works great, but Google-earth is 32bit
[17:47] <didrocks> ScottK: will you have the time to accept the -settings package (would be nice to have it for tomorrow respin image)
[17:47] <ScottK> didrocks: Need to get an ack from the docs team first.  Maybe you can find someone to look at it.
[17:55] <tkamppeter> OdyX, I succeeded to make a foomatic-db package with foomatic-db-compressed-ppds now.
[18:00] <didrocks> ScottK: I still wonder as I've seen no UNE documentation. Don't know who can give such an exception for it
[18:01] <ScottK> didrocks: I'm not sure, but I'd ask someone on the docs team.  If they aren't doing docs, then just them saying that is more than enough.
[18:01] <didrocks> mdke: do you know if there are some people working on UNE documentation? seems not (asked to some doc core team member as well and they don't know) ^
[18:02] <seb128> didrocks, what did you change?
[18:02] <didrocks> seb128: just added the evo express icons in the launcher and removed nautilus. Still not the definitive launcher in any case
[18:10] <seb128> ScottK, you need an ack from the documentation team?
[18:11] <ScottK> seb128: Post U/I freeze for things in Main we normally do that.
[18:11] <seb128> ScottK, https://wiki.ubuntu.com/FreezeExceptionProcess doesn't say that
[18:11] <seb128> "Every change of the user interface (either a string or the layout) requires you to notify the documentation and translation teams. Please include a link to these posts in the mailing list archives of ubuntu-doc@ and ubuntu-translators@. "
[18:11] <seb128>  
[18:11] <seb128> it says to notify and subscribe ubuntu-release
[18:11] <seb128> it doesn't say you need to wait for them to ack the change
[18:12] <ScottK> Actually that's right.  Thanks for pointing it out.
[18:12] <ScottK> Now that they've been notified, I'll accept it
[18:12] <seb128> ScottK, thanks
[18:12] <didrocks> thanks seb128 and ScottK :)
[18:12] <seb128> yw
[18:13] <ScottK> didrocks: Accepted.  In the future, please inform them before upload on post-U/I freeze changes that affect U/I.
[18:14] <didrocks> ScottK: sure, will do for upcoming changes, thanks for the notice
[18:21] <penguin42> 32bit pbuilder worked nicely - thanks!
[18:58] <seb128> slangasek, review of ubuntu-sso-client would be appreciated by the u1 team I think
[18:59] <seb128> it fixes some bugs which break clients right now
[18:59] <seb128> slangasek, the rhythmbox upload fixes a crash which seems to happen to quite some users
[18:59] <seb128> if you can review that as well
[18:59] <seb128> thanks
[18:59] <neeraj> for bug 511225, should I file a ff'e request separately?
[19:03] <tkamppeter> OdyX, ping
[19:04] <OdyX> tkamppeter: pong
[19:10] <slangasek> seb128: accepted both
[19:10] <tkamppeter> OdyX, I have created the foomatic-db-compressed-ppds now and it is working nicely. I made it conflicting with foomatic-db-engine to avoid duplicate PPD entries which deliver PPDs from different data sources. My problem is now to make updates from Lucid to Maverick smoothly migrate.
[19:12] <OdyX> tkamppeter: for sweet upgrades, you should look after "Provides" (which only works if the relationship is non-versioned)
[19:17] <tkamppeter> OdyX, to let the update only happen in Ubuntu I thought about replacing foomatic-db, foomatic-db-engine in the dependencies of ubuntu-desktop by foomatic-db-compressed-ppds, does the conflict of foomatic-db-compressed-ppds with foomatic-db-engine remove foomatic-db-engine then?
[19:18] <OdyX> tkamppeter: IMHO you should leave the choice. That means using "Provides" and converting "Depends" or "Recommends" into alternative relationship, with the one you want first..
[19:19] <OdyX> tkamppeter: but the answer to your question is probably yes.
[19:20] <tkamppeter> OdyX, Ubuntu is CUPS-only, there it is no problem to make the default installation to use a CUPS-only solution. In Debian I want to leave the choice.
[19:20] <slangasek> seb128: do you know why gir-repository ftbfs now?  (looks for vte headers in the wrong path; wants rebuild to get rid of dep on libavahi-core6)
[19:20] <OdyX> tkamppeter: I mean leaving the choice between compressed and non-compressed
[19:20] <OdyX> tkamppeter: but I agree with your strategy.
[19:24] <seb128> slangasek, no but I will get it fixed, thanks for pointing it
[19:25] <slangasek> seb128: looks like pkg-config --variable=includedir vte spits out the wrong path
[19:25] <slangasek> (/usr/include, not /usr/include/vte-0.0)
[19:29] <seb128> slangasek, seems buggy indeed
[19:29] <seb128> slangasek, can you open a bug about that?
[19:29] <slangasek> ack
[19:29] <seb128> thanks
[19:36] <slangasek> Daviey, smoser: do you know why eucalyptus-udeb depends on libavahi-core6-udeb when nothing else in eucalyptus wants libavahi?
[19:37] <slangasek> (the package now needs a rebuild for the libavahi-core ABI change, just wondering if it should be future-proofed in the process)
[19:38] <smoser> ttx might be able to answer more, but i'm guessing its so that the nodes can find a server and populate the server field
[19:38] <slangasek> ok
[19:51] <achiang> quick process question -- when ubuntu moves from version N to N+1, how do the changelog lines for the packages get updated (so they are built properly)? is it automatic or is it manual on a per-package basis?
[19:52] <achiang> e.g., foo-package (1.0) lucid; urgency=low ; how does that get rebuilt for maverick (if at all)?
[19:52] <micahg> achiang: old entries don't change, new entries have the new release name
[19:53] <smoser> achiang, i believe that initially, its a binary copy over.
[19:54] <achiang> smoser: so if foo-package is copied from lucid -> maverick, but didn't need any updates for maverick, then its release field in the changelog remains the same?
[19:56] <ccheney> what happened to the ubuntu amd64 daily live image? it seems to not been produced for the last several days
[19:58] <smoser> achiang, it sure appears that that is the case.
[19:58] <smoser> for example, on my maverick system here, i have /usr/share/doc/notify-osd-icons/changelog.gz with 'notify-osd-icons (0.6) lucid; urgency=low'
[19:58] <achiang> smoser: makes sense. so if a developer actually needs to make a change to the package, then s/he will s/lucid/maverick/ for the last  changelog entry, as micahg said
[19:59] <smoser> right. they *have* to to get it re-built for maverick
[19:59] <micahg> achiang: no, a new entry will be added
[19:59] <achiang> micahg: right, i meant that, i just wasn't clear in what i wrote. :)
[19:59] <achiang> smoser: micahg: thanks
[20:01] <smoser> ccheney, i believe size issues
[20:02] <superm1> smoser, ccheney no, according to http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu/maverick/daily-live-20100830.log: "mkfs.msdos: command not found"
[20:04] <smoser> manjo, ^ (you asked about that earlier)
[20:05] <manjo> smoser, also the i386 iso won't boot without a hack
[20:05] <superm1> from usb or from cd?
[20:05] <manjo> smoser, you need to do sed -i -e 's/ui gfxboot/gfxboot/' /media/New\ Volume/syslinux/syslinux.cfg to the usb stick
[20:06] <manjo> superm1, I have not tried CD
[20:06] <superm1> that's only if you are burning from usb-creator on 10.04 however (and only on USB)
[20:06] <manjo> superm1, correct
[20:06] <manjo> superm1, I am running lucid on my desktop @ home
[20:07] <superm1> manjo, that's bug 608382
[20:08] <manjo> smoser, superm1 also the installer supposed to show me a list of networks that I can chose from but all I see if a pink area ... no list
[20:08] <manjo> currently my install is stuck on retreveing files 2of6
[20:09] <manjo> detailed message says "*** Message: useQuirks: 0 / 0 /"
[20:09] <superm1> manjo, that could be a bug in a lot of areas, i think best to do is to ubuntu-bug ubiquity (ctrl-alt-t from the installer right now should get you a terminal), and then also attach lspci
[20:14] <manjo> superm1, :) its a chicken and egg problem, I don't have wifi to file a bug, since no wifi got listed by the installer
[20:14] <cjwatson> ccheney: NCommander fixed that earlier today
[20:14] <cjwatson> ScottK: hm, not sure I want even more publicity, oh well :-/
[20:15] <ccheney> cjwatson: thanks
[20:15] <manjo> cjwatson, when you get a chance can you look at my mail about UEFI ?
[20:17] <cjwatson> manjo: yes, I will do, but I'm technically on holiday today and it will take a good chunk of time to answer your mail
[20:18] <manjo> cjwatson, np, sorry to bug you.
[20:18] <cjwatson> manjo: and in small chunks of time I have at the moment, I need to focus on the beta release
[20:18] <manjo> cjohnston, totally understand, its bad timing I know
[20:18] <manjo> cjwatson, ^
[20:22] <janimo> Hello, does anyone here know which application was used to create the syslinux boot splash used as the first image on the LiveCD ?
[20:22] <janimo> I'd like to replicate that look for a deirvative and being quite a beginner in graphic manipulation it would help to at least know that I am not trying to do it using the wron g tools (gimp in this case)
[20:22] <janimo> thanks
[20:26] <cjwatson> janimo: I think I used something akin to the instructions in debian-installer/build/boot/x86/pics/polverini_b.README, but it was quite a while ago and I don't remember
[20:26] <janimo> cjwatson: thank you, I'll read that
[20:45] <janimo> cjwatson: I see a few images in that directory, but they are debian or pre-10.04 ubuntu. Is the original Lucid one available as well? Besides the conversion routines desribed in that readme and for which I used Gimp
[20:46] <janimo> before, I was curious if there is a raw file for the png or jpg from which it was generated, and maybe an artist who can tell what tools and effect were used
[20:47] <cjwatson> janimo: I really don't remember unfortunately
[20:47] <janimo> cjwatson: np, thanks anyway
[20:48] <cjwatson> I don't seem to have them locally in the place I was expecting
[20:48] <cjwatson> I have a vague memory that michaelforrest did it
[20:57] <sidh> Greetings
[20:58] <sidh> not sure if I'm asking to the right chan , but since i upgrade xubuntu 10.04 LTS , i get freezes with nfsclient when copying big files (2.1 GB)
[20:59] <sidh> does this problem has been reported ?
[20:59] <sidh> (i made no change in my mount options)
[21:06] <ScottK> cjwatson: Right.  It was intentional I didn't start out with "Congratulations ....".
[21:10] <tkamppeter> OdyX, are you currently working on Foomatic? It would be nice if you do not commit to GIT in the next days, to make it easier for me to commit my results.
[21:11] <OdyX> tkamppeter: I'm not. What I wanted in is already in. And in any case, if I would, I would in the master-squeeze branches.
[21:11] <OdyX> tkamppeter: feel free then !
[21:13] <tkamppeter> OdyX, OK.
[21:35] <ScottK> gilir: Is  awn-applets-common supposed to include anything other than translations?
[21:36] <gilir> ScottK, no, only translations
[21:36] <ScottK> gilir: OK.  Does it need to be arch any?
[21:41] <ScottK> didrocks: You didn't happen to see 627030 when you were working on Evolution, did you?
[21:43] <didrocks> ScottK: not really, my bugmail is closed (it's quite late here), just a quick fix for beta. In any case I'll upload after beta evo 2.30.3 and look at this one so
[21:44] <ScottK> didrocks: OK.  Thanks.
[21:44] <didrocks> yw
[21:47] <gilir> ScottK, no, should be arch all, I'll fix it for the next upload
[21:47] <ScottK> gilir: OK.  I'll go ahead an accept it.
[22:49] <tkamppeter> OdyX, ping
[23:07] <slangasek> pitti: do you have any idea what this error message is?  I can't reproduce it in a local build, even with pkgbinarymangler installed: Error: Package: and Architecture: do not alternate in debian/control
[23:08] <slangasek> pitti: from http://launchpadlibrarian.net/54444678/buildlog_ubuntu-maverick-i386.emdebian-crush_2.2.4ubuntu1_FAILEDTOBUILD.txt.gz
[23:09] <slangasek> hmm, maybe it's a parallel building problem
[23:15] <soren> slangasek: Maybe it gets confused by "Package:pdebuild-cross" (no space)
[23:15] <soren> slangasek: As for why you can't reproduce it, I have no clue.
[23:15]  * soren didn't try
[23:16] <slangasek> soren: good catch, I'll fix that and give it another try.  Would still like to know where this error comes from though :(
[23:16] <soren> slangasek: I can reproduce it.
[23:17] <slangasek> soren: in what env?
[23:17] <soren> slangasek: sbuild
[23:17] <soren> (maverick)
[23:17] <slangasek> hmm
[23:17] <soren> with pkgbinarymangler installed.
[23:17] <slangasek> infuriating
[23:17] <slangasek> soren: thanks :)
[23:18] <soren> Sure thing.
[23:19] <soren> slangasek: Adding the space fixes the build.
[23:19] <soren> Just FYI.
[23:19] <slangasek> ack
[23:19]  * soren wanders off
[23:22] <pitti> slangasek: it means that a Package: record in debian/control either has zero or more than one Architecture: fields; I wasn't sure how to interpret those cases, and at best they would only "accidentally" be right, so I thought to play it safe
[23:23] <pitti> soren, slangasek: ah, interesting little buglet in the mangler then
[23:23] <slangasek> pitti: ok, where does that message /come/ from? :) I can't find it in the code
[23:23] <slangasek> pkgbinarymangler /is/ the current package name, right?
[23:24] <pitti> slangasek: it's actually from pkg-create-dbgsym
[23:24] <slangasek> ahh
[23:24] <pitti> slangasek: but yes, it's the current name for that part
[23:24] <slangasek> I didn't have pkg-create-dbgsym here
[23:25]  * slangasek files a bug
[23:26] <pitti> thanks
[23:34]  * pitti waves good night