[03:31] <savvas> is there a way to prevent a package from building in certain architectures? can "Architecture" be used for the Source package in debian/control?
[03:36] <StevenK> savvas: The simplest way is to get the package added to Packages-arch-specific, and then Soyuz won't even add builds for those arches
[03:36] <savvas> ah, it's an old package, gambas 1 :)
[03:37] <savvas> the best way would be to patch it for 2, but I don't know that programming language hehe
[03:37] <savvas> StevenK: thanks though, noted!
[07:36] <dholbach> good morning
[07:36] <slytherin> dholbach: good morning. :-)
[07:36] <dholbach> hi slytherin
[07:49] <DanMcGoo> hi
[07:50] <DanMcGoo> need help
[07:51] <micahg> DanMcGoo: it's usually easier to just post your issue
[07:51] <micahg> someone will reply if they can
[07:51] <iulian> Morning dholbach.
[07:51] <DanMcGoo> ok ^^
[07:53] <DanMcGoo> I am trying to configure mini-dinstall and pbuilder in order to resolve some dependencies
[07:53] <dholbach> hi iulian
[07:53] <DanMcGoo> in order to test one of my package building
[07:53] <DanMcGoo> but it does not seems to work
[10:10] <loell> general question, if one is to package for debian, does one really needs to setup a debian system and not ubuntu?
[10:11] <gaspa> loell: it's really better, you can find differences in build systems, too.
[10:12] <loell> gaspa, it's just i'm really frustrated at setting up sid :(
[10:12] <gaspa> loell: just use a virtual machine.
[10:13] <loell> sidux?
[10:13] <loell> i mean vm with sidux? or generic sid?
[10:14] <gaspa> loell: I didn't know sidux... it depends from how it differ from a clean debian, imho.
[10:14] <loell> ok
[10:15] <loell> this has actually made me appreciate more, at how ubuntu makes it easier for packagers
[10:19] <directhex> i just use a pbuilder & wait to get moaned at if it breaks in a real environment
[10:19] <directhex> i'm naughty like that
[10:20] <siretart`> directhex: how do you test your debian builds then? pbuilder login?
[10:21] <loell> on related question, does lintian depend on specific build environment?
[10:21] <directhex> siretart, aye
[10:24] <loell> directhex, i wish i could do something like that too, but not having a mentor is difficult to hide what your build environment really is :)
[10:26] <directhex> loell, it becomes easier (to break the archive?) ifwhen the powers that be approve my DD application
[10:27] <loell> directhex, oh my, i couldn't wait to be under your wings :D
[10:30] <loell> OTH, how about i should just do the revu route then give back to debian later?
[10:31] <loell> how feasible would that be?
[10:32] <loell> or more generally, how does ubuntu give back to debian again? ;)
[10:33] <RAOF> loell: Well, by joining one of the various debian CLI teams!
[10:34] <loell> ah i see
[10:38] <slytherin> directhex: banshee works very well in jaunty (i386). :-)
[10:38] <slytherin> loell: What problems are you facing setting up sid?
[10:45] <directhex> slytherin, i wish i had the means to track down this ppc thing though :(
[10:45] <directhex> slytherin, lack of access to hardware sucks. is there no way to use qemu effectively?
[10:53] <loell> slytherin, setting up the build environment
[10:53] <loell> my bad, for taking a while to reply.
[11:16] <slytherin> loell: I thoought you were having issues in installing Debian sid
[11:17] <loell> slytherin, and that too
[11:17] <slytherin> loell: what kind of issues in installation?
[11:18] <slytherin> directhex: how hard is it to track without hardware?
[11:18] <loell> minor once, i must concede
[11:18] <loell> like no grub entry for ubuntu
[11:19] <loell> no pidgin package!?
[11:19] <directhex> slytherin, well, it's a PPC-only bug you've got, so i need a way to reproduce it to isolate it.
[11:19] <directhex> slytherin, i think the problem is with the sqlite binding, but that's a pure guess
[11:20] <loell> slytherine, in ubuntu, ubuntu-dev meta-package would most probably be enough
[11:20] <loell> but i'm stumped on how to redo that on sid
[11:22] <loell> err i mean ubuntu-dev-tools
[11:26] <slytherin> directhex: hmm, does it look like one of those endian related issues?
[11:26] <directhex> slytherin, i don't know. not obviously so, but i'd be surprised if it was something else
[11:27] <slytherin> loell: there is no ubuntu-dev-tools package for Debian (it's obvious). And you don't need ubuntu-dev-tools to setup pbuilder for Debian sid.
[11:28] <slytherin> directhex: do you have any idea where I should I look for the problem? Banshee code or sqlite bindings?
[11:28] <loell> which i just installed pbuilder which requires me a mirror?
[11:29] <loell> i could have swear i've use pbuilder in ubuntu many times, but setting a mirror wasn't one of them, when i use it
[11:30] <slytherin> loell: have you gone through https://wiki.ubuntu.com/PbuilderHowto It nicely explains how to setup different chroots from Debian and Ubuntu.
[12:00] <slytherin> directhex: pm?
[12:02] <directhex> slytherin, well the challenge is trying to find a reproducible test case, but it's such a wide search space :/
[12:03] <directhex> slytherin, gah, and the debugger is only for i386/amd64
[12:26] <bigon> could someone have a look at bug 389203 ?
[12:27] <bigon> it's for a sru (no changes only rebuild)
[13:07] <roshan08> hi all, i am writing a desktop app for blogging, how does a deb gets included in the ubuntu repo
[13:08] <Ampelbein> roshan08: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[13:09] <roshan08> Ampelbein, ok thanks
[13:32] <rrittenhouse> Anyone know how soon firefox 3.5 might be available as a replacement to firefox 3.0 in 9.04?
[13:42] <ogra> never ?
[13:43] <RainCT> ogra: I think it'll be made available in -backports
[13:43] <ogra> right
[13:43] <ogra> but not as a replacement
[13:44] <slytherin> ogra is correct here. It will never be made available as replacement.
[13:44] <RainCT> right, missed that part of the question
[13:45] <RainCT> (but it can be set as the default browser in System -> Preferences -> Preferred Applications, of course)
[13:45] <ogra> indeed
[13:48] <slytherin> geser: It is bugs like this - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535919 - that make the sync of maven related packages very time consuming. :-(
[13:53] <geser> slytherin: does it at least build with openjdk?
[13:54] <slytherin> geser: it should, I guess.
[14:00] <slytherin> geser: there are two options 1. Sync all the maven related packages from Debian and try solving FTBFS on our own. 2. Try test building the packages first, report any FTBFS to Debian and then sync them. What do you suggest?
[14:06] <geser> depends on how quick it get fixed in Debian, I'd probably do a mix of 1 and 2: Test build, upload (if patch is necessary) or sync, and forward the patch to Debian
[14:11] <directhex> moo
[14:13] <artfwo> Hi! I wonder is it possible to backport the fix for bug 309841 to Hardy and Intrepid as an update (not a backport)?
[14:22] <bddebian> Heya gang
[14:23] <iulian> Hello bddebian.
[14:23] <bddebian> Hi iulian
[14:25] <geser> Hi bddebian
[14:28] <bddebian> Heya geser
[14:32] <slytherin> TheMuso: did you get any chance to test your theory regarding build failures on powerpc?
[14:39] <slytherin> dholbach: nice and to the point of reply. :-)
[14:39] <dholbach> slytherin: thanks for the flowers :)
[14:41] <dholbach> nhandler: I don't know if I replied to your UbuntuDeveloperWeek edit, but if you can get a perl packaging session rolling for UDW - that'd be fantastic
[14:41] <dholbach> nhandler: can you please get them to pick a date and time? :)
[14:45] <nhandler> dholbach: I'm still talking with some of them. I'll try and get them to choose a date and time sometime this week
[14:45] <dholbach> excellent
[14:45] <dholbach> thanks a lot nhandler!
[14:46] <dholbach> much appreciated
[14:46] <nhandler> :)
[14:46] <dholbach> the earlier we get the schedule together, the better :)
[14:47] <nhandler> dholbach: I think we should make a stronger effort to get the Debian teams involved in these sessions. Most of the tools/procedures would be the same, but it would boost interaction between Ubuntu and Debian.
[14:47] <dholbach> absolutely
[14:48] <Laney> will there be a Debian collaboration session?
[14:48] <Laney> has there been before?
[14:55] <dholbach> Laney: there has
[14:56] <dholbach> https://wiki.ubuntu.com/MeetingLogs/devweek0901/Debian
[14:56] <dholbach> https://wiki.ubuntu.com/MeetingLogs/devweek0802/Debian
[14:56] <Laney> yay
[14:56] <dholbach> and maybe at UOW too
[14:57] <dholbach> if you could help to chase up people who want to run a session and get them to drop me an email, I'd really really appreciate it :)
[14:59] <Laney> we have some DDs in here
[14:59] <dholbach> maybe something about Packaging QA efforts?
[14:59] <dholbach> like NBS, getting a package to be lintian-clean, etc.
[15:00] <dholbach> finding out what a new standards-version is about
[15:00] <dholbach> and so on
[16:06] <Laney> DktrKranz: geser: gaspa: In case you guys didn't notice, pkg-haskell is now live
[16:08] <DktrKranz> Laney: uh?
[16:09] <Laney> debian team
[16:09] <Laney> just pinged the people who I thought might care
[16:09] <DktrKranz> ah, cool
[16:09] <DktrKranz> wasn't a team up already?
[16:09] <Laney> not really
[16:10] <Laney> it existed but was dead
[16:11] <gaspa> Laney: saw right now your post.
[16:11] <Laney> \o
[16:12] <DktrKranz> Laney: did you mail something?
[16:12] <Laney> to who?
[16:13] <DktrKranz> ubuntu-motu, or whatever?
[16:13] <Laney> nope
[16:13] <Laney> thought it was a bit too niche for anyone to care
[16:14] <gaspa> Laney: so, will we stand with 6.10.3 ? (i don't seen any news about 6.12 )
[16:14] <Laney> i guess so :(
[16:15] <Laney> Joachim just came up with a tool to generate the required rebuilds. I'll hack that up for Ubuntu and then we can start to clean up the mess
[16:15] <gaspa> Laney: is there a wiki page?
[16:16] <Laney> there's wiki.d.o/haskell but most stuff is happening on the ML now
[16:16] <gaspa> I hear something about it... but never investigate.
[16:16] <gaspa> ah
[16:16] <Laney> come to the IRC channel
[16:19] <DktrKranz> Laney: great, we really need it.
[17:56] <kklimonda> asac, why doesn't firefox 3.5 (the one from jaunty-security) doesn't use mozilla branding?
[17:57] <kklimonda> erm, doesn't.. sigh.. i need some sleep
[17:59] <asac> kklimonda: we only ship the default browser with official branding
[18:00] <asac> also we explicitly want the package to be installed side by side
[18:00] <asac> and having same branding causes confusino then
[18:00] <asac> because you cannot identify, what icon mean what ;)
[18:00] <kklimonda> i see, thanks
[18:00] <asac> but first reason is the dominating reason. also changing branding in a -security update is beyond its scope (even beyond SRU)
[18:01] <asac> its a main UI element ... and changing UI is officially forbidden
[18:01] <kklimonda> mhm
[18:33] <joaopinto> kklimonda, that bug report you were handling for cherrypy, I believe you used it for an SRU please note that Karmic's version is still not fixed (or was not, the last time I have checked)
[18:34] <kklimonda> joaopinto, i know about it
[18:34] <joaopinto> ok
[18:36] <kklimonda> joaopinto, i think I've attached a debdiff for it to update to 3.1.2.. I'm almost sure that I should have done it differently (i.e. attach .orig.tar.gz and .diff.gz) but I couldn't find a right page when I was last working on that
[19:34] <RoAkSoAx> Hey guys, I'm trying to package from scratch an app. This app already comes with a debian/ directory. What should be done in this cases?
[19:34] <nhandler> RoAkSoAx: You can try and contact the upstream developer to try and have them remove that directory from the tarball
[19:35] <RoAkSoAx> nhandler, if they refuse to do that?? Should I just debianize it myself?
[19:46] <hggdh> RoAkSoAx, you can code a get-orig-source to clean up the upstream tarball, and then debianise from there
[19:47] <hggdh> (in ./debian/rules)
[19:49] <RoAkSoAx> hggdh, you mean for example create a script that cleans up the upstreams tarball or a Makefile that does that?
[19:51] <hggdh> RoAkSoAx, if this is a new package, just clean it up; then, in the ./debian/rules that you will have, add in a get-orig-source rule to grab a new/current version. This will allow for a reviewer to confirm there are no other changes to the upstream source
[19:52] <RoAkSoAx> hggdh, ok thanks :)
[19:52] <hggdh> in the get-orig-source, you download the source from upstream, remove the ./debian directory, and tarball it
[19:54] <RoAkSoAx> ok cool :)
[19:58] <ScottK> RoAkSoAx: Repacking is not required unless you need to remove a file completely in their debian dir.  It's up to you if you want to fix their packaging or do your own.
[20:01] <RoAkSoAx> ScottK, ok. I guess doing my own packaging will be better then. Thanks :)
[20:28] <neversfelde> Hi, how can I replace a ../0.9.951.0Beta1/.. in a watch file?
[20:40] <Ampelbein> neversfelde: untested: versionmangle=s/\/0\.9\.951\.0Beta1\//<whateveryouwant>
[20:40] <neversfelde> Ampelbein: thank you
[23:11] <daurnimator_> hi
[23:11] <daurnimator_> theres a couple of lua librarys I would really like to be put in ubuntu repos, is there someone that can help?
[23:16] <micahg> ping mdeslaur_
[23:29] <daurnimator_> ok, I filed a bug for one package
[23:30] <daurnimator_> but theres another I'm not sure if I should file for: its a new library that has just had it's first release...
[23:43] <mdeslaur_> micahg: pong
[23:44] <micahg> mdeslaur_: did your phpmyadmin updates take care of all the outstanding CVEs?
[23:45] <mdeslaur_> micahg: yes, except CVE-2008-2960 on hardy
[23:45] <micahg> ok, cool
[23:45] <mdeslaur_> micahg: I didn't make updates for dapper though
[23:45] <micahg> should I open a new bug report if more are released?
[23:45] <mdeslaur_> micahg: sure
[23:45] <micahg> ok, thanks mdeslaur_
[23:48] <Arimal> ﻿can anyone help me out with using dpkg-scanpackages to make a repository? for some reason it is not printing anything into the Packages file
[23:48] <Arimal> I'm trying to make a local repository
[23:49] <Arimal> I've read the man page and I believe I have everything set right, but for some reason it isn't outputting anything
[23:49] <azeem> Arimal: what command are you running?
[23:50] <Arimal> find . -name "*.deb" > override
[23:50] <Arimal> then
[23:50] <Arimal> dpkg-scanpackages -m /media/disk/Loot/Debs/dists/hardy/main/binary-i386 override > Packages
[23:50] <Arimal> then
[23:50] <Arimal> cat Packages | gzip -c > Packages.gz
[23:51] <azeem> AFAIK, dpkg-scanpackages expects a path where to look for .debs
[23:51] <azeem> and the current directory is not default
[23:51] <Arimal> I've tried messing with the path in the dpkg-scanpackages
[23:51] <Arimal> I tried just a    .
[23:51] <Arimal> while in that directory
[23:51] <azeem> no idea then, sorry
[23:52] <Arimal> it gives some error info saying there are duplicates and everything, so it is finding the packages, but for some reason it's just not outputting
[23:53] <azeem> maybe Packages is read-only or something?
[23:53] <Arimal> thanks for trying azeem
[23:53] <Arimal> I deleted it before starting... so it's generated new each time through
[23:53] <Arimal> I've been wracking my brain over this because this script used to work fine
[23:54]  * ajmitch just has something like:
[23:54] <ajmitch> dpkg-scanpackages . -a amd64 /dev/null
[23:55] <ajmitch> so an empty override file, and everything below the current directory
[23:55] <Arimal> so /dev/null is the override?
[23:55] <Arimal> hmmm
[23:55] <Arimal> brb
[23:55] <Arimal> will try it
[23:55] <ajmitch> or you could try something like reprepro
[23:58] <Arimal> hmmm.... still no output but i did get an error this time... apparently it doesn't like the froswire deb ;)   trying again