[00:25] <JackyAlcine> TGIF!
[00:47] <axp2> guys is there anyone here that can make USB private bug 699898 public so i can investigate it?
[00:47] <ubottu> Bug 699898 on http://launchpad.net/bugs/699898 is private
[00:47] <axp2> USB=USC
[00:52] <AbsintheSyringe> is unity available as a package for 11.04 or ...? I'm thinking of making a package for Debian as well
[00:53] <AbsintheSyringe> seems like it
[06:24] <beachwood23> i'm having problems booting from testdrive… it will only boot from the floppy, says that the hard disk is not a bootable disk
[06:49] <beachwood23> i'm having problems booting from testdrive… it will only boot from the floppy, says that the hard disk is not a bootable disk
[11:08] <xdanek7> hi, I hope I am on the right channel. I stumbled upon package GLEW (extensions for OpenGL). In Ubuntu it is in version 1.5.2, in Debian Sid 1.5.4 and the current released version is 1.5.7 I tried figure out, how I can send an update to Ubuntu
[11:09] <xdanek7> i downloaded branch bzr branch lp:ubuntu/glew, did some changes but I have no clue how to build the package on my computer to see if it works. Can anybody help?
[11:10] <xdanek7> *to
=== yofel_ is now known as yofel
[11:14] <xdanek7> the command dpkg-deb --build . expects to find the folder DEBIAN, but in the repository the folder name is not capitalized ("debian"). And if I rename the folder to DEBIAN, it says "dpkg-deb: error while parsing  „./DEBIAN/control“ around line 8: package name missing" . What I am doing wrong?
[11:17] <geser> xdanek7: leave it as "debian" and install "bzr-builddeb" and do a "bzr bd -S" to get a new source package which you can either build with pbuilder or upload to your PPA
[11:19] <xdanek7> thanks, Ill try it right now
=== Quintasan_ is now known as Quintasan
=== Lutin is now known as Guest42078
=== Lutin_ is now known as release
=== release is now known as Luton
=== Luton is now known as Lutin
=== oubiwann_ is now known as oubiwann
[12:56] <theclaw> hi
[12:57] <theclaw> how can I report a bug on bugs.launchpad.net? when I select "Report a bug", all I get is a wiki-page where it's explained how to use a bug-reporting-tool
[12:57] <theclaw> I want to report a bug without that tool
[12:58] <theclaw> it's only possible with that tool?
[12:58] <theclaw> I don't have a PID..
[13:00] <theclaw> how annoying :-(
[13:00] <bdrung> theclaw: you can report a bug against an ubuntu package without that tool
[13:00] <theclaw> bdrung: how? on launchpad.net, when I click "Report a bug", only a wiki-page appears
[13:01] <bdrung> theclaw: go to https://bugs.launchpad.net/ubuntu/+source/<source-package-name> and there you can file the bug
[13:02] <theclaw> bdrung: okay, thanks. but I'm just curious - how should I know that?
[13:02] <theclaw> bdrung: I just searched for 15 minutes how to report a bug :-(
[13:04] <bdrung> theclaw: the recommended way is to use the ubuntu-bug tool. on which page did you click "Report a bug"?
[13:05] <theclaw> bdrung: bugs.launchpad.net
[13:06] <theclaw> err, no,
[13:06] <theclaw> https://bugs.launchpad.net/ubuntu <- here
[13:07] <theclaw> bdrung: ubuntu-bug might be the correct tool, but if I have already identified the bug to some extent, it's just annoying
[13:07] <bdrung> theclaw: i am not redirected from this page to a wiki (maybe because i am a developer?). which wiki page is linked?
[13:08] <cdbs> bdrung: bebmers of ubuntu-bugcontrol aren't redirected
[13:08] <cdbs> *members
[13:08] <theclaw> bdrung: when I go to "https://bugs.launchpad.net/ubuntu/+filebug", I get redirected to "https://help.ubuntu.com/community/ReportingBugs"
[13:08] <bdrung> theclaw: if you have identified the bug, you can file it against a specific package.
[13:08] <cdbs> bdrung: and since you're core-dev, you are already a member of ~ubuntu-bugcontrol
[13:08] <cdbs> theclaw: If you want to file a package bug, then go to the url which bdrung prompted
[13:09] <theclaw> bdrung: I actually tried that, but couldn't find a way to go to the launchpad-page of the package
[13:09] <cdbs> theclaw: if you don't know the package, then go to https://bugs.launchpad.net/ubuntu/+filebug?no-redirect
[13:09] <bdrung> theclaw: https://help.ubuntu.com/community/ReportingBugs#Filing%20bugs%20at%20Launchpad.net
[13:10] <bdrung> theclaw: i strongly recommend to file the bug against the correct package.
[13:10] <theclaw> bdrung: okay, thanks - I didn't see that, sorry.
[13:10] <bdrung> np
[13:46] <xdanek7> A followup question. during the build process using bzr bd I get messages about failed patching. It is using tool dpkg-source -b to do the patching. The dpkg says "1 out of 3 hunks FAILED -- saving rejects to file Makefile.rej", but there is no Makefile.rej around, so I do not know what to fix. What does that all mean?
[14:13] <xdanek7> sorry for bothering you, but I am really confused by the debian/patches/* files. Is there an automatic way how to update those patches when I am updating the package, or do I have to do it manually?
=== almaisan-away is now known as al-maisan
=== shadeslayer is now known as kshadeslayer
=== al-maisan is now known as almaisan-away
[14:58] <BlackZ> gilir: the binary package awn-applets-python-extras (from awn-extras-applets) is missing a dependency on the python-vobject package. Without that package the calendar applet will not start
[15:01] <gilir> BlackZ, awn-applets-python-extras was replaced by  binaries for each applets, awn-extras-applets will be removed
[15:01] <gilir> BlackZ, see awn-extras source package
[15:02] <BlackZ> gilir: ok. I just noticed you fixed the bug there :)
[15:27] <JackyAlcine> :D
=== rbelem_ is now known as rbelem
[15:56] <AbsintheSyringe> what's Unity Team email address?
[16:08] <bigon> https://launchpad.net/ubuntu/+source/mutter << is it normal that mutter have gir1.2-mutter-2.31 instead of gir1.2-mutter-2.91 in natty?
=== stalcup is now known as kstalcup
=== apachelogger is now known as kgnomelogger
=== kshadeslayer is now known as kglibslayer
[17:04] <xdanek7> hi, I was poking around the package glew (library for OpenGL) in Launchpad. I downloaded the branch and tried to update the package, but I do not understand a few things.
[17:06] <xdanek7> in file http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/natty/glew/natty/annotate/head:/debian/patches/debian-changes-1.5.2-0ubuntu1 there is section in the diff modifying the file Makefile.linux, which apparently does that it removes the section dealing with x86_64 architecture and it IMO results in placing the .a file into /usr/lib and not into /usr/lib64
[17:07] <xdanek7> I want to ask, where I can learn why this is done. Thank you
[17:08] <kklimonda> xdanek7: you can try reading through the debian/changelog file
[17:08] <xdanek7> thanks for a hint
[17:11] <kklimonda> xdanek7: in ubuntu and debian, /usr/lib64 is a symbolic link to /usr/lib - it may be a reason for this change
[17:11] <xdanek7> regarding other changes in the diff, I assume they all have a good rationale to be there and have to stay there. But the source code that gets patched has changed. Is there an easy way how to do proceed with the update or do I have to manually go through all the lines in diff and decide what to do?
[17:12] <geser> xdanek7: you might also want to look at the Debian Policy
[17:13] <geser> Debian (and therefor Ubuntu) make the decision that native libs for the architecture should be in /usr/lib (independent if it's 32 or 64bit)
[17:14] <kklimonda> xdanek7: you pretty much have to go through the whole diff and decide if changes still make sense
[17:15] <xdanek7> you were right, the x68_64 thing is mentioned in the changelog, it solves a bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=+419452
[17:19] <xdanek7> and when I am going through the diff, do I assume I do not have to pay attention to all architectural specific things (the package comes from Debian)? There is part about configuration under i86pc:SunOS:5.*:* | i86xen:SunOS:5.*:*). So I can safely ignore that and not move it into the new version? Or something that is mentioned in the changelog as "Include patch from Aurelien Jarno to fix...
[17:19] <xdanek7> ...FTBFS on GNU/kFreeBSD;"?
[17:19] <xdanek7> *can
=== kglibslayer is now known as kshadeslayer
[18:42] <ScottK> xdanek7: Generally we want to minimize the diff with Debian so we keep Debian specific changes unless they actively cause a problem for us.
[18:46] <xdanek7> ok, I am done. What should I do now? Should I fill a bug with a path? (There is already one asking for a newer version, so I can post it there) Or should I e-mail the person that is listed as a maintainer?
[18:46] <xdanek7> (the package works for me)
[18:59] <xdanek7> i will probably do both. And also write about it on Twitter ;-)
[19:01] <JackyAlcine> How do I cast a CURLcode to a std::basic_string, const char * or char *?
[19:02] <juliank> JackyAlcine: Using curl_easy_strerror()
[19:03] <JackyAlcine> That's not what I needed, but that is useful.
[19:03] <JackyAlcine> I need to cast data returned from curl_easy_perform() to a std::basic_string, const char *, or char *
[19:04] <juliank> JackyAlcine: It returns no data, it returns an error code
[19:05] <xdanek7> "curl_easy_strerror(3) can be called to get an error string from a given CURLcode number."  Does that help?
[19:06] <JackyAlcine> o.O it does! but I can std::cout << curl_easy_perform(CURL) and get the data output. what gives?
[19:08] <xdanek7> oh, sorry for saying what has been already said :-(
[19:09] <ebroder> JackyAlcine: uh, that's not what's printing out anything
[19:09] <ebroder> JackyAlcine: a CURL handle is configured by default to print any data it gets to stdout
[19:10] <ebroder> JackyAlcine: your std::cout << isn't what's printing out the data
[19:10] <JackyAlcine> Hmm, thanks.
[19:10] <JackyAlcine> But I want that data, lol, I need to read it.
[19:10] <ebroder> JackyAlcine: look at the options in curl_easy_setopt(3)
[19:11] <ebroder> in particular, CURLOPT_WRITEFUNCTION
[19:11] <ebroder> "Set this option to NULL to get the internal default function. The internal default function will write the data to the FILE * given with CURLOPT_WRITEDATA.", and CURL_WRITEDATA defaults to stdout
[19:14] <juliank> JackyAlcine: How about asking for help in #curl - I don't think that's really on-topic here.
[19:15] <JackyAlcine> Thanks.
=== kstalcup is now known as stalcup
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
[22:29] <kshadeslayer> http://paste.ubuntu.com/551948 << any idea why dpkg-buildpackage runs make before running cmake .. ?
[22:29] <dapal> kshadeslayer: how does your debian/rules look like?
[22:30] <kshadeslayer> dapal: http://paste.ubuntu.com/551950/
[22:32] <dapal> kshadeslayer: can't tell, sorry :/
[22:32]  * dapal doesn't know cdbs well either
[22:33] <kshadeslayer> well ... lets try MOTU as well ... after that ... i sleep
[22:33] <kshadeslayer> dapal: yeah ... all of us are being spoilt by dh :>
[23:23] <ebroder> kshadeslayer: Does changing the order of the includes change things?
=== MattJ100 is now known as MattJ