[16:52] <obfs4[m]> hello theodotos
[16:52] <obfs4[m]> how are you?
[17:16] <theodotos[m]> Hi obfs4 . What's up?


[12:15] <PriceChild> eek forgot to move packaging copyright to bottom but hopefully that doesn't really matter...
[12:20] <thedonvaughn> any revu admins kindly available?
[12:20] <LaserJock> what do you need?
[12:21] <TheMuso_> Hey all.
[12:21] <LaserJock> morning TheMuso
[12:21] <thedonvaughn> LaserJock, remove my account and files that was created yesterday, so that I may re-open it with my correct gnupg key
[12:22] <LaserJock> thedonvaughn: you've updated the key on Launchpad?
[12:22] <thedonvaughn> LaserJock, yes
[12:22] <thedonvaughn> LaserJock, the issue is i was never able to get my password.  I uploaded one package with my old key, and i can not decrypt it because of an error with my elg-e secondary key
[12:25] <bashelier> hey TheMuso :)
[12:25] <bashelier> TheMuso: I have a question about network-manager-ovpn
[12:26] <bashelier> TheMuso: why didn't you add the patch 02_fix_wrong_awk_path.diff in the Debian package ?
[12:28] <bashelier> TheMuso: oups I'm sorry, you're not the one I was looking for for this package ^^", anyway, I have qestion about adonthell-data
[12:30] <Adri2000> bug #118508 - TheMuso: I reviewed bashelier's merge of adonthell-data
[12:30] <ubotu> Launchpad bug 118508 in adonthell-data "Please merge adonthell-data 0.3.4.cvs.20050903 from Debian Unstable (main)" [Wishlist,In progress]  https://launchpad.net/bugs/118508
[12:30] <Kmos> !factoid
[12:30] <ubotu> I am ubotu, all-knowing infobot. You can browse my brain at http://bots.ubuntulinux.nl - Usage info: http://wiki.ubuntu.com/UbuntuBots
[12:31] <Adri2000> TheMuso: and I'm not sure of "Update Italian translation." which you put as a remaining change
[12:32] <Adri2000> TheMuso: it's not in the previous ubuntu changelog entry, and my guess is that these .po changes come from MoM's output, and that you thought they were real changes
[12:34] <bashelier> geser, Lutin: https://bugs.launchpad.net/ubuntu/+source/xulrunner/+bug/118500
[12:34] <ubotu> Launchpad bug 118500 in xulrunner "Please merge xulrunner (universe) from Debian unstable (main)" [Undecided,Rejected]
[12:34] <TheMuso> Adri2000: Yes thats right. I wasn't sure what happened back then, so leaving that out of the new entry is fine.
[12:35] <pygi> hi hi
[12:35] <Adri2000> ok, thanks TheMuso. bashelier: so you can fix that
[12:36] <bashelier> Adri2000: ok
[12:36] <pochu> Adri2000: would you mind to review 118030 too? :)
[12:36] <pochu> bug 118030
[12:36] <ubotu> Launchpad bug 118030 in listen "Please merge Listen 0.5-3 from Debian Unstable (main)" [Low,Confirmed]  https://launchpad.net/bugs/118030
[12:39] <Adri2000> pochu: #87959 is already closed, so no need to mention it in the remaining changes, otherwise soyuz will try to re-close it :)
[12:40] <bashelier> Adri2000: done
[12:42] <pochu> Adri2000: It was for reference. Would "#87959" be OK (instead of "LP: #")
[12:43] <crimsun> LaserJock: it's dirty, but someone has to do it.  Besides, many of our bug reports come from there (even though they're not reported as bugs...)
[12:43] <crimsun> I'm probably missing a good 70% of ALSA bugs simply by not reading UF consistently
[12:44] <LaserJock> crimsun: yeah, that's the bugger of it
[12:45] <Adri2000> pochu: personally I don't put the bug number at all in the remaining changes. but if you prefer to put it, no problem, I'll keep it with "LP:" (I hope soyuz can handle it :p)
[12:45] <crimsun> anyhow, back into hell.
[12:45] <LaserJock> for all the junk and noise, there is a certainly amount of good stuff there
[12:46] <LaserJock> thedonvaughn: ok, got the keyring synced, what packages did you upload?
[12:50] <joejaxx> LaserJock: crimsun maybe someone can work out some LP/VBF bridge :P
[12:51] <thedonvaughn> LaserJock, thanks, i sent you a pm
[12:52] <LaserJock> joejaxx: yeah, the Forums guys have some proposals on that ;-)
[12:52] <joejaxx> ;)
[12:54] <pochu> Adri2000: so do you find it ok? :)
[12:55] <crimsun> joejaxx: I'm tired of waiting for something to happen, and meanwhile, hundreds of potential bug reports are being lost in the cracks.  This reflects poorly on my work, on Ubuntu and its derivatives, and generally, I just don't have time for this mess.
[12:56] <joejaxx> crimsun: yeah :\
[12:56] <joejaxx> crimsun: maybe UF should point people to launchpad
[12:56] <LaserJock> well, they've added some LP linkage
[12:56] <joejaxx> and a FAQ on how to submit a useful bugs
[12:56] <LaserJock> I think you can link *to* LP from UF
[12:57] <joejaxx> s/a//g
[12:57] <LaserJock> I'm pretty sure they already have FAQ/Stickies on that
[01:00] <Adri2000> pochu: I'll upload it as soon as I've finished with bashelier's merge
[01:02] <joejaxx> LaserJock: so why are people still submitting bugs on the forums? :\
[01:02] <joejaxx> "submitting"
[01:02] <pygi> joejaxx, they'll always do that, you can't stop them
[01:02] <LaserJock> joejaxx: because people don't read
[01:02] <LaserJock> the don't know what's a bug and what isn't
[01:03] <crimsun> that's not necessarily an issue.
[01:03] <LaserJock> because they would have to leave the forums and sign up on LP
[01:03] <crimsun> What _is_ an issue is that there is no way for devs to cull this information from UF.
[01:03] <LaserJock> because they want a quick solution to their problem and not run around LP
[01:03] <joejaxx> i am surprised more people have not been using answers.lp
[01:03] <LaserJock> crimsun: yes, I agree
[01:03] <LaserJock> joejaxx: they won't use what they don't know about
[01:04] <joejaxx> LaserJock: true
[01:04] <joejaxx> maybe there needs to be a forum announcement
[01:04] <crimsun> I agree that a user shouldn't _have_ to use launchpad
[01:04] <crimsun> I do not agree that there is not _employed_ Canonical structure in place to make it happen
[01:05] <PriceChild> Hey crimsun, upstream fixed the copyright and wondered whether http://revu.tauware.de/details.py?upid=5358 is good for an advocation yet? :)
[01:05] <crimsun> We simply cannot expect anyone - users, maintainers, developers, whatever - to read _everything_ before asking for help
[01:06] <crimsun> And likewise, those of us hacking upstream and downstream don't have resources to ferret out all these posts
[01:06] <PriceChild> joejaxx, whenever i see someone reporting a bug on the forum I point them towards launchpad... but I don't see everythign and it just needs more people pointing the others :)
[01:06] <joejaxx> PriceChild: :)
[01:06] <crimsun> PriceChild: I'm not even close to finishing my Forum stomp, sorry.  Perhaps in a few hours if someone else hasn't stepped up.
[01:07] <PriceChild> Haha :) I'm off to bed soon so I won't notice :P
[01:07] <crimsun> 28124 posts?  Right.
[01:07] <crimsun> And this is just Hardware & Laptops.  :(
[01:08] <joejaxx> crimsun: do you think some sort of extended search engine would help?
[01:08] <joejaxx> have an external search engine spider the forums
[01:08] <joejaxx> or certain parts
[01:08] <crimsun> joejaxx: that would still require someone to _search_, which may be useful for new users but certainly doesn't assist a resource-starved dev
[01:08] <joejaxx> crimsun: true
[01:09] <joejaxx> so we want the information to be pre-presented
[01:09] <joejaxx> in some sort of organized fashion
[01:09] <crimsun> think about it: users and devs are identical.  We all want information at our fingertips.  The difference is that the latter wants pertinent information to resolve the former's symptoms.
[01:09] <joejaxx> yeah
[01:11] <Plug> A new version of network-manager-pptp, which closes lots of bugs, including a bit AMD64 crasher, is available for revu: http://revu.tauware.de/details.py?upid=5361
[01:11] <Plug> It's been tested by people on LP bugs and received good feedback.
[01:12] <LaserJock> crimsun: yeah, I just don't know really how you do much about that
[01:12] <LaserJock> in a concrete sense
[01:13] <crimsun> Plug: remember to mention the debian/control change.
[01:14] <Plug> as a changelog entry?
[01:14] <crimsun> yes.
[01:15] <crimsun> also, update COPYING in the root of the extracted source package.  The FSF address is outdated.
[01:16] <Plug> I've been prompted about that by lintian before.  Has it changed again more recently than feisty's release?
[01:17] <nixternal> crimsun: mind taking a look at bug 118517 when you get a chance?
[01:17] <ubotu> Launchpad bug 118517 in plucker "[Gutsy Merge]  Please merge plucker (1.8-21ubuntu1) from Debian Unstable (main)" [Undecided,Unconfirmed]  https://launchpad.net/bugs/118517
[01:17] <crimsun> Plug: no, but the version distributed in the source package still uses the obsolete one
[01:17] <Adri2000> pochu: what about the change "Don't modify listen.py's hashbang (it's not there anymore because of 07_listen.py.patch)" ? I don't see it in debian, is it not needed anymore?
[01:18] <Plug> crimsun: right.  I wonder why lintian didn't tell me this time.
[01:19] <Plug> Is that something that I should fix in the orig.tar.gz, or as a dpatch?
[01:20] <Adri2000> pochu: ok, it has been done in debian, but it's not explicitly written in the changelog
[01:23] <crimsun> Plug: just fix it in the extracted source so it'll appear in the diff.gz
[01:23] <crimsun> Plug: oh wait, is this a new upstream version?  Then yes, fix it in the orig.tar.gz.
[01:23] <crimsun> Sorry about the confusion.
[01:24] <crimsun> yay, page 4 of 1407
[01:25] <Adri2000> pochu: listen uploaded
[01:25] <crimsun> god, have they _still_ not fixed plucker?
[01:26] <nixternal> crimsun: I am working on that
[01:26] <crimsun> no, I'm referring to the patch
[01:26] <nixternal> there is no more plucker development sadly, unless they are doing it underground
[01:27] <nixternal> well, I am redoing a SVN patched version of plucker that will probably be Ubuntu only as I can get the Debian maintainer in on it 100% yet
[01:27] <nixternal> I have a library I am trying to get sponsored now in Debian that will allow us to use the patched plucker in the svn snapshot
[01:28] <crimsun> ok, so what do you want me to do with 118517?
[01:28] <nixternal> I guess merge it for the time being to close it in MoM and DaD, that way there nobody else goes messing with it I guess
[01:29] <crimsun> ok, please reroll the debdiff (adhere to DebianMaintainerField)
[01:30] <nixternal> we are back to that now...last I was told not to and now I am being told to do so. :)
[01:30] <nixternal> I will reroll it really quick
[01:30] <crimsun> ....who told you not to?
[01:30] <nixternal> sorry, I partake in the "no snitching law" :p
[01:31] <nixternal> in other words, I don't remember
[01:31] <nixternal> I have an idea, but I can't remember 100%
[01:31] <crimsun> ok, well remember that if we modify anything in the Debian source package, then we adhere to DebianMaintainerField.  This includes simple rebuilds.
[01:32] <crimsun> The only exception if is the Maintainer field already contains an @ubuntu.com
[01:32] <nixternal> roger that
[01:32] <crimsun> right, is if ^.
[01:32] <Adri2000> crimsun: do we have to adther to DebianMaintainerField when uploading a build1 version?
[01:32] <Adri2000> adhere*
[01:33] <nixternal> crimsun: do I add the XSBC-Original-Maintainer or remove the original maintainer totally?
[01:33] <crimsun> nixternal: add & change.
[01:33] <crimsun> Adri2000: it's a good idea to change it (as stated above).
[01:33] <Plug> http://revu.tauware.de/details.py?upid=5363
[01:35] <pochu> Adri2000: thanks!
[01:35] <Adri2000> pochu: np, thanks for your work on this package :)
[01:39] <nixternal> crimsun: http://launchpadlibrarian.net/7935687/plucker_1.8-21ubuntu1.debdiff
[01:41] <crimsun> nixternal: please note the debian/control change in debian/changelog
[01:44] <nixternal> crimsun: http://launchpadlibrarian.net/7935695/plucker_1.8-21ubuntu1.debdiff
[01:44] <nixternal> thank you :)
[01:47] <crimsun> done, please follow up.
[01:48] <PriceChild> persia, Woo thanks for advocation :)
[01:49] <nixternal> I am building a new package, and it is one that requires the following commands in order to install via tarball
[01:50] <nixternal> make -f Makefile.dist && ./configure --prefix=`kde-config --prefix` && make && sudo make install
[01:50] <nixternal> how would you go about doing a rules file for that there? would you recommend debhelper or cdbs for it?
[01:51] <persia> nixternal: If you're using cdbs, add make -f Makefile.dist to your makebuilddir/foo:: rule.  If using debhelper, just put it before ./configure in your configure: rule.
[01:52] <LaserJock> persia: question about ggobi, why did you convert the .png to .xpm?
[01:52] <LaserJock> persia: well, I guess you maybe didn't do the actual change
[01:53] <persia> LaserJock: I didn't actually change it, but my recommendation is to include both .xpm and .png to support Debian menu files (eventually).
[01:53] <LaserJock> seems odd
[01:53] <LaserJock> I'd just install the .png and be done with it
[01:54] <LaserJock> anyway, I just saw it go by on ubuntu-science so I thought I'd ask
[01:54] <persia> LaserJock: If you do that, and someone creates a Debian menu file, it won't show up, as the Debian menu system requires .xpm format for images.  I remember something about discussion to change that, but I don't know that it happened.
[01:55] <TheMuso> c
[01:55] <TheMuso> ugh
[01:55] <LaserJock> persia: sure but I don't know why Ubuntu should carry a diff for Debian menus :-)
[01:55] <LaserJock> Debian shouldn't even be using Debian menus ;-)
[01:56] <persia> LaserJock: Yeah, well.  I'm going to disagree with you formally for policy reasons, but I completely agree with the reasons for your claim :)
[01:56] <LaserJock> hehe
[01:58] <nixternal> for copyright, using the persons IRC nick isn't appropriate correct?
[01:58] <nixternal> I don't know wtf people can just put their damn names and email addresses in copyright properly
[01:59] <PriceChild> Wahey thanks crimsun!!! :D
[01:59] <LaserJock> nixternal:  OMG, SPAM!
[01:59] <nixternal> right
[01:59] <nixternal> you know what, this is a great app too...this dude needs to be smacked for his noobish ways though
[01:59] <LaserJock> or is that OMG, mechanically separated animal byproducts
[01:59] <persia> nixternal: There are special exceptions to allow pseudonyms in copyright, but it has to be a registered pseudonym (with the appropriate authority granting the copyright).
[02:00] <nixternal> persia: this person has put their online nick in every header for the source
[02:00] <nixternal> and uses a freakin' link to a web form contact page
[02:01] <persia> nixternal: If they haven't registered their online nick as a pseudonym with their local government office, that's just wrong.
[02:01] <nixternal> persia: people actually do that? if they do, then they are wrong as well ;p
[02:01] <nixternal> haha, I am going tomorrow and registering my nick
[02:01] <nixternal> muhehe
[02:03] <LaserJock> nixternal: registering Mr. Vista?
[02:04] <nixternal> heh, if you go to the apps website, he puts out everyones name who contributed and their email address, yet he doesn't provide his info
[02:04] <nixternal> LaserJock: ..*#*#$($!)*)$&@#)*$#_@*$*_%&)#*)#__@#+($*_%#*)#$
[02:04] <nixternal> I think that qualifies for hell just having that though ;)
[02:04] <LaserJock> wow, that's "swearing ... Chicago style"
[02:04] <nixternal> hahahaha
[02:08] <nixternal> if this guy has KDE SVN access, he can only hide so much...muhehehe
[02:08] <nixternal> thank god kde svn is so slow right now
[02:14] <nixternal> 2 people in Ubuntu Chicago with Dell 1501s, DEAD, 3 people in my LUG with 1501s, DEAD. That is 5, count them 5, Dell 1501 series laptops dead within the past month or so
[02:17] <ramatieg> Is there an easy way to statically link only some libraries?
[02:18] <crimsun> nixternal: so what are you saying about Vista?
[02:18] <crimsun> Vista kills people?
[02:18] <nixternal> yes
[02:18] <nixternal> it is like cigarettes
[02:18] <nixternal> now we just need to get more people to start sueing
[02:19] <crimsun> neat, so if I get all these Forum users to use Vista...
[02:19] <LaserJock> crimsun: nixternal likes the rush of russian roulette/Vista
[02:19] <crimsun> must be a Chicago thing
[02:19] <LaserJock> must be
[02:19] <nixternal> you know, I could go with XP or 2000, but vista? hell man, you might as well tell people I am the purple teletubby
[02:20] <crimsun> we already knew that.  You have a reddish purse emblazoned with the Microsoft logo.
[02:20] <nixternal> I have tried Vista 1 time, at Best buy or Circuit city...I have watched it break though on other people's machines
[02:20] <nixternal> gah!@!#
[02:20] <Kioshen> :)
[02:20] <nixternal> teehee
[02:20] <nixternal> hahahaha
[02:21] <nixternal> oh wait, BitchX has the /f#@#em script
[02:21] <nixternal> but I don't have powah here
[02:21] <DarkSun88> Night.
[02:22] <ryanakca> nixternal: what happened to irssi? eh?? eh???
[02:22] <nixternal> heh, that is all I use
[02:22] <ryanakca> lol
[02:22] <nixternal> 19:22:34 Irssi: Client: irssi 0.8.11 (20070425 1813)
[02:22] <ryanakca> mIRC scripts in irssi?
[02:22] <nixternal> I am afraid to use Konversation, seeing as Kubuntu does it all wrong ;p
[02:23] <nixternal> and you know I am poking fun at recent events with that I am sure
[02:24] <ryanakca> Konversation hates me :S
[02:25] <nixternal> heh, and so do the devs ;p
[02:25] <nixternal> hahahahah
[02:25] <nixternal> where is jucato when you need an answer to anything?
[02:25] <ryanakca> I get disconnected once, and then I get reconnected 25 times in a span of 3 minutes, with "Excess Flood" as the quit message
[02:28] <LaserJock> I like konversation
[02:28] <ryanakca> LaserJock: I did too
[02:28] <LaserJock> but tend to use xchat/irssi more since I'm in gnome
[02:28] <ryanakca> yeah
[02:28] <ryanakca> irssi runs on my server, and I can get to it from anywhere
[02:29] <ryanakca> offtopic-ish question:
[02:29] <ryanakca> CMake Error: Could NOT find QtCore. Check /home/kde-devel/kde/build/soprano/CMakeFiles/CMakeError.log for more details.
[02:29] <ryanakca> when trying to build soprano, as per http://techbase.kde.org/Getting_Started/Build/KDE4#Soprano
[02:30] <ryanakca> any idea?
[02:32] <crimsun> finally on page 6 of 1407. :(
[02:32] <LaserJock> wow
[02:32] <TheMuso> crimsun: Ok to take qjackctl?
[02:32] <ryanakca> crimsun: for?
[02:32] <crimsun> TheMuso: all yours.
[02:33] <TheMuso> crimsun: Thanks.
[02:33] <LaserJock> crimsun:  you must be going pretty thoroughly
[02:33] <crimsun> TheMuso: keep in mind the md5sum mismatch, so you'll need to manually apply the Debian diff.gz against our orig.tar.gz.
[02:33] <persia> TheMuso: about 8 hours ago, DarkSun88 was looking at whether the new upstream version closed a couple more LP bugs.  I thought there would be another debdiff (and completely failed to leave a comment).
[02:34] <TheMuso> Right.
[02:34] <crimsun> LaserJock: well, yes.  What's the alternative? :)
[02:34] <TheMuso> persia: I'll keep my eye out then.
[02:34] <crimsun> ryanakca: trawling the Forums for audio "bug reports".
[02:34] <persia> TheMuso: I don't think the merge changes - just whether the LP bugs are closed automatically (if you want better freebob or just to clear the queue).
[02:34] <ryanakca> crimsun: oh, fun
[02:34] <LaserJock> crimsun: skimming I guess
[02:35] <TheMuso> persia: Right.
[02:35] <crimsun> LaserJock: not an option.
[02:35] <crimsun> imagine if your kernel simply skimmed your hardware.
[02:35] <crimsun> "Oh, that's unimportant."
[02:36] <LaserJock> I thought that's what it did ;-)
[02:36] <StevenK> "What's that? Oh, it's a video card. I don't care."
[02:36] <crimsun> actually, that sounds like a really interesting DoS. Hmm.
[02:43] <TheMuso> crimsun: I take it by MD5sum mismatch you are rerfrering to .orig.tar.gz?
[02:43] <crimsun> TheMuso: yep.
[02:43] <TheMuso> Ok.
[02:56] <TheMuso> hmm ok. Looks like a merge request was filed.
[03:01] <ryanakca> umm. can anybody open kdiff3 foo.BASE foo.OTHER foo.THIS   and then scroll up and down with the middle scrollwheel? I'm getting low-pitch static like noise out of my speakers, only when I scroll in that app.
[03:02] <crimsun> um...
[03:02] <crimsun> so what are you really saying?
[03:03] <persia> ryanakca: That's not a kdiff issue - it's related to the video card and sound card.  Try wrapping your sound card in a faraday cage.
[03:03] <crimsun> are you saying that opening multiple files with kdiff3 results in non-working scrolling or that attempting to use the scroll wheel exposes pci bus noise?
[03:03] <ryanakca> crimsun: lost me :)
[03:03] <crimsun> that's precisely what I said, too.
[03:03] <crimsun> I have no idea what you are trying to say.
[03:03] <ryanakca> crimsun: the latter I guess
[03:04] <crimsun> it's most probable that you have a lower quality motherboard.
[03:05] <crimsun> if it truly bothers you, use a USB audio device, or puncture your eardrums.
[03:06] <ryanakca> crimsun: I'll take puncturing my eardrums :)
[03:06] <ryanakca> crimsun: just thought it was a bit odd, but, nevermind
[03:10] <nixternal> what can I do about this package? the author only wants to give out his nick and a form to email him?
[03:11] <persia> nixternal: You might be able to find a useful cluebat in the debian-legal archives, if you really want the package.
[03:11] <nixternal> I have been searching that for the past 30 minutes
[03:11] <nixternal> I am back in 2006, gotta few years to go yet :)
[03:11] <crimsun> combine google with waybackmachine
[03:16] <jmg> doesnt google sponsor archive.org?
[03:17] <crimsun> page 9!
[03:39] <crimsun> ok, overdosed on the Forums for now.
[03:40] <nixternal> heh, I found my first company I worked for after the military on wayback...pretty cool
[03:41] <nixternal> so I found the old webpage I did for them, about 9 years ago
[03:54] <Hobbsee> morning all
[03:55] <RAOF> Mornin Hobbsee
[03:56] <Hobbsee> :)
[03:56] <Hobbsee> hi spam
[03:56] <jsgotangco> hi!
[03:56] <jsgotangco> good morning!
[03:57] <Hobbsee> :)
[04:01] <nixternal> hiya jsgotangco
[04:03] <jsgotangco> hey nixternal how's it going on your side
[04:03] <nixternal> it's going
[04:03] <nixternal> how about yourself?
[04:04] <jsgotangco> not bad will be moving to new place and work in a week so things have been hectic
[04:05] <nixternal> cool, at least you are going back to work
[04:05] <jsgotangco> well a month of rest helped
[04:06] <jsgotangco> also got to sort out a lot of personal ToDos
[04:06] <jsgotangco> right now I am just grabbing Nexuiz and will be fragging
[04:07] <Plug> crimsun: cheers for the upload
[04:09] <nixternal> well, from what I have found, you can use whatever name you want when copyrighting your material...you can even use Anonymous for a name
[04:14] <persia> nixternal: It really depends on your jurisdiction.  For US law, see  401.b.3 of http://www.copyright.gov/title17/92chap4.html.  At least in the US, it is required that one use a "generally known alternative designation", which is usually interpreted to be a properly registered alias.
[04:14] <nixternal> persia: in the US I can copyright a book under Anonymous or a pseudonym
[04:14] <nixternal> that is why this is confusing
[04:15] <nixternal> there are many countries that allow this, and then there are some countries that don't
[04:15] <nixternal> I found an entire thread on just this in debian-legal from 1998
[04:15] <ScottK> nixternal: Get your licensing question figured out yet?
[04:15] <nixternal> nope
[04:16] <nixternal> can you use apt-cache to search within a license? or any command where I can search for stuff within the debian/copyright? there are a couple of names that are listed and I want to see if I can find them
[04:16] <ScottK> grep?
[04:18] <nixternal> how would I use grep to go through the repos and find a name?
[04:18] <nixternal> man, and don't tell me to bash it :)
[04:20] <persia> nixternal: Which thread?  I've just skimmed all the 1998 archives, and I'm not seeing it.
[04:21] <nixternal> sorry..hehe 2003
[04:21] <nixternal> site: works great in google :)
[04:21] <nixternal> http://lists.debian.org/debian-legal/2003/10/msg00204.html
[04:21] <nixternal> there is the start of it..that is the most confusing and uneducated thread I have ever read
[04:22] <nixternal> it is nothing more than a bunch of he-said, she-said
[04:24] <nixternal> heh, the greatness of a phone call to a lawyer
[04:24] <nixternal> he just told me I could copyright any material as "Jesus Christ" if I wanted to
[04:25] <nixternal> and to think, copyright lawyers answer the phone at 9:30pm on a sunday evening
[04:25] <nixternal> if I was to sue, I would have to come forward and prove that I am "Jesus Christ" though
[04:26] <kenro> Oh it's good to be back home.
[04:26] <kenro> On Freenode...
[04:26] <nixternal> heh, did you click your heals together a few times first?
[04:26] <nixternal> now place like freenode
[04:26] <nixternal> now place like freenode
[04:26] <nixternal> jeesh, I can spell
[04:26] <kenro> Fayd knot
[04:26] <nixternal> heh
[04:26] <persia> nixternal: I agree with ScottK: you should ask an archive admin.  From my reading, I believe that copyright under pseudonym is OK, so long as it can later be shown that the pseudonym uniquely identifies an entity (person or corporation), but that anonymous copyright does not restrict rights in any way (is indistinguishable from public domain).  Regarding copyright to Jesus Christ, that's just an assignment of copyright: you cannot later assert re
[04:27] <persia> Grr.   "Regarding copyright to Jesus Christ, that's just an assignment of copyright: you cannot later assert restrictions (e.g. GPL) unless these are agreed by the assignee."
[04:27] <kenro> I pirated time from churches, hotels, even Fedex/Kinkos.
[04:27] <nixternal> are there any archive admins online right now?
[04:28] <kenro> persia, why would someone waste time to get anonymous patent?
[04:29] <nixternal> kenro: don't get me started on that one ;p
[04:29] <nixternal> I am dealin with a package that is anonymous in (c) holding
[04:29] <persia> kenro: My claim is that an anonymous copyright doesn't mean anything.  I suspect the same applies to patents, but as there is no automatic grant of patent, I suspect that pseudonymous patents are the closest one could ever achieve.
[04:31] <nixternal> I just asking Mith in ubuntu-devel, I am sure he is sleeping where ever in the world he is right now
[04:32] <kenro> So (one) might seek to garauntee that no other should use said * to make money...
[04:33] <kenro> forget it, I won't get you started...
[04:33] <Hobbsee> nixternal: yes, and norway
[04:34] <nixternal> oh ya, definitely sleeping
[04:34] <kenro> When's the Gibbon coming?
[04:34] <nixternal> October
[04:36] <kenro> Well, I hope it's safe to use early, coz I just spent 35 dollars on an install CD that's 3 releases old.
[04:37] <nixternal> http://tinyurl.com/2u69f4
[04:37] <nixternal> cool
[04:38] <kenro> nixternal:  think that's tiny, I got the world's shortest poem. I'm publishing it tonoght public domain.
[04:38] <kenro> LOOK   See Me.
[04:41] <persia> nixternal: At least in AU, http://www.copyright.org.au/publications/G024.pdf seems to indicate that the copyright holder must be able to assert rights in order to grant a license (e.g. GPL).  Otherwise, the work is protected by normal copyright (so assigning copyright to "Jesus Christ" means you cannot then GPL the software).
[04:42] <kenro> persia:  Can I GPL my poem?
[04:42] <Hobbsee> nixternal: FWIW, usually a person will require being in the web of trust for uploading things - which requires that they've shown a person in the web of trust their ID which matches their key.
[04:42] <persia> kenro: If you can demonstrate you can assert copyright, yes.
[04:43] <Hobbsee> but copyright is likely different
[04:43] <kenro> persia:  I just released it to pubdom...
[04:44] <nixternal> there are packages in Debian with
[04:44] <nixternal> Upstream Author: Money<EMAIL_ADDRESS>[04:44] <nixternal> err
[04:44] <nixternal> s/Money/Monty
[04:45] <nixternal> heh. the vorbis stuff as a matter of fact is like that
[04:45] <nixternal> http://svn.xiph.org/trunk/cdparanoia/debian/copyright
[04:45] <persia> nixternal: That's a pseudonym which can be disambiguated by running `whois xiph.org`.  That's sufficient to meet "generally known".
[04:45] <nixternal> interesting
[04:46] <nixternal> well I have an email address for this other person
[04:47] <nixternal> well, this same person has a few copyrights in both KDE and possibly Debian
[04:48] <persia> nixternal: If you can (relatively) easily get sufficient information to contact the person to discuss licensing questions, it may be sufficient.  Getting Monty's physical address is easy, but I don't know about your new package.
[04:48] <nixternal> ya, I don't know about a physical address
[04:49] <kenro> Forgive me for the over-the-top counterexample...
[04:50] <nixternal> well, seeing as he has some library files that are in kde, of which is in Debian...I need to find the packages now
[04:51] <nixternal> http://directory.fsf.org/KPlayer.html
[04:51] <nixternal> there is the FSF "verifying" his license and listing him in the directory
[04:52] <nixternal> I can put that in the copyright file as backup maybe?
[05:10] <kenro> I'll be back. Unless I'm Beethoven first.
[05:46] <Dabian> I have trouble mailing mwolson
[05:46] <Dabian> I get an error
[05:47] <nixternal> alrighty then
[05:49] <crimsun> right, no mention of method or error.
[05:49] <crimsun> -brilliant-
[05:50] <nixternal> hehe
[05:51] <nixternal> Requires: or Required:
[05:51] <nixternal> to lazy to google
[05:57] <nixternal> crimsun: if I am building a package the is a KDE frontend to mplayer, mplayer doesn't go in the build-depends: correct? does it go into depends:
[05:59] <nixternal> nm, answered my own question
[06:01] <crimsun> just Depends
[06:01] <crimsun> unless it's so screwed up that it actually requires mplayer being present to compile...
[06:02] <nixternal> it doesn't
[06:29] <arcligh1> I have a quick question about .deb packaging, specifically, how to add manpages for code that doesn't have any in the original source tarball.
[06:29] <RAOF> You write one :)
[06:29] <arcligh1> :)
[06:30] <arcligh1> I used help2man to make minimal man pages.
[06:30] <RAOF> An example of that is the "specto" source package.
[06:30] <RAOF> Oooh, that sounds like a good idea. :)
[06:31] <arcligh1> I've built my first package but it's from FSF so there are no man pages; I added them, packed everything up, but they're not in the original tarball so I was afraid they'd disappear if anyone regenerated the package.
[06:31] <RAOF> And you want to know how to get those man pages into the right spots in the final package?
[06:31] <arcligh1> Precisely.
[06:31] <crimsun> dh_installman(1)
[06:32] <crimsun> remember to build
[06:32] <crimsun> -depend on debhelper
[06:33] <RAOF> arcligh1: They will (or should) make it into the diff, so your man pages will stay in the source package.
[06:33] <arcligh1> Let me check what I've built so far...
[06:34] <arcligh1> FWIW, for as many files as I had to touch, the whole process was far less painful than an equivalent RPM build. A nice surprise.
[06:48] <arcligh1> Ok, I think I see what's happening.
[06:49] <arcligh1> I'm building a package for marst, the GNU ALGOL60 -> C translator
[06:49] <arcligh1> (don't ask...)
[06:49] <arcligh1> I unpacked it, created the ./debian directory with skeleton files, deleted a bunch and edited the rest
[06:50] <RAOF> Sounds good so far
[06:50] <arcligh1> generated the manpages and put them in the original ./docs directory in the unpacked source tree
[06:50] <RAOF> They should probably be in the debian directory.
[06:51] <arcligh1> iteratively built the package, ran lintian, and adjusted the ./debian files until lintian came up clean
[06:51] <RAOF> (Generally, you shouldn't change *anything* outside of the debian directory.  If you need to, it's a good idea to add a patch system to the build)
[06:51] <arcligh1> Agreed.
[06:52] <RAOF> Sounds like the package is pretty much ready for review, then?
[06:52] <arcligh1> I hope so
[06:52] <arcligh1> It wasn't clear how to format marst.manpages to reference manpages in the ./debian directory
[06:53] <arcligh1> It just contains doc/macvt.1 and doc/marst.1
[06:53] <arcligh1> This feels like a dumbly simple question
[06:53] <RAOF> They'd be "debain/macvt.1" and "debian/marst.1", surely.
[06:54] <arcligh1> Duh. :)
[06:54] <arcligh1> That's disturbingly clear.
[06:54] <RAOF> As far as I know, all directories in all the files are relative to the top-level source directory.  The debian directory is just another directory :)
[06:54] <arcligh1> Thanks!
[06:54] <RAOF> NP.
[06:55] <arcligh1> I have this strange urge to package up dead languages so it's easy for people to play with them, say in the context of a CS comparative languages class.
[06:56] <arcligh1> And a small project like this was perfect for learning how to build .deb packages.
[06:57] <arcligh1> I'm a sysadmin; my background is in engineering not CS so I'm trying to pick up all the stuff I would've learned without having to get another degree.
[06:58] <RAOF> Fair enough.
[06:58] <RAOF> Once you've got some idea of how debhelper works, you can use CDBS, which does almost everything for you :)
[06:58] <arcligh1> Cool.
[06:58] <RAOF> It's a bit of arcane magic, though, so it's good to have some idea how it does what it does for when it breaks.
[06:59] <arcligh1> I figured I'd start simple.
[07:00] <arcligh1> Now to sort out this bzr thing; I've stuffed the package into my local svn repository so at least it's under some form of version control.
[07:01] <RAOF> Aaah, sweet bazaar.
[07:01] <RAOF> Sweet, sweet distributed version control.
[07:02] <arcligh1> "B-but where does the canonical source *live*? ... Brain ... melting ..."
[07:02] <arcligh1> :)
[08:24] <imbrandon> qemubuilder .... hrm
[08:30] <imbrandon> quiet night
[08:30] <imbrandon> heh good, i'm at work, hopefully they will be gone when i get there
[08:34] <nixternal> I have just finished watching the sopranos for the 3rd time tonight...drive-by sounds harmless now
[08:34] <imbrandon> heh
[08:35] <nixternal> 1 more episode to go
[08:35] <nixternal> man, I can't wait until next Sunday
[08:36] <highvoltage> nixternal: I love it when I feel that way about a series :)
[08:36] <nixternal> man...I don't think I have ever watched a show that has kept me on the edge so much
[08:36] <nixternal> not even M.A.S.H. did that for me
[09:36] <crimsun> hmm, www.ubuntuwire.com doesn't lead to the "community buildds" anymore?
[09:40] <crimsun> 8 K/s on tiber.
[09:53] <dholbach> good morning
[10:02] <bashelier> hey dholbach :)
[10:04] <bashelier> dholbach: could I show you one merge ore two ?
[10:04] <dholbach> hey bashelier
[10:04] <crimsun> dholbach: when you have time, please eyeball http://adhd.irule.net/~crimsun/rhythmbox_0.11.0-0ubuntu3.debdiff . I've tested the upgrade path and verified it resolves the issue.
[10:04] <dholbach> bashelier: can you post links in here for somebody to review them and if you don't get answers drop me a mail about it?
[10:05] <bashelier> dholbach: no problem, thanks :)
[10:05] <dholbach> thanks bashelier
[10:05] <bashelier> here are two merge requests, https://bugs.launchpad.net/ubuntu/+source/inventor/+bug/118608 and, https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/118604, could someone have a look ? :)
[10:05] <ubotu> Launchpad bug 118604 in erlang "Please merge erlang (universe) from Debian Unstable (main)" [Undecided,Unconfirmed]
[10:07] <dholbach> crimsun: looks good
[10:07] <dholbach> crimsun: thanks for looking into it
[10:07] <crimsun> dholbach: I have a source package prepared locally and can upload it now.
[10:08] <dholbach> crimsun: rock on - just upload it
[10:08] <crimsun> done.
[10:08] <dholbach> crimsun: not sure about tribe1 freeze though - but in that case it'll be queued anyway
[10:13] <Fujitsu_> crimsun: Yay! /me builds.
[10:13] <crimsun> if you want a deb, I pbuilt it earlier
[10:14] <Fujitsu> Ah, yes please. I'm currently building qgis, so it'd have to wait a couple of hours if I were to build.
[10:15] <Fujitsu> Found it, thanks.
[10:15] <crimsun><EMAIL_ADDRESS>sha1sum rhythmbox_0.11.0-0ubuntu3_i386.deb
[10:15] <crimsun> b2be85b8c4820e38cbb884bd5b98aecf4231d7dd  rhythmbox_0.11.0-0ubuntu3_i386.deb
[10:16] <Fujitsu> Right.
[10:16] <Fujitsu> Box. Very creative!
[10:16] <StevenK> Heh, I was just thinking that.
[10:16] <StevenK> % hostname
[10:16] <StevenK> liquified
[10:17] <crimsun> I actually had no say in its naming.  It was done by the admin.
[10:17] <crimsun> the other machine's hostname is "FUN".  Truly creative.
[10:17] <StevenK> A fun box. Hrm.....
[10:34] <siretart> crimsun: I see that you're updating pbuilder-gutsy on tiber
[10:34] <siretart> crimsun: do you notice any problems there?
[10:34] <pygi> hey siretart ^_^
[10:34] <siretart> hi pygi
[10:35] <crimsun> siretart: I was going to pbuild rhythmbox there, but it was updating much more slowly than usual - on the tune of 8 K/s
[10:36] <crimsun> other than that, I don't notice anything horrendous
[10:36] <siretart> crimsun: yes, its awfully slow. I wanted to reboot tiber to boot a 2.6.17 kernel
[10:36] <siretart> I hope dapper's userspace can handle this
[10:37] <crimsun> the indicator says ~2.5 minutes of downloading updated packages remaining
[10:38] <siretart> okay, please ping me when you're done
[10:38] <Fujitsu> siretart: Userspace shouldn't be a problem, but are you sure it works with the NIC again?
[10:38] <siretart> I'll reboot tiber than
[10:38] <crimsun> siretart: sure thing.
[10:38] <siretart> Fujitsu: no idea. I hope it does. that's what I want to figure out
[10:38] <StevenK> Large Ubuntu changes to debian/rules, and the Debian maintainer just went and rewrote it.
[10:38] <siretart> Fujitsu: if it does come up, I'll upgrade tiber to edgy and then to feisty. and see what gets broken
[10:39] <Fujitsu> Sounds nice and messy.
[10:39] <siretart> StevenK: what package? who was it/
[10:39] <Fujitsu> Mekong is still (semi-)happily running Dapper with a Breezy kernel.
[10:39] <StevenK> siretart: python-qt4
[10:39] <siretart> hm. Torsten Marek, never heard of him...
[10:41] <crimsun> siretart: finished & logged out
[10:42] <crimsun> Fujitsu: hmm, same situation as 0.11.0-0ubuntu2?
[10:42] <Fujitsu> crimsun: I believe so.
[10:42] <crimsun> that patch fixed things for me
[10:43] <Fujitsu> I presumed they were due to that bug, but maybe not.
[10:44] <siretart> crimsun: thanks, rebooting now
[10:46] <crimsun> Fujitsu: if you can, try removing your library and reimporting in an attempt to reproduce the symptom
[10:46] <Fujitsu> crimsun: Done a few times. It seems to only affect some of the files that are mounted on smbfs at the moment.
[10:46] <Fujitsu> (just tried copying one to another place, and it works)
[10:47] <crimsun> hmm!
[10:47] <Fujitsu> They play fine, but their tags aren't read.
[10:58] <dholbach> ooooh, new canonical job posting: http://www.ubuntu.com/employment#ISVPPS
[11:00] <crimsun> "Debian developer ideal, but must have some Linux-based packaging experience."
[11:00] <crimsun> welp, there goes me :-)
[11:10] <sorsis> where could i find more specific information of ubuntu update process?
[11:12] <imbrandon> sorsis, which update process ?
[11:12] <sorsis> how updating is done step by step
[11:12] <sorsis> dep package update
[11:12] <StevenK> Excellent. I run off to get my dinner, and while I'm gone, the band next door finish up.
[11:13] <sorsis> i'm tring to make own package repository and update-tool for client so it would be nice if i would know how it works
[11:13] <joejaxx> StevenK: :P
[11:14] <sorsis> for example if i have package program in version 0.4, newest is 0.6, but most ubuntu users are allready updated to 0.5 before. what happens?
[11:14] <joejaxx> it updates to 0.6
[11:14] <sorsis> does it distribute whole new application package or is there specifically created update packages?
[11:14] <siretart> sorsis: you understand how apt works?
[11:14] <sorsis> somewhat
[11:16] <siretart> perhaps you should read http://www.debian.org/doc/manuals/apt-howto/index.en.html
[11:16] <sorsis> is there package which updates from 0.4 to 0.6, does it have to install first update to 0.5 and then to 0.6 or does it do more like clean install of package 0.6
[11:16] <siretart> it will always try to directly update to the 'best' package
[11:17] <siretart> with 'best' being the highest version available in most cases
[11:18] <bashelier> doko: ping
[11:18] <sorsis> but is there packages which work as update packages or is it allways the normal newest application.dep which is found from repository?
[11:20] <doko> bashelier: just ask
[11:20] <siretart> sorsis: I don't understand your question
[11:20] <siretart> sorsis: I think you should really read the apt-howto
[11:21] <bashelier> doko: ok sorry, I've just succesfully build gdc with gcc-4.1, but with --disbale-shared, as indicated on upstream website, could you tell me how is it a problem really ?
[11:22] <bashelier> how much*
[11:23] <doko> bashelier: the only thing I can see: if we teach the gcc driver to know about the D language, then we might get into problems; as long as you use gdc as the compiler driver, things should work well
[11:23] <\sh> moins
[11:23] <\sh> who wants to take care about wine in ubuntu?
[11:24] <sorsis> siretart: lets say that you have installed application-0.4. your neighbour has installed 0.5. repository provides version 0.6. do both ger same package while they do upgrade, or do both get different package?
[11:24] <bashelier> \sh: me :)
[11:24] <\sh> bashelier, do you have upload rights or a sponsor which is in ubuntu-wine team?
[11:24] <siretart> sorsis: if they are both using the same repository, both will get 0.6 on the next upgrade
[11:24] <\sh> (no motu is in ubuntu-wine btw...pls support the ubuntu-wine team, thx=
[11:25] <bashelier> doko: then, why not to build gdc only from the gdc source tarball, and --disable-shared if with_d = yes ?
[11:25] <\sh> bashelier, gdc just compiles with a complete gnu-c source tree
[11:25] <sorsis> siretart: but is it same package? i understand that both upgrade to 0.6 but is it the same package they get?
[11:25] <sorsis> siretart: bit by bit
[11:26] <siretart> sorsis: err, apt 'just' downloads packages from the archive. it calls dpkg for the actual upgrade. does this help you?
[11:26] <bashelier> \sh: I'm in contact with yuriy in the ubuntu-wine team
[11:26] <sorsis> siretart: do people who don't have program installed at all use the same package to get fresh installment
[11:26] <\sh> bashelier, you need at least a sponsor from motu...
[11:26] <sorsis> so dpkg handles the update process more specifically
[11:26] <sorsis> siretart: yes that helps. thank you.
[11:26] <\sh> bashelier, take the new packages from archive.linux-server.org, i packaged them last saturday
[11:26] <bashelier> \sh: no problem for that, can ask several frenchs MOTUs
[11:27] <\sh> bashelier, tonio or raphink are good candidates ;)
[11:27] <raphink> what for?
[11:27] <\sh> raphink, sponosring wine uploads :)
[11:28] <raphink> I'm not a big alcohol fan ;)
[11:28] <bashelier> ^^"
[11:28] <raphink> (nor a win32 fan either)
[11:28] <raphink> but I can sponsor uploads if necessary
[11:28] <bashelier> \sh: dgeting it
[11:28] <raphink> just send me the debdiff with an explanation if necessary
[11:29] <bashelier> raphink: ok, thanks :)
[11:29] <\sh> raphink, wine has only new upstream versions ;) so -S -sa and a debdiff is not a good solution :)
[11:29] <raphink> ah it's a new upstream
[11:29] <raphink> well then send the package by email or put it somewhere
[11:31] <bashelier> raphink: I'm rather going to put it somewere, is is 15M size
[11:31] <raphink> ok then
[11:31] <raphink> you can put it on REVU oetherwise
[11:32] <\sh> bashelier, push it to a bugreport :)
[11:33] <bashelier> \sh: ok :)
[11:33] <doko> bashelier: I do not want to build it from the gcc-4.1 source; but it might be worth to make the gcc driver be knowledgable about D sources (like done for java and ada sources)
[11:42] <\sh> bashelier, have fun with wine :)
[11:42] <\sh> bashelier, and please talk to scott ritchie, who is doing the winehq packages...
[11:43] <bashelier> \sh: I will, thanks for everything :)
[11:43] <bashelier> have a nice day \sh
[11:47] <bashelier> doko: so what do you suggest finally ?
[11:48] <doko> bashelier: nothing else than suggested previously =) add the D tar.gz to the gdc source package, don't modify the driver (yet).
[11:49] <bashelier> doko: ok, I'll send you the final debdiff against gcc-4.1 right after my exams :)
[11:50] <doko> bashelier: cool
[11:53] <bashelier> raphink: ping
[11:55] <bashelier> raphink: here is the bug, https://bugs.launchpad.net/ubuntu/+source/wine/+bug/118616, should I add a changelog entry to mention I'm going to maint it in ubuntu ?
[11:55] <ubotu> Launchpad bug 118616 in wine "Please upload wine 0.9.38" [Undecided,Unconfirmed]
[11:57] <svschwartz> nice bug ))
[11:58] <persia> bashelier: To make reviewing easy, consider attaching an interdiff of the debian/ directory (so the reviewer can see how the packaging changed).
[11:58] <bashelier> persia: as \sh just said, this is just a new upstream release :)
[11:59] <persia> bashelier: Right.  That makes for a small interdiff :)
[12:00] <bashelier> persia: okay, hold on a second :)
[12:02] <bashelier> persia: the "small" interdiff is 12216 lines long ^^"
[12:02] <johnnybuoy> hi all!
[12:02] <persia> bashelier: That's the output of `interdiff -z packagename_version-revision.diff.gz packagename_newversion-newrevision.diff.gz > packagename_version-newrevision.interdiff`?
[12:03] <johnnybuoy> is there someone familiar with mono here?
[12:03] <johnnybuoy> I'm trying to get banter compiled, but I have problems with the mono deps
[12:04] <johnnybuoy> it seems ubuntu has a lot of mono libs missing yet
[12:04] <bashelier> persia:  wc -l wine_0.9.38-0ubuntu1.interdiff
[12:04] <bashelier> 12216 wine_0.9.38-0ubuntu1.interdiff
[12:04] <johnnybuoy> so I'm looking for gnome-keyring-sharp, but it seems it's not in gutsy (libgnome-keyring-cil)
[12:04] <johnnybuoy> and the feisty version doesn't work
[12:05] <StevenK> One conflict fixed for python-qt4. Only three more to go.
[12:05] <persia> bashelier: That's a huge amount!  Either lots of patches were accepted upstream (and removed), or lots of patches were added to the new upstream.  Either way, it's probably good to try to explain it.
[12:06] <bashelier> johnnybuoy: if the API of mono-libs are not considered as "stable" yet, they can't be put in the GAC, so it's must be a path problem,see:
[12:06] <bashelier> apt-cache madison libgnome-keyring-cil
[12:06] <bashelier> libgnome-keyring-cil |    0.0.1-8 | http://archive.ubuntu.com feisty/universe Packages
[12:06] <bashelier> gnome-keyring-sharp |    0.0.1-8 | http://archive.ubuntu.com feisty/universe Sources
[12:06] <bashelier> gnome-keyring-sharp |    0.0.1-7 | http://archive.ubuntu.com dapper/universe Sources
[12:06] <bashelier> gnome-keyring-sharp |    0.0.1-8 | http://archive.ubuntu.com edgy/universe Sources
[12:06] <johnnybuoy> ah, okay, I'll try the source deb
[12:07] <Fujitsu> !info libgnome-keyring-cil gutsy
[12:07] <ubotu> Package libgnome-keyring-cil does not exist in gutsy
[12:07] <johnnybuoy> nope
[12:07] <johnnybuoy> it's not in gutsy
[12:07] <bashelier> persia: ok then, don't have time to do it now, but is it really necessary ? this version have been packaged by \sh, I'm just asking for upload, thing that he would have done if...
[12:08] <Fujitsu> `(From Debian) RoM; obsolete' is the reason for removal.
[12:08] <johnnybuoy> Fujitsu, obsolete?
[12:09] <persia> bashelier: It's not a requirement: it just makes it easier for the reviewer when the packaging changes are already explained.
[12:09] <Fujitsu> johnnybuoy: Right. Debian bug #392427
[12:09] <bashelier> persia: ok, I'll try to do that tonight, thanks
[12:09] <ubotu> Debian bug 392427 in ftp.debian.org "RM: gnome-keyring-sharp -- obsolete" [Normal,Closed]  http://bugs.debian.org/392427
[12:10] <johnnybuoy> strange
[12:10] <johnnybuoy> why does banter depend on it then?
[12:11] <Fujitsu> Because mono is strange.
[12:12] <Fujitsu> !find gnome-keyring-sharp gutsy
[12:13] <ubotu> Package/file gnome-keyring-sharp does not exist in gutsy
[12:13] <Fujitsu> It'd be nice to know why it was obsolete...
[12:13] <persia> Fujitsu: http://russell.rucus.net/2005/gnome-keyring-sharp/
[12:14] <Fujitsu> persia: Ah, thanks.
[12:15] <Fujitsu> Maintainers probably should give a reason when requesting removals.
[12:27] <raphink> bashelier: how come the changelog was made by \sh?
[12:50] <siretart> raphink: the problem with wine isn't that it is maintained by MOTU team, but that it isn't maintained at all :(
[12:50] <siretart> raphink: in the past, \sh was in effect the only one updating the package to the latest version. but that's all
[12:51] <raphink> right
[12:51] <raphink> although it's a popular package
[12:52] <siretart> that's the problem with it
[12:52] <raphink> it's good if bashelier wants to take that responsability
[12:52] <siretart> it has a very high userbase, but nobody is interested in working on it :(
[12:52] <raphink> very understandably
[12:52] <raphink> ;)
[12:52] <siretart> e.g.: if the apport crash reports are not usable for wine, we should add an apport hook to disable them
[12:52] <raphink> I mean I wouldn't like to spend the little time I have on a win32-centered project
[12:53] <raphink> siretart: I see
[12:53] <siretart> there are many more problems with it
[12:53] <bashelier> raphink: I do :)
[12:53] <raphink> which is good bashelier
[12:53] <siretart> bashelier: you want to work on wine?
[12:53] <raphink> yes siretart, he wants to support wine
[12:53] <siretart> great news
[12:54] <raphink> yep
[12:54] <siretart> bashelier: are you already in 'ubuntu-wine'?
[12:54] <highvoltage> I have to package a win32 product suite for a client. it would also be nice if there were guidelines on how windows software should be packaged.
[12:54] <raphink> do you feel at ease with packaging bashelier? I see yo uhave a few packages in gutsy already
[12:55] <raphink> very good point highvoltage
[12:55] <raphink> I've seen horrid packages for win32 apps lately
[12:55] <pygi> highvoltage, there are guidelines
[12:55] <pygi> highvoltage, wine-doors stuff
[12:55] <pygi> ergh, why is LP timing out o.O
[12:55] <siretart> raphink: my problem is that I don't have enough time and energy left to really care about wine as well
[12:56] <highvoltage> pygi: aah
[12:56] <siretart> raphink: I notice that the wine package bugs are growing over, and the package hasn't seen real maintainance work besides updating
[12:56] <siretart> and the updates between releases are nearly always looking like massive rewrites
[12:57] <pygi> highvoltage, what? :)
[12:57] <highvoltage> pygi: about the guidelines
[12:57] <siretart> ideally, we'd have a ubuntu-wine team, which tracks upstream, discusses with them, cherry-picks patches during freeze times, and triages all wine bugs
[12:57] <pygi> did you saw those guidelines highvoltage ? :)
[12:57] <highvoltage> pygi: no. where are they?
[12:58] <siretart> if bashelier is willing to work on that, you have my full support!
[12:58] <pygi> I could even package that stuff for you if you need it
[12:58] <pygi> sec
[12:58] <pygi> highvoltage, http://www.wine-doors.org/trac/wiki/HowToApplicationPack
[12:59] <highvoltage> pygi: but that doesn't use debian packages, does it?
[12:59] <pygi> highvoltage, nop
[12:59] <pygi> but it does enable you to package/update/whatever windows applications
[12:59] <highvoltage> pygi: ah, well I mean specifically in context of ubuntu packages
[01:01] <pygi> oh, sorry then
[01:01] <bashelier> siretart: ok thanks a lot :)
[01:03] <siretart> bashelier: as a start, could you please have a look at http://archive.linux-server.org/
[01:03] <siretart> bashelier: please import them to the ~ubuntu-wine bzr branches on lp
[01:04] <bashelier> siretart: just have to join the ubuntu-wine team first
[01:05] <siretart> bashelier: you can prepare the branches in your personal branches first
[01:05] <bashelier> siretart: ok :)
[01:20] <imbrandon> i think i might have some time to wine triage later today too possibly
[01:20] <imbrandon> and yes that apport hook would be nice
[01:26] <DarkSun88> Hi all
[01:27] <bashelier> siretart: just pushing now
[01:27] <RainCT> Hey
[01:28] <RainCT> do you know when LP will be back?
[01:28] <persia> RainCT: Hi.  Did you see the upstream comment about desktop-file-utils?
[01:29] <RainCT> Hi persia. Yes. Do you know where the CVS for desktop-file-utils is?
[01:31] <persia> RainCT: http://webcvs.freedesktop.org/menus/desktop-file-utils/ or cvs.freedesktop.org module menus/desktop-file-utils.
[01:32] <RainCT> persia: ah yes just found it
[01:33] <RainCT> persia: what should I do if that version is updated? reject the bug and open a new one requesting a new package for desktop-file-utils?
[01:36] <persia> RainCT: You can either reject the bug and make a new one, or add a comment saying that upstream version x.y addresses this issue.  I recommend editing the bug, as that way the current subscribers will continue to see your work on it, and it is less likely to get lost.  Don't forget to update the upstream bug as well, either with a patch if more is required, or to close it if everything is addressed with the rewrite.
[01:38] <RainCT> persia: okay then I'll update it
[01:38] <RainCT> persia: it seems everything is ok with the new one
[01:39] <persia> RainCT: Thank you for chasing this.
[01:41] <apachelogger> omg
[01:41] <apachelogger> evil lintian :S
[01:41] <apachelogger> W: krawlsite: binary-or-shlib-defines-rpath ./usr/bin/krawlsite /usr/lib:/usr/share/qt3/lib
[01:41] <apachelogger> suggestions what I can do?
[01:42] <TheMuso> apachelogger: There is a utility that can strip that stuff from binaries.
[01:42] <TheMuso> apachelogger: Give chrpath a try.
[01:43] <RainCT> persia: is the tag called 'needs-packaging'?
[01:44] <RainCT> ah yes found it
[01:44] <persia> RainCT: Not in this case, as the package already exists.  You just want the "upgrade" tag. "Needs-Packaging" is for a new package, not yet in the archives.
[01:44] <RainCT> persia: should be tagget 'update' or?
[01:45] <RainCT> :p
[01:45] <persia> RainCT: Yes.
[01:45] <fernando> moin all
[01:47] <pochu> !tags
[01:47] <ubotu> Sorry, I don't know anything about tags - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[01:47] <RainCT> persia: ok, I'll try to package it on wednesday. thanks for your help!
[01:49] <persia> RainCT: That would be great.  Thank you very much.
[01:51] <dholbach> TheMuso: new lsr - maybe you want a new contributor to do the update? :_)
[01:51] <TheMuso> dholbach: I don't mind doing it.
[01:51] <dholbach> alrighty
[01:52] <RainCT> is there something I can work on from school (aka without linux)?
[01:54] <persia> RainCT: Translations, bug triage, .desktop files and icons don't need Linux.  Remember to test when you get home before uploading the patches.
[01:54] <pochu> !tags is We use some common tags for the bugs. Check https://wiki.ubuntu.com/BugSquad/Tags to know them.
[01:55] <Riddell> Nightrose: hi, I hear you're interested in helping with kubuntu packages?
[01:55] <RainCT> persia: translations isn't possible with my language (catalan), don't ask me why :S. I'm triaging bugs now but I don't think I'm very good in this :p
[01:56] <StevenK> RainCT: Why not? Because Jordi Mallach has done of all of them?
[01:57] <RainCT> Stevenk: xDD
[01:57] <RainCT> StevenK: no, I think they are set as suggestions and not used or something strange
[01:57] <RainCT> well I've to go
[01:57] <RainCT> bye
[01:57] <xxxxx1> morning people!
[01:59] <ScottK> Good morning
[02:00] <ScottK> nixternal: Re your discussion about who can copyright stuff last night, this message from the clamsmtp author might be of interest http://preview.tinyurl.com/2c4k7l
[02:02] <Nightrose> Riddell: hi yea thats right
[02:03] <Riddell> Nightrose: cool, do join us in #kubuntu-devel if you like
[02:07] <ScottK> bashelier: If you are going to do someone else's merges, please ask first.
[02:08] <pygi> anyone around? :)
[02:08] <pygi> pochu, poke! :)
[02:09] <pygi> (messing with your package, so if you wanna sponsor, I'd be grateful ;))
[02:09] <pochu> pygi: hi
[02:09] <pygi> hey ^^ Mind sponsoring an upload for me?
[02:09] <pochu> Which package?
[02:09] <pochu> pygi: I don't have upload rights :)
[02:09] <pygi> pochu, oh! I'll bug someone else then :) Scribes btw  ;)
[02:10] <pygi> who wanna sponsor a package? raise your hands now :)
[02:12] <persia> pygi: Is it a new revision, or a new package?  If a new revision, subscribing ubuntu-universe-sponsors should get attention within a day or so (especially for a merge).
[02:12] <pygi> persia, I know that, but heh :P New revision :)
[02:14] <pochu> !importance
[02:14] <ubotu> Sorry, I don't know anything about importance - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[02:15] <pygi> pochu, hehe :)
[02:17] <pochu> pygi: btw, what are the changes to scribes? My sponsor will upload <IP_ADDRESS> tonight.
[02:18] <pygi> pochu, meh, I created a <IP_ADDRESS> package :p
[02:18] <pygi> pochu, you should talk to it's authors you know :)
[02:18] <pygi> but ok, then I can remove my packaging
[02:18] <pygi> oh well
[02:19] <pochu> pygi: talk to whom?
[02:19] <pygi> pochu, authors of scribes ;)
[02:19] <pochu> I've already done it ;)
[02:21] <pygi> pochu, meh, didn't meant that
[02:21] <pygi> I mean you should talk to them all the time :p
[02:21] <bueroman> 1.2G maemo-sdk-vm.tar.bz2
[02:22] <bueroman> sorry! wrong channel! :(
[02:24] <pochu> pygi: oh :)
[02:27] <PriceChild> persia, pochu I added !tags for you :)
[02:28] <pochu> PriceChild: thanks a lot :)
[02:28] <pochu> PriceChild: I have a question, have you added them in all channels, or just in these two?
[02:28] <PriceChild> all
[02:28] <pochu> Cool
[02:28] <persia> PriceChild: Thanks a lot.
[02:28] <pochu> PriceChild: Maybe you can add !importance to all too. I've miss is here :)
[02:28] <pochu> !importance
[02:28] <ubotu> Sorry, I don't know anything about importance - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[02:30] <PriceChild> !importance | pochu
[02:30] <ubotu> pochu: You can learn about setting bug importance at https://wiki.ubuntu.com/Bugs/Importance
[02:32] <pochu> PriceChild: thanks :)
[02:33] <RainCT> persia: I know you didn't ask but I tell you for the case you have some suggestion.
[02:33] <RainCT> persia: (btw, say it if I'm too tiresome ;-P)
[02:34] <persia> RainCT: No worries.  I'll just ignore you if you're too tiresome :)  I've only submitted a couple translations to Rosetta, but my understanding is that you need to be a member of the appropriate translation team to submit final translations, but that suggestions are set for review by the team, and appreciated.
[02:35] <persia> s/but/and/2
[02:48] <Hobbsee> hi all!
[02:48] <xxxxx1> morning hobbsee!
[02:48] <xxxxx1> core-hobbsee :>
[02:48] <ScottK> Hello Hobbsee
[02:49] <Hobbsee> :)
[02:49] <Hobbsee> :)
[03:10] <koke_> hi all!
[03:12] <ScottK> Hello koke_
[03:30] <highvoltage> I have a makefile that does a         find usr/ -type f >> debian/install
[03:30] <StevenK> Ewww!
[03:31] <highvoltage> but the filenames have spaces in, which doesn't seem to work that well
[03:31] <highvoltage> StevenK: do you have an alternative for me? :)
[03:31] <StevenK> Yeah. Listing them manually? Like it's going to change every other day.
[03:31] <highvoltage> StevenK: I need it automated, because the package contains more than 500 little files
[03:32] <StevenK> highvoltage: And? debian/install can contain wildcards.
[03:32] <highvoltage> ah ok. so I'll just do the find usr/ -type f then, and put in a * wherever I see a space?
[03:33] <StevenK> Twitch
[03:33] <StevenK> Um, don't do that, then?
[03:34] <highvoltage> StevenK: sorry, I'm not following you
[03:35] <StevenK> highvoltage: Okay, my point is that the list of files isn't going to change very often. I daresay those 500 small files are spread over like five directories. So you can put debian/usr/lib/* in debian/install
[03:35] <persia> highvoltage: Why does the makefile modify debian/install?  If it's debian/rules, debian/install should already be populated.  If it's a separate makefile, it would be better to patch it to use a collection (perhaps tracked during the build), and use the local install: rule to put them in $(PREFIX)/usr/lib/
[03:37] <highvoltage> StevenK: aah, use wildcards like that. I see
[03:38] <StevenK> highvoltage: If you don't use wildcards, there will be pain. Your pain. :-)
[03:38] <highvoltage> StevenK, persia: well, this particular package is for a Windows product, so this contains this programs software that will go into the wine "drive_c" directory
[03:38] <highvoltage> StevenK: heh :)
[03:41] <highvoltage> what's the point in having an install file anyway? Why not install everything that you have in your package directory?
[03:41] <StevenK> If they're already under debian/<package> you don't need a .install file
[03:43] <persia> highvoltage: The debian/install file is to install extra stuff that the upstream makefile failed to install (often used for local things that are stored in debian/).
[03:43] <highvoltage> perhaps I should do that?
[03:43] <highvoltage> persia: aaaaah
[03:47] <highvoltage> StevenK: when you say debian/<package>, does <package> mean the package name as defined in the control/changelog file?
[03:47] <highvoltage> StevenK: for example, would I put my files under debian/package-name/usr ?
[03:48] <StevenK> The package name in the changelog is the source package name.
[03:49] <StevenK> I mean one of the binary packages listed in the control file.
[03:51] <highvoltage> StevenK: ok
[03:51] <highvoltage> StevenK: where should I put the files then?
[03:52] <StevenK> Um, I'd suggest debian/<package>/usr/share/<package>
[04:20] <highvoltage> *sigh*. I still end up with a practically empty .deb
[04:20] <StevenK> highvoltage: You can e-mail a link to the source and I can look when I get to work?
[04:22] <highvoltage> StevenK: that will be appreciated, thanks
[04:22] <StevenK> highvoltage<EMAIL_ADDRESS>[04:22] <highvoltage> StevenK: do you have irc access at work?
[04:23] <StevenK> When I choose to. :-)
[04:23] <StevenK> highvoltage: It's 12:23am local, so I won't be at work for roughly 8 hours
[04:24] <highvoltage> StevenK: aah, ok. goodnight!
[04:24] <StevenK> Night!
[04:29] <Hobbsee> hiya Nightrose
[04:30] <Nightrose> hey Hobbsee - cheer from me too for your success - shure a lot of people allready did that ;-)
[04:31] <Hobbsee> Nightrose: thankyou :)
[04:34] <Qball> Hobbsee: what did you do
[04:35] <Hobbsee> Qball: i went to the moon.
[04:35] <Qball> aah
[04:35] <Qball> boring
[04:35] <Hobbsee> Nightrose: what kind of stuff have you looked into packaging so far?
[04:36] <leonel> good week everyone !
[04:36] <Nightrose> Hobbsee: unfortunatly nothing so far - right now I'm bussy washing my cloth from linuxtag, getting the room tidy and writing a blogentry about our booth and stuff at linuxtag
[04:37] <Nightrose> butt I'll do that later
[04:37] <Nightrose> -t
[04:38] <Hobbsee> Nightrose: ahh, fun :)
[04:38] <Hobbsee> nixternal: did you ever get your answer?
[04:39] <joejaxx> Hello All
[04:39] <Hobbsee> hi joejaxx
[04:39] <joejaxx> :)
[04:47] <bashelier> siretart: here it is https://code.launchpad.net/~bashelier/wine/winehq-upstream, and I'm now part of the ubuntu-wine team :)
[04:48] <joejaxx> :)
[05:27] <nixternal> Hobbsee: get my answer on what
[05:28] <Hobbsee> nixternal: the copyright for an aliased name
[05:28] <nixternal> ahh, not yet
[05:30] <dholbach> anybody interested in updating telepathy-python telepathy-glib and libtelepathy - I'm happy to review and sponsor
[05:31] <mruiz> :-)
[05:33] <bashelier> dholbach: what is it ? new upstream release ? merge ?
[05:34] <dholbach> bashelier: new releases
[05:34] <bashelier> dholbach: I can do that :)
[05:34] <dholbach> rock and roll
[05:34] <dholbach> let me know how it goes
[05:37] <fernando> bashelier: hi
[05:38] <fernando> bashelier: let's go to work together on its ?
[05:38] <bashelier> dholbach: libtelepathy latest revision is -1, is the package synced from debian ?
[05:38] <dholbach> bashelier: I guess so
[05:38] <bashelier> dholbach: do you have the upload right on mentors ?
[05:38] <dholbach> no, I'd upload it to Ubuntu - to Debian, I can't upload
[05:39] <bashelier> dholbach: if not, I can put it on REVU, upload it in debian with my sponsor and then sync it
[05:39] <bashelier> fernando: on telepathy ? :)
[05:39] <siretart> bashelier: err, nice, but how do you intend to use the branch?
[05:40] <dholbach> bashelier: as you like it, let me know if there's something to review
[05:42] <bashelier> dholbach: just have to test build and then I'll put it on revu, hold one 2 minutes ;)
[05:42] <dholbach> bashelier: take your time
[05:42] <dholbach> bashelier: coordinate with fernando for the tarballs
[05:42] <dholbach> bashelier: maybe you can even cross-review
[05:42] <dholbach> let me know how that goes
[05:43] <bashelier> dholbach: np
[05:56] <bashelier> dholbach: http://revu.tauware.de/details.py?upid=5364
[05:57] <dholbach> fernando: which updates are you doing?
[05:57] <fernando> dholbach: python-telepathy together with bashelier
[05:57] <bashelier> ^^
[05:58] <dholbach> super
[05:58] <dholbach> bashelier: checking it out in a bit
[06:00] <mruiz> hi all. Someone know if the Uploader field (Debian) in debian/control must me replaced as XBSC-Original-Uploader ? I ask, bacuse https://wiki.ubuntu.com/DebianMaintainerField is only about Maintainer...
[06:00] <pochu> mruiz: no, leave the uploader as it is.
[06:01] <mruiz> thanks pochu
[06:01] <nixternal> unless you have ubuntu edits
[06:01] <pochu> Since it doesn't mean anything in Ubuntu.
[06:01] <nixternal> pochu: that isn't correct, crimsun pointed me to an email last night
[06:01] <bashelier> dholbach: ok thanks :)
[06:01] <mruiz> nixternal, :o
[06:01] <nixternal> we do use the XBSC-Original-Maintainer: now and use MOTU for the Maintainer...only in Ubuntu edits though
[06:01] <nixternal> so if your package is something like foo_1.0-1ubuntu1 then it would have the Maintainer set to MOTU
[06:02] <nixternal> and the orig maintainer set to XSBC-Original-Maintainer
[06:02] <dqdev> hello all! I have an 'urgent' question
[06:02] <nixternal> and then make a note in the changelog
[06:02] <dqdev> after an update of ubuntu, the graphical envirnoment went crazy. BTW I am using ubuntu 7.04 AMD64. Whenever I change desktops, I lose the application-bar (up) or the lower-panel. Any ideas what;s wrong?
[06:02] <mruiz> nixternal, I did it
[06:02] <pochu> nixternal: That's what I meant, sorry if I wasn't clear :)
[06:02] <nixternal> hehe
[06:02] <mruiz> nixternal: I'm asking about Uploader field ;-)
[06:02] <nixternal> OH
[06:02] <nixternal> damnit, I just ran out of breath for a misunderstanding
[06:03] <nixternal> ;p
[06:03] <mruiz> hehehehe
[06:03] <nixternal> ya leave it alone ;)
[06:03] <nixternal> sorry....
[06:03] <pochu> nixternal: lol, you confused me :)
[06:03] <nixternal> pochu: and I confused myself, so somehow I think that makes us even :)
[06:04] <mruiz> It was my fault :P
[06:04] <nixternal> I just seen the XSBC thing
[06:04] <dqdev> and whenever I try to playy a video with movie player, the window turns into black or other elements come in the middle
[06:04] <nixternal> that is what you call "sipping the juice w/o knowing the flavor"
[06:05] <nixternal> dqdev: #ubuntu is where you will get an answer for that..you are in a dev channel of highly caffeniete people, of which most are foaming at the mouth in a very rabid way :)
[06:05] <Hobbsee> mmm...caffeine...
[06:08] <dholbach> bashelier, fernando: seems we can sync telepathy-python from incoming
[06:15] <dholbach> bashelier, fernando: good work on libtelepathy (uploading)
[06:18] <dholbach> bashelier, fernando: libtelepathy uploaded - thanks you two
[06:19] <Dabian> ubotu: seen mwolson
[06:19] <ubotu> Sorry, I don't know anything about seen mwolson - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[06:20] <fernando> dholbach: on libtelepathy, only Mr. bashelier work in it.
[06:20] <fernando> bashelier: good work
[06:20] <bashelier> thanks :)
[06:20] <bashelier> fernando: what about telepathy-python then ? :)
[06:20] <dholbach> maybe you can work on the other together
[06:20] <bashelier> dholbach: this is already the case in pm ;)
[06:21] <dholbach> rock
[06:21] <dholbach> thanks a lot you two - I think I can push all my package update requests to the two of you from now on ;-)
[06:22] <bashelier> dholbach: feel free to ask anytime ;)
[06:22] <dholbach> thanks :)
[06:22] <dholbach> brb
[06:27] <xxxxx1> hello dholbach
[06:28] <dholbach> heya xxxxx1
[06:29] <bashelier> dholbach: telepathy-glib builds fine, just have to fix lintian warnings and then I'll upload it
[06:30] <dholbach> bashelier: excellent
[06:31] <bashelier> dholbach: "File telepathy-glib.devhelp.gz not symlinked to from devhelp dirs": "to from" sounds strange doesn't it ?
[06:32] <dholbach> a bit, yes
[06:38] <bashelier> dholbach: this warning can't be fixed because devhelp is in Suggests, and then it's impossible to make a dh_link in the debhelp dirs
[06:39] <dholbach> you could add the directory to debian/dirs
[06:39] <bashelier> dholbach: right :)
[06:42] <Martinp23> dholbach: would you happen to have any jobs for me to do? :)
[06:43] <dholbach> Martinp23: if you coordinate with fernando - there are some gnome updates on http://mail.gnome.org/archives/ftp-release-list/2007-June/thread.html
[06:43] <dholbach> Martinp23: I'm happy to review
[06:43] <dholbach> although your updates might not land in the next 3-4 days
[06:43] <dholbach> as we're approaching gutsy tribe 1 release
[06:44] <bashelier> Martinp23: you should have a look to https://wiki.ubuntu.com/MOTU/TODO ;)
[06:44] <Martinp23> bashelier: hehe :)
[06:44] <Martinp23> dholbach: OK - will do
[06:45] <Martinp23> brb
[06:53] <mruiz> dholbach: when Merges/Syncs days will finish ?
[06:54] <dholbach> mruiz: I'd reckon that with UpstreamVersionFreeze we should have them done
[06:54] <dholbach> hey gpocentek
[06:54] <dholbach> gpocentek: thanks for goffice/gnumeric goodness
[06:55] <gpocentek> dholbach: np
[06:55] <Adri2000> pochu: bug #87959 - see, soyuz tried to re-close the bug :/ you should file a bug against soyuz
[06:55] <ubotu> Launchpad bug 87959 in listen "Listen should build-dep in firefox-dev" [Medium,Fix released]  https://launchpad.net/bugs/87959
[07:01] <bashelier> dholbach: I'm sorry, I don't now how to fix this warning: don't know where the link should be
[07:01] <dholbach> bashelier: drop me a mail with that and I'll look at it tomorrow
[07:02] <bashelier> dholbach: ok
[07:02] <dholbach> thanks bashelier
[07:03] <dholbach> it does not sound like a serious issue to me, but nice if we can get it fixed
[07:03] <cbx33> hey all
[07:03] <cbx33> ping imbrandon
[07:29] <pochu> Adri2000: Bug #118671
[07:29] <ubotu> Launchpad bug 118671 in soyuz "Changelog-Close feature tries to close already-closed bugs." [Undecided,Unconfirmed]  https://launchpad.net/bugs/118671
[07:43] <LaserJock> pochu: related to that, what if we don't want to actually close the bug
[07:44] <LaserJock> I suppose we should have some documentation on that
[07:45] <pochu> LaserJock: then split the "LP:" part.
[07:45] <pochu> Since it looks for "LP: #" constructions
[07:46] <LaserJock> yeah, but something should be documented
[07:46] <pochu> Maybe we should use "Ubuntu:"
[07:46] <pochu> LaserJock: Yes, I'll write something later tonight.
[07:46] <LaserJock> we've used something like LP: # for a long time for all referenced in changelogs
[08:05] <stgraber> If a MOTU has some time : http://revu.tauware.de/details.py?upid=5355 , thanks
[08:05] <bmm> Anybody willing to post a comment on ccbuild http://revu.tauware.de/details.py?upid=5295 is very welcome, I'm looking for my first avocate
[08:05] <bmm> stgraber: haha, what timing ;-)
[08:06] <stgraber> yeah :)
[08:08] <bashelier> stgraber: have you made the orig tarball by yourself ?
[08:10] <stgraber> bashelier: I had to, as mentioned in the changelog it's been retrieved from git
[08:10] <ScottK> geser: Did you know someone is working on decoratortools to get it into Debian?
[08:10] <geser> I've seen an ITP for it
[08:11] <geser> Debian bug #425761
[08:11] <ubotu> Debian bug 425761 in wnpp "ITP: decoratortools -- version-agnostic decorators support for Python" [Wishlist,Open]  http://bugs.debian.org/425761
[08:11] <ScottK> There's a draft package in the Debian Python Modules Team svn.
[08:11] <bashelier> StevenK: I have a question, README.Debian-source must be added in case the orig tarball has been repacked, is it already the case if it has been build from a git repo for example ?
[08:11] <bashelier> erf
[08:11] <ScottK> Would it make sense to help push that one out and not make an Ubuntu unique one?
[08:12] <bashelier> ScottK: this question was for you ^^"
[08:12] <ScottK> geser: http://svn.debian.org/wsvn/python-modules/packages/decoratortools/trunk/debian/?rev=0&sc=0
[08:13] <geser> this doesn't surprise me as kov filed the ITP
[08:13] <ScottK> bashelier: If you didn't have an orig.tar.gz, then you should explain how to construct what you used for the source tarball.
[08:13] <bashelier> ScottK: ok thanks :)
[08:14] <bashelier> stgraber: see what ScottK just said first ;)
[08:14] <ScottK> geser: Debian Python Modules Team is very open to Ubuntu people IME.
[08:14] <bashelier> stgraber: then, just let me the time to eat and I'll finish your review ;)
[08:16] <gpocentek> somebody knows if the beryl packages on REVU can be archieved?
[08:17] <gpocentek> looks like they are all in the archive
[08:20] <geser> ScottK: I only needed decoratortools to unbreak turbogears but as Debian worked around it (for now) I stopped packaging it.
[08:21] <ScottK> OK.  So you aren't actively working the package?  Nevemind then.
[08:21] <ScottK> Nevemind/Nevermind
[08:21] <geser> no
[08:21] <stgraber> bashelier: ok, there is the way to build it in the changelog (get the git, remove .git and existing debian/ + add COPYING (gpl-2)), so I think that should be ok
[08:22] <ScottK> geser: Should we archive it then?
[08:23] <bashelier> stgraber: exact commands must be listed in README.Debian-source, please read http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html#s-bpp-origtargz ;)
[08:24] <geser> ScottK: yes, did I forget it?
[08:25] <ScottK> geser: Yes.  I just archived it.
[08:26] <geser> hmm, I remember archiving it
[08:27] <gpocentek> I'm wondering what happened on REVU
[08:27] <gpocentek> all the beryl packages were archived IIRC
[08:27] <ScottK> geser: I see other stuff that I'm pretty sure was archived.  It looks like when the server was rebooted, some stuff came back for some reason.
[08:28] <geser> I'm pretty sure the beryl packages were also already archived
[08:29] <ScottK> Maybe siretart will read the scrollback and can explain...
[08:32] <bashelier> siretart: ping
[08:35] <stgraber> bashelier: New version uploaded to revu, renamed the directory inside the .orig.tar.gz and added the README.Debian-source thing
[08:36] <bashelier> stgraber: ok, let me have a look :)
[08:38] <bashelier> stgraber: first, minor: please add a blank line between lines 1 and 2 in debian/changelog
[08:40] <bashelier> stgraber: extented description: please add Homepage, idented with two spaces
[08:40] <bashelier> stgraber: please remove libpam-exec.install, and put "README" in a debian/docs file
[08:42] <bashelier> stgraber: debian/rules: please put "-Wl,-z,defs" in first CFLAGS declaration line 12
[08:43] <bashelier> stgraber: try to be a bit more precise in manpage, and use /usr/share/debhelper/dh_make/debian/manpage.1 as template ;) also see others pam_* manpages for examples
[08:44] <bashelier> siretart: debian/changelog: missing package license, incomplete license declaration, see /usr/share/debhelper/dh_make/debian/copyright
[08:56] <stgraber> bashelier: thank you, I'll have a look at that a bit later
[09:43] <Riddell> revu server is slow to download from today
[09:43] <nixternal> revu server is always slow for me..but not as slow as LP
[09:43] <nixternal> or the wikis
[09:43] <nixternal> the wikis for me, open a page, go to lunch, come back and it should be done loading
[09:44] <Kmos> hehe
[09:44] <Kmos> nixternal: have you tried www.opendns.com ?
[09:44] <nixternal> ya, it is actually worse
[09:44] <Kmos> jesus
[09:44] <nixternal> opendns causes to many problems for me
[09:44] <Kmos> it's your ISP problem so..
[09:45] <nixternal> well, it isn't so much a DNS problem as it is a connection problem
[09:45] <nixternal> I use a caching server here to help
[09:46] <Kmos> :)
[09:46] <Kmos> i've 512/128 kbps
[09:46] <Kmos> and it's fast
[09:46] <nixternal> I am 8MB/384k
[09:46] <Kmos> and it's so slowly
[09:46] <Kmos> hehe
[09:46] <Kmos> traceroute give you a lot of hops ?
[09:46] <nixternal> ya, there is a booged connection between me and the UK somewhere
[09:46] <nixternal> ya, around 30+ hops usually
[09:46] <Kmos> yeah
[09:46] <Kmos> i got that too i think
[09:47] <Kmos> my ISP uses http://www.cogentco.com
[09:48] <Q-FUNK> http://30hopsmax.at/
[09:49] <Kmos> web based game
[09:49] <Kmos> !?
[09:49] <Kmos> lol
[09:55] <cbx33> pingity imbrandon
[09:56] <Kmos> nixternal: http://paste.ubuntu-nl.org/24117/
[09:56] <Kmos> i've also 30 hops
[09:57] <pygi> cbx33, :)
[09:58] <cbx33> hey pygi
[10:04] <HiFructose> guys where can i report a package bug?
[10:05] <HiFructose> well, packaging bug to be clear sorry
[10:05] <xxxxx1> HiFructose: in launchpad
[10:05] <xxxxx1> hmm
[10:05] <HiFructose> xxxxx1: ok thanks
[10:05] <xxxxx1> packaging bug?
[10:05] <HiFructose> xxxxx1: libsexymm is missing the pkg-config file
[10:05] <ScottK> HiFructose: Tag it as a packaging bug when you file it.
[10:05] <HiFructose> allright
[10:06] <HiFructose> ok actually, i just download the source, and the source package doesn't have one either
[10:07] <HiFructose> report to upstream first then?
[10:07] <HiFructose> or will/would/should the package maintainer in ubuntu add one on his own?
[10:37] <fdoving> who are revu admins?
[10:38] <crevette> hello
[10:39] <fdoving> hi.
[10:39] <crevette> I would need the REVU keyring to be re-sync to permit to upload packages
[10:39] <pygi> sispotty probably
[10:40] <RainCT> Hi
[10:40] <jussi01> ajmitch: can do it if he has time crevette
[10:50] <Qball> Seveas: I had to poke you
[11:18] <RainCT> keescook: thanks :)
[11:23] <keescook> RainCT: sure!  thanks for getting it built up!  :)
[11:53] <xxxxx1> bye all!
[11:53] <DarkSun88> G'night
[12:05] <siretart> gpocentek: ScottK: geser: yes, all uploads > 3 months ago have been archived, as discussed/announced on<EMAIL_ADDRESS>nobody objected/joined in the discussion that time


[05:13] -queuebot:#ubuntu-release- New binary: ocaml-qcheck [s390x] (eoan-proposed/universe) [0.9-2] (no packageset)
[05:14] -queuebot:#ubuntu-release- New binary: ocaml-qcheck [i386] (eoan-proposed/universe) [0.9-2] (no packageset)
[05:14] -queuebot:#ubuntu-release- New binary: ocaml-qcheck [ppc64el] (eoan-proposed/universe) [0.9-2] (no packageset)
[05:14] -queuebot:#ubuntu-release- New binary: croaring [amd64] (eoan-proposed/universe) [0.2.63+ds-2] (no packageset)
[05:14] -queuebot:#ubuntu-release- New binary: ocaml-qcheck [amd64] (eoan-proposed/universe) [0.9-2] (no packageset)
[05:15] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [amd64] (eoan-proposed/universe) [0.15.1-1] (no packageset)
[05:15] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [s390x] (eoan-proposed/universe) [0.15.1-1] (no packageset)
[05:15] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [i386] (eoan-proposed/universe) [0.15.1-1] (no packageset)
[05:15] -queuebot:#ubuntu-release- New binary: phpmyadmin-motranslator [amd64] (eoan-proposed/universe) [4.0-2] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: ocaml-qcheck [arm64] (eoan-proposed/universe) [0.9-2] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: ocaml-qcheck [armhf] (eoan-proposed/universe) [0.9-2] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [ppc64el] (eoan-proposed/universe) [0.15.1-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [arm64] (eoan-proposed/universe) [0.15.1-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [armhf] (eoan-proposed/universe) [0.15.1-1] (no packageset)
[06:08] <ginggs> Morning! would an archive admin please remove r-bioc-metagenomeseq ?  LP: #1839706
[06:09] <ginggs> ^ this should unconstipate r-base
[07:45] <vorlon> ginggs: done
[07:46] <ginggs> vorlon: thanks!
[08:34] <Locutusofborg> now rbase is entangled with everything else, sigh
[08:35] <Locutusofborg> vorlon, I don't know the deal.ii arm64 failure, I tried old gcc, old fortran, old foo old bar, no idea how to fix it
[08:36] <Locutusofborg> ./obj-aarch64-linux-gnu/source/non_matching/./source/non_matching/coupling.cc:178:(.text._ZN6dealii11NonMatching32create_coupling_sparsity_patternILi2ELi1ELi2ENS_16TrilinosWrappers20BlockSparsityPatternEfEEvRKNS_9GridTools5CacheIXT_EXT1_EEERKNS_10DoFHandlerIXT_EXT1_EEERKNS9_IXT0_EXT1_EEERKNS_10QuadratureIXT0_EEERT2_RKNS_17AffineConstraintsIT3_EERKNS_13ComponentMaskEST_RKNS_7MappingIXT0_EXT1_EEE[_ZN6dealii11NonMatching32create
[08:36] <Locutusofborg> _coupling_sparsity_patternILi2ELi1ELi2ENS_16TrilinosWrappers20BlockSparsityPatternEfEEvRKNS_9GridTools5CacheIXT_EXT1_EEERKNS_10DoFHandlerIXT_EXT1_EEERKNS9_IXT0_EXT1_EEERKNS_10QuadratureIXT0_EEERT2_RKNS_17AffineConstraintsIT3_EERKNS_13ComponentMaskEST_RKNS_7MappingIXT0_EXT1_EEE]+0x5c): additional relocation overflows omitted from the output
[08:36] <Locutusofborg> looks like a binutils regression to me
[08:36] <Locutusofborg> I would kick it out from arm64 to let something progress
[08:37] <Locutusofborg> it is blocking a lot of stuff
[09:13] <ginggs> would someone please kick the scipy can along?  'force-badtest python-scipy/1.2.2-4/amd64 python-scipy/1.2.2-4/i386'
[09:20] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [arm64] (eoan-proposed) [0.15.1-1]
[09:20] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [armhf] (eoan-proposed) [0.15.1-1]
[09:21] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [amd64] (eoan-proposed) [0.15.1-1]
[09:21] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [ppc64el] (eoan-proposed) [0.15.1-1]
[09:21] -queuebot:#ubuntu-release- New: accepted ocaml-qcheck [amd64] (eoan-proposed) [0.9-2]
[09:21] -queuebot:#ubuntu-release- New: accepted ocaml-qcheck [armhf] (eoan-proposed) [0.9-2]
[09:21] -queuebot:#ubuntu-release- New: accepted ocaml-qcheck [ppc64el] (eoan-proposed) [0.9-2]
[09:21] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [i386] (eoan-proposed) [0.15.1-1]
[09:21] -queuebot:#ubuntu-release- New: accepted ocaml-qcheck [arm64] (eoan-proposed) [0.9-2]
[09:21] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [s390x] (eoan-proposed) [0.15.1-1]
[09:21] -queuebot:#ubuntu-release- New: accepted ocaml-qcheck [i386] (eoan-proposed) [0.9-2]
[09:21] -queuebot:#ubuntu-release- New: accepted ocaml-qcheck [s390x] (eoan-proposed) [0.9-2]
[09:21] -queuebot:#ubuntu-release- New: accepted phpmyadmin-motranslator [amd64] (eoan-proposed) [4.0-2]
[09:31] -queuebot:#ubuntu-release- Unapproved: gpgme1.0 (bionic-proposed/main) [1.10.0-1ubuntu2 => 1.10.0-1ubuntu2.1] (core)
[13:04] <ginggs> r-base migrated \o/
[15:20] <Locutusofborg> ginggs, great success!
[16:53] <Locutusofborg> Hello, general question: is it possible to know all the Ubuntu delta I own?
[16:53]  * Locutusofborg moves to #-devel
[16:58] <ginggs> in soviet russia, ubuntu delta own you
[17:18] -queuebot:#ubuntu-release- New binary: m2crypto [amd64] (eoan-proposed/universe) [0.31.0-5] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: rust-backtrace [i386] (eoan-proposed/universe) [0.3.34-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: rust-phf [amd64] (eoan-proposed/universe) [0.7.24-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: rust-rand-core [amd64] (eoan-proposed/universe) [0.5.0-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: rust-backtrace [s390x] (eoan-proposed/universe) [0.3.34-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: rust-string [amd64] (eoan-proposed/universe) [0.2.1-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: rust-phf [i386] (eoan-proposed/universe) [0.7.24-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: m2crypto [s390x] (eoan-proposed/universe) [0.31.0-5] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: rust-string [i386] (eoan-proposed/universe) [0.2.1-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: rust-wild [i386] (eoan-proposed/none) [2.0.2-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: rust-backtrace [amd64] (eoan-proposed/universe) [0.3.34-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: rust-wild [amd64] (eoan-proposed/none) [2.0.2-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: rust-pango [amd64] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: rust-phf [s390x] (eoan-proposed/universe) [0.7.24-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: rust-pango [i386] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: rust-rand-core [i386] (eoan-proposed/universe) [0.5.0-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: rust-backtrace [armhf] (eoan-proposed/universe) [0.3.34-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: rust-phf-macros [amd64] (eoan-proposed/none) [0.7.24-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: rust-pango [s390x] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: rust-phf [armhf] (eoan-proposed/universe) [0.7.24-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: rust-phf [arm64] (eoan-proposed/universe) [0.7.24-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: rust-rand-core [s390x] (eoan-proposed/universe) [0.5.0-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: m2crypto [ppc64el] (eoan-proposed/universe) [0.31.0-5] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: rust-phf-macros [i386] (eoan-proposed/none) [0.7.24-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: rust-rand-core [armhf] (eoan-proposed/universe) [0.5.0-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: rust-string [s390x] (eoan-proposed/universe) [0.2.1-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: rust-backtrace [arm64] (eoan-proposed/universe) [0.3.34-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: rust-string [arm64] (eoan-proposed/universe) [0.2.1-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: rust-phf-macros [s390x] (eoan-proposed/none) [0.7.24-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: rust-wild [s390x] (eoan-proposed/none) [2.0.2-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: rust-pango [armhf] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: rust-string [armhf] (eoan-proposed/universe) [0.2.1-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: rust-pango [arm64] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: m2crypto [arm64] (eoan-proposed/universe) [0.31.0-5] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: rust-phf-macros [arm64] (eoan-proposed/universe) [0.7.24-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: rust-rand-core [arm64] (eoan-proposed/universe) [0.5.0-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: rust-backtrace [ppc64el] (eoan-proposed/universe) [0.3.34-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: rust-phf [ppc64el] (eoan-proposed/universe) [0.7.24-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: rust-pango [ppc64el] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: rust-rand-core [ppc64el] (eoan-proposed/universe) [0.5.0-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: rust-phf-macros [armhf] (eoan-proposed/universe) [0.7.24-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: rust-string [ppc64el] (eoan-proposed/universe) [0.2.1-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: m2crypto [armhf] (eoan-proposed/universe) [0.31.0-5] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: rust-wild [armhf] (eoan-proposed/universe) [2.0.2-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: rust-wild [arm64] (eoan-proposed/universe) [2.0.2-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: rust-phf-macros [ppc64el] (eoan-proposed/universe) [0.7.24-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: rust-wild [ppc64el] (eoan-proposed/universe) [2.0.2-1] (no packageset)
[18:01] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [ppc64el] (eoan-proposed) [0.7.24-1]
[18:01] -queuebot:#ubuntu-release- New: accepted rust-wild [ppc64el] (eoan-proposed) [2.0.2-1]
[18:02] -queuebot:#ubuntu-release- New: accepted m2crypto [armhf] (eoan-proposed) [0.31.0-5]
[18:02] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [armhf] (eoan-proposed) [0.7.24-1]
[18:02] -queuebot:#ubuntu-release- New: accepted rust-rand-core [arm64] (eoan-proposed) [0.5.0-1]
[18:02] -queuebot:#ubuntu-release- New: accepted rust-string [ppc64el] (eoan-proposed) [0.2.1-1]
[18:02] -queuebot:#ubuntu-release- New: accepted rust-wild [armhf] (eoan-proposed) [2.0.2-1]
[18:02] -queuebot:#ubuntu-release- New: accepted rust-pango [ppc64el] (eoan-proposed) [0.7.0-1]
[18:02] -queuebot:#ubuntu-release- New: accepted rust-rand-core [ppc64el] (eoan-proposed) [0.5.0-1]
[18:02] -queuebot:#ubuntu-release- New: accepted rust-phf [ppc64el] (eoan-proposed) [0.7.24-1]
[18:02] -queuebot:#ubuntu-release- New: accepted rust-wild [arm64] (eoan-proposed) [2.0.2-1]
[18:03] -queuebot:#ubuntu-release- New: accepted m2crypto [arm64] (eoan-proposed) [0.31.0-5]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-backtrace [ppc64el] (eoan-proposed) [0.3.34-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-pango [armhf] (eoan-proposed) [0.7.0-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [s390x] (eoan-proposed) [0.7.24-1]
[18:03] -queuebot:#ubuntu-release- New: accepted m2crypto [ppc64el] (eoan-proposed) [0.31.0-5]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [arm64] (eoan-proposed) [0.7.24-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-pango [arm64] (eoan-proposed) [0.7.0-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-string [armhf] (eoan-proposed) [0.2.1-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-backtrace [arm64] (eoan-proposed) [0.3.34-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-phf [arm64] (eoan-proposed) [0.7.24-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-rand-core [armhf] (eoan-proposed) [0.5.0-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-string [arm64] (eoan-proposed) [0.2.1-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-wild [s390x] (eoan-proposed) [2.0.2-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [i386] (eoan-proposed) [0.7.24-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-rand-core [s390x] (eoan-proposed) [0.5.0-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-phf [armhf] (eoan-proposed) [0.7.24-1]
[18:03] -queuebot:#ubuntu-release- New: accepted rust-string [s390x] (eoan-proposed) [0.2.1-1]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-backtrace [armhf] (eoan-proposed) [0.3.34-1]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-pango [i386] (eoan-proposed) [0.7.0-1]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [amd64] (eoan-proposed) [0.7.24-1]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-pango [amd64] (eoan-proposed) [0.7.0-1]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-rand-core [i386] (eoan-proposed) [0.5.0-1]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-pango [s390x] (eoan-proposed) [0.7.0-1]
[18:04] -queuebot:#ubuntu-release- New: accepted m2crypto [s390x] (eoan-proposed) [0.31.0-5]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-phf [s390x] (eoan-proposed) [0.7.24-1]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-wild [amd64] (eoan-proposed) [2.0.2-1]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-backtrace [amd64] (eoan-proposed) [0.3.34-1]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-wild [i386] (eoan-proposed) [2.0.2-1]
[18:04] -queuebot:#ubuntu-release- New: accepted rust-string [i386] (eoan-proposed) [0.2.1-1]
[18:05] -queuebot:#ubuntu-release- New: accepted m2crypto [amd64] (eoan-proposed) [0.31.0-5]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-backtrace [s390x] (eoan-proposed) [0.3.34-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-phf [i386] (eoan-proposed) [0.7.24-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-string [amd64] (eoan-proposed) [0.2.1-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-backtrace [i386] (eoan-proposed) [0.3.34-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-rand-core [amd64] (eoan-proposed) [0.5.0-1]
[18:05] -queuebot:#ubuntu-release- New: accepted rust-phf [amd64] (eoan-proposed) [0.7.24-1]
[18:05] -queuebot:#ubuntu-release- New: accepted croaring [amd64] (eoan-proposed) [0.2.63+ds-2]
[18:05] -queuebot:#ubuntu-release- New: accepted safeclib [armhf] (eoan-proposed) [3.5-1]
[18:05] -queuebot:#ubuntu-release- New: accepted safeclib [ppc64el] (eoan-proposed) [3.5-1]
[18:05] -queuebot:#ubuntu-release- New: accepted safeclib [amd64] (eoan-proposed) [3.5-1]
[18:05] -queuebot:#ubuntu-release- New: accepted safeclib [i386] (eoan-proposed) [3.5-1]
[18:34] -queuebot:#ubuntu-release- New binary: okteta [s390x] (eoan-proposed/universe) [5:0.26.2-2ubuntu1] (kubuntu)
[18:36] -queuebot:#ubuntu-release- New binary: okteta [amd64] (eoan-proposed/universe) [5:0.26.2-2ubuntu1] (kubuntu)
[18:36] -queuebot:#ubuntu-release- New binary: okteta [i386] (eoan-proposed/universe) [5:0.26.2-2ubuntu1] (kubuntu)
[18:36] -queuebot:#ubuntu-release- New binary: okteta [ppc64el] (eoan-proposed/universe) [5:0.26.2-2ubuntu1] (kubuntu)
[18:50] -queuebot:#ubuntu-release- New binary: okteta [arm64] (eoan-proposed/universe) [5:0.26.2-2ubuntu1] (kubuntu)
[18:56] -queuebot:#ubuntu-release- New binary: okteta [armhf] (eoan-proposed/universe) [5:0.26.2-2ubuntu1] (kubuntu)
[19:52] <tjaalton> xrdp-hwe-18.04 is still in binary NEW, any AA availabe to give it a nudge?
[19:54] <vorlon> looking
[19:57] -queuebot:#ubuntu-release- New: accepted xrdp-hwe-18.04 [amd64] (bionic-proposed) [0.9.5-2~18.04.1]
[19:57] -queuebot:#ubuntu-release- New: accepted xrdp-hwe-18.04 [armhf] (bionic-proposed) [0.9.5-2~18.04.1]
[19:57] -queuebot:#ubuntu-release- New: accepted xrdp-hwe-18.04 [ppc64el] (bionic-proposed) [0.9.5-2~18.04.1]
[19:57] -queuebot:#ubuntu-release- New: accepted xrdp-hwe-18.04 [arm64] (bionic-proposed) [0.9.5-2~18.04.1]
[19:57] -queuebot:#ubuntu-release- New: accepted xrdp-hwe-18.04 [s390x] (bionic-proposed) [0.9.5-2~18.04.1]
[19:57] -queuebot:#ubuntu-release- New: accepted xrdp-hwe-18.04 [i386] (bionic-proposed) [0.9.5-2~18.04.1]
[19:57] <tjaalton> vorlon: great, thanks!
[20:16] <ginggs> would someone please kick the scipy can along?  'force-badtest python-scipy/1.2.2-4/amd64 python-scipy/1.2.2-4/i386'
[20:20] -queuebot:#ubuntu-release- New binary: ipmctl [amd64] (eoan-proposed/universe) [<IP_ADDRESS>74+ds-1] (no packageset)
[20:23] <tumbleweed> ginggs: sure. Kicking...
[20:23] <vorlon> ginggs: I had resisted doing so up to now because the test failures in the new upstream version are different from those in the old, and I am not confident they don't point to a serious problem with the new package.  any insight there?
[20:24] <tumbleweed> ah, I saw a screenful of red, and didn't dig deeper
[20:24] -queuebot:#ubuntu-release- New: accepted ipmctl [amd64] (eoan-proposed) [<IP_ADDRESS>74+ds-1]
[20:25] <tumbleweed> vorlon: wanna revert that?
[20:25] <ginggs> vorlon: the tests run fine for me locally, and in debian
[20:25] <vorlon> tumbleweed: no, I was going to add the hint anyway because I also don't like blocking packages based on test failures that are not regressions :)
[20:25] <vorlon> ginggs: do you think the tests need more memory?
[20:26] <tumbleweed> I see they got killed, so that's a possibility
[20:27] <ginggs> vorlon: quite possibly, iirc they are already running on the huge instances
[20:42] <vorlon> ginggs: I don't find python-scipy mentioned in autopkgtest-cloud
[20:47] <ginggs> vorlon: ok, do you think that's worth trying first?
[21:24] -queuebot:#ubuntu-release- Unapproved: grub2 (eoan-proposed/main) [2.04-1ubuntu5 => 2.04-1ubuntu5] (core)
[21:24] <vorlon> ginggs: yes
[21:49] -queuebot:#ubuntu-release- Unapproved: grub2 (eoan-proposed/main) [2.04-1ubuntu5 => 2.04-1ubuntu5] (core)


[21:47] <hads> Yay, an hour before I leave home to go overseas for the week and I do an rm * on my home directory.
[21:47] <hads> I'll assume there was nothing important in there.
[22:03] <ajmitch> hads: that's a little bit of a pain
[22:04] <ajmitch> if it was literally rm *, it at least wouldn't get .gnupg, .ssh, etc