/srv/irclogs.ubuntu.com/2010/09/16/#ubuntu-devel.txt

SpamapSIts only going to affect people who have built against 0.8.2, and use the error enums, and then move their app directly to maverick without recompiling.00:00
mathiazSpamapS: if they recompile on maverick it wouldn't be broken?00:00
SpamapSnope00:00
SpamapSIt will be fine because maverick has 0.8.300:01
mathiazSpamapS: so IOW the only broken use case is: a 3rd party app built on lucid wouldn't work on maverick?00:01
SpamapSWhat won't be fine is if there's somebody mixing debian/backports.org/ubuntu packages and they end up depending on libdbi0 from squid (0.8.2) and then try to use it on ubuntu.00:01
SpamapSs/squid/squeeze/00:01
SpamapSright, app from lucid that uses the error enums will break on maverick00:02
SpamapSor likewise, an app compiled on maverick that uses the enum will break on lucid00:02
SpamapSits just a confusing situation00:03
SpamapSThe fear I have is that the breakage will be *really* subtle00:03
mathiazSpamapS: right - so I lean towards not updating the libdbi package in maverick and add a release note00:03
SpamapSits not a missing symbol, its a missing constant value.00:04
SpamapSso like, your app from maverick goes  if error == XYZ ...   you'll never match that value if you install the package on lucid00:04
mathiazSpamapS: ok - let's explore the other solution.00:05
mathiazSpamapS: all the packages required to be rebuilt are ready?00:05
mathiazSpamapS: how did you rebuilt them?00:05
SpamapSppa00:05
SpamapSran test suites where available too00:05
mathiazSpamapS: ready == the source has been modify to use libdbi-dev instead of libdbi0-dev?00:05
SpamapSyeah00:05
SpamapSI held off pushing for merge proposals until we decided what to do in maverick.00:06
mathiazSpamapS: do you have the PPA url?00:06
SpamapShrm.. I must have deleted the packages.. it was in https://edge.launchpad.net/~clint-fewbar/+archive/fixes/+packages00:07
SpamapSrrdtool is still there though00:07
SpamapSmathiaz: I wasn't very scientific about it I guess. ;)00:08
mathiazSpamapS: do you still have the source packages somewhere?00:08
mathiazSpamapS: IIRC it's possible to copy src package from PPA to the primary ubuntu archive00:09
SpamapSmathiaz: what about having a new source package called libdbi084 that adds libdbi-dev to the archive...00:09
mathiazSpamapS: hm - that's too complicated00:09
mathiazSpamapS: if you still have all the source packages, I could sponsor them easily00:09
SpamapSmathiaz: I always tack on ~ppa so that wouldn't work. but let me find the dir with all of them00:10
SpamapSmathiaz: only rrdtool is in main00:10
mathiazSpamapS: given that you've already tried to the rebuild and tested them in the PPA that's a good thing00:10
SpamapSthough libdbi-drivers is supposed to be in main too and hasn't seeded yet00:10
mathiazSpamapS: has the MIR been approved?00:10
SpamapSmathiaz: long ago.. just never seeded00:11
mathiazSpamapS: ok - I can do that too - is there a bzr branch to sponsor somewhere?00:11
SpamapSmathiaz: its not Depended or Recommended by any main packages.. sort of a weird seed because libdbi is useless without them.00:11
SpamapSwhy yes there is..00:11
SpamapShttps://code.edge.launchpad.net/~clint-fewbar/ubuntu-seeds/platform.maverick-add-libdbi-drivers00:12
SpamapSI can propose for merging if need be00:12
mathiazSpamapS: I'll merge your branch00:13
SpamapSmathiaz: if you look, there are already some branches linked to the bug report for the dependent packages00:18
SpamapSmathiaz: crap.. I'm at starbucks and they seem to be blocking port 21. weird.00:25
mathiazSpamapS: so my proposal is to leave things as it is for maverick on libdbi00:25
mathiazSpamapS: and may be a release note00:26
mathiazSpamapS: I'm merging the libdbi-driver seed change00:26
SpamapSmathiaz: I think thats 100% reasonable00:26
SpamapSmathiaz: I think a release note in the "known issues" is definitely a good idea.00:26
SpamapSmathiaz: lets leave it at that. Do I need to contact somebody about the release note?00:27
mathiazSpamapS: I'll open a task against the release-note project00:28
mathiazSpamapS: I'd suggest to update the description of the bug with a section outlining the release note to be added00:28
psusifinal freeze is in effect isn't it?00:28
mathiazSpamapS: once the release notes are being prepared the release manager will just need to copy'n paste the note for the bug00:28
SpamapSsoon00:28
* psusi hopes he can get this fix applied in time so mav doesn't ship with broken dmraid support00:30
SpamapSmathiaz: ok, I'm satisfied that we've exhausted all avenues. ;)00:31
SpamapSmathiaz: and actually I prefer this route, as it means we can just pursue this in Debian directly and get rid of any delta.00:31
* mathiaz nods00:31
mathiazSpamapS: we should revisit that for natyy00:32
mathiazSpamapS: natty00:32
mathiazSpamapS: given that squeeze is frozen it may take some time until Debian is released00:32
mathiazSpamapS: so if it's really important we may wanna schedule to do it in natty00:32
mathiazSpamapS: doing the work in Debian is also a very good option - there is not guarantee that it will be done in time for natty though00:33
SpamapSmathiaz: *ugh*00:33
TheMusopsusi: Let me know if you need a sponsor.00:34
SpamapSWe can at least get it into experimental00:34
SpamapSso the devs can just bump those packages to unstable whenever they're comfortable.00:34
mathiazSpamapS: right - that's a good option.00:35
SpamapSmathiaz: thanks for working through it with me. I'm sure we'll get it right for natty. :)  Should we remove the server-mrs tag?00:35
mathiazSpamapS: I'm doing something similar with the puppet package00:35
mathiazSpamapS: where the version in maverick is the actually the one from experimental00:36
psusiTheMuso, actually I was noticing you do work on... wait, I might be thinking dmraid?  grub needs a patch to fix its brokeness for dmraid that developed during mav cycle... finished building now with debian's patch, going to boot live usb, install new package, and test installing now00:36
mathiazSpamapS: yes - I've also opened a task against the ubuntu-release-notes project00:36
SpamapSmathiaz: I think when debian is in freeze, thats going to be a common thing.00:36
TheMusopsusi: ok00:36
JanCpsusi: is that related to the naming of dmraid devices?00:37
psusiTheMuso, but so far, looks like grub-pc is returning the correct results... and this patch also fixes those ANNOYING memory leak warnings ;)00:37
psusiJanC, yes...00:37
psusiit was looking for a device name containing mapper/ but the name gets canonicalized to dm-x00:38
TheMusolovely00:38
psusigoing to go test a new clean install using it now... bbiab00:38
mathiazSpamapS: https://code.edge.launchpad.net/~clint-fewbar/ubuntu-seeds/platform.maverick-add-libdbi-drivers00:39
mathiazSpamapS: ^^ I've merged the diff00:39
mathiazSpamapS: so you can update your branch accordingly.00:39
SpamapSmathiaz: :-D cool00:40
SpamapSmathiaz: I've been trying to keep all my branches marked accurately... they stack up quick. ;)00:40
mathiazSpamapS: yop - OTOH that gives you a lot of LP karma :)00:41
SpamapSmathiaz: I should throw a party when I get to 10,00000:42
SpamapSOK I have to run..00:43
SpamapSmathiaz: thanks again, ttyl!00:43
mathiazSpamapS: sure!00:43
psusidamn.... grub-install works fine now, but for some reason ubiquity says it fails.... updating daily iso and retrying01:12
psusiit also says it is running it on /dev/sda the first time despite the fact that I told it to use the raid01:12
TheMusoYay dmraid. I am glad I don't deal with that garbage any more. :p01:15
psusiheh, I'm using lvm to hold various install volumes that are split and I sometimes migrate across the dmraid disks, the ssd, and the 1.5 tb monster drive now ;)01:16
psusibtw, has anyone figured out how to deal with the very annoying massive slow down of dpkg due to ext4 being retarded issue yet?01:21
TheMusoProbably, I haven't investigated personally.01:22
psusialright, it works... once I installed the updated grub package both on the livecd and on the target during the install01:45
psusithough ubiquity still claims it is installing grub to sda when it isn't01:45
TheMusointeresting.01:51
psusiso... what do I need to do now to get bug #634840 sponsored? ;)01:52
ubottuLaunchpad bug 634840 in grub2 (Ubuntu) "grub does not detect partitions properly on DMRAID" [Critical,In progress] https://launchpad.net/bugs/63484001:52
TheMusoAh if the bug is in grub2, then I feel a little less comfortable in touching the grub2 packaging...01:53
psusik... I'll have to poke cjwatson then01:53
TheMusoI also dare say that that will be able to get in post freeze.01:53
psusido I need to do anything with the bug report?  like assign it to him?  or subscribe the release team or anything?01:53
TheMusoEven going by the one line description.01:54
TheMusoI'd have to read the docs to be sure, so no idea sorry.01:54
* TheMuso has done it before in previous releases, but can't remember.01:54
TheMusoProbably a procedure similar to feature freeze exceptions.01:54
psusithat bloody memory leak message has been in there since lucid was released hasn't it?  bloody annoying thing... nice that this patch fixes that too01:55
psusihrm... what now?  ureadahead?  e2defrag?  hrm...01:56
psusicjwatson, when you wake up, take a look at bug #634840.  Patch attached from debian, tested well for me, fixes dmraid issue, as well as the annoying memory leak that has been there since lucid02:08
ubottuLaunchpad bug 634840 in grub2 (Ubuntu) "grub does not detect partitions properly on DMRAID" [Critical,In progress] https://launchpad.net/bugs/63484002:08
=== bjf is now known as bjf[afk]
TheMusos/c02:52
josh_This room is out of hand.04:05
=== rgreening_ is now known as rgreening
crimsun_TheMuso: are you also merging in the latest stable-queue bits from pulse for upload?05:05
TheMusocrimsun_: took care of them yesterday when I uploaded pulse.05:05
crimsun_TheMuso: great!  thanks05:05
TheMusonp05:05
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
WubbbiHey guys. I found a strange bug. I use a netbook with broadcom Wifi and it realy works good. But now the problem. When I'm in Batterie mode ( even if the batterie is very very full ) my Wifi speed is like 3,4kb/s ... it takes 5 minutes to load google.com. In Lucid I dont have any problems. Well when I put in my Charger, the Wifi connection speeds up to normal speed. I dont have to reboot, no reconnect. I just put it in and its fast as07:56
Wubbbinormal. When I put it out again, the connection slows down. Can you guys take a look on it? I even can give you more information!07:56
pittiGood morning08:04
tkamppeterpitti, morning.08:28
smbpitti, Morning. I hate to ask but could we at least move the kernel stuff in Karmic-proposed into updates, even though the four reports also got no verification after 21 days?08:29
pittihello tkamppeter08:29
pittismb: hm, I'd like to see at least one report that it actually works08:29
smb*sigh* yeah08:30
* smb hates those lazy buggers08:30
tkamppeterpitti, I got everything into Maverick except the auto-download for the Epson drivers, but there it seems that I have to tell Epson that I asked the Ubuntu developers for including it but there was not enough man power to implement it.08:31
=== tankdriver is now known as tankdriver_
pittitkamppeter: right, unfortunately :/08:33
=== tankdriver_ is now known as tankdriver
pittitkamppeter: after next UDS I'll be back and can spend some time on that08:33
tkamppeterpitti, should we leave it as a bug report/feature request or should I create a blueprint/UDS session with apt and seurity people invited?08:34
pittitkamppeter: from my POV the bug is fine; I don't think there's need for further discussion, it's a SMOP now08:35
tkamppeterSMOP?08:35
pittibut if you prefer a blueprint for tracking, that's fine08:35
pittitkamppeter: "simple matter of programming"08:35
tkamppeterpitti, OK. So no blueprint.08:35
tkamppeterpitti, I think so, too. We have done all agreements with our security people, the LF, and the manufacturers, and the server side is completely implemented.08:36
tkamppeterTpitti, the thing was only that I do not have the knowledge to implement the client side and the person(s) with the knowledge did not have the time.08:37
tkamppeters/Tpitti/pitt/ ^^08:38
tkamppeterpitti, I was so much behind this Epson thingy because Epson people were pressurizing, and I also wanted to turn a project into live I worked a longer time on, and I hoped by showing off the Epson auto-download in Maverick, the other manufacturers and also the other distros will quickly follow.08:40
pittimvo: can you please upload the fix for bug 633967 to maverick ASAP? this blocks the lucid SRU08:40
ubottuLaunchpad bug 633967 in apt (Ubuntu Maverick) "apt-ftparchive generates corrupt Sources stanzas for .dsc files without Checksums-* fields" [Critical,In progress] https://launchpad.net/bugs/63396708:40
pittitkamppeter: don't worry, the next Ubuntu release will come :)08:41
pittikirkland: can you please upload the fix for bug 590929  to maverick, so that the lucid SRU can go to -updates?08:42
ubottuLaunchpad bug 590929 in eucalyptus (Ubuntu) "[SRU] eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT configs)" [Medium,Confirmed] https://launchpad.net/bugs/59092908:42
tkamppeterpitti, at least I could cater for Ricoh: PPD selection sensitive to presence of PostScript add-on installed in printer and much faster PPD search and package download/installation.08:43
mvopitti: hm, that should be in already, let me check08:48
mvopitti: not sure why the bug was not auto-closed08:50
pittimvo: LP doesn't currently auto-close bugs08:50
pittiif it was fixed only recently08:50
mvopitti: aha, ok. thanks08:57
smbpitti, did you reject the hardy upload because of the events from yesterday or another reason. iow, should I bother to prepare it to re-upload later on?08:58
pittismb: I thought we agreed to wrap this into another update, but that uploading it by its own isn't worth it? also, I thought it's superseded by the security update now anyway08:58
smbpitti, second is true. first maybe we did miss each other. I'd rather do that on its own on hardy as there are not really much normal things coming along there.09:00
pittismb: so just commit it, and we'll wait with the upload until something more urgent pops up?09:01
smbpitti, That might be never. Because urgent things will likely be security and those wont take that. And then I end up pushing around a commit for the remaining lifetime of hardy and that is just a waste of effort.09:03
pittismb: then my gut feeling is to just forget about it; if it hasn't hurt anyone in over two years, then it's not a biggie now09:03
smbpitti, Alright then. I rather not bother about that then09:08
=== spike_ is now known as spikeWRK
=== hanska is now known as dapal
pittiYokoZar: hey, how are you?10:15
pittiYokoZar: question for you in bug 60650910:15
ubottuLaunchpad bug 606509 in wine1.2 (Ubuntu Lucid) "Wine 1.2 Stable is released" [Undecided,Fix committed] https://launchpad.net/bugs/60650910:15
YokoZarpitti: heya10:15
pittismb: is the linux-mvl-dove upload (lucid) still current, with yesterday's security update?10:19
smbpitti, It basically is all moot atm10:20
pittismb: ok, rejecting then10:20
smback10:20
YokoZarpitti: per my comment on 606509 I'll get to work on a new gnome-exe-thumbnailer for Lucid10:23
pittiYokoZar: in other words, you want to overwrite the current SRU and not publish it?10:24
YokoZarpitti: no, hold it for now10:25
pittiack10:25
YokoZarpitti: and I'll upload a new gnome-exe-thumbnailer and we release them together10:25
YokoZarpitti: then the minor bugfix can follow10:25
pittiYokoZar: no, I think we misunderstand10:25
pittiYokoZar: I'll hold the current upload in the unapproved queue10:25
pittiYokoZar: but I meant the pacakge which is already in lucid-proposed and got some testing10:26
pittii. e.  1.2-0ubuntu1~lucid310:26
YokoZarYes hold off on moving that to -updates10:26
pittiok10:26
YokoZarwait for it to go to -updates at the same time as a new gnome-exe-thumbnailer that isn't ugly10:26
YokoZarthe reason is if they install the old one it'll cache some ugly thumbnails that won't change10:26
pittiok; but then I'd still prefer ~lucid4 to be on top of ~lucid3, i. e. get its own changelog10:29
pittiso that we don't invalidate all the testing that went into ~lucid310:29
vishcould someone upload this for maverick? lp:human-theme fixes a small bug Bug #553393 ..10:35
ubottuLaunchpad bug 553393 in human-theme (Ubuntu) "Checkboxes and radiobuttons almost invisible using Human themes" [Low,Triaged] https://launchpad.net/bugs/55339310:35
vishobviously someone still uses human theme ;p  .. they came to -artwork asking for a fix ;)10:35
vishhuman theme is still in main.. maybe it should be moved to universe?10:36
=== amitk is now known as amitk-afk
jibelpitti, I think that you can publish gzip from lucid-proposed to -updates. It was verified 4 weeks ago but the list of pending SRUs fails to report the status.10:47
jibelpitti, bug 52436610:48
pittijibel: ah, the syntax is wrong in https://edge.launchpad.net/ubuntu/lucid/+source/gzip/1.3.12-9ubuntu1.110:48
ubottuLaunchpad bug 524366 in gzip (Ubuntu Lucid) "Regression: CRC error an i386" [Undecided,Fix committed] https://launchpad.net/bugs/52436610:48
pittijibel: thanks10:48
cndpitti, do you know where didrocks or seb128 are?11:08
pitticnd: no, I don't; I think didrocks mentioned something about holidays until Friday11:09
cndok11:09
mvoseb is on vacation as well11:10
cndmvo, thanks11:11
=== diwic is now known as diwic_lunch
=== smb is now known as smb-lunch
=== amitk-afk is now known as amitk
=== ivoks-afk is now known as ivoks
=== MacSlow is now known as MacSlow|lunch
ograhmm, so whats up with samba today12:15
pittil12:40
=== smb-lunch is now known as smb
=== MacSlow|lunch is now known as MacSlow
=== ivoks is now known as ivoks-afk
=== rgreening_ is now known as rgreening
=== diwic_lunch is now known as diwic
cndpitti, would adding an apport hook require an FFE?13:40
shadeslayerjcastro: thanks for the sponsorship... thanks to canonical as well :D13:45
shadeslayercould you tell me who else is coming from the Kubuntu team btw?13:45
=== njpatel_ is now known as njpatel
pitticnd: no, those are fine13:59
cndpitti, ok, thanks!14:00
=== bjf[afk] is now known as bjf
jjohansencjwatson: is it you I bug about a grub2 issue?14:04
cjwatsonyes14:04
jjohansencjwatson: okay, I have a multipath bug I am looking at but grub-probe is failing with error no mapping exists for X-part114:05
jjohansenwhere X is the multipath14:05
jjohansenthat exists in /dev/mapper/14:06
cjwatsonrun it with -vvv and send me the output, together with ls -l of the relevant device nodes and the contents of /boot/grub/device.map (if any)14:06
jjohansencjwatson: okay, thanks14:06
ogracan a buildd admin please bump https://edge.launchpad.net/ubuntu/+source/samba/2:3.5.4~dfsg-1ubuntu6/+build/1962200 and https://edge.launchpad.net/ubuntu/+source/ubiquity/2.3.19/+build/1962841 to very high ?14:07
pittiogra: done14:08
ograthanks14:08
ograpitti, if you want amd64 to build properly again i'd suggest doing that for samba on amd64 too14:09
pittiogra: it's already built on amd6414:09
ograoh, it was powerpc ... sorry14:09
pittibumped14:10
ograi just heard several people complain about it not being upgradeble this morning ... and amd64 handt built then14:10
ograbah, sigh, why is the armel queue so full14:14
ograpitti, can i get  https://edge.launchpad.net/ubuntu/+source/ubuntuone-client/1.4.1-0ubuntu1/+build/1961868 bumped too ? (last one, promised)14:14
pittiogra: nudged14:15
pittiogra: well, yesterday we had a gazillion "OMGfreeze" uploads :)14:15
ograpitti, yes, me too and i'd love to test them to find remaining bugs :=14:16
ogra:)14:16
ograbut that requires an image14:16
* ogra would like to have separate buildds for proposed/security on arm ... 14:17
=== jjohansen is now known as jj-afk
chrisccoulsonpitti - well, i had to do a few OMGregression uploads yesterday ;)14:23
chrisccoulsonthat happened to coincide with all the OMGfreeze uploads14:23
psusicjwatson: hey there, did you get my message from last night?14:48
cjwatsonpsusi: yes, I followed up to the bug, it's on my to-do list now.  I want to get it upstream14:49
cjwatsonpsusi: upstream's code freeze for 1.99 is in a few days and it would be good to get this sorted out there14:49
cjwatsonpsusi: but I want to spend a bit of time thinking about it and reconciling it with other patches people have sent to achieve similar goals, rather than going straight ahead with it14:49
psusicool... but either way it's going to make it in maverick?14:49
cjwatsonyes14:49
cjwatsonI certainly don't want to release with broken dmraid support, as that's a recipe for lots of confusing bugs14:50
psusiahh, ok... I had actually debugged the problem to that same area of code myself before I found that patch from debian... looked good to me and tested well14:50
psusiindeed14:50
cjwatsonwell, just to be clear, it's a bug report from a Debian contributor rather than a patch that's been applied to Debian14:51
cjwatsonI'd want to fix it in Debian too14:51
psusiahh14:51
mvoogra: what was that samba issue you taked about earlier? hang in configure?14:55
ogramvo, arch any vs arch all and full build queue14:56
ogramvo, since arch all is built on x86 thats usually ahead so we get uninstallability14:57
mvoogra: aha, ok. there is another samba releated issue that I was wondering about14:58
ograah, no, it was only installability issues during image build due to the above14:58
ograStevenK, still awake ?15:09
kirklandpitti: fix is already in maverick15:12
kirklandpitti: i updated the bug status, but its noted in the sru justification15:13
pittikirkland: ah, thanks15:13
ograal-maisan, hey, mind letting linux-ti-omap4 our of NEW ?15:20
al-maisanogasawara: sure, please give me a 10 minutes or so.15:20
al-maisanI am just finishing something up..15:21
cjwatsonI can do it if you like15:21
al-maisancjohnston: that would be great15:21
cjwatsonthough I see it's al-maisan's archive day15:21
cjwatsonbut anyway :)15:21
al-maisanif you don't get to it, I will do so in 10 minutes.15:21
ograal-maisan, lol, you messed up all tab completion that was possible the the last lines :)15:22
al-maisanouch :)15:22
al-maisancjohnston: sorry15:22
al-maisan.. and, also sorry to ogasawara :)15:22
ograshe is used to it ... i'll claim back stolen pings in beer at uds :)15:23
cjwatsonogra,al-maisan: done15:24
cjwatsonI think cjohnston must be used to it by now as well15:24
al-maisanthank you!15:24
ograTA15:24
mathiazcr3: o/15:55
mathiazcr3: re checkbox 0.10.3 - I forgot to update the branch before I uploaded the package15:56
mathiazcr3: could you prepare a 0.10.4 with the correct po file?15:56
cr3mathiaz: if this could wait until monday, I could do even better and fix a bug that's been affecting the translators team15:58
mathiazcr3: well - final freeze is in less than 2 hours15:58
mathiazcr3: is it release critical?15:58
=== dendro-afk is now known as dendrobates
cr3mathiaz: I think it would qualify as release critical, let me ask dpm16:02
cr3dpm: hey dude, do you think the bug in Checkbox affecting translations of questions to be release critical?16:02
mathiazcr3: I'd ask the release manager as well16:02
hallynttx: proposed a fix for bug 488285.  probably too late, but...16:03
ubottuLaunchpad bug 488285 in multipath-tools (Ubuntu) "multipathd segfault" [Low,Confirmed] https://launchpad.net/bugs/48828516:03
mathiazcr3: the release team is making the final call16:03
cr3skaet: would you consider this bug release critical and be acceptable for an exception if fixed next week: https://bugs.edge.launchpad.net/ubuntu/+source/checkbox/+bug/51440116:04
ubottuLaunchpad bug 514401 in Ubuntu Translations "Translations are not loaded for the test descriptions in Checkbox" [High,Triaged]16:04
dpmcr3, mathiaz, perhaps you guys can bring it up tomorrow in the release team meeting. For me personally, it would be important that checkbox could be used in any language16:04
cr3dpm: agreed16:06
mathiazcr3: IIUC the most important bug has been fixed in 0.10.3?16:06
cr3mathiaz: yes16:06
mathiazcr3: the remaining part is an updated po file that wouldn't be used for now unless another bug is fixed?16:07
cr3mathiaz: yes, so lets wait until we get a verdict tomorrow16:07
skaetcr3,  lets discuss tomorrow.16:07
mathiazcr3: ok.16:08
=== ivoks-afk is now known as ivoks
cr3skaet, mathiaz: thanks folks!16:09
mathiazttx: so re samba bug - new bugs are still pouring in16:12
mathiazttx: should the package be blocked?16:12
ttxmathiaz: not sure, it's a development release after all -- ask the release team, I'm on a call right now16:13
mathiazskaet: robbiew: cjwatson: slangasek: bug 639768 - samba fails to upgrade on maverick16:14
ubottuLaunchpad bug 639768 in samba (Ubuntu Maverick) "Samba process gets hung on maverick update" [High,Triaged] https://launchpad.net/bugs/63976816:14
mathiazbugs are pouring in LP - is it worth blocking the package on the mirrors?16:15
cjwatsonI don't like doing that in development releases - can we just get it fixed ASAP?16:15
mathiazcjwatson: I've started the investigation16:16
mathiazcjwatson: in the mean time we can just mark the bugs duplicated16:16
robbiewmathiaz: yeah...I hit that last night16:16
robbiewI just killed the upload, dpkg --configure -a, and did another dist-upgrade16:17
robbiewit doesn't lock up the system or anything16:17
mathiazrobbiew: hm16:17
mvoit seems like ists enough to kill the "start smbd" process16:17
mvoI helped some people with that problem last night and today16:17
mathiazrobbiew: I've uploaded a new version of samba - but I don't see how it could produce that16:18
mathiazmvo: right - so start smbd is blocking16:18
mathiazrobbiew: was your network down?16:18
robbiewnope16:19
robbiewI don't even use samba16:19
mathiazlooking at the smbd upstart job: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/samba/maverick/annotate/head%3A/debian/samba.smbd.upstart16:19
mathiazline 4: start on local-filesystems16:20
mathiazwould this be the reason why start smbd blocks on package upgrade?16:20
sorenmathiaz: I'd say no. that just specifies what will /automatically/ start samba. On upgrades, it would get explicitly restarted.16:21
mathiazrobbiew: do you have logs in /var/log/samba/ ?16:22
mathiazrobbiew: something like log.smbd?16:22
mathiazrobbiew: it may give a clue why "start smbd" was blocked16:22
robbiewlet me check16:22
sorenmathiaz: Do we know that that is what is blocked?16:23
mathiazsoren: I think so - see mvo comment above16:23
soren\O/ it hangs for me on install.16:23
* soren investigates16:23
mathiazsoren: 11:17 < mvo> it seems like ists enough to kill the "start smbd" process16:23
cjwatsonthere was that recent change to cups16:24
robbiewyeah...I think that's related16:24
cjwatsonwhich made it 'start on starting smbd' or similar, I believe16:24
sorenAh, so it's cups, maybe?16:24
cjwatsongrr16:24
robbiewmathiaz: I'll attach my log.smbd file16:24
cjwatsonmisuse of 'and' in a way that's known to break upstart16:25
cjwatson++start on ((starting smbd or filesystem)16:25
cjwatson++          and started dbus16:25
cjwatson++          and stopped udevtrigger)16:25
robbiewhas CUPS related errors16:25
cjwatsonthat means that when 'starting smbd' arrived, it will wait for dbus to start and udevtrigger to stop (since those edge events have long since come and gone at system boot)16:25
cjwatsonpitti: ^-16:25
cjwatsonstarted and stopped are *not states*16:25
cjwatsonI thought Keybuk went through this in detail on #ubuntu-devel a couple of days back?16:26
=== diwic is now known as diwic_afk
ogra_cmpcyes together with pitti and till16:26
ogra_cmpcyesterday even i think16:27
cjwatsonit's not obvious to me how to fix this16:27
cjwatsonhttp://irclogs.ubuntu.com/2010/09/14/%23ubuntu-devel.html#t16:2816:29
quadrisprohi guys16:29
cjwatsonin which Keybuk explains exactly why this is broken16:29
cjwatsonpitti: so remember how the consensus on Tuesday seemed to be "ok, it will break if you start or stop smbd manually, but just don't do that" ...16:30
cjwatsonpitti: bit of an upgrade issue there ;-)16:31
pitticjwatson: just got a DSL reconnect, so I guess I missed a bit of the conversation16:31
pitticjwatson: oh, right16:31
pittiyou mean if we upgrade the samba package, it'll wait forever on cups16:31
cjwatsonand indeed it's doing so for lots of people16:32
cjwatsonbug 63976816:32
ubottuLaunchpad bug 639768 in samba (Ubuntu Maverick) "[Maverick] Samba process gets hung on maverick update" [High,Triaged] https://launchpad.net/bugs/63976816:32
pittiurgh, so we better revert this for now, I think16:32
pittiI haven't seen a good solution for "start cups before samba" yet16:33
cjwatsonperhaps we can decouple those two jobs, and instead signal samba somehow when cups is ready for it?16:33
cjwatsonreverting the entire upstartification may be painful16:33
pittithat's the tricky bit -- you can have a system with samba and without cups16:33
cjwatsonthe upgrade rules aren't designed for that16:33
pitticjwatson: oh, I'd keep the upstart job16:33
pitticjwatson: just drop the "on starting smbd"16:33
cjwatsonright16:34
pittithe upstart script works fine, I think we can just as well keep it16:34
pitti(except for that bit, of course)16:34
cjwatsonwell, if you're signalling samba in a way which doesn't involve direct arcs in the upstart job graph, that would be easier16:34
cjwatsonyou know, if you could send SIGHUP to it or something16:34
cjwatsonif it fails, whatever16:34
=== yofel_ is now known as yofel
pittislangasek: ^ is there a way to tell smbd "go redetect the configuration" like this? (SIGHUP etc.)16:35
sorenpitti: As in reread its configuration file?16:36
sorenpitti: Or what exactly changes that samba needs to notice?16:36
slangasekpitti: to go reread smb.conf?  sure, SIGHUP does it16:36
pittisoren: I don't think that's in samba's configuration file; I guess it just asks cups?16:36
mathiazpitti: http://manpages.ubuntu.com/manpages/maverick/en/man8/smbd.8.html16:36
sorenpitti: My problem is that I don't know what "that" is in your question.16:36
mathiazpitti: you can force a reload by sending a SIGHUP to the server.16:37
pittisoren: if only I knew :)16:37
cjwatsonwill SIGHUP be sufficient to get it to notice that cups is now available?16:37
sorenOk, why does CUPS need to wait for Samba?16:37
pittisoren: I was told that we should start cups before smbd, so that smbd can pick up cups' printers and export them to the windows network16:37
slangasekI believe so but would have to test that16:37
sorenAh, I see.16:37
pittisoren: but I don't know whether samba is using libcups or reading /etc/cups/printers.conf, etc.16:37
pittimathiaz: grabbing the bug, FYI16:38
mathiazpitti: ok16:38
ttxok, so this happens to be the first samba update since that problematic cups update, IIUC16:41
mathiazttx: yes16:42
cjwatsonperhaps, after cups is fixed, samba ought to be reuploaded with a Breaks: cups (= thatversion)16:42
ttxmathiaz: unlucky you :)16:42
mathiazttx: well - better now than when the first security update for samba in maverick is published16:43
pittiso I wonder whether I should only drop the "on starting smbd" for now, or add a killall -HUP smbd as well16:43
ttxmathiaz: heh, yes16:43
cjwatsonuse 'status' to find the pid of smbd according to upstart16:44
cjwatson(yes, you have to do a little text parsing)16:44
pitticjwatson: except that there are two smbd processes16:44
pitti$ status smbd16:44
pittismbd start/running, process 121316:44
pittiroot      1213  0.0  0.1  93504  4784 ?        Ss   13:35   0:00 smbd -F16:44
pittiroot      1226  0.0  0.0  93504  1988 ?        S    13:35   0:00 smbd -F16:44
cjwatsonbut at least the format is documented16:44
cjwatsonoh16:44
pitti1226 is a child16:44
cjwatsonwhich one do you need to SIGHUP?16:44
cjwatsonis it sufficient to SIGHUP the top one?16:44
pittialso, I'm not sure whther that'd help at all16:45
pittiThe configuration file, and any files that it includes, are16:45
cjwatsonI'd suggest just dropping 'on starting smbd' for now while we research thiss16:45
pitti       automatically reloaded every minute, if they change. You can force a16:45
cjwatson*this16:45
pitti       reload by sending a SIGHUP to the server.16:45
mathiazpitti: right - I'm not sure either16:45
cjwatsonbut the configuration file is not changed in this case16:45
pittii. e. it doesn't seem necessary nor sufficient16:45
mathiazpitti: I'm not sure smbd would pick up the new printers16:45
cjwatsonthe thing that changes is cups starting, which smbd can't detect16:45
pittiok, let's just drop the dependency for now16:46
mathiazpitti: if you drop the dependency and *restart* smbd in the post-script section of cups?16:47
mathiazpitti: hm - well - that would probably break existing smbd sessions16:47
pittimathiaz: that, and would be rather costly, too16:48
pittilet's figure this out under less pressure; this has been broken for ages, after all16:49
pittiuploaded for now16:51
=== jj-afk is now known as jjohansen
pittia really cheesy workaound might also be to start smbd later? i. e. "start on runlevel [2345]" instead of "start on local-filesystems"?16:55
cjwatsondon't leave it up to chance like that, please16:56
cjwatsonwe'll just get confused later16:57
mathiazpitti: ok - so the starting on smbd has been removed16:58
mathiazpitti: for now smbd will not pick up new printers from cups?16:58
pittimathiaz: right, same situation as since karmic16:58
mathiazpitti: ok16:59
pittitkamppeter: ^ FYI17:00
mathiazpitti: should samba be reuploaded with a breaks as suggested by cjwatson ?17:00
pittimathiaz: I'm not sure under which conditions that would help17:00
pittibut it's certainly not wrong17:01
cjwatsoncome to think of it I can't think of a condition where it would help17:01
cjwatsonI was thinking of upgrades from lucid, but those will just upgrade to the fixed cups17:01
cjwatsonperhaps partial upgrades17:01
cjwatsonah yes17:01
cjwatsonuser has already upgraded cups to the version currently in the archive, before pitti's fix today; there's some attractive bug-fix in samba, so they run 'apt-get install samba'17:02
cjwatsonbang17:02
cjwatsona Breaks would encourage the package manager to upgrade cups as well17:02
mathiazcjwatson: well there was only one upload after the upstartification of cups17:07
cjwatsonyes, but there might be more17:07
cjwatsonpartial upgrades - we can't necessarily assume that users are up to date on all packages in a level way17:07
cjwatsonparticularly during development cycles when one thing or another is often broken, or when people sometimes just change one thing at a time17:08
mathiazcjwatson: gotcha17:09
mathiazcjwatson: so the following line should be added to the debian/control file of the samba package: Breaks: cups (= 1.4.4-4) ?17:09
jelmerpitti, mathiaz: our print dev hasn't gotten back to me yet, but I've looked at the code and its intend at least is that the printers are reloaded on SIGHUP.17:10
pittijelmer: ah, splendid17:10
pittijelmer: thanks a lot for checking17:10
pittijelmer: while you are there: I have two smbd processes, one is the child of the other17:10
mathiazcjwatson: 1.4.4-4 being the version that added the upstart job, 1.4.4-4ubuntu1 being the one that pitti just uploaded17:10
pittijelmer: is it enough to send sighup to the parent, or do I need both?17:11
pittimathiaz: right, -4 is the only one that wreaks havoc17:11
mathiazpitti: ok - so I'll upload a new version of the samba package wich add a Breaks line17:12
pittimathiaz: cheers17:12
tkamppeterpitti, the Ricoh guys are suggesting to let a straight PS workflow (pstops filter) happen when printing  PS on a PS filter. see e-mail.17:13
jelmerpitti: not sure, I'll check17:13
cjwatsonpitti: right17:14
cjwatsoner17:14
cjwatsonmathiaz: right, that's what I'm thinking17:14
jelmerpitti: fwiw it should update the list every "printcap cache time" seconds as well (defaults to 750)17:14
pittijelmer: ah, so it'll work after 13 minutes anyway?17:14
jelmerpitti: I'm betting that's not an ideal time to have to wait for printers to come up on startup though..17:14
tkamppeterpitti, they do it for two reasons: 1. They observe yellow backgrounds with some files, but this I cannot reproduce. I also have already fixed such kind of bug.17:14
jelmerpitti: yep17:14
pittijelmer: right, so if sending SIGHUP to the parent smbd will cause it to reload immediately, then doing that is easy17:15
pittistatus smbd -> check for "running" -> parse out pid -> send sighup to that17:15
pittibut that doesn't give me the child pid, just the parent17:15
tkamppeterpitti, 2. There is a file which makes one of the Ricoh printers hang with the current workflow.17:16
pittitkamppeter: can we control the filter priorities (ps vs. pdf) on a per-driver level even?17:16
tkamppeterpitti, no. The suggestion is to slightly lower the cost factor of pstops, so that only for the "input is PS and printer is PS" case the PS workflow happened. Possible solutions are implementing this or adding a remark in README.Debian.17:18
pittitkamppeter: why do we do ps -> pdf -> ps at all? so that we can do transformations like "4-on-1" in between?17:18
tkamppeterpitti, the suggested change is replacing17:18
tkamppeterapplication/pdf                 application/vnd.cups-postscript 66      pdftops17:19
tkamppeterby17:19
tkamppeterapplication/pdf                 application/vnd.cups-postscript 65      pdftops17:19
tkamppeterin /usr/share/cups/mime/mime.convs17:19
pittitkamppeter: what's the potential regression from using pstops again?17:20
pittithat'd apply to all printer drivers, not just Ricoh, right?17:20
pittibut indeed I remember similar Debian bug reports which said that using ps works better17:20
tkamppeterpitti, yes, this way we do the page management stuff, like 4-on-1 on PDF data, which always works. PS can be non-DSC-conforming and so a 4-on-1 on PS is not always performed.17:20
tkamppeterpitti, yes, it applies to all PostScript printers and also to drivers which take only PostScript input (like foo2zjs).17:22
=== MacSlow is now known as MacSlow|break
jelmerpitti: <idra> jelmer, IIRC the parent should send a "reload config" message to all children when it receive a SIGHUP17:25
pittijelmer: ah, perfect17:25
pittijelmer: thanks a bunch!17:26
pittitkamppeter: so, if you think it's better that way, please commit to bzr17:26
jelmerpitti: you're welcome, upstart ftw!17:26
* jelmer returns to sync source bugfixing17:27
pitticjwatson, tkamppeter, slangasek, mathiaz: so I'll add the SIGHUP to cups' post-start17:27
cjwatsonsounds good to me17:28
mathiazpitti: sounds good to me as well17:28
=== al-maisan is now known as almaisan-away
pitti$ status smbd | awk '/process [[:digit:]]+/ { print $NF}'17:31
pittithat seems to DWIM17:31
slangasekpitti: technically no17:33
slangasekpitti: you need to make sure it's 'start/running' if you're going to HUP it17:33
ftahighvoltage, what does it take to have bug 636894 fixed (in time)??17:33
ubottuLaunchpad bug 636894 in libvpx (Ubuntu) "please sync libvpx 0.9.2-1 from debian experimental (main)" [Undecided,New] https://launchpad.net/bugs/63689417:33
slangasekso you aren't killing the pre-start script :)17:33
ftahighvoltage (oops, sorry, not for you)17:33
pittislangasek: ah, thanks; does it really need to be "start/running", or could it be anything/running?17:33
pittislangasek: i. e. "I intend to stop, but can't yet"?17:34
fta(was "hi, ...")17:34
slangasekpitti: if it's anything else, there's no reason for you to signal it :)17:34
slangasekpitti: and in most cases, sending the signal would go to a process that's *not* smbd - so I think you should only worry about start/running17:34
pittistatus smbd | awk '/start\/running, process [[:digit:]]+/ { print $NF}'17:34
pittiusing that then17:34
pittiok, I added some logging to cups.conf, seems to work fine17:36
pittiok, committed17:38
pittitkamppeter: do you plan to do a commit for the ps stuff?17:38
highvoltagefta: :)17:38
ftahighvoltage, xchat's fault :P17:39
tkamppeterpitti, yes, I am preparing it now.17:39
tkamppeterpitti, done.17:49
pittitkamppeter: hm, bzr pull doesn't give anything new17:49
pittitkamppeter: 11 minutes to go until freeze starts :)17:49
tkamppeterpitti, resolved conflict and pushed again.17:51
pittihm, that commit looks weird17:52
pittitkamppeter: did you push --overwrite?17:52
=== deryck is now known as deryck[lunch]
pittion a conflict, you should uncommit, pull, fix, and commit again17:52
micahgany AA available for a main sync before Final Freeze (6 minutes)?17:53
cjwatsonmicahg: yes17:53
tkamppeterpitti, I did only bzr push. I never used --overwrite.17:53
micahgcjwatson: bug 636894 please :)17:53
cjwatsonis ubuntu-archive already subscribed to it?17:53
ubottuLaunchpad bug 636894 in libvpx (Ubuntu) "please sync libvpx 0.9.2-1 from debian experimental (main)" [Undecided,New] https://launchpad.net/bugs/63689417:53
micahgyes17:53
cjwatsonok, then I'll just do a sync-helper pass17:54
tkamppeterpitti, conflict was only in debian/changelog, I have made sure that your newer comment got used.17:54
cjwatson(of course, archive admin syncs bypass freezes anyway ... *cough*)17:54
cjwatsonat least I think they do, could be wrong17:54
micahgcjwatson: does that script require a core-dev comment?17:54
cjwatsonnot necessarily, it's interactive so we can apply judgement17:55
micahgcjwatson: ah, ok17:55
cjwatsonthough generally a main sync should have a main uploader's approval17:55
micahgcjwatson: it has one indirectly17:55
cjwatsonhowever, I can look at it since you asked nicely17:55
micahgcjwatson: thank you :)17:56
pittitkamppeter: please bzr pull  --overwrite; I fixed the branch17:56
pittitkamppeter: for some reason the last rev was messed up17:56
tkamppeterpitti, did my attempt to solve the conflict revert the upstart script?17:57
pittitkamppeter: I don't know, I didn't look (want to get this uploaded..)17:57
pittithe topmost change was a weird merge and shuffled the changelog17:58
tkamppeterpitti, did you fix it, so that you can upload?17:58
pittitkamppeter: yes, doing now17:58
ftacjwatson, thanks! (for libvpx)17:59
pittitkamppeter: 2 mins before freeze, nice timing! /me ^5s you17:59
tkamppeterpitti, printing stack has boarded on last call, now we have a great Maverick (especially on Ricoh users).18:00
pittiwe lift off in time18:01
tkamppeterpitti, to land exactly om 10/10/10 at 10:10:10.18:02
cjwatsonmicahg: gar, another bug blocked on bug 63559118:02
ubottuLaunchpad bug 635591 in Soyuz "Regression: syncing packages with UTF-8 changelogs fails" [High,Triaged] https://launchpad.net/bugs/63559118:02
tkamppeterpitti, on the advertizing screen of the metro of Berlin they announce release parties. I hope they will this time stop the metro for one minute to announce this great event :-).18:03
pittihttp://people.canonical.com/~pitti/scripts/syncpackage FTW?18:03
cjwatsonmicahg: I think we can give this a freeze exception though18:03
cjwatsonpitti: the fix is supposed to land soon, and there is another bug blocked on it18:03
pittiah18:03
* cjwatson prefers not to use syncpackage if possible18:03
=== iulian changed the topic of #ubuntu-devel to: Archive: Open | FINAL Freeze in effect! | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper-lucid | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs
=== pitti changed the topic of #ubuntu-devel to: Archive: FINAL Freeze in effect! | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper-lucid | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs
pitti(the archive is not quite "open" any more)18:14
micahgcjwatson: ok, thanks, should I subscribe to the soyuz bug and poke about libvpx when it's cleared18:22
cjwatsonI'm subscribed to the Soyuz bug, and have noted in it all the bugs which it blocks18:22
cjwatsonso I'll go through them myself18:22
micahgcjwatson: great, thank you18:23
=== jtechidna is now known as JontheEchidna
ari-tczewdoes anyone from archive-admins is working on syncs?18:57
ari-tczew(right now)18:57
=== deryck[lunch] is now known as deryck
chrisccoulsonari-tczew, see the topic19:07
ari-tczewok chrisccoulson19:07
cjwatsonari-tczew: I've been doing them at least daily for the last two weeks, and I processed one of yours immediately before the freeze.19:41
ari-tczewcjwatson: yes, thanks19:42
cjwatsonari-tczew: but as of now, as chrisccoulson points out, any change needs a final-freeze exception and needs a very good reason19:42
cjwatsonari-tczew: although actually, if it's in universe and not on the CDs, it's still OK19:42
ari-tczewcjwatson: I would upload a new package - clementine. it's a music player. what are the chances to upload?19:43
cjwatsonari-tczew: you can certainly upload it; whether we accept it would be a judgement call on how complex it looks19:45
cjwatsonI suppose chances would be moderate19:45
cjwatsonit's a question of whether it's likely to need significant fixes to be of release quality19:46
ari-tczewcjwatson: it's not related to main packages, so ubuntu's API won't be broken. :)19:46
cjwatsonI know, but the quality of universe does matter too19:46
cjwatsonas a MOTU you should be keen on that ;-)19:46
ari-tczewcjwatson: ubuntu-release will decide about upload. :)19:48
ScottKari-tczew: You shouldn't propose it unless you are convinced it is appropriate.  We've got pleanty of things to do already.19:53
ari-tczewScottK: I'm convinced about this upload. It's a great music player and we should ship it with Maverick release.19:54
ScottKari-tczew: Why not just wait a month, put it in Natty, and then backport it?19:54
ari-tczewScottK: why not now?19:55
ScottKBecause the people that would have to review it are all busy with other things.19:55
ScottKIf we do it now, some other thing doesn't get done.19:55
ari-tczewScottK: I'm sad to hear this.19:59
ScottKari-tczew: This is why we have a new package deadline in the release schedule.19:59
ari-tczewScottK: when is the deadline for new packages?20:00
ScottKari-tczew: Same as feature freeze, August 12.20:01
highvoltageari-tczew: I don't think it's completely rational being disappointed, the deadline for new packages was more than a month ago already: https://wiki.ubuntu.com/MaverickReleaseSchedule20:01
=== jtechidna is now known as JontheEchidna
highvoltageari-tczew: usually, after that, a FFU (or Feature Freeze Exception) has to be filed to get a new package in: https://wiki.ubuntu.com/FreezeExceptionProcess20:02
=== MacSlow|break is now known as MacSlow
ari-tczewScottK: what do you need review in package?20:03
highvoltageari-tczew: after Final Freeze (today), upi20:03
highvoltageoops, well, after final freeze you'll need an exception for that too20:03
ari-tczewhighvoltage: I know. 2 years ago also I provided FFe for kadu upgrade.20:06
ari-tczewbut it wasn't a new package like clementine right now.20:06
ScottKari-tczew: It's somewhat described in https://wiki.ubuntu.com/ArchiveAdministration20:07
ari-tczewScottK: when we will backport package from natty, new package will be published in -release pocket or -backport?20:10
ScottKari-tczew: Backport20:10
ari-tczewScottK: quite so I'm afraid. I'd give users this music player at start.20:11
ScottKari-tczew: I can understand being disappointed, but it's highly unlikely you'll get an FFe for it approved now.20:12
* ScottK has other this to get busy with.20:12
highvoltageari-tczew: moral of the story: if you want your packages in the archive, try to follow the schedule :)20:13
=== hanska is now known as dapal
ari-tczewScottK: what about other admins?20:14
ScottKI think it's unlikely.20:15
ari-tczewScottK: ok, but I can request FFe, right?20:21
ScottKari-tczew: You can.  I'd prefer you spend your time fixing FTBFS or NBS instead, but you can.20:21
cjwatsonari-tczew: I thought you were focusing on security until release, btw? ;)20:23
ari-tczewcjwatson: that's right. however, I loved use amarok 1.4 and clementine can give me similiar enjoy. I'd give people this great program. It can be a small argument for choice Ubuntu. ;)21:06
keesari-tczew: added you to ubuntu-sponsors21:09
ari-tczewkees: thanks. :)21:11
keesari-tczew: np :)21:12
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
dokoRiddell: kdoctools : Depends: kdelibs5-data (= 4:4.5.1-0ubuntu4) but 4:4.5.1-0ubuntu5 is to be installed22:03
dokoplease stop this insanity!  makes the packages uninstallable until built on armel too ...22:04
lex79doko: kdoctools needs kdelibs5-data for dtd/kdex.dtd needed to build docs22:14
ogra_cmpclex79, i think doko refers to the =22:15
dokoexactly ...22:15
dokothat should be a >= 4.5.122:15
lex79ah, now it is kdelibs5-data (= ${source:Version})22:16
lex79I can change to >=  ${source:Version}22:16
dokolex79: doesn't help, think about it22:16
lex79uhm right ;)22:16
lex79I can drop that (= ${source:Version})22:17
ogra_cmpcyou actually want the upstream version22:17
ogra_cmpc(and the epoch)22:17
=== dendrobates is now known as dendro-afk
=== jtechidna is now known as JontheEchidna
=== dendro-afk is now known as dendrobates
=== dendrobates is now known as dendro-afk
=== bjf is now known as bjf[afk]

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