[01:45] <vadi2> Hi. I put a backported package into my ppa, and made the build-depends and depends field depend on the version >= in the ppa. But launchpad, when building, is not linking to my package in ppa but ubuntus. how can I rectify this?
[01:49] <savvas> vadi2: try #launchpad :)
=== yofel_ is now known as yofel
[01:49] <vadi2> Yeah
[01:49] <savvas> ah, both fronts, hehe
[01:49] <savvas> when did you build the backport?
[01:50] <savvas> maybe it's not in the repository yet?
[01:50] <vadi2> I built it in my ppa
[01:50] <vadi2> https://launchpad.net/~mudlet-makers/+archive/ppa
[01:51] <vadi2> when installing the upgraded mudlet package, it -did- properly pull in the updated qscintilla
[01:51] <savvas> hm, no idea then
[01:53] <vadi2> however mudlet is linked against qscintilla 2.so.3, which is ubuntus version. my updated qscintilla is 2.so.5
[02:01] <vadi2> savvas: this one is annoying too. qscintilla in hardy is unusable, it crashes on newlines (qscintilla being an editor widget)
[02:07] <savvas> vadi2: if no-one replies ask it as a question at http://answers.launchpad.net/launchpad :)
=== Andre_Gondim is now known as Andre_Gondim-afk
=== bastiao_ is now known as k0p
[10:47] <szabgab_> hi,
[10:47] <szabgab_> I have been asking for a long time and finally the Debian team has included Padre, the Perl IDE in Debian Sid
[10:47] <szabgab_> would it be possible to pull it over to Ubuntu at this late time of the release process?
[10:47] <Kamping_Kaiser> for the next release? doubt it
[10:48] <Kamping_Kaiser> (read its to late)
[10:48] <szabgab_> yeah I thought so but someone told me to come here and beg you ppl
[10:48] <hyperair> file an FFe, and see if it gets accepted =p
[10:49] <szabgab_> I have this ticket https://bugs.launchpad.net/ubuntu/+bug/326353
[10:49] <ubottu> Launchpad bug 326353 in ubuntu "[needs-packaging] padre-perl" [Wishlist,Confirmed]
[10:50] <szabgab_> what is an FF ?
[10:50] <hyperair> Feature Freeze.
[10:50] <hyperair> that's a package request.
[10:50] <hyperair> a needs-packaging bug
[10:50] <hyperair> for this you'll need a sync-request + FFe request
[10:50] <hyperair> but for FFe you need a good reason
[10:51] <szabgab_> I don't think I have, besides that it is already in Fedora and Mandriva too :-)
[10:52] <Kamping_Kaiser> szabgab_, wait 2 months and it'll be in Ubuntu too ;)
[10:52] <szabgab_> yeah I think that will be the action plan :-(
[10:53] <hyperair> well blame the bad timing =p
[10:53] <hyperair> i've got a few packages waiting out the freeze
[10:53] <szabgab_> yeah but at least it is now in Debian so I hope thing will be smooth next time
[10:54] <szabgab_> and the IDE will be much more mature too
[10:54] <hyperair> should be
[10:54] <hyperair> auto-sync will pull it =)
[10:54] <szabgab_> so do you mean I don't even need to ask for a sync ?
[10:55] <hyperair> nope
[10:55] <hyperair> probably not
[10:55] <szabgab_> FWIW it runs find on 8.10 (and is being developed mostly on it)
[10:55] <szabgab_> s/find/fine
[10:55] <hyperair> no i mean it'll autosync when karmic opens
[10:55] <hyperair> which is ubuntu 9.10
[10:56] <szabgab_> that's ok
[10:56] <szabgab_> At least that means I can point people there if they ask what about Ubuntu packaging
[10:56] <hyperair> yeah
[10:57] <hyperair> well if you're impatient you can set up a PPA for it
[10:59] <szabgab_> I think we are better off with a plain binary executable distribution for the impatient
[10:59] <szabgab_> thanks for your pointers anyway
[11:57] <maxb> Does anyone know of a script to merge debian/changelog files? Intelligently combining entries in version number order?
[11:57] <bencrisford> no, sorry :|
[11:57] <maxb> maybe I should write one :-)
[11:58] <Laney> yes
[11:58] <Laney> hold up
[12:00] <geser> as MoM does it for the proposed merges, perhaps you can re-use that code
[12:00] <Laney> maxb: http://orangesquash.org.uk/~laney/merge_changelog
[12:01] <maxb> yay! Thanks - and it's written in Python, even better :-)
=== azeem_ is now known as azeem
[12:19] <soc> hi
[12:19] <soc> can someone help me?
[12:20] <soc> ~/Entwicklung/Quelltexte/m/merkaartor-0.13.1$ debuild -S -sa
[12:20] <soc> This package has a Debian revision number but there does not seem to be an appropriate original tar file or .orig directory in the parent directory; (expected merkaartor_0.13.orig.tar.gz or merkaartor-0.13.1.orig)
[12:20] <soc> my downloaded archive is named merkaartor_0.13.1.orig.tar.gz, my dir merkaartor-0.13.1
[12:20] <soc> somehow debuild thinks there is a debian revision somewhere ...
[12:21] <soc> what should i do?
[12:21] <azeem> soc: probably you have 0.13 in debian/changelog, as opposed to 0.13.1
[12:31] <sladen> A package I uplaoded has just gone 1.0 (with most of the delta in Ubuntu commited upstream)
[12:31] <sladen> is it worth doing the UVF?
[12:31] <Laney> what's new in it?
[12:34] <sladen> Laney: bug fixes rather than new features
[12:35] <Laney> then yes
[12:35] <Laney> no exception needed
[12:42] <sladen> Laney: ta for the confirmation
[12:57] <soc> azeem: thanks!
[14:51] <skarn> I have a package that does not build, it seems the compiler exits with a segfault
[14:52] <skarn> here's the log from one of the compilers
[14:52] <skarn> http://dl.getdropbox.com/u/529363/arkn11745.scidavis_0.2.1-1-skarn86_FAILEDTOBUILD.txt
[15:31] <skarn> I have a package in my PPA that does not build, it seems the compiler exits with a segfault
[15:31] <skarn> however it builds under intrepid
[15:33] <skarn> er.. lupdater-qt4 segfaults
[17:25] <ScottK> mok0: libglw1-mesa-dev: Depends: mesa-common-dev (= 7.4) but 7.4-0ubuntu1 is to be installed
[17:26] <ScottK> mok0: Do you want to take care of it or should I?
[17:45]  * andol is rather new to working with deb packages, and is rather confused by the ntop package.
[17:45] <andol> I can see that the ntop packages has a debian/patches, with a bunch of diffs, but I can't find any references to patching inside debian/rules.
[17:46] <nhandler> andersk: If you have ubuntu-dev-tools installed, type 'what-patch' to see what patch system is being used
[17:46] <nhandler> andol: ^^^
[17:47] <nhandler> andol: Then follow https://wiki.ubuntu.com/PackagingGuide/PatchSystems to learn how to add/modify a patch using that patch system
[17:48] <andol> nhandler: Seems like the famous "unknown patch system" :)
[17:48]  * nhandler goes to look
[17:55] <nhandler> andol: What exactly are you trying to do with that package? After looking at it, that package is a huge mess
[17:55] <nhandler> It also hasn't been touched by the DM in nearly a year (even though the BTS has plenty of bugs and patches)
[17:57] <andol> nhandler: Figured I'd take a crack at bug #325393 and implement the simple patch applied by Fedora.
[17:57] <ubottu> Error: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/325393/+text)
[17:59] <andol> nhandler: Later on I'd also like to do something about bug #355127, and see if I can make debconf ask for that password during the installation.
[17:59] <ubottu> Launchpad bug 355127 in ntop "ntop admin user not created during install" [Undecided,New] https://launchpad.net/bugs/355127
[18:01] <andol> nhandler: But if the package is a mess, perhaps it should get "cleaned up" in Debian first, before we start doing any major things with it?
[18:02] <nhandler> andol: What I would suggest doing is contacting the Debian Maintainer to see if they are still interested in the package. If so, try and work with them to clean it up as well as incorporate some of these patches (as well as the ones on the BTS) into the package. Then, we can sync this package in Karmic
[18:05] <andol> nhandler: Did I mention that I'm rather new to working with packages? :) But hey, I guess it can be a learning experience...
[18:05] <nhandler> andol: A lot of the clean-up stuff is relatively simple. However, they are the types of changes that we like to avoid making for packages that are also in Debian. That is why I recommended contacting the DM
[18:06] <andol> nhandler: makes sense.
[18:06] <bluefoxicy> aww, the geramik engine no longer exists
[18:11] <bluefoxicy> why does evolution take like 10minutes to start up?
[18:25] <MTecknology> bluefoxicy: because it's bloated
[18:25] <bluefoxicy> MTecknology:  switching to evo was probably a mistake, also they deleted the "unmatched" search folder which has made it practically useless
[18:25] <MTecknology> Hey, if there's a good reason for 2.6.0 to be included in Ubuntu once it's released, how hard is the to get pushed?
[18:26] <bluefoxicy> evolution's strange sorting method only works because of the "unmatched" folder
[18:26] <MTecknology> bluefoxicy: I used it a few times and hated every on eof those experiences. I have no trace of anything e-d-s on my system
[18:28] <MTecknology> hrm - that's not my problem... If I make a patch to change the SSL back end of pidgin, how hard is that to get pushed through?
[18:28] <bluefoxicy> hey that's cool
[18:28] <bluefoxicy> when Jaunty locks up I can push numlock and the kernel wakes up
[18:28] <MTecknology> interesting
[18:28] <bluefoxicy> Jaunty has a habit of halting all disk access
[18:28] <bluefoxicy> and then everything freezes for 5 minutes
[18:29] <andol> nhandler: Hey, the debian maintainer for ntop just happens to have been a member of the same academic computer soceity which I have connections to :) That should makes things a bit easier...
[18:30] <MTecknology> There's an issue with the timing in gnutls inpidgin, so I want to make a patch to making it use something different, but of course - that'll be a massive pita.
[18:30] <MTecknology> http://developer.pidgin.im/ticket/8594
[18:30] <nhandler> andol: That is always nice. You might make a new friend out of this ;)
[18:37] <goshawk> what does dfgs means in a package name?
[18:38] <ScottK> dfsg stands for Debian Free Software Guidelines.  It means some non-free bits had to be removed from the tarball and the tarball repacked.
[18:44] <Laney> Does the MonoDevelop 2 FFe still stand?
[18:45] <Laney> actually, it might even be bugfix
[18:57] <mok0> ScottK: Thanks for message, I didn't notice. I'll take care of it
[18:58] <ScottK> mok0: OK.  Thanks.  I've got a depwait I'm trying to clear that I need that for ....
[19:01] <mok0> ScottK: I can use 7.4~ right?
[19:02] <ScottK> mok0: The problem is th =
[19:02] <ScottK> th/the
[19:02] <ScottK> 7.4 != 7.4-0ubuntu1
[19:02] <mok0> ScottK: yes... but I'd like it to ignore the release
[19:03] <mok0> ScottK: there's no wildcard afaik
[19:03] <ScottK> I'd just do >= 7.4, =< 7.5 (or whatever number is approprate)
[19:03] <james_w> >= 7.4~ , < 7.5~
[19:03]  * ScottK high fives james_w.
[19:04] <mok0> ScottK, james_w: thx
[19:04] <ScottK> Not =<, <
[19:04] <Laney> isn't it <<?
[19:06] <mok0> Using  mesa-common-dev (>= 7.4~)
[19:07] <ScottK> Isn't mesa-common-dev (>= 7.4~), mesa-common-dev (< 7.5) what you want?
[19:15] <mok0> ScottK: oh
[20:51] <maxb> Isn't < a deprecated alias for <= ?
[20:53] <hyperair> maxb: where did you get that from?
[20:53] <maxb> Good question :-)
[20:56] <maxb> The deprecated forms < and > were used to mean earlier/later or equal, rather than strictly earlier/later, so they should not appear in new packages (though dpkg still supports them).
[20:56] <maxb> sez policy
[20:59] <ScottK> So I guess it should have been <<
[21:19] <wintellect> I have an app that I wrote a while back that I am trying to pkg-ise. It supports both MySQL and PgSQL, but only needs one DB to work. Do I build it with support for one DB only? Both DBs? write it as two seperate pkgs that are mutually exclusive?
[21:19] <james_w> wintellect: hey, checkout dbconfig-common
[21:21] <wintellect> james_w: ok... but I'm new to this, do I download the source with "apt-get source" to check it out?
[21:22] <james_w> of course :-)
=== bastiao_ is now known as k0p
[21:22] <wintellect> james_w: k, thanks
[21:26] <maxb> wintellect: and use "apt-cache rdepends dbconfig-common" to show a list of packages using it, that you might look at to see examples of its usage
[21:38] <wintellect> maxb: thanks
[22:02] <wintellect> How do I get dbconfig-common to add "--enable-mysql" to the "./configure" command?
=== RainCT_ is now known as RainCT
=== yofel_ is now known as yofel
=== ash3 is now known as Sobriquet
=== Sobriquet is now known as ashley3
[23:27] <neversfelde> Hello, I'm trying to package bilbo, a KDE blogging app. It uses a modified version of KBlog, which is included in the source, I splitted it into a package called libbilbokblog0, but no I ran into a problem with dh_shlibdeps. Error is like that: http://pastebin.ubuntu.com/145175/
[23:27] <neversfelde> I guess I have to write a shlib.local , but I cannot figure out, what to put in there. Can somebody help me?
[23:34] <neversfelde> mhh, I may be wrong, only a debian/shlib?
[23:36] <RAOF> If you're making a library from the same source, you'll need do be calling dh_makeshlibs first, I think.
[23:39] <neversfelde> RAOF: cdbs should call it, or?
[23:40] <neversfelde> it is
[23:40] <RAOF> Oh, cdbs? :(
[23:41] <neversfelde> mhh, this is really complex :)
[23:41] <RAOF> Yeah; library packaging _is_ complex.
[23:42] <neversfelde> mhh, should sleep, will try tomorrow again
[23:42] <neversfelde> RAOF: thank you
[23:56] <pochu> neversfelde: do you really want to make the modified kblog library public?
[23:56] <pochu> I doubt it
[23:57] <neversfelde> pochu: lintian complained. Should it stay in the main package?
[23:58] <pochu> yes
[23:59] <pochu> and don't install any .la, .a, .so, or .h for it
[23:59] <neversfelde> mhh, ok. Than my first package was the best :). But I learned a bit^^
[23:59] <pochu> just the .so.X.Y.Z and .so.X, I guess
[23:59] <neversfelde> pochu: thank you, I will look into it again.
[23:59] <pochu> since you don't want to make a public library...
[23:59] <pochu> the public library would be the real kblog :)
[23:59] <pochu> neversfelde: np