/srv/irclogs.ubuntu.com/2008/04/29/#ubuntu-motu.txt

=== x-spec-t is now known as Spec
LaserJockis a 2GB file size limit a property of the kernel or filesystem?01:12
RAOFFilesystem.  Don't use fat, it's borken :)01:13
LaserJockI'm not using fat01:13
LaserJockI'm using ext301:13
* RAOF looks at his various >4GB files sitting on ext301:14
RAOFAnd is surprised.01:14
LaserJockthen maybe it is the kernel?01:15
LaserJockor maybe an old version of ext301:15
leonelor a < 2gb HD01:16
jdongleonel: LOL.01:16
jdongLaserJock: 2GB is such a weird size01:16
jdongLaserJock: what inode size did you set up?01:16
jdongLaserJock: you didn't hit that news server button thing for fun did you? :)01:17
LaserJockno01:18
LaserJockI just have an old Debian version01:18
LaserJockit's a 120GB hard drive01:18
LaserJockand I was writing a data file and it said it reached a 2Gb limit01:19
jdongLaserJock: 2GB file size limit is likely the result of silly inode sizes01:19
LaserJockhow can I check that?01:19
LaserJockpreferably without destroying my data :-)01:19
jdongLaserJock: dumpe2fs dev_node01:20
jdongLaserJock: I think that's Block size:               1024 you should be lookin for01:20
LaserJockjdong: so it's not because I'm running a 2.4 kernel?01:26
LaserJockI get a block size of 1024 it looks like01:26
jdongLaserJock: I'm at least not aware of kernel 2.4 limiting filesizes down to that extremity01:27
jdongLaserJock: I know some userland apps have trouble with >4GiB but I'm unaware of a 2GB barrier01:27
LaserJockreally?01:27
LaserJockwe used to have 2GB barriers all the time01:27
jdongLaserJock: maybe I was just really really poor when I started with Linux 2.4 :D01:27
LaserJockwas a problem when DVD .isos started being made01:27
jdongLaserJock: oh yeah, wget had a 2GB barrier didn't it.01:28
LaserJockyep01:28
jdongyeah you're right, you might be hitting userland size type barriers01:28
LaserJockI believe that stemmed from "well, we can't make a file bigger than 2GB anyway"01:28
jdongbtw I liked your piece on Fedora01:29
jdongI think it roughly mirrors my experience with the distro and its community too01:29
LaserJockglad somebody thought it was ok01:30
LaserJocknext up I'm gonna look at Fedora and Ubuntu SRU policies01:30
LaserJockthat's the one I'm gonna put my fire suit on for ;-)01:30
RAOFI thought Fedora didn't freeze, and as such didn't really have a SRU policy?01:31
jdongLaserJock: yeah you're really gonna need a fire suit for that01:31
jdongRAOF: they partially freeze01:31
jdongRAOF: i.e. they won't bring in big things that'll break the world01:31
LaserJockthey have a "be sensible" freeze01:31
jdongRAOF: i.e. toolchain, certain kernel updates, GNOME core01:31
jdongRAOF: but they will feel free to bring in basically anything we call universe01:31
RAOFRight.  That makes sense.01:31
jdongIMO it's sensible for the home Linux enthusiast01:32
LaserJockbut there are some other more philosophical things as well I'm gonna try to hit on01:32
jdongit's not terribly appropriate for the enterprise deployment01:32
jdongand I think that's something that needs to be addressed in your thoughts on it, LaserJock01:32
RAOFWhich means that their SRU policy is likely at least as stringent as Ubuntu's, right?01:32
jdongi.e. Ubuntu tries to cater to both enterprise and enthusiast users01:32
jdongwhile Fedora only has to dealw it hthe latter.01:32
jdongRHEL's SRU policy is even more stringent than Ubuntu's01:32
RAOF(If we restrict 'stable' to mean 'the part that's frozen')01:32
jdongRAOF: correct01:33
jdongRAOF: they do RHEL-style backporting for the part that's frozen01:33
LaserJock"As a 32-bit UNIX system, Linux can handle files not longer than 2Gb."01:33
jdongRAOF: but that's less of a concern for the end user that just wonders why the latest K3b isn't available in a 4-month-old release01:33
RAOFjdong: Yeah.  It makes a lot of sense for some fraction of the userbase.01:34
zulbye bye reiser01:35
jdongRAOF: I like Ubuntu's duality and I think ultimately our best solution is to cater to Fedora-like users with a more expanded, open Backports-style effort, while still doing traditional SRUs side by side01:35
jdongRAOF: there's no reason why they have to be mutually exclusive the way they are now01:35
jdongif someone wants to bring in KTorrent 2.0.4 to fix a bug in KTorrent 2.0.3, there's no reason why we should reject that just because we *can* do a SRU patch-backport01:36
TheMusozul: I saw that.01:36
RAOFjdong: Have some sort of Debian-testing like backports thing?01:36
TheMusoLaserJock: Yeah I liked your piece on Fedora. I intend installing Fedora on a new box I got recently alongside other distros. I want to see whats going on elsewhere.01:36
zulTheMuso: let the jokes begin :)01:36
LaserJockI was honestly surprised01:36
jdongRAOF: yeah, I'm thinking a backports-proposed repo that all MOTUs are allowed to upload any (reasonable) packaging of their choosing01:36
LaserJockfor my laptop Fedora would be my #2 distro01:36
LaserJockDebian's nice but takes quite a bit of work on my laptop01:37
jdongRAOF: and then the backports team ACKs such packages for copying into backports01:37
jdongLaserJock: I feel better having some OS diversity across my systems too01:37
jdongLaserJock: I'm strongly considering turning one of my systems to Fedora01:37
LaserJockjdong: the problem I personally have -backports is I almost never want the whole thing01:37
LaserJockjdong: it's well worth having a look at what they're doing01:38
jdongLaserJock: perhaps we need to handle pinning better via update-manager and apt/preferences then01:38
RAOFIsn't it by default pinned so that you can install individual things & pull in the necessary deps?01:38
jdongRAOF: no default, backports is shut off entirely01:38
jdongRAOF: turning it on, update manager recognizes backports separately but checks them all by default01:38
RAOFjdong: I mean, once you turn it on.01:38
jdongRAOF: and also, update-manager nags about backports updates just like any other update01:39
jdongRAOF: when you turn it on, it's not pinned at all01:39
RAOFOh, right.  Yeah, that could be better.01:39
LaserJockjdong: what if we did something more like Main -> more enterprise like, Universe -> more desktop like01:39
LaserJockand have a strict SRU policy for Main and Fedora-like for Universe?01:39
jdongLaserJock: doesn't handle the use case of transmission, KTorrent, and other universe-like apps that seeped into main01:39
jdongLaserJock: but in general that distinction works well01:40
LaserJockjdong: but those could be perhaps handled via exceptions?01:40
jdongLaserJock: perhaps the added provision that we are allowed in universe-SRU to override a main package01:40
jdong(puts on flamesuit!)01:40
LaserJockyikes01:40
RAOFOr a reworking of the archive structure, ala that u-d thread.01:40
jdongLaserJock: it sounded better before I wrote it down!01:40
LaserJockRAOF: that would be a rather messy SRU policy01:41
LaserJockI'm not sure how we'd do it there01:41
LaserJockper-seed SRU policies sounds like not-so-fun times01:41
jdongLaserJock: my opinion still stands that we should open backports uploads to all SRUs and filter them through a -proposed queue on backports01:41
jdongand keep SRUs  there too01:42
LaserJockhmm01:42
jdongthere's defintiely some packages in universe we want to do regular SRUs for, like lighttpd, clamav, etc01:42
LaserJockI kinda am not found of that idea01:42
LaserJock*fond01:42
jdongand IMO those two styles of updating should be kept as independent efforts in independent repos01:42
jdongFedora makes no attempt to combine them01:42
jdongwhich is why Fedora is not designed for an enterprise environment01:42
LaserJockif an SRU should be done it should be done, doing it in -backports seems like a workaround01:42
jdongLaserJock: it might be a workaround but is a faster , more effortless soltuion that satisfies the enthusiast user01:43
jdongLaserJock: it doesn't preclude the delivery of a SRU01:43
LaserJockmaybe we can have an SRU policy that accommodates that though01:43
jdongLaserJock: that's like the archive admins refusing to pull a faulty update because it's a workaround of uploading a new fixed one tomorrow ;-)01:43
LaserJockwell, let me rethink this01:43
jdongthey should be complementary01:43
LaserJockI guess in a broad definition of SRU it makes sense01:44
LaserJockso if we break it up into bug SRUs and feature SRUs01:44
jdongLaserJock: I think it makes more sense to break this down in terms of use cases01:44
LaserJockthen we have a reasonable definition of -updates and -backports01:44
jdongwe clearly have two different usecases that Ubuntu tries to meet:01:44
jdong(1) Joe User is running Ubuntu on his personal laptop. He hears about the newest KTorrent that fixes 2 bugs and adds a major new feature. He wants to try it out.01:45
jdong(2) Bob Sysadmin manages an enterprise KDE rollout. He is concerned about 1 of the bugs in KTorrent which is a remote crasher but doesn't want the risk of regressions from the unrelated updates.01:45
jdong#1 should be handled as a backport and #2 should be a traditional SRU01:45
LaserJocksure01:46
jdongboth can be offered side by side because typically it's different people who want them01:46
LaserJockthat's the current situation, IMO01:46
jdongand in fact different people who will perform the update01:46
jdongLaserJock: current situation is technically we're not allowed to backport for the purpose of bugfixing01:46
jdongLaserJock: and also backports must be derived from development packaging, when sometimes current packaging + uupdate is more appropriate01:46
LaserJockbut that would be a SRU under your scheme01:46
jdong(i.e. when Intrepid undergoes some migration or rocky packaging)01:46
jdongwhat I'm saying is we should be allowed to do both. Both backport with intent to fix bugs AND introduce new features01:47
LaserJockwell01:47
LaserJockthat's kinda grey01:47
jdongthe only major issue I see is versioning convention01:48
LaserJockif doing a new upstream releases fixes bugs I don't think anybody is going to complain ;-)01:48
LaserJockbut the purpose of -backports is for user 1)01:48
jdongLaserJock: indeed , but the current imposed limitations on backports doesn't satify user #101:48
LaserJockjdong: why?01:48
jdongLaserJock: I'd estimate 25% of backports requests get approved ultimately.01:48
ScottKjdong: Backports shouldn't be a workaround for SRUs are to hard.01:49
arpuhi01:49
arpui hope here am right01:49
jdongLaserJock: the remaining 25% are packages that FTBFS due to a migration, 25% are bugfix-only updates that the archive admins would reject, and the remaining are during a freeze or other case where development branch cannot receive the new version necessary01:49
arpucan someone help me with this bug ? https://bugs.launchpad.net/ubuntu/+bug/22384301:49
arpu  i found out it have nothing to do with the xrdb error messages in .xsession-errors01:49
ScottKjdong: I think backporting for non-sru worthy bug fixes should be fine.01:49
jdongScottK: I don't think we need to preclude backporting SRU-worthy fixes either01:50
ScottKI've been accepting that all along in fact.01:50
jdongScottK: because there's no reason why the presence of that backport would discourage/preclude a SRU anyway01:50
LaserJockjdong: but they should be fixed in -updates?01:50
jdongLaserJock: ideally they should be fixed in both01:50
ScottKjdong: I think they should do the SRU first if it's feasible.01:50
jdongLaserJock: independently at their own pace01:50
LaserJockjdong: well, sure01:50
LaserJockbut there's nothing that says you can't do that now01:50
jdongone should not discourage/preclude the other01:50
ScottKjdong: I think that's a good theory, but in practice backports do take the pressure off getting an SRU done.01:51
LaserJockI just don't know why you'd want to do the same thing twice01:51
jdongScottK: should we really be artificially be imposing that pressure to favor SRUs though?01:51
ScottKIt's not the same thing twice.01:51
ScottKjdong: We should.  -updates is enabled by default and -backports is not.01:51
jdongLaserJock: a SRU fix is often not the same as a backport both in the patch itself and the validation process involved01:52
ScottKEach for good reasons..01:52
LaserJockScottK: why isn't it?01:52
jdongLaserJock: volatility and reduced QA01:52
LaserJockI'm just not sure I have good realistic cases here01:52
jdongLaserJock: backports is pretty lax on letting new packages in and they're probably at a higher regression risk01:52
LaserJockjdong: so?01:52
jdongLaserJock: users might cry and whine when backports breaks things01:53
jdongnot like they don't when -updates breaks things ;-)01:53
LaserJockwhat I'm saying is, if a bug is SRU worthy, then should get it into -updates01:53
ScottKThe standard for backports is "Builds, Installs, Runs".  Updates go through rather more QA.01:53
LaserJockwhy would we then do the same thing in -backports?01:53
LaserJockwhen the user is getting the fix from -updates01:53
ScottKWe wouldn't do the same thing.01:53
jdongLaserJock: because it's often not the same thing01:53
LaserJockthen I don't see the problem01:53
LaserJockyou can already do it01:53
jdongLaserJock: the backport would be we take the latest upstream tarball and package it and upload it01:53
LaserJockjust upload your new upstream release01:53
ScottK-updates would get a targetted patch.  -backports gets the whole new version.01:53
LaserJockScottK: that's my point01:53
jdongLaserJock: the SRU would be examining the changes line-by-line and isolating only the useful ones01:53
LaserJockthere's no reason you can't do that now01:54
jdongLaserJock: other than the limitations the TB imposed on backports01:54
LaserJockno01:54
jdongLaserJock: i.e. speicifcally we are not allowed to backport for bugfixing reasons01:54
LaserJockbut you aren't01:54
LaserJockyou're backporting a new version that happens to fix a bug01:54
LaserJockno biggie01:54
jdongLaserJock: try telling the archive admins that ;-)01:54
LaserJockwhy would they object?01:54
jdongLaserJock: I've gotten rejected backport approvals for that reason before01:55
LaserJockhow would they  know?01:55
jdongLaserJock: i.e. "this looks like it should be SRU, won't do"01:55
jdongLaserJock: they read the backports bug tickets01:55
LaserJockhmm, I guess I'm not really up on -backports, I can't imagine why there's an issue01:55
LaserJockif a bug is SRU worthy then it should be in -updates01:56
LaserJockthat says *nothing* about -backports01:56
jdongLaserJock: agreed01:56
jdongScottK: do you think I'd be in a shark-infested pool alone to propose that -backports get a -backports-proposed where all MOTUs are allowed to upload? ;-)01:56
LaserJockjdong: what would that do for us?01:57
persiaI suspect the rationale is that a bugfix oughtn't be backported before it goes to -updates, rather than that bugfixes oughtn't go to backports.01:57
jdongLaserJock: increase the accessibility of the backports path01:57
jdongpersia: I think the ultimate rationale is that IF we allow backports to do it, then nobody would bother separating out the patch for SRU because it's more work01:57
jdongi.e. people would start saying that Backports "fixes" some bug as a solution.01:57
LaserJockjdong: and why do we want that?01:58
ScottKjdong: I think anything that increases archive admin steps is a bad idea in the current archive management paradigm.01:58
persiajdong: Right,01:58
LaserJockjdong: I think that's correct01:58
jdongLaserJock: why do we want the current system that I have to keep ScottK on a leash for sponsoring backports? ;-)01:58
LaserJockwe want to push people to -updates for bug fixes01:58
LaserJockas that's turned on by default and is the minimal use-case for getting a fix to people01:59
LaserJockjdong: I just wondered if you're having a hard time getting backports done or what. I just don't know01:59
jdongLaserJock: at times, yes. I feel like the burden is mostly on ScottK and I to do all of the grunt of the work and people who can be testing can't really test because packages are not readily available02:00
ScottKWe have choke points all along the path.02:00
LaserJockk02:00
LaserJockI don't do backports because I don't use -backports02:00
ScottKNot enough testers, not enough core-dev support, not enough archive admin time.02:00
LaserJockthat's sort of a limitation02:00
=== twanj____ is now known as twanj
jdongLaserJock: backports would work great from a community testing model where users volunteer as guinea pigs for a -proposed archive of just generously-built backports02:01
jdongLaserJock: msot of the users I speak to have no reservations about putting their systems up for such a job02:01
jdongLaserJock: but they also are afraid of the pbuilder/prevu build process02:01
LaserJockhmm02:02
LaserJockwhat if you had a PPA? or do you do that already?02:02
jdongLaserJock: imagine if all SRU verifications had to be done by posting a debdiff and asking users to "go test"02:02
jdongLaserJock: well I've considered using a PPA to simulate such a build but I'd like it better if it were something official02:02
LaserJockhmm02:03
LaserJockit just seems to me that we should be able to create common testing grounds/tools/strategies02:03
LaserJockI don't think we get nearly enough testing from -proposed02:04
jdongLaserJock: the other advantage of having an archive is the ability to directly copy a tested backport verbatim, without having to deal with the race condition of the devel branch getting a new upload02:04
ScottKWe get 'go path' is the bug fixed testing, not are there regressions testing.02:04
jdongLaserJock: I don't think users are too aware of the SRU -proposed archive sheerly because of its low volume and "uninteresting" updates02:04
jdongLaserJock: I'd venture a bet that a theoretical testing backports repo that accepted new version backports of everything to be quite "popular" ;-)02:05
jdong(good thing or not, I won't say!)02:05
LaserJock*sigh*02:06
LaserJockI suppose02:06
jdongmaybe I've just completely lost my sanity tonight :)02:06
LaserJockif we could get more testing though I think we could have more interesting uploads to -proposed02:06
ajmitchs/tonight//g02:06
jdongLaserJock: there is this viscous cycle :)02:06
ScottKjdong and LaserJock: My clamav updates to Dapper are perhaps an interesting hybrid.  That went PPA (test) -> dapper-backports (test) -> dapper-updates02:08
ScottKclamav and a all the needed rdepends02:09
LaserJockin reality, I think -proposed is almost useless02:12
LaserJockfor almost all SRUs your not gonna just enable -proposed and say, "Oh, they fixed that, cool"02:13
ScottKWhen there was a bad upload of svn to gutsy-proposed a few months ago we got a lot of bug.02:13
* ScottK would never just enable proposed (although apparently people do).02:13
LaserJockpeople most often have to read the bug report, check out the use cases, and actively test02:13
LaserJockyou're pretty much just as well to attach a .deb or link to a PPA02:14
ScottKWhat proposed gets you is knowing exactly what's going to end up in -updates is what got testing.02:15
LaserJockyep02:15
ajmitchassuming that people actually test & give feedback on -proposed02:15
ScottKThat and you aren't encouraging people to install random software from bug reports/third party repos.02:15
LaserJockbut having an option for it in "Software Sources" does pretty much nothing02:16
LaserJockif you know what I mean02:16
wgrant-proposed and -backports should really be pinned when enabled... why don't we do that?02:16
ScottKGood question.02:17
* wgrant hasn't read the whole conversation, as he's at work.02:17
LaserJockI'm just trying to think of some ways that we can actually get some testing for SRUs02:18
LaserJockas I think that opens up a lot of possibilities02:18
wgrantHave people subscribe to a mythical testing ML, to which emails soliciting SRU testing are sent.02:19
LaserJockthat's a good idea02:20
LaserJockhmm, I wonder if something along the lines of the iso tracker could be used02:21
LaserJockand plugging more into the QA team02:21
LaserJocksay we had a page with a list of packages02:23
LaserJockand then individual pages for them that give the test case and a place to click on a "worked for me"02:23
LaserJockthen promote the snot out of it02:23
bddebianHeya gang02:25
* ScottK is envisioning this page on Launchpad. It will be slow and very confusing, but look really cool.02:26
ScottKheya bd.02:26
ScottKbddebian even02:26
ScottKGotta hit tab for the tab completion to work.02:27
bddebianHeya ScottK02:27
ScottKleonel: Debian package of clamav 0.93 is up in the clamav PPA.03:21
ScottKsoyuz eating ppa uploads for anyone else?03:42
ScottKNevermind.  Finally showed up.03:50
=== dmb_ is now known as dmb
ScottKThree cheers for upstreams that rely on internal interfaces of things they build against.04:11
* ScottK slaps klamav across the room and heads for bed.04:11
=== greeneggsnospam is now known as jsgotangco
Zelutso when I try to build a package with dpkg-buildpackage it complains about no Makefile04:22
Zelut..but it has the instructions it needs in the rules file.  I'm lost..04:22
TheMusoZelut: Is the rules file executable?04:22
ZelutTheMuso: it is04:23
TheMusoWell obviously a makefile is not found, which the rules file in calling the make command, says it needs.04:23
Zeluthttp://pastebin.ca/1001327 - this is the output of my attempt.04:24
Zelutthe application does not need to be compiled. the rules file just needs to install them to a few locations.04:25
ZelutI guess I don't see / am not familiar enough with the rules file to see why/where its looking for a Makefile04:26
persiaLine 27.  It calls make.  This implicitly looks for a Makefile.04:29
Zelutthis is my first rules file.. let me paste what I have and maybe ya'll can tell me what to trim04:30
* persia suspects the problem is the use of dh_make04:31
Zeluthttp://pastebin.ca/100133304:31
persiaOK.  Quick look: firstly, do you have a ./configure in the source?04:31
ZelutI don't.04:32
persiaOK.  Then you likely don't need either of the configure or configure-stamp rules.04:32
Zelutall this package needs to do is place 'origami' in /usr/bin and the docs in /usr/share/doc.04:32
persiaKeep walking through the file with the same sanity check.04:32
persiaFor something that simple, I'd recommend just having a CDBS include of debhelper.mk, and an entry in debian/origami.install04:33
ZelutI'm fine with that too if you want to walk me through that :)04:33
persiaZelut: OK.  Rules file is two lines.04:37
persia#!/usr/bin/make -f04:37
persiainclude /usr/share/cdbs/1/rules/debhelper.mk04:38
persiadebian/origami.install is one line04:38
persiaorigami usr/bin04:38
persiaadd CDBS to the build-dependencies in debian/control04:38
Zelutdone04:39
Zelutdo I need to add the docs I want in /usr/share/doc/origami into the origami.install file?04:40
copprowhat is the proper way to use dh_compress and dh_installman?04:41
copproassuming I have a prog.1 file already04:41
StevenKZelut: List them in debian/origmai.docs04:41
TheMusocoppro: List it in debian/package.manpages04:41
copprodh_compress first, right?04:42
TheMusocoppro: I think you shouldn't have to give any arguments to dh_compress04:42
TheMusoNo.04:42
ZelutStevenK: thank you.04:42
TheMusodh_man first.04:42
copprook04:42
Zelutpersia: ok, so what do I use to build this voodoo magic?04:42
copprothanks. let's see if this works04:42
persiaZelut: debuild :)04:42
persia(assuming CDBS and debhelper are installed)04:43
StevenK% debuild :)04:43
StevenKzsh: parse error near `)'04:43
* StevenK hides.04:43
crimsunmksh: syntax error: ')' unexpected04:43
persiaRight then.  `debuild # :)`04:43
crimsun1|04:43
TheMusohaha04:44
Zelutpersia: wow.. so it built.  cdbs is magical voodoo isn't it :)04:44
persiaYes.  It's magic.  For simple things, magic is quick and easy.  If it gets complex, it may be worth unwinding (I really don't like the sendmail debian/rules)04:45
Zelutnow, lets say I wanted this package to run three basic commands to clean something up.  How would I do that?04:46
persiaSee, that's where you start getting into deep magic.  You'd add an override rule.  Look at the CDBS documentation from perso.duckcorp: it has a list of common overrides.  When you get longer than about 30 lines, you likely don't want to be using CDBS anymore.04:47
Zelutok.04:48
copproand where can I find the correct list of possible options to fix a doc-base-unknown-section error?04:52
copproI can't figure it out!04:52
=== RAOF_ is now known as RAOF
=== dmb_ is now known as dmb
a7xi wrote a patch to fix a bug (LP: #221661).  would someone be willing to review it and tell me if it's OK?05:08
a7x(perhaps ubuntu-devel is a better place to ask...  i'll try there)05:13
persiabug #22166105:13
gnomefreaka7x: it might be easier to apply the patch and upload to revu05:13
gnomefreakpersia: bot is gone05:13
persiaErm, no.  bugfixes don't belong in REVU: that's for new packages.05:14
gnomefreakah05:14
gnomefreakdebdiff on bug report thats right05:14
persiaFor bugfixes, best to generate a patch, either put it in a debdiff (or have someone else do that), and subscribe the sponsors.05:14
a7xi'm new:  what's debdiff?05:17
jdonga7x: you'd really want to catch mvo or Amaranth who are both familiar with compiz enough to give you a meaningful answer05:18
leonelScottK: Great  diffs I'll send them tomorrow05:18
jdonga7x: intuitively from looking at the patch I side with you that the current use of export $ENV does nothing useful05:18
persiaa7x: You might want to take a look at https://wiki.ubuntu.com/MOTU/Contributing (although you may well find someone here who would review your patch)05:18
a7xjdong and persia:  thanks05:19
copprohow do I get rid of doc-base-unknown-section05:19
bimberibr1|: /win 1105:20
bimberiwell that was deft05:23
warp10Good morning06:13
* persia is amused by intrepid FTBFS reports, and wonders if the FTBFS tracker is watching intrepid yet06:18
StevenKHah06:20
wgrantpersia: It is now.06:22
wgrantIt's not right, but...06:22
wgrantI can't see why.06:24
YokoZarHey, what exactly do I put into dput to upload to hardy-proposed for an SRU?06:26
YokoZarincoming = /hardy-proposed/ ?06:27
persiaAll 0?  Strange.  I received at least two reports for hppa.06:27
wgrantpersia: As did I.06:27
wgrantWell, they were for lpia, and one for hppa.06:27
YokoZaractually launchpad rejected incoming = /hardy-proposed06:27
persiaYokoZar: just upload to ubuntu as usual, with hardy-proposed in your .changes file06:27
persiaActually, I've a couple powerpc failures as well.06:28
ajmitchYokoZar: new wine for -proposed already? :)06:28
wgrantAh.06:28
wgrantrmadison is broken.06:28
YokoZarpersia: you mean as distribution?06:28
persiaYokoZar: preceisely06:29
YokoZarajmitch: Yeah the package needs to depend on lib32nss-mdns otherwise dns can't be done on amd6406:29
persiaYou can set this in your changelog entry06:29
wgrantHmm, I think intrepid is borked.06:30
wgrantIt has no packages.06:30
ajmitchborked, or just not setup fully yet?06:31
ajmitchYokoZar: yes, that's a definite issue06:31
wgrantBoth.06:31
wgrantYokoZar: Isn't that only the case when libnss-mdns is installed?06:31
StevenKwgrant: The Packages files seem large enough06:32
persiaHrm.  Somehow I don't think the buildds ought be running intrepid before it's set up...06:32
wgrantStevenK: Ah, it didn't have any packages a few hours ago, and I presumed that was why rmadison was being empty. I see it has packages now.06:34
StevenK(hardy)root@liquified:~# grep -c Package /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_intrepid_*Packages | cut -d: -f2 | numsum06:34
StevenK2481906:34
wgrantI see LP even says it has packages.06:35
persiaSo rmadison ought catch up with the next run of some cronjob?06:36
wgrantSo somebody needs to fix rmadison.06:36
wgrantIs rmadison using a dak import, or some new Soyuz-specific implementation?06:36
StevenKNeither06:36
wgrantStevenK: What, then?06:37
StevenKwgrant: It runs madison-lite06:37
wgrantAha.06:37
wgrantStevenK: Should I poke some archive person about it when they appear?06:43
StevenKI don't see the point bugging them until the toolchain is uploaded.06:44
persiaIs it not yet?  Why am I getting build failure messages then?06:51
persiaIs it just trying to rebuild packages with the old toolchain when the binary version doesn't match the source version?06:52
wgrantpersia: That's right.06:53
wgrantIIRC the build queue thing creates build records for the next distroseries if the build in the previous distroseries failed.06:54
persiaNifty.  All the FTBFS's that don't with the latest build tools ought get fixed then :)06:54
=== Coper_ is now known as Coper
wgrantYay, we have a bot.06:56
StevenKwgrant: rmadison should be sorted.07:35
janimosiretart: hi, do you know if the pulseaudio fixes and improvements mentioned in libxine 1.1.12 relnotes are the same ones backported in ubuntu's 1.1.11.1-1ubuntu3?07:38
Taylorhey kahrytan can't you get to terminal? ctrl+alt+f1?07:52
kahrytanTaylor,  What?07:52
Taylorkahrytan: because if you can get to the terminal by pressing ctrl+alt+f1, then the monitor isn't supported by xorg by default07:53
kahrytanI can get to it but screen resolution is messed up. Text is enlarged.07:54
kahrytanYou must have been in club.07:54
siretartjanimo: yes, at least they should be. why?07:55
janimosiretart: thanks07:55
janimosiretart: PA does not seem to get along with totem-xine07:56
kahrytanTaylor,  Why you talking to me here?07:56
janimosiretart: and I was suggested to maybe check out the latest xine which has PA fixes07:56
siretartwe had testers on launchpad claiming it would work07:56
Taylorkahrytan: because you left ##club-ubuntu07:57
kahrytanNo one talked.07:58
Taylorkahrytan: that's true07:58
Taylorkahrytan: did you try editing the xorg config?07:59
Taylorpm07:59
kahrytanyeah07:59
kahrytan!pastebin > kahrytan08:00
kahrytanBug #220952, someone added linux-restricted-modules-2.6.24 to the bug even though it has nothing to do with nvidia drivers.  Though, someone did attach mandriva #40403 bug to it and it mirrors the same problem. Could someone correct the bad attachment.08:37
persiakahrytan: That's really an #ubuntu-bugs question: looking anyway08:39
kahrytanaww. ill redirect in the future08:39
* persia waits for a join for feedback...08:41
emgentmorning08:43
kahrytanWhat is motu?08:43
highvoltagemotu is an acronym for 'masters of the universe'08:44
highvoltagethey take care of the 'universe' component of ubuntu08:45
highvoltagewhich is the community maintained part of ubuntu08:45
kahrytanOh08:45
highvoltageso the motus are mostly community developers08:45
kahrytanThen, are you to blame for adding the broken Alien Arena to Hardy08:45
highvoltagethe motu-games team have merged with the debian games team.08:45
kahrytandarn08:46
highvoltagein short, the answer to your question is yes.08:46
kahrytanThe game is broken .. seems well known08:46
highvoltagebut you might have to hound the debian-games team for that problem :)08:46
highvoltagethat's a pity. it's a very popular game.08:46
persiaWell, a fair number of debian-games people are also here08:46
kahrytantry playing it for more then 2 maps on single player ...08:46
kahrytan2008 version works from google search.08:47
norsettohappy SRU'ing everybody09:53
YokoZarnorsetto: Indeed...already got one for Wine...10:40
iulianG'morning10:54
jpatrickmorning iulian10:55
iulianHey jpatrick10:56
norsettoway to go yokozar11:03
proppyoy11:33
=== Nightrose_ is now known as Nightrose
norsettosuper proppy is in, all bow11:51
* proppy hail to norsetto11:54
wgrant\o/ .*11:54
proppy.* = fireworks ?11:54
wgrant.* == regexp11:54
proppyaah ^.*$11:55
wgrantNo point doing that.11:55
wgrantRestricting that there are 0 or more of any character anywhere in the line should be somewhat similar to matching 0 or more of any character being the entire line.11:56
proppysure, but it's pretty11:56
wgrantFSVO pretty.11:56
proppyuseless is pretty11:56
proppywgrant: FSVO ?11:57
wgrantFor some values of.11:57
sistpoty|workhi folks12:09
emgentheya12:17
sistpoty|workhi emgent12:17
=== __Czessi is now known as Czessi
Myrtti!bot12:52
ubot5I am ubot5, ubotu's backup today. :)12:52
Hobbseeah, there we are12:53
zul\sh: ping12:59
\shzul, pong13:01
zul\sh: do you do the php-xdebug stuff for universe?13:01
\shzul, I uploaded and bugfixed the packages, yes13:02
zul\sh: : have you seen #21798013:02
\shbug #21798013:02
sistpoty|workubotu must be on holidays :)13:03
\shzul, hmm?? no open bugs?13:03
zulcheck the apache2 bug listing for 21798013:04
\shzul, yes...I have it now13:04
\shwell, the problem is zend-platform ;)13:04
Kopfgeldjaegerhoi13:05
zul\sh: well no the user says he had to remove php5-xdebug13:07
\shzul, yes, because zend-platform does not support other modules next to it13:07
zul\sh: ok13:07
\shzul, acrtually zend-platform is closed source, in our company the situation was that, that we couldn't use zend-platform with xdebug, because zend-platform doesn't like some compile options13:08
azeembtw, is the UTF8 character at the beginning of the /topic intentional?13:08
\shzul, btw..this applies on windows, too13:08
zulcare to comment on the bug report then13:09
\shI'll do...I'll subscribe to the bug and do a full knowledge transfer this evening from home...13:10
* \sh just wonders why he doesn't use the build in zend module for debugging, which is delivered with zend-platform13:11
zulthanks13:11
\shwell, most likely it crashs because of the strange compile stuff they need...and the build in module works only with zend-core apache package, which doesn't work with php-xdebug, too ;)13:11
ScottKSo.  I've got this opensuse src.rpm that I know must have the patch I need in it.  What's the easy way to break into this thing and extract stuff?13:23
lagaScottK: turn it into a tar.gz using alien?13:24
ScottKMaybe.  I'm asking.13:24
ScottK\sh: You used to do rpm stuff all the time.  What do you recommend?13:24
HobbseeScottK: running away.13:27
ScottKlaga: That seems to work.  THanks.13:27
ScottKHobbsee: That's worked up to now.  Unfortunately klamav FTBFS with the new clamav just uploaded to Debian and opensuse seem to have got it working.13:27
\shScottK, you just need to extract a patch?13:28
\shScottK, apt-get install rpm ; mc ; choose the rpm <enter> voila13:28
ScottKmc does that.  Cool.13:31
\shScottK, the magic is pkg rpm ;) without it, it doesn't extract the cpio ;913:32
\shzul, anyways..updated the bug report...you can decide to invalid it13:32
zul\sh: thanks13:33
ScottKRight.13:33
ScottKThe magic opensuse solution was "remove klammail as it no longer builds against clamav".  Urgh.  I'd hoped for actual fixing.13:39
\shlol13:39
=== danielm_ is now known as danielm
ScottKEven better their patch removed the binary, but left the UI for the now missing function.13:43
sistpoty|workyay, I win with the first package in hardy-updates :)13:44
lagadamn :)13:46
ScottKsistpoty|work: I'm not sure that's actually a 'win'.13:54
HobbseeScottK: depensd if it builds or not.13:55
ScottKYeah.  Particularly in this case.13:55
sistpoty|workhm? it is already published actually, so it did build... :)13:58
DktrKranz2sistpoty|work: re bug 208666, I'm not suure Debian's binNMUs are synced or rebuilt automatically, so we probably need a manual rebuild.13:59
sistpoty|workDktrKranz2: yes... error on my side. the source version is not changed, so nothing to sync. I'll take care once intrepid is open13:59
DktrKranz2sistpoty|work: thakns. and congrats to be the first one to populate hardy-updates :p14:00
sistpoty|workthanks :)14:00
DktrKranz2*thanks14:00
=== asac_ is now known as asac
Kopfgeldjaegercan i already upload debdiffs to launchpad and subscribe u-u-s? or doesnt it make sense yet?14:12
cody-somervilleKopfgeldjaeger, For hardy?14:14
Kopfgeldjaegerfor intrepid14:14
cody-somervilleSure, upload it.14:14
Kopfgeldjaegerok14:14
cody-somervilleIt won't be uploaded until Intrepid is open but you'll be able to get it reviewed and what not and be able to get it in quick once it is open.14:15
Hobbseeassuming the package doesn't need a merge, or further modifications to make it build.14:17
sistpoty|worknorsetto: I've been playing with libitpp yesterday evening, but I couldn't actually find s.th. which doesn't work with the *old* version. any hints what I could try?14:18
sistpoty|work(as I'm looking for a good test case)14:18
norsettosistpoty|work: can't help you there, I have spent days looking for something too without success14:19
sistpoty|workah, k14:20
Kopfgeldjaegerhow can i make debdiff not show the /tmp directories? i mean, when i debdiff two .dsc's, i get something like this: http://nopaste.com/p/aFY7mefYB14:49
Kopfgeldjaegerbut of course i only want the path starting from gthumb-2.10.6/...14:49
Kopfgeldjaegeri knew the solution some time ago :/ but i've forgotten it14:50
HobbseeKopfgeldjaeger: cd into the directory which contains the gthumb-* ?14:50
Hobbseewhihc appears to be different directories, in your patch14:50
persiaKopfgeldjaeger: Generally, install patch-utils.  If that's not enough, you're working on a native package.14:51
Hobbseepersia: oh, so that's the problem.14:52
Kopfgeldjaegeryeah. i thought the solution once was to install the package patch-utils and then debdiff behaved the "right" way. but patchutils is installed :/14:52
HobbseeKopfgeldjaeger: uh, those sources are in 2 different parent directories, in /tmp.14:53
HobbseeKopfgeldjaeger: it's never oging to wokr if you do that.14:53
sistpoty|workKopfgeldjaeger: hm... this looks like you're trying to debdiff too different upstream versions (at least the dirs indicate that)14:53
Hobbseeor otherwise the patch paths are borked14:54
KopfgeldjaegerYes. So I guess I shouldn't do that?14:54
persiaKopfgeldjaeger: You can't debdiff that.  Just attach the diff.gz, and the sponsor will unroll it (make sure you have a working get-orig-source rule)14:54
Hobbseepersia: why can't you?  i've done so before, iirc14:54
KopfgeldjaegerOK. thanks.14:54
persiaHobbsee: Well, it works in some rare cases, but it's not guaranteed.  Essentially, debdiff can't handle the sort of changes that are permitted in orig.tar.gz, so it's not recommended to use it.14:55
persiaI'm not sure how debdiff will handle the new packaging formats, or if we will have to define a special procedure to handle processing patches for each one.14:56
Hobbseehm, right14:56
Kopfgeldjaegerpersia: Just one question left. Can you give me a link about this get-orig-surce rule?14:57
persiaKopfgeldjaeger: I believe https://wiki.ubuntu.com/PackagingGuide/Examples/ChangingTheOrigTarball is the best in Ubuntu, but the Debian wiki likely has more14:59
Kopfgeldjaegerthanks14:59
CrippledCanaryI need some help.... i found a bug #221973, which is now in hardy-proposed but now i found another bug that just shows when upgrading... should this be addressed to in the SRU?15:01
ubot5CrippledCanary: Error: Could not parse data returned by Launchpad: The read operation timed out15:01
CrippledCanarybug #22197315:01
ubot5Launchpad bug 221973 in smstools "smstools folder under /var/run isn't recreated after reboot" [Undecided,Confirmed] https://launchpad.net/bugs/22197315:01
ScottKCrippledCanary: Is it another bug or does your fix cause a regression?15:02
CrippledCanaryit's another bug... but it stops the smsd daemon from working when doing an upgrade15:03
CrippledCanarya line in the config that before upgrade is ......   # eventhandler = @EVENTHANDLER@15:03
CrippledCanarybut after upgrade it gets uncommented15:03
CrippledCanarydoing a clean install of the new version works and the line is commented out15:04
CrippledCanaryprolly something in postinst15:04
jdongDear Compiz:15:04
jdongThe bullet point toolbar is *NOT* the main Openoffice Writer window.15:04
sistpoty|workCrippledCanary: I guess that should be fixed as well15:04
jdongThe one you're looking for is the one that occupies 230MB RAM currently.15:04
jdongPLEASE don't think I closed openoffice every time the freaking toolbar disapears!15:05
jdongLove, John15:05
sistpoty|workheh15:05
jdongP.S. Do it one more time and I'll go back to LaTeX15:05
CrippledCanarysistpoty|work: then someone will need to help me sort it out15:06
proppyjdong :)15:06
ScottKCrippledCanary: I'd finish your current SRU (as it affects all users and not just upgrades) and then evaluate if another SRU is warranted.15:06
ScottKBut that's just me.15:06
sebnermok0: sistpoty|work: heya. You may also want to add a testimonial. https://wiki.ubuntu.com/StefanEbner ^^15:07
CrippledCanaryScottK: sounds as a reasonable solution to me to but I wanted to check here first...15:07
mok0sebner: sure, I will write something15:08
sistpoty|worksebner: lol at the current testimonials15:08
sebnerhrhr ^^^15:08
sebnermok0: thx :)15:08
sistpoty|worksebner: must add s.th. from home, I have no clue how to log in to the wiki from work *g*15:09
mok0sebner: ah, you're hellboy95? Hehe15:09
sebnersistpoty|work: np np np15:09
sebnermok0: yeah ^^15:09
DktrKranz2CrippledCanary: if it's urgent enough, you can push ubuntu0.2 and go to verification phase with two different test cases15:09
sebnerDktrKranz2: ah, I was looking for you. please write a testimonial :P15:10
DktrKranz2sebner: sure. 150 euros15:10
* mok0 will abstain from making nasty comments about Austria and pedophiles15:10
mok0Ooops15:11
sebnerrofl15:11
sebnerDktrKranz2: hrhr. free mind and not free beer. how true this is :P15:11
DktrKranz2sebner: I don't like beer :D15:12
DktrKranz2even free one15:12
sebnerdito :)15:12
\shDktrKranz2, free wine -> apt-get install wine ,->15:12
DktrKranz2\sh, wine is good, italian one, of course :)15:13
sistpoty|workapt-get install gerstensaft :P15:13
sebnerDktrKranz2: haven't heard good things about italian wine ;)15:13
sebner*recently*15:13
\shsistpoty|work, ah the very well known gerstensaft...I remember having gestersaft on every invoice of our drink delivery company during redhat times in stuttgart :)15:14
\shgerstensaft even ;)15:14
sistpoty|workheh15:14
DktrKranz2sebner: a silly try from french producers15:14
sistpoty|work(strange enough /me prefers wheat beer though, but that's not in the archives)15:14
sebnerDktrKranz2: hm?15:14
DktrKranz2only french producers dare say something negative about our wines :P15:15
sebnerlol15:15
sebnerDktrKranz2: what about the scandal with chemicals in you wine?15:15
sebner*your15:15
mok0DktrKranz2: You mean the cheap stuff being sold as expensive wines?15:16
\shguys, I switched from french/italian wine to good red wines from stellenbosch, cape area, ZA :)15:16
DktrKranz2mok0: these are french ones, our "brunello" is expensive sold as cheap :P15:17
\shok...end of business15:17
\shcu later515:17
DktrKranz2sebner: I'm still alive, so... I'm immune to chemical stuffs or no chemical in our wines :)15:17
sistpoty|workcya \sh15:18
sebnercu \sh15:18
DktrKranz2woo-hooo... 3 RC closed in Debian today \o/15:18
sebnerDktrKranz2: lol. If it doesn't kill you it doesn't mean that that it isn't dangerous ;)15:18
CrippledCanaryDktrKranz2: It's quite easy to work around so i'll just file another bug and wait.15:20
CrippledCanarythe old working config gets backed up so the only thing to do is to restore that one15:21
DktrKranz2CrippledCanary: ok, then. Subscribe motu-sru when ready. Thanks ;)15:23
CrippledCanarywhat sould i do with the previous SRU bug... just make a comment that I verify the fix (and perhaps give a pointer to the new one)?15:28
jdongoh bloody hell wine in backports FTBFSed on all arches15:28
* jdong looks to see what embarrassing thing he did wrong15:29
DktrKranz2let's get someone check it, two or more people are ok, sru-verification is better15:29
jdongBFD: /build/buildd/wine-0.9.59/debian/wine-dbgsym/usr/lib/debug/./usr/bin/wine-kthread: section `.note.ABI-tag' can't be allocated in segment 215:29
jdongurr....15:29
jdongI swear that didn't happen in my pbuilder15:29
CrippledCanaryI commented the old bug as fixed verified and the new one is bug  #22424115:34
ubot5Launchpad bug 224241 in smstools "smstools stop working after upgrade" [Undecided,New] https://launchpad.net/bugs/22424115:34
CrippledCanaryIs 224241 SRU worthy at all...? should I subscribe motu-sru?15:38
ScottKCrippledCanary: I'd ask a motu-sru member (like DktrKranz2) here what they think.15:38
jdongon the face of it, I think any bugfix that would be worth an upload to Intrepid is also worthy of a SRU15:39
DktrKranz2CrippledCanary: definitely.15:39
jdongCrippledCanary: but pertaining yoru bug specifically, can you please describe exactly how this bug happens?15:39
jdongCrippledCanary: how does the .bak file get created? does the upgrade overwrite a config file? try to "upgrade" the existing config file?15:40
CrippledCanarypostinst creates the .bak file from the original and then creates a new "default" /etc/smsd.conf15:40
bddebianHeya gang15:40
jdongCrippledCanary: err... postinst unconditionally overwrites the config file and just saves a backup?15:41
jdongCrippledCanary: well at any rate, we can "discuss" that "feature" another time, but please do prepare a SRU to fix the default config file :)15:41
CrippledCanaryjdong: I'll try to... not that good at postinst I'm afraid15:42
jdongCrippledCanary: well in this case it looks like the "default" config file is simply malformed15:43
CrippledCanaryjdong: but it works from a clean install with the same postinst script... strange15:44
jdongCrippledCanary: it doesn't feel correct to me that postinst places a dummy config file that's not working by default, regardless of if the user had a previous config file15:44
CrippledCanaryjdong: Can't agree more but that's how the debian folks have packed it15:44
jdongCrippledCanary: agreed, it's not appropriate at a SRU stage to fix that, but if installing the SRU causes configs to break, that's an issue15:45
jdongCrippledCanary: see if you can (1) reproduce the bug (2) more concisely state with reference to lines in the postinst script what's going on15:45
CrippledCanaryjdong: I can reproduce the bug... described how to in the bug report15:46
jdongCrippledCanary: ah, ok, you reproduced it.15:46
jdongCrippledCanary: well in that case I think this should be combined with the other SRU15:47
jdongCrippledCanary: as without it, the other SRU would be a regression.15:47
jdongi.e. installing it causes the config file to bork15:47
jdongCrippledCanary: I think you should modify postinst so that if it detects an existing smsd.conf, it doesn't try to replace it.15:47
jdongprobably get DktrKranz2's opinion on the combining of the SRUs too15:48
CrippledCanaryjdong: should a new SRU be ubuntu0.2 then or just keep adding on to the 0.1 one?15:48
CrippledCanaryand should I assign it to me while trying to sort it out?15:50
jdongCrippledCanary: should be 0.2, since 0.1 is a faulty update15:50
jdongCrippledCanary: and yes, you can claim ownership via assignment if you plan on doing it15:50
CrippledCanaryjdong: I'd guess the best way to learn postinst is to start fixing bugs :)15:51
ScottKCrippledCanary: That's the right idea.  Keep at it.15:51
jdong:)15:51
jdongI think we got ourselves a future MOTU in the making :)15:52
* jdong whispers to ScottK to lock the doors15:52
CrippledCanaryshoud I subscribe motu-sru to the new bug as well?15:52
jdongCrippledCanary: yeah, once the combined debdiff is available15:52
* jdong wonders if we should just merge the two bug reports together15:52
ScottKjdong: First SRU is already in proposed, so shouldn't he just diff against that?15:53
jdongScottK: same result. Ultimately I want 0.2 to contain both fixes15:54
jdongwhether he wants to base off 0.1 or start over from -1 I'm fine15:54
jdongprobably your proposal makes more sense :)15:54
CrippledCanaryIt doesn't matter to me... I just want to use the correct procedures15:54
CrippledCanaryAnd perhaps keeping them as separate bugs is more useful if someone from upstream have a look as the first affects only ubuntu and the second prolly both ubuntu and debian15:56
DktrKranz2jdong: I think uploading a second SRU against ubuntu0.1 is enough, given that we preserve first fix.15:56
DktrKranz2so, once ubuntu0.2 will be copied in -updates, we will ship both SRU fix15:57
CrippledCanaryDktrKranz2: Ok... new patch against 0.1 and fix both in 0.215:57
DktrKranz2(I'm not an archive-admin, this is just my opinion)15:58
jdongCrippledCanary: both should be relevant to Debian, but what's clear to me is 0.1 should NOT go in without 0.2's fixes15:59
jdongas currently 0.1 alone would break upgrades15:59
CrippledCanaryjdong: just doing a version bump to -1 would actually trigger the bug... the 0.1 fix isn't the source15:59
CrippledCanaryjdong: but agree... both should be fixed16:00
jdongCrippledCanary: it isn't the source but it does show up at that point16:02
CrippledCanaryjdong: yes and prolly upgrade from 7.10 to 8.04 to16:03
jdongindeed16:03
=== x-spec-t is now known as Spec
CrippledCanarywhat does "db_get" do in a postinst?16:06
lagaCrippledCanary: it gets a value from debconf16:06
lagaCrippledCanary: man debconf or man debconf-devel16:07
lagafor the latter, you probably also need the debconf-docs package16:07
CrippledCanarylaga: shit, then I have to learn that to :)16:07
lagadebconf-doc*16:07
lagaCrippledCanary: debconf is great :)16:07
CrippledCanarylaga: the debian/config is the file that controls debconf, right?16:14
=== x-spec-t is now known as Spec
* ScottK encourages the hamsters for the PPA buildd to peddle faster.16:40
cprovlol16:41
persiahttp://xkcd.com/413/16:43
Hobbseeyay, hamsters!16:43
=== x-spec-t is now known as Spec
YokoZarIf a stable release update only affects a specific arch, will a later package version only be released for that arch?17:15
YokoZarI'm thinking of https://bugs.edge.launchpad.net/ubuntu/+source/wine/+bug/224042  -- the 32 bit package should be identical to how it was before17:16
ubot5Launchpad bug 224042 in wine "Wine 64 bit does not depend on lib32nss-mdns package; dns lookups broken" [Medium,Confirmed]17:16
=== x-spec-t is now known as SPec
=== SPec is now known as Spec
sistpoty|workYokoZar: it will always get rebuilt for all arches, so it may not be bit-identical17:16
YokoZarsistpoty|work: That's what I figured, I'm just sort of wondering if that needs to be the case17:17
sistpoty|workYokoZar: for ubuntu it needs to be like that, as there's no way to say you want only one arch rebuilt17:17
sistpoty|work(and if there are source changes, you'd always need to rebuild all arches, otherwise source wouldn't match the binary)17:18
persiaCan't one give-back a specific arch manually?17:21
persiaOr does that only work when it previously FTBFS?17:21
LaserJockYokoZar: ping17:22
YokoZarLaserJock: pong17:23
LaserJockYokoZar: did you get MOTU SRU approval for bug #224042?17:23
ubot5Launchpad bug 224042 in wine "Wine 64 bit does not depend on lib32nss-mdns package; dns lookups broken" [Medium,Confirmed] https://launchpad.net/bugs/22404217:23
YokoZarLaserJock: still waiting on it17:23
LaserJockYokoZar: but it's already been uploaded to proposed?17:24
YokoZarLaserJock: have I done something really wrong?  I just followed the instructions on the wiki page: https://wiki.ubuntu.com/StableReleaseUpdates17:25
LaserJockYokoZar: you aren't supposed to upload it until it's been approved17:25
LaserJockso it's already going through without any MOTU SRU member looking at it17:25
LaserJockYokoZar: so please do wait until MOTU SRU has ack'd it before uploading :-)17:27
sistpoty|workpersia: once it's published, you cannot give-back s.th. (otherwise we wouldn't need to upload packages for rebuilds)17:27
YokoZarLaserJock: :(  I thought uploading to -proposed was how the SRU team looked at the new version of the package.  There's nothing between step 3 and 4 that says to wait for approval, so I naturally thought that came in the -proposed to -updates transition17:28
LaserJockYokoZar: yeah, we should probably make that clearer :-)17:30
LaserJockgotta run, bbl maybe17:30
persiasistpoty|work: Ah.  It's the publish run.  Thanks for the clarification.17:30
sistpoty|workpersia: I'm not too sure, if it's the publisher run actually (as I don't know lp internals that much)17:30
sistpoty|workmaybe wgrant would know the details though?17:31
persiasistpoty|work: Well, right.  In simple terms, the issue is likely that one can't update a binary package to the same version number.17:31
DktrKranz2YokoZar: SRU page is not clear that way, it doesn'tsay developers needs to wait for an ACK before uploading to proposed17:32
sistpoty|workpersia: yes (which does make some sense... otherwise apt wouldn't draw in the "new" packages... and it sounds awful to me to change s.th. which is already released at a version)17:32
persiasistpoty|work: Oh, I agree it'd be ugly.  Be nice if Soyuz grew a function to do binNMU's at the click of a button (for appropriately authorised people: e.g. those who can upload there)17:37
sistpoty|workpersia: hm, yes, that'd be nice indeed :)17:38
sebnerpersia: you still think new contributors group is open tomorrow? ^^17:38
persiasebner: I've had no information on the matter since it was last discussed.17:39
sebnergrml17:39
sebnerkk. thx anyway17:39
* sistpoty|work heads home now... cya17:40
sebnersistpoty|work: hf17:40
=== x-spec-t is now known as Spec
ScottKAny doubts I had about not jumping straight to clamav 0.93 before we released are resolved.17:53
ScottKEvery single package that build-dep's on libclamav-dev FTBFS against 0.93.17:53
jcastronxvl: ready for your session in ~1 hour?18:00
=== slangase` is now known as slangasek
nxvljcastro: always ready18:13
nxvl:D18:13
nxvljcastro: i'm just working on the last details18:15
ScottKI'd love it if someone would look at the serpentine crashes that are coming in and come up with an SRU to make the bugmail stop.18:46
ScottKTheMuso: Dunno if it's something you're interested in or not, but I see some kind of accessibility issue in the last comment for Bug 22047519:02
ubot5Launchpad bug 220475 in virtkey "Onboard segfaults on Ubuntu Hardy" [High,New] https://launchpad.net/bugs/22047519:02
=== fta_ is now known as fta
cyberixDo you agree with this guy that this is not a bug? https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/22199519:46
ubot5Launchpad bug 221995 in rhythmbox "Last.fm plug-in fails to communicate current song to lyrics plug-in and cover art plug-in" [Wishlist,New]19:46
macoi dont want to ask this in -devel because its not really related to devel, though theyre probably the ones that could answer best... if im writing a script to download the current source package for the kernel and make a modification that fixes a bug and recompile it, do i need to include for it to compile l-r-m?  The bugfix isn't in a spot related to any restricted modules, but will the fact that its even slightly different have an effect?19:54
CrippledCanarydoes anyone here know where debconf information is stored? i want to make sure they are gone for a package i'm debugging20:04
crimsunCrippledCanary: /var/cache/debconf/*.dat20:09
CrippledCanarycrimsun: thanks20:09
CrippledCanarycrimsun: is there any tools for cleaning that up20:12
crimsunCrippledCanary: I need more info to answer your question adequately.20:19
crimsunCrippledCanary: e.g., are you attempting to edit /var/cache/debconf/config.dat by hand, or are you attempting to clean it programatically using a package's postrm?20:20
CrippledCanarycrimsun: by hand...20:21
=== santiago-php is now known as santiago-ve
CrippledCanarycleaning up20:22
CrippledCanaryi'm working on a SRU here... don't want to change more then necessary so changing postrm is not on the schedule :)20:22
crimsunCrippledCanary: ok, I'm lacking context for the SRU.  Which is it?20:23
crimsunmaco: to address your question from 2:54, please see the ABI checking portion of debian/rules20:27
CrippledCanaryits bug #224241 which should be combined with bug #224241 to make it through -proposed20:30
ubot5Launchpad bug 224241 in smstools "smstools stop working after upgrade" [Undecided,New] https://launchpad.net/bugs/22424120:30
crimsunerr20:30
CrippledCanarysorry bug 22197320:31
ubot5CrippledCanary: Error: Could not parse data returned by Launchpad: The read operation timed out20:31
CrippledCanarythe bug #221973 made a upgrade bug visible that is addressed in 22424120:31
ubot5Launchpad bug 221973 in smstools "smstools folder under /var/run isn't recreated after reboot" [Undecided,Confirmed] https://launchpad.net/bugs/22197320:31
CrippledCanaryi just attached a debdiff to 224241 and subscribed it to motu-sru20:33
macocrimsun: in l-r-m or the kernel one?20:34
crimsunmaco: linux.20:36
macocrimsun: actually, how do i change the abi number? i do want to change it because if i leave it the same, update manager tries to "upgrade" from the new, edited one to the old one20:37
crimsunmaco: no, you don't want to bump the ABI unnecessarily.  You want to adjust the version number in debian/changelog.20:38
macocrimsun: oh. ok...20:38
macocrimsun: since it's 16.30, should i make it 16.30.1? im afraid putting .31 would mean that when the next kernel update comes out itll be .31 and i dont know how it would react to that20:39
crimsunmaco: I would use 2.6.24-16.30+foo20:41
macook20:42
crimsunthat sorts before the unextremely unlikely 2.6.24-16.30.1 and thus trivially before 2.6.24-16.31, which is far more likely20:42
crimsunugh20:42
crimsunextremely^20:42
macook20:42
macobut it comes after jut plain 16.30?20:43
crimsunyes20:43
macook20:43
macois there a list of what +, -, and ~ (anything else?) do in sorting?20:43
crimsunyeah, in Debian Policy20:43
macook20:43
crimsun(http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version)20:44
crimsunyou can check these by dpkg --compare-versions and checking the exit value20:45
crimsunor use &&, etc., etc.20:45
macook20:45
crimsunCrippledCanary: ok, a few comments on the 0.2 debdiff20:47
crimsunCrippledCanary: first, the distro should be hardy-proposed.  Second, do you really want to include the commented-out debugging echo?20:48
CrippledCanarycrimsun: will fix both those things... in a few min20:49
CrippledCanarycrimsun: a new debdiff is attached20:58
macocrimsun: ok so if i just change the version number and i leave the ABI number alone, l-r-m doesn't need to be recompiled, right?20:58
crimsunmaco: if the ABI in fact does not change, correct.20:59
crimsunCrippledCanary: ok, ~motu-sru will process it.20:59
macocrimsun: it's this: http://tinyurl.com/5vm3ul  i dont think that changes the ABI20:59
macoi could be totally wrong, of course21:00
CrippledCanarycrimsun: great, thanks for your attention21:00
crimsunmaco: you're correct; it does not.  Have you filed a bug against linux?21:01
crimsunthat's a trivial fix.21:01
macocrimsun: there's a bug filed, targetted at 8.04.121:01
crimsungood.21:01
macoi just figure someone might want 3D in the meantime21:01
=== cprov is now known as cprov-afk
rulusHi, I'm using a combination of distutils, pycentral and cdbs to create a package from my Python program. Now, how do I split it up in multiple binary packages? Is there any documentation available in this regard?21:09
elmargolsomeone knows a tool to se what parts of an application uses most of the memory?21:12
crimsunrulus: dh_install(1)21:16
ruluscrimsun: thanks :)21:19
crimsunrulus: for an example, see quodlibet source.21:19
ruluswill do, thanks again21:21
=== never|mobi is now known as neversfelde|mobi
=== ubot5 is now known as ubottu
Kopfgeldjaegercan i convert a dpatch to a normal patch?22:39
lagait's a normal patch. patch should strip the leading "garbage"22:39
Kopfgeldjaegerok, thanks22:40
=== wolfger_ is now known as wolfger
Kopfgeldjaeger16 hunks FAILED. super, that means i may go through a 500 lines patch by hand22:50
Flare183ouch22:52
TheMusoScottK: I am aware of that issue, and will be preparing an SRU for that today.23:34
TheMusoI filed that bug FWIW.23:34
=== ember_ is now known as ember
ScottKTheMuso: OK.  I just saw it in bugmail and it seemed up your alley.  I guess so.23:53
milliScottK: Are there DVDs built?23:57
milliI'm at Interop this week and I'm seeding all the CD torrents ...23:57
ScottKYes.23:58
ScottKThey were built before release.23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!