[00:00] I tried the easiest route, just debuild the tree and upload to my ppa, but the package was rejected (obviously) because the information was for the unstable distribution which does not exist in ubuntu [00:01] Laibsch: Change the distribution in the changelog to an Ubuntu release. [00:03] Fujitsu: Hi, how are holidays? [00:03] geser: Pretty good, thanks. I'm about to head off again. [00:04] Fujitsu: This is for openembedded.org. The information is maintained in a version control system upstream. Is there no easier way than duplicating all information and keeping it in sync? [00:04] How does ubuntu handle debian packages for import? [00:04] There must be some more elegant way, right? [00:05] Laibsch: The script does special evil things that modify the distribution in the .changes file, I believe, but that's bad, and is to be avoided. [00:05] One should not do that for manually uploaded packages. [00:05] Anyway, I have to go now. [00:10] Fujitsu: thanks, I've asked for that package removal in the appropriate place now [00:29] RAOF: Bug 185099 [00:29] Launchpad bug 185099 in apt "apt output in all caps on amd64 when stdin is /dev/null" [Undecided,Triaged] https://launchpad.net/bugs/185099 [00:30] StevenK: Oh, cool. That's the actual sbuild trigger? [00:30] Yeah, sbuild calls schroot blahbalhbalhbab 'apt-get -y install foo < /dev/null' or something to that effect. [00:30] Cool. [00:31] and due to weirdness in apt's termios handling that sets the pty to spew all uppercase stuff. [00:31] RAOF: Which makes keescook The Man. [00:31] * RAOF prostrates himself before The Man [00:31] Haha [00:34] * ryanakca grumbles at having to write a copyright file for a package (a compilation of libraries/bindings) with 50+ authors... [00:36] * ryanakca grumbles at people not giving their email address in Copyright (C) 2007 John Smith [00:39] Mmh, nautilus crashes on my Hardy. [00:40] dist-upgrade [00:42] crimsun: Yes, I knew but there are packages that the dist-upgrade wants to remove. [00:43] using aptitude safe-upgrade ? [00:43] sorry, and* using aptitude safe-upgrade ? [00:43] I'll try it. [00:43] crimsun: Are you still a Debian ALSA teamer? If so, or even otherwise, is my thinking in debian bug #436201 reasonable? I'd like to get that done before FF. [00:43] Debian bug 436201 in libasound2-plugins "libasound2-plugins: Could we get an ia32 package for amd64?" [Wishlist,Open] http://bugs.debian.org/436201 [00:44] crimsun: It works. Thanks a lot. [00:44] RAOF: yes, it's reasonable. I read the e-mails earlier, but I don't like to post from yahoo since it's spam-nasty. [00:45] crimsun: Ta. I'll look at that tonightish then. [00:45] crimsun: But that command doesn't update the packages? [00:48] DarkSun88: hmm? [00:48] safe-upgrade Upgrades installed packages to their most recent version. Installed packages will not be removed unless they are unused (see the [00:49] direct from hardy's aptitude(8) [00:53] crimsun: After that command, return me the prompt. [00:53] DarkSun88: well, if you've already executed aptitude safe-upgrade, it's likely it won't do anything but exit successfully if it completed successfully prior :-) [00:56] crimsun: Yes, I've already executed aptitude safe-upgrade but I repeat: It doesn't upgrade my packages. It said me that there are 84 packages not updated. [01:17] do you put copyright for install-sh in debian/copyright? [01:21] ryanakca: Is it the same license as the rest of the package? [01:23] ScottK: no, its MIT vs GPL [01:23] helo motu`s . i wonder if there's some guidance docs or suggestions at the wiki in order to create a development enviroment for my laptop, i want to develop and package some things for ubuntu but don't want to make my desktop a complete mess.... [01:23] ryanakca: Then you need to mention it. Not mentioning all licenses is an automatic reject. [01:24] andresmujica: Install build-essential, devsrcripts, and ubuntu-dev-tools and never compile outside of a chroot. [01:24] ScottK: or no... wait... *checks* I'm not sure its MIT, I'll pastebin [01:24] ryanakca: As long as it's not GPL, it needs to be in there. [01:24] andresmujica: chroots and pbuilder/sbuild are very helpful [01:24] ScottK: http://paste.ubuntu-nl.org/53101/ ... what do I put it as? [01:25] ScottK: clamav backport still going? [01:25] ScottK: surprising thing is that the package got into universe /without/ a copyright file. [01:25] LaserJock: Yes. [01:25] ryanakca: what package? [01:26] LaserJock: Riddell had connectivity problems so not all of them got kicked off properly. [01:26] ScottK: well, the file was there, but it was still the default dh_make [01:26] ScottK: ah, I see perhaps Hobbsee is coming to the rescue [01:26] LaserJock: kdebindings-kde4 [01:26] arrr! [01:27] Unfortunately the rest aren't source backports, so IIRC they can't be done through the web ui. [01:27] what are the rest? binary backports or something? [01:28] Hobbsee: There the ones that they use their automagic script to pull them straight out of soyuz. [01:28] They are source, but no new source is uploaded. [01:28] ahhh [01:28] ScottK: would something along these lines work as a copyright files (incomplete, yes...) http://blog.ryanak.ca/copyright ? [01:28] * ScottK looks [01:29] simply since there are quite a few copyright holders, each "owning" a section/branch/tree in kdebindings-kde4-4.0.0 ? [01:29] ryanakca: ummm, that's messed up [01:30] Yeah. [01:30] crap... so where do I put all the authors? [01:30] all in a list, without saying who did what? [01:31] ryanakca: Collect each license together and say foo is copyright bar, alpha is copyright omega, and they are distributed under the terms of the blankety blank license [01:31] Also you need the bit like you have with LGPL 2.1. [01:31] ok, thanks, i'm gonna explore those packages. [01:32] andresmujica: for having chroots the schroot package is very helpful [01:36] ScottK: ok, so would it be like the top or bottom part of http://blog.ryanak.ca/copyright2 ? [01:45] Heya gang [01:46] hi bddebian [01:46] Hi LaserJock [01:46] ryanakca: Sorry. I'm busy with $WORK and can't really focus on it. [01:47] ryanakca: As long as it's clear what license/copyright goes with what files and all the licenses are listed in reasonably compact and clear way, it should be fine. [01:47] ScottK: ok, thanks :) === kitterma is now known as ScottK2 [01:56] shesh, my uni is getting crazy [01:56] I keep getting tons of emails about safety [01:57] LaserJock: Ah, so they noticed your lab practices? [01:57] apparently the answer to several rapes and a kidnapping is to have "Personal Safety Awareness Training" [01:57] StevenK: no, my lab's not to horrible [01:58] I've actually gotta brush up on lab safety for teaching next week [02:02] Here's one to make you shudder folks: https://nm.debian.org/nmstatus.php?email=bddebian%40comcast.net ;-) [02:03] StevenK: haha [02:03] bddebian: \o/ [02:04] ajmitch would probably have a heart-attack :-) [02:05] bddebian: Congratulations. Prepare to get a lot of practice waiting. [02:11] ScottK: Yeah I figure I'll be dead and buried before I actually get in but what the hell :-) [02:17] does the AM actually have to meet with you? [02:18] I hope not :-) [02:18] I see "ID to be checked by AM" [02:20] what's a small package with an init script... [02:20] ddclient? *checks* [02:21] I just spent 20 minutes getting a watchfile to work on a new package :) [02:21] LaserJock, becoming a DD ? [02:21] LaserJock, if so can i whore you for uploads? (: [02:21] jdong: "Fun" sometimes aren't they? :-) [02:21] nenolod: hah, no [02:22] LaserJock, no to which? [02:22] both [02:22] bddebian: and better... upstream doesn't provide an indexed downloads directory (403 forbidden) [02:22] LaserJock, then what application manager? :o [02:22] bddebian: so I'm scraping the FRONT PAGE, the only place with an AJAXified download link [02:22] Ugh [02:22] bddebian: so I'm betting $100 that by the time next upstream release comes, THIS WATCHFILE WONT WORK :) [02:22] nenolod: bddebian is going for DD [02:22] oh. right. [02:22] LaserJock, i already knew that (: [02:22] but there's some personal satisfaction in writing one [02:23] i'd go for DD but no debian person has signed my key. :( [02:23] Boy, that will just make ari's year.. :-) [02:23] i think being a ubuntu member would provide more value. [02:23] bddebian, oh yes. ari would love it if i became a DD (: [02:23] or 2 years, or 3 years... :-) [02:23] he'd probably have a heartattack [02:23] nenolod: No, I meant me. We have a long "interesting" relationship :-) [02:23] I can't find a file with an init script! [02:23] ah. [02:23] forget it, let's look at apache [02:24] the only relationship with ari i have is a cooperative trolling one. [02:24] (; [02:24] I don't think I'm really interested in DD, I think DM is enough for me [02:24] which reminds me [02:24] LaserJock: Are you on NM for DM ? [02:24] can i whore someone for an upload in a while? (: [02:24] bddebian: not quite yet, gotta sen in my app [02:25] *send [02:25] Ah [02:25] i'm packaging up a default skin for audacious for ubuntu [02:25] \:D/ [02:25] but I got everything I need [02:25] or do i need to upload it to revu [02:26] jdong: Just grab a randome tarball and run dh_make on it. It'll give you a shell for an init. [02:28] ScottK: yeah, actually I'm working from the dh_make examples [02:28] ScottK: unsure whether to use init.d.ex or init.d.lsb.ex, I think the LSB variant [02:28] Use the LSB one. [02:28] ScottK: then also I wanted to ask what to name it, but I figured that out by myself :) [02:29] wow, debianizing a new daemon is so much fun :) [02:29] (not) [02:29] Yeah. [02:29] * ScottK is working on one too. [02:31] also, which is better, audacious-skin-human or audacious-theme-human ? [02:31] * RAOF would go with theme. [02:31] nifty, thanks [02:31] (: [02:31] skin-human sounds mean [02:31] ;-) [02:32] skin-cat =D [02:35] DarkMageZ, actually i may need your expertise with something in a bit (: [02:37] hi [02:37] are there some resources on backporting to dapper ? [02:38] rzr: What are you after? [02:38] !backports | rzr [02:38] rzr, as in getting a package into backports or as in you backporting a package for yourself? [02:38] rzr: If new updated Ubuntu packages are built for an application, then they may go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging [02:38] unicorn is broken in dapper [02:39] !SRU then. [02:39] Sorry, I don't know anything about sru then. - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi [02:39] Argh. [02:39] Stable Release Update. [02:39] DarkMageZ: no i want to replace the one in repo .. I'll read this [02:40] rzr: If the one in the repositories is broken, we can do a stable release update to fix it. Backports is for new features, not for serious bug fixing. [02:41] rzr: https://wiki.ubuntu.com/StableReleaseUpdates [02:41] ScottK: the version in hardy is ok [02:42] rzr: Right, but backports is not enabled by default. If a package is totally broken, we should try to fix it in updates so more people can benifit. It's more effort, but worth it. [02:43] ok i note this down for next weekend [02:48] i heard rumors that debian was obsoleting gtk1.2 and removing it. is this true and if so is ubuntu following the same path? [02:49] Was that gtk1.2 or all the gnome-1 stuff? Because I remember someone saying that they're finally reaching the bottom of the gnome 1 stack :) [02:50] It's possible that gtk1.2 will be included in that master plan. [02:50] It is suppose to go the way of the dodo [02:51] One of the reason xmms is scheduled for removal [02:51] crap i still use xmms [02:51] use mocp instead =) [02:51] So do 12,000 other people according to popcon :) [02:52] so i could reject a "needs-packaging" because it depends on gtk1.2? [02:52] zul, use audacious. [02:52] DarkMageZ: I would unless they are willing to port it [02:52] zul, it's similar to xmms and is still maintained. [02:53] What needs packaging and is dependent on gtk1.2? [02:54] Hopefully nothing. [02:54] New gtk1.2 sutff now isn't where we want to be going. [02:54] For Gutsy I had to stop something building a gtk1.2 variant to get it into Main. [02:55] Hi all. [02:55] Hi DarkSun88 [02:55] Hi Scott. [02:56] Heya DarkSun88 [02:56] Mmh, nautilus continues to crash. [02:56] bddebian: Hi. :) [03:00] RAOF, AutoZen [03:03] DarkSun88: Think KDE. [03:18] Think xfce! ;-P [03:26] ScottK, bddebian: I think that now, I'll go to sleep. :D Gute Nacht. [03:26] Gute Nacht [03:35] Gnight DarkSun88 [03:39] does apache (1) have its config files in /etc/apache? [03:39] jdong: /etc/apache2/ [03:39] Hobbsee: apache 1.3.x uses /etc/apache2 too? === santiago-ve is now known as foursixnine [03:40] oh, i thought you were talking about apache(1), ie the manpage. [03:40] no idea then, sorry [03:40] Hobbsee: well I'll guess it uses /etc/apache till someone screams at me otherwise :D [03:40] * jdong is packaging the shiny clutch bittorrent webui [03:40] jdong: What apache1? [03:40] We don't have that anymore. [03:40] ScottK: we don't have it anymore? [03:41] Nope. Just apache2 [03:41] ScottK: pfft well that's even better! [03:41] *happily removes apache1 references* === foursixnine is now known as santiago-ve [04:04] i don't know. am i going in the wrong direction for this: http://nenolod.net/audacious-theme-human.png -- it's intended to be the default theme for audacious in ubuntu. [04:06] Dear git: go faster. [04:07] Hah [04:07] git sucks honestly :/ [04:08] take mercurial, make it use gitweb theme. problem solved :P [04:08] And bzr ROCKs.. [04:08] * bddebian hides [04:08] * nenolod can't stand bzr [04:08] * bddebian either [04:08] But bzr is great [04:08] * StevenK can understand it [04:08] great for humans [04:09] i need revision control for nenolods instead (; [04:09] nenolods are only one human see :P [04:09] Understanding of git still eludes me, but I use it like once every three weeks [04:09] nenolod: What doesn't make sense about bzr? [04:10] Other than being slower than my grandparents? :-) [04:10] bddebian: Try 1.0 [04:11] StevenK, it's not that bzr doesn't make sense, it's that bzrweb and loggerhead are awful [04:11] Ah. [04:11] hgweb just works, and with some tweaking works on mod_python. [04:12] I tend to not use web frontends to VCSs [04:12] bzr works great if you push your branch to for instance launchpad [04:12] but i don't think canonical would appreciate me using their resources for internal development [04:12] (; [04:13] Well, I admit I use bzr for Launchpad stuff only, like code hosted there, and the seeds [04:13] outside launchpad, bzr kinda sucks :/ [04:13] at least for publishing branches [04:14] I thought you could just push to ~/public_html? [04:15] yes, but then you don't get searchable branches and all that other nifty stuff launchpad has via loggerhead [04:15] Hello everyone, got a quick question [04:15] Ah, you also miss the nice lists of branches, and so on [04:16] I'm working on packaging Handbrake and during the build process it uses wget to download libraries and compile them [04:16] ugh [04:16] yet all of these libraries are available in ubuntu repositories [04:16] AdamSun: Please kill the devs for us, then. [04:16] haha... i wish [04:16] * nenolod hands AdamSun a shotgun, "you know what to do." [04:17] AdamSun: the handbrake build system is retarded [04:17] And how hard would it be to patch this out of their build system. [04:17] so i'm guessing my thoughts were true? [04:17] AdamSun: you're gonna have to strip out their build system and make your own [04:17] AdamSun: I recalled looking at this earlier :) [04:17] I don't think it will be too hard [04:17] sounds fantastically crap [04:17] RAOF: their entire build system specializes in fetching deps from random URL's [04:17] it's a living nightmare [04:17] Looks like I'll have some fun cleaning it up :) [04:17] it's not make, it's some other system [04:17] crikey [04:17] Aaah, the unadulterated joy that is apt. [04:18] yeah [04:18] it uses jam [04:18] at any rate, no comments on audacious-theme-human? :P [04:18] AdamSun: well, your task is to write a new buidl system for handbrake [04:18] actually though, it switches back and forth between the two... extremely sad [04:18] ha.. great fun [04:18] AdamSun: I know, but we'll all be thankful [04:18] AdamSun: (I'm the other transcoding nut around here) :D [04:18] Shouldn't be too hard to autotoolify it :P [04:19] jdong: well.. i'll think of you as i go through hell :) [04:19] jdong: Excited about Dirac hitting 1.0, then? [04:19] this is actually my first attempt at packaging a new app [04:20] RAOF: meh no time for getting excited :) [04:21] in terms of packaging this... would it be best to try to just alter their build system, or just scrap it all and start fresh? [04:23] AdamSun: how familiar are you with jam? [04:24] I quickly acclimated myself to it when i started, so i'm comfortable with it [04:25] AdamSun: cool, does it look easy to strip off the other build-dep fetchers from their jamfile? [04:25] AdamSun: I mean, I'd hate to see their code for building the actual transmission program go to waste [04:25] yeah.. actually that is the main complexity of the build process [04:27] my only concern was how to work around the need to download [04:27] it'd be nice to just leave them their horrible build process and then use the nice one only with this package [04:28] AdamSun: maybe ship your own jamfile in debian// [04:29] jdong: possibly, it actually starts the whole process off with make though [04:29] jdong: make then calls jam [04:31] jdong: ( cd .. ; ./configure ; cd contrib ; cp -f ../config.jam . ; jam ) [04:31] jdong: that wonderful line there is called from make [04:31] AdamSun: that might work, what's your clean line gonna look like though? ;-) [04:32] AdamSun: can you not specify an explicit jamfile to jam? [04:32] jdong: yeah.. i do believe [04:32] * jdong laughs at dpkg [04:32] _i386 is picked over _all [04:33] well there's my problem [04:33] I was WONDERING why that fix wouldn't propagate after 10 rebuilds! [04:35] jdong: the jamfile that gets used from that line is basically useless, except that it runs patches to the source... otherwise it's only function is to build the libraries [04:37] AdamSun: ah, ok [04:40] jdong: would it be better to create a new rule that builds without wget, or just to alter their rule [04:44] AdamSun: if you alter their rule, do so from a patch [04:48] nixternal: ping [04:56] LaserJock: That's two of us looking for him. I pinged him about 5 minutes before you did in #kubuntu-devel. [04:58] he's popular, clearly [04:58] jdong: looks like i'm going to need to package libdca first :) luckily it should be easier [05:03] heh [05:04] well I don't need him anymore [05:04] I lost my plasma panel and wondered how to get it back [05:04] LaserJock: pong [05:04] hah [05:05] nixternal: just actually logged into KDE 4 [05:05] lost my panel [05:05] that's a scary thought [05:05] but figured it out [05:05] logged out and then logged back in? [05:05] yep [05:06] I had to kill plasma and then remove the config and it came back [05:06] ya, that will be fixed with the next release due out in about 2 weeks [05:06] actually, there have been a lot of fixes for KDE 4.0 already [05:06] I wonder though if the icon stuff had been figured out [05:07] most of it has [05:07] apachelogger_ actually patched quite a bit of it already [05:07] has it made it to gutsy? [05:07] DarkSun88: so, are those related to dist-upgrade? :-) [05:08] dunno if stdin has updated the gutsy ppa or not yet [05:31] has anyone else been running into some weird FTBFS today related to stat64? [05:32] for example, see this log: http://launchpadlibrarian.net/11491264/buildlog_ubuntu-hardy-i386.mythplugins_0.20.2%2Bfixes15096-0ubuntu3_FAILEDTOBUILD.txt.gz [05:44] hmm, KDE desktop effects are pretty sweet [05:49] LaserJock: Do you not play with compiz much? :). I found them pretty... jerky isn't really the right word, but it'll have to do. [05:51] I think it's something to do with the animations. Effects in compiz tend to go: accelerate, move, decelerate. Whereas kwin's seem to be all the same speed. [06:06] RAOF: well, I guess I'm just impressed you can even use it [06:12] LaserJock: What? Compiz? Or kwin? [06:12] well, both actually [06:12] but kwin specifically [06:12] Heh. [06:12] I got a new laptop with an intel graphics card [06:13] and my previous laptop had ATI and didn't really do 3D desktop well at all [06:13] Ah. Sweet open source drivers. Without TTM, sadly. [06:14] I didn't really know that KDE had made any advancement in 3D desktop [06:14] I'm currently playing with the metacity compositor. Which isn't too bad. But isn't anything like kwin, and has most of the bugs that xcompmgr had. [06:15] but the expose and virtual desktop switching is nice [06:15] I'd played around with it at some point. [06:16] Exposé is the best new window-manager feature is a long, long time. [06:19] Oh, dear. Multiarch is quite a lot harder than I'd hoped. [06:24] Why can't we have a ia32-libs-dev package :( [06:29] I thought we did? [06:29] Not according to aptitude search ia32 [06:32] Hrm. I see that. [06:33] So I get to play around with fun like -l:libpulse.so.0 [06:39] Heya all! [06:50] Why couldn't they just use compiz, anyway? [06:58] LucidFox: Because it's not written in C++ :P [06:59] heh [06:59] LucidFox: I'm not really sure. I remember one of the reasons being that the plugins were not sufficiently isolated; one bad plugin can bring compiz down. [06:59] Although that should change reasonably soon. [07:00] (With the landing of the object-framework branch) [07:00] Or, rather, it'll make it easier to not bring down compiz. [07:01] I think that their reasons, while valid at the time, aren't any more. At least those reasons that I was aware of. [07:01] "...And at about the same time, the GNU developers found a fatal flaw in Poppler: they didn't write it! They decided to create GNU PDF, which is like Poppler but different..." [07:01] Yup, pretty much. [07:02] It's true that they'd have to introduce a bunch of window manager bugs, but by starting from compiz they would have had fewer compositing manager bugs :) [07:03] i just found this phrase from the packaging guide under KDE section: "remember debian policy implies that every single application has a man page!". so is it mandatory for new ubuntu packages to include a man page? [07:03] and if there isn't one should it be somehow generated from the README file? [07:03] Yes. [07:03] That's one way, yes. [07:04] any links or "googlewords" to help with that? :) [07:04] I usually use help2man to create the initial draft [07:04] Well, there's the help2man program. [07:04] Heh. [07:04] and then tweak it in a text editor [07:05] ok. thank you! [07:05] crimsun: Still here, and willing to be a foil for multi-arch alsa-plugins? [07:06] i should probably generate some kind of faq from all the answers you guys have given me :D [07:07] vemon> Actually, that would be a good idea. I'm thinking of writing one on the wiki. [07:08] LucidFox, when it's up&running i'm more than happy to contribute [07:09] i usually write small instructions for everything new i learn to be able to re-do it later [07:12] Would an empty debian/docs (rather than just a lack of it) be a blocker for a REVU package? [07:12] You know what'd be _awesome_? Frikkin proper dpkg/apt supported multiarch. [07:15] oh. forgot to ask how can i package the man page properly? the packaging guide seems to be lacking that information [07:18] found it. if it's as simple as adding this to rules: DEB_INSTALL_MANPAGES_myapp = myapp.1 [07:29] vemon> um [07:30] I think it's better to add it to debian/manpages than edit debian/rules [07:34] if i add it there will it be magically included in the package and install correctly without adding any (for example) cdbs includes/params to rules? [07:35] That's right. dh_installman is automatically run by CDBS, and will look at that file. [07:35] thanks again :) [07:37] hello, i want to get involved! [07:37] jackdaw> Excellent! :) [07:37] great! well that was easy [07:38] Do you have any specific interests? [07:38] numeric / scientific code is what i'm good at [07:39] so it'd be good if there was something i could use that for that would be helpful [07:40] Is the software you're interested in already in Ubuntu, or do you want to get it there? [07:41] yeah i was just reading the wiki article, so you lovely folks are loosely the package maintainers? [07:41] LucidFox: yea go for waste.sf.net [07:41] it compiled well [07:41] i think i was more looking to join something more like a specific dev team [07:42] There is a list of MOTU teams here: https://wiki.ubuntu.com/MOTU/Teams [07:42] LucidFox: oops forget what i said , i didnt got the context :) [07:43] But generally, the people here will help you with any area [07:43] jackdaw> Here is the page for the MOTU Science team: https://wiki.ubuntu.com/MOTU/Teams/Science [07:43] thanks! i just got to that myself [07:44] ok, i'll lurk for a bit [08:03] hello world! :) [08:19] can someone explain https://bugs.launchpad.net/ubuntu/+source/axis/+bug/150081 to me? Whats wrong with the package? [08:19] Launchpad bug 150081 in axis "autopkgtest gutsy axis: erroneous package!" [High,New] === civija_ is now known as civija [08:48] morning everyone [09:20] HI [09:21] foolano: hi [09:21] one of the two packages i uploaded to REVU yesterday is already in hardy. how should i proceed to cancel it? [09:21] slytherin: hello, can you please reproduce or close https://bugs.launchpad.net/ubuntu/+source/axis/+bug/150081? [09:21] Launchpad bug 150081 in axis "autopkgtest gutsy axis: erroneous package!" [High,New] [09:22] slytherin: I guess it can be closed as I cannot reproduce it here in Debian. [09:22]